A service bus data integration method and system based on publish-subscribe technology

Abstract

This invention provides a service bus data integration method and system based on publish / subscribe technology, relating to the fields of industrial internet and enterprise service bus technology. By completely decoupling data producers and consumers through a publish / subscribe model, neither needs to be aware of the other's existence. The introduction of structured topic metadata and a topic registry center allows newly launched devices or systems to declare their data capabilities on the bus, while consumers dynamically discover the required data through semantic queries. Asynchronous processing liberates the production end, load balancing strategies optimize computing resource allocation, QoS grading ensures the real-time performance of critical data, and message persistence mechanisms ensure eventual consistency in data interaction. This invention achieves end-to-end security protection through a security management module, encompassing access authentication, access control, transmission encryption, and operation auditing. Fine-grained RBAC policies ensure compliance of data access, meeting the stringent requirements of industrial environments for data security and privacy protection.

Description

Technical Field

[0001] This invention relates to the field of industrial internet and enterprise service bus technology, and in particular to a service bus data integration method and system based on publish-subscribe technology. Background Technology

[0002] With the rapid development of intelligent manufacturing, modern factories have integrated numerous heterogeneous subsystems, including Manufacturing Execution Systems (MES), Enterprise Resource Planning (ERP) systems, Supervisory Control and Data Acquisition (SCADA) systems, Programmable Logic Controllers (PLCs), and various intelligent sensors. These systems form typical information silos, severely hindering the global flow of data and the extraction of its value. To address this issue, the Industrial Service Bus (ISB) has emerged as a core integration platform.

[0003] However, existing ISB platforms mostly adopt traditional point-to-point connections or request / response models for data integration. These models have inherent limitations: First, tight coupling leads to a rigid system architecture, requiring extensive manual configuration for any changes to either side, resulting in high maintenance costs; second, poor scalability, requiring modifications to existing system code or configuration when adding new data sources or consumers, making it difficult to cope with rapidly changing industrial production environments; third, a lack of dynamic discovery capabilities, failing to automatically detect newly added devices or services, necessitating tedious reconfiguration through manual intervention, severely impacting production agility; finally, synchronous blocking communication methods easily create performance bottlenecks in high-concurrency scenarios, affecting system real-time performance and reliability.

[0004] While the publish / subscribe (Pub / Sub) model has been incorporated into some integration solutions due to its loose coupling, most existing practices simply apply general-purpose message middleware without deeply optimizing for the characteristics of industrial data (such as high real-time performance, strong semantics, and security sensitivity). They generally neglect key aspects required for deep integration with the service bus, such as metadata-driven processes, dynamic registration and discovery, quality of service assurance, and end-to-end security governance.

[0005] Therefore, there is an urgent need for a service bus data integration method specifically designed for industrial scenarios and deeply integrating the advantages of the publish / subscribe model, in order to build a flexible, scalable, self-describing, and self-discovering intelligent data ecosystem. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to address the shortcomings of the prior art by providing a service bus data integration method and system based on publish-subscribe technology, which can transform the original static and hard-coded data interaction relationship into a loosely coupled mode that is driven by the data itself and can be dynamically configured, and provides a visual and manageable integration interface.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows: On one hand, the present invention provides a service bus data integration method based on publish-subscribe technology, comprising: Before an industrial subsystem needs to access the service bus for data interaction, a complete data topic model must first be established, and dynamic integration must be performed based on this model. After the data topic model is built, dynamic registration and publishing of data producers are realized, and then dynamic discovery and subscription of data consumers are realized. Based on the subscription request, topic-based message brokering and transmission are executed. During the process, full-link security and governance need to be implemented. Constructing the data topic model includes: Define topic specifications: Define a standardized set of data topic naming and description specifications; each data topic is abstracted into a logical channel with a unique identifier and associated with a set of structured metadata; the metadata includes at least: topic name, data format, data source system identifier, data update frequency, data timeliness level, and optional business semantic tags; Build a topic registry: Establish an efficient and scalable topic registry to centrally store and manage metadata information for all data topics, serving as the core database for dynamic discovery functionality.

[0008] The implementation of dynamic registration and publishing for data producers includes: Topic Declaration: Data producers send a topic declaration request to the topic registry, declaring whether they intend to publish a new data topic or an existing data topic, and attaching complete topic metadata; Metadata Validation and Registration: After receiving a request, the topic registry center verifies the legality and uniqueness of the metadata and verifies the producer's operation permissions. After the verification is successful, the corresponding topic entry is created or updated in the topic registry center, and confirmation information and topic ID are returned. Data publishing: Producers publish actual business data load to the logical channel corresponding to the specified topic ID through the message broker cluster. The publishing process is independent of the specific consumer list. The implementation of dynamic discovery and subscription for data consumers includes: Topic discovery: Data consumers initiate query requests to the topic registry center; query methods support fuzzy matching by topic name, filtering by business semantic tags, and system filtering by data source; Smart subscription: Consumers assess their own processing capabilities based on the metadata information returned by the topic registry, select one or more target topics, and send subscription requests to the message broker cluster; Establish dynamic routing: After receiving a subscription request, the message broker cluster internally establishes message routing rules from the corresponding topic to the data consumer. According to the QoS policy, the message broker accurately pushes the real-time data published by the producer to the consumer through the established routing logic. The execution of topic-based message brokerage and transmission includes: Asynchronous non-blocking processing: The message broker cluster returns immediately after receiving data published by the producer, unblocking the producer and improving its response speed; Load balancing: In scenarios where there are multiple homogeneous consumers for the same topic, the message broker uses consistent hashing to distribute messages evenly and avoid single point of overload. Service Quality Assurance: Based on the timeliness level and security requirements defined in the topic metadata, the message broker configures differentiated transmission strategies for different topics; for industrial control data with extremely high real-time requirements, memory queues are used for priority processing, and disk persistence is performed simultaneously to prevent sudden failures; for routine monitoring data, standard queues are used to process the data and balance system resource usage. Message persistence and retry: Persistently store messages that fail to push on critical topics, allowing offline consumers to resume consumption from the breakpoint after recovery, ensuring no data loss; The implementation of end-to-end security and governance includes: Identity authentication and authorization: All producers and consumers must be authenticated by the security management module before accessing the bus; role-based access control policies determine the operation permissions of each subject for specific data topics; Data encryption: During transmission, all data payloads are encrypted using TLS / SSL to ensure the security of data flow; Auditing and Monitoring: The platform records all registration, publishing, and subscription activity logs for all topics and provides a real-time monitoring panel for administrators to perform operations and auditing.

[0009] On the other hand, the present invention also provides a service bus data integration system based on publish-subscribe technology, for implementing the above-mentioned service bus data integration method based on publish-subscribe technology. The system includes a heterogeneous industrial subsystem access layer, a core industrial service bus platform, a highly available topic registry center, a high-performance message broker cluster, a full-link security and governance module, and an intelligent data consumer layer. The heterogeneous industrial subsystem access layer, as the underlying data producer, interfaces with the service bus through standardized interfaces. The core industrial service bus platform is responsible for coordinating the interaction between producers and consumers, transforming the original hard-coded, tightly coupled connection method into a loosely coupled mode driven by the data itself. The high-availability topic registry is the system's "metadata repository," responsible for centrally storing and managing the logical channels, unique identifiers, and associated structured metadata of all data topics. It is the core database that enables the system's dynamic discovery and self-description capabilities. A high-performance message broker cluster executes topic-based message routing and distribution logic, supports asynchronous and non-blocking communication, is responsible for receiving the producer's load, and implements precise push to consumers according to subscription rules; The end-to-end security and governance module integrates identity authentication, role-based access control, TLS / SSL data transmission encryption, and operation auditing functions to ensure that all registration, publishing, and subscription activities of all topics are carried out in a controlled environment, meeting industrial-grade data security requirements. The intelligent data consumer layer includes data analysis engines, visualization applications, predictive maintenance systems, and decision support systems. Consumers do not need to pre-configure the physical address of the producer; they can dynamically discover and obtain high-quality, real-time global data on demand through the topic registry center.

[0010] Thirdly, this application proposes an electronic device, comprising: one or more processors, and a memory for storing instructions that, when executed by the one or more processors, cause the one or more processors to perform the service bus data integration method based on publish-subscribe technology.

[0011] Fourthly, this application proposes a computer-readable storage medium storing executable instructions that, when executed, cause a processor to perform the service bus data integration method based on publish-subscribe technology.

[0012] Fifthly, this application proposes a computer program product, including a computer program or instructions that, when executed by a processor, implement the aforementioned service bus data integration method based on publish-subscribe technology.

[0013] The beneficial effects of adopting the above technical solution are as follows: The service bus data integration method and system based on publish / subscribe technology provided by this invention have the following advantages: First, they possess extreme loose coupling and flexibility: This invention completely decouples data producers and consumers through a publish / subscribe model, so they do not need to know about each other's existence. This architecture can greatly improve the modularity and flexibility of the system, ensuring that the upgrade, replacement, or failure of a single component will not have a cascading impact on the entire system, effectively isolating fault domains. Second, they possess powerful dynamic discovery and plug-and-play capabilities: This invention introduces structured topic metadata and a topic registry center, which allows newly launched devices or systems to declare their data capabilities on the bus like "registering a service"; while consumers can dynamically discover the data they need through semantic queries, just like shopping in a "data supermarket"; the entire process does not require pre-configuration or code modification, truly realizing "plug-and-play" industrial data, and can perfectly adapt to dynamic industrial scenarios such as production line additions and subtractions, and equipment upgrades. Third, it boasts high system performance and reliability: the asynchronous processing mode of this invention liberates the production end, the load balancing strategy optimizes the allocation of computing resources, QoS classification ensures the real-time performance of critical data, and the message persistence mechanism ensures the eventual consistency of data interaction; these mechanisms together construct a high-throughput, low-latency, and highly available industrial data pipeline. Fourth, it offers comprehensive security and manageability: through a security management module, this invention achieves end-to-end security protection from access authentication, access control, transmission encryption to operation auditing; fine-grained RBAC policies ensure compliance of data access, meeting the stringent requirements of industrial environments for data security and privacy protection. Fifth, it promotes cross-departmental collaboration and intelligent decision-making: by breaking down information silos, this invention lays a solid foundation for seamless data sharing and collaboration between different departments and systems; high-quality, real-time global data flow provides strong support for upper-level intelligent analysis, predictive maintenance, and scientific decision-making, thereby greatly improving the intelligence level and operational efficiency of the entire industrial network. Attached Figure Description

[0014] Figure 1 This is an overall architecture diagram of a service bus data integration system based on publish-subscribe technology provided in the first embodiment of the present invention; Figure 2 This is a flowchart illustrating the dynamic registration and publishing process for data producers, provided in the second embodiment of the present invention. Figure 3 A flowchart illustrating the dynamic discovery and subscription process for data consumers provided in the second embodiment of the present invention; Figure 4 This is a flowchart of message broker cluster data processing and distribution provided for the second embodiment of the present invention. Detailed Implementation

[0015] The specific embodiments of the present invention will be described in further detail below with reference to the accompanying drawings and examples. The following examples are for illustrative purposes only and are not intended to limit the scope of the invention.

[0016] Example 1:

[0017] A service bus data integration system based on publish-subscribe technology, with the following overall architecture: Figure 1 As shown, modular design enables end-to-end integration of industrial data. Specifically, it includes the following modules: Component S1: Heterogeneous Industrial Subsystem Access Layer. This embodiment covers heterogeneous systems such as Manufacturing Execution Systems (MES), Enterprise Resource Planning (ERP) systems, Supervisory Control and Data Acquisition (SCADA) systems, Programmable Logic Controllers (PLCs), and various intelligent sensors. These systems, as underlying data producers, interface with the service bus through standardized interfaces, breaking down traditional information silos.

[0018] Component S2: Core Industrial Service Bus (ISB) Platform. As the core integration platform, the ISB is responsible for coordinating interactions between producers and consumers. It transforms the previously hard-coded, tightly coupled connection method into a loosely coupled model driven by data itself, thus adapting to rapidly changing industrial production environments.

[0019] Component S3: High-Availability Topic Registry. This center serves as the system's "metadata repository," responsible for centrally storing and managing the logical channels, unique identifiers (TopicIDs), and associated structured metadata of all data topics. It is the core database enabling the system's dynamic discovery and self-description capabilities.

[0020] Component S4: High-performance message broker cluster. This cluster executes topic-based message routing and distribution logic, supporting asynchronous non-blocking communication. It is responsible for receiving the producer's load and accurately pushing messages to consumers according to subscription rules, effectively avoiding system performance bottlenecks in high-concurrency scenarios.

[0021] Component S5: End-to-End Security and Governance Module. This module integrates identity authentication, role-based access control (RBAC), TLS / SSL data transmission encryption, and operation auditing functions to ensure that all subject registration, publishing, and subscription activities are conducted in a controlled environment, meeting industrial-grade data security requirements.

[0022] Component S6: Intelligent Data Consumer Layer. This includes a data analytics engine, visualization applications, a predictive maintenance system, and a decision support system. Consumers do not need to pre-configure the physical addresses of producers; they can dynamically discover and obtain high-quality, real-time global data on demand through the topic registry center.

[0023] Example 2:

[0024] A service bus data integration method based on publish-subscribe technology requires that before an industrial subsystem needs to access the service bus for data interaction, a complete data topic model must first be established, and dynamic integration is performed based on this model. After constructing the data topic model, dynamic registration and publishing of data producers are implemented, followed by dynamic discovery and subscription of data consumers. Based on subscription requests, topic-based message brokering and transmission are executed, and end-to-end security and governance are implemented throughout the process. The method of this embodiment is described below.

[0025] Constructing the data topic model includes: Define topic specifications: Define a set of standardized data topic naming and description specifications; each data topic is abstracted into a logical channel with a unique identifier and associated with a set of structured metadata; the metadata includes at least: topic name, data format, data source system identifier, data update frequency, data timeliness level, and optional business semantic tags.

[0026] Build a topic registry: Establish an efficient and scalable topic registry to centrally store and manage metadata information for all data topics, serving as the core database for dynamic discovery functionality.

[0027] like Figure 2 As shown, the specific process for dynamic registration and publishing of data producers is as follows: Step S1: Topic Specification Definition and Declaration. When modules such as PLC or MES need to connect to the bus, they must first define the data topic and its metadata (such as data format JSONSchema, update frequency, timeliness level, etc.) according to the standardized naming convention. This is the process of building the data topic model. Then, a topic declaration request is sent to the registry center.

[0028] Step S2: Metadata Validation and Uniqueness Verification. Upon receiving a request, the topic registry automatically performs a deep validation of the submitted metadata. The system checks whether the TopicID or name already exists within the bus and ensures that its schema conforms to industry data interchange standards.

[0029] Step S3: Operation Permission Authentication. The security management module intervenes and verifies the producer's digital identity and its corresponding RBAC permission policy. Only entities that pass authentication and have publishing permissions can proceed to the subsequent registration stage; otherwise, the system will immediately return an error code and terminate the process.

[0030] Step S4: Topic entry creation and ID assignment. After all verifications pass, the registry center persists the topic information in the metadata database and returns a confirmation message and the assigned TopicID to the producer, completing the establishment of the logical channel.

[0031] Step S5: Asynchronous Business Data Publishing. After receiving confirmation, the producer publishes the actual business load through the message broker cluster. The publishing process uses TopicID for logical isolation, and the publishing action is completely decoupled from the specific consumer list. The producer can continue executing its own tasks immediately after sending the data without waiting for feedback.

[0032] Step S6: Transmission Encryption and Reception Processing. When receiving data, the message broker ensures data security during transmission through the TLS / SSL protocol, and the broker cluster performs initial message parsing and caching, preparing it for subsequent distribution.

[0033] like Figure 3 As shown, the specific process for dynamic discovery and subscription of data consumers is as follows: Step S11: Multi-dimensional topic discovery query. Data consumers (such as visualization dashboards or analysis modules) initiate query requests to the registry center. The system supports multiple query modes, such as fuzzy matching by topic name, filtering by business semantic tags, or filtering by data source system, helping users accurately locate the resources they need in the "data supermarket".

[0034] Step S12: Metadata List Acquisition and Parsing. The registry center returns the details of the matching topic to the consumer, including key parameters such as data format schema, data publication frequency, and data timeliness level.

[0035] Step S13: Intelligent Subscription Assessment and Schema Matching. The consumer assesses its own parsing capabilities based on the returned schema information. The system uses automated capability matching to ensure the consumer can correctly process structured data under that topic, thereby achieving intelligent subscription selection.

[0036] Step S14: Initiate a subscription request to the message broker. After determining the target topic, the consumer submits a subscription request to the message broker cluster, containing its own identifier and the target TopicID.

[0037] Step S15: Dynamic routing rules are established in real time. The message broker cluster internally configures mapping rules to direct data flows for specified topics to the consumers that initiate the requests. This dynamically established routing mechanism eliminates the need to restart services or perform manual configuration, greatly enhancing system agility.

[0038] Step S16: Subscription Confirmation and Targeted Push Activation. The system returns a confirmation signal to the consumer, and then the message broker, according to the QoS policy, accurately pushes the real-time data published by the producer to the consumer through the established routing logic.

[0039] like Figure 4 As shown, the specific process of data processing and distribution in the message broker cluster is as follows: Step S21: Asynchronous non-blocking message reception. After receiving the data packet sent by the producer, the message broker cluster responds quickly through a memory caching mechanism, immediately returning an ACK confirmation to the producer, thereby completely relieving the producer's synchronous blocking pressure.

[0040] Step S22: QoS-based topic hierarchical resolution. The system extracts the TopicID from the message packet and compares it with the metadata associated with the registry center to resolve the timeliness level and security requirements of the topic.

[0041] Step S23: Differentiated transmission strategy execution. The system allocates different channels for messages based on QoS levels: High-priority channel: For industrial control data with extremely high real-time requirements, a memory queue is used for priority processing, and disk persistence is performed simultaneously to prevent sudden failures.

[0042] Normal priority channel: Standard queues are used to process regular monitoring data to balance system resource usage.

[0043] Step S24: Cluster load balancing scheduling. For scenarios with multiple homogeneous consumers (such as clustered analytics engines), the proxy cluster uses strategies such as consistent hashing to distribute messages evenly to each consumer, avoiding overload of a single consumer node.

[0044] Step S25: End-to-end secure encrypted push. Data is verified again by the security module before being pushed to the consumer and delivered via a TLS encrypted link. The system also records operation logs for subsequent auditing and monitoring.

[0045] Step S26: Message persistence and breakpoint retry mechanism. For messages that fail to be pushed, the system stores them in the persistent storage area. For offline consumers, the system supports consuming historical data from the point of breakpoint after they come back online, ensuring the eventual consistency and reliability of industrial data interaction.

[0046] Example 3:

[0047] This embodiment proposes an electronic device, including: one or more processors, and a memory, wherein the memory is used to store instructions, and when the instructions are executed by the one or more processors, the one or more processors execute the service bus data integration method based on publish-subscribe technology.

[0048] The electronic device may be a mobile phone, computer, or tablet computer, etc., and includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, implements the service bus data integration method based on publish-subscribe technology as described in the embodiments. It is understood that the electronic device may also include input / output (I / O) interfaces and communication components.

[0049] The processor is used to execute all or part of the steps in the service bus data integration method based on publish-subscribe technology as described in the above embodiments. The memory is used to store various types of data, which may include, for example, instructions for any application or method in the electronic device, as well as application-related data.

[0050] The processor may be implemented as an Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), controller, microcontroller, microprocessor, or other electronic components, and is used to execute the service bus data integration method based on publish-subscribe technology described in the above embodiments.

[0051] Example 4:

[0052] This embodiment proposes a computer-readable storage medium that stores executable instructions. When these instructions are executed, if they are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.

[0053] The computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the service bus data integration method based on publish-subscribe technology described in various embodiments of this application.

[0054] The aforementioned storage media include: flash memory, hard disks, multimedia cards, card-type memory (e.g., SD (Secure Digital Memory Card) or DX (Memory Data Register, MDR) memory), random access memory (RAM), static random-access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, disks, optical discs, servers, APP (Application) application stores, and other media capable of storing program verification codes. These media store computer programs, which, when executed by a processor, can implement the various steps of the service bus data integration method based on publish-subscribe technology described above.

[0055] Example 5:

[0056] This embodiment proposes a computer program product, including a computer program or instructions, which, when executed by a processor, implements the service bus data integration method based on publish-subscribe technology.

[0057] Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a computer program product.

[0058] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope defined by the present invention.

Claims

1. A service bus data integration method based on publish-subscribe technology, characterized in that: include: Before an industrial subsystem needs to access the service bus for data interaction, a complete data topic model must first be established, and dynamic integration must be performed based on this model. After the data topic model is built, dynamic registration and publishing of data producers are realized, and then dynamic discovery and subscription of data consumers are realized. Based on the subscription request, topic-based message brokering and transmission are executed. During the process, full-link security and governance need to be implemented. Constructing the data topic model includes: Define topic specifications: Define a standardized set of data topic naming and description specifications; each data topic is abstracted into a logical channel with a unique identifier and associated with a set of structured metadata; the metadata includes at least: topic name, data format, data source system identifier, data update frequency, data timeliness level, and optional business semantic tags; Build a topic registry: Establish an efficient and scalable topic registry to centrally store and manage metadata information for all data topics, serving as the core database for dynamic discovery functionality; The implementation of dynamic registration and publishing for data producers includes: Topic Declaration: Data producers send a topic declaration request to the topic registry, declaring whether they intend to publish a new data topic or an existing data topic, and attaching complete topic metadata; Metadata Validation and Registration: After receiving a request, the topic registry center verifies the legality and uniqueness of the metadata and verifies the producer's operation permissions. After the verification is successful, the corresponding topic entry is created or updated in the topic registry center, and confirmation information and topic ID are returned. Data publishing: Producers publish actual business data load to the logical channel corresponding to the specified topic ID through the message broker cluster. The publishing process is independent of the specific consumer list. The implementation of dynamic discovery and subscription for data consumers includes: Topic discovery: Data consumers initiate query requests to the topic registry center; query methods support fuzzy matching by topic name, filtering by business semantic tags, and system filtering by data source; Smart subscription: Consumers assess their own processing capabilities based on the metadata information returned by the topic registry, select one or more target topics, and send subscription requests to the message broker cluster; Establish dynamic routing: After receiving a subscription request, the message broker cluster internally establishes message routing rules from the corresponding topic to the data consumer. According to the QoS policy, the message broker accurately pushes the real-time data published by the producer to the consumer through the established routing logic. The execution of topic-based message brokerage and transmission includes: Asynchronous non-blocking processing: The message broker cluster returns immediately after receiving data published by the producer, unblocking the producer and improving its response speed; Load balancing: In scenarios where there are multiple homogeneous consumers for the same topic, the message broker uses consistent hashing to distribute messages evenly and avoid single point of overload. Service Quality Assurance: Based on the timeliness level and security requirements defined in the topic metadata, the message broker configures differentiated transmission strategies for different topics; for industrial control data with extremely high real-time requirements, memory queues are used for priority processing, and disk persistence is performed simultaneously to prevent sudden failures; for routine monitoring data, standard queues are used to process the data and balance system resource usage. Message persistence and retry: Persistently store messages that fail to push on critical topics, allowing offline consumers to resume consumption from the breakpoint after recovery, ensuring no data loss; The implementation of end-to-end security and governance includes: Identity authentication and authorization: All producers and consumers must be authenticated by the security management module before accessing the bus; role-based access control policies determine the operation permissions of each subject for specific data topics; Data encryption: During transmission, all data payloads are encrypted using TLS / SSL to ensure the security of data flow; Auditing and Monitoring: The platform records all registration, publishing, and subscription activity logs for all topics and provides a real-time monitoring panel for administrators to perform operations and auditing.

2. A service bus data integration system based on publish-subscribe technology, characterized in that: To implement the service bus data integration method based on publish-subscribe technology as described in claim 1, the system includes a heterogeneous industrial subsystem access layer, a core industrial service bus platform, a highly available topic registry center, a high-performance message broker cluster, a full-link security and governance module, and an intelligent data consumer layer; The heterogeneous industrial subsystem access layer, as the underlying data producer, interfaces with the service bus through standardized interfaces. The core industrial service bus platform is responsible for coordinating the interaction between producers and consumers, transforming the original hard-coded, tightly coupled connection method into a loosely coupled mode driven by the data itself. The high-availability topic registry is the system's "metadata repository," responsible for centrally storing and managing the logical channels, unique identifiers, and associated structured metadata of all data topics. It is the core database that enables the system's dynamic discovery and self-description capabilities. A high-performance message broker cluster executes topic-based message routing and distribution logic, supports asynchronous and non-blocking communication, is responsible for receiving the producer's load, and implements precise push to consumers according to subscription rules; The end-to-end security and governance module integrates identity authentication, role-based access control, TLS / SSL data transmission encryption, and operation auditing functions to ensure that all registration, publishing, and subscription activities of all topics are carried out in a controlled environment, meeting industrial-grade data security requirements. The intelligent data consumer layer includes data analysis engines, visualization applications, predictive maintenance systems, and decision support systems. Consumers do not need to pre-configure the physical address of the producer; they can dynamically discover and obtain high-quality, real-time global data on demand through the topic registry center.

3. An electronic device, characterized in that: It includes one or more processors and a memory for storing instructions that, when executed by the one or more processors, cause the one or more processors to perform the service bus data integration method based on publish-subscribe technology as described in claim 1.

4. A computer-readable storage medium, characterized in that: It stores executable instructions that, when executed, cause the processor to perform the service bus data integration method based on publish-subscribe technology as described in claim 1.

5. A computer program product, characterized in that: It includes a computer program or instructions that, when executed by a processor, implement the service bus data integration method based on publish-subscribe technology as described in claim 1.

Images