A device management method and network device

Abstract

The embodiment of the present application provides a device management method and network device, which are applied to a first device in an ad hoc network. The method comprises the following steps: when the first device is a master device, a network support module of the first device receives a discovery request sent by a network support module of a second device, wherein the discovery request comprises target device information; the network support module of the first device sends a subsumption notification to the network support module of the second device, and sends a joining event to a network service module of the first device; the network service module of the first device sends first configuration information matched with the target device information to the network support module of the first device; the network support module of the first device sends the first configuration information to the network service module of the second device; and the network service module of the second device is configured by using the first configuration information. The technical scheme provided by the embodiment of the present application can solve the problem that a device cannot be on duty 24 hours a day, and realizes automatic subsumption and whole-network management of the device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a device management method and network device. Background Technology

[0002] To reduce the cost and improve the security of ad hoc networks, mobile applications (APPs) are often used to manage them. For users, ad hoc networks using mobile APPs are less expensive, but they cannot be maintained 24 / 7. Summary of the Invention

[0003] The purpose of this application is to provide a device management method and apparatus to solve the problem of not being able to monitor devices 24 / 7, and to achieve automatic device management and network-wide management. The specific technical solution is as follows:

[0004] In a first aspect, embodiments of this application provide a device management method applied to a first device in a self-organizing network, the method comprising:

[0005] When the first device is the master device, the network support module of the first device receives a discovery request sent by the network support module of the second device through the first tunnel between the first device and the network support module of the second device in the ad hoc network. The discovery request includes the target device information of the second device.

[0006] The network support module of the first device sends a management notification to the network support module of the second device through the first tunnel, and sends a join event to the network service module of the first device. The join event includes the target device information.

[0007] The network service module of the first device obtains first configuration information that matches the target device information and sends the first configuration information to the network support module of the first device.

[0008] The network support module of the first device sends the first configuration information to the network service module of the second device through a second tunnel, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification.

[0009] Secondly, embodiments of this application provide a network device, the network device comprising: a first network support module and a first network service module;

[0010] The first network support module is configured to receive a discovery request sent by the network support module of the second device through a first tunnel between the network device and the network support module of the second device in the self-organizing network when the network device is the master device of the self-organizing network. The discovery request includes target device information of the second device.

[0011] The first network support module is configured to send a management notification to the network support module of the second device through the first tunnel, and send a join event to the first network service module, wherein the join event includes the target device information;

[0012] The first network service module is used to obtain first configuration information that matches the target device information and send the first configuration information to the first network support module;

[0013] The first network support module is configured to send the first configuration information to the network service module of the second device through a second tunnel, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification.

[0014] Thirdly, embodiments of this application provide a network device including a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, which in turn cause the processor to perform any of the steps of the method provided in the first aspect.

[0015] Fourthly, embodiments of this application provide a machine-readable storage medium storing a computer program, which, when executed by a processor, implements any of the method steps described in the first aspect.

[0016] Fifthly, embodiments of this application provide a computer program that, when executed by a processor, implements any of the method steps described in the first aspect.

[0017] In the technical solution provided in this application embodiment, after a new device is connected to the network and powered on, automatic management and automatic synchronization configuration of the new device are achieved through the interaction between the network support module of the new device and the network support module of the main device, as well as the interaction between the network support module of the main device and the network service module, thus solving the problem of not being able to be on-network 24 / 7. Furthermore, since the main device manages all slave devices, such as the new device, user terminals can access the main device and manage all devices in the entire network after connecting to the network on any device, achieving whole-network management. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention and the prior art, the drawings used in the embodiments and the prior art are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0019] Figure 1 A schematic diagram of the architecture of a self-organizing network;

[0020] Figure 2a A schematic diagram of a cloud-free device management system provided in an embodiment of this application;

[0021] Figure 2b A schematic diagram of a cloud-based device management system provided in an embodiment of this application;

[0022] Figure 3 A schematic diagram of a three-layer architecture with network devices provided in an embodiment of this application;

[0023] Figure 4 A schematic diagram of three types of tunnels provided in the embodiments of this application;

[0024] Figure 5 This is a schematic diagram of a first type of device management method provided in an embodiment of this application;

[0025] Figure 6 This is a second flowchart illustrating the device management method provided in an embodiment of this application;

[0026] Figure 7 A signaling diagram for automatic management, configuration synchronization, and cloud migration provided in an embodiment of this application;

[0027] Figure 8 This is a third flowchart illustrating the device management method provided in the embodiments of this application;

[0028] Figure 9 This is a schematic diagram of a first type of interface access method provided in an embodiment of this application;

[0029] Figure 10 This is a second flowchart illustrating the interface access method provided in an embodiment of this application.

[0030] Figure 11 A signaling diagram for a slave device accessing a web page of a master device, provided in an embodiment of this application;

[0031] Figure 12 This is a schematic diagram of a first structure of a network device provided in an embodiment of this application;

[0032] Figure 13 This is a schematic diagram of a second structure of a network device provided in an embodiment of this application;

[0033] Figure 14 This is a schematic diagram of a third structure of a network device provided in an embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. Obviously, the described embodiments are merely some embodiments of this invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0035] A self-organizing network is a network that combines mobile communication and computer networks, and the information exchange in the network adopts the packet switching mechanism in computer networks.

[0036] Plug and play means that the device can be connected to the network immediately after being powered on.

[0037] In scenarios such as villa-style guesthouses, chain stores, business hotels, and government / enterprise offices, self-organizing networks are often used to build networks, such as... Figure 1 The diagram illustrates a self-organizing network architecture. Various access devices connect to the network via gateways or ACs (Access Controllers), while user terminals such as mobile phones and PCs (Personal Computers) connect to the network through these access devices. These access devices can be access points (APs), switches, and routers. APs are further divided into Fit APs and Fat APs. In the aforementioned self-organizing network scenario, due to the relatively small number of access devices, it belongs to a low-end, small-scale network.

[0038] Against the backdrop of societal digital transformation, competition in the low-end small form factor networking (SMN) market is intensifying. Network vendors have successively launched network management architectures supporting SMNs. These architectures, found in their respective network products, offer features such as automatic discovery of new access devices, unified management of all access devices within the network, and automatic configuration of new access devices. These features enhance usability through simplified setup, convenient management, and automated logic, bringing tangible benefits to non-professional users and gaining widespread market acceptance.

[0039] The low-end small-scale networking market is highly price-sensitive. To reduce the cost of self-organizing networks, public clouds and mobile applications (APPs) are often used to manage them. For users, self-organizing networks using public clouds and mobile APPs are less expensive. However, due to issues such as the reliability of public clouds themselves and the reliability of the network between the self-organizing network and the public cloud, the reliability of solutions using public clouds to manage self-organizing networks is poor. Furthermore, the public cloud can only be used after the local network is set up and operational, which limits the applicability of solutions using public clouds to manage self-organizing networks. Mobile APPs can avoid the aforementioned reliability issues, but they cannot be online 24 / 7.

[0040] To address the issue of the inability to maintain online monitoring 24 / 7 and to achieve automatic management of devices, this application provides a device management system. This device management system includes multiple devices, which may include, but are not limited to, FatAPs, FitAPs, switching devices, routers, gateways, and ACs.

[0041] To meet the need for reduced costs in ad hoc networks, the AC (Access Controller) can be used as a gateway in the device management system, or its functions can be integrated into network devices such as gateways, routers, or switches. Additionally, the AC can be connected to Fit APs or other managed APs to extend the coverage of the ad hoc network.

[0042] In a device management system, devices with high hardware configuration and performance, such as the aforementioned Fat APs, switching devices, routers, gateways, and ACs, need to assume the role of controllers and support the device management method provided in this application embodiment. This device management method will be described in detail later and will not be elaborated here. In this application embodiment, devices such as Fat APs, switching devices, and routers can all assume the role of controllers. Therefore, in this application embodiment, there is no need to set up wireless controllers such as gateways and ACs, and self-organizing networks of Fat APs and switching devices are supported, which can effectively reduce the cost of self-organizing networks.

[0043] For devices with lower hardware configuration and performance, such as the aforementioned Fit AP or other managed APs, supporting the management of devices with the aforementioned controller role can enable support for the device management method provided in the embodiments of this application.

[0044] The device management system provided in this application embodiment can adopt a cloud-free self-organizing network, such as... Figure 2a As shown, in this self-organizing network, apps, browsers, and other devices connect to the local network to manage the various devices within the network. These apps and browsers can be installed on devices such as mobile phones and personal computers, and the local network is the self-organizing network itself.

[0045] The device management system provided in this application embodiment can adopt a cloud-based self-organizing network, such as... Figure 2b As shown, in this self-organizing network, once the local network establishes a connection with the cloud, the APP can remotely operate the local network through the cloud, thereby managing each device in the self-organizing network.

[0046] In this embodiment of the application, the devices in the device management system may include three modules, such as... Figure 3 As shown, these are the network interaction module, network service module, and network support module. The following provides a detailed explanation of these modules.

[0047] (1) The network interaction module provides the user interface (UI) for user terminals and a data channel for communication between the front-end and back-end. The UI may include, but is not limited to, mobile browser pages, mobile APP pages, etc. The front-end refers to the network interaction module, and the back-end refers to the network service module.

[0048] The data channel for communication between the front-end and the back-end can adopt the SOAP (Simple Object Access Protocol) protocol framework, using a network configuration protocol interface (such as the netconf interface) as the message format to realize communication between the front-end and the back-end.

[0049] (2) The network service module is used to implement various service logics such as network-wide management and plug-and-play functionality. Here, the service logic may include global wireless service activation logic, global wired service activation logic, automatic cloud access logic for new devices joining the network, automatic VLAN (Virtual Local Area Network) adaptation logic for Ethernet ports, and automatic synchronization configuration logic, etc.

[0050] To facilitate the implementation of various business logics in the network service module, the network service module may include network service (Webserver) units and business processing units. The network service module can be associated with network configuration protocol interfaces and cloud pipelines to facilitate communication with network interaction modules, network support modules, and the cloud. For ease of description, the netconf interface will be used as an example for the network configuration protocol interface in the following explanations.

[0051] In this system, the Webserver unit receives SOAP messages from the frontend, and the netconf interface distributes these messages to the corresponding business processes for processing based on the actual business logic of the interface. This method can be used for data communication between the frontend, backend, and devices. Considering the high coupling between the Webserver unit and the business processing unit, in this embodiment, the Webserver unit, the business processing unit, and other business logic processing units can be placed together in the network service module.

[0052] The service processing unit handles plug-and-play automatic synchronization configuration, automatic cloud migration, global wireless service activation logic, Ethernet port VLAN automatic adaptation logic, global wired service activation logic, and other service logics. It also stores the service configuration of the entire self-organizing network and maintains service data.

[0053] Cloud pipelines enable communication between devices and the management cloud, while also supporting plug-and-play automatic cloud migration. A cloud pipeline establishes a connection between the network service modules of a network device and the cloud. The management cloud is the cloud service itself.

[0054] (3) The network support module is responsible for supporting the network architecture of the self-organizing network and is used to realize functions such as device role election, master-slave device relationship maintenance, network topology maintenance and data channel maintenance between devices.

[0055] To facilitate the implementation of various functions by the network support module, the network support module may include network architecture unit, AP management unit, and link management unit, etc.

[0056] The network architecture unit is responsible for functions such as automatic device discovery and networking, master device self-election and role determination, and automatic management of new devices. It provides a unified channel for service delivery and information acquisition for network service modules. The network architecture unit can also store and maintain master-slave information and topology relationships among network devices.

[0057] Once the device is powered on, the network architecture unit can initiate Layer 2 negotiation to determine its own role based on the current network environment. For example, if the network is still in the setup phase, the device participates in the election of the master device and determines its own working mode based on the election results, i.e., whether the device is a master device or a slave device. If the network is already in normal working order, i.e., the network has been set up, the device initiates the process of joining the network. The process of joining the network will be explained in detail later and will not be elaborated here.

[0058] The link management unit is responsible for reporting and collecting neighbor relationships so that the network architecture unit can draw the overall network topology. In this embodiment, the link management unit can be an LLDP (Link Layer Discovery Protocol) unit or other link protocol units, and there is no limitation on this.

[0059] The AP management unit is used to manage Fit APs and other managed APs.

[0060] The network service module and network support module within a device contain user-mode services and kernel-mode services. User-mode services can be implemented through IPC (Inter-Process Communication); kernel-mode services can be implemented through internal kernel interface calls. Figure 3 This only illustrates the services implemented in the network service module and network support module via IPC communication, and does not constitute a limitation. The service processing unit of the network service module focuses on maintaining service data, while the network architecture unit of the network support module focuses on maintaining data such as the management relationships between master and slave devices and network topology information.

[0061] To enable communication between devices, the network support module in this embodiment provides three types of tunnels for inter-device communication, such as... Figure 4 As shown:

[0062] (1) The first type of tunnel can be called a network architecture tunnel, such as Figure 4 The solid line shown.

[0063] Network architecture tunnels operate at the data link layer, primarily serving the network support module, specifically the network architecture unit within that module. These tunnels are used for tasks such as automatic discovery between master and slave devices, role election, maintenance of master-slave relationships, slave device joining responses, and master-slave device keep-alive.

[0064] Network architecture tunnels are built between the network support modules of different devices. When a slave device is managed by a master device, a network architecture tunnel is established between the slave and master devices and kept alive. The master and slave devices determine whether the other end is on the network based on the keep-alive status of the network architecture tunnel.

[0065] (2) The second type of tunnel can be called an application service tunnel, such as... Figure 4 The dashed lines shown.

[0066] Application service tunnels are built between the network support modules and network service modules of different devices. They are packaged upwards as a logical tunnel; that is, when facing the network service module of the local device, the application service tunnel is packaged as a logical tunnel, and the network service module calls the interface provided by the application service tunnel to send messages to other devices. Downwards, they reuse the common mechanisms of existing network devices; that is, when facing the target device to which data is being sent, the application service tunnel reuses the common mechanisms of existing network devices, using methods such as SOAP to send messages.

[0067] For example, before sending data, the network service module calls the application service tunnel interface to send the message to the network architecture unit in the network support module. The network architecture unit converts the message into a SOAP message and sends it to the target device. The target device is the receiving end. The Webserver unit in the network service module of the receiving end receives the SOAP message and forwards it to the corresponding service processing unit for processing through the netconf interface.

[0068] In this embodiment, the application service tunnel is actually a logical link. Therefore, devices do not need to maintain a specific physical tunnel for a long time, and SOAP does not require maintaining a long-term connection, reducing link maintenance costs. Furthermore, in this embodiment, communication between devices reuses common network device mechanisms, significantly reducing the implementation cost of the technical solution provided in this embodiment.

[0069] (3) The third type of tunnel can be called a wireless AP management tunnel, such as... Figure 4 The dotted line shown.

[0070] The wireless AP management tunnel can reuse the existing AP management tunnel of the wireless product. This ensures that resource-constrained Fit APs or other managed APs can support the technical solutions provided in the embodiments of this application without incurring additional performance overhead.

[0071] The foregoing Figure 3 The network interaction module, network service module, and network support module shown constitute a three-layer architecture for an ad hoc network. Figure 4 The first, second, and third types of tunnels shown are the three types of tunnels in an ad hoc network. Based on this three-layer architecture and the device management system designed for these three types of tunnels, this application embodiment provides a device management method, such as... Figure 5 As shown, this is the first device applied in a self-organizing network. When the first device is the master device, it executes steps S51-S54.

[0072] In some embodiments, the network support module of the first device in the ad hoc network negotiates with the network support modules of other devices in the ad hoc network through a sixth tunnel to elect and determine the roles of the first device and other devices in the ad hoc network, namely, master device or slave device. The sixth tunnel is the tunnel between the network support module of the first device and the network support modules of other devices; that is, the sixth tunnel is the first type of tunnel mentioned above, namely, the network architecture tunnel.

[0073] In this embodiment, a master device is determined through an election process. This master device manages the devices in the network, addressing usability issues in low-end small networks, such as automatic device discovery and management, plug-and-play functionality for new devices, and single-point network management. It also improves setup efficiency and the user experience of logging into the network management system. This effectively solves problems caused by the failure of fixed network management devices, which prevents automatic discovery and management, and ensures plug-and-play functionality for new devices.

[0074] like Figure 5 As shown, the above-mentioned equipment management method includes:

[0075] In step S51, the network support module of the first device receives a discovery request sent by the network support module of the second device through the first tunnel between the first device and the network support module of the second device in the ad hoc network. The discovery request includes the target device information of the second device.

[0076] In this embodiment, the second device is a newly connected network device in the ad hoc network, and the first tunnel is the tunnel between the network support module of the first device and the network support module of the second device; that is, the first tunnel is the first type of tunnel mentioned above, namely, a network architecture tunnel. The device information of the second device is the target device information. The device information includes device type, serial number, MAC (Media Access Control) address, etc.

[0077] After the second device powers on and connects to the ad hoc network, its network support module sends a discovery request, which includes target device information, to the network support module of the first device through the first tunnel. The network support module of the first device then receives the discovery request from the network support module of the second device through the first tunnel.

[0078] In combination with the above Figure 3 In the self-organizing network architecture shown, step S51 can be as follows: the network architecture unit in the network support module of the second device sends a discovery request to the network support module of the first device through the first tunnel; the network architecture unit in the network support module of the first device receives the discovery request sent by the network support module of the second device through the first tunnel.

[0079] In step S52, the network support module of the first device sends a management notification to the network support module of the second device through the first tunnel, and sends a join event to the network service module of the first device. The join event includes target device information.

[0080] After receiving the discovery request, the network support module of the first device sends a management notification to the network support module of the second device through the first tunnel, completing the automatic management of the second device. Thus, the second device successfully joins the ad hoc network, and the network support modules of both devices update network data such as master-slave information and topology relationships.

[0081] In addition, after the second device is managed, the network support module of the first device sends an join event to the network service module of the first device to facilitate the subsequent synchronization configuration to the second device.

[0082] In combination with the above Figure 3 In the self-organizing network architecture shown, step S52 can be as follows: the network architecture unit in the network support module of the first device sends a management notification to the network support module of the second device through the first tunnel; the network architecture unit in the network support module of the first device reports the joining event to the service processing unit in the network service module of the first device.

[0083] In step S53, the network service module of the first device obtains the first configuration information that matches the target device information and sends the first configuration information to the network support module of the first device.

[0084] After receiving the join event, the network service module of the first device extracts the target device information from the join event, and then obtains configuration information matching the target device information, such as the first configuration information. The network service module of the first device sends the first configuration information to the network support module of the first device.

[0085] In some embodiments, the first device stores configuration information for various device types. In this case, the process in step S53 where the network service module of the first device obtains the first configuration information that matches the target device information can be: the network service module of the first device obtains the first configuration information that matches the device type in the target device information.

[0086] In combination with the above Figure 3 In the self-organizing network architecture shown, step S53 can be as follows: After receiving a join event, the service processing unit in the network service module of the first device extracts the target device information from the join event, and then obtains the first configuration information that matches the target device information. The service processing unit in the network service module of the first device sends the first configuration information to the network architecture unit in the network support module of the first device.

[0087] In step S54, the network support module of the first device sends first configuration information to the network service module of the second device through the second tunnel between the first device and the network service module of the second device, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification.

[0088] In this embodiment of the application, the second tunnel is the tunnel between the network support module of the first device and the network service module of the second device. That is, the second tunnel is the second type of tunnel mentioned above, namely the application service tunnel.

[0089] After receiving the first configuration information, the network support module of the first device sends the first configuration information to the network service module of the second device through the second tunnel. When the network support module of the second device receives the management notification, the network service module of the second device uses the received first configuration information to perform configuration, thus realizing the automatic synchronous configuration of the second device.

[0090] In combination with the above Figure 3 In the self-organizing network architecture shown, step S54 can be as follows: the network architecture unit in the network support module of the first device sends the first configuration information to the network service module of the second device through the second tunnel; the service processing unit in the network service module of the second device uses the first configuration information to perform configuration.

[0091] In the technical solution provided in this application embodiment, after a new device is connected to the network and powered on, automatic management and automatic synchronization configuration of the new device are achieved through the interaction between the network support module of the new device and the network support module of the main device, as well as the interaction between the network support module of the main device and the network service module, thus solving the problem of not being able to be on-network 24 / 7. Furthermore, since the main device manages all slave devices, such as the new device, user terminals can access the main device after connecting to the network on any device, enabling them to manage the entire network and all devices, thus achieving whole-network management.

[0092] In addition, the new equipment can be automatically managed and automatically synchronized for configuration, providing users with great convenience for expanding the network and replacing spare parts. At the same time, because the new equipment can be added to the network as soon as it is plug and play, there is no need to wait for all network devices to complete the networking, wiring, and power-on during network deployment, providing greater flexibility for network deployment.

[0093] In some embodiments, the step of the network service module of the first device sending the first configuration information to the network support module of the first device in step S53 above can be: the network service module of the first device calls the interface of the second tunnel to send the first configuration information to the network support module of the first device.

[0094] In this case, step S54 above, where the network support module of the first device sends the first configuration information to the network service module of the second device through the second tunnel between the first device and the network service module of the second device, can be implemented as follows: the network support module of the first device receives the first configuration information through the interface of the second tunnel between the first device and the network service module of the second device; converts the first configuration information into a target message of a preset protocol, and sends the target message to the network service module of the second device. The preset protocol can be a common protocol between network devices, such as SOAP.

[0095] When the network support module of the second device receives the management notification, the network service module of the second device converts the target message into first configuration information and uses the first configuration information for configuration.

[0096] In combination with the above Figure 3 In the illustrated self-organizing network architecture, the service processing unit in the network service module of the first device calls the interface of the second tunnel to send first configuration information to the network support module of the first device. The network architecture unit of the network support module of the first device receives the first configuration information through the interface of the second tunnel; it converts the first configuration information into a SOAP target message and sends the target message to the network service module of the second device. The Webserver unit in the network service module of the second device receives the target message and forwards it to the service processing unit for processing through the netconf interface.

[0097] In the technical solution provided in this application embodiment, when the network support module of the first device communicates with the network service module of the second device, an application service tunnel is used. The application service tunnel is a logical link, and the devices do not need to maintain a specific physical tunnel, reducing link maintenance costs. Furthermore, in this application embodiment, when the devices communicate, the common mechanisms of network devices are reused, greatly reducing the implementation cost of the technical solution provided in this application embodiment.

[0098] In some embodiments, a device management method is also provided, such as Figure 6 As shown, steps S61-S65 may be included. Steps S61-S64 are the same as steps S51-S54 described above, and will not be repeated here.

[0099] In step S65, the network service module of the first device sends a registration event to the cloud through the cloud pipeline. The registration event includes target device information so that the cloud can register the second device using the target device information. After the second device completes registration and receives the connection request sent by the second device through the cloud pipeline, a connection is established with the second device. The connection request is a request sent periodically by the second device.

[0100] In this embodiment, the first device establishes a connection with the cloud via a cloud pipeline. The network service module of the first device sends a registration event to the cloud via the cloud pipeline. After receiving the registration event, the cloud extracts the target device information from the registration event and uses the target device information to register the second device. In this way, the first device completes the registration of the second device to the cloud.

[0101] The first device does not need to notify the second device. The network service module of the second device periodically sends connection requests to the cloud through the cloud pipeline to attempt to establish a connection with the cloud.

[0102] Before the second device is registered with the cloud, the cloud will not establish a connection with the second device even if it receives a connection request. After the second device is registered with the cloud, the cloud will establish a connection with the second device upon receiving a connection request.

[0103] In combination with the above Figure 3 In the self-organizing network architecture shown, step S65 can be as follows: the service processing unit in the network service module of the first device sends a registration event to the cloud through the cloud pipeline; the service processing unit in the network service module of the second device periodically sends connection requests to the cloud through the cloud pipeline; after registering the second device, the cloud establishes a connection with the second device through the cloud pipeline according to the connection request.

[0104] In the technical solution provided in this application embodiment, the master device registers the slave device to the cloud. The slave device periodically attempts to establish a connection with the cloud, and automatically establishes a connection with the cloud after the master device registers the slave device to the cloud, thereby realizing automatic cloud access for the slave device and enabling remote operation of the master and slave devices in the ad hoc network through the cloud.

[0105] The following is combined Figure 7 The signaling diagrams shown below, illustrating the automatic management, configuration synchronization, and cloud migration, explain the device management method provided in the embodiments of this application. Figure 7 In this embodiment, the network service module of the new device (such as the second device mentioned above) includes a service processing unit 12, the network support module of the new device includes a network architecture unit 13, the network service module of the main device (such as the first device mentioned above) includes a service processing unit 22, and the network support module of the main device includes a network architecture unit 23. In this application embodiment, the new device may refer to the second device mentioned above, and the main device may refer to the first device mentioned above. The network support module and network service module of the new device and the main device may also include other units, as described above. Figure 3 As shown, no restrictions are imposed on this.

[0106] In step S71, network architecture unit 13 sends a discovery request to network architecture unit 23.

[0107] In step S72, network architecture unit 23 sends a management notification to network architecture unit 13.

[0108] In step S73, the network architecture unit 23 sends an add event to the service processing unit 22. The add event includes the device information 1 of the new device.

[0109] In step S74, the service processing unit 22 obtains the corresponding configuration information 1 based on the device type in the device information 1.

[0110] In step S75, the service processing unit 22 calls the interface of the application service tunnel to send configuration information 1 to the network architecture unit 23.

[0111] In step S76, network architecture unit 23 converts configuration information 1 into SOAP message 1.

[0112] In step S77, the network architecture unit 23 sends SOAP message 1 to the service processing unit 12.

[0113] In step S78, the service processing unit 12 will activate the configuration, that is, configure it using the configuration information 1 in SOAP message 1.

[0114] In step S79, the business processing unit 22 sends registration event 1 to the cloud via the cloud pipeline. Registration event 1 includes device information 1.

[0115] In step S710, the business processing unit 12 periodically sends connection requests to the cloud to achieve automatic connection with the cloud.

[0116] The technical solutions provided in this application do not distinguish between device types; Fat APs, routers, and switching devices also support the functions of a main device. Therefore, even when only Fat APs, routers, and switching devices are present in the network, plug-and-play functionality is still possible.

[0117] The above steps S71-S710 are described in a relatively simple manner; for details, please refer to the above descriptions. Figure 5 and Figure 6 Related descriptions for some parts.

[0118] In some embodiments, an automatic inclusion function can be configured on the master device. Taking the first device as the master device as an example, the first device can turn the automatic inclusion function on and off, that is, control the enabling of the automatic inclusion function to flexibly control the automatic inclusion of new devices. Specifically, it can be as follows:

[0119] Upon receiving the discovery request, if the network support module of the first device has enabled the automatic management function, i.e., the automatic management function is turned on, the network architecture unit in the network support module of the first device responds to the discovery request, i.e., sends a management notification to the network support module of the second device and sends an join event to the network service module of the first device.

[0120] If the network support module of the first device does not enable the automatic management function, that is, disables the automatic management function, the network architecture unit in the network support module of the first device will refuse to respond to the discovery request, that is, it will not send a management notification to the network support module of the second device, and will not send an join event to the network service module of the first device.

[0121] In the technical solution provided in this application embodiment, the main device can restrict the accidental addition of devices from outside the network by switching on the automatic inclusion function, thereby solving the problem of network information security being compromised due to the accidental addition of devices from outside the network.

[0122] In some embodiments, a whitelist for management can also be configured on the master device. The whitelist includes device information that allows devices to access the ad hoc network.

[0123] Taking the first device as the main device as an example. In this embodiment, the first device can record a device list, which includes device information of each device that has sent a discovery request. The user terminal views the device information in the recorded device list through the network interaction module of the main device and adds some or all of the device information in the device list to the whitelist. In this embodiment, the user can also directly add or compile device information in the whitelist manually, without limitation.

[0124] If the network architecture unit in the network support module of the first device detects that the whitelist does not include the target device information when the automatic management function is not enabled in the network support module of the first device, the network architecture unit in the network support module of the first device will refuse to respond to the discovery request.

[0125] If the network architecture unit in the network support module of the first device detects that the whitelist includes the target device information, the network architecture unit in the network support module of the first device responds to the discovery request, that is, sends a management notification to the network support module of the second device and sends an add event to the network service module of the first device.

[0126] In the technical solution provided in this application embodiment, the main device can restrict the accidental addition of devices from outside the network by switching on the automatic management function, thus solving the problem of network information security damage caused by the accidental addition of devices from outside the network. The management whitelist allows network administrators to authorize the network to allow specified devices to join at any time, regardless of whether the new device is already plugged into the network or powered on. The combination of the automatic management function and the management whitelist can further improve the flexibility and security of plug-and-play devices in the network.

[0127] In some embodiments, after the first device manages the second device, the second device becomes a slave device. In this case, embodiments of this application also provide a device management method, such as... Figure 8 As shown, the steps may include the following.

[0128] In step S81, the network service module of the first device sends the target page data provided by the network interaction module of the first device to the user terminal, so that the user terminal can display the target page data and operate on the target page data to obtain the second configuration information for the second device.

[0129] In this embodiment, the user terminal can access the network from any device, whether it is a slave or master device. For example, a PC can be plugged into any port of any switch or any panel AP, and a mobile phone can access the network from within the coverage area of ​​any AP. Since the master device manages all slave devices, the user terminal can access the network interaction module of the master device and manage all devices in the entire network after accessing the network from any device.

[0130] In this embodiment, the user terminal accesses the network interaction module of the first device. The service processing unit in the network service module of the first device obtains the page data, i.e., the target page data, provided by the network interaction module of the first device, and sends the target page data to the user terminal. The user terminal displays the target page data, enabling the user terminal to access the web page of the first device. The user terminal operates on the target page data to obtain configuration information for the second device, such as second configuration information.

[0131] In step S82, the network service module of the first device receives the second configuration information sent by the user terminal and sends the second configuration information to the network support module of the first device.

[0132] The service processing unit in the network service module of the first device receives the second configuration information sent by the user terminal, performs service identification and calculation on the second configuration information, and then sends the second configuration information to the network support module of the first device.

[0133] In one example, the second configuration information is a SOAP message. The Webserver unit in the network service module of the first device receives this SOAP message and forwards it to the service processing unit for processing through the netconf interface. The service processing unit in the network service module of the first device calls the interface of the application service tunnel to send the second configuration information to the network architecture unit in the network support module of the first device.

[0134] In step S83, the network support module of the first device sends second configuration information to the network service module of the second device through the second tunnel, so that the network service module of the second device can use the second configuration information for configuration.

[0135] After receiving the second configuration information, the network architecture unit in the network support module of the first device sends the second configuration information to the service processing unit in the network service module of the second device through the second tunnel. The service processing unit in the network service module of the second device uses the received second configuration information to perform configuration, realizing synchronous configuration of the second device. In addition, the service processing unit in the network service module of the second device manages the entire network through the first device, that is, it realizes one-point login management of the entire network, improving the usability of the ad hoc network.

[0136] In some embodiments, the step of the network service module of the first device sending the second configuration information to the network support module of the first device in step S82 above can be: the network service module of the first device calls the interface of the second tunnel to send the second configuration information to the network support module of the first device.

[0137] In this case, step S83 above, where the network support module of the first device sends the second configuration information to the network service module of the second device through the second tunnel, can be modified as follows: the network support module of the first device receives the second configuration information through the interface of the second tunnel; converts the second configuration information into a target message of a preset protocol, and sends the target message to the network service module of the second device. The preset protocol can be a common protocol between network devices, such as SOAP. The network service module of the second device converts the target message into second configuration information and uses the second configuration information for configuration.

[0138] In combination with the above Figure 3In the illustrated ad hoc network architecture, the service processing unit in the network service module of the first device calls the interface of the second tunnel to send second configuration information to the network support module of the first device. The network architecture unit in the network support module of the first device receives the second configuration information through the interface of the second tunnel; it converts the second configuration information into a SOAP target message and sends the target message to the network service module of the second device. The webserver unit in the network service module of the second device receives the target message and forwards it to the service processing unit for processing through the netconf interface.

[0139] In the technical solution provided in this application embodiment, when the network support module of the first device communicates with the network service module of the second device, an application service tunnel is used. The application service tunnel is a logical link, and the devices do not need to maintain a specific physical tunnel, reducing link maintenance costs. Furthermore, in this application embodiment, when the devices communicate, the common mechanisms of network devices are reused, greatly reducing the implementation cost of the technical solution provided in this application embodiment.

[0140] In some embodiments, a method for accessing an interface is also provided, such as Figure 9 As shown, it may include the following steps:

[0141] Step S91: The network service module of the first device receives an access request sent by the user terminal. The access request includes the target URL (Uniform Resource Locator).

[0142] The user terminal sends an access request to the first device. The service processing unit in the network service module of the first device receives the access request sent by the user terminal through the Webserver unit. The access request can be a SOAP message.

[0143] In this embodiment, the access request can be a request from a user terminal sent by the network support module of a third device in the ad hoc network through a third tunnel between the network support module of the first device and the network support module of the third device. The third tunnel is the tunnel between the network support module of the first device and the network support module of the third device; that is, the third tunnel is the aforementioned third type of tunnel, namely, the wireless AP management tunnel. In this embodiment, the third device is a managed device, such as the aforementioned Fit AP or other managed APs.

[0144] Access requests can also be requests from user terminals sent from the cloud via cloud pipelines.

[0145] In this embodiment, taking an APP as the user terminal as an example, the APP can implement an HTML5 architecture. Through the data channel of APP <--> cloud <--> cloud pipeline of the first device <--> webserver unit of the first device, the APP sends an access request to the first device, thereby pulling and displaying the web page of the first device, thus constructing a data channel for the network interaction module between the user terminal and the first device. Subsequent interactions between the user terminal and the network service module and network support module of the first device, as well as the synchronization process of information such as the first configuration information and the second configuration information across devices, can be found in the above. Figures 5-8 Related descriptions for some parts.

[0146] Access requests can also be sent directly from the user terminal to the first device. For example, if the user terminal accesses the network on the first device, the user terminal can send an access request directly to the first device.

[0147] In step S92, when the target URL is the domain name of the self-organizing network, the network service module of the first device obtains the target page data provided by the network interaction module of the first device.

[0148] The service processing unit in the network service module of the first device recognizes that the target URL in the access request is the domain name of the ad hoc network, and obtains the page data provided by the network interaction module of the first device, namely the target page data.

[0149] In step S93, the network service module of the first device carries the target page data in the access response of the access request and sends the access response back to the user terminal.

[0150] In this embodiment, the service processing unit of the network service module handles business logic such as plug-and-play automatic synchronization configuration, automatic cloud migration, global wireless service activation logic, Ethernet port VLAN automatic adaptation logic, and global wired service activation logic. After obtaining the target page data, the service processing unit in the network service module of the first device carries the target page data in the access response corresponding to the access request and sends the access response back to the user terminal. The access response can be a SOAP message.

[0151] In the technical solution provided in this application embodiment, step S81 is implemented using steps S91-S93. Network management requires user terminals to access the main device. Taking browser access to the main device as an example, accessing a local web page via a traditional IP address is unfriendly to most consumer market users. In this application embodiment, the user terminal only needs to access the network on any AP and use a mobile phone or other user terminal to access a specified domain name to open the main device's local web page and manage all devices in the network. This achieves the effect of "one-point login for network management," improving the usability of ad hoc networks.

[0152] In some embodiments, a method for accessing an interface is also provided, such as Figure 10 As shown, it may include the following steps:

[0153] In step S101, the network service module of the first device receives a page request sent by the network support module of the fourth device of the ad hoc network through the fourth tunnel between the network service module of the first device and the network service module of the first device. The page request is a request sent by the network service module of the fourth device to the first device after receiving an access request from the user terminal. The target URL included in the access request is the domain name of the ad hoc network.

[0154] The fourth tunnel is the tunnel between the network support module of the fourth device and the network service module of the first device. In other words, the fourth tunnel is the second type of tunnel mentioned above, namely the application service tunnel.

[0155] The fourth device can be configured with DNS (Domain Name System) hijacking and web proxy functions.

[0156] The Webserver unit in the network service module of the fourth device receives access requests from user terminals and forwards them to the service processing unit. The service processing unit uses DNS hijacking to identify the target URL in the access request as the domain name of the ad hoc network, and then sends a page request to the network architecture unit in the network support module of the fourth device. The network architecture unit in the network support module of the fourth device then sends the page request to the network service module of the first device through the fourth tunnel.

[0157] In step S102, the network service module of the first device obtains the target page data from the network interaction module of the first device according to the page request; and sends the target page data to the network service module of the fourth device through the fifth tunnel between the network support module of the first device and the network service module of the fourth device, so that the network service module of the fourth device carries the target page data in the access response of the access request and feeds back the access response to the user terminal.

[0158] The fifth tunnel is the tunnel between the network support module of the first device and the network service module of the fourth device. In other words, the fifth tunnel is the second type of tunnel mentioned above, namely the application service tunnel.

[0159] After receiving a page request from the fourth device, the service processing unit in the network service module of the first device retrieves the target page data, including the HTML file, static resources, and other data, from the network interaction module of the first device. This target page data is then sent to the network support module of the first device. The network architecture unit in the network support module of the first device returns the target page data to the network service module of the fourth device through a fifth tunnel. The service processing unit in the network service module of the fourth device then integrates the target page data and returns it to the user terminal. This achieves the effect of accessing the main device's web interface for network management via a domain name.

[0160] In the technical solution provided in this application embodiment, step S81 is implemented using the above steps S101-S102. Network-wide management requires user terminals to access the main device. Taking browser access to the main device as an example, traditional IP address access to local web pages is unfriendly to most consumer market users. In this application embodiment, the user terminal only needs to access the network on any AP and use a mobile phone or other user terminal to access the specified domain name to open the main device's local web page and manage all devices in the network, thus achieving the effect of "one-point login for network-wide management".

[0161] For many home routers, DNS hijacking is often used to enable domain name login to local web pages. However, traditional DNS hijacking has a problem: wireless routers are mostly single-unit devices, acting as DHCP (Dynamic Host Configuration Protocol) servers themselves. Their own IP addresses generally don't change, while the master device in a self-organizing network may be elected and not necessarily the device hosting the DHCP service, and its IP address may change. Once the IP address corresponding to a domain name changes, the browser may not be able to promptly re-initiate a DNS request (i.e., access request) to obtain the new IP address corresponding to the domain name, resulting in the page becoming inaccessible.

[0162] In addition, another approach is to embed pages from other devices within the local web page. However, embedding pages can lead to cluttered pages, limited embedding scope, and poor user-friendliness.

[0163] This application's embodiments optimize the method of network-wide management, using DNS hijacking and web proxy for each device, which can reduce the problem of domain name inaccessibility caused by changes in the main device's IP address.

[0164] First, the device connected to the user terminal uses DNS hijacking, but instead of returning the IP address of the main device where the actual page resides, it returns the IP address of the device itself. This is because if the access point (AP) or switch connected to the user terminal fails, the user terminal will disconnect, and the device will likely be reassigned to its previously used IP address after it recovers. However, if the main device fails, according to the device role election mechanism described in this application, a secondary device will be promoted to the main device, and the main device's IP address will inevitably change. Therefore, the technical solution provided in this application reduces the probability of the IP address corresponding to the domain name changing, and reduces the probability that the user terminal cannot access the main device's page through the domain name.

[0165] Secondly, a web proxy function is added to both the master and slave devices. When a user accesses a local web page via a domain name, the slave device, such as an AP or switch, receives the access request. Recognizing the URL as the domain name of the self-organizing network, it sends the same page request to the master device's network service module via its network support module. Upon receiving the page request from the slave device, the master device's network service module returns the target page data to the slave device's network service module via its network support module. The slave device then integrates this target page data from the master device and returns it to the user terminal. This achieves the effect of managing the entire network by accessing the master device's web page via a domain name.

[0166] The following is combined Figure 11 The signaling diagram shown illustrates the interface access method provided in the embodiments of this application for accessing the web page of the slave device. Figure 11 In this embodiment, the network service module of the slave device includes a Webserver unit 31 and a service processing unit 32; the network support module of the slave device includes a network architecture unit 33; the network service module of the master device includes a service processing unit 41; the network support module of the master device includes a network architecture unit 42; and the network interaction module of the master device includes a local web 43. In this embodiment, the slave device can refer to the fourth device described above, and the master device can refer to the first device described above. The network support module, network service module, and network interaction module of the slave and master devices may also include other units, as described above. Figure 3 As shown, no restrictions are imposed on this.

[0167] In step S111, after the slave device is managed, the network architecture unit 33 configures the DNS hijacking function in the service processing unit 32, and configures the domain name to the slave device's own IP address.

[0168] In step S112, the Webserver unit 31 receives the access request sent by the user terminal.

[0169] In step S113, the Webserver unit 31 sends an access request to the business processing unit 32.

[0170] In step S114, the service processing unit 32 calls the interface of the application service tunnel to send a page request to the network architecture unit 33.

[0171] In step S115, network architecture unit 33 converts the page request into SOAP message 2.

[0172] In step S116, the network architecture unit 33 sends SOAP message 2 to the service processing unit 41.

[0173] In step S117, the business processing unit 41 obtains page data 1 from the local web 43 based on SOAP message 2.

[0174] In step S118, the service processing unit 41 calls the interface of the application service tunnel to send page data 1 to the network architecture unit 42.

[0175] In step S119, network architecture unit 42 converts page data 1 into SOAP message 3.

[0176] In step S1110, the network architecture unit 42 sends SOAP message 3 to the service processing unit 32.

[0177] In step S1111, the business processing unit 32 sends the page data 1 corresponding to SOAP message 3 to the Webserver unit 31.

[0178] In step S1112, the Webserver unit 31 sends page data 1 back to the user terminal.

[0179] The above steps S111-S1112 are described in a relatively simple way; for details, please refer to the above descriptions. Figure 5 and Figure 10 Related descriptions for some parts.

[0180] Corresponding to the above-described device management method, this application also provides a network device, such as... Figure 12 As shown, the network device includes: a first network support module 121 and a first network service module 122.

[0181] The first network support module 121 is used to receive a discovery request sent by the network support module of the second device through a first tunnel between the network device and the network support module of the second device in the self-organizing network when the network device is the master device of the self-organizing network. The discovery request includes the target device information of the second device.

[0182] The first network support module 121 is used to send a management notification to the network support module of the second device through the first tunnel, and to send a join event to the first network service module. The join event includes target device information.

[0183] The first network service module 122 is used to obtain first configuration information that matches the target device information and send the first configuration information to the first network support module.

[0184] The first network support module 121 is used to send first configuration information to the network service module of the second device through a second tunnel, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification.

[0185] In some embodiments, the first network service module 122 is specifically used to call the interface of the second tunnel to send first configuration information to the first network support module;

[0186] The first network support module 121 is specifically used to receive first configuration information through the interface of the second tunnel between the network service module of the second device and the network service module of the second device; convert the first configuration information into a target message of a preset protocol and send the target message to the network service module of the second device, so that when the network support module of the second device receives the management notification, the network service module of the second device converts the target message into the first configuration information and uses the first configuration information for configuration.

[0187] In some embodiments, the default protocol may be SOAP.

[0188] In some embodiments, the first network service module 122 can also be used to send a registration event to the cloud via a cloud pipeline after the first network support module sends the first configuration information to the network service module of the second device. The registration event includes target device information so that the cloud can register the second device using the target device information. After the second device completes registration and receives the connection request sent by the second device through the cloud pipeline, a connection is established with the second device. The connection request is a request sent periodically by the second device, and the cloud pipeline is the connection established between the network service module of the first device and the cloud.

[0189] In some embodiments, the first network support module 121 can also be used for:

[0190] Upon receiving the discovery request, if the automatic management function has been enabled, a management notification is sent to the network support module of the second device, and an add event is sent to the first network service module.

[0191] If automatic management is not enabled, the discovery request will be rejected.

[0192] In some embodiments, the first network support module 121 can also be used for:

[0193] When the automatic management function is not enabled, if the management whitelist does not include the target device information, the discovery request will be rejected. The management whitelist includes device information of devices that are allowed to access the ad hoc network.

[0194] If the whitelist includes the target device information, a management notification is sent to the network support module of the second device, and an add event is sent to the first network service module.

[0195] In some embodiments, the network device may further include: a first network interaction module 123, such as Figure 13 As shown;

[0196] The first network service module 122 can also be used to send target page data provided by the first network interaction module 123 to the user terminal, so that the user terminal can display the target page data and operate on the target page data to obtain the second configuration information for the second device.

[0197] The first network service module 122 can also be used to receive second configuration information sent by the user terminal and send the second configuration information to the first network support module.

[0198] The first network support module 121 can also be used to send second configuration information to the network service module of the second device through the second tunnel, so that the network service module of the second device can use the second configuration information for configuration.

[0199] In some embodiments, the first network service module 122 may be specifically used for:

[0200] Receive access requests sent by user terminals, including the target URL;

[0201] When the target URL is the domain name of the self-organizing network, obtain the target page data provided by the first network interaction module 123;

[0202] The target page data is carried in the access response of the access request, and the access response is sent back to the user terminal.

[0203] In some embodiments, the access request may be a request sent from a user terminal by the network support module of a third device in the ad hoc network through a third tunnel with the first network support module; or,

[0204] Access requests can be requests sent from user terminals and sent from the cloud via cloud pipelines.

[0205] In some embodiments, the first network service module 122 may be specifically used for:

[0206] The network support module of the fourth device in the self-organizing network receives a page request sent by the fourth tunnel between itself and the first network service module. The page request is a request sent by the network service module of the fourth device to the network device after receiving an access request from the user terminal. The target URL included in the access request is the domain name of the self-organizing network.

[0207] According to the page request, the target page data is obtained from the first network interaction module 123; the target page data is sent to the network service module of the fourth device through the fifth tunnel between the first network support module and the network service module of the fourth device, so that the network service module of the fourth device carries the target page data in the access response of the access request and feeds back the access response to the user terminal.

[0208] In some embodiments, the first network support module 121 can also be used to perform Layer 2 negotiation with the network support modules of other devices through a sixth tunnel between the network support modules of other devices to determine the roles of network devices and other devices in the ad hoc network, with the role being a master device or a slave device.

[0209] In the technical solution provided in this application embodiment, after a new device is connected to the network and powered on, automatic management and automatic synchronization configuration of the new device are achieved through the interaction between the network support module of the new device and the network support module of the main device, as well as the interaction between the network support module of the main device and the network service module, thus solving the problem of not being able to be on-network 24 / 7. Furthermore, since the main device manages all slave devices, such as the new device, user terminals can access the main device and manage all devices in the entire network after connecting to the network on any device, achieving whole-network management.

[0210] This application also provides a network device, such as... Figure 14 As shown, it includes a processor 141 and a machine-readable storage medium 142, the machine-readable storage medium 142 storing machine-executable instructions that can be executed by the processor 141, the processor 141 being prompted by the machine-executable instructions to: implement Figures 5-11 The method steps shown in any embodiment.

[0211] In this embodiment, the network support module, network service module, and network interaction module can be implemented by machine-executable programs or instructions. The processor 141 executes the corresponding machine-executable programs or instructions to realize the functions of the network support module, network service module, and network interaction module, thereby achieving… Figures 5-11 The method steps shown in any embodiment.

[0212] This application also provides a machine-readable storage medium storing a computer program, which is implemented when executed by a processor. Figures 5-11 The method steps shown in any embodiment.

[0213] This application also provides a computer program that, when executed by a processor, implements... Figures 5-11 The method steps shown in any embodiment.

[0214] The aforementioned machine-readable storage medium may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the machine-readable storage medium may also be at least one storage device located remotely from the aforementioned processor.

[0215] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0216] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0217] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0218] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the network device, machine-readable storage medium, and computer program embodiments are basically similar to the method embodiments, and therefore the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0219] The above description is merely a preferred embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this disclosure are included within the scope of protection of this disclosure.

Claims

1. A method for managing equipment, characterized in that, The method, applied to a first device in a self-organizing network, includes: When the first device is the master device, the network support module of the first device receives a discovery request sent by the network support module of the second device through a first tunnel between the first device and the network support module of the second device in the ad hoc network. The discovery request includes the target device information of the second device. The first tunnel is a network architecture tunnel. The network support module of the first device sends a management notification to the network support module of the second device through the first tunnel, and sends a join event to the network service module of the first device. The join event includes the target device information. The network service module of the first device obtains first configuration information that matches the target device information and sends the first configuration information to the network support module of the first device. The network support module of the first device sends the first configuration information to the network service module of the second device through a second tunnel, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification. The second tunnel is an application service tunnel.

2. The method according to claim 1, characterized in that, The step of the network service module of the first device sending the first configuration information to the network support module of the first device includes: The network service module of the first device calls the interface of the second tunnel to send the first configuration information to the network support module of the first device; The step of the network support module of the first device sending the first configuration information to the network service module of the second device through the second tunnel includes: The network support module of the first device receives the first configuration information through the interface of the second tunnel between the network service module of the second device; it converts the first configuration information into a target message of a preset protocol and sends the target message to the network service module of the second device, so that when the network support module of the second device receives the management notification, the network service module of the second device converts the target message into the first configuration information and uses the first configuration information for configuration.

3. The method according to claim 2, characterized in that, The preset protocol is the Simple Object Access Protocol.

4. The method according to claim 1, characterized in that, After the network support module of the first device sends the first configuration information to the network service module of the second device, the method further includes: The network service module of the first device sends a registration event to the cloud through the cloud pipeline. The registration event includes the target device information, so that the cloud can register the second device using the target device information. After the second device completes the registration and receives the connection request sent by the second device through the cloud pipeline, the cloud establishes a connection with the second device. The connection request is a request sent periodically by the second device. The cloud pipeline is the connection established between the network service module of the first device and the cloud.

5. The method according to claim 1, characterized in that, After receiving the discovery request, the method further includes: If the automatic management function has been enabled, the network support module of the first device performs the steps of sending a management notification to the network support module of the second device and sending an add event to the network service module of the first device. If the automatic management function is not enabled, the network support module of the first device will refuse to respond to the discovery request.

6. The method according to claim 5, characterized in that, When the network support module of the first device does not enable the automatic management function, the method further includes: If the whitelist does not include the target device information, the network support module of the first device performs the step of refusing to respond to the discovery request. The whitelist includes device information of devices that are allowed to access the ad hoc network. If the whitelist includes the target device information, the network support module of the first device executes the steps of sending a management notification to the network support module of the second device and sending an add event to the network service module of the first device.

7. The method according to claim 1, characterized in that, The method further includes: The network service module of the first device sends target page data provided by the network interaction module of the first device to the user terminal, so that the user terminal can display the target page data and operate on the target page data to obtain second configuration information for the second device; The network service module of the first device receives the second configuration information sent by the user terminal and sends the second configuration information to the network support module of the first device; The network support module of the first device sends the second configuration information to the network service module of the second device through the second tunnel, so that the network service module of the second device can use the second configuration information for configuration.

8. The method according to claim 7, characterized in that, The step of the network service module of the first device sending the target page data provided by the network interaction module of the first device to the user terminal includes: The network service module of the first device receives an access request sent by a user terminal, the access request including a target URL; When the target URL is the domain name of the self-organizing network, the network service module of the first device obtains the target page data provided by the network interaction module of the first device; The network service module of the first device carries the target page data in the access response of the access request and feeds back the access response to the user terminal.

9. The method according to claim 8, characterized in that, The access request is a request sent from the user terminal by the network support module of the third device in the ad hoc network through a third tunnel with the network support module of the first device; or... The access request is a request sent from the user terminal by the cloud through the cloud pipeline.

10. The method according to claim 7, characterized in that, The step of the network service module of the first device sending the target page data provided by the network interaction module of the first device to the user terminal includes: The network service module of the first device receives a page request sent by the network support module of the fourth device of the ad hoc network through the fourth tunnel between the network service module of the first device and the network service module of the first device. The page request is a request sent by the network service module of the fourth device to the first device after receiving an access request from a user terminal. The target URL included in the access request is the domain name of the ad hoc network. The network service module of the first device obtains target page data from the network interaction module of the first device according to the page request; and sends the target page data to the network service module of the fourth device through the fifth tunnel between the network support module of the first device and the network service module of the fourth device, so that the network service module of the fourth device carries the target page data in the access response of the access request and feeds back the access response to the user terminal.

11. The method according to any one of claims 1-10, characterized in that, The method includes: The network support module of the first device negotiates with the network support modules of other devices in the ad hoc network through a sixth tunnel to determine the roles of the first device and the other devices in the ad hoc network, wherein the role is master device or slave device.

12. A network device, characterized in that, The network device includes: a first network support module and a first network service module; The first network support module is used to receive a discovery request sent by the network support module of the second device through a first tunnel between the network device and the network support module of the second device in the self-organizing network when the network device is the master device of the self-organizing network. The discovery request includes the target device information of the second device. The first tunnel is a network architecture tunnel. The first network support module is configured to send a management notification to the network support module of the second device through the first tunnel, and send a join event to the first network service module, wherein the join event includes the target device information; The first network service module is used to obtain first configuration information that matches the target device information and send the first configuration information to the first network support module; The first network support module is used to send the first configuration information to the network service module of the second device through a second tunnel, so that the network service module of the second device can use the first configuration information to configure itself when the network support module of the second device receives the management notification. The second tunnel is an application service tunnel.

13. The network device according to claim 12, characterized in that, The first network service module is specifically used to call the interface of the second tunnel and send the first configuration information to the first network support module; The first network support module is specifically configured to receive the first configuration information through the interface of the second tunnel between the network service module of the second device and the network service module of the second device; convert the first configuration information into a target message of a preset protocol and send the target message to the network service module of the second device, so that when the network support module of the second device receives the management notification, the network service module of the second device converts the target message into the first configuration information and uses the first configuration information for configuration.

14. The network device according to claim 13, characterized in that, The preset protocol is the Simple Object Access Protocol.

15. The network device according to claim 12, characterized in that, The first network service module is further configured to send a registration event to the cloud via a cloud pipeline after the first network support module sends the first configuration information to the network service module of the second device. The registration event includes the target device information, so that the cloud can register the second device using the target device information. After the second device completes registration and receives a connection request sent by the second device via the cloud pipeline, the cloud module establishes a connection with the second device. The connection request is a request sent periodically by the second device, and the cloud pipeline is the connection established between the first network service module and the cloud.

16. The network device according to claim 12, characterized in that, The first network support module is further configured to: Upon receiving the discovery request, if the automatic management function has been enabled, a management notification is sent to the network support module of the second device, and an add event is sent to the first network service module. If the automatic management function is not enabled, the discovery request will be rejected.

17. The network device according to claim 16, characterized in that, The first network support module is further configured to: When the automatic management function is not enabled, if the management whitelist does not include the target device information, the discovery request will be refused. The management whitelist includes device information of devices that are allowed to access the ad hoc network. If the whitelist includes the target device information, a management notification is sent to the network support module of the second device, and an add event is sent to the first network service module.

18. The network device according to claim 12, characterized in that, The network device further includes: a first network interaction module; The first network service module is further configured to send target page data provided by the first network interaction module to the user terminal, so that the user terminal can display the target page data and operate on the target page data to obtain second configuration information for the second device; The first network service module is further configured to receive the second configuration information sent by the user terminal and send the second configuration information to the first network support module; The first network support module is further configured to send the second configuration information to the network service module of the second device through the second tunnel, so that the network service module of the second device can use the second configuration information for configuration.

19. The network device according to claim 18, characterized in that, The first network service module is specifically used for: Receive an access request sent by a user terminal, the access request including a target URL; When the target URL is the domain name of the self-organizing network, the target page data provided by the first network interaction module is obtained; The target page data is carried in the access response of the access request, and the access response is fed back to the user terminal.

20. The network device according to claim 19, characterized in that, The access request is a request sent from the user terminal by the network support module of the third device in the ad hoc network through a third tunnel with the first network support module; or... The access request is a request sent from the user terminal by the cloud through the cloud pipeline.

21. The network device according to claim 18, characterized in that, The first network service module is specifically used for: The network support module of the fourth device of the self-organizing network receives a page request sent by the network support module through the fourth tunnel between the network support module and the first network service module. The page request is a request sent by the network service module of the fourth device to the network device after receiving an access request from the user terminal. The target URL included in the access request is the domain name of the self-organizing network. According to the page request, target page data is obtained from the first network interaction module; the target page data is sent to the network service module of the fourth device through the fifth tunnel between the first network support module and the network service module of the fourth device, so that the network service module of the fourth device carries the target page data in the access response of the access request and feeds back the access response to the user terminal.

22. The network device according to any one of claims 12-21, characterized in that, The first network support module is further configured to perform Layer 2 negotiation with the network support modules of other devices through a sixth tunnel to determine the roles of the network devices and the other devices in the ad hoc network, wherein the roles are master devices or slave devices.

23. A network device, characterized in that, The method includes a processor and a machine-readable storage medium storing machine-executable instructions that can be executed by the processor, the processor being prompted by the machine-executable instructions to perform the steps of the method according to any one of claims 1-11.

24. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-11.

25. A computer program product, characterized in that, It also includes a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-11.

Images