RAN2 #135-bis preview: what the meeting will debate
12 October to 16 October 2026South Korea3GPP TSG RAN WG2Last updated 2026-10-11
At a glance
The meeting is working through sensing operation, connected mode mobility, AI/ML lifecycle management and uplink scheduling. Several proposals address how much configuration to reuse and when reporting is needed. Others test whether existing uplink procedures fit new service requirements. The main technical tension is between simpler baselines and mechanisms tailored to particular operating conditions.
1Hottest topics
ISAC
Significance 42 of 100, 43 TDocs
ISAC proposals address both how a sensing UE obtains information and how a sensing entity is selected. One proposal considers broadcasts of downlink sensing resources and assistance information, alongside requests initiated by the sensing UE. Another places TRP or aNB selection with the sensing function, using service area and deployment information. These approaches concern different stages of sensing operation, from supplying a UE to choosing the network-side entity.
To improve the efficiency of UE-centric operation mode, the following solutions can be considered: - The network can directly broadcast the DL radio resource configuration ...
Connected mode mobility proposals focus on the structure and control of pre-configured candidates. A shared candidate configuration is proposed across network-triggered and UE-triggered mobility types, including operation without pre-configuration. Another proposal considers activating and deactivating pre-configurations as network needs change. Together, the proposals put configuration reuse and the ability to change active candidates in play.
Proposal 2: In order to address the shortcoming of similar or duplicated configuration for separate cell switch, one common pre-configured candidate configuration is shared/applicable for ...
Proposal 4: To allow greater flexibility for the network to dynamically change the pre-configurations, the activation and deactivation of pre-configurations could be considered in 6G ...
LCM procedure work addresses repeated inference reports and the cell scope of performance monitoring. A proposed prohibit timer prevents another report for the same predicted event while that timer runs. A separate proposal applies the allowed cell list in NR reporting configuration to predictions, as it applies to legacy measurements. The two proposals affect different parts of the procedure: report frequency and which cells a prediction covers.
For indirect event prediction for temporal domain case A, following approaches can be taken into consideration to avoid frequent and duplicated inference reporting: A prohibit ...
AI/ML proposals put functionality-based LCM forward as a 6G baseline, while also calling for study of model-based LCM. Applicability reporting has a separate choice between a proposed Option A baseline and an argument that Option B has lower signaling overhead. The Option A proposal also covers initial and updated reports when applicability changes. These are contested proposals, so neither the lifecycle baseline nor the reporting approach is settled by them.
Uplink scheduling proposals differ on whether the existing two-step LCP procedure is a suitable starting point for 6G. One proposes it as a possible baseline with study of dynamic parameter adjustment. Another raises concern that existing LCP does not meet QoS requirements in some 6G use cases. For CB-PUSCH, a proposed model based on two-step random access faces a separate concern about replacing scheduling requests across different loads.
RAN2 to define a unified applicability reporting framework: Use Option A as the baseline, and support Option B only when the benefits are shown and ...
For applicable reporting, Option B has less signaling overhead compared to Option A considering not all parameters within full inference configuration are used for applicability ...
Functionality for Upper User Plane and related functional requirements
40
9.3.3.3
Energy efficiency
39
9.3.1.3.2
UL resource allocation and request
38
9.3.1.3.1
Scheduling Information
37
9.3.2.1
RRC Modelling and connection management
34
9.3.3.1
Data transfer
34
8.3.2
LCM procedure
33
Built by 3GPP Scout from the public meeting record (1370 TDocs registered, catalog synced 2026-10-11). 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.