Remote View Logic for Coordinated Electronic Device Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional coordinated control methods between intelligent devices, such as smartphones and smart TVs, are limited in scenario adaptability as they require customized components and parameters on the controlling device, restricting the range of applications and scenarios that can be simultaneously managed.
Innovation Solution
A coordinated control method and system where the second intelligent device sends remote view logic information, including an interface layout file, to the first device, allowing it to locally load and bind services related to the application, enabling the first device to control the second device without needing customized components or parameters, and allowing for distributed application logic synchronization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If customized components and parameters are created on the controlling device for each application scenario, then the coordinated control function can be implemented, but the device complexity increases and the adaptability to different scenarios is limited
Solution Approach 1:
The patent uses interface layout files that define the structure and components of application interfaces. Instead of customizing components on the controlling device, the interface layout files are copied from the controlled device and locally loaded, allowing the controlling device to render interfaces without having the actual application components installed.
Solution Approach 2:
The patent creates a universal coordinated control mechanism that works across different applications and scenarios through a standardized interface layout file format. The same control architecture can handle various applications (video playback, picture viewing, etc.) by simply loading different interface layout files, eliminating the need for scenario-specific customizations.
2Ease of operation
If application-specific components and parameters are customized on the controlling device, then the application can be controlled, but the quantity of components and parameters increases
Solution Approach 1:
The patent extracts the interface definition from the application components themselves and separates it into independent interface layout files. These files contain only the structural information needed for rendering, while the actual application logic and data remain on the controlled device, reducing the quantity of components needed on the controlling device.
Solution Approach 2:
The patent introduces interface layout files as an intermediary between the controlled device and the controlling device. These files serve as a lightweight representation that enables coordination without requiring the full application components to be present on the controlling device.
3Reliability
If the controlling device loads all application components locally, then complete control is achieved, but the loss of information is reduced only at the cost of increased device complexity
Solution Approach 1:
The patent segments the application into two parts: interface definition (stored in interface layout files that can be transmitted and loaded) and application logic (remaining on the controlled device). This segmentation allows the controlling device to have reliable control over the interface presentation without needing to host the entire application.
Solution Approach 2:
The patent performs preliminary action by pre-defining interface layouts in portable files that can be prepared in advance and transmitted to the controlling device. This allows the controlling device to have all necessary interface information available before actual coordination occurs, ensuring reliable control without last-minute component installation.
Data Source
AI summary
This application discloses a coordinated control method and system for electronic devices. When triggering coordinated control, a second electronic device sends remote view logic information associated with a running business to a first electronic device. The first device directly locally loads an application-related interface based on an interface layout file included in the remote view logic information. In this way, for the first device end, a component, a parameter, and the like that are related to the running application of the second device do not need to be customized on the first device end for the running application, and only the remote view logic information transmitted to the first device needs to be loaded. Distributed application logic may be defined for all running applications of the second device on a side of the second device, and then the second device synchronizes the distributed application logic with the first device.