XMPP Message Broker for Mobile Device Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile telecommunication device management systems using Server/Client agents are limited by scalability and cost, particularly for bottom-of-the-pyramid solutions, as they require persistent connections and heavy client components, restricting the number of clients that can be managed effectively.
Innovation Solution
Implementing a general-purpose messaging protocol like XMPP (Extensible Messaging and Presence Protocol) for bi-directional, non-blocking asynchronous communication between server and client agents, using a message broker to facilitate seamless asynchronous messaging, allowing for a large number of clients to be managed without persistent connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Server/Client agents are used for device management, then device control and monitoring capability is provided, but scalability is limited and system cost increases
Solution Approach 1:
The patent introduces an XMPP message broker as an intermediary component that mediates communication between management servers and mobile devices. The broker receives management commands from servers, routes them to appropriate devices, and delivers device responses back to servers, enabling scalable many-to-many communication without persistent connections between servers and devices
Solution Approach 2:
The patent replaces the traditional HTTP request-response model with XMPP publish-subscribe messaging. Instead of blocking server sockets waiting for client actions or requiring clients to run lightweight servers, the system uses asynchronous XMPP stanzas that enable fire-and-forget command delivery and push-based device status reporting
2Reliability
If persistent connections are maintained for device management, then real-time control is enabled, but the number of manageable clients is restricted
Solution Approach 1:
The patent implements periodic presence broadcasting by devices to the XMPP broker, which announces device availability and status at regular intervals. Management servers subscribe to presence updates and receive notifications when devices come online or go offline, enabling real-time awareness without maintaining persistent bidirectional connections
Solution Approach 2:
The XMPP message broker acts as a centralized intermediary that maintains connection state with all devices and manages message routing. Devices connect to the broker rather than directly to management servers, allowing the broker to efficiently manage many concurrent connections and route messages only to relevant recipients
3Use of energy by moving object
If lightweight client components are deployed on mobile devices, then device resource consumption is reduced, but server-initiated communication becomes complex
Solution Approach 1:
The patent enables devices to autonomously publish their status information to the XMPP broker without server requests. Devices automatically generate and send presence stanzas and status updates, eliminating the need for servers to initiate communication or for devices to implement complex server-like functionality
Solution Approach 2:
The patent inverts the traditional client-server communication model by enabling devices to push information to servers through XMPP presence publishing, rather than servers polling devices. This reversal simplifies device software while maintaining real-time visibility of device status
Data Source
Figure 1A
Figure 1B
Figure 2A
AI summary
A system uses a general purpose messaging transport protocol to manage, control, and monitor a mobile communication device and/or a plurality of mobile communication devices.