Communication Network Load Management Through Service-Level Overload Signaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network nodes in communication networks face resource overload issues, leading to limitations in providing additional services and impacting the ability of network controllers to subscribe to new services.

Innovation Solution

A method and device for managing load by explicitly identifying overload states and changes in resource availability, allowing network devices to communicate overload information and adjust service provision or subscription accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network nodes provide more services to network controllers, then service coverage and functionality are improved, but resource overload occurs and interface limits are reached

Engineering Contradiction:
Improveservice coverageVSAvoidresource availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the service portfolio into overloaded and non-overloaded services, allowing the network node to selectively continue providing only those services that do not exacerbate the overload condition. This is achieved by identifying specific services causing resource overload and maintaining other services that remain within resource capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic service management where the network node can adaptively adjust service provision based on real-time resource status. When overload is detected, the system dynamically modifies which services are continued and which are suspended, allowing flexible response to changing resource conditions.

Inventive Principle:
Principle #15Dynamics

2Duration of action of stationary object

If network nodes continue providing all services during overload, then service continuity is maintained, but resource exhaustion and system failure occur

Engineering Contradiction:
Improveservice continuityVSAvoidsystem stability
Core Design Contradiction:
Duration of action of stationary objectVSReliability

Solution Approach 1:

The patent extracts and isolates the problematic overloaded services from the overall service portfolio. By identifying and separating specific services that cause resource overload, the system can continue providing remaining services without being constrained by the overloaded ones, thus maintaining partial service continuity while ensuring system stability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by continuing to provide only a subset of services (those not causing overload) rather than attempting to maintain all services. This selective continuation allows the system to remain operational for critical functions while avoiding the resource exhaustion that would result from maintaining the full service portfolio.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If network controllers are restricted from subscribing to additional services due to overload, then resource exhaustion is prevented, but network functionality and adaptability are reduced

Engineering Contradiction:
Improveresource managementVSAvoidnetwork functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by treating different services differently based on their individual resource impact. Instead of applying a uniform restriction to all services, the system identifies specific services that are safe to continue providing and selectively maintains those, allowing differentiated resource management that preserves necessary functionality while preventing overload.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements a feedback mechanism where the network node monitors resource usage and communicates overload status to the network controller. This feedback enables the controller to make informed decisions about service subscription, continuing services that do not cause overload while avoiding those that would exacerbate resource constraints.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4608002A1Methods and devices for load management in a communication network
Publication Date: 2025.08.27 NOKIA SOLUTIONS & NETWORKS OY
  • EP4608002A1 patent drawingFigure 1
  • EP4608002A1 patent drawingFigure 2
  • EP4608002A1 patent drawingFigure 3

AI summary

An aspect concerns a method comprising, at a first communication network device: - receiving a request from a second network device, wherein the request is for a given service to be provided by a network function of the first network device; - responsive to the request, providing said given service; - determining an overload state change of resources required, by the first device, for said given service provided by said network function, wherein an overload state change type is one of a change from an overloaded state to a non-overloaded state or a change from a non-overloaded state to an overloaded state; - sending a message to the first device, wherein the message comprises information explicitly identifying at least said given service provided by said network function and the type of overload state change. Other aspects concern a method at a second device and first and second devices.