Summary Report from 3GPP plenaries #105 (Melbourne, Australia, 9 - 13 September 2024)

Summary Report from 3GPP plenaries #105 (Melbourne, Australia, 9 - 13 September 2024)

Hans van der Veen, NEC Laboratories Europe GmbH

Rel-18

  • Only some performance work of NR positioning is remaining in RAN.

Rel-19

  • This was the first meeting since approval of the Rel-19 package to allow new RAN Rel-19 work and scope expansion.
  • The main other RAN discussion was on so-called checkpoints of objectives of the various WI and SIs.
  • SA approved new WIs/SIs for all WGs except SA1 (SA1 is focused on Rel-20).

Rel-20 (5G)

  • SA approved a Study Item and several new Work Items for SA1.

Rel-20 (6G)

  • In RAN companies were given the opportunity to give their views on the IMT-2030 related work for which a new RAN Study Item is planned to be approved in next plenary, but no decisions were taken.
  • SA approved a Rel-20 Study Item on 6G Use Cases and Service Requirements

Rel-18 Planning and progress (RAN4 perf. work remaining for NR positioning)

Stage 1: frozen December 2021 without exceptions

RAN1/2/3 work package: approved December 2021

RAN4 work package: approved March 2022

Stage 2: frozen June 2023 without exceptions

SA3: frozen September 2023

RAN1: frozen September 2023

RAN2/3/4 core functionality: frozen December 2023 with exceptions (no more exceptions by June 2024)

Stage 3: frozen March 2024 with exceptions (no more exceptions by June 2024)

ASN.1 and open APIs: frozen June 2024

RAN4: frozen June 2024 (remaining in September 2024: RAN4 perf. work for NR positioning)

 

Closed Rel-18 Work Items and Study Items (excluding spectrum-related and conformance testing)

Rel-18 NR

  • Perf.: Enhancement of UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC)

Rel-18 RAN Work Item Summaries (descriptions of features in the release after the work has actually finished). Overall draft TR with Rel-18 description (under construction, incomplete)

RAN

  • <None>

SA

  • SP-241076 Interconnection and Migration Aspects for Railways (IRail)
  • SP-241077 Gateway UE function for Mission Critical Communication (MCGWUE)
  • SP-241079 Mission Critical Security
  • SP-241080 Application layer support for Factories of the Future (FFAPP)
  • SP-241161 EXPOSE - Service exposure interfaces for industry
  • SP-241291 Multimedia Priority Service (MPS) when access to EPC/5GC is WLAN
  • SP-241297 Service enabler architecture layer (SEAL_Ph3)
  • SP-241309 Spending Limits for AM and UE Policies in the 5GC (TEI18_SLAMUP)
  • SP-241311 Seamless UE context recovery (SUECR)
  • SP-241337 Ad hoc Group Communication support in Mission Critical Services (AHGC)
  • SP-241341 Generic group management, exposure and communication
  • SP-241342 Service enabler architecture layer (SEAL) data delivery enabler for vertical applications
  • SP-241343 Mission critical services over 5GProse

Rel-19 Planning (No milestone at this meeting)

RAN Workshop: took place in June 2023

SA Workshop: took place in June 2023

Stage 1: frozen December 2023 with exceptions (no more exceptions by June 2024)

SA Stage 2 work package: approved December 2023

RAN1/2/3 work package: approved December 2023

RAN4 work package: approved March 2024

Stage 2: freezing target December 2024

RAN1: freezing target June 2025

RAN2/3/4 core functionality: freezing target September 2025

Stage 3: freezing target September 2025

ASN.1 and open APIs: freezing target December 2025

RAN4: freezing target December 2025

 

Closed Rel-19 Work Items and Study Items (excluding spectrum-related and conformance testing)

Rel-19 NR

  • SI: Study on enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN
  • SI: Study on additional topological enhancements for NR

Rel-19 SI NR Ambient IoT (Endorsed moderator summary: RP-242360)

  • No change to the SID regarding the study of Do-A.

On RAN2 out-of-coverage aspects:

  • No clarification needed on top of the RAN2 agreement.
  • Keep the A-IoT device architectures on the RAN1 agenda in 2024/Q4.
  • Keep the CW waveform characteristics on the RAN1 agenda in 2024/Q4.

On the SID objective to study necessary characteristics of carrier-wave waveform

  • As already clarified at RAN#103, the above objective does not include studying how to control the characteristics of the CW waveform in topology 1 or topology 2 or outside the topology.
  • RAN guidance to RAN4: RAN confirms that RAN4 studies and documents the methods and feasible values of CW interference cancellation according to their agreements.
  • No additional discussion in RAN1 on proximity determination in the Rel-19 SI.
  • No guidance from RAN to RAN1 on inventory completion time for multiple devices for the Rel-19 SI. RAN1 proceeds in Q4 based on RAN1 agreements.
  • RAN reiterates that "study a harmonized framework with minimized differences (where necessary)" includes studying minimized differences (where necessary) between devices, e.g. for frequency synchronization between device 1/2a and device 2b, etc.

 

Rel-19 SI NR ISAC (Endorsed proposal 1 from discussion document: RP-242227; Approved revised SID: RP-242348)

  • Only ISAC channel modelling was included as part of the Rel-19 scope and the checkpoint was removed from the SID.

Rel-19 SI NR AI/ML mobility (Endorsed WF: RP-242362; Approved revised SID: RP-242393)

RAN4 objective in SID AI/ML for mobility in NR was clarified as follows:

  • Evaluate testability, interoperability, and impacts on RRM requirements and performance [RAN4]
  • Study the impacts on requirements based on RAN2 assumptions, and coordinate with RAN2 if needed
  • Study the testability and interoperability based on RAN2 framework (e.g., number of cells to measure, beams etc.)
  • NOTE 1: RAN1/3 work can be triggered via LS
  • NOTE 2: RAN4 scope/work can be defined and confirmed by RAN#105 after some RAN2 discussions (within the RAN4 pre-allocated TUs)
  • NOTE 23: To avoid duplicate study with "AI/ML for NG-RAN" led by RAN3
  • NOTE 34: Two-sided model is not included
  • Note X: Leverage the work from  "AI/ML for NR air interface" led by RAN1 and avoid the duplicate study for testability and interoperability.
  • Note Y: Avoid the overlaps with RAN2 work for evaluation

Rel-19 SI NR FR2 OTA testing enhancement (Approved revised SID: RP-242400)

  • The checkpoint was removed without any further changes.

Rel-19 WI NR MIMO (Endorsed WF: RP-242367; Approved revised WID: RP-242394)

The following will be specified as part of the normative work on Rel-19 MIMO:

  • Item A: SRS port grouping for TDD low-complexity 6/8RX receiver
  • Item B: 2TA without CoresetPoolIdx association for asymmetric DL sTRP/UL mTRP
  • Item C: 3T6R SRS antenna switching
  • Item D: UE capability for 3T3R SRS antenna switching
  • Item G: UE capability for non-codebook-based UL transmission

Rel-19 WI NR AI/ML air interface (Endorsed WF: RP-242351, RP-242387; LSout: RP-242389; Approved revised WID: RP-242399)

RAN2 aspects (RP-242351):

  • Requirements for data collection for UE sided model training for standardized solution (if standardized) (i.e. Option 1b, 2, 3). Option 1a is not precluded.
  1. The data collected is secured and data integrity and confidentiality for that data is ensured.
  2. User data privacy, anonymity and user consent is respected.
  3. The MNO has full control of the standardized data collection transfer process and can manage data transfer to the server for UE-side data collection, without the need of SLA for this purpose. This includes initiating, terminating, and fully managing data transfer.
  4. MNO has full visibility for standardized data. 
  5. The design is futureproof and extendable.
    • FFS/study if and how to handle non-standardized data (i.e. partial visibility). 
    • FFS controllability on data collection
    • Standardized solutions should follow the principle of aiming to minimize air interface overhead and impact to NW operation
  • WF (solution)
    • SA input is required for further decision on which solutions to proceed with.  RAN will consider SA input in making a final decision in RAN#106.
    • RAN extends the study item on data collection by one quarter. Checkpoint in RAN#106 on how to proceed
    • Send an LS to SA (RP-242389)
    • Provide the table and reference to TR 38.843
    • Provide requirements agreed in RAN for a standardized solution (if standardized). 
    • Provide facts in terms of what RAN2 couldn't reach consensus on.  
    • Reference to LS for message size R1-2310681 (RAN1 is still discussing)
    • The solutions developed need to meet the requirements.  Ask SA to provide input on the solutions 1b, 2, and 3. at the beginning of LS that all solutions in the table are under consideration in RAN.
    • Input from SA will be used by RAN in RAN#106 to use in order to make a decision on how to proceed

Non-RAN2 aspects (RP-242387)

  • For CSI compression (two-sided model):
    • Extend the CSI compression study objective till the end of Rel-19.
    • Add necessary spec impact analysis.
  • For CSI prediction (one-sided model):
    • Move CSI prediction to normative phase to focus on
    • Functionality-based LCM leveraged from other use cases, when necessary and applicable,
    • Study, and if necessary, specify consistency of training/inference,
    • RAN4 requirements. For RAN4 TUs, revisited in RAN#106.
    • Note: Normative work in RAN1 for CSI prediction will start from Q1 of 2025
  • Testability and interoperability (RAN4):
    • Extend the testability and interoperability study objective till the end of Rel-19.
      • Beam management OTA test setup.
      • Continue the study in AI/ML work item, including test setup and methodology, which is part of RAN4 core requirements related objectives
      • Remove the check point from FR2 OTA study item
  • For Model identification, transfer/delivery (RAN2/RAN1):
    • Extend the study of Model identification for two-sided model till the end of Rel-19.
    • Extend the study of Model transfer/delivery till the end of Rel-19.
  • For second priority issues of positioning:
    • RAN1 will not discuss any proposals targeting second priority issues in Q4, 2024.

 

Rel-19 WI Low-power wake-up signal and receiver (Endorsed WF: RP-242361; Approved revised WID: RP-241824)

  • Confirm in RAN#105 that Rel-19 LP-WUS work item scope includes both FR1 and FR2
  • Request RAN1 to make a progress on the FFS "Whether the above is applicable to FR2" (under RAN1#117 agreement on LP-WUS and LP-SS bandwidth) in RAN1#118bis.
  • Reuse the FR1 design when possible
  • No additional guidance in RAN#105 for RAN4 work and TU allocation

Rel-19 WI NR NES (Endorsed WF: RP-242384; Approved revised WID: RP-242354)

  • Support Case-2 as part of normative work on on-demand SIB1 for Rel-19 NES
    • Case-2: UE obtains UL WUS configuration from Cell A, UE transmits UL WUS on NES Cell, UE receives on-demand SIB1 from NES Cell
    • Above does not impact the ongoing discussion in RAN2 on WUS configuration update for UEs camping a NES cell

Rel-19 WI NR Mobility enhancements (Endorsed proposals from discussion documents: P1 RP-241917, P4 RP-242221; Approved revised WID: RP-242356)

  • Remove the checkpoint from the L1 event triggered measurement objective with no additional follow-up
  • Add a third bullet for the second WID objective: Specify CSI acquisition and reporting for candidate cell(s).
  • New checkpoint at RAN#107.

Rel-19 WI NR XR (Endorsed proposals from discussion document: P1, P3 RP-241936; Endorsed WF: RP-242390; Approved revised WID: RP-241771)

  • Update revised WID for NR Phase 3 XR enhancement to capture the RAN awareness based rate control in the scope.
  • Update revised WID for NR Phase 3 XR enhancement to include specifying how to support Scheduling Enhancements in RAN in Rel-19.
  1. Scheduling enhancements
    • Specify Enhancements for support of UL scheduling to enable high XR capacity while meeting delay requirements/avoiding too late PDUs, as follows [RAN2]:
    • Specify additional Logical Channel priority handling using delay/deadline information of packets;
    • Specify enhanced DSR (Delay Status Report) reporting with multiple pairs of remaining time and buffer size for a LCG.
  2. Uplink congestion indication (in downlink)
    • Specify uplink congestion signalling [RAN2]
    • Specify in MAC layer XR rate control signalling over downlink per QoS flow/per DRB to enable faster source rate adaption to uplink congestion
  3. Multimodality
    • Specify support for multimodality in RAN for UL and DL [RAN3]
    • Note: This is subject to alignment with SA2, e.g., if MMSID is not available from CN, then UE assistance information based approach as an alternative. RAN#106 to check handling of uplink discard based on SA2/SA4 outputs on whether the corresponding information is available at the UE.
    • Note: Review in RAN#106 the conclusions on SA2 side (including MMSID delivery to RAN) to allocation for further TUs in RAN3 from Q1/25 onwards.
  4. Other aspects
    • Reflection of SA2 development in RAN3
    • RAN4 work: Review in RAN#106 the conclusions on SA2 side (including MMSID delivery to RAN) to allocation for further TUs in RAN3 from Q1/25 onwards
    • In Q4/24 discussion in RAN3 on the SA2 LS is enabled with necessary analysis

Rel-19 WI LTE NTN IoT (Endorsed WF: RP-242368; Approved revised WID: RP-242397)

  • Update scope of WI to support broadcast of PWS messages for NB-IoT re-using the LTE mechanisms [RAN2]
  • The solutions will be developed for NTN but can be applicable to TN (if possible).   Specific NB-IoT TN optimizations will not be considered as part of this WI.
  • Support for indication of intended service area will be considered based on NR NTN discussions/outcome.

Approved Rel-19 Work Items and Study Items RAN (excluding spectrum-related; excluding conformance testing)

NR WIs/SIs led by RAN1

  • RP-242408 WI: Multi-carrier enhancements for NR Phase 2 
    • Keywords: Specify the support of the following for multi-cell PUSCH/PDSCH scheduling with a single DCI (1) Different SCS/carrier type among co-scheduled cells by the single DCI; (2) One or multiple PUSCHs/PDSCHs per scheduled cell by the single DCI.

NR WIs/SIs led by RAN2

  • RP-242414 WI: Introduction of A-GNSS support for NavIC L1 SPS in NR & LTE
    • Keywords: (1) Specify signalling support for NavIC L1 band SPS in NR specifications by introducing necessary assistance data information based on existing GNSS framework, including enhancements to Ionospheric model, NavIC system time and Ephemeris; (2) Specify signalling support for NavIC L1 band SPS in LTE specifications similar to NR.
  • RP-242413 WI: Introduction of BDS B2b Signal in A-GNSS
    • Keywords: Specify A-BDS enhancements in Rel-19, including (1) Supporting new signal of BDS B2b in A-GNSS for both E-UTRA and NR; (2) Specify corresponding assistant information in dedicated signalling.

NR WIs/SIs led by RAN3

  • RP-242395 WI: Additional topological enhancements for NR
    • Keywords: Specify (1) Wireless Access Backhaul; (2) 5G Femto: (a) Support NR Femto architecture with optional NR Femto GW for NG interface; (b) Support access control for NR Femtos operating in open, hybrid and closed modes reusing existing CAG functionality.
  • P-242385 WI: Enhancements for Artificial Intelligence (AI)/Machine Learning (ML) for NG-RAN
    • Keywords: (1) Specify data collection enhancements and signalling support within existing NG-RAN interfaces and architecture (including non-split architecture and split architecture) for AI/ML-based Slicing and AI/ML based CCO; (2) Support of the Leftovers in Rel-18 AI/ML for NG-RAN: Mobility Optimization for NR-DC; Split architecture support for Rel-18 use cases; Continuous MDT collection targeting the same UE across RRC states.

NR WIs/SIs led by RAN4

  • <None>

LTE WIs/SIs led by RAN1

  • RP-242415 WI: Introduction of IoT-NTN TDD mode
    • Keywords: Enable NTN operation with a NB-IoT TDD mode leveraging commonalities with half-duplex NB-IoT FDD NTN (not intended to be applicable to existing NTN bands).

LTE WIs/SIs led by RAN2

  • <None>

LTE WIs/SIs led by RAN3

  • <None>

LTE WIs/SIs led by RAN4

  • <None>

 

Approved Rel-19 Work Items and Study Items SA

SA1

  • <None>

SA2

  • SP-241388 WI: Energy Efficiency and Energy Saving (Controversial. This WI was only approved after a challenge to the SA2 Working Agreement had failed).

SA3

  • SP-241376 WI: Security for Monitoring of signalling traffic in 5G (MonStra)

SA4

  • SP-241374 SI: Study on immersive Real-Time Communication for WebRTC, Phase 2
  • SP-241314 WI: Terminal Audio quality performance and Test methods for Immersive Audio Services, Phase 2

SA5

  • SP-241377 WI: Charging Aspects for 5G ProSe Phase 3
  • SP-241378 WI: Enhancement of Management Aspects Relatod of NWDAF
  • SP-241379 WI: Management of planned configurations
  • SP-241380 WI: Data management regarding subscriptions and reporting

SA6

  • SP-241375 SI: Study on Service enabler architecture layer (SEAL) enhancements
  • SP-241381 WI: Enhancements to Common API Framework (CAPIF) Phase 3
  • SP-241382 WI: Mission Critical services support on IOPS mode of operation

Rel-20 (5G) Planning (New)

Stage 1 approval of SIDs: June 2024; Stage 1 normative freeze : June 2025

Stage 2 approval of SIDs: tbc; Stage 2 normative freeze : June 2026 (80%); September 2026 (100%)

Stage 3 (CT) approval of SIDs: March 2026 or earlier; Stage 3 CT normative freeze : March 2027

Stage 3 RAN approval of SIDs: tbc; Stage 3 RAN normative freeze : tbc

ASN.1/OpenAPI freeze: June 2027

Other WGs : + 18 months compared to Rel-19 dates, i.e. for RAN:

Content definition: June 2025

RAN1: December 2026

RAN2/3/4 Core: March 2027

RAN4 Perf: June 2027

 Approved 5G Rel-20 Work Items and Study Items RAN (excluding spectrum-related; excluding conformance testing)

  • <None>

Approved 5G Rel-20 Work Items and Study Items SA

SA1

  • SP-241392 SI: Study on FRMCS Phase 6
  • SP-241393 WI: Network Sharing on Satellite Access Network
  • SP-241147 WI: Network Sharing Phase II on Disaster Condition
  • SP-241149 WI: Enhanced 5G Resident Phase II
  • SP-241150 WI: Combined QoS configuration and monitoring
  • SP-241151 WI: Legacy Residential Gateway Supporting 5G LAN-type
  • SP-241153 WI: Exposure for Virtual Network information and capability

SA2

  • <None>

SA3

  • <None>

SA4

  • <None>

SA5

  • <None>

SA6

  • <None>

In RAN, companies were given the opportunity to give their views on the IMT-2030 related work for which a new RAN Study Item is planned to be approved in next plenary, but no decisions were taken.

Rel-20 (6G) Planning (New)

Stage 1 approval of SIDs: September 2024 (TSG 105); Stage 1 (study) freeze: March 2026

March 2025 (TSG#107): First TSG-wide 6G workshop

RAN IMT-2030 discussion is expected in RAN from 09/24 to 12/24

RP SI Rel-20 focusing on ITU– IMT-2030: approval 12/24 until 06/25

RP SI Rel-20 focusing on 6G General: approval 03/25 (after WS), until 06/26

SA2 and RAN-WG SIDs approval: June 2025 (TSG 108); SA2 (study) freeze: December 2026 or Mar 2027

SA1/SA2 6G SI may continue beyond Stage-1/Stage-2 freeze dates for 5G-Advanced

Other SA WG (SA3, SA4, SA5, SA6) SIDs approval: tbd at future TSG meeting

CT WG SIDs approval: March 2026

RAN1 starts in 3Q/25 until 1Q/27; RAN2/3/4 start in 4Q/25 until 2Q/27

CT WG 6G SI will start 9 months after approval of SA2 SI.

 

Approved 6G Rel-20 Study Items SA (there will be no 6G Work Items in Rel-20)

  • SP-241391 SI: Study on 6G Use Cases and Service Requirements(the first 6G Study Item in 3GPP!)


Year:
2024
Q1
Mapping of Common Requirements:
  • Rel-18
  • Rel-19
  • Rel-20