Traffic Handling Decision Module for Mobile Network Function Upgrades

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile network upgrades face challenges such as service disruptions, incompatibility between old and new software versions, and the need for data conversion, which can lead to reduced capacity and potential service outages, especially when upgrading software in high-availability communication systems like LTE networks.

Innovation Solution

A method that allows simultaneous operation of old and new software versions during upgrades, where control traffic is routed to instances with the new software version while maintaining existing traffic on the old version, enabling incremental capacity transfer and avoiding data conversion, with a traffic handling decision module to manage incoming requests and ensure continuous service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the mobile network function is upgraded to a new software version, then the system gains new features and improved performance, but service disruptions and incompatibility issues occur

Engineering Contradiction:
Improvesoftware version compatibilityVSAvoidservice continuity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments traffic into existing traffic and new traffic, routing existing traffic to old software version instances and new traffic to new software version instances. This segmentation allows both versions to coexist and operate independently, preventing service disruptions during upgrades.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A traffic handling decision module acts as an intermediary between incoming traffic and software version instances. This mediator intelligently routes traffic based on traffic type and software version compatibility, ensuring seamless transitions during upgrades without service interruption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data conversion is performed during upgrade, then incompatibility between versions is resolved, but processing time and complexity increase

Engineering Contradiction:
Improveversion compatibilityVSAvoidupgrade processing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system extracts and removes the data conversion step from the upgrade process by directly routing traffic based on version compatibility. This eliminates the time-consuming data conversion operation while maintaining version compatibility through intelligent traffic handling.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary routing decisions before traffic reaches the software instances. By pre-configuring traffic handling rules and using a decision module to route traffic appropriately, the system avoids last-minute data conversion operations during the upgrade process.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If all traffic is migrated to the new software version at once, then the upgrade is completed quickly, but service disruption risk increases

Engineering Contradiction:
Improveupgrade speedVSAvoidservice availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system dynamically adjusts traffic routing between old and new software version instances based on real-time conditions. The traffic handling decision module can flexibly modify routing policies, allowing gradual migration of traffic while maintaining service availability and enabling quick rollback if issues arise.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system prepares backup routing paths and maintains old software version instances running alongside new ones during the transition. This cushioning approach ensures that if the new version encounters issues, traffic can be immediately redirected to the stable old version, preventing service disruption.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If the system maintains both old and new software versions simultaneously, then service continuity is ensured, but resource consumption increases

Engineering Contradiction:
Improveservice continuityVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies partial action by maintaining only the necessary portion of old software version instances required for handling existing traffic. The traffic handling decision module optimizes resource usage by routing traffic efficiently and allowing gradual decommissioning of old instances as new instances take over, reducing overall resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP3757778B1Upgrading of a mobile network function
Publication Date: 2023.10.04 HUAWEI TECH CO LTD
  • EP3757778B1 patent drawingFigure 1
  • EP3757778B1 patent drawingFigure 2
  • EP3757778B1 patent drawingFigure 3a

AI summary

The invention relates to upgrading a network service function within a mobile communication network. In this context the invention relates to a traffic handling decision module that distributes incoming request of the control plane to instances implementing the mobile network function either according to the current software version or an upgraded software version. Furthermore, the invention relates to a method, network entity and computer readable medium for upgrading a mobile network function.