A station equipment control method and system

Abstract

The application discloses a kind of station equipment control method and system, belong to urban rail transit technical field, comprising: S1: according to station historical operation demand to obtain process control node and historical control strategy, node metadata corresponding to process control node is constructed in database;Wherein, process control node includes event node, condition node and action node;S2: strategy table including process control node field and process control node associated field is constructed in database, and strategy table is filled according to node metadata and historical control strategy;S3: comparing station real-time operation demand with strategy table, if comparison is successful, then strategy table is parsed to obtain execution instruction, and station equipment is controlled according to execution instruction, if comparison fails, then strategy table is updated by station real-time operation demand, and S3 is re-executed.It solves the technical problems that the prior art is difficult to improve the flexibility and response efficiency of station equipment control.

Description

Technical Field

[0001] This invention relates to the field of urban rail transit technology, specifically to a station equipment control method and system. Background Technology

[0002] In modern urban rail transit systems, subway stations typically deploy a large number of heterogeneous devices, including but not limited to automatic fare collection systems, environmental and equipment monitoring systems, automatic fire alarm systems, power monitoring systems, passenger information systems, video surveillance systems, and various electromechanical equipment such as lighting, ventilation, and access control. The stable and coordinated operation of these devices is crucial for ensuring the safe and efficient operation of the subway. Currently, the control of these devices mainly relies on the following methods: Manual / semi-automatic control of independent subsystems: Station equipment is divided into multiple independent automated subsystems (such as BAS, FAS, etc.), each with its own dedicated control logic and human-machine interface. Operators need to monitor and operate on their respective consoles. When cross-system linkage is required, operators often need to manually execute a series of complex operating instructions according to emergency plans, or rely on fixed, hard-coded linkage logic pre-configured during the system integration phase. Automation based on fixed scripts: Some systems achieve automated responses in specific scenarios by writing fixed control scripts or programs. However, these scripts are usually static, one-off, and lack flexibility. Once the business logic needs to be adjusted (such as changing temperature thresholds or adding linked equipment), professional developers must modify the code and redeploy it. Therefore, how to improve the control flexibility and response efficiency of station equipment is a technical challenge that needs to be solved by existing technologies. Summary of the Invention

[0003] To address the technical problem that existing technologies struggle to improve the flexibility and response efficiency of station equipment control, this invention provides a station equipment control method and system. It acquires process control nodes and historical control strategies based on historical station operational needs, constructs node metadata corresponding to the process control nodes in a database, decoupling the perception of equipment status and the control of equipment actions. Furthermore, it constructs a strategy table in the database, including process control node fields and associated fields, and by reserving fields, supports the subsequent addition of control strategies based on new requirements. This provides structured data support for visual configuration, avoiding direct code modification and solving the technical problem of existing technologies failing to improve the flexibility and response efficiency of station equipment control.

[0004] To solve the above-mentioned technical problems, the present invention provides a station equipment control method, comprising the following steps: S1: Obtain process control nodes and historical control strategies based on the station's historical operational needs, and construct node metadata corresponding to the process control nodes in the database; among them, process control nodes include event nodes, condition nodes, and action nodes; S2: Construct a strategy table in the database that includes process control node fields and process control node association fields, and populate the strategy table according to node metadata and historical control strategies; S3: Compare the station's real-time operational needs with the strategy table. If the comparison is successful, parse the strategy table to obtain the execution instructions and control the station equipment according to the execution instructions. If the comparison fails, update the strategy table based on the station's real-time operational needs and re-execute S3.

[0005] Preferably, in S1, the node metadata corresponding to the event node includes event ID, event name, event trigger source, and trigger parameters; the node metadata corresponding to the condition node includes condition ID, condition name, judgment rule, and associated branch; and the node metadata corresponding to the action node includes action ID, action name, execution subject, and execution parameters.

[0006] Preferably, in S2, the step of populating the policy table based on node metadata and historical control policies includes: By filtering event nodes, condition nodes, and action nodes using historical control strategies, the first target event node, first target condition node, and first target action node are obtained. The unique identifier of the node metadata corresponding to the first target event node, first target condition node, and first target action node is then filled into the process control node field. Map the dependencies between the first target event node, the first target condition node, and the first target action node to the first structured data, and populate the first structured data into the associated fields of the process control node.

[0007] Preferably, in step S3, the real-time operational needs of the station are compared with the strategy table. If the comparison is successful, the strategy table is parsed to obtain execution instructions, including... Based on the station's real-time operational needs, obtain real-time control strategies, compare the real-time control strategies with the strategy table, and if the comparison is successful, parse the columns in the strategy table that match the real-time control strategies to obtain execution instructions.

[0008] Preferably, before obtaining the real-time control strategy based on the station's real-time operational needs, the method further includes: The system acquires real-time operating data of station equipment and determines whether the real-time operating data meets the triggering conditions obtained based on the station's safe operation requirements. Only when the conditions are met can the real-time control strategy be obtained based on the station's real-time operation requirements. The triggering conditions include at least time-based triggering conditions and data threshold triggering conditions.

[0009] Preferably, in S3, updating the strategy table based on the real-time operational needs of the station includes: Based on the real-time operational needs of the station, the event nodes, condition nodes, and action nodes are filtered to obtain the second target event node, the second target condition node, and the second target action node. The unique identifier of the node metadata corresponding to the second target event node, the second target condition node, and the second target action node is filled into the process control node field. Map the dependencies between the second target event node, the second target condition node, and the second target action node to second structured data, and populate the associated fields of the process control node with the second structured data.

[0010] By adopting the above technical solution, the present invention has the following advantages: Based on the station's historical operational needs, process control nodes and historical control strategies are obtained. Node metadata corresponding to the process control nodes is constructed in the database, decoupling the sensing of equipment status and the control of equipment actions. A strategy table, including process control node fields and associated fields, is built in the database. By reserving fields, it supports the subsequent addition of control strategies based on new requirements, providing structured data support for visual configuration. Operators can directly obtain control strategies by dragging and dropping process control nodes and establishing connections between them, thus avoiding direct code modification. This solves the technical problem that existing technologies struggle to improve the flexibility and response efficiency of station equipment control. By acquiring real-time operating data of station equipment, it can be determined whether the real-time operating data meets the triggering conditions obtained based on the station's safe operation requirements. Once the triggering conditions are met, the real-time control strategy is automatically obtained based on the station's real-time operation requirements, which significantly improves the automation level and reliability of emergency response.

[0011] The present invention also provides a station equipment control system, applicable to the aforementioned station equipment control method, comprising: The node metadata construction module is used to obtain process control nodes and historical control strategies based on the station's historical operational needs, and to build the node metadata corresponding to the process control nodes in the database. The strategy table acquisition module is used to build a strategy table in the database, which includes process control node fields and process control node association fields, and populate the strategy table according to node metadata and historical control strategies. The control module compares the station's real-time operational needs with the strategy table. When the comparison is successful, it parses the strategy table to obtain execution instructions and controls the station equipment according to the execution instructions. When the comparison fails, the update module updates the strategy table with the station's real-time operational needs and restarts the control module.

[0012] Preferred options also include: The data acquisition module is used to collect real-time operating data of station equipment; The display module is used to view the execution information of the executed instructions.

[0013] By adopting the above technical solution, the present invention has the following advantages: Based on the station's historical operational needs, process control nodes and historical control strategies are obtained. Node metadata corresponding to the process control nodes is constructed in the database, decoupling the sensing of equipment status and the control of equipment actions. A strategy table, including process control node fields and associated fields, is built in the database. By reserving fields, it supports the subsequent addition of control strategies based on new requirements, providing structured data support for visual configuration. Operators can directly obtain control strategies by dragging and dropping process control nodes and establishing connections between them, thus avoiding direct code modification. This solves the technical problem that existing technologies struggle to improve the flexibility and response efficiency of station equipment control.

[0014] The present invention also provides a computer device, including: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the steps of the station equipment control method described above.

[0015] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the station equipment control method described above. Attached Figure Description

[0016] Other features, objects, and advantages of the invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings. The drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings.

[0017] Figure 1 This is a flowchart illustrating a station equipment control method according to the present invention; Figure 2 This is a configuration flowchart of the strategy engine system of the present invention; Figure 3 This is a flowchart of the operation of the strategy engine system of the present invention. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only one preferred embodiment of this invention and are only used to explain this invention. They do not limit the scope of protection of this invention. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0019] Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the operations (or steps) as sequential processes, many of the operations (or steps) can be performed in parallel, concurrently, or simultaneously. Furthermore, the order of the operations can be rearranged. The process can be terminated when its operation is completed, but it may also have additional steps not included in the figures; the process may correspond to a method, function, procedure, subroutine, subroutine, etc.

[0020] Example 1: like Figure 1 As shown, a station equipment control method includes the following steps: S1: Obtain process control nodes and historical control strategies based on the station's historical operational needs, and construct node metadata corresponding to the process control nodes in the database; among them, process control nodes include event nodes, condition nodes, and action nodes.

[0021] Specifically, in S1, the node metadata corresponding to the event node includes the event ID, event name, event trigger source, and trigger parameters; the node metadata corresponding to the condition node includes the condition ID, condition name, judgment rule, and associated branch; and the node metadata corresponding to the action node includes the action ID, action name, execution subject, and execution parameters.

[0022] Event triggering sources include equipment, such as turnstiles or ticket vending machines detecting malfunctions; personnel, such as staff manually reporting platform congestion; time, such as the system automatically detecting "8:00 AM peak hour," with triggering parameters referring to the specific data sent by the event, including fault codes, such as turnstiles reporting "E102 ticket malfunction"; timestamps, such as "2023-10-01 08:00:00" triggering the morning peak event, with judgment rules including: "Platform camera detected more than 800 people" and "Turntile malfunction duration > 5 minutes," etc. Related branches include: if "more than 800 people" is met, then "add shifts" will be executed; if not, then "maintain normal shifts," etc. The executing entity includes automatic system execution, such as the control center system directly operating the turnstiles; manual operation, such as notifying staff to handle the situation on-site, with execution parameters including the notification recipient, such as "Maintenance team employee Zhang San"; and operation instructions, such as "Open all turnstile channels 1-6."

[0023] In the traditional model, a hard-coded association exists where a device A malfunction directly controls the action of device B (e.g., gate 1 malfunctions, immediately opening gate 2). This means the perceived state and the executed action are directly bound, and modifying either device requires simultaneous adjustments to the associated logic. In this embodiment, the direct association between perception and execution is severed through the abstraction of node metadata. Event nodes only describe the perceived state, without involving any execution action; action nodes only describe the operation to be performed, independent of the specific perceived state. The two are dynamically mapped through the association fields of a subsequent policy table, rather than being fixedly bound. This separation allows for changes to the sensing device; only the trigger source metadata of the event node needs updating, without modifying the action node. Similarly, when adding an execution device, only the execution subject metadata of the action node needs to be supplemented, without adjusting the event node. Through the abstraction and modular design of node metadata, the perception device state and the control device action are dynamically associated through a policy table instead of being directly bound. When a sensing device or execution device changes (e.g., adding, replacing, or upgrading), only the metadata of the corresponding node or the association relationship in the policy table needs adjustment, without reconstructing the entire control logic, significantly improving flexibility and scalability.

[0024] S2: Construct a strategy table in the database that includes process control node fields and associated fields of process control nodes, and populate the strategy table according to node metadata and historical control strategies.

[0025] In some embodiments, S2, the step of populating the policy table based on node metadata and historical control policies includes: By filtering event nodes, condition nodes, and action nodes using historical control strategies, the first target event node, first target condition node, and first target action node are obtained. The unique identifier of the node metadata corresponding to the first target event node, first target condition node, and first target action node is then filled into the process control node field. Map the dependencies between the first target event node, the first target condition node, and the first target action node to the first structured data, and populate the first structured data into the associated fields of the process control node.

[0026] In this embodiment, if the historical control strategy is "if the number of people on the platform exceeds 800 during the morning rush hour, open all turnstile channels and increase train frequency; if the number of people on the platform does not exceed 800, only open 60% of the turnstile channels", the event nodes include E001 (event name = arrival during the morning rush hour, trigger source = time, trigger parameter = 07:30-09:00) and E002 (event name = abnormal station environment, trigger source = equipment, trigger parameter = current temperature 32 degrees Celsius), and the condition nodes include C001 (condition name = number of people on the platform > 800, judgment rule = camera count > 800), C002 (condition name = number of people on the platform ≤ 800, judgment rule = camera count ≤ 800), and C003 (condition name = emergency permission verification, judgment rule = operator permission level > level 5), and the action... The nodes include A001 (Action Name = Fully open turnstiles + Add trains, Execution Subject = Automatic system, Execution Parameters = Turnstiles 1-10 fully open; train interval shortened to 2 minutes), A002 (Action Name = Open 60% of turnstiles, Execution Subject = Automatic system, Execution Parameters = Turnstiles 1-6 open), and A003 (Action Name = Emergency equipment linkage control, Execution Subject = System + Manual, Execution Parameters = Emergency lighting turned on, non-evacuation passage turnstiles closed, smoke exhaust fan started). At this time, the first target event node selected is E001, the first target condition nodes are C001 and C002, and the first target action nodes are A001 and A002. The dependency relationship is that after E001 occurs, C001 is triggered first. If C001 is true, then A001 is executed. If C001 is false (i.e., C002 is true), then A002 is executed. The first structured data can be {"trigger_chain": "E001→C001→(A001, A002)", "branch_rule": "C001 satisfies → A001; C001 does not satisfy → A002", "priority": "high"}. The strategy table stores the specific node identifiers of the event-condition-action and records the logical dependencies between nodes through structured data, such as trigger order and branch rules. In this embodiment, by reserving the process control node field and the process control node association field, it supports the subsequent addition of control strategies according to new requirements, and provides structured data support for visual configuration. Operators can directly obtain control strategies by dragging and dropping process control nodes and establishing connections between process control nodes, thereby avoiding direct modification of the code and solving the technical problem that existing technologies cannot improve the control flexibility and response efficiency of station equipment.

[0027] S3: Compare the station's real-time operational needs with the strategy table. If the comparison is successful, parse the strategy table to obtain the execution instructions and control the station equipment according to the execution instructions. If the comparison fails, update the strategy table based on the station's real-time operational needs and re-execute S3.

[0028] In step S3, the real-time operational needs of the station are compared with the strategy table. If the comparison is successful, the strategy table is parsed to obtain execution instructions, including... Based on the station's real-time operational needs, a real-time control strategy is obtained. This strategy is then compared with a strategy table. If the comparison is successful, the columns in the strategy table that match the real-time control strategy are parsed to obtain the execution instructions. Specifically, comparing the real-time control strategy with the strategy table involves converting the event nodes, condition nodes, and action nodes in the real-time control strategy into corresponding node metadata and matching them with the strategy table. If the node metadata corresponding to the event nodes, condition nodes, and action nodes in the real-time control strategy all match successfully, the comparison is considered successful.

[0029] In some embodiments, before obtaining the real-time control strategy based on the station's real-time operational needs, the method further includes: The system acquires real-time operating data of station equipment and determines whether the real-time operating data meets the triggering conditions obtained based on the station's safe operation requirements. Only when the conditions are met can the real-time control strategy be obtained based on the station's real-time operation requirements. The triggering conditions include at least time-based triggering conditions and data threshold triggering conditions.

[0030] In S3, updating the strategy table based on real-time station operational needs includes: Based on the real-time operational needs of the station, the event nodes, condition nodes, and action nodes are filtered to obtain the second target event node, the second target condition node, and the second target action node. The unique identifier of the node metadata corresponding to the second target event node, the second target condition node, and the second target action node is filled into the process control node field. Map the dependencies between the second target event node, the second target condition node, and the second target action node to second structured data, and populate the associated fields of the process control node with the second structured data.

[0031] In this embodiment, when the control strategy in the strategy table does not meet the real-time operation requirements of the station, the operator can directly update the strategy table by dragging and dropping process control nodes and establishing connections between them, thereby avoiding direct modification of the code and further improving the flexibility of control.

[0032] Example 2: This embodiment also provides a station equipment control system, applicable to the aforementioned station equipment control method, including: The node metadata construction module is used to obtain process control nodes and historical control strategies based on the station's historical operational needs, and to build the node metadata corresponding to the process control nodes in the database. The strategy table acquisition module is used to build a strategy table in the database, which includes process control node fields and process control node association fields, and populate the strategy table according to node metadata and historical control strategies. The control module compares the station's real-time operational needs with the strategy table. When the comparison is successful, it parses the strategy table to obtain execution instructions and controls the station equipment according to the execution instructions. When the comparison fails, the update module updates the strategy table with the station's real-time operational needs and restarts the control module.

[0033] Also includes: The data acquisition module is used to collect real-time operating data of station equipment; The display module is used to view the execution information of the executed instructions.

[0034] In this embodiment, the station equipment control system is specifically a strategy engine system, such as... Figure 2 As shown, the configuration process of the strategy engine system is as follows: Station equipment data is obtained from the data configuration system. The central operator logs into the central strategy engine system and drags and drops event nodes, condition nodes, and action nodes from the database to the work area, constructing control strategies through connections. The central operator sets trigger conditions for the configured control strategies and saves them. The central strategy engine system stores the compiled control strategy data in its own database, thus obtaining a strategy table. Users select and issue control strategies in the central strategy engine system. The edge strategy engine in the strategy engine system receives the control strategy data and saves it in its own database. The central strategy engine system supports three execution methods: manual, automatic time-triggered, and automatic event-triggered. The manual execution process of the strategy engine system is as follows: Figure 3As shown, station operators select control strategies and issue execution commands; the edge strategy engine collects device status from the IoT system or issues device control commands based on the strategy configuration information; the edge strategy engine saves the execution data of each node (including execution time, execution results, etc.) to its own database and pushes the execution data information to the central strategy engine and business applications; central and station operators can view the strategy execution information through the central strategy engine interface and the business application interface, respectively. The automatic time-triggered execution / automatic steps of the central strategy engine system are as follows: Step 1: The edge strategy engine system continuously monitors the device status or time. When the device status meets the preset trigger state / reaches the preset trigger time, Step 2 is executed; otherwise, monitoring of the device status or time continues. Step 2: Search for a matching control strategy. If a control strategy is found, the system begins to execute the preset control strategy process, i.e., Step 3. If no control strategy is found, Step 4 is executed. Step 3: The edge strategy engine collects device status from the IoT system or issues device control commands based on the strategy configuration information. Step 4: The edge strategy engine saves the execution data of each node (including execution time, execution results, etc.) to its own database and pushes the execution data information to the central strategy engine and business applications. Central and station operators can view the strategy execution information through the central strategy engine interface and the business application interface, respectively.

[0035] In this embodiment, the operator obtains control strategies by dragging and dropping process control nodes on the display module and establishing connections between them. The central strategy engine system solves the problems of fixed linkage logic and complex configuration by providing a graphical drag-and-drop orchestration interface. The central strategy engine system uniformly configures and manages strategy data and can distribute the designed control strategies to the corresponding edge strategy engines. The edge strategy engine systems can execute control strategies as long as the corresponding conditions are met, meeting the needs of operation and management personnel for real-time configuration and immediate effectiveness, effectively reducing the complexity of configuration and maintenance. The central strategy engine system automatically obtains device data from the data configuration system through the data acquisition module. Users only need to register new device data or actions as standard nodes of the system to access the strategy engine orchestration, overcoming the problem of insufficient scalability in the existing design. When a specific device status (such as a fire alarm) is detected, each edge strategy engine system can automatically and accurately trigger the preset multi-device collaborative control process, reducing human intervention and delays, and overcoming the problem of low emergency response efficiency. The central strategy engine system provides a unified configuration interface and monitoring interface, supporting visualized operations for the creation, activation, deactivation, monitoring, and log auditing of all strategies, improving the transparency and controllability of operation and maintenance.

[0036] Example 3: This embodiment also provides a computer device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the steps of the station equipment control method described above.

[0037] Example 4: This embodiment also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the station equipment control method described above.

[0038] The specific embodiments described above are preferred embodiments of a station equipment control method and system of the present invention, and are not intended to limit the specific scope of the present invention. The scope of the present invention includes, but is not limited to, these specific embodiments. All equivalent changes made in accordance with the shape and structure of the present invention are within the protection scope of the present invention.

Claims

1. A method for controlling station equipment, characterized in that, Includes the following steps: S1: Obtain process control nodes and historical control strategies based on the station's historical operational needs, and construct node metadata corresponding to the process control nodes in the database; among them, process control nodes include event nodes, condition nodes, and action nodes; S2: Construct a strategy table in the database that includes process control node fields and process control node association fields, and populate the strategy table according to node metadata and historical control strategies; S3: Compare the station's real-time operational needs with the strategy table. If the comparison is successful, parse the strategy table to obtain the execution instructions and control the station equipment according to the execution instructions. If the comparison fails, update the strategy table based on the station's real-time operational needs and re-execute S3. In S2, the step of populating the policy table based on node metadata and historical control policies includes: By filtering event nodes, condition nodes, and action nodes using historical control strategies, the first target event node, first target condition node, and first target action node are obtained. The unique identifier of the node metadata corresponding to the first target event node, first target condition node, and first target action node is then filled into the process control node field. Map the dependency relationships between the first target event node, the first target condition node, and the first target action node to the first structured data, and populate the first structured data into the associated fields of the process control node; In S3, updating the strategy table based on real-time station operational needs includes: Based on the real-time operational needs of the station, the event nodes, condition nodes, and action nodes are filtered to obtain the second target event node, the second target condition node, and the second target action node. The unique identifier of the node metadata corresponding to the second target event node, the second target condition node, and the second target action node is filled into the process control node field. Map the dependencies between the second target event node, the second target condition node, and the second target action node to second structured data, and populate the associated fields of the process control node with the second structured data.

2. The station equipment control method according to claim 1, characterized in that, In S1, the node metadata corresponding to the event node includes the event ID, event name, event trigger source, and trigger parameters; The node metadata corresponding to the condition node includes the condition ID, condition name, judgment rule, and associated branch; The node metadata corresponding to the action node includes the action ID, action name, execution subject, and execution parameters.

3. The station equipment control method according to claim 1, characterized in that, In step S3, the real-time operational needs of the station are compared with the strategy table. If the comparison is successful, the strategy table is parsed to obtain execution instructions, including... Based on the station's real-time operational needs, obtain real-time control strategies, compare the real-time control strategies with the strategy table, and if the comparison is successful, parse the columns in the strategy table that match the real-time control strategies to obtain execution instructions.

4. The station equipment control method according to claim 3, characterized in that, Before obtaining the real-time control strategy based on the station's real-time operational needs, the following steps are also included: The system acquires real-time operating data of station equipment and determines whether the real-time operating data meets the triggering conditions obtained based on the station's safe operation requirements. Only when the conditions are met can the real-time control strategy be obtained based on the station's real-time operation requirements. The triggering conditions include at least time-based triggering conditions and data threshold triggering conditions.

5. A station equipment control system, applicable to the station equipment control method according to any one of claims 1-4, characterized in that, include: The node metadata construction module is used to obtain process control nodes and historical control strategies based on the station's historical operational needs, and to build the node metadata corresponding to the process control nodes in the database. The strategy table acquisition module is used to build a strategy table in the database, which includes process control node fields and process control node association fields, and populate the strategy table according to node metadata and historical control strategies. The control module compares the station's real-time operational needs with the strategy table. When the comparison is successful, it parses the strategy table to obtain execution instructions and controls the station equipment according to the execution instructions. When the comparison fails, the update module updates the strategy table with the station's real-time operational needs and restarts the control module.

6. A station equipment control system according to claim 5, characterized in that, Also includes: The data acquisition module is used to collect real-time operating data of station equipment; The display module is used to view the execution information of the executed instructions.

7. A computer device, characterized in that: include: The computer device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor communicates with the memory via the bus, and the processor executes the machine-readable instructions to perform the steps of a station equipment control method as described in any one of claims 1-4.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, performs the steps of a station equipment control method as described in any one of claims 1-4.

Images