TDoc | Title | Source |
---|---|---|
R2-2004300 | Agenda for RAN2#110-e | Chairman |
TDoc | Title | Source |
---|---|---|
R2-2004301 | RAN2#109bis-e Meeting Report | MCC |
TDoc | Title | Source |
---|---|---|
R2-2004462 | RAN2#110-e Meeting Guidelines | ETSI MCC |
R2-2005871 | Signalling UE capability Identity | R3 (Huawei) |
R2-2005872 | Baseline CR for introducing Rel-16 NR mobility enhancement | R3 (Intel Corporation) |
R2-2005873 | NRIIOT Higher Layer Multi-Connectivity | R3 (CATT, Ericsson, Samsung, Huawei, ZTE, Nokia, Nokia Shanghai Bell) |
R2-2005874 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | R3 (ZTE, CATT, NTT DOCOMO, INC., Google, China Telecom) |
R2-2005875 | Addition of SON features | R3 (Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Ericsson, Qualcomm Incorporated, LG Electronics, NTT DOCOMO) |
R2-2005876 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | R3 (Intel Corporation) |
R2-2005877 | Introduction of Non Public Networks | R3 (Nokia, Nokia Shanghai Bell, China Telecom, Huawei, ZTE) |
R2-2005878 | Supporting of RACS for EN-DC and MR-DC | R3 (CATT, ZTE, Huawei, Nokia, Nokia Shanghai Bell) |
R2-2005879 | Mapping of Uplink Traffic to Backhaul RLC Channels | R3 (Ericsson) |
R2-2005986 | TS37.340 Stage2 Introduction of Rel-16 Mobility Enhancement in MR-DC | ZTE Corporation, CATT, NTT DOCOMO, INC., Google, China Telecom, Ericsson, Intel Corporation |
R2-2005987 | Baseline CR for introducing Rel-16 NR mobility enhancement | R3 (Intel Corporation, Ericsson, Huawei) |
R2-2005988 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | R3 (Intel Corporation, Ericsson) |
R2-2005989 | Introduction of Non Public Networks | R3 (Nokia, Nokia Shanghai Bell, China Telecom, Huawei, ZTE) |
R2-2006010 | Report R2 110e prep Web Conference | RAN2 Chairman |
R2-2006395 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | R3 (Nokia, Nokia Shanghai Bell, Ericsson) |
R2-2006396 | Global Cell Identities and Global NG-RAN Node Identities when NR access is shared | R3 (Nokia, Nokia Shanghai Bell, Ericsson) |
R2-2006397 | Correction of connected en-gNB Identifier | R3 (Huawei, Nokia, Nokia Shanghai Bell) |
R2-2006398 | Correction of connected en-gNB Identifier | R3 (Huawei, Nokia, Nokia Shanghai Bell) |
R2-2006399 | Support for Alternative QoS profiles | R3 (Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC.) |
R2-2006400 | Support of inter-RAT handover in response to MCGFailureInformation | R3 (Nokia, Nokia Shanghai Bell, Huawei) |
R2-2006401 | TS38.300 Introduction of Inter-(en)gNB CSI-RS Based Mobility | R3 (ZTE, China Telecom) |
R2-2006402 | Correction for Network Sharing | R3 (Ericsson) |
R2-2006403 | Correction for Network Sharing | R3 (Ericsson) |
R2-2006404 | CR 36.300 for support of WUS | R3 (ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Huawei) |
R2-2006405 | Correction of NAS NON Delivery | R3 (Nokia, Nokia Shanghai Bell, Orange) |
R2-2006406 | Correction of NAS NON Delivery | R3 (Nokia, Nokia Shanghai Bell, Orange) |
R2-2006407 | CR 36.300 for support of WUS | R3 (ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Huawei) |
R2-2006442 | Support for Alternative QoS profiles | R3 (Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE, Samsung, LG Electronics, InterDigital, NTT DOCOMO INC.) |
TDoc | Title | Source |
---|---|---|
R2-2004305 | Reply LS on UAV positioning (S1-201089; contact: InterDigital) | SA1 |
R2-2004306 | LS on 5GC assisted cell selection for accessing network slice (S2-2001728; contact: ZTE) | SA2 |
R2-2004307 | Response LS on the “LS OUT on Location of UEs and associated key issues” (S3i200056; contact: Rogers) | SA3-LI |
R2-2004310 | LS on Requirements on positioning for UAS (S6-200269; contact: InterDigital) | SA6 |
R2-2004311 | Reply LS to extend the scope of eV2X (SP-191379; contact: Telecom Italia) | SA |
R2-2004330 | Response to 5GC assisted cell selection for accessing network slice (R3-202558; contact: ZTE) | RAN3 |
R2-2004335 | Response LS on the “LS out on Location of UEs and associated key issues” (R3-202824; contact: Thales)) | RAN3 |
R2-2004380 | LS on updated Rel-16 LTE and NR parameter lists (R1-2003191; contact: Qualcomm) | RAN1 |
R2-2005701 | draft Reply LS on 5GC assisted cell selection for accessing network slice | ZTE Corporation, Sanechips |
R2-2005740 | LS on 5GC assisted cell selection for accessing network slice (S1-202264; contact: ZTE) | SA1 |
R2-2005994 | Reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN (S1-202294; contact: Nokia) | SA1 |
R2-2006007 | Reply LS on GSMA NG.116 Attribute Area of service and impact on PLMN (S1-202294; contact: Nokia) | SA1 |
R2-2006040 | LS Reply on QoE Measurement Collection (S4-200962; contact: Ericsson) | SA4 |
R2-2006241 | Reply LS on energy efficiency (S5-203016; contact: Orange) | SA5 |
R2-2006361 | LS on updated Rel-16 NR parameter lists (R1-2005051; contact: Qualcomm) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2005025 | Clarification on RLC UM SN size for NB-IoT | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004317 | Reply LS on assistance indication for WUS (S2-2003217; contact: Qualcomm) | SA2 |
R2-2004812 | Allow sending Rel-14 AS RAI when no UL grant | MediaTek Inc. |
R2-2004816 | Allow sending Rel-14 AS RAI when no UL grant | MediaTek Inc. |
R2-2004819 | Allow sending Rel-14 AS RAI when no UL grant | MediaTek Inc. |
R2-2004828 | Allow sending Rel-14 AS RAI when no UL grant | MediaTek Inc. |
R2-2005012 | Discussion on eNB knowledge of UE Radio paging capability when UE is in RRC_CONNECTED mode | Huawei, HiSilicon |
R2-2005013 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005014 | System support for (Group) Wake Up Signal | Huawei, HiSilicon |
R2-2005015 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005016 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005017 | System support for Group Wake Up Signal | Huawei, HiSilicon |
R2-2005026 | Clarification on PHR report for power class 14dBm UE | Huawei, HiSilicon |
R2-2005027 | Clarification on PHR report for power class 14dBm UE | Huawei, HiSilicon |
R2-2005199 | [draft] Reply LS on assistance indication for WUS | Qualcomm Incorporated |
R2-2005200 | Restrict WUS to last used cell | Qualcomm Incorporated |
R2-2005201 | Restrict WUS to last used cell | Qualcomm Incorporated |
R2-2005202 | Restrict WUS to last used cell | Qualcomm Incorporated |
R2-2005203 | Restrict WUS to last used cell | Qualcomm Incorporated |
R2-2005588 | Clarification for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc. |
R2-2005590 | Clarification for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc |
R2-2005928 | Report of \t[AT110-e][308][NBIOT] R14 Allow sending Rel-14 AS RAI when no UL grant (Mediatek) | MediaTek |
R2-2005929 | Report of [AT110-e][309][NBIOT] R15 Clarification on PHR report for power class 14dBm UE (Huawei) | Huawei |
R2-2005930 | Report of [AT110-e][310][NBIOT] R15 Clarification for dedicated SR with HARQ-\nACK (ZTE) | ZTE |
R2-2005931 | [DRAFT] Reply LS on assistance indication for WUS | Qualcomm Incorporated |
R2-2005932 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005933 | System support for (Group) Wake Up Signal | Huawei, HiSilicon |
R2-2005934 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005935 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2005939 | Reply LS on assistance indication for WUS | RAN2 |
R2-2005940 | Clarification for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc. |
R2-2005941 | Clarification for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc |
R2-2005943 | Clarification on PHR report for power class 14dBm UE | Huawei, HiSilicon |
R2-2005944 | Clarification on PHR report for power class 14dBm UE | Huawei, HiSilicon |
R2-2005947 | Draft LS on system support for WUS | Qualcomm |
R2-2005985 | LS on system support for WUS | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2005081 | Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC | Huawei, HiSilicon |
R2-2005082 | Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC | Huawei, HiSilicon |
R2-2005591 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
R2-2005596 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
R2-2005602 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
R2-2005609 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
TDoc | Title | Source |
---|---|---|
R2-2004627 | Relaxed serving cell measurement for UEs using WUS | Qualcomm Technologies Int |
R2-2004634 | Relaxed serving cell measurement for UEs using WUS | Qualcomm Technologies Int |
R2-2004654 | [Draft] LS on implementation of relaxed serving cell measurement by Rel-15 UEs | Qualcomm Technologies Int |
R2-2005010 | Clarification for CP EDT | Huawei, HiSilicon |
R2-2005011 | Clarification for CP EDT | Huawei, HiSilicon |
R2-2005018 | Porting back corrections made during Rel-16 ASN.1 review | Huawei, HiSilicon |
R2-2005821 | Report for [AT110-e][401][eMTC] R15 Relaxed serving cell measurement for UEs using WUS (Qualcomm) | Qualcomm |
R2-2005822 | Report of \t[AT110-e][402][eMTC] R15 Clarification for CP EDT (Huawei) | Huawei |
R2-2005823 | Report of [AT110-e][403][eMTC] R15 Porting back corrections made during Rel-16 ASN.1 review (Huawei) | Huawei |
R2-2005834 | Report of [AT110-e][403][eMTC] R15 Porting back corrections made during Rel-16 ASN.1 review (Huawei) | Huawei |
R2-2005836 | Clarification for CP EDT | Huawei, HiSilicon |
R2-2005837 | Clarification for CP EDT | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005572 | Correction on Uu and PC5 prioritization | ASUSTeK |
R2-2005573 | Correction on Uu and PC5 prioritization | ASUSTeK |
TDoc | Title | Source |
---|---|---|
R2-2004407 | Correction on SRB duplication | OPPO, LG Electronics |
R2-2004408 | Correction on SRB duplication | OPPO, LG Electronics |
R2-2005083 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005084 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005186 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005187 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005188 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005189 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005190 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005191 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005192 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005193 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005194 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2005283 | Minor changes collected by Rapporteur | Samsung Telecommunications |
R2-2005351 | Correction on t312 timer information | ZTE Corporation, Sanechips |
R2-2005352 | Correction on t312 timer information | ZTE Corporation, Sanechips |
R2-2005353 | Correction on t312 timer information | ZTE Corporation, Sanechips |
R2-2005354 | Correction on t312 timer information | ZTE Corporation, Sanechips |
R2-2005355 | Correction on t312 timer information | ZTE Corporation, Sanechips |
R2-2005481 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005482 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005483 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005484 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005485 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005486 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005487 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
R2-2005551 | PDU generation for UL spatial multiplexing | ASUSTeK |
R2-2005552 | Correction on PDU generation for UL spatial multiplexing | ASUSTeK |
R2-2005553 | Correction on PDU generation for UL spatial multiplexing | ASUSTeK |
R2-2005554 | Correction on PDU generation for UL spatial multiplexing | ASUSTeK |
R2-2005678 | Correction of AUL HARQ process | ASUSTeK |
R2-2005741 | Summary of discussion [201] on missing TDD/FDD differentiation in LTE (Huawei) | Huawei |
R2-2005742 | [DRAFT] LS on missing TDD/FDD differentiation in LTE | Huawei |
R2-2005743 | [AT110-e#201][LTE] LTE Rel-15 TDD/FDD capability differentiation [Pre-meeting] | Huawei, HiSilicon |
R2-2005744 | Summary of discussion [202] on non-contigous CA capabilities (Nokia) | Nokia |
R2-2005745 | Correction of AUL HARQ process | ASUSTeK |
R2-2005746 | Minor changes collected by Rapporteur | Samsung |
R2-2005747 | Summary of discussion [203] on LTE contributions in AI 4.5 | Nokia (RAN2 vice-chair) |
R2-2005772 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005773 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005774 | Correction of AUL HARQ process | ASUSTeK |
R2-2005775 | Correction of AUL HARQ process | ASUSTeK |
R2-2005776 | Correction on SRB duplication | OPPO, LG Electronics |
R2-2005777 | Correction on SRB duplication | OPPO, LG Electronics |
R2-2005781 | Minor changes collected by Rapporteur | Samsung (Rapporteur) |
R2-2005787 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005788 | Correction to the LTE Rel-15 TDD/FDD capability differentiation | Huawei, HiSilicon |
R2-2005995 | Minor changes collected by Rapporteur | Samsung Telecommunications |
R2-2006044 | Correction of AUL HARQ process | ASUSTeK |
R2-2006045 | Correction of AUL HARQ process | ASUSTeK |
R2-2006376 | Minor changes collected by Rapporteur | Samsung (Rapporteur) |
R2-2006420 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-2006440 | Minor changes collected by Rapporteur | Samsung (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004326 | LS on default RE mapping patterns (R1-2002828; contact: Ericsson) | RAN1 |
R2-2004337 | Reply LS on handover without SN configuration query (R3-202832; contact: Huawei) | RAN3 |
R2-2006123 | LS on clarification for the definition of the UL duty cycle (R4-2008418; contact: Apple) | RAN4 |
R2-2006163 | Clarification to maxUplinkDutyCycle-FR2 | Apple, Ericsson |
R2-2006164 | Clarification to maxUplinkDutyCycle-FR2 | Apple, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004442 | Correction on bandwidth adaptation | vivo, Nokia (rapporteur) |
R2-2004443 | Correction on bandwidth adaptation | vivo, Nokia (rapporteur) |
R2-2006370 | Correction on bandwidth adaptation | vivo, Nokia (rapporteur) |
R2-2006371 | Correction on bandwidth adaptation | vivo, Nokia (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2006359 | Summary of offline discussion #001: Correction on 38300 | vivo |
TDoc | Title | Source |
---|---|---|
R2-2005230 | Clarification on PDCP version change | Huawei, HiSilicon, ZTE Corporation (Rapporteur) |
R2-2005231 | Clarification on PDCP version change | Huawei, HiSilicon |
R2-2006421 | Clarification on PDCP version change | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005163 | Correction on MN-SN measurements coordination in INM | Ericsson |
R2-2005164 | Correction on MN-SN measurements coordination in INM | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2005356 | Corrections to MAC description | ZTE Corporation (Rapporteur), Ericsson, Huawei, HiSilicon |
R2-2005357 | Corrections to MAC description | ZTE Corporation (Rapporteur), Ericsson, Huawei, HiSilicon |
R2-2006167 | Corrections to MAC description | ZTE Corporation (Rapporteur), Ericsson, Huawei, HiSilicon |
R2-2006168 | Corrections to MAC description | ZTE Corporation (Rapporteur), Ericsson, Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004734 | CR to clarify the meaning of GNSS term in 36.305 Rel-15 | ESA, Nokia, Nokia Shanghai Bell |
R2-2004735 | CR to clarify the meaning of GNSS term in 36.305 Rel-16 | ESA, Nokia, Nokia Shanghai Bell |
R2-2004745 | CR to clarify the meaning of GNSS term in 38.305 Rel-15 | ESA, Nokia, Nokia Shanghai Bell |
R2-2004746 | CR to clarify the meaning of GNSS term in 38.305 Rel-16 | ESA, Nokia, Nokia Shanghai Bell |
R2-2004790 | Clarification on UE Positioning Architecture in 38 305 for Rel-15 | CATT |
R2-2004791 | Clarification on UE Positioning Architecture in 38 305 for Rel-16 | CATT |
R2-2005891 | Clarification on UE Positioning Architecture | CATT |
R2-2005892 | Clarification on UE Positioning Architecture | CATT |
TDoc | Title | Source |
---|---|---|
R2-2004423 | Clarification on obtaining of PH values | Samsung |
R2-2004424 | Clarification on obtaining of PH values | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004940 | Clarification on preamble selection for beam failure recovery | Google Inc. |
R2-2004942 | Clarification on preamble selection for beam failure recovery | Google Inc. |
R2-2005555 | Discussion on clarification of BWP inactivity timer operation | ASUSTeK |
R2-2005556 | Clarification of BWP inactivity timer operation | ASUSTeK |
R2-2005557 | Discussion on presence of IEs in BeamFailureRecoveryConfig | ASUSTeK |
R2-2005558 | Clarification on presence of IEs in BeamFailureRecoveryConfig | ASUSTeK |
R2-2005559 | Clarification on presence of IEs in BeamFailureRecoveryConfig | ASUSTeK |
R2-2005560 | Handling on absence of IEs in BeamFailureRecoveryConfig | ASUSTeK |
R2-2005561 | Handling on absence of IEs in BeamFailureRecoveryConfig | ASUSTeK |
R2-2006158 | Report of [AT110e][013][NR15] User Plane Corrections (Samsung) | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2005471 | Discussion on missing RLC segment in RLC STATUS PDU | Huawei, HiSilicon |
R2-2005472 | Clarification on the reception status of RLC STATUS PDU | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005459 | Correction to IMS capabilities for NGEN-DC | Google Inc. |
R2-2006221 | Correction to IMS capabilities for NGEN-DC | Google Inc. |
TDoc | Title | Source |
---|---|---|
R2-2006042 | Report of [AT110-e][003][NR15] Misc RRC Corrections | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004853 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, InterDigital, Nokia, NTT DOCOMO INC |
R2-2004854 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, InterDigital, Nokia, NTT DOCOMO INC |
R2-2005000 | Correction on PUCCH configuration | Huawei, HiSilicon |
R2-2005001 | Correction on PUCCH configuration | Huawei, HiSilicon |
R2-2005233 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
R2-2005234 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
R2-2005641 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
R2-2005642 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
R2-2005643 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
R2-2005644 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004448 | Clarifying RRC procedure performance requirements | Nokia, Nokia Shanghai Bell |
R2-2004449 | Clarifying RRC procedure performance requirements | Nokia, Nokia Shanghai Bell |
R2-2004468 | CR on SRS-CarrierSwitching | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2004469 | CR on SRS-CarrierSwitching | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2004488 | Clarification for radioBearerConfig and radioBearerConfig2 | vivo |
R2-2004489 | Clarification for radioBearerConfig and radioBearerConfig2 | vivo |
R2-2004531 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2004532 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2004533 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2004534 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2004564 | Presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Samsung |
R2-2004565 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Samsung |
R2-2004566 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Samsung |
R2-2004567 | Introduction of ssb-perRACH-Occasion-CSI-RS-Solution 3 (R15) | ZTE Corporation, Sanechips, Samsung |
R2-2004568 | Introduction of ssb-perRACH-Occasion-CSI-RS-Solution 3 (R16) | ZTE Corporation, Sanechips, Samsung |
R2-2004768 | Clarification on the configuration of RAN-AreaConfig | Apple |
R2-2004769 | Clarification on the configuration of RAN-AreaConfig | Apple |
R2-2004770 | Clarification on the maxPUSCH-Duration for LCP Restriction | Apple |
R2-2004771 | Clarification on the maxPUSCH-Duration for LCP Restriction | Apple |
R2-2004772 | Clarificaiton on the default BWP configuration | Apple |
R2-2004773 | Clarificaiton on the default BWP configuration | Apple |
R2-2004774 | Clarificaiton on the default BWP configuration | Apple |
R2-2004903 | Corrections to CORESET and PDCCH TCI state release | Nokia, Nokia Shanghai Bell |
R2-2004904 | Corrections to CORESET and PDCCH TCI state release | Nokia, Nokia Shanghai Bell |
R2-2004905 | Corrections to CORESET and PDCCH TCI state release | Nokia, Nokia Shanghai Bell |
R2-2005002 | Clarification on release and addition of the uplink for Scell | Huawei, HiSilicon |
R2-2005003 | Clarification on release and addition of the uplink for Scell | Huawei, HiSilicon |
R2-2005009 | Clarification on SCell release | Huawei, HiSilicon |
R2-2005072 | Configuration of SRS Carrier Switching | Ericsson |
R2-2005073 | Corrections to configuration of SRS Carrier Switching | Ericsson |
R2-2005110 | Corrections to configuration of SRS Carrier Switching | Ericsson |
R2-2005111 | [DRAFT] Ambiguities related SRS Carrier Switching | Ericsson |
R2-2005270 | T310 handling during mobility from NR | Ericsson |
R2-2005271 | T310 handling during mobility from NR | Ericsson |
R2-2005531 | SMTC Configuration for PSCell Addition for NR-DC | Apple, ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2005532 | SMTC Configuration for PSCell Addition for NR-DC | Apple, ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2005533 | SMTC Configuration for PSCell Addition for NR-DC | Apple, ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2005534 | SMTC Configuration for PSCell Addition for NR-DC | Apple, ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2005634 | MAC Default Configuration for SCG | Qualcomm Incorporated |
R2-2005635 | MAC Default Configuration for SCG | Qualcomm Incorporated |
R2-2005636 | Correction to Resending UEAssistanceInformation upon HO | Qualcomm Incorporated |
R2-2005637 | Correction to Resending UEAssistanceInformation upon HO | Qualcomm Incorporated |
R2-2005703 | Correction for handover from EN-DC to NR | Huawei, HiSilicon |
R2-2005704 | Correction for handover from EN-DC to NR | Huawei, HiSilicon |
R2-2006067 | [AT109bis-e][009][NR15] Processing Time and Security | Qualcomm |
R2-2006068 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2006069 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2006070 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2006071 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
R2-2006107 | CR on SRS-CarrierSwitching | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2006108 | CR on SRS-CarrierSwitching | ZTE Corporation, Sanechips, Qualcomm Incorporated |
R2-2006186 | Summary of [AT110e][007][NR15] DC Configuration (Apple) | Apple |
R2-2006228 | Clarification on release and addition of the uplink for SCell | Huawei, HiSilicon |
R2-2006229 | Clarification on release and addition of the uplink for SCell | Huawei, HiSilicon |
R2-2006244 | SMTC Configuration for PSCell Addition for NR-DC (Option 2) | Apple |
R2-2006245 | SMTC Configuration for PSCell Addition for NR-DC (Option 2) | Apple |
R2-2006246 | Clarification on the maxPUSCH-Duration for LCP Restriction | Apple |
R2-2006247 | Clarification on the maxPUSCH-Duration for LCP Restriction | Apple |
R2-2006248 | Summary of the offline discussion on SMTC configuration for NR-DC | Apple |
R2-2006304 | Summary for [008][NR15] Mobility (phase 1) | Huawei |
R2-2006324 | Corrections to CORESET and PDCCH TCI state release | Nokia, Nokia Shanghai Bell |
R2-2006325 | Correction to CORESET and PDCCH TCI state release | Nokia, Nokia Shanghai Bell |
R2-2006334 | SMTC Configuration for PSCell Addition for NR-DC (Option 2) | Apple |
R2-2006339 | [Draft] LS on NR SRS carrier switching | Qualcomm Incorporated |
R2-2006347 | T310 handling during MobilityFromNR | Ericsson |
R2-2006348 | T310 handling during MobilityFromNR | Ericsson |
R2-2006362 | LS on NR SRS carrier switching | RAN2 |
R2-2006373 | Correction to re-sending UEAssistanceInformation upon reconfiguration w/ sync | Qualcomm Incorporated |
R2-2006374 | Correction to re-sending UEAssistanceInformation upon reconfiguration w/ sync | Qualcomm Incorporated |
R2-2006415 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004363 | LS on UE reporting criteria (R4-2005265; contact: Nokia) | RAN4 |
R2-2005419 | 36331 CR(R15) on inter-RAT SFTD measurements | Huawei, HiSilicon, Ericsson, Nokia |
R2-2005420 | 36331 CR(R16) on inter-RAT SFTD measurements | Huawei, HiSilicon, Ericsson, Nokia |
R2-2005421 | 38331 CR(R15) on inter-RAT SFTD measurements | Huawei, HiSilicon |
R2-2005422 | 38331 CR(R16) on inter-RAT SFTD measurements | Huawei, HiSilicon |
R2-2006305 | Summary for [010][NR15] Measurements and System Information (phase 1) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2005392 | Corrections to SIB1 Processing | Samsung Electronics Co., Ltd |
R2-2006047 | Corrections to SIB1 Processing | Samsung Electronics Co., Ltd |
R2-2006065 | Corrections to SIB1 Processing | Samsung Electronics Co., Ltd |
TDoc | Title | Source |
---|---|---|
R2-2005167 | Correction to measurement coordination in MR-DC | Ericsson |
R2-2005168 | Correction to measurement coordination in MR-DC | Ericsson |
R2-2005182 | Discussion on left issue in Handover without fetching source SN config | Nokia, Nokia Shanghai Bell |
R2-2005235 | Handover without up to date SN radio bearer configuration | Huawei, HiSilicon |
R2-2005236 | Correction for handover preparation with SN terminated bearers | Huawei, HiSilicon |
R2-2005237 | Correction for handover preparation with SN terminated bearers | Huawei, HiSilicon |
R2-2005574 | Introduction of p-MaxUE-FR1 in the inter-node message | Google Inc. |
R2-2005576 | Introduction of p-MaxUE-FR1 in the inter-node message | Google Inc. |
R2-2006214 | Correction to measurement coordination in MR-DC | Ericsson |
R2-2006215 | Correction to measurement coordination in MR-DC | Ericsson |
R2-2006306 | Summary for [011][NR15] Inter-Node RRC (phase 1) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2004912 | Correction on SpCell | OPPO |
R2-2004913 | Correction on SpCell | OPPO |
R2-2005165 | Correction to inter-system (intra-system) handover terminology | Ericsson |
R2-2005166 | Correction to inter-system (intra-system) handover terminology | Ericsson |
R2-2005322 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2005581 | Discussion on AS rekeying failure handling | Huawei, HiSilicon |
R2-2005844 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2005920 | Miscellaneous non-controversial corrections Set VI | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2005728 | Reply LS on Calculation of ShortResumeMAC-I (S3-201489; contact: Huawei) | SA3 |
R2-2006251 | Summary of [AT110e][012][NR15] LTE changes related to NR (Nokia) | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2004450 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
R2-2004451 | Avoiding security risk for RLC AM and RLC UM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
R2-2004452 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
R2-2004453 | Avoiding security risk for RLC AM and RLC UM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
R2-2004605 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
R2-2004606 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
R2-2005583 | UE measurement capability requirements for NR | Google Inc. |
R2-2005586 | UE measurement capability requirements for NR | Google Inc. |
R2-2005819 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
R2-2006416 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
R2-2006425 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2004766 | Clarification on Pcompensation for IRAT Cell Selection Criterion | Apple |
R2-2004767 | Clarification on Pcompensation for IRAT Cell Selection Criterion | Apple |
R2-2005195 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell, CMCC, Google Inc. |
R2-2005196 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell, CMCC, Google Inc. |
R2-2005232 | Clarification on PDCP version change in Rel-15 | Huawei, HiSilicon |
R2-2005660 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell, CMCC, Google Inc., vivo |
R2-2005661 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell, CMCC, Google Inc., vivo |
TDoc | Title | Source |
---|---|---|
R2-2005112 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson, NTT Docomo |
R2-2005113 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson, NTT Docomo |
R2-2005395 | Correction to RequestedCapabilityCommon | Huawei, HiSilicon |
R2-2005396 | Correction to RequestedCapabilityCommon | Huawei, HiSilicon |
R2-2005407 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
R2-2005408 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
R2-2005409 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
R2-2005410 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004313 | Reply LS on the applicability of UE capabilities for NE-DC (R1-2002792; contact: ZTE) | RAN1 |
R2-2004394 | Band combination list for NE-DC (Cat-F) | OPPO |
R2-2004395 | Band combination list for NE-DC (Cat-A) | OPPO |
R2-2004396 | Band combination list for NE-DC (Cat-F) | OPPO, ZTE Corporation, Sanechips |
R2-2004397 | Clarification on L1 feature of NGEN-DC and NE-DC | OPPO |
R2-2004398 | Clarification on L1 feature of NGEN-DC and NE-DC | OPPO |
R2-2004399 | Clarification on NGEN-DC and NE-DC support | OPPO |
R2-2004400 | Clarification on L2 and RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2004405 | [Draft] LS on Clarification on RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2004431 | UE requirement on the number of RLC bearers | Qualcomm Incorporated |
R2-2004432 | Corrections on the number of DRBs and RLC bearers | Qualcomm Incorporated, Samsung, Nokia |
R2-2004433 | Corrections on the number of DRBs and RLC bearers | Qualcomm Incorporated, Samsung, Nokia |
R2-2004434 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Qualcomm Incorporated |
R2-2004435 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Qualcomm Incorporated |
R2-2004436 | Signalling of NR-DC only band combination | Qualcomm Incorporated |
R2-2004437 | Clarification on supported NR-DC cell grouping | Qualcomm Incorporated |
R2-2004439 | Summary of email discussion [Post109bis-e][064][NR15] XDD FRX differentiation | Qualcomm Incorporated |
R2-2004440 | Correction on UE capabilities with xDD and FRx differentiation | Qualcomm Incorporated |
R2-2004441 | UE requirement on the number of RLC bearers | Qualcomm Incorporated |
R2-2004454 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2004455 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2004456 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2004457 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2004458 | Clarification on BCS and UE BW capabilities | Nokia, Nokia Shanghai Bell |
R2-2004459 | Draft LS to RAN4 on clarification on BCS and UE BW capabilities | Nokia, Nokia Shanghai Bell |
R2-2004470 | CR on introduction of extended capabilities for NE-DC only BCs | ZTE Corporation, Sanechips, OPPO |
R2-2004471 | CR on applicability of UE MIMO capabilities for NE-DC | ZTE Corporation, Sanechips, OPPO |
R2-2004472 | CR on introduction of extended capabilities for NE-DC only BCs | ZTE Corporation, Sanechips, OPPO |
R2-2004473 | CR on applicability of UE MIMO capabilities for NE-DC | ZTE Corporation, Sanechips, OPPO |
R2-2004478 | Report of [Post109bis-e][924][NR15] Unnecessary FRx differentiation | ZTE Corporation |
R2-2004479 | CR on unnecessary xDD FRx differentiation | ZTE Corporation, Sanechips |
R2-2004480 | CR on unnecessary xDD FRx differentiation | ZTE Corporation, Sanechips |
R2-2004490 | XDD/FRX additional Differentiation | vivo |
R2-2004491 | CR38.306 CR to XDD/FRX additional Differentiation | vivo |
R2-2004560 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2004561 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2004574 | XDD/FRX additional Differentiation | vivo |
R2-2004575 | CR to XDD/FRX additional Differentiation | vivo |
R2-2004754 | FR2 CA fallback | Apple, InterDigital Inc. |
R2-2004755 | FR2 CA fallback | Apple, InterDigital Inc. |
R2-2004821 | Clarification on L1 feature of NGEN-DC and NE-DC | OPPO |
R2-2004822 | Clarification on L1 feature of NGEN-DC and NE-DC | OPPO |
R2-2004823 | Clarification on L2 and RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2004831 | xDD differentiation of UE capabilities for SUL/SDL bands | Samsung |
R2-2004842 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
R2-2004843 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
R2-2004844 | Missing UE capability requirements | Ericsson |
R2-2004845 | Missing UE capability requirements | Ericsson |
R2-2004846 | Clarification for KPAS and EU-alert 38.300 | Ericsson |
R2-2004847 | Clarification for KPAS and EU-alert 38.300 | Ericsson |
R2-2004848 | Clarification for KPAS and EU-alert 38.304 | Ericsson |
R2-2004849 | Clarification for KPAS and EU-alert 38.304 | Ericsson |
R2-2004850 | Clarification for KPAS and EU-alert 38.331 | Ericsson |
R2-2004851 | Clarification for KPAS and EU-alert 38.331 | Ericsson |
R2-2004969 | Clarifications on the BandList of the BandCombination | ZTE Corporation, Sanechips, OPPO |
R2-2004970 | Clarifications on the BandList of the BandCombination | ZTE Corporation, Sanechips, OPPO |
R2-2004971 | Further considerations on the simultaneously SRS carrier switch and antenna switch | ZTE Corporation, Sanechips |
R2-2004972 | Further consideration on the Notes to the FeatureSetCombination | ZTE Corporation, Sanechips |
R2-2004994 | Correction on UE capability constraints | vivo |
R2-2004995 | Correction on UE capability constraints | vivo |
R2-2004996 | Correction on UE capability constraints | vivo |
R2-2005004 | Discussion on minimum UE requirements for the number of RLC bearers | Huawei, HiSilicon |
R2-2005005 | Minimum UE requirements for the number of RLC bearers | Huawei, HiSilicon |
R2-2005006 | Minimum UE requirements for the number of RLC bearers | Huawei, HiSilicon |
R2-2005007 | Minimum UE requirements for the number of RLC bearers | Huawei, HiSilicon |
R2-2005008 | Minimum UE requirements for the number of RLC bearers | Huawei, HiSilicon |
R2-2005119 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2005120 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2005358 | Corrections on the number of DRBs and RLC bearers | Qualcomm Incorporated, Samsung, Nokia |
R2-2005359 | Corrections on the number of DRBs and RLC bearers | Qualcomm Incorporated, Samsung, Nokia |
R2-2005360 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Qualcomm Incorporated |
R2-2005361 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Qualcomm Incorporated |
R2-2005397 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
R2-2005398 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
R2-2005411 | Summary of [Post109bis-e][923][NR15] clarification on codebook parameters for 2-32 | Huawei, HiSilicon |
R2-2005412 | on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, CATT |
R2-2005413 | on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, CATT |
R2-2005414 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2005415 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2005458 | Correction to IMS capabilities for NGEN-DC | Google Inc. |
R2-2005494 | Introduction of IMS capabilities for NR-DC | Google Inc. |
R2-2005499 | Introduction of IMS capabilities for NR-DC | Google Inc. |
R2-2005535 | Introduction of IMS capability for NR-DC | Google Inc. |
R2-2005540 | Introduction of IMS capability for NR-DC | Google Inc. |
R2-2005577 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2005578 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2005579 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2005580 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2005618 | Introduction of CGI reporting capabilitie | vivo |
R2-2005619 | Introduction of CGI reporting capabilitie | vivo |
R2-2005620 | Introduction of CGI reporting capabilitie | vivo |
R2-2005621 | Introduction of CGI reporting capabilitie | vivo |
R2-2005622 | Introduction of CGI reporting capabilitie | vivo |
R2-2005630 | UE Capability Enhancement for FR1 FR2 CA and DC | Qualcomm Incorporated |
R2-2005631 | UE Capability Enhancement for FR1 FR2 CA and DC | Qualcomm Incorporated |
R2-2005632 | UE Capability Enhancement for FR1 FR2 CA and DC | Qualcomm Incorporated |
R2-2005633 | UE Capability Enhancement for FR1 FR2 CA and DC | Qualcomm Incorporated |
R2-2005690 | Discussion on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2005691 | CR to 38.306 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2005692 | CR to 38.331 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2005709 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2005710 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2005999 | Summary of email discussion [Post109bis-e][921][NR15] CRs for FR2 CA Fallback (Apple) | Apple |
R2-2006021 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2006022 | Default values for UE capability | Nokia, Nokia Shanghai Bell, NTT Docomo |
R2-2006061 | UE Capability Enhancement for FR1 (TDD/FDD) / FR2 CA and DC | Qualcomm Incorporated |
R2-2006062 | UE Capability Enhancement for FR1 (TDD/FDD) / FR2 CA and DC | Qualcomm Incorporated |
R2-2006063 | UE Capability Enhancement for FR1 (TDD/FDD) / FR2 CA and DC | Qualcomm Incorporated |
R2-2006064 | UE Capability Enhancement for FR1 (TDD/FDD) / FR2 CA and DC | Qualcomm Incorporated |
R2-2006115 | CR on unnecessary XDD FRX differentiation | ZTE Corporation, Sanechips |
R2-2006116 | CR on unnecessary XDD FRX differentiation | ZTE Corporation, Sanechips |
R2-2006122 | LS on serving cell number for EN-DC power class (R4-2008415; contact: Huawei) | RAN4 |
R2-2006152 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2006153 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2006199 | Clarification on L2 and RAN4 feature of NGEN-DC and NE-DC | OPPO |
R2-2006200 | Clarification on L2 and RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2006205 | Band combination list for NE-DC (Cat-F) | OPPO, ZTE Corporation, Sanechips |
R2-2006206 | Clarification on L2 and RAN4 feature of NGEN-DC and NE-DC | OPPO |
R2-2006207 | Clarification on L2 and RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2006208 | [Draft] LS on Clarification on RAN4 features of NGEN-DC and NE-DC | OPPO |
R2-2006219 | Summary for Offline [020][NR15] UE cap IMS voice | |
R2-2006220 | Correction to IMS capabilities for NGEN-DC | Google Inc. |
R2-2006222 | Clarification on the support of IMS voice over split bearer for NR-DC and NE-DC | Google Inc. |
R2-2006223 | Clarification on the support of IMS voice over split bearer for NR-DC and NE-DC | Google Inc. |
R2-2006233 | Clarification for KPAS and EU-alert 38.304 | Ericsson |
R2-2006234 | Clarification for KPAS and EU-alert 38.331 | Ericsson |
R2-2006235 | Clarification for KPAS and EU-alert 38.331 | Ericsson |
R2-2006236 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
R2-2006237 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
R2-2006238 | Missing UE capability requirements | Ericsson |
R2-2006239 | Missing UE capability requirements | Ericsson |
R2-2006252 | Summary of [AT110e][014][NR15] UE Cap IPA and email disc last meeting (Nokia) | Nokia |
R2-2006253 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2006254 | Invalidating bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2006256 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2006257 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2006268 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2006269 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon |
R2-2006270 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
R2-2006271 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
R2-2006278 | Correction on UE capabilities with xDD and FRx differentiations | Qualcomm Incorporated |
R2-2006279 | Correction on UE capabilities with xDD and FRx differentiations | Qualcomm Incorporated |
R2-2006280 | DRAFT Reply LS on XDD-FRX Differentiation | Qualcomm Incorporated |
R2-2006281 | Corrections on the number of DRBs | Qualcomm Incorporated, Samsung, Nokia |
R2-2006282 | Corrections on the number of DRBs | Qualcomm Incorporated, Samsung, Nokia |
R2-2006283 | Corrections on the number of DRBs | Qualcomm Incorporated, Samsung, Nokia |
R2-2006284 | Corrections on the number of DRBs | Qualcomm Incorporated, Samsung, Nokia |
R2-2006285 | FR2 CA fallback | Apple, InterDigital Inc. |
R2-2006286 | FR2 CA fallback | Apple, InterDigital Inc. |
R2-2006298 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon, CATT |
R2-2006299 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Huawei, HiSilicon, CATT |
R2-2006309 | Correction on SRS antenna capability for carrier switching | Huawei, HiSilicon, CATT |
R2-2006310 | Correction on SRS antenna capability for carrier switching | Huawei, HiSilicon, CATT |
R2-2006311 | Introduction of CGI reporting capabilitie | vivo |
R2-2006312 | Introduction of CGI reporting capabilitie | vivo |
R2-2006313 | Introduction of CGI reporting capabilitie | vivo |
R2-2006314 | Introduction of CGI reporting capabilitie | vivo |
R2-2006315 | Correction on UE capability constraints | vivo |
R2-2006316 | Correction on UE capability constraints | vivo |
R2-2006317 | Draft LS on UE capability for CGI reporting | vivo |
R2-2006322 | LS on UE capability xDD differentiation for SUL/SDL bands | RAN2 |
R2-2006328 | CR on introduction of extended capabilities for NR-DC only BCs | ZTE Corporation, Sanechips, OPPO |
R2-2006329 | CR on introduction of extended capabilities for NR-DC only BCs | ZTE Corporation, Sanechips, OPPO |
R2-2006352 | LS on Clarification on RAN4 features of NE-DC | RAN2 |
R2-2006355 | Introduction of CGI reporting capabilities | vivo |
R2-2006356 | Introduction of CGI reporting capabilities | vivo |
R2-2006357 | Introduction of CGI reporting capabilities | vivo |
R2-2006358 | Introduction of CGI reporting capabilities | vivo |
R2-2006367 | Reply LS on XDD-FRX Differentiation | RAN2 |
R2-2006382 | Introduction of CGI reporting capabilities | vivo |
R2-2006383 | Introduction of CGI reporting capabilities | vivo |
R2-2006384 | Introduction of CGI reporting capability | vivo |
R2-2006385 | Introduction of CGI reporting capability | vivo |
R2-2006386 | Correction on UE capability constraints | vivo |
R2-2006387 | Correction on UE capability constraints | vivo |
R2-2006388 | Introduction of CGI reporting capabilities | vivo |
R2-2006389 | Introduction of CGI reporting capabilities | vivo |
R2-2006390 | Introduction of CGI reporting capabilities | vivo |
R2-2006391 | Introduction of CGI reporting capability | vivo |
R2-2006392 | Draft LS on UE capability for CGI reporting | vivo |
R2-2006414 | Introduction of CGI reporting capability | vivo |
R2-2006422 | on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, CATT |
R2-2006432 | UE Capability Enhancement for FR1 (TDD/FDD) / FR2 CA and DC | Qualcomm Incorporated |
R2-2006444 | FR2 CA fallback | Apple, InterDigital, Nokia, Nokia Shanghai Bell, Xiaomi Communications, Spreadtrum \n Communications, CMCC, Panasonic, MediaTek Inc. |
R2-2006445 | FR2 CA fallback | Apple, InterDigital, Nokia, Nokia Shanghai Bell, Xiaomi Communications, Spreadtrum Communications, CMCC, Panasonic, MediaTek Inc. |
R2-2006448 | Reply LS on XDD-FRX Differentiation | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004852 | Corrections to cell barred handling | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004547 | Measurement rules for cell re-selection | OPPO |
R2-2004548 | Measurement rules for cell re-selection | OPPO |
R2-2004752 | Correction on suitable cell definition | Apple |
R2-2004753 | Correction on suitable cell definition | Apple |
R2-2004762 | Clarification on Mobility State Detection | Apple |
R2-2004763 | Clarification on Mobility State Detection | Apple |
R2-2004764 | Clarification on Pcompensation for IRAT Cell Selection Criterion | Apple |
R2-2004765 | Clarification on Pcompensation for IRAT Cell Selection Criterion | Apple |
R2-2005078 | Corrections to cell barred handling | Huawei, HiSilicon |
R2-2005079 | Corrections to cell barred handling | Huawei, HiSilicon |
R2-2005135 | Clarification on the frequencies UE shall evaluate for reselection | ZTE Corporation, Sanechips |
R2-2005136 | Clarification on the frequencies UE shall evaluate for reselection (R15) | ZTE Corporation, Sanechips |
R2-2005137 | Clarification on the frequencies UE shall evaluate for reselection (R16) | ZTE Corporation, Sanechips |
R2-2005431 | Correction on inter-RAT cell (re)selection in RRC_INACTIVE | Samsung Electronics Co., Ltd |
R2-2005432 | Correction on inter-RAT cell (re)selection in RRC_INACTIVE | Samsung Electronics Co., Ltd |
R2-2006249 | Correction on suitable cell definition | Apple |
R2-2006250 | Correction on suitable cell definition | Apple |
R2-2006259 | Corrections to cell barred handling | Huawei, HiSilicon |
R2-2006260 | Corrections to cell barred handling | Huawei, HiSilicon |
R2-2006437 | Corrections to cell barred handling | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004602 | [I654] Adding DL AM RLC extension in NR RRC | Lenovo, Motorola Mobility, Intel Corporation |
R2-2004669 | Stop condition on T310 (C003) | Intel Corporation |
R2-2004709 | Extension of SearchSpace IE [Z106][I657][I658][I659] | MediaTek Inc. |
R2-2004732 | Miscellaneous ASN.1 corrections related to I630, I631, I632, I633 | Intel Corporation |
R2-2004925 | [Z118] Clarification on providing network specific uac-AccessCategory1-SelectionAssistanceInfo | ZTE Corporation, Sanechips, CMCC, Nokia |
R2-2004926 | [Z118] CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo-Option 1 | ZTE Corporation, Sanechips, Nokia |
R2-2004927 | [Z118] CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo-Option 2 | ZTE Corporation, Sanechips, Nokia |
R2-2004928 | [Z118] CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo-Option 3 | ZTE Corporation, Sanechips, Nokia |
R2-2004929 | [Z118] CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo-Option 4 | ZTE Corporation, Sanechips, Nokia |
R2-2004951 | [H003] On merging uplink TDRA into one IE | Ericsson |
R2-2004952 | [E228][E230] On grouping similar parameters in PUSCH-Config/PDSCH-Config | Ericsson |
R2-2004993 | [H249] Discuission on the ASN.1 of inter-dependent field values | Huawei, HiSilicon |
R2-2005130 | [B108][IAB][SON] TP for failure type in SCGFailurinformation message | Lenovo, Motorola Mobility |
R2-2005176 | [E207,E206,E239] Correction to failureType handling in SCGFailureInformation | Ericsson |
R2-2005177 | [E039] Correction of RLF report upon MCG RLF | Ericsson |
R2-2005261 | [38.331][H244] TP for PDSCH-TimeDomainResourceAllocationList | Huawei, HiSilicon |
R2-2005262 | [38.331][H245] TP for PUSCH-TimeDomainResourceAllocationList | Huawei, HiSilicon |
R2-2005317 | Consolidation of parameter names in RAN1 and RAN2 specifications | Ericsson |
R2-2005318 | 38331 Rel-16 Ph2 ASN.1 review file | Ericsson |
R2-2005319 | RIL list Rel-16 Ph2 ASN.1 review | Ericsson |
R2-2005320 | Miscellaneous ASN.1 review corrections | Ericsson |
R2-2005321 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2005450 | Early Release Support of Features | CMCC |
R2-2005628 | Analysis of cross-WI configurability | Huawei, HiSilicon |
R2-2005717 | [B200] Using Extension Addition Group in SIB | Lenovo, Motorola Mobility |
R2-2005843 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2005918 | Miscellaneous ASN.1 review corrections | Ericsson |
R2-2005919 | Miscellaneous non-controversial corrections Set VI | Ericsson |
R2-2006025 | Flagged RILs, 38331 Rel-16 Ph2 | Ericsson |
R2-2006036 | [DRAFT] Reply LS on updated Rel-16 LTE and NR parameter lists | Ericsson |
R2-2006037 | RAN1 parameter list with ASN.1 names for Rel-16 NR | Ericsson |
R2-2006038 | RAN1 parameter list with ASN.1 names for Rel-16 LTE | Ericsson |
R2-2006057 | Reply LS on Conflicting configurations (R1-2004808; contact: Huawei) | RAN1 |
R2-2006074 | [DRAFT] Reply LS on updated Rel-16 LTE and NR parameter lists | Ericsson |
R2-2006075 | Reply LS on updated Rel-16 LTE and NR parameter lists | RAN2 |
R2-2006085 | Reply LS on updated Rel-16 LTE and NR parameter lists | RAN2 |
R2-2006301 | [AT110-e][067][NR16] NR ASN1 3 (Ericsson) Mail discussion report | Ericsson |
R2-2006302 | [AT110-e][064][NR16] NR RRC 1 (Ericsson) Mail discussion report | Ericsson |
R2-2006343 | Summary of [AT110-e][066][NR16] NR ASN1 2 (Intel) | Intel Corporation (rapporteur) |
R2-2006346 | Report from email discussion [AT110-e][068][NR16] NR ASN1 4 | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2004358 | LS on Rel-16 RAN1 UE features lists for NR (R1-2003072; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2004362 | LS on Rel-16 RAN4 UE features lists for LTE and NR (R4-2005192; contact: NTT DOCOMO) | RAN4 |
R2-2005052 | Views on MIMO capability (FG 16-5c) | vivo |
R2-2005109 | Discussion on the SRS UE capability in LPP | Huawei, HiSilicon |
R2-2005311 | Report of email discussion [Post109bis-e][963][NR16] UE capabilities | Intel Corporation, NTT DoCoMo |
R2-2005312 | [draft] Reply LS on Rel-16 UE feature list | Intel Corporation, NTT DoCoMo |
R2-2005313 | Release-16 UE capabilities for RAN1 and RAN4 feature list | Intel Corporation, NTT DoCoMo |
R2-2005314 | Release-16 UE capabilities for RAN1 and RAN4 feature list | Intel Corporation, NTT DoCoMo |
R2-2005315 | Introduction of Release-16 UE positioning capabilities | Intel Corporation, NTT DoCoMo |
R2-2005460 | Discussion on UE capability for OdSIB | Huawei, HiSilicon |
R2-2005582 | Discussion on the way of capturing Rel-16 UE capabilities | Huawei, HiSilicon |
R2-2005817 | Release-16 UE capabilities for RAN1 and RAN4 feature list | Intel Corporation, NTT DoCoMo |
R2-2005818 | Release-16 UE capabilities for RAN1 and RAN4 feature list | Intel Corporation, NTT DoCoMo |
R2-2005886 | Introduction of Release-16 UE positioning capabilities | Intel Corporation, NTT DoCoMo |
R2-2006004 | LS on Rel-16 RAN4 UE features lists for LTE and NR (R4-2005192; contact: NTT DOCOMO) | RAN4 |
R2-2006020 | Open issues for Rel-16 UE capability handling | Intel Corporation |
R2-2006023 | [draft] Reply LS on Rel-16 UE feature list | Intel Corporation, NTT DoCoMo |
R2-2006029 | [DRAFT] Reply LS on Rel-16 UE feature lists | Intel Corporation, NTT DoCoMo |
R2-2006030 | Reply LS on Rel-16 UE feature lists | RAN2 |
R2-2006097 | LS on updated Rel-16 RAN1 UE features lists for NR (R1-2004969; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2006105 | Way forward on Rel-16 RAN1/4 UE capability handling | Intel Corporation |
R2-2006119 | LS on updated Rel-16 RAN1 UE features lists for NR (R1-2005096; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2006134 | LS on Rel-16 RAN4 UE features lists for LTE and NR (R4-2009173; contact: NTT DOCOMO) | RAN4 |
R2-2006378 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#101-e (R2-2006378; contact: NTT DOCOMO, AT&T) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2004302 | LS on RAN1 input to Rel-16 TS 38.300 on V2X, Positioning and MR-DC (R1-2001356; contact: Nokia) | RAN1 |
R2-2005258 | [38.331][H230] Extension of a single Need M item to a list of this item | Huawei, HiSilicon |
R2-2005259 | [38.331][H231] Extending the number of entries of a list not using ToAddMod list | Huawei, HiSilicon |
R2-2005260 | [38.331][H232][I656][I657][658][I659][E130][E266] Extensions of ToAddModList | Huawei, HiSilicon |
R2-2005263 | [38.331][H246] Usage of presence conditions for SetupRelease structures | Huawei, HiSilicon |
R2-2005264 | [38.331][H247] Missing need codes for absence in presence conditions | Huawei, HiSilicon |
R2-2005265 | [38.331][H248] Fieds that cannot be released | Huawei, HiSilicon |
R2-2005328 | Alignment of SR clause | Ericsson, Samsung |
R2-2005393 | Corrections to SIB1 Processing | Samsung Electronics Co., Ltd |
R2-2005501 | 38321 CR Clarification on eLCID | LG Electronics Inc., MediaTek |
R2-2005502 | Stopping ongoing Random Access procedure | LG Electronics Inc. |
R2-2005562 | Handling of unexpected eLCID values. | ASUSTeK |
R2-2005626 | [H241] Correction to PDCCH configuration | Huawei, HiSilicon |
R2-2005627 | [H242] Correction to DCI formats in SearchSpace | Huawei, HiSilicon |
R2-2005998 | Stage 2 Cleanup | Nokia (Rapporteur) |
R2-2006011 | Releasing Rel-16 configurations when handover to Rel-15 cells | Huawei, HiSilicon |
R2-2006231 | 38321 CR Clarification on eLCID | LG Electronics Inc., MediaTek, ASUSTek |
R2-2006232 | Outcome of [AT110-e][062][NR16] MAC updates | Ericsson (Rapporteur) |
R2-2006344 | Summary of [AT110-e][065][NR16] NR ASN1 1 (Huawei) | Huawei, HiSilicon |
R2-2006345 | Summary of [AT110-e][075][NR16] Conflicting Configurations (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004338 | LS on UL F1-C traffic mapping for intra-CU migration scenario (R3-202851; contact: ZTE) | RAN3 |
R2-2004353 | LS on RAN1 agreements related to resource multiplexing in IAB (R1-2003043; contact: Ericsson) | RAN1 |
R2-2004361 | RRC Message Design for IAB IP Address Allocation (R3-202926; contact: Ericsson) | RAN3 |
R2-2005992 | Reply LS on UAC applicability to IABs (S1-202274; contact: Nokia) | SA1 |
R2-2006087 | LS on IAB updates to 38.300 (R1-2004872; contact: Qualcomm) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2004688 | Stage-2 correction on RLF handling by IAB-MT | Nokia, Nokia Shanghai Bell |
R2-2004782 | Conditional handover upon BH RLF in IAB | Kyocera |
R2-2005518 | Miscellaneous correction to 37.340 for IAB | Huawei, HiSilicon |
R2-2005520 | Discussion on the R16 other WI features supporting for IAB-MT | Huawei, HiSilicon |
R2-2005672 | Applicability of Conditional Handover in IAB | Samsung R&D Institute UK |
R2-2005673 | Minor text correction for CR 38300 for IAB | Samsung R&D Institute UK |
R2-2006146 | Miscellaneous correction to 37.340 for IAB | Huawei, HiSilicon |
R2-2006210 | [AT110e][041][IAB] 3800/36300 – Open issues | Qualcomm Incorporated (Rapporteur) |
R2-2006303 | CR to 38.300 on Integrated Access and Backhaul for NR | Qualcomm (Rapporteur) |
R2-2006411 | CR to 38.300 on Integrated Access and Backhaul for NR | Qualcomm (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004593 | Some left over issues on IAB BH RLF handling | NEC Corporation |
R2-2005584 | Miscellaneous corrections to 38.340 for IAB | Huawei, HiSilicon |
R2-2005585 | Summary of email discussion [Post109bis-e][019][IAB] BAP | Huawei |
R2-2005665 | Clarification on BAP routing ID determination | LG Electronics Inc. |
R2-2005666 | Consideration on default configuration during IAB migration | LG Electronics Inc. |
R2-2005667 | TP on default and BAP routing ID determination | LG Electronics Inc. |
R2-2006226 | Summary for [AT110-e][042][IAB] BAP | Huawei, HiSilicon |
R2-2006227 | Miscellaneous corrections to 38.340 for IAB | Huawei, HiSilicon |
R2-2006408 | Miscellaneous corrections to 38.340 for IAB | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004494 | On Guard Symbol MAC CE Design | vivo |
R2-2004495 | Remaining Issues of SR Cancellation for Preemptive BSR | vivo |
R2-2004946 | Finalising Rel-16 MAC design (IAB-related open issues) | Samsung Electronics GmbH |
R2-2004948 | IAB MAC - rapporteur corrections and clarifications | Samsung |
R2-2004966 | Summary of IAB User Plane open issues and corrections | Samsung Electronics GmbH |
R2-2005521 | Adding AI-RNTI and IAB specific RACH parameters in MAC specification | Huawei, HiSilicon |
R2-2005522 | Differentiation between Pre-emptive BSR MAC CE and BSR MAC CE | Huawei, HiSilicon |
R2-2005563 | Remaining issue of SR triggered by Pre-emptive BSR | ASUSTeK |
R2-2005664 | Consideration on reserved value in two byte eLCID space | LG Electronics Inc. |
R2-2006051 | Summary of IAB User Plane open issues and corrections | Samsung Electronics GmbH |
R2-2006086 | LS response to RAN2 LS on Guard Symbols in IAB (R1-2004784; contact: Samsung) | RAN1 |
R2-2006265 | IAB MAC - rapporteur corrections and clarifications | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2005653 | Clarification of access control bypasssing | LG Electronics France |
R2-2005655 | RRC message for IP allocation | LG Electronics France |
R2-2005656 | Support of RRC_INACTIVE | LG Electronics France |
R2-2005916 | [AT110e][044][IAB] RRC CR (Ericsson) | Ericsson (Rapporteur) |
R2-2005917 | Correction to TS 38.331 for IAB WI | Ericsson |
R2-2006141 | Summary of IAB particular issues I Misc | ZTE Corporation |
R2-2006155 | Way forward on IP Address handling in IAB | Samsung |
R2-2006157 | TP for F1-C transfer path configuration | ZTE Corporation |
R2-2006211 | Draft LS on establishment cause of IAB MT access | LGE |
R2-2006319 | Summary of IAB particular issues I Misc | ZTE Corporation |
R2-2006351 | TP for TS 38.331 on IP address allocation for IAB nodes | Samsung |
R2-2006429 | Correction to TS 38.331 for IAB WI | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004607 | Report on email discussion [Post109bis-e][920][IAB] RRC 2 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004496 | RRC signaling for IP request and indication | vivo |
R2-2004608 | Remaining Issues for IP Address Allocation in IAB Network | Ericsson |
R2-2004609 | On the Issue of INACTIVE mode for IAB-MT | Ericsson |
R2-2004610 | Further Discussion on F1-AP Transport in EN-DC | Ericsson |
R2-2004687 | RRC signalling for F1-C-over-LTE/X2 path configuration | Nokia, Nokia Shanghai Bell |
R2-2004748 | IAB - establishment of F1-C over LTE | Qualcomm Incorporated |
R2-2004749 | Implications of RAN3 agreements on RRC configurations for IP- and BAP-layer | Qualcomm Incorporated |
R2-2004750 | TP for 38331 on IP address signaling | Qualcomm Incorporated |
R2-2004801 | Discussion on default UL mapping configuration during migration | ZTE, Sanechips |
R2-2004802 | Further discussion on F1-C over LTE path | ZTE, Sanechips |
R2-2004803 | Remaining issues of IP address allocation | ZTE, Sanechips |
R2-2004999 | TP for configuration on F1AP transport in EN-DC | vivo |
R2-2005157 | IP address configuration for IAB | Samsung |
R2-2005524 | TP for IP addresss signaling of IAB [ToDo RIL H698] | Huawei, HiSilicon |
R2-2005625 | Draft CR to TS 38.331 on IP address request and configuration to IAB nodes | Futurewei |
R2-2005657 | Options for IAB node address allocation using RRC | Futurewei |
TDoc | Title | Source |
---|---|---|
R2-2004612 | RIL E264 About Backhaul RLC Channel IDs | Ericsson |
R2-2004685 | Access category and establishment cause for IAB-MT [RIL: H697] | Nokia, Nokia Shanghai Bell |
R2-2004686 | Draft LS to CT1 on IAB-MT establishment cause | Nokia, Nokia Shanghai Bell |
R2-2004874 | [C501] Corrections to RRC Resume for IAB | CATT |
R2-2005406 | [C502] Corrections to IAB behavior in Determining the NPN-only Cell | CATT |
R2-2005525 | Clarification on the cause value and not supporting UAC for IAB [ToDo RIL H697] | Huawei, HiSilicon |
R2-2005526 | Default BAP configuration for non-bootstrapping cases [ToDo RIL H691] | Huawei, HiSilicon |
R2-2005527 | Suspending BAP operation at IAB-MT during RRC re-establishment, RRC inactive state [ToDo RIL H690] | Huawei, HiSilicon |
R2-2005528 | Correction on the TDD-UL-DL-ConfigDedicated-IAB-MT [ToDo RIL H696] | Huawei, HiSilicon |
R2-2005669 | [S001] Adding procedural text for smtc3 occasion derivation for IAB | Samsung R&D Institute UK |
R2-2005670 | [S002] Change of need code regarding smtc3list for IAB | Samsung R&D Institute UK |
R2-2005671 | [S003] Failure Type extension in SCGFailureInformation msg for IAB | Samsung R&D Institute UK |
TDoc | Title | Source |
---|---|---|
R2-2004373 | LS on RAN4 IAB-MT feature list agreement (R4-2005608; contact: Qualcomm) | RAN4 |
R2-2004497 | Discussion for IAB-MT Capabilities | vivo |
R2-2004498 | TP for indicator of IAB-MT class | vivo |
R2-2004611 | Allowing an IAB Configuration Without DRB | Ericsson |
R2-2004684 | Summary of e-mail discussion: [Post109bis-e][925][IAB] UE Cap (Nokia) | Nokia, Nokia Shanghai Bell |
R2-2004731 | Capability signalling and mandatory/optional features for IAB MT | Intel Corporation, KDDI, AT&T |
R2-2004804 | Considerations on IAB-MT features | ZTE, Sanechips |
R2-2004805 | Discussion on channel bandwidth for Rel-16 IAB-MT | ZTE, Sanechips |
R2-2004875 | Proposals on IAB MT Capabilities | CATT |
R2-2004977 | Further discussion on Rel-15 IAB-MT capabilities | Ericsson |
R2-2004978 | Introduction of IAB capabilities | Ericsson |
R2-2004979 | Introduction of IAB capabilities | Ericsson |
R2-2005226 | Support of Rel-15 UE features by IAB-MTs | AT&T |
R2-2005519 | Discussion on inapplicable features for IAB | Huawei, HiSilicon |
R2-2005654 | Capabilities of IAB MTs | LG Electronics France |
R2-2006032 | Capability signalling and mandatory/optional features for IAB MT | Intel Corporation, KDDI, AT&T, Kyocera, Apple |
R2-2006049 | Summary of Phase 1 of e-mail discussion: [AT110e][048][IAB] UE capabilities (Nokia) | Nokia, Nokia Shanghai Bell |
R2-2006094 | Reply LS on RAN4 IAB-MT feature list agreement (R1-2004954; contact: Qualcomm) | RAN1 |
R2-2006128 | Reply LS on IAB-MT Features (R4-2009051; contact: Qualcomm) | RAN4 |
R2-2006161 | E-mail discusson: [AT110-e][047][IAB] Particular issues III UAC | LG Electronics |
TDoc | Title | Source |
---|---|---|
R2-2004780 | Better cell selection for IAB Nodes | Apple |
R2-2004783 | Remaining issue on idle mode procedure for IAB-MT | Kyocera |
R2-2004784 | Corrections to 38.331 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
R2-2004785 | Corrections to 38.304 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
R2-2004876 | Remaining issues of IAB in NPN | CATT |
R2-2005142 | PWS information handling in IAB | Sony |
R2-2005516 | Miscellaneous corrections to 38.304 for IAB | Huawei, HiSilicon |
R2-2005517 | Miscellaneous corrections to 36.304 for IAB | Huawei, HiSilicon |
R2-2005523 | Correction on RLC spec to support the BAP as upper layer | Huawei, HiSilicon |
R2-2006145 | Summary of offline discussion [AT110e][049][IAB] Other | Huawei |
R2-2006147 | Corrections to 38.331 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
R2-2006148 | Corrections to 38.304 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
R2-2006149 | Miscellaneous correction to 38.304 for IAB | Huawei, HiSilicon |
R2-2006150 | Miscellaneous correction to 36.304 for IAB | Huawei, HiSilicon |
R2-2006151 | Correction on RLC spec to support the BAP as upper layer | Huawei, HiSilicon |
R2-2006165 | Reply LS on IAB supporting in NPN deployment (S2-2004469; contact: Qualcomm) | SA2 |
R2-2006258 | Miscellaneous corrections to 38.304 for IAB | Huawei, HiSilicon |
R2-2006320 | Corrections to 38.331 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
R2-2006321 | Corrections to 38.304 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
TDoc | Title | Source |
---|---|---|
R2-2004315 | LS on intra-cell guard band configuration for NR-U (R1-2002908; contact: LGE) | RAN1 |
R2-2004351 | LS to RAN2 on NR-U ARFCN restriction for CGI reading (R1-2003032; contact: Qualcomm) | RAN1 |
R2-2004352 | LS on aligning RRC parameter list with TS38.213 (R1-2003040; contact: Lenovo) | RAN1 |
R2-2004354 | LS on Signaling of Q Parameter for NR-U (R1-2003044; contact: Charter Communications) | RAN1 |
R2-2004359 | LS to RAN2 on clarification of RVID for the first transmission for CG-PUSCH (R1-2003074; contact: Qualcomm) | RAN1 |
R2-2004369 | LS on UE declaring beam failure due to LBT failur+B70:V70es during active TCI switching (R4-2005365; contact: Ericsson) | RAN4 |
R2-2004370 | LS on timing reference cell adjustment under NR-U (R4-2005373; contact: ZTE) | RAN4 |
R2-2004422 | Running CR to 38.306 on Introducing UE Capability for NR Shared Spectrum | vivo |
R2-2004544 | Deployment Scenarios for NR-U | Qualcomm Incorporated, Nokia |
R2-2004725 | [Draft] Reply LS on RVID selection for CG-PUSCH | Qualcomm Incorporated |
R2-2004829 | [Draft] Reply LS on NR-U ARFCN restriction for CGI reading | Qualcomm Incorporated |
R2-2004864 | ARFCN restriction for CGI reading | Qualcomm Incorporated |
R2-2005331 | Corrections of NR operating with shared spectrum channel access in 38.321 | Ericsson, Nokia |
R2-2005332 | Corrections of NR operating with shared spectrum channel access in 38.321 | Ericsson, Nokia |
R2-2005334 | LS reply to RAN4 on UE declaring beam failure due to LBT failures during active TCI switching | Ericsson |
R2-2005851 | LS reply to RAN4 on UE declaring beam failure due to LBT failures during active TCI switching | RAN2 |
R2-2005852 | Reply LS on RVID selection for CG-PUSCH | RAN2 |
R2-2005853 | Corrections of NR operating with shared spectrum channel access in 38.321 | Ericsson, Nokia |
R2-2005859 | Running CR to 38.306 on Introducing UE Capability for NR Shared Spectrum | vivo |
R2-2005860 | Running CR to 38.306 on Introducing UE Capability for NR Shared Spectrum | vivo |
R2-2005864 | UE capabilities for NR Shared Spectrum | Qualcomm Incorporated (Rapporteur) |
R2-2005870 | UE capabilities for NR Shared Spectrum | Qualcomm Incorporated |
R2-2006072 | [AT110-e][501][NR-U] CP Open and ASN.1 Issues (Qualcomm) | Qualcomm Incorporated |
R2-2006073 | Miscellaneous corrections for NR operation with shared spectrum | Qualcomm Incorporated, Nokia |
R2-2006090 | LS to RAN2 on NR-U RSSI Measurement Duration (R1-2004915; contact: Charter Communications) | RAN1 |
R2-2006095 | LS on UE capability on wideband carrier operation for NR-U (R1-2004965; contact: MediaTek) | RAN1 |
R2-2006099 | LS to RAN2 on initial BWP for NR-U (R1-2004998; contact: Ericsson) | RAN1 |
R2-2006102 | LS to RAN2 on initial BWP for NR-U (R1-2005016; contact: Ericsson) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2004419 | Discussion on LBT Failure Detection and Recovery During HO with DAPS and CHO | vivo |
R2-2004420 | LBT Impacts on the TCI State Switching | vivo |
R2-2004421 | [Draft] Reply LS on UE Declaring Beam Failure due to LBT Failures During Active TCI Switching | vivo |
R2-2004425 | Clarification on when to use one-octet or four-octet LBT failure MAC CE | Samsung |
R2-2004426 | Clarification on the variable LBT_COUNTER | Samsung |
R2-2004549 | Remaining issues on UL LBT failure | OPPO |
R2-2004598 | Discussion about LBT failure and beam failure relation | Nokia, Nokia Shanghai Bell |
R2-2004599 | Draft Reply LS on UE declaring beam failure due to LBT failures | Nokia, Nokia Shanghai Bell |
R2-2004616 | UE declaring beam failure due to LBT failures during active TCI switching | ZTE Corporation, Sanechips |
R2-2004659 | UL LBT failures interactions with DAPS and CHO | Intel Corporation |
R2-2004660 | Draft CR for UL LBT failures under DAPS handover | Intel Corporation |
R2-2004671 | Beam failure declaration due to TC switching failure | Intel Corporation |
R2-2004974 | LBT failure recovery for DAPS and CHO | Huawei, HiSilicon |
R2-2004975 | Remaining issue on 2-step random access for NRU | Huawei, HiSilicon |
R2-2004976 | DraftCR on pending status for HARQ process in NR-U | Huawei, HiSilicon |
R2-2005049 | Consistent LBT failure in DAPS | Spreadtrum Communications |
R2-2005050 | Consistent LBT failure in CHO | Spreadtrum Communications |
R2-2005053 | Text Proposal | Huawei, HiSIlicon |
R2-2005054 | Text proposal for the pending status for HARQ process in NR-U | Huawei, HiSilicon |
R2-2005329 | LBT failure detection and recovery for DAPS and CHO | Ericsson |
R2-2005330 | UE declaring beam failure due to LBT failures during active TCI switching | Ericsson |
R2-2005333 | Report on [Post109bis-e][935]][NR-U] MAC open issues (Ericsson) | Ericsson |
R2-2005550 | Handling of UL LBT failure for DAPS and CHO | Qualcomm Incorporated |
R2-2005713 | Consideration on DAPS and CHO in NR-U | ZTE Corporation, Sanechips |
R2-2006084 | Summary of NR-U User plane | Lenovo |
TDoc | Title | Source |
---|---|---|
R2-2004529 | Consistent LBT Failure Handling during Handover | Samsung Electronics Co., Ltd |
R2-2004543 | White listed cells for reselection to NR-U | Qualcomm Incorporated (Rapporteur) |
R2-2004545 | Miscellaneous corrections for NR-U | Qualcomm Incorporated (Rapporteur) |
R2-2004546 | Miscellaneous corrections for NR-U | Qualcomm Incorporated |
R2-2004615 | Consideration on Multiple CG Support in NR-U | ZTE Corporation, Sanechips |
R2-2004622 | Signalling related to the extended RAR window | Ericsson |
R2-2004694 | On Applicability of DAPS Handover in NR-U | MediaTek Inc. |
R2-2004696 | On Conditional Handover in NR-U | MediaTek Inc. |
R2-2004799 | Report of [Post109bis-e][936][NR-U] RRC open issues | Qualcomm Incorporated |
R2-2004800 | Mobility to NR operating with shared spectrum access | Qualcomm Incorporated |
R2-2004839 | U624, U613 and discussion on the RAN1 LS R1-2003040 on the searchSwitchTrigger ASN.1 coding | Nokia, Nokia Shanghai Bell |
R2-2004840 | non numbered issue on ra-responseWindow | Nokia, Nokia Shanghai Bell |
R2-2004990 | [H541-544] Text proposal for SlotFormatIndicator | Huawei, HiSilicon |
R2-2004991 | [H544][H548] DraftCR for COT sharing in configured grant | Huawei, HiSilicon |
R2-2004992 | [H546][H547] DraftCR for ffsValue in ConfiguredGrantConfig | Huawei, HiSilicon |
R2-2005617 | Discussion on issues with DAPS in NR-U | LG Electronics Deutschland |
R2-2005698 | Paging stop indication in TS 38.331 | LG Electronics Inc. |
R2-2005699 | Correction on triggering RSSI measurement report | LG Electronics Inc. |
R2-2005842 | Miscellaneous corrections for NR-U | Qualcomm Incorporated (Rapporteur) |
R2-2005865 | LS to RAN1 on signalling SFN bits for random access response | RAN2 |
R2-2006031 | Signalling related to the extended RAR window | Ericsson, Samsung |
R2-2006035 | [DRAFT] LS to RAN1 on signalling SFN bits for random access response | Ericsson |
R2-2006143 | [DRAFT] LS to RAN1 on signalling SFN bits for random access response | Ericsson, Samsung, Huawei, Nokia |
R2-2006144 | Signalling related to the extended RAR window | Ericsson, Samsung, Huawei, Nokia |
R2-2006230 | [DRAFT] LS to RAN1 on signalling SFN bits for random access response | Ericsson, Samsung, Huawei, Nokia, ZTE |
R2-2006368 | Mobility to NR operating with shared spectrum access | Qualcomm Incorporated (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004312 | LS on the 3GPP work on the NR sidelink (S-200078; contact: VolksWagen) | 5GAA WG4 |
R2-2004314 | LS on LTE V2X capabilities in NR V2X (R1-2002930; contact: Huawei) | RAN1 |
R2-2004316 | LS reply to RAN WG2 LS on NR V2X Security issues (S3-200820; contact: CATT) | SA3 |
R2-2004336 | Reply LS to RAN2 on Sidelink UE Information (R3-202831; contact: LGE) | RAN3 |
R2-2004343 | LS on HARQ parameters for Mode 1 (R1-2002848; contact: Ericsson) | RAN1 |
R2-2004348 | LS on sidelink HARQ operations (R1-2002985; contact: LGE) | RAN1 |
R2-2004349 | LS on sidelink CSI report (R1-2002986; contact: LGE) | RAN1 |
R2-2004350 | LS on NR V2X Slot number determination (R1-2002990; contact: CATT) | RAN1 |
R2-2004374 | Reply LS on Sidelink UE capability for (NG)EN-DC and NE-DC (R4-2005646; contact: CATT) | RAN4 |
R2-2004576 | (draft)Reply LS on sidelink HARQ operations | ZTE Corporation, Sanechips |
R2-2004982 | [draft]Reply LS on sidelink HARQ operations | CATT |
R2-2005075 | Correction on NR sidelink description | Ericsson, Nokia |
R2-2005229 | [DRAFT] LS response to RAN1 on Sidelink HARQ operation | Intel Corporation |
R2-2005299 | Draft LS response on sidelink HARQ operations | vivo |
R2-2005727 | LS reply to RAN WG2 LS on the security related issues for NR SL (S3-201483; contact: CATT) | SA3 |
R2-2005964 | Reply LS on sidelink HARQ operations | RAN2 |
R2-2006091 | LS reply to RAN2 on Cast type indication and MAC agreements (R1-2004916; contact: LGE) | RAN1 |
R2-2006092 | Reply on LS on RAN1 views on sidelink (R1-2004921; contact: Ericsson) | RAN1 |
R2-2006100 | LS to RAN2 on resource allocation Mode-2 agreements related to QoS requirements (R1-2005009; contact: Intel) | RAN1 |
R2-2006101 | LS to RAN2 on SL_RESOURCE_RESELECTION_COUNTER and period value provided to L1 (R1-2005010; contact: Intel) | RAN1 |
R2-2006133 | Reply LS to RAN2 on UL-SL Prioritization (R4-2009150; contact: Futurewei) | RAN4 |
TDoc | Title | Source |
---|---|---|
R2-2005466 | TP for final clean-up on RAN2 part in TR 37.985 | Huawei, HiSilicon |
R2-2005966 | TP for final clean-up on RAN2 part in TR 37.985 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004401 | Left issues on RRC running CR [O311, O312, O315] | OPPO |
R2-2004404 | Correction on SL configuration procedure | OPPO |
R2-2004485 | R2-20xxxxx_Introduction of segementation for SIB12 | OPPO |
R2-2004486 | R2-20xxxxx_Introduction of segementation for SIB28 | OPPO |
R2-2004487 | Summary of [Post109bis-e][954][V2X] SIB12 overhead reduction (OPPO) | OPPO |
R2-2004525 | Corrections to Interruption handling during RLF | Samsung Electronics Co., Ltd |
R2-2004577 | Discussion on remaining issue related to RRC in NR V2X | ZTE Corporation, Sanechips |
R2-2004596 | Remaining issues on RRC for NR V2X | Nokia, Nokia Shanghai Bell |
R2-2004712 | Size of sl-PSFCH-RB-Set in SIB12 [M117] | MediaTek Inc. |
R2-2004760 | Introduction of Sidelink Counter Check Procedure | Apple |
R2-2004899 | [C402] Correction on (Re)Selection of Synchronisation Reference | CATT |
R2-2004901 | [C402] Correction on (Re)Selection of Synchronisation Reference | CATT |
R2-2004911 | [C403] The Detail of Slot Number Determination in 38.331 | CATT |
R2-2004919 | [C401]New RRC connection establishment trigger | CATT |
R2-2004920 | [C401]New RRC connection establishment trigger | CATT |
R2-2004921 | [C401]New RRC connection establishment trigger | CATT |
R2-2004931 | [C401]New RRC connection establishment trigger | CATT |
R2-2004933 | [C401]New RRC connection establishment trigger | CATT |
R2-2004934 | [C401]New RRC connection establishment trigger | CATT |
R2-2004935 | [C401]New RRC connection establishment trigger | CATT |
R2-2004937 | [C404]Issue on consistent zone configuration | CATT |
R2-2005131 | [B103] TP for sidelink transmission during fast MCG link recovery | Lenovo, Motorola Mobility |
R2-2005132 | [B104] TP for sidelinkUEinformation with fast MCG link recovery | Lenovo, Motorola Mobility |
R2-2005179 | [E261] Miscellaneous corrections for NR V2X | Ericsson |
R2-2005180 | [E212] Correction to addModList for SL measurements | Ericsson |
R2-2005293 | Sidelink communication reception (RIL#V022) | vivo |
R2-2005294 | Align RRC and SA2 spec on sidelink SRB handling (RIL#V023) | vivo |
R2-2005295 | UE behavior upon detecting sidelink SRB integrity check failure (RIL#V024) | vivo |
R2-2005310 | Need codes in sl-RxPool [M114] | MediaTek Inc. |
R2-2005326 | Corrections to SUI and RRCReconfigurationSidelink | InterDigital |
R2-2005327 | Configuration of HARQ Enable for NR V2X | Interdigital |
R2-2005461 | [H335] SR configuration for SL SRB | Huawei, HiSilicon |
R2-2005462 | [H336] Discussion on security policy related aspects for NR SL unicast | Huawei, HiSilicon |
R2-2005463 | [H352] Handling of integrity check failure in RRC for NR SL unicast | Huawei, HiSilicon |
R2-2005491 | Corrections on V2X functionalities in TS 36.331 | Huawei, Hisilicon |
R2-2005495 | Miscellaneous corrections to 38.331 for V2X | Huawei, HiSilicon |
R2-2005496 | Summary of email discussion [952][V2X] RRC ASN.1 issues-38.331 | Huawei, HiSilicon |
R2-2005530 | Discussion on Interoperability of V2X UEs camped in different cells | Apple, InterDigital Inc. |
R2-2005542 | Remaining issues for NR SL preconfiguation parameters | Qualcomm Finland RFFE Oy |
R2-2005544 | Sidelink PDCP out of order delivery configuration | Samsung Electronics Co., Ltd |
R2-2005545 | Configuration of remaining ROHC related parameters | Samsung Electronics Co., Ltd |
R2-2005546 | Clarification of SLRB configuration procedures | Samsung Electronics Co., Ltd |
R2-2005615 | Left issues on RRC for NR V2X | LG Electronics France |
R2-2005711 | Summary document of AI 6.4.2.1 - RRC aspects | Huawei, HiSilicon |
R2-2005951 | Miscellaneous corrections to 38.331 for V2X | Huawei, HiSilicon |
R2-2005952 | Corrections on V2X functionalities in TS 36.331 | Huawei, HiSilicon |
R2-2005965 | Summary of offline discussion [701][V2X] V2X RRC ASN.1 issues | Huawei, HiSilicon |
R2-2006430 | Corrections on V2X functionalities in TS 36.331 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004402 | Summary of [Post109bis#955] V2X UE capability issues (OPPO) | OPPO |
R2-2004403 | Summary of capability related Tdoc submitted to R2#109bis-E | OPPO |
R2-2004578 | Report of summary on NR V2X cell (re-)selection remaining issues | ZTE Corporation, Sanechips |
R2-2004579 | (draft)Running CR on TS 38.304 for remaining NR V2X cell (re-)selection issues | ZTE Corporation, Sanechips |
R2-2004597 | On the peer UE capability transfer in unicast sidelink | Nokia, Nokia Shanghai Bell |
R2-2004761 | Discussion on SL Capability | Apple |
R2-2004798 | (draft)Running CR on TS 36.304 for remaining NR V2X cell (re-)selection issues | ZTE Corporation, Sanechips |
R2-2005044 | TX resource pool configuration in mode1 | Spreadtrum Communications |
R2-2005076 | Correction for reselection priority handling for V2X communications in 36.304 | Ericsson, ZTE, Sanechips |
R2-2005077 | Correction for reselection priority handling for V2X communications in 38.304 | Ericsson, ZTE, Sanechips |
R2-2005127 | Remaining issues of cell (re)selection for NR V2X | Lenovo, Motorola Mobility |
R2-2005133 | TP for 38.300 Conditional handover with sidelink | Lenovo, Motorola Mobility |
R2-2005208 | Remaining issue on groupcast RRC state transition and future p-t-M delivery | ITRI |
R2-2005296 | Discussion on SL UE capability details | vivo |
R2-2005465 | Miscellaneous Stage-2 corrections for NR SL communication in TS 38.300 | Huawei, HiSilicon |
R2-2005480 | Miscellaneous Stage-2 corrections for NR SL communication in TS 36.300 | Huawei, HiSilicon |
R2-2005547 | Discussion for Sidelink UE Capability | Samsung Electronics Co., Ltd |
R2-2005587 | Coverage status condition for NR sidelink communication transmission | Samsung Electronics Co., Ltd |
R2-2005721 | Summary of NR V2X cell (re-)selection related contributions for RAN2 #110e | ZTE Corporation, Sanechips |
R2-2005953 | CR on PC5 capability on PC5-RRC and Uu-RRC (focusing on L2 capability) | OPPO |
R2-2005954 | CR on PC5 capability on PC5-RRC and Uu-RRC (focusing on L2 capability) | OPPO |
R2-2005955 | Summary of open issue for V2X capability (OPPO) | OPPO |
R2-2005957 | Correction for NR sidelink communication | Ericsson |
R2-2005958 | Correction for NR sidelink communication | Ericsson |
R2-2005959 | CR for NR V2X UE capability | OPPO |
R2-2005960 | CR for NR V2X UE capability | OPPO |
R2-2005967 | Correction for NR sidelink communication | Ericsson |
R2-2005968 | Correction for NR sidelink communication | Ericsson |
R2-2005969 | Draft Running CR on cell (re)selection for sidelink in TS 38.304 | ZTE Corporation, Sanechips |
R2-2005972 | Draft running CR on cell (re)selection for sidelink in TS 36.304 | ZTE Corporation, Sanechips |
R2-2005973 | Draft-CR for V2X UE capability (focusing on RAN2 capability) | OPPO |
R2-2005974 | Draft-CR for V2X UE capability (focusing on RAN2 capability) | OPPO |
R2-2005975 | LS on RAN2 NR V2X cell (re-)selection related agreements | RAN2 |
R2-2005979 | CR on cell (re)selection for sidelink in TS 38.304 | ZTE Corporation, Sanechips |
R2-2005980 | CR on cell (re)selection for sidelink in TS 36.304 | ZTE Corporation, Sanechips |
R2-2005981 | CR on cell (re)selection for sidelink in TS 38.304 | ZTE Corporation, Sanechips |
R2-2005982 | CR on cell (re)selection for sidelink in TS 36.304 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2005036 | LS on sidelink HARQ operations | Lenovo, Motorola Mobility |
TDoc | Title | Source |
---|---|---|
R2-2004406 | Left issues on MAC running CR | OPPO |
R2-2004520 | Discussion on SL CSI report trigger | SHARP |
R2-2004580 | Discussion on remaining issue related to NR V2X MAC | ZTE Corporation, Sanechips |
R2-2004751 | Remaining issues for MAC | MediaTek Inc. |
R2-2004759 | Discussion on remaining issues on NR V2X MAC | Apple |
R2-2004889 | Discussion on NR-V2X MAC left issues | Fujitsu |
R2-2004941 | Open issue on mixing blind and feedback-based HARQ retransmissions of a TB in the sidelink HARQ operations | CATT |
R2-2004968 | Open issue on mixing blind and feedback-based HARQ retransmissions of a TB in the sidelink HARQ operations | CATT |
R2-2004980 | Discussion on mixed blind and HARQ-based retransmissions | CATT |
R2-2004981 | Discussion on mixed blind and HARQ-based retransmissions | CATT |
R2-2004998 | Remaining issues in MAC for NR sidelink | Nokia, Nokia Shanghai Bell |
R2-2005039 | Remaining MAC Issues | Lenovo, Motorola Mobility, InterDigital Inc. |
R2-2005042 | Remaining issues on MAC for NR V2X | Spreadtrum Communications |
R2-2005043 | Discussion on mixed blind and feedback-based HARQ retransmissions for NR sidelink | Spreadtrum Communications |
R2-2005074 | Discussion on MAC left issues | Ericsson |
R2-2005207 | Groupcast HARQ feedback without location information | Kyocera |
R2-2005228 | On mixing of blind and feedback based HARQ retransmissions | Intel Corporation |
R2-2005297 | Remaining MAC issues | vivo |
R2-2005325 | Remaining Issues on HARQ for NR V2X | InterDigital, Apple, Lenovo, Motorola Mobility |
R2-2005492 | Discussion on remaining MAC Open issues for 5G V2X with NR SL | Huawei, Hisilicon |
R2-2005515 | Groupcast HARQ feedback from RX UE without location information | Futurewei |
R2-2005541 | Remaining V2X MAC Issues | LG Electronics France |
R2-2005564 | Left NR V2X issues regarding SL MAC CE | ASUSTeK |
R2-2005575 | Remaining MAC issues | Qualcomm Finland RFFE Oy |
R2-2005705 | Discussion on BSR prioritization issue | Beijing Xiaomi Software Tech |
R2-2005719 | [Post109e#22] CR to 38.321 on Corrections to NR sidelink | LG Electronics Inc. |
R2-2005720 | Report of [Post109bis-e][957][V2X] MAC issues | LG Electronics Inc. |
R2-2005725 | Summary of V2X MAC issues | LG Electronics |
R2-2005956 | [Offline Disc#704] Identified proposals to V2X MAC open issues | LG Electronics Inc. (Rapporteur) |
R2-2005970 | Corrections to 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2005971 | Corrections to 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2005977 | LS to RAN1 on physical layer related agreements | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004581 | Discussion on the establishment-release of the Rx SDAP entity | ZTE Corporation, Sanechips |
R2-2004747 | Remaining Issues on PDCP | CATT |
R2-2004881 | Draft LS on trigger of PDCP reestablishment | OPPO |
R2-2004888 | 38.323 CR for NR V2X | CATT |
R2-2005045 | Discussion on counter check procedure for NR sidelink | Spreadtrum Communications |
R2-2005055 | Remaining issues in PDCP for NR sidelink | Nokia, Nokia Shanghai Bell |
R2-2005298 | Open issues on NR V2X SDAP | vivo |
R2-2005343 | Remaining issues for NR SL PDCP header format | Qualcomm Finland RFFE Oy |
R2-2005464 | Discussion on PDCP SN size for SL groupcast and broadcast in NR V2X | Huawei, MediaTek Inc.,HiSilicon |
R2-2005548 | Clarification of SL PDCP Operation | Samsung Electronics Co., Ltd |
R2-2005677 | Summary of NR V2X SDAP related contribution | vivo |
R2-2005724 | Summary of PDCP remaining issues on NR V2X | CATT |
R2-2005961 | Capture latest agreements on SDAP | vivo |
R2-2005962 | Summary of [706][V2X] PDCP remaining issues (CATT) | CATT (rapporteur) |
R2-2005963 | 38.323 CR for NR V2X | CATT |
R2-2005976 | Summary of [706][V2X] PDCP remaining issues (CATT) | CATT (rapporteur) |
R2-2005978 | LS on the re-keying procedure for NR SL | RAN2 |
R2-2006182 | Summary of NR V2X SDAP related contribution | vivo |
R2-2006431 | Capture latest agreements on SDAP | vivo |
TDoc | Title | Source |
---|---|---|
R2-2004321 | Reply LS on RACS and signalling of UE capabilities at handover (S2-2003483; contact: Ericsson) | SA2 |
R2-2004324 | LS on different coding formats (S2-2003507; contact: Samsung) | SA2 |
R2-2004710 | Correction to transfer of UE capabilities at HO for RACS and correction of ASN.1 review issues [N012] [N013] | MediaTek Inc., Ericsson, ZTE Corporation, Sanechips |
R2-2004711 | Work plan for RACS-RAN work item | MediaTek Inc., CATT |
R2-2005539 | Correction to transfer of UE capabilities at HO for RACS and minor ASN.1 correction (38.331) | ZTE Corporation, Ericsson, MediaTek Inc.,Sanechips,OPPO |
R2-2005802 | Correction to transfer of UE capabilities at HO for RACS and minor ASN.1 correction (38.331) | ZTE Corporation, Ericsson, MediaTek Inc.,Sanechips,OPPO |
TDoc | Title | Source |
---|---|---|
R2-2004675 | Summary of IIOT WI agreements and open issues | Nokia (rapporteur) |
R2-2006088 | Reply LS on Intra-UE Prioritization (R1-2004899; contact: LGE) | RAN1 |
R2-2006104 | LS on Intra-UE Prioritization for data with different priorities (R1-2005078; contact: vivo) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2004585 | Open issues on Accurate Reference Timing | CATT |
R2-2004676 | Remaining issues for accurate reference time request | Nokia, Nokia Shanghai Bell |
R2-2004736 | Remaining issues on the UE request of the reference time | vivo |
R2-2004830 | Remaining issues on Accurate Reference timing | NTT DOCOMO, INC. |
R2-2004957 | Remaining details on UE request of reference time | Ericsson |
R2-2005040 | FFS for UE request for accurate reference timing | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2005152 | Request of accurate reference time delivery | Huawei, HiSilicon |
R2-2005300 | On UE request of reference time provisioning | Intel Corporation |
R2-2005340 | Discussion on the need of prohibit timer and retransmission of the same interest message | OPPO |
R2-2005646 | Confirmation of UE assistance with referenceTimeInfoInterest | Samsung |
R2-2006050 | Report of email discussion [AT110-e][053][IIOT] Accurate Reference Time (NTT DOCOMO) | NTT DOCOMO, INC. |
TDoc | Title | Source |
---|---|---|
R2-2004590 | [C601] PDCP Duplication Configuration in MR-DC | CATT |
R2-2004953 | Way forward for class 3 RIL issues | Ericsson |
R2-2004954 | Email discussion summary [AT110e][054][IIOT] RRC (Ericsson) | Ericsson |
R2-2004955 | Correction of NR IIoT | Ericsson (Rapporteur) |
R2-2004956 | Correction of NR IIoT | Ericsson (Rapporteur) |
R2-2004958 | [E225] On simplification for PDCP-duplication | Ericsson |
R2-2005155 | correction IIoT | Huawei, HiSilicon |
R2-2005156 | correction IIoT | Huawei, HiSilicon |
R2-2005649 | Radio Bearer with More than Two RLC Entities for Downlink Duplication or Split [E225] | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2005645 | Report of [Post109bis-e][913][IIOT] MAC Remaining issues | Samsung |
R2-2005652 | Correction for NR IIOT in 38.321 | Samsung |
R2-2006046 | Report of [AT110e][055][IIOT] MAC: Part 1A | Samsung |
R2-2006243 | Report of [AT110e][055][IIOT] MAC: Part 1B | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004586 | Impacts of independent configuration of intra-UE prioritization in PHY and MAC layers | CATT |
R2-2004587 | Considerations on SR Prioritization | CATT |
R2-2004588 | MAC TP addressing PHY limitations for equal-priority collisions | CATT |
R2-2004738 | Priority of SR triggered by BFR or LBT failure | vivo, ZTE corporation, OPPO |
R2-2004739 | Text proposal for the UE autonomous retransmission | vivo, Samsung |
R2-2004885 | Avoid providing second MAC PDU with the same L1 priority to PHY | SHARP Corporation |
R2-2004890 | On prioritization handling for PUSCH and PUSCH with the same L1 priority | Fujitsu |
R2-2004891 | On prioritization handling for SR and PUSCH with the same L1 priority | Fujitsu |
R2-2004900 | Handling of autonomous transmissions following a BWP switch | Lenovo, Motorola Mobility |
R2-2004922 | Intra-UE Prioritization with the Same L1-Priority | Nokia, Nokia Shanghai Bell |
R2-2004923 | Handling of Absence of PHY-based or LCH-based prioritization configuration | Nokia, Nokia Shanghai Bell |
R2-2004959 | On interaction between LCH-based and PHY-based prioritization | Ericsson |
R2-2004960 | Remaining issues on intra-UE priortization | Ericsson |
R2-2004961 | CG/SPS remaining issues | Ericsson |
R2-2005070 | Discussion on LCH-based prioritization and PHY-based prioritization | Huawei, HiSilicon |
R2-2005124 | Consideration on the intra-UE multiplexing involved SR | ZTE, Sanechips |
R2-2005149 | Remaining issues of Intra-UE prioritizations | Sony |
R2-2005337 | Open issues on intra-UE prioritization | OPPO |
R2-2005503 | Intra-UE prioritization with the same L1 priority | LG Electronics Inc. |
R2-2005565 | SR-data prioritization regarding MAC CE-triggered SR | ASUSTeK |
R2-2005566 | Handling UL grant prioritization with non-overlapping PUSCH duration | ASUSTeK |
R2-2005647 | MAC Impact of MAC-PHY Misalignment in Prioritization | Samsung |
R2-2005648 | Correction to Prioritization between SR and Random Access Related Uplink Grant | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004677 | Periodicities of multiple of 2 or 7 symbols for CG | Nokia, Nokia Shanghai Bell, Ericsson, NTT Docomo, CMCC, CATT, Sony |
R2-2004737 | Clarification on the suspension of the CG type-1 | vivo |
R2-2005051 | Handling of collision involving measurement gap | Spreadtrum Communications |
R2-2005338 | Open issues on scheduling enhancement | OPPO |
R2-2005339 | Discussion on remaining issues for Type-1 CG | OPPO |
R2-2005613 | Discussion on the open issue for CG type 1 | CMCC |
R2-2006039 | Report of [AT110-e][056][IIOT] Scheduling Enhancements (vivo) | vivo |
TDoc | Title | Source |
---|---|---|
R2-2005504 | 38323 CR NR PDCP corrections for NR IIOT | LG Electronics Inc. |
R2-2005505 | 36323 CR LTE PDCP corrections for NR IIOT | LG Electronics Inc. |
R2-2006224 | NR PDCP corrections for NR IIOT | LG Electronics Inc. |
R2-2006225 | LTE PDCP corrections for NR IIOT | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2004589 | Control of Duplication by Rel-16 Duplication MAC CE | CATT |
R2-2004740 | Clarification on the RRC-based activation of PDCP duplication | vivo |
R2-2004887 | Configuration of PDCP duplication (discuss issues raised in E225) | SHARP Corporation |
R2-2004892 | MAC update on R15 MAC CE not used for moreThanTwoRLC | Fujitsu |
R2-2004924 | Issues with Network Coordination for PDCP Duplication | Nokia, Nokia Shanghai Bell |
R2-2005068 | Clarification of DC+CA duplication definition | Huawei, HiSilicon |
R2-2005506 | Indication of PDCP duplication configuration | LG Electronics Inc. |
R2-2005650 | Clarification on Initial State of PDCP Duplication in IIOT | Samsung |
R2-2005723 | Summary of AI 6.7.4.1 PDCP duplication | LG Electronics Inc. |
R2-2006066 | [AT110e][045][IIOT] PDCP Duplication and PDCP CRs | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2004542 | Remaining Issues in Ethernet Header Compression | III |
R2-2004678 | EHC remaining issues | Nokia, Nokia Shanghai Bell |
R2-2004679 | Clarification on Ethernet frame handling by EHC | Nokia, Nokia Shanghai Bell, ZTE Corporation |
R2-2004742 | Corrections on the EHC | vivo |
R2-2004962 | Remaining EHC issues | Ericsson |
R2-2005041 | Remaining FFS for EHC in TSC | ZTE Corporation, Sanechips |
R2-2005147 | Switching from Compressed header in EHC to Full header | Sony |
R2-2005154 | Remaining issues about EHC | Huawei, HiSilicon |
R2-2005336 | Open issues on EHC | OPPO |
R2-2005589 | Summary on Ethernet Header Compression | Intel Corporation |
R2-2006058 | Report of email discussion [AT110-e][058][IIOT] EHC (Intel) | Intel Corporation |
R2-2006142 | Report of phase 2 of email discussion [AT110-e][058][IIOT] EHC (Intel) | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2005067 | Introduction of IIOT features to TS 37.340 | Huawei, HiSilicon |
R2-2005162 | Stage-2 updates for IIOT | Nokia, Nokia Shanghai Bell |
R2-2005181 | Stage-2 updates for IIOT (36.300) | Nokia, Nokia Shanghai Bell |
R2-2006288 | Introduction of IIOT features to TS 37.340 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004591 | Capability constraints on the number of DRBs in IIoT | CATT |
R2-2004680 | UE feature list and capabilities remaining issues | Nokia, Nokia Shanghai Bell |
R2-2004681 | Summary of Tdocs on IIOT UE capabilities (AI 6.7.6) | Nokia, Nokia Shanghai Bell |
R2-2004682 | Draft CR for IIOT capabilities introduction to TS 38.331 | Nokia, Nokia Shanghai Bell |
R2-2004683 | IIOT capabilities introduction to TS 36.331 | Nokia, Nokia Shanghai Bell |
R2-2004741 | Remaining issues on the UE capability of IIOT | vivo |
R2-2004779 | Supported Number of DRBs and RLC entities for R16 PDCP Duplication Enhancement | Apple |
R2-2004963 | UE capability for IIoT | Ericsson |
R2-2005069 | Discussion on requirements of the number of DRBs and RLC bearers | Huawei, HiSilicon |
R2-2005128 | Configuration of the additional RLC entities | Lenovo, Motorola Mobility |
R2-2005153 | Discussion about remaining issues on scheduling enhancements | Huawei, HiSilicon |
R2-2005158 | UE radio access capabilities introduction for IIOT WI (CR for 36.306) | Nokia, Nokia Shanghai Bell |
R2-2005183 | UE radio access capabilities introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2005301 | Remaining issues in IIoT UE capability | Intel Corporation |
R2-2005335 | How to capture maximum number of SPS/CG per MAC | OPPO, vivo |
R2-2005341 | Feasibility of additional RLC entities to be configured for duplication | OPPO |
R2-2005507 | Relation between LCH-based and PHY-based prioritization | LG Electronics Inc. |
R2-2005508 | Capability signaling for Joint EHC-ROHC operation | LG Electronics Inc. |
R2-2005509 | Number of DRBs for duplication | LG Electronics Inc. |
R2-2005651 | Remaining UE Capability Issues for IIOT | Samsung |
R2-2005679 | Necessity of UE capability for simultaneous EHC and RoHC | NTT DOCOMO INC. |
R2-2006048 | Summary of Phase 1 of e-mail discussion: [AT110e][048][IIOT] UE capabilities (Nokia) | Nokia, Nokia Shanghai Bell |
R2-2006293 | Draft CR for IIOT capabilities introduction to TS 38.331 | Nokia, Nokia Shanghai Bell |
R2-2006294 | IIOT capabilities introduction to TS 36.331 | Nokia, Nokia Shanghai Bell |
R2-2006295 | Summary of Phase 2 of e-mail discussion: [AT110e][048][IIOT] UE capabilities (Nokia) | Nokia, Nokia Shanghai Bell |
R2-2006296 | Draft CR for IAB capabilities introduction to TS 38.331 | Nokia, Nokia Shanghai Bell |
R2-2006297 | UE radio access capabilities introduction for IAB WI (CR for 38.306) | Nokia, Nokia Shanghai Bell |
R2-2006409 | Draft CR for IAB capabilities introduction to TS 38.331 | Nokia, Nokia Shanghai Bell |
R2-2006410 | UE radio access capabilities introduction for IAB WI (CR for 38.306) | Nokia, Nokia Shanghai Bell |
R2-2006419 | UE radio access capabilities introduction for IIOT WI (CR for 36.306) | Nokia, Nokia Shanghai Bell |
R2-2006438 | IIOT capabilities introduction to TS 36.331 | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2004319 | Reply LS on Local NR positioning in NG-RAN (S2-2003341; contact: Nokia) | SA2 |
R2-2004332 | LS on support for UL NR E-CID (R3-202646; contact: Nokia) | RAN3 |
R2-2004333 | LS on support for Area Scope in Assistance Information metadata (R3-202749; contact: Ericsson) | RAN3 |
R2-2004376 | LS on NR Positioning gNB measurement report range and granularity (R4-2005841; contact: Intel) | RAN4 |
R2-2004377 | LS on report mapping for UE positioning measurement (R4-2005839; contact: Huawei) | RAN4 |
R2-2004383 | LS on report mapping for UE positioning measurement (R4-2005839; contact: Huawei) | RAN4 |
R2-2004635 | Introduction of UE capability for Positioning | Ericsson |
R2-2004639 | Report Open issues on on-demand SI for positioning | Ericsson |
R2-2004653 | Introduction of on-demand System Information functionality for Positioning | Ericsson |
R2-2005881 | Introduction of on-demand System Information functionality for Positioning | Ericsson |
R2-2005884 | Introduction of UE capability for Positioning | Intel Corporation |
R2-2005885 | Introduction of UE capability for Positioning | Intel Corporation |
R2-2005897 | [AT110-e][605][POS] On-demand posSIBs (Ericsson) | Ericsson |
R2-2005909 | Report of offline discussion [608][POS] Positioning capabilities (Intel) | Intel Corporation |
R2-2006093 | LS on removing SMTC from SSB assistance data (R1-2004951; contact: Huawei) | RAN1 |
R2-2006103 | LS on Capturing UE DL PRS Processing Capability (R1-2005047; contact: Intel) | RAN1 |
R2-2006129 | LS on intra/inter-frequency measurement for NR positioning (R4-2009111; contact: Huawei) | RAN4 |
R2-2006136 | LS on measurement gaps for NR positioning (R4-2009246; contact: Ericsson) | RAN4 |
R2-2006138 | LS on impact of NTA offset on UE Rx-Tx time difference measurement (R4-2009267; contact: Ericsson) | RAN4 |
R2-2006170 | [Draft] LS on capability bits for E-CID measurements | Huawei, HiSilicon |
R2-2006179 | LS on capability bits for E-CID measurements | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004517 | Missing SIB for positioning | Nokia (Rapporteur) |
R2-2004638 | Text Proposal for on demand system information procedure | Ericsson |
R2-2004727 | Introduction of UL NR E-CID | Intel Corporation |
R2-2005094 | Corrections to stage-2 spec | Huawei, HiSilicon |
R2-2005103 | Summary of stage-2 AI 6.8.2.1 | Huawei, HiSilicon |
R2-2005210 | Corrections to NR Positioning | Qualcomm Incorporated |
R2-2005700 | SUL support for Rel-16 positioning purpose | Samsung R&D Institute UK |
R2-2005887 | Missing SIB for positioning | Nokia (Rapporteur) |
R2-2005888 | Corrections to NR Positioning | Qualcomm Incorporated |
R2-2005889 | [AT110-e][610][POS] Stage 2 proposals (Huawei) | Huawei, HiSilicon |
R2-2005910 | Corrections to NR Positioning | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2004637 | Solution for RIL E259 to remove cond on ServingCell ID | Ericsson |
R2-2004707 | Broadcast of additional assistance data | NextNav, AT&T, FirstNet, Intel, Polaris Wireless |
R2-2004708 | Removal of CSI-RS as pathloss reference for positioning SRS [M111] | MediaTek Inc. |
R2-2004796 | Report of [Post109bis-e][950][POS] Remaining issues on broadcast (CATT) | CATT |
R2-2005089 | DraftCR for SSB configuration in RRC spec | Huawei, HiSilicon |
R2-2005090 | DraftCR for introduction of new posSIB | Huawei, HiSilicon |
R2-2005091 | DraftCR for 38.331 on location measurement indication | Huawei, HiSilicon |
R2-2005093 | Discussion on SRS spitial relation configuration | Huawei, HiSilicon |
R2-2005095 | DraftCR for posSI-SchedulingInfo | Huawei, HiSilicon |
R2-2005096 | DraftCR for onDemand Positioning system information | Huawei, HiSilicon |
R2-2005097 | Correction on prohibit timer for SI request for positioning | Huawei, HiSilicon |
R2-2005098 | DraftCR for duplicated description for SI request for positioning | Huawei, HiSilicon |
R2-2005099 | Text proposal for positioning system information | Huawei, HiSilicon |
R2-2005100 | Draft CR the resourceType under SRS-PosResource | Huawei, HiSilicon |
R2-2005106 | Corrections to SSB configuration in RRC | Huawei, HiSilicon |
R2-2005316 | [E271] unicast tag for positioning posSI-BroadcastStatus | Ericsson |
R2-2005394 | [N043] Location Measurement Indication updates for NR inter-frequency RSTD | Nokia, Nokia Shanghai Bell |
R2-2005714 | Summary for RRC Corrections for Positioning | Ericsson |
R2-2005718 | Capturing RRC Positioning Impacts after RAN2-109bis | Ericsson [Rapporteur) |
R2-2005890 | Introduction of RRC Positioning | Ericsson (Rapporteur) |
R2-2005902 | LS on Cell list in NRPPa | Ericsson |
R2-2005903 | [AT110-e][615][POS] Remaining positioning RRC issues (Huawei) | Huawei, HiSilicon |
R2-2006012 | Report of [Post109bis-e][950][POS] Remaining issues on broadcast (CATT) | CATT |
TDoc | Title | Source |
---|---|---|
R2-2004460 | Editorial and other minor updates | Spirent Communications |
R2-2004700 | Report on Structure of UE-based assistance data | Ericsson |
R2-2004701 | Report on TRP-ID structure | Ericsson |
R2-2004702 | Report on Reference for additional path reporting | Ericsson |
R2-2004703 | Summary and Text Proposal Reference for additional path reporting | Ericsson |
R2-2004704 | Summary and Text Proposal on TRP-ID structure | Ericsson |
R2-2004705 | Summary and Text Proposal on Structure of UE-based assistance data | Ericsson |
R2-2004730 | summary of 6.8.2.3\tLPP corrections | Intel Corporation |
R2-2005088 | DraftCR for SSB configuration in LPP spec | Huawei, HiSilicon |
R2-2005101 | Corrections on the positioning measurement report in 37.355 | Huawei, HiSilicon |
R2-2005104 | [Post109bis-e][951][POS] Remaining issues on UE-based positioning (Huawei) | Huawei, HiSilicon |
R2-2005105 | DraftCR on UE-based positioning | Huawei, HiSilicon |
R2-2005107 | Remaining issues in LPP | Huawei, HiSilicon |
R2-2005108 | Remaining issues in LPP ASN.1 | Huawei, HiSilicon |
R2-2005212 | Email discussion report: [Post109bis-e][948][POS] LPP ASN.1 review | Qualcomm Incorporated |
R2-2005213 | LPP Clean-Up | Qualcomm Incorporated |
R2-2005215 | LPP Clean-Up | Qualcomm Incorporated |
R2-2005305 | UL SRS UE Capability | Ericsson |
R2-2005882 | Report of offline discussion [AT110-e][606][POS] Open issues in LPP ASN.1 review | Qualcomm Incorporated |
R2-2005894 | Report on TRP-ID continuation | Ericsson |
R2-2005904 | Report on TRP-ID continuation | Ericsson |
R2-2005906 | LPP Clean-Up | Qualcomm Incorporated |
R2-2005907 | [AT110-e][617][POS] Report on email discussion about structure of UE-based assistance data (Ericsson) | Ericsson |
R2-2005908 | Editorial and other minor updates | Spirent Communications |
R2-2006003 | Email discussion report: [Post109bis-e][948][POS] LPP ASN.1 review | Qualcomm Incorporated |
R2-2006013 | Structure of UE-based beam information assistance data (Extension to email discussion 949) | Ericsson |
R2-2006171 | LPP Clean-Up | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2004461 | Discussion on SRS for positioning during the DRX inactive period | vivo |
R2-2004636 | Discussion and corrections for MAC CE Design for Positioning | Ericsson |
R2-2005046 | Discussion on positioning SRS during DRX inactive period | Spreadtrum Communications |
R2-2005087 | Runnnig CR to MAC spec for R16 Positioning | Huawei, HiSilicon |
R2-2005092 | Remaining issues in MAC spec | Huawei, HiSilicon |
R2-2005211 | Corrections to Power Headroom Reporting for SRS for positioning | Qualcomm Incorporated |
R2-2005905 | [AT110-e] [Offline-618][POS] MAC proposals (Huawei) | Huawei, HiSilicon |
R2-2006172 | Running CR for MAC in R16 positioning | Huawei, HiSilicon |
R2-2006434 | Running CR for MAC in R16 positioning | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004797 | UE capabilities on supporting positioning SRS during DRX inactive period | CATT |
R2-2005304 | DL PRS and UL SRS Coupling for UE Rx Tx measurements for NR positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004355 | LS on Simultaneous reception of DL signals in intra-frequency DAPS HO (R1-2003058; contact: Intel) | RAN1 |
R2-2004518 | Corrections to Mobility Enhancements | Nokia, Intel Corporation (Rapporteurs) |
R2-2004662 | Corrections on NR mobility enhancements (109b-927) | Intel Corporation |
R2-2004670 | Corrections on NR mobility enhancements | Intel Corporation |
R2-2004914 | Correction on CHO failure handling | OPPO |
R2-2005755 | Corrections on NR mobility enhancements | Intel Corporation |
R2-2006173 | Corrections on NR mobility enhancements | Intel Corporation |
R2-2006435 | Corrections on NR mobility enhancements | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2005344 | On stopping evaluating execution condition once triggering the legacy HO | ZTE Corporation, Sanechips |
R2-2005380 | Discussion on leftovers for CHO | Huawei, HiSilicon |
R2-2005456 | Further consideration on CHO in MR-DC operation | CMCC |
R2-2005681 | Stage 2 CR for CHO Evaluating Handling during Legacy HO | LG Electronics Inc. |
R2-2005682 | CHO Evaluating Handling during Legacy HO | LG Electronics Inc. |
R2-2005754 | Summary of discussion [209] on CHO/CPC | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2005071 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2005279 | Corrections on procedure for CPC complete | Futurewei |
R2-2005345 | Remaining issues for CPC | ZTE Corporation, Sanechips |
R2-2005381 | Discussion on leftovers for CPC | Huawei, HiSilicon |
R2-2006379 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
TDoc | Title | Source |
---|---|---|
R2-2004663 | [109b#930] UE capabilities for NR mobility | Intel Corporation |
R2-2004664 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
R2-2004665 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
R2-2004917 | Discussion on UE capability for CHO and CPC | OPPO |
R2-2005061 | Discussion on UE capabilities for NR DAPS | Huawei, HiSilicon |
R2-2005160 | UE capabilities for Mobility Enhancements WI | Nokia, Nokia Shanghai Bell |
R2-2005457 | Discussion on the maxinum CPC candidates | CMCC |
R2-2005684 | Consideration on Conditional mobility capability | LG Electronics Inc. |
R2-2005762 | Introduction of NR mobility UE capabilities | Intel Corporation |
R2-2005763 | Introduction of NR mobility UE capabilities | Intel Corporation |
R2-2005779 | Summary of discussion][214][MOB] UE capability CRs for NR mobility (Intel) | Intel Corporation |
R2-2005784 | UE capabilities for RAN1 feature list | Intel Corporation |
R2-2005785 | UE capabilities for RAN1 feature list | Intel |
R2-2005786 | UE capabilities for RAN1 feature list | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2004427 | Clarification on tag-Config for DAPS (subject to [H223]) | Samsung |
R2-2004619 | Re-establishment initiation and CHO | Ericsson |
R2-2004620 | Remaining issues for conditional PSCell change | Ericsson |
R2-2004649 | Disabling multi-leg RB for DAPS | vivo |
R2-2004661 | Phase 1 class 2 issues on MOB WI (I101, I103, I104, I105, I107, I109, I100, S303, I111) | Intel Corporation |
R2-2004666 | Phase 1 open issue on DAPS CP (S350, I112) | Intel Corporation |
R2-2004667 | Phase 1 open issue on CHO (I113) | Intel Corporation |
R2-2004668 | Phase 1 Open issue on CPC (Z255) | Intel Corporation |
R2-2004672 | Phase 2 MOB RIL issues | Intel Corporation |
R2-2004693 | [E232] Source and target entities at DAPS HO | Ericsson |
R2-2004915 | [O201] Correction on dapsConfig | OPPO |
R2-2005062 | [S350] Discussion on reconfiguration procedure in DAPS | Huawei, HiSilicon |
R2-2005064 | [I112] discussion on RLC re-establishment upon fallback | Huawei, HiSilicon |
R2-2005065 | [I113] Discussion on handling CHO candidate cells upon RRC re-establishment | Huawei, HiSilicon |
R2-2005134 | [B105] TP for DAPS handover with fast MCG link recovery | Lenovo, Motorola Mobility |
R2-2005346 | [Z276] Discussion on UE configuration release in RRC re-establishment | ZTE Corporation, Sanechips |
R2-2005347 | [Z277] Discussion on stopping conditional reconfiguration evaluation during fast MCG recovery | ZTE Corporation, Sanechips |
R2-2005348 | [Z255] Further discussion on the handling of stored CPC configuration | ZTE Corporation, Sanechips |
R2-2005349 | Clarification on not supporting CHO+DAPS | ZTE Corporation, Sanechips |
R2-2005382 | [C003] T312 discussion | Huawei, HiSilicon |
R2-2005383 | [H458] Triggering quantity discussion | Huawei, HiSilicon |
R2-2005430 | [J030, J031] UE DAPS configuration release upon RLF | SHARP |
R2-2005511 | [G103] Clarification on CHO handling during RRC connection re-establishment procedure | Google Inc. |
R2-2005512 | [J033] RoHC handling with and without key change at the UE | SHARP Corporation |
R2-2005529 | [G104] Clarification on DAPS handover failure while the T310 is running | Google Inc. |
R2-2005668 | [S304] Clarification on applicable cell in CHO | Samsung R&D Institute UK |
R2-2005683 | Draft CR for Clarification to release CPC when SCG Release | LG Electronics Inc. |
R2-2005708 | [S350] Discussion on radio bearer handling during DAPS | Samsung Electronics |
R2-2005751 | Summary of discussion [207] on NR mobility ASN.1 review | Intel |
R2-2005997 | TP on DAPS terminology related ASN.1 review issues (ao Z258) | Samsung Telecommunications |
TDoc | Title | Source |
---|---|---|
R2-2005612 | Draft CR on 38.321 for NR mobility enhancement | LG Electronics |
TDoc | Title | Source |
---|---|---|
R2-2004371 | LS on SCell dormancy requirement scope (R4-2005424; contact: Ericsson) | RAN4 |
R2-2005116 | Timer-based transitions for dormancy | Ericsson |
R2-2005118 | Draft reply LS on SCell dormancy requirement scope | Ericsson |
R2-2005266 | CR for 36.331 for CA/DC Enhancements | Ericsson |
R2-2005267 | CR for 38.331 on CA/DC Enhancements | Ericsson |
R2-2005268 | CR for 36.300 for CA/DC Enhancements | Ericsson |
R2-2005269 | CR for 38.300 for CA/DC Enhancements | Ericsson |
R2-2006024 | Capture latest agreements on fast MCG recovery | vivo, Ericsson |
R2-2006130 | Response LS on clarification of UE requirements for early measurement performance and reporting (R4-2009116; contact: Ericsson) | RAN4 |
R2-2006131 | LS to RAN2 on RRM Enhanced Measurement Reporting (R4-2009121; contact: Nokia) | RAN4 |
R2-2006135 | Reply LS to RAN2 on dormant BWP (R4-2009245; contact: Futurewei) | RAN4 |
R2-2006255 | Draft reply LS on SCell dormancy requirement scope | Ericsson |
R2-2006287 | Reply LS on RRM Enhanced Measurement Reporting | RAN2 |
R2-2006318 | Reply LS on SCell dormancy requirement scope | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004499 | Capability issue for MR-DC | vivo |
R2-2005221 | Remaining issues of UE capability of Rel-16 DCCA enhancement | Qualcomm Incorporated |
R2-2005223 | Introduce capabilities on Async NR-DC and cell-grouping configuration | Qualcomm Incorporated |
R2-2005238 | Remain issues on UE capability for Edcca RAN2 features | Huawei, HiSilicon |
R2-2005250 | Remaining issues for UE eDCCA capabilities for RAN2 features | Huawei, HiSilicon |
R2-2005251 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
R2-2005252 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
R2-2005253 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
R2-2005254 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
R2-2005255 | Summary of [Post109bis-e][033][DCCA] UE capabilities CRs (Huawei) | Huawei, HiSilicon |
R2-2005256 | Summary of contributions on UE capabilities | Huawei, HiSilicon |
R2-2006266 | Summary of [AT110-e][074][DCCA] UE capabilities (Huawei) | Huawei, HiSilicon |
R2-2006363 | Introduction of UE capabilities for eDCCA | Huawei |
R2-2006364 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
R2-2006365 | Introduction of UE capabilities for eDCCA | Huawei |
R2-2006366 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004390 | Corrections on dormant BWP operation | OPPO, Nokia, Ericsson, Huawei |
R2-2004582 | Corrections on dormant BWP operation | OPPO, Nokia, Ericsson, Huawei |
R2-2004813 | Correction on CSI-RS measurement in dormant BWP | MediaTek Inc. |
R2-2004837 | MAC and dormant SCell configuration | Nokia, Nokia Shanghai Bell |
R2-2005241 | Remaining issues on SCell dormancy behaviour | Huawei, HiSilicon |
R2-2005280 | Resolve the issue with SRS for dormant SCell | Futurewei |
R2-2005363 | Consideration on dormant BWP | LG Electronics Inc. |
R2-2005623 | Correction on activating SCells into dormant or non-dormant BWP | vivo |
R2-2006078 | Email report of [AT110e][050][DCCA] MAC updates (OPPO) | OPPO |
R2-2006080 | Corrections on dormant BWP operation | OPPO, Nokia, Ericsson, Huawei, MediaTek Inc., Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004389 | Open issues for early measurement | OPPO |
R2-2004492 | RIL#v021 The submission of the embedded RRCReconfigurationComplete | vivo |
R2-2004493 | CR for RIL021 The submission of the embedded RRCReconfigurationComplete | vivo |
R2-2004541 | Remaining issues of NR early measurements | China Unicom |
R2-2004838 | C122, C123, C124 and C150 - TPs for inter-RAT handover via SRB3 upon MCG failure recovery | Nokia, Nokia Shanghai Bell |
R2-2004868 | [E215] Need codes for IEs in ssb-MeasConfig of MeasIdleCarrierNR | CATT |
R2-2004894 | [C141] Correction on the Structure of Configuration of Dormant BWP | CATT |
R2-2004895 | [C140]Correction to separate checking validity area and updating onfiguration | CATT |
R2-2005114 | [H200] Handling of dormancy configuration | Ericsson |
R2-2005171 | [E053] Correction to DL information transfer MR-DC | Ericsson |
R2-2005242 | [38.331][Flagged C121] SCell state configuration for handover case | Huawei, HiSilicon |
R2-2005244 | [38.331][H303][H304][H316][C125] Correction on dormant BWP | Huawei, HiSilicon |
R2-2005247 | [36.331][H301] TP to promote TDM-PatternConfig to a global IE | Huawei, HiSilicon |
R2-2005249 | [38.331][H315] TP to promote MRDC-SecondaryCellGroup to a global IE | Huawei, HiSilicon |
R2-2005272 | [E215][E216][E217][E218][E219] Missing field descriptions and need codes for IEs related to idle/inactive measurement (38.331) | Ericsson |
R2-2005273 | [E924] Clarification regarding the sending of idle/inactive measurements (36.331) | Ericsson |
R2-2005274 | [E923] Clarification regarding carrier prioritization during measurement reporting (36.331) | Ericsson |
R2-2005275 | [E925][E926][E927] Missing field descriptions and need codes for idle/inactive measurement (36.331) | Ericsson |
R2-2005276 | [E930] conditional presence of mobilityControlInfoSCG/scg-ConfigPartSCG for resuming with NE-DC (36.331) | Ericsson |
R2-2005498 | [G100] Clarification on system information handling for early measurement | Google Inc. |
R2-2005537 | Measurement results handling upon reporting | LG Electronics Inc. |
R2-2005604 | [Z312]Correction on upperlayerIndication in RRC resume procecedure | ZTE Corporation, Sanechips |
R2-2005605 | [C121]Correction on direct SCell activation procedure | ZTE Corporation, Sanechips |
R2-2005606 | [Z305]Correction on need condition of first non-dormant BWP | ZTE Corporation, Sanechips |
R2-2005607 | [E215] Need code for IEs within SSB-MeasConfig | ZTE Corporation, Sanechips |
R2-2005638 | Clarification on Inactive AS context update in LTE | LG Electronics Inc. |
R2-2006349 | CR for 36.331 on CA/DC Enhancements | Ericsson (Rapporteur) |
R2-2006350 | CR for 38.331 on CA/DC Enhancements | Ericsson (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004329 | Reply LS on TDD pattern exchange for NR-DC power control (R3-202557; contact: vivo) | RAN3 |
R2-2004775 | SMTC Configuration for PSCell Addition for NR-DC | Apple |
R2-2004776 | Email Report of [Post109bis-e][926][DCCA] UL PC for NR-DC | Apple |
R2-2004777 | Draft LS Reply to RAN1 on UL PC for NR-DC | Apple |
R2-2004835 | NR DC power control | Nokia, Nokia Shanghai Bell |
R2-2005047 | Discussion on DC UL power control | Spreadtrum Communications |
R2-2005240 | TDD pattern exchange for NR-DC power control | Huawei, HiSilicon |
R2-2006028 | LS Reply to RAN1 on UL PC for NR-DC | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004360 | LS response to dormant BWP configuration and related operation (R1-2003075; contact: OPPO) | RAN1 |
R2-2004384 | Open issues for dormant BWP operation | OPPO |
R2-2004385 | Draft Response LS on SCell dormancy requirement scope | OPPO |
R2-2004500 | New PHR trigger for dormancy Scell | vivo |
R2-2004501 | Remaining issue for dormancy Scell configuration | vivo |
R2-2004809 | Finalize dormant BWP | Qualcomm Incorporated |
R2-2004814 | Discussion on timer based transitions for dormant BWP | MediaTek Inc. |
R2-2004815 | Reply LS on SCell dormancy requirement scope | MediaTek Inc. |
R2-2004836 | Resolving RAN1 LS R1-2003075 on dormancy | Nokia, Nokia Shanghai Bell |
R2-2004865 | No SRS transmission for dormancy | Samsung |
R2-2004866 | Support of Implicit Configuration for BFR RS in Dormant BWP | CATT |
R2-2004867 | Discussion on Requirement of Timer-based transition for Dormancy and Non-dormancy | CATT |
R2-2004877 | PHR triggering condition for non-dormant BWP | Samsung |
R2-2004997 | Remaining issue for dormancy Scell configuration | vivo |
R2-2005115 | PHR triggering for dormant BWP | Ericsson |
R2-2005117 | TDD transition to dormant BWP | Ericsson |
R2-2005608 | Remaining issues of dormant BWP | ZTE Corporation, Sanechips |
R2-2005694 | Discussion on the necessity of supporting implicit BFD-RS in dormant BWP | Qualcomm Incorporated, ZTE Corporation, Sanechips |
R2-2005715 | Discussion on the necessity of supporting implicit BFD-RS in dormant BWP | Qualcomm Incorporated, ZTE Corporation, Sanechips |
R2-2006079 | Email report of [AT110e][052][DCCA] Fast Scell Activation (OPPO) | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2004573 | Discussion on NR-U frequency in early measurement | OPPO |
R2-2005239 | Using NR early measurements with network sharing | Huawei, HiSilicon, BT |
R2-2005243 | [38.331][H319] TP to populate all fields of early measurement report | Huawei, HiSilicon |
R2-2005245 | [36.331][H308] TP to populate all fields of early measurement report | Huawei, HiSilicon |
R2-2005246 | [36.331][E927] Need code of ss-RSSI-Measurement-r16 | Huawei, HiSilicon |
R2-2005248 | [38.331][H309] TP for underscribed fields of ssb-Config-r16 | Huawei, HiSilicon |
R2-2005716 | [B001] Adding missing condition for releasing measIdleConfig | Lenovo, Motorola Mobility |
R2-2006267 | Summary of [AT110-e][071][DCCA] New cases (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004502 | Capture latest agreements on fast MCG recovery | vivo |
R2-2004869 | [C122][C123] Correction to Support Inter-RAT Handover for MCG Fast Reovery | CATT |
R2-2004870 | [C150][C151] Correction to Support Inter-RAT Handover for MCG Fast Reovery | CATT |
R2-2005291 | Introducing support for IRAT mobility upon fast MCG recovery (C122, C123) | Samsung Telecommunications |
R2-2005616 | Introduction of transmitting NAS messages on SCG | Google Inc. |
R2-2005629 | Introduction of transmitting NAS messages on SCG | Google Inc. |
R2-2005639 | Remaining issue on inter-RAT HO | LG Electronics Inc. |
R2-2005687 | [38.331][H313][H323][H302] Corrections to MCG fast recovery | Huawei, HiSilicon |
R2-2005688 | [36.331][C150][C151] Corrections to MCG fast recovery | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005169 | Clarification of DAPS configuration in MR-DC | Ericsson |
R2-2005170 | Clarification of DAPS configuration in MR-DC | Ericsson |
R2-2005640 | 37.340 CR for Supporting inter-RAT handover during fast MCG link recovery | LG Electronics Inc. |
R2-2006014 | Support of asynchronous NR-DC | ZTE Corporation (Rapporteur) |
R2-2006169 | Support of asynchronous NR-DC | ZTE Corporation (Rapporteur) |
R2-2006216 | Clarification of DAPS configuration in MR-DC | Ericsson |
R2-2006217 | Clarification of DAPS configuration in MR-DC | Ericsson |
R2-2006218 | Report of [AT110-e][073][DCCA] Stage-2 Updates | Ericsson |
R2-2006338 | DCCA corrections | ZTE Corporation (Rapporteur), Ericsson, LG Electronics Inc., vivo |
R2-2006436 | Clarification of DAPS configuration in MR-DC | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004346 | Reply LS on DCP (R1-2002953; contact: Huawei) | RAN1 |
R2-2004356 | Reply LS on DCP (R1-2003068; contact: CATT) | RAN1 |
R2-2004366 | Reply LS on RRM relaxation in power saving (R4-2005331; contact: Huawei) | RAN4 |
R2-2004551 | SRB3 for reporting UAI for power saving | OPPO, MediaTek Inc. |
R2-2004655 | Report of email discussion [Post109bis-e][941][PowSav] UE capabilities | Intel Corporation |
R2-2004656 | UE capabilities for Rel-16 Power Saving WI | Intel Corporation |
R2-2004657 | UE capabilities for Rel-16 Power Saving WI | Intel Corporation |
R2-2005854 | SRB3 for reporting UAI for power saving | OPPO, MediaTek Inc. |
R2-2005856 | UE capabilities for Rel-16 Power Saving WI | Intel Corporation |
R2-2005857 | UE capabilities for Rel-16 Power Saving WI | Intel Corporation |
R2-2005866 | SRB3 for reporting UAI for power saving | OPPO, MediaTek Inc. |
R2-2005868 | Reply LS on DCP | RAN2 |
R2-2006098 | LS Reply on DCP Open Issues (R1-2004994; contact: CATT) | RAN1 |
R2-2006132 | LS on RRM relaxation in UE power saving (R4-2009132; contact: vivo) | RAN4 |
R2-2006375 | Reply LS on DCP | RAN2 |
R2-2006427 | SRB3 for reporting UAI for power saving | OPPO, MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2004428 | Clarification on DCP configuration | Samsung |
R2-2004642 | Remaining issues for DCP | vivo |
R2-2004967 | Correction on RAR and DCP monitoring | Nokia, Nokia Shanghai Bell |
R2-2005125 | Remaining issues on CSI report when DCP is configured | ZTE, Sanechips |
R2-2005362 | Remaining issues on DCP | LG Electronics Inc. |
R2-2005418 | Prioritization between DCP and RAR addressed to C-RNTI | Samsung |
R2-2005610 | Report of email discussion [Post109bis-e][938][PowSav] MAC open issues | Huawei |
R2-2005611 | MAC CR for Rel-16 UE power saving | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
R2-2005862 | Summary of UP open issues for Rel-16 UE power saving | Huwei |
R2-2005869 | MAC CR for Rel-16 UE power saving | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2004558 | Remaining issues on UE assistance information | OPPO |
R2-2004643 | Remaining issues for implicitly indicating SCG release preference (RIL v110) | vivo |
R2-2004758 | Configurability aspect for Requested values in UE Assistance Information | Apple |
R2-2004860 | UE assistance for connection release | Ericsson, ZTE, Deutsche Telekom, NTT DOCOMO, INC., Vodafone, Verizon, InterDigital |
R2-2004871 | [C301] Considerations on the first reporting of UAI for power saving | CATT |
R2-2004943 | CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2004944 | CR for 36.331 for Power Savings | MediaTek Inc. |
R2-2004945 | Summary of [Post109bis-e][939][PowSav] RRC open issues | MediaTek Inc. |
R2-2005145 | Power Saving UE assistance information | Sony |
R2-2005405 | [H390] Discussion on search space configuration for DCP | Huawei, HiSilicon |
R2-2005863 | [AT110-e][504][PowSav] CP Open and ASN.1 Issues (Mediatek) | MediaTek Inc, |
R2-2006417 | CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2006418 | CR for 36.331 for Power Savings | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2004444 | Report of [Post109bis-e][940][PowSav] RRM open issues | vivo (rapporteur) |
R2-2004445 | CR on 38.304 for UE Power saving in NR | vivo |
R2-2004446 | Draft Reply LS to RAN4 on RRM measurement relaxation in power saving | vivo |
R2-2004540 | Open issues Configurations for RRM Measurement Relaxation | China Unicom |
R2-2004550 | Remaining issues on higher priority frequency measurements | OPPO |
R2-2004562 | RRM Measurement Relaxation Behavior | MediaTek Inc. |
R2-2004594 | Configurations for inter-frequency RRM Measurement Relaxation | NEC Corporation |
R2-2004613 | Remaining issues for RRM measurement relaxation | PANASONIC R&D Center Germany |
R2-2004861 | Relaxed RRM measurements | Ericsson |
R2-2005086 | Discussion on the RAN4 Reply LS on RRM relaxation | Huawei, HiSilicon |
R2-2005139 | Clarification of the low mobility in relaxed measurement | ZTE Corporation, Sanechips |
R2-2005140 | Discussion on higher priority frequency relaxation approach | ZTE Corporation, Sanechips |
R2-2005536 | Remaining issues on relaxed meausrements | LG Electronics Inc. |
R2-2005855 | LS to RAN4 capturing our agreements | vivo |
R2-2005858 | LS to RAN4 capturing our agreements | RAN2 |
R2-2005861 | Summary of RRM measurement relaxation for PowSav | vivo |
R2-2005867 | Summary of RRM relaxation behaviors | CATT |
R2-2005949 | CR for UE Power Saving in NR | vivo |
R2-2006008 | Report of [Post109bis-e][940][PowSav] RRM open issues | vivo (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004303 | Reply LS on QoS monitoring for URLLC (R3-201372; contact: Intel) | RAN3 |
R2-2004304 | LS on removal of Management Based MDT Allowed IE for NR (R3-201437; contact: Qualcomm) | RAN3 |
R2-2004308 | Reply to LS to SA5 on trace related configurations for NR MDT (S5-201424; contact: Ericsson) | SA5 |
R2-2004309 | LS on the status update of the SON support for NR works (S5-201525; contact: Intel) | SA5 |
R2-2004320 | Reply LS on QoS Monitoring for URLLC (S2-2003468; contact: Huawei) | SA2 |
R2-2004327 | Reply LS on the feasibility of Received Interference Power measurement (R1-2002932; contact: Huawei) | RAN1 |
R2-2004331 | Reply LS on the status update of the SON support for NR works (R3-202630; contact: CMCC) | RAN3 |
R2-2004334 | LS on information needed for MRO in UE RLF Report (R3-202818; contact: Samsung) | RAN3 |
R2-2004339 | Propagation of immediate MDT configuration in case of Xn inter-RAT HO (R3-202868; contact: ZTE) | RAN3 |
R2-2004340 | LS on Logged MDT Status (R3-202869; contact: Ericsson) | RAN3 |
R2-2004379 | Reply LS to LS on EN-DC related MDT configuration details (S5-202052; contact: Ericsson) | SA5 |
R2-2004724 | [Post109bis-e][961][MDTSON] SON open issues (Ericsson) | Ericsson |
R2-2004729 | [Draft] Response LS on the status update of the SON support for NR works | Intel Corporation |
R2-2005367 | Corrections on MDT and SON in NR | Huawei, Ericsson, HiSilicon |
R2-2005368 | Corrections on MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2005454 | [Draft] Reply LS on MDT Configuration | CMCC |
R2-2006184 | Corrections on MDT and SON in NR | Huawei, Ericsson, HiSilicon |
R2-2006185 | Corrections on MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2006242 | Reply LS to LS on removal of Management Based MDT Allowed IE for NR (S5-203410; contact: Ericsson) | SA5 |
R2-2006336 | Corrections on MDT and SON in NR | Huawei, Ericsson, HiSilicon |
R2-2006337 | Corrections on MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2006412 | Corrections on MDT and SON in NR | Huawei, Ericsson, HiSilicon |
R2-2006413 | Corrections on MDT and SON | Huawei, Ericsson, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004412 | Discussion on RAN3 related concerns on MDT | ZTE Corporation, Sanechips |
R2-2004413 | Further Considerations and Modifications on MRO in UE RLF Report | CATT, CMCC |
R2-2004503 | TP on Management and signalling based MDT | vivo |
R2-2004716 | On RAN3 related concerns | Ericsson |
R2-2005197 | Signaling based MDT priority in EN-DC | Nokia, Nokia Shanghai Bell |
R2-2005198 | Draft LS on Signalling based MDT priority in DC | Nokia, Nokia Shanghai Bell |
R2-2005225 | Draft LS on Signalling based MDT priority in DC | Nokia, Nokia Shanghai Bell |
R2-2005369 | Discussion on incoming RAN3 LSs | Huawei, HiSilicon |
R2-2005455 | Propagation of MDT configuration in case of Xn inter-RAT HO | CMCC |
R2-2005911 | LS on MDT and SON decisions related to RAN3 LSs | RAN2 |
R2-2006006 | Summary of AI 6.12.2 Essential input from RAN3 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004414 | Miscellaneous Corrections for 37.320 | CATT |
R2-2004673 | Handling of management-based MDT and signalling based MDT | QUALCOMM Europe Inc. - Spain |
R2-2004674 | Remaining issues on L2 measurement | QUALCOMM Europe Inc. - Spain |
R2-2004713 | Corrections to TS 37.320 | Ericsson |
R2-2005370 | Minor issues on TS 37.320 | Huawei, HiSilicon |
R2-2005453 | CR to 37.320 | CMCC, Nokia, Nokia Shanghai Bell |
R2-2005467 | Correction to TS 37.320 on MDT configuration | ZTE Corporation, Sanechips |
R2-2005915 | [AT110-e][886] MDT Stage 2 corrections | CMCC, Nokia |
R2-2006002 | Summary of Corrections for 37.320 | CMCC |
R2-2006342 | CR to 37.320 to support NR MDT | CMCC, Nokia, Nokia Shanghai Bell |
R2-2006439 | CR to 37.320 to support NR MDT | CMCC, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2004409 | [Z162-Z166] Correction to connection establishment failure report | ZTE Corporation, Sanechips |
R2-2004410 | [Z167][Z169] Correction to RLF report | ZTE Corporation, Sanechips |
R2-2004411 | [Z170-171][Z173] Correction to RACH report | ZTE Corporation, Sanechips |
R2-2004416 | [C210] Discussion on Field Description of timeConnFailure in RLF Report | CATT |
R2-2004417 | Corrections on Sensor Measurement | CATT |
R2-2004528 | Corrections to RA/RLF Report_S951_S952 | Samsung Electronics Co., Ltd |
R2-2004717 | [E008] On adding LBTFailure as SCG Failure cause and RLF cause | Ericsson |
R2-2004718 | [E009] On EUTRA previousPCellID in NR RLF report | Ericsson |
R2-2004719 | [E012] On logging TAC in CEF report | Ericsson |
R2-2004720 | [E021] Any cell selection state related logging for OOC event | Ericsson |
R2-2004721 | [E028] On SON-MDT related UE capabilities addition | Ericsson |
R2-2004722 | [E200] On T312 expiry related RLF cause | Ericsson |
R2-2004723 | [E235] UE power savings impact on MDT | Ericsson, CMCC, Samsung |
R2-2004733 | Clarification to RA-report purposes | Ericsson |
R2-2004884 | [S953] Mobility state reporting in RRC connection re-establishment | Samsung Electronics Co., Ltd |
R2-2004886 | [S954] Logged MDT configuration in UE Inactive AS Context | Samsung Electronics Co., Ltd |
R2-2004902 | Text Proposal_for_RIL_S481 | Samsung Electronics Co., Ltd |
R2-2005371 | Summary of [Post109bis-e][960] ASN1 RIL discussion | Huawei |
R2-2005372 | [H363] Discussion on UE logging of a MDT entry | Huawei, HiSilicon |
R2-2005373 | [H365] Discussion on conditions for RLF report | Huawei, HiSilicon |
R2-2005374 | [H366] Discussion on processing delay requirements | Huawei, HiSilicon |
R2-2005375 | [H367] Discussion on failedPcellId-EUTRA | Huawei, HiSilicon |
R2-2005376 | [H368] Discussion on measResult-RLF-Report-EUTRA | Huawei, HiSilicon |
R2-2005377 | [H369][H370] Discussion on corrections of TAC | Huawei, HiSilicon |
R2-2005378 | [H371] Discussion on applying the field interFreqTargetList | Huawei, HiSilicon |
R2-2005416 | Correction on MDT Configuration [S959] | Samsung |
R2-2005468 | TP on cat-a proposal2/3 of SON emailDisc[961] | ZTE Corporation, Sanechips |
R2-2005469 | [Z168][Z172] Alignment of RA informatiom | ZTE Corporation, Sanechips |
R2-2006001 | Summary of ASN1 review | Huawei |
R2-2006015 | Summary of ASN1 review | Huawei |
R2-2006183 | Summary of [888] RRC correction | Huawei, Ericsson |
R2-2006335 | Summary of phase 2 [888] RRC correction | Huawei, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004415 | Consideration on UL Packet Delay | CATT |
R2-2004714 | Corrections to TS 38.314 | Ericsson |
R2-2004789 | Remaining issues for Number of active UEs | NTTDOCOMO, INC. |
R2-2005379 | Minor issues on TS 38.314 | Huawei, HiSilicon |
R2-2005433 | Summary of AI 6.12.5 L2 measurements | CMCC |
R2-2005434 | draft TS 38.314 | CMCC |
R2-2005470 | Remianing issues on L2 measurement | ZTE Corporation, Sanechips |
R2-2005912 | Summary of AI 6.12.5 L2 measurements | CMCC |
R2-2005913 | Proposals to be agreed on L2 measurements | Session chair (CMCC) |
R2-2006195 | draft TS 38.314 | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2004504 | Running CR to 38.306 for NR_SON_MDT | vivo, CMCC |
R2-2004505 | Running CR to 38.306 for NR_SON_MDT | vivo, CMCC |
R2-2005435 | UE feature list introduction for NR SON/MDT WI | CMCC |
R2-2005722 | Running CR to 36.306 for NR_SON_MDT | vivo, CMCC |
R2-2006196 | UE capabilities for NR MDT and SON | CMCC, Huawei, Ericsson, HiSilicon |
R2-2006197 | UE capabilities for NR MDT and SON | vivo, CMCC |
R2-2006198 | UE capabilities for NR MDT and SON | vivo, CMCC |
R2-2006209 | UE feature list introduction for NR SON/MDT WI | CMCC |
R2-2006340 | UE capabilities for NR MDT and SON | CMCC, Huawei, Ericsson, HiSilicon |
R2-2006341 | UE capabilities for NR MDT and SON | vivo, CMCC |
R2-2006372 | Reply LS on the status update of the SON support for NR works | Intel |
TDoc | Title | Source |
---|---|---|
R2-2004344 | LS Response on NR-U PRACH root sequence for 2-step RA (R1-2002853; contact: Ericsson) | RAN1 |
R2-2004879 | 4-step RA type description | Nokia (rapporteur), Nokia Shanghai Bell, ZTE |
R2-2004882 | 4-step RA type figure description | Nokia (rapporteur), Nokia Shanghai Bell, ZTE |
R2-2006034 | Clarification for 4-step RACH CSI-RS capability | ZTE Corporation (rapporteur), LG Electronics Inc |
TDoc | Title | Source |
---|---|---|
R2-2004418 | Remaining Issues on MsgA Transmission | vivo |
R2-2004523 | Issues - 2 step RA | Samsung Electronics Co., Ltd |
R2-2004552 | Remaining issues of 2-step RACH | OPPO |
R2-2004600 | 2-step RA and C-DRX | Nokia, Nokia Shanghai Bell, ZTE (Rapporteur) |
R2-2004614 | Email Discussion Summary: UP and other open issues ([Post109e-bis#xx][ 2s-RA]) | ZTE Corporation (Email Rapporteur) |
R2-2004617 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo, Ericsson, Fujitsu |
R2-2004973 | Remaining issue on 2-step random access | Huawei, HiSilicon |
R2-2005144 | msgB-RNTI ambiguity for CFRA and CBRA of 2-Step RACH | Sony |
R2-2005601 | Remaining issue on user plane aspects | LG Electronics |
R2-2006018 | Email Discussion Summary: UP and other open issues ([Post109e-bis#xx][ 2s-RA]) | ZTE Corporation (Email Rapporteur) |
R2-2006019 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo, Ericsson, Fujitsu |
R2-2006026 | Email Discussion Summary: UP and other open issues ([Post109e-bis#xx][ 2s-RA]) | ZTE Corporation (Email Rapporteur) |
R2-2006027 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo, Ericsson, Fujitsu |
R2-2006323 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo, Ericsson, Fujitsu, LG |
TDoc | Title | Source |
---|---|---|
R2-2004559 | [O911~O916] RRC open issues of 2-step RACH | OPPO |
R2-2004988 | [H631][H632][H635] DraftCR on RACH-ConfigCommonTwoStepRA | Huawei, HiSilicon |
R2-2004989 | [H636][H638] DraftCR on RACH-ConfigGenericTwoStepRA | Huawei, HiSilicon |
R2-2005048 | Discussion on preamble-to-PRU mapping for 2-step CFRA | Spreadtrum Communications |
R2-2005302 | Email_Discussion_Report_Post109bis-e_943_2sRA_RRC_Open_Issues | Ericsson |
R2-2005303 | 38331_Rel16_CRxxx_Corrections for 2-step RA | Ericsson |
R2-2005567 | Removal of total number of preamble for 2-step RACH | ASUSTeK |
R2-2006159 | 38331_Rel16_CRxxx_Corrections for 2-step RA | Ericsson |
R2-2006160 | Email_Discussion_Report[AT110-e][507][2s RA] CP and ASN.1 Issues (Ericsson) | Ericsson |
R2-2006178 | Corrections for 2-step Random Access Type | Ericsson (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2005066 | CR on 38.331 for SRVCC from 5G to 3G | Huawei, HiSilicon, Lenovo, Motorola Mobility, China Unicom |
TDoc | Title | Source |
---|---|---|
R2-2004347 | LS on subcarrier spacing for CLI-RSSI measurement (R1-2002966; contact: LGE) | RAN1 |
R2-2004365 | Reply LS on CLI measurement and reporting (R4-2005297; contact: LGE) | RAN4 |
R2-2004430 | UE capabilities for CLI | Qualcomm Incorporated |
R2-2005277 | CLI Featurre overview - Additional changes | Nokia (Rapporteur) |
R2-2005695 | CR on UE capabilities for CLI | LG Electronics Inc. |
R2-2005707 | CLI Corrections | Nokia (Rapporteur) |
R2-2005730 | UE capabilities for CLI | Ericsson |
R2-2005791 | Offline discussion 101: CLI - RRC and UE capabilities aspects | LG (Rapporteur) |
R2-2005800 | UE capabilities for CLI | Qualcomm Incorporated |
R2-2005801 | CLI Corrections | Nokia (Rapporteur) |
R2-2005805 | Corrections for CLI | LG Electronics Inc. |
R2-2006000 | CR on UE capabilities for CLI | LG Electronics Inc. |
R2-2006423 | CLI Corrections | Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2005309 | On the impact of DRX on CLI SRS-RSRP measurement | Huawei, HiSilicon |
R2-2005603 | Potential correction on SRS resource for Xn exchange | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2004833 | Miscellaneous corrections on eMIMO | Samsung, Nokia, Nokia Shanghai Bell |
R2-2005797 | Miscellaneous corrections on eMIMO | Samsung, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2004465 | [Post109bis-e][933][eMIMO] RRC Open Issues (Ericsson) | Ericsson |
R2-2005792 | Offline discussion 102: eMIMO - RRC open issues - first round | Ericsson |
R2-2005803 | eMIMO corrections | Ericsson |
R2-2005810 | eMIMO corrections | Ericsson |
R2-2005812 | eMIMO corrections | Ericsson |
R2-2005841 | eMIMO corrections | Ericsson |
R2-2006426 | eMIMO corrections | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004463 | On pathloss reference RS MAC CE for SRS and PUSCH | Ericsson |
R2-2004464 | On SRS activation/deactivation MAC CE for the list of serving cells | Ericsson |
R2-2004524 | Issues - Beam Failure Recovery | Samsung Electronics Co., Ltd |
R2-2004646 | Discussion on the priority of the BFR MAC CE and SR | vivo, Samsung |
R2-2004647 | RACH cancellation after the transmission of Msg3 or MsgA | vivo |
R2-2004832 | Remaining issues on the MAC CEs for beam enhancements | Samsung |
R2-2004897 | Open issues for PUSCH Pathloss Reference RS Update MAC CE | OPPO |
R2-2004898 | Open issues on Spcell BFR | OPPO |
R2-2005122 | The Remaining issue on stopping the sr-ProhibitTimer | ZTE, Sanechips |
R2-2005123 | Discussion on Beam Failure Recovery for SCell | ZTE , Sanechips, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, OPPO, Sharp, Lenovo, Apple, Asia Pacific Telecom, Futurewei |
R2-2005185 | Remaining issues on DL MIMO MAC CE | Qualcomm Incorporated |
R2-2005257 | Remaining issues on SCell BFR | Huawei, HiSilicon |
R2-2005366 | Consideration on timer based BFR MAC CE transmission | LG Electronics Inc. |
R2-2005493 | Discussion on timer based BFR MAC CE transmission | Qualcomm Incorporated, vivo, Ericsson, Samsung, MediaTek, CATT |
R2-2005568 | Clarification on generation of BFR MAC CE | ASUSTeK |
R2-2005793 | Offline discussion 103: eMIMO - MAC corrections - first round | Samsung |
R2-2005796 | Offline discussion 103: eMIMO - MAC corrections - second round | Samsung |
R2-2005811 | LS on Detail MIMO MAC CE operations | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004508 | Miscellaneous corrections to NPN | Nokia (Rapporteur) |
R2-2005814 | Miscellaneous corrections to NPN | Nokia (Rapporteur) |
R2-2006424 | Miscellaneous corrections to NPN | Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004484 | Finalization of the support of Non-Public Networks | Nokia (Rapporteur) |
R2-2005739 | Reply LS on CMAS/ETWS and emergency services for SNPNs (S1-202220; contact: Nokia) | SA1 |
R2-2005809 | Finalization of the support of Non-Public Networks | Nokia (Rapporteur) |
R2-2005991 | Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs (S1-202265; contact: CMCC) | SA1 |
R2-2005993 | Reply LS on manual CAG selection (S1-202277; contact: Qualcomm) | SA1 |
R2-2006041 | Reply LS on manual CAG ID selection and granularity of UAC parameters for PNI-NPNs (S2-2004335; contact: vivo) | SA2 |
TDoc | Title | Source |
---|---|---|
R2-2004481 | Report from email discussion [Post109bis-e][934][PRN] Remaining open issues | Nokia (Rapporteur) |
R2-2004482 | Selected NPN issue (ASN.1 Z102) | Nokia, Nokia Shanghai Bell |
R2-2004483 | Discussion on NPN indexing | Nokia, Nokia Shanghai Bell |
R2-2004521 | Consideration on Cells in PCI Range for CAG | CATT |
R2-2004571 | draft CR on introdcution of UE capability for non-public network | ZTE Corporation, Sanechips |
R2-2004572 | Remaining issues for NPN | ZTE Corporation, Sanechips |
R2-2004690 | Remaining aspects of NPN | Ericsson |
R2-2004743 | Discussion on ANR for NPN | vivo |
R2-2005148 | UE behavior for CAG PCI range | Sony |
R2-2005451 | Early Implementation of CAG Features | CMCC, China Telecom, CATT, ZTE, Huawei, Sony |
R2-2005452 | CR for Early Implementation of CAG Features | CMCC, China Telecom, CATT, ZTE, Huawei, Sony |
R2-2005592 | Discussion on network indexing | Huawei, HiSilicon |
R2-2005593 | Discussion on remaining issues on NPN | Huawei, HiSilicon |
R2-2005658 | Need code of hrnn-List in SIB10 | LG Electronics France |
R2-2005659 | Prioritization of CAG for mobility | LG Electronics France |
R2-2005689 | PCI List for CAG | QUALCOMM Europe Inc. - Italy |
R2-2005794 | Offline discussion 104: PRN - RRC open issues - first round | Nokia (Rapporteur) |
R2-2005799 | draft CR on introdcution of UE capability for non-public network | ZTE Corporation, Sanechips |
R2-2005804 | Offline discussion 104: PRN - RRC open issues - second round | Nokia (Rapporteur) |
R2-2005806 | draft CR on introdcution of UE capability for non-public network | ZTE Corporation, Sanechips |
R2-2005807 | UE capability for PRN | Nokia |
R2-2005808 | draft CR on introdcution of UE capability for non-public network | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2004522 | Remaining Issues related to 38.304 | CATT |
R2-2004603 | Remaining open issues in the specification of NPN | Lenovo, Motorola Mobility |
R2-2004689 | Purpose and consequences of manual CAG selection | Ericsson |
R2-2004728 | Remaining issues for Manual CAG selection | Intel Corporation |
R2-2004744 | Discussion on manual CAG selection | vivo |
R2-2005364 | Clarification of cell reselection for NPN-capable U | China Telecom |
R2-2005365 | Further consideration of UAC in PRN | China Telecom |
R2-2005674 | PRN 38304 rapporteur summary of open issues | QUALCOMM Europe Inc. - Italy |
R2-2005676 | PRN 38304 CR (rapporteur update) | QUALCOMM Europe Inc. - Italy |
R2-2005680 | Emergency Calls in CAG Cells for UE supporting NPN-ANR | QUALCOMM Europe Inc. - Italy |
R2-2005795 | Offline discussion 105: PRN - 38304 open issues - first round | Qualcomm (Rapporteur) |
R2-2005798 | Corrrection to 38.304 for PRN | Qualcomm (Rapporteur) |
R2-2005813 | Offline discussion 105: PRN - 38304 open issues - first round | Qualcomm (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2004328 | Reply LS on UE Tx switching period delay and DL interruption (R1-2002960; contact: Apple) | RAN1 |
R2-2004341 | LS on MPE enhancements (R4-2005670; contact: Nokia) | RAN4 |
R2-2004367 | LS on inter-frequency measurement requirement without MG (R4-2005350; contact: Huawei) | RAN4 |
R2-2004368 | LS on the UE capability and network assistance signalling on inter-RAT measurement for Rel-16 NR HST RRM (R4-2005359; contact: CMCC) | RAN4 |
R2-2004372 | LS on supporting Rel-16 NR HST from Rel-15 UEs (R4-2005533; contact: CMCC) | RAN4 |
R2-2004375 | LS on UE capability on DL interruption for UL Tx switching (R4-2005665; contact: Apple) | RAN4 |
R2-2004378 | LS on mandatory of measurement gap patterns (R4-2005846; contact: ZTE) | RAN4 |
R2-2006109 | Report of [AT110e][025][TEI16 Other] In-principle Agreed CRs (Mediatek) | MediaTek |
R2-2006300 | [AT110e][030][Other] FR2 MPE (interdigital) | InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2004318 | Reply LS on support for eCall over NR (S2-2003308; contact: Qualcomm) | SA2 |
R2-2004391 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
R2-2004392 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
R2-2004583 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
R2-2004584 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
R2-2004880 | P bit for Single Entry PHR | Nokia, Nokia Shanghai Bell, Apple, Ericsson, Lenovo, MediaTek Inc., NTT DOCOMO, INC., OPPO |
R2-2004883 | P bit for Single Entry PHR | Nokia, Nokia Shanghai Bell, Apple, Ericsson, Lenovo, MediaTek Inc., NTT DOCOMO, INC., OPPO |
R2-2005388 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
R2-2005389 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
R2-2005390 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
R2-2005391 | Corrections on Emergency Services | Huawei, HiSilicon |
R2-2005399 | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | Huawei, HiSilicon, Telus |
R2-2006272 | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | Huawei, HiSilicon, Telus |
TDoc | Title | Source |
---|---|---|
R2-2004386 | Discussion on UE FR2 P-MPR reporting | OPPO, Huawei |
R2-2004387 | Draft Response LS on UE FR2 P-MPR reporting | OPPO |
R2-2004474 | CR to 38.306 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo |
R2-2004475 | CR to 38.331 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo |
R2-2004476 | CR to 36.306 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo |
R2-2004477 | CR to 36.331 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo |
R2-2004509 | Temporary Boost | Nokia, Nokia Shanghai Bell |
R2-2004510 | LS on Temporary Boost | Nokia |
R2-2004650 | Discussion on the support of P-MPR report | vivo |
R2-2004651 | Draft CR on supporting the P-MPR report | vivo |
R2-2004652 | Draft CR on supporting the P-MPR report | vivo |
R2-2004756 | Remaining issues on UL switching | Apple, China Telecom |
R2-2004778 | P-MPR Reporting | Apple |
R2-2004824 | Introduction of NR inter-frequency measurement without MG | MediaTek Inc. |
R2-2004825 | Introduction of NR inter-frequency measurement without MG | MediaTek Inc. |
R2-2004906 | UE FR2 MPE enhancements and solutions | Nokia, Nokia Shanghai Bell |
R2-2004907 | Introduction of MPE reporting for FR2 | Nokia, Nokia Shanghai Bell |
R2-2004908 | Introduction of MPE reporting for FR2 | Nokia, Nokia Shanghai Bell |
R2-2004909 | Introduction of MPE reporting for FR2 | Nokia, Nokia Shanghai Bell |
R2-2004910 | Introduction of MPE reporting for FR2 | Nokia, Nokia Shanghai Bell |
R2-2004932 | Discussion on MPE enhancements | Ericsson |
R2-2004936 | Implementing MPE enhancements | Ericsson |
R2-2004938 | Implementing MPE enhancements | Ericsson |
R2-2004939 | Implementing MPE enhancements | Ericsson |
R2-2005126 | Considerations on MPE enhancement FR2 | ZTE, Sanechips |
R2-2005138 | L2/3 aspects of MPE mitigation | InterDigital |
R2-2005141 | Addition of MPE reporting | InterDigital |
R2-2005151 | Addition of MPE reporting | InterDigital |
R2-2005219 | Report of [Post109bis-e][045][R16 Other] UL TX Switching-NR_FR1 (China Telecom) | China Telecommunications |
R2-2005220 | 38331CR for UE capability and RRC configuration of supporting UL Tx switching | China Telecommunications |
R2-2005222 | 38306CR for UE capability of supporting UL Tx switching | China Telecommunications |
R2-2005400 | CR on introduction of BCS to asymmetric channel bandwidths (38.331) | Huawei, HiSilicon, Telus |
R2-2005424 | Draft reply LS on inter-frequency measurement without gap | Huawei, HiSilicon |
R2-2005425 | CR to 38.306 on mandatory gap patterns | Huawei, HiSilicon |
R2-2005426 | CR to 38.331 on mandatory gap patterns | Huawei, HiSilicon |
R2-2005427 | CR to 36.306 on mandatory gap patterns | Huawei, HiSilicon |
R2-2005428 | CR to 36.331 on mandatory gap patterns | Huawei, HiSilicon |
R2-2005440 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2005441 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2005442 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2005443 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2005444 | Discussion on signalling for R16 NR HST enhancement | CMCC |
R2-2005445 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2005446 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2005447 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2005449 | Reply LS on supporting Rel-16 NR HST from Rel-15 Ues | CMCC |
R2-2005712 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006016 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2006017 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2006112 | Report of [AT110e][026][Other] UL Tx switching (China Telecom) | China Telecom |
R2-2006113 | 38331CR for UE capability and RRC configuration of supporting UL Tx switching | China Telecommunications |
R2-2006114 | 38306CR for UE capability of supporting UL Tx switching | China Telecommunications |
R2-2006120 | LS on supporting Rel-16 NR HST RRM enhanced requirements from Rel-15 UEs (R4-2006965; contact: CMCC) | RAN4 |
R2-2006121 | LS on inter-frequency measurement requirement without MG (R4-2007745; contact: Huawei) | RAN4 |
R2-2006124 | LS on Frequency separation class for DL-only spectrum for FR2 (R4-2008484; contact: Apple) | RAN4 |
R2-2006125 | Reply LS on asymmetric channel bandwidths (R4-2008893; contact: Huwei) | RAN4 |
R2-2006126 | LS on new UE power class 1.5 (R4-2008906; contact: T-Mobile) | RAN4 |
R2-2006137 | LS on CSI-RS based intra-frequency and inter-frequency measurement definition (R4-2009260; contact: CATT) | RAN4 |
R2-2006139 | Reply LS on CGI reading with autonomous gaps (R4-2009268; contact: ZTE) | RAN4 |
R2-2006140 | LS on mandatory of measurement gap patterns (R4-2009269; contact: ZTE) | RAN4 |
R2-2006174 | LS on Frequency separation class for DL-only spectrum for FR2 (R4-2009294; contact: Apple) | RAN4 |
R2-2006175 | RRC configuration of supporting UL Tx switching | China Telecom, Huawei, ZTE, CATT, Ericsson, OPPO, China Mobile, China Unicom, MTK, Apple |
R2-2006176 | UE capability of supporting UL Tx switching | China Telecom, Huawei, ZTE, CATT, Ericsson, OPPO, China Mobile, China Unicom, MTK, Apple |
R2-2006177 | UE capability of supporting UL Tx switching | China Telecom, Huawei, ZTE, CATT, Ericsson, OPPO, China Mobile, China Unicom, MTK, Apple |
R2-2006187 | Summary of email discussion on R16 NR HST enhancement | CMCC |
R2-2006188 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006189 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006190 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006191 | Introduction of signalling for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006192 | Reply LS on supporting Rel-16 NR HST from Rel-15 Ues | RAN2 |
R2-2006201 | Introduction on frequency separation class for DL-only FR2 spectrum | Apple |
R2-2006202 | Introduction on frequency separation class for DL-only FR2 spectrum | Apple |
R2-2006240 | LS on AT Commands for Bit Rate Recommendation (S4-200880; contact: Qualcomm) | SA4 |
R2-2006261 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2006262 | Introduction of inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2006263 | Introduction of UE capabilities for inter-frequency measurement without gap | CMCC, Huawei, HiSilicon |
R2-2006264 | Reply LS on inter-frequency measurement without gap | RAN2 |
R2-2006273 | CR on introduction of BCS to asymmetric channel bandwidths (38.331) | Huawei, HiSilicon, Telus |
R2-2006274 | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | Huawei, HiSilicon, Telus |
R2-2006275 | CR on introduction of BCS to asymmetric channel bandwidths (38.331) | Huawei, HiSilicon, Telus |
R2-2006289 | CR to 38.306 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo, Huawei, HiSilicon |
R2-2006290 | CR to 38.331 on on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo, Huawei, HiSilicon |
R2-2006291 | CR to 36.306 on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo, Huawei, HiSilicon |
R2-2006292 | CR to 36.331 on introduction of mandatory gap patterns in Rel-16 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc., OPPO, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Vivo, Huawei, HiSilicon |
R2-2006307 | Summary for [028][Other] Inter-Freq measurements without Gaps (phase 1) | Huawei |
R2-2006327 | Introduction of UE capability for high-speed train scenarios | CMCC, Huawei, HiSilicon, CATT, Ericsson |
R2-2006380 | Aperiodic CSI-RS triggering with beam switching timing of 224 and 336 | Ericsson |
R2-2006381 | Implementing confirmation of code block group based transmission | Ericsson |
R2-2006393 | Introduction on frequency separation class for DL-only FR2 spectrum | Apple |
R2-2006394 | Introduction on frequency separation class for DL-only FR2 spectrum | Apple |
R2-2006441 | Implementing confirmation of code block group based transmission | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2006106 | Report on Email [035] on TEI16 new proposals | Chairiman |
TDoc | Title | Source |
---|---|---|
R2-2005417 | Consideration on overheating assistance from the perspective of time-domain allocation | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2004806 | Introduction of NeedForGap capability for NR measurement | MediaTek Inc. |
R2-2004807 | Introduction of NeedForGap capability for NR measurement - 36.331 | MediaTek Inc. |
R2-2004808 | Introduction of NeedForGap capability for NR measurement | MediaTek Inc. |
R2-2004810 | Introduction of NeedForGap capability for NR measurement - 38.306 | MediaTek Inc. |
R2-2004811 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
R2-2005308 | upperLayerIndication enhancements | Huawei, HiSilicon, BT, Samsung |
R2-2005438 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO |
R2-2005439 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO |
R2-2005599 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO, Samsung |
R2-2005600 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO, Samsung |
R2-2005693 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
R2-2006081 | upperLayerIndication enhancements | Huawei, HiSilicon, BT, Samsung |
R2-2006110 | Capability of dynamic NeedForGap reporting | MediaTek Inc. |
R2-2006111 | Introduction of NeedForGap capability for NR measurement - 38.306 | MediaTek Inc. |
R2-2006127 | Reply LS on NeedForGap capability (R4-2008997; contact: MediaTek) | RAN4 |
R2-2006194 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO, Samsung |
R2-2006326 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO, Samsung |
R2-2006353 | Introduction of NeedForGap capability for NR measurement | MediaTek Inc. |
R2-2006354 | Introduction of NeedForGap capability for NR measurement | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2004447 | Remaining issue on EPS voice fallback enhancement | LG Uplus |
R2-2004506 | Further discussion on EN-DC cell reselection issue | vivo |
R2-2004507 | CR for EN-DC cell reselection issue | vivo |
R2-2004757 | Discussion on gapless measurement | Apple |
R2-2004983 | Report of email discussion [Post109bis-e][962][TEI16] Under-reporting CSI-RS Capabilities | NTT DOCOMO, INC. |
R2-2004984 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2004985 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2005159 | Missing reportAddNeighMeas in periodic measurement reporting | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO |
R2-2005401 | Report for [Post109bis-e][050][TEI16] Overheating | Huawei, Huawei Device |
R2-2005402 | 36.331 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2005403 | 38.331 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2005404 | 36.306 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2005436 | Report for [Post109bis-e][051][TEI16] EN-DC cell reselection | CMCC |
R2-2005437 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo |
R2-2005538 | Considerations on alternative priorities for EN-DC cell reselection | LG Electronics Inc. |
R2-2005543 | CR for 36.304 for EN-DC cell reselection | LG Electronics France |
R2-2005549 | CR for 36.331 CR for EN-DC cell reselection | LG Electronics France |
R2-2005594 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, Samsung |
R2-2005595 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, Samsung |
R2-2005598 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, Samsung |
R2-2005815 | Missing reportAddNeighMeas in periodic measurement reporting | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO |
R2-2005816 | Missing reportAddNeighMeas in periodic measurement reporting | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO |
R2-2005820 | 36.306 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2005840 | 36.306 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2006193 | Introduce of alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, Samsung |
R2-2006203 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2006204 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2006276 | 36.331 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
R2-2006277 | 38.331 CR for overheating in (NG)EN-DC and NR-DC | Huawei, Huawei Device |
TDoc | Title | Source |
---|---|---|
R2-2004535 | Mechanisms to enable simultaneous operation of NR Unicast + LTE MBMS | Qualcomm Incorporated, FirstNet, AT&T, Telstra, Academy of Broadcasting Science, Shanghai Jiao Tong University, British Broadcasting Corporation, European Broadcasting Union, Institut für Rundfunktechnik |
R2-2004536 | Introduction of simultaneous operation of NR Unicast + LTE MBMS | Qualcomm Incorporated, FirstNet, AT&T, Telstra, Academy of Broadcasting Science, Shanghai Jiao Tong University, British Broadcasting Corporation, European Broadcasting Union, Institut für Rundfunktechnik |
R2-2004537 | Introduction of simultaneous operation of NR Unicast + LTE MBMS | Qualcomm Incorporated, FirstNet, AT&T, Telstra, Academy of Broadcasting Science, Shanghai Jiao Tong University, British Broadcasting Corporation, European Broadcasting Union, Institut für Rundfunktechnik |
R2-2004538 | Introduction of simultaneous operation of NR Unicast + LTE MBMS | Qualcomm Incorporated, FirstNet, AT&T, Telstra, Academy of Broadcasting Science, Shanghai Jiao Tong University, British Broadcasting Corporation, European Broadcasting Union, Institut für Rundfunktechnik |
R2-2004539 | Introduction of simultaneous operation of NR Unicast + LTE MBMS | Qualcomm Incorporated, FirstNet, AT&T, Telstra, Academy of Broadcasting Science, Shanghai Jiao Tong University, British Broadcasting Corporation, European Broadcasting Union, Institut für Rundfunktechnik |
R2-2004569 | Clarification on providing network specific uac-AccessCategory1-SelectionAssistanceInfo | ZTE Corporation, Sanechips, CMCC |
R2-2004570 | CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo | ZTE Corporation, Sanechips |
R2-2004592 | Maximum Number of DRBs and RLC entities | Nokia, Nokia Shanghai Bell |
R2-2004618 | Updates to reestablishment procedure | ZTE Corporation, Sanechips, Intel Corporation, CATT, Mediatek |
R2-2004715 | Measurement priority handling in NR | Ericsson |
R2-2004834 | Additional UE capability filtering to limit the total number of carriers in NR | Samsung |
R2-2004872 | SRB only connection enhancement for PDU session change | CATT,Huawei, HiSilicon |
R2-2004873 | SRB only connection ehancement option 1 | CATT,Huawei, HiSilicon |
R2-2004949 | On combined RRC procedures | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2004950 | RRC processing delays for combined procedures | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2005121 | CR to 38.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated, Ericsson, MediaTek Inc., ZTE Corporation, Sanechips, Apple, Intel, OPPO |
R2-2005175 | Introduction of SN request of measurement identities in INM | Ericsson, NEC, ZTE Corporation, Sanechips, Vivo, Softbank, Turkcell, Deutsche Telekom, NTT DOCOMO INC., China Unicom, Qualcomm Incorporated, InterDigital |
R2-2005184 | CR to 36.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated, Ericsson, MediaTek Inc., ZTE Corporation, Sanechips, Apple, Intel, OPPO |
R2-2005423 | On the support of NG-based (i.e. via CN) handover using CGI report | Huawei, HiSilicon |
R2-2005697 | Introduction of New Measurement Gap Configuration | vivo |
R2-2005702 | CR to 38.331 on New Measurement Gap Configuration | vivo |
R2-2006117 | Correction on MN-SN measurements coordination in INM | Ericsson, NEC, ZTE Corporation, Sanechips, Vivo, Softbank, Turkcell, Deutsche Telekom, NTT DOCOMO INC., China Unicom, Qualcomm Incorporated, InterDigital |
R2-2006118 | Correction on MN-SN measurements coordination in INM | Ericsson, NEC, ZTE Corporation, Sanechips, Vivo, Softbank, Turkcell, Deutsche Telekom, NTT DOCOMO INC., China Unicom, Qualcomm Incorporated, InterDigital |
R2-2006212 | Correction on MN-SN measurements coordination in INM | Ericsson, NEC, ZTE Corporation, Sanechips, Vivo, Softbank, Turkcell, Deutsche Telekom, NTT DOCOMO INC., China Unicom, Qualcomm Incorporated, InterDigital |
R2-2006213 | Correction on MN-SN measurements coordination in INM | Ericsson, NEC, ZTE Corporation, Sanechips, Vivo, Softbank, Turkcell, Deutsche Telekom, NTT DOCOMO INC., China Unicom, Qualcomm Incorporated, InterDigital |
TDoc | Title | Source |
---|---|---|
R2-2004388 | additional SSB-ToMeasure for smtc2-LP | OPPO, ZTE,CMCC |
R2-2004393 | Discussion on update of NeedForGap | OPPO |
R2-2004438 | Correction on establishment cause value upon enhanced EPS voice fallback | Qualcomm Incorporated |
R2-2004526 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
R2-2004527 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
R2-2004792 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2004793 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2004794 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2005429 | CR to 36.300 on support of inter-RAT HO from SA to EN-DC | Huawei, HiSilicon |
R2-2005614 | CR to 38321 on RACH Prioritization for MPS and MCS | vivo |
R2-2005893 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2005895 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2005896 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS | CATT, CAICT, Huawei, ZTE Corporation |
R2-2006076 | CR to 36.300 on support of inter-RAT HO from SA to EN-DC | Huawei, HiSilicon |
R2-2006077 | Email report of [AT110e][036][TEI16] TEI16 corrections (OPPO) | OPPO |
R2-2006082 | Correction on additional SSB-ToMeasure for smtc2-LP | OPPO |
R2-2006083 | Adding needForGapsInfoNR in HandoverPreparationInformation | OPPO |
R2-2006154 | CR to 38321 on RACH Prioritization for MPS and MCS | vivo |
R2-2006180 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
R2-2006181 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
R2-2006308 | Correction on establishment cause value upon enhanced EPS voice fallback | Qualcomm Incorporated, Ericsson, Softbank |
R2-2006433 | CR to 38321 on RACH Prioritization for MPS and MCS | vivo |
TDoc | Title | Source |
---|---|---|
R2-2004364 | Reply LS on secondary DRX group for FR1+FR2 CA (R4-2005296; contact: Apple) | RAN4 |
TDoc | Title | Source |
---|---|---|
R2-2004325 | LS response on secondary DRX group (R1-2002961; contact: Ericsson) | RAN1 |
R2-2004511 | Offline 053 on LCP Mapping Restrictions | Nokia (Rapporteur) |
R2-2004512 | Dynamic LCP Mapping Restrictions | Nokia, Deutsche Telekom, Ericsson, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
R2-2004513 | Dynamic LCP Mapping Restrictions | Nokia, Nokia Shanghai Bell |
R2-2004514 | Dynamic LCP Mapping Restrictions | Nokia, Deutsche Telekom, Ericsson, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
R2-2004515 | Dynamic LCP Mapping Restrictions | Nokia, Deutsche Telekom, Ericsson, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
R2-2004519 | Dynamic LCP Mapping Restrictions | Nokia, Deutsche Telekom, Ericsson, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
R2-2004553 | Further considerations on secondary DRX group | OPPO |
R2-2004554 | CR to 38.321 on introduction of secondary DRX group | OPPO |
R2-2004555 | CR to 38.331 on introduction of secondary DRX group | OPPO |
R2-2004556 | Cell restriction mask for logical channel | OPPO |
R2-2004557 | Cell restriction mask for logical channel | OPPO |
R2-2004601 | CFRA resource handling for BFR upon TAT expiry | Nokia, Nokia Shanghai Bell, Apple, ASUSTek |
R2-2004640 | Views on TEI for Secondary DRX Group | vivo |
R2-2004786 | Views on introduction of Dual DRX | Xiaomi Communications |
R2-2004855 | Email report of [PostAT109bis-e][054][TEI16] Secondary DRX | Ericsson |
R2-2004856 | Introduction of secondary DRX group | Ericsson |
R2-2004857 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
R2-2004858 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
R2-2004859 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
R2-2005663 | Consideration on LCP mapping restrictions | LG Electronics Inc. |
R2-2005729 | Email report of [PostAT109bis-e][054][TEI16] Secondary DRX | Ericsson |
R2-2006156 | Email report [AT110e][037][TEI16] Secondary DRX (Ericsson) | Ericsson |
R2-2006331 | Email report [AT110e][037][TEI16] Secondary DRX (Ericsson) | Ericsson |
R2-2006332 | Introduction of secondary DRX group | Ericsson |
R2-2006333 | Introduction of secondary DRX group | Ericsson |
R2-2006443 | Introduction of secondary DRX group CR 38.306 | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
R2-2006446 | Introduction of secondary DRX group CR 38.321 | Ericsson |
R2-2006447 | Introduction of secondary DRX group CR 38.331 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004516 | Multiple Scheduling Requests | Nokia, Nokia Shanghai Bell |
R2-2004863 | PDCP security issue about duplicate detection | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, LG Uplus, Deutsche Telekom, NTT DOCOMO, Intel, Huawei, HiSilicon |
R2-2004893 | SR_COUNTER initialization due to RRC reconfiguration | Fujitsu, LG Electronics Inc. |
R2-2005143 | RNTI ambiguity for CFRA and CBRA of 4-Step RACH | Sony |
R2-2005473 | Stopping ra-ResponseWindow for contention-free BFR | Huawei, HiSilicon, China Unicom |
R2-2005510 | ON Duration adaptation | LG Electronics Inc., LG Uplus, Vivo |
R2-2005514 | Adaptation of QoS Flow to DRB Mapping for MDBV Enforcement | Futurewei |
R2-2005662 | Retransmission of an RLC SDU with a poll after discard procedure | LG Electronics Inc., Ericsson, NTT Docomo, LG Uplus, Sharp |
R2-2005706 | Issue on ping pong state transition for sidelink UE | Beijing Xiaomi Software Tech |
TDoc | Title | Source |
---|---|---|
R2-2005209 | Intraband EN_DC power class expansion for 29 dBm | T-Mobile USA Inc. |
R2-2006360 | Intraband EN_DC power class expansion for 29 dBm | T-Mobile USA Inc., Ericsson, Nokia |
TDoc | Title | Source |
---|---|---|
R2-2004726 | Discussion on gapless feature for inter-frequency measurement | Intel Corporation |
R2-2004781 | UE Information for 0-PDCCH | Apple |
TDoc | Title | Source |
---|---|---|
R2-2004530 | Corrections for onDemandSIB-RequestProhibitTimer operation | Samsung Electronics Co., Ltd |
R2-2004604 | Open issues on Prohibit timer | Lenovo, Motorola Mobility |
R2-2004641 | Remaining issues of on-demand SI in RRC_CONNECTED | vivo |
R2-2004706 | On-demand request for SIB9 (for reasons beyond IIoT) [M118] | MediaTek Inc. |
R2-2004795 | [C701]Prohibit Timer for on Demand SIB Request in RRC_CONNECTED | CATT |
R2-2004986 | [H780] Text Proposal on PDCCH monitoring for SI request in RRC_CONNECTED | Huawei, HiSilicon |
R2-2004987 | [H781-783] Correction on OnDemandSIB-Request | Huawei, HiSilicon |
R2-2005102 | Discussion on the remaining issue of on-demand SI in RRC_CONNECTED | Huawei, HiSilicon |
R2-2005172 | Introduction of on-demand SIB(s) procedure in CONNECTED | Ericsson (Rapporteur) |
R2-2005173 | Introduction of on-demand SIB(s) procedure in CONNECTED | Ericsson (Rapporteur) |
R2-2005174 | [E243] ASN.1 remaining issues on on-demand SIBs in CONNECTED | Ericsson |
R2-2005597 | [Z113] [Z117] Text proposal for accepted RIL issues | ZTE Corporation, Sanechips |
R2-2005696 | Condition for T350 stop | LG Electronics Inc. |
R2-2005883 | Report of offline discussion [AT110-e][607][OdSIB] Proposals for on-demand SI in connected | Ericsson |
R2-2005898 | Introduction of on-demand SIB(s) procedure in RRC CONNECTED | Ericsson (Rapporteur) |
R2-2005899 | Introduction of on-demand SIB(s) procedure in CONNECTED | Ericsson |
R2-2005900 | Introduction of capability for on-demand SIB(s) procedure in CONNECTED | Ericsson (Rapporteur) |
R2-2005901 | Introduction of capability for on-demand SIB(s) procedure in CONNECTED | Ericsson (Rapporteur) |
R2-2006043 | Report of [AT110-e][607][OdSIB] Proposals for on-demand SI in connected | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2005476 | Introduction of NR eURLLC capabilities | Huawei, HiSilicon |
R2-2005477 | Introduction of NR eURLLC capabilities | Huawei, HiSilicon |
R2-2006052 | Introduction of NR eURLLC capabilities | Huawei, HiSilicon |
R2-2006053 | Introduction of NR eURLLC capabilities | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005342 | [H603] How to support UL CI for UL Transmission | OPPO |
R2-2005475 | Correction to RRC spec for eURLLC | Huawei, HiSilicon |
R2-2005478 | [H600]-[H603] Capturing the updated L1 parameters from RAN1#100bis-e | Huawei, HiSilicon |
R2-2005479 | [H604] [H605] [H609] Clean-up of the remaining Editor's notes for L1 parameters | Huawei, HiSilicon |
R2-2006054 | Summary of [AT110e][039][eURLLC] RRC (Huawei) | Huawei |
R2-2006055 | Correction to RRC spec for eURLLC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004964 | CG autonomous transmission in inter-UE priortization | Ericsson |
R2-2004965 | draft CR on CG autonomous transmission in inter-UE priortization | Ericsson |
R2-2005474 | Correction to MAC spec for eURLLC | Huawei, HiSilicon |
R2-2006056 | Correction to MAC spec for eURLLC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2004626 | [Q502] [Z302] Merging issues in TS 36.331 subclause 5.3.3.4a | Qualcomm Incorporated |
R2-2005178 | [S003 (LTE), S005 (LTE), B002 (LTE), S046 (LTE), E055 (NR), E057 (NR)] Correction on crossRAT signalling for NR V2X | Ericsson |
R2-2005281 | General ASN.1 issues for 36.331 Rel-16 (S004, S006, B102, Q604, B103, X002) | Samsung Telecommunications |
R2-2005282 | TP for general ASN.1 issues for 36.331 REL-16 (General ASN.1 issues for 36.331 Rel-16 (S004, S006, B102, Q604, B103, X002) | Samsung Telecommunications |
R2-2005284 | ASN.1 Review file (LTE, Word) | Samsung Telecommunications |
R2-2005285 | ASN.1 Review RIL (LTE, Excel) | Samsung Telecommunications |
R2-2005286 | LTE Rel-16 ASN.1 Review, Class 0 and Class 1 issues | Samsung Telecommunications |
R2-2005287 | General changes resulting from ASN.1 review for LTE RRC REL-16 | Samsung Telecommunications |
R2-2005288 | Report of [Post109bis-e][932][LTE/NR/ASN.1] Resolution of review issues S003, S005, B002, S046 (Samsung/Ericsson)) | Samsung Telecommunications |
R2-2005289 | V2X IRAT signalling (resolution of S003, S005, B002, S046) | Samsung Telecommunications |
R2-2005290 | Encoding of 5G indicator (S191) | Samsung Telecommunications |
R2-2005292 | Adding guidelines for SetupRelease paramterised type (S008) | Samsung Telecommunications |
R2-2005752 | Summary of discussion [206] on general LTE ASN.1 review | Samsung |
R2-2005766 | TP for general ASN.1 issues for 36.331 REL-16 (General ASN.1 issues for 36.331 Rel-16 (S004, S006, B102, Q604, B103, X002) | Samsung Telecommunications |
R2-2005767 | V2X IRAT signalling (resolution of S003, S005, B002, S046) | Samsung Telecommunications |
R2-2005768 | General changes resulting from ASN.1 review for LTE RRC REL-16 | Samsung Telecommunications |
R2-2005769 | [S003 (LTE), S005 (LTE), B002 (LTE), S046 (LTE), E055 (NR), E057 (NR)] Correction on crossRAT signalling for NR V2X | Ericsson |
R2-2005770 | ASN.1 Review file (LTE, Word) | Samsung Telecommunications |
R2-2005771 | ASN.1 Review RIL (LTE, Excel) | Samsung Telecommunications |
R2-2005780 | TP for general ASN.1 issues for 36.331 REL-16 (General ASN.1 issues for 36.331 Rel-16 (S004, S006, B102, Q604, B103, X002) | Samsung Telecommunications |
R2-2005782 | LTE Rel-16 ASN.1 Review, Class 0 and Class 1 issues | Samsung Telecommunications |
R2-2005783 | General changes resulting from ASN.1 review for LTE RRC REL-16 | Samsung Telecommunications |
R2-2005845 | General changes resulting from ASN.1 review for LTE RRC REL-16 | Samsung |
R2-2005996 | General ASN.1 issues for 36.331 Rel-16 (S004, S006, B102, Q604, B103, X002) | Samsung Telecommunications |
TDoc | Title | Source |
---|---|---|
R2-2004357 | LS on updated Rel-16 RAN1 UE features lists for LTE (R1-2003070;; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2006089 | LS on categories for terrestrial broadcast (R1-2004912; contact: Qualcomm) | RAN1 |
R2-2006096 | LS on updated Rel-16 RAN1 UE features lists for LTE (R1-2004967; contact: NTT DOCOMO, AT&T) | RAN1 |
R2-2006369 | LS on further updated Rel-16 RAN1 UE features list for LTE (R1-2005118; contact: NTT DOCOMO, AT&T) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2004323 | LS on SA WG2 status of MT-EDT in Rel-16 (S2-2003505; contact: Qualcomm) | SA2 |
R2-2004628 | Corrections to MAC for Rel-16 eMTC | Ericsson |
R2-2004658 | Miscellaneous corrections to Rel-16 eMTC enhancements | Intel Corporation |
R2-2004918 | Corrections to WUS group for eMTC | Nokia |
R2-2005205 | Miscellaneous Rel-16 eMTC corrections | Qualcomm Incorporated |
R2-2005824 | Miscellaneous corrections to Rel-16 eMTC enhancements | Intel Corporation |
R2-2005825 | Corrections to WUS group for eMTC | Nokia |
R2-2005826 | Corrections to MAC for Rel-16 eMTC | Ericsson |
R2-2005827 | Miscellaneous Rel-16 eMTC corrections | Qualcomm Incorporated |
R2-2005880 | Corrections to WUS group for eMTC | Nokia |
R2-2006166 | Reply LS on early UE capability retrieval for eMTC (S2-2004446; contact: Qualcomm) | SA2 |
R2-2006428 | Corrections to WUS group for eMTC | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2004629 | Report on Standalone email discussion | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2005038 | RSS configuration for UEs in RRC_CONNECTED | ZTE Corporation, Sanechips |
R2-2005306 | Text Proposal RSS for RSRP | Ericsson |
R2-2005307 | Text Proposal RSS Configurations for narrowBandIndex and timeoffsetgranularity | Ericsson, Sony |
R2-2005831 | Text Proposal RSS Configurations for narrowBandIndex and timeoffsetgranularity | Ericsson, Sony |
R2-2006162 | Relaxed serving cell measurement for UEs using WUS | Qualcomm Technologies Int |
TDoc | Title | Source |
---|---|---|
R2-2004630 | Enabling R16 AS RAI for 5GC | Ericsson |
R2-2004841 | Early UE capability retrieval enhancements for eMTC/5GC | Qualcomm India Pvt Ltd |
R2-2004862 | Idle Mode cell reselection based on CN type supported | Qualcomm Incorporated, TurkCell, Sony |
R2-2005024 | UP data protection for UP CIoT 5GS Opmitisation | Huawei, HiSilicon |
R2-2005150 | Mobility enhancements for Connectivity to 5GC for MTC and NB-IoT | Sony, Qualcomm |
R2-2005323 | AS RAI and optimization of release | Ericsson, LG Electronics Inc., Sony, Sierra Wireless, Thales, Lenovo, Motorola Mobility, MediaTek Inc., Turkcell |
R2-2005324 | LS on AS RAI and optimization of release | Ericsson |
R2-2005675 | Enabling R16 AS RAI for 5GC | Ericsson |
R2-2005832 | LS on AS RAI and optimization of release | Ericsson |
R2-2005838 | LS on AS RAI and optimization of release | Ericsson |
R2-2005839 | LS on AS RAI and optimization of release | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2005080 | Update to UE capabilities for eMTC | Huawei, HiSilicon |
R2-2005085 | RAN1 feature list and UE capabilities issues for eMTC | Huawei, HiSilicon |
R2-2005828 | Update of UE capabilities for eMTC | Huawei |
R2-2005829 | RAN1 feature list and UE capabilities issues for eMTC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005830 | [AT110-e][410][eMTC] ASN.1 review for eMTC (Phase 2) – Preliminary report | Qualcomm |
R2-2005833 | [AT110-e][410][eMTC] ASN.1 review for eMTC (Phase 2) | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2004322 | Reply LS on MO exception data (S2-2003504; contact: Qualcomm) | SA2 |
R2-2004342 | Reply LS on open PUR issues for NB-IoT/eMTC (R1-2002846; contact: Intel) | RAN1 |
R2-2004345 | LS on PUR working assumption for NB-IoT and eMTC (R1-2002944; contact: Huawei) | RAN1 |
R2-2004466 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Rapporteur (BlackBerry) |
R2-2004631 | Corrections to MAC for Rel-16 NB-IoT | Ericsson |
R2-2004930 | Introduction of Rel-16 NB-IoT enhancements | Nokia |
R2-2005028 | Miscellaneous corrections to TS 36.300 for Rel-16 NB-IoT | Huawei, HiSilicon |
R2-2005029 | Miscellaneous corrections to 36.331 for Rel-16 NB-IoT | Huawei, HiSilicon |
R2-2005921 | Miscellaneous corrections to 36.331 for Rel-16 NB-IoT | Huawei, HiSilicon |
R2-2005922 | Miscellaneous corrections to TS 36.300 for Rel-16 NB-IoT | Huawei, HiSilicon |
R2-2005923 | Introduction of Rel-16 NB-IoT enhancements | Nokia |
R2-2005924 | Corrections to MAC for Rel-16 NB-IoT | Ericsson |
R2-2005948 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Rapporteur (BlackBerry) |
R2-2005950 | Corrections to Rel-16 NB-IoT enhancements | Nokia |
R2-2006059 | LS on RAN1 clarification on MWUS frequency allocation (R1-2004952; contact: Ericsson) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2005129 | Group WUS for mobile UE | Lenovo, Motorola Mobility |
R2-2005146 | On supporting UE group WUS operation with mobility | Sony, Ericsson |
R2-2005204 | Group WUS corrections | Qualcomm Incorporated |
R2-2005278 | GWUS Resource location signalling for eMTC | Nokia Solutions & Networks (I) |
R2-2005624 | TP for 36.331 changes for GWUS Config | Nokia Solutions & Networks (I) |
R2-2006009 | Summary of WUS contributions | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2004632 | [E906, E907] Remaining open issues in PUR | Ericsson |
R2-2004633 | Draft LS reply on PUR open issues and working assumption | Ericsson |
R2-2004817 | Remaining issue on NB-IoT Preconfigured resources | ITL |
R2-2005019 | Discussion on start offset and requested TBS for PUR | Huawei, HiSilicon |
R2-2005020 | RRC-MAC interactions for PUR | Huawei, HiSilicon |
R2-2005021 | Discussion on RAN1 LSs for PUR | Huawei, HiSilicon |
R2-2005022 | [Draft] Reply LS on PUR working assumption for NB-IoT and eMTC | Huawei |
R2-2005023 | [Draft] Reply LS on open PUR issues for NB-IoT and eMTC | Huawei |
R2-2005035 | Remaining FFSs for PUR | ZTE Corporation, Sanechips |
R2-2005206 | [H810] [H840] [H854] PUR start time offset | Qualcomm Incorporated |
R2-2005569 | Remaining issue of D-PUR TA timer in RRC | ASUSTeK |
R2-2005570 | PUR configuration maintenance during RRC state transition | ASUSTeK |
R2-2005571 | HARQ feedback in RRC_IDLE | ASUSTeK |
R2-2005726 | Summary for 7.2.3 Preconfigured uplink resources | Ericsson |
R2-2005936 | [ATT110-e][313] PUR open issues | Ericsson (Summary rapporteur) |
R2-2005937 | Draft LS reply on PUR open issues and working assumption | Ericsson |
R2-2005942 | [ATT110-e][313] PUR open issues – Phase 2 | Ericsson (Summary rapporteur) |
R2-2005945 | [ATT110-e][313] PUR open issues – Phase 3 | Ericsson (Summary rapporteur) |
R2-2005946 | LS reply on PUR transmission for NB-IoT/eMTC | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2005037 | Necessity of time stamp info for ANR in NB-IoT | ZTE Corporation, Sanechips |
R2-2005686 | Report of [Post109bis-e][944][NBIOT] CSS overlapping case for UE specific DRX | Sequans Communications |
R2-2005938 | Report of [AT110-e][315][NBIOT] CSS overlapping case for UE specific DRX (Sequans) | Sequans Communications (email rapporteur) |
R2-2006005 | Report of [Post109bis-e][944][NBIOT] CSS overlapping case for UE specific DRX | Sequans Communications |
TDoc | Title | Source |
---|---|---|
R2-2004467 | Updates for Rel-16 additional enhancements NB-IoT | BlackBerry UK Limited |
R2-2005030 | RAN1 features list and UE capabilities issues | Huawei, HiSilicon |
R2-2005925 | Updates for Rel-16 additional enhancements NB-IoT | BlackBerry UK Limited |
R2-2005926 | Report of [AT110-e][306][NBIOT] R16 RAN1 features list and UE capabilities (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2005031 | [H812][H842] Signalling of newUEidentity for PUR | Huawei, HiSilicon |
R2-2005032 | [H813][H843] Description of groupForServiceList for GWUS | Huawei, HiSilicon |
R2-2005033 | [H816] GWUS frequency location and resource pattern | Huawei, HiSilicon |
R2-2005034 | [H844, H847, H845, H846, H853 ] Miscellaneous RIL WI open issues | Huawei, HiSilicon |
R2-2005927 | Summary of [AT110-e][307][NBIOT] R16 ASN.1 Review (Huawei) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2005214 | Corrections to even further mobility enhancement in E-UTRAN | China Telecommunications |
R2-2005756 | Corrections to even further mobility enhancement in E-UTRAN | China Telecom |
TDoc | Title | Source |
---|---|---|
R2-2004563 | ROHC Handling for DAPS Handover without Key Change | MediaTek Inc. |
R2-2004644 | CR on 36.321 for LTE feMob | vivo |
R2-2004645 | CR on 38.321 for NR mobility enhancement | vivo |
R2-2004648 | Handling of the source SRB at DAPS failure | vivo |
R2-2004697 | RoHC feedback to source cell after UL transmission switch | Ericsson |
R2-2004698 | RoHC handling during DAPS handover without key change | Ericsson |
R2-2004699 | Open issues for control plane aspects of DAPS handover | Ericsson |
R2-2004787 | Handling of expiry of DataInactivityTimer for DAPS | NEC |
R2-2004788 | Solutions for security issue in case of DAPS without key change | NEC |
R2-2004878 | Compromised solutions for ROHC related security issue | Samsung |
R2-2004896 | Discussion on old stored RRC message handling upon DAPS HO failure | OPPO |
R2-2004916 | Discussion on ROHC handling in DAPS HO | OPPO |
R2-2004947 | DAPS handover UP remaining key issues | Qualcomm India Pvt Ltd |
R2-2005056 | Discussion on ROHC handling in DAPS HO without key change | Huawei, HiSilicon |
R2-2005057 | Discussion on transmitting ROHC IR packets in target during DAPS HO | Huawei, HiSilicon, Vivo, Oppo, Apple, China Telecom, Samsung, LG Electronics, CATT, CMCC, Mediatek Inc., LG Uplus |
R2-2005058 | CR on 38.323 for NR mobility enhancement | Huawei, HiSilicon, Mediatek Inc., LG Electronics |
R2-2005059 | CR on 36.323 for LTE feMob | Huawei, HiSilicon, Mediatek Inc., LG Electronics |
R2-2005060 | Discussion on DAPS CP remaining issue | Huawei, HiSilicon |
R2-2005161 | Target cell’s ROHC behaviour for DAPS handover | Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, NEC |
R2-2005448 | Discussion of remaining issues for DAPS HO | CMCC |
R2-2005497 | Handling of RLC for SRBs | LG Electronics Inc. |
R2-2005500 | ROHC handling for DAPS HO without security key change | LG Electronics Inc. |
R2-2005513 | Remaining issues on fallback from DAPS handover failure | SHARP Corporation |
R2-2005753 | Summary of discussion [208] on DAPS UP | Huawei |
R2-2005758 | CR on 38.323 for NR mobility enhancement | Huawei, HiSilicon, Mediatek Inc., LG Electronics, Nokia, Nokia Shanghai-Bell |
R2-2005759 | CR on 36.323 for LTE feMob | Huawei, HiSilicon, Mediatek Inc., LG Electronics, Nokia, Nokia Shanghai Bell |
R2-2005760 | CR on 38.321 for NR mobility enhancement | vivo |
R2-2005761 | CR on 36.321 for even further mobility enhancement in E-UTRAN | vivo |
TDoc | Title | Source |
---|---|---|
R2-2004691 | Open issues on UE capabilities at DAPS HO | Ericsson |
R2-2005063 | Discussion on UE capabilities for LTE DAPS | Huawei, HiSilicon |
R2-2005216 | report of [Post109bis-e][931][LTE MOB] UE capabilities for NR mobility (China Telecom) | China Telecommunications |
R2-2005217 | UE Capability for Rel-16 LTE even further mobility enhancement | China Telecommunications |
R2-2005218 | UE Capability for Rel-16 LTE even further mobility enhancement | China Telecommunications |
R2-2005685 | Consideration on DAPS Capability | LG Electronics Inc. |
R2-2005764 | UE Capability for Rel-16 LTE even further mobility enhancement | China Telecom |
R2-2005765 | UE Capability for Rel-16 LTE even further mobility enhancement | China Telecom |
TDoc | Title | Source |
---|---|---|
R2-2004621 | Updates for R16 LTE Mobility Enhancements and LTE updates for R16 NR Mobility Enhancements | Ericsson |
R2-2004695 | [E928][I114] Condition for setting statusReportRequired for RLC UM | Ericsson, Intel Corporation |
R2-2005350 | [Z263] Discussion on UE configuration release in RRC re-establishment | ZTE Corporation, Sanechips |
R2-2005757 | Updates for R16 LTE Mobility Enhancements and LTE updates for R16 NR Mobility Enhancements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2004692 | Power coordination at DAPS HO in LTE | Ericsson |
R2-2005384 | Discussion on LTE specific CHO issues | Huawei, HiSilicon |
R2-2006377 | LS on power sharing for LTE Mobility Enhancements | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004381 | LS on Reply on QoE Measurement Collection (S5-202304; contact: Ericsson) | SA5 |
R2-2004382 | LS on Reply on QoE Measurement Collection (S5-202305; contact: Ericsson) | SA5 |
R2-2004623 | Handling of incoming LS on QoE Measurement Collection | Ericsson |
R2-2004624 | QoE Measurement Collection additions | Ericsson |
R2-2004625 | Draft LS Reply on QoE Measurement Collection | Ericsson |
R2-2005385 | Discussion on QMC regarding incoming SA5 LS | Huawei, HiSilicon |
R2-2005386 | [Draft] Reply LS to R2-2004381 | Huawei |
R2-2005387 | [Draft] reply LS to R2-2004382 | Huawei |
R2-2005748 | Summary of discussion [204] on Handling of SA5 LS replies on QoE Measurement Collection (Ericsson) | Ericsson |
R2-2005749 | Draft LS Reply on QoE Measurement Collection | Huawei |
R2-2005778 | LS Reply on QoE Measurement Collection | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2004818 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
R2-2004820 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
R2-2004826 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
R2-2004827 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
TDoc | Title | Source |
---|---|---|
R2-2005750 | Summary of discussion [205] on LTE contributions in AIs 7.6, 7.8 and 7.9 | Nokia (RAN2 vice-chair) |
TDoc | Title | Source |
---|---|---|
R2-2004595 | Introduction of NavIC Keplerian set IE | Reliance Jio |
TDoc | Title | Source |
---|---|---|
R2-2005488 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
R2-2005489 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
R2-2005789 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
R2-2005790 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
R2-2004429 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Incorporated |
R2-2005224 | MBMS UE capabilities per band for subcarrier spacing of 2.5 kHz and 0.37 kHz | Qualcomm Technologies Int |
R2-2005227 | MBMS UE capabilities per band for subcarrier spacing of 2.5 kHz and 0.37 kHz | Qualcomm Technologies Int |
R2-2005490 | Correction on MCCH configuration for 0.37kHz SCS | Huawei, Hisilicon |
R2-2006033 | LS on categories for terrestrial broadcast (R1-2004912; contact: Qualcomm) | RAN1 |
R2-2006060 | MBMS UE capabilities per band for subcarrier spacing of 2.5 kHz and 0.37 kHz | Qualcomm Technologies Int |
R2-2006330 | LS on categories for terrestrial broadcast (R1-2004912; contact: Qualcomm) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2005731 | Report from session on LTE legacy, LTE TEI16 and NR/LTE Rel-16 Mobility | Vice Chairman (Nokia) |
TDoc | Title | Source |
---|---|---|
R2-2005732 | Report from Break-Out Session on SRVCC, CLI, PRN, eMIMO, RACS | Vice Chairman (ZTE) |
TDoc | Title | Source |
---|---|---|
R2-2005733 | Report eMTC breakout session | Session chair (Ericsson) |
R2-2005984 | Report eMTC breakout session | Session chair (Ericsson) |
TDoc | Title | Source |
---|---|---|
R2-2005734 | Session minutes for NR-U, Power Savings, NTN and 2-step RACH | Session chair (InterDigital) |
TDoc | Title | Source |
---|---|---|
R2-2005735 | Report from session on positioning and on-demand SI in connected | Session chair (MediaTek) |
TDoc | Title | Source |
---|---|---|
R2-2005736 | Report from SOM/MDT session | Session chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R2-2005737 | Report NB-IoT breakout session | Session chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R2-2005738 | Report from session on LTE V2X and NR V2X | Session chair (Samsung) |
R2-2005983 | Report from session on LTE V2X and NR V2X | Session chair (Samsung) |