CN106997510B - Rule-based accident picture and emergency plan pushing method - Google Patents
Rule-based accident picture and emergency plan pushing method Download PDFInfo
- Publication number
- CN106997510B CN106997510B CN201710211645.3A CN201710211645A CN106997510B CN 106997510 B CN106997510 B CN 106997510B CN 201710211645 A CN201710211645 A CN 201710211645A CN 106997510 B CN106997510 B CN 106997510B
- Authority
- CN
- China
- Prior art keywords
- rule
- data point
- picture
- plan
- key item
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/156—Query results presentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/06—Electricity, gas or water supply
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C3/00—Registering or indicating the condition or the working of machines or other apparatus, other than vehicles
- G07C3/08—Registering or indicating the production of the machine either with or without registering working or idle time
- G07C3/12—Registering or indicating the production of the machine either with or without registering working or idle time in graphical form
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Abstract
The invention discloses a rule-based accident picture and emergency plan pushing method, which comprises the steps of loading rule objects and the hierarchical logic relationship of the rule objects and analyzing by using a rule object analyzer; extracting a data point object in the rule object through a data point object message registration monitoring component and performing message registration on the data point object; meanwhile, carrying out message registration on the rule online submission data point object; responding and processing the state change of the data point object, and evaluating the logic expression rule of the rule object by using a logic expression rule evaluator; and dynamically creating pop-up accident pictures and failure plan resources and actively looking up and editing the failure plan resources by using the accident picture and plan resource processing component. The invention can effectively help the dispatching personnel to rapidly carry out fault emergency command so that the related emergency repair personnel can rapidly organize emergency repair according to the content of the plan, thereby preventing the further expansion of the fault or the dangerous case and ensuring the system safety and the operation safety.
Description
Technical Field
The invention relates to the field of power monitoring systems, in particular to a rule-based accident picture and emergency plan pushing method.
Background
With the rapid development of computer technology, communication technology and artificial intelligence technology, power monitoring systems are increasingly widely used in the power industry and other related industries. Particularly, with the rapid development of world economy and population, people have higher and higher requirements on convenient, rapid and comfortable transportation, and urban rail transit is rapidly developed while the rapid development of water, land and air, particularly urban rail transit represented by subways, urban rails and light rails, and the rapid development of the urban rail transit is realized while the power supply which is highly safe, reliable, economical, reasonable and applicable and convenient to dispatch and operate is an important condition and guarantee for the safe, normal and effective operation of the urban rail transit. Meanwhile, in order to effectively deal with emergency accidents and other safety derived events of the regional power system, corresponding emergency treatment is carried out, the work is recovered after being improved, and the guarantee of regional power supply is also an indispensable important content.
However, the emergency plans of the common operation departments such as subways, light rails and the like exist in the form of files, so that the emergency plans are inconvenient to directly call and read in a system, and real-time monitoring pictures and failure plan resources cannot be actively pushed according to emergencies. Although training can be performed aiming at the emergency handling process of the fault at ordinary times, if sudden faults occur in the actual working process, hands and feet are in disorder, and the training content at ordinary times can be recalled difficultly and the emergency handling of corresponding accidents can be guaranteed to be completed smoothly. Therefore, when an alarm or a fault event occurs, the dispatching center is difficult to rapidly provide an auxiliary decision for the accident recovery processing according to the effective reference plan and carry out correct command and dispatching.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a method which can effectively help the dispatching personnel to rapidly carry out fault emergency command so that the related emergency repair personnel can rapidly organize emergency repair according to the content of a plan, thereby preventing the fault or dangerous situation from further expanding and ensuring the system safety and the operation safety. In addition, the emergency plan resources can be retrieved at any time for learning or online revision, and the problem of storage, management and upgrading of paper plans is further solved.
The purpose of the invention is realized by the following technical scheme.
A method for pushing accident pictures and emergency plans based on rules comprises the following steps:
1) loading the rule object and the hierarchical logic relationship of the rule object, analyzing by using a rule object analyzer, and then executing the step 2);
2) extracting a data point object in the rule object through a data point object message registration monitoring component and performing message registration on the data point object; meanwhile, carrying out message registration on the rule online submission data point object, and then executing the step 3);
3) responding to the state change of the data point object, evaluating the logic expression rule of the rule object by using a logic expression rule evaluator, and then executing the step 4);
4) and dynamically creating pop-up accident pictures and fault plan resources by using the accident picture and plan resource processing component, and actively looking up and editing the fault plan resources, and ending the method.
Further, the rule object in step 1) includes: ObjectID key item, text key item, pop key item, alias key item, format key item, plan key item, schema key item, the ObjectID key item is used for uniquely identifying the rule object; the text key item is used for indicating the rule object name; the pop key item is used for indicating an active pop-up strategy, the pop key item comprises a datarec key item, and the datarec key item is used for indicating a data point object set related to the rule object; the alias key is used to indicate a custom alias for the data point object; the formula key item is used for evaluating a logic rule, and a logic rule expression is customized by using a user-defined alias of the data point object; the plan key item is used for indicating a failure plan resource; the schema key item is used for indicating a picture resource, and the schema key item includes schema object id for identifying a unique picture object and name information of a station to which the picture object belongs.
Further, the data point object comprises a double point type remote signaling point, a MeasuredValue type remote point, a double command object remote control point and an integrated total object remote control point, and the data point object comprises an object Id attribute, an object name attribute and an object description.
Further, the hierarchical logic relationship is expressed as a triple, the triple comprises an ObjectId, an AttributeTypeId and a WiredObjectId, the ObjectId represents an identification of a rule object, the WiredObjectId represents an identification of a rule object associated with the rule object identified as ObjectId, and the value set of the AttributeTypeId is { x ≦ 2, x ∈ N*}; when x is 1, it indicates that the rule object identified as wiredobject id is the parent object of the rule object identified as ObjectId; when x is 2, it indicates that the rule object identified as wiredobject id is a child object of the rule object identified as ObjectId.
Further, the object parser loads all rule object information and the hierarchical logic information thereof into the memory and establishes a mapping relationship, and then constructs the rule objects into a tree-shaped organization structure to be stored into the memory.
Further, the data point object message registration monitoring component in step 2) supports message registration monitoring of Web B/S architecture data point objects, the data point object message registration monitoring component provides a uniform front-end request interface and a uniform background service process management mechanism, the data point object message registration monitoring component acquires all rule objects and extracts a data point object of each object, and the data point object message registration monitoring component generates a combination Key by using a data point identifier and an attribute name of a data point object and establishes a one-to-one mapping relationship with the corresponding rule object.
Further, the unified front-end request interface completes message registration and read-write request of real-time data of the data point objects in batch by means of specifying a background request service process name, a service function signature and a callback function object; the unified background service process management mechanism is composed of a communication relay process and different background services.
Further, the rule object is configured through a configuration tool, a configuration online modification interface is reserved, a rule submission event is triggered after configuration is completed, the data point object monitoring and processing component is required to analyze a new rule object again after monitoring the submission event, and the data point object monitoring and processing component is used for updating a data point object message monitoring list to complete a configuration online modification function.
Further, when the attribute value or the state of the registered data point object changes in step 3), the rule object is located through a mapping relationship, then the logic rule of the rule object and the alias information of the data point object are extracted, and the logic rule is analyzed and restored to be the logic rule which can be analyzed and executed by the logic expression rule evaluator, and if the evaluation result is true, the subsequent processing is performed; if false, no response is made.
Further, the accident picture and plan resource processing component in the step 4) comprises an accident picture processing unit, a failure plan processing unit and a failure plan resource retrieval and editing interface for receiving and processing the rule object transmitted by the logic expression rule evaluator.
Further, the accident picture processing unit is used for actively popping up an accident picture in the step 4): first, a preloaded screen is processed. Extracting a schema key item of a regular object picture, and knowing whether the picture object starts a preloading mechanism or not according to the schema key item, wherein the picture preloading mechanism is used for ensuring that the time from receiving a real-time library signal point change signal to successfully pushing the picture does not exceed the performance requirement of 2s, and larger accident picture files can be specified to be preloaded in the schema key item of the regular object; secondly, processing the real-time data of the picture according to a processing result of a preloading mechanism, requesting to load a picture resource file to a background service process if the pre-loaded picture file does not exist, dynamically generating a picture display window and actively popping up, and then requesting real-time data of a picture configuration model to the background service process; if the pre-loaded picture file exists, only the corresponding picture configuration model real-time data is required to be requested.
Further, the failure plan processing unit is used for actively popping up accident plan resources in the step 4): the method comprises the steps of extracting a plan key item of a rule object, obtaining an accident plan resource storage path, dynamically generating an electronic fault plan document display window after loading plan content to a background service process and actively popping up the electronic fault plan document display window, enabling a fault plan resource retrieval and editing interface to be called by a client, extracting the plan key item of the rule object, obtaining the accident plan resource storage path and requesting the background service process to retrieve the plan content.
Compared with the prior art, the invention has the advantages that: when the sudden failure occurs, the invention can actively push out the emergency failure plan according to the logic pushing rule corresponding to the failure state of each monitoring device when the accident occurs, and simultaneously actively push out the real-time picture of the monitoring failure device and carry out the flash prompt on the failed real-time picture, and the flash prompt is cancelled until the failure of the device is recovered. Therefore, the emergency command of the fault can be effectively assisted by the dispatching personnel to rapidly organize the emergency repair according to the content of the plan by the related emergency repair personnel, so that the fault or the dangerous case is prevented from further expanding, and the system safety and the operation safety are guaranteed. In addition, the emergency plan resources can be retrieved at any time for learning or online revision, and the problems of storage, management, upgrading and the like of the paper plans are further solved.
Drawings
FIG. 1 is a process flow diagram of the present invention.
Fig. 2 is a layered structure diagram according to an embodiment of the present invention.
FIG. 3 is a flowchart illustrating a process according to an embodiment of the present invention.
FIG. 4 is a process flow of accident picture processing according to an embodiment of the present invention.
FIG. 5 is a diagram illustrating the data point object array and the alias array corresponding relationship according to an embodiment of the invention.
Detailed Description
The invention is described in detail below with reference to the drawings and specific examples.
As shown in fig. 1, a method for pushing an accident picture and an emergency plan based on rules includes the following steps:
1) loading the rule object and the hierarchical logic relationship of the rule object, analyzing by using a rule object analyzer, and then executing the step 2);
2) extracting a data point object in the rule object through a data point object message registration monitoring component and performing message registration on the data point object; meanwhile, carrying out message registration on the rule online submission data point object, and then executing the step 3);
3) responding to the state change of the data point object, evaluating the logic expression rule of the rule object by using a logic expression rule evaluator, and then executing the step 4);
4) and dynamically creating pop-up accident pictures and fault plan resources by using the accident picture and plan resource processing component, and actively looking up and editing the fault plan resources, and ending the method.
The rule object in step 1) comprises: ObjectID key item, text key item, pop key item, alias key item, format key item, plan key item, schema key item, the ObjectID key item is used for uniquely identifying the rule object; the text key item is used for indicating the rule object name; the pop key item is used for indicating an active pop-up strategy, the pop key item comprises a datarec key item, and the datarec key item is used for indicating a data point object set related to the rule object; the alias key is used to indicate a custom alias for the data point object; the formula key item is used for evaluating a logic rule, and a logic rule expression is customized by using a user-defined alias of the data point object; the plan key item is used for indicating a failure plan resource; the schema key item is used for indicating a picture resource, and the schema key item includes schema object id for identifying a unique picture object and name information of a station to which the picture object belongs.
The data in the power monitoring system is designed by adopting an object-oriented design concept, the data point objects comprise double point type remote signaling points, MeasuredValue type remote measuring points, double Command object remote control points and IntegratedTotal object remote pulse points, each point object comprises a plurality of attributes, and each attribute corresponds to a value. The attribute objects that are common to the different types of data point objects include at least an object Id attribute (ObjectId), an object Name attribute (Name), and an object description (description).
The hierarchical logical relationship is expressed as one<ObjectId,AttributeTypeId,WiredObjectId>The triplet comprises an ObjectId, an AttributeTypeId and a WiredObjectId, wherein the ObjectId represents the identification of a rule object, the WiredObjectId represents the identification of a rule object which is associated with the rule object identified as the ObjectId, the AttributeTypeId takes values in a set of { x | x ≦ 2, x ∈ N*}; when x is 1, it indicates that the rule object identified as wiredobject id is the parent object of the rule object identified as ObjectId; when x is 2, it indicates that the rule object identified as wiredobject id is a child object of the rule object identified as ObjectId.
After the hierarchical logic between the rule objects is expressed, the storage of the logic rule objects and the storage of the hierarchical logic relationship between the logic rule objects can be conveniently and respectively and independently stored.
The object resolver loads all rule object information and the hierarchical logic information thereof into the memory and establishes a mapping relation, and then constructs the rule objects into a tree-shaped organization structure to be stored into the memory.
Step 2) the data point object message registration monitoring component supports message registration monitoring of Web B/S architecture data point objects, the data point object message registration monitoring component provides a uniform front-end request interface and a uniform background service process management mechanism, the data point object message registration monitoring component acquires all rule objects and extracts the data point object of each object, and the data point object message registration monitoring component generates a combination Key by using the data point identifier and the attribute name (ObjectID _ attribute name) of the data point object and establishes a one-to-one mapping relationship with the corresponding rule object.
The unified front-end request interface completes message registration and read-write request of real-time data of the data point object in batch by specifying a background request service process name, a service function signature and a callback function object; the unified background service process management mechanism is composed of a communication relay process (wg _ message _ relay) and different background services. The front end establishes a maintenance communication connection with the wg _ message _ relay, and all front end requests are communicated with the wg _ message _ relay. And the wg _ message _ relay is responsible for distributing the request to the service process according to the service process name in the front-end request parameter. And the service process returns the service processing result to the wg _ message _ relay process, and then the process returns the processing result to the front end.
The method has the advantages that no matter how many background processes are added later, the added background service processes are only required to be registered to the wg _ message _ relay process and the inter-process communication is established, and the front end does not need any change.
The front end has an automatic reconnection function after being disconnected with the server until the connection with the server is recovered to ensure an automatic communication recovery mechanism.
The rule object is configured through a configuration tool, a configuration online modification interface is reserved, a rule submission event is triggered after configuration is completed, the data point object monitoring and processing component is required to analyze a new rule object again after monitoring the submission event, and the data point object monitoring and processing component is used for updating a data point object message monitoring list to complete a configuration online modification function.
When the attribute value or the state of the registered data point object changes in the step 3), the rule object is positioned through a mapping relation, then the logic rule of the rule object and the alias information of the data point object are extracted, and the logic rule is analyzed and restored to be the logic rule which can be analyzed and executed by the logic expression rule evaluator, and if the evaluation result is true, the subsequent processing is carried out; if false, no response is made.
The accident picture and plan resource processing component in the step 4) comprises an accident picture processing unit, a fault plan processing unit and a fault plan resource retrieval and editing interface for receiving and processing the rule object transmitted by the logic expression rule evaluator.
And step 4), an accident picture is actively popped up by using an accident picture processing unit: first, a preloaded screen is processed. Extracting a schema key item of a regular object picture, and knowing whether the picture object starts a preloading mechanism or not according to the schema key item, wherein the picture preloading mechanism is used for ensuring that the time from receiving a real-time library signal point change signal to successfully pushing the picture does not exceed the performance requirement of 2s, and larger accident picture files can be specified to be preloaded in the schema key item of the regular object; secondly, processing the real-time data of the picture according to a processing result of a preloading mechanism, requesting to load a picture resource file to a background service process if the pre-loaded picture file does not exist, dynamically generating a picture display window and actively popping up, and then requesting real-time data of a picture configuration model to the background service process; if the pre-loaded picture file exists, only the corresponding picture configuration model real-time data is required to be requested.
And 4), actively popping up accident plan resources by using the fault plan processing unit: the method comprises the steps of extracting a plan key item of a rule object, obtaining an accident plan resource storage path, dynamically generating an electronic fault plan document display window after loading plan content to a background service process and actively popping up the electronic fault plan document display window, enabling a fault plan resource retrieval and editing interface to be called by a client, extracting the plan key item of the rule object, obtaining the accident plan resource storage path and requesting the background service process to retrieve the plan content. The client with the modification authority can perform editing and saving operations.
Examples
The client side of the embodiment adopts an Extjs framework, and the background adopts a C + + service process. The processing flow of this embodiment is as shown in fig. 3, and the communication mode adopts a WebSocket of wss protocol. As shown in fig. 2, the background process includes "wg _ schema _ module", "wg _ runtime _ provider", "wg _ faultplan _ module", "wg _ message _ relay".
Step one, starting the background processes of 'wg _ message _ relay', 'wg _ runtime _ provider', 'wg _ schema _ module' and 'wg _ fault _ module' in sequence.
And step two, initializing a front-end Extjs client system.
The rule object and the hierarchical logical relationship of the rule object may be stored in a database or a configuration file independently of each other, and in this embodiment, the hierarchical logical relationship of the rule object and the rule object is stored in the configuration file separately. And analyzing the rule object and the hierarchical logic relationship thereof by adopting a mode of loading a configuration file.
Step21 loads rule object information, and each parsed rule object is an object in a standard JSON format.
Each rule object contains at least one ObjectID key for uniquely identifying the rule object. And the text key item is used for indicating the name of the rule object. pop key entry to indicate active pop-up strategy. Wherein the pop key includes at least a datarec key for indicating a set of data point objects associated with the rule object. and the alias key item is used for indicating the data point object to define the alias. And the format key item is used for evaluating a logic rule, and the logic rule expression is customized by utilizing the custom alias of the data point object. And the plan key item is used for indicating the failure plan resource. schema key item, which is used to indicate the picture resource.
The "datarec" key is, in this embodiment, a data point object stored in an Extjs array, each element of which is also an array containing two elements, namely, the ObjectId of the data point and the name of some attribute thereof. Indirect properties are also supported in this embodiment, such as the property name can be specified in the form of "State 1Link- > State". As shown in FIG. 5, the elements in datarec (data point object array) and "alias" (alias array) are to be in one-to-one correspondence. The array element "Ax" corresponding to the "alias" key term, where x is [1,2,3, …, n ], is the alias of the data point object defined in this embodiment.
The formula key is configured using the alias and the logical expression operator. For example, it is configured that "a 1 ═ 1& & a2 ═ 1", and in conjunction with fig. 5 and as described above, it is known that the elements in datarec and alias are in one-to-one correspondence, so that the meaning of the logical expression is that the logical regular expression is established when the State of the data point object whose ObjectID is 520623616 is 1 and the State of the data point object whose ObjectID is 520623872 is 1.
The "plan key item" is a file name of the electronic failure plan content actively popped up, and in this embodiment, the plan content is conveniently loaded by the Extjs front end and is stored in an HTML format for online editing.
The rule objects are exemplified as follows.
Step22, loading the rule object level logic relationship information, and storing each level logic relationship triple in the Extjs array after analysis.
Step23, the rule objects and the hierarchical logical combination generate a recursive structure in the standard JSON format.
The structure is to extend leaf and child key items on the basis of rule objects. The leaf key item indicates whether the rule object is a leaf node, and the value is true or false. When leaf is true, it is denoted as a leaf node. children represents an array of child nodes of a certain tree node. Only leaf ═ false nodes have child key terms. Child nodes are processed in a recursive manner. Until all child nodes are leaf true, i.e., correspond to a rule object.
Step three, establishing communication connection between front and back stations websocket
Step31, defining an ext. And defines a wg _ dataassociated event for data transfer when communication data arrives.
Step32, define the ext. windows. websocket. socket class, which also defines the wg _ dataarived event, also for communication data transfer. Websocket join operation for the ext.
Step33, creating an instance of the unified data request interface ext.sac.router.router class when the front-end system is initialized, creating and maintaining an instance _ web _ socket of the ext.windows.websocket.socket class, and registering a response function this _ web _ socket.on ("wg _ dataarived", this. __ on dataarived, this) of wg _ dataarived event for this instance. Additionally, the instance recreates and maintains an instance _ messageRelayManager of the ext.
When the background response data arrives, the messagerelaymarmanager instance fireEvent ("wg _ dataassociated", responseData), then __ onmessagerelayadataassociated response function triggers wg _ dataassociated event of the ext.
Step34 operates the message RelayManager to perform channel connection operation through the connection method of the web socket, and transmits all the rule objects analyzed by the rule object analyzer to the data point object monitoring and processing component after the connection is successful.
Extracting the data point objects in the rule objects by using the data point object message registration monitoring component and registering the messages; and performs message registration for the rule submission event.
Step41, traversing the rule Object which is analyzed by the rule Object analyzer and saved in the JSON format, extracting the Object and the attribute name of the data point Object, generating 'Object Id _ attribute name' as the Key of the Map structure, using the rule Object as the Value of the Map structure, and establishing the mapping relation. And storing the extracted data point object and the data point object representing the commit operation in an array structure as input parameters for requesting registration of the message.
Step42, the data point object message registration monitoring component uniformly calls the sendRequest method of the ext. The function declaration structure is:
ext.sac.router.router.sendrequest ("background service process name", "handle function signature", "parameters passed to background Json format", "ext.windows.router.requestcallback" object);
specify a callback function when the background service process data is returned in an ext. The structure example is as follows:
where scope represents the scope of the execution of the callback function and __ onInitResponse signs the callback function. args is a callback function parameter, autoRetry indicates whether a failure re-request occurs, and autoRetry indicates whether the object is automatically destroyed after the processing is finished.
Step43, the specific implementation steps of message registration are as follows:
step431, the request message registration identifies the initialization context, the request being as follows.
Sat, sac, router, sendrequest ("wg _ runtime _ provider", "Init", "clientId: this _ clientI }, and" ext.
After the initialization of Step432 and the message registration identifier is successful, the data point objects which need to be subjected to message registration are registered in batch, and the request mode is shown as follows.
Step433, circularly monitoring the state change of the data point object registered in the real-time base, and requesting as follows.
Step434, triggering this. _ web _ socket. fireevent ("wg _ dataassociated", responsedata) in the callback __ onGetUpdateResponse function and looping request to call the GetUpdates function signature of wg _ runtimeprovider.
Step435, processing the pre-loaded picture, and saving the picture file resource of the picture object to the memory by requesting the picture file resource of the picture object from the background wg _ schema _ module process.
Processing accident pictures and plan resources and dynamically creating active pop-up; and actively calling and editing the failure plan resources.
Step51, accident picture processing flow, as shown in fig. 4.
First, the picture object information in the rule object is extracted. Then, whether the picture is the preloaded picture is searched in the memory mapping of the preloaded picture object, if not, the picture is preloaded by two steps:
step551, requesting to obtain the picture file resource of the picture object from the background wg _ schema _ module process by using an ext.
Step552, using an ext, windows, router, sendrequest interface to perform message registration to the background wg _ running _ provider process, and then requesting real-time data to update the screen model configuration state from the background process.
When the data of the data point object bound by the model configuration changes, the background wg _ runtime _ provider process sends the changed real-time data to the front end, and the front end calls a message monitoring callback function to update the model configuration state of the picture. If yes, the Step552 operation is directly carried out on the preloading picture.
Step52, extracting the fault plan resource file path of the rule object directly through the fault plan processing unit, and requesting to load the background wg _ faultplan _ module through the ext. Then, an htmleditor control based on Extjs is used for displaying, and the active popup failure plan does not support online modification and storage operation.
Step53, actively calling and editing the failure plan resources, and directly calling and reading the failure plan resource editing interface by the user through the human-computer interface. And judging whether the on-line modification and storage operation of the retrieved fault plan resources is supported or not according to the authority of the user.
The invention provides a rule-based accident picture and emergency plan pushing method in a power monitoring system, which can not only carry out retrieval study and online revision on emergency plan resources at any time in the monitoring system, but also can actively push a real-time accident monitoring picture and a corresponding fault plan at the first time when sudden faults occur in operation, effectively provides an auxiliary decision basis for a dispatcher to recover and process the sudden accidents, further carries out correct command and dispatch so as to prevent the faults or dangerous situations from further expanding, and ensures the safety of the system and the operation.
Claims (11)
1. A method for pushing accident pictures and emergency plans based on rules is characterized by comprising the following steps:
1) loading the rule object and the hierarchical logic relationship of the rule object, analyzing by using a rule object analyzer, and then executing the step 2);
2) extracting a data point object in the rule object through a data point object message registration monitoring component and performing message registration on the data point object; meanwhile, carrying out message registration on the rule online submission data point object, and then executing the step 3);
3) responding to the state change of the data point object, evaluating the logic expression rule of the rule object by using a logic expression rule evaluator, and then executing the step 4);
4) and dynamically creating pop-up accident pictures and fault plan resources by using the accident picture and plan resource processing component, and actively looking up and editing the fault plan resources, and ending the method.
2. The method according to claim 1, wherein the rule object in step 1) comprises: ObjectID key item, text key item, pop key item, alias key item, format key item, plan key item, schema key item, the ObjectID key item is used for uniquely identifying the rule object; the text key item is used for indicating the rule object name; the pop key item is used for indicating an active pop-up strategy, the pop key item comprises a datarec key item, and the datarec key item is used for indicating a data point object set related to the rule object; the alias key is used to indicate a custom alias for the data point object; the formula key item is used for evaluating a logic rule, and a logic rule expression is customized by using a user-defined alias of the data point object; the plan key item is used for indicating a failure plan resource; the schema key item is used for indicating a picture resource, and the schema key item includes schema object id for identifying a unique picture object and name information of a station to which the picture object belongs.
3. The method according to claim 1, wherein the data point objects include a double point type remote signaling point, a MeasuredValue type remote signaling point, a double command object remote control point, and an integrated total object remote vein point, and the data point objects include an object Id attribute, an object name attribute, and an object description.
4. The method according to claim 1, wherein the hierarchical logical relationship is expressed as a triplet, the triplet includes ObjectId, AttributeTypeId and WiredObjectId, and the objectId represents an identifier of a rule object; the WiredObjectId represents an identifier of a rule object which has an association relationship with the rule object identified as the ObjectId, and the AttributeTypeId value set is
(ii) a When x =1, it indicates that the rule object identified as wiredobject id is the parent object of the rule object identified as ObjectId; when x =2, it indicates that the rule object identified as wiredobject id is a child object of the rule object identified as ObjectId.
5. The method according to claim 1, wherein the object parser loads all rule object information and its hierarchical logic information into the memory and establishes a mapping relationship, and then constructs the rule objects into a tree-shaped organization structure and stores the tree-shaped organization structure in the memory.
6. The method according to claim 1, wherein the data point object message registration monitoring component in step 2) supports message registration monitoring of Web B/S architecture data point objects, the data point object message registration monitoring component provides a unified front-end request interface and a unified background service process management mechanism, the data point object message registration monitoring component acquires all rule objects and extracts a data point object of each object, and the data point object message registration monitoring component generates a combination Key by using a data point identifier and an attribute name of the data point object to establish a one-to-one mapping relationship with the corresponding rule object.
7. The method according to claim 6, wherein the unified front-end request interface completes message registration and read-write request of real-time data to the data point object in batch by specifying a background request service process name, a service function signature, and a callback function object; the unified background service process management mechanism is composed of a communication relay process and different background services.
8. The method according to claim 1, wherein the rule object is configured by a configuration tool, an online configuration modification interface is reserved, a rule submission event is triggered after configuration is completed, the data point object monitoring and processing component monitors the submission event, and then the rule object parser is required to parse a new rule object again, and the data point object monitoring and processing component is used to update the data point object message monitoring list, so as to complete an online configuration modification function.
9. The method as claimed in claim 1, wherein the accident picture and emergency plan processing component in step 4) includes an accident picture processing unit, a failure plan processing unit and a failure plan resource review editing interface for receiving the rule object transmitted by the processing logic expression rule evaluator.
10. The method for pushing the accident picture and the emergency plan based on the rules of claim 9, wherein the accident picture processing unit is used to actively pop up the accident picture in step 4): firstly, processing a preloading picture, extracting schema key items of a regular object picture, and knowing whether a picture object starts a preloading mechanism or not according to the schema key items, wherein the picture preloading mechanism is used for ensuring that the time from receiving a real-time library signal point change signal to successfully pushing the picture does not exceed the performance requirement of 2s, and larger accident picture files can be specified to be preloaded in the schema key items of the regular object; secondly, processing the real-time data of the picture according to a processing result of a preloading mechanism, requesting to load a picture resource file to a background service process if the pre-loaded picture file does not exist, dynamically generating a picture display window and actively popping up, and then requesting real-time data of a picture configuration model to the background service process; if the pre-loaded picture file exists, only the corresponding picture configuration model real-time data is required to be requested.
11. The method according to claim 9, wherein the failure scenario processing unit is used to actively pop up failure scenario resources in step 4): the method comprises the steps of extracting a plan key item of a rule object, obtaining an accident plan resource storage path, dynamically generating an electronic fault plan document display window after loading plan content to a background service process and actively popping up the electronic fault plan document display window, enabling a fault plan resource retrieval and editing interface to be called by a client, extracting the plan key item of the rule object, obtaining the accident plan resource storage path and requesting the background service process to retrieve the plan content.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710211645.3A CN106997510B (en) | 2017-04-01 | 2017-04-01 | Rule-based accident picture and emergency plan pushing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710211645.3A CN106997510B (en) | 2017-04-01 | 2017-04-01 | Rule-based accident picture and emergency plan pushing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106997510A CN106997510A (en) | 2017-08-01 |
| CN106997510B true CN106997510B (en) | 2020-09-11 |
Family
ID=59434999
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710211645.3A Active CN106997510B (en) | 2017-04-01 | 2017-04-01 | Rule-based accident picture and emergency plan pushing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106997510B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113487210A (en) * | 2021-07-19 | 2021-10-08 | 广州市绯影信息科技有限公司 | Emergency plan processing method based on rule engine digital plan modeling |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110121885A (en) * | 2010-05-03 | 2011-11-09 | 연세대학교 산학협력단 | Apparatus and method for traffic accident recognition |
| CN102855142A (en) * | 2012-09-24 | 2013-01-02 | 广东华大集成技术有限责任公司 | Client architecture based on RIA (rich internet applications) and implementation method thereof |
| CN102880492A (en) * | 2012-09-24 | 2013-01-16 | 广东华大集成技术有限责任公司 | Extensive makeup language (XML) script resolver based on analysis server (AS) and method for script resolver |
| CN103529707A (en) * | 2013-11-07 | 2014-01-22 | 南京国电南自轨道交通工程有限公司 | Design method for full object-oriented intelligent alarm model in integrated supervisory control system of metro |
| CN105550355A (en) * | 2015-12-29 | 2016-05-04 | 四川中电启明星信息技术有限公司 | Rule-based data push system and method of Hose |
| CN106407579A (en) * | 2016-09-27 | 2017-02-15 | 南京国电南自轨道交通工程有限公司 | An electrical power supervisory control simulation system scene design method |
-
2017
- 2017-04-01 CN CN201710211645.3A patent/CN106997510B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110121885A (en) * | 2010-05-03 | 2011-11-09 | 연세대학교 산학협력단 | Apparatus and method for traffic accident recognition |
| CN102855142A (en) * | 2012-09-24 | 2013-01-02 | 广东华大集成技术有限责任公司 | Client architecture based on RIA (rich internet applications) and implementation method thereof |
| CN102880492A (en) * | 2012-09-24 | 2013-01-16 | 广东华大集成技术有限责任公司 | Extensive makeup language (XML) script resolver based on analysis server (AS) and method for script resolver |
| CN103529707A (en) * | 2013-11-07 | 2014-01-22 | 南京国电南自轨道交通工程有限公司 | Design method for full object-oriented intelligent alarm model in integrated supervisory control system of metro |
| CN105550355A (en) * | 2015-12-29 | 2016-05-04 | 四川中电启明星信息技术有限公司 | Rule-based data push system and method of Hose |
| CN106407579A (en) * | 2016-09-27 | 2017-02-15 | 南京国电南自轨道交通工程有限公司 | An electrical power supervisory control simulation system scene design method |
Non-Patent Citations (1)
| Title |
|---|
| 基于规则的情境感知信息推送架构;胡蓓蓓;《万方数据库》;20150917;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106997510A (en) | 2017-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108108297B (en) | Method and device for automatic testing | |
| US20020035606A1 (en) | Method and system for straight through processing | |
| CN104657402A (en) | Language Tag Management On International Data Storage | |
| CN111309550A (en) | Data acquisition method, system, equipment and storage medium of application program | |
| CN106055337A (en) | Interface generation method and device | |
| CN109194762B (en) | SSH-based soil information network publishing system and method | |
| CN112836018A (en) | Method and device for processing emergency plan | |
| CN113159091A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN115858796A (en) | Fault knowledge graph construction method and device | |
| CN109615290A (en) | For obtaining the method, apparatus, system and medium of address for service | |
| CN115240157A (en) | Road scene data persistence method, device, equipment and computer readable medium | |
| CN106997510B (en) | Rule-based accident picture and emergency plan pushing method | |
| CN115599386A (en) | Code generation method, device, equipment and storage medium | |
| CN115588244A (en) | Internet of vehicles big data real-time analysis method, device, equipment and medium | |
| CN113934832A (en) | Interactive processing method, device, equipment, medium and program product based on session | |
| CN112799760A (en) | Form rendering method and device | |
| CN112612904A (en) | Rail transit emergency method and device based on knowledge graph | |
| CN111209750A (en) | Internet of vehicles threat intelligence modeling method, device and readable storage medium | |
| CN115455922A (en) | Form verification method and device, electronic equipment and storage medium | |
| CN110759191B (en) | Elevator control method based on 5G smart park | |
| US7805715B2 (en) | Model publishing framework | |
| CN114036218A (en) | Data model switching method and device, server and storage medium | |
| CN114860233A (en) | Page generation method, device, equipment, storage medium and product | |
| CN113672603A (en) | Multi-source heterogeneous electric power big data automatic label implementation method and system | |
| CN113296796A (en) | Project release method, device, system, storage medium and electronic equipment |
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 |