CONFIGURATION OF AN ACCESS POINT WITH AN INTERNET OF THINGS (IoT) RADIO DEVICE

Abstract

Procedures (400), comprising: Receiving (402) by a processor (204; 704) an access point identifier list (216) from a network management node (202) in a network (120), wherein the access point identifier list (216) comprises a plurality of access point identifiers (210, 212, 214) and wherein each access point identifier in the access point identifier list (216) is uniquely associated with an access point (106A-C) comprising an Internet of Things (IoT) radio device (108A-C) capable of supporting IoT protocols; Received (404), by the processor (204; 704), a first rule list (218) from the network management node (202), where a rule in the first rule list (218) specifies a restriction and an access point configuration value; iterative selection of a new combination of an access point identifier from the access point identifier list (216) and the access point configuration value using an objective function until the objective function obtains an objective function value for the access point identifier that exceeds the constraint usually specified; Identify (406), by the processor (204; 704), the access point identifier that satisfies the usually specified constraint, using the objective function; and Configure (408) the access point associated with the access point identifier, by the processor (204; 704), with the access point configuration value usually specified.

Description

BACKGROUND

[0001] To provide network access across a large area, such as a large building, organizations typically rely on the use of access points. Access points can be placed at various locations within the desired wireless network access area, ensuring that a client device within range of one or more access points is always within range of that area. An access point can provide a wireless interface to a wired network. A typical access point may have many configurable settings. The state of a setting can affect the operation of the access point and / or how other network devices, such as client devices, interact with the access point. For example, a particular setting might determine the transmit power used when sending signals to client devices on the network.Other settings can specify the firmware and the protocol enabled by the firmware through which the access point can communicate with the client devices.

[0002] US 2009 / 0141694A1 describes a method for configuring and managing access points and an access controller. The method includes: creating at least one virtual radio interface, each assigned a standardized interface index from the Management Information Base (MIB), with each of the at least one virtual radio interface corresponding to at least one physical radio interface of at least one access point; determining a physical radio interface that corresponds to a virtual radio interface; and sending configuration information via the virtual radio interface to the determined physical radio interface when necessary. SHORT DESCRIPTION

[0003] A method according to claims 1 to 10, an administrative node according to claims 11 to 16 and a non-transitory machine-readable medium according to claims 17 to 20 is disclosed. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] These and other features, aspects, and benefits of the present specification will be better understood if the following detailed description is read with reference to the accompanying drawings, in which identical symbols represent identical parts in the drawings, wherein: Fig. shows an example of a network system; Fig. shows an example of a network system for configuring an access point with an Internet of Things (IoT) radio; The Fig. , Fig. and Fig. display an access point identifier list, a rule list, or a configuration file in accordance with an example; Fig.is a flowchart that illustrates a procedure for configuring an access point with an IoT radio according to another example; Fig. is a flowchart that illustrates a procedure for selecting an access point for the configuration according to an example; Fig. and Fig. are flowcharts that show a procedure for selecting multiple access points for configuration according to another example; Fig. is a block diagram showing a processor and a machine-readable medium encoded with example instructions for configuring access points with an IoT radio according to an example.

[0005] It is emphasized that the various features in the drawings are not drawn to scale. Rather, the dimensions of the various features in the drawings have been arbitrarily enlarged or reduced to clarify the discussion. DETAILED DESCRIPTION

[0006] The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and in the following description to refer to identical or similar parts. It is expressly stated that the drawings are for illustration and description purposes only. Although several examples are described in this document, modifications, adaptations, and other embodiments are possible. Accordingly, the following detailed description does not limit the disclosed examples. Instead, the proper scope of the disclosed examples can be defined by the accompanying claims.

[0007] The terminology used here serves to describe specific examples and is not intended to be restrictive. The singular forms "ein" and "die" used here also include the plural forms unless otherwise indicated by the context. The term "ein Weiteres" used here is defined as at least one second or more. The term "gekoppelt" used here is defined as connected, either directly, without any intervening elements, or indirectly with at least one intervening element, unless otherwise specified. For example, two elements may be mechanically, electrically, or communicatively connected via a communication channel, path, network, or system. Furthermore, the term "and / or," as used here, refers to and includes all possible combinations of the elements listed. It is also understood that, although the terms first, second, third, fourth, etc.,These terms are used to describe various elements, but these elements should not be restricted by them, as these terms are only used to distinguish one element from another unless otherwise stated or clear from the context. As used herein, the term "includes" means that it includes but is not limited to; the term "including" means that it includes but is not limited to; the term "based on" means at least partially based on.

[0008] An access point can contain a radio component capable of sending and receiving data to and from wireless client devices on a network using radio signals. The radio component can comprise a combination of hardware and software and may be developed based on a technical standard (e.g., IEEE 802.11ax, IEEE 802.15.1, IEEE 802.15.4, etc.). Based on the standard, the radio component can support a protocol for communication with a client device that supports that protocol. A protocol can refer to a set of rules that govern the type of data, commands, syntax, etc., to be used when devices communicate on a network. Some example protocols include Wi-Fi protocols, Bluetooth protocols, Internet of Things (IoT) protocols, etc.

[0009] A wireless component that supports IoT protocols can be referred to as an "IoT radio." An access point with an IoT radio can support IoT protocols such as Bluetooth Low Energy (BLE), Zigbee, Thread, and others. In some cases, IoT radios can be developed based on standards such as Wireless Personal Area Network (WPAN) standards, like IEEE 802.15.1 and IEEE 802.15.4, which enable support for multiple IoT protocols. An IoT radio can also support other protocols, such as Wireless Highway Addressable Remote Transducer Protocol (WirelessHART), ISA100.11a, IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN), Real-Time IoT (RIOT), TinyOS, Unison Real-Time Operating System (Unison RTOS), nanoQplus, Contiki, Zephyr, and others.

[0010] The access point and the IoT radio can contain separate memory components capable of storing firmware. Firmware refers to a specific set of instructions stored in non-volatile memory that initializes the functionality of hardware and software components within a device. In an IoT radio, the firmware can support one or more protocols (such as the IoT protocol) that allow the access point to connect to another device (such as an IoT device). In an access point, the firmware can authenticate other software components, such as an access point image stored in non-volatile memory. The access point image can contain boot software, such as a bootloader, an operating system, and other machine-executable instructions for implementing a protocol, such as the IoT protocol.The bootloader can contain instructions that are loaded into main memory and can form an interface between the hardware components and the operating system.

[0011] An access point can communicate with multiple IoT devices using different IoT protocols, which may be supported by firmware stored in the memory components of the IoT radio and / or the access point. However, the memory component in the IoT radio and access points has limited capacity. Due to this limited storage capacity, the firmware installed in the IoT radio may not be able to support multiple protocols. For example, the total storage space in the IoT radio may be less than 1 MB. The memory component may need to contain the firmware for the protocol, a bootloader, and additional software components such as the OEM (Original Equipment Manufacturer) image, which together may require more than 1 MB of storage space.To overcome this limitation, multiple firmwares can be bundled within the access point's memory component of the image, with each firmware supporting a different protocol. However, the access point's memory component also has limited capacity, thus restricting the number of firmwares that can be bundled within the access point image.

[0012] Some approaches to overcoming memory limitations involve manually reconfiguring the access point as needed with a specific radio setting or configuration (e.g., protocols, firmware, transmit power). However, manually reconfiguring each access point can be tedious and time-consuming. For example, a network environment might include IoT devices that operate and communicate using the BLE or Zigbee protocols. In such a network, access points may need to be reconfigured in certain scenarios. These scenarios include varying densities of different types of IoT devices within an area, weak signal strength received at some access points, and / or the installation of new IoT devices at a particular location.To change access point configurations, a network administrator may need to manually assign configuration values ​​to each individual access point. This task can become complex as the number of protocols, firmware versions, and / or IoT devices on the network increases. Furthermore, some access points may require third-party firmware to support specific protocols, such as 6LoWPAN.

[0013] In some solutions, a central entity on the network can run an application or microservice that manages the reconfiguration of access points. This central entity can be a server, a controller, or a network device capable of managing a group of access points or individual access points. The central entity can periodically retrieve network data and determine the configuration values ​​for each access point. However, in a network that includes access points with IoT radios and IoT client devices, the central entity may not be able to obtain useful data to determine the configuration values. For example, some IoT devices, such as Zigbee-based devices, may be silent and not automatically provide data to the central entity. Such devices may require manual interaction, for instance, to connect to a nearby access point.In such scenarios, a central authority may not be able to perform the automatic configuration of the access points.

[0014] To this end, the examples described here address the aforementioned technical problems by providing automatic reconfiguration of access points with an Internet of Things (IoT) radio using a centralized unit. In some examples, an access point identifier list is received from a network administration node in a network. Each access point identifier in the list is uniquely associated with an access point containing an IoT radio. An initial rule list is received from the network administration node. Each rule in the initial rule list specifies a constraint and access point configuration values. A target function is used to identify access point identifiers that satisfy one or more of the constraints in the rules.The access points associated with the identified access point identifiers are configured with the access point configuration values ​​specified in the rules.

[0015] Accordingly, the examples presented here enable the configuration of access points containing IoT radio components using a centralized unit. This centralized unit utilizes administrator-defined rules to dynamically determine ideal combinations of access points and access point configuration values, rather than configuring each access point individually. Furthermore, this configuration process overcomes the memory limitations of IoT radios and reduces the need for manual access point configuration. Additionally, the examples described here allow for dynamic access point configuration upon receiving rules from a network administrator. Based on this configuration process, the radio capacities of the access points can also be balanced to manage varying client device densities within a network.

[0016] Before describing examples of the disclosed methods and systems in detail, it is useful to describe an exemplary network installation with which these systems and methods could be implemented in various applications. Fig.This diagram shows an example of a network system 100 that can be implemented for an organization such as a commercial space, a healthcare facility, a warehouse or storage facility, an educational institution, a government agency, or another type of organization. This diagram illustrates an example of a network implemented in an organization with multiple client devices 110 and multiple physical or geographic locations 122, 132, and 142. The network system 100 can include a primary location 122 that communicates with a network 120. The network system 100 can also include a secondary location 132 and a tertiary location 142, which may be located remotely from the primary location and communicate with the network 120.

[0017] The primary location 122 can encompass a primary network, which could be, for example, a home network, a business network, or another network installation. In some examples, the primary network of location 122 might be a private network, such as one that includes security and access controls to restrict access to authorized users of the private network. Authorized users might include, for example, the residents of a house, the customers of a business, the employees of a business at the primary location 122, and so on.

[0018] Each site 122, 132, 142 can communicate with a management node 102 to manage and configure the network devices present at the sites. The management node 102 can be a central system, such as a computer system or server, that has computing, storage, and networking capabilities. The management node 102 can use these capabilities to receive network data, process network data, and configure network devices. For example, the management node 102 can configure the access points 106A-C, for example, at the primary site 122, as well as at the secondary site 132 and tertiary site 142. The management node 102 can also manage the configuration of switches, routers, and / or client devices. The management node 102 and its capabilities are discussed in the context of Fig. described in more detail.

[0019] In the example shown, the primary site 122 includes a controller 104, which communicates with the management node 102 via network 120. The controller 104 can provide communication with network 120 for the primary site 122, although it need not be the only point of communication with network 120 for the primary site 122. In some examples, the controller 104 can be hardware, software, or a combination thereof, used to control and centralize the management of network devices such as access points 106A-C, client devices 110A-J, and so on. A single controller 104 is shown, although the primary site 122 may include multiple controllers and / or multiple communication points with network 120. In some examples, the controller 104 communicates with network 120 via a router (not shown).In some examples, the controller 104 itself can be the access points 106A-C or provide their functionality. In other examples, the controller 104 provides router functionality to the devices at the primary site 122. The controller 104 can communicate with the access points 106A-C and / or one or more switches 108. The switches 108 and the access points 106A-C provide network connectivity for various client devices 110A-J. Through a connection to a switch 108 or access points 106A-C, a client device 110A-J can access network resources, including other devices at the primary site 122 and other systems and devices connected to the network 120.

[0020] Client devices 110 can provide resources, such as computing, storage, and / or network resources, for one or more workloads, such as applications, running on them. In various examples, client devices 110 can be Internet of Things (IoT) devices with a processor or microcontroller, a memory component, a network component, and / or other electronic components. Client devices 110 can have similar or different hardware and / or software configurations in a given implementation of the network system 100. Examples of client devices 110 can include, but are not limited to, sensors, computer devices, IoT-enabled devices, and Industrial IoT (IIoT) devices, which may be contained in a virtualized and / or non-virtualized architecture.The term "IoT-enabled devices" as used here encompasses devices equipped with electronics, software, sensors, actuators, and / or network connectivity that allow these devices to connect to a network and / or exchange data. The term "IoT-enabled devices" as used here refers to IoT-enabled devices used in industrial applications, such as manufacturing or energy management. Examples of IoT-enabled devices include sensors, vehicles, monitoring devices, devices enabling smart purchasing systems, manufacturing equipment, and the like.

[0021] In addition to IoT devices, client devices 110 may also include electronic devices or systems, such as a computer, workstation, desktop computer, laptop computer, smartphone, smart wearable device, head-worn display device, mainframe, tablet computer, e-reader, netbook computer, televisions and similar screens (e.g., smart TVs), content receivers, set-top boxes, personal digital assistants (PDAs), smart terminals, silent terminals, servers, virtual terminals, video game consoles, virtual assistants, and the like.

[0022] Furthermore, within the primary site 122, a switch 108 is included as an example of an access point to the network established at the primary site 122 for wired client devices 110I-J. The client devices 110I-J can connect to the switch 108 and access other devices within the network system 100 via the switch 108. The client devices 110I-J can also access the network 120 via the switch 108. The client devices 110I-J can communicate with the switch 108 via a wired connection 112. In the example shown, the switch 108 communicates with the controller 104 via a wired connection 112, although this connection could also be wireless.

[0023] The access points 106A-C provide the client devices 110A-H with access to the network established at the main site 122. The access points 106A-C can control the network access of the client devices 110A-H and authenticate the client devices 110A-H for connection to the access points and, via the access points, to other devices within the network system 100. Each of the access points 106A-C can be a combination of hardware, software, and / or firmware configured to provide wireless network connectivity for wireless client devices 110A-H. In some examples, the access points 106A-C can be configured and managed by the management node 102. In other examples, the access points 106A-C can be managed and configured by the controller 104.The access points 106A-C communicate with the control unit 104 and the network via connections 112, which can be either wired or wireless interfaces. The access points 106A-C can contain radio components for communicating with the client devices 110A-H via radio signals. In some examples, the radio components may be an IoT radio component capable of communicating with IoT client devices using IoT protocols. In other examples, the radio components may include a Wi-Fi radio component, a Bluetooth radio component, and the like.

[0024] Network system 100 can include one or more secondary sites 132. A secondary site 132 can be located at a different physical or geographic location than a primary site 122. In some cases, a secondary site 132 may be located at the same geographic location or possibly in the same building as a primary site 122, but it will not have a direct connection to the primary site 122 network. Instead, a secondary site 132 may use a connection through another network, such as network 120. A secondary site 132 may include a gateway device 134 for communication with network 120. A gateway device 134 can be a router, a digital-to-analog modem, a cable modem, a DSL modem, or any other network device configured to communicate with network 120.The secondary site 132 can also include a switch 138 and / or an access point 106D, which communicates with the gateway device 134 via wired or wireless connections. The switch 138 and the access point 106D can connect to the network for various client devices 110K-N.

[0025] In various examples, the secondary site 132 can communicate directly with the primary site 122, allowing client devices 110K-N at secondary site 132 to access network resources at primary site 122 as if they were located at primary site 122. In such examples, the secondary site 132 can be managed by the controller 104 at primary site 122, and the controller 104 can provide the necessary connectivity, security, and accessibility to enable communication between the secondary site 132 and primary site 122. Once connected to primary site 122, the secondary site 132 can function as part of a private network provided by primary site 122.

[0026] In various examples, the network system 100 can include one or more smaller tertiary sites 142, each comprising only a gateway device 144 for communication with the network 120 and a wireless access point 106E through which various client devices 1100-P access the network 120. Such a tertiary site 142 could be, for example, the apartment of a single employee or a temporarily remote office. The tertiary site 142 can also communicate with the primary site 122, allowing the client devices 1100-P at the tertiary site 142 to access network resources at the primary site 122 as if these client devices 1100-P were located at the primary site 122. Once the tertiary site 142 is connected to the primary site 122, it can function as part of a private network provided by the primary site 122.

[0027] Network 120 can be a public or private network, such as the internet or another communications network that enables connections between the various locations 122, 132 to 142. Network 120 can include third-party telecommunications lines, such as telephone lines, broadcast coaxial cables, fiber optic cables, satellite communications, cellular communications, and the like. Network 120 can include any number of intermediate network devices, such as switches, routers, gateways, servers, and / or controllers, which are not directly part of network system 100 but facilitate communication between the various parts of network system 100 and between network system 100 and other units connected to the network.

[0028] Fig.Figure 200 shows a network system with a management node 102, a network administration node 202, and access points 106A-C, according to an example. The access points 106A-C can be part of the network site 122, as shown, for example, in Figure 200. Fig. described. The management node 102 can be connected to the network site 122 via the network 120 as part of the network system 200. The network system 200 can facilitate the configuration of the access points 106A-C, including the IoT radio components 108A-C. Although the network system 200 in Fig. As depicted, comprising a management node 102, a network administration node 202 and three access points 106A-C, the network system 200 can include any number of management nodes, network administration nodes and access points without limiting the scope of this disclosure.

[0029] Examples of Network 120 include public or private networks, including but not limited to Internet Protocol (IP) or non-IP-based local area networks (LANs), wireless LANs (WLANs), metropolitan area networks (MANs), wide area networks (WANs), storage area networks (SANs), personal area networks (PANs), cellular communication networks, and the Internet. Communication over Network 120 can be in accordance with various communication protocols, such as, but not limited to, Transmission Control Protocol and Internet Protocol (TCP / IP), User Datagram Protocol (UDP), IEEE 802.11, and / or cellular communication protocols. Communication over Network 120 can be via wired (e.g., copper cables, optical communication, etc.) or wireless communication technology.In some examples, the 120 network can be activated via private communication links, including but not limited to communication links established via wireless, wired (e.g., copper), and similar technologies.

[0030] Access points 106A-C may be the same or similar access points as those found in Fig. are described. The 106A-C access points can perform network data transmission operations, including but not limited to switching, routing, bridging, or a combination thereof. The 106A-C access points can also perform network interface operations, enabling wireless network devices, such as those described in Fig.The client devices shown, 110A-P, enable connection to a wired or wireless network via various communication standards. The 106A-C access points can contain all necessary hardware components, including but not limited to processing units, storage units, input devices, communication devices, etc. The 106A-C access points can include one or more network interfaces. A network interface can comprise a network interface controller (NIC) with one or more ports (e.g., Ethernet ports), one or more sockets, one or more adapters, or a combination thereof. The access point is not limited to wireless access points that comply with IEEE 802.11 standards.

[0031] Furthermore, the access point 106A-C can contain a radio component with a specific MAC (Media Access Control) address. In some examples, the radio component can be an IoT radio. In some examples, the radio component can operate in a 5 GHz band conforming to the IEEE 802.11ac standard, in a 2.4 GHz band conforming to one or more of the IEEE 802.11ac, 802.11n, and 802.11g standards, or in a combination thereof. In some examples, the radio component 108A-C can operate in one or more frequency bands. A person skilled in the art will understand that a radio component of a network interface can transmit and receive wireless signals conforming to any suitable type(s) of wireless communication standards now known or subsequently developed, and / or operating in any suitable frequency range(s).

[0032] The network management node 202 can include at least one processor and at least one machine-readable storage medium encoded with instructions that can be executed by the at least one processor to manage the functions of the network site 122. The network management node 202 can manage the functions of the access points and other devices (e.g., client device 110A-P, switch 108, as described in Fig.(shown) at site 122, the network management node 202 can monitor and coordinate settings associated with access points 106A-C at network site 122. In some examples, access point settings might include radio configurations, including but not limited to firmware type, protocols, power specifications, and the like. In some examples, network management node 202 can receive access point identifiers 210, 212, and 214 (designated as AP_ID1, AP_ID2, and AP_ID3) from the respective access points 106AC. The access point identifier can contain an access point context, which can specify the type and location of an access point at network site 122. The access point type might be, for example, a network access point, a network access point, or a network access point. Specify, for example, a type of access point design (e.g., internal antenna or external antenna) or a type based on the operating environment (e.g., indoor access point or outdoor access point).The location of the access point can, for example, specify the location in relation to a site (e.g., floor number and building name at a site).

[0033] Furthermore, the network management node 202 can perform any network data transfer operations, including but not limited to switching, routing, bridging, or a combination thereof. In some examples, the functions of the network management node 202 can be implemented in the management node 102. Alternatively, the network management node 202 can be a computer system that communicates with the management node 102 over the network 120. In some examples, the functions performed by the network management node 102 can be automated using various machine learning techniques. In other examples, the network management node 202 can be operated manually by a network administrator or operator. Additionally, in some examples, the network management node 202 can have a dashboard interface (in Fig.(not shown) to display a summary of the settings and context of the 106A-C access points and other network devices.

[0034] As in Fig.As depicted, the management node 102 can, in some examples, be a system with a processor or microcontroller and / or other electronic component, or a device that enables, for example, various computing and / or data storage services. Examples of the management node 102 may include, but are not limited to, a server, a computer device, a desktop computer, a laptop, a smartphone, a workstation, a storage system, or a converged or hyperconverged system, and the like, configured for managing and configuring network devices. Furthermore, in certain examples, the management node 102 may be or include a virtual machine or a containerized application running on the hardware of the network system 200.

[0035] In some examples, the management node 102 may include a processor 204 and a machine-readable medium 206. The machine-readable medium 206 may be any electronic, magnetic, optical, or other physical storage device capable of storing data and / or executable instructions 208. For example, the machine-readable medium 206 may include one or more of the following types of memory: random-access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a storage disk, flash memory, compact disc read-only memory (CD-ROM), and the like. The machine-readable medium 206 may be non-transferable. As detailed here, the machine-readable medium 206 may be encoded with the executable instructions 208 to perform one or more procedures, such as those described in the Fig. , Fig. , Fig. and Fig. described procedure.

[0036] Furthermore, the processor 204 can be a physical device, such as one or more central processing units (CPUs), one or more semiconductor-based microprocessors, one or more graphics processing units (GPUs), application-specific integrated circuits (ASICs), a field-programmable gate array (FPGA), other hardware devices capable of retrieving and executing instructions 208 stored in the machine-readable medium 206, or combinations thereof. The processor 204 can retrieve, decode, and execute the instructions 208 stored in the machine-readable medium 206 to configure access points 106A-C, including IoT radios 108A-C (described below).Alternatively or additionally to executing instructions 208, the processor 204 may contain at least one integrated circuit (IC), control logic, electronic circuits, or combinations thereof, comprising a set of electronic components for performing the functions to be executed by the management node 102 (described below). Furthermore, in certain examples where the management node 102 may be a virtual machine or a containerized application, the processor 204 and the machine-readable medium 206 may represent a processor and a machine-readable medium of the hardware or computer system that hosts the management node 102 as the virtual machine or the containerized application.

[0037] During operation, processor 204 can receive an access point ID list 216 (designated as AP_ID_LIST) from network management node 202 in network 122. Access point ID list 216 can specify access point IDs 210, 212, and 214, which are associated with access points 106A-C, including IoT radios 108A-C. In other examples, processor 204 can receive access point IDs 210, 212, and 214 directly from access points 106A-C. Processor 204 can also receive an initial rule list 218 (designated as RUL_LIST) from network management node 202. The initial rule list 218 can contain one or more rules for configuring access points 106A-C at network location 122.

[0038] In the Fig. and Fig.The access point identifier list file and the rule list file are shown as an example. The access point identifier list (216) and the rule list (218) can be transferred in a key-value pair file format, such as a JSON (JavaScript Object Notation) or XML (Extensible Markup Language) file. In the access point identifier list (216), each access point identifier can be a key, and the access point location (designated as AP_LOC1, AP_LOC2, AP_LOC3) and the access point type (APTYPE1, AP_TYPE2, AP_TYPE3) can be the values ​​for the respective key. The access point location can specify the location of the access point relative to a site (e.g., floor number and building name at a site). For example, AP_LOC1 can be "floor 1", AP_LOC2 "floor 2" and AP_LOC3 "floor 3" of a building at a location (e.g., location 122).The access point type can specify the type of access point construction (e.g., internal antenna or external antenna) or the type of access point depending on the operating environment (e.g., indoor access point or outdoor access point). For example, AP_TYPE1 can be "AP with external antenna", AP_TYPE2 "AP with internal antenna", and AP_TYPE3 "AP with internal antenna".

[0039] In rule list 218, each rule can specify a restriction and access point configuration values. In some examples, the restriction may include an access point selection function for choosing one or more access point identifiers. The access point selection function may include one or more criteria, such as a location or access point type, to select one or more access points. In some examples, the access point configuration values ​​may include firmware, protocol, power specifications, and similar information. The firmware may be original equipment manufacturer (OEM) supported firmware or third-party firmware. Protocol examples include Bluetooth Low Energy (BLE), Zigbee, Thread, Wireless Highway Addressable Remote Transducer Protocol (WirelessHART), and ISA100.This includes IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN), Real-Time IoT (RIOT), TinyOS, Unison Real-Time Operating System (Unison RTOS), nanoQplus, Contiki, Zephyr, etc. The power specification can include a measure of the transmit power to be used during communication. Each rule can be formulated in a key-value pair format, where the constraint (designated AP_SEL_FN1, AP_SEL_FN2, AP_SEL_FN3) is the key and the configuration values ​​(designated AP_CONFIG_VAL1, AP_CONFIG_VAL2, AP_CONFIG_VAL3) are the values.

[0040] Back to Fig.The processor 204 can identify access point identifiers from the access point identifier list 216 based on the rules contained in the first rule list 218. In some examples, the processor 204 can identify access point identifiers that satisfy one or more of the constraints specified in the rules. In some examples, the identification of the access point identifiers can be performed using an objective function. The objective function can be a mathematical function for determining a value (hereafter referred to as the objective function value) for a given input. For example, an access point identifier and the rule list can be provided as input to the objective function, and the objective function value can be the output. In some examples, the objective function value can indicate whether a given access point identifier satisfies a constraint in a rule in the first rule list 218.The access point identifier can satisfy a condition if the location of the access point (e.g., AP_LOC1) or the type (e.g., AP_TYPE1) matches the location or type specified in the condition.

[0041] In some examples, the processor 204 can execute an optimization algorithm to vary the input (e.g., the access point identifier) ​​to determine an optimal objective function value. For example, the processor 204 can use the optimization algorithm to iteratively select different access point identifiers as input for the objective function to determine whether the optimal objective function value is achieved for that access point identifier. The optimal objective function value can be a predefined maximum or minimum value of the objective function. For example, the predefined maximum or minimum objective function value can indicate that the given access point identifier satisfies one of the rules in the first rule list 218.

[0042] In other examples, the processor can identify 204 access point identifiers based on a combination of access point identifiers and access point configuration values ​​that satisfy a rule in the rule list (as in relation to Fig. (further described). In such examples, the 204 processor can provide a combination of access point identifiers, access point configuration values, and the rule list as inputs for the objective function to obtain objective function values.

[0043] Based on the objective function value for each access point identifier, the processor 204 can obtain a list of access point identifiers for configuration that satisfy the constraints in the rules. The processor 204 can configure the access points 106A-C associated with the one or more access point identifiers using the access point configuration values ​​specified in the rules. For example, the processor 204 can use a configuration file 220 (designated as CONFIG_FILE, as in Fig.(as shown) to a network management node 202. In other examples, processor 204 can send configuration file 220 directly to access points 106A-C. The configuration file can be a key-value pair file containing access point identifiers and access point configuration values ​​as keys and values, respectively. The access points are configured with the access point configuration values ​​specified in configuration file 220.

[0044] Fig. Figure 400 shows a flowchart illustrating a procedure 400 for configuring access points with IoT radios according to an example. For illustrative purposes, procedure 400 is shown in conjunction with network system 200. Fig.described, but procedure 400 should not be interpreted as being limited to the example configuration of system 200. Procedure 400 can include procedure blocks 402, 404, 406, and 408 (hereafter collectively referred to as blocks 402-408), which can be executed by a system such as the management node 102. In particular, the operations in each of the procedure blocks 402-408 can be performed by the processor 204 by executing the instructions 208 stored on the machine-readable medium 206 (see Fig. In some other examples, the execution order of blocks 402-408 can be changed from the one in Fig. The order shown may differ. For example, blocks 402-408 can be executed in series, in parallel, or in a series-parallel combination. Certain details of the operations performed by processor 204, already described in Fig.For the sake of brevity, the details already described will not be repeated here.

[0045] In block 402, the processor 204 can receive an access point identifier list 216 from a network management node 202 in a network. Each access point identifier in the access point identifier list 216 is uniquely assigned to an access point with an IoT radio. The access point identifier can specify an access point location and / or an access point type. For example, the format of an access point identifier that specifies the location of the access point might be: {Location}-{Building}-{Floor}-{Quadrant}-{Extra Modifier}. Such an access point identifier gives the location of the access point in the form of the location (e.g., 122, 132, 142 in [location]). Fig. ), the name of the building at the location, the floor number in the building, the quadrant (e.g. East, West, North, South) of the floor, and an additional variable specified under "Extra Modifier".

[0046] In block 404, processor 204 can receive an initial rule list 218 from network management node 202. Each rule in the initial rule list contains a constraint and configuration values ​​for the access point. In some examples, each rule may also contain a penalty value. The penalty value can be used to change the objective function value in cases where the access point identifier does not satisfy a constraint in a rule (as in relation to...). Fig. (described further). In some examples, the rules can be created and deployed by a network administrator who operates the network management node 202. As described in Fig.As described, the rules can be in a key-value pair format. In some examples, the network management node 202 can create a key-value pair format using inputs provided by the network administrator. For example, the network administrator can provide the access point restrictions and configuration values ​​as input in a predefined syntax. An example rule based on the predefined syntax might be: "SELECT [AP_SEL_FUN] {IOT_RADIO_FW} {IOT_RADIO_PARAM} {PENALTY}". In such a rule, the restriction can be the access point selection function specified as "AP_SEL_FUN". The access point configuration values ​​can be the firmware type (specified as "IOT_RADIO_FW") and the protocols and power specification (specified as "IOT_RADIO_PARAM"). The penalty value can be a numeric value (specified as "PENALTY").Some examples of the rules in the rule list can be shown in Table 1. Table 1: Example rules based on a predefined syntax Rule Rule syntax First Rule SELECT [#if the {Extra Modifier} of the access point name matches "Elevator"] {iot_radio_firmware=default} {iot_radio_mode=zigbee}{penalty=-20} Second rule SELECT [#if access point name's {Floor} is greater than 1 and less than 5]{iot_radio_firmware=default} {iot_radio_mode=BLE} {penalty=-10} Third Rule

[0054] SELECT [#if the access point name {building} matches “warehouse”] {iot_radio_firmware=third party}{iot_radio_mode=ISA} {penalty=-90}

[0047] The first rule (in Table 1) specifies that the radio mode for all IoT radios on access points whose name contains "Elevator" should be set to Zigbee. The constraint, i.e., the access point selection function, is [#if access point name's {Extra Modifier} matches with "Elevator"], meaning that access point identifiers containing "Elevator" must be selected.

[0048] The second rule (in Table 1) specifies that the radio mode for all IoT radios connected to access points with names whose Floor values ​​are greater than 1 and less than 5 should be set to BLE. The constraint, i.e., the function for selecting the access points, is [#if access point name's {Floor} is greater than 1 and less than 5], which means that access points from the first to the fifth floor will be selected.

[0049] The third rule (in Table 1) specifies that the radio should be reprogrammed to third-party firmware to enable support for the ISA100 protocol for all IoT radios on access points with names where the building substring is "Warehouse". The constraint, i.e., the access point selection function, is [#if access point name's {Building} is 'Warehouse'], meaning that access points located in the Warehouse building will be selected.

[0050] Table 2 shows the restrictions (selection function for the access point) and the configuration values ​​for the access point in a key-value format. The key-value pairs can be specified, for example, in a configuration file 220. Table 2: Restriction and configuration values ​​in key-value pairs Rule {Key:Value} First Rule {[if the {Extra Modifier} of the access point name matches "Elevator"]: "iot_radio_firmware=default", "iot_radio_mode=zigbee"} Second rule {[#if the access point name {Floor} is greater than 1 and less than 5] :"iot_radio_firmware=default", "iot_radio_mode=BLE"}. Third Rule {[#if access point name's {Building} is ‚Warehouse‘] :„iot_radio_firmware=other", „iot_radio_mode=ISA"}.

[0051] In block 406, processor 204 can use an objective function to identify an access point identifier that satisfies the constraint specified in the rule. In some examples, the processor can use the objective function to identify a set of access point identifiers that satisfy one or more constraints specified in the rules. The identification of access point identifiers and the selection of access points based on the identification are described in the Fig. described in more detail.

[0052] In block 408, processor 204 can configure the access points associated with the access point identifier using the access point configuration values ​​specified in the standard. In some examples, configuring the access points might involve assigning the access point configuration values ​​to the access point based on the rule. Based on this assignment, a configuration file can be sent to the access point. In some examples, the configuration file might contain instructions for configuring the access point's configuration values.

[0053] In some examples, the Processor 204 can receive a second rule list from the network management node in the network. Each rule in the second rule list contains constraint and access point configuration values. The Processor 204 can identify an access point that satisfies the constraint specified in the second rule list by using the objective function. The Processor 204 can dynamically configure the access point with the access point configuration values ​​specified in the second rule list.

[0054] Fig. This is a flowchart illustrating a Procedure 500 for selecting access points for configuration according to an example. In block 502, processor 204 can select an initial combination of access point identifiers and access point configuration values. For example, the initial combination might include an access point identifier (e.g., AP_ID1 210) and multiple access point configuration values ​​(default firmware, Zigbee protocol, etc.). In some examples, the access point identifier can be randomly selected from the list of access point identifiers, and the access point configuration values ​​can be randomly selected from one of the rules in the initial rule list. For example, processor 204 might select an initial access point identifier (210 AP_ID1) from the access point identifier list (216) and access point configuration values ​​(e.g., default firmware, Zigbee protocol) from one of the rules in the initial rule list.In other examples, the access point identifiers and access point configuration values ​​can be selected arbitrarily from the network. For instance, the Processor 204 can obtain a complete list of the access point identifiers and access point configurations used in the network. Based on this complete list, the Processor 204 can select a random combination of access point identifiers and access point configuration values.

[0055] In block 504, processor 204 can calculate an objective function value for the first combination to determine if the first combination satisfies a rule in the first rule list. For example, the processor provides the first combination (AP_ID1 with default firmware and Zigbee protocol) and the rule list as input for an objective function to calculate the objective function value. The first combination satisfies a rule if the access point identifier satisfies a constraint specified in the rule and the access point's configuration values ​​match those specified in that rule. In cases where the combination satisfies a rule, the objective function value can increment (e.g., to a predefined value).

[0056] In block 506, processor 204 can determine whether the objective function value matches a predefined objective function value. In some examples, the predefined objective function value might be a predefined maximum or minimum objective function value. For example, the predefined objective function value might indicate that a particular input combination (AP_ID1 with default firmware and Zigbee protocol) satisfies a rule. In cases where the objective function does not match the predefined maximum or minimum value and specifies a penalty value for the rule, processor 204 can determine that the given combination does not satisfy the rule. In some examples, processor 204 can execute an optimization algorithm to vary the input for the objective function (i.e., provide a different combination of access point identifiers and access point configuration values).The processor can determine the objective function value for each of the different combinations provided as input. For example, processor 204 can iterate through procedure blocks 502-506 to select new combinations of the access point identifier and access point configuration values.

[0057] In block 508, processor 204 can select access point 106A, which is associated with access point ID AP_ID1, if the target function value for a given input combination matches the predefined target function value. Furthermore, in block 510, processor 204 can configure access point 106A with the access point configuration values, i.e., with the default firmware and the Zigbee protocol.

[0058] Fig. and Fig. These are flowcharts illustrating a procedure 600A-600B for identifying and selecting multiple access points for configuration according to another example. In block 602, processor 204 can randomly select multiple combinations (referred to as random multiple combinations) of access point identifiers and access point configuration values. For example, processor 204 can arbitrarily select multiple combinations of access identifiers and access point configuration values ​​from the complete list of access identifiers and configurations used in the network. The complete list of access point identifiers and configurations used in the network can be received, for example, from network management node 202.

[0059] In block 604, processor 204 can compute a random objective function value for the random multiple combinations using the objective function. For example, the random multiple combinations and a current network configuration can be provided as input to the objective function, and the random objective function value can be the output. The random objective function value can be a measure of the number of access point identifiers that are correctly paired with a set of access point configuration values ​​in the random multiple combinations. Correctness can refer, for example, to the current configuration of the access points in the network. The current configuration data can be obtained from the complete list of access points received from network management node 202. In some examples, processor 204 can execute an optimization algorithm to improve the random objective function value.to increase the number of correct combinations of access point identifiers and access point configuration values. For example, processor 204 can iterate steps 602 and 604 to vary the inputs (random multiple combinations) for the objective function and obtain an improved random objective function value.

[0060] In block 606, the processor 204 can select an initial multiple combination of access point identifiers and access point configuration values. These initial multiple combinations can differ from the random multiple combinations selected in block 602. For example, the initial multiple combinations can include access point identifiers arbitrarily selected from the list of access point identifiers and access point configuration values ​​arbitrarily selected from a rule in the first rule list 218. The initial multiple combination of access point identifiers and access point configuration values, as well as the rule list, can be provided as input for the objective function.

[0061] In block 608, processor 204 can compute an initial objective function value for the first multiple combinations using the objective function. In some examples, the objective function used to determine the random objective function value may differ from the objective function used to determine the initial objective function values. The initial objective function value may be a measure of the number of combinations that satisfy one or more rules from the first rule list 218. Rule satisfaction may involve determining whether the access point identifiers satisfy a constraint in the rule and whether the access point configuration values ​​match the access point configuration values ​​specified in the same rule. The initial objective function value may increment based on the number of combinations that satisfy the rule. For each combination that satisfies a rule, the initial objective function value increments.In cases where a combination fails to comply with a rule, the initial objective function value may decrease. This decrease could be based, for example, on a penalty value specified in the rule that was not met. The Processor 204 can determine that a combination fails to comply with a particular rule based on this penalty value.

[0062] In block 610, processor 204 can determine whether the first objective function value is greater than the random objective function value. For example, processor 204 can compare the quality of the first multiple combinations with the quality of the random multiple combinations. Quality can be understood as the correct combination of access point identifiers and access point configuration values. In cases where the first objective function value is less than or equal to the random objective function value, processor 204 can attempt to select improved first multiple combinations. For example, in block 606, processor 204 can select a new first multiple combination of access point identifiers and access point configuration values ​​in a subsequent iteration of 606, 608, and 610. In cases where the first objective function value is greater than the random objective function value, processor 204 can select the corresponding first multiple combination, e.g.,Stored in a cache. The stored first multiple combination is a more accurate combination of access point identifiers and access point configuration values ​​compared to random multiple combinations. The Processor 204 can use the stored first multiple combination as a base combination to determine other multiple combinations of access identifiers and access point configuration values ​​based on objective function values.

[0063] As in Fig. As shown, processor 204 in block 612 can select a second multiple combination of access point identifiers and access point configuration values. The second multiple combinations can be selected based on the base multiple combinations, such as the stored first multiple combinations. For example, the second multiple combinations can contain one or more combinations from the first multiple combinations.

[0064] In block 614, processor 204 can compute a second objective function value for the second multiple combinations using the objective function. This second objective function value can specify the accuracy of the selected second multiple combinations. In other words, the second objective function value can be a measure of the number of combinations that satisfy one or more rules from the first rule list 218. Rule satisfaction can involve determining whether the access point identifiers satisfy a constraint in the rule and whether the access point configuration values ​​match the access point configuration values ​​specified in the same rule.

[0065] In some examples, processor 204 can execute an optimization algorithm to improve the second objective function value, that is, to increase the number of combinations that satisfy a rule in the first rule list 218. For example, processor 204 can iterate steps 612 and 614 to vary the inputs to the objective function and obtain an improved second objective function value. To check whether the second objective function value has improved compared to the previous iteration, processor 204 can determine in block 616 whether the second objective function value remains unchanged. In cases where the second objective function value remains unchanged, processor 204 can determine that the highest number of combinations satisfying one or more rules in the first rule list 218 has been obtained.

[0066] In cases where the second objective function value is less than or greater than the previous second objective function value, the processor 204 can select another set of second combinations of access point identifiers and access point configuration values ​​in block 612. The processor 204 can iterate through blocks 612 to 616 until the second objective function value is the same as the one calculated in the previous iteration. In some examples where the second objective function value is less than the previous second objective function value, the processor 204 can additionally compare the second objective function value and the first objective function value to determine whether the second multiple combination is better than the basic multiple combination. In cases where the second objective function value is less than the first objective function value, the processor 204 can select the basic multiple combinations (i.e.,The first multiple combinations are used as second multiple combinations, and blocks 612-616 are re-executed. The baseline multiple combination allows the Processor 204 to discard a second multiple combination in cases where the number of combinations is small compared to the baseline multiple combinations.

[0067] Furthermore, in the example where the second objective function value remains unchanged with respect to the previous iteration (i.e., the highest number of combinations that satisfy one or more rules in the first rule list 218), processor 204 can store in a cache memory that the second set of multiple combinations of access point identifiers and access point configuration values ​​are available. In block 618, processor 204 can select the access points associated with the access identifiers from the cache memory for configuration with access configuration values.

[0068] As described here, the example procedure 600A-600B enables the configuration of multiple access points with access point configuration values ​​at a single site. Configuring multiple access points can be performed with less manual intervention. For example, a network administrator (e.g., the network management node 202) can provide a set of rules (e.g., the first rule list 218) and the access point identifiers 216, and the example procedure described here can automatically select accurate combinations of access point identifiers and access point configuration values.

[0069] Fig. Figure 700 shows a block diagram with a processor 702 and a machine-readable medium 704 encoded with example instructions to facilitate the reconfiguration of IoT radio access points, in accordance with an example. The machine-readable medium 704 can be non-transitory and is alternatively referred to as non-transitory machine-readable medium 704. As detailed here, the machine-readable medium 704 can be loaded with executable instructions 706, 708, 710, and 712 (hereafter collectively referred to as instructions 706-712) to perform the operation described in Figure 700. Fig. The described procedure 400 may be encoded. Although not shown, in some examples the machine-readable medium 704 may be encoded with certain additional executable instructions to execute the procedure 400. Fig.and / or to perform other operations executed by the management node 102, without limiting the scope of this disclosure. In some examples, the machine-readable medium 704 can be accessed by the processor 702. In some examples, the processor 702 can represent an example of the processor 204 of the management node 102. Furthermore, the machine-readable medium 704 can represent an example of the machine-readable medium 206 of the management node 102. In some examples, the processor 702 can retrieve, decode, and execute the instructions 706-712 stored on the machine-readable medium 704 to perform a reconfiguration of IoT radio access points.

[0070] Instructions 706, when executed by Processor 702, can cause Processor 702 to receive an access point identifier list from a network management node in a network. Each access point identifier in the access point identifier list can be uniquely associated with an access point device equipped with an Internet of Things (IoT) radio. Instructions 708, when executed by Processor 702, can cause Processor 702 to receive an initial rule list from the network management node. Each rule in the initial rule list can specify a constraint and access point configuration values. Furthermore, instructions 710, when executed by Processor 702, can cause Processor 702 to identify an access point identifier that satisfies the constraint specified in the rule by using a target function.Furthermore, when executed by processor 702, instructions 712 can cause processor 702 to configure the access point device associated with the access point identifier with the access point configuration values ​​that are usually specified.

[0071] Although specific implementations have been shown and described above, various changes in form and details are possible. For example, some features and / or functions described in relation to one implementation and / or process may be transferred to other implementations. In other words, processes, features, components, and / or properties described in relation to one implementation may also be useful in other implementations. Furthermore, it should be noted that the systems and procedures described here may include various combinations and / or sub-combinations of the components and / or features of the different implementations described.

[0072] The foregoing description includes numerous details to facilitate understanding of the subject matter disclosed herein. However, the implementation can also be carried out without some or all of these details. Other implementations may involve modifications, combinations, and variations of the details described above. The following claims are intended to cover such modifications and variations.

Claims

[1] Procedure (400), comprising: Receiving (402) by a processor (204; 704) an access point identifier list (216) from a network management node (202) in a network (120), wherein the access point identifier list (216) comprises a plurality of access point identifiers (210, 212, 214) and wherein each access point identifier in the access point identifier list (216) is uniquely associated with an access point (106A-C) comprising an Internet of Things (IoT) radio device (108A-C) capable of supporting IoT protocols; Received (404), by the processor (204; 704), a first rule list (218) from the network management node (202), where a rule in the first rule list (218) specifies a restriction and an access point configuration value; iterative selection of a new combination of an access point identifier from the access point identifier list (216) and the access point configuration value using an objective function until the objective function obtains an objective function value for the access point identifier that exceeds the constraint usually specified; Identify (406), by the processor (204; 704), the access point identifier that satisfies the usually specified constraint, using the objective function; and Configure (408) the access point associated with the access point identifier, by the processor (204; 704), with the access point configuration value usually specified. [2] Method (400) according to claim 1, wherein the iterative selection of the new combination of the access point identifier from the access point identifier list (216) and the access point configuration value further comprises: Select, by the processor (204; 704), a first combination of a second access point identifier from the access point identifier list (216) and a second access point configuration value; Calculate, by the processor (204; 704), a second objective function value for the first combination of the second access point identifier and the second access point configuration value using the objective function; Determine, using the processor (204; 704), whether the second objective function value matches a predefined objective function value; and In response to a determination that the second objective function value matches the predefined objective function value, the processor (204; 704) selects the access point associated with the second access point identifier to be configured with the second access point configuration value. [3] Method (400) according to claim 2, further comprising: In response to a determination that the second objective function value does not match the predefined objective function value, the processor (204; 704) performs a next iteration of selecting, calculating, and determining. [4] Method (400) according to claim 1, further comprising: Identify, by the processor (204; 704), several access point identifiers (210, 212, 214) that satisfy the constraint, usually specified in the first rule list (218), using the objective function. [5] The method of claim 4, further comprising: Select, by the processor (204; 704), a combination of each access point identifier from the identified multiple access point identifiers (210, 212, 214) with a respective access point configuration value from the first rule list (218); Calculate, by the processor (204; 704), an objective function value for each combination using the objective function; and If the respective objective function values ​​for the respective combinations are the same, the processor (204; 704) selects the respective access points for configuration with the same access point configuration values. [6] The method (400) according to claim 1, further comprising: Received by the processor (204; 704), a second rule list from the network management node (202) in the network (120), wherein each rule in the second rule list includes a second constraint and a second access point configuration value; Identify, by the processor (204; 704), an access point identifier that satisfies the second constraint usually specified in the second rule list, using the objective function; and Configure, by the processor (204; 704), of the access point with the second access point configuration value, which is usually specified in the second rule list. [7] Method (400) of claim 1, wherein configuring the access point with the access point configuration value usually specified comprises: Assign, by the processor (204; 704), the access point configuration value to the access point (106A-C) based on the rule; and Sending, through the processor (204; 704), a configuration file (220) to the access point (106A-C), where the configuration file (220) specifies the configuration value assigned to the access point (106A-C). [8] Method (400) according to claim 1, wherein the access point identifier comprises one or more of a location and a type of access point. [9] Method (400) according to claim 1, wherein the configuration value of the access point comprises one or more of a firmware, protocol and performance specifications. [10] Method (400) according to claim 1, wherein the restriction specifies an access point selection function comprising at least one of an access point location and an access point type. [11] Administrative node (102) comprising the following: a processor (204); a machine-readable medium (206) that stores instructions which, when executed by the processor (204), cause the processor (204) to: Receiving an access point identifier list (216) from a network management node (202) in a network (120), wherein the access point identifier list (216) comprises a plurality of access point identifiers (210, 212, 214) and wherein each access point identifier in the access point identifier list (216) is uniquely associated with an access point (106A-C) comprising an Internet of Things (IoT) radio device (108A-C) capable of supporting IoT protocols; Receiving an initial rule list (218) from the network management node (202), wherein a rule in the initial rule list (218) specifies a restriction and an access point configuration value; iterative selection of a new combination of an access point identifier from the access point identifier list (216) and the access point configuration value using an objective function until the objective function obtains an objective function value for the access point identifier that exceeds the constraint usually specified; Identifying the access point identifier that satisfies the typically specified constraint, using the objective function; and Configure the access point associated with the access point identifier using the access point configuration value that is usually specified. [12] Management node (102) according to claim 11, wherein the instructions further cause the processor (204) to: Receiving a second rule list from the network management node (202) in the network (120), wherein each rule in the second rule list includes a second constraint and a second access point configuration value; Identifying a second access point identifier that satisfies the second constraint typically specified in the second rule list, using the objective function; and Configure the access point with the second configuration value, which is usually specified in the second rule list. [13] Management node (102) according to claim 11, wherein the instructions further cause the processor (204) to: Selecting a first combination of a second access point identifier from the access point identifier list (216) and a second access point configuration value; Calculating a second objective function value for the first combination of the second access point identifier and the second access point configuration value using the objective function; Determine whether the second objective function value matches a predefined objective function value; and Selecting the access point associated with the second access point identifier for configuration with the second access point configuration value in response to the objective function value matching the predefined objective function value. [14] Management node (102) according to claim 11, wherein the instructions further cause the processor (204) to: Identify multiple access point identifiers (210, 212, 214) that satisfy the constraint usually specified in the first rule list (218) using the objective function. [15] Management node (102) according to claim 14, wherein the instructions further cause the processor (204) to: Selecting a combination of each access point identifier from the identified multiple access identifiers with a respective access point configuration value from the first rule list (218); Calculating an objective function value for each combination using the objective function; and If the respective objective function values ​​are the same for the respective combinations, select the respective access points for configuration with the same access point configuration values. [16] Management node (102) according to claim 11, wherein the access point configuration value comprises a firmware, a protocol and a performance specification. [17] Non-transitory machine-readable medium (206; 706) storing instructions that can be executed by a processor (204; 704), the instructions comprising: Instructions for receiving an access point identifier list (216) from a network management node (202) in a network (120), wherein the access point identifier list (216) comprises a plurality of access point identifiers (210, 212, 214) and wherein each access point identifier in the access point identifier list (216) is uniquely associated with an access point (106A-C) comprising an Internet of Things (IoT) radio device (108A-C) capable of supporting IoT protocols; Instructions for receiving an initial rule list (218) from the network management node (202), wherein a rule in the initial rule list (218) specifies a restriction and an access point configuration value; Instructions for iteratively selecting a new combination of an access point identifier from the access point identifier list (216) and the access point configuration value using an objective function until the objective function obtains an objective function value for the access point identifier that exceeds the constraint usually specified; Instructions for identifying the access point identifier that satisfies the usually specified constraint, using the objective function; and Instructions for configuring the access point associated with the access point identifier, using the access point configuration value that is usually specified. [18] Non-transitory machine-readable medium (206; 706) according to claim 17, wherein the instructions for iteratively selecting the new combination of the access point identifier from the access point identifier list (216) and the access point configuration value further comprise instructions for: Selecting a first combination of a second access point identifier from the access point identifier list (216) and a second access point configuration value; Calculating a second objective function value for the first combination of the second access point identifier and the second access point configuration value using the objective function; Determine whether the objective function value matches a predefined objective function value; and Selecting the access point associated with the second access point identifier for configuration with the second access point configuration value in response to the second objective function value matching the predefined objective function value. [19] Non-transitory machine-readable medium according to claim 17, further comprising instructions for: identifying multiple access point identifiers (210, 212, 214) that satisfy the constraint typically specified in the first rule list (218) using the objective function. [20] Non-transitory machine-readable medium according to claim 19, wherein the instructions for identifying the multiple access point identifiers further comprise instructions for: Selecting a combination of each access identifier from the identified multiple access point identifiers with a respective access point configuration value from the first rule list(218); Calculating an objective function value for each combination using the objective function; and If the respective objective function values ​​are the same for the respective combinations, select the respective access points for configuration with the same access point configuration values.

Images