TDoc | Title | Source |
---|---|---|
R2-2000008 | Agenda for RAN2#109-e | Chairman |
TDoc | Title | Source |
---|---|---|
R2-2000009 | RAN2#108 Meeting Report | MCC |
TDoc | Title | Source |
---|---|---|
R2-2002046 | RAN2 109-e Methods and Guidence | RAN2 chairman, RAN2 vice chairmen, session chairs |
R2-2002047 | Real Settings Test of GoToWebinar | RAN2 Chairman (Mediatek), RAN2 Secretary (MCC) |
TDoc | Title | Source |
---|---|---|
R2-2000023 | LS on updated Rel-16 LTE and NR parameter lists (R1-1913675; contact: Qualcomm) | RAN1 |
R2-2000041 | LS on Requirements on positioning for UAS (S6-200269; contact: InterDigital) | SA6 |
R2-2000081 | LS on Requirements on positioning for UAS (S6-200269; contact: Interdigital) | SA6 |
R2-2000082 | Reply LS to extend the scope of eV2X (SP-191379; contact: Telecom Italia) | SA |
R2-2000087 | LS on 5GC assisted cell selection for accessing network slice (S2-2001728; contact: ZTE) | SA2 |
R2-2000089 | Response LS on the “LS OUT on Location of UEs and associated key issues” (S3i200056; contact: Rogers) | SA3-LI |
R2-2002095 | Reply LS on UAV positioning (S1-201089; contact: InterDigital) | SA1 |
TDoc | Title | Source |
---|---|---|
R2-2000617 | Clarification on polling bit for RRCConnectionRelease | Huawei, HiSilicon |
R2-2000618 | Clarification on polling bit for RRCConnectionRelease | Huawei, HiSilicon |
R2-2000632 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2000633 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2000634 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2000635 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2000637 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2000638 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2000809 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2000810 | System support for Wake Up Signal | Huawei, HiSilicon |
R2-2001805 | Report of [AT109e][301][ NBIOT R14] Clarification on polling bit for RRCConnectionRelease (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2001806 | Report of [AT109e][302][NBIOT R13] Handling of UE Radio Capability for Paging in NB-IoT and eMTC (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2001807 | Report of [AT109e][303][NBIOT R15] System support for Wake Up Signal (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2001809 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2001810 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2001811 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
R2-2001812 | Handling of UE Radio Capability for Paging in NB-IoT and eMTC | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000339 | Correction for relaxed monitoring for BL and CE UE | Ericsson |
R2-2001062 | Correction to support of UP-EDT, CP-EDT, in eMTC TDD | Huawei, HiSilicon |
R2-2001866 | Correction for relaxed monitoring for BL and CE UE | Ericsson |
R2-2001867 | Correction to support of UP-EDT, CP-EDT, in eMTC TDD | Huawei, HiSilicon |
R2-2001889 | Correction to support of UP-EDT, CP-EDT, in eMTC TDD | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000636 | Clarification on default configuration and SRB1 for UP-EDT and RRC_INACTIVE | Huawei, HiSilicon |
R2-2000663 | Missing QCI to CAPC mapping | Nokia, Nokia Shanghai Bell |
R2-2000680 | Correction on cellReselectionSubPriority | Nokia, Nokia Shanghai Bell |
R2-2000685 | Correction on LTE early measurement | MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson |
R2-2000761 | Corrections to T312 and Discovery Signals measurement | Lenovo, Motorola Mobility |
R2-2001134 | Interpretation of UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
R2-2001135 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
R2-2001136 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
R2-2001137 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
R2-2001138 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
R2-2001139 | Inclusion of Maximum Number of PDCP SDUs per TTI for DL Categories 22-26 | Nokia, Nokia Shanghai Bell |
R2-2001140 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell |
R2-2001141 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell |
R2-2001142 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell |
R2-2001156 | Correction of UE assistance information | Samsung Telecommunications |
R2-2001157 | Correction of UE assistance information | Samsung Telecommunications |
R2-2001158 | Minor corrections collected by Rapporteur | Samsung Telecommunications |
R2-2001347 | The problem of LTE RLC out-of-order delivery configuration | Samsung |
R2-2001351 | CR on RLC OutOfOrderDelivery configuration | Samsung |
R2-2001508 | Correction on the content of RRCConnectionReconfigurationComplete message | Google Inc. |
R2-2001722 | Missing QCI to CAPC mapping | Nokia, Nokia Shanghai Bell |
R2-2001723 | Clarification on default configuration and SRB1 for UP-EDT and RRC_INACTIVE | Huawei, HiSilicon |
R2-2001724 | Correction on LTE early measurement | MediaTek Inc., Nokia, Nokia Shanghai Bell, Ericsson |
R2-2001725 | Corrections to T312 and Discovery Signals measurement | Lenovo, Motorola Mobility |
R2-2001726 | Inclusion of Maximum Number of PDCP SDUs per TTI for DL Categories 22-26 | Nokia, Nokia Shanghai Bel,l Lenovo, Motorola Mobility |
R2-2001729 | Correction of UE assistance information | Samsung Telecommunications |
R2-2001736 | Report of [AT109e][203][LTE15] LTE pre-Rel-15 CRs on CA (Nokia) | Nokia |
R2-2001743 | Report of [AT109e][201][LTE15] Agreeing to simple LTE Rel-15 CRs (RAN2 VC) | RAN2 Vice Chairman |
R2-2001744 | Report of [AT109e][202][LTE15] Discuss remaining LTE Rel-15 CRs (RAN2 VC) | RAN2 Vice Chairman |
R2-2001745 | Report of [AT109e][205][LTE16] Agreeing to simple LTE Rel-16 CRs | RAN2 Vice Chair |
R2-2001762 | Minor corrections collected by Rapporteur | Samsung Telecommunications |
R2-2002056 | Correction to full configuration | Google Inc. |
R2-2002087 | Summary of LTE contributions in AI 4.5 | Summary rapporteur (RAN2 vice-chair) |
R2-2002114 | Minor corrections collected by Rapporteur | Samsung Telecommunications |
TDoc | Title | Source |
---|---|---|
R2-2000036 | Reply LS on Tx DC location (R4-1915361; contact: Huawei) | RAN4 |
TDoc | Title | Source |
---|---|---|
R2-2000566 | Security and RRC Resume Request | Nokia (Rapporteur) |
R2-2000567 | Security and RRC Resume Request | Nokia (Rapporteur) |
R2-2001608 | Unsecured UE capability handling | NTT DOCOMO INC. |
R2-2002215 | Security and RRC Resume Request | Nokia (Rapporteur) |
R2-2002216 | Security and RRC Resume Request | Nokia (Rapporteur) |
R2-2002307 | Security and RRC Resume Request | Nokia (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000159 | TS 36.331 Clarifying the options for PDCP version change | Nokia, Nokia Shanghai Bell |
R2-2000160 | TS 36.306 Clarifying the options for PDCP version change | Nokia, Nokia Shanghai Bell |
R2-2000937 | Allowing PDCP version change without handover | Ericsson |
R2-2000938 | Allowing PDCP version change without handover | Ericsson |
R2-2001175 | Clarification on PDCP version change | Huawei, HiSilicon |
R2-2001176 | Clarification on PDCP version change | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000762 | Corrections to the Location measurement indication procedure | Lenovo, Motorola Mobility |
R2-2001932 | Corrections to the Location measurement indication procedure | Lenovo, Motorola Mobility |
TDoc | Title | Source |
---|---|---|
R2-2000975 | Correction on the RACH parameters for BFR | Huawei, HiSilicon |
R2-2001354 | Clarification on p-CSI reporting multiplexed with SR in DRX | Huawei, HiSilicon |
R2-2001468 | Correction on the RACH parameters for BFR | Huawei, HiSilicon |
R2-2001589 | UL grant overridden between configured grant and RAR grant | ASUSTeK |
R2-2001626 | Clarification on the Operation of DRX Inactivity Timer | Apple |
R2-2002065 | Clarification on the Operation of DRX Inactivity Timer | Apple |
TDoc | Title | Source |
---|---|---|
R2-2001295 | Ordering of PDCP SN and RLC SN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2001294 | PDCP Recovery conditions | Qualcomm Incorporated |
R2-2001296 | Ordering of PDCP SN and RLC SN | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000073 | Reply LS on Handling of UE radio network capabilities in 4G and 5G (S3-194488; contact: Intel) | SA3 |
R2-2000187 | Clarification on RRCReconfiguration and RRCReconfigurationComplete in MR-DC | Apple |
R2-2000233 | Add Description of RACH Resouse Distribution | CATT |
R2-2000341 | Poll request in RRC signalling from NW to UE | Ericsson |
R2-2000342 | Clarification of successful acknowledgement of RRCRelease message | Ericsson |
R2-2000359 | Cell re-selection during RRC connection resume | vivo |
R2-2000616 | Clarification on RRCReconfiguration and RRCReconfigurationComplete in MR-DC | Apple |
R2-2000664 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Ericsson (Rapporteur) |
R2-2000681 | Correction on reporting of uplink TX direct current | MediaTek Inc. |
R2-2000856 | Discussion on recursion in RRC | Nokia, Nokia Shanghai Bell |
R2-2000857 | Clarification on recursion in RRC messages | Nokia, Nokia Shanghai Bell |
R2-2000965 | Discussion on security requirement for UE capability enquiry | Huawei, HiSilicon |
R2-2000973 | Correction on PUSCH-less uplink carrier | Huawei, HiSilicon |
R2-2001096 | Security requirement for UE capability enquiry for LTE | Intel Corporation, NTT DoCoMo, Apple |
R2-2001177 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
R2-2001178 | Correction to RRC reconfiguration complete for NR-DC | Huawei, HiSilicon |
R2-2001179 | Correction to DRB addition/modification for the LTE UE not in EN-DC | Huawei, HiSilicon |
R2-2001180 | Potential issue on the Counter Check in (NG)EN-DC and NR standalone | Huawei, HiSilicon |
R2-2001181 | Draft LS to SA3 on potential issue of Counter Check | Huawei, HiSilicon |
R2-2001183 | Clarification on gap sharing configuration at handover and re-establishment | Huawei, HiSilicon |
R2-2001184 | Clarification on gap sharing configuration at handover and re-establishment | Huawei, HiSilicon |
R2-2001186 | Clarification on SCell release | Huawei, HiSilicon |
R2-2001466 | Correction on PUSCH-less uplink carrier | Huawei, HiSilicon |
R2-2001590 | Correction on NZP-CSI-RS-ResourceSet | ASUSTeK |
R2-2001604 | Unsecured UE capability handling | NTT DOCOMO INC. |
R2-2001614 | Unsecured UE capability handling | NTT DOCOMO INC. |
R2-2001619 | Unsecured UE capability handling | NTT DOCOMO INC. |
R2-2002049 | Unsecured UE capability handling | NTT DOCOMO INC. |
R2-2002094 | Security requirement for UE capability enquiry for LTE | Intel Corporation, NTT DoCoMo, Apple, Ericsson |
R2-2002129 | Correction on NZP-CSI-RS-ResourceSet | ASUSTeK |
R2-2002139 | Report of [AT109e][004][NR15] Potential Easies I | MediaTek |
R2-2002141 | Correction on reporting of uplink TX direct current | MediaTek Inc. |
R2-2002310 | [offline-070]]NR15]Unsecured UE capability handling (NTTDocomo) | NTT DOCOMO |
R2-2002332 | Clarification on gap sharing configuration at handover and re-establishment | Huawei, HiSilicon |
R2-2002333 | Clarification on gap sharing configuration at handover and re-establishment | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000163 | TDOC Capability Coordination for Measurement Reporting Identities in MR-DC | Nokia, Nokia Shanghai Bell |
R2-2000164 | TS 38.331 Dummifying bandwidth class F | Nokia, Nokia Shanghai Bell |
R2-2000245 | Corrections on maxMeasIdentitiesSCG-NR in MR-DC | ZTE Corporation, Sanechips, Ericsson, NEC, CATT |
R2-2000858 | SSB-ToMeasure related clarification | Nokia, Nokia Shanghai Bell |
R2-2000859 | SSB-ToMeasure related clarification | Nokia, Nokia Shanghai Bell |
R2-2002218 | Summary of [AT109e][005][NR15] Coordination on number of measurment ID | ZTE Corporation |
R2-2002344 | Corrections on maxMeasIdentitiesSCG-NR in MR-DC | ZTE Corporation, Sanechips, Ericsson, NEC, CATT |
TDoc | Title | Source |
---|---|---|
R2-2000343 | ETWS and CMAS acquisition during measurement gaps | Ericsson |
R2-2000344 | Clarification for SIB6, SIB7 and SIB6 acquisition during measurement gaps | Ericsson |
R2-2000353 | Clarification on the PLMN-IdentityInfoList | ZTE Corporation, Sanechips |
R2-2002183 | Clarification on the PLMN-IdentityInfoList | ZTE Corporation, Sanechips |
R2-2002305 | Clarification on the PLMN-IdentityInfoList | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2000162 | TS 38.331 Capability Coordination for Measurement Reporting Identities in MR-DC | Nokia, Nokia Shanghai Bell |
R2-2000166 | TDoc IODT issue in 1-symbol PUCCH configuration with frequency hopping | Nokia, Nokia Shanghai Bell |
R2-2000167 | TS 38.331 IODT issue in 1-symbol PUCCH configuration with frequency hopping | Nokia, Nokia Shanghai Bell |
R2-2000879 | Correction on p-maxNR-FR1 for NE-DC | Ericsson |
R2-2000880 | Correction on SFTD frequency list in INM | Ericsson |
R2-2001452 | Discussion on SN trigger MN release measurement gap | Nokia, Nokia Shanghai Bell |
R2-2001456 | Clarification on SN trigger MN release measurement gap | Nokia,Nokia Shanghai Bell |
R2-2001612 | Correction on handover preparation message | LG Electronics Inc. |
R2-2002154 | Correction on p-maxNR-FR1 for NE-DC | Ericsson |
R2-2002155 | Potential easies II | Ericsson |
R2-2002324 | Summary of email discussion [AT109e][068][NR15] IODT issue in 1-symbol PUCCH configuration with frequency hopping | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2000693 | Correction on RLC entity release in case of full config | Huawei, HiSilicon |
R2-2000763 | Introduction of provisions for late non-critical extensions | Lenovo, Motorola Mobility |
R2-2000764 | Introduction of provisions for late non-critical extensions | Lenovo, Motorola Mobility |
R2-2001081 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2001185 | "Need M" field mandatory presence due to a child presence condition | Huawei, HiSilicon |
R2-2001324 | CR on overheating assistance reporting in handover case | Huawei, HiSilicon |
R2-2002149 | CR on overheating assistance reporting in handover case | Huawei, HiSilicon |
R2-2002291 | Miscellaneous non-controversial corrections Set V | Ericsson |
R2-2002377 | Miscellaneous non-controversial corrections Set V | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000682 | Clarification on candidate NR frequencies for IDC in EN-DC | NTT DOCOMO, INC., Ericsson, MediaTek Inc., ZTE Corporation, Qualcomm Incorporated |
R2-2000692 | Correction on FR1-GP flag | Huawei, HiSilicon |
R2-2001455 | Correction on Release of EN-DC | CATT |
R2-2002142 | report of [AT109e][007][NR15] Potential easies III (Huawei, Lenovo, NTT Docomo) | Huawei, HiSilicon |
R2-2002143 | Correction on FR1-GP flag | Huawei, HiSilicon |
R2-2002189 | Clarification on candidate NR frequencies for IDC in EN-DC | NTT DOCOMO, INC., Ericsson, MediaTek Inc., ZTE Corporation, Qualcomm Incorporated, Samsung |
TDoc | Title | Source |
---|---|---|
R2-2000011 | LS on UE data rate (R1-1913552; contact: Ericsson) | RAN1 |
R2-2000013 | LS on XDD-FRX Differentiation (R1-1913579; contact: Qualcomm) | RAN1 |
R2-2000034 | LS on UE capability of intraBandENDC-Support (R4-1913130; contact: Qualcomm) | RAN4 |
R2-2000035 | Reply LS on BCS reporting for EN-DC BC (R4-1915358; contact: Huawei) | RAN4 |
R2-2000161 | TS 38.331 Fixing NE-DC Band Combinations | Nokia, Nokia Shanghai Bell |
R2-2000165 | TS 38.306 Clarifying consequences if not supported | Nokia, Nokia Shanghai Bell |
R2-2000246 | Discussion on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2000247 | CR to 38.306 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2000248 | CR to 38.331 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
R2-2000425 | Correction on removal of NR-DC and NE-DC band combinations when capabilityRequestFilterCommon is absent | MediaTek Inc. |
R2-2000487 | Introduction of extended capabilities for NE-DC only BCs | ZTE Corporation, Sanechips |
R2-2000488 | CR on introduction of extended capabilities for NE-DC only BCs | ZTE Corporation, Sanechips |
R2-2000531 | Corrections on bwp-WithoutRestriction | OPPO |
R2-2000583 | xDD FRx split capabilities. | Qualcomm Incorporated |
R2-2000600 | Handling of fallbacks for combined contiguous and non-contiguous CA in FR2 | Apple, Nokia, Nokia Shanghai Bell, OPPO, Intel |
R2-2000601 | CR to TS38.331 on FR2 intra band contiguous and non-contiguous CA fallback | Apple, Nokia, Nokia Shanghai Bell, OPPO, Intel |
R2-2000602 | CR to TS38.306 on FR2 intra band contiguous and non-contiguous CA fallback | Apple, Nokia, Nokia Shanghai Bell, OPPO, Intel |
R2-2000684 | Correction on SRB capability in NR-DC | MediaTek Inc. |
R2-2001082 | Clarification of handover and measurement capabilities in NR-DC and NE-DC | Ericsson |
R2-2001083 | Clarification of fallback per band feature set | Ericsson |
R2-2001084 | Un-defined band combinations in UECapabilityInformation | Ericsson |
R2-2001182 | Clarification on NE-DC only band combination | Huawei, HiSilicon |
R2-2001187 | Correction on parameter description of beamManagementSSB-CSI-RS | Huawei, HiSilicon |
R2-2001220 | Data rate for the case of single carrier standalone operation | Ericsson |
R2-2001221 | Clarification on maximum number of supported PDSCH Resource Element mapping patterns | Ericsson |
R2-2001222 | Handling of FR2 fallback band combinations | Ericsson |
R2-2001223 | [DRAFT] Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 | Ericsson |
R2-2001224 | Capability coordination for NE-DC | Ericsson |
R2-2001312 | Report for email discussion 108#04 on support of 70MHz CBW | Huawei, HiSilicon |
R2-2001313 | CR to 38.331 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2001314 | CR to 38.306 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2001318 | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.331) | Huawei, HiSilicon |
R2-2001319 | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.306) | Huawei, HiSilicon |
R2-2001320 | Discussion on capabilities with XDD-FRX differentiations | Huawei, HiSilicon |
R2-2001321 | Draft reply LS on capabilities with XDD-FRX differentiations | Huawei, HiSilicon |
R2-2001322 | CR on fallback BC reporting | Huawei, HiSilicon |
R2-2001323 | CR on maximum stored number of deprioritisation frequencies | Huawei, HiSilicon |
R2-2001382 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
R2-2001393 | Miscellaneous Corrections to UE capability parameters | Intel Corporation, Lenovo, Motorola Mobility, NTT DOCOMO, INC., Samsung, Qualcomm Incorporated, Ericsson |
R2-2002036 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
R2-2002059 | Dummifying bandwidth class F for FR1 | Nokia, Nokia Shanghai Bell |
R2-2002061 | TS 38.331 Fixing NE-DC Band Combinations | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2002073 | Miscellaneous Corrections to UE capability parameters | Intel Corporation, Lenovo, Motorola Mobility, NTT DOCOMO, INC., Samsung, Qualcomm Incorporated, Ericsson |
R2-2002080 | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | NTT DOCOMO, INC. |
R2-2002081 | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | NTT DOCOMO, INC. |
R2-2002127 | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.331) | Huawei, HiSilicon |
R2-2002128 | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.306) | Huawei, HiSilicon |
R2-2002134 | [AT109e][008][NR15] Cap Discussion | Ericsson |
R2-2002148 | [AT109e][010][NR15] Potential easies IV (Huawei) | Huawei |
R2-2002150 | CR on fallback BC reporting | Huawei, HiSilicon |
R2-2002151 | CR on the maximum stored number of deprioritisation frequencies | Huawei, HiSilicon |
R2-2002152 | CR to 38.331 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2002153 | CR to 38.306 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2002209 | CR to 38.331 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2002210 | CR to 38.306 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2002220 | CR on introduction of extended capabilities for NE-DC only BCs | ZTE Corporation, Sanechips |
R2-2002221 | LS on the applicability of UE capability for NE-DC | RAN2 |
R2-2002274 | Correction on removal of NR-DC and NE-DC band combinations when capabilityRequestFilterCommon is absent | MediaTek Inc. |
R2-2002275 | Capability coordination for NE-DC | Ericsson |
R2-2002276 | Data rate for the case of single carrier standalone operation | Ericsson |
R2-2002297 | Miscellaneous Corrections to UE capability parameters | Intel Corporation, Lenovo, Motorola Mobility, NTT DOCOMO, INC., Samsung, Qualcomm Incorporated, Ericsson |
R2-2002306 | CR to 38.306 on support of 70MHz channel bandwidth | Huawei, HiSilicon, Vodafone |
R2-2002312 | [DRAFT] Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 | MediaTek Inc |
R2-2002347 | CR on fallback BC reporting | Huawei, HiSilicon |
R2-2002349 | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | NTT DOCOMO, INC., Qualcomm Incorporated |
R2-2002350 | UE capability of intra-band requirements for inter-band EN-DC/NE-DC | NTT DOCOMO, INC., Qualcomm Incorporated |
R2-2002390 | CR on BWCS for inter-ENDC BC with intra-ENDC BC (38.306) | Huawei, HiSilicon |
R2-2002402 | Data rate for the case of single carrier standalone operation | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000340 | Correction for Pcompensation for PC1 in FR2 | Ericsson, NTT DOCOMO INC. |
TDoc | Title | Source |
---|---|---|
R2-2001085 | [108#28][R16 RRC] RRC Merge – 38331 - Email discussion report | Ericsson |
R2-2001086 | Rel-16 RRC 38331 CR Merge | Ericsson |
R2-2001087 | Rel-16 ASN.1 review plan | Ericsson |
R2-2001159 | Draft 36331 Rel-16 resulting from CR merge [108#28][R16 RRC] | Samsung Telecommunications |
R2-2001160 | Notes from 36331 Rel-16 CR merge [108#28][R16 RRC] | Samsung Telecommunications |
R2-2001709 | Rel-16 ASN.1 review plan | Ericsson |
R2-2002290 | [AT109e][065][R16] R16 NR RRC coordination Email discussion report | Ericsson |
R2-2002293 | Rel-16 RRC 38331 CR Merge | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2002064 | Draft LS on Guidelines for UE capability definitions | Ericsson |
R2-2002292 | [DRAFT] LS on Guidelines for UE capability definitions | RAN2 |
R2-2002378 | Guidelines for UE capability definitions | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000533 | LCID extension for Rel-16 | Samsung |
R2-2002208 | Report of LCID extension for Rel-16 | Samsung |
R2-2002266 | Introduction of 5G-SRVCC | R3 (Nokia, Nokia Shanghai Bell) |
R2-2002267 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | R3 (Ericsson, Qualcomm) |
R2-2002268 | Propagation of Roaming and Access Restriction information in E-UTRAN in non-homogenous eNB deployments | R3 (Ericsson, Qualcomm) |
R2-2002269 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | R3 (Ericsson, Qualcomm) |
R2-2002270 | Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments | R3 (Ericsson, Qualcomm) |
R2-2002271 | RAN3 inputs for RAN2 NB-IoT running CR | R3 (Huawei, Ericsson) |
R2-2002272 | RAN3 inputs for RAN2 eMTC running CR | R3 (Huawei, Ericsson) |
R2-2002277 | Report of LCID extension for Rel-16 | Samsung |
R2-2002320 | Introduction of a new MAC subheader for MAC Ces | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2000027 | LS Reply on CP Bearer Mapping for IAB (R3-197659; contact: Ericsson) | RAN3 |
R2-2000045 | LS on definition of IAB-MT channel bandwidth (R4-1916165; contact: Qualcomm) | RAN4 |
R2-2000480 | IAB workplan update | Qualcomm Incorporated |
R2-2000481 | Email discussion [108#51][IAB]: BAP functional view | Qualcomm Incorporated |
R2-2000524 | Correction of TS 38.304 to introduce IAB | Huawei, HiSilicon |
R2-2000525 | Correction of TS 36.304 to introduce IAB | Huawei, HiSilicon |
R2-2000526 | Correction of TS 37.340 on the support of MR-DC for IAB | Huawei, HiSilicon |
R2-2000740 | Summary of email discussion [108#46][IAB] Feature List | Ericsson |
R2-2000741 | Running CR to TS 38.331 on IAB for NR | Ericsson |
R2-2000742 | Running CR to TS 36.331 on IAB for NR | Ericsson |
R2-2000760 | Running CR to 38.321 on Integrated Access and Backhaul for NR | Samsung Electronics GmbH |
R2-2000989 | Summary of email discussion 108#51 on BAP open issue | Huawei |
R2-2000990 | draft TS for TS 38.340 (BAP) | Huawei |
R2-2002113 | draft TS for TS 38.340 (BAP) | Huawei |
R2-2002116 | Running CR to 38.321 on Integrated Access and Backhaul for NR | Samsung Electronics GmbH |
R2-2002117 | Correction of TS 38.304 to introduce IAB | Huawei, HiSilicon |
R2-2002118 | Correction of TS 36.304 to introduce IAB | Huawei, HiSilicon |
R2-2002119 | Correction of TS 37.340 on the support of MR-DC for IAB | Huawei, HiSilicon |
R2-2002122 | Running CR to TS 38.331 on IAB for NR | Ericsson |
R2-2002123 | Running CR to TS 36.331 on IAB for NR | Ericsson |
R2-2002166 | Correction of TS 38.304 to introduce IAB | Huawei, HiSilicon |
R2-2002167 | Correction of TS 36.304 to introduce IAB | Huawei, HiSilicon |
R2-2002168 | Correction of TS 37.340 on the support of MR-DC for IAB | Huawei, HiSilicon |
R2-2002225 | Running CR to 38.321 on Integrated Access and Backhaul for NR | Samsung Electronics GmbH |
R2-2002253 | LS on the inter donor DU re-routing and source IP configuration (R3-201418; contact: Huawei)) | RAN3 |
R2-2002258 | Open issue discussion for TS 38.304 and 36.304 | Huawei |
R2-2002283 | RRC CRs 38331 36331 | Ericsson |
R2-2002321 | Correction of TS 38.304 to introduce IAB | Huawei, HiSilicon |
R2-2002322 | Correction of TS 36.304 to introduce IAB | Huawei, HiSilicon |
R2-2002323 | Correction of TS 37.340 on the support of MR-DC for IAB | Huawei, HiSilicon |
R2-2002328 | Running CR to TS 38.331 on IAB for NR | Ericsson |
R2-2002329 | Running CR to TS 36.331 on IAB for NR | Ericsson |
R2-2002345 | draft TS for TS 38.340 (BAP) | Huawei |
R2-2002354 | Running CR to 38.321 on Integrated Access and Backhaul for NR | Samsung Electronics GmbH |
R2-2002357 | 38.331 CR on Integrated Access and Backhaul for NR | Ericsson |
R2-2002358 | 36.331 CR on Integrated Access and Backhaul | Ericsson |
R2-2002365 | CR to 38.300 on Integrated Access and Backhaul for NR | Qualcomm |
R2-2002403 | Correction of TS 38.304 to introduce IAB | Huawei, HiSilicon |
R2-2002404 | Correction of TS 36.304 to introduce IAB | Huawei, HiSilicon |
R2-2002405 | Introduction of Integrated Access and Backhaul for NR | Samsung Electronics GmbH |
R2-2002406 | 38.331 CR on Integrated Access and Backhaul for NR | Ericsson |
R2-2002407 | CR to 38.300 on Integrated Access and Backhaul for NR | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2000469 | Parent selection at IAB nodes during Initial Setup | Intel |
R2-2000743 | On Multi-connectivity for IAB | Ericsson |
R2-2000744 | Security for inter-IAB node Signalling | Ericsson |
R2-2001624 | NR-DC support in IAB (signaling perspective) | Samsung R&D Institute UK |
R2-2001634 | EN-DC support in IAB | Samsung R&D Institute UK |
TDoc | Title | Source |
---|---|---|
R2-2000270 | Design of DL HbH Flow Control Message | vivo |
R2-2000271 | Discussion on BAP control PDU | vivo |
R2-2000470 | Multi-route support in IAB | Intel |
R2-2000502 | Further consideration on routing configuration | ZTE, Sanechips |
R2-2000503 | Further consideration on bearer mapping | ZTE, Sanechips |
R2-2000504 | Consideration on flow control control PDU | ZTE, Sanechips |
R2-2000518 | Remaining issues for routing | Huawei, HiSilicon |
R2-2000519 | Remaining issues for bearer mapping | Huawei, HiSilicon |
R2-2000561 | Flow control open issues in IAB | NEC Corporation |
R2-2000661 | Considerations on BAP entity release | KDDI Corporation |
R2-2000745 | Further Discussion on BAP Layer Signaling | Ericsson |
R2-2000746 | Remaining Issues Related to HbH Flow Control | Ericsson |
R2-2000770 | Desired data rate for hop-by-hop flow control | Samsung |
R2-2000819 | On BAP features and their mandatory vs optional support | Samsung Electronics GmbH |
R2-2000847 | Flow-control details | Nokia, Nokia Shanghai Bell |
R2-2000893 | Remaining open Issues of IAB Flow Control | CATT |
R2-2000902 | Inter-node BH RLF indication | CMCC |
R2-2000903 | BAP mapping support for routing | CMCC |
R2-2001060 | Remaining issues of BAP | Nokia, Nokia Shanghai Bell |
R2-2001562 | Need of BAP buffer | LG Electronics Inc. |
R2-2001563 | Consideration on local routing in IAB | LG Electronics Inc. |
R2-2001564 | Details of polling for hop-by-hop flow control | LG Electronics Inc. |
R2-2001565 | Configuration of BH RLC channel for control PDU transmission | LG Electronics Inc. |
R2-2001622 | Remaining issues for IAB HbH Flow control | Futurewei Technologies |
R2-2001635 | BAP layer indication of RLF at child node | Samsung R&D Institute UK |
R2-2002055 | Summary on BAP functionality in AI 6.1.3 | Huawei, HiSilicon |
R2-2002157 | Proposals for approval on BAP functionality (Set I) | Huawei |
R2-2002259 | Proposals for approval on BAP functionality (Set II) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000272 | Preemptive BSR Procedures and Format | vivo |
R2-2000471 | Uplink latency reduction | Intel |
R2-2000483 | (TP for NR_IAB BL CR to TS 38.321) MAC CE for guard symbols | Qualcomm Incorporated, Samsung |
R2-2000505 | Discussion on the pre-emptive BSR format | ZTE, Sanechips |
R2-2000506 | Discussion on remaining issues on Timing Delta MAC CE | ZTE, Sanechips |
R2-2000507 | TP for Timing Delta MAC CE | ZTE, Sanechips |
R2-2000508 | Draft LS on Timing Delta signaling | ZTE, Sanechips |
R2-2000514 | Remaining issue of pre-emptive BSR in IAB | Kyocera |
R2-2000520 | Remaining issues of the pre-emptive BSR | Huawei, HiSilicon |
R2-2000521 | Leftover issues to support the IAB RACH procedure | Huawei, HiSilicon |
R2-2000527 | Remaining issue for the Timing Delta MAC CE | Huawei, HiSilicon |
R2-2000528 | TP for Guard Symbols MAC CEs | Huawei, HiSilicon |
R2-2000747 | Remaining Aspects of Pre-emptive BSR Format | Ericsson |
R2-2000748 | L1 Resource Multiplexing MAC CE | Ericsson |
R2-2000781 | Finalising Rel-16 pre-emptive BSR design | Samsung Electronics GmbH |
R2-2000782 | TP on outstanding issues with pre-emptive BSR | Samsung Electronics GmbH |
R2-2000808 | Open issues with IAB LCID space extension and its wider impact on Rel-16 | Samsung Electronics GmbH |
R2-2000848 | Remaining issues of buffer status reporting for IAB | Nokia, Nokia Shanghai Bell |
R2-2000849 | Format for pre-emptive BSR | Nokia, Nokia Shanghai Bell |
R2-2000850 | MAC CE for guard symbols indication | Nokia, Nokia Shanghai Bell |
R2-2000894 | Remaining Issues on Pre-emptive BSR | CATT |
R2-2001018 | Consideration on uplink low-latency scheduling | Lenovo, Motorola Mobility |
R2-2001019 | Pre-emptive BSR in DC scenario | Lenovo, Motorola Mobility |
R2-2001020 | BSR and pre-BSR in packet re-routing scenario | Lenovo, Motorola Mobility |
R2-2001342 | Data volume reporting and dual connectivity with Pre-emptive BSR | Futurewei Technologies |
R2-2001556 | Consideration on truncated pre-BSR MAC CE | LG Electronics Inc. |
R2-2001558 | Remaining issues on Timing Delta MAC CE | LG Electronics Inc. |
R2-2001559 | [DRAFT] LS on Timing Delta MAC CE | LG Electronics Inc. |
R2-2001560 | LCG based UL grant | LG Electronics Inc. |
R2-2001561 | Ambiguity of pre-BSR with multiple parents | LG Electronics Inc. |
R2-2001591 | Discussion on including pre-emptive BSR in MAC PDU | ASUSTeK |
R2-2001592 | Discussion on cancelling pre-emptive BSR | ASUSTeK |
R2-2001631 | F1-U Flow Control and Reordering Issues | Sequans Communications |
R2-2001632 | Packet Marking for E2E Flow Control | Sequans Communications |
R2-2001645 | TP for Guard Symbol MAC CE | ZTE Corporation, Sanechips |
R2-2002044 | Summary of IAB MAC impacts | Samsung (rapporteur) |
R2-2002092 | Summary of IAB MAC impacts | Samsung (rapporteur) |
R2-2002120 | Summary of IAB MAC impacts | Samsung (rapporteur) |
R2-2002162 | IAB MAC impacts: Proposals for discussion and approval (Set I) | Samsung |
R2-2002163 | IAB MAC impacts: Proposals for discussion and approval (Set II) | Samsung |
R2-2002217 | IAB MAC impacts: Proposals for discussion and approval (Set III) | Samsung |
R2-2002254 | LS to RAN1 on T-delta in IAB | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000273 | Discussion on IAB BH RLF report mechanism in case of DC | vivo |
R2-2000274 | Verification of BH RLF notification | vivo |
R2-2000275 | [Draft] LS on BH RLF notification verification | vivo |
R2-2000276 | RLF Notification Messages | vivo |
R2-2000472 | Further discussion on Backhaul RLF handling | Intel |
R2-2000509 | Discussion on IAB BH RLF handling | ZTE, Sanechips |
R2-2000510 | Discussion on BAP control PDU of RLF indication | ZTE, Sanechips |
R2-2000516 | Possible issues on Backhaul RLF handling | Kyocera |
R2-2000662 | Considerations on Intra-CU indication | KDDI Corporation |
R2-2000749 | Further details on Backhaul link RLF Notification Types to Downstream Node(s) | Ericsson |
R2-2001348 | Cell Selection for Backhaul RLF Recovery | Futurewei Technologies |
R2-2001633 | Remaining issues on IAB RLF | Samsung R&D Institute UK |
TDoc | Title | Source |
---|---|---|
R2-2000277 | Cell baring indication for IAB support | vivo |
R2-2000479 | Parent selection at IAB nodes during Initial Setup (Text proposal) | Intel Corporation |
R2-2000482 | (TP for NR_IAB BL CR to TS 38.331) IP address configuration | Qualcomm Incorporated |
R2-2000511 | Discussion on the RRC signalling for IP address allocation | ZTE, Sanechips |
R2-2000529 | The impacts of IP address management of IAB node to RAN2 | Huawei, HiSilicon |
R2-2000750 | IP Address Assignment for IAB Node(s) | Ericsson |
R2-2000769 | IP address configuration for IAB | Samsung |
R2-2000895 | Views on RRC States of IAB nodes | CATT |
R2-2001016 | Remaining details for IAB-MT access | Samsung Electronics GmbH |
R2-2001059 | IP address assignment for IAB nodes | Nokia, Nokia Shanghai Bell |
R2-2001061 | IAB-MT features list and capabilities | Nokia, Nokia Shanghai Bell |
R2-2002045 | Summary on IAB IP address configuration | Samsung (rapporteur) |
R2-2002057 | Summary of 6.1.5.2: IAB-MT Features List | Ericsson |
R2-2002164 | IAB IP address allocation - Proposals for discussion and approval | Samsung |
R2-2002284 | Summary of 6.1.5.2: IAB Configuration except IP address | Ericsson (rapporteur) |
R2-2002375 | Summary of 6.1.5.2: IAB Configuration except IP address | Ericsson (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000484 | IAB access barring | Qualcomm Incorporated |
R2-2000512 | Consideration on IAB node access control | ZTE, Sanechips |
R2-2000522 | Backhaul RLF Recovery | Huawei, HiSilicon |
R2-2000523 | Leftover issue for cell barring | Huawei, HiSilicon |
R2-2000751 | On cell Reservations in MIB and SIB1 | Ericsson |
R2-2000752 | Draft CR to 36.304 on cell Reservations for IAB-MTs | Ericsson |
R2-2000753 | Draft CR to 38.304 on cell Reservations for IAB-MTs | Ericsson |
R2-2000754 | IAB-MT Feature Capabilities | Ericsson |
R2-2000824 | PWS information handling in IAB | Sony |
R2-2000835 | IAB Cell Barring | Sony |
R2-2000892 | Views on Cell Barring Mechanism for IAB | CATT |
R2-2001021 | Cell selection for IAB RLF recovery | Lenovo, Motorola Mobility |
R2-2001056 | BH link failure handling | Nokia, Nokia Shanghai Bell |
R2-2001057 | Remaining aspects of F1AP transport in EN-DC | Nokia, Nokia Shanghai Bell |
R2-2001058 | Remaining aspects of IAB initial access | Nokia, Nokia Shanghai Bell |
R2-2001523 | Access control in IAB networks | LG Electronics France |
R2-2001524 | Necessity of even earlier BH RLF notification | LG Electronics France |
R2-2001525 | BH RLF Notification Termination Layer | LG Electronics France |
R2-2001605 | Differential barring for IAB nodes and UEs | Futurewei Technologies |
R2-2001625 | F1AP related terminology in NSA IAB | Samsung R&D Institute UK |
R2-2002058 | Summary of 6.1.5.3: SI Broadcast, cell Restrictions/Reservation and Barring, Initial Access, and Connection Setup | Ericsson |
R2-2002285 | Email discussion to progress on: SI Broadcast, cell Restrictions/Reservation and Barring, Initial Access, and Connection Setup | Ericsson (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000016 | Response LS to RAN2 LS on SFN LSB indication in msg2/msgB (R1-1913582; contact: Qualcomm) | RAN1 |
R2-2000018 | Reply LS on PHR reporting for NR-U (R1-1913584; contact: Lenovo) | RAN1 |
R2-2000021 | LS on signaling of Q for a serving cell in NR-U (R1-1913592; contact: Nokia) | RAN1 |
R2-2000414 | Running CR to 37.340 for NR-U | OPPO |
R2-2001254 | Running RRC CR for NR Shared Spectrum | Qualcomm Incorporated |
R2-2001267 | Running Stage-2 CR for NR Shared Spectrum | Qualcomm Incorporated |
R2-2001341 | Running MAC CR for NR-U | Ericsson |
R2-2001343 | Summary of open issues for NR-U Running 38.321 | Ericsson |
R2-2001435 | Running Idle/Inactive CR for NR Shared Spectrum | Qualcomm Incorporated |
R2-2001437 | Control Plane Open Issues for NR Shared Spectrum | Qualcomm Incorporated |
R2-2001918 | Summary of open issues for NR-U Running 38.321 | Ericsson |
R2-2001919 | LS response to RAN1 on MIB signalling of Q | Qualcomm |
R2-2001920 | Introduction of NR operation with Shared Spectrum Access in RRC | Qualcomm Incorporated |
R2-2001921 | Running Stage-2 CR for NR-U | OPPO |
R2-2001922 | Introduction of NR operation with Shared Spectrum Access to Stage-2 | Qualcomm Incorporated |
R2-2001923 | Introduction of NR operation with Shared Spectrum Access in idle mode | Qualcomm Incorporated |
R2-2001924 | Introduction of NR-U in 38.321 | Ericsson |
R2-2001981 | Introduction of NR operation with Shared Spectrum Access in RRC | Qualcomm Incorporated |
R2-2001982 | Introduction of NR-U to 37.340 | OPPO |
R2-2001983 | Introduction of NR operation with Shared Spectrum Access to Stage-2 | Qualcomm Incorporated |
R2-2002301 | Reply LS on signaling of Q for a serving cell in NR-U | RAN2 |
R2-2002361 | LS to RAN2 on NR-U related changes for 38.300 running CR (R1-2001300; contact: Qualcomm) | RAN1 |
R2-2002362 | LS on SSB index and candidate SSB index for NR-U (R1-2001357; contact: Samsung) | RAN1 |
R2-2002363 | LS on NR-U enhancements to initial access procedures (R1-2001375; contact: Charter Communications) | RAN1 |
R2-2002364 | Reply LS on consistent Uplink LBT failure detection mechanism (R1-2001397; contact: Nokia) | RAN1 |
R2-2002385 | Introduction of NR operation with Shared Spectrum Access in Idle/Inactive mode | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2001911 | NR-U UP Summary for RACH and UL LBT | InterDigital |
R2-2002029 | Summary of open issues from NR-U AI6.2.2.3 and AI6.2.2.4 | OPPO |
R2-2002196 | LS on random access procedure in NR-U | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000145 | Further Consideration on RACH Procedure in NR-U | vivo |
R2-2000146 | Issue on the Autonomous BWP Awitching in NR-U | vivo |
R2-2000147 | LBT Impacts on 2-step RACH | vivo |
R2-2000416 | 2-step RACH for NR-U | OPPO |
R2-2000771 | RA procedure considering SSBs with QCL relationship | Fujitsu |
R2-2000851 | MSGA PUSCH LBT failure and PDCCH decoding | Nokia, Nokia Shanghai Bell |
R2-2000958 | Remaining issue on 2-step random access in NRU | Huawei, HiSilicon |
R2-2001208 | Remaining issues on RACH | Ericsson |
R2-2001209 | Gapless msgA transmissions in NR-U | Ericsson |
R2-2001449 | Additional opportunity for Msg1 in 4-step RACH | LG Electronics Polska |
R2-2001606 | Consideration for C-RNTI monitoring in NR-U | LG Electronics Polska |
TDoc | Title | Source |
---|---|---|
R2-2000148 | Remaining Issues of UL LBT Failure | vivo |
R2-2000415 | Remaining issues on consistent uplink LBT failure for NR-U | OPPO |
R2-2000449 | Remaining issues on UL LBT failures handling | Intel Corporation |
R2-2000534 | LBT failure handling considering SUL aspect | Samsung |
R2-2000563 | LBT Failures Handling in Non-Connected State | Spreadtrum Communications |
R2-2000603 | SpCell LBT Failure MAC CE Delivery | Apple, vivo |
R2-2000737 | Handling of consistent UL LBT failures during HO | ITRI |
R2-2000772 | [Eri10] SR resources for consistent LBT failure | Fujitsu |
R2-2000822 | UE behavior upon consistent LBT failure | Lenovo, Motorola Mobility |
R2-2000840 | Remaining issues on consistent LBT failures and BWP switching | MediaTek Inc. |
R2-2000904 | On counting the LBT failure of a BWP with multiple sub-bands | CMCC |
R2-2000941 | Uplink transmission upon detection of LBT failure | Nokia, Nokia Shanghai Bell |
R2-2000957 | Remaining issue on handling UL LBT failure | Huawei, HiSilicon |
R2-2000963 | Remaining issues on LBT failure MAC CE | Huawei, HiSilicon |
R2-2000999 | The remaining issues for UL LBT failure | ZTE Corporation, Sanechips |
R2-2001207 | Handling consistent UL LBT failures | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000417 | Remaining issues on NR-U configured grant | OPPO |
R2-2000821 | HARQ process configuration for configured grants | Lenovo, Motorola Mobility |
R2-2000841 | Issues on retransmissions across different configured grant configurations | MediaTek Inc. |
R2-2000959 | Remaining issue on configured grant | Huawei, HiSilicon |
R2-2001205 | Configured Grant remaining issues | Ericsson |
R2-2001206 | Channel access priority for Configured Grant | Ericsson |
R2-2001442 | Consideration of delayed CG confirmation | LG Electronics Polska |
TDoc | Title | Source |
---|---|---|
R2-2000149 | Remaining Issues on CAPC Selection for Configured Grant | vivo |
R2-2000154 | Consideration on SR transmission colliding with PUSCH transmission | Xiaomi Communications |
R2-2000172 | Consideration on SR transmission colliding with PUSCH transmission | Xiaomi Communications |
R2-2000173 | Consideration on SR transmission colliding with PUSCH transmission | Xiaomi Communications |
R2-2000176 | Remaining issues of CAPC | Huawei, HiSilicon |
R2-2000535 | Applicability of NR-U features to licensed carrier | Samsung |
R2-2000669 | LBT failure measurement report handling | Nokia, Nokia Shanghai Bell |
R2-2000838 | PHR for NR-U | Lenovo, Motorola Mobility |
R2-2000842 | On PHR and autonomous retransmissions | MediaTek Inc. |
R2-2000960 | PHR reporting for NR-U | Huawei, HiSilicon |
R2-2000961 | Reply LS on PHR report | Huawei, HiSilicon |
R2-2000962 | Disucssion PDCCH group switching | Huawei, HiSilicon |
R2-2001094 | CAPC selection for UL transmissions | Intel Corporation |
R2-2001108 | Remaining CAPC aspects for CG when SRB is multiplexed | NEC Telecom MODUS Ltd. |
R2-2001204 | Remaining issue on PHR | Ericsson |
R2-2001450 | Dynamic DL opportunity enhancement based on channel busy level in NR-U | LG Electronics Polska |
R2-2001451 | MAC impacts of multiple CCAs in wide band operation | LG Electronics Polska |
TDoc | Title | Source |
---|---|---|
R2-2002022 | NR-U Control Plan Summary | Qualcomm Incorporated |
R2-2002203 | LS on dropping measurement results due to LBT delays | Qualcomm |
R2-2002300 | LS on dropping measurement results due to LBT delays | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000151 | Short Message for Stopping Paging Monitoring in NR-U | vivo |
R2-2000336 | Remaining issues on Paging | Ericsson |
R2-2000337 | RRM in NR-U | Ericsson |
R2-2000403 | Handling of SIB1 decoding error | Nokia, Nokia Shanghai Bell |
R2-2000405 | On RLM and RLF Issues in NR-U | Mediatek Inc. |
R2-2000670 | LS on LBT failure measurement report handling | Nokia, Nokia Shanghai Bell |
R2-2001546 | Cell selection after consecutive UL LBT failures | LG Electronics Inc. |
R2-2001547 | Support of conditional handover for NR-U | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000150 | UE Capability for NR-U Support | vivo |
R2-2000338 | Signaling of Q in NR-U | Ericsson |
R2-2000404 | Including RSSI and Channel Occupancy in NR-U UE Capabilities | Mediatek Inc. |
R2-2000418 | Stopping criteria for paging monitoring | OPPO |
R2-2000442 | UE Capabilities for Measurements in NR-U | Mediatek Inc. |
R2-2000671 | using spare from SIB1 | Nokia, Nokia Shanghai Bell |
R2-2000672 | Q values per cell and useInterlacePUCCH coding | Nokia, Nokia Shanghai Bell |
R2-2000673 | intraCellGuardBand coding | Nokia, Nokia Shanghai Bell |
R2-2000905 | Further enhancement of reporting for NR-U cell reselection | CMCC |
R2-2000964 | Discussion on the remaining issues in RRC signalling | Huawei, HiSilicon |
R2-2001422 | SUL Operating over NR-U | Samsung |
R2-2001432 | On Indicating LBT Failure for NR-U | Samsung |
R2-2001469 | Enhancements to MIB transmission | OPPO |
R2-2001548 | Stopping condition for paging monitoring | LG Electronics Inc. |
R2-2001549 | RLMRLF in NR-U | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000022 | Reply LS on mapping restriction for LCP procedure (R1-19135932; contact: Vivo) | RAN1 |
R2-2000031 | LS to RAN2 on Sidelink UE Information (R3-197770; contact: Ericsson) | RAN3 |
R2-2000042 | Reply LS to RAN2 on UL-SL Prioritization (R4-1915985; contact: Futurewei) | RAN4 |
R2-2000044 | LS on channel raster for NR V2X UE (R4-1916146; contact: CATT) | RAN4 |
R2-2000052 | Reply LS on LS on PC5S and PC5 RRC unicast message protection (S2-1912002; contact: Qualcomm) | SA2 |
R2-2000053 | LS on clarifying NR PC5 priority level (S2-1912003; contact: LGE) | SA2 |
R2-2000061 | Reply LS on PC5 unicast and groupcast security protection (S2-2000971; contact: Interdigital) | SA2 |
R2-2000062 | Reply LS on Response LS on SL RLM/RLF (S2-2000973; contact: Qualcomm) | SA2 |
R2-2000063 | Reply LS on SL RLF handling (S2-2000974; contact: Ericsson) | SA2 |
R2-2000075 | LS on PC5 unicast and groupcast security protection (S3-194658; contact: Interdigital) | SA3 |
R2-2000083 | Reply LS on signalling of sidelink RSRP and CSI (R1-1913693; contact: LGE) | RAN1 |
R2-2000084 | Reply LS on additional high layer information for sidelink physical layer operations (R1-1913694; contact: LGE) | RAN1 |
R2-2000085 | Reply LS on TX resource (re-)selection and MAC related agreements (R1-1913695; contact: LGE) | RAN1 |
R2-2000086 | Reply LS on sidelink synchronization under multiple synchronization sources with different timing (R1-1913696; contact: Qualcomm) | RAN1 |
R2-2000097 | Reply LS on SL RLM/RLF (R1-1913464; contact: InterDigital) | RAN1 |
R2-2000203 | 38.323 CR for NR V2X | CATT |
R2-2000883 | Draft Reply LS on Sideline UE information | Ericsson |
R2-2001963 | Report to Offline #701 | Ericsson |
R2-2001964 | [DRAFT] Reply LS on Sideline UE information | Ericsson |
R2-2001972 | Reply LS on Sideline UE information | RAN2 |
R2-2002018 | 38.323 CR for NR V2X | CATT |
R2-2002234 | 38.323 CR for NR V2X | CATT |
TDoc | Title | Source |
---|---|---|
R2-2000138 | Remaining issues of PC5-RRC | Qualcomm Incorporated |
R2-2000182 | Discussion on Zone Configurations in NR V2X | Apple |
R2-2000185 | Discussion on TX resource pool selection | Apple |
R2-2000189 | Left issues on SLRB re-configuration due to state transition | OPPO |
R2-2000190 | Left issues on failure case handling for NR V2X | OPPO |
R2-2000191 | Left issues on RRC running CR | OPPO |
R2-2000192 | Left issues on RLC mode collision | OPPO |
R2-2000257 | NR V2X CBR left issues | ZTE Corporation, Sanechips |
R2-2000261 | UE behaviors upon PC5-RRC connection release and configuration failure | ZTE Corporation, Sanechips |
R2-2000262 | Discussion on the LS on Sidelink UE Information sent from RAN3 | ZTE Corporation, Sanechips |
R2-2000263 | Consideration on sidelink RLM management | ZTE Corporation, Sanechips |
R2-2000264 | Consideration on NR V2X cross RAT support | ZTE Corporation, Sanechips |
R2-2000269 | (draft)Reply LS on Sidelink UE Information | ZTE Corporation, Sanechips |
R2-2000279 | MAC handling upon PC5 RRC release | vivo |
R2-2000280 | Remaining issues for sidelink SRB | vivo |
R2-2000282 | Resource pool (re-)selection based on HARQ feedback | vivo |
R2-2000327 | Reporting of Sensing Result for Mode 1 UEs | Fraunhofer HHI, Fraunhofer IIS, Lenovo, Motorola Mobility, Deutsche Telekom |
R2-2000328 | Open HARQ Issues | Fraunhofer HHI, Fraunhofer IIS |
R2-2000419 | PC5-RRC connection scope and identification of unicast link | MediaTek Inc. |
R2-2000420 | DRAFT LS on Layer 2 IDs and PC5 unicast link | MediaTek Inc. |
R2-2000456 | Open aspects on mode 2 operation | Intel Corporation |
R2-2000609 | Disucssion on PC5 RRC left issues | Apple |
R2-2000611 | Discussion on Zone Configurations in NR V2X | Apple |
R2-2000614 | Discussion on TX resource pool selection | Apple |
R2-2000710 | Conditions for Uu RRC connection establishment and resume for NR SL | Huawei, HiSilicon |
R2-2000713 | Handling of multiple resource pools for NR sidelink mode-2 | Huawei, HiSilicon |
R2-2000714 | Measurement and reporting for SL-RSRP and SL pathloss for open-loop power control | Huawei, HiSilicon |
R2-2000739 | Tirggering condition for sidelink RSRP reporting | MediaTek Inc. |
R2-2000756 | Running CR to TS 38.331 for 5G V2X with NR sidelink | Huawei, HiSilicon |
R2-2000757 | Summary of email discussion [108#44][V2X] - Miscellaneous RRC issues for 5G V2X with NR Sidelink | Huawei, HiSilicon |
R2-2000881 | Discussion on SL information reporting over Uu | Ericsson |
R2-2000884 | Handling of SLRB (re)configuration failure | Ericsson |
R2-2000885 | Inter-node resource coordination in NR SL | Ericsson |
R2-2000886 | Remaining issues on capability transfer in sidelink | Ericsson |
R2-2000947 | On PC5-S and PC5-RRC signalling | Ericsson |
R2-2001000 | Remaining Exceptional Pool Aspects | LG Electronics Inc. |
R2-2001077 | Zone configuration and Tx Rx distance calculation | Lenovo, Motorola Mobility |
R2-2001090 | Discussion on PC5-RRC AS-layer configuration failure and T400 expiry handling | Intel Corporation |
R2-2001099 | Support of PC5-S Keep alive signalling | Intel Corporation |
R2-2001231 | Discussion on timer T400 | Nokia, Nokia Shanghai Bell |
R2-2001334 | Discussion on V2X SIB Specific Validity Area | Samsung Electronics Co., Ltd |
R2-2001335 | TX profile for selected sidelink RAT | Samsung Electronics Co., Ltd |
R2-2001336 | Aperiodic traffic support in UE Assistance Information | Samsung Electronics Co., Ltd |
R2-2001349 | Issues on layer-2 ID update | LG Electronics France |
R2-2001413 | Running CR to 36.331 for NR V2X | Huawei, HiSilicon |
R2-2001517 | NR V2X Zone ID | Qualcomm Finland RFFE Oy |
R2-2001519 | NR V2X Minimum Communication Range values | Qualcomm Finland RFFE Oy |
R2-2001533 | NR V2X Zone ID | Qualcomm Finland RFFE Oy |
R2-2001541 | NR V2X Zone ID | Qualcomm Finland RFFE Oy |
R2-2001568 | UE behaviour on receipt of RRCReconfigurationFailureSidelink message and T400 expiry | Qualcomm Finland RFFE Oy |
R2-2001570 | RRC connection initiation trigger for SLRB configuration handling | Samsung Electronics Co., Ltd |
R2-2001571 | Further discussion on SL-RSRP reporting | Samsung Electronics Co., Ltd |
R2-2001593 | Clarification on how UE initiates a Sidelink UE Information procedure for NR sidelink communication | ASUSTeK |
R2-2001594 | Clarification on how UE reports sidelink QoS flow release | ASUSTeK |
R2-2001595 | Supporting both IP based and non-IP based V2X messages over PC5 | ASUSTeK |
R2-2001965 | Report for the offline discussion on Category-2 proposals in RRC summary | Huawei (Rapporteur) |
R2-2001966 | Introduction of 5G V2X with NR sidelink | Huawei, HiSilicon |
R2-2001967 | Introduction of 5G V2X with NR Sidelink in TS 36.331 | Huawei, HiSilicon |
R2-2002011 | Summary document for AI 6.4.2.1 - RRC aspects | Huawei (Rapporteur) |
R2-2002093 | Summary document for AI 6.4.2.1 - RRC aspects | Huawei (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000193 | Left issues on SL capability | OPPO |
R2-2000194 | Summary of [108#50][V2X] Feature List and UE caps (OPPO) | OPPO |
R2-2000199 | Open issues on system information | OPPO |
R2-2000204 | Discussion on inter-RAT Cell Selection/Reselection | CATT |
R2-2000266 | Report of open issues on V2X 38.304 and 36.304 running CR | ZTE Corporation, Sanechips |
R2-2000267 | (running)36.304CR on cell selection(reselection) for NR V2X UE | ZTE Corporation, Sanechips |
R2-2000268 | (running)38.304CR on cell selection(reselection) for NR V2X UE | ZTE Corporation, Sanechips |
R2-2000281 | Mode switch for QoS guarantee in NR V2X | vivo |
R2-2000530 | PC5 L2/L3 protocols for unicast and groupcast | Kyocera |
R2-2000712 | General framework for the introduction of UE capabilities for 5G V2X with NR SL in TS 38.306 | Huawei, HiSilicon |
R2-2000882 | Discussion on SL Mode 2 left issues | Ericsson |
R2-2001001 | Remaining issues on V2X System Information | LG Electronics Inc. |
R2-2001417 | Remaining issues on cell reselection | Huawei, HiSilicon |
R2-2001418 | Remaining issue on sidelink AS configuration | Huawei, HiSilicon |
R2-2001569 | Further discussion on cell reselection for V2X | Samsung Electronics Co., Ltd |
R2-2001578 | NR sidelink communication resource selection | Qualcomm Finland RFFE Oy |
R2-2001961 | Summary of NR V2X cell selection/reselection related contributions | ZTE Corporation, Sanechips |
R2-2001974 | Report of offline discussion 709 | ZTE Corporation, Sanechips |
R2-2001975 | LS on Sidelink UE capability for (NG)EN-DC and NE-DC | OPPO |
R2-2001978 | LS on Sidelink UE capability for (NG)EN-DC and NE-DC | OPPO |
R2-2001979 | LS on Sidelink UE capability for (NG)EN-DC and NE-DC | RAN2 |
R2-2002023 | Summary of sidelink capability related contributions | OPPO |
R2-2002185 | (running)36.304CR on cell selection(reselection) for NR V2X UE | ZTE Corporation, Sanechips |
R2-2002186 | (running)38.304CR on cell selection(reselection) for NR V2X UE | ZTE Corporation, Sanechips |
R2-2002263 | Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2002264 | Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2002265 | Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2002317 | CR on cell selection/ reselection for NR V2X UE | ZTE Corporation, Sanechips |
R2-2002318 | CR on cell selection/ reselection for NR V2X UE | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2000140 | Remaining MAC issues on NR V2X mode 1 | Qualcomm Incorporated |
R2-2000181 | Discussion on Tx-Side RLM Support | Apple |
R2-2000183 | Discussion on HARQ feedback for Sidelink groupcast | Apple |
R2-2000184 | Draft Reply LS on Sidelink HARQ Feedback for Groupcast | Apple |
R2-2000186 | Discussion on remaining issues on SL HARQ process | Apple |
R2-2000195 | Left issues on MAC running CR for NR-V2X | OPPO |
R2-2000196 | Left issues on HARQ for NR-V2X | OPPO |
R2-2000200 | Open issues on prioritization | OPPO |
R2-2000202 | Discussion on multiple configured grants | OPPO |
R2-2000205 | MAC open issues | CATT |
R2-2000206 | Leftover Issue of SL SR | CATT |
R2-2000207 | New Resource (Re-) Selection Triggers | CATT |
R2-2000208 | Draft LS to RAN1 on New Resource (Re-) Selection Triggers | CATT |
R2-2000209 | Remaining Issues on NR SL RLM/RLF Procedure | CATT |
R2-2000210 | Draft LS to RAN1 on NR SL RLM/RLF Procedure | CATT |
R2-2000211 | Leftover Issues on LCP | CATT |
R2-2000212 | Remaining Issues on Multiple SL CGs | CATT |
R2-2000213 | Draft LS to RAN1 on the maximum number of HARQ process used by one SL CG configuration | CATT |
R2-2000229 | Remaining Issues of Sidelink CSI Reporting | Samsung Electronics Co., Ltd |
R2-2000234 | [Draft] LS to RAN1 on cast type indication | CATT |
R2-2000235 | Running CR to 38.321 on Introduction of 5G V2X with NR Sidelink | LG Electronics France |
R2-2000236 | Running CR to 36.321 on Introduction of 5G V2X with NR Sidelink | LG Electronics France |
R2-2000237 | Report of [108#100][V2X]: Miscellaneous issues on MAC CR for 5G V2X with NR Sidelink | LG Electronics France |
R2-2000258 | Groupcast HARQ feedback related issue | ZTE Corporation, Sanechips |
R2-2000259 | Discussion on left MAC issues | ZTE Corporation, Sanechips |
R2-2000260 | Discussion on LTE-SL/NR-UL prioritization | ZTE Corporation, Sanechips |
R2-2000283 | Left issues on CSI report | vivo |
R2-2000284 | The UE behivour of deactivated sidelink BWP | vivo |
R2-2000285 | HARQ feedback of SL transmission reporting on uplink | vivo |
R2-2000286 | MAC PDU handling for reserved/unkonwn LCID | vivo |
R2-2000287 | Remaining issues on HARQ support for NR Sidelink | vivo |
R2-2000288 | SL BSR triggered by retxBSR-Timer expiry | vivo |
R2-2000454 | Remaining aspects for SL HARQ operation | Intel Corporation |
R2-2000455 | Open aspects on SL Configured Grant design | Intel Corporation |
R2-2000457 | Open issues on mode 2 resource selection | Intel Corporation |
R2-2000458 | Cross-RAT scheduling for NR V2X SL | Intel Corporation |
R2-2000532 | Remaining issues of UL/SL prioritization | MediaTek Inc. |
R2-2000543 | Report on email discussion on [108#99][V2X] HARQ based TX side RLM/RLF | InterDigital |
R2-2000544 | Draft CR to 38.321 for HARQ-Based RLF at TX UE | InterDigital |
R2-2000545 | Draft CR to 38.331 for HARQ-Based RLF at TX UE | Interdigital |
R2-2000546 | HARQ Buffer Management at the RX UE | InterDigital, Lenovo, Motorola Mobility, ZTE |
R2-2000547 | Remaining Aspects of CSI Reporting | InterDigital |
R2-2000548 | Remaining Asoects of Sidelink HARQ Feedback for Groupcast | InterDigital |
R2-2000549 | Details of Flexible BSR Prioritization | InterDigital, Apple |
R2-2000550 | Remaining Aspects of HARQ for NR V2X | InterDigital |
R2-2000562 | Miscellaneous MAC issues for 5G V2X with NR Sidelink | Spreadtrum Communications |
R2-2000608 | UL-SL Prioritization under SL incapable RAN | Apple |
R2-2000610 | Discussion on Tx-Side RLM Support | Apple |
R2-2000612 | Discussion on HARQ feedback for Sidelink groupcast | Apple |
R2-2000613 | Draft Reply LS on Sidelink HARQ Feedback for Groupcast | Apple |
R2-2000615 | Discussion on remaining issues on SL HARQ process | Apple |
R2-2000709 | On SL LCP mapping restriction for HARQ feedback enable and disable | Huawei, HiSilicon |
R2-2000711 | Further discussion on the Sidelink CSI reporting related issues | Huawei, HiSilicon |
R2-2000715 | On the left FFS on SR trigger for SL Mode 1 | Huawei, Lenovo, Motorola Mobility, ZTE, Sanechips, OPPO, HiSilicon |
R2-2000773 | Discussion on sidelink SR trigger | Fujitsu |
R2-2000774 | Discussion on remaining PDB | Fujitsu |
R2-2000820 | SL BWP operation | Lenovo, Motorola Mobility |
R2-2000823 | Remaining aspects of SL HARQ protocol operation | Lenovo, Motorola Mobility |
R2-2000944 | On the need of HARQ based RLF | Ericsson |
R2-2000946 | Discussion on congestion control | Ericsson |
R2-2000948 | Discussion on SL Mode 1 left issues | Ericsson |
R2-2000950 | MAC miscellaneous issues | Ericsson |
R2-2001022 | Considerations on QoS based resource pool for NR V2X | Lenovo, Motorola Mobility |
R2-2001023 | Views on miscellaneous issues for NR V2X MAC layer | Lenovo, Motorola Mobility |
R2-2001073 | Blind HARQ retransmissions | Lenovo, Motorola Mobility |
R2-2001074 | Ensuring timeliness of CSI Reporting | Lenovo, Motorola Mobility |
R2-2001076 | RLM Procedure | Lenovo, Motorola Mobility |
R2-2001078 | Remaining aspects of NR V2X Tx UE behavior | Lenovo, Motorola Mobility, Deutsche Telekom, Fraunhofer HHI and Fraunhofer IIS, Continental Automotive GmbH |
R2-2001107 | Discussion on BSR prioritization issue | Beijing Xiaomi Software Tech |
R2-2001337 | Remaining issue in SL SCH subheader | Samsung Electronics Co., Ltd |
R2-2001338 | Clarification for LCP procedure with HARQ feedback | Samsung Electronics Co., Ltd |
R2-2001339 | Handling of error in MAC PDU for SL unicast | Samsung Electronics Co., Ltd |
R2-2001346 | Logical Channel with/without HARQ Feedback Multiplexing | Panasonic Corporation |
R2-2001414 | Configuration Aspects for Configured Sidelink Grant in Mode-1 | Huawei, HiSilicon |
R2-2001416 | Remaining issues on HARQ operation for NR SL | Huawei, HiSilicon |
R2-2001481 | Need of clarification on NDI in SCI for configured grant type 2 | ITL |
R2-2001550 | Remaining issues for SL-SCH MAC subheader | Qualcomm Finland RFFE Oy |
R2-2001552 | Remaining issues on RLM/RLF | Qualcomm Finland RFFE Oy |
R2-2001588 | PC5 groupcast handling | Qualcomm Finland RFFE Oy |
R2-2001596 | Considerations of CSI reporting regarding SL LCP | ASUSTeK |
R2-2001962 | Summary of contributions to MAC for 5G V2X with NR Sidelink | LG Electronics Inc. (Rapporteur) |
R2-2001968 | [Offline Disc#704] Identified proposals to V2X MAC | LG Electronics Inc. (Rapporteur) |
R2-2001969 | [Running CR] Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2001970 | [Running CR] Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2002054 | Remaining aspects of NR V2X Tx UE behavior | Lenovo, Motorola Mobility, Deutsche Telekom, Fraunhofer HHI and Fraunhofer IIS, Continental Automotive GmbH, MediaTek, Bosch |
R2-2002074 | Report on email discussion on [108#99][V2X] HARQ based TX side RLM/RLF | InterDigital |
R2-2002316 | Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
R2-2002342 | Introduction of 5G V2X with NR Sidelink | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000201 | Discussion on PDCP open issues | OPPO |
R2-2000214 | Summary of Email discussion [108#102][V2X] Remaining issues on PDCP | CATT |
R2-2000215 | Draft LS to SA3 on NR V2X Security issues on PDCP | CATT |
R2-2000278 | Running CR to 37324 for 5G_V2X_NRSL | vivo (Rapporteur) |
R2-2000887 | Running CR for 38.322 for NR V2X | Ericsson |
R2-2000945 | On PDCP re-establishment | Ericsson |
R2-2000949 | Discussion on RLC left issues | Ericsson |
R2-2001308 | Initialization of HFNs of RX_DELIV and RX_NEXT | Futurewei |
R2-2001340 | Security impact in SL PDCP | Samsung Electronics Co., Ltd |
R2-2001499 | Initial Value of RX_DELIV and RX_NEXT | Samsung |
R2-2001544 | PDCU SDU Type Length | Qualcomm Finland RFFE Oy |
R2-2001973 | [DRAFT] LS to SA3 on NR V2X Security issues on PDCP | CATT |
R2-2001976 | Report for offline discussion on RLC left issues | Ericsson |
R2-2001977 | Summary of offline discussion for open issues on V2X PDCP (CATT) | CATT (rapporteur) |
R2-2001980 | LS to SA3 on NR V2X Security issues | RAN2 |
R2-2002017 | Summary of PDCP remaining issues on NR V2X | CATT |
R2-2002019 | Summary for NR V2X RLC left issues | Ericsson |
R2-2002051 | [Pre109e][V2X] Summary on SDAP | vivo |
R2-2002311 | CR for 38.322 for NR V2X | Ericsson |
R2-2002319 | Running CR to 37324 for 5G_V2X_NRSL | vivo (Rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000197 | Discussion on resource allocation mode for NR-V2X | OPPO |
R2-2000265 | Discussion on multi-mode co-existence | ZTE Corporation, Sanechips |
R2-2000696 | Remaining issue on Groupcast and Broadcast Support | ITRI |
R2-2001075 | MCR for Option 2 FB and group size ambiguity | Lenovo, Motorola Mobility |
R2-2001091 | PC5 QoS information in UAI | Intel Corporation |
R2-2001415 | Remaining issue for groupcast HARQ feedback option 1 and option 2 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000354 | Introduction of UECapabilityInformation segmentation in TS38.331 | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd, MediaTek Inc, CATT, Ericsson, Intel Corporation, Spreadtrum Communications |
R2-2000421 | Introduction of RACS and DL RRC segmentation | MediaTek Inc. |
R2-2000422 | Introduction of RACS and DL RRC segmentation | MediaTek Inc. |
R2-2000423 | Introduction of UECapabilityInformation segmentation in 36.331 | MediaTek Inc., CATT, Ericsson, Spreadtrum Communications, ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated |
R2-2000424 | Work plan for RACS-RAN work item | MediaTek Inc., CATT |
R2-2001687 | Introduction of RACS and DL RRC segmentation | MediaTek Inc., Ericsson, CATT |
R2-2001688 | Introduction of RACS and DL RRC segmentation | MediaTek Inc., Ericsson, CATT |
R2-2001689 | Introduction of UECapabilityInformation segmentation in TS38.331 | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd, MediaTek Inc, CATT, Ericsson, Intel Corporation, Spreadtrum Communications |
R2-2001690 | Introduction of UECapabilityInformation segmentation in 36.331 | MediaTek Inc., CATT, Ericsson, Spreadtrum Communications, ZTE Corporation, Sanechips, OPPO, Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000355 | UE radio capability ID in inter-node RRC messages | ZTE Corporation, Sanechips |
R2-2000356 | Introduction of UE radio capability ID in inter-node RRC messages | ZTE Corporation, Sanechips |
R2-2001227 | Inter-node signaling of UE Capabilities | Ericsson |
R2-2001691 | [DRAFT] LS on Optional signalling of UE capabilities at handover | Ericsson |
R2-2001702 | LS on RACS and signaling of UE capabilities at handover | RAN2 |
R2-2001891 | LS on RACS and signaling of UE capabilities at handover | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000765 | Transfer of segmented UECapabilityInformation by SRB2 | Samsung |
R2-2000939 | Generic stage-2 description for RRC segmentation | Ericsson |
R2-2001329 | Remaining issues on UE capability segmentation | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000060 | Reply LS on reference time delivery (S2-1912769; contact: Qualcomm) | SA2 |
R2-2000783 | RRC running CR for NR IIoT | Ericsson |
R2-2000784 | LTE RRC running CR for NR IIoT | Ericsson |
R2-2000785 | Remaining minor issues in [108#32][IIoT] Running CR 38.331 | Ericsson |
R2-2001046 | Summary of open issues for IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2001052 | UE feature list and capabilities remaining issues | Nokia, Nokia Shanghai Bell |
R2-2001053 | Summary of e-mail discussion: [108#47][IIOT] UE feature list | Nokia, Nokia Shanghai Bell |
R2-2001054 | UE radio access capabilities introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2001055 | UE feature list introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2001280 | Summary of e-mail discussion on PDCP Running CR for NR IIOT | LG Electronics Inc. |
R2-2001281 | PDCP running CR for NR IIOT | PDCP Rapporteur (LG Electronics Inc.) |
R2-2001282 | Introducing EHC in LTE PDCP | PDCP Rapporteur (LG Electronics Inc.) |
R2-2001487 | MAC Running CR for NR IIOT | Samsung |
R2-2001657 | RRC running CR for NR IIoT | Ericsson |
R2-2001658 | LTE RRC running CR for NR IIoT | Ericsson |
R2-2002013 | Introduction of NR Industrial IoT features | Nokia, Nokia Shanghai Bell |
R2-2002072 | Summary: UE features and capabilities | Nokia, Nokia Shanghai Bell |
R2-2002169 | PDCP running CR for NR IIOT | PDCP Rapporteur (LG Electronics Inc.) |
R2-2002170 | Introducing EHC in LTE PDCP | PDCP Rapporteur (LG Electronics Inc.) |
R2-2002279 | UE radio access capabilities introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2002280 | UE feature list introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
R2-2002282 | Summary of [AT109e][031][IIOT] IIOT UE capabilities | Nokia, Nokia Shanghai Bell |
R2-2002341 | Introduction of NR IIOT | Samsung |
R2-2002355 | Summary of IIOT WI agreements and open issues | Nokia, Nokia Shanghai |
R2-2002356 | Introduction of NR Industrial IoT features | Nokia, Nokia Shanghai Bell |
R2-2002359 | Introduction of NR IIoT | Ericsson |
R2-2002360 | Introduction of NR IIoT | Ericsson |
R2-2002366 | Introduction of NR IIOT | PDCP Rapporteur (LG Electronics Inc.) |
R2-2002367 | Introducing EHC in LTE PDCP | PDCP Rapporteur (LG Electronics Inc.) |
R2-2002408 | Introduction of NR IIOT | PDCP Rapporteur (LG Electronics Inc.) |
R2-2002409 | Introducing EHC in LTE PDCP | PDCP Rapporteur (LG Electronics Inc.) |
TDoc | Title | Source |
---|---|---|
R2-2000110 | Remaining Issues on Propagation Delay Compensation | CATT |
R2-2000427 | Discussion on propagation delay compensation | Huawei, HiSilicon |
R2-2000428 | Remaining issues of reference time delivery | Huawei, HiSilicon |
R2-2000489 | UE report of the TSC interest | vivo |
R2-2000490 | Discussion on propagation delay compensation in rel-16 | vivo |
R2-2000491 | Discussion on provisioning of timing information for EN-DC | vivo |
R2-2000492 | TP on 38.331 of provisioning of timing information for EN-DC | vivo |
R2-2000493 | TP on 36.331 of provisioning of timing information for EN-DC | vivo |
R2-2000705 | Consideration on propagation delay compensation for TSC | OPPO |
R2-2000786 | On downlink delay compensation | Ericsson, LG, Samsung |
R2-2000787 | On UE need for time synch | Ericsson |
R2-2001047 | Propagation delay compensation | Nokia, Nokia Shanghai Bell |
R2-2001048 | Determining the need for accurate reference time delivery | Nokia, Nokia Shanghai Bell |
R2-2001212 | Propagation Delay Compensation in TSC | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2001233 | Request for accurate reference timing delivery in TSC | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
R2-2001297 | Open issues in Accurate Reference Timing Delivery | Qualcomm Incorporated |
R2-2001426 | Remaining Issues for Propagation Delay Compensation | CMCC |
R2-2001427 | TP on IIoT Running RRC for Propagation Delay Compensation | CMCC |
R2-2002012 | Summary: Accurate reference timing | Nokia, Nokia Shanghai Bell |
R2-2002281 | Summary of [AT109e][032][IIOT] Accurate Reference Timing | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2000111 | Remaining issues for multiple CG configurations | CATT |
R2-2000429 | Configured grant configurations for SUL serving cell | Huawei, HiSilicon |
R2-2000430 | Discussion on the new CG type 2 confirmation MAC CE | Huawei, HiSilicon |
R2-2000431 | Method to avoid confusion between UE and network for CG type 1 | Huawei, HiSilicon |
R2-2000564 | Consideration on collision of measurement gap and TSN traffic | Spreadtrum Communications |
R2-2000697 | SFN misalignment issue on periodicities of non-divisor of 10240ms | OPPO |
R2-2000699 | Left issue on multiple entry confirmation MAC CE | OPPO |
R2-2000706 | Support mapping LCHs configured with allowedCG-list to dynamic grant | OPPO |
R2-2000788 | LCP restriction enhancement based on PHY priority indcation | Ericsson |
R2-2000789 | SPS and CG remaining MAC aspects | Ericsson |
R2-2000790 | TSC AI clarifications: meaning of arrival time | Ericsson |
R2-2000791 | Draft LS: TSC AI clarifications for arrival time | Ericsson |
R2-2001049 | Remaining issues on TSC scheduling | Nokia, Nokia Shanghai Bell |
R2-2001171 | LCP restrictions in IIoT | Intel Corporation |
R2-2001290 | Open issues in Scheduling Enhancements | Qualcomm Incorporated |
R2-2001428 | Remaining Issues for Multiple SPS-CG enhancements | CMCC |
R2-2001429 | Remaining Issues for LCP restrictions | CMCC |
R2-2001461 | The considerations on scheduling enhancement | ZTE Corporation, Sanechips |
R2-2001476 | TP on IIoT Running RRC for Scheduling Enhancements | CMCC |
R2-2001489 | Remaining Issues on CG Confirmation MAC CE | Samsung |
R2-2001493 | LCP Restriction for allowedCG-List and allowedPHY-PriorityIndex | Samsung |
R2-2001498 | Type 1 Configured Grant with Integer Periodicity | Samsung |
R2-2001555 | Consideration on multiple entry CG confirmation MAC CE | LG Electronics Inc. |
R2-2001613 | Multiple Entry Configured Grant Confirmation MAC CE | Intel Corporation |
R2-2001627 | Impact of CG/SPS with periodicities non dividing HF length | Sequans Communications |
R2-2001660 | Summary on Scheduling Enhancement for IIoT (6.7.2.2) | Ericsson |
R2-2002091 | Summary on Scheduling Enhancement for IIoT (6.7.2.2) | Ericsson |
R2-2002294 | Summary on [AT109e][033][IIOT] Scheduling Enhancements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000112 | Discussion on the processing order of ROHC and EHC | CATT |
R2-2000113 | Remaining Issues of EHC | CATT |
R2-2000175 | Report of email discussion [108#53] [IIOT] EHC remaining issues | Huawei, HiSilicon |
R2-2000432 | Further discussion on EHC related issues | Huawei, HiSilicon |
R2-2000477 | Remaining issues in Ethernet header compression | Intel Corporation |
R2-2000494 | Remaining issues for EHC | vivo |
R2-2000726 | SDAP control PDU handling in Rel-16 EHC | Samsung |
R2-2000792 | EHC solution | Ericsson |
R2-2000793 | EHC padding removal | Ericsson |
R2-2000834 | EHC absence of Q-Tags and NACK feedback | Sony |
R2-2000867 | Further Consideration on Ethernet Header Compression | China Telecom Corporation Ltd. |
R2-2001050 | Joint IP and Ethernet Header compression | Nokia, Nokia Shanghai Bell |
R2-2001051 | Ethernet Header compression remaining issues | Nokia, Nokia Shanghai Bell |
R2-2001229 | Remaining issues for EHC in TSC | ZTE Corporation, Sanechips |
R2-2001287 | CR for introducing Ethernet Headere Compression features | Huawei,HiSilicon |
R2-2001298 | Open issues in Ethernet Header Compression | Qualcomm Incorporated |
R2-2001309 | Configuration and Processing Order of ROHC and EHC | Futurewei |
R2-2001501 | Discussion on EHC feedback | LG Electronics Inc. |
R2-2001502 | Discussion on performing ROHC and EHC | LG Electronics Inc. |
R2-2001521 | Discussion on support of the padding removal | LG Electronics Inc. |
R2-2002020 | Summary of submissions on Ethernet header compressions | MediaTek Inc. |
R2-2002097 | Reply LS on need for Ethernet padding compression (S1-201085; contact: Qualcomm) | SA1 |
R2-2002182 | [AT109e][034][IIOT] EHC Phase 1 summary | MediaTek Inc. |
R2-2002296 | [AT109e][034][IIOT] EHC Phase 2 summary | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000114 | Remaining Issues on Autonomous Transmission | CATT |
R2-2000485 | Summary on deprioritized transmissions | CATT |
R2-2000495 | Discussion on the MAC PDU recovery procedure | vivo |
R2-2000593 | Open Issues on TSC Scheduling Enhancement | Apple |
R2-2000698 | Left issues on autonomous transmission | OPPO |
R2-2000703 | Consideration on CG timer for the deprioritized MAC PDU | OPPO |
R2-2000755 | Deprioritized transmissions on configured grants | III |
R2-2000794 | Handling of de-prioritized MAC PDUs | Ericsson |
R2-2000813 | Remaining Issues on Autonomous Transmission of Pending MAC PDUs | Nokia, Nokia Shanghai Bell |
R2-2000825 | HARQ retransmissions for deprioritized PDU with empty HARQ buffer | Sony |
R2-2000839 | Remaining details for autonomous retransmission functionality | Lenovo, Motorola Mobility |
R2-2000845 | On UL intra-UE prioritisation | MediaTek Inc. |
R2-2001028 | Consideration on the de-prioritized PDU transmission | Lenovo, Motorola Mobility |
R2-2001033 | Remaining issues on Configured Grant | Huawei, HiSilicon |
R2-2001291 | Open issues in autonomous retransmission | Qualcomm Incorporated |
R2-2001420 | Autonomous transmission on different CG configuration | LG Electronics Polska |
R2-2001475 | Remaining Issues for LCP restrictions | CMCC |
R2-2001477 | Remaining Issues for Handling of deprioritized transmission | CMCC |
R2-2001490 | Autonomous Retransmissions of Different CG Configurations and Timeline Restriction | Samsung |
R2-2001628 | Rescheduling dropped CG when PDU was not generated | Sequans Communications |
R2-2002286 | Report of [035][IIOT] Deprioritized transmissions (CATT)”. | CATT |
TDoc | Title | Source |
---|---|---|
R2-2000115 | Remaining issues for intra-UE multiplexing and prioritization | CATT |
R2-2000116 | MAC CE priorities and LCP mapping restrictions | CATT |
R2-2000486 | Avoiding unnecessary preemption among eMBB traffic | CATT |
R2-2000496 | Intra-UE Prioritization with CA | vivo |
R2-2000497 | Remaining issues for SR and PUSCH collision | vivo |
R2-2000701 | Grant collision with the same HARQ process | OPPO |
R2-2000702 | Discussion on SR cancelling on intra-UE prioritization involving SR | OPPO |
R2-2000722 | Consideration of configured grant timer for Intra-UE prioritization | Asia Pacific Telecom co. Ltd |
R2-2000795 | On PHY and MAC interaction to support intra-UE prioritization | Ericsson |
R2-2000796 | Draft LS on PHY and MAC interaction to support intra-UE prioritization | Ericsson |
R2-2000797 | Remaining details of intra-UE prioritization | Ericsson |
R2-2000814 | Intra-UE Prioritization for conflicts with existing MAC PDU | Nokia, Nokia Shanghai Bell |
R2-2000815 | Intra-UE Prioritization Considering MAC CEs and Configured Grant Timer | Nokia, Nokia Shanghai Bell |
R2-2001010 | HARQ process collision between CG and DG | Huawei, HiSilicon |
R2-2001011 | Prioritization issues for MAC CEs and PUSCH | Huawei, HiSilicon |
R2-2001029 | L1-priority applies for CG | Lenovo, Motorola Mobility |
R2-2001101 | Handling of dropped SRs | InterDigital |
R2-2001289 | Open issues in Intra-UE prioritization | Qualcomm Incorporated |
R2-2001431 | The handling of de-prioritized CG due to SR transmission | LG Electronics Polska |
R2-2001434 | CS-RNTI ambiguity in IIoT | LG Electronics Polska |
R2-2001457 | Remainiing issues on intra-UE multiplexing | ZTE Corporation, Sanechips |
R2-2001458 | Consideration on HARQ Conflict Between Configured Grant and Dynamic Grant | ZTE Corporation, Sanechips |
R2-2001459 | Consideration on the multiplexing between BSR MAC CE and URLLC data | ZTE Corporation, Sanechips |
R2-2001488 | Summary of Data-Data Prioritization and SR-Data Prioritization | Samsung |
R2-2001492 | UL-SCH Resource De-prioritization by Deprioritized SR | Samsung |
R2-2001494 | Condition of Priority Value Determination | Samsung |
R2-2001495 | Transmission of Deprioritized Data by Retransmission Grant | Samsung |
R2-2001496 | lch-basedPrioritization and MAC CE Priority | Samsung |
R2-2001497 | Prioritization of SR Transmission | Samsung |
R2-2001557 | Priority determination considering MAC CE | LG Electronics Inc. |
R2-2001597 | Additional prioritization for configured uplink grant | ASUSTeK |
R2-2001598 | Handling UL grant prioritization with non-overlapping PUSCH duration | ASUSTeK |
R2-2002083 | Summary of Data-Data Prioritization and SR-Data Prioritization | Samsung |
R2-2002190 | Report of [Offline-036][IIOT] Data Data and Data SR prioritization | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2000700 | Intra-UE prioritization between multiple SRs | OPPO |
R2-2001566 | Measurement gap skipping for TSN traffic | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000117 | Discussion on the Rel-15 Duplication MAC CE | CATT, Sharp |
R2-2000118 | On the Open Issues of PDCP Duplication | CATT |
R2-2000119 | LCH-to-Cell Restriction in Rel-16 | CATT |
R2-2000498 | Reusing legacy MAC CE for multi-leg PDCP duplication | vivo |
R2-2000499 | Discussion on LCID restriction | vivo |
R2-2000565 | Discussion on configured selective PDCP duplication mechanism | Spreadtrum Communications |
R2-2000597 | Open Items for usage of R15 MAC CE for PDCP Duplication | Apple |
R2-2000704 | Cell restriction for PDCP duplication in IIoT | OPPO |
R2-2000775 | MAC CE for duplication per UE or per MAC entity | Fujitsu |
R2-2000776 | R15 MAC CE duplication on/off for R16 duplication on/off | Fujitsu |
R2-2000798 | Remaining issues related to MAC CEs for PDCP duplication | Ericsson |
R2-2000816 | On MAC CEs for PDCP Duplication | Nokia, Nokia Shanghai Bell |
R2-2000817 | PDCP Duplication for SRB in Rel-16 | Nokia, Nokia Shanghai Bell |
R2-2000818 | PDCP PDU Discarding by Secondary RLC entities | Nokia, Nokia Shanghai Bell |
R2-2000868 | Discussion on MAC CE for PDCP Duplication | China Telecom Corporation Ltd. |
R2-2000929 | To discard duplicate PDUs for the RLCs deactivated for PDCP duplication | Sharp, CATT |
R2-2000940 | CR for discarding duplicate PDUs for the RLCs deactivated for PDCP duplication | Sharp |
R2-2001012 | Discussion on PDCP duplication activation/deactivation | Huawei, HiSilicon |
R2-2001013 | Remaining issues of cell restriction for PDCP duplication | Huawei, HiSilicon |
R2-2001030 | Reuse R15 MAC CE on/off for R16 configurations | Lenovo, Motorola Mobility |
R2-2001172 | Remaining issues in PDCP duplication enhancements | Intel Corporation |
R2-2001283 | Issues on Duplicate PDU discard | LG Electronics Inc. |
R2-2001284 | Issues on Duplication Activation-Deactivation MAC CE | LG Electronics Inc. |
R2-2001286 | Summary of PDCP duplication enhancements | LG Electronics Inc. |
R2-2001288 | Open issues in PDCP duplication enhancements | Qualcomm Incorporated |
R2-2001460 | Discussion on UE based PDCP dupllication activation/deactivation | ZTE Corporation, Sanechips |
R2-2001462 | Remaining issues on PDPC duplication enhancement | ZTE Corporation, Sanechips |
R2-2001491 | Remaining Issues of PDCP Duplication for IIOT | Samsung |
R2-2002171 | Summary of [AT109e][037][IIOT] PDCP Duplication Enhancements | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000010 | LS on agreements related to NR Positioning (R1-1913522; contact: Nokia) | RAN1 |
R2-2000033 | LS on DL-AOD procedure (R3-197794; contact: Huawei) | RAN1 |
R2-2000038 | Response LS on Reference Point for Timing Related Measurements in FR2 (R4-1915801; contact: CATT, Ericsson) | RAN4 |
R2-2001933 | [DRAFT] reply LS on agreements related to NR Positioning | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2000473 | Running stage 2 CR on NR positioning (\n[108#84][NR Pos] ) | Intel Corporation, ESA |
R2-2000513 | Discussion on non-periodic SRS resource for positioning | ZTE Corporation |
R2-2000967 | Remaining issues on SRS configuration | Huawei, HiSilicon |
R2-2001080 | Stage 2 CR for the introduction of SSR positioning support into LTE | ESA, Intel Corporation |
R2-2001214 | Semi-persistent and aperiodic SRS-for-positioning | Qualcomm Incorporated |
R2-2001237 | Spatial Relations and MAC CE | Ericsson |
R2-2001931 | Summary on the Stage-2 Aspects of R16 Positioning | Huawei, HiSilicon, Intel Corporation |
R2-2001934 | Running stage 2 CR on NR positioning (\n[108#84][NR Pos] ) | Intel Corporation, ESA |
R2-2001935 | Summary of offline discussion #611 on non-periodic SRS for positioning | Huawei, HiSilicon |
R2-2001936 | Summary of offline discussion #612 on spatial relationship for positioning | Huawei, HiSilicon |
R2-2001960 | RAN1 stage 2 agreements related to positioning | Intel Corporation |
R2-2002111 | CR for the introduction of SSR positioning support into LTE | ESA, Intel Corporation |
R2-2002241 | Running CR for the introduction of NR positioning | Intel Corporation, ESA |
R2-2002246 | Running CR for the introduction of NR positioning on MAC spec | Huawei, HiSilicon |
R2-2002330 | Running CR for the introduction of NR positioning on MAC spec | Huawei, HiSilicon |
R2-2002399 | Introduction of NR positioning | Intel Corporation, ESA |
R2-2002400 | Introduction of NR positioning on MAC spec | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000243 | UL SRS UE capabilities captured by RRC in TS 38.331. | CATT |
R2-2000968 | Discussion on GAP request for RSTD measurement | Huawei, HiSilicon |
R2-2001216 | Introduction of PPP-RTK (SSR) | Qualcomm Incorporated |
R2-2001228 | Introduction of NR positioning | Qualcomm Incorporated |
R2-2001255 | Running CR on 38.331 for on-demand SI procedure in RRC_CONNECTED for Positioning | Ericsson |
R2-2001333 | Running CR for the introduction of NR positioning | Ericsson |
R2-2001937 | Introduction of PPP-RTK (SSR) | Qualcomm Incorporated |
R2-2001938 | Running CR for the introduction of NR positioning | Ericsson |
R2-2002052 | Summary for Positioning RRC running CR | Ericsson |
R2-2002112 | Running CR for the introduction of NR positioning | Ericsson |
R2-2002242 | Running CR for the introduction of NR positioning | Ericsson |
R2-2002247 | Running CR for the introduction of NR positioning | Ericsson |
R2-2002401 | Introduction of NR positioning | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000241 | Design of ProvideAssistantData for RAT-Dependent positioning methods | CATT |
R2-2000289 | Reduce overhead of RSTD measurement report | vivo |
R2-2000290 | Remaining issues on support of NR RAT-dependent positioning | vivo |
R2-2000474 | LPP CR Capturing RAN1 parameters for positioning ([108#85][NR Pos]) | Intel Corporation |
R2-2000475 | UE capability on positioning ([108#85][NR Pos]) | Intel Corporation |
R2-2000476 | Open issues in LPP CR | Intel Corporation |
R2-2000966 | Remaining issues on DL positioning procedure | Huawei, HiSilicon, MediaTek |
R2-2000969 | Discussion on DL-AoD positioning procedure | Huawei, HiSilicon |
R2-2000970 | Discussion on SRS capability transfer | Huawei, HiSilicon |
R2-2000991 | SSB Configuration for UL-PRS and DL-PRS | LG Electronics Inc. |
R2-2001168 | Introduction of Rel-16 NR positioning | Intel Corporation |
R2-2001173 | Summary on LPP for aganda 6.8.2.3 | Intel Corporation |
R2-2001230 | Introduction of PPP-RTK (SSR) | Qualcomm Incorporated |
R2-2001232 | posSIBs for NR positioning | Qualcomm Incorporated |
R2-2001243 | Summary of [108#87][NR/Rel-16] Additional path reporting | Ericsson |
R2-2001278 | Single positioning method approach in LPP | Ericsson |
R2-2001279 | Summary of [108#86][NR/Pos] Single positioning method approach in LPP | Ericsson |
R2-2001353 | Strongest first path indication with RSTD and UE RxTx measurements | Ericsson |
R2-2001659 | Summary of [108#87][NR/Rel-16] Additional path reporting | Ericsson |
R2-2001941 | LPP CR Capturing RAN1 parameters for positioning ([108#85][NR Pos]) | Intel Corporation |
R2-2001942 | Introduction of Rel-16 NR positioning | Intel Corporation |
R2-2001943 | Summary of [AT109e][617][POS] Single positioning method | Ericsson |
R2-2001944 | Summary of [AT109e][618][POS] Supported frequency/band list | Intel |
R2-2001945 | [DRAFT] LS on uplink additional path reporting | Ericsson |
R2-2001946 | Text proposal on additional path reporting | Ericsson |
R2-2001947 | Summary of [AT109e][622][POS] Uplink capability for positioning | Huawei |
R2-2001948 | [DRAFT] LS on positioning measurement range and granularity | Intel |
R2-2001950 | Summary of [AT109e][621][POS] Open issues on broadcast assistance data | CATT |
R2-2001951 | Report of [AT109e][601][POS] Harmonise posSIB numbering across CRs (Intel) | Intel Corporation |
R2-2001959 | Report of [AT109e][615][POS] Update RAN1 parameters part of 37.355 CR (Intel) | Intel Corporation |
R2-2002115 | Summary of [108#86][NR/Pos] Single positioning method approach in LPP | Ericsson |
R2-2002243 | Introduction of NR positioning | Intel Corporation |
R2-2002244 | LS on Additional path reporting with uplink timing measurements | RAN2 |
R2-2002245 | LS to RAN4 on measurement range and granularity | RAN2 |
R2-2002331 | Way forward on the AoD calculation | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000242 | Further Considerations on Broadcast Assistance Data | CATT |
R2-2000971 | Discussion on on-demand SI in connected for NR positioning | Huawei, HiSilicon |
R2-2001236 | Segmentation info in gNB | Ericsson |
R2-2001239 | Overhead in current structure | Ericsson |
R2-2001241 | Summary of [108#88][NR/Rel-16] Remaining issues on broadcast assistance data | Ericsson |
R2-2001268 | Restructuring of LPP Broadcast solution to remove overheads | Ericsson |
R2-2001269 | Restructuring of RRC Broadcast solution to remove overheads | Ericsson |
R2-2001636 | On supporting of SIB for positioning | Samsung R&D Institute UK |
R2-2002053 | Summary for Broadcast of Assistance data | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000837 | On supporting UE-based positioning | Sony |
R2-2001234 | Summary of [108#89][NR/Pos] UE-based downlink positioning assistance data | Qualcomm Incorportaed |
R2-2001240 | UE-based configuration options | Ericsson |
R2-2001244 | Remaining details for UE-based downlink positioning assistance data | Qualcomm Incorporated |
R2-2001245 | Summary of UE-based positioning Agenda Item 6.8.2.5 | Qualcomm Incorporated |
R2-2001949 | Summary of [AT109e][634][POS] Open issues on UE-based downlink positioning assistance data | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000291 | Inactive state measurement message sending for positioning | vivo |
TDoc | Title | Source |
---|---|---|
R2-2000015 | Reply LS to RAN1&4 on UE capabilities on DAPS HO (R1-1913581; contact: Intel) | RAN1 |
R2-2000037 | Reply to LS on UE capabilities on DAPS HO (R4-1915781; contact: Qualcomm) | RAN4 |
R2-2000071 | Reply LS to LS on AS key derivation for conditional handover (S3-194447; contact: Apple) | SA3 |
R2-2000329 | Major CHO issues discussed in [108#66][NR Mob] phase-2 | Ericsson |
R2-2000330 | Major CHO issues not discussed in [108#66][NR Mob] | Ericsson |
R2-2000459 | UE feature list for LTE and NR mobility | Intel Corporation |
R2-2000460 | Running CR for the introduction of NR mobility enhancement | Intel Corporation |
R2-2000461 | Report of [108#66][LTE NR Mob] Open issues for LTE and NR mobility | Intel Corporation |
R2-2000462 | RRC running CR for introduction of NR mobility enhancement [108#34] | Intel Corporation |
R2-2000463 | RRC running CR for introduction of NR mobility enhancement [108#66 P2] | Intel Corporation |
R2-2000466 | Open issues in RRC CR on NR mobility | Intel Corporation |
R2-2001092 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
R2-2001093 | UE Capability for Rel-16 LTE even further mobility enhancement | Intel Corporation |
R2-2001270 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
R2-2001271 | RRC running CR for introduction of NR mobility enhancement [108#34] | Intel Corporation |
R2-2001272 | UE Capability for Rel-16 LTE even further mobility enhancement | Intel Corporation |
R2-2001520 | Interruption Time Reduction in Release 16 | Samsung, KT, LG Uplus, Verizon Wireless, ZTE, KDDI |
R2-2001530 | RAN4 requirements on Make-Before-Break | Samsung |
R2-2001531 | Stage-2 details (38.300/37.340) for Make-Before-Break | Samsung, ZTE |
R2-2001540 | Supporting Make-Before-Break in NR | Samsung, ZTE |
R2-2001543 | Supporting Make-Before-Break in NR | Samsung, ZTE |
R2-2001730 | Summary Report: [AT109e][216][NR MOB] Discussion on MBB handover for NR Rel-16 | Samsung |
R2-2001748 | Introduction of NR mobility enhancement | Intel Corporation |
R2-2001749 | Iintroduction of NR mobility enhancement | Intel Corporation |
R2-2001767 | Introduction of NR mobility enhancement | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2000374 | RRC remaining issues for conditional handover configuration | vivo |
R2-2000375 | Discussion on CHO release | vivo |
R2-2000444 | On CHO execution triggering with two joint events | Futurewei |
R2-2000445 | Resource limitation on number of CHO candidates | Futurewei |
R2-2000464 | Remaining issues on PDCP status report for CHO | Intel Corporation |
R2-2000468 | "And" events for CHO | Intel Corporation |
R2-2000592 | Return CHO Configuration | Apple |
R2-2000653 | On the need of including CHO configuration in HO command | OPPO |
R2-2000922 | Further consideration on CHO compliance check failure | CMCC |
R2-2000923 | Combination of CHO and DAPS HO | CMCC |
R2-2001002 | On reconfigurations when CHO is prepared | Nokia, Nokia Shanghai Bell |
R2-2001257 | Conventional HO overriding a CHO command | ZTE Corporation, Sanechips |
R2-2001258 | CHO triggering configuration | ZTE Corporation, Sanechips |
R2-2001259 | Applicable CHO configuration | ZTE Corporation, Sanechips |
R2-2001384 | Discussion on configuration aspect for CHO | Huawei, HiSilicon, China Telecom |
R2-2001385 | Discussion on remaining issues for CHO | Huawei, HiSilicon |
R2-2001534 | Consideration of HO Command including CHO | LG Electronics Inc. |
R2-2001584 | Further details of CHO configuration and execution | China Telecom |
R2-2001637 | Remaining issues for CHO execution | Samsung R&D Institute UK |
R2-2001649 | Discussion on the target to configure CHO | Google Inc. |
R2-2001650 | Autonomous release of CHO | Google Inc. |
R2-2001651 | Autonomous release of conditional configuration | Google Inc. |
R2-2001654 | On the target to configure conditional handover | Google Inc. |
R2-2001728 | Report of [AT109e][212][MOB] CHO configuration and execution details (Intel) | Intel |
TDoc | Title | Source |
---|---|---|
R2-2000331 | CHO and re-establishment procedure | Ericsson |
R2-2000376 | Discussion on the CHO during failure handling | vivo |
R2-2001003 | On T312 in Conditional PSCell change or handover | Nokia, Nokia Shanghai Bell |
R2-2001105 | Avoid consecutive CHO failure | Beijing Xiaomi Software Tech |
R2-2001106 | Discussion on the use case of CHO failure recovery | Beijing Xiaomi Software Tech |
R2-2001260 | Discussion on fast RLF recovery when applying CHO and fast MCG recovery | ZTE Corporation, Sanechips |
R2-2001742 | Report from [AT109e][213][MOB] CHO failure handling | Nokia |
TDoc | Title | Source |
---|---|---|
R2-2000332 | Other aspects of CHO | Ericsson |
R2-2000377 | Discussion on simultaneous connectivity in CHO | vivo |
R2-2000855 | Measurement reporting while CHO is configured | PANASONIC R&D Center Germany |
R2-2000899 | Further Discussion on Cell Evaluation for CHO Cell Selection | CATT |
R2-2000918 | Discussion on CHO for DC scenarios | CMCC |
R2-2001004 | On serving cell’s radio link status reporting for CHO preparation | Nokia, Nokia Shanghai Bell |
R2-2001305 | Timing of Key Derivation in Conditional Handover | Futurewei |
R2-2001306 | Draft LS on the Timing of AS Key Derivation in Conditional Handover | Futurewei |
R2-2001386 | Discussion on combination of simultaneous connectivity and CHO | Huawei, HiSilicon |
R2-2001535 | T304 Running Issue When CHO Execution | LG Electronics Inc. |
R2-2001537 | Measurement ID Handling for CHO and CPC | LG Electronics Inc. |
R2-2001545 | CHO in NR-U | LG Electronics Inc. |
R2-2001553 | Discussion on CHO for DC scenarios | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2000652 | Discussion on CHO impact on T312 | OPPO |
R2-2000928 | T312 handling in NR | Sharp |
R2-2001609 | Discussion on T312 support in CHO events | Samsung |
R2-2001623 | Introduction of T312 for NR PSCell in (NG)EN-DC | Samsung |
R2-2002187 | [AT109e][214][NR MOB] Finalization of T312 for fast handover failure recovery | Samsung |
R2-2002188 | Introduction of T312 for NR PSCell in (NG)EN-DC | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2002016 | CHO failure handling | Nokia |
R2-2002040 | Summary of CHO in AI 6.9.3.1 and 6.9.3.3 | Intel |
R2-2002070 | Summary of AI 6.9.3.4 (Fast handover failure recovery) | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2000333 | Remaining open issues for conditional PSCell change | Ericsson |
R2-2000446 | Failure and validation handling on intra-SN CPC | Futurewei |
R2-2000447 | Fast Pcell RLF recovery during intra-SN CPC | Futurewei |
R2-2000554 | Remaining Issues and TP on Simultaneous CHO and CPC Configurations | InterDigital |
R2-2000560 | Failure Recovery for Conditional Pscell change | Nokia, Nokia Shanghai Bell |
R2-2000606 | Discussion on open issues in PSCell change | Apple |
R2-2000900 | Report on email discussion [108#67][NR Mob] Resolving open issues in CPAC and creating TP (CATT) | CATT |
R2-2001005 | On MN-initiated reconfigurations during conditional PSCell change | Nokia, Nokia Shanghai Bell |
R2-2001006 | On informing the MN about CPC execution | Nokia, Nokia Shanghai Bell |
R2-2001007 | On avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
R2-2001008 | Draft LS on avoiding simultaneous CHO and CPC | Nokia, Nokia Shanghai Bell |
R2-2001043 | Stage-3 CR for Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001044 | Stage-2 CR for Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001045 | Stage-3 CR for Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001103 | Remaining issues for CPC-intra-SN in NR | Potevio Company Limited |
R2-2001150 | Remaining issues on failure handling for conditional PSCell change | Qualcomm Incorporated |
R2-2001151 | Remaining issues on RRC message handling for conditional PSCell change | Qualcomm Incorporated |
R2-2001163 | Remaining issues concerning conditional change (mostly PSCell) | Samsung Telecommunications |
R2-2001387 | Discussion on leftovers for CPAC | Huawei, HiSilicon |
R2-2001388 | Discussion on failure handling for MR-DC for CHO | Huawei, HiSilicon |
R2-2001536 | Transaction ID Issue in CPC | LG Electronics Inc. |
R2-2001538 | Consideration of SCG failure with CPC | LG Electronics Inc. |
R2-2001756 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001757 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001758 | Stage-3 CR for Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2001764 | LS on avoiding simultaneous CHO and CPC | RAN2 |
R2-2002089 | Report on email discussion [108#67][NR Mob] Resolving open issues in CPAC and creating TP (CATT) | CATT |
R2-2002237 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
R2-2002248 | Introduction of Conditional PSCell Change for intra-SN without MN involvement | CATT |
TDoc | Title | Source |
---|---|---|
R2-2000901 | Summary document for conditional PSCell change for Intra-SN | CATT |
R2-2001747 | Report of [AT109e][215][NR MOB] Finalization of CPC and discussing remaining open issues | CATT |
R2-2002235 | Report of [AT109e][215][NR MOB] Finalization of CPC and discussing remaining open issues | CATT |
R2-2002236 | Terminology and other open issues for stage 3 capturing of CPC | CATT |
TDoc | Title | Source |
---|---|---|
R2-2000026 | Reply LS on Fast MCG Link Recovery using SRB3 (R3-197606; contact: ZTE) | RAN3 |
R2-2000039 | Reply LS on direct SCell activation in RRC resume message (R4-1915844; contact: ZTE) | RAN4 |
R2-2000292 | Running CR to 37.340 for CA_DC enhancements | vivo, Ericsson |
R2-2001189 | Summary of [108#48][DCCA] DCCA R2 feature list | Huawei |
R2-2001190 | TP for 38.331 on introducing UE capability for eDDCA | Huawei |
R2-2001191 | TP for 36.331 on introducing UE capability for eDCCA | Huawei |
R2-2001192 | Running CR for 38.306 on introducing UE capability for eDCCA | Huawei |
R2-2001246 | Running CR for 36.300 on CA/DC Enhancements | Ericsson |
R2-2001247 | Running CR for 38.300 for CA/DC Enhancements | Ericsson |
R2-2001248 | Running CR for 36.331 for CA/DC Enhancements | Ericsson |
R2-2001249 | Running CR for 38.331 on CA/DC Enhancements | Ericsson |
R2-2002042 | Feature summary for DC and CA enhancements: organizational aspects | Ericsson |
R2-2002132 | Open issues regarding DCCA stage 3 running CRs | Ericsson |
R2-2002287 | Running CR for 36.331 for CA/DC Enhancements | Ericsson |
R2-2002288 | Running CR for 38.331 on CA/DC Enhancements | Ericsson |
R2-2002334 | [AT109e][039][DCCA] UE capabilities (Huawei) | Huawei |
R2-2002335 | Running CR for 36.306 on introducing UE capability for eDCCA | Huawei |
R2-2002368 | Running CR to 37.340 for CA_DC enhancements | vivo, Ericsson |
R2-2002371 | CR for 36.300 on CA/DC enh | Ericsson |
R2-2002372 | CR for 38.300 for CA/DC Enhancements | Ericsson |
R2-2002373 | Running CR for 36.331 for CA/DC Enhancements | Ericsson |
R2-2002374 | Running CR for 38.331 on CA/DC Enhancements | Ericsson |
R2-2002391 | CR for 36.331 for CA&DC enh | Ericsson |
R2-2002392 | CR for 38.331 for CA&DC enh | Ericsson |
R2-2002395 | Introduction of CA/DC enhancements to 37.340 | vivo, Ericsson |
R2-2002411 | CR for 36.300 on CA/DC enh | Ericsson |
R2-2002412 | CR for 38.300 for CA/DC Enhancements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000137 | Remaining issues of power control in NR-DC | Qualcomm Incorporated |
R2-2000293 | Report of email discussion power control for NR-DC | vivo |
R2-2000294 | LS on power control for NR-DC | RAN2 |
R2-2000674 | NR DC power control | Nokia, Nokia Shanghai Bell |
R2-2000872 | Remaining issues for NR-DC power control | Ericsson |
R2-2001391 | NR-DC power control | Huawei, HiSilicon |
R2-2001759 | LS on TDD pattern exchange for NR-DC power control | RAN2 |
R2-2002109 | Report of email discussion power control for NR-DC | vivo |
R2-2002256 | Summary of power Control NR DC | vivo |
R2-2002257 | Text proposal of power control NR-DC | vivo |
TDoc | Title | Source |
---|---|---|
R2-2000252 | Remaining issues for SSB measurement configuration | CATT |
R2-2000295 | Priority for early measurement frequency | vivo |
R2-2000322 | Open issues for early measurement | OPPO |
R2-2000323 | Draft LS on early measurement configuration during 2 step resume procedure without UE context relocation | OPPO |
R2-2000675 | LTE early measurement legacy text changes | Nokia, Nokia Shanghai Bell |
R2-2000676 | On early measurements related to SCG CA | Nokia, Nokia Shanghai Bell |
R2-2000889 | Early measurement performing for SCG CA case | CATT |
R2-2001124 | Early measurement indication in NR SIB1 | ZTE Corporation, Sanechips, Ericsson, MediaTek Inc |
R2-2001162 | Remaining eDCCA issues (early measurements, fast MCG recovery) | Samsung Telecommunications |
R2-2001193 | Discussion on UE behaviour of checking MR-DC band combination when performing early measurement | Huawei, HiSilicon |
R2-2001194 | Discussion on editor’s notes in the running CR for early measurement | Huawei, HiSilicon |
R2-2001195 | Considerations on SFTD measurement in idle/inactive state | Huawei, HiSilicon |
R2-2001250 | Early measurement configuration in UE context retrieval | Ericsson, Qualcomm Incorporated, LG Electronics Inc., CATT, OPPO |
R2-2001251 | Granular reporting of early measurement results | Ericsson, MediaTek Inc., ZTE Corporation, LG Electronics Inc. |
R2-2001252 | Report on Email Discussion [108#54][DCCA] Early measurements (Ericsson) | Ericsson |
R2-2001262 | Remaining Issues on Early Measurements | ZTE Corporation, Sanechips |
R2-2001403 | Early measurement results handling upon inter-RAT cell reselection | LG Electronics |
R2-2001404 | Validity area enhancement in NR | LG Electronics |
R2-2001574 | Early measurement configuration mismatch in 2-step resume | Samsung Electronics Co., Ltd |
R2-2002043 | Feature summary for DC and CA enhancements: Early measurement reporting | Ericsson |
R2-2002131 | Summary of [AT109e][045][DCCA] Early Measurements Reporting – Phase 1 | Ericsson |
R2-2002289 | Summary of [AT109e][045][DCCA] Early Measurements Reporting – Part 2 (Ericsson) | Ericsson |
R2-2002376 | Clarification of UE requirements for early measurement performance and reporting | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000136 | Finalize NR SCell dormancy | Qualcomm Incorporated |
R2-2000296 | Remaining issue of SCell dormancy | vivo |
R2-2000314 | Email report [108#56][DCCA] Scell Dormancy Open Issues | OPPO |
R2-2000315 | Text Proposal of dormant BWP introduction-38300 | OPPO |
R2-2000316 | text proposal of dormant BWP introduction-38331 | OPPO |
R2-2000317 | text proposal of SCell Group configuration for dormancy indication-38331-Alt 1 | OPPO |
R2-2000318 | text proposal of SCell Group configuration for dormancy indication-38331-Alt2 | OPPO |
R2-2000319 | Draft LS on dormant BWP configuration and related operation | OPPO |
R2-2000320 | 38321CR introductin of dormant BWP | OPPO |
R2-2000321 | Fast Scell activation in sTAG | OPPO |
R2-2000448 | Discussion on Scell domancy | Futurewei |
R2-2000678 | BFD on Dormant Scell | Nokia, Nokia Shanghai Bell |
R2-2000679 | BFR on Dormant Scell | Nokia, Nokia Shanghai Bell |
R2-2001225 | Remaining issues for SCell dormancy | Ericsson |
R2-2001226 | Short CSI reporting for NR CA | Ericsson |
R2-2001263 | On SRS transmission on SCell in dormancy | ZTE Corporation, Sanechips |
R2-2001264 | On transmission from dormancy behavior | ZTE Corporation, Sanechips |
R2-2001265 | On UL dormant BWP | ZTE Corporation, Sanechips |
R2-2001302 | SRS transmission on dormancy SCell | LG Electronics Inc. |
R2-2001303 | Consideration on dormant uplink BWP | LG Electronics Inc. |
R2-2001344 | Discussion on some open items of SCell dormancy operation | Intel Corporation |
R2-2001389 | SCell dormancy behaviour | Huawei, HiSilicon |
R2-2001453 | Temporary RS utilization for SCell and SpCell | CATT |
R2-2001511 | Summary of fast SCell activation | OPPO |
R2-2001513 | the ASN.1 design for SCell group configuration | OPPO |
R2-2002110 | Summary of fast SCell activation | OPPO |
R2-2002156 | Proposed discussion order for dormant BWP | OPPO |
R2-2002222 | Draft LS on dormant BWP configuration and related operation | OPPO |
R2-2002223 | Introductin of dormant BWP operation | OPPO |
R2-2002224 | Email discussion[AT109e#46][DCCA] Scell Dormancy Open Issues | OPPO |
R2-2002381 | LS on dormant BWP configuration and related operation | RAN2 |
R2-2002382 | Introduction of dormant BWP operation and Async CA | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2000249 | [108#55] Report of MCG SCell and SCG configuration with RRC Resume | ZTE Corporation |
R2-2000297 | Some remaining issues on SCG resume | vivo |
R2-2000298 | Granularity of early measurement and reporting | vivo |
R2-2000551 | Draft 36.331 CR for Handling SCG Configuration in Resume | InterDigital, Ericsson, LG, OPPO |
R2-2000552 | Draft 38.331 CR for Handling SCG Configuration in Resume | InterDigital, Ericsson, LG, OPPO |
R2-2000553 | Handling the SCG Configuration in RRC Resume | InterDigital, Ericsson, LG, OPPO, KT Corp |
R2-2000588 | Optimization of RRC Resume with SCG Configuration Procedure | Apple |
R2-2000589 | RRC Resume with SCG Configuration Procedure | Apple |
R2-2001253 | Synchronization and random access to the PSCell during resume | Ericsson |
R2-2001390 | Remaining issues on SCG configuration with RRC Resume | Huawei, HiSilicon |
R2-2001607 | Remaining issue on SCG delta configuration | LG Electronics Inc. |
R2-2001610 | Remaining issue on SN notificaiton | LG Electronics Inc. |
R2-2001611 | Remaining issue on stored SCG configuration | LG Electronics Inc. |
R2-2002026 | Summary of MCG SCell and SCG Configuration with RRC Resume | ZTE Corporation |
R2-2002135 | Summary of MCG SCell and SCG Configuration with RRC Resume | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
R2-2000301 | Fast recovery failure indication | vivo |
R2-2000541 | Discussion on RRC reestablishment initiated by failure of MCG failure recovery | sharp |
R2-2000677 | Remaining details of MCG failure recovery | Nokia, Nokia Shanghai Bell |
R2-2000873 | SN change during fast MCG recovery procedure | Ericsson |
R2-2000874 | Value range for T316 | Ericsson |
R2-2001266 | Further issues on MCG fast recovery | ZTE Corporation, Sanechips |
R2-2001454 | Discussion on MCG Failure Information Report | CATT |
R2-2001618 | Remaining issue on gurard timer setup | LG Electronics Inc. |
R2-2001620 | Remaining issue on gurard timer setup | LG Electronics Inc. |
R2-2001655 | Further Correction on fast MCG link recovery | Google Inc. |
R2-2001669 | Feature summary for fast MCG recovery | Ericsson (Rapporteur) |
R2-2002039 | Discussion on MCG Failure Information Report | CATT |
R2-2002137 | Fast MCG Recovery | Ericsson |
R2-2002226 | Fast MCG recovery Phase 2 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000590 | Clarification on DRX Timers for Cross-carrier Scheduling with Different Numerologies | Apple |
TDoc | Title | Source |
---|---|---|
R2-2000109 | [108#57] Async CA (QC) - Report on Email Discussion | Qualcomm Incorporated |
R2-2000122 | [108#57] Async CA (QC) - CR to 38.331 on support of async CA | Qualcomm Incorporated |
R2-2000135 | UE capability of Rel-16 DCCA enhancement | Qualcomm Incorporated |
R2-2000177 | FDD and TDD Timing Alignment for Dual Connectivity | VODAFONE |
R2-2000691 | Further discussion on NR CA with unaligned frame boundary | MediaTek Inc. |
R2-2001350 | RAN2 impact to support enhancements for dual UL and single UL operations in EN-DC | Huawei, HiSilicon |
R2-2001392 | UE capability for eDCCA RAN1 features | Huawei, HiSilicon |
R2-2001400 | Discussion on FR2 gap timing in async CA | ZTE Corporation, Sanechips |
R2-2002079 | Feature summary for miscellaneous topics in CA&DC | Ericsson |
R2-2002082 | Feature summary for miscellaneous topics in CA&DC | Ericsson |
R2-2002230 | Summary report: [AT109e][049][DCCA] - Remaining issues of Async CA” | Qualcomm |
R2-2002231 | CR to 38.331 on FR2 gap timing under Async CA | Qualcomm |
R2-2002232 | CR to 36.331 on rel-16 TDM pattern for dual UL and single UL operations in EN-DC | Qualcomm |
R2-2002233 | CR to 38.321 on clarifications of Async CA | Qualcomm |
R2-2002325 | CR to 36.331 on rel-16 TDM pattern for dual UL and single UL operations in EN-DC | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2000017 | LS reply to RAN2 on WUS for short DRX cycle (R1-1913583; contact: CATT) | RAN1 |
R2-2000098 | LS reply on CSI/SRS reporting (R1-1913480; contact: Vivo) | RAN1 |
R2-2000364 | Running 38.304 CR on UE Power saving in NR | vivo (rapporteur) |
R2-2000365 | Report of EmailDisc-79 on open issues for RRM measurement relaxation | vivo (rapporteur) |
R2-2000366 | Draft LS to RAN4 on RRM measurement relaxation in power saving | vivo |
R2-2000411 | Running CR to 37.340 for power saving | OPPO |
R2-2000452 | UE capabilities for Rel-16 UE power saving WI | Intel Corporation |
R2-2000453 | UE capabilities for Rel-16 UE power saving WI | Intel Corporation |
R2-2000843 | Running CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2000844 | Email discussion summary on running 38.331 CR for Power Saving | MediaTek Inc. |
R2-2000888 | Introduction of UE Power Saving in NR | CATT |
R2-2001615 | Running CR for Introduction of Rel-16 NR UE power saving in TS 38.321 | Huawei |
R2-2001616 | Report of email discussion [108#78][Power Saving] 38.321 open issues | Huawei |
R2-2001617 | [Draft] LS on MAC-PHY modelling for DCP | Huawei |
R2-2001912 | Email discussion summary on running 38.331 CR for Power Saving | MediaTek Inc. |
R2-2001926 | [DRAFT] LS to RAN4 on RRM relaxation in power saving | vivo |
R2-2002100 | Report of EmailDisc-79 on open issues for RRM measurement relaxation | vivo (rapporteur) |
R2-2002192 | [Draft] LS on DCP | Huawei |
R2-2002193 | [Draft] LS on DCP | Huawei |
R2-2002194 | Running CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2002195 | Running 38.304 CR on UE Power saving in NR | vivo (rapporteur) |
R2-2002197 | [Draft] LS on DCP | Huawei |
R2-2002198 | LS to RAN4 on RRM relaxation in power saving | RAN2 |
R2-2002201 | LS on DCP | RAN2 |
R2-2002302 | Running 38.304 CR on UE Power saving in NR | vivo (rapporteur) |
R2-2002303 | Running CR to 37.340 for power saving | OPPO |
R2-2002304 | Running CR for Introduction of Rel-16 NR UE power saving in TS 38.321 | Huawei |
R2-2002369 | Introduction of UE Power Saving in NR | CATT |
R2-2002383 | RAN2#109e agreements and remaining Issues for Power Saving | CATT |
R2-2002384 | Running CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2002386 | Introduction of UE Power Saving in NR | vivo |
R2-2002387 | CR for supporting UE Power Saving in TS 37.340 | OPPO |
R2-2002388 | Introduction of Rel-16 NR UE power saving in 38.321 | Huawei, Nokia, Nokia Shanghai Bell |
R2-2002389 | CR for 38.331 for Power Savings | MediaTek Inc. |
R2-2002394 | LS to RAN4 on RRM relaxation in power saving | RAN2 |
R2-2002410 | Introduction of UE Power Saving in NR | CATT |
R2-2002414 | Introduction of UE Power Saving in NR | vivo |
TDoc | Title | Source |
---|---|---|
R2-2000253 | Contributions summary on further impacts of DCP | CATT |
R2-2000254 | New issue on CSI reporting with DCP | CATT |
R2-2000349 | Open issues DCP | Ericsson |
R2-2000367 | PDCCH-WUS not applicable for short DRX cycle | vivo |
R2-2000368 | WUS impact on CSI reporting | vivo |
R2-2000412 | Remaining issues on DCP | OPPO |
R2-2000413 | Impacts of power saivng signalling on CSI reporting | OPPO |
R2-2000450 | Open issues of DCP feature | Intel Corporation |
R2-2000584 | PDCCH-WUS Mechanism | Apple |
R2-2000599 | PDCCH-WUS and Short DRX Cycle | Apple |
R2-2000665 | Discussion on introduction of search space for the DCP | ZTE Corporation, Sanechips |
R2-2000666 | Introduction of search space for the DCP in TS38.331 | ZTE Corporation, Sanechips |
R2-2000811 | Discussion on PDCCH-WUS missing problems during handover | Xiaomi Communications |
R2-2001037 | On DRX ambiguous period | Nokia, Nokia Shanghai Bell |
R2-2001038 | On DCP monitoring and CSI/SRS transmission | Nokia, Nokia Shanghai Bell |
R2-2001040 | On short DRX cycle applicability for DCP | Nokia, Nokia Shanghai Bell |
R2-2001300 | Consideration on Short DRX cycle on DCP | LG Electronics Inc. |
R2-2001463 | Remaining issues on WUS signal for Power Saving | ZTE Corporation, Sanechips |
R2-2001482 | Wakeup signaling with DRX groups | Qualcomm Inc, Samsung |
R2-2001913 | Summary of open issues for PDCCH | CATT |
TDoc | Title | Source |
---|---|---|
R2-2000255 | Reporting UE Assistance Info to NR SN | CATT |
R2-2000350 | Open issues for UE assistance | Ericsson |
R2-2000351 | Open issues for MR-DC scenarios | Ericsson |
R2-2000369 | UE assistance information for power saving | vivo |
R2-2000451 | Open issues of new UE assistance information for PWS | Intel Corporation |
R2-2000585 | UE Power Saving in (NG)EN-DC | Apple, Samsung, Qualcomm, Huawei, HiSilicon |
R2-2000596 | UE Assistance Information for Scell | Apple |
R2-2000649 | Remaining open issues on UE assistance information | OPPO |
R2-2000826 | Power Saving UE assistance information | Sony |
R2-2000869 | Power Saving UE assistance information | Sony Europe B.V. |
R2-2001301 | Remaining issue on UE assistance | LG Electronics Inc. |
R2-2001330 | Remaining issues on UE assistance information | Huawei, HiSilicon |
R2-2001483 | Remaining issues on UE Assistancec Information | Qualcomm Inc |
R2-2001914 | Summary of open issues for UE assistance | Qualcomm |
R2-2002030 | Introduce SCG release indication in UAI for EN-DC | OPPO |
TDoc | Title | Source |
---|---|---|
R2-2000256 | Way forward on measurement relaxation with high priority frequencies | CATT |
R2-2000312 | Configurations for RRM Measurement Relaxation in NR | MediaTek Inc. |
R2-2000352 | Open issues RRM measurement relaxation | Ericsson |
R2-2000370 | UE Power Consumption Reduction in RRM Measurement | vivo |
R2-2000595 | Open Issues of RRM Measurement Relaxation | Apple |
R2-2000827 | UE power saving for inter frequency measurements | Sony |
R2-2000913 | Discussion on power saving for inter-frequency measurements | CMCC |
R2-2001039 | On RRM measurement relaxation | Nokia, Nokia Shanghai Bell |
R2-2001063 | On SrxlevRef adaptation in relaxed monitoring | Huawei, HiSilicon |
R2-2001064 | Reducing the number of neighbour cells/carriers to measure | Huawei, HiSilicon |
R2-2001401 | Coexistence issues of measurement relaxation and early measurements | LG Electronics, Ericsson, MediaTek |
R2-2001402 | Per-frequency measurement relaxation based on neighbour cell quality | LG Electronics |
R2-2001577 | RRM measurement relaxation | Samsung |
R2-2001643 | On the frequency selection for RRM relaxation | Samsung R&D Institute UK |
R2-2001915 | Summary of RRM measurement relaxation open issue | Huawei |
R2-2002034 | Impact of RRM relaxation on ETWS&CMAS | ZTE corporation, Sanechips |
R2-2002035 | Coexistance of mesurement relaxation and early measurements | ZTE corporation, Sanechips |
R2-2002199 | Summary of RRM measurement relaxation open issue | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000927 | Feature list for R16 SON MDT WI | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2000012 | Reply LS on PRACH configuration conflict detection (R1-1913578; contact: CATT) | RAN1 |
R2-2000028 | LS on information needed for MRO in UE RLF Report (R3-197668; contact: CATT) | RAN3 |
R2-2000299 | Running CR to 38.306 for NR_SON_MDT | vivo, CMCC |
R2-2000907 | Summary of open points in [108#91][NR/L2M] running 38.314 CR (CMCC) | CMCC |
R2-2000908 | Running TS 38.314 | CMCC |
R2-2000924 | Leftovers for TS 37.320 to support NR MDT | CMCC |
R2-2000925 | Running TS 37.320 CR | CMCC, Nokia |
R2-2001123 | Report of email discussion [108#93] running 38.331 CR to support RACH report | Ericsson |
R2-2001363 | Report of email discussion [108#42] | Huawei, Ericsson |
R2-2001364 | CR for introducing MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2001365 | CR on enhancements on LTE MDT and SON | Huawei, CMCC, HiSilicon |
R2-2001994 | SON/MDT agreements from email discussions | Session chair (CMCC) |
R2-2001995 | SON/MDT agreements from email discussions part2 | Session chair (CMCC) |
R2-2001997 | Running TS 37.320 CR | CMCC, Nokia, Nokia Shanghai Bell (Rapporteur) |
R2-2001998 | CR on enhancements on LTE MDT and SON | Huawei, HiSilicon, CMCC |
R2-2001999 | CR for introducing MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2002000 | TS 38.314, v0.0.5 | CMCC |
R2-2002001 | CR on enhancements on LTE MDT and SON | Huawei, CMCC, HiSilicon |
R2-2002002 | CR to Introduce NR MDT | CMCC, Nokia, Nokia Shanghai Bell (Rapporteur) |
R2-2002003 | CR for introducing MDT and SON | Huawei, Ericsson, HiSilicon |
R2-2002004 | Reply LS on Information Needed for MRO in UE RLF Report | RAN2 |
R2-2002005 | CR on enhancements on LTE MDT and SON | Huawei, CMCC, HiSilicon |
R2-2002006 | CR to Introduce NR MDT | CMCC, Nokia, Nokia Shanghai Bell (Rapporteur) |
R2-2002250 | Reply LS on QoS monitoring for URLLC (R3-201372; contact: Intel) | RAN3 |
R2-2002393 | Reply LS on Information Needed for MRO in UE RLF Report | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000001 | Remaining issues of UE Location Information | Qualcomm Incorporated |
R2-2000100 | Discussion on logged MDT | CATT |
R2-2000101 | Corrections for CEF and RLF Report | CATT |
R2-2000102 | Failure Indication about SCG | CATT |
R2-2000300 | Remaining issues on MDT | vivo |
R2-2000807 | Remaining issues on MDT | ZTE Corporation, Sanechips |
R2-2001100 | Clarification on CEF report | ZTE Corporation, Sanechips |
R2-2001111 | [DRAFT] LS on MDT configurations | Ericsson |
R2-2001114 | Measurement configuration options for immediate and logged MDT in NR | Ericsson |
R2-2001115 | Neighbor frequency coverage hole indication in logged MDT | Ericsson |
R2-2001117 | Open issues related to current logged MDT contents in running CR | Ericsson |
R2-2001143 | A2-like measurement results in Logged MDT | Nokia, Nokia Shanghai Bell |
R2-2001144 | CGI in MDT reports | Nokia, Nokia Shanghai Bell |
R2-2001145 | Location information encoding in NR MDT | Nokia, Nokia Shanghai Bell |
R2-2001146 | Principle on Rareport entry logging | Nokia, Nokia Shanghai Bell |
R2-2001366 | Enhancements on logged MDT and accessibility measurements | Huawei, HiSilicon |
R2-2001367 | Discusison on sensor measurement reporting | Huawei, HiSilicon |
R2-2001436 | Clarification on Cell ID Applied to NR MDT | Samsung |
R2-2001438 | Introducing Further Information Useful for NR MDT | Samsung |
R2-2001439 | On supporting Event-triggered Logged MDT | Samsung |
R2-2001441 | RLF Report Enhancement | Samsung |
R2-2001443 | Stage-3 Miscellaneous for NR MDT | Samsung |
R2-2001684 | Offline discussion 110: eMIMO RRC CR discussion - Second round | Ericsson |
R2-2001991 | Email discussion report: [AT109e][803][MDT] MDT open issues | Huawei (Summary rapporteur) |
R2-2002076 | Summary on MDT | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000000 | Remaining Issues of UL PDCP Packet Average Queuing Delay Measurement | Qualcomm Incorporated |
R2-2000103 | Correction and Open Issues of UL Delay Measurement | CATT |
R2-2000806 | Further consideration on INACTIVE UE counting | ZTE Corporation, Sanechips |
R2-2000909 | Summary of L2M open points and proposals | CMCC |
R2-2000910 | Clarification for per cell PRB usage | CMCC, Ericsson, Huawei |
R2-2001110 | [DRAFT] LS on throughput measurement in DC based PDCP duplication scenario | Ericsson |
R2-2001112 | Definition of number of active UEs | Ericsson, CMCC |
R2-2001113 | Handling PDCP queueing delay measurements in split bearer scenario | Ericsson |
R2-2001119 | Throughput measurement in duplication scenario | Ericsson |
R2-2001147 | Per DRB measurements in TS38.314 | Nokia, Nokia Shanghai Bell |
R2-2001368 | Discussion on per DRB and excess delay measurement for L2M | Huawei, HiSilicon |
R2-2001369 | TP on per DRB measurements for L2M | Huawei, HiSilicon |
R2-2001370 | Discussion on min and max value for delay measurements for L2M | Huawei, HiSilicon |
R2-2001371 | Discussion on UL delay measurements in non MR-DC | Huawei, HiSilicon |
R2-2001372 | Discussion on DL delay measurements | Huawei, HiSilicon |
R2-2001373 | Discussion on delay measurements for MR-DC and CA | Huawei, HiSilicon |
R2-2001419 | Clarification on PRB usage | ZTE Corporation, Sanechips |
R2-2001440 | On Mapping 5QI to DRB | Mediatek Inc |
R2-2001603 | Clarification for per cell PRB usage | CMCC, Ericsson, Huawei, ZTE |
R2-2001993 | Report for [AT109e][805][SON/MDT]L2 open issues (CMCC) | CMCC |
TDoc | Title | Source |
---|---|---|
R2-2000002 | Cross-system RLF report | Qualcomm Incorporated |
R2-2000104 | Analysis about MRO Issues Request by RAN3 | CATT |
R2-2000105 | Corrections for RACH Records Structure | CATT |
R2-2000106 | Corrections for the Content of RACH Records | CATT |
R2-2000107 | Draft Reply LS on Information Needed for MRO in UE RLF Report | CATT |
R2-2000801 | Remaining issues on RLF report | ZTE Corporation, Sanechips |
R2-2000802 | CR to 38300 on Introducing RLF report in NR | ZTE Corporation, Sanechips |
R2-2000803 | Draft Reply LS to RAN3 on RLF report | ZTE Corporation, Sanechips |
R2-2000804 | Remaining issues on RACH report procedure | ZTE Corporation, Sanechips |
R2-2000805 | Further considerations on RACH optimization | ZTE Corporation, Sanechips |
R2-2001116 | Open issues associated to RA report | Ericsson |
R2-2001118 | SCGFailureInformation message content alignment with RLFReport | Ericsson |
R2-2001148 | TP to 38.300 on SON support | Nokia, Nokia Shanghai Bell |
R2-2001374 | Discussion on remaining aspects on SON | Huawei, HiSilicon |
R2-2001444 | Inter-RAT RLF reporting for MRO | Samsung |
R2-2001446 | Remaining Aspects on UE History Information | Mediatek Inc |
R2-2001479 | Discussion on UE capability for location reporting in SCG failure | NTT DOCOMO INC. |
R2-2001992 | Email discussion report: [AT109e][804][SON/MDT]SON open issues (Ericsson) | Ericsson (email discussion rapporteur) |
R2-2001996 | Introduction of SON support | Nokia (rapporteur), Nokia Shanghai Bell |
R2-2002025 | Feature summary for SON contributions in AI 6.12.4 | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2001166 | Review of UE information in NR, alignment and harmonisation | Samsung Telecommunications |
R2-2001375 | Discussion on UE history information in RRC reestablishment | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000942 | Stage-2 running CR for 2-step RACH | Nokia (rapporteur), Nokia Shanghai Bell |
R2-2000992 | Summary of running MAC CR review issue list - phase 1 | ZTE Corporation (email discussion rapporteur) |
R2-2000993 | Summary of running MAC CR review issue list - phase 2 | ZTE Corporation (email discussion rapporteur) |
R2-2000994 | Summary of open issues in MAC running CR | ZTE Corporation (email discussion rapporteur) |
R2-2000995 | Summary of open issues in MAC running CR - Updated | ZTE Corporation (email discussion rapporteur) |
R2-2000996 | Draft-Running MAC CR for 2-step RACH | ZTE Corporation (email discussion rapporteur) |
R2-2000997 | Running MAC CR for 2-step RACH | ZTE Corporation (email discussion rapporteur) |
R2-2001217 | Draft CR 2-step RA 38.331 Running CR | Ericsson (Email disc rapporteur) |
R2-2001218 | Open issues for RRC | Ericsson (Email disc rapporteur) |
R2-2001219 | Phase 2 and phase 1 issue list | Ericsson (Email disc rapporteur) |
R2-2001927 | [DRAFT] LS on Support of CSI-RS for 2-step RACH (CFRA) | ZTE |
R2-2001928 | LS to RAN1 on NR-U PRACH root sequence for 2-step RA | RAN2 |
R2-2001929 | LS to RAN1 on Support of 2-step CFRA | RAN2 |
R2-2002031 | Running CR on 38.331 for 2-step RA | Ericsson (Email disc rapporteur) |
R2-2002032 | 2-step RA control plane summary | Ericsson (Email disc rapporteur) |
R2-2002125 | Open issues for RRC | Ericsson (Email disc rapporteur) |
R2-2002126 | [DRAFT] LS to RAN1 on NR-U PRACH root sequence for 2-step RA | Ericsson |
R2-2002138 | LS to RAN1 on NR-U PRACH root sequence for 2-step RA | RAN2 |
R2-2002202 | Running MAC CR for 2-step RACH | ZTE Corporation (email discussion rapporteur) |
R2-2002348 | Introduction of 2-step RACH | Nokia (rapporteur), Nokia Shanghai Bell |
R2-2002379 | Introduction of 2-step RACH in 38.321 | ZTE Corporation, Sanechips |
R2-2002380 | Introduction of 2-step RA | Ericsson |
R2-2002413 | Introduction of 2-step RACH in 38.321 | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2000141 | Simultaneous BWP Switching and Contention Resolution in 2-step RACH | vivo |
R2-2000142 | Resource Selection for 2-step RACH Considering Measurment Gap | vivo |
R2-2000143 | Handling of the Collision Between MsgA Grant and Another UL Grant | vivo |
R2-2000144 | Discuession on the MsgB Response Window for 2-step CFRA | vivo |
R2-2000220 | Handling PDCCH Order Initiated CFRA | Samsung Electronics Co., Ltd |
R2-2000221 | NDI Toggling Aspects | Samsung Electronics Co., Ltd |
R2-2000222 | Preamble Group Selection upon switching from 2 step CFRA to 2 step CBRA | Samsung Electronics Co., Ltd |
R2-2000223 | Preamble Group Selection upon switching from 2 step to 4 step RA | Samsung Electronics Co., Ltd |
R2-2000225 | Handling Preambles not associated with PRUs | Samsung Electronics Co., Ltd |
R2-2000388 | Preamble group selection and 2-step failure reporting | Ericsson |
R2-2000389 | Combined Back-off and 4-step switch | Ericsson |
R2-2000391 | Use of 2-step resources on different BWPs | Ericsson |
R2-2000408 | Issues on preamble group selection for 2-step RACH | OPPO |
R2-2000409 | Measurement gap impacts on MSGA transmission | OPPO |
R2-2000777 | Discussion on preamble group selection for 2step RACH initiated by HO | Fujitsu |
R2-2000812 | Views on Remaining MAC Issues for 2-Step RACH | CATT |
R2-2000831 | Differentiating between MsgB carrying RRC and other messages | Sony |
R2-2000833 | msgB-RNTI ambiguity for CFRA and CBRA of 2-Step RACH | Sony |
R2-2000852 | 2-step CBRA preamble group selection | Nokia, Nokia Shanghai Bell |
R2-2000853 | Need for ra-MsgASizeGroupA parameter | Nokia, Nokia Shanghai Bell |
R2-2000951 | Remaining issues on the msgA transmission | Huawei, HiSilicon |
R2-2000952 | Remaining issues on MsgB reception | Huawei, HiSilicon |
R2-2000953 | Draft LS to RAN1 on LSBs of SFN | Huawei, HiSilicon |
R2-2000954 | Open issues on MAC spec for 2-stepRACH | Huawei, HiSilicon |
R2-2000955 | MAC handling of MsgA with invalid PUSCH | Huawei, HiSilicon |
R2-2001017 | Remaining issues on 2-step CBRA | Qualcomm Incorporated |
R2-2001125 | Preamble grouping for 2-step RA | NEC Telecom MODUS Ltd. |
R2-2001510 | Further discussion on preamble group selection | LG Electronics |
R2-2001512 | Draft 38.321 CR on preamble group selection for 2-step RA type | LG Electronics |
R2-2001529 | Remaining issue on user plane aspects | LG Electronics |
R2-2001916 | Summary of UP open issues | ZTE |
R2-2002200 | LS to RAN1 on the starting point of MSGB window | ZTE |
R2-2002205 | LS to RAN1 on the starting point of MSGB window | ZTE |
R2-2002298 | LS to RAN1 on the starting point of MSGB window | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000224 | PUSCH Resource Configuration for CFRA | Samsung Electronics Co., Ltd |
R2-2000410 | Remaining issues on configuration of 2-step CFRA | OPPO |
R2-2000586 | Open Issues on 2-step RACH | Apple |
R2-2000650 | Views on Remaining RRC Issues for 2-Step RACH | CATT |
R2-2000778 | Discussion on RO and PO configuration for CFRA | Fujitsu |
R2-2000998 | Resource configuration for 2-step CFRA | ZTE Corporation, Sanechips |
R2-2002204 | LS to RAN1 on preamble-to-PRU mapping for 2-step CFRA | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000390 | BSR over 2-step RA | Ericsson |
R2-2000392 | Beam specific 2-step RA support | Ericsson |
R2-2000393 | MsgA transmission for NR-U | Ericsson |
R2-2000916 | Discussion on the release of the PUSCH resources | CMCC |
R2-2000917 | Remaining issues on 2-step CFRA | CMCC |
R2-2000926 | Open issues for 2-step CFRA | CMCC |
R2-2000943 | MSGB for CFRA | Nokia, Nokia Shanghai Bell |
R2-2000956 | Prioritized 2-step RACH | Huawei, HiSilicon |
R2-2001032 | Remaining issues on 2-step CFRA | Qualcomm Incorporated |
R2-2001095 | RAN2 aspect of UE capability for 2-step RACH | Intel Corporation |
R2-2001102 | Discussion on MsgB PDCCH | Potevio Company Limited |
R2-2001471 | Further discussion on 2-Step CFRA | CMCC |
R2-2001514 | Releasing CFRA resources for 2-step RA type | LG Electronics |
R2-2001515 | Draft 38.321 CR on release of CFRA resource for 2-step RA type | LG Electronics |
R2-2001518 | Draft 38.331 CR on release of CFRA resource for 2-step RA type | LG Electronics |
TDoc | Title | Source |
---|---|---|
R2-2000152 | Running CR for the introduction of SRVCC from 5G to 3G | China Unicom |
R2-2000174 | Running CR for the introduction of SRVCC from 5G to 3G | China Unicom |
R2-2000325 | Introduction of SRVCC from 5G to 3G | Ericsson, ZTE |
R2-2000326 | Running CR for introduction of SRVCC from 5G to 3G | Ericsson |
R2-2000335 | Introduction of SRVCC from 5G to 3G | Ericsson |
R2-2000542 | Introduction of SRVCC from 5G to 3G | Huawei, HiSilicon, China Unicom |
R2-2000651 | Introduction of SRVCC from 5G to 3G | China Unicom, Huawei, HiSilicon |
R2-2001692 | Introduction of SRVCC from 5G to 3G | Ericsson |
R2-2001693 | Introduction of SRVCC from 5G to 3G | Huawei, HiSilicon, China Unicom |
R2-2001701 | Introduction of SRVCC from 5G to 3G | Ericsson, ZTE, China Unicom |
R2-2002370 | Introduction of SRVCC from 5G to 3G | Ericsson, China Unicom |
TDoc | Title | Source |
---|---|---|
R2-2000441 | Introduction of Cross Link Interference (CLI) handling and Remote Interference Management (RIM) | Qualcomm Incorporated |
R2-2001411 | Introduction of cross link interference management | Huawei, HiSilicon |
R2-2001412 | Introduction of cross link interference management | Huawei, HiSilicon, ZTE Corporation (Rapporteur) |
R2-2001542 | Introduction of CLI handling and RIM in TS38.331 | LG Electronics Inc. |
R2-2001694 | Introduction of cross link interference management | Huawei, HiSilicon |
R2-2001695 | Introduction of cross link interference management | Huawei, HiSilicon, ZTE Corporation (Rapporteur) |
R2-2001696 | Introduction of CLI handling and RIM in TS38.331 | LG Electronics Inc. |
R2-2001700 | Introduction of cross link interference management | Huawei, HiSilicon |
R2-2001895 | Introduction of CLI handling and RIM in TS38.331 | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000555 | Remaining Issues of UE-CLI Reporting | Nokia, Nokia Shanghai Bell |
R2-2000556 | UE-CLI Measurements for EN-DC | Nokia, Nokia Shanghai Bell |
R2-2000557 | Draft LS to RAN3 on UE-CLI measurements for EN-DC | Nokia, Nokia Shanghai Bell |
R2-2001621 | Remaining last issues on CLI | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000095 | LS on explicit higher layer signalling on PUCCH resource grouping for simultaneous spatial relation updates (R1-1913423; contact: LGE) | RAN1 |
R2-2000096 | Reply LS on multi PDCCH-based and single PDCCH-based multi-TRP operation (R1-1913463; contact: Huawei) | RAN1 |
TDoc | Title | Source |
---|---|---|
R2-2000860 | Multiple rate matching patterns with M-TRP | Nokia, Nokia Shanghai Bell |
R2-2001036 | Discussion the MIMO RRC parameter CRS pattern list | Qualcomm Incorporated |
R2-2001104 | Proposals for [108#36][NR eMIMO] Running RRC CR (Ericsson) | Ericsson Limited |
R2-2001109 | Running RRC CR for Introduction of NR eMIMO | Ericsson |
R2-2001345 | Remaining RRC signalling aspects of NR eMIMO | Intel Corporation |
R2-2001671 | Summary of [NR eMIMO] RRC aspects | Ericsson |
R2-2001677 | Offline discussion 110: eMIMO RRC CR discussion | Ericsson |
R2-2001683 | LS on eMIMO RRC parameters | RAN2 |
R2-2001705 | Introduction of MIMO enhancements | Ericsson |
R2-2001896 | Introduction of MIMO enhancements | Ericsson |
R2-2002071 | Introduction of MIMO enhancements | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000385 | MAC CEs regarding multiple CCs/BWPs | vivo |
R2-2000659 | CC list-based SRS Activation MAC CE | OPPO |
R2-2000660 | Report of [108#68][NR eMIMO] Design of DL MAC CEs | OPPO |
R2-2000766 | Enhancement of multiple PDCCH-based TRP transmission | Samsung |
R2-2000890 | Views on eMIMO MAC CEs | CATT |
R2-2001034 | Design of MIMO DL MAC CE | Qualcomm Incorporated |
R2-2001126 | Remaining update for PDSCH TCI state MAC CE | Ericsson |
R2-2001128 | New MAC CE for indicating spatial resource for PUCCH resources | Ericsson |
R2-2001196 | MAC CE signalling for multi-beam enhancement | Huawei, HiSilicon |
R2-2001465 | Considerations on TCI state MAC CE for mPDCCH mTRP transmission | ZTE Corporation, Sanechips |
R2-2001551 | Summary of DL MAC CE design for aganda 6.16.3 | OPPO |
R2-2001686 | [AT109e][121][EMIMO] DL MAC CE design (Oppo) | OPPO |
R2-2001917 | Summary of CP open issues | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000226 | Remaining issues of SCell BFR | Samsung Electronics Co., Ltd |
R2-2000227 | Summary of Email discussion 108#70 - BFR MAC CE | Samsung Electronics Co., Ltd |
R2-2000386 | SR cancellation due to the truncated BFR MAC CE | vivo |
R2-2000587 | SCell BFR Operation | Apple, Nokia, Nokia Shanghai Bell |
R2-2000658 | Open issues on SCell BFR | OPPO |
R2-2000767 | MAC running CR for NR eMIMO | Samsung |
R2-2000891 | Views on Remaining Issues of SCell BFR | CATT |
R2-2001304 | Consideration on Truncated format on SCell BFR MAC CE | LG Electronics Inc. |
R2-2001421 | Remaining issues on SCell BFR procedure | Asia Pacific Telecom co. Ltd |
R2-2001464 | The remaining issue on BFR on SpCell and SCell | ZTE Corporation, Sanechips, Asia Pacific Telecom co. Ltd |
R2-2001484 | Remaining issues on SCell BFR | Qualcomm Inc |
R2-2001509 | The remaining issue on BFR on SpCell and SCell | ZTE Corporation, Sanechips, Asia Pacific Telecom co. Ltd |
R2-2001599 | Remaining issues of SCell BFR | ASUSTeK |
R2-2001600 | SCell BFR regarding Scell deactivation | ASUSTeK |
R2-2001652 | BFR MAC CE for SpCell | Ericsson, Nokia, Nokia Shanghai Bell, Apple |
R2-2001672 | Summary of [NR eMIMO] Beam management enhancements | Samsung |
R2-2001678 | Offline discussion 112: Beam management enhancements | Samsung |
R2-2001685 | Offline discussion 112: Beam management enhancements | Samsung |
R2-2001706 | MAC running CR for NR eMIMO | Samsung |
R2-2001897 | Introduction of eMIMO for NR | Samsung |
TDoc | Title | Source |
---|---|---|
R2-2000025 | Reply LS on Sending CAG ID in NAS layer (R3-197591; contact: Ericsson) | RAN3 |
R2-2000051 | Reply LS on NPN clarifications (S1-193605; contact: Qualcomm) | SA1 |
R2-2000055 | LS on RAN sharing for NPNs (S2-1912602; contact: Qualcomm) | SA2 |
R2-2000057 | Reply LS on sending CAG ID during resume procedure (S2-1912731; contact: Qualcomm) | SA2 |
R2-2000065 | LS reply on NPN network sharing (S2-2001398; contact: Huawei) | SA2 |
R2-2000066 | Reply LS on CMAS/ETWS and emergency services for SNPNs (S2-2001400; contact: Qualcomm) | SA2 |
R2-2000067 | LS reply on CAG definition (S2-2001401; contact: Huawei) | SA2 |
R2-2000069 | LS on Sending CAG ID (S2-2001616; contact: Ericsson) | SA2 |
R2-2000074 | Reply LS on Sending CAG ID in NAS layer (S3-194559; contact: Qualcomm) | SA3 |
R2-2000078 | LS on NPN network sharing (S5-197805; contact: Huawei) | SA5 |
R2-2000079 | LS on CAG definition (S5-197806; contact: Huawei) | SA5 |
R2-2000568 | NPN Work Plan | Nokia (Rapporteur) |
R2-2000569 | Non-Public Networks | Nokia, China Telecom (Rapporteurs) |
R2-2000570 | Emergency Calls in CAG-Only Cells | Nokia (Rapporteur), China Telecom, Ericsson, Intel, Nokia Shanghai Bell, Vodafone, ZTE |
R2-2001331 | Open issues in NPN | Qualcomm Incorporated |
R2-2001679 | [DRAFT] Reply LS on CAG definition | Huawei |
R2-2001703 | Reply LS on CAG definition | RAN2 |
R2-2002068 | Non-Public Networks | Nokia, China Telecom (Rapporteurs) |
R2-2002069 | [DRAFT] Reply LS on CAG definition | Huawei |
R2-2002096 | Reply LS on manual CAG selection (S1-201084; contact: Qualcomm) | SA1 |
R2-2002213 | Reply LS on sending CAG ID (C1-201027; contact: Ericsson) | CT1 |
R2-2002346 | Non-Public Networks | Nokia, China Telecom (Rapporteurs) |
TDoc | Title | Source |
---|---|---|
R2-2000003 | Access Control about NPN | CATT |
R2-2000004 | Idle and Inactive Open Issues for NPN | CATT |
R2-2000132 | Support of emergency calls in NPN-only cells | Ericsson |
R2-2000357 | Remaining issues on the cell reselection | ZTE Corporation, Sanechips |
R2-2000399 | Support for Non-Public Networks | Nokia (Rapporteur) |
R2-2000400 | Proposals on Editor’s Notes of running RRC CR | Nokia, Nokia Shanghai Bell |
R2-2000402 | Handling of selected CAG ID in Idle/Inactive mode | Nokia, Nokia Shanghai Bell |
R2-2000829 | Blacklist/whitelist for PCI range signaling and stage-3 details | Sony |
R2-2001035 | Introducing the support of Non-Public Networks | Nokia (Rapporteur) |
R2-2001170 | Remaining mobility issues for idle mode and connected mode | Intel Corporation |
R2-2001174 | Open issues in the specification of NPN in TS 38.304 | Lenovo, Motorola Mobility |
R2-2001310 | PRN Running CR for TS 38.304 | Qualcomm Incorporated |
R2-2001311 | Report for email discussion [108#71][PRN] Running 38.304 CR (Qualcomm) | Qualcomm Incorporated |
R2-2001376 | General considerations on idle and inactive mode for NPN | Huawei, HiSilicon |
R2-2001423 | Signalling Design on the PCI Range | CMCC |
R2-2001424 | TP on NPN Running RRC for PCI list of PRN Cells | CMCC |
R2-2001526 | Resolving miscellaneous issues | LG Electronics France |
R2-2001527 | High Quality Criterion for SNPN | LG Electronics France |
R2-2001528 | Manual CAG selection | LG Electronics France |
R2-2001673 | Summary of [PRN] Cell Selection and selection | Qualcomm |
R2-2001676 | Summary of [PRN] Cell Selection and selection | Qualcomm |
R2-2001680 | Summary of [PRN] Cell Selection and selection | Qualcomm |
R2-2001697 | Summary of [PRN] Cell Selection and selection | Qualcomm |
R2-2001707 | Introducing the support of Non-Public Networks | Nokia (Rapporteur) |
R2-2001708 | PRN Running CR for TS 38.304 | Qualcomm Incorporated |
R2-2001898 | Introduction of PRN for TS 38.304 | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000005 | Connected Mode Open Issues for NPN | CATT |
R2-2000358 | Consideration on the remaining Connected State Issues | ZTE Corporation, Sanechips |
R2-2000401 | Proposals on open RRC issues | Nokia, Nokia Shanghai Bell |
R2-2001071 | Discussion on the proximity indication in connected mode | vivo |
R2-2001377 | General considerations on connected mode for NPN | Huawei, HiSilicon, China Telecom |
R2-2001430 | Access and mobility control for NPN | CMCC |
R2-2001572 | Transfer of NPN ID in RRC connection establishment | Samsung Electronics Co., Ltd |
R2-2001573 | Discussion on ANR for NPN | Samsung Electronics Co., Ltd |
R2-2001586 | Remaining issues discussion on NPN | China Telecom |
R2-2001674 | Summary of [PRN] Connected mode aspects | Nokia |
R2-2001681 | Report from email discussion [118][PRN] Connected mode aspects | Nokia (summary rapporteur) |
R2-2001698 | offline discussion 118: [PRN] Connected mode aspects - Final status | Nokia |
R2-2001704 | LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | RAN2 |
R2-2002416 | LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | RAN2 |
R2-2002417 | LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000130 | Remaining RRC aspects of NPN | Ericsson |
R2-2000131 | Remaining RRC aspects of NPN | Ericsson |
R2-2000668 | Consideration on the HRNN and Access control | ZTE Corporation, Sanechips, Qualcomm Inc |
R2-2001072 | Consideration on fixed MCC for SNPN | vivo |
R2-2001155 | UE-initiated change of NPN UE configuration | Lenovo, Motorola Mobility |
R2-2001169 | Network indexing for UAC and Connection Control | Intel Corporation |
R2-2001378 | Considerations on SI Validity Checking | Huawei, HiSilicon |
R2-2001585 | Discussion on human-readable network name | China Telecom, Huawei, HiSilicon |
R2-2001587 | Discussion on the deployment for CAG | China Telecom, Huawei, HiSilicon |
R2-2001675 | Summary of [PRN] Other (HRNN, Access Control, etc) | ZTE Corporation |
R2-2001682 | Report of offline [119 [PRN] HRNN and Access Control aspects (ZTE) | ZTE Corporation, Sanechips |
R2-2001699 | offline discussion 119: [PRN] HRNN and Access Control aspects - Intermediate status | ZTECorporation |
TDoc | Title | Source |
---|---|---|
R2-2000019 | Reply LS on Tx switching between two uplink carriers (R1-1913585; contact: China Telecom) | RAN1 |
R2-2000029 | Reply LS on LS on dependencies on AS design for mobility management aspects of NTN in 5GS / LS on system level design assumptions for satellite in 5GS (R3-197699; contact: Qualcomm) | RAN3 |
R2-2000030 | Reply LS on energy efficiency (R3-197745; contact: Orange) | RAN3 |
R2-2000040 | LS on the UE capability and network assistance signalling for Rel-16 NR HST RRM (R4-1915855; contact: China Mobile) | RAN4 |
R2-2000043 | LS on UE capabilities and RRC signalling on Tx switching period delay (R4-1916083; contact: Apple) | RAN4 |
R2-2000046 | LS on MPE enhancements (R4-1916183; contact: Qualcomm) | RAN4 |
R2-2000047 | LS on Local NR positioning in NG-RAN (RP-193262; contact: Nokia) | RAN |
R2-2000054 | LS OUT on Location of UEs and associated key issues (S2-1912560; contact: Thales) | SA2 |
R2-2000059 | LS on the support for ECN in 5GS (S2-1912765; contact: Qualcomm) | SA2 |
R2-2000076 | LS on Reply on QoE Measurement Collection (S5-197543; contact: Ericsson) | SA5 |
R2-2000077 | Reply on radio resource management policy (S5-197637; contact: Ericsson) | SA5 |
R2-2000080 | LS on analysis of GSMA GST attributes (S5-197853; contact: China Mobile) | SA5 |
R2-2000090 | Reply on QoE Measurement Collection (S4-200241; contact: Ericsson) | SA4 |
R2-2000091 | Reply LS on Support for ECN in 5GS (S4-200298; contact: Qualcomm) | SA4 |
R2-2000099 | LS to RAN3 for TPs endorsed in RAN1 (R1-1913506; contact: Thales) | RAN1 |
R2-2000178 | L2 aspects of MPE mitigation | InterDigital |
R2-2000218 | CR to 36.331 on introducing autonomous gap in Rel-16 | ZTE Corporation,Sanechips,CATT,OPPO |
R2-2000219 | CR to 36.306 on introducing autonomous gap in Rel-16 | ZTE Corporation,Sanechips,CATT,OPPO |
R2-2000438 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2000439 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2000440 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2000573 | Temporary Boost | Nokia, Nokia Shanghai Bell |
R2-2000574 | LS on Temporary Boost | Nokia |
R2-2000846 | draft response to SA2 LS on Location of UEs and associated key issues | THALES |
R2-2000861 | Introduction of UL Tx switching for UL MIMO in FR1 | Nokia, Nokia Shanghai Bell |
R2-2000862 | RRC signalling for Tx switching for UL MIMO | Nokia, Nokia Shanghai Bell |
R2-2000863 | UE capabilities for Tx switching for UL MIMO | Nokia, Nokia Shanghai Bell |
R2-2000864 | Support of UL sharing for variable-duplex FDD bands | Nokia, Nokia Shanghai Bell |
R2-2000870 | RRC signalling for Tx switching for UL MIMO | Nokia, Nokia Shanghai Bell |
R2-2000871 | UE capabilities for Tx switching for UL MIMO | Nokia, Nokia Shanghai Bell |
R2-2000919 | Discussion on signalling for R16 NR HST | CMCC |
R2-2000920 | 38.331 CR on introduction of RRC parameters and UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon |
R2-2000921 | 38.306 CR on introduction of UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon |
R2-2001088 | On the introduction of P-bit into the single entry PHR MAC CE | Apple |
R2-2001089 | Initial view on introduction of the MPE related enhancements | Apple |
R2-2001580 | Discussion on support of UL Tx swithing | ChinaTelecom, CMCC, ChinaUnicom, Orange, Huawei, HiSilicon, ZTE, CATT, Vivo |
R2-2001581 | 38306CR UE capability of supporting UL Tx switching | ChinaTelecom,Huawei,HiSilicon,CMCC,ZTE, ChinaUnicom |
R2-2001582 | 38331CR UE capability and RRC configuration of supporting UL Tx switching | ChinaTelecom,Huawei,HiSilicon,CMCC,ZTE, ChinaUnicom |
R2-2001656 | LS on the UE capability and network assistance signalling for Rel-16 NR HST demodulation (R4-1915916; contact: CMCC) | RAN4 |
R2-2002060 | RRC signalling for Tx switching for UL MIMO | Nokia, Nokia Shanghai Bell |
R2-2002084 | Discussion on signalling for R16 NR HST | CMCC, CATT |
R2-2002085 | 38.331 CR on introduction of RRC parameters and UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT |
R2-2002086 | 38.306 CR on introduction of UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT |
R2-2002124 | LS on FDD band capability signalling for uplink sharing (R4-1916180; contact: Nokia) | RAN4 |
R2-2002176 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002177 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002178 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002179 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002180 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002181 | Recommended Bit Rate/Query for FLUS and MTSI | Qualcomm Incorporated |
R2-2002214 | LS on suspend indication to the NAS (C1-201040; contact: Samsung) | CT1 |
R2-2002262 | Report of [AT109e][050][R16 Other WISI] NR HST | CMCC (rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000014 | LS on NR Rel-16 TEI (R1-1913580; contact: NTT Docomo) | RAN1 |
R2-2000050 | Reply LS on enhanced access control for IMS signalling (S1-193595; contact: NTT Docomo) | SA1 |
R2-2000108 | LTE / NR Spectrum sharing in Band 40/n40 for LTE-NR | Reliance Jio |
TDoc | Title | Source |
---|---|---|
R2-2000139 | CR to 38.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated |
R2-2000238 | Introduction of B1C signal in BDS system in A-GNSS | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc |
R2-2000239 | Introduction of B1C signal in BDS system in A-GNSS | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc |
R2-2000240 | Introduction of B1C signal in BDS system in A-GNSS | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc |
R2-2000244 | CR to 36.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated |
R2-2000324 | additional SSB-ToMeasure for smtc2-LP | OPPO, ZTE |
R2-2001041 | On combined RRC procedures | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2001042 | RRC processing delays for combined procedures | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2001120 | On inter-frequencyand inter-RAT measurement priority handling | Ericsson |
R2-2001121 | On inter-frequencyand inter-RAT measurement priority handling | Ericsson |
R2-2001122 | Measurement priority handling in NR | Ericsson |
R2-2001130 | Introduction of UE capability indicator of supporting inter-RAT handover from NR to EN-DC in 36.306. | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm |
R2-2001131 | Support of inter-RAT handover from NR to EN-DC in TS 36.331 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm |
R2-2001132 | Support of inter-RAT handover from NR to EN-DC in TS 38.331 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm |
R2-2001133 | Introduction of UE capability indicator of supporting inter-RAT handover from NR to EN-DC in 38.306 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm |
R2-2001238 | Transfer of unicast RS observations with GNSS integer ambiguity level information | Ericsson |
R2-2001256 | Introducing support for GNSS Integer Ambiguity Level Indications | Ericsson |
R2-2001292 | Allow fallback band combinations when reporting SRS-TxSwitch capability | Qualcomm Incorporated |
R2-2001293 | Discussion of the PUCCH & SRS Resource Release | Qualcomm Incorporated |
R2-2001325 | 36.331 CR for addressing overheating issue in (NG)EN-DC (comeback from RAN2#108) | Huawei, Huawei Device, Apple, CATT |
R2-2001326 | 38.331 CR for addressing overheating issue in (NG)EN-DC (comeback from RAN2#108) | Huawei, Huawei Device, Apple, CATT |
R2-2001327 | On the enhancement of SRS carrier switching capability | Huawei, HiSilicon |
R2-2001328 | On the over-cold issue | Huawei, HiSilicon |
R2-2001894 | Introducing support for GNSS Integer Ambiguity Level Indications | Ericsson |
R2-2002077 | Stage 2 CR for Inter-RAT HO between NR to EN-DC in Rel-16 | China Telecom, NTT DOCOMO, Huawei, Ericsson, ZTE, OPPO, Mediatek, VIVO, CATT |
R2-2002121 | Introduction of B1C signal in BDS system in A-GNSS | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc |
R2-2002336 | Support of inter-RAT handover from NR to EN-DC in TS 36.331 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm, NTT DOCOMO, Ericsson |
R2-2002337 | Support of inter-RAT handover from NR to EN-DC in TS 38.331 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm, NTT DOCOMO, Ericsson |
R2-2002338 | Introduction of UE capability indicator of supporting inter-RAT handover from NR to EN-DC in 38.306 | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm, NTT DOCOMO, Ericsson |
R2-2002339 | Introduction of UE capability indicator of supporting inter-RAT handover from NR to EN-DC in 36.306. | China Telecom, Huawei, ZTE, CATT, VIVO, Qualcomm, NTT DOCOMO, Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000155 | Inclusion of 90MHz UE Bandwidth | VODAFONE |
R2-2000302 | Introduction of a second SMTC per frequency carrier in idle/inactive | Orange, AT&T, Vodafone, Telecom Italia S.p.A., CMCC, NTT Docomo Inc., Samsung, Ericsson |
R2-2000303 | Introduction of a second SMTC for inter-RAT cell reselection | Orange, AT&T, Vodafone, Telecom Italia S.p.A., CMCC, NTT Docomo Inc., Samsung, Ericsson |
R2-2000580 | Introduction of voice fallback indication | Qualcomm Incorporated, T-Mobile USA, Verizon, China Telecom, Softbank, Ericsson |
R2-2000581 | Introduction of voice fallback indication | Qualcomm Incorporated, T-Mobile USA, Verizon, China Telecom, Softbank, Ericsson |
R2-2000687 | Correction on usage of access category 2 for UAC for RNA update | MediaTek Inc. |
R2-2001383 | Support of releasing UL configuration | Huawei, HiSilicon, CMCC, China Telecom, MediaTek Inc., Vodafone, Orange, vivo, OPPO, Spreadtrum Communications, China Unicom |
R2-2002102 | PRACH prioritization parameters for MPS and MCS | Perspecta Labs, ECD, AT&T, FirstNet, T-Mobile, Sprint, Verizon, Qualcomm, Ericsson |
R2-2002103 | PRACH prioritization procedure for MPS and MCS | Perspecta Labs, ECD, AT&T, FirstNet, T-Mobile, Sprint, Verizon, Qualcomm, Ericsson |
R2-2002104 | NAS handling error of nas-Container for security key derivation | Intel |
R2-2002105 | NAS handling error of nas-Container for security key derivation | Intel |
R2-2002106 | CR on capability of maxUplinkDutyCycle for inter-band EN-DC PC2 UE | CMCC |
R2-2002107 | CR on capability of maxUplinkDutyCycle for inter-band EN-DC PC2 UE | CMCC |
R2-2002130 | CR on capability of maxUplinkDutyCycle for inter-band EN-DC PC2 UE | CMCC |
R2-2002133 | Inclusion of 90MHz UE Bandwidth | VODAFONE, Sprint, Ericsson |
R2-2002326 | Introduction of voice fallback indication | Qualcomm Incorporated, T-Mobile USA, Verizon, China Telecom, Softbank, Ericsson, Sharp |
TDoc | Title | Source |
---|---|---|
R2-2000048 | LS on 5G indicator (RP-193265; contact: Intel) | RAN |
R2-2000133 | Introduction of enhanced support for dynamic spectrum sharing | Ericsson |
R2-2000134 | Introduction of enhanced support for dynamic spectrum sharing | Ericsson |
R2-2000156 | Completing the Solution for the 5G Indicator | VODAFONE |
R2-2000168 | Autonomous gap support for CGI reading | vivo, CMCC, Ericsson |
R2-2000169 | Autonomous gap support for CGI reading | vivo, CMCC, NTT DOCOMO, CATT, Ericsson, Huawei, HiSilicon, Intel, Mediatek, Nokia, Qualcomm incorporated, ZTE Corporation, Sanechips |
R2-2000170 | Autonomous gap support for CGI reading | vivo, CMCC, Ericsson |
R2-2000171 | Autonomous gap support for CGI reading | vivo, CMCC, NTT DOCOMO, CATT, Ericsson, Huawei, HiSilicon, Intel, MediaTek, Nokia, Qualcomm incorporated, ZTE Corporation, Sanechips |
R2-2000216 | Introducing autonomous gap in CGI reporting | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2000217 | CR to 38.306 on introducing autonomous gap in Rel-16 | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2000362 | Introduction of NR IDC solution | vivo, Nokia, Nokia Shanghai Bell, Spreadtrum, ZTE Corporation, Sanechips, Huawei, HiSilicon, Fujitsu, NTT DOCOMO INC., NEC, Xiaomi Communications, Qualcomm Inc, CATT, InterDigital, China Telecom, Ericsson |
R2-2000363 | UE capability for IDC | vivo, Nokia, Nokia Shanghai Bell, Spreadtrum, ZTE Corporation, Sanechips, Huawei, HiSilicon, Fujitsu, NTT DOCOMO INC., NEC, Xiaomi Communications, Qualcomm Inc, CATT, InterDigital, China Telecom, Ericsson |
R2-2000434 | LS on CGI reading with autonomous gaps (R4-1914782; contact: ZTE) | RAN4 |
R2-2000575 | Introduction of NR IDC Solution | Nokia, CATT, Ericsson, Huawei, InterDigital, NEC, NTT DOCOMO INC., Nokia Shanghai Bell, Qualcomm, vivo, ZTE |
R2-2000582 | Introdution of EPS voice fallback enhancement | Qualcomm Incorporated |
R2-2000716 | Report of [108#58][TEI16] NeedForGap Signaling (MTK) | MediaTek Inc. |
R2-2000717 | Introduction of NeedForGap capability for NR measurement - 36.331 | MediaTek Inc. |
R2-2000718 | Introduction of NeedForGap capability for NR measurement - 36.306 | MediaTek Inc. |
R2-2000719 | Introduction of NeedForGap capability for NR measurement - 38.300 | MediaTek Inc. |
R2-2000720 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
R2-2000721 | Introduction of NeedForGap capability for NR measurement - 38.306 | MediaTek Inc. |
R2-2000865 | Introduction of multiple LTE CRS rate matching patterns | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2000866 | Introduction of multiple LTE CRS rate matching patterns | Nokia, Nokia Shanghai Bell, Ericsson |
R2-2000914 | CR on alternative cell reselection priorities in 38.304 | CMCC, Ericsson |
R2-2000915 | CR on alternative cell reselection priorities in 38.331 | CMCC, Ericsson |
R2-2000931 | Introduction of DL RRC segmentation | Ericsson |
R2-2000932 | Introduction of DL RRC segmentation | Ericsson |
R2-2000933 | Introduction of DL RRC segmentation | Ericsson |
R2-2000934 | Introduction of DL RRC segmentation | Ericsson |
R2-2000935 | Introduction of DL RRC segmentation | Ericsson |
R2-2000936 | Introduction of DL RRC segmentation | Ericsson |
R2-2001009 | Missing reportAddNeighMeas in periodic measurement reporting | Nokia, Nokia Shanghai Bell |
R2-2001199 | Introduction of bandlist for ENDC for 5G indicator | HUAWEI, British Telecom, HiSilicon |
R2-2001380 | Report of [108#60][TEI16] DRX coordination | Huawei, HiSilicon |
R2-2001381 | CR to 38.331 on DRX coordination | Huawei, HiSilicon |
R2-2001433 | Supporting WUS in multiple DRX groups | Samsung |
R2-2001445 | Discussion on FFS issue in NR SA NeedForGap Signalling | Nokia,Nokia Shanghai Bell |
R2-2001448 | Discussion on support of inter-RAT HO from SA to EN-DC | Nokia, Nokia Shanghai Bell |
R2-2001480 | LS on NeedForGap capability | MediaTek Inc. |
R2-2001575 | Further discussion on EN-DC cell reselection | Samsung Electronics Co., Ltd |
R2-2001576 | Support of 5G indicator in EN-DC | Samsung Electronics Co., Ltd |
R2-2001638 | CR to 38.306 on introducing autonomous gap in Rel-16 | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2001648 | Introduction of NeedForGap capability for NR measurement - 36.331 | MediaTek Inc. |
R2-2002037 | CR on alternative cell reselection priorities in 36.304 | CMCC, Ericsson, SoftBank |
R2-2002038 | CR on alternative cell reselection priorities in 36.331 | CMCC, Ericsson, SoftBank |
R2-2002098 | Introduction of bandlist for ENDC for 5G indicator | HUAWEI, British Telecom, HiSilicon |
R2-2002108 | Introduction of NeedForGap capability for NR measurement - 36.331 | MediaTek Inc. |
R2-2002144 | Autonomous gap support for CGI reading | vivo, CMCC, NTT DOCOMO, CATT, Ericsson, Huawei, HiSilicon, Intel, Mediatek, Nokia, Qualcomm incorporated, ZTE Corporation, Sanechips |
R2-2002145 | Autonomous gap support for CGI reading | vivo, CMCC, NTT DOCOMO, CATT, Ericsson, Huawei, HiSilicon, Intel, MediaTek, Qualcomm incorporated, ZTE Corporation, Sanechips |
R2-2002146 | Introducing autonomous gap in CGI reporting | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2002147 | Introducing autonomous gap in CGI reporting | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2002158 | Introduction of DL RRC segmentation | Ericsson, Deutsche Telekom, Vodafone, AT&T, Apple, Qualcomm Incorporated, OPPO, KT, Turkcell, Verizon |
R2-2002159 | Introduction of DL RRC segmentation | Ericsson, Deutsche Telekom, Vodafone, AT&T, Apple, Qualcomm Incorporated, OPPO, KT, Turkcell, Verizon |
R2-2002160 | Introduction of DL RRC segmentation | Ericsson, Deutsche Telekom, Vodafone, AT&T, Apple, Qualcomm Incorporated, OPPO, KT, Turkcell, Verizon |
R2-2002161 | Introduction of DL RRC segmentation | Ericsson, Deutsche Telekom, Vodafone, AT&T, Apple, Qualcomm Incorporated, OPPO, KT, Turkcell, Verizon |
R2-2002175 | Introduction of NR IDC solution | vivo, Nokia, Nokia Shanghai Bell, Spreadtrum, ZTE Corporation, Sanechips, Huawei, HiSilicon, Fujitsu, NTT DOCOMO INC., NEC, Xiaomi Communications, Qualcomm Inc, CATT, InterDigital, China Telecom, Ericsson, Samsung |
R2-2002219 | Reply LS on CGI reading with autonomous gaps | RAN2 |
R2-2002255 | Autonomous gap support for CGI reading | vivo, CMCC, NTT DOCOMO, CATT, Ericsson, Huawei, HiSilicon, Intel, Mediatek, Nokia, Qualcomm incorporated, ZTE Corporation, Sanechips |
R2-2002278 | Introducing autonomous gap in CGI reporting | ZTE Coporation, Sanechips, CATT, OPPO, CMCC, MediaTek Inc, Vivo, Ericsson, Qualcomm Incorporated, Intel, Nokia, Huawei, HiSilicon, China Telecom, China Unicom, NTT DOCOMO |
R2-2002308 | Report of [AT109e][080][TEI16] NeedForGap capability (MTK) | MediaTek |
R2-2002309 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
R2-2002327 | Introdution of EPS voice fallback enhancement | Qualcomm Incorporated |
R2-2002340 | Summary of offline discussion [AT109e][075][TEI16] | China Telecom |
TDoc | Title | Source |
---|---|---|
R2-2000230 | SRB only connection enhancement for PDU session change | CATT,Huawei, HiSilicon |
R2-2000231 | SRB only connection ehancement option 1 | CATT,Huawei, HiSilicon |
R2-2000232 | SRB only connection ehancement option 2 | CATT |
R2-2000598 | 0-PDCCH RRC Connections for Certain Application Types | Apple |
R2-2000604 | Maximum Data Rate Enumeration for UP Integrity Protection | Apple, ZTE Corporation, Sanechips |
R2-2000605 | Draft LS on Maximum Data Rate Enumeration for UP Integrity Protection | Apple |
R2-2000686 | Mobility state related information inheritance after inter-RAT cell reselection | Huawei, HiSilicon, China Unicom |
R2-2000768 | Additional UE capability filtering to limit the total number of carriers in NR | Samsung |
R2-2000906 | Discussion on the flexible configuration of Maximum Data Rate Enumeration for UP Integrity Protection | CMCC, Huawei, Hisilicon |
R2-2001188 | On the support of NG-based (i.e. via CN) handover based using CGI report | Huawei, HiSilicon |
R2-2001447 | Signaling of delta configuration for SCG in NR SA to EN-DC inter-system handover | Qualcomm Incorporated |
R2-2002136 | Mandatory User Plane Integrity for 5G (FSAG Doc 79_002; contact: DT) | GSMA |
TDoc | Title | Source |
---|---|---|
R2-2001355 | Stopping ra-ResponseWindow for contention-free BFR | Huawei, HiSilicon, China Unicom |
TDoc | Title | Source |
---|---|---|
R2-2000974 | Correction on autonomous RACH retransmission for SRS switching | Huawei, HiSilicon |
R2-2001467 | Correction on autonomous RACH retransmission for SRS switching | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000345 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, Deutsche Telekom, Verizon |
R2-2000346 | Introduction of secondary DRX group CR 38.306 | Ericsson, Qualcomm, Samsung, Deutsche Telekom, Verizon |
R2-2000347 | Introduction of secondary DRX group CR 38.321 | Ericsson, Qualcomm, Samsung, Deutsche Telekom, Verizon |
R2-2000348 | Introduction of secondary DRX group CR 38.331 | Ericsson, Qualcomm, Samsung, Deutsche Telekom, Verizon |
R2-2000407 | Further considerations on secondary DRX group | OPPO |
R2-2000576 | LCP Mapping Restrictions | Nokia, Ericsson, Fujitsu, Nokia Shanghai Bell |
R2-2000577 | Dynamic LCP Mapping Restrictions | Nokia, Nokia Shanghai Bell |
R2-2000779 | SR_COUNTER initialization due to RRC reconfiguration | Fujitsu |
R2-2000854 | CFRA resource handling for BFR upon TAT expiry | Nokia, Nokia Shanghai Bell, Apple, ASUSTek |
R2-2001015 | Updates to reestablishment procedure | ZTE Corporation, Sanechips, Intel Corporation, CATT |
R2-2001500 | Extension of the LCID | LG Electronics Inc. |
R2-2001644 | SR_COUNTER initialization due to RRC reconfiguration | Fujitsu, LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000120 | MAC upgrade for SR dropping in PHY | CATT, Qualcomm Inc. |
R2-2000121 | Correction on the drx-HARQ-RTT-TimerDL | CATT |
R2-2000406 | Cell restriction for CA duplication | OPPO |
R2-2000578 | QoS Flow Handling | Nokia, Nokia Shanghai Bell |
R2-2000579 | MDBV Enforcement | Nokia, InterDigital, Nokia Shanghai Bell |
R2-2000594 | Preamble Selection for RACH Procedure | Apple |
R2-2000723 | PDCP security issue about duplicate detection | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, LG Uplus |
R2-2000724 | CR on PDCP security issue | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, LG Uplus |
R2-2000725 | Unnecessary deciphering for duplicated PDUs | Samsung |
R2-2000758 | Enhancement on BSR format for the one LCG case | Huawei, HiSilicon |
R2-2000832 | RNTI ambiguity for CFRA and CBRA of 4-Step RACH | Sony |
R2-2001285 | ON Duration adaptation | LG Electronics Inc., LG Uplus, Vivo |
R2-2001299 | Handling of bwp-InactivityTimer upon BWP switching | LG Electronics Deutschland |
R2-2001307 | Adaptation of QoS Flow to DRB Mapping for MDBV Enforcement | Futurewei |
R2-2001554 | Retransmission of an RLC SDU with a poll after discard procedure | LG Electronics Inc., Ericsson, NTT Docomo, LG Uplus, Sharp |
TDoc | Title | Source |
---|---|---|
R2-2000360 | Correction on beamSwitchTiming values of 224 and 336 | vivo, Huawei, Hisilicon |
R2-2001379 | CR to 38.331 on CSI-RS inter-node message | Huawei, HiSilicon |
R2-2001893 | Correction on beamSwitchTiming values of 224 and 336 | vivo, Huawei, Hisilicon |
R2-2002184 | CR to 38.331 on CSI-RS inter-node message | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000093 | LS on Discussion over UE capabilities of FG2-36/2-40/2-41/2-43 (R1-1913295; contact: Huawei) | RAN1 |
R2-2000198 | Introduction of downgraded configurations for SRS antenna switching | OPPO |
R2-2000361 | Correction on beamSwitchTiming values of 224 and 336 | vivo |
R2-2000683 | Solution for under-reporting CSI-RS capabilities | NTT DOCOMO, INC. |
R2-2000688 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2000689 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2000690 | [DRAFT] Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) | NTT DOCOMO, INC. |
R2-2000911 | Introduction of one-slot periodic TRS configuration for FR1 under a certain condition in TS38.306 | CMCC |
R2-2000912 | Introduction of one-slot periodic TRS configuration for FR1 under a certain condition in TS38.331 | CMCC |
R2-2001273 | Downgrading configuration of SRS for antenna switching - Alt. 1 | Intel Corporation |
R2-2001274 | Downgrading configuration of SRS for antenna switching - Alt. 1 | Intel Corporation |
R2-2001275 | Downgrading configuration of SRS for antenna switching | Intel Corporation |
R2-2001276 | Downgrading configuration of SRS for antenna switching - Alt. 2 | Intel Corporation |
R2-2001277 | Downgrading configuration of SRS for antenna switching - Alt. 2 | Intel Corporation |
R2-2001315 | Discussion on under-reporting CSI-RS capabilities | Huawei, HiSilicon, China Unicom, CMCC |
R2-2001316 | CR on CSI UE capabilities parameters (38.331) | Huawei, HiSilicon, China Unicom, CMCC |
R2-2001317 | CR on CSI UE capabilities parameters (38.306) | Huawei, HiSilicon, China Unicom, CMCC |
R2-2001352 | Introduction of additional RACH configurations for TDD FR1 | NTT DOCOMO, INC. |
R2-2001486 | Discussion on under-reporting CSI-RS capabilities | Huawei, HiSilicon, China Unicom, CMCC, China Telecom |
R2-2002066 | Introduction of downgraded configurations for SRS antenna switching | OPPO |
R2-2002067 | Introduction of downgraded configuration for SRS antenna switching | OPPO |
R2-2002260 | Introduction of downgraded configuration for SRS antenna switching | OPPO, Intel |
R2-2002261 | Introduction of downgraded configuration for SRS antenna switching | OPPO, Intel |
R2-2002273 | Summary of [AT109e][058][TEI16] Downgraded configuration SRS antenna switching (Intel OPPO) | OPPO (Rapporteur) |
R2-2002351 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2002352 | Extension of CSI-RS capabilities per codebook type | NTT DOCOMO, INC. |
R2-2002353 | [DRAFT] Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) | NTT DOCOMO, INC. |
R2-2002415 | Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000228 | Remaining Issues of On Demand SI Procedure in RRC Connected | Samsung Electronics Co., Ltd |
R2-2000478 | Remaining open issues on on-demand request in Connected mode | Intel |
R2-2000500 | On-demand SI support for EN-DC SCG | vivo |
R2-2000607 | Discussion on open issues in On Demand SI | Apple |
R2-2000667 | Remaining issues on on-demand SI in connected | ZTE Corporation, Sanechips |
R2-2000875 | Summary of [108#61][R16] On-demand SI procedure in RRC_CONNECTED_summary | Ericsson |
R2-2000876 | Running CR on 38.331 for on-demand SIB(s) in CONNECTED | Ericsson |
R2-2000877 | Running CR on 38.300 for on-demand SIB(s) in CONNECTED | Ericsson |
R2-2000878 | Open issues list for on-demand SIB | Ericsson |
R2-2000972 | Discussion on SI request enhancement for Connected UEs | Huawei, HiSilicon |
R2-2001154 | Discussion on open issues of on-demand SI procedure in connected | Lenovo, Motorola Mobility |
R2-2001522 | Resolving open issues for on-demand SI | LG Electronics France |
R2-2001670 | Feature summary for on-demand SIB in CONNECTED | Ericsson (Rapporteur) |
R2-2002227 | On-demand SIB in CONNECTED Functionality | Ericsson |
R2-2002228 | Running CR on 38.331 for on-demand SI procedure in RRC_CONNECTED | Ericsson |
R2-2002229 | Running CR on 38.300 for on-demand SI procedure in RRC_CONNECTED | Ericsson |
R2-2002343 | On-demand SIB in CONNECTED Functionality | Ericsson |
R2-2002396 | Introduction of on-demand SI procedure in RRC_CONNECTED | Ericsson |
R2-2002397 | Introduction of on-demand SI procedure in RRC_CONNECTED | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000020 | Response LS on LCP Restriction for Dynamic Grant (R1-1913591; contact: Qualcomm) | RAN1 |
R2-2001356 | Report of [108#112][URLLC] RRC running CR | Huawei, HiSilicon |
R2-2001357 | Running 38.331 CR for NR_L1enh_URLLC | Huawei, HiSilicon |
R2-2001358 | Running 38.321 CR for NR_L1enh_URLLC | Huawei, HiSilicon |
R2-2001359 | Running 38.300 CR for NR_L1enh_URLLC | Huawei, HiSilicon |
R2-2002313 | Introduction of NR eURLLC | Huawei, HiSilicon |
R2-2002314 | Introduction of NR eURLLC | Huawei, HiSilicon |
R2-2002315 | Introduction of NR eURLLC | Huawei, HiSilicon, Nokia (TS rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000032 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point (R3-197775; contact: Nokia) | RAN3 |
R2-2000070 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point (S2-2001675; contact: Nokia) | SA2 |
R2-2000571 | Notification for Alternative QoS profiles | Nokia, Nokia Shanghai Bell |
R2-2000572 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Nokia |
R2-2001360 | Discussion on UE feature list for URLLC | Huawei, HiSilicon |
R2-2001361 | On Layer 2 parameter values to support delay critical GBR QoS flows | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000780 | PDCP discard timer with 0.5ms | Fujitsu |
R2-2000799 | on MAC CE design for eURLLC | Ericsson |
R2-2000800 | PDCP discard timers | Ericsson |
R2-2001332 | New values for RLC and PDCP timers- Open issue and capabilities | Qualcomm Incorporated |
R2-2001362 | On handling of URLLC traffic during measurement gaps in uplink | Huawei, HiSilicon |
R2-2001485 | Enhancement to PHR timeline with URLLC | Qualcomm Inc |
R2-2001567 | Enhancements of SR cancellation for URLLC traffic | LG Electronics Inc. |
R2-2002140 | Summary of [AT109e][063][URLLC] L2 Parameters | Huawei |
R2-2002295 | Summary on [AT109e][064][URLLC] MAC CEs (Ericsson) | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000056 | LS on category M devices and NR (S2-1912608; contact: Qualcomm) | SA2 |
R2-2000094 | Reply LS on direct indication of ETWS/CMAS (R1-1913367; contact: Futurewei) | RAN1 |
R2-2000305 | Introduction of additional enhancements for eMTC | Qualcomm Incorporated |
R2-2000387 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Document Rapporteur (BlackBerry) |
R2-2000433 | Introduction of Rel-16 eMTC enhancements | Qualcomm Incorporated |
R2-2000501 | Addressing Editor's Notes in 36.302 running CR for eMTC | ZTE Corporation, Sanechips |
R2-2000558 | Rapporteur Summary :Discussion on cell selection for non-BL UE | Nokia, Nokia Shanghai Bell |
R2-2000976 | Running CR on 36.321 for eMTC | Ericsson |
R2-2001065 | Introduction of additional enhancements for eMTC | Huawei, HiSilicon |
R2-2001066 | Open issues on the 36.306 running CR for eMTC | Huawei, HiSilicon |
R2-2001097 | Introduction of Rel-16 eMTC enhancements | Intel Corporation |
R2-2001167 | Introduction of Rel-16 eMTC enhancements | Nokia |
R2-2001213 | Running 36.302 CR for R16 eMTC | ZTE Corporation, Sanechips |
R2-2001470 | Report from eMTC/NB-IoT RRC CR coordination telco | Ericsson |
R2-2001868 | Introduction of Rel-16 eMTC additional enhancements | Intel Corporation |
R2-2001869 | Introduction of additional enhancements for R16 eMTC | ZTE Corporation, Sanechips |
R2-2001870 | Introduction of Rel-16 eMTC enhancements | Nokia |
R2-2001871 | Introduction of additional enhancements for eMTC | Huawei |
R2-2001872 | Introduction of further enhancements for eMTC | Ericsson |
R2-2001873 | Introduction of Rel-16 eMTC enhancements | Qualcomm Incorporated |
R2-2001874 | Running CR to 37324 for 5G_V2X_NRSL | Rapporteur (vivo) |
R2-2001886 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Document Rapporteur (BlackBerry) |
R2-2001892 | Introduction of additional enhancements for eMTC | Qualcomm Incorporated |
R2-2001900 | Introduction of additional enhancements for R16 eMTC | ZTE Corporation, Sanechips |
R2-2001901 | Introduction of 5G_V2X_NRSL to 37.324 | Rapporteur (vivo) |
R2-2002211 | Reply LS on extended NAS timers for CE in 5GS (C1-200717; contact: Ericsson) | CT1 |
R2-2002252 | Reply LS on Rel-16 NB-IoT enhancements (R3-201417; contact: Huawei) | RAN3 |
TDoc | Title | Source |
---|---|---|
R2-2000179 | Cat. M2/NB2 indication in UERadioPagingInformation | Qualcomm Incorporated |
R2-2000397 | Support of MT-EDT CIoT EPS optimisation (for CP and UP) | BlackBerry UK Limited |
R2-2001197 | Remaining FFSs for MT-EDT | ZTE Corporation, Sanechips |
R2-2001861 | Summary of contributions on mobile-terminated (MT) early data transmission (EDT) | BlackBerry UK Limited |
R2-2001876 | [AT109e][411][eMTC/NB-IoT] MT-EDT: Open issues (Huawei) | Huawei (offline email discussion rapporteur) |
TDoc | Title | Source |
---|---|---|
R2-2000395 | HARQ RTT Timers in Rel-16 NB-IoT | BlackBerry UK Limited |
R2-2000644 | Signalling aspect of multiple TBs scheduling for NB-IoT | Huawei, HiSilicon |
R2-2000977 | Scheduling enhancements for LTE-M and NB-IoT | Ericsson |
R2-2001862 | Summary of contributions on scheduling multiple Dl/UL transport blocks | Ericsson |
R2-2001877 | Report of [AT109e][412][eMTC/NB-IoT] Scheduling multiple TBs: Open issues (Ericsson) | Ericsson |
R2-2002027 | Summary of Scheduling multiple DL/UL transmission blocks | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000309 | Report of Email Discussion 108#72 To finalize the 2 bit Quality report | Qualcomm Incorporated |
R2-2000310 | Text proposal for 2-bit downlink channel quality reporting in MSG3 for eMTC | Qualcomm Incorporated |
R2-2001069 | Remaining issue of DL quality report | Huawei, HiSilicon |
R2-2001235 | Quality Report in eMTC Remaining Issues | Ericsson |
R2-2001863 | Summary of contributions on quality report in Msg3 | Qualcomm Incorporated |
R2-2001878 | Report of Email Discussion 109e[413][eMTC] Quality report: Open issues | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2000978 | Stage-3 details for MPDCCH performance improvement | Ericsson |
R2-2001879 | Report of [AT109e][414][eMTC] MPDCCH performance imp: Open issues | Qualcomm |
TDoc | Title | Source |
---|---|---|
R2-2000251 | Clarification to idle mode mobility for non-BL UEs | THALES |
R2-2000979 | S-Criterion interpretation for non-BL UEs | Ericsson |
R2-2001067 | Enhancements to idle mode mobility for non-BL UEs | Huawei, HiSilicon |
R2-2001098 | Non-BL UE in normal and enhanced coverage | Intel Corporation |
R2-2001864 | Summary of contributions on idle mode mobility | Intel Corporation |
R2-2001880 | Email discussion of Idle mode mobility for non-BL UE | Intel Corporation |
TDoc | Title | Source |
---|---|---|
R2-2000980 | Cell Reselection improvement for LTE-M Standalone cells | Ericsson |
R2-2001070 | Remaining issue on standalone deployment | Huawei, HiSilicon |
R2-2001127 | Remaining details for standalone LTE-M deployment | Ericsson |
R2-2001865 | Summary of contributions on stand-alone deployment | Nokia, Nokia Shanghai Bell |
R2-2001881 | Standalone deployments – Discussion on remaining Issues | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R2-2001242 | Summary of [108#73] [eMTC] TPs for RSS (Ericsson) | Ericsson |
R2-2001882 | TPs for RSS | Ericsson |
R2-2001887 | TPs for RSS | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000981 | LTE-M coexistence with NR | Ericsson |
R2-2001068 | Coexistence with NR for eMTC | Huawei, HiSilicon |
R2-2001883 | Report of [AT109e][418][eMTC/NB-IoT] Coexistence with NR: Open Issues (ZTE) | ZTE |
R2-2001888 | LS on NR coexistence | RAN2 |
R2-2002024 | Summary of Coexistence with NR | ZTE |
R2-2002062 | LTE-M coexistence with NR | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2001885 | [AT109e][419][eMTC/NB-IoT] Connection to 5GC: Open Issues (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2002014 | Summary of contributions for connection to 5GC (AI 7.1.12) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000538 | Page monitoring in RRC_INACTIVE state with short eDRX | Qualcomm India Pvt Ltd |
R2-2000645 | Discussion on paging of RRC_INACTIVE for eMTC connected to 5GC | Huawei, HiSilicon, Ericsson |
R2-2001211 | FFSs for supporting short eDRX in RRC_INACTIVE for eMTC in 5GC | ZTE Corporation, Sanechips |
TDoc | Title | Source |
---|---|---|
R2-2000646 | SRBs and DRBs handling for NB-IoT and eMTC connected to 5GC | Huawei, HiSilicon |
R2-2000982 | Report of [108#19] when to resume DRBs in UP optimization for 5GC | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000311 | Text proposal for 36.306 to align Cat M definition with LTE-M indicator | Qualcomm Incorporated |
R2-2000536 | Early UE capability retrieval enhancements for eMTC/5GC | Qualcomm India Pvt Ltd |
TDoc | Title | Source |
---|---|---|
R2-2000515 | CE Mode Threshold Adjustments for non-BL and BL UE | NTT DOCOMO INC. |
R2-2001396 | Draft Reply LS on category M devices and NR | LG Electronics UK |
R2-2001875 | Report of [AT109e][410][eMTC] CE Mode Threshold Adjustments for non-BL and BL UE (DoCoMo) | NTT DOCOMO Inc. (offline email discussion rapporteur |
R2-2001884 | CE Mode Threshold Adjustments for non-BL and BL UE | NTT DOCOMO Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000049 | Reply LS on UAC for NB-IOT (S1-193592; contact: Qualcomm) | SA1 |
R2-2000058 | Reply LS on Rel-16 NB-IoT enhancements (S2-1912763; contact: Huawei) | SA2 |
R2-2000064 | Reply LS on 5G-S-TMSI Truncation Procedure (S2-2001248; contact: Qualcomm) | SA2 |
R2-2000068 | Reply LS on assistance indication for WUS (S2-2001578; contact: Huawei) | SA2 |
R2-2000072 | Reply LS to SA2 on 5G-S-TMSI Truncation Procedure (S3-194482; contact: Huawei) | SA3 |
R2-2000088 | Reply LS on assistance indication for WUS (S2-2001732; contact: Huawei) | SA2 |
R2-2000092 | Reply LS on assistance indication for WUS (C1-199008; contact: Huawei) | CT1 |
R2-2000304 | Introduction of additional enhancements for NB-IoT | Qualcomm Incorporated |
R2-2000394 | Introduction of Rel-16 additional enhancements NB-IoT: running 36.306 CR | BlackBerry UK Limited |
R2-2000619 | Introduction of additional enhancements for NB-IoT in TS 36.300 | Huawei |
R2-2000620 | Introduction of additional enhancements for NB-IoT in TS 36.331 | Huawei |
R2-2000621 | Introduction of additional enhancements for NB-IoT in TS 36.302 | Huawei |
R2-2000622 | UE capabilities, TDD/FDD differentiation and 5GC applicability for NB-IoT | Huawei, HiSilicon |
R2-2000647 | Miscellaneous for NB-IoT and eMTC RRC CRs | Huawei, HiSilicon |
R2-2000930 | Introduction of Rel-16 additional enhancements NB-IoT in TS 36.306 | BlackBerry UK Limited |
R2-2000983 | Running CR on 36.321 for NB-IoT | Ericsson |
R2-2001161 | Introduction of Rel-16 eMTC enhancements | Nokia Solutions & Networks (I) |
R2-2001782 | Introduction of additional enhancements for NB-IoT in TS 36.331 | Huawei |
R2-2001783 | Introduction of additional enhancements for NB-IoT | Qualcomm Incorporated |
R2-2001784 | Introduction of additional enhancements for NB-IoT in TS 36.300 | Huawei |
R2-2001785 | Introduction of additional enhancements for NB-IoT in TS 36.302 | Huawei |
R2-2001786 | Introduction of Rel-16 additional enhancements NB-IoT in TS 36.306 | BlackBerry UK Limited |
R2-2001787 | Introduction of additional enhancements for NB-IoT | Ericsson |
R2-2001788 | Introduction of Rel-16 NB-IoT enhancements | Nokia |
R2-2001808 | Report of [AT109e][304][NBIOT R16] NRS presence on non-anchor paging carrier (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2002090 | Introduction of Rel-16 eMTC enhancements | Nokia |
R2-2002212 | Reply LS on Rel-16 NB-IoT enhancements (C1-201024; contact: Ericsson) | CT1 |
R2-2002249 | Reply LS on updates for TS 36.300 and TS 38.300 (R3-201297; contact: Ericsson) | RAN3 |
R2-2002251 | Reply LS on assistance indication for WUS (R3-201397; contact: Huawei) | RAN3 |
TDoc | Title | Source |
---|---|---|
R2-2000306 | Report of Email Discussion 108#94 Finalise the WUS signalling | Qualcomm Incorporated |
R2-2000307 | Text proposal for WUS description in TS 36.304 | Qualcomm Incorporated |
R2-2000308 | Summary of WUS contributions to RAN2#109e. | Qualcomm Incorporated |
R2-2000639 | Remaining issues for Rel-16 GWUS | Huawei, HiSilicon |
R2-2000828 | UE-group wake-up signal for MTC/NB-IoT | Sony |
R2-2001024 | Paging probability based UE grouping | Lenovo, Motorola Mobility |
R2-2001025 | WUS grouping for mobile UE | Lenovo, Motorola Mobility |
R2-2001026 | Consideration on WUS configuration | Lenovo, Motorola Mobility |
R2-2001203 | Consideration on mobility for WUS | ZTE Corporation, Sanechips |
R2-2001210 | Formula for mapping UE to WUS group | ZTE Corporation, Sanechips |
R2-2001472 | Group WUS | Ericsson |
R2-2001789 | WUS: Progress the FFS from Email Discussion 108#94 and Summary (QC) | Qualcomm Incorporated |
R2-2001790 | WUS: Finalise the signalling | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000250 | Remaining clarifications on PUR configuration | THALES |
R2-2000435 | T300 applicability for PUR | Qualcomm Incorporated |
R2-2000443 | TA validation based on serving cell RSRP change (related to RAN4 LSes) | Sierra Wireless, S.A. |
R2-2000559 | Security Aspects of D-PUR for control plane solution | Nokia, Nokia Shanghai Bell |
R2-2000640 | Handling of D-PUR configuration for CP solution | Huawei, HiSilicon |
R2-2000641 | [Draft] LS on handling of D-PUR configuration for the CP solution | Huawei |
R2-2000642 | RRC-MAC-PHY interactions for PUR | Huawei, HiSilicon |
R2-2000643 | Signalling aspect of PUR configuration | Huawei, HiSilicon |
R2-2000695 | Remaining FFSes on RRC-MAC interaction for PUR | Qualcomm Incorporated |
R2-2000984 | PUR periodicity and UE multiplexing | Ericsson |
R2-2000985 | RRC-MAC interaction details and other FFSs for PUR in running MAC CR | Ericsson |
R2-2001198 | D-PUR reconfiguration and release for CP solution | ZTE Corporation, Sanechips |
R2-2001200 | MAC-RRC coordination for TA validation and some FFS for D-PUR | ZTE Corporation, Sanechips |
R2-2001201 | Remaining FFSs for D-PUR in 36.331 | ZTE Corporation, Sanechips |
R2-2001202 | Remaining FFSs for D-PUR in 36.321 | ZTE Corporation, Sanechips |
R2-2001394 | Clarification for the condition of PUR configuration request procedure | LG Electronics UK |
R2-2001395 | Handling application response for D-PUR transmission | LG Electronics UK |
R2-2001397 | Discussion on delivery of D-PUR configuration request | LG Electronics UK |
R2-2001398 | Paging response usign D-PUR | LG Electronics UK |
R2-2001399 | Discussion on preconfigured shared uplink resource transmission | LG Electronics UK |
R2-2001516 | Further Pre-configured UL Resources Design Considerations | Sierra Wireless, S.A. |
R2-2001601 | Handling D-PUR configuration in RRC_CONNECTED state | ASUSTeK |
R2-2001602 | Remaining issues of D-PUR TA timer | ASUSTeK |
R2-2001791 | Report of [AT109e][307][NBIOT] PUR RRC-MAC-PHY interactions | Qualcomm (Rapporteur) |
R2-2001792 | Report of [AT109e][308][NBIOT] PUR RRC in general and L1 signalling impact to RRC (Ericsson) | Ericsson (Rapporteur) |
R2-2001796 | Report of [AT109e][308][NBIOT] updated PUR RRC in general and L1 signalling impact to RRC (Ericsson) | Ericsson (Rapporteur) |
R2-2001816 | LS on open PUR issues for NB-IoT/eMTC | RAN2 |
R2-2002021 | Summary of Other RRC-MAC-PHY interactions | Qualcomm Incorporated |
R2-2002028 | Summary of RRC in general and L1 signalling impact to RRC (including e.g. how/when to configure PHY) | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000623 | Summary of [108#95][NB-IoT] Finalise SON ANR and RLF | Huawei |
R2-2001027 | Remaining issues on ANR reporting | Lenovo, Motorola Mobility |
TDoc | Title | Source |
---|---|---|
R2-2000624 | NRS presence on non-anchor paging carrier | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000625 | Coexistence with NR for NB-IoT | Huawei, HiSilicon |
R2-2000986 | NB-IoT coexistence with NR | Ericsson |
R2-2001215 | RAN2 impacts of coexistence between NB-IoT and NR | ZTE Corporation, Sanechips |
R2-2002063 | NB-IoT coexistence with NR | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000517 | Remaining FFSs for connection to 5GC | ZTE Corporation, Sanechips |
R2-2000539 | UAC information change indication for eMTC UE connected to 5GC | Qualcomm Incorporated |
R2-2000540 | Email discussion report [108#97] for how to minimize ping-pong between CN types in RRC_IDLE/RRC_INACTIVE | Qualcomm India Pvt Ltd |
R2-2000648 | Access barring for eMTC connected to 5GC | Huawei, HiSilicon |
R2-2000830 | Mobility enhancements for Connectivity to 5GC for MTC and NB-IoT | Sony |
R2-2001014 | UE redirection to a specific CN type and ping-pong behavior | Sony Europe B.V. |
R2-2001474 | Report - Email discussion [108#96][NB-IoT/eMTC R16] Finalise details on RAI | Ericsson |
R2-2001478 | AS RAI and optimization of release in EDT | Ericsson |
R2-2001793 | Report -[AT109e][309][NBIOT/EMTC] RAI whether AS RAI should be provided in case including AS RAI would lead to data segmentation (Ericsson) | Ericsson (Rapporteur) |
R2-2001794 | Report of [AT109e][310][ NBIOT] 5GC open issues in AI 7.2.10 (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2001797 | [AT109e][309][NBIOT/EMTC] RAI whether AS RAI should be provided in case including AS RAI would lead to data segmentation | Ericsson (Rapporteur) |
R2-2001798 | Report of [AT109e][310][ NBIOT] 5GC open issues in AI 7.2.10 (Huawei) | Huawei (offline email discussion rapporteur) |
R2-2002015 | Summary of contributions for connection to 5GC (AI 7.2.10) | Huawei |
TDoc | Title | Source |
---|---|---|
R2-2000626 | Report of email discussion [108#98][NB-IoT] UE specific DRX | Huawei |
R2-2000627 | [Drfat] Reply LS to Reply LS on Rel-16 NB-IoT enhancements | Huawei |
R2-2000628 | TP for Introduction of UE specific DRX for NB-IoT in 36.300 | Huawei |
R2-2000629 | TP Introduction of UE specific DRX for NB-IoT in 36.304 | Huawei |
R2-2000630 | TP for Introduction of UE specific DRX for NB-IoT in 36.306 | Huawei |
R2-2000631 | TP for Introduction of UE specific DRX for NB-IoT in 36.331 | Huawei |
R2-2000836 | Details on UE Specific DRX cycle | Sony |
R2-2001629 | NB-IoT UE Specific DRX - NB-IoT UE specific DRX – Options 1/2 and Fast Paging Escalation | Sequans Communications |
R2-2001630 | NB-IoT UE Specific DRX - Efficiency Issues | Sequans Communications |
R2-2001781 | Report of email discussion [108#98][NB-IoT] UE specific DRX | Huawei |
R2-2001795 | [DRAFT] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
R2-2001804 | Report of [AT109e][318][NBIOT] value range of UE specific DRX in NB-IoT | Huawei |
R2-2001815 | Reply LS on Rel-16 NB-IoT enhancements | RAN2 |
TDoc | Title | Source |
---|---|---|
R2-2000024 | Reply LS on uplink TDM pattern for LTE DAPS based enhanced make-before-break HO (R1-1913686; contact: Intel) | RAN1 |
R2-2000334 | Running CR for Introduction of Even futher Mobility enhancement in E-UTRAN | Ericsson |
R2-2001129 | Introduction of Even futher Mobility enhancement in E-UTRAN | Ericsson India Private Limited |
R2-2001473 | UE Capability for Rel-16 LTE even further mobility enhancement | Intel Corporation |
R2-2001579 | Running 36300 CR for LTE feMob | ChinaTelecom |
R2-2001653 | 36300 CR for LTE feMob | ChinaTelecom |
R2-2001752 | Running CR for introduction of even further mobility enhancement in E-UTRAN | ChinaTelecom |
R2-2001753 | Introduction of Even futher Mobility enhancement in E-UTRAN | Ericsson, China Telecom |
R2-2001761 | Introduction of NR Mobility enhancement | Ericsson, CATT |
R2-2001899 | Introduction of even further mobility enhancement in E-UTRAN | ChinaTelecom |
TDoc | Title | Source |
---|---|---|
R2-2000124 | PDCP status reporting in target cell at DAPS handover | Ericsson |
R2-2000128 | Switch of UL data during DAPS handover with 2-step RA or RACH-less access | Ericsson |
R2-2000378 | Release of the source ROHC upon the source link release | vivo |
R2-2000379 | PDCP status report for RLC UM | vivo |
R2-2000383 | Header compression after PDCP reordering | vivo |
R2-2000384 | Issue on the uplink duplicated PDCP SDUs | vivo |
R2-2000465 | Remaining issues on PDCP status report for DAPS | Intel Corporation |
R2-2000591 | Open issues on Mobility Enhancement | Apple |
R2-2000694 | PDCP Status Report for DAPS Handover | ETRI |
R2-2000707 | Resetting UL PDCP SN for RLC UM in DAPS | NEC |
R2-2000708 | PDCP anchor relocation in DAPS | NEC |
R2-2000727 | Running CR for 38.323 on supporting DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2000728 | Running CR for 36.323 on supporting DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2000729 | Discussion on ROHC failure issue | Huawei, HiSilicon |
R2-2000730 | Draft CR for 38.323 based on email discussion#66 output | Huawei, HiSilicon |
R2-2000731 | Draft CR for 36.323 based on email discussion#66 output | Huawei, HiSilicon |
R2-2000732 | Draft CR for 38.323 on ROHC failure issue | Huawei, HiSilicon |
R2-2000738 | Leftover issues on DAPS PDCP | Samsung |
R2-2000896 | UDC Impacts of DAPS | CATT |
R2-2001425 | Discussion of PDCP status report and UL switching for DAPS HO | CMCC. |
R2-2001503 | Need of discard indication | LG Electronics Inc. |
R2-2001504 | Discussion on consecutive ROHC failure during DAPS HO | LG Electronics Inc. |
R2-2001505 | Handling of stroed PDCP PDUs for DAPS | LG Electronics Inc. |
R2-2001507 | Discussion on PDCP status report | LG Electronics Inc. |
R2-2001583 | DAPS configuration related issues for disscussion | China Telecom |
R2-2001639 | Discussion on status reporting for UM DRB upon DAPS handover | SHARP Corporation |
R2-2001646 | Running CR for 38.323 on supporting DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2001647 | Running CR for 36.323 on supporting DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2001750 | Introduction of DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2001754 | Introduction of DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2001765 | Introduction of DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
R2-2001766 | Introduction of DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
TDoc | Title | Source |
---|---|---|
R2-2000371 | Running 36.321 CR for LTE feMob | vivo (rapporteur) |
R2-2000372 | Running 38.321 CR for NR mobility enh. | vivo (rapporteur) |
R2-2000373 | Report of EmailDisc-65 on MAC open issues for mobility enh. | vivo (rapporteur) |
R2-2000736 | The source MAC LCP procedure for DAPS handover | Samsung |
R2-2001751 | Introduction NR mobility enhancement | vivo (rapporteur) |
R2-2001755 | [Running 36.321 CR for LTE feMob] | vivo (rapporteur) |
R2-2001768 | Introduction NR mobility enhancement | vivo |
R2-2001769 | Introducation of even further mobility enhancement in E-UTRAN | vivo |
TDoc | Title | Source |
---|---|---|
R2-2001532 | Summary document for PDCP/RLC aspects of DAPS HO | LG Electronics Inc. |
R2-2002099 | Summary of DAPS MAC | vivo |
R2-2002165 | Outcome of offline discussion 209 for closing UP issues (PDCP/RLC/MAC) and discussing remaining open items for DAPS | LGE |
TDoc | Title | Source |
---|---|---|
R2-2000125 | Open issues at fallback to source cell at DAPS handover | Ericsson |
R2-2000126 | DAPS handover without key change | Ericsson |
R2-2000127 | RRC signalling of DAPS handover per DRB | Ericsson |
R2-2000129 | Subsequent RRC procedures after DAPS handover | Ericsson |
R2-2000313 | Security Key Handling for DAPS Handover | MediaTek Inc. |
R2-2000380 | Failure handling of the non-DAPS DRB | vivo |
R2-2000381 | Clarification on stopping the source link failure | vivo |
R2-2000382 | Single or two RRC messages for DAPS handover | vivo |
R2-2000467 | Remaining issues on RLM after RACH for DAPS | Intel Corporation |
R2-2000656 | Non-DAPS DRB handling upon DAPS HO failure | OPPO |
R2-2000657 | Source RLF handling during DAPS HO | OPPO |
R2-2000733 | Discussion on fallback to source cell | Huawei, HiSilicon |
R2-2000898 | Remaining RRC configuration details for DAPS | CATT |
R2-2001149 | Source connection handling during DAPS HO | Qualcomm Incorporated |
R2-2001152 | Remaining open issues on DAPS HO | Qualcomm Incorporated |
R2-2001506 | Handling of DAPS HO failure | LG Electronics Inc. |
R2-2001640 | State variables of SRB PDCP for the target in NR | SHARP Corporation |
R2-2001641 | Clarification of implementation order of Reconfiguration with sync and AS Security key update procedures | SHARP Corporation |
R2-2001642 | Non-DAPS DRB handling at DAPS handover failure | SHARP Corporation |
R2-2001746 | Report of [AT109e][210][MOB] RRC procedural issues and remaining open items for DAPS CP (Huawei) | Huawei |
R2-2002207 | Report of [AT109e][210][MOB] RRC procedural issues and remaining open items for DAPS CP (Huawei) | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
R2-2000123 | Capability coordination for DAPS handover | Ericsson |
R2-2000537 | UE capability co-ordination signalling aspects for DAPS HO | Qualcomm Inc, Google Inc, Apple Inc, MediaTek Inc, Charter Communications |
R2-2000654 | Discussion on UE capabilities for DAPS HO | OPPO |
R2-2000655 | Further considerations on capability coordination | OPPO |
R2-2000734 | Discussion on SCell handling during DAPS HO | Huawei, HiSilicon |
R2-2000735 | Discussion on UE capability coordination for DAPS HO | Huawei, HiSilicon |
R2-2000759 | Remaining issues on capability coordination for DAPS | NEC |
R2-2000897 | Further Discussion on Capability Coordination for DAPS | CATT |
R2-2001153 | UE capability handling for DAPS | Nokia Italy |
R2-2001164 | Capability coordination for DAPS | Samsung Telecommunications |
R2-2001261 | Remaining issues on UE capability coordination for DAPS HO | ZTE Corporation, Sanechips |
R2-2001539 | Handling Excess of UE Capability in DAPS HO | LG Electronics Inc. |
R2-2001727 | Report of [AT109e][211][MOB] UE capabilities for DAPS and CHO (Intel) | Intel |
TDoc | Title | Source |
---|---|---|
R2-2002033 | Summary on RRC procedures during DAPS HO | Huawei, HiSilicon |
R2-2002041 | Summary of DAPS UE capabilities for DAPS HO in AI 7.3.2.2.2 | Intel |
R2-2002101 | Summary of DAPS UE capabilities for DAPS HO in AI 7.3.2.2.2 | Intel |
TDoc | Title | Source |
---|---|---|
R2-2002048 | Introduction of RRC parameters and UE capabilities for enhanced high speed scenario | NTT DOCOMO INC. |
R2-2002050 | Introduction of UE capabilities for further performance enhancement for LTE in high speed scenario in Rel-16 | CMCC, Huawei, HiSilicon, NTTDOCOMO INC. |
R2-2002172 | [AT109e][204][LTE16] Agreeable CRs for LTE High-speed performance enhancement (NTT DOCOMO) | NTT DOCOMO |
R2-2002173 | Introduction of RRC parameters and UE capabilities for enhanced high speed scenario | NTT DOCOMO INC. |
R2-2002174 | Introduction of UE capabilities for further performance enhancement for LTE in high speed scenario in Rel-16 | CMCC, Huawei, HiSilicon, NTTDOCOMO INC. |
TDoc | Title | Source |
---|---|---|
R2-2000180 | Introduction of RLOS support indicator and RLOS request indicator | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2000006 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
R2-2000007 | Sensor Provide Location Information Elements Correction | Polaris Wireless |
R2-2000188 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
R2-2000396 | Broadcast of TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
R2-2000398 | Broadcast of TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
R2-2000426 | Broadcast of TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
R2-2000987 | Early security re-activation at RRC Connection Resume | Ericsson, Qualcomm Inc., LG Electronics Inc., Sierra Wireless, Turkcell |
R2-2000988 | Early security re-activation at RRC Connection Resume | Ericsson, Qualcomm Inc., LG Electronics Inc., Sierra Wireless, Turkcell |
R2-2001165 | Whether to continue R15 general principle to limit UE capability size | Samsung Telecommunications |
R2-2001408 | Introduction of wideband PRG size | Huawei, HiSilicon |
R2-2001409 | Introduction of wideband PRG size | Huawei, HiSilicon |
R2-2001410 | UDC reconfiguration for RRC connection re-establishment case | Huawei, HiSilicon |
R2-2001731 | Early security re-activation at RRC Connection Resume | Ericsson, Qualcomm Inc., LG Electronics Inc., Sierra Wireless, Turkcell |
R2-2001732 | Early security re-activation at RRC Connection Resume | Ericsson, Qualcomm Inc., LG Electronics Inc., Sierra Wireless, Turkcell |
R2-2001733 | Report of [AT109e][206][LTE16] CR discussion on Rel-16 early security activation (Ericsson) | Ericsson |
R2-2001737 | UDC reconfiguration for RRC connection re-establishment case | Huawei, HiSilicon |
R2-2001738 | Correction on non-3GPP paging | Huawei, HiSilicon |
R2-2001763 | Report of [AT109e][206][LTE16] CR discussion on Rel-16 early security activation (Ericsson) | Ericsson |
R2-2001940 | Sensor Provide Location Information Elements Correction | Polaris Wireless |
R2-2001955 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
R2-2001956 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
R2-2001957 | Addition of broadcast of barometric pressure assistance data | Polaris Wireless, FirstNet, Intel, AT&T, NextNav |
R2-2001958 | Broadcast of TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
R2-2002075 | Correction on non-3GPP paging | Huawei, HiSilicon |
R2-2002078 | Correction on H1 and H2 events | Samsung Electronics |
R2-2002088 | Summary of LTE contributions in AIs 7.5 and 7.6 | Summary rapporteur (RAN2 vice-chair) |
R2-2002191 | Addition of broadcast TBS assistance data | NextNav, AT&T, FirstNet, Polaris Wireless |
TDoc | Title | Source |
---|---|---|
R2-2000153 | CR of TS 36.355 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs Private Limited, Tejas Networks Ltd., Qualcomm Incorporated |
R2-2000157 | CR of TS 36.331 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs Private Limited, Tejas Networks Ltd., Qualcomm Incorporated |
R2-2000158 | CR of TS 36.305 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs |
R2-2001952 | CR of TS 36.355 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs Private Limited, Tejas Networks Ltd., Qualcomm Incorporated |
R2-2001953 | CR of TS 36.331 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs Private Limited, Tejas Networks Ltd., Qualcomm Incorporated |
R2-2001954 | CR of TS 36.305 for introducing NavIC in LTE | Reliance Jio, MediaTek Inc., Huawei, CEWiT, Saankhya Labs |
R2-2002238 | CR of TS 36.355 for introducing NavIC in LTE | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
R2-2002239 | CR of TS 36.331 for introducing NavIC in LTE | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
R2-2002240 | CR of TS 36.305 for introducing NavIC in LTE | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
R2-2002398 | CR of TS 36.355 for introducing NavIC in LTE | Reliance Jio, CEWiT, Huawei, ISRO, MediaTek Inc., Qualcomm Incorporated, Saankhya Labs Private Limited, Tejas Networks Ltd. |
TDoc | Title | Source |
---|---|---|
R2-2001031 | Power headroom reporting for additional SRS | Lenovo, Motorola Mobility |
R2-2001079 | Introduction of Power headroom reporting for Additional SRS | Ericsson |
R2-2001405 | Introduction of DL MIMO efficiency enhancement | Huawei, HiSilicon |
R2-2001406 | Introduction of DL MIMO efficiency enhancement | Huawei, HiSilicon |
R2-2001721 | Introduction of Power headroom reporting for Additional SRS | Ericsson |
R2-2001734 | Introduction of DL MIMO efficiency enhancement | Huawei, HiSilicon |
R2-2001735 | Introduction of DL MIMO efficiency enhancement | Huawei, HiSilicon |
R2-2001741 | Introduction of Power headroom reporting for Additional SRS | Ericsson |
TDoc | Title | Source |
---|---|---|
R2-2000436 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
R2-2000437 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
R2-2001407 | Discussion on handling of MBSFN configuration for new numerologies | Huawei, HiSilicon |
R2-2001739 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
R2-2001740 | Introduction of LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R2-2001661 | Report from session on LTE legacy, LTE TEI16 and NR/LTE Rel-16 Mobility | Vice Chairman (Nokia) |
TDoc | Title | Source |
---|---|---|
R2-2001662 | Report from Break-Out Session on SRVCC, CLI, PRN, eMIMO, RACS | Vice Chairman (ZTE) |
TDoc | Title | Source |
---|---|---|
R2-2001663 | Report eMTC breakout session | Session chair (Ericsson) |
TDoc | Title | Source |
---|---|---|
R2-2001664 | Session minutes for NR-U, Power Savings, NTN and 2-step RACH | Session chair (InterDigital) |
TDoc | Title | Source |
---|---|---|
R2-2001665 | Report from session on Rel-15 and 16 LTE and NR positioning | Session chair (MediaTek) |
TDoc | Title | Source |
---|---|---|
R2-2001666 | Report from SOM/MDT session | Session chair (CMCC) |
TDoc | Title | Source |
---|---|---|
R2-2001667 | Report NB-IoT breakout session | Session chair (Huawei) |
R2-2001814 | Report NB-IoT breakout session | Session chair (Huawei) |
TDoc | Title | Source |
---|---|---|
R2-2001668 | Report from session on LTE V2X and NR V2X | Session chair (Samsung) |
TDoc | Title | Source |
---|---|---|
R2-2001710 | (reserved) | Sergio's tdocs |
R2-2001711 | (reserved) | Sergio's tdocs |
R2-2001712 | (reserved) | Sergio's tdocs |
R2-2001713 | (reserved) | Sergio's tdocs |
R2-2001714 | (reserved) | Sergio's tdocs |
R2-2001715 | (reserved) | Sergio's tdocs |
R2-2001716 | (reserved) | Sergio's tdocs |
R2-2001717 | (reserved) | Sergio's tdocs |
R2-2001718 | (reserved) | Sergio's tdocs |
R2-2001719 | (reserved) | Sergio's tdocs |
R2-2001720 | (reserved) | Sergio's tdocs |
R2-2001760 | (reserved) | Tero's tdocs |
R2-2001770 | (reserved) | Tero's tdocs |
R2-2001771 | (reserved) | Tero's tdocs |
R2-2001772 | (reserved) | Tero's tdocs |
R2-2001773 | (reserved) | Tero's tdocs |
R2-2001774 | (reserved) | Tero's tdocs |
R2-2001775 | (reserved) | Tero's tdocs |
R2-2001776 | (reserved) | Tero's tdocs |
R2-2001777 | (reserved) | Tero's tdocs |
R2-2001778 | (reserved) | Tero's tdocs |
R2-2001779 | (reserved) | Tero's tdocs |
R2-2001780 | (reserved) | Tero's tdocs |
R2-2001799 | (reserved) | Brian's tdocs |
R2-2001800 | (reserved) | Brian's tdocs |
R2-2001801 | (reserved) | Brian's tdocs |
R2-2001802 | (reserved) | Brian's tdocs |
R2-2001803 | (reserved) | Brian's tdocs |
R2-2001813 | (reserved) | Brian's tdocs |
R2-2001817 | (reserved) | Brian's tdocs |
R2-2001818 | (reserved) | Brian's tdocs |
R2-2001819 | (reserved) | Brian's tdocs |
R2-2001820 | (reserved) | Brian's tdocs |
R2-2001821 | (reserved) | Brian's tdocs |
R2-2001822 | (reserved) | Brian's tdocs |
R2-2001823 | (reserved) | Brian's tdocs |
R2-2001824 | (reserved) | Brian's tdocs |
R2-2001825 | (reserved) | Brian's tdocs |
R2-2001826 | (reserved) | Brian's tdocs |
R2-2001827 | (reserved) | Brian's tdocs |
R2-2001828 | (reserved) | Brian's tdocs |
R2-2001829 | (reserved) | Brian's tdocs |
R2-2001830 | (reserved) | Brian's tdocs |
R2-2001831 | (reserved) | Brian's tdocs |
R2-2001832 | (reserved) | Brian's tdocs |
R2-2001833 | (reserved) | Brian's tdocs |
R2-2001834 | (reserved) | Brian's tdocs |
R2-2001835 | (reserved) | Brian's tdocs |
R2-2001836 | (reserved) | Brian's tdocs |
R2-2001837 | (reserved) | Brian's tdocs |
R2-2001838 | (reserved) | Brian's tdocs |
R2-2001839 | (reserved) | Brian's tdocs |
R2-2001840 | (reserved) | Brian's tdocs |
R2-2001841 | (reserved) | Brian's tdocs |
R2-2001842 | (reserved) | Brian's tdocs |
R2-2001843 | (reserved) | Brian's tdocs |
R2-2001844 | (reserved) | Brian's tdocs |
R2-2001845 | (reserved) | Brian's tdocs |
R2-2001846 | (reserved) | Brian's tdocs |
R2-2001847 | (reserved) | Brian's tdocs |
R2-2001848 | (reserved) | Brian's tdocs |
R2-2001849 | (reserved) | Brian's tdocs |
R2-2001850 | (reserved) | Brian's tdocs |
R2-2001851 | (reserved) | Brian's tdocs |
R2-2001852 | (reserved) | Brian's tdocs |
R2-2001853 | (reserved) | Brian's tdocs |
R2-2001854 | (reserved) | Brian's tdocs |
R2-2001855 | (reserved) | Brian's tdocs |
R2-2001856 | (reserved) | Brian's tdocs |
R2-2001857 | (reserved) | Brian's tdocs |
R2-2001858 | (reserved) | Brian's tdocs |
R2-2001859 | (reserved) | Brian's tdocs |
R2-2001860 | (reserved) | Brian's tdocs |
R2-2001890 | (reserved) | Emre's tdocs |
R2-2001902 | (reserved) | Emre's tdocs |
R2-2001903 | (reserved) | Emre's tdocs |
R2-2001904 | (reserved) | Emre's tdocs |
R2-2001905 | (reserved) | Emre's tdocs |
R2-2001906 | (reserved) | Emre's tdocs |
R2-2001907 | (reserved) | Emre's tdocs |
R2-2001908 | (reserved) | Emre's tdocs |
R2-2001909 | (reserved) | Emre's tdocs |
R2-2001910 | (reserved) | Emre's tdocs |
R2-2001925 | (reserved) | Diana's tdocs |
R2-2001930 | (reserved) | Diana's tdocs |
R2-2001939 | (reserved) | Nathan's tdocs |
R2-2001971 | (reserved) | Kyeongin's tdocs |
R2-2001984 | (reserved) | Kyeongin's tdocs |
R2-2001985 | (reserved) | Kyeongin's tdocs |
R2-2001986 | (reserved) | Kyeongin's tdocs |
R2-2001987 | (reserved) | Kyeongin's tdocs |
R2-2001988 | (reserved) | Kyeongin's tdocs |
R2-2001989 | (reserved) | Kyeongin's tdocs |
R2-2001990 | (reserved) | Kyeongin's tdocs |
R2-2002007 | (reserved) | HuNan's tdocs |
R2-2002008 | (reserved) | HuNan's tdocs |
R2-2002009 | (reserved) | HuNan's tdocs |
R2-2002010 | (reserved) | HuNan's tdocs |
R2-2002206 | (reserved) | Diana's tdocs |
R2-2002299 | (reserved) | Diana's tdocs |