Message service bus architecture based on DDS

Abstract

The invention discloses a message service bus architecture based on a DDS (Direct Digital Synthesizer). The message service bus architecture comprises a DDS message engine module, a DDS message arrangement module and a message node, the message nodes comprise interception type nodes, conversion type nodes and connection type nodes; the DDS message engine module is responsible for transmitting and distributing messages by using DDS data distribution, and ensures the high efficiency and reliability of message transmission through a QoS (Quality of Service) mechanism; the DDS message arrangement module arranges and manages various types of message nodes to form a complete message stream processing logic. The embodiment of the invention shows remarkable advantages in the aspects of real-time performance, reliability, flexibility, usability, message processing capability and the like.

Description

Technical Field

[0001] The present invention relates to the field of message service bus architecture, in particular to a message service bus architecture based on DDS. Background Art

[0002] In today's complex and ever-changing enterprise information environment, the message service bus (ESB) is a key central system responsible for connecting and coordinating various services and applications within and across enterprises to achieve seamless data exchange and automation of business processes. However, with the rapid development of information technology and the increasing complexity of business needs, traditional ESB has gradually revealed its limitations when dealing with large-scale, high-concurrency, and low-latency data transmission. Especially in application scenarios with extremely high real-time requirements, such as industrial automation, remote monitoring, and real-time data analysis, traditional ESB often finds it difficult to ensure the real-time nature of data and the scalability of the system.

[0003] At the same time, as a communication middleware designed for real-time systems, Data Distribution Service (DDS) has occupied an important position in the field of real-time data communication with its efficient publish / subscribe mechanism, flexible data distribution strategy and excellent real-time performance. DDS not only supports real-time data exchange between a large number of nodes, but also provides a rich quality of service (QoS) settings to meet the specific needs of different application scenarios. However, although DDS performs well in real-time data communication, it is relatively weak in service integration, business process orchestration and complex message processing, making it difficult to adapt to the rapidly changing information system integration requirements of enterprises. Summary of the invention

[0004] The present invention provides a DDS-based message service bus architecture to solve the problems of poor data real-time performance and poor scalability in the conventional ESB of the prior art.

[0005] In order to achieve the above object, the technical solution adopted by the present invention is: A message service bus architecture based on DDS, including a DDS message engine module, a DDS message arrangement module, and a message node; The message nodes include listening type nodes, conversion type nodes, and connection type nodes; wherein the listening type nodes listen to and receive messages from different message sources, then convert the messages from different message sources into a unified message message structure, and transmit the converted messages to the corresponding conversion type nodes or connection type nodes according to business requirements; the conversion type nodes receive messages from the listening type nodes or connection type nodes, parse and process the received messages, and then perform corresponding operations according to business requirements; the connection type nodes send the messages processed by the listening type nodes or conversion type nodes to other business systems, or databases, or third-party services, and receive response messages from other business systems, or databases, or third-party services, and transmit the response messages to the corresponding conversion type nodes for processing according to business requirements; The DDS message engine module is responsible for the message transmission and distribution between message nodes through DDS data distribution technology, and guarantees the service quality of the message transmission process through the QoS mechanism; The DDS message orchestration module orchestrates and manages various types of message nodes. Users combine and orchestrate message nodes through the DDS message orchestration module according to business needs to form a complete message flow processing logic.

[0006] Furthermore, the unified message structure formed in the listening type node includes a message header, a message body and a message tail, wherein the message header carries an unalterable metadata set and user-defined data, the message body carries specific business data required at the application level, and the message tail records and processes variable information and exception information during the message flow.

[0007] Furthermore, the internal structure of each message node includes a subscriber, a logic unit, and a publisher, where: The subscriber is used to receive messages from the DDS network according to the subscribed DDS topic list; The logic unit performs business logic processing on the message according to the preset business rules of the message node; The publisher publishes the processed message to the DDS network according to the specified topic, where the topic includes the publisher's default DDS topic and user-defined related DDS topics.

[0008] Furthermore, in the message flow processing logic, the message transmission between each message node is carried out through the DDS publish / subscribe mode, and all the message nodes participating in the collaboration are in the same domain, and have the following subscription rules: the latter message node subscribes to the DDS topic of the previous message node, and the first message node subscribes to the DDS topic of the last message node.

[0009] Furthermore, the message orchestration module also constructs, adjusts and optimizes the message flow processing logic through a graphical interface. The user selects the required message nodes and constructs the path and logic of the message flow by connecting lines. Each message node represents a message processing unit, and the lines between message nodes indicate the direction and rules of message transmission. At the same time, the user sets the parameters of the message nodes according to actual needs.

[0010] Furthermore, the protocol adaptation process is as follows: (1) Inbound Adaptation Message reception: listens and receives messages from different systems or protocols through listening type nodes; Protocol parsing: The listening node performs protocol parsing on the received message and extracts the data required for the business according to the protocol specification to which the message belongs; Data conversion: The listening type node converts the parsed data into a unified message structure within the DDS message service bus, including a message header, a message body, and a message footer; Message encapsulation: The listening type node encapsulates the converted data into a DDS message; Message processing: Complete message processing according to the arranged message flow processing logic; (2) Outbound Adaptation Message preparation: In the DDS message service bus, the connection type node prepares the DDS message to be sent; Message parsing: The connection type node extracts the key data required for the business from the DDS message; Data conversion: According to the protocol specifications of the target system, the connection type node formats the extracted key data; Protocol encapsulation: The connection type node encapsulates the converted data into messages of the corresponding protocol according to the protocol specifications of the target system; Message sending: The connection type node sends the encapsulated message to the target system through the corresponding protocol.

[0011] The present invention proposes a message service bus architecture based on DDS, which combines the real-time data distribution advantage of DDS with the service integration and message processing capabilities of ESB to build a new message service bus that has high real-time performance and high reliability, and can flexibly integrate multiple services and support complex business process processing. The present invention optimizes the message transmission path and improves the real-time performance and efficiency of data transmission by introducing the publish / subscribe mechanism of DDS; at the same time, it uses the service integration capabilities of ESB to seamlessly connect various heterogeneous systems, services and applications, realize unified data management, and provide a more efficient, flexible and reliable solution for enterprise information construction.

[0012] Compared with the existing ESB, the advantages of the present invention are: 1. High real-time performance and high efficiency: By introducing the publish / subscribe mechanism of DDS, the message transmission path is optimized, the delay of message transmission is reduced, and the real-time performance of data transmission is improved.

[0013] DDS's efficient data distribution strategy further improves the speed and efficiency of message processing, ensuring the stable operation of the system in a high-concurrency environment.

[0014] 2. High reliability and stability: The rich QoS settings provided by DDS enable the present invention to adjust the service quality according to different application scenarios and ensure the reliability and stability of message transmission.

[0015] The message orchestration function configures the message flow processing logic through a graphical interface, reducing the possibility of configuration errors and enhancing the stability and maintainability of the system.

[0016] 3.Flexibility and scalability: The present invention combines the real-time data distribution advantage of DDS with the service integration capability of ESB, can flexibly integrate multiple heterogeneous systems, services and applications, realize unified data management, and provide a more flexible solution for enterprise informatization construction.

[0017] As business needs grow, you can expand the system's functionality by adding message nodes or adjusting the message flow processing logic to meet changing business needs.

[0018] 4. Ease of use and visualization: The message orchestration function provides a graphical interface, and users can build, adjust and optimize the message flow processing logic through simple drag and drop and connection operations, which lowers the technical threshold and improves the user experience.

[0019] The visual orchestration logic makes system maintenance and management more intuitive and convenient, helping to quickly locate problems and perform troubleshooting.

[0020] 5. Powerful message processing capabilities: The design of the message structure enables messages to carry rich metadata and business data during the flow process, supporting complex message processing logic.

[0021] Different types of message nodes collaborate with each other and can handle multiple types of messages and business needs to meet the processing requirements of complex business processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a diagram of the architecture of an embodiment of the present invention.

[0023] Figure 2 It is a message message structure diagram in an embodiment of the present invention.

[0024] Figure 3 It is a diagram of the message node architecture in an embodiment of the present invention.

[0025] Figure 4 It is the message flow processing logic routing structure in the embodiment of the present invention.

[0026] Figure 5 It is a diagram of the DDS message service bus protocol adaptation process in an embodiment of the present invention. DETAILED DESCRIPTION

[0027] The present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0028] like Figure 1 As shown, this embodiment discloses a message service bus architecture based on DDS, including a DDS message engine module, a DDS message arrangement module, and a message node, wherein: Message nodes include listening nodes, conversion nodes, and connection nodes. Listening nodes listen to and receive messages from different message sources, and then convert messages from different message sources into a unified message structure; conversion nodes parse and process received messages, and perform corresponding operations according to business needs; connection nodes are used to interact with other business systems, databases, or third-party services.

[0029] The DDS message engine module uses DDS data distribution to be responsible for the transmission and distribution of messages, and ensures the efficiency and reliability of message delivery through the QoS mechanism.

[0030] The DDS message orchestration module orchestrates and manages various types of message nodes, combines and orchestrates message nodes to form a complete message flow processing logic.

[0031] In this embodiment, Figure 2 As shown, the unified message structure formed in the listening type node includes a message header, a message body and a message tail, wherein: The message header is divided into two logical areas: the Inbound area and the Outbound area. The Inbound area carries a set of metadata that cannot be tampered with. The metadata is automatically filled when the message is generated or received, including but not limited to the requested access path, the client IP address that initiated the request, and the specific attributes of the current processing node. The Outbound area is a user-defined data area that allows users to dynamically add or modify information during the message flow. Whenever the message is passed to the next processing node, the Outbound data of the current node will be automatically converted to the Inbound data of the node.

[0032] The message body is the core part of the message structure and carries the specific business data required at the application level.

[0033] The message tail is the end part of the message and is used to record and process variable information and exception information during the message flow.

[0034] In this embodiment, Figure 3 As shown, the message node includes a subscriber, a logic unit, and a publisher, where: The subscriber is used to receive messages from the DDS network according to the subscribed DDS topic list.

[0035] The logic unit performs business logic processing on the message according to the preset business rules of the message node.

[0036] The publisher publishes the processed messages to the DDS network according to the specified topic, which includes the default DDS topic of the publisher and the related DDS topics defined by the user.

[0037] The routing structure of the message flow processing logic of this embodiment is as follows Figure 4 As shown, Figure 4 Sub means the DDS topic subscribed by the subscriber in the message node, and Pub means the DDS topic published by the publisher in the message node. The message transmission between the message nodes is carried out through the DDS publish / subscribe mode, and all the message nodes participating in the collaboration are in the same domain, and have the following subscription rules: the next message node subscribes to the DDS topic of the previous message node, and the first message node subscribes to the DDS topic of the last message node.

[0038] In this embodiment, the message orchestration module also constructs, adjusts and optimizes the message flow processing logic through a graphical interface. The user selects the required message nodes and constructs the path and logic of the message flow by connecting lines. Each message node represents a message processing unit, and the lines between message nodes indicate the direction and rules of message transmission. At the same time, the user sets the parameters of the message node according to actual needs, including publish / subscribe topics, DDS domains, QOS policies, number of processing threads, node names, etc., to meet the needs of different business scenarios.

[0039] In the message transmission process of this embodiment, two protocol adaptation stages are used to achieve docking with applications with different communication protocols. Figure 5 As shown in the figure, the protocol adaptation process is as follows: (1) Inbound Adaptation Message reception: Listen to and receive messages from different systems or protocols.

[0040] Protocol parsing: Perform protocol parsing on the received message and extract the data required for the business according to the protocol specification to which the message belongs.

[0041] Data conversion: convert the parsed data into a unified message structure within the DDS message service bus, including a message header, message body, and message footer.

[0042] Message encapsulation: Encapsulate the converted data into DDS messages.

[0043] Message processing: Complete message processing according to the arranged message flow processing logic.

[0044] (2) Outbound Adaptation Message preparation: In the DDS message service bus, prepare the DDS message to be sent.

[0045] Message parsing: Extract key data required for business from DDS messages.

[0046] Data conversion: Format the extracted key data according to the protocol specifications of the target system.

[0047] Protocol encapsulation: According to the protocol specification of the target system, the converted data is encapsulated into messages of the corresponding protocol.

[0048] Message sending: Send the encapsulated message to the target system through the corresponding protocol.

[0049] This embodiment has demonstrated significant advantages in terms of real-time performance, reliability, flexibility, ease of use, and message processing capabilities, and provides a more efficient, flexible, and reliable solution for enterprise informatization construction.

[0050] The preferred embodiments of the present invention are described in detail above in conjunction with the accompanying drawings. The embodiments described in the present invention are merely descriptions of the preferred embodiments of the present invention, and do not limit the concept and scope of the present invention. The various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction, and such combinations should also be regarded as the contents disclosed in the present disclosure as long as they do not violate the concept of the present invention. In order to avoid unnecessary repetition, the present invention will not further describe various possible combinations.

[0051] The present invention is not limited to the specific details of the above-mentioned embodiments. Within the technical concept of the present invention and without departing from the design concept of the present invention, various modifications and improvements made to the technical solution of the present invention by technical personnel in this field should fall within the protection scope of the present invention. The technical contents for which protection is sought in the present invention have been fully recorded in the claims.

Claims

1. A message service bus architecture based on DDS, characterized in that: Includes DDS message engine module, DDS message orchestration module, and message node; The message nodes include listening type nodes, conversion type nodes, and connection type nodes; The listening type node listens to and receives messages from different message sources, then converts the messages from different message sources into a unified message message structure, and transmits the converted messages to the corresponding conversion type node or connection type node according to business needs; the conversion type node receives messages from the listening type node or the connection type node, parses and processes the received messages, and then performs corresponding operations according to business needs; the connection type node sends the messages processed by the listening type node or the conversion type node to other business systems, or databases, or third-party services, and receives response messages from other business systems, or databases, or third-party services, and transmits the response messages to the corresponding conversion type node for processing according to business needs; The DDS message engine module is responsible for the message transmission and distribution between message nodes through DDS data distribution technology, and guarantees the service quality of the message transmission process through the QoS mechanism; The DDS message orchestration module orchestrates and manages various types of message nodes. Users combine and orchestrate message nodes through the DDS message orchestration module according to business needs to form a complete message flow processing logic.

2. A DDS-based message service bus architecture according to claim 1, characterized in that: The unified message structure formed in the listening type node includes a message header, a message body and a message tail. The message header carries an unalterable metadata set and user-defined data, the message body carries the specific business data required at the application level, and the message tail records and processes variable information and exception information during the message flow.

3. A DDS-based message service bus architecture according to claim 1, characterized in that: The internal structure of each message node includes a subscriber, a logical unit, and a publisher, where: The subscriber is used to receive messages from the DDS network according to the subscribed DDS topic list; The logic unit performs business logic processing on the message according to the preset business rules of the message node; The publisher publishes the processed message to the DDS network according to the specified topic, where the topic includes the default DDS topic of the publisher and the related DDS topic defined by the user.

4. A DDS-based message service bus architecture according to claim 1, characterized in that: In the message flow processing logic, message transmission between message nodes is carried out through the DDS publish / subscribe mode, and all message nodes participating in the collaboration are in the same domain, with the following subscription rules: the latter message node subscribes to the DDS topic of the previous message node, and the first message node subscribes to the DDS topic of the last message node.

5. A DDS-based message service bus architecture according to claim 1, characterized in that: The message arrangement module also constructs, adjusts and optimizes the message flow processing logic through a graphical interface. The user selects the required message nodes and constructs the path and logic of the message flow by connecting lines. Each message node represents a message processing unit, and the lines between message nodes indicate the direction and rules of message transmission. At the same time, the user sets the parameters of the message nodes according to actual needs.

6. A DDS-based message service bus architecture according to claim 1, characterized in that: The protocol adaptation process is as follows: (1) Inbound Adaptation Message reception: listens and receives messages from different systems or protocols through listening type nodes; Protocol parsing: The listening node performs protocol parsing on the received message and extracts the data required for the business according to the protocol specification to which the message belongs; Data conversion: The listening type node converts the parsed data into a unified message structure within the DDS message service bus, including a message header, a message body, and a message footer; Message encapsulation: The listening type node encapsulates the converted data into a DDS message; Message processing: Complete message processing according to the arranged message flow processing logic; (2) Outbound Adaptation Message preparation: In the DDS message service bus, the connection type node prepares the DDS message to be sent; Message parsing: The connection type node extracts the key data required for the business from the DDS message; Data conversion: According to the protocol specifications of the target system, the connection type node formats the extracted key data; Protocol encapsulation: The connection type node encapsulates the converted data into messages of the corresponding protocol according to the protocol specifications of the target system; Message sending: The connection type node sends the encapsulated message to the target system through the corresponding protocol.

Images