Smart station scene processing method and system
Through the smart station scenario processing method and system, the data acquisition, processing and engine modules are used to dynamically access model data, and the problems of low efficiency and difficulty in business expansion of rail transit operation systems in complex scenario processing are solved, and automated management and Business modularity improves execution efficiency and system flexibility.
Patent Information
- Application Number
- CN202411250341.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-06
- Publication Date
- 2024-12-06
AI Technical Summary
The existing rail transit operation system is inefficient when dealing with complex scenarios. It relies on manual experience to achieve automated driving and equipment control, it is difficult to dynamically load business modules, and it is unable to meet the needs of scenario expansion.
Using smart station scenario processing methods and systems, through data acquisition module, data processing module, scene engine module and visual interface module, device status modeling, real-time data processing, alarm processing and command processing are realized, model data is dynamically connected, and group is provided. Statistical configuration and operational display, supporting automated management and business modularity and hot plugging.
It improves the execution efficiency of rail transit scenarios, realizes automated management, supports business expansion, meets the needs of complex scenarios, and improves the flexibility and scalability of the system.
Smart Images

Figure CN119088376A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of smart stations, and in particular to a smart station scene processing method and system. Background Art
[0002] According to the actual situation of the existing rail transit industry, its daily operations are generally carried out according to scenarios. At present, the process manual is used for the on-site execution of rail transit scenarios. During the entire execution process, multiple people need to cooperate with each other, and the control of equipment and the processing of processes need to be manually confirmed. There are huge communication costs and low execution efficiency. Faced with complex processes, scenario execution relies entirely on manual experience, which has high requirements for personnel. The execution process relies on manual execution records, data is scattered, and scenario execution data cannot be managed uniformly.
[0003] The existing rail transit operation solutions mainly use linkage and electronic plans. The linkage method mainly solves the problem of equipment control. When an event occurs, one or several linkage control actions are triggered, but it cannot be further linked according to the results of the action execution, and cannot handle complex and deeper business logic. Electronic plans focus on documented business process presentation, focus on business specifications and prompts, rely on manual labor, and cannot drive the flow of business by themselves. Neither solution can solve the needs of rail transit scenarios for both standardized business execution and automated drive and equipment control.
[0004] At the same time, with the expansion of rail transit operation scenarios, new businesses are constantly being proposed. The implementation of the business may be provided by the system itself, or it may rely on third-party implementation. Traditional linkage or electronic plans cannot dynamically load business during operation, or cannot load third-party business modules. Therefore, it cannot meet the business needs of the ever-expanding scenarios.
[0005] Therefore, how to combine control and business and dynamically transfer business, how to intelligently drive the execution of scenarios, how to quickly and dynamically load and execute business, and how to expand the business scope of scenarios have become the development trend of the industry. However, the existing process processing systems usually adopt fixed process designs, which are difficult to cope with different scenario requirements and business changes. Summary of the invention
[0006] The purpose of the present invention is to provide a smart station scene processing method and system, aiming to solve the problem that the existing process processing system usually adopts a fixed process design and is difficult to cope with different scene requirements and business changes.
[0007] To achieve the above object, the present invention provides a smart station scene processing method, comprising the following steps:
[0008] Collect the status of the equipment, model the equipment, and provide real-time data processing, alarm processing, and command processing. The generated model data can be used to drive the process of the scene;
[0009] Model the collected equipment status, third-party alarms, and energy consumption data, generate trigger information based on the modeled data, and send it to the scenario service to trigger specific business scenarios;
[0010] Provides scene configuration and operation status, and can dynamically access model data;
[0011] It provides configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understands the current scene execution status through a visual interface.
[0012] Among them, in the configuration and operation state of the provided scene, the model data can be dynamically accessed:
[0013] A scene has a start node and an end node. The scene execution starts from the start node. Each scene is a directed acyclic graph. The lines between nodes represent the relationship between two nodes. Each node has a predefined output relationship. During execution, the scene engine will determine the next flow node based on the node output relationship. When configuring the scene, the lines between nodes must be configured. Configuration errors will cause the scene to fail to end normally.
[0014] Among them, in the configuration and operation state of the provided scene, the model data can be dynamically accessed:
[0015] Identify the initial node of the scenario execution;
[0016] Marks the end of the scene;
[0017] Execute a group of actions in parallel. The business nodes in the group are executed in parallel. The status of the parallel group is determined according to the status of each node.
[0018] Count the number of business nodes that pass through this node. If it is equal to the specified number, the output is successful and the next node corresponding to the successful execution is executed.
[0019] Among them, in the configuration and operation state of the provided scene, the model data can be dynamically accessed:
[0020] The node provides an output relationship for configuration during scene configuration. The engine framework provides interface methods. When adding a new node, you only need to implement the corresponding interface to introduce it into the framework for execution.
[0021] Among them, it provides configuration configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understands the current scene execution status through a visual interface:
[0022] Directly click on the scene in the visual execution interface to trigger the scene or trigger the scene through the trigger management module. After the scene is triggered, the trigger source information of the scene trigger is saved. Subsequent nodes can obtain the trigger information of the scene from the scene trigger parameters.
[0023] Among them, it provides configuration configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understands the current scene execution status through a visual interface:
[0024] Scene list display, the scene engine provides a restful interface to query the scene execution list and scene execution status;
[0025] The scene visualization interface uses flowchart display and list display, establishes a long connection with the backend through websocket, and pushes the node status to the frontend after the scene is executed.
[0026] A smart station scene processing system comprises a data acquisition module, a data processing module, a scene engine module and an interface visualization module, wherein the data processing module is connected to the data acquisition module, the scene engine module is connected to the data processing module, and the interface visualization module is connected to the scene engine module;
[0027] The data acquisition module is used to collect the status of the equipment, model the equipment, and provide real-time data processing, alarm processing and command processing. The generated model data can be used to drive the process of the scene;
[0028] The data processing module is used to model the collected device status, third-party alarms, and energy consumption data, generate trigger information based on the modeled data, and send it to the scenario service to trigger a specific business scenario;
[0029] The scene engine module is used to provide the configuration and operation status of the scene and can dynamically access the model data;
[0030] The interface visualization module is used to provide configuration configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understand the current scene execution status through the visualization interface.
[0031] A smart station scene processing method and system of the present invention realizes the automated management and execution of rail transit smart station scenes through a data acquisition module, a data processing module, a scene engine module and a visual interface module. It is more intelligent and has higher execution efficiency. At the same time, it provides an extensible mechanism to realize modularization, hot plugging and dynamic loading of services, which can quickly expand the scope of services supported by the system and meet new scene requirements. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.
[0033] Figure 1 It is a step diagram of the smart station scene processing method of the present invention.
[0034] Figure 2 It is a scene data flow diagram of the smart station scene processing method of the present invention.
[0035] Figure 3 It is a flow chart of the smart station scene processing method of the present invention.
[0036] Figure 4 It is a structural diagram of the smart station scene processing system of the present invention.
[0037] In the figure: 11-data acquisition module, 12-data processing module, 13-scene engine module, 14-visualization interface module. DETAILED DESCRIPTION
[0038] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present invention, and should not be construed as limiting the present invention.
[0039] In the description of the present invention, it should be understood that the terms "length", "width", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, in the description of the present invention, "multiple" means two or more, unless otherwise clearly and specifically defined.
[0040] See also Figures 1 to 3 The present invention provides a smart station scene processing method, comprising the following steps:
[0041] S101: Collect the status of the equipment, model the equipment, provide real-time data processing, alarm processing and command processing, and the generated model data can be used to drive the process of the scene;
[0042] S102: Model the collected device status, third-party alarms, and energy consumption data, generate trigger information based on the modeled data, and send it to the scenario service to trigger a specific business scenario;
[0043] S103: Provide the configuration and operation status of the scene, and dynamically access the model data;
[0044] S104: Provide configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understand the current scene execution status through a visual interface.
[0045] In this embodiment, the scene engine provides a visual interface for scene configuration. Users can freely organize business processes according to their needs. The scene configuration includes: scene basic information configuration and action node configuration. Scene execution mode: fully automatic mode, manual mode, operation mode: single instance, the same scene can only execute one instance; multiple instances, the same scene can be executed multiple times, each time may correspond to a different scene trigger source, operation period: scene execution period configuration, scene configuration requirements: each scene must have one and only one start node and end node, the scene execution starts from the start node, each scene is a directed acyclic graph, the connection between the nodes represents the relationship between the two nodes, each node predefines the output relationship of the node, during execution, the scene engine will determine the next flow node based on the node output relationship, so when configuring the scene, the connection between the nodes must be configured, and configuration errors will cause the scene to fail to end normally. Among them, the action nodes include: built-in nodes and business nodes. The built-in nodes are mainly built-in logical nodes of the scene engine, and the control of user processes. The main ones are: start node: used to identify the initial node of scene execution; end node: used to identify the end of the scene; parallel grouping node: used to execute a group of actions in parallel, the business nodes in the group are executed in parallel, and the parallel grouping status is determined according to the status of each node; parallel end node: used to count the number of business nodes passing through the node. When it is equal to the specified number of times, the output is successful, and the next node corresponding to the successful execution is executed. Business nodes are user-defined nodes. According to user needs, they can be dynamically added or modified. They are generally divided into control, monitoring, broadcast, trigger, and reminder types. Action nodes are generally closely integrated with the platform and can be applied to multiple platforms. Business nodes need to provide possible output relationships of nodes for configuration during scene configuration. The engine framework provides interface methods. When adding new business nodes, you only need to implement the corresponding interfaces to introduce framework execution. The specific implementation steps include: introducing the scene engine interface jar package; inheriting AbstractNode to implement the process interface. Users can implement onException and onFinish interfaces as needed. onException is used for callback after execution failure. Business nodes can perform exception handling in this interface. onFinish users return the node execution relationship. The scene engine will determine the next node to flow to based on this relationship; put it into the scene engine's specified reference node directory.
[0046] For further information, see Figures 1 to 3 The triggering of the scene supports manual triggering and fully automatic triggering. Manual triggering means that the user directly clicks on the scene in the visual execution interface to execute it. Fully automatic triggering means triggering through the trigger management module. After the scene is triggered, the trigger source information of the scene trigger is saved. Subsequent nodes can obtain the trigger information of the scene from the scene trigger parameters.
[0047] For further information, see Figure 2 ,Scene execution data flow: scene list display, the scene engine provides a restful interface for querying the scene execution list, and the scene execution status; the scene visualization interface adopts two display methods: flowchart display and list display, and establishes a long connection with the backend through websocket. After the scene is executed, the node status is pushed to the front end.
[0048] For further information, see Figure 3 ,The scene execution process includes : the scene first loads the ,scene configuration information, and then builds a directed acyclic graph based on the ,scene, nodes, and relationships, and then starts execution from the start node, first searching for the start ,node, and executing from the start node until the end node is executed; ,whether it is executable, it will be judged that the current scene is a singleton. If it is a singleton, no new instance will be executed; each node in the scene can customize the ,output relationship, output parameters, and output relationship after failure. The scene engine will find the ,output relationship of the node based on the implementation of the node, and ,execute the next node.
[0049] For further information, see Figure 3 ,The running status of each node includes the execution status and the execution result. The execution status includes not executed - it has not been executed yet, ,in progress - it is being executed, ,waiting for user input - the scenario needs to wait for the user to input an operation to drive, ,execution completed - the execution has been completed. The execution results include successful ,execution failure, execution timeout, failed to obtain relationship, skipped after execution failure, and manually terminated.
[0050] See also Figure 4 , a smart station scene processing system, including a data acquisition module 11, a data processing module 12, a scene engine module 13 and an interface visualization module 14;
[0051] The data processing module 12 is connected to the data acquisition module 11, the scene engine module 13 is connected to the data processing module 12, and the interface visualization module 14 is connected to the scene engine module 13;
[0052] The data acquisition module 11 is used to collect the status of the equipment, model the equipment, and provide real-time data processing, alarm processing and command processing. The generated model data can be used for process driving of the scene;
[0053] The data processing module 12 includes data modeling and trigger management. Data modeling is used to model the collected device status, third-party alarms, and energy consumption data. Trigger management generates trigger information based on the modeled data and sends it to the scenario service to trigger a specific business scenario.
[0054] The scene engine module 13 is used to provide the configuration and operation status of the scene, and can dynamically access model data, not limited to real-time data, alarm processing, command processing, equipment energy consumption alarm data, video analysis data, etc.;
[0055] The interface visualization module 14 is used to provide configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understand the current scene execution status through a visualization interface.
[0056] In this embodiment, the data acquisition module 11 is used to collect the status of the equipment, and the equipment is modeled to provide real-time data processing, alarm processing, and command processing. The generated model data can be used for process driving of the scene. The data processing module 12 is used to collect the equipment status, third-party alarms, and energy consumption data for modeling. Trigger information is generated based on the modeled data and sent to the scene service to trigger a specific business scene. The scene engine module 13 provides the configuration and operation status of the scene, and the model data can be dynamically accessed. Finally, the visualization interface module provides configuration configuration, scene operation status display, scene configuration efficiency improvement, and scene interaction. Users can intuitively understand the current state of scene execution through the visualization interface module 14, thereby realizing the automated management and execution of the rail transit smart station scene, which is smarter and more efficient. At the same time, it provides an extensible mechanism to realize the modularization, hot plugging, and dynamic loading of the business, which can quickly expand the business scope supported by the system to meet new scene requirements.
[0057] What is disclosed above is only one or more preferred embodiments of the present application, and cannot be used to limit the scope of rights of the present application. Ordinary technicians in this field can understand that all or part of the processes of implementing the above embodiments and equivalent changes made according to the claims of the present application are still within the scope covered by the present application.
Claims
1. A smart station scene processing method, characterized in that: The following steps are involved: Collect the status of the equipment, model the equipment, provide real-time data processing, alarm processing and command processing, and the generated model data is used to drive the process of the scene; Model the collected equipment status, third-party alarms, and energy consumption data, generate trigger information based on the modeled data, and send it to the scenario service to trigger specific business scenarios; Provides scene configuration and operation status, and can dynamically access model data; It provides configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understands the current scene execution status through a visual interface.
2. The intelligent station scene processing method according to claim 1, characterized in that: In the configuration and operation states of the provided scenarios, the model data can be dynamically accessed: A scene has a start node and an end node. The scene execution starts from the start node. Each scene is a directed acyclic graph. The lines between nodes represent the relationship between two nodes. Each node has a predefined output relationship. During execution, the scene engine will determine the next flow node based on the node output relationship. When configuring the scene, the lines between nodes configure the relationship.
3. The intelligent station scene processing method according to claim 2, characterized in that: In the configuration and operation states of the provided scenarios, the model data can be dynamically accessed: Identify the initial node of the scenario execution; Marks the end of the scene; Execute a group of actions in parallel. The business nodes in the group are executed in parallel. The status of the parallel group is determined according to the status of each node. Count the number of business nodes that pass through this node. If it is equal to the specified number, the output is successful and the next node corresponding to the successful execution is executed.
4. The intelligent station scene processing method according to claim 3, characterized in that: In the configuration and operation states of the provided scenarios, the model data can be dynamically accessed: The node provides an output relationship for configuration during scene configuration. The engine framework provides interface methods. When adding a new node, you only need to implement the corresponding interface to introduce it into the framework for execution.
5. The intelligent station scene processing method according to claim 4, characterized in that: In providing configuration configuration, display of scene running status, scene configuration efficiency improvement, scene interaction, and intuitively understanding the current scene execution status through a visual interface: Directly click on the scene in the visual execution interface to trigger the scene or trigger the scene through the trigger management module. After the scene is triggered, the trigger source information of the scene trigger is saved, and the subsequent nodes obtain the trigger information of the scene from the scene trigger parameters.
6. The intelligent station scene processing method according to claim 5, characterized in that: In providing configuration configuration, display of scene running status, scene configuration efficiency improvement, scene interaction, and intuitively understanding the current scene execution status through a visual interface: Scene list display, the scene engine provides a restful interface to query the scene execution list and scene execution status; The scene visualization interface uses flowchart display and list display, establishes a long connection with the backend through websocket, and pushes the node status to the frontend after the scene is executed.
7. A smart station scene processing system, applicable to the smart station scene processing method according to any one of claims 1 to 6, characterized in that: It includes a data acquisition module, a data processing module, a scene engine module and an interface visualization module, wherein the data processing module is connected to the data acquisition module, the scene engine module is connected to the data processing module, and the interface visualization module is connected to the scene engine module; The data acquisition module is used to collect the status of the equipment, model the equipment, and provide real-time data processing, alarm processing and command processing. The generated model data can be used to drive the process of the scene; The data processing module is used to model the collected device status, third-party alarms, and energy consumption data, generate trigger information based on the modeled data, and send it to the scenario service to trigger a specific business scenario; The scene engine module is used to provide the configuration and operation status of the scene and can dynamically access the model data; The interface visualization module is used to provide configuration configuration, scene running status display, scene configuration efficiency improvement, scene interaction, and intuitively understand the current scene execution status through the visualization interface.
