3GPP TDocs (written contributions) at meeting
Meeting: R3-93 - 2016-08-22 to 2016-08-26, Gothenburg
meeting id: R3-93 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑161545 | Agenda for RAN3#93, Gothenburg, Sweden | Chairman | imported from 3GU |
| R3‑161546 | RAN3#92 Meeting Report, Nanjing, China | MCC | imported from 3GU |
| R3‑161547 | TR 30.531, v1.25.0 | MCC | imported from 3GU |
| R3‑161548 | LS response on lower layer failure (To: RAN3; Cc: RAN2) | CT1, Samsung | imported from 3GU |
| R3‑161549 | LS on HS-SCCH DRx Design in Cell Fach (To: RAN2, RAN3) | RAN1, Qualcomm | imported from 3GU |
| R3‑161550 | LS on OTDOA for the same PCI (To: RAN2, RAN3; Cc: RAN4) | RAN1, Huawei | imported from 3GU |
| R3‑161551 | Reply LS on the feasibility of mobility enhancement solutions (To: RAN2; Cc: RAN3, RAN4) | RAN1, ZTE | imported from 3GU |
| R3‑161552 | LS on RAN2 aspects on MC enhancements (To: RAN1; Cc: RAN3) | RAN2, Huawei | imported from 3GU |
| R3‑161553 | LS on RAN initiated paging for the light connection (To: RAN3) | RAN2, Huawei & Intel | imported from 3GU |
| R3‑161554 | LS on RAN2 agreements on eDRX Paging Hyper-frame Calculation (To: RAN3, SA2; Cc: CT1, CT4, RAN) | RAN2, Samsung | imported from 3GU |
| R3‑161555 | Reply LS on NB-IOT NAS retransmission timers (To: SA2, CT1; Cc: RAN3, CT4) | RAN2, Vodafone | imported from 3GU |
| R3‑161556 | LS on eDRX paging timing calculation and security concern (To: SA3; Cc: RAN3, SA2, CT1) | RAN2, NTT DOCOMO | imported from 3GU |
| R3‑161557 | Reply LS on the feasibility of mobility enhancement solutions (To: RAN2; Cc: RAN1, RAN3) | RAN4, ZTE | imported from 3GU |
| R3‑161558 | LS on Network Assistance for Network Synchronization in LTE (To: RAN1, RAN4; Cc: RAN3) | RAN, Huawei | imported from 3GU |
| R3‑161559 | Reply LS on eDRX Paging Hyper-frame and PTW_Start Calculation (To: RAN2, RAN3, SA2; Cc: CT1, CT4) | RAN, NTT DOCOMO | imported from 3GU |
| R3‑161560 | LS on Enhanced coverage impacts on NAS timers in eMTC (To: RAN3, CT1; Cc: SA2) | RAN, Ericsson | imported from 3GU |
| R3‑161561 | LS Response on QoS requirements for V2X (To: RAN2, RAN3) | SA2, Huawei | imported from 3GU |
| R3‑161562 | Response LS on CSG and LIPA support in DC (Dual Connectivity) enhancements for LTE (To: RAN3; Cc: RAN, RAN2) | SA2, Nokia | imported from 3GU |
| R3‑161563 | LS out on RAN impacts from enTV study of SA WG2 (To: RAN2, RAN3) | SA2, Qualcomm | imported from 3GU |
| R3‑161564 | LS on Update of SRVCC Capability Real time during emergency PDC connection setup (To: RAN3) | SA2, Ericsson | imported from 3GU |
| R3‑161565 | Reply LS on SAND (To: RAN3) | SA4, Intel | imported from 3GU |
| R3‑161566 | Response LS on Progress on Security for LWIP (To: SA3, RAN; Cc: RAN2, RAN3) | SA, Nokia | imported from 3GU |
| R3‑161567 | Reply LS on Multiple bearer capability handling (To: SA2, RAN2; Cc: RAN3, CT) | CT1, Intel | imported from 3GU |
| R3‑161568 | LS on prioritization of NAS signalling (To: SA2, RAN2, RAN3) | CT1, Ericsson | imported from 3GU |
| R3‑161569 | Reply to LS on eDRX paging timing calculation and security concern (To: RAN2; Cc: RAN3, SA2, CT1) | SA3, NTT DOCOMO | imported from 3GU |
| R3‑161570 | LS on the study of the management of RAN virtualized network functions (To: RAN3; Cc: SA) | SA5, Intel | imported from 3GU |
| R3‑161571 | RAN functional split: intra PHY | Intel Corporation | imported from 3GU |
| R3‑161572 | RAN functional split: MAC-PHY | Intel Corporation | imported from 3GU |
| R3‑161573 | RAN functional split: intra MAC | Intel Corporation | imported from 3GU |
| R3‑161574 | C-plane and U-plane separation of NR RAN | Intel Corporation, KT Corp., Deutsche Telekom, AT&T, Samsung, Telecom Italia | imported from 3GU |
| R3‑161575 | Local Breakout for Ultra-Low Latency Communications | Intel Corporation | imported from 3GU |
| R3‑161576 | Fronthaul transport network aspects | Intel Corporation, KT Corp. | imported from 3GU |
| R3‑161577 | Realization of Network Functions | Intel Corporation | imported from 3GU |
| R3‑161578 | [DRAFT] Reply LS on the study of the management of RAN virtualized network functions | Intel Corporation | imported from 3GU |
| R3‑161579 | Handover without WT change procedure | Intel Corporation | imported from 3GU |
| R3‑161580 | Considerations for additional WLAN related metrics | Intel Corporation, Broadcom, Ruckus, Qualcomm Incorporated | imported from 3GU |
| R3‑161581 | Introduction of throughput indication | Intel Corporation, Broadcom, Ruckus, Qualcomm Incorporated | imported from 3GU |
| R3‑161582 | Benefits of Light connection over Suspend-Resume procedure | Intel Corporation | imported from 3GU |
| R3‑161583 | Benefits of RAN based paging (light connection) | Intel Corporation | imported from 3GU |
| R3‑161584 | NR Overall RAN Architecture | Intel Corporation | imported from 3GU |
| R3‑161585 | NR RAN function to support new RAN-controlled state | Intel Corporation | imported from 3GU |
| R3‑161586 | Correction to UE Context Resume Function | Intel Corporation | imported from 3GU |
| R3‑161587 | WLAN/NR interworking | Intel Corporation | imported from 3GU |
| R3‑161588 | Discussion on authorization for Pedestrian UEs | LG Electronics Inc. | imported from 3GU |
| R3‑161589 | Authorization of vehicular communication over S1 | LG Electronics Inc. | imported from 3GU |
| R3‑161590 | Authorization of vehicular communication over X2 | LG Electronics Inc. | imported from 3GU |
| R3‑161591 | Discussion on support of small and variable areas | LG Electronics Inc. | imported from 3GU |
| R3‑161592 | Miscellaneous Issues for Clarification in 38.801 | ZTE Corporation | imported from 3GU |
| R3‑161593 | Impacts on Radio Aggregation Scenarios due to CU-DU Separation | ZTE Corporation | imported from 3GU |
| R3‑161594 | Further Thoughts on CP and UP Separation Architecture | ZTE Corporation | imported from 3GU |
| R3‑161595 | Further Consideration on Various RAN3 Aspects of eLTE | ZTE Corporation | imported from 3GU |
| R3‑161596 | Clarification on Network Slicing in RAN | ZTE Corporation | imported from 3GU |
| R3‑161597 | Network Slice Selection Procedure | ZTE Corporation | imported from 3GU |
| R3‑161598 | Data forwarding issues for solution 2 | ZTE Corporation | imported from 3GU |
| R3‑161599 | Signaling procedures for Solution 2: Including both SeNB change/SC HO/DC HO | ZTE Corporation | imported from 3GU |
| R3‑161600 | MRO Issue for solution 2 | ZTE Corporation | imported from 3GU |
| R3‑161601 | New Radio internal architecture and Virtualized Small Cells (To: RAN3) | Small Cell Forum, Cisco | imported from 3GU |
| R3‑161602 | Misalignment between SA2 and RAN3 | Samsung | imported from 3GU |
| R3‑161603 | NR RAN functions | Samsung | imported from 3GU |
| R3‑161604 | RAN-CN interface deployment scenarios | Samsung | imported from 3GU |
| R3‑161605 | User Plane between NR and EPC | Samsung | imported from 3GU |
| R3‑161606 | Target/reference architectures | Samsung | imported from 3GU |
| R3‑161607 | Evolution path of target architectures | Samsung | imported from 3GU |
| R3‑161608 | NG1 interface considerations | Samsung | imported from 3GU |
| R3‑161609 | NG1 UP considerations | Samsung | imported from 3GU |
| R3‑161610 | Inter-RAT handover with LTE | Samsung | imported from 3GU |
| R3‑161611 | Increased CSFB setup delay problem in case of context fetch | Samsung | imported from 3GU |
| R3‑161612 | Introduction of solution to solve CSFB setup delay problem | Samsung | imported from 3GU |
| R3‑161613 | Introduction of solution to solve CSFB setup delay problem | Samsung | imported from 3GU |
| R3‑161614 | Solutions for the LTE mobility enhancements and analysis of their network side impact | Samsung | imported from 3GU |
| R3‑161615 | Discussion of PC5 and Uu interface switch for V2V | CATT | imported from 3GU |
| R3‑161616 | Discussion on QoS requirements for V2V/V2X | CATT | imported from 3GU |
| R3‑161617 | Introduction of UE PC5 AMBR over S1 | CATT | imported from 3GU |
| R3‑161618 | Introduction of UE PC5 AMBR over X2 | CATT | imported from 3GU |
| R3‑161619 | Further evaluation of solutions for V2X transmission | CATT | imported from 3GU |
| R3‑161620 | Discussion on Localized MBMS architecture | CATT | imported from 3GU |
| R3‑161621 | Discussion on LWA mobility | CATT | imported from 3GU |
| R3‑161622 | Discussion on RAN initiated paging | CATT | imported from 3GU |
| R3‑161623 | Correction to RETRIEVE UE CONTEXT RESPONSE | CATT | imported from 3GU |
| R3‑161624 | Discussion on CSG support in Dual Connectivity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161625 | Correction on CSG support in Dual Connectivity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161626 | Correction on CSG support in Dual Connectivity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161627 | General considerations for LTE-NR tight interworking | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161628 | Analysis of Higher-Layer functional split option | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161629 | SCG split bearer for NR | ZTE Corporation | imported from 3GU |
| R3‑161630 | DL transmission in small areas | Huawei | imported from 3GU |
| R3‑161631 | Authorization for Pedestrian UE | Huawei | imported from 3GU |
| R3‑161632 | Introduction of Pedestrian UE Authorization | Huawei | imported from 3GU |
| R3‑161633 | Introduction of Pedestrian UE Authorization | Huawei | imported from 3GU |
| R3‑161634 | Considerations on UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑161635 | Introduction of UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑161636 | Introduction of UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑161637 | Discussion on CE Mode B support Indicator | Huawei | imported from 3GU |
| R3‑161638 | Introduction of CE mode B support indicator | Huawei | imported from 3GU |
| R3‑161639 | NB-IoT Release 14 enhancements work plan | Huawei | imported from 3GU |
| R3‑161640 | Unsuccessful Retrieve UE Context procedure | Huawei | imported from 3GU |
| R3‑161641 | Correction on Retrieve UE Context Failure | Huawei | imported from 3GU |
| R3‑161642 | Correction on NB-IoT inter node RRC containers | Huawei | imported from 3GU |
| R3‑161643 | Correction on NB-IoT inter node RRC container | Huawei | imported from 3GU |
| R3‑161644 | Discussion on NB-IoT UE Identity Index Value in Paging | Huawei | imported from 3GU |
| R3‑161645 | Introduction of NB-IoT UE Identity Index Value in Paging | Huawei | imported from 3GU |
| R3‑161646 | Migration path towards NR with EPC | NTT DOCOMO, INC. | imported from 3GU |
| R3‑161647 | Consideration on the deployment of function split | Samsung | imported from 3GU |
| R3‑161648 | Consideration on the Fronthaul function split granularity | Samsung | imported from 3GU |
| R3‑161649 | Consideration on the tight interworking effect the split option | Samsung | imported from 3GU |
| R3‑161650 | QoS model for NR RAN | Samsung | imported from 3GU |
| R3‑161651 | Authorization for pedestrian Ues | Samsung | imported from 3GU |
| R3‑161652 | Legacy functionality impact result from RAN initiated paging | Samsung | imported from 3GU |
| R3‑161653 | The required features analysis for RAN initiated paging | Samsung | imported from 3GU |
| R3‑161654 | Handover without WT change | Samsung | imported from 3GU |
| R3‑161655 | Discussion on supporting small and variable areas in V2X | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161656 | Multiple Operator support in V2X | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161657 | Discussion on RAN3 impacts from enTV study in SA WG2 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161658 | Discussion on solutions for video optimization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161659 | Discussion on solutions for TCP optimization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161660 | Discussion on solutions to address backhaul long distance issue | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161661 | Geo broadcast | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161662 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161663 | Inter-eNB HO without WT change – solution details | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161664 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161665 | Network Slice Selection | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161666 | Resource Isolation for RAN Part of Network Slice | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161667 | QoS for slicing in RAN | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161668 | RAN-CN Interface Analysis | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161669 | RAN Internal Interfaces | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161670 | Connecting legacy LTE eNB to 5G Core | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161671 | Paging and location management in inactive mode | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161672 | Principles for QoS in the RAN | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161673 | Tight Interworking between LTE and NR | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161674 | Considerations on CU/DU functional split | Qualcomm Incorporated | imported from 3GU |
| R3‑161675 | Throughput prediction and network assisted DASH | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161676 | Video object deadline-aware scheduling | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161677 | Radio-aware TCP Optimization | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161678 | UE based context-aware and selective acceleration | QUALCOMM CDMA Technologies | imported from 3GU |
| R3‑161679 | Analysis of RAN impacts from enTV study of SA2 | Qualcomm Incorporated | imported from 3GU |
| R3‑161680 | Reply LS on RAN impacts from enTV study of SA WG2 | Qualcomm Incorporated | imported from 3GU |
| R3‑161681 | OTDOA Enhancements for the Shared Cell-ID Scenario | Qualcomm Incorporated | imported from 3GU |
| R3‑161682 | OTDOA Enhancements for the Shared Cell-ID Scenario | Qualcomm Incorporated | imported from 3GU |
| R3‑161683 | 5G access – a heterogeneous deployment scenario | IAESI, Thales, Fairspectrum, VTT | imported from 3GU |
| R3‑161684 | Distributed and centralized gNB-gNB mobility scenarios | IAESI, Thales, Fairspectrum, VTT | imported from 3GU |
| R3‑161685 | RAN-based solution for LTE tight interworking with NR | IAESI, Thales | imported from 3GU |
| R3‑161686 | Additional NR RAN specific functions | IAESI, Thales, Fairspectrum, VTT | imported from 3GU |
| R3‑161687 | TR 38.801, New Radio Access Technology: Radio Access Architecture and Interfaces, v0.3.0 | DOCOMO Communications Lab. | imported from 3GU |
| R3‑161688 | Discussion on RAN controlled UE state | CATT | imported from 3GU |
| R3‑161689 | On selection of RAN part of the network slice | CATT | imported from 3GU |
| R3‑161690 | QoS framework impact on RAN | CATT | imported from 3GU |
| R3‑161691 | TP on deployment scenarios for RAN-CN interface | CATT | imported from 3GU |
| R3‑161692 | Consideration on the evolution path of interface between LTE and NR | CATT | imported from 3GU |
| R3‑161693 | Considerations on intra-RAT mobility | CATT | imported from 3GU |
| R3‑161694 | Considerations on LTE and NR interworking | CATT | imported from 3GU |
| R3‑161695 | Consideration on RAN function split between CU and DU | CATT | imported from 3GU |
| R3‑161696 | Considerations on wireless relay scenarios | CATT | imported from 3GU |
| R3‑161697 | Solutions evaluation on maximum number of cells extension in an eNB | Huawei, China Telecom | imported from 3GU |
| R3‑161698 | TP for Solutions evaluation on maximum number of cells extension in an eNB | Huawei, China Telecom | imported from 3GU |
| R3‑161699 | Discussion on Mobility enhancements for eLWA | Huawei | imported from 3GU |
| R3‑161700 | UL data transfer between WT and eNB | Huawei | imported from 3GU |
| R3‑161701 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑161702 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑161703 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑161704 | NR Migration and forward compatibility | NEC | imported from 3GU |
| R3‑161705 | Intra NR Mobility (Inter gNBs Mobility) | NEC | imported from 3GU |
| R3‑161706 | NR Tight Interworking with LTE | NEC | imported from 3GU |
| R3‑161707 | Analysis and Evaluation of Function Split options - Criterions | NEC | imported from 3GU |
| R3‑161708 | How many splits in Function Split options and principles | NEC | imported from 3GU |
| R3‑161709 | Architecture and solution for Context Aware service delivery | NEC | imported from 3GU |
| R3‑161710 | Network Slicing: A Holistic Approach | NEC | imported from 3GU |
| R3‑161711 | On the Need for RAN-based Paging | NEC | imported from 3GU |
| R3‑161712 | Manual VS Automatic Neighbour Relation for LWA | NEC | imported from 3GU |
| R3‑161713 | eNB-ID and Cell-ID Extension: How to handle? | NEC | imported from 3GU |
| R3‑161714 | Consideration on the scenarios of RAN-CN interface (alignment with RP-161266) | LG Electronics Inc. | imported from 3GU |
| R3‑161715 | Consideration on the Migration Path | LG Electronics Inc. | imported from 3GU |
| R3‑161716 | Discussion on NB-IoT Cell Information | Huawei | imported from 3GU |
| R3‑161717 | Correction on NB-IoT Cell Information | Huawei | imported from 3GU |
| R3‑161718 | Principles of Light Connection | Huawei | imported from 3GU |
| R3‑161719 | Evaluation on RAN initiated paging and MME initiated paging | Huawei | imported from 3GU |
| R3‑161720 | RAN initiated paging | Huawei | imported from 3GU |
| R3‑161721 | Context fetch in light connection | Huawei | imported from 3GU |
| R3‑161722 | [Draft] Reply LS on RAN initiated paging for the light connection | Huawei | imported from 3GU |
| R3‑161723 | Introduction of Light Connection | Huawei | imported from 3GU |
| R3‑161724 | Introduction of Light Connection | Huawei | imported from 3GU |
| R3‑161725 | X2AP correction for eMTC | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161726 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161727 | Planning for “Study on SON for eCoMP for LTE” | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161728 | Scope of the “SON for eCoMP” study and structure of TR 36.742 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161729 | draft TR 36.742 skeleton | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161730 | Problem statement and related use-cases for SON for eCoMP | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161731 | Discussion on the same PCI case for OTDOA enhancements | Huawei | imported from 3GU |
| R3‑161732 | Introduction of the same PCI case for OTDOA enhancements | Huawei | imported from 3GU |
| R3‑161733 | Discussion on the same PCI case for E-CID enhancements | Huawei | imported from 3GU |
| R3‑161734 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161735 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161736 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161737 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161738 | UL bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161739 | Enabling uplink data bearers for LWA | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161740 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161741 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161742 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161743 | Clarification on deployment and interface scenarios | Huawei | imported from 3GU |
| R3‑161744 | Overview of 5G architecture options | Huawei | imported from 3GU |
| R3‑161745 | Refinement of NR RAN functions | Huawei | imported from 3GU |
| R3‑161746 | NG1 interface protocol structure | Huawei | imported from 3GU |
| R3‑161747 | Justification for PDCP-RLC splitting | Huawei | imported from 3GU |
| R3‑161748 | Scope of RAN internal function split | Huawei | imported from 3GU |
| R3‑161749 | Key principle for horizontal intra-RAT interfaces | Huawei | imported from 3GU |
| R3‑161750 | Migration path from LTE to NR | Huawei | imported from 3GU |
| R3‑161751 | Key principles for Support of Network Slicing in RAN | Huawei | imported from 3GU |
| R3‑161752 | RAN configuration for network slices | Huawei | imported from 3GU |
| R3‑161753 | Inter-RAT mobility with LTE | Huawei | imported from 3GU |
| R3‑161754 | LTE-NR tight interworking user plane options | Huawei | imported from 3GU |
| R3‑161755 | LTE-NR interface functions and procedures | Huawei | imported from 3GU |
| R3‑161756 | Consideration on NR PDCP design | Huawei | imported from 3GU |
| R3‑161757 | Functionality and procedure for LTE-NR tight interworking | Huawei | imported from 3GU |
| R3‑161758 | Location area management | HuaWei Technologies Co., Ltd | imported from 3GU |
| R3‑161759 | RAN Support for Core Network Slicing | Huawei | imported from 3GU |
| R3‑161760 | Discussion on RAN Functions Realization | Huawei | imported from 3GU |
| R3‑161761 | [DRAFT] Response LS on the study of the management of RAN virtualized network | Huawei | imported from 3GU |
| R3‑161762 | RAN Functional Split Considerations for NR | Interdigital Asia LLC | imported from 3GU |
| R3‑161763 | RAN Functional Split Option Grouping | Interdigital Asia LLC | imported from 3GU |
| R3‑161764 | Internal RAN Architecture Interface Naming | Interdigital Asia LLC | imported from 3GU |
| R3‑161765 | Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161766 | Correction to Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161767 | Extending maximum number of cells in eNB – Solution 1 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161768 | Extending maximum number of cells in eNB – Solution 3 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161769 | Deployment options for NR and eLTE | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161770 | Characteristics of eLTE eNB | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161771 | Migration scenario for NR | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161772 | AT&T Views on 5G Architecture Evolution | AT&T | imported from 3GU |
| R3‑161773 | Preferred NR Functional Splits and Considerations | AT&T | imported from 3GU |
| R3‑161774 | Clarification on the use cases for relay scenarios | KDDI Corporation | imported from 3GU |
| R3‑161775 | TR 36.896, Study on Flexbile eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | imported from 3GU |
| R3‑161776 | Discussion on 5G Deployment Scenarios | ZTE Corporation | imported from 3GU |
| R3‑161777 | NR RAN internal functional split and interface | KT Corp. | imported from 3GU |
| R3‑161778 | Support for Ultra-Reliable Low Latency Communication | ZTE Corporation | imported from 3GU |
| R3‑161779 | Consideration on QoS enforcement in NG RAN | ZTE Corporation | imported from 3GU |
| R3‑161780 | Discussion on global procedures of RAN-CN interface | ZTE Corporation | imported from 3GU |
| R3‑161781 | Consideration on “inactive state” in NR | ZTE Corporation | imported from 3GU |
| R3‑161782 | The interface between RAN nodes | ZTE Corporation | imported from 3GU |
| R3‑161783 | Discussion on global procedures of the interface between RAN nodes | ZTE Corporation | imported from 3GU |
| R3‑161784 | The evaluation for different split options | ZTE Corporation | imported from 3GU |
| R3‑161785 | The peak bitrate requirement for different split options | ZTE Corporation | imported from 3GU |
| R3‑161786 | Discussion on CU-DU functional split | ZTE Corporation | imported from 3GU |
| R3‑161787 | Architecture options for Context Aware Service Delivery | ZTE Corporation | imported from 3GU |
| R3‑161788 | S1 impact of NAS timer setting for eMTC | ZTE Corporation | imported from 3GU |
| R3‑161789 | Work plan on NR Study Item in RAN2 and RAN3 | NTT DOCOMO, INC. (Rapporteur) | imported from 3GU |
| R3‑161790 | Discussion on switching between Uu and PC5 | LG Electronics Inc. | imported from 3GU |
| R3‑161791 | Mobility and service continuity enhancements | Samsung | imported from 3GU |
| R3‑161792 | Correction on the reinitiating waiting time in Xw | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161793 | Discussion on the solution of video optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161794 | Text proposal for the solution of video optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161795 | Discussion on the solution of TCP optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161796 | Text proposal for the solution of TCP optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161797 | Discussion on the solution of the DASH optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161798 | Text proposal for the solution of the DASH optimization | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161799 | Draft reply LS to the SA4 on CASD | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161800 | Consideration on the Full Picture for Inter-RAT HO | LG Electronics Inc. | imported from 3GU |
| R3‑161801 | Evaluation on the remain issues of the possible solutions for eNB-ID Extension | China Telecommunications | imported from 3GU |
| R3‑161802 | Fronthaul split considerations | Mitsubishi Electric RCE | imported from 3GU |
| R3‑161803 | TP for Solutions evaluation on extend maximum number of eNBs in a PLMN | China Telecommunications | imported from 3GU |
| R3‑161804 | Solution description for concurrent UMTS CS and LTE PS | Qualcomm Incorporated | imported from 3GU |
| R3‑161805 | CP/UP separation for NR | Deutsche Telekom, AT&T, SK-Telecom, Intel, CMCC, Telecom Italia | imported from 3GU |
| R3‑161806 | Discussion on small and variable broadcast area in V2X | ZTE Corporation | imported from 3GU |
| R3‑161807 | UE-PC5-AMBR over S1 | ZTE Corporation | imported from 3GU |
| R3‑161808 | UE-PC5-AMBR over X2 | ZTE Corporation | imported from 3GU |
| R3‑161809 | Analysis of migration paths towards RAN for new RAT | CMCC | imported from 3GU |
| R3‑161810 | Discussion of function split between CU/DU | CMCC | imported from 3GU |
| R3‑161811 | Architectural aspect of split options 3/5/7 | CMCC | imported from 3GU |
| R3‑161812 | Text proposal for TP for split options architecture | CMCC | imported from 3GU |
| R3‑161813 | Transport requirement for CU&DU functional splits options | CMCC | imported from 3GU |
| R3‑161814 | Draft TR 36.933v_020 | CMCC | imported from 3GU |
| R3‑161815 | Issue and solution for UL resource shortage | CMCC | imported from 3GU |
| R3‑161816 | Text proposal for Issue for UL resource shortage | CMCC | imported from 3GU |
| R3‑161817 | Text proposal for solution for UL resource shortage | CMCC | imported from 3GU |
| R3‑161818 | Solution to backhaul long latency issue | CMCC | imported from 3GU |
| R3‑161819 | Discussion on Video Issue Solutions | CMCC | imported from 3GU |
| R3‑161820 | TP for Solution impact analysis in LTE&UMTS Joint Cooperation | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161821 | TP for Dual Standby in LTE&UMTS Joint Cooperation | Nokia, Alcatel-Lucent Shanghai Bell, China Unicom | imported from 3GU |
| R3‑161822 | Discussion on data forwarding for make before break solution | CATT | imported from 3GU |
| R3‑161823 | Correction on WT initiated WT modification procedure | Huawei | imported from 3GU |
| R3‑161824 | Selection of Split options between Central-Unit and Distributed-Unit | NTT DOCOMO, INC. | imported from 3GU |
| R3‑161825 | Discussion on SCG split bearer | NTT DOCOMO INC. | imported from 3GU |
| R3‑161826 | Correction of the LWA PDU type | Intel Corporation | imported from 3GU |
| R3‑161827 | Correction of the LWA PDU type | Intel Corporation | imported from 3GU |
| R3‑161828 | Correction of the LWA PDU type | Intel Corporation | imported from 3GU |
| R3‑161829 | Correction of the LWA PDU type | Intel Corporation | imported from 3GU |
| R3‑161830 | IMS paging type differentiation for PS domain | Intel Corporation | imported from 3GU |
| R3‑161831 | Paging cause introduction | Intel Corporation | imported from 3GU |
| R3‑161832 | Considerations on QoS aspects for NR | Intel Corporation | imported from 3GU |
| R3‑161833 | Discussion on a new video transmission issue in UL | Intel Corporation | imported from 3GU |
| R3‑161834 | Tight Interworking between LTE and New RAT | LG Electronics Inc. | imported from 3GU |
| R3‑161835 | Support of inter-PLMN for PC5 and Uu | LG Electronics Inc. | imported from 3GU |
| R3‑161836 | Conclusion of Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications,Huawei | imported from 3GU |
| R3‑161837 | Specification aspects for RAN functional split | LG Electronics Inc. | imported from 3GU |
| R3‑161838 | Discussion on NR interface functions | LG Electronics Inc. | imported from 3GU |
| R3‑161839 | UE centric operation and mobility for NR | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑161840 | Further study of Specifying RAN interface between central and distributed units for NR | NTT DOCOMO INC. | imported from 3GU |
| R3‑161841 | Case 1 analysis for joint operation | Huawei | imported from 3GU |
| R3‑161842 | TP for solution of case 1 | Huawei | imported from 3GU |
| R3‑161843 | Case 2 analysis for joint operation | Huawei | imported from 3GU |
| R3‑161844 | TP for solution of case 2 | Huawei | imported from 3GU |
| R3‑161845 | Case 3 analysis for joint operation | Huawei | imported from 3GU |
| R3‑161846 | TP for solution of case 3 | Huawei | imported from 3GU |
| R3‑161847 | Evaluation of solutions for joint operation | Huawei | imported from 3GU |
| R3‑161848 | Possible impacts of Multi-carrier enhancements | Huawei | imported from 3GU |
| R3‑161849 | DTX/DRX enhancements in CELL_FACH | Huawei | imported from 3GU |
| R3‑161850 | Presence Condition of Paging Time Window IE | NTT DOCOMO INC. | imported from 3GU |
| R3‑161851 | Vehicular Sidelink Authorization Signaling over S1 | Ericsson | imported from 3GU |
| R3‑161852 | Vehicular Sidelink Authorization Signaling over X2 | Ericsson | imported from 3GU |
| R3‑161853 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | imported from 3GU |
| R3‑161854 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑161855 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
| R3‑161856 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
| R3‑161857 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | imported from 3GU |
| R3‑161858 | NR function for Data Connectivity Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161859 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑161860 | NR function for In-band Path Switch | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161861 | Solution for Selection of Network Slice and CN entity | Nokia, Alcatel-Lucent Shanghai Bell, Samsung, ZTE, CATT | imported from 3GU |
| R3‑161862 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161863 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
| R3‑161864 | Content Aware QoS framework and NG1 impact | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161865 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161866 | Splitting Key Principles for RAN-CN interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161867 | Key Principles for NG1 Application Protocol | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161868 | Paging and Mobility in Inactive Mode | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161869 | Handling of SRVCC for Emergency Calls | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161870 | SRVCC capability for Emergency call | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161871 | SRVCC capability for Emergency call | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161872 | Reply LS on update of SRVCC capability real time during emergency PDN connection setup | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161873 | UE Radio Capability for signaling only RRC connections | Nokia, Alcatel-Lucent Shanghai Bell, TeliaSonera, Huawei | imported from 3GU |
| R3‑161874 | Correction of UE Radio Capability Information | Nokia, Alcatel-Lucent Shanghai Bell, TeliaSonera, Huawei | imported from 3GU |
| R3‑161875 | Status of NextGen study in SA2 | Nokia, CMCC | imported from 3GU |
| R3‑161876 | Solutions for signaling reduction in Light Connected mode | Nokia, Alcatel-Lucent Shanghai Bell, NTT DOCOMO INC. | imported from 3GU |
| R3‑161877 | Transfer of NBIOT capabilities | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161878 | Transfer of NBIOT capabilities | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161879 | Correction of NAS Timer Extension for NBIOT and eMTC | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161880 | Correction of NAS Timer Extension for NBIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161881 | Response to LS on Update of SRVCC Capability Real time during emergency PDC connection setup (To: SA2) | Ericsson | imported from 3GU |
| R3‑161882 | Update of SRVCC capability for emergency call | Ericsson | imported from 3GU |
| R3‑161883 | Correction to enable update of SRVCC capability for emergency call | Ericsson | imported from 3GU |
| R3‑161884 | Packet Length Correction | Ericsson | imported from 3GU |
| R3‑161885 | NAS Timer setting for eMTC | Ericsson | imported from 3GU |
| R3‑161886 | On the use of the term "NR RAN" in RAN (WG3) discussions | Ericsson | imported from 3GU |
| R3‑161887 | Functions for URLLC | Ericsson | imported from 3GU |
| R3‑161888 | Principles of Network Slicing for 5G | Ericsson | imported from 3GU |
| R3‑161889 | Network Slice Selection for 5G | Ericsson | imported from 3GU |
| R3‑161890 | Optimised RAN-CN interface design | Ericsson | imported from 3GU |
| R3‑161891 | RAN-CN interface procedures per connectivity scenario | Ericsson | imported from 3GU |
| R3‑161892 | Procedures analysis for the NG1 interface | Ericsson | imported from 3GU |
| R3‑161893 | Mobility between LTE and NR for inactive UEs | Ericsson | imported from 3GU |
| R3‑161894 | Consequences from discussions on RP-161266 at TSG#72 | Ericsson | imported from 3GU |
| R3‑161895 | New RAN Roll Out Scenarios | Ericsson | imported from 3GU |
| R3‑161896 | On RAN paging with CN assistance | Ericsson | imported from 3GU |
| R3‑161897 | Tight NR/LTE interworking and stand-alone NR access | Ericsson | imported from 3GU |
| R3‑161898 | RAN architecture scenarios requiring flexible design | Ericsson | imported from 3GU |
| R3‑161899 | Transport Network Topologies | Ericsson | imported from 3GU |
| R3‑161900 | RAN Architecture and Specification Aspects | Ericsson | imported from 3GU |
| R3‑161901 | Clarifications on fronthaul bitrate requirements | Ericsson | imported from 3GU |
| R3‑161902 | Automatic base station relations in NR | Ericsson | imported from 3GU |
| R3‑161903 | Authorization for Pedestrian Operation | Ericsson | imported from 3GU |
| R3‑161904 | Work Item: Multi-Carrier Enhancements for UMTS | Ericsson | imported from 3GU |
| R3‑161905 | Work Item: RRC Optimization for UTRAN | Ericsson | imported from 3GU |
| R3‑161906 | MBMS Distribution across Multiple PLMNs | Ericsson | imported from 3GU |
| R3‑161907 | DTX/DRX enhancements in CELL_FACH | Ericsson | imported from 3GU |
| R3‑161908 | OTDOA Positioning and the Same-PCI Issue | Ericsson | imported from 3GU |
| R3‑161909 | OTDOA Enhancements for Same-PCI Issue | Ericsson | imported from 3GU |
| R3‑161910 | WLAN Information for E-CID | Ericsson | imported from 3GU |
| R3‑161911 | LWA Enhanced Mobility Open Issues - Common | Ericsson | imported from 3GU |
| R3‑161912 | LWA Enhanced Mobility Open Issues - X2AP | Ericsson | imported from 3GU |
| R3‑161913 | Study on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
| R3‑161914 | Evaluation criteria for the study on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
| R3‑161915 | Text proposal on Study on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
| R3‑161916 | Use Cases on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
| R3‑161917 | Other aspects on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
| R3‑161918 | Solution of “Establish an interface instance per eNB” in Study Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑161919 | Solution of “Fixed extension of Cell bits” in Study on Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑161920 | Solution of “Supporting more Macro eNB IDs in an interface instance” in Study Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑161921 | Text proposal on Flexible Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑161922 | Discussion on additional requirement in Study Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑161923 | Analysis of Context Aware RAN Issues | Ericsson | imported from 3GU |
| R3‑161924 | [Draft] Reply LS on scope of SA4 SAND SI | Ericsson | imported from 3GU |
| R3‑161925 | WI work plan for Further Enhanced MTC | Ericsson | imported from 3GU |
| R3‑161926 | Correction of Transfer of NBIOT capabilities | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161927 | Correction of NAS Timer Extension for NBIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161928 | Consideration on CoMP set formation | Fujitsu | imported from 3GU |
| R3‑161929 | Consideration for network slice selection | LG Electronics Inc. | imported from 3GU |
| R3‑161930 | Discussion on paging for a lightly connected UE | LG Electronics Inc. | imported from 3GU |
| R3‑161931 | Discussion on functionality considering RRC-Inactive state | LG Electronics Inc. | imported from 3GU |
| R3‑161932 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.0.0 | China Unicom | imported from 3GU |
| R3‑161933 | Text proposal for evaluation criteria | China Unicom | imported from 3GU |
| R3‑161934 | Discussions on aspects of cross layer awareness | China Unicom | imported from 3GU |
| R3‑161935 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.0.1 | China Unicom | imported from 3GU |
| R3‑161936 | Text proposal for evaluation criteria | China Unicom | imported from 3GU |
| R3‑161937 | Correction on Security Related Information in UE Context Retrieval Request | Samsung | imported from 3GU |
| R3‑161938 | Correction on Security Related Information in UE Context Retrieval Request | Samsung | imported from 3GU |
| R3‑161939 | NR RRC inactive state principles | Qualcomm Incorporated | imported from 3GU |
| R3‑161940 | NR Mobility Procedure | Qualcomm Incorporated | imported from 3GU |
| R3‑161941 | Considerations for additional WLAN metrics | Intel Corporation, Broadcom, Ruckus, Qualcomm Incorporated | imported from 3GU |
| R3‑161942 | Reply LS on the feasibility of mobility enhancement solutions (To: RAN2; Cc: RAN4, RAN3) | RAN1, ZTE | imported from 3GU |
| R3‑161943 | Response to R3-161696 | Ericsson LM | imported from 3GU |
| R3‑161944 | Response to R3-161774 | Ericsson LM | imported from 3GU |
| R3‑161945 | Response to R3-161805 and R3-161574 | IAESI, Fairspectrum | imported from 3GU |
| R3‑161946 | Liaison letter to 3GPP RAN3 | IEEE 802.1, Ericsson | imported from 3GU |
| R3‑161947 | Response to contributions R3-161805 and R3-161574 | IAESI, Thales, Fairspectrum | imported from 3GU |
| R3‑161948 | Clarification on the use cases for relay scenarios | KDDI, Mitsubishi Electric | - |
| R3‑161949 | Discussion on data forwarding for make before break solution | CATT | - |
| R3‑161950 | Introduction of CE mode B support indicator | Huawei | - |
| R3‑161951 | Correction on NB-IoT inter node RRC containers | Huawei | - |
| R3‑161952 | Correction on NB-IoT inter node RRC container | Huawei | - |
| R3‑161953 | Correction to Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑161954 | Correction on Security Related Information in UE Context Retrieval Request | Samsung | - |
| R3‑161955 | Correction to UE Context Resume Function | Intel Corporation | - |
| R3‑161956 | Correction on WT initiated WT modification procedure | Huawei | - |
| R3‑161957 | [DRAFT] Reply LS on RAN impacts from enTV study of SA WG2 (To: SA2; Cc: RAN2) | Qualcomm Incorporated | - |
| R3‑161958 | Way Forward for LTE_eMob after RAN3#93 | ZTE | - |
| R3‑161959 | Way Forward on Light Connection | Huawei | - |
| R3‑161960 | Possible Agreements for Light Connection | Huawei | - |
| R3‑161961 | [DRAFT] Reply LS on the study of the management of RAN virtualized network functions (To: SA5; Cc: SA) | Intel Corporation | - |
| R3‑161962 | TR 38.801, New Radio Access Technology: Radio Access Architecture and Interfaces, v0.4.0 | NTT DOCOMO | - |
| R3‑161963 | [DRAFT] [LSout to SA2 on interface naming (To: SA2)] | Samsung | imported from 3GU |
| R3‑161964 | [TP based on Fig 2 of R3-161594] | ZTE | imported from 3GU |
| R3‑161965 | [DRAFT] [LS to RAN to clarify the requirements for CP/UP (To: RAN)] | ZTE | imported from 3GU |
| R3‑161966 | Deployment options for NR and eLTE | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑161967 | RAN-CN Interface Analysis | QUALCOMM CDMA Technologies | - |
| R3‑161968 | Vehicular Authorization Signaling over S1 | Ericsson, LGE Inc. | - |
| R3‑161969 | Vehicular Authorization Signaling over X2 | Ericsson, LGE Inc. | - |
| R3‑161970 | [DRAFT] LS on Multiple TMGIs for support of small and variable MBMS areas (To: RAN2) | LGE | - |
| R3‑161971 | Way forward for “LTE-based V2X Services WI” in RAN3 | LGE | - |
| R3‑161972 | On the use of the term "NR RAN" in RAN (WG3) discussions | Ericsson | - |
| R3‑161973 | 5G access – a heterogeneous deployment scenario | IAESI, Thales, Fairspectrum, VTT | - |
| R3‑161974 | TP on IRAT HO for 5G | Ericsson | - |
| R3‑161975 | Refinement of NR RAN functions | Huawei | - |
| R3‑161976 | TP on URLLC | Ericsson | - |
| R3‑161977 | Network Slicing: A Holistic Approach | NEC | - |
| R3‑161978 | Key principles for Support of Network Slicing in RAN | Huawei | - |
| R3‑161979 | TP for Network Slice election and CN entity selection | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑161980 | Resource Isolation for RAN Part of Network Slice | Qualcomm | - |
| R3‑161981 | Introduction of throughput indication | Intel Corporation, Broadcom, Ruckus, Qualcomm Incorporated, Blackberry, China Telecom, Xiaomi, NEC | - |
| R3‑161982 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑161983 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson | - |
| R3‑161984 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson | - |
| R3‑161985 | Extending maximum number of cells in eNB – Solution 1 | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑161986 | Text proposal on Flexible Cell-ID in E-UTRAN | Ericsson | - |
| R3‑161987 | OTDOA Enhancements for Same-PCI Issue | Ericsson | - |
| R3‑161988 | OTDOA Enhancements for Same-PCI Issue | Ericsson | - |
| R3‑161989 | TP for evaluation on Solution 3 of maximum number of cells extension in an eNB | Huawei | - |
| R3‑161990 | eNB-ID and Cell-ID Extension: How to handle? | NEC | - |
| R3‑161991 | TP for Solutions evaluation on extend maximum number of eNBs in a PLMN | China Telecommunications, Huawei, Ericsson | - |
| R3‑161992 | Conclusion of the Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications, Huawei, Ericsson, Nokia, NEC | - |
| R3‑161993 | TR 36.896, Study on Flexbile eNB-ID and Cell-ID in E-UTRAN, v 1.1.0 | China Telecommunications | - |
| R3‑161994 | Way forward for Flexible eNB ID and Cell ID in EUTRAN | China Telecommunications | - |
| R3‑161995 | WLAN/NR interworking | Intel Corporation | - |
| R3‑161996 | Session Report for Flexible eNB and Cell ID in EUTRAN | Vice Chairman | - |
| R3‑161997 | Considerations on wireless relay scenarios | CATT | - |
| R3‑161998 | Automatic base station relations in NR | Ericsson | - |
| R3‑161999 | AT&T Views on 5G Architecture Evolution | AT&T | - |
| R3‑162000 | Migration path towards NR with EPC | NTT DOCOMO, INC. | - |
| R3‑162001 | Analysis of migration paths towards RAN for new RAT | CMCC | - |
| R3‑162002 | RAN functional split: intra PHY | Intel Corporation | - |
| R3‑162003 | Consideration on RAN function split between CU and DU | CATT | - |
| R3‑162004 | Preferred NR Functional Splits and Considerations | AT&T | - |
| R3‑162005 | Transport requirement for CU&DU functional splits options | CMCC | - |
| R3‑162006 | Clarifications on fronthaul bitrate requirements | Ericsson | - |
| R3‑162007 | Consideration on the deployment of function split | Samsung | - |
| R3‑162008 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | - |
| R3‑162009 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | - |
| R3‑162010 | Discussion on NR interface functions | LG Electronics Inc. | - |
| R3‑162011 | TP for UP-CP separation | Ericsson | - |
| R3‑162012 | TP for Solution impact analysis in LTE&UMTS Joint Cooperation | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162013 | Evaluation criteria for the study on HSPA and LTE Joint Operation | Ericsson | - |
| R3‑162014 | WF on target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162015 | Study on HSPA and LTE Joint Operation | Ericsson | - |
| R3‑162016 | Use Cases on HSPA and LTE Joint Operation | Ericsson | - |
| R3‑162017 | Text proposal for conclusion section | China Unicom | - |
| R3‑162018 | RAN2#95 agreements Light Connection (To: RAN3) | RAN2, Huawei & Intel | - |
| R3‑162019 | LS on RAN1 agreements in sidelink-based V2V (To: RAN2, RAN3, RAN4) | RAN1, LGE | - |
| R3‑162020 | Reply LS on Network Assistance for Network Synchronization in LTE (To: RAN3, RAN; Cc: RAN4) | RAN1, Huawei | - |
| R3‑162021 | Discussion on a new video transmission issue in UL | Intel Corporation | - |
| R3‑162022 | Analysis of Context Aware RAN Issues | Ericsson | - |
| R3‑162023 | [DRAFT] Reply LS on scope of SA4 SAND SI (To: SA4) | Ericsson | - |
| R3‑162024 | Throughput prediction and network assisted DASH | QUALCOMM CDMA Technologies | - |
| R3‑162025 | Discussion on solutions for video optimization | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162026 | Text proposal for the solution of the DASH optimization | HUAWEI TECHNOLOGIES Co. Ltd. | - |
| R3‑162027 | Video object deadline-aware scheduling | QUALCOMM CDMA Technologies | - |
| R3‑162028 | Text proposal for the solution of video optimization | HUAWEI TECHNOLOGIES Co. Ltd. | - |
| R3‑162029 | draft TR 36.742 skeleton | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162030 | Problem statement and related use-cases for SON for eCoMP | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162031 | Realization of Network Functions | Intel Corporation | - |
| R3‑162032 | Mobility between LTE and NR for inactive UEs | Ericsson | - |
| R3‑162033 | Correction to enable update of SRVCC capability for emergency call | Ericsson, Nokia | - |
| R3‑162034 | NR function for Data Connectivity Request | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162035 | Key principle for horizontal intra-RAT interfaces | Huawei | - |
| R3‑162036 | Generic slice selection | Nokia | imported from 3GU |
| R3‑162037 | General considerations for LTE-NR tight interworking | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162038 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162039 | NR discussion status in RAN3#93 and way forward | NEC | - |
| R3‑162040 | Session Report: Multi-Carrier Enhancements for UMTS | Vice Chairman | - |
| R3‑162041 | Session Report: RRC Optimization for UMTS | Vice Chairman | - |
| R3‑162042 | Session Report: DTX/DRX enhancements in CELL_FACH | Vice Chairman | - |
| R3‑162043 | Session Report: Further Indoor Positioning enhancements for UTRA and LTE | Vice Chairman | - |
| R3‑162044 | Session Report: Study on HSPA and LTE Joint Operation | Vice Chairman | - |
| R3‑162045 | Correction on Security Related Information in UE Context Retrieval Request | Samsung | - |
| R3‑162046 | Correction to UE Context Resume Function | Intel Corporation | imported from 3GU |
| R3‑162047 | eNB-ID and Cell-ID Extension: How to handle? | NEC | - |
| R3‑162048 | TP on IRAT HO for 5G | Ericsson | - |
| R3‑162049 | TP on URLLC | Ericsson | - |
| R3‑162050 | Network Slicing: A Holistic Approach | NEC | imported from 3GU |
| R3‑162051 | Consideration on RAN function split between CU and DU | CATT | - |
| R3‑162052 | LS on eDRX Paging Hyper-frame and PTW_Start Calculation (To: SA2, RAN3, CT1; Cc: SA3, CT4) | RAN2, NTT DOCOMO | - |
| R3‑162053 | Network Slicing: A Holistic Approach | NEC | - |
| R3‑162054 | RAN-CN Interface Analysis | QUALCOMM CDMA Technologies | - |
| R3‑162055 | Handling of the UE context in the WT during HO | Nokia | - |
| R3‑162056 | Migration path towards NR with EPC | NTT DOCOMO, INC. | - |
| R3‑162057 | AT&T Views on 5G Architecture Evolution | AT&T | - |
| R3‑162058 | Analysis of migration paths towards RAN for new RAT | CMCC | - |
| R3‑162059 | Key principle for horizontal intra-RAT interfaces | Huawei | - |
| R3‑162060 | General considerations for LTE-NR tight interworking | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162061 | Possible Agreements for Light Connection | Huawei | - |
| R3‑162062 | RAN functional split: intra PHY | Intel Corporation | - |
| R3‑162063 | Text Proposal: Justification and Description with detail of Option 2 and 3 | AT&T | - |
| R3‑162064 | Inclusion of Solution 3c and corresponding Evaluation | NEC | - |
| R3‑162065 | Realization of Network Functions | Intel Corporation | - |
| R3‑162066 | [DRAFT] LS on Multiple TMGIs for support of small and variable MBMS areas (To: RAN2; Cc: SA2) | LGE | - |
| R3‑162067 | LS on Multiple TMGIs for support of small and variable MBMS areas (To: RAN2; Cc: SA2) | RAN3 | - |
| R3‑162068 | Reply LS on RAN impacts from enTV study of SA WG2 (To: SA2; Cc: RAN2) | RAN3 | - |
| R3‑162069 | [DRAFT] Reply LS on the study of the management of RAN virtualized network functions (To: SA5; Cc: SA) | Intel Corporation | - |
| R3‑162070 | TP for Solution impact analysis in LTE&UMTS Joint Cooperation | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162071 | Text proposal for conclusion section | China Unicom | - |
| R3‑162072 | Text proposal for evaluation section | China Unicom | - |
| R3‑162073 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.1.0 | China Unicom | - |
| R3‑162074 | Conclusion of the Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | - |
| R3‑162075 | Draft TR 36.933 v0.3.0 | CMCC | - |
| R3‑162076 | [DRAFT] Reply LS on scope of SA4 SAND SI (To: SA4) | Ericsson | - |
| R3‑162077 | TP on IRAT HO for 5G | Ericsson | - |
| R3‑162078 | Realization of Network Functions | Intel Corporation | - |
| R3‑162079 | TR 36.896, Study on Flexbile eNB-ID and Cell-ID in E-UTRAN, v 1.2.0 | China Telecommunications | - |
| R3‑162080 | Reply LS on scope of SA4 SAND SI (To: SA4) | RAN3 | - |
| R3‑162081 | LS on RAN2 agreements on UMTS and LTE joint operation (To: RAN3) | RAN2, China Unicom | - |
| R3‑162082 | TP on RAN2 agreements on UMTS and LTE Joint Operation | China Unicom | - |
| R3‑162083 | Introduction of NB-IoT UE Identity Index Value in Paging | Huawei | - |
| R3‑162084 | Correction on CSG support in Dual Connectivity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
page generated from database: 2024-04-13 13:51:47