Content for TR 33.833 Word version: 13.0.0
A Possible post-Rel-13 Key Issues p. 203
A.1 Key Issues on One-to-many communications p. 203
A.1.1 Key Issue #A1.1: Mutual authentication of ProSe enabled devices in group owner mode p. 203
A.1.1.1 Key issue details p. 203
A.1.1.2 Security threats p. 203
A.1.1.3 Potential security requirements p. 203
A.1.2 Key Issue #A1.2: ProSe Communications in Group Owner Mode p. 203
A.1.2.1 Key issue details p. 203
A.1.2.2 Security threats p. 203
A.1.2.3 Potential security requirements p. 204
B Possible post-Rel-13 Solutions p. 205
B.1 Solutions for One-to-many Communications p. 205
B.2 Solutions for One-to-one communications p. 206
B.2.1 Solution #A2.1: Security for direct one-to-one connections p. 206
B.2.1.1 General p. 206
B.2.1.2 Overview of solution p. 206
B.2.1.2.1 General p. 206
B.2.1.2.2 Difference between network independent and network authorized cases p. 206
B.2.1.3 Security parameters p. 208
B.2.1.4 Security procedures p. 209
B.2.2 Solution #A2.2: Security for direct one-to-one connections p. 214
B.2.2.1 General p. 214
B.2.2.2 Overview of solution p. 214
B.2.2.3 D2D authentication and key-agreement using IMS E2E security solutions p. 215
B.2.3 Solution #A2.3: Security for ProSe one-to-one communications p. 217
B.2.3.1 General p. 217
B.2.3.2 IDENTITY Security Solution p. 217
B.2.3.2.1 General p. 217
B.2.3.3 IDENTITY One-to-One communications p. 217
B.2.4 Solution #A2.4: Network assisted key establishment for one-to-one communication p. 222
B.2.4.1 General p. 222
B.2.4.2 Procedure p. 222
B.3 Solutions for Relays p. 223
B.3.1 Solution #A3.1: Security for ProSe communication through UE-to-Network relay with network authorization p. 223
B.3.2 Solution #A3.2: Security for relays p. 225
B.3.2.1 General p. 225
B.3.2.2 Overview of solution p. 225
B.3.2.2.1 Solution description p. 225
B.3.2.2.2 Security Keys p. 226
B.3.2.2.3 Identities p. 226
B.3.2.2.4 Key Derivation and Data Protection p. 226
B.3.2.2.5 Packet Format p. 226
$ Change History p. 227
