UDR Implicit Identity Translation Flow
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing identity translation process in unified data repository (UDR) devices is resource-intensive and negatively impacts network performance due to multiple steps involved, leading to increased latency and resource consumption.
Innovation Solution
An optimized identity translation flow is enabled by allowing the UDR device to perform implicit identity translation based on requests, mapping external identifiers to internal identifiers or vice versa without requiring communication with separate devices, thereby reducing the number of network transactions and resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the UDR device performs explicit identity translation by communicating with separate devices (UDM), then identity translation accuracy is ensured, but network latency increases and resource consumption increases
Solution Approach 1:
The UDR device performs identity translation autonomously using implicit translation, eliminating the need to communicate with separate UDM devices. The UDR translates external identifiers to internal identifiers (or vice versa) directly based on subscription data stored in its own data repository, thereby reducing network latency and resource consumption while maintaining translation accuracy.
Solution Approach 2:
The patent merges the identity translation function with the UDR device's core data storage and retrieval capabilities. By combining the translation logic into the UDR, the system eliminates separate translation services and reduces the number of inter-device communications, thereby resolving the latency-resource tradeoff.
2Reliability
If the UDR device communicates with separate UDM devices for identity translation, then translation reliability is maintained, but device complexity and resource utilization increase
Solution Approach 1:
The UDR device performs identity translation autonomously using implicit translation, eliminating the need to communicate with separate UDM devices. The UDR translates external identifiers to internal identifiers (or vice versa) directly based on subscription data stored in its own data repository, thereby reducing network latency and resource consumption while maintaining translation accuracy.
Solution Approach 2:
The UDR device is designed to perform multiple functions including data storage, data retrieval, and identity translation. By making the UDR multi-functional, the system reduces the need for separate dedicated translation devices, thereby simplifying the overall system architecture while maintaining reliable translation capability.
3Manufacturing precision
If multiple identity translation steps are performed sequentially, then translation completeness is ensured, but productivity decreases due to increased processing time
Solution Approach 1:
The UDR device performs identity translation in advance as part of the data retrieval process. By preparing and storing the necessary translation mappings in the subscription data before actual translation is needed, the system eliminates sequential processing steps and achieves complete translation in a single operation, thereby improving productivity.
Solution Approach 2:
The patent merges the identity translation function with the UDR device's core data storage and retrieval capabilities. By combining the translation logic into the UDR, the system eliminates separate translation services and reduces the number of inter-device communications, thereby resolving the latency-resource tradeoff.
Data Source
AI summary
In some implementations, a unified data repository (UDR) device may receive, from a network device, a request associated with a user equipment (UE). The request may indicate an external identifier of the UE. The UDR device may determine, based on the external identifier of the UE, an internal identifier of the UE. The UDR device may provide, to the network device, a request response that is in response to the request. The request response may indicate information identified via the internal identifier of the UE.


