SMF–UPF Configuration Hashes for Network Slice Integrity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G network configurations lack efficient mechanisms for ensuring the integrity and consistency of configuration information between Session Management Function (SMF) and User Plane Function (UPF), leading to transmission errors, resource waste, and unnecessary message exchanges due to non-synchronized or corrupted configurations.
Innovation Solution
Implementing a technique for integrity and consistency checks using configuration identifiers, such as hash values, to verify and synchronize configuration information between SMF and UPF, along with peer-to-peer provisioning and optimized recovery procedures to minimize unnecessary data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration information is transmitted between SMF and UPF without integrity verification, then message exchange frequency increases, but configuration reliability deteriorates
Solution Approach 1:
The patent introduces configuration identifiers (hash values) as an intermediary element between the configuration information and the verification process. Instead of verifying the entire configuration data, the SMF and UPF exchange compact configuration identifiers that serve as mediators to confirm configuration integrity, thereby reducing message exchange overhead while maintaining reliability.
Solution Approach 2:
The patent transforms the configuration verification approach by changing the parameter being verified from the complete configuration information to a condensed configuration identifier (hash value). This parameter transformation allows for efficient verification with minimal data exchange, resolving the contradiction between reliability and message overhead.
2Reliability
If complete configuration information is re-transmitted during recovery, then configuration synchronization is ensured, but network resource waste increases
Solution Approach 1:
The patent applies preliminary action by having the UPF send its current configuration identifier to the SMF before the SMF decides whether to re-transmit configuration information. This preliminary exchange allows the SMF to compare identifiers and determine if re-transmission is necessary, preventing unnecessary resource waste while ensuring synchronization when needed.
Solution Approach 2:
The patent implements a feedback mechanism where the UPF provides its configuration identifier back to the SMF, which then uses this feedback to make an intelligent decision about configuration re-transmission. This feedback loop enables the system to avoid unnecessary complete re-transmissions while ensuring synchronization is achieved when configuration drift is detected.
3Reliability
If configuration verification is performed frequently, then configuration consistency is maintained, but system overhead increases
Solution Approach 1:
The patent uses configuration identifiers (hash values) as simplified copies of the complete configuration information. Instead of verifying the entire configuration data structure, the system verifies these compact identifier copies, which maintains configuration consistency while significantly reducing the complexity and overhead of the verification process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In one embodiment, a method includes determining a first configuration information for configuring a user plane device of the first network slice associated with the control plane device, generating a first configuration identifier based on the first configuration information, sending, to the user plane device of the first network slice, the first configuration identifier and the first configuration information, receiving, from the user plane device of the first network slice, a second configuration identifier, wherein the second configuration identifier is generated by the user plane device of the first network slice based on the first configuration information received from the control plane device, and verifying, by comparing the first configuration identifier and the second configuration identifier, that the user plane device of the first network slice is configured using the first configuration information.