XML-Based Mobile Device Testing System for Remote Diagnostics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and cost of testing mobile devices are increased due to proprietary testing software, manual testing, and the difficulty in sharing and reusing testing tools across factories, leading to challenges in maintenance, remote diagnosis, and data collection during research and development phases.
Innovation Solution
A mobile device testing system utilizing XML sheets to organize commands, allowing for reusable and scalable testing across local, remote, and factory environments, enabling automated testing and data collection through a user interface application, and a method for executing commands remotely or locally, with results stored and analyzed in a database.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If proprietary testing software is used in each factory, then testing can be performed locally, but manufacturing costs increase and software cannot be reused or shared
Solution Approach 1:
The patent creates a universal testing software platform that can be deployed across multiple factories and device types. The system uses a common core software that can adapt to different testing scenarios through configuration files and plug-ins, eliminating the need for each factory to maintain separate proprietary software while still enabling local testing capabilities.
Solution Approach 2:
The patent implements a centralized software repository where testing software can be copied and deployed to multiple locations. Instead of each factory developing unique software, the same core software can be instantiated across different factories, reducing maintenance overhead and enabling knowledge sharing while maintaining local operational independence.
2Adaptability or versatility
If new testing software is developed for each new-generation mobile device, then device-specific testing requirements are met, but development and maintenance costs increase
Solution Approach 1:
The testing software is designed as a universal platform that can test multiple device generations and types through a common interface. The system uses device-specific configuration files and test case adaptations rather than requiring complete software redevelopment for each new device, thereby maintaining adaptability while reducing development complexity.
Solution Approach 2:
The patent segments the testing software into modular components: a universal core engine, device-specific configuration layers, and test case modules. This segmentation allows the core software to remain unchanged while only the configuration and test case layers need adjustment for new devices, significantly reducing development and maintenance effort.
3Adaptability or versatility
If testing commands are added by modifying source code and recompiling, then new test functionality is achieved, but maintenance difficulty increases
Solution Approach 1:
The patent separates test command definitions from the core software code by using external configuration files and scripting languages. New test commands can be added by creating new configuration entries or script files without modifying or recompiling the core software, thereby maintaining flexibility while dramatically improving maintainability.
Solution Approach 2:
The patent introduces an intermediary layer (configuration files and scripting interface) between the user and the core software. This intermediary allows test commands to be defined and modified without touching the compiled core software, serving as a buffer that provides flexibility while protecting the stability of the main system.
4Ease of operation
If testing results are stored locally in mobile devices or testing computers, then data is readily accessible, but data collection for statistics becomes difficult
Solution Approach 1:
The patent merges local data storage with centralized data collection by implementing a dual-mode storage system. Testing results are stored locally for immediate access and simultaneously transmitted to a centralized server for aggregate analysis. This combination maintains local accessibility while enabling efficient statistical analysis across multiple devices and locations.
Solution Approach 2:
The system implements automated feedback loops where testing results are automatically collected, transmitted, and analyzed. The centralized server provides feedback to the local testing systems, enabling continuous improvement and statistical analysis without manual intervention, thereby improving both accessibility and collection efficiency.
Data Source
AI summary
Systems and methods for testing mobile device s are disclosed. In an embodiment, a mobile device testing system comprises a non-transitory memory and one or more hardware processors coupled to the non-transitory memory. The one or more hardware processors execute instructions to perform operations that include receiving a command XML sheet and rendering the command XML sheet into a user interface application, wherein the command XML sheet comprises elements corresponding to one or more commands for testing a mobile device.