API Adaptation Layer for Cross-Platform Router Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing application programs for intelligent routers is highly difficult due to the lack of a specialized router system and differing API call syntax rules between various operating systems, such as ANDROID and LINUX.
Innovation Solution
An operating method that involves converting API call requests and responses between different systems using preset mapping relationships, allowing application programs to call APIs across different platforms, thereby simplifying the development process by using a universal development platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a specialized router system is used, then the router can achieve intelligent management functions, but the difficulty of developing application programs increases significantly
Solution Approach 1:
The patent introduces an intermediary layer (API adaptation layer) between the application program and the router system. This intermediary translates API calls from one system's syntax to another's, allowing application programs developed for universal platforms to communicate with specialized router systems without requiring developers to learn multiple syntax rules. The intermediary resolves the contradiction by maintaining intelligent management capabilities while simplifying the development process.
Solution Approach 2:
The patent implements a universal API interface layer that can adapt to multiple different router systems and operating systems. This universal layer provides consistent programming interfaces regardless of the underlying system, enabling application programs to run on universal platforms while accessing router-specific functions. This resolves the contradiction by making the development process universal while maintaining system-specific capabilities.
2Adaptability or versatility
If different operating systems are used in routing devices, then more functionality can be achieved, but API call syntax rules differ making development more complex
Solution Approach 1:
The patent introduces an API adaptation intermediary that sits between the application program and different operating systems. This intermediary translates API calls from a universal syntax to the specific syntax requirements of each operating system (ANDROID, LINUX, etc.). The intermediary maintains a mapping relationship between different API syntaxes, allowing application programs to use a unified interface while the intermediary handles the complexity of syntax conversion to multiple operating systems.
3Ease of manufacture
If a universal development platform is used, then application program development is simplified, but direct access to router-specific APIs is lost
Solution Approach 1:
The patent introduces an API adaptation intermediary that acts as a bridge between the universal development platform and router-specific APIs. The intermediary maintains mapping relationships between universal API interfaces and router-specific API interfaces, ensuring that calls from the universal platform are accurately translated to the appropriate router-specific commands. This preserves both the development ease of universal platforms and the access accuracy to router-specific functions.
Solution Approach 2:
The patent implements preliminary configuration of API mapping relationships between universal interfaces and router-specific interfaces. During system initialization or configuration phase, the intermediary pre-establishes the correspondence between different API syntaxes. This preliminary action ensures that when application programs are developed on universal platforms, the API translations are already optimized and accurate, maintaining both development ease and access reliability.
Data Source
AI summary
An operating method of a routing device, a routing device and a terminal device, where the routing device includes a first system and a second system, and the method includes acquiring, by the first system, a first application programming interface (API) call request, where the first API call request is sent by an application program running in the first system, converting, by the first system, the first API call request into a second API call request matching the second system, sending the second API call request to the second system, and executing, by the second system, the second API call request. Hence, difficulty of developing the application program on the routing device can be reduced.