Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TR 23.703
Word version: 12.0.0
1…
4…
6…
6.2
6.3
6.4…
7…
6.4
ProSe Identities
6.5
EPC Support for WLAN Direct Communications
6.6
ProSe Configuration and capabilities handling
6.4
ProSe Identities
p. 213
6.4.1
Solution I1: Solution for ProSe Identifiers for Public Safety Mission Critical Applications using direct discovery
p. 213
6.4.1.1
Length of ProSe Identifiers used for ProSe direct Discovery
p. 213
6.4.1.2
Security considerations for ProSe Identifiers used for ProSe direct Discovery
p. 214
6.4.1.3
Considerations on the identification of applications
p. 214
6.4.1.4
A potential format for direct discovery messages containing ProSe identifiers
p. 215
6.4.1.4a
Impact on existing entities and interfaces
p. 215
6.4.1.5
Solution evaluation
p. 215
6.4.2
Solution I2: ProSe Identities
p. 215
6.4.2.1
Functional description
p. 215
6.4.2.1.1
General
p. 215
6.4.2.1.2
Identity architecture
p. 216
6.4.2.2
Procedures
p. 216
6.4.2.2.1
Application authorization
p. 216
6.4.2.2.2
Registration in order to be discoverable
p. 217
6.4.2.2.3
Authorization for discovery
p. 219
6.4.2.2.4
Discovery event
p. 220
6.4.2.3
Summary
p. 221
6.4.2.3a
Impact on existing entities and interfaces
p. 222
6.4.2.4
Solution evaluation
p. 222
6.4.3
Solution I3: Retrieval of ProSe Identity
p. 222
6.4.3.1
Functional description
p. 222
6.4.3.2
Signalling Flow
p. 223
6.4.3.2.1
Login procedure of ProSe enabled application
p. 223
6.4.3.2.2
Retrieval of ProSe ID for discoverable procedure
p. 224
6.4.3.2.3
Retrieval of ProSe ID for discovery procedure
p. 225
6.4.3.3
Impact on existing entities and interfaces
p. 226
6.4.3.4
Solution evaluation
p. 226
6.4.4
Solution I4: ProSe Identities for ProSe service
p. 226
6.4.4.1
Identity for ProSe discovery
p. 226
6.4.4.1.1
ProSe discovery type and the requirement for ProSe Identities
p. 226
6.4.4.1.2
Application Identity
p. 227
6.4.4.1.3
Application User Identity
p. 227
6.4.4.1.4
ProSe UE Identity
p. 227
6.4.4.1.5
ProSe discovery code
p. 227
6.4.4.2
Identity for ProSe communication
p. 228
6.4.4.2.1
ProSe UE identity
p. 228
6.4.4.2.2
ProSe Group identity
p. 228
6.4.4.2.3
ProSe Source and Destination Identity
p. 228
6.4.4.2.4
ProSe direct Connection Identity
p. 228
6.4.4.3
Impact on existing entities and interfaces
p. 228
6.4.4.4
Solution evaluation
p. 228
6.4.5
Solution I5: Solution with ProSe UE Identifiers targeted towards Public Safety applications
p. 228
6.4.5.1
Definitions
p. 228
6.4.5.2
Assumptions about ProSe UE Identifiers targeted towards Public Safety applications
p. 228
6.4.5.3
Impact on existing entities and interfaces
p. 229
6.4.5.4
Solution evaluation
p. 229
6.4.6
Solution I6: ProSe Application Identities allocated using application layer mechanisms
p. 229
6.4.6.1
Functional description
p. 229
6.4.6.3
Impact on existing entities and interfaces
p. 230
6.4.6.4
Solution evaluation
p. 230
6.4.7
Solution I7: Random and Temporary ProSe Identity
p. 230
6.4.7.1
General
p. 230
6.4.7.2
Flows for ProSe Temporary Identity Association and Inquiry
p. 230
6.4.7.3
ProSe Identity under Out-of-Coverage scenarios
p. 233
6.4.7.4
Impact on existing entities and interfaces
p. 233
6.4.7.5
Solution evaluation
p. 234
6.4.8
Solution I8: Application-defined ProSe Application ID and system provided ProSe UE ID
p. 234
6.4.8.1
Functional description
p. 234
6.4.8.2
Procedures
p. 235
6.4.8.3
Impact on existing entities and interfaces
p. 238
6.4.8.4
Solution evaluation
p. 238
6.4.9
Solution I9: Registration for ProSe services by using a 3GPP assigned ProSe Identity
p. 238
6.4.9.1
Functional description
p. 238
6.4.9.2
Signalling Flow
p. 239
6.4.9.2.1
Registration procedure
p. 239
6.4.9.3
Impact on existing entities and interfaces
p. 240
6.4.9.4
Solution evaluation
p. 240
6.5
EPC Support for WLAN Direct Communications
p. 241
6.5.1
Solution W1: EPC support for WLAN Direct communication
p. 241
6.5.1.1
Functional description
p. 241
6.5.1.1.1
General
p. 241
6.5.1.1.2
System architecture
p. 241
6.5.1.2
Procedures
p. 241
6.5.1.3
Impact on existing entities and interfaces
p. 241
6.5.1.4
Solution evaluation
p. 241
6.5.2
Solution W2: ProSe assisted WLAN Direct communication
p. 241
6.5.2.1
Functional description
p. 241
6.5.2.2
Procedures
p. 242
6.5.2.2.1
WLAN Direct Connection Setup
p. 242
6.5.2.3
Configuration information from DPF for WLAN Direct communication
p. 243
6.5.2.4
IP address allocation
p. 243
6.5.2.5
Mobility Aspects
p. 243
6.5.2.6
Operational aspects
p. 243
6.5.2.6.1
Lawful Intercept
p. 243
6.5.2.6.2
Accounting
p. 243
6.5.2.7
Impact on existing entities and interfaces
p. 243
6.5.2.8
Solution evaluation
p. 244
6.5.3
Solution W3: Network-assisted WLAN Direct communication
p. 244
6.5.3.1
Functional description
p. 244
6.5.3.2
Procedures
p. 245
6.5.3.2.1
Network-initiated WLAN Direct Group Formation
p. 245
6.5.3.2.2
Network-initiated WLAN Direct Group Termination
p. 247
6.5.3.3
Impact on existing entities and interfaces
p. 247
6.5.3.4
Solution evaluation
p. 247
6.6
ProSe Configuration and capabilities handling
p. 247
6.6.1
Solution P1: Configuration of ProSe feature support of network in UE
p. 247
6.6.1.1
Functional description
p. 247
6.6.1.2
Procedures
p. 247
6.6.1.3
Impact on existing entities and interfaces
p. 247
6.6.1.4
Solution evaluation
p. 248
6.6.2
Solution P2: HSS based configuration
p. 248
6.6.2.1
Functional description
p. 248
6.6.2.2
Procedures
p. 249
6.6.2.2.1
High-level interactions for ProSe configuration
p. 249
6.6.2.3
Impact on existing entities and interfaces
p. 249
6.6.2.4
Solution evaluation
p. 250