Telephony Server Protocol Overhead Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy network protocols like GSM MAP incur high overhead, limiting network expansion and consuming bandwidth, especially in 3G and 4G networks, due to the use of multiple wrapper protocols and limited point codes, which restricts the number of users and sessions that can be supported.

Innovation Solution

Replacing GSM MAP messages with HTTP transactions according to RESTful protocol specifications between nodes, reducing the number of wrapper protocols and using Internet-Protocol-based Lightweight Protocols (IPLPs) for data encapsulation, such as HTTP or HTTPS, to decrease protocol overhead and increase network efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If GSM MAP protocol is used for legacy network communication, then compatibility with older protocols is maintained, but network overhead increases and bandwidth is consumed

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidbandwidth consumption
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent introduces an intermediary translation mechanism that converts legacy GSM MAP protocol messages into modern HTTP/HTTPS transactions. This mediator layer maintains compatibility with older protocols while enabling efficient IP-based communication, thereby reducing bandwidth consumption without sacrificing adaptability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the protocol parameters by transitioning from the traditional GSM MAP protocol stack to HTTP/HTTPS-based transactions. This parameter change involves modifying message formats, transport mechanisms, and protocol handlers to use lightweight IP-based protocols, thereby reducing overhead while maintaining functional equivalence.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If multiple wrapper protocols are used in legacy networks, then protocol compatibility is maintained, but device complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidprotocol stack complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts and removes unnecessary wrapper protocols from the legacy protocol stack. By eliminating redundant protocol layers and keeping only the essential HTTP/HTTPS transactions, the system maintains protocol compatibility while significantly reducing device complexity and protocol stack overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If legacy point codes are used for network addressing, then compatibility with older networks is maintained, but the number of supported users and sessions is limited

Engineering Contradiction:
Improvenetwork compatibilityVSAvoidconcurrent sessions capacity
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal addressing mechanism using modern IP addresses that can handle both legacy and modern communication requirements. This multi-functional approach allows the system to maintain compatibility with older networks while supporting a much larger number of concurrent users and sessions through the expanded addressing space of IP protocols.

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

Data Source

PatentUS10609090B2Reducing network protocol overhead
Publication Date: 2020.03.31 T MOBILE US INC
  • US10609090B2 patent drawing
  • US10609090B2 patent drawing
  • US10609090B2 patent drawing

AI summary

A telecommunications network includes a telephony application server (TAS). In some examples, the TAS receives, from a terminal, a session-initiation request identifying a called party. The TAS sends structured text (e.g., XML or JSON) identifying the called party (e.g., data of an anyTimeInterrogation query payload) to an information server (e.g., an HLR), which responds with structured text of a destination-terminal address dynamically bound to a terminal associated with the called party (e.g., data of a sendRoutingInformation reply payload). In some examples, the TAS receives Unstructured Supplementary Service Data (USSD) request data from a terminal. The TAS sends structured text indicating the USSD string and an identifier of the terminal to a USSD gateway via an Internet-Protocol-based Lightweight Protocol (IPLP), e.g., HTTPS, and receives structured text including USSD answer data. The TAS sends, to the terminal, a report message comprising the USSD answer data.