Content for TR 23.779 Word version: 13.0.0
6 Functional diagram
7 Information Flow Diagrams
8 Allocation of functional entities
9 Evaluation
10 Conclusions
A MCPTT architectural scope
B MCPTT deployment options
C MCPTT roaming scenarios
D Solution evaluation criteria
$ Change History
6 Functional diagram p. 190
6.1 Functional model p. 190
6.2 Description of the planes p. 191
6.3 Functional diagram p. 191
6.3.1 On-network architecture model p. 191
6.3.1.1 On-network architectural model diagram p. 191
6.3.1.2 Application services layer p. 192
6.3.1.3 SIP core p. 193
6.3.1.4 EPS p. 193
6.3.1.5 UE 1 p. 193
6.3.1.6 UE 2 p. 193
6.3.1.7 On-network functional model p. 193
6.3.2 Off-network architecture model p. 193
6.3.2.1 Off-network architectural model diagram p. 193
6.3.2.2 UE 3 p. 194
6.3.2.3 UE 4 p. 194
6.3.2.4 UE 5 p. 194
6.3.2.5 UE 6 p. 194
6.3.2.6 UE 7 p. 194
6.3.2.7 Off-network functional model p. 194
6.3.3 Architectural model for roaming scenarios p. 196
6.4 Identities p. 196
6.4.1 Application plane p. 196
6.4.2 Signalling control plane p. 196
6.4.3 Relationship between identities in different planes p. 196
6.4.4 MCPTT group identity p. 196
6.5 List of functional entities p. 196
6.5.1 Introduction p. 197
6.5.2 Application plane p. 197
6.5.2.1 Common services core p. 197
6.5.2.1.1 Configuration management client p. 197
6.5.2.1.2 Configuration management server p. 197
6.5.2.1.3 Group management client p. 197
6.5.2.1.4 Group management server p. 197
6.5.2.1.5 Identity management server p. 197
6.5.2.1.6 Identity management client p. 197
6.5.2.2 MCPTT application service p. 197
6.5.2.2.1 MCPTT client p. 197
6.5.2.2.2 MCPTT server p. 197
6.5.3 Signalling control plane p. 198
6.5.3.1 Signalling user agent p. 198
6.5.3.2 Local inbound / outbound proxy p. 198
6.5.3.3 Registrar finder p. 198
6.5.3.4 Registrar / application service selection p. 199
6.5.3.5 Hypertext client p. 199
6.5.3.6 Hypertext proxy p. 199
6.5.3.7 Hypertext server p. 200
6.5.4 Media plane p. 200
6.5.4.1 Floor participant p. 200
6.5.4.2 Floor control server p. 200
6.5.4.3 Media resource function controller p. 200
6.5.4.4 Media resource function gateway p. 200
6.5.5 Bearer plane p. 200
6.5.6 Non-plane specific entities p. 200
6.6 Reference points p. 201
6.6.1 General reference point principle p. 201
6.6.2 Application plane p. 201
6.6.2.1 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server) p. 201
6.6.2.2 Reference point MCPTT-2 (between MCPTT server and MCPTT user database) p. 201
6.6.2.3 Reference point CSC-1 (between identity management client and identity management server) p. 201
6.6.2.4 Reference point CSC-2 (between the group management client and the group management server) p. 201
6.6.2.5 Reference point CSC-3 (between MCPTT server and group management server) p. 201
6.6.3 Signalling control plane p. 202
6.6.3.1 General p. 202
6.6.3.2 Reference point SIP-1(between MCPTT UE SIP User Agent Client and the SIP core) p. 202
6.6.3.3 Reference point SIP-2 (between the SIP core and the MCPTT server) p. 202
6.6.3.4 Reference point SIP-3 (between the SIP core and SIP core) p. 202
6.6.3.5 Reference point HTTP-1 (between the MCPTT UE HTTP client and the MCPTT server) p. 203
6.6.4 Media plane p. 203
6.6.5 Bearer plane p. 203
7 Information Flow Diagrams p. 203
7.1 Registration and user authentication for MCPTT service p. 203
7.2 Affiliation to an MCPTT group p. 204
7.2.1 Functional description p. 204
7.2.2 Procedure p. 204
7.3 Subscription to MCPTT group metadata p. 205
7.3.1 Functional description p. 205
7.3.2 Procedure p. 205
7.4 Group management p. 206
7.4.1 Temporary group formation - group regrouping involving multiple MCPTT systems p. 206
7.4.2 Temporary group - broadcast group call p. 208
7.5 Group call p. 210
7.5.1 Pre-arranged group call p. 210
7.5.2 Group call involving groups from multiple MCPTT systems p. 213
7.6 Floor control for on-network MCPTT service p. 215
7.6.1 Introduction p. 215
7.6.2 Floor request, floor grant and floor taken during an MCPTT session p. 215
7.6.3 Floor revoke, floor rejected during an MCPTT session p. 216
7.6.4 Queue position during an MCPTT session p. 217
7.7 Private call p. 218
7.7.1 Call setup - automatic commencement mode p. 218
7.7.2 Private call using manual commencement mode p. 220
7.7.2.1 Description p. 220
7.7.2.2 Procedure p. 220
7.7.3 End private call p. 221
7.7.4 Call Setup - automatic commencement mode - users in multiple MCPTT system p. 222
7.7.5 Private call set up in off-network mode with solicited discovery p. 224
7.7.6 Private call set up in off-network mode with unsolicited discovery p. 225
7.8 MCPTT media plane transmissions with partner MCPTT systems p. 227
8 Allocation of functional entities p. 228
9 Evaluation p. 228
10 Conclusions p. 228
10.1 Overall architecture for on-network operations p. 228
10.2 Conclusions for the functional architecture p. 229
A MCPTT architectural scope p. 230
B MCPTT deployment options p. 232
B.1 Public safety administration of the full MCPTT system p. 232
B.2 Public safety administration of the MCPTT application p. 233
B.3 Public safety administration of MCPTT application and full SIP core p. 234
B.4 Public safety administration of MCPTT application and partial SIP core p. 235
B.5 Public safety administration of the MCPTT system plus carrier RANs p. 236
B.6 Public safety administration of MCPTT application plus public safety RANs p. 236
B.7 Carrier administration of the full system p. 237
B.8 Interoperability between different deployments p. 239
C MCPTT roaming scenarios p. 240
C.1 Overview p. 240
C.2 Scenario list p. 240
C.3 Scenario 1: UE in visited network using primary MCPTT system p. 241
C.4 Scenario 2: UE in visited network using partner MCPTT system with connection to primary MCPTT system p. 241
C.5 Scenario 3: Communicating between UEs in different home networks using different primary MCPTT systems (interconnect) p. 242
C.6 Scenario 4: UEs in home networks using primary MCPTT systems p. 243
C.7 Scenario 5: UE in visited network using partner MCPTT system without making use of real time connection to primary MCPTT system p. 243
C.8 Scenario 6: UE in visited network not using any MCPTT system p. 244
C.9 Scenario 7: UE in visited network using partner MCPTT system, communicating with both members of home and partner MCPTT system p. 244
C.10 Scenario 8: UE in same home network using partner MCPTT system with connection to primary MCPTT system p. 245
C.11 Scenario 9: Communicating between UEs on the same home network using different primary MCPTT systems p. 245
C.12 Scenario 10: UE in home network using a primary MCPTT system not in that UE's home network p. 246
C.13 Scenario 11: UE in home network using a partner MCPTT system not in UE4's home network p. 246
D Solution evaluation criteria p. 248
D.1 Overview p. 248
D.2 Evaluation criteria p. 248
$ Change History p. 251
