Rules-Based Overload Control for 5G Network Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 3GPP service architecture for 5G networks lacks guidelines for overload handling mechanisms at intermediate proxy nodes, leading to potential service starvation for low priority services due to congestion, and relies on consumer NFs to set message priority correctly, which is unreliable, causing denial of service issues.
Innovation Solution
Implementing rules-based overload control at intermediate or producer network functions (NFs) that associate guaranteed processing bandwidth with specific message handling rules, using criteria like destination network name or network slice, and tracking message counts to ensure prioritization and prevent service denial.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If intermediate proxy nodes route all traffic without overload control, then traffic flow is maintained, but service starvation occurs for low priority services during congestion
Solution Approach 1:
The patent applies preliminary action by pre-configuring overload control rules and thresholds at intermediate proxy nodes before congestion occurs. The system establishes message counting mechanisms and priority-based handling rules in advance, enabling automatic enforcement when traffic patterns indicate potential overload conditions, thus preventing service starvation before it happens.
Solution Approach 2:
The patent segments traffic handling into priority-based categories at intermediate proxy nodes. By dividing message streams into different priority levels and applying distinct handling rules to each segment, the system ensures that critical services maintain throughput while non-critical services are throttled during congestion, resolving the contradiction between maintaining overall traffic flow and protecting service availability.
2Ease of operation
If consumer NFs set message priority values, then priority-based handling is enabled, but inconsistent priority setting causes denial of service
Solution Approach 1:
The patent introduces intermediate proxy nodes as mediators between consumer NFs and producer NFs. These proxy nodes override the unreliable priority values set by consumer NFs and instead apply consistently enforced priority rules based on service type, message type, and pre-configured policies. This intermediary layer ensures uniform priority handling across the network regardless of consumer NF variations.
Solution Approach 2:
The patent changes the parameter control approach by shifting priority determination from consumer NF configuration to network-enforced rules at intermediate proxies. The system modifies how priority is applied by using message counting thresholds and service-type-based rules rather than relying on consumer-set priority values, thereby ensuring consistent and reliable priority-based handling.
3Device complexity
If no overload control is implemented at intermediate nodes, then system complexity is low, but traffic congestion leads to service denial
Solution Approach 1:
The patent implements self-service by enabling intermediate proxy nodes to autonomously monitor their own traffic loads and enforce overload control policies without requiring complex centralized control or modifications to consumer/producer NFs. The proxy nodes independently count messages, evaluate against pre-configured rules, and apply throttling or prioritization, maintaining service continuity while adding minimal architectural complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for rules-based overload control for 5G services includes configuring, at an intermediate or a producer network function (NF), overload message handing rules, wherein at least some of the rules include destination network name (DNN), network subscription, network location, or a network slice identifying parameter or any parameter/attribute defined by 3GPP/vendor as rule selection criteria. The method includes a guaranteed processing bandwidth of the intermediate or producer NF with at least some of the overload message handling rules, receiving a first message at the intermediate or producer NF, determining that an overload condition exists, identifying that the first message includes parameters that match the rule selection criteria for one of the overload message handling rules, determining, that a portion of the guaranteed processing bandwidth of the intermediate or producer NF for the matching overload message handling rule is available to process the first message, processing the first message, and updating a message count for the overload message handling rule.