Context-Aware Network Node Reselection for Overload Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no mechanism allowing a reselected alternative server to take appropriate actions upon receiving a request message for an existing context, leading to potential overload and inefficient resource utilization in network function (NF) sets.
Innovation Solution
A mechanism is introduced where a client network node includes property information about the request message in the request sent to an alternative server, allowing the server to reject the request based on overload or failure conditions, and provides rejection cause information in the response, enabling the client to avoid further reselections for the same cause.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a client continuously reselects alternative servers when the original server is unavailable or overloaded, then service availability is improved, but network resource utilization deteriorates due to inefficient reselection loops
Solution Approach 1:
The patent implements feedback mechanisms where the server sends rejection cause information back to the client, and the client stores this information to avoid repeating the same reselection errors. This feedback loop enables intelligent decision-making that prevents futile reselection attempts while maintaining service availability.
Solution Approach 2:
The patent introduces rejection cause information as an intermediary element between the server and client. This intermediary carries the rejection reason from the server to the client, enabling the client to understand why a reselection was necessary and avoid similar situations in the future, thus optimizing resource utilization.
2Speed
If a server accepts all request messages without checking overload conditions, then service responsiveness is improved, but server overload worsens leading to potential service failure
Solution Approach 1:
The patent applies preliminary action by having the server check overload conditions and rejection causes before processing request messages. The server pre-evaluates whether accepting a request would exacerbate overload situations and takes preventive action by rejecting requests with appropriate cause information, thus avoiding service failure.
Solution Approach 2:
The patent changes the server's operational parameters by introducing selective acceptance based on overload conditions and rejection cause information. Instead of a fixed accept-all policy, the server dynamically adjusts its behavior based on current system state, accepting requests when resources are available and rejecting them when overload is detected.
3Device complexity
If the client does not store rejection cause information, then device complexity is reduced, but reselection efficiency deteriorates due to repeated unsuccessful attempts
Solution Approach 1:
The patent implements self-service by having the client autonomously store and utilize rejection cause information without external intervention. The client independently manages its own reselection logic by remembering previous rejection reasons and avoiding those servers in the future, thereby reducing reselection time and improving efficiency.
Data Source
AI summary
The present disclosure provides methods (200, 300), network nodes (500, 600, 700, 800), and computer readable media for network node reselection for a context related to a service. The method (200) at a first network node includes: determining (S201) to reselect a third network node that can provide a service for a context that was provided by the second network node: and transmitting (S203) a request message for the context to the third network node, the request message comprising property information about the request message.