Automatic inclusion management of multiple devices

Abstract

Techniques for incorporating a plurality of devices into management using a network management system (NMS) are described. The NMS has a memory and one or more processors coupled to the memory, the one or more processors configured to obtain inclusion management information of a first device of the plurality of devices; allocating the first device to a device group to be managed by the network management system based on the acquired inclusion management information of the first device; and automatically assigning a second device of the plurality of devices to a device group to be managed by the network management system based on assigning the first device to the device group to be managed by the NMS.

Description

[0001] Related applications

[0002] This application claims the benefit of U.S. Patent Application No. 18 / 933,154, filed October 31, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to computer networks, and more specifically, to providing devices for bringing networks under management. Background Technology

[0004] Commercial locations such as offices, hospitals, airports, stadiums, or retail stores typically install sophisticated wireless network systems throughout the premises, including networks of wireless access points (APs) to provide wireless network services to one or more wireless client devices (or simply "clients"). An AP is a physical electronic device that enables other devices to wirelessly connect to a wired network (e.g., a router and / or switch) using various wireless network protocols and technologies, such as IEEE 802.11-compliant (i.e., "WiFi"), one or more wireless LAN protocols including Bluetooth / Bluetooth Low Energy (BLE), mesh networking protocols such as ZigBee, or other wireless network technologies. Many different types of wireless client devices (such as laptops, smartphones, tablets, wearables, appliances, and Internet of Things (IoT) devices) incorporate wireless communication technologies and can be configured to connect to a compatible wireless access point to access a wired network when the device is within range of the access point. Summary of the Invention

[0005] In general, this disclosure describes techniques that enable the automatic inclusion of multiple devices for management by a network management system (NMS). An organization may include one or more sites, each containing different types of devices, such as access points (APs), routers, switches, and / or edge devices. To manage an organization's devices, the NMS may include devices for management, for example, by adding (also referred to as "claiming") devices to a device list maintained by the NMS and assigning one or more devices from the device list to a device group (such as a device group for a given site of the organization) that will be managed by the NMS. Devices are typically claimed and / or assigned to sites individually, which can be time-consuming, costly, and error-prone for organizations with a large number of sites and / or sites containing a large number of devices. According to the techniques of this disclosure, an NMS can automatically include multiple devices into a device group that will be managed by the NMS.

[0006] In some examples, the NMS can automatically bring one or more devices connected to an already managed device into management. For instance, the NMS can obtain management information associated with a first device (e.g., a router or switch), such as the first device's code (e.g., a claim code or activation code), to add the first device to a device list. From this device list, the NMS can assign one or more devices from the list to a device group (e.g., a device group within a site) that will be managed by the NMS. In response to claiming the first device, the first device can receive the network address of a second device (e.g., an access point) connected to it. For example, the first device can learn the MAC address of a second device directly connected to it, for instance, by using a discovery protocol such as Link Layer Discovery Protocol (LLDP). The second device can also use a discovery protocol to learn the first device's address. The NMS can obtain the second device's MAC address from the first device and determine whether the second device has been claimed based on the second device's MAC address. For instance, the NMS can determine whether it previously obtained the first device's MAC address from the second device, which can instruct the second device to connect to the first device. Based on the fact that NMS has already obtained the MAC addresses of the first and second devices, NMS can claim the second device, and if the first device is assigned to a site, it will automatically assign the second device to the same site.

[0007] In some examples, an NMS can automatically bring one or more devices under management, which then route traffic through the managed devices. For instance, an NMS can obtain management information associated with multiple devices and add them to a device list. From this list, the NMS can assign one or more devices from the device list to a site. An NMS can obtain the network address (e.g., IP address) of a given device (e.g., a switch or edge device) from among multiple devices and determine the given device's geographic coordinates (e.g., longitude and latitude) based on its IP address. Based on the given device's geographic coordinates, the NMS can determine the given device's physical address (e.g., street number and name, city, state, zip code, etc.). The NMS can generate a site based on the physical address and assign the given device to that site. An NMS can automatically assign one or more other devices to the same site, such as devices that route traffic to the NMS through a given device (e.g., devices sharing a common source IP address for traffic to the NMS).

[0008] The technology disclosed herein provides one or more technical advantages and practical applications. For example, by obtaining the network addresses of multiple connected devices and using those network addresses to claim and / or assign the multiple connected devices, NMS can incorporate multiple devices to a site using a single code for a given device among the connected devices, rather than using the corresponding code for each connected device. This reduces the time, cost, and / or error rate associated with incorporating multiple devices to a site. Furthermore, by incorporating multiple devices to a site based on the geographic location of a given device among the multiple devices, the multiple devices are incorporated into the site without having to incorporate each of the multiple devices individually, thereby reducing the time, cost, and / or error rate associated with incorporating devices to a site.

[0009] Details of one or more examples of the technology disclosed herein are illustrated in the following figures and description. Other features, objects, and advantages of the technology will be apparent from the specification, figures, and claims. Attached Figure Description

[0010] Figure 1A This is a block diagram of an example network system including a cloud-based network management system according to one or more technologies of this disclosure, the cloud-based network management system being configured to automatically incorporate multiple devices for management by the network management system.

[0011] Figure 1B It is shown Figure 1A A block diagram providing further examples and details of the network system.

[0012] Figure 2 This is a block diagram of an example access point device based on one or more technologies according to this disclosure.

[0013] Figure 3 This is a block diagram of an example network management system based on one or more technologies disclosed herein.

[0014] Figure 4 This is a block diagram of an example network node (such as a router or switch) according to one or more technologies of this disclosure.

[0015] Figure 5 This is a flowchart illustrating an example operation of managing multiple devices based on the network address of a given device among multiple devices, according to one or more techniques of this disclosure.

[0016] Figure 6 This is a flowchart of another example operation for incorporating multiple devices into management based on the geographic location of at least one of the multiple devices, according to one or more techniques of this disclosure.

[0017] Figure 7This is a flowchart illustrating an example operation of a network management system that automatically incorporates multiple devices into its management according to one or more technologies disclosed herein.

[0018] Figure 8 This is a flowchart illustrating an example operation of a network management system according to one or more technologies of this disclosure automatically including multiple devices under management based on the network address of a given device among multiple devices.

[0019] Figure 9 This is a flowchart illustrating an example operation of a network management system according to one or more technologies of this disclosure automatically incorporating multiple devices into management based on the geographic location of at least one of the multiple devices. Detailed Implementation

[0020] Figure 1A This is a block diagram of an example network system 100 including a cloud-based network management system (NMS) 130, which is configured to automatically incorporate multiple devices for management by the NMS 130, according to one or more technologies disclosed herein. The example network system 100 includes multiple sites 102A-102N, at which a network service provider manages one or more wireless networks 106A-106N respectively. Although in Figure 1A Each of the sites 102A-102N is shown as comprising a single wireless network 106A-106N, but in some examples each of the sites 102A-102N may include multiple wireless networks, and this disclosure is not limited in this respect.

[0021] Each of sites 102A through 102N includes multiple network access server (NAS) devices, such as access points (APs) 142, routers, or switches (shown as network nodes 146A through 146N) within the wired network edge. For example, site 102A includes multiple APs 142A-1 through 142A-N. Similarly, site 102N includes multiple APs 142N-1 through 142N-M. Each of the APs 142 can be any type of wireless access point, including but not limited to commercial or enterprise APs, routers, or any other device connected to a wired network and capable of providing wireless network access to client devices within the site. References to “N” or “M” can refer to any number. The reference to “N” for different elements does not have to be the same number. Similarly, the reference to “M” for different elements does not have to be the same number.

[0022] Each of sites 102A-102N also includes multiple client devices, typically referred to as UEs or client devices 148, also known as user equipment (UEs), representing various wireless-enabled devices within each site. For example, multiple UEs 148A-1 to 148A-N are currently located at site 102A. Similarly, multiple UEs 148N-1 to 148N-M are currently located at site 102N. Each UE 148 can be any type of wireless client device, including but not limited to mobile devices such as smartphones, tablets, or laptops, personal digital assistants (PDAs), wireless terminals, smartwatches, smart rings, or other wearable devices. UE 148 may also include wired client-side devices, such as IoT devices, such as printers, security devices, environmental sensors, or any other device connected to a wired network and configured to communicate over one or more wireless networks 106.

[0023] To provide wireless network services to UE 148 and / or communicate via wireless network 106, AP 142 and other wired client-side devices at site 102 are directly or indirectly connected to one or more network devices (e.g., routers, switches, etc.) via physical cables (e.g., Ethernet cables). Figure 1A In the example, site 102A includes network node 146A, and each of APs 142A-1 to 142A-N at site 102A is connected to network node 146A. Similarly, site 102N includes network node 146N, and each of APs 142N-1 to 142N-M at site 102N is connected to network node 146N. Although in Figure 1A The illustration appears to show each site 102 comprising a single network node 146 and all APs 142 at a given site 102 connected to that single network node 146. However, in other examples, each site 102 may include more or fewer switches and / or routers. Furthermore, APs and other wired client-side devices at a given site may be connected to two or more switches and / or routers. Additionally, two or more switches at a site may be interconnected and / or connected to two or more routers, for example, via a mesh or partial mesh topology in a central branch architecture. In some examples, the interconnected switches and routers comprise a wired local area network (LAN) at site 102 hosting the wireless network 106.

[0024] Example network system 100 also includes various network components for providing network services within a wired network, including (as an example) an authentication, authorization, and accounting (AAA) server 110 for authenticating users and / or UEs 148; a dynamic host configuration protocol (DHCP) server 116 for dynamically assigning network addresses (e.g., IP addresses) to UEs 148 during authentication; a domain name system (DNS) server 122 for resolving domain names to network addresses; multiple servers 128A-128N (collectively referred to as "Server 128") (e.g., web servers, database servers, file servers, application servers, etc.); and a network management system (NMS) 130. Figure 1A As shown, different devices and systems of network 100 are coupled together via one or more networks 134 (e.g., the Internet and / or corporate intranets).

[0025] Management device 111 may include a computing device associated with an administrator and / or information technology (IT) personnel at one or more sites 102 and / or network nodes 146 at the edge of a wired network. Management device 111 may be implemented as any suitable device for presenting output and / or accepting user input. For example, management device 111 may include a display. Management device 111 may be a computing system, such as a mobile or non-mobile computing device operated by a user and / or an administrator. Management device 111 may, for example, represent a workstation, laptop or notebook computer, desktop computer, tablet computer, or any other computing device that can be operated by a user and / or present a user interface according to one or more aspects of this disclosure. Management device 111 may be physically separate from NMS 130 and / or located in a different location from NMS 130, such that management device 111 can communicate with NMS 130 via network 134 or other means of communication.

[0026] As further described herein, the NMS 130 provides an integrated suite of management tools and implements the various technologies described in this disclosure. Figure 1AIn the example, NMS 130 is a cloud-based computing platform that manages wireless networks 106A-106N at one or more sites 102A-102N. For example, NMS 130 can provide a cloud-based platform for wireless and / or wired network data acquisition, monitoring, activity logging, reporting, predictive analytics, network anomaly detection, and alarm generation. NMS 130 monitors network data 137 received from wireless networks 106A-106N at each site 102A-102N and manages network resources (such as NAS devices at each site) to deliver a high-quality wireless experience to end users, IoT devices, and clients at the sites. Network data 137 may include statistics for one or more APs (e.g., AP 142), such as information indicating AP connectivity, information about client devices associated with the AP, AP traffic usage, and / or other information collected and reported by the AP (referred to as "AP statistics"). Network data 137 may also include statistics for one or more network nodes (e.g., network node 146), such as information indicating the network node's connectivity, information about devices connected to the network node, traffic usage of the network node, and / or other information collected and reported by the network node (referred to as "oc-stats"). Network data 137 may also include data from one or more client devices (e.g., UE 148), such as information indicating the client device's connectivity, information about the access point associated with the client device, traffic usage of the client device, and / or other information collected and reported by the client device.

[0027] NMS 130 may include a Virtual Network Assistant (VNA) 133, which implements an event processing platform to provide real-time insights into IT operations and streamline troubleshooting, and automatically takes corrective actions or provides recommendations to proactively resolve wireless network problems. VNA 133 may, for example, include an event processing platform configured to handle concurrent streams of network data 137 from sensors and / or agents associated with NAS devices (e.g., AP 142, routers, or switches, such as network node 146, etc.) and / or nodes within network 134. For example, VNA 133 of NMS 130 may include a low-level analytics and network error detection engine and alerting system, according to different examples described herein. The low-level analytics engine of VNA 133 can apply historical data and models to the inbound event stream to calculate assertions, such as the predicted occurrence of identified anomalies or events constituting network error conditions. In addition, VNA 133 can provide real-time alerts and reports to notify site or network administrators of any predicted events, anomalies, or trends via management device 111, and can perform root cause analysis and automatic or assisted error correction. In some examples, VNA 133 of NMS 130 can apply machine learning techniques to identify the root cause of error conditions detected or predicted from network data 137. If the root cause can be resolved automatically, VNA 133 can invoke one or more corrective actions to correct the root cause of the error condition, thereby automatically improving the underlying Service Level Expectation / Experience (SLE) metric and also automatically improving the user experience.

[0028] Further details of the operations implemented by the VNA 133 of the NMS 130 are described in the following patents: U.S. Patent No. 9,832,082, published November 28, 2017, entitled "Monitoring Wireless AccessPoint Events"; U.S. Publication No. US 2021 / 0306201, published September 30, 2021, entitled "Network System Fault Resolution Using a Machine Learning Model"; U.S. Patent No. 10,985,969, published April 20, 2021, entitled "Systems and Methods for a Virtual Network Assistant"; and U.S. Patent No. 10,985,969, published March 23, 2021, entitled "Methods and Apparatus for Facilitating Fault Detection and / or Predictive Fault". U.S. Patent No. 10,958,585, entitled “Method for Spatio-Temporal Modeling”, published on March 23, 2021; and U.S. Patent No. 10,862,742, entitled “Method for Conveying AP Error Codes Over BLE Advertisements”, published on December 8, 2020, the entire contents of all these patents are incorporated herein by reference.

[0029] The NMS 130 can also provide a cloud-based platform for incorporating devices managed by the NMS 130. The NMS 130 can obtain information associated with devices, such as a code used to add (i.e., "claim") a device to a device list (hereinafter referred to as a "claim code" or "activation code"). The NMS 130 can then assign one or more devices from the device list to a device group managed by the NMS 130. For example, network node 146A may include a claim code, such as a two-dimensional (QR) code. The NMS 130 can obtain and use this claim code to add network node 146A to the device list, from which the NMS 130 can assign network node 146A to site 102A for management by the NMS 130.

[0030] To incorporate multiple devices into a network of sites, each device is typically claimed and / or assigned to a site individually. For organizations with a large number of sites or sites with a large number of devices, claiming and / or assigning devices to sites individually can be time-consuming, costly, and prone to errors.

[0031] According to the technology described in this disclosure, NMS 130 includes a device manager 135 configured to provide automatic inclusion of multiple devices for management by NMS 130. As further described below, in some examples, device manager 135 of NMS 130 can automatically include one or more devices connected to already included devices under management based on, for example, the network address of a given device among the multiple devices. In some examples, NMS 130 can automatically include one or more devices that route traffic through already included devices under management based on, for example, the geographic location of at least one device among the multiple devices.

[0032] exist Figure 1AIn the example, the device manager 135 of the NMS 130 can bring network node 146A under management and automatically bring one or more devices (e.g., AP 142A-1) connected to network node 146A to management. For example, network node 146A may include a code that uniquely identifies network node 146A (e.g., a claim code, activation code, QR code, etc.). Device manager 135 can obtain the code of network node 146A and add (i.e., "claim") network node 146A to device list 136. The NMS 130 can then assign one or more devices from device list 136 to site 102A. In response to adding network node 146A to device list 136 and / or assigning network node 146A to site 102A, network node 146A can exchange information with devices connected to network node 146A (e.g., AP 142A-1). The information exchanged between connected devices may include the device's network address, such as the device's MAC address. For example, network node 146A can use a discovery protocol such as Link Layer Discovery Protocol (LLDP) to send its MAC address to AP 142A-1. Similarly, AP 142A-1 can use a discovery protocol to send its MAC address to network node 146A. As further described below, NMS 130 can claim AP 142A-1 based on the device's network address (e.g., MAC address), and in some examples, if network node 146A is assigned to site 102A, AP 142A-1 is automatically assigned to site 102A.

[0033] In some examples, the Device Manager 135 of the NMS 130 can bring network node 146A under management and automatically bring one or more devices (e.g., AP 142A-1) that route traffic to the NMS 130 through network node 146A to site 102A. For example, the Device Manager 135 of the NMS 130 can obtain inclusion management information associated with multiple devices, such as network devices (e.g., network node 146A) and one or more devices (e.g., one or more from AP 142A-1 to AP 142A-N) that route traffic to the NMS 130 through that network device. The Device Manager 135 of the NMS 130 can add these multiple devices to a device list 135, which can then be used to assign one or more devices from the device list 135 to site 102A. For example, the device manager 135 of the NMS 130 can obtain the IP address of network node 146A and determine the geographical location of network node 146A based on the IP address. For example, the device manager 135 of the NMS 130 can send a request to a geolocation provider, which can then determine the geographical coordinates of network node 146A based on the IP address of network node 146A and send the geographical coordinates of network node 146A to the NMS 130. Based on the geographical coordinates of network node 146A, the device manager 135 of the NMS 130 can determine the physical address of network node 146A (e.g., street number and name, city, state, zip code, etc.). For example, the device manager 135 of the NMS 130 can send a request to a physical address provider to determine the physical address of network node 146A based on its geographical location. Device Manager 135 of NMS 130 can generate device groups to be managed by NMS 130, such as device groups for site 102A, based on the physical address of network node 146A. For example, Device Manager 135 of NMS 130 can generate group names based on physical addresses (e.g., site names for site 102A), human-readable descriptors such as specifying at least a portion of the physical address (e.g., street number and name, city, etc.), and assign network node 146A to the generated site. As further described below, Device Manager 135 of NMS 130 can also assign one or more other devices (e.g., devices sharing a common source IP address for traffic to NMS) that route traffic to NMS 130 via network node 146A, such as one or more of AP 142A-1 to AP 142A-N.

[0034] Figure 1B It is shown Figure 1A A further example of a detailed block diagram of the network system. In this example... Figure 1B The NMS 130 is shown, and the NMS 130 is configured to provide services from a wireless network 106 and a wired LAN 175 network at the network edge. Figure 1B (The far left) crosses over to cloud-based application services 181 hosted by computing resources within data center 179. Figure 1B The rightmost part operates on an AI / machine learning-based computing platform that provides comprehensive automation, insights, and assurance (WiFi assurance, wired assurance, and WAN assurance).

[0035] As described herein, NMS 130 provides an integrated suite of management tools and implements various technologies disclosed herein. Typically, NMS 130 can provide a cloud-based platform for managing devices, acquiring wireless and / or wired network data, monitoring, activity logging, reporting, predictive analytics, network anomaly detection, and alarm generation. Once devices in network 100 are managed, NMS 130 can proactively monitor and adaptively configure network 100 to provide self-driving capabilities. For example, VNA 133 includes an AI-driven support and troubleshooting engine, anomaly detection, AI-driven location services, and an AI-driven RF-optimized natural language processing engine with reinforcement learning for network 100.

[0036] like Figure 1B As illustrated in the example, the AI-driven NMS 130 also provides configuration management, monitoring, and automated supervision of a software-defined wide area network (SD-WAN) 177, which operates as an intermediate network to communicatively couple wireless network 106 and wired LAN 175 to data center 179 and application services 181. Typically, SD-WAN 177 provides seamless, secure, traffic-engineered connectivity between “branch” routers 187A (e.g., branch or campus networks) hosting the edge wired network 175 of wireless network 106 and a “central” router 187B higher up in the cloud stack of cloud-based application services 181. SD-WAN 177 typically operates and manages overlay networks on top of the underlying physical wide area network (WAN), providing connectivity for geographically separated customer networks. In other words, SD-WAN 177 extends software-defined networking (SDN) capabilities to the WAN and allows the network to decouple the underlying physical network infrastructure from virtualized network infrastructure and applications, enabling the network to be configured and managed in a flexible and scalable manner. Once devices in SD-WAN 177 are brought under management, NMS 130 can provide configuration management, monitoring, and automated network construction tools for managed devices in SD-WAN 177.

[0037] In some implementations, the underlying routers of the SD-WAN 177 can implement a stateful, session-based routing scheme, where routers 187A and 187B dynamically modify the header content of raw packets originating from client device 148 to direct traffic to application service 181 along a selected path (e.g., path 189) without using tunnels and / or additional labels. In this way, routers 187A and 187B can be more efficient and scalable for large networks because the use of tunnelless, session-based routing allows routers 187A and 187B to achieve considerable network resource utilization by avoiding the need to perform encapsulation and decapsulation at tunnel endpoints. Furthermore, in some examples, each router 187A and 187B can independently perform path selection and traffic engineering to control the packet flow associated with each session, without using a centralized SDN controller for path selection and label assignment. In some examples, routers 187A and 187B implement session-based routing as Secure Vector Routing (SVR) provided by Juniper Networks.

[0038] Additional information regarding session-based routing and SVR is described in the following patents: U.S. Patent No. 9,729,439, published August 8, 2017, entitled "Computer Network Packet Flow Controller"; U.S. Patent No. 9,729,682, published August 8, 2017, entitled "Network Device and Method for Processing Sessions Using Packet Signature"; U.S. Patent No. 9,762,485, published September 12, 2017, entitled "Network Packet Flow Controller with Extended Session Management"; and U.S. Patent No. 9,762,485, published January 16, 2018, entitled "Router with Optimized Statistical Functions". U.S. Patent No. 9,871,748, entitled "Optimized Statistical Functionality"; U.S. Patent No. 9,985,883, published on May 29, 2018, entitled "Name-Based Routing System and Method"; U.S. Patent No. 10,200,264, published on February 5, 2019, entitled "Link Status Monitoring Based on Packet Loss Detection"; U.S. Patent No. 10,277,506, published on April 30, 2019, entitled "Stateful Load Balancing in a Stateless Network"; and U.S. Patent No. 10,277,506, published on October 1, 2019, entitled "Network Packet Flow Controller with Extended Session Management". U.S. Patent No. 10,432,522, entitled “FLOWCONTROLLER WITH EXTENDED SESSION MANAGEMENT”; and U.S. Patent Application Publication No. 2020 / 0403890, entitled “IN-LINE PERFORMANCE MONITORING”, published on December 24, 2020, the entire contents of each of these patents are incorporated herein by reference.

[0039] In some examples, the AI-driven NMS 130 can enable intent-based configuration and management of network system 100, including enabling the construction, presentation, and execution of intent-driven workflows for configuring and managing devices associated with wireless network 106, wired LAN network 175, and / or SD-WAN 177. For example, declarative requirements express the desired configuration of network components without specifying precise local device configurations and control flows. By utilizing declarative requirements, what should be achieved is specified, rather than how it should be achieved. Declarative requirements can contrast with imperative instructions that describe the exact device configuration syntax and control flow required to achieve the desired configuration. By utilizing declarative requirements instead of imperative instructions, users and / or user systems are relieved of the burden of determining the exact device configurations needed to achieve the desired results for the user / system. For example, when utilizing various types of devices from different vendors, specifying and managing the exact necessary instructions for configuring each device in the network is often difficult and cumbersome. As new devices are added and devices fail, the types and kinds of devices in the network can change dynamically. Managing various types of devices from different vendors to configure devices in a cohesive network using different configuration protocols, syntaxes, and software versions is often difficult to achieve. Thus, by requiring only the user / system to specify declarative requirements that define the expected results applicable across a wide variety of devices, the management and configuration of network devices become more efficient. Further examples of details and techniques for intent-based network management systems are described in the following patents: U.S. Patent No. 10,756,983, entitled "Intent-based Analytics," and U.S. Patent No. 10,992,543, entitled "Automatically generating an intent-based network model of an existing computer network," the entire contents of which are incorporated herein by reference.

[0040] According to the technology described in this disclosure, NMS 130 enables multiple devices to be automatically included for management by NMS 130. As further described below, in some examples, the device manager 135 of NMS 130 can automatically include one or more devices under management based on, for example, the network address of a given device among the multiple devices, which are connected to the already managed devices. In some examples, NMS 130 can automatically include one or more devices under management based on, for example, the geographic location of at least one device among the multiple devices, which route traffic through the managed device.

[0041] For example, NMS 130 can obtain the inclusion management information (e.g., claim code) of router 187A in SD-WAN 177, add router 187A to device list 136, and assign router 187A to a device group to be managed by NMS 130, such as a site including wired network 175 and / or wireless network 106. Based on assigning router 187A to a site, NMS 130 can automatically assign one or more devices connected to router 187A to one or more devices in the same site, such as wireless network 106 (e.g., AP) or wired network 175 (e.g., router or switch). As further described below, NMS 130 can obtain the network address (e.g., MAC address) of the device connected to router 187A and can include the device connected to router 187A in management based on the device's network address.

[0042] As another example, the device manager 135 of the NMS 130 can be configured to automatically include multiple devices under management based on the geographic location of network devices (such as router 187A in SD-WAN 177). In this example, the NMS 130 can obtain the inclusion information (e.g., claim code) of router 187A and assign router 187A to a site generated based on the IP address of router 187A. Based on the assignment of router 187A to the site, the NMS 130 can automatically assign one or more devices (such as one or more devices in wired network 175 and / or wireless network 106) that route traffic to the NMS 130 via router 187A.

[0043] Figure 2 This is a block diagram of an example access point (AP) device 200 configured according to one or more technologies disclosed herein. Figure 2 The example access point 200 shown can be used to implement the content of this article. Figure 1A Any of the APs 142 shown and described. Access point 200 may include, for example, a Wi-Fi, Bluetooth and / or Bluetooth Low Energy (BLE) base station or any other type of wireless access point.

[0044] exist Figure 2 In the example, access point 200 includes a wired interface 230, wireless interfaces 220A-220B, one or more processors 206, memory 212, and input / output 210 coupled together via bus 214. Different components can exchange data and information via bus 214. Wired interface 230 represents a physical network interface and includes a receiver (RX) 232 and a transmitter (TX) 234 for sending and receiving network communications (e.g., data packets). Wired interface 230 directly or indirectly couples access point 200 to a network providing... Figure 1A One or more network devices (e.g., network 134) that are connected to network 134. Figure 1A Network node 146). The first wireless interface 220A and the second wireless interface 220B represent wireless network interfaces and respectively include receivers (RX) 222A and 222B, each receiver including a receiving antenna, through which the access point 200 can receive wireless communication devices (such as…) Figure 1A The UE 148 receives wireless signals. The first wireless interface 220A and the second wireless interface 220B also include transmitters (TX) 224A and 224B, respectively. Each transmitter includes a transmitting antenna, through which the access point 200 can transmit wireless signals to wireless communication devices, such as… Figure 1A UE 148. In some examples, the first wireless interface 220A may include a Wi-Fi 802.11 interface (e.g., 2.4 GHz and / or 5 GHz), and the second wireless interface 220B may include a Bluetooth interface and / or a Bluetooth Low Energy (BLE) interface.

[0045] Processor 206 is a programmable, hardware-based processor configured to execute software instructions, such as software instructions for defining software or computer programs, which are stored in a computer-readable storage medium (such as memory 212), such as a non-transient computer-readable medium that includes storage devices (e.g., disk drives or optical drives) or memories (such as flash memory or RAM) or any other type of volatile or non-volatile memory, which stores instructions to cause one or more processors 206 to perform the techniques described herein.

[0046] Memory 212 includes one or more devices configured to store programming modules and / or data associated with the operation of access point 200. For example, memory 212 may include a computer-readable storage medium, such as a non-transient computer-readable medium that includes storage devices (e.g., disk drives or optical drives) or memories (such as flash memory or RAM) or any other type of volatile or non-volatile memory, which stores instructions to cause one or more processors 206 to perform the techniques described herein.

[0047] In this example, memory 212 stores executable software, including an application programming interface (API) 240, a communication manager 242, configuration settings 250, a device status log 252, a data storage 254, and a log controller 255. The device status log 252 includes a list of events specific to access point 200. Events may include logs of normal and error events (such as memory status, reboot events, crash events, Ethernet port status, upgrade failure events, firmware upgrade events, configuration changes, etc.) and the time and date stamp for each event. The log controller 255 determines the device's log level based on instructions from NMS 130. Data storage 254 may store any data used and / or generated by access point 200, including data received from devices connected to access point 200, such as the network address (e.g., MAC address) of the device connected to access point 200 (e.g., a router or switch). Access point 200 can send data to NMS 130 to bring access point 200 under management, for example, by automatically assigning access point 200 to the same site as the device assigned to it.

[0048] Input / output (I / O) 210 represents a physical hardware component capable of interacting with a user, such as a button, display, etc. Although not shown, memory 212 typically stores executable software for controlling the user interface regarding input received via I / O 210.

[0049] The communication manager 242 includes program code, when executed by one or more processors 206, allowing access point 200 to communicate with UE 148 and / or network devices providing access to one or more networks 134 via one or more interfaces 230 and / or any of 220A-220C. Configuration settings 250 include any device settings for access point 200, such as radio settings for each of the one or more wireless interfaces 220A-220C. These settings can be configured manually or can be remotely monitored and managed by NMS 130 to optimize wireless network performance on a periodic basis (e.g., hourly or daily).

[0050] Figure 3 An example NMS 300 with a device manager 370 according to one or more technologies of this disclosure is shown. The device manager 370 is configured to automatically include multiple devices for management by the NMS 300. The NMS 300 and the device manager 370 can be substantially similar. Figure 1AThe NMS 130 and Device Manager 136 operate accordingly. In such an example, the NMS 300 is responsible for monitoring and managing one or more wireless networks 106A-106N at sites 102A-102N respectively. In some examples, the NMS 300 receives data collected by AP 142 and network node 146, such as address information used to bring AP 142 and router 187 under management, for management by the NMS 300.

[0051] The NMS 300 includes a communication interface 330, one or more processors 306, a user interface 310, a memory 312, and a database 318. The components are coupled together via a bus 314, through which they can exchange data and information.

[0052] Processor 306 executes software instructions, such as software instructions for defining software or computer programs, which are stored in a computer-readable storage medium (such as memory 312), such as a non-transient computer-readable medium that includes storage devices (e.g., disk drives or optical drives) or memories (such as flash memory or RAM) or any other type of volatile or non-volatile memory, which stores instructions to cause one or more processors 306 to perform the techniques described herein.

[0053] The communication interface 330 may include, for example, an Ethernet interface. The communication interface 330 couples the NMS 300 to a network and / or the Internet, such as... Figure 1A This refers to any network 134 and / or any local area network shown. Communication interface 330 includes a receiver (RX) 332 and a transmitter (TX) 334. The NMS 300 sends / receives data and information, such as data, from / from any of the following devices or systems forming part of network 100: AP 142, network node 146, servers 110, 116, 122, 128, and / or ... and / or AP 142, network node 146, and / or AP 110, 116, 122, 128, and / or AP 142, network node 146, and / or AP 110, 116, 122, 128. Figure 1A As shown in the diagram. The data and information received by the NMS 300 may include, for example, connected devices (e.g., Figure 1AThe NMS 300 can use the network addresses (e.g., MAC addresses) of AP 142A-1 and network node 146A to automatically bring devices connected to already managed devices under management. In some examples, the data and information received by the NMS 300 may include, for example, the IP addresses of network devices, which the NMS 300 can use to bring network devices under management and proactively bring one or more other devices that route traffic to the NMS 300 through network devices under management.

[0054] Memory 312 includes one or more devices configured to store programming modules and / or data associated with the operation of NMS 300. For example, memory 312 may include a computer-readable storage medium, such as a non-transient computer-readable medium, including storage devices (e.g., disk drives or optical drives) or memories (e.g., flash memory or RAM) or any other type of volatile or non-volatile memory, which stores instructions that cause one or more processors 306 to perform the techniques described herein.

[0055] In this example, memory 312 includes API 320, SLE module 322, Virtual Network Assistant (VNA) / AI engine 350, Radio Resource Management (RRM) engine 360, and device manager 370. NMS 300 may also include any other programming modules, software engines, and / or interfaces configured for inclusion management and / or remote monitoring and management of wireless networks 106A-106N (including inclusion management and / or remote monitoring and management of any of AP 142, network node 146, etc.).

[0056] SLE module 322 implements the setting and tracking of thresholds for SLE metrics for each network 106A-106N. SLE module 322 also analyzes SLE-related data collected by APs (such as any of AP 142) from UEs in each wireless network 106A-106N. For example, APs 142A-1 to 142A-N collect SLE-related data from UEs 148A-1 to 148A-N currently connected to wireless network 106A. This data is sent to NMS 300, which is executed by SLE module 322 to determine one or more SLE metrics for each UE 148A-1 to 148A-N currently connected to wireless network 106A. In addition to any network data collected by one or more APs 142A-1 to 142A-N in wireless network 106A, this data is also sent to NMS 300 and stored in database 318, for example, as SLE metric 316.

[0057] RRM Engine 360 ​​monitors one or more metrics at each site 106A-106N to learn and optimize the RF environment at each site. For example, RRM Engine 360 ​​can monitor coverage and capacity SLE metrics for wireless network 106 at site 102 to identify potential SLE coverage and / or capacity issues in wireless network 106 and adjust the radio settings of the access points at each site to address the identified issues. For example, RRM Engine 360 ​​can determine the channel and transmit power distribution among all APs 142 in each network 106A-106N. For example, RRM Engine 360 ​​can monitor events, power, channel, bandwidth, and number of clients connected to each AP. RRM Engine 360 ​​can also automatically change or update the configuration of one or more APs 142 at site 106 to improve coverage and capacity SLE metrics and thus provide users with an improved wireless experience.

[0058] The VNA / AI engine 350 can be basically similar to Figure 1A The VNA 132 operates. The VNA / AI engine 350 analyzes data received from AP 142 / 200 and its own data to identify when an unwanted anomalous state is encountered in one of the wireless networks 106A-106N. For example, the VNA / AI engine 350 can identify the root cause of any unwanted or anomalous state (e.g., any poor SLE metric at one or more locations in the wireless networks 106A-106N). Furthermore, the VNA / AI engine 350 can automatically invoke one or more corrective actions designed to resolve the identified root cause of one or more poor SLE metrics. Examples of corrective actions that can be automatically invoked by the VNA / AI engine 350 may include, but are not limited to, invoking the RRM engine 360 ​​to reboot one or more APs, adjusting / modifying the transmit power of a specific radio in a specific AP, adding an SSID configuration to a specific AP, changing the channel on an AP or set of APs, etc. Corrective actions may also include restarting a switch and / or router, invoking the download of new software to an AP, switch, or router, etc. These corrective actions are given for illustrative purposes only, and this disclosure is not limited to this aspect. If automatic corrective actions are unavailable or do not adequately address the root cause, the VNA / AI Engine 350 can proactively provide notifications, including suggested corrective actions to be taken by IT personnel, to resolve network errors.

[0059] According to one or more techniques disclosed herein, the NMS 300 includes a device manager 370 configured to provide automatic inclusion of multiple devices for management by the NMS 300. As further described below, in some examples, the NMS 300's device manager 370 can automatically include one or more devices connected to the included devices for management based on, for example, the network address of a given device among multiple connected devices (e.g., ...). Figure 5 and Figure 8 (As further described in the text). In some examples, the NMS 300's Device Manager 370 can automatically bring one or more devices that route traffic through already managed devices under management, based on, for example, the geographic location of at least one of a plurality of devices (e.g., ...). Figure 6 and Figure 9 (As further described in the text). In these examples, NMS 300 can obtain address information (e.g., the MAC address of the connected device and / or the geographical location of the device) and store the address information in database 318 (shown as address information 340), which device manager 370 can use to manage multiple devices.

[0060] Figure 4 This is a block diagram illustrating an example network node 400 configured according to the technology described herein. In one or more examples, network node 400 implements a network device, such as, for example, a router, a switch, etc. In some implementations, Figure 4 Network node 400 can represent Figure 1A Network node 146 Figure 1B Examples of wired network 175 devices and / or SD-WAN 177 devices.

[0061] In this example, network node 400 includes a communication interface 402 (e.g., an Ethernet interface), a processor 406, input / output 408 (e.g., a display, buttons, keyboard, keypad, touchscreen, mouse, etc.), and memory 412 coupled together via bus 414. These components can exchange data and information via bus 414. Communication interface 402 couples network node 400 to a network, such as an enterprise network. While only one interface is shown by way of example, those skilled in the art will recognize that network nodes can (and often do) have multiple communication interfaces. Communication interface 402 includes a receiver (RX) 420 through which network node 400 (e.g., a router or switch) can receive data and information from one or more servers (e.g., an AAA server, DHCP server, DNS server, application server, etc.). Communication interface 402 includes a transmitter (TX) 422 through which network node 400 can transmit data and information, such as configuration information, authentication information, management information, web page data, etc.

[0062] Memory 412 stores executable software application 432, operating system 440, and data / information 430. Operating system 440 may include one or more discovery protocols, such as LLDP, Address Resolution Protocol (ARP), etc., to advertise identification information of network node 400, such as network address (e.g., MAC address) or other identification information. For example, network node 400 may use LLDP to advertise its MAC address to one or more other devices connected to it. Similarly, network node 400 may receive MAC addresses of one or more other devices connected to it.

[0063] Data 430 may include system logs and / or error logs, which store SLE metrics for node 400 and / or other devices (such as wireless access points) based on log levels as instructed by the network management system. In some examples, data 430 may store data learned from one or more devices connected to network node 400, such as identification information (e.g., MAC addresses) of the devices connected to network node 400. In some examples, as described herein, network node 400 may forward data 430 to the network management system (e.g., ...). Figure 1A The NMS130 is used for analysis and / or for managing network node 400 and / or devices connected to network node 400.

[0064] Figure 5 This is a flowchart illustrating an example operation of managing multiple devices based on the network address of a given device among multiple devices, according to one or more techniques of this disclosure. Figure 5 In the example shown, relative to Figure 1A Network node 146A describes device 502A, and relative to Figure 1A The AP 142A-1 describes device 502B. In Figure 5 The examples described herein are merely examples, and devices 502A and 502B can represent any connected devices and are not limited to them. Figure 5 The example described in [the document].

[0065] In this example, NMS 130 can obtain the inclusion management information (510) of a first device (e.g., device 502A). For example, NMS 130 can obtain the inclusion management information (510) of device 502A (e.g., device 502A). Figure 1A The NMS 130 can add (i.e., "claim") device 502A to the device list, and from this device list, the NMS 130 can assign one or more devices from the device list to a device group that will be managed by the NMS 130 (e.g., network node 146A). Figure 1A In the example of device group 102A in the NMS 130, device 502A can be assigned to a device group that will be managed by the NMS 130.

[0066] In response to adding device 502A to the device list and / or assigning device 502A to a device group (512) to be managed by NMS 130, device 502A can be connected to a second device (e.g., device 502B connected to device 502A). Figure 1A The AP 142A-1) exchanges information. For example, device 502A can send its identification information to device 502B. The identification information exchanged between connected devices may include the device's network address (e.g., MAC address). For example, device 502A can use a discovery protocol (such as LLDP) to send its MAC address to device 502B (514). Similarly, device 502B can use a discovery protocol to send its MAC address to device 502A (516).

[0067] Device 502A can determine whether device 502B has been claimed based on the network address of device 502B. For example, device 502A can determine whether it has binding information (referred to herein as "device binding" or "device mapping") associated with both device 502A and device 502B. Device 502A can periodically determine whether it has binding information associated with both device 502A and device 502B until it does. The absence of a device binding associated with both device 502A and device 502B indicates that device 502B has not yet been claimed. As further described below, if both device 502A and device 502B are claimed, NMS 130 can generate a device binding associated with both device 502A and device 502B and can send this device binding to device 502A.

[0068] Based on the determination that device 502A does not have binding information associated with devices 502A and 502B (518), device 502A sends a request (520) to NMS 130 for binding information associated with devices 502A and 502B. In response to receiving the request for binding information associated with devices 502A and 502B, NMS 130 can determine whether device 502B has been claimed. For example, NMS 130 can determine whether it has previously obtained the MAC address of device 502A from device 502B (e.g., AP 142A-1 may send the MAC address of network node 146A as AP statistics to NMS 130 in response to becoming active and learning the MAC address of network node 146A via LLDP). Based on the determination that NMS 130 has not yet obtained identification information for device 502B (522), NMS 130 does not claim device 502B.

[0069] Devices 502A and 502B can exchange identification information (524 and 526) again. Figure 5 In the example, device 502B can route uplink traffic to NMS 130 (528) via device 502A. For example, device 502B can send device information of device 502A learned by device 502B to NMS 130 (530).

[0070] Device 502A can again determine whether it has binding information associated with both Device 502A and Device 502B. Based on the determination that Device 502A does not have binding information associated with both Device 502A and Device 502B, Device 502A can send another request (532) to NMS 130 for binding information associated with both Device 502A and Device 502B. Based on the determination that NMS 130 has obtained the MAC address of Device 502A from Device 502B (534), NMS 130 can determine whether device binding associated with Device 502A and Device 502B exists (e.g., whether device binding is included in...). Figure 1A (In device list 136). If no device binding is associated with devices 502A and 502B, NMS 130 may claim device 502B to the device list. NMS 130 may then assign device 502B to a device group that will be managed by NMS 130 from the device list. In some examples, if device 502A is assigned to a device group, NMS 130 may further assign device 502B to the device group that will be managed by NMS 130 (536). In response to claiming device 502B, NMS 130 may generate a device binding associated with devices 502A and 502B (538), store the device binding in device list 136, and / or send the device binding to device 502A (540).

[0071] Figure 6 This is a flowchart illustrating an example operation of incorporating multiple devices into management based on the geographical location of at least one of a plurality of devices, according to one or more techniques of this disclosure. Figure 6 In the example shown, relative to Figure 1A Network node 146A describes device 602A, and relative to Figure 1A The AP 142A-1 describes device 602B. In Figure 6 The examples described are merely examples, and device 602A can represent any network device, and device 602B can represent any device that routes traffic to NMS 130 via device 602A.

[0072] In this example, NMS 130 can obtain the inclusion management information (610) of a first device (e.g., device 602A). For example, NMS 130 can obtain the inclusion management information (610) of device 602A (e.g., device 602A). Figure 1A The NMS 130 can add (i.e., "claim") device 602A to the device list, and from this device list, the NMS 130 can assign one or more devices from the device list to a device group that will be managed by the NMS 130 (e.g., network node 146A). Figure 1AIn the example of device group 102A in the NMS 130, device 602A can be assigned to a device group that will be managed by the NMS 130.

[0073] In response to adding device 602A to the device list and / or assigning device 602A to a device group to be managed by NMS 130, device 602A may perform device initialization (e.g., zero-touch configuration) upon power-on and may obtain an IP address via DHCP server 116. Device 602A may send its address (e.g., IP address) to NMS 130 (614). NMS 130 may obtain the geographic location (e.g., longitude and latitude) of device 602A based on its IP address. For example, NMS 130 may send a request (616) to a geographic location provider 604, which may then determine the geographic coordinates of device 602A based on its IP address and send the geographic coordinates of device 602A to NMS 130 (618). Based on the geographic location of device 602A, NMS 130 may obtain the physical address of device 602A (e.g., street number and name, city, state, zip code, etc.). For example, NMS 130 can send a request (620) for the physical address of device 602A to physical address provider 606, which can then determine the physical address of device 602A based on the geographical coordinates of device 602A and receive a response (622) including the physical address of device 602A.

[0074] NMS 130 can generate sites to be managed by NMS 130 based on the physical address of device 602A (624). For example, NMS 130 can generate a site name for site 102A based on its physical address, such as a human-readable descriptor specifying at least a portion of the physical address (e.g., street number and name, city, etc.), and assign device 602A to the generated site (626). NMS 130 can also assign one or more other devices (e.g., devices sharing a public source IP address for traffic to NMS) that route traffic to NMS 130 via network node 146A, such as device 602B (e.g., ...). Figure 1A (AP142A-1). For example, device 602B can perform device initialization (e.g., ZTP) and can route traffic to NMS 130 (628) via device 602A. NMS 130 can determine that the traffic received from device 602B has the same source IP address as the traffic from device 602A, and in response, automatically assign device 602B to the generated site (630).

[0075] Figure 7This is a flowchart illustrating an example operation of a network management system automatically incorporating multiple devices into management according to one or more technologies of this disclosure. (Relative to...) Figure 1A NMS 130 Device Manager 135 Description Figure 7 Example operation.

[0076] In this example, NMS 130 obtains the inclusion management information (702) of a first device (such as network node 146A) among multiple devices. For example, NMS 130's device manager 135 can obtain codes, such as the claim code, activation code, and / or QR code of network node 146A, to include network node 146A in management. Based on the obtained inclusion management information of network node 146A, NMS 130 assigns network node 146A to a device group to be managed by NMS 130, such as the device group of site 102A (704). For example, NMS 130's device manager 135 can add (i.e., "claim") network node 146A to device list 135 based on network node 146A's claim code and assign network node 146A to the device group of site 102A to be managed by NMS 130.

[0077] Based on assigning network node 146A to a device group to be managed by NMS 130, NMS 130 automatically assigns the second device (e.g., AP 142A-1) from among multiple devices to the device group (706) of site 102A to be managed by NMS 130. As further described below, in some examples, the device manager 135 of NMS 130 can be based on, for example, the network address of a given device among multiple devices (e.g., ... Figure 8 (as shown) or the geographical location of at least one of the multiple devices (such as...) Figure 9 As shown, AP 142A-1 is automatically included in the device group (e.g., the device group of the site) of site 102A, which will be managed by NMS 130.

[0078] Figure 8 This is a flowchart illustrating an example operation of a network management system according to one or more technologies of this disclosure automatically including multiple devices under management based on the network address of a given device among multiple devices. Relative to Figure 1A NMS 130 Device Manager 135 Description Figure 8 Example operation.

[0079] In this example, NMS 130 obtains the inclusion management information of the first device among multiple devices (802). For example, Device Manager 135 of NMS 130 can obtain the code of the first device, such as the claim code, activation code, and / or QR code of network node 146A. Based on the obtained inclusion management information of the first device, NMS 130 can assign the first device to a device group that will be managed by NMS 130 (804). For example, Device Manager 135 of NMS 130 can add (i.e., "claim") network node 146A to device list 135 and assign network node 146A to a device group that will be managed by NMS 130, such as the device group in site 102A.

[0080] NMS 130 obtains the network address of a second device among multiple devices, where the second device is connected to the first device (806). For example, in response to claiming network node 146A, network node 146A can receive the MAC address of AP 142A-1 connected to network node 146A. Network node 146A can learn the MAC address of AP 142A-1 directly connected to network node 146A, for example, by utilizing a discovery protocol such as LLDP. AP 142A-1 can also utilize a discovery protocol to learn the MAC address of network node 146A. NMS 130 can obtain the MAC address of AP 142A-1 from network node 146A and determine whether AP 142A-1 has been claimed based on the MAC address of AP 142A-1. For example, NMS 130 can determine whether NMS 130 previously obtained the MAC address of network node 146A from AP 142A-1 (e.g., Figure 5 Step 530 indicates that AP 142A-1 is active and has received a network address from network node 146A. Based on the determination that NMS 130 has obtained the MAC address of network node 146A and the MAC address of AP 142A-1, NMS can claim AP 142A-1 and automatically assign AP 142A-1 to site 102A (808).

[0081] Figure 9 This is a flowchart illustrating an example operation of a network management system according to one or more technologies of this disclosure automatically incorporating multiple devices into management based on the geographic location of at least one of the multiple devices. Relative to Figure 1A NMS130 Device Manager 135 Description Figure 9 Example operation.

[0082] In this example, NMS 130 obtains the inclusion management information (902) of the first device among multiple devices. For example, the device manager 135 of NMS 130 can obtain the code of the first device, such as the claim code, activation code, and / or QR code of network node 146A.

[0083] NMS 130 can obtain the IP address of the first device (904). For example, network node 146A can, for instance, perform device initialization upon power-up (e.g., zero-touch configuration) and can obtain an IP address via DHCP server 116. NMS 130 can obtain the IP address of network node 146A and can obtain the geographic coordinates (e.g., longitude and latitude) of network node 146A based on the IP address of network node 146A (906). For example, NMS 130 can send a request to a geolocation provider, which can then determine the geographic location (e.g., geographic coordinates) of network node 146A based on the IP address of network node 146A and send the geographic coordinates of network node 146A to NMS 130. Based on the geographic coordinates of network node 146A, NMS 130 can obtain the physical address of network node 146A (e.g., street number and name, city, state, zip code, etc.) (908). For example, NMS 130 can send a request for the physical address of network node 146A to the physical address provider, which can then determine the physical address of network node 146A based on geographical coordinates and send a response including the physical address of network node 146A.

[0084] NMS 130 can generate a device group to be managed by NMS 130, such as a device group for site 102A, based on the physical address of network node 146A (910). For example, NMS 130 can generate a physical address-based site name for site 102A, such as a human-readable descriptor specifying at least a portion of the physical address (e.g., street number and name, city, etc.), and assign network node 146A to the generated site (912). NMS 130 can also assign one or more other devices that route traffic through network node 146A to NMS 130 (914). For example, AP 142A-1 can perform device initialization (e.g., ZTP) and route traffic to NMS 130 through network node 146A. NMS 130 can determine that traffic received from AP 142A-1 has the same source IP address as traffic from network node 146A, and in response, automatically assign AP 142A-1 to the generated site.

[0085] The techniques described herein can be implemented in hardware, software, firmware, or any combination thereof. Different features described as modules, units, or components can be implemented together in an integrated logic device or individually as discrete but interoperable logic devices or other hardware devices. In some cases, different features of electronic circuits can be implemented as one or more integrated circuit devices, such as integrated circuit chips or chipsets.

[0086] If implemented in hardware, this disclosure may relate to apparatus, such as a processor or integrated circuit device, such as an integrated circuit chip or chipset. Alternatively or additionally, if implemented in software or firmware, these techniques may be implemented at least in part by a computer-readable data storage medium comprising instructions that, when executed, cause a processor to perform one or more of the methods described above. For example, the computer-readable data storage medium may store such instructions executed by a processor.

[0087] Computer-readable media can form part of a computer program product, which may include packaging material. Computer-readable media may include computer data storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, etc. In some examples, the article of manufacture may include one or more computer-readable storage media.

[0088] In some examples, computer-readable storage media may include non-transient media. The term "non-transient" can indicate that the storage medium is not embodied in a carrier wave or propagating signal. In some examples, non-transient storage media may store data that can change over time (e.g., in RAM or cache).

[0089] The code or instructions can be software and / or firmware executed by processing circuitry including one or more processors, such as one or more digital signal processors (DSPs), general-purpose microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Therefore, the term "processor" as used herein can refer to any of the foregoing structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functionality described in this disclosure can be provided within a software module or a hardware module.

Claims

1. A network management system, comprising: Memory; as well as One or more processors are coupled to the memory, the one or more processors being configured to: Obtain the inclusion management information of the first device among multiple devices; Based on the inclusion management information of the first device, the first device is assigned to a device group that will be managed by the network management system; as well as Based on assigning the first device to the device group to be managed by the network management system, the second device among the plurality of devices is automatically assigned to the device group to be managed by the network management system.

2. The network management system according to claim 1, wherein, In order to automatically assign the second device among the plurality of devices to the device group to be managed by the network management system, the one or more processors are configured to: Obtain the network address of the second device among the plurality of devices, wherein the second device is connected to the first device; and Based on the network address of the second device, the second device is assigned to the group of devices that will be managed by the network management system.

3. The network management system according to claim 2, wherein, The network address of the second device includes the MAC address of the second device.

4. The network management system according to claim 2, wherein, In order to obtain the network address of the second device, the one or more processors are configured to: Obtain the network address of the second device from the first device.

5. The network management system according to claim 1, in, In order to assign the first device to the group of devices to be managed by the network management system, the one or more processors are configured to: Obtain the IP address of the first device. Based on the IP address of the first device, obtain the geographical location of the first device; Based on the geographical location of the first device, obtain the physical address of the first device; Based on the physical address of the first device, a device group is generated that will be managed by the network management system; as well as The first device is assigned to the group of devices that will be managed by the network management system.

6. The network management system according to claim 5, wherein, In order to automatically assign the second device among the plurality of devices to the device group to be managed by the network management system, the one or more processors are configured to: Receive traffic from the second device that includes the source IP address associated with the first device; as well as Based on the traffic including the source IP address associated with the first device, the second device is assigned to the group of devices to be managed by the network management system.

7. The network management system according to claim 5, wherein, In order to generate a group of devices to be managed by the network management system, the one or more processors are further configured to: Based on the physical address of the first device, a group name is generated for the device group that will be managed by the network management system.

8. The network management system according to claim 5, wherein, The first device includes a network device at the edge of the site network.

9. The network management system according to any one of claims 1 to 8, wherein, The first device and the second device are directly connected.

10. The network management system according to any one of claims 1 to 8, wherein, The second device routes traffic to the network management system through the first device.

11. A method for incorporating equipment into management, comprising: The network management system obtains the inclusion management information of the first device among multiple devices. Based on the inclusion management information of the first device, the network management system assigns the first device to a device group that will be managed by the network management system. as well as Based on the assignment of the first device to the device group to be managed by the network management system, the network management system automatically assigns the second device from the plurality of devices to the device group to be managed by the network management system.

12. The method according to claim 11, wherein, Automatically assigning the second device from the plurality of devices to the group of devices to be managed by the network management system includes: The network management system obtains the network address of the second device among the plurality of devices, wherein the second device is connected to the first device; and The network management system assigns the second device to the group of devices to be managed by the network management system based on the network address of the second device.

13. The method according to claim 12, wherein, The network address of the second device includes the MAC address of the second device.

14. The method according to claim 12, wherein, Obtaining the network address of the second device includes: obtaining the network address of the second device from the first device.

15. The method according to claim 11, wherein, Assigning the first device to the group of devices to be managed by the network management system includes: The network management system obtains the IP address of the first device; The network management system obtains the geographical location of the first device based on its IP address; The network management system obtains the physical address of the first device based on its geographical location. The network management system generates the group of devices to be managed by the network management system based on the physical address of the first device; and The network management system assigns the first device to the group of devices that will be managed by the network management system.

16. The method according to claim 15, wherein, Automatically assigning the second device from the plurality of devices to the group of devices to be managed by the network management system includes: The network management system receives traffic from the second device, including the source IP address associated with the first device; and The network management system assigns the second device to the group of devices to be managed by the network management system based on the traffic including the source IP address associated with the first device.

17. The method according to claim 15, wherein, Generating the group of devices to be managed by the network management system includes: The network management system generates a group name for the device group that will be managed by the network management system based on the physical address of the first device.

18. The method according to any one of claims 11 to 17, wherein, The first device and the second device are directly connected.

19. The method according to any one of claims 11 to 17, wherein, The second device routes traffic to the network management system through the first device.

20. A computer-readable storage medium encoded with instructions for configuring one or more programmable processors to be a network management system according to any one of claims 1 to 10, or to be configured to perform the method according to any one of claims 11 to 19.

Images