| |
Figure 4.2.2-1 | Logical 5GS and EPS architecture for UAV |
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 |
Figure 4.2.3-1 | 5G System non-roaming architecture for UAVs and for A2X communication over PC5 and Uu reference points |
Figure 4.2.4-1 | 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 |
Table 4.4.1.1.1-1 | NF Services provided by NEF |
Table 4.4.1.2.1-1 | NF Services provided by AF |
Figure 5.2.2.1-1 | UUAA in the context of the Registration procedure (UUAA-MM) |
Figure 5.2.2.2-1 | UUAA-MM procedure |
Figure 5.2.3.2-1 | UUAA during PDU Session Establishment |
Figure 5.2.3.3-1 | UUAA during PDN connection establishment at Attach procedure in EPS |
Figure 5.2.3.4-1 | UUAA during the UE requested PDN connectivity procedure in EPS |
Figure 5.2.4.1-1 | UAV Re-authentication procedure in 5GS |
Figure 5.2.4.2-1 | UAV Re-authentication procedure in EPS |
Figure 5.2.4.3-1 | UAV Re-authorization procedure in 5GS |
Figure 5.2.4.4-1 | UAV Re-authorization procedure in EPS |
Figure 5.2.5.2.2-1 | PDU Session modification for C2 communication (common PDU session for UAS services) |
Figure 5.2.5.2.3-1 | PDU Session establishment for C2 communication (separate PDU Sessions for UAS services) |
Figure 5.2.5.3.1-1 | UE requested PDN Connectivity for C2 authorization |
Figure 5.2.5.3.2-1 | UE requested bearer resource modification of an existing PDN connection for C2 authorization |
Figure 5.2.5.4.1-1 | USS initiated C2 pairing policy configuration in 5GS |
Figure 5.2.5.4.2-1 | USS initiated C2 pairing policy configuration in EPS |
Figure 5.2.7.1-1 | Procedure for UAV authorization revocation by USS |
Figure 5.2.8-1 | UAV-C replacement procedure |
Figure 5.2.8.2-1 | UAV controller replacement in EPS |
Figure 5.2.9.1-1 | Revocation of C2 connectivity in 5GS |
Figure 5.2.9.2-1 | Revocation of C2 connectivity in EPS |
Figure 5.3.2-1 | UAV Location Reporting |
Figure 5.3.3-1 | UAV Presence Monitoring |
Figure 5.3.4-1 | List of Aerial UEs in a geographic area |
Figure 5.6.1-1 | DAA procedure based on PC5 |
Figure 5.7.1-1 | Logical architecture for ground based DAA |
Figure 5.7.2-1 | High-level procedure for Ground-based DAA for an Area |
Figure 5.12.2-1 | Procedure for NEF Assisted Pre-flight Planning |
Figure 5.12.3-1 | Procedure for NEF Assisted In-flight Monitoring |
Figure 5.13.2-1 | Procedure for UAV changeover from one USS to another serving different geographical areas |
Figure 5.14.2-1 | Procedure for UAV/UAV-C Triggered Network-assisted DAA |
Figure 5.14.3-1 | Procedure for AAM Triggered Network-assisted DAA |
Figure 5.14.4-1 | Procedure for USS Triggered Network-assisted DAA |
Figure 5.16.2-1 | Procedure for instructing aerial UEs for altitude reporting |
Figure 5.16.3-1 | Procedure for reporting of UE's altitude information |
Figure 6.1.2.2-1 | 5G System architecture for AF-based service parameter provisioning for A2X communications |
Table 6.2.4.1-1 | Standardized PQI values to QoS characteristics mapping |
Figure 6.3.1.1-1 | User Plane for NR PC5 reference point |
Figure 6.3.2.3-1 | UE triggered A2X Policy provisioning procedure |
Figure A.1-1 | Procedure for PDU Session establishment for C2 redundant |
Figure A.2-1 | Architecture for achieving C2 communication reliability via redundant (disjoint) user plane paths |
Figure A.2-2 | Reliability group-based redundancy concept in RAN |