Man-machine interaction power supply control system and method based on event trigger mechanism

Abstract

The invention discloses a man-machine interaction power supply control system and method based on an event triggering mechanism. The man-machine interaction power supply control system comprises a data storage module, an event monitoring module and an event distribution module which are connected in sequence, the event distribution module is connected with a human-computer interaction interface module and an instruction control module, and is provided with an external system interface; data configuration change in a power supply system is used as a unified event source, high collaboration of man-machine interaction and power supply control is realized by establishing a standardized event monitoring, packaging, distributing and processing flow, and complete closed-loop control from user operation to equipment response to state feedback is realized; the system has the advantages of high real-time performance, low delay, high resource efficiency, strong decoupling, high maintainability, excellent expandability and excellent user experience, and the reliability of the system is improved.

Description

Technical Field

[0001] This invention relates to a power control system, and more particularly to a human-computer interaction power control system and method based on an event-triggered mechanism. Background Technology

[0002] With the rapid development of power electronics technology, the Industrial Internet, and intelligent manufacturing, modern power control systems have evolved from single, isolated power conversion devices into crucial components of complex, networked, and intelligent systems. In high-end equipment manufacturing, precision testing, data centers, and new energy fields, unprecedented demands are being placed on the control precision, response speed, operational reliability, and human-machine interface of power systems. Users expect to set and monitor power parameters (such as voltage, current, and power) in real time and with precision through intuitive interfaces (such as touchscreens, web interfaces, and mobile apps), ensuring that control commands are executed without delay and that system status is seamlessly synchronized across all interactive terminals.

[0003] This development trend urgently requires power control systems to break through the limitations of traditional architectures and build a new technical solution that can achieve deep collaboration and efficient response at the data, control and interaction levels, in order to meet the core demands of increasingly complex applications for system real-time performance, flexibility and scalability.

[0004] Existing technology and its limitations:

[0005] Currently, the power control field primarily employs a centralized control architecture and polling mechanism as its core technical solutions. In a centralized control architecture, the system tightly couples the human-machine interface, core control logic, and hardware driver instructions, forming a highly integrated control mode. This architecture blurs the boundaries between internal modules, and any functional adjustment (such as interface updates or protocol upgrades) can trigger a global code refactoring, significantly increasing maintenance costs and development complexity. Simultaneously, system scalability is severely limited; integrating new external systems or functional modules requires deep modifications to the core code, making it difficult to adapt to rapidly changing business needs.

[0006] Polling-based query mechanisms are another widely adopted approach. This system periodically checks power status or configuration data updates at fixed time intervals. This passive monitoring method limits system response performance to the preset polling cycle, failing to achieve real-time detection of status changes, thus resulting in unavoidable control delays and real-time performance deficiencies. More significantly, regardless of whether the data has actually changed, continuous polling consumes valuable CPU computing resources and communication bandwidth, leading to low system resource utilization. In applications with high reliability requirements, instantaneous status changes or fault signals are easily missed between two query intervals, posing a potential threat to system safety.

[0007] In distributed application environments with multi-terminal collaboration, existing technologies face severe challenges in state synchronization. Systems typically rely on customized point-to-point communication or simple client query mechanisms, lacking a unified and efficient message distribution system. This approach struggles to guarantee data consistency across terminals, often resulting in discrepancies in displayed states on different interfaces due to network latency and query timing differences, severely impacting operational decisions. Furthermore, the triggering mechanism for control commands is significantly inadequate. Command issuance is often limited to fixed control cycles or requires additional user confirmation, rather than responding instantly to data changes. This not only leads to delayed power output adjustments but also severely impacts user experience, significantly lacking smoothness and intuitiveness in the operational process.

[0008] It is worth noting that although event-driven architecture has been widely used in general software design, it still has significant shortcomings in the deep integration of human-computer interaction and command execution in the specific field of power control. Existing event-driven solutions are often limited to the implementation of local functions, failing to form a complete closed loop from interface operation to command issuance and status feedback, and thus unable to systematically solve the core problems of real-time performance, decoupling, and scalability faced in the field of power control. This lack of integration makes it difficult for existing event-driven technologies to meet the high standards of modern intelligent power control systems for full-process collaborative control.

[0009] In view of this, the present invention is hereby proposed. Summary of the Invention

[0010] The purpose of this invention is to provide a human-computer interaction power control system and method based on an event-triggered mechanism to solve the above-mentioned technical problems existing in the prior art.

[0011] The objective of this invention is achieved through the following technical solution:

[0012] A human-computer interaction power control system based on an event-triggered mechanism includes a data storage module, an event listening module, and an event distribution module connected in sequence.

[0013] The event distribution module is connected to the human-machine interface module and the command control module, and is equipped with an external system interface;

[0014] The data storage module serves as the foundation of the system and is responsible for persisting or caching all power configuration parameters and real-time status data.

[0015] The event monitoring module constitutes the system's perception layer and uses technologies such as the observer pattern or monitoring services to continuously monitor changes in preset key data items in the data storage module.

[0016] The event distribution module contains a message bus, which is the information hub and scheduling center of the system. This module receives event objects from the listening module and intelligently distributes them according to predefined routing rules.

[0017] The human-computer interaction interface module consists of multiple independently operable intelligent UI components. These components adopt a subscription mechanism and register the data change events or message topics they are interested in during initialization.

[0018] The instruction control module, as the system's execution terminal, is specifically designed to subscribe to data change events that require driving hardware actions.

[0019] The above-mentioned system implements a method for human-machine interactive power control, including the following steps:

[0020] Step 1: System Initialization:

[0021] The system begins operation during the initialization phase, with each module starting in a predetermined order.

[0022] Step 2: Data Change Monitoring

[0023] After the system enters a stable operating phase, the event monitoring module begins to continuously monitor changes in multiple data sources;

[0024] Step 3: Event Generation and Encapsulation:

[0025] When a change in data is detected, the system immediately enters the event generation and encapsulation phase;

[0026] Step 4: Event dispatching and processing:

[0027] The event dispatch and processing phase employs a multi-path parallel execution mechanism;

[0028] Step 5: Subscriber Processing:

[0029] The subscriber processing phase adopts an asynchronous execution mode. After obtaining messages on relevant topics from the message bus, the various internal and external subscription modules process them according to their own business logic.

[0030] Step 6: Closed-loop feedback:

[0031] The system ensures state consistency through a closed-loop feedback mechanism;

[0032] Step 7: Exception Handling

[0033] An exception handling mechanism is implemented in every stage of system operation;

[0034] The entire system achieves event-triggered intelligent power control through the cyclical execution of the above seven steps, realizing a complete closed-loop control from user operation to device response and status feedback.

[0035] Compared with existing technologies, the human-computer interaction power control system and method based on event triggering mechanism provided by this invention have the following advantages: high real-time performance and low latency, high resource efficiency, strong decoupling and high maintainability, excellent scalability, superior user experience, and improved system reliability. Attached Figure Description

[0036] Figure 1 A module architecture diagram of a human-computer interaction power control system based on an event-triggered mechanism provided in an embodiment of the present invention;

[0037] Figure 2 This is a system operation flowchart of an embodiment of the present invention. Detailed Implementation

[0038] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them, and do not constitute a limitation on the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the protection scope of the present invention.

[0039] First, the following explanations are provided for the terms that may be used in this article:

[0040] The terms “including,” “contains,” “comprising,” “having,” or other similar semantic descriptions shall be interpreted as non-exclusive inclusion.

[0041] The term "composed of" excludes any technical features not expressly listed. When used in a claim, it closes the claim to exclude all technical features other than those expressly listed, except for associated conventional impurities. If the term appears only in a clause of a claim, it limits the claim to the elements expressly listed in that clause; elements recited in other clauses are not excluded from the overall claim.

[0042] The technical solution provided by this invention will be described in detail below. Contents not described in detail in the embodiments of this invention are prior art known to those skilled in the art. Where specific conditions are not specified in the embodiments of this invention, they shall be performed according to conventional conditions in the art or conditions recommended by the manufacturer. Reagents or instruments used in the embodiments of this invention whose manufacturers are not specified are all conventional products that can be purchased commercially.

[0043] like Figure 1As shown, a human-computer interaction power control system based on an event-triggered mechanism is characterized by comprising a data storage module, an event listening module, and an event distribution module connected in sequence.

[0044] The event distribution module is connected to the human-machine interface module and the command control module, and is equipped with an external system interface;

[0045] The data storage module serves as the foundation of the system and is responsible for persisting or caching all power configuration parameters and real-time status data.

[0046] The event monitoring module constitutes the system's perception layer and uses technologies such as the observer pattern or monitoring services to continuously monitor changes in preset key data items in the data storage module.

[0047] The event distribution module contains a message bus, which is the information hub and scheduling center of the system. This module receives event objects from the listening module and intelligently distributes them according to predefined routing rules.

[0048] The human-computer interaction interface module consists of multiple independently operable intelligent UI components. These components adopt a subscription mechanism and register the data change events or message topics they are interested in during initialization.

[0049] The instruction control module, as the system's execution terminal, is specifically designed to subscribe to data change events that require driving hardware actions.

[0050] The data storage module provides a unified and reliable data source for the entire system, ensuring data consistency and integrity.

[0051] Once the event listening module detects a data change, it will immediately respond and generate a standardized event object, providing a basis for subsequent processing.

[0052] The high-performance message bus integrated within the event distribution module supports a topic-based publish-subscribe pattern and can route events in parallel to the following three processing channels:

[0053] Drive the human-computer interaction interface module to perform precise local display refresh;

[0054] The trigger instruction control module generates and issues hardware control instructions;

[0055] The event content is encapsulated as a message and published to the corresponding topic on the bus to achieve broadcast distribution of information.

[0056] After receiving an event notification, the human-computer interaction interface module only updates its corresponding display area to achieve efficient and accurate local refresh. At the same time, it is responsible for converting user operations into data modification requests, which become the source of new events.

[0057] The instruction control module has built-in instruction generation logic. When it receives a relevant event, it can automatically generate control instructions that conform to the hardware communication protocol based on the event content, and send them to the power supply device through the corresponding physical interface to complete the final control execution.

[0058] The system supports external system access through an open architecture of an external system interface message bus. Any external application or service can obtain system status changes and control information in real time simply by subscribing to the relevant message topics, thus achieving seamless and decoupled integration with the external environment.

[0059] The various modules of the system are organically connected through standardized event flow and message flow, together forming a smart power control architecture that is responsive, has clear responsibilities, and is easy to expand.

[0060] The modules collaborate through defined interface specifications to form a complete event-driven processing chain. When the system starts, each module initializes in sequence, establishes necessary connections and subscription relationships, and enters a standby state. When data changes, the system automatically triggers the corresponding event processing flow to ensure timely data updates and accurate execution of instructions.

[0061] The above-mentioned system implements a method for human-machine interactive power control, including the following steps:

[0062] Step 1: System Initialization:

[0063] The system begins operation during the initialization phase, with each module starting in a predetermined order.

[0064] Step 2: Data Change Monitoring

[0065] After the system enters a stable operating phase, the event monitoring module begins to continuously monitor changes in multiple data sources;

[0066] Step 3: Event Generation and Encapsulation:

[0067] When a change in data is detected, the system immediately enters the event generation and encapsulation phase;

[0068] Step 4: Event dispatching and processing:

[0069] The event dispatch and processing phase employs a multi-path parallel execution mechanism;

[0070] Step 5: Subscriber Processing:

[0071] The subscriber processing phase adopts an asynchronous execution mode. After obtaining messages on relevant topics from the message bus, the various internal and external subscription modules process them according to their own business logic.

[0072] Step 6: Closed-loop feedback:

[0073] The system ensures state consistency through a closed-loop feedback mechanism;

[0074] Step 7: Exception Handling

[0075] An exception handling mechanism is implemented in every stage of system operation;

[0076] The entire system achieves event-triggered intelligent power control through the cyclical execution of the above seven steps, realizing a complete closed-loop control from user operation to device response and status feedback.

[0077] In step 1, the data storage module first loads the device configuration and system parameters, establishes a data image in memory, and initializes the database connection;

[0078] The event listening module then starts the monitoring service and registers interceptors for data access, laying the foundation for subsequent event capture.

[0079] The message bus module initializes the switch and queue, establishes topic routing rules, and at the same time, the business service module completes its own state preparation and waits to process events.

[0080] The entire initialization process ensures that all system components are in a ready state, providing a stable foundation for subsequent event-driven mechanisms;

[0081] In step 2, the monitoring scope covers all possible ways that may cause data changes, such as user interface operations, remote API calls, scheduled task triggers, and device status updates.

[0082] The monitoring mechanism is implemented through a unified data access interface, and any modification operation to the stored data will be captured in real time;

[0083] This comprehensive monitoring ensures that the system can detect any changes in status in a timely manner, providing a guarantee for rapid response;

[0084] In step 3, the event generator creates a standardized event object containing complete information. This object not only records the data values ​​before and after the change, but also includes metadata such as the event source, timestamp, and device identifier.

[0085] Event objects are encapsulated in a uniform JSON format to ensure that subsequent processing modules can parse them accurately;

[0086] All events will be assigned a unique identifier to facilitate subsequent tracking and logging;

[0087] In step 4:

[0088] Branch 4a: UI Update: In the UI Update branch, the system first queries all UI components that have subscribed to the data item, then sends the event to the corresponding message queue, and finally triggers a partial refresh of the interface;

[0089] Branch 4b: Command Issuance: In the command issuance branch, the command service parses the event content, generates corresponding control commands according to the device type, and issues them to the hardware device through the corresponding communication interface;

[0090] Branch 4c: Message Publishing: In the message publishing branch, the system determines the message topic based on the event type, publishes the formatted message to the message bus, and records the distribution log for subsequent auditing.

[0091] In step 5, the log service records detailed operation history, monitors the system to update real-time status data, synchronizes data changes with external systems, and the alarm service checks whether threshold alarms have been triggered.

[0092] This decoupled design allows the system to flexibly expand to new subscribers without affecting core business processes.

[0093] In step 6, after the control command is sent to the power supply device, the change in the device's state will be detected again, thereby triggering a new round of event processing.

[0094] This closed-loop process enables the user interface to reflect the actual status of the device in real time, forming a complete control loop from operation to feedback.

[0095] In step 7, the system will automatically initiate a retry mechanism when the instruction fails to be issued;

[0096] In the event of a network outage, unsent events will be temporarily cached;

[0097] Once the system recovers, the automatic synchronization program will ensure the consistency of the state;

[0098] All abnormal situations will be recorded in detail, providing a basis for system maintenance and troubleshooting.

[0099] In summary, the embodiments of the present invention provide a human-computer interaction power control system and method based on an event-triggered mechanism.

[0100] To more clearly demonstrate the technical solution and its effects provided by the present invention, the following detailed description of the human-computer interaction power control system and method based on the event triggering mechanism provided by the present invention is given by specific embodiments.

[0101] Description of the invention principle:

[0102] The core of this invention lies in constructing an intelligent power control system and method based on a data configuration change event triggering and forwarding mechanism. The basic principle of this invention is to use data configuration changes in the power system as a unified event source. By establishing a standardized event listening, encapsulation, distribution, and processing flow, a high degree of synergy between human-machine interaction and power control is achieved. When any change occurs in key configuration data of the system (such as output voltage setpoints, operating modes, protection thresholds, etc.), regardless of whether the change originates from user interface operation, remote command, or internal system policy triggering, it will be instantly captured by the unified event listening mechanism and encapsulated into a structured event object containing complete information such as data identifier, old and new values, timestamp, and the source of the change.

[0103] This event object serves as a unified carrier for internal system communication, driving three concurrent key processing flows: First, it triggers the immediate refresh of the relevant human-machine interface, providing users with accurate visual feedback; simultaneously, it initiates the control command generation logic, converting changed parameters into executable control commands and sending them to the power hardware; furthermore, it publishes the change information to a specific topic on the message bus for consumption by internal modules or external systems subscribing to that topic. This mechanism fundamentally changes the working mode of traditional polling or tightly coupled architectures, driving system operation through data changes and forming a complete control loop of "interface operation → data change → event triggering → (interface refresh & control command issuance & message publication) → hardware response → status data change → event triggering → interface refresh," ensuring the system's efficiency, real-time performance, decoupling, and scalability at the architectural level.

[0104] Example 1

[0105] The modular architecture of this system is as follows: Figure 1 As shown, it mainly includes the following core modules:

[0106] As the foundation of the system, the data storage module is responsible for persisting or caching all power configuration parameters and real-time status data, providing a unified and reliable data source for the entire system, and ensuring data consistency and integrity.

[0107] The event monitoring module constitutes the system's perception layer. Employing techniques such as the observer pattern or a monitoring service, it continuously monitors changes to preset key data items in the data storage module. Once a data change is detected, the module immediately responds and generates standardized event objects, providing a basis for subsequent processing.

[0108] The event distribution module (containing a message bus) is the system's information hub and scheduling center. This module receives event objects from the listening module and intelligently distributes them according to predefined routing rules. Its integrated high-performance message bus supports a topic-based publish-subscribe model, enabling parallel routing of events to three processing channels: driving the human-machine interface module for precise partial display refresh; triggering the command control module to generate and issue hardware control commands; and encapsulating the event content into messages and publishing them to the corresponding topic on the bus, achieving broadcast distribution of information.

[0109] The human-computer interaction interface module consists of multiple independently operating intelligent UI components. These components use a subscription mechanism, registering the data change events or message topics they are interested in during initialization. Upon receiving an event notification, the component only updates its corresponding display area, achieving efficient and accurate local refresh, while also being responsible for converting user actions into data modification requests, thus becoming the source of new events.

[0110] The instruction control module, acting as the system's execution terminal, subscribes specifically to data change events that require driving hardware actions. This module has built-in instruction generation logic; upon receiving a relevant event, it automatically generates control instructions conforming to the hardware communication protocol based on the event content and sends them to the power supply device through the corresponding physical interface to complete the final control execution.

[0111] Furthermore, the system's open architecture via a message bus naturally supports external system access. Any external application or service can obtain real-time system status changes and control information simply by subscribing to relevant message topics, achieving seamless and decoupled integration with the external environment. All these modules are organically connected through standardized event and message flows, collectively forming a responsive, clearly defined, and easily expandable intelligent power control system.

[0112] The modules collaborate through clearly defined interface specifications, forming a complete event-driven processing chain. Upon system startup, each module initializes sequentially, establishing necessary connections and subscription relationships, and enters a standby state. When data changes, the system automatically triggers the corresponding event handling process, ensuring timely data updates and accurate command execution.

[0113] like Figure 2 As shown:

[0114] The specific embodiments of the present invention achieve an event-triggered power control system through the coordinated operation of the following modules:

[0115] Step 1: System Initialization

[0116] System operation begins with the initialization phase, where modules start in a predetermined order. The data storage module first loads device configurations and system parameters, establishes a data mirror in memory, and initializes database connections. The event listening module then starts the monitoring service, registers interceptors for data access, and lays the foundation for subsequent event capture. The message bus module initializes the switch and queues, establishes topic routing rules, and simultaneously, the business service modules complete their own state preparation, awaiting event processing. The entire initialization process ensures that all system components are in a ready state, providing a stable foundation for the subsequent event-driven mechanism.

[0117] Step 2: Data Change Monitoring

[0118] Once the system enters a stable operating phase, the event monitoring module continuously monitors changes from multiple data sources. The monitoring scope covers all possible sources of data change, including user interface operations, remote API calls, scheduled task triggers, and device status updates. The monitoring mechanism is implemented through a unified data access interface, ensuring that any modification to stored data is captured in real time. This comprehensive monitoring ensures the system can promptly detect any status changes, guaranteeing rapid response.

[0119] Step 3: Event Generation and Encapsulation

[0120] When a data change is detected, the system immediately enters the event generation and encapsulation phase. The event generator creates a standardized event object containing complete information. This object records not only the data values ​​before and after the change, but also metadata such as the event source, timestamp, and device identifier. The event object is encapsulated in a unified JSON format to ensure accurate parsing by subsequent processing modules. All events are assigned a unique identifier for easy tracking and logging.

[0121] Step 4: Event Dispatch Processing

[0122] The event dispatch and processing phase employs a multi-path parallel execution mechanism.

[0123] Branch 4a: UI Update: In the UI Update branch, the system first queries all UI components that have subscribed to the data item, then sends the event to the corresponding message queue, and finally triggers a partial refresh of the interface.

[0124] Branch 4b: Command Issuance: In the command issuance branch, the command service parses the event content, generates corresponding control commands based on the device type, and issues them to the hardware device through the corresponding communication interface.

[0125] Branch 4c: Message Publishing: In the message publishing branch, the system determines the message topic based on the event type, publishes the formatted message to the message bus, and records the distribution log for subsequent auditing.

[0126] Step 5: Subscriber Processing

[0127] The subscriber processing phase employs an asynchronous execution model. Internal and external subscription modules retrieve messages related to their respective topics from the message bus and then process them according to their own business logic. The log service records detailed operation history, monitors real-time status data updates, synchronizes data changes with external systems, and the alarm service checks whether threshold alarms have been triggered. This decoupled design allows the system to flexibly expand to include new subscribers without impacting core business processes.

[0128] Step 6: Closed-loop feedback

[0129] The system ensures state consistency through a closed-loop feedback mechanism. When a control command is issued to the power supply device, the device's state change is detected again, triggering a new round of event handling. This closed-loop process allows the user interface to reflect the actual state of the device in real time, forming a complete control loop from operation to feedback. This design not only improves system reliability but also provides users with intuitive operational feedback.

[0130] Step 7: Exception Handling

[0131] An exception handling mechanism is implemented throughout all stages of system operation. When a command fails to be issued, the system automatically initiates a retry mechanism; in the event of a network interruption, unsent events are temporarily cached; and upon system recovery, an automatic synchronization program ensures state consistency. All exceptions are logged in detail, providing a basis for system maintenance and troubleshooting. Through robust exception handling, the system maintains stable operation, ensuring the normal functioning of core features even when some components fail.

[0132] The entire system achieves event-triggered intelligent power control through the cyclical execution of the above seven steps. This design ensures high real-time performance, high reliability, and good scalability, meeting the stringent requirements of modern industrial environments for power control systems. Through this detailed workflow, the system achieves complete closed-loop control from user operation to equipment response and status feedback, ensuring the accuracy of power control and the reliability of system operation.

[0133] Key innovations and beneficial effects of this invention:

[0134] Innovation Point 1: Using data configuration changes as a unified event source. All behaviors in the system that may lead to state changes (user operations, remote commands, policy triggers) are uniformly abstracted into "data change events," serving as the core driving force for the entire system's operation.

[0135] Innovation Point 2: Multi-target concurrent event response mechanism. A single data change event can simultaneously and automatically trigger multiple actions such as interface updates, control command issuance, and message publishing, achieving efficient and consistent response.

[0136] Innovation Point 3: Topic-based message subscription / publishing architecture. A message bus enables completely decoupled communication within the system and between internal and external systems, greatly enhancing the system's modularity and scalability.

[0137] Beneficial effects:

[0138] High real-time performance and low latency: Eliminates polling overhead, enabling millisecond-level event response and control.

[0139] Resource efficiency: Processing and communication only occur when data actually changes, saving system resources.

[0140] Strong decoupling and high maintainability: Each module has a clear responsibility and interacts through events / messages, making it easy to develop, test, and maintain independently.

[0141] Excellent scalability: New features can be integrated into the system simply by subscribing to relevant message topics, without modifying the core logic.

[0142] Excellent user experience: fast operation response, intuitive status feedback, forming a smooth control loop.

[0143] Improved system reliability: A precise command triggering mechanism reduces control risks caused by delays or omissions.

[0144] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims. The information disclosed in the background section is intended only to enhance the understanding of the overall background technology of the present invention and should not be construed as an admission or implication in any way that such information constitutes prior art known to those skilled in the art.

Claims

1. A human-computer interaction power control system based on an event-triggered mechanism, characterized in that, This includes a data storage module, an event listening module, and an event dispatch module connected in sequence; The event distribution module is connected to the human-machine interface module and the command control module, and is equipped with an external system interface; The data storage module serves as the foundation of the system and is responsible for persisting or caching all power configuration parameters and real-time status data. The event monitoring module constitutes the system's perception layer and uses technologies such as the observer pattern or monitoring services to continuously monitor changes in preset key data items in the data storage module. The event distribution module contains a message bus, which is the information hub and scheduling center of the system. This module receives event objects from the listening module and intelligently distributes them according to predefined routing rules. The human-computer interaction interface module consists of multiple independently operable intelligent UI components. These components adopt a subscription mechanism and register the data change events or message topics they are interested in during initialization. The instruction control module, as the system's execution terminal, is specifically designed to subscribe to data change events that require driving hardware actions.

2. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, The data storage module provides a unified and reliable data source for the entire system, ensuring data consistency and integrity.

3. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, Once the event listening module detects a data change, it will immediately respond and generate a standardized event object, providing a basis for subsequent processing.

4. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, The high-performance message bus integrated within the event distribution module supports a topic-based publish-subscribe pattern and can route events in parallel to the following three processing channels: Drive the human-computer interaction interface module to perform precise local display refresh; The trigger instruction control module generates and issues hardware control instructions; The event content is encapsulated as a message and published to the corresponding topic on the bus to achieve broadcast distribution of information.

5. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, After receiving an event notification, the human-computer interaction interface module only updates its corresponding display area to achieve efficient and accurate local refresh. At the same time, it is responsible for converting user operations into data modification requests, which become the source of new events.

6. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, The instruction control module has built-in instruction generation logic. When it receives a relevant event, it can automatically generate control instructions that conform to the hardware communication protocol based on the event content, and send them to the power supply device through the corresponding physical interface to complete the final control execution.

7. The human-computer interaction power control system based on an event-triggered mechanism according to claim 1, characterized in that, The system supports external system access through an open architecture of an external system interface message bus. Any external application or service can obtain system status changes and control information in real time simply by subscribing to the relevant message topics, thus achieving seamless and decoupled integration with the external environment. The various modules of the system are organically connected through standardized event flow and message flow, together forming a smart power control architecture that is responsive, has clear responsibilities, and is easy to expand. The modules collaborate through defined interface specifications to form a complete event-driven processing chain. When the system starts, each module initializes in sequence, establishes necessary connections and subscription relationships, and enters a standby state. When data changes, the system automatically triggers the corresponding event processing flow to ensure timely data updates and accurate execution of instructions.

8. A method for implementing human-machine interactive power control using the system according to any one of claims 1 to 7, characterized in that, Including the following steps: Step 1: System Initialization: The system begins operation during the initialization phase, with each module starting in a predetermined order. Step 2: Data Change Monitoring After the system enters a stable operating phase, the event monitoring module begins to continuously monitor changes in multiple data sources; Step 3: Event Generation and Encapsulation: When a change in data is detected, the system immediately enters the event generation and encapsulation phase; Step 4: Event dispatching and processing: The event dispatch and processing phase employs a multi-path parallel execution mechanism; Step 5: Subscriber Processing: The subscriber processing phase adopts an asynchronous execution mode. After obtaining messages on relevant topics from the message bus, the various internal and external subscription modules process them according to their own business logic. Step 6: Closed-loop feedback: The system ensures state consistency through a closed-loop feedback mechanism; Step 7: Exception Handling An exception handling mechanism is implemented in every stage of system operation; The entire system achieves event-triggered intelligent power control through the cyclical execution of the above seven steps, realizing a complete closed-loop control from user operation to device response and status feedback.

9. The method according to claim 8, characterized in that: In step 1, the data storage module first loads the device configuration and system parameters, establishes a data image in memory, and initializes the database connection; The event listening module then starts the monitoring service and registers interceptors for data access, laying the foundation for subsequent event capture. The message bus module initializes the switch and queue, establishes topic routing rules, and at the same time, the business service module completes its own state preparation and waits to process events. The entire initialization process ensures that all system components are in a ready state, providing a stable foundation for subsequent event-driven mechanisms; In step 2, the monitoring scope covers all possible ways that may cause data changes, such as user interface operations, remote API calls, scheduled task triggers, and device status updates. The monitoring mechanism is implemented through a unified data access interface, and any modification operation to the stored data will be captured in real time; This comprehensive monitoring ensures that the system can detect any changes in status in a timely manner, providing a guarantee for rapid response; In step 3, the event generator creates a standardized event object containing complete information. This object not only records the data values ​​before and after the change, but also includes metadata such as the event source, timestamp, and device identifier. Event objects are encapsulated in a uniform JSON format to ensure that subsequent processing modules can parse them accurately; All events will be assigned a unique identifier to facilitate subsequent tracking and logging; In step 4: Branch 4a: UI Update: In the UI Update branch, the system first queries all UI components that have subscribed to the data item, then sends the event to the corresponding message queue, and finally triggers a partial refresh of the interface; Branch 4b: Command Issuance: In the command issuance branch, the command service parses the event content, generates corresponding control commands according to the device type, and issues them to the hardware device through the corresponding communication interface; Branch 4c: Message Publishing: In the message publishing branch, the system determines the message topic based on the event type, publishes the formatted message to the message bus, and records the distribution log for subsequent auditing. In step 5, the log service records detailed operation history, monitors the system to update real-time status data, synchronizes data changes with external systems, and the alarm service checks whether threshold alarms have been triggered. This decoupled design allows the system to flexibly expand to new subscribers without affecting core business processes. In step 6, after the control command is sent to the power supply device, the change in the device's state will be detected again, thereby triggering a new round of event processing. This closed-loop process enables the user interface to reflect the actual status of the device in real time, forming a complete control loop from operation to feedback. In step 7, the system will automatically initiate a retry mechanism when the instruction fails to be issued; In the event of a network outage, unsent events will be temporarily cached; Once the system recovers, the automatic synchronization program will ensure the consistency of the state; All abnormal situations will be recorded in detail, providing a basis for system maintenance and troubleshooting.

Images