3GPP TDocs (written contributions) at meeting
Meeting: R3-100 - 2018-05-21 to 2018-05-25, Busan
meeting id: R3-100 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑182540 | RAN3-100 meeting Agenda | Chairman (Ericsson) | imported from 3GU |
| R3‑182541 | RAN3-99Bis meeting Report | MCC | imported from 3GU |
| R3‑182542 | En-gNB X2 TNL Address Discovery for option 3 | Huawei | imported from 3GU |
| R3‑182543 | Stage 2 CR for en-gNB X2 TNL Address Discovery for option 3 | Huawei | imported from 3GU |
| R3‑182544 | Stage 3 CR for en-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑182545 | State transition from inactive to idle state | Huawei | imported from 3GU |
| R3‑182546 | (TP for NR BL CR for TS 38.300): Network initiated state transition from inacitve state to idle state | Huawei | imported from 3GU |
| R3‑182547 | TP for 38.410 for support of location reporting function in NG-RAN | Huawei | imported from 3GU |
| R3‑182548 | Removal of FFSes in location reporting procedure | Huawei | imported from 3GU |
| R3‑182549 | TP for 38.423 for removal FFSes in location reporting procedure | Huawei | imported from 3GU |
| R3‑182550 | Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | 3GPP CT4 | imported from 3GU |
| R3‑182551 | LS on NR UE feature list | 3GPP RAN1 | imported from 3GU |
| R3‑182552 | LS on RRC and LPP parameter list for further NB-IoT enhancements | 3GPP RAN1 | imported from 3GU |
| R3‑182553 | Reply LS on adding new service type in QMC reporting | 3GPP RAN2 | imported from 3GU |
| R3‑182554 | Reply LS on SpCell selection in gNB-CU/DU configuration | 3GPP RAN2 | imported from 3GU |
| R3‑182555 | LS on secondary RAT data volume counting for EN-DC | 3GPP RAN2 | imported from 3GU |
| R3‑182556 | LS on Bluetooth/WLAN measurement collection in MDT | 3GPP RAN2 | imported from 3GU |
| R3‑182557 | LS on MSG3 size reduction | 3GPP RAN2 | imported from 3GU |
| R3‑182558 | LS on different CGIs for different SSBs | 3GPP RAN2 | imported from 3GU |
| R3‑182559 | LS response on Applying Xn and NG HO procedure for Inter-RA Mobility | 3GPP SA2 | imported from 3GU |
| R3‑182560 | LS response on LS on Support User Plane Encryption in UP security policy | 3GPP SA2 | imported from 3GU |
| R3‑182561 | LS response on LS on UP Security Policy | 3GPP SA2 | imported from 3GU |
| R3‑182562 | Reply LS on QoS | 3GPP SA2 | imported from 3GU |
| R3‑182563 | Reply LS on coexistence between RRC inactive and dual connectivity | 3GPP SA2 | imported from 3GU |
| R3‑182564 | LS on clarification of NSSAI information exchange during Inactive to connected mode transition | 3GPP SA2 | imported from 3GU |
| R3‑182565 | Reply LS on secured Signalling-only connection | 3GPP SA2 | imported from 3GU |
| R3‑182566 | Reply LS on paging with IMSI/SUCI in 5GS | 3GPP SA2 | imported from 3GU |
| R3‑182567 | LS OUT on UE capability related to integrity protection of DRBs | 3GPP SA2 | imported from 3GU |
| R3‑182568 | LS on aspects of handling large UE radio capabilities in EPC | 3GPP SA2 | imported from 3GU |
| R3‑182569 | LS on optimisation of UE capability signalling | 3GPP SA2 | imported from 3GU |
| R3‑182570 | LS on MDBV for delay critical QoS flows | 3GPP SA2 | imported from 3GU |
| R3‑182571 | Reply LS on INOBEAR | 3GPP SA2 | imported from 3GU |
| R3‑182572 | Reply LS to LS on Secured Signalling-only connection | 3GPP SA3 | imported from 3GU |
| R3‑182573 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99Bis on NR | NEC | imported from 3GU |
| R3‑182574 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99Bis on CPUP_Split | NEC | imported from 3GU |
| R3‑182575 | Baseline CR for June version of TS 38.470 covering agreements of RAN3#99Bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182576 | Baseline CR for June version of TS 38.473 covering agreements of RAN3#99Bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182577 | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99Bis | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182578 | Baseline CR for June version of TS 36.413 covering agreements of RAN3#99Bis | Nokia Shanghai Bell | imported from 3GU |
| R3‑182579 | Baseline CR for LTE-NR coexistence for TS 36.423 covering agreements of RAN3#99Bis | Ericsson | imported from 3GU |
| R3‑182580 | Baseline CR for essential corrections of TS 38.473 covering agreements of RAN3#99bis | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑182581 | Baseline CR: Introduction of assistance information for DL PDCP duplication | Ericsson | imported from 3GU |
| R3‑182582 | Baseline CR: Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182583 | Baseline CR: Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑182584 | Discussion on IAB architecture 1a | KDDI Corporation, Kyocera | imported from 3GU |
| R3‑182585 | Discussion on IAB architecture 1b | KDDI Corporation, Kyocera | imported from 3GU |
| R3‑182586 | Consideration on NSA operation in architectures, 1a, 1b and 2a | KDDI Corporation, Kyocera | imported from 3GU |
| R3‑182587 | Discussion on IAB Setup procedures | KDDI Corporation, Kyocera | imported from 3GU |
| R3‑182588 | Consideration on IAB node discovery and connection establishment | KDDI Corporation, Kyocera | imported from 3GU |
| R3‑182589 | Registration with AMF Reallocation | Interdigital Asia LLC | imported from 3GU |
| R3‑182590 | Reply LS on Secondary RAT data volume counting for EN DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182591 | Signaling 5QI in QoS Profile | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182592 | Signaling 5QI in QoS Profile | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182593 | LS on signaling of dynamic 5QI values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182594 | Handling of notification control in TS 38.423 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182595 | (TP for SA BL CR for TS 38.473): Handling of notification control in TS 38.473 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182596 | Registration with AMF re-allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182597 | Registration with AMF re-allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182598 | Frequency prioritization based on slices | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182599 | Reply LS regarding RAN support for Network Slicing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182600 | Stage 3 TP for Signalling of allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182601 | (TP for NR BL CR for TS 38.300) Signalling of allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182602 | Reply LS on Allowed NSSAI indication to RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182603 | Completion of paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182604 | (TP for NR BL CR for TS 38.300) Handling of forwarding tunnels | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182605 | Completion of data forwarding encoding in TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182606 | Clean up Signaling of NAS PDU in PDU Session management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182607 | Completion of PDU session & Qos flow release in TS38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182608 | (TP for NR BL CR for TS 38.300) Definition of RAN Notification Area | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182609 | (TP for NR BL CR for TS 38.300) TP for Handling of class 1 signaling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182610 | TP for Handling of class 1 signaling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182611 | (TP for NR BL CR for TS 38.300) Tracking area of interest in RRC inactive state | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182612 | Tracking area of interest in RRC inactive state. | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182613 | Tracking area of interest in RRC inactive state. | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182614 | Text Proposal for Xn Assistance Data for RAN Paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182615 | Handling Paging priority over Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182616 | (TP for NR BL CR for TS 38.300) UE context retrieval when UE moves out of RNA | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182617 | UE context retrieval when UE moves out of RNA | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182618 | Rapporteur’s updates for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182619 | Rapporteur’s updates forTS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182620 | Support of secured signaling only connections | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182621 | Baseline CR: Introduction of early data transmission | Huawei, China Telecom, CMCC, Qualcomm Incorporated, China Unicom | imported from 3GU |
| R3‑182622 | Baseline CR: Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
| R3‑182623 | Baseline CR: Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
| R3‑182624 | Baseline CR: Introduction of UE differentiation | Ericsson, Vodafone, Huawei | imported from 3GU |
| R3‑182625 | Further Discussion and 38.423 pCR on Xn Notification | ZTE | imported from 3GU |
| R3‑182626 | Clarification of IE Additional QoS Flow Information | ZTE | imported from 3GU |
| R3‑182627 | TS38.423 pCR on Slice not supported | ZTE | imported from 3GU |
| R3‑182628 | Further Discussion and TS38.413 pCR for UP Security Handling | ZTE | imported from 3GU |
| R3‑182629 | TS38.423 pCR for UP Security Handling | ZTE | imported from 3GU |
| R3‑182630 | Further Discussion on Reporting Security Result via Notify | ZTE | imported from 3GU |
| R3‑182631 | Further Discussion and 38.413 pCR on NG Handover Type | ZTE | imported from 3GU |
| R3‑182632 | Further Discussion and 38.413 pCR on NG Handover Type | ZTE | imported from 3GU |
| R3‑182633 | TS38.413 pCR on Configuring Index to RFSP info During NG Mobility | ZTE | imported from 3GU |
| R3‑182634 | TS38.423 pCR on Configuring Index to RFSP info During Xn Mobility | ZTE | imported from 3GU |
| R3‑182635 | TS38.423 pCR about RRC Container References | ZTE | imported from 3GU |
| R3‑182636 | Further Discussion and 38.423 pCR on Setting RLC Mode | ZTE | imported from 3GU |
| R3‑182637 | Further Discussion and 38.423 pCR on MR-DC@5GC Operations | ZTE | imported from 3GU |
| R3‑182638 | TS38.413 pCR on Location Report for N3IWF Node | ZTE | imported from 3GU |
| R3‑182639 | Further Discussion and 38.423 pCR on RNA IE Structure | ZTE | imported from 3GU |
| R3‑182640 | Further Discussion and 38.413 pCR on UE Context Release in RRC_INACTIVE State | ZTE | imported from 3GU |
| R3‑182641 | Further Discussion on MR-DC Coexisting with INACTIVE State | ZTE | imported from 3GU |
| R3‑182642 | Further Updates of TS 38.414 v0.5.0 | ZTE | imported from 3GU |
| R3‑182643 | Further Discussion and 38.300 TP on Cell Radio Resource Sharing | ZTE | imported from 3GU |
| R3‑182644 | Further Discussion and TS38.401 TP on Multi-Connectivity with DualMultiple gNB-DUs | ZTE | imported from 3GU |
| R3‑182645 | Leftover issues for Early Data Transmission | Huawei, China Unicom | imported from 3GU |
| R3‑182646 | Introduction of early data transmission | Huawei, China Telecom, CMCC | imported from 3GU |
| R3‑182647 | Introduction of Early Data Transmission | Huawei, China Telecom, CMCC, China Unicom | imported from 3GU |
| R3‑182648 | [Draft] Reply LS on EDT procedures and AS NAS interaction | Huawei | imported from 3GU |
| R3‑182649 | Reason for SgNB Addition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182650 | Synchronisation of the RLC reset at the assisting node and the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182651 | Indication of the RLC Reset at the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182652 | Correction of the SgNB Reconfiguration Completion procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182653 | Clarification of the cells used in the SgNB Addition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182654 | Correction of the mandatory presence of the UE ID in the X2 Partial Reset | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182655 | Adding missing relation for the TEID | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182656 | Various corrections for the NR UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182657 | Combined solution for AMBR in EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182658 | Addition of the new TEIDs for signalling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182659 | Addition of the new TEIDs for signalling and AMBR IEs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182660 | PDUs for AMBR Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182661 | More details for the UE AMBR specification | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182662 | Further discussion on UE radio capability enquiry | Huawei | imported from 3GU |
| R3‑182663 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182664 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182665 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182666 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182667 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182668 | Clarification on Connection Establishment Indication procedure scenarios | Huawei, Ericsson, NEC, Samsung, CATT, Nokia | imported from 3GU |
| R3‑182669 | Leftover FFS in UE Differentiation topic | Huawei, China Unicom | imported from 3GU |
| R3‑182670 | Disaggregated ng-eNB connecting to 5GC | Huawei, China Unicom | imported from 3GU |
| R3‑182671 | Disaggregated eNB connecting to EPC | Huawei, China Unicom | imported from 3GU |
| R3‑182672 | W1 interface general aspects and principles | Huawei, China Unicom | imported from 3GU |
| R3‑182673 | W1 interface layer1 | Huawei, China Unicom | imported from 3GU |
| R3‑182674 | W1 interface Data Transport Protocol | Huawei, China Unicom | imported from 3GU |
| R3‑182675 | W1 interface User Plane Protocol | Huawei, China Unicom | imported from 3GU |
| R3‑182676 | W1 interface signalling transport | Huawei, China Unicom | imported from 3GU |
| R3‑182677 | W1 Interface Application Protocol | Huawei, China Unicom | imported from 3GU |
| R3‑182678 | X2 partial reset for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182679 | TP for NGAP GUAMI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182680 | TP to support selective activation of UP connection of existing PDU Sessions | Nokia, Nokia Shanghai Bell, Intel Corporation | imported from 3GU |
| R3‑182681 | (TP for NR BL CR for TS 38.401) SCTP association for F1AP Initial UL RRC Message Transfer procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182682 | (TP for SA BL CR for TS 38.473): SCTP association for F1AP Initial UL RRC Message Transfer procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182683 | (TP for NR BL CR for TS 38.401): Overload Control in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182684 | TP for NGAP Overload Control | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182685 | TP for TS29.413 with update to align with TS38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182686 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑182687 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑182688 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson, AT&T | imported from 3GU |
| R3‑182689 | Final Frame Indication | Ericsson | imported from 3GU |
| R3‑182690 | Introduction of NR-U Sequence Number for UL | Ericsson, Telecom Italia | imported from 3GU |
| R3‑182691 | Assistance Information Broadcasting | Ericsson | imported from 3GU |
| R3‑182692 | Discussion on future extensions of CHOICE types | Ericsson | imported from 3GU |
| R3‑182693 | Introduction of QMC for MTSI in UTRAN and EUTRAN | Ericsson | imported from 3GU |
| R3‑182694 | Draft reply LS on adding new service type in QMC reporting | Ericsson | imported from 3GU |
| R3‑182695 | Correction on Additional QoS information | Ericsson | imported from 3GU |
| R3‑182696 | Introduction of “Additional QoS flow Information” in XnAP | Ericsson | imported from 3GU |
| R3‑182697 | (TP for NR BL CR for TS 37.340): Notification Control – Text proposal for 37.340 | Ericsson | imported from 3GU |
| R3‑182698 | (TP for NR BL CR for TS 38.300): Notification Control – Text proposal for 38.300 | Ericsson | imported from 3GU |
| R3‑182699 | Notification Control – Text proposal for 38.423 | Ericsson | imported from 3GU |
| R3‑182700 | Discussion on Allowed NSSAI for Frequency Priority Selection | Ericsson | imported from 3GU |
| R3‑182701 | Introduction of NR and E-UTRA neighbour information | Ericsson | imported from 3GU |
| R3‑182702 | Filling holes in APs with security related content | Ericsson | imported from 3GU |
| R3‑182703 | Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – HO aspects | Ericsson, Vodafone, KT, AT&T, Intel | imported from 3GU |
| R3‑182704 | (TP for NR BL CR for TS 38.300): Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – HO aspects | Ericsson | imported from 3GU |
| R3‑182705 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.413 | Ericsson | imported from 3GU |
| R3‑182706 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.423 | Ericsson | imported from 3GU |
| R3‑182707 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.413 | Ericsson | imported from 3GU |
| R3‑182708 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.423 | Ericsson | imported from 3GU |
| R3‑182709 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.300 | Ericsson | imported from 3GU |
| R3‑182710 | Introducing CM-Connected Mobility Restrictions | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182711 | Introduction of 5GS restriction in S1AP | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182712 | Introduction of 5GS restriction in X2AP | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182713 | Introduction of CM-CONNECTED Mobility Restrictions in XnAP | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182714 | [DRAFT] LS on 5G CM-Connected Mobility Restrictions | Ericsson | imported from 3GU |
| R3‑182715 | Data forwarding handling from 4G to 5G | Ericsson | imported from 3GU |
| R3‑182716 | Data forwarding handling from 5G to 4G | Ericsson | imported from 3GU |
| R3‑182717 | Data Forwarding – Common Aspects | Ericsson | imported from 3GU |
| R3‑182718 | How should the AMF or the N3IWF react while receiving a message not specified in 29.413? | Ericsson | imported from 3GU |
| R3‑182719 | Partial Xn Reset – Text Proposal for 38.420 | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182720 | Partial Xn Reset – XNAP Text Proposal | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑182721 | How to realise UE Context Retrieval for RRC_INACTIVE with no Xn connectivity | Ericsson | imported from 3GU |
| R3‑182722 | (TP for NR BL CR for TS 38.300): NG based UE context retrieval | Ericsson | imported from 3GU |
| R3‑182723 | NGAP TP to support NG-based UE Context Retrieval | Ericsson | imported from 3GU |
| R3‑182724 | TP for 38.410 to introduce support of NG-based relay of XnAP messages | Ericsson | imported from 3GU |
| R3‑182725 | Including RANAC in Xn Setup and NG-RAN node Configuration Update messages | Ericsson | imported from 3GU |
| R3‑182726 | Resolving open issues on RAN Paging Area and RAN Area | Ericsson | imported from 3GU |
| R3‑182727 | 5GS Location Reporting continued – NGAP text proposal | Ericsson | imported from 3GU |
| R3‑182728 | 5GS Location Reporting continued – XnAP Text Proposal | Ericsson | imported from 3GU |
| R3‑182729 | [DRAFT] LS on Location Reporting for Area of Interest | Ericsson | imported from 3GU |
| R3‑182730 | AP ID handling and related Cause Values | Ericsson | imported from 3GU |
| R3‑182731 | Cause Value corrections on NGAP | Ericsson | imported from 3GU |
| R3‑182732 | Cause values on XnAP | Ericsson | imported from 3GU |
| R3‑182733 | Reviewing Restructured DC messages for MN iniated procedures – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182734 | How to apply principle of resturctured DC messages on SN initiated procedures – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182735 | (TP for NR BL CR for TS 38.300): Support of SN initiated QoS flow offload | Ericsson | imported from 3GU |
| R3‑182736 | (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‑182737 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑182738 | PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑182739 | (TP for NR BL CR for TS 37.340): PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑182740 | Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – DC aspects | Ericsson, Vodafone, KT, AT&T, Intel | imported from 3GU |
| R3‑182741 | (TP for NR BL CR for TS 37.340): Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑182742 | Centralised User Plane – Dual Connectivity – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182743 | Data forwarding aspects for DC bearer type change and QoS flow offloading | Ericsson | imported from 3GU |
| R3‑182744 | (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‑182745 | Data forwarding aspects for intra-system ACTIVE mobility – DC TP for XnAP | Ericsson | imported from 3GU |
| R3‑182746 | Introducing SN initiated SN Change procedure in XnAP | Ericsson | imported from 3GU |
| R3‑182747 | Correction of presence of Highest retransmitted SN | Ericsson | imported from 3GU |
| R3‑182748 | Correction of presence of Highest retransmitted SN | Ericsson | imported from 3GU |
| R3‑182749 | UP version handling paper NR UP SN for UL | Ericsson | imported from 3GU |
| R3‑182750 | E1 support for UP version handling | Ericsson | imported from 3GU |
| R3‑182751 | (TP for SA BL CR for TS 38.473): F1 support for UP version handling | Ericsson | imported from 3GU |
| R3‑182752 | Radio quality information report activation | Ericsson | imported from 3GU |
| R3‑182753 | Radio quality information report activation | Ericsson | imported from 3GU |
| R3‑182754 | Final Frame Indication | Ericsson | imported from 3GU |
| R3‑182755 | Introduction of NR-U Sequence Number for UL PDU | Ericsson, Telecom Italia | imported from 3GU |
| R3‑182756 | (TP for SA BL CR for TS 38.473): Access class barring for F1 | Ericsson | imported from 3GU |
| R3‑182757 | (TP for SA BL CR for TS 38.473): Other SI delivery command | Ericsson | imported from 3GU |
| R3‑182758 | (TP for SA BL CR for TS 38.473): Public Warning System for F1 | Ericsson | imported from 3GU |
| R3‑182759 | (TP for SA BL CR for TS 38.473): Paging over F1 | Ericsson | imported from 3GU |
| R3‑182760 | (TP for SA BL CR for TS 38.473): Cell information over F1 | Ericsson | imported from 3GU |
| R3‑182761 | (TP for NR BL CR for TS 38.470): Removal of gNB DU Measurement reporting function | Ericsson | imported from 3GU |
| R3‑182762 | Rapporteur’s input TS 38.423 version 0.8.0 | Ericsson | imported from 3GU |
| R3‑182763 | TP on general FFS’s | Ericsson | imported from 3GU |
| R3‑182764 | TP on E-CID related information | Ericsson | imported from 3GU |
| R3‑182765 | TP on OTDOA related information | Ericsson | imported from 3GU |
| R3‑182766 | NRPPa ASN.1 | Ericsson | imported from 3GU |
| R3‑182767 | NR Measurements in LPPa E-CID | Ericsson | imported from 3GU |
| R3‑182768 | Inter-RAT Measurements for E-CID | Ericsson | imported from 3GU |
| R3‑182769 | Discussion on UE differentiation for NB-IoT | Ericsson | imported from 3GU |
| R3‑182770 | [Draft] Reply LS on Reply LS on UE differentiation for NB-IoT from SA2 | Ericsson | imported from 3GU |
| R3‑182771 | Assistance Information Broadcast Procedure in LPPa | Ericsson | imported from 3GU |
| R3‑182772 | Assistance Data Signaling in LPPa | Ericsson | imported from 3GU |
| R3‑182773 | (TP for LTE Aerial CR for TS 36.423): Resolving the remaining issues | Ericsson | imported from 3GU |
| R3‑182774 | Discussion on the remaining FFS on Aerial | Ericsson | imported from 3GU |
| R3‑182775 | (TP for NR BL CR for TS 38.401): Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – E1 aspects | Ericsson | imported from 3GU |
| R3‑182776 | Network Synchronization for IAB Nodes | Ericsson | imported from 3GU |
| R3‑182777 | Protocol Stack for IAB Architecture 1a and 1b | Ericsson | imported from 3GU |
| R3‑182778 | CN functions for supporting IAB nodes | Ericsson | imported from 3GU |
| R3‑182779 | Setup Procedure for the Adaptation Layer of an IAB system | Ericsson | imported from 3GU |
| R3‑182780 | Setup procedures for IAB-node and a UE connected to an IAB node | Ericsson | imported from 3GU |
| R3‑182781 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑182782 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑182783 | LPPa Rapporteur Update | Ericsson | imported from 3GU |
| R3‑182784 | Rapporteur’s corrections on the specification | Ericsson | imported from 3GU |
| R3‑182785 | Signalling procedures for broadcasting of assistance data | Huawei | imported from 3GU |
| R3‑182786 | Introduction of signalling procedures for broadcasting of assistance data_WA solution | Huawei | imported from 3GU |
| R3‑182787 | Introduction of signalling procedures for broadcasting of assistance data | Huawei | imported from 3GU |
| R3‑182788 | Considerations on adaptation layer in IAB | ZTE Corporation | imported from 3GU |
| R3‑182789 | Discussion on Secondary RAT data volume reporting | ZTE Corporation | imported from 3GU |
| R3‑182790 | Considerations on IAB deployment scenarios | ZTE Corporation | imported from 3GU |
| R3‑182791 | CR37.340 for Secondary RAT data volume reporting | ZTE Corporation | imported from 3GU |
| R3‑182792 | Discussion on control plane protocol for IAB | ZTE Corporation | imported from 3GU |
| R3‑182793 | Discussion on QoS and bearer mapping | ZTE Corporation | imported from 3GU |
| R3‑182794 | Consideration on Topology Management for IAB | ZTE Corporation | imported from 3GU |
| R3‑182795 | Consideration on Routing Design for IAB | ZTE Corporation | imported from 3GU |
| R3‑182796 | [DRAFT] Reply LS on secondary RAT data volume counting for EN-DC | ZTE Corporation | imported from 3GU |
| R3‑182797 | Considerations on Data Forwarding tunneling and End Marker | CATT | imported from 3GU |
| R3‑182798 | TP for NR BL CR for TS 38.300 on handling of UE Context release | CATT | imported from 3GU |
| R3‑182799 | TP for NR BL CR for TS 38.300 on RAN Paging priority | CATT | imported from 3GU |
| R3‑182800 | TP for NR BL CR for TS 38.423 on RAN Paging priority | CATT | imported from 3GU |
| R3‑182801 | TP for NR BL CR for TS 38.300 on RRC state report | CATT | imported from 3GU |
| R3‑182802 | TP for NR BL CR for TS 38.413 on RRC state report | CATT | imported from 3GU |
| R3‑182803 | LS on RRC State report | CATT | imported from 3GU |
| R3‑182804 | TP for NR BL CR for TS 38.413 on IMS voice fallback | CATT | imported from 3GU |
| R3‑182805 | Considerations on startup procedure for L2 IAB architecture | CATT | imported from 3GU |
| R3‑182806 | Considerations on bearer management for L2 IAB architecture | CATT | imported from 3GU |
| R3‑182807 | Considerations on Network topology and Route Selection | CATT | imported from 3GU |
| R3‑182808 | Adapter Layer Termination for L2 IAB architecture | CATT | imported from 3GU |
| R3‑182809 | Discussion on Cell information exchange related to wideband carrier | ZTE Corporation | imported from 3GU |
| R3‑182810 | Discussion on the remaining issue for SMTC transmission | ZTE Corporation | imported from 3GU |
| R3‑182811 | CR36.423 for the remaining issue for SMTC transmission | ZTE Corporation | imported from 3GU |
| R3‑182812 | (TP for EN-DC BL CR for TS 38.473): The remaining issue for SMTC transmission | ZTE Corporation | imported from 3GU |
| R3‑182813 | Further Correction on Session AMBR for MR-DC@5GC | ZTE Corporation | imported from 3GU |
| R3‑182814 | Correction on the same terminology of “Split SRB” in TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑182815 | Correction on same terminology of split SRB in TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑182816 | Correction on Split SRB configuration | ZTE Corporation | imported from 3GU |
| R3‑182817 | Correction of Split SRB configuration in TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑182818 | Correction of Split SRB configuration in TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑182819 | Clarifications on SgNB initiated SgNB Modification procedure | ZTE Corporation | imported from 3GU |
| R3‑182820 | Correction on SgNB initiated SgNB Modification procedure in TS37.340 | ZTE Corporation | imported from 3GU |
| R3‑182821 | S-RLF related information transmission in TS37.340 | ZTE Corporation | imported from 3GU |
| R3‑182822 | S-RLF related information transmission in TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑182823 | Discussion on truncation of I-RNTI for Msg3 | ZTE Corporation | imported from 3GU |
| R3‑182824 | [Draft]Reply LS on MSG3 size reduction | ZTE Corporation | imported from 3GU |
| R3‑182825 | TS38.413 pCR on Optionality of PDU Session tunnel for Data forwarding | ZTE Corporation | imported from 3GU |
| R3‑182826 | TS38.423 pCR on Optionality of PDU Session tunnel for Data forwarding | ZTE Corporation | imported from 3GU |
| R3‑182827 | Introduction of SMTC information for neighbour cells | CATT | imported from 3GU |
| R3‑182828 | (TP for EN-DC BL CR for TS 38.473)Introduction of SMTC information for neighbour cells | CATT | imported from 3GU |
| R3‑182829 | CR to 36.423 on SMTC information for neighbour cells | CATT | imported from 3GU |
| R3‑182830 | [DRAFT] LS to RAN2 on SMTC information for neighbour cells | CATT | imported from 3GU |
| R3‑182831 | (TP for PDCP dup Assist Info CR for TS 38.425)Correction on the granularity of Assist Information | CATT | imported from 3GU |
| R3‑182832 | (TP for SA BL CR for TS 38.473):Support of PDCP Duplication for DRB | CATT | imported from 3GU |
| R3‑182833 | (TP for SA BL CR for TS 38.473):Support of PDCP Duplication for SRB | CATT | imported from 3GU |
| R3‑182834 | Correction on SgNB initiated SgNB Modification procedure | CATT | imported from 3GU |
| R3‑182835 | Discussion on selection of SCG cells for EN-DC scenario | CATT | imported from 3GU |
| R3‑182836 | CR to 36.423 on EN-DC configuration update procedure | CATT | imported from 3GU |
| R3‑182837 | TP to 37.340 on SgNB Addition procedure | CATT | imported from 3GU |
| R3‑182838 | (TP for EN-DC BL CR for TS 38.473)Correction on UE Context Modification Confirm | CATT | imported from 3GU |
| R3‑182839 | Guidance on Secondary RAT Data Volume | KT Corp. | imported from 3GU |
| R3‑182840 | TP for Guidance on Secondary RAT Data Volume | KT Corp. | imported from 3GU |
| R3‑182841 | Discussion on supporting IAB in NSA | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182842 | Architecture and Protocols: Connectivity Service Solution for IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182843 | IAB Topology Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182844 | Bearer Context Modification Required procedure | LG Electronics Inc., KT Corp. | imported from 3GU |
| R3‑182845 | Reflective QoS support in E1 interface | LG Electronics Inc. | imported from 3GU |
| R3‑182846 | F1-U and F1-C backhauling between IAB Donor and IAB Node | LG Electronics Inc. | imported from 3GU |
| R3‑182847 | Flow Control enhancements for uplink PDCP duplication | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182848 | Flow Control for uplink PDCP duplication | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182849 | Flow Control enhancement for DRX | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182850 | Flow Control enhancement for DRX | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182851 | Flow Control enhancement for DL QoS flow remapping | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182852 | Flow Control enhancement for DL QoS flow remapping | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑182853 | Unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
| R3‑182854 | (TP for NR BL CR for TS 38.300): Stage 2 CR for network initiated state transition from inacitve state to idle state | Intel Corporation, Huawei | imported from 3GU |
| R3‑182855 | Stage-3 TP for Xn SN Status Transfer | Intel Corporation | imported from 3GU |
| R3‑182856 | QoS handling over F1 | ZTE Corporation | imported from 3GU |
| R3‑182857 | (TP for NR BL CR for TS38.470) Update on QoS information transfer | ZTE Corporation | imported from 3GU |
| R3‑182858 | (TP for SA BL CR for TS38.473) Update on QoS information transfer | ZTE Corporation | imported from 3GU |
| R3‑182859 | The F1 impact for Secured SRB-only connection | ZTE Corporation | imported from 3GU |
| R3‑182860 | (TP for EN-DC BL CR for TS38.473) Update for Secured SRB-only connection | ZTE Corporation | imported from 3GU |
| R3‑182861 | [DRAFT] LS on UE Registration without a PDU session setup | ZTE Corporation | imported from 3GU |
| R3‑182862 | (TP for SA BL CR for TS38.473) UE Reject Indication from CU to DU | ZTE Corporation | imported from 3GU |
| R3‑182863 | Discussion on Multiple CU-UPs impact on NG interface | ZTE Corporation | imported from 3GU |
| R3‑182864 | TP for TS38.413 on supporting multiple CU-UPs over NG interface | ZTE Corporation | imported from 3GU |
| R3‑182865 | Discussion on DL Data Notification over E1 interface | ZTE Corporation | imported from 3GU |
| R3‑182866 | Further consideration on AMF reallocation approaches | ZTE Corporation | imported from 3GU |
| R3‑182867 | Further consideration on Allowed NSSAI | ZTE Corporation | imported from 3GU |
| R3‑182868 | Overload control for unified access control | ZTE Corporation | imported from 3GU |
| R3‑182869 | (TP for SA BL CR for TS38.473)Further discussion on Access Control for F1 interface | ZTE Corporation | imported from 3GU |
| R3‑182870 | Update on E1 setup for TS38.463 | ZTE Corporation | imported from 3GU |
| R3‑182871 | TP for TS38.473 on E1 setup | ZTE Corporation | imported from 3GU |
| R3‑182872 | Discussion on PDCP COUNT wrap around | ZTE Corporation | imported from 3GU |
| R3‑182873 | (TP for NR BL CR for TS38.470)Support PWS in CU-DU deployment | ZTE Corporation | imported from 3GU |
| R3‑182874 | (TP for SA BL CR for TS38.473)Support PWS in CU-DU deployment | ZTE Corporation | imported from 3GU |
| R3‑182875 | (TP for NR BL CR for TS38.470)Further Discussion on Load Management | ZTE Corporation | imported from 3GU |
| R3‑182876 | (TP for SA BL CR for TS38.473)Further Discussion on Load Management | ZTE Corporation | imported from 3GU |
| R3‑182877 | TP for TS38.460 on UP information transfer over E1 | ZTE Corporation | imported from 3GU |
| R3‑182878 | Consideration on the enhancement for UL AMBR | ZTE Corporation | imported from 3GU |
| R3‑182879 | enhancement for UL AMBR for TS38.401 | ZTE Corporation | imported from 3GU |
| R3‑182880 | enhancement for UL AMBR for TS37.340 | ZTE Corporation | imported from 3GU |
| R3‑182881 | Centralized Retransmission in EN-DC for TS38.401 | ZTE Corporation | imported from 3GU |
| R3‑182882 | (TP for SA BL CR for TS 38.473) Further discussion CA-based SRB duplication | ZTE Corporation | imported from 3GU |
| R3‑182883 | Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑182884 | CR for Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑182885 | (TP for PDCP dup Assist Info CR for TS 38.425)Addition of UL information for the node hosting PDCP | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182886 | Maintaining the bearer type on wrap-around | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182887 | CR on maintaining the bearer type on wrap-around for TS37.340 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182888 | Further consideration on data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182889 | CR for Clarification of data volume reporting on TS37.340 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182890 | CR for Clarification of data volume reporting on TS38.401 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182891 | CR for Clarification of start or end timing for data volume reporting on TS36.413 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182892 | Clarification of start or end timing for data volume reporting on TS36.423 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182893 | [draft]LS on Secondary RAT data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182894 | Way forward on TNL Address Discovery for Option 3 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182895 | Further consideration on data existence indication for split bearer | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182896 | CR on data existence indication for split bearer | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182897 | (TP for EN-DC BL CR for TS 38.473)further consideration on Load managemen | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182898 | CR on Introduction of Load management for EN-DC over X2 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182899 | CR on clarification of retransmitted pakcets | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182900 | (TP for EN-DC BL CR for TS 38.473)SCG full coinfiguration over F1 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑182901 | Xn Notification Control TP for 38.420 | CATT | imported from 3GU |
| R3‑182902 | Xn Notification Control TP for 38.423 | CATT | imported from 3GU |
| R3‑182903 | (TP for NR BL CR for TS 38.470):F1 Notification Control | CATT | imported from 3GU |
| R3‑182904 | (TP for NR BL CR for TS 38.473):F1 Notification Control | CATT | imported from 3GU |
| R3‑182905 | TP for 38.413 on cause value Slice resources not available | CATT | imported from 3GU |
| R3‑182906 | TP for 38.423 on slice related cause value | CATT | imported from 3GU |
| R3‑182907 | TP for User Location Information | CATT | imported from 3GU |
| R3‑182908 | TP for accepted QoS flow list in Path Switch request | CATT | imported from 3GU |
| R3‑182909 | Discussion on QoS flow remapping | CATT | imported from 3GU |
| R3‑182910 | Solution on data forwarding | CATT | imported from 3GU |
| R3‑182911 | (TP for NR BL CR for TS 38.473) PWS over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182912 | (TP for NR BL CR for TS 38.401) User inactivity monitoring | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑182913 | (TP for NSA BL CR for TS 38.473) User inactivity monitoring | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑182914 | Completion of Xn setup stage 3 | Huawei | imported from 3GU |
| R3‑182915 | I-RNTI encoding and length reduction | Huawei | imported from 3GU |
| R3‑182916 | Solutions for UE moving out of RNA | Huawei | imported from 3GU |
| R3‑182917 | Exchange of RANAC over Xn and F1 | Huawei | imported from 3GU |
| R3‑182918 | (TP for SA BL CR for TS 38.473): Exchange of RANAC over Xn and F1 | Huawei | imported from 3GU |
| R3‑182919 | Update to RAN paging area IE | Huawei,Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182920 | Acquisition of neighbour cell's CSI-RS resource configuration | Huawei | imported from 3GU |
| R3‑182921 | ANR stage 2 clean up | Huawei | imported from 3GU |
| R3‑182922 | (TP for NR BL CR for TS 38.470) QoS handling for SA over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182923 | (TP for NSA BL CR for TS 38.473) Additional cause values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182924 | Handling of gNB-DU UE F1AP ID during RRC Connection Re-establishment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182925 | On Allowed NSSAI Usage | China Telecommunications | imported from 3GU |
| R3‑182926 | gNB-CU-UP notification function | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑182927 | gNB-CU-UP notification procedure | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑182928 | (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‑182929 | Information to be exchanged during E1 Setup (TS 38.460) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182930 | Information to be exchanged during E1 Setup (TS 38.463) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182931 | Multiple SCTP for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182932 | Filling holes in APs with security related content | Ericsson | imported from 3GU |
| R3‑182933 | Support of RNL initialisation of an additional NG-C TNL association – TP for 38.413 | Ericsson | imported from 3GU |
| R3‑182934 | draft LS on RAN3 progress on data forwarding for intra- and inter-system mobility | Ericsson | imported from 3GU |
| R3‑182935 | Introducing tabular definition of the DATA FORWARDING ADDRESS INDICATION message in XnAP | Ericsson | imported from 3GU |
| R3‑182936 | Correction of R3-181866 to cover data forwarding aspects | Ericsson | imported from 3GU |
| R3‑182937 | Correction of RRC Transfer procedure – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑182938 | Handling of PDCP Duplication on Xn | Ericsson | imported from 3GU |
| R3‑182939 | Correction for PDCP Duplication | Ericsson | imported from 3GU |
| R3‑182940 | (TP for LTE-NR coexistence BL CR for TS 36.423) E-UTRA - NR resource allocation coordination over X2 | Ericsson | imported from 3GU |
| R3‑182941 | E-UTRA - NR resource allocation coordination over Xn, TP for TS 38.423 | Ericsson | imported from 3GU |
| R3‑182942 | Update to XnAP list of functions - TP for TS 38.420 | Ericsson | imported from 3GU |
| R3‑182943 | Addition of an SN Change Indicator – based on CR1107r2 for TS36.423 R3-182480 | Ericsson | imported from 3GU |
| R3‑182944 | (TP for NR BL CR for TS 37.340): Addition of an SN Change Indicator – based on R3-182339 | Ericsson | imported from 3GU |
| R3‑182945 | Coordination of Inactivity for EN-DC | Ericsson | imported from 3GU |
| R3‑182946 | Coordination of Inactivity for EN-DC | Ericsson | imported from 3GU |
| R3‑182947 | Introduction of EN-DC | Ericsson | imported from 3GU |
| R3‑182948 | Secondary RAT Data Usage Report function | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182949 | Secondary RAT Data Usage Report procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182950 | Rapporteur update for TS 38.413 with ASN.1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182951 | Cleanup of NAS Transport procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182952 | Way forward for retrieval of UE Radio Capability information after establishment of the logical S1-connection | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, NEC, Qualcomm Incorporated, Samsung | imported from 3GU |
| R3‑182953 | [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‑182954 | Triggering UE capability info retrieval using DL NAS TRANSPORT (Stage 2) | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑182955 | Triggering UE capability info retrieval using DL NAS TRANSPORT | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑182956 | UE capability check for IMS voice | Qualcomm Incorporated, Huawei, T-Mobile USA INC., CMCC | imported from 3GU |
| R3‑182957 | (TP for SA BL CR for TS 38.473):Paging procedure clean-up | Qualcomm Incorporated | imported from 3GU |
| R3‑182958 | Paging procedure clean-up (P-CR 38.413) | Qualcomm Incorporated | imported from 3GU |
| R3‑182959 | UE capablity Indication (P-CR 38.413) | Qualcomm Incorporated | imported from 3GU |
| R3‑182960 | CN Type Indication in Emergency Fallback | Qualcomm Incorporated | imported from 3GU |
| R3‑182961 | (TP for SA BL CR for TS 38.473):ARFCN in served cell info | Qualcomm Incorporated | imported from 3GU |
| R3‑182962 | ARFCN in served cell info (pCR 38.423) | Qualcomm Incorporated | imported from 3GU |
| R3‑182963 | Serving cell list aware for LTE-NR coordination on RF coexistence | Qualcomm Incorporated, NTT DOCOMO INC | imported from 3GU |
| R3‑182964 | (TP for NB-IoT-Early-Data-TX BL CR for TS 36.413): MME awareness of Early Data Transmission | Qualcomm Incorporated, Huawei, Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑182965 | LTE-NR coordination for inter-modulation issue | Qualcomm Incorporated, NTT DOCOMO INC | imported from 3GU |
| R3‑182966 | Direct Data Forwarding in SgNB change | Qualcomm Incorporated | imported from 3GU |
| R3‑182967 | On I-RNTI partitioning for correctly addressing the old serving NG-RAN node | Ericsson | imported from 3GU |
| R3‑182968 | (TP for NR BL CR for TS 38.300): On definition of I-RNTI in 38.300 | Ericsson | imported from 3GU |
| R3‑182969 | [DRAFT] Reply LS on MSG3 size reduction | Ericsson | imported from 3GU |
| R3‑182970 | (TP for SA BL CR for 38.473) TAC usage in EN-DC | Huawei | imported from 3GU |
| R3‑182971 | (TP for SA BL CR for TS 38.473): Necessity of C-RNTI in Initial UL RRC Message Transfer procedure | LG Electronics Inc. | imported from 3GU |
| R3‑182972 | Overload control in NGAP | LG Electronics Inc. | imported from 3GU |
| R3‑182973 | TAC usage in EN-DC | Huawei | imported from 3GU |
| R3‑182974 | Introduction of Mobility Restriction List on NGAP | Huawei | imported from 3GU |
| R3‑182975 | Introduction of Mobility Restriction List on XnAP | Huawei | imported from 3GU |
| R3‑182976 | (TP for NR BL CR for TS 36.413) Introduction of CN type restriction | Huawei | imported from 3GU |
| R3‑182977 | Introduction of CN type restriction | Huawei | imported from 3GU |
| R3‑182978 | Solution Down-selection on UE-AMBR for EN-DC | LG Electronics, KT Corp. | imported from 3GU |
| R3‑182979 | TNL address discovery for EN-DC | LG Electronics, KT Corp. | imported from 3GU |
| R3‑182980 | Issues on Session AMBR for Option 7 family | LG Electronics, KT Corp. | imported from 3GU |
| R3‑182981 | Issue on bearer type selection for NGEN-DC DRB options | LG Electronics, KT Corp. | imported from 3GU |
| R3‑182982 | Procedures for Security Support in CU-CP UP Separation | LG Electronics, KT Corp. | imported from 3GU |
| R3‑182983 | Clarification of the default configuration behavior in SN change | Google Inc. | imported from 3GU |
| R3‑182984 | The MeNB behavior when receiving no RRC indication | Google Inc. | imported from 3GU |
| R3‑182985 | The MeNB behavior when receiving no RRC indication | Google Inc. | imported from 3GU |
| R3‑182986 | Default CU behavior when receiving no indication from DU | Google Inc. | imported from 3GU |
| R3‑182987 | (TP to EN-DC BL CR 38.473): Default CU behavior when receiving no indication from DU | Google Inc. | imported from 3GU |
| R3‑182988 | (TP for NR BL CR for TS 38.401): cell spans over multiple Dus | NEC | imported from 3GU |
| R3‑182989 | (TP for NR BL CR for TS 38.401): UE Context description in F1 | NEC | imported from 3GU |
| R3‑182990 | Presence of UE AP ID in Partial Reset | NEC | imported from 3GU |
| R3‑182991 | Correction of missing uL-Configuration in ASN.1 | NEC | imported from 3GU |
| R3‑182992 | PDU Type for DL and UL | NEC | imported from 3GU |
| R3‑182993 | User Inactivity handling over X2 EN-DC | NEC | imported from 3GU |
| R3‑182994 | User Inactivity handling over X2 EN-DC | NEC | imported from 3GU |
| R3‑182995 | Core Network Assistance Information | NEC | imported from 3GU |
| R3‑182996 | (TP for NR BL CR for TS 38.401): solving the FFS on RRC inactive | NEC | imported from 3GU |
| R3‑182997 | On the definition of RAN Paging Area – TP to 38.413 | NEC | imported from 3GU |
| R3‑182998 | On the definition of RAN Paging Area – TP to 38.423 | NEC | imported from 3GU |
| R3‑182999 | (TP for SA BL CR for TS 38.473): solving the FFS on 5G-S-TMSI | NEC | imported from 3GU |
| R3‑183000 | solving the FFS on QFI size | NEC | imported from 3GU |
| R3‑183001 | (TP for EN-DC BL CR for TS 38.473)How to extract PDCP SN for DL | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183002 | CR on how to extract PDCP SN for DL over X2 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183003 | Rapporteur proposal for editorial and other changes to TS38.425 | Samsung | imported from 3GU |
| R3‑183004 | Rapporteur’s update to TS38.425 v15.1.0 | Samsung | imported from 3GU |
| R3‑183005 | Data forwarding tunnel for inter-system HO | Samsung,KT Corp. | imported from 3GU |
| R3‑183006 | End marker handling in HO and DC | Samsung,KT Corp. | imported from 3GU |
| R3‑183007 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung,KT Corp. | imported from 3GU |
| R3‑183008 | Resolve some FFSs for handover procedures in XnAP | Samsung | imported from 3GU |
| R3‑183009 | Correction of handover procedures in NGAP | Samsung | imported from 3GU |
| R3‑183010 | (TP for NR BL CR for TS 38.300) RRC Inactive State Report | Samsung | imported from 3GU |
| R3‑183011 | Stage 3 TP on RRC Inactive Transition Report | Samsung | imported from 3GU |
| R3‑183012 | Considerations on the I-RNTI size for NR | Samsung | imported from 3GU |
| R3‑183013 | (TP for PDCP dup Assist Info CR for TS38.425) Further discussions on assistant information over F1 | Samsung, KT Corp. | imported from 3GU |
| R3‑183014 | (TP for NR BL CR for TS38.401) Discussions on supporting Msg3 based on-demand SI over F1 | Samsung, KT Corp. | imported from 3GU |
| R3‑183015 | (TP for SA BL CR for TS38.473) Discussions on supporting Msg3 based on-demand SI over F1 | Samsung, KT Corp. | imported from 3GU |
| R3‑183016 | Discussions on user plane protocol for IAB | Samsung | imported from 3GU |
| R3‑183017 | Adaptation layer location within the IAB donor node | Samsung | imported from 3GU |
| R3‑183018 | Discussions on control plane protocol for IAB | Samsung | imported from 3GU |
| R3‑183019 | UE Context Fetch Procedure in Xn | Samsung,KT Corp.,QC Incorporated,Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183020 | Security Information Transmission for HO-TP for Xn | Samsung | imported from 3GU |
| R3‑183021 | Security Information Transmission for HO-TP for NG | Samsung | imported from 3GU |
| R3‑183022 | DC establishment for PDCP Termination at SN-TP for 38.423 | Samsung | imported from 3GU |
| R3‑183023 | DC establishment for PDCP Termination at SN-TP for 37.340 | Samsung | imported from 3GU |
| R3‑183024 | Support of DRB offloading and QoS Flow offloading | Samsung | imported from 3GU |
| R3‑183025 | Addition of Cause Value | Samsung | imported from 3GU |
| R3‑183026 | Discussion for PCI Confusion | Samsung | imported from 3GU |
| R3‑183027 | Addition of MeNB cell ID to solve the PCI confusion | Samsung | imported from 3GU |
| R3‑183028 | Discussion on the extension of QFI -TP to Xn | Samsung | imported from 3GU |
| R3‑183029 | Discussion on the extension of QFI -TP to NG | Samsung | imported from 3GU |
| R3‑183030 | gNB-CU-UP selection function | Samsung, KT | imported from 3GU |
| R3‑183031 | TP for TS38.463 to support the load balancing of the gNB-CU-UPs connected to the same gNB-CU-CP | Samsung, KT | imported from 3GU |
| R3‑183032 | Allowed NSSAI | Huawei | imported from 3GU |
| R3‑183033 | [draft] Reply LS on Allowed NSSAI indication to RAN | Huawei | imported from 3GU |
| R3‑183034 | [draft] Reply LS regarding RAN support for NW slicing | Huawei | imported from 3GU |
| R3‑183035 | A new cause value for slice resource shortage | Huawei | imported from 3GU |
| R3‑183036 | A new cause value for slice resource shortage | Huawei | imported from 3GU |
| R3‑183037 | (TP for SA BL CR for TS 38.473): A new cause value for slice resource shortage | Huawei | imported from 3GU |
| R3‑183038 | NG overload | Huawei | imported from 3GU |
| R3‑183039 | NG reset | Huawei | imported from 3GU |
| R3‑183040 | (TP for NR BL CR for TS 38.470): Rapporteur update | Huawei | imported from 3GU |
| R3‑183041 | (TP for SA BL CR for TS 38.473): Rapporteur update | Huawei | imported from 3GU |
| R3‑183042 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183043 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183044 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183045 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183046 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183047 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183048 | Updated reference to IPv6 | Huawei | imported from 3GU |
| R3‑183049 | Additional UE-associated E1 procedures | Samsung, KT | imported from 3GU |
| R3‑183050 | TP for TS38.463 on additional UE-associated E1 procedure | Samsung, KT | imported from 3GU |
| R3‑183051 | Removal of Note for timely coordination of steps in MN initiated SN Release procedure | Samsung | imported from 3GU |
| R3‑183052 | ASN.1 correction for EN-DC support in TS 36.423 | Samsung | imported from 3GU |
| R3‑183053 | (TP for EN-DC BL CR) ASN.1 correction for GNB-DU CONFIGURATION UPDATE message | Samsung | imported from 3GU |
| R3‑183054 | NR-U Support for Centralized Retransmission | Samsung | imported from 3GU |
| R3‑183055 | NR-U support for centralized retransmission | Samsung, Qualcomm Incorporated^^ | imported from 3GU |
| R3‑183056 | Text proposal to 38.874: Adding architecture 1a with full headers | Ericsson, AT&T | imported from 3GU |
| R3‑183057 | Further consideration on RRC Inactive Assistance Information | LG Electronics, Huawei | imported from 3GU |
| R3‑183058 | Completion of QoS Parameters (NGAP) | Huawei | imported from 3GU |
| R3‑183059 | Completion of QoS Parameters (XnAP) | Huawei | imported from 3GU |
| R3‑183060 | (TP for NR BL CR for TS 38.473) Completion of QoS Parameters | Huawei | imported from 3GU |
| R3‑183061 | Stage 3 TP on CN selective awareness for RRC-INACTIVE state | LG Electronics | imported from 3GU |
| R3‑183062 | (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‑183063 | Consideration on Allowed NSSAI in NG-RAN | LG Electronics | imported from 3GU |
| R3‑183064 | (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‑183065 | Correction of applicability of Secondary RAT Data Usage report for LAA, LWA and LWIP | Intel Corporation, Qualcomm Inc | imported from 3GU |
| R3‑183066 | Further considerations about E1 bearer context modification required procedure | Intel Corporation | imported from 3GU |
| R3‑183067 | On E1 setup procedure | Intel Corporation | imported from 3GU |
| R3‑183068 | RAT and Access type signaling to 5GC | Intel Corporation | imported from 3GU |
| R3‑183069 | RAT and Access type signaling to 5GC – TP for alt1 | Intel Corporation | imported from 3GU |
| R3‑183070 | RAT and Access type signaling to 5GC – TP for alt2 | Intel Corporation | imported from 3GU |
| R3‑183071 | X2 Re-Establishment following a Radio Link Failure on LTE Networks | Vodafone Ireland Plc | imported from 3GU |
| R3‑183072 | [DRAFT] Reply LS on different CGIs for different SSBs | ZTE Corporation | imported from 3GU |
| R3‑183073 | UE Radio Access Capability Size Reduction | Vodafone Ireland Plc | imported from 3GU |
| R3‑183074 | UE Radio Access Capability Size Reduction | Vodafone Ireland Plc | imported from 3GU |
| R3‑183075 | RAN initiated multi-SCTP associations | Huawei, Nokia | imported from 3GU |
| R3‑183076 | UE Radio Access Capability Size Reduction - S1 Part | Vodafone Ireland Plc | imported from 3GU |
| R3‑183077 | IMS voice service via RAT fallback in 5GS | Huawei | imported from 3GU |
| R3‑183078 | Clean up of remaining FFS on Security | Huawei | imported from 3GU |
| R3‑183079 | Clean up of remaining FFS on Security | Huawei | imported from 3GU |
| R3‑183080 | Signaling RFSP during NG handover | Huawei | imported from 3GU |
| R3‑183081 | Signaling RFSP during Xn handover | Huawei | imported from 3GU |
| R3‑183082 | Removal of FFS on AMF name | Huawei | imported from 3GU |
| R3‑183083 | Removal of FFS on a particular ARP value for emergency services | Huawei | imported from 3GU |
| R3‑183084 | UE Radio Access Capability Size Reduction - S1 Part | Vodafone Ireland Plc | imported from 3GU |
| R3‑183085 | (TP for EN-DC BL CR for TS 38.473) F1 support for LTE - NR coexistence | Huawei, Qualcomm Incorporated, Ericsson | imported from 3GU |
| R3‑183086 | Consideration on architecture and protocol stack for IAB | LG Electronics | imported from 3GU |
| R3‑183087 | [draft]LS on how to extract PDCP SN for DL | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183088 | CR on how to extract PDCP SN for DL | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183089 | CR on how to extract PDCP SN for DL | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183090 | (TP for NR BL CR for TS 38.300): Correction on Principles of Data forwarding | Huawei | imported from 3GU |
| R3‑183091 | Correction on Principles of Data forwarding | Huawei | imported from 3GU |
| R3‑183092 | Further considerations of the PDCP Sequence COUNT | Vodafone Ireland Plc | imported from 3GU |
| R3‑183093 | PDCP COUNT expiry Alert Message | Vodafone Ireland Plc | imported from 3GU |
| R3‑183094 | Correction of abnormal conditions for EN-DC security algorithm selection | Qualcomm Incorporated | imported from 3GU |
| R3‑183095 | RAN initiated multi-SCTP associations | Huawei,Nokia | imported from 3GU |
| R3‑183096 | Handling of Security Aspects in NGAP | Qualcomm Incorporated | imported from 3GU |
| R3‑183097 | Handling of Security Aspects in XnAP | Qualcomm Incorporated | imported from 3GU |
| R3‑183098 | Rapporteur update for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
| R3‑183099 | UE-AMBR enforcement | Qualcomm Incorporated, NEC | imported from 3GU |
| R3‑183100 | Handling of Uplink UE-AMBR | Qualcomm Incorporated | imported from 3GU |
| R3‑183101 | Introduction of UE-AMBR feedback in X2 | Qualcomm Incorporated | imported from 3GU |
| R3‑183102 | (TP for EN-DC BL CR for TS 38.473) Introduction of Uplink UE-AMBR control in F1 | Qualcomm Incorporated | imported from 3GU |
| R3‑183103 | Missing UL Configuration IE in ASN | Qualcomm Incorporated | imported from 3GU |
| R3‑183104 | LPPa Broadcast Assistance Data Information | Qualcomm Incorporated | imported from 3GU |
| R3‑183105 | Handling of UE Context Release Command for RRC_INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑183106 | (TP for NR BL CR for TS 38.300) Stage 2 Handling of Remaining DL Class 1 Signalling | Qualcomm Incorporated | imported from 3GU |
| R3‑183107 | Support of MR-DC with RRC INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑183108 | Support of MR_DC with RRC_INACTIVE | Qualcomm Incorporated | imported from 3GU |
| R3‑183109 | Cause value for release request after RAN paging failure | Qualcomm Incorporated | imported from 3GU |
| R3‑183110 | TR 38874 v0.2.1 | Qualcomm Incorporated | imported from 3GU |
| R3‑183111 | IAB Intra-donor transport for architecture group 1 | Qualcomm Incorporated | imported from 3GU |
| R3‑183112 | Modifications to CU-DU architecture for IAB | Qualcomm Incorporated | imported from 3GU |
| R3‑183113 | IAB C-plane support for architecture group 1 | Qualcomm Incorporated | imported from 3GU |
| R3‑183114 | Network synchronization in multi-hop IAB | Qualcomm Incorporated | imported from 3GU |
| R3‑183115 | Inter-IAB-node discovery | Qualcomm Incorporated | imported from 3GU |
| R3‑183116 | IAB topology and route management | Qualcomm Incorporated | imported from 3GU |
| R3‑183117 | Corrections on misalignment between tabular and ASN.1 | Huawei | imported from 3GU |
| R3‑183118 | Discussion on Network Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑183119 | Discussion on Network Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑183120 | Discussion on Network Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑183121 | Discussion on Network Sharing for NR | China Telecommunications | imported from 3GU |
| R3‑183122 | Further discussions on Pmax transfer over F1 | Huawei | imported from 3GU |
| R3‑183123 | (TP for EN-DC BL CR for TS 38.473): on pMax transfer over F1 | Huawei | imported from 3GU |
| R3‑183124 | (TP for SA BL CR for TS 38.473): on CA-based DRB duplication | Huawei | imported from 3GU |
| R3‑183125 | (TP for SA BL CR for TS 38.473): on CA-based SRB duplication | Huawei | imported from 3GU |
| R3‑183126 | (TP for SA BL CR for TS 38.473): on Paging Identity over F1 | Huawei | imported from 3GU |
| R3‑183127 | (TP for EN-DC BL CR for TS 38.473): on ServCellIndex for SpCell | Huawei | imported from 3GU |
| R3‑183128 | (TP for NR BL CR for TS 38.470) on Further discussions on QoS parameter transfer over F1 | Huawei | imported from 3GU |
| R3‑183129 | (TP for SA BL CR for TS 38.473): on gNB-CU behaviour without DU to CU RRC information | Huawei | imported from 3GU |
| R3‑183130 | (TP for SA BL CR for TS 38.473): on Cell Barred Info exchange over F1 interface | Huawei | imported from 3GU |
| R3‑183131 | (TP for SA 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‑183132 | (TP for SA BL CR for TS 38.473): on Cell type indication | Huawei | imported from 3GU |
| R3‑183133 | (TP for SA BL CR for TS 38.473): on RRC connection rejection indication over F1 | Huawei | imported from 3GU |
| R3‑183134 | (TP for SA BL CR for TS 38.473): on Further clarification on UE context management procedure | Huawei | imported from 3GU |
| R3‑183135 | (TP for SA BL CR for TS 38.473): Procedural text for CG-ConfigInfo IE | Huawei | imported from 3GU |
| R3‑183136 | Further discussions on SPID and RFSP over F1 | Huawei | imported from 3GU |
| R3‑183137 | (TP for EN-DC BL CR for TS 38.473): on support SPID over F1 | Huawei | imported from 3GU |
| R3‑183138 | (TP for SA BL CR for TS 38.473): on support RFSP over F1 | Huawei | imported from 3GU |
| R3‑183139 | Further discussions on AMBR enforcement | Huawei | imported from 3GU |
| R3‑183140 | (TP for EN-DC BL CR for TS 38.473) on the introduction of UL UE AMBR over F1 for EN-DC operation | Huawei | imported from 3GU |
| R3‑183141 | (TP for NR BL CR for TS 38.470) on the introduction of UL UE AMBR over F1 for EN-DC operation | Huawei | imported from 3GU |
| R3‑183142 | (TP for SA BL CR for TS 38.470): on PWS in CU DU split | Huawei | imported from 3GU |
| R3‑183143 | (TP for SA BL CR for TS 38.473): on PWS in CU DU split | Huawei | imported from 3GU |
| R3‑183144 | (TP for SA BL CR for TS 38.473): on System information delivery over F1 interface | Huawei | imported from 3GU |
| R3‑183145 | (TP for EN-DC BL CR for TS 38.473) Transmission Stop Indication | Huawei | imported from 3GU |
| R3‑183146 | pCR to 38.412 on clean-ups | Huawei, NTT DOCOMO, INC | imported from 3GU |
| R3‑183147 | pCR to 38.422 on clean-ups | Huawei, NTT DOCOMO, INC | imported from 3GU |
| R3‑183148 | (TP for SA BL CR for TS 38.473): on full configuraiton over F1 | Huawei | imported from 3GU |
| R3‑183149 | (TP for EN-DC BL CR for TS 38.473): on full configuraiton over F1 | Huawei | imported from 3GU |
| R3‑183150 | Impacts of network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183151 | X2 interface between eNB and shared en-gNB with TAC and access mode per PLMN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183152 | Support of X2 removal for EN-DC | Huawei | imported from 3GU |
| R3‑183153 | Introduction of EN-DC X2 removal procedure | Huawei, Deutsche Telekom | imported from 3GU |
| R3‑183154 | Introduction of Xn removal procedure | Huawei, Deutsche Telekom | imported from 3GU |
| R3‑183155 | Further considerations on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑183156 | Clarification on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑183157 | Clarification on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑183158 | [DRAFT] reply LS on secondary RAT data volume reporting | Huawei | imported from 3GU |
| R3‑183159 | Support of QoS for MR-DC with 5GC Alt1 | Huawei | imported from 3GU |
| R3‑183160 | Support of QoS for MR-DC with 5GC Alt2 | Huawei | imported from 3GU |
| R3‑183161 | Correction on length for retransmission | Huawei | imported from 3GU |
| R3‑183162 | Cause values for XnAP | Huawei | imported from 3GU |
| R3‑183163 | Discussion on DL TEID change | Huawei | imported from 3GU |
| R3‑183164 | Support of DL TEID change over S1 at SN | Huawei | imported from 3GU |
| R3‑183165 | Support of NG-U DL UP TNL Information change at NG-RAN | Huawei | imported from 3GU |
| R3‑183166 | Support of SN UL PDCP UP TNL Information change | Huawei | imported from 3GU |
| R3‑183167 | Guidance for measuring secondary RAT data volume for EN-DC | Fujitsu | imported from 3GU |
| R3‑183168 | Clarification on how to measure secondary RAT data volume | Fujitsu | imported from 3GU |
| R3‑183169 | Adaptation layer and Routing for IAB in NR | Intel | imported from 3GU |
| R3‑183170 | Addition of essential NR frequency information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183171 | Additional NR frequency information for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183172 | ASN.1 issue in EN-DC Conf Update Ack message | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183173 | Correction of EN-DC Conf Update Ack message | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| R3‑183174 | RAN3 impacts from "LS on different CGIs for different SSBs" | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183175 | [DRAFT] Reply LS on different CGIs for different SSBs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183176 | Specification impact for TNL address discovery based on intermediate node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183177 | TNL address discovery involving en-gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183178 | MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183179 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183180 | Further handling of Local RRM Policy Specific Containers in RAN3 | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated | imported from 3GU |
| R3‑183181 | Using Standalone IAB node for EN-DC Access link | Huawei | imported from 3GU |
| R3‑183182 | UP protocol design for architecture 1a | Huawei | imported from 3GU |
| R3‑183183 | CP protocol design for L2 relaying | Huawei | imported from 3GU |
| R3‑183184 | IAB node access procedure | Huawei | imported from 3GU |
| R3‑183185 | Protocol design for architecture 2a | Huawei | imported from 3GU |
| R3‑183186 | Network Synchronization of IAB nodes | Huawei | imported from 3GU |
| R3‑183187 | QoS Management of IAB nodes | Huawei | imported from 3GU |
| R3‑183188 | Support of multiple connectivity for IAB | Huawei | imported from 3GU |
| R3‑183189 | Topology type, discovery and update for IAB | Huawei | imported from 3GU |
| R3‑183190 | Destination Address and Forwarding Path based Routing for IAB | Huawei | imported from 3GU |
| R3‑183191 | IAB node configuration and network integration | AT&T | imported from 3GU |
| R3‑183192 | IAB architecture for NSA based deployment | AT&T | imported from 3GU |
| R3‑183193 | Network synchronization for IAB | AT&T | imported from 3GU |
| R3‑183194 | Architecture considerations for L2 relaying | AT&T | imported from 3GU |
| R3‑183195 | End-to-end vs. hop-by-hop RLC ARQ design for L2 relaying in IAB | AT&T | imported from 3GU |
| R3‑183196 | (TP for SA BL CR for TS 38.473): Notification control over F1 | Ericsson | imported from 3GU |
| R3‑183197 | (TP for SA BL CR for TS 38.473): Clarifications on multiple TNLA – TP 473 | Ericsson | imported from 3GU |
| R3‑183198 | (TP for NR BL CR for TS 38.401): Clarifications on multiple TNLA – TP 401 | Ericsson | imported from 3GU |
| R3‑183199 | (TP for SA BL CR for TS 38.473): Multiple port numbers - TP 473 | Ericsson | imported from 3GU |
| R3‑183200 | Multiple port numbers - CR 472 | Ericsson | imported from 3GU |
| R3‑183201 | (TP for SA BL CR for TS 38.473): Clarification on signalling connection | Ericsson | imported from 3GU |
| R3‑183202 | (TP for SA BL CR for TS 38.473): Measurement configuration for SA | Ericsson | imported from 3GU |
| R3‑183203 | (TP for NR BL CR for TS 38.473): RRC version handling | Ericsson | imported from 3GU |
| R3‑183204 | (TP for NR BL CR for TS 38.473): RRC container over F1AP | Ericsson | imported from 3GU |
| R3‑183205 | (TP for NR BL CR for TS 38.401): Clarification on active cell list | Ericsson | imported from 3GU |
| R3‑183206 | (TP for NR BL CR for TS 38.401): E1 support for RRC-inactive | Ericsson | imported from 3GU |
| R3‑183207 | Dual-connectivity configuration over E1 | Ericsson | imported from 3GU |
| R3‑183208 | PDCP duplication configuration | Ericsson | imported from 3GU |
| R3‑183209 | E1 multiple SCTP associations - 462 | Ericsson | imported from 3GU |
| R3‑183210 | E1 multiple SCTP associations - 463 | Ericsson | imported from 3GU |
| R3‑183211 | E1 Setup procedure | Ericsson | imported from 3GU |
| R3‑183212 | E1 Release procedure | Ericsson | imported from 3GU |
| R3‑183213 | Bearer Context Setup procedure | Ericsson | imported from 3GU |
| R3‑183214 | Bearer Context Modification procedure | Ericsson | imported from 3GU |
| R3‑183215 | Other Bearer Context procedures | Ericsson | imported from 3GU |
| R3‑183216 | Rapporteur TP for TS 38.463 | Ericsson | imported from 3GU |
| R3‑183217 | (TP for EN-DC BL CR for TS 38.473): Priority order for SpCell list | Ericsson | imported from 3GU |
| R3‑183218 | (TP for EN-DC BL CR for TS 38.473): Measurement configuration for EN-DC | Ericsson | imported from 3GU |
| R3‑183219 | (TP for EN-DC BL CR for TS 38.473): Monitoring of inactivity | Ericsson | imported from 3GU |
| R3‑183220 | Clarification on SCTP association establishment – for 36.300 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
| R3‑183221 | (TP for NR BL CR for TS 38.300): Clarification on SCTP association establishment – for 38.300 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
| R3‑183222 | (TP for NR BL CR for TS 38.401): Clarification on SCTP association establishment – for 38.401 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
| R3‑183223 | LTE-NR coordination for inter-modulation issue (CR to 36.423) | Qualcomm Europe Inc.(France) | imported from 3GU |
| R3‑183224 | E1 Setup procedure for 38.460 | Ericsson | imported from 3GU |
| R3‑183225 | On Coexistence between RRC inactive and dual connectivity – TP for 38.423 | Ericsson | imported from 3GU |
| R3‑183226 | (TP for NR BL CR for TS 37.340): Support of RRC_INACTIVE and MR-DC with 5GC | Ericsson | imported from 3GU |
| R3‑183227 | On Coexistence between RRC inactive and dual connectivity – TP for 38.420 | Ericsson | imported from 3GU |
| R3‑183228 | Coordination of Inactivity for EN-DC | Ericsson | imported from 3GU |
| R3‑183229 | (TP for NR BL CR for TS 37.340): Correction for PDCP Duplication | Ericsson | imported from 3GU |
| R3‑183230 | Content of data forwarding address indication message | LG Electronics | imported from 3GU |
| R3‑183231 | Handling large capability containers in inter-RAT HO | Qualcomm Incorporated | imported from 3GU |
| R3‑183232 | Removing FFSs on integrity protection for ng-eNBs (NGAP) | Qualcomm Incorporated | imported from 3GU |
| R3‑183233 | Removing FFSs on integrity protection for ng-eNBs (XnAP) | Qualcomm Europe Inc.(France) | imported from 3GU |
| R3‑183234 | On IAB architectures | Mitsubishi Electric RCE | imported from 3GU |
| R3‑183235 | Draft TS skeleton for W1 general aspects and principles | China Unicom | imported from 3GU |
| R3‑183236 | Draft TS skeleton for W1 general aspects and principles | China Unicom | imported from 3GU |
| R3‑183237 | Draft TS skeleton for W1 layer 1 | China Unicom | imported from 3GU |
| R3‑183238 | Discussion on Allowed NSSAI Applicability | Ericsson | imported from 3GU |
| R3‑183239 | Discussion on AMF Overload Control procedure | Ericsson | imported from 3GU |
| R3‑183240 | [DRAFT] Reply LS on Allowed NSSAI indication to RAN | Ericsson | imported from 3GU |
| R3‑183241 | [DRAFT] LS on AMF Overload control | Ericsson | imported from 3GU |
| R3‑183242 | Addition of SSB and other NR frequency information | Ericsson | imported from 3GU |
| R3‑183243 | (TP for EN-DC BL CR for TS 38.473): support of NR Multiple frequency band in EN-DC | Ericsson | imported from 3GU |
| R3‑183244 | X2AP CR for support of NR Multiple frequency band in EN-DC | Ericsson | imported from 3GU |
| R3‑183245 | TP for signalling of RFSP over NG during HO procedures | Ericsson | imported from 3GU |
| R3‑183246 | TP for signalling of RFSP over Xn during HO procedures | Ericsson | imported from 3GU |
| R3‑183247 | Resolving FFSs for DRB QoS procedures over F1-C | Ericsson | imported from 3GU |
| R3‑183248 | Analysis and conclusion on securing signalling connections | Ericsson | imported from 3GU |
| R3‑183249 | Support of secured signalling-only connections | Ericsson | imported from 3GU |
| R3‑183250 | Way Forward on UL AMBR Monitoring and enforcement | Ericsson | imported from 3GU |
| R3‑183251 | Handling of UE UL AMBR | Ericsson | imported from 3GU |
| R3‑183252 | Correcting some more items in the XnAP Handover Preparation and Retrieve UE Context Procedure | Ericsson | imported from 3GU |
| R3‑183253 | (TP for EN-DC BL CR for TS 38.473): Signalling of RFSP over F1-C | Ericsson | imported from 3GU |
| R3‑183254 | LS on NR Cell Information signalled over X2 for EN-DC | Ericsson | imported from 3GU |
| R3‑183255 | Draft TS skeleton for W1 signalling transport | China Unicom | imported from 3GU |
| R3‑183256 | Draft TS skeleton for W1 application protocol (W1AP) | China Unicom | imported from 3GU |
| R3‑183257 | Draft TS skeleton for W1 data transport | China Unicom | imported from 3GU |
| R3‑183258 | Allowed NSSAI indication to NG-RAN | CMCC | imported from 3GU |
| R3‑183259 | DL data handling in RRC_INACTIVE | CMCC | imported from 3GU |
| R3‑183260 | Correction for INITIAL CONTEXT SETUP REQUEST related to signalling connection only | Huawei | imported from 3GU |
| R3‑183261 | Remaining TNL aspects F1 | Huawei | imported from 3GU |
| R3‑183262 | Remaining TNL aspects NG | Huawei | imported from 3GU |
| R3‑183263 | UE History Information introduction NG | Huawei | imported from 3GU |
| R3‑183264 | (TP for NR BL CR for TS 36.413): NR UE History Information introduction | Huawei | imported from 3GU |
| R3‑183265 | UE History Information introduction Xn | Huawei | imported from 3GU |
| R3‑183266 | NR UE History Information introduction X2 | Huawei | imported from 3GU |
| R3‑183267 | End marker handling for handover | CMCC | imported from 3GU |
| R3‑183268 | Resolving the remaining FFS on 5QI in QoS profile of TS 38.413 | CMCC | imported from 3GU |
| R3‑183269 | Resolving the remaining FFS on 5QI in QoS profile of TS 38.423 | CMCC | imported from 3GU |
| R3‑183270 | Cleanup of Timers in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183271 | Open issues for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183272 | (TP for NR BL CR for TS 38.470): Introduction of LTE-NR coexistence function | Huawei | imported from 3GU |
| R3‑183273 | rapporteur updates to 38.462 | Huawei | imported from 3GU |
| R3‑183274 | pCR to 38.460 for Notification control functionality | Huawei | imported from 3GU |
| R3‑183275 | pCR to 38.463 for Notification control functionality | Huawei | imported from 3GU |
| R3‑183276 | pCR to 38.460 on Reflective QoS handling over E1 | Huawei | imported from 3GU |
| R3‑183277 | pCR to 38.463 on Reflective QoS handling over E1 | Huawei | imported from 3GU |
| R3‑183278 | pCR to 38.460 on further discussion on E1 interface management message | Huawei | imported from 3GU |
| R3‑183279 | pCR to 38.460 on indication of PDCP duplication over E1 interface | Huawei | imported from 3GU |
| R3‑183280 | pCR to TS38.463 on further discussion on E1 interface management message | Huawei | imported from 3GU |
| R3‑183281 | pCR to 38.463 on indication of PDCP duplication over E1 interface | Huawei | imported from 3GU |
| R3‑183282 | pCR to 38.460 on Inactivity monitoring in CP/UP separation | Huawei | imported from 3GU |
| R3‑183283 | pCR to 38.463 on Inactivity monitoring in CP/UP separation | Huawei | imported from 3GU |
| R3‑183284 | pCR to 38.463 on on Correction of bearer context management procedures | Huawei | imported from 3GU |
| R3‑183285 | pCR to 38.463 on 38.460 on Correction of bearer context management procedures | Huawei | imported from 3GU |
| R3‑183286 | pCR to 38.463 on Data Forwarding in CPUP separation | Huawei | imported from 3GU |
| R3‑183287 | pCR to 38.460 on Corrections for initial access in NG-RAN with CP-UP separation | Huawei | imported from 3GU |
| R3‑183288 | (TP for CPUP_Split BL CR for TS 38.401): on Clarification on use case of gNB-CU-UP TEID change | Huawei | imported from 3GU |
| R3‑183289 | pCR to 38.463 on Clarification on use case of gNB-CU-UP TEID change | Huawei | imported from 3GU |
| R3‑183290 | (TP for CPUP_Split BL CR for TS 38.401): on centralized retransmission for CP-UP separation | Huawei | imported from 3GU |
| R3‑183291 | pCR to 38.463 on centralized retransmission for CP-UP separation | Huawei | imported from 3GU |
| R3‑183292 | (TP for NR BL CR for TS 38.401): on RRC state transition for CP-UP separation | Huawei | imported from 3GU |
| R3‑183293 | Correction of Packet Loss Rate | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183294 | Response to R3-182775 | HUAWEI | imported from 3GU |
| R3‑183295 | Response to R3-182552 | Huawei | imported from 3GU |
| R3‑183296 | Response to R3-182542, R3-182894, R3-182979 and R3-183176 | Ericsson | imported from 3GU |
| R3‑183297 | Response to R3-182543 and R3-183177 | Ericsson | imported from 3GU |
| R3‑183298 | Response to R3-182544 | Ericsson | imported from 3GU |
| R3‑183299 | Response to R3-183144 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183300 | response to R3-183231 “Handling large capability containers in inter-RAT HO” (source: Qualcomm Incorporated) | Vodafone Group Plc | imported from 3GU |
| R3‑183301 | Response to R3-182764 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183302 | Response to R3-182721 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183303 | Response to R3-183028 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183304 | Response to R3-183029 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183305 | Response to R3-182765 | HuaWei Technologies Co., Ltd | imported from 3GU |
| R3‑183306 | Response to R3-182862 | Ericsson-LG Co., LTD | imported from 3GU |
| R3‑183307 | Response to R3-183248 | HUAWEI | imported from 3GU |
| R3‑183308 | (TP for SA BL CR for TS 38.473): on the support of support of secured signalling only connection | HUAWEI | imported from 3GU |
| R3‑183309 | LS on Removal of LTE specific terminology from Group Communication System Enablers TS 22.468 | SA1, Nokia | imported from 3GU |
| R3‑183310 | LS on completion of the 5G Trace | SA5, Nokia | imported from 3GU |
| R3‑183311 | LS on L2 measurement specification for NR in R15 | SA5, Ericsson | imported from 3GU |
| R3‑183312 | Reply LS to RAN2 on Bluetooth/WLAN measurement collection in MDT | SA5, China Mobile | imported from 3GU |
| R3‑183313 | Handling large capability containers in inter-RAT HO | Qualcomm Incorporated | imported from 3GU |
| R3‑183314 | Rapporteur’s input TS 38.423 version 0.8.0 | Ericsson | imported from 3GU |
| R3‑183315 | NB-IoT session report | Intel (Vice chairman) | imported from 3GU |
| R3‑183316 | Aerial Session Report | ZTE (Vice chairman) | imported from 3GU |
| R3‑183317 | Baseline CR for LTE-NR coexistence for TS 36.423 covering agreements of RAN3#99Bis | Ericsson | imported from 3GU |
| R3‑183318 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑183319 | Introduction of QMC for MTSI in EUTRAN | Ericsson | imported from 3GU |
| R3‑183320 | Reply LS on adding new service type in QMC reporting | Ericsson | imported from 3GU |
| R3‑183321 | UE Radio Access Capability Size Reduction | Vodafone Ireland Plc | imported from 3GU |
| R3‑183322 | UE Radio Access Capability Size Reduction | Vodafone Ireland Plc | imported from 3GU |
| R3‑183323 | UE Radio Access Capability Size Reduction - S1 Part | Vodafone Ireland Plc | imported from 3GU |
| R3‑183324 | UE Radio Access Capability Size Reduction - S1 Part | Vodafone Ireland Plc | imported from 3GU |
| R3‑183325 | Reply LS on applicability of Connection Establishment Indication procedure after the establishment of S1 logical connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183326 | Triggering UE capability info retrieval using DL NAS TRANSPORT | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑183327 | IAB scenarios Summary of offline discussion | Intel (Vice-chairman) | imported from 3GU |
| R3‑183328 | Summary of offline discussion on IAB architecture options | Intel (Vice-chairman) | imported from 3GU |
| R3‑183329 | Summary of offline discussion on IAB and NSA | ZTE (Vice-chairman) | imported from 3GU |
| R3‑183330 | Summary of offline discussion on IAB protocol stack | Intel (Vice-chairman) | imported from 3GU |
| R3‑183331 | Summary of offline discussion on IAB-node integration | ZTE (Vice-chairman) | imported from 3GU |
| R3‑183332 | IAB QoS | Intel (Vice-chairman) | imported from 3GU |
| R3‑183333 | Summary of offline discussion on IAB network synchronization | Intel (Vice-chairman) | imported from 3GU |
| R3‑183334 | IAB MultiConn | ZTE | imported from 3GU |
| R3‑183335 | Summary of offline discussion on IAB-node topologies | ZTE (Vice-chairman) | imported from 3GU |
| R3‑183336 | Summary and way forward of discussions on UL AMBR | Ericsson | imported from 3GU |
| R3‑183337 | Handling of Uplink UE-AMBR | Ericsson | imported from 3GU |
| R3‑183338 | Management of UL AMBR | Ericsson | imported from 3GU |
| R3‑183339 | (TP for EN-DC BL CR for TS 38.473) Management of UL AMBR | Ericsson | imported from 3GU |
| R3‑183340 | Support of NB-IoT measurement enhancement and TDD Config | Huawei | imported from 3GU |
| R3‑183341 | Support of OTDOA in NB-IoT enhancement | Huawei | imported from 3GU |
| R3‑183342 | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99Bis | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183343 | Rapporteur’s updates for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183344 | (TP for SA BL CR for TS 38.473): Rapporteur update | Huawei | imported from 3GU |
| R3‑183345 | Cleanup of NAS Transport procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183346 | Open issues for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183347 | (TP for NR BL CR for TS38.401) Discussions on supporting Msg3 based on-demand SI over F1 | Samsung, KT Corp. | imported from 3GU |
| R3‑183348 | Discussions on control plane protocol for IAB | Samsung | imported from 3GU |
| R3‑183349 | Discussion on the extension of QFI -TP to Xn | Samsung | imported from 3GU |
| R3‑183350 | Support of Enhanced VoLTE Performance | Huawei | imported from 3GU |
| R3‑183351 | Support of Enhanced VoLTE Performance | Huawei | imported from 3GU |
| R3‑183352 | LS on Support of Enhanced VoLTE Performance | Nokia | imported from 3GU |
| R3‑183353 | Correction of applicability of Secondary RAT Data Usage report for LAA, LWA and LWIP | Intel Corporation, Qualcomm Inc | imported from 3GU |
| R3‑183354 | Support of secured signalling-only connections | Ericsson, Vodafone, DoCoMo, CMCC, T-Mobile USA | imported from 3GU |
| R3‑183355 | Support of secured signaling only connections | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183356 | Secured signalling-only connections (Modification and handover) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183357 | (TP for EN-DC BL CR for TS38.473) Update for Secured SRB-only connection | ZTE Corporation | imported from 3GU |
| R3‑183358 | (TP for BL SA CR for TS 38.473): UE Context Release | Ericsson-LG Co., LTD | imported from 3GU |
| R3‑183359 | (TP for NSA BL CR for TS 38.473) Additional cause values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183360 | (TP for SA BL CR for TS 38.473): on clarification of on the presence of C-RNTI in Initial UL RRC Transfer message | Huawei, LG | imported from 3GU |
| R3‑183361 | (TP for EN-DC BL CR for TS 38.473): on ServCellIndex for SpCell | Huawei | imported from 3GU |
| R3‑183362 | (TP for EN-DC BL CR for TS 38.473): on full configuraiton over F1 | Huawei | imported from 3GU |
| R3‑183363 | (TP for EN-DC BL CR for TS 38.473): Measurement configuration for EN-DC | Ericsson | imported from 3GU |
| R3‑183364 | Addition of an SN Change Indicator – based on CR1107r2 for TS36.423 R3-182480 | Ericsson | imported from 3GU |
| R3‑183365 | (TP for NR BL CR for TS 37.340): Addition of an SN Change Indicator – based on R3-182339 | Ericsson | imported from 3GU |
| R3‑183366 | Addition of MeNB cell ID to solve the PCI confusion | Samsung, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183367 | Enabling re-use of NR PCIs in cells served by the same en-gNB in EN-DC | Nokia | imported from 3GU |
| R3‑183368 | Correction of Split SRB configuration in TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑183369 | Correction of Split SRB configuration in TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑183370 | CR for Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑183371 | ASN.1 correction for EN-DC support in TS 36.423 | Samsung | imported from 3GU |
| R3‑183372 | Addition of Cause Value | Samsung | imported from 3GU |
| R3‑183373 | Introduction of EN-DC X2 removal procedure | Huawei, Deutsche Telekom | imported from 3GU |
| R3‑183374 | Introduction of Xn removal procedure | Huawei, Deutsche Telekom | imported from 3GU |
| R3‑183375 | Xn Removal stage 2 | Qualcomm | imported from 3GU |
| R3‑183376 | Completion of Xn setup stage 3 | Huawei | imported from 3GU |
| R3‑183377 | X2AP CR for support of NR Multiple frequency band in EN-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑183378 | SSB information correction in XnAP | Huawei, Ericsson | imported from 3GU |
| R3‑183379 | F1AP TP for EN-DC BL CR | Ericsson | imported from 3GU |
| R3‑183380 | Summary of offline discussion on NG/Xn Setup | Ericsson | imported from 3GU |
| R3‑183381 | Use of SPID for EN-DC | Ericsson, Deutsche Telekom, Orange, Telecom Italia, Vodafone | imported from 3GU |
| R3‑183382 | Various corrections for the NR UP | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183383 | (TP for PDCP dup Assist Info CR for TS 38.425)Addition of UL information for the node hosting PDCP | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183384 | Further Discussion and TS38.401 TP on Multi-Connectivity with DualMultiple gNB-DUs | ZTE | imported from 3GU |
| R3‑183385 | Removing FFSs on integrity protection for ng-eNBs (NGAP) | Qualcomm Incorporated | imported from 3GU |
| R3‑183386 | Removing FFSs on integrity protection for ng-eNBs (XnAP) | Qualcomm Europe Inc.(France) | imported from 3GU |
| R3‑183387 | Further Discussion and TS38.413 pCR for UP Security Handling | ZTE | imported from 3GU |
| R3‑183388 | Clean up of remaining FFS on Security | Huawei | imported from 3GU |
| R3‑183389 | Handling of Security Aspects in XnAP | Qualcomm Incorporated | imported from 3GU |
| R3‑183390 | Completion of paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183391 | AP ID handling and related Cause Values | Ericsson | imported from 3GU |
| R3‑183392 | Cause Value corrections on NGAP | Ericsson | imported from 3GU |
| R3‑183393 | Cause values for XnAP | Huawei, Ericsson | imported from 3GU |
| R3‑183394 | TP for User Location Information | CATT | imported from 3GU |
| R3‑183395 | Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – HO aspects | Ericsson, Vodafone, KT, AT&T, Intel, Orange | imported from 3GU |
| R3‑183396 | UE capability check for IMS voice | Qualcomm Incorporated, Huawei, T-Mobile USA INC., CMCC | imported from 3GU |
| R3‑183397 | LS on RAN initiated TNL Associations over NGAP | Huawei | imported from 3GU |
| R3‑183398 | Summary of offline discussion on DL UP termination point on the RAN-CN interface at handover | Ericsson | imported from 3GU |
| R3‑183399 | Signaling RFSP during NG handover | Huawei | imported from 3GU |
| R3‑183400 | (TP for EN-DC BL CR for TS 38.473): Signalling of RFSP over F1-C | Ericsson | imported from 3GU |
| R3‑183401 | TS38.423 pCR on Configuring Index to RFSP info During Xn Mobility | ZTE | imported from 3GU |
| R3‑183402 | Further Discussion and 38.413 pCR on NG Handover Type | ZTE | imported from 3GU |
| R3‑183403 | Reply LS on Aspects of Handling Large UE Radio Capabilities in EPC | Vodafone | imported from 3GU |
| R3‑183404 | Discussion on the extension of QFI -TP to Xn | Samsung | imported from 3GU |
| R3‑183405 | Discussion on the extension of QFI -TP to NG | Samsung | imported from 3GU |
| R3‑183406 | Completion of QoS Parameters (NGAP) | Huawei | imported from 3GU |
| R3‑183407 | Completion of QoS Parameters (XnAP) | Huawei | imported from 3GU |
| R3‑183408 | (TP for NR BL CR for TS 38.473) Completion of QoS Parameters | Huawei | imported from 3GU |
| R3‑183409 | LS on signalling of dynamic 5QI values | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183410 | Correction on Additional QoS information | Ericsson | imported from 3GU |
| R3‑183411 | Introduction of “Additional QoS flow Information” in XnAP | Ericsson | imported from 3GU |
| R3‑183412 | (TP for SA BL CR for TS 38.473): Notification control over F1 | Ericsson | imported from 3GU |
| R3‑183413 | PDU Type for DL and UL | NEC | imported from 3GU |
| R3‑183414 | Clean up Signaling of NAS PDU in PDU Session management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183415 | TP to support selective activation of UP connection of existing PDU Sessions | Nokia, Nokia Shanghai Bell, Intel Corporation | imported from 3GU |
| R3‑183416 | How should the AMF or the N3IWF react while receiving a message not specified in 29.413? | Ericsson | imported from 3GU |
| R3‑183417 | Rapporteur’s update to TS38.425 v15.1.0 | Samsung | imported from 3GU |
| R3‑183418 | Summary of offline discussion on UP version handling | Ericsson | imported from 3GU |
| R3‑183419 | (TP for SA BL CR for TS 38.473):Support of PDCP Duplication for SRB | CATT | imported from 3GU |
| R3‑183420 | (TP for SA BL CR for TS 38.473):Support of PDCP Duplication for DRB | CATT | imported from 3GU |
| R3‑183421 | (TP for NR BL CR for TS 37.340): Correction for PDCP Duplication | Ericsson | imported from 3GU |
| R3‑183422 | Radio quality information report activation | Ericsson | imported from 3GU |
| R3‑183423 | Further handling of Local RRM Policy Specific Containers in RAN3 | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Qualcomm Incorporated | imported from 3GU |
| R3‑183424 | CR on data existence indication for split bearer | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183425 | LS on NGAP SMF Ies | CT4, Nokia | imported from 3GU |
| R3‑183426 | LS on updates for TS 36.300 | RAN2, Huawei | imported from 3GU |
| R3‑183427 | F1 support for LTE - NR coexistence | Huawei, Qualcomm Incorporated, Ericsson | imported from 3GU |
| R3‑183428 | Introduction of LTE-NR coexistence function | Huawei | imported from 3GU |
| R3‑183429 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183430 | Baseline CR: Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑183431 | Baseline CR: Introduction of the Aerial Usage Indication | Ericsson, NTT Docomo | imported from 3GU |
| R3‑183432 | Reply LS on NGAP SMF Ies | Nokia | imported from 3GU |
| R3‑183433 | TP on E-CID related information | Ericsson | imported from 3GU |
| R3‑183434 | TP on general FFS’s | Ericsson | imported from 3GU |
| R3‑183435 | TP on E-CID related information | Ericsson | imported from 3GU |
| R3‑183436 | TP on OTDOA related information | Ericsson | imported from 3GU |
| R3‑183437 | Assistance Information Broadcasting | Ericsson | imported from 3GU |
| R3‑183438 | ANR stage 2 clean up | Huawei | imported from 3GU |
| R3‑183439 | Reply LS on signalling | Huawei | imported from 3GU |
| R3‑183440 | Introduction of a Configured TAC into the NR Neighbour Information IE and the Served NR Cell Information IE | Ericsson | imported from 3GU |
| R3‑183441 | On the definition of RAN Paging Area – TP to 38.423 | NEC | imported from 3GU |
| R3‑183442 | Including RANAC in Xn Setup and NG-RAN node Configuration Update messages | Ericsson | imported from 3GU |
| R3‑183443 | (TP for SA BL CR for TS 38.473): Exchange of RANAC over Xn and F1 | Huawei | imported from 3GU |
| R3‑183444 | Resolving open issues on RAN Paging Area and RAN Area | Ericsson | imported from 3GU |
| R3‑183445 | (TP for NR BL CR for TS 38.300) Definition of RAN Notification Area | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183446 | (TP for NR BL CR for TS 38.300) TP for Handling of class 1 signaling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183447 | State transition from inactive to idle state | Huawei,Intel Corporation | imported from 3GU |
| R3‑183448 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183449 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183450 | On I-RNTI partitioning for correctly addressing the old serving NG-RAN node | Ericsson | imported from 3GU |
| R3‑183451 | (TP for NR BL CR for TS 38.300): On definition of I-RNTI in 38.300 | Ericsson | imported from 3GU |
| R3‑183452 | [DRAFT] Reply LS on MSG3 size reduction | Ericsson | imported from 3GU |
| R3‑183453 | CR on maintaining the bearer type on wrap-around for TS37.340 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183454 | Removal of FFSes in location reporting procedure | Huawei | imported from 3GU |
| R3‑183455 | 5GS Location Reporting continued – XnAP Text Proposal | Ericsson | imported from 3GU |
| R3‑183456 | LS on Location Reporting for Area of Interest | Ericsson | imported from 3GU |
| R3‑183457 | (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‑183458 | pCR to 38.460 on further discussion on E1 interface management message | Huawei | imported from 3GU |
| R3‑183459 | Information to be exchanged during E1 Setup (TS 38.463) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183460 | E1 UE-associated procedures | Ericsson | imported from 3GU |
| R3‑183461 | W1 interface general aspects and principles | Huawei, China Unicom | imported from 3GU |
| R3‑183462 | W1 interface layer1 | Huawei, China Unicom | imported from 3GU |
| R3‑183463 | W1 interface Data Transport Protocol | Huawei, China Unicom | imported from 3GU |
| R3‑183464 | W1 interface signalling transport | Huawei, China Unicom | imported from 3GU |
| R3‑183465 | W1 Interface Application Protocol | Huawei, China Unicom | imported from 3GU |
| R3‑183466 | RAN3 TP to R2-1807880 on Introduction of EDT for eMTC and NB-IoT enhancements in TS 36.300 | Huawei | imported from 3GU |
| R3‑183467 | Reply LS on updates for TS 36.300 | Huawei | imported from 3GU |
| R3‑183468 | [Draft] Reply LS on EDT procedures and AS NAS interaction | Huawei | imported from 3GU |
| R3‑183469 | Baseline CR: Introduction of early data transmission | Huawei, China Telecom, CMCC, Qualcomm Incorporated, China Unicom | imported from 3GU |
| R3‑183470 | [Draft] Reply LS on Reply LS on UE differentiation for NB-IoT from SA2 | Ericsson | imported from 3GU |
| R3‑183471 | Baseline CR: Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
| R3‑183472 | Support of NB-IoT measurement enhancement and TDD Config | Huawei | imported from 3GU |
| R3‑183473 | Support of OTDOA in NB-IoT enhancement | Huawei | imported from 3GU |
| R3‑183474 | LS on Definition of Maximum Packet Loss Rate | CT3, Huawei | imported from 3GU |
| R3‑183475 | Reply LS on Clarification on GTP-U "Long PDCP PDU Number" extension header | CT4, NTT Docomo | imported from 3GU |
| R3‑183476 | Security solution for encryption of broadcast positioning information | SA3, Qualcomm | imported from 3GU |
| R3‑183477 | Reply LS on UE capability related to integrity protection of DRBs | SA3, Qualcomm | imported from 3GU |
| R3‑183478 | Reply LS on security keys for generation of shortResumeMAC-I for UP EDT | SA3, Samsung | imported from 3GU |
| R3‑183479 | Registration with AMF re-allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183480 | Registration with AMF Reallocation | Interdigital Asia LLC | imported from 3GU |
| R3‑183481 | Reply LS on Allowed NSSAI indication to RAN | Huawei | imported from 3GU |
| R3‑183482 | Remaining TNL aspects F1 | Huawei | imported from 3GU |
| R3‑183483 | Reason for SgNB Addition | Nokia, Nokia Shanghai Bell, AT&T | imported from 3GU |
| R3‑183484 | RAN3#100 Awards ceremony | RAN3 | imported from 3GU |
| R3‑183485 | RAN3#100 - “I went to RAN3” song lyrics | RAN3 | imported from 3GU |
| R3‑183486 | (TP for SA BL CR for TS 38.473): Public Warning System for F1 | Ericsson | imported from 3GU |
| R3‑183487 | (TP for SA BL CR for TS 38.470): on PWS in CU DU split | Huawei | imported from 3GU |
| R3‑183488 | (TP for SA BL CR for TS38.473) Discussions on supporting Msg3 based on-demand SI over F1 | Samsung, KT Corp. | imported from 3GU |
| R3‑183489 | (TP for SA BL CR for TS 38.473): on System information delivery over F1 interface | Huawei | imported from 3GU |
| R3‑183490 | Handling of gNB-DU UE F1AP ID during RRC Connection Re-establishment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183491 | (TP for SA BL CR for TS 38.473): on gNB-CU behaviour without DU to CU RRC information | Huawei | imported from 3GU |
| R3‑183492 | (TP for SA BL CR for TS 38.473): on Paging Identity over F1 | Huawei | imported from 3GU |
| R3‑183493 | Reply LS on measurement gap configuration for gNB-CU/DU split scenario | RAN2, CATT | imported from 3GU |
| R3‑183494 | LS to RAN3 on IAB security architecture | RAN2 | imported from 3GU |
| R3‑183495 | (TP for NSA BL CR for TS 38.473) User inactivity monitoring | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑183496 | (TP for EN-DC BL CR for TS 38.473) Introducing configured EPS TAC in the Served Cell Information IE for EN-DC | Ericsson | imported from 3GU |
| R3‑183497 | UE Context Fetch Procedure in Xn | Samsung,KT Corp.,QC Incorporated,Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183498 | (TP for NR BL CR for TS 38.401) User inactivity monitoring | Nokia, Nokia Shanghai Bell, CMCC, KT, Fujitsu, Samsung | imported from 3GU |
| R3‑183499 | (TP for NR BL CR for TS 36.413): NR UE History Information introduction | Huawei | imported from 3GU |
| R3‑183500 | NR UE History Information introduction X2 | Huawei | imported from 3GU |
| R3‑183501 | (TP for NR BL CR for TS 36.413) UE History Information restriction | Huawei | imported from 3GU |
| R3‑183502 | Reply LS on Definition of Maximum Packet Loss Rate | Nokia | imported from 3GU |
| R3‑183503 | Support of Enhanced VoLTE Performance | Huawei | imported from 3GU |
| R3‑183504 | Support of Enhanced VoLTE Performance | Huawei | imported from 3GU |
| R3‑183505 | (TP for SA BL CR for TS 38.473): on Cell type indication | Huawei | imported from 3GU |
| R3‑183506 | (TP for NR BL CR for TS 38.401): Clarification on active cell list | Ericsson | imported from 3GU |
| R3‑183507 | (TP for EN-DC BL CR for TS 38.473)Introduction of SMTC information for neighbour cells | CATT | imported from 3GU |
| R3‑183508 | Baseline CR: Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
| R3‑183509 | (TP for SA BL CR for TS 38.473): on Cell Barred Info exchange over F1 interface | Huawei | imported from 3GU |
| R3‑183510 | Introducing CM-Connected Mobility Restrictions | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑183511 | Introduction of CM-CONNECTED Mobility Restrictions in XnAP | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑183512 | LS on 5G CM-Connected Mobility Restrictions | Ericsson | imported from 3GU |
| R3‑183513 | (TP for NR BL CR for TS 38.300) Handling of forwarding tunnels | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183514 | (TP for NR BL CR for TS38.470)Support PWS in CU-DU deployment | ZTE Corporation | imported from 3GU |
| R3‑183515 | Completion of data forwarding encoding in TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183516 | (TP for NR BL CR for TS 38.473) PWS over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183517 | Stage-3 TP for Xn SN Status Transfer | Intel Corporation | imported from 3GU |
| R3‑183518 | LS on Radio Capability Check for IMS Voice | Qualcomm | imported from 3GU |
| R3‑183519 | Partial Xn Reset – XNAP Text Proposal | Ericsson, Qualcomm Incorporated | imported from 3GU |
| R3‑183520 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183521 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183522 | Summary of offline discussion on UL UE AMBR | Ericsson, Verizon, DoCoMo2, Orange, Vodafone, AT&T, Qualcom Incorporated, Deutsche Telekom | imported from 3GU |
| R3‑183523 | Addition of MeNB cell ID to solve the PCI confusion | Samsung, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183524 | Enabling re-use of NR PCIs in cells served by the same en-gNB in EN-DC | Ericsson, Samsung | imported from 3GU |
| R3‑183525 | Correction of Split SRB configuration in TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑183526 | CR for Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑183527 | Completion of Xn setup stage 3 | Huawei | imported from 3GU |
| R3‑183528 | LS on NR Cell Information signalled over X2 for EN-DC | Ericsson | imported from 3GU |
| R3‑183529 | X2AP CR for support of NR Multiple frequency band in EN-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑183530 | (TP for PDCP dup Assist Info CR for TS 38.425)Addition of UL information for the node hosting PDCP | NTT DOCOMO, INC. | imported from 3GU |
| R3‑183531 | Further Discussion and TS38.401 TP on Multi-Connectivity with DualMultiple gNB-DUs | ZTE | imported from 3GU |
| R3‑183532 | (TP for NR BL CR for TS 38.300) Current Status of Discussions on intra- and inter-system HO discussions – companion paper for CBno86 | Ericsson | imported from 3GU |
| R3‑183533 | Reply LS on Aspects of Handling Large UE Radio Capabilities in EPC | Vodafone | imported from 3GU |
| R3‑183534 | SSB information correction in XnAP | Huawei, Ericsson | imported from 3GU |
| R3‑183535 | Support of secured signaling only connections | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183536 | AP ID handling and related Cause Values | Ericsson | imported from 3GU |
| R3‑183537 | UE capability check for IMS voice | Qualcomm Incorporated, Huawei, T-Mobile USA INC., CMCC | imported from 3GU |
| R3‑183538 | LS on Radio Capability Check for IMS Voice | Qualcomm | imported from 3GU |
| R3‑183539 | (TP for EN-DC BL CR for TS 38.473): Signalling of RFSP over F1-C | Ericsson | imported from 3GU |
| R3‑183540 | (TP for EN-DC BL CR for TS 38.473): Signalling of RFSP over F1-C | Ericsson | imported from 3GU |
| R3‑183541 | TS38.423 pCR on Configuring Index to RFSP info During Xn Mobility | ZTE | imported from 3GU |
| R3‑183542 | (TP for NR BL CR for TS 36.413): NR UE History Information introduction | Huawei | imported from 3GU |
| R3‑183543 | NR UE History Information introduction X2 | Huawei | imported from 3GU |
| R3‑183544 | Further Discussion and 38.413 pCR on NG Handover Type | ZTE | imported from 3GU |
| R3‑183545 | (TP for SA BL CR for TS 38.473):Support of PDCP Duplication for DRB | CATT | imported from 3GU |
| R3‑183546 | LS on updated RRC and LPP parameter list for further NB-IoT enhancements | RAN1, Huawei | imported from 3GU |
| R3‑183547 | Indication of the RLC Reset at the UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183548 | Introduction of a Configured TAC into the NR Neighbour Information IE and the Served NR Cell Information IE | Ericsson | imported from 3GU |
| R3‑183549 | Summary of offline discussion on SMTC information for neighbor cell | CATT | imported from 3GU |
| R3‑183550 | pCR to 38.460 on further discussion on E1 interface management message | Huawei | imported from 3GU |
| R3‑183551 | E1 UE-associated procedures | Ericsson | imported from 3GU |
| R3‑183552 | Draft TS skeleton for W1 general aspects and principles | China Unicom | imported from 3GU |
| R3‑183553 | Draft TS skeleton for W1 layer 1 | China Unicom | imported from 3GU |
| R3‑183554 | Draft TS skeleton for W1 signalling transport | China Unicom | imported from 3GU |
| R3‑183555 | Draft TS skeleton for W1 application protocol (W1AP) | China Unicom | imported from 3GU |
| R3‑183556 | W1 interface layer1 | Huawei, China Unicom | imported from 3GU |
| R3‑183557 | W1 interface signalling transport | Huawei, China Unicom | imported from 3GU |
| R3‑183558 | Registration with AMF Reallocation | Interdigital Asia LLC | imported from 3GU |
| R3‑183559 | Baseline CR for June version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99Bis | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183560 | TP for TR 38.874 on IAB architecture options | Intel | imported from 3GU |
| R3‑183561 | Baseline CR for September version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#99Bis | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183562 | Correction of the Limited List IE encoding to enable extensibility | Ericsson | imported from 3GU |
| R3‑183563 | TP for TR 38.874 on IAB NSA | Qualcomm | imported from 3GU |
| R3‑183564 | TP for TR 38.874 on IAB node integration | Qualcomm | imported from 3GU |
| R3‑183565 | TP for TR 38.874 on IAB topologies | Qualcomm | imported from 3GU |
| R3‑183566 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183567 | Retrieve UE Context at UE Re-establishment | Ericsson, Vodafone | imported from 3GU |
| R3‑183568 | X2AP CR for support of NR Multiple frequency band in EN-DC | Qualcomm Incorporated | imported from 3GU |
| R3‑183569 | LS on NR Cell Information signalled over X2 for EN-DC | Ericsson | imported from 3GU |
| R3‑183570 | CR for Clarification on resource coordination | NTT DOCOMO, INC., Qualcomm Incorporated | imported from 3GU |
| R3‑183571 | W1 interface general aspects and principles | Huawei, China Unicom | imported from 3GU |
| R3‑183572 | Reply LS on updates for TS 36.300 | Huawei | imported from 3GU |
| R3‑183573 | RAN3 TP to R2-1807880 on Introduction of EDT for eMTC and NB-IoT enhancements in TS 36.300 | Huawei | imported from 3GU |
| R3‑183574 | Reply LS on EDT procedures and AS NAS interaction | Huawei | imported from 3GU |
| R3‑183575 | Support of NB-IoT measurement enhancement and TDD Config | Huawei | imported from 3GU |
| R3‑183576 | Support of OTDOA in NB-IoT enhancement | Huawei | imported from 3GU |
| R3‑183577 | TP for TR 38.874 on IAB topologies | Qualcomm | imported from 3GU |
| R3‑183578 | Radio quality information report activation | Ericsson | imported from 3GU |
| R3‑183579 | pCR to 38.460 on further discussion on E1 interface management message | Huawei | imported from 3GU |
| R3‑183580 | Introduction of SA NR (38.401 Baseline CR covering RAN3 agreements) | NEC | imported from 3GU |
| R3‑183581 | Baseline CR for June version of TS 38.401 covering agreements of RAN3#99Bis on CPUP_Split | NEC | imported from 3GU |
| R3‑183582 | Introduction of SA NR (38.470 Baseline CR covering RAN3 agreements) | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑183583 | Introduction of SA NR (38.473 Baseline CR covering RAN3 agreements) | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑183584 | Introduction of SA NR (38.300 Baseline CR covering RAN3 agreements) | Nokia UK | imported from 3GU |
| R3‑183585 | Introduction of SA NR (36.413 Baseline CR covering RAN3 agreements) | Nokia Shanghai Bell | imported from 3GU |
| R3‑183586 | LTE-NR coexistence (36.423 Baseline CR covering RAN3 agreements) | Ericsson | imported from 3GU |
| R3‑183587 | Essential corrections of EN-DC for NSA NR (38.473 Baseline CR covering RAN3 agreements) | Huawei Technologies Co. Ltd. | imported from 3GU |
| R3‑183588 | Introduction of assistance information for DL PDCP duplication (38.425 Baseline CR covering RAN3 agreements) | Ericsson | imported from 3GU |
| R3‑183589 | TS 29.413 v0.2.0 covering agreements of RAN3#100 | Nokia | imported from 3GU |
| R3‑183590 | TS 38.410 v0.10.0 covering agreements of RAN3#100 | Nokia | imported from 3GU |
| R3‑183591 | TS 38.412 v0.4.0 covering agreements of RAN3#100 | NTT Docomo | imported from 3GU |
| R3‑183592 | TS 38.413 v0.9.0 covering agreements of RAN3#100 | Nokia | imported from 3GU |
| R3‑183593 | TS 38.414 v0.5.0 covering agreements of RAN3#100 | ZTE | imported from 3GU |
| R3‑183594 | TS 38.415 v0.2.0 covering agreements of RAN3#100 | Nokia | imported from 3GU |
| R3‑183595 | TS 38.420 v0.9.0 covering agreements of RAN3#100 | Qualcomm | imported from 3GU |
| R3‑183596 | TS 38.422 v0.3.0 covering agreements of RAN3#100 | NTT Docomo | imported from 3GU |
| R3‑183597 | TS 38.423 v0.9.0 covering agreements of RAN3#100 | Ericsson | imported from 3GU |
| R3‑183598 | TS 38.455 v0.7.0 covering agreements of RAN3#100 | Ericsson | imported from 3GU |
| R3‑183599 | TS 38.460 v0.4.0 covering agreements of RAN3#100 | Nokia | imported from 3GU |
| R3‑183600 | TS 38.462 v0.2.0 covering agreements of RAN3#100 | Huawei | imported from 3GU |
| R3‑183601 | TS 38.463 v0.3.0 covering agreements of RAN3#100 | Ericsson | imported from 3GU |
| R3‑183602 | TS 37.470 v0.1.0 covering agreements of RAN3#100 | China Unicom | imported from 3GU |
| R3‑183603 | TS 37.471 v0.1.0 covering agreements of RAN3#100 | China Unicom | imported from 3GU |
| R3‑183604 | Baseline CR for September version of RAN2 TS 38.300 (RAN3 part) covering agreements of RAN3#100 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183605 | TS 38.461 v0.2.0: Rapporteur's update | Intel | imported from 3GU |
| R3‑183606 | TS 38.421 v0.3.0: Rapporteur's update | CATT | imported from 3GU |
| R3‑183607 | Baseline CR for E-UTRA - NR Cell Resource Coordination for TS 36.423 covering agreements of RAN3#100 | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑183608 | Introduction of SA NR (38.473 Baseline CR covering RAN3 agreements) | Huawei | imported from 3GU |
| R3‑183609 | Essential corrections of EN-DC for NSA NR (38.473 Baseline CR covering RAN3 agreements) | Huawei | imported from 3GU |
page generated from database: 2024-04-22 07:58:53