hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.4.6 Notify_USSChangeTrigger | API operation name: Notify_USSChangeTrigger
Description: Notify a trigger event related to the recommended change of USS.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.6.3.9.
Outputs: None.
See clause 7.6.2.5 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5 UAE_DAASupport API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5.1 General | API description: This API enables the UAS application specific server to communicate with the UAE server for the DAA application policy and send and receive notifications related with DAA support aspects between the USS and the UAE client. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5.2 Manage_DAAManagement operation | API operation name: Manage_DAAManagement
Description: Manage (initiate, change or delete) configuration of the DAA application policy.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.7.3.1.
Outputs: Refer clause 7.7.3.2.
See clause 7.7.2.1.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5.3 Notify_DAAManagementComplete operation | API operation name: Notify_DAAManagementComplete
Description: Notification about the DAA management completion by UAE server.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.7.3.3.
Outputs: None.
See clause 7.7.2.1.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5.4 Notify_DAAClientSupportEvent operation | API operation name: Notify_DAAClientSupportEvent
Description: Notification about possible UAVs in proximity, identified by the client.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.7.3.6.
Outputs: Refer clause 7.7.3.7.
See clause 7.7.2.2.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.5.5 Manage_DAAServerSupportEvent operation | API operation name: Manage_DAAServerSupport
Description: Notification about possible UAVs in proximity, identified by the server.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.7.3.8.
Outputs: Refer clause 7.7.3.9.
See clause 7.7.2.2.2 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.6 UAE_UAVDynamicInfo API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.6.1 General | API description: This API enables the UAS application specific server to subscribe for and receive notifications for the host UAV dynamic information. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.6.2 Subscribe_UAVDynamicInfo operation | API operation name: Subscribe_UAVDynamicInfo
Description: Subscription for obtaining the UAV dynamic information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.8.3.1.
Outputs: Refer clause 7.8.3.2.
See clause 7.8.2.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.6.3 Unsubscribe_UAVDynamicInfo operation | API operation name: Unsubscribe_UAVDynamicInfo
Description: Unsubscription for a existing subscription for obtaining the UAV dynamic information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.8.3.5.
Outputs: Refer clause 7.8.3.6.
See clause 7.8.2.x for the details of usage of this API operati... |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.6.4 Notify_UAVDynamicInfo operation | API operation name: Notify_UAVDynamicInfo
Description: Notification of the UAV dynamic information.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.8.3.4.
Outputs: None.
See clause 7.8.2.4 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.7 UAE_FlightPathMonitoring API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.7.1 General | API description: This API enables the UAS application specific server to communicate with the UAE server to send information related to real time flight path monitoring for the UAS and receive notifications from the UAS UEs (i.e. UAV) about real time flight path monitoring. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.7.2 Manage_FlightPathReportingConfiguration | API operation name: Manage_FlightPathReportingConfiguration
Description: Manage (initiate, change or delete) the configuration of the real time flight path monitoring for the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.9.3.1.
Outputs: Refer clause 7.9.3.2.
See clause 7.9.2.1 for th... |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.7.3 Notify_FlightPathReportingConfigurationComplete | API operation name: Notify_FlightPathReportingConfigurationComplete
Description: Notification about the real time flight path monitor completion by UAE server.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.9.3.3.
Outputs: None.
See clause 7.9.2.1 for the details of usage of this API operation... |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.7.4 Notify_FlightPathEventReport | API operation name: Notify_FlightPathEventReport
Description: Notification of the real time flight path monitoring from the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.9.3.7.
Outputs: Refer clause 7.9.3.8.
See clause 7.9.2.3 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.8 UAE_FlightRouteSupport API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.8.1 General | API description: This API enables the UAS application specific server or the UAE client to communicate with the UAE server to send information related to creating flight path for the UAS and receive response from the UAE server containing list of waypoints which support the requested QoS and service availability. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.8.2 Manage_QoSFlightRoutePlan | API operation name: Manage_QoSFlightRoutePlan
Description: Request the flight route for the UAS UEs based on needed QoS and service availability.
Known Consumers: UAS application specific server or UAE client.
Inputs: Refer clause 7.10.3.1.
Outputs: Refer clause 7.10.3.2.
See clause 7.10.2.1 for the details of usage of... |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9 UAE_NTZ management API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9.1 General | API description: This API enables the UAS application specific server to communicate with the UAE server to send configurations for NTZ management. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9.2 Manage_NTZ | API operation name: Manage_NTZ
Description: Manage the configuration of the NTZ for the UAS UEs.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.11.3.1.
Outputs: Refer clause 7.11.3.2.
See clause 7.11.2.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9.3 Notify_ NTZManagementComplete | API operation name: Notify_ NTZManagementComplete
Description: Notification about the NTZ management completion by UAE server.
Known Consumers: UAS application specific server.
Inputs: Refer clause 7.11.3.3.
Outputs: None.
See clause 7.11.2.1 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9 UAE_NTZ configuration API | 8.2.9.1 General
API description: This API enables the UAE server to communicate with the UAE client to send configuration about NTZ. This API enables the UAE client to notify the UAE server and the UAE server to notify the UAS application specific server about NTZ status changes in the UAE client. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9.2 Configure_NTZ | API operation name: Configure_NTZ
Description: Configure NTZ in UAE client.
Known Consumers: UAE server.
Inputs: Refer clause 7.11.3.4.
Outputs: Refer clause 7.11.3.5.
See clause 7.11.2.2 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.9.3 Notify_NTZ | API operation name: Notify_NTZ
Description: Notify of NTZ status changes in the UAE client.
Known Consumers: UAE server, UAS application specific server.
Inputs: Refer clause 7.11.3.6.
Outputs: None.
See clause 7.11.2.3 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.10 UAE_NTZ enforce API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.10.1 General | API description: This API enables the UAE server to communicate with the UAE client to send enforced configuration on NTZ. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.10.2 Enforce_NTZ | API operation name: Enforce_NTZ
Description: Enforce NTZ in UAE client.
Known Consumers: UAE server.
Inputs: Refer clause 7.11.3.9.
Outputs: Refer clause 7.11.3.10.
See clause 7.11.2.4 for the details of usage of this API operation. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.11 UAE_newNTZ policy API | |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.11.1 General | API description: This API enables the UAE client to communicate with the UAE server to obtain a new NTZ policy. |
19da2a74570834d986caa9f57137c28d | 23.255 | 8.2.11.2 NewPolicy_NTZ | API operation name: NewPolicy_NTZ Description: Configure new NTZ policy in UAE client. Known Consumers: UAE client. Inputs: Refer clause 7.11.3.7. Outputs: Refer clause 7.11.3.8. See clause 7.11.2.5 for the details of usage of this API operation. Annex A (informative): Support for edge deployments The application archi... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 1 Scope
| The present document specifies architecture enhancements for supporting Uncrewed Aerial Systems (UAS) connectivity, identification and tracking, according to the use cases and service requirements defined in TS 22.125 [5].
The following functions are specified:
- UAV Identification, authentication and authorization.
... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 3 Definitions and abbreviations
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] or TS 23.501 [2].
3GPP UAV ID: Identifier assigned by the 3GPP system and used by ex... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
A2X Aircraft-to-Everything
AAM Area Airspace Manager
BRID Broadcast Remo... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4 Architecture model and concepts
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.1 General concept
| The architecture enhancements for UAVs introduce the following functionalities:
- Authentication and authorization of a UAV with the USS during 5GS registration (optional).
- Authentication and authorization of a UAV with the USS during PDU session establishment and PDN connection establishment.
- Support for USS au... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2 Architectural reference model
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.1 General
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.1.1 Support for general UAV features
| This specification covers UAV functionality provided by 5GC connected to NG-RAN and EPC connected to LTE.
The following functionality is defined for UAV support in the 3GPP system:
- An UAV is authenticated and authorized by USS via a USS UAV Authentication & Authorization (UUAA) with the support of the 3GPP system b... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.1.2 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.2 Logical UAV Reference Architecture
|
Figure 4.2.2-1: Logical 5GS and EPS architecture for UAV
NOTE 1: Provisioning of UAS services over EPC is based on the use of an SMF+PGW-C node.
Figure 4.2.2-2: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN
Figure 4.2.2-3: Local breakout roaming architecture for interworking between 5GS... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.3 5GS Non-roaming Reference Architecture
|
Figure 4.2.3-1: 5G System non-roaming architecture for UAVs and for A2X communication over PC5 and Uu reference points
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.4 5GS Roaming Reference Architecture
|
Figure 4.2.4-2: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - local breakout scenario in service-based interface representation
Figure 4.2.4-2: Roaming 5G System architecture for UAVs and for A2X communication over PC5 and Uu reference points - Home routed sce... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.5 Service-based interfaces
| The 5G System Architecture for UAVs contains the service-based interfaces defined in TS 23.501 [2], with the following differences:
Nudm: In the case of A2X Service, services provided by UDM are used to get A2X Service related subscription information to AMF during Initial registration procedure or UE Configuration Up... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.2.6 Reference points
| The 5G System Architecture for UAV contains the reference points defined in TS 23.501 [2]. In addition, the reference points of TS 23.287 [11] apply, with the following differences:
A2X1: The reference point between the A2X applications in the UAV UE and in the UAV-C and the A2X Application Server. This reference poin... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3 Functional entities
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.1 General
| In addition to the 5GS functional entities defined in TS 23.501 [2] and the EPS functional entities defined in TS 23.401 [6], the following functional entities are defined for UAS.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.2 UAS NF
| The UAS Network Function is supported by the NEF or SCEF+NEF and used for external exposure of services to the USS. The UAS-NF makes use of existing NEF/SCEF exposure services for UAV authentication/authorization, for UAV flight authorization, for UAV-UAVC pairing authorization and related re-authentication/re-authoriz... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.3 UAV
| The UAV is a 3GPP UE supporting the UE functionality defined in TS 23.401 [6] and in TS 23.501 [2].
In addition:
- a UAV that is configured for UAS services is provisioned with a single CAA-Level UAV ID;
- a UAV that is configured for UAS services (i.e. is provisioned with a CAA-Level UAV ID) registers to the 3GPP s... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.4 AMF
| In addition to the functionality defined in TS 23.501 [2], the AMF:
- may trigger the UUAA-MM procedure for a UE requiring UAV authentication and authorization by a USS when registering with 5GS when the UE has Aerial UE subscription information and based on local operator policy, or when the USS that authenticated th... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.5 SMF
| In addition to the functionality defined in TS 23.501 [2], the SMF:
- triggers the UUAA-SM procedure for a UE requiring UAV authentication and authorization by a USS when requesting user plane resources for UAV operation, or when the USS/UTM that authenticated the UAV triggers a re-authentication;
- may trigger the a... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.6 SMF+PGW-C
| The SMF+PGW-C implements the functions of the SMF described in clause 4.3.5.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.7 PCF
| In addition to the functions defined in TS 23.501 [2], the PCF includes the functions described in 23.287 [11] to provision the UE and AMF with necessary parameters in order to use A2X communication.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.8 UDM
| In addition to the functions defined in TS 23.501 [2], the UDM performs subscription management for A2X communication over PC5 reference point.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.9 A2X Application Server
| The A2X Application Server implements a subset of the V2X AS functionality specified in clause 4.4.3 of TS 23.287 [11]:
- includes AF functionality and may support at least the following capabilities:
- For A2X service parameters provisioning, the A2X AS provides the 5GC and the UAV UE (possibly via the UAVC) with pa... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.10 UDR
| In addition to the functions defined in TS 23.501 [2], the UDR stores A2X service parameters.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.3.11 NRF
| In addition to the functions defined in TS 23.501 [2], the NRF performs PCF discovery by considering A2X capability.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4 High level function
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1 Service Operations
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1 NEF Services
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.1 General
| In addition to those defined in TS 23.501 [2] clause 7.2.8 and TS 23.502 [3] clause 5.2.6, the following table illustrates additional NEF services to support UAS.
Table 4.4.2.1.1-1: NF Services provided by NEF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Nnef_Authentication
Authentica... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.2 Nnef_Authentication service
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.2.1 General
| 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 implicit... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.2.2 Nnef_Authentication_AuthenticateAuthorize service operation
| 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... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.2.3 Nnef_Authentication_Notification service operation
| Service operation name: Nnef_Authentication_Notification
Description: Re-authenticate, update authorization data or revoke the UUAA authorization of a UAV.
NOTE: This notification corresponds to an implicit subscription by Nnef_Authentication_AuthenticateAuthorize service operation.
Input, Required: Notification Cor... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3 Nnef_UAVFlightAssistance service
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3.1 General
| 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 with the USS changeover, to inform the core networ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3.2 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3.3 Nnef_UAVFlightAssistance_Create service operation
| Service operation name: 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 next point in the flight path (even when the next point is located in geographical area served by different USS) or providi... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3.4 Nnef_UAVFlightAssistance_Update service operation
| Service operation name: Nnef_UAVFlightAssistance_Update
Description: The consumer can use this service operation to delete/update its previously provided information about UAV flight path(s) and/or time schedule and to cancel the associated subscriptions, when, for instance, the serving USS determines that it does not... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.3.5 Nnef_UAVFlightAssistance_Notify service operation
| 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, notifying the USS abou... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.4 Nnef_RetrieveInfoUAVFlight_Get service
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.4.1 General
| Service Description: This service enables the consumer (i.e. USS) to request the 5GC to collect data from NFs to be used by the USS for UAV's flight planning and assistance purposes, for instance, USS changeover and/or pre-flight planning. This service also enables the UAS NF/NEF to trigger the UAV's altitude reporting... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.1.4.2 Nnef_RetrieveInfoUAVFlight_Get service operation
| Service operation name: Nnef_RetrieveInfoUAVFlight_Get
Description: Requesting from a NEF/UAS NF to retrieve data from 5GC NFs that can be used by USS for UAV's flight purposes, notifying the USS about the altitude reporting.
Input, Required: UAV's identifier (e.g. GPSI), indication about the purpose of the retrieved... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2 AF Services
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2.1 General
| In addition to the AF services defined in TS 23.501 [2] clause 7.2.19 and TS 23.502 [3] clause 5.2.19, the following table shows the AF services to support UAS.
Table 4.4.1.2.1-1: NF Services provided by AF
Service Name
Service Operations
Operation
Semantics
Example Consumer(s)
Naf_Authentication
AuthenticateAu... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2.2 Naf_Authentication service
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2.2.1 General
| 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 ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2.2.2 Naf_Authentication_AuthenticateAuthorize service operation
| 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 (req... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.2.2.3 Naf_Authentication_Notification service operation
| Service operation name: Naf_Authentication_Notification
Description: Re-authenticate, update authorization data or revoke the UUAA authorization of a UAV.
NOTE: This notification corresponds to an implicit subscription by Naf_Authentication_AuthenticateAuthorize service operation.
Input, Required: Notification Corre... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.3 AMF Services
| AMF services related to UAS are defined in TS 23.502 [3] clause 5.2.2.
In addition, when SMF invokes Namf_Communication_N1N2MessageTransfer service operation, it may provide the UUAA result to the UAV.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.4 SMF Services
| SMF services related to UAS are defined in TS 23.502 [3] clause 5.2.8.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.5 UDM Services
| UDM services related to UAS are defined in TS 23.502 [3] clause 5.2.3.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.6 LMF Services
| LMF services related to UAS are defined in clause 8.3 and clause 4.3.8 of TS 23.273 [8] and clause 4.3.8 of TS 23.586 [25].
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.7 GMLC Services
| GMLC services related to UAS are defined in clause 8.4 and clause 4.3.3 of TS 23.273 [8] and clause 4.3.9 of TS 23.586 [25].
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.8 UDR Services
| UDR services related to UAS are defined in clause 5.2.12 of TS 23.502 [3].
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.1.9 PCF Services
| PCF services related to UAS are defined in clause 5.2.5 of TS 23.502 [3].
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.2 USS Discovery
| 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... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.4.3 CAA-Level UAV ID Assignment
| 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 CA... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.5 Identifiers
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.5.1 General
| The UAV is associated with the following identifiers in the 3GPP system.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.5.2 CAA-Level UAV Identity
| A UAV is assigned a CAA-level UAV Identity by functions in the aviation domain (e.g. USS). This assigned identity is used for Remote Identification and Tracking and to identify the UAV.
The UAV provides the CAA-level UAV Identity to the 3GPP system during UUAA procedures.
The CAA-level UAV Identity is used by the UAV... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 4.5.3 3GPP UAV ID
| A 3GPP UAV ID is associated to the UAV by the 3GPP system in the subscription information and is used by the 3GPP system to identify the UAV. GPSI in the format of External Identifier is used as the 3GPP UAV ID.
The USS stores the association of the CAA-level UAV ID (provided by the UAV or a new one allocated by the a... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5 Functional description and information flows
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.1 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2 UAV Authentication and Authorization
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.