Content for TR 33.854 Word version: 17.1.0
6 Proposed solutions p. 15
6.0 Mapping of solutions to key issues p. 15
| Solutions | KI#1 | KI#2 | KI#3 | KI#4 | KI#5 | KI#6 | KI#7 |
|---|---|---|---|---|---|---|---|
| #1: UAS authentication and authorization | x | ||||||
| #2: UAS authentication and authorization using User Plane | x | ||||||
| #3: UAV authentication and authorization by USS/UTM with AMF as authenticator | x | ||||||
| #4: UAV authentication and authorization using EAP-based PDU secondary authentication | x | ||||||
| #5: UAV authentication and authorization using API-based PDU secondary authentication | x | x | x | x | |||
| #6: Obtaining UAV location information from the PLMN | x | ||||||
| #7: UAS authentication, authorization and security aspects | x | x | |||||
| #8: Using 5G location result for location information verification | x | ||||||
| #9: UAS enabled authentication | x | ||||||
| #10: Authentication and authorization of UAVs | x | ||||||
| #11: UAV and UAVC pairing authorization through bound IDs | x | ||||||
| #12: UAV location privacy protection | x | x | x | ||||
| #13: Authorization of UAV/UAVC when connected to EPS | x | x | |||||
| #14: Authorization of UAV/UAVC pairing when connected to 5GS | x | ||||||
| #15: UAV and UAV-C Pairing Authorization and Security Aspects | x | x | |||||
| #16: Preventing malicious revocation from unauthorized UTM/USS | x |
