Network Slicing Privacy Routing via Default Slice
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network slicing technologies in 5G NR systems face challenges in user privacy concerns and inefficient data routing due to the reliance on application IDs and FQDNs, which can reveal user behavior and cause privacy issues, and lack dynamic slice configuration based on application needs.
Innovation Solution
User Equipment (UE) devices are configured to receive application-related information from the Access and Mobility Management Function (AMF) for determining traffic routing, allowing users to opt for default or application-specific network slices based on privacy settings, with the option to indicate supported traffic descriptors and use application categories for network slice determination.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If application IDs and FQDNs are used for network slice routing, then data routing efficiency is improved, but user privacy is compromised due to revelation of user behavior
Solution Approach 1:
The patent extracts and removes application-specific identifiers (application IDs and FQDNs) from the network slice routing process. Instead of routing based on these identifiable parameters, the system uses a default network slice that does not require such identifiers, thereby eliminating the privacy exposure while maintaining routing functionality through a generic pathway.
Solution Approach 2:
The patent introduces a privacy-preserving intermediary mechanism by using a default network slice as a mediator between the application and the network infrastructure. This intermediary pathway allows data to be routed without exposing user behavior information, acting as a buffer that prevents direct linkage between application usage and network routing decisions.
2Object-affected harmful factors
If default network slice routing is used, then user privacy is protected, but data routing efficiency and application-specific optimization are reduced
Solution Approach 1:
The patent implements a dynamic routing system that adapts between privacy-protected default routing and optimized application-specific routing. The system dynamically selects the routing pathway based on whether the application has been granted permission to use the default slice, allowing it to switch between privacy protection mode and efficiency optimization mode as needed.
Solution Approach 2:
The patent changes the routing parameter from application-specific identifiers to a permission-based parameter. Instead of routing decisions being made based on application IDs and FQDNs, the system uses a binary permission state (granted/not granted) to determine whether to use the default network slice, thereby protecting privacy while maintaining the ability to optimize for specific applications when permitted.
3Measurement precision
If application-specific network slicing is implemented, then data routing precision is improved, but system complexity increases due to multiple configuration parameters
Solution Approach 1:
The patent segments the network slicing functionality into two distinct parts: a simplified default network slice for privacy protection and application-specific network slices for optimized routing. This segmentation allows the system to handle routing decisions in a modular way, reducing overall complexity by separating the privacy-preserving default pathway from the optimization-oriented application-specific pathways.
Data Source
AI summary
Apparatuses, systems, and methods for enhancement of network slicing for a UE. A UE may receive, from an AMF of a network, application related information associated with network slice data routing for data associated with an application. The information may be provided to the network by network slice customers. The UE may, in response to application initiation, determine traffic routing for data associated with the application. Traffic routing may be based on the application related information and a UE configuration associated with user privacy (e.g., user privacy setting) associated with the application. When the user UE configuration is enabled, the data may be routed via a default network slice and when the UE configuration is disabled, the data may be routed via a network slice indicated by the application related information. The UE configuration may be indicated by the application via a Boolean flag and/or via a user interface setting.