hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9e07bd31ffc5059c64f2a6b357d833b6 | 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 Req... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.2 UUAA at Registration in 5GS (UUAA-MM)
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 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 t... |
9e07bd31ffc5059c64f2a6b357d833b6 | 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/N... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.3 UUAA At PDN Connection/PDU Session Establishment (UUAA-SM)
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 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 com... |
9e07bd31ffc5059c64f2a6b357d833b6 | 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.... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.3.3 USS UAV Authorization/Authentication (UUAA) during default PDN connection at Attach
| In the figure 5.2.3.3-1 the execution of the UUAA is specified for the scenario where UUAA-SM is performed at Attach.
Figure 5.2.3.3-1: UUAA during PDN connection establishment at Attach procedure in EPS
0. Steps 1 - 13 in TS 23.401 [6] figure 5.3.2.1-1 and steps 1 - 2 in TS 23.502 [3] figure 4.11.1.5.2-1 or clause... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.3.4 USS UAV Authorization/Authentication (UUAA) using UE requested PDN connectivity procedure
| In the figure 5.2.3.4-1, the execution of UUAA during the UE requested PDN connectivity procedure is specified for the scenario where UUAA-SM is not performed at Attach.
Figure 5.2.3.4-1: UUAA during the UE requested PDN connectivity procedure in EPS
0. Steps 1-2 in figure 4.11.1.5.4.1-1 of TS 23.502 [3] and steps ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.4 UUAA Re-authentication and Re-authorization by USS/UTM
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.4.1 UAV Re-authentication procedure in 5GS
|
Figure 5.2.4.1-1: UAV Re-authentication procedure in 5GS
UAS NF stores the UE UUAA context after successful UUAA procedure as explained in clause 5.2.2.2 for UUAA-MM and in clause 5.2.3 for UUAA-SM procedure. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF depending on deployments.
... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.4.2 UAV Re-authentication procedure in EPS
|
Figure 5.2.4.2-1: UAV Re-authentication procedure in EPS
UAS NF stores the UE UUAA context after successful UUAA-SM procedure as explained in clause 5.2.3. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF depending on deployments.
1. The USS sends a Naf_Authentication_Notification r... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.4.3 USS initiated UAV Re-authorization procedure in 5GS
|
Figure 5.2.4.3-1: UAV Re-authorization procedure in 5GS
UAS NF stores the UE UUAA context after successful UUAA procedure as explained in clause 5.2.2.2 for UUAA-MM and in clause 5.2.3 for UUAA-SM procedure. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF depending on deployments.
... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 3a For UUAA-MM re-authorization, the UAS-NF/NEF sends a Nnef_Authentication_Notification request including the CAA-Level UAV ID and the authorization message to the serving AMF.
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 3b For UUAA-SM re-authorization or C2 re-authorization, the UAS-NF/NEF sends a Nnef_Authentication_Notification request to the SMF serving the UUAA or C2 for the UE which includes the corresponding PDU session identity, CAA-Level UAV ID and the authorization message.
| 4. The UAS NF responds back to the USS indicating that re-authorization request has been successfully initiated.
5a. In the case of UUAA-MM:
If the UE is in CM_Idle state, the AMF initiates the Network Triggered Service Request procedures as described in clause 4.2.3.3 of TS 23.502 [3].
The AMF delivers the CAA-Le... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5b In the case of UUAA-SM or C2 re-authorization:
| The SMF identifies, based on the received information, the PDU Session that is serving the UUAA-SM or C2 re-authorization and invokes the Network Requested PDU Session Modification procedure (figure 4.3.3.2-1 of TS 23.502 [3] triggering event SMF Requested modification) by sending Namf_Communication_N1N2MessageTransfe... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.4.4 USS initiated UAV Re-authorization procedure in EPS
|
Figure 5.2.4.4-1: UAV Re-authorization procedure in EPS
UAS NF/NEF stores the UE UUAA context after successful UUAA procedure as in clause 5.2.3 for UUAA-SM procedure. The UUAA context may be stored in the UDSF or may be stored locally in the UAS NF/NEF depending on deployments.
1. The USS sends a request to UAS NF... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5 Authorization for C2 over Uu
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.1 General
| Authorization for C2 is required when a UAV establishes a user plane connection for C2 operations, i.e. to deliver messages with information of command and control for UAV operations from a UAV-C or USS to a UAV or to report telemetry data from a UAV to its UAV-C. Two sides of C2 communication, i.e. UAV and UAV-C, belo... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.2 Procedure for C2 authorization in 5GS
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.2.1 C2 Authorization request during UUAA-SM procedure in 5GS
| If C2 authorization is requested during the UUAA-SM procedure the procedure described in clause 5.2.3.2 takes place with the following additions:
- In Step 0, the UE includes pairing information (if available) in a C2 Aviation Payload. which is forwarded further to the USS;
- In step 4, the USS performs C2 authorizat... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.2.2 UE initiated PDU Session Modification for C2 Communication
| C2 authorization is requested at PDU session Modification:
- After UUAA-SM is performed and a common PDU session is used for connectivity to USS and C2 communication to a UAV-C (as configured in the UAV); or
- If the UE has already established a PDU session for C2 communication to a UAV-C.
Figure 5.2.5.2.2-1: PDU ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.2.3 UE initiated PDU Session Establishment for C2 Communication
| If C2 authorization is requested during PDU session establishment to a PDU session used specifically for C2 communication to UAV-C the UAV requests C2 authorization as follows.
Figure 5.2.5.2.3-1: PDU Session establishment for C2 communication (separate PDU Sessions for UAS services)
0. The UAV has performed a succ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.3 Procedure for C2 authorization in EPS
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.3.0 C2 Authorization request during UUAA-SM procedure in EPS
| If C2 authorization is requested during the UUAA-SM procedure the procedure described in clause 5.2.3.3 takes place with the following additions:
- In step 0, the UE includes pairing information (if available) in a C2 Aviation Payload, which is forwarded further to the USS.
- Initially in step 5, the USS performs C2 ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.3.1 UE requested PDN connectivity for C2 authorization
| When the UAV requests to establish connectivity to an additional PDN over E-UTRAN for C2, the procedure described in clause 5.10.2 of TS 23.401 [6] takes place with the following modifications:
Figure 5.2.5.3.1-1: UE requested PDN Connectivity for C2 authorization
0. The UAV has performed a successful UUAA with the... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.3.2 UE requested bearer resource modification of an existing PDN connection for C2 authorization
| C2 authorization is requested at UE requested bearer resource modification (see clause 5.4.5 of TS 23.401 [6]):
- After UUAA-SM is performed and a common PDN Connection is used for connectivity to USS and C2 communication to a UAV-C (as configured in the UAV); or
- If the UE has already established a PDN Connection f... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.4 USS initiated C2 pairing policy configuration
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.4.1 USS initiated C2 pairing policy configuration in 5GS
| The USS initiated C2 pairing policy configuration Figure 5.2.5.4.1-1.
Figure 5.2.5.4.1-1: USS initiated C2 pairing policy configuration in 5GS
0. The UAV is registered in the network and a PDU session is established as specified in clause 5.2.3.2.
1. The USS initiates the PDU Session modification by invoking the N... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.5.4.2 USS initiated C2 pairing policy configuration in EPS
| The USS initiated C2 pairing policy configuration in EPS figure 5.2.5.4.2-1.
Figure 5.2.5.4.2-1: USS initiated C2 pairing policy configuration in EPS
0. The UAV is registered in the network and a PDN Connection is established as specified in clause 5.2.3.3.
1. The USS initiates the PDN Connection modification by i... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.6 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.7 UUAA Revocation by USS/UTM
|
Figure 5.2.7.1-1: Procedure for UAV authorization revocation by USS
UAS NF stores the UAV UE's UUAA context after successful UUAA procedure as explained in clause 5.2.2.2 for UUAA-MM and in clause 5.2.3.2 for UUAA-SM procedure.
1. The USS sends Naf_Authentication_Notification to UAS NF for authorization revocation.... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.8 UAV Controller Replacement
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.8.1 UAV controller replacement in 5GS
| If USS determines that UAV controller replacement is required the USS invokes an Nnef_AFsessionWithQoS_Update service operation to the UAS NF including in the request authorization information (i.e. new pairing information). NEF authorizes the request from the USS followed by interacting with PCF triggering a Npcf_Poli... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.8.2 UAV controller replacement in EPS
| The procedure for UAV-C replacement in EPS is as follows:
Figure 5.2.8.2-1: UAV controller replacement in EPS
0. UAV is attached to EPC with a PDN connection established
1. The USS determines that the UAV-C controlling the UAV needs to be replaced (e.g. if the UAV is misbehaving).
2. USS initiates the Nnef_AFSess... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.9 Revocation of C2 Connectivity
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.9.1 Revocation of C2 connectivity in 5GS
| When the USS decides to revoke an existing C2 connection between the UAV and UAV-C the USS invokes an Nnef_AFsessionWithQoS_Revoke request to NEF in order to revoke the AF request as described in Figure 5.2.9.1-1.
Figure 5.2.9.1-1: Revocation of C2 connectivity in 5GS
0. USS decides to revoke C2 connectivity.
1. U... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.2.9.2 Revocation of C2 connectivity in EPS
| The procedure is as follows:
Figure 5.2.9.2-1: Revocation of C2 connectivity in EPS
0. USS decides to revoke C2 connectivity.
1. Steps 1 - 2 as described in Figure 5.2.9.1-1 are performed.
2. The PCF deletes policy information associated with the AF session and configures the resources and routing information as ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3 UAV Tracking
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.1 UAV Tracking Model
| 3GPP network supports the functionality of UAV Tracking via the service exposure support towards USS. The USS invokes 3GPP network service through a UAS-NF for UAV tracking. The UAS-NF acts as an NEF/SCEF and interacts with other network functions (e.g. GMLC and AMF/MME) to support UAV tracking. The USS shall use 3GPP ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.1.1 UAV Location Reporting Mode
| For UAV location reporting mode, the USS/TPAE that wants to be reported on the UAV location subscribes to the UAS NF with the target 3GPP UAV ID. The USS/TPAE could indicate the required location accuracy, reliable UE location information required and whether it's for immediate reporting or deferred reporting (e.g. per... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.1.2 UAV Presence Monitoring Mode
| For UAV presence monitoring mode, the USS/TPAE may subscribe for the event report of UAV moving in or out of the geographic area (e.g. longitude/latitude, zip code, etc). The request includes target 3GPP UAV ID, indication of reliable UE location information required and geographic area info.
If the requested geograph... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.1.3 List of Aerial UEs in a geographic area
| In this mode, the USS/TPAE requests UAS NF for a list of the UAVs in the geographic area and served by the PLMN (i.e. no 3GPP UAV ID provided by the USS/TPAE). The request includes geographic area info, indication of reliable UE location information required and indication of one-time reporting by setting "maximumNumbe... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.2 Procedure for UAV location reporting
| The following procedures describe the 5GC UAV's location reporting service to USS.
Figure 5.3.2-1: UAV Location Reporting
1. USS to UAS NF/NEF: The USS sends Nnef_EventExposure_Subscribe request to the UAS NF/NEF as described in step 1b-1 from clause 6.1.2 of TS 23.273 [8] for immediate location reporting (i.e. 5... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.3 Procedure for UAV presence monitoring
| The following procedures describe the 3GPP UAV presence monitoring mode operation.
Figure 5.3.3-1: UAV Presence Monitoring
1. USS to UAS NF/NEF: The USS initiates the UAV presence monitoring request via the Nnef_EventExposure_Subscribe service operation to UAS NF/NEF to subscribe to the target UAV presence events f... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.3.4 Procedure for obtaining list of Aerial UEs in a geographic area
| This procedure may be used by USS/TPAE to obtain a list of the UAVs in a geographic area and served by the PLMN. The USS/TPAE provides the geographic area information to the UAS-NF. Based on the received information, the UAS NF may either trigger the AMF/MME monitoring event configuration procedure with event ID "Numb... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4 Direct C2 Communication
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.1 General
| A UAV that supports Direct C2 Communication may establish direct PC5 link with a UAV-C. Only NR PC5 is supported for Direct C2 Communication. The UAV that is engaged in Direct C2 Communication may or may not be capable of connection with 3GPP network. The UAV is authorized by the USS for establishing Direct C2 Communic... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.2 Authorization policy for A2X Direct C2 Communication service
| Authorization policy parameters as described in clause 6.2.1.2.1 for A2X are leveraged using a service type indicating Direct C2 Communication where applicable.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.3 Procedure for C2 authorization by the USS for using the A2X Direct C2 Communication service
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.3.1 General
| If the UAV is capable of 3GPP network connection and is served by a PLMN, the UAV performs the Direct C2 Communication authorization either as part of the UUAA-MM procedure in 5GS described in clause 5.2.2 or as part of the C2 Authorization during UUAA-SM procedure described in clause 5.2.5. In either case, if the UAV ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.3.2 Authorization of Direct C2 Communication service via UUAA-MM
| In 5GS, the UUAA-MM procedure may be used to authorize direct C2 communication described in clause 5.2.2 with the following enhancements:
- In step 1 of clause 5.2.2.1: When the UAV needs to establish a direct PC5 link required for connectivity to UAV-C (i.e. Direct C2 Communication), the UAV may include an authorizat... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.3.3 Authorization of Direct C2 Communication service via UUAA-SM
| In 5GS, the following procedures are used to request C2 authorization for Direct C2 Communication to the USS:
- The procedure for C2 Authorization request during UUAA-SM procedure in 5GS as specified in clause 5.2.5.2.1 with the following enhancements:
- In step 0: When the UAV needs to establish a direct PC5 link re... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.4.4 Procedure for Direct C2 Communication establishment
| The procedures for Direct C2 Communication leverages A2X Unicast mode communication over PC5 reference point as defined in clause 6.2.2.1.3 and clause 6.3.3.2.
To establish Direct C2 communication the procedure for A2X unicast mode Layer-2 link establishment over PC5 reference point as defined by clause 6.3.3.2 and th... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5 Broadcast Remote ID
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.1 Broadcast Remote ID using PC5
| Broadcast Remote ID leverages A2X broadcast communication mode as defined in clauses 6.2.2.1.2 and 6.3.3.1, for both UAV UEs that register to the MNO network(s) and UAVs that operate out of coverage.
The content of the messages for BRID is defined according to regional regulations for BRID (e.g. message set of ASTM F3... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.2 Broadcast Remote ID using MBS
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.2.1 Policy/Parameter provisioning
| Policy parameters provisioning as described in clause 6.2.1.3 for A2X communication over Uu reference point is leveraged. Where applicable an A2X service type indicating Broadcast Remote ID is used.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.2.2 Broadcast Remote ID reception via MBS
| The A2X Broadcast Remote ID service is identified with a corresponding service type.
The Broadcast Remote ID sent by a UAV UE to an A2X application server identified by A2X service type set to Broadcast Remote ID is as a A2X message routed to UAV UEs via MBS sessions using the mechanisms and procedures described in cl... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.2.3 QoS handling
| QoS is handled as described in clause 6.2.4.2 for delivery of A2X message over MBS.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.5.2.4 MBS service area mapping
| Broadcast Remote ID using MBS facilitates procedures and mechanisms for MBS service area mapping for A2X communication with MBS as specified in clause 6.3.4.2.1 in accordance with:
- UE applies to a UAV UE.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.6 Mechanisms for Detect and Avoid (DAA)
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.6.1 Mechanisms for Detect and Avoid (DAA) based on PC5
| DAA leverages procedures and mechanisms as defined for A2X in clause 6. This includes the corresponding references to TS 23.287 [11] below.
NOTE 1: The content of the messages for DAA are defined according to the regional regulations for DAA and is out of scope of 3GPP.
The detection and deconfliction of potential co... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.7 Ground-based DAA for an Area
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.7.1 Functional Description
| This clause provides a network-assisted (ground based) DAA mechanism. It is applicable for a specific area, such as a stadium or arena where UAVs are used e.g. for filming an event. It is based on a ground-based entity, Area Airspace Manager (AAM), that is able to detect UAVs in the specific area and provide local stee... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.7.2 Procedures
|
Figure 5.7.2-1: High-level procedure for Ground-based DAA for an Area
Ground-based DAA for an area leverages the procedures and mechanisms defined for A2X. Any references to TS 23.287 [11] made in this clause shall be interpreted in accordance with corresponding definitions and descriptions for A2X in clause 6.
Pre... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.8 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.9 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.10 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.11 Void
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.12 Pre-flight Planning and In-flight Monitoring for UAVs
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.12.1 General
| 5G network may support pre-flight planning and in-flight monitoring for UAVs via the NEF service exposure. The USS/UTM may request assistance information to NEF of pre-flight planning and in-flight monitoring for UAV, after the UAV establishes user plane connection with the USS/UTM.
In the case of pre-flight planning,... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.12.2 Procedure for NEF Assisted Pre-flight Planning
|
Figure 5.12.2-1: Procedure for NEF Assisted Pre-flight Planning
1. The UAV establishes a PDU Session for communication with the USS/UTM as described in clause 5.2.3.
2. (via application layer) The UAV requests the pre-flight planning service from the USS/UTM.
3. The USS/UTM determines to request a pre-flight assis... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.12.3 Procedure for NEF Assisted In-flight Monitoring
|
Figure 5.12.3-1: Procedure for NEF Assisted In-flight Monitoring
NOTE: The NFs in Figure 5.12.3-1 represents all the other NFs beside GMLC and NEF/UAS NF involved in the procedure.
1. The USS/UTM sends an Nnef_UAVFlightAssistance_Create request with an indication to provide the in-flight monitoring of a target UAV ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.13 Multiple USS serving different geographical areas
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.13.1 USS changeover
| In cases when a UAV moves over geographical areas served by different USSs, a 3GPP network may assist the UAV UE to perform a changeover from one USS to another. The following describes the interactions in order to perform the changeover:
- USS can serve the UAV within its geographical area and each USS may have an ov... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.13.2 Procedure for USS changeover during a UAV flight
| Procedure for USS changeover in cases when a UAV moves over geographical areas served by different USS is shown in Figure 5.13.2-1.
NOTE 1: This procedure can be used in conjunction with the NEF-assisted pre-flight planning as specified in clause 5.12.
NOTE 2: USS changeover is independent of AMF(s) or NEF(s) changes... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.14 Support of Network-Based/Assisted DAA
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.14.1 Functional Description
| This clause provides a network-based/assisted DAA mechanism. To enable NWDAA, the following information can be utilised:
- Absolute location of a UAV provided by the LoCation Service;
- Relative Location of UAVs provided by the Ranging Service;
- Output of Relative Proximity Analytics provided by NWDAF.
Absolute lo... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.14.2 Procedure for UAV Triggered Network-assisted DAA
|
Figure 5.14.2-1: Procedure for UAV/UAV-C Triggered Network-assisted DAA
1. The UAV establishes a PDU Session for communication with the USS as described in clause 5.2.3.
2. The DAA service may be triggered by UAV(s). The UAV(s) (via its paired UAV-C) requests DAA service from USS. The request message includes ident... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.14.3 Procedure for AAM Triggered Network-assisted DAA
|
Figure 5.14.3-1: Procedure for AAM Triggered Network-assisted DAA
1. As described in clause 5.7.2 steps 1-6, the UAV(s) listens for signals on the correspondingly destination Layer-2 ID configured for the used service type. The AAM scans the airspace over the area/arena for UAV(s), retrieves for each detected UAV th... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.14.4 Procedure for USS Triggered Network-assisted DAA
|
Figure 5.14.4-1: Procedure for USS Triggered Network-assisted DAA
1. The UAV and UAV-C establish PDU Session for communication with the USS as described in clause 5.2.3.
2. The USS may decide to trigger NWDAA based on application layer request.
3. The USS requests absolute location of UAV(s) based on the identifie... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.15 Support of No-Transmit Zones
| The following principles are applied to support of NTZ for UAV UEs.
1) NTZ enforcement applies to the UE that is a UAV UE (i.e. an aerial UE that is a UE with aerial subscription).
2) UAV UEs supporting NTZ regulations are configured/provisioned with NTZ assistance information comprising of a mandatory list of the re... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.16 Altitude reporting for aerial UEs
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.16.1 General
| In order to assist a USS/UTM with aerial UE's flight planning and monitoring, the 5GS may enable configuration of aerial UEs (UAVs) to perform altitude reporting. This may include providing aerial UEs with threshold values for altitude reporting and/or request reporting periodicity (e.g. threshold-based, event-based, p... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.16.2 Instructing aerial UEs to perform altitude reporting
| Procedure shown in Figure 5.16.2-1 specifies how the 5GS instructs the aerial UEs (UAVs) to perform altitude reporting, considering requests from a USS/UTM for assistance with UAV's flight. This procedure can be used in conjunction with the NEF-assisted pre-flight planning, in-flight monitoring and USS changeover as sp... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.16.3 Reporting UE's altitude information
| A procedure for reporting aerial UE's altitude information to the core network is shown in Figure 5.16.3-1. The reporting can be done by the aerial UE based on the received altitude reporting thresholds and indication about reporting periodicity as specified in clause 5.16.2.
Figure 5.16.3-1: Procedure for reporting... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 5.16.4 Stop and update altitude reporting for aerial UEs
| Procedure shown in Figure 5.16.4-1 specifies how the 5GS instructs the aerial UEs to stop and/or update their altitude reporting due to a trigger from NG-RAN and/or a request from the USS.
Figure 5.16.4-1: Procedure for instructing aerial UEs to stop/update the altitude reporting
0. The UAV UE is requested to perfo... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6 Aircraft-to-Everything (A2X) services
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1 Architecture model and concepts
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.1 General concept
| There are two modes of operation for A2X communication, namely A2X communication over PC5 reference point and A2X communication over Uu reference point. These two operation modes may be used by a UE independently of different A2X communications.
A2X communications over PC5 reference point are supported by LTE and/or N... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2 Architectural reference model
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.1 PC5 and Uu based A2X architecture reference model
| |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.1.1 Non-roaming 5G System architecture for A2X communication over PC5 and Uu reference points
| Clause 4.2.3 describes the non-roaming architectures for A2X communications.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.1.2 Roaming 5G System architecture for A2X communication over PC5 and Uu reference points
| Clause 4.2.4 describes the roaming architectures for A2X communications.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.1.3 Inter-PLMN 5G System architecture for A2X communication over PC5 reference point
| In the case of inter-PLMN A2X communication over PC5 reference point, the PC5 parameters need to be configured in a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is similar to the one defined in clauses 4.2.3 and 4.2.4.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.2 AF-based service parameter provisioning for A2X communication
| The 5G System provides NEF services to enable communication between NFs in the PLMN and A2X Application Server. Figure 6.1.2.2-1 shows the high level view of AF-based service parameter provisioning for A2X communications. The A2X Application Server may provide A2X service parameters to the PLMN via NEF. The NEF stores ... |
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.3 MBS for Uu based A2X architecture reference model
| A2X leverages what is defined for V2X in TS 23.287 [11] clause 4.2.2A with the following differences:
- V2X is replaced by A2X.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.4 Reference points
| See clause 4.2.6.
|
9e07bd31ffc5059c64f2a6b357d833b6 | 23.256 | 6.1.2.5 Service-based interfaces
| See clause 4.2.5.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.