Transport Context Translation for Dynamic 5G Backhaul Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traffic engineered mobile network backhauls rely on static engineering estimates that are not suitable for dynamically changing contexts, such as 5G networks, leading to inefficiencies in meeting varying traffic demands.

Innovation Solution

A method and apparatus for resolving multi-transport network context-identifiers (MTNC-IDs) from 3GPP slice-specific identifying information, enabling dynamic traffic engineering by mapping MTNC-IDs to IP ports for network load balancing and encoding, and facilitating flexible routing based on dynamically varying resource provisioning requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static engineering estimates are used for traffic engineering configuration, then provisioning is simplified and easier to manage, but the system cannot adapt to dynamically changing traffic demands in 5G networks

Engineering Contradiction:
Improveadaptability to dynamically changing traffic demandsVSAvoidcomplexity of traffic engineering configuration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic traffic engineering by enabling real-time translation and mapping of transport network context identifiers (MTNC-IDs) to IP ports. This allows the system to dynamically adapt traffic routing based on changing network conditions and traffic demands, moving away from static engineering estimates to a flexible, real-time configuration approach that maintains adaptability while managing complexity through automated identifier resolution.

Inventive Principle:
Principle #15Dynamics

2Productivity

If dynamic traffic engineering is implemented to meet varying traffic demands, then network adaptability improves, but the complexity of path provisioning and identifier management increases

Engineering Contradiction:
Improveefficiency in meeting traffic demandsVSAvoidcomplexity of transport path identifier management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary translation mechanism that maps MTNC-IDs to IP ports and resolves transport path identifiers automatically. This intermediary layer simplifies identifier management by providing a standardized translation process between different network domains, reducing the complexity burden on individual network elements while enabling efficient dynamic traffic engineering across the entire transport network.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If translation requests are processed for each transport path identifier, then routing accuracy improves, but processing time and network latency increase

Engineering Contradiction:
Improveprecision of transport path identificationVSAvoidtime for identifier translation and path resolution
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-establishing translation tables and mappings between MTNC-IDs and IP ports before traffic flows are activated. Network functions can quickly resolve transport path identifiers by referencing pre-computed translation data, significantly reducing the time required for path resolution while maintaining precise routing accuracy. This approach avoids real-time computation delays by performing translation准备工作 in advance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260052458A1Methods and apparatus for transport context translation
Publication Date: 2026.02.19 HUAWEI TECH CO LTD
  • US20260052458A1 patent drawing
  • US20260052458A1 patent drawing
  • US20260052458A1 patent drawing

AI summary

A method for resolving an identifier of a path between a first user plane entity (UPE) and a second UPE includes receiving a translation request comprising a network slice selection assistance information (S-NSSAI), a first transport interface address, a second transport interface address, and one or more quality of service (QoS) parameters associated with the transport path between the first UPE and the second UPE; selecting the identifier of the transport path from a translation table in accordance with the S-NSSAI, the first transport interface address and the second transport interface address; and sending a translation response comprising an indicator of the identifier.