Distributed Test Engine Control via Centralized Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distributed testing and monitoring systems face limitations due to high message volume requirements, processing capacity constraints, and difficulty in passing control messages through firewalls, which restrict the number of remote clients that can be used and affect system synchronization and effectiveness.
Innovation Solution
The system employs a plurality of distributed test engines controlled by a central controller using a control database and an API that allows communication via HTTP or other firewall-capable protocols, enabling efficient configuration, task assignment, and result recording, with separate control and analysis networks to maintain system stability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a message-based approach is used to control remote clients, then coordination and control can be achieved, but the volume of messages increases significantly, limiting the number of remote clients that can be managed
Solution Approach 1:
The system divides the control architecture into hierarchical segments: a central controller for high-level coordination and multiple remote clients for distributed execution. This segmentation allows the controller to manage groups of clients without requiring individual message exchange for every action, thereby reducing overall message volume while maintaining control coordination.
Solution Approach 2:
The patent introduces an intermediary mechanism where the central controller acts as a mediator that broadcasts commands to multiple remote clients simultaneously using multicast protocols. This intermediary approach consolidates what would otherwise require numerous individual messages into fewer broadcast messages, reducing message volume while preserving control effectiveness.
2Stability of the object's composition
If the central controller tracks status of multiple remote clients, then system coordination is maintained, but processing capacity is exceeded causing synchronization loss
Solution Approach 1:
The system segments the monitoring function by having remote clients autonomously track their own status and only report when necessary (event-driven reporting). This reduces the processing burden on the central controller while maintaining synchronization, as the controller receives updates only when state changes occur rather than continuously polling all clients.
Solution Approach 2:
The patent implements periodic status reporting where remote clients send updates at scheduled intervals or when specific events occur. This periodic action reduces the frequency of messages to the controller compared to continuous monitoring, allowing the controller to maintain synchronization information without being overwhelmed by constant status updates from numerous clients.
3Ease of operation
If proprietary communication protocols are used, then client-controller communication can be established, but system development costs increase
Solution Approach 1:
The system employs universal, standardized communication protocols (such as HTTP, TCP/IP) that can be implemented across multiple platforms and devices without requiring proprietary software development. This multi-functionality allows the same protocol stack to serve various communication needs between controllers and remote clients, significantly reducing development costs while maintaining robust communication capabilities.
4Ease of operation
If control messages are sent through firewalls, then remote clients can be controlled, but message exchange rate is limited by network interface capacity
Solution Approach 1:
The system segments network communication into control plane traffic (commands and status) and data plane traffic (test data and results). By using multicast protocols for control messages, the system efficiently handles firewall traversal while reducing the burden on network interfaces. Remote clients can receive control commands through firewall-friendly protocols without limiting the overall message exchange rate, as the multicast approach consolidates control traffic.
Data Source
AI summary
Various example embodiments are directed to systems and methods for managing a plurality of distributed test engines to test at least one device under analysis (DUA). A controller and a control database may be used to manage the plurality of test engines. The control database may have stored thereon a plurality of configuration documents, a plurality of instruction documents, and at least one statistics document. Each configuration document may be associated with at least one of the plurality of test engines and may indicate an execution group of the associated at least one test engine. Each instruction document may be associated with an execution group and may comprise an indication of a testing task to be performed by the execution group associated with the instruction document. The controller may be configured to write to the plurality of configuration documents to assign each of the plurality of test engines to an execution group; write to the plurality of instruction documents to provide, for each execution group, a testing task to be performed by test engines of the execution group on the at least one DUA. The control database may configured to receive from at least a portion of a plurality of test engines an update to the at least one statistics document.