Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 33.847  Word version:  17.1.0

Top   Top   Up   Prev   None
1…   4…   6…

 

6  Solutionsp. 29

6.0  Mapping of Solutions to Key Issuesp. 29

6.1  Solution #1: Solution for key management in 5G Proximity Services relay communicationp. 30

6.2  Solution #2: Secure data transfer between UE and 5GDDNMFp. 33

6.3  Solution #3: Reuse LTE security mechanism for 5G ProSe open discoveryp. 34

6.4  Solution #4: Reuse LTE security mechanism for 5G ProSe restricted discoveryp. 37

6.5  Solution #5: Protection of the PC3 interface using AKMA and TLSp. 44

6.6  Solution #6: Key management for UE-to-Network Relays and Remote UE'sp. 46

6.7  Solution #7: Security establishment of one-to-one PC5 communicationp. 50

6.8  Solution #8: Confidential protection against UE-to-UE relay using asymmetric cryptographyp. 52

6.9  Solution #9: Key management in discovery procedurep. 53

6.10  Solution #10: Authorization and security with UE-to-Network relay using Remote UE network primary authenticationp. 54

6.11  Solution #11: Protection of the PC3 interface using GBAp. 62

6.12  Solution #12: Privacy handling for Layer-3 UE-to-UE Relay based on IP routingp. 62

6.13  Solution #13: Secondary Authentication for a Layer 3 Remote UEp. 65

6.14  Solution #14: A security solution for UE-to-Network Relay based on Layer 2 Relayp. 70

6.15  Solution #15: Key management in UE-to-Network Relay based on primary authenticationp. 72

6.16  Solution #16: Security establishment procedures between two UEs in the UE-to-UE relay scenariop. 75

6.17  Solution #17: Solution on securely creating destination Layer-2 ID in groupcast communicationp. 76

6.18  Solution #18: Authorization and PC5 link setup for UE-to-Network relayp. 77

6.19  Solution #19: End-to-end security for the L3 UE-to-Network relayp. 80

6.20  Solution #20: PC5 link setup for UE-to-UE relayp. 82

6.21  Solution #21: 5G PKMF for key management in PC5 communicationp. 83

6.22  Solution #22: Representation of identities during broadcastp. 90

6.23  Solution #23: Initial key with validity timep. 94

6.24  Solution #24: NSSAA for Remote UE with L3 UE-to-Network relayp. 97

6.25  Solution #25: Secondary authentication of Remote UE with L3 UE-to-Network relayp. 104

6.26  Solution #26: Protecting PDU session-related parameters for L2 relay with existing mechanismp. 109

6.27  Solution #27: Mitigating the conflict between security policies using match report proceduresp. 110

6.28  Solution #28: Mitigating the conflict between security policies using restricted discovery procedures on network sidep. 113

6.29  Solution #29: Security flow for Layer-3 UE-to-Network Relayp. 115

6.30  Solution #30: UE-to-Network Relay security based on primary authenticationp. 118

6.31  Solution #31: Use of authorization tokens in UE-to-UE relayp. 121

6.32  Solution #32: Mitigating privacy issues of user info IDs, relay service codes and PDU parameters for L3 UE-to-NW relaysp. 124

6.33  Solution #33: Security establishment of one-to-one PC5 communication rekeyingp. 131

6.34  Solution #34: Authorization of the remote UE in L3 U2N relayp. 132

6.35  Solution #35: Discovery procedures for UE-to-network relaysp. 133

6.36  Solution #36: UE-to-Network Relay security based on AKMAp. 136

6.37  Solution #37: Keying procedures for Group Member and Relay discovery: public safety casep. 138

6.38  Solution #38: Mitigating the conflict between security policies using restricted discovery procedures on network sidep. 141

6.39  Solution #39: Key management in UE-to-Network Relay based on shared key generated during primary authenticationp. 143

6.40  Solution #40: Protection with Security Policies for PC5 Direct Communicationp. 146

6.41  Solution #41: Security protection for 5G ProSe indirect network communicationp. 147

6.42  Solution #42: Privacy enhancements during PC5 link setup for UE-to-Network relayp. 150

6.43  Solution #43: Improved LTE security mechanism for 5G ProSe restricted discovery to ensure source authentication in out of coverage use casesp. 152

6.44  Solution #44: PC5 anchor key generation via GBA Pushp. 156

7  Conclusionsp. 159

$  Change historyp. 165


Up   Top