OSS Device Coordinated RAN Transport Resource Utilization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Telecommunication networks face inefficiencies due to uncoordinated resource allocation and congestion monitoring between the air interface and backhaul/transport networks, leading to suboptimal resource utilization and user experience issues.
Innovation Solution
An Operations Support System (OSS) device coordinates resource utilization by receiving congestion indications from RAT components and edge routers, determining if thresholds are met, and either obtaining additional transport resources or updating resource utilization policies to adjust allocations and alleviate bottlenecks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If QoS control is implemented at air interface and backhaul/transport separately without coordination, then resource allocation can be managed at each level, but resource utilization is not optimized and congestion cannot be effectively mitigated
Solution Approach 1:
The patent merges previously separate QoS control functions at the air interface and backhaul/transport into a coordinated system. The E-RAB manager at the base station now controls both radio resource allocation and transport network resource allocation jointly, transforming independent operations into an integrated control mechanism that optimizes overall resource utilization.
Solution Approach 2:
The patent introduces an intermediary coordination mechanism where the E-RAB manager acts as a mediator between radio access resources and transport network resources. This intermediary receives QoS parameters from the core network and coordinates resource allocation across both domains, enabling optimized resource utilization without direct complex interactions between all components.
2Reliability
If independent QoS control is used at air interface and backhaul, then each component can manage its own resources, but congestion monitoring is uncoordinated and resources are not fully utilized
Solution Approach 1:
The patent implements feedback mechanisms where congestion indicators from both air interface and backhaul/transport are collected and fed back to the E-RAB manager. This feedback loop enables dynamic adjustment of resource allocation based on actual congestion conditions, improving both QoS reliability and resource utilization by responding to real-time network state.
Solution Approach 2:
The patent performs preliminary resource reservation and allocation based on QoS parameters before congestion occurs. The E-RAB manager proactively allocates transport network resources alongside radio resources, preparing the system in advance to handle traffic demands and maintain QoS without waiting for congestion to manifest.
3Productivity
If no coordination exists between air interface and backhaul resource allocation, then implementation is simpler, but resources are not fully utilized and user experience deteriorates
Solution Approach 1:
The patent segments the coordinated control function into manageable components: the E-RAB manager handles high-level coordination and policy decisions, while subordinate modules manage specific resource allocation tasks. This segmentation allows complex coordinated control to be implemented through modular, easier-to-manage functional blocks.
Data Source
AI summary
OSS device(s) described herein are configured to receive a congestion indication from a RAT component, a CSR, or an edge router of a core network and to determine whether the congestion indication meets a threshold or criteria. Based on that determination, the OSS device(s) may perform one or both of obtaining additional transport resources from a provider of a transport network or updating a resource utilization policy for the RAT component, CSR, or edge router. If obtaining additional transport resources, the OSS device(s) may notify the RAT component, the CSR, and the edge router. If updating a policy, the OSS device(s) may provide the updated resource utilization policy to its associated RAT component, CSR, or edge router.


