hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 deployment on satellite
0.1.0
2025-09
SA6#68
S6-253657
Key Issue on Satellite based AIML service maintenance while losing connection with terrestrial network
0.1.0
2025-09
SA6#68
S6-253660
Key Issue on Support satellite switch selection in data delivery
0.1.0
2025-09
SA6#68
S6-253722
New KI on efficient content delivery over satellite access
0.1.0
2025-09
SA6#68
S6-253732
Pseudo-CR KI on location service via satellite access
0.1.0
2025-09
SA6#68
S6-253755
New KI on improving service performance over satellite access utilizing AI capabilities
0.1.0
2025-10
SA6#69
S6-254605
New Solution on support of satellite related information utilizing AI analysis
0.2.0
2025-10
SA6#69
S6-254606
New Solution for support of QoS analysis for services over satellite access
0.2.0
2025-10
SA6#69
S6-254607
Pseudo-CR Solution for location service via satellite access
0.2.0
2025-11
SA6#70
S6-255134
Solution evaluation for Sol#1
0.3.0
2025-11
SA6#70
S6-255520
Solution evaluation for Sol#2
0.3.0
2025-11
SA6#70
S6-255521
KI#3 Solution: Enhance SEALDD to support satellite selection in data delivery
0.3.0
2025-11
SA6#70
S6-255522
KI#4 Solution: Application enablement layer enhancement for efficient content delivery over satellite access
0.3.0
|
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 the existing SEAL architecture specified in 3GPP TS 23.434 [2] to investigate how to support the potential enhanced application enablement services by utilizing Sensing results.
Furthermore, the study also provides recommendations for the normative work.
|
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[3] 3GPP TS 22.137, "Service requirements for Integrated Sensing and Communication; Stage 1".
[4] 3GPP TS 23.255, "Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows;".
[5] 3GPP TS 23.286, "Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows; "
[6] 3GPP TR 22.837: "Feasibility Study on Integrated Sensing and Communication (Release 19)".
[7] 3GPP TR 23.700-14: "Study on Integrated Sensing and Communication (Release 20)".
[8] 3GPP TS 23.437: "Service Enabler Architecture Layer for Verticals (SEAL); Spatial map and Spatial anchors".
|
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.
Sensing result
For the purposes of the present document, the terms given in 3GPP TS TS 23.255 [4] apply.
UAS Service Supplier (USS)
UAV
For the purposes of the present document, the terms given in 3GPP TS TS 23.286 [5] apply.
V2X service
|
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 Application Enabler
UAS Uncrewed Aerial System
UAV Uncrewed Aerial Vehicle
USS UAS Service Supplier
V2X Vehicle-to-Everything
VAE V2X Application Enabler
VAL Vertical Application Layer
|
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 a target object when specific requested conditions are met;
- Subject to operator’s policy and regulation, the 5G system shall be able to provide secure means for a trusted third-party to receive sensing results with contextual information;
- Subject to user’s consent, regulation and operator’s policy, the 5G network may provide secure means to expose to a trusted third-party the combined sensing result derived from the joint processing of the 3GPP sensing data and non-3GPP sensing data.
- Subject to operator’s policy, the 5G network may provide secure means for the operator to expose information towards trusted third-party on whether a given sensing service is available and the estimated quality of the given service for a certain geographic area and time.
A vertical application may provide the application enabler layer with specific information defining the conditions for the situation of interest. When such conditions are met, the application enabler layer shall be able to provide the vertical application with a report together with the relevant information.
The information required to define the situation of interest may include, but is not limited to, basic parameters such as a specific geographical area, state information, or conditions (e.g., speed, distance). Furthermore, depending on the requirements of the vertical application, more detailed and complex conditional information may be specified, such as indicators of a disaster in a specific area, tracking of the movement of a target UE over a defined time period together with environmental status information around the UE, or detection of unauthorized UE entry into a specific area, etc.
Thus, in 5G wireless sensing each vertical application may specify a single sensing service requirement (e.g. object detection) or a combination of multiple requirements (e.g. detect-and-avoid, no-transmit zone enforcement), and request them to the application enabler layer. Therefore, the application enabler layer shall be able to handle these application requirements, and shall dynamically provide the necessary capabilities to fulfil sensing requirements.
|
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 exposure mechanisms (e.g., subscription, notification, etc) defined in the SEAL architecture and functions are sufficient to meet vertical application requirements.
3. Whether and how to process the collected sensing results (e.g., sensing exposure from the core network), to generate application enabler layer enhanced sensing results, and to expose them to vertical applications.
4. Whether and how to resolve conflicts in sensing service requirements among different vertical applications or under resource limitations.
5. Whether new application enabler architecture is needed to support the above functions.
Note that applications-specific aspects (e.g., UAV, V2X, Metaverse, etc) will be covered in separate KIs.
4.2 Key issue #2: Enhance UAV service utilizing sensing results
|
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 support UAS which specified in 3GPP TS 23.255 [4] in which communications between UAVs, monitoring of UAV location deviation and reporting of UAV events have been studied. Especially for Detect And Avoid (DAA) service, which is to detect the potential collision between UAVs, is a key service of UAS to accomplish the safe and efficient UAV management. However, the DAA service depends on the PC5 communication, and the current situation is that the PC5 communication is not large-scale commercially used in UAV industry and even some UAVs are not equipped with 3GPP UE modules (e.g. USIM).
Furthermore, according to clause 7.8 of 3GPP TS 23.255 [4], an UAE service of tracking dynamic UAVs in an application defined area relative to a host UAV is specified. For this service, the UAE layer needs to provide the dynamic information (i.e. other UAVs’ location information) to the application layer and/or the host UAV. Currently, this service is performed by invoking location management service in SEAL layer. The location management service localizes an UAV only when the UE is equipped an UE module (e.g. USIM), and it is impossible to obtain the location information of an UAV without such UE module.
In addition, it is essential to manage UAV flight in No Drone Zone. This requires that once UAVs enter No Drone Zone, the intrusion can be detected, triggering notification immediately, e.g., sending warning to the UAV controller or UTM.
In fact, sensing results can be utilized to assist in detecting UAV, tracking UAV and avoiding the collision when there is any object during UAV trajectory or when UAV is entering a No Drone Zone, especially when the UAV is without the UE module. So, it would make sense to study how to utilize related sensing results to support the DAA, UAV trajectory tracking services, UAV flight management in No Drone Zone.
|
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 sensing results.
- How to enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results.
4.3 Key issue #3: Key issue on use of sensing results for spatial maps
4.3.1 Description
This KI aims to study how to use sensing results to manage object information in spatial maps. Objects in spatial maps can be stationary or mobile. As a result, tracking mobile objects within spatial maps can be more efficient with the use of sensing technology. A sensing service can be triggered to generate sensing results for an area of interest in a spatial map and the sensing results can be used to determine and identify objects within the spatial map. As an object moves, sensing results can be used to track the object and allow a spatial map server the ability to keep the spatial map current. The information obtained from sensing results for the spatial map can then be exposed to third-party consumers.
In Rel-19, the processed sensor data is stored at VAL layer (e.g., in database at VAL layer) and the SEAL SM server gets access to such database to create a spatial map via application specific way which is out of scope.
4.3.2 Open Issues
The key issue will study:
1. Whether and how the enabler layer can use sensing results for determining the presence of objects (e.g. humans, animals, and vehicles) within an area of interest in a spatial map.
2. Whether and how the enabler layer can associate a sensing result with an object within a spatial map.
3. Whether and how the enabler layer can localize objects and detect object movements within a spatial map from sensing results.
4. How the enabler layer can support SM server with creating SM.
NOTE: In Rel-20, exposure of sensing results (with or without the sensing contextual information) to support sensing services will be provided by 3GPP core network to enabler layer.
|
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 application layer, the VAE layer support providing the dynamic information (i.e. location information) required for HD maps management to the V2X application specific server. During this procedure, VAE needs to invoke location management service to get dynamic UEs list and further obtain their location. However, in current transportation system, there are many traditional vehicles which may be not equipped with UE module, or GNSS module, so it is difficult to localize their location by location management service provided by SEAL. Moreover, the environment information around vehicle (e.g., pedestrian/animal objects) also is important for safe operation, but there is no an efficient method to obtain those information.
According to the sensing service requirement specified in 3GPP TS 22.137 [3], the 5G system shall be able to provide sensing service to detect, and/or track one or more objects and the environment around the object(s). This service could be used to enhance HD map service to provide the location information of traditional vehicles and environment information around host vehicle to improve system safety.
Hence, it would make sense to study how to utilize sensing results for HD map in V2X.
|
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 objects, etc) with considering sensing results.
4.x Key issue #x: <Title>
4.x.1 Description
This clause provides a description of the key issue.
4.x.2 Open Issue
This clause provides the open issue(s) of the key issue.
|
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 requirements.
The following clauses specify generic functional model of SEAL Sensing Enabler for support application relevant sensing services.
|
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 grouped into SEAL Sensing Enabler server. The SEAL Sensing Enabler server consists of a common set of services and reference points. The SEAL Sensing Enabler server offers its services to the vertical application layer (VAL), VAE/UAE, and other SEAL servers.
NOTE: In this release, the SEAL sensing client is not used for sensing data collection.
Editor’s Note: Whether the SEAL sensing client is needed and the usage of it are FFS.
|
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 separate SEAL sensing server or directly by the specific SEAL/VAL enabler server. The decision on whether a separate SEAL sensing server is needed will be based on the evaluation of the solutions and FFS.
In this solution, after acquiring the sensing requirements from the sensing service consumer, a Sensing enabler server will send sensing request to a 5GC NF(e.g.,NEF). After it receives the sensing results from the 5GC NF, it determines whether the sensing requirements (e.g. the required accuracy of sensing result) are met, if not, it may further select other sensing service supplier(s) to acquire more sensing results, then it may generate enhanced sensing results based on the received sensing results from the 5GC NF and other sensing service supplier(s) and expose them to the sensing service consumer.
In this solution, the sensing service supplier which can provide sensing results can be another 5GC NF or vertical application server.
Editor's note: Whether the sensing service supplier can be 3rd party AF is FFS.
|
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 sensing consumer performs sensing service subscription procedure by sending sensing service subscription request and receiving sensing service subscription response. During the sensing service subscription procedure, the Sensing enabler server can acquire the sensing requirements of the VAL Server/Client such as Sensing Service Area of interest, Sensing target object type, Accuracy requirements, QoS requirements and so on.
2. Sensing enabler server sends sensing request to 5GC NF(e.g.,NEF) and receives sensing response.
Editor's note: The parameters in the sensing request and response are FFS and should be determined based on SA2’s progress.
3. Sensing enabler server receives sensing results from 5GC NF(e.g.,NEF) and determine whether the sensing requirements are met.
4. If the sensing requirements are met, skip to step 8, if not, the Sensing enabler server selects other Sensing Service Supplier(s) according to the sensing capability information of Sensing Service Supplier(s) and sensing requirement as received in step1 (e.g. by matching sensing capability information of Sensing Service Supplier to the sensing subscription parameters received from the sensing consumer).
5. The Sensing enabler server sends sensing request to each selected Sensing Service Supplier and receives sensing response. Different Sensing Service Supplier may be given different sensing request parameters.
Editor's note: The parameters in the sensing request and response are FFS.
6. Each Sensing Service Supplier sends sensing results to the Sensing enabler server based on the sensing request parameters respectively.
7. The Sensing enabler server further generate enhanced sensing results(e.g.,with higher accuracy) based on the received sensing results from the 5GC NF and other Sensing Service Supplier(s).
8. The Sensing enabler server sends the (enhanced) sensing results to the VAL Server/Client.
|
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 sensing results.
Figure 6.4.1-1: Procedure of exposure of sensing results
1. The VAL server sends a sensing service request to the Sensing Enabler server, including the service type (e.g., UAV detection, dynamic HD map, Vehicle tracking, etc.), service ID, sensing target object information (e.g., UAV ID, UE ID, Vehicle ID), sensing service requirements for the target object (e.g., the target area, sensing accuracy, sensing resolution, max sensing service latency, etc.), the reporting conditions (e.g., periodic reporting or event-triggered reporting), the time duration for the sensing, etc.
2. The Sensing Enabler server checks whether the VAL server is authorized to invoke such request, may be based on e.g. the pre-configurations or operator policies.
3. If the request is authorized, the SM server may invoke the sensing related service request to the 3GPP CN and obtain the sensing results from the 3GPP CN.
Editor’s note: The exposure of sensing results from 3GPP CN depends on SA2’s progress. What will be exposed to the consumers is FFS.
4. The Sensing Enabler server may interact with other SEAL enablers (e.g., SEALDD, ADAES) to get more sensing results (e.g., the transmission latency, sensing accuracy analysis) utilizing the obtained sensing results from the 3GPP CN, in case the 3GPP core network will not provide.
- The Sensing Enabler server may interact with ADAES to get the e.g., sensing accuracy analysis and the prediction analysis for the target object utilizing the obtained sensing results from the 3GPP CN;
- The Sensing Enabler server may interact with SEALDD to get the e.g., the transmission latency for the target object utilizing the obtained sensing results from the 3GPP CN.
Editor’s note: How the ADAES and SEALDD support the sensing related functionalities are FFS.
5. The Sensing Enabler may analyse and aggregate the sensing results obtained in step 3 and step 4 to generate the value-added sensing results (e.g. the statistic results in a location/time/direction/height granularity), and then expose to the VAL server if the results can fulfil the requested sensing service requirements.
6. The Sensing Enabler sends the value-added sensing results to the VAL server via sensing service response message, including all of target objects and the value-added sensing information.
|
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 related to UAVs to the AF (e.g., VAL server).
|
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
2. The VAL server sends a UAV detect request to the UAE to detect the UAVs in a certain area, including the service type (i.e., UAV detection, invalid UAV detection ), service ID, sensing service requirements for the detected UAVs (e.g., location accuracy, velocity, latency, sensing resolution, etc.), the target area, the reporting conditions (e.g., periodic reporting or event-triggered reporting), the reporting time intervals if the request is periodic, time duration, optional tracked object information (e.g., UAV ID, flight trajectory) if the object needs to be tracked, etc.
3. The UAE checks whether the VAL server is authorized to invoke such request based on e.g. the pre-configurations or the operator policies.
4. If the request is authorized, the UAE sends the UAV related sensing results request to the sensing enabler to ask for the UAV related sensing results.
4. The sensing enabler may invoke the sensing related service request to the 3GPP CN and obtain the sensing results from the 3GPP CN via NEF if the SM server is an untrusted AF or interact with the SF entity in 5GC directly as a trusted AF.
Editor’s note: The exposure of sensing results from 3GPP CN depends on SA2’s progress. What will be exposed to the consumers is FFS.
5. Upon received the exposure from network layer, the sensing enabler may determine the detected UAVs that entering the target area and then the sensing enabler may interact with LMS to track the detected UAVs and obtain the location trajectory (including the velocity, direction, altitude, etc.) for them in the requested time duration.
Editor’s note: How the LMS tracks the detected UAVs that without UE modules is FFS.
6. The sensing enabler aggregates and combines the sensing results obtained in step 4 and step 5 to determine all of UAVs entering the target area as well as their flight trajectories, and then the sensing enabler compares the detected UAV flight trajectory with requested flight trajectory included in Step 1 to identify if the UAVs entering the target area are invalid or not.
7. The sensing enabler notifies the UAE for the UAV related sensing results, including all UAVs entering the target area and the invalid UAVs that not allowed entering the target area.
8. The UAE sends the analysed sensing results to the VAL server via UAV detect response message, including all UAVs entering the target area and the invalid UAVs that not allowed entering the target area.
|
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 dynamic area for sensing
- Step 4: UAE server obtaining dynamic information from sensing results
- Step 5: UAE server notification of host UAV’s dynamic information to the UAS Application Specific Server and/or to the host UAV.
Note: Step 1 and Step 2 are same to the exisiting procedures defined in clause 7.8.2.1 in 3GPP TS 23.255 [4]. Step 5 is enhanced to inclucde UVA dynamic information obtained by sensing results based on the procedure in 7.8.2.4 in 3GPP TS 23.255 [4].
|
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 received an updated location of the host UAV as per procedure specified in 3GPP TS 23.434 [5].
Figure 6.6.2.2-1: Management of dynamic area for sensing
1. Dynamice area for sensing creation/update is triggered (e.g. notified of the UE location of host UAV or notified a location update) via the step 4 in clause 7.8.2.1 in 3GPP TS 23.255 [4] for the UAV ID of the host UAV.
2. UAE server 1 determines the dynamice area for sensing based on the location of host UAV and the proximity range defined by application by its implementation.
6.6.2.3 UAE server obtaining dynamic information from sensing results
Figure 6.6.2.3-1 describes the procedure of obtaining dynamice 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) operating in the dynamice area for sensing.
2. The UAE server 1 request and obtain sensing results from 5GC.
3. The UAE server 1 obtain dynamic information of UAVs by considering all sensing results from 5GC.
Editor Note: the detail of how to request and obtain sensing results from 5GC depends on SA2.
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 UAV dynamic information
1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UAS Application Specific Server and/or to the subscribed UAE client of the host UAV). The UAE server can aggregate the dynamic information obtained by sensing and other methods. The notification includes the aggregated information of all the objects in the application defined proximity range of the host UAV and the location of the host UAV.
2. The UAS Application Specific Server or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client.
Editor note: How to define objects in the notification message is FFS. It may be associated to an UAV identity or not.
|
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) operating in the dynamic area for sensing.
2. The UAE server 1 request and obtain sensing results from 5GC.
3. The UAE server 1 obtain dynamic information of UAVs by considering all sensing results from 5GC.
Editor's Note: the detail of how to request and obtain sensing results from 5GC depends on SA2.
|
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 UAV dynamic information
1. The UAE server 1 sends notification of host UAV dynamic information to the subscribed entity (i.e. UAS Application Specific Server and/or to the subscribed UAE client of the host UAV). The UAE server can aggregate the dynamic information obtained by sensing and other methods. The notification includes the aggregated information of all the objects in the application defined proximity range of the host UAV and the location of the host UAV.
2. The UAS Application Specific Server or the UAE client of the host UAV updates the host UAV dynamic information with the host UAV dynamic information received in step 1. The UAE client provides the host UAV dynamic information to the UAS Client.
Editor's note: How to define objects in the notification message is FFS. It may be associated to an UAV identity or not.
|
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 performed the UAS UE registration procedure.
Figure 6.7.2.1.1-1: DAA support management procedure
1. The UAS application specific server sends to the UAE server a DAA support management request. The request includes the UAV (UAE client) identifier and the DAA application policy. If the procedure is for LDGS assisted DAA, then the request may include a list of UAE client identifiers (LDGS IDs) and/or geographical area so UAE server may select the relevant UAE client(s). The DAA application policy includes parameters for the control of LDGS assisted DAA. DAA application policy could includes parameters for the control of sensing assisted DAA.
2. The UAE server shall send to the UAS application specific server a DAA support management response with a positive or negative acknowledgement of the request.
3. The UAE server shall timestamp and store the DAA application policy and execute the DAA configuration according to clause 7.7.2.1.2 and sensing based DAA support configuration procedure according to clause 6.7.2.1.2 if DAA application policy include parameter for the control of sensing assisted DAA.
4. After execution of DAA configuration, the UAE server shall send a DAA support management complete to the UAS application specific server.
|
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 management procedure according to clause 6.7.2.1.1.
Figure 6.7.2.1.2-1: Sensing based DAA support configuration procedure
1. The UAE server obtains and initiates tracking the UAV location from the location management server as speicified in 3GPP TS 23.434.
2. The UAE server determines the dynamic area for sensing based on the location of the UAV and the sensing based DAA application policy.
3. The UAE server sends request and obtain sensing results of the area determined in Step 2.
4. The UAE detects UAVs in approaching based on the obtained sensing results and sensing based DAA application policy.
Editor’s Note: how to request and obtain sensing results depends on SA2.
|
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 specific server with information about one or more UAVs in approaching as detected and the corresponding timestamp.
2. The UAS application specific server provides a sensing based DAA event information acknowledge to the UAE server.
Editor’s Note 1: UAE server how to consider sensing based detection result and other detection methods jointly to determine DAA event is FFS
Editor’s Note 2: The message name of sensing based DAA event information report depends on what information is used to trigger the report and it is FFS
6.8 Solution #7: Sensing Coverage Information Exposure for Supporting UAV Services
|
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 during the deployment phase. Given that sensing capabilities are critical for the safety of UAVs and automotive systems, comprehensive sensing coverage information is essential for these sectors to develop robust services and ensure operational safety. Currently, there is no mechanism for CSP to expose the sensing coverage information.
The following clauses specify sensing coverage information exposure for supporting UAV services.
|
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 (e.g., to collect sensing coverage information from sensing entities).
3. The SEAL Sensing Server responds to the VAL server for the check sensing coverage information request.
Editor’s Note: Whether the SEAL sensing server gets initial sensing coverage information from CN between 3 and 4, will be decided based on the stable conclusion of SA2.
4. The SEAL Sensing Server interacts with the 3rd party sensing server(s) to collect the sensing coverage information of the 3rd party sensing data.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
5. The SEAL Sensing Server aggregates the sensing coverage information from different sensing entities received in step 4.
6. The SEAL Sensing Server sends check sensing coverage information response to the VAL server with the aggregated sensing coverage information.
Editor’s Note: Further changes to this procedure are FFS.
|
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) for collection of sensing data.
3. The SEAL Sensing Server responds to the SM server for the sensing result request.
4. The SEAL Sensing Server interacts with the NEF to collect the sensing result measured by the 3GPP network. The SEAL Sensing Server determines whether the sensing result fulfils the request from the consumer provided in step 1, and determines whether additional sensing data is needed to enhance the sensing result.
5. The SEAL Sensing Server interacts with the 3rd party sensing server to collect third party sensing data measured.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
6. The SEAL Sensing Server consolidates the sensing data/results from different sources in steps 4-5 to generate sensing result (e.g. draft spatial map).
7. The SEAL Sensing Server sends sensing result response to the SM server with the consolidated sensing results.
8. The Spatial Map Server creates spatial map based on the consolidated sensing result.
|
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 interacts with Spatial Map server via a new SEAL-X interference.
The functional model for the SEAL Sensing server is based on the generic functional model specified in clause 6 of 3GPP TS 23.434 [4] and the generic architecture of sensing service concluded in this study. The functional model enhanced to Spatial map for this solution is illustrated in Figure 6.10.1-1.
Figure 6.10.1-1: On-network spatial map functional model for use of sensing
NOTE: In this solution, SEAL SM client/server in the architecture and procedures refer to SEAL Spatial Map client/server specified in 3GPP TS 23.437 [8].
This solution contains two basic procedures:
1. Create spatial map with sensing capabilities.
2. Spatial map subscription and notification with sensing capabilities.
|
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:
1. The VAL Server or SEAL SM client is authorized to use APIs provided by the SEAL SM server.
2. The SEAL SM server can interact with SEAL Sensing server via SEAL-X interface.
3. The SEAL Sensing server is authorized to use Sense ing related capability APIs provided by sensing related function in the 3GPP core network or authorized to use the NEF exposed Sense ing related capability.
NOTE: In this solution, it is assumed that neither the VAL Server nor the SEAL SM Server has sufficient knowledge to understand the detailed use of sensing-related capabilities/parameters provided by the 3GPP core network, whether directly or via the NEF. Alternatively, If the VAL Server/SEAL SM Server knows that sensing service can be provided by SEAL sensing server, the VAL Server/SEAL SM Server may include a sensing indicator in the request. If so, the SEAL SM server will use the sensing indicator to decide whether to utilize sensing capabilities.
.
Figure 6.10.2.1-1: Create spatial map procedure
1. The requester (e.g., VAL server or SEAL SM client) sends a Create Spatial Map Request message to the SEAL SM server to create a spatial map. The request includes the same IEs as specified in clause 9.3.1.3.1 of 3GPP TS 23.437 [8].
2. The SEAL SM server decides to utilize sensing capabilities to assist the creation of the spatial map based on local policy. If SEAL SM server decides to utilize sensing capabilities, it sends a Get Sensing Results Request to SEAL Sensing server. The request includes requester ID, security credentials and three-dimensional area of interest.
Editor’s note: the detailed IEs included in the Get Sensing Result Request is FFS.
3. The SEAL Sensing server sends a Sensing Service Request either directly to a sensing-related function in the 3GPP core network or to this function via the NEF (e.g., using the Nnef_Sensing_Subscribe service operation). The request includes the Target Sensing Area information. This information is derived from a three-dimensional area of interest and can be handled by 3GPP core network.
Editor’s note: the Sensing Service Request may be used to trigger the sensing service provided by 3GPP core network, or used to request the sensing result. How the SEAL sensing server utilizes the sensing service will be based on SA2 progress and is FFS.
4. The sensing-related function in the 3GPP core network sends the Sensing Service Response either directly to the SEAL Sensing server or via the NEF. The response includes the sensing result (with or without the sensing contextual information).
Editor’s note: the detailed IEs included in the step 3 and step 4 are based on the output of SA2 and are FFS.
5. The SEAL Sensing server sends the Get Sensing Result Response to the SEAL SM server. The response includes the List of objects information in the Area of interest obtained from the sensing service.
6. The SEAL SM server creates the spatial map as per step 2 in clause 9.3.1.2 of 3GPP TS 23.437 [8]. In this step, the processed sensor data may be sourced from step 5 instead of the VAL layer.
7. The SEAL SM server sends response message to the requester as per step 3 in clause 9.3.1.2 of 3GPP TS 23.437 [8].
8. If the response in step 7 indicates "in-progress", the SEAL SM server notifies the requester with the spatial map ready notification message as per step 4 in clause 9.3.1.2 of 3GPP TS 23.437 [8].
|
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:
1. The VAL Server or SEAL SM client is authorized to use APIs provided by the SEAL SM server.
2. The SEAL SM server can interact with SEAL Sensing server via SEAL-Xsensing interface.
3. The SEAL Sensing server is authorized to use Sense ing related capability APIs provided by sensing related function in the 3GPP core network or authorized to use the NEF exposed Sense ing related capability.
Figure 6.10.2.2-1: Create spatial map with periodic update notification procedure
The following step 1 to step 8 are Spatial map subscription procedure.
1. The VAL server (or SEAL SM client) sends a Subscribe Spatial Map Event Request to the SEAL SM server to subscribe spatial map event.. The request includes the same IEs as specified in clause 9.3.6.2.1 of 3GPP TS 23.437 [8].
2. The SEAL SM server processes the Subscribe Spatial Map Event Request as per step 2 in clause 9.3.6.2.1 of 3GPP TS 23.437 [8]. If the "Change of objects event" is subscribed by requester (VAL server or SEAL SM client), the SEAL SM server may subscribe the Sensing Results from SEAL Sensing server.
3. The SEAL SM server sends a Get Sensing Results Subscription Request to SEAL Sensing server. The request includes requester ID, security credentials, and may include one or more IEs in the Target spatial map(s) and/or List of events.
Editor’s note 1: the detailed IEs included in the Get Sensing Result Request is FFS.
4. The SEAL Sensing server processes the Sensing subscription for this Get Sensing Results Subscription Request.
5. The SEAL Sensing server sends a Sensing Service Request either directly to a sensing-related function in the 3GPP core network or to this function via the NEF (e.g. Nnef_Sensing_Subscribe service). The request may includes:
a. the Target Sensing Area information. This information is derived from the Target spatial map(s) (e.g. Area of interest) and can be handled by 3GPP core network.
b. If periodic or event triggered sensing result notification is supported by the 3GPP core network, the SEAL Sensing server may also utilize them based on the Notification intervals included in the List of events.
c. If Detection or Tracking specific object is supported by the 3GPP core network, the SEAL Sensing server may also translates the information included in the specified objects IE in the List of events to a list of IDs that can be handled by the 3GPP core network and includes them in this Sensing Service Request.
Editor’s note 2: the Sensing Service Request may be used to trigger the sensing service provided by 3GPP core network, or used to request the sensing result. How the SEAL sensing server utilizes the sensing service will be based on SA2 progress and is FFS.
6. The sensing-related function in the 3GPP core network sends the Sensing Service Response either directly to the SEAL Sensing server or via the NEF.The response indicates the result of Sensing Service subscription.
Editor’s note 3: the detailed IEs included in the step 5 and step 6 are based on the output of SA2 and are FFS.
7. The SEAL Sensing server sends a Get Sensing Results Subscription response to the SEAL SM server to indicate the result of Sensing Results Subscription.
8. The SEAL SM server sends a Subscribe Spatial Map Event Response to the VAL server (or SEAL SM client) as per step 3 in clause 9.3.6.2.1 of 3GPP TS 23.437 [8].
The following step 9 to step 12 are Spatial map notification procedure.
9. The SEAL Sensing server detects a sensing event that requires the use of sensing capabilities, e.g. a specific time, then the SEAL Sensing server interacts with 3GPP core network to get the sensing result. The interaction may be also based on the information included in the Get Sensing Results Subscription Request, e.g. if periodic notification is required, the 3GPP core network may notify the sensing result to the SEAL Sensing server periodically.
10. The SEAL Sensing server sends a Sensing Event Notification to the SEAL SM server. This notification includes the information obtained from step 9.
11. The SEAL SM server sends a Spatial Map Event Notification to the requester as per step 2 in clause 9.3.6.2.2 of 3GPP TS 23.437 [8].
|
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 [8].
The enhancements enable a VAL server or SM client to specify a sensing service policy when requesting to create or update a spatial map. The SM server uses the information in the sensing service policy to send requests to a sensing service to obtain objects for the area of interest. Within the sensing service policy, there are sensing configuration parameters the SM server can use for sending the requests to the sensing service. An Object label classification policy is provided to enable the SM server to label sensing results received from the sensing service with object IDs.
|
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 space of area of interest, objects).
Figure 9.3.1.2-1: Create spatial map procedure
1) The requestor (e.g., VAL server or SEAL SM client) sends a request message to the SEAL SM server to create a spatial map. The request includes requestor ID, security credentials, three-dimensional area of interest, information to be included in the spatial map such as allowed entities list defining which entities are permitted to discover and access the spatial map. The request may include spatial map layering information parameters and may also include augmented layer information that can be requested with the spatial map. The request may include a required media format for the spatial map. A sensing service policy may be provided to configure the SM server to use a sensing service to obtain object information for the spatial map.
NOTE: SEAL SM server can obtain augmented layer information and can provide the obtained augmented layer information to the requestor in the response message.
2) The SEAL SM server authorizes the requestor, and validates the request. The SEAL SM server produces a requested spatial map using layering information and processed sensor data, according to the requested spatial map media format. The SEAL SM server does not create a spatial map if the requested spatial map media format is not supported and can create a spatial map based on local configuration if no spatial map media format is included in the request.
a) If the augmented layer information indicates to include VAL UE information, the SEAL SM server fetches the list of VAL UEs in the area of interest from LM server using clause 9.3.10 of 3GPP TS 23.434 [4] and/or from NEF as specified in 3GPP TS 23.502 [5].
b) If the augmented layer information indicates to include spatial anchors information within area of interest, the SEAL SM server fetches the list of spatial anchors in the area of interest as specified in clause 8.3.4.
c) If a sensing service policy is provided, the SM server triggers a sensing service to obtain object information using information in the sensing service policy.
NOTE: Processed sensor data is stored at the VAL layer (e.g., in database at VAL layer) or within the SM server (e.g., when sensing service policy is provided). When processed sensor data is stored at the VAL layer, the SEAL SM server gets access to such database to create a spatial map via application specific way which is out of scope. When processed sensor data is stored within the SM server, the SM server will use the sensing service policy to configure and manage sensing service(s) to obtain object information for the spatial map. ML models are used to derive object information from sensing results and the object information is saved within the SM server.
Editor’s Note: The procedure of triggering of sensing service by the SM server is FFS.
3) The SEAL SM server sends response message to the requestor with a indication of success, in-progress or fail. If the requested spatial map has been created sussesfully, the response message includes assigned spatial map ID and information which includes three-dimensional space defined by the spatial map and can include a list of spatial map layers with their corresponding layer ID, objects belong to the layer, etc.. If the response indicates "in-progress", an assigned spatial map ID is included in the message. Further, if the response indicates "in-progress" and the requestor has not provided a notification target address, then the requestor subscribes for spatial map event to receive notification when the spatial map is created. Otherwise, the response includes an indication of failure and may include a reason for the failure and indication of supported spatial map media formats if the failure is related to an unsupported spatial map media format.
4) If the response indicates "in-progress", the SM server detects when the SEAL SM server has sufficient information to map all the objects related to area of interest and the spatial map is ready to provide service (e.g. employed for localization). If the requestor has provided a notification target address in the request or has subscribed for spatial map events, the SEAL SM server notifies the requestor with the spatial map ready notification message. The notification includes parameters as specifed in Table 9.3.6.3.3-1.
|
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)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Area of interest
M
Three-dimensional area information to produce the spatial map
Notification Target Address
O
Notification target address (e.g. URL, URI, IP) where the notifications should be sent.
Spatial map media format
O
The media format requested for the spatial map.
Information to include
O
Information to be included in the spatial map
> Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover and access the spatial map
> List of spatial map layers
O
List of spatial map layer information. Each element includes the information described below.
>> Spatial map layer information
O
Information to specify the corresponding spatial map layer specific information
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_USERS;
- SPATIAL_ANCHORS.
Sensing service policy
O
A policy to provide configuration parameters for the SM server to trigger sensing service to obtain object information for the spatial map. The contents of the policy is described in Table 9.3.1.3.1-y.
NOTE 1: For the current release, the spatial map layer information is implementation specific and out of scope.
Table 9.3.1.3.1-y: Sensing service policy
Information element
Status
Description
Sensing service policy ID
M
The identifier of the sensing service policy.
Sensing service provider IDs
O
The identifier of the sensing service providers the SM server should use to trigger sensing service.
Sensing area
O
Three-dimensional area information of the sensing area.
Sensing resolution
O
A resolution to provide to the sensing service.
Sensing schedule
O
A schedule to trigger sensing service.
Sensing refresh interval
O
An interval to refresh SM object information provided by a sensing service.
Sensing output requirements
M
A listing of object characteristics required from the sensing service. Object characteristics describes the size, shape, orientation, speed, and absolute and relative location of an object obtained from sensing service.
Object label classification policy
O
A policy to assist with the labeling of sensing results obtained from the sensing service. The policy provides e.g. a list of ML models that derives object information from sensing results received by the SM server.
NOTE 2: Sensing service policy values are within the range defined in Table 9.3.1.3.1-1.
Editor's Note: Whether the Object label classification policy IE is included in the sensing service policy is FFS.
|
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 message to the SEAL SM server to update a spatial map. The request includes requestor ID, security credentials, spatial map ID, information on what to update such as updated spatial map layering information and updated spatial map coverage area. As a part of update, the request may include augmented layer information (e.g., VAL users, spatial anchors). The request may include a list of UE-object association information for the SEAL SM server to identify associations between UEs and objects in a spatial map. A sensing service policy may be provided to configure the SM server to use a sensing service to obtain object information for the spatial map.
2) The SEAL SM server authorizes the requestor and validates the request. The SEAL SM server updates the spatial map as requested. If a sensing service policy is provided, the SM server triggers a sensing service to obtain object information with the information in the sensing service policy.
Editor’s Note: The procedure of triggering of sensing service by the SM server is FFS.
3) The SEAL SM server sends response message to the requestor with result of the request and updated spatial map information with the spatial map ID. SEAL SM server may include the requested augmented layer information in the response message.
|
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 UE)
Security credentials
M
The security credentials of the requestor.
Application service ID
M
ID of the requesting VAL application service
Spatial map ID
M
ID of the spatial map to update
Spatial map update information
M
The spatial map Information to update as described in described in Table 7.3.3.1-1. Only IEs which need to be updated are included.
> Augmented layer information
O
List of required augmented layer information. This IE can contain multiple values. Possible values are:
- VAL_UE;
- SPATIAL_ANCHORS.
List of UE-object association information
O
List of UE-object association information to identify associations between UEs and objects in a spatial map as described in Table 7.3.3.x-1.
Sensing service policy
O
A policy to provide configuration parameters for the SM server to trigger sensing service to obtain object information for the spatial map. The contents of the policy is described in Table 9.3.1.3.1-y.
NOTE: At least one of the information elements shall be provided.
6.12 Solution #11: Use Sensing Results to Enhance HD Map for V2X Services
|
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 the corner”. An sensing system can complement onboard sensory data with more “global” data that cannot be obtained by sensors mounted on the vehicle. Another automotive-related example is the detection of pedestrians or animals on highways.
Application enablement layer can aggregate the sensing demands of a large number of vehicles, enabling unified subscription to sensing data from different sensing entities. By tracking or predicting vehicle locations in real time, this layer transforms the geographically scoped sensing data into a vehicle-centric dynamic view, and simplifies the vehicle's data consumption process and significantly enhances processing efficiency and system responsiveness.
The following clauses specify use sensing results to enhance HD map for supporting V2X services.
|
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.
2. The SEAL Sensing Server authenticates the request, checks the stored sensing data, and determines the next actions (e.g., to collect sensing data from sensing entities, to collect device location information/analytics, to generate device-centric sensing result).
3. The SEAL Sensing Server responds to the VAL server for the sensing result subscription request.
4. The SEAL Sensing Server interacts with the 5GC NF (e.g. NEF) for receiving notifications with the sensing data from the 3GPP network. The SEAL sensing server determines whether the sensing result fulfils the request from the consumer provided in step 1, and determines whether additional sensing data is needed to enhance the sensing result.
5. The SAE Server interacts with the 3rd party sensing server for receiving the sensing data from the 3rd party sensing data.
Editor’s Note: Whether the revision of the architecture is needed for the 3rd party sensing server is FFS.
6. After receiving the sensing data from the sensing entities in steps 4-5, the SEAL Sensing Server interacts with the other SEAL servers for collection of location information/analytics (e.g., LMS for device location information, ADAES for device location analytics).
7. The SEAL Sensing Server filters the sensing data and location information/analytics, to generate device-centric sensing results.
8. The SEAL Sensing Server sends sensing result subscription notifications the Consumer with the generated device-centric sensing results.
9. The Consumer may use the sensing result for e.g., create/update HD map.
|
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.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 7 Deployment scenarios
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 7.1 General
| This clause will provide a general description of the deployment scenarios.
7.x Deployment model #x: <Title>
Provide a description of the deployment scenarios.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 8 Business Relationships
| Provide a description of the involved business relationships.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 9 Overall evaluation
| This clause will provide evaluation of different solutions.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10 Conclusions
| |
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10.1 General conclusions
| This clause will provide general conclusions for the study.
|
3e26027ac593756f9c48ee9868ce45b2 | 23.700-15 | 10.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
Annex A (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-08
SA6#68
S6-253520
Skeleton
0.0.0
2025-09
SA6#68
Implemented the following pCRs, S6-253521,S6-253522,S6-253723,S6-253759,S6-253760,S6-253776
0.1.0
2025-10
SA6#69
Implemented the following pCRs,S6-254617, S6-254779, S6-254736, S6-254623, S6-254737, S6-254679, S6-254756, S6-254681, S6-254682, S6-254790, S6-254781, S6-254739, S6-254686
0.2.0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.