SIP Registration Bulk Request for Multiple Addresses of Record

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SIP registration systems face scalability and performance issues due to the need for multiple discrete register requests for each address of record, leading to increased network burden and longer registration times, especially during failover scenarios.

Innovation Solution

Implementing a method that allows multiple addresses of record to be registered using a single SIP register request, either explicitly or implicitly, reducing the number of messages sent to the SIP registrar server and enabling faster registration and deregistration processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple discrete register requests are sent for each address of record, then complete registration of multiple AORs is achieved, but network burden increases and registration time extends

Engineering Contradiction:
Improveregistration completenessVSAvoidregistration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple discrete register requests into a single bulk register request message. The SIP endpoint device sends one consolidated message containing multiple AORs to be registered, rather than sending separate requests for each AOR. This merging approach reduces the total number of messages exchanged between the endpoint and registrar server, thereby decreasing registration time and reducing network burden while still achieving complete registration of all required addresses.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If multiple discrete register requests are sent for each address of record, then all addresses are properly registered, but CPU processing capacity and bandwidth are excessively consumed

Engineering Contradiction:
Improveregistration accuracyVSAvoidCPU processing capacity
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The invention merges multiple individual register request processing operations into a single bulk processing operation at the registrar server. Instead of parsing and processing each register request separately (which consumes significant CPU cycles), the server receives one bulk message containing multiple AORs and processes them in a consolidated manner. This reduces the overhead associated with message parsing, validation, and database operations, thereby lowering CPU processing capacity requirements while maintaining registration accuracy.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If multiple discrete register requests are sent during failover, then all endpoints can switch to new registration servers, but network scalability is reduced

Engineering Contradiction:
Improvefailover capabilityVSAvoidnetwork scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

During failover scenarios, the patent enables multiple SIP endpoints to simultaneously send bulk register requests to new registration servers without creating a message flood. Each endpoint consolidates its multiple AORs into a single bulk request, and the registrar server is designed to handle these bulk requests efficiently. This approach maintains failover capability (all endpoints can switch to new servers) while improving network scalability by reducing the total message volume and processing load on the registration servers.

Inventive Principle:
Principle #5Merging (Combining)

4Productivity

If a single bulk register request is used for multiple addresses of record, then network bandwidth and CPU processing are reduced, but compatibility with existing SIP systems must be maintained

Engineering Contradiction:
Improveregistration efficiencyVSAvoidsystem compatibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the bulk register request message into a standard SIP message format with well-defined structure and fields. The bulk request is organized as a legitimate SIP message that can be parsed by standard SIP processors, maintaining compatibility with existing SIP systems. The message contains structured information about multiple AORs that can be individually processed, allowing legacy systems to handle the bulk request without requiring fundamental changes to their architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The bulk register request mechanism is designed to be universal and compatible with existing SIP infrastructure. The patent implements the bulk registration feature within the standard SIP protocol framework, allowing the same message format and processing logic to handle both traditional individual register requests and new bulk register requests. This multi-functionality enables existing SIP systems to adopt bulk registration without requiring separate processing paths or incompatible modifications, thereby maintaining system compatibility while improving registration efficiency.

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

Data Source

PatentUS8271663B2System and method for multiple address of record registration using a single implicit SIP request
Publication Date: 2012.09.18 CISCO TECHNOLOGY INC
  • US8271663B2 patent drawing
  • US8271663B2 patent drawing
  • US8271663B2 patent drawing

AI summary

A method for registering multiple addresses of record comprises receiving a session initiation protocol register request, the session initiation protocol register request comprising a unique identifier of a session initiation protocol endpoint and a contact address for the session initiation protocol endpoint. The method proceeds by retrieving one or more addresses of record associated with the unique identifier of the session initiation protocol endpoint. The method further comprises associating each of the one or more addresses of record with the contact address for the session initiation protocol endpoint.