3GPP TDocs (written contributions) at meeting
Meeting: R3-91b - 2016-04-11 to 2016-04-15, Bangalore
meeting id: R3-91b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑160572 | Agenda for RAN3#91bis, Bangalore | Chairman | imported from 3GU |
R3‑160573 | RAN3#91 Meeting Report, St Julian's, Malta | MCC | imported from 3GU |
R3‑160574 | TR 30.531, v 1.24.0 | MCC | imported from 3GU |
R3‑160575 | Existence of CIoT support and NAS protocol details for CIoT (To: RAN2, RAN3, SA2) | CT1, Huawei | imported from 3GU |
R3‑160576 | LS on extension to field length of PDCP Sequence Number (To: CT4; Cc: RAN2, RAN3) | CT4, Nokia | imported from 3GU |
R3‑160577 | LS on LTE Rel-13 UE feature list (To: RAN2; Cc: RAN3, RAN4) | RAN1, NTT DOCOMO | imported from 3GU |
R3‑160578 | LS on updates for TS 36.300 (To: RAN1, RAN3) | RAN2, Huawei | imported from 3GU |
R3‑160579 | LS on paging in NB-IoT (To: RAN3, SA2, CT1) | RAN2, Ericsson | imported from 3GU |
R3‑160580 | LS on Rel-13 MDT enhancements (To: SA5; Cc: RAN3) | RAN2, Nokia | imported from 3GU |
R3‑160581 | LS on Paging Narrowband for eMTC (To: RAN3) | RAN2, Qualcomm | imported from 3GU |
R3‑160582 | Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: SA2, RAN3) | RAN2, Nokia | imported from 3GU |
R3‑160583 | Response to LS on NB-IoT work progress in RAN2 (To: CT1; Cc: SA2, RAN3) | RAN2, NTT DOCOMO | imported from 3GU |
R3‑160584 | Reply LS to R3-160501 = RP-160031 on RAN decision for CSG and LIPA support in DC (Dual Connectivity) enhancements for LTE (To: SA, SA2; Cc: RAN3) | RAN, Samsung | imported from 3GU |
R3‑160585 | Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: RAN2, RAN3) | SA2, Qualcomm | imported from 3GU |
R3‑160586 | LS on paging in NB-IoT (To: RAN2, RAN3, CT1) | SA2, Ericsson | imported from 3GU |
R3‑160587 | Reply LS on NB-IoT work progress in RAN2 (To: RAN2, CT1; Cc: RAN3) | SA2, Qualcomm | imported from 3GU |
R3‑160588 | Reply LS on questions on NB-IoT (To: RAN2, RAN3, CT1, SA3; Cc: RAN1, CT4) | SA2, Vodafone | imported from 3GU |
R3‑160589 | Reply LS on CIOT optimization (To: RAN3, RAN2; Cc: CT1) | SA2, Samsung | imported from 3GU |
R3‑160590 | Reply LS on Existence of CIoT support and NAS protocol details for CIoT (To: CT1, RAN2, RAN3) | SA2, Huawei | imported from 3GU |
R3‑160591 | Response LS on CIoT optimization for non-NB-IoT UEs (To: RAN2, RAN3, CT1; Cc: SA3) | SA2, Nokia | imported from 3GU |
R3‑160592 | LS on RRC connection resume procedure (To: CT1; Cc: SA2, RAN3) | RAN2, Ericsson | imported from 3GU |
R3‑160593 | UE Context release in Control Plane CIoT EPS optimization | Huawei, Nokia, CATT, Qualcomm Incorporated, China Unicom, LGE | imported from 3GU |
R3‑160594 | Introduction of the UE context resume function | Ericsson | imported from 3GU |
R3‑160595 | Introduction of common impacts of NB-IoT solutions | Huawei | imported from 3GU |
R3‑160596 | Introduction of Connection Establishment Indication procedure | Huawei, Nokia | imported from 3GU |
R3‑160597 | Introduction of Connection Establishment Indication procedure | Huawei, Nokia | imported from 3GU |
R3‑160598 | Introduction of the UE context resume function | Ericsson, Nokia | imported from 3GU |
R3‑160599 | Introduction of the inter-eNB UE Context Resume function | Ericsson | imported from 3GU |
R3‑160600 | Further consideration on authorization for PC5 based V2V | LG Electronics Inc. | imported from 3GU |
R3‑160601 | [DRAFT] LS on authorization for PC5 based V2V (To: SA2) | LG Electronics Inc. | imported from 3GU |
R3‑160602 | Authorization for PC5 based V2V | LG Electronics Inc. | imported from 3GU |
R3‑160603 | Discussion on switching between PC5 and Uu based V2V | LG Electronics Inc. | imported from 3GU |
R3‑160604 | TP for TR 36.885 on V2X SI | LG Electronics Inc. | imported from 3GU |
R3‑160605 | Discussion on service area and MBMS function split for V2X | LG Electronics Inc. | imported from 3GU |
R3‑160606 | Issue on resource management for MBMS based V2X | LG Electronics Inc. | imported from 3GU |
R3‑160607 | Open issues for local breakout | LG Electronics Inc. | imported from 3GU |
R3‑160608 | Considerations on Resume ID | CATT | imported from 3GU |
R3‑160609 | Initiation of S1 Connection resume | CATT | imported from 3GU |
R3‑160610 | Inclusion of UE history IEs in Context Fetch message | CATT | imported from 3GU |
R3‑160611 | Provision of CEL to MME | CATT | imported from 3GU |
R3‑160612 | Discussion on RAT Type | CATT | imported from 3GU |
R3‑160613 | Discussion on ANR for LWA | CATT | imported from 3GU |
R3‑160614 | Discussion on mobility procedures for LWA | CATT | imported from 3GU |
R3‑160615 | Paging via anchor eNB | CATT | imported from 3GU |
R3‑160616 | TS 36.463 correction for WT Status Reporting | CATT | imported from 3GU |
R3‑160617 | TS 36.463 correction for WLAN Information | CATT | imported from 3GU |
R3‑160618 | TS 36.463 correction for WLAN Information | CATT | imported from 3GU |
R3‑160619 | TS 36.465 correction for LWA | CATT | imported from 3GU |
R3‑160620 | Interruption analysis on mobility events | ZTE Corporation | imported from 3GU |
R3‑160621 | Analysis on solutions for service interruption reduction in mobility events | ZTE Corporation | imported from 3GU |
R3‑160622 | Fronthaul and RAN functional split aspects of the next generation radio access network | Intel Corporation | imported from 3GU |
R3‑160623 | NFV aspects of the next generation radio access network | Intel Corporation | imported from 3GU |
R3‑160624 | Control-user plane split aspects of the next generation radio access network | Intel Corporation | imported from 3GU |
R3‑160625 | End-to-end latency aspects of the next generation network | Intel Corporation | imported from 3GU |
R3‑160626 | Mobility Enhancements for eLWA | Intel Corporation | imported from 3GU |
R3‑160627 | ANR aspects of eLWA | Intel Corporation | imported from 3GU |
R3‑160628 | Considerations for additional WLAN related metrics | Intel Corporation | imported from 3GU |
R3‑160629 | Control plane aspects of 60GHz support for LWA | Intel Corporation | imported from 3GU |
R3‑160630 | Discussion on the use cases and requirements for context awareness service delivery | Huawei | imported from 3GU |
R3‑160631 | Text proposal of use cases and requirements for context awareness service delivery | Huawei | imported from 3GU |
R3‑160632 | Discussion on local cache and local breakout | Huawei | imported from 3GU |
R3‑160633 | Text proposal of local cache and local breakout | Huawei | imported from 3GU |
R3‑160634 | Support of Redirection for VoLTE | Huawei | imported from 3GU |
R3‑160635 | Text Proposal for Support of Redirection for VoLTE | Huawei | imported from 3GU |
R3‑160636 | Maintaining Source eNB Connection during Handover | Huawei | imported from 3GU |
R3‑160637 | RAN3 impact analysis of further eMBMS enhancement | Huawei | imported from 3GU |
R3‑160638 | Correction on the DC function description | Huawei | imported from 3GU |
R3‑160639 | Correction on eNB UE X2AP ID extension | Huawei | imported from 3GU |
R3‑160640 | Correction on the paging optimization | Huawei | imported from 3GU |
R3‑160641 | Immediately Release after Initial UE message | Huawei | imported from 3GU |
R3‑160642 | UE Radio Capability Handling | Huawei | imported from 3GU |
R3‑160643 | CEL to assist the MME in NAS retransmission strategies | Huawei | imported from 3GU |
R3‑160644 | Open issues in User Plane solution | Huawei | imported from 3GU |
R3‑160645 | Common impacts of NB-IoT solutions | Huawei | imported from 3GU |
R3‑160646 | [DRAFT] LS on OAM Requirement of NB-IoT (To: SA5; Cc: RAN2, SA2) | Huawei | imported from 3GU |
R3‑160647 | Analysis of PC5-based V2V authorization | Huawei | imported from 3GU |
R3‑160648 | Selection between Uu and PC5 for V2V transport | Huawei | imported from 3GU |
R3‑160649 | Support of small and variable areas in V2X | Huawei | imported from 3GU |
R3‑160650 | Consideration on Localized MBMS in V2X | Huawei | imported from 3GU |
R3‑160651 | Consideration on Local Breakout in V2X | Huawei | imported from 3GU |
R3‑160652 | Multiple operators operating for Uu based V2V | Huawei | imported from 3GU |
R3‑160653 | Consideration on mHealth in V2X | Huawei | imported from 3GU |
R3‑160654 | Work plan for light connection | Huawei, Intel Corporation, China Telecom | imported from 3GU |
R3‑160655 | General consideration on light connection | Huawei, China Telecom | imported from 3GU |
R3‑160656 | Consideration on RAN initiated Paging | Huawei, China Telecom | imported from 3GU |
R3‑160657 | Correction on WT Initiated WT Modification procedure | Huawei | imported from 3GU |
R3‑160658 | Correction on WT association confirmation | Huawei | imported from 3GU |
R3‑160659 | Addition of measurement configuration | Huawei | imported from 3GU |
R3‑160660 | Addition of measurement configuration | Huawei | imported from 3GU |
R3‑160661 | Correction on RESET procedure | Huawei | imported from 3GU |
R3‑160662 | Correction on Xw-U SN | Huawei | imported from 3GU |
R3‑160663 | Correction on flow control | Huawei | imported from 3GU |
R3‑160664 | Correction on WT Initiated WT Modification | Huawei | imported from 3GU |
R3‑160665 | Correction to the description of the Xw UP protocol services and Xw-U Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160666 | Scope of the ANR-related enhancements | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160667 | Scope of the mobility-related enhancements | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160668 | Extension to field length of PDCP Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160669 | [DRAFT] Reply LS on extension to field length of PDCP Sequence Number (To: CT4, RAN2) | Nokia | imported from 3GU |
R3‑160670 | Flexible Split of Next Generation RAN Architecture Functions | AT&T | imported from 3GU |
R3‑160671 | Next Generation RAN-Core Connectivity Considerations | AT&T | imported from 3GU |
R3‑160672 | Proposal for relaying capability | KDDI Corporation | imported from 3GU |
R3‑160673 | RAN-CN interface and functional split | Samsung | imported from 3GU |
R3‑160674 | Inter-RAT with LTE | Samsung | imported from 3GU |
R3‑160675 | Overview of solutions for the LTE mobility enhancements | Samsung | imported from 3GU |
R3‑160676 | Increased CSFB setup delay problem in case of context fetch | Samsung | imported from 3GU |
R3‑160677 | Introduction of solution to solve CSFB setup delay problem | Samsung | imported from 3GU |
R3‑160678 | Introduction of solution to solve CSFB setup delay problem | Samsung | imported from 3GU |
R3‑160679 | Function split between central and remote node | Samsung | imported from 3GU |
R3‑160680 | 5G RAN Network Functions Virtualization | Samsung | imported from 3GU |
R3‑160681 | Text proposal of MBMS for V2X | Samsung | imported from 3GU |
R3‑160682 | Radio capabilty transfer in case of CP CIOT optimization | Samsung | imported from 3GU |
R3‑160683 | CIOT indication for UP CIOT optimization | Samsung | imported from 3GU |
R3‑160684 | Introduction of the CIOT indication | Samsung | imported from 3GU |
R3‑160685 | Release or suspend the bearer fail to be resumed | Samsung | imported from 3GU |
R3‑160686 | UE check in case of context fetch | Samsung | imported from 3GU |
R3‑160687 | Mobility Enhancedment for LWA | Samsung | imported from 3GU |
R3‑160688 | The RAN side local caching | Samsung | imported from 3GU |
R3‑160689 | The impact of network slicing on RAN | Samsung | imported from 3GU |
R3‑160690 | Overview of Multi-Carrier enhancements | Huawei | imported from 3GU |
R3‑160691 | DTX/DRX enhancement in CELL_FACH | Huawei | imported from 3GU |
R3‑160692 | Working assumption for HSPA and LTE joint operation | Huawei | imported from 3GU |
R3‑160693 | Analysis on procedures of initiating voice call in LTE for joint operation | Huawei | imported from 3GU |
R3‑160694 | Analysis on procedures of initiating PS service in LTE for joint operation | Huawei | imported from 3GU |
R3‑160695 | [DRAFT] LS on working assumption for U&L joint operation (To: RAN2) | Huawei | imported from 3GU |
R3‑160696 | Missing DL DPCH slot formats for DCH enhancements in ASN.1 | Huawei, Qualcomm | imported from 3GU |
R3‑160697 | Correction on DL DPCH Slot Format configuration for DCH enhancements | Huawei, Qualcomm | imported from 3GU |
R3‑160698 | Correction on DL DPCH Slot Format configuration for DCH enhancements | Huawei, Qualcomm | imported from 3GU |
R3‑160699 | Correction on DL DPCH Slot Format configuration for DCH enhancements | Huawei, Qualcomm | imported from 3GU |
R3‑160700 | Correction on DL DPCH Slot Format configuration for DCH enhancements | Huawei, Qualcomm | imported from 3GU |
R3‑160701 | Correction on Procedure specification principles | Huawei | imported from 3GU |
R3‑160702 | Correction on WT Configuration update | Huawei | imported from 3GU |
R3‑160703 | Correction on Global eNB ID | Huawei | imported from 3GU |
R3‑160704 | Mobility optimizations for LWA | Huawei | imported from 3GU |
R3‑160705 | Discussion on ANR for LWA | Huawei | imported from 3GU |
R3‑160706 | Supporting of 60G new band and increased data rate in WLAN | Huawei | imported from 3GU |
R3‑160707 | Possible solutions for eNB ID extension in a PLMN | Huawei | imported from 3GU |
R3‑160708 | TP for Possible solutions for eNB ID extension in a PLMN | Huawei | imported from 3GU |
R3‑160709 | Possible solutions to extend maximum number of cells in an eNB | Huawei | imported from 3GU |
R3‑160710 | TP for Possible solutions to extend maximum number of cells in an eNB | Huawei | imported from 3GU |
R3‑160711 | Correction on Procedure code | Huawei | imported from 3GU |
R3‑160712 | Discussion on the security key update in LWA | Huawei | imported from 3GU |
R3‑160713 | Correction on security key update in LWA(Option1) | Huawei | imported from 3GU |
R3‑160714 | Correction on security key update in LWA(option1) | Huawei | imported from 3GU |
R3‑160715 | Correction on security key update in LWA (option2) | Huawei | imported from 3GU |
R3‑160716 | Correction on security key update in LWA (option2) | Huawei | imported from 3GU |
R3‑160717 | [DRAFT] LS on NB-IoT Progress in RAN3 (To: SA2, RAN2; Cc: SA3, CT1) | Huawei | imported from 3GU |
R3‑160718 | 5G TR usage and structure | Samsung | imported from 3GU |
R3‑160719 | Function Description for new RAN | Samsung | imported from 3GU |
R3‑160720 | Idle mode balancing for signaling only RRC connections | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160721 | [DRAFT] LS on UE behaviour when receiving not supported target frequencies in configuration (To: RAN2) | Nokia | imported from 3GU |
R3‑160722 | Correction of connection establish indication | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160723 | Handling of TAU Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160724 | Handling of RAT Type | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160725 | Correction of bearer type | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160726 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160727 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160728 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160729 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160730 | Indication of bearer type for cIOT WB EUTRAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160731 | Indication of bearer type over S1 for cIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160732 | Indication of bearer type for cIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160733 | Key princples for RAN-CN interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160734 | Key Requirements and Principles for Network Slicing | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160735 | Key princples for Slice Selection Support in RAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160736 | RAN QoS Framework | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160737 | Considerations for RAN architecture | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160738 | Deployment Scenarios for Interworking | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160739 | Dual connectivity between LTE and the New RAT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160740 | Interface consideration for tight LTE/NR interworking anchored to NextGen Core | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160741 | Proposal for Fronthaul Split Study | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160742 | Skeleton TR for study on Flexbile eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | imported from 3GU |
R3‑160743 | Work plan for Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | imported from 3GU |
R3‑160744 | Additional Requirements of Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | imported from 3GU |
R3‑160745 | TP of Additional Requirements for Flexible eNB-ID and Cell-ID in E-UTRAN | China Telecommunications | imported from 3GU |
R3‑160746 | Signalling optimization for VoLTE | Huawei | imported from 3GU |
R3‑160747 | Evaluation on codec adaptation mechanisms | Huawei | imported from 3GU |
R3‑160748 | Correction on Extention of X2 SN | Huawei | imported from 3GU |
R3‑160749 | Consideration on fronthauling | LG Electronics Inc. | imported from 3GU |
R3‑160750 | Discussion on V2V authorization | ZTE Corporation | imported from 3GU |
R3‑160751 | Correction on TP for TR 36.885 | ZTE Corporation | imported from 3GU |
R3‑160752 | Considerations on localization for Uu based V2X service | ZTE Corporation | imported from 3GU |
R3‑160753 | TR 36.898 v1.5.0 | Huawei | imported from 3GU |
R3‑160754 | Fronthauling: Motivations and Constraints | Mitsubishi Electric RCE | imported from 3GU |
R3‑160755 | Consideration on network slice selection | LG Electronics Inc. | imported from 3GU |
R3‑160756 | Consideration on the Interworking between LTE and New RAT | LG Electronics Inc. | imported from 3GU |
R3‑160757 | Further Discussion on Resume procedure for solution 18 | LG Electronics Inc. | imported from 3GU |
R3‑160758 | Triggering a Context Fetch when a TAU arrives from a different eNB | NEC | imported from 3GU |
R3‑160759 | Stage-2: Triggering a Context Fetch when a TAU arrives from a different eNB | NEC | imported from 3GU |
R3‑160760 | Stage-3: Triggering a Context Fetch when a TAU arrives from a different eNB | NEC | imported from 3GU |
R3‑160761 | [DRAFT] LS on Misalignment on TAU and UE Context deletion for Solution 18 (To: SA2, CT1, RAN2) | NEC | imported from 3GU |
R3‑160762 | Bearer Setup at the time of Context Resume | NEC | imported from 3GU |
R3‑160763 | General management of NR study | NEC | imported from 3GU |
R3‑160764 | Architecture and Migration | NEC | imported from 3GU |
R3‑160765 | Network Slicing in RAN | NEC | imported from 3GU |
R3‑160766 | Motivation of Functionality Splitting in RAN architecture | NEC | imported from 3GU |
R3‑160767 | Options of Functionality Splitting in RAN logical architecture | NEC, KDDI | imported from 3GU |
R3‑160768 | Discussion of use case and architecture for Context Aware service delivery | NEC | imported from 3GU |
R3‑160769 | Considerations on Context Aware Service Delivery | CATT | imported from 3GU |
R3‑160770 | Further analysis of solution 1 | Huawei | imported from 3GU |
R3‑160771 | Considerations on SeNB change in DC | CATT | imported from 3GU |
R3‑160772 | Discussion on the open issue for V2V | CATT | imported from 3GU |
R3‑160773 | Consideration on Localized V2X system | CATT | imported from 3GU |
R3‑160774 | Correction on Old/New eNB UE X2AP ID | CATT | imported from 3GU |
R3‑160775 | Consideration on RAN architecture in 5G NR | CATT | imported from 3GU |
R3‑160776 | TP for evaluation of solution 1 | Huawei | imported from 3GU |
R3‑160777 | Interworking between LTE and New RAT | CATT | imported from 3GU |
R3‑160778 | Wireless relay in 5G NR | CATT | imported from 3GU |
R3‑160779 | Conclusion of network synchronization study | Huawei | imported from 3GU |
R3‑160780 | Analysis on enabling network slicing in RAN | CATT | imported from 3GU |
R3‑160781 | Email summary of TP for solution 1 | Huawei | imported from 3GU |
R3‑160782 | Discussion on RAN-CN Functional Split in 5G NR | CATT | imported from 3GU |
R3‑160783 | Discussion on operational aspects of MBMS with MBSFN and SC-PTM | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160784 | Localized MBMS for V2X | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160785 | Discussion on the impact to RAN3 regarding the “eMBMS enhancements for LTE” | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160786 | Multiple Operator support in V2X | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160787 | Principles for Context Aware Service Delivery SI | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160788 | Further Consideration on Radio Aggregation Between NextGen RAN and eNB | ZTE Corporation | imported from 3GU |
R3‑160789 | Correction of RSRP Measurement Report List – Alt1 | ITRI, CATT | imported from 3GU |
R3‑160790 | Correction of RSRP Measurement Report List – Alt2 | ITRI, CATT | imported from 3GU |
R3‑160791 | Interworking Scenarios Between NextGen NW and LTE | ZTE Corporation | imported from 3GU |
R3‑160792 | Suspend and resume within the same eNB | ZTE Corporation | imported from 3GU |
R3‑160793 | Context Fetch and Resume procedure with different eNBs | ZTE Corporation | imported from 3GU |
R3‑160794 | Update on CIOT User Plane Solution | ZTE Corporation | imported from 3GU |
R3‑160795 | Update on CIOT User Plane Solution | ZTE Corporation | imported from 3GU |
R3‑160796 | Update on inter-eNB UE Context Resume function | ZTE Corporation | imported from 3GU |
R3‑160797 | Discussion on the framework for context aware service delivery | ZTE Corporation | imported from 3GU |
R3‑160798 | Next Generation Network Architecture with Access Independent Core | ZTE Corporation | imported from 3GU |
R3‑160799 | Initial mobility consideration for the NextGen | ZTE Corporation | imported from 3GU |
R3‑160800 | Clarification on the deployment of CU and DU | ZTE Corporation | imported from 3GU |
R3‑160801 | Discussion and TP for evaluation of solution 1 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160802 | Resolving FFSs in evaluation of solution 2 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160803 | TP for conclusion of network assisted synchronization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160804 | The function split between CU and DU | ZTE Corporation | imported from 3GU |
R3‑160805 | The capacity requirement for the interface between CU and DU | ZTE Corporation | imported from 3GU |
R3‑160806 | Considerations on standalone and non-standalone operation of new RAT | CMCC | imported from 3GU |
R3‑160807 | Considerations on interworking between LTE and new RAT | CMCC | imported from 3GU |
R3‑160808 | Discussion on Next generation fronthaul interface | CMCC | imported from 3GU |
R3‑160809 | Considerations on Next Generation RAN Architecture | CMCC | imported from 3GU |
R3‑160810 | Consideration on enhancing VoLTE technologies | CMCC | imported from 3GU |
R3‑160811 | Discussion on Automatic Neighbour Relation for eLWA | CMCC | imported from 3GU |
R3‑160812 | Draft TR 36933 skeleton for Study on Context Aware Service Delivery in RAN for LTE | CMCC | imported from 3GU |
R3‑160813 | Use cases and requirements for local cache and local breakout in RAN | CMCC | imported from 3GU |
R3‑160814 | Considerations on use cases for RAN optimizations | CMCC | imported from 3GU |
R3‑160815 | Discussion on ANR for eLWA | CATT | imported from 3GU |
R3‑160816 | Initial consideration in U&L joint operation SI | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160817 | Overall Thoughts on NFs of NextGen RAN | ZTE Corporation | imported from 3GU |
R3‑160818 | Discussion on the QoS control in the NextGen RAN | ZTE Corporation | imported from 3GU |
R3‑160819 | Clarification of CP and UP Separation from 38.913 | ZTE Corporation | imported from 3GU |
R3‑160820 | Clarification of Mobility Interruption Time Requirement from 38.913 | ZTE Corporation | imported from 3GU |
R3‑160821 | Consideration on RAN Side Network Slicing | ZTE Corporation | imported from 3GU |
R3‑160822 | Correction to the range of the Xw-U Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160823 | Multi-RAT RAN and CN | Qualcomm Incorporated | imported from 3GU |
R3‑160824 | Architecture of Distributed RAN | Qualcomm Incorporated | imported from 3GU |
R3‑160825 | Intra-RAN Coordination | Qualcomm Incorporated | imported from 3GU |
R3‑160826 | Aggregation scenarios for the new RAT | Qualcomm Incorporated | imported from 3GU |
R3‑160827 | Use Cases of Context Aware Service Delivery | Qualcomm Incorporated, CMCC | imported from 3GU |
R3‑160828 | Benefits of Edge Caching | Qualcomm Incorporated | imported from 3GU |
R3‑160829 | Overall radio protocol and NW architecture for NR | NTT DOCOMO, INC. | imported from 3GU |
R3‑160830 | Correction of Idle Mode Load Balancing for signalling only RRC connections | Nokia, Alcatel-Lucent Shanghai Bell , TeliaSonera, Huawei | imported from 3GU |
R3‑160831 | General considerations on the new RAT | Huawei | imported from 3GU |
R3‑160832 | Network Enablers for New Vehicular Services | Huawei | imported from 3GU |
R3‑160833 | Network slicing considerations | Huawei | imported from 3GU |
R3‑160834 | Scenarios for LTE-NR tight interworking | Huawei | imported from 3GU |
R3‑160835 | Fronthauling with New Radio Technology | Interdigital Asia LLC | imported from 3GU |
R3‑160836 | Requirements for Support of Self Organizing Network Techniques | QUALCOMM Incorporated | imported from 3GU |
R3‑160837 | On concurrent UMTS CS and LTE PS operation | QUALCOMM Incorporated | imported from 3GU |
R3‑160838 | Skeleton TR for New Radio Access Technology: Radio Access Architecture and Interfaces | NTT DOCOMO INC. | imported from 3GU |
R3‑160839 | Removing signaling of NRI from MSC/SGSN to RNC for CS/PS coordination | Ericsson | imported from 3GU |
R3‑160840 | [DRAFT] LS on CS/PS coordination in GERAN Shared Networks (To: SA2, Cc: GERAN2) | Ericsson | imported from 3GU |
R3‑160841 | Correction to WT-Initiated WT Modification | Ericsson, Qualcomm Incorporated, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160842 | 5G architecture scenarios | Ericsson | imported from 3GU |
R3‑160843 | RAN internal architecture | Ericsson | imported from 3GU |
R3‑160844 | Next Generation RAT Functionalities | Ericsson | imported from 3GU |
R3‑160845 | Handling of inactive Ues | Ericsson | imported from 3GU |
R3‑160846 | CN / RAN aspects of NR integration | Ericsson | imported from 3GU |
R3‑160847 | RAN support for network slicing | Ericsson | imported from 3GU |
R3‑160848 | Initial considerations on NR System access | Ericsson | imported from 3GU |
R3‑160849 | Tight integration of the New Radio interface (NR) and LTE: User Plane design | Ericsson | imported from 3GU |
R3‑160850 | V2V Sidelink Authorization | Ericsson | imported from 3GU |
R3‑160851 | Sidelink Authorization Signaling over S1 | Ericsson | imported from 3GU |
R3‑160852 | Sidelink Authorization Signaling over X2AP | Ericsson | imported from 3GU |
R3‑160853 | V2x Message Broadcast | Ericsson | imported from 3GU |
R3‑160854 | Delivery of V2x Messages via MBMS - Text Proposal | Ericsson | imported from 3GU |
R3‑160855 | Localized MBMS Deployment | Ericsson | imported from 3GU |
R3‑160856 | Study on Multi-Carrier Enhancements for UMTS | Ericsson | imported from 3GU |
R3‑160857 | Work plan for eMBMS enhancements in LTE | Ericsson | imported from 3GU |
R3‑160858 | DTX/DRX enhancements in CELL_FACH | Ericsson | imported from 3GU |
R3‑160859 | Handovers without WT Change | Ericsson | imported from 3GU |
R3‑160860 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
R3‑160861 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
R3‑160862 | Study on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
R3‑160863 | Evaluation criteria for the study on HSPA and LTE Joint Operation | Ericsson | imported from 3GU |
R3‑160864 | Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
R3‑160865 | UE Capabilities Exchange for DoNAS | Ericsson | imported from 3GU |
R3‑160866 | Addressing the UE Context at Context Retrieval | Ericsson, Vodafone | imported from 3GU |
R3‑160867 | Security Related Information exchanged at UE Context Retrieval | Ericsson | imported from 3GU |
R3‑160868 | [DRAFT] Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: SA2, RAN2) | Ericsson | imported from 3GU |
R3‑160869 | Parameterisation of the Retrieve UE Context Response message | Ericsson | imported from 3GU |
R3‑160870 | Resumption of S1 with an S1AP NAS Transport procedure | Ericsson | imported from 3GU |
R3‑160871 | Unsuccessful operation of the S1 UE Context Resume procedure | Ericsson | imported from 3GU |
R3‑160872 | Indicating the Coverage Level in Initial UE Message | Ericsson | imported from 3GU |
R3‑160873 | Inter-RAT mobility and indication of RAT on S1-MME | Ericsson | imported from 3GU |
R3‑160874 | Accuracy Evaluation for Solution 4 | Ericsson | imported from 3GU |
R3‑160875 | Evaluation of Solution 1 | Ericsson | imported from 3GU |
R3‑160876 | Evaluation of Solution 2 | Ericsson | imported from 3GU |
R3‑160877 | Introduction of the UE context resume function | Ericsson, Alcatel-Lucent, Nokia Networks | imported from 3GU |
R3‑160878 | Skeleton TR for Study on HSPA and LTE Joint Operation | China Unicom | imported from 3GU |
R3‑160879 | Motivation of HSPA and LTE Joint Operation | China Unicom | imported from 3GU |
R3‑160880 | Consideration on the UMTS and LTE joint operation | China Unicom | imported from 3GU |
R3‑160881 | Work plan for HSPA and LTE Joint Operation SI | China Unicom | imported from 3GU |
R3‑160882 | Considerations on Context Aware system in LTE RAN | China Unicom | imported from 3GU |
R3‑160883 | Discussion on Context Aware Service Delivery solution in LTE networks | China Unicom | imported from 3GU |
R3‑160884 | Network Enablers for New Vehicular Services | Huawei | imported from 3GU |
R3‑160885 | Consideration of inter eNB HO without WT change | Kyocera Corporation | imported from 3GU |
R3‑160886 | Consideration for TAU with U-plane solution | Kyocera Corporation | imported from 3GU |
R3‑160887 | Consideration on the use cases for mobility enhancement | LG Electronics Inc. | imported from 3GU |
R3‑160888 | LTE mobility without WT change | QUALCOMM CDMA Technologies | imported from 3GU |
R3‑160889 | Feedback Enhancements for LWA | QUALCOMM CDMA Technologies | imported from 3GU |
R3‑160890 | Introduction of the CIOT indication | Samsung | imported from 3GU |
R3‑160891 | Introduction of the CIOT indication | Samsung | imported from 3GU |
R3‑160892 | RAN based paging mechanism | Intel Corporation (UK) Ltd | imported from 3GU |
R3‑160893 | RAN-CN interface considerations | Huawei | imported from 3GU |
R3‑160894 | Consideration on RAN logical Architecture | Huawei | imported from 3GU |
R3‑160895 | Correction on Xw-U SN | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
R3‑160896 | Response to R3-160605 | ZTE Corporation | imported from 3GU |
R3‑160897 | Response to R3-160873 (and also response to R3-160724, and R3-160612) “Inter-RAT mobility and indication of RAT on S1-MME” | VODAFONE Group Plc | imported from 3GU |
R3‑160898 | Response to R3-160872 “Indicating the Coverage Level in Initial UE Message” | VODAFONE Group Plc | imported from 3GU |
R3‑160899 | LS on updated LTE Rel-13 UE feature list (To: RAN2; Cc: RAN3, RAN4) | RAN1, NTT DOCOMO | imported from 3GU |
R3‑160900 | Interworking Scenarios Between NextGen NW and LTE | ZTE Corporation | imported from 3GU |
R3‑160901 | Overall Thoughts on NFs of NextGen RAN | ZTE Corporation | imported from 3GU |
R3‑160902 | Indication of RAT type | Nokia, Alcatel Lucent Shanghai Bell, Vodafone | imported from 3GU |
R3‑160903 | [DRAFT] LS on indication of RAT Type for cIOT | Nokia, Alcatel-Lucent Shanghai Bell, Vodafone | imported from 3GU |
R3‑160904 | Introduction of the UE context resume function | Ericsson, Nokia | imported from 3GU |
R3‑160905 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
R3‑160906 | [DRAFT] Reply LS on extension to field length of PDCP Sequence Number (To: CT4; Cc: RAN2) | Nokia | imported from 3GU |
R3‑160907 | Reply LS on extension to field length of PDCP Sequence Number (To: CT4; Cc: RAN2) | RAN3 | imported from 3GU |
R3‑160908 | TS 36.463 correction for WT Status Reporting | CATT | imported from 3GU |
R3‑160909 | TS 36.465 correction for LWA | CATT | imported from 3GU |
R3‑160910 | Correction on WT Initiated WT Modification procedure | Huawei | imported from 3GU |
R3‑160911 | Correction on RESET procedure | Huawei | imported from 3GU |
R3‑160912 | Correction on flow control | Huawei | imported from 3GU |
R3‑160913 | Correction on Global eNB ID | Huawei | imported from 3GU |
R3‑160914 | [DRAFT] LS on UE behaviour when receiving not supported target frequencies in configuration (To: RAN2) | Nokia | imported from 3GU |
R3‑160915 | Correction on Old/New eNB UE X2AP ID | CATT | imported from 3GU |
R3‑160916 | Correction of RSRP Measurement Report List | CATT | imported from 3GU |
R3‑160917 | Way Forward on eMBMS Enhancements in LTE | Ericsson | imported from 3GU |
R3‑160918 | Way forward on further mobility enhancements in LTE WI | ZTE | imported from 3GU |
R3‑160919 | Way Forward on Signalling reduction to enable light connection for LTE | Huawei | imported from 3GU |
R3‑160920 | Way Forward on ANR for LWA | Intel | imported from 3GU |
R3‑160921 | Way Forward on the Handover without WT Change procedure | Intel | imported from 3GU |
R3‑160922 | Way forward for “Support for V2V services based on LTE side link WI” in RAN3 | LG Electronics Inc. | imported from 3GU |
R3‑160923 | TP for TR 36.885 on V2X SI | LG Electronics Inc. | imported from 3GU |
R3‑160924 | Text proposal of MBMS for V2X | Samsung | imported from 3GU |
R3‑160925 | Delivery of V2x Messages via MBMS - Text Proposal | Ericsson | imported from 3GU |
R3‑160926 | Consideration on Localized MBMS in V2X | Huawei | imported from 3GU |
R3‑160927 | Issues for Localized MBMS based on implementation option – Text Proposal | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160928 | Localized MBMS Deployment – Text Proposal | Ericsson | imported from 3GU |
R3‑160929 | Response to LS on questions on CIoT (To: SA2, CT1; Cc: CT4, RAN1, SA3, RAN3) | RAN2, Vodafone | imported from 3GU |
R3‑160930 | [DRAFT] LS on NB-IoT Progress in RAN3 (To: SA2, RAN2, SA3, CT1) | Huawei | imported from 3GU |
R3‑160931 | [DRAFT] LS on increased CSFB setup delay (To: RAN2, CT1) | Samsung | imported from 3GU |
R3‑160932 | Correction of connection establish indication | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160933 | TR for eMBMS enhancements for LTE (To: RAN2; Cc: RAN3, RAN4) | RAN1, Ericsson | imported from 3GU |
R3‑160934 | Consideration on the Interworking between LTE and New RAT | LG Electronics Inc. | imported from 3GU |
R3‑160935 | [DRAFT] LS on UE Radio Capability handling in CP solution (To: RAN2; Cc: SA2) | Huawei | imported from 3GU |
R3‑160936 | Introduction of the UE context resume function | Ericsson | imported from 3GU |
R3‑160937 | Introduction of the UE context resume function | Ericsson, Nokia | imported from 3GU |
R3‑160938 | Unsuccessful operation of the S1 UE Context Resume procedure | Ericsson | imported from 3GU |
R3‑160939 | Security Related Information exchanged at UE Context Retrieval | Ericsson | imported from 3GU |
R3‑160940 | [DRAFT] Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: SA2, RAN2) | Ericsson | imported from 3GU |
R3‑160941 | Introduction of the inter-eNB UE Context Resume function | Ericsson | imported from 3GU |
R3‑160942 | Text Proposal for Neutral Indicator for coverage level | Nokia, Alcatel Lucent Shanghai Bell | imported from 3GU |
R3‑160943 | [DRAFT] Response LS on Reply LS on questions on NB-IOT (To: SA2; Cc: RAN1, RAN2, CT1, CT4) | Nokia | imported from 3GU |
R3‑160944 | Indication of RAT type | Nokia, Alcatel Lucent Shanghai Bell, Vodafone | imported from 3GU |
R3‑160945 | [DRAFT] LS on indication of RAT Type for cIOT (To: SA2) | Nokia | imported from 3GU |
R3‑160946 | Introduction of common impacts of NB-IoT solutions | Huawei | imported from 3GU |
R3‑160947 | TR 38.801, New Radio Access Technology: Radio Access Architecture and Interfaces, v0.1.0 | NTT DOCOMO INC. | imported from 3GU |
R3‑160948 | 5G architecture scenarios | Ericsson | imported from 3GU |
R3‑160949 | TP on Ultra-Reliable and Low Latency Communications | Intel Corporation | imported from 3GU |
R3‑160950 | TP for the NR RAN Function List | NEC | imported from 3GU |
R3‑160951 | Handling of inactive UEs | Ericsson | imported from 3GU |
R3‑160952 | Skeleton TR for study on Flexbile eNB-ID and Cell-ID in E-UTRAN | China Telecom, Huawei | imported from 3GU |
R3‑160953 | TP for Possible solutions for eNB ID extension in a PLMN | Huawei | imported from 3GU |
R3‑160954 | TP for Possible solutions to extend maximum number of cells in an eNB | Huawei | imported from 3GU |
R3‑160955 | TP for Evaluation Criteria in Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
R3‑160956 | Way forward for Flexible eNB ID and Cell ID in EUTRAN | Huawei, China Telecom | imported from 3GU |
R3‑160957 | Introduction Control Plane CIoT EPS optimization | Huawei | imported from 3GU |
R3‑160958 | Introduction Control Plane CIoT EPS optimization | Huawei | imported from 3GU |
R3‑160959 | LS on indication of support of "attach without PDN connectivity" in SIB for NB-IoT and WB-EUTRAN (To: RAN2; Cc: SA2, RAN3) | CT1, Intel | imported from 3GU |
R3‑160960 | CN/RAN Interface deployment scenarios | Ericsson | imported from 3GU |
R3‑160961 | TP for Key principles for Support of Network Slicing in RAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160962 | NR discussion status in RAN3#91bis and way forward | NEC | imported from 3GU |
R3‑160963 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160964 | Session Report for Flexible eNB ID and Cell ID in EUTRAN | Vice Chairman | imported from 3GU |
R3‑160965 | TP for evaluation of solution 1 | Huawei | imported from 3GU |
R3‑160966 | TP update for HSPA and LTE Joint Operation SI | China Unicom | imported from 3GU |
R3‑160967 | Reply LS on Existence of CIoT support and NAS protocol details for CIoT (To: CT1, RAN3; Cc: SA2) | RAN2, Huawei | imported from 3GU |
R3‑160968 | Text Proposal for Support of Redirection for VoLTE | Huawei | imported from 3GU |
R3‑160969 | TR 36.933, v0.0.2, Study on Context Aware Service Delivery in RAN for LTE | CMCC | imported from 3GU |
R3‑160970 | Correction to the description of the Xw UP protocol services and Xw-U Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160971 | Correction to the range of the Xw-U Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160972 | Principles for Context Aware Service Delivery SI | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160973 | Indication of bearer type over S1 for cIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160974 | Indication of bearer type for cIOT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160975 | Text proposal of use cases and requirements for context awareness service delivery | Huawei | imported from 3GU |
R3‑160976 | TP for the backhaul long distance issue description | NEC | imported from 3GU |
R3‑160977 | Correction on WT Configuration update | Huawei | imported from 3GU |
R3‑160978 | [DRAFT] LS on WT triggered S-KWT update (To: SA3; Cc: RAN2) | Huawei | imported from 3GU |
R3‑160979 | TP for evaluation of solution 1 | Huawei | imported from 3GU |
R3‑160980 | Evaluation of Solution 2 | Ericsson | imported from 3GU |
R3‑160981 | TR 36.898, Network Assistance for Network Synchronization, v1.6.0 | Huawei | imported from 3GU |
R3‑160982 | TP for conclusion of network assisted synchronization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160983 | Session Report: Study on Multi-Carrier Enhancements for UMTS | Vice Chairman | imported from 3GU |
R3‑160984 | Session Report: DTX/DRX enhancements in CELL_FACH | Vice Chairman | imported from 3GU |
R3‑160985 | Session Report: Study on HSPA and LTE Joint Operation | Vice Chairman | imported from 3GU |
R3‑160986 | Fronthauling: Motivations and Constraints | Mitsubishi Electric RCE | imported from 3GU |
R3‑160987 | Introduction of the CIOT indication | Samsung | imported from 3GU |
R3‑160988 | Discussion summary of SA2 progress on UP CIOT | Samsung | imported from 3GU |
R3‑160989 | Flexible Split of Next Generation RAN Architecture Functions | AT&T | imported from 3GU |
R3‑160990 | Function split between central and remote node | Samsung | imported from 3GU |
R3‑160991 | Correction on the DC function description | Huawei | imported from 3GU |
R3‑160992 | Correction on eNB UE X2AP ID extension | Huawei | imported from 3GU |
R3‑160993 | Correction on eNB UE X2AP ID extension (Tabular modification) | Huawei, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160994 | Correction on Extention of X2 SN | Huawei | imported from 3GU |
R3‑160995 | Correction to the description of the Xw UP protocol services and Xw-U Sequence Number | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑160996 | Correction on WT Initiated WT Modification procedure | Huawei | imported from 3GU |
R3‑160997 | Correction on flow control | Huawei | imported from 3GU |
R3‑160998 | [DRAFT] LS on error scenarios during CSFB (To: RAN2, CT1) | Samsung | imported from 3GU |
R3‑160999 | Correction on WT Configuration update | Huawei | imported from 3GU |
R3‑161000 | Correction on Global eNB ID | Huawei | imported from 3GU |
R3‑161001 | Considerations on use cases for RAN optimizations | CMCC | imported from 3GU |
R3‑161002 | [DRAFT] LS on WT triggered S-KWT update (To: SA3; Cc: RAN2) | Huawei | imported from 3GU |
R3‑161003 | LS on UE behaviour when receiving not supported target frequencies in configuration (To: RAN2) | RAN3 | imported from 3GU |
R3‑161004 | Correction of Reroute NAS Request | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑161005 | 5G architecture scenarios | Ericsson | imported from 3GU |
R3‑161006 | TP on Ultra-Reliable and Low Latency Communications | Intel Corporation | imported from 3GU |
R3‑161007 | TP for the NR RAN Function List | NEC | imported from 3GU |
R3‑161008 | TP for the NR RAN Function List | NEC | imported from 3GU |
R3‑161009 | Handling of inactive UEs | Ericsson | imported from 3GU |
R3‑161010 | CN/RAN Interface deployment scenarios | Ericsson | imported from 3GU |
R3‑161011 | TP for Key principles for Support of Network Slicing in RAN | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑161012 | Fronthauling: Motivations and Constraints | Mitsubishi Electric RCE | imported from 3GU |
R3‑161013 | Function split between central and remote node | Samsung | imported from 3GU |
R3‑161014 | [DRAFT] Response LS on Reply LS on questions on NB-IOT (To: SA2, CT1; Cc: RAN1, RAN2, CT4) | Nokia | imported from 3GU |
R3‑161015 | [DRAFT] Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: SA2, RAN2) | Ericsson | imported from 3GU |
R3‑161016 | Reply LS on Clarifications on RRC Resume Request (To: SA3; Cc: SA2, RAN2) | RAN3 | imported from 3GU |
R3‑161017 | [DRAFT] Response LS on Reply LS on questions on NB-IOT (To: SA2, CT1, RAN2; Cc: RAN1, CT4) | Nokia | imported from 3GU |
R3‑161018 | [DRAFT] LS on indication of RAT Type for cIOT (To: SA2) | Nokia | imported from 3GU |
R3‑161019 | LS on indication of RAT Type for cIOT (To: SA2) | RAN3 | imported from 3GU |
R3‑161020 | Introduction of common impacts of NB-IoT solutions | Huawei | imported from 3GU |
R3‑161021 | Localized MBMS Deployment – Text Proposal | Ericsson | imported from 3GU |
R3‑161022 | Way Forward on Signalling reduction to enable light connection for LTE | Huawei | imported from 3GU |
R3‑161023 | TR 37.805, Study on HSPA and LTE Joint Operation, v0.1.0 | China Unicom | imported from 3GU |
R3‑161024 | TP for update of Solution 2 | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
R3‑161025 | TP for evaluation of solution 1 | Huawei | imported from 3GU |
R3‑161026 | TP for the backhaul long distance issue description | NEC | imported from 3GU |
R3‑161027 | TR 36.933, v0.1.0, Study on Context Aware Service Delivery in RAN for LTE | CMCC | imported from 3GU |
R3‑161028 | LS on error scenarios during CSFB (To: RAN2, CT1) | RAN3 | imported from 3GU |
R3‑161029 | LS on WT triggered S-KWT update (To: SA3; Cc: RAN2) | RAN3 | imported from 3GU |
R3‑161030 | NR discussion status in RAN3#91bis and way forward | NEC | imported from 3GU |
R3‑161031 | [DRAFT] Response LS on Reply LS on questions on NB-IOT (To: SA2, CT1, RAN2; Cc: RAN1, CT4) | Nokia | imported from 3GU |
R3‑161032 | Response LS on Reply LS on questions on NB-IOT (To: SA2, CT1, RAN2; Cc: RAN1, CT4) | RAN3 | imported from 3GU |
R3‑161033 | [DRAFT] LS on NB-IoT Progress in RAN3 (To: SA2, RAN2, SA3, CT1) | Huawei | imported from 3GU |
R3‑161034 | LS on NB-IoT Progress in RAN3 (To: SA2, RAN2, SA3, CT1) | RAN3 | imported from 3GU |
page generated from database: 2024-09-26 11:02:35