Enterprise Traffic QoS via Dynamic Dedicated Bearer Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise applications in mobile networks lack the ability to dynamically create and manage dedicated bearers with appropriate quality of service (QoS) attributes due to their topology unawareness and lack of interfaces for triggering bearer creation, leading to inefficient and suboptimal traffic handling.
Innovation Solution
A system and method where a service anchor in the mobile network inspects enterprise application flows, detects characteristics, and dynamically binds them to dedicated bearers with suitable QoS attributes, either using existing bearers or creating new ones as needed, without requiring triggers from the applications or significant involvement of policy and charging functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If enterprise applications trigger dedicated bearer creation manually, then QoS management precision is improved, but device complexity and ease of operation worsen due to topology unawareness and lack of interfaces
Solution Approach 1:
The service anchor performs automatic flow inspection, characteristic detection, and dedicated bearer binding without requiring enterprise applications to manually trigger bearer creation. The system self-services by monitoring traffic flows and dynamically allocating appropriate bearers based on detected characteristics, eliminating the need for complex application-side QoS management interfaces.
Solution Approach 2:
The service anchor acts as an intermediary between enterprise applications and the mobile network infrastructure. It inspects application flows, detects traffic characteristics, and automatically binds appropriate dedicated bearers, serving as a mediator that translates application traffic patterns into network resource allocations without requiring direct application-network interaction.
2Productivity
If service anchor dynamically inspects and binds flows to dedicated bearers, then productivity and QoS adaptability improve, but use of energy and device complexity increase
Solution Approach 1:
The service anchor performs flow inspection and characteristic detection selectively based on traffic patterns and QoS requirements rather than continuously monitoring all flows. The system applies partial action by only initiating dedicated bearer creation when flow characteristics indicate a need for enhanced QoS, avoiding unnecessary energy consumption from continuous full-scale inspection.
3Device complexity
If manual bearer creation is required, then device complexity is reduced, but adaptability and loss of time worsen due to inability to dynamically respond to changing application requirements
Solution Approach 1:
The system transitions from static manual bearer creation to dynamic automatic bearer allocation. The service anchor continuously monitors flow characteristics, detects changes in application requirements, and dynamically binds or rebinds flows to appropriate dedicated bearers in real-time, enabling the network to adapt to changing traffic patterns without manual intervention.
Solution Approach 2:
The service anchor implements feedback mechanisms by continuously inspecting flow characteristics and using this information to make real-time decisions about bearer binding. The system monitors traffic patterns, detects characteristic changes, and adjusts bearer allocations accordingly, creating a closed-loop control system that adapts to evolving application requirements.
Data Source
Figure 1
Figure 2
Figure 2
AI summary
In one embodiment, an apparatus comprising networking circuitry adapted to receive, at a mobile network operated by an SP, flows associated with enterprise applications executing on device(s) in an enterprise network, the device(s) including a CPE and/or one or more devices behind the CPE, and processing circuitry adapted to vary, during a duration in which there is IP connectivity between the CPE and the mobile network, a pool of dedicated bearers for binding the flows, in response to at least part of changes occurring during the duration with respect to the flows, wherein the changes include variations during the duration in number of the flows and/or differences during the duration in detected characteristics of the flows, the detected characteristics of the flows having been detected based on inspection of respective packet(s) of the flows, and bind at least part of the flows to respective dedicated bearers included in the pool.