On-Site AI API Routing for Low-Latency Secure Traffic Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
On-site devices such as cameras, scanners, and point-of-sale systems experience increased latency and security vulnerabilities due to communicating with remote servers, as different devices contact different servers, leading to high traffic at particular servers and exposure to attacks like data exfiltration and DDoS.
Innovation Solution
Implementing on-site artificial intelligence (AI) application programming interfaces (APIs) managed by an API manager that provision APIs closer to devices, use AI to monitor traffic patterns, and generate new API instances or cache inputs to reduce latency and detect security risks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If on-site devices communicate with remote servers through centralized APIs, then data processing capability is improved, but latency increases and security vulnerabilities arise
Solution Approach 1:
The patent segments the centralized API system into multiple distributed API instances deployed across different locations. Each on-site device can be assigned to a nearby API instance, reducing communication latency while maintaining distributed data processing capability. This segmentation resolves the contradiction by enabling both improved reliability through distribution and reduced latency through geographic proximity.
Solution Approach 2:
The patent introduces a spatial dimension to API deployment by distributing API instances across multiple geographic locations rather than concentrating them in a single remote server. This dimensional change allows on-site devices to communicate with nearest API instances, reducing latency while maintaining the distributed processing architecture for improved reliability.
2Productivity
If multiple devices contact different remote servers, then processing capacity is improved, but security exposure to attacks increases
Solution Approach 1:
The patent introduces an API manager as an intermediary component that coordinates communication between on-site devices and API instances. The API manager implements security measures such as authentication, authorization, and traffic monitoring across all API instances, providing centralized security control while maintaining distributed processing capacity. This intermediary resolves the contradiction by enabling high productivity through distribution while mitigating security vulnerabilities through unified security management.
3Ease of operation
If centralized API management is used, then system control is improved, but traffic patterns cause server overload and increased latency
Solution Approach 1:
The patent segments the centralized API management into multiple distributed API instances, each handling a portion of the traffic load. The API manager distributes requests across these instances based on current traffic patterns and server capacity, maintaining system control while preventing any single server from becoming overloaded. This segmentation resolves the contradiction by preserving ease of operation through centralized coordination while reducing latency through load distribution.
Solution Approach 2:
The patent implements dynamic load balancing where the API manager continuously monitors traffic patterns and adjusts the distribution of requests to API instances in real-time. This dynamic adaptation allows the system to maintain optimal performance under varying traffic conditions, resolving the contradiction between centralized control and traffic-induced latency by making the system responsive to changing conditions.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
In some implementations, an application programming interfaces (API) manager may receive, at a set of artificial intelligence (AI) APIs, a set of inputs from a set of on-site devices. Accordingly, the API manager may route the set of inputs to a corresponding set of remote servers and may receive, from at least one server of the corresponding set of remote servers, at least one response based on at least one input, from the set of inputs, routed to the at least one server. The API manager may transmit the at least one response to a corresponding device from the set of on-site devices. Further, the API manager may modify at least one API, of the set of AI APIs, based on a traffic pattern associated with the set of inputs and the at least one response.