| TDoc | Title | Source |
|---|---|---|
| R3-235001 | RAN3#121-bis Meeting Agenda | RAN3 Chair |
| TDoc | Title | Source |
|---|---|---|
| R3-235002 | Draft RAN3#121 Meeting Report | ETSI-MCC |
| R3-235697 | RAN3#121 Meeting Report | ETSI-MCC |
| TDoc | Title | Source |
|---|---|---|
| R3-235003 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| TDoc | Title | Source |
|---|---|---|
| R3-235163 | TR 30.531 v1.48.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| TDoc | Title | Source |
|---|---|---|
| R3-235004 | LS on usage of paging subgrouping information in RAN in case of abnormal scenario. | CT1(Huawei) |
| R3-235010 | LS on Rel-18 higher-layers parameter list | RAN1(Ericsson) |
| R3-235013 | Reply to LS on addressing packet loss during multicast MBS delivery | RAN2(Qualcomm) |
| R3-235021 | Reply LS Network Triggered Service Request for a UE in Suspend State | SA2(Ericsson) |
| R3-235039 | Reply LS for LS on Multiple Trace/MDT configurations | SA5(Nokia) |
| R3-235185 | Consideration on addressing packet loss during multicast MBS delivery | Huawei, CBN, Samsung, CMCC, Lenovo, Qualcomm Incorporated |
| R3-235186 | Correction on multicast data forwarding in case of UE context retrieval | Huawei, CBN, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Lenovo, Qualcomm Incorporated |
| R3-235187 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Huawei, CBN, Samsung, CMCC, Ericsson, Lenovo, ZTE, Qualcomm Incorporated |
| R3-235228 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Lenovo, Huawei, ZTE |
| R3-235334 | Discussion on multiple traces in NG-RAN | Huawei |
| R3-235335 | [draft] Reply LS to S5-235775 = R3-235039 on Multiple Trace/MDT configurations (to: SA5; cc: SA2; contact: Huawei) | Huawei |
| R3-235336 | Multiple trace and MDT configurations [multi_trace] | Huawei |
| R3-235337 | Multiple trace and MDT configurations [multi_trace] | Huawei |
| R3-235407 | Discussion on multiple Trace activations | CATT |
| R3-235408 | Support of multiple Trace activations | CATT, Huawei, Samsung, ZTE, CMCC |
| R3-235409 | Support of multiple Trace activations during mobility procedure | CATT |
| R3-235410 | Support of multiple Trace activations during mobility procedure | CATT |
| R3-235411 | Support of multiple Trace activations during mobility procedure | CATT |
| R3-235435 | The usage of paging subgrouping information in RAN in case of abnormal scenario | Huawei |
| R3-235436 | The usage of paging subgrouping information in RAN in case of abnormal scenario | Huawei |
| R3-235437 | [Draft] Reply LS to C1-235673 = R3-235004 on the usage of paging subgrouping information in RAN in case of abnormal scenario (to: CT1, SA2; cc: RAN2; contact: Huawei) | Huawei |
| R3-235441 | Discuss on Multiple Trace and MDT configurations | ZTE |
| R3-235442 | [Draft] Reply LS to S5-235775 = R3-235039 on Multiple Trace and MDT configurations (to: SA5; cc: SA2; contact: ZTE) | ZTE |
| R3-235534 | Paging subgrouping in abnormal scenario | Nokia, Nokia Shanghai Bell |
| R3-235535 | Correction of Paging subgrouping in abnormal scenario | Nokia, Nokia Shanghai Bell |
| R3-235536 | Draft Reply LS to C1-235673 = R3-235004 on usage of paging subgrouping information in RAN in case of abnormal scenario (to: CT1; cc: RAN2, SA2; contact: Nokia) | Nokia, Nokia Shanghai Bell |
| R3-235537 | Addressing packet loss and delay during multicast session | Nokia, Nokia Shanghai Bell |
| R3-235538 | Correction addressing packet loss and delay during multicast session | Nokia, Nokia Shanghai Bell |
| R3-235539 | Correction of addressing packet loss and delay during multicast session | Nokia, Nokia Shanghai Bell |
| R3-235540 | Draft Reply LS to R2-2309245 = R3-235013 on addressing packet loss during multicast MBS delivery (to: RAN2; cc: SA2; contact: Nokia) | Nokia, Nokia Shanghai Bell |
| R3-235567 | Discussion on way forward for multiple trace/MDT configurations | Nokia, Nokia Shanghai Bell |
| R3-235568 | Support of multiple trace sessions | Nokia, Nokia Shanghai Bell |
| R3-235569 | [Draft] Reply LS to S5-235775 = R3-235039 on Multiple Trace/MDT configurations (to: SA5; cc: RAN2, SA2; contact: Nokia) | Nokia, Nokia Shanghai Bell |
| R3-235577 | Discussion on LS from CT1 on PEIPS usage in case of abnormal scenario | Ericsson |
| R3-235578 | [Draft] Reply LS to C1-235673 = R3-235004 on usage of paging subgrouping information in RAN in case of abnormal scenario (to: CT1, RAN2; cc: -; contact: Ericsson) | Ericsson |
| R3-235628 | The usage of paging subgrouping information in RAN in case of abnormal scenario | Huawei |
| R3-235629 | The usage of paging subgrouping information in RAN in case of abnormal scenario | Huawei |
| R3-235678 | Discussion on additional PEIPS assistance info supporting | ZTE |
| R3-235679 | Correction for F1AP on additional PEIPS assistance information | ZTE |
| R3-235680 | Correction for XnAP on additional PEIPS assistance information | ZTE |
| R3-235681 | Correction for NGAP on additional PEIPS assistance information | ZTE |
| R3-235682 | Correction on additional PEIPS assistance information | ZTE |
| R3-235692 | Response to R3-235334 | Ericsson |
| R3-235693 | Response to LSout R3-235335: [draft] Reply LS to S5-235775 = R3-235039 on Multiple Trace/MDT configurations (to: SA5; cc: RAN2; contact: Ericsson) | Ericsson |
| R3-235694 | Response to CR R3-235336 | Ericsson |
| R3-235695 | Response to CR R3-235337 | Ericsson |
| R3-235698 | Summary of offline discussion CB#1 Multiple Traces | CATT |
| R3-235699 | Summary of offline discussion CB#2 PEIPS | Huawei |
| R3-235700 | Summary of offline discussion CB #3 MBSPacketLoss | Huawei |
| R3-235740 | Correction on multicast data forwarding in case of UE context retrieval | Huawei, CBN, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, Lenovo, Qualcomm Incorporated, CATT, ZTE |
| R3-235741 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Huawei, CBN, Samsung, CMCC, Ericsson, Lenovo, ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-235742 | Correction on Temp no data and DL data arrival for Activate Multicast Session | Lenovo, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-235828 | [Draft] Reply LS to C1-235673 = R3-235004 on the usage of paging subgrouping information in RAN in case of abnormal scenario (to: CT1; cc: RAN2; contact: Huawei) | Huawei |
| R3-235846 | [Draft] Reply LS to S5-235775 = R3-235039 on Multiple Trace/MDT configurations (to: SA5; cc: RAN2; contact: Nokia) | Nokia, Nokia Shanghai Bell |
| R3-235882 | Reply LS to S5-235775 = R3-235039 on Multiple Trace/MDT configurations (to: SA5; cc: RAN2; contact: Nokia) | RAN3 |
| R3-235883 | Reply LS to C1-235673 = R3-235004 on the usage of paging subgrouping information in RAN in case of abnormal scenario (to: CT1; cc: RAN2, SA2; contact: Huawei) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235754 | LS on a Framework for Network Slices in Networks Built from IETF Technologies Submission (IETF_LS_231009; to: RAN3, SA2, SA3, SA5; cc: -; contact: Cisco) | IETF(Cisco) |
| TDoc | Title | Source |
|---|---|---|
| R3-235320 | Discussion on pre-configured measurement gap for RedCap UE | ZTE |
| R3-235321 | Correction on SI delivery to RedCap UE during handover | ZTE |
| R3-235439 | Consideration on on introduction new attribute to support source coordination between LTE and NR SA | ZTE |
| R3-235440 | Discuss user consent for trace reporting | ZTE |
| R3-235541 | Conclusion on the use of PEI during Emergency PDU session | Nokia, Nokia Shanghai Bell |
| R3-235542 | Correction of Paging with PEI | Nokia, Nokia Shanghai Bell |
| R3-235543 | Draft Reply LS to S2-2307974 = R3-233727 on the use of PEI during an emergency PDU session (to: SA2; cc: CT1, RAN2; contact: Nokia) | Nokia, Nokai Shanghai Bell |
| R3-235570 | Correction of user consent for MDT | Nokia, Nokia Shanghai Bell |
| R3-235579 | Discussion on support of preconfigured GAP over F1 | Ericsson |
| R3-235580 | Support of preconfigured Measurement GAPs | Ericsson, Qualcomm Inc. |
| R3-235591 | Discussion on the on introduction of a new attribute “Only Resource Coordination” | Ericsson |
| R3-235597 | Discussion on user consent for trace reporting | Ericsson, InterDigital |
| R3-235598 | [draft] Reply LS to S3-234267 = R3-234493 on the user consent for trace reporting (to: SA3, SA5, RAN2; cc: SA1, RAN; contact: Ericsson) | Ericsson |
| R3-235599 | Corrections to the solutions on user consent for trace | Ericsson, InterDigital |
| R3-235648 | Discussion on user consent for trace reporting | CMCC |
| R3-235665 | Further discussions on the user consent for trace reporting | Huawei |
| R3-235666 | Correction to 38.401 on the user consent for trace reporting | Huawei |
| R3-235667 | [draft] Reply LS to S3-234267 = R3-234493 on the user consent for trace reporting (to: SA3; cc: RAN2, SA5, SA1, RAN; contact: Huawei) | Huawei |
| R3-235701 | Summary of offline discussion CB #4 GapMeasurement | Ericsson |
| R3-235702 | Reply LS to S5-234839 = R3-233738 introduction new attribute to support source coordination between LTE and NR SA (to: SA5; cc: -; contact: ZTE) | RAN3 |
| R3-235703 | Summary of offline discussion CB #6 UserConsent | Nokia |
| R3-235704 | Summary of offline discussion CB #7 PEI | Nokia |
| R3-235773 | Correction of user consent for MDT | Nokia, Nokia Shanghai Bell |
| R3-235779 | Correction of Paging with PEI | Nokia, Nokia Shanghai Bell |
| R3-235795 | Correction to 38.401 on the user consent for trace reporting | Huawei |
| R3-235864 | Correction on SI delivery to RedCap UE | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235869 | Support of preconfigured Measurement GAPs | Ericsson, Qualcomm Inc. |
| R3-235880 | Introduction of new attributes “Only Resource Coordination” in ANR | ZTE, Ericsson, China Telecom, CATT, Huawei |
| R3-235884 | Introduction of new attributes “Only Resource Coordination” in ANR | Ericsson, ZTE, China Telecom, CATT, Huawei |
| R3-235895 | Support of preconfigured Measurement GAPs | Ericsson, Qualcomm Inc. |
| TDoc | Title | Source |
|---|---|---|
| R3-235282 | Rapporteur update for 38.401 | NEC |
| R3-235544 | Correction of NG-U | Nokia, Nokia Shanghai Bell |
| R3-235576 | NRPPa Rapporteur Corrections | Rapporteur (Ericsson) |
| R3-235705 | Correction of NG-U | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235051 | (BL CR to 38.401) Addition of SON features enhancement | ZTE |
| R3-235058 | (BL CR to 38.470) Addition of SON features enhancement | CMCC |
| R3-235065 | (BL CR to 37.320) Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei |
| R3-235077 | (BL CR to 36.300) Addition of SON features enhancement | Lenovo |
| R3-235078 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-235079 | (BL CR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell |
| R3-235080 | (BL CR to 38.300) Addition of SON features enhancement | CMCC |
| R3-235081 | (BL CR to 38.413) for SON | Ericsson |
| R3-235082 | (BL CR to 38.423) for MDT | Huawei |
| R3-235083 | (BL CR to 38.423) Addition of SON features enhancement | Samsung |
| R3-235084 | (BL CR to 38.473) Addition of SON features enhancement | Huawei |
| R3-235116 | (BL CR to 38.420) SON Introduction of RACH Indication | Huawei |
| R3-235133 | (BL CR to 38.413) for MDT | Ericsson |
| R3-235355 | Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI | CMCC |
| R3-235725 | (BL CR to 38.413) for MDT | Ericsson |
| R3-235726 | (BL CR to 38.473) Addition of SON features enhancement | Huawei |
| R3-235956 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-235957 | (BL CR to 37.320) Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei |
| R3-235958 | (BL CR to 38.413) for MDT | Ericsson |
| R3-235959 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-235960 | (BLCR to 38.473) Addition of SON features enhancement | Huawei |
| R3-235961 | (BL CR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235012 | Response LS on SHR and SPR | RAN2(Nokia) |
| R3-235209 | (TP for SON BLCR for 38.300) SON enhancement for SHR | Samsung, Nokia, Nokia Shanghai Bell |
| R3-235210 | (TP for SON BLCR for 37.340 and 38.423) SON enhancement for SPR | Samsung |
| R3-235229 | Discussion on SON enhancements for SHR and SPR | Lenovo |
| R3-235258 | (TPs for SON BLCRs for TS 38.300 and TS 38.423) SHR and SPR | Huawei |
| R3-235291 | Discussion on remaining issue of inter-RAT SHR | NEC |
| R3-235302 | Open issues on SPR and SHR | Qualcomm Incorporated |
| R3-235356 | Discussion on SON enhancement for SPR | CMCC |
| R3-235385 | Remaining issues on SPR | Nokia, Nokia Shanghai Bell |
| R3-235443 | (TPs for SON BLCRs for TS 38.300 38.423)Inter-RAT SHR and SPR | ZTE |
| R3-235448 | (TP for SON 37.340) Discussion on SON enhancement for SHR and SPR | CATT |
| R3-235551 | (TP for SON BL CR for TS 38.423, TS 37.340) SHR and SPR for SON rel-18 | Ericsson |
| R3-235727 | Summary of offline discussion SONMDT1_SHRSPR | Samsung |
| R3-235848 | (TP for SON BLCR for 37.340) SON enhancement for SPR | Samsung |
| R3-235868 | LS on SON SPR (Successful PSCell change Report) (to: RAN2; cc: -; contact: Samsung) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235211 | (TP for SON BLCR for 38.423 and 37.340) SON enhancements for CPAC | Samsung |
| R3-235212 | (TP for SON BLCR for 38.413) MRO for the fast MCG recovery and inter-system handover for voice fallback | Samsung |
| R3-235230 | (TP for SON BLCR to TS 38.423) MRO for CPAC | Lenovo |
| R3-235231 | MRO for fast MCG recovery | Lenovo |
| R3-235259 | (TPs for SON BLCRs for TS 38.300 and TS 38.423) MRO on CPAC | Huawei |
| R3-235260 | (TPs for SON BLCRs for TS 38.423) MRO on fast MCG recovery | Huawei |
| R3-235292 | Discussion on remaining issue of MRO | NEC |
| R3-235303 | MRO enhancements for CPAC and fast MCG recovery | Qualcomm Incorporated |
| R3-235322 | (TPs for SON BL CR 36.300, 38.300 and 38.413) MRO for inter-system handover for voice fallback | ZTE |
| R3-235323 | (TPs for SON BL CR 37.340 and 38.423) MRO for CPAC and fast MCG recovery | ZTE |
| R3-235357 | Discussion on MRO for CPAC | CMCC |
| R3-235358 | Discussion on MRO for fast MCG recovery | CMCC |
| R3-235386 | (TPs for SON BLCR for TS 38.423) Further discussion on the MRO for CPAC and for the fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R3-235449 | (TP for SON 37.340 and 38.423) Discussion on MRO enhancement for CPAC | CATT |
| R3-235450 | (TP for SON 38.413) Discussion on MRO enhancement for fast MCG recovery and voice fallback | CATT |
| R3-235552 | (TP for SON BL CR for TS 38.413) SON enhancements for MRO | Ericsson |
| R3-235553 | (TP for SON BL CR for TS 37.340) Clarification on CPAC failure definitions | Ericsson |
| R3-235728 | Summary of offline discussion SONMDT2_MRO | Huawei |
| R3-235809 | (TP for SON BLCR for 37.340) SON enhancements for CPAC | Samsung |
| R3-235865 | (TP for BL CR for TS 36.300) MRO for inter-system handover for voice fallback | ZTE |
| R3-235866 | (TP for BL CR for TS 38.300) MRO for inter-system handover for voice fallback | ZTE |
| R3-235867 | DRAFT LS on MRO for fast MCG recovery (to: RAN2; cc: -; contact: Huawei) | Huawei |
| R3-235897 | LS on MRO for fast MCG recovery (to: RAN2; cc: -; contact: Huawei) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235192 | (TP to BL CR for TS38.423) Discussion on SON for RACH | Samsung |
| R3-235232 | (TP for SON BLCR to TS 38.423 and TS 36.423) Discussion on SN RACH enhancements | Lenovo |
| R3-235338 | (TP for SON BLCR for TS38.423 and TS 36.423): Clean-up for RACH Enhancement | Huawei |
| R3-235444 | (TPs for SON BLCRs for TS36.423 TS 38.423 TS 38.473)RACH enhancements | ZTE |
| R3-235451 | (TP for SON 37.340) Discussion on RACH enhancement | CATT |
| R3-235554 | (TP for SON BL CR for TS 38.423, TS 38.473) RACH Optimization enhancement | Ericsson |
| R3-235562 | (TP for SON BLCR for 36.423, 38.423) RA report forwarding via Xn/X2 to neighbour’s neighbour node | Nokia, Nokia Shanghai Bell |
| R3-235729 | (TP for SON BLCR for TS36.423 ) RACH enhancements | ZTE |
| R3-235730 | (TP for SON BLCRs for TS38.423 ) RACH enhancements | Huawei |
| R3-235731 | (TP for SON BLCRs for TS38.473 ) RACH enhancements | Ericsson |
| R3-235854 | (TP for SON BLCR for TS38.423 ) RACH enhancements | Huawei |
| R3-235855 | (TP for SON BLCR for TS38.473 ) RACH enhancements | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235134 | Left issues remaining in NPN | CATT |
| R3-235304 | SON MDT enhancements for SNPNs | Qualcomm Incorporated |
| R3-235339 | (TP for MDT BLCR for TS 38.413 and TS 38.423): Remaining issues for MDT in NPN | Huawei |
| R3-235445 | (TPs for MDT BLCRs for TS38.413 TS 38.423)MDT support in NPN | ZTE |
| R3-235555 | (TP for SON to BLCR for TS 38.413, TS 38.423) SON enhancements for Non-public networks | Ericsson |
| R3-235563 | (TP for TS 37.320) Removal of editor’s note | Nokia, Nokia Shanghai Bell |
| R3-235732 | Summary of offline discussion SONMDT3_NPN | ZTE |
| R3-235870 | (TP for SON BL CR to TS 38.413) SON enhancements for Non-public networks | Ericsson |
| R3-235871 | Draft LS on SON MDT for Equivalent SNPNs (to: RAN2; cc: -; contact: Qualcomm) | Qualcomm |
| R3-235885 | (TP for TS 37.320) Removal of editor’s note | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235162 | Future of MRO solution in Rel.18 and optimisation of the EDT | Nokia, Nokia Shanghai Bell |
| R3-235193 | (TPs to BL CRs for TS 38.423, 38.473) Discussion on SON for NR-U | Samsung |
| R3-235233 | (TP for SON BLCR to TS 38.423) Discussion on MRO for NR-U | Lenovo |
| R3-235305 | SON enhancements for NR-U | Qualcomm Incorporated |
| R3-235324 | (TP for SON BL CR 38.300) NR-U optimizations in Rel-18 | ZTE |
| R3-235340 | (TP for SON BL CR for TS 38.300): SON for NR-U | Huawei |
| R3-235452 | Discussion on SON enhancement for NR-U | CATT |
| R3-235556 | (TP for SON to BLCR for TS 38.473, TS 38.423) NR-U enhancements for MRO and MLB | Ericsson |
| R3-235733 | (TP for SON BL CR for TS 38.300): SON for NR-U | Huawei |
| R3-235734 | Summary of offline discussion SONMDT4_NRU | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R3-235564 | Further discussion on signalling based logged MDT override protection | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235011 | LS on QoE in RRC IDLE/INACTIVE and NR-DC scenarios | RAN2(Huawei) |
| R3-235029 | Reply LS on Approval of eQoE CRs for NR | SA5(Ericsson) |
| R3-235052 | (BL CR to 38.413) Introduction of R18 QoE measurement | Huawei, China Telecom, China Unicom |
| R3-235059 | (BL CR to 38.401) Introduction of R18 QoE measurement | Samsung |
| R3-235060 | (BL CR to 38.473) Introduction of R18 QoE measurement | ZTE |
| R3-235099 | (BL CR to 37.340) QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson |
| R3-235100 | (BL CR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-235101 | (BL CR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| R3-235395 | Update Workplan for Rel-18 NR QoE Enhancement | China Unicom |
| R3-235807 | Draft reply LS to R2-2309004 = R3-235011 and S5-235542 = R3-235028 on Priority information and NR-DC (to: RAN2; cc: SA4, SA5; contact: Huawei) | Huawei |
| R3-235912 | Reply LS to R2-2309004 = R3-235011 and S5-235542 = R3-235028 on Priority information and NR-DC (to: RAN2; cc: SA4, SA5; contact: Huawei) | RAN3 |
| R3-235989 | (BL CR to 37.340) QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson |
| R3-235990 | (BL CR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-235991 | (BL CR to 38.401) Introduction of R18 QoE measurement | Samsung |
| R3-235992 | (BLCR to 38.413) Introduction of R18 QoE measurement | Huawei, China Telecom, China Unicom |
| R3-235993 | (BLCR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| R3-235994 | (BLCR to 38.473) Introduction of R18 QoE measurement | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R3-235024 | Reply LS on area scope for QoE measurements | SA4(Huawei) |
| R3-235025 | Reply LS on QoE measurement collection for application sessions delivered via MBS broadcast or multicast | SA4(Huawei) |
| R3-235032 | Reply LS on collecting QoE measurements per MBS service area and MBS session ID | SA5(Huawei) |
| R3-235033 | Reply LS on area scope for QoE measurements | SA5(Huawei) |
| R3-235234 | Remaining issues on QoE measurement in RRC_INACTIVE and RRC_IDLE states | Lenovo |
| R3-235235 | (TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-235295 | Discussion on INACTIVE/IDLE QoE | NEC |
| R3-235306 | QMC for applications carried over MBS broadcast and multicast | Qualcomm Incorporated |
| R3-235307 | QoE enhancements for high mobility scenarios | Qualcomm Incorporated |
| R3-235345 | TP to BLCR for 38.413 on NR QoE in RRC_INACTIVE/RRC_IDLE states | CATT |
| R3-235346 | [Draft] Reply LS to R2-2309004 = R3-235011 on introducing assistance information (to: RAN2; cc: SA5; contact: CATT) | CATT |
| R3-235399 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | China Unicom |
| R3-235475 | Leftover issues on QMC for MBS and RRC state | Samsung |
| R3-235523 | QoE and RVQoE Measurement Collection for Sessions Carried via MBS | Ericsson |
| R3-235524 | (TP for QoE BL CR for TS 38.413) QMC in HSDN Cells and High Mobility Scenarios | Ericsson |
| R3-235558 | (TP for TS 38.413) Configuration of MBS QMC | Nokia, Nokia Shanghai Bell |
| R3-235559 | Open points on high mobility scenarios | Nokia, Nokia Shanghai Bell |
| R3-235630 | QoE measurement collection for MBS | Xiaomi |
| R3-235656 | Further discussion on the support of MBS QoE | Huawei |
| R3-235657 | [draft] Reply LS to S4-231491 = R3-235025 on QoE measurement collection for application sessions delivered via MBS broadcast or multicast (to: SA4, RAN2; cc: SA5; contact: Huawei) | Huawei |
| R3-235658 | [draft] Reply LS to S5-232760 = R3-234095, R2-2309004 = R3-235011 on QoE measurements in RRC IDLE&INACTIVE states (to: SA5, RAN2; cc: SA4; contact: Huawei) | Huawei |
| R3-235659 | (TP to 38.413) on support of MBS QoE | Huawei, China Telecom, China Unicom |
| R3-235673 | TP to 38.413, 38.423 BLCR and draft CR 38.300 for INACTIVE IDLE QoE | ZTE, China Telecom, China Unicom |
| R3-235674 | Discussion on INACTIVE/IDLE QoE and high mobility QoE | ZTE, China Telecom, CMCC |
| R3-235675 | Discussion on selection policy for IDLE/INACTIVE QoE report | ZTE, China Telecom |
| R3-235766 | Summary of the offline discussion on IDLE INACTIVE QoE | ZTE |
| R3-235796 | Reply LS to R3-234745 on QMC support in RRC_IDLE and RRC_INACTIVE (R2-2311409; to: RAN3; cc: SA2, SA5, SA3; contact: China Unicom) | RAN2(China Unicom) |
| R3-235803 | (TP for TS 38.413) Configuration of MBS QMC | Nokia, Nokia Shanghai Bell |
| R3-235804 | (TP to 38.420) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-235805 | TP to 38.300 for INACTIVE IDLE QoE | ZTE, China Telecom, China Unicom |
| R3-235806 | Summary for offline discussion QoE1_INACTIVE | ZTE |
| R3-235808 | Draft Reply to S4-231491 = R3-235025 and S5-235781 = R3-235032 on MBS communication service (to: SA4, SA5, RAN2; cc: -; contact: Huawei) | Huawei |
| R3-235909 | TP to 38.300 for INACTIVE IDLE QoE | ZTE, China Telecom, China Unicom, Ericsson |
| R3-235910 | (TP to 38.423) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-235911 | (TP for TS 38.413) Configuration of MBS QMC | Nokia, Nokia Shanghai Bell |
| R3-235913 | Reply LS to S4-231491 = R3-235025 and S5-235781 = R3-235032 on MBS communication service (to: SA4, SA5, RAN2, SA2; cc: -; contact: Huawei) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235236 | On Remaining issues of QoE measurement in NR-DC | Lenovo |
| R3-235296 | Remaining issues on support of NR-DC | NEC |
| R3-235308 | Support for QoE in NR-DC | Qualcomm Incorporated |
| R3-235347 | Discussion on Support for QoE in NR-DC | CATT |
| R3-235396 | Discussion on QoE measurement in NR-DC | China Unicom |
| R3-235397 | (TP to BL CR of 38.423) QoE in NR-DC | China Unicom |
| R3-235476 | Leftover issues on QMC support of NR-DC | Samsung |
| R3-235525 | (TPs for QoE BL CR for TS 37.340, TS 38.300, and TS 38.423) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | Ericsson |
| R3-235560 | (TP for TS 38.423) QoE scenarios requiring support in Xn signalling for NR-DC | Nokia, Nokia Shanghai Bell |
| R3-235631 | (TP to BL CR for TS 38.423) QoE configuration and reporting in NR-DC | Xiaomi |
| R3-235651 | Further discussion on QoE enhancement for NR-DC | ZTE, China Telcom |
| R3-235652 | (TP to BL CR of 37.340) Procedure flows on the initial QMC configuration in NR-DC | ZTE, China Unicom, China Telecom |
| R3-235653 | (TP to BL CR of 38.423) QoE in NR-DC | ZTE, China Telecom |
| R3-235660 | Further discussion on the support for QoE in NR-DC | Huawei |
| R3-235661 | (TP to 38.423) on QoE measurement enhacements in DC | Huawei |
| R3-235744 | (TP for BL CR for TS 38.423) QMC support in NR-DC | Ericsson |
| R3-235745 | (TP for QoE BL CR for TS 37.340) QMC support in NR-DC | ZTE, Ericsson, China Unicom, China Telecom, Samsung, Huawei |
| R3-235747 | Summary of offline discussion on QMC (QoE Measurement Collection) for NR-DC | Ericsson |
| R3-235898 | (TP for BL CR for TS 38.423) QMC support in NR-DC | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235026 | Reply LS on buffer level threshold-based RVQoE reporting | SA4(Apple) |
| R3-235028 | Reply LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload | SA5(Huawei) |
| R3-235237 | Remaining issues on QoE measurement during intra-5GC inter-RAT handover | Lenovo |
| R3-235309 | Open issues on other QoE topics | Qualcomm Incorporated |
| R3-235348 | Discussion on Left-over issues | CATT |
| R3-235398 | Discussion on NR QoE Left-over issues | China Unicom |
| R3-235526 | (TP for QoE BL CR for TS 38.473) Enhancements of Rel-17 QoE and RVQoE Features | Ericsson |
| R3-235561 | (TP for TS 38.473) Discussion on QoE reporting assistance information provisioning during RAN overload and RVQoE report deactivation over F1 interface | Nokia, Nokia Shanghai Bell, ZTE |
| R3-235654 | Discussion on the other issues of NR QoE enhancement | ZTE, China Telecom, CMCC |
| R3-235655 | (TPs for BL CR of TS38.401&38.470) Deactivation of RVQoE reporting over F1AP | ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-235662 | Further discussion on the support of R17 left-over features and inter RAT handover | Huawei |
| R3-235663 | [draft] Reply LS to S5-235542 = R3-235028 on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload (to: SA5; cc: RAN2; contact: Huawei) | Huawei |
| R3-235664 | (TP to 38.413) on support of assistance information for overloading | Huawei, China Telecom, China Unicom |
| R3-235777 | (TP for BL CR of TS 38.401) Deactivation of RVQoE reporting over F1AP | ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-235780 | Summary of offline discussion about QoE other aspects | Huawei |
| R3-235821 | (BL CR for 38.470) on RVQoE reporting over F1 | Lenovo |
| R3-235822 | (TP for TS 38.473) Discussion on QoE reporting assistance information provisioning during RAN overload and RVQoE report deactivation over F1 interface | Nokia, Nokia Shanghai Bell, ZTE |
| R3-235823 | (TP to 38.413) on support of assistance information for overloading | Huawei, China Telecom, China Unicom |
| R3-235899 | (BL CR for 38.470) on RVQoE reporting over F1 | Lenovo, ZTE, Ericsson, Huawei, Samsung, Nokia |
| R3-235900 | (TP for TS 38.473) RVQoE report deactivation over F1 interface | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-235901 | (TP for BL CR of TS 38.401) Deactivation of RVQoE reporting over F1AP | ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| TDoc | Title | Source |
|---|---|---|
| R3-235050 | (BL CR to TS 38.401) for addition of AI/ML-RAN feature in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC |
| R3-235075 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated |
| R3-235076 | (BL CR to 38.423) for AI/ML for NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235735 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated |
| R3-235953 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated |
| R3-235954 | (BL CR to 38.420) Support of AIML for NG-RAN | CATT |
| R3-235955 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235137 | (TP to 38.300) Adding the description of UE trajectory feedback | CATT |
| R3-235470 | (TP to 38.300 BLCR) Stage2 description update for AI/ML RAN | ZTE |
| R3-235486 | Further discussions on common issues and Stage2 updates on the introduction of RAN AIML | Huawei |
| R3-235607 | General aspects of Data Collection Reporting procedure | Ericsson, InterDigital, Orange, Deutsche Telekom, AT&T |
| R3-235608 | (TP to AIML CE to TS38.423) General aspects of Data Collection Reporting procedure | Ericsson, InterDigital, Orange, Deutsche Telekom, AT&T |
| R3-235609 | (TP for CR for AIML to TS38.423) General aspects of Prediction Time Definition | Ericsson, InterDigital |
| R3-235610 | (TP to TS 38.300) Stage 2 Updates | Nokia, Nokia Shanghai Bell |
| R3-235616 | (TP for CR for AIML to TS38.423) General aspects of Prediction Time Definition | Ericsson, InterDigital |
| R3-235624 | (TP to 38.300 BLCR) Stage2 description for AIML RAN | ZTE |
| R3-235625 | (TP to 38.423 BLCR) Clean miscellaneous name FFS in 38.423 | ZTE |
| R3-235690 | General aspects of Prediction Time Definition | Ericsson, InterDigital |
| R3-235736 | (TP to 38.300 BLCR) Stage2 description update for AI/ML RAN | ZTE |
| R3-235737 | (TP to AIML CE to TS38.423) General aspects of Data Collection Reporting procedure | Ericsson, InterDigital, Orange, Deutsche Telekom, AT&T |
| R3-235902 | (TP to AIML CE to TS38.423) General aspects of Data Collection Reporting procedure | Ericsson, InterDigital, Orange, Deutsche Telekom, AT&T, Lenovo, CATT |
| R3-235904 | (TP to 38.300 BLCR) Stage2 description update for AI/ML RAN | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R3-235138 | (TP to BL CR for TS 38.423) Discussion on UE performance feedback | CATT |
| R3-235142 | (TP to BLCR for 38.420) Support of AI/ML for NG-RAN | CATT |
| R3-235194 | (TP to BL CR for TS 38.423) Discussion on Xn impact of LB | Samsung |
| R3-235238 | Left issues related to load balancing use case | Lenovo |
| R3-235239 | (TP for TS38.423 BLCR) On UE related feedback collection | Lenovo |
| R3-235287 | RAN AI/ML Reporting Periodicity on UE Performance Feedback | NEC |
| R3-235288 | (TP to TS 38.423 on RAN AI/ML) Reporting Periodicity on UE Performance Feedback | NEC |
| R3-235363 | Discussion on AIML remaining issues | CMCC |
| R3-235364 | (TP for 38.423)Procedure for Load Balancing | CMCC |
| R3-235426 | (TP to 38.423) Further discussion on remaining issues for LB | ZTE |
| R3-235466 | Discussion on Xn Enhancements for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-235487 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Load Balancing use case | Huawei |
| R3-235527 | Discussion on open issues for AIML load balancing | LG Electronics Inc. |
| R3-235528 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on open issues for AI/ML load balancing | LG Electronics Inc. |
| R3-235605 | (TP for AIML BLCR for TS 38.423) Cause values for Data Collection Reporting Initiation | Ericsson, Deutsche Telekom, InterDigital, AT&T |
| R3-235606 | Cause values for Data Collection Reporting Initiation | Ericsson, Deutsche Telekom, InterDigital, AT&T |
| R3-235611 | (TP to TS 38.423) AI/ML Load Balancing and UE Performance Feedback Discussion | Nokia, Nokia Shanghai Bell |
| R3-235618 | Timing configuration for UE performance feedback reporting | Ericsson, InterDigital, Deutsche Telekom |
| R3-235619 | (TP to CR for AI/ML to TS38.423) Timing configuration for UE performance feedback reporting | Ericsson, InterDigital, Deutsche Telekom |
| R3-235620 | Discussion on cause value and UE Performance Feedback | Intel Corporation |
| R3-235738 | Summary of offline discussion for AIRAN2_LB | Samsung |
| R3-235878 | (TP to BLCR for 38.420) Support of AI/ML for NG-RAN | CATT |
| R3-235879 | (TP to TS 38.423 BLCR) Support of UE performance transferring via Xn | Samsung |
| R3-235903 | (TP to BLCR for 38.420) Support of AI/ML for NG-RAN | CATT, Ericsson, Lenovo, Nokia, ZTE, Samsung, NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-235141 | (TP to BL CR for TS 38.423) Support of AI/ML based mobility optimization | CATT |
| R3-235149 | Mobility Optimization Outputs | InterDigital |
| R3-235150 | [TP for BL CR 38.423] Handling Additional Mobility Outputs | InterDigital |
| R3-235195 | (TP to BL CR for TS 38.423) Discussion on Xn impact of ME | Samsung |
| R3-235240 | Left issues related to mobility enhancement use case | Lenovo |
| R3-235289 | AI/ML Measured UE Trajectory information | NEC |
| R3-235290 | (TP to TS 38.423 on RAN AI/ML) Measured UE Trajectory information | NEC |
| R3-235359 | Discussion on Measured UE Trajectory Collection | CMCC |
| R3-235360 | (TP for TS 38.423)Measured UE Trajectory Collection | CMCC |
| R3-235389 | Discussion on remaining issues for UE trajectory | China Telecommunication |
| R3-235390 | (TP for BLCR of TS 38.423) On support of measured UE trajectory | China Telecommunication |
| R3-235427 | (TP to 38.423 BLCR) Discussion on left issues of Measured&Predicted UE Trajectory in AI based mobility optimization | ZTE |
| R3-235467 | (TP to BL CR for TS 38.423) Discussion on UE Trajectory Feedback Reporting | Qualcomm Incorporated |
| R3-235488 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Mobility Enhancements use case | Huawei |
| R3-235529 | Discussion on open issues for AI/ML mobility optimization | LG Electronics Inc. |
| R3-235530 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on open issues for AIML mobility optimization | LG Electronics Inc. |
| R3-235600 | Cell based UE trajectory prediction configuration | Ericsson, Orange, Deutsche Telekom, InterDigital, AT&T |
| R3-235601 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, Orange, Deutsche Telekom, InterDigital, AT&T |
| R3-235612 | (TP to TS 38.423) AI/ML Trajectory Data Collection and Other Mobility Aspects | Nokia, Nokia Shanghai Bell |
| R3-235739 | Summary for offline discussion about AIRAN3_ME | ZTE |
| R3-235834 | (TP to 38.423 BLCR) Discussion on left issues of Measured&Predicted UE Trajectory in AI based mobility optimization | ZTE |
| R3-235859 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, Orange, Deutsche Telekom, InterDigital, AT&T |
| R3-235906 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, Orange, Deutsche Telekom, InterDigital, AT&T, CATT |
| TDoc | Title | Source |
|---|---|---|
| R3-235031 | Reply to LS on AI/ML for NG-RAN Energy Saving Energy Cost index | SA5(Huawei) |
| R3-235139 | Discussion on reply LS about EC metric | CATT |
| R3-235196 | Discussion on Xn impact of ES | Samsung |
| R3-235241 | Left issues related to network energy saving use case | Lenovo |
| R3-235428 | (Draft) Reply LS to S5-235777 = R3-235031 Further discussion on AIML based Energy Saving (to: SA5; cc: -; contact: ZTE) | ZTE |
| R3-235471 | Discussion on ES LS and Energy Cost over F1 interface | Qualcomm Incorporated |
| R3-235489 | Remaining open issues for the Energy Saving use case | Huawei |
| R3-235490 | [Draft] Reply LS to S5-235777 = R3-235031 on AI/ML for NG-RAN Energy Saving Energy Cost index (to: SA5; cc: -; contact: Huawei) | Huawei |
| R3-235491 | (TPs for AIML BL CRs for TS 38.300 and TS 38.423) EC Stage 2 and Stage 3 updates on the introduction of RAN AIML | Huawei |
| R3-235602 | AI-ML Network Energy Saving | Ericsson |
| R3-235603 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | Ericsson |
| R3-235604 | Draft Reply LS to S5-235777 = R3-235031 on AI/ML for NG-RAN Energy Saving Energy Cost index (to: SA5; cc: -; contact: Ericsson) | Ericsson |
| R3-235613 | (TP to TS 38.423) Energy Efficiency aspects related to SA5 LS and Energy Cost Description | Nokia, Nokia Shanghai Bell, Orange |
| R3-235614 | [Draft] Reply LS to S5-235777 = R3-235031 on AI/ML for NG-RAN Energy Saving Energy Cost index (to: SA5; cc: -; contact: Nokia) | Nokia, Nokia Shanghai Bell |
| R3-235623 | Further discussion on NG-RAN AIML energy saving | NTT DOCOMO INC.. |
| R3-235640 | Discussion on reply to SA5 LS of Energy Cost Index | CMCC |
| R3-235641 | Draft reply LS to S5-235777 = R3-235031 on SA5 questions of Energy Cost Index (to: SA5; cc: -; contact: CMCC) | CMCC |
| R3-235743 | Reply LS to S5-235777 = R3-235031 on AI/ML for NG-RAN Energy Saving Energy Cost index (to: SA5; cc: -; contact: Huawei) | Huawei |
| R3-235835 | Summary of offline discussion AIRAN4_ES | Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-235140 | (TP to 38.473 & 37.483) Discussion on E1AP and F1AP impacts | CATT |
| R3-235197 | Discussion on E1/F1 impact of AI/ML for NG-RAN | Samsung |
| R3-235198 | (CR to 37.483) for AI/ML for NG-RAN (existing procedure for EC) | Samsung |
| R3-235199 | (CR to 37.483) for AI/ML for NG-RAN (new procedure) | Samsung |
| R3-235242 | (TPs to BL CRs for TS 37.480 TS 38.470) Discussion on E1 F1 interface impact | Lenovo |
| R3-235365 | Discussion on F1E1 interface impact | CMCC |
| R3-235366 | (TP for 38.473 and 37.483)Procedure for E1 F1 interface | CMCC |
| R3-235429 | (TP to 38.473 & 37.483) Consideration on Measured Energy Cost over F1&E1 interface | ZTE, China Unicom |
| R3-235430 | [TP for BLCR 38.401] Stage2 impact of E1&F1 interface for AIRAN | ZTE, Samsung, CATT, CMCC, China Unicom |
| R3-235492 | (TP for AI/ML BL CR for TS 37.483 and 38.473) On the impact of RAN AI/ML over E1 and F1 interfaces | Huawei |
| R3-235615 | (TP to TS 38.473) Energy Cost Exchange over F1 | Nokia, Nokia Shanghai Bell |
| R3-235617 | (TP to CR for AIML to TS38.473) On transmission of measured EC from gNB-DU to gNB-CU | Ericsson |
| R3-235748 | Summary of offline discussion AIRAN5_F1E1 | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-235049 | (BL CR to 38.305) Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235054 | (BL CR to 38.455) Support for mobile TRP Location Information | Xiaomi, Ericsson, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-235093 | (BL CR to 38.413) Support for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-235094 | (BL CR to 38.473): Support for mobile IAB | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-235120 | (BL CR to 38.401) Support for mobile IAB | Huawei |
| R3-235121 | (BL CR to 38.470) New F1 setup | ZTE |
| R3-235297 | Updated workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R3-235724 | Summary of offline discussion on Mobile IAB | Qualcomm |
| R3-235974 | (BL CR to 38.401) Support for mobile IAB | Huawei |
| R3-235975 | (BL CR to 38.423) Support for mobile IAB | Samsung |
| R3-235976 | (BL CR to 38.455) Support for mobile TRP Location Information | Xiaomi, Ericsson, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-235977 | (BL CR to 38.473): Support for mobile IAB | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-235978 | (BL CR to 38.470) Support of mobile IAB | ZTE |
| TDoc | Title | Source |
|---|---|---|
| R3-235170 | (TP for Mobile IAB BL CR TS38.401) Discussion on IAB-node mobility and integration | Fujitsu |
| R3-235222 | Discussion on leftover issues for IAB-node mobility | CATT |
| R3-235243 | (TP to TS 38.420 BLCR) Discussion on mobile IAB-MT handover | Lenovo |
| R3-235244 | (TP to TS 38.401 BLCR) Discussion on mIAB-DU migration and mIAB-node integration | Lenovo |
| R3-235298 | (TP to TS 38.401) BL ST2 procedures for mobile IAB | Qualcomm Inc. |
| R3-235299 | Open issues for mobile IAB topology adaptation | Qualcomm Inc. |
| R3-235314 | Discussion on DU migration | Samsung |
| R3-235315 | Discussion on multiple partial migration | Samsung |
| R3-235400 | (TP for Mobile IAB BL CR for TS 38.401/38.413/38.423/38.473/38.470): Inter-donor migration in mobile IAB scenario | ZTE |
| R3-235401 | (TP for Mobile IAB BL CR for TS 38.413) Transfer of mobile IAB authorization state in NGAP DOWNLINK NAS TRANSPORT | ZTE, CATT, Samsung |
| R3-235416 | (TP for NR_mobile_IAB BL CRs for TS 38.401/ 38.423) Support of mobility for mobile IAB | Huawei |
| R3-235432 | Discussion on IAB-node mobility | CANON Research Centre France |
| R3-235480 | (TP for mIAB BL CR for TS 38.401) Migration Procedure for Mobile IAB-Nodes | Ericsson |
| R3-235510 | (TP for Mobile IAB TS38.413 BL CR) Discussion on Support IAB-node mobility | Nokia, Nokia Shanghai Bell |
| R3-235633 | (TP to BL CR for TS 38.473) Discussion on IAB-node mobility | Xiaomi |
| R3-235672 | (TP for Mobile IAB BL CR for TS 38.423) Transfer of mobile IAB authorization state in Xn HO request message | ZTE, Samsung, Xiaom |
| R3-235776 | (TP to BL CR for TS 38.401) on stage 2 procedures for mobile IAB | Huawei, Qualcomm Inc. |
| R3-235781 | (TP for Mobile IAB BL CR for TS 38.423): Adding of BAP address in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message | ZTE |
| R3-235783 | (TP for mIAB BL CR for TS 38.401) Migration Procedure for Mobile IAB-Nodes | Ericsson |
| R3-235856 | (TP for mIAB BL CR for TS 38.473) Adding of MT info in DU configuration update message | ZTE |
| R3-235857 | (TP for mIAB for BL CR TS 38.470) Transferring of MT info via F1AP | ZTE |
| R3-235858 | (TP to BL CR for TS 38.423) on Transfer of mobile IAB authorization state in Xn HO request message | ZTE, Samsung, Xiaomi, Nokia, Fujitsu |
| R3-235872 | [Draft] LS on awareness of gNB ID of RRC terminating donor for mobile IAB (to: RAN2; cc: -; contact: Huawei) | Huawei |
| R3-235905 | (TP for mIAB BL CR for TS 38.473) Adding of MT info in DU configuration update message | ZTE, Samsung |
| R3-235914 | (TP for Mobile IAB BL CR for TS 38.423): Adding of BAP address in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message | ZTE, Nokia, Nokia Shanghai Bell |
| R3-235915 | (TP to BL CR for TS 38.423) on Transfer of mobile IAB authorization state in Xn HO request message | ZTE, Samsung, Xiaomi, Nokia, Fujitsu |
| R3-235917 | (TP for Mobile IAB BL CR for TS 38.423): Adding of BAP address in the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message | ZTE, Nokia, Nokia Shanghai Bell |
| R3-235918 | (TP for mIAB BL CR for TS 38.473) Adding MT info over F1 | ZTE, Samsung, Huawei, Ericsson, Nokia |
| R3-235919 | LS on awareness of gNB ID of RRC terminating donor for mobile IAB (to: RAN2; cc: -; contact: Huawei) | RAN3 |
| R3-235920 | (TP for mIAB BL CR for TS 38.401) Migration Procedure for Mobile IAB-Nodes | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235034 | LS reply to LS on Cell ID (re)configuration for mobile IAB cell | SA5(Ericsson) |
| R3-235223 | Enhancements for mobility IAB | CATT |
| R3-235245 | Mobility enhancements for mobile IAB-node and its served UE | Lenovo |
| R3-235300 | Configuration of NCGI and TAC for mIAB | Qualcomm Inc. |
| R3-235316 | Discussion on mobility enhancements | Samsung |
| R3-235402 | (TP for Mobile IAB BL CR for TS 38.473/38.401) Enhancements to IAB node migration in mobile IAB scenario | ZTE |
| R3-235417 | (TP for NR_mobile_IAB BL CR for TS 38.473): Mobility enhancement for mobile IAB | Huawei |
| R3-235481 | (TP for mIAB BL CR for TS 38.401) CU-based NCI (Re)configuration for mIAB Cells | Ericsson |
| R3-235482 | IAB-Node Mobility Enhancements | Ericsson |
| R3-235511 | Discussion on IAB configuration and Mobility Enhancements | Nokia, Nokia Shanghai Bell |
| R3-235634 | (TPs to BL CR for TS 38.401 and TS 38.473) mobility enhancement for mobile IAB | Xiaomi |
| R3-235784 | Draft Reply LS to S5-236128 = R3-235034 on Cell ID (re)configuration for mobile IAB cell (to: SA5; cc: -; contact: Ericsson) | Ericsson |
| R3-235785 | (TP for NR_mobile_IAB BL CR for TS 38.473): Mobility enhancement for mobile IAB | Huawei |
| R3-235921 | Reply to S5-236128 = R3-235034 on Cell ID (re)configuration for mobile IAB cell (to: SA5; cc: -; contact: Ericsson) | RAN3 |
| R3-235922 | (TP for NR_mobile_IAB BL CR for TS 38.473): IAB onor CU based NCGI refconfiguration | Huawei, Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R3-235224 | On interference mitigation | CATT |
| R3-235246 | PCI collision mitigation of mobile IAB-node mobility | Lenovo |
| R3-235317 | Discussion on mitigation of interference | Samsung |
| R3-235403 | Discussion on PCI collision avoidance for mobile IAB | ZTE |
| R3-235433 | PCI Collision Avoidance with Mobile IAB | CANON Research Centre France |
| R3-235483 | PCI Collision Avoidance for Mobile IAB-Nodes | Ericsson |
| R3-235512 | Mobile IAB interference mitigation | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235022 | Reply LS CAG solution for mobile IAB | SA2(Ericsson) |
| R3-235036 | LS on UE RACH-less handover for mobile IAB | RAN2(Huawei) |
| R3-235037 | LS on CAG solution for mobile IAB | RAN2(Ericsson) |
| R3-235038 | LS On IAB-node De-authorization handling | SA2(Ericsson) |
| R3-235225 | Discussion on additional ULI for mIAB | CATT, ZTE |
| R3-235301 | Discussion on reply LSs to RAN2 and SA2 on mIAB | Qualcomm Inc. |
| R3-235404 | (TP for Mobile IAB BL CR TS38.473) Enhancements on positioning and additional ULI for mobile IAB | ZTE, Xiaomi, CATT |
| R3-235405 | Discussion on LS on Mobile IAB-node De-authorization Handling and UE RACH-less handover | ZTE |
| R3-235418 | (TP for NR_mobile_IAB BL CR for TS 38.455): Positioning enhancement on uplink E-CID measurement for mobile TRP | Huawei, Ericsson, Xiaomi |
| R3-235419 | (TP for NR_mobile_IAB BL CR for TS 38.473): Positioning enhancement on uplink E-CID measurement for mobile TRP | Huawei, Ericsson, Xiaomi |
| R3-235420 | Discussion on IAB-node De-authorization handling | Huawei |
| R3-235421 | (TP for NR_mobile_IAB BL CR for TS 38.473): Support of RACH-less HO for mobile IAB | Huawei |
| R3-235422 | [draft] Reply LS to \tR2-2306817 = R3-233713 = R3-235036, R3-233713 on UE RACH-less handover for mobile IAB (to: RAN2; cc: -; contact: Huawei) | Huawei |
| R3-235484 | (TP for mIAB BL CR for TS 38.470) Discussion of SA2 FS_VMR Solutions | Ericsson |
| R3-235485 | Discussion and Draft Reply LS on Mobile IAB-node De-authorization Handling | Ericsson |
| R3-235513 | Discussion on incoming LS | Nokia, Nokia Shanghai Bell |
| R3-235632 | (TP to BL CR for TS 38.423) Discussion on LS from SA2 and RAN2 | Xiaomi |
| R3-235775 | (TP to BL CR for TS 38.423) Discussion on LS from SA2 and RAN2 | Xiaomi, Nokia, Nokia Shanghai Bell, Huawei |
| R3-235782 | (TP for Mobile IAB BL CR for TS 38.473) Enhancements to IAB node migration in mobile IAB scenario | ZTE, Xiaomi, CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235786 | Draft reply LS to S2-2211437 = R3-230032 on FS_VMR solutions review (to: SA2; cc: RAN2, RAN4, RAN; contact: Qualcomm) | Qualcomm |
| R3-235787 | Draft reply LS to S2-2308158 = R3-233730 on IAB-node De-authorization handling (to: SA2; cc: -; contact: Qualcomm) | Qualcomm |
| R3-235916 | (TP to BL CR for TS 38.423) Support of mobile IAB authorization information transfer | Xiaomi, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-235923 | (TP for Mobile IAB BL CR for TS 38.473) Enhancements to IAB node migration in mobile IAB scenario | ZTE, Xiaomi, CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235924 | Reply LS to S2-2211437 = R3-230032 on FS_VMR solutions review (to: SA2; cc: RAN2, RAN4, RAN; contact: Qualcomm) | RAN |
| R3-235925 | Reply LS to S2-2308158 = R3-233730 on IAB-node De-authorization handling (to: SA2; cc: -; contact: Qualcomm) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235064 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| R3-235089 | (BL CR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-235090 | (BL CR to 38.401) for L1L2Mob | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235091 | (BL CR to TS 38.423) Introduction of Subsequent CPAC | Huawei, ZTE |
| R3-235092 | (BL CR to 38.473) Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE |
| R3-235119 | (BL CR to 38.423) Introduction of CHO with SCG(s) | Lenovo, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-235762 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| R3-235763 | (BL CR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-235968 | (BLCR to 38.401) for L1L2Mob | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235969 | (BL CR to 38.423) Introduction of CHO with SCG(s) | Lenovo, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-235970 | (BL CR to TS 38.423) Introduction of Subsequent CPAC | Huawei, ZTE |
| R3-235971 | (BLCR to 38.473) Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE |
| R3-235972 | (BL CR to 38.473) On Subsequent CPAC | Lenovo |
| R3-235973 | (BL CR to 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235008 | LS on L1 measurement and TA management for LTM | RAN1(Fujitsu, Mediatek) |
| R3-235014 | Reply LS to R3-230889 on Approaches during execution for inter-DU LTM | RAN2(Ericsson) |
| R3-235016 | LS on RAN2 progress on LTM | RAN2(Huawei) |
| R3-235019 | Reply LS on beam application time and UE based TA measurement for LTM | RAN4(Ericsson) |
| R3-235040 | (TP to BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia, Nokia Shanghai Bell |
| R3-235041 | (TPs to BL CRs for TS 38.473 and TS 38.423) On Reference Configuration and SCG Release for L1/2 Triggered Mobility (LTM) | Nokia, Nokia Shanghai Bell |
| R3-235135 | Discussion about candidate cell RS configuration | CATT |
| R3-235136 | (TP for 38.473 BLCR) Left issues remaining in LTM | CATT |
| R3-235164 | Discussion on L1 measurement reporting configuration in Inter-DU LTM | LG Electronics Inc. |
| R3-235177 | (TP to Mob_enh2 BL CR TS 38.473) Discussion on L1/L2 based Inter-cell Mobility | Samsung |
| R3-235247 | Discussion on L1L2 based inter-cell mobility | Lenovo |
| R3-235248 | (TPs to TS 38.401 BLCR & TS 38.470) Support of L1/L2 based inter-cell mobility | Lenovo |
| R3-235264 | Signalling Support for LTM | Qualcomm Incorporated |
| R3-235266 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | Ericsson |
| R3-235267 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM | Ericsson |
| R3-235283 | (TP to TS38.473 on LTM) Rel-18 LTM Configuration ID and other | NEC |
| R3-235284 | (TP to TS38.401 on LTM) Informing of other candidate Cell(s) in other candidate gNB-DU(s) to candidate gNB-DU | NEC |
| R3-235341 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures | Huawei |
| R3-235342 | (TP for L1L2Mob BLCR for TS 38.473): LTM procedure design | Huawei |
| R3-235368 | Resource management at gNB-DU for LTM | Rakuten Symphony |
| R3-235370 | (TP for L1L2Mob BLCR for TS 38.401) Reference configuration and Target Configuration ID in LTM | Google Inc. |
| R3-235371 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | Google Inc. |
| R3-235372 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification after successful cell switch | Google Inc. |
| R3-235375 | (TP for LTM BL CR to TS 38.401) Discussion on L1L2 triggered mobility | ZTE |
| R3-235621 | Further discussion on LTM | NTT DOCOMO INC.. |
| R3-235642 | Discussion on L1L2 based Inter-Cell Mobility | CMCC |
| R3-235643 | (TP to TS 38.401) L1L2 based Inter-Cell Mobility | CMCC |
| R3-235691 | [DRAFT] Reply LS to R2-2309251 = R3-235014 on Approaches during execution for inter-DU LTM (to: RAN2; cc: -; contact: Ericsson) | Ericsson |
| R3-235764 | Summary of offline discussion MobilityEnh_LTM | Huawei |
| R3-235827 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures | Huawei |
| R3-235894 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM | Ericsson |
| R3-235926 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on LTM procedures | Huawei, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235152 | (TP for CHO with NR-DC to TS 38.423, TS37.340): Avoid Multiple Data forwarding Path | ZTE |
| R3-235153 | (TP for CHO with NR-DC to TS 38.423, TS37.340): CHO with multiple SCG | ZTE |
| R3-235160 | [TPs to TS38423, TS37483 and TS37340, CHO with MRDC] Continuation of the discussions on enhancements for CHO with MR-DC | Nokia, Nokia Shanghai Bell |
| R3-235165 | (TP to BL CR for TS 38.423) Discussion on signaling support for CHO with SCGs | LG Electronics Inc. |
| R3-235166 | (TP to BL CR for TS 38.423) Completion for the avoidance of multiple data forwarding paths | LG Electronics Inc. |
| R3-235181 | (TPs to CHO with SCG BL CRs of TS 37.340 and TS 38.423) support of CHO with SCGs | Huawei |
| R3-235249 | (TP to TS 38.423 BLCR) CHO in NR-DC | Lenovo |
| R3-235250 | (TP for BLCR TS 38.423) Miscellaneous issues on CHO with multiple SCGs | Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, NEC, Huawei, LG Electronics, ZTE |
| R3-235263 | CHO with multiple candidate SCGs | Qualcomm Incorporated |
| R3-235268 | (TP to TS 38.423 BL CR) CHO with candidate SCG(s) | Ericsson |
| R3-235332 | (TP to BLCR TS38.423) Considerations on CHO in NR-DC | Samsung |
| R3-235349 | TP to BLCR for 38.423 on CHO with SCG and multiple SCGs | CATT |
| R3-235767 | Summary of offline discussion MobilityEnh_CHO | Samsung |
| R3-235873 | [TP to BL CR for TS 38.423, CHO with MRDC] Continuation of the discussions on enhancements for CHO with MR-DC | Nokia, Nokia Shanghai Bell |
| R3-235887 | (TP to TS 38.423 BL CR) CHO with candidate SCG(s) | Ericsson |
| R3-235927 | [TP to BL CR for TS 38.423, CHO with MRDC] Continuation of the discussions on enhancements for CHO with MR-DC | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Lenovo, Huawei, Samsung |
| R3-235928 | (TP to TS 38.423 BL CR) CHO with candidate SCG(s) | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235015 | Reply LS on security for selective SCG activation | RAN2(Nokia) |
| R3-235161 | Further development of the S-CPAC solution | Nokia, Nokia Shanghai Bell |
| R3-235167 | (TP to BL CR for TS 38.423) Discussion on subsequent CPAC | LG Electronics Inc. |
| R3-235182 | (TP to subsequent CPAC TS 38.423 BL CR) support of subsequent CPAC | Huawei |
| R3-235251 | (TP for BLCR TS 38.473) On Subsequent CPAC | Lenovo |
| R3-235265 | Subsequent CPAC in NR-DC | Qualcomm Incorporated |
| R3-235269 | (TP to TS 38.423 BL CR) Subsequent CPAC | Ericsson |
| R3-235285 | Discussion S-CPAC remaining issues (handling of S-SN, data forwarding, container for reference configuration) | NEC |
| R3-235286 | (TP to TS 38.423 on S-CPAC) S-CPAC related handling of S-SN, Data Forwarding, container for Reference Configuration | NEC |
| R3-235333 | Discussion on selective activation of the cell groups | Samsung |
| R3-235350 | Discussion on subsequent CPAC | CATT |
| R3-235369 | (TPs for Subsequent CPAC BLCR for TS 38.423 & TS 38.473) Reference SCG configuration | Google Inc. |
| R3-235376 | (TP to TS 38.423 and 37.340) Discussion on support of subsequent CPAC | ZTE |
| R3-235387 | Discussion on subsequent CPAC procedures | China Telecommunication |
| R3-235388 | (TP to BL CRs of TS 38.473) On support of subsequent CPAC procedures | China Telecommunication |
| R3-235622 | Security issue on subsequent CPAC | NTT DOCOMO INC.. |
| R3-235768 | Summary of offline discussion MobilityEnh_S-CPAC | Lenovo |
| R3-235845 | (TP for BLCR TS 38.473) On Subsequent CPAC | Lenovo |
| R3-235851 | (TP to BL CR for TS 37.340) on support of subsequent CPAC | ZTE, Ericsson, NEC |
| R3-235888 | (TP to TS 38.423 BL CR) Subsequent CPAC | Ericsson |
| R3-235929 | (TP to TS 38.423 BL CR) Subsequent CPAC | Ericsson, Google, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235035 | Reply to LS addressing packet loss | SA6(Ericsson) |
| R3-235061 | (BL CR to TS 38.423) Introduction of NR MBS enhancements | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, CATT, Samsung |
| R3-235062 | (BL CR to 38.470) Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell |
| R3-235085 | (BL CR to 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung |
| R3-235086 | (BL CR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-235087 | (BL CR to TS 38.413) Introduction of NR MBS enhancements | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, HW, Samsung,Ericsson |
| R3-235088 | (BL CR to TS 38.473) Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| R3-235117 | (BL CR to 38.410) Update of MBS RAN sharing solution | Qualcomm Inc, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Huawei |
| R3-235118 | (BL CR to TS 37.483) Introduction of NR MBS enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, Ericsson, CMCC, Samsung |
| R3-235151 | (BL CR to TS 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-235797 | Summary of offline discussion on Rel-18 MBS | CATT |
| R3-235962 | (BL CR to TS 37.483) Introduction of NR MBS enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, Ericsson, CMCC, Samsung |
| R3-235963 | (BL CR to 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung |
| R3-235964 | (BLCR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-235965 | (BL CR to TS 38.413) Introduction of NR MBS enhancements | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, Samsung, Ericsson, CMCC, CBN |
| R3-235966 | BLCR to 38.470) Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235967 | (BL CR to TS 38.473) Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| TDoc | Title | Source |
|---|---|---|
| R3-235144 | (TP to TS 37.483) Network sharing for MBS Broadcast | ZTE |
| R3-235183 | (TPs to MBS BL CRs) MBS reception in RAN sharing scenario | Huawei, CBN |
| R3-235207 | (TP for TS 37.483, TS 38.473) Discussion on MBS RAN sharing | Samsung |
| R3-235253 | Remaining issues of supporting MBS reception in RAN Sharing | Lenovo |
| R3-235272 | (TP for TS 38.470, 38.473) Resolution of RAN Sharing open points | Nokia, Nokia Shanghai Bell |
| R3-235278 | Support of MBS in RAN sharing scenarios | Qualcomm Incorporated |
| R3-235406 | Stage-2 CR for Introducing RAN OAM based solution for MBS RAN Sharing | Qualcomm Inc, Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, CMCC, FirstNet, ATT, Lenovo, MITRE, LGE,China Unicom, China Telecom,NTT DOCOMO, CBN, Google,NEC |
| R3-235415 | (TPs for BL CRs to TS 38.401, TS 38.473, TS 37.483) Discussion on efficient MBS reception in RAN sharing scenario | CATT |
| R3-235461 | [TPs for BL CRs to TS 38.473, 37.483, 38.413, 38.401, 38.300] Considerations, comments and content to progress Rel-18 work on MBS reception in RAN sharing scenarios | Ericsson |
| R3-235644 | Multicast Reception in RRC_INACTIVE state | CMCC |
| R3-235836 | (TP to BL CR for 38.300) Support of OAM based solution for RAN sharing scenario | Qualcomm Inc, Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, CMCC, FirstNet, ATT, Lenovo, MITRE, LGE,China Unicom, China Telecom,NTT DOCOMO, CBN, Google,NEC |
| R3-235837 | Summary for offline discussion MBS1_Networksharing | CATT |
| R3-235860 | (TP to BL CR for TS 38.413) Support of Broadcast in RAN sharing scenario | Huawei, CBN |
| R3-235861 | (TP for BL CR for TS 38.473) Support of Broadcast in RAN sharing scenario | Samsung |
| R3-235862 | (TP to BL CR for TS 37.483) Support of Broadcast in RAN sharing scenario | ZTE |
| R3-235863 | (TP for BLCR to 38.401) Support of Broadcast in RAN sharing scenario | CATT |
| R3-235907 | (TP to BL CR for 38.300) Support of OAM based solution for RAN sharing scenario | Qualcomm Inc, Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, CMCC, FirstNet, ATT, Lenovo, MITRE, LGE,China Unicom, China Telecom,NTT DOCOMO, CBN, Google,NEC |
| R3-235930 | (TP to BL CR for 38.300) Support of OAM based solution for RAN sharing scenario | Qualcomm Inc, Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung, CMCC, FirstNet, ATT, Lenovo, MITRE, LGE,China Unicom, China Telecom,NTT DOCOMO, CBN, Google,NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-235145 | (TP to 38.413, 38.473) Further thoughts on Multicast reception in RRC_INACTIVE | ZTE, Sanechips, CBN |
| R3-235184 | (TPs to MBS BL CRs) Multicast Reception for RRC_INACTIVE state UEs | Huawei, CBN |
| R3-235208 | (TP for BLCR TS 38.473) Discussion on MBS reception by inactive state UE | Samsung |
| R3-235252 | Discussion on multicast reception in RRC_INACTIVE | Lenovo |
| R3-235273 | (TP for TS 38.300, TS 38.423, TS 38.470, TS 38.473) Resolution of open points for MBS Reception in RRC Inactive State | Nokia, Nokia Shanghai Bell |
| R3-235279 | Enhancements to support Multicast reception by UEs in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-235414 | (TPs to BL CRs for TS 38.413, 38.423, 38.473) Discussion on Multicast over Inactive | CATT |
| R3-235462 | [TP for BL CR 38.473, 38.401] Continuation, clarification and contributions to progress Rel-18 work on support of multicast reception in RRC_INACTIVE | Ericsson |
| R3-235798 | (TP for TS 38.300) Update of MBS stage 2 | Nokia, Nokia Shanghai Bell |
| R3-235838 | Summary for offline discussion MBS2_INACTIVE | Ericsson |
| R3-235844 | [TP for BLCR for 38.473] Update of MBS RRC_INACTIVE reception | Ericsson |
| R3-235881 | (TP to TS 38.470 BL CR) Multicast Context Notification | Lenovo, Ericsson |
| R3-235886 | (TP to BL CR for TS 38.401) on Update of MBS RRC_INACTIVE reception | CMCC |
| R3-235931 | [TP for BLCR for 38.473] Update of MBS RRC_INACTIVE reception | Ericsson |
| R3-235932 | (TP to BL CR for TS 38.401) on Update of MBS RRC_INACTIVE reception | CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-235043 | (BL CR to 38.401) Introduction of NR SL relay enhancements | LG Electronics |
| R3-235107 | (BL CR to 38.300) Support of SL relay enhancements | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE, Huawei |
| R3-235108 | (BL CR to 38.413) Support for NR Sidelink Relay Enhancements | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei |
| R3-235109 | (BL CR to 38.423) Support NR Sidelink Relay Enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC |
| R3-235110 | (BL CR to 38.473) Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-235123 | (BL CR to 38.470) Support of NR SL relay enhancements | ZTE, CAICT, China Telecom, CATT, LG Electronics, Ericsson, Huawei |
| R3-235760 | Summary of offline discussion on SL relay enhancement | LG Electronics |
| R3-235769 | (BL CR to 38.401) Introduction of NR SL relay enhancements | LG Electronics |
| R3-235772 | Summary of offline discussion SLRelay | LG Electronics |
| R3-235998 | (BLCR to 38.401) Introduction of NR SL relay enhancements | LG Electronics, Huawei, Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235999 | (BL CR to 37.483) Introduce new indication for proactive data forwarding | Samsung, CATT, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-236000 | (BLCR to 38.473) Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| TDoc | Title | Source |
|---|---|---|
| R3-235156 | Remaining issues for service continuity | ZTE |
| R3-235169 | (TPs to BL CRs for TS 38.300, TS 37.483, 37.480, 38.401) Remaining open issues for service continuity enhancement | LG Electronics |
| R3-235261 | (TP for BLCR 38.413, 38.423, 37.483) Inter-gNB mobility | Huawei |
| R3-235270 | (TP for SL Relay BL CR to TS 38.300) Inter-gNB Service Continuity for L2 U2N Relay | Ericsson |
| R3-235293 | (TP for TS 38.300 on SL relay enhancement) on service continuity enhancement | NEC |
| R3-235362 | Remaining issues on service continuity | CMCC |
| R3-235393 | Discussion on service continuity leftover issues | China Telecommunication |
| R3-235453 | (TP for SL relay 38.300 and 37.483) Discussion on Support Service Continuity Enhancements | CATT |
| R3-235472 | Leftover issues on SL relay service continuity | Samsung |
| R3-235514 | (TP for TS37.483 BL CR) Discussion on Support Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-235810 | (TP for SL relay 37.483) Introduce new indication for proactive data forwarding | CATT |
| TDoc | Title | Source |
|---|---|---|
| R3-235157 | (TP to BL CR for TS 38.473, 38.470) Further discussion on multi-path relay support | ZTE |
| R3-235168 | (TP to BL CR for TS 37.480, 37.483, 38.473, 38.401) Further consideration on multi-path support | LG Electronics |
| R3-235262 | (TP for BLCR 38.473) Multi-path relay | Huawei |
| R3-235271 | (TP for SL Relay to TS 38.473) Multi-path for Sidelink Relay | Ericsson |
| R3-235294 | Discussion on remaining issue under multi-path relay | NEC |
| R3-235361 | (TP to TS 38.401 and TS 38.473) Discussion on multi path scenario 2 | CMCC |
| R3-235394 | Discussion on multi-path for sidelink relay | China Telecommunication |
| R3-235454 | (TP for SL relay 38.401) Discussion on Multi-path Support for SL relay | CATT |
| R3-235473 | Leftover issues on SL relay multipath | Samsung |
| R3-235515 | (TP for TS38.401 BL CR) discussion on the support for multi-path | Nokia, Nokia Shanghai Bell |
| R3-235746 | (TP for BLCR 38.473) Multi-path relay | Huawei |
| R3-235753 | Draft Reply LS to R2-2306781 = R3-233712 on mode 1 scheduling in inter-DU multi-path (to: RAN2; cc: -; contact: NEC) | NEC |
| R3-235761 | LS on handling of location information in multi-path operation (to: SA2; cc: RAN2; contact: LG Electronics) | RAN3 |
| R3-235770 | Reply LS to R2-2306781 = R3-233712 on mode 1 scheduling in inter-DU multi-path (to: RAN2; cc: -; contact: NEC) | RAN3 |
| R3-235771 | (TP for TS38.401 BL CR) discussion on the support for multi-path | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235057 | (BL CR to 38.300) Stage 2 BL CR for NR NTN | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-235063 | (BL CR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-235072 | (BL CR to 38.423) BL CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-235221 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
| R3-235839 | (BL CR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-235840 | (BLCR to 38.423) BL CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-235981 | (BLCR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-235982 | (BLCR to 38.423) BL CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| TDoc | Title | Source |
|---|---|---|
| R3-235023 | Reply LS on time-based trigger condition in NG HO for NR NTN | SA2(Samsung) |
| R3-235497 | Time Margin for CHO in NR NTN | Ericsson, Thales, ESA |
| R3-235498 | (TP to BL CR for TS 38.423) Time Margin for CHO in NR NTN - XnAP Impact | Ericsson, ESA, Thales |
| R3-235499 | (TP to BL CR for TS 38.423) Location-Triggered CHO for NR NTN | Ericsson, ESA, ZTE, Thales, Inmarsat |
| R3-235516 | (TP for TS38.413 BL CR and TS38.423 BL CR) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| R3-235696 | (TP to BL CR for TS 38.423) Location-Triggered CHO for NR NTN | Ericsson, ESA, ZTE, Thales, Inmarsat, Hughes |
| R3-235944 | (TP to BL CR for TS 38.413) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| R3-235945 | (TP to BL CR for TS 38.423) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235146 | Discussion on E-CID method for NTN | THALES, Huawei, Ericsson |
| R3-235215 | Consideration on OAM requirements for UE location verification | CATT,Ericsson, Huawei |
| R3-235216 | (TP to BL CR for TS 38.455, 38.300, 38.305)Positioning support for NR NTN UE location verification | CATT |
| R3-235254 | On NTN NW verified UE location | Lenovo |
| R3-235325 | (draftCR to 38.305, TP to BL CR for TS 38.300) Discussion on OAM configuration for network verified UE location | ZTE |
| R3-235326 | Discussion on mirror positions ambiguity for network verified UE location | ZTE |
| R3-235392 | Discussion on UE location verification for NTN | China Telecommunication |
| R3-235460 | (TP to BL CR for TS 38.455, 38.473) Discussion on TRP Information for NR NTN | Qualcomm Incorporated |
| R3-235463 | (TP to BL CR for TS 38.455) Discussion on Mirror Point Resolution and ECID Measurement | Qualcomm Incorporated |
| R3-235474 | Leftover issue on UE location verification | Samsung |
| R3-235496 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei |
| R3-235504 | (TP BL 38.300) OAM Requirements for UE Location Verification | Huawei, Ericsson, CATT |
| R3-235505 | Discussion on Altitude for the NTN TRP | Huawei, Thales, Ericsson |
| R3-235506 | (TP BL 38.455) NTN Access Point Position | Huawei, Thales, Ericsson |
| R3-235507 | Draft LS on Altitude for the Access Point (to: SA2; cc: CT1, CT4, SA5, RAN2, RAN1; contact: Huawei) | Huawei, Thales, Ericsson |
| R3-235508 | Mapped Cell Id Introduction for E-CID and NR NTN | Huawei, Thales, Ericsson |
| R3-235517 | Discussion on UE location verification | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235069 | (BL CR to 36.300) IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-235070 | (BL CR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-235071 | (BL CR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-235852 | (BL CR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-235853 | (BL CR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-235949 | (BLCR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-235950 | (BLCR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235143 | (TP to BL CR for TS 36.455, 36.300, 36.305) supporting of E-CID | CATT |
| R3-235327 | (TP for IoT NTN BL CR 36.423) Location-Triggered CHO for IoT NTN | ZTE, Ericsson, ESA, Thales |
| R3-235493 | Mapped Cell ID Introduction for E-CID and IoT NTN | Ericsson, Huawei, Thales |
| R3-235494 | (TP to BL CR for TS 36.455) NTN Access Point Position | Ericsson, Huawei, Thales |
| R3-235495 | (TP to BL CR for TS 38.423) Time Margin for CHO in IoT NTN - X2AP Impact | Ericsson, Inmarsat, ESA |
| R3-235509 | E-CID for Network UE location Verification | Huawei, Thales, Ericsson |
| R3-235518 | (TP for TS36.413 BL CR and TS36.423 BL CR) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| R3-235942 | (TP for TS 36.413 BL CR) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| R3-235943 | (TP for TS 36.423 BL CR) miscellaneous Correction on the BL CRs | Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235055 | (BL CR to 38.413) Introduction of Aerial authorization information | Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-235056 | (BL CR to 38.423) NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235045 | (BL CR to 38.423) Introduction on MT-SDT | Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo |
| R3-235047 | (BL CR to 38.473) Introduction on MT-SDT | China Telecom, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-235053 | (BL CR to 38.420) Introduction on MT-SDT | Lenovo, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-235095 | (BL CR to 37.483) Introduction of MT-SDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics |
| R3-235096 | (BL CR to 38.300) Introduction on MT-SDT | ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics |
| R3-235097 | (BL CR to 38.401) Introduction on MT-SDT | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics |
| R3-235132 | (BL CR to 37.480) Introduction on MT-SDT | LG Electronics, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235102 | (BL CR to 38.300) Introduction of NR Redcap Enhancement | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| R3-235103 | (BL CR to 38.410) Introduction of NR Redcap Enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235104 | (BL CR to 38.413) Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-235105 | (BL CR to TS 38.423) Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-235106 | (BL CR to 38.473) Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-235581 | WI work plan for Rel-18 RedCap | Ericsson |
| R3-235995 | Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-235996 | (BL CR to 38.413) Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-235997 | (BLCR to 38.473) Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| TDoc | Title | Source |
|---|---|---|
| R3-235005 | Reply LS on INACTIVE eDRX above 10.24sec and SDT | CT4(Ericsson) |
| R3-235020 | Reply LS on INACTIVE eDRX above 10.24sec and SDT | SA2(Ericsson) |
| R3-235154 | (TP to 38.423, 38.473, 38.300) Left issues on NR Redcap enhancement | ZTE |
| R3-235155 | (TP to 38.413) NR Redcap enhancement with MT-SDT | ZTE |
| R3-235213 | Support of MT-SDT in NR RedCap Enhancement | China Telecom |
| R3-235214 | (TP to BL CR for TS38.413) on support of MT-SDT in NR RedCap Enhancement | China Telecom |
| R3-235274 | (TP for TS 38.413) Finalization of eDRX for RRC_INACTIVE over NG | Nokia, Nokia Shanghai Bell |
| R3-235275 | (TP for TS 38.423) Finalization of eDRX for RRC_INACTIVE over Xn/F1 | Nokia, Nokia Shanghai Bell |
| R3-235311 | (TP to TS 38.413) Further discussion on long eDRX support for RRC_INACTIVE UE and draft LS to SA2 | Huawei |
| R3-235312 | (TP to TS 38.300) Further discussion on long eDRX support for RRC_INACTIVE UE | Huawei |
| R3-235313 | (TP to TS 38.423 and TS 38.473) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication |
| R3-235455 | (TP for eRedCap for 38.413) Discussion on MT Communication Handling | CATT |
| R3-235456 | Draft Reply LS to S2-2309757 = R3-235020 on INACTIVE eDRX above 10.24sec and SDT (to: SA2; cc: CT4; contact: CATT) | CATT |
| R3-235464 | Discussion on RRC Inactive with long eDRX for RedCap | Qualcomm Incorporated |
| R3-235465 | Draft Reply to S2-2309757 = R3-235020 on INACTIVE eDRX above 10.24sec and SDT (to: SA2; cc: RAN2, CT4; contact: Qualcomm) | Qualcomm Incorporated |
| R3-235582 | (TP to BL CR for TS 38.423) Discussion on support of data size in RAN PAGING REQUEST message | Ericsson |
| R3-235583 | (TPs to BL CRs for TS 38.423, 38.473) Discussion on eRedCap support indication over Xn and F1 | Ericsson |
| R3-235590 | [Draft] Reply LS to S2-2309757 = R3-235020, C4-233691 = R3-235005 on INACTIVE eDRX above 10.24sec and SDT (to: SA2, CT4; cc: RAN2; contact: Ericsson) | Ericsson LM |
| R3-235718 | Summary of offline discussion about R18eRedcap | Ericsson |
| R3-235756 | (TP to TS 38.473) Left issues on NR Redcap enhancement | ZTE |
| R3-235757 | (TP for TS 38.413) Finalization of eDRX for RRC_INACTIVE over NG | Nokia, Nokia Shanghai Bell |
| R3-235758 | (TP to TS 38.423 and TS 38.473) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication |
| R3-235759 | [Draft] Reply LS to S2-2309757 = R3-235020, C4-233691 = R3-235005 on INACTIVE eDRX above 10.24sec and SDT (to: SA2, CT4; cc: RAN2; contact: Ericsson) | Ericsson LM |
| R3-235765 | Reply LS to S2-2309757 = R3-235020, C4-233691 = R3-235005 on INACTIVE eDRX above 10.24sec and SDT (to: SA2, CT4; cc: RAN2; contact: Ericsson) | RAN3 |
| R3-235889 | (TP to BL CR for TS 38.423) Remaining issues on eRedCap UE access | Huawei, China Unicom, China Telecommunication, ZTE, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235044 | (BL CR to 38.413) Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235046 | (BL CR to TS 38.423) Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235098 | (BL CR to TS 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-235122 | (BL CR to 38.455) Support of NR Positioning Enhancements | CATT |
| R3-235751 | Summary of Positioning R18 offline discussion | CATT |
| R3-235788 | (BL CR to 38.413) Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235789 | (BLCR to 38.423) Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235790 | (BLCR to 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-235830 | Summary of offline discussion for remaining issues of Positioning | CATT |
| R3-235983 | (BL CR to 38.305) Support of NR Positioning Enhancements | Nokia, Nokia Shanghai Bell |
| R3-235984 | (BL CR to 38.413) Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235985 | (BL CR to 38.423) Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-235986 | (BL CR to 38.455) Support of NR Positioning Enhancements | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi, Samsung |
| R3-235987 | (BL CR to 38.470) Support of NR Positioning Enhancements | Samsung, Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Xiaomi |
| R3-235988 | (BL CR to TS 38.473) Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235017 | LS on SL positioning and CPP measurements report mapping | RAN4(CATT) |
| R3-235434 | [Draft LS out] Discussion on SL positioning authorization | ZTE, CATT, CMCC |
| R3-235477 | Further discussion on sidelink positioning and others | Samsung |
| R3-235635 | (TP to BL CRs for TS 38.413 and TS 38.423) Discussion on Sidelink Positioning | Xiaomi, Ericsson, Huawei |
| R3-235636 | draft LS on Authorization Information for Ranging and SL positioning service (to: SA2; cc: RAN2, CT4; contact: Xiaomi) | Xiaomi, Ericsson, Huawei |
| R3-235791 | draft reply LS to S2-2305734 = R3-232507 on Authorization Information for Ranging and SL positioning service (to: SA2; cc: RAN2, CT4; contact: Xiaomi) | Xiaomi, Ericsson, Huawei |
| R3-235792 | (TP for BL CR TS 38.413) clarification on Ranging and Sidelink Positioning Service Information | Xiaomi, Ericsson, Huawei, ZTE, Samsung, CATT |
| R3-235793 | (TP to BL CRs for TS 38.423) Discussion on Sidelink Positioning | Samsung |
| R3-235794 | (TP to BL CRs for TS 38.473) Discussion on Sidelink Positioning | ZTE |
| R3-235933 | Reply LS to S2-2305734 = R3-232507 on Authorization Information for Ranging and SL positioning service (to: SA2; cc: RAN2, CT4; contact: Xiaomi) | RAN3 |
| TDoc | Title | Source |
|---|---|---|
| R3-235006 | Reply LS on LPHAP | RAN1(Huawei) |
| R3-235007 | LS on the longer PRS/SRS periodicity for LPHAP (R1-2308571) | RAN1(Huawei) |
| R3-235217 | (TP to BL CR for TS 38.455, 38.305) on support of LPHAP | CATT |
| R3-235478 | Further discussion on LPHAP | Samsung |
| R3-235500 | (TPs to BL CRs for TS 38.455, 38.473, 38.470, 38.413) Discussion on LPHAP | Huawei |
| R3-235546 | Further details of SRS resource coordination within a validity area | Nokia, Nokia Shanghai Bell |
| R3-235557 | Enhancements for LPHAP | Qualcomm Incorporated |
| R3-235584 | (TPs to BL CRs for TS 38.455 and TS 38.473) Way forward on LPHAP | Ericsson |
| R3-235627 | (TP to 38.455&38.473) Discussion on LPHAP impacts | ZTE |
| R3-235637 | (TP to BL CR for TS 38.455) support of LPHAP | Xiaomi |
| R3-235811 | (TP to BL CR for TS 38.455) Support of cross-cell SRS configuration | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Xiaomi |
| R3-235812 | (TP to BL CR for TS 38.305) Support of cross-cell SRS configuration | CATT |
| R3-235814 | (TP to BL CR for TS 38.473) Support of cross-cell SRS configuration | Ericsson, Huawei, CATT, Xiaomi, ZTE |
| R3-235815 | (TP to BL CR for TS 38.413) Support of cross-cell SRS configuration | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Xiaomi |
| R3-235816 | TP to BL CR for TS 38.470) Support of cross-cell SRS configuration | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Xiaomi |
| R3-235934 | TP to BL CR for TS 38.470) Support of cross-cell SRS configuration | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Samsung, Xiaomi |
| TDoc | Title | Source |
|---|---|---|
| R3-235009 | Reply LS on PRU Procedures | RAN1(CATT) |
| R3-235018 | Reply LS on LPHAP | RAN4(Huawei) |
| R3-235218 | (TP to BL CR for TS 38.455) On the details of Carrier Phase Positioning | CATT |
| R3-235501 | Discussion on CPP and Bandwdith Aggregation | Huawei |
| R3-235548 | (TP for TS 38.455 BL CR) Resolution of open issues for UL CPP | Nokia, Nokia Shanghai Bell |
| R3-235585 | (TP to BL CR for TS 38.455) Discussion on CPP aspects and other topics | Ericsson |
| R3-235626 | [TP for 38.455 & 38.473 BLCR] Discussion on other positioning impacts | ZTE |
| R3-235638 | (TP to BL CR for TS 38.455) Discussion on CPP and SRS aggregation | Xiaomi |
| R3-235813 | (TP for TS 38.455 BL CR) Update of CPP parameters | Nokia, Nokia Shanghai Bell |
| R3-235829 | (TP to BL CR for TS 38.473) Update of CPP parameters | Nokia |
| TDoc | Title | Source |
|---|---|---|
| R3-235073 | (BL CR to 38.423) Network energy saving techniques | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-235074 | (BL CR to 38.473) Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| R3-235115 | (BL CR to 38.300) Introduction of Network Energy Saving | ZTE, Ericsson |
| R3-235174 | WI Work plan for R18 network energy savings | Huawei |
| R3-235571 | TP to the XnAP 38.423 Baseline CR for Correction | Ericsson |
| R3-235951 | (BLCR to 38.423) Network energy saving techniques | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-235952 | (BL CR to 38.470) Network energy saving techniques | Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| R3-235175 | (TP to Netw_Energy_NR BLCR for TS 38.423) Network energy saving techniques | Huawei |
| R3-235176 | (TP to Netw_Energy_NR BLCR for TS 38.473, 38.413, 38.470 and 38.300) Network energy saving techniques | Huawei |
| R3-235200 | Discussion on network energy saving | Samsung |
| R3-235201 | Introduction of Network Energy Saving for Paging IDLE UE | Samsung |
| R3-235226 | Discussion on Cell DTX/DRX for NES | CATT |
| R3-235227 | (TP to NES BL CR for TS 38.423) Paging Enhancement for NES | CATT |
| R3-235310 | Open issues on NES techniques | Qualcomm Incorporated |
| R3-235431 | Discssion on network energy saving | Lenovo |
| R3-235565 | (TP to TS 38.423) Support of network energy saving techniques | Nokia, Nokia Shanghai Bell |
| R3-235566 | (TP to BL CR TS 38.473) Beam deactivation decision and signalling for energy saving | Nokia, Nokia Shanghai Bell |
| R3-235572 | Introduction of Network Energy Saving | Ericsson |
| R3-235573 | (TP to BL CR for TS 38.423) Introduction of Network Energy Saving | Ericsson |
| R3-235668 | Discussion on network energy saving | ZTE |
| R3-235669 | TPs to BL CRs for network energy saving | ZTE |
| R3-235799 | Summary of offline discussion EnergySaving | Huawei |
| R3-235849 | (TP to Netw_Energy_NR BLCR for TS 38.470) Network energy saving techniques | Huawei |
| R3-235850 | (TP to BL CR TS38.300) for network energy saving | ZTE |
| R3-235908 | (TP to BL CR TS38.300) for network energy saving | ZTE |
| R3-235935 | (TP to BL CR TS 38.470) Network energy saving techniques | Huawei, ZTE, Samsung, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235124 | (BL CR to 37.483) Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235125 | (BL CR to 38.300) for XR Enhancements | Qualcomm Inc, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-235126 | (BL CR to 38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom, ZTE |
| R3-235127 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc |
| R3-235128 | (BL CR to TS 38.423) Introduction of XR enhancement | Ericsson, ZTE |
| R3-235129 | (BL CR to 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc |
| R3-235130 | (BL CR to 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235519 | Work Plan for Rel-18 on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| R3-235719 | (XR BL CR to 38.423) Introduction of XR enhancement | Ericsson, ZTE |
| R3-236001 | (BL CR to 38.300) for XR Enhancements | Qualcomm Inc, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-236002 | (BL CR to 38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom, ZTE |
| R3-236003 | (XR BL CR to TS 38.423) Introduction of XR enhancement | Ericsson, ZTE, Qualcomm Inc., Nokia, Nokia Shanghai Bell |
| R3-236004 | (BL CR to 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-236005 | (BLCR to 37.483) Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-236006 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc |
| R3-236007 | (BL CR to 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc |
| TDoc | Title | Source |
|---|---|---|
| R3-235027 | LS Reply on Design of RTP Header Extension for PDU Set Handling | SA4(Lenovo) |
| R3-235204 | Discussion on the support of PDU Set handling | Samsung |
| R3-235205 | [TP for BLCR TS 38.413 TS 37.483 TS 38.415] Introducing enhancement for NR XR | Samsung |
| R3-235255 | Discussion on User Plane Protocol for PDU Set Information | Lenovo, Ericsson |
| R3-235280 | XR Enhancements for PDU Set Handling | Qualcomm Incorporated |
| R3-235377 | (TP to TS 38.413) Discussion on support of PDU Set Handling | ZTE |
| R3-235378 | TP for XR BL CR to TS 38.415 | ZTE |
| R3-235423 | (TP for NR_XR_enh BL CRs): Add PDU set parameters for support NR XR | Huawei |
| R3-235424 | (TP for NR_XR_enh BL CR for TS38.413) Non-homogeneous PDU set handling and TSCAI handling | Huawei |
| R3-235457 | Discussion on PDU set handling for XR | CATT |
| R3-235520 | Discussion on support for PDU Set based QoS handling | Nokia, Nokia Shanghai Bell |
| R3-235521 | (TP for TS 38.413 BL CR) Support for NR XR | Nokia, Nokia Shanghai Bell |
| R3-235531 | Discussion on open issues related to PDU Set handling | LG Electronics Inc. |
| R3-235586 | Discussion on XR PDU Set Handling | Ericsson |
| R3-235587 | (TPs to TSes 38.413 and 38.423 BL CRs): addition of NG-RAN capability support information to SMF | Ericsson |
| R3-235588 | [Draft] Reply LS to S2-2308252 = R3-233735 on Non-homogeneous deployment of PDU Set based handling (to: SA2, CT4; cc: RAN2; contact: Ericsson) | Ericsson |
| R3-235639 | (TPs for TS 38.300 and TS 38.413) PDU set based handling for XR | Xiaomi |
| R3-235646 | (TP for TS 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, ZTE |
| R3-235647 | Discussion on PDU Set handling | CMCC |
| R3-235649 | Discussion on XR Enhancement in Split Architecture | China Telecom |
| R3-235650 | (TP for BL CR for TS 38.401) Introduction of XR enhancements | China Telecom |
| R3-235722 | Summary of offline discussion CB PDUSethandling | Ericsson |
| R3-235802 | (TP for BL CR TS 38.413) Addition of UL PDU Set QoS parameters | Huawei, Ericsson, Qualcomm |
| R3-235824 | [TP for BLCR TS 37.483] Addition of UL PDU Set QoS parameters | Samsung, Ericsson |
| R3-235825 | [TP for BLCR TS 38.423] Addition of UL PDU Set QoS parameters | ZTE, Ericsson |
| R3-235826 | [TP for BLCR TS 38.473] Addition of UL PDU Set QoS parameters | Nokia, Ericsson |
| R3-235874 | Draft LS on provisioning separate DL and UL PDU Set QoS Parameters to NG-RAN (to: SA2; cc: RAN2; contact: Qualcomm) | Qualcomm, Ericsson |
| R3-235875 | (TP for NR_XR_enh BL CR for TS 38.300) Support for XR Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-235890 | LS on provisioning separate DL and UL PDU Set QoS Parameters to NG-RAN (to: SA2; cc: RAN2; contact: Qualcomm) | RAN3 |
| R3-235891 | (TP for NR_XR_enh BL CR for TS 38.300) Support for XR Enhancements | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235206 | [TP for BLCR TS 38.413, TS 38.423, TS 37.483] Introducing enhancement for NR XR ECN and discarding | Samsung |
| R3-235256 | Discussion on PDU Set handling in non-homogenous cases, PDU Set based discard and data forwarding | Lenovo |
| R3-235257 | Discussion on ECN marking for L4S | Lenovo |
| R3-235281 | RAN Enhancements for DL PDU Set Discarding and ECN marking | Qualcomm Incorporated |
| R3-235379 | (TP to TS 38.415 and 38.413) Discussion on ECN marking and PDU Set discard | ZTE |
| R3-235425 | (TP for NR_XR_enh BL CRs) Discussion on open issues for support NR XR | Huawei |
| R3-235458 | Discussion on ECN Marking and others for XR | CATT |
| R3-235459 | (TP for 38.413 and 37.483) Support Enhancements on NR XR | CATT |
| R3-235522 | Discussion on ECN marking for NR XR | Nokia, Nokia Shanghai Bell |
| R3-235683 | Support for L4S in NG-RAN | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235684 | (TP for XR CR for TS 38.300) ECN Marking for L4S | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235685 | (TP for XR CR for TS 38.415) ECN Marking for L4S | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235686 | (TP for XR CR for TS 38.425) ECN Marking for L4S | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235687 | (TP for XR CR for TS 38.473) ECN Marking for L4S | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235688 | (TP for XR CR for TS 38.413) ECN Marking for L4S | Ericsson, Orange, Deutsche Telekom, AT&T, Verizon Wireless |
| R3-235723 | Summary of offline discussion CB XR_ECNMarking | ZTE |
| R3-235831 | (TP to TS 38.415) support for ECN Marking | ZTE |
| R3-235832 | (TP to BL CR TS 38.473) support for ECN Marking | Huawei |
| R3-235833 | (TP to BL CR TS 37.483) support for ECN Marking | Samsung |
| R3-235841 | (TP to BL CR TS 38.425) support for ECN Marking | CMCC, ZTE |
| R3-235842 | (TP to BL CR TS 38.423) support for ECN Marking | Ericsson, ZTE |
| R3-235843 | TP to BL CR TS 38.413) support for ECN Marking | Nokia, Nokia Shanghai Bell, ZTE |
| R3-235876 | (TP for XR CR for TS 38.423) ECN Marking for L4S activation/deactivation procedures | Ericsson |
| R3-235896 | (TP to BL CR TS 37.483) support for ECN Marking | Samsung |
| R3-235936 | (TP to BL CR TS 38.423) support for ECN Marking | Ericsson, ZTE |
| R3-235937 | TP to BL CR TS 38.413) support for ECN Marking | Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-235938 | (TP to BL CR TS 38.473) support for ECN Marking | Huawei, Samsung |
| R3-235939 | (TP to BL CR TS 37.483) support for ECN Marking | Samsung, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| R3-235042 | (BL CR to 29.413) Support of the enhanced NPN phase 2 | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson |
| R3-235048 | (BL CR to 38.300) On introduction of R18 eNPN | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-235066 | (BL CR to 38.413) Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-235067 | (BL CR to 38.423) Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| TDoc | Title | Source |
|---|---|---|
| R3-235111 | (BL CR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-235112 | (BL CR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-235113 | (BL CR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-235131 | (BL CR for 38.401) Introduction of 5G Timing Resiliency and URLLC enhancements | Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT, Ericsson, Huawei, ZTE |
| R3-235147 | (TP for TS 38.413 BL CR) Resolution of open issues for timing resiliency | Nokia, Nokia Shanghai Bell |
| R3-235148 | (TP for TS 38.413 BL CR) Resolution of open issues for URLLC | Nokia, Nokia Shanghai Bell |
| R3-235171 | (TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of 5G Timing Resiliency enhancements | Huawei, China Unicom |
| R3-235172 | (TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of RAN feedback enhancements | Huawei, China Unicom |
| R3-235173 | (TP to TRS_URLLC BLCR for TS 38.413) Support of TSN enabled transport network | Huawei, China Unicom, China Telecommunication |
| R3-235351 | TP for 38.300 on Introduction of 5G Timing Resiliency and URLLC enhancements | CATT |
| R3-235352 | Discussion on Adapting downstream and upstream scheduling | CATT |
| R3-235373 | (BL CR to 38.410) Introduction of 5G Timing Resiliency and URLLC enhancements | Samsung |
| R3-235374 | Discussion on open issues for RAN feedback | Samsung |
| R3-235383 | (TP for BL CR for TS 38.470) Introduction of 5G Timing Resiliency and URLLC enhancements | China Telecom,ZTE,Huawei |
| R3-235384 | (BL CR to 38.470) Introduction of 5G Timing Resiliency and URLLC enhancements | China Telecom,ZTE,Huawei |
| R3-235468 | Discussion on Open Issues in Timing Resiliency and uRLLC | Qualcomm Incorporated |
| R3-235469 | (TP to TS 38.300) Introduction of 5G Timing Resiliency and URLLC enhancements | Qualcomm Incorporated |
| R3-235574 | Support NR Timing Resiliency and URLLC enhancements | Ericsson |
| R3-235575 | Further discussion on Support NR Timing Resiliency and URLLC enhancements | Ericsson |
| R3-235670 | (TPs to BL CRs for TS 38.413, 38.473) Discussion and TPs for timing synchronization status and reporting | ZTE |
| R3-235671 | (TPs to BL CRs for TS 38.413, 38.473) Discussion on TSN integration and RAN feedback | ZTE |
| R3-235749 | (BL CR to 38.470) Introduction of 5G Timing Resiliency and URLLC enhancements | China Telecom,ZTE,Huawei |
| R3-235750 | Summary of offline discussion R18URLLC | Nokia |
| R3-235817 | (TP for BL CR TS 38.413) Resolution of open issues for TRS_URLLC | Huawei, China Unicom |
| R3-235818 | (TP for BL CR TS 38.473) Resolution of open issues for TRS_URLLC | ZTE |
| R3-235819 | (TP for BL CR TS 38.423) Resolution of open issues for TRS_URLLC | Ericsson |
| R3-235820 | Draft LS on timing resiliency (to: RAN2, SA2, CT4; cc: -; contact: Nokia) | Nokia |
| R3-235940 | (TP for BL CR TS 38.423) Resolution of open issues for TRS_URLLC | Ericsson |
| R3-235941 | LS on timing resiliency (to: RAN2, SA2, CT4; cc: -; contact: Nokia) | RAN3 |
| R3-236009 | (BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-236010 | (BL CR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-236011 | (BL CR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| TDoc | Title | Source |
|---|---|---|
| R3-235030 | LS on Response to Reply LS on Support of network slices which have area of service not matching deployed tracking areas | SA5(Huawei) |
| R3-235068 | (BL CR to 38.413) Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell |
| R3-235114 | (BL CR to 38.300) Enhancement of RAN Slicing for NR | ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-235178 | (TP to eNS_Ph3 BLCR for TS 38.300) Enhanced network slicing phase 3 | Huawei |
| R3-235179 | (TP to eNS_Ph3 BLCR for TS 38.413) Partially allowed NSSAI in a registration area | Huawei |
| R3-235276 | (TP for TS 38.413 and TS 38.423) Support of Network Slice Service Continuity | Nokia, Nokia Shanghai Bell, Orange |
| R3-235277 | (TP for TS 38.413) Support of Partially Allowed NSSAI | Nokia, Nokia Shanghai Bell, Orange |
| R3-235343 | Discussion on remaining open issues for RAN slicing | LG Electronics |
| R3-235344 | (TP to TS 38.413 and 38.423) TP for RAN slicing enhancement | LG Electronics |
| R3-235353 | TP to BLCR for 38.300 on supporting Partially Allowed NSSAI | CATT |
| R3-235354 | TP for 38.423 for supporting alternative S-NSSAI | CATT |
| R3-235391 | Discussion on support of Network Slice Service Continuity | China Telecommunication |
| R3-235446 | (TPs for BLCRs for 38.473 38.300)RAN impact on supporting Network Slice Service continuity scenario | ZTE |
| R3-235447 | RAN impact on support Partially Allowed NSSAI | ZTE |
| R3-235479 | Remaining issues on the enhancement of RAN slicing | Samsung |
| R3-235592 | (TP for slicing CR for TS 38.300) Clarifications on Partially Allowed NSSAI | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-235593 | Clarifications on Partially Allowed NSSAI | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-235594 | Draft LS on the use of Target NSSAI for optimised slice based mobility (to: SA2; cc: -; conclusion: Ericsson) | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-235595 | Clarifications and Way Forward on Network Slice Service Continuity | Ericsson |
| R3-235596 | Clarification on the use of S-NSSAI in PDU Session Resource Modify | Ericsson |
| R3-235645 | Discussion on network slice service continuity | CMCC |
| R3-235752 | (TP for BLCR for 38.473) RAN impact on supporting Network Slice Service continuity scenario | ZTE |
| R3-235755 | Summary of offline discussion R18Slice | ZTE |
| R3-235778 | (TP for TS 38.413) Support of Partially Allowed NSSAI | Nokia, Nokia Shanghai Bell, Orange |
| R3-235800 | (TP to eNS_Ph3 BLCR for TS 38.300) Enhanced network slicing phase 3 | Huawei, Nokia, Nokia Shanghai Bell |
| R3-235801 | (TP for BLCR for 38.300) RAN impact on supporting Network Slice Service continuity scenario | ZTE |
| R3-235892 | (TP for BLCR for 38.300) RAN impact on supporting Network Slice Service continuity scenario | ZTE |
| R3-235946 | (BL CR to 38.300) Enhancement of RAN Slicing for NR | ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-235947 | (BL CR to 38.413) Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell |
| R3-235948 | (BL CR to 38.473) RAN impact on supporting Network Slice Service continuity scenario | CATT, ZTE |
| TDoc | Title | Source |
|---|---|---|
| R3-235180 | Introduction of measurements without gap with interruption | Huawei, Deutsche Telekom, BT |
| R3-235188 | (TP to MT-SDT TS 38.423 BL CR) Correction on the MT-SDT Data Size | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm Incorporated, China Unicom |
| R3-235202 | Discussion on HARQ Related Assistance Information in NR User Plane | Samsung, China Telecom, CMCC, Lenovo |
| R3-235203 | Correction for HARQ Related Assisstance Information in NR User Plane | Samsung, China Telecom, CMCC, Lenovo |
| R3-235330 | Discussion on Avoiding unnecessary setup of DRB(s) in indirect data forwarding | Samsung, ZTE, CATT, LG Electronics |
| R3-235331 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung, CATT, LG Electronics |
| R3-235367 | Indirect data forwarding produce to avoid unnecessary setup of DRB(s) [Indirect Data forwarding] | ZTE, Samsung, CATT, LG Electronics |
| R3-235380 | Discussion on corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom |
| R3-235381 | Corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell, CATT |
| R3-235382 | Corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell, CATT |
| R3-235412 | Discussion on MRB PDCP count “wrap around” problem | CATT,CBN |
| R3-235413 | Correction on MRB PDCP count “wrap around” problem | CATT, CBN |
| R3-235438 | Correction of NAS Non Delivery Indication | Huawei |
| R3-235545 | Correction of Transport Addresses | Nokia, Nokia Shanghai Bell, Huawei |
| R3-235676 | TP for TS 38.300 draft CR on Rel-18 NCR | ZTE, China Telecom, Ericsson, Xiaomi, LG Electronics, China Unicom, CATT, Samsung, CMCC, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, NEC |
| R3-235677 | Further discussion on capturing RAN1 agreement in draft CR | ZTE, China Telecom, Ericsson, Xiaomi, LG Electronics, China Unicom, CATT, Samsung, CMCC, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, NEC |
| R3-235689 | Correction on the MN initiated SN Modification procedure | Ericsson |
| R3-235706 | (TP to MT-SDT TS 38.423 BL CR) Correction on the MT-SDT Data Size | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, ZTE, Qualcomm Incorporated, China Unicom |
| R3-235707 | TP for TS 38.300 draft CR on Rel-18 NCR | ZTE, China Telecom, Ericsson, Xiaomi, LG Electronics, China Unicom, CATT, Samsung, CMCC, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, NEC |
| R3-235708 | Summary of offline discussion CB #8HARQAssistanceInfor | Samsung |
| R3-235709 | Summary of offline discussion CB #9 IndirectDataFrowarding | Samsung |
| R3-235710 | Summary of offline discussion CB #10 PDUSessionSplit | ZTE |
| R3-235711 | Correction of Transport Addresses | Nokia, Nokia Shanghai Bell, Huawei |
| R3-235774 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding [Indirect Data forwarding] | Samsung, CATT, LG Electronics |
| R3-235877 | Correction for HARQ Related Assisstance Information in NR User Plane | Samsung, ZTE, China Telecom, CMCC, Lenovo, Qualcomm |
| R3-235979 | (BLCR to 38.423) Introduction of MT-SDT | Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo |
| R3-235980 | (BL CR to 38.300) BL CR for Network Controlled Repeater management | ZTE, China Telecom, Samsung,CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| TDoc | Title | Source |
|---|---|---|
| R3-235158 | The slice availability for SN change procedure - further discussion | Nokia, Nokia Shanghai Bell |
| R3-235159 | The slice availability for SN change procedure | Nokia, Nokia Shanghai Bell |
| R3-235189 | Consideration on large size UL SDT data in case of without anchor relocation | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom |
| R3-235190 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom |
| R3-235191 | (TP to R3-234736 to TS 38.300) Correction on large size UL SDT data in case of without anchor relocation | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom |
| R3-235219 | Discussion on Inactive Positioning in SDT without anchor relocation | CATT, Huawei, Ericsson, Samsung, CMCC, ZTE, Xiaomi, LG Electronics |
| R3-235220 | Support of Inactive Positioning in SDT without anchor relocation case | CATT, Huawei, Ericsson, Samsung, CMCC, ZTE, Xiaomi, LG Electronics |
| R3-235318 | Support of less than 5MHz Bandwidth for FR1 over Xn and F1 | China Telecom,Ericsson,ZTE |
| R3-235319 | introduction of 3 MHz channel bandwidth | Ericsson,China Telecom, ZTE |
| R3-235328 | introduction of 3 MHz channel bandwidth | ZTE, China Telecom, Ericsson |
| R3-235329 | Draft LS on introduction of 3MHz Channel Bandwidth over Xn and F1 interface (to: RAN4; cc: RAN1, RAN2; contact: China Telecom) | China Telecom |
| R3-235502 | Discussion on positioning in inactive mode for SDT without anchor relocation | Huawei, CATT, Samsung, Ericsson, LG Electronics |
| R3-235503 | Positioning inactive mode for SDT without anchor relocation | Huawei, CATT, Samsung, CMCC, ZTE, Ericsson, LG Electronics |
| R3-235532 | Positioning inactive mode for SDT without anchor relocation | Huawei, CATT, Samsung, CMCC, ZTE, Ericsson, LG Electronics |
| R3-235533 | TEI18 RRC Inactive enhancements | Ericsson |
| R3-235547 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Samsung, Qualcomm Incorporated, CATT, Orange, China Unicom, Deutsche Telekom |
| R3-235549 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Qualcomm Incorporated, Orange, China Unicom, Deutsche Telekom |
| R3-235550 | Reporting of MBS Load | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated |
| R3-235589 | (TPs to BL CRs for TS 38.423, 38.455, 38.423) Discussion on enhancement for positioning | Ericsson |
| R3-235712 | Summary of offline discussion CB #11 SliceZeroResource | Nokia |
| R3-235713 | Positioning inactive mode for SDT without anchor relocation [POS_SDT] | Huawei, CATT, Samsung, CMCC, ZTE, Ericsson, LG Electronics, Xiaomi |
| R3-235714 | Support of Inactive Positioning in SDT without anchor relocation case [POS_SDT] | CATT, Huawei, Ericsson, Samsung, CMCC, ZTE, Xiaomi, LG Electronics |
| R3-235715 | Summary of offline discussion CB #12 ULSDT | Huawei |
| R3-235716 | introduction of 3 MHz channel bandwidth | Ericsson, China Telecom, ZTE, Nokia, Nokia Shanghai Bell |
| R3-235717 | introduction of 3 MHz channel bandwidth | ZTE, China Telecom, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-235720 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom, ZTE, LG Electronics, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-235721 | (TP to R3-234736 to TS 38.300) Correction on large size UL SDT data in case of without anchor relocation | Huawei, China Telecom, Ericsson, Qualcomm Incorporated, China Unicom, ZTE, LG Electronics, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-235847 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Qualcomm Incorporated, Orange, China Unicom, Deutsche Telekom |
| R3-235893 | Signalling cells configured with zero resources for a slice | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Qualcomm Incorporated, Orange, China Unicom, Deutsche Telekom, Samsung, CMCC |
| R3-236008 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, LG Electronics, China Telecom, Samsung, Ericsson |