CN116312098A - Method and device for checking distributed information - Google Patents

Abstract

The present disclosure provides a method and apparatus for inspecting distributed information. The method comprises the following steps: acquiring target configuration file information; checking whether the information byte length is equal to the configuration file definition byte length; checking the sender code to determine if the sender is a protocol definition user when the information byte length is equal to the profile definition byte length; when the sender is a protocol definition user, checking a system code check code, and determining whether a system for sending the target configuration file is a simulation test system or not; 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 definition event; when the event is a protocol definition event, examining the sub-event code to determine whether the sub-event is a protocol definition sub-event; when the sub-event is a protocol defined sub-event, then a channel is distributed for the sender. The method can solve the problem that the distributed information of the simulation test system used in military training cannot be checked.

Description

Inspection method and device for distributing information

technical field

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

Background technique

The data link is used in combat, and the biggest change it brings is the real-time realization of collective perception and shared data. To put it simply, it is a link exchange and distribution system, which can transmit various tactical data in real time, automatically and confidentially in a unified format standard and agreement, and form a real-time, accurate and complete combat situation map, so that no matter where the commander is The command position can know oneself and the enemy, follow orders, and achieve a high degree of synchronization of combat operations.

Military data links transmit tactical information over wired and wireless channels. Wired channels, such as optical fibers and cables, have high transmission reliability and effectiveness, but it takes a long time to establish communication, and lines need to be erected, and their mobility and resistance to destruction are not as good as wireless channels. The wireless channel is often referred to as the frequency band. At present, the working frequency band of the military data link has covered the short wave, ultrashort wave, LX frequency band, satellite communication frequency band, and quantum band.

Today, with the rapid development of new technologies such as the Internet of Things, cloud computing, and artificial intelligence, the development of data links is facing new challenges and opportunities. Whether the future battlefield can be more transparent depends on the development trend and process of the data link. What is certain is that in the future, the data link will still be the "multiplier" for energy gathering at the end of the battlefield and an important support for the army to win the battlefield. However, the current problem is the distribution of information for the simulation test system used in military training. Unable to check to ensure that the information is valid.

Contents of the invention

The purpose of the present disclosure is to overcome the deficiencies in the prior art, and provide a method and device for distributing information. The method for distributing information can solve the problem that the distributing information of the simulation test system used in military training cannot be checked, so that it cannot Questions to make sure the information is valid.

According to the first aspect of the embodiments of the present disclosure, there is provided a checking method for distribution information, the method includes:

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;

Check whether the byte length of the information is equal to the byte length defined by the configuration file;

When the byte length of the information is equal to the byte length defined by the configuration file, check the code of the sender to determine whether the sender is a user defined by the protocol;

When the sender is a protocol definition user, check 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, check the event code to determine whether the event is a protocol-defined event;

When the event is a protocol-defined event, check 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 channel is distributed for the sender.

In one embodiment, the method also includes:

The method also includes:

When the byte length of the information is not equal to the byte length defined by the configuration file, an error message is sent, and the error message carries error type information;

When the sender is not a protocol-defined user, send an error message, and the error message carries error type information;

When the system sending the target configuration file is not a simulation test system, send an error message, and 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.

In one embodiment, the method also includes:

Count the number of the error information and the error type information;

determining the error frequency of the sender information according to the amount of the error 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 for the sender to correct errors.

In one embodiment, said checking the sender code to determine whether the sender is a protocol defined user comprises:

Check whether the first N codes of the information byte are within the definition of the target configuration file; wherein, N is a natural number, and N is not equal to 0;

If the first N codes of the information byte are located within the definition of the target configuration file, then it is determined that the sender is a protocol definition user;

If the code of the first N digits of the information byte is not within the definition of the target configuration file, it is determined that the sender is not a protocol definition user.

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

Check whether the N+X bit code of the information byte is equal to the target configuration file definition code; wherein, X is a natural number, and X>N;

If the N+X bit code of the information byte is equal to the target configuration file definition code, then it is determined that the system sending the target configuration file is a simulation test system;

If the N+X bit code of the information byte is not equal to the target configuration file definition code, it is determined that the system sending the target configuration file is not a simulation test system.

In one embodiment, the inspecting the event code to determine whether the event is a protocol-defined event includes:

Check whether the N+X+Y bit code of the information byte is within the definition of the target configuration file; wherein, Y is a natural number, and Y>X;

If the N+X+Y bit code of the information byte is within the definition of the target configuration file, then determine that the event is a protocol definition event;

If the N+X+Y bit code of the information byte is not defined in the target configuration file, it is determined that the event is not a protocol-defined event.

In one embodiment, the checking subevent code to determine whether the subevent is a protocol defined subevent comprises:

Check whether the N+X+Y+Z bit code of the information byte is within the definition of the target configuration file; wherein, Z is a natural number, and Z>Y;

If the N+X+Y+Z bit code of the information byte is within the definition of the target configuration file, then determine that the sub-event is a protocol-defined sub-event;

If the N+X+Y+Z 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.

In one embodiment, the method also includes:

If the length of the event code is less than the length of the defined code, fill in before the event code;

If the sub-event code length is less than the defined code length, a place is filled before the sub-event code.

According to the second aspect of the embodiments of the present disclosure, there is provided an inspection device for distributing information, the device includes:

The acquisition module acquires 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 check module checks whether the byte length of the information is equal to the byte length defined by the configuration file;

The second inspection module, when the byte length of the information is equal to the byte length defined by the configuration file, checks the code of the sender to determine whether the sender is a user defined by the protocol;

The third inspection module, when the sender is a protocol definition user, checks the system code check code to determine whether the system sending the target configuration file is a simulation test system;

The fourth inspection module, when the system sending the target configuration file is a simulation test system, inspects the event code to determine whether the event is a protocol definition event;

The fifth checking module, when the event is a protocol-defined event, checks the sub-event code to determine whether the sub-event is a protocol-defined sub-event;

The distribution module distributes channels for the sender when the sub-event is a protocol-defined sub-event.

In one embodiment, the device also includes:

A statistics module, counting the quantity of the error information and the error type information;

A determining module, which determines the error frequency of sender information according to the number of error information and error type information;

The generation module generates an analysis report of the sender according to the error frequency of the sender's information, and the analysis report is used for the sender to correct errors.

The disclosure provides a verification method for distribution information. By obtaining target configuration file information, the target configuration file information includes information byte length, sender code, system code check code, event code and sub-event code, and checks the information word Section length 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, further check the sender’s code to determine whether the sender is a protocol-defined user. When the sender is a protocol-defined user, Check 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, check the event code to determine whether the event is a protocol definition event. If the event is When the protocol defines an event, check 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, then distribute the channel for the sender to solve the problem of the emulation test system used in military training The distribution information cannot be checked to ensure that the information is valid.

Description of drawings

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

FIG. 1 is a flow chart of a method for checking distribution information provided by an embodiment of the present disclosure.

FIG. 2 is a flow chart of a method for checking distribution information provided by an embodiment of the present disclosure.

Fig. 3 is a structural diagram of an inspection device for distributing information provided by an embodiment of the present disclosure.

FIG. 4 is a structural diagram of an inspection device for distributing information provided by an embodiment of the present disclosure.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

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

Step 101, obtaining target configuration file information;

In this step, the target configuration file information includes information byte length, sender code, system code check code, event code and sub-event code;

Step 102, checking whether the byte length of the information is equal to the byte length defined by the configuration file;

In this step, if the byte length of the information is equal to the byte length defined in the configuration file, then enter step 103; if the byte length of the information is not equal to the byte length defined in the configuration file, an error is reported and the error type is fed back.

Step 103, when the byte length of the information is equal to the byte length defined in the configuration file, check the code of the sender to determine whether the sender is a protocol-defined user;

In one embodiment, said checking the sender code to determine whether the sender is a protocol defined user comprises:

Check whether the first N codes of the information byte are within the definition of the target configuration file; wherein, N is a natural number, and N is not equal to 0;

If the first N codes of the information byte are located within the definition of the target configuration file, then it is determined that the sender is a protocol definition user;

If the code of the first N digits of the information byte is not within the definition of the target configuration file, it is determined that the sender is not a protocol definition user.

In this embodiment, if the code of the first N bits of the information byte is within the definition range of the configuration file, go to step 104; if the code of the first N bits of the information byte is not within the range of the definition of the configuration file, an error will be reported and the error type will be fed back.

Step 104, when the sender is a protocol definition user, check the system code check code to determine whether the system sending the target configuration file is a simulation test system;

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

Check whether the N+X bit code of the information byte is equal to the target configuration file definition code; wherein, X is a natural number, and X>N;

If the N+X bit code of the information byte is equal to the target configuration file definition code, then it is determined that the system sending the target configuration file is a simulation test system;

If the N+X bit code of the information byte is not equal to the target configuration file definition code, it is determined that the system sending the target configuration file is not a simulation test system.

In this embodiment, check the system code check code to determine whether the target system for information transmission belongs to the simulation test system, that is, whether the N+X bit code of the information byte is equal to the configuration file definition code, if the Nth bit of the information byte is determined +X bit code is equal to the target configuration file definition code, then it is determined that the system of the target configuration file is a simulation test system, then enter step 105, if it is determined that the N+X bit code of the information byte is not equal to the target configuration file definition code, then determine If the system of the target configuration file is not a simulation test system, an error will be reported and the error type will be fed back.

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 definition event;

In one embodiment, the inspecting the event code to determine whether the event is a protocol-defined event includes:

Check whether the N+X+Y bit code of the information byte is within the definition of the target configuration file; wherein, Y is a natural number, and Y>X;

If the N+X+Y bit code of the information byte is within the definition of the target configuration file, then determine that the event is a protocol definition event;

If the N+X+Y bit code of the information byte is not defined in the target configuration file, it is determined that the event is not a protocol-defined event.

In this embodiment, check the event code to determine whether the event belongs to a protocol-defined event, that is, whether the N+X+Y bit code of the information byte is within the definition range of the configuration file, if the N+X+Y bit of the information byte If the bit code is within the definition of the target configuration file, it is determined that the event is a protocol-defined event. If the N+X+Y 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, and an error is reported and Feedback error type.

Step 106, when the event is a protocol-defined event, check the sub-event code to determine whether the sub-event is a protocol-defined sub-event;

In one embodiment, the checking subevent code to determine whether the subevent is a protocol defined subevent comprises:

Check whether the N+X+Y+Z bit code of the information byte is within the definition of the target configuration file; wherein, Z is a natural number, and Z>Y;

If the N+X+Y+Z bit code of the information byte is within the definition of the target configuration file, then determine that the sub-event is a protocol-defined sub-event;

If the N+X+Y+Z 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.

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 bit of the information byte is within the definition range of the configuration file, if the Nth bit of the information byte +X+Y+Z bit code is within the definition of the target configuration file, then it is determined that the sub-event is a protocol-defined sub-event, if the N+X+Y+Z bit code of the information byte is not within the definition of the target configuration file, then If it is determined that the sub-event is not a protocol-defined sub-event, an error will be reported and the error type will be fed back.

Step 107, when the sub-event is a protocol-defined sub-event, distribute the channel to the sender.

In this step, if the information satisfies the verification result, it enters the distribution channel and records it for filing.

The disclosure provides a verification method for distribution information. By obtaining target configuration file information, the target configuration file information includes information byte length, sender code, system code check code, event code and sub-event code, and checks the information word Section length 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, further check the sender’s code to determine whether the sender is a protocol-defined user. When the sender is a protocol-defined user, Check 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, check the event code to determine whether the event is a protocol definition event. If the event is When the protocol defines an event, check 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, then distribute the channel for the sender to solve the problem of the emulation test system used in military training The distribution information cannot be checked to ensure that the information is valid.

Optionally, as shown in Figure 2, the shown method also includes:

Step 201, counting the quantity of the error information and the error type information;

Step 202. Determine the error frequency of sender information according to the number of error information and error type information;

Step 203: Generate an analysis report of the sender according to the error frequency of the sender information, and the analysis report is used for the sender to correct errors.

In this embodiment, by counting the number of error information and error type information, and determining the error frequency of the sender's information according to the amount of error information and error type information, and then generating the sender's analysis report according to the error frequency of the sender's information , so that the sender can correct the error.

Optionally, the method also includes:

If the length of the event code is less than the length of the defined code, fill in before the event code;

If the sub-event code length is less than the defined code length, a place is filled before the sub-event code.

In this embodiment, when the event code length is less than the defined code length, the place is automatically filled before the event code, and when the sub-event code length is less than the defined code length, the place is automatically filled before the sub-event code, and 0 or Custom character padding. In this embodiment, the problem of simple bit error code is automatically corrected by means of error correction, so as to avoid the problem of resource loss and efficiency reduction caused by repeated sending of information.

Fig. 3 is a structural diagram of an inspection device for distributing information provided by an embodiment of the present disclosure. As shown in Figure 3, the checking device of this distributing information comprises: acquisition module 301, first checking module 302, second checking module 303, the 3rd checking module 304, the 4th checking module 305, the 5th checking module 306 and distributing module 307; wherein, the obtaining 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 check module 302 Used to check whether the byte length of the information is equal to the byte length defined by the configuration file; the second check module 303 is used to check the sender code to determine the sender when the byte length of the information is equal to the byte length defined by the configuration file Whether it is a protocol definition user; the third inspection module 304 is used to check the system code check code when the sender is a protocol definition user, to determine whether the system sending the target configuration file is a simulation test system; the fourth inspection module 305 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; 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 configured to distribute channels for the sender when the sub-event is a protocol-defined sub-event.

FIG. 4 is a structural diagram of an inspection device for distributing information provided by an embodiment of the present disclosure. As shown in Figure 4, the inspection device of 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 quantity of the error information and the error type information; the determination module 409 is used to calculate the error information according to the error information and the error type The amount of information determines the error frequency of the sender's information; the generating module 4010 is configured to generate an analysis report of the sender according to the error frequency of the sender's information, and the analysis report is used for the sender to correct errors.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above method embodiments can be completed by program instructions and related hardware. The aforementioned programs can be pre-installed in a computer-readable storage medium. When the program is executed, it executes the steps including the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. The present disclosure is intended to cover any modification, use or adaptation of the present disclosure. These modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. . The specification and examples are considered exemplary only, with the true and spirit of the disclosure pointed out by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have 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 (10)

1. A method of inspecting distributed information, the method comprising:

acquiring target configuration file information; the target configuration file information comprises an information byte length, a sender code, a system code check code, an event code and a sub-event code;

checking whether the information byte length is equal to the configuration file definition byte length;

checking the sender code to determine if the sender is a protocol definition user when the information byte length is equal to the profile definition byte length;

checking a system code check code when the sender is a protocol definition user to determine whether the system transmitting the target configuration file is a simulation test system;

when the system sending the target configuration file is a simulation test system, checking an event code to determine whether an event is a protocol definition event;

when the event is a protocol definition event, examining the sub-event code to determine whether the sub-event is a protocol definition sub-event;

and when the sub-event is a protocol definition sub-event, distributing a channel for the sender.

2. The method according to claim 1, wherein the method further comprises:

when the information byte length is not equal to the configuration file definition byte length, sending error reporting information, wherein the error reporting information carries error type information;

when the sender is not a protocol definition user, sending error reporting information, wherein the error reporting information carries error type information;

when the system for transmitting the target configuration file is not a simulation test system, transmitting error reporting information, wherein the error reporting information carries error type information;

when the event is not a protocol definition event, sending error reporting information, wherein the error reporting information carries error type information;

and when the sub-event is not the protocol definition sub-event, sending error reporting information, wherein the error reporting information carries error type information.

3. The method according to claim 2, wherein the method further comprises:

counting the number of the error information and the error type information;

determining the error frequency of the sender information according to the error information and the number of the error type information;

and generating an analysis report of the sender according to the error frequency of the sender information, wherein the analysis report is used for correcting errors by the sender.

4. A method according to any one of claims 1 to 3, wherein said examining the sender code to determine if the sender is a protocol defining user comprises:

checking whether the first N-bit code of the information byte is located within a target profile definition; wherein N is a natural number, and N is not equal to 0;

if the first N-bit code of the information byte is positioned in the target configuration file definition, determining that the sender is a protocol definition user;

if the first N-bit code of the information byte is not located within the target profile definition, it is determined that the sender is not a protocol definition user.

5. The method of claim 4, wherein the validating the system code check code to determine whether the system sending the target profile is a simulation test system comprises:

checking whether an n+x bit code of the information byte is equal to the target profile definition code; wherein X is a natural number, and X > N;

if the (N+X) th bit code of the information byte is equal to the target configuration file definition code, determining that the system for transmitting the target configuration file is a simulation test system;

if the (N+X) th bit code of the information byte is not equal to the target configuration file definition code, determining that the system sending the target configuration file is not a simulation test system.

6. The method of claim 5, wherein the examining the event code to determine if the event is a protocol-defined event comprises:

checking whether an n+x+y bit code of the information byte is within the target profile definition; wherein Y is a natural number, and Y > X;

if the n+X+Y bit code of the information byte is within the target profile definition, determining that the event is a protocol definition event;

if the n+X+Y bit code of the information byte is not within the target profile definition, determining that the event is not a protocol definition event.

7. The method of claim 6, wherein the examining the sub-event code to determine whether the sub-event is a protocol-defined sub-event comprises:

checking whether an n+x+y+z bit code of the information byte is within the target profile definition; wherein Z is a natural number, and Z > Y;

if the N+X+Y+Z bit code of the information byte is within the target configuration file definition, determining that the sub-event is a protocol definition sub-event;

if the n+X+Y+Z bit code of the information byte is not within the target profile definition, determining that the sub-event is not a protocol definition sub-event.

8. The method of claim 7, wherein the method further comprises:

and if the event code length is less than the definition code length, supplementing bits before the event code.

9. An inspection apparatus for distributing information, the apparatus comprising:

the acquisition module acquires target configuration file information; the target configuration file information comprises an information byte length, a sender code, a system code check code, an event code and a sub-event code;

a first checking module for checking whether the information byte length is equal to the configuration file definition byte length;

a second checking module for checking the sender code to determine whether the sender is a protocol definition user when the information byte length is equal to the profile definition byte length;

a third checking module for checking the system code check code to determine whether the system transmitting the target configuration file is a simulation test system when the sender is a protocol definition user;

a fourth checking module for checking an event code to determine whether an event is a protocol definition event when the system transmitting the target profile is a simulation test system;

a fifth checking module for checking the sub-event code to determine whether the sub-event is a protocol definition sub-event when the event is a protocol definition event;

and the distribution module is used for distributing a channel for the sender when the sub-event is a protocol definition sub-event.

10. The apparatus of claim 9, wherein the apparatus further comprises:

the statistics module is used for counting the number of the error information and the error type information;

the determining module is used for determining the error frequency of the sender information according to the error information and the number of the error type information;

and the generation module is used for generating an analysis report of the sender according to the error frequency of the sender information, wherein the analysis report is used for correcting errors by the sender.

Images