Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 33.854  Word version:  17.0.0

Top   Top   Up   Prev   None
1…   5…

 

5  Key issues

6  Proposed solutions

6.0  Mapping of solutions to key issues

6.1  Solution #1: UAS authentication and authorizationWord‑p. 16

6.2  Solution #2: UAS authentication and authorization using User Plane

6.3  Solution #3: UAV authentication and authorization by USS/UTM during Registration

6.4  Solution #4: UAV authentication and authorization using EAP-based PDU secondary authenticationWord‑p. 26

6.5  Solution #5: UAV authentication and authorization and pairing authorization using API-based PDU secondary authentication

6.6  Solution #6: Obtaining UAV location information from the PLMNWord‑p. 32

6.7  Solution #7: UAS authentication, authorization and security aspects

6.8  Solution #8: Using 5G location result for location information verification

6.9  Solution #9: UAS enabled authentication

6.10  Solution #10: Authentication and authorization of UAVsWord‑p. 41

6.11  Solution #11: UAV and UAVC pairing authorization through bound IDs

6.12  Solution #12: UAV location privacy protection

6.13  Solution #13: Authorization of UAV/UAVC when connected to EPSWord‑p. 47

6.14  Solution #14: Authorization of UAV/UAVC pairing when connected to 5GS

6.15  Solution #15: UAV and UAV-C Pairing Authorization and Security AspectsWord‑p. 53

6.16  Solution #16: Preventing malicious revocation from unauthorized UTM/USS

7  Conclusions

$  Change historyWord‑p. 62


Up   Top