Mobile Notification Delivery via Secure Hardware and Connectivity Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile notification systems rely on IP connectivity, leading to service disruptions when cellular data is deactivated, require significant engineering from telecom operators, and pose data privacy risks due to centralized service platforms, with no alternative solutions for maintaining functionality during platform unavailability.
Innovation Solution
A method for transmitting notifications using a secure hardware element in mobile terminals, which determines suitable connectivity based on terminal identifiers to communicate with the terminal via compatible devices like SMS or USSD, ensuring notifications are delivered even without IP connectivity, while maintaining user privacy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a permanent communication channel is established between the terminal and service platform using IP connectivity, then notifications can be delivered in quasi-real time, but the service becomes disrupted when cellular data is deactivated
Solution Approach 1:
The notification system is designed to support multiple communication channels (IP-based permanent channel, SMS, USSD) that can be selected based on connectivity availability. The system universally handles different transmission methods through a single architecture that adapts to available resources, ensuring notification delivery regardless of which communication channel is active.
Solution Approach 2:
The system dynamically selects the appropriate communication channel based on real-time connectivity conditions. When IP connectivity is available, it uses the permanent communication channel; when cellular data is deactivated, it dynamically switches to alternative channels like SMS or USSD. This dynamic adaptation ensures continuous notification delivery despite changing network conditions.
2Productivity
If a permanent communication channel is maintained between terminal and service platform, then notifications can be delivered efficiently, but significant engineering is required from telecom operators
Solution Approach 1:
The system introduces an intermediary notification service that bridges the terminal and application servers. This intermediary handles the complexity of multiple communication channels and translates various transmission methods (IP, SMS, USSD) into unified notification delivery. The intermediary absorbs the infrastructure complexity, preventing it from propagating to telecom operators while maintaining efficient notification delivery.
Solution Approach 2:
The notification system performs self-service by automatically selecting appropriate communication channels based on connectivity conditions without requiring manual configuration or complex operator intervention. The system autonomously manages channel selection, retry logic, and fallback mechanisms, reducing the operational burden on telecom operators while maintaining high delivery efficiency.
3Productivity
If centralized service platforms are used for notification management, then notification delivery can be coordinated efficiently, but data privacy risks increase due to centralized access to sensitive information
Solution Approach 1:
The notification system is segmented into distributed components: terminal-based notification services, network-based intermediaries, and application server integrations. Each segment handles specific functions locally or semi-locally, distributing data processing across multiple trusted entities rather than centralizing all sensitive information in a single platform. This segmentation reduces privacy risks while maintaining coordination efficiency through standardized interfaces.
Solution Approach 2:
The system implements local quality by allowing terminals to maintain local notification services that process and manage notifications locally when possible. Sensitive data remains on the terminal or in distributed locations rather than being centralized. The local notification service coordinates with network intermediaries only when necessary, minimizing data transmission and reducing privacy exposure while maintaining efficient local notification delivery.
4Ease of operation
If the notification system requires IP connectivity, then modern notification protocols can be used, but the terminal cannot receive notifications when cellular data is deactivated
Solution Approach 1:
The notification system is designed with universal compatibility across multiple connectivity types including IP-based connections, SMS, and USSD. The same notification service architecture handles all these different connection types, allowing the terminal to receive notifications regardless of which connectivity type is available. This multi-functionality ensures ease of operation by maintaining notification reception availability across diverse network conditions.
Solution Approach 2:
The system changes operational parameters based on available connectivity. When IP connectivity is available, it uses modern notification protocols over data connections. When cellular data is deactivated, it changes parameters to use SMS or USSD-based notification mechanisms. This parameter adaptation maintains notification reception availability while flexibly adapting to different connectivity types without requiring the terminal to be constantly connected via IP.
Data Source
AI summary
A method is described for transmitting a notification to an application of a mobile terminal having a secure hardware element allowing the authentication of said mobile terminal in a telecommunications network. The method includes receiving a notification from an application server, the notification including at least one identifier of the mobile terminal and at least one identifier of the application, obtaining, depending on the at least one identifier of the mobile terminal, at least one item of connectivity data, determining, depending on the obtained item of connectivity data, an access parameter for access to at least one communication device able to communicate with the mobile terminal, and transmitting the notification to the communication device accessible via the access parameter.