SIP Message User Data Embedding to Reduce HSS Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In communication networks, particularly in IP Multimedia Subsystems (IMS), the existing methods for managing Session Initiation Protocol (SIP) communications are inefficient due to the need for multiple queries to a Home Subscriber Server (HSS) when multiple application servers are involved, leading to increased complexity and resource utilization.

Innovation Solution

The solution involves generating and distributing user-specific data within SIP messages exchanged between network entities, allowing a first application server to forward this data to other network entities, such as the S-CSCF or another application server, thereby reducing the need for redundant queries to the HSS by embedding user-specific information, like communication status, location, or prepaid information, directly within SIP messages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple application servers are deployed for communications, then service functionality is improved, but the number of queries to HSS increases leading to increased complexity and resource utilization

Engineering Contradiction:
Improveservice functionalityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The first application server performs preliminary action by obtaining user-specific data from the HSS in advance and embedding it into SIP messages before forwarding them to other network entities. This preliminary acquisition and embedding of data eliminates the need for subsequent application servers to query the HSS separately, thereby reducing overall system complexity and resource utilization while maintaining multi-server functionality

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple application servers are deployed for communications, then service functionality is improved, but resource utilization increases due to multiple HSS queries

Engineering Contradiction:
Improveservice functionalityVSAvoidresource utilization
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The first application server performs preliminary action by obtaining user-specific data from the HSS in advance and embedding it into SIP messages before forwarding them to other network entities. This preliminary acquisition and embedding of data eliminates the need for subsequent application servers to query the HSS separately, thereby reducing overall system complexity and resource utilization while maintaining multi-server functionality

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If user-specific data is obtained from HSS by each application server, then data accuracy is improved, but the number of queries to HSS increases

Engineering Contradiction:
Improvedata accuracyVSAvoidnumber of queries
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The first application server creates a copy of the user-specific data obtained from the HSS and embeds this copy into SIP messages that are forwarded to other network entities. Subsequent application servers obtain data from these message copies rather than querying the HSS directly, maintaining data accuracy while significantly reducing the number of HSS queries required in the system

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2418815B1Managing Session Initiation Protocol communications towards a user entity in a communication network
Publication Date: 2019.01.02 DEUTSCHE TELEKOM AG
  • EP2418815B1 patent drawingFigure 1
  • EP2418815B1 patent drawingFigure 2
  • EP2418815B1 patent drawingFigure 3

AI summary

The present invention relates to a network entity (201) for managing Session Initiation Protocol (SIP) communications towards a user entity in a communication network. The network entity has a receiver (203) and a processor (205). The receiver (203) is configured to receive a first SIP message. The processor (205) is configured to generate a second SIP message in response to receiving the first SIP message, the second SIP message having user-specific data relating to the user entity.