hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 operation. |
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 the details of usage of this API operation. |
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 this API operation. |
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 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 can be deployed with the application architecture for supporting edge applications. 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 2022-03 SA#99 SP-230277 0033 2 A Correction of various inconsistencies and unclarities 18.1.0 2022-03 SA#99 SP-230297 0034 2 B Addition of IEs to messages related with change of USS 18.1.0 2022-03 SA#99 SP-230297 0035 1 B Addition of API for change of USS 18.1.0 2022-03 SA#99 SP-230297 0036 2 B Requirements for support for DAA 18.1.0 2022-03 SA#99 SP-230297 0037 4 B Additions to functional entities on support for DAA deployments 18.1.0 2022-03 SA#99 SP-230297 0038 1 B Addition of DAA assist capability to UAE layer registration 18.1.0 2022-03 SA#99 SP-230297 0039 4 B Addition of procedures for DAA configuration 18.1.0 2022-03 SA#99 SP-230297 0040 2 B Addition of API for DAA 18.1.0 2022-03 SA#99 SP-230297 0041 1 B Support the USS re-mapping for a UAS 18.1.0 2022-03 SA#99 SP-230297 0042 1 B Enhancements to Realtime UAVs status for DAA support 18.1.0 2022-03 SA#99 SP-230297 0043 2 B Tracking UAVs in an application defined area for DAA support 18.1.0 2023-06 SA#100 SP-230715 0044 F Removal of Editor’s Note on multi-USS 18.2.0 2023-06 SA#100 SP-230715 0045 F Removal of Editor’s Note on DAA 18.2.0 2023-06 SA#100 SP-230715 0046 3 B Support for C2 direct mode availability reporting 18.2.0 2023-06 SA#100 SP-230715 0047 1 B Unsubscribe UAV dynamic information 18.2.0 2023-06 SA#100 SP-230715 0048 B UAV dynamic information API 18.2.0 2023-12 SA#102 SP-231573 0049 1 B Improved redundancy for command and control (C2) traffic 19.0.0 2024-03 SA#103 SP-240321 0050 4 B Support for real time UAV flight path monitoring assistance 19.1.0 2024-03 SA#103 SP-240321 0052 2 B Require QoS along UAV planned flight path 19.1.0 2024-03 SA#103 SP-240321 0053 1 B Simultaneous link support for UTM-Navigated C2 and clarifications 19.1.0 2024-06 SA#104 SP-240770 0054 2 B Assist selecting UAV flight path based on QoS 19.2.0 2024-06 SA#104 SP-240770 0055 2 B Support for DAA ground-based UAE layer assistance 19.2.0 2024-09 SA#105 SP-241231 0056 1 B Flight route selection support API 19.3.0 2024-09 SA#105 SP-241231 0057 D Editorial corrections 19.3.0 2024-12 SA#106 SP-241732 0059 1 B No-transmit zones configuration and execution for UAS 19.4.0 2024-12 SA#106 SP-241732 0061 F Alignment and work completion 19.4.0 2024-12 SA#106 SP-241732 0062 F Clarifications to real time UAV flight path monitoring assistance 19.4.0 |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
- UAV tracking in the 3GPP system:
- this includes how the 3GPP system can provide support for UAV to ground identification (e.g. to authorized third parties such as police devices).
- handling of unauthorized UAVs and revocation of authorization.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)".
[3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)".
[4] 3GPP TS 23.222: "Common API Framework for 3GPP Northbound APIs".
[5] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP".
[6] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[7] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[8] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[9] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[10] 3GPP TS 33.256: "Security aspects of Uncrewed Aerial Systems (UAS)".
[11] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[12] 3GPP TS 23.285: "Architecture enhancements for V2X services".
[13] ASTM F3411.19: "Standard Specification for Remote ID and Tracking".
[14] ASD-STAN prEN 4709-002:2022-03: "Aerospace series - Unmanned Aircraft Systems - Part 002: Direct Remote Identification".
[15] 3GPP TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2".
[16] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[17] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[18] 3GPP TS 26.502: "5G multicast-broadcast services; User Service architecture".
[19] 3GPP TS 26.517: "5G Multicast-Broadcast User Services; Protocols and Formats".
[20] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[21] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[22] ECC Decision (22)07 (cept.org) https://docdb.cept.org/download/4240: "Harmonised technical conditions for the usage of aerial UE for communications based on LTE and 5G NR in the bands 703-733 MHz, 832-862 MHz, 880-915 MHz, 1710- 1785 MHz, 1920-1980 MHz, 2500-2570 MHz and 2570- 2620 MHz harmonised for MFCN".
[23] 3GPP TS 38.331: "Radio Resource Control (RRC) protocol specification".
[24] 3GPP TS 38.413: "NG Application Protocol (NGAP)".
[25] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning".
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 3 Definitions and abbreviations
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 external AF (e.g. USS) to identify the UAV. GPSI is used as the 3GPP UAV ID.
A2X communication: A communication to support Aircraft-to-Everything (A2X) services leveraging PC5 and/or Uu reference points. A2X services are realized by various types of A2X applications.
A2X message: A dedicated messaging type of A2X service.
A2X service: A data service, offered to A2X applications and optionally A2X Application Servers. An A2X service belongs to one A2X service type. An A2X service can be associated with one or more A2X applications and a A2X application can be associated with one or more A2X services.
A2X service type: A type of A2X service, which is identified by any one of ITS-AID (ITS Application Identifier), PSID (Provider Service Identifier) or AID (Application Identifier) according to values defined specifically for aviation applications.
NOTE 1: It is expected a dedicated set of A2X services will be defined with associated A2X service types. The definition of DAA/UAV service type is out of scope of 3GPP.
Application Layer ID: An identifier identifying an entity, e.g. a UAV, a UAV-C, within the context of a specific A2X application. These identifiers are used for Direct C2 Communication or for Direct Detect And Avoid. The format of this identifier is outside the scope of 3GPP.
NOTE 2: The Application Layer ID could be e.g. CAA-Level UAV ID for UAV defined by other SDOs e.g. ASTM, etc.
Area Airspace Manager (AAM): A ground-based entity that is responsible for managing the airspace for a specific area/arena so that correspondingly residing UAVs are prevented to collide with each other and with other physical objects. For this purpose, AAM is able to detect UAVs residing in the specific airspace and provide policies for collision avoidance to the corresponding UASs. The AAM acts as a TPAE having specific abilities for direct communication with UAVs relevant for the applicable airspace and it includes one or more UEs enabled for use of PC5.
Broadcast Remote ID: The capability of providing Remote Identification and Tracking over broadcast radio links.
NOTE 3: In the scope of this release, the radio link for Broadcast Remote ID is assumed to utilize radio technologies outside the scope of 3GPP.
CAA (Civil Aviation Administration)-Level UAV Identity: a UAV identity assigned by USS/UTM and uniquely identifies a UAV at least within the scope of a USS.
Command and Control (C2) Communication: the user plane link to deliver messages with information of command and control for UAV operation from a UAV controller or a UTM to a UAV or to report telemetry data from a UAV to its UAV controller or a UTM. C2 communication may be over Uu reference point or PC5 reference point.
C2 Aviation Payload: Contains application layer information sent by the UAS to the USS containing UAV pairing information and/or flight authorization information that is transparent to the 3GPP System.
C2 Authorization Payload: Contains application layer information sent by the USS to the UAV containing e.g. C2 pairing information and/or C2 security information that is transparent to the 3GPP System.
C2 Pairing Information: Contains UAV-C Addressing Information which may e.g. include the UAV-C IP Address.
Detect And Avoid: The capability to see, sense or detect conflicting traffic or other hazards and take the appropriate action.
Direct Detect And Avoid: DAA that leverages communications over PC5 reference point.
Direct C2 Communication: the UAV controller and UAV establish a direct C2 link over PC5 reference point to communicate with each other.
Networked UAV Controller: a UAV Controller connected to the 3GPP network and connected to the UAV via a 3GPP network.
Non-Networked UAV Controller: a UAV Controller not connected to the 3GPP network and connected to UAV via a transport outside the scope of 3GPP, e.g. internet connectivity or direct wireless communication over a technology outside the scope of 3GPP.
No-Transmit Zone (NTZ): Geographical area where UAV UEs (i.e. aerial UEs that are UEs with aerial subscriptions) are not allowed to operate in a certain frequency band(s) and in a certain time period(s) (if time restriction exists). The geographical area includes coordinates with longitude, latitude and altitude restrictions. The purpose and requirements of NTZ is described in ECC Decision (22)07 [22].
Networked Remote ID: The capability of providing Remote Identification and Tracking to a USS over 3GPP network.
Remote Identification (Remote ID) of UAS: The ability of a UAS in flight to provide identification and tracking information that can be received by other parties, to facilitate advanced operations for the UAS (such as Beyond Visual Line of Sight operations as well as operations over people), assist regulatory agencies, air traffic management agencies, law enforcement and security agencies when a UAS appears to be flying in an unsafe manner or where the UAS is not allowed to fly. The Remote ID information payload may include Serial Number or Session ID assigned to the UAV, location of the ground-station controller, emergency status indication, etc.
Third Party Authorized Entity: is either a privileged Networked UAV Controller, or a privileged Non-Networked UAV Controller, or another entity which gets information on sets of UAV controllers and UAVs from the 3GPP network and may be connected to the UAV via the Internet; it may be authorized by the UTM to interface with sets of UAV(s).
UAS NF: a 3GPP UAS Network Function for support of aerial functionality related to UAV identification, authentication/authorization and tracking and to support Remote Identification.
UAS Service Supplier (USS): An entity that provides services to support the safe and efficient use of airspace by providing services to the operator / pilot of a UAS in meeting UTM operational requirements. A USS can provide any subset of functionality to meet the provider's business objectives (e.g. UTM, Remote Identification). In the scope of this specification, the term USS refers to both USS and USS/UTM.
UAS Traffic Management (UTM): a system that can safely and efficiently integrate the flying UAV along with other airspace users. It provides a set of functions and services for managing a range of autonomous vehicle operations (e.g. authenticating UAV, authorizing UAS services, managing UAS policies and controlling UAV traffics in the airspace).
UAV controller: The UAV controller of a UAS enables a drone pilot to control an UAV.
UAV operator: the entity owning and operating a UAV.
UAS Container: A container to the 3GPP system that includes UUAA Aviation/Authorization Payload and/or C2 Aviation/Authorization Payload. The internal content of the individual payloads is transparent to the 3GPP system.
UAS Services: refers to establishment of connectivity for a UAS for communication with USS, for C2, for remote identification and for UAV location and tracking.
USS communication: A communication between a UAV and a USS other than C2 communication, by means of user plane data transmission for some UAS Services.
NOTE 4: The PDU session/PDN connection for C2 communication and the PDU session/PDN connection for USS communication can be common or separate.
UUAA Authorization Payload: Contains application layer information optionally including UUAA result for UAV consumption provided by the USS to the UAS which is transparent to the 3GPP System.
UUAA Aviation Payload: Contains application layer information provided by the UAS to USS and is transparent to the 3GPP System
Uncrewed Aerial System (UAS): Composed of Uncrewed Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the control station, the UAV and the network and for remote identification. An UAS may comprise of a UAV and a UAV controller.
Unknown UAVs: A list of the UAVs to be identified in the target area and served by the PLMN as the result of the UAV tracking requested by USS/UTM.
UUAA: UAV USS authentication and authorization procedure of the UAV to ensure that the UAV has successfully registered with a USS and has therefore been authorized for operations by the USS. An UAV is authenticated and authorized by USS via a UUAA procedure with the support of the 3GPP system before connectivity for UAS services is enabled.
UUAA-MM: the UUAA procedure optionally performed during registration to a 5GS.
UUAA-SM: the UUAA procedure performed during the establishment of a PDU session and performed during the establishment of a PDN connection.
For the purposes of the present document, the following terms and definitions given in TS 23.287 [11] apply:
NR Tx Profile
Intelligent Transport Systems
ITS Application Identifier
Provider Service Identifier
Application Identifier
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 Remote Identification
BVLOS Beyond Visual Line of Sight
C2 Command and Control
DAA Detect And Avoid
DDAA Direct Detect And Avoid
MBS Multicast/Broadcast Service
NRID Networked Remote Identification
NTZ No-Transmit Zone
NWDAA Network-Based/Assisted DAA
PQI PC5 5QI
RID Remote Identification
TPAE Third Party Authorized Entity
UAS Uncrewed Aerial System
UAV Uncrewed Aerial Vehicle
UAV-C/UAVC Uncrewed Aerial Vehicle Controller
USS UAS Service Supplier
UTM Uncrewed Aerial System Traffic Management
UUAA USS UAV Authorization/Authentication
UUID Universal Unique Identifier
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4 Architecture model and concepts
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 authorization of C2 Communication.
- A reference model for UAV tracking, supporting three UAV tracking modes: UAV location reporting mode, UAV presence monitoring mode and list of Aerial UEs in a geographic area. The 3GPP system supports geofencing (for in-flight UAV) and geocaging (for UAV on the ground intending to fly) functionality in USS by providing enablers such as location services, event notification to a subscribing USS, etc.
NOTE: Geofencing/geocaging mechanisms are an air traffic control functionality performed by the USS and are out of scope of this specification. The 3GPP system provides enablers to support geofencing/geocaging functionality in USS, e.g. location services, enablement of C2 connectivity, event notification to a subscribing USS, etc. However, no specific geofencing/geocaging mechanisms are defined in 3GPP.
- Support for Broadcast Remote ID using MBS.
- Support for Direct C2 Communication.
- Support for Detect and Avoid mechanisms based on PC5 reference point.
- Support for Broadcast Remote ID using PC5 reference point.
- Support for pre-mission flight planning and in-mission flight monitoring for UAVs.
- Support for multiple USS serving different geographical areas corresponding to the UAV flight path, i.e. changeover of the UAV from one USS to another USS.
- Support for network-assisted/ground-based Detect And Avoid mechanisms.
- Enforcement of No Transmit Zone restriction by UAVs is implementation-specific.
- Support for altitude reporting.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.2 Architectural reference model
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.2.1 General
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 before connectivity for UAS services is enabled.
- Depending on 3GPP network operator and/or regulatory requirements, the UUAA is performed:
- In 5GS: either as a separate procedure during the 5GS registration procedure (optional and based on specific PLMN policies, USS requirements and geographic regulatory requirements), or when the UAV requests user plane resources for UAV operation (i.e. PDU session establishment). The UAV shall support UUAA during Registration and PDU session establishment procedure. The network shall support UUAA during PDU session establishment.
- In EPS: during the attach procedure and the corresponding PDN connection establishment. The network shall support UUAA during PDN connection establishment. The UAV shall support UUAA during PDN connection establishment procedure.
- A UAV that is provisioned with a CAA-Level UAV ID shall provide the CAA-Level UAV ID in 5GS in both Registration and in PDU Session establishment. In EPC, a UAV that is provisioned with a CAA-Level UAV ID provides the CAA-Level UAV ID in PDN Connection establishment in SM-PCO. The CN determine whether UUAA is executed at 5GS registration or at PDU session/PDN Connection establishment, based on local policies.
- The UUAA is performed at PDU session establishment when the UAV requests user plane resources for UAV operation and the UAV provides its CAA Level ID during PDU session (PDN connection) establishment.
- The UAV flight authorization and UAV-UAVC pairing authorization is performed at PDU session/PDN connection establishment/modification procedures.
- The 3GPP system supports USS authorization of pairing between a UAV and a networked UAVC or a UAVC that connects to the UAV via Internet connectivity during either the establishment of the PDN connection/PDU session for C2 communication or a modification of a PDN connection/PDU session either dedicated to C2 communication or common to USS communication and C2 communication. Modifications of the pairing or re-authorization take place via modification of the established PDN connection/PDU session. During such procedures, the USS provides to the 3GPP system information (e.g. QoS requirement, data flow descriptors, etc.) that enable traffic between the UAV and the UAVC.
NOTE 1: How the USS is made aware of the UAVC is outside the scope of 3GPP in this Release.
- For EPC, the PDN connections used by UAV are served by SMF+PGW-C regardless of whether the UAV support 5G NAS or whether their subscription allows access to 5GC. The APN(s) used by the UAV for contacting USS or for C2 communication always resolves to a SMF+PWG-C.
The following architectural assumptions apply:
- It is assumed that the UAV trying to access UAS services using 3GPP connectivity is already registered with a USS and has been assigned a CAA-Level-UAV ID. The procedure for UAV registration and assignment of CAA-Level-UAV ID is out of scope of 3GPP. The USS assigns to the UAV a CAA-Level UAV ID, or is made aware of the assigned CAA-Level UAV ID.
- A UAV is associated with an Aerial subscription in the UDM. The Aerial subscription contains aerial UE indication in the Access and Mobility Subscription data (to be used similarly to aerial UE indication defined in EPS), an aerial service indication in the Session Management Subscription data for each DNN dedicated for UAS services (C2 and UUAA-SM) which indicates that corresponding authentication/authorization has to be done using API based mechanism.
- An UAV is identified by USS using a CAA-level UAV ID and identified by the 3GPP System using a 3GPP UAV ID assigned by the MNO:
- It is assumed that an aerial subscription associated to a UAV includes at least one GPSI to be used as 3GPP UAV ID.
- A UAV is registered with the USS either before connecting with the 3GPP system or using plain internet connectivity via the 3GPP system. Before registering for UAS services with the 3GPP system, the UAV shall be provisioned with a CAA-Level UAV Identity.
- In roaming scenarios, it is assumed that access to USS is in the VPLMN, thus packet data connectivity for UAV-USS communication is in local breakout and the UAS NF function is located in the VPLMN.
- In this Release, the UAV uses 3GPP access (i.e. LTE & NR) for 3GPP UAV related operations.
- Activation of RAN aerial features for UAV accessing via E-UTRA reuses the existing mechanism defined in TS 36.300 [7].
- One or more USS(s) may be present in a specific region and may manage UAVs over one or more 3GPP networks.
- The 3GPP Network subscription for the UAV is not assumed to contain any information about the USS.
- The USS address(es), if known to the UAV, is/are configured in the UAV via mechanisms outside the scope of 3GPP. Multiple USS addresses may be configured/provisioned to UAV in case that multiple USSs are deployed in a geographic area and may serve the UAV flight path.
- For PC5, Release 15 (and later) version of the specification is the baseline.
NOTE 2: In this Release, UAV UE uses A2X capability to support the PC5 based DAA and BRID.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.2.1.2 Void
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 and EPC/E-UTRAN
NOTE 2: Transferring the UUAA context from AMF to MME when the UE moves from 5GS to EPS and the UUAA was performed at 5GS registration is not supported on the N26 interface.
NOTE 3: No new UAV-specific functionality is defined for T6a.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 scenario
4.2.4A Void
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 Update (UCU) procedure to inform AMF subscription information has changed.
Npcf: In the case of A2X Service, services provided by H-PCF are used to provide A2X Service related parameters to V-PCF for UE and NG-RAN in the roaming case.
Nudr: In the case of A2X Service, services provided by UDR are used to notify the PCF and the UDM of the update of the A2X Service related information.
Nnef: In the case of A2X Service, services provided by NEF are used by the A2X Application Server to update A2X Service related information of 5GC.
Namf: In the case of A2X Service, services provided by AMF are consumed by PCF to provide the A2X Service related parameters for the UE and the NG-RAN to AMF and to enable the AMF create or update UE context related to A2X service.
Nnrf: In the case of A2X Service, services provided by NRF are used to discover the PCF that supports A2X.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 point is out of scope of this specification.
A2X5: The reference point between the A2X applications in the UEs. This reference point is not specified in this release of the specification.
N1: In addition to the relevant functions defined in TS 23.501 [2] for N1, in the case of A2X Service it is also used to convey the A2X Policy and parameters (including service authorization) from AMF to UE and to convey the UE's A2X Capability and PC5 Capability for A2X information from UE to AMF.
N2: In addition to the relevant functions defined in TS 23.501 [2] for N2, in the case of A2X Service it is also used to convey the A2X Policy and parameters (including service authorization) from AMF to NG-RAN.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.3 Functional entities
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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-authorization and revocation; for location reporting, presence monitoring, obtaining list of Aerial UEs in a geographic area and control of QoS/traffic filtering for C2 communication.
The UAS NF makes use of NEF exposure services for pre-flight planning and in-flight monitoring for UAVs.
The UAS NF may coordinate with the USS to assist CAA-Level UAV ID assignment.
A dedicated NEF may be deployed to provide only the UAS NF functionality, i.e. to support the UAS specific features/APIs and the NEF features/APIs that are specified for capability exposure towards the USS.
For external exposure of services related to specific UAV(s), the UAS NF resides in the VPLMN, in order to interface with country specific USS(es).
When CAPIF is supported by the UAS NF, the UAS NF supports the CAPIF API provider domain functions as specified in TS 23.222 [4].
To support re-authentication/re-authorization and revocation request by USS, the UAS NF stores information as to whether the re-authentication/re-authorization and revocation is towards an AMF or SMF/SMF+PGW-C and the address of the serving AMF or SMF/SMF+PGW-C.
UAS NF stores the result of UUAA-MM procedures and the result of UUAA-SM procedures.
The UAS NF requests information from relevant NFs and generates pre-flight planning assistance information and in- flight monitoring information.
The UAS NF requests information from relevant NFs for determining whether UAV has left or is about to leave the service area of one USS and moves into area of another USS.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 system for UAS services (i.e. to take advantage of aerial features, connectivity with USS and for C2 connectivity) and provides the CAA-Level UAV ID and a UUAA Aviation Payload to 5GS or EPS. A UAV that has not performed a registration with aviation authorities shall not attempt to request for UAS services.
NOTE: A UAV that is configured for UAS services but does not have an aerial subscription is not allowed by the network to register for UAS services.
- a UAV that is configured for UAS services may support the following functions:
- reports the A2X Capability and PC5 Capability for A2X (i.e. LTE PC5 and/or NR PC5) to 5GC over N1 reference point.
- indicates A2X Policy Provisioning Request in UE Policy Container for UE triggered A2X Policy provisioning.
- receives the A2X parameters from 5GC over N1 reference point.
- supports procedures for A2X communication over PC5 reference point.
- Configuration of parameters for A2X communication. These parameters can be pre-configured in the UE, or, if in coverage, provisioned or updated by signalling over the N1 reference point from the PCF in the HPLMN or over A2X1 reference point from the A2X Application Server.
- Provided with the following for receiving Broadcast Remote ID via MBS:
- Announcement via existing announcement mechanisms specified in TS 23.247 [17], TS 26.502 [18] and TS 26.517 [19]; or
- MBS session announcement provisioned as specified in clause 6.2.1.3.1.
- Provisioned with MBS session announcement for receiving A2X Application Server information via MBS as specified in clause 6.2.1.3.1.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 the UAV triggers a re-authentication, or when AMF itself determines to re-authentication the UAV after the initial registration.
An AMF supporting A2X additionally performs the following functions:
- Obtain from UDM the subscription information related to A2X and store them as part of the UE context data.
- Select a PCF supporting A2X Policy/Parameter provisioning and report the PC5 Capability for A2X to the selected PCF.
- Obtain from PCF the PC5 QoS information related to A2X and store it as part of the UE context data.
- Provision the NG-RAN with indication about the UE authorization status about A2X communication over PC5 reference point.
- Provision the NG-RAN with PC5 QoS parameters related to A2X communication.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 authorization of pairing between a UAV and a networked UAVC or a UAVC that connects to the UAV via Internet connectivity during the establishment/modification of the PDN connection/PDU session for C2 communication.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.3.6 SMF+PGW-C
| The SMF+PGW-C implements the functions of the SMF described in clause 4.3.5.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 parameters for A2X communications over PC5 reference point and parameters for A2X communications over MBS.
- Act as an AF/AS in clause 5.1 and Annex A of TS 23.247 [17] e.g. request NEF/MBSF for allocation/de-allocation of a set of TMGIs, initiate broadcast service from the 5GC by providing service information including QoS requirement to 5GC.
- Perform MBS service area mapping as specified in clause 5.5.2.4.
NOTE: The A2X AS and the USS serving a UAV can be the same or different entities.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.3.10 UDR
| In addition to the functions defined in TS 23.501 [2], the UDR stores A2X service parameters.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4 High level function
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1 Service Operations
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.1 NEF Services
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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
AuthenticateAuthorize
Request/Response
AMF, SMF
Notification
Subscribe/Notify
AMF, SMF
Nnef_UAVFlightAssistance
Create
Subscribe/Notify
AF/USS
Update
Subscribe/Notify
AF/USS
Notify
Subscribe/Notify
AF/USS
Nnef_RetrieveInfoUAVFlight
Get
Request/Response
AF/USS
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.1.2 Nnef_Authentication service
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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 either 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) or by SMF when the PDU session is released as specified in clause 5.2.3.2.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.1.3 Nnef_UAVFlightAssistance service
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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. This service also enables the UAS NF/NEF to trigger the UAV's altitude reporting, altitude reporting stop and update and receive the UAV's altitude from USS.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.1.3.2 Void
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 providing a NEF/UAS NF information about the in-flight monitoring of a target UAV. The request creates an implicit subscription to get notified about the following events, when applicable, (1) the UAS NF/NEF determines that UAV will leave a geographical area served by the USS, (2) the UAV enters a TA/Cell with a border-crossing point to another USS, (3) the UAV deviates from the assigned flight plan and (4) failure of altitude reporting.
Input, Required: UAV's identifier (e.g. GPSI), indication about the purpose of the request (i.e. USS changeover, in-flight monitoring).
Input, Optional: Flight path information, which may include planned flight path information for each of the segment of the paths served by different USS, e.g. a list of TA, UAV's speed, candidate border-crossing point(s), 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 need the assistance from the 5GS, and it can be used by the service consumer to inform the UAS NF/NEF about UAV's altitude.
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), Notification Target Address, UAV's altitude information, indication to stop the configured altitude information reporting.
Output, Required: None.
Output, Optional: None.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 about the information related to altitude reporting (e.g. the altitude thresholds and information about the required periodicity of the reporting) and failure of altitude reporting, notifying a USS about the monitoring results for the UAV.
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, altitude thresholds, indication about the required periodicity of the reporting, failure of altitude reporting.
Output, Required: Indication whether the USS changeover is completed successfully when used by the target USS when responding to the notification.
Output, Optional: None.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.1.4 Nnef_RetrieveInfoUAVFlight_Get service
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 information (i.e. USS changeover, pre-flight planning).
Input, Optional: List of suitable target USSs, a list of candidate border-crossing point(s), acceptable deviations for flight plan/route, information about the starting and ending points for the flight, information about candidate flight path(s), requirements on the flight path and accuracy level of predictions relevant to the flight planning, as described in clause 5.12.
Output, Required: Report containing a Report ID (e.g. Transaction Reference ID assigned by the NEF) and the retrieved information.
Output, Optional: Altitude thresholds, reporting periodicity indication.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.2 AF Services
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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
AuthenticateAuthorize
Request/Response
UAS NF/NEF
Notification
Subscribe/Notify
UAS NF/NEF
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.2.2 Naf_Authentication service
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 notification related with the authentication/authorization (e.g. re-authenticate, update authorization data or revoke the UUAA authorization). This implicit subscription is implicitly released either 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) or by SMF when the PDU session is released as specified in clause 5.2.3.2.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 (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: Information about relevant USSs (i.e. a list of USS addresses, information about geographical area each of the USSs serve).
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.4 SMF Services
| SMF services related to UAS are defined in TS 23.502 [3] clause 5.2.8.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.4.1.5 UDM Services
| UDM services related to UAS are defined in TS 23.502 [3] clause 5.2.3.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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].
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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].
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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].
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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].
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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. A UAV can be either pre-configured with addresses of multiple USSs and information about a geographical area the particular USS serves or a UAV can be provisioned with that information (i.e. USS addresses and geographical area information) from a USS via the NEF/UAS NF in a UUAA Authorization Payload. If the UAV is pre-configured/provisioned with the information about USSs, then the UAV may provide to the NEF/UAS NF the USS address of the corresponding geographical area based on UAV's 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. When a USS address is available, the USS address is used by the UAS NF in addition to a CAA-Level UAV ID to discover a specific USS. If the UAS NF is configured with addresses of multiple USSs where each USS serves a different geographical area (either Pre-Configured or received from USS), the UAS NF considers the location of the UAV (if available) to discover and select the correct USS.
NOTE: A USS, whose address is provided by the UAV, is assumed to be accessible to any UAS NF/NEF in the 3GPP network.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 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.
NOTE 1: Whether privacy or confidentiality requirements will apply to the unique UAV temporary identity depends on regulations in various regions.
- 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.
Two types of CAA-level UAV ID assignment are supported:
1. USS-assigned CAA-Level UAV ID: the identity is assigned completely at USS level.
2. 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).
NOTE 2: It is assumed that the UAV is not aware of which assignment mechanisms is used for the CAA-Level UAV ID.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.5 Identifiers
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 4.5.1 General
| The UAV is associated with the following identifiers in the 3GPP system.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 as UAV identity in Remote Identification.
The aviation domain may allocate a new CAA-level UAV Identity for the UAV at any time. The new CAA-level UAV Identity may be provided to the UAV and 3GPP system during UAS related procedures.
NOTE: It is assumed that mechanisms are available to ensure privacy and protection (e.g. anti-spoofing) of the CAA-assigned UAV Identity when it is used for Remote Identification. Security solutions to provide such privacy are outside the scope of this specification.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 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 aviation domain) to the 3GPP UAV ID (which is provided during the UUAA procedure).
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5 Functional description and information flows
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.1 Void
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2 UAV Authentication and Authorization
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.1 UUAA Model
| The following applies for UUAA for a UAV:
- UUAA-MM is optional and performed at 5GS registration based on operator's policy. If required by the operator, UUAA-MM is performed if the UAV has an aerial UE subscription in the Access and Mobility Subscription Data and provides the CAA-Level UAV ID in the Registration Request message.
- UUAA-SM in 5GS is performed at PDU session establishment to a subscribed DNN applicable for UAS services if the UAV provides the CAA-Level UAV ID in the PDU Session Establishment Request message. Whether the DNN is applicable for UAS services is determined by the aerial service indication being set for the DNN in the Session Management Subscription Data.
- UUAA-SM in EPS is performed at PDN Connection Establishment when activating a PDN Connection to a subscribed APN applicable for UAS service if the UAV provides the CAA-Level UAV ID in the ESM container. Whether the APN is applicable for UAS services is determined by the aerial service indication being set for the corresponding DNN in the Session Management Subscription Data (fetched from UDM triggered by CAA-Level UAV ID being provided in request).
- UUAA-SM may be performed to re-authenticate the UAV or to reauthorize at PDU session modification or EPS bearer modification (e.g. in case of C2 authorization or flight plan authorization change) if the UE includes CAA-Level UAV ID and a UUAA Aviation Payload.
NOTE: If the network is configured to perform UUAA at registration, UAV has not provided CAA-Level UAV ID and the UE has aerial subscription, then the AMF can allow the UAV to register as a normal UE. If the network is configured to perform UUAA at PDU Session Establishment, the UE has not provided CAA-Level UAV ID and the SM subscription data indicates that UUAA-SM to be performed, the SMF rejects the PDU Session Establishment request.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.2 UUAA at Registration in 5GS (UUAA-MM)
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.2.1 General
| The UUAA-MM procedure is optional and triggered for a UE that requires UAV authentication and authorization by a USS when registering with 5GS. The UUAA-MM procedure is triggered by the AMF. UUAA-MM is triggered during the UE Registration based on the local network policy, if the UE has an Aerial UE subscription with the 5GS and if the UE has provided the CAA-Level UAV ID of the UAV in the Registration Request, or when the USS that authenticated the UAV triggers a re-authentication.
The UE is authenticated and authorized by USS using a CAA-Level UAV ID and credentials associated to the CAA-Level UAV ID, different from the 3GPP subscription credentials (e.g. SUPI and credentials used for PLMN access). During UUAA-MM procedure, the AMF communicates with the USS via a UAS NF and forwards authentication messages transparently between the UE and UAS NF.
UAS NF stores the UAV UEs UUAA context after successful UUAA procedure. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF depending on deployments. The UAS NF shall also create an implicit subscription for notification towards the AMF after the successful UUAA procedure. This notification is used by the UAS NF to trigger re-authentication, update authorization data or revoke authorization of the UAV, upon receipt of such request from the USS.
Figure 5.2.2.1-1: UUAA in the context of the Registration procedure (UUAA-MM)
1. The UE sends a Registration request message and, if configured with one, it shall provide a CAA-level UAV ID of the UAV and optionally a USS address when registering for UAS services.
2. If primary authentication is required (e.g. if this is an initial Registration), AMF invokes it as described in step 9 in Figure 4.2.2.2.2-1 of TS 23.502 [3]. Subsequently AMF retrieves UE subscription data from UDM as described in step 14 in Figure 4.2.2.2.2-1 of TS 23.502 [3] - (not shown in the figure).
3. AMF shall determine whether UUAA-MM is required for the UAV. The AMF decides that UUAA is required if:
a) the UE has a valid Aerial UE subscription information;
b) UUAA is to be performed during Registration according to local operator policy;
c) there is no successful UUAA result from a previous UUAA-MM procedure;
d) the UE has provided a CAA-Level UAV ID.
AMF shall not perform UUAA-MM for non-3GPP access and shall ensure that the UE is not allowed to access any aerial services in non-3GPP access by rejecting PDU session establishment requests for aerial services (identified by DNN/S-NSSAI).
4. If AMF determines in step 3 that a UUAA-MM is to be performed, AMF shall include a pending UUAA-MM indication in the Registration Accept message. The AMF stores in the UE context that a UUAA is pending. The UE shall wait for completion of the UUAA-MM procedure without attempting to register for UAS services or to establish user plane connectivity to USS or UAV-C.
If AMF determines that UUAA is not to be performed during this Registration procedure, UUAA may be triggered during PDU Session Establishment later on.
If UUAA is configured in the AMF to be performed during 5GS registration and the UE has provided a CAA-Level UAV ID in the registration request in step 1, but the UE does not have an aerial subscription in the UE subscription data retrieved from the UDM in step 2, then the AMF rejects the registration with an indication informing no aerial subscription. This information indicates to the UAV of the reason for the rejection for aerial services and ensures that the UE is not allowed to access any aerial service.
If UAS services become enabled or disabled (e.g. because the aerial subscription becomes a part of the UE subscription data retrieved from UDM as described in clause 5.2.3.3.1 of TS 23.502 [3]) then AMF may trigger a UE Configuration Update procedure as described in clauses 4.5.1 and 4.2.4.2 of TS 23.502 [3] to notify the UE. The UE may initiate a mobility registration update procedure to get the UAS services after completion of the UE Configuration Update procedure.
If UUAA is configured in the AMF to be performed during 5GS registration, the UE did not provide a CAA-Level UAV ID in the registration request in step 1, but UE has aerial subscription in the UE subscription data retrieved from UDM in step 2, then the AMF accepts the registration and ensures that the UE is not allowed to access any aerial service by storing in the UE context that 'UUAA-MM has FAILED' and further rejecting PDU session establishment requests for aerial services (identified by DNN/S-NSSAI). At a later point in time, if the UE wants to use the aerial services by providing the CAA Level UAV ID later on via UUAA-MM procedure, then the UE shall first perform Mobility Registration Update as explained in clause 4.2.2.2.2 of TS 23.502 [3].
5. If UE indicates its support for Network Slice-Specific Authentication and Authorization (NSSAA) procedure in the UE MM Core Network Capability and if the UE includes Requested S-NSSAI in Registration Request which is subject to NSSAA, however, the Requested S-NSSAI has not been successfully authenticated, the NSSAA procedure is executed as described in clause 4.2.2.2.2 of TS 23.502 [3].
6. If required based on step 3 determination and if the S-NSSAI that is associated with the UAS services is part of the Allowed NSSAI, UUAA-MM procedure (see clause 5.2.2.2) is executed at this step. Once the UUAA-MM procedure is successfully completed for the UAV, the AMF stores a successful UUAA result and updates the UE context indicating that UUAA is no longer pending and the authorized CAA-Level UAV ID if provided by the USS. The USS may provide a new CAA-Level UAV ID as the authorized CAA-Level UAV ID. The AMF shall trigger a UE Configuration Update procedure (see TS 23.502 [3], clause 4.2.4.2) to deliver the UUAA result, the UUAA Authorization Payload containing UAV configuration and the authorized CAA-Level UAV ID if received from the USS to the UE.
NOTE 1: The UAV configuration is application layer information outside the scope of 3GPP.
If UUAA fails, based on local network policy, the AMF may decide to de-register the UE with an appropriate cause value in the De-Registration Request message, or keep the UE-registered with a failure UUAA result in UE context as described in step 7 of clause 5.2.2.2 and ensures that the UE is not allowed to access any aerial service based on the DNN/S-NSSAI value. If the UE is de-registered, the UE may re-attempt to re-register without including the CAA-level UAV ID.
NOTE 2: The security aspects for this procedure is defined in TS 33.256 [10].
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.2.2 UUAA-MM Procedure
|
Figure 5.2.2.2-1: UUAA-MM procedure
1. For a UE that requires UUAA or when triggered by re-authentication by USS, the AMF triggers a UUAA-MM procedure. If the UE does not have an Aerial subscription in the UE subscription data retrieved from the UDM, the AMF shall not trigger a UUAA-MM procedure.
2. AMF to UAS NF/NEF: The AMF invokes Nnef_Authentication_AuthenticateAuthorize Request message. For initial authentication, this shall include the GPSI and the CAA-Level UAV ID and may include USS address (e.g. FQDN), UUAA Aviation Payload if it was provided by the UE. For re-authentication triggered by AMF, this may not include the CAA-Level UAV ID. UAS NF resolves the USS address based on CAA-Level UAV ID or considers the pre-configured USS addresses per serving area based on the current location of the UAV or uses the provided USS address, as described in clause 4.4.2. In addition, the AMF may also include the User Location Information (e.g. Cell ID). The UAS NF should store the serving AMF ID.
The AMF identifies the UAS NF/NEF based on local configuration or by NF discovery procedure using DNN/S-NSSAI and/or UE provided identity e.g. USS address.
The AMF also provides a Notification Endpoint to the UAS NF/NEF, so that UAS NF/NEF can include this Notification Endpoint together with UUAA updated parameters, as shown in clause 5.2.4. By providing the Notification Endpoint, the AMF is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from UAS NF/NEF, if the UUAA result is successful in step 5.
NOTE 1: The security aspects for this procedure is defined in TS 33.256 [10].
3. UAS NF/NEF to USS: Naf_Authentication_AuthenticateAuthorize Request message, shall include the GPSI and CAA-Level UAV ID and optionally UAV location obtained from AMF in step 2 e.g. to support geo-caging functionality. UAS NF/NEF may translate the Cell ID received as UAV location from AMF in step 2 into a corresponding geographic area and/or may further obtain the UE location information using Location Service Procedures as defined in TS 23.273 [8].
The UAS NF/NEF also provides a Notification Endpoint to the USS, so that USS can include this Notification Endpoint together with UUAA updated parameters, as shown in clause 5.2.4. By providing the Notification Endpoint, the UAS NF/NEF is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from USS, if the UUAA result is successful in step 5.
4. [Conditional] Multiple round-trip messages as required by the authentication method used by USS. Naf_Authentication_AuthenticateAuthorize Response messages from USS shall include GPSI and shall include an authentication message based on authentication method used that is forwarded transparently to UE over NAS MM transport messages. The authentication message in step 4d may contain UUAA Aviation Payload required by the USS if it was not provided by the UE before.
5. USS to UAS NF/NEF: (final) Naf_Authentication_AuthenticateAuthorize Response message, shall include: GPSI, a UUAA result (success/failure) for the UAV and the UAS NF, may include an authorized/new CAA-Level UAV ID for the UAV and a UUAA Authorization Payload to the UAV (e.g. security info to be used to secure communications with USS) and a final authentication message (e.g. indicating success or failure and if the UUAA is for re-authentication, indicating whether the UAS service related network resource can be released in case of UUAA failure) based on authentication method used that is forwarded transparently to UE over NAS MM transport messages. The USS may send in the Naf_Authentication_AuthenticateAuthorize Response message the information about relevant USSs (i.e. a list of USS addresses, information about geographical area each of the USSs serve); the USS includes that information also inside the UUAA Authorization Payload for the UAV consumption.
6. UAS NF/NEF to AMF: (final) Nnef_Authentication_AuthenticateAuthorize Response message, forwards information received from USS in step 5. If UUAA for re-authentication failed and UAS NF/NEF received indication that the UAS service related network resource can be released in step 5, the UAS NF/NEF includes an indication that the PDU sessions associated with the "DNN(s) subject to aerial services" can be released.
7a. [Conditional] UAS NF/NEF to AMF: If UUAA-MM succeeded and UAS NF/NEF has not subscribed to AMF for the access and mobility information events before, UAS NF/NEF subscribes to AMF for the mobility event notification by sending Namf_EventExposure_Subscribe request with the mobility events as described in TS 23.502 [3], Table 5.2.2.3.1-1 with Event ID = Reachability Filter.
7b. [Conditional] UAS NF/NEF to AMF: If UUAA-MM failed and UAS NF/NEF has subscribed to AMF for the access and mobility information events earlier, UAS NF/NEF unsubscribes to AMF for the mobility event notification by sending Namf_EventExposure_Unsubscribe request with Subscription Correlation ID.
8a. [Conditional] AMF to UAS NF/NEF: The AMF acknowledges the subscription request from 7a by sending Namf_EventExposure_Subscribe response with Subscription Correlation ID.
8b. [Conditional] AMF to UAS NF/NEF: The AMF acknowledges the un-subscription request from 7b by sending Namf_EventExposure_Unsubscribe response.
9. AMF to UE: (final) NAS MM transport message forwarding authentication message from USS including authentication/authorization result (success/failure) and the UUAA Authorization Payload.
10. [Conditional] if UUAA-MM succeeded, AMF triggers a UE Configuration Update procedure to deliver to the UAV authorization information from USS, as described in clause 5.2.2.1.
11. [Conditional] If UUAA-MM fails during a Re-authentication and Re-authorization and there are PDU session(s) established using UAS services and the USS has indicated that the network resources can be released, AMF may trigger these PDU Sessions release. AMF identifies the relevant PDU session(s) for UAS services based on the DNN/S-NSSAI value of the PDU session.
NOTE 2: When the UUAA-MM fails during a Re-authentication and the USS has not indicated that the network resources can be released, the USS can initiate UUAA revocation as described in clause 5.2.7.
[Conditional] if UUAA-MM fails, based on network policy the AMF may trigger Network-initiated Deregistration procedure described (as specified in clause 4.2.2.3.3 of TS 23.502 [3]) and it shall include in the explicit De-Registration Request the appropriate rejection cause value.
If there is an AMF relocation for the UAV, the new serving AMF shall notify the UAS NF about the new AMF ID and the related CAA-level UAV ID using the existing AMF event notification service.
At any time after the initial registration, the USS (via UAS NF/NEF) or the AMF may initiate Re-authentication procedure for the UAV. For AMF initiated case the Re-authentication procedure shall start from step 2. USS initiated re-authentication procedure is described in clause 5.2.4.
If the UE is deregistered as per clause 4.2.2.3 of TS 23.502 [3], then the AMF shall unsubscribe to UAS NF and then UAS NF/NEF may clear the UUAA-MM context and update USS.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.3 UUAA At PDN Connection/PDU Session Establishment (UUAA-SM)
| |
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.3.1 General
| NOTE 1: The security aspects for this procedure is defined in TS 33.256 [10].
An UAV uses PDU Sessions or PDN Connections in the UE for connectivity with the USS and for connectivity with a networked UAV-C.
A networked UAV-C is a UE which uses existing procedures for establishing PDU Session or PDN Connection for communication with the USS/UTM and the procedures described in this clause do not apply to a networked UAV-C.
This clause describes procedure that applies both for 5GS and EPS, where PDU Session refers to 5GS and PDN Connection refers to EPS.
PDU Session(s)/PDN Connection(s) for UAS services shall only be established after a UAV has been authenticated and authorized by the USS. This may happen during UUAA-SM as described in this clause.
A UAV may use either a common or separate PDU Session/PDN connection for connectivity with the USS and a UAV-C.
When the UAV requests establishment of a PDU session/PDN connection, the PDU session/PDN Connection may require UUAA authorization of the UAV, subject to operator policy and regulatory requirements.
If the UAV uses the PDU session/PDN connection for C2 the PDU session is subject to C2 authorization as described in clause 5.2.5.
The PDU Session/PDN Connection is identified by the SMF/SMF+PGW-C as being for USS/C2 communication based on the aerial service indication set in the Session Management Subscription data for the DNN or DNN and S-NSSAI combination.
To subscribe to the PDU Session/PDN Connection Status Event, UAS NF/NEF determines the APN/DNN or DNN and S-NSSAI combination as below:
- The UAS NF/NEF may receive APN/DNN or DNN and S-NSSAI combination from the USS as specified in clause 4.15.3.2.3 of TS 23.502 [3];
- The UAS NF/NEF may map the AF-Identifier from the USS into APN/DNN or DNN and S-NSSAI combination based on local configuration as specified in clause 4.15.3.2.3 of TS 23.502 [3]; or
- The UAS NF/NEF may map the External Application Identifier from the USS into the APN/DNN or DNN and S-NSSAI combination based on local configuration.
NOTE 2: If the PDU session/PDN connection for C2 communication and the PDU session/PDN connection for USS communication are separate, different AF-Identifiers or External Application Identifiers can be used.
During the establishment or modification procedure of the PDU Session/PDN connection for C2 communication, the USS shall provide the 3GPP system with following information for enabling basic C2 communication between UAV and UAV-C:
- Traffic filters;
- QoS requirements.
The USS can enable/disable C2 communication between UAV and UAV-C necessary for services used during the flight operation at any point in time as described in clause 5.2.9.
UAS NF stores the UAV UEs UUAA context after successful UUAA-SM procedure. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF depending on deployments. The SMF shall subscribe for notifications from UAS NF which may be used to trigger re-authentication, update authorization data or revoke authorization of the UAV, upon receipt of such request from the USS.
Clause 5.2.3.2 defines the USS UAV Authorization/Authentication (UUAA) procedures at PDU Session Establishment in 5GS and clauses 5.2.3.3 and 5.2.3.4 are for the PDN Connection Establishment for EPS using the interworking functionality.
When the C2 authorization is revoked by the USS, the SMF or SMF+PGW-C shall release the PDU Session/PDN connection for C2 communication (in case separate PDU Sessions/PDN Connections are used), or disable C2 communication for the PDU Session/PDN connection (in case common PDU Session/PDN Connection is used), e.g. by removing the traffic filters for C2 communications and the QoS flow for C2 communication and informs the UE with a PDU session modification/bearer modification request.
When the UUAA is revoked by the USS, all UAV related PDU Session/PDN connections shall be released.
|
7c1d55c5e04b1d8831fd0a9b333a8d08 | 23.256 | 5.2.3.2 USS UAV Authorization/Authentication (UUAA) during the PDU Session Establishment
| The USS UAV Authorization/Authentication (UUAA) is triggered by the SMF during the PDU Session Establishment, specified in TS 23.502 [3], clause 4.3.2.2 and additionally based on the SM subscription data obtained from UDM and the Service Level Device Identity provided by the UE in the PDU Session establishment request.
Figure 5.2.3.2 -1: UUAA during PDU Session Establishment
The procedure assumes that the UE/UAV has already registered on the AMF.
0. Steps 1 - 5 as in TS 23.502 [3] figure 4.3.2.2.1-1.
The UAV includes the Service Level Device Identity (e.g. the CAA-Level UAV ID of the UVA) and may include the Authentication Server Address (i.e. the USS address or the USS address for the corresponding geographical area based on the UAV current location) and optionally Authentication Data (i.e. the UUAA Aviation Payload) in the PDU Session Establishment request.
The SMF determines that it needs to invoke UAS NF/NEF service operation for UUAA Authentication/Authorization of the PDU session establishment request based on that the provided DNN/S-NSSAI combination is dedicated for aerial services (have aerial service indicator set) and that the Service Level Device Identity (CAA-Level-UAV ID) is included in the request. If the provided APN/DNN is dedicated for aerial services but Service Level Device Identity (CAA-Level UAV ID) is not provided, the SMF shall reject the establishment of the PDU Session and steps 1 - 9 are not performed.
The SMF identifies the UAS NF/NEF based on local configuration or by NF discovery procedure using DNN/S-NSSAI and/or UE provided identity e.g. USS address.
1. The SMF invokes Nnef_Authentication_AuthenticateAuthorize service operation, including the Service Level Device Identity (that contains the CAA-Level UAV ID of the UAV), DNN, S-NSSAI and may include the Authentication Server Address (i.e. the USS address) and the UUAA Aviation Payload if it was provided by the UE, GPSI, optionally UAV location, PEI if available and the UE IP Address if available. The UAV location is the User Location Information provided by the AMF (e.g. Cell ID). The UAS NF/NEF selects a USS based on either the Service Level Device Identity (i.e. CAA-Level UAV ID of the UAV) or the pre-configured USS addresses per serving area based on the current location of the UAV or the Authentication Server address (i.e. USS address) as described in clause 4.4.2.
SMF also provides a Notification Endpoint to the UAS NF/NEF, so that UAS NF/NEF can include this Notification Endpoint together with UUAA updated parameters, as shown in clause 5.2.4. By providing the Notification Endpoint, the SMF is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from UAS NF/NEF, if the UUAA result is successful in step 4.
2. From UAS NF/NEF to USS: Naf_Authentication_AuthenticateAuthorize service operation forwarding the authentication request received information from the SMF. UAS NF may translate the Cell ID received as part of UAV location in the Nnef_Authentication_AuthenticateAuthorize request at step 1 into a corresponding geographic area and/or may further obtain the UE location information using Location Service Procedures as defined in TS 23.273 [8] and include them in the Naf_Authentication_AuthenticateAuthorize message towards the USS e.g. to support geo-caging functionality.
UAS NF/NEF also provides a Notification Endpoint to the USS, so that USS can include this Notification Endpoint together with UUAA updated parameters, as shown in clause 5.2.4. By providing the Notification Endpoint, the UAS NF/NEF is implicitly subscribed to be notified of re-authentication, update authorization data or revocation of UAV from USS, if the UUAA result is successful in step 4.
3. [Conditional] Multiple round-trip messages as required by the authentication method used by USS. This step is performed if the Naf_Authentication_AuthenticateAuthorize response messages from USS in step 3a does not contain a UUAA result (SUCCESS/FAILURE). Naf_Authentication_AuthenticateAuthorize response messages from USS shall include GPSI and shall include an authentication message based on authentication method used that is forwarded transparently to UE over NAS MM transport messages. The authentication message in step3e may contain UUAA Aviation Payload required by the USS if it was not provided by the UE before.
4. From USS to UAS NF/NEF: Naf_Authentication_AuthenticateAuthorize response.
The USS sends Naf_Authentication_AuthenticateAuthorize response to the UAS NF/NEF with the Authentication/Authorization result containing the UUAA result (SUCCESS/FAILURE) for the UAS NF and indication whether the UAS service related network resource can be released in the case of UUAA failure for re-authentication or re-authorization, optionally a Service Level Device Identity containing the authorized CAA-Level UAV ID, requested policy information and the UUAA Authorization Payload. The requested policy information from USS may contain a DN Authorization Profile Index and/or a DN authorized Session AMBR. The USS may include a new CAA-Level UAV ID as authorized CAA-Level UAV ID. The USS may send in the Naf_Authentication_AuthenticateAuthorize response the information about relevant USSs (i.e. a list of USS addresses and information about a geographical area each of the USSs serve); the USS includes that information also inside the UUAA Authorization Payload for the UAV consumption.
NOTE 1: The USS stores a mapping between CAA-Level UAV ID and the External Identifier (i.e. GPSI as defined in clause 4.5.3). The External Identifier (GPSI) and/or UAV IP Address can be used at a later point by the USS for accessing various services exposed by 3GPP network e.g. location information retrieval, monitoring event configuration, requesting dedicated policies for e.g. C2, etc.
5. The UAS NF/NEF confirms the successful Authentication/Authorization of the PDU Session. The UAS NF/NEF stores the UUAA result together with the GPSI. UAS NF/NEF forwards the Authentication/Authorization result, a Service Level Device Identity containing the authorized CAA-Level UAV ID and the Authorization Data (i.e. the UUAA Authorization Payload), if received from the USS, to the SMF.
6. [Conditional] If the authentication/authorization is successful, the USS shall subscribe to the PDU Session Status Event as described in steps 1-5 in Figure 4.15.3.2.3-1 of TS 23.502 [3]. This step can be executed in parallel to step 4. The UAS NF/NEF determines the DNN, S-NSSAI to subscribe to the PDU Session Status Event notification as specified in clause 5.2.3.1.
7. The PDU Session establishment continues with steps 7 to 21 in Figure 4.3.2.2.1-1 of TS 23.502 [3] and completes. In the step 7b in Figure 4.3.2.2.1-1of TS 23.502 [3], if the SMF receives the DN Authorization Profile Index from the UAS NF/NEF, it sends the DN Authorization Profile Index to retrieve the PDU Session related policy information (described in clause 6.4 of TS 23.503 [9]) and the PCC rule(s) (described in clause 6.3 of TS 23.503 [9]) from the PCF. If the SMF receives the DN authorized Session AMBR in from the UAS NF/NEF, it sends the DN authorized Session AMBR within the Session AMBR to the PCF to retrieve the authorized Session AMBR (described in clause 6.4 of TS 23.503 [9]).
The SMF transfers the Authentication/Authorization result, the Service Level Device Identity containing the authorized CAA-Level UAV ID and the Authorization Data (i.e. the UUAA Authorization Payload) to the UAV if received from the UAS NF, as in steps 11, 12 and 13 in Figure 4.3.2.2.1-1 of TS 23.502 [3].
If the authentication/ authorization result is a failure, the SMF rejects the PDU session establishment with a proper cause value.
8. [Conditional] If the USS in step 6 subscribed to the PDU Session Status Event the SMF will, as described in steps 6-7 in Figure 4.15.3.2.3-1 of TS 23.502 [3], detect when the PDU Session is established and send the PDU Session Establishment event report to the UAS NF/NEF by means of Nsmf_EventExposure_Notify message, including GPSI and the UE IP Address. Then, the UAS-NF/NEF forwards the event message to the USS.
If UUAA-SM fails during a Re-authentication and Re-authorization and the USS has indicated that the network resources can be released, SMF may trigger PDU Session release for UAS services with a proper cause value.
NOTE 2: When the UUAA-SM fails during a Re-authentication and the USS has not indicated that the network resources can be released, the USS can initiate UUAA revocation as described in clause 5.2.7.
NOTE 3: If C2 information reference is available from USS during the initial PDU Session Establishment procedure the SMF can interact with the PCF to set up a predefined PCC rule(s) profile for the C2 communication.
If the PDU session is released as per clause 4.3.4 of TS 23.502 [3] then the SMF shall notify the UAS NF/NEF about the PDU Session Status event (as specified in clause 4.15.3.2.3 of TS 23.502 [3]). Then the UAS NF/NEF may clear the UUAA-SM context and notify the USS about the PDU session release.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.