Content for TS 23.256 Word version: 19.0.0
1…
4…
4.2…
4.2.3…
4.3…
4.4…
4.5…
5…
5.2.3…
5.2.4…
5.2.5…
5.2.5.3…
5.2.5.4…
5.2.7
5.2.8…
5.2.9…
5.3…
5.4…
5.5…
5.12…
5.13…
5.14…
6…
6.2…
6.3…
6.3.4…
A…
4.4 High level function
4.4.1 Service Operations
4.4.1.1 NEF Services
4.4.1.1.1 General
4.4.1.1.2 Nnef_Authentication service
4.4.1.1.3 Nnef_UAVFlightAssistance service
4.4.1.2 AF Services
4.4.1.2.1 General
4.4.1.2.2 Naf_Authentication service
4.4.1.3 AMF Services
4.4.1.4 SMF Services
4.4.1.5 UDM Services
4.4.1.6 LMF Services
4.4.1.7 GMLC Services
4.4.1.8 UDR Services
4.4.1.9 PCF Services
4.4.2 USS Discovery
4.4.3 CAA-Level UAV ID Assignment
...
...
4.4 High level function p. 23
4.4.1 Service Operations p. 23
4.4.1.1 NEF Services p. 23
4.4.1.1.1 General p. 23
In addition to those defined in clause 7.2.8 of TS 23.501 and clause 5.2.6 of TS 23.502, the following Table illustrates additional NEF services to support UAS.
| Service Name | Service Operations | Operation Semantics | Example Consumer(s) |
|---|---|---|---|
| Nnef_ | AuthenticateAuthorize | Request/Response | AMF, SMF |
| Notification | Subscribe/Notify | AMF, SMF | |
| Nnef_ | Get | Request/Response | AF/USS |
| Create | Request/Response | AF/USS | |
| Update | Request/Response | AF/USS | |
| Notify | Request/Response | AF/USS |
4.4.1.1.2 Nnef_Authentication service p. 23
4.4.1.1.2.1 General p. 23
Service Description:
This service enables the consumer to either authenticate and authorise, or just authorize, the Service Level Device Identity. In case of UAS, the service is used to authenticate and/or authorize the UAV identified by a CAA-Level UAV ID.
When creating an authentication session, the AMF/SMF implicitly subscribes to NEF about notification related with the authentication/authorization (e.g. re-authenticate, update authorization data or revoke the UUAA authorization). This implicit subscription is implicitly released by UAS NF/NEF when the corresponding authentication association is removed (e.g. in the case of re-authentication failure and USS indicating to release network resource, or in the case of authorization revocation).
4.4.1.1.2.2 Nnef_Authentication_AuthenticateAuthorize service operation p. 23
Service operation name:
Nnef_Authentication_AuthenticateAuthorize
Description:
Provides the authentication and authorization result of the Service Level device Identity.
Input, Required:
Service Level Device Identity (i.e. CAA-Level UAV ID) for authentication, GPSI, NF Type.
Input, Conditional Required:
Notification endpoint (required for initial authentication request), DNN, S-NSSAI (in case the consumer NF is SMF).
Input, Optional:
Authorization Server Address (i.e. USS Address), PEI, UE IP address (in case the consumer NF is SMF), authentication/authorization container provided by UE, UAV location.
Output, Required:
None.
Output, Conditional Required:
Success/Failure indication [Not required when PDU Session Modification for C2 Communication], Authorization Data container, Indication whether the PDU sessions associated with the "DNN(s) subject to aerial services" can be released [Required for re-authentication failure].
Output, Optional:
None.
4.4.1.1.2.3 Nnef_Authentication_Notification service operation p. 23
Service operation name:
Nnef_Authentication_Notification
Description:
Re-authenticate, update authorization data or revoke the UUAA authorization of a UAV.
Input, Required:
Notification Correlation Information, Service Level Device Identity, 3GPP UAV ID, Notify reason (revoke, re-authentication, or authorization data update).
Input, Conditional Required:
Authorization Data container (if the Notify reason is authorization data update).
Input, Optional:
None.
Output, Required:
Acknowledge indication.
Output, Optional:
None.
4.4.1.1.3 Nnef_UAVFlightAssistance service |R19| p. 24
4.4.1.1.3.1 General p. 24
Service Description:
This service enables the consumer to request assistance for USS changeover if/when a UAV/UE moves from a geographical area served by one USS to an area served by another USS. For this purpose, a USS requests a core network to provide the assistance information for the serving USS, to inform the core network about the flight trajectory assigned and time schedule for the UAV/UE, and to receive notifications when the UAV/UE moves out/in the geographical area served by a USS triggering and completing the changeover.
4.4.1.1.3.2 Nnef_UAVFlightAssistance_Get service operation p. 24
Service operation name:
Nnef_UAVFlightAssistance_Get
Description:
Requesting from a NEF/UAS NF assistance with USS changeover.
Input, Required:
UAV's identifier (e.g. GPSI), indication about USS changeover.
Input, Optional:
List of addresses of suitable target USS, a list of candidate border-crossing point(s), acceptable deviations for flight plan/route, information about candidate flight path(s), requirements on the flight path as described in clause 5.13.
Output, Required:
None.
Output, Optional:
Pre-mission flight planning assistance information as described in clause 5.12.
4.4.1.1.3.3 Nnef_UAVFlightAssistance_Create service operation p. 24
Service operation name:
Input, Required:
Nnef_UAVFlightAssistance_Create
Description:
Providing a NEF/UAS NF information about the planned flight path(s) and a time schedule for the UAV from a starting point to a destination point (even when the destination point is located in geographical area served by different USS).
UAV's identifier (e.g. GPSI).
Input, Optional:
Flight path information, which may include e.g. a list of TA, UAV's speed, flight height/altitude and/or time schedule for crossing/spending at each of the TAs/cells).
Output, Required:
Flight plan configuration ID (associated with the changeover).
Output, Optional:
None.
4.4.1.1.3.4 Nnef_UAVFlightAssistance_Update service operation p. 25
Service operation name:
Nnef_UAVFlightAssistance_Update
Description:
Used by the service consumer to update the core network about changes in the previously provided UAV flight path(s) and/or time schedule.
Input, Required:
Flight plan configuration ID.
Input, Optional:
Flight path information, which may include e.g. a list of TA, UAV's speed, flight height/altitude and/or time schedule for crossing/spending at each of the TAs/cells).
Output, Required:
None.
Output, Optional:
None.
4.4.1.1.3.5 Nnef_UAVFlightAssistance_Notify service operation p. 25
Service operation name:
Nnef_UAVFlightAssistance_Notify
Description:
Notifying a USS about UAV leaving its serviced area and which border crossing point will be used for this purpose, informing a target USS about the UAV entering its serviced area, and confirming the completion of the changeover.
Input, Required:
Flight plan configuration ID, status of the UAV according to the assigned flight path (leaving, entering, deviating).
Input, Optional:
Information about border-crossing point that will be used for USS changeover.
Output, Required:
Indication whether the USS changeover is completed successfully when used by the target USS when responding to the notification.
Output, Optional:
None.
4.4.1.2 AF Services p. 25
4.4.1.2.1 General p. 25
In addition to the AF services defined in clause 7.2.19 of TS 23.501 and clause 5.2.19 of TS 23.502, the following Table shows the AF services to support UAS.
| Service Name | Service Operations | Operation Semantics | Example Consumer(s) |
|---|---|---|---|
| Naf_ | AuthenticateAuthorize | Request/Response | UAS NF/NEF |
| Notification | Subscribe/Notify | UAS NF/NEF |
4.4.1.2.2 Naf_Authentication service p. 25
4.4.1.2.2.1 General p. 25
Service Description:
This service enables the consumer to authenticate and authorize the Service Level Device Identity. In case of UAS, the service is used to authenticate and authorize the UAV identified by a CAA-Level UAV ID.
When creating an authentication session, the UAS NF/NEF implicitly subscribes to USS about notification related with the authentication/authorization (e.g. re-authenticate, update authorization data or revoke the UUAA authorization). This implicit subscription is implicitly released by USS when the corresponding authentication session is removed (e.g. in the case of re-authentication failure and USS indicating to release network resource, or in the case of authorization revocation).
4.4.1.2.2.2 Naf_Authentication_AuthenticateAuthorize service operation p. 25
Service operation name:
Naf_Authentication_AuthenticateAuthorize
Description:
Provides the Authentication and Authorization result of the Service Level Device Identity (i.e. CAA-Level UAV ID for UAS).
Input, Required:
Service Level Device Identity for authentication, GPSI.
Input, Optional:
Notification endpoint (required for initial authentication request), PEI, UE IP address, authentication container provided by UE, UAV location.
Output, Required:
None.
Output, Conditional Required:
Success/Failure indication and GPSI [Not required when PDU Session Modification for C2 Communication], Authorization Data container, Indication whether the UAS service related network resource can be released [Required for re-authentication failure]
Output, Optional:
None.
4.4.1.2.2.3 Naf_Authentication_Notification service operation p. 25
Service operation name:
Naf_Authentication_Notification
Description:
Re-authenticate, update authorization data or revoke the UUAA authorization of a UAV.
Input, Required:
Notification Correlation Information, Service Level Device Identity, GPSI, Notify reason (revoke, re-authentication, or authorization data update).
Input, Conditional Required:
Authorization Data container (if the Notify reason is authorization data update).
Input, Optional:
PDU Session IP address.
Output, Required:
Acknowledge indication.
Output, Optional:
None.
4.4.1.3 AMF Services p. 26
AMF services related to UAS are defined in clause 5.2.2 of TS 23.502.
In addition, when SMF invokes Namf_Communication_N1N2MessageTransfer service operation, it may provide the UUAA result to the UAV.
4.4.1.4 SMF Services p. 26
SMF services related to UAS are defined in clause 5.2.8 of TS 23.502.
4.4.1.5 UDM Services p. 26
UDM services related to UAS are defined in clause 5.2.3 of TS 23.502.
4.4.1.6 LMF Services p. 27
LMF services related to UAS are defined in clause 8.3 of TS 23.273.
4.4.1.7 GMLC Services p. 27
GMLC services related to UAS are defined in clause 8.4 of TS 23.273.
4.4.1.8 UDR Services p. 27
UDR services related to UAS are defined in clause 5.2.12 of TS 23.502.
4.4.1.9 PCF Services p. 27
PCF services related to UAS are defined in clause 5.2.5 of TS 23.502.
4.4.2 USS Discovery p. 27
There may be multiple USS(es) serving UASs in a country, and no direct association is expected between the 3GPP network serving a UAS and the USS providing services to the UAS. How the association between a UAV and a USS is realized, is outside the scope of 3GPP and is not related to the UAV subscription with the mobile operator.
In order to enable the interaction between the 3GPP network and the USS serving a UAS, the 3GPP network needs to discover the correct USS serving a specific UAV. This is required either during 5GS registration (when the UUAA is performed during 5GS registration), or during PDU session/PDN connection establishment.
It is assumed that mechanisms for resolution of CAA Level UAV ID to the USS serving the corresponding UAV, defined outside 3GPP, and available to entities outside the 3GPP system (e.g. the TPAE), are used in the 3GPP system to discover the USS for the UAV.
Optionally, the UAV may also provide to the 3GPP system, in addition to the CAA-level UAV ID, the USS address (USS IP address or USS FQDN) in order to discover the USS for the UAV. If the UAV is configured with multiple USS addresses per geographical area (i.e. either Pre-Configured or received from USS via NEF) then the UAV may provide the USS address of the corresponding geographical area based on UAV current location.
When the UAV provides the USS address (i.e. USS FQDN) separately from the CAA-Level UAV ID in UUAA-MM or UUAA-SM, the USS address (i.e. USS FQDN) shall be used to discover the USS. The USS address, when available, is used by the UAS NF in addition to CAA-Level UAV ID to discover a specific USS. If the UAS NF is configured with multiple USS addresses per geographical area (e.g. Pre-Configured) then UAS NF considers the location of the UAV (if available) to discover and select the correct USS.
4.4.3 CAA-Level UAV ID Assignment p. 27
The format of the CAA-Level UAV ID is defined outside 3GPP, however how such identity is used to enable a TPAE to query about UAV information is defined with respect to the 3GPP functionality.
In this release, the assignment of a CAA-level UAV ID for Remote Identification functionality applies solely to the UAV. No CAA-level UAV ID is assigned to and used by a UAVC.
Various formats of CAA-level UAV ID must be supported by the UAV to support various geo-specific regulations. At least Serial Number Identification, a CAA-Issued Registration Identifier (aka Session ID), and USS Issued UUID shall be supported.
In the case of Session ID, though the actual format of the CAA-Level UAV ID is defined outside 3GPP and is not decided by 3GPP, it is assumed that the CAA-Level UAV ID used for Remote Identification contains at least the following information:
- an identity unique to the UAV, which may preferably have temporary validity: this identifies uniquely the UAV with the entity that allocates the CAA-level UAV ID.
- CAA-level UAV ID Routing Information, used by an entity attempting to retrieve the UAV data (e.g. TPAE) to identify and address the appropriate UAS NF/NEF where to send the query. This is also used in USS discovery.
- USS-assigned CAA-Level UAV ID: the identity is assigned completely at USS level.
-
3GPP-assisted CAA-Level UAV ID assignment:
- The allocation to the UAV of a CAA-Level UAV ID by the USS is done in collaboration with the UAS NF, for the use by the UAV for UUAA, and for the use for Remote Identification.
- The USS interacts with the UAS NF to allocates the UAV identities to be used for Remote Identification (i.e. the CAA-Level UAV ID). When the UAV registers with the USS before registering to a 3GPP system for UAS services, the UAV operator provides information about the serving PLMN to the USS. In order to allocate a CAA-Level UAV ID, the USS interacts with a UAS NF if 3GPP Assisted CAA-Level UAV ID Assignment is desired. The 3GPP network selects a UAS NF to respond to the USS, and the UAS NF provides to the USS the CAA-Level Routing Information to enable a resolver of the CAA-level UAV ID to resolve to the UAS NF.
-
The USS delegates to the UAS NF the role of "resolver" of the CAA-Level UAV ID and return to an entity (e.g. the TPAE) querying information about the UAV based on the CAA-Level UAV ID the UAV data that the UAS NF retrieves from the USS.
- It is assumed that the mapping between USS assigned CAA-level UAV ID and the associated 3GPP UAV ID is known by the UAS NF after the UAV is authorized by the USS via a successful UUAA. If UAS NF receives a remote identification and tracking query from a TPAE with the USS-assigned CAA-Level UAV ID, the UAS NF uses the mapped 3GPP UAV ID to coordinate with different 3GPP functions to collect the UAV remote identification and tracking information. In addition, the UAS NF can retrieve aviation-level information (e.g. pilot information, USS operator, etc.) from the USS to provide it to the querying party (e.g. TPAE).
