3GPP RAN#94e: Electronic meeting, 6 - 17 December 2021
Summary
This e-meeting lasted two weeks. For only the second time, more than 1000 Tdocs were submitted. Unlike the first time, this time most of them were covered because of the two-week timeframe. Week 1 focused on new Rel-18 topics and RAN5 (conformance testing) while week 2 prioritised other topics and finalising the Rel-18 work package.
Planning and Timelines
There was no discussion during this meeting in planning and timeline issues. Before the meeting it had already been decided that due to the COVID-19 situation all RAN WG meetings until June 2022 will be electronic.
Release 17 - RAN
Planning: No changes in planning, but there are still some unfinished Stage 2 Work Items; RAN1 work is largely completed.
- Stage 1: frozen in December 2019 with some exceptions; all remaining Stage 1 work was completed by June 2020
- RAN "Feature Packaging" ("Content definition") achieved December 2019
- Stage 2: frozen June 2021 with exceptions; in December 2021 there are still some unfinished Work Items (see list below)
- RAN1: freezing target December 2021; largely achieved, but no formal "freeze" declared
- RAN2 and RAN3: freezing target March 2022
- Stage 3: freezing target March 2022
- ASN.1 and open APIs: freezing target June 2022
- RAN4: freezing target September 2022
Release 17 - SA
Stage 2 Work Items not yet finished in TSG SA (all in SA2)
- Support for Minimisation of service Interruption (MINT)
- Non-Public Networks (eNPN)
- Multicast-Broadcast (5MBS)
- Network Slicing (eNS)
- Proximity Services (5G_ProSe)
- Multimedia Priority Service (MPS)
- Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS)
Rel-17 Closed Work Items and Study Items (excluding spectrum-related and conformance testing)
The following Rel-17 work was completed and the corresponding SIs and WIs closed:
NR: SI: Study on XR evaluations for NR
LTE: <None>
Rel-17 Work Item Summaries (descriptions of features in the release after the work has actually finished): <None in RAN>
Rel-17 NR: 6GHz topics (Endorsed WF: RP-213694; Approved LS: RP-213698; Approved revised WIDs: RP-213604, RP-213683, RP-213696; Summaries: RP-213612, RP-213628, RP-213699)
Companies could not agree on any Text Proposal for the Study Item. The main issue is a different understanding on what "regulatory" means. The same problem occurred in the discussion on interpreting the LS input from RCC (the telecoms regulatory organization of Russia, ex-Soviet states and neighbouring countries). Some companies said this input was not mandating implementation to RCC member states and therefore the WI on 6GHz in licensed band should not start, which was opposed by many other companies. It was decided to start that WI in Q1, but work is supposed to be restricted to the frequency range and requirements provided by RCC only. A new band for unlicensed operation in the lower 6GHz band was defined as 5.925-6.425GHz. The EU/CEPT NS flag(s) will be explicitly limited to the 5.945-6.425GHz range.
Rel-17 NR: pi/2 BPSK uplink power in NR (Endorsed WF: RP-213532; "Postponed" CRs: RP-213533, RP-213534; Summary: RP-213613)
A Way Forward was found to include the Indian 5Gi technology in 3GPP. The CRs are "postponed" until TSDSI has officially (via official LS to 3GPP, ITU and Indian Government) committed not to develop 5Gi further outside of 3GPP.
Rel-17 NR: Sidelink Enhancement (SR: RP-212880; Summary: RP-213660)
RAN1 was tasked to complete remaining normative work for Rel-17 by Q1 of 2022. All RAN1 decisions that impact other WGs should be finalized in RAN1#107bis-e
The list of open issues provided in RP-212880 (SR) will be used a starting point for technical discussions in RAN1.
• This does not mean that all issues included in the list are considered essential or that list is complete
• RAN1 should not spend additional effort to further refine the list
Rel-17 NR: Coverage Enhancements (SR: RP-213684; Summary: RP-213615)
For the determination of the index of the starting coded bit in a transmitted slot for TBoMS RAN decided to adopt Option C:
For each transmitted slot for TBoMS, the index of the starting coded bit in the circular buffer is the index continuous from the position of the last bit selected in the previous allocated slot, regardless of whether UCI multiplexing occurred in the previous allocated slot or not. RAN1 was tasked to work on the corresponding CR(s) for RAN#95e.
Rel-17 NR: Reduced Capability (Summary: RP-213689)
Agreement from RAN#93e (RP-212634) remains an agreement. No RAN4 time to be spent discussing the 3 cases (covered by the RAN#93e agreement) in Rel-17. Regarding RedCap Idle mode operation:
- Scheme 1 (i.e. UE in IDLE and INACTIVE monitors paging in an initial BWP associated with CD-SSB) is adopted for further work in Rel-17. Scheme 2 (i.e. UE in IDLE and INACTIVE monitors paging in an initial BWP associated with NCD-SSB) is not considered further in Rel-17
- RAN2 should work on the assumption that the cell reselection measurements and cell ranking are performed based on measurements on the CD-SSB. This applies for intra- and inter-frequency measurements, and for IDLE and INACTIVE states.
Rel-17 NR: IIoT/URLLC (Summary: RP-213673)
Capability 3 was dropped because it cannot be finished in one quarter. The issue whether to support the multiplexing of UCI of different PHY priorities also for PUCCH format 2 was left for RAN1 to decide. RAN1 is tasked to complete remaining normative work for Rel-17 Enhanced IIoT & URLLC by Q1 of 2022 All RAN1 decisions that impact other WGs should be finalized in RAN1#107bis-e.
Rel-17 NR: NTN (Approved revised WID: RP-213691; Summary: RP-213618)
The discussion was about whether to create separate RAN4 specs for NTN or keep NTN together with TN. Satellite companies wanted to keep NTN and TN together, other companies generally preferred the separation. Main decisions:
- Create new separate NR NTN TS specifying UE radio transmission and reception and Performance requirements for satellite access, including satellite bands, i.e., create new part for 38.101 in 38.101-5.
- Integrate NR NTN RRM requirements in TS 38.133 with dedicated sub-clauses with suffix
- The new TS should refer to 38.101-1 for radio transmission and reception part and to 38.101-4 for performance part where relevant and suitable, and avoid duplication.
Rel-17 NR: MBS (Summary: RP-213675)
Case E is supported, under the assumption that configuration work is driven by RAN2, that RAN1 impact is zero, and RAN2 impact is reasonable (i.e. RAN2 may decide to not support it if issues surface during WG discussions):
[Case E] the case where a CFR [Common Frequency Resource] is defined based on a configured BWP.
- In particular, study the following:
- whether a configured BWP for MBS is needed or not.
- whether BWP switching is needed or not.
- In this study, the configured BWP has the following properties:
- The configured BWP is different than the initial BWP where the frequency resources of this initial BWP are configured smaller than the full carrier bandwidth.
- The CFR has the frequency resources identical to the configured BWP.
- The configured BWP needs to fully contain the initial BWP in frequency domain and has the same SCS and CP as the initial BWP.
- Note: The configured BWP is not larger than the carrier bandwidth
Rel-17 NR: IAB enhancements (Approved revised WID: RP-213668; Summary: RP-213620)
The scope of the work was clarified as no change of F1 termination point due to specification of inter-donor migration. Also, as already discussed at RAN#93e, enhancements to improve topology-wide fairness and multi-hop latency were replaced by enhancements to LCG-range extension, RLF indications and local rerouting.
Rel-17 NR: Small Data Transmissions (Summary: RP-213621)
Potential need to define BS demodulation requirements (and related conformance testing needs) for SDT will be re-addressed by RAN at a later point in time once RAN4 defined the UE RRM requirements.
Rel-17 NR: MUSIM (Approved revised WID: RP-213679; Summary: RP-213622)
RAN4 was requested to capture in TS38.133 that legacy measurement gap patterns (as defined in TS 38.133 Table 9.1.2-1, and also including patterns #24 and #25) can be applicable for MUSIM operation and also to capture new gap patterns for MUSIM with MGRP equal to paging DRX cycles for IDLE/INACTIVE.
All discussion on RRM requirements related to MUSIM gaps was postponed to Rel-18. Whether this aspect will be covered under the R18 MUSIM WI or another RAN4 WI can be discussed as part of the Rel-18 RAN4 package.
0.25 RAN4 RD TUs were allocated to R17 MUSIM WI Core part for remaining Rel-17 RAN4 meetings (i.e. RAN4 #101bis-e and RAN4 #102-e), to make existing gap patterns in TS 38.133 applicable for MUSIM and to define new gap patterns for MUSIM.
Rel-17 MUSIM WID was updated to add a new Objective 4: "Specify that existing gap patterns in TS 38.133 can be applicable for MUSIM and also define new gap patterns for MUSIM [RAN4]" and to list TS 38.133 as affected specification.
Rel-17 NR: Sidelink Relay (Approved revised WID: RP-212819; Summary: RP-213623)
The revised WID only adds specifications. Downscoping was discussed, but there was no majority for any specific proposal.
Rel-17 NR: QoE (Summary: RP-213624)
The work on Pause/Resume should continue in Rel-17. Technical discussion is left to RAN2, which needs to also involve RAN3 and SA4 on the matter. Specification work in Rel-17 should focus on a solution which provides overall benefits and not "eat up" the potential gains by increased signaling.
Rel-17 NR: Demodulation performance (Approved revised WID: RP-213656; Summary: RP-213693)
Objective "Introducing UE capability signaling for supporting CRS-IM [RAN2]" was included in the Core part, taking RAN2 as responsible WG. Objective "Evaluate the feasibility of supporting 30kHz scenario and specify performance requirements if needed" was included in the Performance part, where 15kHz will be prioritized and any cross-WG impact shall be concluded before March 2022. Network assistant signaling will be further discussed in RAN4. The CRS-IC receiver will be further discussed in Rel-18 if needed.
Rel-17 NR: NR RF requirements for FR2 (Approved revised WID: RP-213666; Summary: RP-213626)
The following note was added to the objective: "Note: The work of FR2 UL gaps includes (NG) EN-DC, NE-DC, NR-DC and SA. FR2 UL gap operation shall have no impacts to eNB operation or LTE RRC."
Rel-17 NR: Flexible gNB-ID solutions (Disc.: RP-213245; Summary: RP-213630)
There was no consensus on the issues brought up by the discussion document. RAN2 and RAN3 Chairs stated that TEI escalation to plenary is not desirable. The issues can be brought up in RAN2 and RAN3, which can consider each on its own merits and decide. No need for RAN plenary intervention.
Rel-17 LTE: WI UPIP support for EPC connected architectures [33] (Approved WI: RP-213669; Summary: RP-213610)
After several failed attempts, this WI was finally approved (as a Rel-17 WI), with the following conditions:
1) This feature is fully optional to EN-DC capable UEs
2) It does not challenge Rel-17 completion in RAN2 and RAN3
Approved Work Items and Study Items (excluding spectrum-related and conformance testing)
- RP-213669 WI: User Plane Integrity Protection support for EPC connected architectures
Keywords: RAN basic functions for of UPIP (at full data rate supported by UE) for EPC connected architectures using NR PDCP; In Rel-17 only applicable to EN-DC capable devices.
Release 18
Planning (Stage 1 frozen and RAN1/2/3 WI/SI package approved)
- Stage 1: frozen in December 2021 without exceptions
- RAN1/2/3 WI/SI package approved December 2021
- RAN4-led WI/SI approval planned for March 2022
- Stage 2: freezing target March 2023
- RAN1: freezing target September 2023
- RAN2/3/4 Core: freezing target December 2023
- Stage 3: freezing target December 2023
- ASN.1 and open APIs: freezing target March 2024
- RAN4: freezing target June 2024
RAN Rel-18 work package (Endorsed: RP-213469; Potential impacts on SA/CT: RP-212745; TUs: RP-213697)
The following RAN WI/SI package was approved by the end of the two-week meeting. Note that the documents referred to above are partly earlier versions and therefore do not reflect the final result. The following is an adapted table.
Note: The full RAN4 part of the package will be discussed by email in February and finalized at RAN#95e in March.
Summary table
|
WID/SID# |
WI/SI Title |
Topics (simplified; please see WID/SID for exact scope) |
Potential Interaction with CT/SA |
|---|---|---|---|
|
|
RAN1-led |
|
|
|
WI: MIMO Evolution for Downlink and Uplink |
(1) CSI reporting enhancement for high/medium UE velocities by exploiting time-domain correlation/Doppler-domain information to assist DL precoding, targeting FR1; (2) Extension of Rel-17 Unified TCI framework for indication of multiple DL and UL TCI states focusing on multi-TRP use case, using Rel-17 unified TCI framework; (3) Larger number of orthogonal DMRS ports for downlink and uplink MU-MIMO (without increasing the DM-RS overhead), only for CP-OFDM; (4) Enhancements of CSI acquisition for Coherent-JT targeting FR1 and up to 4 TRPs, assuming ideal backhaul and synchronization as well as the same number of antenna ports across TRPs; (5) UL DMRS, SRS, SRI, and TPMI (including codebook) enhancements to enable 8 Tx UL operation to support 4 and more layers per UE in UL targeting CPE/FWA/vehicle/Industrial devices; (6) Facilitate simultaneous multi-panel UL transmission for higher UL throughput/reliability, focusing on FR2 and multi-TRP, assuming up to 2 TRPs and up to 2 panels, targeting CPE/FWA/vehicle/industrial devices (if applicable); (7) Two TAs for UL multi-DCI for multi-TRP operation and Power control for UL single DCI for multi-TRP operation where unified TCI framework extension in objective 2 is assumed |
None identified so far |
|
|
SI: Study on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface |
3GPP framework for AI/ML for air-interface corresponding to each target use case regarding aspects such as performance, complexity, and potential specification impact: (1) Use cases to focus on: CSI feedback enhancement, Beam management, Positioning accuracy enhancements for different scenarios including those with heavy NLOS conditions; (2) AI/ML model, terminology and description to identify common and specific characteristics for framework investigations; (3) For the use cases under consideration: (a) Performance benefits of AI/ML based algorithms for agreed use cases in final representative set; (b) Potential specification impact, specifically for the agreed use cases in the final representative set and for a common framework. |
None identified so far |
|
|
SI: Study on Evolution of NR Duplex Operation |
Potential enhancements to support duplex evolution for NR TDD in unpaired spectrum, assuming (a) Duplex enhancement at the gNB side; (b) Half duplex operation at the UE side; (c) No restriction on frequency ranges: (2) Evaluation methodology for duplex enhancement; (3) Subband non-overlapping full duplex and potential enhancements on dynamic/flexible TDD |
None identified so far |
|
|
WI: NR sidelink evolution |
(1) NR sidelink CA operation based on LTE sidelink CA operation; (2) Support of sidelink on unlicensed spectrum for both mode 1 and mode 2 where Uu operation for mode 1 is limited to licensed spectrum only; (3) Enhanced sidelink operation on FR2 licensed spectrum; (4) Co-channel coexistence for LTE sidelink and NR sidelink including performance, necessity, feasibility, and potential specification impact; (5) UE Tx and Rx RF requirement for supporting new features introduced in this WI, sidelink frequency bands for single-carrier operation and frequency band combinations for carrier aggregation operation; (6) UE RRM core requirement |
None identified so far |
|
|
SI: Study on Expanded and improved NR positioning |
(1) Solutions for sidelink positioning; (2) Improved accuracy, integrity, and power efficiency; (3) Positioning support for RedCap UEs |
From "Objective" Study of positioning architecture and signalling procedures (e.g. configuration, measurement reporting, etc) to enable sidelink positioning covering both UE based and network based positioning [RAN2, including coordination and alignment with RAN3 and SA2 as required] From "Aspects that involve other WGs" Study of positioning architecture and signalling procedures to enable sidelink positioning covering both UE based and network based positioning may require coordination and alignment with SA2. |
|
|
SI: Study on Further NR RedCap UE complexity reduction |
Study further UE complexity reduction techniques: (a) Considering network impact, coexistence of Rel-17 and Rel-18 RedCap and non-RedCap UEs in a cell, UE impact, specification impact; (b) Potential solutions, which may complement each other focus on: UE bandwidth reduction to 5MHz in FR1, reduced UE peak data rate in FR1; (c) Rel-15 SSB should be reused and L1 changes minimized; (d) Operation in BWP with/without SSB and without/with RF retuning should be considered; (e) Some solutions for FR1 may be applied to FR2 in WI stage; (f) Single Rel-18 RedCap UE type for further UE complexity reduction |
None identified so far |
|
|
SI: Study on Network energy savings |
Prioritize idle/empty and low/medium load scenarios: (1) Base station energy consumption model; (2) Evaluation methodology and KPIs; (3) Techniques on gNB and UE side to improve network energy savings in terms of both BS transmission and reception |
From "Aspects that involve other WGs" The study should coordinate with SA5 as needed, e.g. on how the potential energy saving techniques integrate 3GPP management system |
|
|
WI: Further NR coverage enhancements |
Uplink coverage enhancements for PRACH, power domain and DFT-S-OFDM: (1) PRACH coverage enhancements; (2) Power domain enhancements; (3) Dynamic switching between DFT-S-OFDM and CP-OFDM |
None identified so far |
|
|
SI: Study on NR Network-controlled Repeaters |
Scenarios and assumptions: (a) Inband RF repeaters used for extension of network coverage on FR1 and FR2 bands; FR2 deployments may be prioritized for both outdoor and O2I scenarios; (b) For only single hop stationary repeaters; (c) Transparent to UEs; (d) Can maintain gNB-repeater link and repeater-UE link simultaneously. (e) Cost efficiency is key consideration point: (2) L1/L2 signaling (including its configuration) to carry side control information; (3) Aspects of network-controlled repeater management (identification and authorization). |
From "Objective" Study the following aspects of smart repeater management Identification and authorization of smart repeaters [RAN2, RAN3] NOTE2: Coordination with SA3 may be needed. |
|
|
WI: Enhancement of NR Dynamic spectrum sharing (DSS) |
Improvement of NR spectrum efficiency for LTE-NR co-existence: (1) NR PDCCH reception in symbols with LTE CRS REs; (2) Allow UE to support, and be configured with, two overlapping CRS rate matching patterns regardless of support or configuration of multi-TRP |
None identified so far |
|
|
SI: Study on Low-power Wake-up Signal and Receiver for NR |
Study will not require existing signals to be used as WUS. All WUS solutions identified shall be able to operate in a cell supporting legacy UEs. Other aspects such as detection performance, coverage, UE complexity, should be covered by the evaluation: (1) Use cases & KPIs; (2) Low-power wake-up receiver architectures; (3) Wake-up signal designs to support wake-up receivers; (4) L1 procedures and higher layer protocol changes needed to support wake-up signals; (5) Potential UE power saving gains including system impact |
None identified so far |
|
|
WI: Multi-carrier enhancements for NR |
(1) Solution for multi-cell PUSCH/PDSCH scheduling (one PDSCH/PUSCH per cell) with a single DCI; (2) Possible enhancements for multi-carrier UL operation (e.g. UL Tx switching schemes across up to 3 or 4 bands with restriction of up to 2 Tx simultaneous transmission for FR1 UEs; Switching time and other RF aspects, and RRM requirements for the above |
None identified so far |
|
|
|
RAN2-led |
|
|
|
WI: Further NR Mobility Enhancements |
(1) L1/L2 based inter-cell mobility for mobility latency reduction; (2) NR-DC with selective activation of the cell groups (at least for SCG) via L3 enhancements; (3) CHO including target MCG and target SCG; (4) CHO including target MCG and candidate SCGs for CPC/CPA; (5) RRM core requirements for the above; (6) RF requirements to cover inter-frequency L1/L2-based mobility; (7) Study FR2 SCell/SCG setup/resume delay |
None identified so far |
|
|
SI: Study on XR Enhancements for NR |
Based on Release 17 TR 38.838, on corresponding Release 17 work from SA4 (as per SP-210043) and on Release 18 work from SA2 (as per SP-211166); (1) XR-awareness in RAN; (2) XR-specific Power Saving; (3) XR-specific capacity improvements. |
From "Objective" The study is to be based on Release 17 TR 38.838, on corresponding Release 17 work from SA4 (as per SP-210043) and on Release 18 work from SA2 (as per SP-211166). From "Aspects that involve other WGs" SA2 is involved for determination of XR specific information made available in the network and the UE. |
|
|
WI: NR sidelink relay enhancements |
Enhance NR Sidelink Relay for V2X, public safety, commercial use cases: (1) Support single-hop Layer-2 and Layer-3 UE-to-UE relay (i.e., source UE -> relay UE -> destination UE) for unicast; (2) Enhance service continuity for single-hop Layer-2 UE-to-Network relay; (3) Study benefit and potential solutions for multi-path support to enhance reliability and throughput; (4) Sidelink DRX for Layer-2 UE-to-Network sidelink relay operation (if not in Rel-17); (5) RRM core requirements for relay discovery and (re)selection in UE-to-UE relay |
From "Objective" Specify mechanisms to support single-hop Layer-2 and Layer-3 UE-to-UE relay (i.e., source UE -> relay UE -> destination UE) for unicast [RAN2, RAN3, RAN4]. A. Common part for Layer-2 and Layer-3 relay to be prioritized until RAN#98 […..] Signalling support for Relay and remote UE authorization if SA2 concludes it is needed [RAN3] B. Layer-2 relay specific part [……] QoS handling if needed, subject to SA2 progress [RAN2] Note 3C: Support of Layer-3 UE-to-Network relay in multi-path scenario is assumed to have no RAN impact and the work and solutions are subject to SA2 to progress. From "Aspects that involve other WGs" SA2/CT1 have to capture impacts of NR Sidelink Relay on Discovery/PC5-S and CN. SA3 has to capture impacts of NR Sidelink Relay on security related part. |
|
|
WI: NR NTN (Non-Terrestrial Networks) enhancements |
Enhancements for NG-RAN based NTN (non-terrestrial networks) according to following assumptions with implicit compatibility to support HAPS (high altitude platform station) and ATG (air to ground) scenarios: (a) GSO and NGSO (LEO and MEO) with transparent payload; (b) Earth fixed tracking area. Earth fixed & Earth moving cells for NGSO; (c) FDD mode; (d) UEs with GNSS capabilities; (e) Both "VSAT" devices with directive antenna (including fixed and moving platform mounted devices and commercial handset terminals (e.g. Power class 3) are supported in FR1; (f) Only "VSAT" devices with directive antenna (including fixed and moving platform mounted devices) are supported in above 10 GHz band: (2) NR-NTN deployment in above 10 GHz bands; (3) Network verified UE location; (4) NTN-TN and NTN-NTN mobility and service continuity enhancements |
From "Objective" • Improved performance of low-rate codecs in link budget limited situation including reducing RAN protocol overhead for VoNR [RAN2,RAN1] [Liaise with SA2/SA4 as necessary] From "Aspects that involve other WGs" Possible cooperation/alignment with: • SA2, SA3 and SA3-LI with respect to 'Network verified UE location' and the possible impact on regulatory requirements (e.g. LI, PWS,…). • SA2 & SA4 with respect to 'coverage enhancement' and in particular the potential low-rate codecs performance enhancements for in link budget limited context. |
|
|
WI: IoT NTN enhancements |
Enhancements for E-UTRA (LTE-RAN) based NTN (non-terrestrial networks) according to following assumptions: (a) GEO and NGSO (LEO and MEO); (b) Earth fixed Tracking area. Earth fixed & Earth moving cells for NGSO; (c) FDD mode; (d) UEs with GNSS capabilities; Specify enhanced NB-IoT NTN and eMTC NTN radio interfaces and E-UTRAN/NG-RAN: (2) Mobility enhancements; (3) Enhancement to discontinuous coverage. |
From "Objective" Further enhancement to discontinuous coverage This objective will be revisited at RAN#96e / June 2022, subject to Rel-17 IoT-NTN status on discontinuous coverage at RAN#96e, SA#94e, CT#95e. From "Aspects that involve other WGs" Possible cooperation/alignment with: SA2 and CTx WGs with respect to the improvements related to the operation under discontinuous coverage: this will be revisited at RAN#96e / June 2022 depending on the status on the above objective on further enhancement to discontinuous coverage. |
|
|
WI: Enhancements of NR Multicast and Broadcast Services |
Enhance NR Multicast/Broadcast functions based on Rel-17 MBS: (1) Support of multicast reception by UEs in RRC_INACTIVE state; (2) Uu signalling enhancements to allow UE to use shared processing for MBS broadcast and unicast reception; (3) Enhancements to improve resource efficiency for MBS reception in RAN sharing scenarios. |
From "Objective" Note: collaboration with SA2 is expected in due course for the above objectives (That is, i) Specify support of multicast reception by UEs in RRC_INACTIVE state; ii) Study and if necessary, specify enhancements to improve the resource efficiency for MBS reception in RAN sharing scenarios) |
|
|
WI: NR Support for UAV |
(1) Enhancements on measurement reports; (2) Support subscription-based aerial-UE identification; (3) Enhancements for UAV identification broadcast for both LTE and NR; (4). Study UE capability signaling to indicate UAV beamforming capabilities and, if necessary, RRC signaling |
From "Objective" Specify the signaling to support subscription-based aerial-UE identification [RAN3/SA2 interaction/RAN2] Study and specify, if needed, enhancements for UAV identification broadcast [RAN2, SA2]. Note: This description is a placeholder for a more detailed objective to be drafted once SA2 will have concluded their study on the architectural aspects. From "Aspects that involve other WGs" SA2: Subscription-based aerial-UE identification Enhancements for UAV identification |
|
|
WI: Dual Tx/Rx MUSIM |
MUSIM procedures to operate in RRC_CONNECTED state simultaneously in NW A and NW B: (1) Mechanism to indicate preference on temporary UE capability restriction and removal of restriction; (2) RAT Concurrency; (3) Applicable UE architecture: Dual-RX/Dual-TX UE |
None identified so far |
|
|
WI: In-Device Co-existence (IDC) enhancements for NR and MR-DC |
Address interference between 3GPP (NR-DC and EN-DC) and non-3GPP RAT (e.g. WiFi); Priority for FDM solution (more granular indication of affected frequencies); TDM solution (e.g. indication of UE preferred TDM pattern for UL/DL) complementary to FDM solution; LTE IDC solution is baseline for solutions |
None identified so far |
|
|
WI: Mobile Terminated-Small Data Transmission (MT-SDT) for NR |
Paging-triggered SDT (MT-SDT) for UEs in RRC_INACTIVE, supporting RA-SDT and CG-SDT as the UL response, and for initial DL data reception and subsequent UL/DL data transmissionsin RRC_INACTIVE; Data transmission in DL within paging message is not in scope |
None identified so far |
|
|
|
RAN3-led |
|
|
|
WI: Mobile IAB |
Migration/topology adaptation to enable IAB-node mobility, including inter-donor migration of the entire mobile IAB-node (full migration); Ability to serve legacy UEs |
From "Aspects that involve other WGs" Alignment and coordination with Rel-18 SA2 work on VMR should be considered, if needed. |
|
|
WI: Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN |
Specify data collection enhancements and signaling support within existing NG-RAN interfaces and architecture (including non-split architecture and split architecture) for AI/ML-based Network Energy Saving, Load Balancing and Mobility Optimization |
From "Objective" Note: On security impacts, coordination with SA3 when needed. On OAM aspects, coordination with SA5 when needed. |
|
|
WI: Further enhancement of data collection for SON (Self-Organising Networks)/MDT (Minimization of Drive Tests) in NR and EN-DC |
Specify data collection enhancement in NR for SON/MDT purpose; Including "left-over" features (i.e. MR-DC CPAC and MRO successful PScell change report, fast MCG recovery, NR-U) and MRO enhancement for inter-system handover voice fallback; UE reporting necessary to enhance mobility parameter tuning; Inter-node information exchange, including possible enhancements to interfaces; Support for RACH enhancements, NPN; Support of signaling based logged MDT override protection to address scenario where signaling based MDT configured in LTE, UE comes to connected in NR. |
From "Objective" If needed, co-operate with RAN1, SA2, SA5, CT4. |
|
|
WI: Enhancement on NR QoE management and optimizations for diverse services |
Support new service type, defined or to be supported by SA4. Support RAN-visible parameters for additional service types, and existing service; Configuration and collection in RRC_INACTIVE and RRC_IDLE states for MBS, at least for broadcast service; Support for QoE in NR-DC; Left-over features Rel-17; Support continuity of legacy QoE measurement job for streaming and MTSI service during intra-5GC inter-RAT handover process |
From "Objective" Support for new service type, such as AR, MR, MBS and other new service type defined or to be supported by SA4. Support RAN-visible parameters for the additional service types, and the existing service if needed, and the coordination with SA4 is needed[RAN3, RAN2]. Specify the new service and the existing service defined or to be supported by SA4, combined with high mobility scenarios, e.g., High Speed Trains. […] Other objectives: Note 3: If needed, co-operate with other working groups, e.g. SA4/SA5/SA2/CT1. From "Aspects that involve other WGs" TSG SA4: for Codec aspects TSG SA5: for the QoE measurement configuration and reporting aspects TSG SA2: for the QoE measurement related procedures aspects TSG CT1: for the UE internal handling between its Access Stratum and upper layers |
|
|
SI: Study on Enhancement for resiliency of gNB-CU-CP |
Study and identify failure scenarios associated with the gNB-CU-CP, based on the current architecture for the NG-RAN |
None identified so far |
|
|
|
RAN4-led |
|
|
|
WI: NR support for dedicated spectrum less than 5MHz for FR1 |
Dedicated spectrum in FR1; Spectrum allocations from approximately 3 MHz upto below 5 MHz; RAN1 necessary physical layer changes; RAN4 requirements at least in bands n100, n8, n26 and n28 |
None identified so far |
SA2 Rel-18 WIs and SIs (Approved: SP-211655)
|
WID/SID# |
WI/SI Title |
Acronym |
|---|---|---|
|
SP-211594 |
Study on System Enabler for Service Function Chaining |
FS_SFC |
|
SP-211595 |
MPS when access to EPC/5GC is WLAN |
MPS_WLAN |
|
SP-211603 |
Study on Generic group management, exposure and communication enhancements |
FS_GMEC |
|
SP-211612 |
Study on Access Traffic Steering, Switching and Splitting support in = 5G system architecture; Phase 3 |
FS_ATSSS_Ph3 |
|
SP-211656 |
Study on Enhanced support of Non-Public Networks phase 2 |
FS_eNPN_Ph2 |
|
SP-211632 |
Study on Phase 2 for UAS, UAV and UAM |
FS_UAS_Ph2 |
|
SP-211633 |
Study on Extensions to the TSC Framework to support DetNet |
FS_DetNet |
|
SP-211634 |
Study on 5G Timing Resiliency and TSC & URLLC enhancements |
FS_5TRS_URLLC |
|
SP-211635 |
Study on RedCap Phase 2 |
FS_REDCAP_Ph2 |
|
SP-211636 |
Study on Vehicle Mounted Relays |
FS_VMR |
|
SP-211637 |
Study on 5GC LoCation Services Phase 3 |
FS_eLCS_Ph3 |
|
SP-211638 |
Study on Edge Computing Phase 2 |
FS_EDGE_Ph2 |
|
SP-211639 |
Study on 5G System with Satellite Backhaul |
FS_5GSATB |
|
SP-211640 |
Study on Support for 5WWC Phase 2 |
FS_5WWC_Ph2 |
|
SP-211641 |
Study on Network Slicing Phase 3 |
FS_eNS_Ph3 |
|
SP-211642 |
Study on 5G AM Policy Phase 2 |
FS_AMP_Ph2 |
|
SP-211643 |
Study on Personal IoT Networks |
FS_PIN |
|
SP-211644 |
Study on Evolution of IMS multimedia telephony service |
FS_MMTELin5G |
|
SP-211645 |
Study on 5G multicast-broadcast services Phase 2 |
FS_5MBS_Ph2 |
|
SP-211646 |
Study on XR (Extended Reality) and media services |
FS_XRM |
|
SP-211647 |
Study on Ranging based services and sidelink positioning |
FS_Ranging_SL |
|
SP-211648 |
Study on System Support for AI/ML-based Services |
FS_AIML |
|
SP-211649 |
Study on 5G UE Policy Phase 2 |
FS_UEPO_Ph2 |
|
SP-211650 |
Study on Enablers for Network Automation for 5G - Phase 3 |
FS_eNA_Ph3 |
|
SP-211651 |
Study on Satellite access Phase 2 |
FS_5GSAT_Ph2 |
|
SP-211652 |
Study on UPF enhancement for Exposure And SBA |
FS_UPEAS |
|
SP-211653 |
Study on Proximity-based Services in 5GS Phase 2 |
FS_5G_ProSe_Ph2 |
|
SP-211654 |
Study on Seamless UE context recovery. |
FS_SUECR |
