Core Domain QoS Policy Selection for Content Providers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current communication network core domains face challenges in managing Quality of Service (QoS) effectively for content provided by content provider domains, especially when there is no pre-established Service Level Agreement (SLA) and when content providers need to implement their own logic for enhancing specific content flows without a common solution for flow identification.

Innovation Solution

A method where a first network node in the core domain provides a second network node in the content provider domain with information enabling the selection of policies that affect QoS, based on network conditions such as congestion or predicted usage of network resources, allowing for dynamic QoS management without relying on static SLAs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the CD manages network resources based on a previously established static SLA, then the QoS can be guaranteed, but the system lacks flexibility to adapt to changing network conditions and content provider needs

Engineering Contradiction:

ImproveQoS guaranteeVSAvoidFlexibility in QoS control

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent transforms the static SLA-based QoS management into a dynamic system where the content provider domain can request QoS targets irrespective of pre-established SLAs. The core domain evaluates these requests based on current network conditions and available resources, allowing the system to adapt QoS parameters dynamically rather than being constrained by fixed agreements.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system allows changing of QoS parameters based on network conditions and content provider requirements. Instead of fixed SLA parameters, the system evaluates and adjusts QoS targets dynamically, enabling parameter changes in response to varying network states and content priorities.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If the CPD implements its own logic for flow identification and provides identification to the CD, then the CPD can enhance specific content flows, but this results in much signaling traffic between the CPD and the CD

Engineering Contradiction:

ImproveFlow identification capabilityVSAvoidSignaling traffic

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the flow identification function from the content provider domain and relocates it to the core domain. The core domain performs the flow identification itself based on QoS targets provided by the content provider, eliminating the need for the content provider to send detailed flow identification information and reducing signaling traffic.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the core domain acts as a mediator between the content provider domain and the network resources. Instead of direct communication for flow identification, the core domain receives QoS targets and independently identifies flows, reducing the communication burden.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the CPD provides flow identification to the CD, then the CD can take action on identified flows, but there is a delay between the flow identification by CPD and the action taken on the identified flow by the CD

Engineering Contradiction:

ImproveFlow enhancement capabilityVSAvoidDelay in QoS application

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent inverts the traditional approach by having the core domain perform flow identification instead of the content provider domain. This reversal allows the core domain to immediately apply QoS policies to identified flows without the delay of inter-domain communication and processing, significantly reducing the time lag between flow identification and QoS application.

Inventive Principle:

Principle #13The other way round (Inversion)

4Adaptability or versatility

If the content provider requests a QoS target irrespective of an SLA, then the content provider has flexibility, but the core domain may not be able to fulfil the requested QoS target and must reject the request

Engineering Contradiction:

ImproveQoS request flexibilityVSAvoidQoS fulfillment guarantee

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the core domain evaluates QoS requests from the content provider domain based on current network conditions and resource availability. The system provides feedback on whether requests can be fulfilled, allowing the content provider to adjust requests accordingly while maintaining flexibility in initiating QoS targets.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS20250097806A1Technique enabling selection of core domain QOS policies in a content provider domain

Publication Date: 2025.03.20 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A technique enabling selection of Quality of Service, QoS, policies of a core domain of a mobile communication network is described. A method performed by a first network node, NN, configured as at least a part of the core domain includes providing, based on at least one network condition, a second NN in a content provider domain with information enabling a selection of at least one of one or more policies of the core domain that affect a QoS provided by the core domain for content provided by the content provider domain. A corresponding method performed by the second NN is also provided.