S-CSCF Server Registration Queue Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IMS network registration management is complicated by mobile terminals' mobility, leading to automatic re-registration issues, which can result in rejection of home gateways and other registered terminals, and generates additional load and security weaknesses in the network.

Innovation Solution

Implementing independent registration queues with distinct policies for different types of terminals, allowing for personalized configuration and management of registration durations and policies based on discriminating parameters, such as terminal type or network address, to avoid rejection and maintain service availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mobile terminals re-register automatically when leaving and re-entering Wifi zone, then terminal mobility is supported, but home gateway and other registered terminals are rejected due to FIFO policy

Engineering Contradiction:
Improveterminal mobility supportVSAvoidregistration stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the registration management system into multiple independent queues (first queue for home gateway, second queue for SIP terminals). This segmentation allows mobile terminals to re-register without affecting the home gateway's registration status, as each queue operates independently with its own policy. The discriminating parameter (e.g., terminal type, network address) is used to route registrations to the appropriate queue.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If maximum number of terminals with same IMPU is limited, then registration control is achieved, but service availability is reduced when maximum is reached

Engineering Contradiction:
Improveregistration control mechanismVSAvoidservice availability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

By dividing terminals into different queues based on their type and priority, the system can apply different registration limits and policies to each queue. The home gateway queue can maintain a guaranteed registration slot, while other terminals share the remaining capacity. This ensures service availability for critical terminals even when the overall maximum is reached.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different registration policies and limits are applied locally to different queues. The home gateway queue may have a higher priority or guaranteed slot, while other terminal queues have standard limits. This local differentiation allows the system to maintain service availability for critical services while controlling overall registration numbers.

Inventive Principle:
Principle #3Local quality

3Reliability

If centralized registration management is implemented, then registration policy enforcement is achieved, but network load and processing complexity increase

Engineering Contradiction:
Improveregistration policy enforcementVSAvoidnetwork processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The S-CSCF server pre-configures multiple registration queues with their respective policies, limits, and discriminating parameters. This preliminary setup allows the server to make rapid routing decisions without complex real-time analysis, reducing processing load while maintaining policy enforcement. The queues are prepared in advance with all necessary parameters defined.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2550776B1Method for managing records in an IMS network, and s-cscf server implementing said method
Publication Date: 2020.04.29 ORANGE SA
  • EP2550776B1 patent drawingFigure 1~3
  • EP2550776B1 patent drawingFigure 2

AI summary

The invention relates to a method for managing records in an IMS network, comprising: a step (E5) of creating, for a given public identity, at least two record files, each being associated with a recording policy; a step (E10) of receiving a record message transmitted by a terminal having said public identity; and a step (E70) of assigning one of said record files to said terminal on the basis of a field included in said message.