IPv4-to-IPv6 Redirect for AF-Specific UEID Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 3GPP architecture lacks a solution to enable third-party application functions to uniquely and anonymously identify user endpoint devices using network address translated or port address translated IPv4 addresses, leading to challenges in user privacy and identification in 5G networks.
Innovation Solution
Implement an IP4ID network function that redirects dual-stack user endpoint devices from IPv4 to IPv6, enabling the use of application function-specific user endpoint identifiers through a network exposure function, binding support function, and application function-specific management function to assign and extract unique UEIds.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network address translation (NAT) or port address translation (PAT) is used for IPv4 addresses, then device connectivity is enabled, but unique identification of user endpoint devices is lost
Solution Approach 1:
The patent introduces an intermediary system comprising a network exposure function, binding support function, and application function-specific management function. This intermediary layer maps non-unique IPv4 addresses to unique application function-specific UEIds, enabling both connectivity through NAT/PAT and accurate device identification by translating addresses through multiple functional layers.
Solution Approach 2:
The patent transitions from a single-dimension IPv4 addressing system to a multi-dimensional identification system. It combines IPv4 addresses with application function identifiers and UEId to create a composite identification mechanism, adding dimensional layers (application function dimension, UEId dimension) to the original address space to restore uniqueness.
2Device complexity
If a single UEId is used across all applications, then device identification is simplified, but user privacy is compromised due to correlation and tracking
Solution Approach 1:
The patent segments the identification system by creating application function-specific UEIds instead of using a single universal UEId. Each application function receives a dedicated identifier segment, preventing cross-application correlation while maintaining simplicity within each application context. The segmentation occurs at the identifier generation level through the application function-specific management function.
Solution Approach 2:
The patent applies local quality by making UEIds specific to particular application functions rather than universal. Each application function receives identifiers with properties tailored to its needs, creating localized identification quality that protects privacy in one application context without affecting others. The identifier properties (uniqueness, anonymity) are optimized locally for each application function.
3Adaptability or versatility
If IPv4 is used for application functions, then compatibility with existing systems is maintained, but unique and anonymous identification cannot be achieved
Solution Approach 1:
The patent uses the network exposure function as an intermediary that sits between IPv4 application functions and the 5G core network identification system. This intermediary translates and adapts requests, allowing IPv4 applications to access unique UEIds generated for IPv6 addresses without requiring the application functions themselves to be upgraded to IPv6.
Solution Approach 2:
The patent creates a universal identification mechanism that works across both IPv4 and IPv6 environments. The application function-specific UEId system serves multiple functions: it provides unique identification for IPv6-native applications, enables identification for IPv4 applications through the network exposure function intermediary, and maintains user privacy across all application types regardless of their IP version.
Data Source
AI summary
The present disclosure describes a device, computer-readable medium, and method for an IPv4-to-IPv6 redirect to enable use of application function-specific user endpoint identifiers (AF-specific UEIds). In one example, a method performed by a processing system includes receiving, from an application function of a communications network, a redirected request for an AF-specific UEId that is unique to a user endpoint device and the application function, where the redirected request includes an IPv6 address associated with the user endpoint device, querying a binding support function of the communications network for a subscription permanent identifier associated with the IPv6 address associated with the user endpoint device, querying an application function-specific management function for an AF-specific UEId associated with the subscription permanent identifier and an identifier of the application function, and forwarding the AF-specific UEId associated with the subscription permanent identifier and the identifier of the application function to the application function.