Push Registry API Extension for Mobile Event Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Java mobile communications devices lack the ability to interact with push-to-x (PTX) events and other traditional services such as voice calls to trigger service-related applications, due to limited trigger event support in the PushRegistry API.
Innovation Solution
The implementation of a method that registers event handlers with unique attributes in a push registry, allowing for the detection and handling of various communication events, including PTX events, by associating event handlers with trigger events and filters, enabling automatic initiation of applications in response to specific communication events.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the PushRegistry API supports only limited trigger events (time-based alarms, UDP packets, SMS messages), then the system maintains simplicity and ease of operation, but the adaptability and versatility of the system are reduced, preventing interaction with PTX events and traditional services such as voice calls
Solution Approach 1:
The patent extends the PushRegistry API to support multiple types of trigger events beyond the original limited set. The registration process now accepts diverse event types including PTX events, voice calls, and data sessions, allowing a single API to handle multiple functions and event sources uniformly through a common registration interface
Solution Approach 2:
The patent segments the trigger event handling by introducing event-specific attributes and filters that can be registered independently. Each event type (PTX, voice call, data session) can be registered with its own unique attributes, allowing the system to manage complexity through modular, segmented event registration while maintaining a unified API interface
2Reliability
If the system registers event handlers with unique attributes and associations in the push registry, then the ability to detect and handle various communication events is improved, but the device complexity and registration process complexity increase
Solution Approach 1:
The patent implements self-service through automatic event handler initiation. Once event handlers are registered with their trigger event associations and attributes in the push registry, the system automatically detects when registered events occur and initiates the appropriate event handlers without requiring manual intervention or complex runtime decision-making logic
Solution Approach 2:
The patent applies preliminary action by requiring event handlers to be registered in advance with their trigger event definitions and attributes before runtime. This pre-registration phase establishes all necessary associations and filters, allowing the runtime system to simply match incoming events against the pre-configured registry without complex real-time processing
Data Source
AI summary
A mobile communications device, method, and medium are provided for capturing and handling a wide range of communication events. A registrar populates a push registry with information corresponding to an event handler. The registrar associates the event handler with a trigger event and stores the association in the push registry. An event receiver identifies an occurrence of the trigger event and calls an application management system (AMS) so that the AMS can initiate the event handler. Event filters, which can include user-definable filters, are applied to communication events according to filter definitions associated with the event handler.