OMA Management Object for Application-Specific Congestion Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current ACDC standards lack granularity in controlling specific applications during network traffic congestion, as they cannot distinguish between applications within the same access class and do not effectively manage bearer establishment in connected mode, leading to inefficient congestion control.

Innovation Solution

The implementation of an Open Mobile Alliance (OMA) management object with IP flow descriptions, including operating-system-specific application IDs, fully qualified domain names, and packet filters, allows for finer granularity in application control by assigning priority levels to IP flows, enabling the mobile network to determine which applications can establish or maintain connections based on congestion levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access class barring is used to reduce congestion, then network congestion is reduced, but the granularity to control specific applications is lost

Engineering Contradiction:
Improvecongestion control effectivenessVSAvoidapplication-specific control granularity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the congestion control mechanism by introducing application-specific parameters (application IDs, packet filters, flow descriptions) that divide the monolithic access class barring into granular, application-level controls. This allows different applications to be treated differently during congestion, resolving the contradiction between achieving congestion reduction and maintaining control granularity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If conventional ACDC standards are used, then basic congestion control is achieved, but fine-grained control over specific applications within the same access class is not possible

Engineering Contradiction:
Improvecongestion controlVSAvoidapplication identification precision
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent applies local quality by introducing specific application-identifying characteristics (application IDs, packet filters, flow descriptions) that enable precise identification and differentiation of specific applications within the same access class. This allows the system to apply different congestion control policies to different applications locally, achieving both reliable congestion control and precise application-level measurement.

Inventive Principle:
Principle #3Local quality

3Productivity

If access class barring denies access to selected mobile devices, then radio access network congestion is reduced, but control over specific application types is not achieved

Engineering Contradiction:
Improvenetwork throughput optimizationVSAvoidapplication-level access control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent adds another dimension to congestion control by introducing application-specific parameters (application IDs, packet filters, flow descriptions) as additional control variables beyond the traditional access class level. This dimensional expansion enables the system to optimize network throughput while simultaneously maintaining application-level access control, resolving the contradiction between productivity optimization and operational granularity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS9980299B2Use of an OMA management object to support application-specific congestion control in mobile networks
Publication Date: 2018.05.22 INTEL CORP
  • US9980299B2 patent drawing
  • US9980299B2 patent drawing
  • US9980299B2 patent drawing

AI summary

Technology for using an open mobile alliance (OMA) management object (MO) for congestion control in mobile networks is described. A novel type of OMA MO for application specific access control (ASAC) can include internet protocol (IP) flow descriptions that can be used to characterize applications with fine granularity. Priorities can be assigned to IP flows based on the IP flow descriptions. A user equipment (UE) can receive such an OMA MO and also receive application-barring information regarding a congestion level in a mobile network with which an application at the UE wishes to connect. The UE can have a connectivity manager (CM) that determines whether to allow the application to establish a connection with the mobile network based on the priority level of the application's associated IP flow and the application-barring information.