TDoc | Title | Source |
---|---|---|
R4-2215300 | RAN4#104-e Meeting Report | ETSI MCC |
R4-2215301 | Agenda for RAN4 #104bis-e | RAN4 Chair (Huawei) |
R4-2215302 | RAN4#104bis-e E-Meeting Arrangements and Guidelines | RAN4 Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2215303 | FREQUENCY ARRANGEMENTS FOR IMT IN THE BAND 470 703 MHZ | APT Wireless Group (AWG) |
R4-2215304 | LS on BWP operation without restriction | RAN1 |
R4-2215305 | Reply LS to RAN4 on DMRS bundling | RAN1 |
R4-2215306 | LS on switching option capability for UL 2Tx-2Tx switching | RAN2 |
R4-2215307 | LS to RAN4 on RLM/BFD relaxation for ePowSav | RAN2 |
R4-2215308 | Reply LS on CCA configurations of neighbour cells | RAN2 |
R4-2215309 | LS to RAN4 on capability for PRS measurement without MG | RAN2 |
R4-2215310 | LS on L1/L2-based inter-cell mobility | RAN2 |
R4-2215311 | LS on work towards two new recommendations "Generic unwanted emission characteristics of base stations/mobile stations using the terrestrial radio interfaces of IMT-2020" | RAN5 |
R4-2215312 | Reply LS on the feasibility of testing UE initiated SDT data transmission in RRC_INACTIVE | RAN5 |
R4-2215313 | LS to RAN4 on A-MPR regions for NS_50 (Power Class 2) | RAN5 |
R4-2215314 | LS on FS_VMR solutions review | SA2 |
TDoc | Title | Source |
---|---|---|
R4-2216607 | CR to 38.106: ACRR requirements | NEC |
R4-2216610 | CR to 38.106: EVM requirements | NEC |
R4-2216613 | CR to 38.106: ACLR requirements | NEC |
R4-2217287 | CR to 38.106: ACRR requirements | NEC |
R4-2217288 | CR to 38.106: EVM requirements | NEC |
R4-2217289 | CR to 38.106: ACLR requirements | NEC |
TDoc | Title | Source |
---|---|---|
R4-2215490 | CR for 38.106 OOB gain radiated related requirements | CMCC |
R4-2217290 | CR for 38.106 OOB gain radiated related requirements | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215732 | Discussion on NR repeater EMC performance assessment | ZTE Corporation |
R4-2215733 | Draft CR to TS38.114 repeater clause 8.1 R17 | ZTE Corporation |
R4-2215960 | Draft CR to TS 38.114 Clause 4.5 | Ericsson |
R4-2216038 | CR to TS38.114 repeater clause 8.1 R17 | ZTE Corporation |
R4-2217291 | Draft CR to TS 38.114 Clause 4.5 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216192 | NR Repeater stimulus signal | Nokia, Nokia Shanghai Bell |
R4-2216500 | Repeater stimulus signal spectral purity annex | Keysight Technologies UK Ltd |
R4-2217299 | TS 38.115-1 v0.2.0 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2216611 | TP to 38.115-1: EVM requirement | NEC |
R4-2216838 | TP to TS 38.115-1: Repeater output power (6.1, 6.2) | Huawei, HiSilicon |
R4-2217292 | TP to 38.115-1: EVM requirement | NEC |
R4-2217293 | TP to TS 38.115-1: Repeater output power (6.1, 6.2) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216608 | TP to 38.115-1: ACRR requirement | NEC |
R4-2216614 | TP to 38.115-1: ACLR requirement | NEC |
R4-2217294 | TP to 38.115-1: ACRR requirement | NEC |
R4-2217295 | TP to 38.115-1: ACLR requirement | NEC |
TDoc | Title | Source |
---|---|---|
R4-2215387 | TP for TS 38.115-1: scope and reference | CATT |
R4-2216837 | TP to TS 38.115-1: Measurement uncertainties and test requirements (4.1) | Huawei, HiSilicon |
R4-2216839 | TP to TS 38.115-1: Annex B: Environmental requirements for the repeater | Huawei, HiSilicon |
R4-2216840 | TP to TS 38.115-1: Annex C: Test tolerances and derivation of test requirements | Huawei, HiSilicon |
R4-2216841 | TP to TS 38.115-1: Annex E: Characteristics of interfering signals | Huawei, HiSilicon |
R4-2217296 | TP for TS 38.115-1: scope and reference | CATT |
R4-2217297 | TP to TS 38.115-1: Measurement uncertainties and test requirements (4.1) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216567 | TP for TS 38.115-2: Scope, reference and editorial changes | ZTE Corporation |
R4-2216568 | TS 38.115-2 | ZTE Corporation |
R4-2217300 | TP for TS 38.115-2: Scope, reference and editorial changes | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216612 | TP to 38.115-2: OTA EVM requirement | NEC |
R4-2216843 | TP to TS 38.115-2: OTA output power (6.1, 6.2) | Huawei, HiSilicon |
R4-2217310 | TP to TS 38.115-2: OTA output power (6.1, 6.2) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215791 | Discussion on test tolerance values of OOB Gain for FR2 repeater | NTT DOCOMO, INC. |
R4-2216194 | Draft CR to TS 38.115-2 with updates and corrections | Nokia, Nokia Shanghai Bell |
R4-2216609 | TP to 38.115-2: OTA ACRR requirement | NEC |
R4-2216615 | TP to 38.115-2: OTA ACLR requirement | NEC |
R4-2217301 | Draft CR to TS 38.115-2 with updates and corrections | Nokia, Nokia Shanghai Bell |
R4-2217305 | TP to 38.115-2: OTA EVM requirement | NEC |
R4-2217306 | TP to 38.115-2: OTA ACRR requirement | NEC |
R4-2217307 | TP to 38.115-2: OTA ACLR requirement | NEC |
TDoc | Title | Source |
---|---|---|
R4-2215388 | TP for TS 38.115-2: scope and reference | CATT |
R4-2215389 | Discussion of remaining issues for FR2 MU | CATT |
R4-2216193 | TP to TS 38.115-2 Annex I TRP measurement procedures | Nokia, Nokia Shanghai Bell |
R4-2216407 | Spectrum purity requirements for FR2 | Ericsson |
R4-2216408 | Draft CR to 38.115-2: Spectrum purity requirements | Ericsson |
R4-2216842 | TP to TS 38.115-2: Measurement uncertainties and test requirements (4.1) | Huawei, HiSilicon |
R4-2216844 | TP to TS 38.115-2: Annex A: Environmental requirements for the repeater | Huawei, HiSilicon |
R4-2216845 | TP to TS 38.115-2: Annex B: Test tolerances and derivation of test requirements | Huawei, HiSilicon |
R4-2216846 | On the need for the Annex on Characteristics of interfering signals in TS 38.115-2 | Huawei, HiSilicon |
R4-2217302 | TP to TS 38.115-2 Annex I TRP measurement procedures | Nokia, Nokia Shanghai Bell |
R4-2217303 | Draft CR to 38.115-2: Spectrum purity requirements | Ericsson |
R4-2217308 | TP to TS 38.115-2: Measurement uncertainties and test requirements (4.1) | Huawei, HiSilicon |
R4-2217309 | TP to TS 38.115-2: Annex B: Test tolerances and derivation of test requirements | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216885 | Email discussion summary for [104-bis-e][301] NR_Repeater_RFMaintenance | Moderator (Nokia) |
R4-2216886 | Email discussion summary for 1[04-bis-e][302] NR_Repeater_RFConformance_Part1 | Moderator (Huawei) |
R4-2216887 | Email discussion summary for [104-bis-e][303] NR_Repeater_RFConformance_Part2 | Moderator (CATT) |
R4-2217298 | WF on stimulus signal spectral purity requirements for FR1 and FR2 | Nokia |
R4-2217475 | Email discussion summary for [104-bis-e][301] NR_Repeater_RFMaintenance | Moderator (Nokia) |
R4-2217476 | Email discussion summary for [104-bis-e][302] NR_Repeater_RFConformance_Part1 | Moderator (Huawei) |
R4-2217477 | Email discussion summary for [104-bis-e][303] NR_Repeater_RFConformance_Part2 | Moderator (CATT) |
R4-2217511 | Email discussion summary for 1[04-bis-e][302] NR_Repeater_RFConformance_Part1 | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2216150 | CR to 38.101-5: Corrections on section 5.3.3 for NTN UE | Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2215336 | Corrections to SAN TS 38.108 | THALES |
R4-2215337 | Discussion on SAN Out-of-Band Mask | THALES |
R4-2215412 | CR for TS 38.108, Corrrect definiiton order in sub-clause 3.1 | CATT |
R4-2217316 | Corrections to SAN TS 38.108 | THALES |
TDoc | Title | Source |
---|---|---|
R4-2216064 | CR for TR 38.863 to maintain SAN parts | Huawei, HiSilicon |
R4-2216065 | Discussion on definition of delta FOBUE | Huawei, HiSilicon |
R4-2216066 | CR for 38.108 to maitain unwanted emissions clause | Huawei, HiSilicon |
R4-2216526 | NTN - Discussion on remaining open issues | Ericsson |
R4-2216527 | CR to TS 38.108 - Updates related to DfOBUE - conducted clauses | Ericsson |
R4-2217312 | CR for 38.108 to maitain unwanted emissions clause | Huawei, HiSilicon |
R4-2217313 | CR to TS 38.108 - Updates related to DfOBUE - conducted clauses | Ericsson |
R4-2217315 | CR for TR 38.863 to maintain SAN parts | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216528 | CR to TS 38.108 - Updates related to DfOBUE - radiated clauses | Ericsson |
R4-2217314 | CR to TS 38.108 - Updates related to DfOBUE - radiated clauses | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215802 | TS 38.181 v0.2.0 NR Satellite Access Node (SAN) conformance testing | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215401 | TP for TS 38.181 Clause 4.9 RF channels and test models | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215350 | TP for TS 38.181 - Annex D | THALES |
R4-2215400 | TP for TS 38.181 Clause 4.7 Test configurations and Clause 4.8 Applicability of requirements | CATT |
R4-2217322 | TP for TS 38.181 - Annex D | THALES |
R4-2217503 | TP for TS 38.181 Clause 4.7 Test configurations and Clause 4.8 Applicability of requirements | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215338 | Discussion on SAN Test Conditions | THALES |
R4-2215397 | TP for TS 38.181 Clause 1 Scope, Clause 2 References and Clause 3 Definition of terms, symbols and abbreviations | CATT |
R4-2215398 | TP for TS 38.181 Clause 4.1 Measurement uncertainties and test requirements | CATT |
R4-2215399 | TP for TS 38.181 Clause 4.6 Manufacturer declarations | CATT |
R4-2215406 | TP for TS 38.181 A.1 FRCs for RF Rx requriement(QPSK, R=1/3) and A.2 FRCs for dynamic range (16QAM, R=2/3) | CATT |
R4-2215407 | TP for TS 38.181 Annex F Calibration | CATT |
R4-2215408 | TP for TS 38.181 Annex H In-channel Tx test | CATT |
R4-2215409 | TP for TS 38.181 Annex I Transmitter spatial emissions declaration | CATT |
R4-2215410 | TP for TS 38.181 Annex K Measuring noise close to the noise-floor | CATT |
R4-2215411 | Discussion on conformance testing for NTN SAN | CATT |
R4-2216195 | TP to TS 38.181 Clauses 4.10 and 4.11 | Nokia, Nokia Shanghai Bell |
R4-2216489 | TS 38.181: TP on clause 5 | Ericsson |
R4-2216491 | TS 38.181: TP on Annex B | Ericsson |
R4-2216492 | TS 38.181: TP on Annex C | Ericsson |
R4-2216493 | TS 38.181: TP on Annex E | Ericsson |
R4-2216494 | TS 38.181: TP on Annex J | Ericsson |
R4-2216495 | Discussion on relevant test environment for SAN | Ericsson |
R4-2216847 | TP to TS 38.181: General test conditions and declarations (4.2 - 4.5) | Huawei, HiSilicon |
R4-2217323 | TP for TS 38.181 Clause 4.1 Measurement uncertainties and test requirements | CATT |
R4-2217324 | TP for TS 38.181 Annex F Calibration | CATT |
R4-2217325 | TP to TS 38.181 Clauses 4.10 and 4.11 | Nokia, Nokia Shanghai Bell |
R4-2217328 | TS 38.181: TP on Annex B | Ericsson |
R4-2217329 | TS 38.181: TP on Annex C | Ericsson |
R4-2217330 | TS 38.181: TP on Annex E | Ericsson |
R4-2217331 | TS 38.181: TP on Annex J | Ericsson |
R4-2217336 | TP to TS 38.181: General test conditions and declarations (4.2 - 4.5) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215339 | TP for TS 38.181 - Clause 6.5.3 EVM | THALES, CATT |
R4-2215340 | TP for TS 38.181 - Clause 6.6.4 OBUE | THALES |
R4-2215341 | TP for TS 38.181 - Clause 6.6.5 Spurious Emissions | THALES |
R4-2215349 | TP for TS 38.181 - Occupied BandWidth Clauses 6.6.1 and 6.6.2 | THALES |
R4-2215402 | TP for TS 38.181 Clause 6.1 General and Clause 6.2 Satellite Access Node output power | CATT, THALES |
R4-2216561 | TP for TS 38.181: Section 6.3 Output power dynamics | ZTE Corporation |
R4-2216848 | TP to TS 38.181: occupied bandwidth (6.6.1, 6.6.2) | Huawei, HiSilicon |
R4-2216849 | TP to TS 38.181: OBUE (6.6.4) | Huawei, HiSilicon |
R4-2217321 | TP for TS 38.181 - Clause 6.6.5 Spurious Emissions | THALES |
R4-2217333 | TP for TS 38.181: Section 6.3 Output power dynamics | ZTE Corporation |
R4-2217337 | TP to TS 38.181: occupied bandwidth (6.6.1, 6.6.2) | Huawei, HiSilicon |
R4-2217338 | TP to TS 38.181: OBUE (6.6.4) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215403 | TP for TS 38.181 Clause 7.1 General and Clause 7.2 Reference sensitivity level | CATT |
R4-2216196 | TP to TS 38.181 Clause 7.4 In-band selectivity and blocking | Nokia, Nokia Shanghai Bell |
R4-2216562 | TP for TS 38.181: Section 7.3 Dynamic range | ZTE Corporation |
R4-2216563 | TP for TS 38.181: Section 7.6~7.8 | ZTE Corporation |
R4-2216850 | TP to TS 38.181: Out-of-band blocking (7.5) | Huawei, HiSilicon |
R4-2217326 | TP to TS 38.181 Clause 7.4 In-band selectivity and blocking | Nokia, Nokia Shanghai Bell |
R4-2217334 | TP for TS 38.181: Section 7.3 Dynamic range | ZTE Corporation |
R4-2217339 | TP to TS 38.181: Out-of-band blocking (7.5) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215404 | TP for TS 38.181 Clause 9.1 General | CATT |
R4-2216564 | TP for TS 38.181: Section 9.4 OTA output power dynamics | ZTE Corporation |
R4-2216851 | TP to TS 38.181: OTA occupied bandwidth (9.7.1, 9.7.2) | Huawei, HiSilicon |
R4-2216852 | TP to TS 38.181: OTA ACLR (9.7.3) | Huawei, HiSilicon |
R4-2216853 | TP to TS 38.181: OTA OBUE (9.7.4) | Huawei, HiSilicon |
R4-2217335 | TP for TS 38.181: Section 9.4 OTA output power dynamics | ZTE Corporation |
R4-2217340 | TP to TS 38.181: OTA occupied bandwidth (9.7.1, 9.7.2) | Huawei, HiSilicon |
R4-2217341 | TP to TS 38.181: OTA ACLR (9.7.3) | Huawei, HiSilicon |
R4-2217342 | TP to TS 38.181: OTA OBUE (9.7.4) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215405 | TP for TS 38.181 Clause 10.1 General and Clause 10.2 OTA sensitivity | CATT |
R4-2216197 | TP to TS 38.181 Clause 10.5 In-band selectivity and blocking | Nokia, Nokia Shanghai Bell |
R4-2216490 | TS 38.181: TP on clause 10.3 OTA refsens | Ericsson |
R4-2216565 | TP for TS 38.181: Section 10.4 OTA dynamic range | ZTE Corporation |
R4-2216566 | TP for TS 38.181: Section 10.7~10.9 | ZTE Corporation |
R4-2216854 | TP to TS 38.181: OTA out-of-band blocking (10.6) | Huawei, HiSilicon |
R4-2217327 | TP to TS 38.181 Clause 10.5 In-band selectivity and blocking | Nokia, Nokia Shanghai Bell |
R4-2217332 | TS 38.181: TP on clause 10.3 OTA refsens | Ericsson |
R4-2217343 | TP to TS 38.181: OTA out-of-band blocking (10.6) | Huawei, HiSilicon |
R4-2217508 | TP to TS 38.181 Clause 10.5 In-band selectivity and blocking | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215315 | CR: 0005 Doppler test conditions for RF requirements 38.101-5 | Qualcomm Incorporated |
R4-2216593 | On decoupling DL MIMO from number of Rx branches for NTN UE capabilities | Apple |
R4-2216594 | CR to 38.101-5 on corrections related to 64QAM requirements | Apple |
R4-2216640 | On NTN Frequency error requirment | Ericsson |
R4-2216641 | CR on NTN Frequency error requirement | Ericsson |
R4-2216835 | NR NTN Frequency Error | MediaTek (Chengdu) Inc. |
R4-2217317 | CR to 38.101-5 on corrections related to 64QAM requirements | Apple |
R4-2217318 | CR on NTN Frequency error requirement | Ericsson |
R4-2217319 | CR: 0005 Doppler test conditions for RF requirements 38.101-5 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215448 | Discussion on the remaining issues for NTN RRM | Xiaomi, CAICT |
R4-2215500 | CR on correction to cell re-selection requirement for satellite access | CMCC |
R4-2217162 | CR on correction to cell re-selection requirement for satellite access | CMCC |
R4-2217174 | WF on NR NTN RRM requirements | Qualcomm Incorporated |
R4-2217175 | Reply LS to RAN2 on measurement gap enhancements for NTN | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215391 | Discussion on fully overlapping concurrent MGs for NTN | CATT |
R4-2215603 | On measurement procedure for NTN UE | Apple |
R4-2215604 | CR on intra-frequency and inter-frequency measurement requirement without MG for NTN | Apple |
R4-2215749 | CR on intra-frequency measurements in NTN | Samsung |
R4-2215751 | Discussion on measurement procedure requirements in NTN | MediaTek inc. |
R4-2216315 | On remaining issues for NTN measurement requirements | Huawei, HiSilicon |
R4-2216316 | CR on RLM and BFR requirements for NTN | Huawei, HiSilicon |
R4-2216317 | CR on MG requirements for NTN | Huawei, HiSilicon |
R4-2216463 | CR for Cell Reselection requirements with distance trigger | Nokia, Nokia Shanghai Bell |
R4-2216472 | Discussion on Colliding Measurement Gaps | Nokia, Nokia Shanghai Bell |
R4-2216502 | CR on intra-frequency measurements for NTN | Ericsson |
R4-2216504 | Measurement requirements for NTN | Ericsson |
R4-2217163 | CR on intra-frequency and inter-frequency measurement requirement without MG for NTN | Apple |
R4-2217164 | CR on RLM and BFR requirements for NTN | Huawei, HiSilicon |
R4-2217165 | CR on MG requirements for NTN | Huawei, HiSilicon |
R4-2217166 | CR for Cell Reselection requirements with distance trigger | Nokia, Nokia Shanghai Bell |
R4-2217167 | CR on intra-frequency measurements for NTN | Ericsson |
R4-2217589 | Big CR for NTN RRM performance requirements | MCC, Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2215395 | Completing requirements for conditional handover for NTN | CATT |
R4-2215431 | CR on cell re-selection, MDT and timing requirements for NTN | CATT |
R4-2215582 | CR on scheduling restrictions for L3 measurements in FR1 for NTN | Apple |
R4-2215605 | Reply LS on measurement gap enhancements for NTN | Apple |
R4-2215748 | CR on intra-frequency cell reselection in NTN | Samsung |
R4-2216312 | Discussion on other requirements for NTN RRM | Huawei, HiSilicon |
R4-2216313 | CR on RRC re-establishment requirements for NTN | Huawei, HiSilicon |
R4-2216314 | CR on UL spatial relation switch requirements for NTN | Huawei, HiSilicon |
R4-2216464 | Editorial CR To TS 38.133 Handover requirements | Nokia, Nokia Shanghai Bell |
R4-2216467 | Transmit Timing Aspects for NTN RRM | Nokia, Nokia Shanghai Bell |
R4-2216592 | Editorial CR To TS 38.133 Handover requirements | Nokia, Nokia Shanghai Bell |
R4-2217168 | Completing requirements for conditional handover for NTN | CATT |
R4-2217169 | CR on cell re-selection, MDT and timing requirements for NTN | CATT |
R4-2217170 | CR on scheduling restrictions for L3 measurements in FR1 for NTN | Apple |
R4-2217171 | CR on UL spatial relation switch requirements for NTN | Huawei, HiSilicon |
R4-2217172 | Editorial CR To TS 38.133 Handover requirements | Nokia, Nokia Shanghai Bell |
R4-2217173 | Reply LS on measurement gap enhancements for NTN | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215449 | Discussion on the performance requirements for NTN RRM | Xiaomi, CAICT |
R4-2215501 | Discussion on RRM test cases for NTN | CMCC |
R4-2215752 | Discussion on RRM performance for NR NTN | MediaTek inc. |
R4-2215819 | Discussion on general RRM performance requirements for NR NTN | OPPO |
R4-2216318 | Discussion on measurement accuracy and TCs for NTN | Huawei, HiSilicon |
R4-2216319 | CR on measurement accuracy requirements for NTN | Huawei, HiSilicon |
R4-2216863 | draft CR of BWP switch and CBW change test cases for NR NTN | Qualcomm Incorporated |
R4-2216868 | Open Issues in NTN RRM Test Case Design | Qualcomm Incorporated |
R4-2217183 | CR on measurement accuracy requirements for NTN | Huawei, HiSilicon |
R4-2217185 | WF on performance part for NTN RRM | Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2215936 | Draft CR on test case for cell reselection to FR1 inter-frequency NR cell for satellite access | LG Electronics UK |
R4-2216320 | Discussion on cell reselection test for NTN | Huawei, HiSilicon |
R4-2216321 | CR on cell reselection TCs for NTN | Huawei, HiSilicon |
R4-2216471 | Amendments on cell reselection parameters when not using enhanced mode | Nokia, Nokia Shanghai Bell |
R4-2217182 | Draft CR on test case for cell reselection to FR1 inter-frequency NR cell for satellite access | LG Electronics UK |
R4-2217184 | CR on cell reselection TCs for NTN | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215393 | Test cases for Intra- and inter-frequency HO with known cell for NTN | CATT |
R4-2215454 | 4-step RA type randon access test for satellite access | Xiaomi, CAICT |
R4-2216322 | CR on TCs for RRC Re-establishment for NTN | Huawei, HiSilicon |
R4-2216465 | Discussion on configuration of HO aspects for NTN | Nokia, Nokia Shanghai Bell |
R4-2217176 | Test cases for Intra- and inter-frequency HO with known cell for NTN | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215392 | Discussion on test cases for handover for NTN | CATT |
R4-2215394 | Test cases for Intra- and inter-frequency CHO for NTN | CATT |
R4-2215452 | RRC connection release with redirection rest for satellite access | Xiaomi, CAICT |
R4-2216466 | Discussion on configuration of CHO aspects for NTN | Nokia, Nokia Shanghai Bell |
R4-2217177 | Test cases for Intra- and inter-frequency CHO for NTN | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215502 | draft CR for NTN timing advance adjustment accuracy test | CMCC |
R4-2216278 | Discussion on remaining issues on test cases for NTN UE timing | Huawei, HiSilicon |
R4-2216279 | DraftCR on UE transmit timing tests for NTN | Huawei, HiSilicon |
R4-2216470 | Discussion on open issues for timing advance | Nokia, Nokia Shanghai Bell |
R4-2217282 | LS on the feasibility of testing UE initiated SDT data transmission in RRC_INACTIVE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215451 | Pathloss reference signal switching delay test for satellite access | Xiaomi, CAICT |
R4-2215503 | draft CR for CSI-RS based RLM for NTN | CMCC |
R4-2216503 | draft CR on test cases of BFD and LR for SA | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215820 | CR to Test case 10-4 to 10-9 intra-frequency measurement delay with gap for satellite access | OPPO |
R4-2216323 | Discussion on measurement delay TCs for NTN | Huawei, HiSilicon |
R4-2216324 | CR on TCs for intra-frequency measurement delay for NTN | Huawei, HiSilicon |
R4-2217181 | CR to Test case 10-4 to 10-9 intra-frequency measurement delay with gap for satellite access | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215455 | Test case for inter-frequency measurement without gap for satellite access | Xiaomi, CAICT |
R4-2217180 | Test case for inter-frequency measurement without gap for satellite access | Xiaomi, CAICT |
TDoc | Title | Source |
---|---|---|
R4-2215450 | L1-RSRP measurement accuracy test for satellite access | Xiaomi, CAICT |
R4-2217178 | L1-RSRP measurement accuracy test for satellite access | Xiaomi, CAICT |
TDoc | Title | Source |
---|---|---|
R4-2215453 | SS-SINR measurement accuracy test for satellite access | Xiaomi, CAICT |
R4-2216325 | CR on general requirement for NTN RRM test cases | Huawei, HiSilicon |
R4-2217179 | SS-SINR measurement accuracy test for satellite access | Xiaomi, CAICT |
TDoc | Title | Source |
---|---|---|
R4-2215344 | Work Split for Performance Requirements in TS 38.108 and TS 38.181 | THALES |
R4-2215674 | Discussion on NTN channel model | Ericsson |
R4-2215976 | Discussion on UE NTN demod general | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215977 | Summary of simulation results for NTN SAN demodulation performance requirements | Huawei,HiSilicon |
R4-2215978 | Big CR on NTN SAN performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2215979 | Draft CR on propagation conditions of NTN SAN performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2215980 | pCR on FRC of NTN SAN performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
R4-2217349 | Draft CR on propagation conditions of NTN SAN performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2217350 | pCR on FRC of NTN SAN performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
R4-2217515 | Big CR for UE NTN performance requirements | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215548 | Simulation results for NTN SAN PUSCH demodulation | Nokia, Nokia Shanghai Bell |
R4-2215549 | Discussion on NTN SAN PUSCH demodulation requirements | Nokia, Nokia Shanghai Bell |
R4-2215675 | Discussion on general and PUSCH issue SAN demodulation | Ericsson |
R4-2215677 | Simulation results for SAN PUSCH demodulation | Ericsson |
R4-2215680 | draftCR for TS38.108 introduce FRC tables for SAN PUSCH demodulation | Ericsson |
R4-2215682 | draftCR for TS38.181 introduce SAN PUSCH conducted demodulation requirements and Annex for test setup | Ericsson |
R4-2215981 | Discussion on satellite NTN demod PUSCH | Huawei,HiSilicon |
R4-2215982 | Simulation results on satellite NTN demod PUSCH | Huawei,HiSilicon |
R4-2215983 | Draft CR on NTN SAN PUSCH performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2215984 | pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
R4-2216697 | Initial simulation results on PUSCH demodulation requirement for Rel-17 NTN | Samsung |
R4-2217351 | draftCR for TS38.108 introduce FRC tables for SAN PUSCH demodulation | Ericsson |
R4-2217352 | pCR for TS38.181 introduce SAN PUSCH conducted demodulation requirements and Annex for test setup | Ericsson |
R4-2217353 | Draft CR on NTN SAN PUSCH performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2217354 | pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215550 | Simulation results for NTN SAN PUCCH demodulation | Nokia, Nokia Shanghai Bell |
R4-2215551 | Discussion on NTN SAN PUCCH demodulation requirements | Nokia, Nokia Shanghai Bell |
R4-2215676 | Discussion on general and PUCCH issue SAN demodulation | Ericsson |
R4-2215678 | Simulation results for SAN PUCCH demodulation | Ericsson |
R4-2215681 | draftCR for TS38.108 introduce requirements for SAN PUSCH demodulation | Ericsson |
R4-2215683 | draftCR for TS38.181 introduce SAN PUCCH radiated demodulation requirements | Ericsson |
R4-2215985 | Discussion on satellite NTN demod PUCCH | Huawei,HiSilicon |
R4-2215986 | Simulation results on satellite NTN demod PUCCH | Huawei,HiSilicon |
R4-2215987 | pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
R4-2216698 | Initial simulation results on PUCCH demodulation requirement for Rel-17 NTN | Samsung |
R4-2217355 | Initial simulation results on PUCCH demodulation requirement for Rel-17 NTN | Samsung |
R4-2217356 | draftCR for TS38.108 introduce requirements for SAN PUSCH demodulation | Ericsson |
R4-2217357 | pCR for TS38.181 introduce SAN PUCCH radiated demodulation requirements | Ericsson |
R4-2217358 | pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215679 | Simulation results for SAN PRACH demodulation | Ericsson |
R4-2215684 | draftCR for TS38.181 introduce SAN PRACH conducted demodulation requirements | Ericsson |
R4-2215988 | Simulation results on satellite NTN demod PRACH | Huawei,HiSilicon |
R4-2215989 | Draft CR on NTN SAN PRACH performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2215990 | pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
R4-2216699 | Initial simulation results on PRACH demodulation requirement for Rel-17 NTN | Samsung |
R4-2217359 | pCR for TS38.181 introduce SAN PRACH conducted demodulation requirements | Ericsson |
R4-2217360 | Draft CR on NTN SAN PRACH performance requirements (TS38.108, Rel-17) | Huawei,HiSilicon |
R4-2217361 | pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17) | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215991 | Draft CR on general part of UE NTN performance requirements (TS38.101-5, Rel-17) | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215546 | Discussion on PDSCH demodulation requirements for NTN | Nokia, Nokia Shanghai Bell |
R4-2215547 | Simulation results on PDSCH demodulation requirements for NTN | Nokia, Nokia Shanghai Bell |
R4-2215583 | On PDSCH demod requirements for NTN | Apple |
R4-2215584 | Draft CR on Propagation Conditions, Physical Channels, Environmental Conditions for NTN | Apple |
R4-2215860 | Simulation Results on NTN UE PDSCH demodulation requirements | Qualcomm Incorporated |
R4-2215861 | Views on NTN UE PDSCH Requirements | Qualcomm Incorporated |
R4-2215992 | Discussion on UE NTN demod PDSCH | Huawei,HiSilicon |
R4-2215993 | Simulation results on satellite NTN demod PDSCH | Huawei,HiSilicon |
R4-2215994 | Draft CR on applicability rules of UE NTN performance requirements (TS38.101-5, Rel-17) | Huawei,HiSilicon |
R4-2216394 | Discussion on the remaining issues for PDSCH requirement of NTN | Ericsson |
R4-2216395 | Simulation results for PDSCH requirement of NTN | Ericsson |
R4-2216396 | draft CR to 38.101-5: Throughput and reference channel definition | Ericsson |
R4-2216420 | Summary of simulation results for NTN UE demodulation | Qualcomm Incorporated |
R4-2216705 | Discussion on PDSCH requirements for NR-NTN | MediaTek inc. |
R4-2217345 | Draft CR on Propagation Conditions, Physical Channels, Environmental Conditions for NTN | Apple |
R4-2217346 | Draft CR on general part of UE NTN performance requirements (TS38.101-5, Rel-17) | Huawei,HiSilicon |
R4-2217347 | Draft CR on applicability rules of UE NTN performance requirements (TS38.101-5, Rel-17) | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216888 | Email discussion summary for [104-bis-e][304] NTN_Solutions_RF_Maintenance | Moderator (Thales) |
R4-2216889 | Email discussion summary for [104-bis-e][305] NTN_Solutions_RFConformance | Moderator (Ericsson) |
R4-2216901 | [Email discussion summary for 104-bis-e][317] NR_NTN_Demod_Part1 | Moderator (Qualcomm) |
R4-2216902 | Email discussion summary for [104-bis-e][318] NR_NTN_Demod_Part2 | Moderator (Huawei) |
R4-2216912 | Email discussion summary for [104-bis-e][201] NR_NTN_solutions_RRM_1 | Moderator (Qualcomm) |
R4-2216913 | Email discussion summary for [104-bis-e][202] NR_NTN_solutions_RRM_2 | Moderator (Xiaomi) |
R4-2217134 | Email discussion summary for [104-bis-e][201] NR_NTN_solutions_RRM_1 | Moderator (Qualcomm) |
R4-2217135 | Email discussion summary for [104-bis-e][202] NR_NTN_solutions_RRM_2 | Moderator (Xiaomi) |
R4-2217311 | WF on NTN Solutions SAN RF Maintenance | THALES |
R4-2217320 | WF on NTN solutions SAN RF conformance | Ericsson |
R4-2217344 | WF for NTN demodulation requirements - general and PDSCH | Qualcomm |
R4-2217348 | WF for NTN SAN demodulation requirements | Huawei |
R4-2217478 | Email discussion summary for [104-bis-e][304] NTN_Solutions_RF_Maintenance | Moderator (Thales) |
R4-2217479 | Email discussion summary for [104-bis-e][305] NTN_Solutions_RFConformance | Moderator (Ericsson) |
R4-2217480 | [Email discussion summary for 104-bis-e][317] NR_NTN_Demod_Part1 | Moderator (Qualcomm) |
R4-2217481 | Email discussion summary for [104-bis-e][318] NR_NTN_Demod_Part2 | Moderator (Huawei) |
R4-2217509 | WF on NTN solutions SAN RF conformance | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216684 | System parameters maintenance for NR ext. to 71GHz | Intel Corporation |
R4-2217090 | WF on 60 GHz Operation bands and system parameter and UE RF requirement maintenance | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2215659 | Beam Correspondence for band n263 | Apple |
R4-2216683 | FR2-2 maintenance aspects for UE Tx | Intel Corporation |
R4-2216795 | 60 GHz UE PRACH and PTRS capabilities | Qualcomm France |
R4-2216797 | CR to 38.101-2 on band n263 UE Tx aspects | Qualcomm France |
R4-2217056 | CR to 38.101-2 on band n263 UE Tx aspects | Qualcomm France |
TDoc | Title | Source |
---|---|---|
R4-2216796 | CR to 38.101-2 on band n263 UE Rx aspects | Qualcomm France |
TDoc | Title | Source |
---|---|---|
R4-2215571 | CR to TS 38.104 on reference to FRCs | Nokia, Nokia Shanghai Bell |
R4-2215832 | CR to TS 38.104: Correction of guardband for FR2-2 in sub-clause 5.3.3 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215572 | Proposal on suitability of OTA measurement systems on BS conformance testing for extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2215830 | Draft CR to TR 37.941: Addition of aspects related to EIRP measurement in CATR relevant for FR2-2 in sub-clause 7.3, 8.3, 9.2.3 and 9.2.7 | Ericsson |
R4-2215831 | On further general aspects relevant for FR2-2 conformance testing | Ericsson |
R4-2215836 | Draft CR to TS 38.141-2: Addition of FR2-2 aspects in clause 4 | Ericsson |
R4-2217366 | Draft CR to TR 37.941: Addition of aspects related to EIRP measurement in CATR relevant for FR2-2 in sub-clause 7.3, 8.3, 9.2.3 and 9.2.7 | Ericsson |
R4-2217367 | Draft CR to TS 38.141-2: Addition of FR2-2 aspects in clause 4 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215573 | Proposal on measurement uncertainty of BS OTA transmitter requirements for extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2215828 | Draft CR to TS 38.141-2: Addition of FR2-2 transmitter support in clause 6 | Ericsson |
R4-2215833 | On further aspects related to FR2-2 transmitter conformance testing | Ericsson |
R4-2216496 | FR2-2 BS conformance test consideration for Tx testing | Keysight Technologies UK Ltd |
R4-2216498 | FR2-2 Test Model details and TP | Keysight Technologies UK Ltd |
R4-2216499 | FR2-2 EVM measurement detail and TP | Keysight Technologies UK Ltd |
R4-2216560 | Further discussion on BS conformance testing for 52.6-71GHz | ZTE Corporation |
R4-2217368 | Draft CR to TS 38.141-2: Addition of FR2-2 transmitter support in clause 6 | Ericsson |
R4-2217369 | FR2-2 EVM measurement detail and TP | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2215574 | Proposal on measurement uncertainty of BS OTA receiver requirements for extending current NR operation to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2215829 | Draft CR to TS 38.141-2: Addition of FR2-2 receiver support in clause 7 | Ericsson |
R4-2215834 | On further aspects related to FR2-2 receiver conformance testing | Ericsson |
R4-2216497 | FR2-2 BS conformance test consideration for Rx testing | Keysight Technologies UK Ltd |
R4-2217370 | Draft CR to TS 38.141-2: Addition of FR2-2 receiver support in clause 7 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215416 | Discussion of remaining issues on RRM core requirements for extension to 71GHz | CATT |
R4-2217186 | WF on core requirements maintenance for FR2-2 | Huawei, HiSilicon |
R4-2217187 | LS on capability of relaxed cell detection requirements for FR2-2 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215617 | Remaining general aspects for NR operation in 52.6GHz - 71GHz | Apple |
R4-2215799 | Discussion on TCI assumption for RSSI measurement for FR2-2 | LG Electronics Inc. |
R4-2215800 | CR on QCL-ed assumption for inter-frequency RSSI measurement in FR2-2 | LG Electronics Inc. |
R4-2216256 | CR on applicability of RRM requirements with CCA in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216261 | Discussion on general requirements on FR2-2 | Huawei, HiSilicon |
R4-2216262 | CR on RLM requirements for FR2-2 | Huawei, HiSilicon |
R4-2216263 | CR on SCell activation requirements of FR2-2 | Huawei, HiSilicon |
R4-2216882 | Draft CR on Measurement Procedures | Qualcomm Incorporated |
R4-2217188 | CR on QCL-ed assumption for inter-frequency RSSI measurement in FR2-2 | LG Electronics Inc. |
R4-2217189 | CR on SCell activation requirements of FR2-2 | Huawei, HiSilicon |
R4-2217190 | Draft CR on Measurement Procedures | Qualcomm Incorporated |
R4-2217590 | Big CR for NR operation to 71GHz RRM performance requirements | MCC, Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2215618 | LBT impacts on RRM requirements for NR operation in 52.6GHz - 71GHz | Apple |
R4-2216257 | Discussion on RRM requirements with CCA in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216264 | Discussion on LBT impact on requirements for FR2-2 | Huawei, HiSilicon |
R4-2216265 | CR on LBT assumption for FR2-2 | Huawei, HiSilicon |
R4-2216266 | CR on RSSI measurement for FR2-2 | Huawei, HiSilicon |
R4-2216606 | Reply LS on signalling of CCA configurations of neighbour cells in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217191 | CR on LBT assumption for FR2-2 | Huawei, HiSilicon |
R4-2217192 | CR on RSSI measurement for FR2-2 | Huawei, HiSilicon |
R4-2217193 | Reply LS on signalling of CCA configurations of neighbour cells in FR2-2 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215417 | Further discussion on general RRM performance requirements for NR extension to 71 GHz | CATT |
R4-2217194 | WF on NR extension to 71 GHz RRM - 1 | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2216259 | Discussion on RRM performance timing requirements in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216267 | Discussion on performance requirements for FR2-2 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215418 | Draft CR on test cases for SA RRC Re-establishment for extending NR operation to 71GHz | CATT |
R4-2216258 | Draft CR random access test cases in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216268 | CR on test cases for HO for FR2-2 | Huawei, HiSilicon |
R4-2217196 | Draft CR on test cases for SA RRC Re-establishment for extending NR operation to 71GHz | CATT |
R4-2217199 | Draft CR random access test cases in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217201 | CR on test cases for HO for FR2-2 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215419 | Draft CR on test cases for Beam failure detection and link recovery for extending NR operation to 71GHz | CATT |
R4-2216260 | Draft CR introducing BFD and TCI state switch test cases in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216501 | draft CR on Test Cases on RLM for SCell activation to 71GHz | Ericsson |
R4-2217197 | Draft CR on test cases for Beam failure detection and link recovery for extending NR operation to 71GHz | CATT |
R4-2217200 | Draft CR introducing BFD and TCI state switch test cases in FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217202 | draft CR on Test Cases on RLM for SCell activation to 71GHz | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215863 | Draft CR on introduction of intra-frequency and inter-frequency measurement test cases without CCA for FR2-2 | vivo |
R4-2217198 | Draft CR on introduction of intra-frequency and inter-frequency measurement test cases without CCA for FR2-2 | vivo |
TDoc | Title | Source |
---|---|---|
R4-2216010 | Discussion on general issues for FR2-2 demodulation requirements | Huawei,HiSilicon |
R4-2216178 | On Demod Requirements for FR2-2 - General | Qualcomm Incorporated |
R4-2216179 | Draft CR to 38.101-4 for FR2-2 Demod - General section | Qualcomm Incorporated |
R4-2217393 | Discussion on general issues for FR2-2 demodulation requirements | Huawei,HiSilicon |
R4-2217394 | Draft CR to 38.101-4 for FR2-2 Demod - General section | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215585 | Draft CR for Introducing Propagation channel models for requirements in FR2-2 | Apple |
R4-2215586 | Draft CR for Introducing FRCs for requirements in FR2-2 | Apple |
R4-2216011 | BigCR: Introduction of FR2-2 UE demodulation and CSI requirements in 38.101-4 | Huawei,HiSilicon |
R4-2217392 | Simulation results summary for UE demod in FR2-2 | Ericsson |
R4-2217516 | Big draftCR to 38.104: demodulation requirements introduction for FR2-2 | Nokia, Nokia Shanghai Bell, Intel |
R4-2217517 | Big draftCR to 38.141-2: demodulation requirements introduction for FR2-2 | Nokia, Nokia Shanghai Bell, Intel |
TDoc | Title | Source |
---|---|---|
R4-2215532 | On PDSCH Requirements for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2215533 | PDSCH simulation results for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2215587 | On PDSCH demod requirements for 52.6 - 71 GHz | Apple |
R4-2215910 | The remaining issues of the PDSCH requirements in 52.6 71 GHz band | Ericsson |
R4-2215911 | Simulation results for PDSCH demodulation in 52.6 71 GHz band | Ericsson |
R4-2215918 | draft CR on PDSCH requirements for 52.6 - 71 GHz band | Ericsson |
R4-2216012 | Discussions on FR2-2 PDSCH demodulation requirements | Huawei,HiSilicon |
R4-2216013 | Simulation results on FR2-2 PDSCH demodulation requirements | Huawei,HiSilicon |
R4-2216014 | Draft CR: Introduction of FR1+FR2-2 CA PDSCH performance requirements in TS 38.101-4 | Huawei,HiSilicon |
R4-2216180 | Simulation Results for FR2-2 UE Demodulation PDSCH | Qualcomm Incorporated |
R4-2217395 | draft CR on PDSCH requirements for 52.6 - 71 GHz band | Ericsson |
R4-2217396 | Discussions on FR2-2 PDSCH demodulation requirements | Huawei,HiSilicon |
R4-2217397 | Simulation results on FR2-2 PDSCH demodulation requirements | Huawei,HiSilicon |
R4-2217398 | Draft CR: Introduction of FR1+FR2-2 CA PDSCH performance requirements in TS 38.101-4 | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215534 | On PDCCH and PBCH Requirements for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2215535 | PDCCH and PBCH simulation results for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2215536 | Nokia_DraftCR_38101-4_PDCCH | Nokia, Nokia Shanghai Bell |
R4-2215588 | On PDCCH and PBCH demod requirements for 52.6 - 71 GHz | Apple |
R4-2215912 | The remaining issues for PDCCH and PBCH requirements in FR2-2 | Ericsson |
R4-2215913 | Simulation results for PDCCH and PBCH demodulation in FR2-2 | Ericsson |
R4-2216015 | Simulation results on FR2-2 PDCCHPBCH requirements | Huawei,HiSilicon |
R4-2216181 | Simulation Results for FR2-2 UE Demodulation PDCCH/PBCH | Qualcomm Incorporated |
R4-2216182 | Draft CR to 38.101-4 for FR2-2 Demod - PBCH Requirements | Qualcomm Incorporated |
R4-2217399 | Nokia_DraftCR_38101-4_PDCCH | Nokia, Nokia Shanghai Bell |
R4-2217400 | Simulation results on FR2-2 PDCCHPBCH requirements | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215914 | SDR requirements in 52.6 71 GHz band | Ericsson |
R4-2215915 | Simulation results for SDR requirements in 52.6 71 GHz band | Ericsson |
R4-2215919 | SDR requirements for 52.6 GHz 71 GHz band. | Ericsson |
R4-2216016 | Discussions on FR2-2 SDR requirements | Huawei,HiSilicon |
R4-2216017 | Simulation results FR2-2 SDR requirements | Huawei,HiSilicon |
R4-2217401 | Discussions on FR2-2 SDR requirements | Huawei,HiSilicon |
R4-2217402 | Simulation results FR2-2 SDR requirements | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215537 | On CSI Reporting Requirements for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2215589 | On CQI reporting requirements for 52.6 - 71 GHz | Apple |
R4-2215590 | Draft CR for Introducing CSI reporting requirements for 52.6 - 71 GHz | Apple |
R4-2215916 | CSI reporting requirements in 52.6 71 GHz band | Ericsson |
R4-2215917 | Simulation results for CSI reporting requirements in FR2-2 | Ericsson |
R4-2216018 | Discussion on remaining issues on FR2-2 CQI requirements | Huawei,HiSilicon |
R4-2216019 | Simulation results on FR2-2 CQI requirements | Huawei,HiSilicon |
R4-2216183 | Discussion on FR2-2 CQI Requirements | Qualcomm Incorporated |
R4-2216707 | CSI Simulation Results for ext71GHz | Nokia, Nokia Shanghai Bell |
R4-2217403 | Draft CR for Introducing CSI reporting requirements for 52.6 - 71 GHz | Apple |
R4-2217404 | Discussion on remaining issues on FR2-2 CQI requirements | Huawei,HiSilicon |
R4-2217405 | Simulation results on FR2-2 CQI requirements | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215690 | Discussion on general and PUSCH issue for FR2-2 BS demodualtion | Ericsson |
R4-2215691 | Simulation results for FR2-2 PUSCH | Ericsson |
R4-2215694 | draftCR for TS38.104 introduce FRC tables for FR2-2 PUSCH requirements | Ericsson |
R4-2215695 | draftCR for TS38.141-2 introduce FRC tables for FR2-2 PUSCH requirements | Ericsson |
R4-2216020 | Draft CR: Introduction of FR2-2 PUSCH radiated conformance testing requirements in TS 38.141-2 | Huawei,HiSilicon |
R4-2216021 | Discussions on FR2-2 PUSCH demodulation requirements | Huawei,HiSilicon |
R4-2216022 | Simulation results on FR2-2 PUSCH demodulation requirements | Huawei,HiSilicon |
R4-2216570 | Discussion on PUSCH demodulation requirements for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216571 | PUSCH simulation results for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216691 | View on BS demodulation requirement for NR extended to 71GHz | Samsung |
R4-2216694 | Initial simulation results on PUSCH demodulation requirement for Rel-17 71GHz | Samsung |
R4-2217375 | Simulation results collection for Fr2-2 BS demod | Huawei |
R4-2217376 | Draft CR 38.104: PUSCH requirements for FR2-2 | Nokia, Nokia Shanghai Bell, Intel |
R4-2217378 | draftCR for TS38.104 introduce FRC tables for FR2-2 PUSCH requirements | Ericsson |
R4-2217379 | draftCR for TS38.141-2 introduce FRC tables for FR2-2 PUSCH requirements | Ericsson |
R4-2217380 | Draft CR: Introduction of FR2-2 PUSCH radiated conformance testing requirements in TS 38.141-2 | Huawei,HiSilicon |
R4-2217381 | Discussions on FR2-2 PUSCH demodulation requirements | Huawei,HiSilicon |
R4-2217382 | Simulation results on FR2-2 PUSCH demodulation requirements | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215692 | Simulation results for FR2-2 PUCCH | Ericsson |
R4-2216023 | Discussions and simulation results on FR2-2 PUCCH demodulation requirements | Huawei,HiSilicon |
R4-2216024 | Draft CR Introduction of FR2-2 PUCCH performance requirements in TS 38.104 | Huawei,HiSilicon |
R4-2216572 | Discussion on PUCCH demodulation requirements for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216573 | PUCCH simulation results for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216695 | Initial simulation results on PUCCH demodulation requirement for Rel-17 71GHz | Samsung |
R4-2217377 | Draft CR 38.141-2: PUCCH requirements for FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217383 | Discussions and simulation results on FR2-2 PUCCH demodulation requirements | Huawei,HiSilicon |
R4-2217384 | Draft CR Introduction of FR2-2 PUCCH performance requirements in TS 38.104 | Huawei,HiSilicon |
R4-2217385 | Discussions on FR2-2 PRACH demodulation requirements | Huawei,HiSilicon |
R4-2217386 | Simulation results on FR2-2 PRACH demodulation requirements | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215693 | Simulation results for FR2-2 PRACH | Ericsson |
R4-2216025 | Discussions on FR2-2 PRACH demodulation requirements | Huawei,HiSilicon |
R4-2216026 | Simulation results on FR2-2 PRACH demodulation requirements | Huawei,HiSilicon |
R4-2216574 | Discussion on PRACH demodulation requirements for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216575 | PRACH simulation results for demodulation requirements for the extension to 71 GHz | Nokia, Nokia Shanghai Bell |
R4-2216576 | Draft CR 38.104: PRACH requirements for FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216577 | Draft CR 38.141-2: PRACH requirements for FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2216692 | Draft CR on annex for PRACH requirement for TS 38.104 | Samsung |
R4-2216693 | Draft CR on annex for PRACH requirement for TS 38.141-2 | Samsung |
R4-2216696 | Initial simulation results on PRACH demodulation requirement for Rel-17 71GHz | Samsung |
R4-2217387 | Draft CR 38.104: PRACH requirements for FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217388 | Draft CR 38.141-2: PRACH requirements for FR2-2 | Nokia, Nokia Shanghai Bell |
R4-2217389 | Draft CR on annex for PRACH requirement for TS 38.104 | Samsung |
R4-2217390 | Draft CR on annex for PRACH requirement for TS 38.141-2 | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2216890 | Email discussion summary for [104-bis-e][306] NR_exto71GHz_BSRF | Moderator (Huawei) |
R4-2216903 | Email discussion summary for [104-bis-e][319] NR_exto71GHz_Demod_Part1 | Moderator (Nokia) |
R4-2216904 | Email discussion summary for 1[04-bis-e][320] NR_exto71GHz_Demod_Part2 | Moderator (Qualcomm) |
R4-2216914 | Email discussion summary for [104-bis-e][203] NR_ext_to_71GHz_RRM_1 | Moderator (Huawei) |
R4-2216915 | Email discussion summary for [104-bis-e][204] NR_ext_to_71GHz_RRM_2 | Moderator (Qualcomm) |
R4-2216940 | Email discussion summary for [104-bis-e][102] NR_ext_to_71GHz | Moderator (Qualcomm) |
R4-2216983 | Email discussion summary for [104-bis-e][102] NR_ext_to_71GHz | Moderator (Qualcomm) |
R4-2217133 | Email discussion summary for [104-bis-e][204] NR_ext_to_71GHz_RRM_2 | Moderator (Qualcomm) |
R4-2217136 | Email discussion summary for [104-bis-e][203] NR_ext_to_71GHz_RRM_1 | Moderator (Huawei) |
R4-2217137 | Email discussion summary for [104-bis-e][204] NR_ext_to_71GHz_RRM_2 | Moderator (Qualcomm) |
R4-2217362 | WF on the list of MU contributors for FR2-2 | Nokia |
R4-2217363 | WF on the test equipment MU | Keysight |
R4-2217364 | WF on the OTA chambers applicability for FR2-2 | Ericsson |
R4-2217365 | WF for work-split | Huawei |
R4-2217371 | WF on general aspects for FR2-2 demodulation requirements | Huawei |
R4-2217372 | WF on PUSCH demodulation requirements for FR2-2 | Nokia |
R4-2217373 | WF on PUCCH demodulation requirements for FR2-2 | Ericsson |
R4-2217374 | WF on PRACH demodulation requirements for FR2-2 | Samsung |
R4-2217391 | WF for FR2-2 UE demodulation and CSI requirements | Qualcomm |
R4-2217482 | Email discussion summary for [104-bis-e][306] NR_exto71GHz_BSRF | Moderator (Huawei) |
R4-2217483 | Email discussion summary for [104-bis-e][319] NR_exto71GHz_Demod_Part1 | Moderator (Nokia) |
R4-2217484 | Email discussion summary for [104-bis-e][320] NR_exto71GHz_Demod_Part2 | Moderator (Qualcomm) |
R4-2217762 | Email discussion summary for [104-bis-e][102] NR_ext_to_71GHz | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2216590 | CR on clarification for DMRS bundling RF requirements for SUL in TS 38.101-1 | Huawei, HiSilicon |
R4-2217033 | CR on clarification for DMRS bundling RF requirements for SUL in TS 38.101-1 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215564 | Pcmax time aspects for DMRS bundling | Qualcomm Incorporated |
R4-2215565 | DMRS bundling CA aspects | Qualcomm Incorporated |
R4-2215566 | CR for FR1 uplink CA | Qualcomm Incorporated |
R4-2215567 | CR for FR2 uplink CA | Qualcomm Incorporated |
R4-2215568 | CR for removing configuration limitation in 38.101-3 | Qualcomm Incorporated |
R4-2215795 | Updated summary of RF agreements for NR coverage enhancements WI | China Telecom |
R4-2215796 | DMRS bundling for UL operation over multiple carriers | China Telecom |
R4-2216791 | CR to 38.101-2 to clarify P-MPR behavior when DMRS bundling is configured | Apple, MediaTek |
R4-2216798 | CR to clarify UE requirements for DMRS bundling in case of P-MPR change | MediaTek, Apple |
R4-2217031 | CR for FR1 uplink CA | Qualcomm Incorporated |
R4-2217032 | CR for FR2 uplink CA | Qualcomm Incorporated |
R4-2217091 | CR to 38.101-2 to clarify P-MPR behavior when DMRS bundling is configured | Apple, MediaTek |
R4-2217092 | CR to clarify UE requirements for DMRS bundling in case of P-MPR change | MediaTek, Apple |
R4-2217808 | CR for FR1 uplink CA | Qualcomm Incorporated |
R4-2217809 | CR to 38.101-2 to clarify P-MPR behavior when DMRS bundling is configured | Apple, MediaTek |
R4-2217811 | CR to clarify UE requirements for DMRS bundling in case of P-MPR change | MediaTek, Apple |
TDoc | Title | Source |
---|---|---|
R4-2215643 | Simulation results collection for coverage enhancement for PUCCH | Nokia, Nokia Shanghai Bell |
R4-2217406 | Big draftCR for coverage enhancement performance requirements for TS38.104 | China Telecom |
R4-2217407 | Big draftCR for coverage enhancement performance requirements for TS38.141-1 | Ericsson |
R4-2217408 | Big draftCR for coverage enhancement performance requirements for TS38.141-2 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2215325 | Summary of simulation results for PUSCH coverage enhancements | China Telecom |
R4-2215326 | On BS PUSCH demodulation requirements for NR coverage enhancements | China Telecom |
R4-2215327 | Draft CR on PUSCH with DMRS bundling BS performance test for FR1 | China Telecom |
R4-2215328 | Draft CR on PUSCH with DMRS bundling BS performance test for FR2 | China Telecom |
R4-2215638 | PUSCH demodulation performance of Rel-17 NR coverage enhancements | Nokia, Nokia Shanghai Bell |
R4-2215639 | PUSCH demodulation performance of Rel-17 NR coverage enhancements: simulation results | Nokia, Nokia Shanghai Bell |
R4-2215640 | draftCR for 38.104: FRC for TBoMS and PUSCH JCE | Nokia, Nokia Shanghai Bell |
R4-2215685 | draftCR for TS38.104 PUSCH with JCE for FR1 and FR2 | Ericsson |
R4-2215688 | Simulation results for PUSCH with TBoMS and JCE | Ericsson |
R4-2215995 | Discussion on BS coverage enhancement demod PUSCH | Huawei,HiSilicon |
R4-2215996 | Simulation results on BS coverage enhancement demod PUSCH | Huawei,HiSilicon |
R4-2215997 | Draft CR on requirements for PUSCH TBoMS (TS38.104, Rel-17) | Huawei,HiSilicon |
R4-2215998 | Draft CR on requirements for PUSCH TBoMS (TS38.141-1, Rel-17) | Huawei,HiSilicon |
R4-2215999 | Draft CR on requirements for PUSCH TBoMS (TS38.141-2, Rel-17) | Huawei,HiSilicon |
R4-2216686 | Simulation results for PUSCH demodulation requirement for Rel-17 coverage enhancement | Samsung |
R4-2216689 | Draft CR on FRC for TBoMS and PUSCH JCE for TS 38.141-1 | Samsung |
R4-2216690 | Draft CR on FRC for TBoMS and PUSCH JCE for TS 38.141-2 | Samsung |
R4-2217409 | Draft CR on PUSCH with DMRS bundling BS performance test for FR1 | China Telecom |
R4-2217410 | Draft CR on PUSCH with DMRS bundling BS performance test for FR2 | China Telecom |
R4-2217411 | draftCR for TS38.104 PUSCH with JCE for FR1 and FR2 | Ericsson |
R4-2217412 | Draft CR on requirements for PUSCH TBoMS (TS38.104, Rel-17) | Huawei,HiSilicon |
R4-2217413 | Draft CR on requirements for PUSCH TBoMS (TS38.141-1, Rel-17) | Huawei,HiSilicon |
R4-2217414 | Draft CR on requirements for PUSCH TBoMS (TS38.141-2, Rel-17) | Huawei,HiSilicon |
R4-2217415 | Simulation results for PUSCH demodulation requirement for Rel-17 coverage enhancement | Samsung |
R4-2217416 | Draft CR on FRC for TBoMS and PUSCH JCE for TS 38.141-1 | Samsung |
R4-2217417 | Draft CR on FRC for TBoMS and PUSCH JCE for TS 38.141-2 | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215641 | draftCR for 38.141-1: Perf requirements for PUCCH JCE | Nokia, Nokia Shanghai Bell |
R4-2215642 | draftCR for 38.141-2: Perf requirements for PUCCH JCE | Nokia, Nokia Shanghai Bell |
R4-2215686 | draftCR for TS38.141-1 manufacture declaration, applicability rule, MU and TT | Ericsson |
R4-2215687 | draftCR for TS38.141-2 manufacture declaration, applicability rule, MU and TT | Ericsson |
R4-2215689 | Simulation results for PUCCH with JCE | Ericsson |
R4-2216000 | Discussion on BS coverage enhancement demod PUCCH | Huawei,HiSilicon |
R4-2216001 | Simulation results on BS coverage enhancement demod PUCCH | Huawei,HiSilicon |
R4-2216507 | PUCCH demodulation performance of Rel-17 NR coverage enhancements: simulation results | Nokia, Nokia Shanghai Bell |
R4-2216687 | Simulation results for PUCCH demodulation requirement for Rel-17 coverage enhancement | Samsung |
R4-2216688 | Draft CR on PUCCH JCE requirements for TS 38.104 | Samsung |
R4-2217418 | draftCR for 38.141-1: Perf requirements for PUCCH JCE | Nokia, Nokia Shanghai Bell |
R4-2217419 | draftCR for 38.141-2: Perf requirements for PUCCH JCE | Nokia, Nokia Shanghai Bell |
R4-2217420 | Draft CR on PUCCH JCE requirements for TS 38.104 | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2216905 | Email discussion summary for [104-bis-e][321] NR_cov_enh_Demod | Moderator (China Telecom) |
R4-2216941 | Email discussion summary for [104-bis-e][103] NR_cov_enh_maintenance | Moderator (China Telecom) |
R4-2216984 | Email discussion summary for [104-bis-e][103] NR_cov_enh_maintenance | Moderator (China Telecom) |
R4-2217093 | WF on DMRS bundling | China Telecom |
R4-2217485 | Email discussion summary for [104-bis-e][321] NR_cov_enh_Demod | Moderator (China Telecom) |
R4-2217763 | Email discussion summary for [104-bis-e][103] NR_cov_enh_maintenance | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R4-2215353 | Discussion on remaining issue about Unified TCI state in FeMIMO | Intel Corporation |
R4-2215591 | On remaining issues for unified TCI requirements | Apple |
R4-2215592 | CR for unified TCI | Apple |
R4-2215743 | Discussion on remaining issues of FeMIMO RRM core requirements for unified TCI state | Samsung |
R4-2215764 | Discussion on unified TCI for DL and UL | MediaTek Inc. |
R4-2216280 | Discussion on RRM remaining issues for R17 unified TCI framework | Huawei, HiSilicon |
R4-2216281 | CR on maintaining TCI state switching requirements for R17 unified TCI | Huawei, HiSilicon |
R4-2216360 | Discussion on remaining issues in unified TCI in R17 feMIMO | vivo |
R4-2216361 | CR on unified TCI in R17 feMIMO | vivo |
R4-2216486 | Discussion on Unified TCI for DL and UL | ZTE Corporation |
R4-2216596 | Remaining issues for UL TCI state switch delay | Nokia, Nokia Shanghai Bell |
R4-2216817 | Discussion on remaining issues on Unified TCI for DL and UL | Ericsson |
R4-2216818 | CR on maintenance of unified TCI state switching requirements | Ericsson |
R4-2217203 | WF on FeMIMO Unified TCI state | Intel |
R4-2217204 | WF on FeMIMO RRM requirements for inter-cell beam management | Huawei |
R4-2217205 | CR for unified TCI | Apple, Vivo |
R4-2217591 | Big CR for NR feMIMO RRM performance requirements | MCC, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215354 | Discussion on remaining issue about inter-cell beam management in FeMIMO | Intel Corporation |
R4-2215593 | On remaining issues for inter-cell beam management | Apple |
R4-2215594 | CR for inter-cell beam management | Apple |
R4-2215744 | Discussion on remaining issues of FeMIMO RRM core requirements for inter-cell beam management | Samsung |
R4-2215765 | Discussion on inter cell beam management | MediaTek Inc. |
R4-2215767 | CR on applicability of R17 inter cell beam management for FR2-2 | MediaTek Inc. |
R4-2216282 | Discussion on RRM remaining issues for R17 inter-cell beam managements | Huawei, HiSilicon |
R4-2216283 | CR on maintaining L1-RSRP measurement requirements for R17 inter-cell BM | Huawei, HiSilicon |
R4-2216362 | Discussion on remaining issues in inter-cell beam managements in R17 feMIMO | vivo |
R4-2216363 | CR on inter-cell beam managements in R17 feMIMO | vivo |
R4-2216485 | Discussion on remaining RRM requirements for inter-cell beam management | ZTE Corporation |
R4-2216819 | Discussion on remaining issues of Inter-cell beam management | Ericsson |
R4-2216820 | Maintenance CR on inter-cell BM | Ericsson |
R4-2217206 | CR for inter-cell beam management | Apple |
R4-2217207 | Maintenance CR on inter-cell BM | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215747 | Correction on requirements for TRP specific link recovery procedures | Samsung |
R4-2216487 | CR on SFN based RLM and LRP | ZTE Corporation |
R4-2217583 | CR on SFN based RLM and LRP | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216364 | Discussion on R17 feMIMO test case configurations | vivo |
R4-2216821 | Discussion on test cases for TRP specific BFD and LR | Ericsson |
R4-2217208 | WF on FeMIMO RRM Performance Requirement and Test Case | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215745 | Discussion on remaining issues of test cases for unified TCI state | Samsung |
R4-2215766 | Draft CR on TC for joint unified TCI state switching in FR2 NR SA | MediaTek Inc. |
R4-2216365 | Draft CR on test case for DL TCI state switching for Cell with different PCI in FR2 NR-SA | vivo |
R4-2216822 | CR on maintenance of UL TCI state switching of FR2 PCell | Ericsson |
R4-2217209 | Draft CR on test case for DL TCI state switching for Cell with different PCI in FR2 NR-SA | vivo |
R4-2217210 | Draft CR on TC for joint unified TCI state switching in FR2 NR SA | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R4-2215974 | Draft CR on TC of L1-RSRP measurement on cells with different PCI | Samsung |
R4-2216366 | Draft CR on test case for L1-RSRP measurement procedure in FR1 NR-SA | vivo |
R4-2217211 | Draft CR on TC of L1-RSRP measurement on cells with different PCI | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215358 | Discussion on TRP specific Beam Failure Detection and Link Recovery Test case | Intel Corporation |
R4-2215746 | Discussion on remaining issues of test cases for TRP specific BFD and LR | Samsung |
R4-2216284 | DraftCR on maintaining TRP specific BFR test cases | Huawei, HiSilicon |
R4-2216823 | maintenance CR on test cases for TRP specific BFD and LR | Ericsson |
R4-2217212 | maintenance CR on test cases for TRP specific BFD and LR | Ericsson |
R4-2217213 | DraftCR on maintaining TRP specific BFR test cases | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215728 | Simulation results summary for FeMIMO demodulation and CSI requirement | Samsung |
R4-2217433 | Big draft CR on UE demodulation and CSI requirement for FeMIMO | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215538 | Draft CR for 38_101-4 FeMIMO Applicability of Requirements | Nokia, Nokia Shanghai Bell |
R4-2217434 | Draft CR for 38_101-4 FeMIMO Applicability of Requirements | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215595 | On demod requirements for HST Scheme-A | Apple |
R4-2215596 | Draft CR on PDSCH requirement for HST-SFN scheme A | Apple |
R4-2215713 | Updated simulation results for HST-SFN | CMCC |
R4-2215726 | Discussion and simulation results on demodulation requirement for Enhancement on HST-SFN scenario | Samsung |
R4-2215882 | Views on HST-SFN Tests | Qualcomm Incorporated |
R4-2215886 | Simulation Results on HST-SFN Scheme A | Qualcomm Incorporated |
R4-2215887 | Simulation Results on HST-SFN Scheme B | Qualcomm Incorporated |
R4-2215938 | Discussion on demodulation requirement for Enhancement on HST-SFN deployment | MediaTek inc. |
R4-2216002 | Discussion on UE FeMIMO demod HST-SFN | Huawei,HiSilicon |
R4-2216003 | Simulation results on UE FeMIMO demod HST-SFN | Huawei,HiSilicon |
R4-2216004 | Draft CR on PDSCH requirement for HST-SFN scheme B | Huawei,HiSilicon |
R4-2216387 | Discussion on the PDSCH requirement for HST-SFN | Ericsson |
R4-2216388 | Simulation restuls for PDSCH requirement for HST-SFN | Ericsson |
R4-2217284 | Simulation Results on HST-SFN Scheme A | Qualcomm |
R4-2217285 | Simulation Results on HST-SFN Scheme B | Qualcomm |
R4-2217435 | Draft CR on PDSCH requirement for HST-SFN scheme A | Apple |
R4-2217436 | Draft CR on PDSCH requirement for HST-SFN scheme B | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215597 | On PDCCH demod requirements for multi-TRP | Apple |
R4-2215727 | Draft CR on PMI requirement for multi-TRP | Samsung |
R4-2215874 | Simulation Results on Multi-TRP PDCCH Tests | Qualcomm Incorporated |
R4-2215876 | Views on Performance Requirements for Multi-TRP PDCCH Tests | Qualcomm Incorporated |
R4-2215939 | Discussion on demodulation performance requirements definition for Rel17 multi-TRP | MediaTek inc. |
R4-2216005 | Discussion on UE FeMIMO demod mTRP | Huawei,HiSilicon |
R4-2216006 | Simulation results on UE FeMIMO demod mTRP | Huawei,HiSilicon |
R4-2216391 | Discussion on the requirement of PDCCH enhancement for Multi-TRP | Ericsson |
R4-2216392 | Simulation results for PDCCH enhancement for Multi-TRP | Ericsson |
R4-2216393 | draft CR to 38.101-4: PDCCH requirement with inter-slot repetition | Ericsson |
R4-2216790 | Draft CR on reference measurement channels for multi-TRP PDCCH performance | Qualcomm Incorporated |
R4-2217286 | Simulation Results on Multi-TRP PDCCH Tests | Qualcomm |
R4-2217437 | Draft CR on PMI requirement for multi-TRP | Samsung |
R4-2217438 | draft CR to 38.101-4: PDCCH requirement with inter-slot repetition | Ericsson |
R4-2217439 | Draft CR on reference measurement channels for multi-TRP PDCCH performance | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216007 | Discussion on UE FeMIMO CSI mTRP | Huawei,HiSilicon |
R4-2216008 | Simulation results on UE FeMIMO CSI mTRP | Huawei,HiSilicon |
R4-2216389 | Discussion on the gamma value for PMI reporting tests for Multi-TRP | Ericsson |
R4-2216390 | Simulation results for PMI reporting tests for Multi-TRP | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216906 | Email discussion summary for [104-bis-e][322] NR_FeMIMO_Demod | Moderator (Samsung) |
R4-2216916 | [Email discussion summary for 104-bis-e][205] NR_feMIMO_RRM_1 | Moderator (Intel) |
R4-2216917 | Email discussion summary for [104-bis-e][206] NR_feMIMO_RRM_2 | Moderator (Samsung) |
R4-2217138 | [Email discussion summary for 104-bis-e][205] NR_feMIMO_RRM_1 | Moderator (Intel) |
R4-2217139 | Email discussion summary for [104-bis-e][206] NR_feMIMO_RRM_2 | Moderator (Samsung) |
R4-2217440 | WF on UE demodulation and CSI requirement for FeMIMO | Samsung |
R4-2217486 | Email discussion summary for [104-bis-e][322] NR_FeMIMO_Demod | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R4-2215908 | Corrections on the definition of RedCap UE | ZTE Corporation |
R4-2215941 | definition on RedCap | ZTE Corporation |
R4-2217094 | Corrections on the definition of RedCap UE | ZTE Corporation |
R4-2217095 | definition on RedCap | ZTE Corporation |
R4-2217232 | WF on eDRX and RRM measurement relaxations requirements for Redcap UE | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2215962 | Discussion on LS on configuring margin for 1 Rx RedCap UEs | vivo |
TDoc | Title | Source |
---|---|---|
R4-2215364 | Discussion on the negative configuring margin for RSRP change threshold of 1 Rx RedCap UEs | Intel Corporation |
R4-2215365 | CR on 1Rx. margin for RedCap UEs configured with relaxed measurement criterion | Intel Corporation |
R4-2216215 | Discussion on remaining RRM issues for RedCap UEs | Nokia, Nokia Shanghai Bell |
R4-2216216 | CR 38.133: Corrections to SDT requirements for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216291 | Correction to idle measurement requirements for RedCap Ues | Huawei, HiSilicon |
R4-2216855 | On offset for cell specific RSRP thresholds for 1Rx Redcap UE | Ericsson |
R4-2216856 | Draft CR on offset for cell specific RSRP thresholds for 1Rx Redcap UE in 38.133 | Ericsson |
R4-2217195 | Test cases and work split for NR extension to 71 GHz RRM performance requirements | Qualcomm |
R4-2217214 | WF on RedCap RRM requirements | Ericsson |
R4-2217215 | Test case list for RedCap RRM performance part | Ericsson |
R4-2217216 | Correction to idle measurement requirements for RedCap Ues | Huawei, HiSilicon |
R4-2217217 | Draft CR on offset for cell specific RSRP thresholds for 1Rx Redcap UE in 38.133 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215471 | Discussion on remaining issues for mobility requirements for Redcap UE | Xiaomi |
R4-2216455 | Discussions on RedCap HO | Ericsson |
R4-2216456 | CR on RedCap HO | Ericsson |
R4-2216597 | Discussion on offsets to cell-specific thresholds for 1 Rx RedCap UEs | Nokia, Nokia Shanghai Bell |
R4-2216764 | Changes to RRC_IDLE mode requirements for RedCap for TS 38.133 | Ericsson |
R4-2216877 | Mobility requirements for RedCap UEs | Qualcomm Incorporated |
R4-2217218 | Changes to RRC_IDLE mode requirements for RedCap for TS 38.133 | Ericsson |
R4-2217219 | CR on RedCap HO | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216217 | Discussion on timing requirements for RedCap UEs | Nokia, Nokia Shanghai Bell |
R4-2216218 | CR 38.133 Correction to Tx timing requirements for active BWP without SSB for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216878 | Timing requirements for RedCap UEs | Qualcomm Incorporated |
R4-2216880 | Draft CR on timing requirements with measurement gaps for RedCap UEs | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215472 | Discussion on remaining issues for signalling characteristics for Redcap UE | Xiaomi |
R4-2216292 | Discussion on signaling characteristics for RedCap | Huawei, HiSilicon |
R4-2216598 | Discussion on UE power saving for RedCap | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215491 | On RedCap measurement procedure | CMCC |
R4-2215606 | On remaining issues of RRM requirement for RedCap UE | Apple |
R4-2215607 | CR for serving cell thresholds of s-MeasureConfig for RedCap | Apple |
R4-2216293 | Discussion on measurement requirements due to UE complexity reduction | Huawei, HiSilicon |
R4-2216294 | CR on offset margin for 1Rx RedCap UE | Huawei, HiSilicon |
R4-2216457 | Discussions on RedCap Measurement | Ericsson |
R4-2216458 | CR on RedCap CGI | Ericsson |
R4-2216599 | Remaining issues on measurement procedures for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216771 | Inter-RAT accuracy requirements for RedCap | Ericsson |
R4-2216881 | Draft CR on measurement procedures for RedCap UEs | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216295 | Discussion on Extended DRX enhancements for inactive RedCap UE | Huawei, HiSilicon |
R4-2216296 | Clarification on measurement for inactive mode RedCap UE | Huawei, HiSilicon |
R4-2216454 | CR on RedCap eDRX | Ericsson |
R4-2217233 | Clarification on measurement for inactive mode RedCap UE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215963 | on remaining issues on RRM relaxation for Redcap | vivo |
R4-2216219 | Discussion on RRM relaxations | Nokia, Nokia Shanghai Bell |
R4-2216297 | Correction on relaxed measurement for RedCap | Huawei, HiSilicon |
R4-2216763 | Discussions on RRM measurement relaxations | Ericsson |
R4-2216883 | CR 38.133: RRM relaxations in case of failed S-criterion and SDT for RedCap | Nokia, Nokia Shanghai Bell |
R4-2217234 | Correction on relaxed measurement for RedCap | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215470 | Discussion on NCD-SSB time offset impact for RedCap UE | Xiaomi |
R4-2215598 | CR on scheduling restrictions for L3 measurements in FR1 for RedCap | Apple |
R4-2216220 | Discussion on impact from NCD-SSB time offset | Nokia, Nokia Shanghai Bell |
R4-2217235 | CR on scheduling restrictions for L3 measurements in FR1 for RedCap | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215492 | NCD-SSB configurations and test cases | CMCC |
R4-2216307 | Test case on E-UTRA NR inter-RAT measurement performance for Redcap | Huawei, HiSilicon |
R4-2216452 | Discussions on RedCap NCD-SSB test design | Ericsson |
R4-2216453 | draftCR on RedCap NCD-SSB RMC | Ericsson |
R4-2216600 | Discussion on NCD-SSB test cases for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216765 | Updated test case list for RedCap RRM performance part | Ericsson |
R4-2217220 | draftCR on RedCap NCD-SSB RMC | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216298 | Discussion on handover test for RedCap UE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216601 | draft CR on correction to IDLE mode test cases for RedCap in FR1 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215473 | CR on 4-step random access test in FR1 for RedCap UE | Xiaomi |
R4-2216299 | Test case for handover for FR1 RedCap UE | Huawei, HiSilicon |
R4-2216602 | draft CR on correction to CONNECTED mode test cases for RedCap in FR1 | Nokia, Nokia Shanghai Bell |
R4-2216749 | DraftCR on Intra-frequency handover from FR1 to FR1 unknown target cell for 2 and 1 Rx UE | MediaTek inc. |
R4-2217229 | Test case for handover for FR1 RedCap UE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215420 | CR on timing test for RedCap for FR1 | CATT |
R4-2216603 | draft CR on corrections on timing test cases for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216748 | DraftCR on NR UE Transmit Timing Test for FR1 for 1 and 2 Rx UE | MediaTek inc. |
R4-2217221 | CR on timing test for RedCap for FR1 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215474 | CR on SSB-based RLM in-sync test in FR1 for RedCap UE | Xiaomi |
R4-2215493 | Draft CR on test case for FR1 active BWP swith and UE specific CBW change | CMCC |
R4-2216301 | RLM test cases for FR1 RedCap UE | Huawei, HiSilicon |
R4-2216604 | Draft CR introducing BFD and LR test cases for RedCap in FR1 | Nokia, Nokia Shanghai Bell |
R4-2216750 | DraftCR on Radio Link Monitoring Out-of-sync Test for FR1 PCell configured with SSB-based RLM RS in DRX mode for 1 and 2 Rx UE | MediaTek inc. |
R4-2217230 | Draft CR introducing BFD and LR test cases for RedCap in FR1 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215422 | Draft CR for RedCap UEs for intra-frequency measurement in FR1 | CATT |
R4-2215808 | CR on SA test with per-UE gaps under non-DRX with SSB index reading for intra-frequency measurement | OPPO |
R4-2215964 | draft CR for CSI-RS based L1-RSRP for Redcap | vivo |
R4-2216305 | Test case on SA inter-frequency measurement procedure in FR1 for Redcap | Huawei, HiSilicon |
R4-2216751 | DraftCR on SA event triggered reporting tests without gap under non-DRX for 1 Rx and 2 Rx UE | MediaTek inc. |
R4-2216756 | Draft CR on the test case for SA event triggered reporting tests for FR1 without SSB time index detection when DRX is not used | MediaTek inc. |
R4-2216772 | RRM test cases for FR1: Measurement procedure | Ericsson |
R4-2217222 | Draft CR for RedCap UEs for intra-frequency measurement in FR1 | CATT |
R4-2217223 | CR on SA test with per-UE gaps under non-DRX with SSB index reading for intra-frequency measurement | OPPO |
R4-2217224 | DraftCR on SA event triggered reporting tests without gap under non-DRX for 1 Rx and 2 Rx UE | MediaTek inc. |
R4-2217225 | Draft CR on the test case for SA event triggered reporting tests for FR1 without SSB time index detection when DRX is not used | MediaTek inc. |
R4-2217281 | Big CR for Performance part of RedCap - TS 38.133 | MCC, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216303 | Test case for intra-frequency SS-RSRQ measurement accuracy for FR1 RedCap UE | Huawei, HiSilicon |
R4-2216343 | Draft CR for introduction of the test cases for FR1 measurement accuracy on Redcap | Ericsson |
R4-2217226 | Test case for intra-frequency SS-RSRQ measurement accuracy for FR1 RedCap UE | Huawei, HiSilicon |
R4-2217586 | Test case for intra-frequency SS-RSRQ measurement accuracy for FR1 RedCap UE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215475 | CR on 4-step random access test in FR2 for RedCap UE | Xiaomi |
R4-2216300 | Test case for handover for FR2 RedCap UE | Huawei, HiSilicon |
R4-2217227 | Test case for handover for FR2 RedCap UE | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215421 | CR on timing test for RedCap for FR2 | CATT |
R4-2217228 | CR on timing test for RedCap for FR2 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215476 | CR on RLM in-sync and scheduling restriction in FR2 for RedCap UE | Xiaomi |
R4-2215494 | Draft CR on test case for FR2 active BWP swith, UE specific CBW change, active TCI state switch and uplink spatial relation switch delay | CMCC |
R4-2215965 | draft CR for CSI-RS-based BFD and LR for FR2 PCell | vivo |
R4-2216302 | RLM test cases for FR2 RedCap UE | Huawei, HiSilicon |
R4-2217231 | Draft CR on test case for FR2 active BWP swith, UE specific CBW change, active TCI state switch and uplink spatial relation switch delay | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215423 | Draft CR for RedCap UEs for intra-frequency measurement in FR2 | CATT |
R4-2215477 | CR on SA event triggered reporting test with per-UE gaps under DRX for RedCap UE in FR2 | Xiaomi |
R4-2215478 | CR on SSB and CSI-RS based L1-RSRP measurement for RedCap UE in FR2 | Xiaomi |
R4-2216306 | Test case on SA inter-frequency measurement procedure in FR2 for Redcap | Huawei, HiSilicon |
R4-2216752 | DraftCR on SSB based L1-RSRP measurement when DRX is not used for FR2 | MediaTek inc. |
R4-2216757 | Draft CR on the test case for SA event triggered reporting test without gap under DRX | MediaTek inc. |
R4-2216773 | RRM test cases for FR2: Measurement procedure | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216304 | Test case for intra-frequency SS-RSRQ measurement accuracy for FR2 RedCap UE | Huawei, HiSilicon |
R4-2216344 | Draft CR for introduction of the test cases for FR2 measurement accuracy on Redcap | Ericsson |
R4-2216753 | DraftCR on SSB based L1-RSRP measurement for beam reporting for FR2 | MediaTek inc. |
R4-2216754 | DraftCR on CSI-RS based L1-RSRP measurement for beam reporting for FR2 | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2215625 | Discussion on PDSCH/SDR requirements in RedCap | Apple |
R4-2215628 | Draft CR PDSCH demodulation requirements for RedCap | Apple |
R4-2216027 | Simulation results on RedCap PDSCH requirements | Huawei,HiSilicon |
R4-2216028 | Draft CR: Corrections of RedCap SDR requirements | Huawei,HiSilicon |
R4-2216175 | Simulation Results for Redcap UE Demodulation PDSCH | Qualcomm Incorporated |
R4-2216221 | Simulation results for Redcap PDSCH | Nokia, Nokia Shanghai Bell |
R4-2216230 | draft CR: Correction of RedCap UE demodulation requirements | Ericsson |
R4-2216232 | Open issues on UE demodulation requirements for RedCap | Ericsson |
R4-2216234 | Summary of simulation results for RedCap | Ericsson |
R4-2217430 | Big Draft CR to 38.101-4: Correction of RedCap UE demodulation and CSI reporting requirements | Ericsson |
R4-2217431 | Draft CR PDSCH demodulation requirements for RedCap | Apple |
R4-2217432 | Simulation results on RedCap PDSCH requirements | Huawei HiSilicon |
R4-2217441 | Draft CR: Corrections of RedCap SDR requirements | Huawei,HiSilicon |
R4-2217442 | draft CR: Correction of RedCap UE demodulation requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216176 | Simulation Results for Redcap UE Demodulation PDCCH/PBCH | Qualcomm Incorporated |
R4-2216222 | Simulation results for Redcap PDCCH | Nokia, Nokia Shanghai Bell |
R4-2216223 | Simulation results for Redcap PBCH | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215626 | Discussion on CQI requirements in RedCap | Apple |
R4-2216029 | Simulation results on RedCap CQI requirements | Huawei,HiSilicon |
R4-2216030 | Discussion on remaining issues on RedCap CQI requirements | Huawei,HiSilicon |
R4-2216177 | RedCap UE Demodulation Requirements CQI | Qualcomm Incorporated |
R4-2216224 | Simulation results for RedCap CQI reporting | Nokia, Nokia Shanghai Bell |
R4-2216225 | Draft CR 38.101-4 Finalization of channel quality reporting requirements under static condition for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216231 | draft CR: Correction of RedCap CSI reporting requirements | Ericsson |
R4-2216233 | Open issues on CSI reporting requirements for RedCap | Ericsson |
R4-2216429 | draftCR for RedCap UE Demodulation Requirements CQI for static channel | Qualcomm Incorporated |
R4-2216703 | Discussion on CQI requirements for RedCap | MediaTek inc. |
R4-2217443 | Simulation results on RedCap CQI requirements | Huawei HiSilicon |
R4-2217444 | Discussion on remaining issues on RedCap CQI requirements | Huawei HiSilicon |
R4-2217445 | Draft CR 38.101-4 Finalization of channel quality reporting requirements under static condition for RedCap | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215627 | Discussion on PMI/RI requirements in RedCap | Apple |
R4-2216031 | Simulation results on RedCap RI requirements | Huawei,HiSilicon |
R4-2216032 | Discussion on remaining issues on RedCap RI requirements | Huawei,HiSilicon |
R4-2216033 | Draft CR: Corrections of RedCap PMI requirements | Huawei,HiSilicon |
R4-2216226 | Draft CR 38.101-4 Finalization of Rank Indicator reporting requirements for RedCap | Nokia, Nokia Shanghai Bell |
R4-2216704 | Discussion on PMIRI requirements for RedCap | MediaTek inc. |
R4-2216706 | Draft CR to TS38.101-4, Corrections to ReCap PMI requirements | MediaTek inc. |
R4-2217446 | Simulation results on RedCap RI requirements | Huawei HiSilicon |
R4-2217447 | Discussion on remaining issues on RedCap RI requirements | Huawei HiSilicon |
R4-2217448 | Draft CR: Corrections of RedCap PMI requirements | Huawei,HiSilicon |
R4-2217449 | Draft CR to TS38.101-4, Corrections to ReCap PMI requirements | MediaTek inc. |
R4-2217505 | Draft CR 38.101-4 Finalization of Rank Indicator reporting requirements for RedCap | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2216907 | Email discussion summary for [104-bis-e][323] NR_RedCap_Demod | Moderator (Ericsson) |
R4-2216918 | Email discussion summary for [104-bis-e][207] NR_redcap_RRM_1 | Moderator (Ericsson) |
R4-2216919 | [Email discussion summary for 104-bis-e][208] NR_redcap_RRM_2 | Moderator (Vivo) |
R4-2216942 | Email discussion summary for [104-bis-e][104] NR_RedCap | Moderator (Ericsson) |
R4-2216985 | Email discussion summary for [104-bis-e][104] NR_RedCap | Moderator (Ericsson) |
R4-2217140 | Email discussion summary for [104-bis-e][207] NR_redcap_RRM_1 | Moderator (Ericsson) |
R4-2217141 | [Email discussion summary for 104-bis-e][208] NR_redcap_RRM_2 | Moderator (Vivo) |
R4-2217429 | WF on RedCap UE demodulation and CQI reporting requirements | Ericsson |
R4-2217487 | Email discussion summary for [104-bis-e][323] NR_RedCap_Demod | Moderator (Ericsson) |
R4-2217764 | Email discussion summary for [104-bis-e][104] NR_RedCap | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2215873 | Remaining issues for PDC enhancement | vivo |
R4-2216326 | On RRM requirements for PDC enhancements | Huawei, HiSilicon |
R4-2216327 | CR on requirements for UE Rx-Tx measurement for PDC | Huawei, HiSilicon |
R4-2216422 | Requirements for DRX case | Ericsson |
R4-2216423 | Requirements for DRX case | Ericsson |
R4-2216508 | Discussion on finalization of the requirements for NR_IIOT_URLLC | Nokia, Nokia Shanghai Bell |
R4-2216509 | CR on requirements for NR_IIOT_URLLC | Nokia, Nokia Shanghai Bell |
R4-2216672 | CR to TS 38.133 Correction to measurements core requirements for PDC | vivo |
R4-2216721 | Open issues in core requirements for RTT-based propagation delay compensation | Qualcomm Incorporated |
R4-2217236 | WF on NR_IIOT_URLLC_enh | Nokia |
R4-2217237 | Requirements for DRX case | Ericsson |
R4-2217238 | CR to TS 38.133 Correction to measurements core requirements for PDC | vivo |
TDoc | Title | Source |
---|---|---|
R4-2216510 | Measurement accuracy requirements for TUE-RX | Nokia, Nokia Shanghai Bell |
R4-2216511 | CR on UE Rx-Tx time difference measurement accuracy requirements for RTT-based PDC | Nokia, Nokia Shanghai Bell |
R4-2216512 | Draft CR to verify measurements for UE Rx-Tx time difference measurement with TRS for RTT based PDC in FR2 SA | Nokia, Nokia Shanghai Bell |
R4-2216792 | Draft CR to verify measurements for UE Rx-Tx time difference measurement with TRS for RTT based PDC in FR2 SA | Nokia Corporation |
R4-2217239 | Draft CR to verify measurements for UE Rx-Tx time difference measurement with TRS for RTT based PDC in FR2 SA | Nokia Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216328 | On measurement accuracy for PDC enhancements | Huawei, HiSilicon |
R4-2216329 | CR on PDC measurement accuracy requirements | Huawei, HiSilicon |
R4-2216722 | On performance requirements for RTT-based propagation delay compensation | Qualcomm Incorporated |
R4-2217240 | CR on PDC measurement accuracy requirements | Huawei, HiSilicon |
R4-2217592 | Big CR for NR IIoT and URLLC enh performance requirements | MCC, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2216330 | CR on TCs for PDC measurement | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215543 | Sub-slot based PUCCH repetition performance requirements | Nokia, Nokia Shanghai Bell |
R4-2215544 | Simulation Results on Sub-slot based PUCCH repetition | Nokia, Nokia Shanghai Bell |
R4-2215545 | Draft CR for TS 38.104 Demod performance requirement for sub-slot repetition PUCCH format 0 (Rel-17, CAT B) | Nokia, Nokia Shanghai Bell |
R4-2215696 | Simulation results for PUCCH sub-slot repetition | Ericsson |
R4-2216034 | Simulation results and discussion on remaining issues on Rel-17 URLLC PF0 subslot repetition requirments | Huawei,HiSilicon |
R4-2216035 | Draft CR: Introduction of manufacturer declarations for sub-slot repetition PF0 requirements | Huawei,HiSilicon |
R4-2216036 | Draft CR: Introduction of applicability rules for sub-slot repetition PF0 requirements | Huawei,HiSilicon |
R4-2216037 | Simulation summary of sub-slot repetition PF0 requirements | Huawei,HiSilicon |
R4-2216700 | Discussion and simulation results for Enhanced IIOT and URLLC support | Samsung |
R4-2216701 | Big CR on requirement for Enhanced IIOT and URLLC for TS 38.141-2 | Samsung |
R4-2216702 | Draft CR on OTA performance requirements for PUCCH for TS 38.141-2 | Samsung |
R4-2217283 | draftCR for TS38.141-1 general and PUCCH demodulation requirements for URLLC IIoT enhancement | Ericsson |
R4-2217422 | Big draft CR for TS 38.104 Demodulation requirements for Enhanced IIOT and URLLC support | Nokia, Nokia Shanghai Bell |
R4-2217423 | Big draft CR for TS 38.141-1 Demodulation requirements for Enhanced IIOT and URLLC support (Rel-17, CAT B) | Ericsson |
R4-2217424 | Simulation results and discussion on remaining issues on Rel-17 URLLC PF0 subslot repetition requirments | Huawei,HiSilicon |
R4-2217425 | Draft CR: Introduction of manufacturer declarations for sub-slot repetition PF0 requirements | Huawei,HiSilicon |
R4-2217426 | Draft CR: Introduction of applicability rules for sub-slot repetition PF0 requirements | Huawei,HiSilicon |
R4-2217427 | Draft CR on OTA performance requirements for PUCCH for TS 38.141-2 | Samsung |
R4-2217428 | draftCR for TS38.141-1 general and PUCCH demodulation requirements for URLLC IIoT enhancement | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216908 | Email discussion summary for [104-bis-e][324] NR_IIOT_URLLC_enh_Demod | Moderator (Nokia) |
R4-2216920 | Email discussion summary for [104-bis-e][209] NR_IIOT_URLLC_enh | Moderator (Nokia) |
R4-2217142 | Email discussion summary for [104-bis-e][209] NR_IIOT_URLLC_enh | Moderator (Nokia) |
R4-2217421 | WF on enhanced IIoT and URLLC support demodulation and CSI requirements | Nokia |
R4-2217488 | Email discussion summary for [104-bis-e][324] NR_IIOT_URLLC_enh_Demod | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R4-2215877 | CR on subsequent CG-SDT transmission for NR SDT | ZTE Wistron Telecom AB |
R4-2215878 | Discussion on RRM core requirements for NR SDT | ZTE Wistron Telecom AB |
R4-2216331 | CR on SDT RRM requirements | Huawei, HiSilicon |
R4-2216740 | CR on requirements for CG-SDT in unlicensed band | Qualcomm Incorporated |
R4-2216741 | Description of the CR for CG-SDT in unlicensed band. | Qualcomm Incorporated |
R4-2217241 | WF on RRM requirements for NR SDT | ZTE Corporation |
R4-2217242 | LS on the feasibility of testing UE initiated SDT data transmission in RRC_INACTIVE | Nokia |
R4-2217243 | CR on SDT RRM requirements | Huawei, HiSilicon |
R4-2217588 | WF on RRM requirements for NR SDT | ZTE Corporation |
R4-2217593 | Big CR for NR SDT performance requirements | MCC, ZTE |
TDoc | Title | Source |
---|---|---|
R4-2215879 | Discussion on RRM performance requirements for NR SDT | ZTE Wistron Telecom AB |
R4-2216332 | Discussion on RRM test cases for SDT | Huawei, HiSilicon |
R4-2216333 | CR to introduce SDT RRC TCs | Huawei, HiSilicon |
R4-2216569 | Discussion on performance requirements for SDT | Nokia, Nokia Shanghai Bell |
R4-2216742 | Discussion on RRM performance requirement for CG-SDT | Qualcomm Incorporated |
R4-2216743 | DraftCR for test case for CG-SDT | Qualcomm Incorporated |
R4-2216770 | Discussions on RRM performance requirements for SDT | Ericsson |
R4-2217244 | CR to introduce SDT RRC TCs | Huawei, HiSilicon |
R4-2217245 | DraftCR for test case for CG-SDT | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216921 | Email discussion summary for [104-bis-e][210] NR_SmallData_INACTIVE | Moderator (ZTE) |
R4-2217143 | Email discussion summary for [104-bis-e][210] NR_SmallData_INACTIVE | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2215343 | On Triple Beat Detection Equation for Intra-band Contiguous 2 CCs | Murata Manufacturing Co Ltd. |
R4-2215347 | DC_3C_n28A Triple Beat MSD | Murata Manufacturing Co Ltd. |
R4-2215516 | MSD for CA_n7A-n26A | Skyworks Solutions Inc. |
R4-2215521 | MSD for DC_(n)3AA_n8A | Skyworks Solutions Inc. |
R4-2215523 | MSD for DC_3A_(n)7AA | Skyworks Solutions Inc. |
R4-2215525 | Triple beat MSD for DC_3A_n41C | Skyworks Solutions Inc. |
R4-2215528 | Triple beat MSD for DC_3C_n28A | Skyworks Solutions Inc. |
R4-2215738 | Discussion on the general text for the justification of Rel.18 higher power NR CA/DC, NR SUL, and LTE/NR DC basket WIDs | Samsung, CHTTL |
R4-2215784 | On Triple Beat Detection Equations for Intra-Band Non-Contiguous 2 CCs | Murata Manufacturing Co Ltd. |
R4-2216054 | TP and discussion on triple beat MSD of UL DC_3C_n28A | Huawei, HiSilicon |
R4-2216086 | TP for TR 37 718-21-11 to update DC_3-(n)7 | Ericsson, Skyworks, MediaTek, Telstra |
R4-2216087 | TP for TR 38.718-02-01 to update CA_n3-n26 | Ericsson, Skyworks, Telstra |
R4-2216088 | TP for TR 38.718-02-01 to update CA_n7-n26 | Ericsson, Skyworks, Telstra |
R4-2217099 | TP and discussion on triple beat MSD of UL DC_3C_n28A | Huawei, HiSilicon |
R4-2217100 | TP for TR 38.718-02-01 to update CA_n7-n26 | Ericsson, Skyworks, Telstra |
R4-2217101 | TP for TR 37 718-21-11 to update DC_3-(n)7 | Ericsson, Skyworks, MediaTek, Telstra |
R4-2217804 | WF on MSD due to IMDs of intra-band ULCA and handling of spectrum restrictions | Skyworks Solutions Inc. |
R4-2217805 | draftCR to R18 38.101-1 to capture MSD related to IMD of intra-band ULCA | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216943 | Email discussion summary for [104-bis-e][105] NR_Baskets_Part_1 | Moderator (Skyworks) |
R4-2216986 | Email discussion summary for [104-bis-e][105] NR_Baskets_Part_1 | Moderator (Skyworks) |
R4-2217096 | Way forward on potential triple beat issue for 2 band and 3 band combinations | Murata, Skyworks, ZTE |
R4-2217097 | Way forward on MSD to Scell for intra-band contiguous with IMD overlap | Skyworks, Murata |
R4-2217765 | Email discussion summary for [104-bis-e][105] NR_Baskets_Part_1 | Moderator (Skyworks) |
TDoc | Title | Source |
---|---|---|
R4-2216944 | Email discussion summary for [104-bis-e][106] NR_Baskets_Part_2 | Moderator (Nokia) |
R4-2216945 | Email discussion summary for [104-bis-e][107] NR_Baskets_Part_3 | Moderator (Ericsson) |
R4-2216946 | Email discussion summary for [104-bis-e][108] NR_Baskets_Part_4 | Moderator (Nokia) |
R4-2216948 | Email discussion summary for [104-bis-e][110] NR_LTE_V2X_PC5_combos | Moderator (CATT) |
R4-2216949 | Email discussion summary for [104-bis-e][111] LTE_NR_HPUE_FWVM | Moderator (Nokia) |
R4-2216950 | Email discussion summary for [104-bis-e][113] HPUE_Basket_EN-DC | Moderator (Ericsson) |
R4-2216951 | Email discussion summary for [104-bis-e][114] HPUE_Basket_Intra-CA_TDD | Moderator (HiSilicon) |
R4-2216952 | Email discussion summary for [104-bis-e][115] HPUE_Basket_inter-CA_SUL | Moderator (China Telecom) |
R4-2216953 | Email discussion summary for [104-bis-e][116] HPUE_Basket_FDD | Moderator (China Unicom) |
R4-2216954 | Email discussion summary for [104-bis-e][117] LTE_NR_Other_WI | Moderator (Huawei) |
R4-2216987 | Email discussion summary for [104-bis-e][106] NR_Baskets_Part_2 | Moderator (Nokia) |
R4-2216988 | Email discussion summary for [104-bis-e][107] NR_Baskets_Part_3 | Moderator (Ericsson) |
R4-2216989 | Email discussion summary for [104-bis-e][108] NR_Baskets_Part_4 | Moderator (Nokia) |
R4-2216991 | Email discussion summary for [104-bis-e][110] NR_LTE_V2X_PC5_combos | Moderator (CATT) |
R4-2216992 | Email discussion summary for [104-bis-e][111] LTE_NR_HPUE_FWVM | Moderator (Nokia) |
R4-2216993 | Email discussion summary for [104-bis-e][113] HPUE_Basket_EN-DC | Moderator (Ericsson) |
R4-2216994 | Email discussion summary for [104-bis-e][114] HPUE_Basket_Intra-CA_TDD | Moderator (HiSilicon) |
R4-2216995 | Email discussion summary for [104-bis-e][115] HPUE_Basket_inter-CA_SUL | Moderator (China Telecom) |
R4-2216996 | Email discussion summary for [104-bis-e][116] HPUE_Basket_FDD | Moderator (China Unicom) |
R4-2216997 | Email discussion summary for [104-bis-e][117] LTE_NR_Other_WI | Moderator (Huawei) |
R4-2217766 | Email discussion summary for [104-bis-e][110] NR_LTE_V2X_PC5_combos | Moderator (CATT) |
R4-2217767 | Email discussion summary for [104-bis-e][111] LTE_NR_HPUE_FWVM | Moderator (Nokia) |
R4-2217768 | Email discussion summary for [104-bis-e][114] HPUE_Basket_Intra-CA_TDD | Moderator (HiSilicon) |
R4-2217769 | Email discussion summary for [104-bis-e][116] HPUE_Basket_FDD | Moderator (China Unicom) |
R4-2217770 | Email discussion summary for [104-bis-e][117] LTE_NR_Other_WI | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2215750 | TR 37.718-11-11 v0.2.0 Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) | CHTTL |
TDoc | Title | Source |
---|---|---|
R4-2215371 | DraftCR 38.101-3 Addition of 1 Band LTE and 1 Band NR EN-DC Combinations | AT&T |
R4-2215769 | TP for TR 37.718-11-11: support of DC_8B_n78A | CHTTL |
R4-2215839 | TP for TR 37.718-11-11 to include DC_1-n26 | Ericsson, Telstra |
R4-2215840 | TP for TR 37.718-11-11 to include DC_3-n26 | Ericsson, Telstra |
R4-2215841 | TP for TR 37.718-11-11 to include DC_7-n26 | Ericsson, Telstra |
R4-2216155 | TP for TR 37.718-11-11: DC_1_n1 | VODAFONE Group Plc |
R4-2216157 | TP for TR 37.717-21-11: DC_1-20_n7 | VODAFONE Group Plc |
R4-2216623 | TP for TR 37.718-11-11 on table templates and error corrections | ZTE Corporation |
R4-2217061 | TP for TR 37.718-11-11 to include DC_1-n26 | Ericsson, Telstra |
R4-2217064 | TP for TR 37.718-11-11: DC_1_n1 | VODAFONE Group Plc |
R4-2217065 | TP for TR 37.717-21-11: DC_1-20_n7 | VODAFONE Group Plc |
R4-2217087 | TP for TR 37.718-11-11 on table templates and error corrections | ZTE Corporation |
R4-2217102 | TP for TR 37.718-11-11 to include DC_3-n26 | Ericsson, Telstra |
R4-2217103 | TP for TR 37.718-11-11 to include DC_7-n26 | Ericsson, Telstra |
TDoc | Title | Source |
---|---|---|
R4-2216630 | Draft CR for TS 38.101-3 to add configuration DC_1A_n257(2G) | ZTE Corporation |
R4-2216631 | Draft CR for TS 38.101-3 to add configuration DC_7A_n257(2G) | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216246 | TR 37.718-21-11 V0.2.0 for DC of 2 LTE band and 1 NR band | Huawei, HiSilicon |
R4-2216247 | Draft CR on introduction of completed DC of 2 bands LTE and 1 band NR from RAN4#104-bis-e into TS 38.101-3 | Huawei, HiSilicon |
R4-2216248 | Rel-18 WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215372 | DraftCR 38.101-3 Addition of 2 Bands LTE and 1 Band NR EN-DC Combinations | AT&T |
R4-2215771 | TP for TR 37.718-21-11: support of DC_3A-8B_n78A, DC_3A-3A-8B_n78A | CHTTL |
R4-2215772 | TP for TR 37.718-21-11: support of DC_7A-8B_n78A, DC_7A-7A-8B_n78A | CHTTL |
R4-2215849 | TP for TR 37.718-21-11 to include DC_1_3-n26 | Ericsson, Telstra |
R4-2215850 | TP for TR 37.718-21-11 to include DC_1_7-n26 | Ericsson, Telstra |
R4-2215851 | TP for TR 37.718-21-11 to include DC_3_7-n26 | Ericsson, Telstra |
R4-2215901 | TP for TR 37.718-21-11: Including band combinations DC_3-41_n1 | ZTE Corporation,Ericsson |
R4-2215902 | TP for TR 37.718-21-11: Including band combinations DC_8-41_n78 | ZTE Corporation,Ericsson |
R4-2216092 | TP for TR 37 718-21-11 to include DC_20-41_n1 | Ericsson, ZTE |
R4-2216093 | TP for TR 37 718-21-11 to include DC_20-41_n78 | Ericsson, ZTE |
R4-2216094 | draft CR 38.101-3 to include DC_3-20_n1, DC_3-20_n78, DC_3-41_n78 configurations | Ericsson, ZTE |
R4-2216159 | TP for TR 37.718-11-11: DC_1-3_n1 | VODAFONE Group Plc |
R4-2216161 | TP for TR 37.718-21-11: DC_1-7_n1 | VODAFONE Group Plc |
R4-2216162 | TP for TR 37.718-21-11: DC_1-7_n20 | VODAFONE Group Plc |
R4-2216164 | TP for TR 37.718-21-11: DC_1-8_n20 | VODAFONE Group Plc |
R4-2216165 | TP for TR 37.718-21-11: DC_1-20_n1 | VODAFONE Group Plc |
R4-2216174 | TP for TR 37.718-21-11: DC_1-28_n20 | VODAFONE Group Plc |
R4-2216184 | TP for TR 37.718-21-11: DC_3-20_n3 | VODAFONE Group Plc |
R4-2216185 | TP for TR 37.718-21-11: DC_3-32_n7 | VODAFONE Group Plc |
R4-2216186 | TP for TR 37.718-21-11: DC_7-8_n20 | VODAFONE Group Plc |
R4-2216188 | TP for TR 37.718-21-11: DC_7-28_n20 | VODAFONE Group Plc |
R4-2216189 | TP for TR 37.718-21-11: DC_8-28_n3 | VODAFONE Group Plc |
R4-2216190 | TP for TR 37.718-21-11: DC_20-28_n78 | VODAFONE Group Plc |
R4-2216191 | TP for TR 37.718-21-11: DC_20-32_n7 | VODAFONE Group Plc |
R4-2216249 | TP for TR 37.718-21-11: update the format of tables for ?TIB and ?RIB values | Huawei, HiSilicon |
R4-2216250 | draft CR to 38.101-3: Uniform format for configurarion DC_aA-bA_nc(2A) | Huawei, HiSilicon |
R4-2216591 | TP for TR 37.718-21-11 DC_7A-8A_n7A | Huawei, HiSilicon |
R4-2216625 | TP for TR 37.718-21-11 on table templates and error corrections | ZTE Corporation |
R4-2217066 | TP for TR 37.718-11-11: DC_1-3_n1 | VODAFONE Group Plc |
R4-2217067 | TP for TR 37.718-21-11: DC_1-7_n20 | VODAFONE Group Plc |
R4-2217068 | TP for TR 37.718-21-11: DC_1-8_n20 | VODAFONE Group Plc |
R4-2217069 | TP for TR 37.718-21-11: DC_1-20_n1 | VODAFONE Group Plc |
R4-2217070 | TP for TR 37.718-21-11: DC_1-28_n20 | VODAFONE Group Plc |
R4-2217071 | TP for TR 37.718-21-11: DC_3-20_n3 | VODAFONE Group Plc |
R4-2217072 | TP for TR 37.718-21-11: DC_3-32_n7 | VODAFONE Group Plc |
R4-2217073 | TP for TR 37.718-21-11: DC_7-8_n20 | VODAFONE Group Plc |
R4-2217074 | TP for TR 37.718-21-11: DC_7-28_n20 | VODAFONE Group Plc |
R4-2217075 | TP for TR 37.718-21-11: DC_8-28_n3 | VODAFONE Group Plc |
R4-2217076 | TP for TR 37.718-21-11: DC_20-28_n78 | VODAFONE Group Plc |
R4-2217077 | TP for TR 37.718-21-11: DC_20-32_n7 | VODAFONE Group Plc |
R4-2217098 | TP for TR 37 718-21-11 to update DC_(n)3-n8 | Skyworks |
R4-2217104 | TP for TR 37.718-21-11 to include DC_3_7-n26 | Ericsson, Telstra |
TDoc | Title | Source |
---|---|---|
R4-2216369 | draft Big CR to introduce new combinations DC of x bands LTE inter-band CA (x345) and 1 NR band | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215373 | DraftCR 38.101-3 Addition of 3 Bands LTE and 1 Band NR EN-DC Combinations | AT&T |
R4-2215838 | draft CR 38.101-3 to add DC_1-3-7_n26 | Ericsson, Telstra |
R4-2216047 | Draft CR for 38.101-3 to add DC_3A-8A-20A_n28A and DC_3C-8A-20A_n28A | Huawei, Hisilicon |
R4-2216048 | Draft CR for 38.101-3 to add DC_3C-7A-8A_n78A | Huawei, Hisilicon |
R4-2216049 | Draft CR for 38.101-3 to add DC_3A-20A-38A_n78A and DC_3C-20A-38A_n78A | Huawei, Hisilicon |
R4-2216050 | Draft CR for 38.101-3 to add DC_1A-3C-7A-8A_n78A | Huawei, Hisilicon |
R4-2216051 | Draft CR for 38.101-3 to add DC_3A-7A-20A-38A_n78A | Huawei, Hisilicon |
R4-2216205 | TP for TR 37.718-31-11: DC_1-3-7_n1 | VODAFONE Group Plc |
R4-2216207 | TP for TR 37.718-31-11: DC_1-3-20_n1 | VODAFONE Group Plc |
R4-2216208 | TP for TR 37.718-31-11: DC_1-3-20_n3 | VODAFONE Group Plc |
R4-2216209 | TP for TR 37.718-31-11: DC_1-7-8_n20 | VODAFONE Group Plc |
R4-2216210 | TP for TR 37.718-31-11: DC_1-7-28_n20 | VODAFONE Group Plc |
R4-2216211 | TP for TR 37.718-31-11: DC_3-7-20_n3 | VODAFONE Group Plc |
R4-2216212 | TP for TR 37.718-31-11: DC_3-20-32_n7 | VODAFONE Group Plc |
R4-2216213 | TP for TR 37.718-31-11: DC_8-20-28_n3 | VODAFONE Group Plc |
R4-2216214 | TP for TR 37.718-31-11: DC_8-20-32_n3 | VODAFONE Group Plc |
R4-2217063 | Draft CR for 38.101-3 to add DC_3A-8A-20A_n28A and DC_3C-8A-20A_n28A | Huawei, Hisilicon |
R4-2217078 | TP for TR 37.718-31-11: DC_1-3-7_n1 | VODAFONE Group Plc |
R4-2217079 | TP for TR 37.718-31-11: DC_1-3-20_n1 | VODAFONE Group Plc |
R4-2217080 | TP for TR 37.718-31-11: DC_1-3-20_n3 | VODAFONE Group Plc |
R4-2217081 | TP for TR 37.718-31-11: DC_1-7-8_n20 | VODAFONE Group Plc |
R4-2217082 | TP for TR 37.718-31-11: DC_1-7-28_n20 | VODAFONE Group Plc |
R4-2217083 | TP for TR 37.718-31-11: DC_3-7-20_n3 | VODAFONE Group Plc |
R4-2217084 | TP for TR 37.718-31-11: DC_3-20-32_n7 | VODAFONE Group Plc |
R4-2217085 | TP for TR 37.718-31-11: DC_8-20-28_n3 | VODAFONE Group Plc |
R4-2217086 | TP for TR 37.718-31-11: DC_8-20-32_n3 | VODAFONE Group Plc |
R4-2217813 | TR 37.718-31-11 V0.1.0 for DC_R18_xBLTE_1BNR_yDL2UL | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215383 | TR 37.718-11-21 v0.2.0 TR Update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-18 | LG Electronics Deutschland |
TDoc | Title | Source |
---|---|---|
R4-2215842 | TP for TR 37.718-11-21 to include DC_1_n26-n78 | Ericsson, Telstra |
R4-2215843 | TP for TR 37.718-11-21 to include DC_3_n26-n78 | Ericsson, Telstra |
R4-2215844 | TP for TR 37.718-11-21 to include DC_7_n26-n78 | Ericsson, Telstra |
R4-2215845 | TP for TR 37.718-11-21 to include DC_1-3_n26-n78 | Ericsson, Telstra |
R4-2215846 | TP for TR 37.718-11-21 to include DC_1-7_n26-n78 | Ericsson, Telstra |
R4-2215847 | TP for TR 37.718-11-21 to include DC_3-7_n26-n78 | Ericsson, Telstra |
R4-2215848 | TP for TR 37.718-11-21 to include DC_1-3-7_n26-n78 | Ericsson, Telstra |
R4-2215903 | draft CR to TS38.101-3 DC_3A_n41-n79 | ZTE Corporation |
R4-2215904 | draft CR to TS38.101-3 DC_3A_n40A-n41C | ZTE Corporation |
R4-2215905 | draft CR to TS38.101-3 DC_3A_n40A-n79C | ZTE Corporation |
R4-2216624 | TP for TR 37.718-11-21 on table templates and error corrections | ZTE Corporation |
R4-2216628 | TP for TR 37.718-11-21_DC_1A-38A_n7A-n78A | ZTE Corporation |
R4-2216664 | TP for TR 37.718-11-21 DC_20A_n1A-n75A | Huawei, HiSilicon |
R4-2216665 | TP for TR 37.718-11-21 DC_7A-20A_n1A-n75A | Huawei, HiSilicon |
R4-2216666 | TP for TR 37.718-11-21 DC_7A_n1A-n75A | Huawei, HiSilicon |
R4-2216667 | TP for TR 37.718-11-21 DC_3A-20A_n1A-n75A and DC_3C-20A_n1A-n75A | Huawei, HiSilicon |
R4-2216668 | TP for TR 37.718-11-21 DC_3A-7A_n1A-n75A and DC_3C-7A_n1A-n75A | Huawei, HiSilicon |
R4-2216669 | TP for TR 37.718-11-21 DC_3A_n1A-n75A and DC_3C_n1A-n75A | Huawei, HiSilicon |
R4-2217062 | TP for TR 37.718-11-21 to include DC_1_n26-n78 | Ericsson, Telstra |
R4-2217088 | TP for TR 37.718-11-21_DC_1A-38A_n7A-n78A | ZTE Corporation |
R4-2217105 | TP for TR 37.718-11-21 DC_3A_n1A-n75A and DC_3C_n1A-n75A | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215555 | TP for TR 37.718-11-21 DC_1A_n8A-n257AGHIJKLM | Huawei Technologies France |
R4-2215557 | TP for TR 37.718-11-21 DC_1A_n77A-n257AJKLM | Huawei Technologies France |
R4-2215558 | TP for TR 37.718-11-21 DC_3A_n77A-n257GHIJKLM, DC_3A_n77(2A)-n257AGHIKLM | Huawei Technologies France |
R4-2215559 | TP for TR 37.718-11-21 DC_8A_n3A-n257AGHIJKLM | Huawei Technologies France |
R4-2215906 | draft CR to TS38.101-3 DC_8A_n34A-n258 | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216085 | TR 38.718-01-01 v0.0.1 Rel-18 NR Intra-band | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216373 | DraftCR Additions_to_CA_n46 | Nokia, BT |
R4-2216374 | DraftCR Additions_to_CA_n102 | Nokia, BT |
R4-2217057 | DraftCR Additions_to_CA_n46 | Nokia, BT |
R4-2217058 | DraftCR Additions_to_CA_n102 | Nokia, BT |
TDoc | Title | Source |
---|---|---|
R4-2216055 | Draft CR for TS 38.101-2 to introduce intra-band non-contiguos configurations of band n257 | Huawei, HiSilicon |
R4-2216056 | Draft CR for TS 38.101-2 to introduce intra-band non-contiguos configurations of band n258 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215909 | 38.718-02-01 v0.2.0: Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215489 | TP for 38.718-02-01 CA_n3A-n41C with UL_n41C | CMCC |
R4-2215517 | Draft CR for TS 38.101-1 to add CA_n48A-n66B and CA_n48(2A)-n66B | Dish Network, Samsung |
R4-2215522 | TP for TR 38.718-02-01: CA_n26-n77 | Dish Network, Samsung |
R4-2215524 | TP for TR 38.718-02-01: CA_n70-n77 | Dish Network, Samsung |
R4-2215740 | Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 2 bands | Samsung, Telus, Bell Mobility |
R4-2215742 | TP for TR 38.718-02-01 CA_n12A-n25A | Samsung, Telus, Bell Mobility |
R4-2215774 | DraftCR for 38.101-1: Add additional band n77 uplink configurations | Verizon, Samsung, Ericsson |
R4-2215907 | draft CRto TS 38.101-1_include n39A-n41C | ZTE Corporation |
R4-2215922 | draft CR 38.101-3 to add DC_n26A-n258(A-M) | Ericsson, Telstra |
R4-2215923 | draft CR 38.101-1 to add CA_n3B-n78(2A) | Ericsson, Telstra |
R4-2215924 | draft CR 38.101-1 to add CA_n7B-n78(2A) | Ericsson, Telstra |
R4-2216057 | Draft CR for TS 38.101-1 to introduce configurations CA_n77A-n78C and CA_n77A-n78(2A) | Huawei, HiSilicon |
R4-2216089 | draft CR 38.101-1 to add 2DL/xUL DC combinations | Ericsson, BT plc |
R4-2216141 | TP for TR 38.718-02-01: CA_n3-n94 | VODAFONE Group Plc |
R4-2216142 | TP for TR 38.718-02-01: CA_n7-n75 | VODAFONE Group Plc |
R4-2216151 | TP for TR 38.718-02-01: CA_n28-n94 | VODAFONE Group Plc |
R4-2216152 | TP for TR 38.718-02-01: CA_n78-n94 | VODAFONE Group Plc |
R4-2216382 | draftCR_additions_to_CA_n5-n77 | Nokia, Bell, Telus |
R4-2216383 | draftCR_additions_to_CA_n7-n77 | Nokia, Bell, Telus |
R4-2216384 | draftCR_additions_to_CA_n25-n77 | Nokia, Bell, Telus |
R4-2216385 | draftCR_additions_to_CA_n66-n77 | Nokia, Bell, Telus |
R4-2216386 | draftCR_additions_to_CA_n71-n77 | Nokia, Bell, Telus |
R4-2216626 | TP for TR 38.718-02-01 on table templates and error corrections | ZTE Corporation |
R4-2216629 | TP for TR 38.718-02-01 on corrections to REFSENS requirements for configurations CA_n3-n26 and CA_n7-n26 | ZTE Corporation |
R4-2216661 | TP for TR 38.718-02-01 CA_n75A-n78A | Huawei, HiSilicon |
R4-2216662 | TP for TR 38.718-02-01 CA_n28A-n75A BCS2 | Huawei, HiSilicon |
R4-2216663 | TP for TR 38.718-02-01 CA_n1A-n75A | Huawei, HiSilicon |
R4-2216780 | DraftCR add uplink CA_n78(2A) to the existing two bands DL CA combinations | Huawei, HiSilicon, BT |
R4-2217034 | TP for TR 38.718-02-01: CA_n26-n77 | Dish Network, Samsung |
R4-2217035 | TP for TR 38.718-02-01: CA_n70-n77 | Dish Network, Samsung |
R4-2217036 | Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 2 bands | Samsung, Telus, Bell Mobility |
R4-2217037 | draft CR 38.101-1 to add CA_n3B-n78(2A) | Ericsson, Telstra |
R4-2217038 | Draft CR for TS 38.101-1 to introduce configurations CA_n77A-n78C and CA_n77A-n78(2A) | Huawei, HiSilicon |
R4-2217039 | TP for TR 38.718-02-01: CA_n3-n94 | VODAFONE Group Plc |
R4-2217040 | TP for TR 38.718-02-01: CA_n28-n94 | VODAFONE Group Plc |
R4-2217041 | TP for TR 38.718-02-01: CA_n78-n94 | VODAFONE Group Plc |
R4-2217042 | TP for TR 38.718-02-01 CA_n75A-n78A | Huawei, HiSilicon |
R4-2217106 | TP for 38.718-02-01 CA_n3A-n41C with UL_n41C | CMCC |
R4-2217107 | draftCR_additions_to_CA_n7-n77 | Nokia, Bell, Telus |
R4-2217108 | draftCR_additions_to_CA_n25-n77 | Nokia, Bell, Telus |
R4-2217109 | draftCR_additions_to_CA_n66-n77 | Nokia, Bell, Telus |
R4-2217110 | draftCR_additions_to_CA_n71-n77 | Nokia, Bell, Telus |
R4-2217803 | DraftCR add uplink CA_n78(2A) to the existing two bands DL CA combinations | Huawei, HiSilicon, BT |
TDoc | Title | Source |
---|---|---|
R4-2215436 | Draft CR for TS 38.101-3: Support of DC_n77-n258 | SoftBank Corp. |
R4-2215437 | Draft CR for TS 38.101-3: Support of UL configurations in DC_n79-n258 | SoftBank Corp. |
R4-2215773 | DraftCR for 38.101-3: Inter-band NR CA_n48-n261 NR and NR-DC | Verizon, Samsung, Ericsson |
R4-2215925 | draft CR 38.101-3 to add CA_n26A-n258(A-M) | Ericsson, Telstra |
R4-2216430 | Adding missing combinations with n48 and n263 | Charter Communications, Inc |
R4-2216632 | Draft CR for TS 38.101-3 to add configurations CA_n3A-n257(2G) and DC_n3A-n257(2G) | ZTE Corporation |
R4-2216633 | Draft CR for TS 38.101-3 to add configurations CA_n78A-n257(2G) and DC_n78A-n257(2G) | ZTE Corporation |
R4-2217028 | draft CR 38.101-3 to add missing combinations with n48 and n263 | Charter Communications, Inc |
TDoc | Title | Source |
---|---|---|
R4-2216720 | TR38.718-03-01 v0.2.0 on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL (x=1,2) | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215443 | TP for TR 38.718-03-01: CA_n3-n41-n79 | SoftBank Corp. |
R4-2215444 | TP for TR 38.718-03-01: CA_n41-n77-n79 | SoftBank Corp. |
R4-2215520 | Draft CR for TS 38.101-1 to add CA_n48A-n66(2A)-n77A | Dish Network, Samsung |
R4-2215526 | TP for TR 38.718-03-01: CA_n29-n70-n71 | Dish Network, Samsung |
R4-2215529 | TP for TR 38.718-03-01: CA_n48-n71-n77 | Dish Network, Samsung |
R4-2215739 | Draft CR for 38.101-1 to add missing configurations and intoduce new configurations for NR inter-band CA 3 bands | Samsung, Telus, Bell Mobility |
R4-2216058 | Draft CR for TS 38.101-1 to introduce some configurations for CA_n1-n3-n79 | Huawei, HiSilicon |
R4-2216059 | TP for TR to introduce CA_n1A-n3A-n38A, CA_n1A-n3B-n38A, CA_n1(2A)-n3A-n38A, CA_n1(2A)-n3B-n38A, CA_n1A-n3(2A)-n38A and CA_n1(2A)-n3(2A)-n38A | Huawei, HiSilicon |
R4-2216060 | TP for TR 38.718-03-01 to introduce CA_n1A-n7A-n38A and CA_n1(2A)-n7A-n38A | Huawei, HiSilicon |
R4-2216061 | TP for TR 38.718-03-01 to introduce CA_n3A-n7A-n38A, CA_n3B-n7A-n38A and CA_n3(2A)-n7A-n38A | Huawei, HiSilicon |
R4-2216062 | TP for TR 38.718-03-01 to introduce CA_n3A-n78A-n79A, CA_n3A-n78A-n79C, CA_n3B-n78A-n79A, CA_n3B-n78A-n79C, CA_n3(2A)-n78A-n79A and CA_n3(2A)-n78A-n79C | Huawei, HiSilicon |
R4-2216090 | draft CR 38.101-1 to add 3DL/xUL DC combinations | Ericsson, BT plc |
R4-2216375 | draftCR 38.101-1 CA_n5A-n25A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216376 | draftCR 38.101-1 CA_n5A-n66A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216377 | draftCR 38.101-1 CA_n7A-n25A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216378 | draftCR 38.101-1 CA_n7A-n66A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216379 | draftCR 38.101-1 CA_n25A-n66A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216380 | draftCR 38.101-1 CA_n25-n71-n77 configurations | Nokia, Bell, Telus |
R4-2216381 | draftCR 38.101-1 CA_n66A-n71A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2216627 | TP for TR 38.718-03-01 on table templates and error corrections | ZTE Corporation |
R4-2216781 | DraftCR add uplink CA_n78(2A) to the existing 3 bands DL CA combinations | Huawei, HiSilicon, BT |
R4-2217043 | TP for TR 38.718-03-01: CA_n3-n41-n79 | SoftBank Corp. |
R4-2217044 | Draft CR for TS 38.101-1 to add CA_n48A-n66(2A)-n77A | Dish Network, Samsung |
R4-2217045 | TP for TR 38.718-03-01: CA_n29-n70-n71 | Dish Network, Samsung |
R4-2217046 | TP for TR 38.718-03-01: CA_n48-n71-n77 | Dish Network, Samsung |
R4-2217047 | Draft CR for TS 38.101-1 to introduce some configurations for CA_n1-n3-n79 | Huawei, HiSilicon |
R4-2217048 | TP for TR to introduce CA_n1A-n3A-n38A, CA_n1A-n3B-n38A, CA_n1(2A)-n3A-n38A, CA_n1(2A)-n3B-n38A, CA_n1A-n3(2A)-n38A and CA_n1(2A)-n3(2A)-n38A | Huawei, HiSilicon |
R4-2217049 | TP for TR 38.718-03-01 to introduce CA_n1A-n7A-n38A and CA_n1(2A)-n7A-n38A | Huawei, HiSilicon |
R4-2217050 | TP for TR 38.718-03-01 to introduce CA_n3A-n7A-n38A, CA_n3B-n7A-n38A and CA_n3(2A)-n7A-n38A | Huawei, HiSilicon |
R4-2217051 | TP for TR 38.718-03-01 to introduce CA_n3A-n78A-n79A, CA_n3A-n78A-n79C, CA_n3B-n78A-n79A, CA_n3B-n78A-n79C, CA_n3(2A)-n78A-n79A and CA_n3(2A)-n78A-n79C | Huawei, HiSilicon |
R4-2217052 | draft CR 38.101-1 to add 3DL/xUL DC combinations | Ericsson, BT plc |
R4-2217111 | draftCR 38.101-1 CA_n5A-n25A-n77(3A) configuration | Nokia, Bell, Telus |
R4-2217112 | DraftCR add uplink CA_n78(2A) to the existing 3 bands DL CA combinations | Huawei, HiSilicon, BT |
TDoc | Title | Source |
---|---|---|
R4-2215438 | Draft CR for TS 38.101-3: Support of UL configurations for CA_n3-n41-n257 and CA_n28-n41-n257 | SoftBank Corp. |
R4-2215439 | Draft CR for TS 38.101-1: Support of DC_n1-n41-n79 and DC_n41-n77-n79 | SoftBank Corp. |
R4-2215440 | Draft CR for TS 38.101-3: Support of DC_n77-n79-n258 | SoftBank Corp. |
R4-2215770 | DraftCR for 38.101-3: NR FR1 and FR2 inter-band CA DC combinations for 3 bands DL with single and 2 bands UL | Verizon, Samsung, Ericsson |
R4-2215926 | draft CR 38.101-3 to add CA_n26A-n78A-n258(A-M) and DC_n26A-n78A-n258(A-M) | Ericsson, Telstra |
R4-2215927 | draft CR 38.101-3 to add CA_n28A-n78A-n258(A-M) and DC_n28A-n78A-n258(A-M) | Ericsson, Telstra |
R4-2217053 | Draft CR for TS 38.101-3: Support of UL configurations for CA_n3-n41-n257 and CA_n28-n41-n257 | SoftBank Corp. |
R4-2217054 | DraftCR for 38.101-3: NR FR1 and FR2 inter-band CA DC combinations for 3 bands DL with single and 2 bands UL | Verizon, Samsung, Ericsson |
R4-2217055 | draft CR 38.101-3 to add CA_n28A-n78A-n258(A-M) and DC_n28A-n78A-n258(A-M) | Ericsson, Telstra |
TDoc | Title | Source |
---|---|---|
R4-2215370 | DraftCR 38.101-1 Addition of CA_n2-n30-n66-n77 | AT&T |
R4-2215741 | Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 4 bands | Samsung, Telus, Bell Mobility |
R4-2216091 | draft CR 38.101-1 to add 4DL/xUL DC combinations | Ericsson, BT plc |
R4-2216782 | DraftCR add uplink CA_n78(2A) to the existing 4 and 5 bands DL CA combinations | Huawei, HiSilicon, BT |
R4-2217113 | DraftCR add uplink CA_n78(2A) to the existing 4 and 5 bands DL CA combinations | Huawei, HiSilicon, BT |
TDoc | Title | Source |
---|---|---|
R4-2215441 | Draft CR for TS 38.101-1: Support CA_n1-n28-n41-n79, CA_n1-n41-n77-n79 and CA_n28-n41-n77-n79 | SoftBank Corp. |
R4-2215442 | Draft CR for TS 38.101-3: Support of CA_n1-n41-n79-n257, CA_n28-n41-n79-n257 and CA_n41-n77-n79-n257 | SoftBank Corp. |
TDoc | Title | Source |
---|---|---|
R4-2216045 | Draft TR 37.718-00-00 v0.2.0 | Huawei, HiSilicon |
R4-2216046 | Draft Big CR on Introduction of completed SUL band combinations into TS 38.101-1 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216622 | TP for TR 37.718-00-00 on table templates and error corrections | ZTE Corporation |
R4-2216670 | TP for TR 37.718-00-00 CA_n41A_SUL_n79A-n98A and CA_n79A_SUL_n41A-n98A | Huawei, HiSilicon, CMCC |
R4-2216671 | TP for TR 37.718-00-00 CA_n41A_SUL_n79A-n95A and CA_n79A_SUL_n41A-n95A | Huawei, HiSilicon, CMCC |
R4-2217059 | TP for TR 37.718-00-00 CA_n41A_SUL_n79A-n98A and CA_n79A_SUL_n41A-n98A | Huawei, HiSilicon, CMCC |
R4-2217060 | TP for TR 37.718-00-00 CA_n41A_SUL_n79A-n95A and CA_n79A_SUL_n41A-n95A | Huawei, HiSilicon, CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215376 | TP for V2X_n34A-n47A_V2X_34A-n47A_V2X_n34A-47A | Qualcomm Incorporated |
R4-2215433 | Draft CR for TS 38.101-1, Introduce new band combination of V2X_n3A-n47A | CATT |
R4-2215434 | Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n3A_47A | CATT |
R4-2215435 | TP on coexistence study of V2X_n3A-n47A and V2X_n3A_47A | CATT |
R4-2217114 | TP for V2X_n34A-n47A_V2X_34A-n47A_V2X_n34A-47A | Qualcomm Incorporated |
R4-2217115 | TP on coexistence study of V2X_n3A-n47A and V2X_n3A_47A | CATT |
R4-2217116 | WF on PC1 MPR with edge region | Nokia, Nokia Shanghai Bell |
R4-2217812 | Draft TR 37.878 for Rel-18 band combinations for concurrent operation of NR/LTE Uu bands/band combinations and one NR/LTE V2X PC5 band | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215318 | TR 37.389 v0.1.0 | Nokia |
R4-2215319 | TP for TR 37.389 to add abbreviations | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2216044 | PC1 MPR with edge region | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215554 | DraftCR 38.101-3 Addition of PC2 EN-DC Combinations | AT&T |
R4-2217119 | WF on HPUE_Basket_Intra-CA_TDD | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216082 | WID on HPUE_NR_FR1_TDD_intra_CA_R18 | Huawei,HiSilicon |
R4-2216083 | Draft CR on TS38.101-1 Addition of intra-band CA Combinations with PC2 and PC1.5 | Huawei,HiSilicon |
R4-2217118 | Draft CR on TS38.101-1 Addition of intra-band CA Combinations with PC2 | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216081 | Discussion on UE RF requirements with PC2 | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216080 | Discussion on UE RF requirements with PC1.5 | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216779 | TR for High power UE for FR1 NR inter-band CA/DC or NR SUL band combination with y (1Huawei, HiSilicon, China Telecom |
|
R4-2217120 | Big CR to 38.101-1 Introduce RF requirements for HPUE inter- band CA with y(y=2,3,4) bands downlink and x bands uplink (x =1,2) | China Telecom |
R4-2217121 | WF on requirements for HPUE_Basket_FDD | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2215556 | DraftCR 38.101-1 Addition of PC2 CA Combinations | AT&T |
R4-2216802 | Draft CR for 38.101-1: CA_n25-n41-n66 PC2 and PC1.5 | T-Mobile USA |
R4-2216803 | Draft CR for 38.101-1: CA_n25-n41-n66-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216804 | Draft CR for 38.101-1: CA_n25-n41-n71 PC2 and PC1.5 | T-Mobile USA |
R4-2216805 | Draft CR for 38.101-1: CA_n25-n41-n71-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216806 | Draft CR for 38.101-1: CA_n25-n41-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216807 | Draft CR for 38.101-1: CA_n25-n66-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216808 | Draft CR for 38.101-1: CA_n25-n71-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216809 | Draft CR for 38.101-1: CA_n25-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216810 | Draft CR for 38.101-1: CA_n41-n66-n71 PC2 and PC1.5 | T-Mobile USA |
R4-2216811 | Draft CR for 38.101-1: CA_n41-n66-n71-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216812 | Draft CR for 38.101-1: CA_n41-n66-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216813 | Draft CR for 38.101-1: CA_n41-n71-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216814 | Draft CR for 38.101-1: CA_n66-n71-n77 PC2 and PC1.5 | T-Mobile USA |
R4-2216816 | Draft CR for 38.101-1: CA_n71-n77 PC2 and PC1.5 | T-Mobile USA |
TDoc | Title | Source |
---|---|---|
R4-2216815 | Draft CR for 38.101-1: CA_n66-n77 PC1.5 | T-Mobile USA |
TDoc | Title | Source |
---|---|---|
R4-2215660 | MSD analysis for CA_n3-n78 with PC2 n3 UL | Apple |
R4-2215894 | On CA band combination of DL CA_n1-n78 with UL PC2 n1 | ZTE Corporation,China Unicom |
R4-2215895 | On CA band combination of DL CA_n3-n78 with UL PC2 n3 | ZTE Corporation,China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2215853 | High power for FR1 TDD single bands with power class 1.5 | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215330 | A-MPR for PC1.5 TDD bands | Skyworks Solutions Inc. |
R4-2215509 | Draft CR for updating high power class for FR1 TDD single bands | CMCC |
R4-2216123 | Discussion on the PC1.5 UE RF requirements | vivo |
R4-2216775 | Initial consideration on PC1.5 TDD bands | Huawei, HiSilicon |
R4-2217117 | Draft CR for updating high power class for FR1 TDD single bands | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215852 | TR 38.xxx v0.0.1 HPUE_NR_FR1_FDD_R18 | China Unicom |
R4-2215921 | TR 38.xxx v0.1.0 HPUE_NR_FR1_FDD_R18 | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2215331 | Architecture MSD and A-MPR aspects for PC2 FDD low bands | Skyworks Solutions Inc. |
R4-2215332 | Architecture MSD and A-MPR aspects for PC2 FDD mid bands | Skyworks Solutions Inc. |
R4-2215661 | MSD analyses for PC2 FDD bands with 2Tx | Apple |
R4-2215893 | Discussion on PC2 band n8 RSD | ZTE Corporation,China Unicom |
R4-2216124 | Discussion on the PC2 UE maximum output power and Tx power tolerance | vivo |
R4-2216774 | Initial consideration on PC2 FDD bands | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216097 | TR 37.877 0.1.0 draft TR for Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2216096 | TP to 37.877 DL interruption clarification for CA_n1-n5-n78 at dynamic Tx switching | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2216658 | Revised WID for Rel-18 Basket Simultaneous Rx/Tx | Huawei, HiSilicon |
R4-2216659 | TR skeleton for TR 38.xxx Simultaneous RxTx inter-band combination in Rel-18 | Huawei, HiSilicon |
R4-2217123 | Revised WID for Rel-18 Basket Simultaneous Rx/Tx | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215510 | Draft CR for updating simultaneous Rx/Tx requirements for CA_n39-n41 and CA_n40-n41 | CMCC |
R4-2215899 | RF requirements on CA_n39-n41 supporting simultaneous Rx/Tx | ZTE Corporation |
R4-2216153 | Discussion on new WI: Simultaneous Rx/Tx inter-band combinations for NR CA/DC, NR SUL and LTE/NR DC in Rel-18 | MediaTek Inc. |
R4-2216371 | Discussion on CA_n40-n41 synchronous RX_TX (v02) | Nokia, Nokia Shanghai Bell |
R4-2216660 | Discussion on UE supporting CA_n39A-n41A with simultaneous Rx/Tx | Huawei, HiSilicon |
R4-2217122 | Draft CR for updating simultaneous Rx/Tx requirements for CA_n39-n41 and CA_n40-n41 | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2215375 | Base line TR 38 892 | Spark NZ Ltd |
R4-2216529 | Revised WID for on APT 600 MHz NR band | ZTE Corporation |
R4-2217124 | Base line TR 38 892 | Spark NZ Ltd |
R4-2217806 | WF on UE requirements for n105 | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215637 | REFSENS and Blocking requirement for n105 | Skyworks Solutions Inc. |
R4-2215669 | Refsens and blocking for the 600MHz APT band | Apple |
R4-2215929 | TP on System parameters for APT600 | Nokia, Nokia Shanghai Bell |
R4-2215942 | Asymmetric bandwidths for APT 600 MHz | Ericsson |
R4-2216156 | REFSENS for APT-600 | MediaTek Inc. |
R4-2216451 | TP for TR38.892 | OPPO |
R4-2216646 | In band blocking for APT 600 | Qualcomm Incorporated |
R4-2216647 | Variable duplex for the APT 600 MHz band | Qualcomm Incorporated |
R4-2216648 | Introduction of APT 600 MHz band | Qualcomm Incorporated |
R4-2217125 | TP on System parameters for APT600 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215930 | UE REFENS for APT600 | Nokia, Nokia Shanghai Bell |
R4-2216524 | Draft CR to TS 38.141-1: Introduction of NR band APT600 [n105] | Ericsson |
R4-2216525 | Draft CR to TS 37.105: Introduction of NR band APT600 [n105] | Ericsson |
R4-2216530 | Further discussion on BS RF requirements for APT600MHz | ZTE Corporation |
R4-2216531 | draft CR to TS38.104 the introduction of APT600MHz | ZTE Corporation |
R4-2216532 | draft CR to TS37.145-1 the introduction of APT600MHz | ZTE Corporation |
R4-2216533 | draft CR to TS37.145-2 the introduction of APT600MHz | ZTE Corporation |
R4-2216534 | draft CR to TS38.174 the introduction of APT600MHz | ZTE Corporation |
R4-2216535 | draft CR to TS38.176-1 the introduction of APT600MHz | ZTE Corporation |
R4-2216536 | draft CR to TS38.176-2 the introduction of APT600MHz | ZTE Corporation |
R4-2216537 | draft CR to TS38.106 the introduction of APT600MHz | ZTE Corporation |
R4-2216732 | draft CR to 37.104 on introduction of Band n105 | Nokia, Nokia Shanghai Bell |
R4-2216733 | draft CR to 37.141 on introduction of Band n105 | Nokia, Nokia Shanghai Bell |
R4-2216734 | draft CR to 38.141-2 on introduction of Band n105 | Nokia, Nokia Shanghai Bell |
R4-2217126 | draft CR to TS38.104 the introduction of APT600MHz | ZTE Corporation |
R4-2217127 | Draft CR to TS 38.141-1: Introduction of NR band APT600 [n105] | Ericsson |
R4-2217128 | Draft CR to TS 37.105: Introduction of NR band APT600 [n105] | Ericsson |
R4-2217129 | draft CR to TS37.145-1 the introduction of APT600MHz | ZTE Corporation |
R4-2217130 | draft CR to TS37.145-2 the introduction of APT600MHz | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216288 | Initial discussion on RRM impacts due to introduction of APT 600MHz NR band | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216955 | Email discussion summary for [104-bis-e][118] NR_600MHz_APT_part1 | Moderator (Ericsson) |
R4-2216956 | Email discussion summary for [104-bis-e][119] NR_600MHz_APT_part2 | Moderator (Ericsson) |
R4-2216998 | Email discussion summary for [104-bis-e][118] NR_600MHz_APT_part1 | Moderator (Ericsson) |
R4-2216999 | Email discussion summary for [104-bis-e][119] NR_600MHz_APT_part2 | Moderator (Ericsson) |
R4-2217771 | Email discussion summary for [104-bis-e][118] NR_600MHz_APT_part1 | Moderator (Ericsson) |
R4-2217772 | Email discussion summary for [104-bis-e][119] NR_600MHz_APT_part2 | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2215646 | Update to the workplan for enhanced operation in unlicensed NR bands | Apple |
R4-2215647 | Update of the regulatory requirements and summary of NS values | Apple |
R4-2215649 | Draft running CR for TR 38.849 | Apple |
R4-2215671 | Draft running CR on enhancement for shared spectrum access | Apple |
R4-2217693 | Update to the workplan for enhanced operation in unlicensed NR bands | Apple |
R4-2217694 | Draft running CR for TR 38.849 | Apple |
R4-2217695 | Draft running CR on enhancement for shared spectrum access | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215648 | On enabling first 20MHz for bands n96 and n102 | Apple |
R4-2215650 | On the introduction of power class fallback for shared spectrum access | Apple |
R4-2215670 | Draft CR on power class fallback for shared spectrum bands | Apple |
R4-2216871 | PC5 NRU UE 100MHz A-MPR for a few LPI and Std NS | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2215351 | Discussion on UE RF requirements for SP and LPI | Charter Communications, Inc |
R4-2215651 | NR-U MPR and A-MPR for PC3 | Apple |
R4-2215783 | Discussion on NR-U PC3 UE RF requirements | LG Electronics |
R4-2216206 | PC3 NRU MPR versus ACLR | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216957 | Email discussion summary for [104-bis-e][120] NR_unlic_enh | Moderator (Apple) |
R4-2217000 | Email discussion summary for [104-bis-e][120] NR_unlic_enh | Moderator (Apple) |
R4-2217131 | WF on NR-U PC3 requirements and MPR/A-MPR | Charter Communications, Inc |
R4-2217132 | WF on NR-U 100MHz and Channel Raster | Apple |
R4-2217773 | Email discussion summary for [104-bis-e][120] NR_unlic_enh | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2215366 | Views on 100kHz channel raster and the carrier resource grid | Intel Corporation |
R4-2215644 | Clarifications on key open issues for irregular channels | Apple |
R4-2215672 | UE Channel Bandwidth Configuration | Qualcomm Incorporated |
R4-2215880 | Discussion on SIB1 signaling and CBW configuration | ZTE Wistron Telecom AB |
R4-2215928 | Discussion on contentious issues of SIB1 signalling and CBW configuration | Nokia, Nokia Shanghai Bell |
R4-2215943 | Background to changes on cell-specific carrier bandwidth signaling and UE specific CHBW configuration in RAN4 specifications | Ericsson |
R4-2215944 | Clarification of carrier grid and channel bandwidth mapping to the channel raster | Ericsson, China Telecom, Intel |
R4-2215945 | Clarification of carrier grid and channel bandwidth mapping to the channel raster | Ericsson, China Telecom, Intel |
R4-2215946 | Clarification of carrier grid and channel bandwidth mapping to the channel raster | Ericsson, China Telecom, Intel |
R4-2215947 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2215948 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2215949 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2215950 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2215951 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2215952 | Carrier resource grid mapping to channel raster and use of UE-specific bandwidth | Ericsson, China Telecom, Intel |
R4-2216235 | Consideration of the outcome on SIB1 and CBW configuration issue | Huawei, HiSilicon |
R4-2216236 | Further discussion on SIB1 signaling and CBW configuration | Huawei, HiSilicon |
R4-2216801 | BWPs and UE specific channel BWs and the 100 kHz raster | T-Mobile USA |
TDoc | Title | Source |
---|---|---|
R4-2216960 | Email discussion summary for [104-bis-e][124] FS_NR_eff_BW_util | Moderator (Ericsson) |
R4-2217003 | Email discussion summary for [104-bis-e][124] FS_NR_eff_BW_util | Moderator (Ericsson) |
R4-2217776 | Email discussion summary for [104-bis-e][124] FS_NR_eff_BW_util | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2215730 | Skeleton of TR 38.872 | CATT |
R4-2216137 | Further discussion on RF requirement impacts for 700800900MHz CA band combinations | vivo |
R4-2217708 | WF on CA_n5-n8 | Xiaomi |
R4-2217709 | WF on\tCA_n5-n28 | ZTE |
R4-2217710 | WF on CA_n8-n20-n28 | Skyworks |
R4-2217711 | TR 38.872 v0.2.0 | CATT |
R4-2217712 | Skeleton of TR 38.872 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2215662 | On CA_n5-n8 architectures | Apple |
R4-2216340 | Considerations on CA_n5-n8 | Qualcomm Finland RFFE Oy |
TDoc | Title | Source |
---|---|---|
R4-2215445 | CA_n5-n8 Feasibility and assumptions for UE-UE RF Requirements | Murata Manufacturing Co Ltd. |
R4-2215896 | Feasible on CA band combination of n5-n8 | ZTE Corporation |
R4-2216039 | Discussion on feasibility study for CA_n5-n8 | Xiaomi |
R4-2216136 | Further discussion on feasibility aspects for 700800900MHz CA band combinations | vivo |
R4-2216679 | CA_n5-n8 with restricted frequency range | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2215897 | RF requirements on CA band combination of n5-n8 | ZTE Corporation |
R4-2216072 | TP and discussion on CA_n5-n8 | Huawei, HiSilicon |
R4-2217715 | TP and discussion on CA_n5-n8 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215663 | On CA_n5-n28 architectures | Apple |
R4-2216345 | Considerations on CA_n5-n28 | Qualcomm Finland RFFE Oy |
TDoc | Title | Source |
---|---|---|
R4-2216040 | Discussion on feasibility study for CA_n5-n28 | Xiaomi |
R4-2216870 | CA_n5-n28 MSD for 2UL case | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2215898 | RF requirements on CA band combination of n5-n28 | ZTE Corporation |
R4-2216070 | TP and discussion on CA_n5-n28 | Huawei, HiSilicon |
R4-2217713 | TP and discussion on CA_n5-n28 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215664 | On CA_n8-n20-n28 architectures | Apple |
R4-2216346 | Considerations on CA_n8-n20-n28 | Qualcomm Finland RFFE Oy |
TDoc | Title | Source |
---|---|---|
R4-2216041 | Discussion on feasibility study for CA_n8-n20-n28 | Xiaomi |
R4-2216876 | CA_n5-n20-n28 MSD for 2UL case | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216071 | TP and discussion on CA_n8-n20-n28 | Huawei, HiSilicon |
R4-2217714 | TP and discussion on CA_n8-n20-n28 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216961 | Email discussion summary for [104-bis-e][125] FS_NR_700800900 | Moderator (CATT) |
R4-2217004 | Email discussion summary for [104-bis-e][125] FS_NR_700800900 | Moderator (CATT) |
R4-2217777 | Email discussion summary for [104-bis-e][125] FS_NR_700800900 | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R4-2215900 | TP for TR38.846_Update template for R18 PC3 basket WIDs | ZTE Corporation |
R4-2216595 | Fallbacks in 38.101 specs | Apple |
R4-2216616 | TR 38.846 v0.1.0_Study on simplification of band combination specification for NR and LTE | ZTE Corporation |
R4-2217719 | TP for TR38.846_Update template for R18 PC3 basket WIDs | ZTE |
R4-2217720 | TP and Discussion on test burden reduction | Huawei, HiSilicon |
R4-2217721 | Fallbacks in 38.101 specs | Apple |
TDoc | Title | Source |
---|---|---|
R4-2216370 | On simplification of band combination specification for NR and LTE | Nokia, Nokia Shanghai Bell |
R4-2216621 | TP for TR 38.846 on working procedure of specifying band combinations | ZTE Corporation |
R4-2217722 | TP for TR 38.846 on working procedure of specifying band combinations | ZTE |
TDoc | Title | Source |
---|---|---|
R4-2215665 | On FR1 2UL inter-band CA UE coexistence requirements | Apple |
R4-2215737 | Views on FR1 inter-band UL CA co-existence requirements | Samsung |
R4-2216043 | Discussion on 2UL inter-band CA coexistence requirements | Xiaomi |
R4-2216073 | TP and Discussion on test burden reduction | Huawei, HiSilicon |
R4-2216619 | On test burden reduction for multiple MSD in band combinations | ZTE Corporation |
R4-2216620 | TP for TR 38.846 on rules of delta TIB and RIB due to band combinations | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216962 | Email discussion summary for [104-bis-e][126] FS_SimBC | Moderator (ZTE) |
R4-2217005 | Email discussion summary for [104-bis-e][126] FS_SimBC | Moderator (ZTE) |
R4-2217716 | WF on Reduction on FR1 2UL inter-band CA coexistence | Apple |
R4-2217717 | WF on General text for the justification of Rel.18 higher power basket WIDs | Samsung, CHTTL |
R4-2217718 | WF on test burden reduction for multiple MSD in band combinations | ZTE |
R4-2217778 | Email discussion summary for [104-bis-e][126] FS_SimBC | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2215575 | Proposals on definition of FR2 multi-band BS | Nokia, Nokia Shanghai Bell |
R4-2216241 | TP for deployment scenarios | Huawei, HiSilicon |
R4-2217502 | TP for deployment scenarios | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215413 | General consideration on mmWave multi-band BS | CATT |
R4-2215576 | Discussion on possible issues on performance of wideband RF and antenna architectures | Nokia, Nokia Shanghai Bell |
R4-2215768 | FR2 Multi-band BS | Murata Manufacturing Co Ltd. |
R4-2216240 | Definition of FR2 multi-band BS | Huawei, HiSilicon |
R4-2216242 | Discussion of mmWave multi-band BS feasibility | Huawei, HiSilicon |
R4-2216243 | Study on the FR1 multi-band methods | Huawei, HiSilicon |
R4-2216397 | TP to TR 38.877: NR mm wave BS | Ericsson |
R4-2216551 | Further discussion on FR2 multi-band operation | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216891 | Email discussion summary for [104-bis-e][307] FS_NR_BS_RF_evo | Moderator (Huawei) |
R4-2217450 | WF on definition of FR2-1 multi-band BS | CATT |
R4-2217451 | WF on feasibility of FR2-1 multi-band BS | Huawei |
R4-2217452 | WF on requirements of FR2-1 multi-band BS | Nokia |
R4-2217489 | Email discussion summary for [104-bis-e][307] FS_NR_BS_RF_evo | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2215540 | Testing Considerations for Multi AoA UE RF Spherical Coverage Test Case and FR2 Demodulation | Keysight Technologies UK Ltd |
R4-2215658 | On FR2 OTA test methodology enhancements | Apple |
R4-2215703 | Discussion on full degree of rotation freedom with 2AoA | Samsung |
R4-2215711 | Views on FR2-1 RF OTA test for a device with multi-panel reception (2) | Anritsu Corporation |
R4-2216079 | Discussion on Test methods | Huawei,HiSilicon |
R4-2216114 | Discussion on FR2 OTA test methods for multi-Rx | vivo |
R4-2216169 | on the FR2 OTA Test method | Xiaomi |
R4-2216415 | Discussion on test methodology for FR2 UE with multi-Rx | Qualcomm Incorporated |
R4-2216450 | Views on FR2 OTA enhanced test method | OPPO |
R4-2216642 | Discussion on FR2 methods for UEs with multi-panel reception | ROHDE & SCHWARZ |
TDoc | Title | Source |
---|---|---|
R4-2216078 | Discussion on MU impacts for Multi-Rx test system | Huawei,HiSilicon |
R4-2216755 | On QoQZ Validation and MU for Multi-AoA Systems for Multi-Chain Operation | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2216909 | Email discussion summary for [104-bis-e][325] FS_NR_FR2_OTA_enh | Moderator (Qualcomm) |
R4-2217453 | WF on NR FR2 OTA testing enhancements | Qualcomm |
R4-2217490 | Email discussion summary for [104-bis-e][325] FS_NR_FR2_OTA_enh | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2216675 | TR 38.881 lower MSD v0.1.0 | Huawei, HiSilicon |
R4-2217723 | WF on study for lower MSD | Huawei, HiSilicon |
R4-2217725 | WF on\tFR1 4Tx UE RF requirements | Vivo |
R4-2217726 | WF on FR1 8Rx UE RF requirements | NTT DOCOMO |
TDoc | Title | Source |
---|---|---|
R4-2215377 | 4 Tx RF issues | Qualcomm Incorporated |
R4-2215381 | On international roaming possibility of CPE/FWA/vehicle/industrial devices | SoftBank Corp. |
R4-2215782 | Discussion on 4Tx UE RF requirements | LG Electronics |
R4-2215888 | Discussion on CEP/FWA/vehicle/industrial devices | ZTE Corporation |
R4-2216115 | Discussion on 4Tx UE RF requirements | vivo |
R4-2216143 | Discussion on 4Tx on for CPE FWA vehicle industrial devices | Xiaomi |
R4-2216154 | Views on assumption for CPE/FWA/vehicle/industrial devices for 4Tx and 8Rx | NTT DOCOMO INC. |
R4-2216158 | Views on 4Tx for Rel-18 RF FR1 enhancements | NTT DOCOMO INC. |
R4-2216436 | R18 Discussion on 4Tx FWA | OPPO |
R4-2216673 | Further consideration on 4Tx | Huawei, HiSilicon |
R4-2216674 | draft CR to TS 38.101-1 4Tx requirements (phase 1) | Huawei, HiSilicon |
R4-2216874 | EVM Definition for Conductive MIMO Testing | Lenovo |
R4-2216879 | EVM Definition for 4x4 UL MIMO | Lenovo |
TDoc | Title | Source |
---|---|---|
R4-2216116 | Discussion on 8Rx UE RF requirements | vivo |
R4-2216144 | Discussion on 8Rx on for CPE FWA vehicle industrial devices | Xiaomi |
R4-2216163 | Views on 8Rx for Rel-18 RF FR1 enhancements | NTT DOCOMO INC. |
R4-2216347 | 8RX UE RF requirements | Qualcomm Finland RFFE Oy |
R4-2216437 | R18 Discussion on 8Rx FWA | OPPO |
R4-2216587 | On FR1 8Rx UE RF requirements | Huawei, HiSilicon |
R4-2216872 | Discussion on enabling 8Rx for CPE/FWA/vehicle/industrial devices in FR1 | Ericsson Limited |
TDoc | Title | Source |
---|---|---|
R4-2215379 | Investigation of band combinations for MSD reduction | Qualcomm Incorporated |
R4-2215666 | Further analyses and views on MSD improvement for inter-band CA/DC | Apple |
R4-2215734 | Views on feasibility of improved MSD | Samsung |
R4-2215758 | Consideration on the lower MSD study and capability signaling | Meta Ireland |
R4-2215792 | Feasibility study on amount of MSD improvement | Nokia, Nokia Shanghai Bell |
R4-2215889 | Discussion on lower MSD for inter-band CA/ENDC | ZTE Corporation |
R4-2216117 | Analysis on improve MSD | vivo |
R4-2216145 | Discussion on lower MSD for inter-band CA/EN-DC/DC | Xiaomi |
R4-2216187 | MSD evalueation considering the high PCB isolation for CA n1-n3 | LG Electronics France |
R4-2216434 | R18 Discussion on MSD improvement | OPPO |
R4-2216676 | TP for TR 38.881 Example band combinations for lower MSD | Huawei, HiSilicon |
R4-2216776 | Further discussion on the feasibility of improving MSD | Huawei, HiSilicon |
R4-2217724 | TP for TR 38.881 Example band combinations for lower MSD | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215378 | Signalling for low MSD | Qualcomm Incorporated |
R4-2215382 | Lower MSD signalling and the effects of the introduction | Nokia, Nokia Shanghai Bell |
R4-2215481 | Discussion on lower MSD capability | CMCC |
R4-2215667 | Views on signaling for improved lower MSD | Apple |
R4-2215735 | Views on signaling for Lower MSD | Samsung |
R4-2216118 | Signaling on Lower MSD | vivo |
R4-2216146 | Discussion on lower MSD signaling for inter-band CA/EN-DC/DC | Xiaomi |
R4-2216435 | R18 Discussion on MSD improvement signalling | OPPO |
R4-2216719 | Discussion on the capability signalling design for Low MSD indication | CHTTL |
R4-2216777 | Further discussion on the feasibility of signalling for low MSD | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216963 | Email discussion summary for [104-bis-e][127] FR1_enh2_part1 | Moderator (Huawei) |
R4-2216964 | Email discussion summary for [104-bis-e][128] FR1_enh2_part2 | Moderator (Vivo) |
R4-2216965 | Email discussion summary for [104-bis-e][129] FR1_enh2_part3 | Moderator (NTT Docomo) |
R4-2217006 | Email discussion summary for [104-bis-e][127] FR1_enh2_part1 | Moderator (Huawei) |
R4-2217007 | Email discussion summary for [104-bis-e][128] FR1_enh2_part2 | Moderator (Vivo) |
R4-2217008 | Email discussion summary for [104-bis-e][129] FR1_enh2_part3 | Moderator (NTT Docomo) |
R4-2217779 | Email discussion summary for [104-bis-e][127] FR1_enh2_part1 | Moderator (Huawei) |
R4-2217780 | Email discussion summary for [104-bis-e][128] FR1_enh2_part2 | Moderator (Vivo) |
R4-2217781 | Email discussion summary for [104-bis-e][129] FR1_enh2_part3 | Moderator (NTT Docomo) |
TDoc | Title | Source |
---|---|---|
R4-2216348 | TR38.891 v 0.1.0 for NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 | Xiaomi,Nokia |
R4-2217727 | WF on BC in RRC_INACTIVE and initial access | Nokia |
R4-2217728 | TR38.891 v 0.1.0 for NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 | Xiaomi,Nokia |
R4-2217729 | WF on UL 256 QAM | Xiaomi |
R4-2217730 | TP for TR 38.891 on link level simulation assumptions for FR2 UL 256QAM | Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2215577 | Link level simulation results for FR2-1 UL 256QAM | Nokia, Nokia Shanghai Bell |
R4-2215578 | Proposals on UE RF requirements for FR2-1 UL 256QAM | Nokia, Nokia Shanghai Bell |
R4-2215920 | Link performance on FR2-1 UL 256 QAM | LG Electronics France |
R4-2216128 | Feasibility evaluation of FR2 UL 256 QAM | vivo |
R4-2216245 | Simulation results for UL 256QAM | Huawei, HiSilicon |
R4-2216251 | UL 256-QAM simulations for FR2-1 | Sony |
R4-2216349 | TP for TR 38.891 on link level simulation assumptions for FR2 UL 256QAM | Xiaomi |
R4-2216350 | Discussion on UL 256QAM | Xiaomi |
R4-2216426 | Discussion on FR2 UL 256qam results | ZTE Corporation |
R4-2216584 | FR2-1 UL 256QAM: EVM testing using PTRS | Anritsu Limited |
R4-2216784 | On enabling FR2 UL256QAM | Qualcomm Incorporated |
R4-2216873 | Discussion on enabling the support for 256QAM on UL for FR2-1 | Ericsson Limited |
TDoc | Title | Source |
---|---|---|
R4-2215636 | LS on extending beam lock function for testing in initial access | Apple |
R4-2216252 | Views on Beam correspondence for initial access | Sony, Ericsson |
R4-2216785 | On initial access beam correspondence | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215479 | beam correspondence requirement for initial access state | CMCC |
R4-2215511 | Beam correspondence requirement applicability | Nokia, Nokia Shanghai Bell |
R4-2215630 | Further consideration on BC requirement applicability for IA/RA-SDT/CD-SDT | Apple |
R4-2215854 | On beam correspondence requirements applicability in RRC_IDLE or RRC_INACTIVE for Rel-18 NR FR2 | Huawei, HiSilicon |
R4-2216129 | Discussion on requiremnet applicability for beam correspondence | vivo |
R4-2216351 | Discussion on beam correspondence requirements for RRC_INACTIVE and initial access | Xiaomi |
R4-2216438 | R18 Discussion on FR2 beam correspondence requirements in initial access | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215512 | UE beam type and DRX implications | Nokia, Nokia Shanghai Bell |
R4-2215631 | Discussion on UE beam type and DRX implications | Apple |
R4-2215855 | On UE beam Type for Rel-18 Inactive Beam Correspondence | Huawei, HiSilicon |
R4-2216130 | Discussion on beam type and UE requiremnet for beam correspondence during non-RRC_CONNECTED state | vivo |
R4-2216439 | R18 Discussion on FR2 beam type in initial access | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215480 | beam correspondence test issues for initial access state | CMCC |
R4-2215513 | Beam Correspondence Test Issues | Nokia, Nokia Shanghai Bell |
R4-2215632 | discussion on Beam correspondence test issues | Apple |
R4-2215702 | FR2 beam correspondence requirement and test for random access | Samsung |
R4-2215856 | On beam correspondence test issues in RRC_IDLE or RRC_INACTIVE for Rel-18 NR FR2 | Huawei, HiSilicon |
R4-2216131 | Discussion on test related issue of beam correspondence | vivo |
R4-2216440 | R18 Discussion on FR2 beam correspondence test in initial access | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2216966 | Email discussion summary for [104-bis-e][130] FR2_enh_req_Ph3_part1 | Moderator (Nokia) |
R4-2216967 | Email discussion summary for [104-bis-e][131] FR2_enh_req_Ph3_part2 | Moderator (Xiaomi) |
R4-2217009 | Email discussion summary for [104-bis-e][130] FR2_enh_req_Ph3_part1 | Moderator (Nokia) |
R4-2217010 | Email discussion summary for [104-bis-e][131] FR2_enh_req_Ph3_part2 | Moderator (Xiaomi) |
R4-2217782 | Email discussion summary for [104-bis-e][130] FR2_enh_req_Ph3_part1 | Moderator (Nokia) |
R4-2217783 | Email discussion summary for [104-bis-e][131] FR2_enh_req_Ph3_part2 | Moderator (Xiaomi) |
TDoc | Title | Source |
---|---|---|
R4-2216253 | Views on multi-Rx chain DL reception in FR2 | Sony, Ericsson |
R4-2216589 | On UE RF requirement for FR2 multi-Rx chain DL reception | Huawei, HiSilicon |
R4-2216875 | On Defining Coverage Requirements for Multi-Rx Chain Downlink Reception | Lenovo |
R4-2217731 | WF on FR2 UE RF requirements for 2AoA DL Rx | Vivo |
R4-2217732 | WF on System parameter assumption and UE architecture and test setup | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215579 | Proposals on consideration of UE architecture for FR2-1 multi-Rx chain DL reception | Nokia, Nokia Shanghai Bell |
R4-2215620 | UE implementation assumptions for NR FR2 multi-Rx chain DL reception | Apple |
R4-2215701 | System assumption and UE assumption for FR2 simultaneous DL reception from different directions | Samsung |
R4-2215778 | Discussion for FR2 multi-Rx chain DL reception | Murata Manufacturing Co Ltd. |
R4-2216125 | Discussion on UE implementation assumption of multi-Rx DL reception | vivo |
R4-2216352 | Discussion on UE architecture to support simultaneous DL reception | Xiaomi |
R4-2216445 | Considerations on the UE assumptions for FR2 multi-Rx chain DL reception | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215541 | Multi-Rx Chain DL Spherical Coverage Test Proposal | Keysight Technologies UK Ltd |
R4-2215580 | Proposal on AoA pairs on testing for FR2-1 multi-Rx chain DL reception | Nokia, Nokia Shanghai Bell |
R4-2216126 | Discussion on test setup of multi-Rx DL reception | vivo |
R4-2216444 | Considerations on the AoA pairs for the RF requirement of multi-Rx chain | OPPO |
R4-2216585 | Views on AoA pairs for FR2 Multi-Rx chain DL reception | Anritsu Limited |
R4-2216787 | On test setup for UE RF requirements for 2AoA FR2 DL MIMO | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215581 | Proposal on spherical coverage requirements for FR2-1 multi-Rx chain DL reception | Nokia, Nokia Shanghai Bell |
R4-2215621 | RF requirement for NR FR2 multi-Rx chain DL reception | Apple |
R4-2215781 | Discussion on UE RF requirements for simultaneous DL reception | LG Electronics |
R4-2216127 | Discussion on RF requirement for multi-Rx DL reception | vivo |
R4-2216353 | Discussion on UE RF requirements supporting simultaneous DL reception | Xiaomi |
R4-2216786 | On UE RF requirements for 2AoA FR2 DL MIMO | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215710 | Discussions on FR2 multi Rx chain DL reception | NTT DOCOMO, INC. |
R4-2217246 | WF on RRM impacts and general aspects for multi-Rx | Vivo |
R4-2217247 | WF on L1 measurements, beam sweeping factors and simultaneous reception | Qualcomm |
R4-2217248 | WF on TCI state switching for multi-RX chain DL reception | Ericsson |
R4-2217587 | WF on L1 measurements, beam sweeping factors and simultaneous reception | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2215360 | Discussion on FR2 multi Rx chain RRM impacts and general aspects | Intel Corporation |
R4-2215462 | on the multi-RX chain general aspects | Xiaomi |
R4-2215622 | General aspects for NR FR2 multi-Rx chain DL reception | Apple |
R4-2215720 | Discussion on general aspects for FR2 multi-Rx chain DL reception | CMCC |
R4-2215759 | Discussion on simultaneous DL reception from different directions for general issues | MediaTek Inc. |
R4-2215803 | Discussion on general aspects of RRM for simultaneous DL reception from different directions | LG Electronics Inc. |
R4-2215812 | Discussion on general requirements for FR2_multiRX_DL | OPPO |
R4-2215867 | Further analysis on RRM impacts and general aspects | vivo |
R4-2216285 | Discussion on RRM general impacts for R18 FR2 multi-Rx chain DL reception | Huawei, HiSilicon |
R4-2216474 | Discussion on general aspects on RRM requirements for simultaneous DL reception from different directions | ZTE Corporation |
R4-2216578 | General considerations on RRM requirements for multi-RX RRM | Nokia, Nokia Shanghai Bell |
R4-2216713 | Further Analysis of RRM requirement impacts for simultaneous DL reception from different directions | Samsung |
R4-2216824 | Discussion on scenarios for simultaneous DL reception from different directions | Ericsson |
R4-2216866 | Impacts on RRM to support FR2 multi-Rx chain based 4 layer DL reception from multi-TRP | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215464 | on the multi-RX chain L3 measurement | Xiaomi |
R4-2215623 | On L3 measurements for NR FR2 multi-Rx chain DL reception | Apple |
R4-2215722 | Discussion on L3 measurement for FR2 multi-Rx chain DL reception | CMCC |
R4-2215760 | Discussion on simultaneous DL reception from different directions for L3 measurement | MediaTek Inc. |
R4-2215804 | Discussion on L3 measurement related RRM for simultaneous DL reception from different directions | LG Electronics Inc. |
R4-2215813 | Discussion on L3 requirements for FR2_multiRX_DL | OPPO |
R4-2215868 | On L3 measurement for multi-Rx chain | vivo |
R4-2216286 | Discussion on L3 measurement impacts for R18 FR2 multi-Rx chain DL reception | Huawei, HiSilicon |
R4-2216476 | Discussion on L3 part RRM requirements for simultaneous DL reception from different directions | ZTE Corporation |
R4-2216579 | Discussion on RRM L3 enhancements for multi Rx DL in FR2 | Nokia, Nokia Shanghai Bell |
R4-2216825 | Discussion on L3 measurements and procedures | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215361 | Discussion on RRM impacts for L1 measurement based on FR2 multi Rx chain | Intel Corporation |
R4-2215463 | on the multi-RX chain L1 measurement | Xiaomi |
R4-2215624 | On L1 measurements for NR FR2 multi-Rx chain DL reception | Apple |
R4-2215721 | Discussion on L1 measurement for FR2 multi-Rx chain DL reception | CMCC |
R4-2215761 | Discussion on simultaneous DL reception from different directions for L1 measurement | MediaTek Inc. |
R4-2215805 | Discussion on L1 measurement related to RRM for simultaneous DL reception from different | LG Electronics Inc. |
R4-2215814 | Discussion on L1 requirements for FR2_multiRX_DL | OPPO |
R4-2215869 | On L1 measurement for multi-Rx chain | vivo |
R4-2216287 | Discussion on L1 measurement impacts for R18 FR2 multi-Rx chain DL reception | Huawei, HiSilicon |
R4-2216475 | Discussion on L1 part RRM requirements for simultaneous DL reception from different directions | ZTE Corporation |
R4-2216580 | Discussion on RRM L1 enhancements for multi Rx DL in FR2 | Nokia, Nokia Shanghai Bell |
R4-2216826 | Discussion on L1 measurements and procedures | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215362 | Discussion on RRM impacts for TCI state switching based on FR2 multi Rx chain | Intel Corporation |
R4-2215465 | on the multi-RX chain TCI state switching | Xiaomi |
R4-2215762 | Discussion on simultaneous DL reception from different directions for TCI state switching | MediaTek Inc. |
R4-2215806 | Discussion on TCI state switching for simultaneous DL reception from different directions | LG Electronics Inc. |
R4-2215815 | Discussion on TCI state switching for FR2_multiRX_DL | OPPO |
R4-2215870 | On TCI state switching for multi-Rx chain | vivo |
R4-2216277 | Discussion RRM requirements of TCI state switching for multi-Rx | Huawei, HiSilicon |
R4-2216477 | Discussion on TCI state related RRM requirements for simultaneous DL reception from different directions | ZTE Corporation |
R4-2216581 | Discussion on RRM TCI State Switching for multi Rx DL in FR2 | Nokia, Nokia Shanghai Bell |
R4-2216827 | Discussion on active TCI state requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216922 | Email discussion summary for [104-bis-e][211] FR2_multiRx_RRM_part1 | Moderator (Vivo) |
R4-2216923 | Email discussion summary for 1[04-bis-e][212] FR2_multiRx_RRM_part2 | Moderator (Qualcomm) |
R4-2216924 | Email discussion summary for [104-bis-e][213] FR2_multiRx_RRM_part3 | Moderator (Ericsson) |
R4-2216968 | Email discussion summary for 1[04-bis-e][132] FR2_multiRx_UERF_part1 | Moderator (Qualcomm) |
R4-2216969 | Email discussion summary for [104-bis-e][133] FR2_multiRx_UERF_part2 | Moderator (Apple) |
R4-2217011 | Email discussion summary for 1[04-bis-e][132] FR2_multiRx_UERF_part1 | Moderator (Qualcomm) |
R4-2217012 | Email discussion summary for [104-bis-e][133] FR2_multiRx_UERF_part2 | Moderator (Apple) |
R4-2217144 | Email discussion summary for [104-bis-e][211] FR2_multiRx_RRM_part1 | Moderator (Vivo) |
R4-2217145 | Email discussion summary for 1[04-bis-e][212] FR2_multiRx_RRM_part2 | Moderator (Qualcomm) |
R4-2217146 | Email discussion summary for [104-bis-e][213] FR2_multiRx_RRM_part3 | Moderator (Ericsson) |
R4-2217784 | Email discussion summary for [104-bis-e][132] FR2_multiRx_UERF_part1 | Moderator (Qualcomm) |
R4-2217785 | Email discussion summary for [104-bis-e][133] FR2_multiRx_UERF_part2 | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2215599 | Updated Work plan for R18 eFeRRM | Apple |
R4-2217249 | WF on R18 eFeRRM - FR2 SCell activation enhancement | Apple |
R4-2217250 | WF on RRM Core requirements for FR1-FR1 NR-DC | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215456 | Discussion on FR2 SCell activation delay reduction | Xiaomi |
R4-2215801 | Discussion on FR2 SCell activation delay reduction | LG Electronics Inc. |
R4-2215807 | Discussions on FR2 SCell Activation delay requirements | NTT DOCOMO, INC. |
R4-2216744 | Discussion on RRM requirements for FR2 unknown Scell activation delay reduction | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215356 | Discussion on L3 part enhancement for FR2 SCell activation | Intel Corporation |
R4-2215530 | Discussion on A-TRS based unknown SCell activation | China Telecom |
R4-2215600 | On L3 part enhancement for FR2 SCell activation | Apple |
R4-2215719 | Discussion on L3 part enhancement for FR2 SCell activation | CMCC |
R4-2215785 | L3 part enhancement on FR2 SCell activation delay reduction | Nokia, Nokia Shanghai Bell |
R4-2215809 | Discussion on L3 part enhancement for FR2 Scell activation delay reduction | OPPO |
R4-2215865 | Discussion on L3 part enhancement for FR2 SCell activation | vivo |
R4-2216272 | Discussion on L3 enhancement for FR2 SCell activation delay reduction | Huawei, HiSilicon |
R4-2216480 | Discussion on the L3 part enhancement of RRM requirements for FR2 SCell activation delay reduction | ZTE Corporation |
R4-2216758 | Discussion on L3 part enhancement for FR2 SCell activation | MediaTek inc. |
R4-2216828 | Discussion on L3 part enhancement for FR2 SCell activation | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215357 | Discussion on L1 part enhancement for FR2 SCell activation | Intel Corporation |
R4-2215601 | On L1 part enhancement for FR2 SCell activation | Apple |
R4-2215718 | Discussion on L1 part enhancement for FR2 SCell activation | CMCC |
R4-2215786 | L1 part enhancement on FR2 SCell activation delay reduction | Nokia, Nokia Shanghai Bell |
R4-2215810 | Discussion on L1 part enhancement for FR2 Scell activation delay reduction | OPPO |
R4-2215866 | Discussion on L1 part enhancement for FR2 SCell activation | vivo |
R4-2216273 | Discussion on L1 enhancement for FR2 SCell activation delay reduction | Huawei, HiSilicon |
R4-2216479 | Discussion on the L1 part enhancement of RRM requirements for FR2 SCell activation delay reduction | ZTE Corporation |
R4-2216759 | Discussion on L1 part enhancement for FR2 SCell activation | MediaTek inc. |
R4-2216829 | Discussion on L1 part enhancement for FR2 SCell activation | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215531 | Discussion on SCell activation without SSB in inter-band scenario | China Telecom |
R4-2215787 | Other enhancements on FR2 SCell activation delay reduction | Nokia, Nokia Shanghai Bell |
R4-2216274 | Discussion on FR2 SCell activation delay reduction | Huawei, HiSilicon |
R4-2216478 | Discussion on other aspects of RRM requirements enhancement for FR2 SCell activation delay reduction | ZTE Corporation |
R4-2216760 | Discussion on other potential enhancement for FR2 SCell activation | MediaTek inc. |
R4-2216830 | Discussion on Other potential enhancement for FR2 SCell activation | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215355 | Discussion on FR1-FR1 NR-DC | Intel Corporation |
R4-2215466 | Discussion on RRM core requirements for FR1-FR1 NR-DC. | Xiaomi |
R4-2215602 | On RRM requirements for FR1-FR1 NR-DC | Apple |
R4-2215717 | Discussion on RRM requirements for FR1-FR1 NR-DC | CMCC |
R4-2215763 | Discussion on R18 RRM for FR1-FR1 NR-DC | MediaTek Inc. |
R4-2215811 | Discussion on RRM requirements for FR1-FR1 NR-DC | OPPO |
R4-2215837 | discussion on FR1-FR1 NR-DC | Nokia, Nokia Shanghai Bell |
R4-2215864 | Further discussion on FR1-FR1 NR-DC requirement | vivo |
R4-2216275 | Discussion RRM requirements for FR1-FR1 NR-DC | Huawei, HiSilicon |
R4-2216341 | Discussion on RRM core requirements for FR1-FR1 NR-DC | Ericsson |
R4-2216745 | Discussion on RRM requirements for remaining issues about FR1+FR1 NR-DC | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216925 | Email discussion summary for 1[04-bis-e][214] NR_RRM_enh3_part1 | Moderator (Apple) |
R4-2216926 | Email discussion summary for 1[04-bis-e][215] NR_RRM_enh3_part2 | Moderator (OPPO) |
R4-2217147 | Email discussion summary for 1[04-bis-e][214] NR_RRM_enh3_part1 | Moderator (Apple) |
R4-2217148 | Email discussion summary for 1[04-bis-e][215] NR_RRM_enh3_part2 | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R4-2215367 | Discussion on RRM requirements for pre-configured MGs, multiple concurrent MGs and NCSG | Intel Corporation |
R4-2215426 | Discussion on RRM requirements for combination of pre-MG, concurrent MGs and NCSG | CATT |
R4-2215457 | RRM requirement for the combination of concurrent gaps, pre-MG and NCSG | Xiaomi |
R4-2215610 | On R18 gap enhancement - joint configuration of Pre-MG, NCSG and concurrent gaps | Apple |
R4-2215714 | Discussion on combination of pre-configured MGs, multiple concurrent MGs and NCSG | CMCC |
R4-2215821 | Discussion on joint requirements for PreMG, concurrent MGs and NCSG | OPPO |
R4-2215966 | Considerations on pre-configured MGs, multiple concurrent MGs and NCSG | vivo |
R4-2216336 | Discussion on joint working of eMG features | Huawei, HiSilicon |
R4-2216460 | Discussion on PreMG, ConMG, NCSG | Ericsson |
R4-2216482 | Discussion on RRM requirements for joint considerations between pre-MG, concurrent MG and NCSG for NR and MR-DC | ZTE Corporation |
R4-2216582 | Discussion on requirements for concurrent measurement gaps, pre-configured gaps and NCSG | Nokia, Nokia Shanghai Bell |
R4-2216723 | On joint requirements for Rel-17 measurement gap enhancements | Qualcomm Incorporated |
R4-2216737 | RRM core requirements for pre-configured MGs, multiple concurrent MGs and NCSG | MediaTek inc. |
R4-2217251 | WF on further enhancements on measurement gaps and measurements without gaps | MediaTek inc. |
R4-2217252 | WF on Measurement without gaps for UEs reporting NeedForGapsInfoNR | Intel |
R4-2217253 | WF on inter-RAT measurement without gap | Intel |
TDoc | Title | Source |
---|---|---|
R4-2216746 | Discussion on RRM requirements for measurement without gap | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215368 | Discussion on measurements without gaps when UE reporting NFG | Intel Corporation |
R4-2215427 | Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR | CATT |
R4-2215467 | Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR | Xiaomi |
R4-2215611 | On R18 gap enhancement - NeedForGap | Apple |
R4-2215715 | Discussion on measurements without gaps for UEs reporting NeedForGapsInfoNR | CMCC |
R4-2215822 | Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR | OPPO |
R4-2215967 | Considerations on measurement without gaps for UEs reporting NeedForGapsInfoNR | vivo |
R4-2216337 | Discussion on requirements for NeedForGaps | Huawei, HiSilicon |
R4-2216461 | Discussion on NeedForGaps measurement | Ericsson |
R4-2216484 | Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR | ZTE Corporation |
R4-2216583 | Discussion on RRM requirements without gaps for MG_enh2 | Nokia, Nokia Shanghai Bell |
R4-2216738 | Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2215369 | Discussion on inter-RAT measurement without gaps | Intel Corporation |
R4-2215428 | Discussion on RRM requirements for Inter-RAT measurement without gap | CATT |
R4-2215468 | Discussion on RRM requirements for inter-RAT measurement without gap | Xiaomi |
R4-2215612 | On R18 gap enhancement - inter-RAT measurement with gap | Apple |
R4-2215716 | Discussion on inter-RAT measurements without gaps | CMCC |
R4-2215823 | Discussion on RRM requirements for interRAT measurements without gaps | OPPO |
R4-2215968 | Considerations on inter-RAT measurement without gap | vivo |
R4-2216338 | Discussion on inter-RAT MG-less measurement in feMG | Huawei, HiSilicon |
R4-2216462 | Discussion on Inter-RAT measurement without gap | Ericsson |
R4-2216483 | Discussion on RRM requirements for inter-RAT measurement without gap | ZTE Corporation |
R4-2216739 | Discussion on inter-rat measurements | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2216927 | Email discussion summary for 1[04-bis-e][216] NR_MG_enh2_part1 | Moderator (MediaTek) |
R4-2216928 | Email discussion summary for [104-bis-e][217] NR_MG_enh2_part2 | Moderator (Intel) |
R4-2217149 | Email discussion summary for 1[04-bis-e][216] NR_MG_enh2_part1 | Moderator (MediaTek) |
R4-2217150 | Email discussion summary for [104-bis-e][217] NR_MG_enh2_part2 | Moderator (Intel) |
TDoc | Title | Source |
---|---|---|
R4-2215329 | Architecture enabling 4Rx for non-collocated overlapping bands | Skyworks Solutions Inc. |
R4-2215629 | Further consideration on intra-band non-collocated CA/EN-DC | Apple |
R4-2215673 | Issues for Non-collocated Deployments with 4Layers per CC | Qualcomm Incorporated |
R4-2215736 | Views on UE RF aspect for non-collocated EN-DC, NR-CA deployment | Samsung |
R4-2215790 | Discussion on the power imbalance requirement for Type-2 non-collocated intra-band NR-CA | KDDI Corporation |
R4-2215827 | Clarifications on 2-Layer UE architecture Baseline | Huawei Technologies France |
R4-2215890 | Further discussion on non-collocated EN-DC and NR-CA | ZTE Corporation |
R4-2216132 | Discussion on feasibility of 4-layer MIMO under non-collocated deployment | vivo |
R4-2216425 | On required arrival time difference between CCs | Ericsson |
R4-2217733 | WF on NonCol_intraB_ENDC_NR_CA for NR-CA Type-2 UE | KDDI |
R4-2217734 | WF on NonCol_intraB_ENDC_NR_CA for NR-CA and EN-DC New Type UE | KDDI |
TDoc | Title | Source |
---|---|---|
R4-2216970 | Email discussion summary for 1[04-bis-e][134] NonCol_intraB | Moderator (KDDI) |
R4-2217013 | Email discussion summary for 1[04-bis-e][134] NonCol_intraB | Moderator (KDDI) |
R4-2217786 | Email discussion summary for [104-bis-e][134] NonCol_intraB | Moderator (KDDI) |
TDoc | Title | Source |
---|---|---|
R4-2216708 | Work plan for Enhanced NR support for high speed train scenario in FR2 | Samsung |
R4-2217029 | Work plan for Enhanced NR support for high speed train scenario in FR2 | Samsung |
R4-2217735 | WF on NR FR2 HST UE RF | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215857 | On CA RF requirements for NR FR2 HST enhancement | Huawei, HiSilicon |
R4-2215858 | Draft CR for power class 6 intra-band CA requirements | Huawei, HiSilicon |
R4-2216402 | UE RF requirements or HST FR2 CA | Ericsson |
R4-2216709 | Enhanced NR Support for FR2 HST on RF requirements for intra-band CA | Samsung |
R4-2217030 | Draft CR for power class 6 intra-band CA requirements | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215859 | On Multi-panel RF requirements for NR FR2 HST enhancement | Huawei, HiSilicon |
R4-2216710 | On RF requirement for simultaneous multi-panel operation for FR2 PC6 UE | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215552 | On Tunnel Deployment and UL Timing Adjustment in HST FR2 Enhanced | Nokia, Nokia Shanghai Bell |
R4-2215700 | R18 FR2 HST enhancement core requirement scope | Qualcomm Israel Ltd. |
R4-2216009 | Discussion on reference tunnel deployment scenario | Huawei,HiSilicon |
R4-2216403 | Tunnel scenario for FR2 HST | Ericsson |
R4-2216711 | Study on reference tunnel deployment scenario and UL timing adjustment solution | Samsung |
R4-2217254 | WF on tunnel deployment and UL timing adjustment for FR2 HST enhancement | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215460 | Discussion on RRM requirements for FR2 HST | Xiaomi |
R4-2215553 | On RRM Core Requirements in HST FR2 Enhanced | Nokia, Nokia Shanghai Bell |
R4-2215712 | Discussion on FR2 HST RRM enhancement for CA scenario | CMCC |
R4-2215824 | Discussion on RRM requirements for FR2 HST | OPPO |
R4-2216311 | Discussion on FR2 eHST impact on RRM | Huawei, HiSilicon |
R4-2216506 | Requirements for CA in HST FR2 | Ericsson |
R4-2216712 | Analysis on RRM core requirement impact for FR2 HST enhancement | Samsung |
R4-2217255 | WF on other RRM core requirement impacts for FR2 HST enhancement | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2216929 | Email discussion summary for [104-bis-e][218] NR_HST_FR2_enh_RRM | Moderator (Samsung) |
R4-2216971 | Email discussion summary for [104-bis-e][135] NR_HST_FR2_enh_UERF | Moderator (Samsung) |
R4-2217014 | Email discussion summary for [104-bis-e][135] NR_HST_FR2_enh_UERF | Moderator (Samsung) |
R4-2217151 | Email discussion summary for [104-bis-e][218] NR_HST_FR2_enh_RRM | Moderator (Samsung) |
R4-2217787 | Email discussion summary for [104-bis-e][135] NR_HST_FR2_enh_UERF | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R4-2215335 | TP for ATG TR 38.876 skeleton | CMCC |
R4-2215504 | Updated Work plan on Rel-18 ATG | CMCC |
R4-2215633 | Discussion on ATG general aspects | Apple |
R4-2216398 | ATG general aspects | Ericsson |
R4-2217736 | WF on FR1 co-existence evaluation for ATG | CMCC |
R4-2217737 | TP for TR 38.876 to capture some agreements on ATG coexistence study | Huawei, HiSilicon |
R4-2217738 | WF on ATG terminal RF requirement | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215386 | Further discussion on ATG co-existence simulation assumption | CATT |
R4-2215482 | ATG coexistence simulation assumption | CMCC |
R4-2215940 | Discussion on FR1 ATG co-existence evaluation | LG Electronics UK |
R4-2216067 | Discussion on coexistence simulation assumption for ATG scenario | Huawei, HiSilicon |
R4-2216069 | TP for TR 38.876 to capture some agreements on ATG coexistence study | Huawei, HiSilicon |
R4-2216399 | ATG co-existence simulation parameters | Ericsson |
R4-2216417 | Coexistence scenarios of Air-to-ground network for NR | Qualcomm Incorporated |
R4-2216538 | Discussion on coexistence evaluation for ATG network | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215483 | ATG UE RF requirement | CMCC |
R4-2215634 | Further discussion on ATG UE requirement | Apple |
R4-2216068 | Discussion on UE requirements for ATG scenario | Huawei, HiSilicon |
R4-2216401 | ATG UE requirements | Ericsson |
R4-2216416 | Discussion on UE RF requirements for ATG | Qualcomm Incorporated |
R4-2216539 | Further discussion on ATG UE RF requirements | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215414 | General consideration on BS RF core requirements for ATG network for NR | CATT |
R4-2215508 | ATG BS classes, types and requirements | CMCC |
R4-2216052 | Discussion on ATG BS type | Huawei, Hisilicon |
R4-2216053 | TP for TR 38.876 | Huawei, Hisilicon |
R4-2216400 | ATG BS requirements | Ericsson |
R4-2216540 | Further discussion on ATG BS RF requirements | ZTE Corporation |
R4-2217504 | TP for TR 38.876 | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
R4-2215396 | Further discussion on Rel-18 ATG RRM | CATT |
R4-2215505 | Discussion on RRM requirements for ATG | CMCC |
R4-2215635 | Further discussion on RRM requirement for ATG | Apple |
R4-2215937 | Discussion on RRM core requirements for ATG UE | LG Electronics UK |
R4-2216276 | Discussion on RRM requirements for ATG | Huawei, HiSilicon |
R4-2216481 | Discussion on RRM requirements for air-to-ground network | ZTE Corporation |
R4-2216769 | Discussions on A2G RRM requirements | Ericsson |
R4-2217256 | WF on NR ATG RRM core requirements | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2216892 | Email discussion summary for [104-bis-e][308] NR_ATG_BSRF | Moderator (ZTE) |
R4-2216930 | Email discussion summary for 1[04-bis-e][219] NR_ATG_RRM | Moderator (China Mobile) |
R4-2216972 | Email discussion summary for [104-bis-e][136] NR_ATG_UERF_part1 | Moderator (China Mobile) |
R4-2216973 | Email discussion summary for [104-bis-e][137] NR_ATG_UERF_part2 | Moderator (Huawei) |
R4-2217015 | Email discussion summary for [104-bis-e][136] NR_ATG_UERF_part1 | Moderator (China Mobile) |
R4-2217016 | Email discussion summary for [104-bis-e][137] NR_ATG_UERF_part2 | Moderator (Huawei) |
R4-2217152 | Email discussion summary for 1[04-bis-e][219] NR_ATG_RRM | Moderator (China Mobile) |
R4-2217454 | WF on ATG BS RF requirements | ZTE |
R4-2217491 | Email discussion summary for [104-bis-e][308] NR_ATG_BSRF | Moderator (ZTE) |
R4-2217788 | Email discussion summary for [104-bis-e][136] NR_ATG_UERF_part1 | Moderator (China Mobile) |
R4-2217789 | Email discussion summary for [104-bis-e][137] NR_ATG_UERF_part2 | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2215323 | On the work scope of CA and RedCap | Huawei Tech.(UK) Co.. Ltd |
R4-2215656 | On TRP TRS requirement development prioritization | Apple |
R4-2216103 | Workplan of Rel-18 TRP TRS WI | vivo |
R4-2216104 | TR 38.870 Skeleton for enhanced TRP TRS test methods | vivo |
R4-2216105 | LS on 3GPP NR TRP TRS OTA requirements | vivo |
R4-2216473 | General views on Rel-18 TRP TRS OTA WI | CAICT |
R4-2217455 | Workplan of Rel-18 TRP TRS WI | vivo |
R4-2217456 | TR 38.870 Skeleton for enhanced TRP TRS test methods | vivo |
R4-2217457 | LS on 3GPP NR TRP TRS OTA requirements | vivo |
TDoc | Title | Source |
---|---|---|
R4-2215324 | On TRP Measurement under TxD | Huawei Tech.(UK) Co.. Ltd |
R4-2215653 | On TRP TRS methodology enhancements | Apple |
R4-2215654 | LS on the availability of wrist phantoms for OTA testing of wearable devices | Apple |
R4-2215704 | Initial discussion of TRP TRS on NR 2Tx UE | Samsung |
R4-2216106 | Discussion on Anechoic Chamber test methodology | vivo |
R4-2216172 | on the Anechoic chamber test methodology | Xiaomi |
R4-2216414 | Discussion on enhancement of UE TRP and TRS | Qualcomm Incorporated |
R4-2216446 | Considerations on TRPTRS test methodology for 2Tx UE | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215322 | on test methodology for reverberation chambers | Huawei Tech.(UK) Co.. Ltd |
R4-2215655 | On reverberation chamber harmonization with the reference methodology | Apple |
R4-2216107 | Discussion on Reverberation Chamber test methodology | vivo |
R4-2216173 | on the Reverberation chamber test methodology | Xiaomi |
R4-2216447 | For reverberation chamber test methodology | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215320 | MU for Reverberation Chambers and BHH | Huawei Tech.(UK) Co.. Ltd |
R4-2216108 | Discussion on MU work management | vivo |
R4-2216110 | LS to RAN5 on MU work of Rel-18 FR1 TRP TRS WI | vivo |
R4-2217458 | LS to RAN5 on MU work of Rel-18 FR1 TRP TRS WI | vivo |
TDoc | Title | Source |
---|---|---|
R4-2215539 | Test Time Reduction using Coarser TRP/TRS Measurement Grids | Keysight Technologies UK Ltd |
R4-2216109 | Views on testing time reduction methodologies | vivo |
TDoc | Title | Source |
---|---|---|
R4-2216910 | Email discussion summary for [104-bis-e][326] NR_FR1_TRP_TRS_enh | Moderator (Vivo) |
R4-2217459 | WF on FR1 TRP TRS enhancement | vivo |
R4-2217492 | Email discussion summary for [104-bis-e][326] NR_FR1_TRP_TRS_enh | Moderator (Vivo) |
TDoc | Title | Source |
---|---|---|
R4-2215542 | On FR2 Requirements Framework and Correlation between Simulations and Measurements | Keysight Technologies UK Ltd |
R4-2216357 | Work plan for Rel-18 NR MIMO OTA WI | CAICT |
R4-2217460 | Work plan for Rel-18 NR MIMO OTA WI | CAICT |
TDoc | Title | Source |
---|---|---|
R4-2215657 | On FR2 MIMO OTA test methodology enhancement | Apple |
R4-2216077 | Discussion on FR2 MIMO OTA test methodology enhancement | Huawei,HiSilicon |
R4-2216111 | Discussions on FR2 MIMO OTA enhancement | vivo |
R4-2216171 | on the FR2 MIMO OTA test methodology enhancement | Xiaomi |
R4-2216359 | Views on the framework for FR2 MIMO OTA requirements | CAICT |
R4-2216413 | Discussion on FR2 MIMO OTA requirements | Qualcomm Incorporated |
R4-2216448 | Views on the framework for FR2 MIMO OTA requirement development | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2215321 | on MIMO OTA tests for tablets and smartphones in browsing mode | Huawei Tech.(UK) Co.. Ltd |
R4-2215705 | Necessity and feasibility of hand phantom MIMO OTA test method | Samsung |
R4-2216112 | Discussions on FR1 MIMO OTA enhancement | vivo |
R4-2216170 | on the FR1 MIMO OTA test methodology enhancement | Xiaomi |
R4-2216358 | Discussion on FR1 MIMO OTA testing for hand phantom browsing mode | CAICT |
R4-2216449 | FR1 MIMO OTA in browsing mode | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2216113 | Views on Rel-18 MIMO OTA MU work handling | vivo |
TDoc | Title | Source |
---|---|---|
R4-2216911 | Email discussion summary for [104-bis-e][327] NR_MIMO_OTA_enh | Moderator (CAICT) |
R4-2217461 | WF on MIMO OTA enhancement | CAICT |
R4-2217501 | Email discussion summary for [104-bis-e][327] NR_MIMO_OTA_enh | Moderator (CAICT) |
TDoc | Title | Source |
---|---|---|
R4-2216166 | on the regulation study of UE EMC | Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2216168 | Rel-18 UE EMC work plan | Xiaomi |
R4-2216488 | BS EMC enhancements - Work Plan proposal | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215731 | Discussion on EMC BS enhancement R18 | ZTE Corporation |
R4-2215958 | Discussion of BS EMC Enhancement for NR and LTE | Ericsson |
R4-2215959 | Proposal for Optimization of EMC Test Configurations | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216167 | on the study phase of UE EMC | Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2216893 | Email discussion summary for [104-bis-e][309] NR_LTE_EMC_enh | Moderator (Ericsson) |
R4-2217462 | WF on principles for BS EMC enhancements | Ericsson |
R4-2217463 | WF on continuation of study phase for UE EMC enhancements | Xiaomi |
R4-2217493 | Email discussion summary for [104-bis-e][309] NR_LTE_EMC_enh | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2215384 | Further discussion of the interference modelling for duplex evolution SLS | CATT |
R4-2216200 | General considerations for the study of sub-band full-duplex (SBFD) in RAN4 | Nokia, Nokia Shanghai Bell |
R4-2216406 | On general and deployment considerations for SBFD | Ericsson |
R4-2216542 | Further discussion on reply LS for full duplex BS | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216836 | Duplex enhancements UE-UE CLI modelling remaining aspects | MediaTek (Chengdu) Inc. |
TDoc | Title | Source |
---|---|---|
R4-2215345 | SBFD adjacent channel coexistence evaluation | Qualcomm CDMA Technologies |
R4-2215385 | Further discussion on adjacent channel co-existence simulation assumption | CATT |
R4-2215486 | Study on the simulation assumption for adjacent channel co-existence | CMCC |
R4-2215619 | On UE-UE CLI modeling | Apple |
R4-2215776 | Discussions on adjacent channel co-existence evaluation | Samsung |
R4-2215789 | On interference modelling for duplex evolution | LG Electronics Finland |
R4-2215835 | On initial results for SBFD adjacent channel co-existence evaluation | Ericsson |
R4-2216133 | Further discussion on co-existence in adjacent channel for full duplex | vivo |
R4-2216201 | Assumptions and Initial Simulation results for SBFD coexistence evaluation | Nokia, Nokia Shanghai Bell |
R4-2216237 | Discussion on the co-existence study for NR duplex operation | Huawei, HiSilicon |
R4-2216543 | Further discussion on full duplex coexistence in adjacent channel scenario | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215346 | SBFD feasibility and impact on RF requirements: BS aspects | Qualcomm CDMA Technologies |
R4-2215390 | Further discussion on feasibility study for duplex evolution | CATT |
R4-2215484 | study the feasibility of and impact on RF requirements on gNB side | CMCC |
R4-2216134 | Further discussion on self-interference modelling for full duplex from BS aspect | vivo |
R4-2216202 | SBFD Base Station aspects | Nokia, Nokia Shanghai Bell |
R4-2216238 | Feasibility study from RF perspective | Huawei, HiSilicon |
R4-2216239 | Evolution of receiver blocking and AGC | Huawei, HiSilicon |
R4-2216404 | SBFD gNB RF considerations | Ericsson |
R4-2216409 | Discussion on Total Achievable Self-Interference Cancellation | Intel Corporation |
R4-2216544 | Further discussion on self-interference and CLI for full duplex BS | ZTE Corporation |
R4-2216717 | Discussion on feasibility and RF impact for SBFD capable gNB | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2215485 | Study the feasibility of and impact on RF requirements on UE aspect | CMCC |
R4-2216135 | Further discussion on interference modelling for full duplex from UE aspect | vivo |
R4-2216203 | UE to UE interference in Sub Band non-overlapping Full Duplex | Nokia, Nokia Shanghai Bell |
R4-2216405 | SBFD UE RF considerations | Ericsson |
R4-2216718 | Discussion on UE aspect for SBFD operation | Samsung |
R4-2216794 | Modelling UE CLI SINR for SBFD system study | Qualcomm France |
TDoc | Title | Source |
---|---|---|
R4-2216204 | Regulatory considerations on sub-band non-overlapping full duplex operation | Nokia, Nokia Shanghai Bell |
R4-2216518 | Sub-Band Full Duplex - Regulatory aspects | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216894 | Email discussion summary for [104-bis-e][310] FS_NR_duplex_evo_Part1 | Moderator (Samsung) |
R4-2216895 | [Email discussion summary for 104-bis-e][311] FS_NR_duplex_evo_Part2 | Moderator (China Mobile) |
R4-2217464 | WF on SBFD feasibility study and RF impact: BS aspect | Samsung |
R4-2217465 | WF on SBFD feasibility study and RF impact: UE aspect | Qualcomm |
R4-2217466 | WF for adjacent channel co-existence evaluation of SBFD operation | Samsung, CMCC |
R4-2217494 | Email discussion summary for [104-bis-e][310] FS_NR_duplex_evo_Part1 | Moderator (Samsung) |
R4-2217495 | [Email discussion summary for 104-bis-e][311] FS_NR_duplex_evo_Part2 | Moderator (China Mobile) |
R4-2217510 | Email discussion summary for [104-bis-e][310] FS_NR_duplex_evo_Part1 | Moderator (Samsung) |
R4-2217513 | WF on SBFD feasibility study and RF impact: UE aspect | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2216685 | Work Plan for Study Item on Expanded and Improved NR Positioning | Intel Corporation, CATT, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215430 | Discussion on accuracy improvement based on PRS/SRS bandwidth aggregation for intra-band carriers | CATT |
R4-2215875 | Discussion on PRS/SRS accuracy improvement for BW aggregation | LG Electronics Polska |
R4-2215883 | On accuracy improvement based on bandwidth aggregation for positioning | Ericsson |
R4-2216227 | Discussion on NR positioning measurement accuracy improvement based on bandwidth aggregation | Nokia, Nokia Shanghai Bell |
R4-2216541 | Further discussion on CA based positioning enhancement | ZTE Corporation |
R4-2216725 | Study of PRS/SRS bandwidth aggregation - RF aspects | Qualcomm Incorporated |
R4-2217739 | WF on expanded and improved NR positioning UE RF aspects | Intel |
TDoc | Title | Source |
---|---|---|
R4-2215884 | On accuracy improvement based on NR carrier phase measurements | Ericsson |
R4-2216228 | Discussion on NR positioning measurement accuracy improvement based on carrier phase measurements | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215432 | Discussion on RRM aspects in the study on expanded and improved NR positioning | CATT |
R4-2215825 | RRM requirements on expanded and improved NR positioning | OPPO |
R4-2215885 | RRM aspects of expanded and improved NR positioning | Ericsson |
R4-2216229 | RRM impacts for NR positioning accuracy improvements bandwidth aggregation and carrier phase measurements | Nokia, Nokia Shanghai Bell |
R4-2217257 | WF on Improved NR Positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2216931 | Email discussion summary for [104-bis-e][220] FS_NR_pos_enh2_RRM | Moderator (Ericsson) |
R4-2216974 | Email discussion summary for [104-bis-e][138] FS_NR_pos_UERF | Moderator (Intel) |
R4-2217017 | Email discussion summary for [104-bis-e][138] FS_NR_pos_UERF | Moderator (Intel) |
R4-2217153 | Email discussion summary for [104-bis-e][220] FS_NR_pos_enh2_RRM | Moderator (Ericsson) |
R4-2217790 | Email discussion summary for [104-bis-e][138] FS_NR_pos_UERF | Moderator (Intel) |
TDoc | Title | Source |
---|---|---|
R4-2215613 | On R18 CA enhancement - RRM | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215495 | Switching for UL Tx switching across 3 or 4 bands | CMCC |
R4-2215569 | UL Outage time considerations for 2 TAG | Qualcomm Incorporated |
R4-2215797 | UL Tx switching across 3/4 bands and Tx switching with 2 TAGs | China Telecom |
R4-2215881 | Discussion on Tx switching across 3 or 4 bands | ZTE Wistron Telecom AB |
R4-2215953 | Uplink TX switching with dual-TAG across two bands | Ericsson, Sony |
R4-2215954 | Introduction of ON/OFF time mask for TX switching across two bands with dual-TAG | Ericsson |
R4-2216042 | Discussion on RF requirements for multi-carrier enhancement | Xiaomi |
R4-2216119 | Discussion on UE RF requirements for TxSwitching up to 3 or 4 bands | vivo |
R4-2216160 | Continue discussion on UL Tx switching across 3 or 4 bands in Rel-18 | MediaTek Inc. |
R4-2216433 | R18 Discussion on Tx switching | OPPO |
R4-2216653 | Discussion on Multi-carrier enhancements with single TAG | Huawei, HiSilicon |
R4-2216654 | Discussion on Multi-carrier enhancements with multiple TAG | Huawei, HiSilicon |
R4-2216655 | Draft CR for 38.101-1 to clarify the time mask for switching with multiple TAGs | Huawei, HiSilicon |
R4-2216714 | Further Discussion on Switching Time and other RF Aspects for UL Tx Switching Across 3 or 4 Bands | Samsung |
R4-2217740 | WF on UL Tx switching across 3/4 bands with single TAG | China Telecom |
R4-2217741 | LS on Rel-18 UL Tx switching | China Telecom |
R4-2217742 | WF on UL Tx switching with multiple TAGs | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215496 | RRM requirements for multi-carrier enhancements | CMCC |
R4-2215788 | RRM core requirements for multi-carrier enhancements | Nokia, Nokia Shanghai Bell |
R4-2215798 | DL interruption and UL outage time for Rel-18 Tx switching | China Telecom |
R4-2215872 | Discussion on RRM impacts for mulit-carrier enhancement | vivo |
R4-2216310 | Discussion on RRM core requirements for multi-carrier enhancements | Huawei, HiSilicon |
R4-2216424 | RRM impact | Ericsson |
R4-2216715 | Discussion on RRM requirements for UL Tx Switching Across 3 or 4 Bands | Samsung |
R4-2217258 | WF on multi-carrier enhancements | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216932 | Email discussion summary for [104-bis-e][221] NR_MC_enh_RRM | Moderator (Huawei) |
R4-2216975 | Email discussion summary for [104-bis-e][139] NR_MC_enh_UERF | Moderator (China Telecom) |
R4-2217018 | Email discussion summary for [104-bis-e][139] NR_MC_enh_UERF | Moderator (China Telecom) |
R4-2217154 | Email discussion summary for [104-bis-e][221] NR_MC_enh_RRM | Moderator (Huawei) |
R4-2217791 | Email discussion summary for [104-bis-e][139] NR_MC_enh_UERF | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R4-2215424 | Discussion of improvement on FR2 Scell/SCG setup/resume | CATT |
R4-2215446 | Discussion on improvement on FR2 SCell/SCG setup/resume | MediaTek (Shenzhen) Inc. |
R4-2215458 | Discussion on improvement of FR2 Scell and SCG setup | Xiaomi |
R4-2215518 | Discussion on FR2 SCell/SCG setup/resume | Nokia, Nokia Shanghai Bell |
R4-2215609 | On R18 mobility enhancement - new RRM measurement during RRC connection setup | Apple |
R4-2215723 | Discussion on FR2 SCell/SCG setup/resume | CMCC |
R4-2215816 | Discussion on improvement on FR2 Scell SCG setup resume | OPPO |
R4-2215862 | Discussion on the improvement on FR2 SCell/SCG setup/resume | vivo |
R4-2215961 | Discussion on Study of improvement on FR2 SCell/SCG setup/resume | LG Electronics UK |
R4-2216309 | Discussion on improvement on FR2 SCell/SCG setup/resume | Huawei, HiSilicon |
R4-2216342 | Discussion on Study of improvement on FR2 SCell/SCG setup/resume | Ericsson |
R4-2216867 | Enhancement of FR2 cell measurements in RRC non-connected mode | Qualcomm Incorporated |
R4-2217260 | WF on improvement on FR2 SCell/SCG setup/resume | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215359 | Discussion on RRM impacts from R18 L1/L2 mobility | Intel Corporation |
R4-2215425 | Discussion on L1/L2 based inter-cell mobility | CATT |
R4-2215447 | Discussion on L1/L2 mobility | MediaTek (Shenzhen) Inc. |
R4-2215459 | Discussion on L1/L2 based inter-cell mobility | Xiaomi |
R4-2215519 | Discussion on Lower Layer Mobility, LLM | Nokia, Nokia Shanghai Bell |
R4-2215608 | On R18 mobility enhancement - L1/L2 inter-cell mobility RRM | Apple |
R4-2215724 | Discussion on L1/L2 based inter-cell mobility | CMCC |
R4-2215817 | Discussion on L1L2 based inter-cell mobility | OPPO |
R4-2215957 | Discussion on L1/L2 based inter-cell mobility | LG Electronics UK |
R4-2216308 | Discussion on L1/L2 based inter-cell mobility for mobility latency reduction | Huawei, HiSilicon |
R4-2216367 | Discussion on RRM aspects in R18 L1L2 mobility | vivo |
R4-2216831 | Discussion on L1/L2 based inter-cell mobility | Ericsson |
R4-2217259 | WF on L1/L2 inter-cell mobility | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216933 | Email discussion summary for [104-bis-e][222] NR_Mob_enh2_part1 | Moderator (MediaTek) |
R4-2216934 | Email discussion summary for [104-bis-e][223] NR_Mob_enh2_part2 | Moderator (Apple) |
R4-2217155 | Email discussion summary for [104-bis-e][222] NR_Mob_enh2_part1 | Moderator (MediaTek) |
R4-2217156 | Email discussion summary for [104-bis-e][223] NR_Mob_enh2_part2 | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2215469 | Discussion on RRM requirements for Rel-17 MUSIM gaps | Xiaomi |
R4-2215615 | On R18 MUSIM enhancement - RRM | Apple |
R4-2215725 | Discussion on RRM requirements for Rel-17 MUSIM gaps | CMCC |
R4-2215826 | Discussion on RRM requirements for Rel-17 MUSIM gaps | OPPO |
R4-2215969 | Considerations on RRM requirements for R17 MUSIM gaps | vivo |
R4-2216335 | Discussion on RRM requirements for MUSIM gaps | Huawei, HiSilicon |
R4-2216459 | Discussion on MUSIM gaps | Ericsson |
R4-2216513 | Discussion on MUSIM requirements | Nokia, Nokia Shanghai Bell |
R4-2216724 | On requirements for Rel-17 MUSIM gaps | Qualcomm Incorporated |
R4-2216761 | Discussion on RRM requirements for MUSIM gaps | MediaTek inc. |
R4-2217261 | WF on RRM requirements for Rel-17 MUSIM gaps | Vivo |
R4-2217262 | LS on priority for Rel-17 MUSIM gaps | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2216935 | Email discussion summary for [104-bis-e][224] NR_DualTxRx_MUSIM | Moderator (Vivo) |
R4-2217157 | Email discussion summary for [104-bis-e][224] NR_DualTxRx_MUSIM | Moderator (Vivo) |
TDoc | Title | Source |
---|---|---|
R4-2215709 | NR NTN enhancement workplan | NTT DOCOMO, INC. |
R4-2217507 | NR NTN enhancement workplan | NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R4-2216076 | Discussion on Rel-18 NTN regulatory information and ka band | Huawei, HiSilicon |
R4-2216148 | Initial discussion for NR to support non-terrestrial networks | Xiaomi |
R4-2216372 | Discussion on above 10GHz NTN band | Nokia, Nokia Shanghai Bell |
R4-2216516 | NTN enhancement: System parameters | Ericsson |
R4-2216556 | Discussion on system parameter for NTN in Ka band | ZTE Corporation |
R4-2216651 | Ka band system parameters for NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2215775 | Utilization of frequency range 27.50-28.35GHz spectrum in USA | Verizon, T-Mobile USA |
R4-2216515 | NTN enhancement: Regulatory aspects and band discussion | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215348 | VSAT UE Characteristics and Initial Simulation Parameters | THALES |
R4-2215352 | Discussion on Ka-band NTN-TN NR adjacent band coexistence scenarios | THALES, Lockheed Martin, Hispasat, Intelsat, Magister Solutions Ltd, Satellite Applications Catapult, ESA, Avanti, Hughes/EchoStar, Inmarsat, Eutelsat, Sateliot |
R4-2215777 | Simulation assumptions for above 10GHz NTN co-existence study | Samsung Electronics Nordic AB |
R4-2216517 | NTN enhancement - coex simulations: scenarios and assumptions | Ericsson |
R4-2216557 | Discussion on coexistence evaluation for NTN in Ka-band | ZTE Corporation |
R4-2217743 | WF on NTN UE in Ka-band | ZTE |
TDoc | Title | Source |
---|---|---|
R4-2215415 | General consideration on SAN RF requirements for above 10GHz bands | CATT |
R4-2216558 | Discussion on SAN RF requirements for NTN in Ka-band | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216559 | Discussion on UE RF requirements for NTN in Ka-band | ZTE Corporation |
R4-2216652 | Ka band UE RF requirements for NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216896 | Email discussion summary for [104-bis-e][312] NR_NTN_enh_Part1 | Moderator (Thales) |
R4-2216897 | [Email discussion summary for 104-bis-e][313] NR_NTN_enh_Part2 | Moderator (Samsung) |
R4-2216976 | Email discussion summary for [104-bis-e][140] NR_NTN_enh_UERF | Moderator (ZTE) |
R4-2217019 | Email discussion summary for [104-bis-e][140] NR_NTN_enh_UERF | Moderator (ZTE) |
R4-2217467 | WF on NR NTN Enhancements Part1 | Thales |
R4-2217468 | Way forward on [313] NR_NTN_enh_Part2 | Samsung |
R4-2217469 | Simulation assumptions for NTN co-existence in bands above 10GHz | Samsung |
R4-2217496 | Email discussion summary for [104-bis-e][312] NR_NTN_enh_Part1 | Moderator (Thales) |
R4-2217497 | [Email discussion summary for 104-bis-e][313] NR_NTN_enh_Part2 | Moderator (Samsung) |
R4-2217792 | Email discussion summary for [104-bis-e][140] NR_NTN_enh_UERF | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2216588 | On further enhancement for NR UL coverage | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215793 | Power high limit and intra band UL CA | Nokia, Nokia Shanghai Bell |
R4-2215892 | Discussion on enhancement of increasing UE power high limit for CA and DC | ZTE Corporation |
R4-2215955 | The high-power limit and power-class fallback | Ericsson |
R4-2216120 | Discussion on enhancement of increasing UE power high limit for CA and DC | vivo |
R4-2216149 | initial discussion on enhancement of increasing UE maximum power high limit | Xiaomi |
R4-2216441 | R18 Discussion on power domain enhancement | OPPO |
R4-2217744 | WF on enhancements of increasing UE power high limit | Huawei, HiSilicon |
R4-2217745 | WF on Enhancements to reduce MPR/PAR | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215514 | Scope of the work for MPR/PAR -objective | Nokia, Nokia Shanghai Bell |
R4-2215515 | Enhancements to reduce MPR/PAR | Nokia, Nokia Shanghai Bell |
R4-2215891 | Discussion on power domain enhancements to reduce MPR/PAR | ZTE Corporation |
R4-2216121 | Discussion on power domain enhancements to reduce MPR | vivo |
R4-2216639 | MPR reduction scope discussion in Rel-18 NR Cov-Enh | Ericsson |
R4-2216788 | On UE RF coverage enhancements for Rel-18 | Qualcomm Incorporated |
R4-2217746 | LS on RF evaluation parameters | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2216977 | Email discussion summary for [104-bis-e][141] NR_cov_enh2_part1 | Moderator (Huawei) |
R4-2216978 | Email discussion summary for [104-bis-e][142] NR_cov_enh2_part2 | Moderator (Nokia) |
R4-2217020 | Email discussion summary for [104-bis-e][141] NR_cov_enh2_part1 | Moderator (Huawei) |
R4-2217021 | Email discussion summary for [104-bis-e][142] NR_cov_enh2_part2 | Moderator (Nokia) |
R4-2217793 | Email discussion summary for [104-bis-e][141] NR_cov_enh2_part1 | Moderator (Huawei) |
R4-2217794 | Email discussion summary for [104-bis-e][142] NR_cov_enh2_part2 | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R4-2216198 | Discussion on NR Network-controlled repeaters | Nokia, Nokia Shanghai Bell |
R4-2216552 | Discussion on work plan and spec drafting for NCR in Rel-18 | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215488 | discussion on NCR RF requirements | CMCC |
R4-2216199 | On RF core requirements of NR Network-controlled repeaters | Nokia, Nokia Shanghai Bell |
R4-2216553 | Discussion on RF requirements for NCR in Rel-18 | ZTE Corporation |
R4-2216789 | On RF and EMC requirements for network controlled repeaters | Ericsson France S.A.S |
R4-2216793 | Network-controlled repeater specification impact in 38.106 | Qualcomm France |
R4-2217506 | LS to RAN1 on NCR-MT transmission and Beam correspondence | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2216289 | Initial discussion on RRM impacts for NR network-controlled repeaters | Huawei, HiSilicon |
R4-2216554 | Discussion on RRM requirements for NCR-MT in Rel-18 | ZTE Corporation |
R4-2216862 | Impact of RRM on network controlled repeater | Ericsson |
R4-2217263 | WF on RRM requirements for NCR | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2216898 | Email discussion summary for [104-bis-e][314] NR_netcon_repeater | Moderator (ZTE) |
R4-2216936 | Email discussion summary for [104-bis-e][225] NR_netcon_repeater_RRM | Moderator (ZTE) |
R4-2217158 | Email discussion summary for [104-bis-e][225] NR_netcon_repeater_RRM | Moderator (ZTE) |
R4-2217470 | Work plan for NCR RF requirements in Rel-18 | ZTE |
R4-2217471 | WF on NCR RF requirements in Rel-18 | ZTE |
R4-2217498 | Email discussion summary for [104-bis-e][314] NR_netcon_repeater | Moderator (ZTE) |
R4-2217512 | Email discussion summary for [104-bis-e][314] NR_netcon_repeater | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2215560 | Big CR on Introduction of completed R18 x(x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 | Huawei Technologies France |
R4-2215562 | revised WID Rel-18 LTE-A CA for x(x<=6) DL y(y<=2) UL | Huawei Technologies France |
R4-2215563 | TR 36.718-02-01 LTE-A CA for x(x=123456) DL y(y=12) UL | Huawei Technologies France |
R4-2217814 | TR 36.718-02-01 LTE-A CA for x(x=123456) DL y(y=12) UL | Huawei Technologies France |
TDoc | Title | Source |
---|---|---|
R4-2215561 | TP for TR 36.718-02-01 to add CA_7C-32A | VODAFONE Group Plc |
TDoc | Title | Source |
---|---|---|
R4-2215972 | TP for TR 36.718-02-01 to add CA_1A-7C-32A | VODAFONE Group Plc |
R4-2216084 | TP for TR 36.718-02-01 to add UL CA_1A-3A for CA_1A-3A-32A | VODAFONE Group Plc |
R4-2216095 | TP for TR 36.718-02-01 to add UL CA_1A-7A for CA_1A-7A-32A | VODAFONE Group Plc |
R4-2216099 | TP for TR 36.718-02-01 to add UL CA_3A-28A for CA_3A-28A-32A | VODAFONE Group Plc |
R4-2217799 | TP for TR 36.718-02-01 to add CA_1A-7C-32A | VODAFONE Group Plc |
R4-2217800 | TP for TR 36.718-02-01 to add UL CA_1A-3A for CA_1A-3A-32A | VODAFONE Group Plc |
R4-2217801 | TP for TR 36.718-02-01 to add UL CA_1A-7A for CA_1A-7A-32A | VODAFONE Group Plc |
R4-2217802 | TP for TR 36.718-02-01 to add UL CA_3A-28A for CA_3A-28A-32A | VODAFONE Group Plc |
TDoc | Title | Source |
---|---|---|
R4-2215971 | TP for TR 36.718-02-01 to add CA_7C-20A | VODAFONE Group Plc |
R4-2215973 | TP for TR 36.718-02-01 to add CA_3A-7C-32A | VODAFONE Group Plc |
R4-2215975 | TP for TR 36.718-02-01 to add CA_7C-20A-32A | VODAFONE Group Plc |
R4-2216098 | TP for TR 36.718-02-01 to add UL CA_1A-28A for CA_1A-28A-32A | VODAFONE Group Plc |
R4-2216100 | TP for TR 36.718-02-01 to add CA_1A-3A-7C-32A | VODAFONE Group Plc |
R4-2216101 | TP for TR 36.718-02-01 to add dual UL for CA_1A-3A-7A-32A | VODAFONE Group Plc |
R4-2216102 | TP for TR 36.718-02-01 to add dual UL for CA_1A-3A-28A-32A | VODAFONE Group Plc |
R4-2216138 | TP for TR 36.718-02-01 to add dual UL for CA_1A-7A-28A-32A | VODAFONE Group Plc |
R4-2216139 | TP for TR 36.718-02-01 to add CA_3A-7A-28A-32A | VODAFONE Group Plc |
R4-2216140 | TP for TR 36.718-02-01 to add CA_1A-3A-7A-28A-32A | VODAFONE Group Plc |
TDoc | Title | Source |
---|---|---|
R4-2216947 | Email discussion summary for [104-bis-e][109] LTE_Baskets | Moderator (Huawei) |
R4-2216990 | Email discussion summary for [104-bis-e][109] LTE_Baskets | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2216523 | Draft CR to TS 36.133: Introduction of LTE TDD band 54 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215333 | Band 54 protection from bands n24, n66, n70 and n255 | Skyworks Solutions Inc. |
R4-2215380 | LTE TDD 1670-1675MHz UE-UE Coexistence | Murata Manufacturing Co Ltd. |
R4-2215698 | Draft CR related to Introduction of new LTE TDD Band in 1670 1675 MHz | Ligado Networks |
R4-2215699 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado Networks |
R4-2215707 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado Networks |
R4-2215708 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado Networks |
R4-2216428 | Evaluating spurious emission coexistence limits for Bands 24, 255, 66 and 70 to protect the new LTE TDD Band 54 | Ligado Networks |
R4-2217696 | Draft CR related to Introduction of new LTE TDD Band in 1670 1675 MHz | Ligado, Skyworks Solutions, Nokia |
R4-2217697 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado, Skyworks Solutions, Nokia |
R4-2217698 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado, Skyworks Solutions, Nokia |
R4-2217699 | Draft CR related to Introduction of LTE TDD Band in 1670 1675 MHz | Ligado, Skyworks Solutions, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2216520 | Draft CR to TS 37.105: Introduction of LTE TDD band 54 | Ericsson |
R4-2216521 | Draft CR to TS 37.145-1: Introduction of LTE TDD band 54 | Ericsson |
R4-2216522 | Draft CR to TS 37.145-2: Introduction of LTE TDD band 54 | Ericsson |
R4-2216726 | draft CR to 38.141-1 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216727 | draft CR to 38.141-2 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216728 | draft CR to 36.104 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216729 | draft CR to 36.141 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216730 | draft CR to 37.104 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216731 | draft CR to 37.141 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2216747 | draft CR to 38.104 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2217700 | Draft CR to TS 37.105: Introduction of LTE TDD band 54 | Ericsson |
R4-2217701 | Draft CR to TS 37.145-1: Introduction of LTE TDD band 54 | Ericsson |
R4-2217702 | Draft CR to TS 37.145-2: Introduction of LTE TDD band 54 | Ericsson |
R4-2217703 | draft CR to 36.104 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2217704 | draft CR to 36.141 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2217705 | draft CR to 37.104 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
R4-2217706 | draft CR to 37.141 on introduction of Band 54 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2216958 | Email discussion summary for [104-bis-e][122] R18_LTE_TDD_1.6GHz | Moderator (Ligado) |
R4-2217001 | Email discussion summary for [104-bis-e][122] R18_LTE_TDD_1.6GHz | Moderator (Ligado) |
R4-2217774 | Email discussion summary for [104-bis-e][122] R18_LTE_TDD_1.6GHz | Moderator (Ligado) |
TDoc | Title | Source |
---|---|---|
R4-2216643 | Work plan for 5G broadcast | Qualcomm Incorporated |
R4-2217707 | WF on agreements for 5G broadcast | SWR |
TDoc | Title | Source |
---|---|---|
R4-2215931 | LTE based 5G broadcast band definition | Nokia, Nokia Shanghai Bell |
R4-2215934 | Further discussion on band definition for LTE based broadcast | ZTE Corporation |
R4-2216074 | Discussion on UE implementation for band plan | Huawei, HiSilicon |
R4-2216419 | Coexistence study of 5G terrestrial broadcast | Qualcomm Incorporated |
R4-2216519 | 5G Broadcast: Bands discussion | Ericsson |
R4-2216644 | UHF band plan for 5G broadcast | Qualcomm Incorporated |
R4-2217026 | Further discussion on band definition for LTE based broadcast | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215932 | LTE based 5G UE RF requirement | Nokia, Nokia Shanghai Bell |
R4-2215935 | Discussion on UE RF for LTE based broadcast | ZTE Corporation |
R4-2216075 | Discussion on UE RF requirements | Huawei, HiSilicon |
R4-2216645 | 5G broadcast core requirements verification | Qualcomm Incorporated |
R4-2217027 | Discussion on UE RF for LTE based broadcast | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2215342 | BS requirements for 5G terrestrial broadcast | SWR |
R4-2216550 | Further discussion on BS RF requirements for LTE based broadcast | ZTE Corporation |
R4-2216735 | BS requirements for LTE based 5G terrestrial broadcast band(s) | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2216899 | Email discussion summary for [104-bis-e][315] LTE_terr_bcast_bands_BSRF | Moderator (Nokia) |
R4-2216959 | Email discussion summary for [104-bis-e][123] LTE_terr_bcast_bands_UERF | Moderator (Qualcomm) |
R4-2217002 | Email discussion summary for [104-bis-e][123] LTE_terr_bcast_bands_UERF | Moderator (Qualcomm) |
R4-2217472 | WF on BS requirements for LTE based 5G terrestrial broadcast | ZTE |
R4-2217499 | Email discussion summary for [104-bis-e][315] LTE_terr_bcast_bands_BSRF | Moderator (Nokia) |
R4-2217775 | Email discussion summary for [104-bis-e][123] LTE_terr_bcast_bands_UERF | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2216857 | On band grouping for RRM requirements for IoT with satellite access | Ericsson |
R4-2216858 | Draft CR on band grouping for NB-IoT for satellite access in 36.133 | Ericsson |
R4-2216859 | Draft CR on band grouping for Cat-M1 for satellite access in 36.133 | Ericsson |
R4-2217584 | Draft CR on band grouping for Cat-M1 for satellite access in 36.133 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215487 | discussion on IoT NTN system parameter | CMCC |
R4-2216546 | Further discussion on system parameters | ZTE Corporation |
R4-2216637 | On System parameter for IoT NTN | Ericsson |
R4-2216682 | TP for system parameter | Ericsson |
R4-2216778 | Discussions on IoT NTN system parameters | Huawei, HiSilicon |
R4-2216799 | Remaining issues for system parameters for IoT NTN | MediaTek (Chengdu) Inc. |
R4-2216834 | TP to TS 36.102 clause 5 for IoT NTN | MediaTek (Chengdu) Inc. |
R4-2217753 | TP for IoT NTN UE clause 7 | Mediatek India |
R4-2217754 | TP to TS 36.102 clause 5 for IoT NTN | MediaTek (Chengdu) Inc. |
R4-2217807 | TP to TS 36.102 clause 5 for IoT NTN | MediaTek (Chengdu) Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216418 | Coexistence simulation results for TN-NTN NB IoT | Qualcomm Incorporated |
R4-2216547 | Further discussion on simulation assumptions and evaluation results for IoT over NTN | ZTE Corporation |
R4-2216634 | IoT NTN coexisting initial results | Ericsson |
R4-2216800 | IoT NTN coexistence remaining aspects | MediaTek (Chengdu) Inc. |
TDoc | Title | Source |
---|---|---|
R4-2216545 | Draft spec for TS 36.108 | ZTE Corporation |
R4-2216548 | Further discussion on SAN RF requirements for IoT over NTN | ZTE Corporation |
R4-2216638 | TP for SAN RF requirement | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215570 | Freq error with segmentation | Qualcomm Incorporated |
R4-2215697 | Evaluating emission requirements and whether AMPR needs to be specified for IoT NTN operation in Band 255 or not | Ligado Networks |
R4-2215779 | Discussion on UE RF requirements for IoT NTN | Mediatek India Technology Pvt. |
R4-2215780 | Discussion on UE RF requirements for IoT NTN | Mediatek India Technology Pvt. |
R4-2216147 | Discussion on UE RF requirement for NB-iot/eMTC NTN | Xiaomi |
R4-2216254 | REFSENS for NTN eMTC | Sony |
R4-2216549 | Further discussion on UE RF requirements for IoT over NTN | ZTE Corporation |
R4-2216635 | IoT UE RF remaining issues | Ericsson |
R4-2216636 | TP for UE RF requirement | Ericsson |
R4-2216680 | TP for IoT NTN UE clause 6 | Mediatek India Technology Pvt. |
R4-2216681 | TP for IoT NTN UE clause 7 | Mediatek India Technology Pvt. |
R4-2216884 | Discussion and TP on Suffix information for 36.102 | Qualcomm Incorporated |
R4-2217751 | TP on Cat-M1 UE NTN Frequency Error and b256 UE Rx sensitivity | Ericsson |
R4-2217752 | TP for IoT NTN UE clause 6 | Mediatek India Technology Pvt. |
R4-2217755 | TP for clause 4 of TS36.102 | Qualcomm Incorporated, MediaTek |
R4-2217810 | TP on Cat-M1 UE NTN Frequency Error and b256 UE Rx sensitivity | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215506 | Discussion on RRM core requirements for LTE NB-IoT and eMTC NTN | CMCC |
R4-2215507 | draft CR on RRC re-establishment and timing requirement for eMTC UE in IoT-NTN | CMCC |
R4-2215753 | RRM requirements for LTE NB-IoT/eMTC over NTN | MediaTek inc. |
R4-2215754 | Introduction of cell re-selection and PUR requirement for UE category NB-IoT for Satellite Access | MediaTek inc. |
R4-2215755 | Introduction of RRC Re-establishment requirement for NB-IoT UEs for Satellite Access | MediaTek inc. |
R4-2215756 | Introduction of measurements requirement for UE category NB-IoT for Satellite Access | MediaTek inc. |
R4-2215757 | Introduction of Random Access Requirements for Cat-M1 UEs for Satellite Access | MediaTek inc. |
R4-2216269 | Discussion RRM requirements for IoT NTN | Huawei, HiSilicon |
R4-2216270 | DraftCR on RRM requirements for NB-IoT for IoT NTN | Huawei, HiSilicon |
R4-2216339 | CR on HO and measurement requirements for eMTC over NTN | Huawei, HiSilicon |
R4-2216468 | Discussion on Core Requirements for IoT NTN | Nokia, Nokia Shanghai Bell |
R4-2216505 | Draft CR on RLM for category M1 UE for SA | Ericsson |
R4-2216767 | Discussions on NTN IoT RRM requirements | Ericsson |
R4-2216768 | IDLE mode requirements for IoT NTN (cat-M) | Ericsson |
R4-2216860 | Draft CR on RRC release with redirection non-anchor NB-IoT carrier for satellite access in 36.133 | Ericsson |
R4-2216861 | Draft CR on RRC release with redirection for Cat-M1 for satellite access in 36.133 | Ericsson |
R4-2216864 | draft CR of UE UL Timing Requirements for IoT NTN | Qualcomm Incorporated |
R4-2216869 | RRM requirements of IoT NTN | Qualcomm Incorporated |
R4-2217264 | WF on LTE IoT NTN RRM requirements | MediaTek |
R4-2217265 | LS on information for neighbor/target cell in IoT NTN | Huawei, HiSilicon |
R4-2217266 | Introduction of cell re-selection and PUR requirement for UE category NB-IoT for Satellite Access | MediaTek inc. |
R4-2217267 | Introduction of RRC Re-establishment requirement for NB-IoT UEs for Satellite Access | MediaTek inc. |
R4-2217268 | DraftCR on RRM requirements for NB-IoT for IoT NTN | Huawei, HiSilicon |
R4-2217269 | draft CR of UE UL Timing Requirements for IoT NTN | Qualcomm Incorporated |
R4-2217270 | draft CR of UE UL Timing Requirements for IoT NTN | Qualcomm Incorporated |
R4-2217271 | Introduction of measurements requirement for UE category NB-IoT for Satellite Access | MediaTek inc. |
R4-2217272 | IDLE mode requirements for IoT NTN (cat-M) | Ericsson |
R4-2217273 | CR on HO and measurement requirements for eMTC over NTN | Huawei, HiSilicon |
R4-2217274 | Introduction of Random Access Requirements for Cat-M1 UEs for Satellite Access | MediaTek inc. |
R4-2217275 | draft CR on RRC re-establishment and timing requirement for eMTC UE in IoT-NTN | CMCC |
R4-2217276 | Draft CR on RRC release with redirection for Cat-M1 for satellite access in 36.133 | Ericsson |
R4-2217277 | Draft CR on RLM for category M1 UE for SA | Ericsson |
R4-2217585 | Introduction of RRC Re-establishment requirement for NB-IoT UEs for Satellite Access | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2216900 | Email discussion summary for [104-bis-e][316] IoT_NTN_Co-existence_SANRF | Moderator (ZTE) |
R4-2216937 | Email discussion summary for 1[04-bis-e][226] LTE_NBeMTC_NTN_RRM | Moderator (MediaTek) |
R4-2216979 | Email discussion summary for [104-bis-e][143] LTE_NBeMTC_NTN_UERF | Moderator (MediaTek) |
R4-2217022 | Email discussion summary for [104-bis-e][143] LTE_NBeMTC_NTN_UERF | Moderator (MediaTek) |
R4-2217159 | Email discussion summary for 1[04-bis-e][226] LTE_NBeMTC_NTN_RRM | Moderator (MediaTek) |
R4-2217473 | WF on co-existence assumption for IoT over NTN | MTK |
R4-2217474 | WF on SAN RF requirements for IoT over NTN | ZTE |
R4-2217500 | Email discussion summary for [104-bis-e][316] IoT_NTN_Co-existence_SANRF | Moderator (ZTE) |
R4-2217747 | WF on UE RF and System Parameters for IoT NTN | MediaTek |
R4-2217748 | WF on UE A-MPR and Emissions requirements | ZTE |
R4-2217749 | TP for NB-IoT UE Frequency Error | Qualcomm |
R4-2217750 | TP for Out-of-band blocking for b256 | Xiaomi |
R4-2217795 | Email discussion summary for [104-bis-e][143] LTE_NBeMTC_NTN_UERF | Moderator (MediaTek) |
TDoc | Title | Source |
---|---|---|
R4-2215461 | Further discussion on Maximum uplink timing difference for multi-DCI multi-TRP with two Tas | Xiaomi |
R4-2215614 | On R18 eFeMIMO - MTTD for multi-DCI mult-TRP with two TAs | Apple |
R4-2216290 | On maximum uplink timing difference for multi-DCI multi-TRP with two Tas | Huawei, HiSilicon |
R4-2216368 | Discussion on maximum uplink timing difference for multi-DCI multi-TRP with two TAs | vivo |
R4-2216410 | Multiple TA for multi-TRP deployments limits | InterDigital Communications |
R4-2216605 | Maximum uplink timing difference for multi-DCI multi-TRP with 2 TAs | Nokia, Nokia Shanghai Bell |
R4-2216716 | Discussion on maximum uplink timing difference for Multi-DCI Multi-TRP with two TAs | Samsung |
R4-2216832 | Discussion on maximum uplink timing difference for multi-DCI multi-TRP with two TAs | Ericsson |
R4-2216833 | Reply LS on maximum uplink timing difference for multi-DCI multi-TRP with two TAs | Ericsson |
R4-2217278 | WF on MRTD/MTTD requirement for multi-TRPs with 2 Tas | Apple |
R4-2217279 | Reply LS on maximum uplink timing difference for multi-DCI multi-TRP with two Tas | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215652 | On UE power control for STxMP | Apple |
R4-2216122 | Discussion and reply LS on UE power limitation for STxMP in FR2 | vivo |
R4-2216354 | Discussion on the LS for UE power limitation for STxMP in FR2 | Xiaomi |
R4-2216411 | On UE power limits for STxMP in FR2 | InterDigital Communications |
R4-2216586 | Draft reply LS on the UE power limitation for STxMP in FR2 | Huawei, HiSilicon |
R4-2216783 | Reply LS on UE power limitation for STxMP in FR2 (R1-2205639) | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2216255 | Views on RAN4 action on UL Segmented Transmission for UL synchronization for IoT NTN | Sony |
R4-2216271 | Discussion on UL Segmented Transmission for UL synchronization for IoT NTN | Huawei, HiSilicon |
R4-2216469 | Discussion on UL segmentation for IoT NTN | Nokia, Nokia Shanghai Bell |
R4-2216766 | UL Segmented Transmission for UL synchronization for IoT NTN | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2215706 | Discussion and reply LS on humidity inconsistency among specifications | Samsung |
R4-2216618 | Discussion on lower humidity limit in normal temperature test environment | ZTE Corporation |
R4-2217756 | WF on resolving humidity inconsistency | ZTE |
TDoc | Title | Source |
---|---|---|
R4-2215316 | CR to 38.101-2: Correction to modified MPR information | Nokia, Qualcomm Inc, Skyworks Inc, Ericsson |
R4-2215317 | Reply LS to RAN5 LS on ModifiedMPR-Behaviour clarification for different power classes | Nokia, Qualcomm Inc, Skyworks Inc, Ericsson |
R4-2215970 | CR to 38.101-2: Correction to modified MPR information R16 | Nokia, Qualcomm Inc, Skyworks Inc, Ericsson |
R4-2216355 | Reply LS on Modified MPR-Behaviour clarification for different power classes | Xiaomi |
R4-2216442 | R16 Discuss and reply LS on ModifiedMPR-Behaviour | OPPO |
R4-2216677 | On ModifiedMPR | Huawei, HiSilicon |
R4-2216678 | draft Reply LS on ModifiedMPR | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2216938 | Email discussion summary for 1[04-bis-e][227] LS_reply | Moderator (Apple) |
R4-2216980 | Email discussion summary for 1[04-bis-e][144] NR_reply_LS_UE_RF | Moderator (Apple) |
R4-2217023 | Email discussion summary for 1[04-bis-e][144] NR_reply_LS_UE_RF | Moderator (Apple) |
R4-2217160 | Email discussion summary for 1[04-bis-e][227] LS_reply | Moderator (Apple) |
R4-2217757 | WF on Modified MPR-Behaviour clarification for different power classes | Huawei |
R4-2217758 | Reply LS on UE power limitation for STxMP in FR2 | Vivo |
R4-2217759 | WF on IntrabandENDC-Support | OPPO |
R4-2217760 | WF on NS mapping for intra-band CA | Huawei |
R4-2217796 | Email discussion summary for [104-bis-e][144] NR_reply_LS_UE_RF | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2216939 | Email discussion summary for [104-bis-e][228] RAN_task_RRM | Moderator (Vivo) |
R4-2216981 | Email discussion summary for [104-bis-e][145] RAN_task_UERF_part1 | Moderator (ATT) |
R4-2216982 | Email discussion summary for [104-bis-e][146] RAN_task_UERF_part2 | Moderator (OPPO) |
R4-2217024 | Email discussion summary for [104-bis-e][145] RAN_task_UERF_part1 | Moderator (ATT) |
R4-2217025 | Email discussion summary for [104-bis-e][146] RAN_task_UERF_part2 | Moderator (OPPO) |
R4-2217161 | Email discussion summary for [104-bis-e][228] RAN_task_RRM | Moderator (Vivo) |
R4-2217797 | Email discussion summary for [104-bis-e][145] RAN_task_UERF_part1 | Moderator (ATT) |
R4-2217798 | Email discussion summary for [104-bis-e][146] RAN_task_UERF_part2 | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R4-2215363 | Analysis and summary of specification impacts of RAN4 options for FG 6-1a support | Intel Corporation |
R4-2215429 | Analysis on the options for BWP withoutRestriction | CATT |
R4-2215497 | Discussion on options for "bwp-WithoutRestriction" | CMCC |
R4-2215616 | On BWP without restriction | Apple |
R4-2215729 | Discussion on BWP without restriction | Spreadtrum Communications |
R4-2215818 | Discussion on BWP operation without bandwidth restriction | OPPO |
R4-2215871 | Discussion on options for BWP without restriction | vivo |
R4-2216334 | Discussion on options for bwp-WithoutRestriction | Huawei, HiSilicon |
R4-2216514 | Analysis of options for BWP withoutRestriction | Nokia, Nokia Shanghai Bell |
R4-2216736 | Discussion on BWP operation without BW restrictions | MediaTek inc. |
R4-2216762 | Discussion of BWP operation without bandwidth restriction | Ericsson |
R4-2216865 | BWP operation without bandwidth restriction | Qualcomm Incorporated |
R4-2217280 | WF on RAN task on BWP operation without restriction | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2215374 | Enabling 2Rx option for n104 | Skyworks Solutions Inc. |
R4-2215645 | 2RX exception for the 6GHz band | Apple |
R4-2216244 | CR to 38.101-1: 4 Rx support for n104 | Huawei, HiSilicon |
R4-2217089 | WF on 2Rx Exception for Band n104 | Apple |
TDoc | Title | Source |
---|---|---|
R4-2215668 | Issue for intra-band EN-DC combinations | Apple |
R4-2215933 | Issues on intra-bandENDC-Support | Nokia, Nokia Shanghai Bell |
R4-2215956 | The inconsistency issue for intra-band EN-DC band combinations | Ericsson |
R4-2216356 | Discussion on intrabandENDC-Support | Xiaomi |
R4-2216412 | Discussion on Intra-Band EN-DC band combinations | Google Inc., Comcast, CableLabs |
R4-2216421 | Draft CR for 38.101-3 Rel-16 intra-band contiguous EN-DC band combination | Google Inc., Comcast, CableLabs |
R4-2216427 | Draft CR for 38.101-3 Rel-17 intra-band contiguous EN-DC band combination | Google Inc., Comcast, CableLabs |
R4-2216443 | R16 Discussion on IntrabandENDC-Support capability handling | OPPO |
R4-2216617 | Discussion on intra band ENDC combination inconsistency issues | ZTE Corporation |
R4-2216656 | Discussion on intra-band EN-DC combination | Huawei, HiSilicon |
R4-2216657 | [DRAFT] LS on intra-band EN-DC combination | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2215334 | Impact of NS mapping between RAN2 and RAN4 specs on n77 issue | Nokia, Nokia Shanghai Bell |
R4-2215527 | Introduction of intra band NC UL CA in the n77 frequency range in Canada [n77 Canada] | Nokia, Nokia Shanghai Bell |
R4-2215794 | Discussion on additionalSpectrumEmission for NS mapping and CRs associated with Canada and US band n77 | Mediatek India Technology Pvt. |
R4-2216063 | Discussion on NS mapping for intra-band UL CA | Huawei, HiSilicon |
R4-2216649 | Remove network signalling labels for CA_NS and CA_NC_NS | Qualcomm Incorporated |
R4-2216650 | Remove network signalling labels for CA_NS and CA_NC_NS | Qualcomm Incorporated |
R4-2217761 | Introduction of intra band NC UL CA in the n77 frequency range in Canada [n77 Canada] | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2215498 | Motivation on NR CA band combinations with dual SUL bands in Rel-18 | CMCC |
R4-2215499 | New WID on NR CA band combinations with dual SUL bands in Rel-18 | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2216431 | R18 Motivation of high capability evolution for handheld UE | OPPO |
R4-2216432 | R18 New WI on high capability evolution for handheld UE | OPPO |
R4-2216555 | Discussion on Demod requirements for NCR-MT in Rel-18 | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2217304 | (reserved) | BSRF_Demod_Testing Session |
R4-2217514 | (reserved) | BSRF_Demod_Testing Session |
R4-2217518 | (reserved) | BSRF_Demod_Testing Session |
R4-2217519 | (reserved) | BSRF_Demod_Testing Session |
R4-2217520 | (reserved) | BSRF_Demod_Testing Session |
R4-2217521 | (reserved) | BSRF_Demod_Testing Session |
R4-2217522 | (reserved) | BSRF_Demod_Testing Session |
R4-2217523 | (reserved) | BSRF_Demod_Testing Session |
R4-2217524 | (reserved) | BSRF_Demod_Testing Session |
R4-2217525 | (reserved) | BSRF_Demod_Testing Session |
R4-2217526 | (reserved) | BSRF_Demod_Testing Session |
R4-2217527 | (reserved) | BSRF_Demod_Testing Session |
R4-2217528 | (reserved) | BSRF_Demod_Testing Session |
R4-2217529 | (reserved) | BSRF_Demod_Testing Session |
R4-2217530 | (reserved) | BSRF_Demod_Testing Session |
R4-2217531 | (reserved) | BSRF_Demod_Testing Session |
R4-2217532 | (reserved) | BSRF_Demod_Testing Session |
R4-2217533 | (reserved) | BSRF_Demod_Testing Session |
R4-2217534 | (reserved) | BSRF_Demod_Testing Session |
R4-2217535 | (reserved) | BSRF_Demod_Testing Session |
R4-2217536 | (reserved) | BSRF_Demod_Testing Session |
R4-2217537 | (reserved) | BSRF_Demod_Testing Session |
R4-2217538 | (reserved) | BSRF_Demod_Testing Session |
R4-2217539 | (reserved) | BSRF_Demod_Testing Session |
R4-2217540 | (reserved) | BSRF_Demod_Testing Session |
R4-2217541 | (reserved) | BSRF_Demod_Testing Session |
R4-2217542 | (reserved) | BSRF_Demod_Testing Session |
R4-2217543 | (reserved) | BSRF_Demod_Testing Session |
R4-2217544 | (reserved) | BSRF_Demod_Testing Session |
R4-2217545 | (reserved) | BSRF_Demod_Testing Session |
R4-2217546 | (reserved) | BSRF_Demod_Testing Session |
R4-2217547 | (reserved) | BSRF_Demod_Testing Session |
R4-2217548 | (reserved) | BSRF_Demod_Testing Session |
R4-2217549 | (reserved) | BSRF_Demod_Testing Session |
R4-2217550 | (reserved) | BSRF_Demod_Testing Session |
R4-2217551 | (reserved) | BSRF_Demod_Testing Session |
R4-2217552 | (reserved) | BSRF_Demod_Testing Session |
R4-2217553 | (reserved) | BSRF_Demod_Testing Session |
R4-2217554 | (reserved) | BSRF_Demod_Testing Session |
R4-2217555 | (reserved) | BSRF_Demod_Testing Session |
R4-2217556 | (reserved) | BSRF_Demod_Testing Session |
R4-2217557 | (reserved) | BSRF_Demod_Testing Session |
R4-2217558 | (reserved) | BSRF_Demod_Testing Session |
R4-2217559 | (reserved) | BSRF_Demod_Testing Session |
R4-2217560 | (reserved) | BSRF_Demod_Testing Session |
R4-2217561 | (reserved) | BSRF_Demod_Testing Session |
R4-2217562 | (reserved) | BSRF_Demod_Testing Session |
R4-2217563 | (reserved) | BSRF_Demod_Testing Session |
R4-2217564 | (reserved) | BSRF_Demod_Testing Session |
R4-2217565 | (reserved) | BSRF_Demod_Testing Session |
R4-2217566 | (reserved) | BSRF_Demod_Testing Session |
R4-2217567 | (reserved) | BSRF_Demod_Testing Session |
R4-2217568 | (reserved) | BSRF_Demod_Testing Session |
R4-2217569 | (reserved) | BSRF_Demod_Testing Session |
R4-2217570 | (reserved) | BSRF_Demod_Testing Session |
R4-2217571 | (reserved) | BSRF_Demod_Testing Session |
R4-2217572 | (reserved) | BSRF_Demod_Testing Session |
R4-2217573 | (reserved) | BSRF_Demod_Testing Session |
R4-2217574 | (reserved) | BSRF_Demod_Testing Session |
R4-2217575 | (reserved) | BSRF_Demod_Testing Session |
R4-2217576 | (reserved) | BSRF_Demod_Testing Session |
R4-2217577 | (reserved) | BSRF_Demod_Testing Session |
R4-2217578 | (reserved) | BSRF_Demod_Testing Session |
R4-2217579 | (reserved) | BSRF_Demod_Testing Session |
R4-2217580 | (reserved) | BSRF_Demod_Testing Session |
R4-2217581 | (reserved) | BSRF_Demod_Testing Session |
R4-2217582 | (reserved) | BSRF_Demod_Testing Session |
R4-2217594 | (reserved) | RRM Session |
R4-2217595 | (reserved) | RRM Session |
R4-2217596 | (reserved) | RRM Session |
R4-2217597 | (reserved) | RRM Session |
R4-2217598 | (reserved) | RRM Session |
R4-2217599 | (reserved) | RRM Session |
R4-2217600 | (reserved) | RRM Session |
R4-2217601 | (reserved) | RRM Session |
R4-2217602 | (reserved) | RRM Session |
R4-2217603 | (reserved) | RRM Session |
R4-2217604 | (reserved) | RRM Session |
R4-2217605 | (reserved) | RRM Session |
R4-2217606 | (reserved) | RRM Session |
R4-2217607 | (reserved) | RRM Session |
R4-2217608 | (reserved) | RRM Session |
R4-2217609 | (reserved) | RRM Session |
R4-2217610 | (reserved) | RRM Session |
R4-2217611 | (reserved) | RRM Session |
R4-2217612 | (reserved) | RRM Session |
R4-2217613 | (reserved) | RRM Session |
R4-2217614 | (reserved) | RRM Session |
R4-2217615 | (reserved) | RRM Session |
R4-2217616 | (reserved) | RRM Session |
R4-2217617 | (reserved) | RRM Session |
R4-2217618 | (reserved) | RRM Session |
R4-2217619 | (reserved) | RRM Session |
R4-2217620 | (reserved) | RRM Session |
R4-2217621 | (reserved) | RRM Session |
R4-2217622 | (reserved) | RRM Session |
R4-2217623 | (reserved) | RRM Session |
R4-2217624 | (reserved) | RRM Session |
R4-2217625 | (reserved) | RRM Session |
R4-2217626 | (reserved) | RRM Session |
R4-2217627 | (reserved) | RRM Session |
R4-2217628 | (reserved) | RRM Session |
R4-2217629 | (reserved) | RRM Session |
R4-2217630 | (reserved) | RRM Session |
R4-2217631 | (reserved) | RRM Session |
R4-2217632 | (reserved) | RRM Session |
R4-2217633 | (reserved) | RRM Session |
R4-2217634 | (reserved) | RRM Session |
R4-2217635 | (reserved) | RRM Session |
R4-2217636 | (reserved) | RRM Session |
R4-2217637 | (reserved) | RRM Session |
R4-2217638 | (reserved) | RRM Session |
R4-2217639 | (reserved) | RRM Session |
R4-2217640 | (reserved) | RRM Session |
R4-2217641 | (reserved) | RRM Session |
R4-2217642 | (reserved) | RRM Session |
R4-2217643 | (reserved) | RRM Session |
R4-2217644 | (reserved) | RRM Session |
R4-2217645 | (reserved) | RRM Session |
R4-2217646 | (reserved) | RRM Session |
R4-2217647 | (reserved) | RRM Session |
R4-2217648 | (reserved) | RRM Session |
R4-2217649 | (reserved) | RRM Session |
R4-2217650 | (reserved) | RRM Session |
R4-2217651 | (reserved) | RRM Session |
R4-2217652 | (reserved) | RRM Session |
R4-2217653 | (reserved) | RRM Session |
R4-2217654 | (reserved) | RRM Session |
R4-2217655 | (reserved) | RRM Session |
R4-2217656 | (reserved) | RRM Session |
R4-2217657 | (reserved) | RRM Session |
R4-2217658 | (reserved) | RRM Session |
R4-2217659 | (reserved) | RRM Session |
R4-2217660 | (reserved) | RRM Session |
R4-2217661 | (reserved) | RRM Session |
R4-2217662 | (reserved) | RRM Session |
R4-2217663 | (reserved) | RRM Session |
R4-2217664 | (reserved) | RRM Session |
R4-2217665 | (reserved) | RRM Session |
R4-2217666 | (reserved) | RRM Session |
R4-2217667 | (reserved) | RRM Session |
R4-2217668 | (reserved) | RRM Session |
R4-2217669 | (reserved) | RRM Session |
R4-2217670 | (reserved) | RRM Session |
R4-2217671 | (reserved) | RRM Session |
R4-2217672 | (reserved) | RRM Session |
R4-2217673 | (reserved) | RRM Session |
R4-2217674 | (reserved) | RRM Session |
R4-2217675 | (reserved) | RRM Session |
R4-2217676 | (reserved) | RRM Session |
R4-2217677 | (reserved) | RRM Session |
R4-2217678 | (reserved) | RRM Session |
R4-2217679 | (reserved) | RRM Session |
R4-2217680 | (reserved) | RRM Session |
R4-2217681 | (reserved) | RRM Session |
R4-2217682 | (reserved) | RRM Session |
R4-2217683 | (reserved) | RRM Session |
R4-2217684 | (reserved) | RRM Session |
R4-2217685 | (reserved) | RRM Session |
R4-2217686 | (reserved) | RRM Session |
R4-2217687 | (reserved) | RRM Session |
R4-2217688 | (reserved) | RRM Session |
R4-2217689 | (reserved) | RRM Session |
R4-2217690 | (reserved) | RRM Session |
R4-2217691 | (reserved) | RRM Session |
R4-2217692 | (reserved) | RRM Session |
R4-2217815 | (reserved) | Main Session |
R4-2217816 | (reserved) | Main Session |
R4-2217817 | (reserved) | Main Session |
R4-2217818 | (reserved) | Main Session |
R4-2217819 | (reserved) | Main Session |
R4-2217820 | (reserved) | Main Session |
R4-2217821 | (reserved) | Main Session |
R4-2217822 | (reserved) | Main Session |
R4-2217823 | (reserved) | Main Session |
R4-2217824 | (reserved) | Main Session |
R4-2217825 | (reserved) | Main Session |
R4-2217826 | (reserved) | Main Session |
R4-2217827 | (reserved) | Main Session |
R4-2217828 | (reserved) | Main Session |
R4-2217829 | (reserved) | Main Session |
R4-2217830 | (reserved) | Main Session |
R4-2217831 | (reserved) | Main Session |
R4-2217832 | (reserved) | Main Session |
R4-2217833 | (reserved) | Main Session |
R4-2217834 | (reserved) | Main Session |
R4-2217835 | (reserved) | Main Session |
R4-2217836 | (reserved) | Main Session |
R4-2217837 | (reserved) | Main Session |
R4-2217838 | (reserved) | Main Session |
R4-2217839 | (reserved) | Main Session |
R4-2217840 | (reserved) | Main Session |
R4-2217841 | (reserved) | Main Session |
R4-2217842 | (reserved) | Main Session |