Dynamic Bandwidth Allocation for Non-IMS Access Bearers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems, such as those compliant with 3GPP standards, only support a one-to-one association between application flows and access bearers, limiting dynamic service flow allocation and bandwidth management in WiMAX networks, which restricts the ability to efficiently manage multiple application flows over a single access bearer.

Innovation Solution

A method and system for dynamically allocating bandwidth by creating or modifying access bearers to match desired QoS properties for non-IMS application flows, allowing multiple application flows to share the same access bearer, and managing these associations through a bandwidth manager that communicates with a PCRF to optimize bandwidth utilization and resource conservation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a one-to-one association between application flows and access bearers is maintained, then the system is simple to manage, but bandwidth utilization efficiency deteriorates

Engineering Contradiction:
Improvesimplicity of managementVSAvoidbandwidth utilization efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent merges multiple application flows into a single access bearer, allowing multiple flows to share the same bearer resources. This is achieved by implementing a many-to-one association mechanism where multiple application flows are grouped and mapped to a shared access bearer, thereby improving bandwidth utilization while maintaining manageable complexity through structured flow grouping and QoS parameter inheritance.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The access bearer is designed to serve multiple application flows simultaneously, making it multi-functional. The bearer can handle different types of traffic flows with different QoS requirements by implementing flow-specific QoS policies within the shared bearer framework, allowing a single bearer to perform multiple functions that previously required separate bearers.

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

2Productivity

If multiple application flows are allowed to share the same access bearer, then bandwidth utilization efficiency is improved, but device complexity increases

Engineering Contradiction:
Improvebandwidth utilization efficiencyVSAvoidcomplexity of flow management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the flow management function into distinct components: flow identification, flow grouping, QoS parameter mapping, and bearer allocation. This segmentation allows the system to handle multiple flows systematically by processing each flow through defined stages, reducing overall management complexity despite the many-to-one association. Each segment handles a specific aspect of flow management independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary flow management entity that mediates between multiple application flows and the shared access bearer. This intermediary layer handles the complexity of flow association, QoS parameter translation, and resource allocation, shielding the underlying bearer management from direct complexity while enabling efficient multi-flow support through centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If access bearers are created and deleted frequently to match application flow demands, then service flexibility is improved, but network signaling overhead increases

Engineering Contradiction:
Improveservice flexibilityVSAvoidnetwork signaling overhead
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements preliminary action by pre-establishing access bearers with configurable QoS parameters before application flows arrive. The system prepares bearer templates and resource allocations in advance, allowing flows to be quickly associated with pre-configured bearers rather than creating new bearers dynamically. This reduces signaling overhead by eliminating the need for frequent bearer creation and deletion while maintaining service flexibility through pre-configured options.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent maintains continuity of useful action by keeping access bearers active and reusable rather than creating and deleting them frequently. Once a bearer is established, it remains available to serve multiple flows over time, ensuring continuous resource utilization. This approach reduces the churn of bearer operations and associated signaling overhead while maintaining adaptability through flow dynamic association with existing bearers.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS8305979B2Managing multiple application flows over an access bearer in a quality of service policy environment
Publication Date: 2012.11.06 CLEARWIRE IP HOLDINGS LLC
  • US8305979B2 patent drawing
  • US8305979B2 patent drawing
  • US8305979B2 patent drawing

AI summary

A method, system and software to dynamically allocate bandwidth on an application flow basis in a non-Internet-Protocol Multimedia Subsystem (non-IMS) environment is described. The method includes: receiving a request to create an application flow for an Internet Protocol (IP) filter with desired Quality of Service (QoS) properties; searching for an access bearer that is comparable to the desired QoS properties; when a comparable access bearer is not found, creating the access bearer adapted to support the IP filter and the desired QoS properties; and associating the application flow with the access bearer. According to various embodiments, a method to add a new application flow from a flow bandwidth manager to a Policy Control and Charging Rules Function (PCRF) is also described The method can include: searching for an access bearer that supports an IP filter and desired QoS properties; when there is an existing access bearer, mapping the new application flow to the access bearer and modifying the properties of the existing access bearer to support the new application flow. and creating a new access bearer when there is no existing access bearer.