MCPTT Identity Binding via IMS Core Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Mission Critical Push To Talk (MCPTT) systems require the core network to maintain application IDs, which can be a security risk and limit operational autonomy for Public Safety service providers, as they need to interoperate with IMS networks while maintaining distinct identities.
Innovation Solution
A procedure that allows MCPTT specific identities to be used for call setup and routing using SIP, where MCPTT public user identities are registered with the IMS core, enabling the MCPTT application server to create a binding between network and application identities, and using these identities for SIP INVITE messages to facilitate group and private calls without relying on the core network to maintain application IDs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the core network maintains application IDs for MCPTT, then call routing and setup can be performed, but security risks increase and operational autonomy is limited
Solution Approach 1:
The patent extracts the application identity information from the core network domain and places it in the application server domain. The S-CSCF stores only network identities (IMPI/IMPU) while the MCPTT application server stores and manages application identities (MCPTT public user identities). This separation removes the security burden and operational constraints from the core network while maintaining full functionality for call routing and setup.
2Reliability
If MCPTT specific identities are stored in the core network, then proper routing can be achieved, but device complexity and configuration requirements increase
Solution Approach 1:
The patent segments the identity management functionality into two distinct parts: network identity management (handled by S-CSCF with IMPI/IMPU) and application identity management (handled by MCPTT application server with MCPTT public user identities). This segmentation allows each component to focus on its specific role, reducing overall system complexity while ensuring reliable routing through the binding relationship between network and application identities.
3Ease of operation
If the core network maintains application IDs, then call setup procedures can be simplified, but interoperability with IMS networks is limited
Solution Approach 1:
The patent introduces a binding relationship as an intermediary mechanism between network identities and application identities. The S-CSCF stores the binding between IMPI/IMPU and MCPTT public user identities, enabling it to translate between IMS network protocols and MCPTT application protocols. This intermediary binding allows seamless interoperability between IMS networks and MCPTT services without requiring the core network to maintain application-specific identity information.
Data Source
Figure 1
Figure 2~6
AI summary
It is provided a method, comprising supervising if an information in a registration request is received from a registrar of a network domain, wherein the information comprises an application identity of a user of a terminal device and a network identity; storing, based on the received information, a binding between the application identity and the network identity; determining the network identity based on the binding and a received first request for establishing a communication to the terminal device; providing, based on the received first request, to the network domain, a second request for establishing the communication towards the terminal device, wherein the second request is based on the determined network identity.