3GPP TDocs (written contributions) at meeting
Meeting: R3-101 - 2018-08-20 to 2018-08-24, Gothenburg
meeting id: R3-101 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑184400 | RAN3-101 meeting Agenda | ETSI | imported from 3GU |
R3‑184401 | RAN3-100Bis meeting Report | MCC | imported from 3GU |
R3‑184402 | RAN3-AH-1807 meeting report | ETSI | imported from 3GU |
R3‑184403 | Paging in NGSO Satellite Systems | HUGHES Network Systems Ltd | imported from 3GU |
R3‑184404 | Discussion on F1 RRC version handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184405 | Introduction of F1 RRC version handling | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184406 | (TP for NR BL CR for TS 38.473) Introduction of C-RNTI in UE Context Modification Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184407 | (TP for NR BL CR for TS 38.300): Handling end marker in inter-system | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184408 | (TP for NR BL CR for TS 38.413): Handling end marker in inter-system | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184409 | LS on handling of data forwarding and end markers | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184410 | Rapporteur’s CR for E1 Stage 2 Corrections for NR | Nokia (Rapporteur) | imported from 3GU |
R3‑184411 | (TP for NR BL CR for TS 38.413): Correction of Release inactive to idle | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184412 | (TP for NR BL CR for TS 38.300): Correction of Release inactive to idle | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184413 | (TP for NR BL CR for TS 38.423): Correction of Release inactive to idle | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184414 | (TP for NR BL CR for TS 36.413): Correction of data volume report | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184415 | (TP for NR BL CR for TS 36.423): Correction of data volume report | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184416 | (TP for NR BL CR for TS 38.413): Correction Nokia, Nokia Shanghai Bell of User Plane security | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184417 | (TP for NR BL CR for TS 38.423): Correction of User Plane security | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184418 | (TP for NR BL CR for TS 38.413): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184419 | (TP for NR BL CR for TS 38.423): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184420 | (TP for NR BL CR for TS 38.473): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184421 | (TP for NR BL CR for TS 38.463): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184422 | (TP for NR BL CR for TS 38.413): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184423 | (TP for NR BL CR for TS 38.423): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184424 | (TP for NR BL CR for TS 38.473): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184425 | (TP for NR BL CR for TS 38.463): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184426 | (TP for NR BL CR for TS 38.413): Correction of PPI | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184427 | (TP for NR BL CR for TS 38.423): Correction of PPI | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184428 | (TP for NR BL CR for TS 38.413): Correction of NSSAI for paging. | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184429 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184430 | (TP for NR BL CR for TS 38.300): Correction of slicing stage 2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184431 | (TP for NR BL CR for TS 38.413): Correction of signaled allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184432 | (TP for NR BL CR for TS 38.423): Correction of slice resource cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184433 | (TP for NR BL CR for TS 38.413): Correction of slice resource cause | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184434 | (TP for NR BL CR for TS 36.413): Correction of mobility restriction | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184435 | (TP for NR BL CR for TS 36.423): Correction of mobility restriction | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184436 | (TP for NR BL CR for TS 38.413): Correction of PDU Session Resource Release Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184437 | (TP for NR BL CR for TS 38.413): Correction of Path Swicth Failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184438 | Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
R3‑184439 | Introduction of UE differentiation | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
R3‑184440 | Consideration on UE differentiation | Huawei | imported from 3GU |
R3‑184441 | Consideration on eNB CU DU and W1 interface | Huawei | imported from 3GU |
R3‑184442 | Introduction of eNB-CU and eNB-DU Definition | Huawei | imported from 3GU |
R3‑184443 | Introduction of eNB-CU and eNB-DU Definition | Huawei | imported from 3GU |
R3‑184444 | Introduction of eNB-CU and eNB-DU Definition | Huawei | imported from 3GU |
R3‑184445 | W1 interface User Plane Protocol | Huawei | imported from 3GU |
R3‑184446 | Supporting of W1 user Plane Protocol | Huawei | imported from 3GU |
R3‑184447 | Supporting of W1 user Plane Protocol | Huawei | imported from 3GU |
R3‑184448 | (TP for NR BL CR for TS 38.413): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184449 | (TP for NR BL CR for TS 38.463): Correction of dedicated PDU Session Transport | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184450 | (TP for NR BL CR for TS 38.410): Rapporteur’s updates for TS 38.410. | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184451 | (TP for NR BL CR for TS 38.415): Rapporteur’s updates forTS 38.415 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184452 | (TP for NR BL CR for TS 38.415): Further Correction of TS 38415. | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184453 | Authentication Failure handling in case of eNB CP Relocation | Huawei | imported from 3GU |
R3‑184454 | Correction on Authentication Failure handling in case of eNB CP Relocation | Huawei | imported from 3GU |
R3‑184455 | Correction on Authentication Failure handling in case of eNB CP Relocation | Huawei | imported from 3GU |
R3‑184456 | Introduction of NPRS enhancement | Huawei | imported from 3GU |
R3‑184457 | Introduction of NPRS enhancement | Huawei | imported from 3GU |
R3‑184458 | Consideration on MME supporting RAT Type | Huawei, Vodafone, CMCC, China Unicom | imported from 3GU |
R3‑184459 | Introduction of MME supporting RAT | Huawei, Vodafone, CMCC, China Unicom | imported from 3GU |
R3‑184460 | Introduction of MME supporting RAT | Huawei, Vodafone, CMCC, China Unicom | imported from 3GU |
R3‑184461 | Introduction of MME supporting RAT | Huawei, Vodafone, CMCC, China Unicom | imported from 3GU |
R3‑184462 | Correction on reference of coverage level for location service | Huawei | imported from 3GU |
R3‑184463 | Correction on reference of coverage level for location service | Huawei | imported from 3GU |
R3‑184464 | Inter UE QoS in CP Relocation | Huawei | imported from 3GU |
R3‑184465 | Introduction of inter UE QoS in CP relocation scenario | Huawei | imported from 3GU |
R3‑184466 | (TP for NR BL CR for TS 36.413): Alignment of Abbreviations | Interdigital Asia LLC | imported from 3GU |
R3‑184467 | (TP for NR BL CR for TS 36.423): Alignment of Abbreviations | Interdigital Asia LLC | imported from 3GU |
R3‑184468 | (TP for NR BL CR for TS 36.463): Alignment of Abbreviations | Interdigital Asia LLC | imported from 3GU |
R3‑184469 | (TP for NR BL CR for TS 36.473): Alignment of Abbreviations | Interdigital Asia LLC | imported from 3GU |
R3‑184470 | Baseline CR for TS 38.472 | Interdigital Asia LLC | imported from 3GU |
R3‑184471 | Reply LS on connection control | 3GPP CT1, Qualcomm | imported from 3GU |
R3‑184472 | LS on Definition of Maximum Packet Loss Rate | 3GPP CT3, Huawei | imported from 3GU |
R3‑184473 | LS on Change of value type of Maximum Packet Loss Rate | 3GPP CT3, Huawei | imported from 3GU |
R3‑184474 | LS out to various organisations on usage of NFV Specifications | ETSI ISG NFV, Telefonica | imported from 3GU |
R3‑184475 | Reply LS on Bluetooth/WLAN measurement collection in MDT | 3GPP RAN2, China Mobile | imported from 3GU |
R3‑184476 | Reply LS on aspects of handling large UE radio capabilities in EPC | 3GPP RAN2, Vodafone | imported from 3GU |
R3‑184477 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | 3GPP RAN2, Nokia | imported from 3GU |
R3‑184478 | Reply LS on NR Cell Information signalled over X2 for EN-DC | 3GPP RAN2, Ericsson | imported from 3GU |
R3‑184479 | LS on I-RNTI in NR | 3GPP RAN2, Huawei | imported from 3GU |
R3‑184480 | Reply LS to SA5 on L2 measurements | 3GPP RAN2, Ericsson | imported from 3GU |
R3‑184481 | Reply LS on details of RAN notification area | 3GPP RAN2, Samsung | imported from 3GU |
R3‑184482 | LS to RAN3 on Suspend-Resume agreements | 3GPP RAN2, Ericsson | imported from 3GU |
R3‑184483 | LS on connection re-establishment security | 3GPP RAN2, Samsung | imported from 3GU |
R3‑184484 | Reply LS on optimisation of UE capability signalling | 3GPP RAN2, Mediatek | imported from 3GU |
R3‑184485 | LS on Issues with AS Release Assistance Indicator | 3GPP SA2, Qualcomm | imported from 3GU |
R3‑184486 | Reply LS on FS_eVoLP | 3GPP SA2, Qualcomm | imported from 3GU |
R3‑184487 | LS Reply on LMF determination that the UE is served by NR | 3GPP SA2, Huawei | imported from 3GU |
R3‑184488 | Reply LS on signalling of dynamic 5QI values | 3GPP SA2, Qualcomm | imported from 3GU |
R3‑184489 | Reply LS on Access Restriction Data for NR in EPC | 3GPP SA2, Cisco | imported from 3GU |
R3‑184490 | LS Reply on RAN initiated TNL Associations over NGAP | 3GPP SA2, Huawei | imported from 3GU |
R3‑184491 | Reply LS on Connection Control | 3GPP SA2, Qualcomm | imported from 3GU |
R3‑184492 | Reply LS on Location Reporting for Area of Interest | 3GPP SA2, Samsung | imported from 3GU |
R3‑184493 | LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | 3GPP SA2, Vodafone | imported from 3GU |
R3‑184494 | LS on Data Analytics in SA WG2/NWDAF | 3GPP SA2, Huawei | imported from 3GU |
R3‑184495 | LS on L2 measurement specification for NR in R15 | 3GPP SA5, Ericsson | imported from 3GU |
R3‑184496 | Liaison on Cooperative Dynamic Bandwidth Assignment | ITU-T Study Group 15, Huawei | imported from 3GU |
R3‑184497 | Baseline CR for TS 36.413 covering agreements of RAN3#AH1807 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184498 | Baseline CR for TS 36.423 covering agreements of RAN3#AH1807 | Ericsson | imported from 3GU |
R3‑184499 | Baseline CR for TS 38.401 covering agreements of RAN3#AH1807 | NEC | imported from 3GU |
R3‑184500 | Baseline CR for TS 38.410 covering agreements of RAN3#AH1807 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184501 | Baseline CR for TS 38.413 covering agreements of RAN3#AH1807 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184502 | Baseline CR for TS 38.415 covering agreements of RAN3#AH1807 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184503 | Baseline CR for TS 38.420 covering agreements of RAN3#AH1807 | Qualcomm Incorporated | imported from 3GU |
R3‑184504 | Baseline CR for TS 38.423 covering agreements of RAN3#AH1807 | Ericsson | imported from 3GU |
R3‑184505 | Baseline CR for TS 38.425 covering agreements of RAN3#AH1807 | Samsung | imported from 3GU |
R3‑184506 | Baseline CR for TS 38.460 covering agreements of RAN3#AH1807 | Nokia (Rapporteur) | imported from 3GU |
R3‑184507 | Baseline CR for TS 38.462 covering agreements of RAN3#AH1807 | Huawei | imported from 3GU |
R3‑184508 | Baseline CR for TS 38.463 covering agreements of RAN3#AH1807 | Ericsson | imported from 3GU |
R3‑184509 | Baseline CR for TS 38.470 covering agreements of RAN3#AH1807 | Huawei | imported from 3GU |
R3‑184510 | Baseline CR for TS 38.472 covering agreements of RAN3#AH1807 | Interdigital Asia LLC | imported from 3GU |
R3‑184511 | Baseline CR for TS 38.473 covering agreements of RAN3#AH1807 | Huawei | imported from 3GU |
R3‑184512 | Baseline CR for TS 37.340 covering agreements of RAN3#AH1807 | ZTE | imported from 3GU |
R3‑184513 | Baseline CR for TS 38.300 covering agreements of RAN3#AH1807 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184514 | Initial Considerations on NTN Deployment and Architecture | ZTE | imported from 3GU |
R3‑184515 | Further Discussion on NTN Architecture Issues | ZTE | imported from 3GU |
R3‑184516 | (TP for NR BL CR for TS 37.340) Corrections of Notification Control Indication | ZTE | imported from 3GU |
R3‑184517 | (TP for NR BL CR for TS 37.340) Corrections of Notification Control Indication | ZTE | imported from 3GU |
R3‑184518 | (TP for NR BL CR for TS 38.423) Corrections of Notification Control Indication | ZTE | imported from 3GU |
R3‑184519 | Further Discussion on RRC_INACTIVE Behaviours upon Receiving NG Reset | ZTE | imported from 3GU |
R3‑184520 | (TP for NR BL CR for TS 38.413) Corrections of RRC_INACTIVE Behaviours upon Receiving NG Reset | ZTE | imported from 3GU |
R3‑184521 | Liaison ESOA (EMEA Satellite Operators Association) on 5G for Satellite Systems | ESOA (EMEA Satellite Operators Association), Echostar, Thales Alenia Space | imported from 3GU |
R3‑184522 | Proposed scope | THALES | imported from 3GU |
R3‑184523 | Proposed skeleton | THALES | imported from 3GU |
R3‑184524 | NTN Overview and scenarios | THALES | imported from 3GU |
R3‑184525 | NTN RAN architecture key issues | THALES | imported from 3GU |
R3‑184526 | Discussion on gNB Backward Compatibility with en-gNB and Radio Resource Sharing between eNB and gNB via X2 Interface | ZTE | imported from 3GU |
R3‑184527 | Further Discussion on Applicability of IE Time to Wait | ZTE | imported from 3GU |
R3‑184528 | (TP for NR BL CR for TS 36.423) Add Up IE Time to Wait to EN-DC Relevant Failure Messages | ZTE | imported from 3GU |
R3‑184529 | (TP for NR BL CR for TS 38.413) Correction of IMS Voice fallback over NGAP Aligning to SA2 | ZTE | imported from 3GU |
R3‑184530 | (TP for NR BL CR for TS 36.423) Correction of SgNB Activity Notification Procedure | ZTE | imported from 3GU |
R3‑184531 | (TP for NR BL CR for TS 38.413) Clarification of no priority Value in Priority Level IE of ARP | ZTE | imported from 3GU |
R3‑184532 | (TP for NR BL CR for TS 38.423) Correction of UE Context Id for Retrieval | ZTE | imported from 3GU |
R3‑184533 | (TP for NR BL CR for TS 38.413) Correction of UE Radio Capability etc | ZTE | imported from 3GU |
R3‑184534 | (TP for NR BL CR for TS 38.423) Corrections on RAN Paging Area with Multiple PLMN | ZTE | imported from 3GU |
R3‑184535 | Further Discussion on RAN Information Management | ZTE | imported from 3GU |
R3‑184536 | (TP for NR BL CR for TS 38.413) Introduction of NR RAN Information Management Function | ZTE | imported from 3GU |
R3‑184537 | Discussion on Prohibit Timer Between Consecutive Notify Messages | ZTE | imported from 3GU |
R3‑184538 | (TP for NR BL CR for TS 38.300) Introduction of Prohibit Timer Between Consecutive Notify Messages | ZTE | imported from 3GU |
R3‑184539 | (TP for NR BL CR for TS 38.423) Introduction of New Cause Value Slice Not Supported | ZTE | imported from 3GU |
R3‑184540 | (TP for NR BL CR for TS 38.423) Usage Alignment of Index to RFSP info for XnAP | ZTE | imported from 3GU |
R3‑184541 | (TP for NR BL CR for TS 38.423) Corrections for UP Security Handling in DC R3-184540 Gothenburg, Sweden, 20th – 24th August 2018 | ZTE | imported from 3GU |
R3‑184542 | (TP for NR BL CR for TS 38.413) Corrections for UP Security Handling in DC during PDU Session Lifetime | ZTE | imported from 3GU |
R3‑184543 | (TP for NR BL CR for TS 38.423) Corrections on Setting RLC Mode | ZTE | imported from 3GU |
R3‑184544 | (TP for NR BL CR for TS 38.423) Alignment of Term Mobility Restriction List for DC | ZTE | imported from 3GU |
R3‑184545 | Further Discussion on Cell Radio Resource Sharing over Xn | ZTE | imported from 3GU |
R3‑184546 | (TP for NR BL CR for TS 38.413) Add Up User Location Information into PDU SESSION RESOURCE MODIFY INDICATION Message | ZTE | imported from 3GU |
R3‑184547 | (TP for NR BL CR for TS 37.340) Add Up Stage2 Behaviors for PDCP SN Length Indication | ZTE | imported from 3GU |
R3‑184548 | Consideration on AS RAI triggered UE Context Release | Huawei | imported from 3GU |
R3‑184549 | [Draft] Reply LS on Issues with AS Release Assistance Indicator | Huawei | imported from 3GU |
R3‑184550 | (TP for NR BL CR for TS 38.423): Consideration on SCG kept for Inter-MN handover | ZTE | imported from 3GU |
R3‑184551 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Modify procedure | ZTE | imported from 3GU |
R3‑184552 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Setup procedure | ZTE | imported from 3GU |
R3‑184553 | (TP for NR BL CR for TS 38.413): Correction on PDU Session Resource Modify Inidication procedure | ZTE | imported from 3GU |
R3‑184554 | (TP for NR BL CR for TS 37.340): Consideration on Inactivity notification for EN-DC | ZTE | imported from 3GU |
R3‑184555 | Discussion on RAN initiated PDU session splitting | ZTE | imported from 3GU |
R3‑184556 | (TP for NR BL CR for TS 38.423): Correction on the configuration for SN terminated MCG/Split bearer | ZTE | imported from 3GU |
R3‑184557 | (TP for NR BL CR for TS 37.340): Consideration on the usage of SN UE X2AP ID IE during inter-MN without SN change | ZTE | imported from 3GU |
R3‑184558 | (TP for NR BL CR for TS 38.423): Correction on RRC Inactivity for MR-DC | ZTE | imported from 3GU |
R3‑184559 | (TP for BL CR for TS 37.340) Left issue on Secondary RAT data volume reporting | ZTE | imported from 3GU |
R3‑184560 | (TP for NR BL CR for TS 38.423) Correction on Session AMBR for MR-DC@5GC | ZTE | imported from 3GU |
R3‑184561 | (TP for NR BL CR for TS 38.423) Cell information related to wideband carrier | ZTE | imported from 3GU |
R3‑184562 | Discussion on RAN assisted codec adaptation in DC | ZTE | imported from 3GU |
R3‑184563 | Device-based geo-fencing | Nokia, Nokia Shanghai Bell, AT&T, One2many, Qualcomm Incorporated, Sprint, SyncTechno Inc., T-Mobile USA | imported from 3GU |
R3‑184564 | Introduction of Warning Area Coordinates in S1AP: WRITE-REPLACE WARNING REQUEST | Nokia, Nokia Shanghai Bell, AT&T, One2many, Qualcomm Incorporated, Sprint, SyncTechno Inc., T-Mobile USA | imported from 3GU |
R3‑184565 | Summary of additional corrections in TS 38.413 BL CR (rev1) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184566 | TP for TS 38.413 BL CR: rapporteur cleanup | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184567 | TP for TS 38.413 BL CR: Correction of SMF containers in NGAP procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184568 | Inter system data forwarding | CATT | imported from 3GU |
R3‑184569 | Discussion on Topology Adaption | CATT | imported from 3GU |
R3‑184570 | TP for NR BL CR for TS 38.300 Clarification on RRC Inactive handling | CATT | imported from 3GU |
R3‑184571 | TP for NR BL CR for TS 38.413 Cleanup for Core Network Assistance Information | CATT | imported from 3GU |
R3‑184572 | TP for TS 38.401 Correction to gNB-CU-UP change | CATT | imported from 3GU |
R3‑184573 | TP for TS 38.463 Correction to RNAU with anchor change | CATT | imported from 3GU |
R3‑184574 | TP for TS 38.463 Correction to Data Forwarding Information | CATT | imported from 3GU |
R3‑184575 | TP for NR BL CR for TS 38.413 Correction to security Indication | CATT | imported from 3GU |
R3‑184576 | TP for NR BL CR for TS 38.423 Correction to security Indication | CATT | imported from 3GU |
R3‑184577 | TP for NR BL CR for TS 38.413 Correction to Path Switch ACK | CATT | imported from 3GU |
R3‑184578 | TP for NR BL CR for TS 38.413 Corrections to recommended information for Paging | CATT | imported from 3GU |
R3‑184579 | On inter-system data forwarding and end marker handling | China Telecommunications | imported from 3GU |
R3‑184580 | Notification of PDCP SN length change | Huawei | imported from 3GU |
R3‑184581 | (TP for NR BL CR for TS 38.413): 5QI Presence for Dynamic 5QI Descriptor | Huawei, Qualcomm Incorporated | imported from 3GU |
R3‑184582 | (TP for NR BL CR for TS 38.423): 5QI Presence for Dynamic 5QI Descriptor | Huawei, Qualcomm Incorporated | imported from 3GU |
R3‑184583 | (TP for NR BL CR for TS 38.473): 5QI Presence for Dynamic 5QI Descriptor | Huawei, Qualcomm Incorporated | imported from 3GU |
R3‑184584 | (TP for NR BL CR for TS 38.463): 5QI Presence for Dynamic 5QI Descriptor | Huawei, Qualcomm Incorporated | imported from 3GU |
R3‑184585 | (TP for NR BL CR for TS 38.413): Separation of DL and UL PDU Session AMBR | Huawei | imported from 3GU |
R3‑184586 | (TP for NR BL CR for TS 38.423): Separation of DL and UL PDU Session AMBR | Huawei | imported from 3GU |
R3‑184587 | Consideration on “CP alternatives for architecture 1a” with NSA operation | KDDI Corporation, Kyocera | imported from 3GU |
R3‑184588 | S1 UE Radio Capability issue | KDDI Corporation | imported from 3GU |
R3‑184589 | ANR | Huawei | imported from 3GU |
R3‑184590 | (TP for NR BL CR for TS 38.300): Periodic RNAU without UE context relocation | Huawei | imported from 3GU |
R3‑184591 | (TP for NR BL CR for TS 38.420): CSI-RS configuration transfer over Xn | Huawei, Vodafone | imported from 3GU |
R3‑184592 | (TP for NR BL CR for TS 38.423): Stage 3 CR for support of CSI-RS resource exchange | Huawei | imported from 3GU |
R3‑184593 | [DRAFT] LS on CSI-RS resource configuration transfer over Xn | Huawei | imported from 3GU |
R3‑184594 | L2 Measurements for NG-RAN | Huawei | imported from 3GU |
R3‑184595 | [Draft] Reply LS on L2 Measurements | Huawei | imported from 3GU |
R3‑184596 | (TP for NR BL CR for TS 38.413) Update to area of interest | Huawei | imported from 3GU |
R3‑184597 | (TP for NR BL CR for TS 38.423) Update to area of interest | Huawei | imported from 3GU |
R3‑184598 | (TP for NR BL CR for 38.423) Support of 8bits RANAC | Huawei | imported from 3GU |
R3‑184599 | Support of 8 bits RANAC | Huawei | imported from 3GU |
R3‑184600 | Support of delta configuration for inactive UE in CU DU architecture | Huawei | imported from 3GU |
R3‑184601 | Support of delta configuration for inactive UE in CU DU architecture | Huawei | imported from 3GU |
R3‑184602 | (TP for NR BL CR for TS 38.413) Age of location information | Huawei | imported from 3GU |
R3‑184603 | (TP for NR BL CR for 38.423): Data forwarding for RRC reestablishment UE with context fetch | Huawei | imported from 3GU |
R3‑184604 | (TP for NR BL CR for TS 38.423): Correction to UE Context Release | Huawei | imported from 3GU |
R3‑184605 | En-gNB X2 TNL address discovery | Huawei, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184606 | (TP for NR BL CR for TS 37.340): Correction to Inactive State Handling in MR-DC | Huawei | imported from 3GU |
R3‑184607 | (TP for NR BL CR for TS 37.340) Handling of Session AMBR for NGEN-DC | LG Electronics, KT Corp. | imported from 3GU |
R3‑184608 | (TP for NR BL CR for TS 38.423) Consideration on SN triggered modification for NGEN-DC DRB options | LG Electronics, KT Corp. | imported from 3GU |
R3‑184609 | (TP for NR BL CR for TS 37.340) Corrections on secondary RAT data volume reporting | Huawei | imported from 3GU |
R3‑184610 | Corrections on resource coordination in stage-2 | Huawei | imported from 3GU |
R3‑184611 | X2 Corrections for EN-DC | Huawei | imported from 3GU |
R3‑184612 | Considerations on high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑184613 | Support of high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑184614 | [DRAFT] LS to SA2 for support high bit rate for EN-DC | Huawei | imported from 3GU |
R3‑184615 | Handling of inconsistent RLC mode | Huawei | imported from 3GU |
R3‑184616 | Clarification on RLC mode inconsistency | Huawei | imported from 3GU |
R3‑184617 | (TP for NR BL CR for TS 38.423) Clarification on RLC mode inconsistency | Huawei | imported from 3GU |
R3‑184618 | Data forwarding during bearer type change | Huawei | imported from 3GU |
R3‑184619 | Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
R3‑184620 | (TP for NR BL CR for TS 38.423) Introduction of UL/DL Forwarding GTP TEID | Huawei | imported from 3GU |
R3‑184621 | Considerations on direct data forwarding | Huawei | imported from 3GU |
R3‑184622 | Support of direct data forwarding | Huawei, NTT DOCOMO, INC. | imported from 3GU |
R3‑184623 | (TP for NR BL CR for TS 38.423) Support of direct data forwarding | Huawei, NTT DOCOMO, INC. | imported from 3GU |
R3‑184624 | Considerations on NR usage restriction in EPS | Huawei | imported from 3GU |
R3‑184625 | NR usage restriction in HRL | Huawei | imported from 3GU |
R3‑184626 | NR usage restriction in HRL | Huawei | imported from 3GU |
R3‑184627 | Correction on target NG-RAN Node ID | Huawei | imported from 3GU |
R3‑184628 | [TP for NR BL CR for TS 37.340] Alignment of message name | Huawei | imported from 3GU |
R3‑184629 | (TP for NR BL CR for TS 38.413) Presence of the Security Indication for user plane security | Huawei | imported from 3GU |
R3‑184630 | (TP for NR BL CR for TS 38.423) Presence of the Security Indication for user plane security | Huawei | imported from 3GU |
R3‑184631 | DRB ID allocation for MR-DC with 5GC | Huawei | imported from 3GU |
R3‑184632 | (TP for NR BL CR for TS 38.423) DRB ID allocation | Huawei | imported from 3GU |
R3‑184633 | (TP for NR BL CR for TS 38.423) Support of QoS for MR-DC with 5GC Alt1 | Huawei | imported from 3GU |
R3‑184634 | (TP for NR BL CR for TS 38.423) Support of QoS for MR-DC with 5GC Alt2 | Huawei | imported from 3GU |
R3‑184635 | (TP for NR BL CR for TS 37.340) SN-triggered Modification for MR-DC | Huawei | imported from 3GU |
R3‑184636 | In-order delivery in MR-DC Qos flow offloading | Huawei | imported from 3GU |
R3‑184637 | (TP for NR BL CR for TS 38.423) PDU Session AMBR for MR-DC | Huawei | imported from 3GU |
R3‑184638 | (TP for NR BL CR for TS 38.425) Clarification on DL discard Number of blocks | Huawei | imported from 3GU |
R3‑184639 | (TP for NR BL CR for TS 38.423): Correction to Retrieve UE Context Request | Huawei | imported from 3GU |
R3‑184640 | (TP for NR BL CR for TS 38.413): Notification Control during Handover | CATT | imported from 3GU |
R3‑184641 | (TP for NR BL CR for TS 38.423): Notification Control during Handover | CATT | imported from 3GU |
R3‑184642 | (TP for NR BL CR for TS 38.423): Notification Control during Secondary Node Change | CATT | imported from 3GU |
R3‑184643 | (TP for NR BL CR for TS 38.473): Notification Control during Handover | CATT | imported from 3GU |
R3‑184644 | (TP for NR BL CR for TS 38.413): Allowed NSSAI in DL NAS TRANSPORT | CATT | imported from 3GU |
R3‑184645 | Discuss on Including Allowed NSSAI in paging | CATT | imported from 3GU |
R3‑184646 | (TP for NR BL CR for TS 38.413): slice related cause value | CATT | imported from 3GU |
R3‑184647 | (TP for NR BL CR for TS 38.423): slice related cause value | CATT | imported from 3GU |
R3‑184648 | (TP for NR BL CR for TS 38.410): Overload Control | CATT | imported from 3GU |
R3‑184649 | (TP for NR BL CR for TS 38.413): Overload Control | CATT | imported from 3GU |
R3‑184650 | (TP for NR BL CR for TS 38.413): Correction for PWS Restart Indication | CATT | imported from 3GU |
R3‑184651 | (TP for NR BL CR for TS 38.470) Load management function in F1 interface | LG Electronics Inc., KT Corp. | imported from 3GU |
R3‑184652 | (TP for NR BL CR for TS 38.473) Stage 3 on load management function in F1 interface | LG Electronics Inc., KT Corp. | imported from 3GU |
R3‑184653 | RRC version handling | LG Electronics Inc. | imported from 3GU |
R3‑184654 | Comparison on CP alternatives of architecture 1a | LG Electronics Inc. | imported from 3GU |
R3‑184655 | Access Restriction Data for NR in EPC | Huawei | imported from 3GU |
R3‑184656 | on Access Restriction Data for NR in EPC | Huawei | imported from 3GU |
R3‑184657 | Access Restriction Data for NR in EPC | Huawei | imported from 3GU |
R3‑184658 | Further discussion on Multiple CU-UPs impact on NG interface | ZTE Corporation | imported from 3GU |
R3‑184659 | (TP for NR BL CR for TS 38.413) Supporting multiple CU-UPs over NG interface | ZTE Corporation | imported from 3GU |
R3‑184660 | (TP for SA BL CR for TS38.473) Clarification on Cell activation failure | ZTE Corporation | imported from 3GU |
R3‑184661 | Discussion on PLMN and TAC transmission over F1 | ZTE Corporation | imported from 3GU |
R3‑184662 | (TP for SA BL CR for TS38.470) Update on PLMN and TAC transmission | ZTE Corporation | imported from 3GU |
R3‑184663 | (TP for SA BL CR for TS38.473) Update on PLMN and TAC transmission | ZTE Corporation | imported from 3GU |
R3‑184664 | Left issues on Gap Configuration over F1 | ZTE Corporation | imported from 3GU |
R3‑184665 | (TP for NR BL CR for TS38.470) Gap Configuration over F1 | ZTE Corporation | imported from 3GU |
R3‑184666 | (TP for NR BL CR for TS38.473) Gap Configuration over F1 | ZTE Corporation | imported from 3GU |
R3‑184667 | (TP for NR BL CR for TS38.401) Corrections on centrilized retransmission for TS38.401 | ZTE Corporation | imported from 3GU |
R3‑184668 | Issues on RLC reestablishment indication | ZTE Corporation | imported from 3GU |
R3‑184669 | RLC reestablishment indication over F1 for TS38.473 | ZTE Corporation | imported from 3GU |
R3‑184670 | RLC reestablishment indication over X2 for TS36.423 | ZTE Corporation | imported from 3GU |
R3‑184671 | Left issues on UE Report for ANR | ZTE Corporation | imported from 3GU |
R3‑184672 | (TP for NR BL CR for TS 38.413) Overload control for unified access control | ZTE Corporation | imported from 3GU |
R3‑184673 | More consideration for EN-DC TNL address discovery | ZTE Corporation | imported from 3GU |
R3‑184674 | (TP for NR BL CR for TS36.300) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
R3‑184675 | (TP for NR BL CR for TS36.413) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
R3‑184676 | (TP for NR BL CR for TS36.423) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
R3‑184677 | (TP for NR BL CR for TS38.300) EN-DC TNL address discovery solution 3 | ZTE Corporation | imported from 3GU |
R3‑184678 | Inter MME EN-DC TNL Address discovery | ZTE Corporation | imported from 3GU |
R3‑184679 | Draft LS on Transfer of inter-MME SON Configuration Information for EN-DC | ZTE Corporation | imported from 3GU |
R3‑184680 | (TP for NR BL CR for TS 38.423): UE Level Resource Coordination for MR-DC Connected to 5GC | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑184681 | (TP for NR BL CR for TS 38.413): Serving Cell aware for LTE-NR Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑184682 | Reply LS on signaling of dynamic 5QI | Qualcomm Incorporated | imported from 3GU |
R3‑184683 | (TP for NR BL CR for TS 37.340): Inter-system Handover Between SA and NSA | Qualcomm Incorporated | imported from 3GU |
R3‑184684 | (TP for NR BL CR for TS 38.413): UE Interested Slice | Qualcomm Incorporated, CATT | imported from 3GU |
R3‑184685 | (TP for NR BL CR for TS 38.413): General fallback | Qualcomm Incorporated | imported from 3GU |
R3‑184686 | Avoiding MME Impact from 3-byte TAC in inter-system HO | Qualcomm Incorporated | imported from 3GU |
R3‑184687 | (TP for NR BL CR for TS 38.423): RRC Transfer for NE-DC | Qualcomm Incorporated | imported from 3GU |
R3‑184688 | (TP for MR-DC with 5GC BL CR for TS 38.423): RRC Container correction for NE-DC | Qualcomm Incorporated | imported from 3GU |
R3‑184689 | (TP for NR BL CR for TS 38.423): SN Addition Trigger Indication | Qualcomm Incorporated | imported from 3GU |
R3‑184690 | (TP for MR-DC with 5GC BL CR for TS 38.423): PDCP Change Indication for MR-DC | Qualcomm Incorporated | imported from 3GU |
R3‑184691 | IAB workplan | Qualcomm Incorporated, Samsung, AT&T, KDDI (Rapporteurs) | imported from 3GU |
R3‑184692 | TR 38.874 v040 | Qualcomm Incorporated | imported from 3GU |
R3‑184693 | IAB topology adaption for arch 1a | Qualcomm Incorporated, Ericsson, Nokia, Huawei, KDDI | imported from 3GU |
R3‑184694 | IAB topological redundancy for arch 1a | Qualcomm Incorporated | imported from 3GU |
R3‑184695 | Discussion on SA2’s LS on the Release Assistance Indicator | Qualcomm Incorporated | imported from 3GU |
R3‑184696 | Draft Reply LS on Issues with AS Release Assistance Indicator | Qualcomm Incorporated | imported from 3GU |
R3‑184697 | Introduction of release 14 eMBMS enhancements | Qualcomm Incorporated | imported from 3GU |
R3‑184698 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
R3‑184699 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
R3‑184700 | Addition of TDD UL/DL configuration to OTDOA assistance data | Qualcomm Incorporated | imported from 3GU |
R3‑184701 | Support for NPRS enhancements | Qualcomm Incorporated | imported from 3GU |
R3‑184702 | Support for NPRS enhancements | Qualcomm Incorporated | imported from 3GU |
R3‑184703 | Rapporteur’s CR for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
R3‑184704 | (TP for NR BL CR for TS 38.423) Activity Notification Control over Xn | Qualcomm Incorporated | imported from 3GU |
R3‑184705 | (TP for NR BL CR for TS 38.413) Correction of NAS Container | Qualcomm Incorporated | imported from 3GU |
R3‑184706 | On Data Volume Reporting for 5GC | Qualcomm Incorporated | imported from 3GU |
R3‑184707 | (TP for NR BL CR for TS 38.423) Alignment of Cell Activation Functionality over Xn and F1 | Qualcomm Incorporated, Huawei | imported from 3GU |
R3‑184708 | Mobility restrictions: 5GC restriction in NGAP | Qualcomm Incorporated | imported from 3GU |
R3‑184709 | (TP for NR BL CR for TS 38.413) Cause value for release due to CN-visible mobility | Qualcomm Incorporated | imported from 3GU |
R3‑184710 | (TP for NR BL CR for TS 38.300) Refinement of the stage 2 RRC-Inactive Mobility section | Qualcomm Incorporated | imported from 3GU |
R3‑184711 | (TP for NR BL CR for TS 38.413) Support of maximum bit rate for Integrity Protection | Qualcomm Incorporated | imported from 3GU |
R3‑184712 | (TP for NR BL CR for TS 38.423) Support of maximum bit rate for Integrity Protection | Qualcomm Incorporated | imported from 3GU |
R3‑184713 | [TP for NR BL CR for TS 38.413] Per Slice AMF Set | Huawei | imported from 3GU |
R3‑184714 | [TP for NR BL CR for TS 38.413] Correction on Unique 5G-TMSI | Huawei | imported from 3GU |
R3‑184715 | Considerations on the need for multiple SCTP associations in X2 and Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184716 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184717 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184718 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184719 | Enabling multiple SCTP associations | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184720 | W1 interface Prioritised Time Plan for LTE specific features | Orange Spain | imported from 3GU |
R3‑184721 | (TP for NR BL CR for TS 38.423): further correction to I-RNTI | NEC | imported from 3GU |
R3‑184722 | (TP for NR BL CR for TS 38.473): on exchange of SMTC Info between gNB-CU to gNB-DU | NEC | imported from 3GU |
R3‑184723 | (TP for BL CR to TS 38.463): E1 cause value | NEC | imported from 3GU |
R3‑184724 | (TP for NR BL CR for TS 38.463): discussion on security algorithms and ROHC profile for CP and UP separation | NEC | imported from 3GU |
R3‑184725 | (TP for BL CR to TS 38.413): Maximum Integrity Protected data rate | NEC | imported from 3GU |
R3‑184726 | (TP for NR BL CR for TS 38.473): Clarification of UE Radio Capability presence in CU to DU RRC information | NEC | imported from 3GU |
R3‑184727 | (TP for NR BL CR for TS 38.401): Cell Status when failed to active | NEC | imported from 3GU |
R3‑184728 | (TP for NR BL CR for TS 38.425): Retransmission status in UP | NEC | imported from 3GU |
R3‑184729 | F1 impact due to updated System Information provisioning | NEC | imported from 3GU |
R3‑184730 | F1 impact due to updated System Information provisioning | NEC | imported from 3GU |
R3‑184731 | Tx Direct Current Location of UL BWP | NEC | imported from 3GU |
R3‑184732 | Tx Direct Current Location of UL BWP | NEC | imported from 3GU |
R3‑184733 | Extending the length of E-UTRA-NR Cell Resource Coordination agreement | Ericsson | imported from 3GU |
R3‑184734 | Extending the length of E-UTRA-NR Cell Resource Coordination agreement | Ericsson | imported from 3GU |
R3‑184735 | (TP for NR BL CR for TS 38.423): Xn signaling for E-UTRA - NR Cell Resource Coordination | Ericsson | imported from 3GU |
R3‑184736 | (TP for NR BL CR for TS 38.420): Update to Xn-AP list of functions | Ericsson | imported from 3GU |
R3‑184737 | NR transmission bandwidth signaling | Ericsson | imported from 3GU |
R3‑184738 | CR to TS 36.423 on NR transmission bandwidth signaling | Ericsson | imported from 3GU |
R3‑184739 | CR to TS 38.423 on NR transmission bandwidth signaling | Ericsson | imported from 3GU |
R3‑184740 | CR to TS 38.473 on NR transmission bandwidth signaling | Ericsson | imported from 3GU |
R3‑184741 | Identification of serving PLMN in RRC re-establishment scenario | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184742 | Single X2 instance between eNB and shared en-gNB with TAC per PLMN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184743 | (TP for NR BL CR for TS 36.300): [SON/ANR] Stage 2 updates | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184744 | (TP for NR BL CR for TS 38.423): [SON/ANR] Unified RNL connectivity signalling for 5G cells | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184745 | Unified RNL connectivity signalling for 5G cells | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184746 | Unified RNL connectivity signalling for 5G cells | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184747 | (TP for NR BL CR for TS 38.423): ASN.1 corrections on Served Cell Info | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184748 | Correction of 5GS TAC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184749 | Correction of 5GS TAC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184750 | Encoding of NR Transmission Bandwidth | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184751 | Support for TNL address information discovery for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184752 | Support for TNL address information discovery for EN-DC | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184753 | Establishment of RLC Channels During and After IAB Node Integration for Architecture Group 1 | AT&T | imported from 3GU |
R3‑184754 | Multi-connectivity Architecture Design for IAB Arch. 1a | AT&T | imported from 3GU |
R3‑184755 | Resource Partitioning and Coordination for IAB | AT&T | imported from 3GU |
R3‑184756 | Setup and connection establishment for IAB with NSA | AT&T | imported from 3GU |
R3‑184757 | Control plane signaling delivery in NSA deployment | ZTE Corporation | imported from 3GU |
R3‑184758 | Discussion on UE bearer setup procedure in IAB network | ZTE Corporation | imported from 3GU |
R3‑184759 | Latency analysis for IAB network | ZTE Corporation | imported from 3GU |
R3‑184760 | Discussion on IAB link switch and topology adaptation | ZTE Corporation | imported from 3GU |
R3‑184761 | Consideration on Routing in IAB Architecture 1a and 1b | ZTE Corporation | imported from 3GU |
R3‑184762 | Introduction of PDCP data recovery request/PDCP change indication during SN modification procedure | CATT | imported from 3GU |
R3‑184763 | Introduction of Xn-U TEID in S-Node Modification Required message | CATT | imported from 3GU |
R3‑184764 | Support of PDCP Duplication on Xn | CATT | imported from 3GU |
R3‑184765 | (TP for NR BL CR for TS 37.340) Correction on PCI confusion | CATT | imported from 3GU |
R3‑184766 | (TP for NR BL CR for TS 36.423) Correction on PCI confusion | CATT | imported from 3GU |
R3‑184767 | (TP for SA BL CR for TS 38.473):Support on DC based PDCP duplication | CATT | imported from 3GU |
R3‑184768 | (TP for NR BL CR for TS 38.473) Correction on System Information Delivery^^Command message | CATT | imported from 3GU |
R3‑184769 | (TP for NR BL CR for TS 37.340) Correction on SgNB initiated SgNB Modification procedure | CATT | imported from 3GU |
R3‑184770 | (TP for NR BL CR for TS 37.340)Consideration on DRB ID allocation for MR-DC with 5G CN | CATT | imported from 3GU |
R3‑184771 | (TP for NR BL CR for TS 38.423)Consideration on DRB ID allocation for MR-DC with 5G CN | CATT | imported from 3GU |
R3‑184772 | (TP for TS 38.473) Correction on the definition of RRC-Container IE | CATT | imported from 3GU |
R3‑184773 | (TP for TS 38.473) Correction on gNB-CU System Information on F1 | CATT | imported from 3GU |
R3‑184774 | (TP for TS 38.473)Support of system information update for active UE | CATT | imported from 3GU |
R3‑184775 | Consideration of topology adaptation in IAB | Kyocera | imported from 3GU |
R3‑184776 | Introduction of F1 uplink overload procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184777 | (TP for NR BL CR for TS 38.470) F1 Load management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184778 | Updates on E1 Bearer Context Management | ZTE Corporation | imported from 3GU |
R3‑184779 | (TP for SA BL CR for TS38.463) Updates on E1 RB context management for TS38.463 | ZTE Corporation | imported from 3GU |
R3‑184780 | Further discussion on Load Management over F1 | ZTE Corporation | imported from 3GU |
R3‑184781 | (TP for NR BL CR for TS 38.473) UL configuration in Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184782 | (TP for NR BL CR for TS38.470) Further discussion on Load Management over F1 | ZTE Corporation | imported from 3GU |
R3‑184783 | (TP for NR BL CR for TS38.473) Further discussion on Load Management over F1 | ZTE Corporation | imported from 3GU |
R3‑184784 | (TP for NR BL CR for TS 38.473) Clarification of S-NSSAI in F1 Setup | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184785 | Issues on X2/XnAP Services | ZTE Corporation | imported from 3GU |
R3‑184786 | (TP for NR BL CR for TS36.423) Corrections on X2AP services for TS36.423 | ZTE Corporation | imported from 3GU |
R3‑184787 | New CP Alternative: Distributed RRC functions for IAB | Huawei | imported from 3GU |
R3‑184788 | (TP for NR BL CR for TS38.423) Corrections on XnAP services for TS38.423 | ZTE Corporation | imported from 3GU |
R3‑184789 | Discusson on relationship between CGI and PLMN for NR Served Cell Information | ZTE Corporation | imported from 3GU |
R3‑184790 | (TP for BL CR for TS36.423)Update on NR Served Cell Information | ZTE Corporation | imported from 3GU |
R3‑184791 | (TP for BL CR for TS38.423)Update on NR Served Cell Information | ZTE Corporation | imported from 3GU |
R3‑184792 | Correction on PDCP duplication indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184793 | (TP for BL CR for TS38.473)Update on NR Served Cell Information | ZTE Corporation | imported from 3GU |
R3‑184794 | (TP for BL CR for TS38.463)Clarification on gNB-CU-UP initiated Bearer Context Release Request message | ZTE Corporation | imported from 3GU |
R3‑184795 | (TP for BL CR for TS38.473)Update on SI transfer over F1 | ZTE Corporation | imported from 3GU |
R3‑184796 | Discussion on NTN reference scenarios | ZTE Corporation | imported from 3GU |
R3‑184797 | (TP for NR BL CR for TS 38.401) Support of indirect data transmission for split bearer | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184798 | (TP for NR BL CR for TS 38.463) Processing Capacity Indication for E1 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184799 | Destination Address and Forwarding Path based Routing for IAB | Huawei | imported from 3GU |
R3‑184800 | (TP for NR BL CR for TS 38.463) Support of resuspending the inactive UE and transmission stop | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184801 | Consideration about the F1*-C | Huawei | imported from 3GU |
R3‑184802 | (TP for NR BL CR for TS 38.463) Security Result IE in Bearer Context Setup Response and Bearer Context Modification Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184803 | (TP for NR BL CR for TS 38.463) Transaction ID in non-UE Associated Procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184804 | Comparisons on Control Plane protocols for architecture group 1 | Huawei | imported from 3GU |
R3‑184805 | Basic principles for IAB topology adaptation | Huawei | imported from 3GU |
R3‑184806 | Slice support of IAB nodes | Huawei | imported from 3GU |
R3‑184807 | Support of Multiple connectivity and fast link switch for IAB | Huawei | imported from 3GU |
R3‑184808 | Discussion on Group Communication | Huawei | imported from 3GU |
R3‑184809 | Further consideration on IE type of NRB in Served cell information | NTT DOCOMO, INC. | imported from 3GU |
R3‑184810 | CR on IE type of NRB in Served cell information over X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184811 | CR on IE type of NRB in Served cell information over F1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184812 | Clarification on start/end time stamp for data volume reporting | NTT DOCOMO, INC. | imported from 3GU |
R3‑184813 | CR for Clarification of start or end timing for data volume reporting on TS36.413 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184814 | CR for Clarification of start or end timing for data volume reporting on TS36.423 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184815 | Delivery confirmation of RRC connection release over F1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184816 | CR on delivery confirmation of RRC connection release over F1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184817 | (TP for TS 38.401)Clarification of full configuration over CU-DU split | NTT DOCOMO, INC. | imported from 3GU |
R3‑184818 | CR on clarification of successfully delivered for NR-U | NTT DOCOMO, INC. | imported from 3GU |
R3‑184819 | CR on clarification of successfully delivered for X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184820 | Partial success on SgNB initiated SgNB Modification over X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184821 | CR on clarification of partial success on SgNB initiated SgNB Modification over X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184822 | Solution on load management for NSA | NTT DOCOMO, INC. | imported from 3GU |
R3‑184823 | CR on Introduction of Load management for NSA over F1 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184824 | CR on Introduction of Load management for NSA over X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑184825 | Further discussions on RAN initiated TNL Associations over NGAP | Huawei, Intel Corporation | imported from 3GU |
R3‑184826 | (TP for NR BL CR for TS 38.412): RAN initiated TNL Associations over NGAP | Huawei, Intel Corporation | imported from 3GU |
R3‑184827 | (TP for NR BL CR for TS 38.413): RAN initiated TNL Associations over NGAP | Huawei, Intel Corporation | imported from 3GU |
R3‑184828 | (TP for NR BL CR for TS 38.413): Clarification on weight factor | Huawei, Intel Corporation | imported from 3GU |
R3‑184829 | [Draft] Reply LS on RAN initiated TNL Associations over NGAP | Huawei | imported from 3GU |
R3‑184830 | [TP for NR BL CR for TS 38.413] Including PDU Session ID in UE Context Release Complete | Huawei | imported from 3GU |
R3‑184831 | [TP for NR BL CR for TS 38.413] Including PDU Session ID in UE Context Release Request | Huawei | imported from 3GU |
R3‑184832 | (TP for NR BL CR for TS 38.423): Transfer of Notification Control Status during Xn based Handover | Huawei | imported from 3GU |
R3‑184833 | (TP for NR BL CR for TS 38.413): Transfer of Notification Control Status during NG based Handover | Huawei | imported from 3GU |
R3‑184834 | (TP for NR BL CR for TS 38.413): Transfer of Notification Control Status during NG based Handover | Huawei | imported from 3GU |
R3‑184835 | Pending Data Indication in S1AP | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑184836 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑184837 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑184838 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑184839 | Additional CP protocol stack for architecture 1a | Samsung | imported from 3GU |
R3‑184840 | Harmonization of CP protocol stack for Alt. 1 and 3 for Architecture 1a | Samsung | imported from 3GU |
R3‑184841 | Control plane data mapping for architecture 1a | Samsung | imported from 3GU |
R3‑184842 | F1AP mapping options for IAB | Samsung | imported from 3GU |
R3‑184843 | Overview of flow control solutions for architecture 1 and 2 | Samsung | imported from 3GU |
R3‑184844 | IAB topology and route management | Samsung | imported from 3GU |
R3‑184845 | IAB failure recovery as part of route management | Samsung | imported from 3GU |
R3‑184846 | (TP for NR BL CR for TS38.473) Discussions on RLC-Failure | Samsung | imported from 3GU |
R3‑184847 | (TP for NR BL CR for TS 38.423): Support of DRB offloading and QoS Flow offloading | Samsung | imported from 3GU |
R3‑184848 | (TP for NR BL CR for TS 37.340): DC establishment for PDCP Termination at SN | Samsung | imported from 3GU |
R3‑184849 | (TP for NR BL CR for TS 38.423): DC establishment for PDCP Termination at SN | Samsung | imported from 3GU |
R3‑184850 | Corrections for th misaligned usage of the Maximum MCG admittable E-RAB Level QoS Parameters IE | Samsung | imported from 3GU |
R3‑184851 | (TP for NR BL CR for TS 38.423): Correction of the reference for RRC container | Samsung | imported from 3GU |
R3‑184852 | (TP for NR BL CR for TS 38.413): Security Information Transmission for HO | Samsung | imported from 3GU |
R3‑184853 | (TP for NR BL CR for TS 38.423): Security Information Transmission for HO | Samsung | imported from 3GU |
R3‑184854 | Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., Intel Corporation | imported from 3GU |
R3‑184855 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung, KT Corp., Intel Corporation | imported from 3GU |
R3‑184856 | (TP for NR BL CR for TS 37.340) Direct data forwarding in eNB/gNB to Master Node change | Samsung | imported from 3GU |
R3‑184857 | (TP for NR BL CR for TS 38.423) Correction of Semantics description on Integrity protection IE in RETRIEVE UE CONTEXT REQUEST message | Samsung | imported from 3GU |
R3‑184858 | Extend the RANAC size to 8bits | Samsung | imported from 3GU |
R3‑184859 | Extend the RANAC size to 8bits | Samsung | imported from 3GU |
R3‑184860 | CR to 38.473 on further clarifications on System information transfer over F1 | Huawei | imported from 3GU |
R3‑184861 | CR to 38.473 on corrections to System information delivery | Huawei | imported from 3GU |
R3‑184862 | CR to 38.473 on UE Identity Index value | Huawei | imported from 3GU |
R3‑184863 | CR to 38.473 on PDCP SN over F1 interface | Huawei | imported from 3GU |
R3‑184864 | Separate DL and UL Flow to DRB mapping in Handover | Huawei | imported from 3GU |
R3‑184865 | (TP for NR BL CR for TS 38.300): Correction on Data forwarding over PDU session tunnel | Huawei | imported from 3GU |
R3‑184866 | (TP for NR BL CR for TS 38.473) RANAC value correction | Google Inc. | imported from 3GU |
R3‑184867 | QoS Management of IAB nodes | Huawei | imported from 3GU |
R3‑184868 | TS 37.470 v0.2.0: W1 general aspects and principles | China Unicom | imported from 3GU |
R3‑184869 | TS 37.471 v0.2.0: W1 layer 1 | China Unicom | imported from 3GU |
R3‑184870 | Load management over F1 | Huawei | imported from 3GU |
R3‑184871 | (TP for NR BL CR for TS 38.410) Load management over F1 | Huawei | imported from 3GU |
R3‑184872 | (TP for NR BL CR for TS 38.413) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑184873 | (TP for NR BL CR for TS 38.423) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑184874 | (TP for NR BL CR for TS 38.473)A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑184875 | (TP for NR BL CR for TS 38.463) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑184876 | (TP for NR BL CR for TS 38.423) Slice not supported cause value | Huawei | imported from 3GU |
R3‑184877 | (TP for NR BL CR for TS 38.413) NG overload | Huawei | imported from 3GU |
R3‑184878 | (TP for NR BL CR for TS 38.410) NG overload | Huawei | imported from 3GU |
R3‑184879 | (TP for NR BL CR for TS 38.413) Allowed NSSAI in DL NAS | Huawei | imported from 3GU |
R3‑184880 | (TP for NR BL CR for TS 38.413) Slice information in paging | Huawei | imported from 3GU |
R3‑184881 | [draft] Reply LS on Allowed NSSAI and Requested NSSAI | Huawei | imported from 3GU |
R3‑184882 | Corrections of Choice | Huawei | imported from 3GU |
R3‑184883 | Correction of TNL criticality | Huawei | imported from 3GU |
R3‑184884 | Corrections of usage of single container | Huawei | imported from 3GU |
R3‑184885 | (TP for NR BL CR for TS 38.423) RRC config indication in XnAP | imported from 3GU | |
R3‑184886 | TS 37.472 v0.1.0: W1 signalling transport | China Unicom | imported from 3GU |
R3‑184887 | (TP for NR BL CR for TS 38.423) S-Node reconfiguration complete | imported from 3GU | |
R3‑184888 | TS 37.473 v0.1.0: W1 Application Protocol (E1AP) | China Unicom | imported from 3GU |
R3‑184889 | (TP for NR BL CR for TS 38.423) UE Context Release to S-Node | Google Inc. | imported from 3GU |
R3‑184890 | (TP for NR BL CR for TS 38.463) Further Discussion on Counter Check in CU-CP UP Separation | LG Electronics UK | imported from 3GU |
R3‑184891 | Discussion on inclusion of NSSAI in paging messages | Ericsson | imported from 3GU |
R3‑184892 | Reply LS on inclusion of NSSAI in RRC connection establishment procedure | Ericsson | imported from 3GU |
R3‑184893 | (TP for NR BL CR for TS 38.413): Correction of Area of Interest IE in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184894 | (TP for NR BL CR for TS 38.423): Correction of Area of Interest IE in XnAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184895 | IAB Routing for Architecture 2a | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184896 | Topology Adaptation Scenarios | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson | imported from 3GU |
R3‑184897 | IAB Topology Discovery for Routing and Topology Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184898 | Architectural key issues to be considered for NTN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184899 | (TP for NR BL CR for TS 38.423) on band width info over Xn | Huawei | imported from 3GU |
R3‑184900 | RLC failure notification over F1 | Huawei | imported from 3GU |
R3‑184901 | CR to 38.473 on RLC failure notification over F1 | Huawei | imported from 3GU |
R3‑184902 | Bearer type change indication over F1 | Huawei | imported from 3GU |
R3‑184903 | CR to 38.473 on Bearer type change indication over F1 | Huawei | imported from 3GU |
R3‑184904 | RRC version handling over F1 | Huawei | imported from 3GU |
R3‑184905 | CR to 38.473 on RRC version handling over F1 | Huawei | imported from 3GU |
R3‑184906 | CR to 38.473 on Paging DRX cycle over F1 | Huawei | imported from 3GU |
R3‑184907 | Discussion on RRC re-establishment in case of RAN sharing | Huawei | imported from 3GU |
R3‑184908 | (TP for NR BL CR for 38.423) on the clarification to RAN sharing and RRC re-establishment | Huawei | imported from 3GU |
R3‑184909 | CR to 36.423 on the clarification to RAN sharing and RRC re-establishment | Huawei | imported from 3GU |
R3‑184910 | CR to 38.473 on the clarification to RAN sharing | Huawei | imported from 3GU |
R3‑184911 | (TP for NR BL for 38.473): on supported PLMN over F1 | Huawei | imported from 3GU |
R3‑184912 | (TP for NR BL CR for TS 38.460): on capacity information transfer via E1 interface | Huawei | imported from 3GU |
R3‑184913 | (TP for NR BL CR for TS 38.463): on capacity information transfer via E1 interface | Huawei | imported from 3GU |
R3‑184914 | (TP for NR BL CR for TS 38.463): on clarification to inactivity monitoring over E1 | Huawei | imported from 3GU |
R3‑184915 | (TP for NR BL CR for TS 38.460) on notification of GBR QoS Flow | Huawei | imported from 3GU |
R3‑184916 | (TP for NR BL CR for TS 38.463) on notification of GBR QoS Flow | Huawei | imported from 3GU |
R3‑184917 | On IAB topology and routing management | Intel Corporation | imported from 3GU |
R3‑184918 | On maximum Information Element size on network interfaces | Intel Corporation | imported from 3GU |
R3‑184919 | [DRAFT] Reply LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | Intel Corporation [To be RAN3] | imported from 3GU |
R3‑184920 | (TP for NR BL CR for TS 38.413): Correction to location reporting procedure | Huawei | imported from 3GU |
R3‑184921 | (TP for NR BL CR for TS 38.423): Corrections to location reporting Information on Xn | Huawei | imported from 3GU |
R3‑184922 | Proposed work plan | THALES | imported from 3GU |
R3‑184923 | Conclusion on Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184924 | (TP for NR BL CR for TS 38.423): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184925 | (TP for NR BL CR for TS 38.463): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184926 | (TP for NR BL CR for TS 38.413): Source TEID Reuse for handover | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184927 | Further discussion of NG overload | Huawei | imported from 3GU |
R3‑184928 | TP to TR 38.874 on IAB architecture requirements for CP message transport | Ericsson | imported from 3GU |
R3‑184929 | TP to TR 38.874 on comparison of CP alternatives of architecture 1a | Ericsson | imported from 3GU |
R3‑184930 | TP to TR 38.874 on QoS Handling for the Adaptation layer above RLC layer | Ericsson | imported from 3GU |
R3‑184931 | TP to TR 38.874 on setup procedure for the Adaptation layer of an IAB network | Ericsson | imported from 3GU |
R3‑184932 | TP to TR 38.874 on IAB node access procedure for architecture group 1 | Ericsson | imported from 3GU |
R3‑184933 | TP to TR 38.874 on flow control in multi-hop IAB networks | Ericsson | imported from 3GU |
R3‑184934 | TP to TR 38.874 on support for multiple path redundancy for IAB nodes | Ericsson, AT&T, KDDI | imported from 3GU |
R3‑184935 | TP to TR 38.874 on using F1 functionality to support redudant paths | Ericsson, AT&T, KDDI | imported from 3GU |
R3‑184936 | (TP for NR BL CR for TS 38.413) Corrections to UE Radio Capability for Paging | Datang Mobile Com. Equipment | imported from 3GU |
R3‑184937 | 5G band management and Iuant interface | Huawei | imported from 3GU |
R3‑184938 | [Draft] Antenna Interface Function support in 5G | Huawei | imported from 3GU |
R3‑184939 | Discussion on Non Terrestrial Network | Huawei | imported from 3GU |
R3‑184940 | Discussion on Mobility of Non Terrestrial Network | Huawei | imported from 3GU |
R3‑184941 | Enabling multiple SCTP associations for X2 and Xn | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184942 | (TP for NR BL CR for TS 38.413): Correction of Handover Resource Allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184943 | Correction of incorrect acronym introduced in QMC support for MTSI service type in UTRAN | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑184944 | Data forwarding aspects for intra-system ACTIVE mobility | Ericsson | imported from 3GU |
R3‑184945 | Addition of MCG cell ID to solve the PCI confusion at SN | Ericsson | imported from 3GU |
R3‑184946 | PDU Session Split at UPF | Ericsson | imported from 3GU |
R3‑184947 | Support of Multiple TNL addresses at NG-RAN node | Ericsson | imported from 3GU |
R3‑184948 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson, Vodafone | imported from 3GU |
R3‑184949 | Introduction of UL AMBR on F1 | Ericsson | imported from 3GU |
R3‑184950 | Multiple TNLA over F1 | Ericsson | imported from 3GU |
R3‑184951 | Multiple port numbers | Ericsson | imported from 3GU |
R3‑184952 | NAS Non-delivery in higher layer split deployments | Ericsson | imported from 3GU |
R3‑184953 | RLC mode indication over F1 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
R3‑184954 | RLC mode indication over X2 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
R3‑184955 | Introduction of EN-DC | Ericsson | imported from 3GU |
R3‑184956 | Data forwarding handling between 4G and 5G | Ericsson | imported from 3GU |
R3‑184957 | Data Forwarding – Common Aspects | Ericsson | imported from 3GU |
R3‑184958 | TP for BL CR for 38.300 for inter-system HO | Ericsson | imported from 3GU |
R3‑184959 | Data forwarding aspects for DC bearer type change and QoS flow offloading | Ericsson | imported from 3GU |
R3‑184960 | Data forwarding aspects for intra-system ACTIVE mobility | Ericsson | imported from 3GU |
R3‑184961 | [DRAFT] LS on data forwarding for intra and inter-system HO | Ericsson | imported from 3GU |
R3‑184962 | Introducing SN initiated SN Change procedure in XnAP | Ericsson | imported from 3GU |
R3‑184963 | Enabling re-use of NR PCIs in cells served by the same gNB in MR-DC | Ericsson | imported from 3GU |
R3‑184964 | Handling of PDCP Duplication on Xn | Ericsson | imported from 3GU |
R3‑184965 | Correction for PDCP Duplication | Ericsson | imported from 3GU |
R3‑184966 | Reviewing Restructured DC messages for MN iniated procedures – TP for 38.423 | Ericsson | imported from 3GU |
R3‑184967 | How to apply principle of resturctured DC messages on SN initiated procedures – TP for 38.423 | Ericsson | imported from 3GU |
R3‑184968 | (TP for NR BL CR for TS 37.340): Support of SN initiated QoS flow offload | Ericsson | imported from 3GU |
R3‑184969 | (TP for NR BL CR for TS 37.340): QoS flow mapping information for SN terminated bearers – MR-DC with 5GC | Ericsson | imported from 3GU |
R3‑184970 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
R3‑184971 | Establishing a second NG-U tunnel for a PDU Session | Ericsson | imported from 3GU |
R3‑184972 | PDU Session Split at UPF | Ericsson | imported from 3GU |
R3‑184973 | Correction of RRC Transfer procedure – TP for 38.423 | Ericsson | imported from 3GU |
R3‑184974 | Differences between LTE and NR RRC | Ericsson | imported from 3GU |
R3‑184975 | Introduction of the UE differentiation Information | Ericsson, Vodafone, Huawei | imported from 3GU |
R3‑184976 | Discussion on signalling based Bluetooth/WLAN measurement collection in MDT(LTE) | Ericsson | imported from 3GU |
R3‑184977 | Initial Considerations on NTN Architecture | Ericsson | imported from 3GU |
R3‑184978 | Network Identities for Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑184979 | Considerations on Mobility in Non-Terrestrial Networks | Ericsson | imported from 3GU |
R3‑184980 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑184981 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑184982 | UE AMBR monitoring and enforcement | Ericsson | imported from 3GU |
R3‑184983 | RRC Version Handling over F1 | Ericsson | imported from 3GU |
R3‑184984 | RRC Version Handling | Ericsson | imported from 3GU |
R3‑184985 | PLMN information over F1 | Ericsson | imported from 3GU |
R3‑184986 | Overload Handling over F1-C | Ericsson | imported from 3GU |
R3‑184987 | Introduction of Overload Handling in F1-C | Ericsson | imported from 3GU |
R3‑184988 | Correction on cell management | Ericsson | imported from 3GU |
R3‑184989 | Correction on cell management | Ericsson | imported from 3GU |
R3‑184990 | Parallel non-UE-associated procedures on E1 | Ericsson | imported from 3GU |
R3‑184991 | Capactiy Information over E1 | Ericsson | imported from 3GU |
R3‑184992 | Support of multiple TNLAs on NG-C | Ericsson | imported from 3GU |
R3‑184993 | Support of Multiple TNL addresses at NG-RAN node | Ericsson | imported from 3GU |
R3‑184994 | [DRAFT] LS Definition of TNLA weight factor in the light of supporting multiple control plane TNL end point addresses at an NG-RAN node | Ericsson | imported from 3GU |
R3‑184995 | Option 3 ANR - Discussion on indicating NSA support | Ericsson | imported from 3GU |
R3‑184996 | [DRAFT] reply LS on RAN2 progress on ANR | Ericsson | imported from 3GU |
R3‑184997 | Remove 5G TAC | Ericsson | imported from 3GU |
R3‑184998 | Option 3 ANR - X2 connectivity across MME pools for EN-DC | Ericsson | imported from 3GU |
R3‑184999 | [DRAFT] LS on X2 TNL Address discovery for EN-DC across MME borders | Ericsson | imported from 3GU |
R3‑185000 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
R3‑185001 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
R3‑185002 | Introducing X2 TNL Address discovery for en-gNBs for EN-DC | Ericsson | imported from 3GU |
R3‑185003 | On signalling of dynamic 5QI values | Ericsson | imported from 3GU |
R3‑185004 | On signalling of dynamic 5QI values, XnAP | Ericsson | imported from 3GU |
R3‑185005 | On signalling of dynamic 5QI values, E1AP | Ericsson | imported from 3GU |
R3‑185006 | On signalling of dynamic 5QI values, F1AP | Ericsson | imported from 3GU |
R3‑185007 | Correction on UE AMBR | Ericsson | imported from 3GU |
R3‑185008 | Correction on UE AMBR on XnAP | Ericsson | imported from 3GU |
R3‑185009 | Correction on UE AMBR on E1AP | Ericsson | imported from 3GU |
R3‑185010 | Correction on PDU Session AMBR | Ericsson | imported from 3GU |
R3‑185011 | Correction on PDU Session AMBR on XnAP | Ericsson | imported from 3GU |
R3‑185012 | Correction on PDU Session AMBR on E1AP | Ericsson | imported from 3GU |
R3‑185013 | Introducing PDU Session AMBR over F1 | Ericsson | imported from 3GU |
R3‑185014 | Correction when TNL information is modified at NGAP | Ericsson | imported from 3GU |
R3‑185015 | CSI-RS Configuration Transfer | Ericsson | imported from 3GU |
R3‑185016 | Correction F1 Setup request | Ericsson | imported from 3GU |
R3‑185017 | Correction C-RNTI format | Ericsson | imported from 3GU |
R3‑185018 | Multiple TNLA over F1 | Ericsson | imported from 3GU |
R3‑185019 | Multiple TNLA over F1 - stage2 | Ericsson | imported from 3GU |
R3‑185020 | Multiple SCTP port numbers over F1 | Ericsson | imported from 3GU |
R3‑185021 | NAS Non-delivery in higher layer split deployments | Ericsson | imported from 3GU |
R3‑185022 | PLMN information on E1 | Ericsson | imported from 3GU |
R3‑185023 | gNB-CU-UP connection status | Ericsson | imported from 3GU |
R3‑185024 | Inactivity timer on E1 | Ericsson | imported from 3GU |
R3‑185025 | Clarification on new UL TEI request | Ericsson | imported from 3GU |
R3‑185026 | More consideration on Criticality handling related to SMF Ies | Ericsson | imported from 3GU |
R3‑185027 | Including the missing Allowed NSSAI in Initial UE Message | Ericsson | imported from 3GU |
R3‑185028 | Including the missing Allowed NSSAI in Initial UE Message | Ericsson | imported from 3GU |
R3‑185029 | The Maximum Data Burst Volume presence discussion | Ericsson | imported from 3GU |
R3‑185030 | Correction on PDU Session Resource Modify | Ericsson | imported from 3GU |
R3‑185031 | Including QoS flow information in Handover Required Transfer | Ericsson | imported from 3GU |
R3‑185032 | Discussion on Path Switch Request Failure related to SMF IE | Ericsson | imported from 3GU |
R3‑185033 | Clarification on NRARFCN semantics – TP for X2AP | Ericsson | imported from 3GU |
R3‑185034 | Clarification on NRARFCN semantics – TP for XnAP | Ericsson | imported from 3GU |
R3‑185035 | Clarification on NRARFCN semantics – TP for F1AP | Ericsson | imported from 3GU |
R3‑185036 | Introducing of SCS in NR Transmission Bandwidth and ^^SS Block SCS in Served NR Cell Information | Ericsson | imported from 3GU |
R3‑185037 | Introducing SS Block SCS in Served NR Cell Information | Ericsson | imported from 3GU |
R3‑185038 | Introducing SS Block SCS in Served NR Cell Information | Ericsson | imported from 3GU |
R3‑185039 | RLC mode indication over X2 and F1 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
R3‑185040 | RLC mode indication over XN | Ericsson | imported from 3GU |
R3‑185041 | RLC mode indication over E1 | Ericsson | imported from 3GU |
R3‑185042 | L2 Measurements for NG-RAN | Ericsson | imported from 3GU |
R3‑185043 | Reply LS on L2 Measurements for NG-RAN | Ericsson | imported from 3GU |
R3‑185044 | Clarification on SCTP association establishment – for 36.300 | Ericsson, NTT DOCOMO, INC., KT | imported from 3GU |
R3‑185045 | Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – HO aspects | Ericsson, Vodafone, KT, Intel, Qualcomm | imported from 3GU |
R3‑185046 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.300 | Ericsson | imported from 3GU |
R3‑185047 | Support of keeping the DL UP termination point on the RAN-CN interface at inter-RAN node bearer mobility – DC aspects | Ericsson, Vodafone, KT, Intel, Qualcomm | imported from 3GU |
R3‑185048 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.413 | Ericsson | imported from 3GU |
R3‑185049 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.423 | Ericsson | imported from 3GU |
R3‑185050 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.413 | Ericsson | imported from 3GU |
R3‑185051 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.423 | Ericsson | imported from 3GU |
R3‑185052 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 36.300 | Ericsson | imported from 3GU |
R3‑185053 | Support of keeping the DL UP termination point on the RAN-CN interface at handover – for 38.463 | Ericsson | imported from 3GU |
R3‑185054 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
R3‑185055 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
R3‑185056 | Support for keeping a stable PDCP anchor at bearer type change or MN change or SN change | Ericsson | imported from 3GU |
R3‑185057 | Rapporteur Update for BL CR for TS 38.463 | Ericsson | imported from 3GU |
R3‑185058 | Rapporteur CR for TS 38.455 | Ericsson | imported from 3GU |
R3‑185059 | Further discussion on TNL address discovery for EN-DC | Qualcomm Incorporated | imported from 3GU |
R3‑185060 | (TP for NR BL CR for TS 38.413) Introduction of NAS Security parameters for handover to E-UTRAN | Qualcomm Incorporated | imported from 3GU |
R3‑185061 | LTE cell information in the gNB-DU for LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185062 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185063 | MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185064 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185065 | RAN3-100Bis meeting Report | MCC | imported from 3GU |
R3‑185066 | (TP for NR BL CR for TS 38.300): Corrections on RNA update procedure | LG Electronics | imported from 3GU |
R3‑185067 | (TP for NR BL CR for TS 38.300): Behavior of NG-RAN upon reception of NG Reset message in RRC_INACTIVE | LG Electronics | imported from 3GU |
R3‑185068 | (TP for NR BL CR for TS 38.413): Further discussions on RRC inactive transition report | LG Electronics | imported from 3GU |
R3‑185069 | (TP for NR BL CR for TS 38.401): Correction for early provision of F1-U gNB-DU DL TNL addresses from gNB-CU-CP to gNB-CU-UP | Intel Corporation | imported from 3GU |
R3‑185070 | (TP for NR BL CR for TS 38.463): Correction for DL forwarding over PDU session tunnel | Intel Corporation | imported from 3GU |
R3‑185071 | (TP for NR BL CR for TS 38.425): Correction for the handover issues in a separated CP/UP deployment | Intel Corporation | imported from 3GU |
R3‑185072 | (TP for NR BL CR for TS 38.425): Flow Control for DL QoS flow remapping | Intel Corporation, Samsung, KT Corp. | imported from 3GU |
R3‑185073 | (TP for NR BL CR for TS 38.423): Unique DRB ID assignment between MN and SN | Intel Corporation | imported from 3GU |
R3‑185074 | New TS-37.474-skeleton | China Unicom | imported from 3GU |
R3‑185075 | Discussion on W1 interface stage 2 functions description | China Unicom | imported from 3GU |
R3‑185076 | (TP for NR BL CR for TS 38.410): Overload Control in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185077 | Rapporteur update for TS 37.473 v0.0.1 | China Unicom | imported from 3GU |
R3‑185078 | Introduce Bluetooth and WLAN measurement Collection Support in LTE MDT | CMCC, Huawei, ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185079 | CR to S1AP to introduce Bluetooth and WLAN measurement in MDT | CMCC, Huawei, ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185080 | CR to X2AP to introduce Bluetooth and WLAN measurement in MDT | CMCC, Huawei, ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185081 | Further discussion on data forwarding tunnelling for inter-system handover | CMCC | imported from 3GU |
R3‑185082 | Further discussion on data forwarding tunnelling for inter-system handover | CMCC | imported from 3GU |
R3‑185083 | (TP for NR BL CR for TS 38.401) Cell management over F1 | CMCC | imported from 3GU |
R3‑185084 | CR to 38.473 on disable of SRB PDCP duplication | HUAWEI Technologies Japan K.K. | imported from 3GU |
R3‑185085 | (TP for NR BL CR for TS 38.401): on Context management for inactive over F1 | Huawei | imported from 3GU |
R3‑185086 | (TP for NR BL CR for TS 38.473): on Context management for inactive over F1 | Huawei | imported from 3GU |
R3‑185087 | (TP for NR BL CR for TS 38.473): on cause value of UE rejection | Huawei | imported from 3GU |
R3‑185088 | Discussion on emergency call in case of gNB-DU congestion | Huawei | imported from 3GU |
R3‑185089 | CR to 38.473 on Emergency call in case of gNB-DU congestion | Huawei | imported from 3GU |
R3‑185090 | (TP for NR BL CR for TS 38.473): on presence of QoS information | Huawei | imported from 3GU |
R3‑185091 | (TP for NR BL CR for TS 38.463): on PLMN over E1-C UE associated signalling | Huawei | imported from 3GU |
R3‑185092 | (TP for NR BL CR for TS 38.463): PLMN over E1-C non-UEassociated signalling | Huawei | imported from 3GU |
R3‑185093 | (TP for NR BL CR for TS 38.473): on correction to RRC re-establishment on F1 | Huawei | imported from 3GU |
R3‑185094 | (TP for NR BL CR for TS 38.401): on correction to RRC re-establishment on F1 | Huawei | imported from 3GU |
R3‑185095 | (TP for NR BL CR for TS 38.473): on clarification to INITIAL UL RRC MESSAGE TRANSFER procedure | Huawei | imported from 3GU |
R3‑185096 | CR to 38.473 on correction to PWS System Information | Huawei | imported from 3GU |
R3‑185097 | Efficient Handling of Large UE Radio Capability Information At Inter-RAT and SRVCC Handover Scenarios | Vodafone | imported from 3GU |
R3‑185098 | Response to R3-184988 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185099 | Response to R3-185000, R3-185001, R3-185002, R3-184948, R3-184673, R3-184674, R3-184675, R3-184676, R3-184677, R3-184605, R3-184751, R3-184752, R3-185059, R3-184998, R3-184999, R3-184678 and R3-184679^^ (Summary of contributions on TNL Address Discov | NTT DOCOMO INC. | imported from 3GU |
R3‑185100 | Response to R3-184440 | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
R3‑185101 | Response to R3-184891 | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185102 | Rapporteur CR for TS 38.455 | Ericsson | imported from 3GU |
R3‑185103 | Antenna Interface Function support in 5G | Huawei | imported from 3GU |
R3‑185104 | Reply LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | Intel Corporation | imported from 3GU |
R3‑185105 | (TP for NR BL CR for TS 38.423): further correction to I-RNTI | NEC | imported from 3GU |
R3‑185106 | Reply LS on Issues with AS Release Assistance Indicator | Huawei | imported from 3GU |
R3‑185107 | Data forwarding and end marker handling for inter-system HO | Samsung, KT Corp., Intel Corporation, CMCC, Verizon, LG Electronics Inc., CATT | imported from 3GU |
R3‑185108 | (TP for NR BL CR for TS 38.300): End marker handling | Samsung, KT Corp., Intel Corporation, CMCC, Verizon, LG Electronics Inc., CATT | imported from 3GU |
R3‑185109 | Clarification on SCTP association establishment – for 36.300 | Ericsson, NTT DOCOMO, INC., KT, -^^Vodafone, Deutsche Telekom, Orange | imported from 3GU |
R3‑185110 | NB IoT Session report | Vice chairman (Intel) | imported from 3GU |
R3‑185111 | MDT Session report | Vice chairman (ZTE) | imported from 3GU |
R3‑185112 | on Access Restriction Data for NR in EPC | Huawei | imported from 3GU |
R3‑185113 | Access Restriction Data for NR in EPC | Huawei | imported from 3GU |
R3‑185114 | Reply LS to SA5 on L2 measurements | Ericsson | imported from 3GU |
R3‑185115 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑185116 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑185117 | Pending Data Indication | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
R3‑185118 | Correction on Authentication Failure handling in case of eNB CP Relocation | Huawei | imported from 3GU |
R3‑185119 | Correction on Authentication Failure handling in case of eNB CP Relocation | Huawei | imported from 3GU |
R3‑185120 | Introduction of NPRS enhancement | Huawei | imported from 3GU |
R3‑185121 | Introduction of NPRS enhancement | Huawei | imported from 3GU |
R3‑185122 | Introduction of release 14 eMBMS enhancements | Qualcomm Incorporated | imported from 3GU |
R3‑185123 | Introduction of Warning Area Coordinates in S1AP: WRITE-REPLACE WARNING REQUEST | Nokia, Nokia Shanghai Bell, AT&T, One2many, Qualcomm Incorporated, Sprint, SyncTechno Inc., T-Mobile USA | imported from 3GU |
R3‑185124 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑185125 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑185126 | (TP for NR BL CR for TS 38.410): Rapporteur’s updates for TS 38.410. | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185127 | (TP for NR BL CR for TS 38.415): Further Correction of TS 38415. | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185128 | (TP for NR BL CR for TS 38.420) Rapporteur updates for TS 38.420 | Qualcomm Incorporated | imported from 3GU |
R3‑185129 | Rapporteur’s CR for E1 Stage 2 Corrections for NR | Nokia (Rapporteur) | imported from 3GU |
R3‑185130 | Response to R3-184440 | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange, Verizon Wireless | imported from 3GU |
R3‑185131 | (TP to TR 38.423):Extend the RANAC size to 8bits | Samsung | imported from 3GU |
R3‑185132 | Extend the RANAC size to 8bits | Samsung | imported from 3GU |
R3‑185133 | (TP for NR BL CR for TS 38.413): Correction of Release inactive to idle | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185134 | (TP for NR BL CR for TS 38.423): Correction of Release inactive to idle | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185135 | Further Discussion on RRC_INACTIVE Behaviours upon Receiving NG Reset | ZTE | imported from 3GU |
R3‑185136 | (TP for NR BL CR for TS 38.300) Refinement of the stage 2 RRC-Inactive Mobility section | Qualcomm Incorporated | imported from 3GU |
R3‑185137 | (TP for NR BL CR for TS 36.413): Correction of data volume report | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185138 | (TP for NR BL CR for TS 36.423): Correction of data volume report | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185139 | (TP for NR BL CR for TS 37.340) Corrections on secondary RAT data volume reporting | Huawei | imported from 3GU |
R3‑185140 | Summary of offline discussion on Data Volume Reporting in 5G/NG-RAN | Qualcomm | imported from 3GU |
R3‑185141 | (TP for NR BL CR for TS 38.423) on band width info over Xn | Huawei | imported from 3GU |
R3‑185142 | (TP for NR BL CR for TS38.423) ANR | Huawei | imported from 3GU |
R3‑185143 | Corrections of MeNB/SgNB resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185144 | Corrections on resource coordination in stage-2 | Huawei | imported from 3GU |
R3‑185145 | LS on releasing UE from Inactive to Idle | Nokia | imported from 3GU |
R3‑185146 | (TP for NR BL CR for TS 36.300): [SON/ANR] Stage 2 updates | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185147 | (TP for NR BL CR for TS 38.423) Correction of UE Context Id for Retrieval | ZTE | imported from 3GU |
R3‑185148 | (TP for NR BL CR for TS 38.423) Corrections on RAN Paging Area with Multiple PLMN | ZTE | imported from 3GU |
R3‑185149 | TP for TS 38.463 Correction to RNAU with anchor change | CATT | imported from 3GU |
R3‑185150 | (TP for NR BL CR for TS 38.413) Cause value for release due to CN-visible mobility | Qualcomm Incorporated | imported from 3GU |
R3‑185151 | (TP for NR BL CR for TS 38.413): Further discussions on RRC inactive transition report | LG Electronics | imported from 3GU |
R3‑185152 | Topology Adaptation Scenarios | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei, Ericsson | imported from 3GU |
R3‑185153 | Multi-connectivity Architecture Design for IAB Arch. 1a | AT&T | imported from 3GU |
R3‑185154 | RRC Version Handling | Ericsson | imported from 3GU |
R3‑185155 | (TP for NR BL for 38.473): on supported PLMN over F1 | Huawei | imported from 3GU |
R3‑185156 | Introduction of Overload Handling in F1-C | Ericsson | imported from 3GU |
R3‑185157 | (TP for NR BL CR for TS 38.401): Cell Status when failed to active | NEC | imported from 3GU |
R3‑185158 | Summary of Offiline discussion on Cell Status when failed to active | NEC | imported from 3GU |
R3‑185159 | Summary of offline discussion on data forwarding. | Nokia | imported from 3GU |
R3‑185160 | Summary of offline discussion on Asymetric mapping | Huawei | imported from 3GU |
R3‑185161 | (TP for NR BL CR for TS 37.340) Direct data forwarding in eNB/gNB to Master Node change | Samsung | imported from 3GU |
R3‑185162 | Data forwarding aspects for intra-system ACTIVE mobility | Ericsson | imported from 3GU |
R3‑185163 | Summary of offline discussion on Capacity Indication over E1 | Huawei | imported from 3GU |
R3‑185164 | (TP for NR BL CR for TS 38.413): Overload Control | CATT | imported from 3GU |
R3‑185165 | Summary of offline discussion on RAN initiated TNL Associations over NGAP | Huawei | imported from 3GU |
R3‑185166 | Summary of offline discussions – RLC reestablishment | ZTE | imported from 3GU |
R3‑185167 | (TP for NR BL CR for TS 38.423) Activity Notification Control over Xn | Qualcomm Incorporated | imported from 3GU |
R3‑185168 | (TP for NR BL CR for TS 38.413): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185169 | Summary of offline discussions on CB#42 (TNL Address Discovery for Option 3) | Ericsson | imported from 3GU |
R3‑185170 | IAB Topology Discovery for Routing and Topology Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185171 | Summary of Offline discussion on MAX DATA BURST VOLUME | Ericsson | imported from 3GU |
R3‑185172 | Summary of offline discussion on UE AMBR | Ericsson | imported from 3GU |
R3‑185173 | (TP for NR BL CR for TS 38.413) Clarification of no priority Value in Priority Level IE of ARP | ZTE | imported from 3GU |
R3‑185174 | Introducing PDU Session AMBR over F1 | Ericsson | imported from 3GU |
R3‑185175 | Summary of offline discussion on slicing information in paging messages | Ericsson | imported from 3GU |
R3‑185176 | (TP for NR BL CR for TS 38.413): Correction of signaled allowed NSSAI | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185177 | (TP for NR BL CR for TS 38.413): Including the missing Allowed NSSAI in Initial UE Message | Ericsson | imported from 3GU |
R3‑185178 | (TP for NR BL CR for TS 38.413): UE Interested Slice | Qualcomm Incorporated, CATT | imported from 3GU |
R3‑185179 | LS on Prioritised Use Cases and Requirements for consideration in Rel-16 NR-V2X | 5GAA WG1 | imported from 3GU |
R3‑185180 | Reply LS on RRC Re-establishment security | SA3, Huawei | imported from 3GU |
R3‑185181 | Reply LS on security requirements for RRC connection release | SA3, Huawei | imported from 3GU |
R3‑185182 | LS on NAS parameter for 5GS to EPS handover | SA3, Qualcomm | imported from 3GU |
R3‑185183 | (TP for NR BL CR for TS 38.413) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑185184 | (TP for NR BL CR for TS 38.423) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑185185 | (TP for NR BL CR for TS 38.473) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑185186 | (TP for NR BL CR for TS 38.463) A new cause value for slice resource shortage | Huawei | imported from 3GU |
R3‑185187 | Summary of offline discussion on Notification control | Huawei | imported from 3GU |
R3‑185188 | Summary of offline discussion for CSI-RS Configuration Transfer | Huawei | imported from 3GU |
R3‑185189 | Summary of offline discussion on Maximum Integrity Protection Data Rate | NEC | imported from 3GU |
R3‑185190 | Summary of the offline discussion on support of system information | CATT | imported from 3GU |
R3‑185191 | (TP for TS 38.473) Correction on gNB-CU System Information on F1 | CATT | imported from 3GU |
R3‑185192 | CR to 38.473 on further clarifications on System information transfer over F1 | Huawei | imported from 3GU |
R3‑185193 | (TP for NR BL CR for TS38.473) Discussions on RLC-Failure | Samsung | imported from 3GU |
R3‑185194 | TR to 38.473 BL CR on disable of SRB PDCP duplication | HUAWEI Technologies Japan K.K. | imported from 3GU |
R3‑185195 | Introduction of UE differentiation Information | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
R3‑185196 | Introduction of UE differentiation Information | Huawei, China Telecom, CMCC, Ericsson, Vodafone, China Unicom | imported from 3GU |
R3‑185197 | Introduction of Subscription based UE differentiation | Huawei, China Telecom, CMCC, China Unicom | imported from 3GU |
R3‑185198 | Introduction of Subscription based UE differentiation | Huawei, China Telecom, CMCC, China Unicom | imported from 3GU |
R3‑185199 | Introduction of local RRM based UE differentiation information | Huawei | imported from 3GU |
R3‑185200 | Introduction of local RRM based UE differentiation information | Huawei | imported from 3GU |
R3‑185201 | Introduction of local RRM based UE differentiation information | Huawei | imported from 3GU |
R3‑185202 | Correction of TNL criticality | Huawei | imported from 3GU |
R3‑185203 | CR for TS 38.473 on presence of QoS information | Huawei | imported from 3GU |
R3‑185204 | (TP for NR BL CR for TS 38.473): on Paging DRX cycle over F1 | Huawei | imported from 3GU |
R3‑185205 | Correction C-RNTI format | Ericsson | imported from 3GU |
R3‑185206 | (TP for NR BL CR for TS 38.473) Introduction of C-RNTI in UE Context Modification Response | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185207 | Tx Direct Current Location of UL BWP | NEC | imported from 3GU |
R3‑185208 | (TP for SA BL CR for TS 38.473):Support on DC based PDCP duplication | CATT | imported from 3GU |
R3‑185209 | (TP for NR BL CR for TS 38.473) UL configuration in Initial UL RRC Message Transfer | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185210 | (TP for NR BL CR for TS 38.423): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185211 | CR for TS 38.473: Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185212 | (TP for NR BL CR for TS 38.463): Correction of QoS parameters | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185213 | LS on flow level inter-RAT data forwarding | Nokia | imported from 3GU |
R3‑185214 | (TP for TS 38.401)Clarification of full configuration over CU-DU split | NTT DOCOMO, INC. | imported from 3GU |
R3‑185215 | Correction F1 Setup request | Ericsson | imported from 3GU |
R3‑185216 | LS on Rel-15 LTE UE feature list | RAN1, NTT-Docomo | imported from 3GU |
R3‑185217 | (TP for NR BL CR for TS 38.473): on correction to RRC re-establishment on F1 | Huawei | imported from 3GU |
R3‑185218 | CR for TS 36.423: Correction of SgNB Activity Notification Procedure | ZTE | imported from 3GU |
R3‑185219 | (TP for NR BL CR for TS 36.423) Add Up IE Time to Wait to EN-DC Relevant Failure Messages | ZTE | imported from 3GU |
R3‑185220 | Correction of "Maximum MCG admittable E-RAB Level QoS Parameters" | Qualcomm Incorporated | imported from 3GU |
R3‑185221 | (TP for NR BL CR for TS 37.340) Add Up Stage2 Behaviors for PDCP SN Length Indication | ZTE | imported from 3GU |
R3‑185222 | CR on clarification of partial success on SgNB initiated SgNB Modification over X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑185223 | CR to 38.473 on corrections to System information delivery | Huawei | imported from 3GU |
R3‑185224 | Discussion on W1 interface stage 2 functions description | China Unicom | imported from 3GU |
R3‑185225 | Consideration on eNB CU DU and W1 interface | Huawei | imported from 3GU |
R3‑185226 | Summary of offline discussion on LTE CU-DU definition | Ericsson | imported from 3GU |
R3‑185227 | Summary of offline discussion on W1 User Plane Protocol | Ericsson | imported from 3GU |
R3‑185228 | CR to S1AP to introduce Bluetooth and WLAN measurement in MDT | CMCC, Huawei, ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185229 | CR to X2AP to introduce Bluetooth and WLAN measurement in MDT | CMCC, Huawei, ZTE, Samsung, CATT, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185230 | Way Forward on MeNB/SgNB Resource Coordination | Nokia | imported from 3GU |
R3‑185231 | Corrections on UE-associated LTE/NR resource coordination | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185232 | Correction on PDCP duplication indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185233 | (TP for NR BL CR for TS38.401) Corrections on centrilized retransmission for TS38.401 | ZTE Corporation | imported from 3GU |
R3‑185234 | Proposed skeleton | THALES | imported from 3GU |
R3‑185235 | NTN Overview and scenarios | THALES | imported from 3GU |
R3‑185236 | NTN RAN architecture key issues | THALES | imported from 3GU |
R3‑185237 | LS on Security aspects in EDT | SA3, Ericsson | imported from 3GU |
R3‑185238 | (TP for NR BL CR for TS 38.401) Support of indirect data transmission for split bearer | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185239 | (TP for NR BL CR for TS 38.463) Further Discussion on Counter Check in CU-CP UP Separation | LG Electronics UK | imported from 3GU |
R3‑185240 | (TP for NR BL CR for TS 38.463): Correction for DL forwarding over PDU session tunnel | Intel Corporation | imported from 3GU |
R3‑185241 | (TP for BL CR to TS 38.463): E1 cause value | NEC | imported from 3GU |
R3‑185242 | (TP for NR BL CR for TS 38.413): Correction of Path Swicth Failure | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185243 | (TP for NR BL CR for TS 38.413): Correction of Handover Resource Allocation | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185244 | Correction when TNL information is modified at NGAP | Ericsson | imported from 3GU |
R3‑185245 | (TP for NR BL CR for TS 38.423) Update to area of interest | Huawei | imported from 3GU |
R3‑185246 | (TP for NR BL CR for TS 38.413): Correction of Area of Interest IE in NGAP | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185247 | Reply LS on Data Analytics in SA WG2 NWDAF | SA5, Huawei | imported from 3GU |
R3‑185248 | Summary of offline discussion on RRC re-establishment in case of RAN sharing | Huawei | imported from 3GU |
R3‑185249 | RLC mode indication over F1 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
R3‑185250 | RLC mode indication over X2 | Ericsson, NTT DOCOMO, INC | imported from 3GU |
R3‑185251 | Introducing SS Block SCS in Served NR Cell Information | Ericsson | imported from 3GU |
R3‑185252 | Introducing SS Block SCS in Served NR Cell Information | Ericsson | imported from 3GU |
R3‑185253 | Reply LS on Security aspects of supporting LTE connected to 5GC | SA3, Ericsson | imported from 3GU |
R3‑185254 | (TP for NR BL CR for TS 38.413) Introduction of NAS Security parameters for handover to E-UTRAN | Qualcomm Incorporated | imported from 3GU |
R3‑185255 | Introducing SN initiated SN Change procedure in XnAP | Ericsson | imported from 3GU |
R3‑185256 | Introduction of PDCP data recovery request/PDCP change indication during SN modification procedure | CATT | imported from 3GU |
R3‑185257 | Support of PDCP Duplication on Xn | CATT | imported from 3GU |
R3‑185258 | Correction for PDCP Duplication | Ericsson | imported from 3GU |
R3‑185259 | Enabling re-use of NR PCIs in cells served by the same gNB in MR-DC | Ericsson | imported from 3GU |
R3‑185260 | Reviewing Restructured DC messages for MN iniated procedures – TP for 38.423 | Ericsson | imported from 3GU |
R3‑185261 | (TP for NR BL CR for TS 38.473): Correction of MDBV | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185262 | (TP for NR BL CR for TS 38.463): Correction of MDBV | Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185263 | How to apply principle of resturctured DC messages on SN initiated procedures – TP for 38.423 | Ericsson | imported from 3GU |
R3‑185264 | (TP for NR BL CR for TS 37.340): QoS flow mapping information for SN terminated bearers – MR-DC with 5GC | Ericsson | imported from 3GU |
R3‑185265 | (TP for SA BL CR for TS38.473) Clarification on Cell activation failure | ZTE Corporation | imported from 3GU |
R3‑185266 | (TP for NR BL CR for TS38.473) RLC reestablishment for Solution 2a | ZTE | imported from 3GU |
R3‑185267 | (TP for NR BL CR for TS38.473) RLC reestablishment for Solution 2b | ZTE | imported from 3GU |
R3‑185268 | (TP for NR BL CR for TS 37.340) Handling of Session AMBR for NGEN-DC | LG Electronics, KT Corp. | imported from 3GU |
R3‑185269 | (TP for NR BL CR for TS 38.423) Correction on Session AMBR for MR-DC@5GC | ZTE | imported from 3GU |
R3‑185270 | (TP for NR BL CR for TS 38.423) RRC config indication in XnAP | imported from 3GU | |
R3‑185271 | (TP for NR BL CR for TS 38.413): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185272 | (TP for NR BL CR for TS 38.423): Correction of MDBV | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185273 | (TP for NR BL CR for TS 36.413): Correction of mobility restriction | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185274 | (TP for NR BL CR for TS 36.423): Correction of mobility restriction | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185275 | (TP for NR BL CR for TS 38.413): Maximum Integrity Protected data rate | NEC | imported from 3GU |
R3‑185276 | (TP for NR BL CR for TS 38.423): Maximum Integrity Protected data rate | NEC | imported from 3GU |
R3‑185277 | draftCR to TS 37.340: Corrections of Notification Control Indication | ZTE | imported from 3GU |
R3‑185278 | (TP for NR BL CR for TS 38.423) Corrections of Notification Control Indication | ZTE | imported from 3GU |
R3‑185279 | (TP for NR BL CR for TS 38.423): Correction of the reference for RRC container | Samsung | imported from 3GU |
R3‑185280 | Correction on cell management | Ericsson | imported from 3GU |
R3‑185281 | (TP for NR BL CR for TS 38.423): UE Level Resource Coordination for MR-DC Connected to 5GC | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑185282 | (TP for NR BL CR for TS 38.413): Serving Cell aware for LTE-NR Coordination | Qualcomm Incorporated, NTT DOCOMO, INC., T-Mobile USA | imported from 3GU |
R3‑185283 | Extending the length of E-UTRA-NR Cell Resource Coordination agreement | Ericsson | imported from 3GU |
R3‑185284 | (TP for NR BL CR for TS 38.423): Xn signaling for E-UTRA - NR Cell Resource Coordination | Ericsson | imported from 3GU |
R3‑185285 | TP: CR on clarification of successfully delivered for NR-U | NTT DOCOMO, INC. | imported from 3GU |
R3‑185286 | CR on clarification of successfully delivered for X2 | NTT DOCOMO, INC. | imported from 3GU |
R3‑185287 | IAB failure recovery as part of route management | Samsung | imported from 3GU |
R3‑185288 | (TP for NR BL CR for TS 36.413): Correction of mobility restriction | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185289 | Handling of text proposals for NGAP, XnAP, and E1AP in 4Q2018 | Nokia | imported from 3GU |
R3‑185290 | SoD NB IoT | Huawei | imported from 3GU |
R3‑185291 | (TP for NR BL CR for TS 37.340) Corrections on secondary RAT data volume reporting | Huawei | imported from 3GU |
R3‑185292 | (TP for NR BL CR for TS 38.423) on band width info over Xn | Huawei | imported from 3GU |
R3‑185293 | RRC Version Handling | Ericsson | imported from 3GU |
R3‑185294 | (TP for NR BL CR for TS 37.340) Direct data forwarding in eNB/gNB to Master Node change | Samsung | imported from 3GU |
R3‑185295 | (TP for NR BL CR for TS 38.412): RAN initiated TNL Associations over NGAP | Huawei, Intel Corporation | imported from 3GU |
R3‑185296 | Further Discussion on RRC_INACTIVE Behaviours upon Receiving NG Reset | ZTE | imported from 3GU |
R3‑185297 | (TP for NR BL CR for TS 38.413) Cause value for release due to CN-visible mobility | Qualcomm Incorporated | imported from 3GU |
R3‑185298 | LS on Data Volume Reporting in 5GC | Qualcomm | imported from 3GU |
R3‑185299 | (TP for NR BL CR for TS38.473) RLC reestablishment for Solution 2a | ZTE | imported from 3GU |
R3‑185300 | Summary of the offline discussion on support of system information | CATT | imported from 3GU |
R3‑185301 | IAB Topology Discovery for Routing and Topology Management | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185302 | Summary of offline discussion on Notification control | Huawei | imported from 3GU |
R3‑185303 | Correction on PDCP duplication indication | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185304 | TR 38.821 v0.0.1: skeleton report | THALES | imported from 3GU |
R3‑185305 | Correction F1 Setup request | Ericsson | imported from 3GU |
R3‑185306 | Introduction of PDCP data recovery request/PDCP change indication during SN modification procedure | CATT | imported from 3GU |
R3‑185307 | LS on Data Volume Reporting in 5GC | Qualcomm | imported from 3GU |
R3‑185308 | (TP for NR BL CR for TS 38.413): Overload Control | CATT | imported from 3GU |
R3‑185309 | Consideration on eNB CU DU and W1 interface | Huawei | imported from 3GU |
R3‑185310 | NTN RAN architecture key issues | THALES | imported from 3GU |
R3‑185311 | Extending the length of E-UTRA-NR Cell Resource Coordination agreement | Ericsson | imported from 3GU |
R3‑185312 | IAB failure recovery as part of route management | Samsung | imported from 3GU |
R3‑185313 | Introducing PDU Session AMBR over F1 | Ericsson | imported from 3GU |
R3‑185314 | NR Corrections (36.413 Baseline CR covering RAN3-101 agreements) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185315 | NR Corrections (36.423 Baseline CR covering RAN3-101 agreements) | Ericsson | imported from 3GU |
R3‑185316 | NR Corrections (38.401 Baseline CR covering RAN3-101 agreements) | NEC | imported from 3GU |
R3‑185317 | NR Corrections (38.410 Baseline CR covering RAN3-101 agreements) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185318 | NR Corrections (38.413 Baseline CR covering RAN3-101 agreements) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185319 | NR Corrections (38.415 Baseline CR covering RAN3-101 agreements) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185320 | NR Corrections (38.420 Baseline CR covering RAN3-101 agreements) | Qualcomm Incorporated | imported from 3GU |
R3‑185321 | NR Corrections (38.423 Baseline CR covering RAN3-101 agreements) | Ericsson | imported from 3GU |
R3‑185322 | NR Corrections (38.425 Baseline CR covering RAN3-101 agreements) | Samsung | imported from 3GU |
R3‑185323 | NR Corrections (38.460 Baseline CR covering RAN3-101 agreements) | Nokia (Rapporteur) | imported from 3GU |
R3‑185324 | NR Corrections (38.462 Baseline CR covering RAN3-101 agreements) | Huawei | imported from 3GU |
R3‑185325 | NR Corrections (38.463 Baseline CR covering RAN3-101 agreements) | Ericsson | imported from 3GU |
R3‑185326 | NR Corrections (38.470 Baseline CR covering RAN3-101 agreements) | Huawei | imported from 3GU |
R3‑185327 | NR Corrections (38.472 Baseline CR covering RAN3-101 agreements) | Interdigital Asia LLC | imported from 3GU |
R3‑185328 | NR Corrections (38.473 Baseline CR covering RAN3-101 agreements) | Huawei | imported from 3GU |
R3‑185329 | NR Corrections (37.340 Baseline CR covering RAN3-101 agreements) | ZTE | imported from 3GU |
R3‑185330 | NR Corrections (38.300 Baseline CR covering RAN3-101 agreements) | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185331 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑185332 | Correction C-RNTI format | Ericsson | imported from 3GU |
R3‑185333 | TR 38.821 v0.1.0 | Thales | imported from 3GU |
R3‑185334 | Indication of RLC re-establishment at the gNB-DU | Ericsson-LG Co., LTD | imported from 3GU |
R3‑185335 | NR Corrections (38.412 Baseline CR covering RAN3#101 agreements) | NTT DOCOMO INC. | imported from 3GU |
R3‑185336 | Data forwarding for Retrieve UE Context in case of RRC connection re-establishment | Ericsson | imported from 3GU |
R3‑185337 | Corrections of usage of single container | Huawei | imported from 3GU |
R3‑185338 | (TP for NR BL CR for TS 36.300): [SON/ANR] Stage 2 updates | Nokia, Nokia Shanghai Bell | imported from 3GU |
R3‑185339 | LS on replay protection | 3GPP SA3, Ericsson | imported from 3GU |
R3‑186049 | LS on initial NAS security agreements | 3GPP SA3, Qualcomm | imported from 3GU |
R3‑186050 | LS on RRC Reestablishment during N2 Handover | 3GPP SA3, Huawei | imported from 3GU |
R3‑186051 | LS on the Impacts of increasing the MAC-I and NAS-MAC size | 3GPP SA3, AT&T | imported from 3GU |
page generated from database: 2024-09-26 11:02:35