A border sea defense information exchange system and method

Abstract

The application provides a border sea defense information exchange system, comprising a monitoring station system module and a monitoring center system service module, and the monitoring station system module and the monitoring center system service module communicate through a TCP protocol network; the monitoring station system module classifies and encapsulates the obtained data into multiple data classes according to border sea defense services, and the monitoring center system service module processes data according to the data classes. The application also provides a border sea defense information exchange method. The application encapsulates border sea defense service information by using a general protocol data packet information structure, can unify the information exchange content and data format of multiple border sea defense service application interactions, is beneficial to the upper and lower systems constructed by different units to network and interact information according to a unified information structure and data format, simplifies the information encoding and decoding, data encapsulation and packaging and information receiving and sending work processes of the interaction information between the systems at all levels through application software services, is beneficial to the information interconnection and intercommunication between the border sea defense monitoring systems at all levels, and improves work efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to a kind of border defense information exchange system and method. BACKGROUND

[0002] Border defense monitoring system is an important border defense infrastructure of the country, adopts the architecture of networking of multistage center and monitoring station from top to bottom, and monitoring station is responsible for border defense information acquisition, acquisition and reporting, and monitoring center is responsible for border defense information collection, processing, management and distribution, and various information is transferred between the networked systems of various levels according to the corresponding business process specification.

[0003] Border defense monitoring system has video monitoring, instruction interaction, comprehensive situation, command control, service management and other applications, because the systems of various levels constructed by different units are independent of each other, the technology system, data resources and interfaces are different, the types of interactive information, data content and format are different, etc., often lead to the difficulty of interaction between systems of various levels, form information island, affect interconnection and information resource sharing between systems.

[0004] For the above problems, the main technical solution currently adopted is, as disclosed in application No. CN202110584748.0, a kind of safety isolation and information exchange system and method, which improves efficiency by reducing verification time, obviously, this improvement is far from enough, and it is also impossible to realize interconnection and information resource sharing between systems. SUMMARY

[0005] To solve the above technical problems, the present application provides a kind of border defense information exchange system and method, which can effectively solve the problem of interactive information between border defense monitoring systems of various levels according to unified information format, interactive process and interface specification, simplify the data organization and encapsulation and packaging process of general protocol data packet, and improve the efficiency of data packet generation and analysis

[0006] The present application is realized by the following technical solutions.

[0007] The border defense information exchange system provided by the present application is characterized by: comprising a monitoring station system module and a monitoring center system service module, and the monitoring station system module and the monitoring center system service module communicate through TCP protocol network; the monitoring station system module classifies and encapsulates the data obtained according to border defense business into multiple data classes, and the monitoring center system service module processes data according to data class.

[0008] The monitoring center system service module realizes network communication based on information exchange service, including information exchange server, information exchange client, information exchange interface and service monitoring interface, and the general protocol information structure data packet is transmitted between the information exchange server and the information exchange client through TCP protocol.

[0009] The information exchange server is deployed in a monitoring center system, realizes client connection of a monitoring station and a center service application seat, sends a heartbeat packet to the client, maintains network connection, transmits and receives client information, unpacks and encapsulates the received / sent information according to a general protocol format, distributes the information to a corresponding destination IP address, records the online state of the client and the received / sent packet information, monitors the service state; the information exchange client is deployed in the monitoring station and the center service application seat, and is used for connecting the information exchange server, realizing information transmission and information receiving functions between the monitoring station and the monitoring center; the information exchange service interface is used for information transmission and reception of the service application seat through the information exchange server; the service monitoring interface displays the service state and related information of the information exchange service to an interface window, including a client list connected to the service and data information exchanged between the client and the server.

[0010] The data packet transmitted through the TCP protocol is composed of a packet header and a data block, and the length of the data packet is not greater than 2K bytes, wherein:

[0011] The packet header is composed of 14 bytes, including a packet identifier, a version number, a packet ID, a total number of sub-packets, a sub-packet number, and a sub-packet length, and the packet ID of all sub-packets of the same protocol message must be the same;

[0012] The data block is composed of a data header and a data record.

[0013] The data structure of the packet header is that the first 3 bytes are the packet identifier, indicating a general protocol data packet of the border defense, the 4th byte is the version number, represented by a hexadecimal number, for example, the version number 1.0 is represented by 0x10, the 5th to 10th bytes are the packet header identifier ID, the high 24 bits represent the information source code of the monitoring center / station at each level, and the low 24 bits are the cyclic count from 0 to 0xffffff, the 11th byte is the total number of sub-packets with the same packet ID, the 12th byte is the sequential number of the sub-packet, and the 13th to 14th bytes are the total length of the sub-packet including the packet header length.

[0014] The data header is composed of a protocol version number, a protocol data class, and a data block length, and the data header is fixed at 6 bytes, wherein the 1st byte is the protocol version number, the 2nd byte is the data class transmitted, and the 3rd to 6th bytes are the total length of the data block including the data header.

[0015] The application also provides a border sea defense information exchange method applied to the border sea defense information exchange system, characterized in that the monitoring center system service module realizes the client connection of the monitoring station and the center business application seat based on the information exchange service process, sends the heartbeat packet to the client, maintains the network link, transmits the client information, unpacks and encapsulates the received / sent information according to the general protocol format, and realizes the information transmission and information reception between the monitoring station and the monitoring center based on the information exchange access process.

[0016] The information exchange service process is specifically as follows:

[0017] (1) creating a TCP service socket to listen to at least two service ports, one of which is used for the monitoring station client connection and the other is used for the center business application seat client connection;

[0018] (2) creating a TCP client socket to connect to the service port of the upper center service end, which is used to forward the information received by the center to the upper center according to the related business process requirements;

[0019] (3) listening to the network event message of the service end and the client, and cyclically detecting whether the client is connected to the service end and whether the connection to the upper center service end is successful;

[0020] (4) when it is detected that the client requests to connect, processing the connection request of the client and establishing the connection with the client, and adding the client to the client connection list;

[0021] (5) starting the daemon thread, sending the heartbeat packet to the client at a regular time, receiving the heartbeat packet information sent by the client, and judging whether the network connection of the client is normal;

[0022] (6) when the heartbeat packet of the client is not received or the connection of the client is timed out, closing the client connection, deleting the client from the client connection list, and notifying the monitoring center that the client has lost the connection;

[0023] (7) when the connection of the client is normal, receiving the message sent by the client, and buffering the received data packet in the received information buffer area;

[0024] (8) calling the service end unpacking service program, extracting the data in the data block from the received information buffer area according to the general protocol data packet information structure, and restoring the data to the corresponding business information of the data class;

[0025] (9) calling the business logic processing program to process the related business, converting the data into the corresponding business information, and displaying the business information content on the user interface.

[0026] The information exchange access process is specifically as follows:

[0027] (1) create a TCP socket, connect to the service port of the information exchange server, monitor the client connection of the station service port of the station, and connect the client of the center business application seat to the seat service port of the server;

[0028] (2) adopt asynchronous and event mode to monitor the server information;

[0029] (3) if the connection to the server is successful, send a heartbeat packet to the server at regular intervals to maintain the long connection with the server;

[0030] (4) receive the monitoring center command or message data sent by the information exchange server, and deliver the information to the monitoring station business application;

[0031] (5) encapsulate the information reported by the monitoring station business application into a general protocol data packet, and send it to the information exchange server, and then the server unpacks the information and delivers it to the monitoring center business application seat for display.

[0032] In the information exchange service process and the information exchange access process, the following method is used to realize the underlying information transmission:

[0033] a. receive the byte information to be sent from the information exchange interface;

[0034] b. add the information to be sent to the sending data buffer;

[0035] c. loop to detect whether there is information to be sent in the sending buffer;

[0036] d. if yes, take the information to be sent from the sending buffer, otherwise, return to step c;

[0037] e. judge whether the length of the information to be sent is greater than the packet length, that is, whether it needs to be packaged;

[0038] f. if it needs to be packaged, split the data into several packets not exceeding 2k, otherwise go to step g directly;

[0039] g. add a packet header to the data to be sent, and package the data according to the general protocol data packet format;

[0040] h. send the general protocol data packet information to the destination IP address in an asynchronous manner;

[0041] i. delete the sent byte information from the sending buffer.

[0042] In the information exchange service process and the information exchange access process, the following method is used to realize the underlying information reception:

[0043] A. start receiving data from the network socket;

[0044] B. Determine whether the information is received and the port is normal, and the port is not normal, then exit the receiving process and close the port;

[0045] C. Read information from the network socket into the receiving buffer for processing;

[0046] D. Determine whether the length of the received information is greater than the length of a packet header, if yes, go to the next step, otherwise return to step A;

[0047] E. Determine whether the first three bytes are the packet identifier, if yes, go to the next step, otherwise remove the three bytes from the receiving buffer and return to step D;

[0048] F. Extract the packet header from the receiving buffer to obtain the packet length information;

[0049] G. Determine whether the length of the received information is greater than or equal to the packet length, if yes, go to the next step, otherwise return to step A;

[0050] H. Read the data block to obtain the number of packets and the total number of packets;

[0051] I. Remove a data packet from the receiving buffer;

[0052] J. Merge the data packet into the packet ID buffer belonging to the port;

[0053] K. Determine whether it is the last packet, if yes, go to the next step, otherwise return to step D;

[0054] L. Merge the data into the data packet disassembly service processing, and then jump to step D to receive the data packet.

[0055] The beneficial effects of the present application are that the general protocol packet information structure is used to encapsulate the border sea defense service information, which can unify the information exchange content and data format of various border sea defense service application interactions, and is beneficial to the upper and lower systems constructed by different units to interact information in a unified information structure and data format; the application software service simplifies the information encoding and decoding, data encapsulation and packaging, and information receiving and transmitting workflow when interacting information between systems, which is beneficial to the information interconnection and intercommunication between border sea defense monitoring systems at all levels, and improves work efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0056] Figure 1 is a schematic diagram of module connection of at least one embodiment of the present application;

[0057] Figure 2 is Figure 1 is a schematic diagram of the overall architecture of the embodiment in at least one practical application;

[0058] Figure 3This is a data structure diagram of business application information classification in at least one embodiment of the present invention;

[0059] Figure 4 This is a data packet structure diagram in at least one embodiment of the present invention;

[0060] Figure 5 This is a data field structure diagram in at least one embodiment of the present invention;

[0061] Figure 6 This is a schematic diagram of the information exchange server module in at least one embodiment of the present invention;

[0062] Figure 7 This is a schematic diagram of an information exchange interface module in at least one embodiment of the present invention;

[0063] Figure 8 This is a flowchart of the information exchange service information sending process in at least one embodiment of the present invention;

[0064] Figure 9 This is a flowchart of the information exchange service information receiving process in at least one embodiment of the present invention;

[0065] Figure 10 This is a flowchart of the data packet parsing and processing of information exchange services in at least one embodiment of the present invention. Detailed Implementation

[0066] The technical solution of the present invention is further described below, but the scope of protection is not limited to what is described.

[0067] Example 1

[0068] like Figures 1 to 7 The border and coastal defense information exchange system shown is characterized by: including a monitoring station system module and a monitoring center system service module, which communicate with each other via TCP protocol network; the monitoring station system module classifies and encapsulates the acquired data into various data classes according to the border and coastal defense business, and the monitoring center system service module processes the data according to the data classes.

[0069] Example 2

[0070] Based on Embodiment 1, the monitoring center system service module realizes network communication based on information exchange service. The information exchange service includes information exchange server, information exchange client, information exchange interface and service monitoring interface. The information exchange server and information exchange client transmit general protocol information structure data packets through TCP protocol.

[0071] Example 3

[0072] Based on the embodiment 2, the information exchange service end is deployed in the monitoring center system, realizes the client connection of the monitoring station and the center business application seat, sends the heartbeat package to the client, maintains the network link, transmits the client information, unpacks / encapsulates the received / sent information according to the general protocol format, distributes to the corresponding destination IP address, records the client online state and the received / sent package information, and monitors the service state; the information exchange client is deployed in the monitoring station and the center business application seat, is used for connecting the information exchange service end, realizes the information sending and information receiving function between the monitoring station and the monitoring center; the information exchange service interface is used for the business application seat to send and receive information through the information exchange service end; the service monitoring interface displays the service state and related information of the information exchange service to the interface window, including the client list connected to the service, and the data information exchanged between the client and the service end.

[0073] Embodiment 4

[0074] Based on the embodiment 1, the data packet transmitted through the TCP protocol is composed of a packet header and a data block, and the data packet length is not greater than 2K bytes, wherein:

[0075] The packet header is composed of 14 bytes, including packet identification, version number, packet ID, total number of sub-packets, sub-packet number and sub-packet length, and the packet ID of all sub-packets of the same protocol message must be the same;

[0076] The data block is composed of a data header and a data record.

[0077] Embodiment 5

[0078] Based on the embodiment 4, the data structure of the packet header is that the first 3 bytes are packet identification, indicating the general protocol transmission data packet of the border defense, the 4th byte is version number, represented by hexadecimal number, for example, the version number is 1.0 represented by 0x10, the 5th to 10th bytes are packet header identification ID, the high 24 bits represent the information source code of the monitoring center / monitoring station at all levels, and the low 24 bits are 0-0xffffff cyclic count, the 11th byte is the total number of sub-packets with the same packet ID; the 12th byte is the sequential number of the sub-packet, and the 13th to 14th bytes are the total length of the sub-packet including the packet header length.

[0079] Embodiment 6

[0080] Based on the embodiment 4, the data header is composed of protocol version number, protocol data class and data block length, and the data header is fixed to 6 bytes, wherein the 1st byte is the protocol version number, the 2nd byte is the data class transmitted, and the 3rd to 6th bytes are the total length of the data block including the data header.

[0081] Embodiment 7

[0082] The application also provides a border defense information exchange method, based on the above embodiment, the monitoring center system service module realizes the client connection of the monitoring station and the center business application seat based on the information exchange service process, sends the heartbeat packet to the client, maintains the network link, transmits and receives the client information, unpacks and encapsulates the received / sent information according to the general protocol format; the monitoring station system module realizes the information transmission and information reception between the monitoring station and the monitoring center based on the information exchange access process.

[0083] Embodiment 8

[0084] Based on embodiment 7, the information exchange service process is specifically:

[0085] (1) create a TCP service socket to listen to at least two service ports, one of which is used for the monitoring station client connection, and the other is used for the center business application seat client connection;

[0086] (2) create a TCP client socket to connect to the service port of the upper center service end, which is used to forward the information received by the center to the upper level according to the related business process requirements;

[0087] (3) listen to the network event message of the service end and the client, and cyclically detect whether the client is connected to the service end and whether the connection to the upper center service end is successful;

[0088] (4) when detecting that the client requests connection, process the connection request of the client and establish connection with the client, and add the client to the client connection list;

[0089] (5) start the daemon thread, send the heartbeat packet to the client regularly, receive the heartbeat packet information sent by the client, and judge whether the client network connection is normal;

[0090] (6) if the client heartbeat packet is not received or the client connection is timed out, close the client connection, delete the client from the client connection list, and notify the monitoring center that the client has lost the connection;

[0091] (7) if the client connection is normal, receive the message sent by the client, and cache the received data packet in the received information buffer area;

[0092] (8) call the service end unpacking service program, extract the data in the data block from the received information buffer area according to the general protocol data packet information structure, and restore it to the corresponding data class business information;

[0093] (9) call the business logic processing program to process the related business, convert the data into the corresponding business information, and the user interface displays the business information content.

[0094] Embodiment 9

[0095] Based on embodiment 7, the information exchange access process is as follows:

[0096] (1) Create a TCP socket, connect to the service port of the information exchange server, monitor the client connection to the station service port of the station, and connect the client of the center business application seat to the seat service port of the server;

[0097] (2) Listen to the server information in an asynchronous and event-driven manner;

[0098] (3) If the connection to the server is successful, send a heartbeat packet to the server at regular intervals to maintain a long connection with the server;

[0099] (4) Receive the monitoring center command or message data sent by the information exchange server, and pass the information to the monitoring station business application;

[0100] (5) Encapsulate the information reported by the monitoring station business application into a general protocol data packet, and send it to the information exchange server. The server unpacks the information and passes it to the monitoring center business application seat for display.

[0101] Embodiment 10

[0102] Based on embodiment 7, the information exchange service process and the information exchange access process are implemented as follows:

[0103] a. Receive the byte information to be sent from the information exchange interface;

[0104] b. Add the information to be sent to the send data buffer;

[0105] c. Loop to detect whether there is information to be sent in the send buffer;

[0106] d. If so, take the information to be sent from the send buffer, otherwise, return to step 3;

[0107] e. Determine whether the length of the information to be sent is greater than the packet length, i.e., whether it needs to be packaged;

[0108] f. If it needs to be packaged, split the data into several packets not exceeding 2k, otherwise go directly to step g;

[0109] g. Add a packet header to the data to be sent, and package the data according to the general protocol data packet format;

[0110] h. Send the general protocol data packet information to the destination IP address in an asynchronous manner;

[0111] i. Delete the sent byte information from the send buffer.

[0112] In the information exchange service flow and the information exchange access flow, the underlying information receiving is realized in the following way:

[0113] A. Start receiving data from the network socket;

[0114] B. Determine whether information is received and the port is normal, and if the port is not normal, exit the receiving flow and close the port;

[0115] C. Read information from the network socket into a receiving buffer for processing;

[0116] D. Determine whether the length of the received information is greater than the length of a packet header, and if yes, go to the next step, otherwise return to step A;

[0117] E. Determine whether the first three bytes are a packet identifier, and if yes, go to the next step, otherwise remove the three bytes from the receiving buffer and return to step D;

[0118] F. Extract the packet header from the receiving buffer to obtain packet length information;

[0119] G. Determine whether the length of the received information is greater than or equal to the packet length, and if yes, go to the next step, otherwise return to step A;

[0120] H. Read the data block to obtain the number of packet segments and the total number of packet segments;

[0121] I. Remove a data packet from the receiving buffer;

[0122] J. Merge the data packet into a packet ID buffer belonging to the port;

[0123] K. Determine whether it is the last packet segment, and if yes, go to the next step, otherwise return to step D;

[0124] L. Merge the data into a data packet disassembly service process, and then jump to step D to receive the data packet.

[0125] Embodiment 11

[0126] Based on the above embodiments, according to the service application information data structure, the edge sea defense service data exchanged between different users through a communication medium is divided into several data categories such as data category 1, data category 2, and data category n (for example, the application service data related to edge sea defense monitoring can be divided into several data categories such as comprehensive situation, device state parameter and configuration, video control, command service, and comprehensive target), so as to identify, distribute, and control the priority of the data.

[0127] The smallest information unit in the data category is a data item, and it is agreed that each data category is composed of several mandatory and optional data items, each data item defines a data item reference number, and a data item is uniquely identified in the data item record of the corresponding data category.

[0128] Data item reference number is defined as 8 characters, such as "Innn / AAA", I represents a data item, nnn uses a 3-digit number to indicate the data class to which the data item belongs, and AAA uses a 3-digit number to identify the data item.

[0129] According to different business applications, some data items may be mandatory during network transmission, and some are optional. Mandatory data items represent common data required by any application and must be transmitted. Optional data items are relatively special data that are transmitted under certain conditions or for some specific business applications.

[0130] For each data class, extract all the minimum information units of the business application, i.e. all data items, and organize the list of all data items in the data class into a data item directory as shown in Table 1, which includes serial number, data item reference number, and data item.

[0131] Data item directory content table

[0132]

[0133]

[0134] A user application-related table as shown in Table 2 is defined, which contains data field reference number (FRN), data item reference number, data item, and data item length, to specify the correspondence between data items and data fields.

[0135] User application-related table (taking data class 1 as an example)

[0136]

[0137] Preferably, the data items are sorted. Each data item in the user application-related table is reasonably sorted, and the commonly used application public data items are placed at the front of the table, and the special application data items that are not frequently used are placed at the back of the table, so as to make the transmitted data as short as possible and improve the transmission efficiency.

[0138] The physical entity corresponding to the data item in the information network transmission, i.e. the smallest information transmission unit, is defined as a data field, and the collection of data fields of the same type is a data record. Each data record needs to contain an FSPEC data indication field to indicate whether each data field in the data record exists.

[0139] During the transmission of information of a certain data class, the application system only uses the standardized data items in the data item directory, and assigns various data items to each data field. Each data field is one-to-one corresponding to a data item through the data field reference number (FRN).

[0140] The protocol information containing the same data class is organized as a data block composed of a data header and a data record. The continuous information received and sent by the application program is organized as one or more data packets of TCP protocol continuous transmission.

[0141] Each data packet is composed of a packet header and a data block by TCP protocol transmission, and the data packet length is not greater than 2K bytes. When the information data to be transmitted is too large, the information data should be split into multiple sub-packets for transmission, and the same packet ID and the total number of sub-packets are assigned to these sub-packets, so that the receiving end can correctly parse the information according to the packet ID after receiving all the sub-packets.

[0142] (1) Packet header, the whole packet header is 14 bytes, which is composed of packet identification, version number, packet ID, total number of sub-packets, sub-packet number and sub-packet length, and the packet ID of all sub-packets of the same protocol message must be the same.

[0143] ① The first 3 bytes are packet identification, indicating the transmission data packet of the general protocol of the border defense;

[0144] ② The 4th byte is the version number, represented by a hexadecimal number, for example, the version number is 1.0 represented by 0x10;

[0145] ③ The 5th to 10th bytes are the packet header identification ID, the high 24 bits represent the information source code of the monitoring center / monitoring station at all levels (the information source code is identified by 3 bytes of numerical value to indicate the information source or information sender), and the low 24 bits are 0-0xffffff cyclic count;

[0146] ④ The 11th byte is the total number of sub-packets of the same packet ID;

[0147] ⑤ The 12th byte is the sequential number of the sub-packet;

[0148] ⑥ The 13th to 14th bytes are the total length of the sub-packet including the packet header length.

[0149] (2) Data block, composed of data header and data record.

[0150] ① The data header is composed of protocol version number, protocol data class and data block length. The data header is fixed to 6 bytes, of which the 1st byte is the protocol version number, the 2nd byte is the data class transmitted, and the 3rd to 6th bytes are the total length of the data block including the data header;

[0151] ② The data record includes an application required data class information, which is composed of a variable length FSPEC data indication field and a plurality of variable number of data fields. Each data field is associated with a unique data item, and all data class information in the data field is organized according to the data item indicated by the FSPEC field.

[0152] FSPEC field, as a content table, uses field extension mechanism, the last bit (FX) of byte indicates whether there is a subsequent byte, "1" represents existence, "0" represents nonexistence, the bit order in the field indicates the existence and order of data field in data record;

[0153] Fixed length data field, composed of a fixed number of bits, is used to encode fixed length integer, floating point number and other data units;

[0154] Extensible data field, composed of a predetermined length of main part and variable length of extensible secondary part, uses field extension mechanism, the last bit (FX) of the last byte of main part is "1" indicating that there is an extension part, the last bit of the last byte of the first extension part is "1" indicating that there is a subsequent extension part, and so on until the last bit of the last byte of an extension part is "0", which is used to encode unsigned integer and a group of Boolean type values with variable length.

[0155] Repeated data field, composed of a length byte at the beginning, encodes repetition coefficient N in an extensible encoding manner, indicating that there are N continuous same subfields after it, which is used to encode string information;

[0156] Combined data field, composed of a main subfield and subsequent data subfields, the main subfield uses field extension mechanism (FX) and is a mapping table of data subfields, indicating the order and existence of data subfields, and the format of data subfields can adopt one of the four standard formats, i.e. fixed length data field, extensible data field, repeated data field and fixed length data field.

[0157] Any one of the above data field structure or a combination or nesting of multiple ways is used to realize semantic with arbitrary complexity through simple syntax rules, which is used to encode various data items.

[0158] Embodiment 12

[0159] Based on the above embodiments, the service or application software is deployed on a hardware server and / or computer to run, which is used for information exchange between the monitoring center and the monitoring station and between the monitoring center and the superior center.

[0160] The overall structure of the system includes information exchange server, information exchange client, information exchange interface and service monitoring interface, and the server and the client transmit general protocol information structure data packet through TCP protocol.

[0161] The information exchange server is deployed in the monitoring center, realizes the client connection of the monitoring station and the center business application seat, sends the heartbeat package to the client, maintains the network link, transmits the client information, unpacks / encapsulates the received / sent information according to the general protocol format, distributes it to the corresponding destination IP address (monitoring station or center business application seat), records the online state of the client and the received / sent packet information, and monitors the service state. The main work flow is as follows:

[0162] (1) Create a TCP service socket to listen to at least two service ports, one of which is used for monitoring station client connection, and the other is used for center business application seat client connection;

[0163] (2) Create a TCP client socket to connect to the service port of the upper center server, and forward the information received by the center to the upper level according to the related business process requirements;

[0164] (3) Listen to the network event message of the service end and the client, and loop to detect whether the client is connected to the service end and whether the connection to the upper center server is successful;

[0165] (4) When detecting that a client requests to connect, process the connection request of the client and establish a connection with the client, and add the client to the client connection list;

[0166] (5) Start the daemon thread, send the heartbeat package to the client regularly, receive the heartbeat package information sent by the client, and judge whether the client network connection is normal;

[0167] (6) If no client heartbeat package is received or the client connection is timed out, close the client connection, delete the client from the client connection list, and notify the monitoring center that the client has lost the connection;

[0168] (7) The client connection is normal, receive the message sent by the client, and cache the received data packet in the received information buffer area;

[0169] (8) Call the service end unpacking service program to extract the data in the data block from the received information buffer area according to the general protocol data packet information structure, and restore it to the corresponding data class business information;

[0170] (9) Call the business logic processing program to process the related business, convert the data into the corresponding business information (Json string easy to understand), and the user interface displays according to the business information content.

[0171] The information exchange client is deployed in the monitoring station and the center business application seat, and is used for connecting the information exchange server, realizing the information sending and receiving function between the monitoring station and the monitoring center. The main work flow is as follows:

[0172] (1) Create a TCP socket, connect to the service port of the information exchange service, monitor the client connection of the station service port of the station, and connect the client of the center business application seat to the seat service port of the service;

[0173] (2) Listen to the service information in an asynchronous and event-driven manner;

[0174] (3) If the connection to the service is successful, send a heartbeat packet to the service at regular intervals to maintain a long connection with the service;

[0175] (4) Receive the monitoring center command or message data sent by the information exchange service, and pass the information to the monitoring station business application;

[0176] (5) Encapsulate the information reported by the monitoring station business application into a general protocol data packet, and send it to the information exchange service, which will pass the information to the monitoring center business application seat after unpacking the information.

[0177] The information exchange service interface is used for information transmission and reception by the business application seat through the information exchange service. Since the monitoring center business application seat and the information exchange service are generally distributed, an information exchange interface is designed between the business application seat and the information exchange service:

[0178] (1) Information exchange service and business application seat interface, including seat sending interface and seat receiving interface, used to pass the instructions or data information sent by the seat to the information exchange service through the interface, and send the information from the information exchange service to the designated monitoring station. The information sent by the monitoring station to the information exchange service is also passed to the business application through this interface;

[0179] ① Seat sending interface, receiving business data sent by the business application seat client, constructing a data block according to the general protocol data packet information structure, and sending the data block and the opposite address to the information exchange service;

[0180] ② Seat receiving interface, receiving the data block transmitted by the information exchange service, unpacking according to the unpacked information code, and passing the parsed information data to the corresponding business seat according to the corresponding data class protocol content;

[0181] (2) Interface with the monitoring station, used for information exchange between the information exchange service and the monitoring station, strictly following the relevant business specifications, transmitting general protocol information structure format data packets;

[0182] (3) Interface with the upper center, used for information exchange between the information exchange service and the upper center, strictly following the relevant business specifications, transmitting general protocol information structure format data packets;

[0183] (4) interface with the service monitoring interface for transferring information in the information exchange service to the service monitoring interface.

[0184] The service monitoring interface displays the service status and related information of the information exchange service to the interface window, including the list of clients connected to the service, data information exchanged between the client and the server, and the like.

[0185] The information exchange service interface is deployed in the monitoring station or the monitoring center in the form of a dll file, simplifying the general protocol format data packet packaging and parsing process. Through the information interface provided by the information exchange service, the business application can easily and quickly realize the packaging and organization, sending, data receiving and unpacking of the data block of the above-mentioned general protocol format standard.

[0186] The information exchange sending information flow is shown in Figure 8 According to the business information data structure and the transmission data packet information structure described above, the business byte data to be sent is packaged, and a packet header is added to each package, which contains identification, version number, package serial number, total number of packages, data block length and the like. The steps of the flow are as follows:

[0187] Step 1, receiving the byte information to be sent from the information exchange interface;

[0188] Step 2, adding the information to be sent to the sending data buffer;

[0189] Step 3, cyclically detecting whether there is information to be sent in the sending buffer;

[0190] Step 4, if yes, taking the information to be sent from the sending buffer, otherwise, returning to step 3;

[0191] Step 5, judging whether the length of the information to be sent is greater than the packet length, i.e. whether it needs to be packaged;

[0192] Step 6, if yes, splitting the data into several packages not exceeding 2k, otherwise, directly entering step 7;

[0193] Step 7, adding a packet header to the data to be sent, and packaging the data according to the general protocol data packet format;

[0194] Step 8, sending the general protocol data packet information to the destination IP address in an asynchronous manner;

[0195] Step 9, deleting the sent byte information from the sending buffer.

[0196] The information exchange receiving information is shown in Figure 9As shown, according to the foregoing transmission data packet information structure, the received byte data is unpacked, the unpacked data block is converted into a corresponding data format, is further converted into a Json string data format easy for a business application system to use, and the Json string is sent to a related business system. The steps are as follows:

[0197] Step 1, start receiving data from a network socket;

[0198] Step 2, judge whether information is received and a port is normal, if not, exit the receiving process and close the port;

[0199] Step 3, read information from the network socket into a receiving buffer for processing;

[0200] Step 4, judge whether the length of the received information is greater than a packet header length, if yes, go to the next step, otherwise return to step 1;

[0201] Step 5, judge whether the first three bytes are a packet identifier, if yes, go to the next step, otherwise remove the three bytes from the receiving buffer and return to step 4;

[0202] Step 6, extract a packet header from the receiving buffer to obtain packet length information;

[0203] Step 7, judge whether the length of the received information is greater than or equal to the packet length, if yes, go to the next step, otherwise return to step 1;

[0204] Step 8, read a data block to obtain a packet number and a total packet number;

[0205] Step 9, remove a data packet from the receiving buffer;

[0206] Step 10, merge the data packet into a packet ID buffer belonging to the port;

[0207] Step 11, judge whether it is the last packet, if yes, go to the next step, otherwise return to step 4;

[0208] Step 12, merge data into a data packet exchange and unpacking service for processing, and then jump to step 4 to receive a data packet.

[0209] The unpacking service flow is as shown in Figure 10 The received data packet is extracted according to the foregoing data packet and data block structure, information source, information sink, information type, information code and other data fields are extracted according to the FSPEC data indication field, corresponding data is extracted according to the information type and information code, and is transmitted to a related business application seat through an information exchange interface.

[0210] Thus, the application provides a solution for the application requirement of border sea defense information interaction, on the one hand, proposes a method of border sea defense information data encapsulation and packaging, data packet transceiving and information exchange service, and on the other hand, designs a border sea defense information exchange service system, which provides service for the exchange of business information data between border sea defense monitoring systems, solves the problem of information exchange between border sea defense monitoring systems at all levels according to unified data format, interaction process and interface specification, simplifies the data encapsulation and packaging and analysis process of general protocol format, improves the efficiency of data packet generation and analysis, all data packets are transmitted through TCP / IP network protocol, and the application is suitable for the information exchange and interconnection between border sea defense monitoring centers at all levels and between monitoring centers and monitoring stations.

[0211] The above embodiments are only preferred embodiments of the application, and the parts such as TCP protocol transmission data packets which are not described in detail adopt known mature technologies. The above embodiments are only examples of the preferred implementation methods for clearly illustrating the technical solutions, and are not limited to the specific implementation methods. For those skilled in the art, on the basis of the above description, different forms of changes or variations can be made, and it is not necessary or possible to exhaust all the embodiments. Any skilled person in the art can make equivalent replacement or change within the technical range disclosed by the application, and the obvious changes or variations derived from the technical solutions and methods provided by the application should be covered within the protection scope of the application.

Claims

1. A border defense information exchange system, characterized by: The monitoring station system module and the monitoring center system service module communicate through a TCP protocol network; The monitoring station system module classifies and encapsulates the obtained data into multiple data classes according to the border defense business, and the monitoring center system service module processes the data according to the data classes; The monitoring center system service module realizes network communication based on an information exchange service; the information exchange service includes an information exchange server, an information exchange client, an information exchange interface, and a service monitoring interface; the information exchange server and the information exchange client transmit general protocol information structure data packets through a TCP protocol; The data packets transmitted through the TCP protocol are composed of a packet header and a data block, and the length of the data packet is not greater than 2K bytes, wherein: The packet header is composed of a packet identifier, a version number, a packet ID, a total number of packets, a packet number, and a packet length, and the packet IDs of all packets of the same protocol message must be the same; The data block is composed of a data header and a data record; The data structure of the packet header is that the first 3 bytes are the packet identifier, indicating a border defense general protocol transmission data packet, the 4th byte is the version number, represented by a hexadecimal number, the version number is 1.0 represented by 0x10, the 5th to 10th bytes are the packet header identifier ID, the high 24 bits represent the information source code of the monitoring center / monitoring station at each level, and the low 24 bits are a cyclic count of 0~0xffffff, the 11th byte is the total number of packets with the same packet ID, the 12th byte is the sequential number of the current packet, and the 13th to 14th bytes are the total length of the current packet including the packet header length; the data header is composed of a protocol version number, a protocol data class, and a data block length, and is fixed at 6 bytes, wherein the 1st byte is the protocol version number, the 2nd byte is the data class transmitted, and the 3rd to 6th bytes are the total length of the data block including the data header.

2. The coastal defense information exchange system according to claim 1, wherein: The information exchange server is deployed in the monitoring center system, realizes the connection of the client of the monitoring station and the center business application seat, sends a heartbeat packet to the client, maintains the network link, transmits and receives the client information, unpacks and packages the received / sent information according to the general protocol format, distributes it to the corresponding destination IP address, records the online state of the client and the data packet information transmitted / received, and monitors the service state; The information exchange client is deployed in the monitoring station and the center business application seat, and is used to connect the information exchange server to realize the information transmission and reception function between the monitoring station and the monitoring center; the information exchange service interface is used for the business application seat to transmit and receive information through the information exchange server; and the service monitoring interface displays the service state and related information of the information exchange service to the interface window, including the client list connected to the service and the data information exchanged between the client and the server.

3. A border defense information exchange method applied to the border defense information exchange system according to any one of claims 1 to 2, characterized in that: The monitoring center system service module realizes the client connection of the monitoring station and the center business application seat based on the information exchange service process, sends the heartbeat packet to the client, maintains the network link, transmits and receives the client information, unpacks and packages the received / sent information according to the general protocol format; the monitoring station system module realizes the information transmission and reception between the monitoring station and the monitoring center based on the information exchange access process.

4. The coastal defense information exchange method according to claim 3, characterized by: The information exchange service process is specifically as follows: (1) creating a TCP service socket, listening to at least two service ports, one of which is used for monitoring station client connection, and the other is used for center business application seat client connection; (2) creating a TCP client socket, connecting the service port of the upper center service end, and forwarding the information received by the center to the upper level according to the related business process requirements; (3) listening to the network event message of the service end and the client, and cyclically detecting whether the client is connected to the service end and whether the connection to the upper center service end is successful; (4) when detecting that the client requests connection, processing the connection request of the client and establishing connection with the client, and adding the client to the client connection list; (5) starting a daemon thread, sending a heartbeat packet to the client at a regular time, receiving the heartbeat packet information sent by the client, and judging whether the client network connection is normal; (6) if no client heartbeat packet is received or the client connection is timed out, closing the client connection, deleting the client from the client connection list, and notifying the monitoring center that the client has lost connection; (7) if the client connection is normal, receiving the message sent by the client, and buffering the received data packet in the received information buffer area; (8) calling the service end unpacking service program, extracting the data in the data block from the received information buffer area according to the general protocol data packet information structure, and restoring it to the corresponding data class business information; (9) calling the business logic processing program for related business processing, converting the data into corresponding business information, and displaying the business information content on the user interface.

5. The coastal defense information exchange method according to claim 3, characterized by: The information exchange access process is specifically as follows: (1) creating a TCP socket, connecting the service port of the information exchange service end, the site service port of the service end connected by the client of the monitoring station, and the seat service port of the service end connected by the client of the center business application seat; (2) listening to the service end information in an asynchronous and event manner; (3) if the connection to the service end is successful, sending a heartbeat packet to the service end at a regular time to maintain the long connection with the service end; (4) receiving the monitoring center command or message data sent by the information exchange service end, and delivering the information to the monitoring station business application; (5) packaging the information reported by the monitoring station business application into a general protocol data packet, and sending it to the information exchange service end, and delivering it to the monitoring center business application seat for display after the service end unpacks the information.

6. The coastal defense information exchange method according to claim 3, characterized by: In the information exchange service process and the information exchange access process, the following methods are used to realize the underlying information transmission: a. receiving the byte information to be sent from the information exchange interface; b. adding the information to be sent to the sending data buffer; c. cyclically detecting whether there is information to be sent in the sending buffer; d. If so, take the information to be sent from the sending buffer, otherwise, return to step c; e. Determine whether the length of the information to be sent is greater than the packet length, i.e. whether it needs to be packetized; f. If it needs to be packetized, split the data into several packets no more than 2k, otherwise go directly to step g; g. Add a packet header to the data to be sent, and package the data according to the general protocol packet format; h. Send the general protocol packet information to the destination IP address in an asynchronous manner; i. Delete the sent byte information from the sending buffer; In the information exchange service process and the information exchange access process, the following method is used to implement the underlying information receiving: A. Start receiving data from the network socket; B. Determine whether the information is received and the port is normal, if the port is not normal, exit the receiving process and close the port; C. Read the information from the network socket to the receiving buffer for processing; D. Determine whether the length of the received information is greater than the length of a packet header, if so, go to the next step, otherwise return to step A; E. Determine whether the first three bytes are packet identifiers, if so, go to the next step, otherwise remove the three bytes from the receiving buffer and return to step D; F. Extract the packet header from the receiving buffer to obtain the packet length information; G. Determine whether the length of the received information is greater than or equal to the packet length, if so, go to the next step, otherwise return to step A; H. Read the data block to obtain the number of packets and the total number of packets; I. Remove a data packet from the receiving buffer; J. Merge the data packet into the packet ID buffer belonging to the port; K. Determine whether it is the last packet, if so, go to the next step, otherwise return to step D; L. Merge the data into the data packet disassembly service processing, and then jump to step D to receive the data packet.

Images