16 November to 20 November 2026Calgary, Canada3GPP TSG RAN WG3Last updated 2026-11-10
At a glance
Data collection proposals address interoperable RAN data access and OAM storage for offline model training.
UE context retrieval faces a 48-bit Resume ID proposal and a concern about Msg3 coverage.
Topology 2 work covers UE Reader availability reporting and Inventory and Command call flows.
AI/ML proposals address feedback between aNBs, inference-generated actions, and prediction data for use cases.
Your topic
Follow a topic from RAN3 #134 and get its next outcome by email.
Scout emails you when a new agreement or decision on it is recorded, with the source for each. Or ask Scout and get an answer that cites the exact TDoc. Free to start.
One proposal asks SA5 whether DMFW supports interoperable RAN data access in distributed multi-vendor deployments. Another proposes OAM collection and stored raw data for offline model training.
The interoperability proposal also seeks clarification on standardized interaction if DMFW does not meet those needs. The proposals address different requirements: access and reuse across deployments, and storage for training.
Sisvel (with Reliance Jio, Rakuten Mobile, Charter Communications, Tejas Networks)
Proposal
RAN3 should provide SA5 with the RAN3 requirements concerning data availability and reuse and ask whether the DMFW solutions under study support interoperable access to ...
UE context retrieval with and without Xa connectivity
Significance 34 of 100, 22 TDocs
A 48-bit Resume ID proposal specifies PLMN, AMF set, I-RNTI profile, local RAN, and UE reference fields. An opposing concern says a longer aNB identifier would enlarge Msg3 and reduce coverage.
That concern applies the coverage impact to all resume attempts, while identifying benefits only for retrieval without direct Xa. The proposed field layout therefore faces a coverage objection, not a recorded decision.
14.2
Topology 2
Significance 33 of 100, 20 TDocs
The prior working assumption says NG-RAN may notify AIOTF when provided UE Readers cannot support an operation. A proposal seeks a choice between Inventory Response and Inventory Report for that notification.
Another proposal would refine Inventory and Command call flows to capture A-IoT-specific RRC signalling. The reporting message and call flow details remain separate points for discussion.
CATT
Proposal
Refine the Inventory and Command call flows for Topology 2 for capturing the A-IoT specific RRC signalling, as the TP provided in Annex.
RAN3 to discuss and down-select between the following two approaches for gNB to inform the AIOTF about the unavailable UE Reader(s): 1/ report the unavailable ...
One proposal introduces cause-aware feedback on the disposition of actions generated by inference. Another keeps feedback transfer between neighbouring aNBs within RAN3 scope.
The first would include reasons when Actors report how they executed those actions. The second leaves feedback content for study by use case, regardless of another framework issue.
Tejas Networks
Proposal
A standardized cause-aware feedback mechanism should be introduced to enable Actors to report the execution disposition of inference-generated actions and the associated reasons, thereby improving ...
A proposal would consider UE traffic and trajectory prediction as input and output data across use cases. Another proposes considering future UE distribution and traffic demand as potential NES input.
The NES proposal makes that input conditional on availability and leaves its granularity for further study. These proposals concern which prediction information use cases should handle, not an agreed data set.
Qualcomm
Proposal
For all the agreed use cases and proposed new use cases, consider UE Traffic prediction and UE Trajectory prediction as input and output data.
RAN3 agrees to further consider information on future UE distribution and traffic demand, if available, as potential input for NES, with the appropriate granularity to ...
Carrying a longer aNB identifier increases the Resume ID beyond 40 bits and enlarges Msg3, which reduces Msg3 coverage for all resume attempts, requires RAN1 ...
UE context retrieval with and without Xa connectivity
22
14.2
Topology 2
20
13.2
Sensing information transfer
19
10.2.1
Data collection
18
10.5.1
AI/ML use cases
18
10.5.2
AI/ML framework
15
12.2.2
Intra-CU LTM
15
10.3.1.2
Point to Point Interface (P2P)
14
10.3.2
RAN-CN control plane for connectivity services
14
10.8.1
Service Characteristics Awareness and Performance Monitoring
14
15.2
LTM SCell activation enhancements
14
Built by 3GPP Scout from the public meeting record (422 TDocs registered, catalog synced 2026-11-09). 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.