Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 33.833  Word version:  13.0.0

Top   Top   Up   Prev   Next
1…   4…   7…   A…

 

7  Key Issues for Rel-13p. 96

7.1  Key Issues on ProSe Relaysp. 96

7.2  Key Issues on One-to-one Communicationsp. 99

7.3  Key Issues on Direct Discoveryp. 101

7.4  Key Issues on ProSe Direct Discovery (Public Safety use)p. 105

8  Solutions for Rel-13p. 105

8.1  Solutions on ProSe Relaysp. 105

8.1.1  Solution #8.1.1 UE-to-Network relay discoveryp. 105

8.1.2  Solution #8.1.2 Security between Remote UE and UE-to-Network Relay using GBA push for direct communication keyp. 107

8.1.3  Solution #8.1.3 Security between Remote UE and UE-to-Network relay using GBA push for transport of direct communication keyp. 110

8.1.4  Solution #8.1.4 Security between Remote UE and UE-to-Network Relay using PC4a interface to generate Direct Communication keyp. 113

8.1.5  Solution #8.1.5 Security between Remote UE and UE-to-Network Relay based on the secure transfer of Direct Communication key generated using PC4ap. 114

8.1.6  Solution #8.1.6 Security between Remote UE and UE-to-Network Relay using pre-shared key (PGK)p. 117

8.1.7  Solution #8.1.7: UE-Network Relay security using pre-allocated symmetric keyp. 122

8.1.8  Solution #8.1.8: UE-Network Relay security using normal GBA for direct communication keyp. 126

8.1.9  Solution #8.1.9: UE-Network Relay security using normal GBA for transport of direct communication keyp. 127

8.1.10  Solution #8.1.10: Security of Relay Service Codep. 127

8.1.11  Solution #8.1.11: Authentication and Key Agreement for one-to-one Communication between Remote UE and UE-Network Relay using identity-based cryptographyp. 128

8.1.12  Solution #8.1.12 Security for UE-to-Network Relay using GBA and GBApushp. 131

8.2  Solutions for one-to-one communicationsp. 134

8.2.1  Solution for one-to-one communications with at least one UE in coveragep. 134

8.2.2  Solutions for one-to-one communications with both UEs out of coveragep. 143

8.2.3  Media layer solutionsp. 153

8.3  Solutions for direct discovery (non-Public Safety)p. 153

8.3.1  Solution #8.3.1: Authorisation for restricted ProSe direct discoveryp. 153

8.3.2  Solution #8.3.2: Security for restricted discoveryp. 153

8.3.3  Solution #8.3.3 ProSe Restricted Discovery in Model B with Match Report procedures initiated by Discoveree UE and Discoverer UEp. 155

8.3.4  Solution #8.3.4: Integrity protection of the ProSe code for restricted discovery (Model A)p. 159

8.3.5  Solution #8.3.5 ProSe Restricted Discovery in Model B with Match Report procedure initiated by Discoverer UE onlyp. 160

8.3.6  Solution #8.3.6 ProSe Restricted Discovery in Model B with local MIC Checkingp. 165

8.3.7  Solution #8.3.7: Security for Restricted ProSe Direct Discoveryp. 170

8.3.8  Solution #8.3.8: Security for Restricted ProSe Direct Discovery (Model B)p. 172

8.3.9  Solution #8.3.9 Obtaining the security parameters needed for ProSe Restricted Discoveryp. 177

8.3.10  Solution #8.3.10: Confidentiality of ProSe identifiers in PC5 interfacep. 181

8.3.11  Solution #8.3.11 Protecting a Restricted Discovery Message (Model A and Model B)p. 183

8.3.12  Solution #8.3.12: Security for PC2 interface in Restricted Direct Discoveryp. 187

8.3.14  Solution #8.3.14: Hint of scrambling keyp. 190

8.3.15  Solution #8.3.15 Protecting a Restricted Discovery Message (Model A and Model B)p. 191

8.3.16  Solution #8.3.16: Masked UTC counterp. 195

8.4  Solutions for Direct Discovery (public safety use)p. 196


Up   Top   ToC