5G UE Identifier Translation via Batched SUPI-to-GPSI Requests
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing process for translating multiple Subscription Permanent Identifiers (SUPIs) to Generic Public Subscription Identifiers (GPSIs) in a 5G network is inefficient, leading to multiple repeated transactions between the Network Exposure Function (NEF) and Unified Data Management (UDM), increasing system load and inefficiency.
Innovation Solution
Introduce a new attribute in the Nudm_SDM_Get Multiple Identifiers Translation service API to allow the translation of a list of SUPIs to their corresponding GPSIs in a single request, using AF-specific parameters to select appropriate GPSIs and reduce the number of transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple SUPIs are translated to GPSIs using separate transactions between NEF and UDM, then each translation can be completed individually, but the number of transactions increases and system efficiency decreases
Solution Approach 1:
The patent combines multiple separate SUPI-to-GPSI translation transactions into a single batched transaction. The NEF aggregates multiple SUPIs and sends them together to the UDM in one request, which processes all translations atomically and returns all results in a single response. This merging eliminates redundant transaction overhead while maintaining the reliability of individual translations through the UDM's centralized processing.
Solution Approach 2:
The patent implements preliminary aggregation of SUPIs at the NEF before forwarding to the UDM. The NEF collects multiple SUPIs that need translation, groups them into a batch, and prepares the consolidated request in advance. This preliminary action reduces the total number of transactions by ensuring that multiple translations are requested together rather than individually, thereby improving system productivity without compromising translation accuracy.
2Ease of operation
If multiple separate transactions are used for SUPI to GPSI translation, then individual translation requests can be handled independently, but system load increases due to repeated interactions
Solution Approach 1:
The patent merges multiple independent translation requests into a single batched request that is processed by the UDM in one operation. By combining the transport layer communications and processing steps into one transaction, the system reduces the cumulative load on network resources, database operations, and processing cycles. The UDM handles the batch as a unified operation, minimizing repeated interactions and reducing overall system energy consumption.
Solution Approach 2:
The patent uses a standardized batch request template that can be reused for multiple translation operations. Instead of creating and processing separate request structures for each SUPI, the system uses a single batch request format that contains multiple SUPIs. This copying approach allows the same processing logic to be applied to multiple identifiers simultaneously, reducing redundant operations and lowering system load while maintaining independent handling capabilities through the structured batch format.
3Productivity
If a single batched translation service is implemented, then the number of transactions is reduced and efficiency improves, but the service complexity increases
Solution Approach 1:
The patent segments the batched translation service into distinct functional components: the NEF handles request aggregation and formatting, the transport layer manages batch transmission, the UDM performs centralized translation processing, and the response layer handles result distribution. This segmentation allows each component to focus on a specific aspect of the batched service, making the overall complex system manageable through clear separation of concerns while maintaining high translation efficiency.
Solution Approach 2:
The patent creates a universal batched translation service that can handle multiple SUPIs of different types (5G-SUPI, 4G-SUPI, MSISDN) within a single request framework. The service is designed to be multi-functional, supporting various identifier formats and translation scenarios through a unified interface. This universality reduces service complexity by providing a single standardized mechanism that replaces multiple specialized translation operations, thereby improving productivity without proportionally increasing complexity.
Data Source
AI summary
In the present application, the 5G Core Network (5G-CN) comprises various network functions (NFs) interacting with each other over a Service-Based Architecture (SBA) interface. Each NF has specific functionality and offers a set of services to other NFs. Among them, the Unified Data Repository (UDR) is responsible for storing all information related to User Equipment (UE) in a database. This storage information contains subscription data, exposure data, application data, and policy data. Another NF called the Unified Data Management (UDM) serves as the front-end interface to UDR for accessing the subscription data of the UE(s) from the database. UDM manages data for access authentication, access authorization, user registration, user identification handling and so on. Yet another NF is Network Exposure Function (NEF) that acts as a gateway for an external untrusted application function (uAF) to avail services from 5G-CN after prior authorization and authentication based on operator policies. Apart from this, it is also responsible for translation of external information from uAF to internal information that other NFs can understand and vice versa.


