12 October to 16 October 2026South Korea3GPP TSG RAN WG3Last updated 2026-10-13
At a glance
Work on sensing transfer and AIoT topology centers on draft signaling and data paths. Sensing proposals directly conflict over whether to retain editor's notes pending an SA3 reply. Topology proposals address data forwarding during reader mobility and reporting unavailable UE Readers. Service awareness and data collection proposals concern study-report text. SCell activation work covers candidate information and a separate concern about Option A.
1Agreed so far
No chair-note agreements on these topics have been posted yet. This section updates as the chair notes appear.
2Hottest topics
Sensing information transfer
Significance 38 of 100, 24 TDocs
One proposal would keep the editor's notes tied to the SA3 reply until RAN plenary gives clear guidance. The opposing proposal would remove those notes from the TS 38.300, 38.480 and 38.483 texts. This is a direct keep-versus-remove conflict, not a difference in wording alone. Its resolution affects how the draft sensing procedure records the need for further review.
One proposal addresses AIoT session continuity during inter-gNB UE Reader mobility. If continuity is supported and the target gNB receives AIoT data from the UE, it would forward that data directly to the CN. Another proposal would have NG-RAN inform the AIOTF when provided UE Readers cannot be used. That proposal leaves the specific reporting signaling for RAN3 to determine.
Service Characteristics Awareness and Performance Monitoring
Significance 29 of 100, 12 TDocs
One proposal defines Service Characteristics Awareness as operating without access to service content. Another proposes capturing awareness text in study report TR 38.760-3. The work concerns how the study describes awareness, rather than an agreed normative requirement. Whether the no-content-access formulation enters that report remains a concrete drafting question.
One proposal allows data collected or generated by an aNB to be stored for access by other entities. OAM can host that storage, while additional hosts remain FFS in the proposal. A separate proposal would also consider SON, MDT and network-side data collection for model training in the RAN3 framework. Its model-training item concerns use cases led by other working groups, and it calls for a study-report update.
One proposal specifies candidate SCell information in the SN Addition Request Acknowledge. It includes a per-candidate-PSCell indication of whether at least one associated SCell was activated through RRC sCellState. It also includes per-candidate-SCell SSB and CSI-RS configurations for L1 measurements and TCI state configurations. A separate observation warns that Option A obscures why candidate SCells are absent and loses configured and activated SCell information.
Proposals already uploaded where companies take opposing positions on the same point. These are proposals, not decisions.
Candidate SCell information
Qualcomm
Proposes
In the SN Addition Request Acknowledge message, a candidate SN includes the following information: The candidate SCell(s) associated with each prepared candidate PSCell, For each ...
With Option A, the source node cannot distinguish whether candidate SCells are absent because of RRC based activation, lack of support, or the candidate node's ...
RAN3 should keep the “subject to SA3 reply LS” editor’s notes in the working assumptions, potential agreements and BLCRs, until clear guidance is given by ...
UE context retrieval with and without Xa connectivity
27
8.1
New Incoming LSs
24
13.2
Sensing information transfer
24
14.2
Topology 2
19
10.3.2
RAN-CN control plane for connectivity services
18
10.5.1
AI/ML use cases
18
10.2.1
Data collection
17
10.3.1.1
Requirements for RAN-CN communication for non-connectivity services
17
9.2
NR
16
10.4.2
Interface between aNBs
15
10.5.2
AI/ML framework
15
12.2.2
Intra-CU LTM
15
Built by 3GPP Scout from the public meeting record (481 TDocs registered, catalog synced 2026-10-13). Significance scores rank topics by decisions, contention, breadth and volume. Excerpts are at most 25 words and link to the original on the 3GPP file server.