Micro-service Framework for Cross-App Task Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current UX clients are limited in their ability to complete tasks that require interaction with multiple apps or online services, as they often lack the necessary APIs to interface with various services, leading to incomplete task execution.
Innovation Solution
A micro-service framework is implemented that conducts static analysis on apps to identify deep links and corresponding input parameters, allowing UX clients to execute micro-service requests through API calls to online services, thereby enabling the completion of complex tasks across multiple services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If UX clients are programmed with specific abilities to interface with services, then they can complete tasks requiring interaction with those services, but their scope and versatility are limited to their programming
Solution Approach 1:
The patent introduces a micro-service framework as an intermediary layer between UX clients and online services. This framework automatically generates and manages API calls to services on behalf of UX clients, eliminating the need for clients to be directly programmed with service-specific interface capabilities. The framework acts as a mediator that translates client requests into service interactions through generated code.
Solution Approach 2:
The system enables self-service by allowing UX clients to invoke services through natural interactions without requiring manual programming of service interfaces. The micro-service framework automatically handles the complex tasks of generating API calls, managing authentication, and coordinating service interactions, so clients can access services through simple high-level interfaces.
2Adaptability or versatility
If UX clients switch between multiple apps to complete general tasks, then they can access various services, but the process becomes complex and time-consuming
Solution Approach 1:
The patent merges multiple service interactions into a unified framework that handles all service calls through a single interface. Instead of switching between separate apps, the micro-service framework consolidates service access into one coordinated system that can execute multiple service calls sequentially or in parallel, reducing the time and complexity of task execution.
Solution Approach 2:
The framework performs preliminary actions by pre-generating and caching API call structures, authentication tokens, and service interaction patterns. This preparation allows UX clients to quickly invoke services without repeatedly establishing connections or re-authenticating, significantly reducing task execution time.
3Productivity
If static analysis is conducted on apps to identify deep links and execution paths, then micro-services can be systematically generated, but the analysis process becomes complex
Solution Approach 1:
The patent replaces manual, mechanical analysis of app code with automated static analysis tools that systematically parse and interpret application code to identify deep links and execution paths. This substitution of manual inspection with automated computational analysis dramatically increases productivity while managing complexity through standardized analysis algorithms.
Solution Approach 2:
The system manages analysis complexity by changing parameters such as analysis depth, coverage thresholds, and generation priorities. The framework can adjust these parameters to balance thoroughness with computational resources, generating micro-services at different levels of detail based on productivity requirements without overwhelming complexity.
Data Source
AI summary
Computer systems and methods for generating and interacting with a micro-service framework are provided. A micro-service corresponds to one or more deep link/API calls that carry out some particular function. A static analysis of an app is conducted, from one or more starting sources of the app to identify one or more valid and feasible execution paths, as well as corresponding input parameters within the app. Each valid execution path with corresponding input parameters represent a “deep link” or “API” for that app. The information regarding the deep link is collected and stored as a micro-service in a micro-service catalog. A micro-service framework is implemented that receives a micro-service request (i.e., a request that the micro-service be carried out on behalf of a computer user) from a UX client and executes that micro-service request via execution of the deep link.