Method and device for checking distribution information

Abstract

The present disclosure provides a method and device for verifying distributed information. The method includes: obtaining target configuration file information; verifying whether the information byte length is equal to the configuration file definition byte length; if the information byte length is equal to the configuration file definition byte length, verifying the sender code to determine whether the sender is a protocol-defined user; if the sender is a protocol-defined user, verifying the system code check code to determine whether the system sending the target configuration file is a simulation test system; if the system sending the target configuration file is a simulation test system, verifying the event code to determine whether the event is a protocol-defined event; if the event is a protocol-defined event, verifying the sub-event code to determine whether the sub-event is a protocol-defined sub-event; if the sub-event is a protocol-defined sub-event, determining that the sender is a distribution channel. The method disclosed herein can solve the problem of being unable to verify distributed information of simulation test systems used in military training.

Description

Technical Field

[0001] The present disclosure relates to the technical field of military simulation training, and in particular to a method and device for checking distribution information. Background Art

[0002] The current problem is that the distributed information of the simulation test system used in military training cannot be checked, so it is impossible to ensure that the information is valid. Summary of the Invention

[0003] The purpose of the present disclosure is to overcome the shortcomings of the existing technology and provide a method and device for checking distribution information. The method for checking distribution information can solve the problem that the distribution information of the simulation test system used in military training cannot be checked, thereby failing to ensure the validity of the information.

[0004] According to a first aspect of an embodiment of the present disclosure, a method for checking distribution information is provided, the method comprising:

[0005] Obtain target profile information; wherein the target profile information includes information byte length, sender code, system code check code, event code and sub-event code;

[0006] Check whether the byte length of the information is equal to the byte length defined in the configuration file;

[0007] When the byte length of the information is equal to the byte length defined in the configuration file, checking the sender code to determine whether the sender is a user defined in the protocol;

[0008] When the sender is a protocol definition user, checking the system code check code to determine whether the system sending the target configuration file is a simulation test system;

[0009] When the system sending the target configuration file is a simulation test system, checking the event code to determine whether the event is a protocol-defined event;

[0010] When the event is a protocol-defined event, checking the sub-event code to determine whether the sub-event is a protocol-defined sub-event;

[0011] When the sub-event is a protocol-defined sub-event, a channel is distributed to the sender.

[0012] In one embodiment, the method further comprises:

[0013] The method further comprises:

[0014] When the byte length of the information is not equal to the byte length defined in the configuration file, an error message is sent, wherein the error message carries error type information;

[0015] When the sender is not a user defined by the protocol, an error message is sent, and the error message carries error type information;

[0016] When the system sending the target configuration file is not a simulation test system, an error message is sent, wherein the error message carries error type information;

[0017] When the event is not a protocol-defined event, an error message is sent, and the error message carries error type information;

[0018] When the sub-event is not a protocol-defined sub-event, an error message is sent, and the error message carries error type information.

[0019] In one embodiment, the method further comprises:

[0020] Counting the number of error messages and error type information;

[0021] Determining the error frequency of the sender information according to the number of the error reporting information and the error type information;

[0022] An analysis report of the sender is generated according to the error frequency of the sender information, and the analysis report is used by the sender to correct errors.

[0023] In one embodiment, checking the sender code to determine whether the sender is a user defined in the protocol includes:

[0024] Check whether the first N bits of the information byte are within the definition of the target configuration file; where N is a natural number and is not equal to 0;

[0025] If the first N bits of the information byte are within the definition of the target configuration file, it is determined that the sender is a protocol-defined user;

[0026] If the first N bits of the information byte are not within the definition of the target configuration file, it is determined that the sender is not a protocol definition user.

[0027] In one embodiment, checking the system code verification code to determine whether the system sending the target configuration file is a simulation test system includes:

[0028] Check whether the N+Xth bit code of the information byte is equal to the target configuration file definition code; where X is a natural number and X>N;

[0029] If the N+Xth bit code of the information byte is equal to the target profile definition code, it is determined that the system sending the target profile is a simulation test system;

[0030] If the N+Xth bit code of the information byte is not equal to the target profile definition code, it is determined that the system sending the target profile is not a simulation test system.

[0031] In one embodiment, checking the event code to determine whether the event is a protocol-defined event includes:

[0032] Check whether the N+X+Yth bit code of the information byte is within the definition of the target configuration file; where Y is a natural number and Y>X;

[0033] If the N+X+Yth bit code of the information byte is within the definition of the target configuration file, it is determined that the event is a protocol-defined event;

[0034] If the N+X+Yth bit code of the information byte is not within the definition of the target configuration file, it is determined that the event is not a protocol-defined event.

[0035] In one embodiment, checking the sub-event code to determine whether the sub-event is a protocol-defined sub-event includes:

[0036] Check whether the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file; where Z is a natural number and Z>Y;

[0037] If the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file, then the sub-event is determined to be a protocol-defined sub-event;

[0038] If the N+X+Y+Zth bit code of the information byte is not within the definition of the target configuration file, it is determined that the sub-event is not a protocol-defined sub-event.

[0039] In one embodiment, the method further comprises:

[0040] If the event code length is less than the defined code length, fill in the position before the event code;

[0041] If the sub-event code length is less than the defined code length, fill in the space before the sub-event code.

[0042] According to a second aspect of an embodiment of the present disclosure, there is provided a device for verifying distribution information, the device comprising:

[0043] An acquisition module is configured to acquire target configuration file information, wherein the target configuration file information includes information byte length, sender code, system code check code, event code, and sub-event code;

[0044] A first checking module checks whether the byte length of the information is equal to the byte length defined in the configuration file;

[0045] A second checking module checks the sender code to determine whether the sender is a user defined in the protocol when the byte length of the information is equal to the byte length defined in the configuration file;

[0046] A third checking module checks the system code check code to determine whether the system sending the target configuration file is a simulation test system when the sender is a protocol definition user;

[0047] A fourth checking module, when the system sending the target configuration file is a simulation test system, checks the event code to determine whether the event is a protocol-defined event;

[0048] a fifth checking module, which checks the sub-event code to determine whether the sub-event is a protocol-defined sub-event when the event is a protocol-defined event;

[0049] The distribution module distributes a channel for the sender when the sub-event is a protocol-defined sub-event.

[0050] In one embodiment, the apparatus further comprises:

[0051] A statistics module, for counting the number of error messages and error type information;

[0052] a determination module, determining an error frequency of sender information according to the error information and the number of error type information;

[0053] A generating module generates an analysis report of the sender according to the error frequency of the sender information, wherein the analysis report is used by the sender to correct the error.

[0054] The present disclosure provides a method for checking distribution information, which obtains target configuration file information, which includes information byte length, sender code, system code check code, event code and sub-event code, and checks whether the information byte length is equal to the configuration file definition byte length. When the information byte length is equal to the configuration file definition byte length, the sender code is further checked to determine whether the sender is a protocol-defined user. When the sender is a protocol-defined user, the system code check code is checked to determine whether the system sending the target configuration file is a simulation test system. When the system sending the target configuration file is a simulation test system, the event code is checked to determine whether the event is a protocol-defined event. When the event is a protocol-defined event, the sub-event code is checked to determine whether the sub-event is a protocol-defined sub-event. When the sub-event is a protocol-defined sub-event, it is a sender distribution channel, so as to solve the problem that the distribution information of the simulation test system used in military training cannot be checked, thereby failing to ensure the validity of the information. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0056] Figure 1 A flowchart of a method for checking distribution information provided in an embodiment of the present disclosure.

[0057] Figure 2 A flowchart of a method for checking distribution information provided in an embodiment of the present disclosure.

[0058] Figure 3 This is an architectural diagram of a distribution information verification device provided in an embodiment of the present disclosure.

[0059] Figure 4 This is an architectural diagram of a distribution information verification device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0060] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0061] Figure 1 This is a flow chart of a method for checking distribution information provided by an embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0062] Step 101: Obtain target configuration file information;

[0063] In this step, the target profile information includes information byte length, sender code, system code check code, event code and sub-event code;

[0064] Step 102: Check whether the byte length of the information is equal to the byte length defined in the configuration file;

[0065] In this step, if the information byte length is equal to the byte length defined in the configuration file, the process proceeds to step 103; if the information byte length is not equal to the byte length defined in the configuration file, an error is reported and the error type is fed back.

[0066] Step 103: When the byte length of the information is equal to the byte length defined in the configuration file, check the sender code to determine whether the sender is a user defined in the protocol;

[0067] In one embodiment, checking the sender code to determine whether the sender is a user defined in the protocol includes:

[0068] Check whether the first N bits of the information byte are within the definition of the target configuration file; where N is a natural number and is not equal to 0;

[0069] If the first N bits of the information byte are within the definition of the target configuration file, it is determined that the sender is a protocol-defined user;

[0070] If the first N bits of the information byte are not within the definition of the target configuration file, it is determined that the sender is not a protocol definition user.

[0071] In this embodiment, if the first N bits of the information byte code are within the range defined in the configuration file, the process proceeds to step 104; if the first N bits of the information byte code are not within the range defined in the configuration file, an error is reported and the error type is fed back.

[0072] Step 104: When the sender is a protocol definition user, check the system code verification code to determine whether the system sending the target configuration file is a simulation test system;

[0073] In one embodiment, checking the system code verification code to determine whether the system sending the target configuration file is a simulation test system includes:

[0074] Check whether the N+Xth bit code of the information byte is equal to the target configuration file definition code; where X is a natural number and X>N;

[0075] If the N+Xth bit code of the information byte is equal to the target profile definition code, it is determined that the system sending the target profile is a simulation test system;

[0076] If the N+Xth bit code of the information byte is not equal to the target profile definition code, it is determined that the system sending the target profile is not a simulation test system.

[0077] In this embodiment, the system code check code is checked to determine whether the target system of the information is a simulation test system, that is, whether the N+Xth bit code of the information byte is equal to the configuration file definition code. If it is determined that the N+Xth bit code of the information byte is equal to the target configuration file definition code, it is determined that the system of the target configuration file is a simulation test system, and the process proceeds to step 105. If it is determined that the N+Xth bit code of the information byte is not equal to the target configuration file definition code, it is determined that the system of the target configuration file is not a simulation test system, and an error is reported and the error type is fed back.

[0078] Step 105: When the system sending the target configuration file is a simulation test system, check the event code to determine whether the event is a protocol-defined event;

[0079] In one embodiment, checking the event code to determine whether the event is a protocol-defined event includes:

[0080] Check whether the N+X+Yth bit code of the information byte is within the definition of the target configuration file; where Y is a natural number and Y>X;

[0081] If the N+X+Yth bit code of the information byte is within the definition of the target configuration file, it is determined that the event is a protocol-defined event;

[0082] If the N+X+Yth bit code of the information byte is not within the definition of the target configuration file, it is determined that the event is not a protocol-defined event.

[0083] In this embodiment, the event code is checked to determine whether the event is a protocol-defined event, that is, whether the N+X+Y-th bit code of the information byte is within the range defined by the configuration file. If the N+X+Y-th bit code of the information byte is within the definition of the target configuration file, the event is determined to be a protocol-defined event. If the N+X+Y-th bit code of the information byte is not within the definition of the target configuration file, the event is determined to be not a protocol-defined event, and an error is reported and the error type is fed back.

[0084] Step 106: If the event is a protocol-defined event, check the sub-event code to determine whether the sub-event is a protocol-defined sub-event;

[0085] In one embodiment, checking the sub-event code to determine whether the sub-event is a protocol-defined sub-event includes:

[0086] Check whether the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file; where Z is a natural number and Z>Y;

[0087] If the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file, then the sub-event is determined to be a protocol-defined sub-event;

[0088] If the N+X+Y+Zth bit code of the information byte is not within the definition of the target configuration file, it is determined that the sub-event is not a protocol-defined sub-event.

[0089] In this embodiment, the sub-event code is checked to determine whether the sub-event belongs to a protocol-defined sub-event, that is, whether the N+X+Y+Z-th bit of the information byte is within the configuration file definition range. If the N+X+Y+Z-th bit of the information byte is within the target configuration file definition, the sub-event is determined to be a protocol-defined sub-event. If the N+X+Y+Z-th bit of the information byte is not within the target configuration file definition, the sub-event is determined not to be a protocol-defined sub-event, and an error is reported and the error type is fed back.

[0090] Step 107: When the sub-event is a protocol-defined sub-event, a distribution channel is provided for the sender.

[0091] In this step, if the information meets the verification results, it will enter the distribution channel and be recorded for record.

[0092] The present disclosure provides a method for checking distribution information, which obtains target configuration file information, which includes information byte length, sender code, system code check code, event code and sub-event code, and checks whether the information byte length is equal to the configuration file definition byte length. When the information byte length is equal to the configuration file definition byte length, the sender code is further checked to determine whether the sender is a protocol-defined user. When the sender is a protocol-defined user, the system code check code is checked to determine whether the system sending the target configuration file is a simulation test system. When the system sending the target configuration file is a simulation test system, the event code is checked to determine whether the event is a protocol-defined event. When the event is a protocol-defined event, the sub-event code is checked to determine whether the sub-event is a protocol-defined sub-event. When the sub-event is a protocol-defined sub-event, it is a sender distribution channel, so as to solve the problem that the distribution information of the simulation test system used in military training cannot be checked, thereby failing to ensure the validity of the information.

[0093] Alternatively, as Figure 2 As shown, the method further includes:

[0094] Step 201: Count the number of error messages and error type information;

[0095] Step 202: Determine the error frequency of the sender information based on the error information and the number of error type information;

[0096] Step 203: Generate an analysis report of the sender based on the error frequency of the sender information, and use the analysis report for the sender to correct errors.

[0097] In this embodiment, the number of error messages and erroneous type messages is counted, and the error frequency of the sender's information is determined based on the number of error messages and erroneous type messages. Then, an analysis report of the sender is generated based on the error frequency of the sender's information to facilitate the sender to correct the error.

[0098] Optionally, the method further includes:

[0099] If the event code length is less than the defined code length, fill in the position before the event code;

[0100] If the sub-event code length is less than the defined code length, fill in the space before the sub-event code.

[0101] In this embodiment, when the event code length is less than the defined code length, the event code is automatically padded. When the sub-event code length is less than the defined code length, the sub-event code is automatically padded, and the padded position can be used with 0 or a custom character. This embodiment automatically corrects simple bit errors through error correction, avoiding resource waste and reduced efficiency caused by repeated information transmission.

[0102] Figure 3 This is a diagram of the architecture of a distributed information inspection device provided by an embodiment of the present disclosure. Figure 3 As shown, the inspection device for distribution information includes: an acquisition module 301, a first inspection module 302, a second inspection module 303, a third inspection module 304, a fourth inspection module 305, a fifth inspection module 306 and a distribution module 307; wherein the acquisition module 301 is used to obtain target configuration file information; wherein the target configuration file information includes information byte length, sender code, system code check code, event code and sub-event code; the first inspection module 302 is used to check whether the information byte length is equal to the configuration file definition byte length; the second inspection module 303 is used to check whether the information byte length is equal to the configuration file definition byte length when the information byte length is equal to the configuration file definition byte length. Check the sender code to determine whether the sender is a protocol-defined user; the third checking module 304 is used to check the system code verification code when the sender is a protocol-defined user to determine whether the system sending the target configuration file is a simulation test system; the fourth checking module 305 is used to check the event code when the system sending the target configuration file is a simulation test system to determine whether the event is a protocol-defined event; the fifth checking module 306 is used to check the sub-event code when the event is a protocol-defined event to determine whether the sub-event is a protocol-defined sub-event; the distribution module 707 is used to distribute the channel for the sender when the sub-event is a protocol-defined sub-event.

[0103] Figure 4 This is a diagram of the architecture of a distributed information inspection device provided by an embodiment of the present disclosure. Figure 4As shown, the inspection device for the distribution information includes: an acquisition module 401, a first inspection module 402, a second inspection module 403, a third inspection module 404, a fourth inspection module 405, a fifth inspection module 406 and a distribution module 407, a statistics module 408, a determination module 409 and a generation module 4010; wherein, the statistics module 408 is used to count the number of the error messages and the error type information; the determination module 409 is used to determine the error frequency of the sender information based on the number of the error messages and the error type information; the generation module 4010 is used to generate an analysis report of the sender based on the error frequency of the sender information, and the analysis report is used for the sender to correct the error.

[0104] Those skilled in the art will appreciate that all or part of the steps in the above-described method embodiments can be implemented using hardware associated with program instructions. The aforementioned program can be pre-stored in a computer-readable storage medium. When executed, the program performs the steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0105] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the disclosure herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true spirit of the present disclosure being indicated by the following claims.

[0106] It should be understood that the present disclosure is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing therefrom. The present disclosure is limited only by the appended claims.

Claims

1. A method for checking distributed information, characterized in that: The method comprises: Obtain target profile information; wherein the target profile information includes information byte length, sender code, system code check code, event code and sub-event code; Check whether the byte length of the information is equal to the byte length defined in the configuration file; When the byte length of the information is equal to the byte length defined in the configuration file, checking the sender code to determine whether the sender is a user defined in the protocol; When the sender is a protocol definition user, checking the system code check code to determine whether the system sending the target configuration file is a simulation test system; When the system sending the target configuration file is a simulation test system, checking the event code to determine whether the event is a protocol-defined event; When the event is a protocol-defined event, checking the sub-event code to determine whether the sub-event is a protocol-defined sub-event; When the sub-event is a protocol-defined sub-event, a distribution channel is provided for the sender; When the byte length of the information is not equal to the byte length defined in the configuration file, an error message is sent, wherein the error message carries error type information; When the sender is not a user defined by the protocol, an error message is sent, and the error message carries error type information; When the system sending the target configuration file is not a simulation test system, an error message is sent, wherein the error message carries error type information; When the event is not a protocol-defined event, an error message is sent, and the error message carries error type information; When the sub-event is not a protocol-defined sub-event, an error message is sent, and the error message carries error type information.

2. The method according to claim 1, characterized in that The method further comprises: Counting the number of error messages and error type information; Determining the error frequency of the sender information according to the number of the error reporting information and the error type information; An analysis report of the sender is generated according to the error frequency of the sender information, and the analysis report is used by the sender to correct errors.

3. The method according to claim 1 or 2, characterized in that The checking of the sender code to determine whether the sender is a user defined in the protocol includes: Check whether the first N bits of the information byte are within the definition of the target configuration file; where N is a natural number and is not equal to 0; If the first N bits of the information byte are within the definition of the target configuration file, it is determined that the sender is a protocol-defined user; If the first N bits of the information byte are not within the definition of the target configuration file, it is determined that the sender is not a protocol definition user.

4. The method according to claim 3, characterized in that The checking of the system code verification code to determine whether the system sending the target configuration file is a simulation test system includes: Check whether the N+Xth bit code of the information byte is equal to the target configuration file definition code; where X is a natural number and X>N; If the N+Xth bit code of the information byte is equal to the target profile definition code, it is determined that the system sending the target profile is a simulation test system; If the N+Xth bit code of the information byte is not equal to the target profile definition code, it is determined that the system sending the target profile is not a simulation test system.

5. The method according to claim 4, characterized in that Checking the event code to determine whether the event is a protocol-defined event includes: Check whether the N+X+Yth bit code of the information byte is within the definition of the target configuration file; where Y is a natural number and Y>X; If the N+X+Yth bit code of the information byte is within the definition of the target configuration file, it is determined that the event is a protocol-defined event; If the N+X+Yth bit code of the information byte is not within the definition of the target configuration file, it is determined that the event is not a protocol-defined event.

6. The method according to claim 5, characterized in that Checking the sub-event code to determine whether the sub-event is a protocol-defined sub-event includes: Check whether the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file; where Z is a natural number and Z>Y; If the N+X+Y+Zth bit code of the information byte is within the definition of the target configuration file, then the sub-event is determined to be a protocol-defined sub-event; If the N+X+Y+Zth bit code of the information byte is not within the definition of the target configuration file, it is determined that the sub-event is not a protocol-defined sub-event.

7. The method according to claim 6, characterized in that The method further comprises: If the event code length is less than the defined code length, fill in the space before the event code.

8. A device for checking distribution information, characterized in that: The device comprises: An acquisition module is configured to acquire target configuration file information, wherein the target configuration file information includes information byte length, sender code, system code check code, event code, and sub-event code; A first checking module checks whether the byte length of the information is equal to the byte length defined in the configuration file; A second checking module checks the sender code to determine whether the sender is a user defined in the protocol when the byte length of the information is equal to the byte length defined in the configuration file; A third checking module checks the system code check code to determine whether the system sending the target configuration file is a simulation test system when the sender is a protocol definition user; A fourth checking module, when the system sending the target configuration file is a simulation test system, checks the event code to determine whether the event is a protocol-defined event; a fifth checking module, which checks the sub-event code to determine whether the sub-event is a protocol-defined sub-event when the event is a protocol-defined event; a distribution module, which distributes a channel for the sender when the sub-event is a protocol-defined sub-event; a statistics module, which sends an error message when the event is not a protocol-defined event, wherein the error message carries error type information; and counts the number of the error messages and the error type information; a determination module, determining an error frequency of sender information according to the error information and the number of error type information; A generating module generates an analysis report of the sender according to the error frequency of the sender information, wherein the analysis report is used by the sender to correct the error.

Images