3GPP TDocs (written contributions) at meeting
Meeting: R3-94 - 2016-11-14 to 2016-11-18, Reno, Nevada
meeting id: R3-94 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑162650 | RAN3-94 meeting agenda | MCC | imported from 3GU |
| R3‑162651 | RAN3-93 Bis meeting report | MCC | imported from 3GU |
| R3‑162652 | Further RAN3 actions for make-before-break | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162653 | Activation of make-before-break HO | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162654 | Impacts of data forwarding option 2 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162655 | TR 36.742 v0.2.1 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162656 | Solution for CA allocation taking into account X2 link characteristics | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162657 | Use-case and solutions for CA allocation taking into account the spatial user distribution | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162658 | Why do we need cooperation areas? | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162659 | Introduction of new period values for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162660 | Introduction of new period values for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162661 | RRC signaling between CU and DU | LG Electronics Inc. | imported from 3GU |
| R3‑162662 | TP for RRC signaling between CU and DU | LG Electronics Inc. | imported from 3GU |
| R3‑162663 | Introduction of localized MBMS deployment for V2X | LG Electronics Inc., CATT, Huawei | imported from 3GU |
| R3‑162664 | Adding V2X Services Authorized IE to RETRIEVE UE CONTEXT RESPONSE massage | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162665 | Support of small and variable MBMS areas for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162666 | Discussion on solutions to address backhaul long latency issue | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162667 | Support of small and variable MBMS areas for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162668 | Text Proposal for solutions to address backhaul long latency issue | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162669 | Evaluation on the solutions for DASH optimization (Issue 3 – case 2) | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162670 | Text Proposal for Evaluation on the solutions for DASH optimization (Issue 3 – case 2) | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162671 | Authorization for Pedestrian UE over S1 | LG Electronics Inc., Huawei, CATT, ZTE | imported from 3GU |
| R3‑162672 | Discussion on solutions for TCP optimization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162673 | Text Proposal for solutions to address issue 2 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162674 | Authorization for Pedestrian UE over X2 | LG Electronics Inc., Huawei, CATT, ZTE | imported from 3GU |
| R3‑162675 | Discussion on support of network slicing in RAN | LG Electronics Inc. | imported from 3GU |
| R3‑162676 | Text proposal on RAN selection of CN entity | LG Electronics Inc. | imported from 3GU |
| R3‑162677 | Further consideration on RAN internal interface Xn | LG Electronics Inc. | imported from 3GU |
| R3‑162678 | Text Proposal for RAN internal interface Xn | LG Electronics Inc. | imported from 3GU |
| R3‑162679 | Consideration on inter gNB mobility without CN type change | LG Electronics Inc. | imported from 3GU |
| R3‑162680 | Text Proposal on inter gNB mobility without CN type change | LG Electronics Inc. | imported from 3GU |
| R3‑162681 | Open issues on tight interworking between new RAT and LTE | LG Electronics Inc. | imported from 3GU |
| R3‑162682 | TP on tight interworking between new RAT and LTE | LG Electronics Inc. | imported from 3GU |
| R3‑162683 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑162684 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell, Intel, Ruckus, Qualcomm | imported from 3GU |
| R3‑162685 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Intel | imported from 3GU |
| R3‑162686 | Definition of split option 4 | Interdigital Asia LLC | imported from 3GU |
| R3‑162687 | Centralized RRM and Scheduling | Interdigital Asia LLC | imported from 3GU |
| R3‑162688 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162689 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162690 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Intel | imported from 3GU |
| R3‑162691 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell, Intel, Ruckus, Qualcomm | imported from 3GU |
| R3‑162692 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | imported from 3GU |
| R3‑162693 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑162694 | Discussion on UE context fetch for lightly connected UE | LG Electronics Inc. | imported from 3GU |
| R3‑162695 | Discussion on open issues for lightly connected UE | LG Electronics Inc. | imported from 3GU |
| R3‑162696 | Additional Benefit Considerations for Option 3-1 | AT&T | imported from 3GU |
| R3‑162697 | Discussion on support of small and variable areas for V2X | CATT | imported from 3GU |
| R3‑162698 | Support of small and variable areas for V2X | CATT | imported from 3GU |
| R3‑162699 | V2X Authorization via RETRIEVE UE CONTEXT RESPONSE | CATT | imported from 3GU |
| R3‑162700 | Discussion on QoS mapping for UL | CATT | imported from 3GU |
| R3‑162701 | Discussion on routing of uplink packets | CATT | imported from 3GU |
| R3‑162702 | Discussion on open issues for LC | CATT | imported from 3GU |
| R3‑162703 | Consideration on Tight Interworking with Xx Interface | ZTE Corporation | imported from 3GU |
| R3‑162704 | Consideration on SCG Split Bearer with Option 4a and 7a | ZTE Corporation | imported from 3GU |
| R3‑162705 | Further Consideration on New RAN Aggregation Scenarios due to CU-DU Split | ZTE Corporation | imported from 3GU |
| R3‑162706 | Further Consideration on Xn Procedures for NR/LTE Tight-Interworking | ZTE Corporation | imported from 3GU |
| R3‑162707 | WLAN Measurement Framework for eLWIP | Telekom Research & Development Sdn. Bhd. | imported from 3GU |
| R3‑162708 | Tight interworking procedures for Option 3/3a | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162709 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162710 | Introduction of DRX enhancements | HuaWei Technologies Co., Ltd | imported from 3GU |
| R3‑162711 | Introduction of localized MBMS deployment for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162712 | Introduction of WLAN band indication | Intel Corporation (UK) Ltd | imported from 3GU |
| R3‑162713 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162714 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162715 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162716 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162717 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162718 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162719 | Introduction of UE PC5 AMBR over S1 | CATT, ZTE, Huiawei | imported from 3GU |
| R3‑162720 | Introduction of UE-PC5-AMBR | Huawei, CATT | imported from 3GU |
| R3‑162721 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑162722 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑162723 | Some Clarification for NW Slicing | ZTE Corporation | imported from 3GU |
| R3‑162724 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑162725 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162726 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162727 | Enabling uplink data bearers | Nokia Networks | imported from 3GU |
| R3‑162728 | Flexibility of RAN functional split | Nokia, Alcatel-Lucent Shanghai Bell, KT | imported from 3GU |
| R3‑162729 | Clarification on Option 3-1 | Nokia, Alcatel-Lucent Shanghai Bell, KT, CATT | imported from 3GU |
| R3‑162730 | Interface specification and general principles for Option 3-1 | Nokia, Alcatel-Lucent Shanghai Bell, KT, CATT | imported from 3GU |
| R3‑162731 | Some Issues with NW Slicing in Multiple Connectivity Contexts | ZTE Corporation | imported from 3GU |
| R3‑162732 | TP for NW Slicing in Multiple Connectivity Contexts | ZTE Corporation | imported from 3GU |
| R3‑162733 | TP for Inter-gNB Multiple Connectivity Operation | ZTE Corporation | imported from 3GU |
| R3‑162734 | Impacts on RAN3 by Down-selected ME Solutions | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑162735 | Draft ME Stage2 | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑162736 | Draft ME Stage3 | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑162737 | Support of SC-PTM for NB-IoT | CATT | imported from 3GU |
| R3‑162738 | NG interface procedures analysis | Samsung | imported from 3GU |
| R3‑162739 | Mobility scenarios cleaning up | Samsung | imported from 3GU |
| R3‑162740 | Mobility with CN type change | Samsung | imported from 3GU |
| R3‑162741 | Impacts for one logical node of co-sited (e)LTE eNB and gNB | Samsung | imported from 3GU |
| R3‑162742 | Correction for Multi-connectivity Function | Samsung | imported from 3GU |
| R3‑162743 | Tight interworking between new RAN node | Samsung | imported from 3GU |
| R3‑162744 | NR QOS model for UL and DL | Samsung | imported from 3GU |
| R3‑162745 | Data forwarding options for the make-before-break LTE mobility enhancement | Samsung | imported from 3GU |
| R3‑162746 | Introduction of "Maintain source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162747 | Make before break solution in SeNB change scenario | Samsung | imported from 3GU |
| R3‑162748 | Support SeNB change for "Maintain source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162749 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom, Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, ZTE, CMCC | imported from 3GU |
| R3‑162750 | LTE handover while keeping LWA: PDCP related security aspects | Samsung | imported from 3GU |
| R3‑162751 | QoS Mapping Transfer for UL transmission | Samsung | imported from 3GU |
| R3‑162752 | Discussion on RAN initiated paging | Samsung | imported from 3GU |
| R3‑162753 | Discussion on CP and existing functionalities | Samsung | imported from 3GU |
| R3‑162754 | Discussion on X2 absent | Samsung | imported from 3GU |
| R3‑162755 | Suspend/Release in case UE requests to connect without data activity | Samsung | imported from 3GU |
| R3‑162756 | Consideration of Light connection open issues | Huawei, China Unicom | imported from 3GU |
| R3‑162757 | Introduction of light connection in X2AP | Huawei, Nokia, China Telecom, China Unicom | imported from 3GU |
| R3‑162758 | Introduction of light connection in S1AP | Huawei, Nokia, China Telecom,China Unicom | imported from 3GU |
| R3‑162759 | S1 Context fetch for Light Connection | Huawei | imported from 3GU |
| R3‑162760 | Introduction of S1 context fetch | Huawei, China Unicom | imported from 3GU |
| R3‑162761 | Offline discussion summary of Mobility in NB-IoT enhancements | Huawei (Rapporteur) | imported from 3GU |
| R3‑162762 | Further consideration on mobility in NB-IoT enhancements | Huawei, China Unicom | imported from 3GU |
| R3‑162763 | Mobility support in NB-IoT enhancement in X2AP | Huawei | imported from 3GU |
| R3‑162764 | Mobility support in NB-IoT enhancement in S1AP | Huawei | imported from 3GU |
| R3‑162765 | Coverage enhancement in NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162766 | Introduction of Coverage Level Information in M2 interface | Huawei | imported from 3GU |
| R3‑162767 | Introduction of Coverage Level Information in M3 interface | Huawei | imported from 3GU |
| R3‑162768 | NPRACH Configuration exchanging for NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162769 | Introduction of NPRACH configuration in X2AP | Huawei | imported from 3GU |
| R3‑162770 | Positioning in NB-IoT enhancement | Huawei, China Unicom | imported from 3GU |
| R3‑162771 | Consideration on principles for QoS in RAN | LG Electronics Inc. | imported from 3GU |
| R3‑162772 | TP for consideration on principles for QoS in RAN | LG Electronics Inc. | imported from 3GU |
| R3‑162773 | Further consideration on Option 3-1 | LG Electronics Inc. | imported from 3GU |
| R3‑162774 | TP for further consideration on Option 3-1 | LG Electronics Inc. | imported from 3GU |
| R3‑162775 | Target cell selection for eMTC UEs | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162776 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T, Samsung, LG Electronics Inc., Qualcomm Incorporated | imported from 3GU |
| R3‑162777 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T, Samsung, LG Electronics Inc., Qualcomm Incorporated | imported from 3GU |
| R3‑162778 | Considerations on RAN functions | CATT,China Telecom | imported from 3GU |
| R3‑162779 | TP on scenarios for mobility | CATT,China Telecom | imported from 3GU |
| R3‑162780 | Consideration on Xn interface procedures | CATT,China Telecom | imported from 3GU |
| R3‑162781 | Consideration on CP procedures for LTE and NR interworking | CATT,China Telecom | imported from 3GU |
| R3‑162782 | Align with SA2 on RAN selection of CN entity | CATT,China Telecom | imported from 3GU |
| R3‑162783 | Enhanced LWIP network interface | Intel Corporation, Qualcomm Incorporated, Mediatek Inc., China Telecom | imported from 3GU |
| R3‑162784 | eLWIP: Xs user plane protocol | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑162785 | eLWIP: Xs data transport | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑162786 | UL QoS mapping for eLWA | Intel Corporation | imported from 3GU |
| R3‑162787 | WLAN QoS mapping in UL – first option | Intel Corporation | imported from 3GU |
| R3‑162788 | UL routing for eLWA | Intel Corporation | imported from 3GU |
| R3‑162789 | Enhnaced MME overload procedure | Intel Corporation, U.S. Cellular | imported from 3GU |
| R3‑162790 | Critical data discard on UL Video transmission | Intel Corporation | imported from 3GU |
| R3‑162791 | Alignment between high functional split and DC | Intel Corporation | imported from 3GU |
| R3‑162792 | Further consideration on CU-DU split granularity | Intel Corporation | imported from 3GU |
| R3‑162793 | TP on alignment between high functional split and DC | Intel Corporation | imported from 3GU |
| R3‑162794 | Support of Light connection procedure | Intel Corporation | imported from 3GU |
| R3‑162795 | Stage-2: Support of Light connection | Intel Corporation | imported from 3GU |
| R3‑162796 | Mitigation of impacts to legacy functionalities from light connection | Intel Corporation | imported from 3GU |
| R3‑162797 | NR QoS considerations | Intel Corporation | imported from 3GU |
| R3‑162798 | Interworking between EPC and NGC | Intel Corporation | imported from 3GU |
| R3‑162799 | Benefits of hierarchical centralized control architecture | IAESI, Thales, Fairspectrum | imported from 3GU |
| R3‑162800 | Functional benefits of Central Coordination | IAESI,Thales, Fairspectrum | imported from 3GU |
| R3‑162801 | Introduction of band 48 | Nokia | imported from 3GU |
| R3‑162802 | TP for hierarchical CP architecture | IAESI, Thales, Fairspectrum | imported from 3GU |
| R3‑162803 | Introduction of band 48 | Nokia | imported from 3GU |
| R3‑162804 | TP on benefits of the hierarchical Central Coordination | IAESI, Thales, Fairspectrum | imported from 3GU |
| R3‑162805 | Changes needed to enable LWIP over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162806 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162807 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162808 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162809 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162810 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162811 | Access Categories for LWA uplink bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162812 | Access Category information for uplink LWA bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162813 | Access Category information for uplink LWA bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162814 | UL tunnel identification: further considerations | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162815 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162816 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162817 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162818 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162819 | Correction of handling of GBR bearer in the MME | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | imported from 3GU |
| R3‑162820 | Corrections to TR 38.801 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162821 | Architecture of New RAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162822 | Additional functions of the Xn interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162823 | Network based and UE based mobility | Qualcomm Incorporated | imported from 3GU |
| R3‑162824 | Network Identifiers Analysis | Qualcomm Incorporated | imported from 3GU |
| R3‑162825 | Flow QoS Principles | Qualcomm Incorporated | imported from 3GU |
| R3‑162826 | Granularity of NG-U Tunnel | Qualcomm Incorporated | imported from 3GU |
| R3‑162827 | Slice selection in NG Flex | Qualcomm Incorporated | imported from 3GU |
| R3‑162828 | Slice Isolation in RAN | Qualcomm Incorporated | imported from 3GU |
| R3‑162829 | Xn Interface In Centralized RAN Deployment | Qualcomm Incorporated | imported from 3GU |
| R3‑162830 | RRM Coordination over Xn | Qualcomm Incorporated | imported from 3GU |
| R3‑162831 | Xn Interface Procedures | Qualcomm Incorporated | imported from 3GU |
| R3‑162832 | RAN Paging | Qualcomm Incorporated | imported from 3GU |
| R3‑162833 | Light Connection Model Analysis | Qualcomm Incorporated | imported from 3GU |
| R3‑162834 | CN Impact Analysis | Qualcomm Incorporated | imported from 3GU |
| R3‑162835 | Context Fetch and Mobility | Qualcomm Incorporated | imported from 3GU |
| R3‑162836 | Resolving ambiguity of counting procedures when receiving eMBMS on SCell or non-serving cell | Qualcomm Incorporated | imported from 3GU |
| R3‑162837 | Resolving ambiguous counting responses | Qualcomm Incorporated | imported from 3GU |
| R3‑162838 | Resolving ambiguous counting responses | Qualcomm Incorporated | imported from 3GU |
| R3‑162839 | Introduction of Transmission Points for OTDOA in Shared Cell-ID Scenario and PRS based Terrestrial Beacon Systems | Qualcomm Incorporated | imported from 3GU |
| R3‑162840 | CU-DU spit option selection and interface specification | NTT DOCOMO, INC., Deutsche Telekom, KT, SK Telecom, Fujitsu, CMCC, Telecom Italia, Orange | imported from 3GU |
| R3‑162841 | CU-DU split: Summary table | NTT DOCOMO INC. | imported from 3GU |
| R3‑162842 | CU-DU interface: U-plane aspects | NTT DOCOMO INC. | imported from 3GU |
| R3‑162843 | Clarification on URLLC Requirement | ZTE Corporation | imported from 3GU |
| R3‑162844 | Discussion on Xn interface | ZTE Corporation | imported from 3GU |
| R3‑162845 | Mobility scenarios for “inactive state” | ZTE Corporation | imported from 3GU |
| R3‑162846 | Questions to SA2 on Local Breakout | ZTE Corporation | imported from 3GU |
| R3‑162847 | Further Considerations on Split Option 3 | ZTE Corporation | imported from 3GU |
| R3‑162848 | Discussion on Mobility with CN type change | ZTE Corporation | imported from 3GU |
| R3‑162849 | Discussion on Mobility without CN type change | ZTE Corporation | imported from 3GU |
| R3‑162850 | Further update on the NG-C interface | ZTE Corporation | imported from 3GU |
| R3‑162851 | Update on the key QoS principles in RAN3 | ZTE Corporation | imported from 3GU |
| R3‑162852 | Clarification on CU-DU split options | ZTE Corporation | imported from 3GU |
| R3‑162853 | The left issues on NB IOT mobility enhancement | ZTE Corporation | imported from 3GU |
| R3‑162854 | RAN functional split considerations and preferences | Verizon | imported from 3GU |
| R3‑162855 | Support of SC-PTM for eMTC | CATT | imported from 3GU |
| R3‑162856 | Support of SC-PTM for eMTC | CATT | imported from 3GU |
| R3‑162857 | UP protocol stack over Xn | Samsung | imported from 3GU |
| R3‑162858 | UP protocol stack over NG | Samsung | imported from 3GU |
| R3‑162859 | Liaison out on NR for inter-WG dependent topics | NTT DOCOMO INC. | imported from 3GU |
| R3‑162860 | Principles and key issues for Qos | CATT,China Telecom | imported from 3GU |
| R3‑162861 | QoS impact on PDU session management procedure | CATT, China Telecom | imported from 3GU |
| R3‑162862 | Clarification on function split option 3-1 | CATT, China Telecom | imported from 3GU |
| R3‑162863 | Considerations on RAN function split between CU and DU | CATT,China Telecom | imported from 3GU |
| R3‑162864 | UE Identity for mobility enhancement | Huawei | imported from 3GU |
| R3‑162865 | Further considerations on Option3 | Huawei | imported from 3GU |
| R3‑162866 | Further considerations on traffic aggregation | Huawei | imported from 3GU |
| R3‑162867 | Discussion on the solution of video optimization | Huawei | imported from 3GU |
| R3‑162868 | TP for the solution of video optimization | Huawei, CMCC | imported from 3GU |
| R3‑162869 | TP for the evaluation on the DASH optimization solution | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162870 | Discussion on the solution of TCP optimization | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑162871 | TP for the solutions of TCP optimization | Huawei, Qualcomm Incorporated, CMCC, | imported from 3GU |
| R3‑162872 | TP for Video object deadline-aware scheduling | QUALCOMM Incorporated, Huawei, CMCC | imported from 3GU |
| R3‑162873 | Radio-aware TCP optimization | QUALCOMM Incorporated, Huawei | imported from 3GU |
| R3‑162874 | TP for radio-aware TCP optimization | QUALCOMM Incorporated, Huawei, CMCC | imported from 3GU |
| R3‑162875 | Support of Redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162876 | [Draft] LS on support of redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162877 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162878 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162879 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162880 | Further consideration on non-standalone E-UTRA architecture | CMCC | imported from 3GU |
| R3‑162881 | Clarification for flow control buffer of option3-2 | CMCC | imported from 3GU |
| R3‑162882 | Transmission robustness of option3-2 | CMCC | imported from 3GU |
| R3‑162883 | Support of multiple operators for V2X | CMCC, CATT | imported from 3GU |
| R3‑162884 | Support of multiple operators for V2X | CMCC, CATT | imported from 3GU |
| R3‑162885 | Editorial update of Draft TR 36.933 | CMCC | imported from 3GU |
| R3‑162886 | Solution to backhaul long latency issue | CMCC, Qualcomm Incorporated | imported from 3GU |
| R3‑162887 | TP for service information acquisition and UE assisted local cache | CMCC, Qualcomm Incorporated | imported from 3GU |
| R3‑162888 | Paging reception in eDRX not allowed | NEC | imported from 3GU |
| R3‑162889 | Paging reception in eDRX not allowed | NEC | imported from 3GU |
| R3‑162890 | Function split options selection | NEC | imported from 3GU |
| R3‑162891 | Function split options selection | NEC | imported from 3GU |
| R3‑162892 | Inter gNBs Mobility without CN type change | NEC | imported from 3GU |
| R3‑162893 | Inter gNBs Mobility without CN type change | NEC | imported from 3GU |
| R3‑162894 | Question to SA2 and RAN2 on Network Slicing | NEC | imported from 3GU |
| R3‑162895 | CN Assisted Paging Fallback: How to make it work? | NEC | imported from 3GU |
| R3‑162896 | How a Source determines Connectivity to the Same WT in inter-eNB HO? | NEC | imported from 3GU |
| R3‑162897 | WT Notifying neighbour eNB information on Xw | NEC | imported from 3GU |
| R3‑162898 | eNB Notifying neighbour WT information on X2 | NEC | imported from 3GU |
| R3‑162899 | Use of DCN-ID for better NNSF | NEC | imported from 3GU |
| R3‑162900 | Adding DCN-ID to S1 Setup Response | NEC | imported from 3GU |
| R3‑162901 | Functions and protocols of eLTE eNB connecting to NGC | Huawei | imported from 3GU |
| R3‑162902 | Network selection and access control framework for eLTE | Huawei | imported from 3GU |
| R3‑162903 | Procedures Analysis for the Xn Interface | Huawei | imported from 3GU |
| R3‑162904 | User Plane Protocol of NG/Xn | Huawei | imported from 3GU |
| R3‑162905 | Need for Efficient Session Configuration | Huawei | imported from 3GU |
| R3‑162906 | NG-U Protocol Oblivious Encapsulation Design | Huawei | imported from 3GU |
| R3‑162907 | DRX enhancements in CELL_FACH | Huawei | imported from 3GU |
| R3‑162908 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑162909 | TP editorial changes for joint operation | Huawei | imported from 3GU |
| R3‑162910 | Configuration impacts of Dual Cell E-DCH operation enhancements | Huawei | imported from 3GU |
| R3‑162911 | Introduction of Dual Cell E-DCH operation enhancements configuration | Huawei | imported from 3GU |
| R3‑162912 | Introduction of Dual Cell E-DCH operation enhancements configuration | Huawei | imported from 3GU |
| R3‑162913 | Enhanced TTI switching of Dual Cell E-DCH operation enhancements | Huawei | imported from 3GU |
| R3‑162914 | Introduction of enhanced TTI switching of Dual Cell E-DCH operation enhancements | Huawei | imported from 3GU |
| R3‑162915 | Introduction of enhanced TTI switching of Dual Cell E-DCH operation enhancements | Huawei | imported from 3GU |
| R3‑162916 | RAN3 impacts of QMC for streaming services | Huawei | imported from 3GU |
| R3‑162917 | Introduction of QMC for streaming services | Huawei | imported from 3GU |
| R3‑162918 | Introduction of QMC for streaming services | Huawei | imported from 3GU |
| R3‑162919 | Introduction of QMC for streaming services | Huawei | imported from 3GU |
| R3‑162920 | Introduction of QMC for streaming services | Huawei | imported from 3GU |
| R3‑162921 | TR 36.898 v2.1.0 | Huawei | imported from 3GU |
| R3‑162922 | Conclusion of the SI for Network Synchronization | Huawei | imported from 3GU |
| R3‑162923 | Motivation for the new WI of Network Synchronization | Huawei | imported from 3GU |
| R3‑162924 | New WID on Network Assistance for Network Synchronization | Huawei | imported from 3GU |
| R3‑162925 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.3.0 | China Unicom | imported from 3GU |
| R3‑162926 | User plane design details for LTE-NR tight interworking | Huawei | imported from 3GU |
| R3‑162927 | Further comparison on user plane architecture options for LTE-NR tight interworking | Huawei | imported from 3GU |
| R3‑162928 | LTE-NR tight interworking CP procedure | Huawei | imported from 3GU |
| R3‑162929 | Further justifications on Xx interface | Huawei | imported from 3GU |
| R3‑162930 | Possible RAN3 impacts on UE capability coordination | Huawei | imported from 3GU |
| R3‑162931 | Consideration of RAN impacts on migration | LG Electronics Inc. | imported from 3GU |
| R3‑162932 | Multi link Transport network | THALES | imported from 3GU |
| R3‑162933 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell, Qualcomm, Huawei, NTT Docomo Inc | imported from 3GU |
| R3‑162934 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell, Qualcomm, Huawei, NTT Docomo Inc | imported from 3GU |
| R3‑162935 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell, Qualcomm, Huawei, NTT Docomo Inc | imported from 3GU |
| R3‑162936 | Introduction to Stage 2 and Scenarios in Light Connected mode | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | imported from 3GU |
| R3‑162937 | Introduction of Light Connected State | Nokia, Alcatel-Lucent Shanghai Bell, Huawei, China Telecom, China Unicom | imported from 3GU |
| R3‑162938 | Suspension Options for mobility out of RAN Paging Area | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162939 | Paging Identities used in Light Connected mode | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162940 | Key characteristics of NG-U protocol stack options | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162941 | Management and Configuration of SCTP/IP over NG2 interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162942 | Correction of RAN Selection of CN Entity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162943 | Correction of Selection of RAN part of Network Slice | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162944 | Slice Availability and impact on Mobility | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162945 | Detailed description of QoS framework in RAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162946 | Text Proposal for Session Modification Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162947 | Solutions for intra New-RAN Handover | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162948 | Paging and Mobility in Inactive State | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162949 | Discussion on the CSI-RSRP reporting for E-CID enhancements | Huawei | imported from 3GU |
| R3‑162950 | Introduction of CSI-RSRP for ECID enhancements | Huawei | imported from 3GU |
| R3‑162951 | Procedure of initial access | Huawei | imported from 3GU |
| R3‑162952 | Procedure of inter-RAT handover without CN change | Huawei | imported from 3GU |
| R3‑162953 | Procedure of inter-RAT handover with CN change | Huawei | imported from 3GU |
| R3‑162954 | Key principles for Support of Network Slicing in RAN | Huawei | imported from 3GU |
| R3‑162955 | Resource Management between Slices | Huawei | imported from 3GU |
| R3‑162956 | RAN Support of Slice Availability | Huawei | imported from 3GU |
| R3‑162957 | The QoS procedures in RAN3 | Huawei | imported from 3GU |
| R3‑162958 | QoS considerations in Handover procedure | Huawei | imported from 3GU |
| R3‑162959 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162960 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162961 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162962 | OTDOA Enhancements for Same-PCI Issue and Multiple TPs | Ericsson | imported from 3GU |
| R3‑162963 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑162964 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑162965 | Introduction of an E-UTRAN triggered S1 Overload procedure | Ericsson | imported from 3GU |
| R3‑162966 | Introduction of an E-UTRAN triggered S1 Overload procedure | Ericsson | imported from 3GU |
| R3‑162967 | Extending XwAP for eLWIP | Ericsson LM | imported from 3GU |
| R3‑162968 | Supporting LWIP with XwAP - New Procedure Descriptions | Ericsson LM | imported from 3GU |
| R3‑162969 | QoS and bearer for DC between LTE and NR | NTT DOCOMO INC. | imported from 3GU |
| R3‑162970 | Text Proposal to TR 38.801 on Dual Connectivity between LTE and NR via EPC | NTT DOCOMO INC. | imported from 3GU |
| R3‑162971 | Text Proposal to TR 38.801 on Dual Connectivity between LTE and NR via EPC | NTT DOCOMO INC. | imported from 3GU |
| R3‑162972 | LWIP Addition and Modification | Ericsson LM | imported from 3GU |
| R3‑162973 | Scenarios for inter-RAT mobility | Ericsson | imported from 3GU |
| R3‑162974 | Scenarios for inter-RAT mobility | Ericsson | imported from 3GU |
| R3‑162975 | New RAN architecture | Ericsson | imported from 3GU |
| R3‑162976 | On the NG-U and Xn-U protocol stack | Ericsson | imported from 3GU |
| R3‑162977 | UP stack for NG and Xn interface | Ericsson | imported from 3GU |
| R3‑162978 | Discussion on NG procedures | Ericsson | imported from 3GU |
| R3‑162979 | TP on NG procedures | Ericsson | imported from 3GU |
| R3‑162980 | Support of legacy UEs in the 5G System framework | Ericsson | imported from 3GU |
| R3‑162981 | pCR related to the Support of legacy UEs in the 5G System frameworkt paper | Ericsson | imported from 3GU |
| R3‑162982 | Xn interface procedures | Ericsson | imported from 3GU |
| R3‑162983 | pCR on Xn interface procedures | Ericsson | imported from 3GU |
| R3‑162984 | Availability of Network Slices | Ericsson | imported from 3GU |
| R3‑162985 | TP on Availability of Network Slices | Ericsson | imported from 3GU |
| R3‑162986 | Analysis of interim Agreements for QoS and PDU Session Management | Ericsson | imported from 3GU |
| R3‑162987 | pCR related to the QoS and PDU Session Management paper | Ericsson | imported from 3GU |
| R3‑162988 | Inter-System and intra-system inter-RAT mobility | Ericsson | imported from 3GU |
| R3‑162989 | Possible realisation of Option 2 | Ericsson | imported from 3GU |
| R3‑162990 | TP on possible realisation of Option 2 | Ericsson | imported from 3GU |
| R3‑162991 | Analysis of Option 3 | Ericsson | imported from 3GU |
| R3‑162992 | TP on Analysis of Option 3 | Ericsson | imported from 3GU |
| R3‑162993 | Observations on migration paths | Ericsson | imported from 3GU |
| R3‑162994 | Observations on migration paths | Ericsson | imported from 3GU |
| R3‑162995 | Addition of the abnormal case for the introduction of Multi-carrier Enhancement | Ericsson | imported from 3GU |
| R3‑162996 | Addition of the abnormal case for the introduction of Multi-carrier Enhancement | Ericsson | imported from 3GU |
| R3‑162997 | Addition of the abnormal case for the introduction of Multi-carrier Enhancement | Ericsson | imported from 3GU |
| R3‑162998 | Introduction of fast TTI switching in Multi-carrier Enhancements | Ericsson | imported from 3GU |
| R3‑162999 | Introduction of fast TTI switching in Multi-carrier Enhancements | Ericsson | imported from 3GU |
| R3‑163000 | Introduction of fast TTI switching in Multi-carrier Enhancements | Ericsson | imported from 3GU |
| R3‑163001 | Information transfer between eNB, WT and UE for LWIP | Ericsson | imported from 3GU |
| R3‑163002 | Different PLMN IDs and Enhanced TV Services | Ericsson | imported from 3GU |
| R3‑163003 | PLMN ID Check and Enhanced TV Services | Ericsson | imported from 3GU |
| R3‑163004 | DTX/DRX enhancements in CELL_FACH | Ericsson | imported from 3GU |
| R3‑163005 | DTX/DRX enhancements in CELL_FACH | Ericsson | imported from 3GU |
| R3‑163006 | Remove impact on LTE stage 2 from Flexible eNB-ID and Cell-ID WI | Ericsson | imported from 3GU |
| R3‑163007 | Service Continuity and Mobility | Ericsson | imported from 3GU |
| R3‑163008 | Analysis of RRC configured RAN paging area concepts | Ericsson | imported from 3GU |
| R3‑163009 | Light Connection – forwarding of user data and control plane data on X2 and S1 | Ericsson | imported from 3GU |
| R3‑163010 | On Suspending the UE a la Rel-13 upon the old eNB’s behalf | Ericsson | imported from 3GU |
| R3‑163011 | Analysis of eNB impacts while introducing a RAN paging area | Ericsson | imported from 3GU |
| R3‑163012 | Maintaining paging assistance data during mobility and over idle-active transitions | Ericsson | imported from 3GU |
| R3‑163013 | Issues with a cell list as UE specific paging area | Ericsson | imported from 3GU |
| R3‑163014 | Extending the Cell Portion ID Range | Ericsson | imported from 3GU |
| R3‑163015 | Cell Portion ID Extension | Ericsson | imported from 3GU |
| R3‑163016 | [DRAFT] LS on Cell Portion ID Extension | Ericsson | imported from 3GU |
| R3‑163017 | Ignoring the UE WLAN MAC Address at Handover | Ericsson | imported from 3GU |
| R3‑163018 | Uplink QoS Handling | Ericsson | imported from 3GU |
| R3‑163019 | Solution proposal for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑163020 | Solution proposal for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑163021 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163022 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163023 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163024 | eNB Overload handling for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑163025 | Incomplete further indoor positioning enhancements objectives | NextNav | imported from 3GU |
| R3‑163026 | Consideration on session release and modification | LG Electronics Inc. | imported from 3GU |
| R3‑163027 | Change in X2 TNL performances use-case and solution | Fujitsu | imported from 3GU |
| R3‑163028 | Functions and Mobility Scenarios for eLTE eNB | China Telecommunications | imported from 3GU |
| R3‑163029 | NR inactive state principles - UE ID | Qualcomm Incorporated | imported from 3GU |
| R3‑163030 | NR inactive state principles - notification area | Qualcomm Incorporated | imported from 3GU |
| R3‑163031 | eLWIP: Xs stage-2 proposal for TS 36.300 | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163032 | eLWIP: Xs Application Protocol | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163033 | Introducing UE throughput indication | Qualcomm Incorporated, Intel Corporation, Xiaomi, IAESI, NEC, China Telecom | imported from 3GU |
| R3‑163034 | Update of TR 38.801 (v061) | NTT DOCOMO INC. | imported from 3GU |
| R3‑163035 | Introduction of the light connection over S1 | Samsung | imported from 3GU |
| R3‑163036 | Introduction of the light connection over X2 | Samsung | imported from 3GU |
| R3‑163037 | TP to address solutions for issue 4 | Intel Corporation (UK) Ltd | imported from 3GU |
| R3‑163038 | TP on CU-DU split granularity | Intel Corporation (UK) Ltd | imported from 3GU |
| R3‑163039 | CU-DU spit option selection and interface specification | NTT DOCOMO, INC., Fujitsu, CMCC, KT, SK Telecom, Deutsche Telekom, Orange, Telecom Italia, Verizon | imported from 3GU |
| R3‑163040 | Update to NGMN Description of Network Slicing Concept (To: 3GPP TSG SA WG2, 3GPP TSG SA WG5, TSG RAN3, ETSI NFV, CC: 3GPP TSG SA, 3GPP SA1, 3GPP TSG RAN) | NGMN, Orange | imported from 3GU |
| R3‑163041 | NGMN Paper on Edge Computing (To: 3GPP TSG SA WG2, CC: 3GPP TSG SA, 3GPP SA1, 3GPP TSG RAN, 3GPP RAN3, ETSI ISG MEC, Broadband Forum, Wireless Broadband Alliance, IEEE LAN/MAN) | NGMN, Orange | imported from 3GU |
| R3‑163042 | Reply LS to NB-IOT NAS retransmission timers (To: 3GPP SA WG2, 3GPP RAN WG3, 3GPP RAN WG2 ) | 3GPP CT1, Huawei | imported from 3GU |
| R3‑163043 | Reply LS on the progress and questions for the light connection (To: 3GPP RAN2, Cc: 3GPP SA2, 3GPP RAN3) | 3GPP CT1, Huawei | imported from 3GU |
| R3‑163044 | Liaison about ETSI ISG NGP (Next Generation protocols) (To: 3GPP TSG-SA, 3GPP TSG-RAN, 3GPP TSG-CT, 3GPP SA1, 3GPP SA2, 3GPP RAN3 ) | ETSI ISG NGP, Huawei | imported from 3GU |
| R3‑163045 | LS on collisions between SC-PTM and Paging in NB-IoT (To: 3GPP RAN2, 3GPP RAN3, 3GPP SA2 ) | 3GPP RAN1, Hisilicon | imported from 3GU |
| R3‑163046 | LS on Multipath RSTD reporting and CRS usage together with PRS (To: 3GPP RAN2, CC: 3GPP RAN3, 3GPP RAN4) | 3GPP RAN1, Ericsson, Intel | imported from 3GU |
| R3‑163047 | LS on coverage enhancement in SC-PTM for FeMTC and eNB-IoT (To: 3GPP RAN1, CC: 3GPP RAN3) | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑163048 | Reply LS on QoE reporting for streaming services (To: 3GPP SA4, CC: 3GPP RAN3, 3GPP SA5) | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑163049 | Reply LS on overload control for CP CIoT EPS optimization (To: 3GPP SA2, 3GPP RAN3, CC: 3GPP CT1) | 3GPP RAN2, NEC | imported from 3GU |
| R3‑163050 | Response LS on Multiple TMGIs for support of small and variable MBMS areas. (To: 3GPP RAN3, CC: 3GPP SA2) | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑163051 | LS to SA4 on RAN-assisted codec adaptation solution (To: 3GPP SA4, CC: 3GPP RAN3) | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑163052 | LS on S-TMSI in RAN paging (To:3GPP SA3, Cc: 3GPP RAN3, 3GPP CT1) | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑163053 | Security aspects of RRC Connection Re-Establishment for NB-IoT (DoNAS) (To: 3GPP SA3, CC: 3GPP RAN3, 3GPP CT1) | 3GPP RAN2, Vodafone | imported from 3GU |
| R3‑163054 | LS on RAN2 agreements on Context Aware Service Delivery SI (To: 3GPP RAN3 ) | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑163055 | LS on RAN2 agreements for mobility enhancement (To: 3GPP RAN3, CC: 3GPP RAN1, 3GPP RAN4) | 3GPP RAN2, Intel | imported from 3GU |
| R3‑163056 | LS on RAN2 agreements for NR DL-based mobility and Cell definition (To: 3GPP RAN1, CC: 3GPP RAN3, 3GPP RAN4) | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑163057 | LS on The progress and questions for the light connection (To: 3GPP RAN3, 3GPP CT1, CC: 3GPP SA2) | 3GPP RAN2, Huawei, Intel | imported from 3GU |
| R3‑163058 | LS on mobility enhancements for eNB-IoT (To: 3GPP RAN3, 3GPP CT1, 3GPP SA2 ) | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑163059 | LS on UE demodulation performance enhancement indicator for SFN scenarios (To: 3GPP RAN2, CC: 3GPP RAN3) | 3GPP RAN4, Huawei | imported from 3GU |
| R3‑163060 | LS response on Network Assistance for Network Synchronization in LTE (To: 3GPP TSG RAN, 3GPP RAN3, CC: 3GPP RAN1) | 3GPP RAN4, Huawei | imported from 3GU |
| R3‑163061 | LS on Handling of UE E-UTRAN capabilities when UE is camping on NB-IoT (To: 3GPP RAN2, 3GPP RAN3 ) | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑163062 | LS on migration from LTE/EPC including Option 3 to NextGen System (To: 3GPP RAN2, 3GPP RAN3, 3GPP TSG RAN, CC: 3GPP TSG SA, 3GPP TSG CT) | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑163063 | LS on NextGen QoS interim agreements (To: 3GPP RAN2, 3GPP RAN3, CC: 3GPP RAN1) | 3GPP SA2, Intel | imported from 3GU |
| R3‑163064 | LS on ""Next Generation"" Security Requirements (To: 3GPP SA2, 3GPP SA3 , CC: 3GPP TSG SA, 3GPP TSG CT, 3GPP TSG RAN, 3GPP RAN3) | 3GPP SA3-LI, BT Group | imported from 3GU |
| R3‑163065 | Reply LS on RAN-Assisted Codec Adaptation (To: 3GPP RAN2, Cc: 3GPP RAN3, 3GPP SA2, 3GPP TSG RAN) | 3GPP SA4, Intel | imported from 3GU |
| R3‑163066 | RAN location Tracking in RRC Inactive | MediaTek Inc. | imported from 3GU |
| R3‑163067 | Feasibility of lossless mobility for the CP solution | MediaTek Inc. | imported from 3GU |
| R3‑163068 | CB: # 1_Report_V2X: Chairman's notes for the session on LTE-based V2X Services | Ericsson | imported from 3GU |
| R3‑163069 | CB: # 2_Report_Mce: Chairman's notes for the session on Multi-Carrier Enhancements for UMTS | Vice Chairman | imported from 3GU |
| R3‑163070 | CB: # 3_Report_DTXDRX: Chairman's notes for the session on DTX/DRX enhancements in CELL_FACH | Vice Chairman | imported from 3GU |
| R3‑163071 | CB: # 4_Report_FNBID: Chairman's notes for the session on Flexible eNB-ID and Cell-ID in E-UTRAN | Vice Chairman | imported from 3GU |
| R3‑163072 | CB: # 5_Report_iPos: Chairman's notes for the session on Further Indoor Positioning enhancements for UTRA and LTE | Vice Chairman | imported from 3GU |
| R3‑163073 | CB: # 6_Report_JOP: Chairman's notes for the session on Study on HSPA and LTE Joint Operation SI | Vice Chairman | imported from 3GU |
| R3‑163074 | Response to R3-162741 | Ericsson | imported from 3GU |
| R3‑163075 | Response to R3-162761 - R3-162764 | Ericsson | imported from 3GU |
| R3‑163076 | Response to R3-162941 | Ericsson | imported from 3GU |
| R3‑163077 | Response to R3-162922 and R3-162923 | Ericsson | imported from 3GU |
| R3‑163078 | Draft RAN3-93 Bis meeting report | MCC | imported from 3GU |
| R3‑163079 | Reply LS to S2-164927 on QoS requirements for V2X (S1-163425; to: SA2, RAN2, CT1; cc: RAN1, RAN3; contact: Qualcomm) | SA1, Qualcomm | imported from 3GU |
| R3‑163080 | Reply LSto R3-162642 on Light Connected UE (S3-162087; to: RAN3; cc: RAN2; contact: Intel) | SA3, Intel | imported from 3GU |
| R3‑163081 | Reply LS to R2-167296 on Security aspects of RRC Connection Re-Establishment for NB-IoT (DoNAS) (S3-162088; to: RAN2; cc: RAN3,CT1; contact: Intel) | SA3, Intel | imported from 3GU |
| R3‑163082 | Reply LS to R2-167293 on S-TMSI in RAN paging (S3-162123; to: RAN2; cc: RAN3, CT1; contact: Ericsson) | RAN2, Ericsson | imported from 3GU |
| R3‑163083 | RAN3-93 Bis meeting report | MCC | imported from 3GU |
| R3‑163084 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom, Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, ZTE, CMCC | imported from 3GU |
| R3‑163085 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T, Samsung, LG Electronics Inc., Qualcomm Incorporated | imported from 3GU |
| R3‑163086 | Support of Redirection for VoLTE | Huawei | imported from 3GU |
| R3‑163087 | [Draft] LS on support of redirection for VoLTE | Huawei | imported from 3GU |
| R3‑163088 | PLMN ID Check and Enhanced TV Services | Ericsson | imported from 3GU |
| R3‑163089 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom, Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, ZTE, CMCC | imported from 3GU |
| R3‑163090 | Impacts on RAN3 by Down-selected ME Solutions | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑163091 | Draft ME Stage2 | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑163092 | Draft ME Stage3 | ZTE, China Telecom, China Unicom | imported from 3GU |
| R3‑163093 | RAN functional split considerations and preferences | Verizon | imported from 3GU |
| R3‑163094 | Draft reply to R2-163094 = R3-163094 on mobility enhancements for eNB-IoT (to: RAN2; cc: CT1, SA2; contact: Huawei) | Huawei | imported from 3GU |
| R3‑163095 | Reply LS to S2-166285 = R3-163061 on Handling of UE E-UTRAN capabilities when UE is camping on NB-IoT (to: SA2, RAN2; cc: -; contact: Quaclomm) | Qualcomm | imported from 3GU |
| R3‑163096 | Way forward on NB-IOT enhancements | Huawei | imported from 3GU |
| R3‑163097 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163098 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163099 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163100 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑163101 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑163102 | Way forward on fexible eNB ID | Huawei | imported from 3GU |
| R3‑163103 | [DRAFT[ LS on SA2 dependent issues for RAN3 study on New Radio (to: SA2; cc: RAN2; contact: NTT DOCOMO) | NTT DOCOMO | imported from 3GU |
| R3‑163104 | DRAFT LS on Network slicing and QoS for New Radio (to: SA2, RAN2; cc: -; contact: Ericsson) | Ericsson | imported from 3GU |
| R3‑163105 | [DRAFT LS on RAN2 dependent issues for RAN3 study on New Radio (to: RAN2, SA2; cc: -; contact: Qualcomm) | Qualcomm | imported from 3GU |
| R3‑163106 | Mobility scenarios cleaning up | Samsung | imported from 3GU |
| R3‑163107 | Corrections to TR 38.801 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163108 | Correction for Multi-connectivity Function | Samsung | imported from 3GU |
| R3‑163109 | Scenarios for inter-RAT mobility | Ericsson | imported from 3GU |
| R3‑163110 | New RAN architecture | Ericsson | imported from 3GU |
| R3‑163111 | Management and Configuration of SCTP/IP over NG2 interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163112 | Discussion on NG procedures | Ericsson | imported from 3GU |
| R3‑163113 | NG-U Protocol Oblivious Encapsulation Design | Huawei | imported from 3GU |
| R3‑163114 | Key characteristics of NG-U protocol stack options | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163115 | UP protocol stack over NG | Samsung | imported from 3GU |
| R3‑163116 | pCR related to the Support of legacy UEs in the 5G System frameworkt paper | Ericsson | imported from 3GU |
| R3‑163117 | Additional functions of the Xn interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163118 | Text Proposal for RAN internal interface Xn | LG Electronics Inc. | imported from 3GU |
| R3‑163119 | UP protocol stack over Xn | Samsung | imported from 3GU |
| R3‑163120 | TP on tight interworking between new RAT and LTE | LG Electronics Inc. | imported from 3GU |
| R3‑163121 | Tight interworking procedures for Option 3/3a | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163122 | Reply to: LS on The progress and questions for the light connection (to: RAN2; cc: CT1, SA2; contact: Huawei) | Huawei, Intel | imported from 3GU |
| R3‑163123 | Introduction of Light Connected State | Nokia, Alcatel-Lucent Shanghai Bell, Huawei, China Telecom, China Unicom | imported from 3GU |
| R3‑163124 | Introduction of light connection in X2AP | Huawei, Nokia, China Telecom, China Unicom | imported from 3GU |
| R3‑163125 | Introduction of light connection in S1AP | Huawei, Nokia, China Telecom,China Unicom | imported from 3GU |
| R3‑163126 | LS on RAN1 progress on MC enhancements (R1-1613208; to: RAN2, RAN3; cc: -; contact: Huawei) | RAN1 | imported from 3GU |
| R3‑163127 | Reply LS to R2-167313 on RAN2 agreements for NR DL-based mobility and cell definition (R1-1613348; to: RAN2; cc: RAN3, RAN4; contact: Samsung) | RAN1 | imported from 3GU |
| R3‑163128 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑163129 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑163130 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑163131 | Reply LS to R2-167315 on mobility enhancements for eNB-IoT (C1-165313; to: RAN2, RAN3; cc: SA2; contact: Huawei) | CT1 | imported from 3GU |
| R3‑163132 | Introduction of band 48 | RAN4 (Nokia) | imported from 3GU |
| R3‑163133 | Introduction of band 48 | RAN4 (Nokia) | imported from 3GU |
| R3‑163134 | Way forward on control plane signalling procedure | Ericsson | imported from 3GU |
| R3‑163135 | Way forward on light connnection | Huawei | imported from 3GU |
| R3‑163136 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163137 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell, Intel, Ruckus, Qualcomm | imported from 3GU |
| R3‑163138 | Ignoring the UE WLAN MAC Address at Handover | Ericsson | imported from 3GU |
| R3‑163139 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Intel | imported from 3GU |
| R3‑163140 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163141 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163142 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163143 | Enabling uplink data bearers | Nokia Networks | imported from 3GU |
| R3‑163144 | Reply LS to C1-165313 = R3-163131 on mobility enhancements for eNB-IoT (to: CT1; cc: RAN2, SA2; contact: Huawei) | Huawei | imported from 3GU |
| R3‑163145 | Reply LS to S2-166285 = R3-163061 on Handling of UE E-UTRAN capabilities when UE is camping on NB-IoT (to: SA2, RAN2; cc: -; contact: Quaclomm) | Qualcomm | imported from 3GU |
| R3‑163146 | Supporting LWIP with XwAP - New Procedure Descriptions | Nokia, Ericsson LM | imported from 3GU |
| R3‑163147 | LWIP Addition and Modification | Ericsson LM | imported from 3GU |
| R3‑163148 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163149 | Enabling LWIP support over Xw | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163150 | Review of solution Enabling LWIP support over Xw | Intel Corporation, Qualcomm Incorporated, Mediatek Inc., China Telecom, Brocade | imported from 3GU |
| R3‑163151 | eLWIP: Xs stage-2 proposal for TS 36.300 | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163152 | eLWIP: Xs user plane protocol | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163153 | eLWIP: Xs data transport | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163154 | eLWIP: Xs Application Protocol | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑163155 | Review of solution new Xs interface for eLWIP | Nokia | imported from 3GU |
| R3‑163156 | Way forward on WI LTE_WLAN_eLWIP-Core | Nokia | imported from 3GU |
| R3‑163157 | Reply LS to S2-166285 = R3-163061 on Handling of UE E-UTRAN capabilities when UE is camping on NB-IoT (to: SA2, RAN2; cc: -; contact: Qualcomm) | RAN3 | imported from 3GU |
| R3‑163158 | Draft reply to R2-163094 = R3-163094 on mobility enhancements for eNB-IoT (to: RAN2; cc: CT1, SA2; contact: Huawei) | Huawei | imported from 3GU |
| R3‑163159 | LS on SA2 dependent issues for RAN3 study on New Radio (to: SA2; cc: RAN2; contact: NTT DOCOMO) | RAN3 | imported from 3GU |
| R3‑163160 | DRAFT LS on Network slicing and QoS for New Radio (to: SA2, RAN2; cc: -; contact: Ericsson) | Ericsson | imported from 3GU |
| R3‑163161 | LS on RAN2 dependent issues for RAN3 study on New Radio (to: RAN2, SA2; cc: -; contact: Qualcomm) | RAN3 | imported from 3GU |
| R3‑163162 | Support SeNB change for "Maintain source eNB connection solution" | Samsung | imported from 3GU |
| R3‑163163 | CU-DU spit option selection and interface specification | NTT DOCOMO, INC., Fujitsu, CMCC, KT, SK Telecom, Deutsche Telekom, Orange, Telecom Italia, Verizon, KPN | imported from 3GU |
| R3‑163164 | Draft Reply R2-167312 = R3-163055 on RAN2 agreements for mobility enhancement (to: RAN2, cc: RAN1, RAN4; contact: ZTE) | ZTE | imported from 3GU |
| R3‑163165 | Reply to R2-163094 = R3-163094 on mobility enhancements for eNB-IoT (to: RAN2; cc: CT1, SA2; contact: Huawei) | RAN3 | imported from 3GU |
| R3‑163166 | LS on Network slicing and QoS for New Radio (to: SA2, RAN2; cc: -; contact: Ericsson) | RAN3 | imported from 3GU |
| R3‑163167 | LS on Network slicing and QoS for New Radio (to: SA2, RAN2; cc: -; contact: Ericsson) | RAN3 | imported from 3GU |
| R3‑163168 | Inter gNBs Mobility without CN type change | NEC | imported from 3GU |
| R3‑163169 | Solutions for intra New-RAN Handover | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163170 | Interworking between EPC and NGC | Intel Corporation | imported from 3GU |
| R3‑163171 | Text Proposal for Session Modification Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163172 | Procedure of initial access | Huawei | imported from 3GU |
| R3‑163173 | Further considerations on traffic aggregation | Huawei | imported from 3GU |
| R3‑163174 | TP for RRC signaling between CU and DU | LG Electronics Inc. | imported from 3GU |
| R3‑163175 | TP on possible realisation of Option 2 | Ericsson | imported from 3GU |
| R3‑163176 | Additional Benefit Considerations for Option 3-1 | AT&T | imported from 3GU |
| R3‑163177 | TP for further consideration on Option 3-1 | LG Electronics Inc. | imported from 3GU |
| R3‑163178 | Update of TR 38.801 (v0.7.0) on Study on New Radio Access Technology: Radio Access Architecture and Interfaces | NTT DOCOMO INC. | imported from 3GU |
| R3‑163179 | TP on Analysis of Option 3 | Ericsson | imported from 3GU |
| R3‑163180 | CU-DU split: Summary table | NTT DOCOMO INC. | imported from 3GU |
| R3‑163181 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑163182 | Introduction of new period values for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑163183 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑163184 | Support of small and variable MBMS areas for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑163185 | Authorization for Pedestrian UE over X2 | LG Electronics Inc., Huawei, CATT, ZTE | imported from 3GU |
| R3‑163186 | Way forward on V2X | LG Electronics | imported from 3GU |
| R3‑163187 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑163188 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑163189 | Solution for cooperation area allocation taking into account X2 link characteristics | Nokia, Alcatel-Lucent Shanghai Bell, Fujitsu | imported from 3GU |
| R3‑163190 | Introduction of Transmission Points for OTDOA in Shared Cell-ID Scenario and PRS based Terrestrial Beacon Systems | Qualcomm Incorporated | imported from 3GU |
| R3‑163191 | Cell Portion ID Extension | Ericsson | imported from 3GU |
| R3‑163192 | LS on Cell Portion ID Extension (to: CT4; cc: RAN1, RAN4; contact: Ericsson) | RAN3 | imported from 3GU |
| R3‑163193 | TP for the evaluation on the DASH optimization solution | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑163194 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell, Qualcomm, Huawei, NTT Docomo Inc | imported from 3GU |
| R3‑163195 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell, Qualcomm, Huawei, NTT Docomo Inc | imported from 3GU |
| R3‑163196 | Introduction of DRX enhancements | Huawei, Ericsson | imported from 3GU |
| R3‑163197 | Introduction of DRX enhancements | HuaWei Technologies Co., Ltd | imported from 3GU |
| R3‑163198 | TP for service information acquisition and UE assisted local cache | CMCC, Qualcomm Incorporated | imported from 3GU |
| R3‑163199 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.4.0 | China Unicom | imported from 3GU |
| R3‑163200 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163201 | Conclusion of the SI for Network Synchronization | Huawei | imported from 3GU |
| R3‑163202 | TR 36.898 v2.2.0 on Network Assistance for Network Synchronization | Huawei | imported from 3GU |
| R3‑163203 | LS on The progress for the light connection (R2-168955; to: RAN3, CT1; cc: -; contact: Huawei) | RAN2 | imported from 3GU |
| R3‑163204 | TP for the evaluation on the DASH optimization solution | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑163205 | Solution proposal for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑163206 | Correction of eDRX Information | Nokia | imported from 3GU |
| R3‑163207 | Correction of eDRX Information | Nokia | imported from 3GU |
| R3‑163208 | LS on eDRX Configuration and restoration (to: CT4; cc: -; contact: Nokia) | Nokia | imported from 3GU |
| R3‑163209 | TP to address solutions for issue 4 | Intel Corporation (UK) Ltd | imported from 3GU |
| R3‑163210 | Editorial update v1.2.0 of Draft TR 36.933 on Study on Context Aware Service Delivery in RAN for LTE | CMCC | imported from 3GU |
| R3‑163211 | Change in X2 TNL performances use-case and solution | Fujitsu | imported from 3GU |
| R3‑163212 | Solution for cooperation area allocation taking into account X2 link characteristics | Nokia, Alcatel-Lucent Shanghai Bell, Fujitsu | imported from 3GU |
| R3‑163213 | CU-DU spit option selection and interface specification | NTT DOCOMO, INC., AT&T, CMCC, KT, SK Telecom, Deutsche Telekom, Telecom Italia, Verizon, KPN, Fujitsu, NEC, Nokia, CATT | imported from 3GU |
| R3‑163214 | CU-DU spit option selection and interface specification | NTT DOCOMO | imported from 3GU |
| R3‑163215 | pCR related to the QoS and PDU Session Management paper | Ericsson | imported from 3GU |
| R3‑163216 | Way forward on FS_NR_newRAT | NTT DOCOMO | imported from 3GU |
| R3‑163217 | Text Proposal to TR 38.801 on Dual Connectivity between LTE and NR via EPC | NTT DOCOMO INC. | imported from 3GU |
| R3‑163218 | Support of RLF with UE Context Retrieval for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑163219 | Support of RLF with UE Context Retrieval for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑163220 | Support of RLF with UE Context Retrieval for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑163221 | Key principles for Support of Network Slicing in RAN | Huawei | imported from 3GU |
| R3‑163222 | Slice Availability and impact on Mobility | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163223 | Enable simultaneous radio transmission and data forwarding for Make-Before-Break handover | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163224 | Enable simultaneous radio transmission and data forwarding for Make-Before-Break handover | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163225 | Way forward on eDRX | Nokia | imported from 3GU |
| R3‑163226 | Summary of Counting offline discussion | Qualcomm | imported from 3GU |
| R3‑163227 | WT Notifying neighbour eNB information on Xw | NEC | imported from 3GU |
| R3‑163228 | eNB Notifying neighbour WT information on X2 | NEC | imported from 3GU |
| R3‑163229 | Way forward: eNB overload handling for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑163230 | Reply LS to C1-165313 = R3-163131 on mobility enhancements for eNB-IoT (to: CT1; cc: RAN2, SA2; contact: Huawei) | Huawei | imported from 3GU |
| R3‑163231 | [LS on support of redirection for VoLTE (to: SA2; cc: RAN2; contact: Huawei) | Huawei | imported from 3GU |
| R3‑163232 | Support of small and variable MBMS areas for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑163233 | Introduction of localized MBMS deployment for V2X | LG Electronics Inc., CATT, Huawei | imported from 3GU |
| R3‑163234 | WT Notifying neighbour eNB information on Xw | NEC | imported from 3GU |
| R3‑163235 | Way forward on Enhancement for MME Overload Control | Huawei | imported from 3GU |
| R3‑163236 | LS on the progress of QoE Measurement Collection for Streaming (R2-168917; to RAN3, SA4, SA5, CT1; cc: -; contact: China Unicom) | RAN2 | imported from 3GU |
| R3‑163237 | Reply to R2-167314 on The progress and questions for the light connection (to: RAN2; cc: CT1, SA2; contact: Huawei) | RAN3 | imported from 3GU |
| R3‑163238 | Way forward on agreements and open issues for light connection | Huawei | imported from 3GU |
| R3‑163239 | Reply LS to R3-162637 on Flexible eNB-ID and Cell-ID in E-UTRAN (S5-166410; to: RAN3; cc: CT1, CT4, RAN2, RAN6, SA2; contact: Ericsson) | SA5 | imported from 3GU |
| R3‑163240 | Introduction of DRX enhancements | Huawei, Ericsson | imported from 3GU |
| R3‑163241 | Solution proposal for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑163242 | Change in X2 TNL performances use-case and solution | Fujitsu | imported from 3GU |
| R3‑163243 | Introduction of light connection in X2AP | Huawei, Nokia, China Telecom, China Unicom | imported from 3GU |
| R3‑163244 | Introduction of light connection in S1AP | Huawei, Nokia, China Telecom,China Unicom | imported from 3GU |
| R3‑163245 | Way forward on mobility enhancements for LTE | ZTE | imported from 3GU |
| R3‑163246 | LS on agreement on OTDOA enhancement in RAN1#87 (R1-1613755; to: RAN2, RAN3; cc: -; contact: Intel) | RAN1 | imported from 3GU |
| R3‑163247 | LS on support of redirection for VoLTE (to: SA2; cc: RAN2; contact: Huawei) | RAN3 | imported from 3GU |
| R3‑163248 | Management and Configuration of SCTP/IP over NG2 interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163249 | pCR related to the QoS and PDU Session Management paper | Ericsson | imported from 3GU |
| R3‑163250 | Solutions for intra New-RAN Handover | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163251 | Text Proposal for Session Modification Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑163252 | Procedure of initial access | Huawei | imported from 3GU |
| R3‑163253 | TP on possible realisation of Option 2 | Ericsson | imported from 3GU |
| R3‑163254 | LS on mobility enhancements for NB-IoT (R2-169115; to: RAN3, CT1; cc: SA2, SA3; contact: Huawei) | RAN2 | imported from 3GU |
| R3‑163255 | Draft Reply R2-167312 = R3-163055 on RAN2 agreements for mobility enhancement (to: RAN2, cc: RAN1, RAN4; contact: ZTE) | ZTE | imported from 3GU |
| R3‑163256 | Way forward on mobility enhancements for LTE | ZTE | imported from 3GU |
| R3‑163257 | TR 36.742 v0.3.0 on Study on SON for eCoMP | Nokia | imported from 3GU |
| R3‑163258 | Way forward on WI LTE_WLAN_eLWIP-Core | Nokia | imported from 3GU |
| R3‑163259 | Reply to R2-167314 = R3-163057 on The progress and questions for the light connection (to: RAN2; cc: CT1, SA2; contact: Huawei) | RAN3 | imported from 3GU |
| R3‑163260 | Reply R2-167312 = R3-163055 on RAN2 agreements for mobility enhancement (to: RAN2, cc: -; contact: ZTE) | RAN3 | imported from 3GU |
| R3‑163261 | TR 36.898 v2.3.0 on Network Assistance for Network Synchronization | Huawei | imported from 3GU |
page generated from database: 2024-04-13 13:51:47