hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 4.6.2 Protocol stack for sensing data transfer
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5 High level functionality and features
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.1 Authorization and revocation aspects
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.1.1 Authorization and revocation of Sensing Service Consumers
| If the AF as Sensing Service Consumer is outside the trusted domain, authorization of the sensing service consumer is performed by the NEF as defined in clause 12 of TS 33.501 [6]. If the AF is inside the trusted domain, authorization of the Sensing Service Consumer is performed according to clause 13.3 as defined in T... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.1.2 Authorization and revocation of Sensing Service Requests
| The SenF authorizes the received Sensing Service Request, considering the Sensing Authorization information described in Table 5.1.2-1, and
1) if the authorization is granted, SenF proceeds the Sensing Service Request, as specified in clause 6.2.
2) if the authorization is not granted, the SenF rejects the Sensing Se... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.2 Discovery and selection aspects
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.2.1 SenF discovery and selection
| The SenF Discovery and Selection functionality is to determine an SenF to handle Sensing Service Request from a Sensing Service Consumer (i.e. AF).
The SenF Discovery and Selection functionality is supported by the AF or the NEF. The AF or the NEF selects an SenF either by querying the NRF or by using the locally conf... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.2.2 SenE discovery and (re-)selection
| The SenE discovery and (re-)selection functionality is to determine one or more SenE(s) (i.e. gNB(s)) to handle a sensing service request.
The SenF obtains the information needed for SenE(s) discovery and selection via OAM or local configuration, and selects SenE(s) based on the sensing service request (e.g. target se... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.3 Sensing data collection and transport
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.4 Sensing service exposure
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.4.1 General
| SenF generates and provides sensing results for a given sensing service request
- to the NEF and then the NEF, using the exposure framework, provides the sensing results to the AF or
- to the AF within the operator trusted domain.
|
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.4.2 Sensing Service Request
| A sensing service request from a Sensing Service Consumer (i.e. AF) includes AF Identifier, target sensing service area, sensing service type (e.g., object detection, tracking).
Editor’s Note: The other parameters in the sensing service request and the definitions of them are FFS.
|
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.4.3 Sensing Result
| A sensing result includes sensing content (e.g., presence and position of the object), sensing timestamp.
Editor’s Note: The details of sensing result are FFS.
|
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 5.5 Sensing service parameters for SenE(s)
| The SenF is responsible for providing sensing parameters to the SenE(s).
The SenF derives the sensing parameters based on the sensing service requirement (e.g. Target sensing service area) received from the sensing service consumer (i.e., AF) in the sensing service request.
The SenF may update the sensing parameter... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 6 Sensing procedures
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 6.1 Overview
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 6.2 Procedures for end-to-end sensing service operations
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 7 Network Function services
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 7.1 General
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 7.2 NEF services
| |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 7.3 SenF services
| Annex A
Annex B (informative):
Change History
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2026-02
SA2#173
S2-2601539
-
-
-
[Sensing-ARC] Draft TS Skeleton
0.0.0
2026-02
SA2#173
-
-
-
-
Inclusion of documents approved in SA2#173:
S2-2601515, S2-2601547, S2-260... |
0ab65e75fc1089aa73e560eaf8cd0098 | 23.137 | 7 Network Function services
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 1 Scope
| This clause shall start on a new page.
The present document …
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 3 Definitions of terms, symbols and abbreviations
| This clause and its three subclauses are mandatory. The contents shall be shown as "void" if the TS/TR does not define any terms, symbols, or abbreviations.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify ... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
Abbreviation format (EW)
<ABBREVIATION> <Expansion>
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4 QUIC-based streaming protocols
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.1 General
| Editor’s Note: This clause introduces the relevant protocols.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2 Protocols for media streaming
| Editor’s Note: Protocols are details in the respective subclauses
Editor’s Note: The protocol to be used as baseline (DASH over HTTP 1.1) will be listed here as well.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2.1 Media over QUIC
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2.1.1 Introduction
| Media over QUIC (MoQ) is an IETF working group effort to standardize a publish/subscribe media delivery system over QUIC and WebTransport-over-HTTP/3 [X.1], designed for high scale and low-latency and explicitly supporting intermediaries such as relays, caches, and replication points.
The “MoQ” umbrella is broader th... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2.1.2 Technical design
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2.1.3 Features
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.2.1.4 Targeted applications
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.3 Other protocols
| Editor’s Note: This clause contains protocols that are QUIC-based but were not considered in the evaluation. To be removed if empty.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 4.4 Summary
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5 Evaluation setup
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.1 General
| Editor’s Note: This clause contains the details of the evaluation.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2 Considered applications
| Editor’s Note: This clause contains details on which media streaming applications will be evaluated.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.1 On-demand long form streaming
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.1.1 Description
| This scenario represents traditional segmented on-demand streaming where user experience is primarily driven by time-to-first-frame (TTFF), rebuffering avoidance, and steady-state delivered quality. The downlink traffic is characterized by relatively long sessions with stable demand, high cacheability, and predictable ... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.1.2 Requirements
| TBD
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.1.32 Analysis
| This scenario is a baseline to evaluate whether QUIC-based delivery (e.g., HTTP/3) improves startup robustness, reduces rebuffering under loss, and stabilizes bitrate selection without changing the application semantics or CDN caching model.
This application scenario exhibits the following delivery characteristics:
-... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.2 Live streaming at scale
| 5.2.2.1 Description
This scenario targets one-to-many distribution with very high fanout, where edge replication and caching efficiency are critical for scalability and cost. Downlink behavior includes synchronized consumption of a common live timeline, significant join/rejoin activity (notably at event start and dur... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.2.2 Requirements
| TBD
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.2.32 Analysis
| This scenario is central for comparing DASH over HTTP/1.1 versus other QUIC-based options in terms of join time, live latency distribution, stability under congestion/loss, and operational scalability.
This application scenario exhibits the following delivery characteristics:
- Latency target: ~15–45+ s (service depe... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.3 Low-latency live streaming
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.3.1 Description
| This scenario covers live services with tight latency budgets (e.g., interactive sports experiences, live commerce, auctions), where “tail latency” and timeliness are as important as average latency. Downlink delivery in this scenario typically uses very small chunks/parts and constrained playback buffers to reach low ... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.3.2 Requirements
| TBD
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.3.32 Analysis
| This scenario is the main stress test for QUIC-based approaches, highlighting where HTTP/3’s transport properties may improve the QoE of the conventional segmented model, and where alternatives such as WebTransport or MoQ-style object delivery might reduce overhead and improve timeliness under loss and mobility.
This ... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.4 Short-form video streaming
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.4.1 Description
| This scenario is characterized by extremely high churn: sessions are short, users frequently abandon playback within seconds, and the platform relies heavily on prefetch and fast startup to maintain engagement. The downlink traffic pattern is bursty, with many small or partial transfers, frequent representation switche... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.4.2 Requirements
| TBD
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.4.23 Analysis
| This scenario is relevant to quantify QUIC’s potential benefits in setup/handshake amortization, reduced head-of-line effects between concurrent transfers, improved performance under lossy access networks, and reduced per-request overhead, factors that can materially affect TTFF and abandonment.
This application scena... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.5 Uplink contribution for live services
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.5.1 Description
| This scenario couples a challenging uplink contribution path with large-scale downlink distribution, reflecting modern “creator live” streaming services. The uplink is often mobile and highly variable, with fluctuations in available bitrate, RTT, loss, and NAT rebinding. The downlink simultaneously requires scalable fa... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.5.2 Requirements
| TBD
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.2.5.23 Analysis
| This scenario is particularly relevant to assess QUIC features that support robustness and continuity across path changes, to compare QUIC-based segmented delivery against alternatives that may offer faster re-attachment (e.g., relay-based approaches), and to evaluate system-level KPIs such as recovery time after impai... |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.3 Metrics selection
| Editor’s Note: This clause lists the metrics that are relevant to the evaluation.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 5.4 Other considerations
| Editor’s Note: This clause will include other parameters to be taken in consideration during the evaluation setup. To be removed if empty.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6 Performance evaluation tests
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.1 General
| Editor’s Note: This clause details the actual evaluations to be tested and collects the results of the tests.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.2 Evaluation testbed setup
| Editor’s Note: This clause contains details how the test framework of TR 26.934 is applied.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.3 Test scenarios
| Editor’s Note: This clause lists the tests executed and the results observed.
6.32.1 <Test scenario 1 name>
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.32.1.1 Description
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.32.1.2 Simulation results
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.32.1.3 Analysis
| |
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.4 Test results analysis
| Editor’s Note: This clause contains the cross-test analysis.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 6.4 Evaluation summary
| Editor’s Note: Summary of the observed results and overview of the performance compared to the baseline.
|
af2769d35ec69484ac37617a2ce6eecc | 26.835 | 7 Conclusions and recommendations
| Editor’s Note: This clause provides the conclusions of this study and potential recommendations.
Annex <A> (informative):
Considerations for integration of the protocols in the media delivery architecture
Editor’s Note: This clause provides information on integrating the examined protocols in the current ecosystem... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 1 Scope
| This clause shall start on a new page.
The present document …studies application enablement and exposure aspects for 3GPP 6G system by identifying key issues and, when applicable, associated use cases, and examining potential solutions and associated architectural considerations. The application enablement and exposur... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 3 Definitions of terms, symbols and abbreviations
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Definition format (Normal)
<defined term>: <definition>.
example: text used to clarify abstract r... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
Abbreviation format (EW)
<ABBREVIATION> <Expansion>
|
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4 Key issues
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.1 Exposure framework aspects
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.1.1 Key issue 1.1: Intent-based exposure
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.1.1.1 Description
| 3GPP exposure framework (e.g., CAPIF) is designed to provide a standardized and secure framework for enabling communication between third-party applications and 3GPP system in mobile networks. CAPIF APIs are built around a traditional service-based architecture (SBA) approach that aligns with 5G core network principles... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.1.1.2 Applicability to other aspects
| This key issue requires coordination with WT#3 (AIML Aspects) regarding the role of AI Agents in intent translation and WT#2 (Application Enabler Service Aspects) regarding providing services derived from intents.
|
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.1.1.3 Open issues
| 1. What capabilities are required in the exposure framework to support intent-based interfaces and how would these capabilities be utilised by consumers of the exposure framework?
2. How can the exposure framework support intent-based interfaces and what is the format used to express an intent in the context of the ex... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.2 Application enabler service aspects
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.2.1 Key issue 2.1: Application Data Management
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.2.1.1 Description
| 6G systems are expected to handle massive volumes of heterogeneous data, including sensing data, AI/ML data, spatial maps, and digital twin states, which differ significantly from traditional user traffic. Current specifications often address data management in a fragmented manner. The 6G system requires a framework to... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.2.1.2 Applicability to other aspects
| This key issue may require coordination with WT#1 (Exposure Framework Aspects) regarding the APIs used to expose data.
|
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.2.1.3 Open issues
| The open issues to be studied include:
1. What categories of application data (e.g. vertical application data, application enablement layer data) can be handled at the application enablement layer?
2. Whether and how the application enablement layer can leverage a data management service that can handle the storage, ... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.3 AIML aspects
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.3.1 Key issue 3.1: Unavailability of sufficient training data
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.3.1.1 Description
| 3GPP specified various analytics services, for consumption by third party Application Functions (AFs). These standardized analytics services are consumed by the service consumers and apply for any improvement of their service offerings. 3GPP TS 23.436 [3] specifies the architecture and functional information flows for ... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.3.1.3 Open issues
| The following aspects need to be studied:
- Whether and how to provide the ADAE and AIMLE services, when there is no sufficient training data available.
4.3.x Key issue 3.x: <title>
4.3.x.1 Description
This clause provides details of the key issue related to the aspect addressed in this clause.
4.3.x.2 Applicabili... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.4 Communication aspects
| 4.4.x Key issue 4.x: <title>
4.4.x.1 Description
This clause provides details of the key issue related to the aspect addressed in this clause.
4.4.x.2 Applicability to other aspects
N/A, unless this key issue has applicability across aspects rather than only this sub-clause’s main aspect.
4.4.x.3 Open issues
This... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.5 Compute and communication aspects
| 4.5.x Key issue 5.x: <title>
4.5.x.1 Description
This clause provides details of the key issue related to the aspect addressed in this clause.
4.5.x.2 Applicability to other aspects
N/A, unless this key issue has applicability across aspects rather than only this sub-clause’s main aspect.
4.5.x.3 Open issues
This... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.6 Integrated sensing and communication aspects
| 4.6.x Key issue 6.x: <title>
4.6.x.1 Description
This clause provides details of the key issue related to the aspect addressed in this clause.
4.6.x.2 Applicability to other aspects
N/A, unless this key issue has applicability across aspects rather than only this sub-clause’s main aspect.
4.6.x.3 Open issues
This... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.7 Digital twin aspects
| 4.7.x Key issue 7.x: <title>
4.7.x.1 Description
This clause provides details of the key issue related to the aspect addressed in this clause.
4.7.x.2 Applicability to other aspects
N/A, unless this key issue has applicability across aspects rather than only this sub-clause’s main aspect.
4.7.x.3 Open issues
This... |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.8 Common aspects
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.8.1 Key issue 8.1: representation of the application enablement layer as part of 3GPP 6G system
| |
35c11477334a60f3fc6bc1c5bbec28f7 | 23.801-02 | 4.8.1.1 Description
| In the 5G era, 3GPP application enablement layer framework, i.e., CAPIF, is specified in 3GPP TS 23.222 [5]. However, when referring to the 5G architecture, the industry primarily refers 3GPP TS 23.501 [6], where CAPIF is only optionally supported by the NEF. Consequently, it is difficult for the industry to recognize ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.