hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
5.5.4 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures. 5.x Solution #x: <title> Provide a suitable title for the solution. 5.x.1 Solution description This clause will describe the solution. Each solution should clearly describe wh...
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
6 Deployment scenarios
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
6.1 General
This clause will provide a general description of the deployment scenarios.
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
7 Business Relationships
Provide a description of the involved business relationships.
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
8 Overall evaluation
This clause will provide evaluation of different solutions.
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
9 Conclusions
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
9.1 General conclusions
This clause will provide general conclusions for the study.
a73f5408ee78d2de0a0badee0c4cf584
23.700-02
9.2 Conclusions of key issue #x
This clause will provide conclusions for the specific key issue. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2025-09 SA6#68 S6-253656 Skeleton for TR 23.700-02 0.0.0 2025-09 SA6#68 S6-253655 Key Issue on AIML model storage and deplo...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
1 Scope
The present document is a technical report which identifies potential enhancements to application enablement services by utilizing Sensing results and proposes architectural requirements, key issues, and solutions for the potential application enablement architecture enhancements. The study takes into consideration t...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
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. -...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
3 Definitions of terms, symbols and abbreviations
3e26027ac593756f9c48ee9868ce45b2
23.700-15
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]. For the purposes of the present document, the terms given in 3GPP TS 22.137 [3] apply. ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
3.2 Symbols
For the purposes of the present document, the following symbols apply: Symbol format (EW) <symbol> <Explanation>
3e26027ac593756f9c48ee9868ce45b2
23.700-15
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]. SEAL Service Enabler Architecture Layer for Verticals UAE UAS A...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4 Key issues
4.1 Key issue #1: Application enablement architecture enhancements to support utilization and exposure of sensing results
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.1.1 Description
3GPP TR 22.837[6] and TS 22.137[3] specify a set of service requirements about sensing which may have potential impacts on the application enabler layer. - Subject to operator’s policy, the 5G network shall be able to provide secure means to report sensing results to a trusted third-party requesting information about ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.1.2 Open Issues
Based on the above analysis, the following aspects need to be addressed in the application enabler layer: 1. Whether and how to enhance the application enablement architecture and related functions to support the mapping of sensing service requirements of vertical applications. 2. Whether and how the existing exposur...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.2.1 Description
3GPP TS 22.137 [3] has specified sensing service requirements about UAVs. Such as "The 5G system shall be able to provide sensing service to detect, and/or track one or more objects (e.g., UAVs, birds) and the environment around the object(s). " In Rel-19, the application enabler (i.e. UAE) has been developed to supp...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.2.2 Open Issues
Based on the above analysis, the following open issues need to be studied: - How to enhance the UAS application enabler to support enhanced trajectory tracking for UAVs utilizing the sensing results. - How to enhance the UAS application enabler to support enhanced DAA service/functionalities for UAVs utilizing the se...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.4 Key issue #4: utilizing sensing results for HD map in V2X
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.4.1 Description
According to application layer support for Vehicle-to-Everything (V2X) services specified in 3GPP TS 23.286 [5], the V2X application specific server can be responsible for managing HD maps and providing the HD map information to the V2X application specific client on V2X UE. As per a proximity range set by the applicat...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
4.4.2 Open issues
Based on the above analysis, the following open issue need to be studied: 1. How to enhance VAE layer to provide enhanced HD map including traditional vehicles information with considering sensing results. 2. How to enhance VAE layer to provide enhanced HD map including environment information (e.g. pedestrian/animal...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
5 Architectural Requirements and Assumptions
This clause provides the architectural requirements and assumptions.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6 Solutions
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.1 Mapping of solutions to key issues
Table 6.1-1 Mapping of solutions to key issues KI #1 KI #2 KI #3 KI #4 Sol #1 x Sol #2 x Sol #3 x Sol #4 x Sol #5 x Sol #6 x Sol #7 x Sol #8 x Sol #9 x Sol #10 x Sol #11 x Sol #...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2 Solution #1: Functional Architecture to Support Sensing Application Relevant Services
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1 Solution Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.0 General
There are some common requirements from difference sensing application relevant services, for example, sensing data/result collection, sensing result aggregation, sensing result exposure. Enhancements to the application enablement layer architecture are needed to introduce common functionalities to fulfil these comment...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.1 Functional Model
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.1.1 General
The functional architecture enhancement for the SEAL Sensing Enabler is based on the generic functional model specified in clause 6.2 of 3GPP TS 23.434 [2]. It is organized into functional entities to describe an architecture enhancement which addresses the support for sensing aspects for vertical applications.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.1.2 Network Functional Model
Figure 6.2.1.1.2-1: Network functional model Figure 6.2.1.1.2-1 illustrates the network functional model with SEAL Sensing Enabler. In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. The SEAL functional entity with sensing enabler function on the server is...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.2 Functional Entities Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.2.1 General
The SEAL Sensing Enabler functional entities with sensing application relevant service functions are described in the following subclauses.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.2.2 SEAL Sensing Enabler client
The SEAL Sensing Enabler client interacts with the SEAL Sensing Enabler server. NOTE: In this release, the SEAL sensing client is not used for sensing data collection.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.2.3 SEAL Sensing Enabler server
The SEAL Sensing Enabler server functional entity provides for sensing application relevant services supported within the vertical application layer.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.3 Reference Points Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.1.3.1 General
The reference points for the functional model for sensing application relevant service are described in the following subclauses. Editor’s Note: The description of reference points is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.2.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.3 Solution #2: Support the sensing results exposure based on the sensing subscription request
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.3.1 Solution description
This solution aims to address the issues identified in Key Issue 1 and provides a possible procedure to perform the sensing results exposure. Editor's note: This solution is built on functional architecture described in solution X for key issue 1. The sensing capabilities in the enabler layer may be provided by a sepa...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.3.2 Procedures
The high-level procedure of sensing service exposure is shown in Figure 6.3.2-1. Pre-conditions: 1. The Sensing enabler server has acquired sensing capability information of one or more Sensing Service Supplier(s). Figure 6.3.2-1: Sensing service exposure procedure 1. The VAL Server/Client acting as sen...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.3.3 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.4 Solution #3: Support of exposure of sensing results
This solution addresses the KI#1.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.4.1 Procedure of exposure of sensing results
This solution proposes a new enabler (i.e., Sensing Enabler Server) to support the exposure of sensing results to the consumers (e.g., VAL server). The Sensing Enabler server may interact with other SEAL enabler to get the value-added sensing results. Figure 6.4.1-1 illustrates the high-level procedure of exposure of...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.4.2 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.5 Solution #4: Enhancements of UAV services utilizing the sensing results
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.5.1 Solution description
This solution addresses the KI#2. The following high-level solution principles apply to this solution: - A high-level procedure for sensing request and exposure is proposed with a new Sensing enabler in the application enablement layer. - The solution assumes the 3GPP core network will expose the sensing results r...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.5.1.1 Procedure of detecting UAVs utilizing sensing results
Figure 6.5.1.1-1 illustrates the high-level procedure of detecting UAVs utilizing sensing results. Pre-condition: - The following Sensing enabler is a new enabler that implements the sensing functions in the application enablement layer. Figure 6.5.1.1-1: Procedure of detecting UAVs utilizing sensing results ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.5.2 Architecture Impacts
This solution proposes a new sensing enabler to support the sensing service. For the new architecture for the sensing enabler, pls check the solution for the KI#1.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.5.3 Solution evaluation
This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6 Solution #5: sensing based tracking dynamic UAVs
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6.1 Solution description
This solution intends to solve the first open issue of key issue #2. This solution is to enhance tracking dynamice UAV service by utilizing sensing results.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6.2 Procedures
This feature utilizes the following procedures: - Step 1: UAS Application Specific Server or the host UAV subscription for host UAV’s dynamic information with UAE server. - Step 2: UAE server tracking host UAV’s UE location with support from SEAL’s location management server. - Step 3: UAE server management of dynam...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6.2.1 Subscription for host UAV dynamic information
This procedure intends to obtain the host UAV dynamice information, the procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] is reused. 6.6.2.2 UAE server management of dynamice area for sensing Figure 6.6.2.2-1 describes the procedure for management of dynamic area for sensing. Pre-condition: - UAE server 1 has rec...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6.2.3 UAE server obtaining dynamic information from sensing results
Figure 6.6.2.3-1 describes the procedure of obtaining dynamic information from sensing results. Pre-condition: - UAE server 1 is configured with NEF information of their supported region of operation. Figure 6.6.2.3-1: Obtaining dynamic information from sensing results 1. The UAE server 1 determines the NEF(s) op...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.6.2.4 Notification of host UAV dynamic information
Pre-conditions: - UAS Application Specific Server has performed subscription as per procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] with UAE server 1. - UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3 in 3GPP TS 23.255 [4]. Figure 6.6.2.4: Notification for host UA...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7 Solution #6: Sensing based DAA service
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.1 Solution description
This solution intends to solve the second open issue of key issue #2, i.e. enhance DAA service by utilizing sensing results. This solution is based on the procedures in clause 7.7.2 of 3GPP TS 23.255 [4].
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.2 Procedures
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.2.1 Configuration of sensing based DAA policies to the UAE layer
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.2.1.1 Management of DAA support configuration
Figure 6.7.2.1.1-1 illustrates the DAA support management procedure where the UAE server receives an application request for managing the DAA application policy from the UAS application specific server. Pre-conditions: 1. The UAV has received its UAS ID from the UAS application specific server. 2. The UAV has perfor...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.2.1.2 Sensing based DAA support configuration procedure
Figure 6.7.2.1.2-1 illustrates the sensing based DAA support configuration procedure. This procedure enables the configuration of the UAE server, based on a request from UAS application specific server to configure the sensing based DAA application policy. Pre-conditions: 1. UAE server has performed the DAA support m...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.7.2.2 Sensing based DAA event reporting
Figure 6.7.2.2-1 illustrates the procedure of sensing based DAA event reporting. Pre-conditions: 1. UAE server has detected UAVs in approaching as specified in 6.7.2.1.2. Figure 6.7.2.2-1: Sensing based DAA event reporting 1. The UAE server shall send a sensing based DAA event information to the UAS application s...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.1 Solution Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.1.0 General
The Spatial Map Server can benefit from sensing (including 3rd Party sensing services) data or results to build high-quality Spatial Map. As sensing capabilities rely on the CSP’s infrastructure, which may provide full coverage. And the rollout of the CSP’s sensing service takes time, coverage remains incomplete durin...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.1.1 Procedure
Figure 6.8.1.1-1: Sensing coverage information exposure 1. The Consumer (VAL Server, SEAL Server) sends check sensing coverage information request to the SEAL Sensing Server. 2. The SEAL Sensing Server authenticates the request, checks the stored sensing coverage information, and determines the next actions...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.1.2 Information Flows
Editor’s Note: The information flows of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.8.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS. 6.9 Solution #8: Use Sensing Results for Creating Spatial Map
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.1 Solution Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.1.0 General
The Spatial Map Server can benefit from sensing (including 3rd Party sensing services) data or results to build high-quality Spatial Map. The following clauses specify use combination of sensing results for creating spatial map.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.1.1 Procedure
Figure 6.9.1.1-1: Sensing results for creating spatial map 1. The Spatial Map Server sends sensing result request for consolidated sensing results from the SEAL Sensing Server. 2. The SEAL Sensing Server authenticates the request, and determines the sensing entities (e.g., 5GC NFs, 3rd party sensing server)...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.1.2 Information Flows
Editor’s Note: The information flows of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.9.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.10 Solution #9: high level architecture and procedures for use of sensing results for spatial map
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.10.1 Description
This solution resolves solution of KI#3 on use of sensing results for spatial maps. This solution is based on following principles: 1. No significant changes are made to the spatial map management procedures defined in 3GPP TS 23.437 [8]; 2. A separated SEAL Sensing service server is provided by Enabler layer and i...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.10.2 Procedures
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.10.2.1 Create spatial map with sensing capabilities
Figure 6.10.2.1-1 below illustrates the procedure for creating a spatial map when sensing capabilities are introduced. For the request from VAL server or SEAL SM client, as a spatial map consumer. SEAL SM server creates a spatial map by utilizing sensing capabilities provided by SEAL Sensing server. Pre-conditions: ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.10.2.2 Spatial map subscription and notification with sensing capabilities
Figure 6.10.2.2-1 below illustrates the procedure for Spatial map subscription and notification with sensing capabilities. It is based on the Subscribe spatial map event specified in clause 9.3.6.2.1 of 3GPP TS 23.437 [8] and Notify spatial map event specified in clause 9.3.6.2.2 of 3GPP TS 23.437 [8]. Pre-conditions:...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.11 Solution #10: Sensing results for spatial maps
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.11.1 Solution description
This solution addresses Key Issue #3, open issues #2 and #4 on how the sensing enabler layer can support SM server with creating a spatial map and to associate a sensing result with an object in a spatial map. The solution proposes enhancements to Create spatial map and Update spatial map procedures in 3GPP TS 23.437 [...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.11.2 Procedures
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.11.2.1 Impact to Create spatial map procedure
The Create spatial map procedure and information flows in 3GPP TS 23.437 [8] are enhanced (highlighted in bold italics) as follows.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.1.2 Procedure
Figure 9.3.1.2-1 depicts the procedure for creating a spatial map. For the request from VAL server or SEAL SM client, as a spatial map consumer, SEAL SM server creates a spatial map. A spatial map can be structured in layers where each layer signifies a specific aspect of the spatial information (e.g. three dimensional...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.1.3 Information flows
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.1.3.1 Create spatial map request
Table 9.3.1.3.1-1 descibes the information elements from VAL server (or SEAL SM client) to SM server for create spatial map request. Table 9.3.1.3.1-1: Create spatial map request Information element Status Description Requestor identifier M The identifier of the requestor (e.g., VAL server or VAL User or VAL UE)...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.11.2.2 Impact to Update spatial map procedure
The Update spatial map procedure and information flows in 3GPP TS 23.437 [8] are enhanced (highlighted in bold italics) as follows.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.4 Update spatial map
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.4.1 General
The update spatial map procedure enables the consumers to request the SEAL SM Server to update a spatial map.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.4.2 Procedure
Figure 9.3.4.2-1 depicts the procedure to update the spatial map. For the request from the spatial map consumer (VAL server or SEAL SM client), SEAL SM server updates the spatial map as requested. Figure 9.3.4.2-1: Update spatial map procedure 1) The requestor (e.g., VAL server or SEAL SM client) sends a request...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.4.3 Information flows
3e26027ac593756f9c48ee9868ce45b2
23.700-15
9.3.4.3.1 Update spatial map request
Table 9.3.4.3.1-1 descibes the information elements for update spatial map request from VAL server or SEAL SM client to SEAL SM server. Table 9.3.4.3.1-1: Update spatial map request Information element Status Description Requestor identifier M The identifier of the requestor (e.g., VAL server or VAL User or VAL ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.1 Solution Description
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.1.0 General
Sensing plays an important role in smart transportation. Most modern cars are equipped with onboard sensors – radar, lidar, and cameras just to mention a few – which help the car to get an overview of its immediate surroundings. However, onboard systems fail to provide information further away and cannot “see around th...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.1.1 Procedure
Figure 6.12.1.1-1: Sensing result subscription for enhance HD map 1. The Consumer (e.g., VAL server/client, VAE server/client) sends sensing result subscription request to the SEAL Sensing Server for device-centric sensing result. The request contains the context information, e.g. planned route of the vehicle. ...
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.1.2 Information Flows
Editor’s Note: The information flows of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.2 Architecture impacts
Editor’s Note: The architecture impacts of the solution is FFS.
3e26027ac593756f9c48ee9868ce45b2
23.700-15
6.12.3 Solution evaluation
Editor’s Note: The evaluation of the solution is FFS.