Access method and device of industrial equipment, electronic equipment and storage medium

Abstract

The application provides an access method and device of an industrial equipment, electronic equipment and a storage medium. The method comprises the following steps: receiving an equipment access request, the equipment access request being used for requesting to access a to-be-accessed equipment to a management equipment; the equipment access request comprising first equipment information of the to-be-accessed equipment and second equipment information of the management equipment; the management equipment being an intermediate carrier for the to-be-accessed equipment to interact with a server; determining at least one access component suitable for the to-be-accessed equipment in a cloud component library according to the first equipment information and the second equipment information; wherein the cloud component library comprises a plurality of basic components, and each basic component is a smallest reusable software unit with independent functions; processing the at least one access component to obtain an access program of the to-be-accessed equipment; and accessing the to-be-accessed equipment to the management equipment according to the access program. The application improves the access flexibility of the industrial equipment.

Description

Technical Field

[0001] This application relates to the field of industrial internet technology, and in particular to an access method, device, electronic device and storage medium for industrial equipment. Background Technology

[0002] Device access technology is a technology used in the Industrial Internet to enable real-time acquisition, transmission, and analysis of device data. In some scenarios, it is necessary to connect heterogeneous intelligent terminals and / or dumb devices to management devices to collect data from these heterogeneous intelligent terminals and / or dumb devices.

[0003] In related technologies, device access processing can be handled through preset access programs. Specifically, the server stores multiple access programs adapted to different device models and protocol types. The server receives device access requests sent by the management device, which request the connection of a target device to the management device. Then, based on information such as the target device's model and protocol type, the server determines the corresponding access program for the target device and connects the target device to the management device based on that program. However, this method can only connect target devices of the preset access program's model and protocol type to the management device, resulting in poor flexibility in device access. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for connecting industrial equipment, in order to solve the problem of poor flexibility in connecting industrial equipment.

[0005] In a first aspect, embodiments of this application provide an industrial equipment access method, applied to a server, the method comprising:

[0006] The system receives device access requests, which are used to request that the device to be accessed be connected to the management device. The device access request includes first device information of the device to be accessed and second device information of the management device. The management device serves as an intermediary for the interaction between the device to be accessed and the server.

[0007] Based on the first device information and the second device information, at least one access component adapted to the device to be accessed is determined in the cloud component library; wherein, the cloud component library includes multiple basic components, each of which is the smallest reusable software unit with independent functions;

[0008] Process at least one access component to obtain the access program for the device to be accessed;

[0009] Connect the device to be connected to the management device according to the access procedure.

[0010] In one possible implementation, the first device information includes the communication protocol type of the device to be accessed, and the cloud component library includes multiple combined components; wherein each combined component is a functional combination of at least two basic components integrated based on a preset dependency relationship;

[0011] Based on the first device information and the second device information, at least one access component adapted to the device to be accessed is determined from the cloud component library, including:

[0012] Based on the mapping relationship between protocol type and composite component, and the communication protocol type, determine the target composite component that is compatible with the communication protocol type from among multiple composite components;

[0013] Based on the target composite components and the cloud component library, at least one first candidate component is identified among multiple basic components;

[0014] At least one access component is determined from at least one first candidate component based on the first device information and the second device information.

[0015] In one possible implementation, the cloud-based component library includes a component dependency topology, which indicates the dependencies between multiple basic components; based on the target composite component and the cloud-based component library, at least one first candidate component is determined from among the multiple basic components, including:

[0016] Identify at least one target component in the target assembly;

[0017] For each target component in at least one target component, at least one associated component of the target component is determined based on the component dependency topology; the at least one associated component is a component among multiple basic components that has a direct or indirect dependency relationship with the target component.

[0018] At least one associated component of each of the at least one target component is deduplicated to obtain at least one first candidate component.

[0019] In one possible implementation, determining at least one associated component of the target component based on component dependency topology includes:

[0020] Perform a first operation, which includes: determining the (i+1)th level associated component that has a direct dependency relationship with the i-th level associated component based on the component dependency topology; where i is an integer greater than or equal to 0; when i=0, the 0th level associated component is the target component;

[0021] Until i is greater than or equal to a preset threshold, and / or there is no i+1 level associated component in the component dependency topology that has a direct dependency relationship with the i-th level associated component, at least one associated component is obtained; wherein, at least one associated component includes the i+1 level associated component.

[0022] In one possible implementation, the first device information includes the functional requirements of the device to be accessed; determining at least one access component from at least one first candidate component based on the first device information and the second device information includes:

[0023] Based on functional requirements, at least one second candidate component is determined from at least one first candidate component; wherein the component function of each second candidate component matches the functional requirements.

[0024] Based on the second device information, at least one third candidate component is determined from at least one second candidate component;

[0025] For each of the at least one third candidate components, the third candidate components are processed to obtain the access component corresponding to the third candidate component;

[0026] Among them, at least one access component includes at least one access component corresponding to each of the third candidate components.

[0027] In one possible implementation, the second device information includes hardware resource information and operational constraints of the management device; determining at least one third candidate component from at least one second candidate component based on the second device information includes:

[0028] Construct a resource assessment model for the devices to be accessed based on hardware resource information and operational constraints;

[0029] For each of the at least one second candidate components, the second candidate components are processed based on a resource assessment model to determine the resource consumption and runtime of the second candidate components;

[0030] Determine the resource thresholds corresponding to hardware resource information and the duration thresholds corresponding to operational constraints;

[0031] For each of the at least one second candidate component, if the resource consumption of the second candidate component is less than or equal to the resource threshold and the runtime is less than or equal to the runtime threshold, the second candidate component is determined as the third candidate component.

[0032] In one possible implementation, the third candidate component is processed to obtain the access component corresponding to the third candidate component, including:

[0033] The code of the third candidate component is stripped to identify at least one function branch and at least one global variable of the third candidate component;

[0034] In at least one function branch, identify at least one target function branch that is actually called;

[0035] Determine at least one target global variable that is actually invoked in at least one global variable;

[0036] The code is refactored for at least one objective function branch and at least one objective global variable to obtain the access component corresponding to the third candidate component.

[0037] Secondly, this application provides an access device for industrial equipment, the device comprising:

[0038] The receiving module is used to receive device access requests, which request the device to be accessed to be connected to the management device. The device access request includes first device information of the device to be accessed and second device information of the management device. The management device is the intermediary carrier for the interaction between the device to be accessed and the server.

[0039] The determination module is used to determine at least one access component adapted to the device to be accessed in the cloud component library based on the first device information and the second device information; wherein, the cloud component library includes multiple basic components, and each basic component is the smallest reusable software unit with independent functions;

[0040] The processing module is used to process at least one access component to obtain the access program for the device to be accessed;

[0041] The access module is used to connect the device to be accessed to the management device according to the access program.

[0042] In one possible implementation, the first device information includes the communication protocol type of the device to be accessed, and the cloud component library includes multiple combined components; wherein each combined component is a functional combination of at least two basic components integrated based on a preset dependency relationship; the determining module is specifically used for:

[0043] Based on the mapping relationship between protocol type and composite component, and the communication protocol type, determine the target composite component that is compatible with the communication protocol type from among multiple composite components;

[0044] Based on the target composite components and the cloud component library, at least one first candidate component is identified among multiple basic components;

[0045] At least one access component is determined from at least one first candidate component based on the first device information and the second device information.

[0046] In one possible implementation, the cloud-based component library includes a component dependency topology, which indicates the dependencies between multiple basic components; the determining module is specifically used for:

[0047] Identify at least one target component in the target assembly;

[0048] For each target component in at least one target component, at least one associated component of the target component is determined based on the component dependency topology; the at least one associated component is a component among multiple basic components that has a direct or indirect dependency relationship with the target component.

[0049] At least one associated component of each of the at least one target component is deduplicated to obtain at least one first candidate component.

[0050] In one possible implementation, the determining module is specifically used for:

[0051] Perform a first operation, which includes: determining the (i+1)th level associated component that has a direct dependency relationship with the i-th level associated component based on the component dependency topology; where i is an integer greater than or equal to 0; when i=0, the 0th level associated component is the target component;

[0052] Until i is greater than or equal to a preset threshold, and / or there is no i+1 level associated component in the component dependency topology that has a direct dependency relationship with the i-th level associated component, at least one associated component is obtained; wherein, at least one associated component includes the i+1 level associated component.

[0053] In one possible implementation, the first device information includes the functional requirements of the device to be accessed; the determining module is specifically used for:

[0054] Based on functional requirements, at least one second candidate component is determined from at least one first candidate component; wherein the component function of each second candidate component matches the functional requirements.

[0055] Based on the second device information, at least one third candidate component is determined from at least one second candidate component;

[0056] For each of the at least one third candidate components, the third candidate components are processed to obtain the access component corresponding to the third candidate component;

[0057] Among them, at least one access component includes at least one access component corresponding to each of the third candidate components.

[0058] In one possible implementation, the second device information includes hardware resource information and operating constraints of the management device; the determining module is specifically used for:

[0059] Construct a resource assessment model for the devices to be accessed based on hardware resource information and operational constraints;

[0060] For each of the at least one second candidate components, the second candidate components are processed based on a resource assessment model to determine the resource consumption and runtime of the second candidate components;

[0061] Determine the resource thresholds corresponding to hardware resource information and the duration thresholds corresponding to operational constraints;

[0062] For each of the at least one second candidate component, if the resource consumption of the second candidate component is less than or equal to the resource threshold and the runtime is less than or equal to the runtime threshold, the second candidate component is determined as the third candidate component.

[0063] In one possible implementation, the determining module is specifically used for:

[0064] The code of the third candidate component is stripped to identify at least one function branch and at least one global variable of the third candidate component;

[0065] In at least one function branch, identify at least one target function branch that is actually called;

[0066] Determine at least one target global variable that is actually invoked in at least one global variable;

[0067] The code is refactored for at least one objective function branch and at least one objective global variable to obtain the access component corresponding to the third candidate component.

[0068] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0069] The memory stores the instructions that the computer executes;

[0070] The processor executes computer execution instructions stored in memory to implement the access method for industrial equipment as described in the first aspect.

[0071] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the access method for industrial equipment as described in the first aspect.

[0072] The industrial equipment access method, device, electronic equipment, and storage medium provided in this application utilize multiple independently functional minimum reusable basic components contained in a cloud component library. These components can be combined with the first device information of different devices to be accessed and the second device information of the management device to generate suitable access components. Compared to connecting devices to the management device based on a preset access program, this method is compatible with different types of devices to be accessed and the management device. Furthermore, by generating access programs through component reuse, there is no need to develop complete programs separately for each type of device to be accessed, reducing development costs and time, and enabling rapid response to diverse access needs of devices to be accessed, thus improving the flexibility of industrial equipment access. Attached Figure Description

[0073] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0074] Figure 1 A schematic diagram illustrating an application scenario provided in an embodiment of this application;

[0075] Figure 2 A flowchart illustrating an industrial equipment access method provided in an embodiment of this application;

[0076] Figure 3 This application provides a schematic diagram of a process for determining at least one access component.

[0077] Figure 4 A schematic diagram of a process for determining at least one first candidate component is provided for an embodiment of this application;

[0078] Figure 5 This application provides another schematic diagram of a process for determining at least one access component.

[0079] Figure 6 This is a schematic diagram of the structure of an industrial equipment access device provided in an embodiment of this application;

[0080] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0081] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0082] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0083] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with the relevant laws, regulations, and standards of the relevant regions, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0084] Against the backdrop of the deep integration of the Industrial Internet and intelligent manufacturing, the real-time acquisition, transmission, and analysis of industrial equipment data have become core supports for achieving intelligent and refined management of production processes. With the widespread application of edge computing architecture in industrial control, industrial equipment is often heterogeneous (including intelligent terminals with communication capabilities and a large number of "dumb" devices lacking native data interfaces). Therefore, to support the needs of upper-layer business systems for advanced functions such as industrial equipment status awareness, fault early warning, and energy efficiency optimization, device access technology can be used to connect industrial equipment to management devices.

[0085] In related technologies, device access processing can be performed through preset access programs. Specifically, the server stores multiple access programs adapted to different device models and protocol types. The server receives device access requests sent by the management device, which request the target device to be connected to the management device. Then, based on information such as the target device's model and protocol type, the server determines the corresponding access program for the target device and connects the target device to the management device based on that access program.

[0086] However, the above method can only connect target devices of the pre-defined access program's corresponding device model and protocol type to the management device, resulting in poor flexibility in device access. Furthermore, with the increasing variety of industrial equipment types, the server needs to store a large number of pre-defined access programs corresponding to different industrial equipment types. However, some of these pre-defined access programs may not be used, leading to a waste of server memory resources. In addition, the memory capacity of management devices is typically only tens to hundreds of megabytes, and the processor frequency of management devices is limited. Even if only a general-purpose access program is loaded, its static code size and runtime memory usage require a significant amount of memory resources from the management device, potentially squeezing the resource space for real-time task scheduling and causing problems such as delays in data acquisition terminals or control commands.

[0087] Based on this, this application provides a device access method. A cloud-based component library contains multiple minimum reusable basic components with independent functions. These components can be combined with the first device information of different devices to be accessed and the second device information of the management device to generate suitable access components. Compared to connecting devices to the management device based on a pre-set access program, this method is compatible with different types of devices to be accessed and the management device. Furthermore, by generating access programs through component reuse, there is no need to develop complete programs separately for each type of device to be accessed, which reduces development costs and time, and enables rapid response to diverse access needs of devices to be accessed, thus improving the access flexibility of industrial equipment.

[0088] To facilitate understanding, the following will be combined with... Figure 1 The application scenarios applicable to the embodiments of this application will be briefly described below.

[0089] Figure 1 This is a schematic diagram illustrating an application scenario provided by an embodiment of this application. Please refer to [link / reference]. Figure 1 It includes a server 11, a management device 12, and a device to be connected 13. The server 11 can be, for example, a cloud server with cloud computing capabilities, the management device 12 can be, for example, an edge controller, an industrial gateway, or other devices, and the device to be connected 13 can be, for example, an industrial sensor or other devices.

[0090] In some embodiments, the management device 12 can communicate with the server 11. For example, the management device 12 can send a device access request to the server 11, requesting the server 11 to connect the device 13 to the management device 12. Upon receiving the device access request, the server 11 determines the access procedure for the device 13 and connects the device 13 to the management device 12 based on that access procedure.

[0091] It should be noted that the execution subject in each embodiment of this application can be a chip, chip module, processor, microprocessor, etc., or it can be a device integrating the above-mentioned chips, chip modules, processors, or microprocessors, such as a server. The specific execution subject in each embodiment of this application is not limited, and it can be selected and set according to actual needs. In the following embodiments, a server integrating the above-mentioned chips, chip modules, processors, or microprocessors is used as an example for description, which does not constitute a limitation on the actual execution subject.

[0092] It should be noted that, Figure 1 This is merely an example to illustrate one application scenario, and is not intended to limit the application scenario.

[0093] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0094] Figure 2 This is a flowchart illustrating a method for connecting industrial equipment according to an embodiment of this application. Figure 2 As shown, the process may include the following steps:

[0095] S21. Receive device access request. The device access request is used to request the device to be accessed to be connected to the management device. The device access request includes the first device information of the device to be accessed and the second device information of the management device. The management device is the intermediary carrier for the interaction between the device to be accessed and the server.

[0096] A device access request refers to an information instruction sent by a management device to a server to request the access of a device to the management system. In some embodiments, the device access request includes information required for the device to be accessed. For example, a device access request might be for accessing 10 CNC machine tools, requiring real-time temperature data collection.

[0097] Devices to be connected refer to devices in the device management system that are to be added to the management device. These devices can be edge devices with data interaction or function execution capabilities. It should be noted that devices to be connected cannot collaborate with the management device and server unless they are connected to the management device.

[0098] Management devices are intermediate devices in the industrial internet environment that undertake core functions such as device access, access control, and data forwarding. They serve as a bridge and hub for interaction between the devices to be connected and the server.

[0099] The first device information indicates the number, type, attributes, or configuration of the devices to be connected. The second device information indicates the device identifier or configuration of the managed device.

[0100] In some embodiments, when it is necessary to connect a device to the management device, the staff can determine the first device information and the second device information, and send a device access request to the server through the management device based on the first device information and the second device information.

[0101] S22. Based on the first device information and the second device information, determine at least one access component adapted to the device to be accessed in the cloud component library; wherein, the cloud component library includes multiple basic components, each of which is the smallest reusable software unit with independent functions.

[0102] A cloud-based component library is a centralized resource repository deployed on a server for storing and managing various software components. It features remote access, on-demand invocation, and unified maintenance. The cloud-based component library gathers standardized software units designed for scenarios such as device access, data interaction, and functional expansion. Through mechanisms such as categorization indexing and version management, it provides reusable component resources to support the access needs of different devices. In some embodiments, the cloud-based component library includes multiple basic components.

[0103] Among them, basic components are the smallest reusable software units with independent functions in the cloud component library. Each basic component focuses on a single and clearly defined core function. For example, a basic component can perform any of the following functions: data parsing, protocol conversion, authorization verification, and communication adaptation. It should be noted that basic components can independently complete specific functions without relying on other components, forming the basis for complex access logic. At the same time, basic components can be combined with other basic components to form composite functional units that meet the access requirements of different devices in specific scenarios.

[0104] Access components are software components that the server selects, combines, or adapts from multiple basic components in the cloud component library based on the first device information and the second device information. They are specifically designed to support the effective connection and interaction between the device to be accessed and the management device and server.

[0105] In some embodiments, the server can determine the target tag for connecting the device to the management device based on the first device information and the second device information. Then, the server uses a cosine similarity algorithm to determine at least one access tag with a high matching degree with the target tag from among the access tags corresponding to multiple basic components, and determines the basic component corresponding to each of the at least one access tag as at least one access component.

[0106] S23. Process at least one access component to obtain the access program for the device to be accessed.

[0107] An access program is a complete software program customized for the device to be accessed, which can run directly on the access device or the management device. It is the core execution carrier for realizing stable connection and normal interaction between the device to be accessed and the management device and server. In some embodiments, the access program integrates all the functional logic required for device access, including communication protocol adaptation, identity authentication, data encoding and decoding, command sending and receiving, and exception handling. It is executable and independent, and can directly drive the device to be accessed to complete the access process, maintain the communication link, and complete data interaction according to the specifications of the management device and server.

[0108] In some embodiments, the access procedure can be packaged as a standard Over-the-Air (OTA) update package. This OTA update package can be in a self-describing format; for example, the OTA update package may include a metadata header (containing version number, target architecture, and checksum), program segments (containing .text, .rodata, and .data files), and a digital signature (generated based on the P256 Elliptic Curve Digital Signature Algorithm with P-256curve (ECDSA-P256)).

[0109] In some embodiments, the server may invoke a cross-compiler that matches the instruction set of the management device, and perform a compilation operation on at least one access component using preset compilation parameters in the cross-compiler. These compilation parameters may include, for example, optimization level, target binary format, linker script, and runtime library configuration parameters. In some embodiments, during the compilation of at least one access component, the server strictly adheres to a deterministic construction principle, meaning that identical inputs will inevitably produce bit-inconsistent outputs, to ensure the consistency of OTA deployment and verify feasibility.

[0110] S24. Connect the device to be connected to the management device according to the access procedure.

[0111] In some embodiments, the server can achieve batch, parallel, and consistent program deployment through OTA technology. Specifically, the server can establish encrypted communication links with each device to be connected via HyperText Transfer Protocol Secure (HTTPS) or Message Queuing Telemetry Transport over Transport Layer Security (MQTToverTLS), and use two-way certificate authentication to ensure the legitimacy of the server and each device. Then, the server distributes the access program to each device based on its unique identifier (the device's Media Access Control (MAC) address or device serial number). Upon receiving the access program, each device labels it with its digital signature and version number to determine its security. If the access program is deemed secure, the device performs an atomic installation operation, writing the access program to the spare storage area and loading the access program execution context upon the next startup, thereby connecting the device to the management device.

[0112] In some embodiments, after connecting a device to be connected to the management device, the server receives device access logs sent by the device to be connected. The device access logs include a successful connection flag, resource usage information, and a self-test status. The server compiles the device access logs of all devices to be connected and verifies the version consistency of the access program for each device based on these logs.

[0113] In some embodiments, if a device fails to connect, the server can initiate a retry mechanism based on a retry policy until all devices successfully connect to the management device, or until a preset number of retries is reached. The retry policy can be, for example, an exponential backoff delay policy or a failed node isolation policy.

[0114] exist Figure 2 In the illustrated embodiment, the cloud-based component library contains multiple minimal reusable basic components with independent functions. These components can be combined to create suitable access components based on the first device information of different devices to be accessed and the second device information of the management device. Compared to connecting devices to the management device based on a preset access program, this approach is compatible with different types of devices to be accessed and the management device. Furthermore, generating access programs through component reuse eliminates the need to develop complete programs separately for each type of device to be accessed, reducing development costs and time, and enabling rapid response to diverse access needs of devices to be accessed, thus improving the flexibility of industrial equipment access.

[0115] exist Figure 2 Based on the illustrated embodiment, the following, in conjunction with Figure 3 The process of determining at least one access component adapted to the device to be accessed in the cloud component library based on the first device information and the second device information in this application will be further explained.

[0116] Figure 3 This is a schematic diagram illustrating a process for determining at least one access component, provided as an embodiment of this application. Figure 3 As shown, the process may include the following steps:

[0117] S31. Based on the mapping relationship between protocol type and composite component, and the communication protocol type, determine the target composite component that is compatible with the communication protocol type among multiple composite components.

[0118] The first piece of equipment information includes the communication protocol type of the device to be connected. This communication protocol type refers to the communication rules and data format standards followed when the device to be connected interacts with the management equipment and server, and is the core technical basis for enabling interconnection between devices. Communication protocol types can include various industrial communication protocols such as Modbus, Open Platform Communications Unified Architecture (OPC UA), Long Range (LoRa), Recommended Standard 485 (RS485), and Narrow Band Internet of Things (NB-IoT).

[0119] The cloud-based component library includes multiple composite components; each composite component is a functional combination of at least two basic components integrated based on preset dependencies.

[0120] A composite component is a standardized functional assembly formed by integrating at least two basic components with independent functions according to a preset function call order, data interaction rules, and dependency relationships, specifically for industrial equipment access scenarios or communication protocol types. The essence of a composite component is the pre-encapsulation and modular integration of at least two basic components.

[0121] In some embodiments, the server stores a mapping relationship between protocol types and composite components, wherein the mapping relationship between protocol types and composite components refers to a set of association rules established in advance in the server, which correspond one-to-one or one-to-many between protocol types and composite components.

[0122] For example, suppose the mapping relationship between protocol types and composite components is shown in Table 1:

[0123] Table 1

[0124]

[0125] Assuming the communication protocol type of the device to be accessed is OPC UA, the server determines the target composite component as composite component 2.

[0126] S32. Based on the target composite component and the cloud component library, determine at least one first candidate component among multiple basic components.

[0127] The first candidate component refers to the basic component in the cloud component library that has a dependency or association relationship with the target composite component.

[0128] In some embodiments, since the cloud component library includes multiple basic components and the target composite build is a functional combination of at least two basic components integrated based on a preset dependency relationship, at least one first candidate component in the cloud component library that has a dependency or association relationship with the target composite build library can be determined.

[0129] S33. Determine at least one access component from at least one first candidate component based on the first device information and the second device information.

[0130] In some embodiments, the server may, based on the functional requirements of the device to be accessed as reflected in the first device information, first select a second candidate component from the first candidate components that matches the function of the device to be accessed, and then, based on the management device hardware resources and operational constraints contained in the second device information, perform resource evaluation and screening on the second candidate component to obtain a third candidate component. Finally, perform deep pruning processing such as redundant component elimination, symbol-level code stripping, and link-time optimization on the third candidate component to obtain an access component with complete resource usage and functions that can be directly used to generate an access program.

[0131] exist Figure 3 In the illustrated embodiment, the server first quickly matches target combined components based on communication protocol type and preset mapping relationship, then decomposes the combined components to obtain the first candidate component in the form of basic components, and finally filters the access components by combining the functional requirements of the device to be accessed with the hardware resources and operational constraints of the management device. This enables hierarchical and precise filtering of components, which not only improves the efficiency of protocol adaptation by using combined components, but also ensures the flexibility and lightweight nature of access components through basic components, avoiding redundant functions and resource waste. This ensures that the finally determined access components can adapt to the communication protocol and functional requirements of the device to be accessed, and also fit the hardware resources and operational limitations of the management device, thereby improving the adaptability, stability and execution efficiency of device access.

[0132] Based on the above embodiments, the following, in conjunction with Figure 4 The method of determining at least one first candidate component among multiple basic components based on the target combined component and the cloud component library in this application will be further explained.

[0133] Figure 4 This is a schematic diagram illustrating a process for determining at least one first candidate component, provided as an embodiment of this application. Figure 4 As shown, the process may include the following steps:

[0134] S41. Determine at least one target component in the target combination components.

[0135] A target component refers to a basic component or functional subunit that is extracted from a target composite component and constitutes the core function of that composite component. In other words, a target component is a specific component of the target composite component at the level of basic components.

[0136] In some embodiments, since the target composite component is composed of at least two basic components, the at least two basic components that make up the target composite component can be identified as the target component.

[0137] For example, suppose that the target component X is composed of basic component A, basic component B and basic component C, that is, determine that at least one target component includes basic component A, basic component B and basic component C.

[0138] S42. For each target component in at least one target component, determine at least one associated component of the target component based on the component dependency topology; the at least one associated component is a component among multiple basic components that has a direct or indirect dependency relationship with the target component.

[0139] The cloud-based component library includes a component dependency topology, which indicates the dependencies between multiple basic components. The component dependency topology describes the topological structure of the calling and called relationships between various basic steel components. In some embodiments, the component dependency topology can identify basic components with nodes and represent dependencies with edges, recording which basic components each basic component depends on for proper operation.

[0140] In some embodiments, for each target component, determining at least one associated component of the target component based on the component dependency topology can be performed as follows: performing a first operation, the first operation including: determining a (i+1)th level associated component that has a direct dependency relationship with the i-th level associated component based on the component dependency topology; wherein i is an integer greater than or equal to 0; when i=0, the 0-th level associated component is the target component; until i is greater than or equal to a preset threshold, and / or there is no (i+1)th level associated component in the component dependency topology that has a direct dependency relationship with the i-th level associated component, at least one associated component is obtained; wherein the at least one associated component includes the (i+1)th level associated component.

[0141] Here, the i-th level associated component is obtained by dividing the dependency hierarchy according to the dependency level during the process of searching for dependent components level by level according to the component dependency topology. 'i' represents the dependency level number of the current component relative to the target component, used to distinguish between different levels of direct and indirect dependencies, making the dependency traversal process more standardized and orderly. The (i+1)-th level associated component is obtained by dividing the dependency hierarchy according to the dependency level during the process of searching for dependent components level by level according to the component dependency topology.

[0142] For example, suppose the target component is a base component A, and the related components in the component dependency topology that have a direct dependency relationship with base component A include base component B and base component C. Therefore, the server determines that the level 0 related component is base component A, and determines that the level 1 related components that have a direct dependency relationship with the level 0 related component include base component B and base component C.

[0143] For basic component B, the related components in the component dependency topology that have a direct dependency relationship with basic component B include basic component D. For basic component C, there are no other basic components in the component dependency topology that have a dependency relationship with basic component C. Therefore, the server determines that the second-level related component that has a direct dependency relationship with the first-level related components is basic component D.

[0144] For basic component D, there are no other basic components in the dependency topology that have a dependency relationship with basic component D. Therefore, the server determines that at least one associated component of basic component A includes: basic component B, basic component C and basic component D.

[0145] S43. Perform deduplication on at least one associated component of each of the at least one target component to obtain at least one first candidate component.

[0146] In some embodiments, at least one target component may also have dependencies on each other, and at least one associated component of each target component is a base component that depends on that target component. Therefore, at least one target component and at least one associated component of each target component may have duplicate components. In addition, different target components may depend on the same base component, so at least one associated component of each target component may also have duplicate components.

[0147] Therefore, it is necessary to perform deduplication on the related components of these different components, identify the basic components that appear repeatedly, and retain the unique basic components to obtain at least one first candidate component.

[0148] For example, suppose at least one target component includes base component A, base component M, and base component N. At least one associated component of base component A includes base component B, base component C, and base component D. At least one associated component of base component M includes base component O, base component B, and base component Q. At least one associated component of base component N includes base component C, base component O, and base component D.

[0149] Then, at least one associated component of each of the at least one target component is deduplicated to obtain at least one first candidate component including basic component B, basic component C, basic component D, basic component O and basic component Q.

[0150] exist Figure 4 In the illustrated embodiment, the server determines the target component from the target composite components, then identifies related components with direct or indirect dependencies on the target component by traversing the component dependency topology level by level, and performs deduplication on the related components to obtain the first candidate component. This allows for accurate and complete acquisition of all the basic components required to implement the device access function, reducing the omission of dependent components. Simultaneously, the server reduces redundant components and simplifies the component set through hierarchical traversal and deduplication, improving the efficiency of subsequent component selection and access program generation, ensuring complete access functionality and reasonable resource consumption.

[0151] Based on the above embodiments, the following, in conjunction with Figure 5 The method for determining at least one access component from at least one first candidate component based on first device information and second device information in this application will be further described.

[0152] Figure 5 This is a schematic diagram illustrating another process for determining at least one access component, provided as an embodiment of this application. Figure 5 As shown, the process may include the following steps:

[0153] S51. Based on functional requirements, determine at least one second candidate component from at least one first candidate component; wherein the component function of each second candidate component matches the functional requirements.

[0154] The first device information includes the functional requirements of the device to be connected. Functional requirements refer to the specific business functions or data processing requirements that the device to be connected needs to perform. For example, functional requirements could include data acquisition, protocol parsing, data reporting, anomaly detection, and control command execution.

[0155] The second candidate component refers to a component selected from at least one first candidate component according to functional requirements, whose function matches the business requirements of the equipment.

[0156] In some embodiments, the server includes a mapping relationship between functional requirements and basic components. The server can determine at least one matching component that matches the functional requirements based on the mapping relationship between functional requirements and basic components and the functional requirements of the device to be connected. Then, in at least one first candidate component, the basic component that is the same as at least one matching component is determined as the second candidate component.

[0157] For example, suppose the mapping relationship between functional requirements and basic components is as shown in Table 2:

[0158] Table 2

[0159]

[0160] Assuming the functional requirement of the device to be connected is data acquisition, then at least one matching component is determined to include basic component C and basic component B.

[0161] If at least one first candidate component includes basic component B, basic component C, basic component D, basic component O, and basic component Q, then at least one second candidate component can be determined to include basic component B and basic component C.

[0162] S52. Determine at least one third candidate component from at least one second candidate component based on the second device information.

[0163] The second device information includes the hardware resource information and operational constraints of the management device. The hardware resource information is a set of parameters describing the management device's own hardware capabilities. This information may include the management device's central processing unit architecture, memory capacity, storage space, computing power, interface type, etc., reflecting the upper limit of the hardware that the management device can support and run access components. It serves as the basis for determining whether access components can be properly deployed and operated on the management device.

[0164] Operational constraints are the conditions in the second device information that limit the performance and stability requirements that access components must meet when running on the management device. Operational constraints may include real-time requirements, data acquisition latency thresholds, processor utilization limits, memory usage limits, power consumption limits, etc., to ensure that the operation of access components does not exceed the management device's capacity, and to ensure that the device access process is stable, reliable, and efficient.

[0165] In some embodiments, the server determines at least one third candidate component in the following manner: constructing a resource evaluation model for the device to be accessed based on hardware resource information and operating constraints; processing each of the at least one second candidate component based on the resource evaluation model to determine the resource occupancy and runtime of the second candidate component; determining the resource threshold corresponding to the hardware resource information and the runtime threshold corresponding to the operating constraints; and determining the second candidate component as the third candidate component if the resource occupancy of the second candidate component is less than or equal to the resource threshold and the runtime is less than or equal to the runtime threshold.

[0166] The resource assessment model is an evaluation rule or calculation model constructed based on the hardware resource information and operational constraints of the managed equipment. It is used to quantitatively analyze and determine indicators such as resource consumption and operational efficiency of the second candidate component. Resource occupancy is an indicator obtained through quantitative analysis of the second candidate component using the resource assessment model, used to characterize the degree to which the component consumes the hardware resources of the managed equipment during operation. Runtime is an indicator obtained through performance analysis of the second candidate component using the resource assessment model, used to characterize the time required for the component to complete a specified function, reflecting the component's execution efficiency and real-time performance.

[0167] The resource threshold is an upper limit for resource usage determined by the hardware resource information of the management device, used to limit the maximum amount of hardware resources that the access component is allowed to occupy. In some embodiments, the resource usage of the component must not exceed this threshold to ensure normal and stable operation on the management device. The duration threshold is the maximum allowed runtime determined by the operating constraints of the management device, used to limit the upper limit of the time it takes for the access component to complete its function. In some embodiments, the runtime of the component must not exceed this threshold to meet the system's real-time performance and operational efficiency requirements.

[0168] In some embodiments, the server can use hardware resource information such as the processor architecture, memory capacity, and storage space of the managed device as resource constraint inputs to the model, and runtime constraints such as real-time requirements, runtime latency limits, and resource utilization limits as performance constraint inputs to the model. These two types of constraints are quantified, normalized, and integrated to form evaluation rules and decision logic. The resource evaluation model includes evaluation rules and decision logic; that is, the resource evaluation model can quantify and calculate the resource consumption and execution efficiency of each second candidate component and determine its compliance, thereby outputting standardized evaluation results for component selection.

[0169] For example, assume that at least one second candidate component includes second candidate component a, second candidate component b, and second candidate component c. Based on a resource assessment model, second candidate component a is processed, and its resource consumption is determined to be 40% with a runtime of 1ms. Based on the resource assessment model, second candidate component b is processed, and its resource consumption is determined to be 10% with a runtime of 0.2ms. Based on the resource assessment model, second candidate component c is processed, and its resource consumption is determined to be 30% with a runtime of 0.4ms.

[0170] If the server determines that at least one third candidate component is the second candidate component b (the resource occupancy is less than the resource threshold of 25% and the runtime is less than the runtime threshold of 0.5ms) based on the resource threshold corresponding to the hardware resource information and the runtime threshold corresponding to the running constraints.

[0171] S53. For each of the at least one third candidate components, the third candidate components are processed to obtain the access component corresponding to the third candidate component; wherein, the at least one access component includes the access component corresponding to each of the at least one third candidate component.

[0172] In some embodiments, the server processes the third candidate component to obtain the access component corresponding to the third candidate component in the following ways: performing code stripping on the third candidate component to determine at least one function branch and at least one global variable of the third candidate component; determining at least one target function branch that is actually called in the at least one function branch; determining at least one target global variable that is actually called in the at least one global variable; and performing code refactoring on the at least one target function branch and the at least one target global variable to obtain the access component corresponding to the third candidate component.

[0173] A function branch refers to all independent functions, functional subroutines, conditional branches, and logical execution paths contained in the code of the third candidate component; it is the code execution unit that constitutes the component's functionality. The target function branch refers to the function branch selected from all function branches that is actually called and executed during the device access process; it is the core execution unit necessary for implementing the access function.

[0174] Global variables are variables defined in the third candidate component program that can be accessed by multiple functions or code modules and are used to store data, configuration parameters, and status information. Target global variables are valid global variables selected from all global variables that are actually read, assigned values, or called during program execution; they are indispensable data storage units for ensuring the normal operation of the component.

[0175] In some embodiments, the server can perform fine-grained parsing and decomposition of the program code of the third candidate component, extracting at least one function branch and at least one global variable from the component code through static analysis or compile-time scanning. Then, the server determines at least one target function branch that is actually called within the at least one function branch, and at least one target global variable that is actually called within the at least one global variable. Finally, based on the filtered target function branches and target global variables, the server reorganizes, optimizes, and integrates the code structure of the third candidate component, removing redundant code, simplifying execution logic, and optimizing data interaction methods, generating optimized code that is structurally streamlined, compact in size, and adaptable to managed device resources without changing the core functionality.

[0176] exist Figure 5In the illustrated embodiment, the server first performs functional matching and screening on the first candidate component based on the functional requirements of the device to be connected to obtain the second candidate component. Then, based on the hardware resource information and operational constraints of the management device, a resource evaluation model is constructed to verify the resources and runtime of the second candidate component to determine the third candidate component. Finally, code stripping, target function branch and target global variable screening, and code refactoring are sequentially performed on the third candidate component to obtain the access component. This achieves multi-level refined screening and optimization from functional adaptation and resource adaptation to code lightweighting. It not only ensures that the access component accurately meets the functional requirements of the device to be connected, but also ensures that it complies with the hardware limitations and operational performance requirements of the management device. At the same time, redundant functions and redundant code are eliminated, reducing the resource consumption and running time of the access component, and improving the stability, reliability, and execution efficiency of device access.

[0177] In some embodiments, after the device to be connected is connected to the management device, the server can monitor the update status of the component library. If the component library needs to be updated, the server can download the latest component library from the cloud, compare it with the local component library version number, determine the build that needs to be updated, and perform the component update operation.

[0178] Figure 6 This is a schematic diagram of the structure of an industrial equipment access device provided in an embodiment of this application. Please refer to... Figure 6 The industrial equipment access device 60 provided in this application embodiment includes: a receiving module 61, a determining module 62, a processing module 63, and an access module 64, wherein:

[0179] The receiving module 61 is used to receive a device access request, which requests the device to be accessed to be connected to the management device. The device access request includes first device information of the device to be accessed and second device information of the management device. The management device is an intermediary carrier for the device to be accessed to interact with the server.

[0180] The determining module 62 is used to determine at least one access component adapted to the device to be accessed in the cloud component library based on the first device information and the second device information; wherein, the cloud component library includes multiple basic components, each of which is the smallest reusable software unit with independent functions;

[0181] Processing module 63 is used to process at least one access component to obtain the access program for the device to be accessed;

[0182] Access module 64 is used to connect the device to be accessed to the management device according to the access program.

[0183] In one possible implementation, the first device information includes the communication protocol type of the device to be accessed, and the cloud component library includes multiple combined components; wherein each combined component is a functional combination of at least two basic components integrated based on a preset dependency relationship; the determining module 62 is specifically used for:

[0184] Based on the mapping relationship between protocol type and composite component, and the communication protocol type, determine the target composite component that is compatible with the communication protocol type from among multiple composite components;

[0185] Based on the target composite components and the cloud component library, at least one first candidate component is identified among multiple basic components;

[0186] At least one access component is determined from at least one first candidate component based on the first device information and the second device information.

[0187] In one possible implementation, the cloud component library includes a component dependency topology, which indicates the dependencies between multiple basic components; the determining module 62 is specifically used for:

[0188] Identify at least one target component in the target assembly;

[0189] For each target component in at least one target component, at least one associated component of the target component is determined based on the component dependency topology; the at least one associated component is a component among multiple basic components that has a direct or indirect dependency relationship with the target component.

[0190] At least one associated component of each of the at least one target component is deduplicated to obtain at least one first candidate component.

[0191] In one possible implementation, the determining module 62 is specifically used for:

[0192] Perform a first operation, which includes: determining the (i+1)th level associated component that has a direct dependency relationship with the i-th level associated component based on the component dependency topology; where i is an integer greater than or equal to 0; when i=0, the 0th level associated component is the target component;

[0193] Until i is greater than or equal to a preset threshold, and / or there is no i+1 level associated component in the component dependency topology that has a direct dependency relationship with the i-th level associated component, at least one associated component is obtained; wherein, at least one associated component includes the i+1 level associated component.

[0194] In one possible implementation, the first device information includes the functional requirements of the device to be accessed; the determining module 62 is specifically used for:

[0195] Based on functional requirements, at least one second candidate component is determined from at least one first candidate component; wherein the component function of each second candidate component matches the functional requirements.

[0196] Based on the second device information, at least one third candidate component is determined from at least one second candidate component;

[0197] For each of the at least one third candidate components, the third candidate components are processed to obtain the access component corresponding to the third candidate component;

[0198] Among them, at least one access component includes at least one access component corresponding to each of the third candidate components.

[0199] In one possible implementation, the second device information includes hardware resource information and operating constraints of the management device; the determining module 62 is specifically used for:

[0200] Construct a resource assessment model for the devices to be accessed based on hardware resource information and operational constraints;

[0201] For each of the at least one second candidate components, the second candidate components are processed based on a resource assessment model to determine the resource consumption and runtime of the second candidate components;

[0202] Determine the resource thresholds corresponding to hardware resource information and the duration thresholds corresponding to operational constraints;

[0203] For each of the at least one second candidate component, if the resource consumption of the second candidate component is less than or equal to the resource threshold and the runtime is less than or equal to the runtime threshold, the second candidate component is determined as the third candidate component.

[0204] In one possible implementation, the determining module 62 is specifically used for:

[0205] The code of the third candidate component is stripped to identify at least one function branch and at least one global variable of the third candidate component;

[0206] In at least one function branch, identify at least one target function branch that is actually called;

[0207] Determine at least one target global variable that is actually invoked in at least one global variable;

[0208] The code is refactored for at least one objective function branch and at least one objective global variable to obtain the access component corresponding to the third candidate component.

[0209] The industrial equipment access device 60 provided in this application embodiment can execute the industrial equipment access method shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0210] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device 70 may include: a processor 71, and a memory 72 communicatively connected to the processor;

[0211] Memory 72 stores instructions executed by the computer;

[0212] The processor 71 executes computer execution instructions stored in the memory 72 to implement the industrial equipment access method shown in the above method embodiment.

[0213] Optionally, the aforementioned processor can be a central processing unit (CPU), a graphics processing unit (GPU), other general-purpose processors, a digital signal processor (DSP), or an application-specific integrated circuit (ASIC), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0214] The electronic device 70 provided in this application embodiment can execute the industrial equipment access method shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0215] This application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the industrial equipment access method shown in the above method embodiments.

[0216] This application provides a computer program product, including a computer program that, when executed by a processor, implements the industrial equipment access method shown in the above-described method embodiments.

[0217] This application provides a chip that stores a computer program. When the computer program is executed by the chip, it implements the industrial equipment access method shown in the above method embodiment.

[0218] This application provides a chip module on which a computer program is stored. When the computer program is executed by the chip module, it implements the industrial equipment access method shown in the above method embodiment.

[0219] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0220] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0221] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0222] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0223] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0224] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0225] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0226] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0227] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for connecting industrial equipment, characterized in that, Applied to a server, the method includes: The system receives a device access request, which requests the device to be accessed to be connected to the management device. The device access request includes first device information of the device to be accessed and second device information of the management device. The management device serves as an intermediary for the interaction between the device to be accessed and the server. The first device information includes the communication protocol type of the device to be accessed. Based on the mapping relationship between protocol types and composite components, and the communication protocol type, a target composite component adapted to the communication protocol type is determined from multiple composite components in the cloud component library; wherein, each composite component is a functional combination of at least two basic components integrated based on a preset dependency relationship; the cloud component library also includes multiple basic components and component dependency topology, each basic component is the smallest reusable software unit with independent functions, and the component dependency topology is used to indicate the dependency relationship between the multiple basic components; Based on the target composite component and the cloud component library, at least one first candidate component is determined from the plurality of basic components that has a direct or indirect dependency relationship with the target component in the target composite component; The at least one access component is determined from the at least one first candidate component based on the first device information and the second device information; The at least one access component is processed to obtain the access program for the device to be accessed. The device to be connected is connected to the management device according to the access procedure.

2. The method according to claim 1, characterized in that, The step of determining at least one first candidate component among the plurality of basic components that has a direct or indirect dependency relationship with the target component in the target composite component, based on the target composite component and the cloud component library, includes: Identify at least one target component in the target assembly; For each target component in the at least one target component, at least one associated component of the target component is determined according to the component dependency topology; the at least one associated component is a component among the plurality of basic components that has a direct or indirect dependency relationship with the target component; The at least one associated component of each of the at least one target component is deduplicated to obtain the at least one first candidate component.

3. The method according to claim 2, characterized in that, The step of determining at least one associated component of the target component based on the component dependency topology includes: Perform a first operation, the first operation including: determining a (i+1)th level associated component that has a direct dependency relationship with the i-th level associated component based on the component dependency topology; wherein, i is an integer greater than or equal to 0; when i=0, the 0th level associated component is the target component; Until i is greater than or equal to a preset threshold, and / or there is no i+1 level associated component in the component dependency topology that has a direct dependency relationship with the i-th level associated component, the at least one associated component is obtained; wherein the at least one associated component includes the i+1 level associated component.

4. The method according to any one of claims 1-3, characterized in that, The first device information includes the functional requirements of the device to be accessed; determining the at least one access component from the at least one first candidate component based on the first device information and the second device information includes: Based on the functional requirements, at least one second candidate component is determined from the at least one first candidate component; wherein the component function of each second candidate component matches the functional requirements; Based on the second device information, at least one third candidate component is determined from the at least one second candidate component; For each of the at least one third candidate component, the third candidate component is processed to obtain the access component corresponding to the third candidate component; The at least one access component includes the access component corresponding to each of the at least one third candidate component.

5. The method according to claim 4, characterized in that, The second device information includes the hardware resource information and operating constraints of the management device; determining at least one third candidate component from the at least one second candidate component based on the second device information includes: A resource evaluation model for the device to be connected is constructed based on the hardware resource information and the operational constraints. For each of the at least one second candidate component, the second candidate component is processed based on the resource evaluation model to determine the resource consumption and runtime of the second candidate component; Determine the resource threshold corresponding to the hardware resource information and the duration threshold corresponding to the operating constraints; For each of the at least one second candidate component, if the resource consumption of the second candidate component is less than or equal to the resource threshold and the runtime is less than or equal to the runtime threshold, the second candidate component is determined as the third candidate component.

6. The method according to claim 4, characterized in that, The process of processing the third candidate component to obtain the access component corresponding to the third candidate component includes: The code of the third candidate component is stripped to determine at least one function branch and at least one global variable of the third candidate component; In the at least one function branch, determine at least one target function branch that is actually called; Determine at least one target global variable that is actually invoked from among the at least one global variable; The code is refactored on the at least one objective function branch and the at least one objective global variable to obtain the access component corresponding to the third candidate component.

7. A connection device for industrial equipment, characterized in that, include: The receiving module is used to receive device access requests, which are used to request that the device to be accessed be connected to the management device; The device access request includes first device information and second device information of the management device; the management device serves as an intermediary for the interaction between the device to be accessed and the server. A determining module is configured to: firstly, include the communication protocol type of the device to be accessed in the first device information; determine a target combined component adapted to the communication protocol type from multiple combined components in a cloud component library based on the mapping relationship between the protocol type and the combined components, and the communication protocol type; wherein each combined component is a functional combination of at least two basic components integrated based on a preset dependency relationship; the cloud component library also includes multiple basic components and component dependency topologies, each basic component is a minimum reusable software unit with independent functions, and the component dependency topology is used to indicate the dependency relationship between the multiple basic components; determine at least one first candidate component from the multiple basic components that has a direct or indirect dependency relationship with the target component in the target combined component based on the target combined component and the cloud component library; determine at least one access component from the at least one first candidate component based on the first device information and the second device information; and process the at least one access component to obtain the access program for the device to be accessed. The access module is used to connect the device to be accessed to the management device according to the access program.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the industrial equipment access method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the access method for industrial equipment as described in any one of claims 1 to 6.

Images