TDoc | Title | Source |
---|---|---|
R4-2505300 | RAN4#114-bis Meeting Report | ETSI MCC |
R4-2505301 | Agenda for RAN4#115 | RAN4 Chair (Apple) |
R4-2505302 | RAN4#115 Meeting Arrangements and Guidelines | RAN4 Chair (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2505303 | LS on updated Rel-19 RAN1 UE features lists for NR after RAN1#120bis | RAN1, AT&T, NTT DOCOMO, INC. |
R4-2505304 | LS on initial Rel-19 RAN1 UE features lists for LTE after RAN1#120bis | RAN1, AT&T, NTT DOCOMO, INC. |
R4-2505305 | LS on requirements for the phase continuity and power consistency for OCC with PUSCH in NR NTN Ph3 | RAN1, MediaTek |
R4-2505306 | LS on impact on transmit signal quality/MPR requirement | RAN1, Huawei |
R4-2505307 | Reply LS on L1 measurement | RAN1, Huawei |
R4-2505308 | Reply to RAN4 LS on DL timing reference to support two TA enhancement for asymmetric DL sTRP/ UL mTRP | RAN1, OPPO |
R4-2505309 | LS on the RRM measurement metrics for OFDM-based LP-WUR | RAN1, Apple |
R4-2505310 | LS to RAN4 on time instance B for on-demand SSB SCell operation | RAN1, LG Electronics |
R4-2505311 | LS on precompensation for NB-IoT NTN TDD mode | RAN1, Qualcomm Incorporated |
R4-2505312 | LS on on-demand SSB | RAN2 |
R4-2505313 | LS on SMTC enhancements | RAN2 |
R4-2505314 | Reply LS on soft satellite switch with re-sync | RAN2 |
R4-2505315 | LS on Collision between MUSIM Gap and Measurement Gap | RAN2 |
R4-2505316 | LS on Rel-19 higher layer parameter and UE Feature | RAN2 |
R4-2505317 | LS on simultaneous configuration of SBFD and DC | RAN2 |
R4-2505318 | Reply LS on NR NB-IoT in-band operation | RAN2 |
R4-2505319 | Reply LS on Signalling for 7 MHz Channel Bandwidth | RAN2 |
R4-2505320 | LS on Rel-19 higher layers parameters list Post RAN1#120bis | RAN1, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506275 | (NR_CADC_R17_2BDL_xBUL)Rel-17 CR for TS 38.101-1 to Correct the RB number for CA_n2-n48 PC3 harmonic | Samsung, Skyworks |
R4-2507065 | Discussion UL/DL bandwidths for overlapping NR SUL and NR bands | Qualcomm France |
R4-2507066 | CR on clarification of UL/DL bandwitdhs on overlapping NR SUL and NR bands | Qualcomm France |
R4-2507067 | CR on clarification of UL/DL bandwitdhs on overlapping NR SUL and NR bands | Qualcomm France |
R4-2507068 | CR on clarification of UL/DL bandwitdhs on overlapping NR SUL and NR bands | Qualcomm France |
R4-2507540 | Topic summary for [115][101] Upto_R16_UERF_maintenance | Moderator (OPPO) |
R4-2507541 | Topic summary for [115][102] R17_UERF_maintenance | Moderator (Mediatek) |
TDoc | Title | Source |
---|---|---|
R4-2505550 | Topic summary for [115][201] Maintenance_up_to_R16 | Moderator (Xiaomi) |
R4-2505551 | Topic summary for [115][202] Maintenance_R17 | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2507833 | Topic summary for [115][301] BSRF_Maintenance_TEI | Moderator (Ericsson) |
R4-2507851 | Topic summary for [115][319] Demod_Maintenance_TEI_Part1 | Moderator (Nokia) |
R4-2507852 | Topic summary for [115][320] Demod_Maintenance_TEI_Part2 | Moderator (Apple) |
R4-2507868 | Topic summary for [115][336] OTA_Maintenance_TEI | Moderator (Keysight) |
TDoc | Title | Source |
---|---|---|
R4-2505373 | On test mode references in core requirements | Qualcomm Incorporated |
R4-2505431 | (NR_newRAT-Core) On NS_05 reevaluation | Apple |
R4-2505626 | (NR_newRAT-Core) CR to correct the Band 41 BW used for the DC_5A_41A_n78A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2505627 | (DC_R16_2BLTE_1BNR_3DL2UL) CR to correct the Band 41 BW used for the DC_5A_41A_n79A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2505628 | (DC_R16_2BLTE_1BNR_3DL2UL) CR to correct the Band 41 BW used for the DC_5A_41A_n79A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2505629 | (DC_R16_2BLTE_1BNR_3DL2UL) CR to correct the Band 41 BW used for the DC_5A_41A_n79A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2505630 | (DC_R16_2BLTE_1BNR_3DL2UL) CR to correct the Band 41 BW used for the DC_5A_41A_n79A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2505645 | (NR_unlic-Core) CR to correct the frequency offset of the interferer used in clause 7.5F.1 - TS38.101-1 | Anritsu Limited |
R4-2505646 | (NR_unlic-Core) CR to correct the frequency offset of the interferer used in clause 7.5F.1 - TS38.101-1 | Anritsu Limited |
R4-2505647 | (NR_unlic-Core) CR to correct the frequency offset of the interferer used in clause 7.5F.1 - TS38.101-1 | Anritsu Limited |
R4-2505648 | (NR_unlic-Core) CR to correct the frequency offset of the interferer used in clause 7.5F.1 - TS38.101-1 | Anritsu Limited |
R4-2505892 | (NR_newRAT-Core) CR on adding beam locked mode for some TX requirements | Apple |
R4-2506067 | (NR_NewRAT-Core) CR to TS 38.101-1 on transmitter general statements (Rel-15) | CATT |
R4-2506068 | (NR_NewRAT-Core) CR to TS 38.101-1 on transmitter general statements (Rel-16) | CATT |
R4-2506069 | (NR_NewRAT-Core) CR to TS 38.101-1 on transmitter general statements (Rel-17) | CATT |
R4-2506070 | (NR_NewRAT-Core) CR to TS 38.101-1 on transmitter general statements (Rel-18) | CATT |
R4-2506071 | (NR_NewRAT-Core) CR to TS 38.101-1 on transmitter general statements (Rel-19) | CATT |
R4-2506141 | CR to TS 38.101-1 - Correction to A-MPR for CA_NS_04 (Rel-16) | Qualcomm Technologies |
R4-2506160 | n1 PHS, splitting A2 for PUCCH benefit | Qualcomm Incorporated |
R4-2506175 | (DC_R16_2BLTE_1BNR_3DL2UL) CR to correct the Band 41 BW used for the DC_5A_41A_n79A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2506218 | (NR_CLI_RIM-Perf) 38.133CR on R16 CLI measurement accuracy requirement | Nokia, Nokia Shanghai Bell |
R4-2506219 | (NR_CLI_RIM-Perf) 38.133CR on R16 CLI measurement accuracy requirement - R17 | Nokia, Nokia Shanghai Bell |
R4-2506220 | (NR_CLI_RIM-Perf) 38.133CR on R16 CLI measurement accuracy requirement - R18 Cat.A | Nokia, Nokia Shanghai Bell |
R4-2506221 | (NR_CLI_RIM-Perf) 38.133CR on R16 CLI measurement accuracy requirement - R19 Cat.A | Nokia, Nokia Shanghai Bell |
R4-2506517 | n1 NS_05 A-MPR proposals | Nokia |
R4-2506924 | R16 n1 NS_05U PC2 AMPR | OPPO |
R4-2506925 | R16 n1 NS_05 PC2 AMPR | OPPO |
R4-2506929 | (NR_newRAT-Core) WF on NR A-MPR reevaluation scenarios on n1 for Japan | KDDI Corporation |
R4-2506982 | (LTE_CA_R15_2DL2UL-Core) Add some missing uplink CA band configurations in TS36.101 | MediaTek Korea Inc. |
R4-2506985 | (LTE_CA_R15_2DL2UL-Core) Add some missing uplink CA band configurations in TS36.101 | MediaTek Korea Inc. |
R4-2506987 | (LTE_CA_R15_2DL2UL-Core) Add some missing uplink CA band configurations in TS36.101 | MediaTek Korea Inc. |
R4-2506988 | (LTE_CA_R15_2DL2UL-Core) Add some missing uplink CA band configurations in TS36.101 | MediaTek Korea Inc. |
R4-2506989 | (LTE_CA_R15_2DL2UL-Core) Add some missing uplink CA band configurations in TS36.101 | MediaTek Korea Inc. |
R4-2507006 | Discussion on modifiedMPR-behaviour for n1 | NTT DOCOMO INC. |
R4-2507226 | A-MPR regions for NS_05/NS_05U [NR_newRAT-Core] | Ericsson |
R4-2507260 | (NR_newRAT-Core) Discussion on EESS protection from n260 | NTT DOCOMO INC., SoftBank Corp., Rakuten Mobile, Inc. |
R4-2507402 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on single UL allowed for two bands EN-DC configurations | ZTE Corporation, Sanechips |
R4-2507403 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on single UL allowed for two bands EN-DC configurations_R17_CAT_A | ZTE Corporation, Sanechips |
R4-2507404 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on single UL allowed for two bands EN-DC configurations_R18_CAT_A | ZTE Corporation, Sanechips |
R4-2507405 | (DC_R16_1BLTE_1BNR_2DL2UL-Core) Corrections on single UL allowed for two bands EN-DC configurations_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507676 | [NR_newRAT-Core] CR to TS38.101-1-gn0: Correction to harmonic mixing MSD - CatF | Skyworks Solutions Inc., Anritsu, Qualcomm France |
R4-2507686 | [NR_CADC_R17_2BDL_xBUL-Core] CR to TS38.101-1-hh0: Correction to harmonic mixing MSD - CatF | Skyworks Solutions, Inc., Anritsu, Qualcomm France. |
R4-2507688 | [NR_CADC_R18_2BDL_xBUL-Core] CR to TS38.101-1-i90: Correction to harmonic mixing MSD - CatF | Skyworks Solutions, Inc., Anritsu, Qualcomm France. |
R4-2507689 | [NR_CADC_R18_2BDL_xBUL-Core] CR to TS38.101-1-j10: Correction and missing harmonic mixing MSD - CatA | Skyworks Solutions Inc., Anritsu, Qualcomm France |
R4-2507690 | [LTE_CA_R16_intra-Core] CR to TS36.101-gn0: Clarification of PC2 CA_NS_04 requirements - CatF | Skyworks Solutions, Inc. |
R4-2507691 | [LTE_CA_R16_intra-Core] CR to TS36.101-hg0: Clarification of PC2 CA_NS_04 requirements - CatA | Skyworks Solutions Inc. |
R4-2507692 | [LTE_CA_R16_intra-Core] CR to TS36.101-i90: Clarification of PC2 CA_NS_04 requirements - CatA | Skyworks Solutions Inc. |
R4-2507694 | [LTE_CA_R16_intra-Core] CR to TS36.101-j10: Clarification of PC2 CA_NS_04 requirements - CatA | Skyworks Solutions Inc. |
R4-2507723 | (PHS_System_NRonly) On the requirements of modifiedMPR-Behavior | Huawei, HiSilicon |
R4-2507743 | CR to TS 38.101-1 - Correction to A-MPR for CA_NS_04 (Rel-17) | Qualcomm Technologies |
R4-2507745 | CR to TS 38.101-1 - Correction to A-MPR for CA_NS_04 (Rel-18) | Qualcomm Technologies |
R4-2507746 | CR to TS 38.101-1 - Correction to A-MPR for CA_NS_04 (Rel-19) | Qualcomm Technologies |
R4-2507892 | [NR_newRAT-Core] CR to TS38.101-1-gn0: Correction to harmonic mixing MSD - CatF | Skyworks Solutions Inc., Anritsu, Qulacomm France |
R4-2507897 | (NR_newRAT-Core) CR to correct the Band 41 BW used for the DC_5A_41A_n78A MSD in clause 7.3B.2.3.5.2 according to CA_5A-41A - TS38.101-3 | Anritsu Limited |
R4-2507906 | CR to TS 38.101-1 - Correction to A-MPR for CA_NS_04 (Rel-16) | Qualcomm Technologies |
TDoc | Title | Source |
---|---|---|
R4-2505335 | (NR_CADC_R17_3BDL_2BUL-Core)CR to 38.101-1: Correction on CA_n28-n40-n78 (Rel-17) | Huawei, Hisilicon |
R4-2505336 | (NR_CADC_R17_3BDL_2BUL-Core)CR to 38.101-1: Correction on CA_n28-n40-n78 (Rel-18) | Huawei, Hisilicon |
R4-2505337 | (NR_CADC_R17_3BDL_2BUL-Core)CR to 38.101-1: Correction on CA_n28-n40-n78 (Rel-19) | Huawei, Hisilicon |
R4-2505346 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-17) | Union Inter. Chemins de Fer, Ericsson |
R4-2505347 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-18) | Union Inter. Chemins de Fer, Ericsson |
R4-2505348 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-19) | Union Inter. Chemins de Fer, Ericsson |
R4-2505391 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-17) | Union Inter. Chemins de Fer, Ericsson |
R4-2505392 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-18) | Union Inter. Chemins de Fer, Ericsson |
R4-2505393 | (NR_RAIL_EU_900MHz-Core, NR_RAIL_EU_1900MHz_TDD-Core) CR to TS 38.101-1: Correction to mapping of network signalling table (Rel-19) | Union Inter. Chemins de Fer, Ericsson |
R4-2505442 | CR to TR 38.862 on notation rule corrections for NR CA with one SUL carrier | Apple |
R4-2505443 | Corrections on RedCap UE PC3 FDD band 1Rx REFSENS | Apple, Skyworks Solutions Inc. |
R4-2505444 | CR to 38.101-1 on corrections for RedCap UE PC3 FDD band 1Rx REFSENS | Apple, Skyworks Solutions Inc. |
R4-2505445 | CR to 38.101-1 on corrections for RedCap UE PC3 FDD band 1Rx REFSENS | Apple, Skyworks Solutions Inc. |
R4-2505446 | CR to 38.101-1 on corrections for RedCap UE PC3 FDD band 1Rx REFSENS | Apple, Skyworks Solutions Inc. |
R4-2505480 | (NR_NTN_solutions-Core) CR to TS 38.101-5 n256 REFSENS (Rel-17) | MediaTek (Hefei) Inc. |
R4-2505623 | (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, Huawei, HiSilicon |
R4-2505624 | (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 |
R4-2505625 | (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 |
R4-2505633 | (NR_CADC_R17_2BDL_xBUL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-1 | Anritsu Limited |
R4-2505634 | (NR_CADC_R17_2BDL_xBUL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-1 | Anritsu Limited |
R4-2505635 | (NR_CADC_R17_2BDL_xBUL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-1 | Anritsu Limited |
R4-2505636 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-3 | Anritsu Limited |
R4-2505637 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-3 | Anritsu Limited |
R4-2505638 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) CR to clarify the applicable SCS when UE testing in clause 7.3A.1 - TS 38.101-3 | Anritsu Limited |
R4-2505642 | (NR_NTN_solutions-Core) CR to add active uplink slot and RMC for RF tests of FR1-NTN | Anritsu Limited |
R4-2505643 | (NR_NTN_solutions-Core) CR to add active uplink slot and RMC for RF tests of FR1-NTN | Anritsu Limited |
R4-2505644 | (NR_NTN_solutions-Core) CR to add active uplink slot and RMC for RF tests of FR1-NTN | Anritsu Limited |
R4-2505650 | Discussion on RB allocation in test cases for reference sensitivity for CA | Anritsu Limited |
R4-2505680 | CR 38.101-1 R17 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
R4-2505681 | CR 38.101-1 R18 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
R4-2505682 | CR 38.101-1 R19 Correction for ModifiedMPR table [Modified_MPR] | Nokia |
R4-2505757 | Discussion on ModifiedMPR-Behavior and spec | Xiaomi |
R4-2505893 | Power control ambiguity issue for PC1.5 UEs | Apple |
R4-2506046 | CR for TR 38.863,correction on tolerance for UE Transmission characteristics for satellite access | CATT |
R4-2506186 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
R4-2506187 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
R4-2506188 | (NR_RF_TxD-Core) Reference measurement channels for SRS transmissions | Ericsson |
R4-2507161 | (NR_NTN_solutions-Core) CR to add active uplink slot and RMC for RF tests of FR1-NTN | Anritsu Limited |
R4-2507327 | R17 CR for 38.101-5 to modify the REFSENs Table 7.3.2-1 | OPPO |
R4-2507328 | R18 CR for 38.101-5 to modify the REFSENs Table 7.3.2-1 | OPPO |
R4-2507329 | R19 CR for 38.101-5 to modify the REFSENs Table 7.3.2-1 | OPPO |
R4-2507406 | (NR_ext_to_71GHz-Core) Addition of missing network signalling label for NS_204 | ZTE Corporation, Sanechips |
R4-2507407 | (NR_ext_to_71GHz-Core) Addition of missing network signalling label for NS_204_R18_CAT_A | ZTE Corporation, Sanechips |
R4-2507408 | (NR_ext_to_71GHz-Core) Addition of missing network signalling label for NS_204_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507409 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Corrections on multiple entries for EN-DC configuration MSD test points | ZTE Corporation, Sanechips |
R4-2507410 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Corrections on multiple entries for EN-DC configuration MSD test points_R18_CAT_A | ZTE Corporation, Sanechips |
R4-2507411 | (DC_R17_1BLTE_1BNR_2DL2UL-Core) Corrections on multiple entries for EN-DC configuration MSD test points_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507435 | CR for TR 38.863, Correction on UE Transmission characteristics for satellite access | CATT |
R4-2507754 | CR to TS 38.101-1: RMC for PC2 FDD | Qualcomm Incorporated |
R4-2507755 | CR to TS 38.101-1: RMC for PC2 FDD | Qualcomm Incorporated |
R4-2507756 | CR to TS 38.101-1: RMC for PC2 FDD | Qualcomm Incorporated |
R4-2507776 | CR to TS 38.101-1: HPUE for Uplink Tx Switching with switchedUL | Lenovo, T-Mobile USA, Ericsson |
R4-2507777 | CR to TS 38.101-1: HPUE for Uplink Tx Switching with switchedUL | Lenovo, T-Mobile USA, Ericsson |
R4-2507778 | CR to TS 38.101-1: HPUE for Uplink Tx Switching with switchedUL | Lenovo, T-Mobile USA, Ericsson |
R4-2507790 | CR to TS 38.101-1: HPUE for Uplink Tx Switching with switchedUL | Lenovo, T-Mobile USA, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506045 | CR for TR 38.863,correction on tolerance for UE Transmission characteristics for satellite access | CATT |
R4-2506078 | (NR_IAB-Core)CR for 38.174, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506079 | (NR_IAB-Core)CR for 38.174, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506080 | (NR_IAB-Core)CR for 38.174, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506081 | (NR_IAB-Core)CR for 38.174, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506082 | (NR_IAB-Perf)CR for 38.176-1, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506083 | (NR_IAB-Perf)CR for 38.176-1, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506084 | (NR_IAB-Perf)CR for 38.176-1, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506085 | (NR_IAB-Perf)CR for 38.176-1, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506086 | (NR_IAB-Perf)CR for 38.176-2, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506087 | (NR_IAB-Perf)CR for 38.176-2, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506088 | (NR_IAB-Perf)CR for 38.176-2, Correction on out-of-band blocking co-location requirement | CATT |
R4-2506089 | (NR_IAB-Perf)CR for 38.176-2, Correction on out-of-band blocking co-location requirement | CATT |
R4-2507074 | (AAS_BS_LTE_UTRA-Core) CR to TR 37.842 on correction of table reference | Nokia |
R4-2507075 | (NR_newRAT-Core) CR to TR 38.817-02 on clarification on resource block size for receiver intermodulation requirements | Nokia |
R4-2507088 | (NR_newRAT-Core) CR to 37.104: Correction of co-existence and co-location requirements | Ericsson |
R4-2507089 | (NR_newRAT-Perf) CR to 37.141: Correction of co-existence and co-location requirements | Ericsson |
R4-2507096 | Discussion on introducing additional EESS protection requirement for BS | NTT DOCOMO, INC, SoftBank Corp., Rakuten |
R4-2507236 | CR to 38.174 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507237 | CR to 38.174 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507238 | CR to 38.174 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507239 | CR to 38.174 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507240 | CR to 38.176-1 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507241 | CR to 38.176-1 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507242 | CR to 38.176-1 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507243 | CR to 38.176-1 with clarification for channel bandwidths below 10 MHz | Nokia |
R4-2507443 | (NR_newRAT-Core) CR to TR 38.817-02: correction of the interferer bandwidth derivation for the ICS requirements | Huawei, HiSilicon |
R4-2507452 | (NR_newRAT-Core) CR to TS 38.104: correction of OTA Tx IMD wanted signal characteristics | Huawei, HiSilicon |
R4-2507453 | (NR_newRAT-Core) CR to TS 38.104: correction of OTA Tx IMD wanted signal characteristics | Huawei, HiSilicon |
R4-2507454 | (NR_newRAT-Core) CR to TS 38.104: correction of OTA Tx IMD wanted signal characteristics | Huawei, HiSilicon |
R4-2507455 | (NR_newRAT-Core) CR to TS 38.104: correction of OTA Tx IMD wanted signal characteristics | Huawei, HiSilicon |
R4-2507456 | (NR_newRAT-Core) CR to TS 38.104: correction of OTA Tx IMD wanted signal characteristics | Huawei, HiSilicon |
R4-2507457 | (NR_repeaters-Perf) CR to TS 38.115-2: Correction of the OTA input intermodulation test requirement | Huawei, HiSilicon |
R4-2507458 | (NR_repeaters-Perf) CR to TS 38.115-2: Correction of the OTA input intermodulation test requirement | Huawei, HiSilicon |
R4-2507459 | (NR_repeaters-Perf) CR to TS 38.115-2: Removal of TRP annex | Huawei, HiSilicon |
R4-2507460 | (NR_repeaters-Perf) CR to TS 38.115-2: Removal of TRP annex | Huawei, HiSilicon |
R4-2507461 | (NR_repeaters-Perf) CR to TS 38.115-2: spec quality and consistency improvements | Huawei, HiSilicon |
R4-2507462 | (NR_repeaters-Perf) CR to TS 38.115-2: spec quality and consistency improvements | Huawei, HiSilicon |
R4-2507463 | (AAS_BS_LTE_UTRA-Perf) CR to TS 37.145-2: removal of outstanding FFS | Huawei, HiSilicon |
R4-2507464 | (AAS_BS_LTE_UTRA-Perf) CR to TS 37.145-2: removal of outstanding FFS | Huawei, HiSilicon |
R4-2507465 | (AAS_BS_LTE_UTRA-Perf) CR to TS 37.145-2: removal of outstanding FFS | Huawei, HiSilicon |
R4-2507466 | (AAS_BS_LTE_UTRA-Perf) CR to TS 37.145-2: removal of outstanding FFS | Huawei, HiSilicon |
R4-2507467 | (AAS_BS_LTE_UTRA-Perf) CR to TS 37.145-2: removal of outstanding FFS | Huawei, HiSilicon |
R4-2507614 | (NR_newRAT-Perf) CR for correction on the unit of OTA ACLR (Rel-15) | NTT DOCOMO, INC. |
R4-2507615 | (NR_newRAT-Perf) CR for correction on the unit of OTA ACLR (Rel-16) | NTT DOCOMO, INC. |
R4-2507616 | (NR_newRAT-Perf) CR for correction on the unit of OTA ACLR (Rel-17) | NTT DOCOMO, INC. |
R4-2507617 | (NR_newRAT-Perf) CR for correction on the unit of OTA ACLR (Rel-18) | NTT DOCOMO, INC. |
R4-2507618 | (NR_newRAT-Perf) CR for correction on the unit of OTA ACLR (Rel-19) | NTT DOCOMO, INC. |
R4-2507874 | [37.941] Incorrect MU data for n104 band | ROHDE & SCHWARZ |
R4-2507881 | [37.941] Incorrect MU data for n104 band | ROHDE & SCHWARZ |
R4-2507883 | [38.141-2] Incorrect MU data for n104 band | ROHDE & SCHWARZ |
R4-2507889 | [38.141-2] Incorrect MU data for n104 band | ROHDE & SCHWARZ |
R4-2507890 | [38.141-2] Incorrect MU data for n104 band | ROHDE & SCHWARZ |
TDoc | Title | Source |
---|---|---|
R4-2505349 | (NR_RRM_enh-Core) On Timing Adjustment for Carrier Aggregation and Dual Connectivity | Qualcomm Technologies Ireland |
R4-2505607 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 16) | Rohde & Schwarz |
R4-2505608 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 17) | Rohde & Schwarz |
R4-2505609 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 18) | Rohde & Schwarz |
R4-2505612 | (NR_pos-Perf) CR to TS 38.133: Corrections to NR Positioning test cases (Rel 19) | Rohde & Schwarz |
R4-2505827 | (NR_RRM_Enh-Perf)Correction to CGI measurement test case | Samsung |
R4-2505828 | (NR_RRM_Enh-Perf)Correction to CGI measurement test case | Samsung |
R4-2505829 | (NR_RRM_Enh-Perf)Correction to CGI measurement test case | Samsung |
R4-2505830 | (NR_RRM_Enh-Perf)Correction to CGI measurement test case | Samsung |
R4-2505881 | (NR_RRM_Enh-Perf) CR for SA intra-frequency CGI identification of NR neighbor cell in FR1 - R16 | Apple |
R4-2505882 | (NR_RRM_Enh-Perf) CR for SA intra-frequency CGI identification of NR neighbor cell in FR1 - R17 | Apple |
R4-2505883 | (NR_RRM_Enh-Perf) CR for SA intra-frequency CGI identification of NR neighbor cell in FR1 - R18 | Apple |
R4-2505884 | (NR_RRM_Enh-Perf) CR for SA intra-frequency CGI identification of NR neighbor cell in FR1 - R19 | Apple |
R4-2505894 | (NR_newRAT-core) On UE handling of TX timing larger than MTTD for CA and DC | Apple |
R4-2505895 | (NR_newRAT-core) CR to 38.133 for Gradual Timing Adjustment and MTTD-R15 | Apple |
R4-2505896 | (NR_newRAT-core) CR to 38.133 for Gradual Timing Adjustment and MTTD-R16 | Apple |
R4-2505897 | (NR_newRAT-core) CR to 38.133 for Gradual Timing Adjustment and MTTD-R17 | Apple |
R4-2505898 | (NR_newRAT-core) CR to 38.133 for Gradual Timing Adjustment and MTTD-R18 | Apple |
R4-2505915 | CR for RRC based BWP switching | Apple |
R4-2505916 | CR for RRC based BWP switching for R16 | Apple |
R4-2505917 | CR for RRC based BWP switching for R17 | Apple |
R4-2505918 | CR for RRC based BWP switching for R18 | Apple |
R4-2505919 | CR for RRC based BWP switching for R19 | Apple |
R4-2505920 | CR for UE timing requirement for first Tx after quitting dormant BWP | Apple |
R4-2505921 | CR for UE timing requirement for first Tx after quitting dormant BWP for R17 | Apple |
R4-2505922 | CR for UE timing requirement for first Tx after quitting dormant BWP for R18 | Apple |
R4-2505923 | CR for UE timing requirement for first Tx after quitting dormant BWP for R19 | Apple |
R4-2506620 | CR on measurement period for CCA | CMCC |
R4-2506621 | CR on measurement period for CCA | CMCC |
R4-2506622 | CR on measurement period for CCA | CMCC |
R4-2506623 | CR on measurement period for CCA | CMCC |
R4-2506686 | (NR_2step_RACH-Perf) Correction to 2-step RACH RMCs_R16 | Huawei, HiSilicon, Starpoint |
R4-2506687 | (NR_2step_RACH-Perf) Correction to 2-step RACH RMCs_R17 | Huawei, HiSilicon,Starpoint |
R4-2506688 | (NR_2step_RACH-Perf) Correction to 2-step RACH RMCs_R18 | Huawei, HiSilicon,Starpoint |
R4-2506689 | (NR_2step_RACH-Perf) Correction to 2-step RACH RMCs_R19 | Huawei, HiSilicon,Starpoint |
R4-2506690 | (NR_unlic-Perf) Correction to NR-U 2-step RACH RMCs_R16 | Huawei, HiSilicon |
R4-2506691 | (NR_unlic-Perf) Correction to NR-U 2-step RACH RMCs_R17 | Huawei, HiSilicon |
R4-2506692 | (NR_unlic-Perf) Correction to NR-U 2-step RACH RMCs_R18 | Huawei, HiSilicon |
R4-2506693 | (NR_unlic-Perf) Correction to NR-U 2-step RACH RMCs_R19 | Huawei, HiSilicon |
R4-2506748 | (NR_eMIMO-Perf) CR on L1-SINR performance requirements | Huawei, HiSilicon |
R4-2506749 | (NR_eMIMO-Perf) CR on L1-SINR performance requirements R17 | Huawei, HiSilicon |
R4-2506750 | (NR_eMIMO-Perf) CR on L1-SINR performance requirements R18 | Huawei, HiSilicon |
R4-2506751 | (NR_eMIMO-Perf) CR on L1-SINR performance requirements R19 | Huawei, HiSilicon |
R4-2506809 | (NR_newRAT-Perf, NR_eMIMO-Perf, NR_CSIRS_L3meas-Perf) CR on maintenance for measurement procedure tests R16 | Huawei, HiSilicon |
R4-2506810 | (NR_newRAT-Perf, NR_eMIMO-Perf, NR_CSIRS_L3meas-Perf) CR on maintenance for measurement procedure tests R17 | Huawei, HiSilicon |
R4-2506811 | (NR_newRAT-Perf, NR_eMIMO-Perf, NR_CSIRS_L3meas-Perf) CR on maintenance for measurement procedure tests R18 | Huawei, HiSilicon |
R4-2506812 | (NR_newRAT-Perf, NR_eMIMO-Perf, NR_CSIRS_L3meas-Perf) CR on maintenance for measurement procedure tests R19 | Huawei, HiSilicon |
R4-2506816 | (NR_unlic-Perf) CR on maintenance for band group notations in measurement performance tests R16 | Huawei, HiSilicon |
R4-2506817 | (NR_unlic-Perf) CR on maintenance for band group notations in measurement performance tests R17 | Huawei, HiSilicon |
R4-2506818 | (NR_unlic-Perf) CR on maintenance for band group notations in measurement performance tests R18 | Huawei, HiSilicon |
R4-2506819 | (NR_unlic-Perf) CR on maintenance for band group notations in measurement performance tests R19 | Huawei, HiSilicon |
R4-2506898 | Clarification on mandatory gap patterns in Rel-16 | Ericsson |
R4-2507274 | CR clarifying the UE UL transmit timing requirements | Nokia |
R4-2507275 | CR clarifying the UE UL transmit timing requirements | Nokia |
R4-2507276 | CR clarifying the UE UL transmit timing requirements | Nokia |
R4-2507277 | CR clarifying the UE UL transmit timing requirements | Nokia |
R4-2507278 | CR clarifying the UE UL transmit timing requirements | Nokia |
R4-2507311 | (NR_newRAT-Perf) Correction to CSI-RS based L1-RSRP test case_R15 | ZTE Corporation, Sanechips |
R4-2507312 | (NR_newRAT-Perf) Correction to CSI-RS based L1-RSRP test case_R16 | ZTE Corporation, Sanechips |
R4-2507313 | (NR_newRAT-Perf) Correction to CSI-RS based L1-RSRP test case_R17 | ZTE Corporation, Sanechips |
R4-2507314 | (NR_newRAT-Perf) Correction to CSI-RS based L1-RSRP test case_R18 | ZTE Corporation, Sanechips |
R4-2507315 | (NR_newRAT-Perf) Correction to CSI-RS based L1-RSRP test case_R19 | ZTE Corporation, Sanechips |
R4-2507474 | 38.133 CR on R16 CLI measurement accuracy requirement | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2505610 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 17) | Rohde & Schwarz |
R4-2505611 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 18) | Rohde & Schwarz |
R4-2505613 | (NR_pos_enh-Perf) CR to TS 38.133: Corrections to NR Enhanced Positioning test cases (Rel 19) | Rohde & Schwarz |
R4-2505683 | CR on Link Recovery Procedures for NTN | OPPO |
R4-2505684 | CR on Link Recovery Procedures for NTN | OPPO |
R4-2505685 | CR on Link Recovery Procedures for NTN | OPPO |
R4-2506091 | (NR_NTN_solutions-Core) CR on NR NTN core requirements of (Rel-17) | CATT |
R4-2506092 | (NR_NTN_solutions-Core) CR on NR NTN core requirements of (Rel-18) | CATT |
R4-2506403 | (NR_redcap-Core) CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
R4-2506404 | (NR_redcap-Core) CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
R4-2506405 | (NR_redcap-Core) CR to TS 38.133 Correction of scheduling availability for HD-FDD Redcap UE | CMCC |
R4-2506513 | (LTE_NR_DC_enh2-Core) Discussion on the usage of TCI-ActivatedConfig for SCell activation | MediaTek Inc. |
R4-2506514 | (LTE_NR_DC_enh2-Core) CR on Scell activation delay requirements with TCI-ActivatedConfig | MediaTek Inc. |
R4-2506515 | (LTE_NR_DC_enh2-Core) CR on Scell activation delay requirements with TCI-ActivatedConfig | MediaTek Inc. |
R4-2506516 | (LTE_NR_DC_enh2-Core) CR on Scell activation delay requirements with TCI-ActivatedConfig | MediaTek Inc. |
R4-2506559 | CR for correction on test cases on Handover with PSCell change | vivo, Nokia, Nokia Shanghai Bell |
R4-2506560 | CR for correction on test cases on Handover with PSCell change | vivo |
R4-2506561 | CR for correction on test cases on Handover with PSCell change | vivo |
R4-2506716 | (NR_RRM_enh2-Core) CR on core maintenance for PUCCH Scell activation R17 | Huawei, HiSilicon |
R4-2506717 | (NR_RRM_enh2-Core) CR on core maintenance for PUCCH Scell activation R18 (cat A) | Huawei, HiSilicon |
R4-2506718 | (NR_RRM_enh2-Core) CR on core maintenance for PUCCH Scell activation R19 (cat A) | Huawei, HiSilicon |
R4-2506719 | (NR_RRM_enh2-Perf) CR on TC maintenance for PUCCH Scell activation R17 | Huawei, HiSilicon |
R4-2506720 | (NR_RRM_enh2-Perf) CR on TC maintenance for PUCCH Scell activation R18 (cat A) | Huawei, HiSilicon |
R4-2506721 | (NR_RRM_enh2-Perf) CR on TC maintenance for PUCCH Scell activation R19 (cat A) | Huawei, HiSilicon |
R4-2506745 | (NR_redcap-Core) Correction on requirements for HD-FDD RedCap UE R17 | Huawei, HiSilicon |
R4-2506746 | (NR_redcap-Core) Correction on requirements for HD-FDD RedCap UE R18 | Huawei, HiSilicon |
R4-2506747 | (NR_redcap-Core) Correction on requirements for HD-FDD RedCap UE R19 | Huawei, HiSilicon |
R4-2506752 | (NR_SmallData_INACTIVE-Core) CR on CG-SDT requirements | Huawei, HiSilicon |
R4-2506753 | (NR_SmallData_INACTIVE-Core) CR on CG-SDT requirements R19 | Huawei, HiSilicon |
R4-2506754 | (NR_NTN_solutions-Core) CR on measurement requirements for NTN | Huawei, HiSilicon |
R4-2506755 | (NR_NTN_solutions-Core) CR on measurement requirements for NTN R18 | Huawei, HiSilicon |
R4-2506756 | (NR_NTN_solutions-Core) CR on measurement requirements for NTN R19 | Huawei, HiSilicon |
R4-2506757 | (NR_MG_enh-Core) CR on gap sharing for NCSG | Huawei, HiSilicon |
R4-2506758 | (NR_MG_enh-Core) CR on gap sharing for NCSG R18 | Huawei, HiSilicon |
R4-2506759 | (NR_MG_enh-Core) CR on gap sharing for NCSG R19 | Huawei, HiSilicon |
R4-2506813 | (NR_redcap-Perf) CR on maintenance for SA event triggered reporting with SSB time index detection R17 | Huawei, HiSilicon |
R4-2506814 | (NR_redcap-Perf) CR on maintenance for SA event triggered reporting with SSB time index detection R18 | Huawei, HiSilicon |
R4-2506815 | (NR_redcap-Perf) CR on maintenance for SA event triggered reporting with SSB time index detection R19 | Huawei, HiSilicon |
R4-2506820 | Core maintenance CR on HO with PSCell delay R17 | Intel Corporation |
R4-2506821 | Core maintenance CR on HO with PSCell delay R18 | Intel Corporation |
R4-2507208 | Modification on MDT requirements_R17 | ZTECorporation,Sanechips |
R4-2507209 | Modification on MDT requirements_R18 | ZTECorporation,Sanechips |
R4-2507210 | Modification on MDT requirements_R19 | ZTECorporation,Sanechips |
R4-2507213 | Modify NR operating bands for satellite access in FR1. | ZTECorporation,Sanechips |
R4-2507214 | Modify NR operating bands for satellite access in FR1. | ZTECorporation,Sanechips |
R4-2507215 | Modify NR operating bands for satellite access in FR1. | ZTECorporation,Sanechips |
R4-2507233 | (NR_NTN_solutions-Core) CR on NR NTN core requirements of (Rel-19) | CATT |
R4-2507270 | (NR_newRAT-Core) NR-E-UTRAN HO delay requirement maintenance | Nokia, Ericsson |
R4-2507271 | (NR_newRAT-Core) CR on NR-E-UTRAN HO delay requirement maintenance | Nokia, Ericsson |
R4-2507272 | (NR_newRAT-Core) CR on NR-E-UTRAN HO delay requirement maintenance | Nokia, Ericsson |
R4-2507273 | (NR_newRAT-Core) CR on NR-E-UTRAN HO delay requirement maintenance | Nokia, Ericsson |
R4-2507348 | Discussion on gap association | Nokia |
R4-2507349 | (NR_MG_enh-Core) CR38.133 Gap association for concurrent MGs, Pre-MG and NCSG | Nokia |
R4-2507350 | (NR_MG_enh-Core) CR38.133 Gap association for concurrent MGs, Pre-MG and NCSG | Nokia |
R4-2507351 | (NR_MG_enh-Core) CR38.133 Gap association for concurrent MGs, Pre-MG and NCSG | Nokia |
R4-2507644 | (NR_NTN_solutions-Perf) Correction to NR SA SS-RSRP measurement accuracy for Satellite Access | Keysight Technologies |
R4-2507646 | (NR_NTN_solutions-Perf) Correction to NR SA SS-RSRP measurement accuracy for Satellite Access (Rel18) | Keysight Technologies UK Ltd |
R4-2507792 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-F Rel-17) | Qualcomm Incorporated |
R4-2507793 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-A Rel-18) | Qualcomm Incorporated |
R4-2507794 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-A Rel-19) | Qualcomm Incorporated |
R4-2507795 | (NR_NTN_solutions-Perf) CR on NTN test cases for FR1 SAN (Cat-F Rel-17) | Qualcomm Incorporated |
R4-2507796 | (NR_NTN_solutions-Perf) CR on NTN test cases for FR1 SAN (Cat-A Rel-18) | Qualcomm Incorporated |
R4-2507797 | (NR_NTN_solutions-Perf) CR on NTN test cases for FR1 SAN (Cat-A Rel-19) | Qualcomm Incorporated |
R4-2507818 | (NR_RF_FR1_enh-Perf) CR on TC for DL interruptions at switching between uplink carriers in FDD-TDD CA (R17) | MediaTek inc. |
R4-2507882 | (NR_NTN_solutions-Core) CR on L1-RSRP accuracy requirements for FR1 SAN (Cat-A Rel-18) | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505375 | (NR_NTN_solutions-Perf) CR to 38.101-5 Rel-17 Cat-F for the Note in Table 8.2.1.1.2-1 | CAICT |
R4-2505376 | (NR_NTN_solutions-Perf) CR to 38.101-5 Rel-18 Cat-A for the Note in Table 8.2.1.1.2-1 | CAICT |
R4-2505377 | (NR_NTN_solutions-Perf) CR to 38.101-5 Rel-19 Cat-A for the Note in Table 8.2.1.1.2-1 | CAICT |
R4-2505466 | (NR_newRAT-Perf) CR for TS38.101-4, correction to CSI-RS configurations for CQI requirements | MediaTek inc. |
R4-2505481 | Discussion on aperiodic ZP CSI scheduling for 16Tx and 32Tx PMI requirements | Rohde & Schwarz |
R4-2505482 | (NR_eMIMO-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505483 | (NR_eMIMO-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505484 | (NR_eMIMO-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505485 | (NR_perf_enh-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505486 | (NR_perf_enh-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505487 | (NR_perf_enh-Perf) Correction to ZP CSI configuration for PMI requirements | Rohde & Schwarz |
R4-2505488 | (NR_redcap-Perf) Correction to 1Rx static propagation conditions | Rohde & Schwarz |
R4-2505489 | (NR_redcap-Perf) Correction to 1Rx static propagation conditions | Rohde & Schwarz |
R4-2505490 | (NR_NTN_solutions-Perf) Correction to 1Rx static propagation conditions | Rohde & Schwarz |
R4-2505491 | (NR_NTN_solutions-Perf) Correction to 1Rx static propagation conditions | Rohde & Schwarz |
R4-2505492 | (NR_NTN_solutions-Perf) Correction to 1Rx static propagation conditions | Rohde & Schwarz |
R4-2505899 | (NR_newRAT-perf) CR to 38.101-4 for PT-RS Config - R15 | Apple |
R4-2506445 | (NR_HST_FR2_enh-Perf) CR on 38.101-4 for correcting FRC Table | Nokia |
R4-2506635 | (NR_unlic-Perf) CR to 38.104: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506636 | (NR_unlic-Perf) CR to 38.104: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506637 | (NR_unlic-Perf) CR to 38.104: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506638 | (NR_unlic-Perf) CR to 38.104: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506639 | (NR_unlic-Perf) CR to 38.141-1: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506640 | (NR_unlic-Perf) CR to 38.141-1: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506641 | (NR_unlic-Perf) CR to 38.141-1: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506642 | (NR_unlic-Perf) CR to 38.141-1: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506643 | (NR_unlic-Perf) CR to 38.141-2: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506644 | (NR_unlic-Perf) CR to 38.141-2: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506645 | (NR_unlic-Perf) CR to 38.141-2: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506646 | (NR_unlic-Perf) CR to 38.141-2: Correction to FRC parameters for FR1 interlaced PUSCH performance requirements | Ericsson |
R4-2506647 | (NR_HST_FR1_enh-Perf) CR to 38.104: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506648 | (NR_HST_FR1_enh-Perf) CR to 38.104: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506649 | (NR_HST_FR1_enh-Perf) CR to 38.104: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506650 | (NR_HST_FR1_enh-Perf) CR to 38.141-1: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506651 | (NR_HST_FR1_enh-Perf) CR to 38.141-1: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506652 | (NR_HST_FR1_enh-Perf) CR to 38.141-1: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506653 | (NR_HST_FR1_enh-Perf) CR to 38.141-2: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506654 | (NR_HST_FR1_enh-Perf) CR to 38.141-2: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506655 | (NR_HST_FR1_enh-Perf) CR to 38.141-2: Correction to FRC parameters for HST FR1 PUSCH performance requirements | Ericsson |
R4-2506656 | (NR_ext_to_71GHz-Perf) CR to 38.104: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2506657 | (NR_ext_to_71GHz-Perf) CR to 38.104: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2506658 | (NR_ext_to_71GHz-Perf) CR to 38.104: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2506659 | (NR_ext_to_71GHz-Perf) CR to 38.141-2: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2506660 | (NR_ext_to_71GHz-Perf) CR to 38.141-2: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2506661 | (NR_ext_to_71GHz-Perf) CR to 38.141-2: Correction to FRC parameters for FR2-2 PUSCH performance requirements with transform precoding enabled | Ericsson |
R4-2507342 | (NR_HST_FR2-Perf) CR on 38.101-4 for correcting FRC Table | Nokia |
R4-2507687 | (NR_newRAT-Perf) Correction on aggregation level and number of candidates for SDR test parameters | Keysight Technologies |
R4-2507693 | (NR_newRAT-Perf) Correction on aggregation level and number of candidates for SDR test parameters (Rel16) | Keysight Technologies UK Ltd |
R4-2507695 | (NR_newRAT-Perf) Correction on aggregation level and number of candidates for SDR test parameters (Rel17) | Keysight Technologies UK Ltd |
R4-2507696 | (NR_newRAT-Perf) Correction on aggregation level and number of candidates for SDR test parameters (Rel18) | Keysight Technologies UK Ltd |
R4-2507702 | (NR_perf_enh-Perf) Parameters update for PMI 16/32 Tx test case | Keysight Technologies |
R4-2507708 | (NR_perf_enh-Perf) Parameters update for PMI 16/32 Tx test case (Rel17) | Keysight Technologies UK Ltd |
R4-2507710 | (NR_perf_enh-Perf) Parameters update for PMI 16/32 Tx test case (Rel18) | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2505525 | (NR_ENDC_ RF_FR1_enh2) CR to TS 38.101-1 correction of 4Tx | Huawei, HiSilicon |
R4-2505526 | (TEI18) CR to TS 38.101-1 correction of 4Tx [RF_FR1_4Tx] | Huawei, HiSilicon |
R4-2505801 | (TEI18) CR on 38.101-1 clarifications on special sync rasters for n100 [Sync_raster_3MHz_n100] | Huawei, Hisilicon |
R4-2505808 | (TEI18) CR on 38.101-1 clarifications on special sync rasters for n100[Sync_raster_3MHz_n100] | Huawei, Hisilicon |
R4-2506199 | (TEI18) CR to 38.101-1 on adding asymmetric channel bandwidth for n70 UL15/DL10 [n70_asymBW] | Boost Mobile Network |
R4-2506200 | (TEI18) CR to 38.101-1 on adding asymmetric channel bandwidth for n70 UL15/DL10 [n70_asymBW] | Boost Mobile Network |
R4-2507542 | Topic summary for [115][103] R18_UERF_maintenance_Part1 | Moderator (Xiaomi) |
R4-2507543 | Topic summary for [115][104] R18_UERF_maintenance_Part2 | Moderator (Huawei) |
R4-2507613 | (TEI18) CR to TS 38.101-1 correction of 4Tx [RF_FR1_4Tx] | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505552 | Topic summary for [115][203] Maintenance_R18_R19 | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2505333 | (NR_CADC_R18_3BDL_xBUL-Core) CR to 38.101-1: Correction on CA_n28-n40-n77 (Rel-18) | Huawei, Hisilicon |
R4-2505334 | (NR_CADC_R18_3BDL_xBUL-Core) CR to 38.101-1: Correction on CA_n28-n40-n77 (Rel-19) | Huawei, Hisilicon |
R4-2505405 | (NR_NTN_LSband-Core) Additional power back-off simulation results | Nokia, Apple |
R4-2505406 | (NR_NTN_LSband-Core) Removal of 256QAM entries from band n254 A-MPR tables | Apple, Globalstar |
R4-2505407 | Clarification for the PSD limits for a UE operating in 1610-1626.5 MHz frequency range | Apple, Globalstar |
R4-2505408 | (NR_NTN_LSband-Core) Additional information on the international regulations and WRC provisions for a UE operating in 1610-1626.5 MHz frequency range | Apple, Globalstar |
R4-2505409 | (NR_NTN_LSband-Core) Clarification for the PSD limits for a UE operating in 1610-1626.5 MHz frequency range | Apple, Globalstar |
R4-2505410 | (NR_NTN_LSband-Core) Clarification for the PSD limits for a UE operating in 1610-1626.5 MHz frequency range | Apple, Globalstar |
R4-2505411 | (IoT_NTN_FDD_LS_band-Core) Clarification for the PSD limits for a UE operating in 1610-1626.5 MHz frequency range | Apple, Globalstar |
R4-2505412 | (IoT_NTN_FDD_LS_band-Core) Power back-off simulations for a UE operating in 1610-1626.5 MHz frequency range | Apple |
R4-2505467 | (HPUE_FR1_DC_LTE_NR_R18) CR for TS 38.101-3 to add the missing Note and correct the MSD values for DC_18A_n77A in Rel-18 | KDDI, Samsung, LGE, Murata, Skyworks |
R4-2505539 | (DC_R18_xBLTE_2BNR_yDL2UL-Core) CR for TS 38.101-3 to modify some errors for DC_1A-3A-20A_n8A-n78A | Huawei, HiSilicon, DT |
R4-2505540 | (DC_R18_xBLTE_2BNR_yDL2UL-Core) CR for TS 38.101-3 to modify some errors for DC_1A-3A-20A_n8A-n78A | Huawei, HiSilicon, DT |
R4-2505639 | (NR_CADC_R17_2BDL_xBUL-Core) CR to correct Band n40 DL Fc used in the configuration for CA_n40-n77 cross band isolation MSD requirements in clause 7.3A.6 - TS38.101-1 | Anritsu Limited |
R4-2505640 | (NR_CADC_R17_2BDL_xBUL-Core) CR to correct Band n40 DL Fc used in the configuration for CA_n40-n77 cross band isolation MSD requirements in clause 7.3A.6 - TS38.101-1 | Anritsu Limited |
R4-2505641 | (NR_CADC_R17_2BDL_xBUL-Core) CR to correct Band n40 DL Fc used in the configuration for CA_n40-n77 cross band isolation MSD requirements in clause 7.3A.6 - TS38.101-1 | Anritsu Limited |
R4-2506174 | On completing band 254 requirements | Qualcomm Incorporated |
R4-2506276 | (NR_CADC_R18_2BDL_xBUL)Rel-18 CR for TS 38.101-1 to Correct the RB number for CA_n2-n48 PC3 harmonic | Samsung, Skyworks |
R4-2506277 | (NR_CADC_R18_2BDL_xBUL)Rel-19 CR for TS 38.101-1 to Correct the RB number for CA_n2-n48 PC3 harmonic | Samsung, Skyworks |
R4-2506319 | (LTE410_Europe_PPDR-Core)CR to Rel-18 TS38.106 to correct NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2506320 | (LTE410_Europe_PPDR-Core)CR to Rel-19 TS38.106 to add missing LTE bands 87 and 88 | ZTE Corporation, Sanechips |
R4-2506387 | (HPUE_FR1_TDD_NR_CADC_SUL_R18) CR for 38.101-1 Correct the NOTE for HPUE harmonic/harmonic mixing MSD | ZTE Corporation,Sanechips |
R4-2506388 | (HPUE_FR1_TDD_NR_CADC_SUL_R18) CR for 38.101-1 Correct the NOTE for HPUE harmonic/harmonic mixing MSD | ZTE Corporation,Sanechips |
R4-2506389 | ( 4Rx_low_NR_band_handheld_3Tx_NR_CA_ENDC)CR for 38.101-3 adding the missing NOTE for 3Tx DC_40A_n78A | ZTE Corporation, Sanechips |
R4-2506390 | (4Rx_low_NR_band_handheld_3Tx_NR_CA_ENDC)CR for 38.101-3 adding the missing NOTE for 3Tx DC_40A_n78A | ZTE Corporation, Sanechips |
R4-2506624 | Release independence of SDO bands for 5G broadcast | EBU |
R4-2507341 | (HPUE_FR1_DC_LTE_NR_R19-Core) CR for TS 38.101-3 to add the missing Note and correct the MSD values for DC_18A_n77A in Rel-19 | KDDI, Samsung, LGE, Murata, Skyworks |
R4-2507412 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on BCS denotation for two bands CA configurations | ZTE Corporation, Sanechips |
R4-2507413 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on BCS denotation for two bands CA configurations_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507414 | (NR_CADC_R18_3BDL_xBUL-Core)_Corrections on BCS denotation for three bands CA configurations | ZTE Corporation, Sanechips |
R4-2507415 | (NR_CADC_R18_3BDL_xBUL-Core)_Corrections on BCS denotation for three bands CA configurations_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507416 | (NR_CADC_R18_yBDL_xBUL-Core)_Corrections on BCS denotation for four and five bands CA configurations | ZTE Corporation, Sanechips |
R4-2507417 | (NR_CADC_R18_yBDL_xBUL-Core)_Corrections on BCS denotation for four and five bands CA configurations_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507418 | (DC_R18_1BLTE_1BNR_2DL2UL-Core) Corrections on band n66 DL test frequency for DC_30A_n66A | ZTE Corporation, Sanechips |
R4-2507419 | (DC_R18_1BLTE_1BNR_2DL2UL-Core) Corrections on band n66 DL test frequency for DC_30A_n66A_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507420 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on two bands CA configurations | ZTE Corporation, Sanechips |
R4-2507421 | (NR_CADC_R18_2BDL_xBUL-Core) Corrections on two bands CA configurations_R19_CAT_A | ZTE Corporation, Sanechips |
R4-2507449 | (LTE_terr_bcast_bands_part2-Core) CR to TS 36.101: terminology alignment for the "LTE based 5G terrestrial broadcast" feature | Huawei, HiSilicon |
R4-2507450 | (LTE_terr_bcast_bands_part2-Core) CR to TS 36.101: terminology alignment for the "LTE based 5G terrestrial broadcast" feature | Huawei, HiSilicon |
R4-2507472 | Release independence of SDO bands for 5G broadcast | EBU, BNE |
R4-2507612 | (HPUE_DC_LTE_NR_R19) CR for TS 38.101-3 to add the missing Note and correct the MSD values for DC_18A_n77A in Rel-19 | KDDI, Samsung, LGE, Murata, Skyworks |
R4-2507643 | (IoT_NTN_FDD_LS_band) CR to TS 36.102 for addressing incomplete B254 requirements (Rel-18) | MediaTek (Hefei) Inc. |
R4-2507757 | CR to TS 38.101-1:Removal of 3 MHz CBW from CA in Rel-18 | Qualcomm Incorporated |
R4-2507758 | CR to TS 38.101-1:Removal of 3 MHz CBW from CA in Rel-18 | Qualcomm Incorporated |
R4-2507905 | CR to TS 38.101-1:Removal of 3 MHz CBW from CA in Rel-18 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506057 | CR to TS 38.104 on sync raster correction for band n110 | CATT |
R4-2506058 | CR to TS 38.101-1 on sync raster correction for band n110 | CATT |
R4-2507884 | Discussion on introduction of FR2 PC8 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505958 | CR to TS 38.101-1 - Correction of A-MPR tables for band n68 | Qualcomm Technologies |
TDoc | Title | Source |
---|---|---|
R4-2505676 | CR 38.101-1 Some editorials and corrections for CA configurations | Nokia |
R4-2507069 | Handling of Optional bandwidths across releases | Qualcomm France |
R4-2507070 | MSD considerations related to handling of Optional bandwidths across releases | Qualcomm France |
TDoc | Title | Source |
---|---|---|
R4-2506385 | (NonCol_intraB_ENDC_NR_CA) CR for 38.101-1 Correct the NOTE for non-collocated CA | ZTE Corporation, Nokia, Samsung |
R4-2506386 | (NonCol_intraB_ENDC_NR_CA) CR for 38.101-1 Correct the NOTE for non-collocated CA | ZTE Corporation, Nokia, Samsung |
R4-2507173 | ( NonCol_intraB_ENDC_NR_CA) CR for 38.101-1 Correct the NOTE for non-collocated CA | ZTE Corporation, Nokia, Samsung |
R4-2507174 | (NonCol_intraB_ENDC_NR_CA) CR for 38.101-1 Correct the NOTE for non-collocated CA | ZTE Corporation, Nokia, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2506364 | CR for TS 38.101-1 on ATG UE antenna connector clarification | CMCC |
R4-2506366 | Discussion on R18 ATG UE RF requirement applicability | CMCC |
R4-2507394 | (NR_ATG-Core) CR for 38.101-1 ATG UE transmit signal quality | Ericsson |
R4-2507734 | (NR_ATG-Core) Rel-18 Clarifications on some ATG requirements applicability per connector | Keysight Technologies UK Ltd |
R4-2507735 | (NR_ATG-Core) Rel-19 Clarifications on some ATG requirements applicability per connector | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2506090 | (NR_ATG-Core) CR to TS 38.133 on ATG core requirements (Rel-18) | CATT |
R4-2506406 | (NR_ATG-Core) CR to TS 38.133 Correction of L1 sharing factor for Inter-frequency measurements without measurement gaps for ATG UE | CMCC |
R4-2506407 | (NR_ATG-Core) CR to TS 38.133 Correction of L1 sharing factor for Inter-frequency measurements without measurement gaps for ATG UE | CMCC |
R4-2506408 | (NR_ATG-Perf) CR to TS 38.101-4 Correction on missing applicability for CSI requirements for ATG UE | CMCC |
R4-2506805 | (NR_ATG-Perf) CR on TC maintenance for Rel-18 ATG | Huawei, HiSilicon |
R4-2506806 | (NR_ATG-Perf) CR on TC maintenance for Rel-19 ATG | Huawei, HiSilicon |
R4-2507234 | (NR_ATG-Core) CR to TS 38.133 on ATG core requirements (Rel-19) | CATT |
R4-2507309 | (NR_ATG-Core) CR on CSI-RS based L3 measurements of ATG_R18 | ZTE Corporation, Sanechips |
R4-2507310 | (NR_ATG-Core) CR on CSI-RS based L3 measurements of ATG_R19 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2506829 | Delta Ppowerclass and Delta TRxSRS for 4Tx | Huawei, HiSilicon |
R4-2506830 | Introduction of Delta TRxSRS for 4Tx | Huawei, HiSilicon |
R4-2506831 | Introduction of Delta TRxSRS for 4Tx | Huawei, HiSilicon |
R4-2507713 | Capabilities for Delta PPowerClass for 4Tx SRS transmission | Qualcomm Technologies |
R4-2507736 | 4 Tx Delta PPowerClass for SRS antenna switching | Qualcomm Technologies |
R4-2507779 | (NR_ENDC_RF_FR1_enh2-Core) On DeltaP_PowerClass for SRS-AS for 4Tx | Ericsson |
R4-2507780 | (NR_ENDC_RF_FR1_enh2-Core) CR to 38.101 Rel-18: DeltaP_PowerClass correction for SRS-AS for 4Tx | Ericsson |
R4-2507781 | (NR_ENDC_RF_FR1_enh2-Core) CR to 38.101 Rel-19: DeltaP_PowerClass correction for SRS-AS for 4Tx | Ericsson |
R4-2507811 | (NR_ENDC_RF_FR1_enh2-Core) CR to 38.101 Rel-18: DeltaP_PowerClass correction for SRS-AS for 4Tx | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2507268 | CR for Rel-18 Less Than 5MHz Performance part | Nokia |
R4-2507269 | CR for Rel-18 Less Than 5MHz Performance part | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2507444 | Introduction of OTA requirements for network-nodes specifications for 3MHz channel bandwidth | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2506127 | CR to TS 38.133 on RMSI CORESET Reference Channel for FDD with SCS=15KHz for Less than 5MHz UEs | Nokia |
R4-2506128 | CR to TS 38.133 on RMSI CORESET Reference Channel for FDD with SCS=15KHz for Less than 5MHz UEs | Nokia |
R4-2506578 | CR to TS 38.133: NR channel BW less than 5MHz for FR1 | ZTE Corporation, Sanechips |
R4-2506579 | CR to TS 38.133: NR channel BW less than 5MHz for FR1 | ZTE Corporation, Sanechips |
R4-2506760 | CR on performance requirements for less than 5MHz BW | Huawei, HiSilicon |
R4-2506761 | CR on performance requirements for less than 5MHz BW R19 | Huawei, HiSilicon |
R4-2507224 | CR to TS 38.133 on Intra- and Inter-frquency identification for Less than 5MHz UEs | Nokia |
R4-2507225 | CR to TS 38.133 on Intra- and Inter-frquency identification for Less than 5MHz UEs | Nokia |
R4-2507330 | CR on PDSCH Reference Measurement Channels with NR FR1 lessthan 5MHz BW | Ericsson |
R4-2507331 | CR on PDSCH Reference Measurement Channels with NR FR1 lessthan 5MHz BW | Ericsson |
R4-2507332 | Discussion on RMC Configurations for Rel-18 NR less than 5 MHz | Ericsson |
R4-2507701 | CR on PDSCH Reference Measurement Channels with NR FR1 less than 5MHz BW | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505656 | (LTE_NBIoT_eMTC_NTN_req-Core) CR to TS 36.102 B256 OOB Note (Rel-18) | MediaTek (Hefei) Inc. |
R4-2506329 | Discussion on UE RF A-MPR for B254 | Nordic Semiconductor ASA |
R4-2506861 | CR on Remove GSM_ACLR for NB-Iot based Iot-NTN | vivo, Huawei, MediaTek |
R4-2507126 | AMPR value for NB-IoT in IoT NTN band b254 | Sony |
R4-2507422 | (LTE_NBIOT_eMTC_NTN_req-Core) Corrections on A-MPR requirements subclause for category M1 UE | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2506489 | CR on rsrp-ThresholdsPrachInfoList for IoT NTN test cases | MediaTek inc. |
R4-2506490 | CR on random access test case for IoT NTN test | MediaTek inc. |
R4-2506544 | CR on rsrp-ThresholdsPrachInfoList for IoT NTN test cases | MediaTek inc. |
R4-2506545 | CR on random access test case for IoT NTN test | MediaTek inc. |
R4-2506722 | CR on maintenance for Rel-18 IoT NTN R18 | Huawei, HiSilicon |
R4-2506723 | CR on maintenance for Rel-18 IoT NTN R19 (cat A) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505686 | CR on TRP specific Beam Failure Detection and Link Recovery for FR2 Pcell | OPPO |
R4-2505687 | CR on TRP specific Beam Failure Detection and Link Recovery for FR2 Pcell | OPPO, Qualcomm, Xiaomi |
R4-2505722 | CR for Multi-Rx test case maintenance | Nokia |
R4-2505723 | CR for Multi-Rx test case maintenance | Nokia |
R4-2506724 | CR on TC maintenance for R18 multi-Rx TCI R18 | Huawei, HiSilicon |
R4-2506725 | CR on TC maintenance for R18 multi-Rx TCI R19 (cat A) | Huawei, HiSilicon |
R4-2507008 | CR on maximum receive timing difference requirement for UE supporting multi-RX | CMCC |
R4-2507010 | CR on maximum receive timing difference requirement for UE supporting multi-RX | CMCC |
R4-2507898 | CR on TRP specific Beam Failure Detection and Link Recovery for FR2 Pcell | OPPO, Qualcomm, Xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2507307 | (NR_RRM_enh3-Core) Correction to the SCell activation with L3 report_R18 | ZTE Corporation, Sanechips |
R4-2507308 | (NR_RRM_enh3-Core) Correction to the SCell activation with L3 report_R19 | ZTE Corporation, Sanechips |
R4-2507537 | (NR_RRM_enh3-Core) Correction to the SCell activation with L3 report_R18 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2506696 | (NR_MG_enh2-Perf) Correction to inter-RAT NR measurement without gap test cases_R18 | Huawei, HiSilicon |
R4-2506697 | (NR_MG_enh2-Perf) Correction to inter-RAT NR measurement without gap test cases_R19 | Huawei, HiSilicon |
R4-2506698 | (NR_MG_enh2-Perf) Correction to Rel-18 concurrent gap with NCSG test cases_R18 | Huawei, HiSilicon |
R4-2506699 | (NR_MG_enh2-Perf) Correction to Rel-18 concurrent gap with NCSG test cases_R19 | Huawei, HiSilicon |
R4-2506700 | (NR_MG_enh2-Perf) Correction to Rel-18 concurrent gap with Pre-MG test cases_R18 | Huawei, HiSilicon |
R4-2506701 | (NR_MG_enh2-Perf) Correction to Rel-18 concurrent gap with Pre-MG test cases_R19 | Huawei, HiSilicon |
R4-2506762 | CR on CSSF for R18 MG enhancement | Huawei, HiSilicon |
R4-2506763 | CR on CSSF for R18 MG enhancement R19 | Huawei, HiSilicon |
R4-2507583 | (NR_MG_enh2-Core) CR on MGE2 R18 Core | MediaTek inc. |
R4-2507584 | (NR_MG_enh2-Core) CR on MGE2 R18 Core CAT A | MediaTek inc. |
R4-2507585 | (NR_MG_enh2-Perf) CR on MGE2 R18 Perf | MediaTek inc. |
R4-2507586 | (NR_MG_enh2-Perf) CR on MGE2 R18 Perf CAT A | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2506764 | CR on core requirements for BWP operation without restriction | Huawei, HiSilicon |
R4-2506765 | CR on core requirements for BWP operation without restriction R19 | Huawei, HiSilicon |
R4-2507265 | (NR_BWP_wor-Core) CR for correcting logical errors related to HO requirements | Nokia |
R4-2507266 | (NR_BWP_wor-Core) CR for correcting logical errors related to HO requirements | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2507347 | CR on Spectrum Analyser configuration | ROHDE & SCHWARZ, vivo |
R4-2507358 | CR on Spectrum Analyser configuration | ROHDE & SCHWARZ, vivo |
TDoc | Title | Source |
---|---|---|
R4-2506926 | (NR_MC_enh) R18 correction of switchig time between NUL and SUL carriers | OPPO |
R4-2506927 | (NR_MC_enh) R19 correction of switchig time between NUL and SUL carriers | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2506451 | CR on BWP switching requirements for multi-carrier enhancements | vivo |
R4-2506452 | CR on DCI based BWP switching requirements for multi-carrier enhancements | vivo |
R4-2506453 | Further discussion on UE capability and requirements for multi-carrier enhancements | vivo |
R4-2506897 | Discussion on multiple BWP switching with dormancy Scells | Ericsson |
R4-2507819 | (NR_MC_enh-Perf) CR on TC for DL interruptions at switching between uplink carriers in FDD-TDD CA (R18) | MediaTek inc. |
R4-2507820 | (NR_MC_enh-Perf) CR on TC for DL interruptions at switching between uplink carriers in FDD-TDD CA (R19) | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2506154 | (NR_NTN_enh-Core) CR to TS 38108 - Missing SAN type 2-O definition | Ericsson |
R4-2506155 | (NR_NTN_enh-Core) CR to TS 38108 - Missing SAN type 2-O definition | Ericsson |
R4-2506943 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues - Cat F CR | Qualcomm Incorporated, THALES, Ericsson |
R4-2506977 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues - Cat A CR | Qualcomm Incorporated, THALES, Ericsson |
R4-2507078 | (NR_NTN_enh-Perf) CR to TS 38.181 on corrections of notes in tables | Nokia |
R4-2507469 | (NR_NTN_enh-Core) CR for TS 38.101-5 to clarify Doppler shift issues - Cat F CR | Qualcomm Incorporated, THALES, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505924 | On R18 NTN RRM core and performance requirement maintenance | Apple |
R4-2505925 | CR on satellite switch delay for soft satellite switch with re-sync | Apple |
R4-2505926 | CR on satellite switch delay for soft satellite switch with re-sync for R19 | Apple |
R4-2506409 | (NR_NTN_enh-Core) CR to TS 38.133 Correction of inter-RAT E-UTRAN cells with TN carrier measurement for NTN UE | CMCC |
R4-2506410 | (NR_NTN_enh-Core) CR to TS 38.133 Correction of inter-RAT E-UTRAN cells with TN carrier measurement for NTN UE | CMCC |
R4-2506766 | CR on measurement requirements for FR2-NTN | Huawei, HiSilicon |
R4-2506767 | CR on measurement requirements for FR2-NTN R19 | Huawei, HiSilicon |
R4-2506768 | CR on measurement accuracy requirements for FR2-NTN | Huawei, HiSilicon |
R4-2506769 | CR on measurement accuracy requirements for FR2-NTN R19 | Huawei, HiSilicon |
R4-2507798 | (NR_NTN_enh-Perf) CR on NR NTN test cases (Cat-F Rel-18) | Qualcomm Incorporated |
R4-2507799 | (NR_NTN_enh-Perf) CR on NR NTN test cases (Cat-A Rel-19) | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506770 | CR on RRM requirements for SL positioning | Huawei, HiSilicon |
R4-2506771 | CR on RRM requirements for SL positioning R19 | Huawei, HiSilicon |
R4-2507655 | CR to 38.133 on corrections to general aspects of gapless positioning measurements and core requirements for RedCap positioning | Ericsson |
R4-2507656 | CR to 38.133 on corrections to general aspects of gapless positioning measurements and core requirements for RedCap positioning | Ericsson |
R4-2507657 | CR to 38.133 on corrections to core requirements for carrier phase measurement for positioning | Ericsson |
R4-2507658 | CR to 38.133 on corrections to core requirements for carrier phase measurement for positioning | Ericsson |
R4-2507768 | CR to 38.133 on corrections to general aspects of gapless positioning measurements and core requirements for RedCap positioning | Ericsson |
R4-2507769 | CR to 38.133 on corrections to core requirements for carrier phase measurement for positioning | Ericsson |
R4-2507770 | CR to 38.133 on corrections to general aspects of gapless positioning measurements and core requirements for RedCap positioning | Ericsson |
R4-2507771 | CR to 38.133 on corrections to core requirements for carrier phase measurement for positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506004 | CR for TS 38.133 to add UL RSCP reporting mapping requirement (Rel-18) | CATT |
R4-2506005 | CR for TS 38.133 to add UL RSCP reporting mapping requirement (Rel-19) | CATT |
R4-2506772 | CR on accuracy requirements for RedCap positioning | Huawei, HiSilicon |
R4-2506773 | CR on accuracy requirements for RedCap positioning R19 | Huawei, HiSilicon |
R4-2507659 | CR to 38.133 on corrections to performance requirement for UE Rx-Tx time difference measurements | Ericsson |
R4-2507660 | CR to 38.133 on corrections to performance requirement for UE Rx-Tx time difference measurements | Ericsson |
R4-2507661 | CR to 38.133 on corrections to performance requirement for carrier phase measurements for positioning | Ericsson |
R4-2507662 | CR to 38.133 on corrections to performance requirement for carrier phase measurements for positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505724 | CR for LTM L1 measurement requirement maintenance | Nokia |
R4-2505725 | CR for LTM L1 measurement requirement maintenance | Nokia |
R4-2506129 | Discussion on remaining issues of Rel-18 Mobility Enhancements core | Nokia |
R4-2506130 | CR to 38.133 on Rel-18 LTM PDCCH ordered RACH core requirements | Nokia |
R4-2506131 | CR to 38.133 on Rel-18 LTM PDCCH ordered RACH core requirements | Nokia |
R4-2506449 | CR on R18 LTM RRM performance requirements_perf | vivo |
R4-2506450 | CR on R18 LTM RRM performance requirements_perf | vivo |
R4-2506510 | Discussion on R18 mobility | MediaTek Inc. |
R4-2506511 | CR on R18 LTM Test Cases | MediaTek Inc. |
R4-2506512 | CR on R18 LTM Test Cases | MediaTek Inc. |
R4-2506566 | Discussion on Further NR mobility enhancements | ZTE Corporation, Sanechips |
R4-2506573 | (NR_Mob_enh2-Perf) Correction on Principle of Testing in NR-DC | ZTE Corporation, Sanechips |
R4-2506574 | (NR_Mob_enh2-Perf) Correction on Principle of Testing in NR-DC | ZTE Corporation, Sanechips |
R4-2506580 | (NR_Mob_enh2-Core) Measurement restrictions for CSI-RS based measurement | ZTE Corporation, Sanechips |
R4-2506581 | (NR_Mob_enh2-Core) Measurement restrictions for CSI-RS based measurement | ZTE Corporation, Sanechips |
R4-2506741 | (NR_Mob_enh2-Core) Corrections on LTM core requirements | Huawei, HiSilicon |
R4-2506742 | (NR_Mob_enh2-Core) Corrections on LTM core requirements | Huawei, HiSilicon |
R4-2507019 | LTM Core maintenance | Ericsson |
R4-2507020 | CR to TS 38.133: maintenance CR on LTM | Ericsson |
R4-2507021 | CR for LTM maintenance | Ericsson |
R4-2507800 | UE behavior and timeline for Early-PRACH | Qualcomm Incorporated |
R4-2507900 | CR on R18 LTM RRM performance requirements_perf | vivo |
TDoc | Title | Source |
---|---|---|
R4-2506726 | CR on TC maintenance for R18 MIMO uTCI R18 | Huawei, HiSilicon |
R4-2506727 | CR on TC maintenance for R18 MIMO uTCI R19 (cat A) | Huawei, HiSilicon |
R4-2507381 | CR corrections of RRM core requirements for NR MIMO Evo | Nokia |
R4-2507382 | CR corrections of RRM core requirements for NR MIMO Evo | Nokia |
R4-2507383 | CR corrections of RRM performance requirements for NR MIMO Evo | Nokia |
R4-2507384 | CR corrections of RRM performance requirements for NR MIMO Evo | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506557 | CR for correction on test cases on CHO with PSCell change and CHO with CPC | vivo, Nokia, Nokia Shanghai Bell |
R4-2506558 | CR for correction on test cases on CHO with PSCell change and CHO with CPC | vivo |
R4-2506582 | (NR_redcap_enh-Core) Correction on eRedCap UE | ZTE Corporation, Sanechips |
R4-2506583 | (NR_redcap_enh-Core) Correction on eRedCap UE | ZTE Corporation, Sanechips |
R4-2506743 | (NR_redcap_enh-Core) Correction to TA validation requirements for RedCap R18 | Huawei, HiSilicon |
R4-2506744 | (NR_redcap_enh-Core) Correction to TA validation requirements for RedCap R19 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2507305 | (Netw_Energy_NR-Core) CR on NES CHO_R18 | ZTE Corporation, Sanechips |
R4-2507306 | (Netw_Energy_NR-Core) CR on NES CHO_R19 | ZTE Corporation, Sanechips |
R4-2507379 | 38133CR on inter-band SSB-less SCell activation | Nokia, Nokia Shanghai Bell |
R4-2507380 | 38133CR on inter-band SSB-less SCell activation - R19 CatA | Nokia, Nokia Shanghai Bell |
R4-2507536 | (Netw_Energy_NR-Core) CR on NES CHO_R18 | ZTE Corporation, Sanechips |
R4-2507901 | (Netw_Energy_NR-Core) 38133CR on inter-band SSB-less SCell activation | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2506491 | CR on location-based cell reselection for IoT NTN enhancement | MediaTek inc. |
R4-2506546 | CR on location-based cell reselection for IoT NTN enhancement | MediaTek inc. |
R4-2506834 | CR on location-based cell reselection for IoT NTN enhancement | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505891 | FR2 TX requirements verification in beam locked mode | Apple |
R4-2506179 | CR for 38.101-1: Corrections for Contiguous Intra-band CA | T-Mobile USA, Lenovo |
R4-2506180 | Rel-19 CR for 38.101-1: Corrections for Contiguous Intra-band CA [guardband_30kHz_SCS] | T-Mobile USA, Lenovo |
R4-2506183 | Intra-band Contiguous CA Issue and Proposed Resolution | T-Mobile USA |
R4-2506189 | (NR_channel_raster_enh-Core) Correction to nominal CA spacing to accommodate UE-specific channel bandwidths | Ericsson |
R4-2506190 | (NR_channel_raster_enh-Core) Correction to nominal CA spacing to accommodate UE-specific channel bandwidths | Ericsson |
R4-2506991 | (LTE_NR_Simult_RxTx-Core) CR on release independence for simultaneous Rx-Tx capability for inter-band CA/DC in TS 38.307 | MediaTek Korea Inc. |
R4-2506993 | (LTE_NR_Simult_RxTx-Core) CR on release independence for simultaneous Rx-Tx capability for inter-band CA/DC in TS 38.307 | MediaTek Korea Inc. |
R4-2507076 | (NR_FR1_lessthan_5MHz_BW-Core) CR to TS 38.101-1 on addition of 3 MHz channel bandwidth into Annex D.1 | Nokia |
R4-2507370 | CR to 38.101-1 to correct switching period reference for UL Tx Switching | Nokia |
R4-2507371 | CR to 38.101-1 to correct switching period reference for UL Tx Switching | Nokia |
R4-2507372 | CR to 38.101-3 to correct switching period reference for UL Tx Switching | Nokia |
R4-2507373 | CR to 38.101-3 to correct switching period reference for UL Tx Switching | Nokia |
R4-2507647 | [NR_CA_R18_Intra-Core] CR to TS38.101-1-i90: Correction to PC2 intra-band contiguous CA REFSENS - CatF | Skyworks Solutions Inc., T-Mobile USA |
R4-2507654 | [NR_CA_R18_Intra-Core] CR to TS38.101-1-j10: Correction to PC2 intra-band contiguous CA REFSENS - CatA | Skyworks Solutions Inc., T-Mobile USA |
R4-2507674 | CR to TR 38.922 Addition of AAS BS spectral mask and spurious emissions for 14800 to 15350 MHz frequency range | Ericsson |
R4-2507675 | CR to TR 38.922 Removal of references to internal TRs and Tdocs | Ericsson |
R4-2507896 | Rel-18 CR for 38.101-1: Corrections for Contiguous Intra-band CA [guardband_30kHz_SCS] | T-Mobile USA, Lenovo |
R4-2507903 | [HPUE_NR_FR1_FDD_R18-Core] CR to TS38.101-1-i90: Correction to PC2 intra-band contiguous CA REFSENS – CatF | Skyworks Solutions, Inc., T-Mobile USA |
TDoc | Title | Source |
---|---|---|
R4-2505338 | CR to TS 38.104: Transmit power for 3MHz CBW in band n100 | Union Inter. Chemins de Fer |
R4-2505339 | CR to TS 38.104: Transmit power for 3MHz CBW in band n100 | Union Inter. Chemins de Fer |
R4-2505404 | (FS_NR_IMT_4400_7125_14800MHz) Editorial corrections in Annex A title | Apple |
R4-2506248 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS38.141-1 Introduction of 3MHz channel bandwidth for test configurations | ZTE Corporation, Sanechips |
R4-2506249 | (NR_FR1_lessthan_5MHz_BW-Perf) CR to TS38.141-1 Introduction of 3MHz channel bandwidth for test configurations | ZTE Corporation, Sanechips |
R4-2506326 | (NB_IOTenh3-Core)CR to TS38.113: FRC correction for performance criteria for continuous phenomena for BS | ZTE Corporation, Sanechips |
R4-2506937 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 on removal of undefined references | NEC |
R4-2506938 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 on BS spurious emissions for 4400 to 4800 MHz frequency range and spectral mask for 14800 to 15350 MHz frequency range | NEC |
R4-2506939 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 on BS antenna pattern for 14800 to 15350 MHz frequency range | NEC |
R4-2506940 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 on BS blocking response performance requirements for 4400 to 4800 MHz frequency range | NEC |
R4-2507077 | (FS_NR_IMT_4400_7125_14800MHz) CR to TS 38.922 on transmission power control model | Nokia |
R4-2507079 | (FS_NR_IMT_4400_7125_14800MHz) CR to TS 38.922 on corrections and clarifications on IMT parameters | Nokia |
R4-2507730 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 Addition of AAS BS spectral mask and spurious emissions for 14800 to 15350 MHz frequency range | Ericsson |
R4-2507731 | (FS_NR_IMT_4400_7125_14800MHz) CR to TR 38.922 Removal of references to internal TRs and Tdocs | Ericsson |
R4-2507894 | CR to TS 38.104: Transmit power for 3MHz CBW in band n100 | Union Inter. Chemins de Fer, Nokia |
R4-2507895 | CR to TS 38.104: Transmit power for 3MHz CBW in band n100 | Union Inter. Chemins de Fer, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506291 | CR on Correction for 38.133: clauses 6.1.4.2.2 | Korea Testing Laboratory |
R4-2506292 | CR on Correction for 38.133: clauses 6.1.4.2.2 | Korea Testing Laboratory |
R4-2506694 | (NR_DualTxRx_MUSIM-Perf) Correction to MUSIM gap test cases_R18 | Huawei, HiSilicon |
R4-2506695 | (NR_DualTxRx_MUSIM-Perf) Correction to MUSIM gap test cases_R19 | Huawei, HiSilicon |
R4-2507110 | (NR_newRAT-core) On gradual timing adjustment for CA and DC | Ericsson |
R4-2507111 | (NR_newRAT-core) On gradual timing adjustment for CA and DC | Ericsson |
R4-2507112 | (NR_newRAT-core) On gradual timing adjustment for CA and DC | Ericsson |
R4-2507175 | (NR_newRAT-core) SCell transmission based on MTTD | Ericsson |
R4-2507211 | Modification on measurement requirements in IDLE state_R18 | ZTECorporation,Sanechips |
R4-2507212 | Modification on measurement requirements in IDLE state_R19 | ZTECorporation,Sanechips |
R4-2507216 | Modification on measurement of inter-EUTRAN cells_R18 | ZTECorporation,Sanechips |
R4-2507217 | Modification on measurement of inter-EUTRAN cells_R19 | ZTECorporation,Sanechips |
R4-2507610 | Modification on measurement of inter-EUTRAN cells [Meas_inter-RAT_cells] | ZTECorporation,Sanechips |
R4-2507611 | Modification on measurement of inter-EUTRAN cells [Meas_inter-RAT_cells] | ZTECorporation,Sanechips |
R4-2507899 | CR on Correction for 38.133: clauses 6.1.4.2.2 | Korea Testing Laboratory |
R4-2507902 | Modification on measurement of inter-EUTRAN cells [Meas_inter-RAT_cells] | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505390 | LS on 8Rx UE receiver capability definition update request | China Telecom |
R4-2506074 | (NR_MIMO_evo_DL_UL-Perf)CR for 38.141-2, Correction on manufacturer declarations for PUSCH with enhanced DM-RS for BS type 1-H | CATT |
R4-2506075 | (NR_MIMO_evo_DL_UL-Perf)CR for 38.141-2, Correction on manufacturer declarations for PUSCH with enhanced DM-RS for BS type 1-H | CATT |
R4-2506279 | (LTE_NBIoT_eMTC_NTN_req-Perf) Clarification on test requirement applicability to IoT-NTN devices | Anritsu Corporation |
R4-2506280 | (LTE_NBIoT_eMTC_NTN_req-Perf) CR for TS36.102 on applicability rules for IoT-NTN requirements | Anritsu Corporation |
R4-2506479 | (NR_ENDC_RF_FR1_enh2-Perf) CR to TS38101-4 Correction on the name of 8Rx receivers | Ericsson |
R4-2506672 | CR on PDSCH demodulation performance requirements and Reference Channel for Rel-18 8Rx CA | Samsung |
R4-2507040 | [NR_DSS_enh-Perf] Modification on test applicability rules for eDSS requirements | Huawei, HiSilicon |
R4-2507041 | [NR_ENDC_RF_FR1_enh2-Perf] Modification on test setup of 8Rx CA requirements | Huawei, HiSilicon |
R4-2507627 | CR on NCR Mimo Correlation Matrices in 38.106 | Nokia |
R4-2507628 | CR on NCR Mimo Correlation Matrices in 38.106 | Nokia |
R4-2507629 | CR on NCR Mimo Correlation Matrices in 38.115-1 | Nokia |
R4-2507630 | CR on NCR Mimo Correlation Matrices in 38.115-1 | Nokia |
R4-2507631 | CR on NCR Mimo Correlation Matrices in 38.115-2 | Nokia |
R4-2507648 | Discussion on the LS for updating the definition of 8Rx receivers | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505847 | Correction of SCF CM Validation Frequency for n3 and corresponding reference values and limits | Keysight Technologies UK Ltd |
R4-2505848 | Correction of SCF CM Validation Frequency for n3 and corresponding reference values and limits | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2506321 | CR to Rel-18 TS38.307 on overlapping bands table [Overlapping_Bands] | ZTE Corporation, Sanechips |
R4-2506322 | CR to Rel-19 TS38.307 on overlapping bands table [Overlapping_Bands] | ZTE Corporation, Sanechips |
R4-2506873 | Draft CR on UE channel bandwidth for FR2-NTN | vivo |
R4-2506874 | [R19] CR to 38.101-5 on UE channel bandwidth for FR2-NTN | vivo |
R4-2507227 | CR to 38.101-1: Modification of additional requirements indicated by NS_05 NS_05U [NR_newRAT-Core] | Ericsson, Samsung |
R4-2507228 | CR to 38.101-1 Rel-16. to add indication of modified MPR behavior [NR_newRAT-Core] | Ericsson, Samsung |
R4-2507229 | CR to 38.101-1 Rel-17. to add indication of modified MPR behavior [NR_newRAT-Core] | Ericsson, Samsung |
R4-2507230 | CR to 38.101-1 Rel-18. To add indication of modified MPR behavior [NR_newRAT-Core] | Ericsson, Samsung |
R4-2507231 | CR to 38.101-1 Rel-19. to add indication of modified MPR behavior [NR_newRAT-Core] | Ericsson, Samsung |
R4-2507885 | 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-2507886 | 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-2507887 | 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-2507888 | LS on introduction of FR2 PC8 | Huawei, HiSilicon |
R4-2507893 | On the options proposed for PC8 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506076 | (TEI18 )CR for 38.141-2, Correction on Manufacturer declarations for PRACH format for HAPS scenario for BS type 1-H | CATT |
R4-2506077 | (TEI18 )CR for 38.141-2, Correction on Manufacturer declarations for PRACH format for HAPS scenario for BS type 1-H | CATT |
R4-2508907 | (TEI18) CR for 38.141-2, Correction on Manufacturer declarations for PRACH format for HAPS scenario for BS type 1-H [PRACH_format_HAPS] | CATT |
R4-2508908 | (TEI18) CR for 38.141-2, Correction on Manufacturer declarations for PRACH format for HAPS scenario for BS type 1-H [PRACH_format_HAPS] | CATT |
TDoc | Title | Source |
---|---|---|
R4-2505447 | On UL Tx switching for FR1 intra-band NC UL CA for TEI19 | Apple, T-Mobile USA, Skyworks Solutions Inc., Telstra, TELUS, Vodafone, Murata Manufacturing Co Ltd., BT Plc |
R4-2505448 | Draft LS on FR1 intra-band NC UL CA Tx switching for TEI19 | Apple |
R4-2505449 | CR to 38.101-1 on introducing UL Tx switching for intra-band NC UL CA | Apple |
R4-2505835 | Discussion on remaining issue of Tx switching for 3Tx UEs in Rel-19 TEI | MediaTek inc. |
R4-2505836 | CR 38.101-1 on time mask of Tx switching for 3Tx UEs [TxSwich_R19] | MediaTek inc. |
R4-2506161 | 3Tx and 4Tx switching | Qualcomm Incorporated |
R4-2507151 | Discussion on introducing 3 Tx and 4 Tx switching | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505837 | CR 38.133 on interruption of Tx switching for 3Tx UEs [TxSwich_R19] | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2507544 | Topic summary for [115][105] NR_Baskets_Part_1 | Moderator (Nokia) |
R4-2507545 | Topic summary for [115][106] NR_Baskets_Part_2 | Moderator (Ericsson) |
R4-2507546 | Topic summary for [115][107] LTE_Baskets | Moderator (Huawei) |
R4-2507547 | Topic summary for [115][108] HPUE_NR_bands | Moderator (CMCC) |
R4-2507548 | Topic summary for [115][109] Void | Chair (Apple) |
R4-2507549 | Topic summary for [115][110] HPUE_Basket_EN-DC | Moderator (China Unicom) |
R4-2507550 | Topic summary for [115][111] HPUE_Basket_CADC_SUL | Moderator (China Telecom) |
R4-2507551 | Topic summary for [115][112] LTE_NR_Other_basket | Moderator (Huawei) |
R4-2507552 | Topic summary for [115][113] Void | Chair (Apple) |
R4-2507553 | Topic summary for [115][114] NR_IoT_NTN_Bands | Moderator (Aalyria) |
R4-2507554 | Topic summary for [115][115] NR_mmWave_protect | Moderator (China Unicom) |
R4-2507849 | Topic summary for [115][317] 5G_Broadcast_bands | Moderator (EBU) |
TDoc | Title | Source |
---|---|---|
R4-2505457 | CR Bugfixes and missing Fallbacks 38101-3-j10_s00-05 | Apple |
R4-2505461 | TR37.719-21-11 v0.6.0 for DC_R19_xBLTE_yBNR_3DL2UL | LG Electronics Deutschland |
R4-2505462 | Draft BigCR for DC_R19_xBLTE_yBNR (OBJ-2 DC_R19_xBLTE_yBNR_3DL2UL) | LG Electronics Deutschland |
R4-2506273 | draft BigCR for DC_R19_xBLTE_yBNR (OBJ-4 DC_R19_LTE_NR_SUL_combos | Samsung |
R4-2506274 | Draft TR 37.719-11-10_v0.1.0 | Samsung |
R4-2506891 | TR 37.719-11-11 v0.5.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-2506992 | draft BigCR for DC_R19_xBLTE_yBNR (OBJ-1 DC_R19_1BLTE_1BNR_2DL2UL) | CHTTL |
R4-2507367 | Big draftCR for DC_R19_xBLTE_yBNR (OBJ-3 DC_R19_xBLTE_yBNR_zDLqUL) | Nokia |
R4-2507368 | Big CR for DC_R19_xBLTE_yBNR | Nokia, CHTTL, LG Electronics, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505717 | MSD for DC_(n)3CA | Murata Manufacturing Co Ltd. |
R4-2506278 | TP for TR 37.719-11-11 DC_(n)3 | Samsung, KT, [Murata, Skyworks] |
R4-2507423 | TP for TR 37.719-11-11 to introduce intra-band non-contiguous DC_7A_n7A_BCS1 | ZTE Corporation, Sanechips |
R4-2507698 | DC_(n)3CA MSD | Skyworks Solutions Inc. |
R4-2507704 | LS on E-UTRA uplink configurations for intra-band ENDC MSD | Skyworks Solutions Inc. |
R4-2507705 | DC_28_n71 MSD | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2505329 | TP for TR 37.719-21-11: DC_28A_n40A-n71A | Huawei, Hisilicon |
R4-2505330 | TP for TR 37.719-21-11: DC_8A_n40A-n71A | Huawei, Hisilicon |
R4-2505331 | TP for TR 37.719-21-11: DC_3-28_n71 | Huawei, Hisilicon |
R4-2505543 | TP for TR 37.719-21-11 on introduction of DC_1A-8A_n71A | Huawei, HiSilicon |
R4-2505544 | TP for TR 37.719-21-11 on introduction of DC_3A-8A_n71A and DC_3C-8A_n71A | Huawei, HiSilicon |
R4-2505545 | TP for TR 37.719-21-11 on introduction of DC_1A-28A_n71A | Huawei, HiSilicon |
R4-2505581 | TP for TR 37.719-21-11 on introduction of DC_8A_n71A-n77A | Huawei, HiSilicon |
R4-2505582 | TP for TR 37.719-21-11 on introduction of DC_28A_n71A-n77A | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505332 | draftCR to 38.101-3 to include EN-DC band combinations | Huawei, Hisilicon |
R4-2505546 | Draft CR to 38.101-3 to include EN-DC band combinations | Huawei, HiSilicon,STC |
R4-2505583 | draft CR for TS 38.101-3 to introduce DC band combinations consist of more than three bands | Huawei, HiSilicon |
R4-2505800 | DraftCR for TS 38101-3 to add x LTE and x NR inter-band EN-DC (DC_R19_xBLTE_yBNR_zDLqUL) | Huawei, HiSilicon |
R4-2507378 | draftCR to 38.101-3 to include EN-DC band combinations (DC_R19_xBLTE_yBNR_zDLqUL) | Nokia, Telefonica |
R4-2507424 | Draft CR on TS 38.101-3 to introduce new BC for DC_3-7-20_n28 and DC_3-7-20_n78 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505456 | CR Bugfixes and missing Fallbacks 38101-1-j10_s0505A03-0505A03 | Apple |
R4-2505548 | Draft Big CR on Introduction of completed SUL band combinations into TS 38.101-1 | Huawei, HiSilicon |
R4-2505549 | TR for 38.719-00-00 v0.2.0 | Huawei, HiSilicon |
R4-2506246 | draft big CR on 38.101-1 for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
R4-2506247 | draft big CR on 38.101-2 for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
R4-2506397 | TR38.719-02-01 v0.5.1_NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
R4-2506398 | TR38.719-02-01 v0.6.0 | ZTE Corporation |
R4-2506399 | draft big CR to TS38.101-3 for NR_CADC_SUL_R19(OBJ-2 NR_CADC_R19_2BDL_xBUL) | ZTE Corporation |
R4-2506492 | draft big CR 38.101-1 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) | Ericsson |
R4-2506493 | draft big CR 38.101-3 for NR_CADC_SUL_R19(OBJ-4 NR_CADC_R19_yBDL_xBUL) | Ericsson |
R4-2507398 | TR 38.719-03-01 v0.5.1 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-2507399 | TR 38.719-03-01 v0.6.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-2507400 | Draft big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-1 | ZTE Corporation |
R4-2507401 | Draft big CR for NR_CADC_SUL_R19 (OBJ-3 NR_CADC_R19_3BDL_xBUL) into TS 38.101-3 | ZTE Corporation |
R4-2507587 | Revised WID NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
R4-2507588 | draft big CR 38.101-1 new combinations Rel-19 NR Intra-band | Ericsson |
R4-2507589 | draft big CR 38.101-2 new combinations Rel-19 NR Intra-band | Ericsson |
R4-2507590 | Rel-19 NR intra-band CA combinations | Ericsson |
R4-2507591 | Big CR 38.101-1 for NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
R4-2507592 | Big CR 38.101-2 for NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
R4-2507593 | Big CR 38.101-3 for NR_CADC_SUL_R19 | Ericsson, ZTE Corporation, Sanechips, Huawei, Hisilicon |
R4-2507609 | Discussion paper for PRD01 about status report input from proponents | Ericsson |
R4-2507709 | PRD updates on rules for 1UL MSD configurations | Skyworks Solutions Inc. |
R4-2507791 | PRD input on IMD range definition for inter-band MSD due to 1UL 2CC UL configuration | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2505530 | Draft CR for TS 38.101-2 to introduce CA_n258R and CA_n258S | Huawei, HiSilicon |
R4-2507604 | CR 38.101-3 correcting 2 bands NR CA combinatons | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505450 | Views on 2UL CA_n28A-n71A | Apple |
R4-2505528 | Discussion on UL CA_n28A-n71A | Huawei, HiSilicon |
R4-2505529 | TP for TR 38.719-02-01 on introduction of CA_n28A-n71A | Huawei, HiSilicon |
R4-2505734 | Draft CR 38.101-1 Correction for CA configuration of: CA_n48B-n77A | Nokia |
R4-2506392 | Clarification on UL CA_n41C IMD MSD test point | ZTE Corporation, Sanechips |
R4-2506393 | TP for TR38.719-02-01_UL CA_n3A-n104C | ZTE Corporation, Sanechips |
R4-2506394 | TP for TR38.719-02-01_UL CA_n8A-n104C | ZTE Corporation, Sanechips |
R4-2506395 | TP for TR38.719-02-01_Correct the harmonic MSD test points for CA_n3-n104 and n20-n41 | ZTE Corporation, Sanechips |
R4-2506685 | On CA_n28-n71 2UL operation | Skyworks Solutions Inc. |
R4-2506855 | Discussion on the optional channel bandwidth across releases | vivo |
R4-2507064 | About UL CA_n28-n71 | Qualcomm France |
R4-2507258 | Draft CR for TS 38.101-1 to add bandwidth combination set 4 and 5 for inter-band CA combinations (two bands) | Samsung, Boost Mobile Network |
R4-2507261 | Draft CR for adding CA_n74A-n77(2A) to TS 38101-1 | KDDI, Samsung |
R4-2507279 | TP to TR 38.719-02-01 for adding impact of harmonic mixing to CA_n18-n77 with UL n77 | KDDI, Murata, Samsung |
R4-2507369 | DraftCR to 38.719-02-01 to correct analysis for CA_n66-n77 | Nokia, Verizon |
R4-2507594 | draft CR 38.101-1 adding BCS 4 and 5 configurations CA_n2-n14, CA_n14-n66, CA_n14-n77 | Ericsson, AT&T |
R4-2507599 | draft CR 38.101-3 adding BCS 4 and 5 to 2 bands NR CA combinatons | Ericsson, Rogers |
R4-2507601 | draft CR 38.101-1 adding BCS 4 and 5 to 2 bands NR CA combinatons | Ericsson, Rogers |
R4-2507605 | CR 38.101-1 correcting 3 bands NR CA combinatons | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505547 | Draft CR for TS 38101-1 include BCS 4 and 5 for CA configurations of 3BDL | Huawei, HiSilicon,MTN |
R4-2505653 | Draft CR for TS38.101-1 Rel-19 to add BCS4 and 5 for 3CC NRCA combinations | SoftBank Corp. |
R4-2505735 | Draft CR 38.101-1 Correction for CA configuration of: CA_n3A-n7A-n78(A-C) | Nokia |
R4-2506271 | TP to TR 38.719-03-01 for CA_n28-n74-n77 | Samsung, KDDI, Qualcomm |
R4-2506272 | TP to TR 38.719-03-01 for CA_n28-n41-n74 | Samsung, KDDI, Qualcomm |
R4-2506494 | TP for 38.719-03-01 to add UL CA_n2A-n77C and CA_n5A-n77C for CA_n2-n5-n77 | Ericsson, Verizon |
R4-2506495 | TP for 38.719-03-01 to add UL CA_n2A-n77C and CA_n66A-n77C for CA_n2-n66-n77 | Ericsson, Verizon |
R4-2506496 | TP for 38.719-03-01 to add UL CA_n2A-n77C for CA_n2A-n48A-n77C | Ericsson, Verizon |
R4-2506497 | TP for 38.719-03-01 to add UL CA_n5A-n77C and CA_n66A-n77C for CA_n5-n66-n77 | Ericsson, Verizon |
R4-2506498 | TP for 38.719-03-01 to add UL CA_n5A-n77C for CA_n5-n48-n77 | Ericsson, Verizon |
R4-2506499 | TP for 38.719-03-01 to add UL CA_n66A-n77C for CA_n48-n66-n77 | Ericsson, Verizon |
R4-2506536 | TP for 38.719-03-01 to add UL CA_n2A-n48B and CA_n2A-n77C for CA_n2-n48-n77 | Ericsson, Verizon |
R4-2506537 | TP for 38.719-03-01 to add UL CA_n5A-n77C and CA_n5A-n48B for CA_n5-n48-n77 | Ericsson, Verizon |
R4-2506538 | TP for 38.719-03-01 to add UL CA_n66A-n77C and CA_n48B-n66A for CA_n48-n66-n77 | Ericsson, Verizon |
R4-2506539 | draft CR 38.101-1 adding new UL CA configurations for 3BDL configurations | Ericsson, Verizon |
R4-2506540 | draft CR 38.101-3 to add new NR CADC 3BDL configurations including FR2 | Ericsson, TMUS |
R4-2506541 | draft CR 38.101-1 adding new UL CA configurations for 3BDL configurations | Ericsson, TMUS |
R4-2507262 | Draft CR for adding some n74-inluded three-band combinations to TS 38101-1 | KDDI, Samsung |
R4-2507425 | Draft CR on TS 38.101-3 to add missing CA operating bands for three bands | ZTE Corporation, Sanechips |
R4-2507426 | Draft CR on TS 38.101-3 to introduce new BC for CA_n8-n79-n258 | ZTE Corporation, Sanechips |
R4-2507595 | draft CR 38.101-1 adding BCS 4 and 5 configurations CA_n2-n14-n66, CA_n2-n14-n77, CA_n14-n66-n77 | Ericsson, AT&T |
R4-2507600 | draft CR 38.101-3 adding BCS 4 and 5 to 3 bands NR CA combinatons | Ericsson, Rogers |
R4-2507602 | draft CR 38.101-1 adding BCS 4 and 5 to 3 bands NR CA combinatons | Ericsson, Rogers |
R4-2507606 | CR 38.101-1 correcting 4 bands NR CA combinatons | Ericsson |
R4-2507773 | Draft CR for adding some n74-included three-band combinations to TS 38101-1 | KDDI, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505463 | Draft CR for TS38.101-3: addition of NRDC combinations between FR1 and FR2 | SoftBank Corp. |
R4-2505654 | Draft CR for TS38.101-1 Rel-19 for adding new NRCA combinations for FR1 for 4 DL | SoftBank Corp. |
R4-2505736 | Draft CR 38.101-1 Correction for CA configuration of: CA_n1A-n3A-n7A-n28A-n78C | Nokia |
R4-2506542 | draft CR 38.101-1 adding new UL CA configurations for 4BDL configurations | Ericsson, TMUS |
R4-2507596 | draft CR 38.101-1 adding BCS 4 and 5 configurations CA_n2-n14-n66-n77 | Ericsson, AT&T |
R4-2507603 | draft CR 38.101-1 adding BCS 4 and 5 to 4 bands NR CA combinatons | Ericsson, Rogers |
TDoc | Title | Source |
---|---|---|
R4-2505458 | CR Bugfixes and missing Fallbacks 36101 | Apple |
R4-2505809 | 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-2505811 | TR 36.719-01-01 LTE-A CA for x-DL y-UL | Huawei, HiSilicon |
R4-2505812 | Revised WID Rel-19 LTE-A CA for x(1<=x<=6) DL y(y<=2) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505748 | PC2 and PC1.5 in bands n100 and n101 | Union Inter. Chemins de Fer |
TDoc | Title | Source |
---|---|---|
R4-2505359 | TR 38.796 v0.5.0 HPUE_NR_FR1_bands_R19-FDD | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2506191 | Specification of PC2 for n5 and n26 | Ericsson |
R4-2506192 | Introduction of requirements for PC2 operation in band n5 | Ericsson |
R4-2506193 | Introduction of requirements for PC2 operation in band n26 | Ericsson |
R4-2507003 | Discussion on UE requirement of PC2 for n5 and n26 | China Telecom |
R4-2507707 | n26 PC2 NS_15 measurements | Skyworks Solutions Inc. |
R4-2507719 | On PC2 HPUE requirements | Huawei, HiSilicon |
R4-2507748 | A-MPR for n26 PC2 and n1 PC2 | Qualcomm Incorporated |
R4-2507766 | TP to TR 38.796: adding n26 PC2 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505360 | TR 37.898 v0.5.0 HPUE_DC_LTE_NR_R19 | China Unicom, Ericsson |
R4-2505363 | Big CR on Rel-19 HPUE for DC combinations of LTE band(s) and NR band(s) | China Unicom, Ericsson |
R4-2505364 | 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 |
TDoc | Title | Source |
---|---|---|
R4-2505464 | TP for TR37.898: addition of PC2 to DC_8_n41-n77 and DC_3_n3-n77 | SoftBank Corp. |
R4-2505465 | Draft CR for TS38.101-3: addition of PC2 to FR1 ENDC combinations | SoftBank Corp. |
R4-2506849 | TP for TR 37.898 to add of PC2 for DC_5A_n41A | vivo |
R4-2506850 | TP for TR 37.898 to add of PC2 for DC_14A_n41A | vivo |
R4-2506851 | TP for TR 37.898 to add of PC2 for DC_26A_n41A | vivo |
R4-2506852 | TP for TR 37.898 to add of PC2 for DC_71A_n41A | vivo |
R4-2506853 | TP for TR 37.898 to add of PC2 for DC_11A_n78A | vivo |
R4-2506854 | TP for TR 37.898 to add of PC2 for DC_39A_n78A | vivo |
TDoc | Title | Source |
---|---|---|
R4-2505361 | TR 38.750 v0.6.0 HPUE_NR_CADC_SUL_R19-FDD | China Unicom |
R4-2505362 | draft objective BigCR for HPUE_NR_CADC_SUL_R19 | China Unicom |
R4-2505365 | Revised WID for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
R4-2505366 | DraftBig CR to 38.101-1 new combinations for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
R4-2505367 | TR 38.746 v0.4.0 HPUE_NR_CADC_SUL_R19-TDD | China Telecom |
R4-2506913 | TR38.792 for PC1.5 with high power on both FDD and TDD bands | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2505655 | TP for TR38.746 addition of PC2 ULCA to CA_n3-n78-n79 | SoftBank Corp. |
R4-2507263 | Draft CR for TS 38.101-1 to add HPUE notes for some NR-CA band combinations | KDDI, Samsung |
R4-2507280 | TP to TR 38.746 for adding CA_n18-n41 with UL PC1.5 n41 | KDDI, Murata, Samsung |
R4-2507316 | TP to TR 38.746 for adding CA_n18-n77 with High power UL n77 | KDDI, Murata, Samsung |
R4-2507317 | TP for HPUE CA_n28-n41-n74 with 2UL for TR 38.746 | KDDI, Qualcomm, Samsung |
R4-2507318 | TP for HPUE CA_n28-n74-n77 with 2UL for TR 38.746 | KDDI, Qualcomm, Samsung |
R4-2507597 | draft CR 38.101-1 adding HPUE notes for 2 bands configurations | Ericsson, BT plc |
R4-2507598 | draft CR 38.101-1 adding HPUE notes for 3 bands configurations | Ericsson, BT plc |
R4-2507607 | draft CR 38.101-1 adding HPUE notes for n1-n78 and CA_n3-n78 | Ericsson, Telstra |
R4-2507608 | draft CR 38.101-1 adding missing intra-band note | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505631 | (HPUE_NR_CADC_SUL_R19) CR for addition and correction of notes in clause 6.2A.1.3 UE MOP for Inter-band CA - TS38.101-1 | Anritsu Limited |
R4-2505632 | (HPUE_NR_CADC_SUL_R19) CR for addition and correction of notes in clause 6.2A.1.3 UE MOP for Inter-band CA - TS38.101-1 | Anritsu Limited |
R4-2506182 | MSD for 3Tx UL CA combinations with 2Tx FDD + 1Tx TDD | T-Mobile USA |
R4-2506914 | TP to TR38.792 on MSD definition approach for PC1.5 with HPUE on both FDD and TDD | OPPO |
R4-2506915 | R19 MSD for PC1.5 with HPUE on both FDD and TDD | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2506400 | Revised WID: Additional NR bands for NR features in Rel-19 | ZTE Corporation, Huawei |
R4-2506401 | draft big CR to TS 38.101-1 to include 4Rx and 8Rx | ZTE Corporation |
R4-2506402 | TS 38.101-1 big CR for NR_bands_xFeature_R19-Core | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R4-2505345 | CR to TS 38.101-1: UL MIMO in bands n100 and n101 | Union Inter. Chemins de Fer, Ericsson, Nokia, Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2506396 | Draft CR to TS38.101-1: Introduce n25 to support 8Rx | ZTE Corporation, T-Mobile USA |
TDoc | Title | Source |
---|---|---|
R4-2506999 | TR 37.887 0.0.6 Rel-19 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2507000 | TP to 37.887: DL interruption clarification for CA_n1-n3-n5-n78 for 4 bands dynamic Tx switching | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2505326 | BigCR to 38.101-1: Simultaneous Rx-Tx | Huawei, Hisilicon |
R4-2505327 | BigCR to 38.101-3: Simultaneous Rx-Tx | Huawei, Hisilicon |
R4-2506975 | Revised WID for Rel-19 simultaneous Rx-Tx | Huawei, HiSilicon, China Telecom, CATT |
TDoc | Title | Source |
---|---|---|
R4-2505324 | Discussion on simultaneous Rx-Tx | Huawei, Hisilicon |
R4-2505325 | draftCR to 38.101-3 Simultaneous Rx-Tx | Huawei, Hisilicon |
R4-2505451 | Views on CA_n5A-n8A with non-simultaneous Rx-Tx | Apple |
R4-2506064 | draft reply LS to RAN2 on UE capability for FDD-FDD inter-band CA simultaneous Rx/Tx | CATT |
R4-2506073 | draftCR for TS 38.101-1 2U/2D n5-n8 | CATT, China Telecom, Huawei, HiSilicon |
R4-2506269 | Views on 3 switching solutions for n5-n8 2UL/2DL | Samsung |
R4-2506391 | Reply LS on UE capability for FDD-FDD inter-band CA simultaneous RxTx | ZTE Corporation, Sanechips |
R4-2507063 | CA_n5A-n8A | Qualcomm France |
R4-2507374 | On simultaneous RxTx and capability for overlapping FDD bands | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505430 | CR to 38.101-1 on adding new channel bandwidth to band n48 | Apple |
R4-2506122 | CR to 38.104 on adding new UL channel bandwidth to band n48 | Apple |
R4-2506156 | Draft revised basket WI on adding new channel BW in existing NR bands | Ericsson |
R4-2506157 | TR 37862 for the basket WI on adding new channel BW in existing NR bands | Ericsson |
R4-2506158 | Big CR to TS 38.104: Adding channel BW support in existing NR bands | Ericsson |
R4-2506159 | Big CR to TS 38.101-1: Adding channel BW support in existing NR bands | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505429 | n48: Adding channels of 50MHz and beyond | Apple |
R4-2506167 | n48 AMPR for wider BWs | Qualcomm Incorporated |
R4-2506184 | Input on Optional vs. Mandatory Channel BWs | T-Mobile USA |
R4-2506204 | TP to TR 37.862 Clause 5.1 on adding channel BWs of 50-100 MHz in band n48 | CableLabs |
R4-2507488 | Input on making 3 MHz channel bandwidth mandatory in Rel-19 | Rakuten Mobile, Inc, T-Mobile USA, Southern Co, Antreix |
R4-2507700 | Impact of Rel-19 BCS4_5 new greatest-smallest CBW on MSD | Skyworks Solutions Inc. |
R4-2507706 | Beyond 40MHz CBW measurements for Band n48 NS_27 | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2505413 | Further input on UE power back-off while operating in 2000-2020 MHz UL range of the NTN band n252 | Apple |
R4-2505414 | CR to TS 38.101-5: Introduction of band n252 | Apple |
R4-2505479 | Discussion on NR-NTN n252 UE RF REFSENS | MediaTek (Hefei) Inc. |
R4-2506035 | Discussion on UE RF requirements for the NTN new S-band | CATT |
R4-2506521 | n252 A-MPR simulations and proposal | Nokia |
R4-2507711 | CR to TR 38.863: Introduction of NR-NTN band n252 | EchoStar, Boost Mobile Network |
R4-2507752 | A-MPR for n252 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2507697 | CR on TS 38.108 Introduction of NR NTN band n252 | THALES, ZTE Corporation, CATT, EchoStar, Boost Mobile Network, Aalyria |
TDoc | Title | Source |
---|---|---|
R4-2507207 | Draft CR to TS 38.133 Introduction of a new NTN S-band | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2506034 | Discussion on SAN conformance requirements for the NTN new S-band | CATT |
R4-2507149 | CR to TS 38.181: Introduction of NR-NTN band n252 | EchoStar, Boost Mobile Network |
TDoc | Title | Source |
---|---|---|
R4-2505604 | Discussion on IoT-NTN B252 UE RF requirements | MediaTek (Hefei) Inc. |
R4-2506625 | CR to TS 36.102: Introduction of IoT-NTN B252 | MediaTek (Hefei) Inc. |
R4-2507715 | CR to TR 36.764: Introduction of IoT-NTN band 252 | EchoStar, Boost Mobile Network |
R4-2507751 | B252 NS-signaling | Qualcomm Incorporated |
R4-2507904 | CR to TR 36.764: Introduction of IoT-NTN band 252 | EchoStar, Boost Mobile Network |
TDoc | Title | Source |
---|---|---|
R4-2506250 | CR to TS36.108 Introduction of IoT-NTN band 252 | ZTE Corporation, Thales, CATT |
R4-2507146 | CR to TS 36.181: Introduction of IoT-NTN band 252 | EchoStar, Boost Mobile Network |
TDoc | Title | Source |
---|---|---|
R4-2508909 | CR to TS 36.133: Introduction of a new IoT NTN S-band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505415 | Further considerations on the emission requirements for the UE operating in 1626.5-1660.5MHz and 1668-1675MHz UL frequency ranges | Apple |
R4-2505416 | CR to TS 38.101-5: Introduction of combined L-bands | Apple, Aalyria Technologies |
R4-2507009 | CR to TR 38.863: Introduction of combined L-bands | Aalyria, THALES |
R4-2507712 | Possible approach on L-band NS value for RA protection | Aalyria |
R4-2507718 | CR to TS 38.101-5: NS value for additional Transmit OFF state requirement for RA protection | Aalyria |
R4-2507744 | CR to TS 38.101-5: NS value for additional Transmit OFF state requirement for RA protection | Aalyria |
R4-2507753 | New NR NTN L-bands and ETSI requirements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506036 | CR for TS 38.108, Introduction on band n253, n251 and n250 | CATT, THALES, ZTE, Aalyria |
R4-2506251 | draftCR to TS38.108 Introduction of NR-NTN combined L-band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505952 | CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | EBU |
R4-2505960 | Release independence of SDO bands for 5G broadcast | EBU |
R4-2507428 | CR to TS 36.101: New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | EBU, BNE, ORS, Qualcomm Incorporated, SWR |
R4-2507451 | Draft CR to TS 36.101: optimization of SDO sub-bands 112/113 implementation | Huawei, HiSilicon |
R4-2507471 | Release independence of SDO bands for 5G broadcast | EBU, BNE |
TDoc | Title | Source |
---|---|---|
R4-2505955 | CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | EBU |
R4-2507436 | CR to TS 36.104 : New bands for LTE based 5G terrestrial broadcast for early deployments, Rel-19 | EBU, BNE, ORS, Qualcomm Incorporated, SWR |
TDoc | Title | Source |
---|---|---|
R4-2505328 | TR 38.749 v0.3.0 Protection of Earth Exploration Satellite Service (EESS) | Huawei, Hisilicon |
R4-2505400 | CR on UE RF requirements for EESS protection (Rel-15) | China Unicom |
R4-2505401 | CR on UE RF requirements for EESS protection (Rel-16) | China Unicom |
R4-2505402 | CR on UE RF requirements for EESS protection (Rel-17) | China Unicom |
R4-2505403 | CR on UE RF requirements for EESS protection (Rel-18) | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2506148 | EESS protection - Earlier Releases update | Ericsson |
R4-2506962 | draft CR to 38.101-2 EESS (Rel-15) | Huawei, HiSilicon |
R4-2506963 | draft CR to 38.101-2 EESS (Rel-16) | Huawei, HiSilicon |
R4-2506964 | draft CR to 38.101-2 EESS (Rel-17) | Huawei, HiSilicon |
R4-2506965 | draft CR to 38.101-2 EESS (Rel-18) | Huawei, HiSilicon |
R4-2506966 | draft CR to 38.101-2: EESS (Rel-19) | Huawei, HiSilicon |
R4-2506967 | Discussion on Rel-19 EESS | Huawei, HiSilicon |
R4-2506976 | TP to TR 38.749 A-MPR evaluation and analysis | Huawei, HiSilicon |
R4-2507649 | TP to TR38.749 on 24 GHz EESS band phase 2 requirements : CA A-MPR Analysis | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2507080 | TP to TR 38.749: BS RF requirements for Protection of EESS | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2507232 | Discussion on the new capabilities UE RF enhancements in Phase 4 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505553 | Topic summary for [115][204] NR_ENDC_RF_Ph4 | Moderator (Huawei) |
R4-2507555 | Topic summary for [115][116] NR_ENDC_RF_Ph4_part1 | Moderator (Huawei) |
R4-2507556 | Topic summary for [115][117] NR_ENDC_RF_Ph4_part2 | Moderator (Samsung) |
R4-2507557 | Topic summary for [115][118] NR_ENDC_RF_Ph4_part3 | Moderator (Huawei) |
R4-2507558 | Topic summary for [115][119] Void | Chair (Apple) |
R4-2507858 | Topic summary for [115][326] NR_ENDC_RF_Ph4_Demod_6Rx | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2505321 | Discussion on HPUE MSD | Huawei, Hisilicon |
R4-2505374 | Further discussion on HPUE MSD simplification LUTs for 1 UL and 2 UL | Murata Manufacturing Co Ltd. |
R4-2505452 | On Rel-19 HPUE 2UL IMD MSD | Apple |
R4-2506383 | Some general considerations on R19 HPUE IMD MSD rule | ZTE Corporation, Sanechips |
R4-2506839 | Discussion on HPUE MSD simplification | vivo |
R4-2506980 | MSD simplification rules for HPUE CA/DC UE | MediaTek Korea Inc. |
R4-2507071 | MSD beyond PC3 | Qualcomm France |
R4-2507118 | On HPUE MSD simplification scope and needed corrections for 1UL 2CC and 2UL 3CC | Skyworks Solutions Inc. |
R4-2507473 | Simplification proposal for HPUE 2UL 2CC MSD | Skyworks Solutions Inc. |
R4-2507645 | [NR_ENDC_RF_Ph4-Core] DraftCR to TS38101-1-j10: Introduction of the 1UL band 1CC HPUE MSD requirements simplification | Skyworks Solutions Inc., Nokia, Samsung |
R4-2507699 | Finalizing the 1UL HPUE MSD Simplification | Skyworks Solutions Inc., Nokia, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505453 | On PC1.5 intra-band NC UL CA MPR | Apple |
R4-2505454 | Draft CR to 38.101-1 on introducing PC1.5 intra-band NC UL CA MPR requirements | Apple |
R4-2505614 | [NR_ENDC_RF_Ph4-Core] DraftCR to 38101-1-j10 on PC1.5 NC ULCA MPR A-MPR and PCmax | Skyworks Solutions Inc. |
R4-2505621 | PC1.5 non-contiguous ULCA MPR, NS_04 A-MPR and PCmax requirements | Skyworks Solutions Inc. |
R4-2505622 | PC1.5 contiguous ULCA MPR for NC allocations and NS_04 A-MPR | Skyworks Solutions Inc. |
R4-2505758 | Introduction of PC1.5 intra-band UL NC CA | Xiaomi |
R4-2505799 | PC1.5 MPR evaluations for intra-band CA | Huawei Technologies France |
R4-2505963 | MPR and A-MPR for intra-band contiguous and non-contiguous UL CA for PC1.5 | Qualcomm Technologies |
R4-2506833 | HPUE MPR for intra-band UL CA | LG Electronics Finland |
R4-2506894 | Draft CR on -30dBm and -13dBm MPR for PC1.5 NCCA | LG Electronics Finland |
R4-2506895 | draft CR on MPR for PC1.5 intra-band contiguous CA | LG Electronics Finland |
R4-2506921 | R19 MPR for PC1.5 NCCA | OPPO |
R4-2506922 | R19 MPR for PC1.5 contig CA with NC RB allocation | OPPO |
R4-2506923 | R19 AMPR for PC1.5 contig CA | OPPO |
R4-2506979 | Discussion on HPUE intra-band/inter-band CA/DC with 2Tx/3Tx | MediaTek Korea Inc. |
TDoc | Title | Source |
---|---|---|
R4-2505372 | CR to 38.307 to update for PC1.5 interband ULCA | Qualcomm Incorporated |
R4-2505605 | Discussion on HPUE inter-band UL CA and EN-DC | SK Telecom |
R4-2505852 | CR to 38.307 to update for PC1.5 interband ULCA | Qualcomm Incorporated |
R4-2506181 | Draft CR for 38.101-1: PC1.5 for 2Tx inter-band uplink CA | T-Mobile USA, Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2505432 | On Rel-19 power domain enhancement for FR1 | Apple |
R4-2505584 | On power domain enhancements for single carrier | Huawei, HiSilicon |
R4-2505585 | draft CR for TS 38.101-1 to introduce MPR reduction for single carrier | Huawei, HiSilicon |
R4-2505677 | Power domain enhancements for single carrier | Nokia |
R4-2505962 | Power boosting and MPR reduction | Qualcomm Technologies |
R4-2506059 | Further discussion on power domain enhancements for single carrier | CATT |
R4-2506194 | Power domain enhancement for a UE-specific CHBW within a single carrier | Ericsson |
R4-2506195 | Draft CR for 38.101-1: power domain enhancement for a UE-specific bandwidth within a wider carrier | Ericsson |
R4-2506225 | Views on Power domain enhancements for single carrier | China Telecom |
R4-2506252 | Discussion on power domain enhancements for single carrier | ZTE Corporation |
R4-2506519 | Power domain enhancements for single carrier | Beijing Xiaomi Mobile Software |
R4-2506520 | Discussion on power domain enhancement for NR single carrier | MediaTek (Wuhan) Inc. |
R4-2506837 | Discussion on UE RF power enhancement for NR single carrier | vivo |
R4-2506838 | draftCR to TS 38.101-1 on MPR reduction for single carrier | vivo |
R4-2507127 | Further Views on MPR Reduction | Sony |
R4-2507319 | Discussion on MPR reduction for single carrier | OPPO |
R4-2507619 | Discussion on Power domain enhancement for single carrier | LG Electronics UK |
R4-2507742 | RB and BW for 2x and 1.5x extension and optional smaller granularity extension | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2506060 | Further discussion on MPR applicability for FR1 intra-band UL CA | CATT |
TDoc | Title | Source |
---|---|---|
R4-2506968 | Discussion on FR2 CA MPR related feature list | Samsung |
R4-2506997 | draft CR to TS 38.101-2 for FR2 MPR improvements | NTT DOCOMO INC., Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2505586 | On leftover issues for 6Rx | Huawei, HiSilicon |
R4-2505649 | Discussion on the usage of the terminology “FWA form factor” and its application for 6Rx, 4Rx and 8Rx requirements | Anritsu Limited |
R4-2506379 | On release independent for 6Rx RF requirement | ZTE Corporation, Sanechips |
R4-2506381 | Draft CR to TS38.101-1: Introduction of ?TRxSRS requirements for 6Rx | ZTE Corporation, Sanechips, Huawei, HiSilicon, vivo |
R4-2506867 | Discussion on general aspects of 6Rx requirements | vivo |
TDoc | Title | Source |
---|---|---|
R4-2505384 | Discussion on remaining issues on 6 MIMO layer evaluation for 6Rx UE | China Telecom |
R4-2505853 | On Core Requirements for 6Rx UEs | Apple |
R4-2506222 | Discussions on release independence for 6Rx devices | QUALCOMM Europe Inc. - Spain |
R4-2506917 | R19 release independent of 6Rx | OPPO |
R4-2507528 | Views on remaining issues for 6Rx UE | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505436 | Draft CR for TS 38.101-1 to introduce delta_TRxSRS requirements for 6Rx | Apple |
R4-2506868 | Further discussion on SRS antenna switching requirements for 6Rx | vivo |
R4-2506918 | R19 release independent of 3T6R SRS antenna switching | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2505437 | On release independence for 6Rx RF requirements | Apple |
R4-2505438 | On SRS Antenna Switching IL Imbalance Solution for 6Rx | Apple |
R4-2505499 | Discussion on 6 Layer MIMO Specification Impact | Nokia |
R4-2505587 | On SRS IL imbalance issue | Huawei, HiSilicon |
R4-2505674 | UE assistance for SRS imbalance solution considerations | Nokia |
R4-2506226 | Discussion on remaining issues on SRS IL imbalance | China Telecom |
R4-2506380 | On 6Rx SRS antenna IL | ZTE Corporation, Sanechips |
R4-2506865 | Discussion on SRS IL imbalance reporting | vivo |
R4-2506888 | Views on SRS insertion loss compensation and reporting enhancements | Intel Corporation |
R4-2506916 | R19 SRS IL indication | OPPO |
R4-2506998 | Discussion on SRS IL imbalance for 6Rx UE | Google Korea LLC |
R4-2507073 | SRS IL imbalance indication | Qualcomm France |
R4-2507529 | Views on SRS IL imbalance issue | Samsung |
R4-2507772 | SRS Power Imbalance Handling and PHR Reporting | Lenovo |
R4-2507782 | On the SRS IL imbalance reporting for the SRS-AS | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505855 | (NR_ENDC_RF_Ph4-Perf) CR for RLM/BFD Antenna Connection for 6Rx UEs | Apple |
R4-2506740 | CR on introducing antenna connections for 6Rx capable UEs | Huawei, HiSilicon |
R4-2507158 | Discussions on RRM performance requirements of Rel-19 WI on UE RF enhancements | Ericsson |
R4-2507159 | (NR_ENDC_RF_Ph4-Perf) Draft CR on antenna configuration and principle of RRM testing for 6Rx UE | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505343 | Discussion on demodulation and CSI requirements for 6Rx UE | MediaTek inc. |
R4-2505385 | Discussion on UE demodulation performance requirements for 6Rx | China Telecom |
R4-2505498 | Discussion on 6 Layer MIMO performance requirements | Nokia |
R4-2505615 | Discussions on demodulation performance requirements for 6Rx devices | QUALCOMM Europe Inc. - Spain |
R4-2505854 | On UE Demodulation Performance Requirements for 6Rx Ues | Apple |
R4-2506477 | On UE demodulation and CSI reporting requirements for 6Rx | Ericsson |
R4-2506478 | Simulation results for 6Rx UE demodulation | Ericsson |
R4-2506673 | Discussion on UE demodulation performance requirements for 6Rx | Samsung |
R4-2506955 | Discussion on UE demodulation performance requirements for 6Rx | ZTE Corporation, Sanechips |
R4-2507030 | Discussion on 6Rx UE performance requirements | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2507559 | Topic summary for [115][120] NR_SL_intraB_CA_ITS_part1 | Moderator(OPPO) |
R4-2507560 | Topic summary for [115][121] NR_SL_intraB_CA_ITS_part2 | Moderator (LGE) |
TDoc | Title | Source |
---|---|---|
R4-2506202 | TP to TR 38.787 on SL intra-band CA | LG Electronics |
R4-2506203 | Big CR for SL intra-band CA | LG Electronics |
R4-2507183 | TP to TR 38.787 for intra-band non-contiguous CA | OPPO |
R4-2507365 | Big CR for SL intra-band CA | LG Electronics, Oppo |
TDoc | Title | Source |
---|---|---|
R4-2505554 | Topic summary for [115][205] NR_FR1_lessthan_5MHz_BW_Ph2 | Moderator (Intel) |
R4-2507561 | Topic summary for [115][122] NR_FR1_5MHz_BW_Ph2 | Moderator (Intel) |
R4-2507859 | Topic summary for [115][327] NR_less_than_5MHz_Ph2_demod | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R4-2506827 | Views on less than 5MHz CADC UE features in Rel-19 | Intel Corporation |
R4-2507081 | CR to TS 38.101-1 on addition of 3 MHz channel bandwidth into Annex D.1 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506584 | CR to TS 38.133: NR channel BW less than 5MHz for FR1 | ZTE Corporation, Sanechips |
R4-2506777 | Discussion on RRM requirements for less than 5MHz Ph2 | Huawei, HiSilicon |
R4-2506778 | CR on RRM requirements for less than 5MHz Ph2 | Huawei, HiSilicon |
R4-2506822 | Core maintenance CR on less than 5MHz RRM requirements | Intel Corporation |
R4-2507333 | DraftCR on RRM High Speed requirements for less than 5MHz Ph2 | Ericsson |
R4-2507334 | Discussion on supporting High Speed in Rel-19 NR CA DC in less than 5 MHz | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506132 | Discussion on Less than 5MHz Phase 2 performance requirements | Nokia |
R4-2506133 | DraftCR to 38.133 on Test case for SA event triggered reporting test without gap under non-DRX with SSB index reading and 12 PRB SSB for a deactivated SCell | Nokia |
R4-2506575 | Correction on test cases for NR channel BW less than 5MHz | ZTE Corporation, Sanechips |
R4-2506779 | draftCR on EMR test case for less than 5MHz Ph2 | Huawei, HiSilicon |
R4-2506808 | Big CR on RRM performance requirements of NR channel BW less than 5MHz for FR1 phase 2 | Intel Corporation |
R4-2507335 | Correction of Draft big CR on RRM performance requirements of NR channel BW less than 5MHz for FR1 phase 2 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505386 | Discussion on UE demodulation performance requirements for NR channel bandwidth less than 5MHz | China Telecom |
R4-2505497 | Views on Less Than 5MHz BW Phase 2 for UE Demod | Qualcomm Incorporated |
R4-2505859 | On UE Demodulation Performance Requirements for NR Channel BW less than 5MHz for FR1 Phase 2 | Apple |
R4-2506438 | Discussion on UE CA Demodulation performance requirements for lessthan 5MHz | Nokia |
R4-2506439 | (NR_FR1_lessthan_5MHz_BW_Ph2-Perf) CR on 38.101-4 for adding UE CA Demodulation performance requirements for lessthan 5MHz | Nokia |
R4-2506674 | Discussion and simulation results on UE demodulation performance requirements for less than 5MHz FR1 Phase 2 | Samsung |
R4-2507038 | Discussion on UE performance requirements for less than 5MHz for CA | Huawei, HiSilicon |
R4-2507101 | UE demodulation requirements for CA including 3MHz CBW | Ericsson |
R4-2507102 | Simulation results Summary of PDSCH for 3MHz CBW | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505555 | Topic summary for [115][206] NonCol_intraB_ENDC_NR_CA_Ph2 | Moderator (Huawei) |
R4-2507562 | Topic summary for [115][123] NonCol_intraB_ENDC_NR_CA | Moderator (KDDI) |
TDoc | Title | Source |
---|---|---|
R4-2505860 | On UE feature list for intra-band non-collocated CA | Apple |
TDoc | Title | Source |
---|---|---|
R4-2505678 | draftCR TS38.101-1 On non-collocated NR-CA | Nokia, Samsung, KDDI, Qualcomm Inc. |
R4-2505679 | draftCR TS38.101-3 On non-collocated EN-DC | Nokia, Samsung, KDDI, Qualcomm Inc. |
R4-2505720 | DraftCr TS 38.101-1 for RF requirements for type-4 UEs | Huawei, HiSilicon |
R4-2505721 | DraftCr TS 38.101-3 for RF requirements for type-4 UEs | Huawei, HiSilicon |
R4-2505861 | draft CR on requirement for intra-band non-collocated CA | Apple |
R4-2505862 | draft CR on requirement for inter-band non-collocated EN-DC | Apple |
R4-2506268 | Leftover issue for non-collocated | Samsung |
R4-2507177 | draft CR to introduce Rel-19 intra-band non-collocated requirement | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2505863 | draft CR on scheduling availability for non-collocated CA | Apple |
R4-2506217 | 38133CR on MTTD/MRTD for intra-band non-collocated scenarios Phase 2 (resubmission) | Nokia, Nokia Shanghai Bell |
R4-2506576 | draftCR on interruption requirements for NonCol_intraB | ZTE Corporation, Sanechips |
R4-2506728 | Discussion on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) | Huawei, HiSilicon |
R4-2506729 | Draft CR on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) | Huawei, HiSilicon |
R4-2507259 | Draft CR on interruption requirements for Type 4 EN-DCNR-CA | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2507563 | Topic summary for [115][124] FS_NR_DL_Frag_Carrier | Moderator (Mediatek) |
TDoc | Title | Source |
---|---|---|
R4-2506065 | TP to TR 38.755 on Clause 6 | CATT |
R4-2506835 | TP to TR 38.755 on fallback behaviour | vivo |
R4-2506984 | draft update TR38755-030 | MediaTek Inc. |
R4-2506986 | TP for TR38.755: Summary for NR FR1 DL fragment carriers study | MediaTek Inc. |
R4-2507376 | TPs to TR 38.755 with aspects of Fragmented CA | Nokia |
R4-2507391 | TP to TR 38.755 on UE indication to the network | Ericsson |
R4-2507475 | TP for TR 38.755 on UE's fallback behavior | Huawei, HiSilicon |
R4-2507476 | TP for TR 38.755 on triggering condition | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505783 | TP to TR 38.755 on RF requirements evaluation | Xiaomi |
R4-2505784 | Methods for reducing the number of UE Rx chains | Xiaomi |
R4-2505885 | On methods for reducing the number of UE Rx chains for fragmented carriers | Apple |
R4-2506165 | UE architecture switching process | Qualcomm Incorporated |
R4-2506377 | View the methods for reducing the number of UE Rx chain | ZTE Corporation, Sanechips |
R4-2506543 | Discussion on methods for reducing the number of UE RX chains | Spreadtrum,UNISOC |
R4-2506836 | Discussion on methods for reducing the number of UE RX chains | vivo |
R4-2506994 | Discussion on signalling aspects | MediaTek Inc. |
R4-2507004 | Discussion on methods for reducing the number of UE Rx chains for fragmented carriers | Google Korea LLC |
R4-2507219 | TP to TR 38.755: on UE indication of supporting FR1 fragmented carriers | CHTTL |
R4-2507264 | Discussion on methods for reducing the number of UE Rx RF chains | Nokia |
R4-2507320 | Discussion on reducing the number of UE Rx chains | OPPO |
R4-2507392 | Discussion on signaling aspects of fragmented carriers | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505785 | Impacts on UE RF requirements and DL performance | Xiaomi |
R4-2505886 | On UE RF requirements for fragmented carriers | Apple |
R4-2506270 | TP for TR 38.755 on RF requirements evaluation for fragmented carriers from company S | Samsung |
R4-2506376 | TP to TR 38.755 on UE RF requirements evaluation for fragmented carriers | Spreadtrum,UNISOC |
R4-2506378 | TP to TR38.755 on UE RF requirements impact for fragmented carriers | ZTE Corporation, Sanechips |
R4-2506996 | Summary on the evaluation results and further discussion on the one Rx RF chain mode applicability | MediaTek Inc. |
R4-2507321 | Discussion on impacts on UE RF requirements | OPPO |
R4-2507375 | Discussion on RF requirements for Fragmented CA | Nokia |
R4-2507393 | Discusson on impact on UE RF requirement of fragmented carriers | Ericsson |
R4-2507477 | TP for TR 38.755 on RF performance | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505455 | On PC2 RedCap UE FDD band 1Rx REFSENS | Apple |
R4-2507564 | Topic summary for [115][125] NR_PC2_RedCap_UE | Moderator (ChinaTelecom) |
TDoc | Title | Source |
---|---|---|
R4-2505460 | PC2 RedCap REFSENS | Murata Manufacturing Co Ltd. |
R4-2505534 | Discussion on the Rel-19 PC2 FDD RedCap UE | Huawei, HiSilicon |
R4-2505759 | Discussion on PC2 RedCap RSD | Xiaomi |
R4-2506024 | Discussion on UE RF requirements for RedCap PC2 FDD | CATT |
R4-2506025 | Draft CR for 38.101-1: Introduction on power class 2 RedCap for TDD bands and FDD bands | CATT |
R4-2506121 | PC2 RedCap UE RF requirements | Nokia |
R4-2506384 | On PC2 RedCap in FR1 | ZTE Corporation, Sanechips |
R4-2507001 | Further discuss RF Rx requirements for PC2 RedCap in FDD bands | China Telecom |
R4-2507002 | CR for 38.101-1 to introduce PC2 RedCap | China Telecom |
R4-2507072 | RedCap PC2 FDD REFSENS | Qualcomm France |
R4-2507176 | draft CR to introduce PC2 FDD Redcap | OPPO |
R4-2507178 | on FDD PC2 Redcap | OPPO |
R4-2507499 | RF Impact for FDD bands for PC2 RedCap | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505556 | Topic summary for [115][207] NR_LBCA_Sw | Moderator (Apple) |
R4-2507565 | Topic summary for [115][126] NR_LBCA_Sw | Moderator (Apple) |
TDoc | Title | Source |
---|---|---|
R4-2505344 | UE features for low band CA via switching | TELUS |
R4-2506072 | TP to TR 38.768 on clause 4 (Scenarios) | CATT |
TDoc | Title | Source |
---|---|---|
R4-2505322 | Discussion on LB-LB switching | Huawei, Hisilicon |
R4-2505323 | draftCR to 38.101-1: Time mask for LB-LB switching | Huawei, Hisilicon |
R4-2505439 | UE RF requirements for LB CA via switching | Apple |
R4-2505675 | Considerations for Tx on-off time mask for NR_LBCA_Sw | Nokia |
R4-2505781 | Discussion on LB-CA RRM requirements | Xiaomi |
R4-2505786 | LB (FDD) – LB (SDL) CA with switching | Xiaomi |
R4-2505787 | TP to TR 38.768 on Time mask for switching | Xiaomi |
R4-2505841 | On CA_n5-n8 switching between 1UL2DL and 1DL2UL | Skyworks Solutions Inc. |
R4-2506066 | Further discussion on UE RF requirements for low band CA via switching | CATT |
R4-2506166 | Switching time diagram | Qualcomm Incorporated |
R4-2506196 | TP for 38.768: switching period location and time masks | Ericsson |
R4-2506197 | Draft CR for 38.101.1: time masks for DL-only CA via switching | Ericsson |
R4-2506201 | Discussion on UE RF requirements of LB carrier aggregation | LG Electronics |
R4-2506382 | View on low-low band CA via switching | ZTE Corporation, Sanechips |
R4-2506448 | Discussion on UE RF requirements for LB-LB CA switching | Spreadtrum,UNISOC |
R4-2506864 | Discussion of UE RF impact for LB-LB switching | vivo |
R4-2507060 | Discussion on low-band CA switching time mask and fallback applicapability | MediaTek Inc. |
R4-2507527 | Views on UE RF aspects for LB CA via switching | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505512 | RRM requirements for low band carrier aggregation via switching | Qualcomm Incorporated |
R4-2505716 | Discussion on RRM requirements for low band carrier aggregation via switching | OPPO |
R4-2505927 | On RRM requirement for R19 LB CA | Apple |
R4-2505928 | TP on 38.768 NR_LBCA_Sw RRM | Apple |
R4-2506000 | Discussion on the impacts of low band CA via switching on RRM requirements | CATT |
R4-2506236 | Discussion on RRM requirements for Low Band CA operation | LG Electronics Inc. |
R4-2506454 | Further discussion on RRM requirements for LB CA via switching_v2 | vivo |
R4-2506739 | Discussion on low band carrier aggregation via switching | Huawei, HiSilicon |
R4-2507056 | Discussion on RRM core requirements for LB CA via switching | Ericsson |
R4-2507249 | Discussion on RRM requirements for LB CA switching | Samsung |
R4-2507293 | Discussion on RRM aspects of R19 Low band carrier aggregation via switching | ZTE Corporation, Sanechips |
R4-2507385 | Discussion on LBCA RRM requirements | Nokia |
R4-2507578 | Discussion on low-band CA switching | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505557 | Topic summary for [115][208] NR_FR1_7MHz_BW | Moderator (China Telecom) |
R4-2507566 | Topic summary for [115][127] NR_FR1_7MHz_BW | Moderator (Ericsson) |
R4-2507867 | Topic summary for [115][335] NR_7MHz_demod | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2506061 | draftCR to TS 38.115-1 on 7MHz channel bandwidth | CATT |
TDoc | Title | Source |
---|---|---|
R4-2505428 | On the introduction of 7MHz CBW | Apple |
R4-2505719 | A-MPR requirements for 7MHz channel bandwidth | Huawei Technologies France |
R4-2506062 | Further discussion on UE RF requirements for 7MHz channel bandwidth | CATT |
R4-2506149 | 7 MHz channel BW: UE RF and system parameters | Ericsson |
R4-2506185 | Reply LS to RAN2 on Signalling for 7 MHz Channel Bandwidth | T-Mobile USA |
R4-2506318 | Discussion on A-MPR of 7MHz for band n26 | ZTE Corporation, Sanechips |
R4-2506518 | n26 7 MHz A-MPR simulations and proposals | Nokia |
R4-2507651 | Band n26 A-MPR Analysis for 7 MHz Channel Bandwidth | Qualcomm Incorporated |
R4-2507652 | 7 MHz Channel Bandwidth for n5 and n26 | Qualcomm Incorporated |
R4-2507653 | PC2 UE : Band n26 A-MPR Analysis for 7 MHz Channel Bandwidth | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505802 | draftCR to 38.141-1 on introduction of RF requirements for 7MHz channel bandwidth | Nokia |
R4-2505803 | On BS RF requirements due to introduction of 7MHz channel bandwidth | Nokia |
R4-2506063 | Further discussion on BS RF requirements for 7MHz channel bandwidth | CATT |
R4-2506150 | 7 MHz channel BW: BS RF impacts | Ericsson |
R4-2506151 | Running CR to TS 38.104 - Introduction of 7 MHz channel BW | Ericsson |
R4-2506152 | CR to TS 38106 - 7 MHz channel BW clarification | Ericsson |
R4-2506153 | CR to TS 37113 - Introduction of 7 MHz channel BW | Ericsson |
R4-2506323 | Discussion on BS RF requirements for supporting 7 MHz NR FR1 channel bandwidth | ZTE Corporation, Sanechips |
R4-2506324 | Draft CR to TS37.141 Introduction of 7 MHz NR FR1 channel bandwidth | ZTE Corporation, Sanechips |
R4-2506325 | Draft CR to TS38.113: Introduction of 7 MHz NR FR1 channel bandwidth | ZTE Corporation, Sanechips |
R4-2506473 | Draft CR to TS37.141: Introduction of 7 MHz NR FR1 channel bandwidth | ZTE Corporation, Sanechips |
R4-2507437 | Discussion on BS RF in-channel selectivity requirement for 7 MHz channel bandwidth | Huawei, HiSilicon |
R4-2507438 | Draft CR to TS 37.105: 7MHz channel bandwidth introduction | Huawei, HiSilicon |
R4-2507439 | Draft CR to TS 37.145-1: 7MHz channel bandwidth introduction | Huawei, HiSilicon |
R4-2507440 | Draft CR to TS 37.145-2: 7MHz channel bandwidth introduction | Huawei, HiSilicon |
R4-2507441 | Draft CR to TS 38.141-2: 7MHz channel bandwidth introduction | Huawei, HiSilicon |
R4-2507442 | Draft CR to TS 38.176-2: restriction of 7MHz channel bandwidth introduction | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2506330 | Discussion on RRM performance requirements for NR FR1 7 MHz Channel Bandwidth | China Telecom |
R4-2506780 | Discussion on performance requirements for 7MHz | Huawei, HiSilicon |
R4-2507157 | RRM impact of 7 MHz channel bandwidth | Ericsson |
R4-2507880 | RRM requirements for 7MHz Channel BW | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505387 | Discussion on demodulation aspects for NR FR1 7 MHz Channel Bandwidth | China Telecom |
R4-2505496 | Views on NR FR1 7MHz CBW for UE Demod | Qualcomm Incorporated |
R4-2505900 | On UE Demodulation and CSI Reporting Requirements for 7MHz | Apple |
R4-2505972 | View on demodulation requirement for 7MHz | Samsung |
R4-2506444 | Discussion on UE_BS demodulation performance requirements for 7 MHz CBW | Nokia |
R4-2506634 | Discussion on Rel-19 NR FR1 7 MHz Channel Bandwidth performance requirements | Ericsson |
R4-2506675 | Discussion on UE demodulation and CSI performance requirements for 7MHz CHBW | Samsung |
R4-2506952 | Discussion on UE and BS demodulation and CSI performance requirements for 7MHz channel bandwidth | ZTE Corporation, Sanechips |
R4-2507031 | Discussion on UE and BS performance requirements for 7MHz | Huawei, HiSilicon |
R4-2507032 | Work plan on UE and BS performance requirements for 7MHz | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2507850 | Topic summary for [115][318] 5G_Broadcast_GSO_NTN_band | Moderator (Astrum) |
TDoc | Title | Source |
---|---|---|
R4-2505515 | Draft CR to TS 36.102: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite | ASTRUM MOBILE PTE. LTD. |
R4-2505517 | Big CR to TS 36.102: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite | ASTRUM MOBILE PTE. LTD. |
R4-2505738 | On UE RF requirements for 5G broadcast utilizing a geosynchronous satellite | Qualcomm Incorporated |
R4-2505739 | Draft CR to TS 36.102: UE RF requirements for 5G broadcast for geosynchronous satellite (Reference sensitivity and RMC) | Qualcomm Incorporated |
R4-2505740 | Draft CR to TS 36.102: UE RF requirements for 5G broadcast for geosynchronous satellite (Maximum input level and ACS) | Qualcomm Incorporated |
R4-2506232 | Discussion on UE RF requirements for supporting new SDO band for LTE-based 5G Broadcast | ZTE Corporation, Sanechips |
R4-2506234 | Draft CR to TS36.102 Introduction of New band for 5G Broadcast Utilizing Geosynchronous Satellite | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505516 | Draft CR to TS 36.108: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite | ASTRUM MOBILE PTE. LTD. |
R4-2505527 | Big CR to TS 36.108: New LTE band for 5G broadcast for region 3 utilizing a geosynchronous satellite | ASTRUM MOBILE PTE. LTD. |
R4-2506233 | Discussion on SAN RF requirements for supporting new SDO band for LTE-based 5G Broadcast | ZTE Corporation, Sanechips |
R4-2506235 | Draft CR to TS36.108 Introduction of New band for 5G Broadcast Utilizing Geosynchronous Satellite | ZTE Corporation, Sanechips |
R4-2507831 | Follow-up on SAN RF way forward agreements | Huawei, HiSilicon |
R4-2507832 | Draft CR to TS 36.108: Output power dynamics and Transmitted signal quality | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505558 | Topic summary for [115][209] NR_IoT_NTN_req_test_enh | Moderator (Xiaomi) |
R4-2507567 | Topic summary for [115][128] NR_IoT_NTN_HPUE_part1 | Moderator (Samsung) |
R4-2507568 | Topic summary for [115][129] NR_IoT_NTN_HPUE_part2 | Moderator( Vivo) |
R4-2507842 | Topic summary for [115][310] NR_IoT_NTN_less_than_5MHz_UERF | Moderator (Xiaomi) |
R4-2507843 | Topic summary for [115][311] NR_IoT_NTN_less_than_5MHz_BSRF | Moderator (Nokia) |
R4-2507856 | Topic summary for [115][324] NTN_testing_NGSO_channel_model_and_demod | Moderator (Samsung) |
R4-2507857 | Topic summary for [115][325] NR_IoT_NTN_less_than_5MHz_demod | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2507163 | Draft bigCR to TR 38.863 for NTN HPUE | Samsung |
R4-2507164 | Draft bigCR to TS 38.101-5 for NR-NTN HPUE | Samsung |
R4-2507788 | On less than 5 MHz CBW for NTN and HPUE for NTN UE capabilities for Rel-19 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506044 | DraftCR for TR 38.863, Introduction on UE Transmission characteristics for NTN HPUE | CATT |
R4-2507165 | Draft CR to TR 38.863 for NTN HPUE co-ex studies | Samsung, CATT, China Telecom, Ericsson, LGE, Mediatek, OPPO, Thales, vivo, Xiaomi, ZTE |
R4-2507671 | On NR NTN and IoT NTN HPUE co-existence | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505761 | RF requirements for NR-NTN | xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2505417 | On restricted set of power back-off simulations for the satellite band UE Tx requirements | Apple |
R4-2505418 | Initial power back-off results for PC2 on NTN L-/S-band | Apple, Globalstar |
R4-2505419 | Initial power back-off results for PC2 on NTN S-band | Apple |
R4-2505420 | Introduction of NTN HPUE to TR 38.741 | Apple, Globalstar |
R4-2505537 | Discussion on Tx requirements for NR NTN HPUE | Huawei, HiSilicon |
R4-2505538 | Draft CR for TS 38.101-5 to introduce ACLR and additional spurious emission for NR NTN HPUE | Huawei, HiSilicon |
R4-2506042 | Discussion on UE Tx requirement for NTN support HPUE | CATT |
R4-2506856 | NR NTN HPUE Tx Requirements | vivo |
R4-2506990 | Views on HPUE for NR-NTN | CSCN |
R4-2507091 | NR-NTN HPUE RF requirements for Tx | Nokia |
R4-2507166 | Draft CR to TS 38.101-5 for section 6.1 and 6.2 | Samsung, China Telecom, OPPO, Xiaomi |
R4-2507167 | Discussion on NR-NTN HPUE Tx requirements | Samsung |
R4-2507322 | Discussion on Tx requirements for NR-NTN HPUE | OPPO |
R4-2507763 | NR NTN HPUE Tx requirements | Qualcomm Incorporated |
R4-2507775 | On power boosting options for PC2 NR-NTN | Skyworks Solutions Inc. |
R4-2507784 | On the UE RF Tx requirements for NR-NTN HPUE | Ericsson |
R4-2507789 | (NR_IoT_NTN_req_test_enh-Core) draftCR to 38.863: Introduction of ACLR requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506043 | Discussion on UE Rx requirement for NTN support HPUE | CATT |
R4-2506253 | Discussion on Rx requirements for NR NTN HPUE | ZTE Corporation, Sanechips |
R4-2506254 | DraftCR to TR 38.863 Add RSD for NR-NTN HPUE | ZTE Corporation, Sanechips |
R4-2506312 | Discussion for UE RF Rx requirements of NTN_NR_HPUE | LG Electronics France |
R4-2506857 | NR NTN HPUE Rx Requirements | vivo |
R4-2507323 | Discussion on Rx requirements for NR-NTN HPUE | OPPO |
R4-2507774 | On RSD requirements for non-handheld devices | Apple |
R4-2507785 | On the UE RF Rx requirements for NR-NTN HPUE | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505760 | RF requirements for IoT-NTN | xiaomi |
TDoc | Title | Source |
---|---|---|
R4-2505834 | NR and GSM PAs measurements for NB-IoT-NTN HPUE | Skyworks Solutions Inc. |
R4-2506255 | Discussion on Tx requirements for IoT NTN HPUE | ZTE Corporation, Sanechips |
R4-2506327 | Discussion for UE RF Tx requirements of NTN_NR_HPUE | LG Electronics France |
R4-2506858 | Iot NTN HPUE Tx Requirements and further evaluation | vivo, SmarterMicro |
R4-2506860 | draft CR for Iot-NTN MOP related requirements | vivo |
R4-2506920 | R19 on NTN SAR | OPPO |
R4-2507092 | IoT-NTN HPUE RF requirements for Tx | Nokia |
R4-2507168 | Discussion on NTN HPUE SAR solutions | Samsung |
R4-2507324 | Discussion on Tx requirements for IoT-NTN HPUE | OPPO |
R4-2507470 | Draft CR to TS 36.102 for output RF spectrum emissions requirements | MediaTek (Hefei) Inc. |
R4-2507703 | Discussion on IoT-NTN HPUE TX RF requirements | MediaTek (Hefei) Inc. |
R4-2507721 | On IoT NTN HPUE requirements | Huawei, HiSilicon |
R4-2507764 | IoT NTN high power UE Tx requirements | Qualcomm Incorporated |
R4-2507786 | On the UE RF Tx requirements for IoT-NTN HPUE | Ericsson, Sony, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506256 | Discussion on Rx requirements for IoT NTN HPUE | ZTE Corporation, Sanechips |
R4-2506859 | Iot NTN HPUE Rx Requirements | vivo |
R4-2507325 | Discussion on Rx requirements for IoT-NTN HPUE | OPPO |
R4-2507326 | Draft CR to TS 36.102 for section 7 | OPPO |
R4-2507765 | Draft CR to TS 38.101-5: Refsens for NR NTN HPUE | Qualcomm Incorporated |
R4-2507787 | On the UE RF Rx requirements for IoT-NTN HPUE | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506040 | Discussion on system parameter for NTN support spectrum less than 5 MHz | CATT |
TDoc | Title | Source |
---|---|---|
R4-2505421 | Power back-off values for the 3MHz channel in band n256 | Apple |
R4-2505422 | Addition of the 3MHz channel to TS 38.101-5 (sub-clause 6.2) | Apple |
R4-2505423 | Addition of the 3MHz channel to TR 38.863 | Apple, Thales, Echostar, Aalyria Technologies |
R4-2505424 | Addition of the 3MHz channel to TR 38.741 | Apple, Globalstar, Huawei, Nokia |
R4-2505749 | Big CR on UE RF requirements for NTN less than 5MHz | Xiaomi |
R4-2506041 | CR for TS 38.101-5, Correction on UE REFSENS for NTN supporting less that 5 MHz channel bandwidth | CATT |
R4-2507749 | UE RF requirements for NTN less than 5 MHz | Qualcomm Incorporated |
R4-2507750 | Draft CR to TS 38.307: Addition of 3 MHz CBW for NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506257 | CR to TS38.108 Correction of ACS interfering signal type for 3MHz channel bandwidth | ZTE Corporation, Sanechips |
R4-2507082 | Draft CR to TR 38.863 on SAN RF requirements for less than 5MHz | Nokia |
R4-2507083 | Big CR to TS 38.181 to introduce less than 5MHz for NTN | Nokia, ZTE Corporation, Sanechips, CATT, Samsung |
R4-2507098 | draftCR to TS38.181 Correction of ACS interfering signal type for 3MHz channel bandwidth | ZTE Corporation, Sanechips |
R4-2507218 | Draft CR to TR 38.863 on SAN RF requirements for less than 5MHz | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505776 | Big CR on RRM requirements for NTN less than 5MHz in Rel-19 | Xiaomi, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505775 | Discussion on the performance part requirements for less than 5MHz NTN | Xiaomi |
R4-2505822 | Discussion on RRM performance requirements of Rel-19 NR-NTN in less than 5MHz | Samsung |
R4-2506093 | Discussion on less than 5MHz for NTN RRM performance requirements | CATT |
R4-2506349 | Discussion on RRM requirements of NTN with channel BW less than 5MHz | Ericsson |
R4-2506351 | (NR_IoT_NTN_req_test_enh-Perf) Draft CR on Radio Link Monitoring Out-of-sync Test with SSB-based RLM RS in DRX mode for less than 5 MHz BW | Ericsson |
R4-2506781 | Discussion on RRM test cases for less than 5MHz for NTN | Huawei, HiSilicon |
R4-2507191 | Discussion on RRM performance requirements for less than 5M NTN | ZTECorporation,Sanechips |
R4-2507359 | Performance parameters for Less than 5 MHz test cases in NTN | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505500 | Discussion on Less than 5Mhz demodulation for NTN | Nokia |
R4-2505606 | Discussions on demodulation performance requirements for NR-NTN with bandwidth less than 5MHz | QUALCOMM Europe Inc. - Spain |
R4-2505970 | Discussion on NTN demodulation requirements for Less than 5MHz | Samsung |
R4-2506630 | Discussion on Rel-19 NR NTN less than 5MHz requirements | Ericsson |
R4-2506631 | Simulation results on Rel-19 NR NTN less than 5MHz requirements | Ericsson |
R4-2507026 | Discussion on less than 5MHz for NR NTN demodulation performance requirements | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505600 | Discussion on channel modeling for NTN testing for NGSO | QUALCOMM Europe Inc. - Spain |
R4-2505968 | Discussion on NTN testing NGSO channel model | Samsung |
R4-2506282 | Views on TE emulated channel model for satellite mobility | Anritsu Corporation |
R4-2506950 | Discussion on NTN_testing_NGSO_channel_model | ZTE Corporation, Sanechips |
R4-2507024 | Discussion on NTN testing for NGSO channel model | Huawei, HiSilicon |
R4-2507103 | TE-emulated channel model for NTN UE tests | Ericsson |
R4-2507113 | Discussion on NSGO channel model for NTN testing | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505774 | Discussion NGSO NTN RRM testing | Xiaomi |
R4-2505823 | Discussion on RRM impacts by using NGSO in the test | Samsung |
R4-2506350 | Discussion on the impact of NTN testing for NGSO to RRM performance | Ericsson |
R4-2506782 | Discussion on RRM testing for NGSO | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505501 | Discussion on NTN testing for NGSO | Nokia |
R4-2505601 | Discussions on demodulation performance requirements for NTN testing for NGSO | QUALCOMM Europe Inc. - Spain |
R4-2505969 | Discussion on demodulation requirement for NTN NGSO testing | Samsung |
R4-2506283 | Demodulation test time issue with LEO-600 | Anritsu Corporation |
R4-2507025 | Discussion on NTN testing for NGSO demodulation performance requirements | Huawei, HiSilicon |
R4-2507104 | UE demodulation requirements with time varying Doppler shift and propagation delay model | Ericsson |
R4-2507114 | Discussions on demodulation performance requirements for NGSO channel model | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505559 | Topic summary for [115][210] NR_NTN_Ku_bands | Moderator (Apple) |
R4-2505737 | Running CR for 38.101-5 Ku bands | Eutelsat Group |
R4-2507844 | Topic summary for [115][312] NR_NTN_Ku_Band_General | Moderator (Eutelsat) |
R4-2507845 | Topic summary for [115][313] NR_NTN_Ku_Band_Coexistence | Moderator (Intelsat) |
R4-2507846 | Topic summary for [115][314] NR_NTN_Ku_Band_UE_SAN_RF | Moderator (CHTTL) |
TDoc | Title | Source |
---|---|---|
R4-2506142 | NTN Ku-band - bands numbering | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505718 | Ku Band Co-existence: Performance of 45x45 and 78x78 Element Phase Array Antennas | Intelsat |
R4-2505747 | Coexistence simulation results between TN and NTN for Ku band | Qualcomm Incorporated |
R4-2505762 | Temporary calibration results and simulation results for the Ku-band NTN coexistence study | xiaomi |
R4-2506020 | Further discussion on coexistence evaluations for Ku-band for NR NTN | CATT |
R4-2506258 | Discussion on coexistence study for NR NTN Ku band | ZTE Corporation, Sanechips |
R4-2507169 | Discussion on Ku-band coexsitence studies | Samsung |
R4-2507672 | On co-existence simulation assumptions for NR NTN Ku band | Ericsson |
R4-2507673 | On co-existence simulation results for NR NTN Ku band | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506021 | Further discussion on system parameters for Ku-band for NR NTN | CATT |
R4-2506143 | NTN Ku-band - system parameters aspect | Ericsson |
R4-2506259 | Discussion on system parameters for NR NTN Ku band | ZTE Corporation, Sanechips |
R4-2506869 | Draft CR to 38.101-5 on restriction of simultaneous operation of FR1-NTN and FR2-NTN numerology for Ku band | vivo |
R4-2506931 | Discussion on Ku-band VSAT Variable Tx-Rx frequency | LG Electronics Finland |
R4-2507160 | Discussion on the remaining system parameters for NR NTN Ku band | CHTTL |
R4-2507162 | draft CR for updates to NTN Ku-band channel raster sections | CHTTL |
TDoc | Title | Source |
---|---|---|
R4-2505535 | Discussion on VSAT requirements for NR NTN Ku band | Huawei, HiSilicon |
R4-2505536 | Draft CR for TS 38.101-5 to introduce ACS and blocking characteristics for Ku band | Huawei, HiSilicon |
R4-2506144 | NTN Ku-band - NTN VSAT RF requirements | Ericsson |
R4-2506146 | Draft CR to 38101-5 - Off axis EIRP emissions density | Ericsson |
R4-2506147 | Draft CR to 38101-5 - Receiver antenna off-axis performance | Ericsson |
R4-2506260 | Discussion on UE RF requirements for NR NTN Ku band | ZTE Corporation, Sanechips |
R4-2506261 | DraftCR to TS38.101-5 Add 9.5.1, 9.5.2 and 9.7 requirements for NTN Ku bands | ZTE Corporation, CHTTL |
R4-2506262 | DraftCR to TS38.101-5 Add 9.5.3 requirement for NTN Ku bands | ZTE Corporation, Sanechips |
R4-2506290 | Consideration of beam angle on beam gain degradation for minimum EIRP discussion | Sharp |
R4-2506529 | Discussion on NTN Ku band VSAT RF requirements | MediaTek (Wuhan) Inc. |
R4-2506585 | Discussion on UE RF requirements for NR NTN Ku band | SKY Perfect JSAT Corporation |
R4-2506662 | Draft CR to TS 38.101-5 adding NTN Ku band VSAT maximum output power requirement | SKY Perfect JSAT Corporation, CHTTL |
R4-2507090 | On Ku-band VSAT reference sensitivity and maximum input level | LG Electronics Finland |
R4-2507099 | Draft CR for Ku-band VSAT OTA Reference Sensitivity and Maximum Input Level | LG Electronics Finland |
R4-2507147 | Discussion on the regulations related VSAT requirements for the uplink 13.75~14.0 GHz band | CHTTL, SGS Wireless |
R4-2507172 | Further discussion on the EIRP, EIS and the maximum input level requirement for the Rel.19 NTN Ku band VSAT | CHTTL |
R4-2507716 | Discussion on NR NTN UE requirement for Ku bands | Nokia |
R4-2507873 | On VSAT UE RF requirements for Ku-band | THALES |
TDoc | Title | Source |
---|---|---|
R4-2506022 | Further discussion on SAN RF core requirements for Ku-band for NR NTN | CATT |
R4-2506023 | Draft CR for 38.108, Introduction of OTA reference sensitivity level and FRCs for Ku-band for NR NTN | CATT |
R4-2506145 | NTN Ku-band - SAN requirements | Ericsson |
R4-2506263 | Discussion on SAN RF requirements for NR NTN Ku band | ZTE Corporation, Sanechips |
R4-2506264 | DraftCR to TS38.108 Add 10.4 and 10.5 requirements for NTN Ku bands | ZTE Corporation, Sanechips |
R4-2506293 | Discussion on SAN EIS requirements for NR NTN Ku band | LG Electronics Inc. |
R4-2507170 | Discussion on Ku-band SAN RF requirements | Samsung |
R4-2507171 | Draft CR to TS 38.108 to add 10.6 and 10.9 requirements for Ku-band NTN | Samsung |
R4-2507220 | draft running CR to TS 38.108 the SAN requirement of the NR NTN Ku band | CHTTL |
R4-2507717 | Discussion on NR NTN SAN requirement for Ku bands | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505851 | RRM performance requirements for UEs with directional antenna | Eutelsat Group |
R4-2506237 | Discussion on RRM requirements for Ku-band NTN | LG Electronics Inc. |
R4-2506352 | Discussion on RRM requirements for Ku bands for NR NTN | Ericsson |
R4-2506353 | (NR_NTN_Ku_bands-Core) Draft CR on signalling characteristics for NR_NTN_Ku_Band | Ericsson |
R4-2506480 | Discussion on RRM requirements for Ku bands for NR NTN | MediaTek inc. |
R4-2506481 | DraftCR on uplink timing requirements for mobile VSAT served by NGSO | MediaTek inc. |
R4-2506783 | Discussion on RRM requirements for NTN in Ku band | Huawei, HiSilicon |
R4-2506784 | draftCR on applicability of requirements for Ku band NTN | Huawei, HiSilicon |
R4-2507190 | Discussion on RRM requirements for Ku band NTN | ZTECorporation,Sanechips |
R4-2507200 | (NR_NTN_Ku_bands-Core) Definitions,symbols and abbreviations | ZTECorporation,Sanechips |
R4-2507201 | (NR_NTN_Ku_bands-Core) RRC IDLE state mobility | ZTECorporation,Sanechips |
R4-2507202 | (NR_NTN_Ku_bands-Core) Signalling characteristics | ZTECorporation,Sanechips |
R4-2507360 | Requirements for NTN UEs on Ku band operation | Nokia |
R4-2507361 | DraftCR to TS 38.133 for including measurement procedures for VSAT UEs operating in KU band | Nokia |
R4-2507810 | RRM requirements for VSAT UE in Ku band | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505560 | Topic summary for [115][211] NR_ATG_enh | Moderator (CMCC) |
R4-2507569 | Topic summary for [115][130] NR_ATG_enh | Moderator (CMCC) |
R4-2507837 | Topic summary for [115][305] NR_ATG_enh | Moderator (ZTE) |
R4-2507860 | Topic summary for [115][328] NR_ATG_enh_demod | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R4-2505867 | draft CR on ATG UE MOP requirement | Apple |
TDoc | Title | Source |
---|---|---|
R4-2505532 | Discussion on Rel-19 ATG UE RF with DL inter-band CA_n3-n39 | Huawei, HiSilicon |
R4-2505533 | Draft CR for TS 38.101-1 to introduce Intermodulation characteristics for ATG UE supporting CA | Huawei, HiSilicon |
R4-2506310 | Discussion for ATG UE RF requirements | LG Electronics France |
R4-2506328 | Draft CR to TS 38.101-1 for Rel-19 ATG UE REFSENS requirements | LG Electronics France |
R4-2506365 | Draft CR for 38.101-1 to Introduce R19 ATG enhancement UE RF requirements | CMCC |
R4-2506367 | Discussion on UE RF requirements for ATG with inter-band CA | CMCC |
R4-2506941 | Views on Rel-19 ATG UE RF requirements | Qualcomm Incorporated |
R4-2506942 | Draft CR to TS 38.101-1: Maximum input level and ACS requirements for ATG CA | Qualcomm Incorporated |
R4-2507061 | Draft CR for TS 38.101-1 to Introduce R19 ATG enhancement UE RF requirements | CMCC |
R4-2507395 | Draft CR for TS 38.101-1 to introduce blocking characteristic, spurious response for ATG UE CA | Ericsson |
R4-2507509 | Discussion on RF requirement for Inter-band CA for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2507510 | Draft CR to TS 38.101-1: the introduction of ATG UE in clause 6.3J and 6.4J | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2507396 | Discussion on power declaration on ATG UE CA and MIMO in the feature list | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506026 | (NR_ATG_enh-Perf)CR for 38.141-1, Introduction of R19 ATG enhancement BS RF requirements | CATT, ZTE Corporation, CMCC, Huawei, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505868 | draft CR on ATG UE Scell activation/deactivation requirement and active BWP switching delay | Apple |
R4-2506094 | Discussion on enhancements for Rel-19 ATG RRM core requirements | CATT |
R4-2506095 | Draft CR to TS 38.133 on general measurement requirement for ATG | CATT |
R4-2506096 | Draft CR to TS 38.133 on CSI-RS based L3 measurements for ATG | CATT |
R4-2506238 | Discussion on RRM core requirements for ATG CA operation | LG Electronics Inc. |
R4-2506240 | Draft CR on L1-RSRP measurements for Reporting for ATG CA in Clause 9.5D | LG Electronics Inc. |
R4-2506411 | Discussion on RRM core requirements for R19 ATG | CMCC |
R4-2506412 | draftCR on requirement applicability and cell re-selection requirement introduction for ATG CA | CMCC |
R4-2506413 | LS on UE signaling design for NR ATG enh | CMCC |
R4-2506802 | Discussions on RRM core requirements for Rel-19 ATG | Huawei, HiSilicon |
R4-2506804 | CR on core requirements for Rel-19 ATG | Huawei, HiSilicon |
R4-2506823 | draftCR for MRTD and interruption requirements for ATG UE in R19 | Intel Corporation |
R4-2507284 | Discussion on RRM aspects of R19 ATG | ZTE Corporation, Sanechips |
R4-2507302 | Draft CR on intra-frequency measurement for R19 ATG | ZTE Corporation, Sanechips |
R4-2507303 | Draft CR on inter-frequency measurement for R19 ATG | ZTE Corporation, Sanechips |
R4-2507336 | Discussion on Rel-19 ATG CA in RRM Core Open Issues | Ericsson |
R4-2507338 | Draft CR for ATG Rel-19 Pre-configured measurement gap activation/deactivation delay | Ericsson |
R4-2507339 | Draft CR for L1-SINR measurements for Reporting with ATG | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506097 | Discussion on enhancements for Rel-19 ATG RRM performance requirements | CATT |
R4-2506239 | Discussion on RRM performance requirements for ATG CA operation | LG Electronics Inc. |
R4-2506414 | Discussion on test cases for R19 ATG | CMCC |
R4-2506803 | Discussions on RRM performance requirements for Rel-19 ATG | Huawei, HiSilicon |
R4-2507285 | Discussion on RRM performance of R19 ATG | ZTE Corporation, Sanechips |
R4-2507337 | Discussions on Rel-19 ATG CA RRM Performance Enhancement | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505971 | View on BS demodulation requirement for ATG | Samsung |
R4-2506415 | Discussion on demodulation and CSI requirements for Rel-19 ATG | CMCC |
R4-2506951 | Discussion on Rel-19 ATG demodulation requirements | ZTE Corporation, Sanechips |
R4-2507142 | Discussion on ATG enhancement demodulation requirement | Ericsson |
R4-2507143 | Simulation on ATG enhancement demodulation | Ericsson |
R4-2507623 | On Enhancements for Air-to-ground network for NR | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2507834 | Topic summary for [115][302] NR_BS_RF_Part1_E_EIRP | Moderator (ZTE) |
R4-2507835 | Topic summary for [115][303] NR_BS_RF_Part2_CLTA_SE | Moderator (Huawei) |
R4-2507836 | Topic summary for [115][304] NR_BS_RF_Part3_OTA_TRP | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2506934 | CR to TS 38.104: Requirement set applicability table | NEC |
R4-2507244 | CR to TS 38.106 for introduction of expected EIRP mask core requirement for NCR | Nokia, ZTE Corporation, Ericsson, Huawei, Samsung, Qualcomm, CATT |
R4-2507246 | Draft CR to TR 38.908 with improvements and updates | Nokia |
R4-2507891 | PWS MU to be updated for n104 band | ROHDE & SCHWARZ |
R4-2508910 | PWS MU to be updated for n104 band | ROHDE & SCHWARZ |
TDoc | Title | Source |
---|---|---|
R4-2506307 | Overview of BS-to-BS coupling loss simulation results | Ericsson |
R4-2506308 | CR to TR 37.941: Addition of Rel-19 co-location requirement improvements in subclause 6.4 | Ericsson |
R4-2506309 | CR to TS 38.104: Addition of missing row in applicability table for OTA spatial emission in sub-clause 4.6 | Ericsson |
R4-2507445 | Discussion on CLTA-related aspects | Huawei, HiSilicon |
R4-2507447 | Draft CR to TR 37.941: Background and motivation for CLTA alternatives discussion | Huawei, HiSilicon |
R4-2507468 | Big CR to TR 37.941: Rel-19 CLTA-related agreements | Huawei, HiSilicon |
R4-2507511 | Further discussion on OTA test enhancement | ZTE Corporation, Sanechips |
R4-2507512 | Draft CR to TR 37.941: Impact of BS-to-BS isolation analysis on the legacy co-location requirements | ZTE Corporation, Sanechips |
R4-2507633 | On OTA test enhancements | Nokia |
R4-2507634 | DraftCR to TR 37.941 on CLTA alternatives - wideband horn antenna | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506535 | Views on BS FR1 transmitter co-existence spurious emission requirements | Qualcomm Germany |
R4-2507446 | Tx spurious emissions co-existence limits re-evaluation | Huawei, HiSilicon |
R4-2507513 | Further discussion on Coexistence spurious emission requirements | ZTE Corporation, Sanechips |
R4-2507635 | On TX co-existence spurious emissions requirements | Nokia |
R4-2507670 | On Transmitter Spurious Emission Co-existence discussion | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2506935 | CR to TS 38.141-2: Correction on the test procedure | NEC |
R4-2506936 | CR to TR 38.908: Correction on the test procedure | NEC |
R4-2507154 | CR to TS 38.141-2: improvements related to Expected EIRP for band n104 | Ericsson |
R4-2507247 | Draft CR to TS 38.141-2 with updates to OTA spatial emission requirement | Nokia |
R4-2507248 | CR to TS 38.115-2 for introduction of expected EIRP mask conformance test for NCR | Nokia |
R4-2507514 | Discussion on conformance testing for U6GHz BS EEIRP mask | ZTE Corporation, Sanechips |
R4-2507515 | CR to TS 38.908: MU and others | ZTE Corporation, Sanechips |
R4-2507677 | On EEIRP equations and step size equations | Huawei, HiSilicon |
R4-2507678 | Draft CR to TS 38.908 corrctions | Huawei, HiSilicon |
R4-2507679 | Draft CR to TS 38.141-2 EEIRP measurement uncertainty and coordinate alignment | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2506933 | Discussion on OTA test scope reduction | NEC |
R4-2507245 | On BS OTA test scope reduction | Nokia |
R4-2507516 | Discussion on the OTA testing scope reduction | ZTE Corporation, Sanechips |
R4-2507680 | OTA test case reduction | Huawei, HiSilicon |
R4-2507681 | Draft CR to TS 38.141-2 OTA test case reduction for TX IM requirement | Huawei, HiSilicon |
R4-2507729 | OTA test scope reduction | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2507084 | Simplification of BS TRP test methods | Nokia |
R4-2507155 | Discussion and text proposal on improvement of TRP measurement methods in Annex I in TS 38.104 | Ericsson |
R4-2507448 | Further discussion on European Commission’s feedback wrt. alternative test methods | Huawei, HiSilicon |
R4-2507517 | Discussion on the applicability improvement of TRP measurement | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2507869 | Topic summary for [115][337] TRP_TRS_MIMO_OTA_Ph3 | Moderator (vivo) |
TDoc | Title | Source |
---|---|---|
R4-2505842 | CR to add min measurement distance for 50cm QZ | Keysight Technologies UK Ltd, Huawei, Ericsson, Rohde&Schwarz |
R4-2505843 | On Inadequate Range Length MU | Keysight Technologies UK Ltd |
R4-2506876 | CR to TR 38.870 on testing bands | vivo |
R4-2507095 | Discussion on Near-Field to Far-Field Transform Method for OTA TRP Measurement | GIST, RRA, CSU |
R4-2507097 | Draft CR for 38.870 on Abbreviations Section | GIST, RRA, CSU |
R4-2508911 | CR for 38.870 on Abbreviations Section | GIST, RRA |
TDoc | Title | Source |
---|---|---|
R4-2505399 | on XR OTA tests | Huawei, HiSilicon |
R4-2505425 | CR to TS38.161 for an alternate TRS and TRP test procedure for XR devices | Apple |
R4-2505850 | On Split TRP/TRS Grids for Devices with Limited Battery Capacity | Keysight Technologies UK Ltd, Nokia |
R4-2506877 | Remaining issues for XR OTA test method | vivo |
R4-2507005 | Discussion on OTA requirements for XR Headworn Devices | Vodafone, Telecom Italia S.p.A., Deutsche Telekom |
R4-2507094 | Draft CR for split measurement grids method for TRP/TRS measurements | Nokia, Keysight Technologies UK Ltd |
R4-2507366 | CR for split TRP/TRS measurement grids method | Nokia, Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2505397 | on NTN OTA tests | Huawei, HiSilicon |
R4-2505426 | On NTN TRP TRS test methodology | Apple, GIST, NRRA |
R4-2505743 | On FR1 NTN devices OTA | Qualcomm Incorporated |
R4-2505750 | Discussion on test methodology and radiated performance metric for FR1 NTN devices | Xiaomi |
R4-2505849 | On Partial Radiated Surfaces | Keysight Technologies UK Ltd |
R4-2506878 | Remaining issues for NTN OTA test method | vivo |
R4-2506880 | draft CR to 38.870 on NTN OTA performance metric and test method | vivo |
R4-2506972 | Discussion on partial sphere metric | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505396 | On MIMO dynamic OTA tests | Huawei, HiSilicon |
R4-2505435 | On performance metric for UE dynamic MIMO OTA | Apple |
R4-2505844 | On TMT and CTMT metric definitions | Keysight Technologies UK Ltd |
R4-2505845 | TP to TR 38.762: DynMIMO CM Validation Details, Clarifications, and Corrections | Keysight Technologies UK Ltd, CMCC, CAICT |
R4-2505846 | TP to TR 38.762: on performance metrics | Keysight Technologies UK Ltd |
R4-2506284 | On Rel-19 dynamic MIMO OTA | CAICT |
R4-2506285 | TP to 38.762 on General parts | CAICT, SAICT |
R4-2506289 | TR 38.762 V0.4.0 on MIMO OTA dynamic test methodology for FR1 UEs | CAICT |
R4-2506973 | On performance metric for FR1 dynamic MIMO OTA | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505398 | on TRP TRS OTA tests | Huawei, HiSilicon |
R4-2505440 | Views on TRP TRS Performance Part | Apple |
R4-2505441 | CR to TR 38.870 on clarification of UE configuration for UL-MIMO test | Apple |
R4-2505472 | Discussion on Rel-19 TRP TRS requirements | Ericsson Korea Partners Co Ltd |
R4-2505751 | Discussion on TRP and TRS requirements for Size 2 Ues | Xiaomi |
R4-2505810 | Proposals for Rel-19 TRP TRS requirements working procedure | Telecom Italia S.p.A., Vodafone, Deutsche Telekom, Orange |
R4-2506879 | Discussions on Rel-19 OTA performance part | vivo |
R4-2506887 | Measurement results for Rel-19 TRP TRS 2Tx AC lab alignment activity | vivo |
R4-2506932 | Measurement results for Rel-19 TRP TRS 2Tx AC lab alignment activity - CAICT | CAICT. |
R4-2508912 | Measurement results for Rel-19 TRP TRS 2Tx AC lab alignment activity | SGS Wireless |
TDoc | Title | Source |
---|---|---|
R4-2505434 | On FR1 MIMO OTA n3 Channel Model Validation | Apple |
R4-2505752 | Channel model validation results for Band 3, n7, n8 and n77 | Xiaomi |
R4-2506286 | Framework and time plan for Rel-19 MIMO OTA performance requirements development (May 2025) | CAICT |
R4-2506287 | Template for Rel-19 FR1 MIMO OTA Measurement Campaign | CAICT |
R4-2506288 | Channel model validation results for band n3 | CAICT |
TDoc | Title | Source |
---|---|---|
R4-2507870 | Topic summary for [115][338] NR_FR2_OTA | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2505746 | TR 38.771v0.4.0 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505744 | On remaining issue for FR2 OTA test method on STxMP | Qualcomm Incorporated |
R4-2505745 | TP to TR 38.771 for editorial changes | Qualcomm Incorporated |
R4-2506847 | Discussion on the FR2 OTA test method | vivo |
R4-2506848 | TP to TR 38.771 on FR2 sTxMP MU and test tolerance | vivo |
R4-2506974 | On additional Test Tolerance for STxMP testing | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505504 | Discussion on SCM General Items | Nokia |
R4-2507853 | Topic summary for [115][321] NR_SCM | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R4-2505505 | pCR for General Section of TR 38.753 | Nokia |
R4-2506178 | big pCR for TR 38.753 | Nokia |
R4-2507137 | Discussion on general issue of NR SCM for demodulattion | Ericsson |
R4-2507139 | draft TP for TR38.753 Chapter 7 on simulation results alignment | Ericsson |
R4-2507344 | PMI simulation results for SCM | Huawei,HiSilicon |
R4-2507427 | Temporal and Frequency Coherence for MIMO channels in band n78 | BT plc, Ericsson |
R4-2507825 | TP for TR 38.753 Section 6.2 MU-MIMO | BT plc |
R4-2507826 | TP for TR 38.753 Annex A Channel Measurements | BT plc |
TDoc | Title | Source |
---|---|---|
R4-2505383 | TP to TR 38.753: Scope and reference | China Telecom |
R4-2505495 | Performance comparison of high and low-resolution codebook for 32 antenna ports with respect to different subarray sizes | Orange, Fraunhofer |
R4-2505593 | Discussion on spatial channel modelling | MediaTek inc. |
R4-2505594 | Simulation results of spatial channel modelling | MediaTek inc. |
R4-2505595 | TP to TR38.753: TDL approaches and related Annex | MediaTek inc. |
R4-2505901 | Discussion on Spatial Channel Modeling Study | Apple |
R4-2505902 | Simulation Results for Spatial Channel Modeling Study | Apple |
R4-2505903 | Draft TP to TR 38.753 on SCM Study - 5.1 CDL Approach | Apple, Qualcomm |
R4-2505954 | Views on SCM for UE Demodulation | Qualcomm Incorporated |
R4-2505956 | TP to TR38753 on Spatial Channel Modeling for Demod | Qualcomm Incorporated, Apple |
R4-2505957 | Simulation Results for SCM Demod Alignment | Qualcomm Incorporated |
R4-2506027 | TP for 38.753: on definitions of terms, symbols and abbreviations | CATT |
R4-2506172 | Discussion on Spatial Channel Model for Demodulation Performance Requirements | Nokia |
R4-2506173 | Simulation Results and CDL Implementation for Spatial Channel Model for Demodulation Performance Requirements | Nokia |
R4-2506676 | Discussion on spatial channel model for demodulation performance requirements | Samsung |
R4-2506677 | Simulation results on spatial channel model | Samsung |
R4-2506678 | TP for 38.753 on chapter 4 and chapter 2 | Samsung |
R4-2506957 | Discussion on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
R4-2506958 | Simulation results on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
R4-2506959 | TP for 38.753 introduction of spatial channel models for SU-MIMO PMI cases | ZTE Corporation, Sanechips |
R4-2507044 | Discussion on SCM study for demodulation requirements | Huawei, HiSilicon |
R4-2507045 | Simulation results for SCM | Huawei, HiSilicon |
R4-2507046 | Draft TP introduction of comparision of spatial channel models for SU-MIMO PDSCH cases | Huawei, HiSilicon |
R4-2507138 | Discussion on NR SCM methodology for demodulattion | Ericsson |
R4-2507140 | Simulation results for NR SCM methodology | Ericsson |
R4-2507823 | Results collection table for NR SCM | BT plc |
R4-2507824 | Simulation Results for SCM Comparison and Alignment | BT plc |
TDoc | Title | Source |
---|---|---|
R4-2507854 | Topic summary for [115][322] NR_demod_Ph5_Part1_General_BS | Moderator (China Telecom) |
R4-2507855 | Topic summary for [115][323] NR_demod_Ph5_Part2_UE | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R4-2505340 | Discussion on UE demodulation requirements with 8Rx MMSE-IRC receiver | MediaTek inc. |
R4-2505341 | Simulation results for UE demodulation requirements with 8Rx MMSE-IRC receiver | MediaTek inc. |
R4-2505342 | Draft CR on 8Rx PDSCH demodulation requirements under inter-cell interference scenario (TDD) | MediaTek inc. |
R4-2505378 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | China Telecom |
R4-2505379 | Draft CR on UE demodulation performance requirements for TDD 8Rx MU-MIMO | China Telecom |
R4-2505904 | On UE Demodulation Performance Requirements with 8RX | Apple |
R4-2505905 | Simulation results for ICI and MU-MIMO with 8RX | Apple |
R4-2505906 | Summary of Simulation Results for ICI and MU-MIMO with 8RX | Apple |
R4-2505907 | Draft CR for FRCs for ICI requirements with 8RX | Apple |
R4-2506416 | Draft CR to 38.101-4 Introduce the requirement applicability for PDSCH with interference for 8Rx UE | CMCC |
R4-2506417 | Discussion on interference suppressing performance for 8Rx UE | CMCC |
R4-2506418 | Simulation results for 8Rx UE interference suppressing | CMCC |
R4-2506440 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | Nokia |
R4-2506441 | (NR_demod_Ph5-Perf) Draft big CR on 38.101-4 for adding UE demodulation performance requirements for 8Rx with MMSE-IRC | Nokia |
R4-2506474 | On MMSE-IRC receiver for interference mitigation with 8Rx | Ericsson |
R4-2506475 | Simulation results for MMSE-IRC receiver for 8Rx reception | Ericsson |
R4-2506476 | CR to TS38101-4 Minimum requirement for wideband CQI reporting with inter-cell interference [TDD] | Ericsson |
R4-2506679 | Discussion on UE demodulation and CSI performance requirements for 8Rx with MMSE-IRC | Samsung |
R4-2506680 | draftCR on Minimum requirements for FDD PDSCH with intra-cell inter-user interference for 8Rx with MMSE-IRC | Samsung |
R4-2506947 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
R4-2506948 | Simulation results on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
R4-2506949 | Draft CR on 38.101-4 for UE demodulation performance requirements for 8Rx with inter-cell interferenc | ZTE Corporation, Sanechips |
R4-2507033 | Discussion on 8Rx MMSE-IRC performance requirements | Huawei, HiSilicon |
R4-2507034 | Simulation results on 8Rx MMSE-IRC requirements with interference | Huawei, HiSilicon |
R4-2507035 | draft CR on 38.101-4 Introduction of applicability of rules for 8Rx CQI requirements with inter-cell interference | Huawei, HiSilicon |
R4-2507281 | Views on 8Rx UE demodulation and CSI requirements with inter-cell and intra-cell inter-user interference | Qualcomm India Pvt Ltd |
R4-2507340 | Minimum requirement for wideband CQI reporting with inter-cell interference [FDD] | Qualcomm India Pvt Ltd |
TDoc | Title | Source |
---|---|---|
R4-2505380 | Simulation results on BS demodulation performance requirements for MMSE-IRC | China Telecom |
R4-2505381 | Discussion on BS demodulation performance requirements for MMSE-IRC | China Telecom |
R4-2505382 | Draft CR on 38.104: BS demodulation performance requirements for MMSE-IRC | China Telecom |
R4-2505470 | Discussion on BS demodulation performance requirement for MMSE-IRC | Tejas Network Limited |
R4-2505471 | Simulation results on BS demodulation performance requirements for MMSE-IRC | Tejas Network Limited |
R4-2505964 | Simulation results summary for BS requirement with MMSE-IRC receiver | Samsung |
R4-2505965 | View on the remaining issue for BS demodulation requirement with MMSE-IRC receiver | Samsung |
R4-2505966 | Simulation results on BS demodulation requirement with MMSE-IRC receiver | Samsung |
R4-2505967 | draft CR on conducted performance requirements for MMSE-IRC in 38.141-1 | Samsung |
R4-2506017 | Further discussion on BS demodulation performance for MMSE-IRC | CATT |
R4-2506018 | Simulation results for BS requirement with MMSE_IRC receiver | CATT |
R4-2506019 | Draft CR for 38.141-1, Introduction of Manufacturer declaration and pplicability rule for BS requirement with MMSE_IRC receiver | CATT |
R4-2506419 | Discussion on BS demodulation requirements for MMSE-IRC receiver | CMCC |
R4-2506420 | Simulation results for BS interference suppressing with MMSE-IRC | CMCC |
R4-2506533 | Views on BS demodulation requirements for MMSE-IRC | Qualcomm Germany |
R4-2506534 | Simulation results for base station MMSE-IRC receiver | Qualcomm Germany |
R4-2506626 | Discussion on Rel-19 MMSE-IRC BS demodulation requirements | Ericsson |
R4-2506627 | Simulation results on Rel-19 MMSE-IRC BS demodulation requirements | Ericsson |
R4-2506628 | (NR_demod_Ph5-Perf) Draft CR for TS38.141-1 on BS supporting enhanced performance requirements | Ericsson |
R4-2506629 | (NR_demod_Ph5-Perf) Draft CR for TS38.141-2 on BS supporting enhanced performance requirements | Ericsson |
R4-2506944 | Discussion on BS demodulation performance for MMSE-IRC | ZTE Corporation, Sanechips |
R4-2506945 | Simulation results on BS demodulation performance for MMSE-IRC | ZTE Corporation, Sanechips |
R4-2506946 | Draft CR on 38.141-2 for BS demodulation performance requirements for MMSE-IRC | ZTE Corporation, Sanechips |
R4-2507036 | Discussion on remaining issues on BS MMSE-IRC requirements with inter-cell interference | Huawei, HiSilicon |
R4-2507037 | draft CR on 38.141-2 Introduction of manufacturer declaration and applicability rule for MMSE-IRC requirements | Huawei, HiSilicon |
R4-2507152 | Discussion on BS demodulation for NR MMSE-IRC | NTT DOCOMO, INC. |
R4-2507153 | Simulation results for NR MMSE-IRC BS demodulation | NTT DOCOMO, INC. |
R4-2507620 | NR Demodulation Performance Phase 5: BS demodulation performance requirements for MMSE-IRC | Nokia |
R4-2507621 | Simulation Results – NR BS Demodulation Performance Requirements for MMSE-IRC | Nokia |
R4-2507622 | Draft BigCR Rel-19 BS MMSE-IRC in 38.141-2 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505561 | Topic summary for [115][212] NR_RRM_Ph5_Part1 | Moderator (Apple) |
R4-2505562 | Topic summary for [115][213] NR_RRM_Ph5_Part2 | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R4-2505935 | On feature list for RRM phase 5 WI | Apple |
R4-2506828 | Views on RRM enhancements ph5 RAN4 UE features in Rel-19 | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R4-2505507 | FR2-1 L3 measurement delay reduction by optimizing RX beam sweeping factor | Qualcomm Incorporated |
R4-2505658 | On remanining issues on FR 2-1 L3 measurement delay by optimizing Rx beam sweeping factor | vivo |
R4-2505688 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | OPPO |
R4-2505689 | DraftCR on Multi-Rx based RRC Connection Release with Redirection requirements | OPPO |
R4-2505726 | On remaining FBS requirements | Nokia |
R4-2505727 | DraftCR for FBS requirement maintenance | Nokia |
R4-2505889 | On FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Apple |
R4-2505992 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | CATT |
R4-2505993 | draft bigCR on Rx BSF optimization for NR RRM ph5 | CATT |
R4-2505995 | DraftCR on Multi-Rx based inter-frequency measurement with NCSG | CATT, OPPO |
R4-2506227 | Discussions on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | NTT DOCOMO, INC. |
R4-2506241 | Discussion on RRM requirements for FR2-1 L3 measurement delay reduction | LG Electronics Inc. |
R4-2506331 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | China Telecom |
R4-2506359 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Ericsson |
R4-2506362 | (NR_RRM_Ph5-Core) draft CR on Rx BSF optimization for NR RRM ph5 | Ericsson |
R4-2506597 | Discussion on L3 measurement delay reduction by optimizing Rx beam sweeping factor | CMCC |
R4-2506615 | DraftCR for optimizing Rx beam sweeping factor on RRC connection release with redirection to NR | CMCC |
R4-2506702 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Huawei, HiSilicon |
R4-2506703 | DraftCR on FBS L3 measurement for inter-frequency without gap | Huawei, HiSilicon |
R4-2507283 | Discussion on Rx beam factor optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
R4-2507814 | Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505506 | Enhancement on FR2 CSSF | Qualcomm Incorporated |
R4-2505657 | On remaining issues on FR 2-1 L3 measurement delay by optimizaing CSSF outside gap in CADC | vivo |
R4-2505690 | On optimizing CSSF for FR2-1 L3 measurement delay | OPPO |
R4-2505936 | On FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Apple |
R4-2505937 | draft CR for Rel-19 CSSF enhancement solution 1 (one CC measurement per band) | Apple, CATT, Ericsson |
R4-2505994 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CADC | CATT |
R4-2506214 | FR2-1 SSB based L3 measurement delay reduction with CSSF optimization | Nokia, Nokia Shanghai Bell |
R4-2506215 | draftCR on CSSF optimization solutions | Nokia, Nokia Shanghai Bell |
R4-2506332 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | China Telecom |
R4-2506360 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Ericsson |
R4-2506598 | Discussion on L3 measurement delay reduction by optimizing CSSF outside gap in CA/DC | CMCC |
R4-2506797 | Discussion on FR2-1 L3 measurement delay by optimising CSSF outside gap in CA/DC | Huawei, HiSilicon |
R4-2506807 | CR on L3 measurement delay by utilising 3-searcher solution to optimise CSSF outside gap for Rel-19 | Huawei, HiSilicon |
R4-2507282 | Discussion on CSSF optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
R4-2507815 | Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing CSSF | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505996 | CR for fast SCell activation for UE supporting Rel-18 EMR | CATT, Apple, Huawei, HiSilicon |
R4-2506333 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | China Telecom |
R4-2506572 | Discussion on the fast SCell activation for UE supporting Rel-18 EMR | ZTE Corporation, Sanechips |
R4-2506599 | Discussion on fast SCell activation for UE supporting Rel-18 EMR | CMCC |
R4-2506663 | Discussion on RRM core requirements of Fast SCell activation for UE supporting Rel-18 EMR | Ercisson |
R4-2506665 | CR on Scell activation delay requirements for Deactivated PUCCH Scell | Ericsson |
R4-2507221 | Discussion on RRM core requirements of Fast SCell activation for UE supporting Rel-18 EMR | Nokia |
R4-2507222 | draftCR to 38.133 on Fast SCell activation with EMR | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505691 | Discussion on performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode | OPPO |
R4-2505692 | DraftCR on test cases for Multi-Rx based handover | OPPO |
R4-2505728 | On performance requirements of L3 measurement delay reduction | Nokia, Nokia Shanghai Bell |
R4-2505938 | On testing for CSSF enhancement in CA/DC | Apple |
R4-2505997 | Discussion on performance requirements for FR2-1 L3 measurement delay reduction | CATT |
R4-2505999 | DraftCR to define test case for SSB based Inter-frequency measurement delay reduction without MG with fast beam sweeping | CATT |
R4-2506216 | draftCR TC#1 SSB-based intra-f measurement without MG for solution 1 | Nokia, Nokia Shanghai Bell |
R4-2506242 | Discussion on performance requirements for FR2-1 L3 measurement delay reduction | LG Electronics Inc. |
R4-2506334 | Discussion on RRM performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode | China Telecom |
R4-2506361 | Discussion on performance requirements for FR2-1 L3 measurement enhancement | Ericsson |
R4-2506363 | (NR_RRM_Ph5-Perf) Draft CR on SSB based Inter-frequency measurement without MG | Ericsson |
R4-2506600 | Discussion on RRM performance requirements of FR2-1 SSB based L3 measurement delay reduction for connected mode | CMCC |
R4-2506618 | DraftCR on TC on Rx BSF optimization for SSB based Intra-frequency measurement without MG (TC#1) | CMCC |
R4-2506798 | Discussion on performance part for RRM Phase 5 | Huawei, HiSilicon |
R4-2506826 | Test cases requirements for RRC re-establishment and release with redirection | Intel Corporation |
R4-2507256 | Draft CR on measurement delay reduction for SSB based Inter-frequency measurement | Samsung |
R4-2507257 | Test case on measurement delay reduction for SSB based Inter-frequency measurement | Samsung |
R4-2507296 | Discussion on Perf part of Rx beam factor optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
R4-2507301 | Draft CR on Test case of Inter-RAT SSB measurement without MG of R19 CSSF enh | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505693 | Discussion on performance requirements for fast SCell activation for UE supporting Rel-18 EMR | OPPO |
R4-2505869 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | Apple |
R4-2505998 | Discussion on performance requirements of fase SCell activation for UE supporting R18 EMR | CATT |
R4-2506335 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | China Telecom |
R4-2506556 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | vivo |
R4-2506571 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | ZTE Corporation, Sanechips |
R4-2506601 | Discussion on RRM performance requirements for fast SCell activation for UE supporting Rel-18 EMR | CMCC |
R4-2506664 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | Ercisson |
R4-2506704 | Discussion on performance part for Fast SCell activation for UE supporting Rel-18 EMR | Huawei, HiSilicon |
R4-2507223 | Discussion on RRM performance requirements of Fast SCell activation for UE supporting Rel-18 EMR | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505563 | Topic summary for [115][214] LCS_BDS_B2b_LCS_NAVIC_L1_SPS | Moderator (CATT) |
TDoc | Title | Source |
---|---|---|
R4-2506002 | DraftCR for TS 36.171 to introduce BDS B2b signal in A-GNSS | CATT, CAICT |
R4-2506003 | DraftCR for TS 38.171 to introduce BDS B2b signal in A-GNSS | CATT, CAICT |
R4-2507740 | On RRM requirements BDS B2b Signal in A-GNSS | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505493 | Introduction of UE performance requirements for support of NavIC L1 in NR | Reliance Jio, Huawei, Qualcomm MediaTek, Ericsson, CeWiT |
R4-2505494 | Introduction of UE performance requirements for support of NavIC L1 in LTE | Reliance Jio |
TDoc | Title | Source |
---|---|---|
R4-2507741 | On RRM requirements for NavIC L1 SPS AGNSS support in NR & LTE | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2507125 | Collection of simulation results for AI/ML BM | vivo |
R4-2507570 | Topic summary for [115][131] NR_AIML_air_part1 | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2505509 | Generalization aspects of AI-ML | Qualcomm Incorporated |
R4-2505602 | Discussion on general aspects of AIML for NR air interface | CAICT |
R4-2505763 | Discussion on general aspect for AI | Xiaomi |
R4-2505833 | Discussion on General Aspects for AI/ML Air Interface | Korea Testing Laboratory |
R4-2505940 | Discussion on General Aspects on AI/ML for NR Air Interface | Apple |
R4-2506465 | Discussion on general aspects for AI/ML for NR air interface | vivo |
R4-2506505 | Discussion on General aspects | MediaTek Inc. |
R4-2506522 | Discussion on general aspects on AI/ML for NR air interface | OPPO |
R4-2506606 | Discussion on general aspects for AI/ML for NR air interface | CMCC |
R4-2507047 | Discussion on general aspects on AIML for NR air interface | Huawei, HiSilicon |
R4-2507429 | On General Aspects of AI/ML for NR Air Interface Phase 1 | Nokia |
R4-2507737 | On general issues for AIML | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505508 | CSI Prediction: Testing framework | Qualcomm Incorporated |
R4-2505596 | Discussion on CSI reporting requirement framework for CSI prediction | MediaTek inc. |
R4-2505945 | Discussion on CSI Prediction: CSI reporting requirement and testing framework for CSI prediction | Apple |
R4-2505974 | View on CSI reporting requirement and testing framework for CSI prediction | Samsung |
R4-2506466 | Discussion on CSI reporting requirement and testing framework for CSI prediction | vivo |
R4-2506523 | CSI reporting requirement and testing framework for CSI prediction | OPPO |
R4-2506604 | Discussion on CSI reporting requirement and testing framework for CSI prediction | CMCC |
R4-2507048 | Discussion on CSI reporting requirement and testing framework for CSI prediction | Huawei, HiSilicon |
R4-2507105 | Discussion on CSI prediction | Ericsson |
R4-2507532 | CSI reporting requirement and testing framework for CSI prediction | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505478 | RRM core requirement and testing framework for AIML based beam management | Tejas Network Limited |
R4-2505510 | RRM Core Requirements for AI-ML based Beam Management | Qualcomm Incorporated |
R4-2505603 | Discussion on RRM core requirements for beam management | CAICT |
R4-2505741 | Discussion on AI/ML beam management testability | Qualcomm Incorporated |
R4-2505764 | Discussion on core part requirement and testing framework for AI beam management | Xiaomi |
R4-2505942 | Discussion on Beam Management: RRM core requirement and testing framework for beam management | Apple |
R4-2505980 | Discussion on RRM core requirements and testing framework for BM | CATT |
R4-2506228 | Discussions on RRM core requirement for beam management | NTT DOCOMO, INC. |
R4-2506281 | FR2 test setup for AI/ML beam management evaluation | Anritsu Corporation |
R4-2506347 | Discussion on RRM core requirements and test framework for beam management | Ericsson |
R4-2506464 | Draft CR on RRM core requirements for support of AI/ML for NR Air Interface for beam management | vivo |
R4-2506467 | Discussion on RRM core requirement and testing framework for beam management | vivo |
R4-2506506 | Discussion on RRM core requirement and testing framework for beam management | MediaTek Inc. |
R4-2506524 | RRM core requirement and testing framework for beam management | OPPO |
R4-2506602 | Discussion on RRM core requirement and testing framework for beam management | CMCC |
R4-2506981 | Discussion on test setup for AI/ML based beam management | Rohde & Schwarz |
R4-2507022 | Beam Prediction Performance Metrics for Monitoring and Accuracy Requirement | NTU |
R4-2507049 | Discussion on RRM core requirement for AIML Beam management | Huawei, HiSilicon |
R4-2507184 | Discussion on the RRM requirements of AI/ML Beam management | ZTECorporation,Sanechips |
R4-2507430 | RRM core requirements for AI/ML Based Beam Management | Nokia |
R4-2507479 | Further discussion on beam management core requirements | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505947 | Discussion on RRM Core Requirements for positioning accuracy enhancement | Apple |
R4-2505981 | Discussion on RRM core requirements and testing framework for positioning | CATT |
R4-2506468 | Discussion on RRM core requirement and testing framework for Positioning accuracy enhancement | vivo |
R4-2506525 | RRM core requirement and testing framework for Positioning accuracy enhancement | OPPO |
R4-2506607 | Discussion on RRM requirements for positioning accuracy enhancement | CMCC |
R4-2507050 | Discussion on RRM core requirement for AIML Positioning | Huawei, HiSilicon |
R4-2507185 | Discussion on the RRM requirements of AI/ML positioning | ZTECorporation,Sanechips |
R4-2507533 | RRM core requirements and testing framework for AI/ML positioning accuracy enhancement | Nokia |
R4-2507663 | On core requirements for AI/ML based positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505514 | AI-ML BM: Simulation Results | Qualcomm Incorporated |
R4-2505765 | Discussion on performance requirement for AI beam management | Xiaomi |
R4-2505941 | RRM performance requirements for beam management and positioning accuracy | Apple |
R4-2505982 | Discussion on RRM performance requirements for BM and positioning | CATT |
R4-2506469 | Discussion on RRM performance requirements for beam management and positioning accuracy | vivo |
R4-2506526 | RRM performance requirements for beam management | OPPO |
R4-2506603 | Discussion on RRM performance requirements for beam management | CMCC |
R4-2507051 | Discussion on RRM performance requirements for beam management and positioning accuracy | Huawei, HiSilicon |
R4-2507431 | RRM performance requirements for beam management and positioning accuracy | Nokia |
R4-2507664 | On performance requirements for AI/ML based positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505513 | CSI Prediction: Simulation results | Qualcomm Incorporated |
R4-2505946 | Demodulation and/or CSI reporting requirements for CSI prediction | Apple |
R4-2505973 | View on demodulation requirement for AI based CSI prediction | Samsung |
R4-2506470 | Discussion on Demodulation and CSI reporting requirements for CSI prediction | vivo |
R4-2506527 | Demodulation and CSI reporting requirements for CSI prediction | OPPO |
R4-2506605 | Discussion on demodulation for CSI prediction | CMCC |
R4-2506960 | Discussion on demodulation CSI reporting requirements for CSI prediction | ZTE Corporation, Sanechips |
R4-2507052 | Discussion on demodulation andor CSI reporting requirements for CSI prediction | Huawei, HiSilicon |
R4-2507106 | PMI reporting requirements with CSI prediction | Ericsson |
R4-2507624 | On Demodulation and CSI Reporting Requirements for CSI Prediction | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2507571 | Topic summary for [115][132] NR_AIML_air_part2 | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2505943 | General aspects for NR air interface Phase 2 | Apple |
R4-2505953 | Proposed update for TR 38.843 with RAN4 part | CAICT |
R4-2505983 | Discussion on general aspects for AIML for NR air | CATT |
R4-2506471 | Discussion on general aspects for AI/ML for NR air interface Phase 2 | vivo |
R4-2506608 | Discussion on general aspects for study on AI/ML for NR air interface Phase 2 | CMCC |
R4-2507053 | Discussion on general aspects on AIML for NR air interface phase 2 | Huawei, HiSilicon |
R4-2507055 | On AI/ML Model LCM and Performance Monitoring Requirement | NTU |
R4-2507135 | Discussion on General Aspects of AI/ML for NR Air Interface Phase 2 | Nokia |
R4-2507235 | Comprehensive Simulation Analysis on Dataset Alignment, Model Interoperability, and Fine-tuning Impacts | Korea Testing Laboratory |
TDoc | Title | Source |
---|---|---|
R4-2505511 | CSI Compression: Testability and Interoperability | Qualcomm Incorporated |
R4-2505597 | Discussion on Testing issues for CSI compression two-sided models | MediaTek inc. |
R4-2505944 | Study on CSI Compression: Testability and Interoperability issues | Apple |
R4-2505984 | Discussion on testing issues for CSI compression two-sided models | CATT |
R4-2506244 | Alignment between RAN1 direction C and RAN4 options | CAICT |
R4-2506472 | Discussion on testing issues for CSI compression two-sided models | vivo |
R4-2506528 | Testing issues for CSI compression two-sided models | OPPO |
R4-2506609 | Discussion on testing issues for CSI compression two-sided models | CMCC |
R4-2506961 | Discussion on Testing issues for CSI compression two-sided models | ZTE Corporation, Sanechips |
R4-2507023 | Evaluation Criterion for AI/ML Interoperability from Standardization of Testing and Verification Perspective | NTU |
R4-2507054 | Discussion on testing issues for CSI compression two-sided models | Huawei, HiSilicon |
R4-2507057 | Discussion on the 2-sided CSI study | Ericsson |
R4-2507136 | Discussion on Testing Issues for CSI Compression Two-sided Models | Nokia |
R4-2507480 | Study on testing issues for CSI compression two-sided models | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505564 | Topic summary for [115][215] FS_NR_AIML_Mob_Part1 | Moderator (Nokia) |
R4-2505565 | Topic summary for [115][216] FS_NR_AIML_Mob_Part2 | Moderator (OPPO) |
TDoc | Title | Source |
---|---|---|
R4-2505694 | Discussion on general aspects for AI mobility | OPPO |
R4-2505695 | TP on RAN4 aspects for TR 38.744 | OPPO, Nokia |
R4-2505949 | General aspects on AI/ML for mobility in NR | Apple |
R4-2506547 | Discussion on general aspects for AI mobility | vivo |
R4-2506564 | Discussion on General Aspects of AIML Mobility | ZTE Corporation, Sanechips |
R4-2506610 | Discussion on general part for AI/ML for mobility | CMCC |
R4-2506735 | Discussion on genereal aspects in AIML mobility | Huawei, HiSilicon |
R4-2507534 | On General aspects in AIML Mobility | Nokia |
R4-2507665 | TP for TR38.744 | Ericsson |
R4-2507666 | General discussion on AI/ML for mobility | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505696 | Study of impacts on RAN4 requirements for RRM measurement prediction | OPPO |
R4-2505766 | Discussion on impacts on RAN4 requirement for RRM measurement prediction in AI mobility | Xiaomi |
R4-2505950 | Study of RAN4 impacts for RRM measurement prediction for AIML Mobility in NR | Apple |
R4-2505985 | Discussion on impacts of AIML RRM measurement prediction on RRM requirements | CATT |
R4-2506171 | Study of RAN4 impacts for RRM measurement prediction for AIML mobility in NR | Tejas Network Limited |
R4-2506306 | Discussion of RAN4 impacts for RRM measurement prediction | LG Electronics Inc. |
R4-2506507 | Discussion on RAN4 impacts for RRM measurement prediction | MediaTek Inc. |
R4-2506548 | Discussion on RAN4 impacts for RRM measurement prediction | vivo |
R4-2506563 | Discussion impacts on requirements of AI/ML mobility | ZTE Corporation, Sanechips |
R4-2506611 | Discussion on RAN4 impacts for RRM measurement prediction | CMCC |
R4-2506736 | Discussion on impacts for RRM measurement prediction | Huawei, HiSilicon |
R4-2507123 | Discussions on requirements for RRM measurement prediction on AIML mobility | NTT DOCOMO, INC. |
R4-2507432 | On RAN4 Impacts for RRM measurement prediction in AIML Mobility | Nokia |
R4-2507667 | On requirements for RRM measurement prediction for AI/ML based mobility | Ericsson |
R4-2507801 | Impact of AI based mobility on RRM measurement prediction | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505697 | Study of impacts on RAN4 requirements for measurement event prediction | OPPO |
R4-2505767 | Discussion on impacts on RAN4 requirement for measurement event prediction in AI mobility | Xiaomi |
R4-2505951 | Study of RAN4 impacts for measurement event prediction for AIML Mobility in NR | Apple |
R4-2505986 | Discussion on impacts of AIML measurement event prediction on RRM requirements | CATT |
R4-2506508 | Discussion on RAN4 impacts for measurement event prediction | MediaTek Inc. |
R4-2506549 | Discussion on RAN4 impacts for measurement event prediction | vivo |
R4-2506565 | Discussion on impacts for measurement event prediction | ZTE Corporation, Sanechips |
R4-2506612 | Discussion on RAN4 impacts for measurement event prediction | CMCC |
R4-2506737 | Discussion on impacts for measurement event prediction | Huawei, HiSilicon |
R4-2507124 | Discussions on requirements for measurement event prediction on AIML mobility | NTT DOCOMO, INC. |
R4-2507433 | On RAN4 Impacts for Measurement Event Prediction in AIML Mobility | Nokia |
R4-2507668 | On requirements for Event prediction for AIML based mobility | Ericsson |
R4-2507802 | Impact of AI based mobility on RRM event prediction | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505698 | Study of testability and interoperability for AI mobility | OPPO |
R4-2505790 | Discussion on study of testability and interoperability for AIML mobility | Xiaomi |
R4-2505948 | On Testability and Interoperability Issues for AIML Mobility in NR | Apple |
R4-2505987 | Discussion on testability and interoperability issues for AIML mobility | CATT |
R4-2506509 | Discussion on testability and interoperability of AI mobility | MediaTek Inc. |
R4-2506550 | Discussion on testability and interoperability for AI mobility | vivo |
R4-2506562 | Discussion on the interoperability and testability aspects | ZTE Corporation, Sanechips |
R4-2506613 | Discussion on testability and interoperability for AI/ML for mobility | CMCC |
R4-2506738 | Discussion on testability and interoperability issues in AIML mobility | Huawei, HiSilicon |
R4-2507255 | General discussion on AI mobility regarding testability and interoperability | Samsung |
R4-2507535 | Testability and Interoperability Issues for AIML Mobility | Nokia |
R4-2507669 | On testing of AI/ML based mobility | Ericsson |
R4-2507803 | Testability and data consistency | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505566 | Topic summary for [115][217] NR_MIMO_Ph5_Part1 | Moderator (Samsung) |
R4-2505567 | Topic summary for [115][218] NR_MIMO_Ph5_Part2 | Moderator (MediaTek) |
R4-2507572 | Topic summary for [115][133] NR_MIMO_Ph5_UE | Moderator (Samsung) |
R4-2507861 | Topic summary for [115][329] NR_MIMO_demod | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R4-2506919 | R19 release independent of 3Layer | OPPO |
R4-2507530 | CR for 38.101-2: Beam correspondence requirements for non-simultaneous transmission in different directions | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2505371 | CR on FR2 RF requirements for NR_MIMO_Ph5 | Qualcomm, Sony, Nokia |
R4-2505588 | draft CR for TS 38.101-1 to introduce FR1 3Tx RF requirements | Huawei, HiSilicon |
R4-2505959 | 3Tx NR specifications | Qualcomm Technologies |
R4-2505961 | CR to TS 38.101-1 to capture 3Tx specifications | Qualcomm Technologies |
R4-2506862 | Further discussion of UE RF impact for NR MIMO phase 5 | vivo |
R4-2506863 | draft CR for NR MIMO for 38.101-1 | vivo |
R4-2507093 | UE RF requirements (MIMO Phase5) | Nokia |
R4-2507531 | Views and progress on UE RF discussion for NR MIMO Phase 5 | Samsung |
R4-2507783 | On the Asymmetric DL sTRP/UL mTRP for NR MIMO Phase 5 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505350 | On core requirements for enhanced UE-initiated/event-driven beam management | Qualcomm Technologies Ireland |
R4-2505388 | RRM requirements on UE-initiated/event-driven beam management | China Telecom |
R4-2505729 | On remaining UEIBM requirements | Nokia |
R4-2505770 | Discussion on UE-initiated/event-driven beam management on Rel-19 MIMO phase 5 | Xiaomi |
R4-2505813 | Discussion on RRM requirements of UE-initiated beam management in Rel-19 MIMO phase 5 | Samsung |
R4-2505815 | Draft CR on event trigger Reporting based on L1-RSRP measurements for serving cell | Samsung |
R4-2505908 | On RRM Requirements for UE Initiated Beam Management | Apple |
R4-2505909 | Draft CR on Event triggered L1 reporting - SSB from different PCI | Apple |
R4-2506297 | Discussion on RRM requirements of UE-initiated/event-driven beam management | LG Electronics Inc. |
R4-2506586 | Discussion on RRM requirements for event-driven beam management for NR MIMO Phase 5 | CMCC |
R4-2506711 | Discussion on RRM impact for Rel-19 MIMO on UE initiated BM | Huawei, HiSilicon |
R4-2507011 | Discussion on UE initiated BM requirements | Ericsson |
R4-2507288 | Discussion on RRM aspects of UE-initiated beam management of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
R4-2507816 | Discussion on R19 MIMO for UE-initiated event-driven beam management | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505351 | On additional core requirements for NR MIMO Phase 5 | Qualcomm Technologies Ireland |
R4-2505771 | Discussion on other RRM requirement on Rel-19 MIMO phase 5 | Xiaomi |
R4-2505814 | Discussion on RRM requirements of other aspects in Rel-19 MIMO phase 5 | Samsung |
R4-2505816 | Draft CR on Scheduling availability of UE for CJTC reporting | Samsung |
R4-2505910 | On RRM Requirements for MIMO Phase 5 | Apple |
R4-2506587 | Discussion on other RRM requirements for NR MIMO Phase 5 | CMCC |
R4-2506619 | DraftCR on timing requirements for asymmetric DL sTRP/UL mTRP deployment | CMCC |
R4-2506799 | Discussion on RRM impact for Rel-19 MIMO on other aspects | Huawei, HiSilicon |
R4-2506800 | Collection of simulation results for CJT calibration in NR_MIMO_Ph5 | Huawei, HiSilicon |
R4-2506978 | Draft CR on MIMO CJTC reporting measurement requirement for R19 | Huawei, HiSilicon |
R4-2507012 | Discussion on CJTC reporting and asymmetric UL TRP requirements | Ericsson |
R4-2507013 | Draft CR on CJT calibration reporting for Delay offset, Frequency offset, and Phase offset | Ericsson |
R4-2507289 | Discussion on other RRM aspects of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
R4-2507297 | Draft CR on MRTD for asymmetric DL sTRP&UL mTRP deployment of R19 MIMO | ZTE Corporation, Sanechips |
R4-2507386 | Other RRM requirements for MIMO ph5 | Nokia |
R4-2507387 | Draft CR MTTD requirements for UL only TRP | Nokia |
R4-2507817 | Discussion on R19 MIMO for other RRM requirements | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505352 | On RRM performance requirements for NR MIMO Phase 5 | Qualcomm Technologies Ireland |
R4-2505730 | On performance requirements for MIMO Ph5 | Nokia |
R4-2505772 | Discussion on RRM performance requirement for Rel-19 MIMO phase 5 | Xiaomi |
R4-2505773 | Draft CR on TCI state activation for UEIBM | Xiaomi |
R4-2505817 | Discussion on RRM performance requirements of Rel-19 MIMO Phase5 | Samsung |
R4-2505911 | On RRM Performance Requirements for MIMO Phase 5 | Apple |
R4-2506588 | Discussion on RRM performance requirements for NR MIMO Phase 5 | CMCC |
R4-2506801 | Discussion on RRM impact for Rel-19 MIMO on performance part | Huawei, HiSilicon |
R4-2507014 | On RRM performance aspects and test cases for MIMO Ph 5 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505358 | On demodulation performance requirements for Rel-19 MIMO Phase 5 | Qualcomm Technologies Ireland |
R4-2505598 | Discussion on NR MIMO Phase 5 demodulation and CSI requirements | MediaTek inc. |
R4-2505912 | On UE Demodulation and CSI Reporting Requirements for MIMO Phase 5 | Apple |
R4-2505977 | View on BS demodulation requirement for MIMO with 3Tx | Samsung |
R4-2506442 | Discussion on UE demodulation performance and CSI reporting requirements for MIMO_Ph5 | Nokia |
R4-2506632 | Discussion on Rel-19 NR MIMO Phase 5 performance requirements | Ericsson |
R4-2506681 | RAN4 demodulation and CSI reporting performance work scope for NR MIMO Phase 5 | Samsung |
R4-2506682 | Discussion on Rel-19 NR MIMO Phase 5 UE demodulation performance and CSI requirements | Samsung |
R4-2507042 | Discussion on demodulation and CSI performance requirements for R19 MIMO evolution | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505568 | Topic summary for [115][219] NR_duplex_evo | Moderator (Huawei) |
R4-2507838 | Topic summary for [115][306] NR_duplex_evo_General | Moderator (Samsung) |
R4-2507839 | Topic summary for [115][307] NR_duplex_evo_BSRF | Moderator (Huawei) |
R4-2507862 | Topic summary for [115][330] NR_duplex_evo_demod | Moderator (Samsung) |
TDoc | Title | Source |
---|---|---|
R4-2505459 | Mitigating UE-to-UE Cross Link Interference (CLI) | Charter Communications, Inc |
R4-2505589 | On general aspects for SBFD | Huawei, HiSilicon |
R4-2506006 | Discussion on SBFD general issues | CATT |
R4-2506047 | Discussion on updating duty cycle evaluation with the introduction of SBFD | CATT |
R4-2506048 | draftCR to TS 38.101-1 on updating duty cycle evaluation with the introduction of SBFD | CATT |
R4-2506372 | Discussion on SBFD general part | CMCC |
R4-2506530 | Views on general aspects for SBFD | Qualcomm Germany |
R4-2506875 | Discussion on general aspects for gNB SBFD | vivo |
R4-2507397 | Discussion on SBFD symbol on UL duty cycle evaluation and MPR impact on SBFD UL resource muting | Ericsson |
R4-2507481 | Remaining issues for SBFD general aspects | Samsung |
R4-2507482 | draftCR to TS38.104 on general clauses for SBFD-capable BS | Samsung |
R4-2507487 | Workplan for Evolution of NR Duplex Operation (RAN4 Performance Part) | Samsung, Huawei |
R4-2507518 | Discussion on system parameters for SBFD BS | ZTE Corporation, Sanechips |
R4-2507636 | On SBFD system parameters | Nokia |
R4-2507650 | Cross Link Interference (CLI) handling impact on MPR for SBFD operation | Qualcomm Incorporated |
R4-2507682 | Deployment scenarios for FR1 SBFD macro BS | Huawei, HiSilicon, Samsung, Qualcomm, Verizon, Vodafone, China Telecom, China Unicom, Deutsche Telekom |
R4-2507714 | Draft BigCR to TS38.104 for SBFD BS RF requirement | Samsung |
R4-2507724 | SBFD general aspects | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505591 | Overview on conformance testing for SBFD | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505590 | On potentially new requirements for SBFD | Huawei, HiSilicon |
R4-2506009 | Discussion on potentially new requirements for SBFD operation | CATT |
R4-2506930 | Views on new requirements for SBFD | Qualcomm Germany |
R4-2507483 | On the new requirements for SBFD operation for FR1 and FR2-1 | Samsung |
R4-2507484 | draftCR to TS38.104 on transient period requirements for SBFD-capable BS | Samsung |
R4-2507519 | Discussion on potentially new requirements for SBFD operation | ZTE Corporation, Sanechips |
R4-2507637 | On potentially new BS RF requirements for SBFD operation | Nokia |
R4-2507725 | New SBFD BS RF requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505468 | Discussion on existing Tx requirements for SBFD operation | Tejas Network Limited |
R4-2506007 | Discussion on modification of existing Tx requirements for SBFD operation | CATT |
R4-2506373 | Discussion on existing Tx requirements for SBFD | CMCC |
R4-2506375 | Draft CR for TS 38.104 to add unwanted emissions for SBFD | CMCC |
R4-2507485 | On the modification of existing TX requirements for SBFD-capable BS | Samsung |
R4-2507520 | Discussion on modification of existing Tx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
R4-2507638 | On existing BS RF TX requirements for SBFD operation | Nokia |
R4-2507639 | DraftCR to TS38.104 on requirements for SBFD-capable BS | Nokia |
R4-2507640 | DraftCR to TS38.104 on requirements for SBFD-capable BS | Nokia |
R4-2507683 | On modification of existing TX RF requirements for SBFD | Huawei, HiSilicon |
R4-2507726 | Impact on SBFD BS RF TX requirements | Ericsson |
R4-2507728 | Draft CR to 38.104 on adding RF requirements for SBFD | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505469 | Views on modification of existing Rx requirements for SBFD | Tejas Network Limited |
R4-2506008 | Discussion on modification of existing Rx requirements for SBFD operation | CATT |
R4-2506010 | DraftCR for TS 38.104 to introduce conducted out-of-band blocking for SBFD | CATT |
R4-2506011 | DraftCR for TS 38.104 to introduce OTA out-of-band blocking for SBFD | CATT |
R4-2506374 | Discussion on existing Rx requirements for SBFD | CMCC |
R4-2506532 | Draft CR to 38.104 for introduction of receiver spurious and intermodulation requirements | Qualcomm Germany |
R4-2507486 | On the modification of existing RX requirements for SBFD-capable BS | Samsung |
R4-2507521 | Discussion on modification of existing Rx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
R4-2507641 | On existing BS RF RX requirements for SBFD operation | Nokia |
R4-2507684 | On modification of existing RX RF requirements for SBFD | Huawei, HiSilicon |
R4-2507727 | Impact on SBFD BS RF RX requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505671 | Draft CR on general for SBFD | vivo |
TDoc | Title | Source |
---|---|---|
R4-2505659 | On remaining RRM requirements for UE-to-UE CLI handling | vivo |
R4-2505699 | On RRM requirements for UE-to-UE CLI handling | OPPO |
R4-2505818 | Views on L1 CLI measurement requirements | Samsung |
R4-2505820 | Draft CR on general L1-CLI-RSSI measurements | Samsung |
R4-2505887 | On UE RRM requirements for UE-to-UE CLI handling | Apple |
R4-2505988 | Discussion on UE to UE CLI handling | CATT |
R4-2506208 | RRM requirements for UE-to-UE CLI handling | Nokia, Nokia Shanghai Bell |
R4-2506209 | draftCR on L1 CLI measurement | Nokia, Nokia Shanghai Bell |
R4-2506213 | Simulation result for L1-CLI-SRS-RSRP measurement | Nokia, Nokia Shanghai Bell |
R4-2506300 | Discussion on RRM impacts of UE-to-UE CLI handling | LG Electronics Inc. |
R4-2506302 | Draft CR for L1-SRS-RSRP measurement period | LG Electronics Inc. |
R4-2506336 | Discussion on RRM requirements for UE-to-UE CLI handling for evolution of NR duplex operation | China Telecom |
R4-2506595 | Discussion on RRM requirements for UE-to-UE CLI handling | CMCC |
R4-2506616 | DraftCR on measurement period for L1-SRS-RSRP measurement | CMCC |
R4-2506666 | Dicussion on RRM requirements for UE-to-UE CLI handling | Ericsson |
R4-2506668 | draft CR on scheduling restriction due to L1-CLI-RSSI measurement for SBFD | Ericsson |
R4-2506785 | Discussion on UE CLI measurement for SBFD | Huawei, HiSilicon |
R4-2507290 | Discussion on UE-to-UE CLI of R19 SBFD | ZTE Corporation, Sanechips |
R4-2507300 | Draft CR on scheduling applicability of R19 SBFD | ZTE Corporation, Sanechips |
R4-2507579 | Discussion on SBFD UE-to-UE CLI | MediaTek inc. |
R4-2507879 | RRM requirements for UE-to-UE CLI handling | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505660 | On remaining RRM impacts for SBFD operation | vivo |
R4-2505700 | On RRM impacts for SBFD operation | OPPO |
R4-2505701 | draftCR on requirements of CSI-RS based L1-RSRP Reporting with SBFD | OPPO |
R4-2505819 | Views on RRM requirements for Rel-19 SBFD operation | Samsung |
R4-2505888 | CR on Measurement gap and Active BWP switch delay for SBFD | Apple |
R4-2505989 | Discussion on impacts of SBFD on RRM requirements | CATT |
R4-2506210 | RRM requirements for SBFD operation | Nokia, Nokia Shanghai Bell |
R4-2506301 | Discussion on RRM impacts of SBFD operation | LG Electronics Inc. |
R4-2506337 | Discussion on RRM impacts for SBFD operation for evolution of NR duplex operation | China Telecom |
R4-2506338 | Draft CR on CSI-RS based CBD evaluation period requirements with SBFD | China Telecom |
R4-2506594 | Discussion on RRM impacts for SBFD operation | CMCC |
R4-2506667 | Discussion on RRM impacts for SBFD operation | Ericsson |
R4-2506786 | Discussion on RRM impacts for SBFD operation | Huawei, HiSilicon |
R4-2506787 | draftCR on L1-SINR measurement requirements with SBFD | Huawei, HiSilicon |
R4-2507291 | Discussion on other RRM impacts of R19 SBFD | ZTE Corporation, Sanechips |
R4-2507580 | Draft CR on clarification of L3 CSI-RS measurement requirement for SBFD | MediaTek inc. |
R4-2507581 | Discussion on SBFD Operation | MediaTek inc. |
R4-2507878 | draftCR on CSI-RS based RLM evaluation period requirements with SBFD | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505821 | Discussion on RRM performance requirements of Rel-19 SBFD | Samsung |
R4-2505990 | Discussion on SBFD RRM performance requirements | CATT |
R4-2505991 | DraftCR to update CSI-RS based BFD evaluation period due to impact of SBFD operation | CATT |
R4-2506211 | RRM performance requirements for SBFD operation | Nokia, Nokia Shanghai Bell |
R4-2506212 | draftCR on L1 CLI performance requirements | Nokia, Nokia Shanghai Bell |
R4-2506339 | Discussion on RRM performance requirements for evolution of NR duplex operation | China Telecom |
R4-2506596 | Discussion on RRM performance requirements for SBFD | CMCC |
R4-2506669 | Discussion on RRM performance requirements for SBFD | Ericsson |
R4-2506788 | Discussion on performance requirements for SBFD | Huawei, HiSilicon |
R4-2507295 | Discussion on Perf part of R19 SBFD | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505599 | Discussion on SBFD UE demodulation and CSI requirements | MediaTek inc. |
R4-2505976 | View on demodulation requirement for SBFD | Samsung |
R4-2506531 | Views on UE and BS demodulation requirements for SBFD | Qualcomm Germany |
R4-2506954 | Discussion on UE and BS demodulation performance requirements for SBFD | ZTE Corporation, Sanechips |
R4-2507027 | Discussion on SBFD demodulation performance requirements | Huawei, HiSilicon |
R4-2507141 | Discussion on general issue on SBFD demodulation | Ericsson |
R4-2507626 | On the Evolution of NR Duplex Operation - Sub-Band Full Duplex | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505569 | Topic summary for [115][220] Ambient_IoT_Solutions | Moderator (CMCC) |
R4-2507573 | Topic summary for [115][134] A-IoT_device | Moderator (CMCC) |
R4-2507574 | Topic summary for [115][135] A-IoT_BSCW | Moderator (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2505541 | A-IoT general aspects | Huawei, HiSilicon |
R4-2505619 | Discussion on A-IoT System parameters | CMCC |
R4-2505753 | Discussion on AIoT system parameters | Xiaomi |
R4-2506014 | Discussion on system parameters for A-IoT | CATT |
R4-2506229 | Discussion on system parameters for ambient IoT | Spreadtrum,UNISOC |
R4-2506840 | Discussion on the systeme parameter of AIoT | vivo |
R4-2507182 | on system parameter | OPPO |
R4-2507496 | A-IoT general overview | Ericsson |
R4-2507505 | Discussions on General aspect for A-IoT | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505542 | RF requirements for A-IoT BS | Huawei, HiSilicon |
R4-2505616 | Discussion on A-IoT BS RF requirements | CMCC |
R4-2505754 | Further D2R LLS simulation result | Xiaomi |
R4-2506012 | Discussion on A-IoT BS requirements | CATT |
R4-2506015 | DraftCR for TS 38.194 to introduce base station output power and transmit ON/OFF power | CATT |
R4-2506016 | DraftCR for TS 38.194 to introduce transmitter intermodulation | CATT |
R4-2506841 | Discussion on the RF requirement for AIoT BS | vivo |
R4-2507007 | Discussions on A-IoT BS RF requirements | NTT DOCOMO, INC. |
R4-2507495 | TP to TS38.914 : Inband blocking, OOB and Spurious | Ericsson |
R4-2507506 | Further discussions on RF requirements for A-IoT BS | ZTE Corporation, Sanechips |
R4-2507642 | Draft CR to TS38.194 on ambient IoT BS | LG Electronics UK |
TDoc | Title | Source |
---|---|---|
R4-2505618 | Discussion on A-IoT device RF requirements | CMCC |
R4-2505755 | Discussion on AIoT device 1 RF requirements | Xiaomi |
R4-2506033 | Discussion on Ambient IoT device 1 RF requirements | CATT |
R4-2506162 | REFSENS procedure, SFO and timing aspects | Qualcomm Incorporated |
R4-2506230 | Discussion on RF requirements for ambient IoT device 1 | Spreadtrum,UNISOC |
R4-2506842 | Discussion on the RF requirement for device 1 | vivo |
R4-2507128 | RF requirements of ambient IoT device 1 | Sony |
R4-2507181 | on RF requirements for device 1 | OPPO |
R4-2507497 | A-IoT device requirement overview | Ericsson |
R4-2507507 | Discussion on RF requirement of Ambient IoT device | ZTE Corporation, Sanechips |
R4-2507632 | Discussion on RF requirement for A-IoT device 1 | LG Electronics UK |
R4-2507722 | On the RF requirements for Ambient IoT Device | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505617 | Discussion on A-IoT CW RF requirements | CMCC |
R4-2505756 | Discussion on AIoT CW requirements | Xiaomi |
R4-2506013 | Discussion on RF requirements for CW for D1T1 | CATT |
R4-2506163 | Phase noise specification for CW | Qualcomm Incorporated |
R4-2506231 | Discussion on RF requirements for CW | Spreadtrum,UNISOC |
R4-2506843 | Discussion on the RF requirement for CW | vivo |
R4-2506844 | draft TP to TS 38.194 on CW frequency error and unwanted emssion | vivo |
R4-2507180 | on RF requirements for CW | OPPO |
R4-2507498 | CW node RF impact overview | Ericsson |
R4-2507508 | Discussion on RF requirement for CW node | ZTE Corporation, Sanechips |
R4-2507685 | Further discussion on RF requirements for CW | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505661 | Discussion on RRM impacts for R19 A-IoT device | vivo |
R4-2505782 | Discussion RRM requirements for Ambient IoT | Xiaomi |
R4-2506001 | Discussion on the impacts of A-IoT on RRM requirements | CATT |
R4-2506348 | Discussion on RRM requirements for Ambient-IoT | Ericsson |
R4-2506614 | Discussion on RRM requirements for A-IoT | CMCC |
R4-2507120 | Discussion on RRM impact on A-IoT | Huawei, HiSilicon |
R4-2507122 | Discussions on RRM requirements for A-IoT | NTT DOCOMO, INC. |
R4-2507186 | Discussion on RRM requirements for Ambient-IoT | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505395 | on Ambient IoT device OTA tests | Huawei, HiSilicon |
R4-2505477 | Discussion on OTA testing for A-IoT device 1 | Ericsson Korea Partners Co Ltd |
R4-2505620 | Discussion on OTA test method for A-IoT device | CMCC |
R4-2505742 | Discussion on Ambient IoT Testability | Qualcomm Incorporated |
R4-2506845 | draft CR to 38.870 on test method of AIoT device | vivo |
R4-2506846 | Discussion on the OTA test method for device | vivo |
R4-2507129 | Consideration on the OTA test of ambient IoT device 1 | Sony |
R4-2507179 | on OTA test aspect | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2505570 | Topic summary for [115][221] Netw_Energy_NR_enh_Part1 | Moderator (Ericsson) |
R4-2505571 | Topic summary for [115][222] Netw_Energy_NR_enh_Part2 | Moderator (Huawei) |
R4-2507863 | Topic summary for [115][331] NR_Network_energy_demod | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2506907 | Discussion on UE feature list for Rel-19 NES | Ericsson |
R4-2506909 | Work plan for R19 NES enhancement performance part | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505353 | On core requirements for on-demand SSB SCell operation | Qualcomm Technologies Ireland |
R4-2505662 | On remaining issues for on-demand SSB SCell operation in R19 NES | vivo |
R4-2505672 | Draft CR for Scheduling for L1-SINR measurements for Reporting for NES | vivo |
R4-2505702 | On RRM requirements of on-demand SSB SCell operation | OPPO |
R4-2505777 | Discussion on OD-SSB requirements | Xiaomi |
R4-2505779 | draftCR on Rel19 NES (8.2.2.2.2\tInterruptions at SCell activation/deactivation) | Xiaomi |
R4-2505780 | draftCR on Rel19 NES (8.2.2.2.3\tinterruption during measurements on deactivated SCC) | Xiaomi |
R4-2505870 | Discussion on on-demand SSB SCell operation | Apple |
R4-2505871 | DraftCR of interruptions for OD-SSB transmission | Apple |
R4-2506098 | Discussion on RRM requirements for on-demand SSB SCell operation | CATT |
R4-2506099 | Draft CR to TS 38.133 on carrier-specific scaling factor for OD-SSB | CATT |
R4-2506205 | RRM requirements for OD-SSB SCell operation | Nokia, Nokia Shanghai Bell |
R4-2506206 | draftCR on OD-SSB based SCell activation delay with L3 reporting | Nokia, Nokia Shanghai Bell |
R4-2506294 | Discussion on RRM requirements of on-demand SSB Scell operation for Rel-19 NES | LG Electronics Inc. |
R4-2506298 | Draft CR for NES for SCell Deactivation Delay Requirement for Activated SCell | LG Electronics Inc. |
R4-2506340 | Discussion on On-demand SSB SCell operation for enhancements of NES for NR | China Telecom |
R4-2506341 | Draft CR on OD-SSB based L1-RSRP measurements for Reporting | China Telecom |
R4-2506421 | draftCR on Introduce OD-SSB based direct SCell Activation requirement at SCell addition | CMCC |
R4-2506422 | Discussion on RRM requirement of OD-SSB for NES enhancement | CMCC |
R4-2506482 | Discussion on RRM requirements for OD-SSB for network energy saving | MediaTek inc. |
R4-2506483 | DraftCR on introduction and measurement restriction for L1-SINR measurement | MediaTek inc. |
R4-2506705 | Discussion on RRM impact for Rel-19 NES OD-SSB | Huawei, HiSilicon |
R4-2506706 | DraftCR on OD-SSB based SCell Activation Delay Requirement for Deactivated PUCCH SCell | Huawei, HiSilicon |
R4-2506824 | Discussion on RRM requirements for On-demand SSB SCell operations | Intel Corporation |
R4-2506825 | DraftCR for scheduling availability during UE intra-frequency measurements based on OD-SSB | Intel Corporation |
R4-2506904 | Discussion on OD-SSB in Rel-19 NES | Ericsson |
R4-2506910 | draftCR on OD-SSB based NR intra-frequency measurements | Ericsson |
R4-2507252 | Discussion on RRM requirements for NES OD-SSB | Samsung |
R4-2507254 | Draft CR on OD-SSB based SCell Activation Delay Requirement for Deactivated SCell | Samsung |
R4-2507286 | Discussion on On-demand SSB SCell operation of R19 NES | ZTE Corporation, Sanechips |
R4-2507298 | Draft CR on scheduling restriction of L1-RSRP measurement of R19 NES | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505354 | On core requirements for adaptation of common signal/channel transmission | Qualcomm Technologies Ireland |
R4-2505663 | On remaining issues for adaptation on common signal in R19 NES | vivo |
R4-2505703 | On RRM requirements of SSB adaptation | OPPO |
R4-2505778 | Discussion on RRM requirements for adaptation of common signal/channel in NES | Xiaomi |
R4-2505872 | Discussion on adaptation of common signal/channel transmission | Apple |
R4-2505873 | DraftCR of NR intra-frequency measurement due to SSB adaptation | Apple |
R4-2506295 | Discussion on RRM requirements of SSB adaptation for Rel-19 NES | LG Electronics Inc. |
R4-2506342 | Discussion on adaptation of common signal channel transmission for enhancements of NES for NR | China Telecom |
R4-2506423 | Discussion on RRM requirement of signal adaptation for NES enhancement | CMCC |
R4-2506707 | Discussion on RRM impact for Rel-19 NES on adaptation | Huawei, HiSilicon |
R4-2506708 | DraftCR on SSB adaptation for L1-RSRP | Huawei, HiSilicon |
R4-2506905 | Discussion on SSB adaptation in Rel-19 NES | Ericsson |
R4-2506911 | draftCR on SSB adapation for SCell actiation | Ericsson |
R4-2507251 | Discussion on NES common signal adaptation | Samsung |
R4-2507287 | Discussion on adaptation of common signal and channel of R19 NES | ZTE Corporation, Sanechips |
R4-2507299 | Draft CR on SSB adaptation impact on the CBD of R19 NES | ZTE Corporation, Sanechips |
R4-2507352 | RRM requirements for SSB adaptation | Nokia, Nokia Shanghai Bell |
R4-2507353 | Draft CR38.133 L1-SINR measurements for SSB periodicity adaptation | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2505355 | On core requirements for on-demand SIB1 | Qualcomm Technologies Ireland |
R4-2505664 | On remaining issues for on-demand SIB1 in R19 NES | vivo |
R4-2505704 | On RRM requirement for on-demand SIB1 | OPPO |
R4-2505705 | draftCR on requirements for interruption in paging reception | OPPO |
R4-2505874 | Discussion on on-demand SIB1 | Apple |
R4-2506100 | Discussion on RRM requirements for On-demand SIB1 | CATT |
R4-2506296 | Discussion on RRM requirements of on-demand SIB1 for Rel-19 NES | LG Electronics Inc. |
R4-2506343 | Discussion on On-demand SIB1 for enhancements of NES for NR | China Telecom |
R4-2506424 | draftCR on Introduce timing requirements for UL-WUS for OD-SIB1 | CMCC |
R4-2506425 | Discussion on RRM requirement of OD-SIB1 for NES enhancement | CMCC |
R4-2506484 | Discussion on RRM requirements for OD-SIB1 | MediaTek inc. |
R4-2506709 | Discussion on RRM impact for OD-SIB1 | Huawei, HiSilicon |
R4-2506906 | Discussion on OD-SIB1 in Rel-19 NES | Ericsson |
R4-2507354 | RRM requirements for On-demand-SIB1 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2505356 | On RRM performance requirements for Rel-19 NES | Qualcomm Technologies Ireland |
R4-2505706 | on RRM performance requirements of R19 NES | OPPO |
R4-2506101 | Discussion on RRM performance requirements for Rel-19 NES for NR | CATT |
R4-2506207 | RRM performance requirements for network energy saving | Nokia, Nokia Shanghai Bell |
R4-2506299 | Discussion on RRM performance requirements for Rel-19 NES | LG Electronics Inc. |
R4-2506344 | Discussion on RRM performance requirements of NES for NR | China Telecom |
R4-2506426 | Discussion on test cases for R19 NES | CMCC |
R4-2506710 | Discussion on performance requiremnets for Rel-19 NES | Huawei, HiSilicon |
R4-2506908 | Discussion on RRM performance requirements for Rel-19 NES | Ericsson |
R4-2507253 | Discussion on performance requirements for NES | Samsung |
R4-2507294 | Discussion on Perf part of R19 NES | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505357 | UE and BS demodulation performance requirements | Qualcomm Technologies Ireland |
R4-2505975 | View on BS demodulation requirement for NR NES | Samsung |
R4-2506683 | Discussion on UE demodulation and CSI performance requirements for Rel-19 NES | Samsung |
R4-2507043 | Discussion on demodulation performance requirements for R19 NES | Huawei, HiSilicon |
R4-2507108 | Demodulation requirements for NR network energy saving enhancements | Ericsson |
R4-2507625 | On Enhancements of Network Energy Savings for NR | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2505572 | Topic summary for [115][223] NR_LPWUS | Moderator (vivo) |
R4-2507575 | Topic summary for [115][136] NR_LPWUS_UERF | Moderator( Vivo) |
R4-2507840 | Topic summary for [115][308] NR_LPWUS | Moderator (Huawei) |
R4-2507864 | Topic summary for [115][332] NR_LPWUS_demod | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2506113 | TP to TR 38.774 on transmitted signal quality (clause 7.2.4) for LP-WUS | CATT |
R4-2506118 | TP for TR 38.774 on LP-WUS | Nokia |
R4-2506881 | TR 38.774 v0.4.0 | vivo |
R4-2506882 | Draft Big CR for LP-WUS UE RF requirements in Rel-19 | vivo |
R4-2506971 | TP to TR 38.774 on testability of LP-WUR | Samsung |
R4-2507490 | On general issues for WUR | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505878 | Discussion of RRM impact of XR for NR Phase 3 | Apple |
R4-2505879 | Inter-RAT measurements E-UTRAN TDD measurements | Apple |
R4-2506883 | TP to TR 38.774 on LP-WUS UE RF Simulations | vivo |
R4-2507130 | views on requirements of the low-power wake-up receiver | Sony |
TDoc | Title | Source |
---|---|---|
R4-2506049 | draftCR to TS 38.101-1 on operating bands for LP-WUS/WUR (sub-clause 5.2M) | CATT |
R4-2506050 | draftCR to TS 38.101-1 on UE channel bandwidth for LP-WUS/WUR (sub-clause 5.3M) | CATT |
R4-2506114 | System parameters for LP-WUR | Nokia |
R4-2507491 | On system parameter for WUR | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505368 | On UE RF requirements for the LPWUR | Qualcomm Incorporated |
R4-2505370 | dCR to 38.101-1, LPWUS ACS | Qualcomm, Nokia, Ericsson |
R4-2505433 | On LP-WUR Rx requirements | Apple |
R4-2505518 | Further consideration on UE REFSENS, ACS requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2506053 | Further discussion on REFSENS for LP-WUS | CATT |
R4-2506115 | Fundamental RX requirements for LP-WUR | Nokia |
R4-2506119 | Draft CR to add new LP-WUS requirements | Nokia |
R4-2506311 | Discussion for LP-WUS/WUR REFSENS | LG Electronics France |
R4-2506315 | Discussion on REFSENS, ASCS, ACS for LP-WUR | ZTE Corporation, Sanechips |
R4-2506369 | Discussion on LP-WUS UE RF Rx requirements of REFSENS, ASCS and ACS | CMCC |
R4-2506884 | Discussions on LP-WUS REFSENS, ASCS, ACS and RMC | vivo |
R4-2506969 | Discussion on UE RF requirements for LP-WUR | Samsung |
R4-2507494 | WUR RF requirement REFSESN ACS ASCS | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505519 | Further consideration on UE RF other Rx requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2505522 | draft CR to TS 38.101-1 on Blocking characteristics for LP-WUR | Huawei, HiSilicon |
R4-2505523 | TP for 38.774: Blocking characteristics for LP-WUR | Huawei, HiSilicon |
R4-2506054 | Further discussion on other RF requirements for LP-WUS | CATT |
R4-2506116 | Other RX requirements for LP-WUR | Nokia |
R4-2506316 | Discussion on receiver characteristics for LP-WUR | ZTE Corporation, Sanechips |
R4-2506317 | Draft CR to Rel-19 TS38.101-1 on receiver characteristics for LP-WUR | ZTE Corporation, Sanechips |
R4-2506368 | Draft CR for 38.101-1 to Introduce R19 LPWUS UE intermodulation requirements | CMCC |
R4-2506370 | Discussion on LP-WUS UE RF Rx requirements of IBB, OBB, intermodulation, spurious emissions and others | CMCC |
R4-2506885 | draft CR to 38.101-1 on LP-WUS UE RF | vivo |
R4-2507062 | Draft CR for TS 38.101-1 to Introduce R19 LPWUS UE intermodulation requirements | CMCC |
R4-2507493 | WUR RF requirement other than REFSENS | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505369 | Some test skipping proposals for LPWUS | Qualcomm Incorporated |
R4-2505520 | Further consideration on UE RF testability issues for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2506055 | Further discussion on Testability for UE RF requirements for LP-WUS | CATT |
R4-2506117 | Testability aspects of LP-WUR | Nokia |
R4-2506886 | Discussions on LP-WUS Testability | vivo |
R4-2506970 | Discussion on testability for LP-WUR | Samsung |
R4-2507492 | On WUR RF requirement testability | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505521 | Further consideration on BS RF for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2505524 | draft CR to TS 38.104 on introduction of general part and power boosting definition for LP-WUS | Huawei, HiSilicon |
R4-2506051 | draftCR to TS 38.141-1 on declaration of support for LP-WUS | CATT |
R4-2506052 | draftCR to TS 38.141-2 on declaration of support for LP-WUS | CATT |
R4-2506056 | Further discussion on BS RF requirements for LP-WUS | CATT |
R4-2506313 | Discussion on BS RF requirements for LP-WUS/WUR | ZTE Corporation, Sanechips |
R4-2506314 | TP to TR 38.774 on LP-WUS BS RF general part (Clause 7.2.1) | ZTE Corporation, Sanechips |
R4-2506371 | Discussion on LP-WUS BS RF requirements | CMCC |
R4-2507085 | BS RF requirements for low-power wake-up signal for NR | Nokia |
R4-2507086 | TP to TR 38.774: Other BS RF requirements for Low-Power Wake-up Signal and Receiver | Nokia |
R4-2507087 | Draft CR to TS 38.104 on introduction of LP-WUS into unwanted emissions and transmitter intermodulaton clauses | Nokia |
R4-2507489 | TP to TR38.774: BS RF requirement overview for LP-WUS | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505668 | Reply LS on LS on the wake-up delay for LP-WUS operation in IDLEINACTIVE mode | vivo |
R4-2505673 | Draft CR for inactive state LP-WUR serving cell measurement and evaluation requirements | vivo |
TDoc | Title | Source |
---|---|---|
R4-2505665 | Remaining issues for simulation for LP-WUR | vivo |
R4-2505666 | Further simulation results for LP-WUR | vivo |
R4-2505791 | Discussion on simulation assumptions and results for LP-WUS/WUR | Xiaomi |
R4-2505856 | Discussion of Simulation Assumptions for LP-WUR RRM Requirements | Apple |
R4-2505857 | Summary of Simulation Results for LP-WUR RRM Requirements | Apple |
R4-2506134 | Discussion on LP-WUR Simulation assumptions and results | Nokia |
R4-2506135 | LP-SS Simulation results | Nokia |
R4-2506303 | Discussion on simulation assumptions and results for LP-WUS/WUR | LG Electronics Inc. |
R4-2506427 | Simulation assumption and results for LP-WUR | CMCC |
R4-2506789 | Simulation assumption and additional simulation results for LP-WUR measurement | Huawei, HiSilicon |
R4-2506901 | Simulation on LP-WUS RRM measurement | Ericsson |
R4-2507194 | Discussion on OOK-based LP-WUR simulation | ZTECorporation,Sanechips |
R4-2507812 | Simulation assumptions for R19 LP-WUS | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505667 | On remaining RRM issues for LP-WUR | vivo |
R4-2505707 | Discussion on RRM core requirements for LP-WUSWUR | OPPO |
R4-2505708 | DraftCR on measurements of intra-frequency NR cells for UE with LP-WUR in IDLE and INACTIVE state | OPPO |
R4-2505792 | Discussion on RRM core requirements for LP-WUS/WUR | Xiaomi |
R4-2505793 | draftCR on 5.X.2.3 MR serving cell measurement and evaluation requirements | Xiaomi |
R4-2505929 | On RRM core requirements for LP-WUR | Apple |
R4-2505930 | Reply LS on the RRM measurement metrics for OFDM-based LP-WUR | Apple |
R4-2505931 | Reply LS on the wake-up delay for LP-WUS operation in IDLE/INACTIVE mode | Apple |
R4-2506102 | Draft CR to TS 38.133 on definitions, symbols and abbreviations | CATT |
R4-2506103 | Draft CR to TS 38.133 on measurements of inter-RAT E-UTRAN cells for UE with LP-WUR | CATT |
R4-2506136 | Discussion on LP-WUS-WUR RRM core requirements | Nokia |
R4-2506137 | DraftCR to TS 38.133 on LP-WUR serving cell measurement and evaluation requirements | Nokia, Vivo |
R4-2506304 | Discussion on RRM core requirements for LP-WUS/WUR | LG Electronics Inc. |
R4-2506305 | Draft CR for Measurements of inter-frequency NR cells for UE with LP-WUR | LG Electronics Inc. |
R4-2506345 | Discussion on RRM core requirements for LP-WUS/WUR | China Telecom |
R4-2506428 | Discussion on RRM impact of LP-WUR | CMCC |
R4-2506429 | draftCR Introduce inter-frequency and inter-RAT cell re-selection requirements for UE with LP-WUR in RRC_Inactive | CMCC |
R4-2506790 | Discussion on RRM requirements for LP-WUR | Huawei, HiSilicon |
R4-2506791 | draftCR on MR measurement requirements for serving cell in IDLE | Huawei, HiSilicon, vivo |
R4-2506900 | Discussion on LP-WUS RRM requirement | Ericsson |
R4-2506902 | draftCR on LP-WUS introduction | Ericsson |
R4-2507192 | Discussion on RRM core requirements on LPWUS | ZTECorporation,Sanechips |
R4-2507197 | Draft LS to RAN1 on LP-SSS-RSRP/RSSI measurement | ZTECorporation,Sanechips |
R4-2507198 | Draft LS to RAN1 on wake-up delay for LP-WUS operation in IDLE/INACTIVE | ZTECorporation,Sanechips |
R4-2507203 | (NR_LPWUS-Core) LPWUR and MR measurement capapbility in IDLE state | ZTECorporation,Sanechips |
R4-2507204 | (NR_LPWUS-Core) LPWUR and MR measurement capapbility in INACTIVE state | ZTECorporation,Sanechips |
R4-2507813 | Discussion on the RRM core requirements for LP-WUS | MediaTek inc. |
R4-2507875 | RRM core requirements for LP-WUR | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505669 | Work plan for performance part for LP-WUSWUR | vivo |
R4-2505670 | Initial consideration on performance for LP-WUR | vivo |
R4-2505709 | Discussion on RRM performance requirements for LP-WUSWUR | OPPO |
R4-2506138 | Discussion on RRM performance requirements | Nokia |
R4-2506346 | Discussion on RRM performance requirements for LP-WUS/WUR | China Telecom |
R4-2506430 | Discussion on test cases for LP-WUS | CMCC |
R4-2506792 | Discussion on test case for LP-WUR | Huawei, HiSilicon |
R4-2506903 | Discussion on performance requirements for LP-WUR | Ericsson |
R4-2507193 | Discussion on RRM performance requirements on LPWUS | ZTECorporation,Sanechips |
R4-2507876 | RRM performance requirements for LP-WUR | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505858 | On Demodulation Requirements for LP-WUS | Apple |
R4-2506168 | Discussions on demodulation performance requirements of LP-WUS/WUR for NR | QUALCOMM Europe Inc. - Spain |
R4-2506169 | Discussions on work plan for demodulation performance requirements of LP-WUS/WUR for NR | QUALCOMM Europe Inc. - Spain |
R4-2506443 | Discussion on UE demodulation performance requirements for LPWUS | Nokia |
R4-2506684 | Discussion on UE demodulation requirements for NR LP-WUS and receiver | Samsung |
R4-2506956 | Discussion on UE demodulation performance requirements for LP-WUS | ZTE Corporation, Sanechips |
R4-2507039 | Discussion on demodulation performance requirements for R19 LP-WUS | Huawei, HiSilicon |
R4-2507109 | UE demodulation requirements for LP-WUS/WUR | Ericsson |
R4-2507115 | Discussions on demodulation requirements for R19 LP-WUS/WUR | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505573 | Topic summary for [115][224] NR_Mob_Ph4_Part1 | Moderator (Apple) |
R4-2505574 | Topic summary for [115][225] NR_Mob_Ph4_Part2 | Moderator (China Telecom) |
TDoc | Title | Source |
---|---|---|
R4-2505864 | On UE feature list for CSI-RS based L1 measurement | Apple |
R4-2506460 | On UE capability for mobility enhancement phase 4 WI | vivo |
R4-2507015 | Rel-19 RAN4 UE feature list for NR mobility enhancements Phase 4 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505473 | RRM Core requirements on event triggered L1 measurement reporting | China Telecom |
R4-2505710 | On event triggered L1 measurement reporting | OPPO |
R4-2505711 | draftCR on capabilities for Support of Event Triggering and Reporting Criteria | OPPO |
R4-2505731 | On remaining LTM L1 event-triggered reporting requirements | Nokia |
R4-2505732 | DraftCR for LTM L1 event-triggered reporting | Nokia |
R4-2505768 | Discussion on event triggered L1 measurement reporting for mobility | Xiaomi |
R4-2505875 | Discussion on event triggered L1 measurement reporting | Apple |
R4-2506104 | Discussion on Event triggered L1 measurement reporting for Rel-19 LTM enhancements | CATT |
R4-2506459 | On RRM requirements for LTM event-triggered L1-RSRP reporting | vivo |
R4-2506500 | Discussion on event triggered L1 report for LTM | MediaTek Inc. |
R4-2506569 | Discussion on Event triggered L1 measurement reporting | ZTE Corporation, Sanechips |
R4-2506589 | Discussion on event triggered L1 measurement reporting | CMCC |
R4-2506617 | DraftCR on event-triggered reporting for CSI-RS based L1 measurement | CMCC |
R4-2506730 | Discussion on Event triggered L1 measurement reporting | Huawei, HiSilicon |
R4-2507016 | Discussion on measurements enhancements for purpose of supporting LTM | Ericsson |
R4-2507017 | Draft CR on event-Triggered Reporting for Intra-Frequency L1 Measurements on Neighboring Cells | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505474 | RRM Core requirements on CSI-RS based L1 measurement | China Telecom |
R4-2505712 | On CSI-RS based L1 measurements | OPPO |
R4-2505769 | Discussion on CSI-RS based L1 for mobility | Xiaomi |
R4-2505865 | On open issue for CSI-RS based L1 measurement | Apple |
R4-2505866 | draft CR on CSI-RS based L1 measurement requirement | Apple |
R4-2506105 | Discussion on CSI-RS based L1 measurement for Rel-19 LTM enhancements | CATT |
R4-2506107 | Draft CR to TS 38.133 on number of CSI-RS, number of cells and number of CSI-RS resources | CATT |
R4-2506139 | Discussion on CSI-RS measurements core part | Nokia |
R4-2506140 | DraftCR to 38.133 on LTM CSI-RS applicability | Nokia |
R4-2506458 | On RRM requirements for LTM CSI-RS based L1 measurement | vivo |
R4-2506461 | Draft CR on measurement reporting requirements for CSI-RS based LTM | vivo |
R4-2506501 | Discussion on CSI-RS L1 measurement for LTM | MediaTek Inc. |
R4-2506502 | Draft CR on introduction of CSI-RS L1-RSRP measurement | MediaTek Inc. |
R4-2506568 | Discussion on CSI-RS based L1-RSRP measurement | ZTE Corporation, Sanechips |
R4-2506577 | draftCR on measurement restriction for CSI-RS based L1-RSRP | ZTE Corporation, Sanechips |
R4-2506590 | Discussion on CSI-RS based L1 measurement | CMCC |
R4-2506731 | Discussion on CSI-RS based L1 measurement | Huawei, HiSilicon |
R4-2506732 | Draft CR on scheduling availability of UE during CSI-RS based L1-RSRP measurement | Huawei, HiSilicon |
R4-2507018 | Discussion on CSI-RS based L1 measurement requirements | Ericsson |
R4-2507804 | CSI-RS based L1 measurement for LTM | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505475 | RRM Core requirements on conditional Intra-CU LTM | China Telecom |
R4-2505476 | DraftCR to 38.133 on conditional Intra-CU LTM | China Telecom |
R4-2505794 | Discussion on Conditional Intra-CU LTM for NR mobility enhancements Phase 4 | Xiaomi |
R4-2505876 | Discussion on conditional Intra-CU LTM | Apple |
R4-2506106 | Discussion on conditional Intra-CU LTM for Rel-19 mobility enhancements | CATT |
R4-2506503 | Discussion on Conditional LTM | MediaTek Inc. |
R4-2506555 | Further discussion on Conditional Intra-CU LTM | vivo |
R4-2506567 | Discussion on Conditional Intra-CU LTM | ZTE Corporation, Sanechips |
R4-2506591 | Discussion on conditional intra-CU LTM | CMCC |
R4-2506670 | Discussion on intra-CU conditional LTM | Ericsson |
R4-2506733 | Discussion on conditional Intra-CU LTM | Huawei, HiSilicon |
R4-2507134 | Discussion on Conditional Intra-CU LTM | Nokia |
R4-2507805 | Conditional LTM | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505733 | On performance requirements for NR mobility enhancements Ph4 | Nokia |
R4-2505877 | Discussion on RRM performance of NR mobility enhancements Phase 4 | Apple |
R4-2506108 | Discussion on Rel-19 NR mobility Phase4 RRM performance requirements | CATT |
R4-2506462 | On performance requirements for mobility enh phase 4 | vivo |
R4-2506504 | Discussion on RRM performance requirements for R19 mobility | MediaTek Inc. |
R4-2506570 | Discussion on performance requirements for LTM | ZTE Corporation, Sanechips |
R4-2506592 | Discussion on RRM performance requirements for NR mobility enhancements | CMCC |
R4-2506671 | Discusion on performance requirement for Rel-19 mobility | Ericsson |
R4-2506734 | Discussion on performance requirements of mobility enhancement phase 4 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2505575 | Topic summary for [115][226] NR_XR_Ph3 | Moderator (Nokia) |
TDoc | Title | Source |
---|---|---|
R4-2506457 | On UE capability for XR WI | vivo |
R4-2507388 | Raporteur Inputs | Nokia, Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2505389 | RRM requirements on XR enhancements | China Telecom |
R4-2505394 | NR_XR_Ph3 gap skipping impact | InterDigital Finland Oy |
R4-2505713 | RRM requirements for XR enhancements | OPPO |
R4-2506455 | Draft CR on NR inter-frequency L1 measurement for XR | vivo |
R4-2506456 | Further discussion on RRM requirements for XR | vivo |
R4-2506593 | Discussion on XR (eXtended Reality) for NR Phase 3 | CMCC |
R4-2506712 | Discussion on RRM requirements for Rel-19 XR | Huawei, HiSilicon |
R4-2506713 | DraftCR on Inter-RAT measurements E-UTRAN FDD for Rel-19 XR | Huawei, HiSilicon |
R4-2507121 | Discussions on RRM requirements for XR | NTT DOCOMO, INC. |
R4-2507250 | General discussion on XR RRM requirement | Samsung |
R4-2507292 | Discussion on RRM aspects of R19 XR | ZTE Corporation, Sanechips |
R4-2507304 | Draft CR on measurement gap skipping in intra-frequency measurement with gaps for R19 XR | ZTE Corporation, Sanechips |
R4-2507389 | Draft CR38.133 Introduction of measurement gap cancelation | Nokia |
R4-2507582 | Discussion on RRM requirements for XR | MediaTek inc. |
R4-2507738 | draftCR38133 Inter-frequency measurement requirements with XR | Ericsson |
R4-2507739 | On RRM requirements for XR | Ericsson |
R4-2507747 | Discussion on XR ph3 RRM requirements | Nokia |
R4-2507877 | RRM requirements for XR enhancements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505576 | Topic summary for [115][227] NR_NTN_Ph3_Part1 | Moderator (CATT) |
R4-2505577 | Topic summary for [115][228] NR_NTN_Ph3_Part2 | Moderator (Qualcomm) |
R4-2507841 | Topic summary for [115][309] NR_NTN_Ph3_General_UE_SAN_RF | Moderator (Qualcomm) |
R4-2507865 | Topic summary for [115][333] NR_NTN_Ph3_demod | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2505831 | CR to TS 38.108: Correction of Regenerative Payload Figures | NEC, THALES, [HUAWEI, CATT, Ericsson] |
R4-2506870 | Discussion on simultaneous operation between GNSS and UL transmission in NR NTN | vivo |
R4-2507503 | LS reply on IDC of GNSS | Ericsson |
R4-2507767 | SSB extension impact on UE cell search delay | THALES |
TDoc | Title | Source |
---|---|---|
R4-2505531 | Discussion on the simultaneous operation between GNSS and NR NTN | Huawei, HiSilicon |
R4-2506037 | Discussion on RF requirements for NTN RedCap UE | CATT |
R4-2506038 | Reply LS on GNSS and NR NTN IDC | CATT |
R4-2506120 | RedCap NTN UEs | Nokia |
R4-2506265 | Discussion on UE RF for NR NTN phase 3 | ZTE Corporation, Sanechips |
R4-2507131 | Discussion on the phase continuity and GNSS issue for NR NTN | Sony |
R4-2507345 | Discussion on Rel-19 NR-NTN RedCap UE RF requirements | MediaTek (Hefei) Inc. |
R4-2507500 | RedCap UE RF impact on HD-FDD | Ericsson |
R4-2507720 | On remaining open issues in NR NTN Ph3 | Huawei, HiSilicon |
R4-2507759 | Draft CR to TS 38.101-5: Introduction of RedCap and eRedCap | Qualcomm Incorporated |
R4-2507760 | NR NTN UE RF requirements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506446 | Discussion of requirements for maintaining phase continuity and power consistency for OCC with PUSCH | LG Electronics France |
R4-2506871 | Discussion on requirements for the phase continuity and power consistency for OCC with PUSCH in NR NTN Ph3 | vivo |
R4-2506872 | Draft reply LS on requirements for the phase continuity and power consistency for OCC with PUSCH in NR NTN Ph3 | vivo |
R4-2507501 | Other NTN UE RF impact | Ericsson |
R4-2507761 | NR NTN UL Capacity Enhancements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506039 | CR for TS 38.181, Introduction on SAN diagram for SAN supporting regenerative payload | CATT, NEC, Thales, HUAWEI, Ericsson |
R4-2507434 | CR for TS 38.181, Introduction on SAN diagram for SAN supporting regenerative payload | CATT, NEC, Thales, HUAWEI, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505714 | draftCR on requirements of Link Recovery Procedures for RedCap UEs with NTN | OPPO |
R4-2505715 | On RRM requirements of (e)RedCap UEs with NR FR1-NTN | OPPO |
R4-2505795 | Discussion on (e)RedCap RRM requirements in NTN for NR Phase 3 | Xiaomi |
R4-2505796 | draftCR on 9.5X L1-RSRP measurements for Reporting for RedCap UEs with NTN | Xiaomi |
R4-2505824 | Discussion on RRM requirements of RedCap in Rel-19 NTN phase 3 | Samsung |
R4-2505826 | Draft CR on RRC Connection Mobility Control for RedCap UEs with NTN | Samsung |
R4-2505932 | On R19 NTN (e)RedCap RRM requirements | Apple |
R4-2505933 | draft CR for NR measurements for positioning for RedCap UEs with NTN | Apple |
R4-2506109 | Discussion on (e)RedCap RRM requirements for Rel-19 NTN phase3 | CATT |
R4-2506110 | Draft CR to TS 38.133 on applicability of requirements and Cell Selection for RedCap UEs with NTN | CATT |
R4-2506243 | Discussion on RRM requirements for (e)RedCap in NTN | LG Electronics Inc. |
R4-2506354 | Discussion on RedCap RRM requirements for NTN for NR Phase 3 | Ericsson |
R4-2506357 | (NR_NTN_Ph3-Core) Draft CR on measurement requirement for RedCap UEs with NTN | Ericsson |
R4-2506431 | Discussion on the RRM requirement of (e)Redcap UE for NTN phase3 | CMCC |
R4-2506432 | draftCR on Introduce inter-frequency measurement requirements for RedCap UEs over NTN | CMCC |
R4-2506485 | DraftCR on timing requirements for NTN Redcap | MediaTek inc. |
R4-2506551 | Discussion on RRM requirements on (e)RedCap for R19 NR NTN Phase 3 | vivo |
R4-2506553 | Draft CR for requirements in signalling characteristics for (e)Redcap UEs with FR1-NTN | vivo |
R4-2506793 | Discussion on RRM requirements for RedCap UE in NTN | Huawei, HiSilicon |
R4-2506794 | draftCR on HO requirements for RedCap UE in NTN | Huawei, HiSilicon |
R4-2507188 | Discussion on RRM requirements for RedCap NTN enhancement | ZTECorporation,Sanechips |
R4-2507205 | (NR_NTN_Ph3-Core) Cell Re-selection for RedCap UEs with NTN in IDLE state | ZTECorporation,Sanechips |
R4-2507206 | (NR_NTN_Ph3-Core) Cell Re-selection for RedCap UEs with NTN in INACTIVE state | ZTECorporation,Sanechips |
R4-2507355 | Discussion on requirements for (e)RedCap support in NR NTN | Nokia |
R4-2507356 | Draft CR38.133 CG-SDT requirements for RedCap in NTN | Nokia |
R4-2507357 | Draft CR38.133 RA-SDT requirements for RedCap in NTN | Nokia |
R4-2507807 | draft Cat-B CR on 8.1X Radio Link Monitoring for RedCap UEs with NTN | Qualcomm Incorporated |
R4-2507808 | RedCap for NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505797 | Discussion on other RRM core requirements in NTN for NR Phase 3 | Xiaomi |
R4-2505798 | Reply LS on SMTC enhancements | Xiaomi |
R4-2505825 | Discussion on RRM requirements of other aspects in Rel-19 NTN phase 3 | Samsung |
R4-2505934 | On R19 other NTN RRM requirements | Apple |
R4-2506111 | Discussion on other RRM requirements for Rel-19 NTN phase3 | CATT |
R4-2506245 | Discussion on RRM requirements for downlink coverage enhancement in NTN | LG Electronics Inc. |
R4-2506355 | Discussion on other RRM requirements for NTN for NR Phase 3 | Ericsson |
R4-2506358 | Reply LS to RAN2 on SMTC enhancement | Ericsson |
R4-2506433 | Discussion on the RRM requirement for NTN phase3 DL CE | CMCC |
R4-2506552 | Discussion on RRM impacts on DL coverage for R19 NR NTN Phase 3 | vivo |
R4-2506795 | Discussion on other RRM requirements for Rel-19 NTN | Huawei, HiSilicon |
R4-2507187 | Discussion on RRM requirements for downlink coverage enhancement | ZTECorporation,Sanechips |
R4-2507362 | Impact of DL coverage enhancement on SMTC configuration and measurement requirements | Nokia |
R4-2507809 | Downlink coverage enhancement for NTN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506112 | Discussion on Rel-19 NR NTN phase3 RRM performance requirements | CATT |
R4-2506356 | Discussion on RRM Performance requirements for NTN for NR Phase 3 | Ericsson |
R4-2506434 | Discussion on measurement accuracy and test cases for RedCap UE over NTN | CMCC |
R4-2506554 | Discussion on RRM performance requirements of NTN for NR Phase 3 | vivo |
R4-2506796 | Discussion on performance requirements for Rel-19 NTN | Huawei, HiSilicon |
R4-2507195 | Discussion on RRM performance requirements for NR NTN Phase3 | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505502 | Discussion on Rel-19 NTN Demod performance requirements | Nokia |
R4-2505913 | On UE Demodulation Requirements for NTN Phase 3 | Apple |
R4-2505979 | View on demodulation requirement for NR NTN | Samsung |
R4-2506176 | Discussions on demodulation performance requirements for RedCap and eRedCap UEs over NR-NTN | QUALCOMM Europe Inc. - Spain |
R4-2506633 | Discussion on Rel-19 NR NTN Phase 3 performance requirements | Ericsson |
R4-2507028 | Discussion on NR NTN Phase 3 demodulation performance requirements | Huawei, HiSilicon |
R4-2507116 | Discussions on UE demodulation requirements for Rel-19 NR-NTN | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505578 | Topic summary for [115][229] IoT_NTN_Ph3 | Moderator (MediaTek) |
R4-2507847 | Topic summary for [115][315] IoT_NTN_Ph3 | Moderator (MediaTek) |
R4-2507866 | Topic summary for [115][334] IoT_NTN_Ph3_demod | Moderator (ZTE) |
TDoc | Title | Source |
---|---|---|
R4-2505832 | CR to TS 36.108: Correction of Regenerative Payload Figures | NEC, THALES, [HUAWEI, CATT, Ericsson] |
TDoc | Title | Source |
---|---|---|
R4-2507132 | OCC scheme on the RF requirements for IoT NTN | Sony |
R4-2507346 | Discussion on RF requirement impact for IoT NTN phase 3 | MediaTek (Hefei) Inc. |
R4-2507502 | RF imact for TDM DMRS for IoT NTN | Ericsson |
R4-2507762 | IoT NTN UL Capacity Enhancements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506435 | draftCR Introduce CB-msg3 based random access requirement for Cat-M1 UE over IOT-NTN | CMCC |
R4-2506486 | Discussion on RRM requirements for IoT NTN phase 3 | MediaTek inc. |
R4-2506487 | DraftCR on timing requirement for IoT NTN phase 3 | MediaTek inc. |
R4-2507363 | DraftCR to TS 36.133 to include CB-MSG3 Requirements for NB-IoT Ues | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2506436 | Discussion on test cases for IOT-NTN Phase 3 | CMCC |
R4-2506714 | Discussion on performance requirements for IoT NTN | Huawei, HiSilicon |
R4-2506983 | Discussion on RRM performance requirements for IoT NTN phase 3 | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2505503 | Discussion on IoT NTN SAN demodulation performance | Nokia |
R4-2505978 | View on demodulation requirement for IoT NTN | Samsung |
R4-2506177 | Discussion on IoT NTN SAN demodulation performance | Nokia |
R4-2506953 | Discussion on SAN demodulation performance requirements for IoT-NTN | ZTE Corporation, Sanechips |
R4-2507029 | Discussion on IoT NTN Phase3 demodulation performance requirements | Huawei, HiSilicon |
R4-2507107 | SAN demodulation requirements for IoT-NTN | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505579 | Topic summary for [115][230] IoT_NTN_TDD | Moderator (Qualcomm) |
R4-2507848 | Topic summary for [115][316] IoT_NTN_TDD_UE_SAN_RF | Moderator (Thales) |
TDoc | Title | Source |
---|---|---|
R4-2506170 | Proposal for LS reply to RAN1 on uplink precompensation in IoT-NTN TDD mode | Iridium Satellite LLC |
R4-2507732 | Proposal for LS reply to RAN1 on uplink pre-compensation for NB-IoT NTN TDD mode | Iridium Satellite LLC, THALES |
TDoc | Title | Source |
---|---|---|
R4-2506266 | draftCR to TS36.108 Add EVM requirement for IoT-NTN TDD band | ZTE Corporation, Sanechips |
R4-2507100 | Updates on SAN RF requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
R4-2507539 | Draft CR on TS 36.108 Clauses 3, 4.5, 4.6 and 5 - IoT_NTN_TDD | THALES, Iridium Satellite LLC |
TDoc | Title | Source |
---|---|---|
R4-2505592 | Discussion on UE RF requirements for NTN NB-IoT TDD mode | Nordic Semiconductor ASA |
R4-2506123 | On NS flags and A-MPR values for the IOT TDD band | Apple |
R4-2506164 | Nominated BW use for 249 and freq error | Qualcomm Incorporated |
R4-2506267 | draftCR to TS36.102 Add blocking requirement for IoT-NTN TDD band | ZTE Corporation, Sanechips |
R4-2506447 | Discussion on time/frequency pre-compensation for uplink transmission in NB-IoT NTN TDD mode | LG Electronics France |
R4-2507117 | Updates on UE RF requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
R4-2507538 | Draft CR on TS 36.102 Clause 5 - IoT_NTN_TDD | THALES, Iridium Satellite LLC |
R4-2507733 | LS Reply on precompensation for NB-IoT NTN TDD mode | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2506488 | Discussion on RRM requirements for IoT-NTN TDD mode | MediaTek inc. |
R4-2506715 | Discussion on RRM impact due to periodic pattern for IoT NTN | Huawei, HiSilicon |
R4-2507119 | Updates on RRM requirements for NTN NB-IoT TDD | THALES, Iridium Satellite LLC |
R4-2507189 | Discussion on IoT NTN TDD mode | ZTECorporation,Sanechips |
R4-2507364 | On the measurement framework for the new IOT TDD Punctured frame | Nokia |
R4-2507806 | RRM requirements for IoT NTN in TDD mode | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2505838 | Inputs to Rel-19 UE feature list | MediaTek inc. |
R4-2505890 | Views on el-19 RAN4 UE feature list for NR | Apple |
R4-2506198 | Summary of proposals for the Rel-19 RAN4 UE feature list for NR | Ericsson |
R4-2506437 | Rel-19 NR_ATG_enh input to UE feature list | CMCC |
R4-2506463 | Draft UE features list for Rel-19 NR | vivo |
R4-2506890 | Views on RAN4 Rel-19 UE feature list | Intel Corporation |
R4-2506892 | UE feature list for Rel-19 non-collocated Type 4 | KDDI Corporation |
R4-2506928 | Rel-19 RAN4 UE feature list for NR | OPPO |
R4-2507390 | Discussion on Rel-19 RAN4 UE feature list for NR for XR_Ph3 | Nokia |
R4-2507478 | View on Rel-19 RAN4 UE feature list | Huawei, HiSilicon |
R4-2507576 | Topic summary for [115][137] NR_feature_list | Moderator (CMCC) |
TDoc | Title | Source |
---|---|---|
R4-2505580 | Topic summary for [115][231] Reply_LS | Moderator (Apple) |
R4-2507577 | Topic summary for [115][138] NR_reply_LS_UE_RF | Moderator (Apple) |
R4-2507871 | Topic summary for [115][339] LS_BDaT | Moderator (Qualcomm) |
TDoc | Title | Source |
---|---|---|
R4-2505880 | Reply LS on Collision between MUSIM Gap and Measurement Gap | Apple |
R4-2506774 | (NR_DualTxRx_MUSIM-Core) Discussion on MUSIM gaps without priority | Huawei, HiSilicon |
R4-2506775 | (NR_DualTxRx_MUSIM-Core) CR on MUSIM gaps without priority | Huawei, HiSilicon |
R4-2506776 | (NR_DualTxRx_MUSIM-Core) CR on MUSIM gaps without priority R19 | Huawei, HiSilicon |
R4-2506899 | Discussion on RAN2 LS about MUSIM and MG collision | Ericsson |
R4-2506995 | Discussion on reply LS R2-2503163 | vivo |
R4-2507144 | Discussion on LS on Collision between MUSIM Gap and Measurement Gap | CMCC |
R4-2507196 | Discussion on MUSIM | ZTECorporation,Sanechips |
R4-2507199 | Draft LS to RAN2 on MUSIM gap and measurement gap | ZTECorporation,Sanechips |
R4-2507267 | Discussion on collision between MUSIM Gap and measurement Gap | Nokia |
R4-2507821 | Discussion on Collision between MUSIM Gap and Measurement Gap | MediaTek inc. |
R4-2507822 | Reply LS on collision handling between MUSIM gaps and MGs | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2507343 | Motivation for low-band carrier aggregation via switching enhancement in Rel-20 | Bell Mobility, TELUS, Murata, AT&T, BT plc, Apple, Skyworks Solutions, Inc. |
R4-2507377 | Progress update and next steps for the ETSI MCC band combination database | Nokia, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505804 | CR to 36.141 on framework simplification for co-location/co-existence requirements | Nokia |
R4-2505805 | CR to 37.104 on framework simplification for co-location/co-existence requirements | Nokia |
R4-2505806 | CR to 38.141-1 on framework simplification for co-location/co-existence requirements | Nokia |
R4-2505807 | On RAN task to work on framework simplification for co-location/co-existence requirements | Nokia |
R4-2506028 | Further discussion on framework simplification for co-location/co-existence requirements | CATT |
R4-2506029 | Draft CR for 38.106, on framework simplification for co-location/co-existence requirement | CATT |
R4-2506030 | Draft CR for 38.174, on framework simplification for co-location/co-existence requirement | CATT |
R4-2506031 | Draft CR for 37.145-1, on framework simplification for co-location/co-existence requirement | CATT |
R4-2506032 | Draft CR for 36.106, on framework simplification for co-location/co-existence requirement | CATT |
R4-2507145 | CR to TS 36.104: Introduction of new requirement structure for co-existence and co-location | Ericsson Inc. |
R4-2507148 | CR to TS 37.105: Introduction of new requirement structure for co-existence and co-location | Ericsson Inc. |
R4-2507150 | CR to TS 38.104: Introduction of new requirement structure for transmitter spurious emission | Ericsson |
R4-2507156 | Discussion paper RAN task coex coloc | Ericsson |
R4-2507522 | (TEI19) CR to TS 38.115-1 spec structure simplification for co-locationco-existence requirements | ZTE Corporation |
R4-2507523 | (TEI19) CR to TS 38.176-1: spec structure simplification for co-locationco-existence requirements | ZTE Corporation |
R4-2507524 | (TEI19) CR to TS 38.176-2 spec structure simplification for co-location/co-existence requirements | ZTE Corporation |
R4-2507525 | (TEI19) CR to TS 37.141: spec structure simplification for co-location/co-existence requirements | ZTE Corporation |
R4-2507827 | Discussion on open issues related to the implementation of framework simplification for co-location/co-existence requirements | Huawei, HiSilicon |
R4-2507828 | Draft CR to TS 38-141-2: simplification of co-location and co-existence requirement tables | Huawei, HiSilicon |
R4-2507829 | Draft CR to TS 37.145-2: simplification of co-location and co-existence requirement tables | Huawei, HiSilicon |
R4-2507830 | Draft CR to TS 36.143: simplification of co-location and co-existence requirement tables | Huawei, HiSilicon |
R4-2507872 | Topic summary for [115][340] BSRF_Simplify_CoLo_Coex | Moderator (Ericsson) |
TDoc | Title | Source |
---|---|---|
R4-2506224 | Discussion on NTN specificaiton handling | China Telecom Corporation Ltd. |
R4-2507504 | Specification impact on spectrum sharing by multiple RATs | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2505427 | New WID on enhanced low NR band carrier aggregation via switching | Apple |
R4-2505651 | New WID on Introduction of NR TDD 4.9GHz Band for US Operation | Fujitsu Limited |
R4-2505652 | Additional requirements for 4.9GHz new band for US | Fujitsu Limited |
R4-2505839 | MediaTek Views on Rel-20 RAN4 5G-A scope | MediaTek inc. |
R4-2505840 | MediaTek 6G RAN4 Views | MediaTek inc. |
R4-2506124 | Views on 29dBm high-power handheld devices for the FDD terrestrial and satellite bands in Rel-20 | Apple |
R4-2506125 | Views on NTN RF enhancements in Rel-20 | Apple |
R4-2506126 | Views on further enhancement of TRP TRS in Rel-20 | Apple |
R4-2506832 | MPR reduction for upper 6GHz by ACLR relaxation | Huawei, HiSilicon |
R4-2506866 | New WID on New Power Class and enhanced requirements for NR and IoT NTN | vivo |
R4-2506889 | Intel views on RAN4 Rel-20 5G-Advanced | Intel Corporation |
R4-2506893 | Motivation on supporting Intra-band non-collocated EN-DC/NR-CA deployment in Release 20 (Type 3 UE for handheld) | KDDI, NTT Docomo, SoftBank, KT, LG Uplus |
R4-2506896 | Observation on UE simulation assumption for A-MPR | KDDI Corporation |
R4-2506912 | WF on 200 MHz channel bandwidth | KDDI, China Unicom, China Telecom, BT, Bouygues Telecom, Deutsche Telekom, KPN, Vodafone, Orange, Odido, Telefonica, Telenor, TIM, Telia Company, Spark NZ, Jio Platforms(JPL), Telstra, NTT Docomo, SoftBank, CKH IOD UK LTD, Ericsson, Huawei |
R4-2507058 | Considerations on Rel-20 5G-A RAN4 package | Ericsson |
R4-2507059 | Considerations on RAN4 aspects of the 6G Study Item | Ericsson |
R4-2507133 | (e)Redcap enhancement in Rel-20 | Sony |
R4-2507526 | Discussion on Rel-20 BS RF enhancement | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2505788 | Overview for Rel-20 5G-A RAN4 package | Xiaomi |
R4-2505789 | Proposal on Rel-20 5G-A RAN4 NTN WI scope | Xiaomi |
R4-2505914 | Apple's view on Rel-20 Demod Ph6 | Apple |
R4-2505939 | Motivation paper for Rel-20 RRM phase 6 WI | Apple |
R4-2506223 | Motivation for 3MHz Channel Bandwidth for (e)RedCap | Anterix |
R4-2507907 | (reserved) | Main Session |
R4-2507908 | (reserved) | Main Session |
R4-2507909 | (reserved) | Main Session |
R4-2507910 | (reserved) | Main Session |
R4-2507911 | (reserved) | Main Session |
R4-2507912 | (reserved) | Main Session |
R4-2507913 | (reserved) | Main Session |
R4-2507914 | (reserved) | Main Session |
R4-2507915 | (reserved) | Main Session |
R4-2507916 | (reserved) | Main Session |
R4-2507917 | (reserved) | Main Session |
R4-2507918 | (reserved) | Main Session |
R4-2507919 | (reserved) | Main Session |
R4-2507920 | (reserved) | Main Session |
R4-2507921 | (reserved) | Main Session |
R4-2507922 | (reserved) | Main Session |
R4-2507923 | (reserved) | Main Session |
R4-2507924 | (reserved) | Main Session |
R4-2507925 | (reserved) | Main Session |
R4-2507926 | (reserved) | Main Session |
R4-2507927 | (reserved) | Main Session |
R4-2507928 | (reserved) | Main Session |
R4-2507929 | (reserved) | Main Session |
R4-2507930 | (reserved) | Main Session |
R4-2507931 | (reserved) | Main Session |
R4-2507932 | (reserved) | Main Session |
R4-2507933 | (reserved) | Main Session |
R4-2507934 | (reserved) | Main Session |
R4-2507935 | (reserved) | Main Session |
R4-2507936 | (reserved) | Main Session |
R4-2507937 | (reserved) | Main Session |
R4-2507938 | (reserved) | Main Session |
R4-2507939 | (reserved) | Main Session |
R4-2507940 | (reserved) | Main Session |
R4-2507941 | (reserved) | Main Session |
R4-2507942 | (reserved) | Main Session |
R4-2507943 | (reserved) | Main Session |
R4-2507944 | (reserved) | Main Session |
R4-2507945 | (reserved) | Main Session |
R4-2507946 | (reserved) | Main Session |
R4-2507947 | (reserved) | Main Session |
R4-2507948 | (reserved) | Main Session |
R4-2507949 | (reserved) | Main Session |
R4-2507950 | (reserved) | Main Session |
R4-2507951 | (reserved) | Main Session |
R4-2507952 | (reserved) | Main Session |
R4-2507953 | (reserved) | Main Session |
R4-2507954 | (reserved) | Main Session |
R4-2507955 | (reserved) | Main Session |
R4-2507956 | (reserved) | Main Session |
R4-2507957 | (reserved) | Main Session |
R4-2507958 | (reserved) | Main Session |
R4-2507959 | (reserved) | Main Session |
R4-2507960 | (reserved) | Main Session |
R4-2507961 | (reserved) | Main Session |
R4-2507962 | (reserved) | Main Session |
R4-2507963 | (reserved) | Main Session |
R4-2507964 | (reserved) | Main Session |
R4-2507965 | (reserved) | Main Session |
R4-2507966 | (reserved) | Main Session |
R4-2507967 | (reserved) | Main Session |
R4-2507968 | (reserved) | Main Session |
R4-2507969 | (reserved) | Main Session |
R4-2507970 | (reserved) | Main Session |
R4-2507971 | (reserved) | Main Session |
R4-2507972 | (reserved) | Main Session |
R4-2507973 | (reserved) | Main Session |
R4-2507974 | (reserved) | Main Session |
R4-2507975 | (reserved) | Main Session |
R4-2507976 | (reserved) | Main Session |
R4-2507977 | (reserved) | Main Session |
R4-2507978 | (reserved) | Main Session |
R4-2507979 | (reserved) | Main Session |
R4-2507980 | (reserved) | Main Session |
R4-2507981 | (reserved) | Main Session |
R4-2507982 | (reserved) | Main Session |
R4-2507983 | (reserved) | Main Session |
R4-2507984 | (reserved) | Main Session |
R4-2507985 | (reserved) | Main Session |
R4-2507986 | (reserved) | Main Session |
R4-2507987 | (reserved) | Main Session |
R4-2507988 | (reserved) | Main Session |
R4-2507989 | (reserved) | Main Session |
R4-2507990 | (reserved) | Main Session |
R4-2507991 | (reserved) | Main Session |
R4-2507992 | (reserved) | Main Session |
R4-2507993 | (reserved) | Main Session |
R4-2507994 | (reserved) | Main Session |
R4-2507995 | (reserved) | Main Session |
R4-2507996 | (reserved) | Main Session |
R4-2507997 | (reserved) | Main Session |
R4-2507998 | (reserved) | Main Session |
R4-2507999 | (reserved) | Main Session |
R4-2508000 | (reserved) | Main Session |
R4-2508001 | (reserved) | Main Session |
R4-2508002 | (reserved) | Main Session |
R4-2508003 | (reserved) | Main Session |
R4-2508004 | (reserved) | Main Session |
R4-2508005 | (reserved) | Main Session |
R4-2508006 | (reserved) | Main Session |
R4-2508007 | (reserved) | Main Session |
R4-2508008 | (reserved) | Main Session |
R4-2508009 | (reserved) | Main Session |
R4-2508010 | (reserved) | Main Session |
R4-2508011 | (reserved) | Main Session |
R4-2508012 | (reserved) | Main Session |
R4-2508013 | (reserved) | Main Session |
R4-2508014 | (reserved) | Main Session |
R4-2508015 | (reserved) | Main Session |
R4-2508016 | (reserved) | Main Session |
R4-2508017 | (reserved) | Main Session |
R4-2508018 | (reserved) | Main Session |
R4-2508019 | (reserved) | Main Session |
R4-2508020 | (reserved) | Main Session |
R4-2508021 | (reserved) | Main Session |
R4-2508022 | (reserved) | Main Session |
R4-2508023 | (reserved) | Main Session |
R4-2508024 | (reserved) | Main Session |
R4-2508025 | (reserved) | Main Session |
R4-2508026 | (reserved) | Main Session |
R4-2508027 | (reserved) | Main Session |
R4-2508028 | (reserved) | Main Session |
R4-2508029 | (reserved) | Main Session |
R4-2508030 | (reserved) | Main Session |
R4-2508031 | (reserved) | Main Session |
R4-2508032 | (reserved) | Main Session |
R4-2508033 | (reserved) | Main Session |
R4-2508034 | (reserved) | Main Session |
R4-2508035 | (reserved) | Main Session |
R4-2508036 | (reserved) | Main Session |
R4-2508037 | (reserved) | Main Session |
R4-2508038 | (reserved) | Main Session |
R4-2508039 | (reserved) | Main Session |
R4-2508040 | (reserved) | Main Session |
R4-2508041 | (reserved) | Main Session |
R4-2508042 | (reserved) | Main Session |
R4-2508043 | (reserved) | Main Session |
R4-2508044 | (reserved) | Main Session |
R4-2508045 | (reserved) | Main Session |
R4-2508046 | (reserved) | Main Session |
R4-2508047 | (reserved) | Main Session |
R4-2508048 | (reserved) | Main Session |
R4-2508049 | (reserved) | Main Session |
R4-2508050 | (reserved) | Main Session |
R4-2508051 | (reserved) | Main Session |
R4-2508052 | (reserved) | Main Session |
R4-2508053 | (reserved) | Main Session |
R4-2508054 | (reserved) | Main Session |
R4-2508055 | (reserved) | Main Session |
R4-2508056 | (reserved) | Main Session |
R4-2508057 | (reserved) | Main Session |
R4-2508058 | (reserved) | Main Session |
R4-2508059 | (reserved) | Main Session |
R4-2508060 | (reserved) | Main Session |
R4-2508061 | (reserved) | Main Session |
R4-2508062 | (reserved) | Main Session |
R4-2508063 | (reserved) | Main Session |
R4-2508064 | (reserved) | Main Session |
R4-2508065 | (reserved) | Main Session |
R4-2508066 | (reserved) | Main Session |
R4-2508067 | (reserved) | Main Session |
R4-2508068 | (reserved) | Main Session |
R4-2508069 | (reserved) | Main Session |
R4-2508070 | (reserved) | Main Session |
R4-2508071 | (reserved) | Main Session |
R4-2508072 | (reserved) | Main Session |
R4-2508073 | (reserved) | Main Session |
R4-2508074 | (reserved) | Main Session |
R4-2508075 | (reserved) | Main Session |
R4-2508076 | (reserved) | Main Session |
R4-2508077 | (reserved) | Main Session |
R4-2508078 | (reserved) | Main Session |
R4-2508079 | (reserved) | Main Session |
R4-2508080 | (reserved) | Main Session |
R4-2508081 | (reserved) | Main Session |
R4-2508082 | (reserved) | Main Session |
R4-2508083 | (reserved) | Main Session |
R4-2508084 | (reserved) | Main Session |
R4-2508085 | (reserved) | Main Session |
R4-2508086 | (reserved) | Main Session |
R4-2508087 | (reserved) | Main Session |
R4-2508088 | (reserved) | Main Session |
R4-2508089 | (reserved) | Main Session |
R4-2508090 | (reserved) | Main Session |
R4-2508091 | (reserved) | Main Session |
R4-2508092 | (reserved) | Main Session |
R4-2508093 | (reserved) | Main Session |
R4-2508094 | (reserved) | Main Session |
R4-2508095 | (reserved) | Main Session |
R4-2508096 | (reserved) | Main Session |
R4-2508097 | (reserved) | Main Session |
R4-2508098 | (reserved) | Main Session |
R4-2508099 | (reserved) | Main Session |
R4-2508100 | (reserved) | Main Session |
R4-2508101 | (reserved) | Main Session |
R4-2508102 | (reserved) | Main Session |
R4-2508103 | (reserved) | Main Session |
R4-2508104 | (reserved) | Main Session |
R4-2508105 | (reserved) | Main Session |
R4-2508106 | (reserved) | Main Session |
R4-2508107 | (reserved) | Main Session |
R4-2508108 | (reserved) | Main Session |
R4-2508109 | (reserved) | Main Session |
R4-2508110 | (reserved) | Main Session |
R4-2508111 | (reserved) | Main Session |
R4-2508112 | (reserved) | Main Session |
R4-2508113 | (reserved) | Main Session |
R4-2508114 | (reserved) | Main Session |
R4-2508115 | (reserved) | Main Session |
R4-2508116 | (reserved) | Main Session |
R4-2508117 | (reserved) | Main Session |
R4-2508118 | (reserved) | Main Session |
R4-2508119 | (reserved) | Main Session |
R4-2508120 | (reserved) | Main Session |
R4-2508121 | (reserved) | Main Session |
R4-2508122 | (reserved) | Main Session |
R4-2508123 | (reserved) | Main Session |
R4-2508124 | (reserved) | Main Session |
R4-2508125 | (reserved) | Main Session |
R4-2508126 | (reserved) | Main Session |
R4-2508127 | (reserved) | Main Session |
R4-2508128 | (reserved) | Main Session |
R4-2508129 | (reserved) | Main Session |
R4-2508130 | (reserved) | Main Session |
R4-2508131 | (reserved) | Main Session |
R4-2508132 | (reserved) | Main Session |
R4-2508133 | (reserved) | Main Session |
R4-2508134 | (reserved) | Main Session |
R4-2508135 | (reserved) | Main Session |
R4-2508136 | (reserved) | Main Session |
R4-2508137 | (reserved) | Main Session |
R4-2508138 | (reserved) | Main Session |
R4-2508139 | (reserved) | Main Session |
R4-2508140 | (reserved) | Main Session |
R4-2508141 | (reserved) | Main Session |
R4-2508142 | (reserved) | Main Session |
R4-2508143 | (reserved) | Main Session |
R4-2508144 | (reserved) | Main Session |
R4-2508145 | (reserved) | Main Session |
R4-2508146 | (reserved) | Main Session |
R4-2508147 | (reserved) | Main Session |
R4-2508148 | (reserved) | Main Session |
R4-2508149 | (reserved) | Main Session |
R4-2508150 | (reserved) | Main Session |
R4-2508151 | (reserved) | Main Session |
R4-2508152 | (reserved) | Main Session |
R4-2508153 | (reserved) | Main Session |
R4-2508154 | (reserved) | Main Session |
R4-2508155 | (reserved) | Main Session |
R4-2508156 | (reserved) | Main Session |
R4-2508157 | (reserved) | Main Session |
R4-2508158 | (reserved) | Main Session |
R4-2508159 | (reserved) | Main Session |
R4-2508160 | (reserved) | Main Session |
R4-2508161 | (reserved) | Main Session |
R4-2508162 | (reserved) | Main Session |
R4-2508163 | (reserved) | Main Session |
R4-2508164 | (reserved) | Main Session |
R4-2508165 | (reserved) | Main Session |
R4-2508166 | (reserved) | Main Session |
R4-2508167 | (reserved) | Main Session |
R4-2508168 | (reserved) | Main Session |
R4-2508169 | (reserved) | Main Session |
R4-2508170 | (reserved) | Main Session |
R4-2508171 | (reserved) | Main Session |
R4-2508172 | (reserved) | Main Session |
R4-2508173 | (reserved) | Main Session |
R4-2508174 | (reserved) | Main Session |
R4-2508175 | (reserved) | Main Session |
R4-2508176 | (reserved) | Main Session |
R4-2508177 | (reserved) | Main Session |
R4-2508178 | (reserved) | Main Session |
R4-2508179 | (reserved) | Main Session |
R4-2508180 | (reserved) | Main Session |
R4-2508181 | (reserved) | Main Session |
R4-2508182 | (reserved) | Main Session |
R4-2508183 | (reserved) | Main Session |
R4-2508184 | (reserved) | Main Session |
R4-2508185 | (reserved) | Main Session |
R4-2508186 | (reserved) | Main Session |
R4-2508187 | (reserved) | Main Session |
R4-2508188 | (reserved) | Main Session |
R4-2508189 | (reserved) | Main Session |
R4-2508190 | (reserved) | Main Session |
R4-2508191 | (reserved) | Main Session |
R4-2508192 | (reserved) | Main Session |
R4-2508193 | (reserved) | Main Session |
R4-2508194 | (reserved) | Main Session |
R4-2508195 | (reserved) | Main Session |
R4-2508196 | (reserved) | Main Session |
R4-2508197 | (reserved) | Main Session |
R4-2508198 | (reserved) | Main Session |
R4-2508199 | (reserved) | Main Session |
R4-2508200 | (reserved) | Main Session |
R4-2508201 | (reserved) | Main Session |
R4-2508202 | (reserved) | Main Session |
R4-2508203 | (reserved) | Main Session |
R4-2508204 | (reserved) | Main Session |
R4-2508205 | (reserved) | Main Session |
R4-2508206 | (reserved) | Main Session |
R4-2508207 | (reserved) | Main Session |
R4-2508208 | (reserved) | Main Session |
R4-2508209 | (reserved) | Main Session |
R4-2508210 | (reserved) | Main Session |
R4-2508211 | (reserved) | Main Session |
R4-2508212 | (reserved) | Main Session |
R4-2508213 | (reserved) | Main Session |
R4-2508214 | (reserved) | Main Session |
R4-2508215 | (reserved) | Main Session |
R4-2508216 | (reserved) | Main Session |
R4-2508217 | (reserved) | Main Session |
R4-2508218 | (reserved) | Main Session |
R4-2508219 | (reserved) | Main Session |
R4-2508220 | (reserved) | Main Session |
R4-2508221 | (reserved) | Main Session |
R4-2508222 | (reserved) | Main Session |
R4-2508223 | (reserved) | Main Session |
R4-2508224 | (reserved) | Main Session |
R4-2508225 | (reserved) | Main Session |
R4-2508226 | (reserved) | Main Session |
R4-2508227 | (reserved) | Main Session |
R4-2508228 | (reserved) | Main Session |
R4-2508229 | (reserved) | Main Session |
R4-2508230 | (reserved) | Main Session |
R4-2508231 | (reserved) | Main Session |
R4-2508232 | (reserved) | Main Session |
R4-2508233 | (reserved) | Main Session |
R4-2508234 | (reserved) | Main Session |
R4-2508235 | (reserved) | Main Session |
R4-2508236 | (reserved) | Main Session |
R4-2508237 | (reserved) | Main Session |
R4-2508238 | (reserved) | Main Session |
R4-2508239 | (reserved) | Main Session |
R4-2508240 | (reserved) | Main Session |
R4-2508241 | (reserved) | Main Session |
R4-2508242 | (reserved) | Main Session |
R4-2508243 | (reserved) | Main Session |
R4-2508244 | (reserved) | Main Session |
R4-2508245 | (reserved) | Main Session |
R4-2508246 | (reserved) | Main Session |
R4-2508247 | (reserved) | Main Session |
R4-2508248 | (reserved) | Main Session |
R4-2508249 | (reserved) | Main Session |
R4-2508250 | (reserved) | Main Session |
R4-2508251 | (reserved) | Main Session |
R4-2508252 | (reserved) | Main Session |
R4-2508253 | (reserved) | Main Session |
R4-2508254 | (reserved) | Main Session |
R4-2508255 | (reserved) | Main Session |
R4-2508256 | (reserved) | Main Session |
R4-2508257 | (reserved) | RRM Session |
R4-2508258 | (reserved) | RRM Session |
R4-2508259 | (reserved) | RRM Session |
R4-2508260 | (reserved) | RRM Session |
R4-2508261 | (reserved) | RRM Session |
R4-2508262 | (reserved) | RRM Session |
R4-2508263 | (reserved) | RRM Session |
R4-2508264 | (reserved) | RRM Session |
R4-2508265 | (reserved) | RRM Session |
R4-2508266 | (reserved) | RRM Session |
R4-2508267 | (reserved) | RRM Session |
R4-2508268 | (reserved) | RRM Session |
R4-2508269 | (reserved) | RRM Session |
R4-2508270 | (reserved) | RRM Session |
R4-2508271 | (reserved) | RRM Session |
R4-2508272 | (reserved) | RRM Session |
R4-2508273 | (reserved) | RRM Session |
R4-2508274 | (reserved) | RRM Session |
R4-2508275 | (reserved) | RRM Session |
R4-2508276 | (reserved) | RRM Session |
R4-2508277 | (reserved) | RRM Session |
R4-2508278 | (reserved) | RRM Session |
R4-2508279 | (reserved) | RRM Session |
R4-2508280 | (reserved) | RRM Session |
R4-2508281 | (reserved) | RRM Session |
R4-2508282 | (reserved) | RRM Session |
R4-2508283 | (reserved) | RRM Session |
R4-2508284 | (reserved) | RRM Session |
R4-2508285 | (reserved) | RRM Session |
R4-2508286 | (reserved) | RRM Session |
R4-2508287 | (reserved) | RRM Session |
R4-2508288 | (reserved) | RRM Session |
R4-2508289 | (reserved) | RRM Session |
R4-2508290 | (reserved) | RRM Session |
R4-2508291 | (reserved) | RRM Session |
R4-2508292 | (reserved) | RRM Session |
R4-2508293 | (reserved) | RRM Session |
R4-2508294 | (reserved) | RRM Session |
R4-2508295 | (reserved) | RRM Session |
R4-2508296 | (reserved) | RRM Session |
R4-2508297 | (reserved) | RRM Session |
R4-2508298 | (reserved) | RRM Session |
R4-2508299 | (reserved) | RRM Session |
R4-2508300 | (reserved) | RRM Session |
R4-2508301 | (reserved) | RRM Session |
R4-2508302 | (reserved) | RRM Session |
R4-2508303 | (reserved) | RRM Session |
R4-2508304 | (reserved) | RRM Session |
R4-2508305 | (reserved) | RRM Session |
R4-2508306 | (reserved) | RRM Session |
R4-2508307 | (reserved) | RRM Session |
R4-2508308 | (reserved) | RRM Session |
R4-2508309 | (reserved) | RRM Session |
R4-2508310 | (reserved) | RRM Session |
R4-2508311 | (reserved) | RRM Session |
R4-2508312 | (reserved) | RRM Session |
R4-2508313 | (reserved) | RRM Session |
R4-2508314 | (reserved) | RRM Session |
R4-2508315 | (reserved) | RRM Session |
R4-2508316 | (reserved) | RRM Session |
R4-2508317 | (reserved) | RRM Session |
R4-2508318 | (reserved) | RRM Session |
R4-2508319 | (reserved) | RRM Session |
R4-2508320 | (reserved) | RRM Session |
R4-2508321 | (reserved) | RRM Session |
R4-2508322 | (reserved) | RRM Session |
R4-2508323 | (reserved) | RRM Session |
R4-2508324 | (reserved) | RRM Session |
R4-2508325 | (reserved) | RRM Session |
R4-2508326 | (reserved) | RRM Session |
R4-2508327 | (reserved) | RRM Session |
R4-2508328 | (reserved) | RRM Session |
R4-2508329 | (reserved) | RRM Session |
R4-2508330 | (reserved) | RRM Session |
R4-2508331 | (reserved) | RRM Session |
R4-2508332 | (reserved) | RRM Session |
R4-2508333 | (reserved) | RRM Session |
R4-2508334 | (reserved) | RRM Session |
R4-2508335 | (reserved) | RRM Session |
R4-2508336 | (reserved) | RRM Session |
R4-2508337 | (reserved) | RRM Session |
R4-2508338 | (reserved) | RRM Session |
R4-2508339 | (reserved) | RRM Session |
R4-2508340 | (reserved) | RRM Session |
R4-2508341 | (reserved) | RRM Session |
R4-2508342 | (reserved) | RRM Session |
R4-2508343 | (reserved) | RRM Session |
R4-2508344 | (reserved) | RRM Session |
R4-2508345 | (reserved) | RRM Session |
R4-2508346 | (reserved) | RRM Session |
R4-2508347 | (reserved) | RRM Session |
R4-2508348 | (reserved) | RRM Session |
R4-2508349 | (reserved) | RRM Session |
R4-2508350 | (reserved) | RRM Session |
R4-2508351 | (reserved) | RRM Session |
R4-2508352 | (reserved) | RRM Session |
R4-2508353 | (reserved) | RRM Session |
R4-2508354 | (reserved) | RRM Session |
R4-2508355 | (reserved) | RRM Session |
R4-2508356 | (reserved) | RRM Session |
R4-2508357 | (reserved) | RRM Session |
R4-2508358 | (reserved) | RRM Session |
R4-2508359 | (reserved) | RRM Session |
R4-2508360 | (reserved) | RRM Session |
R4-2508361 | (reserved) | RRM Session |
R4-2508362 | (reserved) | RRM Session |
R4-2508363 | (reserved) | RRM Session |
R4-2508364 | (reserved) | RRM Session |
R4-2508365 | (reserved) | RRM Session |
R4-2508366 | (reserved) | RRM Session |
R4-2508367 | (reserved) | RRM Session |
R4-2508368 | (reserved) | RRM Session |
R4-2508369 | (reserved) | RRM Session |
R4-2508370 | (reserved) | RRM Session |
R4-2508371 | (reserved) | RRM Session |
R4-2508372 | (reserved) | RRM Session |
R4-2508373 | (reserved) | RRM Session |
R4-2508374 | (reserved) | RRM Session |
R4-2508375 | (reserved) | RRM Session |
R4-2508376 | (reserved) | RRM Session |
R4-2508377 | (reserved) | RRM Session |
R4-2508378 | (reserved) | RRM Session |
R4-2508379 | (reserved) | RRM Session |
R4-2508380 | (reserved) | RRM Session |
R4-2508381 | (reserved) | RRM Session |
R4-2508382 | (reserved) | RRM Session |
R4-2508383 | (reserved) | RRM Session |
R4-2508384 | (reserved) | RRM Session |
R4-2508385 | (reserved) | RRM Session |
R4-2508386 | (reserved) | RRM Session |
R4-2508387 | (reserved) | RRM Session |
R4-2508388 | (reserved) | RRM Session |
R4-2508389 | (reserved) | RRM Session |
R4-2508390 | (reserved) | RRM Session |
R4-2508391 | (reserved) | RRM Session |
R4-2508392 | (reserved) | RRM Session |
R4-2508393 | (reserved) | RRM Session |
R4-2508394 | (reserved) | RRM Session |
R4-2508395 | (reserved) | RRM Session |
R4-2508396 | (reserved) | RRM Session |
R4-2508397 | (reserved) | RRM Session |
R4-2508398 | (reserved) | RRM Session |
R4-2508399 | (reserved) | RRM Session |
R4-2508400 | (reserved) | RRM Session |
R4-2508401 | (reserved) | RRM Session |
R4-2508402 | (reserved) | RRM Session |
R4-2508403 | (reserved) | RRM Session |
R4-2508404 | (reserved) | RRM Session |
R4-2508405 | (reserved) | RRM Session |
R4-2508406 | (reserved) | RRM Session |
R4-2508407 | (reserved) | RRM Session |
R4-2508408 | (reserved) | RRM Session |
R4-2508409 | (reserved) | RRM Session |
R4-2508410 | (reserved) | RRM Session |
R4-2508411 | (reserved) | RRM Session |
R4-2508412 | (reserved) | RRM Session |
R4-2508413 | (reserved) | RRM Session |
R4-2508414 | (reserved) | RRM Session |
R4-2508415 | (reserved) | RRM Session |
R4-2508416 | (reserved) | RRM Session |
R4-2508417 | (reserved) | RRM Session |
R4-2508418 | (reserved) | RRM Session |
R4-2508419 | (reserved) | RRM Session |
R4-2508420 | (reserved) | RRM Session |
R4-2508421 | (reserved) | RRM Session |
R4-2508422 | (reserved) | RRM Session |
R4-2508423 | (reserved) | RRM Session |
R4-2508424 | (reserved) | RRM Session |
R4-2508425 | (reserved) | RRM Session |
R4-2508426 | (reserved) | RRM Session |
R4-2508427 | (reserved) | RRM Session |
R4-2508428 | (reserved) | RRM Session |
R4-2508429 | (reserved) | RRM Session |
R4-2508430 | (reserved) | RRM Session |
R4-2508431 | (reserved) | RRM Session |
R4-2508432 | (reserved) | RRM Session |
R4-2508433 | (reserved) | RRM Session |
R4-2508434 | (reserved) | RRM Session |
R4-2508435 | (reserved) | RRM Session |
R4-2508436 | (reserved) | RRM Session |
R4-2508437 | (reserved) | RRM Session |
R4-2508438 | (reserved) | RRM Session |
R4-2508439 | (reserved) | RRM Session |
R4-2508440 | (reserved) | RRM Session |
R4-2508441 | (reserved) | RRM Session |
R4-2508442 | (reserved) | RRM Session |
R4-2508443 | (reserved) | RRM Session |
R4-2508444 | (reserved) | RRM Session |
R4-2508445 | (reserved) | RRM Session |
R4-2508446 | (reserved) | RRM Session |
R4-2508447 | (reserved) | RRM Session |
R4-2508448 | (reserved) | RRM Session |
R4-2508449 | (reserved) | RRM Session |
R4-2508450 | (reserved) | RRM Session |
R4-2508451 | (reserved) | RRM Session |
R4-2508452 | (reserved) | RRM Session |
R4-2508453 | (reserved) | RRM Session |
R4-2508454 | (reserved) | RRM Session |
R4-2508455 | (reserved) | RRM Session |
R4-2508456 | (reserved) | RRM Session |
R4-2508457 | (reserved) | RRM Session |
R4-2508458 | (reserved) | RRM Session |
R4-2508459 | (reserved) | RRM Session |
R4-2508460 | (reserved) | RRM Session |
R4-2508461 | (reserved) | RRM Session |
R4-2508462 | (reserved) | RRM Session |
R4-2508463 | (reserved) | RRM Session |
R4-2508464 | (reserved) | RRM Session |
R4-2508465 | (reserved) | RRM Session |
R4-2508466 | (reserved) | RRM Session |
R4-2508467 | (reserved) | RRM Session |
R4-2508468 | (reserved) | RRM Session |
R4-2508469 | (reserved) | RRM Session |
R4-2508470 | (reserved) | RRM Session |
R4-2508471 | (reserved) | RRM Session |
R4-2508472 | (reserved) | RRM Session |
R4-2508473 | (reserved) | RRM Session |
R4-2508474 | (reserved) | RRM Session |
R4-2508475 | (reserved) | RRM Session |
R4-2508476 | (reserved) | RRM Session |
R4-2508477 | (reserved) | RRM Session |
R4-2508478 | (reserved) | RRM Session |
R4-2508479 | (reserved) | RRM Session |
R4-2508480 | (reserved) | RRM Session |
R4-2508481 | (reserved) | RRM Session |
R4-2508482 | (reserved) | RRM Session |
R4-2508483 | (reserved) | RRM Session |
R4-2508484 | (reserved) | RRM Session |
R4-2508485 | (reserved) | RRM Session |
R4-2508486 | (reserved) | RRM Session |
R4-2508487 | (reserved) | RRM Session |
R4-2508488 | (reserved) | RRM Session |
R4-2508489 | (reserved) | RRM Session |
R4-2508490 | (reserved) | RRM Session |
R4-2508491 | (reserved) | RRM Session |
R4-2508492 | (reserved) | RRM Session |
R4-2508493 | (reserved) | RRM Session |
R4-2508494 | (reserved) | RRM Session |
R4-2508495 | (reserved) | RRM Session |
R4-2508496 | (reserved) | RRM Session |
R4-2508497 | (reserved) | RRM Session |
R4-2508498 | (reserved) | RRM Session |
R4-2508499 | (reserved) | RRM Session |
R4-2508500 | (reserved) | RRM Session |
R4-2508501 | (reserved) | RRM Session |
R4-2508502 | (reserved) | RRM Session |
R4-2508503 | (reserved) | RRM Session |
R4-2508504 | (reserved) | RRM Session |
R4-2508505 | (reserved) | RRM Session |
R4-2508506 | (reserved) | RRM Session |
R4-2508507 | (reserved) | RRM Session |
R4-2508508 | (reserved) | RRM Session |
R4-2508509 | (reserved) | RRM Session |
R4-2508510 | (reserved) | RRM Session |
R4-2508511 | (reserved) | RRM Session |
R4-2508512 | (reserved) | RRM Session |
R4-2508513 | (reserved) | RRM Session |
R4-2508514 | (reserved) | RRM Session |
R4-2508515 | (reserved) | RRM Session |
R4-2508516 | (reserved) | RRM Session |
R4-2508517 | (reserved) | RRM Session |
R4-2508518 | (reserved) | RRM Session |
R4-2508519 | (reserved) | RRM Session |
R4-2508520 | (reserved) | RRM Session |
R4-2508521 | (reserved) | RRM Session |
R4-2508522 | (reserved) | RRM Session |
R4-2508523 | (reserved) | RRM Session |
R4-2508524 | (reserved) | RRM Session |
R4-2508525 | (reserved) | RRM Session |
R4-2508526 | (reserved) | RRM Session |
R4-2508527 | (reserved) | RRM Session |
R4-2508528 | (reserved) | RRM Session |
R4-2508529 | (reserved) | RRM Session |
R4-2508530 | (reserved) | RRM Session |
R4-2508531 | (reserved) | RRM Session |
R4-2508532 | (reserved) | RRM Session |
R4-2508533 | (reserved) | RRM Session |
R4-2508534 | (reserved) | RRM Session |
R4-2508535 | (reserved) | RRM Session |
R4-2508536 | (reserved) | RRM Session |
R4-2508537 | (reserved) | RRM Session |
R4-2508538 | (reserved) | RRM Session |
R4-2508539 | (reserved) | RRM Session |
R4-2508540 | (reserved) | RRM Session |
R4-2508541 | (reserved) | RRM Session |
R4-2508542 | (reserved) | RRM Session |
R4-2508543 | (reserved) | RRM Session |
R4-2508544 | (reserved) | RRM Session |
R4-2508545 | (reserved) | RRM Session |
R4-2508546 | (reserved) | RRM Session |
R4-2508547 | (reserved) | RRM Session |
R4-2508548 | (reserved) | RRM Session |
R4-2508549 | (reserved) | RRM Session |
R4-2508550 | (reserved) | RRM Session |
R4-2508551 | (reserved) | RRM Session |
R4-2508552 | (reserved) | RRM Session |
R4-2508553 | (reserved) | RRM Session |
R4-2508554 | (reserved) | RRM Session |
R4-2508555 | (reserved) | RRM Session |
R4-2508556 | (reserved) | RRM Session |
R4-2508557 | (reserved) | RRM Session |
R4-2508558 | (reserved) | RRM Session |
R4-2508559 | (reserved) | RRM Session |
R4-2508560 | (reserved) | RRM Session |
R4-2508561 | (reserved) | RRM Session |
R4-2508562 | (reserved) | RRM Session |
R4-2508563 | (reserved) | RRM Session |
R4-2508564 | (reserved) | RRM Session |
R4-2508565 | (reserved) | RRM Session |
R4-2508566 | (reserved) | RRM Session |
R4-2508567 | (reserved) | RRM Session |
R4-2508568 | (reserved) | RRM Session |
R4-2508569 | (reserved) | RRM Session |
R4-2508570 | (reserved) | RRM Session |
R4-2508571 | (reserved) | RRM Session |
R4-2508572 | (reserved) | RRM Session |
R4-2508573 | (reserved) | RRM Session |
R4-2508574 | (reserved) | RRM Session |
R4-2508575 | (reserved) | RRM Session |
R4-2508576 | (reserved) | RRM Session |
R4-2508577 | (reserved) | RRM Session |
R4-2508578 | (reserved) | RRM Session |
R4-2508579 | (reserved) | RRM Session |
R4-2508580 | (reserved) | RRM Session |
R4-2508581 | (reserved) | RRM Session |
R4-2508582 | (reserved) | RRM Session |
R4-2508583 | (reserved) | RRM Session |
R4-2508584 | (reserved) | RRM Session |
R4-2508585 | (reserved) | RRM Session |
R4-2508586 | (reserved) | RRM Session |
R4-2508587 | (reserved) | RRM Session |
R4-2508588 | (reserved) | RRM Session |
R4-2508589 | (reserved) | RRM Session |
R4-2508590 | (reserved) | RRM Session |
R4-2508591 | (reserved) | RRM Session |
R4-2508592 | (reserved) | RRM Session |
R4-2508593 | (reserved) | RRM Session |
R4-2508594 | (reserved) | RRM Session |
R4-2508595 | (reserved) | RRM Session |
R4-2508596 | (reserved) | RRM Session |
R4-2508597 | (reserved) | RRM Session |
R4-2508598 | (reserved) | RRM Session |
R4-2508599 | (reserved) | RRM Session |
R4-2508600 | (reserved) | RRM Session |
R4-2508601 | (reserved) | RRM Session |
R4-2508602 | (reserved) | RRM Session |
R4-2508603 | (reserved) | RRM Session |
R4-2508604 | (reserved) | RRM Session |
R4-2508605 | (reserved) | RRM Session |
R4-2508606 | (reserved) | RRM Session |
R4-2508607 | (reserved) | BDaT Session |
R4-2508608 | (reserved) | BDaT Session |
R4-2508609 | (reserved) | BDaT Session |
R4-2508610 | (reserved) | BDaT Session |
R4-2508611 | (reserved) | BDaT Session |
R4-2508612 | (reserved) | BDaT Session |
R4-2508613 | (reserved) | BDaT Session |
R4-2508614 | (reserved) | BDaT Session |
R4-2508615 | (reserved) | BDaT Session |
R4-2508616 | (reserved) | BDaT Session |
R4-2508617 | (reserved) | BDaT Session |
R4-2508618 | (reserved) | BDaT Session |
R4-2508619 | (reserved) | BDaT Session |
R4-2508620 | (reserved) | BDaT Session |
R4-2508621 | (reserved) | BDaT Session |
R4-2508622 | (reserved) | BDaT Session |
R4-2508623 | (reserved) | BDaT Session |
R4-2508624 | (reserved) | BDaT Session |
R4-2508625 | (reserved) | BDaT Session |
R4-2508626 | (reserved) | BDaT Session |
R4-2508627 | (reserved) | BDaT Session |
R4-2508628 | (reserved) | BDaT Session |
R4-2508629 | (reserved) | BDaT Session |
R4-2508630 | (reserved) | BDaT Session |
R4-2508631 | (reserved) | BDaT Session |
R4-2508632 | (reserved) | BDaT Session |
R4-2508633 | (reserved) | BDaT Session |
R4-2508634 | (reserved) | BDaT Session |
R4-2508635 | (reserved) | BDaT Session |
R4-2508636 | (reserved) | BDaT Session |
R4-2508637 | (reserved) | BDaT Session |
R4-2508638 | (reserved) | BDaT Session |
R4-2508639 | (reserved) | BDaT Session |
R4-2508640 | (reserved) | BDaT Session |
R4-2508641 | (reserved) | BDaT Session |
R4-2508642 | (reserved) | BDaT Session |
R4-2508643 | (reserved) | BDaT Session |
R4-2508644 | (reserved) | BDaT Session |
R4-2508645 | (reserved) | BDaT Session |
R4-2508646 | (reserved) | BDaT Session |
R4-2508647 | (reserved) | BDaT Session |
R4-2508648 | (reserved) | BDaT Session |
R4-2508649 | (reserved) | BDaT Session |
R4-2508650 | (reserved) | BDaT Session |
R4-2508651 | (reserved) | BDaT Session |
R4-2508652 | (reserved) | BDaT Session |
R4-2508653 | (reserved) | BDaT Session |
R4-2508654 | (reserved) | BDaT Session |
R4-2508655 | (reserved) | BDaT Session |
R4-2508656 | (reserved) | BDaT Session |
R4-2508657 | (reserved) | BDaT Session |
R4-2508658 | (reserved) | BDaT Session |
R4-2508659 | (reserved) | BDaT Session |
R4-2508660 | (reserved) | BDaT Session |
R4-2508661 | (reserved) | BDaT Session |
R4-2508662 | (reserved) | BDaT Session |
R4-2508663 | (reserved) | BDaT Session |
R4-2508664 | (reserved) | BDaT Session |
R4-2508665 | (reserved) | BDaT Session |
R4-2508666 | (reserved) | BDaT Session |
R4-2508667 | (reserved) | BDaT Session |
R4-2508668 | (reserved) | BDaT Session |
R4-2508669 | (reserved) | BDaT Session |
R4-2508670 | (reserved) | BDaT Session |
R4-2508671 | (reserved) | BDaT Session |
R4-2508672 | (reserved) | BDaT Session |
R4-2508673 | (reserved) | BDaT Session |
R4-2508674 | (reserved) | BDaT Session |
R4-2508675 | (reserved) | BDaT Session |
R4-2508676 | (reserved) | BDaT Session |
R4-2508677 | (reserved) | BDaT Session |
R4-2508678 | (reserved) | BDaT Session |
R4-2508679 | (reserved) | BDaT Session |
R4-2508680 | (reserved) | BDaT Session |
R4-2508681 | (reserved) | BDaT Session |
R4-2508682 | (reserved) | BDaT Session |
R4-2508683 | (reserved) | BDaT Session |
R4-2508684 | (reserved) | BDaT Session |
R4-2508685 | (reserved) | BDaT Session |
R4-2508686 | (reserved) | BDaT Session |
R4-2508687 | (reserved) | BDaT Session |
R4-2508688 | (reserved) | BDaT Session |
R4-2508689 | (reserved) | BDaT Session |
R4-2508690 | (reserved) | BDaT Session |
R4-2508691 | (reserved) | BDaT Session |
R4-2508692 | (reserved) | BDaT Session |
R4-2508693 | (reserved) | BDaT Session |
R4-2508694 | (reserved) | BDaT Session |
R4-2508695 | (reserved) | BDaT Session |
R4-2508696 | (reserved) | BDaT Session |
R4-2508697 | (reserved) | BDaT Session |
R4-2508698 | (reserved) | BDaT Session |
R4-2508699 | (reserved) | BDaT Session |
R4-2508700 | (reserved) | BDaT Session |
R4-2508701 | (reserved) | BDaT Session |
R4-2508702 | (reserved) | BDaT Session |
R4-2508703 | (reserved) | BDaT Session |
R4-2508704 | (reserved) | BDaT Session |
R4-2508705 | (reserved) | BDaT Session |
R4-2508706 | (reserved) | BDaT Session |
R4-2508707 | (reserved) | BDaT Session |
R4-2508708 | (reserved) | BDaT Session |
R4-2508709 | (reserved) | BDaT Session |
R4-2508710 | (reserved) | BDaT Session |
R4-2508711 | (reserved) | BDaT Session |
R4-2508712 | (reserved) | BDaT Session |
R4-2508713 | (reserved) | BDaT Session |
R4-2508714 | (reserved) | BDaT Session |
R4-2508715 | (reserved) | BDaT Session |
R4-2508716 | (reserved) | BDaT Session |
R4-2508717 | (reserved) | BDaT Session |
R4-2508718 | (reserved) | BDaT Session |
R4-2508719 | (reserved) | BDaT Session |
R4-2508720 | (reserved) | BDaT Session |
R4-2508721 | (reserved) | BDaT Session |
R4-2508722 | (reserved) | BDaT Session |
R4-2508723 | (reserved) | BDaT Session |
R4-2508724 | (reserved) | BDaT Session |
R4-2508725 | (reserved) | BDaT Session |
R4-2508726 | (reserved) | BDaT Session |
R4-2508727 | (reserved) | BDaT Session |
R4-2508728 | (reserved) | BDaT Session |
R4-2508729 | (reserved) | BDaT Session |
R4-2508730 | (reserved) | BDaT Session |
R4-2508731 | (reserved) | BDaT Session |
R4-2508732 | (reserved) | BDaT Session |
R4-2508733 | (reserved) | BDaT Session |
R4-2508734 | (reserved) | BDaT Session |
R4-2508735 | (reserved) | BDaT Session |
R4-2508736 | (reserved) | BDaT Session |
R4-2508737 | (reserved) | BDaT Session |
R4-2508738 | (reserved) | BDaT Session |
R4-2508739 | (reserved) | BDaT Session |
R4-2508740 | (reserved) | BDaT Session |
R4-2508741 | (reserved) | BDaT Session |
R4-2508742 | (reserved) | BDaT Session |
R4-2508743 | (reserved) | BDaT Session |
R4-2508744 | (reserved) | BDaT Session |
R4-2508745 | (reserved) | BDaT Session |
R4-2508746 | (reserved) | BDaT Session |
R4-2508747 | (reserved) | BDaT Session |
R4-2508748 | (reserved) | BDaT Session |
R4-2508749 | (reserved) | BDaT Session |
R4-2508750 | (reserved) | BDaT Session |
R4-2508751 | (reserved) | BDaT Session |
R4-2508752 | (reserved) | BDaT Session |
R4-2508753 | (reserved) | BDaT Session |
R4-2508754 | (reserved) | BDaT Session |
R4-2508755 | (reserved) | BDaT Session |
R4-2508756 | (reserved) | BDaT Session |
R4-2508757 | (reserved) | BDaT Session |
R4-2508758 | (reserved) | BDaT Session |
R4-2508759 | (reserved) | BDaT Session |
R4-2508760 | (reserved) | BDaT Session |
R4-2508761 | (reserved) | BDaT Session |
R4-2508762 | (reserved) | BDaT Session |
R4-2508763 | (reserved) | BDaT Session |
R4-2508764 | (reserved) | BDaT Session |
R4-2508765 | (reserved) | BDaT Session |
R4-2508766 | (reserved) | BDaT Session |
R4-2508767 | (reserved) | BDaT Session |
R4-2508768 | (reserved) | BDaT Session |
R4-2508769 | (reserved) | BDaT Session |
R4-2508770 | (reserved) | BDaT Session |
R4-2508771 | (reserved) | BDaT Session |
R4-2508772 | (reserved) | BDaT Session |
R4-2508773 | (reserved) | BDaT Session |
R4-2508774 | (reserved) | BDaT Session |
R4-2508775 | (reserved) | BDaT Session |
R4-2508776 | (reserved) | BDaT Session |
R4-2508777 | (reserved) | BDaT Session |
R4-2508778 | (reserved) | BDaT Session |
R4-2508779 | (reserved) | BDaT Session |
R4-2508780 | (reserved) | BDaT Session |
R4-2508781 | (reserved) | BDaT Session |
R4-2508782 | (reserved) | BDaT Session |
R4-2508783 | (reserved) | BDaT Session |
R4-2508784 | (reserved) | BDaT Session |
R4-2508785 | (reserved) | BDaT Session |
R4-2508786 | (reserved) | BDaT Session |
R4-2508787 | (reserved) | BDaT Session |
R4-2508788 | (reserved) | BDaT Session |
R4-2508789 | (reserved) | BDaT Session |
R4-2508790 | (reserved) | BDaT Session |
R4-2508791 | (reserved) | BDaT Session |
R4-2508792 | (reserved) | BDaT Session |
R4-2508793 | (reserved) | BDaT Session |
R4-2508794 | (reserved) | BDaT Session |
R4-2508795 | (reserved) | BDaT Session |
R4-2508796 | (reserved) | BDaT Session |
R4-2508797 | (reserved) | BDaT Session |
R4-2508798 | (reserved) | BDaT Session |
R4-2508799 | (reserved) | BDaT Session |
R4-2508800 | (reserved) | BDaT Session |
R4-2508801 | (reserved) | BDaT Session |
R4-2508802 | (reserved) | BDaT Session |
R4-2508803 | (reserved) | BDaT Session |
R4-2508804 | (reserved) | BDaT Session |
R4-2508805 | (reserved) | BDaT Session |
R4-2508806 | (reserved) | BDaT Session |
R4-2508807 | (reserved) | BDaT Session |
R4-2508808 | (reserved) | BDaT Session |
R4-2508809 | (reserved) | BDaT Session |
R4-2508810 | (reserved) | BDaT Session |
R4-2508811 | (reserved) | BDaT Session |
R4-2508812 | (reserved) | BDaT Session |
R4-2508813 | (reserved) | BDaT Session |
R4-2508814 | (reserved) | BDaT Session |
R4-2508815 | (reserved) | BDaT Session |
R4-2508816 | (reserved) | BDaT Session |
R4-2508817 | (reserved) | BDaT Session |
R4-2508818 | (reserved) | BDaT Session |
R4-2508819 | (reserved) | BDaT Session |
R4-2508820 | (reserved) | BDaT Session |
R4-2508821 | (reserved) | BDaT Session |
R4-2508822 | (reserved) | BDaT Session |
R4-2508823 | (reserved) | BDaT Session |
R4-2508824 | (reserved) | BDaT Session |
R4-2508825 | (reserved) | BDaT Session |
R4-2508826 | (reserved) | BDaT Session |
R4-2508827 | (reserved) | BDaT Session |
R4-2508828 | (reserved) | BDaT Session |
R4-2508829 | (reserved) | BDaT Session |
R4-2508830 | (reserved) | BDaT Session |
R4-2508831 | (reserved) | BDaT Session |
R4-2508832 | (reserved) | BDaT Session |
R4-2508833 | (reserved) | BDaT Session |
R4-2508834 | (reserved) | BDaT Session |
R4-2508835 | (reserved) | BDaT Session |
R4-2508836 | (reserved) | BDaT Session |
R4-2508837 | (reserved) | BDaT Session |
R4-2508838 | (reserved) | BDaT Session |
R4-2508839 | (reserved) | BDaT Session |
R4-2508840 | (reserved) | BDaT Session |
R4-2508841 | (reserved) | BDaT Session |
R4-2508842 | (reserved) | BDaT Session |
R4-2508843 | (reserved) | BDaT Session |
R4-2508844 | (reserved) | BDaT Session |
R4-2508845 | (reserved) | BDaT Session |
R4-2508846 | (reserved) | BDaT Session |
R4-2508847 | (reserved) | BDaT Session |
R4-2508848 | (reserved) | BDaT Session |
R4-2508849 | (reserved) | BDaT Session |
R4-2508850 | (reserved) | BDaT Session |
R4-2508851 | (reserved) | BDaT Session |
R4-2508852 | (reserved) | BDaT Session |
R4-2508853 | (reserved) | BDaT Session |
R4-2508854 | (reserved) | BDaT Session |
R4-2508855 | (reserved) | BDaT Session |
R4-2508856 | (reserved) | BDaT Session |
R4-2508857 | (reserved) | BDaT Session |
R4-2508858 | (reserved) | BDaT Session |
R4-2508859 | (reserved) | BDaT Session |
R4-2508860 | (reserved) | BDaT Session |
R4-2508861 | (reserved) | BDaT Session |
R4-2508862 | (reserved) | BDaT Session |
R4-2508863 | (reserved) | BDaT Session |
R4-2508864 | (reserved) | BDaT Session |
R4-2508865 | (reserved) | BDaT Session |
R4-2508866 | (reserved) | BDaT Session |
R4-2508867 | (reserved) | BDaT Session |
R4-2508868 | (reserved) | BDaT Session |
R4-2508869 | (reserved) | BDaT Session |
R4-2508870 | (reserved) | BDaT Session |
R4-2508871 | (reserved) | BDaT Session |
R4-2508872 | (reserved) | BDaT Session |
R4-2508873 | (reserved) | BDaT Session |
R4-2508874 | (reserved) | BDaT Session |
R4-2508875 | (reserved) | BDaT Session |
R4-2508876 | (reserved) | BDaT Session |
R4-2508877 | (reserved) | BDaT Session |
R4-2508878 | (reserved) | BDaT Session |
R4-2508879 | (reserved) | BDaT Session |
R4-2508880 | (reserved) | BDaT Session |
R4-2508881 | (reserved) | BDaT Session |
R4-2508882 | (reserved) | BDaT Session |
R4-2508883 | (reserved) | BDaT Session |
R4-2508884 | (reserved) | BDaT Session |
R4-2508885 | (reserved) | BDaT Session |
R4-2508886 | (reserved) | BDaT Session |
R4-2508887 | (reserved) | BDaT Session |
R4-2508888 | (reserved) | BDaT Session |
R4-2508889 | (reserved) | BDaT Session |
R4-2508890 | (reserved) | BDaT Session |
R4-2508891 | (reserved) | BDaT Session |
R4-2508892 | (reserved) | BDaT Session |
R4-2508893 | (reserved) | BDaT Session |
R4-2508894 | (reserved) | BDaT Session |
R4-2508895 | (reserved) | BDaT Session |
R4-2508896 | (reserved) | BDaT Session |
R4-2508897 | (reserved) | BDaT Session |
R4-2508898 | (reserved) | BDaT Session |
R4-2508899 | (reserved) | BDaT Session |
R4-2508900 | (reserved) | BDaT Session |
R4-2508901 | (reserved) | BDaT Session |
R4-2508902 | (reserved) | BDaT Session |
R4-2508903 | (reserved) | BDaT Session |
R4-2508904 | (reserved) | BDaT Session |
R4-2508905 | (reserved) | BDaT Session |
R4-2508906 | (reserved) | BDaT Session |