Access method, device and equipment of distributed device and storage medium
By using cloud-based automated device network information transmission, and employing a tree structure and object model information, the high labor costs and low efficiency of traditional device access methods are solved, achieving highly efficient automation and dynamic expansion of device access.
Patent Information
- Application Number
- CN202411989022.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-31
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2044-12-31
AI Technical Summary
Traditional device access methods require significant labor costs and impact access efficiency, especially when the number of devices is large and widely distributed, as they cannot dynamically expand the access information of the devices.
The system receives user access requests via the cloud, obtains device network information from end-side devices, and sends it to the end-side devices to enable them to automatically connect to sub-devices. Access control is performed using a tree structure topology and object model information.
It reduced labor costs, improved device access efficiency, and enabled dynamic expansion of device access information.
Smart Images

Figure CN119906598B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet of Things (IoT) technology, and in particular to a method, apparatus, device, and storage medium for accessing distributed devices. Background Technology
[0002] With the rapid development of Internet of Things (IoT) technology, the number of devices connected to the internet has increased dramatically, making IoT connectivity a challenge, especially when the number of devices is large and widely distributed. Traditional device access methods typically involve manually connecting control devices to controlled devices. However, when the number of controlled devices is large, this not only incurs significant manual costs but also affects the efficiency of device access, thus impacting the overall efficiency of IoT configuration.
[0003] Therefore, the existing technology still needs to be improved and enhanced. Summary of the Invention
[0004] The technical problem to be solved by this application is to provide a method, apparatus, device and storage medium for accessing distributed devices, in order to address the shortcomings of the prior art.
[0005] To address the aforementioned technical problems, the first aspect of this application provides a method for accessing a distributed device, wherein the method specifically includes:
[0006] Responding to the access operation of the end-side device, obtain the device network information of the end-side device;
[0007] The device network information is sent to the end device, and the end device is controlled to access its corresponding sub-device based on the device network information. The device network information includes the topology between the end device and its corresponding sub-device, as well as the object model information between the end device and its corresponding sub-device.
[0008] The method for accessing distributed devices, wherein the topology adopts a tree structure, the end device is the root node in the tree structure, and the sub-devices corresponding to the end device are the leaf nodes in the tree structure.
[0009] The method for accessing distributed devices, wherein controlling the end-side device to access its corresponding sub-device based on the device network information specifically includes:
[0010] The control device determines the access relationship between the end-side device and its corresponding sub-device based on the topology between the end-side device and its corresponding sub-device;
[0011] Based on the object model information of the terminal device and its corresponding sub-devices, download the object model files of the terminal device and its corresponding sub-devices;
[0012] Compare the verification values of each object model file with their corresponding verification values in the device network information;
[0013] If the comparison passes, the object model files are dynamically loaded so that each sub-device can be connected to the end-side device according to the access relationship.
[0014] The method for accessing distributed devices, wherein before obtaining the device network information of the terminal device in response to the access operation of the terminal device, the method further includes:
[0015] Receive the product / equipment .so file uploaded by the user, wherein the .so file includes the object model file of the product / equipment;
[0016] Store the SO file and associate the SO file with the product device.
[0017] The method for accessing distributed devices, wherein storing the SO file and associating the SO file with the product device specifically includes:
[0018] The SO file is stored, and the association between the product device and the SO file is stored in a preset association table so that the SO file is associated with the product device. The device information item of the product device in the preset association table is expandable.
[0019] The method for accessing distributed devices, wherein before obtaining the device network information of the terminal device in response to the access operation of the terminal device, the method further includes:
[0020] Receive a binding operation input by the user, wherein the binding operation is used to bind a sub-device to the end-side device;
[0021] Obtain the end-side device and sub-device corresponding to the binding operation, and construct the device network information of the end-side device based on the obtained end-side device and sub-device.
[0022] The method for accessing distributed devices further includes:
[0023] Responding to the user's input of an access adjustment operation for the terminal device, read the target sub-device corresponding to the access adjustment operation;
[0024] Based on the access adjustment operation and the target sub-device, the device network information of the end-side device and its corresponding sub-device is adjusted, and the adjusted device network information is sent to the end-side device so that the end-side device can adjust the access relationship between the end-side device and the target sub-device based on the device network information.
[0025] A second aspect of this application provides an access device for a distributed device, wherein the access device for the distributed device specifically includes:
[0026] The reading module is used to respond to the access operation of the end-side device and obtain the device network information of the end-side device.
[0027] The control module is used to acquire the device network information of the end-side device, send the device network information to the end-side device, and control the end-side device to access its corresponding sub-device based on the device network information.
[0028] A third aspect of this application provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps in the access method for a distributed device as described above.
[0029] A fourth aspect of this application provides a terminal device, which includes: a processor and a memory;
[0030] The memory stores a computer-readable program that can be executed by the processor;
[0031] When the processor executes the computer-readable program, it implements the steps in the distributed device access method as described above.
[0032] Beneficial Effects: Compared with existing technologies, this application provides a method, apparatus, device, and storage medium for accessing distributed devices. The method specifically includes responding to an access operation from an end-side device, obtaining the device network information of the end-side device; obtaining the device network information of the end-side device and sending the device network information to the end-side device; and controlling the end-side device to access its corresponding sub-device based on the device network information. This application receives user-input access requests via the cloud and then sends the device network information of the end-side device and its corresponding sub-device to the end-side device. This allows the end-side device to automatically connect to the sub-device based on the device network information, eliminating the need for manual connection of sub-devices to the end-side device. This not only reduces the manual cost of access but also improves access efficiency. Attached Figure Description
[0033] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0034] Figure 1 A flowchart illustrating the access method for a distributed device provided in this application embodiment.
[0035] Figure 2 A timing diagram of the access method for a distributed device provided in an embodiment of this application.
[0036] Figure 3 This is a schematic diagram illustrating an example of the connection relationship between an end-side device and a sub-device.
[0037] Figure 4 A schematic diagram of the access device for a distributed device provided in an embodiment of this application.
[0038] Figure 5 A schematic block diagram of the terminal device provided in the embodiments of this application. Detailed Implementation
[0039] This application provides a method, apparatus, device, and storage medium for accessing distributed devices. To make the objectives, technical solutions, and effects of this application clearer and more explicit, the following detailed description is provided with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only for explaining this application and are not intended to limit this application.
[0040] Those skilled in the art will understand that, unless explicitly stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this application’s specification means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or wireless coupling. The term “and / or” as used herein includes all or any units and all combinations of one or more associated listed items.
[0041] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.
[0042] It should be understood that the sequence number and size of each step in this embodiment do not imply the order of execution. The execution order of each process is determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.
[0043] Research has revealed that with the rapid development of Internet of Things (IoT) technology, the number of devices connected to the internet has increased dramatically, making IoT connectivity a challenge, especially when devices are numerous and widely distributed. Traditional device access methods typically involve manually connecting control devices to controlled devices. However, when the number of controlled devices is large, this not only incurs significant manual costs but also impacts access efficiency, thus affecting IoT configuration efficiency. Furthermore, once device images are burned into the physical network, it's impossible to dynamically change device access information as needed, hindering the expansion of application functionality.
[0044] To address the aforementioned issues, in this embodiment, in response to an access operation from a terminal device, the device network information of the terminal device is obtained; the device network information is then sent to the terminal device, controlling the terminal device to access its corresponding sub-device based on the device network information. This application receives user-input access requests via the cloud and then sends the device network information of the terminal device and its corresponding sub-device to the terminal device. This allows the terminal device to automatically connect to the sub-device based on the device network information, eliminating the need for manual connection of sub-devices to the terminal device. This not only reduces manual access costs but also improves access efficiency. Furthermore, by sending device network information from the cloud to the terminal device, the terminal device can dynamically change its access information as needed, resolving the issue of limited scalability after flashing.
[0045] The application content will be further explained below with reference to the accompanying drawings and through the description of the embodiments.
[0046] This embodiment provides a method for accessing distributed devices, applied to cloud devices. The end-side device can connect to the cloud device, and the end-side device can send an access operation to the cloud device. The cloud device obtains the device network information of the motion device based on the access operation and sends the device network information to the end-side device. The end-side device accesses its corresponding sub-device based on the device network information, so that the corresponding sub-devices of the end-side device can access the end-side device. In this way, sub-devices can access the end-side device in batches, improving the access efficiency of sub-devices accessing the end-side device.
[0047] like Figure 1 and Figure 2 As shown, the access method for the distributed device specifically includes:
[0048] S10. Respond to the access operation of the end-side device and obtain the device network information of the end-side device.
[0049] Specifically, the end-side device is the device to be connected to the sub-device, where the end-side device acts as a control device, the sub-device acts as a controlled device, and the access operation is used to request the sub-device to connect to the end-side device. For example, such as... Figure 3 As shown, the endpoint device is a conference room with a controller, and the sub-devices are an air conditioner and a sensor. The controller acts as the control device, and the air conditioner and sensor act as controlled devices connected to the control device. The access operation can be triggered by the endpoint device. For example, the endpoint device can automatically trigger the access operation after successfully connecting to the cloud device, or the endpoint device can actively send an access operation to the cloud device after connecting. Furthermore, when the endpoint device triggers the access operation, it is unaware of all its corresponding sub-devices, or unaware of some of its corresponding sub-devices. That is, when the cloud device sends device network information to the endpoint device, at least one target sub-device exists among the sub-devices included in the device network information. This target sub-device is unknown to the endpoint device; that is, the endpoint device does not know the access relationship between the target sub-device and the endpoint device, nor the object model information of the target sub-device.
[0050] The device network information includes end-side devices, their corresponding sub-devices, the topology between the end-side devices and their corresponding sub-devices, the object model information of the end-side devices, and the object model information of their corresponding sub-devices. In other words, the device network information reflects the system information of the IoT system formed by the end-side devices and their corresponding sub-devices. For example, if the end-side devices are a conference room with a controller, and the sub-devices are an air conditioner and a sensor, then the device network information reflects the system information of the IoT system formed by the controller, air conditioner, and sensor.
[0051] Furthermore, the device network information is pre-built before responding to the access operation of the terminal device. It can be generated based on the binding operation input by the user terminal, or it can be pre-built based on the terminal device. Then, each time a binding operation to bind a sub-device to the terminal device is received, the device network information is updated based on that sub-device. Therefore, before obtaining the device network information of the terminal device in response to the access operation of the terminal device, the method further includes:
[0052] Receive user input for binding operations;
[0053] Obtain the end-side device and sub-device corresponding to the binding operation, and construct the device network information of the end-side device based on the obtained end-side device and sub-device.
[0054] Specifically, the binding operation is used to bind sub-devices to the terminal device. This binding operation can obtain some or all of the sub-devices corresponding to the terminal device. That is, the terminal device can achieve this by responding to a single binding operation or by responding to multiple binding operations. When multiple binding operations are used, these operations can be independent of each other; that is, binding operations can be sent to the cloud device at different times or under different circumstances to inform the cloud device that a sub-device needs to be added to the terminal device. Therefore, when a sub-device needs to be added to the terminal device, all the sub-devices corresponding to the terminal device can be obtained and then sent to the cloud device, allowing the cloud device to reconstruct the device network information based on all the sub-devices to update the access sub-devices corresponding to the terminal device. Alternatively, only the sub-devices that need to be added to the terminal device can be sent, and then the existing device network information of the terminal device can be updated based on these sub-devices. Regardless of the method used to update the device network information of the terminal device, new sub-devices can be dynamically added to the terminal device, achieving scalability of the terminal device's functionality.
[0055] Furthermore, the binding operation can directly carry information about the sub-device and its access relationship with the end-side device. Upon receiving the binding operation, the system can directly read the sub-device and its access relationship, obtain the object model information of the sub-device, construct a topology between the end-side device and the sub-device based on the access relationship, and add the object model information of the end-side device and the sub-device to the topology to form device network information. Additionally, the binding operation can carry the location information and control range of the end-side device. Upon receiving the binding operation, the system can read the location information and control range of the end-side device, and then determine the corresponding sub-device based on the location information and control range. Specifically, the system can first read the first location information and control range of the end-side device, and then determine the control area of the end-side device with the first location information as the center and the control range as the radius. Then, it can read the known second location information of the product device, and select the sub-device located within the control area based on the second location information and the control area to obtain the sub-device corresponding to the end-side device. In addition, after selecting the sub-devices located within the control area, all selected sub-devices can be directly used as the sub-devices corresponding to the end-side device, or the selected sub-devices that are not connected to the end-side device and the sub-devices connected to the end-side device can be used as the sub-devices corresponding to the end-side device, etc.
[0056] The topology adopts a tree structure, wherein the end device is the root node in the tree structure, and the child devices corresponding to the end device are the leaf nodes in the tree structure.
[0057] For example: Figure 2 As shown, the endpoint device is a conference room controller, and the sub-devices are an air conditioner and a sensor. Therefore, the data structure of the endpoint device's network information is as follows:
[0058]
[0059]
[0060]
[0061] It should be noted that in practical applications, cloud devices can also use other data structures to feed back device network information, in order to accommodate end devices that need to use different protocols to access the cloud device, such as MODBUS, DIDO, and unknown protocol parameters that may appear in the future.
[0062] In one implementation, before receiving the binding operation input by the user, the object model file of the sub-device can be obtained first. This object model file can be uploaded by the user or downloaded automatically by the cloud device based on the object model file information uploaded by the user. Based on this, before responding to the access operation of the end-side device and obtaining the device network information of the end-side device, the method further includes:
[0063] Receives the .so file of the product or device uploaded by the user;
[0064] Store the SO file and associate the SO file with the product device.
[0065] Specifically, a product device refers to an item that can function as a node device in the Internet of Things (IoT) and can be controlled by other devices. Examples of product devices include air conditioners, sensors, refrigerators, and smart lights. The SO file of a product device includes its object model file. In other words, the object model of the product device is encapsulated in the SO file. Uploading the SO file informs the cloud device of the object model of the product device. Upon receiving the SO file, the cloud device stores it and associates it with the product device, then distributes the object model of the product device to the edge device by sending the SO file.
[0066] Furthermore, since different end-devices can communicate with cloud devices using different protocols, in order for the cloud device to enable end-devices using different protocols to obtain the object model of the product device, when associating the SO file with the product device, the association relationship between the product device and the SO file can be stored in a preset association relationship table. This ensures that the SO file is associated with the product device, and the device information field for the product device in the preset association relationship table is expandable. In other words, the product device encapsulates its object model capabilities in the SO file, and the SO file is extracted to the cloud device. The cloud device stores the association relationship between the product device and the SO file in a preset association relationship table, so that different SO plugin information can be issued according to different business scenarios.
[0067] For example, the table structure of the preset relationship table can be:
[0068]
[0069]
[0070] Furthermore, in order to improve the flexibility of different protocols,
[0071] JSON fields can be used to expand device table information. For example, for the DIDO protocol, information such as port number and channel type needs to be specified. JSON can be used to encapsulate this information, with data fields as follows:
[0072] {
[0073] "extends":{
[0074] "soId":"1688375312073084928",
[0075] "port":73,
[0076] "CATCH":"1",
[0077] "channelType":"GPIO",
[0078] "protocolType":"DIDO"
[0079] }
[0080] }
[0081] These parameters are not fixed in the program but are dynamically loaded from metadata in the database. They can also be modified at runtime, and the front-end page can dynamically display them based on the relevant data. For example, DIDO constraints are as follows:
[0082]
[0083]
[0084] S20. Send the device network information to the end device and control the end device to access its corresponding sub-device based on the device network information.
[0085] Specifically, the cloud device sends device network information to the end device. When sending the device network information to the end device, it can send the complete device network information directly, or it can obtain the known sub-devices of the end device, remove the sub-devices from the device network information, and only send the topology between the unknown sub-devices and the end device to the end device. This can improve the access speed of the end device to access its corresponding sub-devices based on the device network information.
[0086] For example, controlling the end-side device to access its corresponding sub-device based on the device network information specifically includes:
[0087] The control device determines the access relationship between the end-side device and its corresponding sub-device based on the topology between the end-side device and its corresponding sub-device;
[0088] Based on the object model information of the terminal device and its corresponding sub-devices, download the object model files of the terminal device and its corresponding sub-devices;
[0089] Compare the verification values of each object model file with their corresponding verification values in the device network information;
[0090] If the comparison passes, the object model files are dynamically loaded so that each sub-device can be connected to the end-side device according to the access relationship.
[0091] Specifically, the device network information includes their respective check values. After the end-side device downloads the object model files of the end-side device and its corresponding sub-devices, the check values can be used to verify the object model files downloaded by the end-side device and its corresponding sub-devices to determine the accuracy of the object model files downloaded by the end-side device and its corresponding sub-devices.
[0092] Furthermore, after connecting the endpoint device and its corresponding sub-devices to the endpoint device, adjustments can be made to the connected sub-devices, such as removing, replacing, or adding sub-devices. Based on this, the method further includes: responding to a user-inputted access adjustment operation for the endpoint device, reading the target sub-device corresponding to the access adjustment operation; adjusting the device network information of the endpoint device and its corresponding sub-devices based on the access adjustment operation and the target sub-device, and sending the adjusted device network information to the endpoint device, so that the endpoint device can adjust the access relationship between the endpoint device and the target sub-device based on the device network information. The adjustment process is the same as the access process described above, and will not be repeated here; please refer to the access process for details.
[0093] In summary, this embodiment provides a method for accessing distributed devices. The method includes responding to an access operation from an end-side device, obtaining the device network information of the end-side device; obtaining the device network information of the end-side device, sending the device network information to the end-side device, and controlling the end-side device to access its corresponding sub-device based on the device network information. This application receives user-input access requests via the cloud, and then sends the device network information of the end-side device and its corresponding sub-devices to the end-side device. This allows the end-side device to automatically connect to the sub-devices based on the device network information, eliminating the need for manual connection of sub-devices to the end-side device. This not only reduces the manual cost of access but also improves access efficiency.
[0094] Based on the above-described distributed device access method, this embodiment provides a distributed device access apparatus, such as... Figure 4 As shown, the access device for the distributed device specifically includes:
[0095] The reading module 100 is used to respond to the access operation of the end-side device and obtain the device network information of the end-side device.
[0096] The control module 200 is used to acquire the device network information of the end-side device, send the device network information to the end-side device, and control the end-side device to access its corresponding sub-device based on the device network information.
[0097] Based on the above-described distributed device access method, this embodiment provides a computer-readable storage medium storing one or more programs that can be executed by one or more processors to implement the steps in the distributed device access method described in the above embodiment.
[0098] Based on the above-described access method for distributed devices, this application also provides a terminal device, such as... Figure 5 As shown, it includes at least one processor 20; a display screen 21; and a memory 22, and may also include a communications interface 23 and a bus 24. The processor 20, display screen 21, memory 22, and communications interface 23 can communicate with each other via the bus 24. The display screen 21 is configured to display a preset user guide interface in the initial setup mode. The communications interface 23 can transmit information. The processor 20 can invoke logical instructions in the memory 22 to execute the methods described in the above embodiments.
[0099] Furthermore, the logical instructions in the aforementioned memory 22 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium.
[0100] The memory 22, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, such as program instructions or modules corresponding to the methods in the embodiments of this disclosure. The processor 20 executes functional applications and data processing by running the software programs, instructions, or modules stored in the memory 22, thereby implementing the methods in the above embodiments.
[0101] The memory 22 may include a program storage area and a data storage area. The program storage area may store the operating system and application programs required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 22 may include high-speed random access memory (RAM) and non-volatile memory. Examples include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, as well as transient storage media.
[0102] Furthermore, the specific process of loading and executing multiple instruction processors in the aforementioned storage medium and terminal device has been described in detail in the above method, and will not be repeated here.
[0103] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. A method for accessing distributed devices, characterized in that, The method for accessing distributed devices specifically includes: In response to the access operation of the end-side device, the device network information of the end-side device is obtained. The device network information includes the topology between the end-side device and its corresponding sub-devices and the object model information between the end-side device and its corresponding sub-devices. The end-side device is a control device, the sub-devices are controlled devices, and at least one target sub-device exists among the sub-devices included in the device network information. The end-side device is unaware of the access relationship between the target sub-device and the end-side device, as well as the object model information of the target sub-device. The device network information is sent to the end device, and the end device is controlled to determine the access relationship between the end device and its corresponding sub-device based on the topology between the end device and its corresponding sub-device. Based on the object model information of the terminal device and its corresponding sub-devices, download the object model files of the terminal device and its corresponding sub-devices; Compare the verification values of each object model file with their corresponding verification values in the device network information; If the comparison passes, the object model files are dynamically loaded so that each sub-device can be connected to the end-side device according to the access relationship; Before obtaining the device network information of the responding end-side device from its access operation, the method further includes: The system receives a binding operation input from the user. The binding operation is used to bind a sub-device to the end-side device. The binding operation carries the location information and control range corresponding to the end-side device. Obtain the terminal device corresponding to the binding operation, and read the first position information and control range of the terminal device; The control area of the end-side device is determined with the first location information as the center and the control range as the radius. Read the known second location information of the product equipment, and select the sub-device located within the control area based on the second location information and the control area to obtain the sub-device corresponding to the end-side device; The device network information of the end-side device is constructed based on the acquired end-side device and the sub-device.
2. The method for accessing distributed devices according to claim 1, characterized in that, The topology adopts a tree structure, wherein the end device is the root node in the tree structure, and the child devices corresponding to the end device are the leaf nodes in the tree structure.
3. The method for accessing distributed devices according to claim 1, characterized in that, Before obtaining the device network information of the terminal device in response to the access operation of the terminal device, the method further includes: Receive the product / equipment .so file uploaded by the user, wherein the .so file includes the object model file of the product / equipment; Store the SO file and associate the SO file with the product device.
4. The method for accessing distributed devices according to claim 3, characterized in that, The process of storing the SO file and associating the SO file with the product device specifically includes: The SO file is stored, and the association between the product device and the SO file is stored in a preset association table so that the SO file is associated with the product device. The device information item of the product device in the preset association table is expandable.
5. The method for accessing distributed devices according to claim 1, characterized in that, The method further includes: Responding to the user's input of an access adjustment operation for the terminal device, read the target sub-device corresponding to the access adjustment operation; Based on the access adjustment operation and the target sub-device, the device network information of the end-side device and its corresponding sub-device is adjusted, and the adjusted device network information is sent to the end-side device so that the end-side device can adjust the access relationship between the end-side device and the target sub-device based on the device network information.
6. An access device for distributed devices, characterized in that, The access device for the distributed devices specifically includes: The reading module is used to respond to the access operation of the end-side device and obtain the device network information of the end-side device. The device network information includes the topology between the end-side device and its corresponding sub-devices and the object model information between the end-side device and its corresponding sub-devices. The end-side device is a control device, the sub-devices are controlled devices, and at least one target sub-device exists among the sub-devices included in the device network information. The end-side device does not know the access relationship between the target sub-device and the end-side device or the object model information of the target sub-device. The control module is used to send the device network information to the end-side device, control the end-side device to determine the access relationship between the end-side device and its corresponding sub-devices based on the topology between the end-side device and its corresponding sub-devices; download the object model files of the end-side device and its corresponding sub-devices based on the object model information of the end-side device and its corresponding sub-devices; compare the verification value of each object model file with the corresponding verification value in the device network information; if the comparison passes, dynamically load each object model file to connect each sub-device to the end-side device according to the access relationship; The process of responding to the access operation of the terminal device, before obtaining the device network information of the terminal device, further includes: The system receives a binding operation input from the user. The binding operation is used to bind a sub-device to the end-side device. The binding operation carries the location information and control range corresponding to the end-side device. Obtain the terminal device corresponding to the binding operation, and read the first position information and control range of the terminal device; The control area of the end-side device is determined with the first location information as the center and the control range as the radius. Read the known second location information of the product equipment, and select the sub-device located within the control area based on the second location information and the control area to obtain the sub-device corresponding to the end-side device; The device network information of the end-side device is constructed based on the acquired end-side device and the sub-device.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more programs, which can be executed by one or more processors to implement the steps in the access method for a distributed device as described in any one of claims 1-5.
8. A terminal device, characterized in that, include: Processor and memory; The memory stores a computer-readable program that can be executed by the processor; When the processor executes the computer-readable program, it implements the steps of the distributed device access method as described in any one of claims 1-5.
Citation Information
Patent Citations
Joint debugging development method of gateway equipment and sub-equipment, cloud platform, equipment and medium
CN117319187A
