MTNC-ID Encapsulation in UDP Headers for Dynamic 5G Traffic Routing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current traffic engineering in 5G mobile networks relies on static provisioning, which is inadequate for dynamically changing traffic demands, as it takes weeks or months to adjust, leading to inefficiencies in providing quality of service, class of service, resilience, and isolation requirements across multiple domains.

Innovation Solution

Implementing a method using User Datagram Protocol (UDP) headers and Generalized UDP Encapsulation (GUE) headers to encapsulate data packets with MTNC-IDs, allowing for dynamic resource provisioning and routing based on quality of service, class of service, resilience, and isolation requirements across multiple transport networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static traffic engineering provisioning is used, then network stability is maintained, but the system cannot adapt to dynamically changing traffic demands in 5G networks

Engineering Contradiction:

Improveadaptability to changing traffic demandsVSAvoidtime required for traffic engineering adjustments

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic traffic engineering by enabling real-time modification of traffic paths and resource allocation in response to changing traffic demands. The system allows network elements to dynamically adjust forwarding paths, bandwidth allocation, and resource provisioning without requiring manual reconfiguration, thus resolving the contradiction between maintaining stability and adapting to dynamic changes.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent establishes feedback mechanisms where network elements continuously monitor traffic conditions, performance metrics, and resource utilization. This feedback enables automatic adjustment of traffic engineering parameters, allowing the system to adapt to changing demands in real-time while maintaining operational stability through controlled, data-driven modifications.

Inventive Principle:

Principle #23Feedback

2Reliability

If manual traffic engineering reconfiguration is performed, then resource provisioning requirements are met, but the process takes weeks or months to complete

Engineering Contradiction:

Improvequality of service provisioningVSAvoidspeed of traffic engineering implementation

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent enables the network to self-configure and self-optimize traffic paths and resource allocation automatically. Network elements use embedded intelligence to make real-time decisions about traffic engineering, eliminating the need for manual reconfiguration processes that take weeks or months, while still ensuring quality of service requirements are met through automated policy enforcement.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements preliminary configuration of traffic engineering policies and parameters before traffic demands arise. By pre-establishing flexible policy frameworks, service level agreements, and resource allocation rules, the system can quickly respond to changing demands by activating pre-configured options rather than performing lengthy manual reconfiguration processes.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If dynamic traffic engineering is implemented, then responsiveness to changing demands improves, but system complexity increases

Engineering Contradiction:

Improvedynamic resource provisioning capabilityVSAvoidcomplexity of traffic engineering system

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces intermediary components such as centralized controllers, policy management systems, and abstraction layers that mediate between network elements and traffic engineering functions. These intermediaries simplify the overall system architecture by centralizing complex decision-making logic and providing standardized interfaces, thereby enabling dynamic traffic engineering without proportionally increasing end-device complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements universal traffic engineering mechanisms that can be applied across multiple network domains, transport networks, and service types through standardized protocols and interfaces. By creating multi-functional capabilities that serve diverse traffic engineering needs through common infrastructure and policies, the system achieves high adaptability without linearly increasing complexity for each specific application.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentEP3991366B1Transporting a multi-transport network context-identifier (MTNC-id) across multiple domains

Publication Date: 2024.10.02 HUAWEI TECH CO LTD

Figure 1~2
Figure 3
Figure 4

AI summary

A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.