Unified Interaction Instruction Conversion for Cross-Device Service Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service providers face significant development resource and cost challenges due to the need to create different application programs for various electronic devices with distinct operating systems and programming languages, which complicates interaction instruction processing across devices.
Innovation Solution
A method and device that configure instruction processing rules for each device type to convert device-specific interaction instructions into unified interaction instructions, allowing for unified interaction data processing and reducing the need for multiple interaction modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different application programs are developed for different types of electronic devices, then device compatibility and interaction instruction processing are improved, but development resources and costs increase significantly
Solution Approach 1:
The patent applies universality by creating a unified interaction instruction processing mechanism that can handle instructions from multiple device types (smartphones, PCs, VR devices) through a single service processing module. The system uses device type detection and corresponding rule-based conversion to make one module serve multiple device types, eliminating the need for separate application programs for each device.
Solution Approach 2:
The patent introduces an intermediary layer consisting of device type detection and instruction conversion rules. This intermediary translates device-specific interaction instructions into a unified format that the service processing module can handle, acting as a mediator between diverse devices and the unified service processing system.
2Measurement precision
If device-specific interaction modules are developed for each electronic device type, then interaction instruction accuracy is improved, but development time and costs increase
Solution Approach 1:
The patent applies preliminary action by pre-configuring instruction processing rules for different device types before runtime. The system detects the device type and retrieves the corresponding pre-prepared conversion rules, avoiding the need for runtime development or complex device-specific module loading. This preliminary preparation maintains accuracy while reducing development time.
3Ease of operation
If multiple service processing modules are created for different devices, then device-specific interaction handling is improved, but system complexity and maintenance difficulty increase
Solution Approach 1:
The patent applies segmentation by separating the instruction processing logic into distinct conversion rules for each device type, while keeping the core service processing module unified. This segmentation allows device-specific handling through modular rules that can be independently managed, while the overall system remains simple with a single main processing module.
Data Source
Figure 1A
Figure 1B
Figure 1C~1D
AI summary
The present application provides a service processing method and device. The method includes the following: detecting a device type of an electronic device that needs to display interaction data; obtaining an instruction processing rule corresponding to the detected device type; obtaining, based on the instruction processing rule, a device interaction instruction initiated by the electronic device, and converting the device interaction instruction into a corresponding unified interaction instruction; and processing the interaction data by invoking a service processing mode corresponding to the unified interaction instruction obtained through conversion, and providing processed interaction data for the electronic device for display. In implementations of the present application, a same interaction effect can be achieved based on different end-user devices and support capabilities, and there is no need to develop different interaction modules for different devices. Therefore, development resources and costs can be significantly reduced, and development efficiency can be improved.