Approved paging reply. The register records approval of an outgoing reply LS to RAN2 and SA2 on single paging for idle and inactive in 6G. Its substantive reply is unavailable in this pack.
Retrieval pCR not pursued. The register marks a pCR on UE context retrieval with and without Xa connectivity not pursued. This is separate from the approved paging reply and does not establish a retrieval procedure.
ISAC inputs not pursued. Two ISAC procedures and signaling contributions, and a draft LS on measurement parameter reuse and physical layer definitions, were marked not pursued. These dispositions do not approve or reject an ISAC procedure.
P2P and unified-interface pCRs not pursued. The pCR on P2P for non-connectivity services and the pCR considering a unified RAN-CN interface were both marked not pursued.
Further P2P pCRs not pursued. The pCR on a P2P-based RAN-CN interface and the pCR on a P2P solution with AMF for new services were also marked not pursued. These statuses do not establish an interface choice.
When direct Xa is unavailable, should the CN relay UE context or store it for RRC Inactive?
Qualcomm proposes telling SA2 to prefer retrieval via the CN over CN storage; Lenovo likewise prefers transfer via the CN, and Apple proposes a transparent CN relay for its Case B. Vodafone's broader RRC Inactive proposal calls for RAN-only storage rather than reliance on CN-based context identification and retrieval.
QualcommPrefers retrieval via the CN over CN storage without direct Xa.
Proposal 5: RAN3 indicate to SA2 that, when direct Xa connectivity between aNBs is unavailable, retrieval of UE context from the last serving aNB via [...]
VodafoneProposes RAN-only RRC Inactive storage, not reliance on CN-based identification and retrieval.
Therefore, even though reducing resume latency is a valid objective, it is proposed to agree that, for RRC Inactive operation, the UE context should be [...]
How should retrieval over Xa handle direct links, multi-hop paths and the resume ID?
NEC proposes direct retrieval when the new aNB has a direct Xa interface to the last serving aNB; AT&T urges consideration of multi-hop retrieval as preferred when an Xa path exists. China Mobile proposes studying a resume ID that may at least include identifiers for the last serving aNB and a UE context unique within it.
NECProposes fetching context directly over Xa when the aNBs have a direct interface.
For the case UE resumes in a new aNB that has a direct Xa interface to the last serving aNB, UE context can be fetched [...]
China MobileProposes studying resume ID design and possible identifiers.
In UE context retrieval with Xa connectivity case, RAN3 study resume ID design which may at least include the identification of the last serving aNB [...]
Should RAN-CN P2P use SCTP for connectivity services, and where else should P2P be considered?
China Mobile proposes SCTP for the connectivity-services P2P interface, while Deutsche Telekom describes SCTP-based P2P as the most mature option for those services. AT&T proposes considering P2P for specified non-connectivity interactions; its contribution was noted, not agreed as an interface choice.
China MobileProposes SCTP-based P2P for connectivity services.
Proposal 1: The SCTP based protocol is used towards P2P interface for connectivity services.
What procedures and messages should be developed for ISAC signaling and the Ns interface?
Samsung proposes that signaling procedures in TR 38.765 also be agreed in the WI phase; LG Electronics proposes annex text for Ns interface procedures, and Huawei proposes gNB-initiated Ns Setup messages for NsAP. Huawei's ISAC TP was marked not pursued, and these submissions do not establish a meeting agreement.
SamsungSeeks WI-phase agreement on signaling procedures captured in TR 38.765.
Proposal 2: The signaling procedures captured in TR 38.765 should be agreed in WI phase as well.
HuaweiProposes gNB-initiated Ns Setup messages within NsAP.
The Ns interface management function include the following messages, which can be incorporated into the NsAP: gNB-Initiated Ns Setup: a Class 1 procedure (i.e., Ns [...]
R3-263597 Reply LS to R2-2602817 = R3-262066 and S2-2606684 = R3-263017 on single paging mechanism for idle and inactive in 6G (to: RAN2, SA2; cc: SA3; contact: ZTE). 3GPP RAN3. Outgoing LS. Register status: approved at R3-133.
R3-263173 (pCR to TR38.760-3) Discussion on UE context retrieval with and without Xa connectivity in 6G. ZTE. pCR. Register status: not pursued at R3-133.
R3-263064 (TPs for ISAC) Procedures and signaling. Huawei. Contribution. Register status: not pursued at R3-133.
R3-263058 (pCR to TR 38.760-3) On P2P IF for 6G non-connectivity services. Qualcomm (with T-Mobile USA, NTT DOCOMO, FiberCop). pCR. Register status: not pursued at R3-133.
R3-263110 Consideration on unified RAN-CN interface solution. Huawei. pCR. Register status: not pursued at R3-133.
R3-263100 ISAC RAN-CN procedure model and signaling content. InterDigital. Contribution. Register status: not pursued at R3-133.
R3-263540 Draft LS on measurement parameter reuse and physical layer definitions for ISAC (to: RAN1; cc: SA2; contact: Xiaomi). Xiaomi. Outgoing LS. Register status: not pursued at R3-133.
R3-263139 Discussion on P2P based RAN-CN interface. Samsung. pCR. Register status: not pursued at R3-133.
R3-263220 P2P solution with AMF for new Services. Nokia. pCR. Register status: not pursued at R3-133.
R3-263270 UE context retrieval in 6G Inactive state with single paging. Qualcomm. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263312 Discussion on UE context retrieval in 6G. Lenovo. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263410 6G UE Context Retrieval without Xa connectivity. Apple. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263092 Views on RRC Inactive in 6G and answers to SA2. Vodafone. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263184 6G paging and UE context retrieval. NEC. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263070 Discussion on UE context retrieval with and without Xa connectivity. AT&T. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263480 Discussion on UE context retrieval with and without Xa connectivity. China Mobile. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263477 Discussion on P2P interface for RAN-CN interface design. China Mobile. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263211 Protocol stack considerations for RAN-CN P2P interface for connectivity services. Deutsche Telekom. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263066 Discussion on P2P for RAN-CN Control Plane. AT&T. Contribution. Register status: noted at R3-133.
R3-263145 Discussion on procedures and signaling. Samsung. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
R3-263417 Discussion on NsAP protocol functions and procedural details. LG Electronics. Contribution. Register status: not treated at R3-133. No decision recorded in the register.
Coverage: RAN3 #133 (Maastricht, 2026-08-24 to 2026-08-28), agenda items 10.6.1, 13.3, 10.3.1.1. Scout read 9 recorded decisions and 146 company positions or contribution passages on these agenda items (catalog synced 2026-09-29) and cites 9 decisions and 13 positions from 21 TDocs. Every quoted passage was matched verbatim against the TDoc text; the summaries around the quotes are Scout's reading. Register statuses are copied from the 3GPP TDoc register: not treated means a document was not handled on its own, though its content may have fed feature-lead summaries or merged revisions. Not covered: other agenda items and meetings, plenary TDocs and plenary decisions after the meeting, email discussions after the meeting, and anything not yet in the chair notes or register.
No chair notes, session report, feature-lead summary or text of the approved reply LS was supplied.
Company contributions marked not treated are proposals submitted to the meeting; this pack does not establish that they were discussed.
Hottest topics
UE context retrieval with and without Xa connectivitysignificance 58 of 100, 29 TDocs
Procedures and signalingsignificance 57 of 100, 31 TDocs
Point to Point Interface (P2P)significance 50 of 100, 25 TDocs
Service Based Interface (SBI)significance 46 of 100, 18 TDocs
LTM SCell activation enhancementssignificance 46 of 100, 22 TDocs
Built by 3GPP Scout from the public meeting record (623 TDocs registered, catalog synced 2026-09-29). 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.