Network Traffic Distribution via NF Capacity Profiles

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current techniques for handling service requests in networks lack a mechanism to distribute network traffic based on the capacity of NF nodes, especially when load information is unavailable or when specific NF nodes require a predefined amount of traffic for testing, leading to inefficiencies and the inability to support scenarios like canary testing.

Innovation Solution

A method where a first network node, either an NF node or an SCP node, distributes network traffic among second NF nodes according to their capacity, irrespective of load information or the need for predefined traffic, by identifying configuration criteria that prioritize capacity-based distribution, allowing for efficient load balancing and supporting testing scenarios without requiring specific enhancements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service requests are handled using existing techniques (direct/indirect communication with load control), then service requests can be routed between NF nodes, but network traffic cannot be distributed based on capacity when load information is unavailable or for testing scenarios

Engineering Contradiction:
Improveability to distribute traffic based on capacityVSAvoidunavailability of load information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent changes the selection parameter from load-based to capacity-based. Instead of using load information (which may be unavailable or inaccurate) to determine traffic distribution, the system uses capacity information from NF profiles to distribute network traffic. This parameter change enables the system to function effectively even when load information is unavailable, particularly for testing scenarios like canary deployments.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If load control mechanisms are used to manage network traffic, then existing load balancing can be achieved, but the system cannot support predefined traffic requirements for testing

Engineering Contradiction:
Improveload balancing efficiencyVSAvoidsupport for testing scenarios
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the traffic distribution approach into two distinct modes: load-based distribution for production traffic and capacity-based distribution for testing traffic. By segmenting the selection criteria based on the operational context (production vs. testing), the system can simultaneously optimize for load balancing efficiency in production while enabling predefined traffic requirements for testing scenarios.

Inventive Principle:
Principle #1Segmentation

3Reliability

If NF nodes are selected based on load information, then traffic can be routed to less loaded nodes, but the system fails when load information is not reported by all NF nodes

Engineering Contradiction:
Improvetraffic distribution reliabilityVSAvoidcompatibility with all NF nodes
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent introduces capacity information as an intermediary parameter that mediates between the selector and the NF nodes. Instead of directly using load information (which may be missing or unreliable), the system uses capacity information from NF profiles as an intermediary to make selection decisions. This intermediary approach ensures reliable traffic distribution while maintaining compatibility with all NF nodes, even those that do not report load information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240179210A1Service Execution Handling
Publication Date: 2024.05.30 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240179210A1 patent drawing
  • US20240179210A1 patent drawing
  • US20240179210A1 patent drawing

AI summary

There is provided a method for handling execution of a service in a network. The method is performed by a first network node. The first network node is a first network function (NF) node of a service consumer or a first service communication proxy (SCP) node that is configured to operate as an SCP between the first NF node and second NF nodes of a service producer for providing the service. The method is performed in response to an event that signals that the service is to be executed. The method comprises, if a first configuration criterion of the first NF node and/or a second configuration criterion of at least one of the second NF nodes is met, identifying (102) that network traffic for executing the service is to be distributed among the second NF nodes according to a capacity of one or more of the second NF nodes.