3GPP TDocs (written contributions) at meeting
Meeting: R3-102 - 2018-11-12 to 2018-11-16, Spokane
meeting id: R3-102 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| R3‑186270 | RAN3#102 Meeting agenda | Chairman (Ericsson) | imported from 3GU |
| R3‑186271 | RAN3#101Bis Meeting report | MCC Support | imported from 3GU |
| R3‑186272 | LS on RRC establishment cause in RRC reestablishment fallback case | 3GPP CT1, Huawei | imported from 3GU |
| R3‑186273 | Reply LS on LS on the Impacts of increasing the MAC-I and NAS-MAC size | 3GPP CT1, Huawei | imported from 3GU |
| R3‑186274 | Reply LS on inclusion of selected PLMN into the complete message | 3GPP CT1, Samsung | imported from 3GU |
| R3‑186275 | LS on RAN1 NR UE features update | 3GPP RAN1, NTT Docomo | imported from 3GU |
| R3‑186276 | LS on TX Profiles Provisioning | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑186277 | LS on UP-EDT procedure when resuming in a new eNB | 3GPP RAN2, Intel | imported from 3GU |
| R3‑186278 | Reply LS on "" LS on Using same counter in EDCE5"" | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑186279 | Reply LS on L2 measurements | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑186280 | LS on RRC establishment cause in RRC reestablishment fallback case | 3GPP RAN2, Sharp | imported from 3GU |
| R3‑186281 | Reply LS on optimisation of UE capability signalling | 3GPP RAN2, Mediatek | imported from 3GU |
| R3‑186282 | Reply LS on initial NAS security agreements | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑186283 | LS on requesting study of system level aspects of NR-U | 3GPP RAN2, Qualcomm | imported from 3GU |
| R3‑186284 | LS on TSN requirements evaluation | 3GPP RAN2, Nokia | imported from 3GU |
| R3‑186285 | LS on UE identity to calculate PF and PO in NR | 3GPP RAN2, Ericsson | imported from 3GU |
| R3‑186286 | LS on drb-Identity assignment in EN-DC | 3GPP RAN2, NTT Docomo | imported from 3GU |
| R3‑186287 | Reply LS on security requirements for RRC connection release | 3GPP RAN2, Intel | imported from 3GU |
| R3‑186288 | LS on RNAU without context relocation | 3GPP RAN2, Huawei | imported from 3GU |
| R3‑186289 | LS on Core Network Overload Control with ‘option 5 enabled eNB’ | 3GPP SA2, Vodafone | imported from 3GU |
| R3‑186290 | LS reply on energy efficiency of 5G | 3GPP SA5, Orange | imported from 3GU |
| R3‑186291 | Reply LS on Slice related Data Analytics | 3GPP SA5, China Mobile | imported from 3GU |
| R3‑186292 | Baseline CR for TS 38.401 | NEC | imported from 3GU |
| R3‑186293 | Baseline CR for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186294 | Baseline CR for TS 38.423 | Ericsson | imported from 3GU |
| R3‑186295 | Baseline CR for TS 38.463 | Ericsson | imported from 3GU |
| R3‑186296 | Baseline CR for TS 37.340 | ZTE Corporation | imported from 3GU |
| R3‑186297 | Baseline CR for TS 38.300 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186298 | (TP for BL CR for TS 38.423): Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186299 | (TP for BL CR for TS 38.422): Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186300 | Addition of EN-DC description | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186301 | Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑186302 | [DRAFT] Response LS on RLC mode reconfiguration | Nokia, Huawei | imported from 3GU |
| R3‑186303 | (TP for NR BL CR for TS 37.340): DRB ID assignment between MN and SN | Nokia, Nokia Shanghai Bell, ZTE, Intel Corporation | imported from 3GU |
| R3‑186304 | (TP for BL CR for TS 38.423): Integrity-check failure of uplink PDUs received from the MN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186305 | Addition of band 53 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186306 | Addition of band 53 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186307 | Reply LS on Return from UTRAN to NG-RAN for SRVCC from 5GS to UTRAN | 3GPP SA2, MediaTek | imported from 3GU |
| R3‑186308 | Reply LS on requesting study of system level aspects of NR-U | 3GPP SA2, Nokia | imported from 3GU |
| R3‑186309 | Reply LS on Issues with AS Release Assistance Indicator | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑186310 | Reply LS on Data Volume Reporting in 5GC | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑186311 | LS on redundant transmission for URLLC | 3GPP SA2, Huawei | imported from 3GU |
| R3‑186312 | LS on supporting low latency and low jitter during handover procedure | 3GPP SA2, Oppo | imported from 3GU |
| R3‑186313 | LS on QoS Monitoring | 3GPP SA2, Huawei | imported from 3GU |
| R3‑186314 | Reply LS on initial NAS security agreements | 3GPP SA2, Intel | imported from 3GU |
| R3‑186315 | Avoiding MME impacts from 3-byte TAC | 3GPP SA2, Qualcomm | imported from 3GU |
| R3‑186316 | Removal of the FFS on IAB Routing update procedure | KDDI Corporation | imported from 3GU |
| R3‑186317 | Detailed design on topology redundancy | KDDI Corporation | imported from 3GU |
| R3‑186318 | Text proposal for FFS resolution | KDDI Corporation | imported from 3GU |
| R3‑186319 | (TP for NR BL CR for TS 38.423) Corrections of Data Forwarding Info Related to S-NODE RELEASE REQUEST (CONFIRM) etc | ZTE | imported from 3GU |
| R3‑186320 | (TP for NR BL CR for TS 38.413) Correction of IMS Voice fallback over NGAP Aligning to SA2 | ZTE | imported from 3GU |
| R3‑186321 | Further Discussion on RAN Information Management | ZTE | imported from 3GU |
| R3‑186322 | (TP for NR BL CR for TS 38.413) Introduction of NR RAN Information Management Function | ZTE | imported from 3GU |
| R3‑186323 | Further Discussion on Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
| R3‑186324 | (TP for NR BL CR for TS 38.413) NGAP Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
| R3‑186325 | (TP for NR BL CR for TS 38.423) Correction of S-NODE Initiated SN Change due to ng-eNB | ZTE | imported from 3GU |
| R3‑186326 | TP of Descriptions for gNB-DU Processed Payload of Regenerative Satellite | ZTE | imported from 3GU |
| R3‑186327 | Further Consideration on Multi-Hop Scenarios in NTN | ZTE | imported from 3GU |
| R3‑186328 | Tracking Area Management and Paging Handling in NTN | ZTE | imported from 3GU |
| R3‑186329 | Further Discussion on UE Mobility Scenarios in NTN | ZTE | imported from 3GU |
| R3‑186330 | Further Discussion on Satellite Mobility Impacts on NTN Interfaces | ZTE | imported from 3GU |
| R3‑186331 | (TP for NR BL CR for TS 38.413) Correction of AMF Pointer | ZTE | imported from 3GU |
| R3‑186332 | (TP for NR BL CR for TS 38.413) Support Indicator of Timer Approach for GUAMI Removal | ZTE | imported from 3GU |
| R3‑186333 | On including S-NSSIA in NG paging message | China Telecommunications | imported from 3GU |
| R3‑186334 | On signalling the complete slice information to NG-RAN | China Telecommunications | imported from 3GU |
| R3‑186335 | (TP for NR BL CR for TS 38.423) Corrections of UP Address Info Related to SN Modification etc | ZTE | imported from 3GU |
| R3‑186336 | (TP for NR BL CR for TS 38.423) Correction of SN Initiated PDU Session Modification Required (Confirm) Info | ZTE | imported from 3GU |
| R3‑186337 | (TP for NR BLCR for TS 38.413) Further Correction of NGAP RRC Inactive Transition Report | ZTE | imported from 3GU |
| R3‑186338 | (TP for NR BL CR for TS 38.423) Correction of RAN Paging due to ng-eNB | ZTE | imported from 3GU |
| R3‑186339 | (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‑186340 | (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‑186341 | (TP for NR BLCR for TS 38.413) Further Correction of PDU Session Aggregate Maximum Bit Rate | ZTE | imported from 3GU |
| R3‑186342 | (TP for NR BL CR for TS 38.423) Correction of PDU Session Aggregate Maximum Bit Rate | ZTE | imported from 3GU |
| R3‑186343 | (TP for NR BL CR for TS 38.413) Interaction Between NG Notify and PDU Session Resource Modify Procedures | ZTE | imported from 3GU |
| R3‑186344 | (TP for NR BL CR for TS 38.413) Alignment of NG Setup with S1 Setup Handling | ZTE | imported from 3GU |
| R3‑186345 | (TP for NR BL CR for TS 38.413) Alignment of NG Setup with S1 Setup Handling | ZTE | imported from 3GU |
| R3‑186346 | (TP for NR BL CR for TS 38.413) Correction of UE CONTEXT RELEASE COMPLETE | ZTE | imported from 3GU |
| R3‑186347 | 36.300 CR on Correction of Physical Layer Resource to Cell Resource | ZTE | imported from 3GU |
| R3‑186348 | (TP for BL CR for TS 37.340): Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
| R3‑186349 | (TP for BL CR for TS 37.340): Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
| R3‑186350 | (TP for BL CR for TS 38.413) Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
| R3‑186351 | Issues on V2X Service Authorization and UE Sidelink AMBR in NG-RAN | LG Electronics | imported from 3GU |
| R3‑186352 | Add the UE TNLA Binding release and overload control procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186353 | Issues of F1 interface to support NR sidelink resource allocation mode 1 and mode 2 | LG Electronics | imported from 3GU |
| R3‑186354 | NTN architecture with regenerative satellite | THALES | imported from 3GU |
| R3‑186355 | NTN architecture with transparent satellite | THALES | imported from 3GU |
| R3‑186356 | NTN multi connectivity | THALES | imported from 3GU |
| R3‑186357 | Summary on RLC mode indication in R3-186079 | ZTE | imported from 3GU |
| R3‑186358 | Summary on RLC mode indication in R3-186079 | ZTE | imported from 3GU |
| R3‑186359 | Discussion on open issues on RLC mode indication | ZTE | imported from 3GU |
| R3‑186360 | CR for modification of presence of RLC mode indication in 36.423 | ZTE | imported from 3GU |
| R3‑186361 | (TP for BL CR for TS 38.423) Modification of presence of RLC mode indication | ZTE | imported from 3GU |
| R3‑186362 | (TP for BL CR for TS 38.423): Consideration on pre-allocation method on DL TNL address allocation at SN | ZTE | imported from 3GU |
| R3‑186363 | (TP for BL CR for TS 38.423): Consideration on UE Inactivity time transmission | ZTE | imported from 3GU |
| R3‑186364 | Discussion on CR Management | SPRINT Corporation | imported from 3GU |
| R3‑186365 | (TP for NR BL CR for TS 38.423) Cell information related to wideband carrier | ZTE | imported from 3GU |
| R3‑186366 | (TP for NR BL CR for TS 38.463):Remaining issue on QoS flow to DRB mapping in case CP-UP separating | ZTE | imported from 3GU |
| R3‑186367 | (TP for NR BL CR for TS 38.463):Remaining issue on QoS flow to DRB mapping in case CP-UP separating | ZTE | imported from 3GU |
| R3‑186368 | Considerations on NTN mobility | CATT | imported from 3GU |
| R3‑186369 | Consideration on synchronization | CATT | imported from 3GU |
| R3‑186370 | Discussion on NR eV2X | CATT | imported from 3GU |
| R3‑186371 | Discussion on IAB failure | CATT | imported from 3GU |
| R3‑186372 | (TP for TS 38.463) Correction on Data Forwarding Information IEs | CATT | imported from 3GU |
| R3‑186373 | (TP for TS 38.423) correction to RAN Paging | CATT | imported from 3GU |
| R3‑186374 | (TP for BL CR for TS 38.423): Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
| R3‑186375 | Support of RLC mode reconfiguration | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186376 | (TP for BL CR for TS 38.423): Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186377 | On Multiple TNL Associations for F1 and Xn | Intel Corporation | imported from 3GU |
| R3‑186378 | On Multiple TNL Associations for NG | Intel Corporation | imported from 3GU |
| R3‑186379 | [TP for BL CR for NGAP] On Multiple TNL Associations for NG | Intel Corporation | imported from 3GU |
| R3‑186380 | (TP for NR BL CR for TS 38.423): Correction to RNAU without context relocation | Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑186381 | Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186382 | (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‑186383 | (TP for NR BL CR for TS 38.413): Support of RAN initiated multiple SCTP | Huawei | imported from 3GU |
| R3‑186384 | Correction on gNB-CU/DU Configuration Update | Huawei | imported from 3GU |
| R3‑186385 | (TP for NR BL CR for TS 38.413): Corrections on RAN/AMF Configuration Update | Huawei | imported from 3GU |
| R3‑186386 | (TP for BL CR for TS 37.340): Data Volume Report for MR-DC | Nokia, Nokia Shanghai Bell, Qualcomm | imported from 3GU |
| R3‑186387 | (TP for BL CR for TS 38.413): Data Volume Report for MR-DC | Nokia, Nokia Shanghai Bell , Qualcomm | imported from 3GU |
| R3‑186388 | (TP for BL CR for TS 37.340): Correction of 5GC initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186389 | (TP for BL CR for TS 38.413): Correction of 5GC initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186390 | Removal of UE NAS PDU in PDU Session Setup | Huawei | imported from 3GU |
| R3‑186391 | Selection of forwarding for RAN initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186392 | (TP for BL CR for TS 37.340): RAN initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186393 | (TP for NR BL CR for TS 38.423): Corrections on NG-RAN node Configuration Update | Huawei | imported from 3GU |
| R3‑186394 | (TP for BL CR for TS 38.413): RAN initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186395 | (TP for BL CR for TS 38.413): Correction of NSSAI for paging | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186396 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186397 | Conclusion on Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186398 | (TP for BL CR for TS 38.423): Source TEID reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186399 | (TP for BL CR for TS 38.463): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186400 | (TP for BL CR for TS 38.413): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186401 | (TP for BL CR for TS 38.413): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑186402 | (TP for BL CR for TS 38.463): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑186403 | (TP for NR BL CR for TS 38.423) AMF Pool Information | Huawei | imported from 3GU |
| R3‑186404 | (TP for BL CR for TS 38.300): Further Correction of QoS paramaters | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186405 | (TP for BL CR for TS 38.423): Correction of slice resource | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186406 | (TP for BL CR for TS 38.413): Correction of slice resource | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186407 | (TP for BL CR for TS 38.413): Correction of Allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186408 | (TP for BL CR for TS 38.413): Correction of IMS Voice Fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186409 | (TP for BL CR for TS 38.413): Correction of PDU Session indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186410 | IP Version of Transport Layer Address | Huawei | imported from 3GU |
| R3‑186411 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑186412 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑186413 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑186414 | Correction on transport layer address | Huawei | imported from 3GU |
| R3‑186415 | Considerations on Satellite-Gateway Link for Non-terrestrial Networks | ETRI | imported from 3GU |
| R3‑186416 | Downselection consideration on IAB architecture group 1 | ZTE Corporation | imported from 3GU |
| R3‑186417 | Consideration on IAB architecture group 1 and 2 | ZTE Corporation | imported from 3GU |
| R3‑186418 | Discussion on user plane many-to-one bearer mapping | ZTE Corporation | imported from 3GU |
| R3‑186419 | Discussion on backhaul bearer setup in IAB network | ZTE Corporation | imported from 3GU |
| R3‑186420 | Discussion on IAB node discovery and selection | ZTE Corporation | imported from 3GU |
| R3‑186421 | Discussion on backhaul link failure and recovery | ZTE Corporation | imported from 3GU |
| R3‑186422 | Considerations on NR V2X | ZTE Corporation | imported from 3GU |
| R3‑186423 | TR 38.885 (for information) | Huawei | imported from 3GU |
| R3‑186424 | Proposed skeleton for RAN3 part of TR 38.885 | Huawei | imported from 3GU |
| R3‑186425 | NR V2X Service Authorization | Huawei | imported from 3GU |
| R3‑186426 | UE Sidelink AMBR in NG-RAN | Huawei | imported from 3GU |
| R3‑186427 | F1 signalling for SL resources | Huawei | imported from 3GU |
| R3‑186428 | Slicing for V2X | Huawei | imported from 3GU |
| R3‑186429 | (TP for NR BL CR for 38.413) NSSAI and Paging Messages | Huawei | imported from 3GU |
| R3‑186430 | [draft] Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Huawei | imported from 3GU |
| R3‑186431 | Addition of UAC assistance information | Huawei | imported from 3GU |
| R3‑186432 | Addition of UAC assistance information | Huawei | imported from 3GU |
| R3‑186433 | (TP for NR BL CR for 38.413) RNA update for overload control | Huawei | imported from 3GU |
| R3‑186434 | Rapporteur CR to align tabular | Huawei | imported from 3GU |
| R3‑186435 | Rapporteur CR to 38.470 | Huawei | imported from 3GU |
| R3‑186436 | Rapporteur CR to align ASN.1 | Huawei | imported from 3GU |
| R3‑186437 | Correction of maxnoofBPLMNs | Huawei | imported from 3GU |
| R3‑186438 | Correction ofmaxnoofBPLMNs | Huawei | imported from 3GU |
| R3‑186439 | (TP for NR BL CR for 38.463) Correction of maxnoofSPLMNs | Huawei | imported from 3GU |
| R3‑186440 | TP for Soft Topology Adaption | OMESH Technologies Co. Ltd. | imported from 3GU |
| R3‑186441 | TP on Soft Topology Adaptation | OMESH Technologies Co. Ltd. | imported from 3GU |
| R3‑186442 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186443 | (TP for TS 38.413 BL CR): Rapporteur cleanup | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186444 | (TP for TS 38.413 BL CR): Resolution of editor’s notes | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑186445 | (TP for TS 38.413 BL CR): Encoding of RRC Establishment Cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186446 | (TP for TS 38.413 BL CR): Warning Area Coordinates | Nokia, Nokia Shanghai Bell, AT&T, T-Mobile USA Inc., Apple, One2many, Qualcomm Incorporated, SyncTechno Inc. | imported from 3GU |
| R3‑186447 | (TP for TS 38.423 BL CR): Mandatory S-NSSAI | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Qualcomm Incorporated | imported from 3GU |
| R3‑186448 | Assistance information for MeNB-SgNB UE-level resource coordination | Ericsson | imported from 3GU |
| R3‑186449 | CR to TS 36.423 Assistance information for MeNB-SgNB UE-level resource coordination | Ericsson | imported from 3GU |
| R3‑186450 | UP retransmission status reporting in the NR UP protocol | Ericsson | imported from 3GU |
| R3‑186451 | CR to TS 38.425 UP retransmission status reporting in the NR UP protocol | Ericsson | imported from 3GU |
| R3‑186452 | DDDS polling clarification | Ericsson | imported from 3GU |
| R3‑186453 | CR to TS 38.425 DDDS polling clarification | Ericsson | imported from 3GU |
| R3‑186454 | TR 38.874 v060 | Qualcomm Incorporated | imported from 3GU |
| R3‑186455 | IAB backhaul RLF recovery for arch 1a | Qualcomm Incorporated, Ericsson, AT&T, Nokia, Huawei, Samsung | imported from 3GU |
| R3‑186456 | IAB inter-CU Topology Adaptation for Arch 1a | Qualcomm Incorporated, Nokia, Samsung | imported from 3GU |
| R3‑186457 | (TP for BL CR for TS 37.340): Inter-system Handover between SA and NSA | Qualcomm Incorporated | imported from 3GU |
| R3‑186458 | (TP for BL CR for TS 38.423): LTE-NR UE Level Resource Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
| R3‑186459 | TNL Information Delivery for flow level offload | Qualcomm Incorporated | imported from 3GU |
| R3‑186460 | (TP for BL CR for TS 37.340): TNL Information Delivery for flow level offload | Qualcomm Incorporated | imported from 3GU |
| R3‑186461 | Criticality Correction for X2AP UE-ID | Qualcomm Incorporated | imported from 3GU |
| R3‑186462 | Dynamic cell group configuration | Qualcomm Incorporated | imported from 3GU |
| R3‑186463 | Remote Interference Mitigation by Backhaul coordination | Qualcomm Incorporated | imported from 3GU |
| R3‑186464 | (TP for BL CR for TS 38.413): UE Interested slices | Qualcomm Incorporated,T-Mobile USA, CATT, CMCC | imported from 3GU |
| R3‑186465 | Discussion on supporting inter-system HO without MME Impacts | Qualcomm Incorporated | imported from 3GU |
| R3‑186466 | Avoiding mandatory MME impacts from 3-byte TAC | Qualcomm Incorporated | imported from 3GU |
| R3‑186467 | Draft Reply LS on Avoiding MME impacts from 3-byte TAC | Qualcomm Incorporated | imported from 3GU |
| R3‑186468 | (TP for NR BL CR for TS 38.413) Corrections on security handling | Qualcomm Incorporated | imported from 3GU |
| R3‑186469 | (TP for NR BL CR for TS 38.423) Corrections on security handling | Qualcomm Incorporated | imported from 3GU |
| R3‑186470 | Enforcement of UE’s maximum bit rate for Integrity Protection | Qualcomm Incorporated | imported from 3GU |
| R3‑186471 | Draft LS on Enforcement of maximum supported data rate for integrity protection | Qualcomm Incorporated | imported from 3GU |
| R3‑186472 | (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‑186473 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑186474 | TP to TR 38.866: The way forward on RIM backhaul RIM frameworks | Ericsson | imported from 3GU |
| R3‑186475 | TP for TR 38.866 on the realization of RIM backhaul communication | Ericsson | imported from 3GU |
| R3‑186476 | [Draft] LS on RIM backhaul framework | Ericsson | imported from 3GU |
| R3‑186477 | TP for TR 38.866: The open issues in RIM | Ericsson | imported from 3GU |
| R3‑186478 | TP to TR 38.866: The RAN3 agreements from RAN3#101bis | Ericsson | imported from 3GU |
| R3‑186479 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑186480 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑186481 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑186482 | En-gNB X2 TNL address discovery | Huawei | imported from 3GU |
| R3‑186483 | (TP for BL CR for TS 38.423): Support of data forwarding for RRC reestablishment UE | Huawei | imported from 3GU |
| R3‑186484 | (TP for BL CR for TS 38.300): Support of data forwarding for RRC reestablishment UE | Huawei | imported from 3GU |
| R3‑186485 | (TP for BL CR for TS 38.423): Correction to UE Context Release | Huawei | imported from 3GU |
| R3‑186486 | (TP for BL CR for TS 38.423): Corrections to Retrieve UE Context Request | Huawei | imported from 3GU |
| R3‑186487 | (TP for BL CR for TS 38.423): Adding UE History Information in Retrieve UE Context | Huawei | imported from 3GU |
| R3‑186488 | (TP for BL CR for TS 38.423): Correction to Neighbour Information NR | Huawei | imported from 3GU |
| R3‑186489 | (TP for BL CR for TS 38.423): SSB type indication over Xn | Huawei | imported from 3GU |
| R3‑186490 | SSB type indication over X2 | Huawei | imported from 3GU |
| R3‑186491 | SSB type indication over F1 | Huawei | imported from 3GU |
| R3‑186492 | [DRAFT] LS on adding SSB type in the MTC inter-node message | Huawei | imported from 3GU |
| R3‑186493 | gNB Grouping and Set ID Design | Huawei | imported from 3GU |
| R3‑186494 | RIM Xn procedure | Huawei | imported from 3GU |
| R3‑186495 | RIM NG procedure | Huawei | imported from 3GU |
| R3‑186496 | Presence of Reference ID in Location Reporting Control | Huawei | imported from 3GU |
| R3‑186497 | [Draft] LS on Presence of Reference ID in Location Reporting Control | Huawei | imported from 3GU |
| R3‑186498 | TP on Inter-gNB Coordination for RIM With Core Network Involvement | ZTE | imported from 3GU |
| R3‑186499 | Discussion on RLC reestablishment indication for MR-DC | ZTE Corporation | imported from 3GU |
| R3‑186500 | RLC reestablishment indication for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑186501 | (TP for NR BL CR for TS 38.413) Clarification on AMF Status Indication | ZTE Corporation | imported from 3GU |
| R3‑186502 | Multiple SCTP associations support over F1&NG interface | ZTE Corporation | imported from 3GU |
| R3‑186503 | (TP for NR BL CR for TS 38.413) Multiple SCTP Associations Support over NG Interface | ZTE Corporation | imported from 3GU |
| R3‑186504 | Multiple SCTP Associations Support over F1 Interface | ZTE Corporation | imported from 3GU |
| R3‑186505 | TP for gNB Grouping and Set ID Design | ZTE | imported from 3GU |
| R3‑186506 | (TP for NR BL CR for TS 38.300) Energy Saving Support for NR in R15 | ZTE, China Unicom, CMCC, China Telecom | imported from 3GU |
| R3‑186507 | pCR IAB_Arch_recommnedation(1a,1b and 2a) | KDDI Corporation | imported from 3GU |
| R3‑186508 | Energy Saving Support over F1 Interface | ZTE, China Telecom, CMCC, China Unicom | imported from 3GU |
| R3‑186509 | Left issue for ANR of option 3 | ZTE Corporation | imported from 3GU |
| R3‑186510 | TP for Intra-cluster coordination | ZTE | imported from 3GU |
| R3‑186511 | Discussion on Reusing Source TEID at Handover | ZTE Corporation | imported from 3GU |
| R3‑186512 | (TP for NR BL CR for TS 38.413) Overload Control for UAC | ZTE Corporation, CMCC, NTT Docomo | imported from 3GU |
| R3‑186513 | Discusson on retransmisson status report in DDDS | ZTE Corporation | imported from 3GU |
| R3‑186514 | Corrections on retransmission status feedback for TS38.425 | ZTE Corporation | imported from 3GU |
| R3‑186515 | (TP for BL CR for TS38.423) Update on Measurement Gap Configuration for MR-DC | ZTE Corporation | imported from 3GU |
| R3‑186516 | PDU session failed to be released due to handover | Huawei | imported from 3GU |
| R3‑186517 | Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑186518 | Wayforward on RRC Re-establishment and RAN Sharing discussion | KDDI Corporation, Samsung, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186519 | Issues on X2&Xn AP Services | ZTE Corporation | imported from 3GU |
| R3‑186520 | Route selection method for architecture 1a | Huawei | imported from 3GU |
| R3‑186521 | Corrections on X2AP services for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑186522 | (TP for NR BL CR for TS38.423) Corrections on XnAP services for TS38.423 | ZTE Corporation | imported from 3GU |
| R3‑186523 | Discussion on Access Control Information over F1 interface | ZTE Corporation | imported from 3GU |
| R3‑186524 | Topology Table Establishment and Update | Huawei | imported from 3GU |
| R3‑186525 | CR to TS38.473 on Access Control Information over F1 interface | ZTE Corporation | imported from 3GU |
| R3‑186526 | Remaining issue on QoS flow to DRB mapping in case CP-UP separating | ZTE Corporation | imported from 3GU |
| R3‑186527 | Discussion on PLMN information for RRC Resume/Reestablishment | ZTE Corporation | imported from 3GU |
| R3‑186528 | (TP for BL CR for TS38.423)Update on Retrieve UE Context message | ZTE Corporation | imported from 3GU |
| R3‑186529 | Principal Steps of Inter-CU Topology Adaptation | Huawei | imported from 3GU |
| R3‑186530 | Update on Retrieve UE Context Request message for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑186531 | (TP for BL CR for TS38.300)Clarification for PLMN specific interface in case of RAN sharing | ZTE Corporation | imported from 3GU |
| R3‑186532 | (TP for BL CR for TS36.300)Clarification for PLMN specific interface in case of RAN sharing | ZTE Corporation | imported from 3GU |
| R3‑186533 | (TP for BL CR for TS38.423)Update on NR Served Cell Information | ZTE Corporation | imported from 3GU |
| R3‑186534 | Update on NR Served Cell Information for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑186535 | Update on NR Served Cell Information for TS38.473 | ZTE Corporation | imported from 3GU |
| R3‑186536 | Security Key indication in case of PDCP wraparound | ZTE Corporation | imported from 3GU |
| R3‑186537 | Consideration on accurate reference timing delivery in TSN related enhancements for NR-IIoT | ZTE Corporation | imported from 3GU |
| R3‑186538 | CP signalling transmission in IAB NSA | Huawei | imported from 3GU |
| R3‑186539 | Reply LS on TSN requirements evaluation | ZTE Corporation | imported from 3GU |
| R3‑186540 | Considersion on Resource-Efficient PDCP Duplication | ZTE Corporation | imported from 3GU |
| R3‑186541 | Description of the architecture for gNB-DU processed payload of regenerative satellite | ZTE Corporation | imported from 3GU |
| R3‑186542 | Tracking Area Management and Paging Handling in NTN | ZTE Corporation | imported from 3GU |
| R3‑186543 | Support of LTE Access over NR backhaul in Architecture 1a | Huawei | imported from 3GU |
| R3‑186544 | Slice Requirement Assurance for IAB E2E Link | Huawei | imported from 3GU |
| R3‑186545 | IAB bearer mapping decisions | Huawei | imported from 3GU |
| R3‑186546 | Correction on PDCP SN length on F1 | CATT | imported from 3GU |
| R3‑186547 | (TP for TS38.413) Support of paging DRX for CU/DU split scenario | CATT | imported from 3GU |
| R3‑186548 | Introduction of Default Paging DRX on F1 | CATT | imported from 3GU |
| R3‑186549 | (TP for TS38.413)Support of PDU session split during Xn handover procedure | CATT | imported from 3GU |
| R3‑186550 | (TP for TS38.423)Support of PDU session split during Xn handover procedure | CATT | imported from 3GU |
| R3‑186551 | (TP for TS 37.340) Correction on PCI confusion | CATT | imported from 3GU |
| R3‑186552 | Consideration on access control related information transfer over F1 | CATT | imported from 3GU |
| R3‑186553 | Access control related information transfer over F1(Alterniatve 2) | CATT | imported from 3GU |
| R3‑186554 | Access control related information transfer over F1(Alterniatve 3) | CATT | imported from 3GU |
| R3‑186555 | TP on introducing SMTC information for NR neighbour cell | CATT,CMCC | imported from 3GU |
| R3‑186556 | Discussion on F1AP IEs for MR-DC coordination | CATT | imported from 3GU |
| R3‑186557 | CR for TS 38.473 for MR-DC coordination | CATT | imported from 3GU |
| R3‑186558 | Discussion on Xn TNL addresses for NG-RAN DC | CATT | imported from 3GU |
| R3‑186559 | Discussion on System Information Update | CATT,NEC | imported from 3GU |
| R3‑186560 | Support of system information update for active UE | CATT | imported from 3GU |
| R3‑186561 | Discussion on RRC version in DC | CATT | imported from 3GU |
| R3‑186562 | Discussion on SA2 LS on supporting low latency and low jitter during handover procedure | OPPO | imported from 3GU |
| R3‑186563 | [Draft] Reply on LS on supporting low latency and low jitter during handover procedure (KI#2) in FS_URLLC | OPPO | imported from 3GU |
| R3‑186564 | QoS parameters for IAB QoS handling | Huawei | imported from 3GU |
| R3‑186565 | SRB Types for Control Plane Alternative 2 | Huawei | imported from 3GU |
| R3‑186566 | Discussion on End marker for QoS flow offloading | CATT | imported from 3GU |
| R3‑186567 | Consideration on PDCP duplication state at network side | CATT | imported from 3GU |
| R3‑186568 | Discussion on impacts of Higher Layer Multi-Connectivity | CATT | imported from 3GU |
| R3‑186569 | Discussion on gNB set ID define | CATT | imported from 3GU |
| R3‑186570 | Discussion on message routing for RIM | CATT | imported from 3GU |
| R3‑186571 | IAB architecture down-selection | Samsung | imported from 3GU |
| R3‑186572 | Clarification on “Highest NR PDCP PDU SN” | Samsung | imported from 3GU |
| R3‑186573 | CR for clarification on highest NR PDCP PDU SN | Samsung | imported from 3GU |
| R3‑186574 | SCell information for RLC failure | Samsung | imported from 3GU |
| R3‑186575 | CR on Scell release for RLC failure | Samsung | imported from 3GU |
| R3‑186576 | (TP for BL CR for TS 37.340): TNL Address Allocation for SN Terminated Bearer | Samsung | imported from 3GU |
| R3‑186577 | (TP for BL CR for TS 38.423): TNL Address Allocation for SN Terminated Bearer | Samsung | imported from 3GU |
| R3‑186578 | (TP for BL CR for TS 37.340): PDU Session Split in MR-DC | Samsung | imported from 3GU |
| R3‑186579 | (TP for BL CR for TS 38.413): PDU Session Split in MR-DC | Samsung | imported from 3GU |
| R3‑186580 | (TP for BL CR for TS 38.423): PDU Session Split in MR | Samsung | imported from 3GU |
| R3‑186581 | [DRAFT] LS on PDU session split | Samsung | imported from 3GU |
| R3‑186582 | Discussion on deduction of NG-RAN node ID length | Samsung | imported from 3GU |
| R3‑186583 | Support on DRB-ID assignment for EN-DC | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186584 | [Draft] Reply LS on drb-Identity assignment in EN-DC | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186585 | Way forward on CP alternatives of architecture group 1a | Huawei | imported from 3GU |
| R3‑186586 | Support of Multiple connectivity for IAB nodes | Huawei | imported from 3GU |
| R3‑186587 | Considerations on the issues for MR-DC based NR V2X | LG Electronics | imported from 3GU |
| R3‑186588 | Further discussion on multiple SCTP over F1 | Huawei | imported from 3GU |
| R3‑186589 | (TP for NR BL CR for TS 38.401)TP for Miscellaneous corrections in 38.401 | NEC, Google | imported from 3GU |
| R3‑186590 | Retransmission status in UP | NEC | imported from 3GU |
| R3‑186591 | Retransmission status in UP | NEC | imported from 3GU |
| R3‑186592 | BWP impact on F1 interface due to System Information updating | NEC, CATT | imported from 3GU |
| R3‑186593 | (TP for NR BL CR for TS 38.401) Cell Failed to Be Activated | NEC | imported from 3GU |
| R3‑186594 | Cell Failed to Be Activated | NEC | imported from 3GU |
| R3‑186595 | (TP for NR BL CR for TS 38.423): Correction of the presence of the Paging DRX IE | NEC | imported from 3GU |
| R3‑186596 | (TP for NR BL CR for TS 38.423): Adding semantics description for I-RNTI | NEC, Huawei | imported from 3GU |
| R3‑186597 | (TP for NR BL CR for TS 38.423): supporting lossless HO with QoS flow remapping | NEC | imported from 3GU |
| R3‑186598 | (TP for NR BL CR for TS 38.300): supporting lossless HO with QoS flow remapping | NEC | imported from 3GU |
| R3‑186599 | [DRAFT] Reply LS on drb-Identity assignment in EN-DC | NEC | imported from 3GU |
| R3‑186600 | Consideration on MBMS Service for V2X | LG Electronics | imported from 3GU |
| R3‑186601 | (TP for BL CR for TS 38.300): Correction of Emergency fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186602 | (TP for BL CR for TS 38.413): Correction of Emeregncy Fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186603 | Correction on the presence of PDU Session AMBR | Huawei | imported from 3GU |
| R3‑186604 | (TP for BL CR for TS 38.413): Correction of NAS PDU | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186605 | Possible prioritzation on RAN3 topic to achieve functional freeze of NR WI | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186606 | Access Control Information over F1 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186607 | CR on Access Control Information over F1 | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186608 | (TP for BL CR for TS 37.340)further consideration on Start end time stamp for data volume reporting | NTT DOCOMO, INC, Orange, China Mobile, KT Corp. | imported from 3GU |
| R3‑186609 | CR on alingment of terminology for eNB or MeNB | NTT DOCOMO, INC, Ericsson | imported from 3GU |
| R3‑186610 | (TP for BL CR for TS 38.401)Further consideration on cell State handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186611 | CR on cell state handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186612 | (TP for BL CR for TS 37.340)necessity on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186613 | High level overview of functions for LTE higher layer split | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186614 | Data forwarding on Inter-system HO | NTT DOCOMO, INC. | imported from 3GU |
| R3‑186615 | Way Forward for Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc. | imported from 3GU |
| R3‑186616 | (TP for BL CR for TS 38.300): Handling of end markers in 5g to 4g handovers | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc. | imported from 3GU |
| R3‑186617 | DRB release-addition and the DRB identity assignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186618 | Indication of DRB release-addition for SN-terminated bearers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186619 | [DRAFT] Reply LS on drb-Identity assignment in EN-DC | Nokia | imported from 3GU |
| R3‑186620 | (TP for NR BL CR for TS 38.413): Solution to Problem Statement 2 in previous summary on S-NSSAI in Paging | TTA | imported from 3GU |
| R3‑186621 | TR 38.866 V0.1.0 | CMCC | imported from 3GU |
| R3‑186622 | (TP to TR 38.866) Signalling flow without CN involvement for backhaul-based RIM framework | CMCC | imported from 3GU |
| R3‑186623 | (TP to TR 38.866) Signalling flow with CN involvement for backhaul-based RIM framework | CMCC | imported from 3GU |
| R3‑186624 | Xn termination and Xn based mobility in IAB | CMCC | imported from 3GU |
| R3‑186625 | Support for Accurate Reference Timing Delivery | CMCC | imported from 3GU |
| R3‑186626 | Clarification on cell management over F1 | CMCC | imported from 3GU |
| R3‑186627 | CR to TS 38.373 on corrections to cell management over F1 | CMCC | imported from 3GU |
| R3‑186628 | (TP for BL CR for TS 38.423) Configure and de-configure PDCP duplication | Huawei | imported from 3GU |
| R3‑186629 | PDU session split | Huawei | imported from 3GU |
| R3‑186630 | (TP for BL CR for TS 37.340): PDU session split | Huawei | imported from 3GU |
| R3‑186631 | (TP for BL CR for TS 38.413): PDU session split | Huawei | imported from 3GU |
| R3‑186632 | In-order delivery in MR-DC | Huawei | imported from 3GU |
| R3‑186633 | (TP for BL CR for TS 37.340): In-order delivery in MR-DC | Huawei | imported from 3GU |
| R3‑186634 | (TP for BL CR for TS 38.423): In-order delivery in MR-DC | Huawei | imported from 3GU |
| R3‑186635 | (TP for BL CR for TS 38.423): Support of DRB level offloading | Huawei | imported from 3GU |
| R3‑186636 | (TP for BL CR for TS 37.340): Clarification on UE AMBR and PDU session AMBR | Huawei | imported from 3GU |
| R3‑186637 | DRB ID assignment for EN-DC | Huawei | imported from 3GU |
| R3‑186638 | [DRAFT] Reply LS on DRB ID assignment for EN-DC | Huawei | imported from 3GU |
| R3‑186639 | (TP for BL CR for TS 38.413): Add missing abnormal conditions over NG | Huawei | imported from 3GU |
| R3‑186640 | (TP for BL CR for TS 38.423): Add missing abnormal conditions over Xn | Huawei | imported from 3GU |
| R3‑186641 | (TP for BL CR for TS 38.423): Xn-U DL TNL Address Allocation for SN terminated bearers | Huawei | imported from 3GU |
| R3‑186642 | (TP for BL CR for TS 37.340): Xn-U DL TNL Address Allocation for SN terminated bearers | Huawei | imported from 3GU |
| R3‑186643 | Further considerations on UL/DL data forwarding TEID | Huawei | imported from 3GU |
| R3‑186644 | Corrections on UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
| R3‑186645 | Introduction of DL Forwarding indication for bearer type change | Huawei | imported from 3GU |
| R3‑186646 | (TP for BL CR for TS 38.423) Paging for ng-eNB | Huawei | imported from 3GU |
| R3‑186647 | (TP for BL CR for TS 37.340) DRB ID Allocation in stage-2 | Huawei, Intel Corporation | imported from 3GU |
| R3‑186648 | Handling of RLC failure | Huawei | imported from 3GU |
| R3‑186649 | Handling of RLC failure | Huawei | imported from 3GU |
| R3‑186650 | (TP for BL CR for TS 37.340): Handling of RLC failure | Huawei | imported from 3GU |
| R3‑186651 | (TP for BL CR for TS 38.423): Handling of RLC failure | Huawei | imported from 3GU |
| R3‑186652 | (TP for BL CR for TS 38.423): PDU session split during handover | Huawei | imported from 3GU |
| R3‑186653 | (TP for BL CR for TS 38.413): PDU session split during handover | Huawei | imported from 3GU |
| R3‑186654 | (TP for BL CR for TS 38.423): Corrections on Served cell information | Huawei | imported from 3GU |
| R3‑186655 | (TP for BL CR for TS 38.423): Presence in QoS flow to be setup list | Huawei | imported from 3GU |
| R3‑186656 | (TP for BL CR for TS 38.423): Introduction of resource configuration | Huawei | imported from 3GU |
| R3‑186657 | (TP for BL CR for TS 37.340): Handling of the SN initiated DRB and flow release | Huawei | imported from 3GU |
| R3‑186658 | (TP for BL CR for TS 38.423): Handling of the SN initiated DRB and flow release | Huawei | imported from 3GU |
| R3‑186659 | (TP for BL CR for TS 38.423): Clarification on the usage of PCell ID | Huawei | imported from 3GU |
| R3‑186660 | Add missing description on non-operational X2 interface for EN-DC | Huawei | imported from 3GU |
| R3‑186661 | Tracking Area and UE position in NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186662 | Analysis on mobility aspects in NTN with earth-fixed beam | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186663 | Analysis on Interface management between satellite and network entity on ground | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186664 | Analysis on IPv6 address management in Architetcure Group 1a | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186665 | IAB Routing and Topology Management for Architecture 1a | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186666 | Consideration on eNB-CU UE W1AP ID and eNB-DU UE W1AP ID | Huawei, China Unicom,Orange | imported from 3GU |
| R3‑186667 | CR to 38.425 on supporting of W1 user Plane Protocol | Huawei, China Unicom, Orange, TIM | imported from 3GU |
| R3‑186668 | System Information handling by ng-eNB | Huawei, China Unicom | imported from 3GU |
| R3‑186669 | W1AP interface management procedures | Huawei, China Unicom | imported from 3GU |
| R3‑186670 | W1AP Paging procedure | Huawei, China Unicom | imported from 3GU |
| R3‑186671 | W1AP RRC message transfer procedures | Huawei, China Unicom | imported from 3GU |
| R3‑186672 | W1AP UE context management procedures | Huawei, China Unicom | imported from 3GU |
| R3‑186673 | pCR to 37.470 on W1AP functions and procedures | Huawei, China Unicom, TIM | imported from 3GU |
| R3‑186674 | Rapporteur’s CR for TS 38.462 | Huawei | imported from 3GU |
| R3‑186675 | Further discussions on network sharing | Huawei | imported from 3GU |
| R3‑186676 | (TP for NR BL CR for TS 38.423) on the clarification to RAN sharing and RRC re-establishment | Huawei | imported from 3GU |
| R3‑186677 | (TP for NR BL CR for 38.423) on common interface in case of RAN sharing | Huawei | imported from 3GU |
| R3‑186678 | CR to 38.473 on the clarification to RAN sharing | Huawei | imported from 3GU |
| R3‑186679 | CR to 36.423 on common interface in case of RAN sharing | Huawei | imported from 3GU |
| R3‑186680 | CR to 38.473 on clarification to the presence of UE AMBR | Huawei | imported from 3GU |
| R3‑186681 | Discussion on system Information Update for Active Ues | Huawei | imported from 3GU |
| R3‑186682 | CR to 38.473 on system Information Update for Active UEs | Huawei | imported from 3GU |
| R3‑186683 | Discussion on SRB duplication and LCID | Huawei | imported from 3GU |
| R3‑186684 | CR to 38.473 on SRB duplication and LCID | Huawei | imported from 3GU |
| R3‑186685 | (TP for NR BL CR for TS 38.463): on PDCP suspend indication over E1 interface | Huawei | imported from 3GU |
| R3‑186686 | CR to 38.460 on PDCP suspend indication over E1 interface | Huawei | imported from 3GU |
| R3‑186687 | (TP for NR BL CR for TS 38.463): Correction on gNB-CU-UP/CP Configuration Update | Huawei | imported from 3GU |
| R3‑186688 | (TP for NR BL CR for TS 38.401): on RRC state transition | Huawei | imported from 3GU |
| R3‑186689 | CR to 38.460 on inactivity notification over E1 | Huawei | imported from 3GU |
| R3‑186690 | (TP for NR BL CR for TS 38.463): on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑186691 | CR to 38.460 on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑186692 | CR to 38.473 on correction to gNB-CU and gNB-DU Configuration Update | Huawei | imported from 3GU |
| R3‑186693 | Selective duplication upon transmission failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186694 | Mobility issues in NTN | Huawei | imported from 3GU |
| R3‑186695 | Handling of Network Identities in NTN | Huawei | imported from 3GU |
| R3‑186696 | Consideration on the paging issues | Huawei | imported from 3GU |
| R3‑186697 | Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186698 | Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186699 | Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186700 | (TP for BL CR for TS 38.401): 5G Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186701 | EN-DC Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑186702 | [Draft] LS on UTRAN, E-UTRAN and 5G Antenna Interface Function specifications | Huawei | imported from 3GU |
| R3‑186703 | Replication framework in 3GPP system | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186704 | XnAP: Reminder on the purpose of Causes for MCG and SCG mobility | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186705 | TSN Time Synchronization | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186706 | [DRAFT] Reply LS on TSN requirements evaluation | Nokia | imported from 3GU |
| R3‑186707 | (TP for NR BL CR for TS 38.423) UE Context Release to S-Node | Google Inc. | imported from 3GU |
| R3‑186708 | IAB architecture down-selection | Samsung | imported from 3GU |
| R3‑186709 | Downlink Data Delivery Status Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186710 | Clarification on CU to DU RRC Info usage in UE Context Setup | Google Inc. | imported from 3GU |
| R3‑186711 | Discussion on Downlink Data Delivery Status Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186712 | Clarification on CU to DU RRC Info usage in UE Context Setup | Google Inc. | imported from 3GU |
| R3‑186713 | F1 Served Cell Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186714 | (TP for NR BL CR for TS 38.401) Clarification on Intra-gNB-CU mobility | Google Inc. | imported from 3GU |
| R3‑186715 | Clarification of Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186716 | Discussion on Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186717 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186718 | (TP for NR BL CR for TS 37.340) SN Status Transfer clarification | Google Inc. | imported from 3GU |
| R3‑186719 | Discussion on Bandwidth Part (BWP) Information Procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186720 | (TP for NR BL CR for TS 37.340) SN Modification Request in MR-DC | Google Inc. | imported from 3GU |
| R3‑186721 | (TP for NR BL CR for TS 38.463) UE Identification and Trace correlation over E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186722 | Clarification on “Highest NR PDCP PDU SN” | Samsung | imported from 3GU |
| R3‑186723 | CR for clarification on highest NR PDCP PDU SN | Samsung | imported from 3GU |
| R3‑186724 | SCell information for RLC failure | Samsung | imported from 3GU |
| R3‑186725 | CR on Scell release for RLC failure | Samsung | imported from 3GU |
| R3‑186726 | NTN hand-over types | THALES | imported from 3GU |
| R3‑186727 | (TP for NR BL CR for TS 38.463) Periodic Load Reporting for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186728 | F1 Periodic Load Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186729 | NTN hand-over types | THALES | imported from 3GU |
| R3‑186730 | (TP for BL CR for TS 38.300): Correction of stage 2 periodic RNA procedure | Huawei | imported from 3GU |
| R3‑186731 | F1 Served Cell Information (Alternative 2) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186732 | Introducing X2 TNL Address discovery for collocated en-gNB/gNB for EN-DC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
| R3‑186733 | TP to TR 38.866: The way forward on RIM backhaul RIM frameworks | Ericsson | imported from 3GU |
| R3‑186734 | R3-18xxxx TP for TR 38.866 on the realization of RIM backhaul communication | Ericsson | imported from 3GU |
| R3‑186735 | [Draft] LS on RIM backhaul framework | Ericsson | imported from 3GU |
| R3‑186736 | TP for TR 38.866: The open issues in RIM | Ericsson | imported from 3GU |
| R3‑186737 | TP to TR 38.866: The RAN3 agreements from RAN3#101bis | Ericsson | imported from 3GU |
| R3‑186738 | Mapping of CP data over backhaul links in IAB Architecture group 1a | Ericsson | imported from 3GU |
| R3‑186739 | Using NDS to protect F1 signaling without any standardization impact | Ericsson | imported from 3GU |
| R3‑186740 | P to TR 38.874: Harmonizing UP alternatives for Architecture group 1a | Ericsson, AT&T, KDDI, KT | imported from 3GU |
| R3‑186741 | TP to TR 38.874: IAB node Access Procedure for Architecture Group 1 | Ericsson | imported from 3GU |
| R3‑186742 | TP to TR 38.874: Setup Procedure for the Adaptation Layer of an IAB Network | Ericsson | imported from 3GU |
| R3‑186743 | TP to TR 38.874: End-to-end Flow Control in Multi-hop IAB Networks | Ericsson | imported from 3GU |
| R3‑186744 | TP to 38.874: Hop-by-hop Flow Control in Multi-hop IAB Networks | Ericsson | imported from 3GU |
| R3‑186745 | TP to TR 38.874: Supporting Network Slicing in IAB Networks | Ericsson | imported from 3GU |
| R3‑186746 | TP to TR 38.874: Minimizing the CN functionalities for IAB network | Ericsson | imported from 3GU |
| R3‑186747 | TP to TR 38.874: Using F1 Functionality to Support Redudant Paths | Ericsson, AT&T, KDDI | imported from 3GU |
| R3‑186748 | (TP for BL CR for TS 38.413): RRC establishment cause in RRC reestablishment fallback case | LG Electronics Inc. | imported from 3GU |
| R3‑186749 | Open issues on gNB grouping and set ID design | LG Electronics Inc. | imported from 3GU |
| R3‑186750 | Selection of IAB architecture for future work | LG Electronics Inc. | imported from 3GU |
| R3‑186751 | Inter-donor topology adaptation for architecture 1a | LG Electronics Inc. | imported from 3GU |
| R3‑186752 | Solutions for remaining MN/SN resource coordination key issues | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186753 | Further corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186754 | On network sharing deployments where CUs are not shared | Nokia, Nokia Shanghai Bell, KDDI | imported from 3GU |
| R3‑186755 | Common X2 instance between eNB and shared en-gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186756 | [TP for TR 38.866] Overall mechanism for inter- and intra-cluster coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186757 | Clarification to QoE Measurement Collection suspension by the eNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186758 | (TP for NR BL CR for TS 38.413) Inter-RAT ANR Scenarios | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186759 | (TP for NR BL CR for TS 38.423) Support for Data Volume Reporting in MR-DC with 5GC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186760 | Reply LS on Data Volume Reporting in 5GC | Qualcomm Incorporated | imported from 3GU |
| R3‑186761 | Architecture considerations for IAB | AT&T | imported from 3GU |
| R3‑186762 | Considerations for packet duplication with more than 2 copies | AT&T | imported from 3GU |
| R3‑186763 | New MDT requirements for NR | AT&T | imported from 3GU |
| R3‑186764 | NR-NTN: Tracking Areas Management | Fraunhofer IIS, Fraunhofer HHI | imported from 3GU |
| R3‑186765 | The consequences of including slicing information in NGAP Paging messages | Ericsson, CATT | imported from 3GU |
| R3‑186766 | The existing mechanisms for CP congestion mitigation in the RAN | Ericsson, CATT, China Telecom | imported from 3GU |
| R3‑186767 | [Draft] Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Ericsson | imported from 3GU |
| R3‑186768 | On slicing-based target cell selection | Ericsson | imported from 3GU |
| R3‑186769 | (TP for NR BL CR for TS 38.423) Common Xn link for network sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186770 | (TP for BL CR for TS 38.300): Handling End Markers in 4g to 5g handovers | Nokia, Nokia Shanghai Bell, Samsung, KT Corp., Huawei, ZTE, CMCC, Verizon Wireless, LG Electronics Inc., CATT, ETRI, KDDI, Google Inc | imported from 3GU |
| R3‑186771 | LS on handling of data forwarding and end markers for inter-system handovers | Nokia, Nokia Shanghai Bell, Samsung, KT Corp., Huawei, ZTE, CMCC, Verizon Wireless, LG Electronics Inc., CATT, ETRI, KDDI, Google Inc | imported from 3GU |
| R3‑186772 | Discussion on timing information for industrial IoT | Qualcomm Incorporated | imported from 3GU |
| R3‑186773 | Interaction between Suspend procedure and AS RAI | Qualcomm Incorporated | imported from 3GU |
| R3‑186774 | Reply LS on Issues with AS Release Assistance Indicator | Qualcomm Incorporated | imported from 3GU |
| R3‑186775 | 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‑186776 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.413 | Ericsson | imported from 3GU |
| R3‑186777 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.423 | Ericsson | imported from 3GU |
| R3‑186778 | Support for keeping RAN UP termination at DC – for 36.423 | Ericsson | imported from 3GU |
| R3‑186779 | CR Multiple TNLA over F1 transport | Ericsson | imported from 3GU |
| R3‑186780 | CR for F1 Multiple TNLA intialization | Ericsson | imported from 3GU |
| R3‑186781 | CR Multiple TNLA over E1 transport | Ericsson | imported from 3GU |
| R3‑186782 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
| R3‑186783 | Introducing X2 TNL Address discovery for en-gNBs for EN-D | Ericsson, Vodafone | imported from 3GU |
| R3‑186784 | Missing Transaction ID in non-UE-associated procedures | Ericsson | imported from 3GU |
| R3‑186785 | Introduction of EN-DC | Ericsson | imported from 3GU |
| R3‑186786 | SA2 discussions on averting further impact from EPS due to unavoidable interworking requirements with 5GS | Ericsson | imported from 3GU |
| R3‑186787 | [DRAFT] Response LS on Avoiding MME impacts from 3-byte TAC | Ericsson | imported from 3GU |
| R3‑186788 | Discussion on Data Volume Report for MR-DC | Ericsson | imported from 3GU |
| R3‑186789 | [TP for BL CR 37.340] Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑186790 | Introduction of Data Volume Reporting for MR-DC - 38.410 | Ericsson | imported from 3GU |
| R3‑186791 | [TP for BL CR 38.420] Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑186792 | [TP BL CR TS 38.413] Discussion on Data Volume Report | Ericsson | imported from 3GU |
| R3‑186793 | [TP for BL CR 38.423] Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑186794 | [TP for BL CR 38.463] Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑186795 | Replace Band table with reference to RAN4 specifications | Ericsson | imported from 3GU |
| R3‑186796 | Further discussion on issues with AS Release Assistance Indicator | Ericsson | imported from 3GU |
| R3‑186797 | Data Notification | Ericsson | imported from 3GU |
| R3‑186798 | Data Notification | Ericsson | imported from 3GU |
| R3‑186799 | Draft] Reply LS on Issues with AS Release Assistance Indicator | Ericsson | imported from 3GU |
| R3‑186800 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑186801 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑186802 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑186803 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑186804 | Data forwarding for inter-system HO with functions available from intra-system data forwarding - or: Why option 3 fulfils all requirements and should be chosen | Ericsson, China Telecom, Interdigital | imported from 3GU |
| R3‑186805 | [TP for BL CR for 38.300] for inter-system HO | Ericsson, Interdigital | imported from 3GU |
| R3‑186806 | [TP BL CR TS 38.413] Data forwarding handling between 4G and 5G | Ericsson, Interdigital | imported from 3GU |
| R3‑186807 | [TP for BL CR 38.463] Support of data forwarding at inter-system HO from 5G to 4G | Ericsson, Interdigital | imported from 3GU |
| R3‑186808 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
| R3‑186809 | Support of SDAP mobility when re-mapping at source side is not yet finalised | Ericsson | imported from 3GU |
| R3‑186810 | [TP for BL CR 38.300] Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑186811 | [TP for BL CR 38.413] Support of ongoing re-mapping on source side during HO | Ericsson | imported from 3GU |
| R3‑186812 | [TP for BL CR 38.423] Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑186813 | [TP for BL CR 38.463] Support of ongoing re-mapping on source side during SDAP mobility | Ericsson | imported from 3GU |
| R3‑186814 | [TP for BL CR 38.423] Continuation of work on MR-DC related data forwarding aspects - resource release scenarios | Ericsson | imported from 3GU |
| R3‑186815 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑186816 | [TP BL CR TS 38.413] Establishing a second NG-U tunnel for a PDU Session, NG-RAN node initiated. | Ericsson | imported from 3GU |
| R3‑186817 | [TP BL CR TS 38.423] PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑186818 | [TP BL CR TS 37.340] PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑186819 | Alternative solution: Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
| R3‑186820 | [TP BL CR TS 38.423] PDU Session Split at UPF, alternative 2 | Ericsson | imported from 3GU |
| R3‑186821 | [TP BL CR TS 37.340] Alternative solution: PDU Session Split at UPF | Ericsson | imported from 3GU |
| R3‑186822 | XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑186823 | [TP BL CR 37.340] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑186824 | [TP BL CR 38.423] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑186825 | Transporting F1 over Satellite Radio Interface | Ericsson | imported from 3GU |
| R3‑186826 | Applicability of Xn to Satellites | Ericsson | imported from 3GU |
| R3‑186827 | Correction to Architecture | Ericsson | imported from 3GU |
| R3‑186828 | Are Tracking Areas Stationary or Not? | Ericsson | imported from 3GU |
| R3‑186829 | Network Identities for Non-Terrestrial Networks | Ericsson | imported from 3GU |
| R3‑186830 | Considerations on Mobility in Non-Terrestrial Networks | Ericsson | imported from 3GU |
| R3‑186831 | Multiple duplicate handling | Ericsson | imported from 3GU |
| R3‑186832 | Further discussion on Higher Layer Multi-Connectivity related to the Key Issue 1 | Ericsson | imported from 3GU |
| R3‑186833 | Study on V2X | Ericsson | imported from 3GU |
| R3‑186834 | TNL address discovery with the flexible gNB/en-gNB ID length | Ericsson | imported from 3GU |
| R3‑186835 | Introducing support of deduction of en-gNB node ID length at X2 TNL address discovery | Ericsson | imported from 3GU |
| R3‑186836 | [TP for BL CR 38.300] Introducing support of deduction of NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186837 | [TP for 38.413 BL CR] Introducing support of deduction of NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186838 | [DRAFT] LS on 5GS HO and X2/Xn TNL address discovery with unknown target RAN node ID length | Ericsson | imported from 3GU |
| R3‑186839 | Support of HO with unknown target NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186840 | Support of inter-system HO to 5GS with unknown target NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186841 | Support of inter-system HO to 5GS with unknown target NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186842 | [TP for BL CR 38.300] NG based HO with unknown NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186843 | [TP for BL CR 38.413] Support of NG HO with unknown target NG-RAN node ID length | Ericsson | imported from 3GU |
| R3‑186844 | System info delivery for UE with multiple BWP | Ericsson | imported from 3GU |
| R3‑186845 | Support of system information update for active UE without CSS | Ericsson | imported from 3GU |
| R3‑186846 | Support of keeping the DL UP termination point on the RAN-CN interface – HO and DC aspects | Ericsson, Vodafone | imported from 3GU |
| R3‑186847 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.300 | Ericsson | imported from 3GU |
| R3‑186848 | [TP for BL CR 38.300] Support of keeping the DL UP termination point on the RAN-CN interface at handover | Ericsson | imported from 3GU |
| R3‑186849 | [TP BL CR TS 38.413] Support of keeping the DL UP termination point on the RAN-CN interface at handover | Ericsson | imported from 3GU |
| R3‑186850 | [TP for BL CR 38.423] Support of keeping the DL UP termination point on the RAN-CN interface at handover | Ericsson | imported from 3GU |
| R3‑186851 | [TP for BL CR 38.463] Support of keeping the DL UP termination point on the RAN-CN interface at handover | Ericsson | imported from 3GU |
| R3‑186852 | [TP BL CR 37.340] Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑186853 | [TP for BL CR 38.423] Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
| R3‑186854 | Multiple SCTPs in NG-RAN | Ericsson | imported from 3GU |
| R3‑186855 | [TP BL CR TS 38.463] Multiple TNLA over E1 initialization | Ericsson | imported from 3GU |
| R3‑186856 | [TP BL CR TS 38.463] Dissociating a TNLA from the E1 interface instance by means of the CU-UP Configuration Update procedures | Ericsson | imported from 3GU |
| R3‑186857 | Dissociating a TNLA from the F1 interface instance by means of the gNB DU Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑186858 | [TP for BL CR 38.423] RNAU w/o context relocation - in response to LS in R3-186288/R2-1816057 | Ericsson | imported from 3GU |
| R3‑186859 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑186860 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑186861 | [TP for BL CR 38.300] RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑186862 | [TP for BL CR 38.401] RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑186863 | RAN sharing with multiple Cell ID broadcast | Ericsson, Interdigital | imported from 3GU |
| R3‑186864 | Discussion on UE associated signalling for initial UL RRC message transfer | Ericsson | imported from 3GU |
| R3‑186865 | Introduction of default paging DRX | Ericsson | imported from 3GU |
| R3‑186866 | Default paging DRX | Ericsson | imported from 3GU |
| R3‑186867 | Access Control Information over F1 | Ericsson | imported from 3GU |
| R3‑186868 | Support of NG-RAN initiated Addition of TNLAs on NG-C | Ericsson | imported from 3GU |
| R3‑186869 | [TP for BL CR for 38.413] Introducing NG-RAN initiated addition of TNL Associations | Ericsson | imported from 3GU |
| R3‑186870 | [TP for BL CR 38.413] Associating an additional TNLA with the NG-C interface instance by means of the RAN Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑186871 | [TP for BL CR 38.413] Dissociating a TNLA from the NG-C interface instance by means of the AMF/RAN Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑186872 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
| R3‑186873 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
| R3‑186874 | [TP for BL CR 38.300] Notification Control at NG-RAN resource establishment or modification | Ericsson | imported from 3GU |
| R3‑186875 | Indication that cells are only UL or DL on F1 | Ericsson | imported from 3GU |
| R3‑186876 | Clarification of SRB ID in UE CONTEXT RELEASE COMMAND | Ericsson | imported from 3GU |
| R3‑186877 | AMF intitiated UE Context Release failure cause | Ericsson | imported from 3GU |
| R3‑186878 | About bandcombinationindex and featureSetEntryIndex | Ericsson | imported from 3GU |
| R3‑186879 | About bandcombinationindex and featureSetEntryIndex | Ericsson | imported from 3GU |
| R3‑186880 | [TP for BL CR 38.463] Activity Notification Level in Bearer Modification messages | Ericsson | imported from 3GU |
| R3‑186881 | [TP for BL CR 38.463] Updates in PDCP Config IE | Ericsson | imported from 3GU |
| R3‑186882 | [TP for BL CR 38.463] PDU Session Type and S-NSSAI in Bearer Context Modification | Ericsson | imported from 3GU |
| R3‑186883 | [TP BL CR TS 38.463] gNB-CU-UP Connection Status | Ericsson | imported from 3GU |
| R3‑186884 | [TP for BL CR 38.463] RAN Paging failure on E1 | Ericsson | imported from 3GU |
| R3‑186885 | [TP BL CR TS 38.463] Clarification on new UL TEID request | Ericsson | imported from 3GU |
| R3‑186886 | [TP for BL CR 38.463] Correction to the Cell Group ID | Ericsson | imported from 3GU |
| R3‑186887 | [TP for BL CR 38.463] Corrections for Data forwarding - NG-RAN and EN-DC/E-UTRAN | Ericsson | imported from 3GU |
| R3‑186888 | [TP BL CR TS 38.413] NGAP Correction related to Intra system Handover | Ericsson | imported from 3GU |
| R3‑186889 | [TP BL CR TS 38.413] Correction on PDU Session Resource Modify | Ericsson | imported from 3GU |
| R3‑186890 | [TP BL CR TS 38.413] Modify the two NG-U tunnels per PDU session at the same time | Ericsson | imported from 3GU |
| R3‑186891 | [TP BL CR TS 38.413] Clarify that the PDU session split in UPF is determined by NG-RAN node | Ericsson | imported from 3GU |
| R3‑186892 | [TP BL CR TS 38.413] Remove the second tunnel in the PDU session split, 5GC initiated | Ericsson | imported from 3GU |
| R3‑186893 | [TP BL CR TS 38.413] Align the QFI definition with SA2 | Ericsson | imported from 3GU |
| R3‑186894 | [TP for BL CR 38.413] Abnormal Conditions for PDU Session Resource establishment | Ericsson | imported from 3GU |
| R3‑186895 | [TP for BL CR 38.413] AMF Load Re-balancing correction | Ericsson | imported from 3GU |
| R3‑186896 | [TP for BL CR 38.401] Uniqueness of an AMF UE NGAP ID within an AMF set | Ericsson | imported from 3GU |
| R3‑186897 | [TP for BL CR 38.413] Correcting the range of the AMF UE NGAP ID | Ericsson | imported from 3GU |
| R3‑186898 | [TP for BL CR 38.423] Correcting the range of the AMF UE NGAP ID | Ericsson | imported from 3GU |
| R3‑186899 | [TP for BL CR 38.423] MR-DC data forwarding correction to agreements in R3-186229 and R3-186239 | Ericsson | imported from 3GU |
| R3‑186900 | [TP BL CR TS 38.423] Rapporteur’s work on Alignment of criticality and presence in tabular and ASN.1 | Ericsson | imported from 3GU |
| R3‑186901 | [TP for BL CR 38.423] Rapporteur’s work: Various non-editorial corrections | Ericsson | imported from 3GU |
| R3‑186902 | [TP for BL CR 38.423] Cleanup of Editor’s Notes | Ericsson | imported from 3GU |
| R3‑186903 | [TP for BL CR 38.423] Open Issue on the Cell Group ID | Ericsson | imported from 3GU |
| R3‑186904 | [TP for BL CR 38.423] Resolving open issues in Cause Value descriptions | Ericsson | imported from 3GU |
| R3‑186905 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
| R3‑186906 | [TP BL CR 38.423] Clarification on NRARFCN semantics – TP for XnAP | Ericsson | imported from 3GU |
| R3‑186907 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
| R3‑186908 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑186909 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑186910 | [TP for 38.413 BL CR] Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
| R3‑186911 | Extending GUMMEI Type | Ericsson | imported from 3GU |
| R3‑186912 | Extending GUMMEI Type | Ericsson | imported from 3GU |
| R3‑186913 | [TP for BL CR 38.401] Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
| R3‑186914 | [TP for BL CR 38.413] Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
| R3‑186915 | [TP for BL CR 38.423] Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
| R3‑186916 | [TP for BL CR 38.463] Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
| R3‑186917 | Handling the case when asymmetric QoS flow to DRB mapping is not supported | Ericsson | imported from 3GU |
| R3‑186918 | On the presence of the Request Reference ID in NGAP and XnAP | Ericsson | imported from 3GU |
| R3‑186919 | [DRAFT] LS on inclusion of Request Reference ID for AoI Reporting | Ericsson | imported from 3GU |
| R3‑186920 | Correction of EN-DC related Causes | Ericsson | imported from 3GU |
| R3‑186921 | [TP for BL CR 37.340] Correction of EN-DC related Causes | Ericsson | imported from 3GU |
| R3‑186922 | [TP for BL CR 37.340] DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
| R3‑186923 | [TP for BL CR 38.423] DRB ID co-ordination between MN and SN at DRB ID offloading | Ericsson | imported from 3GU |
| R3‑186924 | [TP for BL CR 38.463] Rapporteur editorial changes | Ericsson | imported from 3GU |
| R3‑186925 | [TP for BL CR 38.463] Rapporteur proposed changes | Ericsson | imported from 3GU |
| R3‑186926 | Discussion on LSs from SA 2 (S2-189051 / R3-185455) and RAN 2 (R2-1816043 / R3-186284) on Time Sensitive Networks | VODAFONE Group Plc | imported from 3GU |
| R3‑186927 | DRAFT Response LS to SA 2 and RAN 2 on Time Sensitive Networks | VODAFONE Group Plc | imported from 3GU |
| R3‑186928 | (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‑186929 | (TP for NR BL CR for TS 38.423): UL in-order delivery support for QoS flow offloading | Intel Corporation | imported from 3GU |
| R3‑186930 | (TP for NR BL CR for TS 38.423): MN’s Release Request for SN-terminated bearer using MCG resources | Intel Corporation | imported from 3GU |
| R3‑186931 | For RAN2 LS R3-186277 on UP EDT when resuming in a new eNB | Intel Corporation | imported from 3GU |
| R3‑186932 | [Draft] Reply LS on UP-EDT procedure when resuming in a new eNB | Intel Corporation | imported from 3GU |
| R3‑186933 | (TP for NR BL CR for TS 38.423): For RAN2 LS R3-186288 on RNAU without context relocation | Intel Corporation | imported from 3GU |
| R3‑186934 | (TP for NR BL CR for TS 38.423): Refinement of stage-3 behaviors for unique DRB ID assignment between MN and SN | Intel Corporation, Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑186935 | For RAN2 LS R3-186286 on drb-Identity assignment in EN-DC | Intel Corporation | imported from 3GU |
| R3‑186936 | For RAN2 LS R3-186286: Allowing SgNB to request new DRB ID from MeNB in EN-DC for an already established SN terminated bearer | Intel Corporation | imported from 3GU |
| R3‑186937 | Correction for correct DDDS for retransmitted packets | Intel Corporation | imported from 3GU |
| R3‑186938 | Correction for correct DDDS for retransmitted packets | Intel Corporation | imported from 3GU |
| R3‑186939 | Remaining RAN impacts for higher layer multi-connectivity in IIoT | LG Electronics | imported from 3GU |
| R3‑186940 | Further consideration on resource efficient PDCP duplication in IIoT | LG Electronics | imported from 3GU |
| R3‑186941 | Further discussion on RNAU without context relocation | LG Electronics | imported from 3GU |
| R3‑186942 | [TP for BL CR 38.463] Introduction of Data Volume Reporting for MR-DC - new class-2 | Ericsson | imported from 3GU |
| R3‑186943 | Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑186944 | Discussion on simplified handling for 25.466 | Ericsson | imported from 3GU |
| R3‑186945 | TR 30.531 v1.31.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | imported from 3GU |
| R3‑186946 | Correction of EN-DC related Causes | Ericsson | imported from 3GU |
| R3‑186947 | (TP for NR BL CR for TS 38.423): Maximum bit rate for integrity protection | Huawei | imported from 3GU |
| R3‑186948 | (TP for NR BL CR for TS 38.463): Maximum bit rate for integrity protection | Huawei | imported from 3GU |
| R3‑186949 | (TP for NR BL CR for TS 37.340): Maximum bit rate for integrity protection | Huawei | imported from 3GU |
| R3‑186950 | (TP for NR BL CR for TS 37.340): SN-initiated DRB and QoS flow offloading for MR-DC | Huawei | imported from 3GU |
| R3‑186951 | (TP for NR BL CR for TS 38.413): Including PDU Session ID in UE Context Release Request | Huawei | imported from 3GU |
| R3‑186952 | (TP for NR BL CR for TS 38.413): Per Slice AMF Set | Huawei | imported from 3GU |
| R3‑186953 | (TP for NR BL CR for TS 38.413): Correction on Unique 5G-TMSI | Huawei | imported from 3GU |
| R3‑186954 | (TP for NR BL CR for TS 38.423): Further discussion on data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑186955 | (TP for NR BL CR for TS 38.413): Further discussion on data forwarding and QoS flow remapping | Huawei | imported from 3GU |
| R3‑186956 | (TP for NR BL CR for TS 38.413): RRC establishment cause value | Huawei | imported from 3GU |
| R3‑186957 | (TP for NR BL CR for TS 38.423): Data forwarding for MN initiated SN release | Huawei | imported from 3GU |
| R3‑186958 | (TP for NR BL CR for TS 37.340): Data forwarding for MN initiated SN release | Huawei | imported from 3GU |
| R3‑186959 | RRC cause in RRC reestablishment fallback | Huawei | imported from 3GU |
| R3‑186960 | [Draft] Reply LS on RRC cause in RRC reestablishment fallback | Huawei | imported from 3GU |
| R3‑186961 | RAN impact on 3-byte TAC for LTE to NR Handover | Huawei | imported from 3GU |
| R3‑186962 | [Draft] Reply LS on 3-byte TAC for LTE to NR Handover | Huawei | imported from 3GU |
| R3‑186963 | (TP for NR BL CR for TS 37.340): Data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑186964 | (TP for NR BL CR for TS 38.413): Data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑186965 | (TP for NR BL CR for TS 38.423): Data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑186966 | (TP for NR BL CR for TS 38.463): Data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑186967 | CR on Data Volume Reporting in 5GC for TS 38.410 | Huawei | imported from 3GU |
| R3‑186968 | CR on Data Volume Reporting in 5GC for TS 38.420 | Huawei | imported from 3GU |
| R3‑186969 | [Draft] Reply LS on data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑186970 | (TP for BL CR for TS 38.401) RRC reestablishment fallback procedure | Huawei | imported from 3GU |
| R3‑186971 | Resource efficient PDCP duplication | Huawei | imported from 3GU |
| R3‑186972 | PDCP duplication with more than 2 copies | Huawei | imported from 3GU |
| R3‑186973 | Higher layer multi-connection for IIoT | Huawei | imported from 3GU |
| R3‑186974 | [Draft] Rely LS on the higher layer multi-connection for IIoT | Huawei | imported from 3GU |
| R3‑186975 | Consideration on the accurate reference timing in TSN for IIoT | Huawei | imported from 3GU |
| R3‑186976 | [Draft] Reply LS to SA2 on TSN integration in the 5G System | Huawei | imported from 3GU |
| R3‑186977 | Discussion on synchronization accuracy and latency to RAN2 question | Huawei | imported from 3GU |
| R3‑186978 | [Draft] Reply LS on synchronization accuracy and latency to RAN2 question | Huawei | imported from 3GU |
| R3‑186979 | Discussion on the Qos enhancement for IIoT | Huawei | imported from 3GU |
| R3‑186980 | [Draft] Reply LS on QoS mornitoring | Huawei | imported from 3GU |
| R3‑186981 | (TP for NR BL CR for TS 38.401): Paging failure in case of CP-UP split | Huawei | imported from 3GU |
| R3‑186982 | (TP for NR BL CR for TS 37.340): RAN paging failure handling in case of dual connectivity | Huawei | imported from 3GU |
| R3‑186983 | CR to 38.473 on the condition of gNB-DU provides C-RNTI | Huawei | imported from 3GU |
| R3‑186984 | CR to 38.473 on inactivity monitoring request | Huawei | imported from 3GU |
| R3‑186985 | CR to 38.473 on new cause value when entering RRC inactive | Huawei | imported from 3GU |
| R3‑186986 | Further discussion on based DRB PDCP duplication | Huawei | imported from 3GU |
| R3‑186987 | CR to 38.473 on DRB PDCP duplication | Huawei | imported from 3GU |
| R3‑186988 | CR to 38.473 on duplication activation | Huawei | imported from 3GU |
| R3‑186989 | CR to 38.473 on removal of PDCP duplication for SRB | Huawei | imported from 3GU |
| R3‑186990 | CR to 38.473 on Support of delta configuration for inactive UE in disaggregated architecture | Huawei | imported from 3GU |
| R3‑186991 | Further discussions on gap generation in case of two gNB-Dus | Huawei | imported from 3GU |
| R3‑186992 | CR to 38.473 on the clarifications to measurement gap generation in case of two gNB-Dus | Huawei | imported from 3GU |
| R3‑186993 | (TP for NR BL CR for TS 38.463): on correction to PDCP SN size over E1 | Huawei | imported from 3GU |
| R3‑186994 | (TP for NR BL CR for TS 38.463): on correction to the presence of NG DL UP Transport Layer information over E1 | Huawei | imported from 3GU |
| R3‑186995 | (TP for NR BL CR for TS 38.463) on correction to PDCP duplication over E1 | Huawei | imported from 3GU |
| R3‑186996 | Further discussions on system information update over F1 | Huawei | imported from 3GU |
| R3‑186997 | CR to 38.473 on clarifications to system information update over F1 | Huawei | imported from 3GU |
| R3‑186998 | CR to 38.470 on clarifications to system information update over F1 | Huawei | imported from 3GU |
| R3‑186999 | (TP for BL CR for TS 38.463): on inactivity timer over E1 | Huawei | imported from 3GU |
| R3‑187000 | CR to 38.473 on Paging over F1 | Huawei | imported from 3GU |
| R3‑187001 | CR to 38.470 on for MSG1 based on-demand SI | Huawei | imported from 3GU |
| R3‑187002 | Discussion on wait timer in case of gNB-DU congestion | Huawei | imported from 3GU |
| R3‑187003 | CR to 38.473 on wait timer in case of gNB-DU congestion | Huawei | imported from 3GU |
| R3‑187004 | (TP for NR BL CR for TS 38.463) on PLMN over E1-C non-UE associated signaling | Huawei | imported from 3GU |
| R3‑187005 | (TP for NR BL CR for TS 38.300) Corrections of QoS parameters | Huawei | imported from 3GU |
| R3‑187006 | (TP for NR BL CR for TS 37.340): MN-initiated DRB and QoS flow release for MR-DC | Huawei | imported from 3GU |
| R3‑187007 | Route Adaptation upon Backhaul Failure | Intel Corporation | imported from 3GU |
| R3‑187008 | Response to R3-186509 | Huawei | imported from 3GU |
| R3‑187009 | Response to R3-186872 | Huawei | imported from 3GU |
| R3‑187010 | Response to R3-186499 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187011 | Response to R3-186432 | Ericsson Inc. | imported from 3GU |
| R3‑187012 | Response to R3-186766 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187013 | Response to R3-186849 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187014 | Response to R3-186518 and R3-186675 | Ericsson | imported from 3GU |
| R3‑187015 | Response to R3-186527 | Ericsson | imported from 3GU |
| R3‑187016 | Response to R3-186562 | Ericsson | imported from 3GU |
| R3‑187017 | Response to R3-186615 | Ericsson, Vodafone, Interdigital | imported from 3GU |
| R3‑187018 | Response to R3-186973 | Ericsson | imported from 3GU |
| R3‑187019 | Response to R3-186908 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187020 | Response to R3-186846 and R3-186397 | Huawei | imported from 3GU |
| R3‑187021 | Response to R3-186849 and R3-186400 | Huawei | imported from 3GU |
| R3‑187022 | Response to R3-186851 and R3-186399 | Huawei | imported from 3GU |
| R3‑187023 | Response to R3-186853 and R3-186398 | Huawei | imported from 3GU |
| R3‑187024 | Response to R3-186450, R3-186513, R3-186590, R3-186711, R3-186722, R3-186937, R3-186572 (Comparison the differences of companies proposals) | NEC | imported from 3GU |
| R3‑187025 | Response to R3-186606 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187026 | Response to R3-186606 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187027 | TR 30.531 v1.32.0 Work Plan and Working Procedures - RAN WG3 | ETSI MCC | imported from 3GU |
| R3‑187028 | (TP for BL CR for TS 38.413): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei, LG Electronics, Orange, China Telecom, China Unicom | imported from 3GU |
| R3‑187029 | (TP for BL CR for TS 38.463): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei, LG Electronics, Orange, China Telecom, China Unicom | imported from 3GU |
| R3‑187030 | (TP for BL CR for TS 38.413): Data Volume Report for MR-DC | Nokia, Nokia Shanghai Bell , Qualcomm | imported from 3GU |
| R3‑187031 | IAB QoS implementation options and roadmap | telstra | imported from 3GU |
| R3‑187032 | (TP for TS 38.413 BL CR): Encoding of RRC Establishment Cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187033 | [Draft] Reply LS on RRC cause in RRC reestablishment fallback | Huawei | imported from 3GU |
| R3‑187034 | Reply LS on UP-EDT procedure when resuming in a new eNB | Intel Corporation | imported from 3GU |
| R3‑187035 | For RAN2 LS R3-186286: Allowing SgNB to request new DRB ID from MeNB in EN-DC for an already established SN terminated bearer | Intel Corporation | imported from 3GU |
| R3‑187036 | [Draft] Reply LS on drb-Identity assignment in EN-DC | NTT DOCOMO, INC. | imported from 3GU |
| R3‑187037 | Dissociating a TNLA from the F1 interface instance by means of the gNB DU Configuration Update procedure | Ericsson | imported from 3GU |
| R3‑187038 | (TP for NR BL CR for TS 37.340): Data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑187039 | (TP for BL CR for TS 38.413): Data Volume Report for MR-DC | Nokia, Nokia Shanghai Bell , Qualcomm | imported from 3GU |
| R3‑187040 | (TP for NR BL CR for TS 38.423) Support for Data Volume Reporting in MR-DC with 5GC | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187041 | (TP for BL CR for TS 37.340)further consideration on Start end time stamp for data volume reporting | NTT DOCOMO, INC, Orange, China Mobile, KT Corp., Verizon | imported from 3GU |
| R3‑187042 | Introduction of Data Volume Reporting for MR-DC - 38.410 | Ericsson | imported from 3GU |
| R3‑187043 | Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑187044 | [TP for BL CR 38.463] Introduction of Data Volume Reporting for MR-DC - new class-2 | Ericsson | imported from 3GU |
| R3‑187045 | Introduction of Data Volume Reporting for MR-DC | Ericsson | imported from 3GU |
| R3‑187046 | [Draft] Reply LS on data volume reporting in 5GC | Huawei | imported from 3GU |
| R3‑187047 | Data forwarding on Inter-system HO | NTT DOCOMO, INC. | imported from 3GU |
| R3‑187048 | [Draft] Reply on LS on supporting low latency and low jitter during handover procedure (KI#2) in FS_URLLC | OPPO | imported from 3GU |
| R3‑187049 | [DRAFT] Response LS on Avoiding MME impacts from 3-byte TAC | Ericsson | imported from 3GU |
| R3‑187050 | [Draft] Reply LS on UE identity to calculate PF and PO in NR | Ericsson | imported from 3GU |
| R3‑187051 | Reply LS on QoS mornitoring | Huawei | imported from 3GU |
| R3‑187052 | Summary of the discussion on Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑187053 | Further discussion on PLMN mismatch in inactive state | Qualcomm | imported from 3GU |
| R3‑187054 | Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑187055 | (TP for BL CR for TS 38.423): Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187056 | Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187057 | (TP for NR BL CR for TS 38.423): Correction of dedicated PDU Session transport resources | Huawei, Nokia, Nokia Shanghai Bell,China Telecom, China Unicom, Orange, LG Electronics | imported from 3GU |
| R3‑187058 | [DRAFT] Response LS on RLC mode reconfiguration | Nokia, Huawei | imported from 3GU |
| R3‑187059 | (TP for NR BL CR for TS 38.413) Overload Control for UAC | ZTE Corporation, CMCC, NTT Docomo, Orange, China Unicom | imported from 3GU |
| R3‑187060 | Summary of offline discussion on interaction between suspend procedure and AS RAI | Qualcomm | imported from 3GU |
| R3‑187061 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑187062 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑187063 | Pending Data Indication | Ericsson | imported from 3GU |
| R3‑187064 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
| R3‑187065 | [TP for BL CR 38.423] MR-DC data forwarding correction to agreements in R3-186229 and R3-186239 | Ericsson | imported from 3GU |
| R3‑187066 | Rapporteur CR to align tabular | Huawei | imported from 3GU |
| R3‑187067 | Rapporteur CR to align ASN.1 | Huawei | imported from 3GU |
| R3‑187068 | Rapporteur’s CR for TS 38.462 | Huawei | imported from 3GU |
| R3‑187069 | UP retransmission status reporting in the NR UP protocol | Ericsson | imported from 3GU |
| R3‑187070 | CR to TS 38.425 UP retransmission status reporting in the NR UP protocol | Ericsson | imported from 3GU |
| R3‑187071 | Summary of offline discussion on inter-system ANR | Qualcomm Incorporated | imported from 3GU |
| R3‑187072 | [DRAFT] LS on adding SSB type in the MTC inter-node message | Huawei | imported from 3GU |
| R3‑187073 | Summary of offline discussion on CB: # 12_LS_SSB | Huawei | imported from 3GU |
| R3‑187074 | CR to TS 36.423 Assistance information for MeNB-SgNB UE-level resource coordination | Ericsson | imported from 3GU |
| R3‑187075 | Further corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187076 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187077 | (TP for NR BL CR for TS 38.463) Periodic Load Reporting for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187078 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell, Ericsson | imported from 3GU |
| R3‑187079 | Support of CA based PDCP duplication on X2 | CATT, Ericsson | imported from 3GU |
| R3‑187080 | Introduction of UL/DL Forwarding GTP TEID | Huawei, Ericsson | imported from 3GU |
| R3‑187081 | Summary of offline discussion on UE-interested slice | Qualcomm Incorporated | imported from 3GU |
| R3‑187082 | Reply LS on RRC cause in RRC reestablishment fallback | Huawei | imported from 3GU |
| R3‑187083 | Support of system information update for active UE | CATT | imported from 3GU |
| R3‑187084 | Response to R3-186450, R3-186513, R3-186590, R3-186711, R3-186722, R3-186937, R3-186572 (Comparison the differences of companies proposals) | NEC | imported from 3GU |
| R3‑187085 | (TP for BL CR for TS 38.300): Handling End Markers in 4g to 5g handovers | Nokia, Nokia Shanghai Bell, Samsung, KT Corp., Huawei, ZTE, CMCC, Verizon Wireless, LG Electronics Inc., CATT, ETRI, KDDI, Google Inc | imported from 3GU |
| R3‑187086 | (TP for BL CR for TS 38.413): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei, LG Electronics, Orange, China Telecom, China Unicom, Deutsche Telekom | imported from 3GU |
| R3‑187087 | (TP for BL CR for TS 38.463): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell, Huawei, LG Electronics, Orange, China Telecom, China Unicom, Deutsche Telekom | imported from 3GU |
| R3‑187088 | Way Forward for Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc., AT&T | imported from 3GU |
| R3‑187089 | (TP for BL CR for TS 38.300): Handling of end markers in 5g to 4g handovers | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc., AT&T | imported from 3GU |
| R3‑187090 | [TP for BL CR 38.423] Rapporteur’s work: Various non-editorial corrections | Ericsson | imported from 3GU |
| R3‑187091 | TR 38.874 v062 | Qualcomm Incorporated | imported from 3GU |
| R3‑187092 | CB: # 16_UP_retransmission: Summary result of offline discussion | NEC | imported from 3GU |
| R3‑187093 | Summary of offline discussions on CB#17 | Ericsson | imported from 3GU |
| R3‑187094 | Summary of offline discussion on Reusing Source TEID at DC | Ericsson | imported from 3GU |
| R3‑187095 | SoD for Data forwarding on inter-system HO | NTT Docomo | imported from 3GU |
| R3‑187096 | EN-DC Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑187097 | (TP for BL CR for TS 38.401): 5G Antenna Interface Function support | Huawei | imported from 3GU |
| R3‑187098 | Antenna Interface Function support | Huawei, Ericsson | imported from 3GU |
| R3‑187099 | [Draft] LS on UTRAN, E-UTRAN and 5G Antenna Interface Function specifications | Huawei | imported from 3GU |
| R3‑187100 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187101 | Summary of offline discussion on multiple SCTP associations | Intel | imported from 3GU |
| R3‑187102 | Summary of the offline discussion CB: # 21_RANsharing_common_interface | KDDI Corporation | imported from 3GU |
| R3‑187103 | [Draft] Draft LS on on PLMN mismatch in active | nn | imported from 3GU |
| R3‑187104 | LS on UTRAN, E-UTRAN and 5G Antenna Interface Function specifications | Huawei | imported from 3GU |
| R3‑187105 | Replace Band table with reference to RAN4 specifications | Ericsson | imported from 3GU |
| R3‑187106 | Summary of offline discussion on UE maximum Data Rate for Integrity Protection | Qualcomm | imported from 3GU |
| R3‑187107 | Summary of the offline discussion on Default Paging DRX | CATT | imported from 3GU |
| R3‑187108 | Summary of offline discussion on CB: # 26_UAC-F1AP | Ericsson | imported from 3GU |
| R3‑187109 | (TP for NR BL CR for TS 38.463): Maximum bit rate for integrity protection | Huawei, Qualcomm Inc. | imported from 3GU |
| R3‑187110 | (TP for NR BL CR for TS 38.423): Maximum bit rate for integrity protection | Qualcomm Inc. | imported from 3GU |
| R3‑187111 | Summary of offline discussion for TNL Address Discovery on Option 3 | NTT Docomo | imported from 3GU |
| R3‑187112 | NTN architecture with regenerative satellite | THALES | imported from 3GU |
| R3‑187113 | NTN architecture with transparent satellite | THALES | imported from 3GU |
| R3‑187114 | NTN multi connectivity | THALES | imported from 3GU |
| R3‑187115 | (TP for NR BL CR for TS 38.423): Correction to RNAU without context relocation | Huawei, Qualcomm Incorporated, Ericsson | imported from 3GU |
| R3‑187116 | (TP for BL CR for TS38.423)Update on Retrieve UE Context message | ZTE Corporation | imported from 3GU |
| R3‑187117 | Update on Retrieve UE Context Request message for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑187118 | (TP for BL CR for TS 38.300): Correction of stage 2 periodic RNA procedure | Huawei | imported from 3GU |
| R3‑187119 | (TP for NR BL CR for TS 38.401): on RRC state transition | Huawei | imported from 3GU |
| R3‑187120 | Summarry of offline discuttion on QoS monitoring | Huawei | imported from 3GU |
| R3‑187121 | (TP for NR BL CR for TS 38.413) Corrections on security handling | Qualcomm Incorporated | imported from 3GU |
| R3‑187122 | (TP for NR BL CR for TS 38.423) Corrections on security handling | Qualcomm Incorporated | imported from 3GU |
| R3‑187123 | (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‑187124 | (TP for NR BL CR for TS 38.423) Correction of PDU Session Aggregate Maximum Bit Rate | ZTE | imported from 3GU |
| R3‑187125 | (TP for BL CR for TS 38.413): Correction of Allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187126 | Summary of offline discussions on Cell Management over F1 | CMCC | imported from 3GU |
| R3‑187127 | CR to TS 38.373 on corrections to cell management over F1 | CMCC | imported from 3GU |
| R3‑187128 | (TP for BL CR for TS 38.401) Further consideration on cell State handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑187129 | CR on cell state handling | NTT DOCOMO, INC. | imported from 3GU |
| R3‑187130 | TP of Descriptions for gNB-DU Processed Payload of Regenerative Satellite | ZTE | imported from 3GU |
| R3‑187131 | Correction ofmaxnoofBPLMNs | Huawei | imported from 3GU |
| R3‑187132 | (TP for NR BL CR for 38.463) Correction of maxnoofSPLMNs | Huawei | imported from 3GU |
| R3‑187133 | Correction on PDCP SN length on F1 | CATT | imported from 3GU |
| R3‑187134 | CR to 38.473 on clarification to the presence of UE AMBR | Huawei | imported from 3GU |
| R3‑187135 | CR to 38.473 on DRB PDCP duplication | Huawei | imported from 3GU |
| R3‑187136 | CR to 38.473 on clarifications to system information update over F1 | Huawei | imported from 3GU |
| R3‑187137 | Addition of EN-DC description | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187138 | Criticality Correction for X2AP UE-ID | Qualcomm Incorporated | imported from 3GU |
| R3‑187139 | RLC reestablishment indication for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑187140 | Correction of PDCP SN Length Indication | ZTE | imported from 3GU |
| R3‑187141 | Summary of discussion on UE-level resource coordination | Huawei | imported from 3GU |
| R3‑187142 | CR to 38.460 on PDCP suspend indication over E1 interface | Huawei | imported from 3GU |
| R3‑187143 | (TP for BL CR for TS 38.423) Configure and de-configure PDCP duplication | Huawei | imported from 3GU |
| R3‑187144 | (TP for TS38.423)Support of PDU session split during Xn handover procedure | CATT | imported from 3GU |
| R3‑187145 | (TP for TS38.413)Support of PDU session split during Xn handover procedure | CATT | imported from 3GU |
| R3‑187146 | (TP for BL CR for TS 38.423): Handling of the SN initiated DRB and flow release | Huawei | imported from 3GU |
| R3‑187147 | (TP for BL CR for TS 37.340): Handling of the SN initiated DRB and flow release | Huawei | imported from 3GU |
| R3‑187148 | (TP for NR BL CR for TS 38.413) NGAP Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
| R3‑187149 | About bandcombinationindex and featureSetEntryIndex | Ericsson | imported from 3GU |
| R3‑187150 | CR for TS 38.473 for MR-DC coordination | CATT | imported from 3GU |
| R3‑187151 | (TP for NR BL CR for TS 38.423) Correction of SN Initiated PDU Session Modification Required (Confirm) Info | ZTE | imported from 3GU |
| R3‑187152 | (TP for NR BL CR for TS 38.423): Refinement of stage-3 behaviors for unique DRB ID assignment between MN and SN | Intel Corporation, Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187153 | (TP for BL CR for TS 37.340): Correction of 5GC initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187154 | (TP for BL CR for TS 38.413): Correction of 5GC initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187155 | (TP for NR BL CR for TS 37.340): SN-initiated DRB and QoS flow offloading for MR-DC | Huawei | imported from 3GU |
| R3‑187156 | Summary of offline discussion on PDU session split | NTT Docomo | imported from 3GU |
| R3‑187157 | Way Forward on TNL Address Allocation for SN addition/modification | Qualcomm Incorporated | imported from 3GU |
| R3‑187158 | Summary of offline discussion on LTE-NR UE Level Resource Coordination | Qualcomm Inc. | imported from 3GU |
| R3‑187159 | (TP for NR BL CR for TS 38.463): on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑187160 | CR to 38.460 on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑187161 | (TP for NR BL CR for TS 38.463) UE Identification and Trace correlation over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung | imported from 3GU |
| R3‑187162 | pCR to 37.470 on W1AP functions and procedures | Huawei, China Unicom, TIM | imported from 3GU |
| R3‑187163 | (TP for BL CR for TS 38.413): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187164 | Revision of recommendations by RAN-2 for IAB WI | Qualcomm Incorporated | imported from 3GU |
| R3‑187165 | Summary of offline discussion for Cell state handling | NTT Docomo | imported from 3GU |
| R3‑187166 | Text proposal for FFS resolution (RAN2 agreed) | KDDI Corporation | imported from 3GU |
| R3‑187167 | Summary of the offline discussions on NGAP transfer of NAS PDU(s) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187168 | (TP for BL CR for TS 38.413): Correction of NAS PDU | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187169 | [TP BL CR 37.340] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑187170 | [TP BL CR 38.423] XnU bearer establishment at setup of SN-terminated bearers | Ericsson | imported from 3GU |
| R3‑187171 | (TP for NR BL CR for TS 38.413) Overload Control for UAC | ZTE Corporation, CMCC, NTT Docomo, Orange, China Unicom | imported from 3GU |
| R3‑187172 | Rename the Data Forwarding Address Indication procedure | Ericsson | imported from 3GU |
| R3‑187173 | LS on IAB security | RAN WG2, Ericsson | imported from 3GU |
| R3‑187174 | Reply on LS on IAB security | SA WG3, Ericsson | imported from 3GU |
| R3‑187175 | [TP BL CR TS 38.413] NGAP Correction related to Intra system Handover | Ericsson | imported from 3GU |
| R3‑187176 | [TP BL CR TS 38.413] Modify the two NG-U tunnels per PDU session at the same time | Ericsson | imported from 3GU |
| R3‑187177 | (TP for NR BL CR for TS 38.413): Corrections on RAN/AMF Configuration Update | Huawei | imported from 3GU |
| R3‑187178 | (TP for NR BL CR for TS 38.423): Adding semantics description for I-RNTI | NEC, Huawei | imported from 3GU |
| R3‑187179 | summary of offline discution on qctivation Functionality over Xn and F1 | Qualcomm Inc. | imported from 3GU |
| R3‑187180 | (TP for BL CR for TS38.423) Update on Measurement Gap Configuration for MR-DC | ZTE Corporation | imported from 3GU |
| R3‑187181 | (TP for BL CR for TS 38.423): Add missing abnormal conditions over Xn | Huawei | imported from 3GU |
| R3‑187182 | Revision of recommendations by RAN-2 for IAB WI | Qualcomm Incorporated | imported from 3GU |
| R3‑187183 | pCR for TR38.874: CB63_TR_IABenhancements | Qualcomm | imported from 3GU |
| R3‑187184 | Removal of the FFS on IAB Routing update procedure | KDDI Corporation | imported from 3GU |
| R3‑187185 | TP to TR 38.874: Setup Procedure for the Adaptation Layer of an IAB Network | Ericsson | imported from 3GU |
| R3‑187186 | IAB inter-CU Topology Adaptation for Arch 1a | Qualcomm Incorporated, Nokia, Samsung | imported from 3GU |
| R3‑187187 | (TP for BL CR for TS 38.413): RAN initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187188 | TP to TR 38.874: Using F1 Functionality to Support Redudant Paths | Ericsson, AT&T, KDDI | imported from 3GU |
| R3‑187189 | IAB backhaul RLF recovery for arch 1a | Qualcomm Incorporated, Ericsson, AT&T, Nokia, Huawei, Samsung | imported from 3GU |
| R3‑187190 | Route selection method for architecture 1a | Huawei | imported from 3GU |
| R3‑187191 | LS to RAN2/3 on UP Integrity Protection for Small Data in Early Data Transfer | 3GPP SA3, Huawei | imported from 3GU |
| R3‑187192 | Retransmission status in UP | NEC | imported from 3GU |
| R3‑187193 | NTN architecture with regenerative satellite | THALES | imported from 3GU |
| R3‑187194 | Reply LS to RAN2/3 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
| R3‑187195 | NTN multi connectivity | THALES | imported from 3GU |
| R3‑187196 | Transporting F1 over Satellite Radio Interface | Ericsson | imported from 3GU |
| R3‑187197 | Applicability of Xn to Satellites | Ericsson | imported from 3GU |
| R3‑187198 | Summary of Multi-Hop Scenarios in NTN | ZTE | imported from 3GU |
| R3‑187199 | NR Remote Interference Management session report | Vice-chairman (ZTE) | imported from 3GU |
| R3‑187200 | NR V2X session report | Vice-chairman (Intel) | imported from 3GU |
| R3‑187201 | NR Industrial IoT Session Report | Vice-chairman (ZTE) | imported from 3GU |
| R3‑187202 | Summary of offline discussion of CB #1 SET ID | ZTE | imported from 3GU |
| R3‑187203 | Handling of UL packets in PDU session split | Nokia | imported from 3GU |
| R3‑187204 | Inter-cluster Signaling Solution options | ZTE | imported from 3GU |
| R3‑187205 | TP for TR 38.866: The open issues in RIM | Ericsson | imported from 3GU |
| R3‑187206 | Summary of offline discussion on Inter-cluster signaling | Ericsson | imported from 3GU |
| R3‑187207 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
| R3‑187208 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
| R3‑187209 | Clarification on NRARFCN semantics | Ericsson | imported from 3GU |
| R3‑187210 | Rapporteur CR to align tabular | Huawei | imported from 3GU |
| R3‑187211 | Reply LS to RAN2/3 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
| R3‑187212 | TP for gNB Grouping and Set ID Design | ZTE | imported from 3GU |
| R3‑187213 | CR on Scell release for RLC failure | Samsung | imported from 3GU |
| R3‑187214 | (TP for BL CR for TS 38.300): Correction of Emergency fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187215 | (TP for BL CR for TS 38.413): PDU session split during handover | Huawei | imported from 3GU |
| R3‑187216 | (TP for BL CR for TS 38.413): Add missing abnormal conditions over NG | Huawei | imported from 3GU |
| R3‑187217 | Summary of discussion on UE-level resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187218 | [DRAFT] Reply LS on TSN requirements evaluation | Nokia | imported from 3GU |
| R3‑187219 | LS on Network Instance | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑187220 | (TP for BL CR for TS 38.423): Handling of RLC failure | Huawei | imported from 3GU |
| R3‑187221 | (TP for the BL CR for 37.340): Clarification on bearer type change in stage-2 | Huawei | imported from 3GU |
| R3‑187222 | Proposed skeleton for RAN3 part of TR 38.885 | Huawei | imported from 3GU |
| R3‑187223 | Summary of Offline Discussion: WF for “Study on NR V2X” in RAN3 | LG Electronics | imported from 3GU |
| R3‑187224 | (TP for BL CR for TS 38.300): Handling of end markers in 5g to 4g handovers | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc., AT&T, China Unicom | imported from 3GU |
| R3‑187225 | [Draft] Reply on LS on supporting low latency and low jitter during handover procedure (KI#2) in FS_URLLC | OPPO | imported from 3GU |
| R3‑187226 | [Draft] Reply LS on UE identity to calculate PF and PO in NR | Ericsson | imported from 3GU |
| R3‑187227 | (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‑187228 | Further corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187229 | Support of system information update for active UE | CATT | imported from 3GU |
| R3‑187230 | Reply LS to RAN2/3 on UP Integrity Protection for Small Data in Early Data Transfer | Huawei | imported from 3GU |
| R3‑187231 | Rapporteur CR to align ASN.1 - non Backward compatible changes | Huawei | imported from 3GU |
| R3‑187232 | Rapporteur CR to align ASN.1 - Backward compatible changes | Huawei | imported from 3GU |
| R3‑187233 | For RAN2 LS R3-186286: Allowing SgNB to request new DRB ID from MeNB in EN-DC for an already established SN terminated bearer | Intel Corporation | imported from 3GU |
| R3‑187234 | [DRAFT] LS on the Unified Access Control over NG interface | ZTE | imported from 3GU |
| R3‑187235 | Draft LS on on PLMN mismatch in active | nn | imported from 3GU |
| R3‑187236 | Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑187237 | (TP for BL CR for TS 38.300): Handling End Markers in 4g to 5g handovers | Nokia, Nokia Shanghai Bell, Samsung, KT Corp., Huawei, ZTE, CMCC, Verizon Wireless, LG Electronics Inc., CATT, ETRI, KDDI, Google Inc | imported from 3GU |
| R3‑187238 | (TP for BL CR for TS 37.340): Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
| R3‑187239 | (TP for BL CR for TS 38.423): Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187240 | TP of inter-cluster signalling for TR 38.866 | CMCC | imported from 3GU |
| R3‑187241 | Status summary of NR RIM SI | CMCC | imported from 3GU |
| R3‑187242 | (TP for NR BL CR for TS 38.463): Maximum bit rate for integrity protection | Huawei, Qualcomm Inc. | imported from 3GU |
| R3‑187243 | (TP for NR BL CR for TS 38.423) Corrections on security handling | Qualcomm Incorporated | imported from 3GU |
| R3‑187244 | LS on Security Result Exchange Between NG-RAN and SMF in DC | ZTE | imported from 3GU |
| R3‑187245 | [DRAFT] LS on adding SSB type in the MTC inter-node message | Huawei | imported from 3GU |
| R3‑187246 | Summary of discussion on UE-level resource coordination | Huawei | imported from 3GU |
| R3‑187247 | RLC reestablishment indication for TS36.423 | ZTE Corporation | imported from 3GU |
| R3‑187248 | Handling of RLC failure | Huawei | imported from 3GU |
| R3‑187249 | Correction ofmaxnoofBPLMNs | Huawei | imported from 3GU |
| R3‑187250 | (TP for NR BL CR for TS 38.463): on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑187251 | CR to 38.460 on notification for default DRB over E1 | Huawei | imported from 3GU |
| R3‑187252 | Reply LS on TSN requirements evaluation | Nokia | imported from 3GU |
| R3‑187253 | Draft LS on Enforcement of maximum supported data rate for integrity protection | Qualcomm Incorporated | imported from 3GU |
| R3‑187254 | [TP BL CR TS 38.413] Modify the two NG-U tunnels per PDU session at the same time | Ericsson | imported from 3GU |
| R3‑187255 | (TP for NR BL CR for TS 38.413) NGAP Signaling Extensibility for Multi-Connectivity | ZTE | imported from 3GU |
| R3‑187256 | Route selection method for architecture 1a | Huawei, OMESH Technologies Co. Ltd. | imported from 3GU |
| R3‑187257 | IAB backhaul RLF recovery for arch 1a | Qualcomm Incorporated, Ericsson, AT&T, Nokia, Huawei, Samsung | imported from 3GU |
| R3‑187258 | (TP for BL CR for TS 38.300): Correction of Emergency fallback | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187259 | Reply LS on drb-Identity assignment in EN-DC | NTT DOCOMO, INC. | imported from 3GU |
| R3‑187260 | (TP for BL CR for TS 38.413): PDU session split during handover | Huawei | imported from 3GU |
| R3‑187261 | Response LS on Avoiding MME impacts from 3-byte TAC | Ericsson | imported from 3GU |
| R3‑187262 | Addition of the RLC Mode information for bearer modification | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
| R3‑187263 | (TP for BL CR for TS 38.423): Addition of the RLC Mode information for bearer modification | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187264 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187265 | CR for TS 38.473 for MR-DC coordination | CATT | imported from 3GU |
| R3‑187266 | Handling of end markers in 5g to 4g handovers | Samsung, KT Corp., ZTE, CMCC, Verizon, LG Electronics Inc., CATT, ETRI, Nokia, Nokia Shanghai Bell, Huawei, KDDI, Google Inc. | imported from 3GU |
| R3‑187267 | Draft LS on Enforcement of maximum supported data rate for integrity protection | Qualcomm Incorporated | imported from 3GU |
| R3‑187268 | (TP for BL CR for TS 38.413): RAN initiated PDU session split | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187269 | Handling of UL packets in PDU session split | Nokia | imported from 3GU |
| R3‑187270 | pCR to 37.470 on W1AP functions and procedures | Huawei, China Unicom, TIM | imported from 3GU |
| R3‑187271 | LS on the Unified Access Control over NG interface | ZTE | imported from 3GU |
| R3‑187272 | Revision of recommendations by RAN-2 for IAB WI | Qualcomm Incorporated | imported from 3GU |
| R3‑187273 | Applicability of Xn to Satellites | Ericsson | imported from 3GU |
| R3‑187274 | LS on adding SSB type in the MTC inter-node message | Huawei | imported from 3GU |
| R3‑187275 | (TP for BL CR for TS 38.413): Add missing abnormal conditions over NG | Huawei | imported from 3GU |
| R3‑187276 | TP for gNB Grouping and Set ID Design | ZTE | imported from 3GU |
| R3‑187277 | Summary of offline discussion on Intra-cluster co-ordination | Ericsson | imported from 3GU |
| R3‑187278 | NR Corrections (TS 38.401 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) | Rapporteur (NEC) | imported from 3GU |
| R3‑187279 | Baseline CR for TS 38.413 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| R3‑187280 | NR Corrections (TS 38.423 Baseline CR covering RAN3-101Bis and RAN3-102 agreements) | Ericsson | imported from 3GU |
| R3‑187281 | draft TR 38.821 v0.3.0 | Thales | imported from 3GU |
page generated from database: 2024-04-22 07:58:53