EPC Network Resource Class Parameter for Multi-NSP Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Evolved Packet Core (EPC) networks lack the ability to implement resource sharing policies between multiple Network Service Providers (NSPs), as they cannot accurately split bearer capacities or manage resources based on NSP-specific requirements, leading to inefficient resource allocation and scheduling.
Innovation Solution
Introduction of a Resource Class (RC) parameter that identifies a resource partition and the originating subscriber/service group, allowing for the configuration of additional policies in EPC nodes for admission control and packet scheduling, enabling precise resource allocation and sharing between NSPs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the EPC network uses traditional bearer mechanisms without resource class parameters, then the network structure remains simple and easy to operate, but the network cannot implement resource sharing policies between multiple NSPs
Solution Approach 1:
The patent segments bearer resources into different resource classes (RC1, RC2, etc.), each associated with specific NSPs or service groups. This segmentation enables the network to implement resource sharing policies by treating different resource classes differently, while maintaining a relatively simple overall structure that builds upon existing EPC components.
Solution Approach 2:
The patent introduces a Policy and Charging Rules Function (PCRF) as an intermediary component that manages resource class assignments and policy enforcement. The PCRF acts as a mediator between NSPs and the core network, enabling resource sharing capabilities without requiring fundamental changes to the entire EPC architecture.
2Measurement precision
If the EPC network does not have NSP identification capability, then the network operation is simple, but the network cannot accurately split bearer capacities or manage resources based on NSP-specific requirements
Solution Approach 1:
The patent applies local quality by assigning specific resource classes to specific NSPs or service groups, allowing different parts of the network to have different management characteristics. Each resource class can have its own admission control policies, scheduling priorities, and resource allocation rules tailored to the specific needs of the associated NSP.
Solution Approach 2:
The patent changes the bearer parameters by introducing the resource class (RC) parameter alongside existing QoS parameters (QCI, GBR, MBR, ARP). This parameter change enables the network to identify and manage different NSP traffic flows with different resource requirements, allowing for precise resource allocation and sharing without fundamentally altering the existing parameter framework.
3Reliability
If the EPC network uses traditional admission control without resource class parameters, then the admission control process remains simple, but the network cannot enforce predetermined QoS resource policies or Service Level Agreements
Solution Approach 1:
The patent implements preliminary action by pre-configuring resource classes and their associated QoS parameters, admission control policies, and scheduling rules before traffic arrives. The PCRF pre-assigned resource classes to NSPs and service groups, establishing the framework for QoS enforcement before actual bearer establishment, thereby simplifying the admission control operation while improving reliability.
Solution Approach 2:
The patent incorporates feedback mechanisms where the PCRF monitors resource usage across different resource classes and can dynamically adjust admission control decisions and QoS parameters. This feedback enables the network to enforce predetermined QoS policies and SLAs by adapting to real-time network conditions while maintaining reliable service quality.
Data Source
AI summary
One aspect pertains to a method of enabling an Evolved Packet Core (EPC) network to implement predetermined Quality of Service (QoS) resource policies applied to subscriber/service groups operating via the network. The method comprises receiving a request for QoS resources to be provided to a bearer for traffic of a user of a subscriber/service group from which the request originated. A Resource Class (RC) parameter is assigned to the request. The RC parameter identifies a resource partition and the originating subscriber/service group, A Gx-Request that includes the RC parameter is forwarded to the EPC network to invoke application of the requested QoS resources so as to establish a bearer in accordance with the predetermined policies identifiable from the RC. Other aspects pertain to EPC network nodes configured accordingly.