Unified UDR Interface Merges Data Retrieval and Subscription
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network devices consume resources and introduce latency by performing two independent requests to obtain data and subscribe to data change notifications from a unified data repository (UDR) device, leading to potential propagation of stale data and increased network transactions, which can result in reduced quality of service (QoS) and increased resource consumption.
Innovation Solution
Implementing a single communication mechanism that allows network devices to obtain data and subscribe to data change notifications from the UDR device using a unified interface, such as the Nudr, N35, or N36 interface, where a subscription request includes a monitoring indication and a report indication to identify monitored and attribute data sets, enabling simultaneous data retrieval and notification subscription.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network devices perform two independent requests to obtain data and subscribe to data change notifications from the UDR device, then data can be retrieved and notifications can be subscribed, but resource consumption increases and latency is introduced
Solution Approach 1:
The patent combines two separate requests (data retrieval request and subscription request) into a single unified request. The network device sends one request that simultaneously retrieves data from the UDR device and subscribes to data change notifications, eliminating the sequential execution of two independent requests and reducing the time delay between data retrieval and notification subscription.
Solution Approach 2:
The unified request mechanism enables a single communication to serve multiple functions: it retrieves current data, establishes a subscription to data change notifications, and confirms both operations in one interaction. This multi-functional approach eliminates the need for separate dedicated requests for each operation.
2Reliability
If network devices perform two independent requests to obtain data and subscribe to data change notifications from the UDR device, then data can be retrieved and notifications can be subscribed, but the number of network transactions increases
Solution Approach 1:
The patent merges two separate network transactions (data retrieval transaction and subscription transaction) into a single unified network transaction. This reduction in the number of network interactions improves network efficiency by decreasing the total volume of signaling traffic and reducing the processing overhead on both the network device and the UDR device.
Solution Approach 2:
The patent eliminates redundant communication overhead by discarding the need for separate request-response cycles for data retrieval and subscription. The unified request structure recovers network resources by processing both operations atomically in a single transaction, thereby improving overall network throughput.
3Reliability
If network devices perform two independent requests to obtain data and subscribe to data change notifications from the UDR device, then data can be retrieved and notifications can be subscribed, but device complexity increases
Solution Approach 1:
The unified request mechanism consolidates multiple protocol operations into a single standardized interaction pattern. Instead of implementing separate logic for data retrieval requests and subscription requests, the network device uses a universal request structure that handles both operations, simplifying the protocol implementation and reducing the complexity of request management.
Solution Approach 2:
The patent combines the logic and structure of two separate request protocols into one unified protocol. This merging reduces the complexity of maintaining and implementing multiple independent request-handling mechanisms, while ensuring that both data retrieval and subscription operations are reliably executed through a single standardized interface.
Data Source
AI summary
In some implementations, a unified data repository (UDR) device may receive, from a unified data management (UDM) device or a policy control function (PCF) device, a subscription request to subscribe to receive a data change notification from the UDR device. The subscription request may include a monitoring indication and a report indication. The monitoring indication may identify a monitored data set associated with a user equipment (UE). The report indication may identify an attribute data set associated with the UE and indicate a request to receive a report associated with the attribute data set. The UDR may transmit, to at least one of the UDM device or the PCF device, an indication of a subscription to receive the data change notification based on the subscription request and the report based on the report indication.