8 APIs
23.2553GPPApplication layer support for Uncrewed Aerial System (UAS)Functional architecture and information flowsRelease 18TS
Editor’s Note: The additions to the API due to change of USS is FFS.
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.
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].
8.2 UAE server APIs
8.2.1 General
Table 8.2.1-1 illustrates the UAE server APIs.
Table 8.2.1-1: List of UAE server APIs
|
API Name |
API Operations |
Known Consumer(s) |
Communication Type |
|
UAE_C2OperationModeManagement API |
Manage_C2OperationMode |
UAS application specific server |
Request/ Response |
|
Notify_SelectedC2Mode (NOTE) |
UAS application specific server |
Subscribe/notify |
|
|
Notify_C2ModeSwitching (NOTE) |
UAS application specific server |
Subscribe/notify |
|
|
Notify_C2OperationModeManagementComplete (NOTE) |
UAS application specific server |
Subscribe/notify |
|
|
UAE_RealtimeUAVStatus API |
Subscribe_RealtimeUAVStatus |
UAS application specific server |
Subscribe/notify |
|
Unsubscribe_RealtimeUAVStatus |
UAS application specific server |
Subscribe/notify |
|
|
Notify_RealtimeUAVStatus |
UAS application specific server |
Subscribe/notify |
|
|
NOTE: The subscribe operation for Notify_C2OperationModeManagementComplete, Notify_SelectedC2Mode and Notify_C2ModeSwitching is part of Configure_C2OperationMode |
|||
8.2.2 UAE_C2OperationModeManagement API
8.2.2.1 General
API description: This API enables the UAS application specific server to communicate with the UAE server to send configurations for C2 operation modes for the UAS and receive notifications of the selected C2 communication modes from the UAS UEs (i.e. UAV, UAV-C).
8.2.2.2 Manage_C2OperationMode operation
API operation name: Manage_C2OperationMode
Description: Manage (initiate, change or delete) the configuration of the C2 operation modes for the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.4.3.1.
Outputs: Refer clause 7.4.3.2.
See clause 7.4.2.1 for the details of usage of this API operation.
8.2.2.3 Notify_SelectedC2Mode
API operation name: Notify_SelectedC2Mode
Description: Notification of the selected C2 communication modes from the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.4.3.10.
Outputs: Refer clause 7.4.3.11.
See clause 7.4.2.3 for the details of usage of this API operation.
8.2.2.4 Notify_C2ModeSwitching
API operation name: Notify_C2ModeSwitching
Description: Notification of the C2 communication mode switching from the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.4.3.5.
Outputs: Refer clause 7.4.3.6.
See clause 7.4.2.4 for the details of usage of this API operation.
8.2.2.5 Notify_C2OperationModeManagementComplete
API operation name: Notify_C2OperationModeManagementComplete
Description: Notification about the C2 operation mode management completion by UAE server.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.4.3.3.
Outputs: None.
See clause 7.4.2.1 for the details of usage of this API operation.
8.2.3 UAE_ RealtimeUAVStatus API
8.2.3.1 General
API description: This API enables the UAS application specific server to subscribe for and receive notifications for the realtime status information of the UAV.
8.2.3.2 Subscribe_RealtimeUAVStatus operation
API operation name: Subscribe_RealtimeUAVStatus
Description: Subscription for obtaining the realtime UAV status information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.5.3.2.
Outputs: Refer clause 7.5.3.3.
See clause 7.5.2.2 for the details of usage of this API operation.
8.2.3.3 Unsubscribe_RealtimeUAVStatus operation
API operation name: Unsubscribe_RealtimeUAVStatus
Description: Unsubscription for a existing subscription for obtaining the realtime UAV status information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.5.3.5.
Outputs: Refer clause 7.5.3.6.
See clause 7.5.2.4 for the details of usage of this API operation.
8.2.3.4 Notify_RealtimeUAVStatus operation
API operation name: Notify_RealtimeUAVStatus
Description: Notification of the realtime UAV status information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.5.3.4.
Outputs: None.
See clause 7.5.2.3 for the details of usage of this API operation.
Annex A (informative):
Support for edge deployments
The application architecture for supporting edge applications are specified in 3GPP TS 23.558 [7]. The UAS application layer as specified in clause 5 can be deployed in edge computing environment.
Figure A-1 illustrates a UAS application layer deployment in edge computing environments.
Figure A-1: UAS application layer deployment in edge computing environment
Figure A-1 illustrates how the UAS application architecture with EDGEAPP support for edge deployments can be deployed. In a UE, the UAS application specific client(s), UAE client and SEAL clients interact with the Edge Enabler Client (EEC) via EDGE-5 reference point in order to consume edge services. In an Edge Data Network (EDN), the UAS application specific server(s), UAE server and SEAL servers acting as Edge Application Server (EAS), interacts with the Edge Enabler Server (EES) via EDGE-3 reference point. The service provisioning and EAS discovery enable the UAS application layer entities in the UE to communicate with the application layer entities in the EDN. The interactions between the entities and 5GS are not shown for the sake of simplicity.
NOTE: This clause illustrates an example edge deployment using edge enabler layer. There can be other valid edge deployments enabled for UAS application layer.
Annex B (Informative):
Deployment models
B.1 General
This clause describes deployments of the functional model specified in clause 5. The reference points utilized from underlying 3GPP network as specified in clause 5.5 is represented as 3GPP interfaces in the deployment models.
NOTE: The representation of SEAL functionalities in the vertical deployment is specified in 3GPP TS 23.434 [5].
B.2 Deployment of UAE server
The UAE server deployments can be centralized and distributed.
B.2.1 Centralized deployments
A centralized deployment is where a single UAE server offers the UAE capabilities to one or more UAS application specific servers (e.g. USS/UTM). The UAE server and the UAS application specific server can be co-located in a single physical entity. The UAE server can be deployed either in the PLMN operator domain or deployed in the UAS operator domain. The UAE server connects with the 3GPP network systems (EPS, 5GS) in one or more PLMN operator domain. When UAE server and UAS application specific server are co-located in a single physical entity, the Us reference point between the UAE server and the UAS application specific server is not used.
Figure B.2.1-1 illustrates a deployment of the UAE server and the UAS application specific server in a single physical entity and deployed in UAS operator domain. The UAE server can be deployed in a separate physical entity from the UAS application specific server in the UAS operator domain. In such deployments, the Us reference point is used for the communication between the UAE server and the UAS application specific server.
Figure B.2.1-1: UAE server co-located with UAS application specific server in a single physical entity
Figure B.2.1-2 illustrates a deployment of the UAE server in the PLMN operator domain and the UAS application specific server in the UAS operator domain. The Us reference point is used for the communication between UAS application specific server and the UAE server. The UAE server can support multiple UAS application specific servers.
Figure B.2.1-2: UAE server deployed in the PLMN operator domain
Figure B.2.1‑3 illustrates a deployment of the UAE server which connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain. The UAE server can be co-located with the UAS application specific server in a single physical entity or deployed in different physical entities.
Figure B.2.1-3: Deployment of UAE server with connections to 3GPP network systems in multiple PLMN operator domains
Figure B.2.1‑4 illustrates a deployment of the UAE server which provides UAE capabilities to multiple UAS application specific servers over Us reference point and connects to the 3GPP network systems (EPS, 5GS) in multiple PLMN operator domain.
Figure B.2.1-4: Deployment of UAE server with connections to multiple UAS application specific servers
B.2.2 Distributed deployment
The distributed deployment is where multiple UAE servers are deployed either in the UAS operator domain or in the PLMN operator domain. The distributed deployment of the UAE servers provide geographical coverage or support multiple PLMN operator domains in a geographical location. The UAE servers interconnect via UAE-E and the Us reference point is used for interaction between UAS application specific server and the UAE server.
Figure B.2.2-1 illustrates the deployment of UAE servers in multiple PLMN operator domain and provides UAE capabilities to the UAS application specific server deployed in the UAS operator domain. The UAS application specific server connects via Us to the UAE servers.
Figure B.2.2-1: Distributed deployment of UAE servers in multiple PLMN operator domain without interconnection between UAE servers
Figure B.2.2-2 illustrates the deployment of multiple UAE servers deployed in multiple PLMN operator domains. The UAS application specific server connects via Us to the UAE server. The interconnection between UAE servers is via UAE-E and supports the UAS applications for the UAS UEs connected to the UAE servers in multiple PLMN operator domains.
Figure B.2.2-2: Distributed deployment of UAE servers in multiple PLMN operator domain with interconnection between UAE servers
Figure B.2.2-3 illustrates the deployment of multiple UAE servers in PLMN operator domain based on geographical coverage. The UAS application specific server connects via Us to the UAE server 1. The UAE servers interconnect via UAE-E and support the UAS communications to the UAS UEs (i.e., UAV, UAV-C) connected to the UAE servers.
Figure B.2.2-3: Distributed deployment of UAE servers in PLMN operator domain
Figure B.2.2-4 illustrates the deployment of multiple UAE servers in the UAS operator domain where UAE server 1 and UAE server 2 connect with 3GPP network system of PLMN operator domain 1 and PLMN operator domain 2 respectively. The UAS application specific server connects via Us to the UAE server 1. The UAE servers interconnect via UAE-E and support the UAS applications for the UAS UEs connected via both the PLMN operator domains.
Figure B.2.2-4: Distributed deployment of UAE servers in UAS operator domain
Annex C (informative):
Examples of usage of SEAL by UAS application specific server
All procedures of SEAL services (e.g. GMS, LMS) are available directly for usage by UAS application specific server. Some examples of the usage of SEAL by the UAS application specific server is illustrated below:
– Group creation procedures of Group Management server provides support for the UAS applications (e.g. paired UAV and UAV-C are grouped) to provide a dedicated group for the UAV and UAV-C to communicate with each other.
– The UAS application specific server (e.g. USS/UTM) monitors the presence of UAVs in a given geographic area by using the Monitoring Location Deviation procedure of the LM server.
– The UAS application specific server (e.g. USS/UTM) can directly fetch the multiple UAV related events from NRM server (e.g. to detect any events related to the UAV, the UAS application specific server can need multiple events related to the UAV (UE) from the 3GPP core network).
– The UAS application specific client and UAS application specific server can utilize the resource management procedures of the NRM server to manage unicast resources associated to SIP sessions.
Annex D (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2020-11 |
SA6#40-e |
TS skeleton approved in S6-202322 |
0.0.0 |
||||
|
2020-11 |
SA6#40-e |
Implementation of the following pCRs approved by SA6: S6-202204, S6-202324, S6-202354 |
0.1.0 |
||||
|
2021-01 |
SA6#41-e |
Implementation of the following pCRs approved by SA6: S6-210149, S6-210296, S6-210349 |
0.2.0 |
||||
|
2021-01 |
SA6#41-e |
Editorial correction of ref [3] specification number from 23.254 to 23.256. |
0.2.1 |
||||
|
2021-03 |
SA6#42-e |
Implementation of the following pCRs approved by SA6: S6-210555, S6-210556, S6-210718, S6-210719 |
0.3.0 |
||||
|
2021-04 |
SA6#42-BIS-e |
Implementation of the following pCRs approved by SA6: S6-211008, S6-211035, S6-211099, S6-211100, S6-211101, S6-211102, S6-211103, S6-211104, S6-211105 |
0.4.0 |
||||
|
2021-04 |
SA6#43-e |
Implementation of the following pCRs approved by SA6: S6-211254, S6-211304, S6-211308, S6-211311, S6-211363, S6-211364, S6-211365, S6-211366, S6-211386, S6-211458, S6-211459, S6-211460, S6-211461, S6-211462, S6-211463, S6-211468 |
0.5.0 |
||||
|
2021-06 |
SA#92-e |
SP-210471 |
Presentation for approval at SA#92-e |
1.0.0 |
|||
|
2021-06 |
SA#92-e |
SP-210471 |
MCC Editorial update for publication after TSG SA approval (SA#92) |
17.0.0 |
|||
|
2021-06 |
SA#92-e |
SP-210579 |
MCC Editorial update of the titles of the present document as well as ref [4] to align UAS terminology (SA#92) |
17.0.1 |
|||
|
2021-09 |
SA#93-e |
SP-210966 |
0003 |
1 |
F |
Correction of SEAL references |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0004 |
1 |
D |
Terminology alignment to use uncrewed |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0005 |
1 |
F |
Alignment with 5GC architecture |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0006 |
1 |
F |
Resolve EN about Geographical Area |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0007 |
F |
Alignment of text in clause 7.4.2.3 |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0008 |
F |
Correction to the UAV ID assignment assumption |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0009 |
F |
Correction to add the missing reference of UUAA 5GC procedure |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0010 |
F |
Correction to the UAV application message information flow |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0011 |
F |
Correction to the input and output of Notify C2 communication mode switching operation |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0012 |
1 |
F |
Correction to add the missing API operation for C2 operation mode configuration complete notification |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0013 |
1 |
F |
Correction about IP address use as UAV ID |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0014 |
1 |
F |
Correction to the usage of UAS ID |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0015 |
F |
Correction to the C2 operation mode switching confirmation |
17.1.0 |
|
|
2021-09 |
SA#93-e |
SP-210966 |
0016 |
1 |
F |
Correction to add the missing UAE layer registration procedure |
17.1.0 |
|
2021-09 |
SA#93-e |
SP-210966 |
0017 |
1 |
F |
Resolving the editor’s note regarding usage of realtime UAV status |
17.1.0 |
|
2021-12 |
SA#94-e |
SP-211528 |
0018 |
F |
Missing API on Realtime UAV status |
17.2.0 |
|
|
2021-12 |
SA#94-e |
SP-211528 |
0019 |
F |
Alignment of the term "USS/UTM" throughout TS 23.255 |
17.2.0 |
|
|
2021-12 |
SA#94-e |
SP-211528 |
0020 |
D |
Removal of Editor’s Note in Introduction |
17.2.0 |
|
|
2021-12 |
SA#94-e |
SP-211528 |
0021 |
F |
Missing IE for Realtime UAV status subscription request |
17.2.0 |
|
|
2021-12 |
SA#94-e |
SP-211528 |
0022 |
F |
Removal of Editor’s Notes in clause 5.2 |
17.2.0 |
|
|
2021-12 |
SA#94-e |
SP-211528 |
0023 |
1 |
F |
Removal of Editor’s Notes in clause 7.3 |
17.2.0 |
|
2022-03 |
SA#95-e |
SP-220104 |
0024 |
1 |
F |
Corrections for operations of C2 communication mode switching |
17.3.0 |
|
2022-03 |
SA#95-e |
SP-220104 |
0025 |
F |
Correction for realtime UAV status |
17.3.0 |
|
|
2022-12 |
SA#98-e |
SP-221237 |
0027 |
2 |
F |
Clarifications on usage of EDGE in Annex A |
17.4.0 |
|
2022-12 |
SA#98-e |
SP-221237 |
0028 |
F |
Removal of normative text in an informative annex |
17.4.0 |
|
|
2022-12 |
SA#98-e |
SP-221251 |
0026 |
1 |
B |
Requirements for support for multi-USS deployments |
18.0.0 |
|
2022-12 |
SA#98-e |
SP-221251 |
0029 |
1 |
B |
Additions to functional entities on support for multi-USS deployments |
18.0.0 |
|
2022-12 |
SA#98-e |
SP-221251 |
0030 |
1 |
B |
Addition of multi-USS capabilities to UAE layer registration |
18.0.0 |
|
2022-12 |
SA#98-e |
SP-221251 |
0031 |
2 |
B |
Addition of procedures for multi-USS configuration and support at change of USS |
18.0.0 |