hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.2 Rx | The reference point Rx supports the interactions between the UAS application server and the PCRF and is specified in 3GPP TS 29.214 [11]. The functions for Rx reference point are supported by the network resource management server of the SEAL. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.3 MB2-C | The reference point MB2-C supports the control plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 29.468 [12]. The functions for MB2-C reference point are supported by the network resource management server of the SEAL. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.4 MB2-U | The reference point MB2-U supports the user plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 29.468 [12]. The functions for MB2-U reference point are supported by the UAE server. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.5 xMB-C | The reference point xMB-C supports the control plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 26.346 [9]. The functions for xMB reference point are supported by the network resource management server of the SEAL. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.6 xMB-U | The reference point xMB-U supports the user plane interactions between the UAS application server and the BM-SC and is specified in 3GPP TS 26.346 [9]. The functions for xMB-U reference point are supported by the UAE server. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.7 T8 | The reference point T8 supports the interactions between the UAS application server and the SCEF and is specified in 3GPP TS 23.682 [8]. The functions of T8 interface are supported by UAE server and the functions related to location management of T8 are supported by the location management server. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.8 N5 | The reference point N5 supports the interactions between the UAS application server and the PCF and is specified in 3GPP TS 23.501 [6]. The functions of N5 interface are supported by UAE server. |
19da2a74570834d986caa9f57137c28d | 23.255 | 5.5.9 N33/Nnef | The reference point N33 supports the interactions between the UAS application server and the NEF and is specified in 3GPP TS 23.501 [6]. Nnef is the service based interface exposed by the NEF as per the N33 reference point. The functions of Nnef interface are supported by UAE server and the functions related to locatio... |
19da2a74570834d986caa9f57137c28d | 23.255 | 6 Identities | |
19da2a74570834d986caa9f57137c28d | 23.255 | 6.1 General | This clause describes the identities associated with the entities in the UAS application layer and used in this specification. |
19da2a74570834d986caa9f57137c28d | 23.255 | 6.2 UAV Identifier (UAV ID) | The UAV identifier is used to uniquely identify a UAV. The UAV ID is in the form of a 3GPP UE ID (e.g. GPSI, External Identifier) as specified in 3GPP TS 23.501 [6] or CAA level UAV ID as assigned by civil aviation authorities (e.g. FAA) via USS/UTM. |
19da2a74570834d986caa9f57137c28d | 23.255 | 6.3 UAS Identifier (UAS ID) | The UAS identifier is used to uniquely identify a pair of UAV and UAV-C collectively known as UAS. The UAS ID is in the form of a Group ID as specified in 3GPP TS 23.434 [5] or a collection of individual identifiers of the entities in the UAS (e.g. CAA level UAV IDs, 3GPP UE IDs). |
19da2a74570834d986caa9f57137c28d | 23.255 | 6.4 UAS Application Specific Server Identifier (UASS ID) | The UAS application specific server identifier is used to uniquely identify the UAS application specific server. The UASS ID is in the form of URI. |
19da2a74570834d986caa9f57137c28d | 23.255 | 6.5 UAE Server Identifier (UAE Server ID) | The UAE server identifier is used to uniquely identify the UAE server. The UAE Server ID is in the form of URI. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7 Procedures and information flows | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1 Usage of SEAL services | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.1 General | The UAE capabilities (UAE client and UAE server) utilize the SEAL services. Also the UAS application specific server(s) may directly utilize the SEAL services. All SEAL services specified in 3GPP TS 23.434 [5] are available to the UAS application layer (i.e. the UAE layer and the UAS application specific layer).
In thi... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.2 Group management service | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.2.1 General | The UAE capabilities (UAE client and UAE server) utilize the group management service procedures (e.g. creation, join, leave) of SEAL based on the group configuration information (e.g. group join policy, group leader) provided by the UAS application specific layer. The decisions and corresponding triggers (e.g. group c... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.2.2 Information flows | The following information flows of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- Group creation request specified in clause 10.3.2.1;
- Group creation response specified in clause 10.3.2.2;
- Group creation notification specified in clause 10.3.2.3;
- Gro... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.2.3 Procedures | The following procedures of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- Group creation specified in clause 10.3.3;
- Group information query specified in clause 10.3.4;
- Group membership specified in clause 10.3.5;
- Group configuration management spec... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.2.4 APIs | The following APIs of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- SS_GroupManagement API specified in clause 10.4.2; |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.3 Location management service | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.3.1 General | The UAE capabilities (UAE client and UAE server) utilize location management (e.g. network location of UEs) service procedures of SEAL to support UAS applications.
The UAS application specific server(s) may directly utilize the location management service procedures of SEAL. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.3.2 Information flows | The following information flows of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- Location reporting configuration request specified in clause 9.3.2.0;
- Location reporting configuration response specified in clause 9.3.2.1;
- Location information repor... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.3.3 Procedures | The following procedures of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- Event-triggered location reporting procedure specified in clause 9.3.3;
- On-demand location reporting procedure specified in clause 9.3.4;
- Location reporting event triggers co... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.3.4 APIs | The following APIs of location management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- SS_LocationReporting API as specified in clause 9.4.2;
- SS_LocationInfoEvent API as specified in clause 9.4.3;
- SS_LocationInfoRetrieval API as specified in clause 9.4.4;
- SS_Locati... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.4 Network resource management service | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.4.1 General | The UAE capabilities (UAE client and UAE server) and UAS application specific servers utilize network resource management service procedures of SEAL to support UAS applications and C2 communications.
The UAS application specific server(s) may directly utilize the network management service procedures of SEAL. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.4.2 Information flows | The following information flows of network resource management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the UAS applications:
- Network resource adaptation request specified in clause 14.3.2.1;
- Network resource adaptation response specified in clause 14.3.2.2;
- Resource request specified... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.4.3 Procedures | The following procedures of network resource management service of SEAL specified 3GPP TS 23.434 [5] are applicable for the UAS applications and C2 communications:
- Request for unicast resources at VAL service communication establishment specified in clause 14.3.3.2.1;
- Request for modification of unicast resources s... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.4.4 APIs | The following APIs of network resource management service of SEAL specified 3GPP TS 23.434 [5] are applicable for the UAS applications and C2 communications:
- SS_NetworkResourceAdaptation API specified in clause 14.4.2;
- SS_EventsMonitoring API specified in clause 14.4.3; |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.5 Network slice capability exposure service | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.5.1 General | The UAE capabilities (UAE client and UAE server) and UAS application specific servers utilize network slice capability exposure service procedures of SEAL to support UAS applications and C2 communications.
The UAS application specific server(s) may directly utilize the network slice capability exposure service procedur... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.5.2 Information flows | The following information flows of network slice capability exposure service of SEAL as specified in 3GPP TS 23.435 [14] are applicable for the UAS applications:
- VAL server policy provisioning request specified in clause 9.5.3.2;
- VAL server policy provisioning response specified in clause 9.5.3.3;
- VAL server poli... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.5.3 Procedures | The following procedures of network slice capability exposure service of SEAL specified 3GPP TS 23.435 [14] are applicable for the UAS applications and C2 communications:
- VAL server policy provisioning procedure specified in clause 9.5.2.1.1;
- VAL server policy update procedure specified in clause 9.5.2.1.2;
- VAL s... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.1.5.4 APIs | The following APIs of network slice capability exposure service of SEAL specified 3GPP TS 23.435 [14] are applicable for the UAS applications and C2 communications:
- SS_NSCE_PolicyManagement API specified in clause 9.5.4.1;
- SS_NSCE_NSOptimization API specified in clause 9.5.4.1;
- SS_NSCE_Policy_harmonization API sp... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2 Communications between UAVs within a geographical area | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2.1 General | This clause describes the procedure for communications between UAVs within a geographical area. The geographical area is from the perspective of the UAV initiating the communication with other UAVs.
The following transport mechanisms can be supported for communications between UAVs within a geographical area:
a. Using ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2.2 Procedures | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2.2.1 Communications between UAVs within a geographical area using unicast Uu | Figure 7.2.2.1-1 illustrates the procedure for communications between UAVs within a geographical area using unicast Uu.
Pre-conditions:
1. The UAE clients of UAVs have successfully registered and connected to the UAE server.
2. The SEAL's LM server information is configured at the UAE server.
Figure 7.2.2.1-1: Communic... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2.3 Information flows | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.2.3.1 UAV application message | Table 7.2.3.1-1 describes the information flow for the UAV application message from UAE client to UAE server and from UAE server to UAE client.
Table 7.2.3.1-1: UAV application message
Information element
Status
Description
UAV ID
M
The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) which initiates the UAV... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3 UAV and UAV-C Pairing and C2 QoS Provisioning using Group ID | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3.1 General | This clause describes the procedure for UAV and UAV-C grouping C2 QoS provisioning using subsequent group ID. It also provides the procedure for UAV replacement resulting in group ID update. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3.2 Procedures | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3.2.1 Procedure for group creation for one pair of UAV and UAV-C | Figure 7.3.2.1-1 illustrates a high-level procedure for group creation.
Pre-conditions:
- Both UAV-C and UAV have successfully registered and connected to the UAE server.
- A CAA level UAV ID is already assigned to the UAV-C and UAV.
Figure 7.3.2.1-1: Procedure for group creation for one pair of UAV and UAV-C
1. The UA... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3.2.2 Procedure for group-based approach for C2 QoS provisioning | Figure 7.3.2.2-1 illustrates a high-level workflow of group-based C2 QoS provisioning.
Pre-conditions:
- Both UAV and UAV-C have registered to 3GPP 5G network respectively. C2 communication is established.
- The procedure specified in clause 7.3.2.1 is performed and the group ID for the UAS group is available at the UA... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.3.3 Information flows | The usage of information flows between UAE server and SEAL's Group management Server is specified in clause 7.1.2.2.
The usage of information flows between UAE server and SEAL's Network Resource Management Server is specified in clause 7.1.4.2. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4 C2 Communication mode selection and switching | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.1 General | This feature introduces the UAS application enablement services for supporting the selection and re-selection of C2 communication modes. In particular, the UAE layer provides support for the following operations:
- Support the switch between two Network-Assisted C2 communications (via different subscriptions/networks) ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2 Procedures | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2.1 Management of C2 mode selection / switching capability | This procedure manages the C2 mode selection/switching capability at the UAE server, based on an application request from UAS application specific server (which can be the USS/UTM) to manage the C2 operation modes (direct, network-assisted, UTM-Navigated) of C2 communication for a UAS.
Figure 7.4.2.1-1 illustrates the ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2.2 C2 communication modes 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 C2 operation modes (direct, network-assisted, UTM-Navigated) of C2 communication for a UAS. For redundancy purposes, two links can be activated to wor... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2.3 C2 communication mode selection by UAE Client | This procedure provides a mechanism for the UAE client to select a primary C2 communication mode and optional secondary C2 communication mode based on C2 communication mode configuration enabled as described in clause 7.4.2.2. If two links are activated to work simultaneously or as active/standby, these links can belon... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2.4 UAE-layer assisted dynamic C2 mode switching | This procedure provides a mechanism for supporting dynamic switching between two Network-Assisted C2 communications (via different networks) or two UTM-Navigated C2 communications (via different networks) or between a direct and a network assisted C2 communication or between a direct/network-assisted and UTM-Navigated,... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.2.5 UAS application specific server triggered C2 communication mode switching | This procedure provides a mechanism for supporting dynamic switching between direct or network assisted C2 communications to UTM-Navigated, initiated by the UAS application specific server (which can be the USS/UTM) after detecting a C2 switching condition which may be required while the UAV enters a no-fly zone. For e... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3 Information flows | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.1 C2 operation mode management request | Table 7.4.3.1-1 describes the information flow C2 operation mode management request from the UAS application specific server to the UAE server.
Table 7.4.3.1-1: C2 operation mode management request
Information element
Status
Description
UASS ID
M
Identity of the UAS application specific server which requests the C2 ope... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.2 C2 operation mode management response | Table 7.4.3.2-1 describes the information flow C2 operation mode management response from the UAE server to the UAS application specific server.
Table 7.4.3.2-1: C2 operation mode management response
Information element
Status
Description
Result
M
The positive or negative result of the C2 operation mode management requ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.3 C2 operation mode management complete | Table 7.4.3.3-1 describes the information flow C2 operation mode management complete from the UAE server to the UAS application specific server.
Table 7.4.3.3-1: C2 operation mode management complete
Information element
Status
Description
Result
M
The positive or negative result of the C2 communication mode configurati... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.4 C2-related trigger event report | Table 7.4.3.4-1 describes the information flow C2-related trigger event report from the UAE client (of the UAV or the UAV-C) to the UAE server.
Table 7.4.3.4-1: C2-related trigger event report
Information element
Status
Description
UAE client ID
M
The identifier of the UAE client which indicates the QoS downgrade
UAS U... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.5 C2 mode switching confirmation request | Table 7.4.3.5-1 describes the information flow C2 mode switching confirmation request from the UAE server to the UAS application specific server.
Table 7.4.3.5-1: C2 mode switching confirmation request
Information element
Status
Description
UAE server ID
M
The identifier of the UAE server which requests the C2 mode swi... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.6 C2 mode switching confirmation response | Table 7.4.3.6-1 describes the information flow C2 mode switching confirmation response from the UAS application specific server (USS/UTM) to the UAE server.
Table 7.4.3.6-1: C2 mode switching confirmation response
Information element
Status
Description
Result
M
The positive or negative result of the C2 mode switching c... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.7 C2 operation mode switching | Table 7.4.3.7-1 describes the information flow C2 operation mode switching from the UAE server to the UAE client(s) of the affected UAS.
Table 7.4.3.7-1: C2 operation mode switching
Information element
Status
Description
UAE server ID
M
The identifier of the UAE server which instructs the UAS to apply the C2 mode switc... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.8 C2 communication modes configuration request | Table 7.4.3.8-1 describes the information flow C2 communication modes configuration request from the UAE server to the UAE client.
Table 7.4.3.8-1: C2 communication modes configuration request
Information element
Status
Description
UAS ID
M
The identification of the UAS for which the C2 QoS management request applies. ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.9 C2 communication modes configuration response | Table 7.4.3.9-1 describes the information flow C2 communication modes configuration response from the UAE client to the UAE server.
Table 7.4.3.9-1: C2 communication modes configuration response
Information element
Status
Description
Result
M
The positive or negative result of reception and storing or removal of the co... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.10 C2 communication mode notification | Table 7.4.3.10-1 describes the information flow C2 communication mode notification from the UAE client to the UAE server and from the UAE server to the UAS application specific server.
Table 7.4.3.10-1: C2 communication mode notification
Information element
Status
Description
UAS ID
M
The identification of the UAS. Thi... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.11 C2 communication mode notification acknowledgement | Table 7.4.3.11-1 describes the information flow C2 communication mode notification acknowledgement from the UAE server to the UAE client and from the UAS application specific server to the UAE server.
Table 7.4.3.11-1: C2 communication mode notification acknowledgement
Information element
Status
Description
Acknowledge... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.4.3.12 C2 operation mode switching performed | Table 7.4.3.12-1 describes the information flow C2 operation mode switching performed from the UAE client to the UAE server.
Table 7.4.3.12-1: C2 operation mode switching performed
Information element
Status
Description
Result
M
The result of the C2 mode switching |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5 Real-Time UAV Connection Status Monitoring and Location reporting | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.1 General | This clause enables the UAE server to provide a real-time view of UAV network status and location reporting based on current network connection status, in particular with the supporting of following use cases:
- Support of real-time monitor the 3GPP network connection with UAVs.
- Support of reporting of loss of commun... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.2 Procedures | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.2.1 Procedure for real-time UAV network connection status monitoring and location update | Figure 7.5.2.1-1 illustrates the real-time network monitoring and location update support for UAV operations.
Pre-conditions:
- UAE server has subscribed to the monitoring event API for connection monitoring by the NRM server for both UAV and/or UAV client as specified in clause 14.3.6.2.2 of 3GPP TS 23.434 [5].
- UAE ... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.2.2 Subscription for real-time UAV status information | Figure 7.5.2.2-1 describes the procedure for subscription for real-time UAV status information.
Pre-condition:
- UAS application specific server has been provisioned with UAE server information.
Figure 7.5.2.2-1: Subscription for real-time UAV status information
1. The UAE application specific server sends subscribe re... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.2.3 Notification of real-time UAV status information | Pre-conditions:
- UAS application specific server has performed subscription as per procedure in clause 7.5.2.2 with UAE server and the procedure for processing real-time UAV status as specified in clause 7.5.2.1 has performed.
Figure 7.5.2.3-1: Notification for real-time UAV status information
1. When real-time UAV st... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.2.4 Unsubscription for real-time UAV status information | Figure 7.5.2.4-1 describes the procedure for unsubscription for real-time UAV status information.
Pre-condition:
- UAS application specific server has performed the subscription procedure as specified in clause 7.5.2.2.
Figure 7.5.2.4-1: Unsubscription for real-time UAV status information
1. The UAE application specifi... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.3 Information flows | |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.3.1 Information flows between UAE server and SEAL servers | The usage of information flows between UAE server and SEAL's Location Management Server is specified in clause 7.1.3.2.
The usage of information flows between UAE server and SEAL's Network Resource Management Server is specified in clause 7.1.4.2. |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.3.2 Subscribe real-time UAV status information request | Table 7.5.3.2-1 describes the information flow for a UAS application specific server to subscribe to real-time UAV status information at the UAE server.
Table 7.5.3.2-1: Subscribe real-time UAV status information request
Information element
Status
Description
UASS ID
M
The identifier of the UAS application specific ser... |
19da2a74570834d986caa9f57137c28d | 23.255 | 7.5.3.3 Subscribe real-time UAV status information response | Table 7.5.3.3-1 describes the information flow for UAE server to respond for real-time UAV status subscription request from the UAS application specific server.
Table 7.5.3.3-1: Subscribe real-time UAV status information response
Information element
Status
Description
Result
M
Result from the UAE server in response to ... |
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 th... |
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 thi... |
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... |
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.
- Sup... |
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... |
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 ... |
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 ... |
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 ... |
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 suppor... |
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. ... |
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 for... |
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 ... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.