Notification Routing via Hierarchical Subtopic Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mechanisms for notification messages in multi-user devices inefficiently manage resources as they do not account for multiple users, leading to wastage of processing resources by invoking unnecessary client applications.
Innovation Solution
Implementing a hierarchical naming system that allows server applications to push notifications with a subtopic identifier, enabling direct routing to specific client applications without invoking other applications, using a user token and subtopic to efficiently deliver messages to the appropriate user account.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If traditional notification routing is used without hierarchical naming, then all client applications subscribing to a topic are notified, but processing resources are wasted by invoking unnecessary applications
Solution Approach 1:
The patent segments the notification routing process by introducing hierarchical naming with topics and subtopics. Instead of notifying all applications subscribing to a topic, the system segments notifications to specific subtopics, allowing precise routing to only the intended client applications. This segmentation eliminates unnecessary invocations and reduces processing resource waste.
Solution Approach 2:
The patent introduces an intermediary routing mechanism that sits between the notification service and client applications. The hierarchical naming system acts as a mediator that receives notifications, determines the appropriate subtopic, and routes them to the correct client application. This intermediary layer prevents direct broadcasting to all applications, reducing unnecessary processing.
2Measurement precision
If hierarchical naming with subtopics is implemented, then notification routing precision is improved, but system complexity increases
Solution Approach 1:
The patent adds another dimension to the notification routing system by introducing subtopics as a second level hierarchy beneath topics. This dimensional extension allows precise routing without fundamentally changing the existing topic-based system. The multi-dimensional naming structure (topic/subtopic) enables fine-grained routing while building upon the familiar single-level topic approach.
Solution Approach 2:
The patent implements preliminary action by requiring client applications to register their subtopic preferences in advance. The notification service pre-configures the hierarchical naming structure and routing rules before notifications are sent. This preliminary setup enables automatic precise routing without requiring complex real-time decision-making, simplifying the operational complexity.
3Reliability
If multiple client applications wait for notifications from the same server, then comprehensive notification coverage is achieved, but resource taxation increases
Solution Approach 1:
The patent applies local quality by allowing different client applications to subscribe to different subtopics under the same topic. Each application receives notifications tailored to its specific needs (local requirement) rather than receiving all notifications under the topic. This localized notification approach maintains comprehensive coverage for each application while improving overall resource efficiency by avoiding duplicate processing.
Data Source
AI summary
Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device that can support multiple users are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application for one of the multiple users to the server application to enable the server application to push notification messages to the client device selectively for the client application for that user. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application for that user without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.