Location Server Message Prioritization for Congestion Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Internet telephony systems, particularly those using TRIP-lite enabled gateways and location servers, lack the ability to prioritize message processing, leading to congestion issues where low-priority messages cannot be dropped during periods of high load.

Innovation Solution

Implementing a method in location servers to receive update messages from media gateways, determine their priority, and drop messages based on those priorities to manage congestion, utilizing the Stream Control Transport Protocol (SCTP) for efficient message handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If TRIP-lite enabled gateways and location servers process all update messages equally, then message processing is simple, but congestion occurs during high load periods and low-priority messages cannot be dropped

Engineering Contradiction:
Improvemessage processing simplicityVSAvoidsystem performance under congestion
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies parameter changes by introducing priority levels (parameters) to update messages. Each message is assigned a priority value that determines its processing order and eligibility for dropping during congestion. This transforms the uniform message processing approach into a differentiated approach where messages with different priorities are handled differently, allowing the system to maintain reliability under congestion while managing complexity through standardized priority assignment rules

Inventive Principle:
Principle #35Parameter changes

2Device complexity

If all update messages are processed with equal priority, then message handling is straightforward, but system reliability deteriorates during congestion periods

Engineering Contradiction:
Improvemessage handling complexityVSAvoidrouting table update reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent applies segmentation by dividing update messages into different priority segments or categories. Instead of treating all messages uniformly, the system segments messages based on their importance to routing table updates, allowing critical messages to be processed reliably while less critical messages can be dropped during congestion. This segmentation maintains reliability for essential functions while managing overall system complexity through structured categorization

Inventive Principle:
Principle #1Segmentation

3Loss of information

If the system processes every update message regardless of priority, then no messages are lost, but processing time and system load increase during congestion

Engineering Contradiction:
Improvemessage delivery completenessVSAvoidmessage processing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent applies partial action by selectively processing only the most critical update messages during congestion periods rather than attempting to process all messages. This partial processing approach accepts that some lower-priority messages may be dropped or delayed, but ensures that essential routing information is updated in a timely manner. The system performs sufficient action to maintain core functionality while avoiding the excessive processing time that would result from handling every message equally

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7624175B1Update messaging system
Publication Date: 2009.11.24 T MOBILE INNOVATIONS LLC
  • US7624175B1 patent drawing
  • US7624175B1 patent drawing
  • US7624175B1 patent drawing

AI summary

An update messaging system comprising a first interface configured to receive a first update message from a first gateway into a first location server wherein the first update message indicates a first type of message for the first update message, and a first processing system configured to determine a priority associated with the first update message based upon the first type of message for the first update message.