TDoc | Title | Source |
---|---|---|
R3-223000 | RAN3#116-e Meeting Agenda | RAN3 Chair |
TDoc | Title | Source |
---|---|---|
R3-223001 | RAN3#115-e Meeting report | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-223060 | Guidelines for RAN3 Electronic Meetings | RAN3 Chair, RAN3 Vice-Chairs |
TDoc | Title | Source |
---|---|---|
R3-223002 | TR 30.531 v1.42.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
TDoc | Title | Source |
---|---|---|
R3-223003 | LS on Call for contribution to ITU FG AN Build-a-thon 2022 | ITU FG-AN |
R3-223004 | LS on updated Rel-17 LTE and NR higher-layers parameter list | RAN1 |
R3-223022 | Reply LS to SA2 on IAB support of NR satellite access | RAN |
R3-223023 | LS on IAB support of NR satellite access | SA2 |
R3-223025 | LS on RAN feedback for low latency | SA2 |
R3-223026 | LS on QoS support with PDU Set granularity | SA2 |
R3-223027 | UE capabilities for MBS | SA2 |
R3-223036 | LS on presentation of EUWENA and involvement in 3GPP on Non Public Network | SA |
R3-223062 | LS on changes over E1AP due to RACH NSA Measurements | SA5 |
R3-223727 | LS Reply on QoS support with PDU Set granularity | SA4 |
R3-223743 | CB: # 50_RACHNSA - Summary of email discussion | Nokia - moderator |
R3-223972 | LS on RACH NSA measurements | Nokia |
R3-224059 | Reply LS on changes over E1AP due to RACH NSA Measurements | Nokia |
R3-224080 | Reply LS on changes over E1AP due to RACH NSA Measurements | Nokia |
TDoc | Title | Source |
---|---|---|
R3-223013 | LS on logged MDT configuration at SN in DC scenario | RAN2 |
R3-223063 | Correction of R17 SON features enhancement | InterDigital |
R3-223064 | Correction of R17 SON features enhancement | InterDigital |
R3-223102 | Analysis and a proposal for correction of the Rel.17 SCG MRO mechanism (incl. draft CRs) | Nokia, Nokia Shanghai Bell |
R3-223103 | A correction to the handling of the Mobility Information in case of CHO (incl. draft CR) | Nokia, Nokia Shanghai Bell |
R3-223137 | (CR for 38.401) Correction on SON features enhancement | China Telecommunication |
R3-223173 | Corrections on SON/MDT | Nokia, Nokia Shanghai Bell |
R3-223174 | Corrections on MDT | Nokia, Nokia Shanghai Bell |
R3-223175 | RACH optimisation in EN-DC secondary cell | Nokia, Nokia Shanghai Bell |
R3-223311 | Correction on MRO for SN Change Failure | Lenovo |
R3-223312 | Correction on SON feature enhancements-XnAP | Lenovo |
R3-223313 | Correction on SON feature enhancements-F1AP | Lenovo |
R3-223419 | Clarification of SCG UE UHI entries when Time Stay value is exceeded | Ericsson |
R3-223423 | Corrections related to Excess Packet delay | Ericsson |
R3-223424 | TS 38.300 corrections for CCO | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223425 | TS 38.401 corrections for CCO | Ericsson, Qualcomm Incorporated, Deutsche Telekom |
R3-223426 | NGAP corrections for Inter-System Load Balancing | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223427 | NGAP RRC Connections for Inter-System Load Balancing | Ericsson |
R3-223428 | NGAP Inter-System Load Balancing corrections for procedure and IEs | Ericsson |
R3-223429 | F1AP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223430 | XnAP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223431 | Load metrics for NR-U | Ericsson |
R3-223432 | MRO for SN change failure correction | Ericsson |
R3-223433 | [DRAFT] Reply LS on User Consent Updating | Ericsson |
R3-223475 | Delivery of Successful Handover Report | Huawei, Qualcomm |
R3-223476 | Corrections to UE History Information in MR-DC | Huawei, CMCC, Qualcomm, Deutsche Telekom |
R3-223477 | Corrections to UE History Information in MR-DC | Huawei, CMCC. Qualcomm, Deutsche Telekom |
R3-223478 | Corrections to UE History Information in MR-DC | Huawei, CMCC, Qualcomm, Deutsche Telekom |
R3-223479 | Corrections to Load Balancing Enhancements | Huawei |
R3-223480 | Correction to MRO for SN Change Failure | Huawei, Deutsche Telekom, Qualcomm |
R3-223482 | Corrections to MRO for mobility enhancement | Huawei, CMCC, Qualcomm |
R3-223483 | Corrections to Mobility Enhancement Optimization | Huawei, CMCC, Qualcomm |
R3-223484 | Corrections to Mobility Enhancement Optimization | Huawei, CMCC, Qualcomm |
R3-223559 | CCO Issue Detection over Xn | Samsung, Verizon |
R3-223560 | The inclusion of the CCO Issue Detection over Xn signalling | Samsung, Verizon |
R3-223561 | Discussion on SON for NR-U | Samsung |
R3-223562 | Correction of SON for NR-U | Samsung |
R3-223563 | Correction of SON for NR-U | Samsung |
R3-223566 | Discussion on corrections for Rel-17 SON MDT | ZTE |
R3-223567 | Correction on R17 SON MDT for 36.300 | ZTE,China Unicom, China Telecom |
R3-223568 | Correction on R17 SON MDT for 36.410 | ZTE,China Unicom, China Telecom |
R3-223569 | Correction on R17 SON MDT for 36.423 | ZTE,China Unicom, China Telecom |
R3-223570 | Correction on R17 SON MDT for 37.483 | ZTE |
R3-223571 | Correction on R17 SON MDT for 38.300 | ZTE |
R3-223572 | Correction on R17 SON MDT for 38.401 | ZTE |
R3-223573 | Correction on R17 SON MDT for 38.410 | ZTE,China Unicom, China Telecom |
R3-223574 | Correction on R17 SON MDT for 38.473 | ZTE,China Unicom, China Telecom |
R3-223575 | Correction on R17 SON MDT for 38.423 | ZTE |
R3-223576 | Correction on R17 SON MDT for 38.413 | ZTE |
R3-223612 | Discussion on the left issues in MDT enhancement | CATT |
R3-223613 | Correction on 38.413 for SON_MDT enhancement | CATT |
R3-223622 | Correction to 37.340 for SON features enhancement | CATT |
R3-223623 | Correction to 38.401 for SON features enhancement | CATT |
R3-223624 | Correction to 38.423 for SON features enhancement | CATT |
R3-223668 | Discussion on MRO SN change failure | ZTE, Samsung, China Telecom |
R3-223669 | Correction for MRO SN change failure | ZTE, Samsung, China Telecom |
R3-223677 | CB: # SONMDT1_SON - Summary of email discussion | Nokia - moderator |
R3-223678 | CB: # SONMDT2_MDT - Summary of email discussion | ZTE - moderator |
R3-223679 | CB: # SONMDT3_NRU - Summary of email discussion | Ericsson - moderator |
R3-223833 | [DRAFT] Reply LS on User Consent Updating | Ericsson |
R3-223843 | CB: # SONMDT1_SON - Summary of email discussion | Nokia - moderator |
R3-223844 | CB: # SONMDT2_MDT - Summary of email discussion | ZTE - moderator |
R3-223860 | Correction to 38.401 for SON features enhancement | CATT, Ericsson, Nokia, Nokia Shanghai Bell |
R3-223862 | F1AP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223863 | XnAP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223864 | CB: # SONMDT3_NRU - Summary of email discussion | Ericsson - moderator |
R3-223933 | Correction to 38.423 for SON features enhancement | CATT |
R3-223952 | CCO Corrections | InterDigital, Lenovo, ZTE, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson |
R3-223953 | NGAP Corrections related to Excess Packet Delay based on RAN2 status | Ericsson |
R3-223954 | XnAP Corrections related to Excess Packet Delay based on RAN2 status | Ericsson |
R3-223964 | Correction of R17 SON features enhancement | InterDigital |
R3-223965 | Correction of R17 SON features enhancement | InterDigital, ZTE |
R3-223974 | Correction on R17 SON MDT for 37.483 | ZTE, Ericsson, CATT |
R3-223975 | Correction on R17 SON MDT for 38.423 | ZTE, Ericsson, CATT |
R3-223976 | Correction on R17 SON MDT for 38.473 | ZTE, China Unicom, China Telecom, Eircsson |
R3-223977 | Correction on SON feature enhancements-F1AP | Lenovo |
R3-223978 | Inter-system energy saving corrections | Nokia, Nokia Shanghai Bell |
R3-223979 | Corrections to UE History Information in MR-DC | Huawei, CMCC. Qualcomm, Deutsche Telekom, Ericsson |
R3-223981 | RACH optimisation in EN-DC secondary cell | Nokia, Nokia Shanghai Bell, CATT, Ericsson |
R3-223984 | Correction on user consent modification | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
R3-223985 | MRO for SN change failure correction | Ericsson |
R3-223986 | Corrections on SON/MDT | Nokia, Nokia Shanghai Bell |
R3-223988 | NGAP Inter-System Load Balancing corrections for procedure and IEs | Ericsson |
R3-223992 | Corrections on MDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
R3-223993 | Correction on R17 SON MDT for 38.300 | ZTE |
R3-223994 | Correction on R17 SON MDT for 38.413 | ZTE, Ericsson |
R3-224008 | A correction to the handling of the Mobility Information in case of CHO | Nokia, Nokia Shanghai Bell |
R3-224013 | TS 38.300 corrections for CCO | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-224016 | F1AP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-224017 | XnAP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-224042 | XnAP corrections for NR-U | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-224069 | LS on Excess Packet delay | CATT |
R3-224075 | TS 38.300 corrections for CCO | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-224076 | Reply LS on User Consent Updating | Ericsson |
R3-224079 | LS on Excess Packet delay | CATT |
R3-224090 | CCO Corrections | InterDigital, Lenovo, ZTE, China Unicom, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson |
TDoc | Title | Source |
---|---|---|
R3-223104 | Alignment of ASN.1 and tabular for inter-RAT MLB solution | Nokia, Nokia Shanghai Bell |
R3-223420 | SON SN UHI maximum values correction in ASN.1 | Ericsson |
R3-223481 | ASN.1 corrections | Huawei |
R3-223621 | ASN.1 review to 38.423 for SON features enhancement | CATT |
R3-223680 | CB: # SONMDT4_ASN - Summary of email discussion | Huawei - moderator |
R3-223875 | ASN.1 corrections | Huawei |
R3-223876 | ASN.1 corrections | Huawei |
R3-224019 | ASN.1 corrections | Huawei, Lenovo, Ericsson |
R3-224043 | ASN.1 corrections | Huawei, Lenovo |
TDoc | Title | Source |
---|---|---|
R3-223115 | (CR TS 38.300): IAB Rel-17 Corrections | Ericsson |
R3-223116 | (CR TS 38.401): IAB Rel-17 Corrections | Ericsson |
R3-223117 | (CR TS 38.420): IAB Rel-17 Corrections | Ericsson |
R3-223118 | (CR TS 38.470): IAB Rel-17 Corrections | Ericsson |
R3-223120 | (CR TS 38.473): IAB Rel-17 Corrections | Ericsson |
R3-223219 | Discussion on IP address request for boundary node in inter-donor redundancy | Fujitsu |
R3-223220 | CR for 38.401 on inter-donor redundancy | Fujitsu |
R3-223221 | Semantics description in Non-F1-terminating Topology BH Information | Fujitsu |
R3-223222 | BAP header rewriting list configuration in NR eIAB | Fujitsu |
R3-223250 | Corrections for IAB | Nokia, Nokia Shanghai Bell |
R3-223251 | Corrections for IAB (Stage-2) | Nokia, Nokia Shanghai Bell |
R3-223252 | Corrections for IAB (XnAP) | Nokia, Nokia Shanghai Bell |
R3-223253 | Corrections for IAB (F1AP) | Nokia, Nokia Shanghai Bell |
R3-223294 | Corrections on procedures for inter-donor topology adaptation, redundancy, and BH RLF recovery in TS 38.401 | ZTE |
R3-223295 | Corrections on IAB in TS 38.423 | ZTE |
R3-223296 | Corrections on IAB in TS 38.473 | ZTE |
R3-223297 | Correction on BAP mapping configuration function in TS 38.470 | ZTE |
R3-223298 | ASN.1 corrections on IAB in TS 38.423 | ZTE |
R3-223299 | ASN.1 corrections on IAB in TS 38.473 | ZTE |
R3-223308 | Correction on IP address allocation | Lenovo |
R3-223309 | Correction on BH Info List | Lenovo |
R3-223310 | Miscellaneous corrections of IAB-XnAP | Lenovo |
R3-223384 | Remaining issue for source IP selection and concurrent TNL migration | Huawei |
R3-223385 | Miscellaneous correction for IAB enhancement | Huawei |
R3-223386 | Correction for IAB inter-donor redundancy and traffic offloading | Huawei |
R3-223387 | Correction for IAB inter-donor DU re-routing and resource multiplexing | Huawei, Lenovo |
R3-223388 | Correction for IAB resource coordination | Huawei |
R3-223389 | Correction for IAB node indication and F1-C traffic transfer | Huawei |
R3-223541 | Correction on Rel-17 eIAB(Stage-2) | Samsung, Huawei |
R3-223542 | Correction on Rel-17 eIAB(XnAP) | Samsung, Huawei |
R3-223673 | CR to 38.401 for Rel-17 IAB | Qualcomm Incorporated |
R3-223674 | CR to 38.423 for Rel-17 IAB | Qualcomm Incorporated |
R3-223675 | CR to 38.473 for Rel-17 IAB | Qualcomm Incorporated |
R3-223705 | CB: # IAB_01_VariousStage2 - Summary of email discussion | Ericsson - moderator |
R3-223706 | CB: # IAB_02_CR38.401 - Summary of email discussion | Lenovo - moderator |
R3-223707 | CB: # IAB_03 _CR38.423 - Summary of email discussion | ZTE - moderator |
R3-223708 | CB: # IAB_04_CR38.473 - Summary of email discussion | Huawei - moderator |
R3-223730 | (CR TS 38.470): IAB Rel-17 Corrections | Ericsson |
R3-223731 | IAB Rel-17 Corrections | ZTE, Ericsson |
R3-223773 | Correction for IAB inter-donor DU re-routing and resource multiplexing | Huawei, Lenovo, Qualcomm, Ericsson, Nokia, ZTE, Fujitsu, Samsung |
R3-223798 | Corrections on IAB in TS 38.423 | ZTE |
R3-223806 | (CR TS 38.300): IAB Rel-17 Corrections | Ericsson |
R3-223807 | (CR TS 38.420): IAB Rel-17 Corrections | Ericsson |
R3-223808 | IAB Rel-17 Corrections | ZTE, Ericsson |
R3-223811 | (CR TS 38.300): IAB Rel-17 Corrections | Ericsson |
R3-223812 | IAB Rel-17 Corrections | ZTE, Ericsson |
R3-223813 | CB: # IAB_02_CR38.401 - Summary of email discussion | Lenovo - moderator |
R3-223814 | CB: # IAB_03 _CR38.423 - Summary of email discussion | ZTE - moderator |
R3-223815 | CB: # IAB_04_CR38.473 - Summary of email discussion | Huawei - moderator |
R3-223913 | LS on RB set configuration | Huawei |
R3-223914 | Correction on IAB Multiplexing info | Huawei |
R3-223939 | Stage-2 corrections on IAB architecture | Lenovo, Ericsson, Fujitsu, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Samsung, Qualcomm Incorporated |
R3-224029 | CB: # IAB_02_CR38.401 - Summary of email discussion | Lenovo - moderator |
R3-224030 | Corrections on IAB in TS 38.423 | ZTE, Nokia, Huawei, Samsung, Ericsson, Lenovo, Qualcomm, Fujitsu |
R3-224031 | LS on RB set configuration | Huawei |
R3-224061 | LS on concurrent TNL migration | Huawei |
TDoc | Title | Source |
---|---|---|
R3-223119 | (CR TS 38.423): IAB Rel-17 Corrections | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-223066 | Enabling SCG activation when needed (incl. draft CRs) | Nokia, Nokia Shanghai Bell |
R3-223067 | Corrections to the CPAC solution (incl. draft CRs) | Nokia, Nokia Shanghai Bell |
R3-223113 | Correction on CPAC to 38.423 | ZTE, Lenovo, CATT |
R3-223114 | Completion of the CPC description to TS37.340 | ZTE, Lenovo, CATT |
R3-223122 | Discussion of some remaining CPAC issues | Qualcomm Incorporated |
R3-223136 | (CR for 38.401) Correction on support of CPAC | China Telecommunication |
R3-223140 | Correction on Early Data Forwarding and other aspects in CPAC | Huawei, China Telecom, Deutsche Telekom |
R3-223141 | Correction on CPAC | Huawei, China Telecom, Deutsche Telekom |
R3-223142 | Correction on CPAC | Huawei, China Telecom, Deutsche Telekom |
R3-223143 | Correction on CPAC | Huawei, China Telecom, Deutsche Telekom |
R3-223164 | Stage-2 aspects for CPAC | Ericsson |
R3-223165 | CPAC corrections over X2 and Xn | Ericsson |
R3-223245 | Corrections to CPAC messages | Google Inc. |
R3-223246 | Corrections to CPAC messages | Google Inc. |
R3-223314 | Correction on CPAC | Lenovo, ZTE, CATT |
R3-223315 | Correction on stage 2 CPAC | Lenovo, Huawei |
R3-223494 | Corrections for Rel-17 SCG | Intel Corporation |
R3-223495 | Corrections for Rel-17 CPAC | Intel Corporation |
R3-223508 | CR to 38.401 Corrections on Overall procedures for CPAC | CATT |
R3-223539 | Supporting of early data forwarding | Huawei |
R3-223597 | Void the clause of Overall procedure CPAC in TS 38.401 | NEC |
R3-223642 | Correction for stage 2 on SCG (de)activation | ZTE, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung, Ericsson, Lenovo, CATT, NEC |
R3-223643 | Correction for E1AP on SCG (de)activation | ZTE, Lenovo, China Unicom, China Telecom |
R3-223644 | Correction for stage 2 on CPAC | ZTE, Lenovo, China Unicom |
R3-223645 | Including data forwarding addresses for multiple T-SNs in the SN Change Confirm message in the SN-initiated inter-SN CPC procedure | Samsung |
R3-223681 | CB: # MRDC1_SCG - Summary of email discussion | ZTE - moderator |
R3-223682 | CB: # MRDC2_CPAC - Summary of email discussion | Qualcomm - moderator |
R3-223779 | Correction for stage 2 on SCG (de)activation | ZTE, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung, Ericsson, Lenovo, CATT, NEC |
R3-223780 | Correction for E1AP on SCG (de)activation | ZTE, Lenovo, China Unicom, China Telecom |
R3-223787 | Correction for stage 2 on SCG (de)activation | ZTE, Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Samsung, Ericsson, Lenovo, CATT, NEC |
R3-223788 | CB: # MRDC1_SCG - Summary of email discussion | ZTE - moderator |
R3-223789 | CB: # MRDC2_CPAC - Summary of email discussion | Qualcomm - moderator |
R3-223894 | Correction on CPAC to 38.423 | ZTE, Lenovo, CATT, Ericsson, Google |
R3-223895 | Correction on CPAC | Huawei, China Telecom, Deutsche Telekom, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
R3-223896 | Correction on CPAC | Huawei, China Telecom, Deutsche Telekom, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
R3-223897 | Correction on CPAC | Lenovo, ZTE, CATT, NEC, Ericsson, Qualcomm, Google |
R3-223898 | Completion of the CPC description to TS37.340 | ZTE, Lenovo, CATT, Intel Corporation, Qualcomm |
R3-223899 | Stage-2 aspects for CPAC | Ericsson, Qualcomm Incorporated, Intel Corporation, ZTE, Lenovo, CATT |
R3-223900 | CR to 38.401 Corrections on Overall procedures for CPAC | CATT, China Telecom, NEC, Google |
R3-223997 | Rel-17 Correction for X2AP on the interaction with SN-intiated SCG (de)activation and SN Addition procedure | Intel Corporation |
R3-223998 | Rel-17 Correction for XnAP on the interaction with SN-intiated SCG (de)activation and SN Addition procedure | Intel Corporation |
R3-224011 | CB: # MRDC1_SCG - Summary of email discussion | ZTE - moderator |
TDoc | Title | Source |
---|---|---|
R3-223068 | Alignment of ASN.1 and tabular for CPC Cancel | Nokia, Nokia Shanghai Bell |
R3-223069 | Alignment of the criticality of CPC Cancel with XnAP ASN.1 | Nokia, Nokia Shanghai Bell |
R3-223166 | CPAC ASN.1 corrections over X2 | Ericsson |
R3-223167 | CPAC ASN.1 corrections over Xn | Ericsson |
R3-223496 | ASN.1 Correction for Rel-17 SCG on SCG Activation Status IE | Intel Corporation |
R3-223538 | Correction on CPAC | Huawei |
R3-223683 | CB: # MRDC3_ASN - Summary of email discussion | Intel - moderator |
TDoc | Title | Source |
---|---|---|
R3-223016 | LS on RAN2 agreements on NR QoE | RAN2 |
R3-223017 | Reply LS on RAN3 agreements on NR QoE | RAN2 |
R3-223043 | (draftCR TS 38.300): QoE Rel-17 Corrections | Ericsson |
R3-223044 | (CR TS 38.401) QoE Rel-17 Corrections | Ericsson |
R3-223045 | (CR TS 38.410) QoE Rel-17 Corrections | Ericsson |
R3-223046 | (CR TS 38.473) QoE Rel-17 Corrections | Ericsson |
R3-223049 | (CR TS 38.401): QoE Rel-17 Corrections | Ericsson |
R3-223050 | (CR TS 38.413): QoE Rel-17 Corrections | Ericsson |
R3-223051 | (CR TS 38.423): QoE Rel-17 Corrections | Ericsson |
R3-223052 | (CR TS 38.473): QoE Rel-17 Corrections | Ericsson |
R3-223092 | (CR TS 38.410 and TS 38.470): QoE Rel-17 Corrections | Ericsson |
R3-223128 | QMC corrections | Nokia, Nokia Shanghai Bell |
R3-223129 | Correction on QMC | Nokia, Nokia Shanghai Bell |
R3-223130 | Correction on QMC | Nokia, Nokia Shanghai Bell |
R3-223131 | Correction on QMC | Nokia, Nokia Shanghai Bell |
R3-223133 | Discussion of potential corrections on R17 QoE measurement | China Unicom |
R3-223134 | CR to TS 38.413 on corrections of QoE configuration | China Unicom, Huawei |
R3-223290 | (draftCR TS 38.300): QoE Rel-17 Corrections | Ericsson |
R3-223509 | CR to 38.413 for Corrections on NR QoE Capability | CATT |
R3-223510 | CR to 38.413 for Corrections on measConfigAppLayerID | CATT |
R3-223511 | CR to 38.423 for Corrections on NR QoE | CATT |
R3-223634 | Discussion on remaining open issues on R17 QoE measurement | Huawei |
R3-223635 | CR to 38.413 on corrections to configuration details | Huawei, China Unicom, Qualcomm Incorporated |
R3-223636 | CR to 38.423 on corrections to QoE measurement continuity | Huawei |
R3-223637 | CR to 38.401 on the introduction of RAN visible QoE metrics | Huawei, Qualcomm Incorporated |
R3-223661 | CR for 38.413 on NR QoE | ZTE |
R3-223662 | CR for 38.423 on NR QoE | ZTE |
R3-223663 | CR for 38.470 on NR QoE | ZTE |
R3-223664 | CR to 38.300 on NR QoE | ZTE |
R3-223684 | CB: # QoE1_Stage2 - Summary of email discussion | Ericsson - moderator |
R3-223685 | CB: # QoE2_Stage3 - Summary of email discussion | Huawei - moderator |
R3-223728 | (CR TS 38.401): QoE Rel-17 Corrections | Huawei, Ericsson |
R3-223729 | (draftCR TS 38.300): QoE Rel-17 Corrections | Ericsson |
R3-223732 | QoE Rel-17 Corrections | Ericsson |
R3-223737 | CR to 38.413 on corrections to configuration details | Huawei, China Unicom, Qualcomm Incorporated, CATT |
R3-223738 | CR to 38.423 on corrections to QoE measurement continuity | Huawei, CATT |
R3-223740 | (CR TS 38.401): QoE Rel-17 Corrections | Huawei, Ericsson |
R3-223746 | QoE Rel-17 Corrections | ZTE, Ericsson |
R3-223781 | (CR TS 38.473): QoE Rel-17 Corrections | Ericsson |
R3-223793 | (draftCR TS 38.300): QoE Rel-17 Corrections | Ericsson |
R3-223794 | QoE Rel-17 Corrections | Ericsson |
R3-223795 | (CR TS 38.401): QoE Rel-17 Corrections | Huawei, Qualcomm Incorporated, Ericsson |
R3-223796 | CB: # QoE1_Stage2 - Summary of email discussion | Ericsson - moderator |
R3-223797 | CB: # QoE2_Stage3 - Summary of email discussion | Huawei - moderator |
R3-223801 | CR to 38.413 for Corrections on NR QoE Capability | CATT, Ericsson, Huawei |
R3-223874 | (CR TS 38.420) QoE Rel-17 Corrections | ZTE |
R3-224044 | (draftCR TS 38.300): QoE Rel-17 Corrections | Ericsson |
R3-224045 | CR to 38.413 on corrections to configuration details | Huawei, China Unicom, Qualcomm Incorporated, CATT, Nokia, ZTE, Ericsson |
R3-224046 | CR to 38.423 on corrections to QoE measurement continuity | Huawei, CATT |
R3-224047 | (CR TS 38.473): QoE Rel-17 Corrections | Ericsson |
R3-224048 | CR to 38.413 for Corrections on NR QoE Capability | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223047 | (CR TS 38.413) QoE Rel-17 Corrections | Ericsson |
R3-223048 | (CR TS 38.423) QoE Rel-17 Corrections | Ericsson |
R3-223135 | CR to TS 38.413 on ASN.1 corrections of QoE measurement | China Unicom |
R3-223512 | CR to 38.423 for ASN.1 Corrections on NR QoE | CATT |
R3-223638 | CR to 38.423 on ASN.1 correction | Huawei |
R3-223639 | CR to 38.413 on ASN.1 correction | Huawei, China Unicom |
R3-223640 | CR to 38.473 on ASN.1 correction | Huawei, China Unicom, China Mobile |
R3-223665 | ASN.1 Correction for 38.423 on NR QoE | ZTE |
R3-223686 | CB: # QoE3_ASN - Summary of email discussion | China Unicom - moderator |
R3-223785 | ASN.1 Correction for 38.423 on NR QoE | ZTE |
R3-223803 | CB: # QoE3_ASN - Summary of email discussion | China Unicom - moderator |
R3-224005 | ASN.1 Correction for 38.423 on NR QoE | ZTE, CATT |
R3-224049 | CR to 38.423 on ASN.1 correction | Huawei |
R3-224050 | CR to 38.473 on ASN.1 correction | Huawei, China Unicom, China Mobile |
TDoc | Title | Source |
---|---|---|
R3-223005 | LS on frequency information of SRS for positioning resources | RAN1 |
R3-223006 | Reply LS on positioning issues needing further input | RAN1 |
R3-223007 | Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN1 |
R3-223008 | LS on multiple measurement instances | RAN1 |
R3-223012 | LS on Positioning in RRC_INACTIVE State | RAN2 |
R3-223021 | Reply LS on latency improvement for PRS measurement with MG | RAN4 |
R3-223032 | Reply LS on Positioning in RRC_INACTIVE State | SA2 |
R3-223123 | Miscellaneous NRPPa corrections for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223124 | Miscellaneous F1AP corrections for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223125 | Stage 2 corrections for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223191 | Discussion on LS on frequency information of SRS for positioning resources and multiple measurement instances | Huawei |
R3-223192 | Discussion on (de)activation of PPW | Huawei |
R3-223193 | Stage 2 update for rel-17 positioning | Huawei |
R3-223273 | Discussion of Positioning Signaling for Alignment with Other Groups | CATT |
R3-223274 | CR to 38.455 for Correction of Positioning Procedure | CATT |
R3-223275 | CR to 38.473 for Correction of Positioning Procedure | CATT |
R3-223276 | Discussion on Positioning support in Inactive | CATT |
R3-223343 | Frequency information of SRS for positioning resources and Signaling of Measurement Instances | Ericsson LM |
R3-223345 | Addition of SRS Frequency to UE Tx TEG and of Measurement Instances | Ericsson LM |
R3-223346 | Support of inactive positioning without anchor relocation | Huawei |
R3-223357 | Positioning corrections (NRPPA) | Ericsson |
R3-223358 | Positioning corrections (F1AP) | Ericsson |
R3-223359 | Discussion on the need of signalling Positioning QoS information to NG-RAN | Ericsson, CATT, Vivo |
R3-223360 | Addition of Positioning QoS information | Ericsson, CATT, Vivo |
R3-223361 | Addition of Positioning QoS information | Ericsson, CATT, Vivo |
R3-223364 | Issues with PRS Processing Window Procedures | Qualcomm Incorporated |
R3-223371 | Corrections to Measurement Pre-configuration Information Transfer | Qualcomm Incorporated |
R3-223372 | Support for Multiple Measurement Instances | Qualcomm Incorporated |
R3-223497 | Correction for positioning measurement during INACTIVE | Intel Corporation |
R3-223498 | Rel-17 ePos correction on positioning measurement during INACTIVE for SRS-PosRRC-InactiveConfig-r17 | Intel Corporation |
R3-223499 | Correction on IE name mismatch in Rel-17 ePos Positioning Context Reservation Indication IE | Intel Corporation |
R3-223505 | SRS for positioning measurement | Google Inc. |
R3-223546 | Issues on Positioning Pre-configured Measurement Gap | Samsung |
R3-223547 | CR to F1AP Support of pre-confiugred measurement gap | Samsung |
R3-223548 | CR to NRPPa Support of pre-confiugred measurement gap | Samsung |
R3-223587 | Correction on Misalignment with Rel-17 changes in NRPPa | ZTE |
R3-223588 | Discussion on multiple measurement instances | ZTE |
R3-223589 | CR for TS38.455 to support multiple measurement instances | ZTE |
R3-223590 | CR for TS38.473 to support multiple measurement instances | ZTE |
R3-223709 | CB: # Positioning_01_MultiMeas - Summary of email discussion | Nokia - moderator |
R3-223710 | CB: # Positioning_02_PPW_Procedures - Summary of email discussion | Qualcomm - moderator |
R3-223711 | CB: # Positioning_03_St3_Corrections - Summary of email discussion | Ericsson - moderator |
R3-223712 | CB: # Positioning_04_RRC_INACTIVEandLS - Summary of email discussion | Intel - moderator |
R3-223865 | Positioning corrections (NRPPA) | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223866 | Positioning corrections (F1AP) | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223873 | Stage 2 corrections for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223886 | CB: # Positioning_01_MultiMeas - Summary of email discussion | Nokia - moderator |
R3-223887 | CB: # Positioning_02_PPW_Procedures - Summary of email discussion | Qualcomm - moderator |
R3-223888 | Positioning corrections (NRPPA) | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223889 | CB: # Positioning_03_St3_Corrections - Summary of email discussion | Ericsson - moderator |
R3-223962 | Corrections to Measurement Pre-configuration Information Transfer | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
R3-223963 | Corrections to Measurement Pre-configuration Information Transfer | Qualcomm Incorporated, Ericsson, CATT, Nokia, Nokia Shanghai Bell |
R3-224018 | CR for TS38.473 to support multiple measurement instances | ZTE |
R3-224032 | Support for Multiple Measurement Instances | Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
R3-224033 | CB: # Positioning_04_RRC_INACTIVEandLS - Summary of email discussion | Intel - moderator |
R3-224036 | CB: # Positioning_02_PPW_Procedures - Summary of email discussion | Qualcomm - moderator |
R3-224037 | Positioning corrections (NRPPA) | Ericsson, Nokia, Nokia Shanghai Bell, CATT |
R3-224038 | Positioning corrections (F1AP) | Ericsson, Nokia, Nokia Shanghai Bell, CATT |
R3-224039 | Reply LS on Positioning in RRC_INACTIVE State | CATT |
R3-224055 | Support of PPW Activation/Deactivation | Huawei |
R3-224071 | CR for TS38.473 to support multiple measurement instances | ZTE Corporation, Ericsson, Nokia, Nokia Shanghai Bell |
R3-224093 | Positioning corrections (NRPPA) | Ericsson, Nokia, Nokia Shanghai Bell, CATT |
R3-224094 | Positioning corrections (F1AP) | Ericsson, Nokia, Nokia Shanghai Bell, CATT |
TDoc | Title | Source |
---|---|---|
R3-223126 | NRPPa ASN.1 review for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223127 | F1AP ASN.1 review for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
R3-223194 | Miscellaneous ASN.1 corrections to NRPPa | Huawei |
R3-223195 | Miscellaneous ASN.1 corrections to F1AP | Huawei |
R3-223277 | ASN.1 review for TS 38.455 | CATT |
R3-223278 | ASN.1 review for TS 38.473 for positioning | CATT |
R3-223347 | Miscellaneous ASN.1 corrections to NRPPa | Huawei |
R3-223348 | Miscellaneous ASN.1 corrections to F1AP | Huawei |
R3-223362 | ASN.1 review of NRPPA | Ericsson |
R3-223363 | ASN.1 review of F1 Positioning | Ericsson |
R3-223585 | ASN.1 correction to TS38.455 on positioning | ZTE |
R3-223586 | ASN.1 correction to TS38.473 on positioning | ZTE |
R3-223713 | CB: # Positioning _05_ASN1_CRs - Summary of email discussion | CATT - moderator |
R3-223756 | ASN.1 review of F1 Positioning | Ericsson |
R3-223867 | NRPPa ASN.1 review for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell, CATT, Ericssion, Huawei, ZTE |
R3-223868 | ASN.1 review for TS 38.473 for positioning | CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson |
R3-223927 | CB: # Positioning _05_ASN1_CRs - Summary of email discussion | CATT - moderator |
R3-224021 | NRPPa ASN.1 review for NR Positioning Enhancements | Nokia, Nokia Shanghai Bell, CATT, Ericssion, Huawei, ZTE |
TDoc | Title | Source |
---|---|---|
R3-223014 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | RAN2 |
R3-223028 | Reply LS on Clarifications on Namf_MBSCommunication N2MessageTransfer service operation | SA2 |
R3-223029 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | SA2 |
R3-223671 | Corrections to F1AP for NR MBS | ZTE |
TDoc | Title | Source |
---|---|---|
R3-223072 | Introduction of RAN triggered Broadcast Session Release procedure | Huawei, CBN, China Unicom, Qualcomm Incorporated, Lenovo, Motorola Mobility |
R3-223073 | Correction on NR MBS for 38410 | Huawei, CBN, China Unicom |
R3-223074 | Correction on Multicast MRB Management and other F1AP aspects | Huawei, CBN |
R3-223075 | Corrections on NR MBS in F1AP | Huawei, CBN, Nokia, Nokia Shanghai Bell |
R3-223076 | Corrections on NR MBS in 38470 | Huawei, CBN, Nokia, Nokia Shanghai Bell |
R3-223077 | MBS Session Status during Xn HO preparation | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility |
R3-223078 | MBS Session Status during NG HO preparation | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility |
R3-223096 | Alignment with rel-17 changes in XnAP | Qualcomm Incorporated |
R3-223185 | Indication for inactive MBS session | NEC |
R3-223187 | MBS Session Status indication in NGAP interface | NEC |
R3-223188 | MBS Session Status indication in Xn interface | NEC |
R3-223282 | Discussion the editors notes related to consent | Samsung |
R3-223283 | Remove the editors notes related to consent information | Samsung |
R3-223284 | Remove the editors notes related to consent information | Samsung |
R3-223300 | User Inactivity Monitoring and Reporting for Multicast | Lenovo |
R3-223301 | Correction on User Inactivity for Multicast Session | Lenovo |
R3-223302 | Configuration of initial value of HFN and reference SN over E1AP | Lenovo, Huawei |
R3-223303 | Correction on configuration of initial value of HFN and reference SN | Lenovo, Huawei |
R3-223304 | F1-U tunnels related issues | Lenovo |
R3-223379 | Rel-17 MBS Corrections | Ericsson |
R3-223380 | MBS NGAP Corrections | Ericsson |
R3-223381 | MBS XnAP Corrections | Ericsson |
R3-223382 | MBS F1AP Corrections | Ericsson |
R3-223383 | MBS E1AP Corrections | Ericsson |
R3-223452 | Correction of MBS Data Forwarding | Nokia, Nokia Shanghai Bell, Huawei |
R3-223459 | Corrections on E1 bearer context management function for NR MBS | LG Electronics |
R3-223533 | [Draft]LS on left-over issues on Rel-17 MBS | CATT |
R3-223535 | Correction on NR MBS | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell |
R3-223604 | Correction on NR MBS mobility for 38300 | ZTE Corporation |
R3-223605 | Correction on NR MBS for 38413 | ZTE Corporation |
R3-223627 | Consent information exchange between E1 interface | Huawei |
R3-223628 | Correction on the FFS consent information | Huawei |
R3-223629 | Correction on the FFS consent information | Huawei |
R3-223650 | Remaining Issues for Stage2 details | CMCC |
R3-223651 | CR to TS38.413 for introduction of broadcast session release required procedure | CMCC |
R3-223672 | Corrections to E1AP for NR MBS | ZTE |
R3-223690 | CB: # MBS1_General_Architecture - Summary of email discussion | Huawei - moderator |
R3-223691 | CB: # MBS2_Service_Continuity - Summary of email discussion | Ericsson - moderator |
R3-223816 | CB: # MBS1_General_Architecture - Summary of email discussion | Huawei - moderator |
R3-223817 | Alignment with rel-17 changes in XnAP | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell and ZTE |
R3-223818 | CB: # MBS2_Service_Continuity - Summary of email discussion | Ericsson - moderator |
R3-223824 | Correction on NR MBS | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell |
R3-223825 | Correction on NR MBS mobility for 38300 | ZTE Corporation |
R3-223826 | Correction of MBS Data Forwarding | Nokia, Nokia Shanghai Bell, Huawei |
R3-223827 | Correction on NR MBS for 38410 | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell, ZTE |
R3-223828 | CR to TS38.413 for introduction of broadcast session release required procedure | CMCC, Huawei, ZTE |
R3-223829 | Corrections on NR MBS in 38470 | Huawei, CBN, Nokia, Nokia Shanghai Bell |
R3-223830 | Corrections on NR MBS in F1AP | Huawei, CBN, Nokia, Nokia Shanghai Bell |
R3-223831 | Corrections on E1 bearer context management function for NR MBS | LG Electronics |
R3-223832 | Correction on configuration of initial value of HFN and reference SN | Lenovo, Huawei |
R3-223834 | MBS NGAP Corrections | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223912 | Corrections on E1 bearer context management function for NR MBS | LG Electronics |
R3-223944 | Correction of the MBS Multicast F1-U Context Descriptor IE | Ericsson |
R3-223945 | Correction of the MBS Multicast F1-U Context Descriptor IE | Ericsson |
R3-223991 | MBS E1AP Corrections | Ericsson |
R3-223996 | Remove the editors notes related to consent information | Samsung |
R3-224009 | Correction of MBS mobility to non supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
R3-224034 | RAN3 Progress on NR MBS | Huawei |
R3-224035 | CB: # MBS1_General_Architecture - Summary of email discussion | Huawei - moderator |
R3-224064 | Remove the editors notes related to consent information | Samsung |
R3-224066 | CB: # MBS2_Service_Continuity - Summary of email discussion | Ericsson - moderator |
R3-224074 | Correction on NR MBS mobility for 38300 | ZTE Corporation |
R3-224078 | MBS NGAP Corrections | Ericsson, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223186 | Correction for maxnoofMBSServiceAreaInformation | NEC |
R3-223285 | Discussion the editors notes in F1AP | Samsung |
R3-223286 | Remove the editors notes | Samsung |
R3-223453 | Correction of MBS Session Management | Nokia, Nokia Shanghai Bell |
R3-223454 | Correction of MBS Xn Handover | Nokia, Nokia Shanghai Bell |
R3-223455 | Correction of MBS NG Handover | Nokia, Nokia Shanghai Bell |
R3-223456 | Correction of MBS Shared CU UP | Nokia, Nokia Shanghai Bell |
R3-223529 | NGAP corrections on MBS feature | CATT |
R3-223530 | XnAP corrections on MBS feature | CATT |
R3-223531 | E1AP corrections on MBS feature | CATT |
R3-223532 | F1AP corrections on MBS feature | CATT |
R3-223536 | Remaining issues over NGAP for NR MBS | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility |
R3-223537 | Correction on NR MBS in E1AP | Huawei |
R3-223591 | E1AP corrections on MBS features | CATT |
R3-223606 | Correction on NR MBS for 38.423 | ZTE Corporation |
R3-223631 | Open issues in NGAP and XnAP specs | Qualcomm Incorporated |
R3-223692 | CB: # MBS3_Stage3Corr - Summary of email discussion | Nokia - moderator |
R3-223819 | CB: # MBS3_Stage3Corr - Summary of email discussion | Nokia - moderator |
R3-223837 | F1AP corrections on MBS feature | CATT |
R3-223838 | Correction of MBS Session Management | Nokia, Nokia Shanghai Bell |
R3-223839 | NGAP corrections on MBS feature | CATT |
R3-223840 | Remaining issues over NGAP for NR MBS | Huawei, CBN, China Unicom, Lenovo, Motorola Mobility, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
R3-223841 | Correction of MBS Xn Handover | Nokia, Nokia Shanghai Bell |
R3-223842 | Correction on NR MBS in E1AP | Huawei |
R3-223930 | XnAP corrections on MBS feature | CATT |
R3-223951 | Correction of MBS Shared CU UP | Nokia, Nokia Shanghai Bell, Ericsson |
R3-223980 | Correction of MBS Shared CU UP | Nokia, Nokia Shanghai Bell, Ericsson |
R3-224065 | Correction of MBS Shared CU UP | Nokia, Nokia Shanghai Bell, Ericsson |
R3-224077 | Correction of MBS Xn Handover | Nokia, Nokia Shanghai Bell, CATT, Huawei |
TDoc | Title | Source |
---|---|---|
R3-223055 | NGAP ASN.1 review for MBS | Nokia, Nokia Shanghai Bell |
R3-223079 | NR MBS NGAP asn.1 correction | Huawei, CBN, Qualcomm Incorporated |
R3-223080 | NR MBS F1AP asn.1 correction | Huawei, CBN |
R3-223607 | Correction on MBS ASN.1 for 38413 | ZTE Corporation |
R3-223608 | Correction on MBS ASN.1 for 38423 | ZTE Corporation |
R3-223630 | NR MBS E1AP asn.1 correction | Huawei |
R3-223693 | CB: # MBS4_ASN - Summary of email discussion | Qualcomm - moderator |
R3-223821 | CB: # MBS4_ASN - Summary of email discussion | Qualcomm - moderator |
R3-223823 | Correction on MBS ASN.1 for 38423 | ZTE Corporation |
R3-223917 | NGAP ASN.1 review for MBS | Nokia, Nokia Shanghai Bell |
R3-223971 | NGAP ASN.1 review for MBS | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei |
TDoc | Title | Source |
---|---|---|
R3-223009 | LS on UE location during initial access in NTN | RAN2 |
R3-223015 | Reply LS on opens issues for NB-IoT and eMTC support for NTN | RAN2 |
R3-223020 | LS on UE location in connected mode in NTN | RAN2 |
R3-223030 | Reply LS on opens issues for NB-IoT and eMTC support for NTN | SA2 |
R3-223031 | Reply LS on RAN Initiated Release due to out-of-PLMN area condition | SA2 |
R3-223098 | Remove unnecessary LTE-M Satellite Indication | Qualcomm Incorporated, Huawei |
R3-223099 | Adding serving PLMN information in ULI for NTN | Qualcomm Incorporated |
R3-223234 | Discussion on remaining issues of NTN and NTN-IoT | Huawei, Deutsche Telekom |
R3-223235 | Correction to NTN-IoT | Huawei, Qualcomm Incorporated, Deutsche Telekom |
R3-223236 | Correction to 38.473 for capturing SIB19 | Huawei, Deutsche Telekom |
R3-223237 | Correction to 38.470 for capturing SIB19 | Huawei, Deutsche Telekom |
R3-223254 | Discussion on corrections for LTE IOT NTN and NR NTN | Nokia, Nokia Shanghai Bell |
R3-223255 | Clarifications for NB-IOT UE | Nokia, Nokia Shanghai Bell, Huawei |
R3-223256 | Corrections for NR NTN | Nokia, Nokia Shanghai Bell |
R3-223271 | Views on UE location aspects for NR NTN | CATT |
R3-223272 | draft CR to TS 38.300 correction on NR NTN | CATT |
R3-223339 | [DRAFT] Reply LS on UE location during initial access in NTN | Ericsson LM |
R3-223340 | LTE-M Capability Indication for NTN | Ericsson LM |
R3-223341 | Removing the unnecessary LTE-M satellite indication | Ericsson LM |
R3-223342 | [DRAFT] Reply LS on open issues for NB-IoT and eMTC support for NTN | Ericsson LM |
R3-223344 | Correction to NTN tabular mistake | Huawei |
R3-223398 | Left Issues on NB-IoT and eMTC Support for NTN | ZTE |
R3-223399 | Stage 2 Correction on NB-IoT and eMTC Support for NTN | ZTE |
R3-223400 | Removal of LTE-M Satellite Indication over S1 | ZTE |
R3-223401 | [DRAFT] Reply LS on open issues for NB-IoT and eMTC support for NTN | ZTE |
R3-223614 | Discussion on reply LS to RAN2 and SA2 | CATT |
R3-223615 | Correction on 36.413 for IoT over NTN | CATT |
R3-223616 | Correction on stage2 for IoT over NTN | CATT |
R3-223687 | CB: # NTN1_NRNTN - Summary of email discussion | Thales - moderator |
R3-223688 | CB: # NTN2_IoToverNTN - Summary of email discussion | ZTE - moderator |
R3-223733 | Removing the unnecessary LTE-M satellite indication | Ericsson LM |
R3-223857 | Clarifications for NB-IOT UE | Nokia, Nokia Shanghai Bell, Huawei |
R3-223858 | Corrections for NR NTN | Nokia, Nokia Shanghai Bell |
R3-223861 | Reply LS on open issues for NB-IoT and eMTC support for NTN | ZTE |
R3-223872 | Correction to 38.470 for capturing SIB19 | Huawei, Deutsche Telekom |
R3-223878 | Removing the unnecessary LTE-M satellite indication | Ericsson LM |
R3-223879 | Removing the unnecessary LTE-M satellite indication | Ericsson LM, Qualcomm Incorporated, ZTE |
R3-223890 | Corrections for NR NTN | Nokia, Nokia Shanghai Bell, CATT, Thales |
R3-223891 | CB: # NTN1_NRNTN - Summary of email discussion | Thales - moderator |
R3-223892 | Stage 2 Correction on NB-IoT and eMTC Support for NTN | ZTE |
R3-223893 | CB: # NTN2_IoToverNTN - Summary of email discussion | ZTE - moderator |
R3-223931 | Correction to 38.470 for capturing SIB19 | Huawei, Deutsche Telekom, Thales |
R3-223982 | Adding serving PLMN information in ULI for NTN | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, CMCC |
R3-224006 | Adding serving PLMN information in ULI for IoT NTN | Ericsson, Nokia, Nokia Shanghai Bell |
R3-224007 | Reply LS on open issues for NB-IoT and eMTC support for NTN | ZTE |
R3-224012 | Clarifications for NB-IOT UE | Nokia, Nokia Shanghai Bell, Huawei |
R3-224081 | Adding serving PLMN information in ULI for IoT NTN | Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
TDoc | Title | Source |
---|---|---|
R3-223413 | ASN.1 Correction on Extended RAT Restriction Information for TS38.423 | ZTE |
R3-223414 | ASN.1 Correction on RAT Restriction Information and Extended RAT Restriction Information for TS38.413 | ZTE |
R3-223689 | CB: # NTN3_ASN - Summary of email discussion | CATT - moderator |
TDoc | Title | Source |
---|---|---|
R3-223223 | CR on TS38.401 for Rel-17 Sidelink Relay | CATT |
R3-223224 | CR on TS38.473 for Rel-17 Sidelink Relay | CATT |
R3-223228 | Corrections on NR SL Relay for 38.413 | ZTE |
R3-223229 | Miscellaneous corrections on NR SL Relay for 38.473 | ZTE |
R3-223257 | Corrections for 5G ProSe UE PC5 Aggregate Maximum Bit Rate IE (NGAP) | Nokia, Nokia Shanghai Bell |
R3-223258 | Corrections for 5G ProSe UE PC5 Aggregate Maximum Bit Rate IE (XnAP) | Nokia, Nokia Shanghai Bell |
R3-223415 | SL Relay corrections over F1 | Ericsson |
R3-223416 | Stage-2 corrections for SL Relay | Ericsson |
R3-223485 | Corrections to SL relay | Huawei |
R3-223486 | Corrections for SL relay | Huawei |
R3-223545 | Correction on Rel-17 sidelink relay (F1AP) | Samsung |
R3-223652 | CR to TS38.413 on R17 Sidelink Relay | CMCC |
R3-223653 | CR to TS38.401 on R17 Sidelink Relay | CMCC |
R3-223694 | CB: # SR1_Corrections - Summary of email discussion | CMCC - moderator |
R3-223932 | Corrections on NR SL Relay for 38.413 | ZTE, Nokia |
R3-223934 | CR on TS38.401 for Rel-17 Sidelink Relay | CATT, Nokia, Ericsson, Samsung |
R3-223949 | Corrections for SL relay | Huawei |
R3-223989 | SL Relay corrections over Xn | Ericsson |
R3-223990 | SL Relay corrections over Xn | Ericsson |
R3-224041 | Corrections for SL relay | Huawei, Nokia, ZTE, Samsung |
TDoc | Title | Source |
---|---|---|
R3-223138 | Correction on Rel-17 Sidelink Relay | China Telecommunication |
R3-223230 | ASN.1 Correction on SL Relay for 38.473 | ZTE |
R3-223259 | Corrections for SL_relay (F1AP) | Nokia, Nokia Shanghai Bell |
R3-223417 | ASN.1 updates on 5G ProSe AMBR | Ericsson |
R3-223418 | Corrections on Remote UE Local ID | Ericsson |
R3-223487 | ASN.1 corrections | Huawei |
R3-223654 | ASN.1 Correction on SL Relay for 38.413 | ZTE |
R3-223695 | CB: # SR2_ASN - Summary of email discussion | China Telecom - moderator |
R3-223859 | Corrections for SL_relay (F1AP) | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223019 | Reply LS on handling of DL non-SDT during SDT procedure | RAN2 |
R3-223070 | Correction on RACH based SDT and CG based SDT | Huawei, China Telecom, China Unicom, ZTE |
R3-223071 | Correction on Fallback from CG-SDT to non-SDT or RA-SDT | Huawei, China Telecom, China Unicom, ZTE, Lenovo, Motorola Mobility |
R3-223097 | Alignment with rel-17 changes in XnAP | Qualcomm Incorporated |
R3-223109 | Discussion on how to buffer the CG-SDT data | ZTE. China Telecm |
R3-223110 | The method on how to buffer the CG-SDT data | ZTE. China Telecm |
R3-223111 | Correction on RACH based SDT | ZTE. China Telecm, CATT |
R3-223112 | Correction on CG based SDT | ZTE, Ericsson, China Telecom, CATT, Huawei,Samsung |
R3-223144 | Correction for Support of SDT procedure over RACH | Huawei, China Telecom, China Unicom |
R3-223145 | Correction for RA-SDT in XnAP | Huawei, China Telecom, China Unicom, Lenovo, Motorola Mobility |
R3-223151 | Correction of RACH-based SDT Stage 2 | Nokia, Nokia Shanghai Bell |
R3-223152 | Correction of RACH-based SDT Stage 3 | Nokia, Nokia Shanghai Bell |
R3-223153 | Correction of CG-based SDT stage 2 | Nokia, Nokia Shanghai Bell |
R3-223168 | SDT corrections in stage-2 | Ericsson |
R3-223170 | SDT corrections over F1 | Ericsson |
R3-223247 | Correction to SDT for supporting delta signaling | Google Inc. |
R3-223248 | Correction to receiving gNB behaviour upon SDT completion | Google Inc. |
R3-223249 | Correction to SDT completion | Google Inc. |
R3-223279 | CR to TS 38.401 Clarifications on RA-SDT overall procedures | CATT, ZTE |
R3-223280 | Draft CR to TS 38.300 correction on RA-SDT overall procedures | CATT, ZTE |
R3-223305 | Correction on SRB SDT indication | Lenovo, ZTE, Huawei, CATT, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
R3-223306 | Correction on SDT termination request in F1 | Lenovo, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson |
R3-223307 | Correction on SRB SDT on XnAP | Lenovo, ZTE, Ericsson, Huawei |
R3-223353 | Analysis of the buffering options for CG-SDT | Ericsson |
R3-223354 | Description of CG-SDT buffering in NG-RAN | Ericsson |
R3-223500 | Correction for Rel-17 RA-SDT with anchor relocation | Intel Corporation |
R3-223501 | Correction for Rel-17 RA-SDT on DL non-SDT data/signalling handling during SDT procedure | Intel Corporation |
R3-223502 | ASN.1 Correction for Rel-17 CG-SDT on SDT-CG-Config container | Intel Corporation |
R3-223534 | Correction on SDT in F1AP | Huawei, China Telecom, China Unicom |
R3-223543 | Correction on Rel-17 SDT (stage-2) | Samsung |
R3-223544 | Correction on Rel-17 SDT (F1AP) | Samsung, ZTE |
R3-223610 | Correction on RA-SDT without anchor relocation in Xn | LG Electronics |
R3-223696 | CB: # SDT1_Common - Summary of email discussion | ZTE - moderator |
R3-223697 | CB: # SDT2_CGbased - Summary of email discussion | Samsung - moderator |
R3-223698 | CB: # SDT3_RACHbased - Summary of email discussion | CATT - moderator |
R3-223845 | Correction on Fallback from CG-SDT to non-SDT or RA-SDT | Huawei, China Telecom, China Unicom, ZTE, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Ericsson, Google, Intel Corporation, NEC, LG Electronics, CATT, Samsung |
R3-223846 | Correction on SDT in F1AP | Huawei, China Telecom, China Unicom, Intel Corporation |
R3-223847 | CB: # SDT1_Common - Summary of email discussion | ZTE - moderator |
R3-223848 | CB: # SDT2_CGbased - Summary of email discussion | Samsung - moderator |
R3-223849 | CB: # SDT3_RACHbased - Summary of email discussion | CATT - moderator |
R3-223852 | Correction on SRB SDT on XnAP | Lenovo, ZTE, Ericsson, Huawei, China Telecom, CATT |
R3-223853 | Correction for RA-SDT in XnAP | Huawei, China Telecom, China Unicom, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Intel Corporation, LG Electronics, CATT |
R3-223854 | CR to TS 38.401 Clarifications on RA-SDT overall procedures | CATT, ZTE |
R3-223855 | Correction on RACH based SDT | ZTE. China Telecm, CATT, Intel Corporation |
R3-223856 | [DRAFT] LS on transfer of SDT related information in case of SDT with UE context relocation | CATT |
R3-223871 | Correction on RA-SDT overall procedures | CATT, ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Google, China Telecom, LG Electronics, NEC, Intel Corporation |
R3-223880 | LS on transfer of SDT related information in case of SDT with UE context relocation | CATT |
R3-223882 | Correction on RACH based SDT | ZTE. China Telecm, CATT, Intel Corporation, Nokia, Nokia Shanghai Bell |
R3-223924 | Correction of RACH-based SDT Stage 3 | Nokia, Nokia Shanghai Bell, LG Electronics, Lenovo |
R3-223925 | Correction on SRB SDT indication | Lenovo, ZTE, Huawei, CATT, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, LG Electronics, China Telecom |
R3-223926 | Correction on SDT termination request in F1 | Lenovo, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Ericsson, China Telecom |
R3-223943 | Correction on Rel-17 SDT (F1AP) | Samsung, ZTE |
R3-223948 | Correction on CG based SDT | ZTE, Ericsson, China Telecom, CATT, Huawei, Samsung, Nokia, Nokia Shanghai Bell |
R3-223955 | LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU | |
R3-224062 | Reply LS on transferring SDT related information in case of SDT with UE context relocation | RAN2 |
R3-224067 | Correction on CG based SDT | ZTE, Ericsson, China Telecom, CATT, Huawei, Samsung, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223169 | SDT corrections over Xn | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-223034 | LS On handover issue for 5G access stratum time distribution | SA2 |
R3-223058 | Resolution of open issues for time synchronisation enhancements | Nokia, Nokia Shanghai Bell |
R3-223059 | Correction of PDC Measurement Periodicity values | Nokia, Nokia Shanghai Bell |
R3-223105 | Consideration on SA2 LS on handover issue for 5G access stratum time distribution | ZTE |
R3-223106 | [DRAFT] Reply LS on handover issue for 5G access stratum time distribution | ZTE |
R3-223265 | Discussion on introducing stop value for the PDC report type over F1 | Samsung |
R3-223266 | Introducing stop value for the PDC report type | Samsung |
R3-223365 | Remaining issues on support of time synchronization | Huawei |
R3-223366 | Correction of PDC Measurement Initiation Failure message | Huawei |
R3-223367 | [Draft] Reply LS on 5G access stratum time distribution during handover | Huawei |
R3-223439 | [Draft] Reply LS On handover issue for 5G access stratum time distribution | Ericsson |
R3-223440 | Introducing Time Synchronisation Assistance Information in Handover Preparation procedure | Ericsson |
R3-223441 | NR-IIoT F1AP correction | Ericsson |
R3-223442 | NR-IIoT periodicity alignment | Ericsson |
R3-223443 | Removing Time Synchronisation Assistance Information | Ericsson |
R3-223513 | Discussion for SA2 LS on handover issue for 5G access stratum time | CATT |
R3-223514 | [Draft]Reply LS on handover issue for 5G access stratum time distribution | CATT |
R3-223699 | CB: # NRIIOT1_Corrections - Summary of email discussion | Nokia - moderator |
R3-223782 | Correction of PDC Measurement Initiation Failure message | Huawei |
R3-223790 | NR-IIoT F1AP correction | Ericsson |
R3-223791 | Reply LS on handover issue for 5G access stratum time distribution | ZTE |
R3-223916 | Correction of PDC Measurement Initiation Failure message | Huawei, Ericsson, CATT |
R3-224002 | NR-IIoT F1AP correction | Ericsson, Huawei, CATT, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223700 | CB: # NRIIOT2_ASN - Summary of email discussion | Ericsson - moderator |
TDoc | Title | Source |
---|---|---|
R3-223010 | Reply LS on LTE User Plane Integrity Protection | RAN2 |
R3-223368 | Signalling the EPS User Plane Integrity Protection Capability for EN-DC | Huawei, Deutsche Telekom |
R3-223369 | Remaining issues to support the EPS User Plane Integrity Protection | Huawei, Deutsche Telekom |
R3-223444 | UPIP EPC Correction on E1AP procedual Text | Ericsson |
R3-223445 | UPIP EPC Correction on S1AP | Ericsson |
R3-223446 | Reuse LTE UE Security Capabilities IE for UE UPIP EPC support | Ericsson, Qualcomm Incorporated |
R3-223447 | Correction on Security Result | Ericsson |
R3-223457 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223458 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223503 | Correction for missing signalling from MeNB to SgNB regarding the UE's EPS-UPIP capability | Intel Corporation |
R3-223504 | Correction for Rel-17 EPS-UPIP on UE's EPS-UPIP capability signalling to SgNB | Intel Corporation |
R3-223506 | eNB UPIP capability over interface management messages | Huawei |
R3-223577 | Correction for UE support UP integrity protection in EN-DC | ZTE |
R3-223701 | CB: # EPSUPIP_Corrections - Summary of email discussion | Vodafone - moderator |
R3-223884 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223885 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223909 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223910 | UPIP EPC Correction on S1AP | Ericsson |
R3-223911 | Correction of EPS Integrity Protection | Nokia, Nokia Shanghai Bell |
R3-223915 | LS on UEs LTE UPIP capability for EN-DC | Vodafone |
TDoc | Title | Source |
---|---|---|
R3-223370 | Correction of the Security Indication IE in Source eNB to Target eNB Transparent Container | Huawei, Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R3-223018 | LS out on PEI and UE Subgrouping | RAN2 |
R3-223033 | Reply LS out on PEI and UE Subgrouping | SA2 |
R3-223038 | Correction of UDC in CP-UP Split architecture | China Telecom,ZTE,CATT,Huawei |
R3-223039 | Correction of UDC in CP-UP Split architecture | China Telecom,ZTE,CATT,Huawei |
R3-223100 | Discussion on remaining PEI issues | Qualcomm Incorporated |
R3-223101 | [DRAFT] Reply LS on PEI and UE Subgrouping | Qualcomm Incorporated |
R3-223139 | CR(38.470) on SIB18 signalling | China Telecommunication, Huawei |
R3-223146 | CR(38.473) on SIB18 signalling | Huawei, China Telecom |
R3-223154 | Correction of MUSIM Cause | Nokia, Nokia Shanghai Bell, ZTE, Orange, Verizon Wireless |
R3-223155 | Correction of Paging Subgrouping | Nokia, Nokia Shanghai Bell |
R3-223156 | Correction of Paging Subgrouping | Nokia, Nokia Shanghai Bell |
R3-223225 | Discussion on LS on PEI and UE Subgrouping | CATT |
R3-223226 | Reply LS on PEI and UE Subgrouping | CATT |
R3-223238 | Correction on enhanced eNB architecture evolution | Huawei |
R3-223239 | Correction to RedCap | Huawei |
R3-223240 | Correction to MUSIM | Huawei, ZTE, Radisys, Reliance JIO, Nokia, Nokia Shanghai Bell |
R3-223241 | Further discussion on MUSIM gaps | Huawei, ZTE |
R3-223242 | Correction of the "last used cell" in UE Context Release Complete | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, Samsung |
R3-223262 | Discussion on PEI and UE Subgrouping | ZTE |
R3-223263 | Clarification on paging capability for TS38.470 | ZTE |
R3-223264 | [Draft] Reply LS for PEI and UE Subgrouping | ZTE |
R3-223267 | Correction E-UTRA Paging eDRX Information for TS38.413 | ZTE |
R3-223268 | Discussion on RedCap Broadcast Information | ZTE |
R3-223269 | Correction on RedCap Broadcast Information for TS38.423 | ZTE |
R3-223270 | Correction on RedCap Broadcast Information for TS38.473 | ZTE |
R3-223292 | PEI and UE Subgrouping | Huawei |
R3-223293 | [Draft] Reply LS on PEI and UE Subgrouping | Huawei |
R3-223350 | UE Power Saving Correction in NGAP | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Inc., CATT, Samsung, ZTE |
R3-223351 | Discussion on RAN2 LS on PEI and UE Subgrouping | Ericsson |
R3-223352 | LS Reply on PEI and UE Subgrouping | Ericsson |
R3-223355 | Correction of Paging Assistance Data for CE Capable UE | Ericsson |
R3-223356 | Correction of Cell Identifier and Coverage Enhancement Level | Ericsson |
R3-223448 | MUSIM Correction on F1AP procedural text | Ericsson, Qualcomm Incorporated |
R3-223449 | MUSIM Correction on NGAP | Ericsson |
R3-223450 | MUSIM corrections | Ericsson |
R3-223632 | Avoid R17 paging to legacy UE | Qualcomm Incorporated |
R3-223633 | Clarification on Paging Cause | Qualcomm Incorporated, Ericsson |
R3-223655 | Avoid R17 paging to legacy UE (NGAP CR) | Qualcomm Incorporated |
R3-223702 | CB: # UEPowSav_Corrections - Summary of email discussion | ZTE - moderator |
R3-223703 | CB: # MUSIM_Corrections - Summary of email discussion | Ericsson - moderator |
R3-223704 | CB: # RedCap_Corrections - Summary of email discussion | ZTE - moderator |
R3-223757 | CB: # MUSIM_Corrections - Summary of email discussion | Ericsson - moderator |
R3-223772 | Correction on enhanced eNB architecture evolution | Huawei |
R3-223901 | Correction on RedCap Broadcast Information for TS38.423 | ZTE, Nokia, Nokia Shanghai Bell |
R3-223902 | Correction on RedCap Broadcast Information for TS38.473 | ZTE, Nokia, Nokia Shanghai Bell |
R3-223903 | Correction to MUSIM | Huawei, ZTE, Radisys, Reliance JIO, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated, CATT, Samsung |
R3-223904 | MUSIM Correction on NGAP | Ericsson, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-223946 | Reply LS for PEI and UE Subgrouping | ZTE |
R3-223947 | Clarification on paging capability for TS38.470 | ZTE |
R3-223950 | Correction of the "last used cell" in UE Context Release Complete | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, Samsung |
R3-223956 | Correction to MUSIM | Huawei, ZTE, Radisys, Reliance JIO, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated, CATT, Samsung |
R3-223957 | MUSIM Correction on NGAP | Ericsson, Nokia, Nokia Shanghai Bell, CATT, Samsung |
R3-223958 | Correction of UDC in CP-UP Split architecture | China Telecom, ZTE, CATT, Huawei |
R3-223959 | CR(38.470) on SIB18 signalling | China Telecommunication, Huawei |
R3-223960 | Clarification on paging capability for TS38.470 | ZTE, Nokia, Nokia Shanghai Bell |
R3-223961 | CB: # UEPowSav_Corrections - Summary of email discussion | ZTE - moderator |
R3-224003 | Correction of the "last used cell" in UE Context Release Complete | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, Samsung, Qualcomm Incorporated |
R3-224004 | Reply LS for PEI and UE Subgrouping | ZTE |
TDoc | Title | Source |
---|---|---|
R3-223121 | SN direct data forwarding in inter-system handover | Qualcomm Incorporated |
R3-223132 | Direct data forwarding in NR SA to EN-DC handover (CR to 36.423) | Qualcomm Incorporated |
R3-223319 | Direct data forwarding for mobility between DC and SA (Scenario 3) | China Telecom, Samsung, Verizon Wireless |
R3-223471 | Inter-system direct data forwarding between source SgNB and target gNB | Ericsson |
R3-223472 | Inter-system direct data forwarding between source SgNB and target gNB | Ericsson |
R3-223473 | Xn UP transport for HO from EN-DC to SA | Ericsson |
R3-223474 | Xn UP transport for HO from EN-DC to SA | Ericsson |
R3-223540 | Direct data forwarding for mobility between DC and SA (Scenario 3) | China Telecom, Samsung, Verizon Wireless |
R3-223552 | Direct Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
R3-223553 | Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
R3-223554 | Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
R3-223555 | Direct data forwarding for mobility between DC and SA | Samsung, Verizon, China Telecom |
R3-223556 | Direct data forwarding for mobility from MR-DC to eNB | Samsung, Huawei, China Telecom, Verizon Wireless |
R3-223557 | Direct data forwarding for mobility between DC and SA (Scenario 3) | Samsung, China Telecom, Verizon Wireless |
R3-223558 | LS to SA2 on direct data forwarding between DC and SA | Samsung |
R3-223714 | CB: # 1_DirectDataFwd_DCtoSA - Summary of email discussion | Samsung - moderator |
R3-223771 | Direct data forwarding in NR SA to EN-DC handover (CR to 36.423) | Qualcomm Incorporated |
R3-223999 | Direct data forwarding for mobility from MR-DC to eNB | Samsung, Huawei, China Telecom, Verizon Wireless |
R3-224000 | Direct data forwarding for mobility from MR-DC to eNB | Samsung, Huawei, China Telecom, Verizon Wireless |
R3-224001 | Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
R3-224015 | Data forwarding address allocation for handover to EN-DC | Samsung, Verizon Wireless, ZTE |
TDoc | Title | Source |
---|---|---|
R3-223199 | Discussion on remaining issues for ACL | Huawei, Deutsche Telekom, Ericsson |
R3-223200 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223201 | F1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223202 | W1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223203 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223204 | F1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223205 | W1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223321 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, Huawei |
R3-223322 | Dynamic ACL over E1 CR 37.483 | Ericsson, Deutsche Telekom, Huawei |
R3-223323 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, Huawei |
R3-223324 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, Huawei |
R3-223325 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, Huawei |
R3-223326 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, Huawei |
R3-223327 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, Huawei |
R3-223328 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, Huawei |
R3-223396 | Reply LS on On ACL support for Indirect Data Forwarding | Ericsson |
R3-223520 | Discussion on ACL for MR-DC to SA handover scenario | CATT |
R3-223521 | CR on support of ACL for handover from EN-DC to SA | CATT |
R3-223522 | CR on support of ACL for handover from EN-DC to SA | CATT |
R3-223601 | Discussion on ACL issues | ZTE Corporation |
R3-223602 | Correction on ACL over W1AP | ZTE Corporation |
R3-223603 | Correction on ACL over F1AP | ZTE Corporation |
R3-223715 | CB: # 2_DynamicACL - Summary of email discussion | Huawei - moderator |
R3-223783 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-223784 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-224053 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson, CATT |
R3-224054 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson, CATT |
R3-224097 | F1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-224098 | W1AP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson |
R3-224099 | NGAP CR for ACL remaining issues | Huawei, Deutsche Telekom, Ericsson, CATT |
R3-224100 | Dynamic ACL over E1 CR 38.463 | Ericsson, Deutsche Telekom, Huawei |
R3-224101 | Dynamic ACL over E1 CR 37.483 | Ericsson, Deutsche Telekom, Huawei |
R3-224102 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, Huawei |
R3-224103 | Dynamic ACL over S1 CR 36.413 | Ericsson, Deutsche Telekom, Huawei |
R3-224104 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, Huawei |
R3-224105 | Dynamic ACL over X2 CR 36.423 | Ericsson, Deutsche Telekom, Huawei |
R3-224106 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, Huawei |
R3-224107 | Dynamic ACL over Xn CR 38.423 | Ericsson, Deutsche Telekom, Huawei |
TDoc | Title | Source |
---|---|---|
R3-223024 | Response LS on NAS PDU delivery during PDU Session modification procedure | SA2 |
R3-223157 | Correction of NAS PDU delivery | Nokia, Nokia Shanghai Bell, Orange, VerizonWireless |
R3-223158 | Correction of NAS PDU delivery | Nokia, Nokia Shanghai Bell, Orange, VerizonWireless |
R3-223159 | Correction of NAS PDU delivery | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless |
R3-223160 | Reply LS on NAS PDU delivery during PDU Session modification procedure | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless |
R3-223316 | Discussion on PDU session related NAS-PDU delivery | Ericsson |
R3-223317 | PDU session related NAS-PDU delivery | Ericsson |
R3-223318 | PDU session related NAS-PDU delivery | Ericsson |
R3-223330 | Correction of PDU session resource modify | Huawei, China Unicom, Orange |
R3-223331 | Correction of PDU session resource modify | Huawei, China Unicom, Orange |
R3-223332 | Correction of PDU session resource modify | Huawei, China Unicom, Orange |
R3-223333 | [Draft] Reply LS on NAS PDU delivery during PDU Session modification procedure | Huawei, China Unicom, Orange |
R3-223451 | PDU session related NAS-PDU delivery | Ericsson |
R3-223523 | Discussion on NAS PDU delivery during PDU Session Modification procedure | CATT,CMCC |
R3-223524 | Correction on NAS PDU delivery during PDU session Modification procedure | CATT,CMCC |
R3-223525 | Correction on NAS PDU delivery during PDU session Modification procedure | CATT,CMCC |
R3-223526 | [Draft]Response LS on NAS PDU delivery during PDU Session modification procedure | CATT, CMCC |
R3-223578 | PDU session NAS PDU Delivery(R16) | ZTE |
R3-223579 | PDU session NAS PDU Delivery(R17) | ZTE |
R3-223716 | CB: # 3_NASPDU_Delivery - Summary of email discussion | Nokia - moderator |
R3-223850 | Correction of NAS PDU delivery | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless, Ericsson, Qualcomm Incorporated, ZTE, Huawei, CATT, Samsung |
R3-223851 | Correction of NAS PDU delivery | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless, Ericsson, Qualcomm Incorporated, ZTE, CATT, Huawei, Samsung |
R3-223929 | Response LS on NAS PDU delivery during PDU Session modification procedure | CATT, CMCC |
TDoc | Title | Source |
---|---|---|
R3-223176 | Standards impacts of Resource Coordination between LTE and NR | Nokia, Nokia Shanghai Bell |
R3-223320 | Support of EN-DC X2 connection between SA gNB and LTE eNB | China Telecom |
R3-223329 | Support of the coordination of resources between co-channel sharing LTE and NR cells | China Telecom |
R3-223406 | Conclusions on PRACH Coordination Between LTE and NR | Ericsson |
R3-223507 | introduction of new attributes Only Resource Coordination in ANR | China Telecom |
R3-223519 | introduction of only resource coordination in EN-DC | China Telecom |
R3-223717 | CB: # 4_PRACH - Summary of email discussion | China Telecom - moderator |
R3-223907 | introduction of new attributes Only Resource Coordination in ANR | China Telecom, Ericsson, Huawei, ZTE, CATT |
R3-223908 | LS on introduction of a new attribute Only Resource Coordination to support source coordination between LTE and NR SA | China Telecom |
R3-224056 | LS on introduction of a new attribute Only Resource Coordination to support source coordination between LTE and NR SA | China Telecom |
TDoc | Title | Source |
---|---|---|
R3-223334 | On node capability detection for non-direct-connected nodes | Huawei, China Unicom, China Telecom |
R3-223335 | On node capability detection for non-direct-connected nodes [Node_Cap_Dect] | Huawei, China Unicom, China Telecom |
R3-223373 | Further discussion on RACS Capability Detection for NG handover (and generalizing detection of target functionality by source NG-RAN node) | Qualcomm Incorporated, Vodafone |
R3-223374 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
R3-223375 | Exchange of protocol support at target RAN node for NG handover | Ericsson |
R3-223376 | Exchange of protocol support at target RAN node for NG handover | Ericsson |
R3-223718 | CB: # 5_ProtocolSupport - Summary of email discussion | Ericsson - moderator |
R3-223987 | Exchange of protocol support at target RAN node for NG handover | Ericsson, Qualcomm Incorporated |
R3-224060 | Exchange of protocol support at target RAN node for NG handover | Ericsson, Qualcomm Incorporated |
R3-224073 | Exchange of protocol support at target RAN node for NG handover | Ericsson, Qualcomm Incorporated |
R3-224082 | Exchange of protocol support at target RAN node for NG handover [PROT_SUP] | Ericsson, Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
R3-223037 | E1 TS 37.480 Editorial corrections | Nokia, Nokia Shanghai Bell |
R3-223053 | Inclusive language review for TS 25.467 | Nokia, Nokia Shanghai Bell |
R3-223054 | Inclusive language review for TS 25.402 | Nokia, Nokia Shanghai Bell |
R3-223056 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
R3-223057 | Moving MBS Session TNL-related IEs to the correct subclause | Nokia, Nokia Shanghai Bell |
R3-223095 | Alignment with rel-17 changes in XnAP | Qualcomm Incorporated |
R3-223171 | X2AP rapporteur's corrections | Ericsson, CATT, NEC |
R3-223172 | X2AP rapporteur's corrections | Ericsson, CATT, NEC |
R3-223189 | Rapporteur Update to TS 36.401 | NEC |
R3-223190 | Rapporteur Update to TS 38.401 | NEC |
R3-223227 | Rapporteur Update to TS 38.401 | NEC Corporation |
R3-223338 | Inclusive Language Discussions - Final Status Update | Ericsson (coordinator) |
R3-223349 | Rapporteur Corrections to Rel-17 NRPPa | Ericsson |
R3-223377 | Corrections caused by rapporteur corrections for Version 17.0.0 | Rapporteur (Ericsson) |
R3-223378 | Rapporteur's correction to XnAP version 17.0.0 | Rapporteur (Ericsson) |
R3-223434 | NGAP rapporteur corrections for SON | Nokia, Nokia Shanghai Bell |
R3-223491 | Editorial corrections | Huawei |
R3-223492 | Editorial corrections | Huawei |
R3-223493 | E1AP Rapporteur Corrections | Ericsson |
R3-223580 | Inclusive language cleanup for TS25.484 | ZTE |
R3-223619 | Inclusive language cleanup for TS25.484 | ZTE Corporation |
R3-223641 | Rapporteur clean-ups to 37.482 | Huawei |
R3-223719 | CB: # 6_RapporteurUpdates - Summary of email discussion | ZTE - moderator |
R3-223739 | Rapporteur clean-ups to 37.482 | Huawei |
R3-223742 | Corrections caused by rapporteur corrections for Version 16.9.0 | Rapporteur (Ericsson) |
R3-223786 | Inclusive language cleanup for TS25.484 | ZTE Corporation |
R3-223869 | Rapporteur Update to TS 38.401 | NEC Corporation |
R3-223877 | Editorial corrections | Huawei |
R3-223918 | NGAP rapporteur corrections | Nokia, Nokia Shanghai Bell |
R3-223919 | NGAP rapporteur corrections for SON | Nokia, Nokia Shanghai Bell |
R3-223983 | E1AP Rapporteur Corrections | Ericsson |
R3-224020 | Rapporteur's correction to XnAP version 17.0.0 | Rapporteur (Ericsson) |
R3-224040 | Editorial corrections | Huawei |
R3-224083 | Rapporteur clean-ups to 37.482 | Huawei |
R3-224088 | Rapporteur Corrections to Rel-17 NRPPa | Ericsson |
R3-224089 | Rapporteur Update to TS 38.401 | NEC Corporation |
R3-224096 | Rapporteur Corrections to Rel-17 NRPPa | Ericsson |
TDoc | Title | Source |
---|---|---|
R3-223040 | Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei |
R3-223041 | R16 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei |
R3-223042 | R17 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei |
R3-223065 | Support of count on QoS flow released in session | China Telecom, CATT |
R3-223081 | Clarification on RFSP index | NTT DOCOMO INC., Ericsson |
R3-223082 | Clarification on RFSP index | NTT DOCOMO INC. |
R3-223083 | Clarification on RFSP index | NTT DOCOMO INC., Ericsson |
R3-223084 | Clarification on RFSP index | NTT DOCOMO INC., Ericsson |
R3-223085 | Clarification on RFSP index | NTT DOCOMO INC., Ericsson |
R3-223086 | Clarification on RFSP index | NTT DOCOMO INC., Ericsson |
R3-223087 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
R3-223088 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
R3-223089 | Clarification on PDU session resource modification | NTT DOCOMO INC. |
R3-223093 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE |
R3-223094 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE |
R3-223107 | Correction on CHO Information SN Modification to 36.423[CHOwithDCkept] | ZTE, Nokia, Nokia Shanghai Bell, NEC, Huawei, Ericsson |
R3-223108 | Correction on CHO Information SN Modification to 38.423[CHOwithDCkept] | ZTE, Nokia, Nokia Shanghai Bell, NEC, Huawei, Ericsson |
R3-223147 | On user consent for RLF/CEF | Apple |
R3-223148 | [DRAFT] Reply LS on the user consent for trace reporting | Apple |
R3-223149 | Introduction of user consent for location information in RLF/CEF to 38.413 | Apple |
R3-223150 | Introduction of user consent for location information in RLF/CEF to 38.423 | Apple |
R3-223177 | Racing condition of the signalling - Handover | NEC, NTT DOCOMO INC. |
R3-223178 | Correction for handling racing condition of signalling Handover | NEC, NTT DOCOMO INC. |
R3-223179 | Correction for handling racing condition of signalling Handover | NEC, NTT DOCOMO INC. |
R3-223180 | Correction for handling racing condition of signalling Handover | NEC, NTT DOCOMO INC. |
R3-223181 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
R3-223182 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
R3-223183 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
R3-223184 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
R3-223196 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
R3-223197 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
R3-223198 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
R3-223206 | Discussion on release-with-redirect in anchor gNB | Huawei, Qualcomm Incorporated, China Unicom |
R3-223207 | Correction on release-with-redirect in anchor gNB | Huawei, Qualcomm Incorporated, China Unicom |
R3-223208 | Further consideration on flexible gNB ID | Huawei, Qualcomm Incorporated, ZTE |
R3-223209 | Measurement Amount on NRPPa | Huawei |
R3-223210 | CR to 38.455 on Measurement Amount | Huawei |
R3-223211 | CR to 38.473 on Measurement Amount | Huawei |
R3-223212 | Discussion on user consent for UE location information | Huawei, BT, Orange |
R3-223213 | Correction to user consent for UE location information | Huawei, BT, Orange |
R3-223214 | Correction to user consent for UE location information | Huawei, BT, Orange |
R3-223215 | Correction to user consent for UE location information | Huawei, BT, Orange |
R3-223216 | Correction to user consent for UE location information | Huawei, BT, Orange |
R3-223217 | Clarification on SRB duplication for TS38.470 (R16) | ZTE |
R3-223218 | Clarification on SRB duplication for TS38.470 (R17) | ZTE |
R3-223231 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
R3-223232 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
R3-223233 | Discussion on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
R3-223243 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom |
R3-223244 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom |
R3-223260 | Clarify the UE Security Capabilities IE not applicable to non-3GPP access | Nokia, Nokia Shanghai Bell, Huawei, BT |
R3-223261 | Clarify the UE Security Capabilities IE not applicable to non-3GPP access | Nokia, Nokia Shanghai Bell, Huawei, BT |
R3-223281 | RAT/Frequency Selection Priority handling in inter system handover | KDDI Corporation |
R3-223287 | Secondary RAT Data Usage Report Co-ordination for MR-DC | Reliance JIO, Radisys, ZTE, NTT Docomo, CATT, Deutsche Telekom |
R3-223288 | Secondary RAT Data Usage Report Co-ordination for EN-DC | Reliance JIO, Radisys, ZTE, NTT Docomo, CATT, Deutsche Telekom |
R3-223289 | Discussion on Secondary RAT Data Usage Report Co-ordination for ENDC and MRDC | Reliance JIO, Radisys |
R3-223291 | Support flexible I-RNTI Decode [RRCInactive] | Radisys, Reliance JIO, Nokia, Nokia Shanghai Bell, ZTE |
R3-223336 | Correction of indirect data forwarding for SA to EN-DC handover | Huawei, CATT, Samsung, Deutsche Telekom |
R3-223337 | Correction of indirect data forwarding for SA to EN-DC handover | Huawei, CATT, Samsung, Deutsche Telekom |
R3-223390 | Correction on IAB-DU Cell Resource Configuration | Huawei, Lenovo |
R3-223391 | Correction on IAB-DU Cell Resource Configuration | Huawei, Lenovo |
R3-223392 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223393 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223394 | F1AP corrections for Load Balancing in Rel 16 | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223395 | F1AP corrections for Load Balancing in Rel 17 | Ericsson, Deutsche Telekom, Qualcomm Incorporated |
R3-223397 | CR to TS38.473 Correction on PC5 DRX parameters for NR V2X | ZTE Corporation |
R3-223402 | CR on clarification scope on Iuant modem | Ericsson |
R3-223403 | CR on clarification scope on Iuant modem | Ericsson |
R3-223404 | CR on clarification scope on Iuant modem | Ericsson |
R3-223407 | Discussion on Flexible gNB-ID disambiguation | Ericsson, Verizon, Bell Mobility, China Telecom, TELUS |
R3-223408 | LS on Flexible Global RAN Node ID | Ericsson, Verizon, Bell Mobility, China Telecom, TELUS |
R3-223421 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson |
R3-223422 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson |
R3-223435 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223436 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223437 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223438 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223460 | Correction on Initial UE Context Setup Failure | Huawei, Deutsche Telekom, Orange |
R3-223461 | Correction on Initial UE Context Setup Failure | Huawei, Deutsche Telekom, Orange |
R3-223462 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell |
R3-223463 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell |
R3-223464 | Retrieve UE context for NPN only cell | Huawei, Deutsche Telekom, Orange, Nokia, Nokia Shanghai Bell |
R3-223488 | Correction of Last Visited NG-RAN Cell Information | Huawei, Qualcomm, China Telecom, China Unicom |
R3-223489 | Correction of Last Visited NG-RAN Cell Information | Huawei, Qualcomm, China Telecom, China Unicom |
R3-223490 | Correction of Last Visited NG-RAN Cell Information | Huawei, Qualcomm, China Telecom, China Unicom |
R3-223527 | Discussion on retainability issue for DC scenario | CATT, China Telecom |
R3-223528 | Support of count on QoS flow released in session for DC case | CATT, China Telecom |
R3-223564 | Discussion on F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
R3-223565 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
R3-223592 | Supporting the disaster roaming information | Huawei, Orange, China Unicom |
R3-223593 | Supporting the disaster roaming information | Huawei, Orange, China Unicom |
R3-223594 | Supporting the disaster roaming information | Huawei, Orange, China Unicom |
R3-223595 | SIB Issues Rel-16 | Nokia, Nokia Shanghai Bell |
R3-223596 | SIB Issues Rel-17 | Nokia, Nokia Shanghai Bell |
R3-223598 | gNB-CU and gNB-DU Name in Configuration Update Procedures | Nokia, Nokia Shanghai Bell |
R3-223599 | gNB-CU and gNB-DU Name in Configuration Update Procedures | Nokia, Nokia Shanghai Bell |
R3-223600 | Discussion on Priority Call-back | Nokia, Nokia Shanghai Bell |
R3-223609 | Priority Call-back Indication | Nokia, Nokia Shanghai Bell |
R3-223625 | Correction to 38.300 for UE history information (R16) | CATT |
R3-223626 | Correction to 38.300 for UE history information (R17) | CATT |
R3-223656 | Discussion on Report Amount for MDT M4, M5, M6, M7 measurements | ZTE, China Telecom, Samsung, CATT |
R3-223657 | CR for 38.413 on MDT report amount | ZTE, China Telecom, Samsung, CATT |
R3-223658 | CR for 38.423 on MDT report amount | ZTE, China Telecom, Samsung, CATT |
R3-223659 | CR for 38.473 on MDT report amount | ZTE, China Telecom, Samsung, CATT |
R3-223660 | CR for 37.483 on MDT report amount | ZTE, China Telecom, Samsung, CATT |
R3-223666 | Correction to Area Scope Configuration and Frequency Band Info in MDT Configuration (REL-16) | CATT, HUAWEI, ZTE, Samsung |
R3-223667 | Correction to Frequency Band Info in MDT Configuration (REL-17) | CATT, HUAWEI, ZTE, Samsung |
R3-223676 | Clarification of DU Early Identification capability for MPS | Peraton Labs, CISA ECD, AT&T |
R3-223720 | CB: # 8_MDTReportAmount - Summary of email discussion | ZTE - moderator |
R3-223721 | CB: # 9_Flexible_gNBID - Summary of email discussion | Qualcomm - moderator |
R3-223722 | CB: # 10_IABCorr - Summary of email discussion | Huawei - moderator |
R3-223723 | CB: # 11_PositionCorr - Summary of email discussion | Nokia - moderator |
R3-223726 | CB: # 7_UserConsent - Summary of email discussion | Apple - moderator |
R3-223734 | CR on clarification scope on Iuant modem | Ericsson |
R3-223735 | CR on clarification scope on Iuant modem | Ericsson |
R3-223736 | CR on clarification scope on Iuant modem | Ericsson |
R3-223741 | Discussion on Flexible gNB-ID disambiguation | Ericsson, Verizon, Bell Mobility, China Telecom, TELUS, Samsung |
R3-223744 | CB: # 51_DiscardTimer - Summary of email discussion | China Telecom - moderator |
R3-223745 | CB: # 52_EHC - Summary of email discussion | Huawei - moderator |
R3-223747 | CR to TS38.473 Correction on PC5 DRX parameters for NR V2X | ZTE Corporation |
R3-223748 | CB: # 54_SIB15 - Summary of email discussion | Huawei - moderator |
R3-223749 | SIB Issues Rel-16 | Nokia, Nokia Shanghai Bell |
R3-223750 | SIB Issues Rel-17 | Nokia, Nokia Shanghai Bell |
R3-223751 | CB: # 55_PriorityCall - Summary of email discussion | Nokia - moderator |
R3-223752 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell, China Telecom, Ericsson, Intel Corporation, ZTE |
R3-223753 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell, China Telecom, Ericsson, Intel Corporation, ZTE |
R3-223754 | Correction of UL-AoA container extension | Ericsson |
R3-223755 | Correction of UL-AoA container extension | Ericsson |
R3-223758 | CB: # 56_GapConfig - Summary of email discussion | Huawei - moderator |
R3-223759 | Correction to Area Scope Configuration and Frequency Band Info in MDT Configuration (REL-16) | CATT, HUAWEI, ZTE, Samsung |
R3-223760 | Correction to Frequency Band Info in MDT Configuration (REL-17) | CATT, HUAWEI, ZTE, Samsung |
R3-223761 | Correction of data forwarding for SA to EN-DC handover | Huawei, CATT, Samsung, Deutsche Telekom |
R3-223762 | CB: # 57_PDCPCount - Summary of email discussion | NEC - moderator |
R3-223763 | CB: # 58_NPNOnlyCell - Summary of email discussion | Huawei -moderator |
R3-223764 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson |
R3-223765 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson |
R3-223766 | CB: # 60_F1UDelay - Summary of email discussion | Samsung - moderator |
R3-223767 | gNB-CU and gNB-DU Name in Configuration Update Procedures | Nokia, Nokia Shanghai Bell |
R3-223768 | gNB-CU and gNB-DU Name in Configuration Update Procedures | Nokia, Nokia Shanghai Bell |
R3-223769 | SIB Issues Rel-16 | Nokia, Nokia Shanghai Bell |
R3-223770 | SIB Issues Rel-17 | Nokia, Nokia Shanghai Bell |
R3-223774 | Correction on IAB-DU Cell Resource Configuration | Huawei, Lenovo |
R3-223775 | Correction on IAB-DU Cell Resource Configuration | Huawei, Lenovo |
R3-223776 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223777 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223799 | CR to 38.455 on Measurement Amount | Huawei |
R3-223800 | CR to 38.473 on Measurement Amount | Huawei |
R3-223802 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE, Ericsson |
R3-223804 | LS on Flexible Global RAN Node ID | Ericsson |
R3-223809 | CB: # 9_Flexible_gNBID - Summary of email discussion | Qualcomm - moderator |
R3-223810 | LS on Flexible Global RAN Node ID | Ericsson |
R3-223835 | Supporting the disaster roaming information [MINT] | Huawei, Orange, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell |
R3-223836 | Supporting the disaster roaming information [MINT] | Huawei, Orange, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell |
R3-223870 | [DRAFT] Reply LS on the user consent for trace reporting | Apple |
R3-223881 | Reply LS on Report Amount for M4, M5, M6 and M7 measurements | ZTE |
R3-223883 | LS on Flexible Global RAN Node ID | Ericsson |
R3-223905 | R16 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
R3-223906 | R17 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
R3-223920 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223921 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223922 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223923 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-223928 | LS on NPN only cell | Huawei |
R3-223935 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei |
R3-223936 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei |
R3-223937 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC |
R3-223938 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC |
R3-223940 | (Rel-16) CR to SSB subcarrier spacing | Samsung |
R3-223941 | (Rel-17) CR to SSB subcarrier spacing | Samsung |
R3-223966 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223967 | Trace Activation IE support for the Retrieve UE Context procedure | Ericsson, Nokia, Nokia Shanghai Bell |
R3-223968 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223969 | Correction for IAB PSK generation | Huawei, Samsung |
R3-223970 | Correction to Frequency Band Info in MDT Configuration (REL-17) | CATT, HUAWEI, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Ericsson |
R3-223995 | Correction to Area Scope Configuration and Frequency Band Info in MDT Configuration (REL-16) | CATT, HUAWEI, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Ericsson |
R3-224010 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE |
R3-224014 | CR to TS38.473 Correction on PC5 DRX parameters for NR V2X | ZTE Corporation |
R3-224022 | Correction of UL-AoA container extension | Ericsson |
R3-224023 | CR to 38.455 on Measurement Amount | Huawei, Ericsson |
R3-224024 | CR to 38.473 on Measurement Amount | Huawei, Ericsson |
R3-224025 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-224026 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-224027 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-224028 | Correction for PRS Muting | Nokia, Nokia Shanghai Bell |
R3-224057 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Intel Corporation, Verizon Wireless, Huawei, CMCC, KDDI |
R3-224058 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell, China Telecom, Ericsson, Intel Corporation, ZTE |
R3-224063 | LS on interFrequencyConfig-NoGap-r16 signalling | Ericsson |
R3-224068 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE |
R3-224070 | LS on Flexible Global RAN Node ID | Ericsson, Verizon, Bell Mobility, China Telecom, TELUS |
R3-224072 | Reply LS on the user consent for trace reporting | Ericsson |
R3-224084 | Reply LS on Report Amount for M4, M5, M6 and M7 measurements | ZTE |
R3-224085 | Support for handling unknown length of gNB identifier [FLEX_gNB_Len] | Qualcomm Incorporated, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
R3-224086 | R16 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
R3-224087 | R17 CR on Extended PDCP Discard Timer over E1 interface | China Telecom, ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
R3-224091 | CR to 38.455 on Measurement Amount | Huawei, Ericsson |
R3-224092 | CR to 38.473 on Measurement Amount | Huawei, Ericsson |
R3-224095 | Correction on EHC parameters | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell, China Telecom, Ericsson, Intel Corporation, ZTE |
R3-224108 | CR to 38.455 on Measurement Amount | Huawei, Ericsson |
R3-224109 | CR to 38.473 on Measurement Amount | Huawei, Ericsson |
TDoc | Title | Source |
---|---|---|
R3-223670 | Updated Work plan for RAN slicing WI | CMCC |
TDoc | Title | Source |
---|---|---|
R3-223011 | Reply LS on Slice list and priority information for cell reselection | RAN2 |
R3-223035 | Reply LS on Slice list and priority information for cell reselection | SA2 |
R3-223090 | (TP for TS 38.413) Support slice grouping over NGAP | NTT DOCOMO INC. |
R3-223091 | (TP for TS 38.423) Support slice grouping over XnAP | NTT DOCOMO INC. |
R3-223161 | Correction of Slice Group Configuration | Nokia, Nokia Shanghai Bell |
R3-223162 | Correction of Slice Group Configuration | Nokia, Nokia Shanghai Bell |
R3-223163 | Correction of Slice Group Configuration | Nokia, Nokia Shanghai Bell |
R3-223409 | Discussion and way forward on Network Slice AS Groups | Ericsson |
R3-223410 | Support for slice grouping over NGAP | Ericsson |
R3-223411 | Support for slice grouping over F1AP | Ericsson |
R3-223412 | Reply LS to Reply LS on Slice list and priority information for cell reselection | Ericsson |
R3-223465 | Supporting network slice AS group | Huawei |
R3-223466 | Supporting network slice AS group | Huawei |
R3-223467 | Supporting network slice AS group | Huawei |
R3-223468 | Supporting network slice AS group | Huawei |
R3-223515 | Discussion on Supporting for NSAG | CATT |
R3-223516 | CR to 38.413 for Supporting for NSAG | CATT |
R3-223517 | CR to 38.423 for Supporting for NSAG | CATT |
R3-223518 | CR to 38.473 for Supporting for NSAG | CATT |
R3-223549 | On support of slice grouping and slice priority | Samsung |
R3-223550 | Correction on the slice group mapping for RAN Slicing (NGAP) | Samsung |
R3-223551 | Correction on the slice group mapping for RAN Slicing (F1AP) | Samsung |
R3-223581 | Impact on Slice Grouping and Slice Priority | ZTE |
R3-223582 | Enable configuration of Network Slice Groups(NGAP) | ZTE |
R3-223583 | Enable configuration of Network Slice Groups(F1AP) | ZTE |
R3-223584 | Enable configuration of Network Slice Groups(XnAP) | ZTE |
R3-223611 | Discussion on NSAG information | LG Electronics |
R3-223617 | Support of NSAG in NG interface | LG Electronics |
R3-223618 | Support of NSAG in Xn interface | LG Electronics |
R3-223620 | Support of NSAG in F1 interface | LG Electronics |
R3-223646 | Discussion on slice grouping and slice priority | CMCC |
R3-223647 | Enabling configuration of Network Slice AS Group | CMCC |
R3-223648 | Enabling configuration of Network Slice AS Group | CMCC, Huawei |
R3-223649 | Enabling configuration of Network Slice AS Group | CMCC |
R3-223724 | CB: # Slice1_Group_Priority - Summary of email discussion | CMCC - moderator |
R3-223792 | CB: # Slice1_Group_Priority - Summary of email discussion | CMCC - moderator |
R3-223805 | Supporting network slice AS group | Huawei |
R3-223822 | Correction of Slice Group Configuration | Nokia, Nokia Shanghai Bell |
R3-223973 | Enable configuration of Network Slice Groups(XnAP) | ZTE |
R3-224051 | Correction of Slice Group Configuration | Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson |
R3-224052 | Supporting network slice AS group | Huawei, LG Electronics, CATT, CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
R3-223061 | LS on Response to LS on Enhancement of RAN Slicing from RAN3 | SA5 |
R3-223405 | Reply LS to Reply LS on Clarification of SCG outside RA for slicing | Ericsson |
R3-223469 | Correction of the presence of UE-Slice-MBR | Huawei, CATT, CMCC |
R3-223470 | Correction of the criticality of UE-Slice-MBR | Huawei, CATT, CMCC |
R3-223725 | CB: # Slice2_Others - Summary of email discussion | Ericsson - moderator |
R3-223778 | Correction of the presence of UE-Slice-MBR | Huawei, CATT, CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
R3-223820 | CB: # Slice2_Others - Summary of email discussion | Ericsson - moderator |
R3-223942 | Correction of the criticality of UE-Slice-MBR | Huawei, CATT, CMCC, Nokia, Nokia Shanghai Bell |