Content for TS 23.255 Word version: 19.3.0
7.7 UAE layer support for DAA services and applications
7.7.1 General
7.7.2 Procedures
7.7.2.1 Configuration of DAA policies to the UAE layer and the UAS client
7.7.2.1.1 Management of DAA support configuration
7.7.2.1.2 DAA support configuration procedure
7.7.2.2 UAE layer support for DAA applications
7.7.2.2.1 DAA support involving UAVs with U2X support
7.7.2.2.2 DAA support involving UAVs without U2X support
7.7.3 Information flows
7.7.3.1 DAA support management request
7.7.3.2 DAA support management response
7.7.3.3 DAA support management complete
7.7.3.4 DAA support configuration request
7.7.3.5 DAA support configuration response
7.7.3.6 DAA client event information
7.7.3.7 DAA client event information acknowledge
7.7.3.8 DAA server event information
7.7.3.9 DAA server event information acknowledge
...
...
7.7 UAE layer support for DAA services and applications |R18| p. 60
7.7.1 General p. 60
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.
7.7.2 Procedures p. 60
7.7.2.1 Configuration of DAA policies to the UAE layer and the UAS client p. 60
7.7.2.1.1 Management of DAA support configuration p. 60
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:
- The UAV has received its UAS ID from the UAS application specific server.
- The UAV has performed the UAS UE registration procedure.
Step 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.
Step 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.
Step 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.
Step 4.
After execution of DAA configuration, the UAE server shall send a DAA support management complete to the UAS application specific server.
7.7.2.1.2 DAA support configuration procedure p. 61
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:
- The UAS UEs are connected to 5GS and authenticated and authorized by UAS application specific server as specified in clause 5.2 of TS 23.256.
- UAE server has established a UAE session with the respective UAE clients as the UAE clients are successfully registered to the UAE server.
- UAE server has performed the DAA support management procedure according to clause 7.7.2.1.1.
Step 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.
Step 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.
Step 3.
The UAE client shall send a DAA support configuration response to the UAE server.
7.7.2.2 UAE layer support for DAA applications p. 62
7.7.2.2.1 DAA support involving UAVs with U2X support p. 62
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:
- UAE server has provided the DAA application policy to the UAE client.
- The UAE client can communicate with the target UAVs using U2X communication.
Step 1.
The UAE layer has, e.g. based on information provided by the U2X layer, detected UAVs in proximity, see clause 5.6 of TS 23.256. 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.
Step 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.
Step 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.
Step 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.
Step 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.
7.7.2.2.2 DAA support involving UAVs without U2X support p. 62
Figure 7.7.2.2.2-1 illustrates the procedure with DAA support involving UAVs without U2X support.
Pre-conditions:
- UAS application specific server has provided DAA configuration parameters to the UAE client.
- The UAV does not support U2X layer.
Step 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.
Step 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.
Step 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 clause 9.3 of TS 23.434. 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.
Step 4.
The UAE client shall send to the UAE server a DAA server event information acknowledge.
Step 5.
The UAE server shall send a DAA server event information acknowledge to the UAS application specific server.
7.7.3 Information flows p. 63
7.7.3.1 DAA support management request p. 63
Table 7.7.3.1-1 describes the information flow DAA support management request from the UAS application specific server to the UAE server.
| 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. |
| The 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. |
7.7.3.2 DAA support management response p. 64
Table 7.7.3.2-1 describes the information flow DAA support management response from the UAE server to the UAS application specific server.
| Information element | Status | Description |
|---|---|---|
| Result | M | The positive or negative result of the DAA support management request. |
7.7.3.3 DAA support management complete p. 64
Table 7.7.3.3-1 describes the information flow DAA support management complete from the UAE server to the UAS application specific server.
| Information element | Status | Description |
|---|---|---|
| Result | M | The positive or negative result of provision of the DAA application policy to the UAS application. |
7.7.3.4 DAA support configuration request p. 64
Table 7.7.3.4-1 describes the information flow DAA support configuration request from the UAE server to the UAE client.
| 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. |
| The 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. |
7.7.3.5 DAA support configuration response p. 65
Table 7.7.3.5-1 describes the information flow DAA support configuration response from the UAE client to the UAE server.
| Information element | Status | Description |
|---|---|---|
| Result | M | The positive or negative result of provision of the DAA application policy to the UAS application. |
7.7.3.6 DAA client event information p. 65
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.
| 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. |
7.7.3.7 DAA client event information acknowledge p. 66
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.
| 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. |
7.7.3.8 DAA server event information p. 66
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.
| 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. |
7.7.3.9 DAA server event information acknowledge p. 67
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.
| Information element | Status | Description |
|---|---|---|
| Reason | M | Acknowledgement of DAA server event information. |
