3GPP TDocs (written contributions) at meeting
Meeting: R3-93b - 2016-10-10 to 2016-10-14, Sophia Antipolis
meeting id: R3-93b (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑162085 | RAN3#93-Bis meeting Agenda | MCC | imported from 3GU |
| R3‑162086 | RAN3#93 meeting report | MCC | imported from 3GU |
| R3‑162087 | Clarification that the Xw UE ID is unique within relevant node | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162088 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162089 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia | imported from 3GU |
| R3‑162090 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia | imported from 3GU |
| R3‑162091 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | imported from 3GU |
| R3‑162092 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑162093 | Further Discussion on Authorization for Pedestrian UEs | LG Electronics Inc. | imported from 3GU |
| R3‑162094 | Authorization for Pedestrian UE over S1 | LG Electronics Inc., Huawei, CATT, ZTE | imported from 3GU |
| R3‑162095 | Authorization for Pedestrian UE over X2 | LG Electronics Inc., Huawei, CATT, ZTE | imported from 3GU |
| R3‑162096 | CU-DU split:refinement on justification of option 2 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162097 | CU-DU split:On the four questions questions regrading Architectural and specification aspects | NTT DOCOMO INC. | imported from 3GU |
| R3‑162098 | CU-DU split:Justification of Option 6 and 7 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162099 | CU-DU split:Justification of Option 6 and 7 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162100 | CU-DU split:on interface specification aspects | NTT DOCOMO INC. | imported from 3GU |
| R3‑162101 | CU-DU split:Justification of Option 2 and 3 and HL/LL split | NTT DOCOMO INC. | imported from 3GU |
| R3‑162102 | CU-DU split:Refinement for Annex A (Transport network and RAN internal functional split) | NTT DOCOMO INC. | imported from 3GU |
| R3‑162103 | Impacts on RAN3 by Down-selected ME Solutions | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑162104 | Draft ME Stage2 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑162105 | Draft ME Stage3 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑162106 | Consideration on Integration of WLAN in New RAN | ZTE Corporation | imported from 3GU |
| R3‑162107 | TP for Integration of WLAN in New RAN | ZTE Corporation | imported from 3GU |
| R3‑162108 | Further considerations on UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑162109 | Introduction of UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑162110 | Introduction of UE-PC5-AMBR | Huawei | imported from 3GU |
| R3‑162111 | Consideration on FS_feD2D_IoT_relay_wearable | Huawei | imported from 3GU |
| R3‑162112 | TP Update Set for TR 38.801 | ZTE Corporation | imported from 3GU |
| R3‑162113 | Consideration on Supporting Legacy LTE eNB | ZTE Corporation | imported from 3GU |
| R3‑162114 | Coverage enhancement in NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162115 | Some Clarification for NW Slicing | ZTE Corporation, China Telecom | imported from 3GU |
| R3‑162116 | Introduction of Coverage Level Information in M2AP | Huawei | imported from 3GU |
| R3‑162117 | Introduction of Coverage Level Information in M3AP | Huawei | imported from 3GU |
| R3‑162118 | Non Anchor Carrier in NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162119 | Introduction of NPRACH configuration in X2AP | Huawei | imported from 3GU |
| R3‑162120 | Positioning in NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162121 | Mobility in NB-IoT enhancements | Huawei | imported from 3GU |
| R3‑162122 | Some Issues with NW Slicing in Multiple Connectivity Contexts | ZTE Corporation | imported from 3GU |
| R3‑162123 | Tight Interworking between new RAT and LTE | Samsung | imported from 3GU |
| R3‑162124 | Correction for the RAN Function | Samsung | imported from 3GU |
| R3‑162125 | Control Plane Function for Xn | Samsung | imported from 3GU |
| R3‑162126 | Interface in new RAN | Samsung | imported from 3GU |
| R3‑162127 | Interface between eNB and gNB | Samsung | imported from 3GU |
| R3‑162128 | Dual Connectivity for new RAN | Samsung | imported from 3GU |
| R3‑162129 | Consideration on the deployment of function split in CU and DU | Samsung | imported from 3GU |
| R3‑162130 | Consideration on the Fronthaul function split granularity | Samsung | imported from 3GU |
| R3‑162131 | Consideration on the tight interworking effect the split option | Samsung | imported from 3GU |
| R3‑162132 | NG interface considerations | Samsung | imported from 3GU |
| R3‑162133 | NG interface functions and procedures | Samsung | imported from 3GU |
| R3‑162134 | Data forwarding for “Maintaining source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162135 | Signalling impacts for “Maintaining source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162136 | Introduction of "Maintain source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162137 | Introduction of "Maintain source eNB connection solution" | Samsung | imported from 3GU |
| R3‑162138 | Increased CSFB setup delay problem in case of context fetch | Samsung, China Telecom | imported from 3GU |
| R3‑162139 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom | imported from 3GU |
| R3‑162140 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom | imported from 3GU |
| R3‑162141 | Handover without WT change | Samsung | imported from 3GU |
| R3‑162142 | LWA configuration for UL transmission | Samsung | imported from 3GU |
| R3‑162143 | Inter eNB data forwarding activity | Samsung | imported from 3GU |
| R3‑162144 | Parameter analysis for RAN initiated paging | Samsung | imported from 3GU |
| R3‑162145 | Text proposal for stage2 procedure | Samsung | imported from 3GU |
| R3‑162146 | Discussion on CP and existing functionalities | Samsung | imported from 3GU |
| R3‑162147 | Discussion on pure paging area change if X2 absent | Samsung | imported from 3GU |
| R3‑162148 | Discussion on pure paging area change without data transmission | Samsung | imported from 3GU |
| R3‑162149 | Further clarifications for Option 3 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162150 | General considerations for Option 4 and 7 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162151 | Proposal of interface specification for Option 3-1 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162152 | General principles for Fs interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162153 | TP for NW Slicing in Multiple Connectivity Context | ZTE Corporation | imported from 3GU |
| R3‑162154 | TP for SCG Split Bearer | ZTE Corporation | imported from 3GU |
| R3‑162155 | Further Consideration on New RAN Aggregation Scenarios due to CU-DU Split | ZTE Corporation | imported from 3GU |
| R3‑162156 | Procedures for moving within RAN based Paging Area | Huawei, China Telecom | imported from 3GU |
| R3‑162157 | Introduction of light connection in X2AP | Huawei, Nokia, China Telecom | imported from 3GU |
| R3‑162158 | Procedures for moving out of RAN based Paging Area | Huawei, Nokia, China Telecom | imported from 3GU |
| R3‑162159 | DL signalling triggered RAN based paging | Huawei, China Telecom | imported from 3GU |
| R3‑162160 | S1 impacts for Light Connection | Huawei | imported from 3GU |
| R3‑162161 | Introduction of light connection S1 impacts | Huawei | imported from 3GU |
| R3‑162162 | Consideration on Legacy functionalities in Light Connection | Huawei | imported from 3GU |
| R3‑162163 | Localized MBMS architecture for V2X | CATT | imported from 3GU |
| R3‑162164 | Discussion on PC5-AMBR | CATT, ZTE | imported from 3GU |
| R3‑162165 | Introduction of UE PC5 AMBR over S1 | CATT, ZTE | imported from 3GU |
| R3‑162166 | Introduction of UE PC5 AMBR over X2 | CATT, ZTE | imported from 3GU |
| R3‑162167 | Multiple Operator support in V2X | CATT | imported from 3GU |
| R3‑162168 | Paging for lightly connected UE | CATT | imported from 3GU |
| R3‑162169 | Discussion on UE mobility in lightly connected mode | CATT | imported from 3GU |
| R3‑162170 | Discussion on mobility enhancement for NB-IoT | CATT | imported from 3GU |
| R3‑162171 | Discussion on open issues for LWA mobility | CATT | imported from 3GU |
| R3‑162172 | Introduction of a new special subframe configuration | CATT | imported from 3GU |
| R3‑162173 | Introduction of a new special subframe configuration | CATT | imported from 3GU |
| R3‑162174 | TIM view on 5G Migration Path | TELECOM ITALIA S.p.A. | imported from 3GU |
| R3‑162175 | Interworking between LTE and New RAT | LG Electronics Inc. | imported from 3GU |
| R3‑162176 | Inter-RAT Mobility for Standalone Operation | LG Electronics Inc. | imported from 3GU |
| R3‑162177 | Consideration on Xn Interface | LG Electronics Inc. | imported from 3GU |
| R3‑162178 | Consideration on NG Interface Functions and Procedures | LG Electronics Inc. | imported from 3GU |
| R3‑162179 | Access Categories for LWA uplink bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162180 | Access Category information for uplink LWA bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162181 | Access Category information for uplink LWA bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162182 | [draft] Response to the LS on QoS mapping for eLWA UL | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162183 | Handling the UE context in the WT and UE identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162184 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162185 | UL bearer identification and QoS support | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162186 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162187 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162188 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162189 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162190 | Considerations on the eNB-SeGW connectivity for LWIP | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162191 | LWIP enhancements: work plan | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162192 | WLAN-NR deployment and architecture | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162193 | Flow QoS support by NR | Qualcomm Incorporated | imported from 3GU |
| R3‑162194 | Network Slice Selection | Qualcomm Incorporated | imported from 3GU |
| R3‑162195 | RAN based notification area in inactive state | Qualcomm Incorporated | imported from 3GU |
| R3‑162196 | Granularity and reconfiguration of the functional split | Qualcomm Incorporated | imported from 3GU |
| R3‑162197 | Xn Interface Functions | Qualcomm Incorporated | imported from 3GU |
| R3‑162198 | On the New RAN Architecture and the role of Xn | Qualcomm Incorporated | imported from 3GU |
| R3‑162199 | Xx protocol and option 7 support in tight interworking | Qualcomm Incorporated | imported from 3GU |
| R3‑162200 | NR mobility and context fetch | Qualcomm Incorporated | imported from 3GU |
| R3‑162201 | Connecting legacy eNB to NGC | Qualcomm Incorporated | imported from 3GU |
| R3‑162202 | Radio-aware TCP optimization | Qualcomm Incorporated, CMCC, Huawei | imported from 3GU |
| R3‑162203 | TP for for Radio-aware TCP optimization | Qualcomm Incorporated, CMCC, Huawei | imported from 3GU |
| R3‑162204 | Close coupled radio-aware TCP optimization and RAN caching | Qualcomm Incorporated | imported from 3GU |
| R3‑162205 | Architectural and specification aspects for CU-DU split | LG Electronics Inc. | imported from 3GU |
| R3‑162206 | Discussion on UE-PC5-AMBR | LG Electronics Inc. | imported from 3GU |
| R3‑162207 | Introduction of UE-PC5-AMBR over S1 | LG Electronics Inc. | imported from 3GU |
| R3‑162208 | Introduction of UE-PC5-AMBR over X2 | LG Electronics Inc. | imported from 3GU |
| R3‑162209 | Introduction of localized MBMS deployment for V2X | LG Electronics Inc. | imported from 3GU |
| R3‑162210 | Discussion on open issues for lightly connected UE | LG Electronics Inc. | imported from 3GU |
| R3‑162211 | NextGen QoS impact on RAN3 | CATT | imported from 3GU |
| R3‑162212 | RAN selection of CN entity when CN slice defined | CATT | imported from 3GU |
| R3‑162213 | Consideration on Xn interface | CATT | imported from 3GU |
| R3‑162214 | Interface between two eLTE eNBs | CATT | imported from 3GU |
| R3‑162215 | Consideration on CP procedures for inter-working | CATT | imported from 3GU |
| R3‑162216 | Considerations on intra-RAT mobility | CATT | imported from 3GU |
| R3‑162217 | Inactive state and RAN based notification area | CATT | imported from 3GU |
| R3‑162218 | Consideration on RAN function split between CU and DU | CATT | imported from 3GU |
| R3‑162219 | Discussion on solutions to address backhaul long latency issue | Nokia, Alcatel-Lucent Shanghai Bell, CMCC, QUALCOMM CDMA Technologies, NEC | imported from 3GU |
| R3‑162220 | Text Proposal for solutions to address backhaul long latency issue | Nokia, Alcatel-Lucent Shanghai Bell, CMCC, QUALCOMM CDMA Technologies, NEC | imported from 3GU |
| R3‑162221 | Discussion on solutions for video optimization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162222 | Text Proposal for solutions to address issue 3 case 1 and case 3 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162223 | Discussion on solutions for TCP optimization | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162224 | Text Proposal for solutions to address issue 2 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162225 | Clarification on V2X Services Authorized IE | Nokia, Alcatel-Lucent Shanghai Bell, LG Electronics Inc. | imported from 3GU |
| R3‑162226 | Clarification on V2X Services Authorized IE | Nokia, Alcatel-Lucent Shanghai Bell, LG Electronics Inc. | imported from 3GU |
| R3‑162227 | Email discussion summary on RAN3 impact due to the change of PH, PTW_Start calculation | NTT DOCOMO INC. | imported from 3GU |
| R3‑162228 | Discussion on the length of eNB-ID for eNB-ID Extension and Cell-ID Extension | China Telecommunications | imported from 3GU |
| R3‑162229 | LS Response on introducing a new special subframe configuration | CATT | imported from 3GU |
| R3‑162230 | TR 36.742, v0.1.0 | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162231 | RAN functional split: MAC-PHY description and benefits | Intel Corporation | imported from 3GU |
| R3‑162232 | RAN functional split: intra MAC split description and benefits | Intel Corporation | imported from 3GU |
| R3‑162233 | C-plane/U-plane separation in NR RAN | Intel Corporation | imported from 3GU |
| R3‑162234 | Local Breakout for Ultra-Low Latency Communications | Intel Corporation | imported from 3GU |
| R3‑162235 | [DRAFT] Reply LS on the study of the management of RAN virtualized network functions | Intel Corporation | imported from 3GU |
| R3‑162236 | NFV Terminology | Intel Corporation | imported from 3GU |
| R3‑162237 | WLAN throughput indication | Intel Corporation, Ruckus Wireless, Xiaomi, Qualcomm Incorporated, China Telecom, BlackBerry UK Limited | imported from 3GU |
| R3‑162238 | Introduction of WLAN throughput indication | Intel Corporation, Qualcomm Incorporated | imported from 3GU |
| R3‑162239 | Handover without WT change procedure | Intel Corporation | imported from 3GU |
| R3‑162240 | WLAN QoS mapping in UL | Intel Corporation | imported from 3GU |
| R3‑162241 | Introduction of WLAN QoS mapping in UL | Intel Corporation | imported from 3GU |
| R3‑162242 | WLAN band indication | Intel Corporation | imported from 3GU |
| R3‑162243 | Introduction of WLAN band indication | Intel Corporation | imported from 3GU |
| R3‑162244 | Introducing LWA UL support | Intel Corporation | imported from 3GU |
| R3‑162245 | Support of Light connection procedure | Intel Corporation | imported from 3GU |
| R3‑162246 | Stage-3: Support of Light connection | Intel Corporation | imported from 3GU |
| R3‑162247 | NR QoS Framework | Intel Corporation | imported from 3GU |
| R3‑162248 | New RAN function to contact inactive mode UEs | Intel Corporation | imported from 3GU |
| R3‑162249 | Solutions for UP-CP separation in access network | IAESI, Thales, Fairspectrum, VTT | imported from 3GU |
| R3‑162250 | Control functions handled by a Central Coordinator | IAESI, Thales, Fairspectrum, VTT | imported from 3GU |
| R3‑162251 | Introduction of Transmission Points for OTDOA in a Shared Cell-ID scenario and PRS-based Terrestrial Beacon Systems | Qualcomm Incorporated | imported from 3GU |
| R3‑162252 | Introduction of Transmission Points for OTDOA in Shared Cell-ID Scenario and PRS based Terrestrial Beacon Systems | Qualcomm Incorporated | imported from 3GU |
| R3‑162253 | Introduction of Transmission Points for OTDOA in Shared Cell-ID Scenario and PRS based Terrestrial Beacon Systems | Qualcomm Incorporated | imported from 3GU |
| R3‑162254 | On the ambiguity of counting procedures when receiving eMBMS on SCell or non-serving cell | Qualcomm Incorporated | imported from 3GU |
| R3‑162255 | Impact on “Messages-Waiting” function in SMS | VODAFONE Group Plc | imported from 3GU |
| R3‑162256 | Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162257 | Correction to Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | imported from 3GU |
| R3‑162258 | Resume Cause | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | imported from 3GU |
| R3‑162259 | Correction to UE Context Resume Request | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | imported from 3GU |
| R3‑162260 | Xn interface functions | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162261 | Mobility enhancement for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162262 | Further discussion on X2AP correction for eMTC | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162263 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T | imported from 3GU |
| R3‑162264 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T | imported from 3GU |
| R3‑162265 | Down-selecting options for X2 data forwarding for make-before-break | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162266 | Proposal for problem analysis | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162267 | SON for eCoMP use-cases | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162268 | Baseline solution and improvement path | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162269 | Further solutions proposals | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162270 | Reply LS on Network Assistance for Network Synchronization in LTE (To: RAN3, RAN; Cc: RAN4) | RAN1, Huawei | imported from 3GU |
| R3‑162271 | LS to RAN2/3 on RAN1 progress on MC enhancements (To: RAN2, RAN3) | RAN1 | imported from 3GU |
| R3‑162272 | LS on RAN1 agreements for NR initial access and mobility (To: RAN2; Cc: RAN3, RAN4) | RAN1, ericsson | imported from 3GU |
| R3‑162273 | LS on NB-IoT positioning (To: TSG RAN; Cc: RAN2, RAN3, RAN4) | RAN1, huawei | imported from 3GU |
| R3‑162274 | LS on PRS sequence generation per TP (To: RAN2, RAN3) | RAN1, huawei | imported from 3GU |
| R3‑162275 | LS on PRS-based Terrestrial Beacon System (TBS) (To: RAN2, RAN3; Cc: RAN4) | RAN1, qualcomm | imported from 3GU |
| R3‑162276 | LS on introducing a new special subframe configuration (To: RAN2, RAN3) | RAN1, China Mobile | imported from 3GU |
| R3‑162277 | LS Response on QoS requirements for V2X (To: SA1, SA2; Cc: RAN1, RAN3) | RAN2, intel | imported from 3GU |
| R3‑162278 | Response LS on delay tolerant access via NB-IOT (To: SA2, CT, CT1; Cc: RAN3) | RAN2, qualcomm | imported from 3GU |
| R3‑162279 | LS on eDRX Paging Hyper-frame and PTW_Start Calculation (To: SA2, RAN3, CT1; Cc: SA3, CT4) | RAN2, nttdocomo | imported from 3GU |
| R3‑162280 | LS on QoS mapping for eLWA UL (To: RAN3) | RAN2, intel | imported from 3GU |
| R3‑162281 | LS on further mobility enhancements (To: RAN1, RAN3, RAN4) | RAN2, zte | imported from 3GU |
| R3‑162282 | Reply LS on RAN impacts of Shared MBMS Network and Receive Only Mode in eMBMS (To: SA2, RAN3) | RAN2, nokia | imported from 3GU |
| R3‑162283 | Reply LS on ECID positioning for TDD (To: RAN1, RAN3, RAN4; Cc: RAN5) | RAN2, catt | imported from 3GU |
| R3‑162284 | LS on RAN2 agreements on UMTS and LTE joint operation (To: RAN3) | RAN2, China Unicom | imported from 3GU |
| R3‑162285 | LS on performance enhancements indicator for high speed scenarios (To: RAN2; Cc: RAN3) | RAN4, ericsson, intel | imported from 3GU |
| R3‑162286 | Reply LS on the feasibility of mobility enhancement solutions (To: RAN2; Cc: RAN1, RAN3) | RAN4, ericsson, ZTE | imported from 3GU |
| R3‑162287 | Reply LS on QoS requirements for V2X (To: RAN2; Cc: SA1, RAN1, RAN3) | SA2, lge | imported from 3GU |
| R3‑162288 | Response to LS S2-164308 (S6-160914) on MBMS enhancements for MCS (To: SA6; Cc: SA4, RAN2, RAN3) | SA2, motorolasolutions | imported from 3GU |
| R3‑162289 | Reply LS on Multiple bearer capability handling (To: CT1, CT4; Cc: RAN2, RAN3, TSG CT) | SA2, intel | imported from 3GU |
| R3‑162290 | LS on overload control for CP CIoT EPS optimization (To: RAN2, RAN3) | SA2, NEC | imported from 3GU |
| R3‑162291 | Further LS on CIoT NAS retransmission timers (To: CT1; Cc: RAN2, RAN3) | SA2, vodafone | imported from 3GU |
| R3‑162292 | Reply LS on SAND (To: RAN3; Cc: RAN2) | SA4, intel | imported from 3GU |
| R3‑162293 | Reply LS on QoE reporting for streaming services (To: RAN2, SA5, RAN3; Cc: TSG RAN) | SA4, huawei | imported from 3GU |
| R3‑162294 | Editorial Update of TR 38.801 (v040) | NEC | imported from 3GU |
| R3‑162295 | How many splits in Function Split options and principles | NEC | imported from 3GU |
| R3‑162296 | Overload control for CP CIoT EPS optimization | NEC | imported from 3GU |
| R3‑162297 | [DRAFT] Reply LS on overload control for CP CIoT EPS optimization | NEC | imported from 3GU |
| R3‑162298 | Network Slicing and Mobility Support | NEC | imported from 3GU |
| R3‑162299 | Network Slicing and Tenant Charging | NEC | imported from 3GU |
| R3‑162300 | Connectivity to the Same WT in inter-eNB HO: how to determine | NEC | imported from 3GU |
| R3‑162301 | Architecture and protocols of evolved LTE connecting to NG-Core | Huawei | imported from 3GU |
| R3‑162302 | NG interface functions | Huawei | imported from 3GU |
| R3‑162303 | Xn interface functions and protocol stack design | Huawei | imported from 3GU |
| R3‑162304 | Interface between two eLTE eNBs | Huawei | imported from 3GU |
| R3‑162305 | Control plane protocol of NG | Huawei | imported from 3GU |
| R3‑162306 | Mobility between NR and (Evolved) E-UTRA | Huawei | imported from 3GU |
| R3‑162307 | Support of Redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162308 | Support of Redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162309 | [Draft] LS on support of redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162310 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162311 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162312 | Enhancement for MME Overload Control | Huawei, U.S. Cellular | imported from 3GU |
| R3‑162313 | Discussion on data forwarding for make before break solution | CATT | imported from 3GU |
| R3‑162314 | Local Breakout to support Ultra-Low Latency Communications | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162315 | Discussion on UE throughput indication | Huawei | imported from 3GU |
| R3‑162316 | Discussion on UL Transmission in LWA | Huawei | imported from 3GU |
| R3‑162317 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑162318 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑162319 | Uplink transmission in eLWA | Huawei | imported from 3GU |
| R3‑162320 | Discussion on Mobility enhancements | Huawei | imported from 3GU |
| R3‑162321 | Discussion on eNB-ID and Cell-ID extension in E-UTRAN | Huawei, China Telecom | imported from 3GU |
| R3‑162322 | Draft LS on Flexible eNB-ID and Cell-ID in E-UTRAN | Huawei, China Telecom | imported from 3GU |
| R3‑162323 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162324 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162325 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162326 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162327 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162328 | Introduction of New types of eNB ID | Huawei, China Telecom | imported from 3GU |
| R3‑162329 | Further consideration on RAN internal function split | Huawei | imported from 3GU |
| R3‑162330 | Further considerations on intra-RLC split | Huawei | imported from 3GU |
| R3‑162331 | Discussion on RAN Functions Realization | Huawei | imported from 3GU |
| R3‑162332 | Draft Response LS on the study of the management of RAN virtualized network functions | Huawei | imported from 3GU |
| R3‑162333 | Correction on Deployment scenarios | ZTE Corporation, China Telecom, China Unicom | imported from 3GU |
| R3‑162334 | Discussion on the functions of Xn interface | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑162335 | Consideration on “inactive state” in NR | ZTE Corporation | imported from 3GU |
| R3‑162336 | Mobility scenarios for “inactive state” | ZTE Corporation | imported from 3GU |
| R3‑162337 | Clarification on URLLC Requirement | ZTE, China Unicom | imported from 3GU |
| R3‑162338 | Option3/3a clean up | ZTE Corporation | imported from 3GU |
| R3‑162339 | Discussion on the basic procedures of NG-C interface | ZTE,China Telecom | imported from 3GU |
| R3‑162340 | Discussion on inter-RAT mobility | ZTE Corporation | imported from 3GU |
| R3‑162341 | QoS consideration in RAN | ZTE Corporation | imported from 3GU |
| R3‑162342 | Discussion on CU-DU functional split | ZTE Corporation | imported from 3GU |
| R3‑162343 | Consideration about the CU-DU function split between intra-PHY | ZTE Corporation | imported from 3GU |
| R3‑162344 | Clarification on CU-DU split options | ZTE Corporation | imported from 3GU |
| R3‑162345 | Correction on NB-IoT RRC Establishment Cause | ZTE Corporation | imported from 3GU |
| R3‑162346 | Consideration on R14 NB IOT mobility enhancement | ZTE Corporation | imported from 3GU |
| R3‑162347 | Further Consideration on Various RAN3 Aspects of eLTE | ZTE Corporation, China Telecom | imported from 3GU |
| R3‑162348 | Consideration for NR RAN internal interface for higher layer functional split | KT Corp. | imported from 3GU |
| R3‑162349 | Consideration for NR RAN internal interface for higher layer functional split | KT Corp. | imported from 3GU |
| R3‑162350 | Evaluation of the DASH optimization solution | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑162351 | Work Plan on QoE Measurement Collection for streaming services in UTRAN | China Unicom | imported from 3GU |
| R3‑162352 | TP for the evaluation on the DASH optimization solution | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑162353 | TR 37.805, Study on HSPA and LTE Joint Operation, v1.2.0 | China Unicom | imported from 3GU |
| R3‑162354 | Discussion on the solution of video optimization | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162355 | Views on 5G architecture evolution path | China Unicom | imported from 3GU |
| R3‑162356 | Xx interface justification and functionalities | Huawei | imported from 3GU |
| R3‑162357 | Considerations on PDCP design | Huawei | imported from 3GU |
| R3‑162358 | Architectural and procedural aspects for tight interworking | Huawei | imported from 3GU |
| R3‑162359 | Comparison of user plane architecture options for tight interworking | Huawei | imported from 3GU |
| R3‑162360 | User plane design details for LTE-NR tight interworking | Huawei | imported from 3GU |
| R3‑162361 | Inter-RAT mobility with LTE | Huawei | imported from 3GU |
| R3‑162362 | Discussion on inactive mode in NR | LG Electronics Inc. | imported from 3GU |
| R3‑162363 | TP for the solution (direct method) of video optimization | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162364 | TP for the solution (indirect method) of video optimization | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162365 | Discussion on the solution of TCP optimization | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162366 | TP for the solution of TCP optimization | Huawei, Qualcomm Incorporated, CMCC | imported from 3GU |
| R3‑162367 | Correction on the reinitiating waiting time in SLm | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑162368 | Correction on the reinitiating waiting time in Xw | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| R3‑162369 | Initial Considerations on Rel14 feD2D | ZTE Corporation | imported from 3GU |
| R3‑162370 | Architecture options for Context Aware Service Delivery | ZTE Corporation | imported from 3GU |
| R3‑162371 | Discussion on the OTDOA enhancements | Huawei | imported from 3GU |
| R3‑162372 | Introduction of the same PCI case for OTDOA enhancements | Huawei | imported from 3GU |
| R3‑162373 | Function support for local breakout | CMCC | imported from 3GU |
| R3‑162374 | Benefit and justification of Option3-2 | CMCC | imported from 3GU |
| R3‑162375 | TP for Benefit and justification of Option3-2. | CMCC | imported from 3GU |
| R3‑162376 | Benefit of asymmetrical split realization of option 7 | CMCC | imported from 3GU |
| R3‑162377 | Draft TR 36.933v_100 | CMCC | imported from 3GU |
| R3‑162378 | Solution to backhaul long latency issue | CMCC, Qualcomm Incorporated | imported from 3GU |
| R3‑162379 | TP for service information acquisition and UE assisted local cache | CMCC, Qualcomm Incorporated | imported from 3GU |
| R3‑162380 | Fronthaul split deployments | Mitsubishi Electric RCE | imported from 3GU |
| R3‑162381 | Text Proposal for 38.801 on CP/UP separation | Deutsche Telekom, SK-Telecom, AT&T, Telecom Italia | imported from 3GU |
| R3‑162382 | Discussion on terminology of next generation technology | ZTE Corporation | imported from 3GU |
| R3‑162383 | DRX enhancements in CELL_FACH | Huawei | imported from 3GU |
| R3‑162384 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑162385 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑162386 | Introduction of DRX enhancements | Huawei | imported from 3GU |
| R3‑162387 | TP corrections for joint operation | Huawei | imported from 3GU |
| R3‑162388 | Configuration impacts of Multi-carrier enhancements | Huawei | imported from 3GU |
| R3‑162389 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑162390 | Introduction of MC configuration | Huawei | imported from 3GU |
| R3‑162391 | Enhanced TTI switching for Multi-carrier enhancements | Huawei | imported from 3GU |
| R3‑162392 | Introduction of enhanced TTI switching | Huawei | imported from 3GU |
| R3‑162393 | Introduction of enhanced TTI switching | Huawei | imported from 3GU |
| R3‑162394 | RAN3 impacts for QoE Measurement Collection for streaming services | Huawei | imported from 3GU |
| R3‑162395 | UP-CP Separation Architecture | Samsung Electronics Co., Ltd | imported from 3GU |
| R3‑162396 | UP-CP Function Descriptions | Samsung Electronics Co., Ltd | imported from 3GU |
| R3‑162397 | Update of the Session Management Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162398 | NG principle for QoS differentiation Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162399 | Description of the Session Management Function | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162400 | Generic QoS Framework over NG interface | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162401 | Definition for RAN support of slicing | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162402 | Update of principle for selection of CN entity | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162403 | Update of principle for selection of RAN part of network slice | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162404 | Isolation using dedicated radio resources | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162405 | Solutions for User Plane protocol stack | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162406 | Paging and Mobility in Inactive State | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162407 | NR function for in-band path switch | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162408 | Reusing Available WLAN Measurements to Enhance E-CID | Ericsson | imported from 3GU |
| R3‑162409 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162410 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson | imported from 3GU |
| R3‑162411 | Introduction of an E-UTRAN triggered S1 Overload procedure | Ericsson | imported from 3GU |
| R3‑162412 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162413 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162414 | Correction of eDRX Information | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162415 | Feedback to RAN2#95 and Open Issues | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162416 | On common and specific building blocks for inactive Ues | Ericsson | imported from 3GU |
| R3‑162417 | Scenarios for inter-RAT mobility | Ericsson | imported from 3GU |
| R3‑162418 | New RAN Architecture | Ericsson | imported from 3GU |
| R3‑162419 | Procedures Analysis for the NG1 Interface | Ericsson | imported from 3GU |
| R3‑162420 | Observations on migration paths | Ericsson | imported from 3GU |
| R3‑162421 | RAN architecture scenarios requiring flexible design | Ericsson | imported from 3GU |
| R3‑162422 | Clarifications on fronthaul bitrate requirements | Ericsson | imported from 3GU |
| R3‑162423 | Analysis of Split Architecture Option 8 | Ericsson | imported from 3GU |
| R3‑162424 | RAN Architecture and Specification Aspects | Ericsson | imported from 3GU |
| R3‑162425 | Analysis of UP-CP Separation | Ericsson | imported from 3GU |
| R3‑162426 | Some observations on NFV | Ericsson | imported from 3GU |
| R3‑162427 | Next Generation Shared RAN | Ericsson | imported from 3GU |
| R3‑162428 | Work Item: Multi-Carrier Enhancements for UMTS | Ericsson | imported from 3GU |
| R3‑162429 | Enhancing LWIP in RAN3 | Ericsson | imported from 3GU |
| R3‑162430 | Specification Impact analysis from WID: Flexible eNB-ID and Cell-ID in E-UTRAN | Ericsson | imported from 3GU |
| R3‑162431 | Service Continuity and Mobility | Ericsson | imported from 3GU |
| R3‑162432 | On common and specific building blocks for light connected UEs | Ericsson | imported from 3GU |
| R3‑162433 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162434 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162435 | Introduction of the light connected mode | Ericsson | imported from 3GU |
| R3‑162436 | Issues identified by the latest WF document | Ericsson | imported from 3GU |
| R3‑162437 | Issues with an explicit RAN Paging Area | Ericsson | imported from 3GU |
| R3‑162438 | Issues with a cell list as UE specific paging area | Ericsson | imported from 3GU |
| R3‑162439 | Further Optimised Paging Optimisation | Ericsson | imported from 3GU |
| R3‑162440 | OTDOA Enhancements for Multiple Transmission Points | Ericsson | imported from 3GU |
| R3‑162441 | OTDOA Enhancements for Same-PCI Issue and Multiple TPs | Ericsson | imported from 3GU |
| R3‑162442 | Further Observations on Handover without WT Change | Ericsson | imported from 3GU |
| R3‑162443 | Uplink QoS Handling | Ericsson | imported from 3GU |
| R3‑162444 | [DRAFT] Reply LS on QoS Mapping for eLWA UL | Ericsson | imported from 3GU |
| R3‑162445 | Solution proposal for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑162446 | Corrections to Solution 1 for DASH Optimisation | Ericsson | imported from 3GU |
| R3‑162447 | CN overload protection for CP solution | Ericsson | imported from 3GU |
| R3‑162448 | Introduction of Overload Action for CP CIoT Data Transfer | Ericsson | imported from 3GU |
| R3‑162449 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑162450 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑162451 | Introduction of eDECOR in RAN | Ericsson | imported from 3GU |
| R3‑162452 | eNB Overload handling for CP CIoT Optimisation | Ericsson | imported from 3GU |
| R3‑162453 | Introduction of an E-UTRAN triggered S1 Overload procedure | Ericsson | imported from 3GU |
| R3‑162454 | Reply LS on RAN2#95 agreements on light connection | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162455 | LS on Paging parameters used in light connected mode | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
| R3‑162456 | Consideration on CP-UP separation | Huawei | imported from 3GU |
| R3‑162457 | Support for Ultra-Reliable Low Latency Communication | Huawei | imported from 3GU |
| R3‑162458 | QoS framework impact on RAN | Huawei | imported from 3GU |
| R3‑162459 | QoS principles in RAN | Huawei | imported from 3GU |
| R3‑162460 | Solution for Selection of Network Slice and CN entity | Huawei | imported from 3GU |
| R3‑162461 | Key principles for Support of Network Slicing in RAN | Huawei | imported from 3GU |
| R3‑162462 | Support of Network Slice Discovery | Huawei | imported from 3GU |
| R3‑162463 | Resource Management between Slices | Huawei | imported from 3GU |
| R3‑162464 | Considerations on SON for eCoMP for LTE | Huawei | imported from 3GU |
| R3‑162465 | Paging and Mobility in Light Connected Mode | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | imported from 3GU |
| R3‑162466 | Introduction of Light Connected State | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | imported from 3GU |
| R3‑162467 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson LM | imported from 3GU |
| R3‑162468 | Proposal for TR 38.801 structure change | TR 38.801 Rapporteur (NTT DOCOMO INC.) | imported from 3GU |
| R3‑162469 | RAN Functional Split Considerations for NR | Interdigital Asia LLC | imported from 3GU |
| R3‑162470 | Tight interworking effects on RAN Split | Interdigital Asia LLC | imported from 3GU |
| R3‑162471 | Split Option 1 benefits | Interdigital Asia LLC | imported from 3GU |
| R3‑162472 | Description of intra-MAC functional split | Fujitsu | imported from 3GU |
| R3‑162473 | Use cases for TR 36.742 - SON for eCoMP | Fujitsu | imported from 3GU |
| R3‑162474 | Consideration on network slice in NR | LG Electronics Inc. | imported from 3GU |
| R3‑162475 | Text Proposal for 38.801 on CP/UP separation | Deutsche Telekom, SK-Telecom, AT&T, Telecom Italia | imported from 3GU |
| R3‑162476 | Stage-2: Support of Light connection | Intel Corporation | imported from 3GU |
| R3‑162477 | Mitigation of impacts to legacy functionalities from light connection | Intel Corporation | imported from 3GU |
| R3‑162478 | Introducing UE throughput indication | Qualcomm Incorporated, Intel Corporation | imported from 3GU |
| R3‑162479 | Discussion on NG1 user plane | LG Electronics Inc. | imported from 3GU |
| R3‑162480 | Analysis On the Use of Xw Interface(s) for eLWIP | BROADCOM CORPORATION | imported from 3GU |
| R3‑162481 | Text proposal for handling thepower saving relation operation | Samsung | imported from 3GU |
| R3‑162482 | Paging and mobility procedures in light connection | Qualcomm Incorporated | imported from 3GU |
| R3‑162483 | Abnormal case for eDRX paging configuration | NTT DOCOMO INC. | imported from 3GU |
| R3‑162484 | User Plane for Handover without WT Change | Qualcomm Incorporated | imported from 3GU |
| R3‑162485 | Discussion on open issues for lightly connected UE | LG Electronics Inc. | imported from 3GU |
| R3‑162486 | Work plan on NR Study Item in RAN2 and RAN3 | NTT DOCOMO, INC. (Rapporteur) | imported from 3GU |
| R3‑162487 | Response to R3-162418 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162488 | LS on RAN1 agreements for LTE-based V2X [To:RAN2, RAN3, SA2] | RAN1 | imported from 3GU |
| R3‑162489 | Response to tdocs in Agenda 10.6.1.1 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162490 | Response to R3-162156 | NTT DOCOMO INC. | imported from 3GU |
| R3‑162491 | LS on Transport of CPRI and future mobile interfaces (ITU_T_SG15_COM15LS382E; to: RAN3, IEEE 1914, CPRI TWG, IEEE 802.1 TSN; cc: ITU-T FG IMT2020; contact: Huawei) | ITU-T SG15 | - |
| R3‑162492 | Chairman's notes for the session on WI Core part: Flexible eNB-ID and Cell-ID in E-UTRAN | RAN3 vice-chairman (Nokia) | - |
| R3‑162493 | Chairman's notes for the session on WI Core part: Multi-Carrier Enhancements for UMTS | RAN3 vice-chairman (Ericsson) | - |
| R3‑162494 | Chairman's notes for the session on Core part: DTX/DRX enhancements in CELL_FACH | RAN3 vice-chairman (Ericsson) | - |
| R3‑162495 | Chairman's notes for the session on Core part: Further Indoor Positioning Enhancements for UTRA and LTE | RAN3 vice-chairman (Ericsson) | - |
| R3‑162496 | Chairman's notes for the session on Study on HSPA and LTE Joint Operation | RAN3 vice-chairman (Ericsson) | - |
| R3‑162497 | TR 30.531 v1.26.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | - |
| R3‑162498 | Introduction of a new special subframe configuration | CATT | - |
| R3‑162499 | [DRAFT] Reply LS on overload control for CP CIoT EPS optimization (to: SA2, RAN2; cc: -; contact: NEC) | NEC | - |
| R3‑162500 | Way forward on eNB-SeGW connectivity for LWIP | Nokia | - |
| R3‑162501 | Introduction of solution to solve CSFB setup delay problem | Samsung, China Telecom | - |
| R3‑162502 | Correction to Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | - |
| R3‑162503 | Correction to UE Context Resume Request | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | - |
| R3‑162504 | Correction to UE Context Resume Request | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | - |
| R3‑162505 | Correction to Served Cell Information for NB-IoT | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | - |
| R3‑162506 | Text Proposal for 38.801 on CP/UP separation | Deutsche Telekom, SK-Telecom, AT&T, Telecom Italia, Intel, BT | - |
| R3‑162507 | Support of Redirection for VoLTE | Huawei | - |
| R3‑162508 | [Draft] LS on support of redirection for VoLTE | Huawei | imported from 3GU |
| R3‑162509 | Introduction of localized MBMS deployment for V2X | LG Electronics Inc. | - |
| R3‑162510 | Authorization for Pedestrian UE over S1 | LG Electronics Inc., Huawei, CATT, ZTE | - |
| R3‑162511 | Authorization for Pedestrian UE over X2 | LG Electronics Inc., Huawei, CATT, ZTE | - |
| R3‑162512 | Report of offline discussions on V2X | Ericsson | imported from 3GU |
| R3‑162513 | Summary of agreements and open issues on V2X | LG Electronics | - |
| R3‑162514 | Correction of eDRX | Nokia | imported from 3GU |
| R3‑162515 | Editorial corrections to Slice Selection Solution 2 | Ericsson | - |
| R3‑162516 | Correction of Benefit and justification of Option3-2 | Ericsson | - |
| R3‑162517 | Control Plane Function for Xn | Samsung | - |
| R3‑162518 | Interface between two eLTE eNBs | CATT | - |
| R3‑162519 | Considerations on intra-RAT mobility | CATT | - |
| R3‑162520 | Draft Reply to: LS on further mobility enhancements (To: RAN1, RAN3, RAN4) | ZTE | - |
| R3‑162521 | Way forward on WI Further Mobility enhancement in LTE, summary of issues and solutions | ZTE | - |
| R3‑162522 | Draft Response LS to (ITU_T_SG15_COM15LS382E = R3-162491 on Transport of CPRI and future mobile interfaces (to: RAN; cc: -; contact: Huawei) | Huawei | - |
| R3‑162523 | Way forward regarding NR coordination | NTT DOCOMO | - |
| R3‑162524 | [DRAFT] Reply LS on the study of the management of RAN virtualized network functions | Intel Corporation | - |
| R3‑162525 | Proposal for TR 38.801 structure change | TR 38.801 Rapporteur (NTT DOCOMO INC.) | - |
| R3‑162526 | TR 38.801 v0.5.0 including agreements in existing TR structure | NTT DOCOMO | imported from 3GU |
| R3‑162527 | TR 38.801 v0.6.0 with new TR structure | NTT DOCOMO | imported from 3GU |
| R3‑162528 | Editorial Update of TR 38.801 (v040) | NEC | - |
| R3‑162529 | pCR to TR 38.801 on Cascade deployment | Mitsubishi Electric RCE | - |
| R3‑162530 | Split Option 1 benefits | Interdigital Asia LLC | - |
| R3‑162531 | CU-DU split:Justification of Option 2 and 3 and HL/LL split | NTT DOCOMO INC. | - |
| R3‑162532 | Tight interworking effects on RAN Split | Interdigital Asia LLC | - |
| R3‑162533 | RAN architecture scenarios requiring flexible design | Ericsson | - |
| R3‑162534 | Further considerations on intra-RLC split | Huawei | - |
| R3‑162535 | TP for Benefit and justification of Option3-2. | CMCC | - |
| R3‑162536 | CP/CP separation | Deutsche Telekom | - |
| R3‑162537 | NFV Terminology | Intel Corporation | - |
| R3‑162538 | NFV challenges | Ericsson | - |
| R3‑162539 | Draft LS on non-anchor paging support for NB-IoT enhancements (to: RAN2; cc: -; contact: Huawei) | Huawei | - |
| R3‑162540 | Summary of agreements and open issues for NB-IoT enhancements | Huawei | - |
| R3‑162541 | Description of intra-MAC functional split | Fujitsu | - |
| R3‑162542 | CU-DU split:Justification of Option 6 and 7 | NTT DOCOMO INC. | - |
| R3‑162543 | LS on TTI switching for MC enhancements (R2-167171; to: RAN1, RAN3; cc: -; contact: Huawei) | RAN2 | - |
| R3‑162544 | Benefit of asymmetrical split realization of option 7 | CMCC | - |
| R3‑162545 | Analysis of Split Architecture Option 8 | Ericsson | - |
| R3‑162546 | Clarifications on fronthaul bitrate requirements | Ericsson | - |
| R3‑162547 | CU-DU split:On first question regrading Architectural and specification aspects | NTT DOCOMO INC. | - |
| R3‑162548 | Granularity and reconfiguration of the functional split | Qualcomm Incorporated | - |
| R3‑162549 | CU-DU split: TP on Reconfiguration dynamicity | NTT DOCOMO | - |
| R3‑162550 | Response to question 2. on whether LTE/NR interworking case effects the number of functional split options | Ericsson | - |
| R3‑162551 | Introducing UE throughput indication | Qualcomm Incorporated, Intel Corporation | - |
| R3‑162552 | Inter-eNB mobility with LWA active | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162553 | Introduction of WLAN band indication | Intel Corporation | - |
| R3‑162554 | Correction on NB-IoT RRC Establishment Cause | ZTE Corporation | - |
| R3‑162555 | Correction of eDRX | Nokia | imported from 3GU |
| R3‑162556 | Introduction of the light connected mode | Ericsson | - |
| R3‑162557 | Introduction of the light connected mode | Ericsson | - |
| R3‑162558 | Introduction of the light connected mode | Ericsson | - |
| R3‑162559 | Introduction of Light Connected State | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | - |
| R3‑162560 | Introduction of light connection in X2AP | Huawei, Nokia, China Telecom | - |
| R3‑162561 | Draft LS on light connection (to: RAN2, SA3, SA2; cc: -; contact: Intel) | Intel | - |
| R3‑162562 | Summary of agreements and open issues on lightweight communication | Huawei | - |
| R3‑162563 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162564 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162565 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162566 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162567 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162568 | Introduction of New types of eNB ID | Huawei, China Telecom | - |
| R3‑162569 | Draft LS on Flexible eNB-ID and Cell-ID in E-UTRAN (to: CT1, CT4, SA5, RAN6; cc: RAN2, SA2; contact: Huawei) | Huawei, China Telecom | - |
| R3‑162570 | Summary of agreements and open issues | Huawei | - |
| R3‑162571 | Introduction of UE PC5 AMBR over S1 | CATT, ZTE, Huiawei | - |
| R3‑162572 | Introduction of UE-PC5-AMBR | Huawei, CATT | - |
| R3‑162573 | New RAN Architecture | Ericsson | - |
| R3‑162574 | Local Breakout to support Ultra-Low Latency Communications | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162575 | NG interface functions and procedures | Samsung | - |
| R3‑162576 | Procedures Analysis for the NG1 Interface | Ericsson | - |
| R3‑162577 | Discussion on NG1 user plane | LG Electronics Inc. | - |
| R3‑162578 | Solutions for User Plane protocol stack | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162579 | Control plane protocol of NG | Huawei | - |
| R3‑162580 | NG interface: flex only | Samsung | - |
| R3‑162581 | Report of offline session on V2X | Ericsson | - |
| R3‑162582 | Introduction of MC configuration | Huawei | - |
| R3‑162583 | Introduction of MC configuration | Huawei | - |
| R3‑162584 | Introduction of DRX enhancements | Huawei | - |
| R3‑162585 | Reusing Available WLAN Measurements as E-CID Assistance Data | Ericsson | - |
| R3‑162586 | Summmary of agreements and open issues on | Huawei | - |
| R3‑162587 | Reply LS to R2-165744 on Multi-carrier enhancements for UMTS (R1-1610571; to: RAN2, RAN3; cc: -; contact: Ericsson) | RAN1 | - |
| R3‑162588 | LS on RAN1 progress on MC enhancements (R1-1610572; to: RAN2, RAN3; cc: -; contact: Huawei) | RAN1 | - |
| R3‑162589 | Update of the Session Management Function | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162590 | Scenarios for inter-RAT mobility | Ericsson | - |
| R3‑162591 | Description of the Session Management Function | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162592 | On common and specific building blocks for inactive Ues | Ericsson | - |
| R3‑162593 | QoS principles in RAN | Huawei | - |
| R3‑162594 | Solution for Selection of Network Slice and CN entity | Huawei | - |
| R3‑162595 | Network Slicing and Mobility Support | NEC | - |
| R3‑162596 | Consideration on Xn Interface | LG Electronics Inc. | - |
| R3‑162597 | Protocol stack for Xn | Huawei | - |
| R3‑162598 | Interface in new RAN | Samsung | - |
| R3‑162599 | Further clarifications for Option 3 | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162600 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T | - |
| R3‑162601 | Target cell selection for low complexity UEs and UEs in enhanced coverage | Nokia, Alcatel-Lucent Shanghai Bell, AT&T | - |
| R3‑162602 | Next Generation Shared RAN | Ericsson | - |
| R3‑162603 | Corrections to Solution 1 for DASH Optimisation | Ericsson | - |
| R3‑162604 | Draft TR 36.933 v1.1.0 | CMCC | - |
| R3‑162605 | TP for the evaluation on the DASH optimization solution | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑162606 | Draft LS Response on introducing a new special subframe configuration (to: RAN1, RAN2; cc: -; contact: CATT) | CATT | - |
| R3‑162607 | Text Proposal for solutions to address issue 3 case 1 and case 3 | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162608 | SON for eCoMP use-cases | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162609 | TR 36.742, v0.2.0 | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162610 | Correction on the reinitiating waiting time in Xw | HUAWEI TECHNOLOGIES Co. Ltd. | - |
| R3‑162611 | Introduction of a new special subframe configuration | CATT | - |
| R3‑162612 | LS Response to R1-168559 = R3-162276 on introducing a new special subframe configuration (to: RAN1, RAN2; cc: -; contact: CATT) | RAN3 | - |
| R3‑162613 | Reply LS to S2-165431 = R3-162290 on overload control for CP CIoT EPS optimization (to: SA2, RAN2; cc: -; contact: NEC) | RAN3 | - |
| R3‑162614 | Correction to UE Context Resume Request | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | - |
| R3‑162615 | Correction to UE Context Resume Request | Nokia, Alcatel-Lucent Shanghai Bell, Intel Corporation | - |
| R3‑162616 | Response LS to ITU_T_SG15_COM15LS382E = R3-162491 on Transport of CPRI and future mobile interfaces (to: RAN; cc: -; contact: Huawei) | RAN3 | - |
| R3‑162617 | Reply LS to S5-164305 = R3-161570 on the study of the management of RAN virtualized network functions (to: SA5; cc: SA, RAN; contact: Intel) | RAN3 | - |
| R3‑162618 | CP/CP separation | Deutsche Telekom | - |
| R3‑162619 | Description of the Session Management Function | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162620 | Uplink bearer identification | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162621 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162622 | Enabling uplink data bearers | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162623 | QoS principles in RAN | Huawei | - |
| R3‑162624 | Network Slicing and Mobility Support | NEC | - |
| R3‑162625 | Procedures Analysis for the NG1 Interface | Ericsson | - |
| R3‑162626 | Solutions for User Plane protocol stack | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162627 | NG interface: flex only | Samsung | - |
| R3‑162628 | Inter-RAT mobility with LTE | Huawei | - |
| R3‑162629 | Further clarifications for Option 3 | Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162630 | Split Option 1 benefits | Interdigital Asia LLC | - |
| R3‑162631 | CU-DU split:On first question regrading Architectural and specification aspects | NTT DOCOMO INC. | - |
| R3‑162632 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell | - |
| R3‑162633 | Response to question 2. on whether LTE/NR interworking case effects the number of functional split options | Ericsson | - |
| R3‑162634 | Granularity and reconfiguration of the functional split | Qualcomm Incorporated | - |
| R3‑162635 | NFV Terminology | Intel Corporation | - |
| R3‑162636 | Summary of agreements and open issues on NR | NTT DOCOMO | imported from 3GU |
| R3‑162637 | LS on Flexible eNB-ID and Cell-ID in E-UTRAN (to: CT1, CT4, SA5, RAN6; cc: RAN2, SA2; contact: Huawei) | RAN3 | - |
| R3‑162638 | Way Forward on WLAN UL QoS mapping for eLWA | Intel | - |
| R3‑162639 | Draft Response LS to R2-165969 = R3-162281 on the Make Before Break solution (to: RAN2; cc: RAN1, RAN4; contact: ZTE) | ZTE | - |
| R3‑162640 | XwAP Support for Inter-eNB Mobility without WT Change | Ericsson, Intel | - |
| R3‑162641 | Draft LS on light connection (to: RAN2, SA3, SA2; cc: -; contact: Intel) | Intel | - |
| R3‑162642 | LS on light connection (to: RAN2, SA3; cc: -; contact: Intel) | RAN3 | - |
| R3‑162643 | X2AP Support for Inter-eNB Mobility without WT Change | Ericsson, Nokia, Alcatel-Lucent Shanghai Bell, Intel, Ruckus, Qualcomm | - |
| R3‑162644 | LS on non-anchor paging support for NB-IoT enhancements (to: RAN2; cc: -; contact: Huawei) | RAN3 | - |
| R3‑162645 | Correction on the reinitiating waiting time in Xw | HUAWEI TECHNOLOGIES Co. Ltd. | - |
| R3‑162646 | Response LS to R2-165969 = R3-162281 on the Make Before Break solution (to: RAN2; cc: RAN1, RAN4; contact: ZTE) | RAN3 | - |
| R3‑162647 | Next Generation Shared RAN | Ericsson | - |
| R3‑162648 | RAN3#93 meeting report | MCC | - |
page generated from database: 2024-04-22 07:58:53