CN115858349A

CN115858349A - Data verification method and device

Info

Publication number: CN115858349A
Application number: CN202211494251.0A
Authority: CN
Inventors: 李凤娇; 张长帅; 杨盛; 孟小通; 张晨; 张晏垚
Original assignee: Beijing Hollysys Co Ltd
Current assignee: Beijing Hollysys Co Ltd
Priority date: 2022-11-25
Filing date: 2022-11-25
Publication date: 2023-03-28

Abstract

The application discloses a data verification method and device. The data verification method is applied to verification of TCC (transmission control center) lower computer data of a train control center, and comprises the following steps: generating a verification case based on preset verification data according to a preset rule; generating a to-be-verified case based on to-be-verified data according to the preset rule, wherein the to-be-verified data are binary data; and comparing the data of the verification case with the data of the case to be verified to obtain a verification result.

Description

Data verification method and device

Technical Field

The present application relates to the field of data verification technologies, and in particular, to a data verification method and apparatus.

Background

The train control center, named as TCC (train center), is a ground core device of the train control system, comprehensively analyzes line speed limit information, track section state, signal interlocking route information and the like to obtain train driving permission, and transmits the train driving permission to a vehicle-mounted subsystem through a train-ground communication channel to ensure the running safety of all trains in the jurisdiction range. The operation control of the TCC device is based on the configuration data in the device, so that the TCC lower computer data becomes the key for influencing the safe and efficient operation of the high-speed railway.

The TCC lower computer data is a binary file which is generated by taking design institute engineering data and scheme design data as input files and can be identified by TCC lower computer equipment. Because the generated TCC lower computer data is a binary file, a verifier cannot directly identify the binary file by naked eyes, and intermediate table data for manual verification is generated while the TCC lower computer data is generated. The intermediate table data is intermediate data corresponding to TCC lower computer data and is directly recognizable by human eyes.

The current verification of TCC lower computer data has the following problems: 1. the verification of binary files really used by the TCC lower computer is replaced by verifying the intermediate table data, so that the TCC lower computer data verification lacks the tightness; 2. the existing verification method is to look up the input document and manually calculate through manual judgment and identification, and due to the fact that functional modules, objects and fields are particularly large, the calculated amount is particularly large, the test period is long, and test missing and test errors are easy to occur.

Disclosure of Invention

The application provides a data verification method and a data verification device, which can solve the technical problems that the manual comparison efficiency is low and the verification cannot be performed on the binary file really used by the TCC lower computer in the data verification process of the TCC lower computer at present, and improve the data verification efficiency and reliability of the TCC lower computer.

The application provides a data verification method, which is applied to verification of TCC (transmission control center) lower computer data of a train control center, and comprises the following steps:

generating a verification case based on preset verification data according to a preset rule;

generating a to-be-verified case based on to-be-verified data according to the preset rule, wherein the to-be-verified data are binary data;

and comparing the data of the verification case with the data of the case to be verified to obtain a verification result.

In an exemplary embodiment, the comparing the data of the verification use case with the data of the to-be-verified use case includes:

and traversing each field of the to-be-verified use case, and comparing the value of the corresponding field of the to-be-verified use case with the value of the field of the to-be-verified use case.

In an exemplary embodiment, the verification result includes a verification conclusion, and the verification conclusion is one of no difference in values of all fields, differences in values of some fields, and differences in values of all fields.

In an exemplary embodiment, the preset rule is any one of the following:

generating a use case based on the specified functional object;

generating a use case based on all the first data;

generating a use case based on all the functional objects;

generating a use case based on the default function object;

the first data is the preset verification data or the data to be verified; the use case is the verification use case or the use case to be verified; each of the function objects includes one or more data structures that implement a predetermined function. According to the data verification method, the use case can be generated according to any one of the preset rules to execute data verification, different requirements of users are met, time spent on verification is saved, and flexibility of data verification is improved.

In an exemplary embodiment, the type of the function object includes any one or more of a speed limit function object, a downgrade function object, a code sending function object, an interface function object, and a special function object;

the generating of the use case based on the specified functional objects, or all the functional objects, or the default functional objects comprises:

and obtaining second data corresponding to the data structure included in the designated functional object, the entire functional objects, or the default functional object from the first data, and assigning values to the data structure included in the designated functional object, the entire functional objects, or the default functional object by using the obtained second data, thereby obtaining the use case. According to the data verification method, the functional object can be designed according to the actual application function of the TCC, the TCC lower computer data corresponding to the functional object can be verified, the combination of the data structure and the application function is achieved, different requirements of users are met, and the flexibility of use case creation and data verification is improved.

In an exemplary embodiment, the data verification method further comprises:

when receiving an operation for modifying a functional object, judging whether an account initiating the operation has a management authority, and if so, allowing the operation; the operation of modifying the functional object comprises the operation of adding, deleting and changing the functional object. For verification of TCC (transmission control center) lower computer data, a functional object is a key element and is not allowed to be modified randomly, in the embodiment of the application, modification of the functional object is limited, and only a user with management authority is allowed to modify, so that the accuracy and the safety of the functional object can be better guaranteed.

In an exemplary embodiment, before comparing the data of the verification use case with the data of the to-be-verified use case, the method further includes:

modifying the verification data or replacing the original verification data with new verification data according to the received instruction to generate a new verification case, and replacing the original verification case with the new verification case; or

Modifying the data to be verified according to the received instruction or replacing the data to be verified by new data to be verified, generating a new case to be verified, and replacing the original case to be verified by the new case to be verified; or

And modifying the verification data or replacing the original verification data with new verification data according to the received instruction to generate a new verification case, replacing the original verification case with the new verification case, modifying the data to be verified or replacing the data to be verified with the new data to be verified to generate a new case to be verified, and replacing the original case to be verified with the new case to be verified. According to the data verification method, the verification data and the data to be verified can be allowed to be modified and used cases can be created, the flexibility of data verification can be improved, and the time of data verification can be effectively shortened.

In an exemplary embodiment, before generating the verification use case based on the predetermined verification data according to the preset rule, the method further includes:

preprocessing the preset verification data, and if the preprocessing result is successful, importing the preset verification data; wherein the preprocessing comprises data checksum base logic computation;

before generating a to-be-verified case based on the to-be-verified data according to the preset rule, the method further includes:

and after the data verification is carried out on the data to be verified, if the data verification result is successful, importing the data to be verified.

In an exemplary embodiment, the preset verification data includes: designing institute engineering data and/or intermediate table data corresponding to the data to be verified; the intermediate table data includes data in a predetermined scene.

In an exemplary embodiment, the generating a verification use case based on predetermined verification data according to a preset rule includes: and generating the verification case based on the data under the preset scene in the design institute engineering data and/or the intermediate table data according to the preset rule. Considering that design shop engineering data is generally data for each implementation site, when data verification is performed by using the design shop engineering data, verification omission may exist for data of a specific scene of some implementation sites. According to the data verification method, the verification case can be generated based on the data in the preset scene in the engineering data of the design institute and/or the data of the intermediate table, and the coverage rate and the reliability of data verification of the TCC lower computer are greatly improved.

The application provides a data verification device, is applied to the verification of train control center TCC next machine data, includes: a processor and a memory; the memory is used for storing programs for performing the data verification method, and the processor is used for reading and executing the programs for performing the data verification method and executing the data verification method of any one of the embodiments.

In summary, according to the data verification method and device provided by the embodiment of the application, a verification case is generated based on predetermined verification data according to a preset rule; generating a case to be verified based on data to be verified according to a preset rule, wherein the data to be verified is binary data; and comparing the data of the verification case with the data of the case to be verified to obtain a verification result. The data verification method of the embodiment of the invention can verify the binary file really used by the TCC lower computer, and improves the reliability of verifying the data of the TCC lower computer.

Additional features and advantages of the present application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the present application. Other advantages of the present application may be realized and attained by the instrumentalities and combinations particularly pointed out in the specification and the drawings.

Drawings

The drawings are intended to provide an understanding of the present disclosure, and are to be considered as forming a part of the specification, and are to be used together with the embodiments of the present disclosure to explain the present disclosure without limiting the present disclosure.

Fig. 1 is a schematic flow chart of a data verification method according to an embodiment of the present application.

Fig. 2 is a schematic structural diagram of a data verification apparatus according to an embodiment of the present application.

Fig. 3 is a platform deployment diagram of a column control lower computer data verification apparatus according to an application example of the present application.

Fig. 4 is a schematic diagram of a flow of column control lower computer data verification according to an application example of the present invention.

Detailed Description

The present application describes embodiments, but the description is illustrative rather than limiting and it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible within the scope of the embodiments described herein. Although many possible combinations of features are shown in the drawings and discussed in the detailed description, many other combinations of the disclosed features are possible. Any feature or element of any embodiment may be used in combination with, or instead of, any other feature or element in any other embodiment, unless expressly limited otherwise.

The present application includes and contemplates combinations of features and elements known to those of ordinary skill in the art. The embodiments, features and elements disclosed in this application may also be combined with any conventional features or elements to form a unique inventive concept as defined by the claims. Any feature or element of any embodiment may also be combined with features or elements from other inventive aspects to form yet another unique inventive aspect, as defined by the claims. Thus, it should be understood that any of the features shown and/or discussed in this application may be implemented alone or in any suitable combination. Accordingly, the embodiments are not limited except as by the appended claims and their equivalents. Furthermore, various modifications and changes may be made within the scope of the appended claims.

Further, in describing representative embodiments, the specification may have presented the method and/or process as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. Other orders of steps are possible as will be understood by those of ordinary skill in the art. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. Further, the claims directed to the method and/or process should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the embodiments of the present application.

Fig. 1 is a schematic flow chart of a data verification method according to an embodiment of the present application. According to the flowchart of fig. 1, the data verification method of the present embodiment includes the steps of:

step S1: and generating a verification case based on preset verification data according to a preset rule.

Step S2: and generating a to-be-verified case based on the to-be-verified data according to a preset rule, wherein the to-be-verified data is binary data.

And step S3: and comparing the data of the verification case with the data of the case to be verified to obtain a verification result.

In an exemplary embodiment, comparing the data of the verification case with the data of the case to be verified includes:

and traversing each field of the case to be verified, and comparing the value of the corresponding field of the case to be verified with the value of the field of the case to be verified.

In an exemplary embodiment, the verification result includes a verification conclusion, and the verification conclusion is one of no difference in values of all fields, differences in values of some fields, and differences in values of all fields. When the difference value of the compared fields is 0 or meets the precision requirement of the corresponding fields, the values of the compared fields can be considered to have no difference. Generally, the system has a precision requirement on the value of the field, and if the difference value of the aligned fields meets the precision requirement of the system on the field, the values of the aligned fields can be considered to have no difference. For example, the precision requirement of the system for the field 1 is 0.01, and if the difference between the value of the field 1 of the verification use case and the value of the field 1 of the use case to be verified is 0.001, the value of the field 1 of the verification use case and the value of the field 1 of the use case to be verified are considered to have no difference. It should be noted that the accuracy requirements of the system for different fields may be different.

In an exemplary embodiment, the verification result further includes a discrepancy report including a discrepancy field identified by color.

In an exemplary embodiment, the preset rule is any one of the following:

generating a use case based on the specified functional object;

generating a use case based on all the first data;

generating a use case based on all the functional objects;

and generating a use case based on the default function object.

In the preset rule, the first data is preset verification data or data to be verified; the use case is a verification use case or a use case to be verified; each functional object includes one or more data structures that implement a predetermined function.

In the following, the functional objects will be described by taking as an example a data structure in which the speed limit functional object includes a transponder, a traffic signal, and an entry, and the data structure may be as follows.

Transponder data structure:

semaphore data structure:

route data structure:

according to the industry service agreement standard, the speed limit of the train is realized by setting a starting point kilometer table and a terminal kilometer table, and when the train passes through the section, the speed of the train is controlled to be within a required range. Therefore, the speed limit function relates to a transponder and a traffic signal at the start and end positions of the route, and information on a station track and a section through which the route passes. The actual speed limit function object may not be limited to the data structure as illustrated above, and the number of the data structures may be more, and the embodiments of the present application are mainly illustrated by the principle as illustrated above, so as to better understand the function object.

In another exemplary embodiment, a functional object may include only one data structure. For example, the speed limit function object may include only a data structure of the speed limit function. As described above, the speed limit function of a train relates to a transponder, a traffic signal, a station track, a section information, etc. of a start point and an end point position of an approach, and thus, a data structure of a speed limit function including all attributes related to the speed limit function can be defined. The following is an example of a data structure of the speed limit function.

Data structure of the speed limit function:

in the example of the data structure of the speed limit function, only some of the attributes contained in the data structure of the speed limit function are shown. The data structure of the actual speed limit function may not be limited to the above example of the data structure of the speed limit function, and the above example of the data structure of the speed limit function is only to better understand the structure of the function object, and the embodiment of the present application does not specifically limit the data structure of the speed limit function.

In an exemplary embodiment, the types of the function objects may include: the system comprises a speed limit function object, a degradation function object, a code sending function object, an interface function object and a special function object. Wherein each of the speed limit function object, the downgrade function object, the code sending function object, the interface function object, and the special function object includes one or more data structures. In another exemplary embodiment, the functional objects may also include extended functional objects, which may be functional objects that the system reserves for subsequent extensions.

In an exemplary embodiment, generating a use case based on the specified functional object, or all of the functional objects, or the default functional object includes: and acquiring second data corresponding to the data structure included in the specified functional object, all the functional objects or the default functional object from the first data, and assigning values to the data structure included in the specified functional object, all the functional objects or the default functional object by using the acquired second data to obtain the use case.

In an exemplary embodiment, when the preset rule is that a use case is generated based on the specified functional object and the obtained verification conclusion is that there is no difference in the values of all the fields, data corresponding to the data structure of the specified functional object may be extracted from the data to be verified, and the extracted data may be stored.

In the actual data verification, it usually takes much time to verify the data to be verified corresponding to all the functional objects or all the data to be verified, however, in many cases, it is actually required to verify the data corresponding to the data structure of one or some functional objects, and in order to save time and improve efficiency, the verification may be performed based on the specified functional objects in the present application. In order to further save storage space, when data verification is performed based on a specified functional object and the obtained verification conclusion is that the values of all fields are not different, the application allows the data corresponding to the data structure of the specified functional object to be extracted from the data to be verified, and only the part of data is loaded into the TCC lower computer.

And taking the specified functional object as a speed-limiting functional object, wherein the speed-limiting functional object only comprises a data structure of a speed-limiting function, and generating the verification case based on the speed-limiting functional object is taken as an example to describe the generation process of the verification case. The generation process of the case to be verified is similar, and the detailed description is omitted in the present application. The method comprises the following specific steps:

firstly, when a preset rule is that a use case is generated based on a specified functional object, the speed-limiting functional object is specified to be used for generating a verification use case, wherein the speed-limiting functional object is one of all functional objects, and the speed-limiting functional object only comprises a data structure of a speed-limiting function.

And secondly, acquiring corresponding data from preset verification data according to a data structure of the speed limit function.

And finally, assigning the data structure of the speed limit function by using the acquired data to obtain a verification case, wherein the verification case comprises the following steps:

in an exemplary embodiment, the values in a use case may be binary or hexadecimal or octal numbers. The present application does not specifically limit the scale used for the numerical values in the use cases. It should be noted that, since the data to be verified is binary data, corresponding value conversion needs to be performed on the data to be verified under the condition that the value in the use case is not binary.

In another exemplary embodiment, assigning values to the data structure is not limited to assigning values to the data structure, but may also include assigning letters, symbols, or the like, or combinations thereof, to the data structure. For example, if the speed limit function object includes a data structure of a transponder, a traffic signal, and an access, the line name LineName, the transponder name balisname, the station name StationName, and the like in the data structure of the transponder are not limited to numbers, and may be letters, a combination of numbers and letters, or other representations. As an example: lineName may be L110C, or LRa, or TRa, etc.

For verification of TCC lower computer data, the functional object is a key element and is not allowed to be modified freely, so that modification of the functional object is limited, and only a user with management authority is allowed to modify the functional object. In one exemplary embodiment, the data verification method further comprises: when receiving an operation for modifying a functional object, judging whether an account initiating the operation has a management authority, and if so, allowing the operation; the operation of modifying the functional object comprises the operation of adding, deleting and changing the functional object.

In an exemplary embodiment, generating the use case based on all the first data includes:

analyzing the first data, acquiring an attribute corresponding to the first data, assigning the first data to a data structure corresponding to the attribute according to the attribute, traversing all the first data until the assignment of all the first data to the corresponding data structure is completed, and obtaining a use case, wherein the first data is preset verification data or data to be verified; the use case is a verification use case or a use case to be verified.

In an exemplary embodiment, the functional object can be backed up, and N versions (N ≧ 1) before the modification of the functional object can be saved, so that when the functional object is damaged or has an error, the functional object can be quickly switched to the backup version or rolled back to the previous version, thereby providing the reliability of the verification device.

In an exemplary embodiment, before comparing the data of the verification case with the data of the case to be verified, the data verification method further includes:

modifying the verification data or replacing the original verification data with new verification data according to the received instruction to generate a new verification use case, and replacing the original verification use case with the new verification use case; or

Modifying the data to be verified according to the received instruction or replacing the data to be verified by the new data to be verified, generating a new case to be verified, and replacing the original case to be verified by the new case to be verified; or

And modifying the verification data or replacing the original verification data with the new verification data according to the received instruction to generate a new verification case, replacing the original verification case with the new verification case, modifying the data to be verified or replacing the data to be verified with the new data to be verified to generate a new case to be verified, and replacing the original case to be verified with the new case to be verified.

In order to save time for data verification and improve flexibility of data verification, modification and replacement of verification data and data to be verified can be supported. Wherein the modification and replacement of the verification data and the modification and replacement of the data to be verified are independent of each other.

For example, if the data verification fails, the data of the original verification data may be modified to correct the error when the verification report of the data verification finds that there is a certain error in the verification data. And then regenerating a new verification case based on the verification data after error correction, and performing data verification again by using the new verification case and the original to-be-verified case. If the original data to be verified is found to be wrong, the data to be verified can be only modified or replaced, then a new case to be verified is generated again based on the new verification data, and the original case and the new case to be verified are used for data verification again. If the original verification data and the original verification data are both wrong, the verification data can be modified or replaced, and the data to be verified can be modified or replaced.

In an exemplary embodiment, before generating a verification use case based on predetermined verification data according to a preset rule, the data verification method further includes:

preprocessing the verification data, and importing the verification data if the preprocessing result is successful; wherein the preprocessing comprises data checksum base logic computation;

before generating a case to be verified based on data to be verified according to a preset rule, the data verification method further comprises the following steps:

and after data verification is carried out on the data to be verified, if the result of the data verification is successful, importing the data to be verified.

preprocessing the verification data, and prompting a failure reason if the preprocessing result is failure; wherein the preprocessing comprises data checksum base logic computation;

and after the data to be verified is subjected to data verification, if the data verification result is failure, prompting a failure reason.

The data verification can include verifying a data path, a folder, a file tab, an attribute title, a cell content format in the tab and the like; the basic logic calculation comprises basic data conversion functions, such as the conversion of a system, the statistics of the same type data in a plurality of tables, the conversion of a time format (such as the unified conversion into a 24-hour time representation mode), and the like.

In an exemplary embodiment, the failure reasons may include a data path error, a folder empty, a file tab inconsistency, an attribute header not meeting requirements, a cell content format error in a tab, and the like. By prompting failure reasons, the method can facilitate users to check defects and make omissions, adapt to perfect document contents, and control the accuracy and integrity of input data.

In an exemplary embodiment, the preset validation data includes design yard engineering data.

In an exemplary embodiment, the preset validation data further includes configuration data. The configuration data may include a database address, a login name, and a password. The configuration data may also be other configuration information, and the embodiment of the present application does not specifically limit the content of the configuration data.

In some scenarios, there are cases where design yard engineering data cannot completely cover the data to be verified. For example, one specific scenario is: when a blocked section such as a station port is calculated, a virtual section may be designed in the running process of a train except for a fixed blocked section appearing in a signal machine table, but whether the virtual section is designed cannot be known from engineering data. The fixed block technology is that a track is divided into a plurality of sections, which are called track sections (also called fixed block sections), signal equipment is installed at the starting point and the end point of each section, and trains run sequentially at certain intervals of the track sections. However, the length of each track section is fixed, so that the interval of train operation cannot be adjusted at will. The virtual block technology in the track traffic is relative to the fixed block technology, the virtual block technology is to virtualize the fixed track section without a fixed spacing distance, and the virtual track section is called a virtual block section. The virtual block technology controls the running interval of the train in a reasonable range through control means such as wireless communication, train positioning technology, automatic overspeed protection and the like, and the technology can greatly improve the running density of the train, reduce the distance of train tracking running and improve the capacity. Is the development direction of rail transit.

Another specific scenario is: for the same equipment, the equipment name in the engineering data provided by the design institute and the equipment name during the specific engineering field construction may be different, and the corresponding equipment name conversion information is not provided in the engineering data. In addition, in the data verification process in the prior art, the device name conversion information cannot be verified, a verification bug exists, once the conversion of the device name is wrong, the project implementation progress can be influenced, and even the operation safety of the train can be seriously influenced.

It should be noted that the predetermined scenario is not limited to the two specific scenarios listed above, and the embodiment of the present application is not limited to this.

In the prior art, the specific data in the predetermined scenario is provided by the project design data, and the design institute engineering data and the project design data are used together as input files to generate the intermediate form data and TCC lower computer data for manual verification.

In order to verify specific data under a predetermined scenario to further improve the reliability of TCC lower computer data verification, in an exemplary embodiment, the preset verification data may include scheme design data.

However, the scheme design data structure and form are arbitrary, there is no fixed structure and form, and the scheme design data provided by different technical departments and different designers are very different in structure and form, for example, the form may include Excel forms, word documents, pictures, etc., which causes great difficulty in generating verification use cases. The specific data in the predetermined scene is also included in the data to be verified and the intermediate table data corresponding to the data to be verified.

In order to verify specific data under a predetermined scenario to further improve reliability of TCC lower computer data verification and improve efficiency of TCC lower computer data verification, in an exemplary embodiment, the preset verification data may include intermediate table data corresponding to data to be verified. In an exemplary embodiment, the intermediate table data is data included in an intermediate table, where the intermediate table may be in the form of Excel, which may include a number of tabs, each of which may include one or more assigned data structures. In an exemplary embodiment, each tab of Excel may include an assigned data structure.

In an exemplary embodiment, the intermediate table data corresponding to the data to be verified may include data in a predetermined scenario. The data in the predetermined scene may include device name conversion information; the equipment name conversion information includes the corresponding relation between the equipment name in the engineering data of the design institute and the equipment name during the field construction.

In an exemplary embodiment, the data under the predetermined scenario may include a virtual interval identifier and/or a virtual interval enable identifier; when the data in the predetermined scene may include the virtual interval identifier, or when the virtual interval identifier is an effective value, or when the virtual interval enable identifier indicates that the virtual interval function is enabled, it indicates that the virtual interval is designed.

In an exemplary embodiment, the intermediate table data corresponding to the data to be verified includes device name conversion information, and/or virtual zone enable identification. The equipment name conversion information comprises the corresponding relation between the equipment name in the engineering data of the design institute and the equipment name during field construction; the virtual interval enable flag may indicate whether the virtual interval function is enabled.

In an exemplary embodiment, generating a verification use case based on predetermined verification data according to a preset rule includes:

and generating a verification case based on the design institute engineering data and/or the data under the preset scene in the intermediate table data according to a preset rule.

In an exemplary embodiment, the types of the function objects further include: the intermediate table predetermines scene function objects.

Compared with the manual inspection of the intermediate table in the prior art, the embodiment of the application can realize the machine verification of the binary file really used by the TCC lower computer, and improves the efficiency and reliability of the data verification of the TCC lower computer. On the basis, the verification of the data of the preset scene in the intermediate table data is added, the data which is not verified in the prior art is also verified, and the coverage rate and the reliability of the data verification of the TCC lower computer are greatly improved on the premise of ensuring the verification efficiency.

In one exemplary embodiment, the data verification method further comprises: and respectively setting and storing corresponding version numbers for the verification data, the verification case, the data to be verified and the verification case.

The verification data, the verification use case, the data to be verified, the verification use case, the functional object, multiple verification results and other data of each version can be stored in the database, and subsequent searching and data maintenance and management are facilitated.

In summary, the data verification method provided by the embodiment of the application realizes machine identification comparison, improves verification efficiency, solves the technical problem that the binary file really used by the TCC lower computer cannot be verified, and improves the reliability of data verification of the TCC lower computer. The verification of the data of the preset scene in the intermediate table data is added, the data which is not verified in the prior art is also verified, and the coverage rate and the reliability of data verification of the TCC lower computer are greatly improved on the premise of ensuring the verification efficiency.

Fig. 2 is a schematic structural diagram of a data verification apparatus according to an embodiment of the present invention. According to the schematic diagram shown in fig. 2, the data verification apparatus of the present embodiment includes a memory 100 and a processor 200. Wherein:

a memory 100 for storing a program for performing a data verification method;

the processor 200, which is used for reading and executing the program for performing the data verification method, performs the following operations:

generating a case to be verified based on data to be verified according to a preset rule, wherein the data to be verified is binary data;

In an exemplary embodiment, comparing the data of the verified case with the data of the to-be-verified case includes:

In an exemplary embodiment, the preset rule is any one of the following:

generating a use case based on the specified functional object;

generating a use case based on all the first data;

generating a use case based on all the functional objects;

and generating a use case based on the default function object.

Examples of the function object may refer to the speed limit function object in the above data method embodiment, and will not be described repeatedly here.

In an exemplary embodiment, the types of the function objects may include: a speed limit function object, a downgrade function object, a code sending function object, an interface function object and a special function object. Wherein each of the speed limit function object, the downgrade function object, the code sending function object, the interface function object, and the special function object includes one or more data structures. In another exemplary embodiment, the functional objects may also include extended functional objects, which may be functional objects that the system reserves for subsequent extensions.

In an exemplary embodiment, when a preset rule is that a use case is generated based on a specified functional object and the obtained verification conclusion is that there is no difference in the values of all the fields, data corresponding to the data structure of the specified functional object may be extracted from the data to be verified, and the extracted data may be stored.

In the actual data verification, it usually takes much time to verify the data to be verified corresponding to all the functional objects or all the data to be verified, however, in many cases, it is actually required to verify the data corresponding to the data structure of one or some functional objects, and in order to save time and improve efficiency, the verification can be performed based on the specified functional objects. In order to further save storage space, when data verification is performed based on a specified functional object and the obtained verification conclusion is that the values of all fields are not different, the application allows the data corresponding to the data structure of the specified functional object to be extracted from the data to be verified, and only the part of the data is loaded into the TCC lower computer.

Regarding the specific process of generating the verification use case based on the function object, reference may be made to the specific example described in the above data verification method embodiment, and the description is not repeated here. The generation process of the to-be-verified use case is similar, and the generation process of the to-be-verified use case is not described in detail in the application.

In another exemplary embodiment, assigning values to the data structure is not limited to assigning values to the data structure, but may also include assigning letters, symbols, etc., or combinations thereof to the data structure. For example, if the speed limit function object includes a data structure of a transponder, a traffic signal, and an access, the line name LineName, the transponder name balisname, the station name StationName, and the like in the data structure of the transponder are not limited to numbers, and may be letters, a combination of numbers and letters, or other representations. As an example: lineName may be L110C, or LRa, or TRa, etc.

For verification of TCC lower computer data, the functional objects are key elements and are not allowed to be modified freely, so that modification of the functional objects is limited, and only users with management authority are allowed to modify the functional objects. In one exemplary embodiment, the data verification method further comprises: when receiving an operation for modifying a functional object, judging whether an account initiating the operation has a management authority, and if so, allowing the operation; the operation of modifying the functional object comprises the operation of adding, deleting and changing the functional object.

In an exemplary embodiment, the processor 200 reads and executes a program for performing the data verification method, and further performs the following operations:

before comparing the data of the verification case with the data of the case to be verified,

modifying the verification data or replacing the original verification data with the new verification data according to the received instruction to generate a new verification case, and replacing the original verification case with the new verification case; or

For example, if the data verification fails, the data of the original verification data may be modified to correct the error when the verification report of the data verification finds that there is a certain error in the verification data. And then regenerating a new verification case based on the verification data after error correction, and performing data verification again by using the new verification case and the original to-be-verified case. Similarly, if the original data to be verified is found to be wrong, the data to be verified can be only modified or replaced, then a new case to be verified is regenerated based on the new verification data, and the original case and the new case to be verified are utilized to perform data verification again. If the original verification data and the original verification data are both found to be wrong, the verification data can be modified or replaced, and the data to be verified can be modified or replaced.

In an exemplary embodiment, the processor 200 reads a program for executing the data verification method, and further performs the following operations:

preprocessing the verification data before generating a verification case based on the preset verification data according to a preset rule, and importing the verification data if the preprocessing result is successful; wherein the preprocessing comprises data checksum base logic calculation;

before generating a case to be verified based on data to be verified according to a preset rule, after the data to be verified is subjected to data verification, if the result of the data verification is successful, importing the data to be verified.

preprocessing the verification data before generating a verification case based on the preset verification data according to a preset rule, and prompting a failure reason if the preprocessing result is failure; wherein the preprocessing comprises data checksum base logic computation;

before generating a case to be verified based on data to be verified according to a preset rule, after the data to be verified is subjected to data verification, if the result of the data verification is failure, prompting a failure reason.

In an exemplary embodiment, the failure reasons may include a data path error, a folder empty, a file tab inconsistency, an attribute header not meeting requirements, a cell content format error in a tab, and the like. By prompting the failure reason, the method can facilitate the user to check the defects and the omission, improve the document content in an adaptive manner, and control the accuracy and the integrity of the input data.

In some scenarios, there are cases where design yard engineering data cannot completely cover the data to be verified. For example, one specific scenario is: when a blocked section such as a station port is calculated, a virtual section may be designed in the running process of a train except for a fixed blocked section appearing in a signal machine table, and whether the virtual section is designed cannot be known from engineering data. The fixed block technology is to divide a track into a plurality of sections, which are called track sections (also called fixed block sections), wherein signal equipment is installed at the starting point and the ending point of each section, and trains run sequentially at certain intervals of the track sections. The length of each track section is fixed, however, so that the interval of train operation cannot be adjusted at will. The virtual block technology in the track traffic is relative to the fixed block technology, the virtual block technology is to virtualize the fixed track section without a fixed spacing distance, and the virtual track section is called a virtual block section. The virtual block technology controls the running interval of the train in a reasonable range through control means such as wireless communication, train positioning technology, automatic overspeed protection and the like, and the technology can greatly improve the running density of the train, reduce the distance of train tracking running and improve the capacity. Is the development direction of rail transit.

In the prior art, the specific data in the predetermined scenario is provided by the project design data, and the design institute engineering data and the project design data are used as input files together to generate intermediate form data and TCC lower computer data for manual verification.

In order to verify specific data under a predetermined scenario to further improve reliability of TCC lower computer data verification and improve efficiency of TCC lower computer data verification, in an exemplary embodiment, the preset verification data may include intermediate table data corresponding to data to be verified. The intermediate table data includes one or more assigned data structures. In an exemplary embodiment, the intermediate table data is data included in an intermediate table, where the intermediate table may be in the form of Excel, which may include a number of tabs, each of which may include one or more assigned data structures. In an exemplary embodiment, each tab of Excel may include an assigned data structure.

In an exemplary embodiment, the intermediate table data corresponding to the data to be verified includes device name conversion information, and/or virtual partition enable identification, and the like. The equipment name conversion information comprises the corresponding relation between the equipment name in the engineering data of the design institute and the equipment name during field construction; the virtual interval enable flag may indicate whether the virtual interval function is enabled.

and according to a preset rule, generating a verification case based on the data under a preset scene in the engineering data of the design institute and/or the intermediate table data.

In an exemplary embodiment, the types of the function objects further include: the intermediate table predefines scene function objects.

Compared with the prior art that the intermediate table is manually checked, the embodiment of the application can realize the machine verification of the binary file really used by the TCC lower computer, and improves the efficiency and reliability of the data verification of the TCC lower computer. On the basis, the verification of the data of the preset scene in the intermediate table data is added, the data which is not verified in the prior art is also verified, and the coverage rate and the reliability of the data verification of the TCC lower computer are greatly improved on the premise of ensuring the verification efficiency.

and respectively setting and storing corresponding version numbers for the verification data, the verification case, the data to be verified and the verification case.

In summary, the data verification device provided by the embodiment of the application realizes machine identification comparison, improves verification efficiency, solves the technical problem that the binary file really used by the TCC lower computer cannot be verified, and improves the reliability of data verification of the TCC lower computer. The verification of the data of the preset scene in the intermediate table data is added, the data which is not verified in the prior art is also verified, and the coverage rate and the reliability of data verification of the TCC lower computer are greatly improved on the premise of ensuring the verification efficiency.

The data verification method is further described below by using a specific application example.

Fig. 3 is a platform deployment diagram of a column control lower computer data verification apparatus according to an application example of the present application. The frame module in fig. 3 comprises a data validation device according to an embodiment of the present application. The data verification device can be deployed in a Windows environment, an environment above Win7 is selected, the environment is installed, net4.8 (or above) is selected, and a database can be selected to be an Sql Server 2008R 2 (or above) environment so as to ensure storage and management of various version data. The verification data and the data to be verified can be stored in separate folders after being imported, and different types of data in the verification data can be placed in different folder directories so as to facilitate data management. The data verification device can be deployed on a single computer or can be deployed on a plurality of computer devices connected with each other in a distributed manner.

Fig. 4 is a schematic diagram of a flow of column control lower computer data verification according to an application example of the present invention. As shown in fig. 4, this application example mainly includes the following steps 1 to 8.

Step 1: and starting the data verification of the column control lower computer.

Step 2: and preparing data, wherein the data comprises configuration data, design institute engineering data, data to be verified and intermediate table data.

And step 3: and checking the data, and screening and checking the engineering data, the configuration data, the data to be verified and the intermediate table data. The screening verification here includes, but is not limited to, verifying data paths, folders, file tabs, attribute titles, and cell content formats in the tabs. If the data checking result is that the data passes, executing a step four; if the data verification flow is abnormal, the user is prompted to correct the data until the data verification result is passed or the user exits the data verification flow.

And 4, step 4: and importing the various data until all the data are imported.

And 5: and generating a verification use case based on the verification data and a to-be-verified use case based on the to-be-verified data according to rules set by a user until all use cases are generated.

Step 6: and comparing the data of the verification case with the data of the case to be verified until the data comparison of all cases is completed.

And 7: and viewing or deriving a verification result, wherein the verification result comprises a verification conclusion and a difference report, and the difference report comprises a difference field identified by color.

And 8: and finishing the data verification of the column control lower computer.

It should be noted that, in the above application example, in the data preparation and data import stage, the verification data and the data to be verified are performed simultaneously, and in the case generation stage, the verification case and the case to be verified are also performed simultaneously, and this data verification flow is only one example of the data verification method of the present invention. The preparation, checking and importing of the verification data and the data to be verified may be independent of each other, and the order of execution thereof is not limited by the embodiments of the present application. Similarly, the generation of the verification case and the to-be-verified case are also independent of each other, and the order of execution is not limited in the embodiments of the present application.

It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.

While the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A data verification method is applied to verification of TCC (transmission control center) lower computer data of a train control center, and comprises the following steps:

2. The data verification method according to claim 1, wherein the comparing the data of the verification use case with the data of the use case to be verified comprises:

3. The data verification method according to claim 2, wherein the verification result includes a verification conclusion, and the verification conclusion is one of no difference in values of all fields, differences in values of some fields, and differences in values of all fields.

4. The data validation method of claim 1, wherein the preset rule is any one of the following:

generating a use case based on the specified functional object;

generating a use case based on all the first data;

generating a use case based on all the functional objects;

generating a use case based on the default function object;

wherein the first data is the predetermined verification data or the data to be verified; the use case is the verification use case or the to-be-verified use case; each of the function objects includes one or more data structures that implement a predetermined function.

5. The data verification method according to claim 4, wherein the type of the function object comprises any one or more of a speed limit function object, a downgrade function object, a code sending function object, an interface function object and a special function object;

and obtaining second data corresponding to a data structure included in the designated functional object, the entire functional objects, or the default functional object from the first data, and assigning values to the data structure included in the designated functional object, the entire functional objects, or the default functional object by using the obtained second data, thereby obtaining the use case.

6. The data validation method of claim 5, the method further comprising:

when receiving an operation for modifying a functional object, judging whether an account initiating the operation has a management authority, and if so, allowing the operation; the operation of modifying the functional object comprises the operation of adding, deleting and changing the functional object.

7. The data verification method according to claim 1, wherein before comparing the data of the verification use case with the data of the use case to be verified, the method further comprises:

And modifying the verification data or replacing the original verification data with new verification data according to the received instruction to generate a new verification case, replacing the original verification case with the new verification case, modifying the data to be verified or replacing the data to be verified with the new data to be verified to generate a new case to be verified, and replacing the original case to be verified with the new case to be verified.

8. The data verification method according to claim 1, wherein before generating the verification use case based on the predetermined verification data according to the preset rule, the method further comprises:

preprocessing the preset verification data, and if the preprocessing result is successful, importing the preset verification data; wherein the preprocessing comprises a data checksum predetermined logical calculation;

9. The data verification method of claim 1, the preset verification data comprising: designing institute engineering data and/or intermediate table data corresponding to the data to be verified; the intermediate table data includes data in a predetermined scene.

10. The data verification method according to claim 9, wherein the generating a verification case based on predetermined verification data according to a preset rule comprises:

and generating the verification case based on the data under the preset scene in the design institute engineering data and/or the intermediate table data according to the preset rule.

11. A data verification device is applied to verification of TCC (transmission control center) lower computer data of a train control center, and comprises the following steps: a processor and a memory;

the method is characterized in that:

the memory is used for storing a program for performing the data verification method, and the processor is used for reading and executing the program for performing the data verification method to perform the data verification method according to claims 1-10.