Industrial internet T-type distributed intelligent connection cluster architecture, 3M implementation method and software platform

Abstract

The invention provides an industrial internet T-type distributed intelligent connection cluster architecture, a 3M implementation method and a software platform, and the system comprises a transverse platform which is composed of a master cluster and a slave cluster, and the master cluster and the slave cluster achieve data communication through a physical link redundancy technology, a cluster metadata synchronization mechanism, a hierarchical message system and edge calculation; the longitudinal platform comprises a production execution system and industrial equipment and is used for industrial data acquisition and control instruction execution; the distributed intelligent connection cluster enterprise standard comprises a transverse platform internal standard, a longitudinal platform internal standard and a standard between the transverse platform and the longitudinal platform, and is used for standardizing service calling, resource access and communication protocols. According to the transverse and longitudinal integrated T-shaped architecture, Internet sensitive service and industrial steady-state production are deeply fused, comprehensive communication of total elements, total industrial chains and total value chains of cross-industry, cross-level and cross-region cooperative capability of a whole group is realized, and a whole scene from manufacturing to service is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of industrial Internet system software. Specifically, it relates to an industrial Internet T-shaped distributed intelligent connection cluster architecture, a 3M implementation method, and a software platform. Background Art

[0002] The industrial Internet T-shaped distributed intelligent connection cluster architecture and the 3M method have verified their feasibility in ultra-large-scale group enterprises, significantly improving cross-industry collaboration efficiency, system stability, and security. The software platform (ePlat / iPlat), as a core support tool, has achieved a deep integration of horizontal service integration and vertical manufacturing penetration. In the future, it is necessary to further optimize the edge intelligent algorithm and protocol ecosystem to adapt to a wider range of industrial scenarios.

[0003] With the increase in the types of industrial equipment, it is necessary to continuously expand the protocol adaptation layer (such as adding 5G industrial protocols). The false alarm rate of the model under complex working conditions still needs to be further reduced. In extreme network fluctuation scenarios, there are occasional delays in metadata synchronization (probability <0.1%).

[0004] The cross-industrial Internet system unified access to spatio-temporal big data REST service in the patent document CN114979189B does not involve data encryption and data signature considering dedicated high-speed optical fibers. The spatio-temporal big data REST microservice in the patent document CN114979189B does not involve details of security. The spatio-temporal big data REST microservice in the patent document CN114979189B does not involve details of stability guarantee. The patent document CN107147728B is only applicable to the specific system of object storage system and cannot be applied to industrial Internet systems.

[0005] Summary of common defects in the prior art: Most technologies require high-speed optical fiber support and cannot adapt to the low-speed Internet network environment in the "one headquarters, multiple bases" mode; the existing architectures focus on vertical control (such as within a single system) and lack the ability of cross-industry and cross-regional all-factor collaboration; there is generally a lack of mechanisms such as multi-tenant isolation, data encryption, flow limiting and fusing, and it is difficult to meet the high-concurrency and high-reliability requirements of ultra-large-scale clusters; the protocols are single and the architectures are rigid, and they cannot support the access of multiple types of industrial equipment and the requirements of dynamic scaling. Summary of the Invention

[0006] Aiming at the defects in the prior art, the purpose of the present invention is to provide an industrial Internet T-shaped distributed intelligent connection cluster architecture, a 3M implementation method, and a software platform.

[0007] According to the industrial Internet T-shaped distributed intelligent connection cluster architecture provided by the present invention, it includes:

[0008] The horizontal platform consists of a main cluster and a subordinate cluster. Data communication between the main cluster and the subordinate cluster is achieved through physical link redundancy technology, cluster metadata synchronization mechanism, hierarchical message system, and edge computing;

[0009] The vertical platform includes a production execution system and industrial equipment, and is used for industrial data collection and control instruction execution;

[0010] The distributed intelligent cluster enterprise standard includes the internal standard of the horizontal platform, the internal standard of the vertical platform, and the standard between the horizontal and vertical platforms, and is used to standardize service calls, resource access, and communication protocols.

[0011] Preferably, the physical link redundancy technology includes:

[0012] At least two independent physical links are established between the main cluster and the subordinate cluster, and link redundancy is achieved through dual network card binding technology;

[0013] When the network packet loss rate exceeds the preset threshold, it automatically switches to the backup link, and the link selection strategy is based on the preset operator priority.

[0014] Preferably, the cluster metadata synchronization mechanism includes:

[0015] Event-driven synchronization: Device status change events are pushed to the message queue in real time, and the message format follows the CloudEvents standard;

[0016] Batch synchronization: Historical data is synchronized through SFTP at a preset time point, and the differential data is marked as sync_status:pending and updated to synced after synchronization is completed;

[0017] Data versioning: Use Delta Lake to retain historical versions and support retroactive query by timestamp.

[0018] Preferably, the hierarchical message system includes three types of standardized messages:

[0019] Instruction message: The control instruction issued by the main cluster, compressed in Avro format, and contains the instruction type, target cluster ID, and timestamp;

[0020] Data message: The production data packet transmitted between the main and subordinate clusters, with a CRC32 checksum forcibly attached, and the retransmission mechanism is triggered when the check fails;

[0021] Control message: Used for cluster health status monitoring, the message body contains the node status code, and is synchronized at a preset frequency through heartbeat packets.

[0022] Preferably, the edge computing includes:

[0023] The deployment model is used for anomaly detection, and the anomaly determination formula is:

[0024]

[0025] Among them, n is the total number of sensors, and w i is the weight of the sensor, and μ i is the historical mean, and σ i is the standard deviation, and x i is the real-time measurement value of the i-th sensor.

[0026] According to the 3M implementation method of the industrial Internet T-type distributed intelligent connection cluster architecture provided by the present invention, it includes: tenant isolation, combination of centralized and decentralized, and multi-party cloud access;

[0027] The tenant isolation means ensuring that the data, resources, and services of different tenants are independent of each other in the shared infrastructure. Inside the tenant, it follows the enterprise standards of the distributed intelligent connection cluster, and between tenants, it follows the enterprise standards of the distributed intelligent connection cluster;

[0028] The combination of centralized and decentralized means that the distributed intelligent connection cluster includes multiple horizontal platforms, one of which is the central control node, and the other horizontal platforms are edge nodes; inside the horizontal platform, it follows the enterprise standards of the distributed intelligent connection cluster, and between the horizontal platforms, it follows the enterprise standards of the distributed intelligent connection cluster;

[0029] The multi-party cloud access means that the horizontal platform accesses multiple vertical platforms. The vertical platforms include various types of production execution systems and various types of industrial equipment. Inside the vertical platform, it follows the enterprise standards of the distributed intelligent connection cluster, and between the horizontal platform and the vertical platform, it follows the enterprise standards of the distributed intelligent connection cluster.

[0030] Preferably, the tenant isolation includes:

[0031] Technical architecture layer isolation: Allocate independent logical resource pools for each tenant through virtual networks, and use SDN technology to achieve network policy isolation;

[0032] Policy management: Define tenant role permissions based on the RBAC model to limit the scope of resource operations;

[0033] Security reinforcement: Use AES-256-GCM encryption for sensitive data, and the key is dynamically allocated by the cluster-level KMS, and the encryption key is updated according to a preset period.

[0034] Preferably, the combination of centralized and decentralized includes:

[0035] Resource dynamic allocation algorithm: Automatically adjust resource allocation according to the cluster load, and the calculation formula is:

[0036]

[0037] Permission Hierarchy: The central control node is responsible for global policies, and the edge nodes autonomously adjust the priorities of local resources.

[0038] The software platform provided by the present invention includes:

[0039] ePlat: Supports horizontal service integration, provides master-slave cluster management, tenant isolation, and multi-lateral protocol conversion functions;

[0040] iPlat: Supports vertical manufacturing integration and realizes real-time data synchronization between the production execution system and industrial equipment.

[0041] Preferably, the API gateway of the ePlat implements the following functions: Converts the REST API of the horizontal platform into the OPC UA method call of the vertical platform; The data mapping is resolved using JSONPath expressions, and the mapping relationship table includes field mapping and data type coercion rules.

[0042] Compared with the prior art, the present invention has the following beneficial effects:

[0043] (1) By adopting the T-shaped distributed intelligent connection cluster architecture, it solves the problems existing in the vertical five-layer architecture of the ISA-95 "Integration of Information Systems and Control Systems" international standard, such as low vertical integration efficiency, lack of horizontal integration ability of the industrial chain, and non-support for distributed mode;

[0044] (2) By adopting the horizontal-vertical integrated "T" structure, it solves the problems of the distributed deployment mode of one headquarters and multiple bases. The horizontal-vertical integrated "T" architecture deeply integrates industrial steady-state production and Internet sensitive services, realizes the full penetration of all elements, the entire industrial chain, and the entire value chain of the cross-industry, cross-level, and cross-region collaborative capabilities of the entire group, and achieves remarkable results;

[0045] (3) By adopting the 3M architecture of tenant isolation architecture (Multi-Tenant), master-slave combined architecture (Master-Slave), and multi-edge cloud architecture (Multi-Edge), it solves the problems of high concurrency and high reliability key technical problems of massive industrial big data, realizes ultra-large-scale processing, ultra-complex scenario applications, and cross-industry cross-region business collaboration in the distributed manufacturing mode of one headquarters and multiple bases, and supports the uninterrupted operation of nearly 100,000 concurrent users and millions of online users in the Baowu Steel ecosystem, as well as the massive high-concurrency access in the complex transaction consistency scenario. Description of the Drawings

[0046] By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, objectives, and advantages of the present invention will become more obvious:

[0047] Figure 1 It is the T-shaped distributed intelligent connection cluster architecture;

[0048] Figure 2 Schematic diagram of the tenant isolation structure;

[0049] Figure 3 Schematic diagram of the integrated centralization and decentralization structure;

[0050] Figure 4 Schematic diagram of the multi - lateral cloud - access structure;

[0051] Figure 5 Flowchart of the 3M implementation method; Specific implementation manners

[0052] The present invention will be described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but do not limit the present invention in any form. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several changes and improvements can still be made. These all fall within the protection scope of the present invention.

[0053] Embodiment

[0054] The present invention provides a T - type distributed intelligent connection cluster architecture, a 3M implementation method, and a software platform, specifically as follows:

[0055] As Figure 1 , the T - type distributed intelligent connection cluster architecture solves the problems existing in the vertical five - layer architecture of the ISA - 95 "Integration of Information Systems and Control Systems" international standard, such as too many levels, lack of flatness, low vertical penetration efficiency, and lack of horizontal integration ability. The architecture includes: a horizontal platform, a vertical platform, and enterprise standards for distributed intelligent connection clusters.

[0056] The horizontal platform includes: a main cluster and subordinate clusters. The T - type distributed intelligent connection cluster architecture includes one main cluster and any number of subordinate clusters. The main cluster follows the enterprise standards for distributed intelligent connection clusters internally. The subordinate clusters follow the enterprise standards for distributed intelligent connection clusters internally. The main cluster and the subordinate clusters follow the enterprise standards for distributed intelligent connection clusters between them.

[0057] The process of data communication between the main cluster and the subordinate clusters includes physical link redundancy technology, cluster metadata synchronization mechanism, hierarchical message system between clusters, and edge computing:

[0058] Physical link redundancy technology: Adopt the dual - network - card binding technology. At least two independent physical links are established between the main cluster and the subordinate clusters. Two independent physical links are provided by selecting two different operators from China Telecom, China Mobile, and China Unicom. When network jitter (such as packet loss rate > 5%) is detected, the standby channel is automatically switched.

[0059] Cluster Metadata Synchronization Mechanism: The master cluster and the slave clusters need to ensure metadata synchronization. The slave clusters regularly send heartbeat packets to the master cluster and send change information when there are changes in the service status, user status, tenant status within the cluster or when there are faults within the cluster, in order to maintain the metadata of the cluster and ensure global status consistency. The synchronization process needs to follow the message format defined in the "Internal Smart Connection Enterprise Standard for Horizontal Platforms".

[0060] Hierarchical Message System between Clusters: Define three types of standardized messages, which are compressed and transmitted in Avro format:

[0061] 1. Instruction Message: Instructions issued by the master cluster;

[0062] 2. Data Message: Data packets transmitted between the master cluster and the slave clusters;

[0063] 3. Control Message: Cluster health status monitoring and fault notification.

[0064] Edge Computing: Through the Multi-Edge feature, the slave clusters are allowed to directly process 80% of the local requests on the edge side and only upload 20% of the data that requires global coordination to the master cluster, reducing cross-cluster traffic.

[0065] The vertical platform includes: a production execution system and industrial equipment. The production execution system is used for industrial manufacturing. The production execution system collects data from industrial equipment and sends control instructions to industrial equipment. The industrial equipment sends industrial data to the production execution system and at the same time accepts the control instructions of the production execution system.

[0066] The Distributed Smart Connection Cluster Enterprise Standard, which is used to replace the ISA-95 "Integration of Information Systems and Control Systems" international standard, includes: the Internal Smart Connection Enterprise Standard for Horizontal Platforms, the Internal Smart Connection Enterprise Standard for Vertical Platforms, and the Smart Connection Enterprise Standard between Horizontal Platforms and Vertical Platforms.

[0067] The Internal Smart Connection Enterprise Standard for Horizontal Platforms is to ensure efficient collaboration and data consistency between the master cluster and the slave clusters. The Internal Smart Connection Enterprise Standard for Horizontal Platforms includes data format standards, communication protocol specifications, permissions and security.

[0068] The data format standards include a unified data model and metadata specifications.

[0069] Unified Data Model: Adopt a Schema definition based on Protobuf to ensure cross-cluster data parsing compatibility.

[0070] Metadata Specification: It is mandatory for data packets to contain meta-information such as source_cluster_id (cluster ID), data_version (version number), etc., for conflict detection and traceability.

[0071] The communication protocol specification includes the RPC framework and the message queue protocol.

[0072] RPC framework: The gRPC framework is mandatory, and the interface definition between the main cluster and the subordinate cluster must comply with the IDL (Interface Description Language) specification.

[0073] Message queue protocol: In the asynchronous communication scenario, it is required that the message body follows the CloudEvents standard and supports Kafka as the transport layer.

[0074] Permissions and security include the RBAC model and data encryption.

[0075] RBAC model: Cluster nodes need to pass two-way TLS authentication (mTLS) and restrict API access permissions based on roles.

[0076] Data encryption: Sensitive data must be encrypted using AES-256-GCM, and the keys are uniformly managed by the cluster-level KMS.

[0077] The intelligent connection enterprise standard within the vertical platform is to achieve seamless integration and real-time control between the production execution system and industrial devices. The intelligent connection enterprise standard within the vertical platform includes device access specifications, production system interactions, security and reliability, disaster recovery and backup.

[0078] Device access specifications include protocol compatibility and data sampling frequency.

[0079] Protocol compatibility: Support for OPC UA, Modbus TCP, and MQTT protocols is mandatory. The data reported by the device must include mandatory fields such as the device unique identifier (device_id) and timestamp, and the timestamp must comply with the ISO8601 specification.

[0080] Data sampling frequency: The data reporting interval for sensor devices shall not exceed 1 second, and the response delay of control commands shall be less than 50 ms.

[0081] Production system interactions include instruction standardization and status synchronization.

[0082] Instruction standardization: The instructions issued by the production execution system must comply with the ISA-88 batch control model.

[0083] Status synchronization: The device needs to provide real-time feedback on the operation_state (operating status) and error_code (fault code), and the production execution system needs to update the local database within 200 ms.

[0084] Security and reliability include physical isolation and data integrity.

[0085] Physical isolation: Critical equipment (such as PLC) must be isolated by an industrial firewall, and only whitelisted IPs are allowed to access designated ports (such as port 4840 of OPC UA).

[0086] Data integrity: The data reported by the device must be accompanied by a CRC32 check code, and the retransmission mechanism will be triggered when the production execution system fails to verify.

[0087] Disaster recovery and backup include local caching and version compatibility.

[0088] Local cache: The production execution system needs to store the device data of the last 24 hours at the edge node and continue to execute the preset control logic when the network is disconnected.

[0089] Version compatibility: Device firmware upgrades must support dual versions coexisting (A / B partitions), and the rollback time must not exceed 5 minutes.

[0090] The intelligent enterprise standards between horizontal and vertical platforms are designed to connect the data flow and control flow between the production execution system and the cross-cluster business system. The intelligent enterprise standards between horizontal and vertical platforms include protocol conversion rules, security isolation mechanisms, data synchronization strategies, auditing and traceability.

[0091] The protocol conversion rules include API gateway and data mapping table.

[0092] API Gateway: The REST API of the horizontal platform needs to be automatically converted into the OPC UA method call of the vertical platform.

[0093] Data mapping table: defines field mapping relationships (such as mapping horizontal order_quantity to vertical Batch.size), and supports JSONPath expression parsing.

[0094] Security isolation mechanisms include DMZ deployment and access control.

[0095] DMZ deployment: The horizontal and vertical platforms must communicate through the API gateway proxy in the DMZ area, and direct connection to the production network is prohibited.

[0096] Access control: The vertical platform only allows access by specific service accounts of the horizontal platform, and permissions are refined to the device group level.

[0097] Data synchronization strategies include event-driven architecture and batch synchronization.

[0098] Event-driven architecture: Device status change events on the vertical platform need to be pushed to the message queue of the horizontal platform in real time.

[0099] Bulk Synchronization: The horizontal platform triggers a batch task every day at midnight to synchronize the historical production data (in CSV format) of the vertical platform through SFTP. The differential data needs to be marked with sync_status:pending.

[0100] Auditing and Traceability include log correlation and data versioning.

[0101] Log Correlation: Cross-platform operations need to generate a globally unique trace_id that complies with the OpenTracing standard and supports tracing the entire link through Jaeger (such as order creation → device execution → result feedback).

[0102] Data Versioning: The data synchronized bidirectionally needs to retain historical versions (based on Delta Lake) and supports querying and tracing back according to timestamps.

[0103] Such as Figure 5 The 3M implementation method described above includes: Tenant Isolation (Multi-Tenant), Combined Centralized and Decentralized (Master-Slave), and Multi-Edge Cloud Access.

[0104] Such as Figure 2 The Tenant Isolation (Multi-Tenant) described above is to ensure that the data, resources, and services of different tenants are independent of each other in the shared infrastructure through technical means. The horizontal platform contains multiple tenants, and all resources owned by each tenant, including but not limited to users, user groups, data, etc., are isolated from each other. Inside the tenant, it follows the enterprise standard of the distributed intelligent connection cluster. Between tenants, it follows the enterprise standard of the distributed intelligent connection cluster. The specific implementation process includes isolation at the technical architecture layer, policy management and permission control, and security reinforcement.

[0105] Isolation at the technical architecture layer includes virtualization technology, network isolation, and storage isolation.

[0106] Virtualization Technology: Allocate an independent logical resource pool for each tenant through virtual networks and virtualized instances.

[0107] Network Isolation: Adopt software-defined network (SDN) technology to configure independent network policies for different tenants.

[0108] Storage Isolation: Use logical volume partitioning, distributed storage, and database sharding technologies to ensure the physical or logical independence of tenant data.

[0109] Policy Management and Permission Control include RBAC (Role-Based Access Control), quota management, and dynamic policy allocation.

[0110] RBAC (Role-Based Access Control): Define tenant-specific roles and permissions to limit the scope of tenant operations on resources.

[0111] Quota management: Set resource quotas to prevent a single tenant from overusing resources.

[0112] Dynamic policy allocation: Dynamically adjust traffic priorities or security rules according to business needs in a software-defined wide area network (SD-WAN).

[0113] Security reinforcement includes encryption and tunneling technologies, security auditing and monitoring.

[0114] Encryption and tunneling technologies: Use TLS to encrypt the tenant data transmission channel to ensure data privacy.

[0115] Security auditing and monitoring: Ensure the effectiveness of the isolation mechanism through log records, intrusion detection systems (IDS), and regular penetration testing.

[0116] Such as Figure 3 The combination of centralized and decentralized (Master-Slave) means that the intelligent distributed cluster contains multiple horizontal platforms, one of which is the central control node, and the other horizontal platforms are edge nodes. Inside the horizontal platform, it follows the enterprise standard of the distributed intelligent cluster. Between the horizontal platforms, it follows the enterprise standard of the distributed intelligent cluster. Its implementation process includes architecture design, resource integration and flexible allocation, and decentralized governance of permissions and services.

[0117] The architecture design includes a unified management platform and a hierarchical execution mechanism.

[0118] Unified management platform: Establish a central control node responsible for global resource scheduling, policy distribution, and monitoring.

[0119] Hierarchical execution mechanism: Implement local execution at the edge nodes to reduce the pressure on the center.

[0120] Resource integration and flexible allocation include resource pooling and dynamic allocation.

[0121] Resource pooling: Virtualize physical resources into a shared pool and allocate them to different levels or tenants as needed.

[0122] Dynamic allocation: Automatically adjust resource allocation according to the load.

[0123] Decentralized governance of permissions and services includes permission stratification and service differentiation.

[0124] Permission stratification: The central control node is responsible for strategic planning and security compliance, while the edge nodes or tenants have operational autonomy.

[0125] Service differentiation: Provide customized services for each tenant through a multi-tenant architecture.

[0126] Such as Figure 4, the so-called Multi-Edge means that there are a large number of them, and the horizontal platform can access multiple vertical platforms; there are various types, and the vertical platforms include various types of production execution systems and various types of industrial equipment. The internal of the vertical platform follows the distributed intelligent connection cluster enterprise standard. The horizontal platform and the vertical platform follow the distributed intelligent connection cluster enterprise standard. Its implementation process includes a protocol adaptation layer, edge computing, and an elastic expansion mechanism.

[0127] The protocol adaptation layer includes an industrial protocol conversion engine, which supports interoperability of more than 15 standard protocols, converts the industrial protocols of the vertical platform into the target protocols of the horizontal platform, and supports dynamic loading of the industrial protocol conversion engine with a hot deployment time ≤ 50ms:

[0128] Edge computing includes implementing a traffic grading strategy and edge-side anomaly detection.

[0129] Implementing the traffic grading strategy means dividing the data into three levels: real-time data, key metrics, and global data, and taking different strategies for each level of data. Described using Mermaid syntax as follows:

[0130] graph LR

[0131] A[Edge device] --> |60% real-time data| B(Local rule engine)

[0132] A --> |30% key metrics| C(Subordinate cluster preprocessing)

[0133] A --> |10% global data| D(Master cluster decision center)

[0134] Edge-side anomaly detection means deploying the DeepSeek-R1 deep thinking large model to complete 80% of the anomaly detection tasks on the edge side through artificial intelligence.

[0135] The elastic expansion mechanism includes a horizontal platform scaling mechanism, a vertical platform scaling mechanism, and a bandwidth dynamic allocation algorithm:

[0136] The scaling mechanism of the horizontal platform means that the horizontal platform can access one vertical platform or multiple vertical platforms.

[0137] The scaling mechanism of the vertical platform means that the vertical platform can access one production execution system or multiple production execution systems, and can access one type of industrial equipment or multiple types of industrial equipment.

[0138] The bandwidth dynamic allocation algorithm refers to restricting the communication between the vertical platform and the horizontal platform through a certain strategy, shaping the traffic, and ensuring the system stability of the horizontal platform. For example, the core logic is expressed in Python code as follows, where throughput represents traffic and latency represents delay:

[0139] def dynamic_bandwidth(throughput,latency):

[0140] if latency>100ms:

[0141] return throughput*0.7#Reduce speed to ensure stability

[0142] elif throughput<50%:

[0143] return min(throughput*1.5,max_capacity)

[0144] else:

[0145] return throughput

[0146] The software platform includes ePlat and iPlat. The ePlat is used to implement the main cluster and all subordinate clusters. The iPlat is used to implement the production execution system.

[0147] Those skilled in the art know that in addition to implementing the systems, devices, and their various modules provided by the present invention in the form of pure computer-readable program code, the method steps can be logically programmed to enable the systems, devices, and their various modules provided by the present invention to be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers, etc. to achieve the same program. Therefore, the systems, devices, and their various modules provided by the present invention can be considered as a kind of hardware component, and the modules included therein for implementing various programs can also be regarded as the structure within the hardware component; the modules for implementing various functions can also be regarded as either software programs for implementing the method or the structure within the hardware component.

[0148] The specific embodiments of the present invention have been described above. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. Without conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily.

Claims

1. An industrial Internet T-shaped distributed intelligent connection cluster architecture, characterized in that, Including: A horizontal platform, which consists of a main cluster and a subordinate cluster. Data communication between the main cluster and the subordinate cluster is achieved through physical link redundancy technology, cluster metadata synchronization mechanism, hierarchical message system, and edge computing; A vertical platform, which includes a production execution system and industrial equipment for industrial data collection and control instruction execution; Enterprise standards for distributed intelligent connection clusters, including internal standards within the horizontal platform, internal standards within the vertical platform, and standards between the horizontal and vertical platforms, which are used to standardize service calls, resource access, and communication protocols.

2. The industrial Internet T-shaped distributed intelligent connection cluster architecture according to claim 1, wherein The physical link redundancy technology includes: At least two independent physical links are established between the main cluster and the subordinate cluster, and link redundancy is achieved through dual network card binding technology; When the network packet loss rate exceeds a preset threshold, it automatically switches to the backup link, and the link selection strategy is based on the preset operator priority.

3. The industrial Internet T-shaped distributed intelligent connection cluster architecture according to claim 1, characterized in that The cluster metadata synchronization mechanism includes: Event-driven synchronization: Device status change events are pushed to the message queue in real time, and the message format follows the CloudEvents standard; Batch synchronization: Historical data is synchronized through SFTP at a preset time point, and the differential data is marked as sync_status:pending and updated to synced after synchronization is completed; Data versioning: Delta Lake is used to retain historical versions and supports querying back by timestamp.

4. The industrial Internet T-shaped distributed intelligent connection cluster architecture according to claim 1, wherein, The hierarchical message system includes three types of standardized messages: Instruction message: The control instruction issued by the main cluster, compressed in Avro format, including instruction type, target cluster ID, and timestamp; Data message: The production data packet transmitted between the main and subordinate clusters, which is forced to carry a CRC32 checksum, and the retransmission mechanism is triggered when the check fails; Control message: Used for cluster health status monitoring, the message body contains node status codes, and is synchronized at a preset frequency through heartbeat packets.

5. The industrial Internet T-shaped distributed intelligent connection cluster architecture according to claim 1, characterized in that, The edge computing includes: Deploying a model for anomaly detection, and the anomaly determination formula is: where n is the total number of sensors, w i is the weight of the sensor, μ i is the historical mean, σ i is the standard deviation, and x i is the real-time measurement value of the i-th sensor.

6. A 3M implementation method applied to the industrial Internet T-shaped distributed intelligent connection cluster architecture described in any one of claims 1 to 5, characterized in that, Including: Tenant isolation, combination of centralized and decentralized, and multi-sided cloud access; The tenant isolation means ensuring that the data, resources, and services of different tenants are independent of each other in the shared infrastructure. Inside the tenant, it follows the enterprise standards of the distributed intelligent connection cluster, and between tenants, it follows the enterprise standards of the distributed intelligent connection cluster; The combination of centralized and decentralized means that the distributed intelligent connection cluster contains multiple horizontal platforms, one of which is the central control node and the other horizontal platforms are edge nodes; inside the horizontal platform, it follows the enterprise standards of the distributed intelligent connection cluster, and between the horizontal platforms, it follows the enterprise standards of the distributed intelligent connection cluster; The multi-sided cloud access means that the horizontal platform accesses multiple vertical platforms. The vertical platform includes various types of production execution systems and various types of industrial equipment. Inside the vertical platform, it follows the enterprise standards of the distributed intelligent connection cluster, and between the horizontal platform and the vertical platform, it follows the enterprise standards of the distributed intelligent connection cluster.

7. The 3M implementation method according to claim 6, wherein The tenant isolation includes: Isolation at the technical architecture layer: Each tenant is assigned an independent logical resource pool through a virtual network, and network policy isolation is achieved using SDN technology; Policy management: Defining tenant role permissions based on the RBAC model to limit the scope of resource operations; Security enhancement: Use AES-256-GCM encryption for sensitive data. The key is dynamically allocated by the cluster-level KMS, and the encryption key is updated at a preset cycle.

8. The 3M implementation method according to claim 6, wherein, The combination of centralization and decentralization includes: Resource dynamic allocation algorithm: Automatically adjust resource allocation according to the cluster load. The calculation formula is: Permission layering: The central control node is responsible for global policies, and the edge nodes independently adjust the local resource priorities.

9. A software platform, characterized in that, An industrial Internet T-shaped distributed intelligent connection cluster architecture according to any one of claims 1 to 5, comprising: ePlat: Support horizontal service integration, providing master-slave cluster management, tenant isolation, and multi-lateral protocol conversion functions; iPlat: Support vertical manufacturing penetration, and realize real-time data synchronization between the production execution system and industrial equipment.

10. The software platform according to claim 9, characterized in that, The API gateway of the ePlat realizes the following functions: Convert the REST API of the horizontal platform into the OPC UA method call of the vertical platform; The data mapping is parsed using JSONPath expressions, and the mapping relationship table includes field mapping and data type coercion rules.

Images