TDF Node Unsuccessful Resource Allocation Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In telecommunication networks, existing solutions fail to effectively handle unsuccessful resource allocation for Over-The-Top (OTT) applications, leading to misalignment between resource enforcement and quality of service, and issues with proper identification of notifications between the Traffic Detection Function (TDF) and Policy and Charging Rules Function (PCRF) nodes.

Innovation Solution

A method is introduced where the PCRF node establishes a session with the TDF node to report unsuccessful resource allocation for OTT applications, allowing the TDF node to take appropriate actions, such as retrying notifications, and enabling the PCRF node to generate and provide Policy Control and Charging (PCC) rules to the Policy and Charging Enforcement Function (PCEF) node, ensuring proper resource allocation and notification status management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the TDF node operates as a standalone entity detecting OTT applications, then service awareness and enforcement capability are improved, but the complexity of coordination between TDF, PCRF, and PCEF nodes increases

Engineering Contradiction:
Improveservice awareness capabilityVSAvoidcoordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism where the PCRF node notifies the TDF node about the outcome of resource allocation decisions. The TDF node receives notifications from the PCRF node regarding successful or unsuccessful resource allocation, and can accordingly adjust its enforcement actions. This feedback loop resolves the coordination complexity by providing clear information about resource allocation status between the TDF and PCRF nodes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The PCRF node acts as an intermediary between the TDF node and the PCEF node. It receives detection information from the TDF node, makes resource allocation decisions, and communicates the outcomes back to the TDF node. This intermediary role simplifies the overall system architecture by centralizing the decision-making logic in the PCRF node, which then coordinates with both the TDF and PCEF nodes.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the PCRF node notifies the TDF node about unsuccessful resource allocation, then the alignment between resource enforcement and quality of service is improved, but the signaling overhead between nodes increases

Engineering Contradiction:
Improveenforcement alignmentVSAvoidsignaling overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system implements partial action by notifying the TDF node only about unsuccessful resource allocation outcomes, rather than providing continuous status updates for all allocation attempts. This selective notification approach reduces signaling overhead while maintaining sufficient information for the TDF node to adjust its enforcement actions when needed.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The feedback mechanism provides targeted information about resource allocation outcomes to the TDF node, enabling it to adjust enforcement actions only when necessary. This selective feedback approach maintains enforcement alignment while minimizing unnecessary signaling overhead by providing information only when the allocation outcome affects enforcement decisions.

Inventive Principle:
Principle #23Feedback

3Reliability

If the TDF node retries notifications for unsuccessful resource allocation, then the reliability of resource allocation is improved, but the time required for allocation increases

Engineering Contradiction:
Improveallocation reliabilityVSAvoidallocation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by having the TDF node detect and report OTT application traffic before final resource allocation decisions are made. The PCRF node receives this advance information and can prepare appropriate resource allocation decisions in advance, reducing the need for repeated notification cycles and minimizing overall allocation time while maintaining reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The feedback mechanism allows the TDF node to receive information about allocation outcomes and adjust its behavior accordingly. When resource allocation is unsuccessful, the TDF node can retry with modified parameters or accept the outcome, reducing unnecessary retry cycles and optimizing the time required for successful allocation while maintaining high reliability.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP3763079B1A method of enabling a standalone traffic detection function, TDF, node in a telecommunication network to act on unsuccessful resource allocation for an over-the-top, OTT, application
Publication Date: 2024.10.23 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3763079B1 patent drawingFigure 1
  • EP3763079B1 patent drawingFigure 2
  • EP3763079B1 patent drawingFigure 3

AI summary

A method of enabling a standalone Traffic Detection Function, TDF, node (104, 204, 304) in a telecommunication network to act on unsuccessful resource allocation for an over-the-top, OTT, application detected by said TDF node (104, 204, 304), said method comprising the steps of receiving (107), by a Policy and Charging Rules Function, PCRF, node (103, 203, 303) from said TDF node (104, 204, 304), a notification that said TDF node (104, 204, 304) has detected a particular OTT application; determining (108; 109), by said PCRF node (103, 203, 303), that resources for said detected particular OTT application can not be successfully allocated, and notifying (110), by said PCRF node (103, 203, 303), said TDF node (104, 204, 304) that said resources for said detected particular OTT application can not be successfully allocated