Resource cross-domain collaborative interconnection and integration method based on service bus

Abstract

The invention discloses a resource cross-domain collaborative interconnection and integration method based on a service bus. The method comprises the following steps: designing a high-compatibility service bus supporting resource wide-area aggregation; a resource service-oriented cascading through platform integration framework is constructed; a service unified management and control system is established on the basis of promoting autonomous management of resources; the high-compatibility service bus runs through the system and service resources, products and equipment services, and provides communication support for the platform integrated framework; the platform integrated framework is based on high-compatibility service bus communication capability, internal and external resource bridging is realized through a service gateway, and service registration and discovery are realized through a mode of combining static configuration and dynamic discovery; the service unified management and control system is based on a high-compatibility service bus and a platform integrated framework, a unified resource management space is formed through a service pool, and full-period sustainable management and control of resource services are achieved. The method has high compatibility and wide-area aggregation capability, the integration efficiency is remarkably improved, and the robustness and maintainability of the system are high.

Description

Technical Field

[0001] This invention relates to the field of industrial internet and intelligent manufacturing technology, and in particular to a method for cross-domain collaborative interconnection and integration of resources based on a service bus. Background Technology

[0002] As the manufacturing industry gradually transforms towards "digitalization, networking, and intelligence," manufacturing enterprises are exhibiting characteristics of "multi-business collaboration, cross-entity cooperation, and dynamic resource changes." However, there are still some problems in the management of cross-domain resources.

[0003] First, manufacturing enterprises have multiple heterogeneous systems such as enterprise resource planning, production execution system, and warehouse management system. These systems have different data formats, communication protocols, and hardware architectures, and are independent of each other. This leads to problems such as the inability of production data to flow across systems and the inability to coordinate and schedule cross-domain resources.

[0004] Second: In today's manufacturing context, cross-environment and cross-resource collaboration is required, but current technologies mostly rely on static configuration, such as manual information entry, and lack dynamic service discovery and subscription mechanisms. Although each service can work independently, there is no mechanism to link them together, requiring manual information transfer, resulting in data isolation, ineffective communication, and the inability to achieve cascading responses of "demand-resource-service".

[0005] Third: The current bus platform integrates many resource services that change frequently. Existing technologies lack a unified resource management system, making it impossible to maintain the consistency of resources between services, resulting in low retrieval efficiency and leading to idle resources or delayed scheduling.

[0006] Fourth: In existing technologies, integration typically uses point-to-point customized interfaces, which results in high coupling, poor scalability, and high maintenance costs. Although some Enterprise Service Bus (ESB) products exist, they usually focus on IT system integration, have poor compatibility with OT layer industrial protocols, and lack effective support for the service-oriented encapsulation and dynamic governance of industrial resources, making it difficult to meet the needs of wide-area resource aggregation and intelligent collaboration in the industrial internet environment.

[0007] Fifth: The closest existing technology is probably the traditional ESB system with SOA architecture at its core, which has performance bottlenecks and functional shortcomings in handling high-concurrency, low-latency industrial real-time data and adapting to diverse industrial protocols.

[0008] In summary, existing technologies lack efficient cross-domain service integration platforms, making it difficult to achieve wide-area aggregation and collaborative invocation of manufacturing resources. Summary of the Invention

[0009] To overcome the aforementioned problems in the existing technology, this invention proposes a cross-domain collaborative interconnection and integration method for resources based on a service bus.

[0010] The technical solution adopted by this invention to solve its technical problem is: a resource cross-domain collaborative interconnection and integration method based on service bus, comprising the following steps: Step 1: Design a highly compatible service bus that supports wide-area resource aggregation; Step 2: Construct a platform-based integration framework for the cascading and interconnected flow of resource services; Step 3: Establish a unified service management system based on promoting autonomous resource governance; In step 1, the highly compatible service bus runs through system and business resources, products and equipment services, providing communication support for the platform integration framework. The platform integration framework obtained in step 2 is based on the communication capabilities of a highly compatible service bus. It bridges internal and external resources through a service gateway and achieves service registration and discovery through a combination of static configuration and dynamic discovery. The unified service management system in step 3 is based on a highly compatible service bus and a platform-based integration framework. It forms a unified resource management space through a service pool, enabling sustainable management and control of resource services throughout their entire lifecycle.

[0011] The above-described cross-domain collaborative interconnection and integration method for resources based on a service bus, in step 1, employs a layered design for the highly compatible service bus, which, from top to bottom, includes a resource access layer, a protocol adaptation layer, a middleware layer, a service management layer, and an application interface layer. The resource access layer is used to connect the enterprise's scattered resources to a highly compatible service bus. The protocol adaptation layer provides a protocol access point and converts the data packets of the access protocol into a format that can be understood by the intermediate layer; The intermediate layer acts as a message intermediary, performing content routing, protocol routing, or destination routing on message data packets transformed by the protocol adaptation layer based on preset or dynamic routing rules, and reliably delivering the messages to the target service. The service management layer is used to monitor the entire service process; The application interface layer is used to provide standardized interfaces to the outside world.

[0012] The above-described cross-domain collaborative interconnection and integration method for resources based on service bus achieves resource access through the service bus function module of the enterprise's internal business domain. The service bus function module of the enterprise's internal business domain provides hybrid cloud support, adapts to various communication protocols, and achieves reasonable distribution of service requests through reverse proxy, traffic allocation, and session persistence mechanisms. It integrates and connects different systems and services through the API platform, sets up service caching, caches frequently used service results, and sets up authentication, session management, and single sign-on functions to ensure system security.

[0013] The above-mentioned cross-domain collaborative interconnection and integration method for resources based on service bus, specifically includes step 2 as follows: Step 2.1, Processing of internal and external resource services: Dynamic discovery is used to detect changes in internal resource services in real time, while static configuration is used to manage external resource services; Step 2.2, register internal and external resource services: register your own metadata information to the service directory. The service directory supports multi-condition combined search and fuzzy search, and provides a unified entry point for service search, discovery and invocation. Step 2.3, Content distribution and cross-environment, cross-ownership service capability interconnection: Content distribution achieves efficient delivery of resource service content and cascading connectivity in a wider range through a central control gateway, a single entry point, and an asynchronous communication mechanism.

[0014] In the above-mentioned cross-domain collaborative interconnection and integration method based on service bus, step 2.3 involves the central control gateway performing unified routing and management of service requests; a single entry point providing a unified service access entry point for users and the system; and asynchronous communication using a non-blocking method to transmit messages during interactions between services.

[0015] The above-mentioned cross-domain collaborative interconnection and integration method for resources based on service bus, specifically includes step 3 as follows: Step 3.1, External Control: By using query language and indexing mechanisms, combined with full-text indexing and attribute indexing, the system can retrieve resource services from the service catalog; control the access permissions of different users and systems to resource services, and record the usage of resource services; Step 3.2, Internal Control: Ensure service consistency by enabling service querying and management through link tracing, dynamic routing, and attribute mapping; support service expansion including horizontal scaling, vertical scaling, and fault recovery; construct a logically unified service pool to virtualize and pool all registered service instances, forming a unified resource management space. This service pool provides role-based access control (RBAC) and a unified retrieval and authorization interface externally, and internally executes service lifecycle management, status monitoring, and elastic scaling strategies; employ continuous integration and rolling updates to achieve service iteration; and perform full backups and service snapshots to ensure the security and recoverability of service data.

[0016] The beneficial effects of this invention include: High compatibility and wide-area aggregation capability: Through a multi-protocol adaptation middleware layer, it seamlessly integrates IT and OT resources, fundamentally solving the problem of interconnecting heterogeneous systems and realizing wide-area aggregation of manufacturing resources.

[0017] Significantly improved integration efficiency: The platform-based integration model and unified service catalog avoid the development workload of point-to-point integration, greatly accelerating the access of new resources and the combination of services.

[0018] High system robustness and maintainability: The microservice architecture and unified service governance mechanism decouple the various parts of the system, isolate faults, and make it easy to upgrade and maintain.

[0019] Resource utilization optimization: Through unified management and intelligent scheduling of services, resource supply and demand can be matched more accurately, resource idleness can be reduced, thereby improving the resource utilization efficiency of the entire manufacturing system. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the present invention. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solution of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0022] This embodiment discloses a method for cross-domain collaborative interconnection and integration of resources based on a service bus. It aims to provide a method to solve the problems of difficulty in cross-domain integration of multi-source heterogeneous resources in manufacturing enterprises, low service aggregation efficiency, and lack of unified management and autonomous governance capabilities of the system, so as to realize cross-domain collaborative interconnection and integration of resources and improve the overall service response capability and resource utilization efficiency of manufacturing enterprises.

[0023] The method in this embodiment is as follows: Figure 1 As shown: First, the highly compatible service bus, as the system's communication infrastructure, is located at the core of the diagram and is responsible for enabling efficient communication between internal and external services. It adopts Integrated Platform as a Service (iPaaS) as its core to build an open bus platform that is "efficient, easy to use, stable, and secure," and realizes the conversion from resources to services, and between services, through a protocol adaptation middleware layer.

[0024] Second, the platform integration framework is responsible for the integration and connection of services, and includes the following key components: Service cascading connectivity: Enables the interconnection of service capabilities across environments and ownership, and uses service gateways to bridge internal and external enterprise resource services; Static configuration and dynamic discovery: This approach combines two modes to implement a service registration and discovery mechanism. Service subscription mechanism: Provides high-quality service subscription functionality based on content delivery networks.

[0025] Third, the unified service management system enables full lifecycle management of services, including: Service pool management: forming a unified resource management space, providing external retrieval and authorization, and internal updates and backups; Resource consistency maintenance: Design methods for maintaining resource consistency between services; Service scaling strategies: Horizontal and vertical scaling strategies for introducing service instances; The highly compatible service bus serves as the core hub, connecting system and business resources, products and equipment services, and providing basic communication support for the platform-based integration framework.

[0026] The platform-based integration framework is based on the communication capabilities of the service bus. It bridges internal and external resources through a service gateway and achieves service registration and discovery through a combination of static configuration and dynamic discovery, forming an open service integration platform.

[0027] The unified service management system is based on numerous services integrated on the service bus. It forms a unified resource management space through service pools, enabling sustainable management and control of resource services throughout their entire lifecycle.

[0028] Figure 1 This demonstrates a complete integration path from internal enterprise resource services to external enterprise resource services, achieving bidirectional connectivity through a service gateway, showcasing a complete technical route for cross-domain collaborative interconnection and integration of resources. Modules communicate through standardized interfaces and protocols, forming a hierarchical system architecture that enables efficient collaborative interconnection and integration of manufacturing resources. Specifically, this includes the following steps: Step 1: A highly compatible service bus supporting wide-area resource aggregation; Step 2: Platform-based integration for cascading and interconnecting resource services; Step 3: Unified management and control of services to promote autonomous resource governance.

[0029] First, a layered design approach is adopted for the highly compatible service bus. From top to bottom, it includes a resource access layer, a protocol adaptation layer, a middleware layer, a service management layer, and an application interface layer.

[0030] (1) Resource access layer: responsible for connecting various scattered resources in the enterprise to the bus, and providing diverse access methods (wired, wireless, and short-range) and stable access methods.

[0031] (2) Protocol Adaptation Layer: This layer provides access points for protocols and converts data packets from access protocols into a format that can be understood by the middle layer. For example, it has built-in access points for multiple protocols such as OPC UA, Modbus, MQTT, and HTTP, and converts data of different formats (binary, XML, JSON, etc.) into a standard format defined by the bus (such as JSON-LD). (3) Middleware: The middleware accurately and efficiently sends the data transformed by the protocol adaptation layer to the target service. It supports both synchronous and asynchronous data reception, uses dynamic routing rules, and employs mechanisms for "resuming interrupted transmission" and "retransmission" in data transmission. Even if a network interruption occurs, transmission can continue after recovery, preventing data loss. It also performs flow control, automatically adjusting the transmission speed when the data volume is too large.

[0032] (4) Service Management Layer: Monitor the entire process to ensure data transmission security and implement load monitoring to prevent bus overload. Use load balancing and access control to control traffic stability and data security.

[0033] (5) Application Interface Layer: Provides standardized interfaces to the outside world, making it convenient for enterprise application systems to use bus resources and services.

[0034] The service bus is the core foundation of the entire technology system, playing a key role in wide-area resource aggregation and highly compatible interconnection.

[0035] (a) Service bus integration and service-oriented architecture All kinds of resources, including business resources, system resources, product resources, and equipment resources, must first undergo a "service-oriented" process, transforming them into service forms that can be managed and scheduled by the service bus. This step is a prerequisite for resources to access the service bus. By standardizing and encapsulating different types and forms of resources, they are given unified service interfaces and interaction methods, laying the foundation for subsequent cross-domain collaboration.

[0036] (ii) Service bus functional modules of enterprise internal business domains Within an enterprise's internal business domain, the service bus comprises several key functional modules, ensuring efficient, stable, and secure resource aggregation and service interaction.

[0037] (1) Integration Platform: Provides hybrid cloud support, is compatible with different cloud environments, and meets the resource integration needs of enterprises under multi-cloud architecture; has protocol compatibility capabilities, can adapt to various communication protocols, and eliminate protocol barriers between different systems. For example, it has built-in access points for multiple protocols such as OPC UA, Modbus, MQTT, HTTP, etc., and converts data of different formats (binary, XML, JSON, etc.) into the standard format defined by the bus (such as JSON-LD); in terms of message transmission, it supports both synchronous and asynchronous data reception, and the routing rules adopt dynamic routing. In terms of data transmission, it adopts the mechanism of "breakpoint resumption" and "message retransmission".

[0038] (2) Load balancing: Through mechanisms such as reverse proxy, traffic distribution and session persistence, the reasonable distribution of service requests is achieved. Reverse proxy hides the specific details of internal services, enhancing the security of the system; traffic distribution ensures the load balance of each service node, avoiding the situation where some nodes are overloaded while other nodes are idle, thus improving the overall performance of the system; session persistence ensures the continuity of user sessions and improves the user experience.

[0039] (3) API Platform: Enables seamless integration, allowing different systems and services to easily connect through API; provides service caching function to cache frequently used service results, reduce redundant calculations and network transmission, and improve service response speed; and provides enterprises with a unified access and management interface for resources based on API, with a resource-oriented approach.

[0040] (4) Access control: This includes functions such as authentication, session management, and single sign-on. Authentication ensures that only legitimate users can access system resources; session management effectively controls user sessions and ensures the security of the session process; single sign-on allows users to access multiple related systems with only one authentication, improving user convenience and system security.

[0041] Second, regarding platform-based integration for resource service cascading: a service integration mechanism of "service gateway + static configuration + dynamic discovery" is constructed to achieve cross-environment and cross-ownership service cascading.

[0042] (1) A service gateway is a bridging node for internal and external resource services of an enterprise. Internally, it connects to the standardized services of the bus platform, and externally, it connects to the heterogeneous services of suppliers or customers, so as to realize the isolation and adaptation of "internal and external" services.

[0043] (2) Service registration mechanism: A combination of "static configuration + dynamic discovery" is adopted. Static configuration: For stable services (such as order query service), registration is completed by the administrator manually entering the service address and interface parameters. Dynamic discovery refers to the use of specific technical means to enable services to automatically register their own information with the service registry during operation, while other services can also obtain the latest service list and related information from the registry in real time. Service registration, update and deregistration operations can be performed dynamically according to the actual running status of the service.

[0044] (3) Adopt modular and loosely coupled design principles. The modular principle is to modularize the commonly used parts to facilitate reuse and replacement; the loosely coupled design is to ensure that there is no strong dependency between the various software parts.

[0045] (4) Single entry point call: Any call to any service is made through a single entry point.

[0046] Platform integration is a key link in realizing the interconnection of resource services, which mainly unfolds from two dimensions: internal resource services and external resource services.

[0047] (a) Processing of internal resource services and external resource services (1) Internal resource services: By adopting a dynamic discovery approach, the service bus can detect changes in internal resource services in real time, such as the addition, updating, or discontinuation of services. Through dynamic discovery, the service bus can obtain the latest service information in a timely manner, ensuring the efficient integration and invocation of internal resource services.

[0048] (2) External resource services: Since external resource services are relatively stable, they are managed using static configuration. By pre-configuring relevant information of external resource services, such as service address and interface specifications, the external resource services are connected to the internal system.

[0049] (II) Service Registration and Service Directory Whether it's an internal or external resource service, it needs to register as a service, registering its metadata information (such as service name, interface, version, provider, etc.) in the service directory. The service directory acts as a "yellow pages" for resource services, centrally storing information on all services that can be integrated, providing a unified entry point for finding, discovering, and invoking services.

[0050] (III) Interconnection of content distribution and cross-environment, cross-ownership service capabilities Content distribution achieves efficient delivery of resource service content through mechanisms such as a central control gateway, a single entry point, and asynchronous communication. The central control gateway performs unified routing and management of service requests, ensuring that requests accurately reach the target service; the single entry point provides users and the system with a unified service access point, simplifying the service access process; and asynchronous communication uses a non-blocking method to transmit messages in the interaction between services, improving the system's concurrent processing capabilities and response speed.

[0051] By interconnecting service capabilities across environments (such as different network environments, cloud environments, etc.) and ownership (such as resources owned by different departments or enterprises), the geographical and ownership limitations of resources are broken down, enabling resource services to be cascaded and connected on a wider scale, allowing enterprises to fully integrate internal and external resources and provide strong support for business development.

[0052] Third, promote unified management and control of services that facilitate autonomous resource governance.

[0053] (1) Service version and fault management: Establish a rapid fault recovery mechanism; for example, use a heartbeat detection mechanism to detect faults, and when a fault is detected, apply the fuse mode to try automatic recovery and restart.

[0054] (2) Resource consistency between services: Ensure that the resource information obtained by each service is accurate and real-time; a hybrid execution mode of "Saga + synchronous + asynchronous" can be adopted.

[0055] (3) Efficient resource retrieval: Supports fuzzy query technology for key resource attributes (4) Service elastic scaling: Horizontal scaling supports high concurrency, and vertical scaling enhances the service's processing capacity. (5) Unified management and control of service pool: Construct a unified service pool to provide external retrieval and authorization, and to perform internal updates and backups.

[0056] Unified management and control of services is an important means to ensure the efficient, safe and stable operation of resource services, and it is mainly carried out from two aspects: external management and internal management.

[0057] (a) External control External control mainly involves aspects such as retrieval and authorization.

[0058] (1) Retrieval: Through query language and indexing mechanism, the system enables fast and accurate retrieval of resource services in the service catalog. Users and the system can specify search conditions through query language according to their own needs, and use the indexing mechanism to improve retrieval efficiency and quickly find the resource services they need.

[0059] (2) Authorization: This includes two parts: access control and usage logs. Access control provides fine-grained control over the access rights of different users and systems to resource services, ensuring that only entities with the corresponding permissions can access specific services; usage logs record the usage of resource services, providing a basis for subsequent auditing, billing, and service optimization.

[0060] (ii) Internal control Internal controls mainly revolve around service consistency, scalability, updates, and backups.

[0061] (1) Service Consistency: Ensure data consistency and resource consistency, and perform version control. Data consistency ensures that data on different nodes can remain synchronized and consistent in a distributed environment; resource consistency ensures that resource services perform consistently in different environments and scenarios; version control manages service versions, facilitating service upgrades, rollbacks, and other operations, and ensuring that service versions are traceable and controllable.

[0062] (2) Service Query: Through functions such as link tracing, dynamic routing, and attribute mapping, efficient querying and management of services can be achieved. Link tracing can track the complete call chain of service requests, helping to troubleshoot problems in the service call process; dynamic routing dynamically adjusts the routing path of service requests according to actual conditions (such as service load, network conditions, etc.), improving service access efficiency; attribute mapping associates and maps different attributes of services, facilitating multi-dimensional querying and analysis of services.

[0063] (3) Service Expansion: Supports horizontal expansion, vertical expansion, and fault recovery. Horizontal expansion increases the system's processing capacity by increasing the number of service nodes, which is suitable for scenarios with a large number of concurrent requests; vertical expansion enhances the system's capacity by improving the performance of individual service nodes (such as increasing CPU, memory, and other resources); the fault recovery mechanism can quickly detect and restore services when they fail, ensuring high availability.

[0064] (4) Service pool: Provides services to the outside world through API, centrally manages and schedules various resource services, and realizes on-demand allocation and efficient utilization of resources.

[0065] (5) Updates: Continuous integration and rolling updates are used to achieve rapid service iteration. Continuous integration quickly integrates code changes into the existing system and performs automated testing to ensure the correctness of the changes; rolling updates gradually replace old versions of service instances without interrupting services, achieving smooth service upgrades and minimizing the impact on business.

[0066] (6) Backup: Perform full backups and service snapshots to ensure the security and recoverability of service data. Full backups provide a complete backup of all service data to ensure data integrity; service snapshots record the service status at a specific point in time, making it easy to quickly restore the service to a specified state when needed.

[0067] This embodiment realizes the integration and interconnection of various internal and external resources of an enterprise; by leveraging platform-based integration oriented towards resource service cascading, it breaks down the geographical and ownership restrictions of resources and achieves cascading resource services; and by promoting unified management and control of services that facilitate autonomous resource governance, it ensures the efficient, secure, and stable operation of resource services.

[0068] It should be noted that the system of this invention can be deployed in a hybrid cloud environment, and its microservice architecture ensures good horizontal scalability. This invention is not only applicable to discrete manufacturing, but also to process industries and other scenarios requiring multi-level resource integration. Specific open-source components involved in this invention (such as Nacos, Spring Cloud Gateway) can be considered as preferred implementations, but the scope of protection of this invention is not limited thereto.

[0069] The above embodiments are merely exemplary embodiments of the present invention and are not intended to limit the present invention. Those skilled in the art can make various modifications or equivalent substitutions to the present invention within its scope and spirit, and such modifications or equivalent substitutions should also be considered to fall within the scope of protection of the present invention.

Claims

1. A method for cross-domain collaborative interconnection and integration of resources based on service bus, characterized in that, Includes the following steps: Step 1: Design a highly compatible service bus that supports wide-area resource aggregation; Step 2: Construct a platform-based integration framework for the cascading and interconnected flow of resource services; Step 3: Establish a unified service management system based on promoting autonomous resource governance; In step 1, the highly compatible service bus runs through system and business resources, products and equipment services, providing communication support for the platform integration framework. The platform integration framework obtained in step 2 is based on the communication capabilities of a highly compatible service bus. It bridges internal and external resources through a service gateway and achieves service registration and discovery through a combination of static configuration and dynamic discovery. The unified service management system in step 3 is based on a highly compatible service bus and a platform-based integration framework. It forms a unified resource management space through service pools to achieve sustainable management and control of resource services throughout their entire lifecycle.

2. The method for cross-domain collaborative interconnection and integration of resources based on service bus according to claim 1, characterized in that, In step 1, the highly compatible service bus adopts a layered design, which includes, from top to bottom, a resource access layer, a protocol adaptation layer, a middleware layer, a service management layer, and an application interface layer. The resource access layer is used to connect the enterprise's scattered resources to a highly compatible service bus. The protocol adaptation layer provides a protocol access point and converts the data packets of the access protocol into a format that can be understood by the intermediate layer; The intermediate layer acts as a message intermediary, performing content routing, protocol routing, or destination routing on message data packets transformed by the protocol adaptation layer based on preset or dynamic routing rules, and reliably delivering the messages to the target service. The service management layer is used to monitor the entire service process; The application interface layer is used to provide standardized interfaces to the outside world.

3. The method for cross-domain collaborative interconnection and integration of resources based on service bus according to claim 2, characterized in that, The resource access layer achieves resource access through the service bus function module of the enterprise's internal business domain. The service bus function module of the enterprise's internal business domain provides hybrid cloud support, adapts to various communication protocols, and achieves reasonable distribution of service requests through reverse proxy, traffic allocation, and session persistence mechanisms. It integrates and connects different systems and services through the API platform, sets up service caching, caches frequently used service results, and sets up authentication, session management, and single sign-on functions to ensure system security.

4. The method for cross-domain collaborative interconnection and integration of resources based on service bus according to claim 1, characterized in that, Step 2 specifically includes: Step 2.1, Processing of internal and external resource services: Dynamic discovery is used to detect changes in internal resource services in real time, while static configuration is used to manage external resource services; Step 2.2: Register internal and external resource services: Register the service's metadata information to the service directory. The service directory supports multi-condition combined retrieval and fuzzy search, and provides a unified entry point for service search, discovery and invocation. Step 2.3, Content distribution and cross-environment, cross-ownership service capability interconnection: Content distribution achieves efficient delivery of resource service content and cascading connectivity in a wider range through a central control gateway, a single entry point, and an asynchronous communication mechanism.

5. The resource cross-domain collaborative interconnection and integration method based on service bus according to claim 4, characterized in that, In step 2.3, the central control gateway performs unified routing and management of service requests; the single entry point provides a unified service access point for users and the system; and asynchronous communication transmits messages in a non-blocking manner during interactions between services.

6. The method for cross-domain collaborative interconnection and integration of resources based on service bus according to claim 4, characterized in that, Step 3 specifically includes: Step 3.1, External Control: By using query language and indexing mechanisms, combined with full-text indexing and attribute indexing, the system can retrieve resource services from the service catalog; control the access permissions of different users and systems to resource services, and record the usage of resource services; Step 3.2, Internal Control: Ensure service consistency by enabling service querying and management through link tracing, dynamic routing, and attribute mapping; support service expansion including horizontal scaling, vertical scaling, and fault recovery; construct a logically unified service pool to virtualize and pool all registered service instances, forming a unified resource management space. This service pool provides role-based access control and a unified retrieval and authorization interface externally, and internally executes service lifecycle management, status monitoring, and elastic scaling strategies; employ continuous integration and rolling updates to achieve service iteration; and perform full backups and service snapshots to ensure the security and recoverability of service data.

Images