WINFO Server Aggregates SIP Watcher Subscription Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SIP event notification systems face difficulties in scenarios with multiple SIP event servers handling subscription requests for a watched subscriber entity, as there isn't a single server with a complete view of all watcher entities, making it challenging for watched subscriber entities to discover and contact all servicing SIP event servers for watcher information.

Innovation Solution

A system comprising one or more notifier servers and a watcher information (WINFO) server that collects and distributes SIP event watcher entity subscription information, allowing the WINFO server to receive, store, and provide watcher entity subscription information to requesting watched entities, thereby facilitating the discovery of all watcher entities subscribed to a particular watched entity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple SIP event servers are deployed to handle subscription requests, then the system can handle more subscribers and scale better, but no single server has a complete view of all watcher entities, making it difficult to provide comprehensive watcher information

Engineering Contradiction:
Improvesubscription handling capacityVSAvoidwatcher entity information completeness
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system segments the watcher information management by allowing each SIP event server to maintain local watcher information for the subscribers it serves, while introducing a separate discovery mechanism that aggregates information across multiple servers. This segmentation enables scalable subscription handling while preserving complete watcher information through the discovery process.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a watcher discovery mechanism that acts as an intermediary between watched entities and multiple SIP event servers. This intermediary collects watcher information from various servers and presents a unified view to the watched entity, solving the information completeness problem while maintaining the distributed architecture's scalability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If a watched subscriber entity contacts multiple SIP event servers to discover all watcher entities, then complete watcher information can be obtained, but the complexity of subscription permissions and traffic increases

Engineering Contradiction:
Improvewatcher entity information completenessVSAvoidsubscription permission complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system performs preliminary action by having SIP event servers pre-collect and maintain watcher information in their respective domains. When a watched entity needs complete watcher information, the discovery mechanism leverages this pre-collected data rather than requiring the watched entity to query multiple servers individually, thereby reducing complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The watcher discovery mechanism serves as an intermediary that consolidates watcher information from multiple SIP event servers and presents it to the watched entity in a single operation. This intermediary approach eliminates the need for the watched entity to manage complex multi-server queries and permission negotiations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of energy

If watcher information requests are distributed across multiple SIP event servers, then the load on any single server is reduced, but the logic for accepting and enforcing subscriptions becomes more complex

Engineering Contradiction:
Improveserver load distributionVSAvoidsubscription enforcement logic
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The system segments subscription enforcement logic by allowing each SIP event server to independently manage and enforce subscriptions for the subscribers in its domain. This segmentation distributes the processing load while maintaining simple, localized enforcement logic at each server, avoiding the need for complex distributed coordination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each SIP event server autonomously handles watcher information collection and subscription enforcement for its own subscribers without requiring complex inter-server coordination. This self-service approach simplifies the enforcement logic at each server while still achieving distributed load management across the system.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8499035B2Methods, systems and computer readable media for providing session initiation protocol (SIP) event watcher entity information in a communications network
Publication Date: 2013.07.30 TEKELEC INC
  • US8499035B2 patent drawing
  • US8499035B2 patent drawing
  • US8499035B2 patent drawing

AI summary

Methods, systems, and computer readable media system for collecting and distributing session initiation protocol (SIP) event watcher entity subscription information in a communications network are disclosed. According to one aspect, a system includes one or more notifier servers for receiving subscription requests for SIP event information associated with a plurality of watched entities from a plurality of watcher entities. The system further includes a watcher information (WINFO) server for receiving, from the notifier servers, SIP event subscription information that includes, for each watcher entity, an association between the watcher entity to each of the watched entities in which a subscription for SIP event information was requested by the watcher entity, for storing the SIP event subscription information in the WINFO server, for receiving, from one of the watched entities, a request for watcher entity subscription information associated with the requesting watched entity from one of the watched entities, and for accessing the SIP event subscription information to locate the watcher entity subscription information associated with the requesting watched entity.