CN115858520A - Data processing method, front-end processor and comprehensive monitoring system - Google Patents

Abstract

The application relates to the technical field of train track system monitoring, and discloses a data processing method, a front-end processor and a comprehensive monitoring system, which are used for solving the problem that the data processing efficiency is too low in the traditional comprehensive monitoring system. The method comprises the following steps: acquiring a label file, wherein the label file comprises a mapping relation among a plurality of label information of each monitored point, the label file comprises a plurality of label information, and each label information at least comprises a label value, a point table address and a label name; receiving a data processing request of a front-end monitoring module, wherein the data processing request comprises a tag name and a tag value of a target monitored point; determining a data operation type according to the mapping relation and the label name of the target monitored point, and determining a target point table address corresponding to the target monitored point according to the mapping relation and the label value of the target monitored point; and positioning a target monitored point through the target point table address, and executing an operation corresponding to the data operation type on the target monitored point.

Description

Data processing method, front-end processor and integrated monitoring system

technical field

The present application relates to the technical field of train monitoring, in particular to a data processing method, a front-end processor and an integrated monitoring system.

Background technique

The inventor found that in the traditional integrated supervision and control system (Integrated Supervision and Control System, ISCS), the control or monitoring of data is to maintain a data table in the system database, and the data of all monitored points are persisted in the data table , when data is monitored or needs to be controlled, the data configuration table will be retrieved, and after the corresponding data variable is found, operations such as calling, adding, updating, modifying, or deleting the data variable will be performed.

For comprehensive monitoring systems such as modern multi-line rail transit, there are a lot of monitored points, and the corresponding data volume is also huge. Through the way of data table configuration table, a series of retrieval and processing methods are performed on the data table, reducing the processing efficiency.

Contents of the invention

The purpose of this application is to provide a data processing method, a front-end processor and an integrated monitoring system to solve the technical problem of low data processing efficiency in traditional solutions.

A data processing method, the data processing method comprising:

Obtaining a label file, the label file is suitable for representing the mapping relationship between multiple label information of each monitored point, the label file includes multiple label information, and each label information includes at least a label value, a point table address and a label name;

Receive a data processing request, the data processing request includes the tag name and tag value of the target monitored point;

Determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the target point table address corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point;

The target monitored point is located through the address of the target point table, and the operation corresponding to the data operation type is performed on the located target monitored point.

A front-end processor, comprising a memory, a processor, and a computer program stored in the memory and operable on the processor, characterized in that, when the processor executes the computer-readable instructions, the aforementioned Steps of the data processing method.

A comprehensive monitoring system, including a front-end monitoring module, a front-end processor and more than one monitored subsystem, and the monitored subsystem includes more than one monitored point;

The front-end processor is used to obtain the label file. The label file contains the mapping relationship between multiple label information of each monitored point. Each label file includes multiple label information, and each label information includes at least the label value and point table address. and the tag name;

The front-end monitoring module is used to send a data processing request to the front-end processor, and the data processing request includes the tag name and tag value of the target monitored point;

The front-end processor is used to respond to the data processing request, determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the target point table corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point Address: Locate the target monitored point through the address of the target point table, and perform the operation corresponding to the data operation type on the target monitored point.

In the solution provided by this application, it can be seen that this application mainly includes the following features: 1) When the monitored point changes, the monitored point can be configured through the label file and configured to the front-end processor, so that the monitored node can be deployed It is not necessary to configure the data tables one by one, but only needs to configure the mapping relationship, which is more flexible and simple. 2) This application only needs to maintain the mapping relationship of the tag information of each monitored point through the tag file, avoiding data concentration into the data table, improving data security, and reducing the impact on the monitored points, especially in the train track system , the change of data at a certain monitored point will have an impact on the train track system that cannot be underestimated. 3) By maintaining the data table in the database, every time the data is monitored or controlled, the data reading and operation must perform a series of indexing, searching and other operations on the data table. When the amount of data is relatively large, for The response time of real-time monitoring and control is relatively long. In this application, the variable of the monitored point can be located directly through the mapping relationship of the label file, so as to directly locate the monitored point for reading or writing. The response time is greatly shortened, the timeliness of real-time monitoring and real-time control is improved, and the processing efficiency is improved. 4) In addition, in order to speed up the response, the method of maintaining the data table may also enable multi-threaded parallel processing, which will also increase the processing burden and resource consumption. However, since this application does not have tedious operations such as table lookup and indexing, it can effectively Reducing the number of threads, to a certain extent, also reduces resource consumption and processing burden, and is also conducive to improving processing efficiency. 5) In this application, through the tag name of the target monitored point in the data processing request, the type of data operation, such as telemetry, remote control, etc., can be known immediately, which is convenient for development. In this way, developers can develop monitoring or control codes. Pay more attention to business logic without judging the data type in the code, effectively reducing the development workload. 6) In the label file of this application, a set of point table addresses of monitored points can be defined for a set of labels. For each set of labels, the Quantity is related. Directly using the mapping relationship of the label file can calculate the monitored equipment corresponding to all monitored points in the cup monitoring subsystem, simplifying the difficulty of troubleshooting after a problem occurs in the monitored equipment. 7) In this application, when a new monitored point is added, it can be directly configured according to the point table address mapping in the label file, reducing the workload, especially when there are many monitored points, the embodiment of the present application can be greatly improved. Reduce the workload caused by configuring the offset address.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the accompanying drawings that need to be used in the descriptions of the embodiments or the prior art will be briefly introduced below. Obviously, the accompanying drawings in the following description are only for the present application For some embodiments, those of ordinary skill in the art can also obtain other drawings based on these drawings without paying creative efforts.

Fig. 1 is a schematic structural diagram of an integrated monitoring system provided by an embodiment of the present application;

Fig. 2 is another structural schematic diagram of an integrated monitoring system provided by an embodiment of the present application;

Fig. 3 is a schematic flow chart of a data processing method provided by an embodiment of the present application;

Fig. 4 is a schematic structural diagram of a front-end processor provided by an embodiment of the present application;

Fig. 5 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

In order to illustrate the technical solution of the present application, specific examples are used below to illustrate.

For the convenience of understanding the present application, the integrated monitoring system framework involved in the present application is first introduced. The integrated monitoring system can be applied in the rail transit system. , HMI), data management module (Real-time Database, RTDB) and front-end processor (Front-End Processors, RTDB), among them, between the front-end monitoring module and the data management module, can be realized through the communication service provided by the communication component service Interaction, between the data management module and the front-end processor, the interaction can also be realized through the communication service provided by the corresponding communication component service.

The front-end monitoring module includes a client component, which can provide a monitoring display interface (Graph), and the monitoring graph provided by the monitoring display interface can include four-level configuration information of site, link, device and label, wherein, One or more stations can be arranged in the rail transit scene, and the station is a computer device responsible for collecting data in the scene, and information such as computer name and network address (Internet Protocol, IP) of this computer device can be configured in the front-end monitoring module; There can be one or more links under the computer equipment used to collect data, and each link corresponds to a network card or a port of the equipment on the computer. You can also configure each link according to the type of link through the front-end monitoring module. Information such as the IP address of the network card of the link, the port number of the port, and the communication baud rate. For each link, the link can mount one or more monitored devices under a monitored subsystem, or multiple Multiple monitored devices under different monitored subsystems. Taking the rail transit system as an example, different monitored subsystems may include but not limited to: train power system, automatic fare collection system (Auto Fare Collection, AFC) , public broadcasting system, etc.

It is worth noting that the above-mentioned different monitored subsystems are independent systems, and usually use different communication drive protocols, for example, the modbus protocol used in the automatic ticketing and checking system, and the IEC104 protocol used in the power system. That is to say, for a certain link under a certain site, multiple different monitored devices can be mounted under the link according to the communication driver protocol run by the monitored subsystem. For the monitored equipment, there are many label points, each label point corresponds to a monitored point, and each monitoring point is a data collection point under the monitored equipment. Each monitored equipment can include There are multiple monitored points, and the variable corresponding to each monitored point is the data variable point that needs to be monitored or controlled.

The front-end monitoring module may include a public address system (Public Address system, PA), through which it can interact with the data management module or other systems.

The data management module is an intermediate module set between the front-end monitoring module and the front-end computer. The data management module is a comprehensive monitoring system server, which is a real-time server. The data management module includes a server plug-in for passing the service The terminal plug-in realizes services such as the delivery and analysis of the front-end monitoring module or pre-message, and the server-side plug-in can provide real-time service (RT server). The data management module can interact with the corresponding device or system through the corresponding communication driver protocol.

The front-end processor, which is a communication front-end processor, is used to connect to the monitored external device in the monitored subsystem through a driver or other interface plug-in form, that is, to connect to the monitored device. The driver (IO Server) refers to the software interface for the front-end processor to communicate with external devices such as the monitored device. Taking the comprehensive monitoring system as an example, the main responsibility of the front-end processor in the comprehensive monitoring system is to provide loading, running, stopping drivers or other interface plug-ins; the front-end processor is also used to connect and disconnect the data source server and other functions. A tool for real-time data of the monitored point. The front-end processor can obtain real-time data about the monitored point of the monitored subsystem through a variety of standard or non-standard protocols. For example, in Figure 1, the front-end processor can interact with the PA vehicle (such as a handheld walkie-talkie) through the FeqTETRA protocol, and interact with the monitored subsystem in the PA station (the station with the public address system) through the FepModbus protocol, wherein , the FeqTETRA protocol is a communication driver protocol used in PA vehicles, and the FepModbus protocol is a communication driver protocol between the front-end processor and the monitored subsystem.

As shown in Figure 2, in one embodiment, the integrated monitoring system can also include a preset database and a historical database, a front-end monitoring module or a data management module, which can be used to write relevant data to the real-time database and/or historical database to Important components in the ISMS or other systems provide the required data.

The front-end processor can realize the command call function, which is used to send force\cancel force, prohibit\cancel prohibition, simulation\cancel simulation, communication monitoring\cancel communication monitoring, record log\cancel record log, start link channel or device\stop Requests or commands such as link channels or devices.

In the traditional solution, the data management module reads the data of the monitored point into a certain database persistently, that is, maintains a data table in the database, and when there is a change in the data corresponding to the monitoring point, it will update the data through the front-end computer. table, and then monitor or subsequently control the data. The disadvantages are obvious, mainly reflected in: the data of the monitored point is too concentrated, and the security is not easy to guarantee; every time the data of the monitored point is read, the front-end processor has to go through a series of indexing operations, first search from the database, and then Update, and then write through IO, especially when the amount of data is relatively large, the response time is relatively slow for real-time monitoring and control requirements, which is unacceptable. In addition, the traditional solution above consumes too much computing resources. In order to shorten the response speed, the front-end processor has to process each data change concurrently with multiple threads. For the modern multi-line rail transit environment, the number of monitored devices and monitored points It is huge, such concurrent data is a huge challenge to the system overhead, causing resource waste and other problems.

In this regard, the inventor proposes a new design concept and introduces a unique label file, so that the front-end processor in the integrated monitoring system can use the label file to implement a monitoring or control scheme for the monitored point. The control includes adding, updating, Modify, or delete operations. In the following, the data processing method and the integrated monitoring system provided by the present application will be described in detail.

In one embodiment, a data processing method is provided, which is applied to the front-end processor in FIG. 1, as shown in FIG. 3, comprising the following steps:

S10: Obtain a tag file, the tag file is suitable for representing the mapping relationship between multiple tag information of each monitored point, the tag file includes multiple tag information, and each tag information includes at least a tag value, a point table address and a tag name.

In this embodiment, the front-end processor can first obtain the label file, which is a mapping file that indicates the mapping relationship between multiple label information of the monitored point proposed by the application. The label file defines the The naming rules and types of tags corresponding to monitoring points. Each of the above tag information includes at least the tag name, tag value and point table address of the monitored point. The monitored point is equivalent to a tag point, and the monitored point has a corresponding tag name , point table address and tag value.

Among them, the tag name is named after the data operation type of the monitored point, and the data operation type includes remote signaling, telemetry, remote control, and remote adjustment. Or remote adjustment points, etc., the corresponding data operation types are remote signaling operation, telemetry operation, remote operation or remote adjustment operation, etc., the tag value uniquely corresponds to the variable address of a monitored point, and the tag value uniquely corresponds to the address of a point table, which can be It can be seen that the unique point table address corresponding to the monitored point is defined in the tag file, and there are one or more monitored points corresponding to the same tag name, and one or more tag values can be corresponding to the same tag name, which needs to be explained More importantly, the address of the point table is also the physical address of the variable of the monitored point.

In an example embodiment, part of the content of the tag file may be specifically shown in Table 1 below:

Table 1

It should be noted that Table 1 is only an example here, and it is an example of part of the content. The label file also includes remote control label types, such as DOA and DOB, and remote control label types, such as AOAA and AOAB. , the details are not listed here, for the sake of easy understanding, combined with the above table 1, give examples of individual tags in the tag file, for example:

1. For the tag DIA, the tag type is remote signaling point, and the data type is Boolean.

The tag name is DIA, and the tag name indicates that this type of tag is a remote signaling point tag. The tag value range under this tag name is DIA1~DIA65536, which means Coils 0××××(DI)00001~065536, such as point table address 00005, Then the corresponding tag value is DIA5, indicating that the monitored point corresponding to DIA5 is a remote signaling point, and the address of the point table is 00005, where Coils0 represents a coil.

2. Label DIB, the label type is remote signaling point, and the data type is Boolean.

The label range is DIB1～DIB165536, indicating Input Registers 1××××(DI)100001～165536. For example, the address of the point table is 10005, and the corresponding label value is DIB5, indicating that the monitored point corresponding to DIB5 is a remote signaling point. The address is 10005. Input Registers1 represents an input register.

3. Label DIC, the label type is return point, the label type is (byte) BYTE, there is only one label value DIC0, and the point table address is DIC0.

Among them, all remote control and remote adjustment share a return point, 1 means remote control or remote adjustment is successful, 0 means remote control or remote adjustment fails, or 0 means it is in the initial state. Before each remote control or remote adjustment is executed, the value of the return point is generally automatically cleared to indicate that it is in the initial state. Once the front-end processor receives the correct response from the monitored device, indicating that the execution is successful, it immediately sets the return point to 1. . If the remote control or remote adjustment fails due to the abnormality of the monitored equipment, the front-end processor may receive the fault code sent by the monitored equipment. At this time, the value of the label point will indicate the fault code, ranging from 128 to 255. Generally speaking, if the value of the tag point is between 128 and 255, it should indicate that the monitored device is abnormal.

4. The tag DID, the tag type is remote signaling point, and the data type is Boolean.

The label range is DID100～DID6553615. In the embodiment of this application, the corresponding register can be split into bits in the label file to represent the DI quantity, which means the 1st to 16th bits of Input Registers 3××××(DI)00001～65536 (DI). One input register can accommodate 16 DIs. The last two digits indicate the bit where the input register is located, and the range is always 0 to 15, representing bits 1 to 16 respectively. The number in front of the bit represents the relative address of the input register. For example, the fifth label point of the point table address 300201 is DID20104. It can also be seen from here that the offset of the variable of the monitored point can be obtained by converting the point table address. address.

5. Label DOB, the label type is remote point, and the data type is byte.

The label range is DOB100～DOB6553615, and the remote control is realized by writing 4X bits (bit), which means HoldingRegister 4××××, the 1st to 16th bits (DO) of 400001～465536, one register can hold 16 DOs, and the last two The bit number indicates the bit where the holding register is located, and the range is always 0 to 15, representing the 1st to 16th bits respectively. The number in front of the bit represents the relative address of the holding register. For example, the label of the fifth bit of the point table address 400201 is DOB20104, and HoldingRegister represents the holding register.

It can also be seen from the above examples that among the label names, the label starting with AI and DI is an input channel label, and the label starting with AO and DO is a kind of output channel label.

It should be noted that, in some embodiments, the label file is also configured with mapping relationships such as data types, function codes, and register types, as shown in Table 1 above, which will not be described here.

In addition, it should be noted that, from the above tag files, it can be further seen that a group of monitored point data is defined under each group of tag names, and each monitored point corresponds to a specific point table address. According to the front-end monitoring module It is related to the number of monitored points to be monitored by configuring each subsystem. According to the configuration of the point table address, the offset address of each monitored point in the monitored subsystem can be quickly calculated to reduce the amount of code. When a problem occurs at a certain monitoring point It is also helpful to simplify the difficulty of troubleshooting.

In one embodiment, as shown in FIG. 1 , in step S10 , that is, the front-end processor obtains the label file, it means that the front-end monitoring module downloads the label file to the front-end processor through the download service. In this embodiment, the user or manager can configure the above-mentioned label file through the configuration graphical interface provided by the front-end monitoring module, and download the label file to the front-end processor through the configuration service.

Among them, according to the format organization of the label file, the supported format of the point table address in the label file can be as follows: %U:UnitAddress=VALUE, for example:

DI%U(0,0,100): If the point table address is expressed as DIX, then the point table address of the label point is X, and the valid range of X is 0-100.

AI%U(0,0,10)%*100+%U(0,0,100): If the address is expressed as AIX:Y, then the point table address of the label point is X*100+Y, and the valid range of X is 0-10, the valid range of Y is 1-100.

It should be noted that, in some implementation manners, other address template formats may also be used, which will not be described or limited here.

After the front-end monitoring module downloads the label file, the front-end computer can load the label file, so that the graphical monitoring interface created by the front-end monitoring module can be established with each monitored point under the front-end computer through the point table address of the label file To form a unified data association, that is, to associate the actual variables of each monitored point in the graphical monitoring interface of the front-end monitoring module, so as to manage the label files of each time period.

As shown in FIG. 2 , in one embodiment, after the front-end monitoring module obtains the label file through configuration, it can see the label file of this version, which is associated with the version number of the label file and stored in the preset database.

S20: Receive a data processing request, the data processing request includes the tag name and tag value of the target monitored point.

After the front-end processor loads the label file, the front-end monitoring module can realize the purpose of monitoring or controlling the monitored point, and display the result on the graphical monitoring interface of the front-end monitoring module. Specifically, the front-end monitor can receive the front-end monitoring The data processing request of the module, the data processing request includes the tag name and tag value of the target monitored point. The target monitored point refers to one or more monitored points among the monitored points in the label file.

S30: Determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the target point table address corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point.

In this embodiment, since the data processing request contains the tag name of the target monitored point, and the tag name is named according to different data operation types, after receiving the data processing request from the front-end monitoring module, the front-end The data processing request can obtain the tag name and tag value in the data processing request. As mentioned above, the tag file configures the mapping relationship between multiple tag information of the monitored point. Therefore, according to the tag name and tag of the target monitored point File, by parsing the tag file, the tag type of the target monitored point can be obtained, and then the specific data operation type can be obtained. For example, if the tag name is DIA, it can be known that the tag type is remote signaling point, and thus the data operation type is remote signaling.

In addition, according to the tag value of the target monitored point, and according to the mapping relationship and the tag value of the target monitored point, the address of the target point table corresponding to the target monitored point is obtained. For example, if the tag value of the target monitored point is DIA5, the target point table address of the target monitored point can be obtained through the tag file as 00005.

S40: Locate the target monitored point through the address of the target point table, and perform an operation corresponding to the data operation type on the target monitored point.

After obtaining the target point table address of the target monitored point, the corresponding offset address of the target monitored point can be calculated through the target point table address, and then the target monitored point can be located by using the offset address of the target monitored point The register unit where the variable of the point is located, so as to operate the variable data of the target monitored point of the register unit, so as to perform the operation corresponding to the data operation type on the target monitored point.

In one embodiment, after step S40, that is, before executing the operation corresponding to the data operation type on the variable of the target monitored point, the following steps are further included:

S50: Determine the monitored subsystem where the target monitored point is located according to the tag name of the target monitored point.

In this embodiment, after receiving the data processing request, the monitored subsystem where the target monitored point is located is determined according to the tag name of the target monitored point.

In one embodiment, before performing the operation corresponding to the data operation type on the data of the target monitored point, the front-end processor can obtain the driver protocol name sent by the front-end monitoring module; query the corresponding driver class according to the driver protocol name, and load the driver The communication driver protocol file in the class includes the communication driver protocol file corresponding to the subsystem where each monitored point is located. In this embodiment, the front-end monitoring module can specify the driver protocol name before downloading the label file, so that the front-end processor responds to the designation of the front-end monitoring module, obtains the corresponding driver class according to the driver protocol name, and loads the communication in the driver class. Driver protocol file. For example, obtain the modbus protocol and IEC104 protocol files to provide a driver interface during communication to facilitate the interaction between the front-end processor and the monitored subsystem.

S60: Determine the communication driver protocol corresponding to the monitored subsystem where the target monitored point is located;

For example, if the target monitored point is a monitored point in the train power system, it can be determined that the communication driving protocol of the train power system is the IEC104 protocol.

In this way, in step S40, the operation corresponding to the data operation type is performed on the target monitored point, and the operation corresponding to the data operation type can be performed on the target monitored point based on the communication driving protocol corresponding to the monitored subsystem.

After determining the communication driver protocol corresponding to the monitored subsystem, based on the communication driver protocol corresponding to the monitored subsystem, the operation corresponding to the data operation type can be performed on the data of the target monitored point. For example, based on the IEC104 protocol, the train can be The variables of the monitored points corresponding to the monitored equipment in the power system are operated. For the automatic ticketing and checking system, the modbus protocol can be loaded. For other monitored subsystems, the follow-up operations can also be completed by loading the corresponding communication driver protocol. Here Not one by one examples.

It can be seen that in this embodiment, the front-end processor pre-loads the required driver class through the driver protocol name specified by the front-end monitoring module to meet the subsequent communication requirements with the monitored subsystem.

In one embodiment, the data operation type includes data monitoring operation, and the operation corresponding to the data operation type is performed on the variable of the target monitored point, including: locating the target monitored point through the target point table address of the target monitored point, reading Variable data of the target monitored point, and publish the variable data of the target monitored point to the target topic (Topic) of the data management module, so that the front-end monitoring module that has subscribed to the target topic can synchronize to the variable of the target monitored point change data. In one embodiment, for the front-end monitoring module, it can subscribe to the topics corresponding to a plurality of different monitored points, and obtain the change data of different monitored points through the above method, and render them in the monitoring display interface in different colors, To achieve the purpose of monitoring each monitored point. Here we do not limit the scheme of how the front-end monitoring module displays the data of the monitored points, which can be set according to the needs, and will not be expanded here in detail.

It can be seen that in this embodiment, there is provided a solution for monitoring the data of each monitored point by using a tag file, wherein, in some application scenarios, the above-mentioned monitored point can be a remote signaling point or a telemetry point, Therefore, the purpose of remote signaling or telemetry is obtained, which is conducive to effective monitoring of all monitored systems.

As shown in FIG. 2 , in some embodiments, after the data management module obtains the change data of each monitored point sent by the front-end processor, it will also synchronously record the change data in the preset database.

In an application scenario, the data operation type includes data control operation, and the operation corresponding to the data operation type is performed on the variable of the target monitored point, including: responding to the data control operation, and correspondingly changing the variable data of the target monitored point. In some application scenarios, the target monitored point is a remote point or a remote adjustment point. When the front-end monitoring module needs to control the target monitored point, it can generate the above data processing request according to the tag type of the target monitored point. The tag name of the data processing request indicates the specific data operation type, such as remote adjustment or remote control, Therefore, the data processing request is sent to the front-end processor, and the front-end processor locates the target monitored point according to the label value of the target monitored point in the data processing request, and performs telemetry or remote adjustment on the variable data of the target monitored point , so as to control the monitored equipment corresponding to the target monitored point. In this embodiment, a solution is provided to control the data of each monitored point by using a label file, which can be telemetry or adjustment, so as to achieve the purpose of remote signaling or telemetry, which is beneficial to all monitored points The monitored points of the system are controlled, such as changing the equipment status of some monitored equipment in the monitored subsystem.

Through the above description, it can be seen that the data processing method provided by the application embodiment mainly includes the following features:

1) When the monitored points change, the monitored points can be configured through the label file and configured to the front-end processor, so that when deploying the monitored nodes, there is no need to configure them one by one, but only need to configure the mapping relationship, which is more flexible and simple.

2) There is no need to centralize the data into the data table of the database as in the traditional scheme. This application only needs to maintain the mapping relationship of the label information of each monitored point through the label file, avoiding the collection of data into the data table, and improving data security. To reduce the impact on the monitored point, especially in the train track system, the change of data at a certain monitored point will have an impact on the train track system that cannot be underestimated.

3) By maintaining the data table in the database, every time the data is monitored or controlled, a series of index operations must be performed on the data table for data reading and operation. First, search. When the amount of data is large, for The response time of real-time monitoring test and control is relatively long. In this application, the variable of the monitored point can be located directly through the mapping relationship of the label file, so as to directly locate the variable of the monitored point to read or Write, greatly shorten the response time, improve the timeliness of real-time monitoring and real-time control, and improve the processing efficiency.

4) In addition, in order to speed up the response, the method of maintaining the data table may also enable multi-threaded parallel processing, which will also increase the processing burden and resource consumption. However, since this application does not have tedious operations such as table lookup and indexing, it can effectively Reducing the number of threads, to a certain extent, also reduces resource consumption and processing burden, and is also conducive to improving processing efficiency.

5) In this application, through the tag name of the target monitored point in the data processing request, the type of data operation, such as telemetry, remote control, etc., can be known immediately, which is convenient for development. In this way, developers can develop monitoring or control codes. Pay more attention to business logic without judging the data type in the code, effectively reducing the development workload.

6) In the label file of this application, a set of point table addresses of monitored points can be defined for a set of labels. For each set of labels, the Quantity is related. Directly using the mapping relationship of the label file can calculate the monitored equipment corresponding to all monitored points in the cup monitoring subsystem, simplifying the difficulty of troubleshooting after a problem occurs in the monitored equipment. 7) In this application, when a new monitored point is added, it can be directly configured according to the point table address mapping in the label file, reducing the workload, especially when there are many monitored points, the embodiment of this application can greatly Reduce the workload caused by configuring the offset address.

In one embodiment, as shown in FIG. 4, a front-end processor is provided, including:

Obtaining module 101, for obtaining label file, and label file comprises the mapping relation of a plurality of label information of each monitored point, and label information comprises label value, point table address and label name;

The receiving module 102 is used to receive the data processing request of the front-end monitoring module, and the data processing request includes the tag name and tag value of the target monitored point;

The processing module 103 is used to determine the data operation type according to the tag name of the mapping relationship and the target monitored point, and determine the target point table address corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point; The table address locates the variable of the target monitored point, and performs the operation corresponding to the data operation type on the variable of the target monitored point.

In an embodiment, the processing module 103 is also used for:

According to the tag name of the target monitored point, determine the monitored subsystem where the target monitored point is located;

Determine the communication driver protocol corresponding to the monitored subsystem;

Based on the communication driver protocol corresponding to the monitored subsystem, the operation corresponding to the data operation type is performed on the variable of the target monitored point.

In an embodiment, the acquisition module 101 is also used to: acquire the name of the driving protocol sent by the front-end monitoring module; the processing module 103 is also used to: acquire the corresponding driver class according to the name of the driver protocol, and load the communication driver protocol file in the driver class , the communication driver protocol file includes the communication driver protocol file corresponding to the monitored subsystem where each monitored point is located.

In one embodiment, the data operation type includes data monitoring operations, and the processing module is also used to: read the variable data of the target monitored point, and publish the variable data of the target monitored point to the target topic of the data management module, so as to Make the front-end monitoring module that has subscribed to the target topic synchronize the variable data of the target monitored point. The target monitored point can be a remote signaling point or a telemetry point.

In an embodiment, the processing module 103 is further configured to: respond to the data control operation, and modify the variable data of the target monitored point accordingly. The target monitored point can be a remote point or a remote adjustment point.

In one embodiment, an integrated monitoring system is characterized in that it includes a front-end monitoring module, a front-end processor, and more than one monitored subsystem, and the monitored subsystem includes more than one monitored point;

The front-end processor is used to obtain a label file. The label file includes a mapping relationship between multiple label information of each monitored point. The label file includes multiple label information, and each label information includes at least a label value, a point table address and tag name;

The front-end monitoring module is used to send a data processing request to the front-end processor, and the data processing request includes the tag name and tag value of the target monitored point;

The front-end processor is used to respond to the data processing request, determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the target point table corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point Address: Locate the target monitored point through the address of the target point table, and perform the operation corresponding to the data operation type on the target monitored point.

In one embodiment, the integrated monitoring system further includes a data management module, and the data operation type includes data monitoring operation;

The front-end processor is used to read the variable data of the target monitored point, and publish the variable data of the target monitored point to the target theme of the data management module;

The front-end monitoring module is used to subscribe to the target topic, and when the variable data corresponding to the target topic changes, synchronize the variable data of the target monitored point.

It should be noted that, for more descriptions about the front-end processor or the integrated monitoring system, you can refer to the aforementioned method embodiments and the description of the aforementioned integrated monitoring system, and the description will not be repeated here. The features may also correspond to the descriptions in the aforementioned method embodiments, and will not be described again here.

In one embodiment, a kind of computer equipment is provided, and its internal structure diagram can be as shown in Figure 5, and this computer equipment can be above-mentioned front-end processor, and this computer equipment comprises the processor connected by system bus, memory and communication interface , wherein the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile and volatile storage media, and internal memory. The storage medium stores a computer program. The communication interface of the computer device is used to connect and communicate with external external systems, such as the front-end monitoring module, etc., to obtain the required data or instructions. When the computer program is executed by the processor, it can realize the above-mentioned The steps or functions of setting up the machine.

In one embodiment, a computer-readable storage medium is provided. The readable storage medium stores a computer program. When the computer program is executed by a processor, the steps or functions of the front-end processor mentioned in the embodiments of the present application are realized.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the above computer programs can be stored in a non-volatile computer-readable storage medium In this case, when the computer program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, any references to memory, storage, database or other media used in the various embodiments provided in the present application may include non-volatile and/or volatile memory. Nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Chain Synchlink DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still apply to the foregoing embodiments Modifications to the technical solutions recorded, or equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of each embodiment of the application, and should be included in this application. within the scope of protection.

Claims (10)

1. A data processing method, characterized in that, the data processing method comprises: Acquiring a tag file, the tag file is suitable for characterizing the mapping relationship between multiple tag information of each monitored point, the tag file includes a plurality of tag information, and each tag information includes at least a tag value, a point table address and a tag name; receiving a data processing request, the data processing request including the tag name and tag value of the target monitored point; Determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the target point table address corresponding to the target monitored point according to the mapping relationship and the tag value of the target monitored point ; The target monitored point is located through the address of the target point table, and an operation corresponding to the data operation type is performed on the located target monitored point. 2. The data processing method according to claim 1, wherein, before performing the operation corresponding to the data operation type on the target monitored point, the method further comprises: determining the monitored subsystem where the target monitored point is located according to the tag name of the target monitored point; Determine the communication driver protocol corresponding to the monitored subsystem; The performing the operation corresponding to the data operation type on the target monitored point includes: Based on the communication driver protocol corresponding to the monitored subsystem, the operation corresponding to the data operation type is performed on the target monitored point. 3. The data processing method according to claim 2, wherein the communication driver protocol corresponding to the monitored subsystem comprises: Obtain the name of the driver protocol sent by the front-end monitoring module; Obtain the corresponding driver class according to the name of the driver protocol, and load the communication driver protocol file in the driver class, the communication driver protocol file includes the communication driver protocol file corresponding to the monitored subsystem where each monitored point is located. 4. The data processing method according to claim 2, wherein the data operation type includes a data monitoring operation, and performing the operation corresponding to the data operation type on the target monitored point includes: Read the variable data of the target monitored point, and publish the variable data of the target monitored point to the target topic of the data management module, so that the front-end monitoring module that has subscribed to the target topic can synchronize all The variable data of the target monitored point. 5. The data processing method according to claim 4, wherein the target monitored point is a remote signaling point or a telemetry point. 6. The data processing method according to claim 2, wherein the data operation type includes a data control operation, and performing the operation corresponding to the data operation type on the target monitored point includes: In response to the data control operation, corresponding changes are made to the variable data of the target monitored point. 7. The data processing method according to claim 6, wherein the target monitored point is a remote control point or a remote adjustment point. 8. A front-end processor, characterized in that it comprises a memory, a processor, and a computer program stored in the memory and operable on the processor, wherein the processor executes the computer program When realizing the steps of the data processing method described in any one of claims 1 to 7. 9. An integrated monitoring system, characterized in that it includes a front-end monitoring module, a front-end processor and more than one monitored subsystem, and the monitored subsystem includes more than one monitored point; The front-end processor is used to obtain a label file, the label file is suitable for representing the mapping relationship between multiple label information of each monitored point, the label file includes multiple label information, each of the label information Include at least tag value, point table address and tag name; The front-end monitoring module is configured to send a data processing request to the front-end processor, and the data processing request includes the tag name and tag value of the target monitored point; The front-end processor is configured to respond to the data processing request, determine the data operation type according to the mapping relationship and the tag name of the target monitored point, and determine the data operation type according to the mapping relationship and the tag name of the target monitored point value, determine the target point table address corresponding to the target monitored point; locate the target monitored point through the target point table address, and execute the operation corresponding to the data operation type on the target monitored point. 10. integrated monitoring system as claimed in claim 9, is characterized in that, described integrated monitoring system also comprises data management module, and described data operation type comprises data monitoring operation; The front-end processor is used to read the variable data of the target monitored point, and publish the variable data of the target monitored point to the target theme of the data management module; The front-end monitoring module is configured to subscribe to the target topic, and when the variable data corresponding to the target topic changes, synchronize the variable data of the target monitored point.

Images