Dual Channel Delivery via Reverse Push for Identity Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IP-based telecommunications services face inefficiencies and unreliability in identity queries due to the use of HTTP requests, which can impact user experience and network performance.
Innovation Solution
Implementing a system where user equipment devices can transmit service-related messages over reverse push connections instead of HTTP requests, with a server generating random values to determine the communication method based on capacity and network conditions, allowing for intelligent switching between reverse push and HTTP requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTP requests are used for identity queries, then the system is simple to implement, but the query process is time-consuming and unreliable
Solution Approach 1:
The patent introduces a push notification service as an intermediary mechanism between the first device and the server. Instead of directly querying the server via HTTP, the first device sends a push notification to the server, which then forwards the notification to the second device. This intermediary approach enables reliable two-way communication without requiring direct HTTP requests, thereby improving query reliability while reducing time loss.
Solution Approach 2:
The patent inverts the traditional client-server query model by enabling the server to actively push notifications to devices. Instead of the client repeatedly querying the server for device capability information, the server proactively sends capability information to the client through push notifications. This inversion of the communication direction resolves the contradiction by eliminating time-consuming HTTP requests while maintaining reliability.
2Ease of operation
If HTTP requests are used for service capability queries, then the implementation is straightforward, but user experience is negatively impacted due to time inefficiency
Solution Approach 1:
The patent implements preliminary action by having the server pre-establish push notification connections with devices before actual queries are needed. The server maintains active push notification channels, allowing it to immediately send capability information when a query is triggered, without waiting for HTTP requests to complete. This preliminary setup eliminates query processing time while keeping the operation simple for users.
3Productivity
If reverse push connections are used for critical messages, then network efficiency is improved, but the system complexity increases
Solution Approach 1:
The patent applies universality by making the push notification service handle multiple functions: device capability queries, service capability notifications, and error communications. Instead of creating separate complex protocols for different message types, the system uses a single push notification mechanism that can carry various types of service-related messages. This multi-functionality improves network efficiency while managing complexity through a unified approach.
4Quantity of substance
If random value selection is used to determine communication method, then server capacity is optimized, but the decision-making process becomes more complex
Solution Approach 1:
The patent uses parameter changes by introducing a random value as a decision parameter to determine whether to use reverse push connections or HTTP requests. The server generates a random value and compares it against threshold parameters to dynamically adjust the communication method. This parameter-based approach optimizes server capacity utilization by distributing traffic patterns while keeping the routing logic simple through mathematical comparison rather than complex decision trees.
Data Source
AI summary
Embodiments described herein relate to systems and methods for transmitting service related messages, e.g., via a reverse push connection. In some embodiments, a UE may be configured to receive a random value from a server, the random value based at least in part on a capacity of the server and/or network. The UE may be configured to compare the random value to a generated value, and determine, based at least in part on the comparison, to transmit a service related message over a reverse push connection rather than via a hypertext transport protocol (HTTP) request. In some embodiments, the service related message may be any message that relates to a service available between devices, such as an identity (ID) query request, a service (de-) registration request, and/or a device listing request, among other types of messages.