3GPP TDocs (written contributions) at meeting
Meeting: R3-101b - 2018-10-08 to 2018-10-12, Chengdu
meeting id: R3-101b (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑185340 | RAN3-101Bis meeting Agenda | Ericsson (Chairman) | imported from 3GU |
| R3‑185341 | RAN3-101 meeting report | ETSI | imported from 3GU |
| R3‑185342 | Baseline CR for TS 38.401 | NEC | imported from 3GU |
| R3‑185343 | Withdrawn - Baseline CR for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185344 | Withdrawn - Baseline CR for TS 38.411 | LG Electronics | imported from 3GU |
| R3‑185345 | Withdrawn - Baseline CR for TS 38.412 | NTT DOCOMO INC | imported from 3GU |
| R3‑185346 | Baseline CR for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185347 | Withdrawn - Baseline CR for TS 38.414 | ZTE | imported from 3GU |
| R3‑185348 | Withdrawn - Baseline CR for TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185349 | Withdrawn - Baseline CR for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
| R3‑185350 | Withdrawn - Baseline CR for TS 38.421 | CATT | imported from 3GU |
| R3‑185351 | Withdrawn - Baseline CR for TS 38.422 | NTT DOCOMO INC | imported from 3GU |
| R3‑185352 | Baseline CR for TS 38.423 | Ericsson LM | imported from 3GU |
| R3‑185353 | Withdrawn - Baseline CR for TS 38.424 | Mitsubishi Electric | imported from 3GU |
| R3‑185354 | Withdrawn - Baseline CR for TS 38.425 | Samsung | imported from 3GU |
| R3‑185355 | Withdrawn - Baseline CR for TS 38.460 | Nokia (Rapporteur) | imported from 3GU |
| R3‑185356 | Withdrawn - Baseline CR for TS 38.461 | Intel Mobile Communications | imported from 3GU |
| R3‑185357 | Withdrawn - Baseline CR for TS 38.462 | Huawei | imported from 3GU |
| R3‑185358 | Baseline CR for TS 38.463 | Ericsson | imported from 3GU |
| R3‑185359 | Response LS on inclusion of selected PLMN into the Complete message | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185360 | (TP for NR BL CR for TS 38.300): Handling end marker in inter-system HO | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185361 | (TP for NR BL CR for TS 38.300): TP for option 3 in inter-system | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185362 | (TP for NR BL CR for TS 38.413): TP for option 3 in inter-system | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185363 | LS on handling of data forwarding and end markers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185364 | (TP for NR BL CR for TS 38.413): Correction of NSSAI for paging. | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185365 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185366 | (TP for NR BL CR for TS 38.463): Unavailability of PLMNs and slices | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185367 | Conclusion on Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185368 | (TP for NR BL CR for TS 38.423): Source TEID reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185369 | (TP for NR BL CR for TS 38.463): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185370 | (TP for NR BL CR for TS 38.413): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185371 | (TP for NR BL CR for TS 38.413): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185372 | (TP for NR BL CR for TS 38.463): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185373 | (TP for NR BL CR for TS 38.413): Correction of RAN Paging Priority | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185374 | (TP for NR BL CR for TS 38.300): Handling of Reset in inactive state | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185375 | (TP for NR BL CR for TS 38.413): Correction of inactive transitions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185376 | (TP for NR BL CR for TS 38.423): Correction of integrity failure in inactive state | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185377 | (TP for NR BL CR for TS 38.401): Correction of Security and multiple CU UPs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185378 | (TP for NR BL CR for TS 38.413): Correction of AMBR Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185379 | (TP for NR BL CR for TS 38.423): Correction of AMBR Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185380 | Correction of AMBR Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185381 | (TP for NR BL CR for TS 38.463): Correction of AMBR Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185382 | (TP for NR BL CR for TS 38.413): Correction of NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185383 | (TP for NR BL CR for TS 38.413): Correction of Paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185384 | (TP for NR BL CR for TS 38.413): Correction of Handover Resource Allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185385 | LS on rejected PDU sessions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185386 | (TP for NR BL CR for TS 38.413): Correction of Path Switch Request | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185387 | (TP for NR BL CR for TS 38.413): Correction of IMS Voice Fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185388 | (TP for NR BL CR for TS 38.300): Correction of Emergency fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185389 | (TP for NR BL CR for TS 38.413): Correction of handover failure to 4g | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185390 | (TP for NR BL CR for TS 37.340): Correction of data volume reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185391 | RNA update corrections | Google Inc. | imported from 3GU |
| R3‑185392 | RNA correction | Google Inc. | imported from 3GU |
| R3‑185393 | TP for Miscellaneous corrections in 38.401 | Google Inc. | imported from 3GU |
| R3‑185394 | RRC msg alignment in Retrieve UE Context | Google Inc. | imported from 3GU |
| R3‑185395 | (TP for NR BL CR for TS 38.423) UE Context Release to S-Node | Google Inc. | imported from 3GU |
| R3‑185396 | TP for TS 38.413 BL CR: Resolution of editor’s notes | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185397 | TP for TS 38.413 BL CR: Uplink/Downlink RAN Status Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185398 | TP for TS 38.413 BL CR: Encoding of RRC Establishment Cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185399 | TP for TS 38.413 BL CR: Warning Area Coordinates | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185400 | Consideration on “CP alternatives for architecture 1a” with NSA operation | KDDI Corporation | imported from 3GU |
| R3‑185401 | Considerations on remaining “FFS” in the TR 38.874 | KDDI Corporation | imported from 3GU |
| R3‑185402 | Use of Multi-connectivity for Load Balancing and Reliability in IAB | OMESH Networks | imported from 3GU |
| R3‑185403 | Removal of the FFS on IAB Routing update procedure | KDDI Corporation | imported from 3GU |
| R3‑185404 | On Reliability and Load Balancing in IAB | OMESH Networks | imported from 3GU |
| R3‑185405 | Baseline CR for TS 38.300 | Nokia | imported from 3GU |
| R3‑185406 | Architecture options for NTN | THALES | imported from 3GU |
| R3‑185407 | On including S-NSSIA in NG paging message | China Telecommunications | imported from 3GU |
| R3‑185408 | On inter-system data forwarding and end marker handling | China Telecommunications | imported from 3GU |
| R3‑185409 | Further Discussion on NTN Architecture Issues | ZTE | imported from 3GU |
| R3‑185410 | (TP for TR 38.821) Refinement of NTN Architectures | ZTE | imported from 3GU |
| R3‑185411 | Further Considerations on Multi-Hop Scenarios in NTN | ZTE | imported from 3GU |
| R3‑185412 | (TP for TR 38.821) NTN Multi-Hop Related Architectures | ZTE | imported from 3GU |
| R3‑185413 | (TP for NR BL CR for TS 38.413) Clarification of RQA Behaviors | ZTE | imported from 3GU |
| R3‑185414 | (TP for NR BL CR for TS 38.413) Alignment of NG Setup with S1 Setup Handling | ZTE | imported from 3GU |
| R3‑185415 | (TP for NR BL CR for TS 38.300) Further Stage2 Corrections of NR QoS Parameters | ZTE | imported from 3GU |
| R3‑185416 | (TP for NR BL CR for TS 38.300) Refinement of RRC_INACTIVE Stage2 Mobility Behaviors | ZTE | imported from 3GU |
| R3‑185417 | (TP for NR BL CR for TS 38.300) Stage2 Introduction of E-UTRA - NR Cell Resource Coordination Procedure | ZTE | imported from 3GU |
| R3‑185418 | Baseline CR for TS 37.340 | ZTE Corporation | imported from 3GU |
| R3‑185419 | Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑185420 | (TP for NR BL CR for TS 38.423) Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑185421 | (TP for NR BL CR for TS 38.423) Correction of PDU Session Aggregate Maximum Bit Rate | ZTE | imported from 3GU |
| R3‑185422 | (TP for NR BL CR for TS 38.413) Clarification of Aggregate Maximum Integrity Protected Data Rate | ZTE | imported from 3GU |
| R3‑185423 | NB-IoT TDD correction | Huawei | imported from 3GU |
| R3‑185424 | NB-IoT Paging eDRX Cycle handling issue | Huawei | imported from 3GU |
| R3‑185425 | Correction of NB-IoT Paging eDRX Cycle handling | Huawei | imported from 3GU |
| R3‑185426 | Correction of NB-IoT Paging eDRX Cycle handling | Huawei | imported from 3GU |
| R3‑185427 | Correction of NB-IoT Paging eDRX Cycle handling | Huawei | imported from 3GU |
| R3‑185428 | Rel-16 additional enhancements for NB-IoT WI work plan | Huawei | imported from 3GU |
| R3‑185429 | Consideration on MME supporting RAT Type | Huawei, CMCC, China Unicom | imported from 3GU |
| R3‑185430 | Introduction of MME supporting RAT | Huawei, CMCC, China Unicom | imported from 3GU |
| R3‑185431 | Introduction of MME supporting RAT | Huawei, CMCC, China Unicom | imported from 3GU |
| R3‑185432 | Introduction of MME supporting RAT | Huawei, CMCC, China Unicom | imported from 3GU |
| R3‑185433 | Consideration on Inter UE QoS in CP Relocation | Huawei | imported from 3GU |
| R3‑185434 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
| R3‑185435 | W1 interface User Plane Protocol | Huawei | imported from 3GU |
| R3‑185436 | Supporting of W1 user Plane Protocol | Huawei | imported from 3GU |
| R3‑185437 | Disaggregated ng-eNB connecting to 5GC | Huawei | imported from 3GU |
| R3‑185438 | Consideration on eNB-CU UE W1AP ID and eNB-DU UE W1AP ID | Huawei | imported from 3GU |
| R3‑185439 | Reply LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | 3GPP CT4, Vodafone | imported from 3GU |
| R3‑185440 | LS on Joint ETSI - OSA Workshop: Open Implementations & Standardization | ETSI, ETSI | imported from 3GU |
| R3‑185441 | LS on NR-RIM frameworks | 3GPP RAN1, China Mobile | imported from 3GU |
| R3‑185442 | LS on new UE features list for NR | 3GPP RAN1, AT&T | imported from 3GU |
| R3‑185443 | LS to RAN3 on data forwarding handling for intra-system HO | 3GPP RAN2, China Mobile | imported from 3GU |
| R3‑185444 | LS to RAN3 on asymmetric mapping for UL and DL QoS flows | 3GPP RAN2, LGE | imported from 3GU |
| R3‑185445 | Reply LS on Issues with AS Release Assistance Indicator | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑185446 | LS on RLC mode reconfiguration | 3GPP RAN2, ZTE | imported from 3GU |
| R3‑185447 | Ls on NR cell type identification | 3GPP RAN2, Vivo | imported from 3GU |
| R3‑185448 | LS on inclusion of selected PLMN into the complete message | 3GPP RAN2, Samsung | imported from 3GU |
| R3‑185449 | Reply LS on Location Service exposure to NG-RAN | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑185450 | LS on CN type indication for Redirection from NR to E-UTRA | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑185451 | LS on UE feature list for NR | 3GPP RAN4, NTT Docomo | imported from 3GU |
| R3‑185452 | Reply LS on RAN2 progress on ANR | 3GPP RAN4, Vivo | imported from 3GU |
| R3‑185453 | LS on UE feature list for LTE | 3GPP RAN4, NTT Docomo | imported from 3GU |
| R3‑185454 | LS on Slice related Data Analytics | 3GPP SA2, China Mobile | imported from 3GU |
| R3‑185455 | LS on TSN integration in the 5G System | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑185456 | Reply LS on Bluetooth/WLAN measurement collection in MDT | 3GPP SA3, Ericsson | imported from 3GU |
| R3‑185457 | LS on Using same counter in EDCE5 | 3GPP SA3, Ericsson | imported from 3GU |
| R3‑185458 | Reply LS on inactive security | 3GPP SA3, Ericsson | imported from 3GU |
| R3‑185459 | LS on indications for key synchronization | 3GPP SA3, ZTE | imported from 3GU |
| R3‑185460 | LS reply to RAN 3 on L2 measurement | 3GPP SA5, Ericsson | imported from 3GU |
| R3‑185461 | LS reply on L2 measurement | 3GPP SA5, Ericsson | imported from 3GU |
| R3‑185462 | TP for TR 38.874 on recovery procedures for different IAB failure scenarios | Samsung R&D Institute UK | imported from 3GU |
| R3‑185463 | Discussion on further downselection of remaining IAB architecture options | Samsung R&D Institute UK | imported from 3GU |
| R3‑185464 | (TP for NR BL CR for TS 38.423) Clarification of Aggregate Maximum Integrity Protected Data Rate | ZTE | imported from 3GU |
| R3‑185465 | (TP for NR BL CR for TS 38.401) correction to UE initial access on NG-RAN | ETRI | imported from 3GU |
| R3‑185466 | (TP for NR BL CR for TS 38.413) Further Cleanups due to AMF Transparency | ZTE | imported from 3GU |
| R3‑185467 | (TP for NR BL CR for TS 38.413) Correction of INITIAL CONTEXT SETUP FAILURE | ZTE | imported from 3GU |
| R3‑185468 | (TP for NR BL CR for TS 38.413) Correction of UE CONTEXT RELEASE COMPLETE | ZTE | imported from 3GU |
| R3‑185469 | Initial consideration on RIM | ZTE | imported from 3GU |
| R3‑185470 | (TP for NR BL CR for TS 38.423) Correction of AOI in XnAP | ZTE | imported from 3GU |
| R3‑185471 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Setup procedure | ZTE | imported from 3GU |
| R3‑185472 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Setup procedure | ZTE | imported from 3GU |
| R3‑185473 | (TP for NR BL CR for TS 38.413) Correction of AMF Pointer | ZTE | imported from 3GU |
| R3‑185474 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Modify procedure | ZTE | imported from 3GU |
| R3‑185475 | (TP for NR BL CR for TS 38.413) Correction of RAN Paging Priority | ZTE | imported from 3GU |
| R3‑185476 | (TP for NR BL CR for TS 38.413) Correction of RAN Paging Priority | ZTE | imported from 3GU |
| R3‑185477 | (TP for NR BL CR for TS 38.413) Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
| R3‑185478 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Modify Inidication procedure | ZTE | imported from 3GU |
| R3‑185479 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Modify Inidication procedure | ZTE | imported from 3GU |
| R3‑185480 | (TP for NR BL CR for TS 38.413) Correction of IMS Voice fallback over NGAP Aligning to SA2 | ZTE | imported from 3GU |
| R3‑185481 | (TP for NR BL CR for TS 38.423) Usage Alignment of Index to RFSP info for XnAP | ZTE | imported from 3GU |
| R3‑185482 | (TP for NR BL CR for TS 38.413) Correction of UE Radio Capability etc | ZTE | imported from 3GU |
| R3‑185483 | Further Discussion on RAN Information Management | ZTE | imported from 3GU |
| R3‑185484 | (TP for NR BL CR for TS 38.413) Introduction of NR RAN Information Management Function | ZTE | imported from 3GU |
| R3‑185485 | CR for LS on RLC mode reconfiguration in 36.423 | ZTE | imported from 3GU |
| R3‑185486 | (TP for BL CR for TS 38.423): Corrections on XnAP | ZTE | imported from 3GU |
| R3‑185487 | (TP for BL CR for TS 38.423): Modification on CA based PDCP duplication in SN terminated SN modification | ZTE | imported from 3GU |
| R3‑185488 | (TP for BL CR for TS 37.340): Modification on CA based PDCP duplication in SN terminated SN modification procedure | ZTE | imported from 3GU |
| R3‑185489 | (TP for BL CR for TS 38.423): Consideration on DRB ID allocation for SN terminated bearer | ZTE | imported from 3GU |
| R3‑185490 | (TP for BL CR for TS 38.423): Consideration on DL TNL address allocation for SN terminated bearer | ZTE | imported from 3GU |
| R3‑185491 | (TP for BL CR for TS 37.340): Consideration on DL TNL address allocation for SN terminated bearer | ZTE | imported from 3GU |
| R3‑185492 | Introduction of NR-DC | ZTE | imported from 3GU |
| R3‑185493 | (TP for BL CR for TS 38.423): Correction on SN STATUS TRANSFER | ZTE | imported from 3GU |
| R3‑185494 | The Redundant CRs for delivering SS Block SCS over EN-DC X2 & F1 | ZTE | imported from 3GU |
| R3‑185495 | Considerations on the need for multiple SCTP associations in X2 and Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185496 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185497 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185498 | (TP for BL CR for TS 38.423): Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185499 | (TP for BL CR for TS 38.422): Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185500 | Enabling multiple SCTP associations for X2 and Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185501 | Addition of EN-DC description | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185502 | (TP for BL CR for TS 38.423): Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185503 | Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185504 | [DRAFT] Response LS on RLC mode reconfiguration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185505 | (TP for BL CR for TS 38.423): Solution for DRB ID allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185506 | (TP for BL CR for TS 38.423): Enabling signalling of the RLC Status | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185507 | (TP for BL CR for TS 38.423): Addition of missing Cause value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185508 | Clarification of the NR UP initialisation for RLC (re)establishment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185509 | (TP for NR BL CR for TS 38.423) Cell information related to wideband carrier | ZTE | imported from 3GU |
| R3‑185510 | Issues to be considered on NR V2X | LG Electronics | imported from 3GU |
| R3‑185511 | UE level resource coordination for MR-DC connected to 5GC | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
| R3‑185512 | Inter-system Handover between SA and NSA | Qualcomm Incorporated | imported from 3GU |
| R3‑185513 | MN DL TNL Information Delivery for Flow Level Offload | Qualcomm Incorporated | imported from 3GU |
| R3‑185514 | Remote Interference Detection | Qualcomm Incorporated | imported from 3GU |
| R3‑185515 | Configuration and coordination for RS transmission | Qualcomm Incorporated | imported from 3GU |
| R3‑185516 | Remote coordination by backhaul (framework #2) | Qualcomm Incorporated | imported from 3GU |
| R3‑185517 | Functionality of RAN-Centric Data Collection | Qualcomm Incorporated | imported from 3GU |
| R3‑185518 | TR 38874 v050 | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
| R3‑185519 | IAB work plan | Qualcomm Incorporated, Samsung, AT&T, KDDI (Rapporteurs) | imported from 3GU |
| R3‑185520 | Comparison of IAB architecture groups | Qualcomm Incorporated | imported from 3GU |
| R3‑185521 | Comparison of IAB architectures 1a and 1b | Qualcomm Incorporated | imported from 3GU |
| R3‑185522 | IAB backhaul RLF recovery for arch 1a | Qualcomm Incorporated, Ericsson, AT&T | imported from 3GU |
| R3‑185523 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑185524 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑185525 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑185526 | Enforcement of UE’s maximum bit rate for Integrity Protection | Qualcomm Incorporated | imported from 3GU |
| R3‑185527 | Mobility restrictions and support for different PLMNs in E-UTRAN and NG-RAN | Qualcomm Incorporated | imported from 3GU |
| R3‑185528 | Rapporteur’s CR for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
| R3‑185529 | (TP for NR BL CR for TS 38.423) Activity Notification Request over Xn | Qualcomm Incorporated | imported from 3GU |
| R3‑185530 | (TP for NR BL CR for TS 38.423) Alignment of Cell Activation Functionality over Xn and F1 | Qualcomm Incorporated, Huawei | imported from 3GU |
| R3‑185531 | (TP for NR BL CR for TS 38.300) Further refinement of the stage 2 RRC-Inactive Mobility section | Qualcomm Incorporated | imported from 3GU |
| R3‑185532 | RRC Delivery Reporting over F1 | Qualcomm Incorporated | imported from 3GU |
| R3‑185533 | Extending RRC message delivery indication to F1AP | Qualcomm Incorporated | imported from 3GU |
| R3‑185534 | Comparison of architecture 1a and 1b | ZTE Corporation | imported from 3GU |
| R3‑185535 | Comparison of IAB architecture group 1 and architecture group 2 | ZTE Corporation | imported from 3GU |
| R3‑185536 | Control plane signaling delivery in NSA deployment | ZTE Corporation | imported from 3GU |
| R3‑185537 | Discussion on backhaul bearer setup in IAB network | ZTE Corporation | imported from 3GU |
| R3‑185538 | Discussion on IAB node discovery and selection | ZTE Corporation | imported from 3GU |
| R3‑185539 | Discussion on backhaul link failure and recovery | ZTE Corporation | imported from 3GU |
| R3‑185540 | Initial consideration on NR V2X | ZTE Corporation | imported from 3GU |
| R3‑185541 | Consideration on RAT Selection in NR V2X | ZTE Corporation | imported from 3GU |
| R3‑185542 | Rapporteur’s updates for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185543 | Rapporteur’CR for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185544 | Rapporteur’s updates for TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185545 | Rapporteur’s CR for TS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185546 | NTN - Min altitude for LEO based scenario | THALES | imported from 3GU |
| R3‑185547 | On Resource Efficient PDCP Duplication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185548 | TP for TS 38.423 BL CR: Mandatory S-NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185549 | Work Plan for NR Industrial IoT SI | Nokia (Rapporteur) | imported from 3GU |
| R3‑185550 | TR 38.825 skeleton (for information) | Nokia (Rapporteur) | imported from 3GU |
| R3‑185551 | NSA support for IAB | AT&T | imported from 3GU |
| R3‑185552 | Performance results for hop-by-hop vs. end-to-end RLC ARQ | AT&T | imported from 3GU |
| R3‑185553 | New MDT requirements for NR | AT&T | imported from 3GU |
| R3‑185554 | Inter system data forwarding | CATT | imported from 3GU |
| R3‑185555 | PDCP Duplication with more than 2 copies | CATT | imported from 3GU |
| R3‑185556 | Higher Layer Multi-Connectivity | CATT | imported from 3GU |
| R3‑185557 | Initial consideration on TSN | CATT | imported from 3GU |
| R3‑185558 | Discussion on RAT/Interface selection | CATT | imported from 3GU |
| R3‑185559 | Discussion on NR eV2X | CATT | imported from 3GU |
| R3‑185560 | Discussion on IAB failure | CATT | imported from 3GU |
| R3‑185561 | (TP for BL CR for TS 38.463) Correction on data forwarding address | CATT | imported from 3GU |
| R3‑185562 | Clarification on gNB-CU Configuration Update Procedure | ZTE Corporation | imported from 3GU |
| R3‑185563 | Clarification on gNB-CU Configuration Update Procedure for TS38.470 | ZTE Corporation | imported from 3GU |
| R3‑185564 | Clarification on gNB-CU Configuration Update Procedure for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑185565 | (TP for NR BL CR for TS 38.413) Clarification on AMF Status Indication | ZTE Corporation | imported from 3GU |
| R3‑185566 | Energy Savings in R15 | ZTE Corporation, China Unicom, China Telecom, CMCC | imported from 3GU |
| R3‑185567 | (TP for NR BL CR for TS 38.423) Energy Saving Support over Xn Interface | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑185568 | Energy Saving Support over F1 Interface | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑185569 | Energy Saving Support over E1 Interface | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑185570 | (TP for NR BL CR for TS 38.463) Energy Saving Support over E1 Interface | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑185571 | (TP for NR BL CR for TS 38.300) Energy Saving Support for NR in R15 | ZTE Corporation, China Unicom | imported from 3GU |
| R3‑185572 | Clarification on SMTC Configuration over F1 | ZTE Corporation | imported from 3GU |
| R3‑185573 | Corrections on RLC reestablishment indication for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑185574 | Corrections on CA duplication for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑185575 | Further discussion on primary path of CA-based SRB duplication | ZTE Corporation | imported from 3GU |
| R3‑185576 | Corrections on SRB duplication for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑185577 | Initial consideration on URLLC duplication enhancement | ZTE Corporation | imported from 3GU |
| R3‑185578 | Initial consideration on RAN-centric Data Collection and Utilization for LTE and NR | ZTE Corporation | imported from 3GU |
| R3‑185579 | (TP for NR BL CR for TS 38.413) Correction on Overload Control | ZTE Corporation | imported from 3GU |
| R3‑185580 | (TP for NR BL CR for TS 38.463) Cause IE in DRB To Modify List of Bearer Context Modification Required | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185581 | (TP for NR BL CR for TS 38.413) Overload Control for UAC | ZTE Corporation, China Unicom, NTT Docomo | imported from 3GU |
| R3‑185582 | More consideration for EN-DC TNL address discovery | ZTE Corporation | imported from 3GU |
| R3‑185583 | (TP for NR BL CR for TS36.300) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
| R3‑185584 | (TP for NR BL CR for TS 38.463) Processing Capacity Indication for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185585 | EN-DC TNL address discovery solution 3 for TS36.413 | ZTE Corporation | imported from 3GU |
| R3‑185586 | (TP for NR BL CR for TS38.423) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
| R3‑185587 | (TP for NR BL CR for TS37.340) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
| R3‑185588 | Inter MME EN-DC TNL Address discovery | ZTE Corporation | imported from 3GU |
| R3‑185589 | Processing Capacity Indication for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185590 | (TP for NR BL CR for TS 38.463) UE Identification and Trace correlation over E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185591 | Further Discussion on PWS System Information | ZTE Corporation | imported from 3GU |
| R3‑185592 | Discussion on Bearer Type Change L2 Handling Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185593 | CR to TS38.473 on PWS System Information | ZTE Corporation | imported from 3GU |
| R3‑185594 | (TP for NR BL CR for TS38.463) Discussion on UP capacity exchange over E1 | ZTE Corporation | imported from 3GU |
| R3‑185595 | Bearer Type Change L2 Handling Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185596 | Further discussion on PLMN specific info in NR Served Cell Information | ZTE Corporation | imported from 3GU |
| R3‑185597 | Update on NR Served Cell Information for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑185598 | (TP for BL CR for TS38.423)Update on NR Served Cell Information | ZTE Corporation | imported from 3GU |
| R3‑185599 | Update on NR Served Cell Information for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑185600 | (TP for BL CR for TS 38.463) Support of maximum bit rate for Integrity Protection for E1 interface | ZTE Corporation | imported from 3GU |
| R3‑185601 | E1 remaining issues | ZTE Corporation | imported from 3GU |
| R3‑185602 | Security issue on multiple PDU sessions served by different UPs | ZTE Corporation | imported from 3GU |
| R3‑185603 | Issues on X2&Xn AP Services | ZTE Corporation | imported from 3GU |
| R3‑185604 | Corrections on X2AP services for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑185605 | (TP for NR BL CR for TS38.423) Corrections on XnAP services for TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑185606 | Correction of paging for F1AP | ZTE Corporation | imported from 3GU |
| R3‑185607 | (TP for NR BL CR for TS 38.413) Correction of paging for NGAP | ZTE Corporation | imported from 3GU |
| R3‑185608 | (TP for NR BL CR for TS 38.300) Correction of RRC Inactive Assistant Information | ZTE Corporation | imported from 3GU |
| R3‑185609 | Parameters in NTN reference scenarios | ZTE Corporation | imported from 3GU |
| R3‑185610 | Discussion on Tracking Area Management in NTN | ZTE Corporation | imported from 3GU |
| R3‑185611 | Discussion on Network Identities in NTN | ZTE Corporation | imported from 3GU |
| R3‑185612 | (TP for BL CR for 38.423): Data forwarding for RRC reestablishment UE with context fetch | Huawei | imported from 3GU |
| R3‑185613 | (TP for BL CR for TS 38.423): Correction to UE Context Release | Huawei | imported from 3GU |
| R3‑185614 | (TP for BL CR for TS 38.423): Correction to Retrieve UE Context Request | Huawei | imported from 3GU |
| R3‑185615 | (TP for BL CR for TS 38.300): RNA update procedure update | Huawei | imported from 3GU |
| R3‑185616 | (TP for BL CR for TS 38.423): CSI-RS configuration transfer over Xn | Huawei | imported from 3GU |
| R3‑185617 | [DRAFT] LS on CSI-RS configuration transfer over Xn (Huawei) | Huawei | imported from 3GU |
| R3‑185618 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑185619 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑185620 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑185621 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑185622 | (TP for BL CR for TS 38.300): ANR stage 2 completion | Huawei | imported from 3GU |
| R3‑185623 | (TP for BL CR for TS 38.300): Stage 2 text correction for RRC Inactive Assistance Information | Huawei | imported from 3GU |
| R3‑185624 | L2 measurements | Huawei | imported from 3GU |
| R3‑185625 | [Draft] Reply LS to SA5 on L2 measurements | Huawei | imported from 3GU |
| R3‑185626 | (TP for BL CR for 38.423): Removal of SSB SCS from Served Cell Information NR | Huawei, NEC | imported from 3GU |
| R3‑185627 | Discussion on Bandwidth Part (BWP) Information Procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185628 | F1 Bandwidth Part (BWP) Information Procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185629 | Discussion on RL failure handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185630 | Clarification of RL failure handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185631 | Discussion on Clarification of cell management over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185632 | Clarification of cell management over F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185633 | Discussion on Downlink Data Delivery Status Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185634 | Downlink Data Delivery Status Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185635 | Discussion on DL RRC Message Transfer Delivery Status | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185636 | DL RRC Message Transfer Delivery Status | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185637 | Discussion on Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185638 | Clarification of Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185639 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185640 | Discussion on PDCP SN length for EN-DC | CATT | imported from 3GU |
| R3‑185641 | Correction on PDCP SN length for EN-DC | CATT | imported from 3GU |
| R3‑185642 | Support of CA based PDCP duplication on X2 | CATT | imported from 3GU |
| R3‑185643 | (TP for NR BL CR for TS 37.340) Correction on PCI confusion | CATT | imported from 3GU |
| R3‑185644 | (TP for BL CR for TS 38.423) PDCP SN length for MR-DC connecting with 5GC | CATT | imported from 3GU |
| R3‑185645 | (TP for BL CR for TS 38.423) Introduction of Xn-U TEID in S-Node ^^Modification Required message | CATT | imported from 3GU |
| R3‑185646 | Initial consideration on SON for NR and LTE V2X | CATT | imported from 3GU |
| R3‑185647 | Discussion on security for multi-CU-UP connection | CATT | imported from 3GU |
| R3‑185648 | Initial consideration on MDT for RAN-centric Data Collection and Utilization | CATT | imported from 3GU |
| R3‑185649 | Discussion on acess control related information transfer over F1 | CATT | imported from 3GU |
| R3‑185650 | Support of acess control related information transfer over F1 | CATT | imported from 3GU |
| R3‑185651 | Discussion on system information update for active UE | CATT | imported from 3GU |
| R3‑185652 | Support of system information update for active UE | CATT | imported from 3GU |
| R3‑185653 | Discussion on LCID for primary path | CATT | imported from 3GU |
| R3‑185654 | [Draft] LS on LCID for primary path | CATT | imported from 3GU |
| R3‑185655 | F1 Load Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185656 | Overload indication for X2 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185657 | CR on Introduction of overload indication over X2 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185658 | (TP for BL CR for TS 37.340)further consideration on Start end time stamp for data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185659 | CR on alingment of terminology for eNB or MeNB | NTT DOCOMO, INC, Ericsson | imported from 3GU |
| R3‑185660 | (TP for BL CR for TS 38.401) Cell State handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185661 | CR on cell state handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185662 | Categorization of SIB | NTT DOCOMO, INC, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185663 | CR on indication of parameters in SI | NTT DOCOMO, INC, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185664 | Prioritization between E-UTRAN and NG-RAN for W1 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185665 | IP Version of Transport Layer Address | Huawei | imported from 3GU |
| R3‑185666 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑185667 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑185668 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑185669 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑185670 | (TP for NR BL CR for TS 38.413): Support of RAN initiated multiple SCTP | Huawei | imported from 3GU |
| R3‑185671 | (TP for NR BL CR for TS 38.413): Corrections on RAN/AMF Configuration Update | Huawei | imported from 3GU |
| R3‑185672 | (TP for NR BL CR for TS 38.423): Corrections on NG-RAN node Configuration Update | Huawei | imported from 3GU |
| R3‑185673 | Correction on gNB-CU/DU Configuration Update | Huawei | imported from 3GU |
| R3‑185674 | (TP for NR BL CR for TS 38.463): Correction on gNB-CU-UP/CP Configuration Update | Huawei | imported from 3GU |
| R3‑185675 | (TP for NR BL CR for TS 38.423): Correction of dedicated PDU Session transport resources | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185676 | (TP for NR BL CR for TS 38.300): Correction on intra-system Data forwarding | Huawei | imported from 3GU |
| R3‑185677 | Agreements for MR-DC with 5GC in RAN2 | ZTE | imported from 3GU |
| R3‑185678 | Correction on Handover Type | Huawei | imported from 3GU |
| R3‑185679 | Use cases for RAN centric-data utilization | NTT DOCOMO, INC. | imported from 3GU |
| R3‑185680 | The scenarios and general principles of RIM solutions | Ericsson | imported from 3GU |
| R3‑185681 | gNB identification and grouping in RIM scenarios | Ericsson | imported from 3GU |
| R3‑185682 | The RIM solution frameworks | Ericsson | imported from 3GU |
| R3‑185683 | [Draft] Reply LS on RIM solution frameworks | Ericsson | imported from 3GU |
| R3‑185684 | IAB solution down-selection criteria | Intel Corporation | imported from 3GU |
| R3‑185685 | IAB flow control | Intel Corporation | imported from 3GU |
| R3‑185686 | IAB route adaptation upon RLF | Intel Corporation | imported from 3GU |
| R3‑185687 | DraftCR on 38.300 for ANR | vivo | imported from 3GU |
| R3‑185688 | (TP for NR BL CR for TS 38.413): Complete of Uplink/Downlink RAN Status Transfer | Huawei | imported from 3GU |
| R3‑185689 | (TP for NR BL CR for TS 38.423): Complete of SN Status Transfer | Huawei | imported from 3GU |
| R3‑185690 | Comparison of Arch 1a alternatives for user plane | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185691 | (TP for NR BL CR for TS 38.413): Support of paging for ng-eNB | Huawei | imported from 3GU |
| R3‑185692 | Comparison of Arch 1a alternatives for C-plane | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185693 | IAB Architecture comparison | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185694 | (TP for NR BL CR for TS 38.413) Correction on UE Radio Capability | Huawei | imported from 3GU |
| R3‑185695 | QoS for Architecture 2a | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185696 | IAB Node Integration Option 2a | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185697 | Discussion on Inter-CU Topology Adaptation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185698 | IAB Routing for Architecture 2a | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185699 | NTN Architecture options | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185700 | Paging issues in NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185701 | (TP for BL CR for TS 38.413): Correction on Overload Start | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185702 | 5G Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑185703 | (TP for BL CR for TS 38.401): 5G Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑185704 | Further discussion on NTN architecture | Huawei | imported from 3GU |
| R3‑185705 | Discussion on Handling of Network Identities in NTN | Huawei | imported from 3GU |
| R3‑185706 | The issue of paging in NTN | Huawei | imported from 3GU |
| R3‑185707 | Discussion on the mobility issues in NTN | Huawei | imported from 3GU |
| R3‑185708 | BWP impact on F1 interface due to System Information updating | NEC | imported from 3GU |
| R3‑185709 | BWP impact on F1 interface due to System Information updating | NEC | imported from 3GU |
| R3‑185710 | (TP for NR BL CR for TS 38.401): Cell State in gNB-CU and gNB-DU | NEC | imported from 3GU |
| R3‑185711 | Retransmission status in UP | NEC | imported from 3GU |
| R3‑185712 | Correstion of Retransmission in UP | NEC | imported from 3GU |
| R3‑185713 | SgNB Initiated SN Modification procedure for Measurement Gap | NEC | imported from 3GU |
| R3‑185714 | Correction of SgNB Initiated SN Modification procedure for Measurement Gap | NEC | imported from 3GU |
| R3‑185715 | (TP for NR BL CR for TS 38.423): Adding semantics description for I-RNTI | NEC, Huawei | imported from 3GU |
| R3‑185716 | Support for Advanced V2X Use Cases | Huawei | imported from 3GU |
| R3‑185717 | V2X RAT and Interface Selection | Huawei | imported from 3GU |
| R3‑185718 | (TP for BL CR for TS 38.413) Clarification of AMF overload | Huawei | imported from 3GU |
| R3‑185719 | (TP for BL CR for TS 38.413) S-NSSAI in paging | Huawei | imported from 3GU |
| R3‑185720 | [draft] Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Huawei | imported from 3GU |
| R3‑185721 | Alignment with stage 3 | Huawei | imported from 3GU |
| R3‑185722 | Corrections to General aspects | Huawei | imported from 3GU |
| R3‑185723 | ASN.1 corrections on NRNeighbour-Information IE and NRFreqInfo IE | Samsung | imported from 3GU |
| R3‑185724 | (TP for BL CR for TS 38.423) Text Proposal for DC messages on SN initiated procedures | Samsung | imported from 3GU |
| R3‑185725 | (TP for BL CR for TS 38.423) Text Proposal for DC messages on MN initiated procedures | Samsung | imported from 3GU |
| R3‑185726 | Use case for Mobility Robustness Optimization | Samsung | imported from 3GU |
| R3‑185727 | Use case for Minimization of Drive Testing | Samsung | imported from 3GU |
| R3‑185728 | Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., Intel Corporation, ZTE, CMCC, Verizon, LG Electronics Inc., CATT | imported from 3GU |
| R3‑185729 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung, KT Corp., Intel Corporation, ZTE, CMCC, Verizon, LG Electronics Inc., CATT | imported from 3GU |
| R3‑185730 | (TP for NR BL CR for TS 38.423) Correction of Semantics description on Integrity protection IE in RETRIEVE UE CONTEXT REQUEST message | Samsung | imported from 3GU |
| R3‑185731 | Enhancement to CP Alt. 2 for Architecture 1a | Samsung | imported from 3GU |
| R3‑185732 | F1AP mapping options for IAB | Samsung | imported from 3GU |
| R3‑185733 | Control plane data mapping for Architecture 1a | Samsung | imported from 3GU |
| R3‑185734 | CR for correction on Initial UL RRC message transfer | Samsung | imported from 3GU |
| R3‑185735 | (TP for BL CR for TS38.463): CU-UP DL transmission resume | Samsung | imported from 3GU |
| R3‑185736 | Discussion on MBMS Service for NR V2X | LG Electronics | imported from 3GU |
| R3‑185737 | RAN3 Work Plan on NR V2X SI | LG Electronics, Huawei | imported from 3GU |
| R3‑185738 | (TP for NR BL CR for TS 38.423) FFS/Issues on SN triggered modification procedures | LG Electronics | imported from 3GU |
| R3‑185739 | Discussion on common interface in case of RAN sharing | Huawei | imported from 3GU |
| R3‑185740 | (TP for NR BL CR for TS 38.423) on the clarification to RAN sharing and RRC re-establishment | Huawei | imported from 3GU |
| R3‑185741 | (TP for NR BL CR for TS 38.423): on common interface in case of RAN sharing | Huawei | imported from 3GU |
| R3‑185742 | CR to 38.473 on the clarification to RAN sharing | Huawei | imported from 3GU |
| R3‑185743 | CR to 36.423 on common interface in case of RAN sharing | Huawei | imported from 3GU |
| R3‑185744 | Further discussion on Bearer type changes | Huawei | imported from 3GU |
| R3‑185745 | CR to 38.473 on bearer type change indication | Huawei | imported from 3GU |
| R3‑185746 | (TP for NR BL CR for TS 38.463): on capacity information transfer via E1 interface | Huawei | imported from 3GU |
| R3‑185747 | CR to 38.460 on capacity information transfer via E1 interface | Huawei | imported from 3GU |
| R3‑185748 | (TP for NR BL CR for TS 38.463): on overload information indication over E1 | Huawei | imported from 3GU |
| R3‑185749 | CR to 38.460 on overload information indication over E1 | Huawei | imported from 3GU |
| R3‑185750 | NAS Non-delivery in higher layer split deployments | Huawei | imported from 3GU |
| R3‑185751 | CR to 38.473 on the introduction of DL RRC message transfer report procedure | Huawei | imported from 3GU |
| R3‑185752 | CR to 38.470 on the introduction of DL RRC message transfer report procedure | Huawei | imported from 3GU |
| R3‑185753 | (TP for NR BL CR for TS 38.463) on PLMN over E1-C non-UE associated signaling | Huawei | imported from 3GU |
| R3‑185754 | CR to 38.473 on correction to PWS System Information | Huawei | imported from 3GU |
| R3‑185755 | CR to 38.473 on Support of delta configuration for inactive UE in disaggregated architecture | Huawei | imported from 3GU |
| R3‑185756 | Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
| R3‑185757 | (TP for BL CR for TS 38.423): DRB ID allocation in MR-DC | Huawei | imported from 3GU |
| R3‑185758 | Data forwarding during bearer type change | Huawei | imported from 3GU |
| R3‑185759 | (TP for BL CR for TS 38.423): Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
| R3‑185760 | (TP for BL CR for TS 38.423): Xn-U TEID for MN terminated bearer | Huawei | imported from 3GU |
| R3‑185761 | Correction on E-UTRA – NR resource coordination | Huawei | imported from 3GU |
| R3‑185762 | (TP for BL CR for TS 38.423) Correction on E-UTRA – NR resource coordination | Huawei | imported from 3GU |
| R3‑185763 | (TP for BL CR for TS 37.340): Alignment of message name | Huawei | imported from 3GU |
| R3‑185764 | (TP for BL CR for TS 38.423): Miscellaneous corrections for Xn | Huawei | imported from 3GU |
| R3‑185765 | E-UTRA usage restriction in 5GS deployment | Huawei | imported from 3GU |
| R3‑185766 | [DRAFT] LS on E-UTRA Usage Restriction in 5GS deployment | Huawei | imported from 3GU |
| R3‑185767 | (TP for BL CR for TS 38.423): De-configuration of PDCP Duplication | Huawei | imported from 3GU |
| R3‑185768 | (TP for BL CR for TS 38.423): Support of SN Initiated PDCP Duplication | Huawei | imported from 3GU |
| R3‑185769 | (TP for BL CR for TS 38.423): Correction on DL UP TNL information in MN initiated procedures | Huawei | imported from 3GU |
| R3‑185770 | PDU session split | Huawei | imported from 3GU |
| R3‑185771 | (TP for BL CR for TS 37.340): PDU session split | Huawei | imported from 3GU |
| R3‑185772 | (TP for BL CR for TS 38.413): PDU session split | Huawei | imported from 3GU |
| R3‑185773 | [DRAFT] LS on PDU session split | Huawei | imported from 3GU |
| R3‑185774 | In-order delivery in MR-DC QoS flow offloading | Huawei | imported from 3GU |
| R3‑185775 | (TP for BL CR for TS 37.340): In-order delivery in MR-DC QoS flow offloading | Huawei | imported from 3GU |
| R3‑185776 | (TP for BL CR for TS 38.423): In-order delivery in MR-DC QoS flow offloading | Huawei | imported from 3GU |
| R3‑185777 | (TP for BL CR for TS 38.423): Support of DRB level offloading | Huawei | imported from 3GU |
| R3‑185778 | (TP for BL CR for TS 38.423): UL usage in the UL split bearer | Huawei | imported from 3GU |
| R3‑185779 | Discussion on RLC mode change | Huawei | imported from 3GU |
| R3‑185780 | Support of RLC mode change | Huawei | imported from 3GU |
| R3‑185781 | (TP for BL CR for TS 38.423): Support of RLC mode change | Huawei | imported from 3GU |
| R3‑185782 | Considerations on using same counter value | Huawei | imported from 3GU |
| R3‑185783 | [DRAFT] Reply LS on using same counter in EDCE5 | Huawei | imported from 3GU |
| R3‑185784 | (TP for BL CR for TS 37.340): Clarification on UE AMBR and PDU session AMBR | Huawei | imported from 3GU |
| R3‑185785 | (TP for BL CR for TS 38.413) Clarification on User plane security | Huawei | imported from 3GU |
| R3‑185786 | (TP for BL CR for TS 38.423) Clarification on User plane security | Huawei | imported from 3GU |
| R3‑185787 | (TP for BL CR for TS 38.463) Clarification on User plane security | Huawei | imported from 3GU |
| R3‑185788 | (TP for BL CR for TS 38.423): Clarification on Counter Check | Huawei | imported from 3GU |
| R3‑185789 | (TP for BL CR for TS 38.425): Differentiate RLC AM and UM for user plane | Huawei | imported from 3GU |
| R3‑185790 | (TP for BL CR for TS 38.425): Corrections on DL USER DATA frame | Huawei | imported from 3GU |
| R3‑185791 | (TP for BL CR for TS 38.425): Miscellaneous corrections for User Plane | Huawei | imported from 3GU |
| R3‑185792 | (TP for BL CR for TS 38.413): Add missing abnormal conditions over NG | Huawei | imported from 3GU |
| R3‑185793 | (TP for BL CR for TS 38.423): Add missing abnormal conditions over Xn | Huawei | imported from 3GU |
| R3‑185794 | (TP for BL CR for TS 38.423): SN Status Transfer for MR-DC | Huawei | imported from 3GU |
| R3‑185795 | Radio quality information report triggering | Ericsson | imported from 3GU |
| R3‑185796 | CR to TS 38.425 Radio quality information report triggering | Ericsson | imported from 3GU |
| R3‑185797 | (TP for NR BL CR for TS 38.413): Corrections on RRC inactive transition report | LG Electronics | imported from 3GU |
| R3‑185798 | (TP for NR BL CR for TS 38.423): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑185799 | (TP for NR BL CR for TS 38.413): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑185800 | (TP for NR BL CR for TS 38.463): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑185801 | CR to 38.473 on asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑185802 | Notification Control during Handover | Huawei | imported from 3GU |
| R3‑185803 | [Draft] LS on Notification Control during Handover | Huawei | imported from 3GU |
| R3‑185804 | (TP for NR BL CR for TS 38.413): Including PDU Session ID in UE Context Release Request | Huawei | imported from 3GU |
| R3‑185805 | (TP for NR BL CR for TS 38.413): Per Slice AMF Set | Huawei | imported from 3GU |
| R3‑185806 | (TP for NR BL CR for TS 38.413): Correction on Unique 5G-TMSI (Huawei) | Huawei | imported from 3GU |
| R3‑185807 | Overview of the requirements and the study scope for IIOT | Huawei | imported from 3GU |
| R3‑185808 | Consideration on the accurate reference timing in TSN for I-IoT | Huawei | imported from 3GU |
| R3‑185809 | Discussion on QoS support for IIoT | Huawei | imported from 3GU |
| R3‑185810 | Discussion on the PDCP Duplication with more than 2 copies | Huawei | imported from 3GU |
| R3‑185811 | Impacts of higher layer multi-connection for IIoT | Huawei | imported from 3GU |
| R3‑185812 | Discussion on KPIs defined in 22.804 for TSN integration in 5G system | Huawei | imported from 3GU |
| R3‑185813 | Reply LS to SA2 on TSN integration in the 5G System | Huawei | imported from 3GU |
| R3‑185814 | (TP for NR BL CR for TS 37.340): Data forwarding for MR-DC | Huawei | imported from 3GU |
| R3‑185815 | [TP for NR BL CR for TS 38.423] Data forwarding for MR-DC | Huawei | imported from 3GU |
| R3‑185816 | (TP for NR BL CR for TS 38.300): Data forwarding handling for intra-system HO | Huawei | imported from 3GU |
| R3‑185817 | Discussion on data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑185818 | (TP for NR BL CR for TS 37.340): SN-initiated DRB and QoS flow offloading for MR-DC | Huawei | imported from 3GU |
| R3‑185819 | (TP for NR BL CR for TS 38.423): SN-initiated DRB and QoS flow offloading for MR-DC | Huawei | imported from 3GU |
| R3‑185820 | (TP for NR BL CR for TS 38.463): RAN paging failure in CP-UP separation | LG Electronics | imported from 3GU |
| R3‑185821 | On PLMN mismatch in inactive state | Qualcomm Incorporated | imported from 3GU |
| R3‑185822 | Considerations on SA2 LS in R2-185455 on TSN integration in the 5G System | Vodafone Ireland Plc | imported from 3GU |
| R3‑185823 | Draft Reply LS on inclusion of selected PLMN into the complete message | Qualcomm Incorporated | imported from 3GU |
| R3‑185824 | RAN paging failure in CP-UP separation | LG Electronics | imported from 3GU |
| R3‑185825 | Further discussion on TNL address discovery for EN-DC using “virtual eNB” | Qualcomm Incorporated | imported from 3GU |
| R3‑185826 | General Requirements of RAN-Centric Data Collection and Utilization for LTE and NR | Vodafone Ireland Plc | imported from 3GU |
| R3‑185827 | TP to TR 38.874: Comparison of CP Alternatives of Architecture 1a | Ericsson | imported from 3GU |
| R3‑185828 | Usage of SCTP Over the IAB Backhaul Interface | Ericsson | imported from 3GU |
| R3‑185829 | TP to TR 38.874: Way Forward on CU-DU Separation | Ericsson, AT&T, KDDI | imported from 3GU |
| R3‑185830 | TP to TR 38.874: Way Forward on F1-AP Termination for CP Alternatives of Architecture Group 1a | Ericsson, AT&T, KDDI, Qualcomm | imported from 3GU |
| R3‑185831 | TP to TR 38.874: Way Forward on F1-U Termination | Ericsson, AT&T, KDDI | imported from 3GU |
| R3‑185832 | TP to TR 38.874: IAB node Access Procedure for Architecture Group 1 | Ericsson | imported from 3GU |
| R3‑185833 | TP to TR 38.874: Setup Procedure for the Adaptation Layer of an IAB Network | Ericsson | imported from 3GU |
| R3‑185834 | TP to TR 38.874: End-to-end Flow Control in Multi-hop IAB Networks | Ericsson | imported from 3GU |
| R3‑185835 | TP to 38.874: Hop-by-hop Flow Control in Multi-hop IAB Networks | Ericsson | imported from 3GU |
| R3‑185836 | TP to TR 38.874: Supporting Network Slicing in IAB Networks | Ericsson | imported from 3GU |
| R3‑185837 | TP to TR 38.874: Using F1 Functionality to Support Redudant Paths | Ericsson, AT&T, KDDI | imported from 3GU |
| R3‑185838 | Use cases for the SON study item | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185839 | Adding PCI information for SSBs on Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185840 | Support for TNL address information discovery for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185841 | Support for TNL address information discovery for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185842 | Solutions for MN/SN resource coordination key issues | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185843 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185844 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185845 | Further analysis of RRC re-establishment in case of RAN sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185846 | Signalling and OAM requirements for NR Remote Interference Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185847 | Xn procedures for inter-gNB signaling of TDD radio frame configuration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185848 | Inter-RAT ANR Scenarios | Qualcomm Incorporated | imported from 3GU |
| R3‑185849 | NR-NTN: Tracking Areas and Paging in NGSO Satellite Systems | Fraunhofer IIS, Fraunhofer HHI | imported from 3GU |
| R3‑185850 | RRC Delivery Indication | Ericsson | imported from 3GU |
| R3‑185851 | Multiple TNLA over F1 initialization | Ericsson | imported from 3GU |
| R3‑185852 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
| R3‑185853 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
| R3‑185854 | [TP BL CR TS 38.413] Asymmetric UL and DL QoS flows to DRB mapping | Ericsson | imported from 3GU |
| R3‑185855 | [TP BL CR TS 38.423] Asymmetric UL and DL QoS flows to DRB mapping | Ericsson | imported from 3GU |
| R3‑185856 | [TP BL CR TS 38.463] Asymmetric UL and DL QoS flows to DRB mapping | Ericsson | imported from 3GU |
| R3‑185857 | Asymmetric UL and DL QoS flows to DRB mapping | Ericsson | imported from 3GU |
| R3‑185858 | [TP for BL CR 38.300] Correction on QoS flow remapping in response to LS in in R2-1813049 | Ericsson | imported from 3GU |
| R3‑185859 | [TP BL CR 38.300] intra-system data forwarding correction | Ericsson | imported from 3GU |
| R3‑185860 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
| R3‑185861 | [TP BL CR TS 38.413] Data forwarding handling between 4G and 5G | Ericsson | imported from 3GU |
| R3‑185862 | Data Forwarding – Common Aspects | Ericsson | imported from 3GU |
| R3‑185863 | TP for BL CR for 38.300 for inter-system HO | Ericsson | imported from 3GU |
| R3‑185864 | Data forwarding aspects for DC bearer type change and QoS flow offloading | Ericsson | imported from 3GU |
| R3‑185865 | [TP for BL CR TS 37.340] Data forwarding aspects for intra-system ACTIVE mobility | Ericsson | imported from 3GU |
| R3‑185866 | [TP BL CR 38.423] Data forwarding aspects for MR-DC | Ericsson | imported from 3GU |
| R3‑185867 | XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185868 | [TP BL CR 37.340] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185869 | [TP BL CR 38.423] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185870 | [TP BL CR TS 38.413] Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑185871 | PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑185872 | PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑185873 | Correction on PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑185874 | Transporting F1 over Satellite Radio Interface | Ericsson | imported from 3GU |
| R3‑185875 | Applicability of Xn to Satellites | Ericsson | imported from 3GU |
| R3‑185876 | Network Identities for Non-Terrestrial Networks | Ericsson | imported from 3GU |
| R3‑185877 | Considerations on Mobility in Non-Terrestrial Networks | Ericsson | imported from 3GU |
| R3‑185878 | Discussion on support for Resource-Efficient PDCP Duplication | Ericsson | imported from 3GU |
| R3‑185879 | Discussion on support for PDCP Duplication with More than 2 Copies | Ericsson | imported from 3GU |
| R3‑185880 | Potential Impacts of Higher Layer Multi-Connectivity related to the Key Issue 1 | Ericsson | imported from 3GU |
| R3‑185881 | Summary of V2X in RAN3 | Ericsson | imported from 3GU |
| R3‑185882 | SON functions to be considered for NR | Ericsson | imported from 3GU |
| R3‑185883 | Xn/X2 TNL address discovery with flexible RAN node ID length | Ericsson | imported from 3GU |
| R3‑185884 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC – and handling of flexible eNB and en-gNB ID length | Ericsson | imported from 3GU |
| R3‑185885 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC – and handling of flexible eNB and en-gNB ID length | Ericsson | imported from 3GU |
| R3‑185886 | Introducing support of deduction of NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑185887 | [TP for 38.413 BL CR] Introducing support of deduction of NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑185888 | Correction on ANR related information | Ericsson | imported from 3GU |
| R3‑185889 | Correction on ANR related information | Ericsson | imported from 3GU |
| R3‑185890 | [TP BL CR TS 38.401] F1 Cell Management | Ericsson | imported from 3GU |
| R3‑185891 | CR for F1 Cell Management | Ericsson | imported from 3GU |
| R3‑185892 | [TP BL CR TS 38.463] Capactiy Information on E1 | Ericsson | imported from 3GU |
| R3‑185893 | [TP BL CR TS 38.413] Correction to AMF overload procedure | Ericsson | imported from 3GU |
| R3‑185894 | CSI-RS Configuration Transfer | Ericsson | imported from 3GU |
| R3‑185895 | System info delivery for UE with multiple BWP | Ericsson | imported from 3GU |
| R3‑185896 | RRC Delivery Indication | Ericsson | imported from 3GU |
| R3‑185897 | Criticality handling related to SMF IEs in request transfer received by NG-RAN node | Ericsson | imported from 3GU |
| R3‑185898 | Criticality handling related to SMF IEs in request transfer received by SMF | Ericsson | imported from 3GU |
| R3‑185899 | Support of keeping the DL UP termination point on the RAN-CN interface – HO and DC aspects | Ericsson, Vodafone | imported from 3GU |
| R3‑185900 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.300 | Ericsson | imported from 3GU |
| R3‑185901 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.413 | Ericsson | imported from 3GU |
| R3‑185902 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.423 | Ericsson | imported from 3GU |
| R3‑185903 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.300 | Ericsson | imported from 3GU |
| R3‑185904 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.413 | Ericsson | imported from 3GU |
| R3‑185905 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.423 | Ericsson | imported from 3GU |
| R3‑185906 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.463 | Ericsson | imported from 3GU |
| R3‑185907 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑185908 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑185909 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑185910 | Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
| R3‑185911 | Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
| R3‑185912 | [TP BL CR TS 38.463] Multiple TNLA over E1 initialization | Ericsson | imported from 3GU |
| R3‑185913 | Option 3 ANR - X2 connectivity across MME pools for EN-DC | Ericsson | imported from 3GU |
| R3‑185914 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
| R3‑185915 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
| R3‑185916 | [TP BL CR TS 38.413] Correction on UE AMBR | Ericsson | imported from 3GU |
| R3‑185917 | [TP BL CR TS 38.423] Correction on UE AMBR on XnAP | Ericsson | imported from 3GU |
| R3‑185918 | [TP BL CR TS 38.463] Correction on UE AMBR on E1AP | Ericsson | imported from 3GU |
| R3‑185919 | Correction on UE AMBR on F1AP | Ericsson | imported from 3GU |
| R3‑185920 | Bearer type change indication | Ericsson | imported from 3GU |
| R3‑185921 | Bearer type change indication | Ericsson | imported from 3GU |
| R3‑185922 | Missing Transaction ID in non-UE-associated procedures | Ericsson | imported from 3GU |
| R3‑185923 | Correction on SGNB ACTIVITY NOTIFICATION IE's | Ericsson | imported from 3GU |
| R3‑185924 | [TP BL CR TS 38.463] Paging Priority Indication on E1 | Ericsson | imported from 3GU |
| R3‑185925 | [TP BL CR TS 38.463] Increasing maxnooUPParameters for support of CA duplication | Ericsson | imported from 3GU |
| R3‑185926 | [TP BL CR TS 38.463] gNB-CU-UP connection status | Ericsson | imported from 3GU |
| R3‑185927 | [TP BL CR TS 38.463] Clarification on new UL TEID request | Ericsson | imported from 3GU |
| R3‑185928 | [TP BL CR TS 38.413] NGAP Correction related to Intra system Handover | Ericsson | imported from 3GU |
| R3‑185929 | Support of NG-RAN initiated Addition of TNLAs on NG-C | Ericsson | imported from 3GU |
| R3‑185930 | [TP for BL CR for NGAP] Introducing NG-RAN initiated addition of TNL Associations | Ericsson | imported from 3GU |
| R3‑185931 | Associating an additional TNLA with the NG-C interface instance by means of the RAN Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑185932 | Dissociating a TNLA from the NG-C interface instance by means of the AMF/RAN Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑185933 | Correction on PDU Session Resource Modify | Ericsson | imported from 3GU |
| R3‑185934 | Including QoS flow information in Handover Required Transfer | Ericsson | imported from 3GU |
| R3‑185935 | [TP BL CR TS 38.423] Corrections to the RETRIEVE UE CONTEXT REQUEST message | Ericsson | imported from 3GU |
| R3‑185936 | XnAP extensibility for multi-connectivity - taking a lean from E1AP | Ericsson | imported from 3GU |
| R3‑185937 | [TP for XnAP BL CR] XnAP extensibility for multi-connectivity | Ericsson | imported from 3GU |
| R3‑185938 | [TP for BL CR XnAP] Resolving open issue on maximum number of bearer configurations | Ericsson | imported from 3GU |
| R3‑185939 | [TP BL CR 36.423] Clarification on NRARFCN semantics – TP for X2AP | Ericsson | imported from 3GU |
| R3‑185940 | [TP BL CR 38.423] Clarification on NRARFCN semantics – TP for XnAP | Ericsson | imported from 3GU |
| R3‑185941 | [TP BL CR 38.473] Clarification on NRARFCN semantics – TP for F1AP | Ericsson | imported from 3GU |
| R3‑185942 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑185943 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑185944 | [TP for 38.413 BL CR] Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑185945 | Gap Configuration Response over X2 | Ericsson | imported from 3GU |
| R3‑185946 | Measurement gap response over X2 | Ericsson | imported from 3GU |
| R3‑185947 | Resource allocation for SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185948 | [TP BL CR TS 38.463] E1 Resource Allocation for SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185949 | [TP BL CR TS 38.423] Xn Resource Allocation for SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑185950 | Removing NG-RAN specific statements from TS 36.300 | Ericsson | imported from 3GU |
| R3‑185951 | Discussion on Notification Control | Ericsson | imported from 3GU |
| R3‑185952 | [TP for BL CR 38.413] Correction for Notification Control | Ericsson | imported from 3GU |
| R3‑185953 | [TP for BL CR 38.423] Correction for Notification Control | Ericsson | imported from 3GU |
| R3‑185954 | [TP for BL CR 38.463] Correction for Notification Control | Ericsson | imported from 3GU |
| R3‑185955 | Open issues in UE-level MeNBSgNB resource coordination | Ericsson | imported from 3GU |
| R3‑185956 | CR to TS 36.423 Assistance information for MeNB/SgNB UE-level resource coordination | Ericsson | imported from 3GU |
| R3‑185957 | Idle State Mobility Scenarios for Non-Terrestrial Networks | TNO | imported from 3GU |
| R3‑185958 | Time Sensitive Networking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑185959 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑185960 | [TP for BL CR 38.423] Various non-editorial corrections | Ericsson | imported from 3GU |
| R3‑185961 | [TP for BL CR 38.423] for introducing the Expected UE behavior into XnAP | Ericsson | imported from 3GU |
| R3‑185962 | UE-Interested Slice | Qualcomm Incorporated, T-Mobile USA, CATT | imported from 3GU |
| R3‑185963 | Discussion on LS TSN integration in the 5G System | Qualcomm Incorporated | imported from 3GU |
| R3‑185964 | [Draft] Reply LS on TSN integration in the 5G System | Qualcomm Incorporated | imported from 3GU |
| R3‑185965 | Possibility of backhaul signaling without core network involvement | LG Electronics Inc. | imported from 3GU |
| R3‑185966 | Consideration on backhaul signaling with core network involvement | LG Electronics Inc. | imported from 3GU |
| R3‑185967 | SRB Types for Control Plane Alternative 2 | Huawei | imported from 3GU |
| R3‑185968 | Route selection method for architecture 1a | Huawei | imported from 3GU |
| R3‑185969 | Topology Table Establishment and Update | Huawei | imported from 3GU |
| R3‑185970 | Further discussions on gap generation in case of two gNB-Dus | Huawei | imported from 3GU |
| R3‑185971 | CR to 38.473 on the clarifications to measurement gap generation in case of two gNB-Dus | Huawei | imported from 3GU |
| R3‑185972 | (TP for NR BL CR for TS 38.401): on further clarification to Cell Status when failed to active | Huawei | imported from 3GU |
| R3‑185973 | CR to 38.473 on further clarification to Cell Status when failed to active | Huawei | imported from 3GU |
| R3‑185974 | Further discussion on RLC failure indication | Huawei | imported from 3GU |
| R3‑185975 | CR to 38.473 on clarification to RLC failure indication over F1 | Huawei | imported from 3GU |
| R3‑185976 | CR to 38.473 on clarification to gNB-CU system information update | Huawei | imported from 3GU |
| R3‑185977 | CR to 38.473 on clarification to the presence of UE AMBR | Huawei | imported from 3GU |
| R3‑185978 | (TP for NR BL CR for TS 38.401): on RRC state transition | Huawei | imported from 3GU |
| R3‑185979 | CR to 38.473 on new cause value when entering RRC inactive | Huawei | imported from 3GU |
| R3‑185980 | CR to 38.460 on inactivity notification over E1 | Huawei | imported from 3GU |
| R3‑185981 | (TP for NR BL CR for TS 38.463): on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑185982 | CR to 38.460 on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑185983 | (TP for NR BL CR for TS 38.463): on notification of GBR QoS FlowFlow | Huawei | imported from 3GU |
| R3‑185984 | CR to 38.460 on notification of GBR QoS Flow | Huawei | imported from 3GU |
| R3‑185985 | Discussion on mapping of ServingCellMO and Serving Cell over F1 | Huawei | imported from 3GU |
| R3‑185986 | CR to 38.473 on mapping of ServingCellMO and Serving Cell over F1 | Huawei | imported from 3GU |
| R3‑185987 | Further discussion on based DRB PDCP duplication | Huawei | imported from 3GU |
| R3‑185988 | CR to 38.473 on DRB PDCP duplication | Huawei | imported from 3GU |
| R3‑185989 | CR to 38.473 on the condition of gNB-DU provides C-RNTI | Huawei | imported from 3GU |
| R3‑185990 | CR to 38.473 on UE context modification required procedure | Huawei | imported from 3GU |
| R3‑185991 | CR to 38.473 on inactivity monitoring request | Huawei | imported from 3GU |
| R3‑185992 | (TP for NR BL CR for TS 38.463): on maximum integrity protected data rate over E1 | Huawei | imported from 3GU |
| R3‑185993 | (TP for NR BL CR for TS 38.463): on duplication indication over E1 interface | Huawei | imported from 3GU |
| R3‑185994 | CR to 38.473 on duplication activation | Huawei | imported from 3GU |
| R3‑185995 | (TP for NR BL CR for TS 38.463): on PDCP suspend indication over E1 interface | Huawei | imported from 3GU |
| R3‑185996 | CR to 38.460 on PDCP suspend indication over E1 interface | Huawei | imported from 3GU |
| R3‑185997 | (TP for NR BL CR for TS 38.463): on corrections of ROHC parameters over E1 | Huawei | imported from 3GU |
| R3‑185998 | CR to 38.473 on removal of PDCP duplication for SRB | Huawei | imported from 3GU |
| R3‑185999 | IAB bearer mapping decisions | Huawei | imported from 3GU |
| R3‑186000 | QoS parameters for IAB QoS handling | Huawei | imported from 3GU |
| R3‑186001 | IAB for vehicular networks | Mitsubishi Electric RCE | imported from 3GU |
| R3‑186002 | Tracking Areas with Non Terrestrial Networks (NTN) | Mitsubishi Electric RCE | imported from 3GU |
| R3‑186003 | (TP for NR BL CR for TS 38.401): Correction for early provision of DL F1-U TNL toward gNB-CU-UP | Intel Corporation | imported from 3GU |
| R3‑186004 | (TP for NR BL CR for TS 38.423): For unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
| R3‑186005 | (TP for NR BL CR for TS 38.423): UL in-order delivery support for QoS flow offloading | Intel Corporation | imported from 3GU |
| R3‑186006 | (TP for NR BL CR for TS 38.423): Correction on data forwarding request and response for offloading from MN to SN | Intel Corporation | imported from 3GU |
| R3‑186007 | (TP for NR BL CR for TS 38.423): Correction on MN's release request for SN-terminated bearer using MCG resources | Intel Corporation | imported from 3GU |
| R3‑186008 | RAN3 scope of the NR V2X SI | Intel Corporation | imported from 3GU |
| R3‑186009 | Further Consideration on Multiple connectivity for IAB nodes | Huawei | imported from 3GU |
| R3‑186010 | Discussion on End marker for QoS flow offloading | CATT | imported from 3GU |
| R3‑186011 | (TP for NR BL CR for TS 38.423): Notification Control during Secondary Node Change | CATT | imported from 3GU |
| R3‑186012 | (TP for NR BL CR for TS 38.473): Notification Control during inter-DU HO | CATT | imported from 3GU |
| R3‑186013 | (TP for NR BL CR for TS 38.423): cause value-slice not supported | CATT | imported from 3GU |
| R3‑186014 | Slice support of IAB nodes | Huawei | imported from 3GU |
| R3‑186015 | Discuss on the RIM support | CATT | imported from 3GU |
| R3‑186016 | Comparisons of C-plane alternatives | Huawei | imported from 3GU |
| R3‑186017 | (TP for NR BL CR for TS 37.340) DRB ID Allocation | LG Electronics | imported from 3GU |
| R3‑186018 | Clarification on highest NR PDCP PDU SN for retransmitted PDCP PDU | Samsung | imported from 3GU |
| R3‑186019 | CR for clarification on highest NR PDCP PDU SN | Samsung | imported from 3GU |
| R3‑186020 | Discussion on PDCP Duplication resource usage | CATT | imported from 3GU |
| R3‑186021 | Distributed RRC functions for IAB | Huawei | imported from 3GU |
| R3‑186022 | Comparison with proposed IAB architectures | LG Electronics Inc. | imported from 3GU |
| R3‑186023 | Comparison with CP alternatives for architecture 1a | LG Electronics Inc. | imported from 3GU |
| R3‑186024 | Considerations on NR RIM | Huawei | imported from 3GU |
| R3‑186025 | The Scenarios and principles for RAN centric Data collection | Huawei | imported from 3GU |
| R3‑186026 | Support for MDT in NG-RAN | Huawei | imported from 3GU |
| R3‑186027 | Support of SON use cases in NG-RAN | Huawei | imported from 3GU |
| R3‑186028 | TR 38.866 V0.0.0 | CMCC | imported from 3GU |
| R3‑186029 | Work plan for study on RIM | CMCC | imported from 3GU |
| R3‑186030 | Discussion on support of RIM framework | CMCC | imported from 3GU |
| R3‑186031 | Skeleton for TR 37.816 | CMCC | imported from 3GU |
| R3‑186032 | Work plan for study on RAN-centric data collection and utilization for LTE and NR | CMCC | imported from 3GU |
| R3‑186033 | Considerations on V2X use cases and measurements | CMCC | imported from 3GU |
| R3‑186034 | (TP for BLCR for TS 38.300) data forwarding handling during lossless handover for AM RLC DRBs | CMCC | imported from 3GU |
| R3‑186035 | Support for Accurate Reference Timing Delivery | CMCC | imported from 3GU |
| R3‑186036 | Performance evaluation and architecture study of TSN | CMCC | imported from 3GU |
| R3‑186037 | [Draft]Reply LS on TSN integration in the 5G System | CMCC | imported from 3GU |
| R3‑186038 | Initial Consideration on 5G SON Functions | CMCC | imported from 3GU |
| R3‑186039 | Considerations on support of MDT in NR | CMCC | imported from 3GU |
| R3‑186040 | Use Case of Edge Computing and Radio Network Exposure | CMCC | imported from 3GU |
| R3‑186041 | (TP for BL CR for TS 38.401) cell management over F1 | CMCC | imported from 3GU |
| R3‑186042 | CR to TS 38.373 on corrections to cell management over F1 | CMCC | imported from 3GU |
| R3‑186043 | Considerations on NG-RAN Architectures for Non-terrestrial Networks | ETRI | imported from 3GU |
| R3‑186044 | The consequences of including slicing information in NGAP Paging messages | Ericsson, CATT, ZTE | imported from 3GU |
| R3‑186045 | Existing mechanisms for CP congestion mitigation in the RAN | Ericsson, CATT, China Telecom, ZTE | imported from 3GU |
| R3‑186046 | [Draft] Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Ericsson | imported from 3GU |
| R3‑186047 | Response to R3-186018 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186048 | Response to R3-185691 | Qualcomm Incorporated | imported from 3GU |
| R3‑186049 | LS on initial NAS security agreements | 3GPP SA3, Qualcomm | imported from 3GU |
| R3‑186050 | LS on RRC Reestablishment during N2 Handover | 3GPP SA3, Huawei | imported from 3GU |
| R3‑186051 | LS on the Impacts of increasing the MAC-I and NAS-MAC size | 3GPP SA3, AT&T | imported from 3GU |
| R3‑186052 | Response to R3-185691: (TP for NR BL CR for TS 38.413): Support of paging for ng-eNB | VODAFONE Group Plc | imported from 3GU |
| R3‑186053 | Response to R3-185596 and R3-185739 | Ericsson | imported from 3GU |
| R3‑186054 | Response to R3-185740 | Ericsson | imported from 3GU |
| R3‑186055 | Response to R3-185741 | Ericsson | imported from 3GU |
| R3‑186056 | Response to R3-185845 | Ericsson | imported from 3GU |
| R3‑186057 | Response to R3-185599 and R3-185742 | Ericsson | imported from 3GU |
| R3‑186058 | Response to R3-185779, R3-185502 | Ericsson | imported from 3GU |
| R3‑186059 | Response to R3-185780, R3-185485, R3-185503 | Ericsson | imported from 3GU |
| R3‑186060 | Response to R3-185781, R3-185485, R3-185502 | Ericsson | imported from 3GU |
| R3‑186061 | Response to R3-185781 | Ericsson | imported from 3GU |
| R3‑186062 | Response to R3-185504 | Ericsson | imported from 3GU |
| R3‑186063 | Response to R3-185702 | Ericsson | imported from 3GU |
| R3‑186064 | Response to R3-186044 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186065 | Response to R3-185804 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186066 | Response to R3-185942 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186067 | LS on replay protection | 3GPP SA3, Ericsson | imported from 3GU |
| R3‑186068 | LS on initial NAS security agreements | 3GPP SA3, Qualcomm | imported from 3GU |
| R3‑186069 | LS on RRC Reestablishment during N2 Handover | 3GPP SA3, Huawei | imported from 3GU |
| R3‑186070 | LS on the Impacts of increasing the MAC-I and NAS-MAC size | 3GPP SA3, AT&T | imported from 3GU |
| R3‑186071 | Baseline CR for TS 38.423 | Ericsson LM | imported from 3GU |
| R3‑186072 | Open issues in UE-level MeNBSgNB resource coordination | Ericsson | imported from 3GU |
| R3‑186073 | Assistance information for UE-level MeNB/SgNB resource coordination | Ericsson | imported from 3GU |
| R3‑186074 | Radio quality information report triggering | Ericsson | imported from 3GU |
| R3‑186075 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186076 | (TP for BL CR to 38.300): RNA update corrections | Google Inc. | imported from 3GU |
| R3‑186077 | Draft Reply LS on inclusion of selected PLMN into the complete message | Qualcomm Incorporated | imported from 3GU |
| R3‑186078 | [Draft] Reply LS to SA5 on L2 measurements | Huawei | imported from 3GU |
| R3‑186079 | Report on Offline Discussions on CB#4 on RLC mode indication | ZTE | imported from 3GU |
| R3‑186080 | Summary of offline discussion on on MME supporting RAT Type | Huawei | imported from 3GU |
| R3‑186081 | NB-IoT TDD correction | Huawei | imported from 3GU |
| R3‑186082 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑186083 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑186084 | Baseline CR for TS 37.340 | ZTE Corporation | imported from 3GU |
| R3‑186085 | Rapporteur’s CR for TS 38.410 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186086 | Rapporteur’s CR for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
| R3‑186087 | Summary of offline discussion on Support of paging for ng-eNB | Qualcomm | imported from 3GU |
| R3‑186088 | (TP for BL CR for TS 38.300): DraftCR on 38.300 for ANR | vivo | imported from 3GU |
| R3‑186089 | Correction on ANR related information | Ericsson | imported from 3GU |
| R3‑186090 | LS on Adding PCI information for SSBs on Xn | nokia | imported from 3GU |
| R3‑186091 | W1 interface User Plane Protocol | Huawei, China Unicom, Orange | imported from 3GU |
| R3‑186092 | Supporting of W1 user Plane Protocol | Huawei, China Unicom, Orange | imported from 3GU |
| R3‑186093 | Disaggregated ng-eNB connecting to 5GC | Huawei, China Unicom, Orange | imported from 3GU |
| R3‑186094 | Consideration on eNB-CU UE W1AP ID and eNB-DU UE W1AP ID | Huawei, China Unicom, Orange | imported from 3GU |
| R3‑186095 | Performance results for hop-by-hop vs. end-to-end RLC ARQ | AT&T | imported from 3GU |
| R3‑186096 | Summary of offline discussion on deduction of en-gNB ID length | Ericsson | imported from 3GU |
| R3‑186097 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186098 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186099 | F1 Load Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186100 | CR on Introduction of overload indication over X2 | NTT DOCOMO,INC. | imported from 3GU |
| R3‑186101 | [TP BL CR TS 38.401] F1 Cell Management | Ericsson | imported from 3GU |
| R3‑186102 | CR for F1 Cell Management | Ericsson | imported from 3GU |
| R3‑186103 | CR to 38.460 on capacity information transfer via E1 interface | Huawei | imported from 3GU |
| R3‑186104 | Use case for Minimization of Drive Testing | Samsung | imported from 3GU |
| R3‑186105 | (TP for NR BL CR for TS 38.463): on capacity information transfer via E1 interface | Huawei | imported from 3GU |
| R3‑186106 | Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., Intel Corporation, ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI | imported from 3GU |
| R3‑186107 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung, KT Corp., Intel Corporation, ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI | imported from 3GU |
| R3‑186108 | (TP for NR BL CR for TS 38.463): on overload information indication over E1 | Huawei | imported from 3GU |
| R3‑186109 | CR to 38.460 on overload information indication over E1 | Huawei | imported from 3GU |
| R3‑186110 | (TP for BL CR for TS 38.413) Clarification of AMF overload | Huawei | imported from 3GU |
| R3‑186111 | (TP for NR BL CR for TS 38.413) Overload Control for UAC | ZTE Corporation, China Unicom, NTT Docomo | imported from 3GU |
| R3‑186112 | Summary of the offline on Notification Control during Secondary Node Change | CATT | imported from 3GU |
| R3‑186113 | Summary of offline discussions on Slicing in Paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186114 | Summary of discussion on UE interested S-NSSAI | Qualcomm Incorporated, T-Mobile USA, CATT, CMCC, Deutsche Telekom, China Unicom | imported from 3GU |
| R3‑186115 | NR Industrial IoT session report | Vice chairman | imported from 3GU |
| R3‑186116 | NR Remote Interference Management session report | Vice chairman | imported from 3GU |
| R3‑186117 | NR V2X session report | Vice chairman | imported from 3GU |
| R3‑186118 | RAN-Centric Data Collection and Utilization for LTE and NR session report | Vice chairman | imported from 3GU |
| R3‑186119 | Liaison letter on IEEE 802.1CM TSN for Fronthaul | IEEE 802.1, Ericsson | imported from 3GU |
| R3‑186120 | Summary of CB: # 25_SysInfoUpdate_ActiveUEs | NEC | imported from 3GU |
| R3‑186121 | RRC Delivery Indication | Ericsson, Nokia, Huawei | imported from 3GU |
| R3‑186122 | CR to 38.470 on the introduction of DL RRC message transfer report procedure | Huawei,Ericsson | imported from 3GU |
| R3‑186123 | Summary of CB: # 27_UP_Retransmission_status | NEC | imported from 3GU |
| R3‑186124 | (TP for NR BL CR for TS 38.300): Data forwarding handling for intra-system HO | Huawei | imported from 3GU |
| R3‑186125 | (TP for NR BL CR for TS 38.300): Correction on intra-system Data forwarding | Huawei | imported from 3GU |
| R3‑186126 | Summary of offline discussions on Inter-System Data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186127 | (TP for NR BL CR for TS 38.300): Handling end marker in inter-system HO | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186128 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung, KT Corp., Intel Corporation, ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI | imported from 3GU |
| R3‑186129 | TP for BL CR for 38.300 for inter-system HO | Ericsson | imported from 3GU |
| R3‑186130 | [TP BL CR TS 38.413] Data forwarding handling between 4G and 5G | Ericsson | imported from 3GU |
| R3‑186131 | Correction on Handover Type | Huawei | imported from 3GU |
| R3‑186132 | TP for TS 38.413 BL CR: Uplink/Downlink RAN Status Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186133 | (TP for NR BL CR for TS 38.423): Complete of SN Status Transfer | Huawei | imported from 3GU |
| R3‑186134 | [TP for BL CR TS 37.340] Data forwarding aspects for intra-system ACTIVE mobility | Ericsson | imported from 3GU |
| R3‑186135 | [TP BL CR 38.423] Data forwarding aspects for MR-DC | Ericsson | imported from 3GU |
| R3‑186136 | Summary of offline discussion on PLMN Information Over E1 Non-UE-Associated Signaling | Huawei | imported from 3GU |
| R3‑186137 | Criticality handling related to SMF IEs in request transfer received by NG-RAN node | Ericsson | imported from 3GU |
| R3‑186138 | (TP for NR BL CR for TS 38.413) Further Cleanups due to AMF Transparency | ZTE | imported from 3GU |
| R3‑186139 | Summary of the off-line discussion on the support of the multiple SCTPs in NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186140 | (TP for BL CR for TS 37.340): MN DL TNL Information Delivery for Flow Level Offload | Qualcomm Incorporated | imported from 3GU |
| R3‑186141 | Summary of offline discussion on TNL Address Discovery for Option 3 | Ericsson | imported from 3GU |
| R3‑186142 | (TP for BL CR to 38.300): RNA update corrections | Google Inc. | imported from 3GU |
| R3‑186143 | (TP for NR BL CR for TS 38.423) Activity Notification Request over Xn | Qualcomm Incorporated | imported from 3GU |
| R3‑186144 | (TP for NR BL CR for TS 38.300): Handling of Reset in inactive state | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186145 | (TP for NR BL CR for TS 38.413): Correction of inactive transitions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186146 | (TP for NR BL CR for TS 38.423): Correction of integrity failure in inactive state | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186147 | (TP for NR BL CR for TS 38.300) Further refinement of the stage 2 RRC-Inactive Mobility section | Qualcomm Incorporated | imported from 3GU |
| R3‑186148 | (TP for BL CR for TS 38.300): Stage 2 text correction for RRC Inactive Assistance Information | Huawei | imported from 3GU |
| R3‑186149 | (TP for BL CR for TS 38.463) Clarification on User plane security | Huawei | imported from 3GU |
| R3‑186150 | (TP for NR BL CR for TS 38.401): Correction of Security and multiple CU UPs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186151 | (TP for NR BL CR for TS 38.463): on maximum integrity protected data rate over E1 | Huawei | imported from 3GU |
| R3‑186152 | Summary of offline discussion on enforcement of UE’s maximum bit rate for Integrity Protection | Qualcomm | imported from 3GU |
| R3‑186153 | (TP for NR BL CR for TS 38.423): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186154 | (TP for NR BL CR for TS 38.413): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186155 | (TP for NR BL CR for TS 38.463): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186156 | Reply LS on asymmetric mapping for UL and DL QoS flows | LGE | imported from 3GU |
| R3‑186157 | CR to 38.473 on asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186158 | Correction of AMBR Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186159 | Removing NG-RAN specific statements from TS 36.300 | Ericsson | imported from 3GU |
| R3‑186160 | LS on Notification Control during Handover | Huawei | imported from 3GU |
| R3‑186161 | [TP for BL CR 38.413] Correction for Notification Control | Ericsson | imported from 3GU |
| R3‑186162 | (TP for NR BL CR for TS 38.300) Further Stage2 Corrections of NR QoS Parameters | ZTE | imported from 3GU |
| R3‑186163 | (TP for NR BL CR for TS 38.413): Correction of NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186164 | (TP for NR BL CR for TS 38.423): cause value-slice not supported | CATT | imported from 3GU |
| R3‑186165 | CR for TS 38.473 on Bearer type change indication | Ericsson | imported from 3GU |
| R3‑186166 | CR to 38.473 on bearer type change indication | Huawei | imported from 3GU |
| R3‑186167 | CR to 38.473 on correction to PWS System Information | Huawei | imported from 3GU |
| R3‑186168 | (TP for NR BL CR for TS 38.413): Correction of Paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186169 | Clarification of RL failure handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186170 | Summary of the offline discussion on UAC barring information | CATT | imported from 3GU |
| R3‑186171 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186172 | (TP for BL CR for TS 38.423): Support of SN Initiated PDCP Duplication | Huawei | imported from 3GU |
| R3‑186173 | Summary of the discussion on LCID for primary path | CATT | imported from 3GU |
| R3‑186174 | (TP for BL CR for TS 38.423): Correction on SN STATUS TRANSFER | ZTE | imported from 3GU |
| R3‑186175 | (TP for BL CR for TS 38.423): Enabling signalling of the RLC Status | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186176 | (TP for BL CR for TS 38.423): Addition of missing Cause value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186177 | (TP for BL CR for TS 38.423): Miscellaneous corrections for Xn | Huawei | imported from 3GU |
| R3‑186178 | (TP for BL CR for TS 38.423): Clarification on Counter Check | Huawei | imported from 3GU |
| R3‑186179 | [TP BL CR TS 38.413] Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑186180 | Summary of offline discussions on RAN initiated PDU session split | Nokia | imported from 3GU |
| R3‑186181 | (TP for BL CR for TS 37.340): Correction on PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑186182 | (TP for NR BL CR for TS 38.423): For unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
| R3‑186183 | Energy Savings in R15 | ZTE Corporation, China Unicom, China Telecom, CMCC | imported from 3GU |
| R3‑186184 | Energy Saving Support over F1 Interface | ZTE, China Unicom | imported from 3GU |
| R3‑186185 | NTN architecture and mobility principles | Thales | imported from 3GU |
| R3‑186186 | MN DL TNL address allocation in flow level offloading | Qualcomm | imported from 3GU |
| R3‑186187 | Correction on E-UTRA – NR resource coordination | Huawei | imported from 3GU |
| R3‑186188 | (TP for BL CR for TS 38.423) Correction on E-UTRA – NR resource coordination | Huawei | imported from 3GU |
| R3‑186189 | CR to 38.473 on mapping of servingCellMO and Serving Cell | Huawei | imported from 3GU |
| R3‑186190 | CR to 38.473 on UE context modification required procedure | Huawei | imported from 3GU |
| R3‑186191 | Corrections on SRB duplication for TS38.473 | ZTE | imported from 3GU |
| R3‑186192 | Architecture options for NTN | THALES | imported from 3GU |
| R3‑186193 | Support of CA based PDCP duplication on X2 | CATT | imported from 3GU |
| R3‑186194 | Correction on PDCP SN length | CATT | imported from 3GU |
| R3‑186195 | Correction on SGNB ACTIVITY NOTIFICATION IE's | Ericsson | imported from 3GU |
| R3‑186196 | Correction of SgNB Initiated SN Modification procedure for Measurement Gap | NEC | imported from 3GU |
| R3‑186197 | Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑186198 | (TP for NR BL CR for TS 38.423) Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑186199 | Clarification of the NR UP initialisation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186200 | Differentiate RLC AM and UM for user plane | Huawei | imported from 3GU |
| R3‑186201 | Corrections on DL USER DATA frame | Huawei | imported from 3GU |
| R3‑186202 | Summary of offline discussion W1 prioritization | NTT Docomo | imported from 3GU |
| R3‑186203 | mobility management principles | Thales | imported from 3GU |
| R3‑186204 | Radio quality information report triggering | Ericsson | imported from 3GU |
| R3‑186205 | Miscellaneous corrections for User Plane | Huawei | imported from 3GU |
| R3‑186206 | (TP for BL CR for TS38.463): CU-UP DL transmission resume | Samsung | imported from 3GU |
| R3‑186207 | (TP for NR BL CR for TS 38.463): on duplication indication over E1 interface | Huawei | imported from 3GU |
| R3‑186208 | Considerations on remaining “FFS” in the TR 38.874 | KDDI Corporation | imported from 3GU |
| R3‑186209 | pCR on comparison of IAB architectures | Qualcomm | imported from 3GU |
| R3‑186210 | TP on IAB with NSA operation | AT&T | imported from 3GU |
| R3‑186211 | TP to TR 38.874: Way Forward on F1-AP Termination for CP Alternatives of Architecture Group 1a | Ericsson, AT&T, KDDI, Qualcomm | imported from 3GU |
| R3‑186212 | Parameters in NTN reference scenarios | ZTE, Sanechips | imported from 3GU |
| R3‑186213 | Way forward for 5G Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186214 | Paging issues in NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186215 | Architecture options for NTN | THALES | imported from 3GU |
| R3‑186216 | Document for the chairman’s education on NG-RAN node initiated TNLA addition | Ericsson | imported from 3GU |
| R3‑186217 | LS on rejected PDU sessions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186218 | (TP for NR BL CR for TS 38.413) Correction of INITIAL CONTEXT SETUP FAILURE | ZTE | imported from 3GU |
| R3‑186219 | [TP for BL CR XnAP] Resolving open issue on maximum number of bearer configurations | Ericsson | imported from 3GU |
| R3‑186220 | Potential Impacts of Higher Layer Multi-Connectivity related to the Key Issue 1 | Ericsson | imported from 3GU |
| R3‑186221 | Way Forward for TSN sychronization | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186222 | [Draft] LS on LCID as primary path | CATT | imported from 3GU |
| R3‑186223 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑186224 | Reply LS on RIM solution frameworks | Ericsson | imported from 3GU |
| R3‑186225 | Summary of Offline Discussion: WF for “Study on NR V2X” in RAN3 | LG Electronics Inc. | imported from 3GU |
| R3‑186226 | Skeleton for TR 37.816 | CMCC | imported from 3GU |
| R3‑186227 | TP of agreed use cases for TR 37.816 | CMCC | imported from 3GU |
| R3‑186228 | Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
| R3‑186229 | (TP for BL CR for TS 38.423): Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
| R3‑186230 | (TP for NR BL CR for TS 38.413): Support of paging for ng-eNB | Huawei | imported from 3GU |
| R3‑186231 | Reply LS on inclusion of selected PLMN into the complete message | Qualcomm Incorporated | imported from 3GU |
| R3‑186232 | Reply LS to SA5 on L2 measurements | Huawei | imported from 3GU |
| R3‑186233 | CR for F1 Cell Management | Ericsson | imported from 3GU |
| R3‑186234 | Way forward on RAN-Centric Data Collection and Utilization for LTE and NR | CMCC | imported from 3GU |
| R3‑186235 | CR to 38.470 on the introduction of DL RRC message transfer report procedure | Huawei,Ericsson | imported from 3GU |
| R3‑186236 | TP for TS 38.413 BL CR: Uplink/Downlink RAN Status Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186237 | (TP for NR BL CR for TS 38.423): For unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
| R3‑186238 | Criticality handling related to SMF IEs in request transfer received by NG-RAN node | Ericsson | imported from 3GU |
| R3‑186239 | [TP BL CR 38.423] Data forwarding aspects for MR-DC | Ericsson | imported from 3GU |
| R3‑186240 | LS to RAN2 on UL/DL asymmetric duplication in the case of CA based duplication | ZTE | imported from 3GU |
| R3‑186241 | (TP for NR BL CR for TS 38.423): cause value-slice not supported | CATT | imported from 3GU |
| R3‑186242 | (TP for BL CR for TS 38.300): Stage 2 text correction for RRC Inactive Assistance Information | Huawei | imported from 3GU |
| R3‑186243 | (TP for NR BL CR for TS 38.463): on maximum integrity protected data rate over E1 | Huawei | imported from 3GU |
| R3‑186244 | (TP for NR BL CR for TS 38.423): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186245 | (TP for NR BL CR for TS 38.413): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186246 | (TP for NR BL CR for TS 38.463): Asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186247 | CR to 38.473 on asymmetric mapping for UL and DL QoS flow | Huawei | imported from 3GU |
| R3‑186248 | Reply LS on asymmetric mapping for UL and DL QoS flows | LGE | imported from 3GU |
| R3‑186249 | LS on Notification Control during Handover | Huawei | imported from 3GU |
| R3‑186250 | (TP for NR BL CR for TS 38.463) Cause IE in DRB To Modify List of Bearer Context Modification Required | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186251 | (TP for BL CR for TS 38.423): Enabling signalling of the RLC Status | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186252 | (TP for BL CR for TS 38.423): Addition of missing Cause value | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186253 | [TP BL CR TS 38.413] Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑186254 | Potential Impacts of Higher Layer Multi-Connectivity related to the Key Issue 1 | Ericsson | imported from 3GU |
| R3‑186255 | Correction on PDCP SN length | CATT | imported from 3GU |
| R3‑186256 | (TP for NR BL CR for TS 38.300): Handling end marker in inter-system HO | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186257 | Architecture options for NTN | THALES | imported from 3GU |
| R3‑186258 | Correction on PDCP SN length | CATT | imported from 3GU |
| R3‑186259 | pCR on comparison of IAB architectures | Qualcomm | imported from 3GU |
| R3‑186260 | TP to TR 38.874: Way Forward on F1-AP Termination for CP Alternatives of Architecture Group 1a | Ericsson, AT&T, KDDI, Qualcomm | imported from 3GU |
| R3‑186261 | LS on rejected PDU sessions | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186262 | LS on Adding PCI information for SSBs on Xn | nokia | imported from 3GU |
| R3‑186263 | TP on IAB with NSA operation | AT&T | imported from 3GU |
| R3‑186264 | Skeleton for TR 37.816 | CMCC | imported from 3GU |
| R3‑186265 | Baseline CR for TS 38.463 | Ericsson | imported from 3GU |
| R3‑186266 | Baseline CR for TS 38.423 | Ericsson LM | imported from 3GU |
| R3‑186267 | Baseline CR for TS 37.340 | ZTE Corporation | imported from 3GU |
| R3‑186268 | Draft TR 37.816 v0.1.0 | CMCC | imported from 3GU |
| R3‑186269 | TR 38.821 v0.2.0 | Thales | imported from 3GU |
page generated from database: 2024-04-22 07:58:53