Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.854  Word version:  17.1.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.1…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.15…   6.16…   7…

 

6.9  Solution #9: UAS enabled authenticationp. 39

6.9.1  Introductionp. 39

This solution addresses the key issue #1 UAS Authentication and Authorization.
When a UAV type UE registers to 5GS, it will after a first successful authentication also register with USS/UTM. The solution proposes to optimize for UAS authentication.

6.9.2  Solution detailsp. 39

When a UAV type UE sends a registration request, it includes in SUCI an indication "UAV type" (step 1) to indicate to the 5GS that additional authentication is needed. After successful authentication, the AUSF provides in its authentication response this UAV type information to AMF (step 2). By this, the AMF knows that the UE is a UAV type UE that also wants to connect to USS/UTM system. I.e. this is to indicate to the serving network the service, for which the UAV enabled UE wants to be authenticated and AMF requests the UAV ID from the UE (step 3).
The 3GPP system is aware of the 'CAA-level UAV ID' and its mapping with 3GPP UAV ID. If the UAV-type UE (UAV/UAV-C) has successfully authenticated to 5GS, it shares within the SMC response its 'CAA level UAV ID' with AMF (step 4).
AMF retrieves 3GPP UAV ID from UDM database (step 5). A mapping of SUPI, CAA level UAV ID and 3GPP UAV ID is performed in UDM (step 6) and 3GPP UAV ID is provided back to AMF (step 7). Now UAV/UAV-C authentication and authorization towards UTM/USS can be triggered by AMF (step 8).
This solution has the following open issues:
  • whether the storage of CAA-level UAV Id in UDM is needed in addition to CAA-level UAV Id storage in UAS NF;
  • which intermediate functions are involved between AMF and USS/UTM; and
  • whether a communication between UAV and UTM is needed in steps 8 and 9.
Copy of original 3GPP image for 3GPP TS 33.854, Fig. 6.9.2-1: UAS enabled authentication flow
Figure 6.9.2-1: UAS enabled authentication flow
(⇒ copy of original 3GPP image)
Up
After successful authentication and authorization by UTM/USS, UAV authentication and authorization response is sent to AMF with external identifier (step 9). In case of failure, UAV Authentication & Authorization response is sent to AMF with a failure status. AMF updates UAV authentication and authorization results to UDM (step 10). Also, the UAV/UAV-C is informed with registration accept or reject message (step 11).
If the UDM did not have an entry for the 'CAA-level UAV ID', i.e. it is a non-registered UAV-type UE, then depending on operator policy the UAV/UAV-C may be registered in UDM, the UE becomes a subscriber for a service and a 3GPP UAV ID is provided.
Up

6.9.3  Evaluationp. 40

This solution has not been evaluated.

Up   Top   ToC