TDoc | Title | Source |
---|---|---|
R4-2414900 | RAN4#112 Meeting Report | ETSI MCC |
R4-2414901 | Agenda for RAN4#112-bis | RAN4 Chair (Huawei) |
R4-2414902 | RAN4#112-bis Meeting Arrangements and Guidelines | RAN4 Chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R4-2414903 | LS on Rel-18 RAN1 UE features list for NR after RAN1#118 | RAN1 |
R4-2414904 | LS on updated Rel-18 RAN1 UE features list for LTE after RAN1#118 | RAN1 |
R4-2414905 | Reply LS on synchronization source change at the transmitting anchor UE in SL positioning | RAN1 |
R4-2414906 | LS on FR2-NTN inclusion to specifications | RAN1 |
R4-2414907 | Reply LS on UL Tx switching | RAN1 |
R4-2414908 | Reply LS to RAN2 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | RAN1 |
R4-2414909 | LS on LP-WUS operation in IDLE/INACTIVE mode | RAN1 |
R4-2414910 | LS on gaps/restrictions that are caused by RRM measurements | RAN1 |
R4-2414911 | LS on timeline for On-demand SSB operation on SCell | RAN1 |
R4-2414912 | Reply LS on UE capability for multi-carrier enhancements | RAN2 |
R4-2414913 | LS on LTM L1 intra and inter-frequency measurements capabilities | RAN2 |
R4-2414914 | LS on common TA in a regenerative payload scenario | RAN2 |
R4-2414915 | Reply LS on Rel-18 higher-layers parameter list | RAN2 |
R4-2414916 | Reply LS on FR2 UE Beamlock test function | RAN5 |
R4-2414917 | Transmitter spurious emissions: co-existence requirements limits for high frequency bands | ETSI MSG TFES |
R4-2414918 | LS to 3GPP on LTE TRP/TRS test method for UE over 72mm wide | ETSI MSG TFES |
R4-2415446 | Request for HIBS band plan information | APT Wireless Group |
R4-2417352 | Reply LS on L3 measurement based LTM support over F1 | RAN3 |
TDoc | Title | Source |
---|---|---|
R4-2415205 | Topic summary for [112bis][101] R18_UERF_maintenance_Part2 | Moderator(Huawei) |
R4-2415648 | Topic summary for [112bis][201] TEI_R18 | Moderator (Apple) |
R4-2415649 | Topic summary for [112bis][202] NR_pos_enh2_Part1 | Moderator (Ericsson) |
R4-2415650 | Topic summary for [112bis][203] NR_pos_enh2_Part2 | Moderator (CATT) |
R4-2416522 | Topic summary for [112bis][301] BSRF_Maintenance_R18_TEI | Moderator (Ericsson) |
R4-2416538 | Topic summary for [112bis][317] Demod_Maintenance_R18_TEI | Moderator (Nokia) |
R4-2416543 | Topic summary for [112bis][322] NR_FR1_TRP_TRS_enh_Maint | Moderator (vivo) |
R4-2416869 | WF on RRM requirements for NR_pos_enh2_Part1 | Ericsson |
R4-2416870 | WF on RRM requirements for NR_pos_enh2_Part2 | CATT |
R4-2416871 | Ad-hoc minutes for NR_pos_enh2 | Ericsson |
R4-2417183 | WF on FR2 power class 8 | Huawei, HiSilicon |
R4-2417184 | WF for NTN NB-IoT inband operation | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415162 | Draft CR on core requirements for SL positioning | CATT |
R4-2415163 | Draft CR on core requirements for CPP | CATT |
R4-2415166 | Discussion on Core requirements of SL Pos and CPP | CATT |
R4-2415847 | Discussion on core requirements for SL positioning and CPP | Huawei, HiSilicon |
R4-2415848 | draftCR on RRM requirements for SL positioning | Huawei, HiSilicon |
R4-2415849 | draftCR on RRM requirements for CPP | Huawei, HiSilicon |
R4-2416198 | Draft CR 38133 on remaining core issues for SL positioning | Ericsson |
R4-2416318 | draftCR to 38.133 on corrections to core requirements for CPP | Ericsson |
R4-2416884 | Draft Big CR to 38133 for RRM core part for expanded and improved NR positioning | Ericsson |
R4-2416888 | Draft CR on core requirements for SL positioning | CATT |
R4-2416889 | Draft CR 38133 on remaining core issues for SL positioning | Ericsson |
R4-2416890 | draftCR on RRM requirements for CPP | Huawei, HiSilicon |
R4-2416891 | draftCR to 38.133 on corrections to core requirements for CPP | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415160 | Draft CR on core requirements for RedCap positioning | CATT |
R4-2415161 | Draft CR on core requirements for SRS BW aggregation | CATT |
R4-2415165 | Discussion on Core requirements of RedCap and BW aggregation Pos | CATT |
R4-2415850 | Discussion on core requirements for RedCap positioning and PRS/SRS BWA | Huawei, HiSilicon |
R4-2415851 | draftCR on requirements for RedCap positioning | Huawei, HiSilicon |
R4-2415852 | draftCR on requirements for PRS BWA | Huawei, HiSilicon |
R4-2415925 | On RRM core maintenance for RedCap positioning and PRS/SRS bandwidth aggregation | Qualcomm Incorporated |
R4-2416319 | On core requirements for RedCap positioning and BW aggregation for positioning measurements | Ericsson |
R4-2416320 | draftCR to 38.133 on interruption requirement for SRS aggregation for positioning | Ericsson |
R4-2416321 | draftCR to 38.133 on corrections to core requirements for RedCap positioning | Ericsson |
R4-2416444 | RRM Core Requirements for RedCap Positioning | Nokia |
R4-2416885 | draftCR on requirements for RedCap positioning | Huawei, HiSilicon |
R4-2416886 | Draft CR on core requirements for SRS BW aggregation | CATT |
R4-2416887 | draftCR on requirements for PRS BWA | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415853 | draftCR on PRS RMC | Huawei, HiSilicon |
R4-2416201 | Updated draft Big CR to 38133 for RRM performance part for expanded and improved NR positioning | Ericsson |
R4-2416881 | Ad-hoc minutes #2 for NR_pos_enh2 WI | Ericsson |
R4-2416882 | Ad-hoc minutes #3 for NR_pos_enh2 WI | Ericsson |
R4-2416892 | draft Big CR to 38133 for RRM performance part for expanded and improved NR positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415164 | Draft CR on SL-PRS configuration for TCs | CATT |
R4-2415168 | Discussion on Performance requirements of SL positioning | CATT |
R4-2415854 | Discussion on performance requirements for SL positioning | Huawei, HiSilicon |
R4-2415855 | draftCR on accuracy requirements for SL positioning | Huawei, HiSilicon |
R4-2415926 | On performance requirements for SL positioning | Qualcomm Incorporated |
R4-2416199 | On remaining performance issues for SL positioning | Ericsson |
R4-2416200 | Draft CR 38133 on remaining performance issues for SL positioning | Ericsson |
R4-2416897 | Draft CR on SL-PRS configuration for TCs | CATT |
R4-2416898 | Draft CR 38133 on remaining performance issues for SL positioning | Ericsson |
R4-2416905 | Updated summary of simulation results for SL positioning accuracy requirements | CATT |
TDoc | Title | Source |
---|---|---|
R4-2415856 | draftCR on performance requirements for LPHAP | Huawei, HiSilicon |
R4-2416322 | draftCR to 38.133 on test cases for LPHAP | Ericsson |
R4-2416901 | draftCR on performance requirements for LPHAP | Huawei, HiSilicon |
R4-2416902 | draftCR to 38.133 on test cases for LPHAP | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415167 | Discussion on Performance requirements of RedCap UE positioning | CATT |
R4-2415857 | Discussion on performance requirements for RedCap positioning | Huawei, HiSilicon |
R4-2415858 | draftCR on performance requirements for RedCap positioning | Huawei, HiSilicon |
R4-2415927 | On performance requirements for RedCap positioning | Qualcomm Incorporated |
R4-2416323 | On performace requirement for RedCap positioning | Ericsson |
R4-2416324 | draftCR to 38.133 on performance requirements for RedCap positioning | Ericsson |
R4-2416325 | Updated summary of simulation results for RedCap positioning | Ericsson |
R4-2416445 | RRM Performance Requirements for RedCap Positioning | Nokia |
R4-2416446 | Simulation Results for RedCap Positioning without Frequency Hopping | Nokia |
R4-2416893 | draftCR on performance requirements for RedCap positioning | Huawei, HiSilicon |
R4-2416894 | draftCR to 38.133 on performance requirements for RedCap positioning | Ericsson |
R4-2416903 | Updated summary of simulation results for RedCap positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415859 | draftCR on performance requirements for PRS BWA | Huawei, HiSilicon |
R4-2415928 | On performance requirements for PRS bandwidth aggregation | Qualcomm Incorporated |
R4-2416326 | draftCR to 38.133 on accuracy requirement and test cases for BW aggregation for positioning measurements | Ericsson |
R4-2416327 | On performance requirement for bandwidth aggregation for positioning measurements | Ericsson |
R4-2416328 | Updated summary of simulation results for PRS aggregation | Ericsson |
R4-2416434 | Simulation results for PRS Bandwidth Aggregation | Nokia |
R4-2416895 | draftCR on performance requirements for PRS BWA | Huawei, HiSilicon |
R4-2416896 | draftCR to 38.133 on accuracy requirement and test cases for BW aggregation for positioning measurements | Ericsson |
R4-2416904 | Updated summary of simulation results for PRS aggregation | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415605 | Corrections on test cases for CPP | CATT |
R4-2415860 | Discussion on performance requirements for CPP | Huawei, HiSilicon |
R4-2415861 | draftCR on performance requirements for CPP | Huawei, HiSilicon |
R4-2416329 | draftCR to 38.133 on performance requirement for CPP | Ericsson |
R4-2416435 | RRM performance requirements for NR Carrier Phase Positioning | Nokia |
R4-2416436 | CR 38.133 Introduction of TCs on CPP measurement accuracy | Nokia |
R4-2416437 | Simulation results for DL RSCPD and DL RSCP | Nokia |
R4-2416505 | On the Need for Additional Scenarios for CPP | Lenovo |
R4-2416899 | Corrections on test cases for CPP | CATT |
R4-2416900 | draftCR to 38.133 on performance requirement for CPP | Ericsson |
R4-2416906 | Updated summary of simulation results for CPP accuracy requirements | CATT |
TDoc | Title | Source |
---|---|---|
R4-2415771 | draft CR to TR 38.870 on spectrum analyzer configurations | vivo |
R4-2415772 | draft CR to TR 38.870 on editorial update | vivo |
R4-2415773 | Discussions on spectrum analyzer for wideband TRP measurement | vivo |
TDoc | Title | Source |
---|---|---|
R4-2415565 | Draft CR to TS 38.161 on introduction of PC3 talk mode TRP requirements for TDD bands | Samsung, vivo, Apple |
R4-2415774 | draft CR to TS 38.161 on editorial corrections | vivo |
TDoc | Title | Source |
---|---|---|
R4-2415439 | NR A-MPR reevaluation scenarios on n1 for Japan | KDDI, NTT Docomo |
R4-2415461 | On inband deployment of NTN NB-IoT in NR carrier | Ericsson |
R4-2415628 | Discussion on introduction of new FR2 PC8 | Huawei,HiSilicon |
R4-2415629 | Updated system simulation assumption for introduction of FR2 PC8 | Huawei,HiSilicon |
R4-2415630 | CR on introduction of RF requirements for FR2 power class 8 [FR2_PC8] | Huawei, HiSilicon |
R4-2415631 | CR on introduction of RRM requirements for FR2 power class 8 [FR2_PC8] | Huawei, HiSilicon |
R4-2415632 | (TEI18) CR on release independence for FR2 PC8 in TS 38.307 [FR2_PC8] | Huawei,HiSilicon |
R4-2415643 | Draft LS on introduction of FR2 UE Power Class 8 | Huawei,HiSilicon |
R4-2415714 | Reconsidering the proposed new FR2 power class 8 | Ericsson |
R4-2415727 | On the proposed FR2 PC8 (new power class) UE | Qualcomm Incorporated |
R4-2415807 | (TEI18) Draft CR to TS 36.102 addressing incomplete Rel-18 requirements in clause 6.2B.3 | Mediatek India Technology Pvt. |
R4-2415826 | (TEI18) Draft CR to TS 36.102 on variable TX-RX frequency separation | MediaTek Inc., EchoStar, Dish Network |
R4-2416099 | (TEI18) Corrections on inter-band uplink CA configurations for two bands | ZTE Corporation, Sanechips |
R4-2416100 | (TEI18) Corrections on inter-band uplink CA configurations for three bands | ZTE Corporation, Sanechips |
R4-2416101 | (TEI18) Corrections on inter-band uplink CA configurations for more than three bands | ZTE Corporation, Sanechips |
R4-2416102 | (TEI18) Corrections on intra-band contiguous CA configurations for CA_n258 | ZTE Corporation, Sanechips |
R4-2416114 | (TEI18) Draft CR to 36.102 In-band NB-IoT NTN deployment with NR [LTE_NBIoT_eMTC_NTN_req-Core] | Mediatek India Technology Pvt. |
TDoc | Title | Source |
---|---|---|
R4-2416390 | Correction on Conditional handover including target MCG in FR1 and target SCG in FR1 in NR-DC | ZTE Corporation, Sanechips |
R4-2416443 | (NR_Mob_enh2-Core) Correction on Conditional handover including target MCG in FR1 and target SCG in FR1 in NR-DC | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415637 | (NR_ENDC_RF_FR1_enh2-Perf) draftCR updates to the requirements applicability for 8Rx | Huawei,HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415206 | Topic summary for [112bis][102] NR_Baskets_Part_1 | Moderator(Nokia) |
R4-2415207 | Topic summary for [112bis][103] NR_Baskets_Part_2 | Moderator(Ericsson) |
R4-2415208 | Topic summary for [112bis][104] LTE_Baskets | Moderator(Huawei) |
R4-2415209 | Topic summary for [112bis][105] HPUE_NR_band | Moderator(CMCC) |
R4-2415210 | Topic summary for [112bis][106] LTE_NR_HPUE_FWVM | Moderator(Nokia) |
R4-2415211 | Topic summary for [112bis][107] HPUE_Basket_EN-DC | Moderator(China Unicom) |
R4-2415212 | Topic summary for [112bis][108] HPUE_Basket_Intra-CA_TDD | Moderator(China Telecom) |
R4-2415213 | Topic summary for [112bis][109] LTE_NR_Other_basket | Moderator(Huawei) |
R4-2415214 | Topic summary for [112bis][110] NR_LTE_TN_Bands | Moderator(Nokia) |
R4-2415215 | Topic summary for [112bis][111] NR_IoT_NTN_Bands | Moderator(Inmarsat) |
R4-2415216 | Topic summary for [112bis][112] NR_n28_PC2_40MHz | Moderator(CMCC) |
R4-2415217 | Topic summary for [112bis][113] NR_mmWave_protect | Moderator(China Unicom) |
R4-2416537 | Topic summary for [112bis][316] HAPS_operating_bands | Moderator (Softbank) |
R4-2417057 | WF on notes for downlink interruption clarification | China Telecom |
R4-2417058 | WF on simultaneous Tx-Rx for CA_n40A-n41A | Huawei |
R4-2417080 | WF on A-MPR for n68 | Ericsson |
R4-2417081 | WF on NTN and IoT-NTN bands | Inmarsat |
R4-2417082 | WF on PC2 and 40MHz CBW for n28 | CMCC |
R4-2417083 | WF on UE RF requirements for EESS protection | Huawei |
R4-2417084 | WF on BS RF requirements for EESS protection | China Unicom, Huawei, HiSilicon, ZTE, CATT |
R4-2417125 | WF for UL_CA_n5-n8 | CATT |
R4-2417156 | WF on DC_(n)8AA MSD and MSD test point clean-up | Skyworks Solutions Inc. |
R4-2417176 | WF on NTN and IoT-NTN bands | Inmarsat |
R4-2417181 | WF on MSD requriemenets with intra-band contiguous UL CA_n40A-n41C and CA_n41C-n79A | Huawei |
R4-2417198 | WF on low band consideration for AAS | Huawei |
R4-2417206 | WF on NTN and IoT-NTN bands | Inmarsat |
TDoc | Title | Source |
---|---|---|
R4-2414954 | Draft TR 37.719-11-10_v0.1.0 | Samsung |
R4-2415388 | Big draftCR for DC_R19_xBLTE_yBNR (OBJ-3 DC_R19_xBLTE_yBNR_zDLqUL) | Nokia |
R4-2415827 | TR37.719-21-11 v0.2.0 for DC_R19_xBLTE_yBNR_3DL2UL | LG Electronics Deutschland |
R4-2415828 | Draft BigCR for DC_R19_xBLTE_yBNR (OBJ-2 DC_R19_xBLTE_yBNR_3DL2UL) | LG Electronics Deutschland |
R4-2416007 | TR 37.719-11-11 v0.2.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-2416010 | draft BigCR for DC_R19_xBLTE_yBNR (OBJ-1 DC_R19_1BLTE_1BNR_2DL2UL) | CHTTL |
R4-2417177 | Big draft CR for DC_R19_xBLTE_yBNR | Nokia, LGE, CHTTL, Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415398 | Draft CR 38.101-3 to add DC_(n)40AA | Nokia, nbn |
R4-2415728 | MSD for DC_(n)8AA | Murata Manufacturing Co Ltd. |
R4-2416228 | DC_(n)8AA MSD and MSD test point clean-up | Skyworks Solutions Inc. |
R4-2416425 | draft CR 38.101-3 adding DC_n77(3A)-n260A/G/H/I/J/K/L/M | Ericsson, US Cellular |
R4-2417155 | Draft CR 38.101-3 to add DC_(n)40AA | Nokia, nbn |
TDoc | Title | Source |
---|---|---|
R4-2414966 | TP for TR 37.719-21-11 to add DC_2A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2414967 | TP for TR 37.719-21-11 to add DC_66A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2414968 | TP for TR 37.719-21-11 to add DC_5A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2414969 | TP for TR 37.719-21-11 to add DC_2A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2414970 | TP for TR 37.719-21-11 to add DC_66A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2414971 | TP for TR 37.719-21-11 to add DC_5A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2415959 | draft CR for EN-DC DC_1-3-3_n8, DC_1-7-7_n8 | CHTTL |
R4-2416031 | TP for TR 37.719-21-11 on introduction of DC_1A-41A_n1A and DC_1A-41C_n1A | Huawei, HiSilicon |
R4-2416032 | TP for TR 37.719-21-11 on introduction of DC_1A_n1A-n78A | Huawei, HiSilicon |
R4-2416033 | Draft CR for TS 38.101-3 to introduce DC_1A-3A-3A_n1A | Huawei, HiSilicon |
R4-2416357 | (DC_R19_xBLTE_yBNR_3DL2UL) draftCR to 38.101-3 to include EN-DC band combination | Huawei, HiSilicon |
R4-2417157 | TP for TR 37.719-21-11 to add DC_2A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2417158 | TP for TR 37.719-21-11 to add DC_66A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2417159 | TP for TR 37.719-21-11 to add DC_5A_n41A-n78A | Huawei, HiSilicon,Rogers |
R4-2417160 | TP for TR 37.719-21-11 to add DC_2A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2417161 | TP for TR 37.719-21-11 to add DC_66A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2417162 | TP for TR 37.719-21-11 to add DC_5A_n41A-n77A | Huawei, HiSilicon,Rogers |
R4-2417163 | TP for TR 37.719-21-11 on introduction of DC_1A_n1A-n78A | Huawei, HiSilicon |
R4-2417164 | Draft CR for TS 38.101-3 to introduce DC_1A-3A-3A_n1A | Huawei, HiSilicon |
R4-2417165 | (DC_R19_xBLTE_yBNR_3DL2UL) draftCR to 38.101-3 to include EN-DC band combination | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414965 | draft CR for TS 38101-3 to add combos of x LTE and y NR inter-band EN-DC | Huawei, HiSilicon,Rogers |
R4-2415995 | draft CR for EN-DC DC_1-3-3-7_n8-n78 related combos | CHTTL |
R4-2416034 | Draft CR for TS 38.101-3 to introduce DC_1A-3A-3A-41C_n1A-n78A and ENDC fallbacks | Huawei, HiSilicon |
R4-2416358 | (DC_R19_xBLTE_yBNR_zDLqUL) draftCR to 38.101-3 to include EN-DC band combination | Huawei, HiSilicon |
R4-2417166 | draft CR for TS 38101-3 to add combos of x LTE and y NR inter-band EN-DC | Huawei, HiSilicon,Rogers |
R4-2417167 | Draft CR for TS 38.101-3 to introduce DC_1A-3A-3A-41C_n1A-n78A and ENDC fallbacks | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2416035 | Draft CR for TS 38.101-3 to introduce DC_1A_SUL_n78C-n84A and DC_1A_SUL_n78C-n80A | Huawei, HiSilicon, China Telecom, China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2415808 | TS 38.101-1 big draftCR for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
R4-2415809 | TS 38.101-2 big draftCR for NR_CADC_R19_2BDL_xBUL | ZTE Corporation, Sanechips |
R4-2415921 | TR38.719-02-01 v0.2.0: Rel-19 NR inter-band CA/DC configurations including inter band CA for 2 different bands DL with up to 2 different bands UL | ZTE Corporation |
R4-2415922 | TS 38.101-3 draft big CR for NR_CADC_R19_2BDL_xBUL | ZTE Corporation |
R4-2416027 | Draft Big CR on Introduction of completed SUL band combinations into TS 38.101-1 | Huawei, HiSilicon |
R4-2416028 | TR for 38.719-00-00 v0.2.0 | Huawei, HiSilicon |
R4-2416096 | TR 38.719-03-01 v0.2.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-2416097 | Draft big CR to reflect the completed NR inter-band CA DC combinations for 3 bands DL with up to 2 bands UL into TS 38.101-1 | ZTE Corporation |
R4-2416098 | Draft big CR to reflect the completed NR inter-band CA DC combinations for 3 bands DL with up to 2 bands UL into TS 38.101-3 | ZTE Corporation |
R4-2416217 | draft big CR 38.101-1 new combinations Rel-19 NR inter-band CADC configurations for yDL with xUL | Ericsson |
R4-2416218 | draft big CR 38.101-3 new combinations Rel-19 NR inter-band CADC configurations for yDL with xUL | Ericsson |
R4-2416418 | Corrections in WID NR_CADC_SUL_R19 | Ericsson |
R4-2416419 | big CR 38.101-1 new combinations Rel-19 NR Intra-band | Ericsson |
R4-2416420 | big CR 38.101-2 new combinations Rel-19 NR Intra-band | Ericsson |
R4-2416421 | TR 38.719-01-01 v0.2.0 NR_CA_R19_Intra | Ericsson |
R4-2417178 | Draft big CR for NR_CADC_SUL_R19 | Ericsson, ZTE, Huawei, HiSilicon |
R4-2417179 | Draft big CR for NR_CADC_SUL_R19 | Ericsson, ZTE, Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2416259 | On NR-U non-contiguous UL-CA | Skyworks Solutions Inc. |
R4-2416424 | draft CR 38.101-1 correcting Note in intra-band MSD table | Ericsson, Skyworks |
R4-2416430 | draft CR 38.101-1 adding BCS4 and 5 and UL CA_n78C to DL CA_n78(A-C) | Ericsson, Telstra |
TDoc | Title | Source |
---|---|---|
R4-2414988 | Draft CR for TS 38.101-1 to add BCS4 and 5 for PC3 inter-band CA | Samsung, TELUS, Bell Mobility |
R4-2414989 | TP for TR 38.719-02-01 CA_n7-n29 | Samsung, TELUS, Bell Mobility |
R4-2414990 | TP for TR 38.719-02-01 CA_n29-n77 | Samsung, TELUS, Bell Mobility |
R4-2415103 | Discussion on how to handle the RF requirements for 2U/2D CA_n5-n8 | CATT |
R4-2415355 | Draft CR for TS 38.101-1 to add BCS4 and 5 for PC3 two-band inter-band CA | SoftBank Corp. |
R4-2415394 | Draft CR 38.101-1 to add CA FR1 combinations of n1, n7, n28, n77 with BCS4 & 5 | Nokia, BT plc |
R4-2415401 | TP to TR 38.719-02-01 CA_n20-n41 | Nokia, Mobily |
R4-2415402 | TP to TR 38.719-02-01 CA_n20-n71 | Nokia, Mobily |
R4-2415416 | Draft CR 38.101-1 to add new CA FR1 combinations of n3 | Nokia, Etisalat |
R4-2415417 | TP to TR 38.719-02-01 CA_n41-n78 w ULCA | Nokia, Etisalat |
R4-2415418 | TP to TR 38.719-02-01 CA_n71-n78 | Nokia, Etisalat |
R4-2415877 | Draft CR to 38.101-1: UE RF requirements for uplink CA_n5-n8 | China Telecom |
R4-2415919 | TP for TR38.719-02-01_CA_n41A-n104A | ZTE Corporation, Sanechips |
R4-2416012 | On MSD requirements with intra-band contiguous UL CA | ZTE Corporation, Sanechips |
R4-2416029 | Discussion on MSD for CA_n40A-n41C with intra-band UL CA_n41C | Huawei, HiSilicon |
R4-2416030 | Discussion on MSD for CA_n41C-n79A with intra-band UL CA_n41C | Huawei, HiSilicon |
R4-2416038 | Draft LS on enabling RRC configuration UL CA_n5-n8 with DL CA_n5-n8 | Huawei, HiSilicon |
R4-2416039 | Discussion on UL CA_n5-n8 | Huawei, HiSilicon |
R4-2416115 | CA_n40A-n41C and CA_n41C-n79A MSD due to n41C UL | Skyworks Solutions Inc. |
R4-2416431 | draft CR 38.101-3 adding missing UL fallbacks for NR CA 2 bands | Ericsson, Telstra |
R4-2417124 | TP for TR 38.719-02-01 CA_n29-n77 | Samsung, TELUS, Bell Mobility |
R4-2417126 | Draft CR 38.101-1 to add CA FR1 combinations of n1, n7, n28, n77 with BCS4 & 5 | Nokia, BT plc |
R4-2417127 | TP to TR 38.719-02-01 CA_n20-n41 | Nokia, Mobily |
R4-2417128 | TP to TR 38.719-02-01 CA_n20-n71 | Nokia, Mobily |
R4-2417129 | Draft CR 38.101-1 to add new CA FR1 combinations of n3 | Nokia, Etisalat |
R4-2417130 | TP to TR 38.719-02-01 CA_n71-n78 | Nokia, Etisalat |
R4-2417131 | TP for TR38.719-02-01_CA_n41A-n104A | ZTE Corporation, Sanechips |
R4-2417180 | CA_n40A-n41C and CA_n41C-n79A MSD due to n41C UL | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2414961 | TP for TR 38.719-03-01 CA_n25-n29-n77 | Samsung, TELUS, Bell mobility |
R4-2414962 | Draft CR for TS 38.101-1 to add BCS4 and 5 for 3-band PC3 inter-band CA | Samsung, TELUS, Bell mobility |
R4-2414972 | TP for TR 38.719-03-01 to add CA_n1A-n75A-n78A | Huawei, HiSilicon, DT |
R4-2414973 | TP for TR 38.719-03-01 to add CA_n1A-n3A-n75A | Huawei, HiSilicon, DT |
R4-2414974 | TP for TR 38.719-03-01 to add CA_n1A-n7A-n78A | Huawei, HiSilicon, DT |
R4-2414991 | TP for TR 38.719-03-01 CA_n7-n25-n29 | Samsung, TELUS, Bell Mobility |
R4-2414992 | TP for TR 38.719-03-01 CA_n7-n29-n66 | Samsung, TELUS, Bell Mobility |
R4-2414993 | TP for TR 38.719-03-01 CA_n7-n29-n77 | Samsung, TELUS, Bell mobility |
R4-2415393 | Corrections of TR 38.719-03-01 | Nokia |
R4-2415395 | Draft CR 38.101-1 to add CA FR1 combinations of n1, n3, n7, n28, n78 with BCS4 & 5 | Nokia, BT plc |
R4-2415396 | TP to TR 38.719-03-01 CA_n3-n7-n77 | Nokia, BT plc |
R4-2415397 | Draft CR 38.101-3 to add new CA and DC FR1+FR2 combinations of n25, n41 and n258 | Nokia, T-Mobile USA |
R4-2415400 | TP to TR 38.719-03-01 CA_n1-n28-n40 | Nokia, STC |
R4-2415403 | TP to TR 38.719-03-01 CA_n1-n20-n41 | Nokia, Mobily |
R4-2415404 | TP to TR 38.719-03-01 CA_n1-n20-n71 | Nokia, Mobily |
R4-2415405 | TP to TR 38.719-03-01 CA_n1-n20-n77 | Nokia, Mobily |
R4-2415406 | TP to TR 38.719-03-01 CA_n1-n20-n78 | Nokia, Mobily |
R4-2415407 | TP to TR 38.719-03-01 CA_n1-n71-n77 | Nokia, Mobily |
R4-2415408 | TP to TR 38.719-03-01 CA_n20-n41-n71 | Nokia, Mobily |
R4-2415409 | TP to TR 38.719-03-01 CA_n20-n41-n77 | Nokia, Mobily |
R4-2415410 | TP to TR 38.719-03-01 CA_n20-n41-n78 | Nokia, Mobily |
R4-2415411 | TP to TR 38.719-03-01 CA_n20-n71-n78 | Nokia, Mobily |
R4-2415412 | TP to TR 38.719-03-01 CA_n3-n20-n41 | Nokia, Mobily |
R4-2415413 | TP to TR 38.719-03-01 CA_n3-n20-n71 | Nokia, Mobily |
R4-2415414 | TP to TR 38.719-03-01 CA_n3-n20-n77 | Nokia, Mobily |
R4-2415415 | TP to TR 38.719-03-01 CA_n3-n71-n77 | Nokia, Mobily |
R4-2415419 | TP to TR 38.719-03-01 CA_n1-n3-n71 | Nokia, Etisalat |
R4-2415420 | TP to TR 38.719-03-01 CA_n1-n3-n8 | Nokia, Etisalat |
R4-2415421 | TP to TR 38.719-03-01 CA_n1-n41-n71 | Nokia, Etisalat |
R4-2415422 | TP to TR 38.719-03-01 CA_n1-n41-n78 w ULCA | Nokia, Etisalat |
R4-2415423 | TP to TR 38.719-03-01 CA_n1-n71-n78 w ULCA | Nokia, Etisalat |
R4-2415424 | TP to TR 38.719-03-01 CA_n1-n8-n41 | Nokia, Etisalat |
R4-2415425 | TP to TR 38.719-03-01 CA_n1-n8-n78 w ULCA | Nokia, Etisalat |
R4-2415426 | TP to TR 38.719-03-01 CA_n3-n41-n71 | Nokia, Etisalat |
R4-2415427 | TP to TR 38.719-03-01 CA_n3-n41-n78 w ULCA | Nokia, Etisalat |
R4-2415428 | TP to TR 38.719-03-01 CA_n3-n71-n78 w ULCA | Nokia, Etisalat |
R4-2415429 | TP to TR 38.719-03-01 CA_n3-n8-n78 w ULCA | Nokia, Etisalat |
R4-2415430 | TP to TR 38.719-03-01 CA_n41-n71-n78 w ULCA | Nokia, Etisalat |
R4-2415431 | TP to TR 38.719-03-01 CA_n8-n41-n78 w ULCA | Nokia, Etisalat |
R4-2415432 | TP to TR 38.719-03-01 Uplink additions of CA_n1A-n3A-n78C | Nokia, Etisalat |
R4-2415920 | TP for TR38.719-03-01_3DL_xUL CA_n3A-n40A-n79A | ZTE Corporation, Sanechips |
R4-2416103 | Draft CR for TS 38.101-3 to introduce new BC for CA_n28-n39-n258, CA_n28-n40-n258 and CA_n28-n41-n258 | ZTE Corporation, Sanechips |
R4-2416219 | TP for 38.719-03-01 to add CA_n1A-n7A-n20A | Ericsson, BT plc |
R4-2416423 | correction draft CR 38.101-1 to remove 40 MHz channel BW from n28 in CA_n7A-n28A-n40A | Ericsson |
R4-2417132 | TP for TR 38.719-03-01 to add CA_n1A-n3A-n75A | Huawei, HiSilicon, DT |
R4-2417133 | TP for TR 38.719-03-01 to add CA_n1A-n7A-n78A | Huawei, HiSilicon, DT |
R4-2417134 | TP for TR 38.719-03-01 CA_n7-n25-n29 | Samsung, TELUS, Bell Mobility |
R4-2417135 | TP for TR 38.719-03-01 CA_n7-n29-n66 | Samsung, TELUS, Bell Mobility |
R4-2417136 | TP for TR 38.719-03-01 CA_n7-n29-n77 | Samsung, TELUS, Bell mobility |
R4-2417137 | Corrections of TR 38.719-03-01 | Nokia |
R4-2417138 | TP to TR 38.719-03-01 CA_n3-n7-n77 | Nokia, BT plc |
R4-2417139 | Draft CR 38.101-3 to add new CA and DC FR1+FR2 combinations of n25, n41 and n258 | Nokia, T-Mobile USA |
R4-2417140 | TP to TR 38.719-03-01 CA_n1-n20-n41 | Nokia, Mobily |
R4-2417141 | TP to TR 38.719-03-01 CA_n1-n20-n77 | Nokia, Mobily |
R4-2417142 | TP to TR 38.719-03-01 CA_n1-n71-n77 | Nokia, Mobily |
R4-2417143 | TP to TR 38.719-03-01 CA_n3-n20-n41 | Nokia, Mobily |
R4-2417144 | TP to TR 38.719-03-01 CA_n3-n71-n77 | Nokia, Mobily |
R4-2417145 | TP to TR 38.719-03-01 CA_n1-n41-n78 w ULCA | Nokia, Etisalat |
R4-2417146 | TP to TR 38.719-03-01 CA_n1-n71-n78 w ULCA | Nokia, Etisalat |
R4-2417147 | TP to TR 38.719-03-01 CA_n1-n8-n78 w ULCA | Nokia, Etisalat |
R4-2417148 | TP to TR 38.719-03-01 CA_n3-n41-n78 w ULCA | Nokia, Etisalat |
R4-2417149 | TP to TR 38.719-03-01 CA_n3-n71-n78 w ULCA | Nokia, Etisalat |
R4-2417150 | TP to TR 38.719-03-01 CA_n3-n8-n78 w ULCA | Nokia, Etisalat |
R4-2417151 | TP to TR 38.719-03-01 CA_n41-n71-n78 w ULCA | Nokia, Etisalat |
R4-2417152 | TP to TR 38.719-03-01 CA_n8-n41-n78 w ULCA | Nokia, Etisalat |
R4-2417153 | TP to TR 38.719-03-01 Uplink additions of CA_n1A-n3A-n78C | Nokia, Etisalat |
R4-2417154 | TP for TR38.719-03-01_3DL_xUL CA_n3A-n40A-n79A | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2414975 | draft CR for TS 38101-1 to add CA_n8A-n20A-n28A-n75A etc | Huawei, HiSilicon, DT |
TDoc | Title | Source |
---|---|---|
R4-2416036 | Draft CR for TS 38.101-1 to introduce BCS4&5 for CA_n41C-n81A CA_n41C-n97A and CA_n79C-n97A | Huawei, HiSilicon, CMCC |
R4-2416037 | Draft CR for TS 38.101-1 to introduce BCS4&5 for SUL_n78A-n84A CA_n78C-n84A and SUL_n3A-n84A | Huawei, HiSilicon, China Telecom, China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2416337 | Draft Big CR on Introduction of completed R19 x(x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 | Huawei, HiSilicon |
R4-2416340 | TR 36.719-01-01 LTE-A CA for x DL y UL | Huawei, HiSilicon |
R4-2416341 | Revised WID Rel-19 LTE-A CA for x(x=123456) DL y(y=2) UL | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415357 | TP to TR 36.719-01-01 Addition of ULCA_8-11 to CA_8-11 | SoftBank Corp. |
R4-2415958 | draft CR for LTE CA_1-3-3-7-7-8 related combo | CHTTL |
R4-2416220 | TP for 36.719-01-01 to add CA_1A-68A | Ericsson |
R4-2416221 | TP for 36.719-01-01 to add CA_3A-68A | Ericsson |
R4-2416222 | TP for 36.719-01-01 to add CA_7A-68A | Ericsson |
R4-2416223 | TP for 36.719-01-01 to add CA_8A-68A | Ericsson |
R4-2416224 | TP for 36.719-01-01 to add CA_20A-68A | Ericsson |
R4-2416225 | TP for 36.719-01-01 to add CA_40A-68A | Ericsson |
R4-2417168 | TP to TR 36.719-01-01 Addition of ULCA_8-11 to CA_8-11 | SoftBank Corp. |
R4-2417169 | draft CR for LTE CA_1-3-3-7-7-8 related combo | CHTTL |
R4-2417170 | TP for 36.719-01-01 to add CA_1A-68A | Ericsson |
R4-2417171 | TP for 36.719-01-01 to add CA_3A-68A | Ericsson |
R4-2417172 | TP for 36.719-01-01 to add CA_7A-68A | Ericsson |
R4-2417173 | TP for 36.719-01-01 to add CA_8A-68A | Ericsson |
R4-2417174 | TP for 36.719-01-01 to add CA_20A-68A | Ericsson |
R4-2417175 | TP for 36.719-01-01 to add CA_40A-68A | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415258 | TR 38.796 v0.2.0 HPUE_NR_FR1_bands_R19-FDD | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2415026 | TP for TR 38.795 to introduce n104 PC1.5 | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2415715 | On the A-MPR for PC2 operation in n26 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415365 | TR 36.767 V0.0.2 | Nokia |
R4-2415366 | Big draftCR for Rel-19 High power UE (power class 2) and high power operation (power class 1) for fixed-wireless/vehicle-mounted use cases in a single LTE band | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415259 | TR 37.898 v0.2.0 HPUE_DC_LTE_NR_R19 | China Unicom |
R4-2415260 | Draft Big CR on Rel-19 HPUE for DC combinations of LTE band(s) and NR band(s) | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2415356 | Draft CR for 38.101-3 to add missing values for MSD due to harmonic mixing in PC2 DC_3A_n77A and DC_3A_n78A | SK Telecom |
R4-2415399 | TP to TR 38.898 Addition of PC2 for DC_(n)40AA | Nokia, nbn |
R4-2415793 | TP for TR 37.898 to add of PC2 for DC_4A_n41A | vivo |
R4-2415794 | TP for TR 37.898 to add of PC2 for DC_4A_n78A | vivo |
R4-2415795 | TP for TR 37.898 to add of PC2 for DC_7C_n78A | vivo |
R4-2415796 | TP for TR 37.898 to add of PC2 for DC_8A_n41A | vivo |
R4-2415797 | TP for TR 37.898 to add of PC2 for DC_20A_n41A | vivo |
R4-2415798 | TP for TR 37.898 to add of PC2 for DC_20A_n78A | vivo |
R4-2415799 | TP for TR 37.898 to add of PC2 for DC_38A_n78A | vivo |
R4-2415800 | TP for TR 37.898 to add of PC2 for DC_41A_n78A and DC_41C_n78A | vivo |
R4-2417054 | Draft CR for 38.101-3 to add missing values for MSD due to harmonic mixing in PC2 DC_3A_n77A and DC_3A_n78A | SK Telecom |
R4-2417055 | TP for TR 37.898 to add of PC2 for DC_8A_n41A | vivo |
R4-2417056 | TP for TR 37.898 to add of PC2 for DC_41A_n78A and DC_41C_n78A | vivo |
TDoc | Title | Source |
---|---|---|
R4-2414977 | Revised WID for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
R4-2414978 | DraftBig CR to 38.101-1 new combinations for HPUE_NR_CADC_SUL_R19 | China Telecom, China Unicom |
R4-2414979 | TR for High power UE (power class 1.5 or 2) for NR Inter-band Carrier Aggregation (CA)/Dual Connectivity (DC) with/without Supplementary Uplink (SUL) with high power on TDD band(s) | China Telecom |
R4-2415261 | TR 38.750 v0.2.0 HPUE_NR_CADC_SUL_R19-FDD | China Unicom |
TDoc | Title | Source |
---|---|---|
R4-2415916 | draft CR to TS 38.101-1 Introduction of PC2 CA_n79C with UL MIMO | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415299 | DraftCR 38.101-1 Addition of Single UL PC1.5 CA Combinations | AT&T |
R4-2415354 | Draft CR for TS38.101-1 Rel-19 for adding some HP-NRCA band combinations | SoftBank Corp. |
R4-2415936 | TP for TR38.746: 3Tx inter-band CA_n1-n77, CA_n3-n77 and CA_n28-n77 | SoftBank Corp. |
R4-2416426 | TP 38.746 for HPUE PC2 dual UL CA_n1-n26-n78 | Ericsson, Telstra |
R4-2416427 | TP 38.746 for HPUE PC2 dual UL CA_n3-n26-n78 | Ericsson, Telstra |
R4-2416428 | TP 38.746 3Tx inter-band CA_n26-n78 | Ericsson, Telstra |
R4-2416429 | draft CR 38.101-1 to add and correct HPUE notes from the RAN4 111 | Ericsson, Telstra |
TDoc | Title | Source |
---|---|---|
R4-2414987 | TR38.792 for PC1.5 with high power on both FDD and TDD bands | OPPO |
R4-2415917 | TP for TR 38.746 Annex part: Valid UL configuration | ZTE Corporation, Sanechips, CHTTL, Samsung |
R4-2415918 | TP for TR 38.746 Correct the template for Maximum output power | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415923 | TS 38.101-1 draft big CR to include 4Rx | ZTE Corporation |
R4-2415924 | TS 38.101-1 draft big CR to include 8Rx | ZTE Corporation |
R4-2416176 | TS 38.101-1 draft big CR for NR_bands_xFeature_R19 for UL-MIMO part | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414980 | (NR_bands_xFeature_R19-Core) Draft CR for 38.101-1 to introduce n3 support 8Rx | China Telecom, Huawei, HiSilicon |
R4-2415012 | Draft CR on 38.101-1 to introduce n39 support 8Rx | CMCC, ZTE Corporation |
R4-2416011 | draft CR for 38.101-1 introduction on 8Rx support for n1 | CHTTL, ZTE, Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415874 | TR 37.887 0.0.2 Rel-19 downlink interruption for NR and EN-DC band combinations at dynamic Tx Switching in Uplink | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2415323 | On DL interruption for Tx switching across 4 bands | Apple |
R4-2415875 | TP to 37.887: General description for DL interruption analysis for dynamic Tx switching | China Telecom |
R4-2415876 | Discussion on the note for DL interruption clarification for 3 or 4 bands | China Telecom |
TDoc | Title | Source |
---|---|---|
R4-2415027 | Discussion on simultaneous Rx/Tx for CA_n40-n41 | CMCC |
R4-2415328 | On simultaneous Rx/Tx for CA_n40A-n41A | Apple |
R4-2415359 | Further discussion on simultaneous Rx-Tx of CA_n40-n41 | Murata Manufacturing Co Ltd. |
R4-2416262 | CA_n40-n41 Simultaneous RxTx | Skyworks Solutions Inc. |
R4-2416359 | drafCR to 38.101-1: On Rel-19 simultaneous Rx-Tx | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415525 | Simulation results for NS_27 | Apple |
R4-2415531 | n48 wider BWs and NS_27 values | Qualcomm Incorporated |
R4-2415532 | n48 wider BWs and NS_27 values: AMPR proposal | Qualcomm Incorporated |
R4-2416041 | Draft CR for TS 38.101-1 to introduce larger channel bandwidth for SUL band n84 | Huawei, HiSilicon |
R4-2416042 | Draft CR for TS 38.101-1 to introduce larger channel bandwidth for SUL band n80 | Huawei, HiSilicon |
R4-2416043 | Draft CR for TS 38.104 to introduce larger channel bandwidth for SUL band n84 | Huawei, HiSilicon |
R4-2416044 | Draft CR for TS 38.104 to introduce larger channel bandwidth for SUL band n80 | Huawei, HiSilicon |
R4-2416214 | n48 NS_27 A-MPR simulations beyond 40 MHz CBW | Nokia |
R4-2416227 | Requirements for 40MHz CBW in Band n28 | Skyworks Solutions Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415115 | draft CR to TS38.307: Introduction of NR band n110 | CATT |
R4-2415279 | draft CR to 38.101-1 on introduction of Band n110 | Nokia |
R4-2417059 | draft CR to 38.101-1 on introduction of Band n110 | Nokia |
R4-2417197 | draft CR to TS38.307: Introduction of NR band n110 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2414941 | draftCR to 36.104 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2414942 | draftCR to 36.141 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2414943 | draftCR to 38.104 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2415951 | (NR_FDD_1400MHz-Core) Draft CR to TS38.101-5: Introduction of NR band n110 | ZTE Corporation, Sanechips |
R4-2415952 | (NR_FDD_1400MHz-Core) Draft CR to TS37.105: Introduction of NR band n110 | ZTE Corporation, Sanechips |
R4-2416155 | Draft CR to 37.145-2 - Introduction of band 1.4 GHz n110 | Ericsson |
R4-2416156 | Draft CR to 37.145-1 - Introduction of band 1.4 GHz n110 | Ericsson |
R4-2416303 | Draft CR to 38.106 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2416304 | Draft CR to 38.115-1 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2416305 | Draft CR to 38.174 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2416306 | Draft CR to 38.176-1 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2416307 | Draft CR to 38.176-2 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2416406 | Draft CR to TS 37.104: n110 band introduction | Huawei, HiSilicon |
R4-2416407 | Draft CR to TS 37.141: n110 band introduction | Huawei, HiSilicon |
R4-2416408 | Draft CR to TS 38.141-1: n110 band introduction | Huawei, HiSilicon |
R4-2416409 | Draft CR to TS 38.141-2: n110 band introduction | Huawei, HiSilicon |
R4-2416410 | Clarification on the NB-IoT requirements applicability for n110 | Huawei, HiSilicon |
R4-2417060 | draftCR to 38.104 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2417061 | draftCR to 36.104 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2417062 | draftCR to 36.141 on introduction of Band n110 | Nokia, MidWave Wireless |
R4-2417063 | Draft CR to 37.145-2 - Introduction of band 1.4 GHz n110 | Ericsson |
R4-2417064 | Draft CR to 37.145-1 - Introduction of band 1.4 GHz n110 | Ericsson |
R4-2417065 | Draft CR to TS 37.104: n110 band introduction | Huawei, HiSilicon |
R4-2417066 | Draft CR to TS 37.141: n110 band introduction | Huawei, HiSilicon |
R4-2417067 | Draft CR to TS 38.141-1: n110 band introduction | Huawei, HiSilicon |
R4-2417068 | Draft CR to TS 38.141-2: n110 band introduction | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2416388 | draft CR to TS 38.133: Introduction of the 1.4GHz band | ZTE Corporation, Sanechips |
R4-2417186 | draft CR to TS 38.133: Introduction of the 1.4GHz band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415286 | draft CR to 36.101 on introduction of Band 111 | NOVAMINT |
R4-2415289 | draft CR to 36.307 on introduction of Band 111 | NOVAMINT |
R4-2415440 | LTE 1800 UL emissions on DL | Nokia, Nokia Shanghai Bell |
R4-2415566 | LTE 1800 UL emissions on DL | Nokia |
R4-2416261 | UE Co-existence and REFSENS for B111 | Qualcomm France |
R4-2417069 | draft CR to 36.101 on introduction of Band 111 | NOVAMINT |
TDoc | Title | Source |
---|---|---|
R4-2415287 | draft CR to 36.104 on introduction of Band 111 | NOVAMINT |
R4-2415290 | draft CR to 37.104 on introduction of Band 111 | NOVAMINT |
R4-2415291 | draft CR to 37.104 on introduction of Band 111 | NOVAMINT |
R4-2415292 | draft CR to 37.105 on introduction of Band 111 | NOVAMINT |
R4-2415293 | draft CR to 38.104 on introduction of Band 111 | NOVAMINT |
R4-2415294 | draft CR to 38.106 on introduction of Band 111 | NOVAMINT |
R4-2417070 | draft CR to 37.104 on introduction of Band 111 | NOVAMINT |
R4-2417071 | draft CR to 37.105 on introduction of Band 111 | NOVAMINT |
TDoc | Title | Source |
---|---|---|
R4-2416150 | Bands n87-n88 - Regulatory aspects | Ericsson |
R4-2416518 | Initial analysis of the NB-IoT requirements for n87 and n88 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415113 | UE RF requirements for new NR bands n87 and n88 | CATT |
R4-2415114 | draft CR to TS 38.101-1 on introduction NR bands n87 and n88 | CATT |
R4-2416401 | Draft CR to TS 38.307: n87 and n88 overlapping bands introduction | Huawei, HiSilicon |
R4-2416405 | Draft CR to TS 38.101-5: n87 and n88 bands introduction | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414933 | draftCR to 36.141 on introduction of Band n87 and n88 | Nokia |
R4-2414934 | draftCR to 37.104 on introduction of Band n87 and n88 | Nokia |
R4-2414935 | draftCR to 37.141 on introduction of Band n87 and n88 | Nokia |
R4-2414936 | draftCR to 38.104 on introduction of Band n87 and n88 | Nokia |
R4-2415295 | draft CR to 38.174 on introduction of Band 111 | NOVAMINT |
R4-2415941 | (NR_bands_n87_n88-Core) Draft CR to TS38.106: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2415942 | (NR_bands_n87_n88-Perf) Draft CR to TS38.176-1: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2415943 | (NR_bands_n87_n88-Perf) Draft CR to TS38.176-2: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2415944 | (NR_bands_n87_n88-Perf) Draft CR to TS38.115-1: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2415945 | (NR_bands_n87_n88-Core) Draft CR to TS38.174: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2416151 | Draft CR to 36.104 - Introduction of bands n87-n88 | Ericsson |
R4-2416152 | Draft CR to 38.141-1 - Introduction of bands n87-n88 | Ericsson |
R4-2416153 | Draft CR to 38.141-2 - Introduction of bands n87-n88 | Ericsson |
R4-2416402 | Draft CR to TS 37.105: n87 and n88 bands introduction | Huawei, HiSilicon |
R4-2416403 | Draft CR to TS 37.145-1: n87 and n88 bands introduction | Huawei, HiSilicon |
R4-2416404 | Draft CR to TS 37.145-2: n87 and n88 bands introduction | Huawei, HiSilicon |
R4-2417073 | (NR_bands_n87_n88-Core) Draft CR to TS38.106: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2417074 | (NR_bands_n87_n88-Perf) Draft CR to TS38.176-2: Introduction of NR bands n87 and n88 | ZTE Corporation, Sanechips |
R4-2417075 | Draft CR to 38.141-1 - Introduction of bands n87-n88 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415288 | draft CR to 36.133 on introduction of Band 111 | NOVAMINT |
R4-2416154 | Draft CR to 38.133 - Introduction of bands n87-n88 | Ericsson |
R4-2417072 | draft CR to 36.133 on introduction of Band 111 | NOVAMINT |
TDoc | Title | Source |
---|---|---|
R4-2415116 | CR to TS38.133: Introduction of NR band n68 | CATT |
R4-2415445 | n68 NS_26 and NS_36 A-MPR simulations | Nokia, Nokia Shanghai Bell |
R4-2415569 | n68 NS_26 and NS_36 A-MPR simulations | Nokia |
R4-2415975 | Introduction of NR band n68 | Nokia |
R4-2416145 | Band n68 - A-MPR simulation results | Ericsson |
R4-2416148 | Draft CR to 38.101-1 - Introduction of band n68 | Ericsson |
R4-2416149 | Draft CR to 38.101-5 - Introduction of band n68 | Ericsson |
R4-2417076 | Draft CR to 38.101-1 - Introduction of band n68 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414937 | draftCR to 36.141 on introduction of Band n68 | Nokia |
R4-2414938 | draftCR to 37.104 on introduction of Band n68 | Nokia |
R4-2414939 | draftCR to 37.141 on introduction of Band n68 | Nokia |
R4-2414940 | draftCR to 38.141-1 on introduction of Band n68 | Nokia |
R4-2415946 | (NR_band_n68-Core) Draft CR to TS38.106: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2415947 | (NR_band_n68-Perf) Draft CR to TS38.176-1: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2415948 | (NR_band_n68-Perf) Draft CR to TS38.176-2: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2415949 | (NR_band_n68-Perf) Draft CR to TS38.115-1: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2415950 | (NR_band_n68-Core) Draft CR to TS38.174: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2416146 | Draft CR to 36.104 - Introduction of band n68 | Ericsson |
R4-2416147 | Draft CR to 38.104 - Introduction of band n68 | Ericsson |
R4-2416397 | Draft CR to TS 37.105: n68 band introduction | Huawei, HiSilicon |
R4-2416398 | Draft CR to TS 37.145-1: n68 band introduction | Huawei, HiSilicon |
R4-2416399 | Draft CR to TS 37.145-2: n68 band introduction | Huawei, HiSilicon |
R4-2416400 | Draft CR to TS 38.141-2: n68 band introduction | Huawei, HiSilicon |
R4-2417077 | (NR_band_n68-Core) Draft CR to TS38.106: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2417078 | (NR_band_n68-Perf) Draft CR to TS38.115-1: Introduction of NR band n68 | ZTE Corporation, Sanechips |
R4-2417079 | Draft CR to TS 38.141-2: n68 band introduction | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2416475 | Discussion on UE-to-UE coexistence | Inmarsat, Viasat |
TDoc | Title | Source |
---|---|---|
R4-2415089 | Discussion on UE RF requirements for the NTN new S-band | CATT |
R4-2415300 | Methodology for n252 UE to UE coexistence evaluation | EchoStar, Dish Network, Terrestar, Thales |
R4-2415314 | Initial view on the UE power back-off while operating in 2000-2020 MHz UL range | Apple |
R4-2415810 | draftCR to TS38.101-5 Introduction of NR-NTN S band | ZTE Corporation, Sanechips |
R4-2415960 | Discussion on NTN-TN coexistence study for new NTN SBand | Mediatek India Technology Pvt. |
R4-2416051 | Discussion on the NTN S band definition | Huawei, HiSilicon |
R4-2416144 | New NTN S-band - UE RF requirements | Ericsson |
R4-2416459 | Co-existence considerations for the new S-band | Qualcomm Inc. |
R4-2416507 | NTN S-Band UE-UE coexistence with TN | T-Mobile USA Inc., AT&T, UScellular |
TDoc | Title | Source |
---|---|---|
R4-2415088 | Discussion on SAN RF requirements for the NTN new S-band | CATT |
R4-2415811 | draftCR to TS38.108 Introduction of NR-NTN S band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2416373 | Introduction of NR-NTN S-band | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415812 | draftCR to TS36.102 Introduction of IoT-NTN S band | ZTE Corporation, Sanechips |
R4-2416008 | Discussion on IoT-NTN B252 UE RF requirements | Mediatek India Technology Pvt. |
TDoc | Title | Source |
---|---|---|
R4-2415813 | draftCR to TS36.108 Introduction of IoT-NTN S band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2416375 | Introduction of IoT-NTN S-band | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2416050 | Discussion on the full NTN L band definition | Huawei, HiSilicon |
R4-2416473 | Input to UE RF requirements for NTN L-bands n253, n521, n250 | Inmarsat, Viasat |
TDoc | Title | Source |
---|---|---|
R4-2415814 | draftCR to TS38.108 Introduction of NR-NTN combined L-band | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2416374 | Introduction of NR-NTN L-band | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415898 | Further discussion on PC3 n28 40MHz | ZTE Corporation, Sanechips |
R4-2415981 | Channel locations for UE capable of 40 MHz in n28 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2414982 | R19 AMPR for n28 40MHz | OPPO |
R4-2414994 | UE RF requirements for n28 | CMCC |
R4-2415322 | On UE RF Requirements for n28 with 40MHz UL CBW | Apple |
R4-2415442 | n28 NS_17 and NS_18 A-MPR proposals | Nokia, Nokia Shanghai Bell |
R4-2415444 | n28 NS_17 and NS_18 A-MPR simulations | Nokia, Nokia Shanghai Bell |
R4-2415464 | On UE RF requirements for band n28 | Huawei, HiSilicon |
R4-2415567 | n28 NS_17 and NS_18 A-MPR proposals | Nokia |
R4-2415568 | n28 NS_17 and NS_18 A-MPR simulations | Nokia |
R4-2415802 | On PC2 and 40 MHz of n28 | vivo |
R4-2415899 | Further discussion on PC2 n28 40MHz | ZTE Corporation, Sanechips |
R4-2416458 | UE RF requirements for PC2 and 40 MHz | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415262 | Work plan for Rel-19 mmWave in NR: UE spurious emissions and EESS protection | China Unicom, Huawei, HiSilicon |
R4-2416354 | TR skeleton for Rel-19 EESS | Huawei, HiSilicon |
R4-2417199 | TR skeleton for Rel-19 EESS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415083 | Discussion on UE spurious emissions for UE in mmWave in NR | CATT |
R4-2415329 | Initial considerations on EESS protection requirements | Apple |
R4-2415375 | UE RF specification impact for MmWave UE spurious emission 2 kuvaa puuttu | Nokia |
R4-2415726 | 24 GHz EESS band phase 2 requirements and UE compliance | Qualcomm Incorporated |
R4-2415908 | On EESS mmWave UE spurious emission | ZTE Corporation, Sanechips |
R4-2416065 | UE RF specification impact for MmWave UE spurious emission | Nokia |
R4-2416161 | EESS protection - UE RF aspects | Ericsson |
R4-2416163 | Draft CR to TS 38101-2 - EESS protection - UE RF aspects | Ericsson |
R4-2416194 | Views on EESS protection for n257 | NTT DOCOMO INC. |
R4-2416353 | Discussion on Rel-19 EESS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415084 | Discussion on EESS (Earth Exploration Satellite Service) protection for BS in mmWave in NR | CATT |
R4-2415477 | BS RF specification impact for MmWave UE spurious emission | Nokia |
R4-2415909 | On EESS protection for BS | ZTE Corporation, Sanechips |
R4-2416160 | EESS protection - BS RF aspects | Ericsson |
R4-2416162 | Draft CR to TS 38104 - EESS protection - BS RF aspects | Ericsson |
R4-2417085 | Draft CR to TS 38104 - EESS protection - BS RF aspects | Ericsson, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415880 | Analysis on additional operating NR bands for HAPS (High Altitude Platform Station) | SoftBank Corp. |
R4-2416059 | Discussion on Rel-19 HAPS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415979 | UE RF requirement for HAPS | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415980 | Discussion on additional operating bands for HAPS | Nokia |
R4-2416316 | HAPS ACLR and ACS | Ericsson |
R4-2416317 | Draft CR to 38.104: Introduction of HAPS bands | Ericsson |
R4-2416558 | Draft CR to 38.104: Introduction of HAPS bands | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414948 | Views on SAR and MSD for HPUE TN | Samsung |
R4-2415054 | Discussion on General aspects for High power UE | Xiaomi |
R4-2415330 | On Rel-19 HPUE CA/DC SAR compliance consideration | Apple |
R4-2415367 | MSD requirement for new PC2/PC1.5 band combinations | Nokia |
R4-2415465 | Discussion on the general aspects for HPUE CA | Huawei, HiSilicon |
R4-2415784 | MSD rules and duty cycle related Issues for CA HPUE | vivo |
R4-2415885 | Duty cycle solutions of HPUE for inter-band UL CA and EN-DC | LG Electronics |
R4-2415904 | Discussion on R19 HPUE duty cycle and MSD rule | ZTE Corporation, Sanechips |
R4-2416018 | Discussion on SAR solutions & MSD rules for new Rel-19 HPUE scenarios | CHTTL |
R4-2416131 | Discussion on MSD rules for HPUE CA/DC | NTT DOCOMO, INC. |
R4-2416252 | HPUE CADC MSD Simplification | Skyworks Solutions Inc. |
R4-2416253 | Valid Uplink-CA Configurations | Skyworks Solutions Inc. |
R4-2416263 | MSD for HPUE | Qualcomm France |
TDoc | Title | Source |
---|---|---|
R4-2414984 | R19 MPR for PC1.5 contiguous CA and NCCA | OPPO |
R4-2415053 | Discussion on PC1.5 TDD intra-band CA | Xiaomi |
R4-2415264 | Views on SAR Solution | China Telecom |
R4-2415275 | On PC1.5 ULCA PCmax and UE behavior under large PSD imbalance | Skyworks Solutions Inc. |
R4-2415331 | On PSD imbalance for PC1.5 intra-band UL CA MPR evaluations | Apple |
R4-2415368 | PSD imbalance impact to MPR | Nokia |
R4-2415644 | Preliminary input on 2Tx PC1.5 contiguous ULCA MPR based on measurements | Skyworks Solutions Inc. |
R4-2415645 | Preliminary input on DualPA PC1.5 non-contiguous ULCA MPR based on measurements | Skyworks Solutions Inc. |
R4-2415712 | Study of PSD imbalance between the 2 CCs for intra-band ULCA | Qualcomm Technologies Int |
R4-2415716 | Configured maximum power and MPR requirements for intra-band UL CA with PC1.5 | Ericsson |
R4-2415742 | Further discussion on HPUE for intra-band contiguous and non-contiguous CA | vivo |
R4-2415905 | Further discussion on R19 PC1.5 Intra-band UL CA | ZTE Corporation, Sanechips |
R4-2416061 | HPUE for intra-band UL CA | LG Electronics Finland |
R4-2416270 | MPR evaluations for PC1.5 with TxD for intra-band contiguous CA with contiguous allocations | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415332 | On Rel-19 HPUE CA/DC MSD consideration | Apple |
R4-2415886 | HPUE for inter-band UL CA and EN-DC. | LG Electronics |
R4-2415906 | Further discussion on R19 2Tx/3Tx PC2/1.5 Inter-band NR CA/ENDC | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2414949 | Draft Rel-19 CR for 38.101-1 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia |
R4-2414950 | Draft Rel-19 CR for 38.101-3 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia |
R4-2415055 | Discussion on increasing high power limit for inter-band CA DC with 2Tx and or 3Tx | Xiaomi |
R4-2415717 | The higher power limit with PC1.5 band capability | Ericsson |
R4-2415725 | On capturing wider applicability of higherPowerLimit-r17 | Qualcomm Incorporated |
R4-2415785 | DraftCR on increasing transmission high power limit for CA HPUE | vivo |
R4-2415786 | DraftCR on increasing transmission high power limit for CA HPUE | vivo |
R4-2415907 | Further discussion on R19 Increasing UE transmission power limit | ZTE Corporation, Sanechips |
R4-2417096 | Draft Rel-19 CR for 38.101-1 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia |
R4-2417097 | Draft Rel-19 CR for 38.101-3 on increasing higher power limit with 2Tx or 3Tx | Samsung, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415035 | Discussion on MPR reduction for single carrier | OPPO |
R4-2415265 | Views on Power domain enhancements for single carrier | China Telecom |
R4-2415274 | Reduced MPR by redefining allocation type based on BS signalled transmission bandwidth | Skyworks Solutions Inc. |
R4-2415326 | On Rel-19 power domain enhancement for FR1 | Apple |
R4-2415369 | Power domain enhancements for single carrier | Nokia |
R4-2415528 | MPR Reduction for Single Carrier | Murata Manufacturing Co Ltd. |
R4-2415579 | Further views on MPR Reduction | Sony |
R4-2415711 | Power boosting and MPR reduction | Qualcomm Technologies Int |
R4-2415718 | Power domain enhancements for scenarios 1 and 2 | Ericsson |
R4-2415753 | Discussion on power domain enhancements for NR single carrier | vivo |
R4-2415815 | Discussion on power domain enhancements for single carrier | ZTE Corporation, Sanechips |
R4-2415961 | Discussion on power domain enhancement for NR single carrier | MediaTek (Shenzhen) Inc. |
R4-2416128 | Further discussion on power domain enhancements for single carrier | CATT |
R4-2416177 | On power domain enhancements for single carrier | Huawei, HiSilicon, China Unicom, Orange |
R4-2416226 | Discussion on BS indication for MPR reduction | NTT DOCOMO, INC. |
R4-2416519 | Discussion on Power domain enhancements for single carrier | LG Electronics UK |
TDoc | Title | Source |
---|---|---|
R4-2414953 | Draft Rel-19 CR on MPR applicability for intra-band contiguous CA with single CC with activated cell | Samsung |
R4-2415036 | Discussion on the applicable MPR for FR1 intra-band UL CA with single activated cell | OPPO |
R4-2415273 | Using single CC MPR and ULCA related emissions when only one CC has RBs allocated | Skyworks Solutions Inc. |
R4-2415370 | MPR applicability for FR1 intra-band UL CA | Nokia |
R4-2415526 | On Rel-19 UL CA power domain enhancement for FR1 | Apple |
R4-2415527 | ULCA Single CC MPR Applicability after SCELL deactivation | Murata Manufacturing Co Ltd. |
R4-2415713 | MPR applicability for FR1 intra-band UL CA | Qualcomm Technologies Int |
R4-2415719 | MPR applicability for non-contiguous and contiguous UL CA in FR1 | Ericsson |
R4-2415754 | Discussion on MPR applicability for FR1 intra-band UL CA | vivo |
R4-2415755 | draft CR to TS 38.101-1 on MPR applicability for FR1 intra-band UL CA | vivo |
R4-2415816 | Discussion on MPR applicability for FR1 intra-band UL CA | ZTE Corporation, Sanechips |
R4-2416129 | Further discussion on MPR applicability for FR1 intra-band UL CA | CATT |
R4-2416178 | On MPR applicability for FR1 intra-band UL CA | Huawei, HiSilicon |
R4-2416504 | Discussion on MPR applicability for FR1 intra-band UL CA | LG Electronics UK |
TDoc | Title | Source |
---|---|---|
R4-2415327 | On Rel-19 power domain enhancement for FR2 | Apple |
R4-2415557 | Discussion on MPR reduction for FR2 CA | Samsung |
R4-2415756 | Discussion on MPR applicability for FR2 | vivo |
R4-2415757 | draftCR to TS 38.101-2 on MPR applicability for FR2 | vivo |
R4-2415817 | Discussion on MPR applicability for FR2 | ZTE Corporation, Sanechips |
R4-2416179 | On MPR applicability for FR2 CA | Huawei, HiSilicon |
R4-2416215 | draft CR to TS 38.101-2 for FR2 configuration based MPR improvement | NTT DOCOMO, INC. |
R4-2416216 | Discussion on MPR improvement for FR2 CA | NTT DOCOMO, INC. |
R4-2417110 | draft CR to TS 38.101-2 for FR2 configuration based MPR improvement | NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R4-2415371 | Final remarks on 6Rx for handheld and FWA REFSENS | Nokia |
R4-2415640 | Disscussion on reference sensitivity requirements for 6RX UE | Spreadtrum Communications |
R4-2415743 | Further discussion on 6Rx REFSENS requirements for FWA and Handheld UE | vivo |
R4-2415900 | Further discussion on 6Rx requirements | ZTE Corporation, Sanechips |
R4-2415901 | Introduction of 6Rx (Rx part) | ZTE Corporation, Sanechips |
R4-2415990 | Draft CR for 38.101-1: Introduction of Rel-19 REFSENS requirement for 6Rx | Ericsson |
R4-2415996 | Discussion on REFSENS requirement for 6Rx UE | |
R4-2416133 | Discussion for 6 Rx REFSENS | LG Electronics France |
R4-2416180 | On 6Rx reference sensitivity requirements for FR1 UE | Huawei, HiSilicon |
R4-2416195 | Views on 6Rx for handheld UE and FWA UE. | NTT DOCOMO INC. |
R4-2417094 | Introduction of 6Rx (Rx part) | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2414985 | R19 Simulation results of 6Layer performance | OPPO |
R4-2415298 | Discussion on 6Rx Support of 6 MIMO Layers | Nokia |
R4-2415433 | Feasibility evaluation of MIMO layer for 6Rx UE | MediaTek inc. |
R4-2415547 | Views on Maximum Number of MIMO Layers for 6Rx UEs | Apple |
R4-2415647 | Discussion on the demodulation performance requirements for 6Rx devices | QUALCOMM Europe Inc. - Spain |
R4-2415681 | Discussion and simulation results on MIMO layer evaluation for 6Rx UE | Samsung |
R4-2415744 | Simulation results of MIMO layer evaluation for 6Rx UE | vivo |
R4-2415991 | Discussion on the support of MIMO layers for 6Rx UE | Ericsson |
R4-2415997 | Discussion on MIMO layer for 6Rx UE | |
R4-2416181 | On MIMO layer evaluation for 6Rx UE | Huawei, HiSilicon |
R4-2416342 | Discussion on MIMO layer evaluation for 6Rx UE | ZTE Corporation, Sanechips |
R4-2416508 | 6-Layer downlink MIMO for handheld UEs | T-Mobile USA Inc. |
TDoc | Title | Source |
---|---|---|
R4-2414981 | R19 6Rx SRS IL for n104 | OPPO |
R4-2415324 | On the values of Delta_TRxSRS for 6Rx SRS antenna switching | Apple |
R4-2415641 | Disscussion on SRS antenna switching requirements for 6RX UE | Spreadtrum Communications |
R4-2415745 | Further discussion on SRS antenna switching requirements | vivo |
R4-2415903 | Further discussion on 6Rx SRS antenna switching requirements | ZTE Corporation, Sanechips |
R4-2416005 | Discussion on SRS antenna switching requirements for 6Rx UE | |
R4-2416182 | On 6Rx SRS antenna switching requirements | Huawei, HiSilicon |
R4-2416193 | Discussion for 6 Rx ?TRxSRS | LG Electronics France |
R4-2416264 | 6Rx SRS antenna switching requirements | Qualcomm France |
R4-2416474 | On remaining DeltaT_RxSRS requirement for 6Rx UE RF | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415266 | Further study on SRS IL imbalance | China Telecom |
R4-2415280 | On the SRS imbalance issue for further discussion | Nokia |
R4-2415313 | On the SRS insertion loss imbalance reporting | Ericsson India Private Limited |
R4-2415325 | Views on 6Rx REFSENS evaluation and SRS IL Imbalance solution | Apple |
R4-2415434 | UE SRS IL imbalance issue for 6Rx UE | MediaTek inc. |
R4-2415642 | Disscussion on SRS IL imbalance for 6RX UE | Spreadtrum Communications |
R4-2415686 | Views on SRS insertion loss compensation and reporting enhancements | Intel Corporation |
R4-2415787 | Discussion on SRS IL imbalance reporting | vivo |
R4-2415902 | Further discussion on 6Rx SRS antenna IL imbalance | ZTE Corporation, Sanechips |
R4-2416003 | Views on SRS IL imbalance | Samsung |
R4-2416006 | Discussion on SRS IL imbalance for 6Rx UE | |
R4-2416183 | On SRS IL imbalance issue | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415247 | Discussion on RRM requirements for R19 UE RF enhancements for NR FR1/FR2 and EN-DC | CMCC |
R4-2415570 | RRM requirements for NR FR1/FR2 and EN-DC Phase 4 | Nokia, Nokia Shanghai Bell |
R4-2415843 | Discussion on UE RF enhancements for NR FR1/FR2 and EN-DC, Phase 4 | Huawei, HiSilicon |
R4-2416361 | Discussions on RRM impact of Rel-19 WI on UE RF enhancements WI | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415218 | Topic summary for [112bis][114] NR_ENDC_RF_Ph4_part1 | Moderator(Huawei) |
R4-2415219 | Topic summary for [112bis][115] NR_ENDC_RF_Ph4_part2 | Moderator(Samsung) |
R4-2415220 | Topic summary for [112bis][116] NR_ENDC_RF_Ph4_part3 | Moderator(AT&T) |
R4-2415651 | Topic summary for [112bis][204] NR_ENDC_RF_Ph4 | Moderator (Huawei) |
R4-2416848 | WF on RRM requirements for NR_ENDC_RF_Ph4 | Huawei |
R4-2417095 | WF on 6Rx UE RF requirements | AT&T |
R4-2417098 | WF on HPUE RF requirements | Samsung |
R4-2417111 | WF on power enhancement for UE | Huawei |
R4-2417204 | WF on power enhancement for UE | Huawei |
R4-2417209 | WF on 6Rx UE RF requirements | AT&T |
TDoc | Title | Source |
---|---|---|
R4-2415044 | Add a section in TR 38.922 on frequency use case in the IMT-2030 bands | Korea Testing Laboratory |
R4-2415048 | TP for 38.922 on frequency use case for 4400 – 4800 MHz, 7125 – 8400 MHz and 14800 – 15350 MHz | Korea Testing Laboratory |
R4-2415343 | Add a section in TR 38.922 on frequency allocation in the IMT-2030 bands | CableLabs |
R4-2415344 | TP for TR 38.922 on frequency allocation in USA for 4400 – 4800 MHz, 7125 – 8400 MHz, and 14800 – 15350 MHz | CableLabs |
R4-2415969 | TP to TR 38.922: Addition of new subclause for adjacent channel array antenna modelling aspects in subclause 7.2 | Ericsson |
R4-2415982 | IMT parameters: General system and UE aspects | Nokia |
R4-2416415 | TP to TR 38.922: Scope clarification | Huawei, HiSilicon |
R4-2417100 | TP to TR 38.922: Scope clarification | Huawei, HiSilicon |
R4-2417190 | TP to TR 38.922: Scope clarification | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415117 | TP to TR 38.922: Corrections on Section 4 for 4400 - 4800 MHz frequency range | CATT |
R4-2415478 | TP to TR 38.922: Corrections and clarifications on IMT parameters for 4400 to 4800 MHz frequency range | Nokia |
R4-2416173 | TP to TR 38.922 Update Clause 1 - 5 | Ericsson |
R4-2416413 | TP to TR 38.922: clean-up for 4400 to 4800 MHz frequency range section | Huawei, HiSilicon |
R4-2417102 | TP to TR 38.922 Update Clause 1 - 5 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415118 | TP to TR 38.922: Corrections on Section 5.2 for BS IMT parameters for 7125 to 8400 MHz frequency range | CATT |
R4-2415473 | Text proposal on 7125 – 8400 MHz IMT parameters in TR 38.922 | Qualcomm Germany |
R4-2415479 | TP to TR 38.922: Corrections and clarifications on IMT parameters for 7125 to 8400 MHz frequency range | Nokia |
R4-2416172 | TP to TR 38.922 Add UE spectrum emission mask for 7125 to 8400 MHz | Ericsson |
R4-2416280 | TP for TR 38.922: Correction on BS IMT parameters for range 7125 to 8400 MHz | Huawei, HiSilicon |
R4-2417101 | Text proposal on 7125 – 8400 MHz IMT parameters in TR 38.922 | Qualcomm Germany |
R4-2417103 | TP for TR 38.922: Correction on BS IMT parameters for range 7125 to 8400 MHz | Huawei, HiSilicon, CATT, Nokia |
R4-2417104 | TP for TR 38.922: 8GHz UE parameters | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415999 | TP on UE parameters for 14800 to 15350 MHz frequency range | Samsung |
R4-2416000 | TP on coexistence simulation results for 14800 to 15350 MHz frequency range | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415119 | On coexistence evaluation results for 14.8 - 15.35GHz frequency range | CATT |
R4-2415378 | Discussion on ACLR for SU-MIMO and MU-MIMO with Co-existence Simulation | ISSDU Inc. |
R4-2415435 | Coexistence study for 14800 to 15350 MHz | MediaTek inc. |
R4-2415476 | Views on co-existence parameters for 14800 - 15350 MHz | Qualcomm Germany |
R4-2415480 | Urban macro coexistence simulation results for 14800 to 15350 MHz frequency range with 3 UE per slot | Nokia |
R4-2415481 | TP to TR 38.922: Revisions of system level simulation assumptions for study on IMT parameters for 14800 to 15350 MHz frequency range | Nokia |
R4-2415761 | Co-existence evaluation for 14800 to 15350 MHz frequency range | vivo |
R4-2416002 | Co-existence simulation results for 14800 – 15350 MHz | Samsung |
R4-2416170 | On 15 GHz co-existence simulation assumptions and results discussion | Ericsson |
R4-2416171 | On 15 GHz co-existence simulation results | Ericsson |
R4-2416242 | Discussion on co-existence evaluation for 14800 to 15350 MHz | ZTE Corporation, Sanechips |
R4-2417105 | TP to TR 38.922: Revisions of system level simulation assumptions for study on IMT parameters for 14800 to 15350 MHz frequency range | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415120 | On radio and antenna parameters for 14.8 - 15.35GHz frequency range | CATT |
R4-2415281 | Discussion on BS antenna array size for 14800 to 15350 MHz frequency range | Fujitsu Limited |
R4-2415315 | TP on general considerations for the UE antenna parameters for 14800-15350MHz | Apple, Samsung |
R4-2415316 | Further input on the UE antenna characteristics and gains | Apple |
R4-2415475 | Views on Radio parameters for 14800 - 15350 MHz | Qualcomm Germany |
R4-2415482 | BS antenna parameters for 14800 to 15350 MHz frequency range | Nokia |
R4-2415762 | Discussion on the UE parameter for 4800 to 15350 MHz frequency range | vivo |
R4-2415962 | Discussion on IMT parameters for 14800 to 15350 MHz. | MediaTek (Shenzhen) Inc. |
R4-2416001 | Views on BS and UE parameters for 14800 to 15350 MHz frequency range | Samsung |
R4-2416169 | On 15 GHz BS-UE radio and antenna parameters | Ericsson |
R4-2416243 | Discussion on radio and antenna parameters for 14800 to 15350 MHz | ZTE Corporation, Sanechips |
R4-2416412 | Discussion on IMT parameters for 15GHz range | Huawei, HiSilicon |
R4-2416414 | TP to TR 38.922: BS parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | Huawei, HiSilicon |
R4-2416416 | Draft running LS Reply on Parameters for 14800 to 15350 MHz of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-27 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414921 | Text Proposals for TR 38 922 on MIMO models and PA nonlinearity impacts and ACLR | Spark NZ Ltd |
R4-2415121 | On other aspects for IMT parameters | CATT |
R4-2415122 | TP for other issues (Adjacent channel modelling) | CATT |
R4-2415474 | Views on Additional AAS aspects | Qualcomm Germany |
R4-2415483 | On additional information required by ITU WP5D | Nokia |
R4-2415523 | Study of AAS performance in adjacent bands with multiple UE specific beams | Nokia |
R4-2415970 | TP to TR 38.922: Addition of new subclause for MIMO modelling aspects in subclause 7.3 | Ericsson |
R4-2416244 | Discussion on other issues in ITU-R LS | ZTE Corporation, Sanechips |
R4-2416281 | Further consideration and update simulation results for AAS modelling | Huawei, HiSilicon |
R4-2417106 | TP to TR 38.922: Addition of new subclause for MIMO modelling aspects in subclause 7.3 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415221 | Topic summary for [112bis][117] FS_NR_IMT | Moderator(Ericsson) |
R4-2417099 | Ad hoc minutes on FS_NR_IMT | Ericsson |
R4-2417107 | WF on 15GHz BS parameters | ZTE |
R4-2417108 | WF on 15GHz UE parameters | Qualcomm |
R4-2417109 | WF on other issues (MIMO) | Nokia, Spark |
R4-2417191 | WF on other issues (MIMO) | Nokia, Spark |
R4-2417200 | TR 38.922 v0.3.0 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415601 | on intra-band NCCA MPR simulation results | OPPO |
R4-2415603 | TP to TR to capture intra-band NCCA MPR simulation results | OPPO |
R4-2416066 | Tx requirements for intra-band non-contiguous CA | LG Electronics Finland |
TDoc | Title | Source |
---|---|---|
R4-2415600 | on intra-band CCA MPR simulation | OPPO |
R4-2415602 | TP to TR to capture intra-band CCA MPR simulation results | OPPO |
R4-2415894 | Tx requirements for intra-band contiguous CA | LG Electronics |
TDoc | Title | Source |
---|---|---|
R4-2415222 | Topic summary for [112bis][118] NR_SL_ intraB_CA_ITS_part1 | Moderator(OPPO) |
R4-2415223 | Topic summary for [112bis][119] NR_SL_ intraB_CA_ITS_part2 | Moderator(LGE) |
R4-2417089 | WF on sidelink intra-band CA part 1 | OPPO |
R4-2417090 | WF on sidelink intra-band CA part 2 | LGE |
TDoc | Title | Source |
---|---|---|
R4-2415123 | On sync raster applicability | CATT |
TDoc | Title | Source |
---|---|---|
R4-2415124 | Further discussion on UE RF requirements for inter-band NR CA/DC with less than 5MHz CBW | CATT |
R4-2415270 | draft LS on UE capability signling for inter-band CA/DC with less than 5MHz channel bandwidth | CATT |
R4-2415484 | UE RF requirements for inter-band NR CA/DC with 3MHz CBW | Nokia |
R4-2415818 | Discussion on UE RF requirements for inter-band NR CADC with 3MHz CBW | ZTE Corporation, Sanechips |
R4-2415819 | LS to RAN2 on introducing UE capability signaling to enable less than 5MHz CBW operation for CA/DC | ZTE Corporation, Sanechips |
R4-2416082 | Discussion on the remaining issues for Rel-19 less than 5MHz UE RF requirements | Intel Corporation |
R4-2416083 | Draft Big CR for less than 5MHz UE RF requirements in Rel-19 | Intel Corporation |
R4-2416084 | draftCR on SCell SSB transmissions for band n100 with 12 or 20PRB bandwidth | Intel Corporation |
R4-2416139 | NR Less than 5 MHz and CA/DC | Ericsson |
R4-2416271 | LS on applicability of Sync raster for SSB on Scell with 3MHz CBW | Huawei, HiSilicon |
R4-2416461 | Scell bandwidth and sync raster | Qualcomm Inc. |
R4-2417120 | draftCR on SCell SSB transmissions for band n100 with 12 or 20PRB bandwidth | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R4-2415540 | On RRM core for less than 5MHz Phase 2 | Apple |
R4-2415862 | Discussion on RRM requirements for less than 5MHz Ph2 | Huawei, HiSilicon |
R4-2416085 | Discussion on the RRM requirements for Rel-19 less than 5MHz UE | Intel Corporation |
R4-2416086 | Draft Big CR for less than 5MHz RRM requirements in Rel-19 | Intel Corporation |
R4-2416090 | Further Discussion on RRM requirements for NR CA/DC in less than 5 MHz | Ericsson |
R4-2416288 | Discussion on RRM core requirements for Less Than 5Mhz Phase 2 | Nokia |
R4-2416383 | Discussion on RRM impacts for less than 5MHz BW | ZTE Corporation, Sanechips |
R4-2416389 | draft CR to TS 38.133: NR channel BW less than 5MHz for FR1 | ZTE Corporation, Sanechips |
R4-2416455 | Discussion on core part for FR1 less than 5MHz | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415224 | Topic summary for [112bis][120] NR_FR1_5MHz_BW_Ph2 | Moderator(Intel) |
R4-2415652 | Topic summary for [112bis][205] NR_FR1_lessthan_5MHz_BW_Ph2 | Moderator (Intel) |
R4-2416849 | WF on RRM requirements for NR_FR1_lessthan_5MHz_BW_Ph2 | Intel |
R4-2416877 | Coffee break discussion minutes for [112bis][205] NR_FR1_lessthan_5MHz_BW_Ph2 | Intel |
R4-2417091 | Topic summary for [112bis][120] NR_FR1_5MHz_BW_Ph2 | Moderator(Intel) |
R4-2417092 | WF on NR channel BW less than 5MHz | Intel |
R4-2417118 | WF on NR channel BW less than 5MHz | Intel |
R4-2417119 | LS on Rel-19 NR channel BW less than 5MHz for FR1 | Intel |
R4-2417192 | WF on NR channel BW less than 5MHz | Intel |
TDoc | Title | Source |
---|---|---|
R4-2415372 | UE RF requirements for Type 4a/4b capable FWA UE for EN-DC/NR-CA | Nokia, NSB |
R4-2415441 | Discussion on UE RF requirement for non-collocated Type 4a4b | KDDI Corporation |
R4-2415514 | On reference architecture and RF capability for type 4 UE | Apple |
R4-2415515 | Draft CR on RF requirement update for type 4 UE | Apple |
R4-2415516 | Draft CR on RF requirement update for type 4 UE | Apple |
R4-2415518 | LS on freqeuncy separation for type 4 UE | Apple |
R4-2415594 | on intra-band non-collocated UE RF requirements | OPPO |
R4-2415913 | Discussion on UE RF for type 4a and type 4b for NonCol_intraB_ENDC_NR_CA | ZTE Corporation, Sanechips |
R4-2416069 | UE RF requirements for Type 4a/4b capable FWA UE for EN-DC/NR-CA | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414952 | Discussion on UE and NW behavior for non-collocated deployment | Samsung |
R4-2415373 | On Rel-19 non-collocated deployment UE Capability/UE behavior and network signaling | Nokia, NSB |
R4-2415443 | Discussion on UE Capability and BS Signaling for non-collocated Type 4a4b | KDDI Corporation |
R4-2415517 | On type 4 UE capability reporting | Apple |
R4-2415593 | on intra-band non-collocated UE behavior and capability | OPPO |
R4-2415914 | Discussion on UE Capability UE behavior and network signaling for Type 4a Type 4b EN-DCNR-CA | ZTE Corporation, Sanechips |
R4-2416070 | On UE Capability/UE behavior and network signaling for Type 4 EN-DC/NR-CA | Ericsson |
R4-2416258 | Non-collocated Intra-band NR CA/EN-DC UE requirements | Qualcomm France |
R4-2416265 | UE capability discussions for type 4 UEs | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414951 | Discussion on the referenced UE architecture table for non-collocated | Samsung |
R4-2415374 | Rel-19 clarifications of RF requirements for different power imbalance UE types | Nokia, NSB |
R4-2416260 | How to introduce UE types into the specifications and rectifying errors UE architecture types | Huawei, HiSilicon |
R4-2416450 | On definition of UE types for NonCol_intraB | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415519 | Discussion on RRM requirements for type 4 UE | Apple |
R4-2415520 | draft CR on RRM requirement update for type 4 UE | Apple |
R4-2415571 | RRM requirements for intra-band non-collocated scenarios Phase2 | Nokia, Nokia Shanghai Bell |
R4-2415840 | Discussion on RRM requirements for supporting intra-band non-collocated EN-DC/NR-CA deployment Phase2: new receiver type(s) | Huawei, HiSilicon |
R4-2416071 | On RRM core requirements | Ericsson |
R4-2416130 | General discussion on intra-band non-collocated EN-DCNR-CA type 4 | Samsung |
R4-2416386 | Discussion on intra-band non-collocated EN-DC and NR-CA | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415225 | Topic summary for [112bis][121] NonCol_intraB_ENDC_NR_CA | Moderator(KDDI) |
R4-2415653 | Topic summary for [112bis][206] NonCol_intraB_ENDC_NR_CA_Ph2 | Moderator (Huawei) |
R4-2416850 | WF on RRM requirements for NonCol_intraB_ENDC_NR_CA_Ph2 | Huawei |
R4-2417114 | WF on Rel-19 non-collocated scenario | KDDI |
R4-2417115 | WF on rest issues for intra-band non-collocated EN-DC/NR-CA | KDDI |
TDoc | Title | Source |
---|---|---|
R4-2415125 | Scope clarification on DL fragmented carriers | CATT |
R4-2416132 | Update of TR for Study on NR FR1 DL Fragmented Carriers | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R4-2414946 | Views on UE architecture and PSD difference for fragmented carriers | Samsung, TELUS, Bell mobility |
R4-2415037 | Discussion on reducing the number of UE Rx chains | OPPO |
R4-2415126 | Discussion on methods for reducing the number of UE Rx chains | CATT |
R4-2415390 | Discussion on methods for reducing the number of UE Rx RF chains for Fragmented Carriers | Nokia |
R4-2415510 | On methods for reducing the number of UE Rx chains for fragmented carriers | Apple |
R4-2415592 | Discussion on methods for reducing the number of UE RX chains | Spreadtrum Communications |
R4-2415758 | Discussion on methods for reducing the number of UE RX chains | vivo |
R4-2415804 | On methods for reducing the number of UE Rx chain | Huawei, HiSilicon |
R4-2415910 | View on methods for reducing the number of UE Rx chains | ZTE Corporation, Sanechips |
R4-2415992 | Discussion on UE Rx chains of Fragmented Carriers | Ericsson |
R4-2416040 | Discussion on the scenarios and the general aspects on the FR1 fragmented carriers study | CHTTL |
R4-2416138 | Discussion on UE Rx chain architecture and network assumption | MediaTek Inc. |
R4-2416287 | Views on UE architecture and PSD difference for fragmented carriers_rev | Samsung, TELUS, Bell mobility |
TDoc | Title | Source |
---|---|---|
R4-2414947 | Views on UE RF requirements for fragmented carriers | Samsung, TELUS, Bell mobility |
R4-2415038 | Discussion on impacts on UE RF requirements and DL performance | OPPO |
R4-2415127 | Discussion on impacts on UE RF requirements and DL performance | CATT |
R4-2415360 | Discussion on UE RF requirement impact for DL fragmented carriers | Murata Manufacturing Co Ltd. |
R4-2415391 | Discussion on impacts on UE RF requirements and DL performance for Fragmented Carriers | Nokia |
R4-2415511 | On UE RF requirements for fragmented carriers | Apple |
R4-2415533 | On in-gap and adjacent blockers level for fragmented spectrum reception in a single Rx path | Skyworks Solutions Inc. |
R4-2415759 | Discussion on impacts on UE RF requirements and DL performance | vivo |
R4-2415805 | On RF requirements of fragmented carriers | Huawei, HiSilicon |
R4-2415911 | View on Fragmented carrier general part and RF requirements | ZTE Corporation, Sanechips |
R4-2415993 | Discusson on impact on UE RF requirement of fragmented carriers | Ericsson |
R4-2416062 | Views on the RF impact on the FR1 fragmented carriers | CHTTL |
R4-2416164 | Discussion of impacts on UE RF requirements and DL performance impacts | MediaTek Inc., Telstra |
TDoc | Title | Source |
---|---|---|
R4-2415226 | Topic summary for [112bis][122] FS_NR_DL_Frag_Carrier | Moderator(Mediatek) |
R4-2417201 | WF on fragmented DL | MediaTek |
R4-2417202 | Ad hoc minutes on fragemented DL | MediaTek |
TDoc | Title | Source |
---|---|---|
R4-2415128 | Discussion on UE RF requirements for RedCap PC2 | CATT |
R4-2415129 | draftCR to TS 38.101-1 for RedCap PC2 | CATT |
R4-2415460 | CR to 38.101-1 for PC2 RedCap | Ericsson |
R4-2415462 | CR to 38.101-1 for PC2 RedCap | Ericsson |
R4-2415872 | Discussion on PC2 RedCap for TDD bands | China Telecom |
R4-2415873 | Draft CR to 38.101-1: power class 2 RedCap for TDD bands | China Telecom, ZTE |
R4-2416049 | Discussion on the specific wordings for Rel-19 PC2 TDD RedCap UE | Huawei, HiSilicon |
R4-2416460 | Draft CR to 38.101-1: Addition of PC2 (e)RedCap | Qualcomm Inc. |
R4-2417086 | Draft CR to 38.101-1: power class 2 RedCap for TDD bands | China Telecom, ZTE, CATT, China Unicom, Huawei, HiSilicon, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415227 | Topic summary for [112bis][123] NR_PC2_RedCap_UE | Moderator(China Telecom) |
TDoc | Title | Source |
---|---|---|
R4-2415025 | co-existence study for NTN HPUE | CMCC |
R4-2415307 | On coexistence study for NTN HPUE | Qualcomm Incorporated |
R4-2415806 | Co-existence evaluation of NTN HPUE | vivo Mobile Communication Co., |
R4-2415963 | Discussion on NTN coexistence study | Mediatek India Technology Pvt. |
R4-2416055 | Discussion on coexistence study for NR NTN HPUE | Huawei, HiSilicon |
R4-2416174 | On Co-existence simulation pre-liminary results for NR-NTN and NB-IoT-NTN HP UE | Ericsson |
R4-2416175 | On Co-existence simulation assumption considerations for NR-NTN and NB-IoT-NTN HP UE | Ericsson |
R4-2416245 | Discussion on coexistence results for NTN HPUE | ZTE Corporation, Sanechips |
R4-2416293 | On coexistence studies and preliminary results | Samsung |
R4-2416396 | Key aspects on HPUE for NTN | Inmarsat, Viasat |
TDoc | Title | Source |
---|---|---|
R4-2415039 | Discussion on Tx requirements for NR-NTN HPUE | OPPO |
R4-2415093 | Discussion on UE Tx requirement for NTN support HPUE | CATT |
R4-2415317 | On restricted set of power back-off simulations for the satellite band UE Tx requirements | Apple |
R4-2415387 | Discussion on feasible power class for UE | China Telecom Corporation Ltd. |
R4-2415731 | Discussion on NR-NTN HPUE TX RF requirements | Mediatek India Technology Pvt. |
R4-2415788 | Feasibility study and analysis for NR NTN HPUE Tx Requirements | vivo |
R4-2416056 | Discussion on Tx requirements for NR NTN HPUE | Huawei, HiSilicon |
R4-2416057 | Draft LS on network scheduling enhancement to gurantee NTN HPUE SAR compliance without output power reduction | Huawei, HiSilicon |
R4-2416246 | Discussion on Tx requirements for NTN UE | ZTE Corporation, Sanechips |
R4-2416294 | On NR-NTN HPUE Tx requirements | Samsung |
R4-2416466 | NTN high power UE requirements | Qualcomm Inc. |
R4-2416483 | On UE RF Tx requirements for NR-NTN HPUE | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415040 | Discussion on Rx requirements for NR-NTN HPUE | OPPO |
R4-2415094 | Discussion on UE Rx requirement for NTN support HPUE | CATT |
R4-2415729 | Discussion on NR-NTN HPUE RX RSD requirements | Mediatek India Technology Pvt. |
R4-2415789 | Analysis for NR NTN HPUE Rx Requirements | vivo |
R4-2416058 | Discussion on Rx requirements for NR NTN HPUE | Huawei, HiSilicon |
R4-2416247 | Discussion on Rx requirements for NTN UE | ZTE Corporation, Sanechips |
R4-2416295 | On NR-NTN HPUE Rx requirements | Samsung |
R4-2416484 | On UE RF Rx requirements for NR-NTN HPUE | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415585 | HPUE Tx requirements in IoT NTN | Sony |
R4-2415739 | Discussion on IoT-NTN HPUE TX RF requirements | Mediatek India Technology Pvt. |
R4-2415790 | Feasibility study and analysis for Iot NTN HPUE Tx Requirements | vivo |
R4-2416296 | On IoT-NTN HPUE Tx requirements | Samsung |
R4-2416485 | On UE RF Tx requirements for IoT-NTN HPUE | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415730 | Discussion on IoT-NTN HPUE RX RSD requirements | Mediatek India Technology Pvt. |
R4-2415791 | Analysis for Iot NTN HPUE Rx Requirements | vivo |
R4-2416297 | On IoT-NTN HPUE Rx requirements | Samsung |
R4-2416486 | On UE RF Rx requirements for IoT-NTN HPUE | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415049 | Discussion on system parameters for NTN less than 5MHz | Xiaomi |
R4-2415091 | Discussion on system parameter for NTN support spectrum less than 5 MHz | CATT |
R4-2415694 | System parameters for Less than 5MHz supporting in NTN | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415746 | Discussion on system parameters for less than 5MHz in FR1-NTN bands | vivo |
R4-2416275 | Remaining NTN System parameters for less than 5MHz CBW | Huawei, HiSilicon |
R4-2416481 | Operator input for NR NTN Less than 5 MHz | Inmarsat, Viasat |
R4-2416487 | On system parameters for less than 5 MHz CBW for NTN | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415050 | Discussion on UE RF requirements for NTN less than 5MHz | Xiaomi |
R4-2415092 | Discussion on UE RF requirements for NTN support spectrum less than 5 MHz | CATT |
R4-2415318 | On UE RF requirements for the 3MHz channel | Apple |
R4-2415319 | Initial results for the power back-off values for the 3MHz channel in band n254 | Apple, Globalstar |
R4-2415583 | Supporting 3MHz BW for Redcap/eRedcap NTN | Sony |
R4-2415693 | UE RF requirements for Less than 5MHz supporting in NTN FR1 bands | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415747 | Discussion on UE RF requirements for less than 5MHz in FR1-NTN bands | vivo |
R4-2415820 | DraftCR to 38.101-5 Introduction of less than 5MHz channel bandwidth for FR1-NTN | ZTE Corporation, Sanechips |
R4-2415974 | Discussion on less than 5 MHz NTN UE aspects | Nokia |
R4-2416255 | A-MPR evaluations of NS_03N, NS_N04N, NS_05N and NS_24 for 3MHz CBW for NTN communication. | Huawei, HiSilicon |
R4-2416465 | UE RF requirements for NTN less than 5 MHz | Qualcomm Inc. |
R4-2416488 | On UE RF requirements for less than 5 MHz for NTN | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415090 | Discussion on SAN RF requirements for NTN support spectrum less than 5 MHz | CATT |
R4-2415485 | SAN RF core requirements for less than 5MHz for NTN | Nokia |
R4-2415691 | SAN RF requirements for Less than 5MHz supporting in NTN FR1 bands | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415821 | DraftCR to TS38.108 Introduction of less than 5MHz channel bandwidth for FR1-NTN | ZTE Corporation, Sanechips |
R4-2416489 | On SAN RF requirements for less than 5 MHz for NTN | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415059 | Discussion on RRM requirements for less than 5MHz NTN | Xiaomi |
R4-2415153 | Discussion on less than 5MHz for NTN RRM requirement | CATT |
R4-2415345 | Support of less than 5MHz for NR NTN | Qualcomm Incorporated |
R4-2415544 | On less than 5MHz for NTN RRM | Apple |
R4-2415550 | Discussion on RRM requirements of Rel-19 NR-NTN in less than 5MHz | Samsung |
R4-2415863 | Discussion on RRM requirements for less than 5MHz for NTN | Huawei, HiSilicon |
R4-2415953 | Discussion on RRM requirements for less than 5MHz over NTN | MediaTek inc. |
R4-2416073 | Discussion on RRM requirements of NTN with channel BW less than 5MHz | Ericsson |
R4-2416191 | Defining RRM scope of work for less than 5 MHz | Nokia |
R4-2416370 | Discussion on RRM requirements for less than 5M in NTN | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415152 | Discussion on NTN testing for NGSO | MediaTek inc. |
R4-2415377 | Views on TE emulated channel model for satellite motion | Anritsu Corporation |
R4-2415633 | Discussion on NTN testing for NGSO channel model | Huawei,HiSilicon |
R4-2415646 | Discussion on NTN testing for NGSO | QUALCOMM Europe Inc. - Spain |
R4-2415870 | TE-emulated channel model for NTN UE demodulation requirements | Ericsson |
R4-2415984 | Discussion on NTN testing NGSO channel model | Samsung |
R4-2416192 | On the NGSO Satellite Motion Trajectory used in testing | Nokia |
R4-2416394 | Discussion on methodology for doppler and delay modelling for NGSO satellites | Rohde & Schwarz |
TDoc | Title | Source |
---|---|---|
R4-2415228 | Topic summary for [112bis][124] NR_IoT_NTN_HPUE_part1 | Moderator(Samsung) |
R4-2415229 | Topic summary for [112bis][125] NR_IoT_NTN_HPUE_part2 | Moderator(Vivo) |
R4-2415654 | Topic summary for [112bis][207] NR_IoT_NTN_req_test_enh | Moderator (Xiaomi) |
R4-2416532 | Topic summary for [112bis][311] NR_IoT_NTN_less_than_5MHz_UERF | Moderator (Xiaomi) |
R4-2416533 | Topic summary for [112bis][312] NR_IoT_NTN_less_than_5MHz_BSRF | Moderator (Nokia) |
R4-2416542 | Topic summary for [112bis][321] NTN_testing_NGSO_channel_model | Moderator (Samsung) |
R4-2416556 | Way Forward for [112bis][321] NTN_testing_NGSO_channel_model | Samsung |
R4-2416562 | Way Forward for [112bis][311] NR_IoT_NTN_less_than_5MHz_UERF | Xiaomi |
R4-2416564 | Way Forward for [112bis][312] NR_IoT_NTN_less_than_5MHz_BSRF | Nokia |
R4-2416587 | Way Forward for [112bis][311] NR_IoT_NTN_less_than_5MHz_UERF | Xiaomi |
R4-2416851 | WF on RRM requirements for [112bis][207] NR_IoT_NTN_req_test_enh | Xiaomi |
R4-2417122 | WF on co-existence study and HPUE for NR-NTN | Samsung |
R4-2417123 | WF on HPUE for IoT NTN | Vivo |
R4-2417205 | WF on HPUE for IoT NTN | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2415380 | Regulatory Landscape and Satellite Use Cases in the Ku Band | Intelsat |
R4-2415381 | Mobile VSAT Motivation and Market Growth | Intelsat |
R4-2415680 | Regulation Analysis for Region 3 Ku-band Band Definitions | SKY Perfect JSAT Corporation |
R4-2416013 | NR NTN Ku band plan for region 3 | CHTTL |
R4-2416052 | Draft CR for TR 38.863 to introduce some regulatory information | Huawei, HiSilicon |
R4-2416142 | NTN Ku-band - Regulatory aspects and bands definition | Ericsson |
R4-2416567 | Draft CR for TR 38.863 to introduce some regulatory information | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415079 | Discussion on coexistence evaluations for Ku-band for NR NTN | CATT |
R4-2415276 | Discussions on VSAT parameters for Ku Band coexistence testing | Sharp |
R4-2415822 | Discussion on coexistence study based on ITU regulations for NTN Ku band | ZTE Corporation, Sanechips |
R4-2416054 | Discussion on coexistence study for NR NTN Ku Band | Huawei, HiSilicon |
R4-2416140 | NTN Ku-band - Coexistence | Ericsson |
R4-2416298 | On Ku-band coexsitence studies | Samsung |
R4-2416503 | On the VSAT and Satellite Parameters for Ku-band Coexistence | THALES |
TDoc | Title | Source |
---|---|---|
R4-2415080 | Discussion on system parameters for Ku-band for NR NTN | CATT |
R4-2415284 | Feasibility analysis of FR1 and FR2 Numerology | Eutelsat Group |
R4-2415379 | Analysis of NTN channel bandwidths for optimal efficiency | Intelsat |
R4-2415436 | Discussions on system parameters of Ku Band for NR NTN | MediaTek inc. |
R4-2415695 | System parameters for Ku band | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415823 | Discussion on system parameters for NTN Ku band | ZTE Corporation, Sanechips |
R4-2415976 | Discussion on NR NTN system parameters for Ku band | Nokia |
R4-2416141 | NTN Ku-band - FR1-NTN vs FR2-NTN | Ericsson |
R4-2416491 | Discussion on the Choice of Numerology for Ku-Band | THALES |
TDoc | Title | Source |
---|---|---|
R4-2415679 | Ku-band VSAT UE RF requirement analysis | SKY Perfect JSAT Corporation |
R4-2415824 | Discussion on UE RF requirements for NTN Ku band | ZTE Corporation, Sanechips |
R4-2415977 | Discussion on NR NTN UE RF requirement for Ku band | Nokia |
R4-2416014 | Initial analysis on the regulations for the UE RF requirements of the NR NTN Ku band | CHTTL |
R4-2416053 | Discussion on VSAT requirements for NR NTN Ku band | Huawei, HiSilicon |
R4-2416067 | Discussion on NR NTN Ku Band SCS and CBW | LG Electronics Finland |
R4-2416143 | NTN Ku-band - UE RF requirements | Ericsson |
R4-2416299 | On Ku-band UE RF requirements | Samsung |
R4-2417116 | WF on UE RF requirements for MIMO enhancement | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415081 | Discussion on SAN RF core requirements for Ku-band for NR NTN | CATT |
R4-2415825 | Discussion on SAN RF requirements for NTN Ku band | ZTE Corporation, Sanechips |
R4-2415978 | Discussion on NR NTN SAN requirement for Ku band | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2416534 | Topic summary for [112bis][313] NR_NTN_Ku_Band_General | Moderator (Eutelsat) |
R4-2416535 | Topic summary for [112bis][314] NR_NTN_Ku_Band_UE_SAN_RF | Moderator (CHTTL ) |
R4-2416563 | Way Forward for [112bis][314] NR_NTN_Ku_Band_UE_SAN_RF | CHTTL |
R4-2416568 | Ad-hoc meeting minutes for [112bis][313] NR_NTN_Ku_Band_General | Eutelsat |
R4-2416569 | Way Forward for [112bis][313] NR_NTN_Ku_Band_General | Eutelsat |
R4-2416593 | Way Forward for [112bis][313] NR_NTN_Ku_Band_General | Eutelsat |
TDoc | Title | Source |
---|---|---|
R4-2415311 | On Rel-19 ATG UE RF requirements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2415015 | Discussion on UE RF requirements for ATG with intra-band contiguous CA | CMCC |
R4-2415985 | Discussion on RF requirement of ATG UE intra-band contiguous CA | Ericsson |
R4-2416046 | Discussion on Rel-19 ATG UE RF with DL intra-band contiguous CA | Huawei, HiSilicon |
R4-2416235 | RF requirement for Intra-band contiguous CA of ATG UE in Rel-19 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415014 | Discussion on UE RF requirements for ATG with inter-band CA | CMCC |
R4-2415896 | ATG UE RF requirements for inter-band CA | LG Electronics |
R4-2415986 | Discussion on RF requirement of ATG UE inter-band CA | Ericsson |
R4-2416047 | Discussion on Rel-19 ATG UE RF with DL inter-band CA_n3-n39 | Huawei, HiSilicon |
R4-2416236 | Discussion on RF requirement for Inter-band CA for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415016 | Discussion on UE RF requirements for ATG with UL-MIMO | CMCC |
R4-2415897 | ATG UE RF requirements for UL-MIMO | LG Electronics |
R4-2415987 | Discussion on RF requirement of ATG UE UL MIMO | Ericsson |
R4-2416048 | Discussion on Rel-19 ATG UE RF with UL MIMO | Huawei, HiSilicon |
R4-2416237 | Discussion on RF requirement for UL-MIMO for ATG UE in Rel-19 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2414976 | discussion on BS requirements for ATG enhancements | Huawei, HiSilicon |
R4-2415013 | Discussion on BS RF requirements for ATG with CA | CMCC |
R4-2415104 | Discussion on the remaining issues for ATG enhancement BS RF | CATT |
R4-2415105 | Draft CR for 38.104: Introduction of R19 ATG enhancement BS RF requirements | CATT |
R4-2415869 | Draft CR for TS 38.104 to add ATG enhancement BS RF requirements | Huawei, HiSilicon |
R4-2415915 | draft CR to TS 38.104: the introduction of Rel-19 ATG BS supporting CA | ZTE Corporation, Sanechips |
R4-2415988 | Discussion on remaining issues of ATG BS supporting CA | Ericsson |
R4-2415989 | Draft CR for 38.104 Introduction of Rel-19 ATG enhancement BS RF | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415002 | (NR_ATG_enh-Core) Discussion on RRM requirements for R19 ATG | CMCC |
R4-2415154 | Discussion on enhancements for Rel-19 ATG RRM requirements | CATT |
R4-2415522 | RRM requirement for ATG | Apple |
R4-2415698 | Discussion on RRM aspects of R19 ATG | ZTE Corporation, Sanechips |
R4-2415839 | Discussions on RRM requirements for Rel-19 ATG | Huawei, HiSilicon |
R4-2415878 | Discussion on RRM requirements for ATG CA operation | LG Electronics Inc. |
R4-2416009 | Further Discussion on Rel-19 ATG CA RRM requirements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415230 | Topic summary for [112bis][126] NR_ATG_enh | Moderator(CMCC) |
R4-2415655 | Topic summary for [112bis][208] NR_ATG_enh | Moderator (CMCC) |
R4-2416526 | Topic summary for [112bis][305] NR_ATG_enh | Moderator (ZTE) |
R4-2416852 | WF on RRM requirements for [112bis][208] NR_ATG_enh | CMCC |
R4-2417093 | WF on UE RF for ATG enhancement | CMCC |
R4-2417121 | WF on UE RF for ATG enhancement | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2415972 | On the topic of focus area for BS RF evolution | Ericsson |
R4-2416278 | DraftCR to 38.141-2: Expected EIRP Test procedure | Huawei, HiSilicon |
R4-2416311 | Draft CR to TS 38.141-2 with EEIRP mask testing procedure | Nokia |
R4-2416517 | Consideration of co-existence and co-location requirements optimisation | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2416266 | Core aspects for OTA spatial emission above the horizon requirement for BS operating in band n104 | Ericsson |
R4-2416268 | Draft CR to TS 38.104: Addition of spatial emission requirement to protect FSS UL within band n104 | Ericsson |
R4-2416308 | Core requirement for Expected EIRP mask | Nokia |
R4-2416309 | Draft CR to TS 38.104 for introduction of expected EIRP mask core requirement | Nokia |
R4-2416501 | Draft CR on correction for OTA spatial emission requirement | Samsung |
R4-2416570 | Draft CR to TS 38.104 for introduction of expected EIRP mask core requirement | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415674 | OTA test enhancements - CLTA | Nokia |
R4-2415971 | On the topic of aspects related to BS-to-BS co-location | Ericsson |
R4-2416238 | Further discussion on OTA test enhancement | ZTE Corporation, Sanechips |
R4-2416276 | Discussion on CLRA/CLTA | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414920 | Text Proposals for TR 38 908 for BS conformance tests for the Validation of EIRP | Spark NZ Ltd |
R4-2415101 | Discussion on U6GHz EEIRP mask requirement test | CATT |
R4-2415102 | Draft CR for TS 38.141-2: Declarations for U6GHz EEIRP mask requirement test | CATT |
R4-2415471 | Views on EIRP mask considerations for upper 6GHz | Qualcomm Germany |
R4-2416239 | TR 38.908 v1.1.0 Protection of fixed satellite service (FSS) UL within 6425 to 7125 MHz | ZTE Corporation, Sanechips |
R4-2416240 | Further discussion on Expected EIRP mask for upper 6GHz | ZTE Corporation, Sanechips |
R4-2416241 | Draft CR for introduction of U6GHz EIRP conformance testing | ZTE Corporation, Sanechips |
R4-2416267 | Conformance test aspects for the requirement on OTA spatial emission above the horizon for BS operating in band n104 | Ericsson |
R4-2416269 | Draft CR to TS 38.141-2: Addition of spatial emission requirement to protect FSS UL within band n104 | Ericsson |
R4-2416277 | Further discussion on Expected EIRP test | Huawei, HiSilicon |
R4-2416279 | TX IMD test for high frequency band in FR1 | Huawei, HiSilicon |
R4-2416310 | On conformance testing of Expected EIRP mask requirement | Nokia |
R4-2416312 | Draft CR to TS 38.141-2 with Annex N Expected EIRP calculation | Nokia |
R4-2416313 | TP to TR 38.908 clause 6 – Conformance testing | Nokia |
R4-2416502 | Discussion on OTA spatial emission conformance testing | Samsung |
R4-2416571 | Draft CR for introduction of U6GHz EIRP conformance testing | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2416523 | Topic summary for [112bis][302] NR_BS_RF_Part1_E_EIRP | Moderator (ZTE) |
R4-2416524 | Topic summary for [112bis][303] NR_BS_RF_Part2_CLTA | Moderator (Huawei) |
R4-2416525 | Topic summary for [112bis][304] NR_BS_RF_Part3_OTA_TRP | Moderator (ZTE) |
R4-2416559 | Ad-hoc meeting minutes for [112bis][302] NR_BS_RF_Part1_E_EIRP | ZTE |
R4-2416572 | Way Forward for [112bis][302] NR_BS_RF_Part1_E_EIRP | ZTE |
R4-2416573 | TP to TR 38.908 clause 6 – Conformance testing | ZTE |
R4-2416574 | Way Forward for [112bis][303] NR_BS_RF_Part2_CLTA | Huawei |
TDoc | Title | Source |
---|---|---|
R4-2415320 | [draft] LS on XR positioning guidelines and MU for head phantom OTA testing | Apple |
R4-2415769 | Discussions and draft reply LS on 3GPP LTE TRP TRS test method for phone >72mm | vivo |
R4-2415770 | Draft CR on adding test method for UE over 72mm wide | vivo |
R4-2416212 | Reply to LS R4-2414918 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2416211 | Rel-19 FR1 OTA requirements | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415269 | on XR OTA test | Huawei, HiSilicon |
R4-2415277 | Discussion on OTA Test for XR Devices | Meta |
R4-2415321 | Discussion on XR test method and Configurations | Apple |
R4-2415560 | On XR UE OTA test | Samsung |
R4-2415775 | Reply LS to CTIA on XR types for phantom development | vivo |
R4-2416063 | Discusion on XR OTA test method | CAICT |
R4-2416210 | Test methodology for FR1 non-RedCap headworn XR devices | Nokia |
R4-2416376 | Consideration of test time reduction for XR device | OPPO |
R4-2416575 | Reply LS to CTIA on XR device type for phantom development | vivo |
TDoc | Title | Source |
---|---|---|
R4-2415056 | Discussion on OTA test for FR1 NTN devices | Xiaomi |
R4-2415268 | on NTN OTA test | Huawei, HiSilicon |
R4-2415309 | On FR1 NTN devices OTA | Qualcomm Incorporated |
R4-2415561 | On NTN UE OTA test | Samsung |
R4-2415776 | Further discussions on IoT-NTN and NR-NTN OTA test method | vivo |
R4-2416377 | Further discussion of NTN OTA performance metrics | OPPO |
R4-2416392 | Operator views on Usage Modes for NTN Smartphones | Inmarsat, Viasat |
R4-2416480 | On NTN OTA Testing | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2415267 | on MIMO dynamic channel tests | Huawei, HiSilicon |
R4-2415310 | On FR1 dynamic MIMO OTA test method | Qualcomm Incorporated |
R4-2415562 | On HARQ parameter for FR1 dynamic MIMO OTA | Samsung |
R4-2416165 | Reference values for FR1 dynamic channel models validation | CMCC |
R4-2416433 | TR 38.762 V0.1.0 on MIMO OTA dynamic test methodology for FR1 UEs | CAICT |
R4-2416478 | TP on Dynamic MIMO Aspects | Keysight Technologies UK Ltd, Spirent Communications |
R4-2416479 | Preliminary Results from Dynamic MIMO OTA Measurement Campaign | Keysight Technologies UK Ltd, CAICT |
R4-2416578 | TP on Dynamic MIMO Aspects | Keysight Technologies UK Ltd, Spirent Communications |
TDoc | Title | Source |
---|---|---|
R4-2415563 | On performance of Rel-19 OTA WI | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415340 | Inputs to Rel-19 TRP TRS Lab Alignment and Performance Campaign | Apple |
R4-2415777 | Working procedure for Rel-19 2Tx lab alignment and UE performance measurement campaign | vivo |
R4-2416064 | Discussion on TRP TRS requirements | CAICT |
TDoc | Title | Source |
---|---|---|
R4-2416432 | Framework for Rel-19 MIMO OTA requirements (Oct 2024) | CAICT |
TDoc | Title | Source |
---|---|---|
R4-2416544 | Topic summary for [112bis][323] TRP_TRS_Ph3 | Moderator (vivo) |
R4-2416545 | Topic summary for [112bis][324] MIMO_OTA_Ph3 | Moderator (CAICT) |
R4-2416576 | Way Forward for [112bis][323] TRP_TRS_Ph3 | Vivo |
R4-2416577 | Ad-hoc meeting minutes for [112bis][323] TRP_TRS_Ph3 | Vivo |
R4-2416579 | Way Forward for [112bis][324] MIMO_OTA_Ph3 | CAICT |
R4-2416590 | Way Forward for [112bis][323] TRP_TRS_Ph3 | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2415308 | Discussion on FR2 OTA test method on STxMP | Qualcomm Incorporated |
R4-2415564 | On FR2 OTA testing of STxMP | Samsung |
R4-2415760 | Discussion on the FR2 sTxMP OTA testing | vivo |
R4-2416476 | On absolute probe locations | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2416546 | Topic summary for [112bis][325] NR_FR2_OTA | Moderator (Qualcomm) |
R4-2416580 | Way Forward for [112bis][325] NR_FR2_OTA | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2414957 | Views on spatial channel modeling study | China Telecom |
R4-2415296 | Discussion on General Items on SCM SI | Nokia |
R4-2415297 | TR 38.753 Skeleton | Nokia |
R4-2416093 | Discussion on general issue of NR SCM for demodulation | Ericsson |
R4-2416549 | TR 38.753 Skeleton | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415078 | Discussion on spatial channel modelling methodology | CATT |
R4-2415282 | Discussion on Spatial Channel Model for Demodulation Performance Requirements | Nokia |
R4-2415283 | Simulation Results and CDL Implementation for Spatial Channel Model for Demodulation Performance Requirements | Nokia |
R4-2415285 | TDL and CDL comparison with respect to the CSI resolution feedback | Orange, BT, Telecom Italia, Vodafone, Bouygues Telecom, Fraunhofer, Deutsche Telekom |
R4-2415382 | Discussion on spatial channel modelling | MediaTek inc. |
R4-2415383 | Simulation results of spatial channel modelling | MediaTek inc. |
R4-2415506 | On Spatial Channel Modeling for Demodulation Requirements | Apple |
R4-2415636 | Discussion on spatial channel modelling methodology | Huawei,HiSilicon |
R4-2415673 | Further observations from deployment and MU-MIMO use cases for SCM evaluation | BT plc |
R4-2415682 | Discussion on spatial channel model for demodulation performance requirements | Samsung |
R4-2416094 | Discussion on methodology of NR SCM for demodulation | Ericsson |
R4-2416095 | Simulation results for NR SCM for demodulation | Ericsson |
R4-2416343 | Discussion on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
R4-2416344 | Simulation results on spatial channel model for demodulation performance requirements | ZTE Corporation, Sanechips |
R4-2416380 | Study of SCM Model Parameters for demodulation performance requirements | Qualcomm Incorporated |
R4-2416451 | On Rel-19 spatial channel model for demodulation performance requirements | Keysight Technologies UK Ltd |
TDoc | Title | Source |
---|---|---|
R4-2416539 | Topic summary for [112bis][318] NR_SCM | Moderator (Nokia) |
R4-2416550 | Ad-hoc meeting minutes for [112bis][318] NR_SCM | Nokia |
R4-2416551 | Way Forward for [112bis][318] NR_SCM | Nokia |
R4-2416581 | Ad-hoc meeting minutes for [112bis][318] NR_SCM | Nokia |
R4-2416591 | Way Forward for [112bis][318] NR_SCM | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415062 | Discussion on FR2-1 SSB based L3 measurement delay reduction by RX beam | Xiaomi |
R4-2415179 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | CATT |
R4-2415196 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | vivo |
R4-2415244 | Discussion on L3 measurement delay reduction by optimizing Rx beam sweeping factor | CMCC |
R4-2415513 | On FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Apple |
R4-2415578 | Discussion on L3 measurement enhancement by optimizing Rx BSF | Samsung |
R4-2415697 | Discussion on Rx beam factor optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
R4-2415732 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | China Telecom |
R4-2415834 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Huawei, HiSilicon |
R4-2415879 | Discussion on RRM requirements for FR2-1 L3 measurement delay reduction | LG Electronics Inc. |
R4-2415887 | FR2-1 L3 measurement delay by optimizing RX beam sweeping factor | Qualcomm Incorporated |
R4-2415929 | Discussions on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | NTT DOCOMO, INC. |
R4-2416017 | On RRM Ph5 L3 BSF reduction | Nokia |
R4-2416078 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | Ericsson |
R4-2416087 | Discussion on delay reduction by optimizing Rx beam sweeping factors | Intel Corporation |
R4-2416118 | Discussion on FR2-1 L3 measurement delay by optimizing Rx beam sweeping factor | OPPO |
R4-2416511 | Discussion on FR2-1 SSB based L3 measurement delay reduction by optimizing Rx beam sweeping factor | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415063 | Discussion on FR2-1 SSB based L3 measurement delay reduction by CCSF optimization | Xiaomi |
R4-2415180 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | CATT |
R4-2415197 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | vivo |
R4-2415245 | Discussion on L3 measurement delay reduction by optimizing CSSF outside gap in CA/DC | CMCC |
R4-2415545 | On FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA DC | Apple |
R4-2415574 | FR2-1 SSB based L3 measurement delay reduction with CSSF optimization | Nokia, Nokia Shanghai Bell |
R4-2415696 | Discussion on CSSF optimization of R19 RRM enhancements | ZTE Corporation, Sanechips |
R4-2415733 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | China Telecom |
R4-2415838 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Huawei, HiSilicon |
R4-2415888 | Enhancement on FR2 CSSF | Qualcomm Incorporated |
R4-2416079 | Discussion on FR2-1 L3 measurement delay by optimizing CSSF outside gap in CA/DC | Ericsson |
R4-2416088 | Discussion on delay reduction by optimizing CSSF outside gaps | Intel Corporation |
R4-2416117 | Discussion on L3 measurement delay by optimizing CSSF | Samsung |
R4-2416119 | Discussion on FR2-1 L3 measurement delay reduction by optimizing CSSF | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2415150 | Discussion on fast SCell activation for UE supporting Rel-18 EMR | vivo |
R4-2415181 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | CATT |
R4-2415182 | draftCR on Fast SCell activation for UE supporting Rel-18 EMR | CATT, Apple |
R4-2415246 | Discussion on fast SCell activation for UE supporting Rel-18 EMR | CMCC |
R4-2415346 | Fast SCell activation based on Rel-18 eEMR | Qualcomm Incorporated |
R4-2415361 | Discussion on RRM requirements for Fast SCell activation for UE supporting R18 EMR | LG Electronics Inc. |
R4-2415487 | Discussion on fast SCell activation for UE supporting Rel-18 EMR | Apple |
R4-2415575 | Discussion on fast SCell activation for UE supporting eEMR | Samsung |
R4-2415734 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | China Telecom |
R4-2415835 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | Huawei, HiSilicon |
R4-2416120 | On fast SCell activation with EMR | OPPO |
R4-2416168 | Disucssion on fast Scell activation for UE supporting Rel-18 EMR | Ericsson |
R4-2416289 | Discussion on Fast SCell activation for UE supporting Rel-18 EMR | Nokia |
R4-2416387 | Discussion on the fast SCell activation for UE supporting Rel-18 EMR | ZTE Corporation, Sanechips |
R4-2416512 | Discussion on the RRM requirements for fast SCell activation for UE supporting Rel-18 EMR | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415656 | Topic summary for [112bis][209] NR_RRM_Ph5_Part1 | Moderator (Apple) |
R4-2415657 | Topic summary for [112bis][210] NR_RRM_Ph5_Part2 | Moderator (CATT) |
R4-2416853 | WF on RRM requirements for NR_RRM_Ph5_Part1 | Apple |
R4-2416872 | Ad-hoc minutes for NR_RRM_Ph5 | Apple |
TDoc | Title | Source |
---|---|---|
R4-2416272 | On general issues for MMSE-IRC receiver under interference | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414955 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | China Telecom |
R4-2415003 | (NR_demod_Ph5-Perf) Discussion on interference suppressing performance for 8Rx UE | CMCC |
R4-2415151 | Discussion on UE requirements with 8Rx MMSE-IRC receiver | MediaTek inc. |
R4-2415507 | On UE demodulation performance requirements with 8RX | Apple |
R4-2415634 | Discussion on UE 8Rx performance requirements with MMSE-IRC | Huawei,HiSilicon |
R4-2415683 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | Samsung |
R4-2416273 | On MMSE-IRC receiver for interference mitigation with 8Rx | Ericsson |
R4-2416274 | Simulation results for MMSE-IRC UE demodulation | Ericsson |
R4-2416345 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
R4-2416346 | Simulation results on UE demodulation performance requirements for 8Rx with MMSE-IRC | ZTE Corporation, Sanechips |
R4-2416417 | Discussion on UE demodulation performance requirements for 8Rx with MMSE-IRC | Nokia |
R4-2416521 | Views on 8Rx UE demodulation and CSI requirements with inter-cell and intra-cell interference | Qualcomm Atheros, Inc. |
TDoc | Title | Source |
---|---|---|
R4-2414956 | Discussion on BS demodulation performance requirements for MMSE-IRC | China Telecom |
R4-2415004 | (NR_demod_Ph5-Perf) Discussion on BS demodulation requirements for interference suppressing with MMSE-IRC receiver | CMCC |
R4-2415047 | BS demodulation performance requirements for MMSE-IRC | Tejas Network Limited |
R4-2415077 | Discussion on BS demodulation performance for MMSE-IRC | CATT |
R4-2415472 | Views on BS demodulation requirements for MMSE-IRC | Qualcomm Germany |
R4-2415635 | Discussion on BS MMSE-IRC requirements with inter-cell interference | Huawei,HiSilicon |
R4-2415983 | View and initial simulation results for BS demodulation requirement with MMSE-IRC receiver | Samsung |
R4-2415994 | Simulation results summary for BS requirement with MMSE-IRC receiver | Samsung |
R4-2416091 | Discussion on NR MMSE-IRC BS demodulation | Ericsson |
R4-2416092 | Simulation results for NR MMSE-IRC BS demodulation | Ericsson |
R4-2416347 | Discussion on BS demodulation performance for MMSE-IRC | ZTE Corporation, Sanechips |
R4-2416348 | Simulation results for BS demodulation performance for MMSE-IRC | ZTE Corporation, Sanechips |
R4-2416442 | NR Demodulation Performance Phase 5: BS demodulation performance requirements for MMSE-IRC | Nokia |
R4-2416506 | Discussion on BS demodulation for MMSE-IRC. | NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R4-2416540 | Topic summary for [112bis][319] NR_demod_Ph5_Part1_General_BS | Moderator (China Telecom) |
R4-2416541 | Topic summary for [112bis][320] NR_demod_Ph5_Part2_UE | Moderator (Nokia) |
R4-2416547 | Ad-hoc meeting minutes for [112bis][319] NR_demod_Ph5_Part1_General_BS | China Telecom |
R4-2416548 | Way Forward for [112bis][319] NR_demod_Ph5_Part1_General_BS | China Telecom |
R4-2416554 | Ad-hoc meeting minutes for [112bis][320] NR_demod_Ph5_Part2_UE | Nokia |
R4-2416555 | Way Forward for [112bis][320] NR_demod_Ph5_Part2_UE | Nokia |
R4-2416854 | WF on RRM requirements for NR_RRM_Ph5_Part2 | CATT |
TDoc | Title | Source |
---|---|---|
R4-2414958 | Discussion on general aspects of AIML for NR air interface | CAICT |
R4-2415169 | Discussion on general aspects for AIML for NR air | CATT |
R4-2415186 | Discussion on general aspects for AIML | vivo |
R4-2415253 | Discussion on general aspects | CMCC |
R4-2415271 | Discussion on general aspects for AI/ML air | Korea Testing Laboratory |
R4-2415495 | Discussion on General Aspects on AI/ML for NR Air Interface | Apple |
R4-2415620 | Discussion on general aspects on AIML for NR air interface | Huawei,HiSilicon |
R4-2415687 | Views on general aspects of AI/ML testability and interoperability | Intel Corporation |
R4-2415930 | Discussions on general aspects of AIML for NR Air Interface | NTT DOCOMO, INC. |
R4-2415964 | On General Aspects of AI/ML for NR Air Interface | Nokia |
R4-2416004 | Views on general aspect of AI/ML for NR air interface | Samsung |
R4-2416202 | On general AI/ML aspects | Ericsson |
R4-2416366 | Discussion on the AI/ML general aspects | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415028 | Testability and interoperability issues for CSI compression | OPPO |
R4-2415072 | Discussion on testability and interoperability issues for CSI compression | Xiaomi |
R4-2415174 | Discussion on testability and interoperability issues for CSI compression | CATT |
R4-2415187 | Discussion on testability and interoperability issues for CSI compression | vivo |
R4-2415251 | Discussion on testability and interoperability issues for CSI compression | CMCC |
R4-2415376 | On AI/ML Interoperability and Standardization of Testing and Verification for CSI Use Case | NTU |
R4-2415384 | Discussion on CSI compression Testability and interoperability | MediaTek inc. |
R4-2415498 | Study for CSI Compression: Testability and Interoperability issues | Apple |
R4-2415621 | Discussion on testability and interoperability issues in AIML CSI compression | Huawei,HiSilicon |
R4-2415688 | Views on AI/ML testability and interoperability for CSI compression use case | Intel Corporation |
R4-2415889 | CSI Compression: Testability and Interoperability | Qualcomm Incorporated |
R4-2415965 | On AI/ML Based CSI Compression | Nokia |
R4-2416314 | CSI compression considerations and simulation results | Ericsson |
R4-2416349 | Discussion on testability and interoperability issues for CSI compression | ZTE Corporation, Sanechips |
R4-2416395 | Discussion on test decoder for CSI compression | Rohde & Schwarz |
R4-2416495 | Further study on testability and interoperability issues for AI-CSI compression | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415029 | AIML two-sided model logistical issues | OPPO |
R4-2415188 | Discussion on AI/ML two-sided model logistical issues for CSI compression | vivo |
R4-2415252 | Discussion on AI/ML two-sided model logistical issues | CMCC |
R4-2415385 | Discussion on CSI compression AI/ML two-sided model logistics | MediaTek inc. |
R4-2415500 | Discussion on CSI Compression: AI/ML two-sided model logistical issues | Apple |
R4-2415622 | Discussion on AIML two-sided model logistical issues | Huawei,HiSilicon |
R4-2415689 | Views on logistics of AI/ML model and dataset sharing for CSI compression use case | Intel Corporation |
R4-2415891 | Logistical Issues of Two-Sided Model for AI/ML CSF | Qualcomm Incorporated |
R4-2415895 | Summary of e-mail discussion on data sharing for AI/ML | Qualcomm Incorporated |
R4-2415966 | On AI/ML CSI Compression Two-Sided Model Logistical Issues | Nokia |
R4-2416315 | On AI/ML model sharing and logistics | Ericsson |
R4-2416350 | Discussion on two-side model logistical issues | ZTE Corporation, Sanechips |
R4-2416496 | Further discussion on AI/ML two-sided model logistical issues | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2414959 | Discussion on testability and interoperability issues for CSI prediction | CAICT |
R4-2415175 | Discussion on testability and interoperability issues for CSI prediction | CATT |
R4-2415189 | Discussion on testability and interoperability issues for CSI prediction | vivo |
R4-2415250 | Discussion on testability and interoperability issues for CSI prediction | CMCC |
R4-2415358 | Discussion on testability and interoperability of AI for CSI feedback enhancement | SEU |
R4-2415386 | Discussion on CSI prediction testability and interoperability | MediaTek inc. |
R4-2415499 | Discussion on CSI Prediction: Testability and Interoperability issues | Apple |
R4-2415623 | Discussion on testability and interoperability issues in AIML CSI prediction | Huawei,HiSilicon |
R4-2415871 | Discussion on CSI prediction | Ericsson |
R4-2415890 | CSI Prediction: Testability | Qualcomm Incorporated |
R4-2415967 | On AI/ML Based CSI Prediction | Nokia |
R4-2416351 | Discussion on testability and interoperability issues for CSI prediction | ZTE Corporation, Sanechips |
R4-2416494 | Testability and interoperability issues for AI-CSI prediction | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2414929 | Discussion on core requirements of AI/ML BM use case | MediaTek Inc. |
R4-2415030 | RRM core requirements for beam management | OPPO |
R4-2415071 | Discussion on core part requirement for AI beam management | Xiaomi |
R4-2415170 | Discussion on RRM core requirements for BM | CATT |
R4-2415190 | Discussion on RRM core requirements for beam management | vivo |
R4-2415249 | Discussion on RRM requirements for beam management | CMCC |
R4-2415496 | Discussion on Beam Management: RRM Core Requirements | Apple |
R4-2415624 | Discussion on RRM core requirements in AIML Beam management | Huawei,HiSilicon |
R4-2415893 | RRM Core Requirements for AI/ML Beam Management | Qualcomm Incorporated |
R4-2416080 | Discussion on RRM core requirements for beam management | Ericsson |
R4-2416363 | Discussion on the RRM requirements of AI/ML Beam management | ZTECorporation,Sanechips |
R4-2416439 | RRM core requirements for AI/ML Based Beam Management | Nokia |
R4-2416492 | Further discussion on beam management core requirements | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2414930 | Discussion on testability issues of AI/ML BM use case | MediaTek Inc. |
R4-2414960 | Discussion on testability and interoperability issues for beam management | CAICT |
R4-2415031 | Testability and interoperability issues for beam management | OPPO |
R4-2415070 | Discussion on testability and interoperability issues for AI beam management | Xiaomi |
R4-2415171 | Discussion on testability and interoperability issues for BM | CATT |
R4-2415191 | Discussion on testability and interoperability issues for beam management | vivo |
R4-2415248 | Discussion on testability and interoperability issues for beam management | CMCC |
R4-2415312 | Discussion on testability issues for AI/ML beam management | Qualcomm Incorporated |
R4-2415497 | Discussion on Beam Management: Testability and Interoperability Issues | Apple |
R4-2415625 | Discussion on testability and interoperability issues in AIML Beam management | Huawei,HiSilicon |
R4-2416081 | Discussion on testability and interoperability issues for beam management | Ericsson |
R4-2416362 | Discussion on the Interoperability and testability aspects of AI/ML Beam management | ZTECorporation,Sanechips |
R4-2416391 | Discussion on test setup for AI/ML based beam management | ROHDE & SCHWARZ |
R4-2416440 | On Testability and Interoperability aspects for AI/ML Based Beam Management | Nokia |
R4-2416477 | On Testability Aspects for FR2 AI/ML Beam Management | Keysight Technologies UK Ltd |
R4-2416493 | Further discussion on testability and interoperability issues for beam management | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415172 | Discussion on RRM core requirements for positioning | CATT |
R4-2415192 | Discussion on RRM core requirements for positioning accuracy enhancement | vivo |
R4-2415255 | Discussion on RRM requirements for positioning | CMCC |
R4-2415501 | Discussion on RRM Core Requirements for positioning accuracy enhancement | Apple |
R4-2415626 | Discussion on RRM core requirements in AIML Positioning | Huawei,HiSilicon |
R4-2415892 | RRM Core Requirements for Positioning Accuracy | Qualcomm Incorporated |
R4-2416330 | On issues related to AI/ML for positioning | Ericsson |
R4-2416365 | Discussion on the RRM requirements of AI/ML positioning | ZTECorporation,Sanechips |
R4-2416447 | RRM core requirements for AI/ML positioning accuracy enhancement | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415032 | Testability and interoperability issues for positioning | OPPO |
R4-2415173 | Discussion on testability and interoperability issues for positioning | CATT |
R4-2415193 | Discussion on testability and interoperability issues for positioning accuracy enhancement | vivo |
R4-2415254 | Discussion on testability and interoperability issues for positioning | CMCC |
R4-2415502 | Discussion on Testability and interoperability issues for positioning accuracy enhancement | Apple |
R4-2415627 | Discussion on testability and interoperability issues in AIML Positioning | Huawei,HiSilicon |
R4-2416331 | On testability of AI/ML for positioning | Ericsson |
R4-2416364 | Discussion on the Interoperability and testability aspects of AI/ML positioning | ZTECorporation,Sanechips |
R4-2416448 | Testability and interoperability issues for AI/ML positioning accuracy enhancement | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415231 | Topic summary for [112bis][127] NR_AIML_air | Moderator(Qualcomm) |
R4-2417113 | WF on requirements for AI/ML air interface | Qualcomm |
R4-2417187 | WF on data sharing for AI/ML air interface | Qualcomm |
R4-2417188 | Ad hoc minutes on AI/ML air interface | Qualcomm |
R4-2417189 | Simulation assumptions for beam prediction | Vivo |
R4-2417207 | WF on data sharing for AI/ML air interface | Qualcomm |
R4-2417208 | Simulation assumptions for beam prediction | Vivo |
R4-2417210 | WF on requirements for AI/ML air interface | Qualcomm |
R4-2417211 | Simulation assumptions for beam prediction | Vivo |
R4-2417212 | WF on requirements for AI/ML air interface | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2415504 | Study on AI (Artificial Intelligence)/ML (Machine Learning) for mobility in NR: General Aspects and Work Plan | Apple |
R4-2415844 | Discussion on genereal aspects in AIML mobility | Huawei, HiSilicon |
R4-2415931 | Discussions on general aspects of AIML for mobility | NTT DOCOMO, INC. |
R4-2415968 | Work Plan for RAN4 Discussions on AI/ML for Mobility in NR | Nokia, OPPO, Mediatek |
TDoc | Title | Source |
---|---|---|
R4-2414931 | Discussion on RRM requirements of AI mobility | MediaTek Inc. |
R4-2415033 | Study of impacts on RAN4 requirements for AI mobility | OPPO |
R4-2415073 | Discussion on impacts on RAN4 requirement for AI mobility | Xiaomi |
R4-2415176 | Views on impacts of AIML mobility on RAN4 requirements | CATT |
R4-2415194 | Discussion on impacts on RAN4 requirements for AI mobility | vivo |
R4-2415256 | Discussion on impacts on RAN4 requirements for AI/ML for mobility | CMCC |
R4-2415347 | Impact of AI based mobility on RRM requirements | Qualcomm Incorporated |
R4-2415505 | Study on AI (Artificial Intelligence)/ML (Machine Learning) for mobility in NR: Study of impacts on RAN4 requirements | Apple |
R4-2415577 | General discussion on RRM requirement impact analyses on AI mobility | Samsung |
R4-2415845 | Discussion on impacts of RAN4 requirements in AIML mobility | Huawei, HiSilicon |
R4-2415932 | Discussions on RAN4 requirement impacts of AIML for mobility | NTT DOCOMO, INC. |
R4-2416332 | On requirements for AI/ML based mobility | Ericsson |
R4-2416381 | Discussion impacts on requirements of AI/ML mobility | ZTE Corporation, Sanechips |
R4-2416449 | On AIML Mobility Scenarios Evaluation and RRM Requirements Impacts | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2414932 | Discussion on testability and interoperability of AI mobility | MediaTek Inc. |
R4-2415034 | Study of testability and interoperabilityfor AI mobility | OPPO |
R4-2415064 | Initial discussion on study of testability and interoperability for AIML mobility | Xiaomi |
R4-2415177 | Discussion on testability and interoperability issues for AIML mobility | CATT |
R4-2415195 | Discussion on testability and interoperability for AI mobility | vivo |
R4-2415257 | Discussion on testability and interoperability for AI/ML for mobility | CMCC |
R4-2415348 | Testability and interoperability for AI based mobility | Qualcomm Incorporated |
R4-2415503 | Study on AI (Artificial Intelligence)/ML (Machine Learning) for mobility in NR: Study of testability and interoperability | Apple |
R4-2415576 | General discussion on AI mobility regarding testability and interoperability | Samsung |
R4-2415846 | Discussion on testability and interoperability issues in AIML mobility | Huawei, HiSilicon |
R4-2416333 | On testability issues related to AI/ML for mobility | Ericsson |
R4-2416382 | Discussion on the Interoperability and testability aspects | ZTE Corporation, Sanechips |
R4-2416441 | On Testability and Interoperability Issues for AI/ML Mobility | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415658 | Topic summary for [112bis][211] FS_NR_AIML_Mob | Moderator (Nokia) |
R4-2416855 | WF on RRM requirements for FS_NR_AIML_Mob | Nokia |
R4-2416915 | Coffee break discussion minutes for FS_NR_AIML_Mob | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2416072 | LS on of frequency offset report range AFO and phase offset number of levels MPO | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414983 | R19 MPR for 3Tx | OPPO |
R4-2415333 | On UE RF impact of 3Tx UL MIMO | Apple |
R4-2415724 | FR1 3Tx power scaling and FR2 asymmetric connection scenario | Qualcomm Incorporated, Sony |
R4-2415792 | Further discussion of UE RF impact for NR MIMO phase 5 | vivo |
R4-2415998 | Views on UE RF requirements of Rel-19 NR MIMO | Samsung |
R4-2416184 | On RF requirements for Rel-19 NR-MIMO | Huawei, HiSilicon |
R4-2416213 | UE RF requirements (MIMO Phase5) | Nokia |
R4-2416490 | On UE RF requirements for NR MIMO Phase 5 | Ericsson India Private Limited |
TDoc | Title | Source |
---|---|---|
R4-2415075 | Discussion on UE-initiated/event-driven beam management on Rel-19 MIMO phase 5 | Xiaomi |
R4-2415238 | Discussion on RRM requirements for event-driven beam management for NR MIMO Phase 5 | CMCC |
R4-2415301 | On RRM requirements for enhanced UE-initiated/event-driven beam management | Qualcomm Technologies Ireland |
R4-2415508 | On RRM Requirements for UE initiated beam management | Apple |
R4-2415534 | Discussion on RRM requirements for UE initiated Beam reporting in R19 MIMO | vivo |
R4-2415551 | Discussion on RRM requirements of UE-initiated beam management in Rel-19 MIMO phase 5 | Samsung |
R4-2415701 | Discussion on RRM aspects of UE-initiated beam management of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
R4-2415830 | Discussion on RRM impact for Rel-19 MIMO on UE initiated BM | Huawei, HiSilicon |
R4-2416016 | On NR MIMO Phase 5 UE-initiated/event-driven beam management | Nokia |
R4-2416334 | Discussion on UE initiated BM requirements | Ericsson |
R4-2416513 | Discussion on R19 MIMO for UE-initiated/event-driven beam management | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415076 | Discussion on other RRM requirement on Rel-19 MIMO phase 5 | Xiaomi |
R4-2415239 | Discussion on other RRM requirements for NR MIMO Phase 5 | CMCC |
R4-2415302 | Views on additional RRM requirements for NR MIMO Phase 5 | Qualcomm Technologies Ireland |
R4-2415509 | On RRM Requirements for MIMO Phase 5 | Apple |
R4-2415535 | Discussion on other RRM requirement impacts in R19 MIMO | vivo |
R4-2415552 | Discussion on RRM requirements of other aspects in Rel-19 MIMO phase 5 | Samsung |
R4-2415702 | Discussion on other RRM aspects of R19 NR MIMO Phase 5 | ZTE Corporation, Sanechips |
R4-2415831 | Discussion on RRM impact for Rel-19 MIMO other aspect | Huawei, HiSilicon |
R4-2416335 | Discussion on other RRM requirements for MIMO | Ericsson |
R4-2416467 | On NR MIMO Phase 5 asymmetric DL sTRP/UL mTRP | Nokia |
R4-2416514 | Discussion on R19 MIMO for other RRM requirements | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415232 | Topic summary for [112bis][128] NR_MIMO_Ph5_UE | Moderator(Samsung) |
R4-2415659 | Topic summary for [112bis][212] NR_MIMO_Ph5_Part1 | Moderator (Samsung) |
R4-2415660 | Topic summary for [112bis][213] NR_MIMO_Ph5_Part2 | Moderator (MediaTek) |
R4-2416856 | WF on RRM requirements for NR_MIMO_Ph5_Part1 | Samsung |
R4-2416857 | WF on RRM requirements for NR_MIMO_Ph5_Part2 | MediaTek |
R4-2416873 | Ad-hoc minutes for NR_MIMO_Ph5 | Samsung |
R4-2416921 | WF on RRM requirements for NR_MIMO_Ph5_Part2 | MediaTek |
R4-2417117 | LS on UE RF issues for Rel-19 MIMO enhancement | Huawei |
TDoc | Title | Source |
---|---|---|
R4-2415021 | Discussion on SBFD general part | CMCC |
R4-2415042 | Discussion on SBFD General aspects | Tejas Network Limited |
R4-2415100 | Discussion on SBFD system parameters | CATT |
R4-2415272 | Consideration of band/channel bandwidth support for SBFD | CableLabs, Charter Communications |
R4-2415467 | Views on general aspects for SBFD | Qualcomm Germany |
R4-2415587 | SBFD minimum channel bandwidth and SBFD as a band-specific feature | Charter, CableLabs |
R4-2415678 | On SBFD system parameters | Nokia |
R4-2415748 | Discussion on the subband configurations and guardbands for gNB SBFD | vivo |
R4-2416134 | SBFD general aspects | Ericsson |
R4-2416185 | On general aspects for SBFD | Huawei, HiSilicon |
R4-2416248 | Discussion on system parameters for SBFD BS | ZTE Corporation, Sanechips |
R4-2416497 | Discussion on RAN4 aspects for SBFD system parameters | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415024 | Discussion on new RF requirement for SBFD | CMCC |
R4-2415043 | Discussion on Potentially new requirements for SBFD operation | Tejas Network Limited |
R4-2415109 | Discussion on potentially new requirements for SBFD operation | CATT |
R4-2415468 | Views on new requirements for SBFD | Qualcomm Germany |
R4-2415677 | On potentially new BS RF requirements for SBFD operation | Nokia |
R4-2416135 | Potentially new SBFD BS RF requirements | Ericsson |
R4-2416186 | On potentially new requirements for SBFD | Huawei, HiSilicon |
R4-2416249 | Discussion on potentially new requirements for SBFD operation | ZTE Corporation, Sanechips |
R4-2416498 | On the potentially new requirements for SBFD operation for FR1 and FR2-1 | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415023 | Discussion on existing Tx requirements for SBFD | CMCC |
R4-2415045 | Discussion on existing Tx requirements for SBFD operation | Tejas Network Limited |
R4-2415108 | Discussion on modification of existing Tx requirements for SBFD operation | CATT |
R4-2415469 | Views on existing Tx BS RF requirements for SBFD | Qualcomm Germany |
R4-2415676 | On existing BS RF TX requirements for SBFD operation | Nokia |
R4-2416136 | Impact on SBFD BS RF TX requirements | Ericsson |
R4-2416250 | Discussion on modification of existing Tx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
R4-2416284 | On modification of existing TX RF requirements for SBFD | Huawei, HiSilicon |
R4-2416499 | On the modification of existing TX requirements for FR1 and FR2-1 SBFD-capable BS | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415022 | Discussion on existing Rx requirements for SBFD | CMCC |
R4-2415046 | Views on modification of existing Rx requirements for SBFD | Tejas Network Limited |
R4-2415106 | SBFD in-band blocking and dynamic range simulation results | CATT |
R4-2415107 | Discussion on modification of existing Rx requirements for SBFD operation | CATT |
R4-2415470 | Views on existing Rx BS RF requirements for SBFD | Qualcomm Germany |
R4-2415675 | On existing BS RF RX requirements for SBFD operation | Nokia |
R4-2416137 | Impact on SBFD BS RF RX requirements | Ericsson |
R4-2416251 | Discussion on modification of existing Rx requirements for FR1 and FR2-1 for SBFD BS | ZTE Corporation, Sanechips |
R4-2416285 | On modification of existing RX RF requirements for SBFD | Huawei, HiSilicon |
R4-2416500 | On the modification of existing RX requirements for FR1 and FR2-1 SBFD-capable BS | Samsung |
TDoc | Title | Source |
---|---|---|
R4-2415145 | Consideration on RRM for SBFD | vivo |
R4-2415178 | Discussions on SBFD RRM requirements | CATT |
R4-2415243 | Discussion on RRM requirements for SBFD | CMCC |
R4-2415362 | Discussion on RRM requirements for NR duplex operation | LG Electronics Inc. |
R4-2415512 | On UE RRM requirement for SBFD | Apple |
R4-2415573 | RRM requirements for evolution of NR duplex operation | Nokia, Nokia Shanghai Bell |
R4-2415690 | Views on RRM requirements for Rel-19 SBFD WI | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415703 | Discussion on RRM aspects of R19 SBFD | ZTE Corporation, Sanechips |
R4-2415735 | Discussion on RRM core requirements for evolution of NR duplex operation | China Telecom |
R4-2415866 | Discussion on RRM requirements for SBFD | Huawei, HiSilicon |
R4-2416167 | Disucssion on SBFD RRM core requirements and simulation assumptions | Ericsson |
R4-2416453 | Discussion on RRM requirements for SBFD | MediaTek inc. |
R4-2416471 | RRM requirements for SBFD | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2415661 | Topic summary for [112bis][214] NR_duplex_evo | Moderator (Huawei) |
R4-2416527 | Topic summary for [112bis][306] NR_duplex_evo_General | Moderator (Samsung) |
R4-2416528 | Topic summary for [112bis][307] NR_duplex_evo_BSRF | Moderator (Huawei) |
R4-2416552 | Ad-hoc meeting minutes for [112bis][306] NR_duplex_evo_General | Samsung |
R4-2416553 | Ad-hoc meeting minutes for [112bis][307] NR_duplex_evo_BSRF | Huawei |
R4-2416583 | Ad-hoc meeting minutes for [112bis][306] NR_duplex_evo_General | Samsung |
R4-2416584 | Way Forward for [112bis][306] NR_duplex_evo_General | Samsung |
R4-2416585 | Way Forward for [112bis][307] NR_duplex_evo_BSRF | Huawei |
R4-2416858 | WF on RRM requirements for NR_duplex_evo | Huawei |
R4-2416907 | Coffee break discussion minutes for NR_duplex_evo | Samsung |
R4-2416909 | LS on the scenario of UE to UE CLI measurement report in SBFD operation | Apple |
R4-2416910 | Simulation assumptions for L1 SRS-RSRP measurement | Ericsson |
R4-2416919 | LS on the scenarios of UE-to-UE CLI measurement report in SBFD operation | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415001 | Collection of calibration data for A-IoT | CMCC |
R4-2415097 | Discuss on AIoT R2D LLS in RAN4 | CATT |
R4-2415449 | A-IoT general overview | Ericsson |
R4-2417193 | A-IoT general overview | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414963 | Discussion on A-IoT deployment scenarios and spectrum usage | Huawei, HiSilicon |
R4-2414995 | Deployment scenario and spectrum usage | CMCC |
R4-2415305 | Discussion on AIoT deployment scenarios and spectrum usage | Qualcomm Incorporated |
R4-2415448 | A-IoT deployment scenario and spectrum usage | Ericsson |
R4-2415763 | Discussion on the impact of CW node | vivo |
TDoc | Title | Source |
---|---|---|
R4-2414996 | Discussion on A-IoT co-existence evaluation | CMCC |
R4-2415052 | Simulation results for Ambient-IoT Co-existence study | Xiaomi |
R4-2415082 | Co-existence evaluation results for Ambient IoT in NR | CATT |
R4-2415098 | Discussion on co-existence simulation parameters | CATT |
R4-2415306 | Discussion on Ambient IoT Coexistence Evaluations | Qualcomm Incorporated |
R4-2415453 | Coexisting study simulation assumptions and initial results | Ericsson |
R4-2415580 | Coexistence evaluation on D1T1 deployment scenario | Sony |
R4-2415596 | on co-existence evaluations | OPPO |
R4-2415608 | Discussion on co-existence evaluation results for Ambient IoT and NR | Spreadtrum Communications |
R4-2415764 | Discussion on the co-existence for D2T2 | vivo |
R4-2416229 | Discussion on Co-existence evaluations | ZTE Corporation, Sanechips |
R4-2416230 | The calibration results for A-IoT evaluations | ZTE Corporation, Sanechips |
R4-2416301 | On co-existence assumptions | Samsung |
R4-2416355 | Collection of simulation results for Ambient-IoT co-existence study | Huawei, HiSilicon |
R4-2416356 | TP to TR38.769: Co-existence simulation | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2414997 | Discussion on A-IoT BS RF requirements | CMCC |
R4-2415110 | draft TP to TR 38.769 for A-IoT BS TX requirements | CATT |
R4-2415111 | Discussion on A-IoT BS requirements | CATT |
R4-2415447 | A-IoT BS RF overview | Ericsson |
R4-2415765 | Discussion on the RF requirement for AIoT BS | vivo |
R4-2416231 | Discussion on RF requirement of Ambient IoT BS | ZTE Corporation, Sanechips |
R4-2416282 | RF requirements for Ambient IoT BS | Huawei, HiSilicon |
R4-2417194 | A-IoT BS RF overview | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414998 | Discussion on A-IoT device RF requirements | CMCC |
R4-2415051 | TP for TR 38.769 on RF requirements for device 2a | Xiaomi |
R4-2415099 | Discussion on A-IoT device RF requirements | CATT |
R4-2415451 | A-IoT device OTA requirement and testing aspects | Ericsson |
R4-2415466 | On the RF requirements for Ambient IoT Device | Huawei, HiSilicon |
R4-2415530 | Energy harvesting considerations for A-IoT device | Qualcomm Incorporated |
R4-2415581 | Further considerations on the ambient IoT device implementation and RF aspect | Sony |
R4-2415588 | Discussion on RF requirements impact for ambient IoT device | Spreadtrum Communications |
R4-2415591 | TP for TR 38.769 on device 1 RF requirements | Spreadtrum Communications |
R4-2415595 | TP to TR on device 2b RF requirements | OPPO |
R4-2415598 | on device RF requirements | OPPO |
R4-2415766 | Discussion on the RF requirement for AIoT device | vivo |
R4-2416232 | Discussion on RF requirement of Ambient IoT device | ZTE Corporation, Sanechips |
R4-2416482 | Discussion on Ambient IoT Device RF requirement impact | LG Electronics UK |
TDoc | Title | Source |
---|---|---|
R4-2414964 | On the RF Requirements for Ambient IoT intermediate UE | Huawei, HiSilicon |
R4-2414999 | Discussion on A-IoT intermediate UE RF requirements | CMCC |
R4-2415112 | Discussion on A-IoT intermediate UE requirements | CATT |
R4-2415450 | RF overview for UE as reader | Ericsson |
R4-2415589 | Discussion on RF requirements impact for intermediate node (UE) | Spreadtrum Communications |
R4-2415599 | on intermediate UE RF requirements | OPPO |
R4-2415767 | Discussion on the RF requirement for intermediate UE | vivo |
R4-2416233 | Discussion on RF requirement of Intermediate node (UE) | ZTE Corporation, Sanechips |
R4-2416352 | Simultaneous operation of Ambient IoT and Uu in intermediate UE | LG Electronics UK |
R4-2416360 | TP to TR 38.769 for Intermediate node Rx requirement | LG Electronics UK |
TDoc | Title | Source |
---|---|---|
R4-2415000 | Discussion on CW cancellation capability | CMCC |
R4-2415452 | On CW cancellation capability | Ericsson |
R4-2415529 | CW cancellation feasibility | Qualcomm Incorporated |
R4-2415590 | Discussion on methods and feasibility values of CW interference cancellation | Spreadtrum Communications |
R4-2415597 | on CW cancellation capability | OPPO |
R4-2415768 | Dicussion on the CW cancellation capbaility | vivo |
R4-2416234 | Discussion on the feasibility values of CW interference cancellation from BS perspective | ZTE Corporation, Sanechips |
R4-2416283 | CW interference cancelation | Huawei, HiSilicon |
R4-2416300 | On Ambient IoT CW cancellation | Samsung |
R4-2417195 | TP for CW interference cancelation | Huawei, HiSilicon, Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415233 | Topic summary for [112bis][129] FS_Ambient_IoT_solutions_part1 | Moderator(CMCC) |
R4-2415234 | Topic summary for [112bis][130] FS_Ambient_IoT_solutions_part2 | Moderator(Huawei) |
R4-2417087 | WF on Co-existence study for A-IoT and NR/LTE | CMCC |
R4-2417088 | WF on RF requirement impact of A-IoT | Huawei |
R4-2417196 | WF on Co-existence study for A-IoT and NR/LTE | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2415536 | Discussion on RRM requirement impacts from on-demand SIB1 in R19 NES | vivo |
R4-2416025 | Discussion on RAN1 LS in NES | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415005 | (Netw_Energy_NR_enh-Core) Discussion on RRM requirement of OD-SSB for NES enhancement | CMCC |
R4-2415060 | Discussion on OD-SSB requirements | Xiaomi |
R4-2415183 | Discussion on RRM requirements for on-demand SSB Scell operation | CATT |
R4-2415303 | On RRM requirements for on-demand SSB SCell operation | Qualcomm Technologies Ireland |
R4-2415488 | Discussion on on-demand SSB SCell operation | Apple |
R4-2415489 | Reply LS on timeline for On-demand SSB operation on SCell | Apple |
R4-2415537 | Discussion on RRM requirements for on-demand SSB SCell operation in R19 NES | vivo |
R4-2415572 | RRM requirements for OD-SSB SCell operation | Nokia, Nokia Shanghai Bell |
R4-2415684 | Discussion on RRM requirements for on-demand SSB SCell operation | Samsung |
R4-2415685 | Reply LS on timeline for On-demand SSB operation on SCell | Samsung |
R4-2415699 | Discussion on On-demand SSB SCell operation of R19 NES | ZTE Corporation, Sanechips |
R4-2415705 | Reply LS on timeline for On-demand SSB operation on SCell | ZTE Corporation, Sanechips |
R4-2415736 | Discussion on On-demand SSB SCell operation for enhancements of network energy savings for NR | China Telecom |
R4-2415832 | Discussion on RRM impact for Rel-19 NES on OD-SSB | Huawei, HiSilicon |
R4-2415933 | Discussions on OD-SSB requirements | NTT DOCOMO, INC. |
R4-2415954 | Discussion on RRM requirements for OD-SSB for network energy saving | MediaTek inc. |
R4-2416019 | Discussion on RRM requirements of on-demand SSB Scell operation for Rel-19 NES | LG Electronics Inc. |
R4-2416023 | Discussion on OD-SSB in Rel-19 NES | Ericsson |
R4-2416089 | Discussion on RRM requirements for On-demand SSB SCell operations | Intel Corporation |
R4-2416121 | On RRM requirements of on-demand SSB SCell operation | OPPO |
R4-2416122 | On RRM requirements of SSB adaptation | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2415006 | (Netw_Energy_NR_enh-Core) Discussion on RRM requirement of signal adapatation for NES enhancement | CMCC |
R4-2415061 | Discussion on RRM requirements for adaptation of common signal/channel in NES | Xiaomi |
R4-2415184 | Discussion on RRM requirements for adaptation of common signal/channel transmission | CATT |
R4-2415304 | On RRM requirements for adaptation of common signal/channel transmission | Qualcomm Technologies Ireland |
R4-2415490 | Discussion on adaptation of common signal/channel transmission | Apple |
R4-2415538 | Discussion on RRM requirements for common signal or channel adaptation in R19 NES | vivo |
R4-2415700 | Discussion on adaptation of common signal and channel of R19 NES | ZTE Corporation, Sanechips |
R4-2415737 | Discussion on SSB adaptation requirements for enhancements of network energy savings for NR | China Telecom |
R4-2415833 | Discussion on RRM impact for Rel-19 NES on adpatation | Huawei, HiSilicon |
R4-2415955 | Discussion on RRM requirements for adaptation of common signal/channel transmission | MediaTek inc. |
R4-2416024 | Discussion on RS and channel adaptation in Rel-19 NES | Ericsson |
R4-2416026 | Discussion on RRM requirements of SSB adaptation for Rel-19 NES | LG Electronics Inc. |
R4-2416116 | General discussion on the NES common signal adaptation | Samsung |
R4-2416438 | RRM requirements for SSB adaptation | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R4-2415662 | Topic summary for [112bis][215] Netw_Energy_NR_enh_Part1 | Moderator (Ericsson) |
R4-2415663 | Topic summary for [112bis][216] Netw_Energy_NR_enh_Part2 | Moderator (Huawei) |
R4-2416859 | WF on RRM requirements for Netw_Energy_NR_enh_Part1 | Ericsson |
R4-2416860 | WF on RRM requirements for Netw_Energy_NR_enh_Part2 | Huawei |
R4-2416874 | Ad-hoc minutes for Netw_Energy_NR_enh | Ericsson |
R4-2416911 | LS on SSB adaptation | Apple |
R4-2416913 | LS on SSB relation in OD-SSB and SSB adaptation on Scell | Ericsson |
R4-2416916 | WF on RRM requirements for Netw_Energy_NR_enh_Part1 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415455 | On general issues for WUR | Ericsson |
R4-2415778 | Skeleton for LP-WUS TR 38.774 | vivo |
R4-2415803 | Discussions on LP-WUS RAN1 LS | vivo |
TDoc | Title | Source |
---|---|---|
R4-2415582 | Further views on requirements of the low-power wake-up receiver | Sony |
TDoc | Title | Source |
---|---|---|
R4-2415018 | Discussion on LP-WUS UE system parameters requirements | CMCC |
R4-2415130 | Further discussion on system parameters for LP-WUS | CATT |
R4-2415456 | On system paramter for WUR | Ericsson |
R4-2415524 | On Low-power Wake-up Receiver for NR | Apple |
R4-2415611 | Discussion on systems parameters for LP-WUR | Spreadtrum Communications |
R4-2415706 | System parameters for LP-WUR | Nokia |
R4-2415779 | Discussions on LP-WUS system parameters | vivo |
TDoc | Title | Source |
---|---|---|
R4-2415020 | Discussion on LP-WUS UE RF Rx requirements of REFSENS, ASCS and ACS | CMCC |
R4-2415131 | On Rx requirements of REFSENS, ASCS and ACS for LP-WUS | CATT |
R4-2415201 | Further consideration on UE REFSENS, ACS requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2415459 | WUR RF requirement REFSESN ASC ASCS | Ericsson |
R4-2415558 | Discussion on UE RF requirements for LP-WUR | Samsung |
R4-2415610 | Discussion on RX requirements of REFSENS for LP-WUR | Spreadtrum Communications |
R4-2415707 | Fundamental RX requirements for LP-WUR | Nokia |
R4-2415723 | On UE Rx requirements for the LPWUR | Qualcomm Incorporated |
R4-2415780 | Further discussions on LP-WUS REFSENS, ASCS and ACS | vivo |
R4-2415938 | Discussion on REFSENS, ASCS, ACS for LP-WUR | ZTE Corporation, Sanechips |
R4-2416196 | Discussion on REFSENS and ASCS for the LP-WUS/WUR | LG Electronics France |
R4-2416378 | LP-WUS ACS | OPPO |
TDoc | Title | Source |
---|---|---|
R4-2415019 | Discussion on LP-WUS UE RF Rx requirements of IBB, OBB, intermodulation, spurious emissions and others | CMCC |
R4-2415132 | On Rx requirements of IBB, OBB, intermodulation for LP-WUS | CATT |
R4-2415202 | Further consideration on UE RF other Rx requirements for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2415458 | WUR RF requirement other than REFSENS | Ericsson |
R4-2415708 | Other RX requirements for LP-WUR | Nokia |
R4-2415781 | Discussions on LP-WUS IBB and OBB requirements | vivo |
R4-2415939 | Discussion on receiver characteristics for LP-WUR | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415133 | Testability for UE RF requirements for LP-WUS | CATT |
R4-2415203 | Further consideration on UE RF testability issues for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2415457 | On WUR RF requirement testability | Ericsson |
R4-2415559 | Discussion on testability for LP-WUR | Samsung |
R4-2415709 | Testability aspects of LP-WUR | Nokia |
R4-2415782 | Discussions on LP-WUS Testability | vivo |
R4-2415940 | Discussion on testability of LP-WUR | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415017 | Discussion on LP-WUS BS RF requirements | CMCC |
R4-2415134 | On BS RF requirements for LP-WUS | CATT |
R4-2415204 | Further consideration on BS RF for Rel-19 LP-WUS | Huawei, HiSilicon |
R4-2415454 | BS RF requirement overview for LP-WUS | Ericsson |
R4-2415486 | BS RF requirements for low-power wake-up signal for NR | Nokia |
R4-2415783 | Further discussions on LP-WUS BS RF requirements | vivo |
R4-2415937 | Discussion on BS RF requirements for LP-WUS/WUR | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415549 | Reply LS on LP-WUS operation in IDLE/INACTIVE mode | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415007 | (NR_LPWUS-Core) Simulation assumption and results for LP-WUR | CMCC |
R4-2415065 | Simulation assumptions and results for LP-WUS/WUR | Xiaomi |
R4-2415143 | On simulation assumptions and results for LP-WUR | vivo |
R4-2415363 | Discussion on simulation assumptions and results for LP-WUS/WUR | LG Electronics Inc. |
R4-2415548 | On Simulation Assumptions and Results for LP-WUR RRM Core Requirements | Apple |
R4-2415864 | Simulation assumption and initial simulation results for LP-WUR measurement | Huawei, HiSilicon |
R4-2416021 | Simulation assumption on LP-WUR RRM measurement | Ericsson |
R4-2416022 | Simulation results on LP-WUR RRM measurement | Ericsson |
R4-2416290 | Discussion on LP-WUS Simulation assumptions and results | Nokia |
R4-2416509 | Simulation assumptions for R19 LP-WUS | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415008 | (NR_LPWUS-Core) Discussion on RRM impact of LP-WUR | CMCC |
R4-2415066 | Discussion on RRM core requirements for LP-WUS/WUR | Xiaomi |
R4-2415144 | Further consideration on RRM requirements for LP-WUR | vivo |
R4-2415185 | Discussion on RRM requirements for LP-WUS/WUR | CATT |
R4-2415364 | Discussion on RRM core requirements for LP-WUS/WUR | LG Electronics Inc. |
R4-2415541 | On RRM core requirements for LP-WUR | Apple |
R4-2415692 | RRM impact for Rel-19 LP-WUS/WUR | SAMSUNG R&D INSTITUTE JAPAN |
R4-2415738 | Discussion on RRM core requirements for LP-WUS/WUR | China Telecom |
R4-2415865 | Discussion on RRM requirements for LP-WUR | Huawei, HiSilicon |
R4-2415934 | Discussions on RRM core requirements for LP-WUSWUR | NTT DOCOMO, INC. |
R4-2416020 | Discussion on LP-WUR RRM requirement | Ericsson |
R4-2416123 | Discussion on RRM requirements for LP-WUS WUR | OPPO |
R4-2416291 | Discussion on LP-WUS RRM core requirements | Nokia |
R4-2416367 | Discussion on LP-WUS for core part | ZTECorporation,Sanechips |
R4-2416469 | RRM requirements for LP-WUR | Qualcomm Incorporated |
R4-2416510 | Discussion on the RRM core requirements for LP-WUS | MediaTek inc. |
TDoc | Title | Source |
---|---|---|
R4-2415235 | Topic summary for [112bis][131] NR_LPWUS_UERF | Moderator(Vivo) |
R4-2415664 | Topic summary for [112bis][217] NR_LPWUS | Moderator (vivo) |
R4-2416529 | Topic summary for [112bis][308] NR_LPWUS | Moderator (Huawei) |
R4-2416560 | Draft LS on NR NTN and GNSS concurrency | Qualcomm |
R4-2416566 | Way Forward for [112bis][308] NR_LPWUS | Huawei |
R4-2416589 | Way Forward for [112bis][308] NR_LPWUS | Huawei |
R4-2416861 | WF on RRM requirements for NR_LPWUS | Vivo |
R4-2416883 | Coffee break discussion minutes for NR_LPWUS | Vivo |
R4-2417112 | WF on UE RF requirements for LP-WUS | Vivo |
TDoc | Title | Source |
---|---|---|
R4-2414928 | Discussion on measurement enhancements for LTM | MediaTek Inc. |
R4-2414944 | RRM Core requirements on measurements related enhancements for LTM | China Telecom |
R4-2415074 | Discussion on RRM impact on measurements related enhancements for LTM | Xiaomi |
R4-2415155 | Discussion on measurements related enhancements for Rel-19 LTM | CATT |
R4-2415240 | Discussion on measurements related enhancements for LTM | CMCC |
R4-2415349 | Measurement enhancement for LTM | Qualcomm Incorporated |
R4-2415491 | Discussion on measurements related enhancements for LTM | Apple |
R4-2415521 | draft LS on intra-frequency/inter-frequency definition for CSI-RS based L1 measurement | Apple |
R4-2415539 | Discussion on RRM requirements for R19 LTM | vivo |
R4-2415553 | Discussion on RRM requirements of enhanced LTM | Samsung |
R4-2415841 | Discussion on Measurements related enhancements for LTM | Huawei, HiSilicon |
R4-2416124 | Discussion on measurements related enhancements for LTM | OPPO |
R4-2416292 | Discussion on Measurements related enhancements for LTM | Nokia |
R4-2416336 | Discussion on measurements enhancements for purpose of supporting LTM | Ericsson |
R4-2416384 | Discussion on NR mobility enhancements | ZTE Corporation, Sanechips |
R4-2416847 | Discussion on measurements related enhancements for LTM | Apple |
TDoc | Title | Source |
---|---|---|
R4-2414945 | RRM Core requirements on Conditional Intra-CU LTM | China Telecom |
R4-2415067 | Initial discussion on Conditional Intra-CU LTM for NR mobility enhancements Phase 4 | Xiaomi |
R4-2415147 | Initial discussion on Conditional Intra-CU LTM | vivo |
R4-2415156 | Discussion on conditional Intra-CU LTM for Rel-19 mobility enhancements | CATT |
R4-2415241 | Discussion on conditional LTM | CMCC |
R4-2415350 | Conditional LTM | Qualcomm Incorporated |
R4-2415492 | Discussion on conditional Intra-CU LTM | Apple |
R4-2415554 | Discussion on RRM requirements of conditional Intra-CU LTM | Samsung |
R4-2415604 | LS to RAN2 on conditional LTM cell switch | Apple |
R4-2415842 | Discussion on conditional Intra-CU LTM | Huawei, HiSilicon |
R4-2416015 | Discussion on Conditional LTM RRM requirements | Nokia |
R4-2416166 | Initial discussion on RRM core requirements for conditional LTM | Ericsson |
R4-2416385 | Discussion on Conditional Intra-CU LTM | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415665 | Topic summary for [112bis][218] NR_Mob_Ph4_Part1 | Moderator (Apple) |
R4-2415666 | Topic summary for [112bis][219] NR_Mob_Ph4_Part2 | Moderator (China Telecom) |
R4-2416862 | WF on RRM requirements for NR_Mob_Ph4_Part1 | Apple |
R4-2416863 | WF on RRM requirements for NR_Mob_Ph4_Part2 | China Telecom |
R4-2416875 | Ad-hoc minutes for NR_Mob_Ph4 | Apple |
TDoc | Title | Source |
---|---|---|
R4-2416204 | Draft LS response on UE assistance information | Ericsson |
R4-2416205 | Draft LS response on UE gaps and restrictions that are caused by RRM measurements | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2414919 | Discussion on gap skipping occasions mechanism - NR XR_Ph3 | InterDigital Canada |
R4-2415198 | Further discussion on RRM impacts for XR and reply LS | vivo |
R4-2415242 | Discussion on XR (eXtended Reality) for NR Phase 3 | CMCC |
R4-2415278 | Discussion on RRM Impacts for XR | Meta |
R4-2415493 | Discussion of RRM impact of XR for NR Phase 3 | Apple |
R4-2415494 | Reply LS on gaps/restrictions that are caused by RRM measurements | Apple |
R4-2415704 | Discussion on RRM aspects of R19 XR | ZTE Corporation, Sanechips |
R4-2415836 | Discussion on RRM requirements for Rel-19 XR | Huawei, HiSilicon |
R4-2415935 | Discussions on RRM core requirements for XR | NTT DOCOMO, INC. |
R4-2416125 | Discussion on RRM requirements for XR | OPPO |
R4-2416203 | On RRM core requirements for XR | Ericsson |
R4-2416454 | Discussion on RRM requirements for XR | MediaTek inc. |
R4-2416468 | Discussion on XR ph3 RRM requirements | Nokia |
R4-2416470 | RRM requirements for XR enhancements | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R4-2415667 | Topic summary for [112bis][220] NR_XR_Ph3 | Moderator (Nokia) |
R4-2416864 | WF on RRM requirements for NR_XR_Ph3 | Nokia |
R4-2416879 | Coffee break discussion minutes for [112bis][220] NR_XR_Ph3 | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2416068 | Reply LS on common TA in a regenerative payload scenario | Ericsson |
R4-2416256 | General issue for NTN RedCap | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415041 | Discussion on RedCap UE RF requirements with NR NTN operating in FR1-NTN bands | OPPO |
R4-2415057 | Discussion on RF requirement for redcap UE in FR1 NTN band. | Xiaomi |
R4-2415096 | Discussion on RF requirements for NTN RedCap UE | CATT |
R4-2415586 | UE RF requirement for NTN Redcap and eRedcap | Sony |
R4-2415609 | Discussion on NTN (e)Redcap UE RF requirements | Spreadtrum Communications |
R4-2415710 | RedCap NTN UEs | Nokia |
R4-2415741 | Discussion on Rel-19 NR-NTN RedCap UE RF requirements | Mediatek India Technology Pvt. |
R4-2416045 | Discussion on the potential specification updates due to simultaneous operation with GNSS | Huawei, HiSilicon |
R4-2416197 | Views on increasing MOP tolerance for NTN HD-FDD Redcap | NTT DOCOMO INC. |
R4-2416257 | RedCap UE RF impact | Ericsson |
R4-2416302 | On NR-NTN Ph3 UE RF | Samsung |
R4-2416462 | UE RF requirements for NR NTN RedCap | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415334 | On NTN simultaneous operation with GNSS | Apple |
R4-2416463 | NR NTN UL capacity enhancements | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415095 | Discussion on NTN SAN RF requirements | CATT |
R4-2416411 | Clarification on SAN architecture for the regenerative payload introduction | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415956 | Discussion on RRM requirements for NR NTN phase 3 | MediaTek inc. |
R4-2416520 | Discussion on the RAN2 LS Reply on Common TA in a Regenerative Payload Scenario | THALES |
TDoc | Title | Source |
---|---|---|
R4-2415009 | (NR_NTN_Ph3-Core) Discussion on the RRM requirement for Redcap over NTN | CMCC |
R4-2415068 | Discussion on (e)RedCap RRM requirements in NTN for NR Phase 3 | Xiaomi |
R4-2415149 | Discussion on RRM requirements on (e)RedCap for R19 NR NTN Phase 3 | vivo |
R4-2415157 | Discussion on (e)RedCap RRM requirements for Rel-19 NTN phase3 | CATT |
R4-2415351 | RedCap for NTN | Qualcomm Incorporated |
R4-2415542 | On R19 NTN (e)RedCap RRM requirements | Apple |
R4-2415555 | Discussion on RRM requirements of RedCap in Rel-19 NTN phase 3 | Samsung |
R4-2415867 | Discussion on RRM requirements for RedCap UE in NTN | Huawei, HiSilicon |
R4-2415881 | Discussion on RRM requirements for (e)RedCap in NTN | LG Electronics Inc. |
R4-2416076 | Discussion on RedCap RRM requirements for NTN for NR Phase 3 | Ericsson |
R4-2416126 | Discussion on (e)RedCap RRM requirements of R19 NR NTN | OPPO |
R4-2416189 | Adapting NGSO requirements for RedCap support in Rel-19 | Nokia |
R4-2416368 | Discussion on RRM requirements for RedCap NTN | ZTECorporation,Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415010 | (NR_NTN_Ph3-Core) Discussion on the RRM requirement for NTN phase3 | CMCC |
R4-2415011 | Reply LS on common TA in a regenerative payload scenario | CMCC |
R4-2415069 | Discussion on other RRM core requirements in NTN for NR Phase 3 | Xiaomi |
R4-2415148 | Discussion on potential RRM impacts on DL coverage and regenerative payload for R19 NR NTN Phase 3 | vivo |
R4-2415158 | Discussion on other RRM requirements for Rel-19 NTN phase3 | CATT |
R4-2415159 | Draft reply LS on common TA in a regenerative payload scenario | CATT |
R4-2415352 | Downlink coverage enhancement for NTN | Qualcomm Incorporated |
R4-2415543 | On R19 other NTN RRM requirements | Apple |
R4-2415556 | Discussion on RRM requirements of other aspects in Rel-19 NTN phase 3 | Samsung |
R4-2415868 | Discussion on other RRM requirements for Rel-19 NTN | Huawei, HiSilicon |
R4-2415882 | Discussion on RRM requirements for regerative payload NTN | LG Electronics Inc. |
R4-2416077 | Discussion on other RRM requirements for NTN for NR Phase 3 | Ericsson |
R4-2416127 | Discussion on other RRM requirements of R19 NR NTN | OPPO |
R4-2416190 | Discussing general RRM requirements for Rel-19 WI and LS Reply to RAN2 | Nokia |
R4-2416369 | Discussion on RRM requirements for regenerative NTN and downlink coverage enhancement | ZTECorporation,Sanechips |
R4-2416371 | Discussion on LS on common TA for regenerative NTN | ZTECorporation,Sanechips |
R4-2416372 | LS on common TA for regenerative NTN | ZTECorporation,Sanechips |
R4-2416912 | Reply LS on common TA in a regenerative payload scenario | CMCC |
R4-2416920 | Reply LS on common TA in a regenerative payload scenario | CMCC |
TDoc | Title | Source |
---|---|---|
R4-2415668 | Topic summary for [112bis][221] NR_NTN_Ph3_Part1 | Moderator (CATT) |
R4-2415669 | Topic summary for [112bis][222] NR_NTN_Ph3_Part2 | Moderator (Qualcomm) |
R4-2416530 | Topic summary for [112bis][309] NR_NTN_Ph3_General_SAN_RF | Moderator (Thales) |
R4-2416531 | Topic summary for [112bis][310] NR_NTN_Ph3_UE_RF | Moderator (Qualcomm) |
R4-2416561 | Way Forward for [112bis][310] NR_NTN_Ph3_UE_RF | Qualcomm |
R4-2416586 | Way Forward for [112bis][310] NR_NTN_Ph3_UE_RF | Qualcomm |
R4-2416865 | WF on RRM requirements for NR_NTN_Ph3_Part1 | CATT |
R4-2416866 | WF on RRM requirements for NR_NTN_Ph3_Part2 | Qualcomm |
R4-2416908 | Ad-hoc minutes for NR_NTN_Ph3 | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2416075 | Discussion on reply LS to RAN1 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415584 | OCC scheme on the RF requirements for IoT NTN | Sony |
R4-2415740 | Discussion on RF requirement impact for IoT NTN phase 3 | Mediatek India Technology Pvt. |
R4-2416464 | IoT NTN UL capacity enhancements | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415353 | Impact on RRM core requirement | Qualcomm Incorporated |
R4-2415829 | Discussion on RRM impacts for R19 IoT NTN | Huawei, HiSilicon |
R4-2415957 | Discussion on RRM requirements for IoT NTN phase 3 | MediaTek inc. |
R4-2416074 | Discussion on RRM requirements of Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 3 | Ericsson |
R4-2416188 | On the reply LS to RAN1 on contention based Msg3 transmission. | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2415670 | Topic summary for [112bis][223] IoT_NTN_Ph3 | Moderator (MediaTek) |
R4-2416536 | Topic summary for [112bis][315] IoT_NTN_Ph3 | Moderator (MediaTek) |
R4-2416565 | Way Forward for [112bis][315] IoT_NTN_Ph3 | MediaTek |
R4-2416867 | WF on RRM requirements for IoT_NTN_Ph3 | MediaTek |
R4-2416880 | Reply LS to RAN1 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | ZTE Corporation, Sanechips |
R4-2416914 | Reply LS to RAN1 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | ZTE Corporation, Sanechips |
R4-2416918 | Reply LS to RAN1 on UL synchronization for contention based Msg3 transmission without Msg1/Msg2 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415085 | LS on FR2-NTN frequency range for NTN | CATT |
R4-2415086 | CR for TS 38.101-5, Correction on FR2-NTN frequency range. | CATT |
R4-2415087 | CR for TS 38.108, Correction on FR2-NTN frequency range. | CATT |
R4-2415146 | Draft CR for update the note for NTN frequency range definition in RLM requirements | vivo |
R4-2415200 | Discussion on UE capability for multi-carrier enhancements | vivo |
R4-2415335 | Views on RAN1 LS on FR2-NTN inclusion to specifications | Apple |
R4-2415336 | [Draft] Reply LS on FR2-NTN inclusion to specifications | Apple |
R4-2415749 | Discussion on FR2-NTN inclusion to specifications | vivo |
R4-2415750 | Draft reply LS to RAN1 on FR2-NTN inclusion to specifications | vivo |
R4-2415751 | draft CR to 38.101-5 on the notes for NTN frequency range definition | vivo |
R4-2415752 | draft CR to 38.108 on the notes for NTN frequency range definition | vivo |
R4-2416060 | Discussion and Draft replied LS on FR2-NTN inclusion to the specifications from RAN1 LS | Huawei, HiSilicon |
R4-2416157 | LS Reply to RAN1 on FR2-NTN frequency range | Ericsson |
R4-2416158 | Draft CR to TS 38.101-5 – NTN frequency range and RAN1 LS | Ericsson |
R4-2416159 | Draft CR to TS 38.108 – NTN frequency range and RAN1 LS | Ericsson |
R4-2416187 | [NR_NTN_enh] LS Reply to R1-2407406 | Nokia |
R4-2416515 | Draft reply LS on the HIBS band plan | Huawei, HiSilicon |
R4-2416516 | Draft reply LS to ETSI MSG TFES on Tx spurious emissions: co-existence requirements limits for high frequency bands | Huawei, HiSilicon |
R4-2416557 | Reply LS on the HIBS band plan | Huawei, HiSilicon |
R4-2416588 | Reply LS to ETSI MSG TFES on Tx spurious emissions: co-existence requirements limits for high frequency bands | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R4-2415973 | On the topic BS transmitter co-existence spurious emissions requirement limits for bands in upper part of FR1 | Ericsson |
R4-2416582 | Way Forward on coexistence levels for upper FR1 | Ericsson |
TDoc | Title | Source |
---|---|---|
R4-2415236 | Topic summary for [112bis][132] NR_reply_LS_UE_RF | Moderator(Apple) |
R4-2415671 | Topic summary for [112bis][224] Reply_LS | Moderator (Apple) |
R4-2416878 | WF on UE report of incremental BWP switch delay for multi-carrier enhancements | NTT DOCOMO |
R4-2417185 | WF on FR2-NTN inclusion to specifications | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415237 | Topic summary for [112bis][133] UERF_Spec_Improvement | Moderator(Qualcomm) |
R4-2417182 | WF on UE RF spec improvement | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2414922 | On potential PRD scope for band combination | Huawei, HiSilicon |
R4-2415135 | On usage of PRD for specs improvement | CATT |
R4-2416104 | Considerations on PRD usage for band combination in RAN4 | ZTE Corporation, Sanechips |
R4-2416254 | RAN4 PRD input on Guidelines for harmonic MSD test points | Skyworks Solutions Inc., Qualcomm France, Nokia |
R4-2416379 | On RAN4 PRD scope for Release 19 and beyond | Skyworks Solutions Inc. |
R4-2416422 | draft PRD on rules guidelines and ways of working for introduction of band combinations | Ericsson, AT&T, Nokia |
TDoc | Title | Source |
---|---|---|
R4-2414923 | (NR_newRAT-Core) Replacement of dual with 2Tx | Huawei, HiSilicon, Ericsson, Qualcomm, Samsung |
R4-2414924 | (NR_newRAT-Core) Replacement of dual with 2Tx | Huawei, HiSilicon, Ericsson, Qualcomm, Samsung |
R4-2414925 | (NR_newRAT-Core) Replacement of dual with 2Tx | Huawei, HiSilicon, Ericsson, Qualcomm, Samsung |
R4-2415136 | CR to TS 38.101-1 on the usage of "Dual Tx " and "2Tx" | CATT |
R4-2415137 | CR to TS 38.101-1 on the usage of "Dual Tx " and "2Tx" | CATT |
R4-2415138 | CR to TS 38.101-1 on the usage of "Dual Tx " and "2Tx" | CATT |
R4-2415139 | CR to TS 38.101-1 on the usage of "Dual Tx " and "2Tx" | CATT |
R4-2416105 | Considerations on NOTEs usage for spec quality improvement | ZTE Corporation, Sanechips |
R4-2416106 | (TEI18) Draft CR for TS 38.101-1 on In-band emissions for NOTEs usage | ZTE Corporation, Sanechips |
R4-2416107 | (TEI18) Draft CR for TS 38.101-1 on reference sensitivity exceptions due to harmonic interference for NOTEs usage | ZTE Corporation, Sanechips |
R4-2416108 | (TEI18) Draft CR for TS 38.101-1 on three bands inter-band CA configurations for NOTEs usage | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2414926 | NOTE(s) handling in a table for future specifications | Huawei, HiSilicon |
R4-2415140 | Further discussion on notes usage in UE RF specifications | CATT |
R4-2416286 | Discussion on the improvement of table notes in RF specifications | Anritsu Limited |
TDoc | Title | Source |
---|---|---|
R4-2414927 | Miscellaneous proposals on spec quality improvement | Huawei, HiSilicon |
R4-2415141 | On potential table modifications for UE RF specs | CATT |
R4-2415392 | On UE RF specifications table improvement | Nokia |
R4-2415607 | Worthy Tips to Improve Spec Table Readability | Murata Manufacturing Co Ltd. |
R4-2415612 | draftCR to TS 38.101-1 on ?T_IB and ?R_IB tables | CATT |
R4-2415613 | draftCR to TS 38.101-1 on ?T_IB and ?R_IB tables | CATT |
R4-2415614 | draftCR to TS 38.101-1 on ?T_IB and ?R_IB tables | CATT |
R4-2415615 | draftCR to TS 38.101-1 on ?T_IB and ?R_IB tables | CATT |
R4-2415616 | draftCR to TS 38.101-3 on intra-band EN-DC configuration tables | CATT |
R4-2415617 | draftCR to TS 38.101-3 on intra-band EN-DC configuration tables | CATT |
R4-2415618 | draftCR to TS 38.101-3 on intra-band EN-DC configuration tables | CATT |
R4-2415619 | draftCR to TS 38.101-3 on intra-band EN-DC configuration tables | CATT |
R4-2416109 | Considerations on grouping rules for inter-band DC configuration tables | ZTE Corporation, Sanechips |
R4-2416110 | (DC_R18_2BLTE_1BNR_3DL2UL) Draft CR for TS 38.101-3 on 2L and 1N bands EN-DC configuration grouping | ZTE Corporation, Sanechips |
R4-2416111 | (DC_R18_xBLTE_1BNR_yDL2UL) Draft CR for TS 38.101-3 on (3-5)L and 1N bands EN-DC configuration grouping | ZTE Corporation, Sanechips |
R4-2416112 | (DC_R18_xBLTE_2BNR_yDL2UL) Draft CR for TS 38.101-3 on (1-4)L and 2N bands EN-DC configuration grouping | ZTE Corporation, Sanechips |
R4-2416113 | (DC_R18_xBLTE_yBNR_zDL2UL) Draft CR for TS 38.101-3 on (1-3)L and (3-5)N bands EN-DC configuration grouping | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R4-2415672 | Topic summary for [112bis][225] RRM_Spec_Improvement | Moderator (Apple) |
R4-2416868 | WF on RRM_Spec_Improvement | Apple |
R4-2416876 | Ad-hoc minutes for RRM_Spec_Improvement | Apple |
R4-2416917 | WF on RRM_Spec_Improvement | Apple |
TDoc | Title | Source |
---|---|---|
R4-2415438 | Hierarchy of indent | MediaTek inc. |
R4-2415546 | Draft CR for RRM Spec Improvement (section 1~6) | Apple |
R4-2415837 | Draft CR on specification improvement for 38.133 A.5 | Huawei, HiSilicon |
R4-2415884 | Draft CR on specification quality improvement for clause A.4 in TS38.133 | LG Electronics Inc. |
R4-2416206 | On RRM specification quality improvement – clean up CRs | Ericsson |
R4-2416208 | Draft CR 38133 RRM specification improvement for clauses 10 to A_3 | Ericsson |
R4-2416209 | Draft CR 38133 RRM specification improvement for clause A_6 | Ericsson |
R4-2416338 | Draft CR for Section 9 specification quality improvement | Nokia |
R4-2416452 | Draft CR on NR standalone tests with all NR cells in FR1 for RedCap | MediaTek inc. |
R4-2416472 | DraftCR 38.133 Editorial corrections to sections 7 and 8 | BeammWave AB |
TDoc | Title | Source |
---|---|---|
R4-2415199 | Further discussion on RRM spec quality improvement | vivo |
R4-2415606 | A specific example for improvements of Rel-19 RRM specifications | Qualcomm Technologies Ireland |
R4-2415883 | Discussion on specification quality improvement for TS38.133 | LG Electronics Inc. |
R4-2416207 | On RRM specification quality improvement – new issues | Ericsson |
R4-2416339 | Specification improvements in R19 timeframe | Nokia |
TDoc | Title | Source |
---|---|---|
R4-2414986 | RAN task R17 power class of 1UL CC with DL CA | OPPO |
R4-2415058 | Discussion on RAN task on HPUE with 1UL and DL CA | Xiaomi |
R4-2415142 | On Solution to enable HPUE maximum transmit power in downlink CA with single UL transmission | CATT |
R4-2415337 | On RAN task for CA power class support | Apple |
R4-2415463 | Discussion on NR CA power class for single configured UL | Huawei, HiSilicon |
R4-2415720 | Facilitating HPUE maximum transmit power in downlink CA with a single configured UL | Ericsson |
R4-2415721 | HPUE maximum transmit power in downlink CA with a single configured UL | Ericsson |
R4-2415722 | HPUE maximum transmit power in downlink CA with a single configured UL | Ericsson |
R4-2415801 | Discussions to enable maximum transmit power in downlink CA with single UL transmission | vivo |
R4-2415912 | Views on power class indication for HPUE DL CA with single UL transmission | ZTE Corporation, Sanechips |
R4-2416456 | draft CR to TS 38.101-1: DL CA HPUE | Qualcomm Inc. |
R4-2416457 | Support for HPUE with DL CA with single UL CC configured | Qualcomm Inc. |
TDoc | Title | Source |
---|---|---|
R4-2415263 | Revised WID: mmWave in NR: UE spurious emissions and EESS (Earth Exploration Satellite Service) protection | China Unicom |
R4-2415338 | Motivation for UL Tx switching for FR1 intra-band non-contiguous UL CA in Rel-19 | Apple |
R4-2415339 | Motivation for MSD reporting enhancement in Rel-19 | Apple |
R4-2415341 | Motivation for a new work item on low band carrier aggregation via switching in Rel-19 | Apple, Skyworks Solutions Inc., BT plc, TELUS, Bell Mobility, Anterix, Southern Linc, AT&T, Dish Network, Murata |
R4-2415342 | New WID on low band carrier aggregation via switching | Apple, Skyworks Solutions Inc., BT plc, TELUS, Bell Mobility, Anterix, Southern Linc, AT&T, Dish Network, Murata |
R4-2415437 | Evolution path of 3Tx UEs | MediaTek inc. |
R4-2415638 | Motivation on simplification of CA band combinations | Huawei,HiSilicon |
R4-2415639 | Draft WID for simplification of CA band combinations | Huawei,HiSilicon |
R4-2417203 | WF on RAN task on HPUE with 1UL and DL CA | Qualcomm |
TDoc | Title | Source |
---|---|---|
R4-2415389 | Progress update and next steps for CA framework overhaul | Nokia |
R4-2416393 | Discussion on the support of Microsoft Office formats | Rohde & Schwarz |
R4-2416592 | (reserved) | BDaT Session |
R4-2416594 | (reserved) | BDaT Session |
R4-2416595 | (reserved) | BDaT Session |
R4-2416596 | (reserved) | BDaT Session |
R4-2416597 | (reserved) | BDaT Session |
R4-2416598 | (reserved) | BDaT Session |
R4-2416599 | (reserved) | BDaT Session |
R4-2416600 | (reserved) | BDaT Session |
R4-2416601 | (reserved) | BDaT Session |
R4-2416602 | (reserved) | BDaT Session |
R4-2416603 | (reserved) | BDaT Session |
R4-2416604 | (reserved) | BDaT Session |
R4-2416605 | (reserved) | BDaT Session |
R4-2416606 | (reserved) | BDaT Session |
R4-2416607 | (reserved) | BDaT Session |
R4-2416608 | (reserved) | BDaT Session |
R4-2416609 | (reserved) | BDaT Session |
R4-2416610 | (reserved) | BDaT Session |
R4-2416611 | (reserved) | BDaT Session |
R4-2416612 | (reserved) | BDaT Session |
R4-2416613 | (reserved) | BDaT Session |
R4-2416614 | (reserved) | BDaT Session |
R4-2416615 | (reserved) | BDaT Session |
R4-2416616 | (reserved) | BDaT Session |
R4-2416617 | (reserved) | BDaT Session |
R4-2416618 | (reserved) | BDaT Session |
R4-2416619 | (reserved) | BDaT Session |
R4-2416620 | (reserved) | BDaT Session |
R4-2416621 | (reserved) | BDaT Session |
R4-2416622 | (reserved) | BDaT Session |
R4-2416623 | (reserved) | BDaT Session |
R4-2416624 | (reserved) | BDaT Session |
R4-2416625 | (reserved) | BDaT Session |
R4-2416626 | (reserved) | BDaT Session |
R4-2416627 | (reserved) | BDaT Session |
R4-2416628 | (reserved) | BDaT Session |
R4-2416629 | (reserved) | BDaT Session |
R4-2416630 | (reserved) | BDaT Session |
R4-2416631 | (reserved) | BDaT Session |
R4-2416632 | (reserved) | BDaT Session |
R4-2416633 | (reserved) | BDaT Session |
R4-2416634 | (reserved) | BDaT Session |
R4-2416635 | (reserved) | BDaT Session |
R4-2416636 | (reserved) | BDaT Session |
R4-2416637 | (reserved) | BDaT Session |
R4-2416638 | (reserved) | BDaT Session |
R4-2416639 | (reserved) | BDaT Session |
R4-2416640 | (reserved) | BDaT Session |
R4-2416641 | (reserved) | BDaT Session |
R4-2416642 | (reserved) | BDaT Session |
R4-2416643 | (reserved) | BDaT Session |
R4-2416644 | (reserved) | BDaT Session |
R4-2416645 | (reserved) | BDaT Session |
R4-2416646 | (reserved) | BDaT Session |
R4-2416647 | (reserved) | BDaT Session |
R4-2416648 | (reserved) | BDaT Session |
R4-2416649 | (reserved) | BDaT Session |
R4-2416650 | (reserved) | BDaT Session |
R4-2416651 | (reserved) | BDaT Session |
R4-2416652 | (reserved) | BDaT Session |
R4-2416653 | (reserved) | BDaT Session |
R4-2416654 | (reserved) | BDaT Session |
R4-2416655 | (reserved) | BDaT Session |
R4-2416656 | (reserved) | BDaT Session |
R4-2416657 | (reserved) | BDaT Session |
R4-2416658 | (reserved) | BDaT Session |
R4-2416659 | (reserved) | BDaT Session |
R4-2416660 | (reserved) | BDaT Session |
R4-2416661 | (reserved) | BDaT Session |
R4-2416662 | (reserved) | BDaT Session |
R4-2416663 | (reserved) | BDaT Session |
R4-2416664 | (reserved) | BDaT Session |
R4-2416665 | (reserved) | BDaT Session |
R4-2416666 | (reserved) | BDaT Session |
R4-2416667 | (reserved) | BDaT Session |
R4-2416668 | (reserved) | BDaT Session |
R4-2416669 | (reserved) | BDaT Session |
R4-2416670 | (reserved) | BDaT Session |
R4-2416671 | (reserved) | BDaT Session |
R4-2416672 | (reserved) | BDaT Session |
R4-2416673 | (reserved) | BDaT Session |
R4-2416674 | (reserved) | BDaT Session |
R4-2416675 | (reserved) | BDaT Session |
R4-2416676 | (reserved) | BDaT Session |
R4-2416677 | (reserved) | BDaT Session |
R4-2416678 | (reserved) | BDaT Session |
R4-2416679 | (reserved) | BDaT Session |
R4-2416680 | (reserved) | BDaT Session |
R4-2416681 | (reserved) | BDaT Session |
R4-2416682 | (reserved) | BDaT Session |
R4-2416683 | (reserved) | BDaT Session |
R4-2416684 | (reserved) | BDaT Session |
R4-2416685 | (reserved) | BDaT Session |
R4-2416686 | (reserved) | BDaT Session |
R4-2416687 | (reserved) | BDaT Session |
R4-2416688 | (reserved) | BDaT Session |
R4-2416689 | (reserved) | BDaT Session |
R4-2416690 | (reserved) | BDaT Session |
R4-2416691 | (reserved) | BDaT Session |
R4-2416692 | (reserved) | BDaT Session |
R4-2416693 | (reserved) | BDaT Session |
R4-2416694 | (reserved) | BDaT Session |
R4-2416695 | (reserved) | BDaT Session |
R4-2416696 | (reserved) | BDaT Session |
R4-2416697 | (reserved) | BDaT Session |
R4-2416698 | (reserved) | BDaT Session |
R4-2416699 | (reserved) | BDaT Session |
R4-2416700 | (reserved) | BDaT Session |
R4-2416701 | (reserved) | BDaT Session |
R4-2416702 | (reserved) | BDaT Session |
R4-2416703 | (reserved) | BDaT Session |
R4-2416704 | (reserved) | BDaT Session |
R4-2416705 | (reserved) | BDaT Session |
R4-2416706 | (reserved) | BDaT Session |
R4-2416707 | (reserved) | BDaT Session |
R4-2416708 | (reserved) | BDaT Session |
R4-2416709 | (reserved) | BDaT Session |
R4-2416710 | (reserved) | BDaT Session |
R4-2416711 | (reserved) | BDaT Session |
R4-2416712 | (reserved) | BDaT Session |
R4-2416713 | (reserved) | BDaT Session |
R4-2416714 | (reserved) | BDaT Session |
R4-2416715 | (reserved) | BDaT Session |
R4-2416716 | (reserved) | BDaT Session |
R4-2416717 | (reserved) | BDaT Session |
R4-2416718 | (reserved) | BDaT Session |
R4-2416719 | (reserved) | BDaT Session |
R4-2416720 | (reserved) | BDaT Session |
R4-2416721 | (reserved) | BDaT Session |
R4-2416722 | (reserved) | BDaT Session |
R4-2416723 | (reserved) | BDaT Session |
R4-2416724 | (reserved) | BDaT Session |
R4-2416725 | (reserved) | BDaT Session |
R4-2416726 | (reserved) | BDaT Session |
R4-2416727 | (reserved) | BDaT Session |
R4-2416728 | (reserved) | BDaT Session |
R4-2416729 | (reserved) | BDaT Session |
R4-2416730 | (reserved) | BDaT Session |
R4-2416731 | (reserved) | BDaT Session |
R4-2416732 | (reserved) | BDaT Session |
R4-2416733 | (reserved) | BDaT Session |
R4-2416734 | (reserved) | BDaT Session |
R4-2416735 | (reserved) | BDaT Session |
R4-2416736 | (reserved) | BDaT Session |
R4-2416737 | (reserved) | BDaT Session |
R4-2416738 | (reserved) | BDaT Session |
R4-2416739 | (reserved) | BDaT Session |
R4-2416740 | (reserved) | BDaT Session |
R4-2416741 | (reserved) | BDaT Session |
R4-2416742 | (reserved) | BDaT Session |
R4-2416743 | (reserved) | BDaT Session |
R4-2416744 | (reserved) | BDaT Session |
R4-2416745 | (reserved) | BDaT Session |
R4-2416746 | (reserved) | BDaT Session |
R4-2416747 | (reserved) | BDaT Session |
R4-2416748 | (reserved) | BDaT Session |
R4-2416749 | (reserved) | BDaT Session |
R4-2416750 | (reserved) | BDaT Session |
R4-2416751 | (reserved) | BDaT Session |
R4-2416752 | (reserved) | BDaT Session |
R4-2416753 | (reserved) | BDaT Session |
R4-2416754 | (reserved) | BDaT Session |
R4-2416755 | (reserved) | BDaT Session |
R4-2416756 | (reserved) | BDaT Session |
R4-2416757 | (reserved) | BDaT Session |
R4-2416758 | (reserved) | BDaT Session |
R4-2416759 | (reserved) | BDaT Session |
R4-2416760 | (reserved) | BDaT Session |
R4-2416761 | (reserved) | BDaT Session |
R4-2416762 | (reserved) | BDaT Session |
R4-2416763 | (reserved) | BDaT Session |
R4-2416764 | (reserved) | BDaT Session |
R4-2416765 | (reserved) | BDaT Session |
R4-2416766 | (reserved) | BDaT Session |
R4-2416767 | (reserved) | BDaT Session |
R4-2416768 | (reserved) | BDaT Session |
R4-2416769 | (reserved) | BDaT Session |
R4-2416770 | (reserved) | BDaT Session |
R4-2416771 | (reserved) | BDaT Session |
R4-2416772 | (reserved) | BDaT Session |
R4-2416773 | (reserved) | BDaT Session |
R4-2416774 | (reserved) | BDaT Session |
R4-2416775 | (reserved) | BDaT Session |
R4-2416776 | (reserved) | BDaT Session |
R4-2416777 | (reserved) | BDaT Session |
R4-2416778 | (reserved) | BDaT Session |
R4-2416779 | (reserved) | BDaT Session |
R4-2416780 | (reserved) | BDaT Session |
R4-2416781 | (reserved) | BDaT Session |
R4-2416782 | (reserved) | BDaT Session |
R4-2416783 | (reserved) | BDaT Session |
R4-2416784 | (reserved) | BDaT Session |
R4-2416785 | (reserved) | BDaT Session |
R4-2416786 | (reserved) | BDaT Session |
R4-2416787 | (reserved) | BDaT Session |
R4-2416788 | (reserved) | BDaT Session |
R4-2416789 | (reserved) | BDaT Session |
R4-2416790 | (reserved) | BDaT Session |
R4-2416791 | (reserved) | BDaT Session |
R4-2416792 | (reserved) | BDaT Session |
R4-2416793 | (reserved) | BDaT Session |
R4-2416794 | (reserved) | BDaT Session |
R4-2416795 | (reserved) | BDaT Session |
R4-2416796 | (reserved) | BDaT Session |
R4-2416797 | (reserved) | BDaT Session |
R4-2416798 | (reserved) | BDaT Session |
R4-2416799 | (reserved) | BDaT Session |
R4-2416800 | (reserved) | BDaT Session |
R4-2416801 | (reserved) | BDaT Session |
R4-2416802 | (reserved) | BDaT Session |
R4-2416803 | (reserved) | BDaT Session |
R4-2416804 | (reserved) | BDaT Session |
R4-2416805 | (reserved) | BDaT Session |
R4-2416806 | (reserved) | BDaT Session |
R4-2416807 | (reserved) | BDaT Session |
R4-2416808 | (reserved) | BDaT Session |
R4-2416809 | (reserved) | BDaT Session |
R4-2416810 | (reserved) | BDaT Session |
R4-2416811 | (reserved) | BDaT Session |
R4-2416812 | (reserved) | BDaT Session |
R4-2416813 | (reserved) | BDaT Session |
R4-2416814 | (reserved) | BDaT Session |
R4-2416815 | (reserved) | BDaT Session |
R4-2416816 | (reserved) | BDaT Session |
R4-2416817 | (reserved) | BDaT Session |
R4-2416818 | (reserved) | BDaT Session |
R4-2416819 | (reserved) | BDaT Session |
R4-2416820 | (reserved) | BDaT Session |
R4-2416821 | (reserved) | BDaT Session |
R4-2416822 | (reserved) | BDaT Session |
R4-2416823 | (reserved) | BDaT Session |
R4-2416824 | (reserved) | BDaT Session |
R4-2416825 | (reserved) | BDaT Session |
R4-2416826 | (reserved) | BDaT Session |
R4-2416827 | (reserved) | BDaT Session |
R4-2416828 | (reserved) | BDaT Session |
R4-2416829 | (reserved) | BDaT Session |
R4-2416830 | (reserved) | BDaT Session |
R4-2416831 | (reserved) | BDaT Session |
R4-2416832 | (reserved) | BDaT Session |
R4-2416833 | (reserved) | BDaT Session |
R4-2416834 | (reserved) | BDaT Session |
R4-2416835 | (reserved) | BDaT Session |
R4-2416836 | (reserved) | BDaT Session |
R4-2416837 | (reserved) | BDaT Session |
R4-2416838 | (reserved) | BDaT Session |
R4-2416839 | (reserved) | BDaT Session |
R4-2416840 | (reserved) | BDaT Session |
R4-2416841 | (reserved) | BDaT Session |
R4-2416842 | (reserved) | BDaT Session |
R4-2416843 | (reserved) | BDaT Session |
R4-2416844 | (reserved) | BDaT Session |
R4-2416845 | (reserved) | BDaT Session |
R4-2416846 | (reserved) | BDaT Session |
R4-2417353 | IRIS² - The New EU Programme Providing Secure Communications Via Satellites | ESA |
TDoc | Title | Source |
---|---|---|
R4-2416922 | (reserved) | RRM Session |
R4-2416923 | (reserved) | RRM Session |
R4-2416924 | (reserved) | RRM Session |
R4-2416925 | (reserved) | RRM Session |
R4-2416926 | (reserved) | RRM Session |
R4-2416927 | (reserved) | RRM Session |
R4-2416928 | (reserved) | RRM Session |
R4-2416929 | (reserved) | RRM Session |
R4-2416930 | (reserved) | RRM Session |
R4-2416931 | (reserved) | RRM Session |
R4-2416932 | (reserved) | RRM Session |
R4-2416933 | (reserved) | RRM Session |
R4-2416934 | (reserved) | RRM Session |
R4-2416935 | (reserved) | RRM Session |
R4-2416936 | (reserved) | RRM Session |
R4-2416937 | (reserved) | RRM Session |
R4-2416938 | (reserved) | RRM Session |
R4-2416939 | (reserved) | RRM Session |
R4-2416940 | (reserved) | RRM Session |
R4-2416941 | (reserved) | RRM Session |
R4-2416942 | (reserved) | RRM Session |
R4-2416943 | (reserved) | RRM Session |
R4-2416944 | (reserved) | RRM Session |
R4-2416945 | (reserved) | RRM Session |
R4-2416946 | (reserved) | RRM Session |
R4-2416947 | (reserved) | RRM Session |
R4-2416948 | (reserved) | RRM Session |
R4-2416949 | (reserved) | RRM Session |
R4-2416950 | (reserved) | RRM Session |
R4-2416951 | (reserved) | RRM Session |
R4-2416952 | (reserved) | RRM Session |
R4-2416953 | (reserved) | RRM Session |
R4-2416954 | (reserved) | RRM Session |
R4-2416955 | (reserved) | RRM Session |
R4-2416956 | (reserved) | RRM Session |
R4-2416957 | (reserved) | RRM Session |
R4-2416958 | (reserved) | RRM Session |
R4-2416959 | (reserved) | RRM Session |
R4-2416960 | (reserved) | RRM Session |
R4-2416961 | (reserved) | RRM Session |
R4-2416962 | (reserved) | RRM Session |
R4-2416963 | (reserved) | RRM Session |
R4-2416964 | (reserved) | RRM Session |
R4-2416965 | (reserved) | RRM Session |
R4-2416966 | (reserved) | RRM Session |
R4-2416967 | (reserved) | RRM Session |
R4-2416968 | (reserved) | RRM Session |
R4-2416969 | (reserved) | RRM Session |
R4-2416970 | (reserved) | RRM Session |
R4-2416971 | (reserved) | RRM Session |
R4-2416972 | (reserved) | RRM Session |
R4-2416973 | (reserved) | RRM Session |
R4-2416974 | (reserved) | RRM Session |
R4-2416975 | (reserved) | RRM Session |
R4-2416976 | (reserved) | RRM Session |
R4-2416977 | (reserved) | RRM Session |
R4-2416978 | (reserved) | RRM Session |
R4-2416979 | (reserved) | RRM Session |
R4-2416980 | (reserved) | RRM Session |
R4-2416981 | (reserved) | RRM Session |
R4-2416982 | (reserved) | RRM Session |
R4-2416983 | (reserved) | RRM Session |
R4-2416984 | (reserved) | RRM Session |
R4-2416985 | (reserved) | RRM Session |
R4-2416986 | (reserved) | RRM Session |
R4-2416987 | (reserved) | RRM Session |
R4-2416988 | (reserved) | RRM Session |
R4-2416989 | (reserved) | RRM Session |
R4-2416990 | (reserved) | RRM Session |
R4-2416991 | (reserved) | RRM Session |
R4-2416992 | (reserved) | RRM Session |
R4-2416993 | (reserved) | RRM Session |
R4-2416994 | (reserved) | RRM Session |
R4-2416995 | (reserved) | RRM Session |
R4-2416996 | (reserved) | RRM Session |
R4-2416997 | (reserved) | RRM Session |
R4-2416998 | (reserved) | RRM Session |
R4-2416999 | (reserved) | RRM Session |
R4-2417000 | (reserved) | RRM Session |
R4-2417001 | (reserved) | RRM Session |
R4-2417002 | (reserved) | RRM Session |
R4-2417003 | (reserved) | RRM Session |
R4-2417004 | (reserved) | RRM Session |
R4-2417005 | (reserved) | RRM Session |
R4-2417006 | (reserved) | RRM Session |
R4-2417007 | (reserved) | RRM Session |
R4-2417008 | (reserved) | RRM Session |
R4-2417009 | (reserved) | RRM Session |
R4-2417010 | (reserved) | RRM Session |
R4-2417011 | (reserved) | RRM Session |
R4-2417012 | (reserved) | RRM Session |
R4-2417013 | (reserved) | RRM Session |
R4-2417014 | (reserved) | RRM Session |
R4-2417015 | (reserved) | RRM Session |
R4-2417016 | (reserved) | RRM Session |
R4-2417017 | (reserved) | RRM Session |
R4-2417018 | (reserved) | RRM Session |
R4-2417019 | (reserved) | RRM Session |
R4-2417020 | (reserved) | RRM Session |
R4-2417021 | (reserved) | RRM Session |
R4-2417022 | (reserved) | RRM Session |
R4-2417023 | (reserved) | RRM Session |
R4-2417024 | (reserved) | RRM Session |
R4-2417025 | (reserved) | RRM Session |
R4-2417026 | (reserved) | RRM Session |
R4-2417027 | (reserved) | RRM Session |
R4-2417028 | (reserved) | RRM Session |
R4-2417029 | (reserved) | RRM Session |
R4-2417030 | (reserved) | RRM Session |
R4-2417031 | (reserved) | RRM Session |
R4-2417032 | (reserved) | RRM Session |
R4-2417033 | (reserved) | RRM Session |
R4-2417034 | (reserved) | RRM Session |
R4-2417035 | (reserved) | RRM Session |
R4-2417036 | (reserved) | RRM Session |
R4-2417037 | (reserved) | RRM Session |
R4-2417038 | (reserved) | RRM Session |
R4-2417039 | (reserved) | RRM Session |
R4-2417040 | (reserved) | RRM Session |
R4-2417041 | (reserved) | RRM Session |
R4-2417042 | (reserved) | RRM Session |
R4-2417043 | (reserved) | RRM Session |
R4-2417044 | (reserved) | RRM Session |
R4-2417045 | (reserved) | RRM Session |
R4-2417046 | (reserved) | RRM Session |
R4-2417047 | (reserved) | RRM Session |
R4-2417048 | (reserved) | RRM Session |
R4-2417049 | (reserved) | RRM Session |
R4-2417050 | (reserved) | RRM Session |
R4-2417051 | (reserved) | RRM Session |
R4-2417052 | (reserved) | RRM Session |
R4-2417053 | (reserved) | RRM Session |
R4-2417213 | (reserved) | Main Session |
R4-2417214 | (reserved) | Main Session |
R4-2417215 | (reserved) | Main Session |
R4-2417216 | (reserved) | Main Session |
R4-2417217 | (reserved) | Main Session |
R4-2417218 | (reserved) | Main Session |
R4-2417219 | (reserved) | Main Session |
R4-2417220 | (reserved) | Main Session |
R4-2417221 | (reserved) | Main Session |
R4-2417222 | (reserved) | Main Session |
R4-2417223 | (reserved) | Main Session |
R4-2417224 | (reserved) | Main Session |
R4-2417225 | (reserved) | Main Session |
R4-2417226 | (reserved) | Main Session |
R4-2417227 | (reserved) | Main Session |
R4-2417228 | (reserved) | Main Session |
R4-2417229 | (reserved) | Main Session |
R4-2417230 | (reserved) | Main Session |
R4-2417231 | (reserved) | Main Session |
R4-2417232 | (reserved) | Main Session |
R4-2417233 | (reserved) | Main Session |
R4-2417234 | (reserved) | Main Session |
R4-2417235 | (reserved) | Main Session |
R4-2417236 | (reserved) | Main Session |
R4-2417237 | (reserved) | Main Session |
R4-2417238 | (reserved) | Main Session |
R4-2417239 | (reserved) | Main Session |
R4-2417240 | (reserved) | Main Session |
R4-2417241 | (reserved) | Main Session |
R4-2417242 | (reserved) | Main Session |
R4-2417243 | (reserved) | Main Session |
R4-2417244 | (reserved) | Main Session |
R4-2417245 | (reserved) | Main Session |
R4-2417246 | (reserved) | Main Session |
R4-2417247 | (reserved) | Main Session |
R4-2417248 | (reserved) | Main Session |
R4-2417249 | (reserved) | Main Session |
R4-2417250 | (reserved) | Main Session |
R4-2417251 | (reserved) | Main Session |
R4-2417252 | (reserved) | Main Session |
R4-2417253 | (reserved) | Main Session |
R4-2417254 | (reserved) | Main Session |
R4-2417255 | (reserved) | Main Session |
R4-2417256 | (reserved) | Main Session |
R4-2417257 | (reserved) | Main Session |
R4-2417258 | (reserved) | Main Session |
R4-2417259 | (reserved) | Main Session |
R4-2417260 | (reserved) | Main Session |
R4-2417261 | (reserved) | Main Session |
R4-2417262 | (reserved) | Main Session |
R4-2417263 | (reserved) | Main Session |
R4-2417264 | (reserved) | Main Session |
R4-2417265 | (reserved) | Main Session |
R4-2417266 | (reserved) | Main Session |
R4-2417267 | (reserved) | Main Session |
R4-2417268 | (reserved) | Main Session |
R4-2417269 | (reserved) | Main Session |
R4-2417270 | (reserved) | Main Session |
R4-2417271 | (reserved) | Main Session |
R4-2417272 | (reserved) | Main Session |
R4-2417273 | (reserved) | Main Session |
R4-2417274 | (reserved) | Main Session |
R4-2417275 | (reserved) | Main Session |
R4-2417276 | (reserved) | Main Session |
R4-2417277 | (reserved) | Main Session |
R4-2417278 | (reserved) | Main Session |
R4-2417279 | (reserved) | Main Session |
R4-2417280 | (reserved) | Main Session |
R4-2417281 | (reserved) | Main Session |
R4-2417282 | (reserved) | Main Session |
R4-2417283 | (reserved) | Main Session |
R4-2417284 | (reserved) | Main Session |
R4-2417285 | (reserved) | Main Session |
R4-2417286 | (reserved) | Main Session |
R4-2417287 | (reserved) | Main Session |
R4-2417288 | (reserved) | Main Session |
R4-2417289 | (reserved) | Main Session |
R4-2417290 | (reserved) | Main Session |
R4-2417291 | (reserved) | Main Session |
R4-2417292 | (reserved) | Main Session |
R4-2417293 | (reserved) | Main Session |
R4-2417294 | (reserved) | Main Session |
R4-2417295 | (reserved) | Main Session |
R4-2417296 | (reserved) | Main Session |
R4-2417297 | (reserved) | Main Session |
R4-2417298 | (reserved) | Main Session |
R4-2417299 | (reserved) | Main Session |
R4-2417300 | (reserved) | Main Session |
R4-2417301 | (reserved) | Main Session |
R4-2417302 | (reserved) | Main Session |
R4-2417303 | (reserved) | Main Session |
R4-2417304 | (reserved) | Main Session |
R4-2417305 | (reserved) | Main Session |
R4-2417306 | (reserved) | Main Session |
R4-2417307 | (reserved) | Main Session |
R4-2417308 | (reserved) | Main Session |
R4-2417309 | (reserved) | Main Session |
R4-2417310 | (reserved) | Main Session |
R4-2417311 | (reserved) | Main Session |
R4-2417312 | (reserved) | Main Session |
R4-2417313 | (reserved) | Main Session |
R4-2417314 | (reserved) | Main Session |
R4-2417315 | (reserved) | Main Session |
R4-2417316 | (reserved) | Main Session |
R4-2417317 | (reserved) | Main Session |
R4-2417318 | (reserved) | Main Session |
R4-2417319 | (reserved) | Main Session |
R4-2417320 | (reserved) | Main Session |
R4-2417321 | (reserved) | Main Session |
R4-2417322 | (reserved) | Main Session |
R4-2417323 | (reserved) | Main Session |
R4-2417324 | (reserved) | Main Session |
R4-2417325 | (reserved) | Main Session |
R4-2417326 | (reserved) | Main Session |
R4-2417327 | (reserved) | Main Session |
R4-2417328 | (reserved) | Main Session |
R4-2417329 | (reserved) | Main Session |
R4-2417330 | (reserved) | Main Session |
R4-2417331 | (reserved) | Main Session |
R4-2417332 | (reserved) | Main Session |
R4-2417333 | (reserved) | Main Session |
R4-2417334 | (reserved) | Main Session |
R4-2417335 | (reserved) | Main Session |
R4-2417336 | (reserved) | Main Session |
R4-2417337 | (reserved) | Main Session |
R4-2417338 | (reserved) | Main Session |
R4-2417339 | (reserved) | Main Session |
R4-2417340 | (reserved) | Main Session |
R4-2417341 | (reserved) | Main Session |
R4-2417342 | (reserved) | Main Session |
R4-2417343 | (reserved) | Main Session |
R4-2417344 | (reserved) | Main Session |
R4-2417345 | (reserved) | Main Session |
R4-2417346 | (reserved) | Main Session |
R4-2417347 | (reserved) | Main Session |
R4-2417348 | (reserved) | Main Session |
R4-2417349 | (reserved) | Main Session |
R4-2417350 | (reserved) | Main Session |
R4-2417351 | (reserved) | Main Session |