hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.1.4 Solution evaluation
| This solution addresses the KI#6 to provide the application satellite coverage availability information (ASCAI) analytics when the VAL UE is using the satellite access.
The solution has no impact on the existing architecture. The ADAES can be enhanced to obtain the satellite related information from the SEAL servers ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2 Solution #2: Support of QoS analysis for services over satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.1 Solution description
| This solution addresses the KI#6.
The VAL server or the UE may act as consumers to subscribe the QoS analysis related to the services over satellite access from ADAES. They may ask to provide the preferred or predicted QoS for the requested service over satellite access.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.1.1 Procedure of QoS analysis for services over satellite access
| Figure 5.2.1.2-1 illustrates the high-level procedure of QoS analysis for services over satellite access.
Pre-condition:
- The ADAES, VAL UE, VAL server, 3GPP CN (e.g., NWDAF) are all deployed on the ground.
- The target UE is accessing the satellite.
Figure 5.2.1.1-1: Procedure of QoS analysis for services o... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.2 Architecture Impacts
| This solution has no impact on the existing architecture.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.2.4 Solution evaluation
| This solution addresses the KI#6 to support the QoS analysis for the services over the satellite access in the application enablement layer.
The solution has no impacts on the existing architecture. The ADAES can be enhanced to obtain the satellite communication related information for the target UE from the 3GPP cor... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3 Solution #3: Location management service via satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.0 General description
| Figure 5.3.0-1, illustrates the deployment of location enabler on-board satellite for assisting location management service.
Figure 5.3.0-1: Deployment of location enabler on-board satellite for assisting location management service
Basically, in this architecture option, SEAL location management server is deployed... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.1 Solution description
| Figure 5.3.1-1 illustrates the procedure for on-board satellite location management server assisting SEAL location history procedure specified in 3GPP TS 23.434.
Pre-conditions:
1. The location management server on-board satellite is deployed to assist the value-added location information.
Figure 5.3.1-1: Procedur... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.2 Architecture Impacts
| SEAL location management server is expected to be deployed on-board satellite. And the SEAL-E interface LM-E is required to support interaction between LMS on-ground to LMS on-board satellite.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.3 Corresponding APIs
| This solution impacts the SEAL-E interface LM-E with new interactions between LMS on-ground to LMS on-board satellite to support SEAL location history service via satellite access.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.3.4 Solution evaluation
| This solution provides a proposal to address the open issues listed in key issue#5 by supporting location management service via satellite access. Architecture impacts are identified where location management server is required to be deployed on-board satellite. SEAL-E interface LM-E is required with new interactions b... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4 Solution #4: Enhance SEALDD to support satellite selection in data delivery
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.1 Architecture
| This solution is based on the SEALDD architecture as in 3GPP TS 23.433 [3].
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2 Solution description
| This solution addresses the KI#3, i.e., support satellite selection in data delivery.
Because the KI description states that operators deploy some components of the SEALDD architecture on satellites to ensure reliable data transmission via satellite communications, the solution proposes to deploy the SEALDD servers on... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.1 Procedures
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.1.1 SEALDD enabled transmission with satellite selection support in data delivery
| Figure 5.4.2.1.1-1 illustrates the procedure for the source SEALDD (or S-SEALDD) server to discover and select a target SEALDD (or T-SEALDD) server based on Application Satellite Coverage Availability Information or ASCAI, and then handle the switching of serving satellites along with the context transfer between the S... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2.2 Information flows
| The following information flows are based on from the clause of 9.2.3.1 in the 3GPP TS 23.433 [3]. All new changes are in bold.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9.2.3.1 SEALDD enabled regular transmission request
| Table 9.2.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the regular application transmission service.
Table 9.2.3.1-1: SEALDD enabled Regular transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
I... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.2 Architecture Impacts
| This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.4.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5 Solution #5: Using SEALDD to enhance application enablement layer for efficient content delivery over satellite access
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.1 Architecture
| This solution is based on the SEALDD architecture as in 3GPP TS 23.433 [3].
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2 Solution description
| According to the 3GPP TS 23.433 [3], the SEALDD server offers the storage capabilities, which supports the data storage and storage management for VAL client/server, SEALDD client and other SEALDD servers. The VAL client and VAL server may coordinate to determine the usage of the SEALDD storage service. For efficient c... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.1 Procedures
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.1.1 SEALDD enabled transmission for efficient content delivery
| Figure 5.5.2.1.1-1 illustrates the procedure for the SEALDD server to determine the content caching capability of the SEALDD client, establishing the data transmission connection with the SEALDD client for efficient content delivery (or so-named ECD), as well as the SEALDD layer utilizing the satellite services to tran... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2 Information flows
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.1 SEALDD enabled ECDforSatAccess transmission request
| Table 5.5.2.2.1-1 describes the information flow from the VAL server to the SEALDD server to enable the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.1-1: SEALDD enabled ECDforSatAccess transmission request
Information element
Status
Description
VAL server ID
M
Identit... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.2 SEALDD enabled ECDforSatAccess transmission response
| Table 5.5.2.2.2-1 describes the information flow from the SEALDD server to the VAL server to respond to the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.2-1: SEALDD enabled ECDforSatAccess transmission response
Information element
Status
Description
Result
M
Success ... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2.2.3 SEALDD enabled ECDforSatAccess transmission notification
| Table 5.5.2.2.3-1 describes the information flow from the SEALDD server to the VAL server to notify the events related to the efficient content delivery (ECD) for satellite access transmission service.
Table 5.5.2.2.3-1: SEALDD enabled ECDforSatAccess transmission notification
Information element
Status
Description... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.2 Architecture Impacts
| This clause provides the architecture impacts of the solution and possible new SA6 capabilities and interfaces.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.3 Corresponding APIs
| This clause provides the corresponding APIs for supporting the solution.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 5.5.4 Solution evaluation
| This clause provides an evaluation of the solution. The evaluation should include the descriptions of the impacts to existing architectures.
5.x Solution #x: <title>
Provide a suitable title for the solution.
5.x.1 Solution description
This clause will describe the solution. Each solution should clearly describe wh... |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 6 Deployment scenarios
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 6.1 General
| This clause will provide a general description of the deployment scenarios.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 7 Business Relationships
| Provide a description of the involved business relationships.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 8 Overall evaluation
| This clause will provide evaluation of different solutions.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9 Conclusions
| |
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9.1 General conclusions
| This clause will provide general conclusions for the study.
|
a73f5408ee78d2de0a0badee0c4cf584 | 23.700-02 | 9.2 Conclusions of key issue #x
| This clause will provide conclusions for the specific key issue.
Annex A:
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2025-09
SA6#68
S6-253656
Skeleton for TR 23.700-02
0.0.0
2025-09
SA6#68
S6-253655
Key Issue on AIML model storage and deplo... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 1 Scope
| The present document is a technical report which identifies potential enhancements to application enablement services by utilizing Sensing results and proposes architectural requirements, key issues, and solutions for the potential application enablement architecture enhancements.
The study takes into consideration t... |
1d6307f47bb31085dee07c7a4bafe57f | 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.
-... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 3 Definitions of terms, symbols and abbreviations
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Symbol format (EW)
<symbol> <Explanation>
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
SEAL Service Enabler Architecture Layer for Verticals
UAE UAS A... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4 Key issues
| 4.1 Key issue #1: Application enablement architecture enhancements to support utilization and exposure of sensing results
|
1d6307f47bb31085dee07c7a4bafe57f | 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 ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4.1.2 Open Issues
| Based on the above analysis, the following aspects need to be addressed in the application enabler layer:
1. Whether and how to enhance the application enablement architecture and related functions to support the mapping of sensing service requirements of vertical applications.
2. Whether and how the existing exposur... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4.2.1 Description
| 3GPP TS 22.137 [3] has specified sensing service requirements about UAVs. Such as "The 5G system shall be able to provide sensing service to detect, and/or track one or more objects (e.g., UAVs, birds) and the environment around the object(s). "
In Rel-19, the application enabler (i.e. UAE) has been developed to supp... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4.2.2 Open Issues
| Based on the above analysis, the following open issues need to be studied:
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 1 How to enhance the UAS application enabler to support enhanced trajectory tracking for UAVs utilizing the sensing results.
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 2 How to enhance the UAS application enabler to support enhanced DAA service/functionalities for UAVs utilizing the sensing results.
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 3 How to enhance the UAS application enabler to support No Drone Zone avoidance (detect and notify) utilizing the sensing results.
| To address the open issues the following solutions are proposed:
- Solution #4: Enhancements of UAV services utilizing the sensing results;
- Solution #5: sensing based tracking dynamic UAVs;
- Solution #6: Sensing based DAA service;
- Solution #7: Sensing Coverage Information Exposure for Supporting UAV Services;
... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4.4 Key issue #4: utilizing sensing results for HD map in V2X
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 4.4.1 Description
| According to application layer support for Vehicle-to-Everything (V2X) services specified in 3GPP TS 23.286 [5], the V2X application specific server can be responsible for managing HD maps and providing the HD map information to the V2X application specific client on V2X UE. As per a proximity range set by the applicat... |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5 Architectural Requirements and Assumptions
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5.1 General
| This clause provides architectural requirements to consider for common aspect on the Sensing result management. The service specific aspect on UAS, Spatial map and V2X services are also provided in the following clauses.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5.2 Seal sensing service
| [AR-5.2-a] The Sensing result management service shall support to manage the VAL specific sensing requirements and map them to the sensing service request supported by SF/NEF, and vice verse.
[AR-5.2-b] The Sensing result management service shall support to resolve conflicts in sensing service requirements among diff... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5.3 Uncrewed Aerial System (UAS)
| [AR-5.3-a] The Uncrewed Aerial System shall support trajectory tracking for UAVs by utilizing the sensing results.
[AR-5.3-b] The Uncrewed Aerial System shall support DAA service for UAVs by utilizing the sensing results.
[AR-5.3-c] The Uncrewed Aerial System shall support No Drone Zone avoidance (detect and notify) ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5.4 Spatial map management
| [AR-5.4-a] The spatial map management service shall support to use sensing results as input data to create and update the spatial map that incorporates environment information.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 5.5 Vehicle-to-Everything (V2X) services
| [AR-5.5-a] The Vehicle-to-Everything (V2X) services shall support the creation and updating of HD map based on the device-centric sensing results.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6 Solutions
| |
1d6307f47bb31085dee07c7a4bafe57f | 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 #12
x
Sol #13
x
Sol #14
x
... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2 Solution #1: Functional Architecture to Support Sensing Application Relevant Services
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.1 Solution Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.1.1 Functional Model
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.1.2 Functional Entities Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.1.3 Reference Points Description
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.2 Architecture impacts
| Editor's Note: The architecture impacts of the solution is FFS.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.2.3 Solution evaluation
| Editor's Note: The evaluation of the solution is FFS.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.3 Solution #2: Support the sensing results exposure based on the sensing subscription request
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
NOTE 1: This solution is built on functional architecture described in solution 1 for key issue 1.
In this solution, after acquiring the sensing requirements from the sensing s... |
1d6307f47bb31085dee07c7a4bafe57f | 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).
2. The Sensing enabler server has acquired Sensing Authorization information for Sensing Service from ... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.3.3 Solution evaluation
| This solution addresses Key Issue #1, open issues #2 and #3 on how the sensing enable layer receive sensing request from sensing consumer(e.g., using the subscription mechanism) and how the sensing enable layer collect sensing results from sensing suppliers (e.g., using request/response mechanism). The solution propose... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.4 Solution #3: Support of exposure of sensing results
| This solution addresses the KI#1.
|
1d6307f47bb31085dee07c7a4bafe57f | 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... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.4.1.1 Procedure of supporting sensing analysis for ADAES
| Figure 6.4.1.1-1 illustrates the high-level procedure when the Sensing enabler, acting as a consumer, asks for sensing accuracy analytics from ADAES.
Pre-conditions:
- A-ADRF may have stored the historical sensing accuracy results for the requested sensing objects.
Figure 6.4.1.1-1: Procedure of supporting sensing... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.4.2 Solution evaluation
| This solution addresses the KI#1, and mainly focuses on open issue #1, #2, #3.
The solution is compatible with architectures described in Solution #1 which assumes there is a new SEAL sensing enabler to support the sensing services in application enablement layer.
It provides the procedure of exposure of value-add... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.5 Solution #4: Enhancements of UAV services utilizing the sensing results
| |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.5.1 Solution description
| This solution addresses the KI#2.
The following high-level solution principles apply to this solution:
- A high-level procedure for sensing request and exposure is proposed with a new Sensing enabler in the application enablement layer.
- The solution assumes the 3GPP core network will expose the sensing results r... |
1d6307f47bb31085dee07c7a4bafe57f | 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
1. ... |
1d6307f47bb31085dee07c7a4bafe57f | 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, please check the solution#1 for the KI#1.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.5.3 Solution evaluation
| This solution addresses Key Issue #2 to support detecting UAVs utilizing sensing results in the application enablement layer.
The solution is compatible with architectures described in Solution #1 which assumes there is a new SEAL sensing enabler to support the sensing services in application enablement layer.
The s... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.6 Solution #5: sensing based tracking dynamic UAVs
| |
1d6307f47bb31085dee07c7a4bafe57f | 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.
|
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.6.2 Procedures
| This feature utilizes the following procedures:
- Step 1: UAS Application Specific Server or the host UAV subscription for host UAV’s dynamic information with UAE server.
- Step 2: UAE server tracking host UAV’s UE location with support from SEAL’s location management server.
- Step 3: UAE server management of dynam... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.6.2.1 Subscription for host UAV dynamic information
| This procedure intends to obtain the host UAV dynamic 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 dynamic 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 recei... |
1d6307f47bb31085dee07c7a4bafe57f | 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) (o... |
1d6307f47bb31085dee07c7a4bafe57f | 23.700-15 | 6.6.2.4 Notification of host UAV dynamic information
| Pre-conditions:
- UAS Application Specific Server has performed subscription as per procedure in clause 7.8.2.1 in 3GPP TS 23.255 [4] with UAE server 1.
- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3 in 3GPP TS 23.255 [4].
Figure 6.6.2.4: Notification for host UA... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.