Page 9 - 3GPP_Highlights_I4

The work in CT Working Groups focused on specifying support
for the following features:

UAV remote identification: C2 communication over cellular connectivity:
The CAA (Civil Aviation Administration)-Level UAV ID was C2 communication over cellular connectivity consists of
introduced in the 3GPP system. It is a globally unique, electronically the UAV establishing a user plane connection to receive
and physically readable, and tamper resistant identification which C2 messages from a UAVC, or to report telemetry data to a
allows the receiving entity to address the correct USS for retrieval of UAVC. Authorization for C2 communication by the USS is
UAV information and can be assigned solely by the USS, via means required and includes authorization for pairing of the UAV
outside the scope of 3GPP, or assigned by the USS with assistance with a UAVC, as well as flight authorization for the UAV.
from 3GPP system, whereby the USS delegates the role of “resolver”
of the CAA-Level UAV ID to the UAS NF. C2 communication authorization may be performed:
UAV USS authentication and authorization (UUAA): • during the UUAA procedure (if UUAA is carried out at
PDU session/PDN connection establishment) when the UAV
The first step for the owner of the UAV is to register the UAV with requests establishment of a PDU Session/PDN connection for
the USS, via a procedure outside the scope of 3GPP, which can take both UAS services and C2 communication
place offline or using internet connectivity. During this procedure,
the CAA-level UAV ID is configured in the UAV and the aviation- • during PDU session modification/UE requested bearer
level information (e.g. UAV serial number, pilot information, UAS resource modification when the UAV requests to use an
operator, etc.) is provided to the USS. existing PDU session/PDN connection for C2 communication
The UE at the UAV then registers with the 3GPP system by using • during a new PDU session/PDN connection establishment,
existing procedures for 3GPP primary authentication, with the MNO if the UAV requests to use a separate PDU Session/PDN
credentials stored in the USIM. connection for C2 communication
After successful authentication of the UE, the UUAA procedure is To support this, CT1 extended the PDU session establishment
performed, to enable the 3GPP Core Network to verify that the UAV and modification procedures in TS 24.501 to enable inclusion
has successfully registered with the USS. In 5GS, this procedure of the CAA-level UAV ID and an application layer payload
can take place during the 3GPP registration, or during the containing information for UAVC pairing and for UAV flight
establishment of a PDU session for UAS services. authorization in the Service-level-AA container carried in
the PDU Session Establishment Request and PDU Session
For the former, CT1 extended the registration procedure in Modification Request messages. The ePCO Information
TS 24.501 to enable the UE to indicate its CAA-Level UAV ID into Element in TS 24.008 was also extended to enable it to
a new container (Service-level-AA container) included in the include the above-mentioned information.
Registration Request message, which triggers the AMF to initiate
UUAA with the USS by invoking the Nnef_Authentication service UAV location reporting and tracking
toward the UAS NF, as specified by CT4 in new specification UAV location reporting and tracking was specified by CT3
TS 29.256, and the UAS NF to invoke the Naf_Authentication service and CT4 by re-using the existing Nnef_EventExposure service
toward the USS, as specified by CT3 in new specification TS 29.255.
specified in TS 29.522 with the UAS NF acting as NEF/SCEF
For the latter, CT1 extended the PDU session establishment and interacting with other network functions (e.g. GMLC and
procedure in TS 24.501 to enable the UE to indicate its CAA-Level AMF/MME) to support UAV tracking. The following tracking
UAV ID via the Service-level-AA container included in the PDU modes were specified:
Session Establishment Request message, which triggers the
SMF to initiate UUAA with the USS via the UAS NF by invoking • UAV location reporting mode: the USS subscribes to the
the services mentioned above. In order to enable exchanging UAS NF UAV to be notified of the location of the UAV, and
the authentication messages between the UE and the USS, CT1 can indicate the required location accuracy and whether the
specified a new Session Management procedure in TS 24.501, request is for immediate reporting or deferred reporting (e.g.
in which the SMF sends a Service-level Authentication Command periodic reporting)
to the UE in a Downlink NAS Transport message. The UE replies to • UAV presence monitoring mode: the USS subscribes
this command with a Service-level Authentication Complete carried for the event report of UAV moving in or out of a given
in an Uplink NAS Transport message. In EPS, the UUAA procedure geographic area
takes place during PDN connection establishment, and the
information exchanged to that end between the UAV and the PGW • List of Aerial UEs in a geographic area: the USS
is carried in the Service-level-AA container included in the ePCO. requests the UAS NF for reporting a list of the UAVs in given
geographic area and served by the PLMN.

|
Issue 04 - Ma y 2 022 09