Server-Managed Notifications for SIP Registration State

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Devices face significant power consumption and battery drain due to frequent SIP registration requests needed to maintain persistent access to voice communications and multimedia services over IP networks, leading to potential loss of service and increased storage requirements on servers.

Innovation Solution

Implementing server-managed notifications that start timers to manage registration and data updates, allowing devices to enter an inactive state between requests, reducing the frequency of registration and data retrieval, and using configurable intervals for notifications to conserve battery life and offload data storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If devices send SIP registers frequently to maintain persistent registration, then access to voice communications and multimedia services is maintained, but power consumption increases and battery life decreases

Engineering Contradiction:
Improvepersistent registrationVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The server sends a notification to the device before the registration expires, allowing the device to proactively renew its registration in advance rather than continuously maintaining an active state. This preliminary action enables the device to stay registered without constant active communication, thereby reducing power consumption while maintaining service access.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If devices send SIP registers frequently to maintain persistent registration, then service access is maintained, but battery life decreases

Engineering Contradiction:
Improveservice accessVSAvoidbattery life
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The server sends a notification to the device before the registration expires, allowing the device to proactively renew its registration in advance rather than continuously maintaining an active state. This preliminary action enables the device to stay registered without constant active communication, thereby extending battery life while maintaining service access.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If devices continuously monitor and retrieve updated data, then data freshness is maintained, but power consumption increases

Engineering Contradiction:
Improvedata freshnessVSAvoidpower consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The server sends notifications to devices when data is updated or when it is time to retrieve updated data, creating a feedback mechanism that informs devices of data changes without requiring continuous polling. This feedback approach ensures devices receive fresh data when needed while avoiding the power consumption associated with continuous monitoring and frequent requests.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12034779B2Server-managed notifications for maintaining registered state
Publication Date: 2024.07.09 T MOBILE US INC
  • US12034779B2 patent drawing
  • US12034779B2 patent drawing
  • US12034779B2 patent drawing

AI summary

Maintaining a registered state via server-managed notifications is described herein. In an example, server(s) can receive an indication from an application associated with a device, the indication can identify a response to a registration request sent by the application for registration with a service provider. Based at least partly on the indication, the server(s) can start a first timer associated with a first predetermined time interval after which the server(s) are to send a first notification to the application. The server(s) can determine, based at least in part on the first timer, a lapse of the first predetermined time interval and can send the first notification to the application. The first notification can cause the application to transition from an inactive state to an active state, and send a new registration request to register with the service provider to maintain a registered state.