Interconnection & migration functions David Chater-Lea Motorola Solutions

Issues following SA6 #19 Functional model for signalling plane Reference points and proxies between systems Functional model for application plane Treatment of gateway server Generic means of showing gateway servers and topology hiding for MC service calls

Interconnection and migration functions What do interconnection and migration reduce to?.... Interconnection Topology hiding Gateway server at MC application used for affiliation, call setup etc Local control Local configuration modification applied to MC service group configuration Migration Connectivity to partner network Local configuration modification applied to MC service user profile Call routing via primary network Forward private calls to migrated user Media for logging

Functional model to-dos for MCSMI Signalling plane SIP and HTTP reference points between MC systems Same or different to existing reference points within systems/trust domains? Proxies connecting between systems Don’t show as separate from proxies used within a system, leave actual configuration to deployment Application plane Incorporate gateway server and relationship with other MC system

Proposed signalling plane functional model SIP-3 (existing) and risk finding differences, or SIP-4 (new) and risk finding no differences? HTTP-3 (existing) and risk finding differences, or HTTP-4 (new) and risk finding no differences? From S6-171391

Proposed application plane functional model (MCPTT) From S6-171159 MCPTT-10 would be another instantiation of MCX-1, agreed in S6-171435 at SA6#19

Gateway server description S6-171159 + comments 7.4.2.3.x Gateway MCPTT server The gateway server provides support for MCPTT interconnection services with a partner MCPTT system whilst providing topology hiding. It may be a role of an the MCPTT server described in subclause 7.4.2.3.2 of the present document. The gateway MCPTT server functional entity does not act as a GCS AS described in 3GPP TS 23.468 [9] and does not control bearers for calls in the MCPTT system. The gateway server is responsible for relaying call control and floor control signalling messages, and media between MCPTT servers within the MCPTT system and the interconnected MCPTT system. The gateway server supports the controlling and participating role on behalf of the interconnected MCPTT system. If the interconnected MCPTT system has the controlling role in an MCPTT call, the gateway server acts in this role within its MCPTT system on behalf of the connected MCPTT system. If an MCPTT server within MCPTT system of the gateway server has the controlling role within an MCPTT call, the gateway server takes a participating role on behalf of the interconnected MCPTT system. The gateway server does not act as the primary MCPTT server for MCPTT users, or as group host MCPTT server for MCPTT groups. However when acting in a controlling or participating role in MCPTT calls on behalf of the interconnected MCPTT system, it acts as if it were the primary MCPTT server for users receiving service in the interconnected MCPTT system and as if it were the group host MCPTT server for groups hosted in the interconnected MCPTT system. ‘Gateway MCPTT server’ -> ‘Gateway server’ Topology hiding Does not host groups. Does not control bearers Acting as application proxy

Generic call procedure for topology hiding Procedure could be contained in 23.280 Text to explain how it applies to private and group calls Text describing media and floor/transmission control routing Define ‘serving MC system’ and ‘serving MC service server’