3GPP TDocs (written contributions) at meeting
Meeting: R3-99b - 2018-04-16 to 2018-04-20, Sanya
meeting id: R3-99b (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑181600 | RAN3-99Bis meeting Agenda | Chairman (Ericsson) | imported from 3GU |
| R3‑181601 | RAN3-99 meeting Report | MCC | imported from 3GU |
| R3‑181602 | NGMN “RAN functional split and x-haul” work item | NGMN Alliance work item “RAN functional split and x-haul” | imported from 3GU |
| R3‑181603 | Reply LS on N2 and N3 interfaces for Non-3GPP access network | 3GPP CT1, Nokia | imported from 3GU |
| R3‑181604 | LS on Service Based interface for PWS | 3GPP CT1, On2many | imported from 3GU |
| R3‑181605 | LS on TAI and forbidden TAI list for 5GS | 3GPP CT1, Intel | imported from 3GU |
| R3‑181606 | Reply LS on defining a new GTP Extension Header for the 5GS Container | 3GPP CT4, Nokia | imported from 3GU |
| R3‑181607 | LS on Clarification on GTP-U ""Long PDCP PDU Number"" extension header | 3GPP CT4, NTT Docomo | imported from 3GU |
| R3‑181608 | LS on NR UE feature list | 3GPP RAN1, AT&T | imported from 3GU |
| R3‑181609 | Reply LS to Reply LS on UE differentiation for Rel-15 NB-IoT | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑181610 | Response LS on optionality of the UE procedures related to RRC Inactive | 3GPP RAN2, Samsung | imported from 3GU |
| R3‑181611 | LS on UE differentiation in NB-IoT | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑181612 | LS on RAN2 agreements for euCA | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑181613 | Reply LS on NR interworking with GSM and UMTS | 3GPP RAN4, Huawei | imported from 3GU |
| R3‑181614 | LS on UE feature list | 3GPP RAN4, Intel | imported from 3GU |
| R3‑181615 | LS on secured Signalling-only connection | 3GPP TSG RAN, Nokia | imported from 3GU |
| R3‑181616 | LS on NR UE feature list | 3GPP TSG RAN, NTT Docomo | imported from 3GU |
| R3‑181617 | LS on optimisation of UE capability signalling | 3GPP TSG RAN, Vodafone | imported from 3GU |
| R3‑181618 | LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | 3GPP SA2, Nokia | imported from 3GU |
| R3‑181619 | LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑181620 | Reply LS on supporting non-3GPP access in NGAP | 3GPP SA2, Nokia | imported from 3GU |
| R3‑181621 | Reply LS on introducing explicit per-UE TNLA binding release in NGAP | 3GPP SA2, Nokia | imported from 3GU |
| R3‑181622 | LS reply to LS from RAN WG2: LS on QoS | 3GPP SA2, Ericsson | imported from 3GU |
| R3‑181623 | LS on 5G-S-TMSI code space | 3GPP SA2, Ericsson | imported from 3GU |
| R3‑181624 | LS on Allowed NSSAI indication to RAN | 3GPP SA2, Ericsson | imported from 3GU |
| R3‑181625 | LS response on User Plane Security Policy | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑181626 | LS on UP Security Policy | 3GPP SA3, Ericsson | imported from 3GU |
| R3‑181627 | LS reply on required information for NSA on X2 | 3GPP RAN4, Nokia | imported from 3GU |
| R3‑181628 | LS on Support User Plane Encryption in UP security policy | 3GPP SA3, Huawei | imported from 3GU |
| R3‑181629 | LS on INOBEAR | 3GPP SA2, Samsung | imported from 3GU |
| R3‑181630 | UE radio capability enquiry | Huawei | imported from 3GU |
| R3‑181631 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson | imported from 3GU |
| R3‑181632 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson | imported from 3GU |
| R3‑181633 | [Draft] Reply LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection | Huawei | imported from 3GU |
| R3‑181634 | Further Consideration on Early Data Transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181635 | Introduction of early data transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181636 | Introduction of Early Data Transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181637 | [Draft] Reply LS on EDT procedures and AS NAS interaction | Huawei | imported from 3GU |
| R3‑181638 | Consideration on UE differentiation | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181639 | Introduction of UE differentiation | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181640 | Introduction of UE differentiation | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑181641 | [DRAFT] Reply LS on UE differentiation for Rel-15 NB-IoT | Huawei | imported from 3GU |
| R3‑181642 | Signalling procedures for broadcasting of assistance data | Huawei | imported from 3GU |
| R3‑181643 | Introduction of signalling procedures for broadcasting of assistance data | Huawei | imported from 3GU |
| R3‑181644 | Discussion on assistance data transmission | Huawei | imported from 3GU |
| R3‑181645 | Assistance data transmission over LPPa | Huawei | imported from 3GU |
| R3‑181646 | Differentiation of LTE-M (eMTC) traffic | Huawei | imported from 3GU |
| R3‑181647 | Introduction of LTE-M (eMTC) traffic Differentiation | Huawei | imported from 3GU |
| R3‑181648 | [DRAFT] Reply LS LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | Huawei | imported from 3GU |
| R3‑181649 | Aerial Vehicles Identification | Huawei | imported from 3GU |
| R3‑181650 | Introduction of Aerial Vehicles Identification | Huawei | imported from 3GU |
| R3‑181651 | Introduction of Aerial Vehicles Identification | Huawei | imported from 3GU |
| R3‑181652 | Correction on the same terminology of “Split SRB” in TS36.423 | ZTE | imported from 3GU |
| R3‑181653 | Correction on same terminology of split SRB in TS38.423 | ZTE | imported from 3GU |
| R3‑181654 | Correction on Split SRB configuration | ZTE | imported from 3GU |
| R3‑181655 | Correction of Split SRB configuration in TS36.423 | ZTE | imported from 3GU |
| R3‑181656 | Correction of Split SRB configuration in TS38.423 | ZTE | imported from 3GU |
| R3‑181657 | Clarifications on SgNB initiated SgNB Modification procedure | ZTE | imported from 3GU |
| R3‑181658 | Correction on SgNB initiated SgNB Modification procedure in TS37.340 | ZTE | imported from 3GU |
| R3‑181659 | S-RLF related information transmission in TS37.340 | ZTE | imported from 3GU |
| R3‑181660 | S-RLF related information transmission in TS38.423 | ZTE | imported from 3GU |
| R3‑181661 | Correction of UL link configuration in TS36.423 | ZTE | imported from 3GU |
| R3‑181662 | Discussion on PDU session resource setup | ZTE | imported from 3GU |
| R3‑181663 | Discussion on splitting PDU session modification | ZTE | imported from 3GU |
| R3‑181664 | S1/X2 Signaling Support of UAV Subscription information | ZTE | imported from 3GU |
| R3‑181665 | Correction on the same terminology of “Split SRB” in TS36.423 | ZTE | imported from 3GU |
| R3‑181666 | Correction of Split SRB configuration in TS36.423 | ZTE | imported from 3GU |
| R3‑181667 | Correction of UL link configuration in TS36.423 | ZTE | imported from 3GU |
| R3‑181668 | Signaling 5QI in QoS profile of TS38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181669 | Signaling 5QI in QoS Profile of TS TS 38.423 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181670 | Handling of notification control in TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑181671 | Handling of notification control in TS 38.423 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181672 | (TP for NR BL CR for TS 38.473) Handling of notification control in TS 38.473 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181673 | Reference QoS profile indication from 5GC | Nokia, Nokia Shanghai Bell, Intel Corporation, LG Electronics Inc., Huawei, CMCC | imported from 3GU |
| R3‑181674 | Reply LS on default DRB establishment for PDU session | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181675 | Design overview of PDU Session UP protocol | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181676 | Stage 3 for registration with AMF re-allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181677 | Frequency prioritization based on slices | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181678 | Reply LS regarding RAN support for Network Slicing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181679 | Signalling of allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181680 | Reply LS on Allowed NSSAI indication to RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181681 | Signalling failed S-NSSAI(s) in Path Switch procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181682 | Correction of slice temporarily unavailable | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181683 | Further Correction on Session AMBR for MR-DC@5GC | ZTE | imported from 3GU |
| R3‑181684 | Discussion on Data volume reporting@Duplication transmission | ZTE | imported from 3GU |
| R3‑181685 | Further Discussion and 38.413 pCR on Notification Procedure | ZTE | imported from 3GU |
| R3‑181686 | Further Discussion and 38.413 pCR on PDU SESSION RESOURCE MODIFY INDICATION | ZTE | imported from 3GU |
| R3‑181687 | Further Discussion and 38.300 TP on Slice Aware Mobility | ZTE | imported from 3GU |
| R3‑181688 | Further Discussion and 38.413 pCR on PDU Session Security Policy Download | ZTE | imported from 3GU |
| R3‑181689 | Further Discussion and 38.423 pCR on PDU Session Security Policy Download | ZTE | imported from 3GU |
| R3‑181690 | Further Discussion on NG-RAN Security Policy Enforcement | ZTE | imported from 3GU |
| R3‑181691 | Guarantee the UE Max Data Rate for Integrity Protection | ZTE | imported from 3GU |
| R3‑181692 | Discussion on the DC based enhancement for aerial vehicles | ZTE | imported from 3GU |
| R3‑181693 | Draft LS on Ensuring UE Capability of Maximum Data Rate for Integrity Operation | ZTE | imported from 3GU |
| R3‑181694 | Discussion and 38.413 pCR on xxx NG-RAN Node to xxx NG-RAN Node Transparent Container | ZTE | imported from 3GU |
| R3‑181695 | Discussion and 38.423 pCR on Xn Mobility with RRC Context | ZTE | imported from 3GU |
| R3‑181696 | Further Discussion and 38.423 pCR on Setting RLC Mode | ZTE | imported from 3GU |
| R3‑181697 | Further Discussion and 38.423 pCR on MR-DC@5GC Operations | ZTE | imported from 3GU |
| R3‑181698 | Discussion and 38.413 pCR on Security Context | ZTE | imported from 3GU |
| R3‑181699 | Discussion and 38.413 pCR on NG Handover Type | ZTE | imported from 3GU |
| R3‑181700 | Discussion and 38.423 pCR on Security Information | ZTE | imported from 3GU |
| R3‑181701 | Further Discussion on MR-DC Coexisting with INACTIVE State | ZTE | imported from 3GU |
| R3‑181702 | Correction of QoS Flow to DRB Mapping in MR-DC@5GC in TS37.340 | ZTE | imported from 3GU |
| R3‑181703 | Stage3 pCR for SN Initiated SN Modification Procedure | ZTE | imported from 3GU |
| R3‑181704 | Further Discussion and TP on XXX Cell Resource Sharing | ZTE | imported from 3GU |
| R3‑181705 | Further Discussion and TS38.401 TP on Multi-Connectivity with DualMultiple gNB-DUs | ZTE | imported from 3GU |
| R3‑181706 | X2 partial reset (bulk release) for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181707 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| R3‑181708 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| R3‑181709 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| R3‑181710 | Clarification of the interactions with the UE Context Release | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181711 | Clarification of the usage of SN Status Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181712 | Clarification of the cells used in the SgNB Addition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181713 | Reason for SgNB Addition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181714 | Addiiton of the full config indicator | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181715 | Clarification of PDU handling in case of radio outage | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181716 | Enabling future extendability of the RAN Container | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑181717 | Enabling future extendability of the Xw RAN Container | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑181718 | Clarification of the cells used in the SgNB Addition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181719 | Registration with AMF Reallocation based on Slice Suitability | Interdigital, ZTE | imported from 3GU |
| R3‑181720 | Skeleton of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181721 | TP for general sections of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181722 | TP for extension mechanisms of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181723 | TP for procedures of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181724 | TP for Frame Type of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181725 | Further discussion on QoS handling over F1 | ZTE Corporation | imported from 3GU |
| R3‑181726 | (TP for SA BL CR)Stage2 CR for QoS handling over F1 | ZTE Corporation | imported from 3GU |
| R3‑181727 | (TP for SA BL CR) Update on QoS information transfer for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑181728 | Discussion on UE Context Setup without DRB | ZTE Corporation | imported from 3GU |
| R3‑181729 | TP on Initial Context Setup for TS38.413 | ZTE Corporation | imported from 3GU |
| R3‑181730 | Corrections on UE Context Setup for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑181731 | [DRAFT] LS on UE Registration without a PDU session setup | ZTE Corporation | imported from 3GU |
| R3‑181732 | Bearer Context Modification over E1 interface for TS38.460 | ZTE Corporation | imported from 3GU |
| R3‑181733 | Bearer Context Modification over E1 interface for TS38.463 | ZTE Corporation | imported from 3GU |
| R3‑181734 | Early data transmission impact on S1 interface | ZTE Corporation | imported from 3GU |
| R3‑181735 | Discussion on PDCP COUNT wrap around | ZTE Corporation | imported from 3GU |
| R3‑181736 | Discussion on E1 interface setup | ZTE Corporation | imported from 3GU |
| R3‑181737 | (TP for SA BL CR)Discussion on Access Control for F1 interface | ZTE Corporation | imported from 3GU |
| R3‑181738 | Further discussion on assistance information for DL duplication (de)activation | ZTE Corporation | imported from 3GU |
| R3‑181739 | (de)activation of duplication over F1 for TS38.401 | ZTE Corporation | imported from 3GU |
| R3‑181740 | (de)activation of duplication over F1 for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑181741 | Centralized Retransmission in EN-DC for TS38.401 | ZTE Corporation | imported from 3GU |
| R3‑181742 | Consideration on the enhancement for UL AMBR | ZTE Corporation | imported from 3GU |
| R3‑181743 | enhancement for UL AMBR for TS38.401 | ZTE Corporation | imported from 3GU |
| R3‑181744 | enhancement for UL AMBR for TS37.340 | ZTE Corporation | imported from 3GU |
| R3‑181745 | Discussion on PWS in CU-DU deployment | ZTE Corporation | imported from 3GU |
| R3‑181746 | (TP for SA BL CR)Further discussion on Load Management | ZTE Corporation | imported from 3GU |
| R3‑181747 | Frequency priorities in case of Slicing | ZTE Corporation | imported from 3GU |
| R3‑181748 | NW Slice Temporarily Unavailable | ZTE Corporation | imported from 3GU |
| R3‑181749 | TP for NR BL CR for TS 38.300 Handling of UE Context release | CATT | imported from 3GU |
| R3‑181750 | TP for NR BL CR for TS 38.423 on UE Context Release | CATT | imported from 3GU |
| R3‑181751 | TP for NR BL CR for TS 38.300 RAN Paging priority | CATT | imported from 3GU |
| R3‑181752 | TP for NR BL CR for TS 38.423 on RAN Paging priority | CATT | imported from 3GU |
| R3‑181753 | TP for NR BL CR for TS 38.300 on RRC state enquiry and report | CATT | imported from 3GU |
| R3‑181754 | TP for NR BL CR for TS 38.413 on RRC state report | CATT | imported from 3GU |
| R3‑181755 | LS on RRC State report | CATT | imported from 3GU |
| R3‑181756 | Considerations on startup procedure for L2 IAB architecture | CATT | imported from 3GU |
| R3‑181757 | Considerations on bearer management for L2 IAB architecture | CATT | imported from 3GU |
| R3‑181758 | Considerations on Network topology and Route Selection | CATT | imported from 3GU |
| R3‑181759 | Discussion on Configuration of Dedicated Frequency Priority for Network Slicing Regardless of RFSP or Allowed NSSAI | OPPO | imported from 3GU |
| R3‑181760 | UE Context Fetch Procedure in Xn | BEIJING SAMSUNG TELECOM R&D | imported from 3GU |
| R3‑181761 | Consideration on GTP-U "Long PDCP PDU Number" extension header | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181762 | [draft]reply LS on Clarification on GTP-U "Long PDCP PDU Number" extension header | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181763 | Correction on UL blockage | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181764 | CR to TS38.401 on UL blockage | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181765 | CR to TS38.425 on UL blockage | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181766 | Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑181767 | CR for Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑181768 | Further consideration on data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181769 | CR for Clarification of data volume reporting on TS37.340 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181770 | CR for Clarification of data volume reporting on TS38.401 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181771 | CR for Clarification of start or end timing for data volume reporting on TS36.413 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181772 | Clarification of start or end timing for data volume reporting on TS36.423 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181773 | [draft]LS on Secondary RAT data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181774 | Clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181775 | CR to TS38.472 on clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181776 | CR to TS36.412 on clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181777 | CR to TS36.422 on clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181778 | CR to TS38.412 on clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181779 | CR to TS38.422 on clarification of SCTP association establishment | NTT DOCOMO, INC., Fujitsu | imported from 3GU |
| R3‑181780 | Further consideration on data existence indication for split bearer | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181781 | CR on data existence indication for split bearer | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181782 | Maintaining the bearer type on wrap-around | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181783 | Further consideration on Load management | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181784 | Way forward on TNL Address Discovery for Option 3 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑181785 | Discussion on support of delta configruation during SN change procedure | CATT | imported from 3GU |
| R3‑181786 | CR to 36.423 on support of delta configuration during SN change procedure | CATT | imported from 3GU |
| R3‑181787 | Support of UE capability coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑181788 | CR to 37.340 on support of UE capability coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑181789 | CR to 36.423 on support of UE capability coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑181790 | CR to 37.340 on SgNB initiated SgNB Modification procedure | CATT | imported from 3GU |
| R3‑181791 | CR to 38.473 on intra-gNB-DU handover | CATT | imported from 3GU |
| R3‑181792 | Correction on DU to CU RRC information IE | CATT | imported from 3GU |
| R3‑181793 | CR to 38.473 on DU to CU RRC information IE | CATT | imported from 3GU |
| R3‑181794 | [Draft]LS on RRC Information from gNB-DU to gNB-CU | CATT | imported from 3GU |
| R3‑181795 | Discussion on support of PDCP Duplication | CATT | imported from 3GU |
| R3‑181796 | CR to 38.473 on PDCP Duplication | CATT | imported from 3GU |
| R3‑181797 | CR to 36.423 on PDCP Duplication | CATT | imported from 3GU |
| R3‑181798 | Removal of SCG change indication and introduction of PDCP data recovery request from MN to SN | CATT | imported from 3GU |
| R3‑181799 | Further Consideration on UE Context Management | CATT | imported from 3GU |
| R3‑181800 | CR to 38.473 on UE Context Management | CATT | imported from 3GU |
| R3‑181801 | (TP for NR BL CR for TS 38.470)QoS handling for CU-DU split | CATT | imported from 3GU |
| R3‑181802 | (TP for NR BL CR for TS 38.473)QoS handling for CU-DU split | CATT | imported from 3GU |
| R3‑181803 | Discussion on DL user data to DU | CATT | imported from 3GU |
| R3‑181804 | CR to 38.401 on DL user data to DU | CATT | imported from 3GU |
| R3‑181805 | CR to 38.425 on DL user data to DU | CATT | imported from 3GU |
| R3‑181806 | Remaining Issue on RRC Reconfiguration Complete Indicator | CATT | imported from 3GU |
| R3‑181807 | CR to 38.473 on RRC Reconfiguration complete indicator | CATT | imported from 3GU |
| R3‑181808 | TP for 38.423 on the presence of SN UL PDCP UP Address | CATT | imported from 3GU |
| R3‑181809 | (TP for NR BL CR for TS 38.300): Correction on AMF Identifier and AMF name | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181810 | TP for NGAP GUAMI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181811 | Discussion on supporting per-UE TNLA-binding release in NGAP | Nokia, Nokia Shanghai Bell, Intel Corporation, Verizon Wireless | imported from 3GU |
| R3‑181812 | TP for TS29.413 | Nokia, Nokia Shanghai Bell, Intel Corporation, China Telecom, KT Corp., Orange, AT&T, China Unicom | imported from 3GU |
| R3‑181813 | Discussion on Non-3GPP Access support in NGAP | Nokia, Nokia Shanghai Bell, Intel Corporation, China Telecom, KT Corp., Orange, AT&T, China Unicom | imported from 3GU |
| R3‑181814 | Reply LS on N2 and N3 interfaces for Non-3GPP access network | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181815 | Discussion on Overload Control in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181816 | TP for NGAP Overload Control | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181817 | Skeleton for TS 29.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181818 | Rapporteur update for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181819 | Retrieval of UE Radio Capability information after establishment of the logical S1-connection | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑181820 | Triggering UE capability info retrieval using DL NAS TRANSPORT (Stage 2) | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑181821 | Adaptation layer for the CU-DU split architecture and its location within the IAB donor node | Samsung R&D Institute UK | imported from 3GU |
| R3‑181822 | Triggering UE capability info retrieval using DL NAS TRANSPORT | Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑181823 | [DRAFT] Reply LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181824 | Trace support in NGAP | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑181825 | Trace support in XnAP | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑181826 | NG interface management procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181827 | Xn interface management procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181828 | Considerations on IAB deployment scenarios | ZTE Corporation | imported from 3GU |
| R3‑181829 | Discussion on IAB architectures | ZTE Corporation | imported from 3GU |
| R3‑181830 | Consideration on Topology Management for IAB | ZTE Corporation | imported from 3GU |
| R3‑181831 | Consideration on Routing Design for IAB | ZTE Corporation | imported from 3GU |
| R3‑181832 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99 on NR | NEC | imported from 3GU |
| R3‑181833 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99 on CPUP_Split | NEC | imported from 3GU |
| R3‑181834 | Baseline CR for June version of TS 36.413 covering agreements of RAN3#99 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181835 | Baseline CR for June version of TS 38.470 covering agreements of RAN3#99 | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑181836 | Baseline CR for June version of TS 38.473 covering agreements of RAN3#99 | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑181837 | Baseline CR for TS 37.340 (RAN3 part) covering agreements of RAN3 #NR adhoc 1801 and RAN3 #99 | ZTE | imported from 3GU |
| R3‑181838 | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181839 | Support of enhanced VoLTE performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑181840 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑181841 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑181842 | (TP for CPUP_Split BL CR for TS 38.401) Support of change of gNB-CU-UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181843 | (TP for CPUP_Split BL CR for TS 38.401) FFS resolution for E1 overall procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181844 | Definition of gNB-CU-CP/UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181845 | E1 non-UE associated functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181846 | E1 non-UE associated procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181847 | gNB-CU-UP notification function | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181848 | gNB-CU-UP notification procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181849 | Bearer Context Management procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181850 | Signalling transport for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181851 | (TP for NR BL CR for TS 38.401) User inactivity monitoring | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu | imported from 3GU |
| R3‑181852 | Discussion on Initial DDDS triggering | Nokia, Nokia Shanghai Bell, Verizon Wireless, KT, Vodafone | imported from 3GU |
| R3‑181853 | Correction on Initial DDDS triggering | Nokia, Nokia Shanghai Bell, Verizon Wireless, KT, Vodafone | imported from 3GU |
| R3‑181854 | Correction of S-NSSAI in NG | Samsung | imported from 3GU |
| R3‑181855 | Correction of S-NSSAI in Xn | Samsung | imported from 3GU |
| R3‑181856 | Addition of Cause Value | Samsung | imported from 3GU |
| R3‑181857 | DC establishment for PDCP Termination at SN | Samsung | imported from 3GU |
| R3‑181858 | Support of DRB offloading and QoS Flow offloading | Samsung | imported from 3GU |
| R3‑181859 | Homogeneous Issue in INOBEAR | Samsung | imported from 3GU |
| R3‑181860 | [draft] Reply LS on INOBEAR | Samsung | imported from 3GU |
| R3‑181861 | (TP for NR BL CR for TS 38.300) End marker handling | Samsung | imported from 3GU |
| R3‑181862 | Data forwarding for intra-system NG based HO | Samsung | imported from 3GU |
| R3‑181863 | Finalization data forwarding for Xn based handover | Samsung | imported from 3GU |
| R3‑181864 | (TP for NR BL CR for TS 38.300) RRC Inactive State Report | Samsung | imported from 3GU |
| R3‑181865 | Stage 3 TP on RRC Inactive Transition Report | Samsung | imported from 3GU |
| R3‑181866 | TP for TS 38.420 on Xn-U | Samsung | imported from 3GU |
| R3‑181867 | (TP for NR BL CR for TS 37.340) Add the Missing Functions of Xn-U | Samsung | imported from 3GU |
| R3‑181868 | TP for TS 38.415 PDU Session User Plane protocol | Samsung | imported from 3GU |
| R3‑181869 | PDCP duplication activation and deactivation over F1 | Samsung | imported from 3GU |
| R3‑181870 | CR for NSA on PDCP duplication activation and deactivation over F1 | Samsung | imported from 3GU |
| R3‑181871 | Packet duplication support over Xn | Samsung | imported from 3GU |
| R3‑181872 | DL/UL differentiation for radio link outage/resume | Samsung | imported from 3GU |
| R3‑181873 | CR for radio link outage/resume for DL and UL | Samsung | imported from 3GU |
| R3‑181874 | Discussions on user plane protocol for IAB | Samsung | imported from 3GU |
| R3‑181875 | Discussions on control plane protocol for IAB | Samsung | imported from 3GU |
| R3‑181876 | Discussion on supplementary uplink (SUL) addition and release for NSA | Samsung | imported from 3GU |
| R3‑181877 | CR for NSA on supplementary uplink (SUL) addition and release over F1 | Samsung | imported from 3GU |
| R3‑181878 | Packet duplication support over X2 | Samsung | imported from 3GU |
| R3‑181879 | CR for NSA on packet duplication support over X2 | Samsung | imported from 3GU |
| R3‑181880 | Introduction of additional cause values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181881 | Handling of protocol error for Transaction ID IE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181882 | Introduction of activation/deactivation indicator for gap | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181883 | Introduction of of UL/SUL indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181884 | (TP for NR BL CR for TS 38.473) QoS handling for SA over F1 | Nokia, Nokia Shanghai Bell, CMCC, Deutsche Telekom, KT, Verizon Wireless | imported from 3GU |
| R3‑181885 | (TP for NR BL CR for TS 38.470) QoS handling for SA over F1 | Nokia, Nokia Shanghai Bell, CMCC, Deutsche Telekom, KT, Verizon Wireless | imported from 3GU |
| R3‑181886 | End marker handling in HO and DC | Samsung | imported from 3GU |
| R3‑181887 | Issue on bearer type selection for NGEN-DC DRB options | LG Electronics, KT Corp. | imported from 3GU |
| R3‑181888 | Issues on Session AMBR for Option 7 family | LG Electronics, KT Corp. | imported from 3GU |
| R3‑181889 | TNL address discovery for EN-DC | LG Electronics, KT Corp. | imported from 3GU |
| R3‑181890 | UE-AMBR for EN-DC | LG Electronics, KT Corp. | imported from 3GU |
| R3‑181891 | On Allowed NSSAI in NG-RAN | China Telecommunications | imported from 3GU |
| R3‑181892 | On the reference QoS profile for default DRBs | China Telecommunications | imported from 3GU |
| R3‑181893 | Procedures for Security Support in CU-CP/UP Separation | LG Electronics, KT Corp. | imported from 3GU |
| R3‑181894 | Solution for early data transmission | ZTE Corporation | imported from 3GU |
| R3‑181895 | Slice aware Idle mode mobility | Huawei | imported from 3GU |
| R3‑181896 | Draft LS response on RAN support for NW slicing | Huawei | imported from 3GU |
| R3‑181897 | Correction on slice information exchange over NG | Huawei | imported from 3GU |
| R3‑181898 | Allowed NSSAI | Huawei, OPPO | imported from 3GU |
| R3‑181899 | Correction to attribute of S-NSSAI | Huawei | imported from 3GU |
| R3‑181900 | (TP for NR BL CR for TS 38.300): Correction to attribute of S-NSSAI | Huawei | imported from 3GU |
| R3‑181901 | Correction to attribute of S-NSSAI | Huawei | imported from 3GU |
| R3‑181902 | (TP for NR BL CR for TS 38.470): Correction to attribute of S-NSSAI | Huawei | imported from 3GU |
| R3‑181903 | (TP for NR BL CR for TS 38.473): Correction to attribute of S-NSSAI | Huawei | imported from 3GU |
| R3‑181904 | Available slice Information exchange for NG mobility | Huawei | imported from 3GU |
| R3‑181905 | Failure cause in path switch | Huawei | imported from 3GU |
| R3‑181906 | New cause value in HO procedures for slicing | Huawei | imported from 3GU |
| R3‑181907 | New cause value in HO procedures for slicing | Huawei | imported from 3GU |
| R3‑181908 | Temporarily unavailable slice | Huawei | imported from 3GU |
| R3‑181909 | Overload control | Huawei | imported from 3GU |
| R3‑181910 | NG reset | Huawei | imported from 3GU |
| R3‑181911 | (TP for NR BL CR for TS 38.473): Rapporteur update | Huawei | imported from 3GU |
| R3‑181912 | ASN.1 correction for BroadcastPLMNs-Item | Huawei | imported from 3GU |
| R3‑181913 | Further considerations of the PDCP Sequence COUNT | Vodafone Group Plc | imported from 3GU |
| R3‑181914 | PDCP COUNT expiry Alert Message | Vodafone Group Plc | imported from 3GU |
| R3‑181915 | Synchronisation of the RLC reset at the assisting node and the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181916 | Indication of the RLC Reset at the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181917 | Indication of the UL configuration and RLC Reset at the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181918 | Correction of the SeNB Reconfiguration Completion procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181919 | Correction of the S-NG-RAN node Reconfiguration Completion procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181920 | Clarification of the use of the desired buffer size | Nokia, Nokia Shanghai Bell, Verizon | imported from 3GU |
| R3‑181921 | LS regarding RAN support for NW slicing | 3GPP RAN2 | imported from 3GU |
| R3‑181922 | Further discussion on support of EDT in S1 | Qualcomm Incorporated | imported from 3GU |
| R3‑181923 | Introduction of Early Data Transmission | Qualcomm Incorporated | imported from 3GU |
| R3‑181924 | Reply LS on EDT procedures and AS NAS interaction | Qualcomm Incorporated | imported from 3GU |
| R3‑181925 | UE-AMBR enforcement | Qualcomm Incorporated | imported from 3GU |
| R3‑181926 | (TP for NR BL CR for TS 38.425): Radio link outage feedback and out-of-order received PDUs | Qualcomm Incorporated | imported from 3GU |
| R3‑181927 | TNL Association handling updates | Qualcomm Incorporated | imported from 3GU |
| R3‑181928 | AMF Overload function support | Qualcomm Incorporated | imported from 3GU |
| R3‑181929 | Adding SCTP termination to context retrieval | Qualcomm Incorporated | imported from 3GU |
| R3‑181930 | Correction of abnormal conditions for EN-DC security algorithm selection | Qualcomm Incorporated | imported from 3GU |
| R3‑181931 | Handling TAI restrictions in EN-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑181932 | Support of extended TAC in Roaming and Access Restrictions for EN-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑181933 | Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | Qualcomm Incorporated | imported from 3GU |
| R3‑181934 | (TP for NR BL CR for TS 38.300): Stage 2 Handling of Remaining DL Class 1 Signalling | Qualcomm Incorporated | imported from 3GU |
| R3‑181935 | Stage 3 NGAP Signalling for RRC_INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑181936 | (TP for NR BL CR for TS 37.340): Support of MR-DC with RRC INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑181937 | Support of MR_DC with RRC_INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑181938 | Reply LS on size of RANAC | Qualcomm Incorporated | imported from 3GU |
| R3‑181939 | (TP for NR BL CR for TS 38.300): Use “gNB” vs “NG-RAN node | Qualcomm Incorporated | imported from 3GU |
| R3‑181940 | Benefit of Periodic RNA Update Without Anchor Relocation | Qualcomm Incorporated | imported from 3GU |
| R3‑181941 | Workplan for IAB Study Item | Qualcomm Incorporated, Samsung, AT&T, KDDI | imported from 3GU |
| R3‑181942 | draft TR 38.874 V0.1.1 | Qualcomm Incorporated, Samsung, AT&T, KDDI | imported from 3GU |
| R3‑181943 | pCR to TR 38874 | Qualcomm Incorporated, KDDI, AT&T, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel, LG Electronics, CMCC, Samsung | imported from 3GU |
| R3‑181944 | WF - IAB Architecture for L2/L3 relaying | Qualcomm Incorporated, KDDI, AT&T, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel, LG Electronics, CMCC, Samsung | imported from 3GU |
| R3‑181945 | IAB U-plane transport for L2 relaying | Qualcomm Incorporated | imported from 3GU |
| R3‑181946 | IAB C-plane transport for L2 relaying | Qualcomm Incorporated | imported from 3GU |
| R3‑181947 | Time synchronization across IAB topology | Qualcomm Incorporated | imported from 3GU |
| R3‑181948 | IAB topology and route management | Qualcomm Incorporated | imported from 3GU |
| R3‑181949 | Slice Rejection Handling in Xn Handover | Qualcomm Incorporated | imported from 3GU |
| R3‑181950 | NG-RAN aware of UE interested NSSAI | Qualcomm Incorporated | imported from 3GU |
| R3‑181951 | UE radio capability handling | Qualcomm Incorporated | imported from 3GU |
| R3‑181952 | UE capability Indication (P-CR 38.413) | Qualcomm Incorporated | imported from 3GU |
| R3‑181953 | UE capability check for IMS voice | Qualcomm Incorporated | imported from 3GU |
| R3‑181954 | Serving cell list aware for LTE-NR coordination on RF coexistence | Qualcomm Incorporated, NTT DOCOMO INC | imported from 3GU |
| R3‑181955 | Paging procedure (P-CR 38.413) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181956 | LTE-NR coordination for inter-modulation issue | Qualcomm Incorporated, NTT DOCOMO INC | imported from 3GU |
| R3‑181957 | LTE-NR coordination for inter-modulation issue | Qualcomm Incorporated, NTT DOCOMO INC | imported from 3GU |
| R3‑181958 | (TP for NR BL CR for TS 37.340): Direct Data Forwarding in SgNB change | Qualcomm Incorporated | imported from 3GU |
| R3‑181959 | Correction cell level coordination for LTE-NR spectral sharing | Qualcomm Incorporated | imported from 3GU |
| R3‑181960 | (TP for NR BL CR for TS 38.300): Clarification on NR data forwarding | Intel Corporation, Samsung | imported from 3GU |
| R3‑181961 | Flow Control enhancements for uplink PDCP duplication | Intel Corporation | imported from 3GU |
| R3‑181962 | Flow Control enhancements for uplink PDCP duplication | Intel Corporation | imported from 3GU |
| R3‑181963 | Flow Control enhancement for DRX | Intel Corporation | imported from 3GU |
| R3‑181964 | Flow Control enhancement for DRX | Intel Corporation | imported from 3GU |
| R3‑181965 | Flow Control enhancement for DL QoS flow remapping | Intel Corporation | imported from 3GU |
| R3‑181966 | Flow Control enhancement for DL QoS flow remapping | Intel Corporation | imported from 3GU |
| R3‑181967 | Unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
| R3‑181968 | Update of user plane security policy for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181969 | Update of user plane security policy for TS 38.423 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181970 | Reply LS on User Plane Security Policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181971 | 5G deployments with homogeneous TAC format | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181972 | TP for TAC format in TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181973 | TP for TAC format in TS 38.423 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181974 | TP for 5GS TAC format in TS 36.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181975 | Reply LS on TAI and forbidden TAI List for 5GS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181976 | Coding of PDU Resource Session Release | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181977 | Clean up Signaling of NAS PDU in PDU Session management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181978 | Assistance Information for RAN Paging Priority | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181979 | Text Proposal for Xn Assistance Data for RAN Paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181980 | Full UE Context Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181981 | Text proposal for TS 38.410 rapporteur's update | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181982 | Support of secured signaling only connections | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181983 | Clean up signaling of S-NSSAI(s) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑181984 | On the size of 5G-S-TMSI | Huawei | imported from 3GU |
| R3‑181985 | Removal of extended TAC | Huawei | imported from 3GU |
| R3‑181986 | Removal of Extended TAC | Huawei | imported from 3GU |
| R3‑181987 | Removal of extended TAC | Huawei | imported from 3GU |
| R3‑181988 | Removal of Extended TAC | Huawei | imported from 3GU |
| R3‑181989 | Removal of Extended TAC | Huawei | imported from 3GU |
| R3‑181990 | (TP for NR BL CR for TS 38.300): Removal of Extended TAC | Huawei | imported from 3GU |
| R3‑181991 | [DRAFT] Reply LS on TAI and forbidden TAI list for 5GS | Huawei | imported from 3GU |
| R3‑181992 | Introduction of Handover Restriction List on NG | Huawei | imported from 3GU |
| R3‑181993 | Introduction of Handover Restriction List on Xn | Huawei | imported from 3GU |
| R3‑181994 | (TP for NR BL CR for TS 38.300): Correction on Principles of Data forwarding | Huawei | imported from 3GU |
| R3‑181995 | Correction on Xn Data forwarding | Huawei | imported from 3GU |
| R3‑181996 | Indirect data forwarding | Huawei | imported from 3GU |
| R3‑181997 | Destination Address and Forwarding Path based Routing for IAB | Huawei | imported from 3GU |
| R3‑181998 | Overview on IAB | Huawei | imported from 3GU |
| R3‑181999 | Adaptation layer based L2 relaying and light L2 relaying | Huawei | imported from 3GU |
| R3‑182000 | Using Standalone IAB Node for EN-DC Access Link | Huawei | imported from 3GU |
| R3‑182001 | Network Synchronization of IAB Nodes | Huawei | imported from 3GU |
| R3‑182002 | (TP for NR BL CR for TS 37.340): DC establishment for PDCP Termination at SN | BEIJING SAMSUNG TELECOM R&D | imported from 3GU |
| R3‑182003 | Handling of notification control over NG interface | CMCC | imported from 3GU |
| R3‑182004 | DL data handling in RRC_INACTIVE | CMCC | imported from 3GU |
| R3‑182005 | Clarification on slice availability principle | CMCC | imported from 3GU |
| R3‑182006 | Data forwarding for NG-based handover | CMCC | imported from 3GU |
| R3‑182007 | Discussion on secured signalling only connection | CMCC | imported from 3GU |
| R3‑182008 | Handling of UE NG connection release | CMCC | imported from 3GU |
| R3‑182009 | Allowed NSSAI Indication to NG-RAN | CMCC | imported from 3GU |
| R3‑182010 | Consideration on Network Slice Priority in RAN | China Telecommunications | imported from 3GU |
| R3‑182011 | Correction of reference in RRC Container (discussion paper) | NEC | imported from 3GU |
| R3‑182012 | Correction of reference in RRC Container | NEC | imported from 3GU |
| R3‑182013 | Correction of condition presence of E-RAB Level QoS Parameters related | NEC, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182014 | Correction of Reporting PDCP SN | NEC | imported from 3GU |
| R3‑182015 | Correction the max value of one octet | NEC | imported from 3GU |
| R3‑182016 | Core Network Assistance Information | NEC | imported from 3GU |
| R3‑182017 | Further discussion on resource coordination in LTE-NR | NEC | imported from 3GU |
| R3‑182018 | Further update to User Plane security impact on NG interface | NEC | imported from 3GU |
| R3‑182019 | Further update to User Plane security impact on Xn interface | NEC | imported from 3GU |
| R3‑182020 | Further discussion on Notification Control and QoS Flows | NEC | imported from 3GU |
| R3‑182021 | TEID change at SN | Huawei | imported from 3GU |
| R3‑182022 | Support of TEID change at SN | Huawei | imported from 3GU |
| R3‑182023 | Further considerations on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑182024 | Xn setup and NG-RAN node configuration update | Huawei | imported from 3GU |
| R3‑182025 | Stage 2 CR for Xn setup and NG-RAN node configuration update | Huawei | imported from 3GU |
| R3‑182026 | Priority Scenarios for RRC_INACTIVE | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, LG Electronics, Qualcomm Incorporated, Deutsche Telekom, Orange, CMCC, NEC | imported from 3GU |
| R3‑182027 | Continuation of AMF triggered UE context release RAN paging | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑182028 | Stage 3 design of RAN notification area | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182029 | Support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182030 | TP for 38.413 for Support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182031 | TP for 38.423 for Support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182032 | I-RNTI design for RRC_INACTIVE UEs | Huawei | imported from 3GU |
| R3‑182033 | En-gNB X2 TNL Address Discovery for option 3 | Huawei | imported from 3GU |
| R3‑182034 | Stage 2 CR for en-gNB X2 TNL Address Discovery for option 3 | Huawei | imported from 3GU |
| R3‑182035 | Stage 3 CR for en-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑182036 | Acquisition of neighbour cell’s CSI-RS resource configuration | Huawei | imported from 3GU |
| R3‑182037 | Support of NR Multiple Frequency Bands support for in EN-DC | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182038 | X2AP CR for support of NR Multiple frequency band in EN-DC | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182039 | F1AP CR for support of NR Multiple frequency band in EN-DC | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182040 | Clarification on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑182041 | Clarification on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑182042 | [DRAFT] LS on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑182043 | Support of QoS for MR-DC with 5GC Alt1 | Huawei | imported from 3GU |
| R3‑182044 | Support of QoS for MR-DC with 5GC Alt2 | Huawei | imported from 3GU |
| R3‑182045 | Introduction of ciphering indicator for User Plane Security | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑182046 | Introduction of ciphering indicator for User Plane Security | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑182047 | Cause values for XnAP | Huawei | imported from 3GU |
| R3‑182048 | BL CR: LTE-NR resource allocation coordination over X2: CR for TS 36.423 | Ericsson LM | imported from 3GU |
| R3‑182049 | Considerations for Secondary RAT Data Volume | KT Corp. | imported from 3GU |
| R3‑182050 | Discussion on Networking Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑182051 | Discussion on additional cause values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182052 | Downselection on gNB behavior in releasing INACTIVE UE Context | Intel Corporation | imported from 3GU |
| R3‑182053 | Consideration on periodic RNAU without anchor relocation | Intel Corporation | imported from 3GU |
| R3‑182054 | UE-AMBR in NG procedures | LG Electronics Inc. | imported from 3GU |
| R3‑182055 | UE-AMBR in Xn procedure | LG Electronics Inc. | imported from 3GU |
| R3‑182056 | Discussion on Bearer Context Modification | LG Electronics Inc., KT Corp. | imported from 3GU |
| R3‑182057 | RAN3 impacts to support UDC | Huawei | imported from 3GU |
| R3‑182058 | Xn Notification Control | CATT | imported from 3GU |
| R3‑182059 | Xn Notification Control TP for 38.423 | CATT | imported from 3GU |
| R3‑182060 | (TP for NR BL CR for TS 38.470):F1 Notification Control | CATT | imported from 3GU |
| R3‑182061 | (TP for NR BL CR for TS 38.473):F1 Notification Control | CATT | imported from 3GU |
| R3‑182062 | TP on inclusion of cause value in Path Switch | CATT | imported from 3GU |
| R3‑182063 | TP for 38.423 on Xn Handover ack | CATT | imported from 3GU |
| R3‑182064 | UE Slicing information usage in RAN | CATT | imported from 3GU |
| R3‑182065 | Slice unavailable | CATT | imported from 3GU |
| R3‑182066 | TP for PDU sessions modified in Path Switch request | CATT | imported from 3GU |
| R3‑182067 | Discussion on QoS flow remapping | CATT | imported from 3GU |
| R3‑182068 | Solution on data forwarding | CATT | imported from 3GU |
| R3‑182069 | Support of UL data decompression | Huawei | imported from 3GU |
| R3‑182070 | Support of UL data decompression | Huawei | imported from 3GU |
| R3‑182071 | Support of UL data decompression | Huawei | imported from 3GU |
| R3‑182072 | CR for clarification of lost NR-U packet | Samsung | imported from 3GU |
| R3‑182073 | User Inactivity monitoring in NG-RAN function split architecture | Samsung | imported from 3GU |
| R3‑182074 | TP for TS38.463 on E1 procedure for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182075 | Adding new F1 procedure for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182076 | Consideration on architecture and protocol stack for IAB | LG Electronics | imported from 3GU |
| R3‑182077 | F1AP support for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182078 | E1 interface management procedures | Samsung | imported from 3GU |
| R3‑182079 | CU-UP Security Capability indication to CU-CP | Samsung | imported from 3GU |
| R3‑182080 | TP for TS38.463 on E1 interface management | Samsung | imported from 3GU |
| R3‑182081 | Additional UE-associated E1 procedures^^ | Samsung | imported from 3GU |
| R3‑182082 | TP for TS38.463 on additional UE-associated E1 procedures | Samsung | imported from 3GU |
| R3‑182083 | F1 message transport between IAB Donor and IAB Node | LG Electronics Inc. | imported from 3GU |
| R3‑182084 | TP for 36.423 SgNB Change Required | Google Inc. | imported from 3GU |
| R3‑182085 | Supporting EN-DC delta configuration in CU-DU architecture | Google Inc. | imported from 3GU |
| R3‑182086 | TP for 38.401 to support delta configuration | Google Inc. | imported from 3GU |
| R3‑182087 | TP for 38.473 in supporting delta configuration | Google Inc. | imported from 3GU |
| R3‑182088 | [DRAFT] LS on supporting delta configuration for F1 UE Context Management | Google Inc. | imported from 3GU |
| R3‑182089 | List of served cells for X2 connection between eNB and en-gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182090 | Specification impact for TNL address discovery based on intermediate node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182091 | TNL address discovery involving en-gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182092 | Options for inclusion of RRC info carrying LTE-CRS rate matching parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182093 | (TP for LTE-NR coexistence BL CR for TS 36.423): Include RRC info carrying LTE-CRS rate matching parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182094 | Impact on the Neighbour Relation Table from the Frequency Sharing feature | Nokia, Nokia Shanghai Bell, Verizon Wireless, Deutsche Telekom, Orange | imported from 3GU |
| R3‑182095 | Addition of ‘No EN-DC’ attribute for the Neighbour Relation Table | Nokia, Nokia Shanghai Bell, Verizon Wireless, Deutsche Telekom, Orange | imported from 3GU |
| R3‑182096 | Impacts of network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182097 | X2 interface between eNB and shared en-gNB with TAC and access mode per PLMN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182098 | Correction of max NR ARFCN value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182099 | Correction of max NR ARFCN value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182100 | Discussion on Network Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑182101 | TP for 38.424 | Mitsubishi Electric RCE | imported from 3GU |
| R3‑182102 | Discussion on supporting IAB in NSA | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182103 | Architecture and Protocols: MAC adaptation layer based IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182104 | MAC adaptation vs RLC adaptation layer for L2 relaying | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182105 | Architecture and Protocols: Connectivity Service Solution for IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182106 | IAB Topology Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182107 | TP to 38.425 on DL user data to DU | CATT | imported from 3GU |
| R3‑182108 | Xn support for RRC Re-establishment | Qualcomm Incorporated | imported from 3GU |
| R3‑182109 | pCR to 38.462 on initial TPs | Huawei | imported from 3GU |
| R3‑182110 | Rapporteur update to 38.462 | Huawei | imported from 3GU |
| R3‑182111 | (TP for NR BL CR for TS 38.473): on Clarification of pMax transfer over F1 | Huawei | imported from 3GU |
| R3‑182112 | CR to 38.473 on pMax transfer over F1 | Huawei | imported from 3GU |
| R3‑182113 | (TP for NR BL CR for TS 38.473): on clarification of on the presence of C-RNTI in Initial UL RRC Transfer message | Huawei | imported from 3GU |
| R3‑182114 | (TP for NR BL CR for TS 38.473): on PWS info transfer about over F1 | Huawei | imported from 3GU |
| R3‑182115 | (TP for NR BL CR for TS 38.473): on paging transfer over F1 | Huawei | imported from 3GU |
| R3‑182116 | (TP for NR BL CR for TS 38.473): on Cell Barred Info exchange over F1 interface | Huawei | imported from 3GU |
| R3‑182117 | (TP for NR BL CR for TS 38.473): on CA-based DRB duplication | Huawei | imported from 3GU |
| R3‑182118 | (TP for NR BL CR for TS 38.473): on CA-based SRB duplication | Huawei | imported from 3GU |
| R3‑182119 | (TP for NR BL CR for TS 38.473): on Further discussions on QoS parameter transfer over F1 | Huawei | imported from 3GU |
| R3‑182120 | (TP for NR BL CR for TS 38.470): on QoS parameter transfer over F1 | Huawei | imported from 3GU |
| R3‑182121 | (TP for NR BL CR for TS 38.473): on Cell type indication | Huawei | imported from 3GU |
| R3‑182122 | (TP for NR BL CR for TS 38.473): on gNB-CU behaviour without DU to CU RRC information | Huawei | imported from 3GU |
| R3‑182123 | (TP for NR BL CR for TS 38.473): on RRC connection rejection indication over F1 | Huawei | imported from 3GU |
| R3‑182124 | Further discussions on AMBR | Huawei | imported from 3GU |
| R3‑182125 | CR to 38.473 on the introduction of UE AMBR over F1 for EN-DC operation | Huawei | imported from 3GU |
| R3‑182126 | CR to 38.470 on the introduction of UE AMBR over F1 for EN-DC operation | Huawei | imported from 3GU |
| R3‑182127 | Full configuration indication over F1 | Huawei | imported from 3GU |
| R3‑182128 | CR to 38.473 on full configuration indication over F1 | Huawei | imported from 3GU |
| R3‑182129 | Inactivity monitoring in CP/UP separation | Huawei | imported from 3GU |
| R3‑182130 | (TP for NR BL CR for TS 38.401): on RRC state transition for CP-UP separation | Huawei | imported from 3GU |
| R3‑182131 | Data Forwarding in CP/UP separation | Huawei | imported from 3GU |
| R3‑182132 | pCR to 38.460 on QoS handling over E1 | Huawei | imported from 3GU |
| R3‑182133 | CR to 38.473 on including RRC container in F1 message | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE | imported from 3GU |
| R3‑182134 | pCR to 38.460 on secondary node modification triggered by gNB-CU-CP | Huawei | imported from 3GU |
| R3‑182135 | (TP for NR BL CR for TS 38.473): Further clarification on UE context management procedure | Huawei | imported from 3GU |
| R3‑182136 | pCR to 38.460 on centralized retransmission for CP-UP separation | Huawei | imported from 3GU |
| R3‑182137 | (TP for NR BL CR for TS 38.473): Procedural text for CG-ConfigInfo IE | Huawei | imported from 3GU |
| R3‑182138 | CR to 38.473 on presence of gNB-CU F1AP UE ID in DL RRC MESSAGE TRANSFER | Huawei | imported from 3GU |
| R3‑182139 | Consideration on Allowed NSSAI in NG-RAN | LG Electronics | imported from 3GU |
| R3‑182140 | Further consideration on RRC Inactive Assistance Information | LG Electronics, Huawei | imported from 3GU |
| R3‑182141 | Stage 3 TP on CN selective awareness for RRC-INACTIVE state | LG Electronics | imported from 3GU |
| R3‑182142 | (TP for NR BL CR for TS 38.300): Stage 2 TP on CN selective awareness for RRC-INACTIVE state | LG Electronics | imported from 3GU |
| R3‑182143 | Introduction of QMC for MTSI in UTRAN and EUTRAN | Ericsson | imported from 3GU |
| R3‑182144 | Draft reply LS on adding new service type in QMC reporting (To:SA4, CC: RAN2, SA5) | Ericsson | imported from 3GU |
| R3‑182145 | Resolving the remaining FFS on QoS | Ericsson | imported from 3GU |
| R3‑182146 | Resolving the remaining FFS on QoS | Ericsson | imported from 3GU |
| R3‑182147 | (TP for NR BL CR for TS 38.473): Notification control over F1 | Ericsson | imported from 3GU |
| R3‑182148 | Notification Control over NGAP | Ericsson | imported from 3GU |
| R3‑182149 | Notification Control | Ericsson | imported from 3GU |
| R3‑182150 | RAN initiated QoS flow/PDU session release | Ericsson | imported from 3GU |
| R3‑182151 | Further Discussion on QoS setting for default DRBs | Ericsson | imported from 3GU |
| R3‑182152 | Slice configuration at NG Setup | Ericsson | imported from 3GU |
| R3‑182153 | Discussion and decision on Allowed NSSAI | Ericsson | imported from 3GU |
| R3‑182154 | [DRAFT] Reply LS on Allowed NSSAI indication to RAN | Ericsson | imported from 3GU |
| R3‑182155 | (TP for NR BL CR for TS 38.401): Definition of PDU Session Resource | Ericsson, Nokia | imported from 3GU |
| R3‑182156 | Text Proposal for NGAP to introduce the term “PDU Session Resource” | Ericsson, Nokia | imported from 3GU |
| R3‑182157 | Text Proposal for XnAP to introduce the term “PDU Session Resource” | Ericsson, Nokia | imported from 3GU |
| R3‑182158 | Text Proposal for E1AP to introduce the term “PDU Session Resource” | Ericsson, Nokia | imported from 3GU |
| R3‑182159 | TP for signalling of RFSP over NG | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182160 | TP for signalling of RFSP over Xn | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182161 | Resolving open topics for HO and Context Retrieval in XnAP – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182162 | Introducing Error Indication and Reset procedures in XnAP – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182163 | Review of RRC Containers in XnAP – TP 38.423 | Ericsson | imported from 3GU |
| R3‑182164 | Correction on the handling concurrent running of security procedures | Ericsson | imported from 3GU |
| R3‑182165 | (TP for NR BL CR for TS 38.401): Corrections on Xn connectivity | Ericsson | imported from 3GU |
| R3‑182166 | End Marker handling | Ericsson | imported from 3GU |
| R3‑182167 | Data forwarding handling 4G to 5G | Ericsson | imported from 3GU |
| R3‑182168 | Correction to the Data forwarding handling over 5GC | Ericsson | imported from 3GU |
| R3‑182169 | AP ID handling and related Cause Values | Ericsson | imported from 3GU |
| R3‑182170 | Cause Value corrections on NGAP | Ericsson | imported from 3GU |
| R3‑182171 | Cause values on XnAP | Ericsson | imported from 3GU |
| R3‑182172 | Reviewing Restructured DC messages for MN iniated procedures – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182173 | How to apply principle of resturctured DC messages on SN initiated procedures – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182174 | (TP for NR BL CR for TS 38.300): Support of SN initiated QoS flow offload | Ericsson | imported from 3GU |
| R3‑182175 | (TP for NR BL CR for TS 37.340): QoS flow mapping information for SN terminated bearers – MR-DC with 5GC | Ericsson | imported from 3GU |
| R3‑182176 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑182177 | PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑182178 | PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑182179 | Potentials of RAN UP network function virtualisation | Ericsson, Vodafone, KT, AT&T | imported from 3GU |
| R3‑182180 | (TP for NR BL CR for TS 37.340): Support of RAN UP network function virtualisation at bearer type change or MN change or SN change | Ericsson, AT&T | imported from 3GU |
| R3‑182181 | Support of RAN UP network function virtualisation at bearer type change or SN change – TP for 38.423 | Ericsson, AT&T | imported from 3GU |
| R3‑182182 | Data forwarding aspects for DC bearer type change and QoS flow offloading | Ericsson | imported from 3GU |
| R3‑182183 | (TP for NR BL CR for TS 37.340): Data forwarding aspects for intra-system ACTIVE mobility – TP for 37.340 | Ericsson | imported from 3GU |
| R3‑182184 | Data forwarding aspects for intra-system ACTIVE mobility – DC TP for XnAP | Ericsson | imported from 3GU |
| R3‑182185 | Introducing SN initiated SN Change procedure in XnAP | Ericsson | imported from 3GU |
| R3‑182186 | Support for UP Version Handling | Ericsson | imported from 3GU |
| R3‑182187 | Introduction of UP Protocol Version Handling | Ericsson | imported from 3GU |
| R3‑182188 | DL PDCP Duplication Support | Ericsson | imported from 3GU |
| R3‑182189 | Introduction of assistance information for DL PDCP duplication | Ericsson | imported from 3GU |
| R3‑182190 | DDDS delivery | Ericsson | imported from 3GU |
| R3‑182191 | DDDS delivery | Ericsson | imported from 3GU |
| R3‑182192 | Final Frame Indication | Ericsson | imported from 3GU |
| R3‑182193 | Final Frame Indication | Ericsson | imported from 3GU |
| R3‑182194 | UL and DL outage | Ericsson | imported from 3GU |
| R3‑182195 | UL and DL outage | Ericsson | imported from 3GU |
| R3‑182196 | Corrections to Minimum Desired Buffer Size | Ericsson | imported from 3GU |
| R3‑182197 | Corrections to Minimum Desired Buffer Size | Ericsson | imported from 3GU |
| R3‑182198 | (TP for NR BL CR for TS 38.473): Clarifications on multiple TNL associations | Ericsson | imported from 3GU |
| R3‑182199 | Clarifications on multiple TNL associations | Ericsson | imported from 3GU |
| R3‑182200 | (TP for NR BL CR for TS 38.401): Clarifications on multiple TNL associations | Ericsson | imported from 3GU |
| R3‑182201 | (TP for NR BL CR for TS 38.473): Definition of TNL Address Information on F1-C | Ericsson | imported from 3GU |
| R3‑182202 | Addition of port number differentiation – CR 38.472 | Ericsson | imported from 3GU |
| R3‑182203 | (TP for NR BL CR for TS 38.473): UE identities for RAN and CN paging | Ericsson | imported from 3GU |
| R3‑182204 | Monitoring inactivity | Ericsson | imported from 3GU |
| R3‑182205 | CR for monitoring inactivity | Ericsson | imported from 3GU |
| R3‑182206 | (TP for NR BL CR for TS 38.473): Clarification on signalling connection | Ericsson | imported from 3GU |
| R3‑182207 | (TP for NR BL CR for TS 38.473): Measurement configuration for SA | Ericsson | imported from 3GU |
| R3‑182208 | (TP for NR BL CR for TS 38.473): Establishment of DRB QoS in CU-DU architecture | Ericsson, Vodafone | imported from 3GU |
| R3‑182209 | (TP for NR BL CR for TS 38.473): Solution 3 for establishment of DRB QoS in CU-DU architecture | Ericsson, Vodafone | imported from 3GU |
| R3‑182210 | (TP for NR BL CR for TS 38.473): RRC version handling | Ericsson | imported from 3GU |
| R3‑182211 | (TP for NR BL CR for TS 38.473): RRC container over F1AP | Ericsson | imported from 3GU |
| R3‑182212 | (TP for NR BL CR for TS 38.401): Clarification on active cell list | Ericsson | imported from 3GU |
| R3‑182213 | XnAP – Rapporteur proposal for editorial and other changes | Ericsson | imported from 3GU |
| R3‑182214 | (TP for LTE-NR coexistence BL CR for TS 36.423): E-UTRA - NR resource allocation coordination over X2 | Ericsson | imported from 3GU |
| R3‑182215 | Introduction of the vendor specific UE differentiation information | Ericsson, Vodafone | imported from 3GU |
| R3‑182216 | Introduction of the vendor specific UE differentiation Information | Ericsson, Vodafone | imported from 3GU |
| R3‑182217 | Introduction of the vendor specific UE differentiation Information | Ericsson, Vodafone | imported from 3GU |
| R3‑182218 | Discussion on UE differentiation for NB-IoT | Ericsson | imported from 3GU |
| R3‑182219 | [Draft] Reply LS on Reply LS on UE differentiation for NB-IoT from SA2 | Ericsson | imported from 3GU |
| R3‑182220 | Assistance Information Broadcast Procedure in LPPa | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182221 | Assistance Data Signaling in LPPa | Ericsson | imported from 3GU |
| R3‑182222 | Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182223 | Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182224 | (TP for NR BL CR for TS 38.401): E1 support for RRC-inactive | Ericsson | imported from 3GU |
| R3‑182225 | Dual-connectivity configuration over E1 | Ericsson | imported from 3GU |
| R3‑182226 | Potentials for RAN UP network function virtualizaiton | Ericsson | imported from 3GU |
| R3‑182227 | PDCP duplication configuration | Ericsson | imported from 3GU |
| R3‑182228 | (TP for NR BL CR for TS 38.401): Support of RAN UP network function virtualisation at handover | Ericsson, Vodafone, KT, AT&T | imported from 3GU |
| R3‑182229 | Support of RAN UP network function virtualisation at handover – for 38.300 | Ericsson | imported from 3GU |
| R3‑182230 | Support of RAN UP network function virtualisation at handover – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182231 | Support of RAN UP network function virtualisation at handover – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182232 | Support of RAN UP network function virtualisation at handover – for 36.300 | Ericsson | imported from 3GU |
| R3‑182233 | (TP for NR BL CR for TS 38.401): Bearer context definition | Ericsson | imported from 3GU |
| R3‑182234 | (TP for CPUP_Split BL CR for TS 38.401): Resolve FFS in procedures in TS 38.401 | Ericsson | imported from 3GU |
| R3‑182235 | Multiple TNL associations over E1 | Ericsson | imported from 3GU |
| R3‑182236 | Dual-connectivity configuration over E1 | Ericsson | imported from 3GU |
| R3‑182237 | E1 Setup procedure | Ericsson | imported from 3GU |
| R3‑182238 | E1 Reset procedure | Ericsson | imported from 3GU |
| R3‑182239 | E1 Release procedure | Ericsson | imported from 3GU |
| R3‑182240 | Error Indication | Ericsson | imported from 3GU |
| R3‑182241 | Bearer Modification procedure | Ericsson | imported from 3GU |
| R3‑182242 | E1 Configuration update | Ericsson | imported from 3GU |
| R3‑182243 | Bearer Context Setup procedure | Ericsson | imported from 3GU |
| R3‑182244 | TS 38.463 v020 | Ericsson | imported from 3GU |
| R3‑182245 | Presentation of Rapporteur TP for TS 38.463 | Ericsson | imported from 3GU |
| R3‑182246 | Network Synchronization for IAB Nodes | Ericsson | imported from 3GU |
| R3‑182247 | Protocol Stack for IAB Architecture 1a and 1b | Ericsson | imported from 3GU |
| R3‑182248 | CN functions for supporting IAB nodes | Ericsson | imported from 3GU |
| R3‑182249 | Setup Procedure for the Adaptation Layer of an IAB system | Ericsson | imported from 3GU |
| R3‑182250 | Setup procedures for IAB-node and a UE connected to an IAB node | Ericsson | imported from 3GU |
| R3‑182251 | Support for SPID over network interfaces | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182252 | Use of SPID for EN-DC | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182253 | Priority order for SpCell list | Ericsson | imported from 3GU |
| R3‑182254 | Priority order for SpCell list | Ericsson | imported from 3GU |
| R3‑182255 | Measurement configuration for EN-DC | Ericsson | imported from 3GU |
| R3‑182256 | CR for measurement configuration in EN-DC | Ericsson | imported from 3GU |
| R3‑182257 | Correction on padding | Ericsson | imported from 3GU |
| R3‑182258 | Correction on padding | Ericsson | imported from 3GU |
| R3‑182259 | RRC container over F1AP | Ericsson | imported from 3GU |
| R3‑182260 | CR for presence of C-RNTI in EN-DC | Ericsson | imported from 3GU |
| R3‑182261 | Correction on SRB ID range | Ericsson | imported from 3GU |
| R3‑182262 | CR for correction on SRB ID range | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182263 | Securing signalling connections | Ericsson | imported from 3GU |
| R3‑182264 | Introduction of QMC for MTSI in UTRAN | Ericsson | imported from 3GU |
| R3‑182265 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑182266 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑182267 | Support of RAN UP network function virtualisation at bearer type change or SN change | Ericsson, AT&T | imported from 3GU |
| R3‑182268 | Assistance Information Broadcasting | Ericsson | imported from 3GU |
| R3‑182269 | Support of RAN UP network function virtualisation at handover – for 36.413 | Ericsson | imported from 3GU |
| R3‑182270 | Support of RAN UP network function virtualisation at handover – for 36.423 | Ericsson | imported from 3GU |
| R3‑182271 | Initial access in NG-RAN with separated CP and UP | Intel Corporation | imported from 3GU |
| R3‑182272 | Adaptation layer and Routing for IAB in NR | Intel Corporation | imported from 3GU |
| R3‑182273 | (TP for SA BL CR) Introducing explicit per-UE TNLA binding release in NGAP (stage-2) | Intel Corporation, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182274 | Rapporteur's correction to TS 38.474 | Intel Corporation | imported from 3GU |
| R3‑182275 | Correction on Transport Layer Information (F1-TS, F1-BL, Xn-BL) | Huawei | imported from 3GU |
| R3‑182276 | (TP for NR BL CR for TS 38.473): non-backward correction on Transport Layer | Huawei | imported from 3GU |
| R3‑182277 | TP for NR BL CR for TS 38.473): Clean-up for Multiple SCTP | Huawei | imported from 3GU |
| R3‑182278 | Correction on Transport Layer Information | Huawei | imported from 3GU |
| R3‑182279 | Support of RNL initialisation of an additional NG-C TNL association – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182280 | Support of AMF initiated update of UE associated signalling connection properties – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182281 | Further Discussions on RRC_INACTIVE | Ericsson | imported from 3GU |
| R3‑182282 | (TP for NR BL CR for TS 38.300): NG based UE context retrieval | Ericsson | imported from 3GU |
| R3‑182283 | (TP for NR BL CR for TS 38.300): NG based RAN paging | Ericsson | imported from 3GU |
| R3‑182284 | NGAP TP to support NG-based UE Context Retrieval | Ericsson | imported from 3GU |
| R3‑182285 | NGAP TP to support NG-based RAN Paging | Ericsson | imported from 3GU |
| R3‑182286 | TP for 38.410 to introduce support of NG-based relay of XnAP messages | Ericsson | imported from 3GU |
| R3‑182287 | Introduction of NR-U Sequence Number for UL PDU | Ericsson | imported from 3GU |
| R3‑182288 | Introduction of NR-U Sequence Number for UL | Ericsson | imported from 3GU |
| R3‑182289 | Correction of references to RRC containers for EN-DC | Ericsson | imported from 3GU |
| R3‑182290 | Way Forward on UL AMBR Monitoring and enforcement | Ericsson | imported from 3GU |
| R3‑182291 | Handling of UE UL AMBR | Ericsson | imported from 3GU |
| R3‑182292 | (TP for CPUP_Split BL CR for TS 38.401): Issues on RRC-INACTIVE state in CU-DU split | LG Electronics | imported from 3GU |
| R3‑182293 | Corrections on Tabular indentation and ASN.1 criticality | Ericsson, Qualcomm | imported from 3GU |
| R3‑182294 | Time plan for WI eNB(s) Architecture Evolution for E-UTRAN and NG-RAN | China Unicom, Orange, Telekom R&D Sdn. Bhd. | imported from 3GU |
| R3‑182295 | Support for UE capability related to integrity protection of DRBs | Intel Corporation | imported from 3GU |
| R3‑182296 | Architecture considerations for IAB with L2 relaying | AT&T | imported from 3GU |
| R3‑182297 | On backhauling of F1-U and F1-C for IAB with L2 relaying | AT&T | imported from 3GU |
| R3‑182298 | Discussion on NSA/SA support for IAB architectures | AT&T | imported from 3GU |
| R3‑182299 | Discussion on IAB node discovery and topology/route management | AT&T | imported from 3GU |
| R3‑182300 | LTE-specific features to be supported in LTE CU DU architecture | China Unicom | imported from 3GU |
| R3‑182301 | QoS handling for DRB management in F1 interface | LG Electronics Inc. | imported from 3GU |
| R3‑182302 | (TP for LTE-NR coexistence BL CR for TS 36.423) Correct Coordination to Cell Level | Qualcomm Incorporated | imported from 3GU |
| R3‑182303 | TR 30.531 v1.30.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | imported from 3GU |
| R3‑182304 | Reply LS on Data support for "voice centric" UE supporting CE mode B | 3GPP RAN2, Intel | imported from 3GU |
| R3‑182305 | Reply LS on EDT procedures and AS NAS interaction | 3GPP RAN2, Mediatek | imported from 3GU |
| R3‑182306 | UE capability related to integrity protection of DRBs | 3GPP RAN2, Intel | imported from 3GU |
| R3‑182307 | Reply LS on adding new service type in QMC reporting | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑182308 | Reply LS on Attributes for QoE measurement collection | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑182309 | Reply LS on Certification/License and Identification of Aerial Vehicles | 3GPP RAN2, NTT Docomo | imported from 3GU |
| R3‑182310 | LS to RAN3 on details of RAN notification area | 3GPP RAN2, Intel | imported from 3GU |
| R3‑182311 | LS on SN triggered fullConfig indication in X2 for EN-DC | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑182312 | Reply LS on periodic RNA update without anchor relocation | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑182313 | LS on NR RRC configuration response message | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑182314 | Response to R3-181811 | Ericsson | imported from 3GU |
| R3‑182315 | Response to R3-181931 (QC), R3-181971 (Nokia) and R3-181985 (Huawei) | Ericsson | imported from 3GU |
| R3‑182316 | Response to R3-181972 | Ericsson | imported from 3GU |
| R3‑182317 | Response to R3-181973 | Ericsson | imported from 3GU |
| R3‑182318 | Response to R3-181974 | Ericsson | imported from 3GU |
| R3‑182319 | Response to R3-181992 (1) | Ericsson | imported from 3GU |
| R3‑182320 | Response to R3-181992 (2) | Ericsson | imported from 3GU |
| R3‑182321 | Response to R3-181993 (1) | Ericsson | imported from 3GU |
| R3‑182322 | Response to R3-181993 (2) | Ericsson | imported from 3GU |
| R3‑182323 | RAN3-99 meeting Report | MCC | imported from 3GU |
| R3‑182324 | Core Network Assistance Information | NEC | imported from 3GU |
| R3‑182325 | [Draft]reply LS on Clarification on GTP-U "Long PDCP PDU Number" extension header | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182326 | [draft] Reply LS on INOBEAR | Samsung | imported from 3GU |
| R3‑182327 | Introduction of LTE-M (eMTC) traffic Differentiation | Huawei, Nokia | imported from 3GU |
| R3‑182328 | Summary of UE capability Offline discussion | Nokia | imported from 3GU |
| R3‑182329 | [DRAFT] Reply LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182330 | Enabling future extendability of the RAN Container | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑182331 | Enabling future extendability of the Xw RAN Container | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑182332 | (TP for NR BL CR for TS 38.473): Rapporteur update | Huawei | imported from 3GU |
| R3‑182333 | Rapporteur update for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182334 | pCR to TR 38874 | Qualcomm Incorporated, KDDI, AT&T, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel, LG Electronics, CMCC, Samsung | imported from 3GU |
| R3‑182335 | TP for 38.424 | Mitsubishi Electric RCE | imported from 3GU |
| R3‑182336 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑182337 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑182338 | Addiiton of the full config indicator | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182339 | Addiiton of the full config indicator Sg 2 | Nokia | imported from 3GU |
| R3‑182340 | TP for 38.401 in supporting full configuration | Google Inc. | imported from 3GU |
| R3‑182341 | Full configuration indication over F1 | Huawei | imported from 3GU |
| R3‑182342 | [DRAFT] LS on supporting delta configuration for F1 UE Context Management | Google Inc. | imported from 3GU |
| R3‑182343 | CR for clarification of lost NR-U packet | Samsung | imported from 3GU |
| R3‑182344 | X2AP CR for support of NR Multiple frequency band in EN-DC | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182345 | (TP for EN-DC BL CR for TS 38.473): support of NR Multiple frequency band in EN-DC | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182346 | (TP for EN-DC BL CR for TS 38.473) Correction on max NR ARFCN value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182347 | Support of secured signaling only connections | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182348 | Support of secured signaling only connections (stage 2) | Ericsson | imported from 3GU |
| R3‑182349 | Summary of offline discussion on Secured SRBs Without PDU Sessions | Nokia | imported from 3GU |
| R3‑182350 | Correction on Initial DDDS triggering | Nokia, Nokia Shanghai Bell, Verizon Wireless, KT, Vodafone, Ericsson, CATT | imported from 3GU |
| R3‑182351 | CR to 38.401 on DL user data to DU | CATT | imported from 3GU |
| R3‑182352 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| R3‑182353 | Use of SPID for EN-DC | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182354 | TP to EN-DC BL 38.473 on including RRC container in F1 message | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE | imported from 3GU |
| R3‑182355 | TP to EN-DC BL 38.473 on intra-gNB-DU handover | CATT | imported from 3GU |
| R3‑182356 | Presence of C-RNTI in EN-DC | Ericsson | imported from 3GU |
| R3‑182357 | Correction on SRB ID range | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182358 | (TP for BL CR EN-DC for TS 38.473) Measurement configuration | Ericsson | imported from 3GU |
| R3‑182359 | [Draft]LS on RRC Information from gNB-DU to gNB-CU | CATT | imported from 3GU |
| R3‑182360 | Introduction of of UL/SUL indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182361 | Handling of protocol error for Transaction ID IE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182362 | Response to R3-182318 | Nokia | imported from 3GU |
| R3‑182363 | Introduction of QMC for MTSI in UTRAN | Ericsson | imported from 3GU |
| R3‑182364 | Xn setup and NG-RAN node configuration update | Huawei | imported from 3GU |
| R3‑182365 | Stage 2 CR for Xn setup and NG-RAN node configuration update | Huawei | imported from 3GU |
| R3‑182366 | Reply LS on INOBEAR | Samsung | imported from 3GU |
| R3‑182367 | Aerial Vehicles session report | Vice chairman (ZTE) | imported from 3GU |
| R3‑182368 | IoT session report | Vice-chairman (Intel) | imported from 3GU |
| R3‑182369 | Problem statement for the AMBR in EN-DC | Nokia | imported from 3GU |
| R3‑182370 | Update of user plane security policy for TS 38.413 | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑182371 | Update of user plane security policy for TS 38.423 | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑182372 | TP for signalling of RFSP over NG | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182373 | TP for signalling of RFSP over Xn | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑182374 | TP for NGAP GUAMI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182375 | Resolving open topics for HO and Context Retrieval in XnAP – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182376 | Introducing Error Indication and Reset procedures in XnAP – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182377 | Discussion on supporting per-UE TNLA-binding release in NGAP | Nokia, Nokia Shanghai Bell, Intel Corporation, Verizon Wireless | imported from 3GU |
| R3‑182378 | TNL IEs | Qualcomm Incorporated | imported from 3GU |
| R3‑182379 | Support of RNL initialisation of an additional NG-C TNL association – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182380 | Support of AMF initiated update of UE associated signalling connection properties – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182381 | 5G deployments with homogeneous TAC format | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182382 | Reply LS on TAI and forbidden TAI List for 5GS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182383 | TP for TAC format in TS 38.413 | Ericsson | imported from 3GU |
| R3‑182384 | TP for TAC format in TS 38.423 | Ericsson | imported from 3GU |
| R3‑182385 | Response to R3-182318 | Nokia | imported from 3GU |
| R3‑182386 | (TP for EN DC BL CR for TS 38.473) Update of TAC format | Huawei | imported from 3GU |
| R3‑182387 | Summary of offline discussion on Handover Restriction List on NG/Xn | Huawei | imported from 3GU |
| R3‑182388 | Summary of offline discussion on End Marker data forwarding | NTT Docomo | imported from 3GU |
| R3‑182389 | Data forwarding handling 4G to 5G | Ericsson | imported from 3GU |
| R3‑182390 | Discussion and 38.413 pCR on xxx NG-RAN Node to xxx NG-RAN Node Transparent Container | ZTE | imported from 3GU |
| R3‑182391 | Data forwarding for intra-system NG based HO | Samsung | imported from 3GU |
| R3‑182392 | Finalization data forwarding for Xn based handover | Samsung | imported from 3GU |
| R3‑182393 | Handling of notification control in TS 38.413 | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑182394 | Further Discussion and 38.413 pCR on PDU SESSION RESOURCE MODIFY INDICATION | ZTE | imported from 3GU |
| R3‑182395 | Resolving the remaining FFS on QoS | Ericsson | imported from 3GU |
| R3‑182396 | Resolving the remaining FFS on QoS | Ericsson | imported from 3GU |
| R3‑182397 | Further Discussions on RRC_INACTIVE | Ericsson | imported from 3GU |
| R3‑182398 | Reference QoS profile indication from 5GC | Nokia, Nokia Shanghai Bell, Intel Corporation, LG Electronics Inc., Huawei, CMCC | imported from 3GU |
| R3‑182399 | TP to Skeleton of TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182400 | UE-AMBR in NG procedures | LG Electronics Inc. | imported from 3GU |
| R3‑182401 | UE-AMBR in Xn procedure | LG Electronics Inc. | imported from 3GU |
| R3‑182402 | Reply LS on size of RANAC | Qualcomm Incorporated | imported from 3GU |
| R3‑182403 | (TP for LTE-NR coexistence BL CR for TS 36.423): E-UTRA - NR resource allocation coordination over X2 | Ericsson, AT&T, Qualcomm, Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑182404 | Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182405 | Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182406 | Skeleton for TS 29.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182407 | TP for TS29.413 | Nokia, Nokia Shanghai Bell, Intel Corporation, China Telecom, KT Corp., Orange, AT&T, China Unicom | imported from 3GU |
| R3‑182408 | Reply LS on N2 and N3 interfaces for Non-3GPP access network | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182409 | Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | Qualcomm Incorporated | imported from 3GU |
| R3‑182410 | Reply LS on INOBEAR | 3GPP CT1, Samsung | imported from 3GU |
| R3‑182411 | LS on security aspects of supporting LTE connected to 5GC | 3GPP CT1, Qualcomm | imported from 3GU |
| R3‑182412 | LS on UE capability related to integrity protection of DRBs | 3GPP CT1, Qualcomm | imported from 3GU |
| R3‑182413 | LS On INOBEAR | 3GPP CT4, Huawei | imported from 3GU |
| R3‑182414 | Response LS on INOBEAR | 3GPP RAN2, Samsung | imported from 3GU |
| R3‑182415 | Reply LS on 5G-S-TMSI | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑182416 | Reply LS on Extending TAC for NR and NG-RAN | 3GPP RAN2, Intel | imported from 3GU |
| R3‑182417 | Reply LS on adding new service type in QMC reporting | 3GPP SA4, Ericsson | imported from 3GU |
| R3‑182418 | LS Reply to SA2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | 3GPP SA5, Nokia | imported from 3GU |
| R3‑182419 | LS on 5G Trace | 3GPP SA5, Nokia | imported from 3GU |
| R3‑182420 | Correction of abnormal conditions for EN-DC security algorithm selection | Qualcomm Incorporated | imported from 3GU |
| R3‑182421 | Correction of reference in RRC Container | NEC | imported from 3GU |
| R3‑182422 | Correction of references to RRC containers for EN-DC | Ericsson | imported from 3GU |
| R3‑182423 | Clarification of the use of the desired buffer size | Nokia, Nokia Shanghai Bell, Verizon | imported from 3GU |
| R3‑182424 | Correction of Reporting PDCP SN | NEC | imported from 3GU |
| R3‑182425 | Correction the max value of one octet | NEC | imported from 3GU |
| R3‑182426 | Correction on padding | Ericsson | imported from 3GU |
| R3‑182427 | Stage 3 design of RAN notification area | Huawei, Nokia, Nokia Shanghai Bell, CATT, NEC, Intel Corporation | imported from 3GU |
| R3‑182428 | Workplan for IAB Study Item | Qualcomm Incorporated, Samsung, AT&T, KDDI | imported from 3GU |
| R3‑182429 | Summary of offline discussions on RRC INACTIVE | Huawei | imported from 3GU |
| R3‑182430 | Summary of discussion on periodic RNA update without anchor relocation | Qualcomm Incorporated | imported from 3GU |
| R3‑182431 | Reply LS on details of RAN notification area | Qualcomm Incorporated | imported from 3GU |
| R3‑182432 | TP for 38.413 for Support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182433 | TP for 38.423 for Support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182434 | Assistance Information for RAN Paging Priority | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182435 | TP: rapporteur update to TS 38.463 v010 | Ericsson | imported from 3GU |
| R3‑182436 | (TP for NR BL CR for TS 38.401): Bearer context definition | Ericsson | imported from 3GU |
| R3‑182437 | Reply LS on User Plane Security Policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182438 | E1 non-UE associated procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182439 | E1 non-UE associated functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182440 | Initial access in NG-RAN with separated CP and UP | Intel Corporation | imported from 3GU |
| R3‑182441 | (TP for CPUP_Split BL CR for TS 38.401): Resolve FFS in procedures in TS 38.401 | Ericsson | imported from 3GU |
| R3‑182442 | Bearer Context Setup procedure | Ericsson | imported from 3GU |
| R3‑182443 | pCR to 38.462 on initial TPs | Huawei | imported from 3GU |
| R3‑182444 | Introduction of early data transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑182445 | Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone | imported from 3GU |
| R3‑182446 | Summary of offline discussion on presence of slicing information | Huawei | imported from 3GU |
| R3‑182447 | Summary of discussion on AMF Relocation | Ericsson | imported from 3GU |
| R3‑182448 | Summary of discussions on Allowed NSSAI usage | Ericsson | imported from 3GU |
| R3‑182449 | New cause value in HO procedures for slicing | Huawei | imported from 3GU |
| R3‑182450 | Further Discussion and 38.300 TP on Slice Aware Mobility | ZTE | imported from 3GU |
| R3‑182451 | (TP for NR BL CR for TS 38.473): non-backward correction on Transport Layer - EN-DC | Huawei | imported from 3GU |
| R3‑182452 | TP for NR BL CR for TS 38.473): Clean-up for Multiple SCTP - SA | Huawei | imported from 3GU |
| R3‑182453 | (TP for NR BL CR SA for TS 38.473) Measurement configuration | Ericsson | imported from 3GU |
| R3‑182454 | Clarifications on multiple TNL associations | Ericsson | imported from 3GU |
| R3‑182455 | (TP for NR BL CR for TS 38.401): Clarifications on multiple TNL associations | Ericsson | imported from 3GU |
| R3‑182456 | (TP for NR BL CR for TS 38.473): on Cell Barred Info exchange over F1 interface | Huawei | imported from 3GU |
| R3‑182457 | (TP for NR BL CR for TS 38.473): UE identities for RAN and CN paging | Ericsson | imported from 3GU |
| R3‑182458 | pCR to TR 38874 | Qualcomm Incorporated, KDDI, AT&T, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel, LG Electronics, CMCC, Samsung | imported from 3GU |
| R3‑182459 | (TP for NR BL CR for TS 38.473): Establishment of DRB QoS in CU-DU architecture | Ericsson, Vodafone | imported from 3GU |
| R3‑182460 | (TP for NR BL CR for TS 38.470) QoS handling for SA over F1 | Nokia, Nokia Shanghai Bell, CMCC, Deutsche Telekom, KT, Verizon Wireless | imported from 3GU |
| R3‑182461 | Summary of offline discussions on UE inactivity monitoring | Samsung | imported from 3GU |
| R3‑182462 | TP for TS38.463 on E1 procedure for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182463 | (EN-DC BL CR for TS 38.473) UE Inactivity Monitoring support over F1 | Samsung | imported from 3GU |
| R3‑182464 | Adding new F1 procedure for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182465 | User Inactivity monitoring in NG-RAN function split architecture | Samsung | imported from 3GU |
| R3‑182466 | Introduction of assistance information for DL PDCP duplication | Ericsson | imported from 3GU |
| R3‑182467 | (TP for NR BL CR for TS 38.473): on CA-based SRB duplication | Huawei | imported from 3GU |
| R3‑182468 | [DRAFT] Reply LS LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | Huawei | imported from 3GU |
| R3‑182469 | TP for PDU sessions modified in Path Switch request | CATT | imported from 3GU |
| R3‑182470 | CR to TS38.401 on UL blockage | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182471 | CR to TS38.425 on UL blockage | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182472 | Clean up Signaling of NAS PDU in PDU Session management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182473 | Paging procedure (P-CR 38.413) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182474 | (TP for EN-DC BL CR) ASN.1 correction for BroadcastPLMNs-Item | Huawei | imported from 3GU |
| R3‑182475 | CR to 37.340 on support of UE capability coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑182476 | CR to 36.423 on support of UE capability coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑182477 | [Draft] LS on use of SPID for EN-DC | Ericsson | imported from 3GU |
| R3‑182478 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson | imported from 3GU |
| R3‑182479 | Reply LS on SN triggered fullConfig indication in X2 for EN-DC | Google Inc. | imported from 3GU |
| R3‑182480 | Addiiton of the full config indicator | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182481 | Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | RAN2, Qualcomm | imported from 3GU |
| R3‑182482 | Reply LS to SA3 on encryption of broadcast positioning information | RAN2, Ericsson | imported from 3GU |
| R3‑182483 | Reply LS on 5G-S-TMSI | SA2, Ericsson | imported from 3GU |
| R3‑182484 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| R3‑182485 | LS on use of SPID for EN-DC | Ericsson | imported from 3GU |
| R3‑182486 | LS on measurement gap configuration for gNB-CU/DU split scenario | CATT | imported from 3GU |
| R3‑182487 | Introduction of of UL/SUL indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182488 | Xn setup and NG-RAN node configuration update | Huawei | imported from 3GU |
| R3‑182489 | [DRAFT] LS on network vendor specific container | Nokia | imported from 3GU |
| R3‑182490 | TP for NR BL CR for TS 38.473): Clean-up for Multiple SCTP - SA | Huawei | imported from 3GU |
| R3‑182491 | Summary of the discussion on UE capability and UE power coordination for EN-DC scenario | CATT | imported from 3GU |
| R3‑182492 | Reply LS on TAI and forbidden TAI List for 5GS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182493 | Data forwarding for intra-system NG based HO | Samsung | imported from 3GU |
| R3‑182494 | Stage 3 design of RAN notification area | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182495 | Draft LS: --- | Qualcomm | imported from 3GU |
| R3‑182496 | Introduction of UE differentiation | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑182497 | LS on UE differentiation in NB-IoT | Huawei | imported from 3GU |
| R3‑182498 | E1 non-UE associated functions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182499 | Initial access in NG-RAN with separated CP and UP | Intel Corporation | imported from 3GU |
| R3‑182500 | Reference QoS profile indication from 5GC | Nokia, Nokia Shanghai Bell, Intel Corporation, LG Electronics Inc., Huawei, CMCC | imported from 3GU |
| R3‑182501 | (EN-DC BL CR for TS 38.473) UE Inactivity Monitoring support over F1 | Samsung | imported from 3GU |
| R3‑182502 | Adding new F1 procedure for User Inactivity Notification | Samsung | imported from 3GU |
| R3‑182503 | (TP for NR BL CR for TS 38.473): on CA-based SRB duplication | Huawei | imported from 3GU |
| R3‑182504 | Introduction of LTE-M (eMTC) traffic Differentiation | Huawei | imported from 3GU |
| R3‑182505 | Reply LS LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | Huawei | imported from 3GU |
| R3‑182506 | Introduction of early data transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑182507 | [Draft]reply LS on Clarification on GTP-U "Long PDCP PDU Number" extension header | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182508 | Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone | imported from 3GU |
| R3‑182509 | LS on UE differentiation in NB-IoT | Vodafone | imported from 3GU |
| R3‑182510 | Introduction of UE differentiation | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑182511 | Introduction of the vendor specific UE differentiation Information | Ericsson, Vodafone | imported from 3GU |
| R3‑182512 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑182513 | Support of Enhanced VoLTE Performance | Huawei, CATT, China Telecom, China Unicom, CMCC, Intel Corporation, Qualcomm Incorporated, Telecom Italia, ZTE | imported from 3GU |
| R3‑182514 | (TP for NR BL CR for TS 38.473): UE identities for RAN and CN paging | Ericsson | imported from 3GU |
| R3‑182515 | (TP for NR BL CR for TS 38.473): Establishment of DRB QoS in CU-DU architecture | Ericsson, Vodafone | imported from 3GU |
| R3‑182516 | Reply LS on Clarification on GTP-U "Long PDCP PDU Number" extension header | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182517 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99Bis on NR | NEC | imported from 3GU |
| R3‑182518 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99Bis on CPUP_Split | NEC | imported from 3GU |
| R3‑182519 | Baseline CR for June version of TS 38.470 covering agreements of RAN3#99Bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182520 | Baseline CR for June version of TS 38.473 covering agreements of RAN3#99Bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182521 | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99Bis | Nokia UK | imported from 3GU |
| R3‑182522 | TS 29.413 v0.1.0 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182523 | TS 38.410 v0.9.0 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182524 | TS 38.413 v0.8.0 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182525 | TS 38.415 v0.1.0 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182526 | TS 38.420 v0.8.0 covering agreements of RAN3#99Bis | Qualcomm | imported from 3GU |
| R3‑182527 | TS 38.423 v0.8.0 covering agreements of RAN3#99Bis | Ericsson | imported from 3GU |
| R3‑182528 | TS 38.424 v0.4.0 covering agreements of RAN3#99Bis | Mitsubishi Electric | imported from 3GU |
| R3‑182529 | TS 38.460 v0.2.0 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182530 | TS 38.462 v0.1.0 covering agreements of RAN3#99Bis | Huawei | imported from 3GU |
| R3‑182531 | TS 38.463 v0.2.0 covering agreements of RAN3#99Bis | Ericsson | imported from 3GU |
| R3‑182532 | Baseline CR for June version of TS 36.413 covering agreements of RAN3#99Bis | Nokia Shanghai Bell | imported from 3GU |
| R3‑182533 | Baseline CR for LTE-NR coexistence for TS 36.423 covering agreements of RAN3#99Bis | Ericsson | imported from 3GU |
| R3‑182534 | Baseline CR for essential corrections of TS 38.473 covering agreements of RAN3#99bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182535 | Baseline CR for June version of TS 38.470 covering agreements of RAN3#99Bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182536 | TS 38.410 v0.9.1 covering agreements of RAN3#99Bis | Nokia | imported from 3GU |
| R3‑182537 | Adding new F1 procedure for User Inactivity Notification | Samsung R&D Institute UK | imported from 3GU |
| R3‑182538 | Support of TEID change at SN | Huawei | imported from 3GU |
page generated from database: 2024-07-20 12:15:34