Mobile Device Operational Status XML Message Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems for determining the operational status of mobile devices executing server-side applications face challenges in diagnosing errors due to lack of technical expertise among users and the complexity of installation programs, which can hinder effective troubleshooting and periodic status assessment.
Innovation Solution
A method involving the exchange of XML messages between a middleware server and mobile devices to request and respond with operational status information, ensuring that the response message omits illegal XML characters through an XML formatter, allowing for efficient status determination and error diagnosis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of repair
If users are expected to diagnose errors at mobile devices, then error diagnosis capability is improved, but user technical expertise requirement increases
Solution Approach 1:
The patent introduces an intermediary system (error diagnosis server) that mediates between the mobile device and the user. The server receives error information from the device, processes it, and provides diagnosis results to the user without requiring the user to have technical expertise. This resolves the contradiction by enabling error diagnosis capability while eliminating the need for users to possess technical knowledge.
Solution Approach 2:
The system implements self-service by automatically collecting error information from mobile devices and generating diagnosis reports without human intervention. The error diagnosis server autonomously processes error data, identifies issues, and communicates results, allowing the system to serve itself rather than requiring expert users to perform diagnosis tasks.
2Adaptability or versatility
If complex installation programs are provided, then application functionality is improved, but installation complexity increases
Solution Approach 1:
The patent extracts the complex installation program from the mobile device and relocates it to a server environment. Applications are installed and executed on the server, while the mobile device only needs to access and interact with the application through a simplified interface. This separation removes installation complexity from the user's device while maintaining full application functionality on the server.
Solution Approach 2:
The patent replaces the mechanical installation process (downloading, configuring, and installing software on the device) with a network-based access model. Instead of physically installing complex programs on the mobile device, users simply access applications through the network, substituting the mechanical installation system with a lighter, network-centric approach that maintains functionality while reducing complexity.
3Reliability
If periodic status assessment of mobile devices is implemented, then system reliability is improved, but communication overhead increases
Solution Approach 1:
The patent implements periodic status assessment by having mobile devices send error information and status updates at scheduled intervals to the error diagnosis server. This periodic communication allows the system to monitor device health and detect issues over time, improving reliability while managing communication overhead through structured, interval-based data exchange rather than continuous monitoring.
Solution Approach 2:
The system applies partial action by selectively collecting only relevant error information and status data from mobile devices, rather than continuously monitoring all device functions. The error diagnosis server requests specific information when needed, reducing unnecessary communication overhead while maintaining sufficient data for reliability assessment and issue detection.
Data Source
AI summary
To determine the operational status of a wireless communication device capable of executing server-side applications, a message is sent to the device requesting operational status of the device. The message may be may be triggered by a system administrator at a middleware server. The wireless communication device may receive the message, compose a response message indicative of the operational status of the device, and send the response message back to the middleware server. The messages may be extensible markup language (XML) messages. Composition of the response message may entail verifying that a textual operational status description forming part of the response message omits illegal XML characters, e.g., by passing the description through an XML formatter for removal of any illegal XML characters.