Presence Document URL Storage for IMS-IMPS Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile terminals and devices cannot store the mapping between a user's Mobile Station International Subscriber Directory Number (MSISDN) and Uniform Resource Locator (URL) identifiers, hindering interoperability and communication between IMS and IMPS systems.

Innovation Solution

A method where the URL of a user is included in a presence document, allowing it to be stored and used for subsequent communications, even in devices that only store MSISDNs, by propagating and storing the URL within the presence document received during presence subscription.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy mobile terminals store only MSISDN identifiers in their contact books, then device compatibility and simplicity are maintained, but interoperability with IMS systems requiring URL identifiers is hindered

Engineering Contradiction:
Improveinteroperability between IMS and IMPS systemsVSAvoidstorage capability for multiple identifier types
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a new dimension for storing URL identifiers by extending the contact book structure to include both MSISDN and URL fields. This allows legacy terminals to maintain backward compatibility while simultaneously supporting IMS systems that require URL identifiers, effectively resolving the interoperability issue without requiring terminal redesign.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The contact book is designed to serve multiple functions: storing traditional MSISDN identifiers for legacy IMPS systems and URL identifiers for IMS systems. This multi-functionality enables a single terminal to communicate with both types of systems, eliminating the need for separate contact books or additional interoperability infrastructure.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If the contact book stores both MSISDN and URL identifiers, then communication compatibility is improved, but storage capacity and device resources are consumed

Engineering Contradiction:
Improvecommunication compatibilityVSAvoidstorage capacity
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements preliminary action by pre-allocating and pre-populating the URL identifier field in the contact book structure. When a user adds a contact, the system proactively retrieves and stores the associated URL identifier from the network, ensuring both MSISDN and URL are available before communication is needed. This prevents storage issues and ensures immediate compatibility with IMS systems.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2301225B1Methods, telecommunications node, and user equipment for transmission of user identifier
Publication Date: 2012.05.09 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP2301225B1 patent drawingFigure 1
  • EP2301225B1 patent drawingFigure 2
  • EP2301225B1 patent drawingFigure 2

AI summary

A method, telecommunications node, and User Equipment (UE) are provided for transmitting a user identifier such as a Uniform Resource Locator (URL) in a presence document of a user, and for using that URL for handling communications. When an a first user, e.g. an IMS user communicates with a second user, e.g. an IMPS user, oftentimes the first user only knows the Mobile Station International Subscriber Directory Number (MSISDN) of the second user, and not also his URL. The invention allows for the transmissions of the second user's URL inside a presence document relative to that second user. The first user subscribes to presence information relative to the second user, and receives a presence document that includes, along the second user's presence information, also the second user's URL. Then, the first user uses the URL for handling communications with the second user, including initiating outgoing communications, or handling incoming communications from the second user.