hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.5.3.4 Notify real-time UAV status information
|
Table 7.5.3.4-1 describes the information flow for a UAS application specific server to receive notification about real-time UAV status information from the UAE server.
Table 7.5.3.4-1: Notify real-time UAV status information
Information element
Status
Description
Subscription ID
M
Identifier of the subscription for this notification.
Real-time UAV(s) status information
M
One or more real-time UAV(s) status information
>UAV ID
M
The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) for which the real-time UAV status information is notified.
>UAV status information
M
The UAV status information includes the UAV network connection status information, location information and timestamp.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.5.3.5 Unsubscribe real-time UAV status information request
|
Table 7.5.3.5-1 describes the information flow for a UAS application specific server to unsubscribe to real-time UAV status information at the UAE server.
Table 7.5.3.5-1: Unsubscribe real-time UAV status information request
Information element
Status
Description
Subscription ID
M
Identifier of the subscription for this notification.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.5.3.6 Unsubscribe real-time UAV status information response
|
Table 7.5.3.6-1 describes the information flow for UAE server to respond for real-time UAV status unsubscription request from the UAS application specific server.
Table 7.5.3.6-1: Unsubscribe real-time UAV status information response
Information element
Status
Description
Result
M
Result from the UAE server in response to unsubscription request indicating success or failure
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6 Change of USS during flight
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.1 General
|
This feature introduces the UAS application enablement services for supporting change of UAS application specific server. In particular, the UAE layer provides support for the following operations:
- Support of the registration of the UAE clients multi-USS capability to the UAE server as described in clause 7.1a.
- Support the distribution of the for multi-USS policies from the UAS application specific server to the UAE server and the UAE client, as described in clause 7.6.2.1 and clause 7.6.2.2.
- Support the change of UAS application specific server, as described in clause 7.6.2.3.
- Support the UAE server triggered change of USS, as described in clause 7.6.2.5.
NOTE: The functions of the USS are out of scope of the present specification.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2.1 Management of multi-USS configuration
|
This procedure manages the multi-USS policies at the UAE server, based on an application request from UAS application specific server to support the change of USS for a UAS.
Figure 7.6.2.1-1 illustrates the procedure where the UAE server receives an application request for managing the multi-USS policies for a UAS from the UAS application specific server.
Pre-condition:
- The UAV has received its UAS ID from the UAS application specific server.
- The UAV has performed the UAS UE registration procedure.
Figure 7.6.2.1-1: Multi-USS management procedure
1. The UAS application specific server sends to the UAE server a Multi-USS management request. The request includes the UAV (UAE client) identifier and the Multi-USS policies. A Multi-USS policy contains: allowed target USSes (identified by e.g. FQDN), serving USS information, and additional information for change of USS (USS change constraints parameter geo location/area threshold for change of USS by UAV). The UAE server stores the Multi-USS policies corresponding to the UAV ID. In case of removal of a Multi-USS policy for a USS from the UAE server, the request shall include the UAV identifier and a USS identifier (e.g. FQDN) for the USS that will be removed.
2. The UAE server sends to the UAS application specific server a Multi-USS management response with a positive or negative acknowledgement of the request.
3. UAE server executes the multi-USS configuration according to clause 7.6.2.2.
4. After execution of USS management configuration, the UAE server notifies the UAS application specific server with a Multi-USS management complete based on the configured capabilities of the UAE client.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2.2 Multi-USS configuration
|
This procedure enables the configuration of the UAE client, based on a request from UAS application specific server to configure multi-USS policies to the UAE client.
Figure 7.6.2.2-1 illustrates the Multi-USS configuration procedure.
Pre-conditions:
1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4].
2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server.
3. UAE server has performed the Multi-USS management procedure according to clause 7.6.2.1.
Figure 7.6.2.2-1: Multi-USS configuration
1. The UAE server sends a Multi-USS configuration request to the UAE client. The UAE client receives a Multi-USS configuration request that includes the Multi-USS policies from the UAE server. In case of removal of one or more Multi-USS policies for a USS from the UAE client, then the request shall only include a USS identifier (e.g. FQDN) for the USSes that will be removed.
2. The UAE client stores or removes the Multi-USS policies as per the information received in step 1.
3. The UAE client sends a Multi-USS configuration response to the UAE server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2.3 UAE layer assisted change of USS
|
This procedure provides a mechanism for supporting dynamic change of USS which may be performed while the UAV flight is ongoing, due to expected location/mobility of the UAV, emergency events, etc.
Figure 7.6.2.3-1 illustrates the procedure where the UAE server supports the change of USS.
Pre-conditions:
1. UAE client has indicated support of change of USS by the Multi-USS capability.
2. UAS application specific server has provided Multi-USS policies to the UAE client and the UAE server.
Figure 7.6.2.3-1: UAE layer assisted change of USS
1. The UAE server receives a USS change request from a serving USS (UAS application specific server #1), indicating that a target USS (UAS application specific server #2) an take over the communication. The request includes the UAV (UAE client) identification information, target USS information and USS change authorization information (e.g. authorization token). Optionally, updated Multi-USS policies for one or more USSes can be included. The UAE server verifies that the request is authorized (e.g., Multi-USS capability is enabled, new USS part of the allowed USS information).
2. If required, the UAE server translates this to a UP path change and interacts with NEF as AF for influence UP path (switching to target DNAI). In particular UAE server (acting as AF) checks whether it can serve the target DNAI corresponding to the target USS based on the mapping of USS to DNAI which was performed in step 2 of clause 7.6.2.5. Interaction with 5GC is performed according to functionality for application function influence on traffic routing, see 3GPP TS 23.502 [13] clause 4.3.6.3.
3. The UAE server forwards the USS change request to the UAE client including target USS information and updated Multi-USS policies.
4. Perform change of USS.
The UAE client initiates communication with the target USS based on the USS change request and the Multi-USS policies.
5. The UAE client sends a USS change response indicating to what USS the change of USS has been performed.
6. The UAE server sends a USS change response to the UAS application specific server indicating that a change of USS has been performed.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2.4 UAE client assisted change of USS
|
This procedure enables the UAE client to provide a dynamic change of USS while the UAV flight is ongoing, due to an emergency change of USS deemed necessary by the UAE client. The UAE client initiates the change of USS on behalf of the USS based on previously provided Multi-USS policy.
Figure 7.6.2.4-1 illustrates the procedure where the UAE server supports the change of USS.
Pre-conditions:
1. UAE client has indicated support of change of USS by the Multi-USS capability.
2. UAS application specific server has provided Multi-USS policies to the UAE client and the UAE server.
Figure 7.6.2.4-1: UAE client assisted change of USS
1. An emergency change of USS is deemed necessary by the UAE Client, and the UAE client initiates the change of USS on behalf of the USS based on previously provided Multi-USS policy.
2. Perform change of USS. The UAE client initiates communication with the target USS (UAS application specific server #2) based on the previously provided Multi-USS policies.
3. The UAE client sends a USS change notification indicating to what USS the change of USS has been performed. The identity of the target USS (UAS application specific server #2) is included. The USS change notification is only sent if the UAE client has a connection to the UAE server.
4. The UAE server sends a USS change notification to the UAS application specific server #1 indicating that a change of USS has been performed.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.2.5 UAE server triggered change of USS
|
In multi-USS scenarios, each USS can be physically located in different clouds, and it is also possible that a USS is deployed at the edge.
Figure 7.6.2.5-1 illustrates the procedure where the UAE server supports change of USS for a multi-USS/LUN scenario, where the interaction with the communication network for supporting a UAS session requires the interaction to more than one USS e.g., due to UAV mobility to different geographical area covered by different edge clouds.
Pre-conditions:
- The UAV has performed the UAS UE registration procedure.
- UAE client and UAE server have indicated multi-USS support.
Figure 7.6.2.5-1: UAE server triggered change of USS
1. The UAE server has performed the USS management procedure of clause 7.6.3.1; however, at the multi-USS management request, UAE server also receives from UAS application specific server the USS service areas (geographical) for all allowed USSs, and optionally the USS to DNAI mapping and a USS list per given Local USS network (LUN).
2. The UAE server maps each USS with different topological areas based on the USS to DNAI mapping (based on step 1), for all USSs which are allowed for a target area where the UAV is allowed to fly (e.g. within the LUN). Then it also maps and stores all pairs of <USS x, DNAI y> per LUN or for the areas of interest for the UAV (e.g., based on the allowable routes).
3. The UAE server tracks the location of the UAV, by requesting on-demand location monitoring from SEAL LMS (acting as VAL server in procedure of clause 9.3.4 or clause 9.3.5 of 3GPP TS 23.434 [5]) or via subscribing for monitoring the UAV location deviation (specified in clause 9.3.11 of 3GPP TS 23.434 [5]).
4. The UAE server detects an expected UAV location change to an area covered by a different USS (based on SEAL LMS monitoring subscription/request as in step 3), it generates a trigger event indicating that the UE moves to an area where the USS is overlapping with other USS, or another overlapping USS within LUN area is not available.
If it is an overlap, the UAE server checks whether the performance of serving USS is expected to get impacted (e.g., by requesting DN performance analytics for the target area) or if the serving USS is not supported at target area, checks what is the best available USS and whether this can provide the same services. The criteria for the best available USS may relate to the location of the UAV, but it can also be the priorities of the USS (based on the policies received) at the target area and the capabilities (services) provided by the target USS.
5. The UAE server sends to the UAS application specific server a USS change trigger notify indicating the recommendation for a USS change for the UAS and provides the target USS ID. Alternatively, the trigger message indicates a UAV mobility event, based on steps 3/4.
6. The UAS change procedure follows as specified in 7.6.2.3.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.1 Multi-USS management request
|
Table 7.6.3.1-1 describes the information flow Multi-USS management request from the UAS application specific server to the UAE server.
Table 7.6.3.1-1: Multi-USS management request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the Multi-USS management. This ID can be the USS identifier, when the UAS application specific server is the USS.
UAS ID
M
The identification of the UAS for which the Multi-USS management request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
UAS registration area
O
The registration area where the UAV is allowed to fly
UAS allowed route
O
The UAV allowed route within the registration area.
Multi-USS policy management container (see NOTE)
O
The Multi-USS policy management container consists of the requirements and policy for Multi-USS management.
> Serving USS information
M
Information about the serving USS identifier
> Additional information for change of USS
M
Information about the serving USS, related with the switch to a particular target USS
> Area for change of USS
M
The area where the Multi-USS management request applies. This can be geographical area, or topological area in which the capability is active.
> Allowed USS(s) information
O
The information for the allowed USSs for the UAS.
>> USS ID
M
The identity of the allowed USS from the list of USSs for the target UAS (identified e.g. by FQDN)
>> USS service area
M
The geographical area per USS
>> USS service requirements
M
The capabilities and key performance requirements per each USS service.
>> List of USS DNAI(s)
M
DNAI(s) associated with the target USS.
>> LUN ID
M
Identity of the LUN where the report applies
NOTE: If Multi-USS policy management container is not included for a USS, it indicates removal of the Multi-USS policy management related information for this USS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.2 Multi-USS management response
|
Table 7.6.3.2-1 describes the information flow Multi-USS management response from the UAE server to the UAS application specific server.
Table 7.6.3.2-1: Multi-USS management response
Information element
Status
Description
Result
M
The positive or negative result of the Multi-USS management request.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.3 Multi-USS management complete
|
Table 7.6.3.3-1 describes the information flow Multi-USS management complete from the UAE server to the UAS application specific server.
Table 7.6.3.3-1: Multi-USS management complete
Information element
Status
Description
Result
M
The positive or negative result of the Multi-USS configuration.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.4 Multi-USS configuration request
|
Table 7.6.3.4-1 describes the information flow Multi-USS configuration request from the UAE server to the UAE client.
Table 7.6.3.4-1: Multi-USS configuration request
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the Multi-USS configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
Multi-USS policy management configuration (see NOTE)
O
The Multi-USS policy management configuration information to be configured at the UAS.
> Allowed USS
M
Identifier of a USS that can be the target of a switch (identified e.g. by FQDN)
> Serving USS information
M
Information about the serving USS identifier
> Additional information for change of USS
M
Information about the serving USS, related with the switch to a particular target USS
> Area for change of USS
M
The area where the Multi-USS management request applies. This can be geographical area, or topological area in which the capability is active.
NOTE: If Multi-USS policy management configuration is not included for a USS, it indicates removal of the Multi-USS policy management configuration for this USS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.5 Multi-USS configuration response
|
Table 7.6.3.5-1 describes the information flow Multi-USS configuration response from the UAE client to the UAE server.
Table 7.6.3.5-1: Multi-USS configuration response
Information element
Status
Description
Result
M
The positive or negative result of the Multi-USS configuration
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.6 USS change request
|
Table 7.6.3.6-1 describes the information flow USS change request from the UAS application specific server to the UAE server and from the UAE server to the UAE client.
Table 7.6.3.6-1: USS change request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the change of USS. This ID can be the USS identifier, when the UAS application specific server is the USS.
UAS ID
M
The identification of the UAS for which the USS change request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
USS change authorization information
M
An authorization token to verify the request.
Target USS
M
Identification of the USS that is the target of a switch (identified e.g. by FQDN)
Target USS info
M
Information for the target USS
> USS endpoint
M
Endpoint information (e.g. URI, FQDN, IP address) used to communicate with the USS.
> USS capabilities
O
The capabilities supported by the target USS
> LUN ID
O
Identity of the LUN where the serving/target USS belongs
>List of USS DNAI(s)
O
DNAI(s) associated with the target USS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.7 USS change response
|
Table 7.6.3.7-1 describes the information flow USS change response from the UAE client to the UAE server and from the UAE server to the UAS application specific server.
Table 7.6.3.7-1: USS change response
Information element
Status
Description
Result
M
The positive or negative result of the USS change request.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.8 USS change notification
|
Table 7.6.3.8-1 describes the information flow USS change notification from the UAE client to the UAE server and from the UAE server to the UAS application specific server.
Table 7.6.3.8-1: USS change notification
Information element
Status
Description
Reason
M
Reason for change of /USS.
Target USS information
M
Identifier of the new USS that the UAV has connected to (identified e.g. by FQDN).
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.6.3.9 USS change trigger notify
|
Table 7.6.3.9-1 describes the information flow USS change trigger notify from the UAE server to the UAS application specific server.
Table 7.6.3.9-1: USS change trigger notify
Information element
Status
Description
UAS ID
M
Identity of the UAS for which the trigger applies
Serving USS ID
M
Identity of the serving USS
Target USS ID
O
Identity of the target USS based on the recommendation
LUN ID
O
Identity of the LUN where the serving USS belongs
UAV mobility event
O
The mobility event e.g., expected UE mobility to a service area outside the current USS serving area
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7 UAE layer support for DAA services and applications
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.1 General
|
This feature enables the UAS application enablement services for assisting the UAS application with DAA handling. In particular, the UAE layer provides support for the following operations:
- Support of the registration of the UAE clients DAA assistance capability and, if supported, the LDGS capability to the UAE server as described in clause 7.1a.
- Support the distribution of the DAA application policy from the UAS application specific server to the UAE server and the UAE client, as described in clause 7.7.2.1.
- Support the UAS application with DAA, as described in clause 7.7.2.2.
NOTE: The Detect and Avoid operations are out of scope of the present specification.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.1 Configuration of DAA policies to the UAE layer and the UAS client
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.1.1 Management of DAA support configuration
|
Figure 7.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-condition:
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 7.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.
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.
4. After execution of DAA configuration, the UAE server shall send a DAA support management complete to the UAS application specific server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.1.2 DAA support configuration procedure
|
Figure 7.7.2.1.2-1 illustrates the DAA support configuration procedure. This procedure enables the configuration of the UAE client, based on a request from UAS application specific server to configure the DAA application policy to the UAE client.
Pre-conditions:
1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4].
2. UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server.
3. UAE server has performed the DAA support management procedure according to clause 7.7.2.1.1.
Figure 7.7.2.1.2-1: DAA support configuration procedure
1. The UAE server shall send a DAA support configuration request to the UAE client. The UAE client receives a DAA support configuration request from the UAE server that includes the DAA application policy. If the UAE client has LDGS capability, and the procedure is for LDGS assisted DAA, then the DAA application policy includes parameters for the control of LDGS assisted DAA.
NOTE: The UAE client can serve multiple USSes, hence, the UAE client receives configuration information pertaining to each USS.
2. The UAE client shall store or remove the DAA application policy as per the information received in step 1. The DAA application policy is forwarded to the UAS application.
3. The UAE client shall send a DAA support configuration response to the UAE server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.2 UAE layer support for DAA applications
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.2.1 DAA support involving UAVs with U2X support
|
Figure 7.7.2.2.1-1 illustrates the procedure with DAA support involving UAVs with U2X support. If the UAE client has LDGS capabilities, the UAE client provides ground based DAA assistance for the target UAVs in its monitoring range.
Pre-conditions:
1. UAE server has provided the DAA application policy to the UAE client.
2. The UAE client can communicate with the target UAVs using U2X communication.
Figure 7.7.2.2.1-1: DAA support involving UAVs with U2X support
1. The UAE layer has, e.g. based on information provided by the U2X layer, detected UAVs in proximity, see 3GPP TS 23.256 [4] clause 5.6. The UAE client informs its own UAS application specific server about the detected collision. If the UAE client has LDGS capability, and the procedure is for LDGS assisted DAA, then based on the configuration/policy received from the USSes (e.g., DAA triggering thresholds), the LDGS assists with deconfliction by detecting possible collisions.
2. The UAE client shall send a DAA client event information to the UAE server with information about one or more UAVs in proximity as detected or about a LDGS collision detection performed in step 1.
3. The UAE server shall record the DAA client event information with current timestamp. UAE server shall request UAE client location information from the SEAL location services. The UAE server shall record the received location information with current timestamp. The UAE server shall send the DAA client event information to the UAS application specific server.
4. The UAS application specific server provides a DAA client event information acknowledge to the UAE server. The UAS application specific server may include more information in the acknowledgement (e.g., other UAVs detected information by UAS application layer mechanisms, alternative flight path). If the event information indicates LDGS deconfliction assistance, the UAS application specific server sends DAA flightpath update to the LDGS.
5. The UAE server shall send a DAA client event information acknowledge to the UAE client, and the UAE client shall provide the application layer (i.e. UAS client) with the consolidated information from the UAS application specific server. If the UAE client has LDGS capability, and the procedure is for LDGS assisted DAA, then the LDGS assists with deconfliction by sending the flight path information to respective target UAVs using U2X connectivity.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.2.2.2 DAA support involving UAVs without U2X support
|
Figure 7.7.2.2.2-1 illustrates the procedure with DAA support involving UAVs without U2X support.
Pre-conditions:
1. UAS application specific server has provided DAA configuration parameters to the UAE client.
2. The UAV does not support U2X layer.
Figure 7.7.2.2.2-1: DAA support involving UAVs without U2X support
1. The UAS application specific server has received information about UAVs (e.g. via UAS application layer mechanism or as in step 3 of clause 7.7.2.2.1. The UAS application specific server determines the information of the UAVs which may be in the proximity of the UAV.
2. The UAS application specific server sends a DAA server event information to the UAE server which includes information of other UAVs in the proximity of the UAV. The UAE server shall verify that the request is authorized before sending the DAA server event information to the UAE client.
3. The UAE server performs coordination with Real-Time UAV connection status monitoring and location reporting is performed by the UAE server, see clause 7.5 and 3GPP TS 23.434 [5], clause 9.3. The UAE server shall send a DAA server event information to the UAE client comprising the UAVs information and location of each UAV in proximity of the UAV.
4. The UAE client shall send to the UAE server a DAA server event information acknowledge.
5. The UAE server shall send a DAA server event information acknowledge to the UAS application specific server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.1 DAA support management request
|
Table 7.7.3.1-1 describes the information flow DAA support management request from the UAS application specific server to the UAE server.
Table 7.7.3.1-1: DAA support management request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the DAA management. This ID can be the USS identifier, when the UAS application specific server is the USS.
UAS ID
M
The identification of the UAS (UAV or LDGS) for which the DAA support management request applies. This could be in form of identifier for the UAS, e.g., group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
List of UAS ID
O
A list of UAS identification information, e.g. CAA level UAV ID, of the UAVs that are identified as target UAVs, is included when UAE client has LDGS capability.
Geographical area
O
The area where the DAA client configuration applies to locate relevant LDGS capable UAE clients. This can be geographical area, or topological area.
DAA application policy
O
The DAA application policy.
>DAA triggering thresholds
O
Indicate threshold for DAA, that determine when an LDGS may trigger detect and/or resolution of flightpath conflict.
>Time validity
O
Time validity where the DAA client configuration applies for an LDGS capable UAE client.
> Reporting frequency
O
Indication on how often the LDGS collect target UAVs information and how often UAS application specific server would like to be reported. This can be event based and / or time based.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.2 DAA support management response
|
Table 7.7.3.2-1 describes the information flow DAA support management response from the UAE server to the UAS application specific server.
Table 7.7.3.2-1: DAA support management response
Information element
Status
Description
Result
M
The positive or negative result of the DAA support management request.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.3 DAA support management complete
|
Table 7.7.3.3-1 describes the information flow DAA support management complete from the UAE server to the UAS application specific server.
Table 7.7.3.3-1: DAA support management complete
Information element
Status
Description
Result
M
The positive or negative result of provision of the DAA application policy to the UAS application.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.4 DAA support configuration request
|
Table 7.7.3.4-1 describes the information flow DAA support configuration request from the UAE server to the UAE client.
Table 7.7.3.4-1: DAA support configuration request
Information element
Status
Description
UAS ID
M
The identification of the UAS (UAV or LDGS) for which the DAA management request applies. This could be in form of identifier for the UAS, e.g., group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
List of UAS ID
O
A list of UAS identification information, e.g. CAA level UAV ID, of the UAVs that are identified as target UAVs, is included when UAE client has LDGS capability.
DAA application policy
O
The DAA application policy.
>DAA triggering thresholds
O
Indicate threshold for DAA, that determine when an LDGS may trigger detect and/or resolution of flightpath conflict.
>Time validity
O
Time validity where the DAA client configuration applies for an LDGS capable UAE client.
> Reporting frequency
O
Indication on how often the LDGS collect target UAVs information and how often UAS application specific server would like to be reported. This can be event based and / or time based.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.5 DAA support configuration response
|
Table 7.7.3.5-1 describes the information flow DAA support configuration response from the UAE client to the UAE server.
Table 7.7.3.5-1: DAA support configuration response
Information element
Status
Description
Result
M
The positive or negative result of provision of the DAA application policy to the UAS application.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.6 DAA client event information
|
Table 7.7.3.6-1 describes the information flow DAA client event information from the UAE client to the UAE server and from the UAE server to the UAS application specific server.
Table 7.7.3.6-1: DAA client event information
Information element
Status
Description
UAS ID
M
The identification of the UAS (UAV or LDGS) for which the DAA client support information applies. This could be in form of identifier for the UAS, e.g., group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
UAE layer detected information
M
List of UASes where e.g. U2X layer or LDGS has detected possible flight path conflict.
> UAS identity
M
The identification of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict or an LDGS where LDGS has detected possible flight path conflict via U2X or Uu communication.
> Location information
M
Location of e.g. a U2X-UAS where U2X layer has detected possible flight path conflict or an LDGS where LDGS has detected possible flight path conflict via U2X or Uu communication.
> Associated alert
M
Alert based on the detection of the UAE client, e.g. collision detected, collision resolved etc.
Time of arrival
O
The time when UAS enters the monitoring range of an LDGS, reported by LDGS as event to USS for the purpose of tracking.
Time of departure
O
The time when UAS leaves the monitoring range of an LDGS, reported by LDGS as event to USS for the purpose of tracking.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.7 DAA client event information acknowledge
|
Table 7.7.3.7-1 describes the information flow DAA client event information acknowledge from the UAS application specific server to the UAE server and from the UAE server to the UAE client.
Table 7.7.3.7-1: DAA client event information acknowledge
Information element
Status
Description
UAS ID
M
The identification of the UAS (UAV or LDGS) for which the DAA client support information acknowledge applies. This could be in form of identifier for the UAS, e.g., group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
UAE layer detected information
M
List of UASes where the UAS application specific server has confirmed possible flight path conflict.
> UAS identity
M
The identification of a UAS where UAS application specific server has confirmed possible flight path conflict or an LDGS where LDGS has detected possible flight path conflict via U2X or Uu communication.
> Location information
M
Location of a UAS where UAS application specific server has confirmed possible flight path conflict or an LDGS where LDGS has detected possible flight path conflict via U2X or Uu communication.
> Updated flight path
O
Updated flight path from USS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.8 DAA server event information
|
Table 7.7.3.8-1 describes the information flow DAA server event information from the UAS application specific server to the UAE server and from the UAE server to the UAE client.
Table 7.7.3.8-1: DAA server event information
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the DAA server support information applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
UAE layer detected information
M
List of UASes where the UAS application specific server has confirmed possible flight path conflict.
> UAS identity
M
The identification of an UAS where UAS application specific server has confirmed possible flight path conflict.
> Location information
M
Location of an UAS where UAS application specific server has confirmed possible flight path conflict.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.7.3.9 DAA server event information acknowledge
|
Table 7.7.3.9-1 describes the information flow DAA server event information acknowledge from the UAE client to the UAE server and from the UAE server to the UAS application specific server.
Table 7.7.3.9-1: DAA server event information acknowledge
Information element
Status
Description
Reason
M
Acknowledgement of DAA server event information.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8 Tracking dynamic UAVs in an application defined area relative to a host UAV
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.1 General
|
The UAE server can be responsible for tracking a host UAV’s dynamic information (i.e., information of other dynamic UAVs in an application defined area relative to a host UAV). As per a proximity range set by the application layer (e.g. UAS Application Specific Server), the UAE layer supports providing the dynamic information (i.e. other UAVs’ location information) to the UAS Application Specific Server (UTM/USS) and/or to the host UAV. This feature can be utilized by UAS applications (e.g. DAA, Dynamic maps).
This feature utilizes the following procedures:
- UAS Application Specific Server or the host UAV subscription for host UAV’s dynamic information with UAE server.
- UAE server tracking host UAV’s UE location with support from SEAL’s location management server.
- UAE server management of dynamic UE location based group.
- UAE server obtaining dynamic information from the UAVs in application defined proximity range of the host UAV.
- UAE server notification of host UAV’s dynamic information to the UAS Application Specific Server and/or to the host UAV.
NOTE: The details of the usage of dynamic information of host UAV by UAS Application Specific Server or by the host UAV is out of scope of this specification.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.1 Subscription for host UAV dynamic information
|
Figure 7.8.2.1-1 describes the procedure for subscription for host UAV’s dynamic information.
Pre-condition:
- UAS Application Specific Server has registered with UAE server 1 which is responsible for the host UAV.
- The UAV ID and application defined proximity range information are configured on the host UAV.
Figure 7.8.2.1-1: Subscription for host UAV dynamic information
1. The UAS Application Specific Server or UAE client of host UAV sends a subscribe host UAV dynamic information request to the UAE server 1. The request includes the UAV ID of the host UAV, application defined proximity range information.
2. The UAE server 1 stores the subscription information.
3. The UAE server 1 sends subscription response to the UAS Application Specific Server.
4. The UAE server 1 obtains and initiates tracking the host UAV location from the location management server 1 as specified in 3GPP TS 23.434 [5].
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.2 Management of dynamic UE location based group
|
Figure 7.8.2.2-1 describes the procedure for management of dynamic UE location based group.
Pre-condition:
- UAE server 1 has received an updated location of the host UAV as per procedure specified in 3GPP TS 23.434 [5].
- UAE server 1 is configured with UAE server 2..N information of other UAS operator and their supported region of operation.
Figure 7.8.2.2-1: Management of dynamic UE location group
1. Dynamic UE location based group creation or update is triggered (e.g. notified of the UE location of host UAV) via the step 4 in clause 7.8.2.1 for the UAV ID of the host UAV.
2. UAE server 1 uses its associated LMS 1 to obtain the dynamic UE list and the corresponding location information in the proximity area of the host UAV by providing the application defined proximity range and the UE location of the host UAV as specified in clause 9.3.10 of 3GPP TS 23.434 [5].
3. UAE server 1 determines the list of other UAE servers 2..N operating in the same location.
4. For each UAE server determined in step 3, UAE server 1 requests the dynamic UE list and its corresponding location information for the application defined proximity range by providing the UE location of the host UAV.
5. The UAE server(s) 2..N obtain UE information corresponding to the UE location and application defined proximity range from its corresponding LMS 2..N as specified in 3GPP TS 23.434 [5].
6. The UAE server(s) 2..N sends get response with UE list in the UE location and application defined proximity range to UAE server 1.
7. If UAE server 1 has no dynamic UE location group for the UAV ID, the UAE server 1 creates a dynamic UE location based group with the UE list received from its LMS and other UAE server(s) 2..N. Further UAE server 1 stores the dynamic UE location based group. Otherwise, the UAE server 1 updates the dynamic UE location group with the latest UE information. The UAVs whose locations are no more within the application defined proximity range are removed from the dynamic UE location group.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.3 Obtaining dynamic information of the UEs in application defined proximity range
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.3.1 Subscription procedure within UAS operator
|
Figure 7.8.2.3.1-1 describes the subscription procedure within UAS operator to obtain dynamic information from the UEs in application defined proximity range.
Pre-condition:
- UAE server 1 is tracking the host UAV and has created the dynamic UE location based group as per procedure in clause 7.8.2.2.
Figure 7.8.2.3.1-1: Subscription procedure within UAS operator
1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE clients who are part of the dynamic UE location group. These UAE clients (UAVs) belong to the same UAS operator as the host UAV. The request consists of reporting configuration (e.g. frequency of reporting, event based).
2. The UAE client(s) store the subscription information.
3. The UAE client(s) send a subscription response to the UAE server 1.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.3.2 Subscription procedure across UAS operators
|
Figure 7.8.2.3.2-1 describes the subscription procedure across UAS operators to obtain dynamic information from the UEs in application defined proximity range.
Pre-condition:
- UAE server 1 has created the dynamic UE location based group as per procedure in clause 7.8.2.2.
Figure 7.8.2.3.2-1: Subscription procedure across UAS operators
1. The UAE server 1 managing the dynamic UE location group sends subscribe dynamic information request to the UAE server(s) who’s UAVs are part of the dynamic UE location group. The request consists of UAV IDs, reporting configuration (e.g. frequency of reporting, event based).
2. The UAE server 2 performs subscription procedure as specified in clause 7.8.2.3.1 with the UAE client(s).
3. The UAE server 2 sends a subscription response to the UAE server 1.
NOTE: UAE server 1 initiates this procedure with other UAE servers operating in the area.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.3.3 Notification procedure
|
Figure 7.8.2.3.3-1 describes the notification procedure of dynamic information from the UEs in application defined proximity range.
Pre-condition:
- UAE server 2 has received the notification of dynamic information from its subscribed UAE client(s).
Figure 7.8.2.3.3-1: Notification procedure
1. As per subscription procedure in clause 7.8.2.3.1 and clause 7.8.2.3.2, the UAE client(s) and UAE server 2 (of another UAS operator) send notification of dynamic information to the UAE server 1. The notification includes the nearby UE information (e.g. UAVs), distance with nearby UEs, UEs location information.
2. The UAE server 1 aggregates information from different UAE clients to create the host UAV dynamic information.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.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 with UAE server 1.
- UAE server 1 has prepared the host UAV dynamic information as per procedure in clause 7.8.2.3.3.
Figure 7.8.2.4-1: 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 notification includes the aggregated information of all the UEs 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.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.2.5 Unsubscription for host UAV dynamic information
|
Figure 7.8.2.5-1 describes the procedure for unsubscription for host UAV’s dynamic information.
Pre-condition:
- The UAS Application Specific Server or UAE client of the host UAV have performed the subscription procedure as specified in clause 7.8.2.1
Figure 7.8.2.5-1: Unsubscription for host UAV dynamic information
1. The UAS Application Specific Server or UAE client of host UAV sends a unsubscribe host UAV dynamic information request to the UAE server 1. The request includes subscription ID.
2. The UAE server 1 removes the previously stored subscription information.
3. The UAE server 1 sends unsubscription response to the UAS Application Specific Server.
4. The UAE server 1 stops tracking the host UAV location from the location management server 1 as specified in 3GPP TS 23.434 [5].
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.1 Subscribe host UAV dynamic information request
|
Table 7.8.3.1-1 describes the information flow for a UAS application specific server to subscribe to host UAV dynamic information at the UAE server.
Table 7.8.3.1-1: Subscribe host UAV dynamic information request
Information element
Status
Description
UAV ID
M
Identifier of the host UAV.
Application defined proximity range information
M
Description of the range information over which the host UAV's dynamic information is required.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.2 Subscribe host UAV dynamic information response
|
Table 7.8.3.2-1 describes the information flow for UAE server to respond for host UAV dynamic subscription request from the UAS application specific server.
Table 7.8.3.2-1: Subscribe host UAV dynamic information response
Information element
Status
Description
Result
M
Result from the UAE server in response to subscription request indicating success or failure
Subscription ID (NOTE)
O
Identifier of a successful subscription.
NOTE: This IE is included when the Result indicates success
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.3 Notify Host UAV dynamic information
|
Table 7.8.3.3-1 describes the information flow for a UAS application specific server to receive notification about Host UAV dynamic information from the UAE server.
Table 7.8.3.3-1: Notify Host UAV dynamic information
Information element
Status
Description
Subscription ID
M
Identifier of the subscription for this notification.
Location of the host UAV
M
The location of the host UAV during the Host UAV dynamic information subscription.
List of UAVs information
M
The information of the UAVs which were detected in the application defined proximity range.
>Nearby UAV ID
M
The identifier of nearby UAS
>Location information
M
Location information of the nearby UAV within the application defined proximity range
>Distance information
M
Distance information of the nearby UAV, relative to the host UAV.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.4 Notification of dynamic information
|
Table 7.8.3.4-1 describes the information flow for notification of dynamic information from UAE client to the UAE server.
Table 7.8.3.4-1: Notification of dynamic information
Information element
Status
Description
Subscription ID
M
Identifier of the subscription for this notification.
List of UAVs information
M
The information of the UAVs which were detected in the proximity area of the reporting UAV.
>Nearby UAV ID
M
The identifier of nearby UAV
>Local dynamic information
M
The local dynamic information of the nearby UAV (e.g. location)
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.5 Unsubscribe host UAV dynamic information request
|
Table 7.8.3.5-1 describes the information flow for a UAS application specific server to unsubscribe the host UAV dynamic information at the UAE server.
Table 7.8.3.5-1: Unsubscribe host UAV dynamic information request
Information element
Status
Description
Subscription ID (NOTE)
M
Identifier of a successful subscription.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.8.3.6 Unsubscribe host UAV dynamic information response
|
Table 7.8.3.6-1 describes the information flow for UAE server to respond for host UAV dynamic unsubscription request from the UAS application specific server.
Table 7.8.3.6-1: Unsubscribe host UAV dynamic information response
Information element
Status
Description
Result
M
Result from the UAE server in response to unsubscription request indicating success or failure
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9 Support of real time UAV flight path monitoring assistance
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.1 General
|
This feature introduces the UAS application enablement services for support of real time UAV flight path monitoring assistance. In particular, the UAE layer provides support for the following operations:
- Support of the registration of the UAE clients real time UAV flight path monitoring assistance capability to the UAE server as described in clause 7.1a.
- Support the real time flight path monitoring assistance procedure from the UAS application specific server to the UAE server and the UAE client, as described in clause 7.9.2.1 and clause 7.9.2.2.
- Support of the real time flight path reporting procedure from the UAE client to the UAS application specific server, as described in clause 7.9.2.3.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.2.1 Real time UAV flight path monitoring assistance procedure
|
This procedure manages the real time UAV flight path monitoring assistance at the UAE server, based on an application request from the UAS application specific server to perform real time UAV flight path monitoring assistance.
Figure 7.9.2.1-1 illustrates the procedure where the UAE server receives a request from the UAS application specific server (e.g., USS) to perform real time UAV flight path monitoring assistance.
Pre-condition:
- The UAE client has indicated support of real time UAV flight path monitoring assistance capability.
- The UAV has received its UAS ID from the UAS application specific server.
- The UAV has performed the UAS UE registration procedure.
Figure 7.9.2.1-1: Real time flight path monitoring assistance procedure
1. The UAE server receives a Flight path reporting configuration request from the UAS application specific server including QoS and QoE related triggering events (QoS thresholds, QoE thresholds, periodicity to collect QoS and QoE information), validity scope (flight path waypoints and/or geographical area, time). The QoS and QoE related triggering events can be provided separately for Uu and for PC5.
2. The UAE server sends to the UAS application specific server a Flight path reporting configuration response with a positive or negative acknowledgement of the request, based on capabilities of the UAE server to undertake the task.
3. The UAE server executes the flight path reporting configuration of the UAE client by sending a configuration request to the UAE client as indicated in Figure 7.9.2.2-1, including the UAV identifier, and the configuration parameters received in step 1.
4. After successful execution of the flight path reporting configuration, the UAE server notifies the UAS application specific server with a Flight path reporting configuration complete.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.2.2 Real time flight path monitoring assistance configuration of UAE Client
|
This procedure enables the real time flight path monitoring assistance configuration of the UAE client, based on a request from UAS application specific server.
Figure 7.9.2.2-1 illustrates the procedure that enables configuration of the real time flight path monitoring assistance of the UAE Client.
Pre-conditions:
- The UAS UE is connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4].
- The UAE server has established a UAE session with the UAE client as the UAE client is successfully registered to the UAE server.
- The UAE server has performed the real time UAV flight path monitoring assistance procedure according to clause 7.9.2.1.
Figure 7.9.2.2-1: Real time flight path monitoring assistance configuration of UAE Client
1. The UAE server sends to the UAE client a Flight path reporting client configuration request including the UAS identifier, including QoS and QoE related triggering events (QoS thresholds, QoE thresholds, periodicity to collect QoS and QoE information), validity scope (flight path waypoints and/or geographical area, time). In case of complete removal of the flight path event, the request shall only include the UAS identifier.
2. The UAE client updates the flight path configuration as per the information received in step 1.
3. The UAE client sends to the UAE Server a Flight path reporting client configuration response.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.2.3 Real time flight path reporting procedure
|
This procedure illustrates the procedure where the UAE client processes the flight path event reporting received from a UAE server and sends to the UAS application specific server. The UAE server can provide flight path reports including associated UAV location information as the UAE server is informed by the UAE client, or in consolidated flight path report(s).
Figure 7.9.2.3-1 illustrates the procedure that reports real time flight path information from the UAE Client.
Pre-conditions:
- The UAE client has indicated support of real time UAV flight path monitoring assistance capability.
- The UAS application specific server has provided the real time UAV flight path monitoring assistance configuration to the UAE client.
Figure 7.9.2.3-1: Real time flight path reporting procedure
1. The UAE client detects event(s) for Uu or PC5 based on application layer experienced rules and thresholds as indicated from the flight path reporting configuration outlined in Figure 7.9.2.2-1, QoS thresholds, QoE thresholds, periodicity to collect QoS and QoE information, validity scope (flight path waypoints and/or geographical area, time).
2. The UAE client sends to the UAE server a Flight path event report including detected event(s) (e.g., low/high QoS and/or QoE). The UAE server records the event(s) with current timestamp.
3. The UAE server requests UAE client current location information from the SEAL location services. The UAE server records the received location information with current timestamp.
4. The UAE server sends to the UAS application specific server a Flight path event report notification. Based on the flight path reporting configuration, the UAE server may send the flight path information with location report information to the UAS application specific server when received, periodically or when the session with the UAE client end (e.g., when flight mission completes).
5. The UAS application specific server confirms with a Flight path event report notification acknowledgement to the UAE server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.1 Flight path reporting configuration request
|
Table 7.9.3.1-1 describes the flight path reporting configuration request from the UAS application specific server to the UAE server.
Table 7.9.3.1-1: Flight path reporting configuration request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the flight path reporting configuration. This ID can be the USS identifier, when the UAS application specific server is the USS.
UAS ID
M
The identification of the UAS for which the Flight path reporting configuration request applies. This could be in form of identifier for the UAS, e.g group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI
Parameters for Uu / PC5
O
Parameters for Uu and PC5
> QoS parameters
O
Parameters for flight path reporting configuration related with QoS (e.g., jitter, latency, throughput, error rate, packet loss).
- QoS thresholds
- QoS periodicity
> QoE parameters
O
Parameters for flight path reporting configuration related with QoE (e.g., distance and time deviation relative to the planned flight path).
- QoE thresholds
- QoE periodicity
> Time validity
O
Time validity where the flight path client configuration applies.
> List of waypoints
O
One or more waypoints along the flight path where the flight path client configuration applies.
> Geographical area
O
The area where the flight path client configuration applies. This can be geographical area, or topological area.
> Reporting frequency
O
Indication on how often the UAS application specific server would like to be reported. This can be event based and / or time based.
Parameters for PC5
O
Parameters for PC5. If this set is provided, the above parameters “Parameters for Uu / PC5” is only for Uu.
> QoS parameters
O
Parameters for flight path reporting configuration related with QoS (e.g., jitter, latency, throughput, error rate, packet loss).
- QoS thresholds
- QoS periodicity
> QoE parameters
O
Parameters for flight path reporting configuration related with QoE (e.g., distance and time deviation relative to the planned flight path).
- QoE thresholds
- QoE periodicity
> Time validity
O
Time validity where the flight path client configuration applies.
> List of waypoints
O
One or more waypoints along the flight path where the flight path client configuration applies.
> Geographical area
O
The area where the flight path client configuration applies. This can be geographical area, or topological area.
> Reporting frequency
O
Indication on how often the UAS application specific server would like to be reported. This can be event based and / or time based.
NOTE: If no flight path reporting configuration information is included, it indicates removal of a previously provided flight path reporting client configuration.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.2 Flight path reporting configuration response
|
Table 7.9.3.2-1 describes the flight path reporting configuration response from the UAE server to the UAS application specific server.
Table 7.9.3.2-1: Flight path reporting configuration response
Information element
Status
Description
Result
M
The positive or negative result of the flight path reporting configuration request.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.3 Flight path reporting configuration complete
|
Table 7.9.3.3-1 describes the information flow Flight path reporting configuration complete from the UAE server to the UAS application specific server.
Table 7.9.3.3-1: Flight path reporting configuration complete
Information element
Status
Description
Result
M
The positive or negative result of the flight path reporting configuration.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.4 Flight path reporting client configuration request
|
Table 7.9.3.4-1 describes the information flow flight path reporting client configuration request from the UAE server to the UAE client.
Table 7.9.3.4-1: Flight path reporting client configuration request
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the flight path reporting client configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
Parameters for Uu / PC5
O
Parameters for Uu and PC5
> QoS parameters
O
Parameters for flight path reporting configuration related with QoS (e.g., jitter, latency, throughput, error rate, packet loss).
- QoS thresholds
- QoS periodicity
> QoE parameters
O
Parameters for flight path reporting configuration related with QoE (e.g., distance and time deviation relative to the planned flight path).
- QoE thresholds
- QoE periodicity
> Time validity
O
Time validity where the flight path client configuration applies.
> List of waypoints
O
One or more waypoints along the flight path where the flight path client configuration applies.
> Geographical area
O
The area where the flight path client configuration applies. This can be geographical area, or topological area.
> Reporting frequency
O
Indication on how often the UAE server would like to be reported. This can be event based and / or time based.
Parameters for PC5
O
Parameters for PC5. If this set is provided, the above parameters “Parameters for Uu / PC5” is only for Uu.
> QoS parameters
O
Parameters for flight path reporting configuration related with QoS (e.g., jitter, latency, throughput, error rate, packet loss).
- QoS thresholds
- QoS periodicity
> QoE parameters
O
Parameters for flight path reporting configuration related with QoE (e.g., distance and time deviation relative to the planned flight path).
- QoE thresholds
- QoE periodicity
> Time validity
O
Time validity where the flight path client configuration applies.
> List of waypoints
O
One or more waypoints along the flight path where the flight path client configuration applies.
> Geographical area
O
The area where the flight path client configuration applies. This can be geographical area, or topological area.
> Reporting frequency
O
Indication on how often the UAE server would like to be reported. This can be event based and / or time based.
NOTE: If no flight path reporting client configuration information is included, it indicates removal of a previously provided flight path reporting client configuration.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.5 Flight path reporting client configuration response
|
Table 7.9.3.5-1 describes the information flow flight path reporting client configuration response from the UAE client to the UAE server.
Table 7.9.3.5-1: Flight path reporting client configuration response
Information element
Status
Description
Result
M
The positive or negative result of the flight path reporting client configuration
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.6 Flight path event report
|
Table 7.9.3.6-1 describes the information flow flight path event report from the UAE client to the UAE server.
Table 7.9.3.6-1: Flight path event report
Information element
Status
Description
Report
M
Indication of event-based, periodic or final flight part event report
> QoS event
O
Indication of QoS event(s).
> QoE event
O
Indication of QoE event(s).
> Waypoint event
O
Indication of waypoint event(s).
> Geographical event
O
Indication of geographical event(s).
> QoS event for PC5
O
Indication of QoS event(s).
> QoE event for PC5
O
Indication of QoE event(s).
> Waypoint event for PC5
O
Indication of waypoint event(s).
> Geographical event for PC5
O
Indication of geographical event(s).
NOTE: Zero, one or more of each of the events may be provided for Uu and/or PC5. If separate parameters for PC5 are provided, then separate events for PC5 are provided.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.9.3.7 Flight path event report notification
|
Table 7.9.3.7-1 describes the information flow flight path event report notification from the UAE server to the UAS application specific server.
Table 7.9.3.7-1: Flight path event report notification
Information element
Status
Description
Report
M
Indication of event-based, periodic or final flight part event report
> QoS event
O
Indication of QoS event(s).
> QoE event
O
Indication of QoE event(s).
> Waypoint event
O
Indication of waypoint event(s).
> Geographical event
O
Indication of geographical event(s).
> Time
O
Time of reception of the report(s) from the UAE client
> Location
O
Location of the UAE client when the report(s) from the UAE client was received by the UAE server
> QoS event for PC5
O
Indication of QoS event(s).
> QoE event for PC5
O
Indication of QoE event(s).
> Waypoint event for PC5
O
Indication of waypoint event(s).
> Geographical event for PC5
O
Indication of geographical event(s).
> Time for event for PC5
O
Time of reception of the report(s) from the UAE client
> Location of event for PC5
O
Location of the UAE client when the report(s) from the UAE client was received by the UAE server
NOTE: Zero, one or more of each of the events may be provided for Uu and/or PC5. If separate parameters for PC5 are provided, then separate events for PC5 are provided.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10 UAS provided flight routes
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.1 General
|
This feature enables the UAE server to provide possible fight path based on specific QoS requested from UTM or UAV. In particular, the UAE layer provides support for the flight route selection.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.2.1 Flight route support
|
Figure 7.10.2.1-1 describes the flight route support procedure.
Pre-conditions:
- UAV has performed the UAS UE registration procedure.
Figure 7.10.2.1-1: Flight route calculation procedure
1. The UAS application specific server or UAE client (UAV or UAV-C) sends flight route request towards the UAE server. This request contains network parameters needed for the specific needs of the specific use case (start point, destination point, specific times of start point and end point, needed QoS, link reliability, shortest route needed, etc).
2. The UAE server has the role of a route planning unit and based on the received end points and provisioned information (e.g., restricted areas, existing flight paths, available base stations coverage, shortest distance, shortest time duration) calculates possible waypoints as geographical coordinates and specific times.
3. The UAE server checks with NWDAF (via NEF) the QoS sustainability analytics (clause 6.9 of 3GPP TS 23.288 [15]) in these areas of interest/waypoints identified in step 2. Location information towards the NWDAF is presented as area of interest or path of interest and can reflect a list of waypoints. Based on the received information from NWDAF the UAE server selects waypoints (geographical coordinates and time) which KPIs map the requested criteria in step1.
4. The UAE server sends flight route reply with the selected waypoints in step 3 to the entity which has send the request (UTM, UAV or UAV-C).
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.3.1 Flight route request
|
Table 7.10.3.1-1 describes the information flow for the UAS application specific server or UAE client to request flight route from the UAE server.
Table 7.10.3.1-1: Flight route request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the flight route. This ID can be the USS identifier, when the UAS application specific server is the USS.
UAV ID
M
The identifier of the UAV/UAV-C (e.g. 3GPP UE ID or CAA level UAV ID) which requests the flight route.
Start point
M
Geographical coordinates of starting point
Start time
M
Time on which the UAV is at the starting point
Destination point
M
Geographical coordinates of destination point
Destination time
M
Time on which the UAV is at the destination point
Required minimum QoS
M
The needed QoS to support the flight mission.
Service availability
O
Percentage of needed service availability
Shortest route indicator
O
Indicator for a need of shortest route
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.10.3.2 Flight route reply
|
Table 7.10.3.2-1 describes the information flow for the UAS application specific server to reply with flight route the UAS application specific server or UAE client.
Table 7.10.3.2-1: Flight route response
Information element
Status
Description
Result
M
Result from the UAE server in response to flight route request indicating success or failure
List of waypoints
(NOTE)
O
List of waypoints containing geographical coordinates and time for each waypoint
NOTE: If Result IE indicates success, then List of waypoints IE provided by UAE server is present
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11 UAE layer support for NTZ
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.1 General
|
This feature enables the UAS application enablement services for assisting the UAS application with NTZ handling. The UAE layer provides support for the following operations:
- Support the management of NTZ between the UAS application specific server and UAE server as described in 7.11.2.1.
- Support the distribution of the NTZ application policy from UAS application specific server to the UAE server and the UAE client as described in clause 7.11.2.1 and 7.11.2.2.
- Support for informing the UAE server and UAS application specific server about NTZ status changes at the UAV as described in clause 7.11.2.3.
- Support the UAE layer assisted NTZ as described in clause 7.11.2.4.
- Support the UAE client in obtaining new NTZ information after changing USS as described in clause 7.11.2.5.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2 Procedures
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2.1 Management of NTZ support configuration
|
Figure 7.y.2.1-1 illustrates the NTZ support management procedure where the UAE server receives an application request for managing the NTZ application policy from the UAS application specific server.
Figure 7.11.2.1-1: NTZ support management procedure
1. The UAS application specific server sends to the UAE server a NTZ management request. The request includes the UASS identifier and the NTZ policy management container. If NTZ policy container is provided, the request shall include area for deactivating transmission, information about frequency bands and reporting configuration.
2. The UAE Server sends to the UAS application specific server a NTZ management response with a positive or negative acknowledgement of the request, based on capability of UAE server to undertake this task.
3. UAE server executes NTZ configuration according to clause 7.11.2.2.
4. After execution of NTZ configuration, the UAE server notifies the UAS application specific server with a NTZ management complete.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2.2 NTZ configuration
|
This procedure enables the configuration of the UAE Client, based on an application request from UAS application specific server (which can be the USS/UTM) to manage the NTZ for a UAS.
Figure 7.11.2.2-1 illustrates the NTZ configuration procedure.
Pre-conditions:
1. The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of 3GPP TS 23.256 [4].
2. UAE Server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server.
3. UAE Server has performed the NTZ management as in clause 7.11.2.1.
Figure 7.11.2.2-1: NTZ configuration
1. The UAE Server sends a NTZ configuration request including the UAS identifier. If the NTZ configuration is provided, the request shall include the area for deactivating transmission, frequency bands and reporting configuration. The UAE server configures all UAS UEs registered in the UAE server.
2. The UAE Client stores or removes the NTZ configuration parameters as per the information received in step 1.
3. The UAE Client sends a NTZ configuration response to the UAE Server.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2.3 NTZ activation by UAE Client
|
This procedure provides a mechanism for the UAE client to deactivate and activate its radio transmission in the respective frequency bands when entering or leaving the NTZ area based on the NTZ configuration as described in clause 7.11.2.2.
Figure 7.11.2.3-1 illustrates the NTZ activation.
Pre-conditions:
1. The UAE Clients are configured with a NTZ configuration as described in clause 7.11.2.2.
2. UAE Server has performed the NTZ management, as described in clause 7.11.2.1.
Figure 7.11.2.3-1: NTZ activation
1. UAE Clients (UAV and UAV-C) detect approaching area for deactivating transmission based on their NTZ configuration. Upon entering the NTZ area, the UAE client can switch to another frequency band or entirely stop its transmission depending on its available functionality and NTZ configuration.
2. The UAE Client sends a NTZ notification to the UAE Server indicating "NTZ imminent entry" and the time for switching off the needed frequency band and its location.
3. The UE clients stop its transmission.
4. The UAE Server forwards the NTZ notification to the UAS application specific server. It contains the UAS identity, the time for switching transmission off and location information of the UAS.
5. The UAE client detects it is out of the area for deactivating transmission and starts transmission.
6. The UAE client sends a NTZ notification to the UAE server indicating “NTZ exit” and the time for switching on the respective frequency band and its location.
7. The UAE Server forwards the NTZ notification to the UAS application specific server. It contains the UAS identity, the specific time when the transmission has been switched on and location information of the UAS.
8. In case that the UAE client has changed its USS according to clause 7.6 then:
9. UAE client requests new USS NTZ policy from the UAE server.
10. The UAE server replies with the new USS NTZ policy.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2.4 UAE-layer/SEAL/LMS assisted NTZ enforcement
|
This procedure provides a mechanism for supporting NTZ activation and deactivation based on usage of existing SEAL/LMS functionality for monitoring location deviation specified in clause 9.3.11 of 3GPP TS 23.434 [5]. The responsibility of following the NTZ policy is in UAV/UAV-C.
Figure 7.11.2.4-1 illustrates the procedure where the UAE server and SEAL/LMS support the assisted NTZ enforcement.
Pre-conditions:
1. UAE Server has performed the NTZ management, as described in clause 7.11.2.1.
2. UAE Server has subscribed for using SEAL/LMS services.
3. UAE Server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server.
Figure 7.11.2.4-1: UAE-layer/LMS assisted NTZ enforcement
1. The UAE server subscribes for monitoring of location deviation according to clause 9.3.2.11 of 3GPP TS 23.434 [5] using the identities of the UAE client successfully registered to the UAE server. The area of interest is the geographical area in which the no-transmit zone is active.
2. If one or more of the monitored UAE clients enter the area of interest, the LMS sends location area monitoring notification according to clause 9.3.2.16 of 3GPP TS 23.434 [5] containing the UAE client identifiers.
3. The UAE Server sends enforce NTZ request to the identified UAE clients entering the area of interest, indicating to stop transmission and containing information about the NTZ (area for deactivating the transmission, frequency bands, altitude). It is up to UAE client and UAV to switch its transmission on the specified NTZ frequency.
4. The UAE clients send enforce NTZ response to the UAE server indicating positive or negative result of the received request.
5. The UAE server sends NTZ notification towards the UAS application specific server. It contains the UAS identity, the specific time when the transmission has been switched off and location information of the UAS.
6. If one or more of the monitored UAE clients leaves the area of interest, the LMS sends location area monitoring notification according to clause 9.3.2.16 of 3GPP TS 23.434 [5] containing the UAE client identifiers.
7. The UAE Server sends enforce NTZ request to the identified UAE clients leaving the area of interest, indicating to start transmission.
8. The UAE clients send enforce NTZ response to the UAE server indicating positive or negative result of the received request.
9. The UAE server sends NTZ notification towards the UAS application specific server. It contains the UAS identity, the specific time when the transmission has been switched on and location information of the UAS.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.2.5 New USS NTZ policy
|
This procedure provides a mechanism for the UAE client to request a new NTZ policy when a change of USS happens.
Figure 7.11.2.5-1 illustrates the new NTZ policy.
Pre-conditions:
1. The UAE Clients are configured with a NTZ configuration as described in clause 7.11.2.2.
2. UAE Server has performed the NTZ management, as described in clause 7.11.2.1.
Figure 7.11.2.5-1: New NTZ policy
1. The UAE client has changed its USS according to the procedures described under clause 7.6.
2. UAE client requests new NTZ policy from the UAE server.
3. The UAE server replies with the new NTZ policy.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3 Information flows
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.1 NTZ management request
|
Table 7.11.3.1-1 describes the information flow NTZ management request from the UAS application specific server to the UAE server.
Table 7.11.3.1-1: NTZ management request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the NTZ management. This ID can be the USS identifier, when the UAS application specific server is the USS.
NTZ policy management container (see NOTE)
O
The NTZ policy management container consists of the requirements and policy for NTZ management.
> Area for deactivating transmission
M
The area where the NTZ management request applies. This can be geographical area, or topological area in which the no-transmit zone is active including specific altitude.
> Time period
M
The time period when the NTZ is valid.
> Frequency bands
M
The information for the frequency bands not allowed to be used in NTZ.
>Reporting configuration
M
The NTZ reporting configutation of the the UE, including the required reporting (e.g., prior to entering or after exiting or both) and the time interval for reporting.
NOTE: If NTZ policy management container is not included, it indicates removal of the NTZ policy management related information.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.2 NTZ management response
|
Table 7.11.3.2-1 describes the information flow NTZ management response from the UAE server to the UAS application specific server.
Table 7.11.3.2-1: NTZ management response
Information element
Status
Description
Result
M
The positive or negative result of the NTZ management request.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.3 NTZ management complete
|
Table 7.11.3.3-1 describes the information flow NTZ management complete from the UAE server to the UAS application specific server.
Table 7.11.3.2-1: NTZ management complete
Information element
Status
Description
Result
M
The positive or negative result of the NTZ configuration.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.4 NTZ configuration request
|
Table 7.11.3.4-1 describes the information flow NTZ configuration request from the UAE server to the UAE client.
Table 7.11.3.4-1: NTZ configuration request
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the NTZ configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
NTZ configuration (see NOTE)
O
NTZ configuration information to be configured at the UAS
> Area for deactivating transmission
M
The area where the NTZ management request applies. This can be geographical area, or topological area in which the no-transmit zone is active including specific altitude.
> Time period
M
The time period when the NTZ is valid.
> Frequency bands
M
The information for the frequency bands not allowed to be used in no-transmit zone.
>Reporting configuration
M
The NTZ reporting configuration of the UE, including the required reporting (e.g., prior to entering or after exiting or both) and the time interval for reporting.
NOTE: If NTZ configuration IE is not included, it indicates removal of the NTZ configuration at the UAS ID.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.5 NTZ configuration response
|
Table 7.11.3.5-1 describes the information flow NTZ configuration response from the UAE client to the UAE server.
Table 7.11.3.5-1: NTZ configuration response
Information element
Status
Description
Result
M
The positive or negative result of reception and storing or removal of the NTZ configuration parameters
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.6 NTZ notification
|
Table 7.11.3.6-1 describes the information flow NTZ notification.
Table 7.11.3.6-1: NTZ notification
Information element
Status
Description
UAS ID
M
The identification of the UAS. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
NTZ status
M
The status of the NTZ enforcement; the status can be "NTZ imminent entry" or "NTZ exit".
NTZ Transmission information
M
Indication for the transmission change; the information indicates whether the transmission is switched on or off and includes the frequency band information.
Time
M
The specific time when the notification is sent.
Location information
M
Location and altitude of the UAE client when the notification is sent.
NTZ enforcement time
O
The information about the NTZ enforcement time.
> estimated start time
(NOTE 1)
O
The time the NTZ enforcement is expected to start.
> estimated completion time (NOTE 1)
O
The time the NTZ enforcement is expected to end.
> actual completion time
(NOTE 2)
O
The time the NTZ enforcement completed.
NOTE 1: Mandatory if the NTZ status is for "NTZ imminent entry".
NOTE 2: Mandatory if the NTZ status is for "NTZ exit".
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.7 New NTZ policy request
|
Table 7.11.3.7-1 describes the information flow new NTZ policy request from the UAE client to the UAE server.
Table 7.11.3.7-1: New NTZ policy request
Information element
Status
Description
UAS ID
M
The identification of the UAS. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
Location information
M
Location and altitude of the UAE client when the request is sent.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.8 New NTZ policy response
|
Table 7.11.3.8-1 describes the information flow new NTZ policy response from the UAE server to the UAE client.
Table 7.11.3.8-1: New NTZ policy response
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the NTZ configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
NTZ configuration
O
NTZ configuration information to be configured at the UAS
> Area for deactivating transmission
M
The area where the NTZ management request applies. This can be geographical area, or topological area in which the no-transmit zone is active including specific altitude.
> Time period
M
The time period when the NTZ is valid.
> Frequency bands
M
The information for the frequency bands not allowed to be used in no-transmit zone.
>Reporting configuration
M
The NTZ reporting configuration of the UE, including the required reporting (e.g., prior to entering or after exiting or both) and the time interval for reporting.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.9 Enforce NTZ request
|
Table 7.11.3.9-1 describes the information flow enforce NTZ request from the UAE server to the UAE client.
Table 7.11.3.9-1: Enforce NTZ request
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the NTZ configuration request applies. This could be in form of identifier for the UAS, e.g. group ID; or collection of individual identifiers for the UAV and UAV-C, e.g. CAA level UAV ID, GPSI.
NTZ enforcement information (see NOTE)
O
NTZ enforcement information to be executed at the UAS
> Area for deactivating transmission
M
The area where the NTZ management request applies. This can be geographical area, or topological area in which the no-transmit zone is active.
>Altitude
M
Altitude range for the NTZ.
> Time
M
Specific time window for deactivating the transmission.
> Frequency bands
M
The information for the frequency bands not allowed to be used in no-transmit zone.
NOTE: If NTZ enforcement information IE is not included, it indicates removal of the NTZ enforcement at the UAS ID.
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
7.11.3.10 Enforce NTZ response
|
Table 7.11.3.10-1 describes the information flow enforce NTZ response from the UAE client to the UAE server.
Table 7.11.3.10-1: Enforce NTZ response
Information element
Status
Description
Result
M
The positive or negative result of the enforce NTZ request
|
19da2a74570834d986caa9f57137c28d
|
23.255
|
8 APIs
| |
19da2a74570834d986caa9f57137c28d
|
23.255
|
8.1 General
|
The following UAE capabilities are offered as APIs:
- UAE server APIs;
The following SEAL service APIs are specified in 3GPP TS 23.434 [5]:
- Group management server APIs;
- Location management server APIs;
- Configuration management server APIs;
- Identity management server APIs; and
- Key management server APIs.
The following SEAL service APIs are specified in 3GPP TS 23.435 [14]:
• Network slice optimization APIs based on VAL server policy,
When UAS application specific server invokes a SEAL server API directly, the UAS application specific server acting as VAL server shall interact with the corresponding SEAL server over the SEAL-S reference point for the API invocation request and response as specified in 3GPP TS 23.434 [5].
Requesting specific QoS per planned flight path/waypoint is available using Policy of needed minimum QoS per UE in the SS_NSCE_PolicyManagement API, see 3GPP TS 23.435 [14] clause 9.5.4.1.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.