3GPP TDocs (written contributions) at meeting
Meeting: R3-105 - 2019-08-26 to 2019-08-30, Ljubljana
meeting id: R3-105 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑193300 | RAN3-105 meeting Agenda | Chairman (Ericsson) | imported from 3GU |
R3‑193301 | RAN3-104Bis meeting report | ETSI MCC | imported from 3GU |
R3‑193302 | LS on piggy-backing of NAS PDUs | 3GPP CT1 | imported from 3GU |
R3‑193303 | Reply LS on piggy-backing of NAS PDUs in NGAP messages | 3GPP CT1 | imported from 3GU |
R3‑193304 | 5G Cell ID(s) in the 3GPP SA5 billing system | ETSI TC LI | imported from 3GU |
R3‑193305 | Femto Access Point Data Model Issue 2 (FAP:2) Updates | Broadband Forum | imported from 3GU |
R3‑193306 | Reply LS on CSI-RS configuration transfer over Xn | 3GPP RAN1 | imported from 3GU |
R3‑193307 | LS on Reference Point for Timing Related Measurements | 3GPP RAN1 | imported from 3GU |
R3‑193308 | LS on PDCCH monitoring for NR-DC | 3GPP RAN1 | imported from 3GU |
R3‑193309 | Reply LS on the user plane latency measurement | 3GPP RAN2 | imported from 3GU |
R3‑193310 | LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC | 3GPP RAN2 | imported from 3GU |
R3‑193311 | Reply LS for Conclusion on 5G CIoT user plane small data solution | 3GPP RAN2 | imported from 3GU |
R3‑193312 | LS on assistance indication for WUS grouping | 3GPP RAN2 | imported from 3GU |
R3‑193313 | LS on UAC for NB-IoT | 3GPP RAN2 | imported from 3GU |
R3‑193314 | LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC | 3GPP RAN2 | imported from 3GU |
R3‑193315 | Response LS on inclusion of selected PLMN into the complete message | 3GPP RAN2 | imported from 3GU |
R3‑193316 | Reply LS on support of default DRB configuration | 3GPP RAN2 | imported from 3GU |
R3‑193317 | Reply LS on PDCCH monitoring for NR-DC | 3GPP RAN2 | imported from 3GU |
R3‑193318 | LS on UE feature list for NR | 3GPP RAN4 | imported from 3GU |
R3‑193319 | Reply LS on PARLOS RAN impacts | 3GPP TSG RAN | imported from 3GU |
R3‑193320 | Further LS relating to “Response LS on reporting all Cell IDs in 5G” | 3GPP SA2 | imported from 3GU |
R3‑193321 | Reply on Combinations of Uu QoS characteristics values for V2X services | 3GPP SA2 | imported from 3GU |
R3‑193322 | Reply LS on piggybacking of NAS PDUs | 3GPP SA2 | imported from 3GU |
R3‑193323 | LS Reply on Transport Level Packet Marking | 3GPP SA2 | imported from 3GU |
R3‑193324 | Reply LS on Support of EPS fallback for voice for eLTE | 3GPP SA2 | imported from 3GU |
R3‑193325 | LS on User Data Congestion Analytics | 3GPP SA2 | imported from 3GU |
R3‑193326 | Reply LS on PARLOS RAN impacts | 3GPP SA2 | imported from 3GU |
R3‑193327 | LS on RAN sharing and Emergency services with Non-Public Networks | 3GPP SA2 | imported from 3GU |
R3‑193328 | LS to BBF on WWC status | 3GPP SA2 | imported from 3GU |
R3‑193329 | LS on LTE-M identification in 5GC | 3GPP SA2 | imported from 3GU |
R3‑193330 | LS on Potential improvements for delay critical QoS Flows | 3GPP SA2 | imported from 3GU |
R3‑193331 | Reply LS on ""LS on the coordination of CN identities used in 5GS and EPS"" | 3GPP SA2 | imported from 3GU |
R3‑193332 | LS on maximum value of MDBV | 3GPP SA2 | imported from 3GU |
R3‑193333 | LS on Broadcast of Location Assistance Data for NR | 3GPP SA2 | imported from 3GU |
R3‑193334 | Reply LS on support for flow based QoS & slicing for NB-IoT & eMTC connected to 5GC | 3GPP SA2 | imported from 3GU |
R3‑193335 | Reply LS on RRC Connection Re-Establishment for CP for NB-IoT connected to 5GC | 3GPP SA2 | imported from 3GU |
R3‑193336 | Reply LS on assistance indication for WUS grouping | 3GPP SA2 | imported from 3GU |
R3‑193337 | LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | 3GPP SA2 | imported from 3GU |
R3‑193338 | Reply LS on Mobile-terminated Early Data Transmission | 3GPP SA2 | imported from 3GU |
R3‑193339 | Reply LS on Solution 1 of 5G_URLLC | 3GPP SA2 | imported from 3GU |
R3‑193340 | LS on Reporting all Cell IDs in 5G | 3GPP SA2 | imported from 3GU |
R3‑193341 | LS reply on Handling of UE radio network capabilities in 4G and 5G | 3GPP SA3 | imported from 3GU |
R3‑193342 | LS on Reporting all Cell IDs in 5G | 3GPP SA3-LI | imported from 3GU |
R3‑193343 | LS on radio resource management policy | 3GPP SA5 | imported from 3GU |
R3‑193344 | LS on inter-operator TDD operation | ITU-T Study Group 15 | imported from 3GU |
R3‑193345 | LS on Reporting all Cell IDs in 5G. | 3GPP TSG SA | imported from 3GU |
R3‑193346 | BL CR to 38.300: Support for network sharing | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Interdigital | imported from 3GU |
R3‑193347 | BL CR to 38.470: Support for IAB | Ericsson | imported from 3GU |
R3‑193348 | BL CR to 38.473: Support for IAB | Ericsson | imported from 3GU |
R3‑193349 | BL CR to 36.413: Support for IAB | Huawei | imported from 3GU |
R3‑193350 | BL CR to 36.423: Support for IAB | Samsung | imported from 3GU |
R3‑193351 | BL CR to 38.401: Support for IAB | Huawei | imported from 3GU |
R3‑193352 | BL CR to 38.413: Support for IAB | Nokia Shanghai Bell | imported from 3GU |
R3‑193353 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑193354 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson | imported from 3GU |
R3‑193355 | Support of Enhanced Coverage restriction in NGAP for LTE-M UEs | Ericsson | imported from 3GU |
R3‑193356 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation | imported from 3GU |
R3‑193357 | Baseline CR for introducing Rel-16 LTE further mobility enhancement | Intel Corporation | imported from 3GU |
R3‑193358 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193359 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation | imported from 3GU |
R3‑193360 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation | imported from 3GU |
R3‑193361 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation | imported from 3GU |
R3‑193362 | Transmission Measurement Function in NG-RAN | Ericsson | imported from 3GU |
R3‑193363 | NR Assistance Data Delivery over NRPPa | Ericsson | imported from 3GU |
R3‑193364 | UE-TNL binding on NG-C SCTP association failure | Altiostar | imported from 3GU |
R3‑193365 | LS on UE-TNLA binding on SCTP failure | Altiostar | imported from 3GU |
R3‑193366 | Addition of PPID for DTLS over SCTP for 38.472 | Interdigital Asia LLC | imported from 3GU |
R3‑193367 | Architecture and procedures for Local LMF in NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193368 | Coordination between Local LMF and 5GC entities | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193369 | Xn impacts of Local LMF in NG-RAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193370 | Necessity on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
R3‑193371 | CR on Clarification on path switch request for inter MN HO without SN change | NTT DOCOMO, INC. | imported from 3GU |
R3‑193372 | (TS38.412) CR on PPID value for DTLS over SCTP | NTT DOCOMO, INC. | imported from 3GU |
R3‑193373 | (TS38.422) CR on PPID value for DTLS over SCTP | NTT DOCOMO, INC. | imported from 3GU |
R3‑193374 | Race condition between X2 and S1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑193375 | CR for addressing Race condition between X2 and S1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑193376 | Addressing issue on timer based solution | NTT DOCOMO, INC. | imported from 3GU |
R3‑193377 | Further consideration on time reference information delivery | NTT DOCOMO, INC. | imported from 3GU |
R3‑193378 | Way forward on LTE HLS for E-UTRAN | NTT DOCOMO, INC, Vodafone, Verizon Wireless, Ericsson | imported from 3GU |
R3‑193379 | Consideration on Conditional Handover | NTT DOCOMO, INC. | imported from 3GU |
R3‑193380 | Data forwarding timing on Conditional Handover | NTT DOCOMO, INC. | imported from 3GU |
R3‑193381 | LPPa enhancement for EN-DC support | NTT DOCOMO, INC.,Vodafone | imported from 3GU |
R3‑193382 | Race condition between X2 and S1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑193383 | CR for addressing Race condition between X2 and S1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑193384 | Inter UE QoS related Corrections | Huawei | imported from 3GU |
R3‑193385 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑193386 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑193387 | Consideration on Data Forwarding Address Indication | Huawei | imported from 3GU |
R3‑193388 | Correction on Data Forwarding Address Indication | Huawei, CATT, Samsung | imported from 3GU |
R3‑193389 | Consideration on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑193390 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑193391 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑193392 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑193393 | Consideration on Ethernet Type Bearer Support | Huawei | imported from 3GU |
R3‑193394 | Support of Ethernet Type Bearer | Huawei | imported from 3GU |
R3‑193395 | Support of Ethernet Type Bearer | Huawei | imported from 3GU |
R3‑193396 | Consideration on NB-IoT TDD cell frequency info exchanging | Huawei | imported from 3GU |
R3‑193397 | Correction of NB-IoT TDD Cell Frequency info | Huawei | imported from 3GU |
R3‑193398 | CP NB-IoT signaling procedure | Huawei | imported from 3GU |
R3‑193399 | Introduction of NB-IoT related NG-AP procedures | Huawei | imported from 3GU |
R3‑193400 | Consideration on CP UP NB-IoT Others | Huawei | imported from 3GU |
R3‑193401 | Introduction of CP UP NB-IoT Others | Huawei | imported from 3GU |
R3‑193402 | Introduction of CP UP NB-IoT Others | Huawei | imported from 3GU |
R3‑193403 | NB-IoT cell frequency information exchange over Xn | Huawei | imported from 3GU |
R3‑193404 | Consideration on Coverage Enhancement | Huawei | imported from 3GU |
R3‑193405 | LTE-M identification in 5GC | Huawei | imported from 3GU |
R3‑193406 | Introduction of LTE-M Indicator | Huawei | imported from 3GU |
R3‑193407 | [Draft] Reply LS on LTE-M identification in 5GC | Huawei | imported from 3GU |
R3‑193408 | QoS and Slicing for NB-IoT and MTC connected to 5GC | Huawei | imported from 3GU |
R3‑193409 | Support of Network Slicing for NB-IoT connected to 5GC | Huawei | imported from 3GU |
R3‑193410 | Support of Network Slicing for NB-IoT and MTC connected to 5GC | Huawei | imported from 3GU |
R3‑193411 | Consideration on ANR for NB-IoT | Huawei | imported from 3GU |
R3‑193412 | Consideration on RACH optimization for NB-IoT | Huawei | imported from 3GU |
R3‑193413 | NPRACH configuration exchange | Huawei | imported from 3GU |
R3‑193414 | NPRACH configuration exchange | Huawei | imported from 3GU |
R3‑193415 | Consideration on RLF for NB-IoT | Huawei | imported from 3GU |
R3‑193416 | Support of RLF in NB-IoT | Huawei | imported from 3GU |
R3‑193417 | Support of RLF in NB-IoT | Huawei | imported from 3GU |
R3‑193418 | Consideration on UE group wake up signal (WUS) | Huawei | imported from 3GU |
R3‑193419 | Support of UE group wake up signal | Huawei | imported from 3GU |
R3‑193420 | Support of UE group wake up signal | Huawei | imported from 3GU |
R3‑193421 | Discussion on Backhaul RLF | CENC | imported from 3GU |
R3‑193422 | Enhancements of QoS with alternative QoS profiles | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193423 | Reply LS on Enhancements to QoS Handling for V2X communication over Uu reference point | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193424 | Support of LTE-M Identification in 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193425 | Reply LS on LTE-M identification in 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193426 | Support of LTE-M Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193427 | Correction of E-RAB Modification Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193428 | Correction of E-RAB Modification Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193429 | Correction of NG connection in MR DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193430 | Correction of NG connection in MR DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193431 | Correction of secured signaling connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193432 | Correction of secured signaling connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193433 | Correction of NG state reporting function | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193434 | Correction of PDU session resource release | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193435 | Correction of security indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193436 | TSC Deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑193437 | Introducing NGAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑193438 | Introducing XnAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑193439 | Introducing F1AP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑193440 | Introducing E1AP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑193441 | S1AP Introduction of New Cause Value for EPS Fallback | ZTE | imported from 3GU |
R3‑193442 | TS37.340 Rapporteur Cleanups | ZTE | imported from 3GU |
R3‑193443 | E1AP Transfer Security Result from CU-CP to CU-UP | ZTE | imported from 3GU |
R3‑193444 | Consolidate Rel-15 Behaviors of RRC_Inactive with MR-DC | ZTE | imported from 3GU |
R3‑193445 | Stage2 Behaviors Clarification for RRC_Inactive with MR-DC | ZTE | imported from 3GU |
R3‑193446 | XnAP Rel-15 Leftover Clean-ups | ZTE | imported from 3GU |
R3‑193447 | XnAP Corrections of Activity Notification Usage | ZTE | imported from 3GU |
R3‑193448 | NGAP Corrections of if supported with ULI Capability | ZTE | imported from 3GU |
R3‑193449 | NGAP Corrections of Location Reporting Request Type | ZTE | imported from 3GU |
R3‑193450 | Further Discussion on CHO Preparation with Multiple Candidate Cells in the Same Target Node | ZTE | imported from 3GU |
R3‑193451 | Further Discussion on Modification of Ongoing CHO | ZTE | imported from 3GU |
R3‑193452 | Further Discussion on Cancel of Ongoing CHO per Target Node | ZTE | imported from 3GU |
R3‑193453 | Further Discussion on Applicability of CHO in MR-DC SN Change Scenario | ZTE | imported from 3GU |
R3‑193454 | Some Other Issues with CHO | ZTE | imported from 3GU |
R3‑193455 | Service Authorization for NR V2X | CATT | imported from 3GU |
R3‑193456 | Support of V2X Service Authorization for NG-AP | CATT | imported from 3GU |
R3‑193457 | Support of V2X Service Authorization for Xn-AP | CATT | imported from 3GU |
R3‑193458 | Support of V2X Service Authorization for S1-AP | CATT | imported from 3GU |
R3‑193459 | Support of V2X Service Authorization for X2-AP | CATT | imported from 3GU |
R3‑193460 | Resource allocation for NR V2X | CATT | imported from 3GU |
R3‑193461 | QoS support for NR V2X | CATT | imported from 3GU |
R3‑193462 | QoS support for NR V2X in NGAP | CATT | imported from 3GU |
R3‑193463 | QoS support for NR V2X in XnAP | CATT | imported from 3GU |
R3‑193464 | QoS support for NR V2X in S1AP | CATT | imported from 3GU |
R3‑193465 | QoS support for NR V2X in X2AP | CATT | imported from 3GU |
R3‑193466 | V2X Resource co-ordination | CATT | imported from 3GU |
R3‑193467 | TSC Assistance Info | CATT | imported from 3GU |
R3‑193468 | Provisioning of TSC Assistance Information in NGAP | CATT | imported from 3GU |
R3‑193469 | Provisioning of TSC Assistance Information in XnAP | CATT | imported from 3GU |
R3‑193470 | Provisioning of TSC Assistance Information in E1AP | CATT | imported from 3GU |
R3‑193471 | Provisioning of TSC Assistance Information in F1AP | CATT | imported from 3GU |
R3‑193472 | Consideration on bearer management for IAB architecture | CATT | imported from 3GU |
R3‑193473 | IAB Backhaul RLF recovery | CATT | imported from 3GU |
R3‑193474 | (TP for NR_IAB BL CR for TS 38.401) Intra CU IAB node migration | CATT | imported from 3GU |
R3‑193475 | (TP for NR_IAB BL CR for TS 38.401) Inter CU IAB node migration | CATT | imported from 3GU |
R3‑193476 | Considersions on RAN3 impact for RACS | CATT,MediaTek Inc. | imported from 3GU |
R3‑193477 | TP for BL CR for TS 38.423 CHO Cancel from Potential Target Node | ZTE | imported from 3GU |
R3‑193478 | TP for BL CR for TS 36.423 CHO Cancel from Potential Target Node | ZTE | imported from 3GU |
R3‑193479 | TP for BL CR for TS 38.423 Handover Success Procedure in MR-DC@5GC | ZTE | imported from 3GU |
R3‑193480 | TP for BL CR for TS 36.423 Handover Success Procedure in EN-DC | ZTE | imported from 3GU |
R3‑193481 | More Usage of Handover Success Procedure | ZTE | imported from 3GU |
R3‑193482 | Further Discussion on CSI-RS Config Info Transfer | ZTE | imported from 3GU |
R3‑193483 | Stage2 Introductions of Some MR-DC New Features (e.g. ARPI) | ZTE | imported from 3GU |
R3‑193484 | Further Discussion on Conveying Location Reporting Control Info | ZTE | imported from 3GU |
R3‑193485 | Some Residual Issues with Secondary RAT DVR | ZTE | imported from 3GU |
R3‑193486 | Stage2 Various Clarifications of Secondary RAT DVR Behaviors | ZTE | imported from 3GU |
R3‑193487 | Stage2 Various Clarifications of Secondary RAT DVR Behaviors | ZTE | imported from 3GU |
R3‑193488 | Support of Service Authorization for V2X | LG Electronics, LG Uplus | imported from 3GU |
R3‑193489 | Support of Service Authorization for V2X over NG | LG Electronics, LG Uplus | imported from 3GU |
R3‑193490 | Support of Service Authorization for V2X over Xn | LG Electronics, LG Uplus | imported from 3GU |
R3‑193491 | Impacts on F1 for support of sidelink resource allocation | LG Electronics, LG Uplus | imported from 3GU |
R3‑193492 | Support of UE Slidelink AMBR for V2X | LG Electronics, LG Uplus | imported from 3GU |
R3‑193493 | Support of UE Sidelink AMBR for V2X over NG | LG Electronics, LG Uplus | imported from 3GU |
R3‑193494 | Support of UE Sidelink AMBR for V2X over Xn | LG Electronics, LG Uplus | imported from 3GU |
R3‑193495 | Further discussion on support of conditional handover | LG Electronics | imported from 3GU |
R3‑193496 | Issues on support of NSA for IAB | LG Electronics | imported from 3GU |
R3‑193497 | Consideration on overload due to CHO | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193498 | (TP for NR_Mob_enh BL CR for TS 38.423): Resource allocation indication for CHO | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193499 | (TP for LTE_feMob BL CR for TS 36.423): Resource allocation indication for CHO | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193500 | Handling of changing conditions during CHO | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193501 | (TP for NR_Mob_enh BL CR for TS 38.423): Enabling efficient RRC reconfiguration and CHO cancel | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193502 | (TP for LTE_feMob BL CR for TS 36.423): Enabling efficient RRC reconfiguration and CHO cancel | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193503 | Avoiding unnecessary data duplication during enhanced HO | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193504 | Further details on the solution to enhance efficiency of PDCP duplication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193505 | Enabling hold-and-go solution and reporting of the transmission attempt failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193506 | Critical correction to the presence of the SgNB UE X2AP ID in the SgNB Release Request Reject | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193507 | Critical correction to the presence of the TAC lists in the Service Area Item IE | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193508 | Correction to the partial reset to handle split CU-DU scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193509 | Correction of the partial reset to enable data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193510 | Correction of the partial reset to enable data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193511 | Discussion on Measurement Gap Configuration over F1 for Multiple-DU Scenario | ZTE | imported from 3GU |
R3‑193512 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 1) | ZTE | imported from 3GU |
R3‑193513 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 2) | ZTE | imported from 3GU |
R3‑193514 | Further Discussion on Solution 1 of URLLC | ZTE | imported from 3GU |
R3‑193515 | CR38.413 for redundant PDU session estalbishment for Solution 1 | ZTE | imported from 3GU |
R3‑193516 | CR38.423 for redundant PDU session in case of one RSN value at SN | ZTE | imported from 3GU |
R3‑193517 | CR38.423 for redundant PDU session in case of two RSN values at one node | ZTE | imported from 3GU |
R3‑193518 | CR38.463 for redundant PDU session in case of two RSN values at one node | ZTE | imported from 3GU |
R3‑193519 | Further consideration on TSC Assistance Information for NR-IIoT | ZTE | imported from 3GU |
R3‑193520 | pCR38473 for Providing TSC Assistance Information in F1AP | ZTE | imported from 3GU |
R3‑193521 | pCR38463 for Providing TSC Assistance Information in XnAP | ZTE | imported from 3GU |
R3‑193522 | pCR38423 for Providing TSC Assistance Information in XnAP | ZTE | imported from 3GU |
R3‑193523 | pCR38413 for Providing TSC Assistance Information in NGAP | ZTE | imported from 3GU |
R3‑193524 | Consideration on accurate reference timing delivery by unicast RRC signaling | ZTE | imported from 3GU |
R3‑193525 | pCR38473 for Providing accurate reference timing Information from gNB-DU to gNB-CU | ZTE | imported from 3GU |
R3‑193526 | Consideration on resource efficiency of solution4 | ZTE | imported from 3GU |
R3‑193527 | Draft LS to SA2 for resource efficiency of solution4 | ZTE | imported from 3GU |
R3‑193528 | CR for TS38.413 on resource efficiency enhanced solution4 | ZTE | imported from 3GU |
R3‑193529 | CR for TS38.423 on resource efficiency enhanced solution4 | ZTE | imported from 3GU |
R3‑193530 | CR for TS38.463 on resource efficiency enhanced solution4 | ZTE | imported from 3GU |
R3‑193531 | CR for TS38.415 on resource efficiency enhanced solution4 | ZTE | imported from 3GU |
R3‑193532 | Consideration on discard timer on PDCP Duplication enhancement for URLLC | ZTE | imported from 3GU |
R3‑193533 | CR for TS38.425 on discard timer | ZTE | imported from 3GU |
R3‑193534 | Correction on the usage of SN Reconfiguration Completion | ZTE | imported from 3GU |
R3‑193535 | CR37340 for correction on the usage of SN Reconfiguration Completion | ZTE | imported from 3GU |
R3‑193536 | Correction on RRC configuration indication | ZTE | imported from 3GU |
R3‑193537 | CR38.423 for Correction on RRC configuration indication | ZTE | imported from 3GU |
R3‑193538 | CR38.423 for correction on PCI confusion | ZTE | imported from 3GU |
R3‑193539 | CR37.340 to correct on avoidance of PCI confusion | ZTE | imported from 3GU |
R3‑193540 | Discussion on SIB9 encoding mechanism in Rel15 | ZTE | imported from 3GU |
R3‑193541 | CR38.470 for re-encoding of SIB9 in the gNB-DU | ZTE | imported from 3GU |
R3‑193542 | Discussion on the default DRB configuration | ZTE | imported from 3GU |
R3‑193543 | Discussion on the remaining issue of default DRB | ZTE | imported from 3GU |
R3‑193544 | CR38.423 for Default DRB | ZTE | imported from 3GU |
R3‑193545 | CR38.300 for remaining issue of default DRB | ZTE | imported from 3GU |
R3‑193546 | [Draft] Reply LS on support of default DRB configuration | ZTE | imported from 3GU |
R3‑193547 | BL CR for support of extended DRX in CM-IDLE for eMTC connected to 5GC | ZTE, Ericsson, Huawei, LG | imported from 3GU |
R3‑193548 | UE context retrieval for UP MT-EDT | ZTE | imported from 3GU |
R3‑193549 | LTE-M Identification in 5GC | Qualcomm Incorporated | imported from 3GU |
R3‑193550 | [Draft] Reply LS on LTE-M identification in 5GC | Qualcomm Incorporated | imported from 3GU |
R3‑193551 | Expanding range of the Maximum Data Burst Value | Qualcomm Incorporated | imported from 3GU |
R3‑193552 | [Draft] Reply LS on LS on maximum value of MDBV | Qualcomm Incorporated | imported from 3GU |
R3‑193553 | Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Qualcomm Incorporated | imported from 3GU |
R3‑193554 | Addition of Activity Notification Control | Qualcomm Incorporated | imported from 3GU |
R3‑193555 | MN Requested full configuration for SN | Qualcomm Incorporated | imported from 3GU |
R3‑193556 | MDT procedure | Qualcomm Incorporated | imported from 3GU |
R3‑193557 | UE mobility history report | Qualcomm Incorporated | imported from 3GU |
R3‑193558 | Value of successful HO report | Qualcomm Incorporated | imported from 3GU |
R3‑193559 | Beam information in rach-report | Qualcomm Incorporated | imported from 3GU |
R3‑193560 | IAB workplan | Qualcomm Incorporated (Rapporteur) | imported from 3GU |
R3‑193561 | IAB indication and parent selection | Qualcomm Incorporated | imported from 3GU |
R3‑193562 | IAB intra-donor UP and CP transport | Qualcomm Incorporated | imported from 3GU |
R3‑193563 | IAB parent-node change | Qualcomm Incorporated | imported from 3GU |
R3‑193564 | IAB parent-node change | Qualcomm Incorporated | imported from 3GU |
R3‑193565 | Discussion on the received LS on MT-EDT | Qualcomm Incorporated | imported from 3GU |
R3‑193566 | Control Plane CIoT 5GS Optimisation in NG-RAN | Quacomm Incorporated | imported from 3GU |
R3‑193567 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated | imported from 3GU |
R3‑193568 | Reuse MR-DC Backhaul Coordination in MBB Handover | Qualcomm Incorporated | imported from 3GU |
R3‑193569 | PDCP SN Continuity for RLC-UM | Qualcomm Incorporated | imported from 3GU |
R3‑193570 | PDCP SN Continuity for NR RLC-UM (Stage 2 CR NR) | Qualcomm Incorporated | imported from 3GU |
R3‑193571 | PDCP SN Continuity for NR RLC-UM (Stage 2 CR LTE) | Qualcomm Incorporated | imported from 3GU |
R3‑193572 | NG based Conditional Handover | Qualcomm Incorporated | imported from 3GU |
R3‑193573 | NG based MBB Handover | Qualcomm Incorporated | imported from 3GU |
R3‑193574 | Discussion on the received LS on NPN scenarios for emergency calls and RAN sharing | Qualcomm Incorporated | imported from 3GU |
R3‑193575 | [Draft] Reply LS on RAN sharing and Emergency services with Non-Public Networks | Qualcomm Incorporated | imported from 3GU |
R3‑193576 | Discussion of NPN support for connected mode mobility | Qualcomm Incorporated | imported from 3GU |
R3‑193577 | Introduction of Non-Public Networks | Qualcomm Incorporated | imported from 3GU |
R3‑193578 | Discussion of NPN impacts on the F1 interface | Qualcomm Incorporated | imported from 3GU |
R3‑193579 | Benefits of periodicity and offset awareness for TSN traffic | Qualcomm Incorporated | imported from 3GU |
R3‑193580 | A note on CN PDB granularity | Qualcomm Incorporated | imported from 3GU |
R3‑193581 | 5G SRVCC procedure | Qualcomm Incorporated | imported from 3GU |
R3‑193582 | Introduction of 5G SRVCC (CR 38.413) | Qualcomm Incorporated | imported from 3GU |
R3‑193583 | Introduction of 5G SRVCC (CR 38.423) | Qualcomm Incorporated | imported from 3GU |
R3‑193584 | (TP for NR_pos BL CR for TS 38.305): Transmission Measurement Function in NG-RAN | Qualcomm Incorporated | imported from 3GU |
R3‑193585 | Discussion of F1AP requirements to support positioning | Qualcomm Incorporated | imported from 3GU |
R3‑193586 | Local NR positioning in NG-RAN | Qualcomm Incorporated | imported from 3GU |
R3‑193587 | Comparison of 5GC-LMF and RAN-LMC based Positioning | Qualcomm Incorporated | imported from 3GU |
R3‑193588 | Support of CSI-RS Configuration Transfer for SA and EN-DC | China Telecommunications | imported from 3GU |
R3‑193589 | Discussion on RAN3 Impact of TSC QoS | China Telecommunications | imported from 3GU |
R3‑193590 | Security aspects of Local LMF design | ZTE Corporation | imported from 3GU |
R3‑193591 | Discussion on the Mobility Load Management | CATT | imported from 3GU |
R3‑193592 | Support for Mobility Load Balancing for NR | CATT | imported from 3GU |
R3‑193593 | Support of Mobility Load Balancing over Xn interface | CATT | imported from 3GU |
R3‑193594 | Support of Mobility Load Balancing over F1 interface | CATT | imported from 3GU |
R3‑193595 | Support of Mobility Load Balancing over E1 interface | CATT | imported from 3GU |
R3‑193596 | Discussion on load balancing optimization for DC Scenario | CATT | imported from 3GU |
R3‑193597 | Support of Mobility Load Balancing over X2 interface | CATT | imported from 3GU |
R3‑193598 | Discusstion on inter-MN handover without SN change | CATT | imported from 3GU |
R3‑193599 | ( CR for TS 36.413) )Support of Inter-MN handover without SN change | CATT | imported from 3GU |
R3‑193600 | ( CR for TS 38.413) )Support of Inter-MN handover without SN change | CATT | imported from 3GU |
R3‑193601 | Trace function Support over F1 Interface for TS38.470 | ZTE, China Unicom, Ericsson, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193602 | Trace function Support over E1 Interface for TS38.460 | ZTE, China Unicom, Ericsson, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193603 | PSCell report in LTE DC | ZTE, Samsung, China Telecom | imported from 3GU |
R3‑193604 | PSCell information report in LTE | ZTE, Samsung, China Telecom | imported from 3GU |
R3‑193605 | PSCell information report in LTE | ZTE, Samsung, China Telecom | imported from 3GU |
R3‑193606 | PSCell information report in LTE | ZTE, Samsung, China Telecom | imported from 3GU |
R3‑193607 | Failure case for EN-DC TNL address discovery | ZTE Corporation | imported from 3GU |
R3‑193608 | Introduction failure case of TNL Address discovery for EN-DC | ZTE Corporation | imported from 3GU |
R3‑193609 | Clarification on Initial UL RRC Message Transfer procedure | ZTE Corporation | imported from 3GU |
R3‑193610 | Clarification on Network sharing | ZTE Corporation | imported from 3GU |
R3‑193611 | Update on TNL Address discovery for EN-DC for TS36.300 | ZTE Corporation | imported from 3GU |
R3‑193612 | Update on TNL Address discovery for EN-DC for TS36.300 | ZTE Corporation | imported from 3GU |
R3‑193613 | Update of TNL Address discovery for EN-DC (using new container) for TS36.413 | ZTE Corporation | imported from 3GU |
R3‑193614 | Clarification on Interface Instance Indication | ZTE Corporation | imported from 3GU |
R3‑193615 | Clarification on Interface Instance Indication for TS36.423 | ZTE Corporation | imported from 3GU |
R3‑193616 | Clarification on Interface Instance Indication for TS38.423 | ZTE Corporation | imported from 3GU |
R3‑193617 | Clarification on Interface Instance Indication for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑193618 | Discussion on Band Combination and Feature Set Selection over F1 | ZTE Corporation | imported from 3GU |
R3‑193619 | Combination and Feature Set Selection over F1 for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑193620 | Discussion on Multiple CU-UPs impact on NG interface | ZTE Corporation | imported from 3GU |
R3‑193621 | Support multiple CU-UPs over NG | ZTE Corporation | imported from 3GU |
R3‑193622 | Support split PDU session served by multiple CU-UPs | ZTE Corporation | imported from 3GU |
R3‑193623 | Security issu on local LMF | ZTE Corporation | imported from 3GU |
R3‑193624 | Consideration on NPN solution | ZTE Corporation | imported from 3GU |
R3‑193625 | Consideration on NPN solution | ZTE Corporation | imported from 3GU |
R3‑193626 | Discussion on CAG support for NR | ZTE Corporation | imported from 3GU |
R3‑193627 | Mobility Settings Change procedure for MRO/MLB | ZTE Corporation | imported from 3GU |
R3‑193628 | Stage2 CR for Mobility Settings Change | ZTE Corporation | imported from 3GU |
R3‑193629 | Consideration on RAN energy efficiency measurement | ZTE Corporation | imported from 3GU |
R3‑193630 | CR for TS38.300 for energy efficiency | ZTE Corporation | imported from 3GU |
R3‑193631 | Draft LS to SA5 on energy efficiency measurement | ZTE Corporation | imported from 3GU |
R3‑193632 | Discussion on Load Information Reporting for MLB | ZTE Corporation | imported from 3GU |
R3‑193633 | Discussion on Measurement Gap Configuration over F1 for Multiple-DU Scenario | ZTE | imported from 3GU |
R3‑193634 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 1) | ZTE | imported from 3GU |
R3‑193635 | Correction on Measurement Gap Configuration over F1 for TS38.473 (Option 2) | ZTE | imported from 3GU |
R3‑193636 | Correction on Load Information Reporting for TS38.300 | ZTE Corporation | imported from 3GU |
R3‑193637 | Correction on Load Information Reporting for TS36.423 | ZTE Corporation | imported from 3GU |
R3‑193638 | Correction on Load Information Reporting for TS38.420 | ZTE Corporation | imported from 3GU |
R3‑193639 | Correction on Load Information Reporting for TS38.423 | ZTE Corporation | imported from 3GU |
R3‑193640 | Correction on Load Information Reporting for TS38.460 | ZTE Corporation | imported from 3GU |
R3‑193641 | Correction on Load Information Reporting for TS38.463 | ZTE Corporation | imported from 3GU |
R3‑193642 | Correction on Load Information Reporting for TS38.470 | ZTE Corporation | imported from 3GU |
R3‑193643 | Correction on Load Information Reporting for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑193644 | Support of inter-system HO from SA to EN-DC in Rel-16 | China Telecommunications | imported from 3GU |
R3‑193645 | Discussion on authorization in NR V2X | ZTE, Sanechips | imported from 3GU |
R3‑193646 | Resource coordination in NR V2X | ZTE, Sanechips | imported from 3GU |
R3‑193647 | Support of NR V2X in case of CU-DU split | ZTE, Sanechips | imported from 3GU |
R3‑193648 | Consideration on IAB many to one bearer mapping | ZTE, Sanechips | imported from 3GU |
R3‑193649 | Consideration on control plane bearer mapping | ZTE, Sanechips | imported from 3GU |
R3‑193650 | Discussion on flow control in IAB | ZTE, Sanechips | imported from 3GU |
R3‑193651 | Discussion on BH RLC channel configuration in IAB | ZTE, Sanechips | imported from 3GU |
R3‑193652 | Parent node selection in IAB | ZTE, Sanechips | imported from 3GU |
R3‑193653 | Discussion on IAB RLF and IAB reestablishment | ZTE, Sanechips | imported from 3GU |
R3‑193654 | Discussion on network-controlled IAB migration handling | ZTE, Sanechips | imported from 3GU |
R3‑193655 | Discussion on inter-CU IAB migration handling | ZTE, Sanechips | imported from 3GU |
R3‑193656 | IAB node indication to CN | ZTE, Sanechips | imported from 3GU |
R3‑193657 | Consideration on IP Address Allocation in IAB | ZTE, Sanechips | imported from 3GU |
R3‑193658 | (TP for NR_IAB BL CR for TS 38.401): Support for inter-gNB-DU IAB topology adaptation procedure | ZTE, Sanechips | imported from 3GU |
R3‑193659 | Inter-gNB-DU mobility using MCG SRB procedure | NEC, NTT DOCOMO Inc. | imported from 3GU |
R3‑193660 | Inter-gNB-DU mobility using MCG SRB procedure | NEC, NTT DOCOMO Inc. | imported from 3GU |
R3‑193661 | PDU Session fail in Path Switch Request procedure | NEC | imported from 3GU |
R3‑193662 | PDU Session fail in Path Switch Request procedure | NEC | imported from 3GU |
R3‑193663 | Enhancements for More Efficient DL PDCP Duplication | NEC | imported from 3GU |
R3‑193664 | Reroute NSSF provided information | NEC | imported from 3GU |
R3‑193665 | CHO for Mobility Enhancement | NEC | imported from 3GU |
R3‑193666 | Correction on Maximum Integrity Protected Data Rate IE over E1 Interface | NEC | imported from 3GU |
R3‑193667 | On common solution for CAG and SNPN | NEC | imported from 3GU |
R3‑193668 | On SIB9 encoding for on-demand broadcast | NEC | imported from 3GU |
R3‑193669 | On SIB9 encoding and delivery | NEC | imported from 3GU |
R3‑193670 | Discussion on MR-DC low layer coordination with an MgNB-DU | CATT | imported from 3GU |
R3‑193671 | CR on MR-DC low layer coordination with an MgNB-DU | CATT | imported from 3GU |
R3‑193672 | LS on MR-DC low layer coordination with an MgNB-DU | CATT | imported from 3GU |
R3‑193673 | Discussion on DC Coordination for PDCCH Blind Detection | CATT | imported from 3GU |
R3‑193674 | CR on DC Coordination for PDCCH Blind Detection | CATT | imported from 3GU |
R3‑193675 | Discussion on MCG PHR format in MgNB-DU | CATT | imported from 3GU |
R3‑193676 | CR on MCG PHR format in MgNB-DU | CATT | imported from 3GU |
R3‑193677 | Discussion on definition of gNB and ng-eNB | CATT | imported from 3GU |
R3‑193678 | CR on definition of gNB and ng-eNB | CATT | imported from 3GU |
R3‑193679 | Discussion on PRACH coordination | CATT | imported from 3GU |
R3‑193680 | CR on PRACH coordination (38.300) | CATT | imported from 3GU |
R3‑193681 | CR on PRACH coordination (X2) | CATT | imported from 3GU |
R3‑193682 | CR on PRACH coordination (Xn) | CATT | imported from 3GU |
R3‑193683 | CR on PRACH coordination (F1) | CATT | imported from 3GU |
R3‑193684 | LS on PRACH coordination | CATT | imported from 3GU |
R3‑193685 | Discussion on Security of Multi-CU-UP connectivity | CATT,China Telecom | imported from 3GU |
R3‑193686 | LS on security for multi-CU-UP connectivity | CATT,China Telecom | imported from 3GU |
R3‑193687 | Discussion on Access Complete Indication of PSCell | CATT | imported from 3GU |
R3‑193688 | CR on Access Complete Indication of PSCell (X2) | CATT | imported from 3GU |
R3‑193689 | CR on Access Complete Indication of PSCell (Xn) | CATT | imported from 3GU |
R3‑193690 | CR on Access Complete Indication of PSCell (F1) | CATT | imported from 3GU |
R3‑193691 | Discussion on Handover Decision in EN-DC scenario | CATT | imported from 3GU |
R3‑193692 | CR on Handover Decision in EN-DC scenario | CATT | imported from 3GU |
R3‑193693 | Work plan for study on Enhancement for disaggregated gNB | CATT,China telecom | imported from 3GU |
R3‑193694 | Discussion on user plane enhancement | CATT,CAICT,China telecom | imported from 3GU |
R3‑193695 | Discussion on desired buffer size in DC scenario | CATT,China telecom | imported from 3GU |
R3‑193696 | Consideration on support of MRO | CATT | imported from 3GU |
R3‑193697 | Support of MRO(Stage 2) | CATT | imported from 3GU |
R3‑193698 | Support of MRO(Inter-system unnecessary HO and inter-system HO too early) | CATT | imported from 3GU |
R3‑193699 | Support of MRO(Inter-system HO too late andHO too early) | CATT | imported from 3GU |
R3‑193700 | Support of MRO(intra-system MRO and inter-system PingPong) | CATT | imported from 3GU |
R3‑193701 | LS on support of RIM procedure | CATT | imported from 3GU |
R3‑193702 | Enhancement of UE history information | CATT | imported from 3GU |
R3‑193703 | Discussion on MDT configuration for EN-DC sceanrio | CATT | imported from 3GU |
R3‑193704 | Support of MDT configruation for EN-DC sceanrio | CATT | imported from 3GU |
R3‑193705 | Support of MDT configruation for EN-DC sceanrio | CATT | imported from 3GU |
R3‑193706 | Support of MDT configruation for split RAN | CATT | imported from 3GU |
R3‑193707 | Discussion on inter-system handover from EN-DC to SA | CATT,China telecom | imported from 3GU |
R3‑193708 | Support of direct data forwarding between Source SN node and target node | CATT,China telecom | imported from 3GU |
R3‑193709 | Support of direct data forwarding between Source SN node and target node | CATT,China telecom | imported from 3GU |
R3‑193710 | Discussion on failed PDU session/E-RAB during handover procedure | CATT | imported from 3GU |
R3‑193711 | Correction on E-RAB to Release List in Handover Command message | CATT | imported from 3GU |
R3‑193712 | Correction on PDU Session Resources to Release List in Handover Command message | CATT | imported from 3GU |
R3‑193713 | LS on support of inter-system handover | CATT | imported from 3GU |
R3‑193714 | Discussion on the availability of NG-C TNL association | CATT | imported from 3GU |
R3‑193715 | Correction on source TNL ADDRESS in NG-C interface-Solution 1 | CATT | imported from 3GU |
R3‑193716 | Correction on source TNL ADDRESS in NG-C interface-Solution 2 | CATT | imported from 3GU |
R3‑193717 | Introduction of handover failure cause | CATT | imported from 3GU |
R3‑193718 | RAN3 Work Plan on 5G V2X with NR Sidelink WI | LG Electronics Inc., Huawei | imported from 3GU |
R3‑193719 | Correction on Maximum Integrity Protected Data Rate | NEC | imported from 3GU |
R3‑193720 | Correction on Maximum Integrity Protected Data Rate | NEC | imported from 3GU |
R3‑193721 | NPN support in NG-RAN | Intel Corporation | imported from 3GU |
R3‑193722 | Mobility aspects of NPN | Intel Corporation | imported from 3GU |
R3‑193723 | Introduction of NPN support in NG | Intel Corporation | imported from 3GU |
R3‑193724 | Introduction of NPN support in Xn | Intel Corporation | imported from 3GU |
R3‑193725 | Introduction of NPN support in F1 | Intel Corporation | imported from 3GU |
R3‑193726 | [DRAFT] Reply LS RAN sharing and Emergency services with Non-Public Networks | Intel Corporation | imported from 3GU |
R3‑193727 | [DRAFT] LS on NPN clarifications | Intel Corporation | imported from 3GU |
R3‑193728 | Correction of positioning methods support in gNB and ng-eNB in Rel-15 | Intel Corporation | imported from 3GU |
R3‑193729 | IAB Parent Node Selection | Ericsson | imported from 3GU |
R3‑193730 | (TP for NR-IAB BL CR for TS 38.401) IAB OAM Connectivity | Ericsson | imported from 3GU |
R3‑193731 | IAB Node Indication in RRCSetupComplete Message | Ericsson | imported from 3GU |
R3‑193732 | Mapping of CP Data Over Backhaul Links | Ericsson | imported from 3GU |
R3‑193733 | Uplink BH RLC Channel Mapping in IAB Nodes | Ericsson | imported from 3GU |
R3‑193734 | Signaling Aspects of BH RLC Channel and BAP Layer Configuration | Ericsson | imported from 3GU |
R3‑193735 | Next Hop Identifier for Packet Forwarding in IAB Networks | Ericsson | imported from 3GU |
R3‑193736 | (TP for NR-IAB BL CR for TS 38.473): DL Routing Configuration | Ericsson | imported from 3GU |
R3‑193737 | CR 38.463 IPv6 Flow Label Signalling and Allocation in IAB Networks | Ericsson | imported from 3GU |
R3‑193738 | (TP for NR-IAB BL CR for TS 38.473): IPv6 Flow Label and LCID Assignment for Bearer Mapping of UP Packets | Ericsson | imported from 3GU |
R3‑193739 | (TP for NR-IAB BL CR for TS 38.401) IP Address Management for IAB-nodes | Ericsson | imported from 3GU |
R3‑193740 | (TP for NR-IAB BL CR for TS 38.401) IAB Node Release Procedure | Ericsson | imported from 3GU |
R3‑193741 | (TP for NR-IAB BL CR for TS 38.401): IAB Protocol Stacks | Ericsson | imported from 3GU |
R3‑193742 | The Use of DSCP for IAB Bearer Mapping | Ericsson, Verizon Wireless, KDDI, AT&T | imported from 3GU |
R3‑193743 | Flow Control in IAB Networks | Ericsson | imported from 3GU |
R3‑193744 | IAB DL Flow Control - General Principles | Ericsson | imported from 3GU |
R3‑193745 | User Plane Aspects of Supporting NR-DC for IAB Nodes | Ericsson | imported from 3GU |
R3‑193746 | Support for Multiple MTs in the Same IAB Node | Ericsson | imported from 3GU |
R3‑193747 | CP Signalling via LTE for NSA IAB Deployments | Ericsson | imported from 3GU |
R3‑193748 | Support for LTE Deployment at IAB Node Sites | Ericsson | imported from 3GU |
R3‑193749 | Radio resource management policy | Huawei | imported from 3GU |
R3‑193750 | [Draft] Reply on radio resource management policy | Huawei | imported from 3GU |
R3‑193751 | Rapporteur update | Huawei | imported from 3GU |
R3‑193752 | Rapporteur update - clarification of semantics | Huawei | imported from 3GU |
R3‑193753 | Rapporteur update | Huawei | imported from 3GU |
R3‑193754 | Mobility Robustness Optimization | Huawei, LGU+ | imported from 3GU |
R3‑193755 | Mobility Robustness Optimization | Huawei | imported from 3GU |
R3‑193756 | Mobility Robustness Optimization | Huawei | imported from 3GU |
R3‑193757 | Mobility Robustness Optimization | Huawei | imported from 3GU |
R3‑193758 | Mobility Robustness Optimization | Huawei | imported from 3GU |
R3‑193759 | UE reported history information | Huawei | imported from 3GU |
R3‑193760 | UE reported history information | Huawei | imported from 3GU |
R3‑193761 | UE reported history information | Huawei | imported from 3GU |
R3‑193762 | UE reported history information | Huawei | imported from 3GU |
R3‑193763 | Slice availability over NG | Huawei | imported from 3GU |
R3‑193764 | Slice availability over NG | Huawei | imported from 3GU |
R3‑193765 | Load Sharing and Load Balancing Optimisation | Huawei, LGU+ | imported from 3GU |
R3‑193766 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193767 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193768 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193769 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193770 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193771 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193772 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193773 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193774 | Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑193775 | Signaling handover and reselection configuration change | Huawei | imported from 3GU |
R3‑193776 | Signaling handover and reselection configuration change | Huawei | imported from 3GU |
R3‑193777 | Signaling handover and reselection configuration change | Huawei | imported from 3GU |
R3‑193778 | Resources not available for the slice | Huawei | imported from 3GU |
R3‑193779 | Resources not available for the slice | Huawei | imported from 3GU |
R3‑193780 | Resources not available for the slice | Huawei | imported from 3GU |
R3‑193781 | Slice(s) not supported on E1 and F1 | Huawei | imported from 3GU |
R3‑193782 | Slice(s) not supported | Huawei | imported from 3GU |
R3‑193783 | Slice(s) not supported | Huawei | imported from 3GU |
R3‑193784 | New SA2 requirements for PSCell reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193785 | Enabling additional PSCell reporting and time since EN-DC was deconfigured | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193786 | Correction of handling of the Location Information at the MeNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193787 | Enabling additional PSCell reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193788 | Correction of handling of the Location Information at the MN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193789 | On Coordination for PDCP Duplication with NR-DC/CA Combination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193790 | Clarifications and signalling proposals for Mobility Optimization | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193791 | Support of Mobility Optimization | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193792 | Support of MLB in Rel-16 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193793 | Overload reporting enhancement | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193794 | Introduction of Load Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193795 | Introduction of Load Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193796 | RACH parameter communication over Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193797 | On RRM policies for slicing and network sharing in split deployment scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193798 | [DRAFT] Reply LS on radio resource management policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193799 | RAN3 aspects of user data congestion analysis in the NWDAF | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193800 | [DRAFT] Reply LS on User Data Congestion Analytics | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193801 | IAB parent node selection | AT&T | imported from 3GU |
R3‑193802 | F1AP signaling for IAB routing configuration | AT&T | imported from 3GU |
R3‑193803 | Architecture for SNPN with a CU DU Split | AT&T | imported from 3GU |
R3‑193804 | Architecture for SNPN with a CP UP Split | AT&T | imported from 3GU |
R3‑193805 | Support of inter-system direct forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193806 | Support of inter-system direct forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193807 | Support of inter-system direct forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193808 | (TP for direct data_forwarding BL CR for TS 38.413) Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193809 | Inter-system direct forwarding with shared SgNB/gNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193810 | Redundant transmission over Xn for solution 1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193811 | Support of Redundant PDU sessions for high layer multi-connectivity solution 1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193812 | Redundant transmission over NG for solution 4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193813 | Support of Redundant transmission over NG with solution 4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193814 | LS on Implementation of redundant transmission for solution 4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193815 | Redundant transmission at handover with solution 4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193816 | Support of Redundant transmission over Xn with solution 4 | Nokia, Nokia Shanghai Bel | imported from 3GU |
R3‑193817 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193818 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193819 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193820 | LS on completion of SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193821 | Introduction of CP NBIOT procedures when connected to 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193822 | Introduction of suspend-resume for 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193823 | Introduction of suspend resume for 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193824 | Introduction of suspend resume for 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑193825 | Introduction of suspend resume for 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑193826 | Discussion on support of Conditional Handover | China Telecommunication | imported from 3GU |
R3‑193827 | Discussion on data forwarding procedure for non-spilt bearer handover | China Telecommunication | imported from 3GU |
R3‑193828 | Introduction of support Public network integrated NPN on NG interface | China Telecommunication | imported from 3GU |
R3‑193829 | CR to 38.413 for introducing PNI-NPN in Rel-16 | China Telecommunication | imported from 3GU |
R3‑193830 | Introduction of support Standalone NPN on NG interface | China Telecommunication | imported from 3GU |
R3‑193831 | CR to 38.413 for introducing SNPN in Rel-16 | China Telecommunication | imported from 3GU |
R3‑193832 | On Private Network Support for NG-RAN | China Telecommunication | imported from 3GU |
R3‑193833 | Work Plan for Private Network Support for NR-RAN WI | China Telecommunication | imported from 3GU |
R3‑193834 | Reply LS on RAN sharing and Emergency services with Non-Public Networks | China Telecommunication | imported from 3GU |
R3‑193835 | On introducing Non Public Network in NG-RAN architecture | China Telecommunication | imported from 3GU |
R3‑193836 | CR for introducing Non Public Netwrok in NG-RAN architecture | China Telecommunication | imported from 3GU |
R3‑193837 | Non IP bearer support for Dual Connectivity | Huawei, Vodafone | imported from 3GU |
R3‑193838 | Non IP bearer support for Dual Connectivity | Huawei, Vodafone | imported from 3GU |
R3‑193839 | Correction on Location Reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193840 | Clarification on SCTP association removal | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193841 | Clarification for TNLA removal | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193842 | Clarification for TNLA removal | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193843 | Analysis on virtualized RAN with IP address sharing | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193844 | Support for Dynamic Port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193845 | Support for Dynamic Port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193846 | Support for Dynamic Port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193847 | Support for Dynamic Port | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193848 | Work Plan for NR WWC WI | Huawei | imported from 3GU |
R3‑193849 | Motivation of WWC call meetings | Huawei | imported from 3GU |
R3‑193850 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑193851 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑193852 | Overview of WWC work | Huawei, Telecom Italia | imported from 3GU |
R3‑193853 | Support of trusted non-3GPP access | Huawei, Telecom Italia | imported from 3GU |
R3‑193854 | Support of 5G-RG connected to 5GC | Huawei, Telecom Italia | imported from 3GU |
R3‑193855 | Support of FN-RG connected to 5GC | Huawei | imported from 3GU |
R3‑193856 | Support of 5G capable UE for WWC | Huawei | imported from 3GU |
R3‑193857 | [Draft] LS on introducing WWC in RAN | Huawei | imported from 3GU |
R3‑193858 | Support of hybrid access for WWC | Huawei | imported from 3GU |
R3‑193859 | CR to support hybrid access to EPC | Huawei | imported from 3GU |
R3‑193860 | Correction on E-RAB to Release List in Handover Command message | CATT | imported from 3GU |
R3‑193861 | Correction on PDU Session Resources to Release List in Handover Command message | CATT | imported from 3GU |
R3‑193862 | Issue on MRO in case of intra-system mobility | LG Electronics | imported from 3GU |
R3‑193863 | Load reporting via Xn and F1 for load balancing | LG Electronics | imported from 3GU |
R3‑193864 | Flow control mechanism for DL and UL in IAB network | LG Electronics | imported from 3GU |
R3‑193865 | (TP for NR_IAB BL CR for TS 38.401): IAB-node migration between different IAB-donors | LG Electronics | imported from 3GU |
R3‑193866 | Mobility Robustness Optimization | Huawei | imported from 3GU |
R3‑193867 | Issue on MRO in case of intra-system mobility | LG Electronics, LG Uplus | imported from 3GU |
R3‑193868 | Load reporting via Xn and F1 for load balancing | LG Electronics, LG Uplus | imported from 3GU |
R3‑193869 | CR to 38.463 on Cause Value correction | ZTE | imported from 3GU |
R3‑193870 | CR to 38.473 on Cause Value correction | ZTE | imported from 3GU |
R3‑193871 | Core Network Assistance Info in DOWNLINK NAS TRANSPORT procedure | ZTE | imported from 3GU |
R3‑193872 | Core Network Assistance Info in DOWNLINK NAS TRANSPORT for TS38.413 | ZTE | imported from 3GU |
R3‑193873 | Support of Network Sharing with RRC Resume | ZTE | imported from 3GU |
R3‑193874 | Support of Network Sharing with RRC Resume for TS38.401 | ZTE | imported from 3GU |
R3‑193875 | Reroute NSSF provided information for TS38.413 | ZTE, Interdigital, NOKIA, NOKIA Shanghai Bell | imported from 3GU |
R3‑193876 | Consideration on NR IP SEC | ZTE | imported from 3GU |
R3‑193877 | Detection solution for SN change failure | ZTE | imported from 3GU |
R3‑193878 | Stage2 CR for Detection solution for SN change failure | ZTE | imported from 3GU |
R3‑193879 | MDT activation for INACTIVE&IDLE mode UE | ZTE | imported from 3GU |
R3‑193880 | MDT activation for INACTIVE_IDLE mode UE for TS38.413 | ZTE | imported from 3GU |
R3‑193881 | MRO initial consideration | ZTE | imported from 3GU |
R3‑193882 | MRO Inter system signalling consideration | ZTE | imported from 3GU |
R3‑193883 | MRO Connection failure due to intra system mobility | ZTE | imported from 3GU |
R3‑193884 | MRO Connection failure due to intra system mobility in TS38.300 | ZTE | imported from 3GU |
R3‑193885 | MRO Common CR for TS38.423 | ZTE | imported from 3GU |
R3‑193886 | MRO Common CR for TS38.420 | ZTE | imported from 3GU |
R3‑193887 | MRO intra system HetNET depolyment | ZTE | imported from 3GU |
R3‑193888 | MRO intra system HetNET depolyment in TS38.300 | ZTE | imported from 3GU |
R3‑193889 | MRO intra system HetNET depolyment in TS38.423 | ZTE | imported from 3GU |
R3‑193890 | MRO Connection failure due to inter system mobility | ZTE | imported from 3GU |
R3‑193891 | MRO Connection failure due to inter system mobility in TS38.300 | ZTE | imported from 3GU |
R3‑193892 | MRO Connection failure due to inter system mobility in TS38.413 | ZTE | imported from 3GU |
R3‑193893 | MRO Connection failure due to inter system mobility in TS36.413 | ZTE | imported from 3GU |
R3‑193894 | MRO Inter system ping pong | ZTE | imported from 3GU |
R3‑193895 | MRO Inter system ping pong in TS38.300 | ZTE | imported from 3GU |
R3‑193896 | MRO Inter system ping pong in TS38.413 | ZTE | imported from 3GU |
R3‑193897 | MRO Inter system ping pong in TS36.300 | ZTE | imported from 3GU |
R3‑193898 | MRO Inter system ping pong in TS36.423 | ZTE | imported from 3GU |
R3‑193899 | MRO Unnecessary HO to another System | ZTE | imported from 3GU |
R3‑193900 | MRO Unnecessary HO to another System in TS38.413 | ZTE | imported from 3GU |
R3‑193901 | MRO Unnecessary HO to another System in TS38.300 | ZTE | imported from 3GU |
R3‑193902 | MRO Unnecessary HO to another System in TS36.300 | ZTE | imported from 3GU |
R3‑193903 | MRO Unnecessary HO to another System in TS36.413 | ZTE | imported from 3GU |
R3‑193904 | RACH report for NR RACH optimization | ZTE | imported from 3GU |
R3‑193905 | RACH report for NR RACH optimization in TS38.473 | ZTE | imported from 3GU |
R3‑193906 | Signalling support for NR MDT | ZTE | imported from 3GU |
R3‑193907 | Signalling support for NR MDT CR in TS38.413 | ZTE | imported from 3GU |
R3‑193908 | Signalling support for NR MDT CR in TS38.423 | ZTE | imported from 3GU |
R3‑193909 | Signaling handover and reselection configuration change | Huawei | imported from 3GU |
R3‑193910 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
R3‑193911 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
R3‑193912 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
R3‑193913 | NAS PDU order | Huawei | imported from 3GU |
R3‑193914 | Correction of NAS PDU order | Huawei | imported from 3GU |
R3‑193915 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
R3‑193916 | Enforcement of UP integrity protection | Huawei | imported from 3GU |
R3‑193917 | Correction of DSCP Derivation | Huawei | imported from 3GU |
R3‑193918 | Correction of Reflective QoS Attribute | Huawei | imported from 3GU |
R3‑193919 | Correction of backup AMF name | Huawei | imported from 3GU |
R3‑193920 | Correction of NAS transparent container | Huawei | imported from 3GU |
R3‑193921 | Correction of N3IWF key | Huawei | imported from 3GU |
R3‑193922 | Correction of Handover Command message | Huawei, CATT | imported from 3GU |
R3‑193923 | Correction of error handling of AP ID | Huawei | imported from 3GU |
R3‑193924 | Addition of timer capability for AMF planned removal | Huawei | imported from 3GU |
R3‑193925 | Remaining issues on direct data forwarding for inter-system handover | Huawei | imported from 3GU |
R3‑193926 | Direct data forwarding for inter-system handover | Huawei | imported from 3GU |
R3‑193927 | Notifcation Control interaction with inter-DU HO-38473 | CATT | imported from 3GU |
R3‑193928 | Notifcation Control interaction with SN change-37340 | CATT | imported from 3GU |
R3‑193929 | Discussion intra-CU eMBB Handover | CATT | imported from 3GU |
R3‑193930 | (TP for [NR_Mob_enh] BL CR for TS 38.473): intra-CU eMBB Handover | CATT | imported from 3GU |
R3‑193931 | Consideration on CHO Signaling Procedure | CATT | imported from 3GU |
R3‑193932 | Discussion intra-CU CHO | CATT | imported from 3GU |
R3‑193933 | (TP for [NR_Mob_enh] BL CR for TS 38.473): intra-CU CHO | CATT | imported from 3GU |
R3‑193934 | The Issues on Data Forwarding Specifics of CHO | CATT | imported from 3GU |
R3‑193935 | Consideration on Efficient PDCP Duplication | CATT | imported from 3GU |
R3‑193936 | Discussion on Higher Layer Multi-Connectivity | CATT | imported from 3GU |
R3‑193937 | CR to 38.300 on NRIIOT Higher Layer Multi-Connectivity | CATT | imported from 3GU |
R3‑193938 | Discussion on Higher Layer Multi-Connectivity Solution#1 | CATT | imported from 3GU |
R3‑193939 | CR to 38.413 on NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT | imported from 3GU |
R3‑193940 | CR to 38.423 on NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT | imported from 3GU |
R3‑193941 | CR to 38.463 on NRIIOT Higher Layer Multi-Connectivity Solution#1 | CATT | imported from 3GU |
R3‑193942 | Discussion on Higher Layer Multi-Connectivity Solution#4 | CATT | imported from 3GU |
R3‑193943 | CR to 38.413 on NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT | imported from 3GU |
R3‑193944 | CR to 38.423 on NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT | imported from 3GU |
R3‑193945 | CR to 38.463 on NRIIOT Higher Layer Multi-Connectivity Solution#4 | CATT | imported from 3GU |
R3‑193946 | Consideration on local NR positioning in NG-RAN | CATT, CAICT | imported from 3GU |
R3‑193947 | Discussion on RAN-LMF impacting on Xn | CATT | imported from 3GU |
R3‑193948 | Discussion on NG-RAN acting as LCS client | CATT | imported from 3GU |
R3‑193949 | Trace (de)activation for F1AP and E1AP | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193950 | Trace function support stage-2 | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193951 | Supporting Trace activation/Deactivation in E1AP | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193952 | Adding Trace Messages in F1AP | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑193953 | (TP for NR_IAB BL CR for TS38.401) IAB OAM | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193954 | Next IAB hop identification and Forwarding table configuration | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193955 | Admission Control during BH RLC Channel establishment | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193956 | Analysis on IP address management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193957 | IAB impact to E1 interface | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193958 | Support for IAB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193959 | F1AP signalling over RRC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193960 | Draft 38.300 BL CR for Information | Nokia, Nokia Shanghai Bell, China Telecom | imported from 3GU |
R3‑193961 | Overview of RAN3 impacts of PNI NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193962 | Introduction of PNI NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193963 | Overview of RAN3 impacts of Stand-alone NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193964 | Introduction of Stand-alone NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193965 | LS on mobility in Stand-alone NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑193966 | Skeleton TR for Study on Enhancement for Disaggregated gNB | China Telecommunications | imported from 3GU |
R3‑193967 | Further corrections on PWS over F1 | Samsung | imported from 3GU |
R3‑193968 | CR on further corrections on PWS over F1 | Samsung | imported from 3GU |
R3‑193969 | (TP for NR_IAB BL CR for TS36.423) IAB node indication for X2 handover | Samsung | imported from 3GU |
R3‑193970 | (TP for NR_IAB BL CR for TS38.401) Discussion on IAB node integration procedure | Samsung | imported from 3GU |
R3‑193971 | (TP for NR_IAB BL CR for TS36.423) Discussion on parent node selection | Samsung | imported from 3GU |
R3‑193972 | Discussion on IP traffic mapping based on flow label&DSCP | Samsung | imported from 3GU |
R3‑193973 | (TP for NR_IAB BL CR for 38.473) IP traffic mapping configuration over F1 | Samsung | imported from 3GU |
R3‑193974 | (TP for NR_IAB BL CR for TS36.423) IP traffic mapping configuration over X2 | Samsung | imported from 3GU |
R3‑193975 | (NR_IAB BL CR for 38.463) IP traffic mapping configuration over E1 | Samsung | imported from 3GU |
R3‑193976 | Control signalling mapping in IAB network | Samsung | imported from 3GU |
R3‑193977 | (TP for NR_IAB BL CR for TS38.473) Discussion on QoS parameters for BH RLC CH | Samsung | imported from 3GU |
R3‑193978 | (TP for NR_IAB BL CR for TS38.473) Discussion on BH RLC CH setup/modification failure | Samsung | imported from 3GU |
R3‑193979 | Further discussion on IP address issues of IAB network | Samsung | imported from 3GU |
R3‑193980 | [Draft] LS on IP assignment in IAB network | Samsung | imported from 3GU |
R3‑193981 | DL End-to-end flow control in IAB network | Samsung | imported from 3GU |
R3‑193982 | Retransmission packet indication in IAB network | Samsung | imported from 3GU |
R3‑193983 | Discussion on routing configuration | Samsung | imported from 3GU |
R3‑193984 | Overview on IAB node migration | Samsung | imported from 3GU |
R3‑193985 | IP address management during the IAB migration | Samsung | imported from 3GU |
R3‑193986 | Overview on IAB node reestablishment | Samsung | imported from 3GU |
R3‑193987 | Stage 2 impact on higher layer duplication | Samsung | imported from 3GU |
R3‑193988 | CR for TS 38.300 on Higher Layer Duplication | Samsung | imported from 3GU |
R3‑193989 | RAN3 impacts for PDU session setup in Solution 1 | Samsung | imported from 3GU |
R3‑193990 | Associated PDU Session ID for PDU Session Setup in Solution 1 | Samsung | imported from 3GU |
R3‑193991 | Associated PDU Session ID for PDU Session Setup in Solution 1 | Samsung | imported from 3GU |
R3‑193992 | RSN for PDU Session Setup in Solution 1 | Samsung | imported from 3GU |
R3‑193993 | RSN for PDU Session Setup in Solution 1 | Samsung | imported from 3GU |
R3‑193994 | The indications of the Secondary RAN to SMF for Solution 1 | Samsung | imported from 3GU |
R3‑193995 | NGAP impacts for indicating the Secondary RAN to SMF | Samsung | imported from 3GU |
R3‑193996 | Inter-system direct forwarding with shared SgNB/gNB | Samsung | imported from 3GU |
R3‑193997 | Editorial Correction | Samsung | imported from 3GU |
R3‑193998 | [DRAFT] LS on Radio Link Failure Report from UE for MRO | Samsung | imported from 3GU |
R3‑193999 | Private Network Support Access Control | Samsung | imported from 3GU |
R3‑194000 | CR for Private Network Impact in NG | Samsung | imported from 3GU |
R3‑194001 | CR for Private Network Impact in Xn | Samsung | imported from 3GU |
R3‑194002 | Private Network Support in F1 interface | Samsung | imported from 3GU |
R3‑194003 | Discussion for MDT procedures and measurements | Samsung | imported from 3GU |
R3‑194004 | NG-RAN impacts for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194005 | E1/F1 impacts in NG-RAN architecture for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194006 | The impacts on Xn general aspects and principles for NR MDT/TRACE features | Samsung | imported from 3GU |
R3‑194007 | The impacts on E1 general aspects and principles for NR MDT/TRACE features | Samsung | imported from 3GU |
R3‑194008 | The impacts on F1 general aspects and principles for NR MDT/TRACE features | Samsung | imported from 3GU |
R3‑194009 | E1AP impacts for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194010 | F1AP impacts for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194011 | NGAP impacts for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194012 | XnAP impacts for MDT activation and reporting | Samsung | imported from 3GU |
R3‑194013 | Discussion for MDT reporting in split RAN | Samsung | imported from 3GU |
R3‑194014 | Discussion for MRO impacts | Samsung | imported from 3GU |
R3‑194015 | NG-RAN impacts for MRO features | Samsung | imported from 3GU |
R3‑194016 | NGAP impacts for MRO features in NR | Samsung | imported from 3GU |
R3‑194017 | XnAP impacts for MRO features | Samsung | imported from 3GU |
R3‑194018 | Discussion for Successful HO report in MRO features | Samsung | imported from 3GU |
R3‑194019 | NGAP impacts for Successful HO report in MRO features | Samsung | imported from 3GU |
R3‑194020 | XnAP impacts for Successful HO report in MRO features | Samsung | imported from 3GU |
R3‑194021 | Discussion for MLB impacts | Samsung | imported from 3GU |
R3‑194022 | NG-RAN impacts for MLB features | Samsung | imported from 3GU |
R3‑194023 | E1AP impacts for MLB features | Samsung | imported from 3GU |
R3‑194024 | F1AP impacts for MLB features | Samsung | imported from 3GU |
R3‑194025 | NGAP impacts for MLB features in NR | Samsung | imported from 3GU |
R3‑194026 | XnAP impacts for MLB features | Samsung | imported from 3GU |
R3‑194027 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑194028 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑194029 | Retainability measurements for DRBs and QoS flows | Ericsson | imported from 3GU |
R3‑194030 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
R3‑194031 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
R3‑194032 | Reference 38.411 and clean up empty sections | Ericsson | imported from 3GU |
R3‑194033 | Clean up empty sections | Ericsson | imported from 3GU |
R3‑194034 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
R3‑194035 | CR to 38.413 for signalling design for RIM | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194036 | Endiannes for the Payload Protocol Identifier in S1 | Ericsson | imported from 3GU |
R3‑194037 | CR to 38.413 for signalling design for RIM (OutofContainer) | Huawei | imported from 3GU |
R3‑194038 | Endiannes for the Payload Protocol Identifier in X2 | Ericsson | imported from 3GU |
R3‑194039 | Endiannes for the Payload Protocol Identifier in Xw | Ericsson | imported from 3GU |
R3‑194040 | Endiannes for the Payload Protocol Identifier in NG | Ericsson | imported from 3GU |
R3‑194041 | The clarfiction of NCGI defnition | Samsung | imported from 3GU |
R3‑194042 | Endiannes for the Payload Protocol Identifier in Xn | Ericsson | imported from 3GU |
R3‑194043 | PDCP duplication with more than 2 entities | Huawei | imported from 3GU |
R3‑194044 | Dynamic control of UL duplication | Huawei | imported from 3GU |
R3‑194045 | Resource efficient DL PDCP duplication | Huawei | imported from 3GU |
R3‑194046 | (TP for IIoT BL CR for TS 38.300) Higher layer duplication | Huawei | imported from 3GU |
R3‑194047 | Higher layer duplication for solution 4 | Huawei, LGU+ | imported from 3GU |
R3‑194048 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
R3‑194049 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
R3‑194050 | Higher layer duplication for solution 4 | Huawei | imported from 3GU |
R3‑194051 | IIoT QoS support over NG | Huawei | imported from 3GU |
R3‑194052 | IIoT QoS support between RAN nodes | Huawei | imported from 3GU |
R3‑194053 | Dynamic CN component of PDB | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194054 | Dynamic CN component of PDB | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194055 | Dynamic CN component of PDB | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194056 | Dynamic CN component of PDB | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194057 | (TP for IIoT BL CR for TS 38.300) Dynamic CN component of PDB | Huawei | imported from 3GU |
R3‑194058 | Reference timing delivery over F1 | Huawei | imported from 3GU |
R3‑194059 | Reference timing delivery over F1 | Huawei | imported from 3GU |
R3‑194060 | Higher layer duplication for solution 1 | Huawei | imported from 3GU |
R3‑194061 | Higher layer duplication for solution 1 | Huawei | imported from 3GU |
R3‑194062 | Higher layer duplication for solution 1 | Huawei | imported from 3GU |
R3‑194063 | Endiannes for the Payload Protocol Identifier in E1 | Ericsson | imported from 3GU |
R3‑194064 | Endiannes for the Payload Protocol Identifier in F1 | Ericsson | imported from 3GU |
R3‑194065 | Conditional Handover Cancel & Modification | Samsung | imported from 3GU |
R3‑194066 | Data Notification | Ericsson | imported from 3GU |
R3‑194067 | Introducing CHO indication to gNB-DU and gNB-CU-UP | Samsung | imported from 3GU |
R3‑194068 | NR Assistance Data Delivery over F1AP | Ericsson | imported from 3GU |
R3‑194069 | Support for Positioning Measurements in F1AP | Ericsson | imported from 3GU |
R3‑194070 | Positioning Measurement Functions | Ericsson | imported from 3GU |
R3‑194071 | (TP for NR_Mob_enh BL CR for TS 38.463): Introducing CHO indication over E1 | Samsung R&D | imported from 3GU |
R3‑194072 | (TP for NR_Mob_enh BL CR for TS 38.473): Introducing CHO indication over F1 | Samsung | imported from 3GU |
R3‑194073 | Consideration on Routing in IAB | ZTE, Sanechips | imported from 3GU |
R3‑194074 | Establishing two NG-U tunnels for single PDU Session (Solution 4) | Samsung | imported from 3GU |
R3‑194075 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT | imported from 3GU |
R3‑194076 | (TP for NR_IIOT BL CR for TS 38.413): Establishing two NG-U tunnels for single PDU Session (Solution 4) | Samsung | imported from 3GU |
R3‑194077 | gNB-CU-UP ID | Ericsson | imported from 3GU |
R3‑194078 | Slice availability issue in RRC resume for inactive UE | Huawei | imported from 3GU |
R3‑194079 | CR to 38.300 for Slice availability issue in RRC resume for inactive UE | Huawei | imported from 3GU |
R3‑194080 | Serving AMF change in RRC reestablishment | Huawei | imported from 3GU |
R3‑194081 | CR to 38.300 for Serving AMF change in RRC reestablishment | Huawei | imported from 3GU |
R3‑194082 | Correction to EN-DC TNL address discovery | Huawei | imported from 3GU |
R3‑194083 | CSI-RS configuration Transfer | Huawei | imported from 3GU |
R3‑194084 | CR to 38.423 on CSI-RS configuration Transfer | Huawei | imported from 3GU |
R3‑194085 | CR to 38.420 on CSI-RS configuration Transfer | Huawei | imported from 3GU |
R3‑194086 | CR to 38.473 on CSI-RS configuration Transfer | Huawei | imported from 3GU |
R3‑194087 | CR to 38.470 on CSI-RS configuration Transfer | Huawei | imported from 3GU |
R3‑194088 | CLI Stage 2 CR correction | Huawei | imported from 3GU |
R3‑194089 | RACH Optimisation in NR | Huawei | imported from 3GU |
R3‑194090 | CR to 38.300 on RACH Optimisation | Huawei | imported from 3GU |
R3‑194091 | CR to 38.401 on RACH Optimisation | Huawei | imported from 3GU |
R3‑194092 | CR to 38.423 on RACH Optimisation | Huawei | imported from 3GU |
R3‑194093 | CR to 38.470 on RACH Optimisation | Huawei | imported from 3GU |
R3‑194094 | CR to 38.473 on RACH Optimisation | Huawei | imported from 3GU |
R3‑194095 | Support of logged MDT | Huawei, LGU+ | imported from 3GU |
R3‑194096 | CR to 38.413 on MDT | Huawei | imported from 3GU |
R3‑194097 | CR to 37.320 on MDT | Huawei | imported from 3GU |
R3‑194098 | CR to 38.473 on MDT | Huawei | imported from 3GU |
R3‑194099 | CR to 38.463 on MDT | Huawei | imported from 3GU |
R3‑194100 | Support of MDT for RRC_INACTIVE UEs | Huawei | imported from 3GU |
R3‑194101 | Support of immediate MDT | Huawei, LGU+ | imported from 3GU |
R3‑194102 | Discussion on L2 measurement | Huawei | imported from 3GU |
R3‑194103 | CR to 38.463 on L2 measurement | Huawei | imported from 3GU |
R3‑194104 | CR to 38.473 on L2 measurement | Huawei | imported from 3GU |
R3‑194105 | Discussion on user data congestion analytics | Huawei | imported from 3GU |
R3‑194106 | Draft Reply LS on user data congestion analytics | Huawei | imported from 3GU |
R3‑194107 | Discussion on the FFSes for CHO | Huawei | imported from 3GU |
R3‑194108 | (TP for NR_Mob_enh BL CR for TS 38.423): Discussion on the FFSes for CHO | Huawei | imported from 3GU |
R3‑194109 | (TP for NR_Mob_enh BL CR for TS 36.423): Discussion on the FFSes for CHO | Huawei | imported from 3GU |
R3‑194110 | Discussion on data forwarding for CHO | Huawei | imported from 3GU |
R3‑194111 | (TP for NR_Mob_enh BL CR for TS 38.300): Discussion on data forwarding for CHO | Huawei | imported from 3GU |
R3‑194112 | (TP for NR_Mob_enh BL CR for TS 36.300): Discussion on data forwarding for CHO | Huawei | imported from 3GU |
R3‑194113 | (TP for NR_Mob_enh BL CR for TS 38.300): CHO procedure | Huawei | imported from 3GU |
R3‑194114 | F1 impact in CHO | Huawei | imported from 3GU |
R3‑194115 | CR to 38.473 on F1 impact in CHO | Huawei | imported from 3GU |
R3‑194116 | Discussion on Conditional SN Change in MR-DC | Huawei | imported from 3GU |
R3‑194117 | CR to 37.340 on Discussion on Conditional SN Change in MR-DC | Huawei | imported from 3GU |
R3‑194118 | (TP for NR_Mob_enh BL CR for TS 38.423):Discussion on Conditional SN Change in MR-DC | Huawei | imported from 3GU |
R3‑194119 | (TP for NR_IIOT BL CR for TS 38.423): Establishing two NG-U tunnels for single PDU Session (Solution 4) | Samsung | imported from 3GU |
R3‑194120 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194121 | (TP for NR_IIOT BL CR for TS 38.463): Establishing two NG-U tunnels for single PDU Session (Solution 4) | Samsung | imported from 3GU |
R3‑194122 | About the case necessary UE capabilities not being supported. | Ericsson | imported from 3GU |
R3‑194123 | Data forwarding for URLLC service with two NG-U tunnels for single PDU Session (solution 4) | Samsung | imported from 3GU |
R3‑194124 | Discussion on TSC Assistance Information | Samsung | imported from 3GU |
R3‑194125 | (TP for NR_IIOT BL CR for TS 38.413): TSC Assistance Information | Samsung | imported from 3GU |
R3‑194126 | (TP for NR_IIOT BL CR for TS 38.423): TSC Assistance Information | Samsung | imported from 3GU |
R3‑194127 | (TP for NR_IIOT BL CR for TS 38.463): TSC Assistance Information | Samsung | imported from 3GU |
R3‑194128 | (TP for NR_IIOT BL CR for TS 38.473): TSC Assistance Information | Samsung | imported from 3GU |
R3‑194129 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑194130 | Discussion on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Ericsson | imported from 3GU |
R3‑194131 | Introducing enhanced Notification Control and alternative QoS profiles | Ericsson | imported from 3GU |
R3‑194132 | [Draft] LS Reply on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Ericsson | imported from 3GU |
R3‑194133 | Introducing enhanced Notification Control and alternative QoS profiles | Ericsson | imported from 3GU |
R3‑194134 | Introducing alternative QoS profiles | Ericsson | imported from 3GU |
R3‑194135 | Introducing enhanced Notification Control and alternative QoS profiles | Ericsson | imported from 3GU |
R3‑194136 | Network Sharing for NPN | Ericsson | imported from 3GU |
R3‑194137 | [Draft] Reply LS on RAN sharing with Non-Public Networks | Ericsson | imported from 3GU |
R3‑194138 | Retainability measurements for DRBs and QoS flows | Ericsson | imported from 3GU |
R3‑194139 | Reply LS on Data activity reporting | Ericsson | imported from 3GU |
R3‑194140 | Rapporteur corrections to Version 15.2.1 | Ericsson | imported from 3GU |
R3‑194141 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
R3‑194142 | Clarification on the handling of CG-ConfigInfo over F1 | Ericsson | imported from 3GU |
R3‑194143 | Clarification on the handling of CG-ConfigInfo over F1 | Ericsson | imported from 3GU |
R3‑194144 | Correction of S-NSSAI presence | Ericsson | imported from 3GU |
R3‑194145 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194146 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194147 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194148 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194149 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194150 | Procedure description on optional IEs in CU to DU RRC information IE | Ericsson | imported from 3GU |
R3‑194151 | On the correct usage of semantic descriptions (TS 38.463 rapporteur) | Ericsson | imported from 3GU |
R3‑194152 | Correction of semantic descriptions in TS 38.463 (rapporteur) | Ericsson | imported from 3GU |
R3‑194153 | Rapporteur’s corrections for TS 38.463 | Ericsson | imported from 3GU |
R3‑194154 | NGAP correction of Initial Context Setup procedure text | Ericsson | imported from 3GU |
R3‑194155 | Rapporteur corrections to Version 15.2.1 | Ericsson | imported from 3GU |
R3‑194156 | Clarification of cardinality for the NG-RAN Architecture | Ericsson | imported from 3GU |
R3‑194157 | Rapporteur’s corrections for TS 38.423 | Ericsson | imported from 3GU |
R3‑194158 | GTP Transport Layer Addresses for SON Configuration Transfer | Ericsson | imported from 3GU |
R3‑194159 | GTP Transport Layer Addresses for SON Configuration Transfer | Ericsson | imported from 3GU |
R3‑194160 | Endianness for the Payload Protocol Identifier | Ericsson | imported from 3GU |
R3‑194161 | Data notification for CIoT UEs in Idle mode | Ericsson | imported from 3GU |
R3‑194162 | Common UP and CP aspects of CIoT when connected to 5GC | Ericsson | imported from 3GU |
R3‑194163 | (TP for Support of Enhanced Coverage restriction in NGAP for LTE-M UEs BL CR for TS 38.413): Introduction of common UP/CP CIoT features to NGAP | Ericsson | imported from 3GU |
R3‑194164 | Conditional Handover - HO preparation | Ericsson | imported from 3GU |
R3‑194165 | Explaining NPN | Ericsson | imported from 3GU |
R3‑194166 | Support for CU-DU Split – F1 interface impact | Ericsson | imported from 3GU |
R3‑194167 | Support for CP-UP Split – Impact on E1 interface | Ericsson | imported from 3GU |
R3‑194168 | Introduce SRVCC from 5G to 3G | Ericsson | imported from 3GU |
R3‑194169 | Support SRVCC from 5G to 3G | Ericsson | imported from 3GU |
R3‑194170 | Support SRVCC from 5G to 3G | Ericsson | imported from 3GU |
R3‑194171 | Support SRVCC from 5G to 3G | Ericsson | imported from 3GU |
R3‑194172 | NR Uplink Positioning for Split gNB | Ericsson | imported from 3GU |
R3‑194173 | How to Support Positioning Measurements in F1AP | Ericsson | imported from 3GU |
R3‑194174 | NR V2X Service Authorization in NG-RAN | Ericsson | imported from 3GU |
R3‑194175 | Introduction of V2X Service Authorization and UE SL AMBR in NGAP | Ericsson | imported from 3GU |
R3‑194176 | Introduction of V2X Service Authorization and UE SL AMBR in XnAP | Ericsson | imported from 3GU |
R3‑194177 | Positioning Server Functionality and the NG-RAN | Ericsson | imported from 3GU |
R3‑194178 | Positioning Client Functionality in NG-RAN | Ericsson | imported from 3GU |
R3‑194179 | [DRAFT] LS on Location Client in NG-RAN | Ericsson | imported from 3GU |
R3‑194180 | Discussion and Solution on number of served cells in Xn/X2 Setup | Ericsson | imported from 3GU |
R3‑194181 | EN-DC X2 Setup message size limitation | Ericsson | imported from 3GU |
R3‑194182 | gNB-CU-UP Graceful shutdown discussion | Ericsson | imported from 3GU |
R3‑194183 | gNB-CU-UP graceful shutdown notification CR | Ericsson | imported from 3GU |
R3‑194184 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT | imported from 3GU |
R3‑194185 | Completion of RAN UE ID | Ericsson | imported from 3GU |
R3‑194186 | RAN UE ID for NG | Ericsson | imported from 3GU |
R3‑194187 | RAN UE ID for X2 | Ericsson | imported from 3GU |
R3‑194188 | RAN UE ID for Xn | Ericsson | imported from 3GU |
R3‑194189 | Discussion on the need of signalling of SPID and ARPI over E1 | Ericsson | imported from 3GU |
R3‑194190 | PDU Session NAS-PDU in PDU Session Resource Release Command | Ericsson | imported from 3GU |
R3‑194191 | About the case necessary UE capabilities not being supported | Ericsson | imported from 3GU |
R3‑194192 | Support for setting up IPSec in F1 | Ericsson | imported from 3GU |
R3‑194193 | Support for setting IPSec in F1 | Ericsson | imported from 3GU |
R3‑194194 | Support for setting IPSec in E1 | Ericsson | imported from 3GU |
R3‑194195 | Support for setting IPSec in Xn | Ericsson | imported from 3GU |
R3‑194196 | Support for setting IPSec in X2 | Ericsson | imported from 3GU |
R3‑194197 | Support for setting IPSec | Ericsson | imported from 3GU |
R3‑194198 | Maximum Integrity Protected Data Rate over E1 | Ericsson | imported from 3GU |
R3‑194199 | Discussion on Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194200 | Default Paging DRX in IDLE Mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194201 | Discussion on DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194202 | Alignment with stage 2 on Expected UE behaviour | Motorola Mobility, Lenovo | imported from 3GU |
R3‑194203 | Correction for DRB to be Released | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194204 | Handling of UE Context Setup and UE Context Modification Requests | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194205 | Detection of the IP version mismatch in data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194206 | Detection of the IP version mismatch in data forwarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194207 | Discussion for the NPN impact in F1 interface | Samsung Electronics Co., Ltd | imported from 3GU |
R3‑194208 | Discussion of NPN access control | Qualcomm Incorporated | imported from 3GU |
R3‑194209 | Discussion on EN-DC Carrier Aggregation and Feature Set Selection | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194210 | Discussion on identities and common procedures for NPN | Qualcomm Incorporated | imported from 3GU |
R3‑194211 | Correction to EN-DC Carrier Aggregation | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194212 | UL Data Split | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194213 | Bearer type change to SN terminated MCG bearer cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194214 | Bearer identification and mapping to backhaul channels | Samsung Electronics GmbH | imported from 3GU |
R3‑194215 | Other-SI delivery from gNB-CU to gNB-DU | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194216 | On usage of Reconfiguration Complete Indicator | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194217 | Correction to DRB to Setup | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194218 | Correction to EN-DC TNL address discovery | Huawei | imported from 3GU |
R3‑194219 | On CellGroupConfig handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194220 | GTP-U Error cause for F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194221 | GTP-U Error cause for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194222 | Correction to SN Status Transfer considering PDCP version change | Google Inc. | imported from 3GU |
R3‑194223 | IP version mismatch cause F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194224 | Correction to SN Release procedures for LTE DC | Google Inc. | imported from 3GU |
R3‑194225 | Correction to SN Release procedures for EN-DC | Google Inc. | imported from 3GU |
R3‑194226 | Correction to SN Release procedure | Google Inc. | imported from 3GU |
R3‑194227 | IP version mismatch cause E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194228 | Correction to SN Modification Request in lower layer re-establishment | Google Inc. | imported from 3GU |
R3‑194229 | Discussion on IPsec Tunnel Pre-Establishment | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194230 | Correction to MR-DC with 5GC with RRC_INACTIVE | Google Inc. | imported from 3GU |
R3‑194231 | IPSec Pre-establishment F1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194232 | Clarification on SN Status Transfer | Google Inc. | imported from 3GU |
R3‑194233 | Correction to RRC Inactive transition | Google Inc. | imported from 3GU |
R3‑194234 | Correction to RRC Inactive transition | Google Inc. | imported from 3GU |
R3‑194235 | IPSec Pre-establishment E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194236 | IAB Indication to CN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194237 | Discussion on UE simultaneously connected to CU-UPs belonging to different security domains | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194238 | Introduction of Public Network Integrated NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194239 | Introduction of Stand-alone NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194240 | Introduction of Stand-alone NPN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194241 | E-UTRA-NR Cell-level Resource Coordination | Ericsson | imported from 3GU |
R3‑194242 | Mitigation of Unnecessary (Fast) Retransmissions in Split gNBs | Ericsson | imported from 3GU |
R3‑194243 | Transport Network Delay Compensation in Split gNB Architecture | Ericsson | imported from 3GU |
R3‑194244 | Draft LS on UE Connected to Multiple CU-UPs | Ericsson | imported from 3GU |
R3‑194245 | Location Reporting: effective PSCell ID reporting | VODAFONE | imported from 3GU |
R3‑194246 | Location Reporting: effective PSCell ID reporting | VODAFONE Group Plc | imported from 3GU |
R3‑194247 | (TP for NR_IAB BL CR for TS 38.473): Introduction of IAB-donor-DU indication IE in F1 SETUP REQUEST MESSAGE | ZTE, Sanechips | imported from 3GU |
R3‑194248 | (TP for NR_IAB BL CR for TS 38.423): Introduction of IAB-donor indication IE in XnAP MESSAGE | ZTE, Sanechips | imported from 3GU |
R3‑194249 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑194250 | LTE-M Indication | Ericsson | imported from 3GU |
R3‑194251 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194252 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194253 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
R3‑194254 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
R3‑194255 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
R3‑194256 | Discussion on correction over Iuant series 37 | Huawei | imported from 3GU |
R3‑194257 | Correction for Iuant | Huawei | imported from 3GU |
R3‑194258 | Correction for Iuant | Huawei | imported from 3GU |
R3‑194259 | Correction for Iuant | Huawei | imported from 3GU |
R3‑194260 | Discussion on DL-AoD procedure | Huawei | imported from 3GU |
R3‑194261 | LS on DL-AOD procedure | Huawei | imported from 3GU |
R3‑194262 | Discussion on Transmission Measurement Function | Huawei | imported from 3GU |
R3‑194263 | Overall architecture for positioning of gNB-CU-CP and gNB-CU-UP | Huawei | imported from 3GU |
R3‑194264 | Transmission Measurement Function in NG-RAN - BL-Update | Huawei | imported from 3GU |
R3‑194265 | Discussion on Multi-RTT procedure | Huawei | imported from 3GU |
R3‑194266 | Discussion on broadcast assistance data delivery | Huawei | imported from 3GU |
R3‑194267 | TP on assistance inforamtion for Positioning- BL Update | Huawei | imported from 3GU |
R3‑194268 | Positioning assistance information delivery | Huawei | imported from 3GU |
R3‑194269 | Positionning assistance information delivery | Huawei | imported from 3GU |
R3‑194270 | Discussion on F1 support for positioning | Huawei | imported from 3GU |
R3‑194271 | F1 support for positioning | Huawei | imported from 3GU |
R3‑194272 | F1 support for positioning | Huawei | imported from 3GU |
R3‑194273 | F1 support for positioning | Huawei | imported from 3GU |
R3‑194274 | Discussion on Local LMF | Huawei | imported from 3GU |
R3‑194275 | Discussion on RAN acting as LCS client | Huawei | imported from 3GU |
R3‑194276 | LTE-M Devices | Ericsson | imported from 3GU |
R3‑194277 | LTE-M Indication | Ericsson | imported from 3GU |
R3‑194278 | [Draft] LS on LTE-M identification in 5GC | Ericsson | imported from 3GU |
R3‑194279 | X2/Xn Signalling for Accessibility Measurement | Ericsson | imported from 3GU |
R3‑194280 | Information on RLF events in a split CU-DU architecture | Ericsson | imported from 3GU |
R3‑194281 | Handling of RLF in the gNB-DU | Ericsson | imported from 3GU |
R3‑194282 | Cell Quality Derivation Configuration Parameters Optimization | Ericsson | imported from 3GU |
R3‑194283 | RLM Wrong Beam Configuration Detection and Resolution | Ericsson | imported from 3GU |
R3‑194284 | On the Use Case of Beam Measurement upon Successful Handover | Ericsson | imported from 3GU |
R3‑194285 | On the Use Case of RLM Related Information upon a Successful Handover | Ericsson | imported from 3GU |
R3‑194286 | Limitation of cell-level load reporting in load balancing | Ericsson, NTT Docomo | imported from 3GU |
R3‑194287 | Per SSB load reporting for load balancing in NG RAN | Ericsson | imported from 3GU |
R3‑194288 | Discussion on potential issues related to SSB load calculation | Ericsson | imported from 3GU |
R3‑194289 | Load Balancing in DC scenarios | Ericsson | imported from 3GU |
R3‑194290 | Stage 2 description for Load Balancing solution | Ericsson, NTT Docomo | imported from 3GU |
R3‑194291 | On the use cases and required F1 signaling for RACH optimization at gNB-DU | Ericsson | imported from 3GU |
R3‑194292 | Solution for RACH Optimization in NG-RAN | Ericsson | imported from 3GU |
R3‑194293 | Intra and inter RAN nodes signaling for RACH optimization | Ericsson | imported from 3GU |
R3‑194294 | Stage 2 description for RACH Optimisation solution | Ericsson | imported from 3GU |
R3‑194295 | Discussion and Solution for Centralised PCI Selection | Ericsson | imported from 3GU |
R3‑194296 | Discussion and Solution for Distributed PCI Selection | Ericsson | imported from 3GU |
R3‑194297 | Discussion and solution on PCI Reconfiguration | Ericsson | imported from 3GU |
R3‑194298 | Overall MDT solution in NG-RAN | Ericsson | imported from 3GU |
R3‑194299 | Remaining issues on MDT activation and reporting in split RAN | Ericsson | imported from 3GU |
R3‑194300 | MDT activation and reporting in split RAN | Ericsson | imported from 3GU |
R3‑194301 | Further discussion on enhancement: the Intra eNB CP Relocation for NB-IoT | Ericsson | imported from 3GU |
R3‑194302 | Discussion on XnAP impacts for supporting UP CIoT Optimization | Ericsson | imported from 3GU |
R3‑194303 | (TP for Support of Enhanced Coverage restriction in NGAP for LTE-M UEs BL CR for TS 38.413): Removal of CE modeB restriction | Ericsson | imported from 3GU |
R3‑194304 | (TP for NR Mob BL CR for TS 38.423): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194305 | (TP for NR Mob BL CR for TS 38.420): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194306 | (TP for LTE_feMob BL CR for TS 36.423): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194307 | (TP for LTE_feMob BL CR for TS 36.420): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194308 | Up to Four RLC entities in the PDCP Duplication | Ericsson | imported from 3GU |
R3‑194309 | Effective PDCP Duplication | Ericsson | imported from 3GU |
R3‑194310 | Effective PDCP Duplication | Ericsson | imported from 3GU |
R3‑194311 | PDCP Discarding | Ericsson | imported from 3GU |
R3‑194312 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194313 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194314 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194315 | Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194316 | Solution #4 of Key Issue 1: two NG-U tunnels for the single PDU Session | Ericsson | imported from 3GU |
R3‑194317 | Solution #4 of Key Issue 1: two NG-U tunnels for the single PDU Session | Ericsson | imported from 3GU |
R3‑194318 | Provisioning of UE’s TSC traffic pattern related information | Ericsson | imported from 3GU |
R3‑194319 | (TP for NR_POS BL CR for TS 38.305): NR Assistance Data Delivery - Stage 2 | Ericsson | imported from 3GU |
R3‑194320 | Discussion on F1 signalling for support of NR V2X | Ericsson | imported from 3GU |
R3‑194321 | Resource coordination between NG-RAN nodes for NR V2X sidelink communication | Ericsson | imported from 3GU |
R3‑194322 | Support of MR-DC V2X SL coordination over X2 | Ericsson | imported from 3GU |
R3‑194323 | Discussion and Solution for inter node signalling of SFN offset | Ericsson | imported from 3GU |
R3‑194324 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194325 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194326 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194327 | (TP for NR_IAB BL CR for TS 38.401):Integration of IAB-node | Huawei | imported from 3GU |
R3‑194328 | (TP for NR_IAB BL CR for TS 38.401):OAM connectivity for the IAB node | Huawei | imported from 3GU |
R3‑194329 | (TP for NR_IAB BL CR for TS 38.413):IAB node indication to CN | Huawei | imported from 3GU |
R3‑194330 | (TP for NR_IAB BL CR for TS 36.413):IAB node indication to CN | Huawei | imported from 3GU |
R3‑194331 | Parent node selection | Huawei | imported from 3GU |
R3‑194332 | IP address management for IAB node | Huawei | imported from 3GU |
R3‑194333 | (TP for NR_IAB BL CR for TS 38.473): BH RLC channel management | Huawei | imported from 3GU |
R3‑194334 | Bearer mapping for control plane signalling | Huawei, LG Uplus | imported from 3GU |
R3‑194335 | DL bearer mapping in IAB-donor-DU | Huawei | imported from 3GU |
R3‑194336 | BAP layer configuration | Huawei | imported from 3GU |
R3‑194337 | Support of flow control for IAB Network | Huawei | imported from 3GU |
R3‑194338 | RAN3 impact analysis of IAB usage in NSA network | Huawei | imported from 3GU |
R3‑194339 | (TP for NR-IAB BL CR for TS 38.401) :NSA IAB Integration Procedure | Huawei | imported from 3GU |
R3‑194340 | Support of multiple connectivity in IAB network | Huawei | imported from 3GU |
R3‑194341 | Congestion reporting and handling for IAB networks | Huawei | imported from 3GU |
R3‑194342 | Resource coordination between multi-hop BH links | Huawei | imported from 3GU |
R3‑194343 | Routing in IAB network | Huawei | imported from 3GU |
R3‑194344 | Routing table design and configuration | Huawei | imported from 3GU |
R3‑194345 | (TP for NR_IAB BL CR for TS 38.401): Backhaul RLF Recovery | Huawei | imported from 3GU |
R3‑194346 | (TP for NR_IAB BL CR for TS 38.401): Intra IAB donor-CU topology adaptation procedure | Huawei | imported from 3GU |
R3‑194347 | Inter IAB donor CU topology adaptation | Huawei | imported from 3GU |
R3‑194348 | IAB bearer mapping for other traffic | Huawei | imported from 3GU |
R3‑194349 | QoS and Fairness enforcement in IAB networks | Huawei | imported from 3GU |
R3‑194350 | Discussion on control plane transmission in NSA (option c) | Huawei | imported from 3GU |
R3‑194351 | Next hop ID design for IAB routing | Huawei | imported from 3GU |
R3‑194352 | Routing and RLF handling for the IAB node connecting to multiple donor Dus | Huawei | imported from 3GU |
R3‑194353 | TNL association establishment of IAB node | Huawei | imported from 3GU |
R3‑194354 | Rapporteur cleanup of IE semantics descriptions | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194355 | Rapporteur corrections | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194356 | Consideration on CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC | LG Electronics | imported from 3GU |
R3‑194357 | Introduction of CP CIoT 5GS Optimisation for NB-IoT and MTC connected to 5GC (Stage 2) | LG Electronics | imported from 3GU |
R3‑194358 | Discussion on open issues for MT-EDT | LG Electronics | imported from 3GU |
R3‑194359 | (TP for MT_EDT BL CR for TS 36.423): Discussion on open issues for MT-EDT | LG Electronics | imported from 3GU |
R3‑194360 | Consideration on open issues for Solution #1 | LG Electronics | imported from 3GU |
R3‑194361 | Introduction of Redundant Sequence Number for Solution #1 (TS 38.413) | LG Electronics | imported from 3GU |
R3‑194362 | Introduction of Redundant Sequence Number for Solution #1 (TS 38.423) | LG Electronics | imported from 3GU |
R3‑194363 | Introduction of Redundant Sequence Number for Solution #1 (TS 38.463) | LG Electronics | imported from 3GU |
R3‑194364 | Correction about gNB-CU System Information IE | Ericsson | imported from 3GU |
R3‑194365 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194366 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194367 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194368 | Independent migration to IPv6 on S1-U for en-gNB’s | Ericsson, Deutsche Telekom | imported from 3GU |
R3‑194369 | Independent migration to IPv6 on S1-U for en-gNB’s | Ericsson, Deutsche Telekom | imported from 3GU |
R3‑194370 | Buffered PDCP throughput measurement computation | Ericsson | imported from 3GU |
R3‑194371 | Draft LS on the feasibility of buffered PDCP throughput computation | Ericsson | imported from 3GU |
R3‑194372 | Minimisation of Glitches in Data Transmission | Ericsson | imported from 3GU |
R3‑194373 | (TP for LTE_feMob BL CR for TS 36.300): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194374 | (TP for LTE_feMob BL CR for TS 36.423): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194375 | Comparison of solutions for reduction of interruption time at HO | Ericsson | imported from 3GU |
R3‑194376 | (TP for LTE_feMob BL CR for TS 36.300): Conditional Handover - Data Forwarding | Ericsson | imported from 3GU |
R3‑194377 | (TP for LTE_feMob BL CR for TS 36.423): Conditional Handover - Data Forwarding | Ericsson | imported from 3GU |
R3‑194378 | (TP for NR_Mob BL CR for TS 38.300): Conditional Handover - Data Forwarding | Ericsson | imported from 3GU |
R3‑194379 | (TP for NR_Mob BL CR for TS 38.423): Conditional Handover - Data Forwarding | Ericsson | imported from 3GU |
R3‑194380 | (TP for LTE_feMob BL CR for TS 36.300): Enhanced Make-Before-Break - Data Forwarding | Ericsson | imported from 3GU |
R3‑194381 | (TP for LTE_feMob BL CR for TS 36.423): Enhanced Make-Before-Break - Data Forwarding | Ericsson | imported from 3GU |
R3‑194382 | Support of NPN on NG and Xn interface | Ericsson | imported from 3GU |
R3‑194383 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194384 | XN Setup message size limitation | Ericsson | imported from 3GU |
R3‑194385 | QoS Upgrading and V2x handover aspects related to incoming LS in S2-1908627 on V2X Uu QoS | VODAFONE | imported from 3GU |
R3‑194386 | Correction on DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
R3‑194387 | Additional Corrections on QoS flow re-mapping before handover | Ericsson | imported from 3GU |
R3‑194388 | Correction of QoS flow re-mapping before handover | Ericsson | imported from 3GU |
R3‑194389 | Data forwarding and QoS flow remapping | Ericsson | imported from 3GU |
R3‑194390 | DRB ID co-ordination between MN and SN | Ericsson | imported from 3GU |
R3‑194391 | Corrections regarding mandatory statements in Semantics Descriptions | Ericsson | imported from 3GU |
R3‑194392 | LS on enhanced Make-Before-Break data forwarding | Ericsson | imported from 3GU |
R3‑194393 | Discussion on Direct Data Forwarding | Ericsson | imported from 3GU |
R3‑194394 | RAN3-105 meeting Agenda | Chairman (Ericsson) | imported from 3GU |
R3‑194395 | Considerations on the use case and issues for resource coordination | LG Electronics | imported from 3GU |
R3‑194396 | Work Plan for study on local NR positioning in NG-RAN | CMCC | imported from 3GU |
R3‑194397 | Discussion on supporting Local LMF in NG-RAN | CMCC | imported from 3GU |
R3‑194398 | Work plan for SON and MDT WI | CMCC | imported from 3GU |
R3‑194399 | 38.300 BLCR for introducing NR SON features | CMCC,Huawei | imported from 3GU |
R3‑194400 | MDT configuration and reporting for CU-DU split architecture | CMCC | imported from 3GU |
R3‑194401 | LS on support of Remote Interference Management | CMCC | imported from 3GU |
R3‑194402 | BLCR for TS 38.413 for support of SON on NGAP | CMCC, Huawei | imported from 3GU |
R3‑194403 | BL CR for TS 38.423 for support of SON on XnAP | CMCC, Huawei | imported from 3GU |
R3‑194404 | TP to 38.300 on support of RACH optimization | CMCC | imported from 3GU |
R3‑194405 | Mobility load balancing | CMCC | imported from 3GU |
R3‑194406 | TP to 38.300 on support of MLB | CMCC | imported from 3GU |
R3‑194407 | PDCP duplication with more than 2 legs | CMCC | imported from 3GU |
R3‑194408 | Public network integrated NPNs | CMCC | imported from 3GU |
R3‑194409 | Discussion on load information | CMCC | imported from 3GU |
R3‑194410 | Maximum Integrity Protected Data Rate over E1 | Ericsson | imported from 3GU |
R3‑194411 | RAN sharing and emergency services for NPN | Huawei, China Telecom | imported from 3GU |
R3‑194412 | General support of standalone NPN | Huawei | imported from 3GU |
R3‑194413 | General support of public network integrated NPN | Huawei, LGU+ | imported from 3GU |
R3‑194414 | Discussion on Paging for NPN | Huawei | imported from 3GU |
R3‑194415 | CR to TS 38.423 on support of NPN | Huawei | imported from 3GU |
R3‑194416 | CR to TS 38.413 on support of NPN | Huawei | imported from 3GU |
R3‑194417 | CR to TS 38.300 on support of NPN | Huawei | imported from 3GU |
R3‑194418 | CR to TS 36.300 on support of NPN | Huawei | imported from 3GU |
R3‑194419 | Handover for public network integrated NPN | Huawei | imported from 3GU |
R3‑194420 | Handover within SNPN and Interworking between SNPN and PLMN | Huawei | imported from 3GU |
R3‑194421 | Connection management between PLMN and SNPN | Huawei | imported from 3GU |
R3‑194422 | LS on connection management between PLMN and SNPN | Huawei | imported from 3GU |
R3‑194423 | Discussion on Spcell/Scell management via UE Context Management procedures | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194424 | Discussion on the handling of RRC information for W1 | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194425 | pCR to 37.470 on W1AP functions | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194426 | pCR for 37.473 on UE context management procedures | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194427 | pCR for 37.473 on Interface Management procedures | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194428 | Structure pCR for TS 37.473 | Huawei, China Unicom, TIM | imported from 3GU |
R3‑194429 | Discussion on LTE non-split bearer solution | Huawei | imported from 3GU |
R3‑194430 | CR to 38.401 on MDT | Huawei | imported from 3GU |
R3‑194431 | CR to 38.423 on MDT | Huawei | imported from 3GU |
R3‑194432 | Support of delta configuration in EN-DC | Huawei | imported from 3GU |
R3‑194433 | Support of delta configuration in MR-DC | Huawei | imported from 3GU |
R3‑194434 | Clarification on rejection for the SN terminated bearer | Huawei | imported from 3GU |
R3‑194435 | Correction on the rejection for the SN terminated bearer | Huawei | imported from 3GU |
R3‑194436 | Clarification on the usage of Offered GBR QoS Flow Information IE | Huawei | imported from 3GU |
R3‑194437 | Support of delta configuration during the SN release procedure | Huawei | imported from 3GU |
R3‑194438 | Bearer type change without anchor change | Huawei | imported from 3GU |
R3‑194439 | Clarification on bearer type change without anchor change | Huawei | imported from 3GU |
R3‑194440 | Considerations on the triggering of SN modification procedure | Huawei | imported from 3GU |
R3‑194441 | Introduction of SgNB Modification Trigger Indication | Huawei | imported from 3GU |
R3‑194442 | Introduction of S-Node Modification Trigger Indication | Huawei | imported from 3GU |
R3‑194443 | Default DRB coordination in MR-DC with 5GC | Huawei, OPPO, CATT | imported from 3GU |
R3‑194444 | Support of default DRB coordination in MR-DC with 5GC | Huawei, OPPO, CATT | imported from 3GU |
R3‑194445 | Support of default DRB coordination in MR-DC with 5GC | Huawei, OPPO, CATT | imported from 3GU |
R3‑194446 | PDCP PDUs delivered over Uu interface out of sequence | Huawei | imported from 3GU |
R3‑194447 | Introduction of successfully delivered PDCP SN ranges | Huawei | imported from 3GU |
R3‑194448 | Considerations on retransmitted PDCP PDUs issue | Huawei | imported from 3GU |
R3‑194449 | Introduction of successfully delivered retransmitted PDCP SN ranges | Huawei | imported from 3GU |
R3‑194450 | Considerations on UP located in different security domains | Huawei | imported from 3GU |
R3‑194451 | [DRAFT] LS on UP located in different security domains | Huawei | imported from 3GU |
R3‑194452 | Support of V2X authorization and sidelink AMBR | Huawei | imported from 3GU |
R3‑194453 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194454 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194455 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194456 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194457 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194458 | V2X configuration exchange between RAN nodes | Huawei | imported from 3GU |
R3‑194459 | Introduction of V2X configuration exchange | Huawei | imported from 3GU |
R3‑194460 | Introduction of V2X configuration exchange | Huawei | imported from 3GU |
R3‑194461 | Introduction of V2X configuration exchange | Huawei | imported from 3GU |
R3‑194462 | Principles for resource pool assignment for V2X over F1 | Huawei | imported from 3GU |
R3‑194463 | Resource coordination between NG-RAN nodes for NR V2X | Huawei | imported from 3GU |
R3‑194464 | Support of multi-QoS profiles for V2X | Huawei | imported from 3GU |
R3‑194465 | Support of alternative QoS profiles | Huawei | imported from 3GU |
R3‑194466 | Support of alternative QoS profiles | Huawei | imported from 3GU |
R3‑194467 | [Draft] Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Huawei | imported from 3GU |
R3‑194468 | Discussion on handover case for V2X QoS | Huawei | imported from 3GU |
R3‑194469 | Support of handover for V2X QoS | Huawei | imported from 3GU |
R3‑194470 | TP to TR 37.985 on LTE V2X | Huawei, LG Electronics | imported from 3GU |
R3‑194471 | NG-U delay measurement for QoS monitoring | Huawei | imported from 3GU |
R3‑194472 | Support of per UE per QoS Flow level QoS Monitoring | Huawei | imported from 3GU |
R3‑194473 | Support the indirect Inter-RAT SRVCC handover procedure | Huawei, China Unicom | imported from 3GU |
R3‑194474 | Support of SRVCC from 5G to 3G | Huawei, China Unicom | imported from 3GU |
R3‑194475 | [Draft] LS on NAS Security Parameters for SRVCC from 5G to 3G | Huawei | imported from 3GU |
R3‑194476 | Skeleton of TR 38.856 v0.0.0 | CMCC | imported from 3GU |
R3‑194477 | Further thinking of SIB9 handling | Huawei | imported from 3GU |
R3‑194478 | CR to 38.462 on the introduction of PPID for DTLS over SCTP | Huawei | imported from 3GU |
R3‑194479 | Discussion on support for setting up IPSec over F1 and E1 | Huawei | imported from 3GU |
R3‑194480 | CR to 38.473 on Support for setting up IPSec tunnel for GTP traffic over F1 | Huawei | imported from 3GU |
R3‑194481 | CR to 38.473 on Support for setting up IPSec tunnel for GTP traffic over E1 | Huawei | imported from 3GU |
R3‑194482 | CR to 38.413 on clarifications to SON configuration transfer | Huawei | imported from 3GU |
R3‑194483 | CR to 38.473 on PDCCH Blind Detection Coordination in NR-DC | Huawei | imported from 3GU |
R3‑194484 | CR to 38.473 on Power Coordination in NE-DC | Huawei | imported from 3GU |
R3‑194485 | General support of NPN over F1 | Huawei, China Telecom | imported from 3GU |
R3‑194486 | CR to 38.473 on support of NPN over F1 | Huawei, China Telecom | imported from 3GU |
R3‑194487 | CR to 38.470 on support of NPN over F1 | Huawei, China Telecom | imported from 3GU |
R3‑194488 | General support of NPN over E1 | Huawei, China Telecom | imported from 3GU |
R3‑194489 | CR to 38.463 on support of NPN over E1 | Huawei, China Telecom | imported from 3GU |
R3‑194490 | CR to 38.460 on on support of NPN over E1 | Huawei, China Telecom | imported from 3GU |
R3‑194491 | Discussion on the human-readable name of NPN for disaggregated gNB | Huawei | imported from 3GU |
R3‑194492 | CR to 38.473 on transfering systemInformationAreaID and areaScope over F1 | Huawei | imported from 3GU |
R3‑194493 | CR to 38.473 inactivity monitoring stop indication over F1 | Huawei | imported from 3GU |
R3‑194494 | CR to 38.463 inactivity monitoring stop indication over E1 | Huawei | imported from 3GU |
R3‑194495 | On the introduction of DL UP parameters during E1 Bearer Setup | Huawei, Vodafone | imported from 3GU |
R3‑194496 | CR to 38.463 on the introduction of DL UP parameters during E1 Bearer Setup | Huawei, Vodafone | imported from 3GU |
R3‑194497 | CR to 38.401 on the introduction of DL UP parameters during E1 Bearer Setup | Huawei, Vodafone | imported from 3GU |
R3‑194498 | CR to 38.473 on MeasGapSharingConfig | Huawei | imported from 3GU |
R3‑194499 | Discussion on W1-U stage 2 functions description | China Unicom | imported from 3GU |
R3‑194500 | pCR to 37.470 on W1 general aspects and principles | China Unicom | imported from 3GU |
R3‑194501 | Discussion on W1 signalling transport | China Unicom | imported from 3GU |
R3‑194502 | pCR to 37.472 on W1 signalling transport | China Unicom | imported from 3GU |
R3‑194503 | Discussion on the application of Network Coding for efficient PDCP Duplication with more than 2 copies | China Unicom | imported from 3GU |
R3‑194504 | RLF Info Discussion | Qualcomm CDMA Technologies | imported from 3GU |
R3‑194505 | RACH Optimization Enhancement for NR | China Telecommunications | imported from 3GU |
R3‑194506 | RACH Optimization Enhancement for NR | China Telecommunications | imported from 3GU |
R3‑194507 | CR to 38.463 on Maximum Integrity Protected Data Rate IE in Security Indication over E1 interface | Huawei | imported from 3GU |
R3‑194508 | CR to 38.413 on Maximum Integrity Protected Data Rate IE in Security Indication over NG interface | Huawei | imported from 3GU |
R3‑194509 | Clarification on Header Compression | Huawei | imported from 3GU |
R3‑194510 | Support of inter-system HO from SA to EN-DC in Rel-16 | China Telecommunications | imported from 3GU |
R3‑194511 | IAB Flow Control for DL | Intel Corporation | imported from 3GU |
R3‑194512 | IAB Flow Control for UL | Intel Corporation | imported from 3GU |
R3‑194513 | IAB lossless delivery of UL data with hop-by-hop ARQ | Intel Corporation | imported from 3GU |
R3‑194514 | (TP for LTE_feMob BL CR for TS 36.300): Downlink Data Forwarding for Simultaneous Connectivity phase | Intel Corporation | imported from 3GU |
R3‑194515 | Removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
R3‑194516 | CR to 38.473 on clarifcations for inactivity monitoring request | Huawei | imported from 3GU |
R3‑194517 | Cause value for “Multiple DRB ID Instances” and “Unknown DRB ID” | Huawei | imported from 3GU |
R3‑194518 | Discussion on Delta RRC configuration support in gNB-CU | Huawei | imported from 3GU |
R3‑194519 | CR to 38473 on Delta RRC config support in gNB-CU | Huawei | imported from 3GU |
R3‑194520 | CR to 38.463 on Security Indication | Huawei | imported from 3GU |
R3‑194521 | CR to 38.423 for Supporting PRACH Configuration exchange | China Telecommunications | imported from 3GU |
R3‑194522 | CR to 36.423 for Supporting PRACH Configuration exchange in EN-DC | China Telecommunications | imported from 3GU |
R3‑194523 | CR to 36.423 for Supporting PRACH Configuration exchange in EN-DC | China Telecommunications | imported from 3GU |
R3‑194524 | Response to R3-194375 | Huawei | imported from 3GU |
R3‑194525 | Response to R3-194394 | CATT | imported from 3GU |
R3‑194526 | Response to R3-194142 and R3-194143 | Google Inc. | imported from 3GU |
R3‑194527 | Response to R3-193956, R3-193979, R3-193980, R3-193985, R3-194332 and R3-193563: IAB IP address assignment | Ericsson Japan K.K. | imported from 3GU |
R3‑194528 | Response to R3-193540 | Nokia Japan | imported from 3GU |
R3‑194529 | Response to R3-193377 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194530 | RAN3-104Bis meeting report | ETSI MCC | imported from 3GU |
R3‑194531 | Skeleton TR for Study on Enhancement for Disaggregated gNB | China Telecommunications | imported from 3GU |
R3‑194532 | Addition of PPID for DTLS over SCTP for 38.472 | InterDigital | imported from 3GU |
R3‑194533 | CR on PPID value for DTLS over SCTP | NTT DOCOMO, INC. | imported from 3GU |
R3‑194534 | CR on PPID value for DTLS over SCTP | NTT DOCOMO, INC. | imported from 3GU |
R3‑194535 | CR to 38.462 on the introduction of PPID for DTLS over SCTP | Huawei | imported from 3GU |
R3‑194536 | Support of multi-QoS profiles for V2X | Huawei, Orange | imported from 3GU |
R3‑194537 | Support of alternative QoS profiles | Huawei | imported from 3GU |
R3‑194538 | Support of alternative QoS profiles | Huawei | imported from 3GU |
R3‑194539 | Way forward on LTE HLS for E-UTRAN | NTT DOCOMO, INC, Vodafone, Verizon Wireless, Ericsson, TIM, Orange | imported from 3GU |
R3‑194540 | Limitation of cell-level load reporting in load balancing | Ericsson, NTT Docomo, Verizon Wireless | imported from 3GU |
R3‑194541 | Per SSB load reporting for load balancing in NG RAN | Ericsson, Verizon Wireless | imported from 3GU |
R3‑194542 | Discussion on potential issues related to SSB load calculation | Ericsson, Verizon Wireless | imported from 3GU |
R3‑194543 | Overall MDT solution in NG-RAN | Ericsson | imported from 3GU |
R3‑194544 | Draft LS on the feasibility of buffered PDCP throughput computation | Ericsson | imported from 3GU |
R3‑194545 | Discussion on the need of signalling of SPID and ARPI over E1 | Ericsson, Orange | imported from 3GU |
R3‑194546 | Summary of offline discussion on LTE-M | Qualcomm | imported from 3GU |
R3‑194547 | Discussion on PRACH coordination | CATT | imported from 3GU |
R3‑194548 | Support of default DRB coordination in MR-DC with 5GC | Huawei, OPPO, CATT, ZTE, Ericsson | imported from 3GU |
R3‑194549 | [DRAFT] Reply LS on User Data Congestion Analytics | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194550 | Reply on radio resource management policy | Huawei | imported from 3GU |
R3‑194551 | Temporary Identifier usage at interworking | Ericsson | imported from 3GU |
R3‑194552 | The GUAMI and GUMMEI usage for EPS/5GS interworking | Huawei | imported from 3GU |
R3‑194553 | Reply LS on LS on maximum value of MDBV | Qualcomm Incorporated | imported from 3GU |
R3‑194554 | CR 38.463 IPv6 Flow Label Signalling and Allocation in IAB Networks | Ericsson | imported from 3GU |
R3‑194555 | CR to 38.413 for signalling design for RIM | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194556 | Correction of secured signaling connection | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑194557 | Correction of secured signaling connection | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑194558 | CR to 38.413 for signalling design for RIM | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194559 | LS on support of Remote Interference Management | CMCC | imported from 3GU |
R3‑194560 | Discussion on Spcell/Scell management via UE Context Management procedures | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194561 | Discussion on the handling of RRC information for W1 | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194562 | pCR to 37.470 on W1AP functions | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194563 | pCR for 37.473 on UE context management procedures | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194564 | pCR for 37.473 on Interface Management procedures | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194565 | Structure pCR for TS 37.473 | Huawei, China Unicom, TIM, Orange | imported from 3GU |
R3‑194566 | Location Reporting: effective PSCell ID reporting | VODAFONE Group Plc | imported from 3GU |
R3‑194567 | Enabling additional PSCell reporting and time since EN-DC was deconfigured | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194568 | Correction of handling of the Location Information at the MeNB | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194569 | Enabling additional PSCell reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194570 | Correction of handling of the Location Information at the MN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194571 | (Draft LS) Reply LS on Reporting all Cell IDs in 5G | Vodafone | imported from 3GU |
R3‑194572 | Reply LS on Data activity reporting | Ericsson | imported from 3GU |
R3‑194573 | Summary of offline discussion on Independent migration to IPv6 on S1-U for en-gNB’s | Ericsson | imported from 3GU |
R3‑194574 | Independent migration to IPv6 on S1-U for en-gNB’s | Ericsson, Deutsche Telekom | imported from 3GU |
R3‑194575 | Non IP bearer support for Dual Connectivity | Huawei, Vodafone | imported from 3GU |
R3‑194576 | Correction of E-RAB Modification Indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194577 | S1AP Introduction of New Indicator for EPS Fallback | ZTE, NOKIA, NOKIA Shanghai Bell, Ericsson | imported from 3GU |
R3‑194578 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑194579 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑194580 | Correction on Handover Request Acknowledge | Huawei | imported from 3GU |
R3‑194581 | Summary of offline discussion on S1AP Error Indication | Ericsson | imported from 3GU |
R3‑194582 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
R3‑194583 | ERROR INDICATION Message in S1AP | Ericsson | imported from 3GU |
R3‑194584 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑194585 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑194586 | Summary of offline discussion on inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑194587 | Rapporteur cleanup of IE semantics descriptions | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194588 | Corrections regarding mandatory statements in Semantics Descriptions | Ericsson | imported from 3GU |
R3‑194589 | Rapporteur update - clarification of semantics | Huawei | imported from 3GU |
R3‑194590 | Correction of semantic descriptions in TS 38.463 (rapporteur) | Ericsson | imported from 3GU |
R3‑194591 | Rapporteur's corrections for TS 38.423 | Ericsson | imported from 3GU |
R3‑194592 | TS37.340 Rapporteur Cleanups | ZTE | imported from 3GU |
R3‑194593 | CR for addressing Race condition between X2 and S1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑194594 | Summary of offline discussion on DL UP parameters during E1 Bearer Setup | Huawei | imported from 3GU |
R3‑194595 | Correction of secured signalling connection | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑194596 | Summary of offline discussion on secured signaling connection | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑194597 | Summary of the offline discussion on the availability of NG-C TNL association | CATT | imported from 3GU |
R3‑194598 | Summary of discussions on use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194599 | Correction to EN-DC TNL address discovery | Huawei | imported from 3GU |
R3‑194600 | Clarification for TNLA removal | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194601 | Clarification for TNLA removal | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194602 | Removal of multiple SCTP associations | Intel Corporation | imported from 3GU |
R3‑194603 | Update on TNL Address discovery for EN-DC for TS36.300 | ZTE Corporation | imported from 3GU |
R3‑194604 | Update of TNL Address discovery for EN-DC (using new container) for TS36.413 | ZTE Corporation | imported from 3GU |
R3‑194605 | Summary of offline discussion on EN-DC TNL Address Discovery | ZTE | imported from 3GU |
R3‑194606 | PDU Session fail in Path Switch Request procedure | NEC | imported from 3GU |
R3‑194607 | XnAP Corrections of Activity Notification Usage | ZTE | imported from 3GU |
R3‑194608 | Critical correction to the presence of the SgNB UE X2AP ID in the SgNB Release Request Reject | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194609 | CR38.423 for Correction on RRC configuration indication | ZTE | imported from 3GU |
R3‑194610 | Introduction of SgNB Modification Trigger Indication | Huawei | imported from 3GU |
R3‑194611 | Introduction of S-Node Modification Trigger Indication | Huawei | imported from 3GU |
R3‑194612 | Discussion on supporting Local LMF in NG-RAN | CMCC | imported from 3GU |
R3‑194613 | Feature Set and Band Combination: Summary of offline discussion | Nokia | imported from 3GU |
R3‑194614 | CR on MR-DC low layer coordination with an MgNB-DU | CATT | imported from 3GU |
R3‑194615 | Summary of the offline discussion on MR-DC low layer coordination | CATT | imported from 3GU |
R3‑194616 | Support of Ethernet Type Bearer | Huawei, Vodafone | imported from 3GU |
R3‑194617 | Support of Ethernet Type Bearer | Huawei, Vodafone | imported from 3GU |
R3‑194618 | Summary of offline discussion on Ethernet Type Bearer Support | Huawei | imported from 3GU |
R3‑194619 | Summary of Discussion on number of served cells in Xn/X2 Setup | Ericsson | imported from 3GU |
R3‑194620 | EN-DC X2 Setup message size limitation | Ericsson | imported from 3GU |
R3‑194621 | XN Setup message size limitation | Ericsson | imported from 3GU |
R3‑194622 | Summary of discussion and Solution for inter node signalling of SFN offset | Ericsson | imported from 3GU |
R3‑194623 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194624 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194625 | Introduction of SFN Offset per NR cell | Ericsson | imported from 3GU |
R3‑194626 | Summary of Offline discussion on CSI-RS Configuration Transfer | China Telecom | imported from 3GU |
R3‑194627 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194628 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194629 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194630 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194631 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194632 | Summary of offline discussion on ARPI E1 | Ericsson | imported from 3GU |
R3‑194633 | Stage2 Introductions of Some MR-DC New Features (e.g. ARPI) | ZTE | imported from 3GU |
R3‑194634 | (TP for LTE_feMob BL CR for TS 36.300): PDCP SN Continuity for NR RLC-UM (Stage 2 CR NR) | Qualcomm Incorporated | imported from 3GU |
R3‑194635 | (TP for LTE_feMob BL CR for TS 38.300): PDCP SN Continuity for NR RLC-UM (Stage 2 CR LTE) | Qualcomm Incorporated | imported from 3GU |
R3‑194636 | eMBB HO preparation - Summary of offline discussion | Ericsson | imported from 3GU |
R3‑194637 | (TP for LTE_feMob BL CR for TS 36.300): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194638 | (TP for LTE_feMob BL CR for TS 36.423): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194639 | Summary of the offline on CHO enhancements | Nokia | imported from 3GU |
R3‑194640 | (TP for NR_Mob_enh BL CR for TS 36.423): Discussion on the FFSes for CHO | Huawei | imported from 3GU |
R3‑194641 | (TP for NR_Mob_enh BL CR for TS 38.423): Enabling efficient RRC reconfiguration and CHO cancel | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194642 | CHO Cancellation - Summary of offline discussion | Ericsson | imported from 3GU |
R3‑194643 | (TP for NR Mob BL CR for TS 38.423): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194644 | (TP for LTE_feMob BL CR for TS 36.423): Conditional Handover - HO modification | Ericsson | imported from 3GU |
R3‑194645 | Summary of the offline on the overload risk in case of CHO | Nokia | imported from 3GU |
R3‑194646 | Offline Summary of Applicability of CHO in MR-DC SN Change Scenario | ZTE | imported from 3GU |
R3‑194647 | eMBB HO preparation - Summary of offline discussion | Ericsson | imported from 3GU |
R3‑194648 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194649 | TSCAI and CN PDB: Summary of offline discussion | nokia | imported from 3GU |
R3‑194650 | Introducing NGAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑194651 | Correction on source TNL ADDRESS in NG-C interface-Solution 1 | CATT | imported from 3GU |
R3‑194652 | MTC/IoT WI Report | Vice-Chair (ZTE) | imported from 3GU |
R3‑194653 | NR SON/MDT WI Report | Vice-Chair (Intel) | imported from 3GU |
R3‑194654 | NR Industrial IoT WI Report | Vice-Chair (ZTE) | imported from 3GU |
R3‑194655 | 5G to 3G SRVCC WI Report | Vice-Chair (ZTE) | imported from 3GU |
R3‑194656 | 5G V2X WI Report | Vice-Chair (Intel) | imported from 3GU |
R3‑194657 | Disaggregated gNB Architecture SI Report | Vice-Chair (Intel) | imported from 3GU |
R3‑194658 | Summary of Offline discussion on accurate reference time provision | ZTE | imported from 3GU |
R3‑194659 | CR38473 for Providing accurate reference time Information from gNB-DU to gNB-CU | ZTE | imported from 3GU |
R3‑194660 | CR to 38.300 on NRIIOT Higher Layer Multi-Connectivity | CATT, Ericsson, Samsung, Huawei, ZTE, Nokia | imported from 3GU |
R3‑194661 | Summary of offline discussion on Stage 3 for Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194662 | Summary of offline discussion on handover failure cause | CATT | imported from 3GU |
R3‑194663 | Correction of DSCP Derivation | Huawei | imported from 3GU |
R3‑194664 | Correction of NAS transparent container | Huawei | imported from 3GU |
R3‑194665 | Summary of offline discussion on NAS transparent container | Huawei | imported from 3GU |
R3‑194666 | Trace function Support over F1 Interface for TS38.470 | ZTE, China Unicom, Ericsson, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑194667 | Adding Trace Messages in F1AP | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑194668 | Trace function Support over E1 Interface for TS38.460 | ZTE, China Unicom, Ericsson, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑194669 | Supporting Trace activation/Deactivation in E1AP | Ericsson, ZTE, China Unicom, CMCC, China Telecom, Altiostar Networks | imported from 3GU |
R3‑194670 | Correction of N3IWF key | Huawei | imported from 3GU |
R3‑194671 | Summary of offline discussion on PWS correction | Samsung | imported from 3GU |
R3‑194672 | Summary of offline discussion on clarification on the handling of CG-ConfigInfo over F1 | Ericsson | imported from 3GU |
R3‑194673 | NGAP correction of Initial Context Setup procedure text | Ericsson | imported from 3GU |
R3‑194674 | GTP TNLA for SON - Summary of offline discussion | Ericsson | imported from 3GU |
R3‑194675 | Default Paging DRX - Summary of offline discussion | Nokia | imported from 3GU |
R3‑194676 | pCR to 37.470 on W1 general aspects and principles | China Unicom | imported from 3GU |
R3‑194677 | Summary of offline discussion - SoD on CP-UP separation for LTE HLS | NTT Docomo | imported from 3GU |
R3‑194678 | pCR to 37.472 on W1 signalling transport | China Unicom | imported from 3GU |
R3‑194679 | Summary of offline discussion on W1 RRC handling | Huawei | imported from 3GU |
R3‑194680 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194681 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194682 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194683 | Use of SCTP ports for multiple TNLA | Ericsson | imported from 3GU |
R3‑194684 | [Draft] Reply LS on RAN sharing and Emergency services with Non-Public Networks | Qualcomm Incorporated | imported from 3GU |
R3‑194685 | Summary of offline discussion on Emergency and RAN sharing scenarios | Qualcomm | imported from 3GU |
R3‑194686 | Way Forward with private networks - Summary of offline discussion | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194687 | Correction of NB-IoT TDD Cell Frequency info | Huawei | imported from 3GU |
R3‑194688 | BL CR to 36.423: Support for IAB | Samsung | imported from 3GU |
R3‑194689 | (TP for NR_IAB BL CR for TS38.401) Discussion on IAB node integration procedure | Samsung | imported from 3GU |
R3‑194690 | LS out on IAB node integration procedure | Qualcomm | imported from 3GU |
R3‑194691 | (TP for NR_IAB BL CR for TS38.401) IAB OAM | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194692 | (TP for NR_IAB BL CR for TS 38.473): BH RLC channel management | Huawei | imported from 3GU |
R3‑194693 | BL CR to 38.300: Support for IAB | Ericsson | imported from 3GU |
R3‑194694 | Summary of offline discussion on intra-donor_mapping | Qualcomm | imported from 3GU |
R3‑194695 | 38.300 BLCR for introducing NR SON features | CMCC,Huawei | imported from 3GU |
R3‑194696 | BLCR for TS 38.413 for support of SON on NGAP | Huawei | imported from 3GU |
R3‑194697 | BLCR for TS 36.413 for support of SON on NGAP | Huawei | imported from 3GU |
R3‑194698 | BLCR for TS 38.423 for support of SON on NGAP | Samsung | imported from 3GU |
R3‑194699 | Summary of discussions on per SSB load reporting for load balancing in NG RAN | Ericsson | imported from 3GU |
R3‑194700 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | Ericsson | imported from 3GU |
R3‑194701 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑194702 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | Nokia | imported from 3GU |
R3‑194703 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | CATT | imported from 3GU |
R3‑194704 | Summary of offline discussion on CB: # SON_MDT_CB_9 | Huawei | imported from 3GU |
R3‑194705 | Reroute NSSF provided information for TS38.413 | ZTE, Interdigital, NOKIA, NOKIA Shanghai Bell | imported from 3GU |
R3‑194706 | Summary of discussions on support for setting up IPSec in F1. | Ericsson | imported from 3GU |
R3‑194707 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT | imported from 3GU |
R3‑194708 | E1 Setup Request for virtualized CU-UPs | Ericsson, Deutsche Telekom, Vodafone, BT | imported from 3GU |
R3‑194709 | (TP for NR_pos BL CR for TS 38.305): Transmission Measurement Function in NG-RAN | Qualcomm Incorporated | imported from 3GU |
R3‑194710 | Summary of offline Discussion on Broadcast Assistance Data Delivery | Huawei | imported from 3GU |
R3‑194711 | Summary of offline discussion on F1AP measurement support | Ericsson | imported from 3GU |
R3‑194712 | GTP Transport Layer Addresses for SON Configuration Transfer | Ericsson | imported from 3GU |
R3‑194713 | Summary of offline discussion on local LMF support for NG-RAN | CMCC | imported from 3GU |
R3‑194714 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑194715 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑194716 | [Draft] LS on NAS Security Parameters for SRVCC from 5G to 3G | Huawei | imported from 3GU |
R3‑194717 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194718 | Support of SRVCC from 5G to 3G | Huawei, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, ZTE | imported from 3GU |
R3‑194719 | Support SRVCC from 5G to 3G | Ericsson | imported from 3GU |
R3‑194720 | Alignment with stage 2 on Expected UE behaviour | Motorola Mobility, Lenovo | imported from 3GU |
R3‑194721 | CR to 38.463 on Security Indication | Huawei | imported from 3GU |
R3‑194722 | CR to 38.423 for Supporting PRACH Configuration exchange | China Telecommunications | imported from 3GU |
R3‑194723 | CR to 36.423 for Supporting PRACH Configuration exchange in EN-DC | China Telecommunications | imported from 3GU |
R3‑194724 | Summary of Offline discussion on DL data size in S1 paging | Ericsson | imported from 3GU |
R3‑194725 | Introduction of NB-IoT Paging and eDRX aspects | Ericsson | imported from 3GU |
R3‑194726 | Introduction of suspend resume for 5GC | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑194727 | Introduction of NB-IoT related NG-AP procedures | Huawei | imported from 3GU |
R3‑194728 | Introduction of CP UP NB-IoT Others | Huawei | imported from 3GU |
R3‑194729 | Reply LS on UAC for NB-IoT | 3GPP SA1 | imported from 3GU |
R3‑194730 | Reply LS from ETSI TC LI to SA5 on 5G Cell ID(s) in the 3GPP SA5 billing system | 3GPP SA5 | imported from 3GU |
R3‑194731 | LS reply from 3GPP SA5 to RAN1 and RAN3 on OAM requirements for RIM | 3GPP SA5 | imported from 3GU |
R3‑194732 | Reply LS on User Data Congestion Analytics | 3GPP SA5 | imported from 3GU |
R3‑194733 | LS on System Impacts of NR-U | 3GPP RAN2 | imported from 3GU |
R3‑194734 | LS on Clarification for private networks | Nokia | imported from 3GU |
R3‑194735 | Correction of security indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194736 | Correction on Maximum Integrity Protected Data Rate | NEC | imported from 3GU |
R3‑194737 | Summary of offline discussion on “Direct Data Forwarding Between NG-RAN and E-UTRAN” (CB#68) | Ericsson | imported from 3GU |
R3‑194738 | [Draft] Reply LS on LTE-M identification in 5GC | Qualcomm Incorporated | imported from 3GU |
R3‑194739 | Summary of Offline Discussion: List of open issues related to F1 for support of NR sidelink resource mode 1 and mode 2 | LG | imported from 3GU |
R3‑194740 | Support of Service Authorization for V2X over NG | LG Electronics, LG Uplus | imported from 3GU |
R3‑194741 | Support of Service Authorization for V2X over Xn | Ericsson | imported from 3GU |
R3‑194742 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194743 | Support of NR V2X sidelink AMBR and authorization | CATT, Huawei, Ericsson, LG Electronics | imported from 3GU |
R3‑194744 | Support of NR V2X sidelink AMBR and authorization - Withdrawn | Huawei | imported from 3GU |
R3‑194745 | Summary of offline for alternative QoS profiles | Vodafone | imported from 3GU |
R3‑194746 | Discussion on user plane enhancement | CATT,CAICT,China telecom | imported from 3GU |
R3‑194747 | LS on security for multi-CU-UP connectivity | CATT,China Telecom | imported from 3GU |
R3‑194748 | Reply LS on LTE-M identification in 5GC | Qualcomm Incorporated | imported from 3GU |
R3‑194749 | Reply LS on User Data Congestion Analytics | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194750 | Enabling additional PSCell reporting and time since EN-DC was deconfigured | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194751 | Enabling additional PSCell reporting | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194752 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑194753 | Correction on source TNL ADDRESS in NG-C interface | CATT | imported from 3GU |
R3‑194754 | Correction to EN-DC TNL address discovery | Huawei | imported from 3GU |
R3‑194755 | LS on full configuration during SN Modification procedure | Huawei | imported from 3GU |
R3‑194756 | Update of TNL Address discovery for EN-DC (using new container) | ZTE | imported from 3GU |
R3‑194757 | LS reply on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194758 | LS on full configuration during SN Modification procedure | Huawei | imported from 3GU |
R3‑194759 | CR on MR-DC low layer coordination with an MgNB-DU | CATT | imported from 3GU |
R3‑194760 | Text proposal to TR 38.856 on local LMF architecture | CMCC | imported from 3GU |
R3‑194761 | Introduction of Additional RRM Policy Index (ARPI) | Ericsson, Vodafone, Deutsche Telekom, Verizon Wireless, TIM, AT&T, Orange | imported from 3GU |
R3‑194762 | Stage2 Introductions of Some MR-DC New Features (e.g. ARPI) | ZTE | imported from 3GU |
R3‑194763 | LS on enhanced Make-Before-Break data forwarding | Ericsson | imported from 3GU |
R3‑194764 | CR on MCG PHR format in MgNB-DU | CATT | imported from 3GU |
R3‑194765 | Introduction of handover failure cause | CATT | imported from 3GU |
R3‑194766 | (TP for LTE_feMob BL CR for TS 36.300): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194767 | (TP for LTE_feMob BL CR for TS 36.423): Enhanced Make-Before-Break - HO preparation | Ericsson | imported from 3GU |
R3‑194768 | LS on enhanced Make-Before-Break data forwarding | Ericsson | imported from 3GU |
R3‑194769 | BLCR for TS 38.413 for support of SON on NGAP | Huawei | imported from 3GU |
R3‑194770 | BLCR for TS 36.413 for support of SON on NGAP | Huawei | imported from 3GU |
R3‑194771 | BLCR for TS 38.423 for support of SON on NGAP | Samsung | imported from 3GU |
R3‑194772 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | Ericsson | imported from 3GU |
R3‑194773 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | Huawei | imported from 3GU |
R3‑194774 | (TP to BL CR for 38.423): Addition of Load Sharing and Load Balancing Optimisation | Nokia | imported from 3GU |
R3‑194775 | BL CR: Addition of Load Sharing and Load Balancing Optimisation | CATT | imported from 3GU |
R3‑194776 | 38.300 BLCR for introducing NR SON features | CMCC,Huawei | imported from 3GU |
R3‑194777 | (TP for LTE_eMTC5, NB_IOTenh3 BL CR for TS 36.413): Introduction of MT Early Data Transmission | Ericsson | imported from 3GU |
R3‑194778 | Introducing NGAP support for TSC deterministic QoS | Nokia, Nokia Shanghai Bell, Huawei | imported from 3GU |
R3‑194779 | TP for 38.473 BL CR for Providing accurate reference time Information from gNB-DU to gNB-CU | ZTE | imported from 3GU |
R3‑194780 | LS reply on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194781 | Introduction of 5G-SRVCC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194782 | Support of NR V2X sidelink AMBR and authorization | Huawei | imported from 3GU |
R3‑194783 | eply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Vodafone | imported from 3GU |
R3‑194784 | LS on security for multi-CU-UP connectivity | CATT,China Telecom | imported from 3GU |
R3‑194785 | Reply LS on RAN sharing and Emergency services with Non-Public Networks | Qualcomm Incorporated | imported from 3GU |
R3‑194786 | LS on clarifications on Private Networks | Nokia | imported from 3GU |
R3‑194787 | LS on the IAB-indication to core networkure | Qualcomm | imported from 3GU |
R3‑194788 | Reroute NSSF provided information | ZTE, Interdigital, NOKIA, NOKIA Shanghai Bell, NEC, Ericsson | imported from 3GU |
R3‑194789 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑194790 | CR for introducing WWC in RAN | Huawei, Telecom Italia | imported from 3GU |
R3‑194791 | Correction of semantic descriptions in TS 38.463 (rapporteur) | Ericsson | imported from 3GU |
R3‑194792 | Support of Ethernet Type Bearer | Huawei, Vodafone | imported from 3GU |
R3‑194793 | Support of Ethernet Type Bearer | Huawei, Vodafone | imported from 3GU |
R3‑194794 | LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
R3‑194795 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point | Vodafone | imported from 3GU |
R3‑194796 | TR 38.821 v0.8.0 | Thales | imported from 3GU |
R3‑194797 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Intel Corporation | imported from 3GU |
R3‑194798 | Baseline CR for introducing Rel-16 LTE further mobility enhancements | Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑194799 | BL CR to 36.413: Support for IAB | Huawei | imported from 3GU |
R3‑194800 | BL CR to 38.401: Support for IAB | Huawei | imported from 3GU |
R3‑194801 | BL CR to 38.413: Support for IAB | Nokia Shanghai Bell | imported from 3GU |
R3‑194802 | BL CR to 38.473: Support for IAB | Ericsson | imported from 3GU |
R3‑194803 | Baseline CR for introducing Rel-16 NR mobility enhancement | Intel Corporation | imported from 3GU |
R3‑194804 | Baseline CR for introducing Rel-16 NR mobility enhancement | Nokia, Nokia Shanghai Bell, Intel Corporation | imported from 3GU |
R3‑194805 | Transmission Measurement Function in NG-RAN | Ericsson | imported from 3GU |
R3‑194806 | BLCR for TS 38.423 for support of SON on NGAP | Samsung | imported from 3GU |
R3‑194807 | Introduction of MT Early Data Transmission | Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑194808 | Support of Enhanced Coverage restriction in NGAP for LTE-M UEs | Ericsson | imported from 3GU |
R3‑194809 | Introduction of Control Plane CIoT 5GS Optimisation for NB-IOT and eMTC | Qualcomm Incorporated | imported from 3GU |
R3‑194810 | Introduction of CP UP NB-IoT Others | Huawei | imported from 3GU |
R3‑194811 | Introduction of NB-IoT related NG-AP procedures | Huawei | imported from 3GU |
page generated from database: 2024-03-25 09:25:51