Content Provider Multipath Policy Steering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current ATSSS proposals do not allow content providers to influence traffic steering policies, making it difficult to trigger steering rules based on application indications and select preferred steering modes, and network operators struggle to determine the protocol stack used by content providers, leading to inefficient resource usage and misapplication of steering functionalities.

Innovation Solution

Implementing a method for content providers to dynamically expose their preferred multipath policies to network operators, allowing the UE to initiate different steering policies based on application events and indicating content provider assistance, and extending the exposure policy framework to include content provider-assisted modes, enabling the UE to signal preferred policies to the UPF.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network operators rely on 3GPP multi-access solutions with local UE steering decisions, then seamless IP session mobility is achieved, but network operators cannot control traffic steering and offload decisions

Engineering Contradiction:
Improvetraffic steering controlVSAvoidUE local decision complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Network Exposure Function (NEF) as an intermediary between the UE and network operators. The NEF receives multipath policy information from the UE and forwards it to the network operator, enabling centralized control while maintaining UE autonomy in making steering decisions. This mediator resolves the contradiction by allowing both local UE decisions and network operator control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If content providers implement native multipath with MP-TCP client proxy, then QoE-friendly flow control is achieved, but dependency on device vendor operating system is created

Engineering Contradiction:
ImproveQoE-friendly flow controlVSAvoiddevice vendor dependency
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal multipath policy framework that works across different device vendors and operating systems. By defining standardized policy structures and using the NEF as a vendor-agnostic interface, the solution enables content providers to enforce their preferred multipath policies regardless of the underlying device implementation, thus achieving universality while maintaining reliability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If content providers use QUIC transport layer for multipath, then application-level policy enforcement is achieved, but terminal dependency is eliminated

Engineering Contradiction:
Improveterminal independenceVSAvoidapplication implementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enables QUIC applications to self-enforce their multipath policies directly at the application level without requiring terminal or OS support. The application can independently declare its preferred multipath policy, and the NEF facilitates communication of this policy to the network operator, allowing the application to serve itself rather than depending on terminal infrastructure.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If network operators deploy standalone MP-TCP proxies, then traffic steering control is improved, but proxies are bypassed when native multipath is applied

Engineering Contradiction:
Improvetraffic steering controlVSAvoidproxy utilization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a feedback mechanism where the UE declares its intended multipath policy to the network operator through the NEF. This allows the network operator to see what native multipath policies are being applied and adjust proxy deployment accordingly. The feedback loop ensures that proxies are used when appropriate while respecting native multipath implementations, optimizing proxy utilization efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240121309A1Managing content provider multi-path policies
Publication Date: 2024.04.11 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240121309A1 patent drawing
  • US20240121309A1 patent drawing
  • US20240121309A1 patent drawing

AI summary

A method for implementing an AF multipath policy. The method may be performed by a PCF and may include a step of transmitting a request message comprising a UE ID identifying a UE. The method also includes receiving a response message transmitted as a response to the request message, the response message comprising: the AF multipath policy, an application ID (App-ID) identifying an application, and an application protocol ID (App-ID-Protocol), identifying a protocol used by the application. The method further includes generating a multipath policy using at least: i) the AF multipath policy and ii) the App-ID-Protocol. The method further includes providing the generated multipath policy to a management function (e.g., SMF).