Communication method and system based on DDS, electronic equipment and storage medium

Abstract

The invention discloses a DDS-based communication method and system, an electronic device and a storage medium, and the method is applied to the DDS-based communication system, and comprises the steps: responding to a received data subscription demand of a data integration platform, and building a mapping relation between a data receiving and transmitting unit and the data integration platform through a target theme; reading target data stored under the target theme to a data integration platform; wherein the target data is published under the target theme by the data transceiving unit.

Description

Technical Field

[0001] The present application belongs to the field of ship communication technology, and specifically relates to a DDS-based communication method, a DDS-based communication system, an electronic device, and a computer-readable storage medium. Background Art

[0002] In the modern marine sector, data information systems have been widely used, and data integration platforms, as the core link in achieving ship informationization, play a vital role. In related technologies, ship data integration platforms typically connect multiple data transceiver units via Ethernet, utilizing a combination of serial communication, CAN networks, OPC UA, Modbus TCP, and other communication technologies to collect various types of data, and rely on data exchange methods such as UDP multicast and TCP unicast to complete information transmission.

[0003] However, due to the complexity and diversity of the communication protocol system, the system debugging process is difficult, and the reliability of data transmission is difficult to be fully guaranteed. These problems restrict the communication performance of the ship data integration platform. Summary of the Invention

[0004] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a DDS-based communication method, system, electronic device, and storage medium. By leveraging the multi-topic publish-and-subscribe mechanism of DDS communication technology, data sharing between data transceiver units and a data integration platform is achieved, reducing development costs and system complexity while improving data communication efficiency.

[0005] In a first aspect, an embodiment of the present application provides a DDS-based communication method, which is applied to a DDS-based communication system. The method includes:

[0006] In response to receiving a data subscription demand from the data integration platform, establishing a mapping relationship between the data transceiver unit and the data integration platform through the target topic;

[0007] The target data stored under the target topic is read into the data integration platform; wherein the target data is published under the target topic by the data transceiver unit.

[0008] In some embodiments, the method further comprises:

[0009] Obtain sensor types, sensor locations, and sensor usages of all sensors of the target ship;

[0010] Identify the topic for each sensor based on the sensor type, sensor location, and sensor purpose.

[0011] In some embodiments, the method further comprises:

[0012] In response to receiving a data release request, determining a sensor type, a sensor location, and a sensor usage represented by the data release request;

[0013] determining a target topic from the topics of all sensors according to the sensor type, sensor location, and sensor purpose characterized by the data release request;

[0014] The target data published by the data transceiver unit is stored in the target topic.

[0015] In some embodiments, after receiving the data publishing request, the method further includes:

[0016] Parsing the data publishing request to obtain the sensor type, sensor location, and sensor purpose indicated by the data publishing request;

[0017] A target topic is determined from topics of all sensors according to the sensor type, sensor location, and sensor purpose indicated by the data publishing request.

[0018] In some embodiments, the data transceiver unit includes at least one data publishing module, each of which manages at least one data writing submodule;

[0019] The data publishing module binds the target topic and provides the target data corresponding to the target topic;

[0020] The data writing submodule writes the target data to the target topic.

[0021] In some embodiments, the data integration unit includes at least one data subscription module, each data subscription module includes at least one data reading submodule;

[0022] The data subscription module is bound to the target topic;

[0023] The data reading submodule reads the target data stored under the target topic.

[0024] In some embodiments, the sensor of the target vessel includes at least one of a navigation sensor, a radar sensor, a communication sensor, and an electromechanical equipment sensor;

[0025] The method further comprises:

[0026] The data transceiver unit obtains target data from the sensor of the target ship through a preset communication protocol; wherein the preset communication protocol includes at least one of the TCP communication protocol, the UDP communication protocol, the CAN communication protocol, the OPC UA communication protocol, the OPC DA communication protocol, the HTTP communication protocol, the WebSocket communication protocol, the serial port communication protocol, the Modbus TCP communication protocol and the Modbus RTU communication protocol.

[0027] In a second aspect, an embodiment of the present application provides a DDS-based communication system, including:

[0028] a communication establishment module configured to establish a mapping relationship between the data transceiver unit and the data integration platform through a target topic in response to receiving a data subscription demand from the data integration platform;

[0029] The reading module is configured to read the target data stored under the target topic into the data integration platform; wherein the target data is stored under the target topic by the data transceiver unit.

[0030] In a third aspect, an embodiment of the present application provides an electronic device comprising: a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the DDS-based communication method as described in the first aspect are implemented.

[0031] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the DDS-based communication method as described in the first aspect are implemented.

[0032] The technical solution provided by this application, in response to receiving a data subscription request from a data integration platform, establishes a mapping relationship between a data transceiver unit and the data integration platform through a target topic. Furthermore, the target data stored under the target topic is read into the data integration platform; the target data is published by the data transceiver unit under the target topic. Through the multi-topic publish and subscribe mechanism of DDS communication technology, data sharing between the data transceiver units and the data integration platform is achieved, reducing development costs and system complexity and improving data communication efficiency.

[0033] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become obvious from the description below, or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0035] Figure 1 This is a schematic diagram of the ship data integration platform architecture in related technologies.

[0036] Figure 2 A schematic diagram of the DDS-based communication system framework provided in an embodiment of the present application.

[0037] Figure 3 A flow chart of a DDS-based communication method provided in an embodiment of the present application.

[0038] Figure 4 A schematic diagram of the DDS-based communication system structure provided in an embodiment of the present application.

[0039] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are for illustrative purposes only and are not intended to limit the scope of protection of the present application.

[0041] It should be understood that the various steps described in the method embodiments of the present application can be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0042] As described in the background technology section, the communication protocol between the data transceiver unit and the data integration platform is complex and difficult to debug, which affects the project delivery cycle. For example, in the related art, different data transceiver units may adopt a variety of communication protocols (such as serial communication, CAN network, OPC UA, etc.), which results in a lot of time required for protocol adaptation and debugging during system integration. In addition, sharing data between data transceiver units requires the addition of a new communication interface, which has a long development cycle and is difficult to debug. In the related art, data sharing between data transceiver units needs to be achieved through additional development interfaces, which not only increases development costs, but may also cause system stability problems. When the data integration platform uses UDP multicast to issue job plans, the data reliability is low and the transmission speed is slow. UDP multicast is prone to data loss, delays and other problems in the complex network environment of ships, affecting the real-time performance and accuracy of ship operations.

[0043] refer to Figure 1 , which is a schematic diagram of the ship data integration platform architecture in related technologies.

[0044] like Figure 1 As shown in FIG, the data transceiver unit and the data integration platform exchange data through multiple communication protocols. This ship data integration platform architecture leads to complex system architecture and low engineering implementation efficiency.

[0045] Data Distribution Service (DDS) is a new-generation distributed real-time communication middleware protocol. It adopts a publish / subscribe architecture, emphasizes data-centricity, and provides a rich set of QoS service quality policies to ensure real-time, efficient, and flexible data distribution, meeting the needs of various distributed real-time communication applications.

[0046] Based on the existing technology, the present invention adjusts the data interaction strategy between the data integration platform and the data transceiver unit, uses the DDS communication technology to design a distributed system architecture, and adopts the strategy of creating multiple topics in the DDS communication technology. The data transceiver unit publishes the collected data according to the designed topics, and the data integration platform obtains marine big data according to the topic name.

[0047] refer to Figure 2 , which is a schematic diagram of the DDS-based communication system framework provided in an embodiment of the present application.

[0048] As shown in the figure, to overcome the shortcomings of the above-mentioned traditional communication system framework, this application proposes a new communication system framework based on DDS. This framework can include several data transceiver units and several data integration platforms. In the global data space constructed by DDS, each data transceiver unit and data integration platform is connected to the topic through the DDS communication protocol.

[0049] In practice, commonly used data transceiver units include those for serial communication, CAN communication, HTTP and WebSocket communication, OPC UA communication, and UDP and TCP communication. The data transceiver units and the data integration platform are connected using optical fiber, and data exchange between them is accomplished using DDS communication technology. For example, in the case of ship communications, a fiber optic switch can be used on the ship to connect the various data transceiver units (such as a serial / CAN / OPC UA gateway). Onshore, optical fiber can be used to connect to the core server of the data integration platform, interconnecting it with the cloud-based DDS domain via a gateway.

[0050] refer to Figure 3 , which is a flow chart of the DDS-based communication method provided in an embodiment of the present application.

[0051] Step S301 : in response to receiving a data subscription demand from a data integration platform, a mapping relationship between a data transceiver unit and the data integration platform is established through a target topic.

[0052] In this step, when the data integration platform needs to obtain a specific type of data, it initiates a subscription request to the DDS middleware and specifies the topic name of interest (such as / vessel / SH001 / sensor / gps). After receiving the subscription request, the DDS middleware will dynamically scan all data transceivers in the DDS network that have published the topic, and automatically establish a logical connection between the publisher (data transceiver) and the subscriber (data integration platform). This process does not require pre-configuration of IP addresses or ports and is completely based on the dynamic discovery mechanism of DDS (such as the SPDP protocol). After the mapping relationship is established, all data published by the data transceiver to the topic will be automatically routed to the data integration platform.

[0053] The core of the mapping relationship is the target topic. Platforms declare their data requirements by subscribing to specific topics. The DDS middleware automatically discovers matching publishers in the network, eliminating the need for manual intervention. The DDS middleware verifies the compatibility of the publisher and subscriber's QoS policies (such as reliability and historical data retention). If incompatible, it may fall back to the lowest common QoS level or report an error.

[0054] Step S302: Read the target data stored under the target topic to the data integration platform; wherein the target data is published under the target topic by the data transceiver unit.

[0055] In this step, the data transceiver unit continuously publishes data (such as GPS coordinates, sensor readings, etc.) to the target topic (such as / vessel / SH001 / sensor / gps). After receiving the data, the DDS middleware pushes the data to the data integration platform that has subscribed to the topic based on the established mapping relationship. After receiving the data, the data integration platform can immediately process (such as real-time display) or store (such as writing to a database). If a historical data strategy such as TRANSIENT_LOCAL is configured during subscription and the publisher supports this strategy, the data integration platform can also obtain historical data cached by the publisher after subscription (such as data missed during disconnection).

[0056] The latency from data publishing to subscription is typically in the millisecond range (depending on the network and QoS configuration). DDS supports limiting the amount of data per unit time (e.g., a maximum of 1,000 data items per second) to avoid subscriber overload.

[0057] Furthermore, if a fiber optic connection is restored after a break, the DDS middleware automatically retransmits historical data from the disconnection period (subject to publisher cache support). This invention also uses sequence numbers to prevent duplicate data from being processed multiple times. DDS adds a timestamp to each piece of data, ensuring that subscribers process it in chronological order. Data can be delivered in the order it was published or in the order specified by the subscriber.

[0058] For example, the data integration platform needs to obtain GPS data from vessel SH001. The platform subscribes to the topic / vessel / SH001 / sensor / gps and configures the QoS to RELIABLE+TRANSIENT_LOCAL. The ship's GPS data transceiver continuously publishes data to this topic. The DDS middleware pushes the data to the platform, which stores it in the database and displays it on the monitoring interface.

[0059] During this process, if the fiber is disconnected, the platform can obtain the GPS data during the disconnection period through TRANSIENT_LOCAL after the connection is restored (assuming the transceiver unit has cached 100 historical data). If the publisher QoS is BEST_EFFORT and the platform requires RELIABLE, DDS will log a warning and fall back to BEST_EFFORT mode.

[0060] As an optional embodiment, the method further includes: obtaining sensor types, sensor locations, and sensor uses of all sensors of the target ship; and determining a subject of each sensor according to the sensor type, sensor location, and sensor use.

[0061] Specifically, ships are equipped with a large number of heterogeneous sensors (such as temperature, pressure, and position sensors). Traditional methods require manual configuration of topics for each sensor, which is inefficient, error-prone, and has poor scalability. This invention automatically generates standardized topics based on sensor metadata (type, location, and purpose), dynamically linking sensors with topics, reducing manual configuration costs and improving system maintainability.

[0062] Sensor data may include sensor type, sensor location, and sensor purpose. The sensor type describes the physical quantity measured by the sensor (such as temperature, pressure, GPS). The sensor location describes the physical installation path (such as / engine / room, / navigation / deck). The sensor purpose describes the business logic classification (such as engine_monitor, safety_alert). Other attributes of the sensor may include units (such as ℃, kPa), accuracy, sampling frequency, etc. Among them, the above-mentioned related sensor data can also be divided into static data and dynamic data. Static data can be structured information such as the sensor model, installation location, and design purpose obtained from the ship equipment database (such as CMDB). Dynamic data can be the real-time status of the sensor (such as online / offline, data sampling rate) obtained through the ship network protocol (such as DDS, MQTT) or the device API.

[0063] When naming topics, you can use a tree-like path to represent the sensor hierarchy, making it easier for subscribers to subscribe on demand. Topic names should directly reflect the sensor's system, location, and measurement type. Furthermore, a unified naming format is required to avoid subscription failures due to naming discrepancies.

[0064] In this application, the subject name of the data can be designed according to the equipment category, regional location, data usage, etc. in the ship. The subject name designed by the present invention is shown in Table 1. The data transceiver unit and the data integration platform publish and subscribe to data according to the subject name in the design rules.

[0065]

[0066]

[0067] Table 1

[0068] As an optional embodiment, the method also includes: in response to receiving a data publishing request, determining the sensor type, sensor location and sensor purpose represented by the data publishing request; determining the target topic from the topics of all sensors based on the sensor type, sensor location and sensor purpose represented by the data publishing request; and storing the target data published by the data transceiver unit under the target topic.

[0069] Furthermore, by parsing the sensor type, location, and usage metadata in the data publishing request, the pre-generated topic mapping table can be automatically matched, the target topic path (such as / vessel / SH001 / engine / room / temperature) can be located, and the DDS middleware can be called to store the data in the corresponding topic, thereby realizing the dynamic association between publishing requirements and topics. There is no need to manually configure the topic path, which improves the system's adaptability to dynamic publishing requirements.

[0070] As an optional embodiment, after responding to receiving a data publishing request, the method also includes: parsing the data publishing request to obtain the sensor type, sensor location and sensor purpose indicated by the data publishing request; and determining the target topic from the topics of all sensors based on the sensor type, sensor location and sensor purpose indicated by the data publishing request.

[0071] Furthermore, after receiving a data publishing request, the sensor type, location, and usage metadata in the request are automatically parsed, and based on predefined topic mapping rules, the corresponding target topic path (such as / vessel / SH001 / engine / room / temperature) is dynamically matched from the registered sensor topic set to achieve intelligent association between publishing requirements and topics, without the need for manual intervention in the topic selection process.

[0072] As an optional embodiment, the data transceiver unit includes at least one data publishing module, each data publishing module manages at least one data writing sub-module; the data publishing module binds the target topic and provides target data corresponding to the target topic; the data writing sub-module writes the target data to the target topic.

[0073] The data transceiver unit consists of one or more data publishing modules. Each publishing module is explicitly bound to one or more specific DDS topics (such as / vessel / SH001 / engine / room / temperature) through configuration, and generates target data (such as temperature value, timestamp, etc.) that matches the topic semantics based on business logic. Each publishing module further manages at least one data writing sub-module. The writing sub-module encapsulates the interaction interface with the underlying communication middleware (such as RTIDDS and EclipseCyclone DDS), is responsible for serializing and encapsulating the target data according to the predefined topic path, and accurately delivering the data to the corresponding topic through the middleware's write() or publish() method. It also supports error handling and retry mechanisms in the data writing process to ensure reliable data transmission.

[0074] As an optional embodiment, the data integration unit includes at least one data subscription module, each data subscription module includes at least one data reading submodule; the data subscription module binds the target topic; the data reading submodule reads the target data stored under the target topic.

[0075] In this embodiment, the data integration unit can adopt a modular layered architecture, including one or more data subscription modules, each subscription module explicitly binds one or more target topics (such as / vessel / SH001 / engine / room / temperature) through a configuration file or API interface, and registers a callback function to monitor changes in topic data; each subscription module internally manages at least one data reading sub-module, which encapsulates the interaction logic with the underlying communication middleware (such as RTIDDS or EclipseCyclone DDS), and asynchronously pulls the latest data stored under the target topic (such as temperature values and timestamps in JSON format) through the read() or take() method of the middleware, and supports data parsing, deduplication and caching mechanisms, while providing data integrity verification (such as CRC verification) and error recovery capabilities to ensure the reliability and consistency of subscribed data.

[0076] As an optional embodiment, the sensor of the target ship includes at least one of a navigation sensor, a radar sensor, a communication sensor, and an electromechanical equipment sensor; the method also includes: the data transceiver unit obtains target data from the sensor of the target ship through a preset communication protocol; wherein the preset communication protocol includes at least one of a TCP communication protocol, a UDP communication protocol, a CAN communication protocol, an OPC UA communication protocol, an OPC DA communication protocol, an HTTP communication protocol, a WebSocket communication protocol, a serial port communication protocol, a Modbus TCP communication protocol, and a Modbus RTU communication protocol.

[0077] In this embodiment, the sensor network of the target ship covers multiple types such as navigation sensors (such as GPS / IMU), radar sensors (such as millimeter wave radar), communication sensors (such as AIS transceivers) and electromechanical equipment sensors (such as engine vibration / temperature sensors).

[0078] Through a configurable protocol adapter module, the data transceiver unit supports hybrid access modes based on TCP / IP (including TCP and UDP), industrial buses (CAN and Modbus TCP / RTU), industrial IoT protocols (OPC UA / DA) and general communication protocols (HTTP, WebSocket and serial ports). It dynamically adapts to the communication interfaces and data formats (such as CAN frames, Modbus registers and OPC UA node values) of different sensors, and realizes the standardized collection and unified transmission of multi-source heterogeneous data. It also supports protocol layer disconnection and reconnection, data verification (such as CRC verification) and transmission encryption (such as TLS / SSL), ensuring the reliability and security of ship sensor data in complex marine environments.

[0079] In summary, the data transceiver unit publishes the ship's navigation system data, radar system data, communication system data, and various electromechanical system data to the DDS network, and the data integration platform and the data transceiver unit subscribe to the required data on demand.

[0080] This application proposes a DDS-based communication method, which is applied to a DDS-based communication system. In response to receiving a data subscription request from a data integration platform, a mapping relationship is established between a data transceiver unit and the data integration platform through a target topic. Furthermore, target data stored under the target topic is read into the data integration platform; the target data is published by the data transceiver unit under the target topic. Through the multi-topic publish and subscribe mechanism of DDS communication technology, data sharing between data transceivers and the data integration platform is achieved, reducing development costs and system complexity and improving data communication efficiency.

[0081] It should be noted that the method of the embodiment of the present invention can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied in a distributed scenario, where multiple devices cooperate to perform the method. In such a distributed scenario, one of the multiple devices may only perform one or more steps of the method of the embodiment of the present invention, and the multiple devices will interact with each other to complete the above method.

[0082] It should be noted that the above description is limited to some embodiments of the present invention. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in an order different from that described in the above embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0083] Corresponding to the above embodiment, the present invention also proposes a communication system based on DDS.

[0084] like Figure 4 As shown, the DDS-based communication system 400 according to the embodiment of the present invention includes a communication establishing module 401 and a reading module 402 .

[0085] The communication establishment module 401 is configured to establish a mapping relationship between the data transceiver unit and the data integration platform through a target topic in response to receiving a data subscription request from the data integration platform;

[0086] The reading module 402 is configured to read the target data stored in the target subject into the data integration platform; wherein the target data is stored in the target subject by the data transceiver unit.

[0087] Optionally, the communication establishing module 401 is further configured to:

[0088] Obtain sensor types, sensor locations, and sensor usages of all sensors of the target ship;

[0089] Identify the topic for each sensor based on the sensor type, sensor location, and sensor purpose.

[0090] Optionally, the communication establishing module 401 is further configured to:

[0091] In response to receiving a data release request, determining a sensor type, a sensor location, and a sensor usage represented by the data release request;

[0092] determining a target topic from the topics of all sensors according to the sensor type, sensor location, and sensor purpose characterized by the data release request;

[0093] The target data published by the data transceiver unit is stored in the target topic.

[0094] Optionally, the communication establishing module 401 is further configured to:

[0095] Parsing the data publishing request to obtain the sensor type, sensor location, and sensor purpose indicated by the data publishing request;

[0096] A target topic is determined from topics of all sensors according to the sensor type, sensor location, and sensor purpose indicated by the data publishing request.

[0097] Optionally, the data transceiver unit includes at least one data publishing module, each data publishing module managing at least one data writing submodule;

[0098] The data publishing module binds the target topic and provides the target data corresponding to the target topic;

[0099] The data writing submodule writes the target data to the target topic.

[0100] Optionally, the data integration unit includes at least one data subscription module, and each data subscription module includes at least one data reading submodule;

[0101] The data subscription module is bound to the target topic;

[0102] The data reading submodule reads the target data stored under the target topic.

[0103] Optionally, the sensor of the target ship includes at least one of a navigation sensor, a radar sensor, a communication sensor, and an electromechanical equipment sensor;

[0104] Optionally, the reading module 402 is further configured to:

[0105] The data transceiver unit obtains target data from the sensor of the target ship through a preset communication protocol; wherein the preset communication protocol includes at least one of the TCP communication protocol, the UDP communication protocol, the CAN communication protocol, the OPC UA communication protocol, the OPC DA communication protocol, the HTTP communication protocol, the WebSocket communication protocol, the serial port communication protocol, the Modbus TCP communication protocol and the Modbus RTU communication protocol.

[0106] This application proposes a DDS-based communication system, comprising a communication establishment module and a reading module. The communication establishment module is configured to establish a mapping relationship between a data transceiver unit and the data integration platform via a target topic in response to receiving a data subscription request from the data integration platform; the reading module is configured to read target data stored under the target topic into the data integration platform; wherein the target data is the data transceiver unit stored under the target topic. Through the multi-topic publishing and subscription mechanism of DDS communication technology, data sharing between data transceivers and the data integration platform is achieved, reducing development costs and system complexity and improving data communication efficiency.

[0107] For the convenience of description, the above system is described as being divided into various modules according to their functions. Of course, when implementing the present invention, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0108] The system of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0109] Corresponding to the above embodiment, the present invention further provides an electronic device.

[0110] refer to Figure 5 , is a block diagram of an electronic device according to some embodiments of the present invention, illustrating a more specific hardware structure of an electronic device provided by this embodiment. The device may include: a processor 510, a memory 520, an input / output interface 530, a communication interface 540, and a bus 550. The processor 510, the memory 520, the input / output interface 530, and the communication interface 540 are connected to each other within the device via the bus 550.

[0111] The processor 510 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0112] The memory 520 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage devices, dynamic storage devices, etc. The memory 520 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510.

[0113] The input / output interface 530 is used to connect an input / output module to implement information input and output. The input / output module can be configured as a component in the device (not shown in the figure) or can be externally connected to the device to provide corresponding functions. Input devices may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and output devices may include a display, speaker, vibrator, indicator light, etc.

[0114] The communication interface 540 is used to connect to a communication module (not shown) to enable communication between the device and other devices. The communication module can communicate via a wired method (such as USB, network cable, etc.) or a wireless method (such as mobile network, WiFi, Bluetooth, etc.).

[0115] The bus 550 comprises a pathway for transmitting information between the various components of the device (eg, the processor 510 , the memory 520 , the input / output interface 530 , and the communication interface 540 ).

[0116] It should be noted that although the above device only shows the processor 510, the memory 520, the input / output interface 530, the communication interface 540, and the bus 550, in a specific implementation, the device may also include other components necessary for normal operation. In addition, it will be understood by those skilled in the art that the above device may only include the components necessary to implement the embodiments of this specification, and does not necessarily include all the components shown in the figure.

[0117] The electronic device of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0118] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present invention further provides a computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute the method of any of the above embodiments.

[0119] The above-mentioned computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.

[0120] The computer instructions stored in the storage medium of the above embodiment are used to enable a computer to execute the method of any embodiment in the above exemplary method section, and have the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0121] Furthermore, although the operations of the present method are described in a particular order in the accompanying drawings, this does not require or imply that the operations must be performed in that particular order, or that all of the operations shown must be performed to achieve the desired results. Rather, the steps depicted in the flowcharts may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into a single step, and / or a single step may be broken down into multiple steps.

[0122] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0123] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present invention should have the usual meanings understood by people with ordinary skills in the field to which the present invention belongs. The "first", "second" and similar words used in the embodiments of the present invention do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0124] Although the spirit and principles of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the specific embodiments disclosed, and the division into various aspects does not mean that the features of these aspects cannot be combined to benefit. Such division is merely for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. The scope of the appended claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.

Claims

1. A communication method based on DDS, characterized in that: Applied to a DDS-based communication system, the method includes: In response to receiving a data subscription demand from the data integration platform, establishing a mapping relationship between the data transceiver unit and the data integration platform through the target topic; The target data stored under the target topic is read into the data integration platform; wherein the target data is published by the data transceiver unit under the target topic.

2. The DDS-based communication method according to claim 1, wherein: The method further comprises: Obtain sensor types, sensor locations, and sensor usages of all sensors of the target ship; A subject of each of the sensors is determined according to the sensor type, the sensor location, and the sensor usage.

3. The DDS-based communication method according to claim 2, wherein: The method further comprises: In response to receiving a data publishing request, determining a sensor type, a sensor location, and a sensor usage represented by the data publishing request; determining a target topic from among all sensor topics according to the sensor type, sensor location, and sensor usage represented by the data publishing request; The target data published by the data transceiver unit is stored under the target topic.

4. The DDS-based communication method according to claim 3, wherein: After receiving the data publishing request in response, the method further includes: Parsing the data publishing request to obtain the sensor type, sensor location, and sensor purpose indicated by the data publishing request; The target topic is determined from topics of all sensors according to the sensor type, sensor location, and sensor usage indicated by the data publishing request.

5. The DDS-based communication method according to claim 4, wherein: The data transceiver unit includes at least one data publishing module, each of which manages at least one data writing submodule; The data publishing module is bound to the target subject and provides the target data corresponding to the target subject; The data writing submodule writes the target data into the target topic.

6. The DDS-based communication method according to claim 4, wherein: The data integration unit includes at least one data subscription module, and each of the data subscription modules includes at least one data reading submodule; The data subscription module is bound to the target topic; The data reading submodule reads the target data stored under the target subject.

7. The DDS-based communication method according to claim 5 or 6, characterized in that: The sensor of the target ship includes at least one of a navigation sensor, a radar sensor, a communication sensor, and an electromechanical equipment sensor; The method further comprises: The data transceiver unit obtains the target data from the sensor of the target ship through a preset communication protocol; wherein the preset communication protocol includes at least one of the TCP communication protocol, the UDP communication protocol, the CAN communication protocol, the OPC UA communication protocol, the OPC DA communication protocol, the HTTP communication protocol, the WebSocket communication protocol, the serial port communication protocol, the Modbus TCP communication protocol and the Modbus RTU communication protocol.

8. A communication system based on DDS, characterized in that: include: a communication establishment module configured to establish a mapping relationship between the data transceiver unit and the data integration platform through a target topic in response to receiving a data subscription demand from the data integration platform; The reading module is configured to read the target data stored under the target subject into the data integration platform; wherein, the target data is stored under the target subject by the data transceiver unit.

9. An electronic device, characterized in that: include: A processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the DDS-based communication method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the DDS-based communication method according to any one of claims 1 to 7 are implemented.

Images