Network topology management method and device, medium and equipment

By receiving and processing sub-device registration requests, judging and updating the topological relationship chain, the problem of topological relationship inconsistency caused by network instability is solved, ensuring the record consistency between the cloud and the gateway, and reducing the risk of abnormal device status management.

CN119094361APending Publication Date: 2024-12-06SHENZHEN TCL NEW-TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411346998.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-25
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the case of unstable network, the topological relationship between the gateway and the cloud records is prone to inconsistent, resulting in abnormalities when building device links and managing device status in the cloud.

Method used

By receiving the device registration request of the target sub-device, obtain its identity and associated gateway identity, create a topological relationship chain, and determine whether the sub-device is bound to other historical gateways. If bound, generate a delete topological relationship instruction to notify the historical gateway to delete and The associated topological relationship chain of sub-devices, thereby updating the topological relationship diagram to ensure consistency between cloud and gateway records.

Benefits of technology

Reduces the probability of an error occurring when reporting a topology relationship diagram by the historical gateway, ensures that the topology relationship between the cloud and the gateway local records is consistent, and avoids abnormal device status management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094361A_ABST
    Figure CN119094361A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a network topology management method and device, a medium and equipment. The method comprises the following steps: receiving an equipment registration request initiated by target sub-equipment; according to the device registration request, obtaining a first identifier corresponding to a target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device; creating a topological relation chain between the target sub-device and the target gateway according to the first identifier and the second identifier, and updating a current topological relation graph; judging whether the target sub-equipment is bound with other historical gateways except the target gateway or not; and if the target sub-device is bound with other historical gateways, generating a first topological relation deletion instruction, issuing the first topological relation deletion instruction to the historical gateway, and notifying the historical gateway to delete a historical topological relation chain currently associated with the target sub-device. According to the method and the device, the probability of report errors when the historical gateway reports the topological relation graph can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to the field of network topology management technology, and in particular to a network topology management method, device, medium and equipment. Background Art

[0002] In the field of IoT, most devices do not have the ability to directly connect to the cloud and the required hardware resources. They need to be transferred through a gateway in order to connect to the cloud and achieve remote control. After connecting to the gateway, the device will become a sub-device of the gateway, and the gateway will locally save the topological relationship between the sub-device and its corresponding sub-device. When a sub-device joins the network for the first time, it will send a device registration request to the cloud through the corresponding gateway. After receiving the device registration request, the cloud will assign a unique identifier to the sub-device and allow the sub-device to join the network. At the same time, after the registration is successful, the cloud will synchronously record the topological relationship between the sub-device and the gateway.

[0003] The topology relationship is used to manage the relationship between sub-devices and the gateway, ensuring that the cloud can build the correct device link and effectively manage the status of each device. Therefore, it is particularly important that the topology relationship recorded locally by the gateway is consistent with the topology relationship recorded in the cloud. However, sub-devices may leave the gateway for various reasons, such as the cloud deleting it, the user removing it or replacing it. In these cases, the topology relationship between the gateway and the cloud needs to be updated in a timely manner to maintain the accuracy of the information. However, in the case of unstable network, it is easy for the topology relationship recorded by the gateway and the cloud to be inconsistent, resulting in abnormalities when the cloud builds device links and manages device status.

[0004] For example, during the process of transferring a sub-device from gateway A to gateway B for mounting, if gateway A is disconnected from the Internet at this time, gateway A cannot update the local topology in real time and upload it to the cloud for synchronous update. Since gateway A cannot obtain the information that the sub-device has been removed in time during the power outage, after gateway A resumes networking, it will report the topology before the update to the cloud. In the unupdated topology, the sub-device is still in a mounted state, resulting in the information received by the cloud showing that the sub-device is mounted under gateway A and gateway B at the same time, resulting in inconsistency between the topology recorded in the cloud and the local gateway. Summary of the invention

[0005] The embodiments of the present application provide a network topology management method, apparatus, medium and device. The network topology management method provided in the embodiments of the present application is used to solve the problem that when the network is unstable, the topological relationship recorded locally by the gateway and in the cloud is inconsistent, which leads to abnormalities in the cloud when building device links and state management.

[0006] On the one hand, an embodiment of the present application provides a network topology management method, which is applied to a cloud platform, including:

[0007] Receive a device registration request initiated by a target sub-device;

[0008] According to the device registration request, obtaining a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0009] According to the first identifier and the second identifier, a topological relationship chain between the target sub-device and the target gateway is created, and a current topological relationship diagram is updated;

[0010] Determine whether the target sub-device has been bound to other historical gateways except the target gateway;

[0011] If the target sub-device has been bound to other historical gateways, a first topology relationship deletion instruction is generated and sent to the historical gateway to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0012] In the network topology management method described in the embodiment of the present application, after the generating and sending the instruction to delete the first topology relationship to the historical gateway, the method further includes:

[0013] After receiving the deletion confirmation information returned by the historical gateway, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

[0014] In the network topology management method described in the embodiment of the present application, after determining whether the target sub-device has been bound to other historical gateways other than the target gateway, the method further includes:

[0015] If the target sub-device is not bound to other historical gateways, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

[0016] In the network topology management method described in the embodiment of the present application, after obtaining the first identifier corresponding to the target sub-device, the method further includes:

[0017] authenticating the target sub-device according to the first identifier;

[0018] If the target sub-device passes the identity authentication, executing the step of creating a topological relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier;

[0019] If the target sub-device does not pass the identity authentication, the device registration request is rejected, and registration failure information is generated and sent to the target sub-device.

[0020] Accordingly, another aspect of the embodiment of the present application further provides a network topology management method, which is applied to a historical gateway, including:

[0021] In response to a power-off and restart operation of the device, obtaining a target topology relationship diagram corresponding to the historical gateway from a cloud platform;

[0022] Compare the target topology relationship graph with the historical topology relationship graph stored locally on the historical gateway to obtain a comparison result;

[0023] If the comparison result is that the target topology relationship graph is inconsistent with the historical topology relationship graph, an abnormal topology relationship chain is determined from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and the abnormal topology relationship chain is deleted.

[0024] In the network topology management method described in the embodiment of the present application, determining an abnormal topology relationship chain from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and deleting the abnormal topology relationship chain, includes:

[0025] If the comparison result is that the number of sub-devices mounted on the historical gateway in the historical topology relationship diagram is greater than the number of sub-devices mounted on the historical gateway in the target topology relationship diagram, the topology relationship chain corresponding to the redundant sub-devices is regarded as an abnormal topology relationship chain;

[0026] The abnormal topology relationship chain is deleted from the historical topology relationship graph.

[0027] In the network topology management method described in the embodiment of the present application, determining an abnormal topology relationship chain from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and deleting the abnormal topology relationship chain, includes:

[0028] If the comparison result is that the number of sub-devices mounted on the historical gateway in the target topology relationship diagram is greater than the number of sub-devices mounted on the historical gateway in the historical topology relationship diagram, the topology relationship chain corresponding to the redundant sub-devices is taken as an abnormal topology relationship chain;

[0029] Generate a second topology relationship deletion instruction and send it to the cloud platform, informing the cloud platform to delete the abnormal topology relationship chain.

[0030] Accordingly, another aspect of the present application embodiment further provides a network topology management device, which is applied to a cloud platform. The network topology management device includes:

[0031] A receiving module, used to receive a device registration request initiated by a target sub-device;

[0032] An acquisition module, configured to acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0033] A creation module, used to create a topology relationship chain between a target sub-device and a target gateway according to the first identifier and the second identifier, and update a current topology relationship diagram;

[0034] A determination module, used to determine whether the target sub-device has been bound to other historical gateways except the target gateway;

[0035] The notification module is used to generate a first topology relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, so as to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0036] Correspondingly, another aspect of the embodiment of the present application further provides a storage medium, wherein the storage medium stores a plurality of instructions, wherein the instructions are suitable for loading by a processor to execute the network topology management method as described above.

[0037] Correspondingly, another aspect of an embodiment of the present application further provides an electronic device, including a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the network topology management method as described above.

[0038] The embodiment of the present application provides a network topology management method, device, medium and equipment, which receives a device registration request initiated by a target sub-device; obtains a first identifier corresponding to the target sub-device and a second identifier corresponding to the target gateway associated with the target sub-device according to the device registration request; creates a topology relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier, and updates the current topology relationship diagram; determines whether the target sub-device has been bound to other historical gateways except the target gateway; if the target sub-device has been bound to other historical gateways, generates a first topology relationship deletion instruction to send to the historical gateway, and notifies the historical gateway to delete the current historical topology relationship chain associated with the target sub-device. Using the network topology management method provided by the embodiment of the present application, it is possible to receive a registration request from a sub-device in the cloud, and after successfully creating a topology relationship between the sub-device and the gateway, first determine whether the sub-device has been bound to other historical gateways, and if it has been bound to other historical gateways, generates a topology relationship deletion instruction to send to the historical gateway, and notifies the historical gateway to delete the current historical topology relationship chain with the sub-device, thereby reducing the probability of the historical gateway reporting an error when reporting the topology relationship diagram. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without creative work.

[0040] Figure 1 A flowchart of a network topology management method provided in an embodiment of the present application.

[0041] Figure 2 Another flowchart of the network topology management method provided in an embodiment of the present application.

[0042] Figure 3 Another flowchart of the network topology management method provided in an embodiment of the present application.

[0043] Figure 4 Another flowchart of the network topology management method provided in an embodiment of the present application.

[0044] Figure 5 A schematic diagram of the structure of a network topology management device provided in an embodiment of the present application.

[0045] Figure 6 Another structural schematic diagram of the network topology management device provided in an embodiment of the present application.

[0046] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0048] An embodiment of the present application provides a network topology management method, which can receive a registration request from a sub-device in the cloud, and after successfully creating a topological relationship between the sub-device and the gateway, first determine whether the sub-device has been bound to other historical gateways. If it has been bound to other historical gateways, generate a delete topology relationship instruction and send it to the historical gateway, informing the historical gateway to delete the current historical topological relationship chain with the sub-device, thereby reducing the probability of the historical gateway reporting an error when reporting a topological relationship diagram.

[0049] The term "and / or" in this application can be a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0050] The terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments described here can be implemented in an order other than that illustrated or described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to the steps or modules clearly listed, but may include other steps or modules that are not clearly listed or inherent to these processes, methods, products or devices. The naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time / logical sequence indicated by the naming or numbering. The process steps that have been named or numbered can change the execution order according to the technical purpose to be achieved, as long as the same or similar technical effects can be achieved. The division of modules in this application is a logical division. There may be other division methods when it is implemented in actual applications. For example, multiple modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection between modules can be electrical or other similar forms, which are not limited in this application. In addition, the modules or submodules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the present application.

[0051] The network topology management method involved in the embodiment of the present application is mainly applied to electronic devices, which may be gateways, smart phones, tablet computers, laptops, desktop computers, smart home appliances, servers, etc., which are not limited here. Optionally, the server may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or an IoT cloud (Internet of Things cloud) that provides the ability to store, process and manage data generated by IoT devices, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms, which are not limited here.

[0052] For ease of understanding, the specific process in the embodiments of the present application is described below. Figure 1 , Figure 1 A flowchart of an embodiment of a network topology management method provided in an embodiment of the present application.

[0053] exist Figure 1 In the illustrated embodiment, the method is applied to a cloud platform and may include the following steps:

[0054] S101, receiving a device registration request initiated by a target sub-device.

[0055] In this embodiment, a sub-device refers to a device that is directly connected to the gateway and can communicate with the gateway wirelessly or by wire. The sub-device can be a sensor, actuator, or other type of IoT device, which usually has weak computing power and limited communication capabilities. The sub-device collects and sends data to the gateway, and the gateway forwards the data to the cloud or other networks. For example, in a smart home system, various devices in the home network (such as smart bulbs, smart sockets, security cameras, etc.) may be connected to a gateway wirelessly. This gateway is responsible for managing the communication of these devices and sending data to the cloud platform for processing. In this smart home system, the gateway is the main device, while smart bulbs, smart sockets and other devices are sub-devices of the network management.

[0056] When a target sub-device wants to join the network to achieve networking, the target sub-device sends a device registration request to the cloud platform through the gateway. After receiving the device registration request, the cloud platform will allow the target sub-device to join the network to communicate with the outside world if the registration is successful.

[0057] S102: Acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device.

[0058] In this embodiment, the first identifier and the second identifier refer to device identifiers corresponding to the target sub-device and the target gateway, respectively, and are used to identify and distinguish between different devices and the cloud platform. The first identifier and the second identifier can be represented by the device's MAC address, serial number, IMEI number (for mobile phones) or other unique identification codes embedded in the device when it is manufactured, which are not limited here.

[0059] S103: Create a topology relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier, and update the current topology relationship diagram.

[0060] In this embodiment, the topology relationship diagram is used to manage the relationship between the sub-device and the gateway, ensure that the cloud can build the correct device link, and effectively manage the status of each device. Therefore, after obtaining the first identifier and the second identifier, it is necessary to create a topology relationship chain between the target sub-device and the target gateway on the cloud platform and update the current topology relationship diagram.

[0061] S104: Determine whether the target sub-device has been bound to other historical gateways except the target gateway.

[0062] It should be noted that in order to ensure the stability and efficiency of the IoT system, the gateway usually needs to save a local topology diagram and keep it consistent with the topology diagram recorded by the cloud platform. In this way, the gateway can quickly respond to changes in device status, ensure the efficient operation of the system, and maintain basic functions when cloud services are unavailable.

[0063] Since the status of sub-devices and gateways in the IoT system may change dynamically, such as the cloud platform deleting a sub-device or gateway, the user removing a sub-device or gateway, or the user replacing a sub-device or gateway. In these cases, the topology diagram between the gateway and the cloud platform needs to be updated in a timely manner to maintain the accuracy of the information. However, in the case of unstable network, it is easy to produce inconsistent topology relationships between the gateway and the cloud, which will cause abnormalities in the cloud platform when building device links and managing device status.

[0064] For example, during the process of transferring the target sub-device from gateway A to gateway B for mounting, if gateway A is disconnected from the Internet at this time, gateway A cannot update the local topology relationship in real time and upload it to the cloud platform for synchronous update. Since gateway A cannot obtain the information that the target sub-device has been removed in time during the power outage, after gateway A resumes networking, it will report the topology relationship before the update to the cloud platform, and the target sub-device is still in the mounted state in the unupdated topology relationship, resulting in the cloud platform receiving information showing that the target sub-device is mounted under gateway A and gateway B at the same time, resulting in inconsistency between the topology relationship recorded locally by the cloud platform and the gateway.

[0065] From the above example scenario, it can be known that by analyzing the topology diagram currently recorded by the cloud platform, whether the target sub-device has multiple bound gateways, it can be determined that other historical gateways bound to the target sub-device may not have uploaded the correct topology diagram in time, resulting in inconsistency between the cloud platform and the local topology diagram recorded by the target gateway. Therefore, in this embodiment, it is necessary to first determine whether the target sub-device has been bound to other historical gateways except the target gateway, so as to analyze whether there is a possibility that the topology diagram recorded locally by the cloud platform and the target gateway is inconsistent.

[0066] S105: If the target sub-device has been bound to other historical gateways, a first topology relationship deletion instruction is generated and sent to the historical gateway to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0067] If it is determined that the target sub-device has been bound to other historical gateways, it means that the historical gateway may have failed to upload the correct topology diagram to the cloud platform in time due to some circumstances, resulting in the target sub-device being bound to multiple different gateways at the same time. In order to avoid the topology diagram recorded on the cloud platform being inconsistent with the topology diagram recorded locally on the historical gateway after updating, in this embodiment, a delete topology instruction is generated and sent to the historical gateway, informing the historical gateway to delete the current topology relationship with the target sub-device, thereby ensuring that the historical gateway will not report an error when reporting the topology diagram to the cloud platform next time.

[0068] It needs to be explained that in the IoT system, when a sub-device changes its gateway and registers with the cloud platform, the cloud platform usually handles it by updating it based on the original topology diagram, rather than simply overwriting the historical topology chain. That is, when a sub-device registers with a new gateway, the cloud platform will add a new topology chain from the sub-device to the new gateway in the topology diagram. For the old historical topology chain, the cloud platform may mark it as inactive or released, indicating that the sub-device is no longer associated with it. Doing so ensures that the cloud platform's database accurately reflects the current status of the sub-device. Specifically, the historical topology chain remains unchanged, and the cloud platform retains the association information of all gateways in the history of the sub-device, even if the sub-device has been moved to a new gateway.

[0069] In some embodiments, Figure 2 As shown, after the instruction to delete the first topological relationship is generated and sent to the historical gateway, the method further includes:

[0070] After receiving the deletion confirmation information returned by the historical gateway, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

[0071] In some embodiments, Figure 2 As shown, after determining whether the target sub-device has been bound to other historical gateways except the target gateway, the method further includes:

[0072] If the target sub-device is not bound to other historical gateways, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

[0073] In some embodiments, Figure 2 As shown, after obtaining the first identifier corresponding to the target sub-device, the method further includes:

[0074] authenticating the target sub-device according to the first identifier;

[0075] If the target sub-device passes the identity authentication, executing the step of creating a topological relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier;

[0076] If the target sub-device does not pass the identity authentication, the device registration request is rejected, and registration failure information is generated and sent to the target sub-device.

[0077] As can be seen from the above, the network topology management method provided by the embodiment of the present application receives a device registration request initiated by a target sub-device; according to the device registration request, obtains a first identifier corresponding to the target sub-device and a second identifier corresponding to the target gateway associated with the target sub-device; according to the first identifier and the second identifier, creates a topology relationship chain between the target sub-device and the target gateway, and updates the current topology relationship diagram; determines whether the target sub-device has been bound to other historical gateways except the target gateway; if the target sub-device has been bound to other historical gateways, generates a first topology relationship deletion instruction and sends it to the historical gateway, notifying the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device. Using the network topology management method provided by the embodiment of the present application, it is possible to receive a registration request from a sub-device in the cloud, and after successfully creating a topology relationship between the sub-device and the gateway, first determine whether the sub-device has been bound to other historical gateways, and if it has been bound to other historical gateways, generates a topology relationship deletion instruction and sends it to the historical gateway, notifying the historical gateway to delete the current historical topology relationship chain with the sub-device, thereby reducing the probability of the historical gateway reporting an error when reporting the topology relationship diagram.

[0078] In some embodiments, Figure 3 In the illustrated embodiment, the method may also be applied to a historical gateway, comprising the following steps:

[0079] S201, in response to a power-off and restart operation of a device, obtaining a target topology relationship diagram corresponding to the historical gateway from a cloud platform.

[0080] Considering that when the cloud platform sends the first delete topology relationship instruction to the historical gateway, if the historical gateway is disconnected from the network, the historical gateway in the disconnected state fails to receive the first delete topology relationship instruction in time, resulting in failure to successfully delete the historical topology relationship chain with the target sub-device, which causes the historical topology relationship diagram recorded locally by the historical gateway to still be inconsistent with the topology relationship diagram recorded by the cloud platform. In order to solve the above problem, in this embodiment, it is necessary to first obtain the target topology relationship diagram corresponding to the historical gateway from the cloud platform after the historical gateway is powered off and restarted, and analyze whether the target topology relationship diagram is consistent with the historical topology relationship diagram recorded locally by the historical gateway. Figure 1 Instead of directly uploading the current historical topology diagram to the cloud platform, it avoids the inconsistency between the historical topology diagram and the target topology diagram.

[0081] S202: Compare the target topology relationship graph with the historical topology relationship graph stored locally in the historical gateway to obtain a comparison result.

[0082] In this embodiment, the comparison process of the target topology relationship diagram and the historical topology relationship diagram is mainly to compare whether the gateways corresponding to the same sub-device in the two topology relationship diagrams are consistent, and the corresponding gateways are not marked as inactive or released. If the gateways corresponding to the same sub-device in the two topology relationship diagrams are consistent, and neither is marked as inactive or released, it means that the comparison result between the target topology relationship diagram and the historical topology relationship diagram is that the two are consistent, otherwise the comparison result is that the two are inconsistent.

[0083] S203: If the comparison result is that the target topology relationship graph is inconsistent with the historical topology relationship graph, an abnormal topology relationship chain is determined from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and the abnormal topology relationship chain is deleted.

[0084] In this embodiment, if Figure 4 As shown, if the comparison result is that the number of sub-devices mounted on the historical gateway in the historical topology diagram is greater than the number of sub-devices mounted on the historical gateway in the target topology diagram, the topology relationship chain corresponding to the redundant sub-devices is taken as an abnormal topology relationship chain; the abnormal topology relationship chain is deleted from the historical topology relationship diagram. This avoids inconsistency between the local and cloud platform topology relationship diagrams after the sub-device completes the gateway transfer operation.

[0085] For example, when a sub-device is passively removed from gateway 1 and registered on gateway 2, the sub-device cannot notify gateway 1 because gateway 1 is in an offline state. When gateway 1 recovers from the Internet and detects that the current target sub-device has been removed, it usually does not directly delete the topological relationship chain between the sub-device and the sub-device, but only defaults to the sub-device being offline. The corresponding topological relationship chain is deleted only when the sub-device is not detected after a timeout. Therefore, the topological relationship chain between the sub-device and gateway 1 is retained in the topological relationship diagram locally saved by gateway 1 at this time, resulting in a comparison result that the number of sub-devices mounted on the gateway in the local topological relationship diagram is greater than the number of sub-devices mounted in the topological relationship diagram of the cloud platform.

[0086] like Figure 4 As shown, if the comparison result is that the number of sub-devices mounted on the historical gateway in the target topology relationship diagram is greater than the number of sub-devices mounted on the historical gateway in the historical topology relationship diagram, the topology relationship chain corresponding to the redundant sub-devices is regarded as an abnormal topology relationship chain; a second topology relationship deletion instruction is generated and sent to the cloud platform to notify the cloud platform to delete the abnormal topology relationship chain. Avoid inconsistency between the local and cloud platform recorded topology relationship diagrams.

[0087] For example, if a sub-device actively withdraws from binding on Gateway 1, even if Gateway 1 is disconnected from the Internet, it will know that the current sub-device has been removed after the Internet is restored. Therefore, the local topology diagram is inconsistent with the topology diagram recorded by the cloud platform. The number of sub-devices mounted on the gateway in the topology diagram of the cloud platform will be greater than the number of sub-devices mounted on the gateway in the local topology diagram.

[0088] In some embodiments, Figure 4 As shown, if the comparison result is the target topology relationship diagram and the historical topology relationship Figure 1 If the local topology relationship diagram is consistent, the historical topology relationship diagram recorded locally will be uploaded to the cloud platform at the specified time point.

[0089] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0090] In specific implementation, the present application is not limited by the execution order of the various steps described. If no conflict occurs, some steps can be performed in other orders or simultaneously.

[0091] As can be seen from the above, the network topology management method provided by the embodiment of the present application receives a device registration request initiated by a target sub-device; according to the device registration request, obtains a first identifier corresponding to the target sub-device and a second identifier corresponding to the target gateway associated with the target sub-device; according to the first identifier and the second identifier, creates a topology relationship chain between the target sub-device and the target gateway, and updates the current topology relationship diagram; determines whether the target sub-device has been bound to other historical gateways except the target gateway; if the target sub-device has been bound to other historical gateways, generates a first topology relationship deletion instruction and sends it to the historical gateway, notifying the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device. Using the network topology management method provided by the embodiment of the present application, after the historical gateway is restored to the network, it obtains the target topology relationship diagram from the cloud platform and compares it with the local historical topology relationship diagram of the historical gateway. If the comparison result is that the two are inconsistent, the abnormal topology relationship chain is deleted according to the actual comparison situation, thereby reducing the probability of the historical gateway reporting an error when reporting the topology relationship diagram.

[0092] An embodiment of the present application also provides a network topology management device, which can be integrated into an electronic device.

[0093] See also Figure 5 , Figure 5 A schematic diagram of the structure of a network topology management device provided in an embodiment of the present application. The network topology management device 30 may include:

[0094] A receiving module 31, configured to receive a device registration request initiated by a target sub-device;

[0095] An acquisition module 32, configured to acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0096] A creation module 33, used to create a topology relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier, and update the current topology relationship diagram;

[0097] A determination module 34 is used to determine whether the target sub-device has been bound to other historical gateways except the target gateway;

[0098] The notification module 35 is used to generate a first topology relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, so as to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0099] In some embodiments, the apparatus further comprises a first sending module, which is used to generate a registration success message and send it to the target sub-device after receiving the deletion confirmation message returned by the historical gateway, so as to complete the sub-device registration operation.

[0100] In some embodiments, the apparatus further comprises a second sending module, which is used to generate a registration success message and send it to the target sub-device if the target sub-device is not bound to other historical gateways, so as to complete the sub-device registration operation.

[0101] In some embodiments, the device also includes a verification module for authenticating the target sub-device based on the first identifier; if the target sub-device passes the identity authentication, the step of creating a topological relationship chain between the target sub-device and the target gateway based on the first identifier and the second identifier is executed; if the target sub-device does not pass the identity authentication, the device registration request is rejected, and a registration failure message is generated and sent to the target sub-device.

[0102] In specific implementation, the above modules can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same entity or several entities.

[0103] As can be seen from the above, the network topology management device 30 provided in the embodiment of the present application, wherein the receiving module 31 is used to receive a device registration request initiated by a target sub-device; the obtaining module 32 is used to obtain a first identifier corresponding to the target sub-device and a second identifier corresponding to the target gateway associated with the target sub-device according to the device registration request; the creating module 33 is used to create a topological relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier, and update the current topological relationship diagram; the judging module 34 is used to judge whether the target sub-device has been bound to other historical gateways except the target gateway; the notifying module 35 is used to generate a first topological relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, and notify the historical gateway to delete the historical topological relationship chain currently associated with the target sub-device.

[0104] See also Figure 6 , Figure 6 Another structural diagram of the network topology management device provided in the embodiment of the present application, the network topology management device 30 includes a memory 120, one or more processors 180, and one or more applications, wherein the one or more applications are stored in the memory 120 and configured to be executed by the processor 180; the processor 180 may include a receiving module 31, an acquisition module 32, a creation module 33, a judgment module 34, and a notification module 35. For example, the structure and connection relationship of the above components may be as follows:

[0105] The memory 120 can be used to store applications and data. The applications stored in the memory 120 include executable codes. The applications can be composed of various functional modules. The processor 180 executes various functional applications and data processing by running the applications stored in the memory 120. In addition, the memory 120 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 120 may also include a memory controller to provide the processor 180 with access to the memory 120.

[0106] The processor 180 is the control center of the device, and uses various interfaces and lines to connect various parts of the entire terminal, and executes various functions of the device and processes data by running or executing applications stored in the memory 120, and calling data stored in the memory 120, so as to monitor the device as a whole. Optionally, the processor 180 may include one or more processing cores; preferably, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs.

[0107] Specifically in this embodiment, the processor 180 will load the executable code corresponding to the process of one or more applications into the memory 120 according to the following instructions, and the processor 180 will run the application stored in the memory 120 to implement various functions:

[0108] A receiving instruction is used to receive a device registration request initiated by a target sub-device;

[0109] An acquisition instruction, used to acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0110] A creation instruction, used to create a topology relationship chain between a target sub-device and a target gateway according to the first identifier and the second identifier, and update a current topology relationship diagram;

[0111] A judgment instruction, used to judge whether the target sub-device has been bound to other historical gateways except the target gateway;

[0112] The notification instruction is used to generate a first topology relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, so as to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0113] In some embodiments, the program further includes a first sending instruction for generating a registration success message and sending it to the target sub-device after receiving the deletion confirmation message returned by the historical gateway, thereby completing the sub-device registration operation.

[0114] In some embodiments, the program further includes a second sending instruction for generating a registration success message and sending it to the target sub-device if the target sub-device is not bound to other historical gateways, thereby completing the sub-device registration operation.

[0115] In some embodiments, the program also includes a verification instruction for authenticating the target sub-device based on the first identifier; if the target sub-device passes the identity authentication, the step of creating a topological relationship chain between the target sub-device and the target gateway based on the first identifier and the second identifier is executed; if the target sub-device does not pass the identity authentication, the device registration request is rejected, and a registration failure message is generated and sent to the target sub-device.

[0116] The present application also provides an electronic device. Figure 7 , Figure 7The electronic device 1200 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application, and the electronic device can be used to implement the network topology management method provided in the above embodiment. The electronic device 1200 can be a gateway, a smart phone, or a tablet computer.

[0117] like Figure 7 As shown, the electronic device 1200 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more (only one is shown in the figure) computer-readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a transmission module 170, a processor 180 including one or more (only one is shown in the figure) processing cores, and a power supply 190. Those skilled in the art will understand that Figure 7 The structure of the electronic device 1200 shown in the figure does not constitute a limitation on the electronic device 1200, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0118] The RF circuit 110 is used to receive and send electromagnetic waves, realize the mutual conversion between electromagnetic waves and electrical signals, and thus communicate with a communication network or other devices. The RF circuit 110 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption / decryption chip, a user identity module (SIM) card, a memory, etc. The RF circuit 110 can communicate with various networks such as the Internet, an intranet, a wireless network, or communicate with other devices through a wireless network.

[0119] The memory 120 can be used to store software programs and modules, such as the program instructions / modules corresponding to the network topology management method in the above embodiment. The processor 180 executes various functional applications and data processing by running the software programs and modules stored in the memory 120. The vibration reminder mode can be automatically selected according to the current scene of the electronic device to perform network topology management, which can not only ensure that scenes such as meetings are not disturbed, but also ensure that users can perceive incoming calls, thereby improving the intelligence of the electronic device. The memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 120 may further include a memory remotely arranged relative to the processor 180, and these remote memories may be connected to the electronic device 1200 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0120] The input unit 130 can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control. Specifically, the input unit 130 may include a touch-sensitive surface 131 and other input devices 132. The touch-sensitive surface 131, also known as a touch display screen or a touch pad, can collect the user's touch operations on or near it (such as the user's operation on or near the touch-sensitive surface 131 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch-sensitive surface 131 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into touch point coordinates, and then sends it to the processor 180, and can receive and execute commands sent by the processor 180. In addition, the touch-sensitive surface 131 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch-sensitive surface 131, the input unit 130 may further include other input devices 132. Specifically, the other input devices 132 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, and the like.

[0121] The display unit 140 can be used to display information input by the user or information provided to the user and various graphical user interfaces of the electronic device 1200, which can be composed of graphics, text, icons, videos and any combination thereof. The display unit 140 may include a display panel 141. Optionally, the display panel 141 may be configured in the form of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc. Further, the touch-sensitive surface 131 may cover the display panel 141. When the touch-sensitive surface 131 detects a touch operation on or near it, it is transmitted to the processor 180 to determine the type of touch event. Subsequently, the processor 180 provides corresponding visual output on the display panel 141 according to the type of touch event. Although in Figure 7 In the embodiment, the touch-sensitive surface 131 and the display panel 141 are implemented as two independent components to realize the input and output functions. However, in some embodiments, the touch-sensitive surface 131 and the display panel 141 can be integrated to realize the input and output functions.

[0122] The electronic device 1200 may also include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 141 and / or the backlight when the electronic device 1200 is moved to the ear. As a type of motion sensor, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that can also be configured in the electronic device 1200, they will not be repeated here.

[0123] The audio circuit 160, the speaker 161, and the microphone 162 can provide an audio interface between the user and the electronic device 1200. The audio circuit 160 can transmit the received audio data to the speaker 161 after converting the received audio data into an electrical signal, which is converted into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 160 and converted into audio data, and then the audio data is processed by the output processor 180, and then sent to another terminal through the RF circuit 110, or the audio data is output to the memory 120 for further processing. The audio circuit 160 may also include an earplug jack to provide communication between an external headset and the electronic device 1200.

[0124] The electronic device 1200 can help users send and receive emails, browse web pages, and access streaming media through the transmission module 170 (such as a Wi-Fi module), which provides users with wireless broadband Internet access. Figure 7 The transmission module 170 is shown, but it is understandable that it is not an essential component of the electronic device 1200 and can be omitted as needed without changing the essence of the invention.

[0125] The processor 180 is the control center of the electronic device 1200. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 120, and calling data stored in the memory 120, it executes various functions of the electronic device 1200 and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 180 may include one or more processing cores; in some embodiments, the processor 180 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 180.

[0126] The electronic device 1200 also includes a power supply 190 for supplying power to various components. In some embodiments, the power supply can be logically connected to the processor 180 through a power management system, so that the power management system can realize functions such as managing discharge and power consumption. The power supply 190 can also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.

[0127] Although not shown, the electronic device 1200 may also include a camera (such as a front camera, a rear camera), a Bluetooth module, etc., which will not be described in detail here. Specifically in this embodiment, the display unit 140 of the electronic device 1200 is a touch screen display, and the electronic device 1200 also includes a memory 120, and one or more programs, wherein one or more programs are stored in the memory 120, and are configured to be executed by one or more processors 180. One or more programs include instructions for performing the following operations:

[0128] A receiving instruction is used to receive a device registration request initiated by a target sub-device;

[0129] An acquisition instruction, used to acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0130] A creation instruction, used to create a topology relationship chain between a target sub-device and a target gateway according to the first identifier and the second identifier, and update a current topology relationship diagram;

[0131] A judgment instruction, used to judge whether the target sub-device has been bound to other historical gateways except the target gateway;

[0132] The notification instruction is used to generate a first topology relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, so as to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0133] In some embodiments, the program further includes a first sending instruction for generating a registration success message and sending it to the target sub-device after receiving the deletion confirmation message returned by the historical gateway, thereby completing the sub-device registration operation.

[0134] In some embodiments, the program further includes a second sending instruction for generating a registration success message and sending it to the target sub-device if the target sub-device is not bound to other historical gateways, thereby completing the sub-device registration operation.

[0135] In some embodiments, the program also includes a verification instruction for authenticating the target sub-device based on the first identifier; if the target sub-device passes the identity authentication, the step of creating a topological relationship chain between the target sub-device and the target gateway based on the first identifier and the second identifier is executed; if the target sub-device does not pass the identity authentication, the device registration request is rejected, and a registration failure message is generated and sent to the target sub-device.

[0136] The embodiment of the present application also provides an electronic device, which may be a smart phone, a gateway, a computer, or other device.

[0137] As can be seen from the above, the embodiment of the present application provides an electronic device 1200, and the electronic device 1200 performs the following steps:

[0138] Receive a device registration request initiated by a target sub-device;

[0139] According to the device registration request, obtaining a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device;

[0140] According to the first identifier and the second identifier, a topological relationship chain between the target sub-device and the target gateway is created, and a current topological relationship diagram is updated;

[0141] Determine whether the target sub-device has been bound to other historical gateways except the target gateway;

[0142] If the target sub-device has been bound to other historical gateways, a first topology relationship deletion instruction is generated and sent to the historical gateway to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

[0143] In some embodiments, the electronic device 1200 further performs the following steps:

[0144] In response to a power-off and restart operation of the device, obtaining a target topology relationship diagram corresponding to the historical gateway from a cloud platform;

[0145] Compare the target topology relationship graph with the historical topology relationship graph stored locally on the historical gateway to obtain a comparison result;

[0146] If the comparison result is that the target topology relationship graph is inconsistent with the historical topology relationship graph, an abnormal topology relationship chain is determined from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and the abnormal topology relationship chain is deleted.

[0147] An embodiment of the present application further provides a storage medium, wherein a computer program is stored in the storage medium. When the computer program runs on a computer, the computer executes the network topology management method described in any of the above embodiments.

[0148] It should be noted that, for the network topology management method described in the present application, ordinary testers in the field can understand that the implementation of all or part of the process of the network topology management method described in the embodiment of the present application can be completed by controlling the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, such as stored in the memory of an electronic device, and executed by at least one processor in the electronic device, and the execution process may include the process of the embodiment of the network topology management method. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), etc.

[0149] For the network topology management device of the embodiment of the present application, each functional module can be integrated into a processing chip, or each module can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium, such as a read-only memory, a disk or an optical disk.

[0150] The network topology management method, device, medium and equipment provided by the embodiments of the present application are described in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and core idea of ​​the present application. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A network topology management method, applied to a cloud platform, characterized in that: include: Receive a device registration request initiated by a target sub-device; According to the device registration request, obtaining a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device; According to the first identifier and the second identifier, a topological relationship chain between the target sub-device and the target gateway is created, and a current topological relationship diagram is updated; Determine whether the target sub-device has been bound to other historical gateways except the target gateway; If the target sub-device has been bound to other historical gateways, a first topology relationship deletion instruction is generated and sent to the historical gateway to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

2. The network topology management method according to claim 1, characterized in that: After the generating and sending the instruction to delete the first topological relationship to the historical gateway, the method further includes: After receiving the deletion confirmation information returned by the historical gateway, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

3. The network topology management method according to claim 1, characterized in that: After determining whether the target sub-device has been bound to other historical gateways except the target gateway, the method further includes: If the target sub-device is not bound to other historical gateways, a registration success message is generated and sent to the target sub-device to complete the sub-device registration operation.

4. The network topology management method according to claim 1, characterized in that: After acquiring the first identifier corresponding to the target sub-device, the method further includes: authenticating the target sub-device according to the first identifier; If the target sub-device passes the identity authentication, executing the step of creating a topological relationship chain between the target sub-device and the target gateway according to the first identifier and the second identifier; If the target sub-device does not pass the identity authentication, the device registration request is rejected, and registration failure information is generated and sent to the target sub-device.

5. A network topology management method, applied to a historical gateway, characterized in that: include: In response to a power-off and restart operation of the device, obtaining a target topology relationship diagram corresponding to the historical gateway from a cloud platform; Compare the target topology relationship graph with the historical topology relationship graph stored locally on the historical gateway to obtain a comparison result; If the comparison result is that the target topology relationship graph is inconsistent with the historical topology relationship graph, an abnormal topology relationship chain is determined from the target topology relationship graph or the historical topology relationship graph according to the comparison result, and the abnormal topology relationship chain is deleted.

6. The network topology management method according to claim 5, characterized in that: The step of determining an abnormal topology relationship chain from the target topology relationship graph or the historical topology relationship graph according to the comparison result and deleting the abnormal topology relationship chain includes: If the comparison result is that the number of sub-devices mounted on the historical gateway in the historical topology relationship diagram is greater than the number of sub-devices mounted on the historical gateway in the target topology relationship diagram, the topology relationship chain corresponding to the redundant sub-devices is regarded as an abnormal topology relationship chain; The abnormal topology relationship chain is deleted from the historical topology relationship graph.

7. The network topology management method according to claim 5, characterized in that: The step of determining an abnormal topology relationship chain from the target topology relationship graph or the historical topology relationship graph according to the comparison result and deleting the abnormal topology relationship chain includes: If the comparison result is that the number of sub-devices mounted on the historical gateway in the target topology relationship diagram is greater than the number of sub-devices mounted on the historical gateway in the historical topology relationship diagram, the topology relationship chain corresponding to the redundant sub-devices is taken as an abnormal topology relationship chain; Generate a second topology relationship deletion instruction and send it to the cloud platform, informing the cloud platform to delete the abnormal topology relationship chain.

8. A network topology management device, applied to a cloud platform, characterized in that: The network topology management device comprises: A receiving module, used to receive a device registration request initiated by a target sub-device; An acquisition module, configured to acquire, according to the device registration request, a first identifier corresponding to the target sub-device and a second identifier corresponding to a target gateway associated with the target sub-device; A creation module, used to create a topology relationship chain between a target sub-device and a target gateway according to the first identifier and the second identifier, and update a current topology relationship diagram; A determination module, used to determine whether the target sub-device has been bound to other historical gateways except the target gateway; The notification module is used to generate a first topology relationship deletion instruction and send it to the historical gateway if the target sub-device has been bound to other historical gateways, so as to notify the historical gateway to delete the historical topology relationship chain currently associated with the target sub-device.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the network topology management method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: It comprises a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the network topology management method according to any one of claims 1 to 7.