5G Transport Context Translation for Dynamic Path Engineering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing traffic engineering in mobile network backhauls is static and inefficient for dynamically changing contexts, particularly in 5G networks, failing to adapt quickly to varying traffic demands.
Innovation Solution
A method and apparatus for translating multi-transport network context-identifiers (MTNC-IDs) from 3GPP slice-specific identifying information, such as S-NSSAI, to dynamically manage transport paths and enable network load balancing by mapping MTNC-IDs to IP ports.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static traffic engineering provisioning is used based on engineering estimates, then network configuration is simple and stable, but the system cannot adapt quickly to dynamically changing traffic demands in 5G networks
Solution Approach 1:
The patent implements dynamic traffic engineering by enabling real-time translation and mapping of network slice identifiers (S-NSSAI) to transport path identifiers (MTNC-IDs). This allows the network to dynamically adapt transport paths according to changing traffic demands and service requirements, moving from static periodic reconfiguration to continuous dynamic adaptation.
Solution Approach 2:
The patent introduces a translation function as an intermediary component that bridges the control plane and transport plane. This translation function converts S-NSSAI to MTNC-ID, enabling the transport network to understand and respond to 5G network slice requirements without direct complex configuration, thus reducing overall system complexity while improving adaptability.
2Speed
If periodic traffic engineering reconfiguration is performed based on demand, then traffic demands are eventually met, but the reconfiguration process takes too long (weeks or months) to be suitable for dynamic 5G networks
Solution Approach 1:
The patent implements preliminary action by pre-establishing translation rules and mappings between S-NSSAI and MTNC-ID in the translation function. When traffic demands change, the system can immediately apply these pre-configured mappings without waiting for lengthy reconfiguration processes, enabling real-time response while maintaining service level agreements.
Solution Approach 2:
The patent implements feedback mechanisms where the system continuously monitors traffic demands and service requirements, then dynamically adjusts transport path mappings through the translation function. This closed-loop feedback enables the system to respond to changing conditions in real-time, ensuring both speed and reliability of service delivery.
3Adaptability or versatility
If transport paths are dynamically reconfigured to meet changing traffic demands, then service flexibility is improved, but the complexity of path identification and management increases
Solution Approach 1:
The patent simplifies path identification by changing the parameter used for identification from complex MTNC-ID to the more manageable S-NSSAI in the control plane. The translation function automatically handles the mapping between these parameters, allowing dynamic service flexibility while reducing the difficulty of path identification and management for network operators.
Data Source
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.