hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.6.3 Solution evaluation
| This solution addresses Key Issue #2 on how to enhance the UAS application enabler to support enhanced trajectory tracking for UAVs utilizing the sensing results. This solution proposes to enhance UAE server to sensing based tracking dynamic UAVs. The UAE server needs to determine a dynamic area for sensing based on th... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.7 Solution #6: Sensing based DAA service
| |
1d6307f47bb31085dee07c7a4bafe57f | 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].
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.7.2 Procedures
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.7.2.1 Configuration of sensing based DAA policies to the UAE layer
| |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.7.3 Solution evaluation
| This solution addresses Key Issue #2 on how to enhance the UAS application enabler to support enhanced DAA service/functionalities for UAVs utilizing the sensing results. This solution proposes to enhance UAE to support sensing based DAA service by enhance the procedure described in clause 7.7 in 3GPP TS 23.255 [4].
T... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.1.1 Procedure
|
Figure 6.8.1.1-1: Sensing coverage information exposure
1. The Consumer (e.g.VAL Server, SEAL Server, UAE Server) sends check sensing coverage subscription request to the SEAL Sensing Server.
2. The SEAL Sensing Server authenticates the request, checks the stored sensing coverage information, and determines the nex... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.1.2 Information Flows
| 6.8.1.2.1 Check Sensing Coverage Subscription request
Table 6.8.1.2.1-1 describes the check sensing coverage subscription request.
Table 6.8.1.2.1-1: Check Sensing Coverage Subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
VAL service ID
O
Th... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.1.2.2 Check Sensing Coverage Subscription response
| Table 6.8.1.2.2-1 describes the check sensing coverage subscription response.
Table 6.8.1.2.2-1: Check Sensing Coverage Subscription response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for the ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.1.2.3 Check Sensing Coverage notify
| Table 6.8.1.2.3-1 describes the check sensing coverage notify.
Table 6.8.1.2.3-1: Check Sensing Coverage notify
Information element
Status
Description
Check subscription identifier
M
The identifier for the check request.
Sensing coverage information
M
The aggregated sensing coverage information, e.g., full co... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.2 Architecture impacts
| This solution has no architecture impact.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.8.3 Solution evaluation
| This solution addresses the KI#2 on utilizing sensing result to support UAV applications. In this solution, SEAL sensing server enables the consumer to get aggregated sensing coverage information, which is generated at the SEAL server based on collected sensing coverage information. The aggregated sensing coverage info... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1.1 Procedure
| Pre-conditions:
1. The Spatial Map Server is triggered to send the sensing result request due to a spatial map create or update procedure as described in clause 6.11.
Figure 6.9.1.1-1: Sensing results for creating spatial map
1. The Spatial Map Server sends sensing result subscribe request for consolidated sensi... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1.2 Information Flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1.2.1 Sensing result Subscribe request
| Table 6.9.1.2.1-1 describes the information elements from SEAL SM server to SEAL Sensing server to subscribe sensing results to create spatial map.
Table 6.9.1.2.1-1: Sensing result Subscribe request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VA... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1.2.2 Sensing Result Subscribe response
| Table 6.9.1.2.2-1 describes the sensing result Subscribe response.
Table 6.9.1.2.2-1: Sensing Result Subscribe response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for the subscription.
Failure... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.1.2.3 Sensing Result notification
| Table 6.9.1.2.3-1 describes the sensing result notification.
Table 6.9.1.2.3-1: Sensing Result notification
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Sensing result information
M
Indicates the sensing result information for the requested sensing are... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.9.2 Solution evaluation
| The solution introduces SEAL Sensing server. The solution enables the SEAL SM server to use the SEAL Sensing server capabilities to request the sensing results to help SM server build its spatial map. It also consolidates sensing results from 3rd party sensing server to generate sensing results. The solution uses SEAL-... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.10 Solution #9: high level architecture and procedures for use of sensing results for spatial map
| |
1d6307f47bb31085dee07c7a4bafe57f | 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 in... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.10.2 Procedures
| |
1d6307f47bb31085dee07c7a4bafe57f | 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:
... |
1d6307f47bb31085dee07c7a4bafe57f | 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:... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.10.3 Solution evaluation
| This solution utilizes sensing results to enhance the spatial maps service specified in 3GPP TS 23.437 [8].
Compared to Rel-19, the SEAL SM Server in this solution can now obtain not only processed sensor data stored at the VAL layer but also sensing results from 3GPP core network.
In this solution, neither the VAL ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.11 Solution #10: Sensing results for spatial maps
| |
1d6307f47bb31085dee07c7a4bafe57f | 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 [... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.11.2 Procedures
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
NOTE: The VAL server discovers the SEAL sensing server based on the CAPIF framework.
|
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.3.1.3 Information flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 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)... |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.3.4 Update spatial map
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.3.4.3 Information flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9.3.4.3.1 Update spatial map request
| Table 9.3.4.3.1-1 describes 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.11.3 Solution evaluation
| 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 sensing results to objects in a spatial map, respectively. The solution proposes to enhance spatial map create and update procedures described in 3GPP TS 23.437... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 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. T... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.1.2 Information Flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.1.2.1 Sensing Result Subscription request
| Table 6.12.1.2.1-1 describes the sensing result subscription request.
Table 6.12.1.2.1-1: Sensing Result Subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor.
VAL service ID
O
The identifier of the VAL service.
Target sensing area
M
Indicates th... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.1.2.2 Sensing Result Subscription response
| Table 6.12.1.2.2-1 describes the sensing result subscription response.
Table 6.12.1.2.2-1: Sensing Result Subscription response
Information element
Status
Description
Successful response
O
(NOTE)
The indication that the request was successful.
> Subscription identifier
M
The identifier for the subscription.
... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.1.2.3 Sensing Result Subscription notification
| Table 6.12.1.2.3-1 describes the sensing result subscription notification.
Table 6.12.1.2.3-1: Sensing Result Subscription notification
Information element
Status
Description
Subscription identifier
M
The identifier for the subscription.
Sensing results
M
The aggregated sensing result, e.g., device-centric se... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.2 Architecture impacts
| This solution has no architecture impact.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.12.3 Solution evaluation
| This solution addresses the KI#4 on collect and filter sensing data/result to generate device-centric sensing result, which can be used by the consumer to enhance HD map for V2X services. In this solution, SEAL sensing server collects sensing data/results, and filters the collected sensing data and location information... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.13 Solution #12: Sensing-based event trigger monitoring procedure
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.13.1 Solution Description
| This solution addresses KI#1 and proposes a new procedure to support enhanced sensing-based event trigger monitoring.
For certain vertical applications such as smart home, smart factory, and disaster and safety services, the VAL server may require continuous event-trigger monitoring according to predefined triggering ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.13.2 Procedures
| Figure 6.13.2-1: Sensing-based event trigger monitoring procedure
1. The VAL server sends a monitoring subscription request to the SEAL Sensing Enabler server to subscribe for event trigger monitoring. The request may specify sensing requirements of the VAL server including sensing service type (e.g., presence, objec... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 10 When the VAL server decides to stop the sensing-based monitoring service, it sends an unsubscribe request to the Sensing Enabler server.
| 11. The Sensing Enabler server sends a Sensing unsubscribe request to 3GPP CN to stop the sensing service in the network.
12. 3GPP CN sends a Sensing unsubscribe response to the Sensing Enabler server.
13. The Sensing Enabler server removes the subscription information.
14. The Sensing Enabler server sends an unsubs... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.13.4 Solution evaluation
| This solution enables Sensing Enabler server to support monitoring for sensing-based event triggering. Upon receiving sensing service requirements from the VAL server, the Sensing Enabler server performs a monitoring process. The Sensing Enabler server can adjust the monitoring process based on the sensing service requ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.1.1 General
| The following clauses specify SEAL Sensing Server service on support processing sensing requests from different consumers to remove conflict in the request, and reuse of sensing result to save resource for sensing result collection.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.1.2 Procedure
| Pre-condition:
- The requests from different consumers are received at the SEAL sensing server in the same time period, so that the SEAL sensing server can process these requests.
Figure 6.14.1.2-1: Procedure on support sensing requests process and sensing result reuse
1. Multiple consumers (e.g. VAL server, SE... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.1.3 Information Flows
| No information flows are introduced in this solution.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.2 Architecture impacts
| SEAL sensing server is needed in this solution for removing conflict in the requests from different consumers.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.14.3 Solution evaluation
| This solution addresses the 4th open issue of KI#1 on “Whether and how to resolve conflicts in sensing service requirements among different vertical applications or under resource limitations.”
In this solution, SEAL sensing server processes the requests from different consumers to remove conflict, e.g. merge requests... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.15 Solution #14: Sensing UAVs combining location and sensing results
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.15.1 Solution description
| This solution addresses the KI#2.
In this solution, it is proposed a mechanism where a UAV with a UE module (UAV ID) can be identified as a Sensed object. Once the matching between a sensed object and the UAV ID is done, the sensing results can be used to assist in continuing tracking the UAV ID when network location... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.15.1.1 Procedure for sensing UAVs with a UE module
| Figure 6.15.1.1-1 illustrates the high-level procedure for sensing UAVs with a UE module.
Pre-condition:
- The UAV ID is registered and connected in the CN.
Figure 6.15.1.1-1: Procedure for sensing UAV ID
1. The Sensing Enabler client (e.g. VAL server, or the UAV server) sends a Sensing request to the Sensing ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.15.2 Architecture Impacts
| This solution proposes a new sensing enabler to support the sensing of UAV ID. The new architecture for the sensing enabler is described in the solution for KI#1.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.15.3 Solution evaluation
| The solution enables the VAL server to track the UAV using sensing, including in scenarios where network location is not available. It introduces SEAL Sensing server to get sensing results to detect the object and correlates these results with the UAV’s network‑based location information to determine the UAV for tracki... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.1 General
| The following clauses specify SEAL Sensing Server service on presence detect of UAV in No Drone Zone and notify.
Pre-condition:
- The UAE server has the No Drone Zone (no UAV flight zone) list of geographical areas.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.2 Procedure
|
Figure 6.16.1.1-1: Presence detect in No Drone Zone and notify
1. The UAE Server sends presence detect in No Drone Zone subscription request to the SEAL Sensing Server. The request contains the planned flight path of the UAV, and no Drone Zone information. The actual trajectory of the flight may change compared wit... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.3 Information Flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.3.1 Presence detect in No Drone Zone subscription request
| Table 6.16.1.3.1-1 describes the information elements from UAE server to SEAL Sensing server for Presence detect in No Drone Zone subscription request.
Table 6.16.1.3.1-1 Presence detect in No Drone Zone subscription request
Information element
Status
Description
Requestor identity
M
The identity of the requesto... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.3.2 Presence detect in No Drone Zone subscription response
| Table 6.16.1.3.2-1 describes the information elements from SEAL Sensing server to UAE server for Presence detect in No Drone Zone subscription response.
Table 6.16.1.3.2-1 Presence detect in No Drone Zone subscription response
Information element
Status
Description
Successful response
O
(NOTE)
The indication th... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.1.3.3 Presence detect in No Drone Zone notification
| Table 6.16.1.3.3-1 describes the information elements from SEAL Sensing server to UAE Server for Presence detect in No Drone Zone notification.
Table 6.16.1.3.3-1 Presence detect in No Drone Zone notification
Information element
Status
Description
Subscription identifier
M
Indicates the identity of the subscrip... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.16.2 Solution evaluation
| The solution addresses the 3rd open issue in KI#2 on “enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results”. The solution introduces SEAL Sensing server to get sensing results. It enables UAE server to request the presence detection of UAVs in a No Dro... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.17.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.17.1.1 General
| Currently, there are two means to for UAE server to track a drone through LM server:
- The drone may periodically report its location (e.g. GPS location) to LM server.
- LM server uses network location service to get the locations of the drone.
However, the drone may be hacked or malfunctioning so that it stops repo... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.17.1.2 Procedure
| Pre-condition:
- UAE Server requests to LM Server for UAV location reporting.
- The LM Server requests the LM Client (deployed on a UAV) to report location.
- The 5GCN provides the sensed objects.
Figure 6.17.1.2-1: Converged trajectory tracking
0. The LM Client (deployed on a UAV) reports the UAV location to ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.17.1.3 Information Flows
| 6.17.1.3.1 sensing request
Table 6.17.1.3.1-1 describes the information elements from UAE server to SEAL Sensing server for sensing request.
Table 6.17.1.3.1-1: sensing request
Information element
Status
Description
Requestor identity
M
The identity of the requestor (e.g., VAL server or VAL User or VAL UE)
UAV... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.17.2 Solution evaluation
| This solution introduces SEAL Sensing server to get sensing results. In this solution, the UAE Server sends a sensing request to the SEAL Sensing Server to correlate the object and UAV ID, which enables the UAE server to request location and sensing information via object and UAV ID. This solution enables the UAE Serve... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18 Solution #17: Sensing enabler service procedure for spatial map object detection and tracking
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1 Solution description
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.0 General
| The Spatial Map server can request sensing enabler services for sensing results, object detection, movement tracking to detect object changes, mobility prediction, estimated duration of staying in-range, etc.
The following clause specifies procedures for sensing enabler services that detect objects, track target spat... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.1 Procedure
| Pre-conditions:
1. SEAL Sensing Enabler server has acquired information of Application Specific Layer server(s).
2. SEAL Sensing Enabler server can identify the object from sensing results and associate it with a target object, utilizing sensing results from 5GC NF and spatial map information in Sensing enabler servi... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.2 Information Flows
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.2.1 Sensing enabler service subscribe request
| Table 6.18.1.2.1-1 shows the Sensing enabler service subscribe request sent by SEAL SM server to SEAL Sensing Enabler server to subscribe to sensing enabler service.
Table 6.18.1.2.1-1: Sensing enabler service subscribe request
Information element
Status
Description
Requestor identifier
M
The identifier of the r... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.2.2 Sensing enabler service subscribe response
| Table 6.18.1.2.2-1 shows the Sensing enabler service subscribe response sent by SEAL Sensing Enabler server to SEAL SM server as the response to sensing enabler service subscribe request.
Table 6.18.1.2.2-1: Sensing enabler service subscribe response
Information element
Status
Description
Result
M
Result (i.e., ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.1.2.3 Sensing enabler service notification
| Table 6.18.1.2.3-1: Sensing enabler service notification
Information element
Status
Description
Subscription ID
M
Sensing enabler service subscription identifier
Notification information
M
Specifies requested sensing service result. The objects in the notification information may include either all objects det... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.2 Architecture impacts
| This solution proposes a procedure and information flow for providing the sensing related services required by the SM server.
Functional architecture enhancement for the SEAL sensing enabler in clause 6.2 is used for this solution. Proposed procedure and information flow for the sensing enabler services may be adapted... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.18.3 Solution evaluation
| This solution enables SM servers to subscribe sensing enabler services for spatial map object detection and tracking within a spatial map based on sensing results.
The current 3GPP TS 23.437 [8] does not address how the spatial map server can detect object changes and obtain required sensing information from 5GS.
The... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.19.1 Solution description
| This solution intends to solve the third open issue of Key Issue #2, i.e. how to enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.19.2 Procedures
| Pre-conditions:
1. UAE server has established a UAE session with respective UAE clients as the UAE clients are successfully registered to the UAE server.
2. The location of UAV is known to UAE server by UAE client periodic reporting or using LMS services.
1. UAS application sends No Drone Zone avoidance service to... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.19.3 Solution evaluation
| This solution addresses Key Issue #2 on how to enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results and location information of the UAVs. This solution proposes to enhance UAE server to support sensing based No Drone Zone avoidance service.
The enhan... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 7 Deployment scenarios
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 8 Business Relationships
| When specific services, e.g., UAS in 3GPP TS 23.255 [4], V2X in 3GPP TS 23.286 [5], SEAL Spatial Map in 3GPP TS 23.437 [8] utilize sensing capabilities from the 3GPP Core Network, either directly from the SF or via the NEF, their respective business relationships apply.
The business Relationships as specified in claus... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 9 Overall evaluation
| This clause will provide evaluation of different solutions.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.