IMS Private Domain Identity Segmentation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The IMS standard does not allow users to use SIP URIs without an operator/provider domain, limiting individuals and organizations that want to publish private or organizational domains instead of provider domains.

Innovation Solution

Implementing a method to receive and store a selected private domain name-based identity within the IMS, allowing it to be coupled with an operator domain name-based identity using the IMS's implicit registered identity set mechanism, enabling users to select and use private domain names for communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the IMS standard requires operator/provider domain in SIP URIs, then the system maintains standardized operator control and routing, but users cannot publish private or organizational domains

Engineering Contradiction:

Improvedomain publishing flexibilityVSAvoididentity management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The identity is segmented into two distinct parts: the private domain name-based identity (user's choice) and the operator domain name-based identity (system requirement). These are stored separately in the implicit registered identity set, allowing the system to handle both types of identities independently while maintaining both user flexibility and operator control.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The operator domain name-based identity acts as an intermediary that bridges the private domain identity and the IMS network infrastructure. This intermediary enables users to publish private domains while the operator maintains standardized routing and control through the operator domain component.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If users must use operator domain names in SIP URIs, then routing and authentication are simplified, but users cannot maintain personal identity when changing operators

Engineering Contradiction:

Improveidentity portabilityVSAvoidregistration simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

By separating the identity into private domain and operator domain components, the private domain component remains constant across operator changes while the operator domain component handles registration-specific functions. This segmentation enables identity portability without complicating the registration process.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system pre-configures the implicit registered identity set to include both private and operator domain identities before the user actually uses them. This preliminary setup allows users to maintain their personal identity across operator changes without needing to reconfigure anything during actual use.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If the system stores only operator domain identities, then the database structure remains simple, but users cannot select private domain names for communication

Engineering Contradiction:

Improveidentity selection flexibilityVSAvoidstored identity data

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The identity data is segmented into multiple identities within the implicit registered identity set, with each identity having a specific role (private domain for user selection, operator domain for system operations). This segmentation allows flexible identity selection without requiring separate storage structures.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The implicit registered identity set structure serves multiple functions: it stores both private and operator domain identities, enables user-selected identity presentation, maintains operator control, and supports standard IMS routing. This multi-functional structure avoids the need for separate storage mechanisms.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9369430B2Method and arrangement for allowing enterprise and personal domains in the IMS

Publication Date: 2016.06.14 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

The present invention relates to a method and an arrangement for allowing private domains in the IMS, which makes it possible to use a SIP URI like ID@private-domain.TLD. This is achieved by providing an administration support and an interface to the IMS interconnect DNS and the DNS system of the operator network. The identity associated with private domain is established as a Private domain name based IMPU. The private domain name based IMPU and the Operator domain name based IMPU is associated by using the implicit registered identity set provided by the IMS.