CN111031122A

CN111031122A - Ship data processing method and device

Info

Publication number: CN111031122A
Application number: CN201911233730.5A
Authority: CN
Inventors: 郑树剑
Original assignee: Beijing Highlandr Digital Technology Co ltd
Current assignee: Beijing Highlandr Digital Technology Co ltd
Priority date: 2019-12-05
Filing date: 2019-12-05
Publication date: 2020-04-17
Anticipated expiration: 2039-12-05
Also published as: CN111031122B

Abstract

The embodiment of the invention provides a ship data processing method and device. The processing method of the ship data on the server side of the shore-based data processing center comprises the following steps: acquiring first data information of ships in different local area networks, wherein the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network; and distributing the first data information of the ships in different local area networks to clients of the ships in each local area network. The scheme of the invention can realize that the shore end can obtain the distribution data as required, and simultaneously ensure that the communication can be carried out between the ships in different local area networks.

Description

Ship data processing method and device

Technical Field

The present invention relates to the field of ship communication technologies, and in particular, to a method and an apparatus for processing ship data.

Background

The intelligent ship has clear technical requirements that the ship and the shore are combined together through a network, and all sensing data on the ship are simultaneously sent to a shore-based platform; and the shore base combines the big data analysis technology, and plays a role in aspects of route and speed optimization, auxiliary driving and collision avoidance, support guarantee, operation management and the like. Through continuous ship data collection, one or more virtual digital ships can be constructed on a shore base, the running state of the ships is continuously tracked and analyzed, the future sailing process is pre-judged, and an auxiliary decision is given.

However, in the actual use process, the shore-based application sometimes needs to acquire the ship-side application, and usually the shore-based application allows a certain time delay, but the standard DDS protocol cannot adapt to such a scenario, and the ship are respectively located in one local area network, and there is no communication connection between these local area networks, so that the ship and the ship located in different local area networks cannot communicate with each other.

Disclosure of Invention

The invention provides a ship data processing method and device. The shore end can acquire distribution data as required, and communication between ships in different local area networks is guaranteed.

To solve the above technical problem, an embodiment of the present invention provides the following solutions:

a ship data processing method is applied to a shore-based data processing center server, wherein the shore-based data processing center server is positioned in a first local area network and is provided with a fixed public network IP address; the method comprises the following steps:

acquiring first data information of ships in different local area networks, wherein the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network;

and distributing the first data information of the ships in different local area networks to clients of the ships in each local area network.

Optionally, the acquiring first data information of ships located in different local area networks includes:

establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection;

and acquiring first data information of ships in different local area networks based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

Optionally, the distributing the first data information of the ships in different local area networks to the clients of the ships in each local area network includes:

and distributing the first data information of the ships in different local area networks to clients of the ships in each local area network based on the QUIC connection.

Optionally, establishing a QUIC connection between different local area networks and the shore-based data processing center server includes:

receiving an initialization connection request sent by clients of ships in different local area networks;

sending a server certificate of the shore-based data processing center server to clients of ships located in different local area networks;

receiving verification certificates fed back by clients of ships located in different local area networks;

if the verification certificate shows that verification is successful, the QUIC connection is established successfully, and the relevant information of the QUIC connection is synchronously established with the client sides of the ships in different local area networks;

and if the verification certificate indicates that the verification is not successful, establishing the QUIC connection between a different local area network and the shore-based data processing center server again.

Optionally, reestablishing a QUIC connection between a different local area network and the shore-based data processing center server includes:

receiving encrypted greeting messages sent by clients of ships located in different local area networks;

returning evaluation content to the client of the ship in different local area networks;

and establishing QUIC connection between different local area networks and the shore-based data processing center server again according to the evaluation content.

Optionally, the ship data processing method further includes: based on the QUIC connection, if a data packet between the shore-based data processing center server and a client of a ship located in a different local area network is lost, sending an acknowledgement frame to the client of the ship located in the different local area network requesting to stop negatively acknowledging the data packet.

Optionally, in the process of establishing the QUIC connection, the method further includes:

sending a first data packet, wherein the first data packet is an authenticated encryption certificate;

sending a second data packet, the second data packet containing a request for encrypted content;

if the client of the ship in different local area networks does not receive the first data packet and/or the second data packet, the QUIC connection is not established; otherwise, the QUIC connection is established.

The embodiment of the invention also provides a ship data processing device, which is applied to a shore-based data processing center server, wherein the shore-based data processing center server is positioned in the first local area network and is provided with a fixed IP address; the device comprises:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first data information of ships in different local area networks, and the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network;

and the processing module is used for distributing the first data information of the ships in different local area networks to clients of the ships in each local area network.

Optionally, the obtaining module is configured to: establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection;

Optionally, the processing module is configured to distribute the first data information of the ships located in different local area networks to clients of the ships in each local area network based on the QUIC connection.

The embodiment of the invention provides a ship data processing method, which is applied to a client of a ship in a local area network, and comprises the following steps:

sending first data information of a ship to a shore-based data processing center server, wherein the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network; the shore-based data processing center server is positioned in a first local area network and is provided with a fixed IP address, and the IP address of the local area network where the ship is positioned is dynamically distributed;

and receiving first data information of the ships in different local area networks, which is sent by the shore-based data processing center server.

Optionally, sending the first data information of the ship to the shore-based data processing center server includes:

and sending first data information of the ship to a shore-based data processing center server based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

Optionally, receiving first data information of the ships located in different local area networks, which is sent by the shore-based data processing center server, includes:

and receiving first data information of the ships in different local area networks, which is sent by the shore-based data processing center server, based on the QUIC connection.

Optionally, the ship data processing method further includes: and the client of the ship in the second local area network transmits the ship data with the client of the ship in the third local area network according to the received first data information of the client of the ship in the third local area network.

Optionally, the transmitting the ship data with the client of the ship located in the third local area network includes: and transmitting ship data with the client of the ship in the third local area network based on a ship-borne network data subscription type communication protocol DSCP.

Optionally, the transmitting the ship data with the client of the ship located in the third local area network based on a ship-borne network data subscription type communication protocol DSCP includes:

the ship in the second local area network and the ship in the third local area network establish DSCP connection based on a ship-borne network data subscription type communication protocol DSCP;

based on the DSCP connection, the equipment information in the first equipment set of the ship in the second local area network is published in a global data space, and the equipment information in the second equipment set of the ship in the third local area network published by the client of the ship in the third local area network is obtained from the global data space.

Optionally, the data formats of the device information in the first device set and the device information in the second device set both include: a domain information field, a domain participant information field, a topic field, a data publisher field, and a data subscriber field.

The embodiment of the present invention further provides a device for processing ship data, which is applied to a client of a ship located in a local area network, and the device includes:

the system comprises a sending module, a processing module and a processing module, wherein the sending module is used for sending first data information of a ship to a shore-based data processing center server, and the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network; the shore-based data processing center server is positioned in a first local area network and is provided with a fixed public network IP address, and the IP address of the local area network where the ship is positioned is dynamically distributed;

and the receiving module is used for receiving the first data information of the ships in different local area networks, which is sent by the shore-based data processing center server.

Optionally, the sending module is configured to: establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection; and sending first data information of the ship to a shore-based data processing center server based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

Optionally, the receiving module receives, based on the QUIC connection, the first data information of the ships located in different local area networks, which is sent by the shore-based data processing center server.

Optionally, the client of the ship located in the second local area network further includes:

and the processing module is used for transmitting the ship data with the client of the ship in the third local area network according to the received first data information of the client of the ship in the third local area network.

Optionally, the transmitting the ship data with the client of the ship located in the third local area network includes:

and transmitting ship data with the client of the ship in the third local area network based on a ship-borne network data subscription type communication protocol DSCP.

An embodiment of the present invention further provides a system for processing ship data, including:

a shore-based data processing center server, the shore-based data processing center server being in a first local area network and having a fixed IP address; and

the IP addresses of the local area networks where ships are located are dynamically allocated to the clients of the ships in different local area networks; the local area network where the ship is located is different from the first local area network;

the shore-based data processing center server comprises the ship data processing device;

the client for the ship located in the local area network comprises the processing device of the ship data.

Embodiments of the present invention also provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the method as described above.

The scheme of the invention at least comprises the following beneficial effects:

according to the scheme, first data information of ships in different local area networks is obtained through a shore-based data processing center server, and the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network; and distributing the first data information of the ships in different local area networks to clients of the ships in each local area network. Therefore, the shore end can be reached, the distributed data can be acquired as required, and communication between ships in different local area networks can be guaranteed.

Drawings

Fig. 1 is a flowchart of a processing method of ship data at a server side of a shore-based data processing center according to an embodiment of the present invention;

fig. 2 is a schematic networking diagram of a shore-based data processing center server and a local area network in which each ship is located according to an embodiment of the present invention;

FIGS. 3-6 are flow diagrams of four phases of the QUIC protocol according to an embodiment of the present invention;

FIG. 7 is a block diagram of a ship data processing device on the server side of the base data processing center according to an embodiment of the present invention;

FIG. 8 is a flow chart of a method for processing ship data at a client side of a ship located in a local area network according to an embodiment of the present invention;

FIG. 9 is a diagram illustrating an implementation architecture of a DSCP protocol according to the present invention;

fig. 10 is a block diagram of a ship data processing device located on a client side of a ship in a local area network according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

As shown in fig. 1, an embodiment of the present invention provides a ship data processing method, which is applied to a shore-based data processing center server, where the shore-based data processing center server is located in a first local area network and has a fixed IP address; the method comprises the following steps:

step 11, acquiring first data information of ships in different local area networks, wherein the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network;

and 12, distributing the first data information of the ships in different local area networks to clients of the ships in each local area network.

In the embodiment, first data information of ships in different local area networks is acquired through a shore-based data processing center server, wherein the first data information is address information of the local area network where the ships are located; the local area network where the ship is located is different from the first local area network; and distributing the first data information of the ships in different local area networks to clients of the ships in each local area network. Therefore, the shore end can be reached, the distributed data can be acquired as required, and communication between ships in different local area networks can be guaranteed.

In an alternative embodiment of the present invention, step 11 may include:

step 111, establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection;

and 112, acquiring first data information of ships in different local area networks based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

In an alternative embodiment of the present invention, step 12 may include:

and 121, distributing the first data information of the ships in different local area networks to clients of the ships in each local area network based on the QUIC connection.

Ship-shore communication based on a QUIC (Quick UDP Internet Connection, UDP network Connection) protocol is adopted between ships and the shore, and the ship-shore communication is a new UDP-based multiplexing and safe transmission protocol. The TCP/IP protocol suite is the foundation of the internet, with transport layer protocols including TCP and UDP protocols. UDP is more lightweight than TCP, but error checking is much less. This means that UDP tends to be more efficient (not always communicating with the server side to see if packets are delivered or in order), but less reliable than TCP. QUIC addresses well the various requirements faced by today's transport and application layers, including handling more connections, security and low latency. QUIC incorporates features of protocols including TCP, TLS, HTTP/2, etc. One of the main goals of QUIC is to reduce connection delay, and when a client first connects to a server, QUIC requires only 1RTT (Round-Trip Time) of delay to establish a reliable and secure connection, which is faster than 1-3 RTTs of TCP + TLS. The client may then locally cache the encrypted authentication information, and may implement a 0-RTT connection establishment delay when establishing a connection with the server again. QUIC simultaneously multiplexes the Multiplexing function of the HTTP/2 protocol (Multiplexing), but avoids the Head-of-line blocking (Head-of-line blocking) problem of HTTP/2 since QUIC is based on UDP. Because the QUIC is based on UDP and runs in a user domain instead of a system kernel, the QUIC protocol can be updated and deployed rapidly, and the difficulty of TCP protocol deployment and updating is well solved.

In an optional embodiment of the present invention, the step 111 may include:

step 1111, receiving an initialization connection request sent by a client of a ship in different local area networks;

step 1112, sending the server certificate of the shore-based data processing center server to the client of the ship located in different local area networks;

step 1113, receiving the verification certificate fed back by the client of the ship in different local area networks;

step 1114, if the verification certificate indicates that the verification is successful, establishing the QUIC connection successfully, and synchronously establishing the relevant information of the QUIC connection with the client of the ship in the different local area networks;

and 1115, if the verification certificate indicates that the verification is not successful, establishing QUIC connection between different local area networks and the shore-based data processing center server again.

Wherein reestablishing a QUIC connection between a different local area network and the shore-based data processing center server comprises:

step 11151, receiving the encrypted hello message sent by the client of the ship in different local area networks;

step 11152, returning the evaluation content to the client of the ship in different local area networks;

step 11153, according to the evaluation content, establishing QUIC connection between different local area networks and the shore-based data processing center server again.

In an optional embodiment of the present invention, the method for processing ship data may further include:

step 1116, based on the QUIC connection, if a data packet between the shore-based data processing center server and the client of the ship located in the different local area network is lost, sending an acknowledgement frame to the client of the ship located in the different local area network requesting to stop negatively acknowledging the data packet.

In the process of establishing the QUIC connection, the method further comprises the following steps:

step 1117, send the first data packet, the said first data packet is the encryption certificate authenticated;

step 1118, sending a second data packet, said second data packet comprising an encrypted content request;

step 1119, if the client of the ship in different local area networks does not receive the first data packet and/or the second data packet, the QUIC connection is not established; otherwise, the QUIC connection is established.

The following describes the implementation process of the above embodiment with reference to fig. 2 to 6:

FIG. 2 is a schematic diagram of a networking of a shore-based data processing center server with a local area where each ship is located, the shore-based data processing center server being in a first local area network (such as DDS03) and having a fixed public network IP address; the local area network where the ship is located is different from the first local area network, and here, taking a second local area network (for example, DDS01) where the ship is located and a third local area network (for example, DDS03) where the ship is located as examples for explanation, two DDS01 and DDS02 represent data distribution nodes of two ships, a plurality of clients are located under the local area network of each ship, and the clients of the local area networks communicate through multicast.

The shore-based data processing center server needs to be provided with a registration center of a fixed public network IP, and the DDS01 and DDS02 can be ensured to be communicated with the registration center through UDP.

The client in the ship local area network allows the client located behind the NAT (or multiple NATs) to find out the public network address of the client through a STUN (Session Traversal application for NAT, NAT Session Traversal application) protocol, and find out which type of NAT the client is located in and the Internet port bound by the NAT as a certain local port. This information is used to create UDP communications between two hosts that are simultaneously behind a NAT router.

And successfully penetrating the local area network to obtain a communication port of the external network. The premise of the aspect is that the NAT structure of the local area network is required to be asymmetric NAT or set on a firewall of the local area network, and a port for sending data and a port for receiving data of an intranet machine through a public network are guaranteed to be unchanged.

The unified communication SDK is provided, the penetration process of the bottom layer is not required to be sensed for upper layer application, a user only needs to call a corresponding interface when needing ship-shore data transmission, the shore-based data return is the same, the data interface is directly accessed to send the data to the ship end, and the communication details of the bottom layer are not required to be concerned.

The ship-shore communication adopts QUIC protocol to ensure low delay and channel multiplexing of connection, TLS1.3 is adopted to ensure data transmission safety, and QUIC + TLS1.3 eliminates delay of a safety transmission layer.

As shown in fig. 3, 4, 5, 6, there are four phases for the QUIC protocol, where, as shown in fig. 3, the first connection at startup: a hello message (negotiation information, one or more requests) is initialized, the server returns a hash chain certificate and proves that the recipient controls the target client IP port. The client verifies the server certificate, if the verification fails, 2RTT is entered, and a request and a synchronous cookie are sent. It should be noted that, the client and the server are in a client and server mode, for example, the server here may be a client of the shore-based data processing center server, the shore-based data processing center server may be installed with a plurality of clients, and the shore-based data processing center server is in a multicast relationship with each client thereof; the number of the clients of the ships in different local area networks can be multiple, and the clients of the local area networks and the ships are also in multicast relation. In the step 1111, the client of the shore-based data processing center server may specifically receive an initialization connection request, that is, an initialization hello message, sent by the client of a ship located in a different local area network. In step 1112 above, the server certificate is the hash chain certificate here.

As shown in fig. 4, upon repeated connections, the client will speculate that the server is still using that visible and authenticated certificate. The client has proof of possession that it controls the return IP address and port. The server receives the packet and evaluates its contents. If the guessed server public key is no longer used or the negotiation result from the message is not accepted by the server, the server may reject the content of the data packet. Returning to the first connection, the received packet is discarded.

As shown in fig. 5, when the connection is in a stable state and packet loss occurs, the client confirms that the hash table is correct and declares that the packet k is lost. An acknowledgement frame is sent requesting the server to stop negatively acknowledging packet k.

As shown in fig. 6, for the active speculative retransmission process, the client sends a first packet, i.e. the authenticated encryption certificate, and then sends a second packet, which contains the encrypted content request, and if the server does not receive any of the packets, the connection will not be established, or at least the content will not be requested in time. The client may wait for a short actual and resend both connection start packets.

Acknowledgements of received data are sent periodically and when no acknowledgement is received, the timeout may be retransmitted autonomously. The QUIC also adds a heartbeat packet on the basis of a congestion avoidance algorithm for reducing the packet loss rate. QUIC uses FEC (Forward error correction code) to recover data, which uses simple XOR. After a group of data including a plurality of data packets is sent each time, the data packets are subjected to exclusive OR operation in sequence, and the final result is used as an FEC packet to be sent out. After the receiving party receives a group of data, the checking and error correction can be carried out according to the data packet and the FEC packet.

In the above embodiment of the present invention, quac (quick UDP Internet connection) protocol is used for ship-shore communication to ensure low latency and channel multiplexing of connection.

As shown in fig. 7, an embodiment of the present invention further provides a ship data processing apparatus 70, which is applied to a shore-based data processing center server, where the shore-based data processing center server is located in a first local area network and has a fixed IP address; the device 70 comprises:

an obtaining module 71, configured to obtain first data information of a ship located in different local area networks, where the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network;

and the processing module 72 is configured to distribute the first data information of the ships located in different local area networks to clients of the ships in each local area network.

Optionally, the obtaining module 71 is configured to: establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection;

Optionally, the processing module 72 is configured to distribute the first data information of the ships located in different local area networks to clients of the ships in each local area network based on the QUIC connection.

Optionally, the processing module 72 is further configured to: based on the QUIC connection, if a data packet between the shore-based data processing center server and a client of a ship located in a different local area network is lost, sending an acknowledgement frame to the client of the ship located in the different local area network requesting to stop negatively acknowledging the data packet.

It should be noted that the apparatus is an apparatus corresponding to the method shown in fig. 1, and all the implementations in the above method embodiment are applicable to the embodiment of the apparatus, and the same technical effects can be achieved.

As shown in fig. 8, an embodiment of the present invention provides a method for processing ship data, which is applied to a client of a ship located in a local area network, and the method includes:

step 81, sending first data information of the ship to a shore-based data processing center server, wherein the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network; the shore-based data processing center server is positioned in a first local area network and is provided with a fixed IP address, and the IP address of the local area network where the ship is positioned is dynamically distributed;

and step 82, receiving first data information of the ships in different local area networks, which is sent by the shore-based data processing center server.

In an alternative embodiment of the present invention, step 81 may include:

step 811, establishing a QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is a fast User Datagram Protocol (UDP) network connection;

and 812, sending first data information of the ship to a shore-based data processing center server based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

In an alternative embodiment of the present invention, step 72 may comprise:

and 821, receiving first data information of the ships in different local area networks, which is sent by the shore-based data processing center server, based on the QUIC connection.

and 83, the client of the ship in the second local area network transmits the ship data with the client of the ship in the third local area network according to the received first data information of the client of the ship in the third local area network.

Here, the data formats of the device information in the first device set and the device information in the second device set each include: a domain information field, a domain participant information field, a topic field, a data publisher field, and a data subscriber field.

The following describes a specific implementation process of this embodiment with reference to fig. 2 and fig. 9:

as shown in fig. 2, the client of the ship in DDS01 obtains the IP address of the ship in DDS02 based on the interaction with the shore-based data processing center server, so that any client of the ship in DDS01 can directly obtain the data of any client of the ship in DDS02 based on the DSCP connection. Each ship-side client has a security certificate to ensure the security of the access identity.

Each client of the ship in the DDS01 will issue its own data to the global data space, each client of the ship in the DDS02 will issue its own data to the global data space, and each client of the ship will obtain its own required data from the global data space.

Specifically, as shown in fig. 9, the global data space is composed of a publish/subscribe registry, a published data buffer, and a received data buffer. The publish/subscribe registry records main characteristics of all publish/subscribe message topics, publisher/subscriber addresses and the like, such as data validity period, message priority, real-time/reliability requirements and the like, and the publish/subscribe topic tables on all hosts are kept consistent and updated in real time; the published data buffer area stores the sending data published by the host and required to be stored, namely the sending data still needs to be kept for a period of time after being published, the data correctly requested by a subscriber in the period of time is supported, and the global data space dynamically deletes or updates the data according to the validity period of the data; the receive data buffer is an indispensable data buffer queue, and the global data space allocates one such queue for each subscribing process to buffer messages that it receives but fails to process in time.

Each DSCP application stores only the data it needs locally, and provides to any application within the entire network when they need them. All data distribution work is done by the DSCP. A global data space is a virtual concept, actually a collection of local storage. Each application, which can be written in almost any language, runs on any system and can read the data displayed in the best data format in local memory. The global data space may share data among embedded systems, mobile and cloud applications, using any transmission means, regardless of language and system, ensuring extremely low latency.

The DSCP infrastructure is a domain (domain) uniquely identified by a domain number. The domain binds the application programs together for communication, only communication entities in the same domain can communicate, and no logical relationship exists among entities in different domains.

The DSCP is composed of a domain, domain participants, a topic, a data writer, and a data reader, as shown in fig. 4.

Domain: the domain establishes a virtual network linking all DDS applications that join it. Colloquially, a domain represents a group of applications that communicate with each other. Only applications in the same domain can communicate.

The domain participants: entry points for applications to interact within a certain domain. Each domain participant may have one or more publishers or subscribers.

Subject matter: topics are the fundamental means of data interaction between publishing and subscribing applications, and each topic has a unique name and a specific data type in a domain. Each topic data type can specify 0 or more fields as keys, when data is published, a publishing terminal needs to specify a topic, and a subscribing terminal subscribes to the data through the topic. In the DCPS model, multiple different data samples of the same topic can be sent through different instances, each instance having a unique key. Multiple data samples published on the same instance all use the same key value. A topic consists of a topic name, a topic type, one or more QoS policies. The topic name is a character string which can uniquely identify the topic in the domain, the topic type is the definition of topic data, and each topic can be associated with a corresponding QoS strategy.

Data writer, data publisher (datawriter): the data writers are release-typed accessors, each data writer is only associated with a specific theme, and therefore only has one data type. The application publishes the data instance of the associated topic through a particular type of interface of the data writer. The data writer is responsible for transmitting the data to the publisher, the publisher distributes the data, and the publisher distributes the data according to the QoS of the publisher and the QoS of the corresponding data writer.

Data reader, subscriber (datareader): data readers are DCPS entities that are used to retrieve data received by subscribers and pass the data to applications, each data reader being bound to a particular topic, i.e., each data reader is only interested in the type of data that it is interested in. The subscriber is responsible for receiving data from the publisher and then passing the received data to the corresponding data reader, thereby enabling the application to obtain the data in which it is interested. The data reader can obtain the data to which it subscribes in both Listener and Waitset ways.

All members in the DSCP are entries, and any two entries in the DSCP must interact within the same domain. The domain owner pointer in the domain is the entry point of the service, and any DSCP application needs to first obtain the domain owner pointer and then obtain other services such as publisher, subscriber, topic, etc. through the domain participant.

The domain participants, which are the entry points of the data distribution service, include several publishers, subscribers and registration topics, responsible for creating, deleting and managing these entities.

The publisher acts as a publisher, contains at least one DataWriter, and is responsible for creating, deleting, and managing data writers. Similarly, the subscriber is associated with at least one datareader and is responsible for publishing data, the data publisher publishes the data by calling the write function of the data reader, but the data is not immediately sent out, and the actual message generation is comprehensively controlled by the publisher and the Qos. The data reader is responsible for subscribing data, and the subscribing mode can adopt three modes, namely an asynchronous mode (listener), a synchronous mode and a non-blocking mode.

In the above embodiment of the present invention, the formats of the device information in the first device set and the device information in the second device set are as follows:

the devices can be various devices on the ship, such as sensors, position sensors and the like, the device entities are described in Objects, the devices are grouped according to an access mode, the devices in the same class are divided into a group, the devices in each group contain specific functions and refer to device types, a single function corresponds to several computing units, and the description of the units refers to the types as the specific values.

For example: the Modbus devices can access the server through interfaces such as a TCP port, an RS232 interface, an RS485 interface and the like, the devices are divided into 3 groups according to an access mode, the Modbus devices in each group refer to device types in types for description, registers contained in each component of the devices refer to register value types in type nodes according to the description of the registers.

OPC UA has three coding modes: binary coding, XML coding, JSON coding, hereinafter XML coding, may allow different programs, platforms and people to use without hindrance. XML documents have a standardized structure, and each program or platform has an interpreter that interprets XML. The following is the predefined file part content of an address space:

the Modbus device Dev1 is shown and accessed in the form of RS232 interface, the alarm amount of the device contains a Register _1 (Register), the Register _1 value type is a self-defined MyRegisterValueType type and contains two variables of mType (Register type) and start-end (start-stop address); the Device Dev1 is a COM _ Device type of the custom MyObjectType, which contains two variables, COM _ Device and TCP _ Device, with their attributes being Baudrate, DevID, Dataset and transit mode, and TCP having their attributes being DevID, IP.

On the basis of an OPC UA information model, the composition of a protocol data packet comprises data description and data types, JSON format data and the data description are in a corresponding relation, a user analyzes the data according to the data description after taking the data, and the specific data packet format is shown in table 1:

table 1 data format of structured data packet

The "data description" is a detailed description of "JSON-format data", and each key value pair of the JSON data is described, including a data type, a name, a unit, a composition form, and the like of the key value. The "data type" includes a basic data type and a complex data type, and may be a generic protocol name or a pre-agreed object name.

For example: a piece of GPS data, having a standard data protocol, may be in a data format as shown in table 2:

table 2 data format of GPS statement example

In the embodiment of the invention, the Ship can acquire Data of other ships across the local area network, and the distribution of the Ship Data across the local area network is realized based on a Data Subscription Protocol (Data Subscription Communication Protocol for Ship-borne network) Protocol.

As shown in fig. 10, an embodiment of the present invention further provides an apparatus 100 for processing ship data, which is applied to a client of a ship located in a local area network, where the apparatus 100 includes:

the sending module 101 is configured to send first data information of a ship to a shore-based data processing center server, where the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network; the shore-based data processing center server is positioned in a first local area network and is provided with a fixed IP address, and the IP address of the local area network where the ship is positioned is dynamically distributed;

a receiving module 102, configured to receive the first data information of the ships located in different local area networks, where the first data information is sent by the shore-based data processing center server.

Optionally, the sending module 101 is configured to: establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection; and sending first data information of the ship to a shore-based data processing center server based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

Optionally, the receiving module 102 receives, based on the QUIC connection, first data information of the ships located in different local area networks, which is sent by the shore-based data processing center server.

the processing module 102 is configured to transmit ship data with the client of the ship located in the third local area network according to the received first data information of the client of the ship located in the third local area network.

It should be noted that the apparatus is an apparatus corresponding to the method shown in fig. 8, and all the implementations in the above method embodiment are applicable to the embodiment of the apparatus, and the same technical effects can be achieved.

As further shown in fig. 2, an embodiment of the present invention further provides a system for processing ship data, including:

a shore-based data processing center server (e.g., DDS03) in a first local area network having a fixed IP address; and

clients of ships located in different local area networks (e.g., DDS01 and DDS02), IP addresses of local area networks where the ships are located are dynamically assigned; the local area network where the ship is located is different from the first local area network;

the application to a shore-based data processing center server includes an apparatus as described above in fig. 7;

the client applied to the ship located in the local area network comprises the device as described in the above fig. 9.

It should be noted that all the implementations in the above embodiments are applicable to the embodiment of the system, and the same technical effect can be achieved.

Embodiments of the present invention also provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the steps of the method described above with respect to fig. 1 or 8. All the implementation manners in the above method embodiment are applicable to this embodiment, and the same technical effect can be achieved.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Furthermore, it is to be noted that in the device and method of the invention, it is obvious that the individual components or steps can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of performing the series of processes described above may naturally be performed chronologically in the order described, but need not necessarily be performed chronologically, and some steps may be performed in parallel or independently of each other. It will be understood by those skilled in the art that all or any of the steps or elements of the method and apparatus of the present invention may be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or any combination thereof, which can be implemented by those skilled in the art using their basic programming skills after reading the description of the present invention.

Thus, the objects of the invention may also be achieved by running a program or a set of programs on any computing device. The computing device may be a general purpose device as is well known. The object of the invention is thus also achieved solely by providing a program product comprising program code for implementing the method or the apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is to be understood that the storage medium may be any known storage medium or any storage medium developed in the future. It is further noted that in the apparatus and method of the present invention, it is apparent that each component or step can be decomposed and/or recombined. These decompositions and/or recombinations are to be regarded as equivalents of the present invention. Also, the steps of executing the series of processes described above may naturally be executed chronologically in the order described, but need not necessarily be executed chronologically. Some steps may be performed in parallel or independently of each other.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A ship data processing method is characterized in that the method is applied to a shore-based data processing center server, wherein the shore-based data processing center server is positioned in a first local area network and has a fixed public network IP address; the method comprises the following steps:

2. The method for processing ship data according to claim 1, wherein the acquiring first data information of ships located in different local area networks comprises:

3. The method according to claim 2, wherein distributing the first data information of the ships located in different local area networks to the clients of the ships in each local area network comprises:

4. Method for the processing of ship data according to claim 2 or 3, characterized in that establishing a QUIC connection between different local area networks and the shore-based data processing central server comprises:

5. The ship data processing method according to claim 4, wherein reestablishing a QUIC connection between a different local area network and the shore-based data processing center server comprises:

6. The ship data processing method according to claim 5, further comprising:

based on the QUIC connection, if a data packet between the shore-based data processing center server and a client of a ship located in a different local area network is lost, sending an acknowledgement frame to the client of the ship located in the different local area network requesting to stop negatively acknowledging the data packet.

7. The ship data processing method according to claim 6, wherein the process of establishing the QUIC connection further comprises:

8. The ship data processing device is applied to a shore-based data processing center server, wherein the shore-based data processing center server is positioned in a first local area network and is provided with a fixed public network IP address; the device comprises:

9. The ship data processing device according to claim 8, wherein the acquiring module is configured to establish a QUIC connection between different local area networks and the shore-based data processing center server, and the QUIC connection is a UDP network connection;

10. The ship data processing device according to claim 9, wherein the processing module is configured to distribute the first data information of ships located in different local area networks to clients of ships in respective local area networks based on the QUIC connection.

11. A method for processing ship data, applied to a client of a ship located in a local area network, the method comprising:

12. The ship data processing method according to claim 11, wherein sending the first data information of the ship to the shore-based data processing center server comprises:

13. The method for processing ship data according to claim 12, wherein receiving the first data information of the ships located in different local area networks sent by the shore-based data processing center server comprises:

14. The ship data processing method according to any one of claims 11 to 13, further comprising:

and the client of the ship in the second local area network transmits the ship data with the client of the ship in the third local area network according to the received first data information of the client of the ship in the third local area network.

15. The method of claim 14, wherein the transmitting the ship data with the client of the ship in the third local area network comprises:

16. The ship data processing method of claim 15, wherein the ship data transmission with the client of the ship in the third local area network based on an on-board network data subscription communication protocol DSCP comprises:

17. The ship data processing method according to claim 16, wherein the data formats of the device information in the first device set and the device information in the second device set each include: a domain information field, a domain participant information field, a topic field, a data publisher field, and a data subscriber field.

18. An apparatus for processing ship data, applied to a client of a ship located in a local area network, the apparatus comprising:

the system comprises a sending module, a processing module and a processing module, wherein the sending module is used for sending first data information of a ship to a shore-based data processing center server, and the first data information is address information of a local area network where the ship is located; the local area network where the ship is located is different from the first local area network; the shore-based data processing center server is positioned in a first local area network and is provided with a fixed IP address, and the IP address of the local area network where the ship is positioned is dynamically distributed;

19. The ship data processing device of claim 18, wherein the sending module is configured to: establishing QUIC connection between different local area networks and the shore-based data processing center server, wherein the QUIC connection is fast User Datagram Protocol (UDP) network connection; and sending first data information of the ship to a shore-based data processing center server based on the QUIC connection, wherein the first data information is packaged by adopting a data format of a QUIC protocol.

20. The ship data processing device according to claim 19, wherein the receiving module receives the first data information of the ships located in different local area networks transmitted by the shore-based data processing center server based on the QUIC connection.

21. The ship data processing apparatus of any one of claims 18 to 20, wherein the client of the ship located in the second local area network further comprises:

22. The ship data processing device according to claim 21, wherein the transmitting of the ship data with the client of the ship located in the third local area network comprises:

23. A system for processing ship data, comprising:

a shore-based data processing center server, the shore-based data processing center server being in a first local area network and having a fixed public network IP address; and

the apparatus applied to a shore-based data processing center server comprises the apparatus of any one of claims 8 to 10;

the client for application to a ship located in a local area network comprises an apparatus as claimed in any one of claims 18 to 22.

24. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 7, or the method of any one of claims 11 to 17.