Mobile OS Update Partitioning and Version Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing software delivery systems for mobile devices face challenges in managing efficient and quick updates of both mobile device operating systems and apps, particularly due to the complex interdependence between firmware and feature apps, which can lead to system instability and difficulties in ensuring high-quality software releases.
Innovation Solution
A system is introduced that includes additional stages in the software development pipeline for integration and testing of firmware and feature apps before promotion to the master or release stages, incorporating manual and automated tests, and a delivery service that supports different release cycles for system updates and app updates, allowing for faster and more stable deployment of software changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If software updates are delivered quickly to mobile devices, then productivity and user satisfaction improve, but system stability and reliability may deteriorate due to insufficient testing and integration issues between firmware and feature apps
Solution Approach 1:
The software delivery system is segmented into multiple independent stages: pre-alpha, alpha, beta, and release stages. Each stage has specific testing and validation requirements, allowing rapid iteration in early stages while ensuring thorough validation before release. This segmentation enables parallel development of firmware and feature apps without compromising overall system stability.
Solution Approach 2:
The system performs preliminary actions by conducting automated and manual tests in pre-alpha and alpha stages before full integration. Feature apps are tested independently against firmware builds in advance, and integration issues are identified and resolved before the software reaches the release stage, ensuring stability while maintaining update speed.
2Reliability
If comprehensive testing and integration stages are added to the software development pipeline, then system reliability and quality improve, but device complexity and development time increase
Solution Approach 1:
The software delivery system implements self-service through automated testing and validation mechanisms. Automated tests are executed across multiple stages without manual intervention, and the system automatically manages version control, dependency resolution, and integration validation between firmware and feature apps, reducing the perceived complexity for developers.
Solution Approach 2:
The system changes parameters by dynamically adjusting testing depth and validation requirements based on the software stage. Pre-alpha and alpha stages use automated testing with specific parameter sets, while beta and release stages incorporate additional manual testing and integration validation, optimizing the balance between quality assurance and development efficiency at each phase.
3Stability of the object's composition
If firmware and feature apps are updated together in integrated releases, then system consistency is maintained, but update flexibility and speed of individual app deployments decrease
Solution Approach 1:
The update system is segmented to allow independent updates of firmware and feature apps. Feature apps can be updated separately from firmware through the same delivery pipeline, enabling flexible deployment schedules and targeted updates without requiring full system reintegration, thus maintaining consistency while improving flexibility.
Solution Approach 2:
The software delivery service implements a universal pipeline that handles both firmware updates and feature app updates through the same staged process. This multi-functional system maintains system consistency through standardized validation while providing the adaptability to update individual components independently based on specific needs and readiness.
Data Source
AI summary
A system of mobile device operation system and apps delivery is disclosed. All updates of the mobile device including system updates and feature apps updates are delivered over-the-air (“OTA”). When a system update is available, it is delivered to the mobile device for download and installation. If feature apps updates are available but a system update is not available, the system delivers the feature apps updates to the mobile device for download and installation. Feature apps updates coming from the two different routes are stored in different partitions of the OS image on the mobile device for version control. Feature apps updates included in subsequent system updates takes precedent over previously installed updates of the same or earlier versions.