Registration Server Refresh Period Selection by Authentication Type

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IP networks face challenges in optimizing the refresh period for client device registration and subscription, which affects network dimensioning, security, and user experience, as existing methods do not adequately consider the type of authentication and access technology used.

Innovation Solution

A registration server in IP networks that selects the refresh period based on the type of authentication and access technology, allowing for flexible dimensioning and security adjustments, such as lengthening the refresh period for robust authentication methods and shortening it for less secure ones, and taking into account the type of access used by client devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a fixed refresh period is used for all client devices, then network dimensioning is simplified, but network costs and resource optimization are compromised

Engineering Contradiction:
Improvenetwork dimensioning complexityVSAvoidnetwork resource optimization
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies dynamics by making the refresh period adjustable rather than fixed. The registration server dynamically selects refresh periods based on authentication types and access technologies, allowing the system to adapt to different security requirements and network conditions while maintaining simplified operation for end users.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of refresh period from a fixed value to a variable that depends on authentication type and access technology. This allows the network to optimize resource usage and costs by assigning longer refresh periods to secure connections and shorter periods to less secure ones, without requiring complex manual configuration.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If authentication type is considered in refresh period selection, then security is enhanced, but device complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidrefresh period selection complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The registration server automatically performs the complex task of selecting appropriate refresh periods based on authentication type and access technology. This self-service approach enhances security through informed decision-making while keeping the client devices simple, as they only need to send registration requests without needing to understand or configure refresh period parameters.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent segments the refresh period selection process into distinct categories based on authentication types (e.g., secure vs. less secure) and access technologies. This segmentation allows the system to apply different refresh period strategies to different segments without requiring complex individual configurations for each device.

Inventive Principle:
Principle #1Segmentation

3Productivity

If longer refresh periods are used, then network costs are reduced, but security is compromised

Engineering Contradiction:
Improvenetwork cost efficiencyVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent changes the refresh period parameter dynamically based on security requirements. For secure authentication types, longer refresh periods are assigned to reduce network costs and signaling traffic. For less secure authentication types, shorter refresh periods are assigned to maintain security. This parameter adaptation resolves the contradiction between cost efficiency and security.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent applies different refresh period qualities to different authentication types and access technologies. Instead of using a uniform refresh period, the system assigns locally optimized values: longer periods for secure connections (e.g., 3GPP access with strong authentication) and shorter periods for less secure connections (e.g., non-3GPP access with weaker authentication).

Inventive Principle:
Principle #3Local quality

4Reliability

If shorter refresh periods are used, then security is improved, but network resources are consumed faster

Engineering Contradiction:
ImprovesecurityVSAvoidnetwork resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent adapts the refresh period parameter based on security needs and resource constraints. For less secure authentication types, shorter refresh periods are used to enhance security through more frequent verification. For secure authentication types, longer refresh periods are used to conserve network resources. This conditional parameter adjustment resolves the contradiction between security and resource efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9800626B2Selecting refresh periods in an IP network
Publication Date: 2017.10.24 ORANGE SA
  • US9800626B2 patent drawing
  • US9800626B2 patent drawing

AI summary

A registration server in an IP network is provided. The server is configured to act, after receiving a request for an initial registration or for refreshing a registration with the IP network, or for an initial subscription or for refreshing a subscription to a given service made available on the IP network, to select for the client device sending the request a value for the corresponding refresh period. The server is also configured to select the value as a function, at least, of the type of authentication used by the client device for authenticating itself with the IP network.