CN110901712B - Inter-professional intelligent linkage method for urban rail transit - Google Patents
Inter-professional intelligent linkage method for urban rail transit Download PDFInfo
- Publication number
- CN110901712B CN110901712B CN201911148282.9A CN201911148282A CN110901712B CN 110901712 B CN110901712 B CN 110901712B CN 201911148282 A CN201911148282 A CN 201911148282A CN 110901712 B CN110901712 B CN 110901712B
- Authority
- CN
- China
- Prior art keywords
- linkage
- flow
- scene
- triggering
- nodes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B61—RAILWAYS
- B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
- B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
- B61L27/04—Automatic systems, e.g. controlled by train; Change-over to manual control
Landscapes
- Engineering & Computer Science (AREA)
- Mechanical Engineering (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a cross-professional intelligent linkage method for urban rail transit, which comprises the following steps: 1) linkage definition used for generating an xml document which meets the specification; 2) linkage deployment is executed, and a linkage plan can be divided into three modes of manual triggering, subscription triggering and timing triggering according to different triggering modes; 3) the linkage record inquiry can describe the execution details of the executed flow besides graphically showing the execution process. Compared with the prior art, the method has the advantages that the online speed of development of the linkage scene is greatly improved, the linkage effect is visual, and the like.
Description
Technical Field
The invention relates to an urban rail transit unmanned system, in particular to an inter-professional intelligent linkage method for urban rail transit.
Background
The urban rail transit unmanned system is a comprehensive information processing platform with high integration of technology and information, integrates and interconnects a plurality of dispersed and isolated subsystems into a whole by using various automatic means, improves the coordination and coordination capability among the subsystems, enhances the strain capability to various emergencies, and finally improves the overall automation level of subway operation. In order to improve the subway operation service quality and guarantee public trip safety all the time, the automation level must be continuously improved, and emergency situations (such as block, burst passenger flow, train night and the like) or various disasters (such as fire, earthquake, flooding and the like) under the operation scene are dealt with and processed in time. Therefore, the integration difficulty of system equipment in an operation scene is overcome by depending on a comprehensive monitoring platform, and effective linkage of different specialized subsystems of a straddle carrier, a motor and an electric system is necessary. At the present stage, although all subsystems are integrated on a comprehensive monitoring platform, the information of all subsystems is still independent, the unification of interfaces is only realized, and the fusion degree of the information layer is not high. Some manufacturers try to develop a linkage engine in a hard coding mode to drive multi-professional information flow, but the mode obviously cannot meet the requirement of rapid change in the subway operation process, and the system expansibility is poor.
Disclosure of Invention
The invention aims to overcome the defects in the prior art and provide a cross-professional intelligent linkage method for urban rail transit.
The purpose of the invention can be realized by the following technical scheme:
an inter-professional intelligent linkage method for urban rail transit comprises the following steps:
1) linkage definition used for generating an xml document which meets the specification;
2) linkage deployment is executed, and a linkage plan can be divided into three modes of manual triggering, subscription triggering and timing triggering according to different triggering modes;
3) the linkage record inquiry can describe the execution details of the executed flow besides graphically showing the execution process.
Preferably, the linkage definition uses a graphical design tool to draw a linkage flow pattern and generate an xml document by dragging a primitive to set an attribute, wherein a complete linkage flow pattern must include a start node, an end node and a service node, and a gateway may be added as needed to call other types of nodes of the sub-flow.
Preferably, the linkage definition specifically includes the following steps:
101) creating a blank linkage definition file by using a linkage graphic design tool;
102) all the linkage plans are drawn in a lane flow chart mode, a swimming pool primitive is dragged out of a toolbar, role modules are divided according to the types of subsystems possibly participating in different linkage scenes, one role is a lane, and a plurality of role lanes are added in the swimming pool;
103) selecting a starting node of a proper type according to the triggering form of the linkage scene, and for the linkage scene of a manual or subscription triggering type, only selecting the starting node without any limitation to place in a proper lane; for a scene with a timing trigger requirement, a timing type starting node needs to be selected;
104) dragging a script task node primitive from a toolbar according to service requirements, configuring a corresponding service script in an attribute frame of the script task node primitive, and supporting Lua and JavaScript type scripts;
105) for a linkage scene with parallel requirements, parallel gateway nodes can be added for adding flow branches, and all branches behind the gateway are executed in parallel;
106) each flow branch is provided with an end node, and other nodes can not be connected after the end node, namely the flow branch can not be connected;
107) after the steps 101 to 105, after all the process nodes are drawn, connecting the primitive nodes in sequence by using connecting lines with arrows, wherein the direction of the arrows is the direction in which the actual service should flow;
108) the designed flow document is output in two forms of pictures and xml documents, and the documents are used for online deployment.
Preferably, in the process of drawing the swim lane flowchart, the swim pool and swim lane primitives are dragged out of the toolbar, and the number of the swim lanes is consistent with the number of all subsystems participating in the linkage scene
Preferably, the number of the start nodes is determined as required, and is one or more, wherein the start node is a flow starting point, and therefore other nodes cannot be connected before the start node, that is, only go out and not go in.
Preferably, the script can set and obtain the flow global or each flow branch variable besides the logic of the corresponding script language; in addition, due to the requirement of cross-professional linkage, a large number of linkage interface instruction sets are packaged according to different specialties for calling in scripts, and the script service granularity of a single task node is consistent with the actual service granularity.
Preferably, for a scene needing to select a proper path branch according to conditions, an exclusive gateway or a inclusive gateway node can be added, and a module which can be repeatedly called in a large number can be extracted into an independent flow to be called by other flows in a mode of calling a sub-flow node.
Preferably, the subscription triggering in the linkage deployment execution specifically includes the following steps:
201) deployment of an xml file generated in the linkage definition process is carried out, the validity of the xml is verified in the deployment process, and the deployment can be successfully carried out only by verification;
202) subscription configuration, namely associating the linkage definition with corresponding subscription information, wherein the configured subscription information comprises the triggering condition of the linkage scene and a process ID to be triggered;
203) initiating a subscription, wherein the configured subscription information can be actually associated with each subsystem only after the subscription;
204) linkage scene triggering, namely the system receives a notification in real time after the numerical value of the configuration point after subscription is changed, when the numerical value meets the scene triggering condition, a corresponding deployed flow is triggered, and if a corresponding plan flow model cannot be found, the starting is failed;
205) the linkage engine can circulate according to the execution action defined in the linkage plan model execution, and whether the actual action is executed or not and the execution sequence are driven by real-time analysis data;
206) linkage tracking, after a linkage scene is triggered, the execution process of linkage is presented in the form of refreshing pictures in real time by a webpage, executed nodes are highlighted in green, the nodes which are being executed are highlighted in red, the nodes which are not being executed are not displayed in any processing, and the actual linkage business execution effect is consistent with the state of a flow chart which is refreshed in real time.
Preferably, the linkage scenario of the timed trigger and the manual trigger only comprises step 201), step 205) and step 206).
Preferably, the timing-triggered linkage scenario needs to use a timing start node during linkage definition, and configure corresponding timing information in the attribute of the timing start node, and the linkage process is executed when a timing condition is met after step 201) is completed;
the linkage scene triggered manually needs to manually start a deployed linkage process, and the same timing triggering process can be immediately triggered in a manual starting mode.
Compared with the prior art, the invention has the following advantages:
1) providing a graphical design tool, wherein the linkage service is flexible and configurable, and the construction of all linkage scenes is realized only by combining simple service scripts through the dragging graphics primitives of the graphical tool;
2) the expansion and definition of the scene can be rapidly realized according to the newly added requirement, and the linkage plan can be thermally deployed on line;
3) the linkage effect is displayed in real time in a graphical mode, and the method is very visual.
Drawings
FIG. 1 is a schematic view of linkage process node classification;
FIG. 2 is a design flow chart of the linkage process;
FIG. 3 is a simplified flow diagram of video passenger-clearing linkage;
FIG. 4 is a schematic view of a video passenger-cleaning linkage definition document structure;
FIG. 5 is a flow chart of video passenger-clearing linkage definition;
FIG. 6 is a flow chart of a linkage model parsing process.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, shall fall within the scope of protection of the present invention.
The invention relates to a cross-professional linkage method in the field of urban rail monitoring, which can realize online deployment of a linkage plan and quick update of services. The urban rail monitoring field developed by referencing workflow technology idea is across professional linkage platform, the method is realized by combining workflow idea with script engine, and linkage script instruction execution is driven by workflow technology. Workflow technology to achieve a business goal, a computer is used to automatically transfer documents, information, or tasks between multiple participants according to some predetermined rules. The workflow technology realizes the characteristics of skip, timing, circulation, judgment, parallelism and the like in a programming world in a graphical mode, and can basically simulate a series of scenes in a programming environment. For urban rail comprehensive monitoring, the monitoring effect can be more visual by using a workflow process visualization technology. The graphical plan design mode can be matched with the script which is interpreted and executed to timely respond to the change of the linkage requirement, and the configuration flexibility and the design freedom degree of the linkage plan can be greatly increased. Based on the consideration of urban rail field safety, a linkage system needs to process a large amount of data generated under a large number of operation environments in real time, and if the requirement changes, restarting the system will have great influence on operation. And based on the hot deployment form of the workflow, the system can realize the hot update of the linkage plan, namely the linkage server can realize the iterative deployment of the modification scheme without restarting.
The drawing of the linkage plan flow completely follows the flow modeling specification, and all linkage businesses are bound to flow primitives. According to the flow specification, flow nodes can be broadly classified into events, activities, gateways, and the like, as shown in fig. 1. The event is a node for controlling the progress of the process, can realize the waiting, jumping and exception handling of the process node, and is in a circle symbol in the appearance in the process. The existence of signal and message events enables the jumping of nodes in the internal steps of the linkage process and the communication among different linkage plans. The activity is a business unit of the process, and is mainly used for binding and calling the linkage script in the linkage engine, and is represented by a rounded-corner rectangular symbol. The existence of the calling sub-process can improve the modeling efficiency of the large-scale linkage scene, and designers can design a plurality of general linkage plan units in advance for calling and realizing expansion of various linkage scenes. The gateway is used for controlling the flow direction of the multi-linkage branch. Sequential flows and message flows are then used for the connection of events, activities and gateways, represented by the unidirectional arrowed connecting line symbols. And the cooperation of the pool and the road container is used for distinguishing the roles of the linkage participants.
The linkage function mainly comprises the following three parts, 1) linkage definition; 2) deployment execution; 3) the query is recorded.
The purpose of linkage definition is to generate an xml document which meets the specification, and is a precondition and a key for realizing the linkage effect. A graphical design tool can be used for drawing linkage flow patterns and generating the xml document in a mode of dragging the primitives to set the attributes. A complete flow chart must include a start node, an end node, a service node, and may also add a gateway, call a sub-flow node, etc. as required, the operation flow is shown in fig. 2, and the specific linkage definition steps are described as follows:
step 1: a blank linkage definition file is created using a linkage graphical design tool.
Step 2: all the linkage plans are drawn in a lane flow chart mode and are divided into modules according to roles of the participating subsystems in different linkage scenes. And dragging out the primitives of the swimming pool and the swimming lane from the toolbar, wherein the number of the swimming lane is consistent with that of all subsystems participating in the linkage scene.
And step 3: selecting a starting node of a proper type according to the triggering form of the linkage scene, and for the linkage scene of a manual or subscription triggering type, only selecting the starting node without any limitation to place in a proper lane; for a scenario with timing trigger requirements, a timing type start node needs to be selected. The number of the starting nodes is determined according to needs, and can be one or more. The start node is a flow starting point, so that other nodes cannot be connected before the start node, namely the node only goes out and does not go in.
And 4, step 4: and dragging the script task node primitive from the toolbar according to the service requirement, configuring the corresponding service script in the attribute box of the script task node primitive, and supporting various scripts such as Lua, JavaScript and the like. Besides writing the logic of the corresponding script language, the inside of the script can also set and obtain the flow global or each flow branch variable. In addition, due to the requirement of cross-professional linkage, a large number of linkage interface instruction sets are packaged by the platform according to different specialties for calling in the script, and the script service granularity is consistent with the actual service steps.
And 5: for a linkage scene with parallel requirements, parallel gateway nodes can be added for adding flow branches, and all branches behind the gateway are executed in parallel. For a scenario that a suitable path branch needs to be selected according to a condition, an exclusive gateway or an inclusive gateway node may be added, where the difference between the two is that a subsequent branch of the exclusive gateway only executes a first branch meeting the condition, and the inclusive gateway judges the conditions of all branches and executes all subsequent branches meeting the condition. And a module which can be called repeatedly in a large number can be extracted into an independent flow, and other flows can be called by a mode of calling a sub-flow node.
Step 6: and each flow branch is provided with an ending node, and other nodes can not be connected after the ending node, namely the flow branch can not be connected.
And 7: after steps 1 to 5, all the process nodes are drawn, and the primitive nodes are connected in sequence by using connecting lines with arrows, wherein the direction of the arrows is the direction in which the actual service should flow.
And 8: the designed flow document is output in two forms of pictures and xml documents, and the documents are used for online deployment.
As shown in fig. 5, in the linked plan designer, a script task and various gateways are collocated with a start event, a middle event and an end event, and are connected in series by a sequence flow (connecting line), so that various linked service scene models can be quickly built, and the linked plan can be timely adjusted according to various on-site emergency requirements.
The implementation of the method is described in detail below by taking a simplified train-to-station video passenger-clearing linkage process as an example. As shown in fig. 3, a simplified video passenger-clearing linkage process is provided, when a train arrives at a terminal station, a passenger-clearing operation needs to be performed, the number of passengers in each carriage of the train can be accurately identified by the train carrying the video identification system, and when the passenger-clearing time point arrives, the platform judges whether passengers exist in the train or not through the total number of passengers in the train. If not, indicating that the visitor is successfully cleared, notifying the passenger to successfully regulate the visitor, and ending the process; if so, the passengers tune and broadcast the broadcast, and simultaneously inform the central dispatching workstation to continue checking the number of people in the car after waiting for two seconds until no people are found in the car, and the process is ended; if the number of the checks exceeds 10, the passengers in the vehicle still do not evacuate completely, the passengers call the site personnel to clear the passengers, and when the passengers are successfully notified to clear the passengers, the passenger dispatching and clearing are completed, the linkage process is finished.
According to the scene description abstracted from fig. 3, according to the steps of the linkage definition flow description, appropriate flow primitive nodes are sequentially selected to generate a linkage plan file, the XML structural schematic diagram of which is shown in fig. 4, wherein the prprocesses node describes all the service information in the linkage scene, and is the functional core of the whole linkage scene. The diagram nodes describe position information of flow primitives, and a corresponding flow picture can be drawn according to the position information of the primitives, as shown in fig. 5.
The feasibility of the linkage plan is greatly influenced by human factors, so that designers of the linkage plan must strictly follow the linkage design specification and flexibly and cautiously match various flow element design flows. The deployment process linkage engine firstly analyzes the grammar of xml of the linkage plan file, if the grammar does not meet the process specification, the deployment fails, and the linkage validity is ensured by a large amount of comprehensive simulation tests.
Linkage deployment is executed, and a linkage plan can be divided into three forms of manual triggering, subscription triggering and timing triggering according to different triggering forms. The linkage model in actual operation is an execution tree, and various gateways are matched with connecting lines with different conditions to enable the real-time linkage plan to have various circulation possibilities. A complete subscription-triggered linkage scenario executes the following steps:
step 1: and (4) deploying the xml file generated in the linkage definition process, wherein the validity of the xml file can be verified in the deployment process, and the xml file can be successfully deployed only if the xml file passes the verification. As shown in fig. 6, the deployment process may parse the linkage plan document in xml format into a flow model, and cache the flow model in the memory for the system to trigger the execution.
Step 2: and (4) subscribing configuration, wherein the deployed linkage plan cannot be automatically executed and needs to be triggered through subscription. Therefore, the linkage definition needs to be associated with corresponding subscription information, and the configured subscription information includes the triggering condition of the linkage scenario and the process ID to be triggered.
And step 3: and initiating a subscription, wherein the configured subscription information can be actually associated with each subsystem only after the subscription.
And 4, step 4: and linking scene triggering, wherein the system receives a notification in real time after the numerical value of the configuration point after subscription is changed, when the numerical value meets the scene triggering condition, a corresponding deployed flow is triggered, and if a corresponding plan flow model cannot be found, the starting is failed.
And 5: the linkage engine can circulate according to the execution action defined in the linkage plan model execution, and the actual action execution or not and the execution sequence are driven by the real-time analysis data.
Step 6: linkage tracking, after a linkage scene is triggered, the execution process of linkage is presented in the form of refreshing pictures in real time by a webpage, executed nodes are highlighted in green, the nodes which are being executed are highlighted in red, the nodes which are not being executed are not displayed in any processing, and the actual linkage business execution effect is consistent with the content of a flow chart which is refreshed in real time.
Compared with the subscription triggering mode, the linkage scene of timing triggering and manual triggering does not have the steps 2-4. The timing triggered linkage scene needs to use a timing start node during linkage definition, and configure corresponding timing information in the attribute of the timing start node. And (3) after the step (1) is finished, executing the linkage process when a timing condition is met. The linkage scene triggered manually needs to manually start a deployed linkage process. The same timed triggering process can also be triggered immediately through a manual starting mode, but a linkage scene triggered by subscription cannot be started through the mode, because a subscription triggering type process needs subscription data support, and a service execution process of a process lacking subscription data cannot be carried out. Therefore, even if the flow can be triggered, the flow execution process cannot be continued in error.
The linkage record query can describe the execution details of the executed flow, including the starting time, the ending time, the process time consumption, the execution sequence, the data change situation in the process and the like of all linkage links, besides graphically displaying the execution process.
The method is already applied to a linkage engine of a Traffic command Integrated automation System (TIDAS) of Kasco signal Limited, and the System takes Traffic command as a core, integrates professional subsystems such as ATS, PSCADA, BAS, FAS, PIS, PA and CCTV and realizes intelligent scheduling. The linkage engine has the main functions of completing information integration among the cross-professional subsystems in the TIDAS and quickly realizing a linkage scene.
The linkage engine is developed by adopting Java, and after the linkage engine is used, the development online speed of a linkage scene is greatly improved, and the linkage effect is visualized; from the use condition of the user, the interaction mode is widely accepted, and the process tracking and recording query functions greatly facilitate the positioning of the user.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (6)
1. An inter-professional intelligent linkage method for urban rail transit is characterized by comprising the following steps:
1) linkage definition used for generating an xml document which meets the specification;
2) linkage deployment is executed, and a linkage plan can be divided into three modes of manual triggering, subscription triggering and timing triggering according to different triggering modes;
3) linkage record inquiry, which can describe the execution details of the executed flow besides graphically displaying the execution process;
the linkage definition specifically comprises the following steps:
101) creating a blank linkage definition file by using a linkage graphic design tool;
102) all the linkage plans are drawn in a lane flow chart mode, a swimming pool primitive is dragged out of a toolbar, role modules are divided according to the types of subsystems possibly participating in different linkage scenes, one role is a lane, and a plurality of role lanes are added in the swimming pool;
103) selecting a starting node of a proper type according to the triggering form of the linkage scene, and for the linkage scene of a manual or subscription triggering type, only selecting the starting node without any limitation to place in a proper lane; for a scene with a timing trigger requirement, a timing type starting node needs to be selected;
104) dragging a script task node primitive from a toolbar according to service requirements, configuring a corresponding service script in an attribute frame of the script task node primitive, and supporting Lua and JavaScript type scripts;
105) for a linkage scene with parallel requirements, adding parallel gateway nodes for adding flow branches, and executing all branches behind a gateway in parallel;
106) each flow branch is provided with an end node, and other nodes can not be connected after the end node, namely the flow branch can not be connected;
107) after the steps 101 to 105, after all the process nodes are drawn, connecting the primitive nodes in sequence by using connecting lines with arrows, wherein the direction of the arrows is the direction in which the actual service should flow;
108) outputting the designed flow document in two forms of a picture and an xml document, wherein the document is used for online deployment;
the subscription triggering in linkage deployment execution specifically comprises the following steps:
201) deployment of an xml file generated in the linkage definition process is carried out, the validity of the xml is verified in the deployment process, and the deployment can be successfully carried out only by verification;
202) subscription configuration, namely associating the linkage definition with corresponding subscription information, wherein the configured subscription information comprises the triggering condition of the linkage scene and a process ID to be triggered;
203) initiating a subscription, wherein the configured subscription information can be actually associated with each subsystem only after the subscription;
204) linkage scene triggering, namely the system receives a notification in real time after the numerical value of the configuration point after subscription is changed, when the numerical value meets the scene triggering condition, a corresponding deployed flow is triggered, and if a corresponding plan flow model cannot be found, the starting is failed;
205) the linkage engine can circulate according to the execution action defined in the linkage plan model execution, and whether the actual action is executed or not and the execution sequence are driven by real-time analysis data;
206) linkage tracking, after a linkage scene is triggered, the execution process of linkage is presented in a mode of refreshing pictures in real time by a webpage, executed nodes are highlighted in green, nodes which are being executed are highlighted in red, nodes which are not being executed are not displayed in any processing mode, and the actual linkage business execution effect is consistent with the state of a flow chart which is refreshed in real time;
the linkage scene of the timing trigger and the manual trigger only comprises step 201), step 205) and step 206);
the timing triggered linkage scene needs to use a timing start node during linkage definition, and configure corresponding timing information in the attribute of the timing start node, and the linkage process is executed when the timing condition is met after step 201) is finished;
the linkage scene triggered manually needs to manually start a deployed linkage process, and the same timing triggering process can be immediately triggered in a manual starting mode.
2. The inter-professional intelligent linkage method for urban rail transit according to claim 1, wherein the linkage definition uses a graphical design tool to draw linkage flow patterns by dragging primitives to set attributes and generate xml documents, wherein a complete linkage flow pattern must include start, end and service nodes, and gateways and other types of nodes for calling sub-flows can be added as required.
3. The intelligent linkage method for urban rail transit cross-speciality according to claim 1, wherein in the process of drawing the swim lane flow chart, swimming pool and swim lane primitives are dragged out of a toolbar, and the number of the swim lanes is consistent with the number of all subsystems participating in the linkage scene.
4. The inter-professional intelligent linkage method for urban rail transit according to claim 1, wherein the number of the start nodes is determined as required and is one or more, wherein the start node is a starting point of a process, so that other nodes cannot be connected before the start node, namely the nodes only go out and go in.
5. The inter-professional intelligent linkage method for urban rail transit according to claim 1, wherein the inside of the script can write the logic of a corresponding script language, and set and acquire a flow global or each flow branch variable; in addition, due to the requirement of cross-professional linkage, a large number of linkage interface instruction sets are packaged according to different specialties for calling in scripts, and the script service granularity of a single task node is consistent with the actual service granularity.
6. The inter-professional intelligent linkage method for urban rail transit according to claim 1, wherein for a scene in which a suitable path branch needs to be selected according to conditions, an exclusive gateway or an inclusive gateway node can be added, a module which can be repeatedly called in large quantity can be extracted into an independent flow, and other flows can be called by calling a sub-flow node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911148282.9A CN110901712B (en) | 2019-11-21 | 2019-11-21 | Inter-professional intelligent linkage method for urban rail transit |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911148282.9A CN110901712B (en) | 2019-11-21 | 2019-11-21 | Inter-professional intelligent linkage method for urban rail transit |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110901712A CN110901712A (en) | 2020-03-24 |
| CN110901712B true CN110901712B (en) | 2022-01-28 |
Family
ID=69818463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911148282.9A Active CN110901712B (en) | 2019-11-21 | 2019-11-21 | Inter-professional intelligent linkage method for urban rail transit |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110901712B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113553094A (en) * | 2020-04-24 | 2021-10-26 | 深圳市中兴系统集成技术有限公司 | Method for configuring linkage rules of graphical rail transit security and protection integrated platform |
| CN112758142B (en) * | 2021-01-28 | 2023-03-14 | 青岛海信网络科技股份有限公司 | Scene modularization realization method and device applied to full-automatic operation system |
| CN114091151B (en) * | 2021-11-15 | 2023-03-31 | 国网江苏省电力有限公司扬州供电分公司 | BIM model-based substation auxiliary equipment linkage logic verification method |
| CN116307658A (en) * | 2023-01-10 | 2023-06-23 | 广东远景信息科技有限公司 | Emergency flow management method, system, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110063326A (en) * | 2009-12-02 | 2011-06-10 | 인터내셔널 비지네스 머신즈 코포레이션 | Managing data in markup language documents stored in a database system |
| CN102880462A (en) * | 2012-08-29 | 2013-01-16 | 青岛海信网络科技股份有限公司 | Method and device for generating configuration monitoring object based on graph mode integration |
| CN105550819A (en) * | 2015-12-29 | 2016-05-04 | 国电南瑞科技股份有限公司 | Realization method for comprehensively monitoring decision support models |
| CN107168703A (en) * | 2017-05-11 | 2017-09-15 | 山大鲁能信息科技有限公司 | A kind of flow drawing generating method and system based on SVG plug-in units |
| CN109606432A (en) * | 2018-12-12 | 2019-04-12 | 卡斯柯信号有限公司 | A kind of method and apparatus for realizing the linkage of station operation post using CTC3.0 |
-
2019
- 2019-11-21 CN CN201911148282.9A patent/CN110901712B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110063326A (en) * | 2009-12-02 | 2011-06-10 | 인터내셔널 비지네스 머신즈 코포레이션 | Managing data in markup language documents stored in a database system |
| CN102880462A (en) * | 2012-08-29 | 2013-01-16 | 青岛海信网络科技股份有限公司 | Method and device for generating configuration monitoring object based on graph mode integration |
| CN105550819A (en) * | 2015-12-29 | 2016-05-04 | 国电南瑞科技股份有限公司 | Realization method for comprehensively monitoring decision support models |
| CN107168703A (en) * | 2017-05-11 | 2017-09-15 | 山大鲁能信息科技有限公司 | A kind of flow drawing generating method and system based on SVG plug-in units |
| CN109606432A (en) * | 2018-12-12 | 2019-04-12 | 卡斯柯信号有限公司 | A kind of method and apparatus for realizing the linkage of station operation post using CTC3.0 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110901712A (en) | 2020-03-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110901712B (en) | Inter-professional intelligent linkage method for urban rail transit | |
| CN108874493B (en) | ATS interface display method and device based on comprehensive monitoring platform | |
| CN109747682A (en) | Rail traffic light current integral system | |
| CN104680320A (en) | BIM-based project management system and method | |
| CN111191314B (en) | BIM and VR-based subway public area decoration integrated design construction method | |
| CN113342704B (en) | Data processing method, data processing equipment and computer readable storage medium | |
| KR102116390B1 (en) | Disaster Countermeasures Training method capable to make training scene and system thereof | |
| CN111104622A (en) | WEBGL-based three-dimensional GIS intelligent monitoring method and device | |
| CN109491735A (en) | Integrated data generates the comprehensively monitoring human-machine interface configuration implementation method with verification | |
| Preis et al. | Ground operation on vertiports–introduction of an agent-based simulation framework | |
| CN108320610B (en) | A kind of public security traffic commander's simulation training system based on network cooperating | |
| Li et al. | Express Parcel Packaging Waste Recycling Platform | |
| Raghothama et al. | Distributed, integrated and interactive traffic simulations | |
| CN112114860B (en) | Virtual reality content output and application integrated equipment | |
| CN111899337B (en) | Model service chain driven environment emergency monitoring and virtual simulation method and device | |
| KR102110259B1 (en) | Method and system for creating related SStandard Operating Procedure | |
| CN113727187A (en) | Animation video processing method and device based on skeleton migration and related equipment | |
| CN107564394B (en) | A kind of intelligent transportation experimental teaching the sand dish controls method and device | |
| ElBanhawy et al. | Real-time electric mobility simulation in metropolitan areas | |
| CN110780737A (en) | ERP enterprise information management and panoramic VR combined system | |
| JP2016006555A (en) | Planning business support method and system | |
| Wang et al. | Virtual controller interface device for hardware-in-the-loop simulation of traffic signals | |
| TWI803309B (en) | Construction method of augmented navigation in flight simulation system and its flight simulation system | |
| Hause et al. | The Use of MBSE in Infrastructure Projects‐‐An MBSE Challenge Team Paper | |
| Madni et al. | From Models to Stories |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |