COMMUNICATION DEVICE, CONTROL METHOD AND PROGRAM FOR COMMUNICATION DEVICE

Abstract

To provide a communication device that, in a wireless network formed by a plurality of access points, can appropriately update firmware of the plurality of access points.SOLUTION: A communication device can operate an access point in a wireless network including a plurality of access points, acquires information on firmware of the other access points other than the communication device, of the plurality of access points, determines a schedule in which the firmware of the other access points should be updated based on the acquired information on the firmware, and notifies the other access points of information on the determined schedule.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a communication device operable as an access point in a wireless network. [Background technology]

[0002] The Wi-Fi EasyMesh (registered trademark) standard established by the Wi-Fi Alliance stipulates various controls for networks formed by multiple access points (hereinafter also referred to as "APs"). A network formed by such multiple APs working together is hereinafter referred to as a "multi-AP network." In the Wi-Fi EasyMesh standard, APs that form a multi-AP network can obtain various information from other APs and use that information to achieve efficient network control between multiple APs.

[0003] An AP forming a multi-AP network operates as either a Multi-AP Controller (hereinafter referred to as a "controller") or a Multi-AP Agent (hereinafter referred to as an "agent"). The controller is an AP that acquires various information about APs in a multi-AP network and stations (hereinafter, also referred to as "STAs") connected to the APs from the agent, and uses the acquired information to perform efficient network control among multiple APs. On the other hand, the agent is an AP that is under the management of the controller and notifies the controller of various network information. The controller function may be performed by an AP or a control device in a multi-AP network. Also, one AP may perform both the controller and agent functions.

[0004] The controller controls the multi-AP network by issuing instructions to the agents based on network information notified from the agents using a protocol defined in the IEEE 1905.1 standard. The network information notified from the agents to the controller includes network topology information, discovery information, etc. The controller also performs proxy control of data communication and data traffic management between the multi-AP network and the public line network.

[0005] Patent Document 1 discloses a connection control device that distributes the communication load in a network formed by a plurality of APs by switching an AP to which a wireless terminal is connected. Specifically, in the technology of Patent Document 1, the connection control device acquires information on the communication load in the plurality of APs, and when an AP is in an overloaded state based on the communication load information, it determines one terminal to be disconnected from among a plurality of STAs connected to the AP. The connection control device further transmits a connection prohibition command to the terminal to be disconnected to APs other than the AP to be switched to, to which the terminal to be connected can be newly connected, and transmits a disconnection command to the AP in an overloaded state after transmitting the connection prohibition command. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2017-038126 A Summary of the Invention [Problem to be solved by the invention]

[0007] Incidentally, in a multi-AP network, from the viewpoints of security and interconnectivity, it is desirable that the firmware of each of the multiple APs that make up the multi-AP network is the latest. This is because, for example, if there is even one AP with a vulnerability problem, the security of the entire multi-AP network may be reduced. Also, if there is an AP with an old version of firmware in the multi-AP network, it may cause problems in controlling the multi-AP network, and the multi-AP network may not be managed as expected.

[0008] On the other hand, a multi-AP network is a mesh network in which each AP has many connections, and from the viewpoint of topology control, it is undesirable to update the firmware of each AP in a disorderly manner, because, for example, simply updating the firmware of an AP that is connected to other APs or an AP that is connected to many STAs may cause a large-scale communication outage.

[0009] An object of the present invention is to provide a communication device capable of appropriately updating firmware of a plurality of access points in a wireless network formed by the plurality of access points. [Means for solving the problem]

[0010] In order to solve the above problems, a communication device according to the present invention is a communication device that operates as one access point in a wireless network consisting of a plurality of access points, and includes an acquisition means for acquiring firmware information of an access point other than the communication device among the plurality of access points, a decision means for deciding a schedule for updating firmware of at least one other access point among the plurality of access points based on the firmware information acquired by the acquisition means, a notification means for notifying the at least one other access point of the schedule information decided by the decision means, and a notification means for updating the at least one other access point based on the schedule. otherBefore updating the firmware of the access point, the at least one other A station connected to an access point is different from the at least one access point. a and a control means for controlling a steering process so as to connect to an access point, and when updating firmware for two or more access points, the determination means determines the schedule based on information about the firmware acquired by the acquisition means so as to prevent the firmware updates from overlapping in time among the multiple access points when updating firmware for two or more access points. Effect of the Invention

[0011] According to the present invention, in a wireless network formed by a plurality of access points, it is possible to appropriately update firmware of the plurality of access points. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an example of a network configuration of a communication system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram showing an example of the hardware and functional configuration of a communication device (controller) according to the first embodiment. [Diagram 3] FIG. 2 is a block diagram showing an example of the hardware and functional configuration of a communication device (agent) according to the first embodiment. [Figure 4] 10 is a flowchart showing an example of a processing procedure of a firmware update management process executed when the communication device according to the first embodiment operates as a controller. [Diagram 5] 6 is a flowchart showing an example of a procedure of a firmware update process executed when the communication device according to the first embodiment operates as an agent. [Figure 6] FIG. 4 is a sequence diagram showing an example of a firmware update processing sequence between communication devices in the communication network according to the first embodiment. [Figure 7]10 is a flowchart showing an example of a procedure of a firmware update management process executed when a communication device according to a second embodiment operates as a controller. [Figure 8] 10 is a flowchart showing an example of a procedure of a firmware update process executed when a communication device according to a second embodiment operates as an agent. [Figure 9] FIG. 11 is a sequence diagram showing an example of a firmware update processing sequence between communication devices in a communication network according to the second embodiment. [Figure 10] 11 is a flowchart showing an example of a procedure of a firmware update management process executed when a communication device according to a third embodiment operates as a controller. [Figure 11] 11 is a flowchart showing an example of a procedure of a firmware update process executed when a communication device according to a third embodiment operates as an agent. [Figure 12] FIG. 11 is a sequence diagram showing an example of a firmware update processing sequence between communication devices in a communication network according to a third embodiment. [Figure 13] 13 is a flowchart showing an example of a processing procedure of a firmware update management process executed when a communication device according to a fourth embodiment operates as a controller. [Figure 14] 13 is a flowchart showing an example of a procedure of a firmware update process executed when a communication device according to a fourth embodiment operates as an agent. [Figure 15] FIG. 13 is a sequence diagram showing an example of a firmware update processing sequence between communication devices in a communication network according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment for carrying out the present invention will be described in detail with reference to the attached drawings. Note that the embodiment described below is one example of a means for realizing the present invention, and should be appropriately modified or changed depending on the configuration of the device to which the present invention is applied and various conditions, and the present invention is not limited to the following embodiment. Also, not all of the combinations of features described in the present embodiment are necessarily essential to the solution of the present invention.

[0014] Hereinafter, an example will be described in which the communication device is a communication device that complies with the Wi-Fi EasyMesh standard that allows a multi-AP network formed by multiple access points (APs), but the present embodiment is not limited to this. For example, the communication device may use another communication method that enables wireless communication in a multi-AP network, which is a wireless network formed by multiple APs. The Wi-Fi EasyMesh standard complies with the specifications published by the Wi-Fi Alliance as "Multi-AP Specification Version 1.0" and subsequent specifications.

[0015] (Embodiment 1) <Network Configuration of the Present Embodiment> In this embodiment, an access point (AP) that operates as a controller adjusts the schedule for updating firmware of other APs that operate as agents, and notifies the other APs of information about the adjusted schedule. In this embodiment, the firmware to be updated is software for controlling the hardware of the communication device, and is usually software that is pre-written in the non-volatile storage device of the communication device and then installed in the communication device. The firmware may include microcode that determines the operation of the CPU (Central Processing Unit) installed in the communication device, a BIOS (Basic Input / Output System), etc.

[0016] FIG. 1 is a diagram showing an example of a network configuration of a communication system according to the present embodiment. The communication system shown in FIG. 1 includes communication devices 1 to 5 connected to a multi-AP network 6, which is a network made up of a plurality of APs, and performs wireless communication on the multi-AP network 6.

[0017] Each of communication device 1, communication device 2, communication device 3, and communication device 4 operates as an access point (AP) that constructs a wireless LAN (Local Area Network) that complies with the IEEE802.11 series standard. Meanwhile, communication devices 5a to 5e operate as stations (STAs) that connect to the wireless LAN constructed by the APs, communication device 2, communication device 3, or communication device 4. Hereinafter, communication devices 1 to 4 are also referred to as AP1 to AP4, and communication devices 5a to 5e are also referred to as STA5a to STA5e.

[0018] AP1 establishes a wireless LAN network and is connected to other APs, AP2 and AP3. AP2 and AP3 are each connected to AP1 via wireless LAN as stations (STAs) for AP1 through backhaul communication relaying an access line and a core network. AP4 is connected to AP2 via wireless LAN as a STA for AP2 through backhaul communication, and is controlled by AP1, which is a controller, via AP2. It should be noted that the APs AP1 to AP4 may be communication devices having an access point function, and are not required to be dedicated devices that provide an access point.

[0019] 1, AP1 is connected to a WAN (Wide Area Network) 7 and operates as a gateway capable of relaying communications of other APs 2 to 4 and STAs 5a to 5e and connecting them to the WAN 7. Any of APs 2 to 4 may operate as a gateway instead of AP 1. Note that APs 1 to 4 may be capable of performing wired communications in addition to or instead of wireless communications.

[0020] The Wi-Fi EasyMesh standard specifies that in a multi-AP network, there is one controller, but multiple agents are allowed. 1, AP1 plays the role of a controller having a function of controlling other APs in the multi-AP network 6 and controlling the entire multi-AP network 6. On the other hand, AP2 to AP4, which are the other APs that do not play the role of controllers, are under the management of the controller and play the role of agents having a function of notifying the controller of network information. 1, STA5a is connected to AP2 via a wireless LAN by fronthaul communication that connects a master station and a slave station. Similarly, STA5b and STA5c are connected to AP3, and STA5d and STA5e are connected to AP4 via fronthaul communication.

[0021] 1, the multi-AP network 6 is a wireless LAN network that complies with the Wi-Fi EasyMesh standard and the IEEE802.11. The multi-AP network 6 is constructed by AP1, which is a controller AP, and is formed by AP1 and AP2 to AP4, which are agent APs. Note that the Wi-Fi EasyMesh standard and the IEEE802.11 standard are merely examples, and other standards having similar functions may be used.

[0022] The multi-AP network 6 may be a network conforming to Wireless Universal Serial Bus (USB), MultiBand OFDM Alliance (MBOA), or Bluetooth (registered trademark). The multi-AP network 6 may also be a network conforming to Ultra Wide Band (UWB), ZigBee (registered trademark), Near Field Communication (NFC), etc. UWB includes Wireless USB, Wireless 1394, and WINET, etc.

[0023] 1 may be communication devices capable of operating as APs conforming to the Wi-Fi EasyMesh standard and having the hardware and functional configurations described below with reference to FIG. 2 and FIG. 3. The APs 1 to 4 may be devices such as, but are not limited to, a wireless LAN (Local Area Network) router, a PC, a tablet terminal, a smartphone, a television, a printer, a copier, a projector, etc. The APs 1 to 4 may be devices different from each other. Similarly, the STAs 5a to 5e shown in FIG. 1 may be any communication devices capable of operating as STAs conforming to the Wi-Fi EasyMesh standard, and the type of device is not limited.

[0024] <Hardware and functional configuration of communication device> Fig. 2 is a diagram showing an example of the hardware and functional configuration of a communication device capable of operating as a controller according to the present embodiment. Hereinafter, a communication device having the hardware and functional configuration shown in Fig. 2 will be described with reference to AP1 in Fig. 1, but AP2 to AP4 may also have the hardware and functional configuration shown in Fig. 2. An AP that plays the role of a controller may also have an agent function. In this embodiment, an example will be described in which AP1 shown in FIG. 1 has both the controller and agent functions, and AP2 to AP4 have only the agent function, but this embodiment is not limited to this. Any of AP1 to AP4 shown in FIG. 1 may have both the controller and agent functions, or may have only one of the controller and agent functions.

[0025] The communication device 1 (AP1) in FIG. 2 includes a power supply unit 11, an input unit 12, an output unit 13, a wireless communication unit 14, a storage unit 15, a control unit 16, and an antenna 17. 2 are communicatively connected to each other via a system bus 18. Note that the AP1 does not need to include all of the above modules, and may include additional modules in addition to the configuration in FIG.

[0026] The power supply unit 11 supplies power to each hardware component of the AP 1. The power supply unit 11 may obtain power from, for example, an AC power source or a battery. The input unit 12 receives various operations from the user via a pointing device such as a mouse, voice input, button operations, and the like. The output unit 13 performs various outputs to the user. Here, the output by the output unit 13 may include, for example, at least one of display on an LED (Light Emitting Diode), display on a screen, audio output by a speaker, vibration output, etc. Alternatively, both the input unit 12 and the output unit 13 may be realized by one module, such as a touch panel.

[0027] The wireless communication unit 14 controls wireless LANs conforming to the IEEE802.11 series standards, which are protocols for the physical layer and data link layer, and wired communications such as wired LANs conforming to the IEEE802.3 standard. The wireless communication unit 14 also controls Internet Protocol (IP) communications, which are communications protocols for the network layer. The wireless communication unit 14 also controls the controller and / or agent in accordance with the Wi-Fi EasyMesh standard, and controls the antenna 17 to transmit and receive wireless signals for wireless communications.

[0028] The storage unit 15 is configured with one or more memories such as a ROM (Read Only Memory) or a RAM (Random Access Memory), and stores information such as programs for executing various operations described below and communication parameters for wireless communication. In addition to memories such as a ROM or a RAM, the storage unit 15 may be a storage medium such as a flexible disk, a hard disk, an optical disk, a CD-ROM, a CD-R, a magnetic tape, a non-volatile memory card, or a DVD. The storage unit 15 may include multiple memories.

[0029] The programs stored in the storage unit 15 include programs for executing controller control and agent control in a multi-AP network compliant with Wi-Fi EasyMesh memory. The firmware is stored in a non-volatile memory, such as a flash memory or a ROM, in the storage unit 15. When the firmware is stored in a ROM, the firmware may be stored in an EEPROM (Electrically Erasable Programmable ROM) that is rewritable without the need for replacement. Alternatively, the firmware may be stored in an EPROM (Erasable Programmable ROM).

[0030] The control unit 16 is configured with one or more processors such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). The control unit 16 performs overall control of the entire AP 1 by executing a program stored in the storage unit 15. The control unit 16 may control the entire AP 1 in cooperation with the program stored in the storage unit 15 and an OS (Operating System).

[0031] In this embodiment, the control unit 16 includes a controller unit 161 and an agent unit 162. The controller unit 161 operates as a controller in the multi-AP network by the control unit 16 reading out from the storage unit 15 a program for executing controller control in the multi-AP network and executing it. Similarly, the agent unit 162 operates as an agent in the multi-AP network by the control unit 16 reading out from the storage unit 15 a program for executing agent control in the multi-AP network and executing it. The AP 1 executes at least one of the functions of a controller and an agent in accordance with settings and operations on the AP 1. The control unit 16 can enable and disable the functions of the controller and the agent individually.

[0032] When operating as a controller of the multi-AP network, the AP 1 controls the multi-AP network 6 by issuing instructions to the agent based on network topology information and discovery information received from the agent. When acting as an agent of a multi-AP network, AP1 notifies the controller of network information, such as network topology information. If the communication device 1 does not play the role of a controller, the communication device 1 may not have a controller function. Similarly, if the communication device 1 does not play the role of an agent, the communication device 1 may not have an agent function.

[0033] Fig. 3 is a diagram showing an example of the hardware and functional configuration of a communication device capable of operating as an agent according to the present embodiment. Hereinafter, a communication device having the hardware and functional configuration shown in Fig. 3 will be described with reference to AP2 in Fig. 1, but AP3 and AP4 may also have the hardware and functional configuration shown in Fig. 3. The communication device 2 (AP2) in FIG. 3 includes a power supply unit 21, an input unit 22, an output unit 23, a wireless communication unit 24, a storage unit 25, a control unit 26, and an antenna 27. 3 are communicatively connected to each other via a system bus 28. The AP 2 does not need to include all of the above modules, and may include additional modules in addition to the configuration in FIG. The control unit 26 includes an agent unit 262 that causes the AP 2 to operate as an agent. Each unit of the AP 2 in Fig. 3 performs the same function as each unit of the AP 1 shown in Fig. 2, except that the control unit 26 does not include a controller unit.

[0034] <Firmware update management process> Fig. 4 is a flowchart showing an example of a firmware update management process executed when a communication device that is an AP operates as a controller in the multi-AP network 6. The firmware update management process is a process for managing firmware updates of AP2 to AP4 that are agents. For the sake of convenience, the following description will be given assuming that AP1 in Fig. 1 operates as the controller, but AP2 to AP4 may execute the process shown in Fig. 4 as the controller instead of AP1. Each step in Fig. 4 is realized by the control unit 16 reading and executing a program stored in the storage unit 15 of the AP 1 when the AP 1 is powered on. Alternatively, instead of when the AP 1 is powered on, each step in Fig. 4 may be executed when a predetermined operation mode such as a communication setting mode is entered by a user operation or the like, or when a predetermined application such as a communication setting application is started. Each step in Fig. 4 may be executed periodically at a predetermined interval while the multi-AP network 6 is formed.

[0035] At least a part of the flowchart shown in Fig. 4 may be realized by hardware. When it is realized by hardware, for example, a specific compiler may be used to automatically generate a dedicated circuit on an FPGA from a program for realizing each step. FPGA is an abbreviation for Field Programmable Gate Array. Also, a gate array circuit may be formed in the same manner as an FPGA, and realized as hardware. Also, it may be realized by an ASIC (Application Specific Integrated Circuit). In this case, each block in the flowchart shown in Fig. 4 can be regarded as a hardware block. Note that multiple blocks may be combined into one hardware block, and one block may be configured as multiple hardware blocks.

[0036] In S101, the controller unit 161 of AP1 transmits a message inquiring about the firmware information of each of AP2 to AP4, which are agents forming the multi-AP network 6. The controller unit 161 broadcasts this message inquiring about the firmware information to the multi-AP network 6 including AP2 to AP4. The firmware information that the controller unit 161 inquires of the agents AP2 to AP4 includes a firmware version number specific to each AP, and a firmware write or update date. The firmware information further includes the version number of the Wi-Fi EasyMesh standard that the AP supports.

[0037] In S102, the controller unit 161 of AP1 receives firmware information transmitted from each of the agent APs AP2 to AP4 other than its own communication device as a response to the inquiry in S101. In S103, the controller unit 161 of AP1 refers to the firmware information received from AP2 to AP4 in S102, and adjusts the schedule for the times when AP2 to AP4, which are agents, should update their firmware.

[0038] Specifically, the controller unit 161 may determine the time to update firmware in each AP so that firmware is not updated at the same time among the multiple APs 2 to 4, i.e., so that there is no temporal overlap. The controller unit 161 may also adjust the schedule so that an AP with an older firmware or Wi-Fi EasyMesh standard version number is given priority and the firmware is updated earlier than other APs. Similarly, the controller unit 161 may adjust the schedule so that an AP with an older firmware date is given priority and the firmware is updated earlier than other APs. The controller unit 161 may further determine the time and order for updating firmware in each AP based on network topology information, network load information, and congestion information received from each of the APs 2 to 4.

[0039] In S104, the controller unit 161 of AP1 transmits the schedule information adjusted in S103 to each of AP2 to AP4. The schedule information transmitted by the controller unit 161 to each of AP2 to AP4 includes information on the time at which the firmware update should be performed in the corresponding AP. Each of the agents AP2 to AP4 performs a firmware update in accordance with the schedule information transmitted in S104. In S105, the controller unit 161 of the AP1 receives notifications from the AP2 to AP4, each of which notifies the completion of the firmware update. The controller unit 161 of the AP1 starts the process of S101 at a predetermined interval, and repeats the processes of S101 to S105.

[0040] <Firmware update process> Fig. 5 is a flowchart showing an example of a firmware update process executed when a communication device that is an AP operates as an agent in the multi-AP network 6. For the sake of convenience, the following description will be given assuming that AP2 in Fig. 1 operates as an agent, but similar firmware update processes are also executed in AP3 and AP4 that are agents. Note that each step shown in FIG. 5 is executed while AP2 is forming a multi-AP network.

[0041] In S201, the agent unit 262 of AP2 receives a message sent from AP1, inquiring about firmware information of AP2. In S202, the agent unit 262 of AP2 responds to the inquiry received in S201 by transmitting firmware information of AP2 to AP1. The firmware information transmitted to AP1 in S202 includes AP-specific firmware version information, firmware writing or update date, and the version number of the supported Wi-Fi EasyMesh standard. Based on the firmware information of AP2 transmitted to AP1 in S202, the AP1 executes schedule adjustment of firmware update times among the agents AP2 to AP4.

[0042] In S203, the agent unit 262 of AP2 receives schedule information transmitted from AP1, the schedule information including information on the time when firmware update should be performed in AP2. In S204, the agent unit 262 of AP2 refers to the schedule information received from AP1 in S203, and performs steering of the STAs to connect to AP2 before the time arrives when the firmware update should be performed in AP2. Specifically, the agent unit 262 executes a process of disconnecting all or some of the STAs connected to AP2 and prohibiting other APs from connecting to these STAs. Furthermore, the agent unit 262 steers (roams) the STAs to be disconnected, if possible, to connect them to either AP3 or AP4, which are other APs forming the multi-AP network 6.

[0043] In S205, the agent unit 262 of AP2 executes the firmware update at the time when the firmware update should be executed in AP2, which is included in the schedule information received from AP1 in S203. In S206, the agent unit 262 of AP2 transmits a notification to AP1 that the firmware update of AP2 has been completed. If the firmware update of AP2 has failed, the agent unit 262 may notify the AP1, which is the controller, of this fact.

[0044] <Control sequence for firmware update in a multi-AP network> FIG. 6 shows an example of a control sequence for firmware update processing between APs in the multi-AP network 6. In FIG. In S61, when the multi-AP network 6 is formed, AP1, which is the controller, transmits a message inquiring about firmware information in each AP to AP2 to AP4, which are agents forming the multi-AP network 6. Specifically, AP1 broadcasts a message inquiring about firmware information in each AP to the multi-AP network 6 including AP2 to AP4. In S62, AP2 to AP4 that have received the firmware information inquiry message each transmit the firmware information of the AP to AP1 as a response to the inquiry.

[0045] In S63, the AP1 adjusts the schedule for firmware update times among the plurality of APs 2 to 4 based on firmware information received from each of the APs 2 to 4. In S64, AP1 transmits schedule information including the scheduled firmware update times to AP2 to AP4, respectively. Here, it is assumed that the schedules of firmware updates among AP2 to AP4 are adjusted so that firmware updates are executed in the order of AP2, AP3, and AP4.

[0046] In S65, AP2 executes steering of the STA connected to AP2 to another agent AP before the firmware update time included in the schedule information received by AP2 arrives. In S66, AP2 updates its own firmware at the firmware update time included in the schedule information received by AP2. In S67, AP2 transmits a notification to AP1 that the firmware of AP2 has been updated.

[0047] Similarly, in S68, AP3 executes steering of the STA connected to AP3 to another agent AP before the arrival of the firmware update time included in the schedule information received by AP3. It is assumed that the schedule information received by AP3 specifies a firmware update time later than the firmware update time of AP2. In S69, the AP3 updates its own firmware at the firmware update time included in the schedule information received by the AP3, and in S70, the AP3 transmits a notification to the AP1 that the firmware of the AP3 has been updated. Although not shown, AP4 may also execute the same processes as S65 to S67 and S68 to S70 based on a firmware update time that is later than both AP2 and AP3. Alternatively, if the schedule information transmitted to AP4 in S64 indicates that a firmware update is not required in AP4, a firmware update in AP4 may not be executed.

[0048] If AP1 does not receive a firmware update completion notification from each of the agents AP2 to AP4 even after a predetermined time has elapsed since the adjusted time, and a timeout occurs, AP1 may adjust the schedule again. Alternatively, if AP1 receives a firmware update failure notification from the agent AP, AP1 may adjust the schedule again. Alternatively, APs where a timeout has occurred or APs that have sent failure notifications may be excluded from the firmware update targets, and a predetermined error message may be output indicating that the firmware update will not be executed.

[0049] As described above, according to this embodiment, the communication device operating as the controller acquires firmware information of each communication device from the communication device operating as the agent, adjusts the schedule for updating firmware among the multiple communication devices, and notifies the multiple communication devices of the adjusted schedule. In addition, the communication device operating as an agent transmits firmware information of its own device to the communication device operating as the controller, and performs firmware updates based on a schedule received from the communication device operating as the controller.

[0050] As a result, in a wireless network formed by multiple access points, the controller can schedule firmware updates among multiple agents so that they do not overlap. Also, since the agent can obtain a schedule for updating firmware in its own device in advance, it can perform preparations such as firmware download and STA steering before performing a firmware update. Therefore, in a wireless network formed by multiple access points, the firmware of the multiple access points can be appropriately updated without impairing the network connectivity and availability of the STAs.

[0051] (Embodiment 2) Hereinafter, the second embodiment will be described in detail with reference to Figs. 7 to 9, focusing only on the differences from the first embodiment. In the first embodiment, the controller in the multi-AP network notifies each agent of an adjusted schedule for updating firmware in the agent, and each agent updates the firmware. In contrast, in the present embodiment, the controller in the multi-AP network broadcasts a schedule and an instruction to start firmware update to multiple agents forming the multi-AP network. Then, prior to the firmware update, multiple access points cooperate with each other to perform steering of the STA. The hardware and functional configuration of the communication device according to the second embodiment are similar to those of the communication device according to the first embodiment described with reference to FIGS. 2 and 3, and therefore will not be described.

[0052] <Firmware update management process> FIG. 7 is a flowchart showing an example of a firmware update management process executed when the communication device according to the present embodiment operates as a controller in the multi-AP network 6. The process from S101 to S103 is similar to the firmware update management process executed by the communication device (AP1) according to the first embodiment shown in FIG.

[0053] In S104, the controller unit 161 of AP1 broadcasts the schedule information adjusted in S103 to the multi-AP network 6 including AP2 to AP4. Broadcasting is an example of broadcast transmission, and other broadcast transmission such as multicast may be used. In this embodiment, the schedule information transmitted by the controller unit 161 to each of AP2 to AP4 includes information on the order in which each of the agents AP2 to AP4 should perform firmware updates. After broadcasting the schedule information to the multi-AP network 6 in S104, in S106 the controller unit 161 of AP1 transmits an instruction message to start firmware update to the agents AP2 to AP4. This instruction message to start firmware update includes the schedule information broadcast to the multi-AP network 6 in S104, and is broadcast to the multi-AP network 6 in the same manner as in S104. This allows AP2 to AP4 to know in what order among AP2 to AP4 they should perform firmware update.

[0054] In S107, the controller unit 161 of AP1 executes steering of the STA connected to the AP included in the multi-AP network 6. In this embodiment, the controller unit 161 executes steering of the STA in cooperation with AP2 to AP4 which are agents included in the multi-AP network 6. Specifically, the controller unit 161 of AP1 executes steering of the STA in cooperation with AP2 to AP4 so as to connect the STA connected to the AP which is first in the order of firmware update to another AP included in the multi-AP network 6.

[0055] After the STA steering is performed in S107, the firmware is updated in AP2 to AP4 included in the multi-AP network 6 in the order broadcast, and notification that the firmware update has been completed is sent from AP2 to AP4. In S105, the controller unit 161 of the AP1 receives notifications sent from the AP2 to AP4 to the effect that the firmware update has been completed. The controller unit 161 of the AP1 starts the process of S101 at predetermined intervals, and repeats the process shown in FIG.

[0056] <Firmware update process> FIG. 8 is a flowchart showing an example of a firmware update process executed when the communication device according to the present embodiment operates as an agent in the multi-AP network 6. The processes from S201 to S203 are similar to the firmware update process executed by the communication device (AP2) according to the first embodiment shown in Fig. 5. In this embodiment, the broadcasted schedule information received by the agent unit 262 of AP2 in S203 includes the order in which AP2 to AP4 should update their firmware.

[0057] After receiving schedule information from AP1 in S203, in S207, the agent unit 262 of AP2 receives an instruction message to start a firmware update broadcast from AP1 to the multi-AP network 6. Here, it is assumed that the instruction message to start a firmware update designates AP2 as the first in the firmware update order. Alternatively, this instruction message to start a firmware update may indicate that a firmware update should be executed in AP2. When an instruction message to start firmware update is received in S207, the agent unit 262 of AP2 executes STA steering in cooperation with other APs included in the multi-AP network 6 in S204a. Specifically, the agent unit 262 of AP2 executes STA steering in cooperation with the other APs so that the STA connected to AP2, which is first in the order of firmware update, is connected to another AP included in the multi-AP network 6.

[0058] In S205, the agent unit 262 of AP2 performs firmware update if AP2 is first in the order of firmware update according to the order of firmware update included in the schedule information received from AP1 in S203. In S206, the agent unit 262 of AP2 broadcasts a notification that the firmware update of AP2 has been completed to the multi-AP network 6. If the firmware update of AP2 has failed, a notification to that effect may be broadcast.

[0059] <Control sequence for firmware update in a multi-AP network> FIG. 9 shows an example of a control sequence of firmware update processing between APs in the multi-AP network 6 in this embodiment. The processing in S61 to S63 is similar to that in the first embodiment shown in FIG. In S64, AP1 broadcasts schedule information including the schedule-adjusted firmware update order to the multi-AP network 67 including AP2 to AP4. Here, it is assumed that the schedule of firmware updates among AP2 to AP4 is adjusted so that firmware updates are executed in the order of AP2, AP3, and AP4.

[0060] After the schedule information is broadcast to the multi-AP network 6 in S64, the AP1 broadcasts, in S71, to the multi-AP network 6 including the AP2 to AP4, an instruction message to execute firmware update. In S65a, AP1 to AP4 cooperate to steer the STA connected to AP2 to another agent AP before firmware update is performed on AP2, which is specified as being first in the firmware update order. In S66, AP2 updates its firmware before AP3 and AP4. In S67, AP2 broadcasts to the multi-AP network 6 a notification that the firmware of AP2 has been updated.

[0061] The subsequent processes are the same as those of S71, S65a, S66, and S67 for AP3, which is specified as second in the firmware update order. That is, upon receiving a notification in S67 that the firmware update in AP2 has been completed, AP1 broadcasts an instruction message to start the firmware update to the multi-AP network 6 in S72. The instruction message to start the firmware update broadcast in S72 provides an opportunity for AP3 to execute the firmware update. In S68a, before the firmware update is performed, AP3 cooperates with other APs to perform steering of the STAs connected to AP3 to other agent APs, and in S69, AP3 updates its own firmware. In S70, the AP 3 broadcasts a notification to the multi-AP network 6 that the firmware of the AP 3 has been updated.

[0062] As described above, according to this embodiment, the communication device operating as the controller broadcasts, to the multi-AP network 6, schedule information as well as an instruction message to start firmware update. In addition, when a communication device operating as an agent receives an instruction message to start a firmware update, it cooperates with other APs to perform TA steering, then updates the firmware on its own device and broadcasts a notice of the firmware update. This allows multiple APs connected to a multi-AP network to work together to quickly steer STAs and update firmware in accordance with the update order.

[0063] (Embodiment 3) Hereinafter, the third embodiment will be described in detail with reference to Figs. 10 to 12, focusing only on the differences from the first embodiment. In the first embodiment, the controller in the multi-AP network notifies each agent of an adjusted schedule for updating firmware in the agent, and each agent updates the firmware. In contrast, in the present embodiment, the controller in the multi-AP network proposes an adjusted schedule to each AP, and the agent determines whether to update firmware according to the proposed schedule. The hardware and functional configuration of the communication device according to the third embodiment are similar to those of the communication device according to the first embodiment described with reference to FIGS. 2 and 3, and therefore will not be described.

[0064] <Firmware update management process> FIG. 10 is a flowchart showing an example of a firmware update management process executed when the communication device according to the present embodiment operates as a controller in the multi-AP network 6. The processes from S101 to S103 are similar to the firmware update management process executed by the communication device (AP1) according to the first embodiment shown in Fig. 4. In S103, the controller unit 161 of AP1 schedules the firmware update times of AP2 to AP4 so that multiple APs do not update their firmware at the same time.

[0065] After the schedule is adjusted in S103, in S108, the controller unit 161 of AP1 transmits a message proposing the schedule adjusted in S103 to each of AP2 to AP4. In this embodiment, the schedule proposal transmitted by the controller unit 161 to each of AP2 to AP4 includes information on the schedule adjusted in S103, and the schedule information includes information on the time when the AP should perform a firmware update. In S109, the controller unit 161 of the AP1 receives responses to the schedule proposals transmitted in S from the AP2 to AP4, respectively. In S110, the controller unit 161 of AP1 refers to the response to the schedule proposal received in S109 and determines whether the proposed schedule has been approved in AP2 to AP4.

[0066] If the proposed schedule is not permitted (S110: N), the process returns to S103, and the controller unit 161 of AP1 adjusts the firmware update schedule again. If the response to the schedule proposal received in S109 includes an alternative time at which the firmware update can be performed in the AP, the controller unit 161 may adjust the schedule using the alternative time. On the other hand, if the proposed schedule is permitted (S110: Y), the process proceeds to S105. In S105, the controller unit 161 of the AP1 receives notifications sent from the AP2 to AP4 to the effect that the firmware update has been completed. The controller unit 161 of the AP1 repeats the process of FIG. 10 at predetermined intervals.

[0067] <Firmware update process> FIG. 11 is a flowchart showing an example of a firmware update process executed when the communication device according to the present embodiment operates as an agent in the multi-AP network 6. The process from S201 to S202 is similar to the firmware update process executed by the communication device (AP2) according to the first embodiment shown in FIG. After transmitting the firmware information in S202, in S208 the agent unit 262 of AP2 receives a message from AP1 proposing a firmware update schedule.

[0068] In S209, the agent unit 262 of AP2 determines whether or not to execute the firmware update according to the proposed schedule based on the schedule information in the message of the proposed schedule received in S208. Specifically, the agent unit 262 may determine whether or not the firmware of AP2 can be updated at the time when the proposed firmware update should be executed based on the load of preparations required prior to the firmware update. For example, the agent unit 262 may determine whether or not the firmware can be updated according to the proposed schedule based on the number of STAs connected to the own device.

[0069] If the firmware update is not to be performed according to the proposed schedule (S209: N), the process proceeds to S210, where the agent unit 262 of AP2 transmits a rejection response to AP1 as the result of the determination of the proposed firmware update schedule, and the process returns to S208. On the other hand, if the firmware update is to be performed according to the proposed schedule (S209: Y), the process proceeds to S211, where the agent unit 262 of AP2 transmits an approval response to AP1 in response to the proposed firmware update schedule, and the process proceeds to S204.

[0070] After transmitting a response to AP1 in response to the schedule proposal indicating approval in S211, the processes from S204 to S206 are the same as those from S204 to S206 shown in Fig. 5. That is, in S204, the agent unit 262 of AP2 executes steering of the STAs connected to AP2 before the firmware update time included in the schedule proposal arrives. In S205, the agent unit 262 of AP2 executes the firmware update, and in S206, transmits a notification to AP1 indicating that the firmware update has been completed.

[0071] <Control sequence for firmware update in a multi-AP network> FIG. 12 shows an example of a control sequence of firmware update processing between APs in the multi-AP network 6 in this embodiment. The processing in S61 to S63 is similar to the processing in S61 to S63 in the first embodiment shown in FIG. After the firmware update schedule adjustment for AP2 to AP4 is performed in S63, AP1 transmits a firmware update schedule proposal to AP2 in S73. In S74, AP2, which has received the schedule proposal, transmits a response to the firmware update schedule proposal to AP1. Similarly, in S75, AP1 transmits a firmware update schedule proposal to AP3, and in S76, AP3, which has received the schedule proposal, transmits a response to the firmware update schedule proposal to AP1. In Fig. 12, it is assumed that both AP2 and AP3 transmit responses to AP1 indicating that the firmware update schedule proposal is permitted.

[0072] S65 to S67 are the same as S65 to S67 shown in Fig. 6. That is, in S65, AP2 executes steering of the STA connected to AP2 to another agent AP before the firmware update time specified as the schedule information arrives, based on the schedule information in the schedule proposed in S73. In S66, AP2 updates its own firmware, and in S67, AP2 transmits a notification to AP1 that its firmware has been updated. In S68 to S70, the AP 3 executes the same processes as in S65 to S67.

[0073] As described above, according to this embodiment, a communication device acting as a controller transmits a firmware update schedule proposal to a communication device acting as an agent, and if the agent responds with a rejection, readjusts the schedule. Furthermore, when the communication device operating as an agent receives a proposed schedule for firmware update, it determines whether or not to execute the firmware update according to the proposed schedule, and responds to the controller as to whether or not the proposed schedule is acceptable. This makes it possible to readjust the firmware update schedule for an AP that is connected to a multi-AP network even if that AP is unable to perform a firmware update according to the adjusted schedule. This allows firmware updates for multiple APs that make up the multi-AP network to be performed more quickly and without delay.

[0074] (Embodiment 4) Hereinafter, the fourth embodiment will be described in detail with reference to Figs. 13 to 15, focusing only on the differences from the first embodiment. In the first embodiment, the controller in the multi-AP network notifies each agent of an adjusted schedule for updating firmware in the agent, and each agent updates its firmware. In contrast, in the present embodiment, an agent requests a firmware update schedule for the agent from the controller, and the controller adjusts the firmware update schedule for the requested agent and transmits it to the requesting agent. The hardware and functional configuration of the communication device according to the fourth embodiment are similar to those of the communication device according to the first embodiment described with reference to FIGS. 2 and 3, and therefore description thereof will be omitted.

[0075] <Firmware update management process> FIG. 13 is a flowchart showing an example of a firmware update management process executed when the communication device according to the present embodiment operates as a controller in the multi-AP network 6. The process from S101 to S102 is similar to the firmware update management process executed by the communication device (AP1) according to the first embodiment shown in FIG. After receiving firmware information from AP2 to AP4 in S102, in S111 the controller unit 161 of AP1 receives a message from any one of AP2 to AP4, which are agents, requesting a schedule for firmware update in that AP.

[0076] In S103, the controller unit 161 of AP1 adjusts the schedule of the firmware update of the AP that requested the schedule based on the firmware information from AP2 to AP4 received in S62. Specifically, the controller unit 161 adjusts the schedule of the firmware update time of the AP that requested the schedule so that multiple APs do not update their firmware at the same time. In S112, the controller unit 161 of AP1 transmits the schedule for firmware update of the AP that requested the schedule adjusted in S103 to the AP that requested the schedule. S105 is the same as S105 shown in FIG. 6, and the controller unit 161 of AP1 receives a notification that the firmware update has been completed, which is sent from the AP that requested the schedule. The controller unit 161 of the AP1 repeats the process shown in FIG. 13 at predetermined intervals.

[0077] <Firmware update process> FIG. 14 is a flowchart showing an example of a firmware update process executed when the communication device according to the present embodiment operates as an agent in the multi-AP network 6. The process from S201 to S202 is similar to the firmware update process executed by the communication device (AP2) according to the first embodiment shown in FIG. After transmitting the firmware information in S202, in S212, the agent unit 262 of AP2 transmits to AP1 a message requesting a schedule for firmware update of AP2. In response to the request for the schedule for firmware update, AP1 adjusts the schedule for firmware update of AP2. In S213, the agent unit 262 of AP2 receives information on the firmware update schedule of AP2 from AP1 as a response to the request for the firmware update schedule.

[0078] After receiving a response to the schedule request in S213, the processes from S204 to S206 are the same as those from S204 to S206 shown in Fig. 5. That is, in S204, the agent unit 262 of AP2 executes steering of the STAs connected to AP2 before the firmware update time included in the response to the schedule request arrives. In S205, the agent unit 262 of AP2 executes the firmware update, and in S206, transmits a notification to AP1 that the firmware update has been completed.

[0079] <Control sequence for firmware update in a multi-AP network> FIG. 15 shows an example of a control sequence of firmware update processing between APs in the multi-AP network 6 in this embodiment. The processing in S61 to S62 is similar to the processing in S61 to S62 in the first embodiment shown in FIG. After receiving firmware information from AP2 to AP4 in S62, AP2 transmits a schedule request for updating the firmware of AP2 to AP1 in S77. In S63, AP1 executes schedule adjustment for firmware update of AP2 based on the firmware information of AP2 to AP4 received in S62, and in S78, AP1 transmits a response to the schedule request to AP2. In S79 to S81, AP3 executes the same processes as those in S77, S63, and S78. That is, in S79, AP3 transmits a schedule request for firmware update of AP3 to AP1, in S80, AP1 executes schedule adjustment for firmware update of AP3, and in S81, AP1 transmits a response to the schedule request to AP3.

[0080] S65 to S67 are the same as S65 to S67 shown in Fig. 6. That is, in S65, AP2 executes steering of the STA connected to AP2 to another agent AP before the firmware update time specified as the schedule information in the response to the schedule request received in S78 arrives. In S66, AP2 updates its own firmware, and in S67, AP2 transmits a notification to AP1 that its firmware has been updated. In S68 to S70, the AP 3 executes the same processes as in S65 to S67.

[0081] As described above, according to this embodiment, a communication device operating as a controller adjusts the schedule for a firmware update of the requesting agent in response to a request from a communication device operating as an agent, and responds to the requesting agent. Furthermore, the communication device operating as an agent requests the controller for a schedule for updating the firmware of the own device, and executes firmware updates according to the schedule returned from the controller. In this way, in response to a request from an AP connected to the multi-AP network, the schedule adjustment of the firmware update for the AP is performed, thereby reducing the load on the controller of adjusting the schedules of firmware updates for a plurality of APs.

[0082] (Other embodiments) The present invention can be embodied, for example, as a system, an apparatus, a method, a program, or a recording medium (storage medium), etc. Specifically, the present invention may be applied to a system composed of multiple devices (for example, a host computer, an interface device, an imaging device, a Web application, etc.), or may be applied to an apparatus composed of a single device. The present invention can also be realized by a program that realizes part or one or more functions of the above-mentioned embodiments. That is, the program can be supplied to a system or device via a network or a storage medium, and one or more processors in a computer (or a CPU, MPU, etc.) of the system or device read and execute the program. The program may also be provided by recording it on a computer-readable recording medium. In addition, the functions of the embodiments are not limited to those that are realized by a computer executing a program read out by the computer. For example, an operating system (OS) running on a computer may perform a part or all of the actual processing based on instructions from the program, and the functions of the above-mentioned embodiments may be realized by the processing. [Explanation of symbols]

[0083] 1...controller, 2, 3, 4...agent, 5a, 5b, 5c, 5d, 5e...station, 6...multi-AP network, 7...WAN, 11, 21...power supply section, 12, 22...input section, 13, 23...output section, 14, 24...wireless communication section, 15, 25...storage section, 16, 26...control section, 17, 27...antenna, 18, 28...system bus, 161...controller section, 162, 262...agent section

Claims

1. A communication device that operates as one access point in a wireless network consisting of a plurality of access points, an acquisition means for acquiring firmware information of an access point other than the communication device among the plurality of access points; a determination means for determining a schedule for updating firmware of at least one other access point among the plurality of access points based on the firmware information acquired by the acquisition means; a notification means for notifying the at least one other access point of information about the schedule determined by the determination means; and a control means for controlling a steering process such that a station connected to the at least one other access point connects to an access point different from the at least one other access point before updating the firmware of the at least one other access point based on the schedule; A communication device characterized in that, when updating firmware of two or more access points, the determination means determines the schedule based on the firmware information acquired by the acquisition means, so as to prevent the firmware updates from overlapping in time among the multiple access points.

2. The acquisition means acquires the firmware information of the other access points by periodically inquiring about the firmware information of the other access points.

2. The communication device according to claim 1 .

3. the wireless network is a mesh type network constructed by the plurality of access points, 3. The communication device according to claim 1, further comprising a management unit for managing the mesh type network.

4. The determining means determines the schedule by giving priority to an access point having firmware with an older version or date among the plurality of access points based on the firmware information acquired by the acquiring means.

4. The communication device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

5. The method further includes broadcasting means for broadcasting information on the order in which the firmware updates are to be started to the wireless network.

5. The communication device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

6. When the determining means receives a rejection response from the other access point in response to the schedule information notified to the other access point by the notifying means, the determining means determines the schedule again based on the rejection response.

6. The communication device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

7. The determining means, when a schedule for updating the firmware of the other access point is requested from the other access point, determines the schedule for the other access point that is the request source.

7. The communication device according to claim 1, wherein the first and second inputs are connected to the first and second inputs.

8. the wireless network is a wireless network conforming to the Wi-Fi EasyMesh (registered trademark) standard, the communication device functions as a controller of the Wi-Fi EasyMesh (registered trademark) standard, and the other access point functions as an agent of the Wi-Fi EasyMesh (registered trademark) standard; The communication device can also operate as the agent of the Wi-Fi EasyMesh (registered trademark) standard under the management of another controller, and when operating as the agent, the process of determining a schedule by the determination means and the process of notifying information about the schedule by the notification means are not executed.

8. A communication device according to claim 1, wherein the communication device is a communication device having a plurality of communication ports.

9. One access point in a wireless network consisting of multiple access points; 1. A control method performed by a communication device operable to Among the plurality of access points, the fan of an access point other than the communication device acquiring firmware information from the other access point; Based on the firmware information acquired in the acquiring step, The firmware of at least one of the other access points is to be updated. a determination process for determining a schedule; and The schedule information determined in the determination step is transmitted to the at least one other activity. a notification control step of notifying an access point; The firmware of the at least one other access point is updated based on the schedule. Before updating the access point, the at least one other access point is connected to the A station may use one of the plurality of access points different from the at least one other access point. and a control step of controlling the steering process so as to connect to an access point constituting a service point, When determining the firmware update schedule for two or more other access points, In the determining step, based on the firmware information acquired in the acquiring step, The firmware updates are prevented from overlapping in time among a plurality of access points. The determination process determines the schedule so as to control the communication. A method for controlling the device.

10. A computer functions as each of the means of the communication device according to any one of claims 1 to 8. A program to make it possible.

Images