Proxy Node Header Enrichment for OTT QoS Enablement

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunications networks are unable to deliver Quality of Service (QoS) based communication channels for Over The Top (OTT) service providers due to the lack of sufficient information in QoS requests, as IP addresses are translated by Network Address Translation (NAT), making it impossible to uniquely associate users and apply QoS.

Innovation Solution

Performing header enrichment in the uplink by adding subscriber identification to application-dependent messages, translating WS/RESTful/API-based QoS requests into Policy Control messages, and using a proxy node to intercept and modify messages before they reach the OTT application server, allowing network policy nodes to determine and enforce appropriate QoS levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Network Address Translation (NAT) is used to translate IP addresses, then network security and address management are improved, but the ability to uniquely identify users and apply QoS deteriorates

Engineering Contradiction:
Improvenetwork securityVSAvoiduser identification capability
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent introduces a proxy node as an intermediary between the UE and OTT application server. This proxy node performs header enrichment by adding subscriber identification information to the message header, enabling the OTT application server to identify subscribers despite NAT translation. The intermediary resolves the contradiction by maintaining network security through NAT while providing user identification capability through the proxy node's enrichment function.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by performing header enrichment at the proxy node before the message reaches the OTT application server. The subscriber identification is added to the message header in advance, so that when the OTT application server receives the message, it already contains the necessary user identification information. This preliminary enrichment action prevents the loss of user identification capability that would otherwise occur due to NAT.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If QoS requests are sent with only IP address information, then the request format is simplified, but the carriers cannot identify specific users and apply QoS

Engineering Contradiction:
Improverequest formatVSAvoiduser identification accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The proxy node acts as an intermediary that enriches the message header with subscriber identification information before forwarding to the OTT application server. This allows the QoS request to contain both the simplified IP address information and the additional user identification data, resolving the contradiction between request simplicity and user identification accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements nesting by placing the subscriber identification information within the message header structure. The enriched header contains both the original IP address information and the additional subscriber identification, creating a nested structure that maintains simplicity while adding necessary identification capabilities.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Adaptability or versatility

If carriers use existing QoS request mechanisms, then backward compatibility is maintained, but OTT service providers cannot deliver applications over QoS-based channels

Engineering Contradiction:
ImproveQoS delivery capabilityVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a proxy node as an intermediary that translates and enriches QoS requests from OTT application servers into carrier-friendly Policy Control messages. This intermediary layer enables OTT service providers to deliver applications over QoS-based channels while maintaining backward compatibility with existing carrier systems, resolving the contradiction between adaptability and complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the direct mechanical connection between OTT application servers and carrier QoS systems with a software-based translation and enrichment mechanism. The proxy node substitutes for direct system integration by providing a layered approach that translates between different system protocols, reducing overall system integration complexity while enabling QoS delivery.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS8982893B2System and method of quality of service enablement for over the top applications in a telecommunications system
Publication Date: 2015.03.17 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US8982893B2 patent drawing
  • US8982893B2 patent drawing
  • US8982893B2 patent drawing

AI summary

A system, method, and node providing a predefined Quality of Service (QoS) level to an Over The Top (OTT) service provider in a telecommunications network. A User Equipment (UE) initiates an IP-based application session (e.g., Hyper Text Transfer Protocol (HTTP) session) with the OTT service provider by sending an application-dependent message toward an OTT application server. The method begins with a proxy node in the telecommunications network intercepting the application-dependent message. The proxy node then modifies the application-dependent message by adding a subscriber identification to the header of the application-dependent message. The proxy node forwards the modified application-dependent message to the OTT application server. The OTT application server then sends a request having the subscriber identification to the telecommunications network with a QoS requirement for the HTTP session. Next, a network policy node determines an appropriate QoS level for the subscriber. A network gateway then enforces the determined QoS level for the HTTP session with the OTT service provider.