Proxy Service Translation for Cross-Device Calling APIs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing consumer electronic devices with different memory and storage capacities require different communication interfaces, making it difficult for developers to create unified software development tools and increasing the development threshold.
Innovation Solution
A proxy service-based method is introduced to unify the distributed service interfaces of electronic devices, allowing developers to access devices with varying capabilities through a single API interface, using a proxy service process that converts between different communication protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If different communication interfaces are used for devices with different memory and storage capacities, then device-specific optimization is achieved, but developer complexity increases and unified software development becomes difficult
Solution Approach 1:
The patent introduces a proxy service as an intermediary component that sits between the developer's unified API calls and the device-specific communication interfaces. The proxy service receives standardized requests, determines the target device type, and translates them into appropriate device-specific protocols (RPC for rich devices, message sending for thin devices). This mediator approach allows developers to work with a single interface while maintaining optimized device-specific communication paths.
Solution Approach 2:
The proxy service is designed with multi-functionality to handle multiple device types through a single unified interface. It can identify different device categories (rich devices with abundant memory/storage versus thin devices with limited resources) and automatically select the appropriate communication strategy. This universal approach eliminates the need for developers to create separate interfaces for different device types while preserving device-specific optimization.
2Adaptability or versatility
If multiple software development toolkits are provided for different device types, then device compatibility is improved, but the number of toolkits increases and development threshold rises
Solution Approach 1:
The patent merges multiple device-specific toolkits into a single unified SDK that provides a consistent API for all device types. The proxy service consolidates the functionality that would otherwise require separate toolkits for rich devices and thin devices. Developers now use one unified toolkit that automatically adapts to different device types through the proxy service's translation layer, reducing the number of toolkits from multiple to one while maintaining full device compatibility.
3Reliability
If device type differentiation is maintained in the API interface, then precise device control is achieved, but ease of operation decreases and development experience deteriorates
Solution Approach 1:
The proxy service implements self-service by automatically detecting the target device type and selecting the appropriate communication protocol without requiring developer intervention. The service autonomously handles device classification (rich vs. thin devices) and protocol selection (RPC vs. message sending), allowing developers to write simple unified code that the proxy service automatically optimizes for the specific device type. This self-service approach maintains precise device control while dramatically improving ease of operation.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Embodiments of this application provide a proxy service-based device calling method, and relate to the field of electronic devices. A proxy service process is pre-installed on a distributed calling initiator, and the proxy service process is compatible with different types of communication interfaces. When a calling initiator initiates distributed scheduling to a called entity, the calling initiator is called to the proxy service process through a specified communication interface, and the proxy service process forwards a calling request to the called entity. Embodiments of this application further provide an electronic device and a computer-readable storage medium. In this application, distributed service interfaces of different types of electronic devices are unified, and a set of unified API interfaces is provided. Therefore, a developer may not consider a device type of a called device when performing distributed service scheduling and development, to lower a development threshold, and improve development experience.