| TDoc | Title | Source |
|---|---|---|
| R4-2500001 | RAN4#113 Meeting Report | ETSI MCC |
| R4-2500002 | Agenda for RAN4#114 | RAN4 Chair (Huawei) |
| R4-2500003 | RAN4#114 Meeting Arrangements and Guidelines | RAN4 Chair (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500004 | LS on Rel-18 RAN1 UE features list for NR after RAN1#119 | RAN1 |
| R4-2500005 | Reply to RAN4 LS on UE RF issues for Rel-19 MIMO Enhancement | RAN1 |
| R4-2500006 | LS on impact on transmit signal quality/MPR requirement | RAN1 |
| R4-2500007 | Reply LS on the scenarios of UE-to-UE CLI measurement report in SBFD operation | RAN1 |
| R4-2500008 | LS on collision between SSB and RA occasion for LTM | RAN1 |
| R4-2500009 | LS to RAN4 on event-instance evaluation periodicity for UE-initiated/event-driven beam management | RAN1 |
| R4-2500010 | Reply LS on SSB relation in On-demand SSB and SSB adaptation on Scell | RAN1 |
| R4-2500011 | Reply LS to R2-2407921/ R1-2407559 | RAN2 |
| R4-2500012 | LS on soft satellite switch with re-sync | RAN2 |
| R4-2500013 | RAN2 agreements on Inter-CU LTM and Conditional LTM | RAN2 |
| R4-2500014 | LS on UE Capabilities for FR2-NTN | RAN2 |
| R4-2500015 | Reply LS on RAN3 vs RAN2 Basketball Match | RAN3 |
| R4-2500016 | LS on HPUE MSD application for DL CA with 1UL CC | RAN |
| R4-2500017 | Reply LS on Head Phantom for XR devices OTA testing | CTIA OTA NFP |
| R4-2503079 | Parameters for 14 800 to 15 350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | ITU-R Working Party 5D |
| TDoc | Title | Source |
|---|---|---|
| R4-2500653 | Topic summary for [114][101] Upto_R16_UERF_maintenance | Moderator(OPPO) |
| R4-2500654 | Topic summary for [114][102] R17_UERF_maintenance | Moderator(Mediatek) |
| R4-2502980 | WF on UE requirements for PHS protection | KDDI, OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500515 | Topic summary for [114][201] Maintenance_up_to_R16 | Moderator (Xiaomi) |
| R4-2500516 | Topic summary for [114][202] Maintenance_R17 | Moderator (Huawei) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500562 | Topic summary for [114][301] BSRF_Maintenance | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500162 | A-MPR re-evaluation on n1 for updated emission requirements | Huawei, HiSilicon |
| R4-2500213 | (NR_newRAT-Core) Further study on NR A-MPR reevaluation scenarios on n1 for Japan | KDDI Corporation |
| R4-2500247 | FR2 TX requirements verification in beam locked mode | Apple |
| R4-2500248 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2500249 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2500250 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2500251 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2500283 | (NR_newRAT-Core) On NS_05 reevaluation | Apple |
| R4-2500349 | CR 36.101 R16 Removal of brackets | Nokia |
| R4-2500350 | CR 36.101 R17 Removal of brackets | Nokia |
| R4-2500351 | CR 36.101 R18 Removal of brackets | Nokia |
| R4-2500352 | CR 36.101 R19 Removal of brackets | Nokia |
| R4-2500353 | CR 36.101 Correction of CA_40-42 R19 | Nokia |
| R4-2500354 | CR 36.101 Correction of CA_40-42 R18 | Nokia |
| R4-2500355 | CR 36.101 Correction of CA_40-42 R17 | Nokia |
| R4-2500356 | CR 36.101 Correction of CA_40-42 R16 | Nokia |
| R4-2500357 | CR 36.101 Correction of CA_40-42 R15 | Nokia |
| R4-2500358 | CR for TS 36.101 Remove the spurious emission requirements for band combinations coexisting with PHS system R18 [PHS_System] | Nokia, Samsung, KDDI, NTT DOCOMO |
| R4-2500359 | CR for TS 36.101 Remove the spurious emission requirements for band combinations coexisting with PHS system R19 [PHS_System] | Nokia, Samsung, KDDI, NTT DOCOMO |
| R4-2500396 | (5G_V2X_NRSL-Core) CR to 38.101-1 Rel-16 Cat-F for 7.3E Reference sensitivity for V2X | CAICT |
| R4-2500419 | (NR_newRAT-Core) CR on 38.101-3 Specifying different inter band EN-DC UE capability types | Huawei, Samsung |
| R4-2500421 | n1 NS_05 A-MPR proposals | Nokia |
| R4-2500483 | LS on ambiguity with maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16 | Qualcomm Incorporated |
| R4-2500487 | (NR_newRAT-Core) n1 NS_05 and NS_05U PC3 A-MPR proposal | Qualcomm Incorporated |
| R4-2500488 | (NR_newRAT-Core) n1 NS_05 and NS_05U PC3 A-MPR re-evaluations | Qualcomm Incorporated |
| R4-2500499 | CR to TS 38.101-2 on MPR correction for FR2 intra-band contiguous CA | Samsung |
| R4-2500500 | CR to TS 38.101-2 on MPR correction for FR2 intra-band contiguous CA | Samsung |
| R4-2500501 | CR to TS 38.101-2 on MPR correction for FR2 intra-band contiguous CA | Samsung |
| R4-2500502 | CR to TS 38.101-2 on MPR correction for FR2 intra-band contiguous CA | Samsung |
| R4-2500801 | LS to RAN2 on modifiedMPR-Behaviour | Samsung |
| R4-2500802 | (NR_newRAT-Core, TEI18) Rel-19 CR for TS 38.101-3 Remove the spurious emission requirements for band combinations coexisting with PHS system | Samsung, KDDI, Nokia, Ericsson, Apple |
| R4-2500955 | (NR_newRAT-Core) Correct the modified MPR behavior | ZTE Corporation, Sanechips |
| R4-2500956 | (NR_newRAT-Core) Correct the modified MPR behavior | ZTE Corporation, Sanechips |
| R4-2500957 | (NR_newRAT-Core) Correct the modified MPR behavior | ZTE Corporation, Sanechips |
| R4-2500958 | (NR_newRAT-Core) Correct the modified MPR behavior | ZTE Corporation, Sanechips |
| R4-2500959 | (NR_newRAT-Core) Correct the modified MPR behavior | ZTE Corporation, Sanechips |
| R4-2500960 | (NR_newRAT-Core) Correct the modified MPR behavior in Annex H | ZTE Corporation, Sanechips |
| R4-2500961 | (NR_newRAT-Core) Correct the modified MPR behavior in Annex H | ZTE Corporation, Sanechips |
| R4-2500962 | (NR_newRAT-Core) Correct the modified MPR behavior in Annex H | ZTE Corporation, Sanechips |
| R4-2500963 | (NR_newRAT-Core) Correct the modified MPR behavior in Annex H | ZTE Corporation, Sanechips |
| R4-2501490 | R16 n1 NS_05 PC2 and PC3 AMPR | OPPO |
| R4-2501491 | R16 n1 NS_05U PC2 and PC3 AMPR | OPPO |
| R4-2501557 | A-MPR for NS_05/NS_05U and optionality in earlier releases. | Ericsson |
| R4-2501558 | (NR_newRAT-Core) Modification of additional requirements indicated by NS_05/NS_05U | Ericsson, Samsung |
| R4-2501559 | (NR_newRAT-Core) Modification of additional requirements indicated by NS_05/NS_05U | Ericsson, Samsung |
| R4-2501560 | (NR_newRAT-Core) Modification of additional requirements indicated by NS_05/NS_05U | Ericsson, Samsung |
| R4-2501561 | (NR_newRAT-Core) Modification of additional requirements indicated by NS_05/NS_05U | Ericsson, Samsung |
| R4-2501562 | (NR_newRAT-Core) Modification of additional requirements indicated by NS_05/NS_05U | Ericsson, Samsung |
| R4-2501629 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on reference sensitivity for intra-band contiguous and inter-band EN-DC configurations | ZTE Corporation, Sanechips |
| R4-2501630 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on reference sensitivity for intra-band contiguous and inter-band EN-DC configurations_R17_CAT_A | ZTE Corporation, Sanechips |
| R4-2501631 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on reference sensitivity for intra-band contiguous and inter-band EN-DC configurations_R18_CAT_A | ZTE Corporation, Sanechips |
| R4-2501632 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on reference sensitivity for intra-band contiguous and inter-band EN-DC configurations_R19_CAT_A | ZTE Corporation, Sanechips |
| R4-2501688 | (5G_V2X_NRSL-Core) CR on PC3 A-MPR for NS_33 (R16) | LG Electronics |
| R4-2501695 | (5G_V2X_NRSL-Core) CR on SL MIMO configuration (R16) | LG Electronics |
| R4-2501702 | (5G_V2X_NRSL-Core) CR on SL MIMO configuration (R17) | LG Electronics |
| R4-2501707 | (5G_V2X_NRSL-Core) CR on SL MIMO configuration (R18) | LG Electronics |
| R4-2501709 | (5G_V2X_NRSL-Core) CR on SL MIMO configuration (R19) | LG Electronics |
| R4-2501736 | Clarification of modifiedMPR-behaviour for n1 | NTT DOCOMO INC. |
| R4-2501816 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2501817 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2501818 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2501819 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2501820 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2502022 | (LTE410_Europe_PPDR-Core) CR to TS 36.101: UTRA ACLR exceptions | Qualcomm Incorporated |
| R4-2502023 | (LTE410_Europe_PPDR-Core) CR to TS 36.101: UTRA ACLR exceptions | Qualcomm Incorporated |
| R4-2502024 | (LTE410_Europe_PPDR-Core) CR to TS 36.101: UTRA ACLR exceptions | Qualcomm Incorporated |
| R4-2502025 | (LTE410_Europe_PPDR-Core) CR to TS 36.101: UTRA ACLR exceptions | Qualcomm Incorporated |
| R4-2502074 | (NR_n259-Core) CR to add missing in-band blocking requirement for n259 intra-band contiguous CA | NTT DOCOMO INC. |
| R4-2502075 | (NR_n259-Core) CR to add missing in-band blocking requirement for n259 intra-band contiguous CA | NTT DOCOMO INC. |
| R4-2502076 | (NR_n259-Core) CR to add missing in-band blocking requirement for n259 intra-band contiguous CA | NTT DOCOMO INC. |
| R4-2502077 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2502078 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2502079 | CR on adding beam locked mode for some TX requirements | Apple |
| R4-2502080 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
| R4-2502236 | On the requirements of modifiedMPR-Behavior | Huawei, HiSilicon |
| R4-2502919 | (5G_V2X_NRSL-Core) CR on SL MIMO configuration (R16) | LG Electronics |
| R4-2502978 | LS on ambiguity with maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16 | Qualcomm Incorporated |
| R4-2502979 | LS to RAN2 on modifiedMPR-Behaviour | Samsung |
| R4-2502996 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| R4-2502998 | (LTE410_Europe_PPDR-Core) CR to TS 36.101: UTRA ACLR exceptions | Qualcomm Incorporated |
| R4-2503029 | CR for TS 38.101-3 to correct Test BW configuration of DC_5A-7A_n78A MSD | Samsung, Anritsu |
| TDoc | Title | Source |
|---|---|---|
| R4-2500320 | (NR_NTN_solutions) CR to 38.101-5 to clarify applicability of phase continuity requirements in R17 | Apple |
| R4-2500360 | CR 38.101-1 R17 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
| R4-2500361 | CR 38.101-1 R18 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
| R4-2500362 | CR 38.101-1 R19 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
| R4-2500380 | (NR_RF_TxD-Core) Replacement of dual Tx with 2Tx and single Tx with 1Tx | Huawei, HiSilicon |
| R4-2500381 | (NR_RF_TxD-Core) Replacement of dual Tx with 2Tx and single Tx with 1Tx | Huawei, HiSilicon |
| R4-2500382 | (NR_RF_TxD-Core) Replacement of dual Tx with 2Tx and single Tx with 1Tx | Huawei, HiSilicon |
| R4-2500422 | (NR_newRAT-Core) CR on 38.101-3 Specifying different inter band EN-DC UE capability types (R17_CAT_A) | Huawei, Samsung |
| R4-2500475 | Rel-17 Minor correction in PC6 UL-MIMO Maximum Output Power requirements [NR_HST_FR2-Core] | Keysight Technologies UK Ltd |
| R4-2500476 | (NR_HST_FR2-Core) Rel-18 Minor correction in PC6 UL-MIMO Maximum Output Power requirements | Keysight Technologies UK Ltd |
| R4-2501050 | Remaining issues on enabling HPUE CA with 1UL | CATT |
| R4-2501051 | (Power_Limit_CA_DC-Core) CR to TS 38.101-1 on DL CA HPUE with 1UL (Cat-F) | CATT |
| R4-2501052 | (Power_Limit_CA_DC-Core) CR to TS 38.101-1 on DL CA HPUE with 1UL (Cat-A) | CATT |
| R4-2501563 | (Power_Limit_CA_DC) Specification of Pcmax for the serving cell of DL-only CA for HPUE | Ericsson |
| R4-2501564 | (Power_Limit_CA_DC) Specification of Pcmax for the serving cell of DL-only CA for HPUE | Ericsson |
| R4-2501565 | (Power_Limit_CA_DC) Specification of Pcmax for the serving cell of DL-only CA for HPUE | Ericsson |
| R4-2501566 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
| R4-2501567 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
| R4-2501568 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
| R4-2501581 | On UL RMC’s for SRS transmissions | Qualcomm France |
| R4-2501584 | (NR_CADC_R17_2BDL_xBUL) CR to clarify that sources of IMD coming from two CCs in clause 7.3A.5 can be from two bands or just a single band - TS38.101-1 | Anritsu Limited, CHTTL, SGS Wireless |
| R4-2501689 | (NR_SL_enh-Core) CR on A-MPR for NS_33 (R17) | LG Electronics |
| R4-2501690 | (NR_SL_enh-Core) CR on A-MPR for NS_33 (R18) | LG Electronics |
| R4-2501693 | (NR_SL_enh-Core) CR on A-MPR for NS_33 (R19) | LG Electronics |
| R4-2501847 | (Power_Limit_CA_DC-Core) CR to TS 38.101-1 on DL CA HPUE with 1UL (Cat-F) | CATT |
| R4-2501864 | (Power_Limit_CA_DC-Core) CR to TS 38.101-1: DL CA HPUE with 1UL (Cat-F) | CATT |
| R4-2502019 | (NR_redcap-Core) CR to TS 38.101-1: OOB blocking for RedCap UEs | Qualcomm Incorporated |
| R4-2502020 | (NR_redcap-Core) CR to TS 38.101-1: OOB blocking for RedCap UEs | Qualcomm Incorporated |
| R4-2502021 | (NR_redcap-Core) CR to TS 38.101-1: OOB blocking for RedCap UEs | Qualcomm Incorporated |
| R4-2502248 | (NR_NTN_solutions-Core) Maintenance CR on 38.101-5 - Removing NTN 256QAM from Rel-17 FR1-NTN | THALES |
| R4-2502944 | (NR_redcap-Core) CR to TS 38.101-1: OOB blocking for RedCap UEs | Qualcomm |
| R4-2502945 | (NR_CADC_R17_2BDL_xBUL) CR to clarify that sources of IMD coming from two CCs in clause 7.3A.5 can be from two bands or just a single band - TS38.101-1 | Anritsu Limited, CHTTL, SGS Wireless |
| R4-2502946 | (NR_HST_FR2-Core) Rel-17 Minor correction in PC6 UL-MIMO Maximum Output Power requirements | Keysight Technologies UK Ltd |
| R4-2502947 | (NR_NTN_solutions-Core) Maintenance CR on 38.101-5 - Removing NTN 256QAM from Rel-17 FR1-NTN | THALES |
| TDoc | Title | Source |
|---|---|---|
| R4-2500058 | CR to TS 38.141-1: Addition of test tolerance for BS total power dynamic range (CBWs 35 MHz and 45 MHz) | Ericsson |
| R4-2500059 | CR to TS 38.141-1: Addition of test tolerance for BS total power dynamic range (CBWs 35 MHz and 45 MHz) | Ericsson |
| R4-2500062 | (LTE-RF) CR to TS 36.141 on removal of references to empty Annex E | Nokia |
| R4-2500063 | (LTE-RF) CR to TS 36.141 on removal of references to empty Annex E | Nokia |
| R4-2500064 | (LTE-RF) CR to TS 36.141 on removal of references to empty Annex E | Nokia |
| R4-2500598 | ( NR_NTN_solutions-Core) CR to 38.181 Correct FRC naming for ICS requirement | ZTE Corporation, Sanechips |
| R4-2500599 | ( NR_NTN_solutions-Core) CR to 38.181 Correct FRC naming for ICS requirement | ZTE Corporation, Sanechips |
| R4-2500972 | Discussion on channel raster for band n102 | CATT |
| R4-2500973 | (NR_6GHz_unlic_EU-Core) CR for TS38.104: Correction on channel raster for band n102 | CATT |
| R4-2500974 | (NR_6GHz_unlic_EU-Core)CR for TS38.104: Correction on channel raster for band n102 | CATT |
| R4-2500975 | Discussion on adding HAPS abbreviation and definition of HAPS BS classes to TS38.141-1/2 | CATT |
| R4-2500976 | (NR_NTN_solutions)CR for TS38.141-1: Adding HAPS abbreviation and definition of HAPS BS class for conformance requirements | CATT |
| R4-2500977 | (NR_NTN_solutions)CR for TS38.141-1: Adding HAPS abbreviation and definition of HAPS BS class for conformance requirements | CATT |
| R4-2500978 | (NR_NTN_solutions)CR for TS38.141-2: Adding HAPS abbreviation and definition of HAPS BS class for conformance requirements | CATT |
| R4-2500979 | (NR_NTN_solutions)CR for TS38.141-2: Adding HAPS abbreviation and definition of HAPS BS class for conformance requirements | CATT |
| R4-2500980 | (NR_repeaters-Perf)CR for TS38.115-2: On mmWave EESS protection | CATT |
| R4-2500981 | (NR_repeaters-Perf)CR for TS38.115-2: On mmWave EESS protection | CATT |
| R4-2501000 | Maintenance CR to TS 38.115-2: NCR conformance part | CATT |
| R4-2501857 | (NR_newRAT-Perf) Correction to theta angle definition | Huawei, HiSilicon |
| R4-2501858 | (NR_newRAT-Perf) Correction to theta angle definition | Huawei, HiSilicon |
| R4-2501859 | (NR_newRAT-Perf) Correction to theta angle definition | Huawei, HiSilicon |
| R4-2501860 | (NR_newRAT-Perf) Correction to theta angle definition | Huawei, HiSilicon |
| R4-2502108 | (LTE410_Europe_PPDR-Perf) Introduction of missing blocking requirements for bands 87, 88 | Huawei, HiSilicon |
| R4-2502109 | (LTE410_Europe_PPDR-Perf) Introduction of missing blocking requirements for bands 87, 88 | Huawei, HiSilicon |
| R4-2502110 | (LTE410_Europe_PPDR-Perf) Introduction of missing blocking requirements for bands 87, 88 | Huawei, HiSilicon |
| R4-2502129 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502130 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502131 | (NR_RAIL_EU_900MHz-Perf, NR_RAIL_EU_1900MHz_TDD-Perf) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502132 | (NR_RAIL_EU_900MHz-Perf, NR_RAIL_EU_1900MHz_TDD-Perf) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502330 | (NR_repeaters-Perf)CR for TS38.115-2: On mmWave EESS protection | CATT |
| R4-2502331 | Maintenance CR to TS 38.115-2: NCR conformance part | CATT |
| R4-2502332 | NR_newRAT-Perf) Correction to theta angle definition | Huawei, HiSilicon |
| R4-2502333 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502334 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502335 | (NR_RAIL_EU_900MHz-Perf, NR_RAIL_EU_1900MHz_TDD-Perf) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502336 | (NR_RAIL_EU_900MHz-Perf, NR_RAIL_EU_1900MHz_TDD-Perf) NB-IoT operation modes clarification for FRMCS BS in multi-carrier operation | Huawei, HiSilicon |
| R4-2502354 | (NR_repeaters-Perf)CR for TS38.115-2: On mmWave EESS protection | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500252 | (NR_RRM_Enh-Core) On gradual timing adjustment and MTTD for CA and DC | Apple |
| R4-2500253 | (NR_newRAT-core) CR to 38.133 for gradual timing adjustment and MTTD-R15 | Apple |
| R4-2500254 | (NR_RRM_Enh-Core) CR to 38.133 for gradual timing adjustment and MTTD-R16 | Apple |
| R4-2500255 | (NR_RRM_Enh-Core) CR to 38.133 for gradual timing adjustment and MTTD-R17 | Apple |
| R4-2500256 | (NR_RRM_Enh-Core) CR to 38.133 for gradual timing adjustment and MTTD-R18 | Apple |
| R4-2500444 | Discussion on RRM measurement on deactivated SCC | Apple |
| R4-2500445 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R15 | Apple |
| R4-2500446 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R16 | Apple |
| R4-2500447 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R17 | Apple |
| R4-2500448 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R18 | Apple |
| R4-2500449 | (NR_RRM_enh-Perf) CR for test case of active BWP switch - R16 | Apple |
| R4-2500450 | (NR_RRM_Enh-Perf) CR on A.4.6.6.1 for EN-DC intra-frequency CGI identification - R16 | Apple |
| R4-2500451 | (NR_RRM_Enh-Perf) CR on A.4.6.6.1 for EN-DC intra-frequency CGI identification - R17 | Apple |
| R4-2500452 | (NR_RRM_Enh-Perf) CR on A.4.6.6.1 for EN-DC intra-frequency CGI identification - R18 | Apple |
| R4-2500831 | CR on requirements for DCI based BWP switch delay on multiple CCs (R16) | vivo |
| R4-2500832 | CR on requirements for DCI based BWP switch delay on multiple CCs (R17) | vivo |
| R4-2500833 | CR on requirements for DCI based BWP switch delay on multiple CCs (R18) | vivo |
| R4-2500915 | (NR_newRAT-Core) CR on R15 CSI-RS based RLM&BFD | ZTE Corporation, Sanechips |
| R4-2500916 | (NR_newRAT-Core) CR on R15 CSI-RS based RLM&BFD | ZTE Corporation, Sanechips |
| R4-2500917 | (NR_newRAT-Core) CR on R15 CSI-RS based RLM&BFD | ZTE Corporation, Sanechips |
| R4-2500918 | (NR_newRAT-Core) CR on R15 CSI-RS based RLM&BFD | ZTE Corporation, Sanechips |
| R4-2500919 | (LTE_NR_DC_CA_enh-Core) CR on R16 EMR | ZTE Corporation, Sanechips |
| R4-2500920 | (LTE_NR_DC_CA_enh-Core) CR on R16 EMR | ZTE Corporation, Sanechips |
| R4-2500921 | (LTE_NR_DC_CA_enh-Core) CR on R16 EMR | ZTE Corporation, Sanechips |
| R4-2500922 | (NR_UE_pow_sav-Core) CR on R16 measurement relaxation for low mobility | ZTE Corporation, Sanechips |
| R4-2500923 | (NR_UE_pow_sav-Core) CR on R16 measurement relaxation for low mobility | ZTE Corporation, Sanechips |
| R4-2500924 | (NR_UE_pow_sav-Core) CR on R16 measurement relaxation for low mobility | ZTE Corporation, Sanechips |
| R4-2500925 | (NR_unlic-Core) CR on R16 CSSF_outside gap for SA scenario | ZTE Corporation, Sanechips |
| R4-2500926 | (NR_unlic-Core) CR on R16 CSSF_outside gap for SA scenario | ZTE Corporation, Sanechips |
| R4-2500927 | (NR_unlic-Core) CR on R16 CSSF_outside gap for SA scenario | ZTE Corporation, Sanechips |
| R4-2501198 | (NR_RF_FR1-Perf) Correction to Rel-16 Tx switching RRM test cases_R16 | Huawei, HiSilicon |
| R4-2501199 | (NR_RF_FR1-Perf) Correction to Rel-16 Tx switching RRM test cases_R17 | Huawei, HiSilicon |
| R4-2501200 | (NR_RF_FR1-Perf) Correction to Rel-16 Tx switching RRM test cases_R18 | Huawei, HiSilicon |
| R4-2501204 | (NR_unlic-Perf) CR on maintenance for NR-U 36.133 R16 | Huawei, HiSilicon |
| R4-2501205 | (NR_unlic-Perf) CR on maintenance for NR-U 36.133 R17 | Huawei, HiSilicon |
| R4-2501206 | (NR_unlic-Perf) CR on maintenance for NR-U 36.133 R18 | Huawei, HiSilicon |
| R4-2501240 | (NR_newRAT-Core) CR on RRC connection release with redirection | Huawei, HiSilicon |
| R4-2501241 | (NR_newRAT-Core) CR on RRC connection release with redirection R16 | Huawei, HiSilicon |
| R4-2501242 | (NR_newRAT-Core) CR on RRC connection release with redirection R17 | Huawei, HiSilicon |
| R4-2501243 | (NR_newRAT-Core) CR on RRC connection release with redirection R18 | Huawei, HiSilicon |
| R4-2501275 | (NR_newRAT-Perf) CR on the correction of band group notations in the SSB_RP and SSB conditions tables R15 | Huawei, HiSilicon |
| R4-2501276 | (NR_newRAT-Perf) CR on the correction of band group notations in the SSB_RP and SSB conditions tables R16 | Huawei, HiSilicon |
| R4-2501277 | (NR_newRAT-Perf) CR on the correction of band group notations in the SSB_RP and SSB conditions tables R17 | Huawei, HiSilicon |
| R4-2501278 | (NR_newRAT-Perf) CR on the correction of band group notations in the SSB_RP and SSB conditions tables R18 | Huawei, HiSilicon |
| R4-2501279 | (NR_newRAT-Perf)CR on the correction of band group notations in the accuracy requirements tables R16 | Huawei, HiSilicon |
| R4-2501280 | (NR_newRAT-Perf)CR on the correction of band group notations in the accuracy requirements tables R17 | Huawei, HiSilicon |
| R4-2501281 | (NR_newRAT-Perf)CR on the correction of band group notations in the accuracy requirements tables R18 | Huawei, HiSilicon |
| R4-2501298 | Clarification on mandatory gap patterns in Rel-16 | Ericsson |
| R4-2501468 | (NR_RRM_enh-Core)Correction on RRC based BWP switch delay for multiple CCs | Samsung |
| R4-2501469 | (NR_RRM_enh-Core)Correction on RRC based BWP switch delay for multiple CCs | Samsung |
| R4-2501470 | (NR_RRM_enh-Core)Correction on RRC based BWP switch delay for multiple CCs | Samsung |
| R4-2501710 | (NR_newRAT-Perf) CR to TS 38.133: Corrections to NR RRM test cases (Rel 15) | Rohde & Schwarz |
| R4-2501711 | (NR_newRAT-Perf) CR to TS 38.133: Corrections to NR RRM test cases (Rel 16) | Rohde & Schwarz |
| R4-2501712 | (NR_newRAT-Perf) CR to TS 38.133: Corrections to NR RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2501713 | (NR_newRAT-Perf) CR to TS 38.133: Corrections to NR RRM test cases (Rel 18) | Rohde & Schwarz |
| R4-2501714 | (NR_unlic-Perf) CR to TS 38.133: Corrections to NR-U RRM test cases (Rel 16) | Rohde & Schwarz |
| R4-2501715 | (NR_unlic-Perf) CR to TS 38.133: Corrections to NR-U RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2501716 | (NR_unlic-Perf) CR to TS 38.133: Corrections to NR-U RRM test cases (Rel 18) | Rohde & Schwarz |
| R4-2501717 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 16) | Rohde & Schwarz |
| R4-2501718 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 17) | Rohde & Schwarz |
| R4-2501719 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 18) | Rohde & Schwarz |
| R4-2501887 | (NR_newRAT-Core) CR clarifying the UE UL transmit timing requirements | Nokia |
| R4-2501888 | (NR_newRAT-Core) CR clarifying the UE UL transmit timing requirements | Nokia |
| R4-2501889 | (NR_newRAT-Core) CR clarifying the UE UL transmit timing requirements | Nokia |
| R4-2501890 | (NR_newRAT-Core) CR clarifying the UE UL transmit timing requirements | Nokia |
| R4-2501922 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters | Keysight Technologies UK Ltd |
| R4-2501923 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters (Rel 16) | Keysight Technologies |
| R4-2501925 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters (Rel 17) | Keysight Technologies |
| R4-2501926 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters (Rel 18) | Keysight Technologies |
| R4-2501945 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters | Keysight Technologies |
| R4-2502184 | (NR_RF_FR1) CR on TC for DL interruptions at switching between two uplink carriers in FDD-TDD CA (R16) | MediaTek inc. |
| R4-2502185 | (NR_RF_FR1) CR on TC for DL interruptions at switching between two uplink carriers in FDD-TDD CA (R17) | MediaTek inc. |
| R4-2502186 | (NR_RF_FR1) CR on TC for DL interruptions at switching between two uplink carriers in FDD-TDD CA (R18) | MediaTek inc. |
| R4-2502251 | (NR_unlic-Perf) Correction CR for A.12.5.1.1 | Qualcomm Incorporated |
| R4-2502257 | (NR_unlic-Perf) Correction CR for A.12.5.1.1 | Qualcomm Incorporated |
| R4-2502258 | (NR_unlic-Perf) Correction CR for A.12.5.1.1 | Qualcomm Incorporated |
| R4-2502609 | (NR_RRM_enh-Perf) CR for test case of active BWP switch - R16 | Apple |
| R4-2502612 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 16) | Rohde & Schwarz |
| R4-2502634 | (NR_newRAT-Perf) Corrections in A.4.7.1.2 and A.6.7.1.2 on derived parameters | Keysight Technologies |
| R4-2502635 | (NR_RRM_enh-Core)Correction on RRC based BWP switch delay for multiple CCs | Samsung |
| R4-2502636 | (LTE_NR_DC_CA_enh-Core) CR on R16 EMR | ZTE Corporation, Sanechips |
| R4-2502637 | (NR_RF_FR1) CR on TC for DL interruptions at switching between two uplink carriers in FDD-TDD CA (R16) | MediaTek inc. |
| R4-2502665 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R15 | Apple |
| R4-2502691 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 16) | Rohde & Schwarz |
| R4-2502695 | (NR_UE_pow_sav-Core) CR on R16 measurement relaxation for low mobility | ZTE Corporation, Sanechips |
| R4-2502696 | (NR_newRAT-Core) CR for RRM measurement on deactivated SCC - R15 | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500453 | (NR_MG_enh-Core) CR on RRM requirements for NCSG - R17 | Apple |
| R4-2500454 | (NR_MG_enh-Core) CR on RRM requirements for NCSG - R18 | Apple |
| R4-2500709 | (NR_RRM_enh2) Correction on NR PSCell Addition Delay requirements | ZTE Corporation, Sanechips |
| R4-2500710 | (NR_RRM_enh2) Correction on NR PSCell Addition Delay requirements | ZTE Corporation, Sanechips |
| R4-2500834 | (NR_SL_enh-Core) CR on correction of wrong indentation for Selection / Reselection of V2X Synchronization Reference Source | LG Electronics Inc. |
| R4-2500835 | (NR_SL_enh-Core) CR on correction of wrong indentation for Selection / Reselection of V2X Synchronization Reference Source | LG Electronics Inc. |
| R4-2500838 | CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
| R4-2500839 | CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
| R4-2500928 | (NR_MG_enh-Core) CR on the interruption of deactivated SCell measurement when NCSG is configured | ZTE Corporation, Sanechips |
| R4-2500929 | (NR_MG_enh-Core) CR on the interruption of deactivated SCell measurement when NCSG is configured | ZTE Corporation, Sanechips |
| R4-2500930 | (NR_redcap-Core) CR on R17 CSI-RS based RLM&BFD for Redcap | ZTE Corporation, Sanechips |
| R4-2500931 | (NR_redcap-Core) CR on R17 CSI-RS based RLM&BFD for Redcap | ZTE Corporation, Sanechips |
| R4-2500932 | (NR_RRM_enh2-Core) CR on R17 handover with PSCell change | ZTE Corporation, Sanechips |
| R4-2500933 | (NR_RRM_enh2-Core) CR on R17 handover with PSCell change | ZTE Corporation, Sanechips |
| R4-2501010 | (NR_ext_to_71GHz-Perf) CR to TS 38.133 on test cases in FR2-2 with CCA | CATT |
| R4-2501011 | (NR_ext_to_71GHz-Perf) CR to TS 38.133 on test cases in FR2-2 with CCA | CATT |
| R4-2501187 | (NR_NTN_solutions-Core) Correction on NR NTN in RRC connected state_R17 | ZTE Corporation, Sanechips |
| R4-2501188 | (NR_NTN_solutions-Core) Correction on NR NTN in RRC connected state_R18 | ZTE Corporation, Sanechips |
| R4-2501201 | (NR_RF_FR1_enh-Perf) Correction to Rel-17 Tx switching RRM test cases_R17 | Huawei, HiSilicon |
| R4-2501202 | (NR_RF_FR1_enh-Perf) Correction to Rel-17 Tx switching RRM test cases_R18 | Huawei, HiSilicon |
| R4-2501207 | (NR_feMIMO-Perf) CR on maintenance for unified TCI TC R17 | Huawei, HiSilicon |
| R4-2501208 | (NR_feMIMO-Perf) CR on maintenance for unified TCI TC R18 | Huawei, HiSilicon |
| R4-2501209 | (NR_RRM_enh2-Perf) CR on TC maintenance for PUCCH Scell activation R17 | Huawei, HiSilicon |
| R4-2501210 | (NR_RRM_enh2-Perf) CR on TC maintenance for PUCCH Scell activation R18 | Huawei, HiSilicon |
| R4-2501237 | (NR_redcap-Core) Correction to TA validation requirements for RedCap R17 | Huawei, HiSilicon |
| R4-2501244 | (NR_SmallData_INACTIVE-Core) CR on CG-SDT requirements | Huawei, HiSilicon |
| R4-2501245 | (NR_SmallData_INACTIVE-Core) CR on CG-SDT requirements R18 | Huawei, HiSilicon |
| R4-2501246 | (NR_MG_enh-Core) Discussion on gap sharing for NCSG | Huawei, HiSilicon |
| R4-2501247 | (NR_pos_enh-Core) CR on requirements for PRS measurement outside MG | Huawei, HiSilicon |
| R4-2501248 | (NR_pos_enh-Core) CR on requirements for PRS measurement outside MG R18 | Huawei, HiSilicon |
| R4-2501720 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 17) | Rohde & Schwarz |
| R4-2501721 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 18) | Rohde & Schwarz |
| R4-2501722 | (NR_NTN_solutions-Perf) CR to TS 38.133: Corrections to NR NTN RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2501723 | (NR_NTN_solutions-Perf) CR to TS 38.133: Corrections to NR NTN RRM test cases (Rel 18) | Rohde & Schwarz |
| R4-2501724 | (NR_redcap-Perf) CR to TS 38.133: Corrections to RedCap RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2501725 | (NR_redcap-Perf) CR to TS 38.133: Corrections to RedCap RRM test cases (Rel 18) | Rohde & Schwarz |
| R4-2501752 | (NR_pos_enh-Perf) CAT-F CR to 38.133 on performance requirement for PRS-RSRP and UE Rx-Tx measurements | Ericsson |
| R4-2501753 | (NR_pos_enh-Perf) CAT-A CR to 38.133 on performance requirement for PRS-RSRP and UE Rx-Tx measurements | Ericsson |
| R4-2501891 | (NR_newRAT-Core) NR-E-UTRAN HO delay requirement maintenance | Nokia |
| R4-2501892 | (NR_newRAT-Core) CR on NR-E-UTRAN HO delay requirement maintenance | Nokia |
| R4-2501893 | (NR_newRAT-Core) CR on NR-E-UTRAN HO delay requirement maintenance | Nokia |
| R4-2501913 | (NR_redcap-Perf) Corrections in A.16.7.1.3 and A.16.7.1.4 on derived parameters | Keysight Technologies |
| R4-2501916 | (NR_redcap-Perf) Corrections in A.16.7.1.3 and A.16.7.1.4 on derived parameters (Rel 18) | Keysight Technologies |
| R4-2501917 | (NR_NTN_solutions-Perf) Remove NR NTN testing scenarios for BFR in SCell | Keysight Technologies, Nokia |
| R4-2501921 | (NR_NTN_solutions-Perf) Remove NR NTN testing scenarios for BFR in SCell (Rel 18) | Keysight Technologies, Nokia |
| R4-2502212 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-F Rel-17) | Qualcomm Incorporated |
| R4-2502213 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-A Rel-18) | Qualcomm Incorporated |
| R4-2502214 | (NR_NTN_solutions-Perf) CR on NTN test cases for FR1 SAN (Cat-F Rel-17) | Qualcomm Incorporated |
| R4-2502215 | (NR_NTN_solutions-Perf) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-A Rel-18) | Qualcomm Incorporated |
| R4-2502610 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 17) | Rohde & Schwarz |
| R4-2502613 | (NR_NTN_solutions-Perf) CR to TS 38.133: Corrections to NR NTN RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2502638 | (NR_RRM_enh2) Correction on NR PSCell Addition Delay requirements | ZTE Corporation, Sanechips |
| R4-2502639 | (NR_RRM_enh2-Core) CR on R17 handover with PSCell change | ZTE Corporation, Sanechips |
| R4-2502640 | CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
| R4-2502641 | (NR_MG_enh-Core) CR on the interruption of deactivated SCell measurement when NCSG is configured | ZTE Corporation, Sanechips |
| R4-2502642 | (NR_ext_to_71GHz-Perf) CR to TS 38.133 on test cases in FR2-2 with CCA | CATT |
| R4-2502643 | (NR_NTN_solutions-Perf) CR to TS 38.133: Corrections to NR NTN RRM test cases (Rel 17) | Rohde & Schwarz |
| R4-2502644 | (NR_feMIMO-Perf) CR on maintenance for unified TCI TC R17 | Huawei, HiSilicon |
| R4-2502645 | (NR_SmallData_INACTIVE-Core) CR on CG-SDT requirements R18 | Huawei, HiSilicon |
| R4-2502686 | Draft CR38.133 Addition of definition for gap association | Nokia |
| R4-2502690 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 17) | Rohde & Schwarz |
| TDoc | Title | Source |
|---|---|---|
| R4-2500052 | (NR_demod_enh2-Perf) CR for TS38.101-4, corrections on configurations for CQI reporting with inter-cell interference | MediaTek inc., Huawei, HiSilicon |
| R4-2500053 | (NR_demod_enh2-Perf) CR for TS38.101-4, corrections on configurations for CQI reporting with inter-cell interference | MediaTek inc., Huawei, HiSilicon |
| R4-2500163 | (NR_perf_enh-Perf) CR to CQI-PMI-RI Delay in 6.2A.3.1.1 Test1 | Anritsu Corporation |
| R4-2500164 | (NR_perf_enh-Perf) CR to CQI-PMI-RI Delay in 6.2A.3.1.1 Test1 | Anritsu Corporation |
| R4-2500165 | (NR_perf_enh-Perf) CR to CQI-PMI-RI Delay in 6.2A.3.1.1 Test1 | Anritsu Corporation |
| R4-2500257 | (NR_newRAT-perf) CR to 38.101-4 for PT-RS config-R15 | Apple |
| R4-2500258 | (NR_perf_enh-Perf) CR to 38.101-4 for PT-RS config-R16 | Apple |
| R4-2500259 | (NR_perf_enh-Perf) CR to 38.101-4 for PT-RS config-R17 | Apple |
| R4-2500260 | (NR_perf_enh-Perf) CR to 38.101-4 for PT-RS config-R18 | Apple |
| R4-2500278 | (NR_newRAT-Perf) Editorial CR to 38.101-4 on PDCCH requirements in FR2-R15 | Apple |
| R4-2500279 | (NR_newRAT-Perf) Editorial CR to 38.101-4 on PDCCH requirements in FR2-R16 | Apple |
| R4-2500280 | (NR_newRAT-Perf) Editorial CR to 38.101-4 on PDCCH requirements in FR2-R17 | Apple |
| R4-2500281 | (NR_newRAT-Perf) Editorial CR to 38.101-4 on PDCCH requirements in FR2-R18 | Apple |
| R4-2500493 | [NR_demod_enh2-Perf] CR to 38.101-4 on clarifying test specifications for CQI reporting with inter-cell interference | Qualcomm |
| R4-2500497 | (NR_demod_enh2-Perf) CR to 38.101-4 on clarifying test specifications for CQI reporting with inter-cell interference | Qualcomm |
| R4-2501312 | (NR_newRAT-Perf) 38.101-4 Information on FRC changes to maximum throughput | Nokia, Rohde&Schwarz, Keysight |
| R4-2501313 | (NR_demod_enh2-Perf) CR for 38.101-4 on Correction to FRC tables | Nokia |
| R4-2501314 | (NR_demod_enh2-Perf) CR for 38.101-4 on Correction to FRC tables | Nokia |
| R4-2501317 | (NR_ext_to_71GHz-Perf) CR for 38.101-4 on Correcting duplicate FRC names | Nokia |
| R4-2501318 | (NR_ext_to_71GHz-Perf) CR for 38.101-4 on Correcting duplicate FRCs | Nokia |
| R4-2501521 | CR on 38.101-4 Modification on the general statement for FR2 CSI test(R17) | Huawei, HiSilicon |
| R4-2501522 | CR on 38.101-4: Modification on the general statement for FR2 CSI test | Huawei, HiSilicon |
| R4-2501524 | CR on 38.101-4 Further clarification on DMRS sequence configuration for tests with interference(R17) | Huawei, HiSilicon |
| R4-2501525 | CR on 38.101-4 Further clarification on DMRS sequence configuration for tests with interference(R18) | Huawei, HiSilicon |
| R4-2501534 | (NR_newRAT-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501535 | (NR_newRAT-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501536 | (NR_newRAT-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501537 | (NR_newRAT-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501538 | (NR_perf_enh-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501539 | (NR_perf_enh-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501540 | (NR_perf_enh-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501541 | (NR_eMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501542 | (NR_eMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501543 | (NR_eMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501544 | (NR_FeMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501545 | (NR_FeMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501546 | (NR_redcap-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501547 | (NR_redcap-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2501549 | (NR_perf_enh-Perf) CR on UE CA demodulation requirements | Huawei, HiSilicon |
| R4-2501550 | (NR_perf_enh-Perf) CR on UE CA demodulation requirements | Huawei, HiSilicon |
| R4-2501909 | (NR_newRAT-Perf) CR to TS38101-4 Correction on the test numbering of PDCCH requirements | Ericsson |
| R4-2501910 | (NR_newRAT-Perf) CR to TS38101-4 Correction on the test numbering of PDCCH requirements | Ericsson |
| R4-2501911 | (NR_newRAT-Perf) CR to TS38101-4 Correction on the test numbering of PDCCH requirements | Ericsson |
| R4-2501912 | (NR_newRAT-Perf) CR to TS38101-4 Correction on the test numbering of PDCCH requirements | Ericsson |
| R4-2502033 | (NR_newRAT-Perf)Correction CR on performance requirements for PUCCH in TS 38.104 | Samsung |
| R4-2502034 | (NR_newRAT-Perf)Correction CR on performance requirements for PUCCH in TS 38.104 | Samsung |
| R4-2502035 | (NR_newRAT-Perf)Correction CR on performance requirements for PUCCH in TS 38.104 | Samsung |
| R4-2502036 | (NR_newRAT-Perf)Correction CR on performance requirements for PUCCH in TS 38.104 | Samsung |
| R4-2502037 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-1 | Samsung |
| R4-2502038 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-1 | Samsung |
| R4-2502039 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-1 | Samsung |
| R4-2502040 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-1 | Samsung |
| R4-2502041 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-2 | Samsung |
| R4-2502042 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-2 | Samsung |
| R4-2502043 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-2 | Samsung |
| R4-2502044 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-2 | Samsung |
| R4-2502045 | (NR_NTN_solutions-Perf)Correction CR on SAN performance requirements in TS 38.108 | Samsung |
| R4-2502046 | (NR_NTN_solutions-Perf)Correction CR on SAN performance requirements in TS 38.108 | Samsung |
| R4-2502048 | (NR_NTN_solutions-Perf)Correction CR on SAN performance requirements in TS 38.181 | Samsung |
| R4-2502263 | (NR_newRAT-Perf)Correction CR on performance requirements for PUCCH in TS 38.104 | Samsung |
| R4-2502264 | ( Correction CR on performance requirements for PUCCH in TS 38.141-1 | Samsung |
| R4-2502265 | (NR_newRAT-Perf)Correction CR on performance requirement for PUCCH in TS 38141-2 | Samsung |
| R4-2502266 | (NR_NTN_solutions-Perf)Correction CR on SAN performance requirements in TS 38.108 | Samsung |
| R4-2502268 | ( Correction CR on SAN performance requirements in TS 38.181 | Samsung |
| R4-2502325 | (NR_eMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2502326 | (NR_perf_enh-Perf) CR to CQI-PMI-RI Delay in 6.2A.3.1.1 Test1 | Anritsu Corporation |
| R4-2502327 | (NR_perf_enh-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2502328 | (NR_perf_enh-Perf) CR on UE CA demodulation requirements | Huawei, HiSilicon |
| R4-2502356 | (NR_demod_enh2-Perf) CR to 38.101-4 on clarifying test specifications for CQI reporting with inter-cell interference | Qualcomm |
| R4-2502359 | CR on 38.101-4 Modification on the general statement for FR2 CSI test(R17) | Huawei, HiSilicon |
| R4-2502360 | (NR_newRAT-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2502361 | (NR_FeMIMO-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2502362 | (NR_redcap-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| R4-2502363 | (NR_NTN_solutions-Perf)Correction CR on SAN performance requirements in TS 38.108 | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500462 | (TEI16) CR on 38.101-1 clarification of maximum transmission bandwidth configuration [Max_Tx_BW_config] | Huawei, Hisilicon |
| R4-2500463 | (TEI16) CR on 38.101-1 clarification of maximum transmission bandwidth configuration [Max_Tx_BW_config] | Huawei, Hisilicon |
| R4-2500464 | (TEI16) CR on 38.101-1 clarification of maximum transmission bandwidth configuration [Max_Tx_BW_config] | Huawei, Hisilicon |
| R4-2500473 | (TEI16) CR on 38.101-1 clarification of maximum transmission bandwidth configuration [Max_Tx_BW_config] | Huawei, Hisilicon |
| R4-2502927 | CR on 38.101-1 clarification of maximum transmission bandwidth configuration | Huawei, Hisilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500655 | Topic summary for [114][103] R18_UERF_maintenance_Part1 | Moderator(Xiaomi) |
| R4-2500656 | Topic summary for [114][104] R18_UERF_maintenance_Part2 | Moderator(Huawei) |
| R4-2502994 | WF on FR2 PC8 UE | Huawei |
| R4-2503000 | LS on NB-IoT NTN in-band operation with NR NTN | Ericsson |
| R4-2503008 | LS on 3MHz support for (e)RedCap | Nokia |
| R4-2503035 | LS on NR NB-IoT in-band operation | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500517 | Topic summary for [114][203] Maintenance_R18 | Moderator (Apple) |
| R4-2500518 | Topic summary for [114][204] NR_MG_enh2 | Moderator (MediaTek) |
| R4-2500519 | Topic summary for [114][205] NR_NTN_enh | Moderator (Qualcomm) |
| R4-2500520 | Topic summary for [114][206] NR_pos_enh2 | Moderator (Ericsson) |
| R4-2500521 | Topic summary for [114][207] NR_Mob_enh2 | Moderator (MediaTek) |
| R4-2500522 | Topic summary for [114][208] Netw_Energy_NR | Moderator (Huawei) |
| R4-2500523 | Topic summary for [114][209] RRM_Spec_Improvement | Moderator (Apple) |
| R4-2502581 | WF on RRM requirements for NR_MG_enh2 | MediaTek |
| R4-2502582 | WF on RRM requirements for NR_NTN_enh | Qualcomm |
| R4-2502583 | WF on RRM requirements for NR_pos_enh2 | Ericsson |
| R4-2502584 | WF on RRM requirements for NR_Mob_enh2 | MediaTek |
| R4-2502585 | WF on RRM requirements for Netw_Energy_NR | Huawei |
| R4-2502618 | Reply LS to RAN1 on collision between SSB and RA occasion for LTM | MediaTek |
| R4-2502619 | LS on UE capability for L1-RSRP measurement in LTM | vivo |
| R4-2502681 | Reply LS on soft satellite switch with re-sync | Huawei |
| R4-2502687 | WF on RRM requirements for NR_NTN_enh | Qualcomm |
| R4-2502694 | LS on neighboring cell measurement for Rel-18 SSB-less | ZTE |
| R4-2502698 | WF on RRM requirements for NR_pos_enh2 | Ericsson |
| R4-2502701 | Reply LS on soft satellite switch with re-sync | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R4-2500581 | Topic summary for [114][320] Demod_Maintenance_Part1 | Moderator (Nokia) |
| R4-2500582 | Topic summary for [114][321] Demod_Maintenance_Part2 | Moderator (Apple) |
| R4-2500587 | Topic summary for [114][326] OTA_Maintenance | Moderator (Keysight) |
| R4-2502312 | Adhoc minutes for [114][320] Demod_Maintenance_Part1 | Moderator (Nokia) |
| R4-2502313 | Ad-hoc meeting minutes for [114][321] Demod_Maintenance_Part2 | Moderator (Apple) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500040 | (HPUE_FR1_DC_LTE_NR_R18) Correction on HP-ENDC combination of 1A_n3A-n77A | SoftBank Corp. |
| R4-2500284 | (NR_NTN_solutions-Core) Corrections to TR 38.863 to align with TS 38.101-5 | Apple, Thales, Echostar, Aalyria Technologies |
| R4-2500285 | (NR_NTN_solutions-Core) Corrections to TR 38.863 to align with TS 38.101-5 | Apple, Thales, Echostar, Aalyria Technologies |
| R4-2500286 | (NR_unlic_enh-Core) Corrections to the 6GHz unlicensed band NS flags | Apple, Charter Communications |
| R4-2500287 | (NR_unlic_enh-Core) Corrections to the 6GHz unlicensed band NS flags | Apple, Charter Communications |
| R4-2500288 | (NR_unlic_enh-Core) Corrections to the 6GHz unlicensed band NS flags | Apple |
| R4-2500871 | CR for TS 38.101-1 to add the missing information on the maximum output power of CA_n41C-n79C | CMCC |
| R4-2500872 | CR for TS 38.101-1 to add the missing information on the maximum output power of CA_n41C-n79C | CMCC |
| R4-2500982 | Discussion on sync raster for band n254 for NTN | CATT |
| R4-2500983 | (NR_NTN_LSband-Core)CR for TS 38.108, Correction on sync raster for band n254 for NTN | CATT |
| R4-2500984 | (NR_NTN_LSband-Core)CR for TS 38.101-5, Correction on sync raster for band n254 for NTN | CATT |
| R4-2501151 | (IoT_NTN_FDD_LS_band) CR to TS 36.102 addressing incomplete Rel-18 requirements in clause 6.2B.3 | MediaTek (Hefei) Inc. |
| R4-2501153 | NS_04N/05N AMPR value for NB-IoT in IoT NTN band b254 | Sony |
| R4-2501163 | Discussion on UE RF A-MPR for B254 | MediaTek (Hefei) Inc. |
| R4-2501167 | (IoT_NTN_FDD_LS_band) CR to TR 36.764 for B254 UE RF 1-Tone A-MPR requirements (Rel-18) | MediaTek (Hefei) Inc. |
| R4-2501366 | (NR_RAIL_EU_900MHz, NR_UAV) CR to TS 38101-1 - Wrong references | Ericsson |
| R4-2501367 | (NR_RAIL_EU_900MHz, NR_UAV) CR to TS 38101-1 - Wrong references | Ericsson |
| R4-2501369 | (NR_FDD_ULn28_DLn75_n76-Core) CR to TS38104 - Wrong channel BW supported by n109 | Ericsson |
| R4-2501573 | Corrections to Harmonic Mixing UL allocations | Qualcomm France |
| R4-2501580 | On UE BW’s in MSD tables | Qualcomm France |
| R4-2501585 | (NR_CADC_R18_2BDL_xBUL) CR to clarify that sources of IMD coming from two CCs in section 7.3A.5 can be from two bands or just a single band - TS38.101-1 | Anritsu Limited, CHTTL, SGS Wireless |
| R4-2501586 | (NR_CADC_R18_2BDL_xBUL) CR to clarify that sources of IMD coming from two CCs in section 7.3A.5 can be from two bands or just a single band - TS38.101-1 | Anritsu Limited, CHTTL, SGS Wireless |
| R4-2501587 | (DC_R18_1BLTE_1BNR_2DL2UL) CR to to change the B66 DL test frequency of DC_66A_n77A/n41A/n38A in Tables 7.3B.2.3.4-1&1a from 2197.5MHz to 2177.5MHz - TS38.101-3 | Anritsu Limited |
| R4-2501588 | (DC_R18_1BLTE_1BNR_2DL2UL) CR to to change the B66 DL test frequency of DC_66A_n77A/n41A/n38A in Tables 7.3B.2.3.4-1&1a from 2197.5MHz to 2177.5MHz - TS38.101-3 | Anritsu Limited |
| R4-2501606 | (HPUE_NR_FR1_FDD_R18) CR for TS 38.101-1 to clarify A-MPR for NS_43 | Huawei,HiSilicon |
| R4-2501607 | (HPUE_NR_FR1_FDD_R18) CR for TS 38.101-1 to clarify A-MPR for NS_43 | Huawei,HiSilicon |
| R4-2501633 | (HPUE_FR1_TDD_NR_CADC_SUL_R18-Core) Corrections on single uplink carrier for inter-band CA configurations | ZTE Corporation, Sanechips |
| R4-2501634 | (HPUE_FR1_TDD_NR_CADC_SUL_R18-Core) Corrections on single uplink carrier for inter-band CA configurations_R19_CAT_A | ZTE Corporation, Sanechips |
| R4-2501635 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on inter-band CA reference sensitivity due to intermodulation interference | ZTE Corporation, Sanechips |
| R4-2501636 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on inter-band CA reference sensitivity due to intermodulation interference_R19_CAT_A | ZTE Corporation, Sanechips |
| R4-2501637 | (DC_R18_xBLTE_2BNR_yDL2UL-Core) Removal of redundant EN-DC configurations including FR1 and FR2 | ZTE Corporation, Sanechips |
| R4-2501638 | (DC_R18_xBLTE_2BNR_yDL2UL-Core) Removal of redundant EN-DC configurations including FR1 and FR2_R19_CAT_A | ZTE Corporation, Sanechips |
| R4-2501639 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on NR CA band for two bands between FR1 and FR2 | ZTE Corporation, Sanechips |
| R4-2501640 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on NR CA band for two bands between FR1 and FR2_R19_CAT_A | ZTE Corporation, Sanechips |
| R4-2501654 | Corrections to 2 3 and 4 NR CA configuration tabels | Nokia, BT plc |
| R4-2501655 | Corrections to 2 3 and 4 NR CA configuration tabels | Nokia, BT plc |
| R4-2501919 | Draft CR for TS 38.101-3 to correct MSD for DC_18A_n77A PC2 IMD | KDDI, Samsung |
| R4-2501920 | Draft CR for TS 38.101-1 to correct some typos and missing notes | KDDI, Samsung |
| R4-2501949 | (HPUE_FR1_TDD_NR_CADC_SUL_R18) Cat F CR for TS 38.101-1-i80 Corrections to PC2 harmonic MSD | Skyworks Solutions Inc. |
| R4-2501950 | (HPUE_FR1_TDD_NR_CADC_SUL_R18) Cat A CR for TS 38.101-1-j00 Corrections to PC2 harmonic MSD | Skyworks Solutions Inc. |
| R4-2502015 | (IoT_NTN_FDD_LS_band-Core) On completing band 254 requirements | Qualcomm Inc. |
| R4-2502948 | (NR_NTN_LSband-Core)CR for TS 38.101-5, Correction on sync raster for band n254 for NTN | CATT, Apple |
| R4-2502958 | Draft CR for TS 38.101-3 to correct MSD for DC_18A_n77A PC2 IMD | KDDI, Samsung |
| R4-2502959 | Draft CR for TS 38.101-1 to correct some typos and missing notes | KDDI, Samsung |
| R4-2502982 | (IoT_NTN_FDD_LS_band) CR to TR 36.764 for B254 UE RF 1-Tone A-MPR requirements (Rel-18) | MediaTek (Hefei) Inc. |
| R4-2502983 | (NR_NTN_solutions-Core) Corrections to TR 38.863 to align with TS 38.101-5 | Apple, Thales, Echostar, Aalyria Technologies |
| R4-2502984 | (NR_NTN_solutions-Core) Corrections to TR 38.863 to align with TS 38.101-5 | Apple, Thales, Echostar, Aalyria Technologies |
| R4-2502985 | (NR_NTN_LSband-Core)CR for TS 38.108, Correction on sync raster for band n254 for NTN | CATT, Apple |
| R4-2502986 | (NR_NTN_LSband-Core) CR for TR 38.741, Correction on sync raster for band n254 for NTN | Apple, CATT |
| R4-2502987 | (NR_CADC_R18_2BDL_xBUL) CR to clarify that sources of IMD coming from two CCs in section 7.3A.5 can be from two bands or just a single band - TS38.101-1 | Anritsu Limited, CHTTL, SGS Wireless |
| R4-2502988 | (DC_R18_1BLTE_1BNR_2DL2UL) CR to to change the B66 DL test frequency of DC_66A_n77A/n41A/n38A in Tables 7.3B.2.3.4-1&1a from 2197.5MHz to 2177.5MHz - TS38.101-3 | Anritsu Limited |
| R4-2502989 | Corrections to 2 3 and 4 NR CA configuration tabels | Nokia, BT plc |
| R4-2503031 | Draft CR for TS 38.101-3 to correct MSD for DC_18A_n77A PC2 IMD | KDDI, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2501827 | Removal of the exceptional raster point from Rel-18 NR band n28 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500365 | CR 38.101-1 Clarifications for non-collocated requirements R19 | Nokia, Samsung, Qualcomm, Huawei, Apple |
| R4-2500366 | CR 38.101-1 Clarifications for non-collocated requirements R18 | Nokia, Samsung, Qualcomm |
| R4-2500367 | CR 38.101-3 Clarification of collocation requirements R19 | Nokia, Samsung, Qualcomm, Huawei, Apple |
| R4-2500368 | CR 38.101-3 Clarification of collocation requirements R18 | Nokia, Samsung, Qualcomm |
| R4-2500369 | CR 38.101-3 Clarification of collocation requirements R17 | Nokia, Samsung, Qualcomm |
| R4-2500370 | CR 38.101-3 Clarification of collocation requirements R16 | Nokia, Samsung, Qualcomm |
| R4-2500418 | (NonCol_intraB_ENDC_NR_CA-Core) Specifying different intra-band non-contiguous CA UE capability types | Huawei, Samsung |
| R4-2500424 | (NonCol_intraB_ENDC_NR_CA-Core) Specifying different intra-band non-contiguous CA UE capability types (R18_CAT_A) | Huawei, Samsung |
| R4-2500439 | LS on clarification for UE type | Apple |
| R4-2501946 | (NonCol_intraB_ENDC_NR_CA-Core) Specifying different inter-band EN-DC UE capability types (R18_CAT_A) | Huawei, Samsung |
| R4-2501997 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) CR on 38.101-3 Specifying different inter band EN-DC UE capability types | Huawei, Samsung |
| R4-2501999 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) CR on 38.101-3 Specifying different inter band EN-DC UE capability types (R17_CAT_A) | Huawei, Samsung |
| R4-2502920 | CR 38.101-1 Clarifications for non-collocated requirements R18 | Nokia, Samsung, Qualcomm |
| R4-2502921 | CR 38.101-3 Clarification of collocation requirements R18 | Nokia, Samsung, Qualcomm |
| R4-2502922 | CR 38.101-3 Clarification of collocation requirements R16 | Nokia, Samsung, Qualcomm |
| R4-2502923 | CR 38.101-3 Clarification of collocation requirements R17 | Nokia, Samsung, Qualcomm |
| R4-2503032 | LS on clarification for UE type | Apple |
| R4-2503033 | LS on clarification for intraBandNR-CA-non-collocated-r18 and interBandMRDC-WithOverlapDL-Bands-r16 | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500443 | On ATG UE RF requirement applicability | Apple |
| R4-2500478 | Rel-18 Clarifications on some ATG requirements applicability per connector [NR_ATG-Core] | Keysight Technologies UK Ltd |
| R4-2500479 | Rel-19 Clarifications on some ATG requirements applicability per connector [NR_ATG-Core] | Keysight Technologies UK Ltd |
| R4-2500855 | CR for TS 38.101-1 on ATG UE antenna connector clarification | CMCC |
| R4-2500856 | CR for TS 38.101-1 on ATG UE antenna connector clarification | CMCC |
| R4-2501991 | (NR_ATG-Core) CR for 38101-1 on ATG Rx RF requirements | Apple |
| R4-2501992 | (NR_ATG-Core) ATG Tx requirements applicability per connector | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500840 | CR to TS 38.133 Correction of L1 sharing factor for Inter-frequency measurements without measurement gaps for ATG UE | CMCC |
| R4-2500934 | (NR_ATG-Core) CR on location-based CHO of R18 ATG | ZTE Corporation, Sanechips |
| R4-2501012 | (NR_ATG-Core) CR to TS 38.133 on core maintenance for R18 ATG | CATT |
| R4-2501138 | CR on Pre-MG requirements for ATG | OPPO |
| R4-2502646 | CR to TS 38.133 Correction of L1 sharing factor for Inter-frequency measurements without measurement gaps for ATG UE | CMCC |
| R4-2502648 | (NR_ATG-Core) CR on location-based CHO of R18 ATG | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2501424 | CR on applicability rules for Rel-18 ATG | Samsung |
| R4-2501501 | Discussion on R18 ATG HARQ k1 value | ZTE Corporation, Sanechips |
| R4-2501502 | CR on 38.101-4 for ATG demodulation requirements with k1 value | ZTE Corporation, Sanechips |
| R4-2502357 | LS on introduce a new capability for the R18 ATG feature | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R4-2500377 | Delta Ppowerclass and Delta TRxSRS for 4Tx | Huawei, HiSilicon |
| R4-2500378 | DeltaP_PowerClass correction for SRS AS for 4Tx | Huawei, HiSilicon |
| R4-2500379 | DeltaP_PowerClass correction for SRS AS for 4Tx | Huawei, HiSilicon |
| R4-2502187 | (NR_ENDC_RF_FR1_enh2-Core) On DeltaP_PowerClass for SRS-AS for 4Tx | Ericsson |
| R4-2502188 | (NR_ENDC_RF_FR1_enh2-Core) CR to 38.101 Rel-18: DeltaP_PowerClass correction for SRS-AS for 4Tx | Ericsson |
| R4-2502189 | (NR_ENDC_RF_FR1_enh2-Core) CR to 38.101 Rel-19: DeltaP_PowerClass correction for SRS-AS for 4Tx | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500131 | CR for TS38.101-4, corrections on codebook restriction for 8Rx CQI reporting requirements | MediaTek inc. |
| R4-2500132 | CR for TS38.101-4, applicability rules for 8Rx requirements | MediaTek inc. |
| R4-2501315 | (NR_ENDC_RF_FR1_enh2-Perf) CR for 38.101-4 on Correction to FRC tables | Nokia |
| R4-2501426 | CR on PDSCH Reference Channel for Rel-18 8Rx CA | Samsung |
| R4-2501520 | CR on 38.101-4: Modification on applicability rules and test setup for 8Rx requirements | Huawei, HiSilicon |
| R4-2501908 | CR to TS38101-4 Correction on the name of the 8Rx receiver | Ericsson |
| R4-2502329 | CR on PDSCH Reference Channel for Rel-18 8Rx CA | Samsung, Nokia |
| R4-2502358 | CR on 38.101-4: Modification on applicability rules and test setup for 8Rx requirements | Huawei, HiSilicon, MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R4-2500363 | CR 38.101-1 R18 Corection for ACS requirement for 3 MHz carrier | Nokia |
| R4-2500364 | CR 38.101-1 R19 Corection for ACS requirement for 3 MHz carrier | Nokia |
| R4-2500410 | PRB misalignment for 12 PRB on 3MHz and 20 PRB on 5MHz | Huawei, HiSilicon |
| R4-2503038 | CR 38.101-1 R19 Corection for ACS requirement for 3 MHz carrier | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500212 | CR to TS 38.141-1 to add 3MHz for occupied bandwidth test | Nokia |
| R4-2500596 | (NR_FR1_lessthan_5MHz_BW-Core) CR to TS38.104 Add NB-IoT RB power dynamic range for 3MHz | ZTE Corporation, Sanechips |
| R4-2500597 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS38.141-1 Add NB-IoT RB power dynamic range and occupied bandwidth requirement for 3MHz | ZTE Corporation, Sanechips |
| R4-2501364 | (NR_FR1_lessthan_5MHz_BW-Core) CR to TS 37104 - FoffsetRAT for NR 3MHz channel BW | Ericsson |
| R4-2501365 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS 37141 - FoffsetRAT for NR 3MHz channel BW | Ericsson |
| R4-2502337 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS38.141-1 Add NB-IoT RB power dynamic range and occupied bandwidth requirement for 3MHz | ZTE Corporation, Sanechips |
| R4-2502338 | (NR_FR1_lessthan_5MHz_BW-Core) CR to TS 37104 - FoffsetRAT for NR 3MHz channel BW | Ericsson |
| R4-2502339 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS 37141 - FoffsetRAT for NR 3MHz channel BW | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500711 | CR on test cases for NR_FR1_lessthan_5MHz_BW | ZTE Corporation, Sanechips |
| R4-2501249 | Discussion on RLM/BFD test cases in R18 less than 5MHz | Huawei, HiSilicon |
| R4-2501250 | CR on TCs for less than 5MHz BW | Huawei, HiSilicon |
| R4-2501975 | Discussion on RRM simulations for < 5MHz | Nokia |
| R4-2501976 | Summary of simulation results for RRM requirements for less than 5MHz | Nokia |
| R4-2502053 | Discussion on performance part for NR in less than 5 MHz bandwidth | Ericsson |
| R4-2502054 | CR to TS 38.133: Maintenance CR of SNR levels for RLM/BFD test cases | Ericsson |
| R4-2502069 | CR for Rel-18 Less Than 5MHz Performance part | Nokia |
| R4-2502073 | CR introducing test case for Radio Link Monitoring In-sync Test for FR1 PCell with 3MHz Channel Bandwidth configured with SSB-based RLM RS in DRX mode | Nokia |
| R4-2502088 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to R18 on Less than 5MHz Perf | MediaTek inc. |
| R4-2502089 | (NR_FR1_lessthan_5MHz_BW-Core) CR to R18 on Less than 5MHz | MediaTek inc. |
| R4-2502649 | Summary of simulation results for RRM requirements for less than 5MHz | Nokia |
| R4-2502650 | CR for Rel-18 Less Than 5MHz Performance part | Nokia, Ericsson, Huawei, HiSilicon, MediaTek, ZTE, Sanechip, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R4-2501425 | CR on applicability rules for Rel-18 less than 5MHz BW | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500766 | CR on Remove GSM_ACLR for NB-Iot based Iot-NTN | vivo, Huawei, MediaTek |
| R4-2501194 | (LTE_NBIOT_eMTC_NTN_req-Core) CR to TS 36.102 on variable TX-RX frequency separation | MediaTek (Hefei) Inc. |
| R4-2502001 | CR to TS 36.102: B255 emissions | Qualcomm Incorporated |
| R4-2502002 | CR to TS 36.307: Flexible Tx-Rx spacing for NB-IoT and eMTC over NTN | Qualcomm Incorporated |
| R4-2502140 | CR on Remove GSM_ACLR for NB-Iot based Iot-NTN | vivo, Huawei, MediaTek |
| R4-2502990 | (LTE_NBIOT_eMTC_NTN_req-Core) CR to TS 36.102 on variable TX-RX frequency separation | MediaTek (Hefei) Inc. |
| R4-2502991 | CR to TS 36.102: B255 emissions | Qualcomm Incorporated |
| R4-2502992 | CR to TS 36.307: Flexible Tx-Rx spacing for NB-IoT and eMTC over NTN | Qualcomm Incorporated |
| R4-2502993 | CR on Remove GSM_ACLR for NB-Iot based Iot-NTN | vivo, Huawei, MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R4-2500985 | Discussion on figures and definitions related to non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2500986 | (LTE_NBIOT_eMTC_NTN_req-Core) CR for TS36.108, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2500987 | (LTE_NBIOT_eMTC_NTN_req-Perf) CR for TS36.181, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2502344 | (LTE_NBIOT_eMTC_NTN_req-Core) CR for TS36.108, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2502345 | (LTE_NBIOT_eMTC_NTN_req-Perf) CR for TS36.181, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2502368 | (LTE_NBIOT_eMTC_NTN_req-Core) CR for TS36.108, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| R4-2502369 | (LTE_NBIOT_eMTC_NTN_req-Perf) CR for TS36.181, Correction on non-regenerative payload and gateway for IoT NTN | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500392 | CR on core maintenance for R18 IoT NTN | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500133 | Discussion on applicability rules for IoT-NTN requirements | MediaTek inc. |
| R4-2500134 | CR for TS36.102, applicability rules for IoT-NTN requirements | MediaTek inc. |
| R4-2500166 | Discussion on the Note in Table 8.2.1.2-1 of TS 36.102 | Anritsu Corporation |
| R4-2502355 | CR for TS36.102, applicability rules for IoT-NTN requirements | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2501407 | On remaining Rel-18 multi-Rx issues | Nokia |
| R4-2502145 | CR for Rel-18 multi-Rx test case maintenance | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500261 | CR to 38.101-4 for PT-RS config for requirements with multi-RX in FR2 | Apple |
| R4-2500509 | [NR_FR2_multiRX_DL-Perf] CR to 38.101-4 on correcting table numbers for reference measurement channels | QUALCOMM Europe Inc. - Spain |
| R4-2501316 | (NR_FR2_multiRX_DL-Perf) CR for 38.101-4 on Correcting FRC tables | Nokia |
| R4-2502322 | (NR_FR2_multiRX_DL-Perf) CR for 38.101-4 on Correcting FRC tables | Nokia, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R4-2501132 | CR on SCell Activation Delay requirement with the L3 reporting | OPPO |
| R4-2501212 | Discussion on requirements maintenance for Rel-18 eFeRRM SCell activation | Huawei, HiSilicon |
| R4-2501213 | (NR_RRM_enh3-Core) CR on core requirements maintenance for R18 eFeRRM multiple SCell activation | Huawei, HiSilicon |
| R4-2501214 | (NR_RRM_enh3-Perf) CR on TC maintenance for Rel-18 eFeRRM | Huawei, HiSilicon |
| R4-2501592 | CR on R18 RRM_enh3 core requirements | vivo |
| R4-2502055 | Discussion on SR based test case setup for L3 report based SCell activation | Ericsson |
| R4-2502056 | CR to 38.133: Addition of sub test using SR for SCell action with valid L3 results | Ericsson |
| R4-2502068 | 38.133 CR on PUCCH SCell activation with L3 report | Nokia, Nokia Shanghai Bell |
| R4-2502651 | CR on R18 RRM_enh3 core requirements | vivo |
| R4-2502652 | 38.133 CR on PUCCH SCell activation with L3 report | Nokia, Nokia Shanghai Bell, OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500902 | Discussion on the maintenance of core part for Case 2 | ZTE Corporation, Sanechips |
| R4-2500935 | (NR_MG_enh2-Core) CR on Case 2 of R18 Concurrent MGs | ZTE Corporation, Sanechips |
| R4-2501104 | CR on concurrent gaps with NCSG | CMCC |
| R4-2501105 | (NR_MG_enh2-Core) Discussion on concurrent gaps with NCSG | CMCC |
| R4-2501139 | Discussion on the remaining issues for further MG enhancements | OPPO |
| R4-2501140 | CR on core requirements of further MG enhancements | OPPO |
| R4-2501251 | Discussion on remaining issues for R18 MG Enhancement | Huawei, HiSilicon |
| R4-2501252 | CR on requirements for inter-RAT measurement without gap | Huawei, HiSilicon |
| R4-2501299 | Remaining issues on MG further enhancement | Ericsson |
| R4-2501300 | (NR_MG_enh2-Core) CR on 38.133 MG enh2 on NCSGs | Ericsson |
| R4-2501419 | CR on interruption during inter-RAT NR measurements without measurement gap | OPPO |
| R4-2502086 | Discussion on remaining issues for MGE2 | MediaTek inc. |
| R4-2502087 | (NR_MG_enh2-Perf) CR on MGE2 R18 performance | MediaTek inc. |
| R4-2502143 | CR to TS 38133 on NeedForInterruption | Nokia |
| R4-2502144 | CR to TS 36133 interruption requirements for interRAT measurements without gaps | Nokia |
| R4-2502171 | (NR_MG_enh2-Perf) CR on MGE2 R18 performance | MediaTek inc. |
| R4-2502237 | Discussion on missing Case 2 requirements | Nokia |
| R4-2502239 | CR38.133 Corrections to Case 2 requirements | Nokia |
| R4-2502242 | CR38.133 Corrections to CSSF requirements | Nokia |
| R4-2502670 | (NR_MG_enh2-Core) CR on 38.133 MG enh2 on NCSGs | Ericsson, Nokia, CMCC, OPPO |
| R4-2502671 | CR on interruption during inter-RAT NR measurements without measurement gap | OPPO, Nokia |
| R4-2502672 | (NR_MG_enh2-Perf) CR on MGE2 R18 performance | MediaTek inc. |
| R4-2502673 | CR to TS 38133 on NeedForInterruption | Nokia, OPPO |
| R4-2502674 | CR38.133 Corrections to CSSF requirements | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2501137 | CR on handover requirements for BWP without restriction | OPPO |
| R4-2502653 | CR on handover requirements for BWP without restriction | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2501239 | (NR_HST_FR2_enh-Core) Correction on inter-frequency cell identification without gap requirements for FR2 HST | Huawei, HiSilicon |
| R4-2502654 | (NR_HST_FR2_enh-Core) Correction on inter-frequency cell identification without gap requirements for FR2 HST | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2501791 | DraftCR on Spectrum Analiser configuration | ROHDE & SCHWARZ, vivo |
| R4-2502366 | DraftCR on Spectrum Analiser configuration | ROHDE & SCHWARZ, vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500485 | (NR_demod_enh3-Perf) Correct Measurement Channel for Requirements in Section 5.6 | Qualcomm Incorporated |
| R4-2502323 | (NR_demod_enh3-Perf) Correct Measurement Channel for Requirements in Section 5.6 | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500964 | (NR_MC_enh-Core) Correct the capability name for Tx switching | ZTE Corporation, Sanechips |
| R4-2500965 | ( NR_MC_enh-Core) Correct the capability name for Tx switching | ZTE Corporation, Sanechips |
| R4-2501412 | (NR_MC_enh-Core) Correct the capability name for Tx switching | ZTE Corporation, Sanechips |
| R4-2501432 | ( NR_MC_enh-Core) Correct the capability name for Tx switching | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500829 | Further discussion on UE capability and requirements for multi-carrier enhancements | vivo |
| R4-2500830 | CR on BWP switching requirements for multi-carrier enhancements | vivo |
| R4-2501203 | (NR_MC_enh-Perf) Correction to multi-carrier enhancement RRM test cases_R18 | Huawei, HiSilicon |
| R4-2501297 | Discussion on multiple BWP switching with dormancy Scells | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500397 | (NR_SL_enh2-Core) CR to 38.101-1 Rel-18 Cat-F for 7.6E.3.1A Out-of-band blocking for Sidelink CA | CAICT |
| R4-2500398 | (NR_SL_enh2-Core) CR to 38.101-1 Rel-19 Cat-A for 7.6E.3.1A Out-of-band blocking for Sidelink CA | CAICT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500836 | (NR_SL_enh2-Core) CR on correction of wrong indentation for Selection / Reselection of Sidelink Synchronization Reference Source with CCA | LG Electronics Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2501523 | CR on 38.101-4 Modification on test setups for R18 sidelink requirements | Huawei, HiSilicon |
| R4-2502365 | CR on 38.101-4 Modification on test setups for R18 sidelink requirements | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500486 | On 200 MHz BW and 2 layer MIMO capabilities | Qualcomm Incorporated |
| R4-2501053 | (NR_NTN_enh-Core) CR for TS 38.101-5 Correction on FR2-NTN frequency range | CATT |
| R4-2501054 | (NR_NTN_enh-Core) CR for TS 38.108 Correction on FR2-NTN frequency range | CATT |
| R4-2501370 | (NR_NTN_solutions) Doppler shift issues for guard band and transmission bandwidth configuration | Ericsson |
| R4-2501446 | (NR_NTN_enh-Core) Discussion on potential solution on Doppler shift issues for guard band and transmission bandwidth configuration | Huawei, HiSilicon |
| R4-2501447 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues for guard band and transmission bandwidth configuration | Huawei, HiSilicon |
| R4-2501448 | (NR_NTN_enh-Core) Discussion and draft replied LS on the FR2-NTN UE capabilities for 200Mhz channel bandwidth and 2 MIMO layers | Huawei, HiSilicon |
| R4-2501826 | draft LS reply on UE Capabilities for FR2-NTN | Nokia |
| R4-2501952 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues | Qualcomm Incorporated, THALES, Ericsson |
| R4-2502249 | (NR_NTN_enh-Core) Maintenance CR on 38.101-5 - Removing NTN 256QAM from Rel-18 FR1-NTN | THALES |
| R4-2502340 | (NR_NTN_enh-Core) CR for TS 38.101-5 Correction on FR2-NTN frequency range | CATT |
| R4-2502341 | (NR_NTN_enh-Core) CR for TS 38.108 Correction on FR2-NTN frequency range | CATT |
| R4-2502342 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues | Qualcomm Incorporated, THALES, Ericsson |
| R4-2502343 | (NR_NTN_enh-Core) Maintenance CR on 38.101-5 - Removing NTN 256QAM from Rel-18 FR1-NTN | THALES |
| TDoc | Title | Source |
|---|---|---|
| R4-2501368 | (NR_NTN_enh-Core) CR to TS 38108 - Missing SAN classes for type 2-O | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500235 | On R18 NTN RRM core and performance requirement maintenance | Apple |
| R4-2500841 | CR to TS 38.133 Correction of inter-RAT E-UTRAN cells with TN carrier measurement for NTN UE | CMCC |
| R4-2500842 | Discussion on core maintenance and LS from RAN2 for NTN enhancement | CMCC |
| R4-2500900 | (NR_NTN_enh-Core) CR on adding FR2 term in the requirement tables in cell re-selection for NTN | LG Electronics Inc. |
| R4-2501013 | (NR_NTN_enh-Core) CR on core requirements of Rel-18 NR NTN enhancements | CATT |
| R4-2501141 | Reply LS on soft satellite switch with re-sync | OPPO |
| R4-2501184 | (NR_NTN_enh-Core) Correction IE for NR NTN in RRC connected state | ZTE Corporation, Sanechips |
| R4-2501185 | (NR_NTN_enh-Core) Correction on NR NTN handover delay | ZTE Corporation, Sanechips |
| R4-2501186 | (NR_NTN_enh-Core) Modify NR NTN cell re-selection measurement in RRC IDLE state. | ZTE Corporation, Sanechips |
| R4-2501253 | Discussion on remaining issues in R18 NTN core requirements | Huawei, HiSilicon |
| R4-2501254 | CR on measurement requirements for FR2-NTN | Huawei, HiSilicon |
| R4-2501255 | CR on UL timing TC for FR2-NTN | Huawei, HiSilicon |
| R4-2501291 | (NR_NTN_enh-Core) Formal CR for TS 38.133 on positioning measurement accuracy requirements for NTN | Ericsson |
| R4-2501292 | (NR_NTN_enh-Core) Formal CR for TS 38.133 on positioning measurement for NTN | Ericsson |
| R4-2501293 | Discussion on reply LS to RAN2 on soft satellite switch with re-sync | Ericsson |
| R4-2501294 | RRM requirements for NR_NTN_enh | Ericsson |
| R4-2501345 | Discussion on LS on soft satellite switch with re-sync | vivo |
| R4-2501485 | Maintenance on soft satellite switching and LS reply to R2-2410978 | Nokia |
| R4-2501664 | Corrections to UE transmit timing for Satellite Access | Eutelsat Group, Thales, European Space Agency, Sharp, CHTTL, Airbus |
| R4-2501821 | (NR_NTN_enh-Core) Formal CR for TS 38.133 on positioning measurement accuracy requirements for NTN | Ericsson |
| R4-2502051 | Corrections to UE transmit timing for Satellite Access | Eutelsat Group, Thales, European Space Agency, Sharp, CHTTL, Airbus |
| R4-2502218 | (NR_NTN_enh-Core) Reply LS to RAN2 (LS on soft satellite switch with re-sync) | Qualcomm Incorporated |
| R4-2502611 | Corrections to UE transmit timing for Satellite Access | Eutelsat Group, Thales, European Space Agency, Sharp, CHTTL, Airbus |
| R4-2502676 | CR to TS 38.133 Correction of inter-RAT E-UTRAN cells with TN carrier measurement for NTN UE | CMCC |
| R4-2502677 | (NR_NTN_enh-Core) CR on adding FR2 term in the requirement tables in cell re-selection for NTN | LG Electronics Inc. |
| R4-2502678 | (NR_NTN_enh-Core) Correction on NR NTN handover delay | ZTE Corporation, Sanechips |
| R4-2502679 | (NR_NTN_enh-Core) Modify NR NTN cell re-selection measurement in RRC IDLE state. | ZTE Corporation, Sanechips |
| R4-2502680 | (NR_NTN_enh-Core) Formal CR for TS 38.133 on positioning measurement for NTN | Ericsson |
| R4-2502688 | Corrections to UE transmit timing for Satellite Access | Eutelsat Group, Thales, European Space Agency, Sharp, CHTTL, Airbus |
| TDoc | Title | Source |
|---|---|---|
| R4-2501789 | CR for 38.108 on FR2-NTN PUSCH demodulation requirements | Ericsson |
| R4-2501790 | CR for 38.181 on FR2-NTN PUSCH demodulation requirements | Ericsson |
| R4-2502047 | Correction CR on SAN performance requirements in TS 38.108 | Samsung |
| R4-2502049 | Correction CR on SAN performance requirements in TS 38.181 | Samsung |
| R4-2502267 | CR on SAN performance requirements in TS 38.108 | Samsung |
| R4-2502269 | Correction CR on SAN performance requirements in TS 38.181 | Samsung |
| R4-2502324 | CR on SAN performance requirements in TS 38.108 | Samsung, Ericsson |
| R4-2502364 | Correction CR on SAN performance requirements in TS 38.181 | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2501049 | CR on correction on interruption requirements for SRS BW aggregation | CATT |
| R4-2501142 | CR on core requirements of positioning enhancements | OPPO |
| R4-2501256 | Discussion on remaining issues in core requirements for R18 positioning | Huawei, HiSilicon |
| R4-2501257 | CR on RRM requirements for SL positioning | Huawei, HiSilicon |
| R4-2501258 | CR on requirements for SRS BWA | Huawei, HiSilicon |
| R4-2501609 | CR 38.133 remaining core issues for SL positioning | Ericsson |
| R4-2501754 | CR to 38.133 on core requirements for CPP | Ericsson |
| R4-2501755 | CR to 38.133 on core requirements for LPHAP | Ericsson |
| R4-2502271 | CR38.133 Corrections to DL RSCP requirements | Nokia Germany |
| R4-2502626 | CR on correction on interruption requirements for SRS BW aggregation | CATT, Huawei, HiSilicon |
| R4-2502627 | CR on core requirements of positioning enhancements | OPPO |
| R4-2502628 | CR to 38.133 on core requirements for CPP | Ericsson |
| R4-2502660 | CR on RRM requirements for SL positioning | Huawei, HiSilicon |
| R4-2502661 | CR 38.133 remaining core issues for SL positioning | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2501259 | CR on accuracy requirements for RedCap positioning | Huawei, HiSilicon |
| R4-2501756 | CR to 38.133 on test case for LPHAP | Ericsson |
| R4-2501757 | CR to 38.133 on performance requirements for carrier phase measurement for NR positioning | Ericsson |
| R4-2502629 | CR to 38.133 on test case for LPHAP | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500624 | CR on core requirements for R18 mobility | Xiaomi |
| R4-2500700 | Discussion on Further NR mobility enhancements | ZTE Corporation, Sanechips |
| R4-2500701 | Discussion on mobility performance part | ZTE Corporation, Sanechips |
| R4-2500706 | (NR_Mob_enh2-Core) Correction on Conditional handover including target MCG in FR1 and target SCG | ZTE Corporation, Sanechips |
| R4-2500707 | (NR_Mob_enh2-Pref) Correction on test cases for Idle mode fast CA/DC measurement | ZTE Corporation, Sanechips |
| R4-2500892 | Discussion on R18 mobility | MediaTek Inc. |
| R4-2500893 | CR on maintenance for R18 mobility [NR_Mob_enh2] | MediaTek Inc. |
| R4-2500936 | (NR_Mob_enh2-Core) CR on R18 CHO with PSCell change | ZTE Corporation, Sanechips |
| R4-2501102 | (NR_Mob_enh2-Core) Discussion on RRM maintenance for Rel-18 LTM | CMCC |
| R4-2501103 | (NR_Mob_enh2-Core) CR on Rel-18 LTM | CMCC |
| R4-2501162 | Discussion on collision between SSB and RA occasion for LTM | |
| R4-2501164 | [Draft] Reply to LS on collision between SSB and RA occasion for LTM | |
| R4-2501226 | Discussion on maintenance for L1/L2-based inter-cell mobility | Huawei, HiSilicon |
| R4-2501227 | (NR_Mob_enh2-Core) Corrections on LTM Cell Switch delay | Huawei, HiSilicon |
| R4-2501228 | (NR_Mob_enh2-Perf) Corrections on TC for LTM PDCCH-order Random Access | Huawei, HiSilicon |
| R4-2501402 | On remaining LTM requirements | Nokia |
| R4-2501403 | CR for LTM core part maintenance | Nokia |
| R4-2501420 | CR on PL1_sharing for L1-RSRP intra-frequency and inter-frequency neighbour cells | OPPO |
| R4-2501593 | Discussion on maintenance of RRM requirements for R18 NR_Mob_enh2 | vivo |
| R4-2501594 | CR on R18 LTM RRM core requirements | vivo |
| R4-2501595 | CR on R18 LTM RRM performance requirements | vivo |
| R4-2501741 | CR on PL1_sharing for L1-RSRP intra-frequency and inter-frequency neighbour cells | OPPO |
| R4-2501751 | CR on PL1_sharing for L1-RSRP intra-frequency and inter-frequency neighbour cells | OPPO |
| R4-2501930 | CR on R18 LTM RRM core requirements | vivo |
| R4-2501931 | CR on R18 LTM RRM performance requirements | vivo |
| R4-2501977 | CR for EMR test case with validityDuration | Nokia |
| R4-2501978 | Discussion on EMR performance requirements | Nokia |
| R4-2502057 | RRM requirements for L1/L2 based inter-cell mobility | Ericsson |
| R4-2502058 | CR to TS 38.133: maintenance CR on LTM | Ericsson |
| R4-2502216 | (NR_Mob_enh2-Core) CR on PDCCH order PRACH timeline (Cat-F Rel-18) | Qualcomm Incorporated |
| R4-2502217 | (NR_Mob_enh2-Core) Fast RRC processing and Early-PRACH based RACH-less LTM | Qualcomm Incorporated |
| R4-2502620 | CR on maintenance for R18 mobility | MediaTek Inc. |
| R4-2502621 | (NR_Mob_enh2-Core) CR on Rel-18 LTM | CMCC |
| R4-2502622 | CR for LTM core part maintenance | Nokia |
| R4-2502623 | CR on PL1_sharing for L1-RSRP intra-frequency and inter-frequency neighbour cells | OPPO |
| R4-2502624 | CR on R18 LTM RRM core requirements | vivo |
| R4-2502692 | CR on R18 LTM RRM performance requirements | vivo |
| R4-2502693 | (NR_Mob_enh2-Core) CR on PDCCH order PRACH timeline (Cat-F Rel-18) | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2501211 | (NR_MIMO_evo_DL_UL-Core) CR on core requirements maintenance for R18 MIMO | Huawei, HiSilicon |
| R4-2501596 | Discussion on maintenance of R18 MIMO RRM requirements | vivo |
| R4-2501597 | CR on R18 MIMO RRM requirements | vivo |
| R4-2502146 | CR corrections of RRM performance requirements for NR MIMO Evo | Nokia |
| R4-2502655 | (NR_MIMO_evo_DL_UL-Core) CR on core requirements maintenance for R18 MIMO | Huawei, HiSilicon |
| R4-2502656 | CR on R18 MIMO RRM requirements | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500708 | (NR_redcap_enh-Core) Correction on eRedCap UE | ZTE Corporation, Sanechips |
| R4-2501238 | (NR_redcap_enh-Core) Correction to TA validation requirements for RedCap R18 | Huawei, HiSilicon |
| R4-2502657 | (NR_redcap_enh-Core) Correction to TA validation requirements for RedCap R18 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2501548 | (NR_redcap_enh-Perf) CR on UE CSI requirements | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500234 | On RRM core requirements maintenance for R18 NES | Apple |
| R4-2500471 | Core maintenance on network energy saving | Nokia, Nokia Shanghai Bell |
| R4-2500472 | 38.133 CR on intra-frequency measurement with SSB-less SCell | Nokia, Nokia Shanghai Bell |
| R4-2500903 | Discussion on the core maintenance of SSB-less SCell operation of Network energy saving for NR | ZTE Corporation, Sanechips |
| R4-2501215 | Discussion on requirements maintenance for R18 NES | Huawei, HiSilicon |
| R4-2501216 | (Netw_Energy_NR-Perf) CR on TC maintenance for Rel-18 NES SSB-less | Huawei, HiSilicon |
| R4-2501217 | (Netw_Energy_NR-Perf) CR on TC maintenance for Rel-18 NES CHO | Huawei, HiSilicon |
| R4-2502059 | Discussions on the remaining open issues for Rel-18 NES | Ericsson |
| R4-2502060 | CR to TS 38.133 on core requirement maintenance for NES | Ericsson |
| R4-2502630 | (Netw_Energy_NR-Perf) CR on TC maintenance for Rel-18 NES SSB-less | Huawei, HiSilicon |
| R4-2502631 | CR to TS 38.133 on core requirement maintenance for NES | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500393 | CR on performance part maintenance for R18 IoT NTN enhancement | MediaTek inc. |
| R4-2501183 | (IoT_NTN_enh-Core) Modify IoT NTN cell re-selection measurement in RRC IDLE state. | ZTE Corporation, Sanechips |
| R4-2501480 | CR to TS 36133 on Radio Link Monitoring for NB-IoT over NTN | Nokia |
| R4-2501481 | The impacts of T310 suspension on RLM requirements in NB-IoT over NTN | Nokia |
| R4-2502625 | CR on performance part maintenance for R18 IoT NTN enhancement | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500192 | CR to TS 38.115-1 with clauses corrections | Nokia |
| R4-2500193 | CR to TS 38.115-1 with clauses corrections | Nokia |
| R4-2502346 | CR to TS 38.115-1 with clauses corrections | Nokia |
| R4-2502347 | CR to TS 38.115-1 with clauses corrections | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2501844 | CR on NCR-MT Correlation Matrix in 38.106 | Nokia |
| R4-2501845 | CR on NCR-MT Correlation Matrix in 38.115-1 | Nokia |
| R4-2501846 | CR on NCR-MT Correlation Matrix in 38.115-2 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500087 | Draft CR on correction for 38.101-1 clause 6 | Korea Testing Laboratory |
| R4-2500321 | (NR_NTN_enh) CR to 38.307 on release independence of DMRS bundling for GSO | Apple |
| R4-2500966 | (NR_redcap_enh-Perf) Add eRedCap in the context of requirements | ZTE Corporation, Sanechips |
| R4-2501569 | PC8 performance and FR2 handheld UE antenna arrangements | Ericsson |
| R4-2501804 | Clarification to beam correspondence requirements in initial access and RRC_INACTIVE [NR_RF_FR2_req_Ph3-Core] | Huawei, HiSilicon |
| R4-2501929 | (DC_R18_1BLTE_1BNR_2DL2UL-Core) Cat F CR for TS 38.101-3-i80 Intra-band contiguous MSD clean-up | Skyworks Solutions Inc., Murata Corporation Ltd |
| R4-2502006 | (NR_NTN_enh-Core, NR_NTN_solutions-Core) CR to TS 38.101-5: Correction on flexible Tx-Rx spacing for NR NTN | Qualcomm Incorporated |
| R4-2502111 | Discussion on the updated ITU-R SM.329 recommendation (v13; 09/2024) for UE RF specifications | Huawei, HiSilicon |
| R4-2502112 | (LTE-RF) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502113 | (LTE-RF) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502114 | (LTE_NBIoT_eMTC_NTN_req-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502115 | (NR_newRAT-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502116 | (NR_newRAT-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502117 | (NR_newRAT-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502118 | (NR_NTN_solutions-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502964 | (NR_redcap_enh-Perf) Add eRedCap in the context of requirements | ZTE Corporation, Sanechips |
| R4-2502971 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Cat F CR for TS 38.101-3-hg0 Intra-band contiguous MSD clean-up | Skyworks, Murata |
| R4-2502972 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Cat A CR for TS 38.101-3-i0 Intra-band contiguous MSD clean-up | Skyworks, Murata |
| R4-2502973 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Cat A CR for TS 38.101-3-j0 Intra-band contiguous MSD clean-up | Skyworks, Murata |
| TDoc | Title | Source |
|---|---|---|
| R4-2502119 | Discussion on the updated ITU-R SM.329 recommendation (v13; 09/2024) for BS RF specifications | Huawei, HiSilicon |
| R4-2502120 | (LTE_Relay-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502121 | (RInImp9-Rfmulti) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502122 | (AAS_BS_LTE_UTRA-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502123 | (AAS_BS_LTE_UTRA-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502124 | (RInImp9-Rfmulti) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502125 | (AAS_BS_LTE_UTRA-Perf) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502126 | (NR_newRAT-Core) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| R4-2502127 | (NR_NTN_solutions) Correction of reference to Suspended version of ITU-R SM.329 Recommendation | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500088 | Draft CR on correction for 38.133: clauses 3.3, 6.1.4.2.2, and 9 | Korea Testing Laboratory |
| R4-2501123 | CR to TS 38.133 on Inter-frequency measurements reporting requirements [NR_newRAT-Core] | CATT |
| R4-2501614 | (NR_newRAT-core) On gradual timing adjustment for CA and DC | Ericsson |
| R4-2501615 | (NR_newRAT-core) SCell transmission based on MTTD | Ericsson |
| R4-2501894 | (LTE_NR_DC_enh2) Correcting interruptions during measurements on deactivated NR PSCell | Nokia |
| R4-2501895 | (LTE_NR_DC_enh2) CR for correcting interruptions during measurements on deactivated NR PSCell | Nokia |
| R4-2502204 | (NR_newRAT-Core) CR to TS 38.133 on Inter-frequency measurements reporting requirements | CATT |
| R4-2502647 | Draft CR on correction for 38.133: clauses 3.3, 6.1.4.2.2, and 9 | Korea Testing Laboratory |
| TDoc | Title | Source |
|---|---|---|
| R4-2500046 | CR on Spec improvement for 38.101-1 | Korea Testing Laboratory |
| R4-2500347 | CR 36.307 R18 Annex A update on overlapping bands table [Overlapping_Bands] | Nokia |
| R4-2500348 | CR 38.307 R18 Annex A update on overlapping bands table [Overlapping_Bands] | Nokia |
| R4-2500482 | On the proposed FR2 PC8 (new power class) UE | Qualcomm Incorporated |
| R4-2501110 | Discussion on NTN NB-IoT UE in-band operation | MediaTek (Hefei) Inc. |
| R4-2501120 | (TEI18) CR to 36.102 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | MediaTek Inc. |
| R4-2501395 | (TEI18) Support of 3MHz channel bandwidth for RedCap devices [RedCap_3MHz] | Nokia, Anterix |
| R4-2501396 | Support of 3MHz channel bandwidth for RedCap devices | Nokia, Anterix |
| R4-2501551 | Discussion on introduction of FR2 PC8 | Huawei, HiSilicon |
| R4-2501552 | CR on introduction of RF requirements for FR2 PC8 in TS 38.101-2 [FR2_PC8] | Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2501553 | CR on introduction of RRM requirements for FR2 PC8 in TS 38.133 [FR2_PC8] | Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2501554 | CR on release independence for FR2 PC8 in TS 38.307 [FR2_PC8] | Huawei, HiSilicon, CTC, CEPRI, OPPO, vivo, Xiaomi, CATT, Spreadtrum, Google, Honor, TD Tech, StarPoint, SRTC |
| R4-2501555 | LS on introduction of FR2 PC8 | Huawei, HiSilicon |
| R4-2501589 | New annex clause listing CRs and the corresponding clauses changed | Anritsu Limited |
| R4-2501763 | (TEI18) CR to 38.101-5 NB-IoT inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | EchoStar |
| R4-2501995 | (TEI18) Support of 3MHz channel bandwidth for RedCap devices [RedCap_3MHz] | Nokia, Anterix |
| R4-2502003 | (TEI18) CR to TS 36.307: NB-IoT in-band operation with NR NTN [NTNNBIoT_inbandNTNNR] | Qualcomm Incorporated |
| R4-2502016 | (TEI18) On NTN NB-IoT in-band operation with NR [NTNNBIoT_inbandNTNNR] | Qualcomm Inc. |
| R4-2502106 | draftCR to 36.102 NB-IoT NTN inband operation with NR NTN [NTN NB-IoT] | Ericsson |
| R4-2502107 | [NTN NB-IoT] On inband deployment of NTN NB-IoT in NR carrier | Ericsson |
| R4-2502152 | (TEI18) CR to TS 36.307: NB-IoT in-band operation with NR NTN [NTNNBIoT_inbandNTNNR] | Qualcomm Incorporated |
| R4-2502929 | (TEI18) CR to 38.101-5 NB-IoT inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | EchoStar |
| R4-2502962 | CR 36.307 R18 Annex A update on overlapping bands table [Overlapping_Bands] | Nokia |
| R4-2502963 | CR 38.307 R18 Annex A update on overlapping bands table [Overlapping_Bands] | Nokia |
| R4-2502965 | WF on support of 3MHz channel bandwidth | Nokia, Anterix, Rakuten, T-mobile, Southern Linc |
| R4-2503001 | (TEI18) CR to 36.102 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | MediaTek Inc. |
| R4-2503002 | (TEI18) CR to TS 36.307: NB-IoT in-band operation with NR NTN [NTNNBIoT_inbandNTNNR] | Qualcomm Incorporated |
| R4-2503030 | Way Forward on IoT-NTN in-band | EchoStar |
| R4-2503034 | (TEI18) CR to 36.102 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | MediaTek Inc. |
| R4-2503036 | (TEI18) CR to 36.102 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | MediaTek Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500047 | CR on Spec improvement for 38.133 | Korea Testing Laboratory |
| R4-2500395 | (NR_RRM_enh3-Core) CR for RRM Spec Improvement (section A.7) | Qualcomm Incorporated |
| R4-2501225 | CR on specification improvement for 38.133 A.5 | Huawei, HiSilicon |
| R4-2501947 | (TEI18) Support of 3MHz channel bandwidth for RedCap devices RRM CR [RedCap_3MHz] | Nokia, Anterix |
| R4-2501948 | (TEI18) Support of 3MHz channel bandwidth for RedCap devices RRM Discussion [RedCap_3MHz] | Nokia, Anterix |
| R4-2502206 | CR to TS 38.133 on Inter-frequency measurements reporting requirements [NR_inter-freq_report] | CATT |
| R4-2502658 | CR to TS 38.133 on Inter-frequency measurements reporting requirements [NR_inter-freq_report] | CATT |
| R4-2502659 | (NR_RRM_enh3-Core) CR for RRM Spec Improvement (section A.7) | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500104 | (TEI18) CR to 38.104 on corrections to co-existence table [bands_coex_req] | Nokia |
| R4-2500105 | (TEI18) CR to 38.141-1 on corrections to co-existence table [bands_coex_req] | Nokia |
| R4-2500106 | (TEI18) CR to 38.141-2 on corrections to co-existence table [bands_coex_req] | Nokia |
| R4-2500200 | (TEI18) CR to 38.106 on corrections to co-existence table [bands_coex_req] | Nokia |
| R4-2500201 | (TEI18) CR to 38.115-1 on corrections to co-existence table [bands_coex_req] | Nokia |
| R4-2501737 | (TEI18) CR to 38.108 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | Inmarsat, Viasat, EchoStar, Thales |
| R4-2501764 | (TEI18) CR to 38.181 NB-IoT inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | EchoStar, Thales, Inmarsat, Viasat |
| R4-2501880 | (TEI18) CR to 36.181 NB-IoT In-band operation with NTN NR [NTNNBIoT_inbandNTNNR] | ZTE Corporation |
| R4-2501897 | (TEI18) Discussion on adding LTE band34 for HAPS [LTE_HAPS_B34] | NTT DOCOMO, INC. |
| R4-2501898 | 36.104 CR to introduce LTE band 34 for HAPS BS [LTE_HAPS_B34] | NTT DOCOMO, INC. |
| R4-2501899 | 36.141 CR to introduce LTE band 34 for HAPS BS [LTE_HAPS_B34] | NTT DOCOMO, INC. |
| R4-2502090 | (TEI18) CR to 36.108 NB-IoT In-band operation with NTN NR [NTNNBIoT_inbandNTNNR] | THALES, EchoStar, Inmarsat, Viasat |
| R4-2502348 | (TEI18) CR to 38.108 NB-IoT NTN inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | Inmarsat, Viasat, EchoStar, Thales |
| R4-2502349 | (TEI18) CR to 38.181 NB-IoT inband operation with NR NTN [NTNNBIoT_inbandNTNNR] | EchoStar, Thales, Inmarsat, Viasat |
| R4-2502350 | (TEI18) CR to 36.181 NB-IoT In-band operation with NTN NR [NTNNBIoT_inbandNTNNR] | ZTE Corporation |
| R4-2502351 | (TEI18) 36.104 CR to introduce LTE bands for HAPS BS [LTE_HAPS_B34] | NTT DOCOMO, INC. |
| R4-2502352 | (TEI18) 36.141 CR to introduce LTE bands for HAPS BS [LTE_HAPS_B34] | NTT DOCOMO, INC. |
| R4-2502353 | (TEI18) CR to 36.108 NB-IoT In-band operation with NTN NR [NTNNBIoT_inbandNTNNR] | THALES, EchoStar, Inmarsat, Viasat |
| TDoc | Title | Source |
|---|---|---|
| R4-2500577 | Topic summary for [114][316] HAPS_operating_bands | Moderator (Softbank) |
| R4-2500580 | Topic summary for [114][319] 5G_Broadcast_bands | Moderator (EBU) |
| R4-2500657 | Topic summary for [114][105] NR_Baskets_Part_1 | Moderator(Nokia) |
| R4-2500658 | Topic summary for [114][106] NR_Baskets_Part_2 | Moderator(Ericsson) |
| R4-2500659 | Topic summary for [114][107] LTE_Baskets | Moderator(Huawei) |
| R4-2500660 | Topic summary for [114][108] HPUE_NR_bands | Moderator(CMCC) |
| R4-2500661 | Topic summary for [114][109] LTE_NR_HPUE_FWVM | Moderator(Nokia) |
| R4-2500662 | Topic summary for [114][110] HPUE_Basket_EN-DC | Moderator(China Unicom) |
| R4-2500663 | Topic summary for [114][111] HPUE_Basket_CADC_SUL | Moderator(China Telecom) |
| R4-2500664 | Topic summary for [114][112] LTE_NR_Other_basket | Moderator(Huawei) |
| R4-2500665 | Topic summary for [114][113] NR_LTE_TN_Bands | Moderator(Nokia) |
| R4-2500666 | Topic summary for [114][114] NR_IoT_NTN_Bands | Moderator(Aalyria) |
| R4-2500667 | Topic summary for [114][115] NR_mmWave_protect | Moderator(China Unicom) |
| R4-2502293 | Ad-hoc meeting minutes for [114][319] 5G_Broadcast_bands | EBU |
| R4-2502376 | Ad-hoc meeting minutes for [114][319] 5G_Broadcast_bands | EBU |
| R4-2502825 | WF on HPUE for single NR band | CMCC |
| R4-2502840 | WF on simultaneous Rx-Tx | Huawei |
| R4-2502841 | WF on channel bandwidth for n48 | Apple |
| R4-2502850 | WF on NR and IoT NTN bands | Aalyria |
| R4-2502857 | WF on mmWave protection requirements | China Unicom |
| R4-2502885 | WF on NB-IoT NTN in-band operation with NR NTN | Echostar |
| R4-2502955 | WF on ULCA n41C MSD test point and IMD range definition | Skyworks, Qualcomm, ZTE, Huawei |
| R4-2502956 | WF on MSD rules for near-miss Rx mixing | Skyworks |
| R4-2502960 | WF on adding 4-band 5-band higher oder ENDC configurations | Murata Manufacturing Co Ltd. |
| R4-2502961 | WF on both (n)3AA BCS1 and (n)3CA | Murata Manufacturing Co Ltd. |
| R4-2502968 | WF on A-MPR for n86 | Ericsson |
| R4-2502999 | WF on NB-IoT NTN in-band operation with NR NTN | Echostar |
| TDoc | Title | Source |
|---|---|---|
| R4-2500137 | TR37.719-21-11 v0.4.0 for DC_R19_xBLTE_yBNR_3DL2UL | LG Electronics Deutschland |
| R4-2500138 | Draft BigCR for DC_R19_xBLTE_yBNR (OBJ-2 DC_R19_xBLTE_yBNR_3DL2UL) | LG Electronics Deutschland |
| R4-2500810 | Draft TR 37.719-11-10_v0.1.0 | Samsung |
| R4-2500811 | Draft big CR for DC SUL | Samsung |
| R4-2501152 | TR 37.719-11-11 v0.3.0 Rel-19 Dual Connectivity of EN-DC and NE-DC configurations consisting of 2 different bands downlink (DL) with 2 different bands uplink (UL) (1 LTE band and 1 NR band) | CHTTL |
| R4-2501160 | draft BigCR for DC_R19_xBLTE_yBNR (OBJ-1 DC_R19_1BLTE_1BNR_2DL2UL) | CHTTL |
| R4-2501650 | Big draftCR for DC_R19_xBLTE_yBNR (OBJ-3 DC_R19_xBLTE_yBNR_zDLqUL) | Nokia |
| R4-2501651 | BigCR for DC_R19_xBLTE_yBNR | Nokia, CHTTL, LG Electronics, Samsung |
| R4-2501652 | Revised WID for DC_R19_xBLTE_yBNR | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500816 | TP for TR 37.719-11-11 DC_(n)3 | Samsung, KT |
| R4-2500820 | MSD test point for DC_(n)3AA BCS1 | Murata Manufacturing Co Ltd. |
| R4-2501078 | MSD test point for DC_(n)3CA | Murata Manufacturing Co Ltd. |
| R4-2501438 | Draft CR for TS 38.101-3 to introduce DC_28C_n77A and DC_28C_n77(2A) | Huawei, HiSilicon, Xiaomi |
| R4-2501775 | TP for TR 37.719-11-11 adding DC_106A_n41A, DC_106A_n41C and DC_106A_n41(2A) | Ericsson, Anterix |
| R4-2501776 | TP for TR 37.719-11-11 adding DC_106A_n48A, DC_106A_n48C and DC_106A_n48(2A) | Ericsson, Anterix |
| R4-2501932 | (NR_CADC_SUL_R19-Core) Cat F CR for TS 38.101-3-j00 DC_(n)8AA MSD and MSD clean-ups | Skyworks Solutions Inc., Murata Corporation Ltd |
| R4-2501986 | DC_(n)8AA MSD and clean-ups for DC_(n)71AA, DC_(n)5AA | Skyworks Solutions Inc. |
| R4-2502886 | TP for TR 37.719-11-11 DC_(n)3 | Samsung, KT |
| R4-2502887 | TP for TR 37.719-11-11 adding DC_106A_n41A, DC_106A_n41C and DC_106A_n41(2A) | Ericsson, Anterix |
| R4-2502888 | TP for TR 37.719-11-11 adding DC_106A_n48A, DC_106A_n48C and DC_106A_n48(2A) | Ericsson, Anterix |
| R4-2502889 | (NR_CADC_SUL_R19-Core) Cat F CR for TS 38.101-3-j00 DC_(n)8AA MSD and MSD clean-ups | Skyworks Solutions Inc., Murata Corporation Ltd |
| R4-2502957 | Draft CR for TS 38.101-3 to introduce DC_28C_n77A and DC_28C_n77(2A) | Huawei, HiSilicon, Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R4-2500152 | [DC_R19_xBLTE_yBNR_3DL2UL] draftCR to 38.101-3 to include EN-DC band combinations | Huawei, HiSilicon |
| R4-2500153 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11: DC_8-28_n40 | Huawei, HiSilicon |
| R4-2500154 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11 DC_8_n40-n77 | Huawei, HiSilicon |
| R4-2500155 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11 DC_28_n40-n77 | Huawei, HiSilicon |
| R4-2500156 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11 DC_8-28_n77 | Huawei, HiSilicon |
| R4-2500817 | Draft CR for TS 38.101-3 to add 3-band higher order ENDC configurations | Samsung, KT |
| R4-2501436 | TP for TR 37.719-21-11 on introduction of DC_8A-28A_n77A and DC_8A-28C_n77A | Huawei, HiSilicon, Xiaomi |
| R4-2501439 | Draft CR for TS 38.101-3 to introduce two LTE bands with 3CC and n77 ENDC combos | Huawei, HiSilicon, Xiaomi |
| R4-2501641 | (DC_R19_xBLTE_yBNR_3DL2UL) Draft CR on TS 38.101-3 to introduce new BC for DC_7-20_n78 | ZTE Corporation, Sanechips |
| R4-2501660 | TP to TR 37.719-21-11 addition of DC_3A_n41A-n71A | Nokia, Etisalat UAE |
| R4-2501661 | TP to TR 37.719-21-11 addition of DC_3A_n71A-n78A | Nokia, Etisalat UAE |
| R4-2502890 | [DC_R19_xBLTE_yBNR_3DL2UL] draftCR to 38.101-3 to include EN-DC band combinations | Huawei, HiSilicon |
| R4-2502891 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11: DC_8-28_n40 | Huawei, HiSilicon |
| R4-2502892 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11 DC_8_n40-n77 | Huawei, HiSilicon |
| R4-2502893 | [DC_R19_xBLTE_yBNR_3DL2UL] TP for TR 37.719-21-11 DC_28_n40-n77 | Huawei, HiSilicon |
| R4-2502894 | TP for TR 37.719-21-11 on introduction of DC_8A-28A_n77A and DC_8A-28C_n77A | Huawei, HiSilicon, Xiaomi |
| R4-2502895 | Draft CR for TS 38.101-3 to introduce two LTE bands with 3CC and n77 ENDC combos | Huawei, HiSilicon, Xiaomi |
| R4-2502896 | TP to TR 37.719-21-11 addition of DC_3A_n41A-n71A | Nokia, Etisalat UAE |
| R4-2502897 | TP to TR 37.719-21-11 addition of DC_3A_n71A-n78A | Nokia, Etisalat UAE |
| TDoc | Title | Source |
|---|---|---|
| R4-2500151 | [DC_R19_xBLTE_yBNR_zDLqUL] draftCR to 38.101-3 to include EN-DC band combinations | Huawei, HiSilicon |
| R4-2500407 | Draft CR for TS 38.101-3 to add 4-band 5-band higher oder ENDC configurations | Samsung, KT |
| R4-2500713 | Draft CR for TS38.101-3 to include DC_8-11_n1-n3 | SoftBank Corp. |
| R4-2501168 | draft CR for EN-DC DC_1-3-3-7-7_n8-n78 related combos | CHTTL |
| R4-2501440 | Draft CR for TS 38.101-3 to introduce three or four LTE bands and n77 ENDC combos | Huawei, HiSilicon, Xiaomi |
| R4-2501441 | Draft CR for TS 38.101-3 to introduce ENDC combos related to LTE CA_1A-3A-3A-41A / CA_1A-3A-3A-41C | Huawei, HiSilicon, samsung |
| R4-2502898 | [DC_R19_xBLTE_yBNR_zDLqUL] draftCR to 38.101-3 to include EN-DC band combinations | Huawei, HiSilicon |
| R4-2502899 | Draft CR for TS 38.101-3 to add 4-band 5-band higher oder ENDC configurations | Samsung, KT |
| R4-2502900 | Draft CR for TS 38.101-3 to introduce ENDC combos related to LTE CA_1A-3A-3A-41A / CA_1A-3A-3A-41C | Huawei, HiSilicon, samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2501443 | Draft CR for TS 38.101-3 to introduce DC_3A_SUL_n79C-n80A | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2501642 | TP for PRD 01 on delta TIB and RIB tables | ZTE Corporation, Sanechips |
| R4-2501643 | TP for PRD 01 to include CA and DC simplification rules for configuration | ZTE Corporation, Sanechips |
| R4-2501663 | TP to PRD01 for Guidelines on delta TIB and RIB | Nokia |
| R4-2501772 | revised RAN4 PRD 01 v0.3.0, Rules guidelines and ways of working for introduction of band combinations | Ericsson |
| R4-2501963 | Input to RAN4 PRD on rules for 1UL CC MSD requirements | Skyworks Solutions Inc. |
| R4-2502974 | TP for PRD 01 on delta TIB and RIB tables | ZTE Corporation, Sanechips |
| R4-2502975 | TP to PRD01 for Guidelines on delta TIB and RIB | Nokia |
| R4-2503022 | Input to RAN4 PRD on rules for 1UL CC MSD requirements | Skyworks Solutions Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500690 | Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 | SoftBank Corp. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500600 | TS 38.101-1 big draftCR for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
| R4-2500601 | TS 38.101-2 big draftCR for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
| R4-2500967 | TR38.719-02-01 v0.4.0_NR_CADC_R19_2BDL_xBUL | ZTE Corporation |
| R4-2500968 | draft big CR for NR_CADC_SUL_R19(OBJ-2 NR_CADC_R19_2BDL_xBUL) | ZTE Corporation |
| R4-2501433 | Draft Big CR on Introduction of completed SUL band combinations into TS 38.101-1 | Huawei, HiSilicon |
| R4-2501434 | TR for 38.719-00-00 v0.2.0 | Huawei, HiSilicon |
| R4-2501626 | TR 38.719-03-01 v0.4.0 on Rel-19 NR Inter-band CA DC configurations including inter band CA for 3 different bands DL with x different bands UL (x=1,2) | ZTE Corporation |
| R4-2501627 | Big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-1 | ZTE Corporation |
| R4-2501628 | Big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-3 | ZTE Corporation |
| R4-2501665 | draft big CR 38.101-1 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) | Ericsson |
| R4-2501666 | draft big CR 38.101-3 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) | Ericsson |
| R4-2501765 | Revised WID NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
| R4-2501766 | draft big CR 38.101-1 new combinations Rel-19 NR Intra-band | Ericsson |
| R4-2501767 | draft big CR 38.101-2 new combinations Rel-19 NR Intra-band | Ericsson |
| R4-2501768 | Rel-19 NR intra-band CA combinations | Ericsson |
| R4-2501769 | big CR 38.101-1 for NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
| R4-2501770 | Big CR 38.101-2 for NR_CADC_SUL_R19 | Ericsson |
| R4-2501771 | big CR 38.101-3 for NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
| R4-2501783 | CR 38.101-1 correcting band combination configuration tables | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2501442 | Draft CR for TS 38.101-2 to introduce CA_n258R and CA_n258S | Huawei, HiSilicon |
| R4-2501784 | draft CR 38.101-1 adding missing intra-band note | Ericsson |
| R4-2502901 | draft CR 38.101-1 adding missing intra-band note | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500461 | Additional test points for CA_n40A-n41C and CA_n41C-n79A with n41C UL | Skyworks Solutions Inc. |
| R4-2500779 | Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 2 DL | SoftBank Corp. |
| R4-2500785 | draft TP to TR 38.719-02-01 include CA_n7A-n40A | Huawei, HiSilicon |
| R4-2500793 | draft TP to TR 38.719-02-01 include CA_n1A-n41A | Huawei, HiSilicon |
| R4-2500794 | draft TP to TR 38.719-02-01 include CA_n20A-n41A | Huawei, HiSilicon |
| R4-2500953 | TP for TR38.719-02-01_CA_n8A-n104C | ZTE Corporation, Sanechips |
| R4-2500954 | TP for TR38.719-02-01_Intra-band UL CA for CA_n41-n104 | ZTE Corporation, Sanechips |
| R4-2501058 | CR for TS 38.101-1 2U/2D n5-n8 | CATT, China Telecom, Huawei |
| R4-2501435 | Discussion on UL CA_n41C MSD test point and its capture in TS | Huawei, HiSilicon |
| R4-2501437 | Draft CR for TS 38.101-1 to introduce CA_n8A-n77(2A) | Huawei, HiSilicon, Xiaomi |
| R4-2501574 | Corrections to Harmonic Mixing UL allocations | Qualcomm France |
| R4-2501577 | CA_n40A-n41C and CA_n41C-n79A MSD | Qualcomm France |
| R4-2501644 | (NR_CADC_R19_2BDL_xBUL) Draft CR on TS 38.101-1 to correct two bands inter-band CA configurations and reference sensitivity exceptions | ZTE Corporation, Sanechips |
| R4-2501670 | Draft CR 38.101-1 to add new NR CA 2BDL configurations | Ericsson, AT&T |
| R4-2501673 | Draft CR 38.101-3 to add new NR CADC 2BDL configurations including FR2 | Ericsson,T-Mobile USA |
| R4-2501684 | Draft CR for TS 38.101-1 to add new inter-band CA combinations (two bands) | Samsung, Boost Mobile Network, Fujitsu |
| R4-2501777 | draft CR 38.101-3 adding CADC_n77(3A)-n260A/G/H/I/J/K/L/M | Ericsson, US Cellular |
| R4-2501848 | CR for TS 38.101-1 2U/2D n5-n8 | CATT, China Telecom, Huawei |
| R4-2501865 | CR for TS 38.101-1 2U/2D n5-n8 | CATT, China Telecom, Huawei |
| R4-2501924 | TP for adding MSD result for CA_n74-n77 to TR38.719-02-01 | KDDI Corporation |
| R4-2501987 | On near-miss for Rx harmonic mixing | Skyworks Solutions Inc., Anritsu, Qualcomm France, Oppo |
| R4-2502902 | Draft CR for TS 38.101-1 to introduce CA_n8A-n77(2A) | Huawei, HiSilicon, Xiaomi |
| R4-2502903 | (NR_CADC_R19_2BDL_xBUL) Draft CR on TS 38.101-1 to correct two bands inter-band CA configurations and reference sensitivity exceptions | ZTE Corporation, Sanechips |
| R4-2502904 | Draft CR 38.101-3 to add new NR CADC 2BDL configurations including FR2 | Ericsson,T-Mobile USA |
| R4-2502905 | Draft CR for TS 38.101-1 to add new inter-band CA combinations (two bands) | Samsung, Boost Mobile Network, Fujitsu |
| R4-2502928 | draft TP to TR 38.719-02-01 include CA_n7A-n40A | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500691 | Draft CR for TS38.101-3 Rel-19 for adding new NRDC combinations between FR1 and FR2 | SoftBank Corp. |
| R4-2500771 | TP for TR38.719-03-01 Support of CA_n3-n78-n79, CA_n3-n77-n79 and CA_n28_n77_n79 | SoftBank Corp. |
| R4-2500780 | Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 3DL | SoftBank Corp. |
| R4-2500786 | draft TP to TR 38.719-03-01 include CA_n40A-78A-n79A | Huawei, HiSilicon |
| R4-2500787 | draft TP to TR 38.719-03-01 include CA_n1A-n40A-n79A | Huawei, HiSilicon |
| R4-2500788 | draft TP to TR 38.719-03-01 include CA_n3A-n40A-n78A | Huawei, HiSilicon |
| R4-2500789 | draft TP to TR 38.719-03-01 include CA_n3A-n40A-n79A | Huawei, HiSilicon |
| R4-2500790 | draft TP to TR 38.719-03-01 include CA_n7A-n40A-n78A | Huawei, HiSilicon |
| R4-2500791 | draft TP to TR 38.719-02-01 include CA_n7A-n40A-n79A | Huawei, HiSilicon |
| R4-2500792 | draft TP to TR 38.719-03-01 include CA_n7A-n78A-n79A | Huawei, HiSilicon |
| R4-2500795 | draft TP to TR 38.719-03-01 include CA_n1A-n3A-n41A | Huawei, HiSilicon |
| R4-2501645 | (NR_CADC_R19_3BDL_xBUL) Draft CR on TS 38.101-1 to correct three bands inter-band CA configurations | ZTE Corporation, Sanechips |
| R4-2501671 | Draft CR 38.101-1 to add new NR CA 3BDL configurations | Ericsson, AT&T |
| R4-2501672 | Draft CR 38.101-1 to add new UL for NR 3BDL configurations | Ericsson,T-Mobile USA |
| R4-2501683 | Draft CR for TS 38.101-1 to add new inter-band CA combinations (three bands) | Samsung, Boost Mobile Network, Fujitsu |
| R4-2501829 | Draft CR for TS 38.101-1 to add BCS 4 and 5 for CA band combinations consist of three bands | Huawei, HiSilicon |
| R4-2502906 | Draft CR for TS38.101-3 Rel-19 for adding new NRDC combinations between FR1 and FR2 | SoftBank Corp. |
| R4-2502907 | TP for TR38.719-03-01 Support of CA_n3-n78-n79, CA_n3-n77-n79 and CA_n28_n77_n79 | SoftBank Corp. |
| R4-2502908 | draft TP to TR 38.719-03-01 include CA_n40A-78A-n79A | Huawei, HiSilicon |
| R4-2502909 | draft TP to TR 38.719-03-01 include CA_n1A-n40A-n79A | Huawei, HiSilicon |
| R4-2502910 | draft TP to TR 38.719-03-01 include CA_n3A-n40A-n78A | Huawei, HiSilicon |
| R4-2502911 | draft TP to TR 38.719-03-01 include CA_n7A-n40A-n78A | Huawei, HiSilicon |
| R4-2502912 | draft TP to TR 38.719-02-01 include CA_n7A-n40A-n79A | Huawei, HiSilicon |
| R4-2502913 | draft TP to TR 38.719-03-01 include CA_n7A-n78A-n79A | Huawei, HiSilicon |
| R4-2502914 | Draft CR 38.101-1 to add new NR CA 3BDL configurations | Ericsson, AT&T |
| R4-2502915 | Draft CR for TS 38.101-1 to add BCS 4 and 5 for CA band combinations consist of three bands | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500796 | Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 4 DL | SoftBank Corp. |
| R4-2501646 | (NR_CADC_R19_yBDL_xBUL) Draft CR on TS 38.101-1 to correct four bands inter-band CA configurations | ZTE Corporation, Sanechips |
| R4-2501669 | Draft CR 38.101-1 to add CA_n2A-n5A-n66A-n77(2A) BCS 4 and 5 | Ericsson, AT&T |
| R4-2501682 | Draft CR for TS 38.101-1 to add new inter-band CA combinations (four bands) | Samsung, Boost Mobile Network, Fujitsu |
| R4-2501781 | draft CR 38.101-1 adding already endorsed 4DL combinations | Ericsson, Telstra |
| R4-2501830 | Draft CR for TS 38.101-1 to add BCS 4 and 5 for CA band combinations consist of more than three bands | Huawei, HiSilicon |
| R4-2502916 | Draft CR for TS 38.101-1 to add BCS 4 and 5 for CA band combinations consist of more than three bands | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2501444 | Draft CR for TS 38.101-1 to introduce BCS4&5 for CA_n1A_n78A-n80A & CA_n1A_n78C-n80A and CA_n1A_n78A-n84A & CA_n1A_n78C-n84A | Huawei, HiSilicon, China Telecom, China Unicom |
| R4-2501445 | Draft CR for TS 38.101-1 to introduce two SUL cells CA_41C_n95A-n98A | Huawei, HiSilicon |
| R4-2502917 | Draft CR for TS 38.101-1 to introduce BCS4&5 for CA_n1A_n78A-n80A & CA_n1A_n78C-n80A and CA_n1A_n78A-n84A & CA_n1A_n78C-n84A | Huawei, HiSilicon, China Telecom, China Unicom |
| R4-2502918 | Draft CR for TS 38.101-1 to introduce two SUL cells CA_41C_n95A-n98A | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500431 | Big CR on Introduction of completed R19 x(1<=x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 | Huawei, Hisilicon |
| R4-2500432 | TR 36.719-01-01 LTE-A CA for x-DL y-UL | Huawei Technologies France |
| R4-2500433 | Revised WID Rel-19 LTE-A CA for x(1<=x<=6) DL y(y<=2) | Huawei, Hisilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500371 | TP into TR 36.719-01-01: Addition of CA_40C/D/E/F | Nokia |
| R4-2500372 | TP into TR 36.719-01-01: Addition of CA_42C/D/E/F | Nokia |
| R4-2500373 | TP into TR 36.719-01-01: Addition of PC2 for UL CA_40A-42A | Nokia |
| R4-2500417 | draftCR on Introduction of new LTE band combinations LTE_CA_R19_xBDL_yBUL | Huawei, HiSilicon |
| R4-2501383 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-28A-38A | Nokia, Telefonica |
| R4-2501384 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-28A-40A | Nokia, Telefonica |
| R4-2501385 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-40A | Nokia, Telefonica |
| R4-2501386 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-28A-38A | Nokia, Telefonica |
| R4-2501387 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-28A-40A | Nokia, Telefonica |
| R4-2501388 | TP for TR 36.719-01-01 - Addition of CA_3A-20A-28A-40A | Nokia, Telefonica |
| R4-2501389 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-28A-38A | Nokia, Telefonica |
| R4-2501390 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-28A-40A | Nokia, Telefonica |
| R4-2501391 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-40A | Nokia, Telefonica |
| R4-2501392 | TP for TR 36.719-01-01 - Addition of CA_8A-28A-38A | Nokia, Telefonica |
| R4-2501393 | TP for TR 36.719-01-01 - Addition of CA_8A-28A-40A | Nokia, Telefonica |
| R4-2501394 | TP for TR 36.719-01-01 - Addition of CA_20A-28A-40A | Nokia, Telefonica |
| R4-2501773 | TP TR 36.719-01-01 adding CA_41A-106A, CA_41C-106A and CA_41A-41A-106A | Ericsson, Anterix |
| R4-2501774 | TP TR 36.719-01-01 adding CA_48A-106A, CA_48C-106A and CA_48A-48A-106A | Ericsson, Anterix |
| R4-2502930 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-28A-38A | Nokia, Telefonica |
| R4-2502931 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-28A-40A | Nokia, Telefonica |
| R4-2502932 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-20A-40A | Nokia, Telefonica |
| R4-2502933 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-28A-38A | Nokia, Telefonica |
| R4-2502934 | TP for TR 36.719-01-01 - Addition of CA_3A-8A-28A-40A | Nokia, Telefonica |
| R4-2502935 | TP for TR 36.719-01-01 - Addition of CA_3A-20A-28A-40A | Nokia, Telefonica |
| R4-2502936 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-28A-38A | Nokia, Telefonica |
| R4-2502937 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-28A-40A | Nokia, Telefonica |
| R4-2502938 | TP for TR 36.719-01-01 - Addition of CA_8A-20A-40A | Nokia, Telefonica |
| R4-2502939 | TP for TR 36.719-01-01 - Addition of CA_8A-28A-38A | Nokia, Telefonica |
| R4-2502940 | TP for TR 36.719-01-01 - Addition of CA_8A-28A-40A | Nokia, Telefonica |
| R4-2502941 | TP for TR 36.719-01-01 - Addition of CA_20A-28A-40A | Nokia, Telefonica |
| R4-2502942 | TP TR 36.719-01-01 adding CA_41A-106A, CA_41C-106A and CA_41A-41A-106A | Ericsson, Anterix |
| R4-2502943 | TP TR 36.719-01-01 adding CA_48A-106A, CA_48C-106A and CA_48A-48A-106A | Ericsson, Anterix |
| R4-2502966 | TP into TR 36.719-01-01: Addition of CA_40C/D/E/F | Nokia |
| R4-2502967 | TP into TR 36.719-01-01: Addition of CA_42C/D/E/F | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500383 | TR 38.796 v0.3.0 HPUE_NR_FR1_bands_R19-FDD | China Unicom |
| TDoc | Title | Source |
|---|---|---|
| R4-2500869 | CR for TS 38.101-1 to introduce PC1.5 n104 | CMCC |
| R4-2502860 | CR for TS 38.101-1 to introduce PC1.5 n104 | CMCC, ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2501570 | Specification of PC2 for n5 and n26 | Ericsson |
| R4-2501571 | Draft CR to 38.101-1: Introduction of requirements for PC2 operation in band n26 | Ericsson |
| R4-2501984 | NS_05 NS_48 NS_49 PC2 A-MPR clean-up | Skyworks Solutions Inc. |
| R4-2502018 | n26 PC2 A-MPR | Qualcomm Inc. |
| R4-2503019 | Draft CR to 38.101-1: Introduction of requirements for PC2 operation in band n26 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500385 | Revised WID on Rel-19 High power UE (power class 1.5 or 2) for Dual Connectivity (DC) combinations of LTE band(s) and NR band(s) | China Unicom, Ericsson |
| R4-2500386 | TR 37.898 v0.3.0 HPUE_DC_LTE_NR_R19 | China Unicom, Ericsson |
| R4-2500394 | Big CR on Rel-19 HPUE for DC combinations of LTE band(s) and NR band(s) | China Unicom, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500718 | TP for TR 37.898 to add of PC2 for DC_11A_n41A | vivo |
| R4-2500719 | TP for TR 37.898 to add of PC2 for DC_12A_n41A | vivo |
| R4-2500720 | TP for TR 37.898 to add of PC2 for DC_12A_n78A | vivo |
| R4-2500721 | TP for TR 37.898 to add of PC2 for DC_18A_n78A | vivo |
| R4-2500722 | TP for TR 37.898 to add of PC2 for DC_25A_n41A | vivo |
| R4-2500723 | TP for TR 37.898 to add of PC2 for DC_25A_n78A | vivo |
| R4-2500724 | TP for TR 37.898 to add of PC2 for DC_26A_n78A | vivo |
| R4-2500725 | TP for TR 37.898 to add of PC2 for DC_40A_n41A | vivo |
| R4-2502826 | TP for TR 37.898 to add of PC2 for DC_12A_n78A | vivo |
| R4-2502827 | TP for TR 37.898 to add of PC2 for DC_25A_n41A | vivo |
| R4-2502828 | TP for TR 37.898 to add of PC2 for DC_25A_n78A | vivo |
| R4-2503023 | TP for TR 37.898 to add of PC2 for DC_18A_n78A | vivo |
| R4-2503024 | TP for TR 37.898 to add of PC2 for DC_26A_n78A | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500384 | TR 38.750 v0.4.0 HPUE_NR_CADC_SUL_R19-FDD | China Unicom |
| R4-2500692 | Revised WID for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
| R4-2500693 | Big CR to 38.101-1 new combinations for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
| R4-2500694 | TR 38.746 v0.3.0 HPUE_NR_CADC_SUL_R19-TDD | China Telecom |
| R4-2501353 | draft objective BigCR for HPUE_NR_CADC_SUL_R19 | China Unicom |
| TDoc | Title | Source |
|---|---|---|
| R4-2500798 | Draft CR for TS 38.101-1 to add HPUE notes for some NR-CA band combinations | KDDI, Samsung |
| R4-2501656 | Draft CR 38.101-1 to add new FR1 TDD intra-band UL combinations of n41 for PC2 | Nokia, T-Mobile USA |
| R4-2501951 | (HPUE_NR_CADC_SUL_R19) Cat F CR for TS 38.101-1-j00 Corrections to intra-band non-contiguous MSD | Skyworks Solutions Inc., T-Mobile USA |
| R4-2501994 | 1UL CC MSD clean-up for intra-band non-contiguous NRCA | Skyworks Solutions Inc., T-Mobile USA |
| R4-2502829 | (HPUE_NR_CADC_SUL_R19) Cat F CR for TS 38.101-1-j00 Corrections to intra-band non-contiguous MSD | Skyworks Solutions Inc., T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R4-2500776 | Draft CR for TS38.101-1 Rel-19 for adding new HP-NRCA combinations for FR1 | SoftBank Corp. |
| R4-2500777 | TP for TR38.746-020 for adding HP-NRCA combinations for FR1 | SoftBank Corp. |
| R4-2501117 | Draft CR for TS 38.101-1 to add HPUE notes for some NR-CA band combinations | KDDI, Samsung |
| R4-2501657 | Draft CR 38.101-1 to add new FR1 TDD inter-band UL combinations of n25 n41 n66 n71 and n77 for PC2 and PC1.5 | Nokia, T-Mobile USA |
| R4-2501778 | TP for TR 38.746 adding missing PC1.5 MSD CA_n7-n78 | Ericsson, Telstra |
| R4-2501779 | draft CR 38.101-1 adding PC1.5 CA_n1-n78, CA_n3-n78, CA_n7-n78, CA_n26-n78 and CA_n28-n78 | Ericsson, Telstra |
| R4-2501780 | draft CR 38.101-1 adding n78 PC1.5 3DL2UL configurations | Ericsson, Telstra |
| R4-2501782 | draft CR 38.101-1 adding already endorsed 3DL HPUE combinations | Ericsson, Telstra |
| R4-2501928 | TP for adding PC2 CA_n74-n77 to TR38.746 | KDDI Corporation |
| R4-2502201 | CR for 38.101-1 to correct errors and remove redundant CA with TxD table | T-Mobile USA, Nokia, Skyworks Solutions, Inc., Deutsche Telekom, Ericsson, Qualcomm |
| R4-2502830 | Draft CR for TS 38.101-1 to add HPUE notes for some NR-CA band combinations | KDDI, Samsung |
| R4-2502831 | draft CR 38.101-1 adding n78 PC1.5 3DL2UL configurations | Ericsson, Telstra |
| R4-2502832 | TP for adding PC2 CA_n74-n77 to TR38.746 | KDDI Corporation |
| R4-2502833 | CR for 38.101-1 to correct errors and remove redundant CA with TxD table | T-Mobile USA, Nokia, Skyworks Solutions, Inc., Deutsche Telekom, Ericsson, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R4-2500037 | TP for TR 38.750 Addition of n2 PC2 UL for CA_n2-n77 | AT&T, Skyworks Solutions, Inc., Murata Manufacturing Co Ltd., Qualcomm |
| R4-2500038 | TP for TR 38.750 Addition of n14 PC2 UL for CA_n14-n77 | AT&T, FirstNet, Skyworks Solutions, Inc., Murata Manufacturing Co Ltd., Qualcomm |
| R4-2500221 | CA_n2A-n77A UL n2A PC2 | Murata Manufacturing Co Ltd. |
| R4-2500222 | CA_n14A-n77A UL n14A PC2 | Murata Manufacturing Co Ltd. |
| R4-2500812 | TP for TR 38.750 CA_n29-n71 with PC2 FDD single UL | Samsung, Boost Mobile Network, Qualcomm, Fujitsu |
| R4-2500813 | TP for TR 38.750 CA_n70-n71 with PC2 FDD single UL | Samsung, Boost Mobile Network, Qualcomm, Fujitsu |
| R4-2500814 | TP for TR 38.750 CA_n70-n77 with PC2 FDD single UL | Samsung, Boost Mobile Network, Qualcomm, Fujitsu |
| R4-2500815 | Draft CR for TS 38.101-1 to add PC2 FDD single UL to 3-band and 4-band DL configurations | Samsung, Boost Mobile Network |
| R4-2501575 | CA_n2A-n77A and CA_n14A-n77A PC2 MSD | Qualcomm France |
| R4-2501658 | Draft CR 38.101-1 to add new FR1 FDD inter-band combinations of n25 n66 n71 n77 for PC2 | Nokia, T-Mobile USA |
| R4-2501667 | Draft CR 38.101-1 Addition of Single UL PC2 FDD CA Combinations with no MSD | Ericsson, BT plc |
| R4-2501933 | (HPUE_NR_CADC_SUL_R19) Cat F CR for TS 38.101-1-j00 SUL PC2 MSD requirements | Skyworks Solutions Inc. |
| R4-2501989 | HPUE MSD for CA_n2A-n77A and CA_n14A-n77A | Skyworks Solutions Inc. |
| R4-2502172 | HPUE MSD for SUL | Skyworks Solutions Inc. |
| R4-2502203 | CR for 38.101-1 to correct FDD HPUE notes | T-Mobile USA |
| R4-2502995 | TP for TR 38.750 CA_n29-n71 with PC2 FDD single UL | Samsung, Boost Mobile Network, Qualcomm, Fujitsu |
| TDoc | Title | Source |
|---|---|---|
| R4-2501659 | Draft CR 38.101-1 to add new FR1 inter-band UL combinations of n25 n41 n66 n71 and n77 for PC2 and UL MIMO | Nokia, T-Mobile USA |
| R4-2501668 | Draft CR 38.101-1 Addition of UL PC2 and PC1.5 CA Combinations with no MSD | Ericsson, BT plc |
| R4-2502834 | Draft CR 38.101-1 to add new FR1 inter-band UL combinations of n25 n41 n66 n71 and n77 for PC2 and UL MIMO | Nokia, T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R4-2500969 | Revised WID: Additional NR bands for NR features in Rel-19 | ZTE Corporation, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R4-2500716 | The remaining issue of n28 UE RF | vivo |
| R4-2500717 | draft CR on Tx power tolerance of n28 | vivo |
| R4-2500873 | CR on support of UL MIMO for PC2 n28 | CMCC, CBN, China Broadnet |
| R4-2500874 | CR on introducing release independence of 40MHz for n28 | CMCC, CBN, China Broadnet |
| R4-2502233 | On UE RF requirements for band n28 | Huawei, HiSilicon |
| R4-2502835 | CR on introducing release independence of 40MHz for n28 | CMCC, CBN, China Broadnet |
| R4-2502836 | draft CR on Tx power tolerance of n28 | vivo |
| R4-2503025 | CR on support of UL MIMO for PC2 n28 | CMCC, CBN, China Broadnet |
| TDoc | Title | Source |
|---|---|---|
| R4-2500970 | TS 38.101-1 draft big CR to include 4Rx and 8Rx | ZTE Corporation |
| R4-2500971 | TS 38.101-1 big CR for NR_bands_xFeature_R19-Core | ZTE Corporation, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R4-2500036 | DraftCR 38.101-1 UL MIMO PC2 Support for Band n2 | AT&T |
| R4-2501831 | Draft CR for TS 38.101-1 to introduce PC2 UL MIMO for band n85 | Huawei, HiSilicon, T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R4-2500870 | CR for TS 38.101-1 to introduce n34 and n39 support 8Rx | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R4-2501106 | TR 37.887 0.0.4 Rel-19 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink | China Telecom |
| R4-2501107 | Big CR to 38.101-1 Introduce no DL interruption clarification for CA at dynamic Tx Switching in uplink | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R4-2500314 | TP to 37.887 General part on the note for DL interruption for dynamic Tx switching | Apple |
| R4-2501108 | TP to 37.887: DL interruption clarification for CA_n1-n5-n78 for 3 bands dynamic Tx switching | China Telecom |
| R4-2502837 | TP to 37.887 General part on the note for DL interruption for dynamic Tx switching | Apple |
| R4-2502838 | TP to 37.887: DL interruption clarification for CA_n1-n5-n78 for 3 bands dynamic Tx switching | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R4-2500148 | TR 38.793 v0.0.1 Rel-19 Requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500146 | Discussion on simultaneous Rx-Tx | Huawei, HiSilicon |
| R4-2500147 | TP to TR38.793 on CA_n40A-n41A | Huawei, HiSilicon |
| R4-2500149 | CR to 38.101-1 on Rel-19 simultaneous Rx-Tx | Huawei, HiSilicon |
| R4-2500150 | CR to 38.101-3 on Rel-19 simultaneous Rx-Tx | Huawei, HiSilicon |
| R4-2500305 | On simultaneous RxTx for CA_n40A-n41A | Apple |
| R4-2500714 | BigCR to 38.101-1: Simultaneous Rx-Tx | Huawei, HiSilicon |
| R4-2500715 | BigCR to 38.101-3: Simultaneous Rx-Tx | Huawei, Hisilicon |
| R4-2501576 | CA_n40A-n41A MSD | Qualcomm France |
| R4-2501944 | (LTE_NR_R19_Simult_RxTx-Core) Cat F CR for TS 38.101-1-j00 Simultaneous RxTx clean-up | Skyworks Solutions Inc., Nokia. |
| R4-2501953 | CA_n40A-n41A second MSD test point | Skyworks Solutions Inc. |
| R4-2501993 | On simultaneous RxTx requirements | Skyworks Solutions Inc. |
| R4-2502839 | TP to TR38.793 on CA_n40A-n41A | Huawei, HiSilicon |
| R4-2503018 | TP for TR 38.793 CA_n40A-n41A | Huawei, HiSilicon, Skyworks Solutions Inc |
| TDoc | Title | Source |
|---|---|---|
| R4-2501371 | Draft revised basket WI on adding new channel BW in existing NR bands | Ericsson |
| R4-2501372 | TR 37862 for the basket WI on adding new channel BW in existing NR bands | Ericsson |
| R4-2501373 | Big CR to TS 38.104: Adding channel BW support in existing NR bands | Ericsson |
| R4-2501374 | Big CR to TS 38.101-1: Adding channel BW support in existing NR bands | Ericsson |
| R4-2503009 | Big CR to TS 38.104: Adding channel BW support in existing NR bands | Ericsson |
| R4-2503010 | Big CR to TS 38.101-1: Adding channel BW support in existing NR bands | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500065 | CR to TS 38.101-1 to introduce 3MHz BS RF channel BW for n5 and n12 | Nokia, AT&T, Rogers, Verizon |
| R4-2500066 | CR to TS 38.104 to introduce 3MHz BS RF channel BW for n5 and n12 | Nokia, AT&T, Rogers, Verizon |
| R4-2500306 | n48: Adding channels of 50MHz and beyond | Apple |
| R4-2501449 | TP for TR 37.862 on introduction of new channel bandwidths in band n80 and n84 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500185 | CR to TS38.101-5 on introduction of NR band n110 | ZTE Corporation, Sanechips |
| R4-2500406 | CR to 38.101-1 on introduction of Band n110 | Nokia |
| R4-2501057 | TS 38.307: Introduction of NR band n110 | CATT |
| R4-2502824 | TS 38.307: Introduction of NR band n110 | CATT |
| R4-2502842 | CR to 38.101-1 on introduction of Band n110 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500128 | CR to 37.145-1 - Introduction of band 1.4 GHz n110 | Ericsson |
| R4-2500129 | CR to 37.145-2 - Introduction of band 1.4 GHz n110 | Ericsson |
| R4-2500186 | CR to TS37.105 on introduction of NR band n110 | ZTE Corporation, Sanechips |
| R4-2500188 | CR to TS 37.104: n110 band introduction | Huawei, HiSilicon |
| R4-2500189 | CR to TS 37.141: n110 band introduction | Huawei, HiSilicon |
| R4-2500190 | CR to TS 38.141-1: n110 band introduction | Huawei, HiSilicon |
| R4-2500191 | CR to TS 38.141-2: n110 band introduction | Huawei, HiSilicon |
| R4-2500194 | CR to TS 38.106 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500195 | CR to TS 38.115-1 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500196 | CR to TS 38.174 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500197 | CR to TS 38.176-1 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500198 | CR to TS 38.176-2 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500204 | CR to TS 38.106 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500205 | CR to TS 38.115-1 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500206 | CR to TS 38.174 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500207 | CR to TS 38.176-1 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500208 | CR to TS 38.176-2 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2502843 | CR to TS 37.141: n110 band introduction | Huawei, HiSilicon |
| R4-2502844 | CR to TS 38.141-1: n110 band introduction | Huawei, HiSilicon |
| R4-2502845 | CR to TS 38.141-2: n110 band introduction | Huawei, HiSilicon |
| R4-2503005 | CR to TS 37.104: n110 band introduction | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500099 | CR to 36.104 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500100 | CR to 36.141 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500101 | CR to 38.104 on introduction of Band n110 | Nokia, MidWave Wireless |
| R4-2500187 | CR to TS38.133 on introduction of NR band n110 | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500018 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500022 | CR for 36.307 B111 and B3 overlapping bands | Novamint |
| TDoc | Title | Source |
|---|---|---|
| R4-2500019 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500021 | CR related to Introduction of new LTE FDD Band 111 | NOVAMINT |
| R4-2500023 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500024 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500025 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500026 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500027 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500028 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500029 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500030 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500031 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500032 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500033 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500034 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500035 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2500060 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2502846 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2502847 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2502848 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| R4-2502849 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| TDoc | Title | Source |
|---|---|---|
| R4-2500020 | CR related to Introduction of new LTE FDD Band 111 | Novamint |
| TDoc | Title | Source |
|---|---|---|
| R4-2501055 | CR to TS 38.101-1 on introduction NR bands n87 and n88 | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500080 | CR to TS 38.307: n87 and n88 overlapping bands introduction | Huawei, HiSilicon |
| R4-2500081 | CR to TS 37.105: n87 and n88 bands introduction | Huawei, HiSilicon |
| R4-2500082 | CR to TS 37.145-1: n87 and n88 bands introduction | Huawei, HiSilicon |
| R4-2500083 | CR to TS 37.145-2: n87 and n88 bands introduction | Huawei, HiSilicon |
| R4-2500084 | CR to TS 38.101-5: n87 and n88 bands introduction | Huawei, HiSilicon |
| R4-2500091 | CR to 36.141 on introduction of Band n87 and n88 | Nokia |
| R4-2500092 | CR to 37.104 on introduction of Band n87 and n88 | Nokia |
| R4-2500093 | CR to 37.141 on introduction of Band n87 and n88 | Nokia |
| R4-2500094 | CR to 38.104 on introduction of Band n87 and n88 | Nokia |
| R4-2500124 | CR to 36.104 - Introduction of bands n87-n88 | Ericsson |
| R4-2500125 | CR to 38.141-1 - Introduction of bands n87-n88 | Ericsson |
| R4-2500126 | CR to 38.141-2 - Introduction of bands n87-n88 | Ericsson |
| R4-2500175 | CR to TS38.106 on introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
| R4-2500176 | CR to TS38.115-1 on introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
| R4-2500177 | CR to TS38.174 on introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
| R4-2500178 | CR to TS38.176-1 on introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
| R4-2500179 | CR to TS38.176-2 on introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500127 | CR to 38.133 - Introduction of bands n87-n88 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500122 | CR to 38.101-1 - Introduction of band n68 | Ericsson |
| R4-2500123 | CR to 38.101-5 - Introduction of band n68 | Ericsson |
| R4-2500130 | CR to 38.101-5 - Introduction of band n68 | Ericsson Limited |
| R4-2500309 | n68: Introduction of the new band and NS_26 and NS_36 | Apple |
| R4-2500423 | n68 NS_26 and NS_36 A-MPR proposals | Nokia |
| R4-2501739 | A-MPR values for NS_36 and NS_2 | Qualcomm Technologies |
| R4-2501825 | Introduction of NR band n68 | Nokia |
| R4-2502823 | CR to 38.101-1 - Introduction of band n68 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500076 | CR to TS 37.105: n68 band introduction | Huawei, HiSilicon |
| R4-2500077 | CR to TS 37.145-1: n68 band introduction | Huawei, HiSilicon |
| R4-2500078 | CR to TS 37.145-2: n68 band introduction | Huawei, HiSilicon |
| R4-2500079 | CR to TS 38.141-2: n68 band introduction | Huawei, HiSilicon |
| R4-2500120 | CR to 36.104 - Introduction of band n68 | Ericsson |
| R4-2500121 | CR to 38.104 - Introduction of band n68 | Ericsson |
| R4-2500180 | CR to TS38.106 on introduction of NR band n68 | ZTE Corporation, Sanechips |
| R4-2500181 | CR to TS38.115-1 on introduction of NR band n68 | ZTE Corporation, Sanechips |
| R4-2500182 | CR to TS38.174 on introduction of NR band n68 | ZTE Corporation, Sanechips |
| R4-2500183 | CR to TS38.176-1 on introduction of NR band n68 | ZTE Corporation, Sanechips |
| R4-2500184 | CR to TS38.176-2 on introduction of NR band n68 | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500095 | CR to 36.141 on introduction of Band n68 | Nokia |
| R4-2500096 | CR to 37.104 on introduction of Band n68 | Nokia |
| R4-2500097 | CR to 37.141 on introduction of Band n68 | Nokia |
| R4-2500098 | CR to 38.141-1 on introduction of Band n68 | Nokia |
| R4-2501056 | CR to TS 38.133- Introduction of NR band n68 | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2501330 | Discussion on UE-to-UE coexistence of n252 UL interference with n2 DL and n25 DL | MediaTek (Hefei) Inc. |
| R4-2502162 | Draft CR to TR 38.863 to capture agreement for n252 WI | EchoStar, Boost Mobile Network |
| TDoc | Title | Source |
|---|---|---|
| R4-2500291 | Further input on UE power back-off while operating in 2000-2020 MHz UL range of the NTN band n252 | Apple |
| R4-2500425 | On NTN S-Band UE Coexistence Requirement | Verizon Finland |
| R4-2500429 | On NTN S-Band UE Coexistence Requirement | Verizon, T-Mobile USA, AT&T |
| R4-2500430 | On NTN S-Band UE Coexistence Requirement | Verizon, T-Mobile USA, AT&T |
| R4-2500602 | Discussion on system parameters and UE RF requirements for NR-NTN S-band | ZTE Corporation, Sanechips |
| R4-2501002 | Discussion on UE RF requirements for the NTN new S-band | CATT |
| R4-2501118 | Way Forward on n252/band 252 co-existence | EchoStar, Boost Mobile Network |
| R4-2501321 | Discussion on NR-NTN n252 UE RF requirements | MediaTek (Hefei) Inc. |
| R4-2501455 | Discussion on the NTN S band definition | Huawei, HiSilicon |
| R4-2501706 | Discussion on NR-NTN n252 UE RF requirements | Tejas Network Limited |
| R4-2502005 | UE-to-UE coexistence and OOB blocking for n252 | Qualcomm Inc. |
| R4-2502202 | NTN S-Band UE-UE coexistence | T-Mobile USA, Verizon |
| R4-2503078 | Discussion on NR-NTN n252 UE RF requirements | Tejas Network Limited |
| TDoc | Title | Source |
|---|---|---|
| R4-2501001 | Discussion on SAN RF requirements for the NTN new S-band | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2501179 | Draft CR to TS 38.133 Introduction of a new NTN S-band | ZTECorporation,Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2501329 | Discussion on IoT-NTN B252 UE RF requirements | MediaTek (Hefei) Inc. |
| R4-2502004 | UE-to-UE coexistence and OOB blocking for B252 | Qualcomm Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2501181 | Draft CR to TS 36.133 Introduction of a new IoT NTN S-band | ZTECorporation,Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500292 | Emission requirements for the UE operating in 1626.5-1660.5MHz and 1668-1675MHz UL frequency ranges | Apple |
| R4-2501309 | Discussion on UE RF requirements for NR-NTN bands to support the Extended L-band and the combined MSS L-band and Extended L-band ranges | MediaTek (Hefei) Inc. |
| R4-2501454 | Discussion on the full NTN L band definition | Huawei, HiSilicon |
| R4-2502011 | On protection of radioastronomy and radiated regulatory requirements | Qualcomm Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2501180 | Draft CR to TS 38.133 Introduction of a new NTN L-band | ZTECorporation,Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2501296 | CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | BNE, EBU |
| R4-2501311 | CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | BNE, EBU |
| TDoc | Title | Source |
|---|---|---|
| R4-2501195 | Discussion on introduction of new bands for LTE based 5G terrestrial broadcast for early deployments | BNE, EBU |
| R4-2502136 | Handling of band 108 sub-bands introduction | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2501914 | CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | BNE, EBU |
| R4-2501915 | CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | BNE, EBU |
| TDoc | Title | Source |
|---|---|---|
| R4-2501918 | CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | BNE, EBU |
| R4-2502137 | Consideration of BS RF aspects for 108 sub-bands introduction | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500145 | TR 38.749 v0.1.0 Protection of Earth Exploration Satellite Service (EESS) | Huawei, HiSilicon |
| R4-2501408 | Big CR on UE RF requirements for WI NR_mmWave_protect | China Unicom, Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500143 | draftCR to 38.101-2 on FR2 EESS | Huawei, HiSilicon |
| R4-2500144 | TP for TR38.749: EESS in Rel-19 | Huawei, HiSilicon |
| R4-2500282 | Discussion on Rel-19 EESS | Huawei Device Co., Ltd |
| R4-2500494 | 24 GHz EESS band phase 2 compliance | Qualcomm Incorporated |
| R4-2500943 | On EESS new NS modified MPR behaviour | ZTE Corporation, Sanechips |
| R4-2500944 | Draft CR to TS 38101-2 - EESS protection(Annex H) | ZTE Corporation, Sanechips |
| R4-2500945 | TP for TR38.749 Study outcome in previous releases(Clause 5) | ZTE Corporation, Sanechips |
| R4-2501359 | CR to TS 38101-2 - EESS protection - UE RF impacts | Ericsson |
| R4-2501734 | Draft CR to add new requirements for EESS protection from n257 and n258 | NTT DOCOMO INC. |
| R4-2501735 | Draft CR to add new requirements for EESS protection from Rel-15 | NTT DOCOMO INC. |
| R4-2502851 | Draft CR to add new requirements for EESS protection from n257 and n258 | NTT DOCOMO INC. |
| R4-2502852 | Draft CR to add new requirements for EESS protection from Rel-15 | NTT DOCOMO INC. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500067 | BS RF specification impact for MmWave UE spurious emission | Nokia |
| R4-2501360 | EESS protection - TP to TR 38749 - BS aspects | Ericsson |
| R4-2502128 | TP to TR 38.749: BS RF requirements section correction (clause 9) | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500119 | CR to 38.104: Addition of HAPS bands | SoftBank, Ericsson, Nokia, Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500117 | Further discussion on HPUE MSD rules | Murata Manufacturing Co Ltd. |
| R4-2500140 | Discussion on HPUE MSD | Huawei, HiSilicon |
| R4-2500141 | draftCR to 38.101-1 HPUE duty-cycle based SAR solution in Rel-19 | Huawei, HiSilicon |
| R4-2500142 | draftCR to 38.101-3 HPUE duty-cycle based SAR solution in Rel-19 | Huawei, HiSilicon |
| R4-2500218 | Simplification of HPUE 2UL DeltaMSD | Skyworks Solutions Inc. |
| R4-2500315 | On Rel-19 HPUE CA DC MSD consideration | Apple |
| R4-2500376 | On 2UL MSD look-up table | Nokia |
| R4-2500731 | Discussion on HPUE MSD simplification | vivo |
| R4-2500769 | draft CR on duty cycle solution for ENDC | vivo |
| R4-2500770 | draft CR on duty cycle solution for PC1.5 of CA | vivo |
| R4-2500797 | On SAR Solution of R19 HPUE for CA | China Telecom |
| R4-2500803 | Views on MSD for HPUE TN | Samsung |
| R4-2500948 | On R19 increase power limit left issue and MSD rule | ZTE Corporation, Sanechips |
| R4-2501282 | Discussion on general aspects of Rel.19 HPUE | CHTTL |
| R4-2501579 | MSD beyond PC3 | Qualcomm France |
| R4-2501590 | draftCR on duty cycle solutions for PC1.5 HPUE CA in Rel-19 | China Telecom |
| R4-2501591 | draftCR on duty cycle solutions for PC1.5 PHUE NE-DC in Rel-19 | China Telecom |
| R4-2501685 | Duty cycle solutions and MSD rules for HPUE inter-band UL CA and EN-DC | LG Electronics |
| R4-2501955 | 1UL MSD simplifications rules for Rel-19 | Skyworks Solutions Inc., Nokia |
| R4-2502865 | draft CR on duty cycle solution for PC1.5 of CA | vivo |
| R4-2502866 | draft CR on duty cycle solution for ENDC | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500316 | On PC1.5 intra-band UL CA MPR | Apple |
| R4-2500732 | Further discussion on HPUE for intra-band contiguous and non-contiguous CA | vivo |
| R4-2500804 | On intra-band ULCA | Samsung |
| R4-2500951 | On the open issues for R19 PC1.5 Intra-band UL CA | ZTE Corporation, Sanechips |
| R4-2501161 | Discussion on PC1.5 Pcmaxfor intra-band NC CA with dual PA | Xiaomi |
| R4-2501492 | R19 MPR for PC1.5 contig CA | OPPO |
| R4-2501493 | R19 MPR for PC1.5 NCCA | OPPO |
| R4-2501742 | MPR Intra-band contiguous UL CA for PC1.5 | Qualcomm Technologies |
| R4-2502067 | Measurement results for PC1.5 intra-band contiguous ULCA | Skyworks Solutions Inc. |
| R4-2502091 | HPUE for intra-band UL CA | LG Electronics Finland |
| R4-2502141 | draft CR on MPR for PC1.5 intra-band contiguous CA | LG Electronics Finland |
| R4-2502142 | draft CR on MPR for PC1.5 intra-band non-contiguous CA | LG Electronics Finland |
| R4-2502151 | draft CR on Pcmax,c for PC1.5 intra-band NC CA | LG Electronics Finland |
| R4-2502234 | Discussion on the intra-band CA with PC1.5 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500112 | Redundancies in 2Tx/3Tx notes | Qualcomm, Nokia, Verizon, T-Mobile |
| R4-2500113 | dCR to 38.101-1, to remove redundancies in 2Tx/3Tx notes | Qualcomm, Nokia, Verizon, T-Mobile |
| R4-2500317 | On Rel-19 HPUE inter-band UL CA DC configurations | Apple |
| R4-2500484 | dCR to 38.101-1, to remove redundancies in 2Tx/3Tx notes | Qualcomm, Nokia, Verizon, T-Mobile |
| R4-2500805 | Re-organize the 3Tx Notes and Release independence for 3Tx | Samsung |
| R4-2500949 | On release independence for 3Tx inter-band UL CA | ZTE Corporation, Sanechips |
| R4-2500950 | Draft CR to TS 38.307 Release independence for R19 3Tx band combination | ZTE Corporation, Sanechips |
| R4-2501197 | draft CR for the support of 3Tx PC1.5 FDD-TDD inter-band EN-DC for SAR compliance | CHTTL |
| R4-2501605 | Discussion on Inter-band UL CA or DC with 2Tx or 3Tx | vivo Mobile Com. (Chongqing) |
| R4-2501686 | HPUE for inter-band UL CA and EN-DC | LG Electronics |
| R4-2502868 | dCR to 38.101-1, to remove redundancies in 2Tx/3Tx notes | Qualcomm, Nokia, Verizon, T-Mobile |
| TDoc | Title | Source |
|---|---|---|
| R4-2500806 | Rel-19 draft CR for 38.101-1 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia, Qualcomm, Apple, Ericsson, vivo, ZTE,OPPO, Huawei, Hisilicon, LG Electronics, CHTTL, Skyworks, xiaomi |
| R4-2502867 | Rel-19 draft CR for 38.101-1 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia, Qualcomm, Apple, Ericsson, vivo, ZTE,OPPO, Huawei, Hisilicon, LG Electronics, CHTTL, Skyworks, xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R4-2500304 | On Rel-19 power domain enhancement for FR1 | Apple |
| R4-2500340 | Views on Power domain enhancements for single carrier | China Telecom |
| R4-2500374 | On MPR Enhancement | Nokia |
| R4-2500603 | Discussion on power domain enhancements for single carrier | ZTE Corporation |
| R4-2500647 | Power domain enhancements for single carrier | Xiaomi |
| R4-2500728 | Discussion on UE RF power enhancement for NR single carrier | vivo |
| R4-2500729 | draftCR to TS 38.101-1 on MPR reduction for single carrier | vivo |
| R4-2501076 | Further discussion on power domain enhancements for single carrier | CATT |
| R4-2501154 | Further Views on MPR Reduction | Sony |
| R4-2501310 | Discussion on BS indication for MPR reduction | NTT DOCOMO INC. |
| R4-2501471 | Discussion on MPR reduction for single carrier | OPPO |
| R4-2501478 | Discussion on power domain enhancement for NR single carrier | MediaTek (Wuhan) Inc. |
| R4-2501489 | BW or RB extension approach for improving MPR when NW BW is larger than UE CBW | Skyworks Solutions Inc. |
| R4-2501762 | Power boosting and MPR reduction | Qualcomm Technologies |
| R4-2501832 | On power domain enhancements for single carrier | Huawei, HiSilicon |
| R4-2501833 | Draft CR for TS 38.101-1 to introduce MPR reduction for single carrier | Huawei, HiSilicon |
| R4-2502254 | A-MPR Handling with Bandwidth Extension | Lenovo |
| R4-2502259 | Discussion on Power domain enhancements for single carrier | LG Electronics UK |
| TDoc | Title | Source |
|---|---|---|
| R4-2500604 | DraftCR to 38.101-1 MPR applicability for FR1 intra-band contiguous UL CA | ZTE Corporation |
| R4-2500646 | MPR applicability for FR1 intra-band UL CA | Xiaomi |
| R4-2501077 | Further discussion on MPR applicability for FR1 intra-band UL CA | CATT |
| R4-2501750 | MPR for FR1 intra-band UL CA | Qualcomm Technologies |
| R4-2501834 | On MPR applicability for FR1 intra-band UL CA | Huawei, HiSilicon |
| R4-2502252 | Bandwidth Extension for Intra-Band UL CA | Lenovo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500114 | FR2 MPR enhancement overview | Qualcomm Incorporated |
| R4-2500498 | Discussion on MPR enhancement for FR2 CA and draft LS | Samsung |
| R4-2500730 | Discussion on MPR applicability for FR2 | vivo |
| R4-2501307 | Discussion on MPR improvement for FR2 | NTT DOCOMO INC. |
| R4-2501835 | On MPR applicability for FR2 CA | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500050 | Feasibility evaluation of MIMO layer for 6Rx UE | MediaTek inc. |
| R4-2500115 | Discussion on the demodulation performance requirements for 6Rx devices | QUALCOMM Europe Inc. - Spain |
| R4-2500275 | Views on Maximum Number of MIMO Layers for 6Rx UEs | Apple |
| R4-2500733 | Simulation results of MIMO layer evaluation for 6Rx UE | vivo |
| R4-2500819 | Discussion on feasibility with regards to 6 layer 6Rx MIMO | Nokia |
| R4-2501192 | Discussion on MIMO layer for 6Rx UE | |
| R4-2501427 | Further Discussion and simulation results on MIMO layer evaluation for 6Rx UE | Samsung |
| R4-2501500 | Discussion on MIMO layer evaluation for 6Rx UE | ZTE Corporation, Sanechips |
| R4-2501836 | On MIMO layer evaluation for 6Rx UE | Huawei, HiSilicon |
| R4-2501935 | Discussion on the support of MIMO layers for 6Rx UE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500312 | On the values of Delta_TRxSRS for 6Rx SRS antenna switching | Apple |
| R4-2500734 | Further discussion on SRS antenna switching requirements for 6Rx | vivo |
| R4-2500799 | Disscussion on SRS antenna switching requirements for 6RX UE | Spreadtrum Communications |
| R4-2500896 | Disscussion on SRS antenna switching requirements for 6RX UE | Spreadtrum,UNISOC |
| R4-2500899 | Discussion for 6 Rx TRxSRS | LG Electronics France |
| R4-2500946 | On 3T6R SRS antenna switching requirements | ZTE Corporation, Sanechips |
| R4-2501582 | SRS antenna switching and ?TRxSRS | Qualcomm France |
| R4-2501837 | On 6Rx SRS antenna switching requirements | Huawei, HiSilicon |
| R4-2502190 | On DeltaT_RxSRS requirements for 3T6R SRS-AS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500311 | On SRS Antenna Switching IL Imbalance Solution for 6Rx | Apple |
| R4-2500341 | Further study on SRS IL imbalance | China Telecom |
| R4-2500404 | SRS imbalance solution considerations | Nokia |
| R4-2500761 | Discussion on SRS IL imbalance reporting | vivo |
| R4-2500800 | Disscussion on SRS IL imbalance for 6RX UE | Spreadtrum Communications |
| R4-2500897 | Disscussion on SRS IL imbalance for 6RX UE | Spreadtrum,UNISOC |
| R4-2500947 | Views on 6Rx SRS antenna IL | ZTE Corporation, Sanechips |
| R4-2501193 | Discussion on SRS IL imbalance for 6Rx UE | |
| R4-2501411 | Views on SRS IL imbalance issue | Samsung |
| R4-2501583 | About SRS IL Imbalance indication | Qualcomm France |
| R4-2501838 | On SRS IL imbalance issue | Huawei, HiSilicon |
| R4-2501903 | Views on SRS insertion loss compensation and reporting enhancements | Intel Corporation |
| R4-2502191 | On the SRS IL imbalance reporting details for the SRS-AS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500524 | Topic summary for [114][210] NR_ENDC_RF_Ph4 | Moderator (Huawei) |
| R4-2500668 | Topic summary for [114][116] NR_ENDC_RF_Ph4_part1 | Moderator(Huawei) |
| R4-2500669 | Topic summary for [114][117] NR_ENDC_RF_Ph4_part2 | Moderator(Samsung) |
| R4-2500670 | Topic summary for [114][118] NR_ENDC_RF_Ph4_part3 | Moderator(AT&T) |
| R4-2502862 | WF on 6Rx requirements | AT&T |
| R4-2502863 | WF on TN HPUE | Samsung, Skyworks, OPPO, LGE, Apple |
| R4-2502864 | WF on MSD rules | Skyworks, Qualcomm, Nokia, Murata |
| R4-2502878 | WF on power domain enhancement | Huawei |
| R4-2503013 | WF on Power domain enhancement | Huawei, HiSilicon |
| R4-2503014 | WF on 6Rx requirements | AT&T |
| TDoc | Title | Source |
|---|---|---|
| R4-2500068 | TP to TR 38.922: Corrections and clarifications on IMT parameters for 4400 to 4800 MHz frequency range | Nokia |
| R4-2501064 | TP to TR38.922 on 4400 - 4800 frequency range | CATT |
| R4-2501512 | Draft TR 38.922 Study on International Mobile Telecommunications (IMT) parameters for 4400 - 4800 MHz, 7125 - 8400 MHz and 14800 - 15350 MHz | Ericsson |
| R4-2502245 | TP to TR 38.922 Editorial corrections for 4400 to 4800 MHz frequency range | Ericsson |
| R4-2502880 | TP to TR 38.922 Editorial corrections for 4400 to 4800 MHz frequency range | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500069 | TP to TR 38.922: Corrections and clarifications on IMT parameters for 7125 to 8400 MHz frequency range | Nokia |
| R4-2501065 | TP to TR38.922 on 7125 - 8400 frequency range | CATT |
| R4-2501699 | Text proposal on 7125 – 8400 MHz IMT parameters in TR 38.922 | Qualcomm Germany, Nokia, Ericsson |
| R4-2502246 | TP to TR 38.922 Editorial corrections for 7125 to 8400 MHz frequency range | Ericsson |
| R4-2502881 | TP to TR 38.922: Corrections and clarifications on IMT parameters for 7125 to 8400 MHz frequency range | Nokia |
| R4-2502882 | Text proposal on 7125 – 8400 MHz IMT parameters in TR 38.922 | Qualcomm Germany, Nokia, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500070 | BS in-band blocking requirements for 14800 to 15350 MHz frequency range | Nokia |
| R4-2500071 | LS Reply on Parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | Nokia |
| R4-2500289 | Clarifications to observations for 7125-8400 MHz frequency range | Apple |
| R4-2500290 | Editorial corrections for the UE IMT parameters for the 15GHz range | Apple |
| R4-2500344 | Discussion on BS OBB for 14800 to 15350 MHz frequency range | Fujitsu Limited |
| R4-2500774 | TP to TR 38.922: Co-existence study | Murata Manufacturing Co Ltd. |
| R4-2501063 | Further discussion on BS in-band blocking for the frequency range 14.8GHz - 15.35GHz | CATT |
| R4-2501066 | TP to TR 38.922 on BS parameters for 14.8 - 15.35GHz frequency range | CATT |
| R4-2501861 | Remaining issues on BS RF requirments for 15 GHz | Huawei, HiSilicon |
| R4-2501862 | TP to TR to update simulation results for 15 GHz | Huawei, HiSilicon |
| R4-2501881 | Discussion on the remaining issue for 15GHz BS RF requirements | ZTE Corporation, Sanechips |
| R4-2502243 | On open issues for 14800 - 15350 MHz | Ericsson |
| R4-2502244 | TP to TR 38.922 Addition of Clause 6.2, 6.3 and editorial corrections for 14800 to 15350 MHz | Ericsson |
| R4-2502854 | LS Reply on Parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | Nokia |
| R4-2502883 | TP to TR 38.922 on BS parameters for 14.8 - 15.35GHz frequency range | CATT |
| R4-2503007 | Clarifications to observations for 7125-8400 MHz frequency range | Apple |
| R4-2503015 | LS Reply on Parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500072 | TP to TR 38.922: Simulation results on MIMO modeling | Nokia |
| R4-2502247 | TP to TR 38.922 Editorial corrections for Additional Information on AAS | Ericsson |
| R4-2502884 | TP to TR 38.922 Editorial corrections for Additional Information on AAS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500671 | Topic summary for [114][119] FS_NR_IMT | Moderator(Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R4-2501799 | UE RF requirments for intra-band non-contiguous CA | OPPO |
| R4-2502153 | Tx requirements for SL intra-band non-contiguous CA | LG Electronics Finland |
| R4-2502154 | TP to TR on SL intra-band NC CA A-MPR | LG Electronics Finland |
| R4-2502161 | Draft CR on MPR for SL intra-band non-contiguous CA | LG Electronics Finland |
| TDoc | Title | Source |
|---|---|---|
| R4-2501687 | Draft CR on MPR for SL intra-band contiguous CA | LG Electronics |
| TDoc | Title | Source |
|---|---|---|
| R4-2500672 | Topic summary for [114][120] NR_SL_intraB_CA_ITS_part1 | Moderator(OPPO) |
| R4-2500673 | Topic summary for [114][121] NR_SL_intraB_CA_ITS_part2 | Moderator(LGE) |
| TDoc | Title | Source |
|---|---|---|
| R4-2501062 | Draft CR for less than 5MHz UE RF requirements in Rel-19 | CATT |
| R4-2501143 | Big CR for less than 5MHz UE RF requirements in Rel-19 | Intel Corporation |
| R4-2502260 | Big CR for less than 5MHz UE RF requirements in Rel-19 | Intel Corporation |
| R4-2502262 | Big CR for less than 5MHz UE RF requirements in Rel-19 | Intel Corporation |
| TDoc | Title | Source |
|---|---|---|
| R4-2500698 | Discussion on RRM impacts for less than 5MHz BW | ZTE Corporation, Sanechips |
| R4-2501144 | Big CR for less than 5MHz RRM requirements in Rel-19 | Intel Corporation |
| R4-2501260 | draftCR on RRM requirements for less than 5MHz Ph2 | Huawei, HiSilicon |
| R4-2501705 | Correction in Big CR for less than 5MHz RRM requirements in Rel-19 | Ericsson |
| R4-2502608 | Big CR for less than 5MHz RRM requirements in Rel-19 | Intel Corporation |
| R4-2502682 | Correction in Big CR for less than 5MHz RRM requirements in Rel-19 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500699 | Discussion on performance for less than 5MHz BW | ZTE Corporation, Sanechips |
| R4-2500712 | draft CR to TS 38.133: NR channel BW less than 5MHz for FR1 | ZTE Corporation, Sanechips |
| R4-2501145 | Discussion on Performance part of less than 5MHz RRM requirements in Rel-19 | Intel Corporation |
| R4-2501261 | Discussion on performance part for less than 5MHz Ph2 | Huawei, HiSilicon |
| R4-2501704 | NR CA/DC Performance Requirements for Less Than 5 MHz | Ericsson |
| R4-2501983 | Discussion on performance part for less than 5MHz Ph2 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500525 | Topic summary for [114][211] NR_FR1_lessthan_5MHz_BW_Ph2 | Moderator (Intel) |
| R4-2500674 | Topic summary for [114][122] NR_FR1_5MHz_BW_Ph2 | Moderator(Intel) |
| R4-2502586 | WF on RRM requirements for NR_FR1_lessthan_5MHz_BW_Ph2 | Intel |
| TDoc | Title | Source |
|---|---|---|
| R4-2501578 | Intra-band Non-collocated NR CA/EN-DC requirements | Qualcomm France |
| TDoc | Title | Source |
|---|---|---|
| R4-2500436 | RF requirement impact for type 4 UE | Apple |
| R4-2501620 | UE RF requirements for Type 4a/4b capable FWA UE for EN-DC/NR-CA | Ericsson |
| R4-2501798 | UE RF requirments for type 4 | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500375 | On non-collocated intra-band EN-DC and NR-CA open issues | Nokia |
| R4-2500409 | Remaining discussions on UE capability for type 4 UEs | Huawei, HiSilicon |
| R4-2500415 | Discussion on BS Signaling for non-collocated Type 4a4b | KDDI Corporation |
| R4-2500437 | On signalling support for type 4 UE | Apple |
| R4-2500807 | Discussion on UE and NW behavior for non-collocated deployment | Samsung |
| R4-2500952 | Discussion on UE Capability UE behavior and network signaling for Type 4a Type 4b EN-DCNR-CA | ZTE Corporation, Sanechips |
| R4-2501619 | UE Capability/UE behavior and network signaling for Type 4 EN-DC/NR-CA | Ericsson |
| R4-2501797 | UE capability and network signalling for type 4-v1 | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500438 | On definition of UE types for NonCol_intraB | Apple |
| R4-2501796 | other aspects | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500440 | On RRM requirement impact for type 4 UE | Apple |
| R4-2500441 | draft CR on scheduling availability for type 4 UE | Apple |
| R4-2500470 | RRM requirements for intra-band non-collocated scenarios Phase2 | Nokia, Nokia Shanghai Bell |
| R4-2500705 | draftCR on SCell Activation Delay Requirement for NonCol_intraB | ZTE Corporation, Sanechips |
| R4-2501229 | Draft CR on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) | Huawei, HiSilicon |
| R4-2501616 | Remaining requirements for type 4 UEs in non-colocated scenario | Ericsson |
| R4-2501617 | DraftCR: Scheduling availability of UE during radio link monitoring | Ericsson |
| R4-2501618 | DraftCR: Scheduling availability of UE performing beam failure detection + L1-RSRP | Ericsson |
| R4-2501681 | Draft CR on interruption requirements for Type 4 capable UE in EN-DCNR-CA | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500526 | Topic summary for [114][212] NonCol_intraB_ENDC_NR_CA_Ph2 | Moderator (Huawei) |
| R4-2500675 | Topic summary for [114][123] NonCol_intraB_ENDC_NR_CA | Moderator(KDDI) |
| R4-2502587 | WF on RRM requirements for NonCol_intraB_ENDC_NR_CA_Ph2 | Huawei |
| R4-2502924 | WF on UE requirements for non-collocated scenario | KDDI |
| TDoc | Title | Source |
|---|---|---|
| R4-2500039 | Comments on Fragmented Carrier Signalling | Rogers Communications Canada, CableLabs |
| R4-2501124 | TP for TR38.755 | MediaTek Inc., Nokia, [Apple, Ericsson, Huawei, Skyworks,…] |
| R4-2502529 | TP for TR38.755 | MediaTek Inc., Nokia, OPPO, vivo [Apple, Ericsson, Huawei, Skyworks,…] |
| R4-2502925 | TP for TR38.755 | MediaTek Inc., Nokia, [Apple, Ericsson, Huawei, Skyworks,…] |
| TDoc | Title | Source |
|---|---|---|
| R4-2500243 | On methods for reducing the number of UE Rx chains for fragmented carriers | Apple |
| R4-2500613 | UE mechanism to trigger one RF RX chain mode | Qualcomm Incorporated |
| R4-2500650 | Methods for reducing the number of UE Rx chains | Xiaomi |
| R4-2500726 | Discussion on methods for reducing the number of UE RX chains | vivo |
| R4-2500808 | Discussion on general aspects for fragmented carriers | Samsung |
| R4-2500941 | Discussion the methods for reducing the number of UE Rx chain | ZTE Corporation, Sanechips |
| R4-2501150 | Discussion on remaining signalling aspects for DL fragmented carriers study | MediaTek Inc. |
| R4-2501189 | Discussion on methods for reducing the number of UE Rx chains for fragmented carriers | |
| R4-2501196 | Disscussion on methods for reducing the number of UE RX chains | Spreadtrum,UNISOC |
| R4-2501295 | Views on enabling condition on the FR1 fragmented carriers | CHTTL |
| R4-2501472 | Discussion on reducing the number of UE Rx chains | OPPO |
| R4-2501802 | On signalling aspect of fragmented carriers | Huawei, HiSilicon |
| R4-2501896 | Discussion on methods for reducing the number of UE Rx chains | Nokia |
| R4-2501936 | Discussion on UE signaling of Fragmented Carriers | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500118 | Discussion on UE RF requirement impact for DL fragmented carriers | Murata Manufacturing Co Ltd. |
| R4-2500219 | In-Gap Blocking for Fragmented Carrier | Murata Manufacturing Co Ltd. |
| R4-2500244 | On UE RF requirements for fragmented carriers | Apple |
| R4-2500727 | Impacts on UE RF requirements and DL performance | vivo |
| R4-2500809 | Link budget calculation for DL performance with shared Rx RF chain | Samsung |
| R4-2500942 | Discussion on the RF requirement for fragmented carrier | ZTE Corporation, Sanechips |
| R4-2501032 | Discussion on fragmented DL carriers | CATT |
| R4-2501397 | Discussion of impacts on UE RF requirements and DL performance impacts | MediaTek Inc. |
| R4-2501473 | Discussion on impacts on UE RF requirements | OPPO |
| R4-2501662 | Discussion on requirements for Fragmented CA | Nokia |
| R4-2501803 | On RF requirements of fragmented carriers | Huawei, HiSilicon |
| R4-2501937 | Discusson on impact on UE RF requirement of fragmented carriers | Ericsson |
| R4-2502949 | Impacts on UE RF requirements and DL performance impacts | MediaTek Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500676 | Topic summary for [114][124] FS_NR_DL_Frag_Carrier | Moderator(Mediatek) |
| R4-2502872 | Ad hoc minutes on fragmented DL | MediaTek |
| R4-2502873 | WF on fragmented DL | MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R4-2500220 | PC2 1RX RSD for RedCap FDD bands | Murata Manufacturing Co Ltd. |
| R4-2500318 | On PC2 RedCap n1 and n3 1Rx REFSENS | Apple |
| R4-2500939 | Discussion on HPUE RedCap in FR1 | ZTE Corporation, Sanechips |
| R4-2501109 | RF requirements for PC2 RedCap in FDD bands | China Telecom |
| R4-2501453 | Discussion on the Rel-19 PC2 FDD RedCap UE | Huawei, HiSilicon |
| R4-2501972 | (NR_PC2_RedCap_UE) CR to 38.101-1: PC2 Redcap support for TDD bands | Nokia |
| R4-2501985 | PC2 RSD for the FD-FDD RedCap UE | Skyworks Solutions Inc. |
| R4-2501996 | On PC2 for the HD-FDD RedCap UE | Skyworks Solutions Inc. |
| R4-2502017 | UE RF requirements for (e)RedCap PC2 UE | Qualcomm Inc. |
| R4-2502102 | RF Impact for FDD bands for PC2 RedCap | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500677 | Topic summary for [114][125] NR_PC2_RedCap_UE | Moderator(China Telecom) |
| R4-2500994 | Discussion on UE RF requirements for RedCap PC2 FDD | CATT |
| R4-2502874 | WF on NR PC2 RedCap UE in FDD bands | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R4-2500089 | Work plan for low NR band carrier aggregation via switching | AT&T |
| R4-2500215 | Skeleton TR 38.768 on low NR band carrier aggregation via switching v0.0.1 | Apple Benelux B.V. |
| R4-2500322 | Skeleton TR 38.768 on low NR band carrier aggregation via switching v0.0.1 | Apple |
| R4-2501119 | Discussion on scope clarification for low-band CA switching | MediaTek Inc. |
| R4-2502875 | Skeleton TR 38.768 on low NR band carrier aggregation via switching v0.0.2 | Apple Benelux B.V. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500139 | Discussion on LB-LB switching | Huawei, HiSilicon |
| R4-2500313 | Initial Views on UE RF requirements for LB CA via switching | Apple |
| R4-2500405 | NR_LBCA_Sw Considerations | Nokia |
| R4-2500492 | Initial aspects of RX Switching | Qualcomm Incorporated |
| R4-2500644 | RF requiremenst for LB-LB CA via swicthing | Xiaomi |
| R4-2500768 | Discussion of UE RF impact for LB-LB switching | vivo |
| R4-2500940 | Discussion on low-low band CA via switching | ZTE Corporation, Sanechips |
| R4-2501031 | Discussion on time mask of low band carrier aggregation | CATT |
| R4-2501121 | Discussion on low-band CA switching | MediaTek Inc. |
| R4-2501122 | Disscussion on UE RF requirements for LB-LB CA switching | Spreadtrum,UNISOC |
| R4-2501169 | Discussion on low band carrier aggregation via switching | |
| R4-2501410 | Views on UE RF requirements for LB CA switching | Samsung |
| R4-2501572 | Time masks for LB-LB CA switching | Ericsson |
| R4-2501988 | NR Low-Band CA Switching | Skyworks Solutions Inc. |
| R4-2502255 | UE RF requirements and UE capability of LB carrier aggregation | LG Electronics UK |
| TDoc | Title | Source |
|---|---|---|
| R4-2500237 | On RRM requirement for R19 LB CA | Apple |
| R4-2500645 | RRM requiremenst for LB-LB CA via swicthing | Xiaomi |
| R4-2500828 | Discussion on RRM requirements for low band carrier aggregation via switching | vivo |
| R4-2500894 | Discussion on RRM requirements for Low Band CA operation | LG Electronics Inc. |
| R4-2500914 | Discussion on RRM aspects of R19 Low band carrier aggregation via switching | ZTE Corporation, Sanechips |
| R4-2501048 | Discussion on the impacts of low band CA via switching on RRM requirements | CATT |
| R4-2501236 | Discussion on low band carrier aggregation via switching | Huawei, HiSilicon |
| R4-2501680 | General discussion on RRM requirements for LB CA switching | Samsung |
| R4-2502061 | RRM core requirements for low band CA via swithcing | Ericsson |
| R4-2502081 | Discussion on low-band CA switching | MediaTek inc. |
| R4-2502148 | On LBCA switching RRM requirements | Nokia |
| R4-2502170 | RRM requirements for low band carrier aggregation via switching | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500527 | Topic summary for [114][213] NR_LBCA_Sw | Moderator (Apple) |
| R4-2500678 | Topic summary for [114][126] NR_LBCA_Sw | Moderator(Apple) |
| R4-2502588 | WF on RRM requirements for NR_LBCA_Sw | Apple |
| R4-2502663 | Ad-hoc minutes for [114][213] NR_LBCA_Sw | Apple |
| R4-2502664 | LS of RAN4 agreements on LB CA via switching | Apple |
| R4-2502697 | LS of RAN4 RRM agreements on LB CA via switching | Apple |
| R4-2502853 | Topic summary for [114][126] NR_LBCA_Sw | Moderator(Apple) |
| R4-2502876 | WF on low-low band switching | Apple |
| R4-2502877 | LS on switching periods for low-low band switching | AT&T |
| R4-2503016 | WF on low-low band switching | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500695 | Work plan on 7MHz Channel Bandwidth for n26 and n5 | China Telecom,T-Mobile USA |
| R4-2501059 | Discussion on release independence for 7MHz channel bandwidth | CATT |
| R4-2502133 | BS specifications missing in the WID | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500310 | On the introduction of 7MHz CBW | Apple |
| R4-2500408 | Introduction of 7MHz channel bandwidth: System parameters and RF requirements | Huawei, HiSilicon |
| R4-2500420 | Inputs to 7MHz CBW | Skyworks Solutions Inc. |
| R4-2500496 | 7 MHz Channel Bandwidth for Bands n26 and n5 | Qualcomm Incorporated |
| R4-2500557 | Discussion on system parameters and UE RF requirements to introduce 7MHz for n5 and n26 | ZTE Corporation, Sanechips |
| R4-2501060 | Discussion on spectrum utilization and UE RF requirements for 7MHz channel bandwidth | CATT |
| R4-2501361 | 7 MHz channel BW: system parameters and UE RF impacts | Ericsson |
| R4-2501362 | 7 MHz channel BW: UE RF impacts | Ericsson |
| R4-2501479 | Discussion on UE RF requirements and system parameters for 7MHz | MediaTek (Wuhan) Inc. |
| R4-2501824 | Discussion on system parameter and UE RF aspects of 7 MHz channel bandwidth | Nokia |
| R4-2502199 | Release Independence of the 7 MHz channel bandwidth | T-Mobile USA, China Telecom, Ericsson |
| R4-2502200 | Spectrum Utilization for the 7 MHz channel bandwidth | T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R4-2500103 | On BS specification impact due to introduction of 7MHz channel bandwidth | Nokia |
| R4-2500558 | Discussion on BS RF core requirements for supporting 7 MHz NR FR1 channel bandwidth | ZTE Corporation, Sanechips |
| R4-2500559 | Draft CR to TS38.104 Introduction of 7 MHz NR FR1 channel bandwidth for NR bands n26 and n5 | ZTE Corporation, Sanechips |
| R4-2500560 | Draft CR to TS38.141-1 Introduction of 7 MHz NR FR1 channel bandwidth for NR bands n26 and n5 | ZTE Corporation, Sanechips |
| R4-2500561 | Draft CR to TS38.141-2 Introduction of 7 MHz NR FR1 channel bandwidth for NR bands n26 and n5 | ZTE Corporation, Sanechips |
| R4-2501061 | Discussion on BS RF requirements for 7MHz channel bandwidth | CATT |
| R4-2501363 | 7 MHz channel BW: BS RF impacts | Ericsson |
| R4-2502134 | BS RF impact for 7 MHz Channel Bandwidth for n26 and n5 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| R4-2500679 | Topic summary for [114][127] NR_FR1_7MHz_BW | Moderator(Ericsson) |
| R4-2502870 | WF on requirements for 7MHz channel bandwidth | Ericsson |
| R4-2502871 | LS on signalling for 7MHz channel bandwidth | T-Mobile USA |
| R4-2503017 | LS on Signalling for 7 MHz Channel Bandwidth | T-Mobile USA |
| TDoc | Title | Source |
|---|---|---|
| R4-2500638 | NTN and IoT-NTN HPUE co-existence study and calibration | Xiaomi |
| R4-2500742 | Discussion on co-existence of NTN HPUE | vivo |
| R4-2501346 | Discussion on NTN HPUE coexistence study | MediaTek (Hefei) Inc. |
| R4-2501347 | IoT-NTN HPUE RF requirements for Tx | Nokia |
| R4-2501400 | On Co-existence simulation assumptions for NR-NTN and NB-IoT-NTN HP UE | Ericsson |
| R4-2501401 | On Co-existence simulation results for NR-NTN and NB-IoT-NTN HP UE | Ericsson |
| R4-2501457 | Discussion on coexistence study for NR NTN HPUE | Huawei, HiSilicon |
| R4-2501731 | On coexistence study for NTN HPUE | Qualcomm Incorporated |
| R4-2501807 | On coexistence results and conclusion | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500090 | Candidate TN PA for NR-NTN HPUE in smartphones | Skyworks Solutions Inc. |
| R4-2500293 | Further considerations on the high-power UE Tx requirements | Apple |
| R4-2500294 | On restricted set of power back-off simulations for the satellite band UE Tx requirements | Apple |
| R4-2500648 | NR-NTN HPUE RF requirements | Xiaomi |
| R4-2500762 | NR NTN HPUE Tx Requirements and feasibility analysis | vivo |
| R4-2501008 | Discussion on UE Tx requirement for NTN support HPUE | CATT |
| R4-2501458 | Discussion on Tx requirements for NR NTN HPUE | Huawei, HiSilicon |
| R4-2501474 | Discussion on Tx requirements for NR-NTN HPUE | OPPO |
| R4-2501808 | On NR-NTN HPUE Tx requirements | Samsung |
| R4-2502010 | NR NTN high power UE Tx requirements | Qualcomm Inc. |
| R4-2502193 | On UE RF Tx requirements for NR-NTN HPUE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500763 | NR NTN HPUE Rx Requirements | vivo |
| R4-2501009 | Discussion on UE Rx requirement for NTN support HPUE | CATT |
| R4-2501283 | Discussion on NR-NTN HPUE RX RSD | MediaTek (Hefei) Inc. |
| R4-2501459 | Discussion on Rx requirements for NR NTN HPUE | Huawei, HiSilicon |
| R4-2501809 | On NR-NTN HPUE Rx requirements | Samsung |
| R4-2502009 | NR NTN high power UE Rx requirements | Qualcomm Inc. |
| R4-2502194 | On UE RF Rx requirements for NR-NTN HPUE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500108 | Candidate TN PA for NR-NTN HPUE in smartphones | Skyworks Solutions Inc. |
| R4-2500649 | IoT-NTN HPUE RF requirements | Xiaomi |
| R4-2500764 | Iot NTN HPUE Tx Requirements and feasibility analysis | vivo, SmarterMicro |
| R4-2501475 | Discussion on Tx requirements for IoT-NTN HPUE | OPPO |
| R4-2501496 | R19 on NTN SAR | OPPO |
| R4-2501701 | Discussion on IoT-NTN HPUE TX RF requirements | MediaTek (Hefei) Inc. |
| R4-2501810 | On IoT-NTN HPUE Tx requirements and handheld SAR | Samsung |
| R4-2502008 | IoT NTN high power UE Tx requirements | Qualcomm Inc. |
| R4-2502195 | On UE RF Tx requirements for IoT-NTN HPUE | Ericsson, Sony |
| TDoc | Title | Source |
|---|---|---|
| R4-2500416 | draftCR for RF requirements for introduction of 3MHz on NTN bands | Huawei, HiSilicon |
| R4-2500765 | Iot NTN HPUE Rx Requirements | vivo |
| R4-2501476 | Discussion on Rx requirements for IoT-NTN HPUE | OPPO |
| R4-2501811 | On IoT-NTN HPUE Rx requirements | Samsung |
| R4-2502007 | IoT NTN high power UE Rx requirements | Qualcomm Inc. |
| R4-2502196 | On UE RF Rx requirements for IoT-NTN HPUE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500297 | Further considerations on the system related aspects of the NTN 3MHz channel | Apple, Globalstar |
| R4-2500735 | Discussion on system parameters for less than 5MHz in FR1-NTN bands | vivo |
| R4-2501006 | Discussion on system parameter for NTN support spectrum less than 5 MHz | CATT |
| R4-2501812 | draft CR for TS 38.101-5 to introduce less than 5MHz-Chapter 5 | Samsung |
| R4-2501813 | On NTN less than 5MHz system parameters | Samsung |
| R4-2502197 | On system parameters for less than 5 MHz CBW for FR1-NTN | Ericsson |
| R4-2502372 | draft CR for TS 38.101-5 to introduce less than 5MHz-Chapter 5 | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500298 | On UE RF requirements for the 3MHz channel | Apple, Globalstar |
| R4-2500299 | Power back-off values for the 3MHz channel in band n254 | Apple, Globalstar |
| R4-2500300 | Power back-off values for the 3MHz channel in band n256 | Apple |
| R4-2500301 | Addition of the 3MHz channel to TS 38.101-5 (sub-clause 6.2) | Apple |
| R4-2500302 | Addition of the 3MHz channel to TR 38.863 | Apple, Thales |
| R4-2500303 | Addition of the 3MHz channel to TR 38.741 | Apple, Globalstar |
| R4-2500412 | Remaining system parameters issues for supporting 3MHz CBW in NTN bands | Huawei Technologies France |
| R4-2500413 | Remaining RF issues for supporting 3MHz CBW in NTN bands | Huawei, HiSilicon |
| R4-2500605 | DraftCR to 38.101-5 Introduction of less than 5MHz channel bandwidth for FR1-NTN | ZTE Corporation, Sanechips |
| R4-2500625 | Discussion on UE RF requirements for NTN less than 5MHz | Xiaomi |
| R4-2500626 | Draft big CR on UE RF requirements for NTN less than 5MHz | Xiaomi |
| R4-2500736 | Discussion on UE RF requirements for less than 5MHz in FR1-NTN bands | vivo |
| R4-2501005 | DraftCR for TS 38.101-5, Introduction on RF requirements for NTN UE supporting less than 5 MHz channel bandwidth | CATT |
| R4-2501007 | Discussion on UE RF requirements for NTN support spectrum less than 5 MHz | CATT |
| R4-2501308 | NTN n254 3 MHz A-MPR simulations | Nokia |
| R4-2502000 | UE RF requirements for NTN less than 5 MHz | Qualcomm Inc. |
| R4-2502198 | On UE RF requirements for less than 5 MHz CBW for FR1-NTN | Ericsson |
| R4-2502371 | DraftCR for TS 38.101-5, Introduction on RF requirements for NTN UE supporting less than 5 MHz channel bandwidth | CATT |
| R4-2502374 | DraftCR for TS 38.101-5, Introduction on RF requirements for NTN UE supporting less than 5 MHz channel bandwidth | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500073 | Big CR to TS 38.108 to introduce less than 5MHz for NTN | Nokia, ZTE Corporation, Sanechips, Ericsson, Samsung, China Telecom |
| R4-2500549 | DraftCR to TS38.108 Add EVM window length requirement for 3MHz | ZTE Corporation, Sanechips |
| R4-2500606 | DraftCR to 38.181 Introduction of less than 5MHz channel bandwidth for FR1-NTN | ZTE Corporation, Sanechips |
| R4-2501004 | DraftCR for TS 38.181, Introduction on OTA conformance requirements for SAN supporting less than 5 MHz channel bandwidth | CATT |
| R4-2501608 | Big CR to TS 38.108 to introduce less than 5MHz for NTN | Nokia, ZTE Corporation, Sanechips, Ericsson, Samsung, China Telecom |
| R4-2501622 | Big CR to TS 38.181 to introduce less than 5MHz for NTN | Nokia |
| R4-2502284 | DraftCR to 38.181 Introduction of less than 5MHz channel bandwidth for FR1-NTN | ZTE Corporation, Sanechips |
| R4-2502285 | DraftCR for TS 38.181, Introduction on OTA conformance requirements for SAN supporting less than 5 MHz channel bandwidth | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500241 | On less than 5MHz for NTN RRM | Apple |
| R4-2500633 | Discussion on RRM requirements for less than 5MHz NTN | Xiaomi |
| R4-2500634 | draftCR on NTN less than 5MHz (9.2C NR intra-frequency measurements for SAN) | Xiaomi |
| R4-2501014 | Further discussion on less than 5MHz for NTN RRM requirement | CATT |
| R4-2501015 | Draft CR to TS 38.133 on NR SAN Satellite switching with re-synchronization for less than 5MHz | CATT |
| R4-2501176 | Discussion on RRM requirements for less than 5M in NTN | ZTECorporation,Sanechips |
| R4-2501182 | (NR_IoT_NTN_req_test_enh-Core) SAN FR1-FR1 handover | ZTECorporation,Sanechips |
| R4-2501262 | Discussion on RRM requirements for less than 5MHz for NTN | Huawei, HiSilicon |
| R4-2501263 | draftCR on RLM requirments for less than 5MHz for NTN | Huawei, HiSilicon |
| R4-2501285 | Discussion on RRM requirements of NTN with channel BW less than 5MHz | Ericsson |
| R4-2501286 | (NR_IoT_NTN_req_test_enh-Core) CR for TS 38.133 on Link Recovery Procedures for less than 5MHz NTN | Ericsson |
| R4-2501460 | Discussion on RRM requirements of Rel-19 NR-NTN in less than 5MHz | Samsung |
| R4-2501461 | Draft CR on NR SAN FR1 conditional handover for NTN less than 5MHz | Samsung |
| R4-2501482 | Adaptation of NR NTN mobility requirements for less than 5 MHz operation | Nokia |
| R4-2501483 | DraftCR to 38.133 Inter frequency mesurement requirements in NTN for less than 5 MHz operation | Nokia |
| R4-2502615 | Draft big CR on RRM requirements for NTN less than 5MHz in Rel-19 | Xiaomi, Samsung |
| R4-2502616 | draftCR on NTN less than 5MHz (9.2C NR intra-frequency measurements for SAN) | Xiaomi |
| R4-2502617 | DraftCR to 38.133 Inter frequency mesurement requirements in NTN for less than 5 MHz operation | Nokia |
| R4-2502683 | Draft CR to TS 38.133 on NR SAN Satellite switching with re-synchronization for less than 5MHz | CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500051 | Discussion on NTN testing for NGSO | MediaTek inc. |
| R4-2500116 | Discussion on NTN testing for NGSO | QUALCOMM Europe Inc. - Spain |
| R4-2500168 | Calculation of satellite motion by 4-th order Runge-Kutta method in the ECEF frame | Anritsu Corporation |
| R4-2500411 | Discussion on NGSO channel model parameters | ROHDE & SCHWARZ |
| R4-2500477 | On updated granularity for propagation delay and Doppler shift | Keysight Technologies UK Ltd |
| R4-2501498 | TE-emulated channel model for NTN UE tests | Ericsson |
| R4-2501511 | Discussion on Discussion on NTN_testing_NGSO_channel_model | ZTE Corporation, Sanechips |
| R4-2501533 | Discussion on NTN testing for NGSO channel model | Huawei, HiSilicon |
| R4-2502030 | Discussion on NTN testing NGSO channel model | Samsung |
| R4-2502031 | Calibration results summary for NTN testing NGSO channel model | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500528 | Topic summary for [114][214] NR_IoT_NTN_req_test_enh | Moderator (Xiaomi) |
| R4-2500572 | Topic summary for [114][311] NR_IoT_NTN_less_than_5MHz_UERF | Moderator (Xiaomi) |
| R4-2500573 | Topic summary for [114][312] NR_IoT_NTN_less_than_5MHz_BSRF | Moderator (Nokia) |
| R4-2500586 | Topic summary for [114][325] NTN_testing_NGSO_channel_model | Moderator (Samsung) |
| R4-2500680 | Topic summary for [114][128] NR_IoT_NTN_HPUE_part1 | Moderator(Samsung) |
| R4-2500681 | Topic summary for [114][129] NR_IoT_NTN_HPUE_part2 | Moderator(Vivo) |
| R4-2502278 | Way Forward for [114][325] NTN_testing_NGSO_channel_model | Samsung |
| R4-2502282 | Way Forward for [114][311] NR_IoT_NTN_less_than_5MHz_UERF | Xiaomi |
| R4-2502314 | Way Forward for [114][325] NTN_testing_NGSO_channel_model | Samsung |
| R4-2502589 | WF on RRM requirements for NR_IoT_NTN_req_test_enh | Xiaomi |
| R4-2502954 | WF on HPUE requirements for NR-NTN | Samsung |
| R4-2502997 | Collected co-existence results | Samsung |
| R4-2503006 | WF on HPUE UE requirement for IoT-NTN | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500210 | Ku Band: Narrow Band Services with 15 kHz Sub-Carrier Spacing | Intelsat |
| R4-2500223 | Minimization of number of Ku bands | Eutelsat Group |
| R4-2500434 | Updated work plan for NTN Ku Band | Intelsat |
| R4-2501354 | NTN Ku-band - WI updates impact | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500435 | Ku Band Co-existence Simulation Assumptions (Draft 1) | Intelsat |
| R4-2500607 | Discussion on coexistence study based on ITU regulations for NTN Ku band | ZTE Corporation, Sanechips |
| R4-2500637 | Discussion the assumptions and parameters for NR NTN Ku Band coexistence study | Xiaomi |
| R4-2500990 | Further discussion on coexistence evaluations for Ku-band for NR NTN | CATT |
| R4-2501398 | On Co-existence simulation assumptions for NR NTN Ku band | Ericsson |
| R4-2501399 | On Co-existence simulation results for NR NTN Ku band | Ericsson |
| R4-2501700 | Discussion on VSAT UE parameters for Ku-band co-existence study | SKY Perfect JSAT Corporation |
| R4-2501814 | On Ku-band coexistence studies | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500211 | Ku Band: Band Numbering, ARFCN and GSCN Calculations | Intelsat |
| R4-2500608 | Discussion on system parameters for NTN Ku band | ZTE Corporation, Sanechips |
| R4-2500642 | System parameters for NTN Ku band | Xiaomi |
| R4-2500988 | Further discussion on system parameters for Ku-band for NR NTN | CATT |
| R4-2501306 | Discussion on the system parameters for NR NTN Ku band | CHTTL |
| R4-2501355 | NTN Ku-band - System parameters | Ericsson |
| R4-2501822 | NR NTN system parameters for Ku band | Nokia |
| R4-2502211 | Discussion on Ku-band FR2-NTN configuration | THALES |
| TDoc | Title | Source |
|---|---|---|
| R4-2500609 | Discussion on UE RF requirements for NTN Ku band | ZTE Corporation, Sanechips |
| R4-2500643 | VSAT Type for Ku band | Xiaomi |
| R4-2501338 | Discussion on the support VSAT types and EIRP, TRP, EIS requirement for the Rel.19 NTN Ku band | CHTTL |
| R4-2501356 | NTN Ku-band - UE RF requirements | Ericsson |
| R4-2501358 | Draft CR to 38101-5 - Needed updates to support NTN VSAT in FR1-NTN | Ericsson |
| R4-2501456 | Discussion on VSAT requirements for NR NTN Ku band | Huawei, HiSilicon |
| R4-2501691 | Discussion on UE RF requirements for NR NTN Ku band | SKY Perfect JSAT Corporation |
| R4-2501815 | On Ku-band UE RF requirements | Samsung |
| R4-2502173 | Discussion on Ku-band VSAT output power and different antenna sizes | LG Electronics Finland |
| R4-2502232 | Addition of structure for support for mobile VSAT served by NGSO | Eutelsat Group |
| TDoc | Title | Source |
|---|---|---|
| R4-2500610 | Discussion on SAN RF requirements for NTN Ku band | ZTE Corporation, Sanechips |
| R4-2500989 | Further discussion on SAN RF core requirements for Ku-band for NR NTN | CATT |
| R4-2501328 | Discussion on the SAN RF requirement for the NTN Ku band | CHTTL |
| R4-2501357 | NTN Ku-band - SAN requirements | Ericsson |
| R4-2501823 | Discussion on NR NTN SAN requirement for Ku band | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500135 | RRM updates required to support the introduction of Ku Bands for NR-NTN | Eutelsat Group |
| R4-2500387 | Discussion on RRM requirements for Ku bands for NR NTN | MediaTek inc. |
| R4-2500575 | Topic summary for [114][314] NR_NTN_Ku_Band_UE_SAN_RF | Moderator (CHTTL ) |
| R4-2500883 | Discussion on RRM requirements for Ku-band NTN | LG Electronics Inc. |
| R4-2501175 | Discussion on Ku bands for NR NTN | ZTECorporation,Sanechips |
| R4-2501271 | Initial discussion on RRM requirements for NTN in Ku band | Huawei, HiSilicon |
| R4-2501621 | Mobile VSAT gradual timing adjustment | Ericsson |
| R4-2502205 | UL Timing modifications to enable mobile VSAT served by NGSO | Eutelsat Group |
| R4-2502207 | CR to 38.133 to modify uplink timing requirements to enable mobile VSAT served by NGSO by NGSO | Eutelsat Group |
| R4-2502227 | (NR_NTN_Ku_bands-Core) RRM requirements for VSAT UE in Ku band | Qualcomm Incorporated |
| R4-2502288 | Way Forward for [114][314] NR_NTN_Ku_Band_UE_SAN_RF | CHTTL |
| TDoc | Title | Source |
|---|---|---|
| R4-2500529 | Topic summary for [114][215] NR_NTN_Ku_bands | Moderator (Apple) |
| R4-2500574 | Topic summary for [114][313] NR_NTN_Ku_Band_General | Moderator (Eutelsat) |
| R4-2502289 | Ad-hoc meeting minutes for [114][313] NR_NTN_Ku_Band_General | Eutelsat |
| R4-2502290 | Way Forward for [114][313] NR_NTN_Ku_Band_General | Eutelsat |
| R4-2502315 | Ku band simulation assumption agreements | Eutelsatn |
| R4-2502590 | WF on RRM requirements for NR_NTN_Ku_bands | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500860 | Discussion on UE RF requirements for ATG with inter-band CA | CMCC |
| R4-2501451 | Discussion on Rel-19 ATG UE RF with DL inter-band CA_n3-n39 | Huawei, HiSilicon |
| R4-2501732 | Discussion on Rel-19 ATG UE RF requirements | Qualcomm Incorporated |
| R4-2501871 | Discussion on RF requirement for Inter-band CA for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
| R4-2501938 | Discussion on RF requirement of ATG UE inter-band CA | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500859 | Discussion on UE RF requirements for ATG with UL-MIMO | CMCC |
| R4-2501452 | Discussion on Rel-19 ATG UE RF with UL MIMO | Huawei, HiSilicon |
| R4-2501872 | Discussion on RF requirement for UL-MIMO for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
| R4-2501902 | ATG UE RF requirements for UL-MIMO | LG Electronics |
| R4-2501939 | Discussion on RF requirement of ATG UE UL MIMO | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2501873 | Discussion on RF requirement for DL-MIMO for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
| R4-2501940 | Discussion on RF requirement of ATG UE DL MIMO | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500783 | BS RF requirements for ATG enhancements | Huawei, HiSilicon |
| R4-2500784 | Draft CR for TS 38.104 to add ATG enhancement BS RF requirements | Huawei, HiSilicon |
| R4-2500857 | Draft CR for TS 38.104 on ATG BS RF clarification | CMCC |
| R4-2500858 | Discussion on BS RF requirements for ATG with DL MIMO | CMCC |
| R4-2500937 | Discussion on left open issues for ATG BS CA | ZTE Corporation, Sanechips |
| R4-2500938 | draft CR to TS 38.104: the introduction of Rel-19 ATG BS supporting CA | ZTE Corporation, Sanechips |
| R4-2500995 | Discussion on BS RF requirements for enhancements for Air-to-ground network for NR | CATT |
| R4-2500996 | Draft CR for 38.104, Introduction of R19 ATG enhancement BS RF requirements | CATT |
| R4-2500997 | Draft CR for 38.141-1, Introduction of R19 ATG enhancement BS RF requirements | CATT |
| R4-2500998 | Draft CR for 38.141-2, Introduction of R19 ATG enhancement BS RF requirements | CATT |
| R4-2501941 | Draft CR for 38.104 TAE and multiband requirement for ATG DL MIMO BS | Ericsson |
| R4-2501942 | Discussion on TAE requirement of ATG BS DL MIMO | Ericsson |
| R4-2502280 | draft CR to TS 38.104: the introduction of Rel-19 ATG BS supporting CA | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500837 | Discussion on RRM requirements for ATG CA operation | LG Electronics Inc. |
| R4-2500843 | Discussion on RRM requirements for R19 ATG | CMCC |
| R4-2500906 | Discussion on RRM aspects of R19 ATG | ZTE Corporation, Sanechips |
| R4-2501016 | Discussion on enhancements for Rel-19 ATG RRM requirements | CATT |
| R4-2501273 | Discussions on RRM requirements for Rel-19 ATG | Huawei, HiSilicon |
| R4-2501703 | Discussion on Rel-19 ATG CA RRM Core Enhancement Related Remaining Issues | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500530 | Topic summary for [114][216] NR_ATG_enh | Moderator (CMCC) |
| R4-2500566 | Topic summary for [114][305] NR_ATG_enh | Moderator (ZTE) |
| R4-2500682 | Topic summary for [114][130] NR_ATG_enh | Moderator(CMCC) |
| R4-2502591 | WF on RRM requirements for NR_ATG_enh | CMCC |
| R4-2502614 | Coffee break discussion minutes on NR_ATG_enh | CMCC |
| R4-2502926 | WF on UE RF requirements for ATG | CMCC |
| R4-2502952 | WF on UE RF requirements for ATG | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R4-2500881 | General aspects related to BS RF evolution WI | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500199 | Draft CR to TS 38.106 for introduction of expected EIRP mask core requirement for NCR | Nokia |
| R4-2500510 | Inclusion of Plane Wave Synthesizer (PWS) method for Expected EIRP test procedures | ROHDE & SCHWARZ |
| R4-2500548 | Plane Wave Synthesizer (PWS) method inclusion for Expected EIRP test procedures | ROHDE & SCHWARZ |
| R4-2501165 | TP to TR 38.908 clause 6.2 The calculation for EEIRP mask | Nokia |
| R4-2501166 | TP to TR 38.908 clause 6.3 Test beams | Nokia |
| R4-2502316 | TP to TR 38.908 clause 6.2 The calculation for EEIRP mask | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2501323 | On OTA test enhancements | Nokia |
| R4-2501875 | Further discussion on OTA test enhancement | ZTE Corporation, Sanechips |
| R4-2502160 | Simulation of BS-to-BS isolation for edge-to-edge co-location isolation at 7 GHz | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500203 | Conformance testing of Expected EIRP mask requirement | Nokia |
| R4-2501190 | Draft CR to TS 38.141-2 with updates to Annex N for Expected EIRP calculation | Nokia |
| R4-2501191 | Draft CR to TS 38.141-2 with updates to OTA spatial emission requirement test procedure | Nokia |
| R4-2501648 | TP for TR 38.908: Conformance test aspects for EEIRP | Ericsson |
| R4-2501649 | TP for TS 38.141-2: Addition of spatial emission requirement to protect FSS UL within band n104 | Ericsson |
| R4-2501850 | Further discussion on Expected EIRP test | Huawei, HiSilicon |
| R4-2501851 | Expected EIRP conformance declarations | Huawei, HiSilicon |
| R4-2501852 | TP to TR 38.908 – section 6.5 | Huawei, HiSilicon |
| R4-2501853 | TP to TR 38.908 – section 6.6 | Huawei, HiSilicon |
| R4-2501874 | TR 38.908 v1.3.0 Protection of fixed satellite service (FSS) UL within 6425 to 7125 MHz | ZTE Corporation, Sanechips |
| R4-2501876 | Discussion on conformance testing for U6GHz BS EEIRP mask | ZTE Corporation, Sanechips |
| R4-2501877 | Draft CR for introduction of U6GHz EIRP conformance testing | ZTE Corporation, Sanechips |
| R4-2501927 | Big draft CR for introduction of U6GHz EIRP conformance testing | ZTE Corporation, Sanechips, Huawei |
| R4-2502317 | Draft CR to TS 38.141-2 with updates to Annex N for Expected EIRP calculation | Nokia |
| R4-2502318 | TP for TR 38.908: Conformance test aspects for EEIRP | Ericsson |
| R4-2502319 | TP for TS 38.141-2: Addition of spatial emission requirement to protect FSS UL within band n104 | Ericsson |
| R4-2502320 | TP to TR 38.908 – section 6.6 | Huawei, HiSilicon |
| R4-2502321 | Draft CR for introduction of U6GHz EIRP conformance testing | ZTE Corporation, Sanechips |
| R4-2502379 | TP for TS 38.141-2: Addition of spatial emission requirement to protect FSS UL within band n104 | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500202 | On BS OTA test scope reduction | Nokia |
| R4-2501033 | Discussion on BS RF OTA test scope | CATT |
| R4-2501854 | OTA test case reduction | Huawei, HiSilicon |
| R4-2501878 | Discussion on the OTA testing scope reduction | ZTE Corporation, Sanechips |
| R4-2502135 | Analysis of BS-to-BS coupling values | Huawei, HiSilicon |
| R4-2502159 | OTA test scope reduction | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500074 | Simplification of BS TRP test methods | Nokia |
| R4-2501647 | TS 38.141-2 Annex I: Discussion on improvement of TRP measurement methods | Ericsson |
| R4-2501879 | Discussion on the applicability improvement of TRP measurement | ZTE Corporation, Sanechips |
| TDoc | Title | Source |
|---|---|---|
| R4-2500563 | Topic summary for [114][302] NR_BS_RF_Part1_E_EIRP | Moderator (ZTE) |
| R4-2500564 | Topic summary for [114][303] NR_BS_RF_Part2_CLTA | Moderator (Huawei) |
| R4-2500565 | Topic summary for [114][304] NR_BS_RF_Part3_OTA_TRP | Moderator (ZTE) |
| R4-2502279 | Way Forward for [114][303] NR_BS_RF_Part2_CLTA | Huawei |
| R4-2502304 | Way Forward for [114][304] NR_BS_RF_Part3_OTA_TRP | ZTE |
| R4-2502308 | Ad-hoc meeting minutes for [114][302] NR_BS_RF_Part1_E_EIRP | ZTE |
| R4-2502309 | Way Forward for [114][302] NR_BS_RF_Part1_E_EIRP | ZTE |
| R4-2502375 | Way Forward for [114][304] NR_BS_RF_Part3_OTA_TRP | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R4-2500748 | CR to TR 38.870 on general part | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500042 | on OTA XR tests | Huawei, HiSilicon |
| R4-2500295 | CR to TR 38.870 for an alternate TRP test procedure for XR devices | Apple |
| R4-2500296 | CR to TS38.161 for an alternate TRS test procedure for XR devices | Apple |
| R4-2500749 | CR to 38.870 on XR OTA test method | vivo |
| R4-2501375 | Discussion on OTA Test for XR Devices | Meta |
| R4-2501613 | Further discussion on XR test method | Ericsson-LG Co., LTD |
| R4-2501973 | Discusion on XR OTA | CAICT |
| R4-2502208 | CR to TR 38.870 for an alternate TRP test procedure for XR devices | Apple |
| R4-2502209 | CR to TS38.161 for an alternate TRS test procedure for XR devices | Apple |
| R4-2502299 | CR to TR 38.870 for an alternate TRP test procedure for XR devices | Apple, Rohde & Schwarz, Keysight Technologies |
| R4-2502300 | CR to 38.870 on XR OTA test method | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500041 | on OTA NTN tests | Huawei, HiSilicon |
| R4-2500107 | CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
| R4-2500323 | On NTN TRP TRS test methodology | Apple |
| R4-2500400 | Discussion on FR1 NTN devices OTA | Qualcomm Incorporated |
| R4-2500505 | On OTA performance metric and polarization for handheld NTN UE | Samsung |
| R4-2500627 | Discussion on OTA test for FR1 NTN devices | Xiaomi |
| R4-2500750 | draft CR to 38.870 on NTN OTA test method | vivo |
| R4-2500751 | Discussions on NTN OTA test method | vivo |
| R4-2501801 | CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
| R4-2501805 | CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
| R4-2501806 | CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
| R4-2502177 | On Circular Polarization for FR1 NTN OTA Conformance Testing | Keysight Technologies UK Ltd, Samsung, Nokia, Verizon Wireless, AT&T, Mediatek, ZTE, Ericsson, ETS-Lindgren, Rohde&Schwarz, OPPO, Xiaomi, CAICT |
| R4-2502301 | draft CR to 38.870 on NTN OTA test method | vivo |
| R4-2502367 | CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
| TDoc | Title | Source |
|---|---|---|
| R4-2500043 | on MIMO tests under dynamic channels | Huawei, HiSilicon |
| R4-2500481 | On FR1 MIMO OTA Dynamic Channel Model | Apple |
| R4-2500506 | On performance metric for FR1 dynamic MIMO | Samsung |
| R4-2501746 | TP to 38.762 on terms and abbreviations | CAICT, SAICT |
| R4-2501747 | On dynamic MIMO OTA channel models in 3GPP and CTIA | CAICT, CMCC |
| R4-2501749 | TR 38.762 V0.2.0 on MIMO OTA dynamic test methodology for FR1 UEs | CAICT |
| R4-2501828 | On dynamic MIMO OTA channel models PDP target values | CMCC |
| R4-2502175 | On Channel Models in CTIA and 3GPP for Dynamic FR1 MIMO OTA | Keysight Technologies UK Ltd, Spirent Communications, CAICT, Huawei, AT&T, Verizon Wireless |
| R4-2502176 | TP for TR 38.762: DynMIMO CM Validation Details and Corrections | Keysight Technologies UK Ltd, Spirent Communications |
| TDoc | Title | Source |
|---|---|---|
| R4-2500044 | On TRP and TRS tests | Huawei, HiSilicon |
| R4-2500480 | Views on Rel19 TRP TRS Performance Part | Apple |
| R4-2500507 | Some initial test for RC harmonization at FR1 low band | Samsung |
| R4-2500752 | Discussions on Rel-19 TRP TRS requirements work | vivo |
| R4-2502238 | Proposals for Rel-19 TRP TRS requirements topic | Telecom Italia S.p.A., Vodafone, Deutsche Telekom, Orange |
| TDoc | Title | Source |
|---|---|---|
| R4-2501748 | Framework and time plan for Rel-19 MIMO OTA performance requirements development (Feb 2025) | CAICT |
| R4-2502295 | Framework and time plan for Rel-19 MIMO OTA performance requirements development (Feb 2025) | CAICT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500588 | Topic summary for [114][327] TRP_TRS_Ph3 | Moderator (vivo) |
| R4-2500589 | Topic summary for [114][328] MIMO_OTA_Ph3 | Moderator (CAICT) |
| R4-2502296 | Way Forward for [114][328] MIMO_OTA_Ph3 | CAICT |
| R4-2502302 | Ad-hoc meeting minutes for [114][327] TRP_TRS_Ph3 | vivo |
| R4-2502303 | Ad-hoc meeting minutes for [114][328] MIMO_OTA_Ph3 | CAICT |
| R4-2502370 | Way Forward for [114][327] TRP_TRS_Ph3 | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2501728 | TR 38.771 v0.2.0 | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500399 | FR2 OTA test method on STxMP | Qualcomm Incorporated |
| R4-2500508 | TP to TR 38.771 on STxMP test procedure | Samsung |
| R4-2500741 | Discussion on the remaining issue of FR2 OTA | vivo |
| R4-2501729 | TP to TR 38.771 on general part | Qualcomm Incorporated |
| R4-2501730 | TP to TR 38.771 on test methodology for STxMP | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500590 | Topic summary for [114][329] NR_FR2_OTA | Moderator (Qualcomm) |
| R4-2502294 | Way Forward for [114][329] NR_FR2_OTA | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R4-2500818 | Discussion on General Aspects of SCM SI | Nokia |
| R4-2501745 | Measurement results for MIMO channels in band n78 | BT plc, Ericsson |
| R4-2501785 | Discussion on Rel-19 NR SCM general aspects | Ericsson |
| R4-2501786 | TP for TR38.753 on content of chapter 7 | Ericsson |
| R4-2501990 | On Spatial Channel Modeling study and TR scope | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500217 | Performance comparison of high and low-resolution codebook under different CDL models and AAV configurations | Orange Romania |
| R4-2500262 | On Spatial Channel Modeling | Apple |
| R4-2500263 | Simulation results Spatial Channel Modeling study | Apple |
| R4-2500264 | Draft TP to TR on SCM study - 5.1 CDL approach | Apple, Qualcomm |
| R4-2500331 | TP to TR 38.753: Scope and reference | China Telecom |
| R4-2500335 | Discussion on spatial channel modelling | MediaTek inc. |
| R4-2500336 | Simulation results of spatial channel modelling | MediaTek inc. |
| R4-2500337 | TP to TR38.753: TDL approaches and related Annex | MediaTek inc. |
| R4-2500427 | Discussion on Spatial Channel Model for Demodulation Performance Requirements | Nokia |
| R4-2500428 | Simulation Results and CDL Implementation for Spatial Channel Model for Demodulation Performance Requirements | Nokia |
| R4-2500993 | Further discussion on spatial channel modelling methodology | CATT |
| R4-2501428 | Discussion on spatial channel model for demodulation performance requirements | Samsung |
| R4-2501429 | Initial simualtion results on spatial channel model | Samsung |
| R4-2501430 | TP for 38.753 on chapter 4 | Samsung |
| R4-2501503 | Discussion on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
| R4-2501504 | Simulation results on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
| R4-2501505 | TP for 38.753 introduction of spatial channel models for SU-MIMO PMI cases | ZTE Corporation, Sanechips |
| R4-2501517 | Discussions on spatial channel model for demodulation requirements | Huawei, HiSilicon |
| R4-2501518 | Simulation results for spatial channel model | Huawei, HiSilicon |
| R4-2501519 | Draft TP introduction of comparision of spatial channel models for SU-MIMO PDSCH cases | Huawei, HiSilicon |
| R4-2501738 | Discussions on spatial channel model for demodulation requirements | Huawei, HiSilicon |
| R4-2501743 | Results collection table for NR SCM | BT plc |
| R4-2501744 | Simulation Results for SCM Comparison and Alignment | BT plc |
| R4-2501787 | Discussion on Rel-19 NR SCM methodology for demodulation | Ericsson |
| R4-2501788 | Simulation results for Rel-19 NR SCM for demodulation | Ericsson |
| R4-2501934 | Study of SCM for demodulation performance requirements | Qualcomm Incorporated |
| R4-2501954 | Performance comparison of high and low-resolution codebook under different CDL models and AAV configurations | Orange, Fraunhofer |
| R4-2501998 | Simulation Results for SCM Demod | Qualcomm Incorporated |
| R4-2502377 | Results collection table for NR SCM | BT plc |
| TDoc | Title | Source |
|---|---|---|
| R4-2500583 | Topic summary for [114][322] NR_SCM | Moderator (Nokia) |
| R4-2502276 | Ad-hoc meeting minutes for [114][322] NR_SCM | Nokia |
| R4-2502277 | Way Forward for [114][322] NR_SCM | Nokia |
| R4-2502378 | Way Forward for [114][322] NR_SCM | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500246 | On FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Apple |
| R4-2500592 | Discussions on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | NTT DOCOMO, INC. |
| R4-2500882 | Discussion on RRM requirements for FR2-1 L3 measurement delay reduction | LG Electronics Inc. |
| R4-2500905 | Discussion on Rx beam factor optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
| R4-2501044 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | CATT |
| R4-2501089 | Discussion on L3 measurement delay reduction by optimizing Rx beam sweeping factor | CMCC |
| R4-2501136 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | OPPO |
| R4-2501147 | Discussion on delay reduction by optimizing Rx beam sweeping factors | Intel Corporation |
| R4-2501149 | draftCR on reduced BSF for handover and re-establishment | Intel Corporation |
| R4-2501218 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Huawei, HiSilicon |
| R4-2501289 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Ericsson |
| R4-2501331 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | China Telecom |
| R4-2501406 | On L3 faster beam sweeping requirements | Nokia |
| R4-2501414 | Further discussion on FR 2-1 L3 measurement delay by optimizing Rx beam sweeping factor | vivo |
| R4-2501678 | Discussion on L3 measurement enhancement by optimizing Rx BSF | Samsung |
| R4-2502149 | Draft CR Handover and RRC re-establishment requirements with FBS | Nokia |
| R4-2502164 | FR2-1 L3 measurement delay by optimizing RX beam sweeping factor | Qualcomm Incorporated |
| R4-2502180 | Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500236 | On FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Apple |
| R4-2500469 | FR2-1 SSB based L3 measurement delay reduction with CSSF optimization | Nokia, Nokia Shanghai Bell |
| R4-2500904 | Discussion on CSSF optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
| R4-2501045 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CADC | CATT |
| R4-2501090 | Discussion on L3 measurement delay reduction by optimizing CSSF outside gap in CA/DC | CMCC |
| R4-2501125 | On optimizing CSSF for FR2-1 L3 measurement delay | OPPO |
| R4-2501148 | Discussion on delay reduction by optimizing CSSF outside gap | Intel Corporation |
| R4-2501272 | Discussion on FR2-1 L3 measurement delay by optimising CSSF outside gap in CA/DC | Huawei, HiSilicon |
| R4-2501290 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Ericsson |
| R4-2501332 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | China Telecom |
| R4-2501413 | Further discussion on FR 2-1 L3 measurement delay by optimizaing CSSF outside gap in CADC | vivo |
| R4-2501677 | Discussion on L3 measurement enhancement by optimizing CSSF | Samsung |
| R4-2502163 | Enhancement on FR2 CSSF | Qualcomm Incorporated |
| R4-2502181 | Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing CSSF | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500455 | draft CR for fast SCell activation for UE supporting Rel-18 EMR | Apple, CATT |
| R4-2501046 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | CATT |
| R4-2501047 | CR on Fast SCell activation for UE supporting Rel-18 eEMR | CATT, Apple, Nokia, Ericsson, Huawei, HiSilicon, Qualcomm, Samsung, ZTE Corporation, Sanechips, MediaTek, CMCC, China Telecom, LG Electronics, OPPO, vivo |
| R4-2501091 | Discussion on fast SCell activation for UE supporting Rel-18 EMR | CMCC |
| R4-2501111 | draft CR to TS 38.133 for fast scell activation for UE supporting Rel-18 EMR | Ericsson |
| R4-2501112 | Discussion for fast scell activaiton for UE supporting Rel-18 EMR | Ericsson |
| R4-2501219 | Discussion on maintenance for fast SCell activation based on EMR | Huawei, HiSilicon |
| R4-2501679 | Discussion on T_uncertainty for eEMR based fast SCell activation | Samsung |
| R4-2501981 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | Nokia |
| R4-2502675 | draft CR for fast SCell activation for UE supporting Rel-18 EMR | Apple, CATT |
| R4-2502685 | draft CR for fast SCell activation for UE supporting Rel-18 EMR | Apple, CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500531 | Topic summary for [114][217] NR_RRM_Ph5_Part1 | Moderator (Apple) |
| R4-2500532 | Topic summary for [114][218] NR_RRM_Ph5_Part2 | Moderator (CATT) |
| R4-2502576 | Ad-hoc minutes for NR_RRM_Ph5 WI | Apple |
| R4-2502592 | WF on RRM requirements for NR_RRM_Ph5_Part1 | Apple |
| R4-2502593 | WF on RRM requirements for NR_RRM_Ph5_Part2 | CATT |
| R4-2502662 | LS on CSSF optimization for NR RRM Phase 5 | Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2501352 | On general issues for Rel-19 MMSE-IRC receiver under interference | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500048 | Discussion on UE demodulation requirements with 8Rx MMSE-IRC receiver | MediaTek inc. |
| R4-2500049 | Simulations for UE demodulation requirements with 8Rx MMSE-IRC receiver | MediaTek inc. |
| R4-2500265 | On UE demodulation performance requirements with 8RX | Apple |
| R4-2500266 | Simulation results for ICI and MU-MIMO with 8RX | Apple |
| R4-2500267 | Summary of simulation results for ICI and MU-MIMO with 8RX | Apple |
| R4-2500328 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | China Telecom |
| R4-2500844 | Discussion on interference suppressing performance for 8Rx UE | CMCC |
| R4-2500845 | Simulation results for 8Rx UE interference suppressing | CMCC |
| R4-2501319 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | Nokia |
| R4-2501320 | Simulations for UE demodulation performance requirements for 8Rx with MMSE-IRC | Nokia |
| R4-2501431 | Discussion on UE demodulation and CSI performance requirements for 8Rx with MMSE-IRC | Samsung |
| R4-2501506 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
| R4-2501507 | Simulation results on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
| R4-2501513 | Discussions on 8Rx MMSE-IRC requirements | Huawei, HiSilicon |
| R4-2501514 | Simulation results for 8Rx MMSE-IRC requirements | Huawei, HiSilicon |
| R4-2501733 | Views on 8Rx UE demodulation and CSI requirements with inter-cell and intra-cell inter-user interference | Qualcomm India Pvt Ltd |
| R4-2501905 | On MMSE-IRC receiver for interference mitigation with 8Rx | Ericsson |
| R4-2501906 | Simulation results for MMSE-IRC receiver for 8Rx reception | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500329 | Simulation results on BS demodulation performance requirements for MMSE-IRC | China Telecom |
| R4-2500330 | Discussion on BS demodulation performance requirements for MMSE-IRC | China Telecom |
| R4-2500334 | BS demodulation performance requirement using MMSE-IRC | Tejas Network Limited |
| R4-2500846 | Discussion on BS demodulation requirements for interference suppressing with MMSE-IRC receiver | CMCC |
| R4-2500847 | Simulation results for BS interference suppressing with MMSE-IRC | CMCC |
| R4-2500992 | Further discussion on BS demodulation performance for MMSE-IRC | CATT |
| R4-2501350 | Discussion on Rel-19 MMSE-IRC BS demodulation requirements | Ericsson |
| R4-2501351 | Simulation results for Rel-19 MMSE-IRC BS demodulation requirements | Ericsson |
| R4-2501510 | Discussion on BS demodulation performance requirements MMSE-IRC | ZTE Corporation, Sanechips |
| R4-2501515 | Discussions on BS MMSE-IRC requirements with inter-cell interference | Huawei, HiSilicon |
| R4-2501516 | Simulation results on BS MMSE-IRC requirements with inter-cell interference | Huawei, HiSilicon |
| R4-2501698 | Views on BS demodulation requirements for MMSE-IRC | Qualcomm Germany |
| R4-2501842 | NR Demodulation Performance Phase 5: BS demodulation performance requirements for MMSE-IRC | Nokia |
| R4-2501843 | Simulation Results – NR BS Demodulation Performance Requirements for MMSE-IRC | Nokia |
| R4-2501900 | Discussion on BS demodulation for NR MMSE-IRC | NTT DOCOMO, INC. |
| R4-2501901 | Simulation results for NR MMSE-IRC BS demodulation | NTT DOCOMO, INC. |
| R4-2502028 | Simulation results summary for BS requirement with MMSE-IRC receiver | Samsung |
| R4-2502029 | View and simulation results for BS demodulation requirement with MMSE-IRC receiver | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500584 | Topic summary for [114][323] NR_demod_Ph5_Part1_General_BS | Moderator (China Telecom) |
| R4-2500585 | Topic summary for [114][324] NR_demod_Ph5_Part2_UE | Moderator (Nokia) |
| R4-2502272 | Way Forward for [114][323] NR_demod_Ph5_Part1_General_BS | China Telecom |
| R4-2502273 | Ad-hoc meeting minutes for [114][323] NR_demod_Ph5_Part1_General_BS | China Telecom |
| R4-2502274 | Ad-hoc meeting minutes for [114][324] NR_demod_Ph5_Part2_UE | Nokia |
| R4-2502275 | Way Forward for [114][324] NR_demod_Ph5_Part2_UE | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500045 | Discussion on general aspects for AI/ML air | Korea Testing Laboratory |
| R4-2500224 | Discussion on General Aspects on AI/ML for NR Air Interface | Apple |
| R4-2500511 | Discussion on general aspects of AI/ML for NR air interface | CAICT |
| R4-2500616 | Discussion on general aspect for AI | Xiaomi |
| R4-2500821 | Discussion on general aspects for AIML | vivo |
| R4-2501034 | Discussion on general aspects for AIML for NR air | CATT |
| R4-2501094 | Discussion on general aspects | CMCC |
| R4-2501172 | Discussion on the AI/ML general aspects | ZTECorporation,Sanechips |
| R4-2501526 | Discussion on general aspects on AIML for NR air interface | Huawei, HiSilicon |
| R4-2501610 | On LCM requirements for AI/ML | Ericsson |
| R4-2501956 | General aspects of AI/ML for NR Air interface | Nokia |
| R4-2502167 | Post Deployment Testing of AI-ML | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500228 | Discussion on CSI Prediction: CSI reporting requirement framework for CSI prediction | Apple |
| R4-2500270 | CSI reporting requirement framework for CSI prediction | OPPO |
| R4-2500338 | Discussion on CSI reporting requirement framework for CSI prediction | MediaTek inc. |
| R4-2500512 | Discussion on RRM core requirement for CSI prediction | CAICT |
| R4-2500822 | Discussion on CSI reporting requirement framework for CSI prediction | vivo |
| R4-2501035 | Discussion on CSI reporting requirement framework for CSI prediction | CATT |
| R4-2501093 | Discussion on CSI prediction | CMCC |
| R4-2501499 | Discussion on CSI prediction | Ericsson |
| R4-2501508 | Discussion on testability and interoperability issues for CSI prediction | ZTE Corporation, Sanechips |
| R4-2501527 | Discussion on CSI reporting requirement framework for AIML CSI predictio | Huawei, HiSilicon |
| R4-2502032 | View on CSI reporting requirements framework for CSI prediction | Samsung |
| R4-2502070 | CSI reporting requirement framework for CSI prediction | Nokia |
| R4-2502166 | CSI Prediction: Core Requirements and Testability Issues | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500085 | Views on outstanding Testability and Interoperability Issues for Beam Management | VIAVI Solutions |
| R4-2500225 | Discussion on Beam Management: RRM Core Requirements | Apple |
| R4-2500274 | RRM core requirement for beam management | OPPO |
| R4-2500513 | Discussion on RRM core requirements for beam management | CAICT |
| R4-2500593 | Discussions on RRM core requirement for beam management | NTT DOCOMO, INC. |
| R4-2500612 | Discussion on RRM requirement for beam management | Jio |
| R4-2500618 | Discussion on core part requirement for AI beam management | Xiaomi |
| R4-2500823 | Discussion on RRM core requirements for beam management | vivo |
| R4-2500888 | Discussion on RRM core requirements of AI/ML BM use case | MediaTek Inc. |
| R4-2501036 | Discussion on RRM core requirements for BM | CATT |
| R4-2501092 | Discussion on RRM requirements for beam management | CMCC |
| R4-2501170 | Discussion on the RRM requirements of AI/ML Beam management | ZTECorporation,Sanechips |
| R4-2501284 | Discussion on RRM core requirements for beam management | Ericsson |
| R4-2501528 | Discussion on RRM core requirement for AIML Beam management | Huawei, HiSilicon |
| R4-2501692 | RRM core requirement for AI/ML based beam management | Tejas Network Limited |
| R4-2501726 | Discussion on test setup for AI/ML based beam management | Rohde & Schwarz |
| R4-2501957 | RRM core requirements for AI/ML Based Beam Management | Nokia |
| R4-2501964 | Further discussion on beam management core requirements | Samsung |
| R4-2502165 | RRM Core Requirements for AI/ML Beam Management | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500229 | Discussion on RRM Core Requirements for positioning accuracy enhancement | Apple |
| R4-2500272 | RRM core requirement for Positioning accuracy enhancement | OPPO |
| R4-2500514 | Discussion on RRM core requirements for positioning | CAICT |
| R4-2500824 | Discussion on RRM core requirements for positioning accuracy enhancement | vivo |
| R4-2501037 | Discussion on RRM core requirements for positioning | CATT |
| R4-2501095 | Discussion on RRM requirements for positioning | CMCC |
| R4-2501171 | Discussion on the RRM requirements of AI/ML positioning | ZTECorporation,Sanechips |
| R4-2501529 | Discussion on RRM core requirement for AIML Positioning | Huawei, HiSilicon |
| R4-2501758 | On requirements for AI/ML based positioning | Ericsson |
| R4-2502071 | RRM core requirements for AI/ML positioning accuracy enhancement | Nokia |
| R4-2502168 | RRM Core Requirements for Positioning Accuracy | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500683 | Topic summary for [114][131] NR_AIML_air_part1 | Moderator(Qualcomm) |
| R4-2502855 | Summary of simulation results for AI beam prediction | vivo |
| R4-2502856 | WF on the requirements for AI/ML air interfance | Qualcomm |
| R4-2502969 | Updated simulation assumptions for beam prediction | vivo |
| R4-2502970 | Way forward on simulation assumptions for CSI prediction | OPPO |
| R4-2503012 | AI/ML ad-hoc meeting minutes-1 | Qualcomm |
| R4-2503020 | Summary of simulation results for AI beam prediction | vivo |
| R4-2503021 | Updated simulation assumptions for beam prediction | vivo, NTU, Nokia, Ericsson, Qualcomm, Xiaomi, Huawei, Hisilicon, Mediatek, OPPO, APPLE, Rohde & Schwarz, CATT, Samsung, Intel, ZTE Corporation, Sanechips, CAICT |
| R4-2503026 | Baseline Simulation assumptions for AIML based CSI prediction | OPPO, CAICT, vivo, Nokia, Ericsson, Qualcomm, Huawei, Hisilicon, Mediatek, CATT, Samsung, ZTE Corporation, Apple |
| TDoc | Title | Source |
|---|---|---|
| R4-2500230 | Discussion on General Aspects on Work Plan | Apple |
| R4-2501096 | Discussion on general aspects for study on AI/ML | CMCC |
| R4-2501530 | Discussion on general aspects on AIML for NR air interface phase 2 | Huawei, HiSilicon |
| R4-2501958 | General aspects of AI/ML for NR air interface Phase 2 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500167 | FR2 test setup for AI/ML beam management evaluation | Anritsu Corporation |
| R4-2500226 | Testing framework and procedure for one-sided models | Apple |
| R4-2500273 | Testing framework and procedure for one-sided models | OPPO |
| R4-2500403 | Testability for AI/ML beam management | Qualcomm Incorporated |
| R4-2500617 | Discussion on test framework and procedure for AI beam management | Xiaomi |
| R4-2500825 | Discussion on testing framework and procedure for one-sided models | vivo |
| R4-2500889 | Discussion on testing framework and procedure for one-sided models | MediaTek Inc. |
| R4-2501038 | Discussion on testing framework and procedure for one-sided models | CATT |
| R4-2501097 | Discussion on testing framework and procedure for one-sided models | CMCC |
| R4-2501531 | Discussion on testing framework and procedure for one-sided models | Huawei, HiSilicon |
| R4-2501959 | Testing framework and procedure for one-sided models | Nokia |
| R4-2501965 | Discussion on testing framework and procedure for AI-BM | Samsung |
| R4-2502174 | On Test Systems and Testability Aspects for FR2 AI/ML Beam | Keysight Technologies UK Ltd |
| TDoc | Title | Source |
|---|---|---|
| R4-2500227 | Study on CSI Compression: Testability and Interoperability issues | Apple |
| R4-2500271 | Testing issues for CSI compression two-sided models | OPPO |
| R4-2500339 | Discussion on Testing issues for CSI compression two-sided models | MediaTek inc. |
| R4-2500826 | Discussion on testing issues for CSI compression two-sided models | vivo |
| R4-2501039 | Discussion on testing issues for CSI compression two-sided models | CATT |
| R4-2501098 | Discussion on testing issues for CSI compression two-sided models | CMCC |
| R4-2501497 | On 2-sided compression study and simulations | Ericsson |
| R4-2501509 | Discussion on testability and interoperability issues for CSI compression | ZTE Corporation, Sanechips |
| R4-2501532 | Discussion on testing issues for CSI compression two-sided models | Huawei, HiSilicon |
| R4-2501960 | Testing issues for CSI compression two-sided models | Nokia |
| R4-2501966 | Study on testing issues for CSI compression two-sided models | Samsung |
| R4-2502169 | CSI Compression: Testability and Interoperability | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500684 | Topic summary for [114][132] NR_AIML_air_part2 | Moderator(Ericsson) |
| R4-2502953 | WF on AI/ML air interface study | Ericsson |
| R4-2503011 | Ad-hoc minutes for [114][132] NR_AIML_air_part2 | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500232 | General aspects on AI/ML for mobility in NR | Apple |
| R4-2501099 | Discussion on general part for AI/ML for mobility | CMCC |
| R4-2501233 | Discussion on genereal aspects in AIML mobility | Huawei, HiSilicon |
| R4-2501339 | Discussion on general aspects for AI mobility | vivo |
| R4-2501759 | General discussion on AI/ML for mobility | Ericsson |
| R4-2501961 | General aspects of AIML Mobility | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500233 | Study of impacts on RAN4 requirements for AIML Mobility in NR | Apple |
| R4-2500594 | Discussions on RAN4 requirement impacts of AIML for mobility | NTT DOCOMO, INC. |
| R4-2500619 | Discussion on impacts on RAN4 requirement for AI mobility | Xiaomi |
| R4-2500696 | Discussion impacts on requirements of AI/ML mobility | ZTE Corporation, Sanechips |
| R4-2500890 | Discussion on impact on RRM requirements of AI mobility | MediaTek Inc. |
| R4-2501040 | Discussion on impacts of AIML mobility on RRM requirements | CATT |
| R4-2501100 | Discussion on impacts on RAN4 requirements for AI/ML for mobility | CMCC |
| R4-2501133 | Study of impacts on RAN4 requirements for AI mobility | OPPO |
| R4-2501234 | Discussion on impacts of RAN4 requirements in AIML mobility | Huawei, HiSilicon |
| R4-2501340 | Discussion on impacts on RAN4 requirements for AI mobility | vivo |
| R4-2501674 | Discussion on general aspects and requirements impact | Samsung |
| R4-2501694 | Study of impacts on RAN4 requirements for AIML Mobility in NR | Tejas Network Limited |
| R4-2501760 | On requirements for AI/ML based mobility | Ericsson |
| R4-2501962 | On RRM Requirement Impacts of AIML Mobility | Nokia |
| R4-2502219 | (FS_NR_AIML_Mob) Impact of AI based mobility on RRM requirements | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500231 | On Testability and Interoperability Issues for AIML Mobility in NR | Apple |
| R4-2500628 | Discussion on study of testability and interoperability for AIML mobility | Xiaomi |
| R4-2500697 | Discussion on the Interoperability and testability aspects | ZTE Corporation, Sanechips |
| R4-2500891 | Discussion on testability and interoperability of AI mobility | MediaTek Inc. |
| R4-2501041 | Discussion on testability and interoperability issues for AIML mobility | CATT |
| R4-2501101 | Discussion on testability and interoperability for AI/ML for mobility | CMCC |
| R4-2501134 | Study of testability and interoperability for AI mobility | OPPO |
| R4-2501235 | Discussion on testability and interoperability issues in AIML mobility | Huawei, HiSilicon |
| R4-2501341 | Discussion on testability and interoperability for AI mobility | vivo |
| R4-2501675 | General discussion on AI mobility regarding testability and interoperability | Samsung |
| R4-2501761 | On testability issues related to AI/ML for mobility | Ericsson |
| R4-2502072 | Testability and Interoperability Issues for AI/ML Mobility | Nokia |
| R4-2502220 | (FS_NR_AIML_Mob) Testability and data consistency | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500533 | Topic summary for [114][219] FS_NR_AIML_Mob | Moderator (Nokia) |
| R4-2502574 | Ad-hoc minutes for FS_NR_AIML_Mob SI | Nokia |
| R4-2502594 | WF on FS_NR_AIML_Mob | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2501494 | R19 on power class for 3T | OPPO |
| TDoc | Title | Source |
|---|---|---|
| R4-2500110 | On the UE RF requirement for the FR2 asymmetric connection scenario | Qualcomm, Sony |
| R4-2500111 | dCR on RF requirements for a UE with different TCI states for UL and DL | Qualcomm, Sony |
| R4-2500308 | On UE RF impact of 3Tx UL MIMO | Apple |
| R4-2500767 | Further discussion of UE RF impact for NR MIMO phase 5 | vivo |
| R4-2501348 | UE RF requirements (MIMO Phase5) | Nokia |
| R4-2501409 | Progress on UE RF requirements of NR MIMO Phase 5 | Samsung |
| R4-2501495 | R19 MPR for 3Tx | OPPO |
| R4-2501740 | 3Tx NR specifications | Qualcomm Technologies |
| R4-2501839 | On RF requirements for Rel-19 NR-MIMO | Huawei, HiSilicon |
| R4-2502192 | On UE RF requirements for NR MIMO Phase 5 | Ericsson |
| R4-2502210 | Supporting full power mode 0 for 3Tx | Skyworks Solutions Inc. |
| R4-2502950 | dCR on RF requirements for a UE with different TCI states for UL and DL | Qualcomm, Sony |
| TDoc | Title | Source |
|---|---|---|
| R4-2500054 | Further considerations for enhanced UE-initiated/event-driven beam management | Qualcomm Technologies Ireland |
| R4-2500268 | On RRM Requirements for UE initiated beam management | Apple |
| R4-2500332 | RRM requirements on UE-initiated/event-driven beam management | China Telecom |
| R4-2500622 | Discussion on UE-initiated/event-driven beam management on Rel-19 MIMO phase 5 | Xiaomi |
| R4-2500775 | Discussion on RRM requirements of UE-initiated/event-driven beam management | LG Electronics Inc. |
| R4-2500909 | Discussion on RRM aspects of UE-initiated beam management of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
| R4-2501081 | Discussion on RRM requirements for event-driven beam management for NR MIMO Phase 5 | CMCC |
| R4-2501222 | Discussion on RRM impact for Rel-19 MIMO on UE initiated BM | Huawei, HiSilicon |
| R4-2501405 | On NR MIMO Phase 5 UEIBM requirements | Nokia |
| R4-2501462 | Discussion on RRM requirements of UE-initiated beam management in Rel-19 MIMO phase 5 | Samsung |
| R4-2501598 | Discussion on RRM requirements for UE initiated Beam reporting in R19 MIMO | vivo |
| R4-2502062 | Discussion on UE initiated BM requirements | Ericsson |
| R4-2502182 | Discussion on R19 MIMO for UE-initiated/event-driven beam management | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500055 | On additional RRM requirements for NR MIMO Phase 5 | Qualcomm Technologies Ireland |
| R4-2500269 | On RRM Requirements for MIMO Phase 5 | Apple |
| R4-2500623 | Discussion on other RRM requirement on Rel-19 MIMO phase 5 | Xiaomi |
| R4-2500910 | Discussion on other RRM aspects of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
| R4-2501082 | Discussion on other RRM requirements for NR MIMO Phase 5 | CMCC |
| R4-2501274 | Discussion on RRM impact for Rel-19 MIMO on other aspect | Huawei, HiSilicon |
| R4-2501463 | Discussion on RRM requirements of other aspects in Rel-19 MIMO phase 5 | Samsung |
| R4-2501599 | Discussion on other RRM requirement impacts in R19 MIMO | vivo |
| R4-2502063 | Other RRM requirements impact in MIMO | Ericsson |
| R4-2502066 | Simulation results for MIMO ph5 | Ericsson |
| R4-2502147 | Other aspects for NR MIMO Phase 5 RRM requirements | Nokia |
| R4-2502183 | Discussion on R19 MIMO for other RRM requirements | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500534 | Topic summary for [114][220] NR_MIMO_Ph5_Part1 | Moderator (Samsung) |
| R4-2500535 | Topic summary for [114][221] NR_MIMO_Ph5_Part2 | Moderator (MediaTek) |
| R4-2500685 | Topic summary for [114][133] NR_MIMO_Ph5_UE | Moderator(Samsung) |
| R4-2502575 | Ad-hoc minutes for NR_MIMO_Ph5 WI | Samsung |
| R4-2502595 | WF on RRM requirements for NR_MIMO_Ph5_Part1 | Samsung |
| R4-2502596 | WF on RRM requirements for NR_MIMO_Ph5_Part2 | MediaTek |
| R4-2502666 | Coffee break discussion minutes for NR_MIMO_Ph5 WI | Samsung |
| R4-2502667 | LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP | CMCC |
| R4-2502951 | WF on NR MIMO Phase 5 | Samsung |
| R4-2503037 | WF on NR MIMO Phase 5 | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500342 | Discussion on SBFD General aspects | Tejas Network Limited |
| R4-2500737 | Discussion on the subband configurations and guardbands for gNB SBFD | vivo |
| R4-2500865 | Discussion on SBFD general part | CMCC |
| R4-2501025 | Discussion on SBFD general issues | CATT |
| R4-2501327 | On SBFD system parameters | Nokia |
| R4-2501696 | Views on general aspects for SBFD | Qualcomm Germany |
| R4-2501840 | On general aspects for SBFD | Huawei, HiSilicon |
| R4-2501883 | Discussion on system parameters for SBFD BS | ZTE Corporation, Sanechips |
| R4-2501943 | Discussion on MPR impact on SBFD UL resource muting | Ericsson |
| R4-2501967 | Further discussion on general aspects for SBFD system | Samsung |
| R4-2502155 | SBFD general aspects | Ericsson |
| R4-2502250 | Cross Link Interference (CLI) handling impact on MPR for SBFD operation | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500343 | Discussion on Potentially new requirements for SBFD operation | Tejas Network Limited |
| R4-2500866 | Discussion on new RF requirement for SBFD | CMCC |
| R4-2501028 | Discussion on potentially new requirements for SBFD operation | CATT |
| R4-2501326 | On potentially new BS RF requirements for SBFD operation | Nokia |
| R4-2501708 | views on new BS RF requirements for SBFD | Qualcomm Germany |
| R4-2501841 | On potentially new requirements for SBFD | Huawei, HiSilicon |
| R4-2501884 | Discussion on potentially new requirements for SBFD operation | ZTE Corporation, Sanechips |
| R4-2501968 | On the potentially new requirements for SBFD operation for FR1 and FR2-1 | Samsung |
| R4-2502156 | Potentially new SBFD BS RF requirements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500345 | Discussion on existing Tx requirements for SBFD operation | Tejas Network Limited |
| R4-2500867 | Discussion on existing Tx requirements for SBFD | CMCC |
| R4-2501026 | Discussion on modification of existing Tx requirements for SBFD operation | CATT |
| R4-2501325 | On existing BS RF TX requirements for SBFD operation | Nokia |
| R4-2501697 | Views on existing BS RF requirements for SBFD | Qualcomm Germany |
| R4-2501855 | On modification of existing TX RF requirements for SBFD | Huawei, HiSilicon |
| R4-2501885 | Discussion on modification of existing Tx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
| R4-2501969 | On the modification of existing TX requirements for SBFD-capable BS | Samsung |
| R4-2502157 | Impact on SBFD BS RF TX requirements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500346 | Views on modification of existing Rx requirements for SBFD | Tejas Network Limited |
| R4-2500868 | Discussion on existing Rx requirements for SBFD | CMCC |
| R4-2501027 | Discussion on modification of existing Rx requirements for SBFD operation | CATT |
| R4-2501324 | On existing BS RF RX requirements for SBFD operation | Nokia |
| R4-2501856 | On modification of existing RX RF requirements for SBFD | Huawei, HiSilicon |
| R4-2501886 | Discussion on modification of existing Rx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
| R4-2501970 | On the modification of existing RX requirements for SBFD-capable BS | Samsung |
| R4-2502158 | Impact on SBFD BS RF RX requirements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500169 | Discussion on RRM impacts of UE-to-UE CLI handling | LG Electronics Inc. |
| R4-2500245 | On UE RRM requirements for UE-to-UE CLI handling | Apple |
| R4-2500466 | RRM requirements for UE-to-UE CLI handling | Nokia, Nokia Shanghai Bell |
| R4-2500468 | Simulation result for L1-CLI-SRS-RSRP measurement | Nokia, Nokia Shanghai Bell |
| R4-2500474 | Fair coexistence between SBFD and TDD networks | Charter Communications, Inc |
| R4-2500911 | Discussion on UE-to-UE CLI of R19 SBFD | ZTE Corporation, Sanechips |
| R4-2501042 | Discussion on UE to UE CLI handling | CATT |
| R4-2501088 | Discussion on RRM requirements for UE-to-UE CLI handling | CMCC |
| R4-2501113 | Discussion for RRM requirements for UE-to-UE CLI handling | Ericsson |
| R4-2501114 | Simulation results for L1-SRS-RSRP | Ericsson |
| R4-2501266 | Discussion on UE CLI measurement for SBFD | Huawei, HiSilicon |
| R4-2501267 | Additional simulation results for UE CLI measurement | Huawei, HiSilicon |
| R4-2501333 | Discussion on RRM requirements for UE-to-UE CLI handling for evolution of NR duplex operation | China Telecom |
| R4-2501415 | Further consideration on RRM requirements for UE-to-UE CLI handling | vivo |
| R4-2501464 | Views on L1 CLI measurement requirements | Samsung |
| R4-2502082 | Discussion on SBFD UE-to-UE CLI | MediaTek inc. |
| R4-2502083 | Discussion on SBFD simulation performance | MediaTek inc. |
| R4-2502231 | RRM requirements for UE-to-UE CLI handling | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500171 | Discussion on RRM impacts of SBFD operation | LG Electronics Inc. |
| R4-2500467 | RRM requirements for SBFD operation | Nokia, Nokia Shanghai Bell |
| R4-2500912 | Discussion on other RRM impacts of R19 SBFD | ZTE Corporation, Sanechips |
| R4-2501043 | Discussion on impacts of SBFD on RRM requirements | CATT |
| R4-2501087 | Discussion on RRM impacts for SBFD operation | CMCC |
| R4-2501115 | Discussion for RRM requirements for SBFD operations | Ericsson |
| R4-2501268 | Discussion on RRM impacts for SBFD operation | Huawei, HiSilicon |
| R4-2501334 | Discussion on RRM impacts for SBFD operation for evolution of NR duplex operation | China Telecom |
| R4-2501416 | Further consideration on RRM impacts for SBFD operation | vivo |
| R4-2501465 | Views on RRM requirements for Rel-19 SBFD operation | Samsung |
| R4-2502084 | Discussion on SBFD Operation | MediaTek inc. |
| R4-2502230 | RRM requirements for SBFD operation | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500536 | Topic summary for [114][222] NR_duplex_evo | Moderator (Huawei) |
| R4-2500567 | Topic summary for [114][306] NR_duplex_evo_General | Moderator (Samsung) |
| R4-2500568 | Topic summary for [114][307] NR_duplex_evo_BSRF | Moderator (Huawei) |
| R4-2502297 | Ad-hoc meeting minutes for [114][307] NR_duplex_evo_BSRF | Huawei |
| R4-2502307 | Ad-hoc meeting minutes for [114][306] NR_duplex_evo_General | Samsung |
| R4-2502310 | Way Forward for [114][306] NR_duplex_evo_General | Samsung |
| R4-2502311 | Way Forward for [114][307] NR_duplex_evo_BSRF | Huawei |
| R4-2502380 | Way Forward for [114][307] NR_duplex_evo_BSRF | Huawei |
| R4-2502573 | Ad-hoc minutes for NR_duplex_evo WI | Samsung |
| R4-2502597 | WF on RRM requirements for NR_duplex_evo | Samsung |
| R4-2502632 | LS on L1 CLI measurement | Huawei |
| R4-2502633 | Updated summary of simulation results for L1-SRS-RSRP | Huawei |
| R4-2502668 | Ad-hoc #2 minutes for NR_duplex_evo WI | Samsung |
| R4-2502699 | WF on RRM requirements for NR_duplex_evo | Samsung |
| TDoc | Title | Source |
|---|---|---|
| R4-2500402 | Discussion on Ambient IoT deployment scenario in Rel-19 | Qualcomm Incorporated |
| R4-2500639 | Discussion on AIoT system parameters | Xiaomi |
| R4-2500743 | Discussion on the systeme parameter of AIoT | vivo |
| R4-2500778 | Discussion on system parameters for ambient IoT | Spreadtrum,UNISOC |
| R4-2500781 | A-IoT general aspects | Huawei, HiSilicon |
| R4-2500875 | Ambient IoT Work Item work plan | CMCC, Huawei, T-Mobile USA |
| R4-2500876 | Discussion on system parameters for A-IOT | CMCC |
| R4-2501792 | general aspects | OPPO |
| R4-2501867 | Discussions on General aspect for A-IoT | ZTE Corporation, Sanechips |
| R4-2502099 | A-IoT general overview | Ericsson |
| R4-2502669 | Coffee break discussion minutes for FS_NR_AIML_Mob | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500489 | Ambient IoT reader ACS requirements with external CW | Qualcomm Incorporated |
| R4-2500744 | Discussion on the RF requirement for AIoT BS | vivo |
| R4-2500782 | RF requirements for A-IoT BS | Huawei, HiSilicon |
| R4-2500877 | Discussion on BS RF requirements for A-IOT | CMCC |
| R4-2501029 | Discussion on A-IoT BS requirements | CATT |
| R4-2501868 | Discussions on RF requirements for A-IoT BS | ZTE Corporation, Sanechips |
| R4-2502098 | A-IoT BS RF impact overview | Ericsson |
| R4-2502253 | Discussion on RF requirement for Type 1-C Ambient-IoT BS | LG Electronics UK |
| TDoc | Title | Source |
|---|---|---|
| R4-2500490 | Ambient IoT device requirements | Qualcomm Incorporated |
| R4-2500614 | Discussion on RF requirements for ambient IoT device 1 | Spreadtrum,UNISOC |
| R4-2500640 | Discussion on AIoT device 1 RF requirements | Xiaomi |
| R4-2500745 | Discussion on the RF requirement for device 1 | vivo |
| R4-2500878 | Discussion on device RF requirements for A-IOT | CMCC |
| R4-2500999 | Discussion on Ambient IoT device 1 RF requirements | CATT |
| R4-2501155 | RF requirements of ambient IoT device 1 | Sony |
| R4-2501795 | RF requirements for device 1 | OPPO |
| R4-2501869 | Discussion on RF requirement of Ambient IoT device | ZTE Corporation, Sanechips |
| R4-2502100 | A-IoT device requirement overview | Ericsson |
| R4-2502235 | On the RF requirements for Ambient IoT Device | Huawei, HiSilicon |
| R4-2502261 | Discussion on RF requirement for device 1 | LG Electronics UK |
| TDoc | Title | Source |
|---|---|---|
| R4-2500615 | Discussion on RF requirements for CW | Spreadtrum,UNISOC |
| R4-2500641 | Discussion on AIoT CW RF requirements | Xiaomi |
| R4-2500746 | Discussion on the RF requirement for CW | vivo |
| R4-2500879 | Discussion on CW requirements | CMCC |
| R4-2501030 | Discussion on RF requirements for CW for D1T1 | CATT |
| R4-2501794 | RF requirements for CW | OPPO |
| R4-2501863 | RF requirements for CW | Huawei, HiSilicon |
| R4-2501870 | Discussion on RF requirement for CW node | ZTE Corporation, Sanechips |
| R4-2502101 | CW node RF impact overview | Ericsson |
| R4-2502256 | CW phase noise requirement | Qualcomm Incorporated |
| R4-2502270 | Discussion on RF requirement for CW | LG Electronics UK |
| TDoc | Title | Source |
|---|---|---|
| R4-2500209 | on OTA tests for ambient IoT devices | Huawei, HiSilicon |
| R4-2500401 | Discussion on Ambient IoT Testability | Qualcomm Incorporated |
| R4-2500747 | Discussion on the OTA test method for device | vivo |
| R4-2501156 | Consideration on the OTA test of ambient IoT device 1 | Sony |
| R4-2501623 | Discussion on OTA testing for A-IoT device 1 | Ericsson-LG Co., LTD |
| R4-2501793 | OTA test method for AIOT device 1 | OPPO |
| R4-2501974 | Discussion on OTA test method for A-IoT device | CAICT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500686 | Topic summary for [114][134] A-IoT_device | Moderator(CMCC) |
| R4-2500687 | Topic summary for [114][135] A-IoT_BSCW | Moderator(Huawei) |
| R4-2502858 | WF on requirements for A-IoT device | CMCC |
| R4-2502859 | WF on requirements for A-IoT BS and CW | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R4-2501600 | Discussion on RRM requirement impacts from on-demand SIB1 in R19 NES | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500056 | Further considerations for on-demand SSB SCell operation | Qualcomm Technologies Ireland |
| R4-2500388 | Discussion on RRM requirements for OD-SSB for network energy saving | MediaTek inc. |
| R4-2500456 | Discussion on on-demand SSB SCell operation | Apple |
| R4-2500465 | RRM requirements for OD-SSB SCell operation | Nokia, Nokia Shanghai Bell |
| R4-2500635 | Discussion on OD-SSB requirements | Xiaomi |
| R4-2500772 | Discussion on RRM requirements of on-demand SSB Scell operation for Rel-19 NES | LG Electronics Inc. |
| R4-2500848 | Discussion on RRM requirement of OD-SSB for NES enhancement | CMCC |
| R4-2500907 | Discussion on On-demand SSB SCell operation of R19 NES | ZTE Corporation, Sanechips |
| R4-2501017 | Discussion on RRM requirements for on-demand SSB SCell operation | CATT |
| R4-2501126 | On RRM requirements of on-demand SSB SCell operation | OPPO |
| R4-2501146 | Discussion on RRM requirements for On-demand SSB SCell operations | Intel Corporation |
| R4-2501220 | Discussion on RRM impact for Rel-19 NES OD-SSB | Huawei, HiSilicon |
| R4-2501304 | Discussion on OD-SSB in Rel-19 NES | Ericsson |
| R4-2501335 | Discussion on On-demand SSB SCell operation for enhancements of network energy savings for NR | China Telecom |
| R4-2501601 | Discussion on RRM requirements for on-demand SSB SCell operation in R19 NES | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500057 | On RRM requirements for adaptation of common signal/channel transmission | Qualcomm Technologies Ireland |
| R4-2500389 | Discussion on RRM requirements for adaptation of common signal/channel transmission | MediaTek inc. |
| R4-2500457 | Discussion on adaptation of common signal/channel transmission | Apple |
| R4-2500636 | Discussion on RRM requirements for adaptation of common signal/channel in NES | Xiaomi |
| R4-2500773 | Discussion on RRM requirements of SSB adaptation for Rel-19 NES | LG Electronics Inc. |
| R4-2500849 | Discussion on RRM requirement of OD-SIB1 and signal adapatation for NES enhancement | CMCC |
| R4-2500908 | Discussion on adaptation of common signal and channel of R19 NES | ZTE Corporation, Sanechips |
| R4-2501018 | Discussion on RRM requirements for adaptation of common signalchannel transmission | CATT |
| R4-2501127 | On RRM requirements of SSB adaptation | OPPO |
| R4-2501221 | Discussion on RRM impact for Rel-19 NES on adaptation | Huawei, HiSilicon |
| R4-2501305 | Discussion on RS and channel adaptation in Rel-19 NES | Ericsson |
| R4-2501336 | Discussion on adaptation of common signal/channel transmission for enhancements of network energy savings for NR | China Telecom |
| R4-2501602 | Discussion on RRM requirements for common signal or channel adaptation in R19 NES | vivo |
| R4-2501676 | General discussion on the NES common signal adaptation | Samsung |
| R4-2502240 | RRM requirements for SSB adaptation | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R4-2500537 | Topic summary for [114][223] Netw_Energy_NR_enh_Part1 | Moderator (Ericsson) |
| R4-2500538 | Topic summary for [114][224] Netw_Energy_NR_enh_Part2 | Moderator (Huawei) |
| R4-2502578 | Ad-hoc minutes for Netw_Energy_NR_enh WI | Ericsson |
| R4-2502598 | WF on RRM requirements for Netw_Energy_NR_enh_Part1 | Ericsson |
| R4-2502599 | WF on RRM requirements for Netw_Energy_NR_enh_Part2 | Huawei |
| R4-2502689 | WF on RRM requirements for Netw_Energy_NR_enh_Part2 | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R4-2500157 | Further consideration on general aspects of LP-WUS | Huawei, HiSilicon |
| R4-2500753 | TR 38.774 v0.2.0 | vivo |
| R4-2500754 | Draft Big CR for LP-WUS UE RF requirements in Rel-19 | vivo |
| R4-2501067 | TP to TR 38.774 on Clause 6 (Simulation assumptions and evaluation) | CATT |
| R4-2501381 | TP for TR 38.774 on LP-WUS | Nokia |
| R4-2502093 | On general issues for WUR | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2501157 | views on requirements of the low-power wake-up receiver | Sony |
| TDoc | Title | Source |
|---|---|---|
| R4-2500551 | Discussion on system parameters for LP-WUS/WUR | ZTE Corporation, Sanechips |
| R4-2500651 | Discussion on systems parameters for LP-WUR | Spreadtrum,UNISOC |
| R4-2500755 | TP to TR 38.774 on LP-WUS | vivo |
| R4-2500756 | Discussions on LP-WUS system parameters | vivo |
| R4-2500861 | Discussion on LP-WUS UE system parameters requirements | CMCC |
| R4-2501068 | Further discussion on system parameters for LP-WUS | CATT |
| R4-2501069 | TP to TR 38.774 on Clause 5 (System parameters) | CATT |
| R4-2501070 | draftCR to TS 38.101-1 on system parameters for LP-WUS | CATT |
| R4-2501071 | draftCR to TS 38.101-2 on system parameters for LP-WUS | CATT |
| R4-2501377 | System parameters for LP-WUR | Nokia |
| R4-2502094 | On system parameter for WUR | Ericsson |
| R4-2503027 | TP for TR 38.774 on LP-WUS UE RF | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500109 | On UE RF requirements for the LPWUR | Qualcomm Incorporated |
| R4-2500158 | Further consideration on UE REFSENS, ACS requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
| R4-2500307 | On LP-WUR Rx requirements | Apple |
| R4-2500503 | Discussion on UE RF requirements for LP-WUR | Samsung |
| R4-2500552 | Discussion on REFSENS, ASCS, ACS for LP-WUR | ZTE Corporation, Sanechips |
| R4-2500652 | Discussion on RX requirements of REFSENS for LP-WUR | Spreadtrum,UNISOC |
| R4-2500757 | Discussions on LP-WUS REFSENS, ASCS and ACS | vivo |
| R4-2500758 | draft CR to 38.101-1 on LP-WUS RF | vivo |
| R4-2500862 | Discussion on LP-WUS UE RF Rx requirements of REFSENS, ASCS and ACS | CMCC |
| R4-2500901 | Discussion for LP-WUR REFSENS requirement | LG Electronics France |
| R4-2501072 | Further discussion on REFSENS for LP-WUS | CATT |
| R4-2501378 | Fundamental RX requirements for LP-WUR | Nokia |
| R4-2502097 | WUR RF requirement REFSESN ACS ASCS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500159 | Further consideration on UE RF other Rx requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
| R4-2500553 | Discussion on receiver characteristics for LP-WUR | ZTE Corporation, Sanechips |
| R4-2500863 | Discussion on LP-WUS UE RF Rx requirements of IBB, OBB, intermodulation, spurious emissions and others | CMCC |
| R4-2501073 | Further discussion on other RF requirements for LP-WUS | CATT |
| R4-2501379 | Other RX requirements for LP-WUR | Nokia |
| R4-2502096 | WUR RF requirement other than REFSENS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500160 | Further consideration on UE RF testability issues for Rel-19 LP-WUS | Huawei, HiSilicon |
| R4-2500504 | Discussion on testability for LP-WUR | Samsung |
| R4-2500554 | Discussion on testability of LP-WUR | ZTE Corporation, Sanechips |
| R4-2500759 | Discussions on LP-WUS Testability | vivo |
| R4-2501074 | Further discussion on Testability for UE RF requirements for LP-WUS | CATT |
| R4-2501380 | Testability aspects of LP-WUR | Nokia |
| R4-2502095 | On WUR RF requirement testability | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500075 | BS RF requirements for low-power wake-up signal for NR | Nokia |
| R4-2500161 | Further consideration on BS RF for Rel-19 LP-WUS | Huawei, HiSilicon |
| R4-2500550 | Discussion on BS RF requirements for LP-WUS/WUR | ZTE Corporation, Sanechips |
| R4-2500555 | TP to TR 38.774 on LP-WUS power boosting (Clause 7.2.2) | ZTE Corporation, Sanechips |
| R4-2500556 | TP to TR 38.774 on regulation relevant spectrum requirements (Clause 7.2.3) | ZTE Corporation, Sanechips |
| R4-2500760 | Discussions on LP-WUS BS RF requirements | vivo |
| R4-2500864 | Discussion on LP-WUS BS RF requirements | CMCC |
| R4-2501075 | Further discussion on BS RF requirements for LP-WUS | CATT |
| R4-2502092 | TP to TR38.774: BS RF requirement overview for LP-WUS | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500172 | Discussion on simulation assumptions and results for LP-WUS/WUR | LG Electronics Inc. |
| R4-2500276 | Simulation Assumptions and Results for LP-WUR Core Requirements | Apple |
| R4-2500277 | Proposal for Simulation Results Collection for LP-SS Performance | Apple |
| R4-2500850 | Simulation assumption and results for LP-WUR | CMCC |
| R4-2501177 | Discussion on OOK based LP-WUR simulation | ZTECorporation,Sanechips |
| R4-2501264 | Simulation assumption and additional simulation results for LP-WUR measurement | Huawei, HiSilicon |
| R4-2501302 | Simulation assumption on LP-WUS RRM measurement | Ericsson |
| R4-2501303 | Simulation on LP-WUS RRM measurement | Ericsson |
| R4-2501417 | Discussion on simulation assumptions and results for LP-WUR | vivo |
| R4-2501980 | Discussion on LP-WUS-WUR Simulation assumptions and results | Nokia |
| R4-2502178 | Simulation assumptions for R19 LP-WUS | MediaTek inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500173 | Discussion on RRM core requirements for LP-WUS/WUR | LG Electronics Inc. |
| R4-2500238 | On RRM core requirements for LP-WUR | Apple |
| R4-2500629 | Discussion on RRM core requirements for LP-WUS/WUR | Xiaomi |
| R4-2500851 | Discussion on RRM impact of LP-WUR | CMCC |
| R4-2501019 | Discussion on RRM requirements for LP-WUS/WUR | CATT |
| R4-2501135 | Discussion on RRM requirements for LP-WUSWUR | OPPO |
| R4-2501173 | Discussion on LP-WUS for core part | ZTECorporation,Sanechips |
| R4-2501265 | Discussion on RRM requirements for LP-WUR | Huawei, HiSilicon |
| R4-2501301 | Discussion on LP-WUS RRM requirement | Ericsson |
| R4-2501337 | Discussion on RRM core requirements for LP-WUS/WUR | China Telecom |
| R4-2501418 | Further considerations on RRM for LP-WUR | vivo |
| R4-2501979 | Discussion on LP-WUS-WUR core requirements | Nokia |
| R4-2502179 | Discussion on the RRM core requirements for LP-WUS | MediaTek inc. |
| R4-2502228 | RRM requirements for LP-WUR | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500539 | Topic summary for [114][225] NR_LPWUS | Moderator (vivo) |
| R4-2500569 | Topic summary for [114][308] NR_LPWUS | Moderator (Huawei) |
| R4-2500688 | Topic summary for [114][136] NR_LPWUS_UERF | Moderator(Vivo) |
| R4-2502298 | Ad-hoc meeting minutes for [114][308] NR_LPWUS | Huawei |
| R4-2502305 | Way Forward for [114][308] NR_LPWUS | Huawei |
| R4-2502577 | Ad-hoc minutes for NR_LPWUS WI | vivo |
| R4-2502600 | WF on RRM requirements for NR_LPWUS | vivo |
| R4-2502879 | WF on UE RF requirements for LP-WUS | vivo |
| R4-2502981 | LS on LP-WUS UE RF | vivo |
| R4-2503003 | LS on LP-WUS UE RF | Vivo |
| R4-2503004 | WF on UE RF requirements for LP-WUS | vivo |
| R4-2503028 | WF on UE RF requirements for LP-WUS | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500884 | Discussion on General aspects | MediaTek Inc. |
| TDoc | Title | Source |
|---|---|---|
| R4-2500458 | Discussion on event triggered L1 measurement reporting | Apple |
| R4-2500620 | Discussion on event triggered L1 measurement reporting for mobility | Xiaomi |
| R4-2500702 | Discussion on Event triggered L1 measurement reporting | ZTE Corporation, Sanechips |
| R4-2500885 | Discussion on event triggered L1 report for LTM | MediaTek Inc. |
| R4-2501020 | Discussion on Event triggered L1 measurement reporting for Rel-19 LTM enhancements | CATT |
| R4-2501083 | Discussion on event triggered L1 measurement reporting | CMCC |
| R4-2501128 | On event triggered L1 measurement reporting | OPPO |
| R4-2501230 | Discussion on Event triggered L1 measurement reporting | Huawei, HiSilicon |
| R4-2501404 | On Event-triggered L1 reporting requirements for LTM | Nokia |
| R4-2501421 | RRM Core requirements on event triggered L1 measurement reporting | China Telecom |
| R4-2501603 | Discussion on RRM requirements for event-triggered L1-RSRP reporting in R19 LTM | vivo |
| R4-2502064 | Event triggered L1 measurement reporting | Ericsson |
| R4-2502221 | (NR_Mob_Ph4-Core) Event triggered L1 measurement reporting for LTM | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500442 | On CSI-RS based L1 measurement | Apple |
| R4-2500621 | Discussion on CSI-RS based L1 for mobility | Xiaomi |
| R4-2500703 | Discussion on CSI-RS based L1-RSRP measurement | ZTE Corporation, Sanechips |
| R4-2500886 | Discussion on CSI-RS L1 measurement for LTM | MediaTek Inc. |
| R4-2501021 | Discussion on CSI-RS based L1 measurement for Rel-19 LTM enhancements | CATT |
| R4-2501084 | Discussion on CSI-RS based L1 measurement | CMCC |
| R4-2501129 | On CSI-RS based L1 measurement | OPPO |
| R4-2501231 | Discussion on CSI-RS based L1 measurement | Huawei, HiSilicon |
| R4-2501422 | RRM Core requirements on CSI-RS based L1 measurement | China Telecom |
| R4-2501604 | Discussion on RRM requirements for CSI-RS based L1 measurement in R19 LTM | vivo |
| R4-2501982 | Discussion on CSI-RS based L1 measurement | Nokia |
| R4-2502065 | CSI-RS based L1 measurement | Ericsson |
| R4-2502222 | (NR_Mob_Ph4-Core) CSI-RS based L1 measurement for LTM | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500061 | On CLTM RRM requirements | Nokia |
| R4-2500459 | Discussion on conditional Intra-CU LTM | Apple |
| R4-2500630 | Discussion on Conditional Intra-CU LTM for NR mobility enhancements Phase 4 | Xiaomi |
| R4-2500704 | Discussion on Conditional Intra-CU LTM | ZTE Corporation, Sanechips |
| R4-2500887 | Discussion on Conditional LTM | MediaTek Inc. |
| R4-2501022 | Discussion on conditional Intra-CU LTM for Rel-19 mobility enhancements | CATT |
| R4-2501085 | Discussion on conditional intra-CU LTM | CMCC |
| R4-2501116 | Discussion on conditional Intra-CU LTM | Ericsson |
| R4-2501232 | Discussion on conditional Intra-CU LTM | Huawei, HiSilicon |
| R4-2501344 | Further discussion on Conditional Intra-CU LTM | vivo |
| R4-2501423 | RRM Core requirements on conditional Intra-CU LTM | China Telecom |
| R4-2502223 | (NR_Mob_Ph4-Core) Conditional LTM | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500540 | Topic summary for [114][226] NR_Mob_Ph4_Part1 | Moderator (Apple) |
| R4-2500541 | Topic summary for [114][227] NR_Mob_Ph4_Part2 | Moderator (China Telecom) |
| R4-2502579 | Ad-hoc minutes for NR_Mob_Ph4 WI | Apple |
| R4-2502601 | WF on RRM requirements for NR_Mob_Ph4_Part1 | Apple |
| R4-2502602 | WF on RRM requirements for NR_Mob_Ph4_Part2 | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R4-2501611 | Draft LS response on UE assistance information | Ericsson |
| R4-2502241 | General aspects for XR enhancements | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500216 | NR_XR_Ph3 RRM core requirements analysis | InterDigital France R&D, SAS |
| R4-2500333 | RRM requirements on XR enhancements | China Telecom |
| R4-2500460 | Discussion of RRM impact of XR for NR Phase 3 | Apple |
| R4-2500595 | Discussions on RRM core requirements for XR | NTT DOCOMO, INC. |
| R4-2500827 | Further discussion on RRM requirements for XR | vivo |
| R4-2500913 | Discussion on RRM aspects of R19 XR | ZTE Corporation, Sanechips |
| R4-2501086 | Discussion on XR (eXtended Reality) for NR Phase 3 | CMCC |
| R4-2501223 | Discussion on RRM requirements for Rel-19 XR | Huawei, HiSilicon |
| R4-2501612 | On RRM requirements for XR | Ericsson |
| R4-2502085 | Discussion on RRM requirements for XR | MediaTek inc. |
| R4-2502150 | Discussion on XR ph3 RRM requirements | Nokia |
| R4-2502229 | RRM requirements for XR enhancements | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500542 | Topic summary for [114][228] NR_XR_Ph3 | Moderator (Nokia) |
| R4-2502580 | Ad-hoc minutes for NR_XR_Ph3 WI | Nokia |
| R4-2502603 | WF on RRM requirements for NR_XR_Ph3 | Nokia |
| R4-2502700 | WF on RRM requirements for NR_XR_Ph3 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500414 | Draft CR to TS 38.108: Introduction of regenerative payload | NEC, THALES |
| R4-2502283 | Draft CR to TS 38.108: Introduction of regenerative payload | NEC, THALES |
| TDoc | Title | Source |
|---|---|---|
| R4-2500319 | On NTN RedCap UE HD-FDD REFSENS | Apple |
| R4-2501003 | Discussion on RF requirements for NTN RedCap UE | CATT |
| R4-2501080 | Disscussion on NTN (e)Redcap UE RF requirements | Spreadtrum,UNISOC |
| R4-2501158 | REFSENS for NTN Redcap and eRedcap | Sony |
| R4-2501322 | Views on increasing MOP tolerance for NTN HD-FDD Redcap | NTT DOCOMO INC. |
| R4-2501382 | RedCap NTN UEs | Nokia |
| R4-2501450 | Discussion on the remaining issues for NR NTN phase 3 | Huawei, HiSilicon |
| R4-2501477 | Discussion on RedCap UE RF requirements with NR NTN operating in FR1-NTN bands | OPPO |
| R4-2501727 | Discussion on Rel-19 NR-NTN RedCap UE RF requirements | MediaTek (Hefei) Inc. |
| R4-2502013 | NR NTN RedCap UE RF requirements | Qualcomm Inc. |
| R4-2502103 | RedCap UE RF impact on HD-FDD | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2502012 | NR NTN UL Capacity Enhancements | Qualcomm Inc. |
| R4-2502104 | Other NTN UE RF impact | Ericsson, Sony |
| TDoc | Title | Source |
|---|---|---|
| R4-2500086 | Draft CR to TS 38.108: Introduction of regenerative payload | NEC Europe Ltd |
| TDoc | Title | Source |
|---|---|---|
| R4-2500239 | On R19 NTN (e)RedCap RRM requirements | Apple |
| R4-2500390 | Discussion on NTN (e)Redcap RRM requirements | MediaTek inc. |
| R4-2500631 | Discussion on (e)RedCap RRM requirements in NTN for NR Phase 3 | Xiaomi |
| R4-2500852 | Discussion on the RRM requirement for Redcap over NTN | CMCC |
| R4-2500895 | Discussion on RRM requirements for (e)RedCap in NTN | LG Electronics Inc. |
| R4-2501023 | Discussion on (e)RedCap RRM requirements for Rel-19 NTN phase3 | CATT |
| R4-2501130 | Discussion on (e)RedCap RRM requirements of R19 NR NTN | OPPO |
| R4-2501174 | Discussion on RRM requirements for RedCap NTN | ZTECorporation,Sanechips |
| R4-2501269 | Discussion on RRM requirements for RedCap UE in NTN | Huawei, HiSilicon |
| R4-2501287 | Discussion on RedCap RRM requirements for NTN for NR Phase 3 | Ericsson |
| R4-2501342 | Discussion on RRM requirements on (e)RedCap for R19 NR NTN Phase 3 | vivo |
| R4-2501466 | Discussion on RRM requirements of RedCap in Rel-19 NTN phase 3 | Samsung |
| R4-2501486 | Discussing requirements for RedCap support in NR NTN | Nokia |
| R4-2502225 | (NR_NTN_Ph3-Core) RedCap for NTN | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500240 | On R19 other NTN RRM requirements | Apple |
| R4-2500391 | Discussion on NTN RRM requirements for SSB periodicity up to 160ms | MediaTek inc. |
| R4-2500632 | Discussion on other RRM core requirements in NTN for NR Phase 3 | Xiaomi |
| R4-2500853 | Discussion on the RRM requirement for NTN phase3 | CMCC |
| R4-2500898 | Discussion on RRM requirements for downlink coverage enhancement in NTN | LG Electronics Inc. |
| R4-2501024 | Discussion on other RRM requirements for Rel-19 NTN phase3 | CATT |
| R4-2501131 | Discussion on other RRM requirements of R19 NR NTN | OPPO |
| R4-2501270 | Discussion on other RRM requirements for Rel-19 NTN | Huawei, HiSilicon |
| R4-2501288 | Discussion on other RRM requirements for NTN for NR Phase 3 | Ericsson |
| R4-2501343 | Discussion on RRM impacts on DL coverage for R19 NR NTN Phase 3 | vivo |
| R4-2501467 | Discussion on RRM requirements of other aspects in Rel-19 NTN phase 3 | Samsung |
| R4-2501487 | On the impact of extended SSB periodicity on the main NTN cell | Nokia |
| R4-2502226 | (NR_NTN_Ph3-Core) Downlink coverage enhancement for NTN | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500543 | Topic summary for [114][229] NR_NTN_Ph3_Part1 | Moderator (CATT) |
| R4-2500544 | Topic summary for [114][230] NR_NTN_Ph3_Part2 | Moderator (Qualcomm) |
| R4-2500570 | Topic summary for [114][309] NR_NTN_Ph3_General_SAN_RF | Moderator (Thales) |
| R4-2500571 | Topic summary for [114][310] NR_NTN_Ph3_UE_RF | Moderator (Qualcomm) |
| R4-2502281 | Way Forward for [114][310] NR_NTN_Ph3_UE_RF | Qualcomm |
| R4-2502604 | WF on RRM requirements for NR_NTN_Ph3_Part1 | CATT |
| R4-2502605 | WF on RRM requirements for NR_NTN_Ph3_Part2 | Qualcomm |
| R4-2502684 | Ad-hoc minutes for [NR_NTN_Ph3-Core] WI | Qualcomm Incorporated, CATT |
| TDoc | Title | Source |
|---|---|---|
| R4-2500426 | Draft CR to TS 36.108: Introduction of regenerative payload | NEC, THALES |
| R4-2502286 | Draft CR to TS 36.108: Introduction of regenerative payload | NEC, THALES |
| TDoc | Title | Source |
|---|---|---|
| R4-2501159 | OCC scheme on the RF requirements for IoT NTN | Sony |
| R4-2501849 | Discussion on RF requirement impact for IoT NTN phase 3 | MediaTek (Hefei) Inc. |
| R4-2502014 | IoT NTN UL Capacity Enhancements | Qualcomm Inc. |
| R4-2502105 | On IoT NTN UE RF requirment | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500854 | Discussion on the RRM requirement for IOT NTN phase3 | CMCC |
| R4-2501484 | On introducing requirements for CB-MSG3 in TS 36.133 | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R4-2500545 | Topic summary for [114][231] IoT_NTN_Ph3 | Moderator (MediaTek) |
| R4-2500576 | Topic summary for [114][315] IoT_NTN_Ph3 | Moderator (MediaTek) |
| R4-2502287 | Way Forward for [114][315] IoT_NTN_Ph3 | MediaTek |
| R4-2502373 | Way Forward for [114][315] IoT_NTN_Ph3 | MediaTek |
| R4-2502606 | WF on RRM requirements for IoT_NTN_Ph3 | MediaTek |
| TDoc | Title | Source |
|---|---|---|
| R4-2500136 | Work plan for WID: introduction of IoT-NTN TDD mode | Iridium Satellite LLC |
| R4-2502291 | Work plan for WID: introduction of IoT-NTN TDD mode | Iridium Satellite LLC |
| TDoc | Title | Source |
|---|---|---|
| R4-2500611 | Discussion on system parameters and UE RF requirements for the new NB-IoT TDD operating NTN band | ZTE Corporation, Sanechips |
| R4-2500738 | Discussion on band and system parameters for IoT-NTN TDD mode | vivo |
| R4-2502026 | General Discussion on the NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
| TDoc | Title | Source |
|---|---|---|
| R4-2502027 | Discussion on SAN RF requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
| TDoc | Title | Source |
|---|---|---|
| R4-2500491 | Initial views on RF impact for NTN IoT TDD | Qualcomm Incorporated |
| R4-2502050 | Discussion on UE RF requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
| TDoc | Title | Source |
|---|---|---|
| R4-2501178 | Discussion on IoT NTN TDD mode | ZTECorporation,Sanechips |
| R4-2501224 | Discussion on RRN impact due to periodic pattern for IoT NTN | Huawei, HiSilicon |
| R4-2501488 | The impact of the NTN IOT TDD Periodic Pattern on RRM requirements | Nokia |
| R4-2502052 | Discussion on RRM requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
| R4-2502224 | (IoT_NTN_TDD-Core) RRM requirements for IoT NTN in TDD mode | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500546 | Topic summary for [114][232] IoT_NTN_TDD | Moderator (Qualcomm) |
| R4-2500578 | Topic summary for [114][317] IoT_NTN_TDD_General | Moderator (Qualcomm) |
| R4-2500579 | Topic summary for [114][318] IoT_NTN_TDD_UE_SAN_RF | Moderator (Thales) |
| R4-2502292 | Way Forward for [114][318] IoT_NTN_TDD_UE_SAN_RF | THALES |
| R4-2502607 | WF on RRM requirements for IoT_NTN_TDD | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R4-2500495 | Cross Link Interference (CLI) handling impact on MPR for SBFD operation | Qualcomm Incorporated |
| TDoc | Title | Source |
|---|---|---|
| R4-2500739 | Discussion on UE capabilities for FR2-NTN | vivo |
| R4-2500740 | Draft reply LS on UE capabilities for FR2-NTN | vivo |
| R4-2501907 | On UE capability for NTN FR2 200MHz channel bandwidth | Ericsson |
| R4-2502977 | Reply LS on UE capabilities for FR2-NTN | vivo |
| R4-2503039 | Reply LS to RAN2 on UE capabilities for FR2-NTN | vivo |
| TDoc | Title | Source |
|---|---|---|
| R4-2500547 | Topic summary for [114][233] Reply_LS | Moderator (Apple) |
| R4-2500591 | Topic summary for [114][330] LS_BDaT | Moderator (Qualcomm) |
| R4-2500689 | Topic summary for [114][137] NR_reply_LS_UE_RF | Moderator(Apple) |
| TDoc | Title | Source |
|---|---|---|
| R4-2501624 | Introducing Tx switching for 3Tx UEs in Rel-19 TEI | MediaTek Inc., Orange, T-Mobile USA, Vodafone, Verizon |
| R4-2501653 | Progress update and next steps for the CA database | Nokia, Ericsson |
| R4-2502976 | WF on progress update and next steps for the CA database | Nokia, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R4-2500102 | On RAN task to work on framework simplification for co-location/co-existence requirements | Nokia |
| R4-2500880 | On the topic of BS RF specification structure improvements | Ericsson |
| R4-2500991 | Discussion on framework simplification for co-location/co-existence requirements | CATT |
| R4-2502139 | Discussion on framework simplification for co-location/co-existence requirements | Huawei, HiSilicon |
| R4-2502306 | Way Forward for [114][331] BSRF_Simplify_CoLo_Coex | Ericsson |
| R4-2502572 | Topic summary for [114][331] BSRF_Simplify_CoLo_Coex | Moderator (Ericsson) |
| TDoc | Title | Source |
|---|---|---|
| R4-2500170 | New band for 5G Broadcast Utilizing Geosynchronous Satellite | ASTRUM MOBILE PTE. LTD. |
| R4-2500174 | 5G Broadcast Utilizing a Geosynchronous Satellite in L-Band for Asia Pacific Satellite-to-Device Services | ASTRUM MOBILE PTE. LTD. |
| R4-2500214 | Way forward on 200MHz Channel Bandwidth | KDDI, China Unicom, China Telecom, BT, Bouygues Telecom, Deutsche Telekom, KPN, Vodafone, Orange, Odido, Telefonica, Telenor, TIM, Telia Company, Spark NZ, Reliance Jio, Telstra, NTT Docomo, Ericsson, Huawei |
| R4-2500242 | Motivation paper for Rel-20 RRM phase 6 WI | Apple |
| R4-2500324 | Motivation and proposal on UL Tx switching for FR1 intra-band NC UL CA in Rel-20 | Apple |
| R4-2500325 | New WID on enhanced low NR band carrier aggregation via switching | Apple |
| R4-2500326 | Views on further enhancement of TRP TRS in Rel-20 | Apple |
| R4-2500327 | Views on enabling 29dBm high-power UE for the FDD bands for terrestrial and satellite operation in Rel-20 | Apple |
| R4-2501079 | New WID on Introduction of NR TDD 4.9GHz Band for US Operation\t | Fujitsu Limited |
| R4-2501349 | 5G Broadcast Utilizing a Geosynchronous Satellite in L-Band for Asia Pacific Satellite-to-Device Services | ASTRUM MOBILE PTE. LTD. |
| R4-2501376 | 5G Broadcast Utilizing a Geosynchronous Satellite in L-Band for Asia Pacific Satellite-to-Device Services | ASTRUM MOBILE PTE. LTD. |
| R4-2501556 | Motivation on simplification of CA band combination | Huawei, HiSilicon |
| R4-2501625 | MediaTek Views on RAN4 Rel-20 5G-A | MediaTek Inc., |
| R4-2501800 | discussion on non-zero switching time for SUL and NUL | OPPO |
| R4-2501866 | Enhancement of low NR band carrier aggregation via switching | TELUS, Bell Mobility, Apple, AT&T, Murata, BT |
| R4-2501882 | Views on Rel-20 RAN4-led topics | ZTE Corporation, Sanechips |
| R4-2501904 | Views on RAN4 Rel-20 5G-Advanced topics | Intel Corporation |
| R4-2501971 | Views on Rel-20 RAN4-led 5G-A scope | Samsung |
| R4-2502138 | Views on Rel-20 RAN4-led topics | Huawei, HiSilicon |
| R4-2502861 | Initial view on Rel-20 RAN4 centric 5G-A proposal | Xiaomi |
| R4-2502869 | New band for 5G Broadcast Utilizing Geosynchronous Satellite | ASTRUM MOBILE PTE. LTD. |
| TDoc | Title | Source |
|---|---|---|
| R4-2502381 | (reserved) | BDaT Session |
| R4-2502382 | (reserved) | BDaT Session |
| R4-2502383 | (reserved) | BDaT Session |
| R4-2502384 | (reserved) | BDaT Session |
| R4-2502385 | (reserved) | BDaT Session |
| R4-2502386 | (reserved) | BDaT Session |
| R4-2502387 | (reserved) | BDaT Session |
| R4-2502388 | (reserved) | BDaT Session |
| R4-2502389 | (reserved) | BDaT Session |
| R4-2502390 | (reserved) | BDaT Session |
| R4-2502391 | (reserved) | BDaT Session |
| R4-2502392 | (reserved) | BDaT Session |
| R4-2502393 | (reserved) | BDaT Session |
| R4-2502394 | (reserved) | BDaT Session |
| R4-2502395 | (reserved) | BDaT Session |
| R4-2502396 | (reserved) | BDaT Session |
| R4-2502397 | (reserved) | BDaT Session |
| R4-2502398 | (reserved) | BDaT Session |
| R4-2502399 | (reserved) | BDaT Session |
| R4-2502400 | (reserved) | BDaT Session |
| R4-2502401 | (reserved) | BDaT Session |
| R4-2502402 | (reserved) | BDaT Session |
| R4-2502403 | (reserved) | BDaT Session |
| R4-2502404 | (reserved) | BDaT Session |
| R4-2502405 | (reserved) | BDaT Session |
| R4-2502406 | (reserved) | BDaT Session |
| R4-2502407 | (reserved) | BDaT Session |
| R4-2502408 | (reserved) | BDaT Session |
| R4-2502409 | (reserved) | BDaT Session |
| R4-2502410 | (reserved) | BDaT Session |
| R4-2502411 | (reserved) | BDaT Session |
| R4-2502412 | (reserved) | BDaT Session |
| R4-2502413 | (reserved) | BDaT Session |
| R4-2502414 | (reserved) | BDaT Session |
| R4-2502415 | (reserved) | BDaT Session |
| R4-2502416 | (reserved) | BDaT Session |
| R4-2502417 | (reserved) | BDaT Session |
| R4-2502418 | (reserved) | BDaT Session |
| R4-2502419 | (reserved) | BDaT Session |
| R4-2502420 | (reserved) | BDaT Session |
| R4-2502421 | (reserved) | BDaT Session |
| R4-2502422 | (reserved) | BDaT Session |
| R4-2502423 | (reserved) | BDaT Session |
| R4-2502424 | (reserved) | BDaT Session |
| R4-2502425 | (reserved) | BDaT Session |
| R4-2502426 | (reserved) | BDaT Session |
| R4-2502427 | (reserved) | BDaT Session |
| R4-2502428 | (reserved) | BDaT Session |
| R4-2502429 | (reserved) | BDaT Session |
| R4-2502430 | (reserved) | BDaT Session |
| R4-2502431 | (reserved) | BDaT Session |
| R4-2502432 | (reserved) | BDaT Session |
| R4-2502433 | (reserved) | BDaT Session |
| R4-2502434 | (reserved) | BDaT Session |
| R4-2502435 | (reserved) | BDaT Session |
| R4-2502436 | (reserved) | BDaT Session |
| R4-2502437 | (reserved) | BDaT Session |
| R4-2502438 | (reserved) | BDaT Session |
| R4-2502439 | (reserved) | BDaT Session |
| R4-2502440 | (reserved) | BDaT Session |
| R4-2502441 | (reserved) | BDaT Session |
| R4-2502442 | (reserved) | BDaT Session |
| R4-2502443 | (reserved) | BDaT Session |
| R4-2502444 | (reserved) | BDaT Session |
| R4-2502445 | (reserved) | BDaT Session |
| R4-2502446 | (reserved) | BDaT Session |
| R4-2502447 | (reserved) | BDaT Session |
| R4-2502448 | (reserved) | BDaT Session |
| R4-2502449 | (reserved) | BDaT Session |
| R4-2502450 | (reserved) | BDaT Session |
| R4-2502451 | (reserved) | BDaT Session |
| R4-2502452 | (reserved) | BDaT Session |
| R4-2502453 | (reserved) | BDaT Session |
| R4-2502454 | (reserved) | BDaT Session |
| R4-2502455 | (reserved) | BDaT Session |
| R4-2502456 | (reserved) | BDaT Session |
| R4-2502457 | (reserved) | BDaT Session |
| R4-2502458 | (reserved) | BDaT Session |
| R4-2502459 | (reserved) | BDaT Session |
| R4-2502460 | (reserved) | BDaT Session |
| R4-2502461 | (reserved) | BDaT Session |
| R4-2502462 | (reserved) | BDaT Session |
| R4-2502463 | (reserved) | BDaT Session |
| R4-2502464 | (reserved) | BDaT Session |
| R4-2502465 | (reserved) | BDaT Session |
| R4-2502466 | (reserved) | BDaT Session |
| R4-2502467 | (reserved) | BDaT Session |
| R4-2502468 | (reserved) | BDaT Session |
| R4-2502469 | (reserved) | BDaT Session |
| R4-2502470 | (reserved) | BDaT Session |
| R4-2502471 | (reserved) | BDaT Session |
| R4-2502472 | (reserved) | BDaT Session |
| R4-2502473 | (reserved) | BDaT Session |
| R4-2502474 | (reserved) | BDaT Session |
| R4-2502475 | (reserved) | BDaT Session |
| R4-2502476 | (reserved) | BDaT Session |
| R4-2502477 | (reserved) | BDaT Session |
| R4-2502478 | (reserved) | BDaT Session |
| R4-2502479 | (reserved) | BDaT Session |
| R4-2502480 | (reserved) | BDaT Session |
| R4-2502481 | (reserved) | BDaT Session |
| R4-2502482 | (reserved) | BDaT Session |
| R4-2502483 | (reserved) | BDaT Session |
| R4-2502484 | (reserved) | BDaT Session |
| R4-2502485 | (reserved) | BDaT Session |
| R4-2502486 | (reserved) | BDaT Session |
| R4-2502487 | (reserved) | BDaT Session |
| R4-2502488 | (reserved) | BDaT Session |
| R4-2502489 | (reserved) | BDaT Session |
| R4-2502490 | (reserved) | BDaT Session |
| R4-2502491 | (reserved) | BDaT Session |
| R4-2502492 | (reserved) | BDaT Session |
| R4-2502493 | (reserved) | BDaT Session |
| R4-2502494 | (reserved) | BDaT Session |
| R4-2502495 | (reserved) | BDaT Session |
| R4-2502496 | (reserved) | BDaT Session |
| R4-2502497 | (reserved) | BDaT Session |
| R4-2502498 | (reserved) | BDaT Session |
| R4-2502499 | (reserved) | BDaT Session |
| R4-2502500 | (reserved) | BDaT Session |
| R4-2502501 | (reserved) | BDaT Session |
| R4-2502502 | (reserved) | BDaT Session |
| R4-2502503 | (reserved) | BDaT Session |
| R4-2502504 | (reserved) | BDaT Session |
| R4-2502505 | (reserved) | BDaT Session |
| R4-2502506 | (reserved) | BDaT Session |
| R4-2502507 | (reserved) | BDaT Session |
| R4-2502508 | (reserved) | BDaT Session |
| R4-2502509 | (reserved) | BDaT Session |
| R4-2502510 | (reserved) | BDaT Session |
| R4-2502511 | (reserved) | BDaT Session |
| R4-2502512 | (reserved) | BDaT Session |
| R4-2502513 | (reserved) | BDaT Session |
| R4-2502514 | (reserved) | BDaT Session |
| R4-2502515 | (reserved) | BDaT Session |
| R4-2502516 | (reserved) | BDaT Session |
| R4-2502517 | (reserved) | BDaT Session |
| R4-2502518 | (reserved) | BDaT Session |
| R4-2502519 | (reserved) | BDaT Session |
| R4-2502520 | (reserved) | BDaT Session |
| R4-2502521 | (reserved) | BDaT Session |
| R4-2502522 | (reserved) | BDaT Session |
| R4-2502523 | (reserved) | BDaT Session |
| R4-2502524 | (reserved) | BDaT Session |
| R4-2502525 | (reserved) | BDaT Session |
| R4-2502526 | (reserved) | BDaT Session |
| R4-2502527 | (reserved) | BDaT Session |
| R4-2502528 | (reserved) | BDaT Session |
| R4-2502530 | (reserved) | BDaT Session |
| R4-2502531 | (reserved) | BDaT Session |
| R4-2502532 | (reserved) | BDaT Session |
| R4-2502533 | (reserved) | BDaT Session |
| R4-2502534 | (reserved) | BDaT Session |
| R4-2502535 | (reserved) | BDaT Session |
| R4-2502536 | (reserved) | BDaT Session |
| R4-2502537 | (reserved) | BDaT Session |
| R4-2502538 | (reserved) | BDaT Session |
| R4-2502539 | (reserved) | BDaT Session |
| R4-2502540 | (reserved) | BDaT Session |
| R4-2502541 | (reserved) | BDaT Session |
| R4-2502542 | (reserved) | BDaT Session |
| R4-2502543 | (reserved) | BDaT Session |
| R4-2502544 | (reserved) | BDaT Session |
| R4-2502545 | (reserved) | BDaT Session |
| R4-2502546 | (reserved) | BDaT Session |
| R4-2502547 | (reserved) | BDaT Session |
| R4-2502548 | (reserved) | BDaT Session |
| R4-2502549 | (reserved) | BDaT Session |
| R4-2502550 | (reserved) | BDaT Session |
| R4-2502551 | (reserved) | BDaT Session |
| R4-2502552 | (reserved) | BDaT Session |
| R4-2502553 | (reserved) | BDaT Session |
| R4-2502554 | (reserved) | BDaT Session |
| R4-2502555 | (reserved) | BDaT Session |
| R4-2502556 | (reserved) | BDaT Session |
| R4-2502557 | (reserved) | BDaT Session |
| R4-2502558 | (reserved) | BDaT Session |
| R4-2502559 | (reserved) | BDaT Session |
| R4-2502560 | (reserved) | BDaT Session |
| R4-2502561 | (reserved) | BDaT Session |
| R4-2502562 | (reserved) | BDaT Session |
| R4-2502563 | (reserved) | BDaT Session |
| R4-2502564 | (reserved) | BDaT Session |
| R4-2502565 | (reserved) | BDaT Session |
| R4-2502566 | (reserved) | BDaT Session |
| R4-2502567 | (reserved) | BDaT Session |
| R4-2502568 | (reserved) | BDaT Session |
| R4-2502569 | (reserved) | BDaT Session |
| R4-2502570 | (reserved) | BDaT Session |
| R4-2502571 | (reserved) | BDaT Session |
| TDoc | Title | Source |
|---|---|---|
| R4-2502702 | (reserved) | RRM Session |
| R4-2502703 | (reserved) | RRM Session |
| R4-2502704 | (reserved) | RRM Session |
| R4-2502705 | (reserved) | RRM Session |
| R4-2502706 | (reserved) | RRM Session |
| R4-2502707 | (reserved) | RRM Session |
| R4-2502708 | (reserved) | RRM Session |
| R4-2502709 | (reserved) | RRM Session |
| R4-2502710 | (reserved) | RRM Session |
| R4-2502711 | (reserved) | RRM Session |
| R4-2502712 | (reserved) | RRM Session |
| R4-2502713 | (reserved) | RRM Session |
| R4-2502714 | (reserved) | RRM Session |
| R4-2502715 | (reserved) | RRM Session |
| R4-2502716 | (reserved) | RRM Session |
| R4-2502717 | (reserved) | RRM Session |
| R4-2502718 | (reserved) | RRM Session |
| R4-2502719 | (reserved) | RRM Session |
| R4-2502720 | (reserved) | RRM Session |
| R4-2502721 | (reserved) | RRM Session |
| R4-2502722 | (reserved) | RRM Session |
| R4-2502723 | (reserved) | RRM Session |
| R4-2502724 | (reserved) | RRM Session |
| R4-2502725 | (reserved) | RRM Session |
| R4-2502726 | (reserved) | RRM Session |
| R4-2502727 | (reserved) | RRM Session |
| R4-2502728 | (reserved) | RRM Session |
| R4-2502729 | (reserved) | RRM Session |
| R4-2502730 | (reserved) | RRM Session |
| R4-2502731 | (reserved) | RRM Session |
| R4-2502732 | (reserved) | RRM Session |
| R4-2502733 | (reserved) | RRM Session |
| R4-2502734 | (reserved) | RRM Session |
| R4-2502735 | (reserved) | RRM Session |
| R4-2502736 | (reserved) | RRM Session |
| R4-2502737 | (reserved) | RRM Session |
| R4-2502738 | (reserved) | RRM Session |
| R4-2502739 | (reserved) | RRM Session |
| R4-2502740 | (reserved) | RRM Session |
| R4-2502741 | (reserved) | RRM Session |
| R4-2502742 | (reserved) | RRM Session |
| R4-2502743 | (reserved) | RRM Session |
| R4-2502744 | (reserved) | RRM Session |
| R4-2502745 | (reserved) | RRM Session |
| R4-2502746 | (reserved) | RRM Session |
| R4-2502747 | (reserved) | RRM Session |
| R4-2502748 | (reserved) | RRM Session |
| R4-2502749 | (reserved) | RRM Session |
| R4-2502750 | (reserved) | RRM Session |
| R4-2502751 | (reserved) | RRM Session |
| R4-2502752 | (reserved) | RRM Session |
| R4-2502753 | (reserved) | RRM Session |
| R4-2502754 | (reserved) | RRM Session |
| R4-2502755 | (reserved) | RRM Session |
| R4-2502756 | (reserved) | RRM Session |
| R4-2502757 | (reserved) | RRM Session |
| R4-2502758 | (reserved) | RRM Session |
| R4-2502759 | (reserved) | RRM Session |
| R4-2502760 | (reserved) | RRM Session |
| R4-2502761 | (reserved) | RRM Session |
| R4-2502762 | (reserved) | RRM Session |
| R4-2502763 | (reserved) | RRM Session |
| R4-2502764 | (reserved) | RRM Session |
| R4-2502765 | (reserved) | RRM Session |
| R4-2502766 | (reserved) | RRM Session |
| R4-2502767 | (reserved) | RRM Session |
| R4-2502768 | (reserved) | RRM Session |
| R4-2502769 | (reserved) | RRM Session |
| R4-2502770 | (reserved) | RRM Session |
| R4-2502771 | (reserved) | RRM Session |
| R4-2502772 | (reserved) | RRM Session |
| R4-2502773 | (reserved) | RRM Session |
| R4-2502774 | (reserved) | RRM Session |
| R4-2502775 | (reserved) | RRM Session |
| R4-2502776 | (reserved) | RRM Session |
| R4-2502777 | (reserved) | RRM Session |
| R4-2502778 | (reserved) | RRM Session |
| R4-2502779 | (reserved) | RRM Session |
| R4-2502780 | (reserved) | RRM Session |
| R4-2502781 | (reserved) | RRM Session |
| R4-2502782 | (reserved) | RRM Session |
| R4-2502783 | (reserved) | RRM Session |
| R4-2502784 | (reserved) | RRM Session |
| R4-2502785 | (reserved) | RRM Session |
| R4-2502786 | (reserved) | RRM Session |
| R4-2502787 | (reserved) | RRM Session |
| R4-2502788 | (reserved) | RRM Session |
| R4-2502789 | (reserved) | RRM Session |
| R4-2502790 | (reserved) | RRM Session |
| R4-2502791 | (reserved) | RRM Session |
| R4-2502792 | (reserved) | RRM Session |
| R4-2502793 | (reserved) | RRM Session |
| R4-2502794 | (reserved) | RRM Session |
| R4-2502795 | (reserved) | RRM Session |
| R4-2502796 | (reserved) | RRM Session |
| R4-2502797 | (reserved) | RRM Session |
| R4-2502798 | (reserved) | RRM Session |
| R4-2502799 | (reserved) | RRM Session |
| R4-2502800 | (reserved) | RRM Session |
| R4-2502801 | (reserved) | RRM Session |
| R4-2502802 | (reserved) | RRM Session |
| R4-2502803 | (reserved) | RRM Session |
| R4-2502804 | (reserved) | RRM Session |
| R4-2502805 | (reserved) | RRM Session |
| R4-2502806 | (reserved) | RRM Session |
| R4-2502807 | (reserved) | RRM Session |
| R4-2502808 | (reserved) | RRM Session |
| R4-2502809 | (reserved) | RRM Session |
| R4-2502810 | (reserved) | RRM Session |
| R4-2502811 | (reserved) | RRM Session |
| R4-2502812 | (reserved) | RRM Session |
| R4-2502813 | (reserved) | RRM Session |
| R4-2502814 | (reserved) | RRM Session |
| R4-2502815 | (reserved) | RRM Session |
| R4-2502816 | (reserved) | RRM Session |
| R4-2502817 | (reserved) | RRM Session |
| R4-2502818 | (reserved) | RRM Session |
| R4-2502819 | (reserved) | RRM Session |
| R4-2502820 | (reserved) | RRM Session |
| R4-2502821 | (reserved) | RRM Session |
| R4-2502822 | (reserved) | RRM Session |
| R4-2503040 | (reserved) | Main Session |
| R4-2503041 | (reserved) | Main Session |
| R4-2503042 | (reserved) | Main Session |
| R4-2503043 | (reserved) | Main Session |
| R4-2503044 | (reserved) | Main Session |
| R4-2503045 | (reserved) | Main Session |
| R4-2503046 | (reserved) | Main Session |
| R4-2503047 | (reserved) | Main Session |
| R4-2503048 | (reserved) | Main Session |
| R4-2503049 | (reserved) | Main Session |
| R4-2503050 | (reserved) | Main Session |
| R4-2503051 | (reserved) | Main Session |
| R4-2503052 | (reserved) | Main Session |
| R4-2503053 | (reserved) | Main Session |
| R4-2503054 | (reserved) | Main Session |
| R4-2503055 | (reserved) | Main Session |
| R4-2503056 | (reserved) | Main Session |
| R4-2503057 | (reserved) | Main Session |
| R4-2503058 | (reserved) | Main Session |
| R4-2503059 | (reserved) | Main Session |
| R4-2503060 | (reserved) | Main Session |
| R4-2503061 | (reserved) | Main Session |
| R4-2503062 | (reserved) | Main Session |
| R4-2503063 | (reserved) | Main Session |
| R4-2503064 | (reserved) | Main Session |
| R4-2503065 | (reserved) | Main Session |
| R4-2503066 | (reserved) | Main Session |
| R4-2503067 | (reserved) | Main Session |
| R4-2503068 | (reserved) | Main Session |
| R4-2503069 | (reserved) | Main Session |
| R4-2503070 | (reserved) | Main Session |
| R4-2503071 | (reserved) | Main Session |
| R4-2503072 | (reserved) | Main Session |
| R4-2503073 | (reserved) | Main Session |
| R4-2503074 | (reserved) | Main Session |
| R4-2503075 | (reserved) | Main Session |
| R4-2503076 | (reserved) | Main Session |
| R4-2503077 | (reserved) | Main Session |