Mesh controller, mesh agent, mesh network system, software update method, and program

Abstract

To efficiently update software in a state where an amount of communication with the outside is reduced without causing service reduction in a network consisting of plural APs.SOLUTION: A mesh controller comprises: a storage unit for storing an update file; and a control unit for controlling the update of software of an agent in a network by using the update file. The control unit comprises: a type determination unit for determining the type of the software of the agent; and an agent update unit for controlling the update of the same type agent installed with software of the same type as an own device. The agent update unit determines whether or not the same type agent requires to be updated, and sends update information to the same type agent requiring the update, and transmits the update file to the same type agent of a reply source when an update start request is returned after the transmission of the update information. The update start request is transmitted when a terminal device is not connected to the same type agent.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a mesh controller, a mesh agent, a mesh network system, a software update method, and a program.

Background Art

[0002] There is a mesh Wi-Fi network in which access points (APs) such as a plurality of relay devices (routers) are connected like a mesh. In a mesh Wi-Fi network, there are cases where multiple APs of the same model (or similar models) are used. Also, the AP updates the installed software such as firmware for function enhancement and security enhancement. Files used for such updates are downloaded from a server via, for example, the Internet or the like.

[0003] In such a network, there is a technology for appropriately updating the firmware of a plurality of APs (see, for example, Patent Document 1). In the technology disclosed in Patent Document 1, "a communication device is operable as an access point in a wireless network including a plurality of access points, obtains information on the firmware of access points other than the communication device among the plurality of access points, and based on the obtained firmware information, determines a schedule for updating the firmware of other access points, and notifies the other access points of the information on the determined schedule (abstract excerpt)".

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The following analysis is provided by the inventor of the present invention.

[0006] According to the technology of Patent Document 1, the AP that serves as a controller schedules so that firmware updates among other APs (agents) in the network do not overlap. Therefore, communication interruption during the update can be minimized.

[0007] However, the problems related to software updates are not limited to this. For example, the files used for the update are downloaded from a server via the Internet or the like. Among these, there are also files with large capacities. When software is updated using the functions of a general router or the like (AP), it is performed by each AP using its respective functions. Therefore, since each AP constituting the mesh Wi-Fi downloads the update file, a lot of communication occurs.

[0008] When LTE (Long Term Evolution) or the like is used as the line on the WAN (Wide Area Network) side in an AP, the communication speed may be limited according to the amount of communication used. Therefore, there is a demand to minimize the communication volume on the WAN side. Also, in the case of APs of the same model, since the files used for the update are the same, each AP downloading them separately means that the same file is downloaded the number of times equal to the number of APs, which is wasteful.

[0009] In addition, after firmware or the like is updated, a restart is required. During that time, the communication of the terminals connected to the AP is interrupted. Therefore, in a mesh Wi-Fi network, this point also needs to be considered.

[0010] The present invention has been made in view of the above circumstances, and an object thereof is to provide a technology that supports updating software efficiently installed without reducing the service while suppressing the communication volume with the outside in a network system configured by a plurality of APs.

Means for Solving the Problems

[0011] According to a first aspect of the present invention, a storage unit that stores an update file; a control unit that controls an update of software installed in a mesh agent in a mesh network using the update file, and the control unit includes a type discrimination unit that discriminates a type of the software installed in the mesh agent, and an agent update unit that controls the update of the same-type agent which is the mesh agent in which the same-type software as the own device is installed, and the agent update unit discriminates necessity of the update of the same-type agent, transmits update information to the same-type agent determined to require the update, when an update start request is returned from the same-type agent after transmission of the update information, transmits the update file to the same-type agent that is the source of the return, the update start request is transmitted when a terminal device is not connected to the same-type agent, and a mesh controller is provided.

[0012] According to a second aspect of the present invention, a control unit that controls an update of software of the own device, and the control unit when receiving update information from a mesh controller in a mesh network, discriminates presence or absence of connection of a terminal device, and when there is no connection, transmits an update start request to the mesh controller, performs the update of the own device using the update file transmitted from the mesh controller in response to the update start request, when the update is completed, transmits an update completion notification to the mesh controller, and a mesh agent is provided.

[0013] According to a third aspect of the present invention, A mesh network system comprising a mesh controller and a mesh agent, wherein the mesh controller, comprises a storage unit for storing an update file, and a controller-side control unit for controlling software updates of the mesh controller and the mesh agent using the update file, the mesh agent comprises an agent-side control unit for controlling the update of the self-device, the controller-side control unit, comprises a type discrimination unit for discriminating the type of software installed in the mesh agent, and an agent update unit for controlling the update of the same-type agent, which is the mesh agent installed with the same-type software as the mesh controller, the agent update unit, discriminates the necessity of the update of the same-type agent, sends update information to the same-type agent determined to require the update, and when an update start request is returned from the same-type agent after the transmission of the update information, sends the update file to the same-type agent that is the source of the return, the agent-side control unit, when receiving the update information from the mesh controller, discriminates the presence or absence of a connection to a terminal device, and if there is no connection, sends the update start request to the mesh controller, performs the update of the self-device using the update file transmitted from the mesh controller in response to the update start request, and when the update is completed, sends an update completion notification to the mesh controller, thereby providing a mesh network system.

[0014] According to a fourth aspect of the present invention, A software update method for updating the software of a mesh controller and a mesh agent in a mesh network system including the mesh controller and the mesh agent, comprising: The mesh controller: Determine the type of the software to be installed in the mesh agent; Determine whether the update is required for the mesh agent in which the same type of software as the own device is installed; Transmit update information to the mesh agent for which the update is determined to be necessary; When the mesh agent receives the update information, it determines whether a terminal device is connected. If there is no connection, it transmits an update start request to the mesh controller; When the mesh controller receives the update start request, it transmits the update file of the software stored in the own device to the mesh agent that is the transmission source; The mesh agent performs the update using the update file received from the mesh controller, and when the update is completed, transmits an update completion notification to the mesh controller, thereby providing a software update method.

[0015] According to a fifth aspect of the present invention: A computer built into a mesh controller is caused to function as: A type determination means for determining the type of software installed in a mesh agent within a mesh network; An agent update means for determining whether the software of a same-type agent, which is a mesh agent in which the same type of software as the mesh controller is installed, needs to be updated, transmitting update information to the same-type agent for which the update is determined to be necessary, and when an update start request is returned from the same-type agent when no terminal device is connected to the same-type agent after the transmission of the update information, transmitting the update file stored in the own device to the same-type agent that is the return source. A program is provided for causing the computer to function as the agent update means.

[0016] According to a sixth aspect of the present invention, a computer incorporated in a mesh agent, when receiving update information from a mesh controller in a mesh network, determines the presence or absence of a connection to a terminal device, and if there is no connection, transmits an update start request to the mesh controller, and uses the update file transmitted from the mesh controller in response to the update start request to update the software installed in the mesh agent, and when the update is completed, functions as control means for transmitting an update completion notification to the mesh controller. A program is provided.

[0017] Note that this program can be recorded on a computer-readable storage medium. The storage medium can be a non-transient one such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. The present invention can also be embodied as a computer program product.

Advantages of the Invention

[0018] According to the present invention, in a network system composed of a plurality of APs, it is possible to update the software installed efficiently without suppressing the communication volume with the outside and degrading the service.

Brief Description of the Drawings

[0019]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0020] Hereinafter, an overview of an embodiment of the present invention (hereinafter referred to as this embodiment) will be described with reference to the drawings. Note that the reference numerals in the drawings are attached to each element for convenience as an example to assist understanding, and are not intended to limit the present invention to the illustrated embodiments. Also, the connection lines between the blocks in the drawings and the like referred to in the following description include both bidirectional and unidirectional ones. The one-way arrow schematically shows the flow of the main signal (data) and does not exclude bidirectionality.

[0021] Also, ports and interfaces are present at the connection points of the inputs and outputs of each block in the figure, but the illustration thereof is omitted. Also, in the following description, "A and / or B" is used to mean A or B, or A and B.

[0022] <<First Embodiment>> First, the first embodiment of the present invention will be described. FIG. 1(a) is an overall view of the mesh network system (network 100a) of this embodiment. As shown in this figure, the network 100a of this embodiment includes a mesh controller (controller 200a) and one or more mesh agents (agent 300a). Here, as an example, the case where three agent 300a are provided is illustrated.

[0023] The controller 200a and each agent 300a perform wireless communication with each other and are mesh APs (Access Points) that constitute the network 100a. The controller 200a is connected to a WAN (Wide Area Network) 801 such as the Internet and controls a plurality of agents 300a. Each agent 300a can communicate with the WAN 801 via the controller 200a.

[0024] The wireless slave terminal (terminal device; slave unit 400) is a wireless terminal that can be moved or fixedly installed, and can communicate with the WAN 801 via the network 100a (controller 200a) by connecting to any mesh AP.

[0025] In such a network 100a, in this embodiment, only the controller 200a downloads the software file (update file) to be updated from the external server 800 via the WAN 801. Then, among the agents 300a in the network 100a, the update file is provided to devices of the same type as the controller 200a through communication within the network 100a. Here, devices of the same type mean that the installed software to be updated is of the same type.

[0026] Each agent 300a receives the update file from the controller 200a and executes the update at the timing when no slave unit 400 is connected to its own device (when there is no slave unit 400 communicating via the agent 300a).

[0027] Hereinafter, taking the case where the software to be updated is firmware (FW) as an example, the network 100a of the present embodiment for realizing this will be described. The FW updated in this embodiment is software for controlling the hardware of the AP. For example, it is software incorporated in the AP in a state pre-written in the non-volatile storage device of the AP. The FW may include microcode that determines the operation of the CPU (Central Processing Unit) mounted on the AP, BIOS (Basic Input / Output System), and the like.

[0028] [Controller] Figure 1(b) is a functional block diagram of the controller 200a. As shown in this figure, the controller 200a of the present embodiment includes a controller storage unit (CNT storage unit) 210 that stores the update file 211, and a controller control unit (CNT control unit) 220 that controls the update of the FW of the APs (controller 200a and agent 300a) in the network 100a using the update file 211.

[0029] The CNT control unit 220 includes a type discrimination unit 230 that discriminates the type of the agent 300a in the network 100a, and an agent update unit 240 that controls the update of the same-type agent 300a that is determined to be the same type as the self-device. Here, the same type means that the same type of FW is installed as described above.

[0030] The agent update unit 240 discriminates whether the update of the same-type agent 300a is necessary. Then, update information is transmitted to the same-type agent 300a determined to require an update as an update instruction. Here, the update information is information for determining whether the FW of each of the APs (controller 200a and agent 300a) can be updated.

[0031] Further, when the agent update unit 240 receives an update start request from the same type of agent 300a, it transmits the update file 211 to the same type of agent 300a that is the source of the update start request.

[0032] [Agent] As shown in FIG. 1(c), the agent 300a includes an agent control unit (AGT control unit) 320 that controls the update of the software of its own device. When the AGT control unit 320 receives update information from the controller 200a within the network 100a, it determines whether or not the slave unit 400 is connected. And when there is no connection of the slave unit 400, that is, when the slave unit 400 is not connected to its own device, it transmits an update start request to the controller 200a. In response, when the update file 211 is transmitted from the controller 200a, it uses the same to update the FW of its own device. Note that when the update is completed, it transmits an update completion notification to the controller 200a.

[0033] As described above, according to the present embodiment, the agent 300a in which the same type of FW as that of the controller 200a is installed does not acquire the update information and the update file 211 from the external server 800. For this reason, in the present embodiment, communication with the WAN 801 is performed only when the controller 200a acquires the update information and the update file 211 from the external server 800. Therefore, it is possible to suppress the communication volume of communication with the WAN 801 with a limited communication usage amount.

[0034] Further, according to the present embodiment, on the agent 300a side, it checks the connection of the slave unit 400, and when there is no connected slave unit 400, it requests the controller 200a for the update file 211 and performs update and restart. Therefore, the communication of the slave unit 400 connected to the agent 300a is less likely to suddenly stop, and a high-quality communication service can be provided.

[0035] Furthermore, since the agent 300a autonomously manages the FW update schedule in this way, there is no need for the controller 200a to manage the updates of each agent 300a. Therefore, an increase in the burden on the controller 200a can also be minimized.

[0036] Therefore, according to this embodiment, in the network 100a composed of the controller 200a and one or more agents 300a, it is possible to suppress the communication volume with the external with communication restrictions and efficiently update the FW without degrading the service.

[0037] <<Second Embodiment>> Next, a second embodiment of this embodiment will be described. This embodiment is a more detailed and specific embodiment of the first embodiment.

[0038] The mesh network system (network 100) of this embodiment is basically the same as the first embodiment. As shown in FIG. 2(a), it includes a mesh controller (controller 200) and one or more mesh agents (agent 300). Hereinafter, the components with the same names as those in the first embodiment basically have the same functions as those in the first embodiment. Hereinafter, this embodiment will be described focusing on the components different from those in the first embodiment.

[0039] [Controller] The controller 200 of this embodiment includes, as shown in FIG. 2(b), a controller (CNT) storage unit 210, a controller (CNT) control unit 220, a controller (CNT) first communication unit 260, and a controller (CNT) second communication unit 270.

[0040] The CNT storage unit 210 stores and manages the FW information of the self-device and the agent 300 that performs wireless communication with the self-device. These are managed, for example, as an FW management table 510. An example of the FW management table 510 is shown in FIG. 3(a).

[0041] As shown in this figure, in the FW management table 510, a FW type 512 indicating the type of FW installed in the own device (controller 200) and the agent 300 respectively, and a version 513 indicating the version of the FW are registered. They are registered in association with information (CNT, AGT ID) for identifying the device respectively. Note that the AGT ID is information for identifying each agent 300.

[0042] Also, a completion flag 514 indicating whether the update has been completed is registered. As will be described later, the completion flag 514 is set by the CNT control unit 220 when a completion notification is received from each agent 300.

[0043] Also, in this embodiment, the update file 211 and the update information 520 downloaded from the external server 800 are also temporarily stored. Note that the update file 211 is a file for performing FW update of the controller 200 and the agent 300. Also, the update information 520 is information for determining whether FW update of the controller 200 and the agent 300 is possible.

[0044] The CNT first communication unit 260 is an interface for communicating with the WAN 801 via LTE or the like. The controller 200 is connected to an external server 800 that holds the update file 211 and the update information 520 via the CNT first communication unit 260.

[0045] The CNT second communication unit 270 is an interface for performing wireless communication with agents 300 within the network 100 that constitutes a mesh Wi-Fi. It also performs communication with the slave unit 400 connected to the controller 200. For example, it performs backhaul communication with the agent 300 and front-haul communication with the slave unit 400.

[0046] The CNT control unit 220 controls the operation of the entire controller 200 and controls the update of the FW of the agents 300 in the network 100. The agent 300 to be controlled is an agent 300 in which the same type of FW is installed. Hereinafter, it is also referred to as a homogeneous agent. Note that an agent 300 in which different types of FW are installed is also referred to as a heterogeneous agent. To achieve this, similar to the first embodiment, the CNT control unit 220 includes a type discrimination unit 230 and an agent update unit 240.

[0047] In addition, the CNT control unit 220 updates the FW of its own device. The CNT control unit 220 accesses the external server 800 via the CNT first communication unit 260 and acquires the update information 520. For example, it accesses the external server 800 at a predetermined time interval or in response to the occurrence of a predetermined event.

[0048] The update information 520 acquired here includes the latest version information of the FW. An example of the information included in the update information 520 is shown in FIG. 3(b). As shown in this figure, the update information 520 includes an FW type 522 which is information for specifying the type of the FW and a version 523 which is information for specifying its version.

[0049] When the CNT control unit 220 acquires the update information 520, it compares it with the version 513 of the FW currently installed in its own device and determines whether an update is necessary. If it is determined that the version 513 of its own device is older and an update is required, the latest version of the update file 211 is acquired from the external server 800 and stored in the CNT storage unit 210.

[0050] After the update of all the homogeneous agents 300 in the network 100 is completed, the CNT control unit 220 updates its own device using the update file 211. Then, the update file 211 is deleted. Also, the version 513 registered in the FW management table 510 is updated to the version 523 of the installed update file.

[0051] The type discrimination unit 230 discriminates the type of the FW installed in each agent 300 within the network 100. In the present embodiment, an FW inquiry 530 is transmitted to inquire about the type and version information of the FW installed in each agent 300. As shown in FIG. 3(c), the FW inquiry 530 is created by attaching an AGT ID 531, which is information for specifying the agent 300 of the inquiry destination, to the inquiry content 532.

[0052] When receiving an FW response 540 returned in response to the FW inquiry 530, the type discrimination unit 230 analyzes the FW response 540 and grasps the type and version of the FW installed in the agent 300 that is the source of the return. As shown in FIG. 3(d), the FW response 540 includes an AGT ID 541, which is information for specifying the source agent, an FW type 542 indicating the type of the installed FW, and a version 543, which is the version information thereof.

[0053] Note that an AGT ID, which is information for specifying the agent 300, is attached to the transmission and reception between the controller 200 and the agent 300.

[0054] When the type discrimination unit 230 determines that the FWs are of the same type, it notifies the agent update unit 240 of the AGT ID 541 of the source of the return and the version 543 of the FW.

[0055] The agent update unit 240 controls the update of the same type of agents 300. In the present embodiment, based on the AGT ID 541 and the version 543 of the FW transmitted from the type discrimination unit 230, it is determined whether the agent 300 needs to be updated. Specifically, when the version 523 of the update information 520 stored in the CNT storage unit 210 is newer, it is determined that an update is required.

[0056] The agent update unit 240 transmits update information 550 to the agent 300 determined to require an update. Note that the update information 550 transmitted here is the above-described update information 520 with the AGT ID 551 of the destination agent 300 added thereto, as shown in Fig. 3(e). Then, when receiving an update start request described later from the agent 300, it transmits the update file 211 stored in the CNT storage unit 210 to the source agent 300.

[0057] [Agent] As shown in Fig. 2(c), the agent 300 includes an agent (AGT) storage unit 310, an agent (AGT) control unit 320, an agent (AGT) first communication unit 360, and an agent (AGT) second communication unit 370.

[0058] The AGT first communication unit 360 is an interface for communicating with the WAN, such as via LTE. Note that if the agent 300 is dedicated for the agent, the AGT first communication unit 360 may not be provided.

[0059] The AGT second communication unit 370 performs wireless communication with the controller 200 and other agents 300, and also performs wireless communication with the slave unit 400 connected to the own device.

[0060] The AGT control unit 320 controls the operation of the entire agent 300. In this embodiment, it also controls the update of the FW. Specifically, when receiving an FW inquiry 530, which is an inquiry about the type and version of the currently installed FW, from the controller 200, it creates and transmits an FW response 540. The FW response 540 includes the FW type 542 and version 543 installed in the own device, as described above.

[0061] Further, after transmitting the FW response 540, when the AGT control unit 320 receives the update information 550 from the controller 200, it creates an update schedule. Here, it determines the update start timing and transmits an update start request to the controller 200.

[0062] In this embodiment, the AGT control unit 320 determines an update schedule according to the presence or absence of the slave unit 400 connected to the own device. That is, the AGT control unit 320 determines whether or not there is a slave unit 400 connected to the own device at a predetermined time interval. Then, the timing when it is determined that there is no slave unit 400 connected to the own device is determined as the update start timing, and an update start request is transmitted to the controller 200. At this time, if the agent 300 already holds an update schedule, it changes the held update schedule to the determined update schedule.

[0063] The determination of the presence or absence of the slave unit 400 connected to the own device is made, for example, based on whether or not there is a change in the amount (traffic volume) of received packets and transmitted packets in the CNT second communication unit 270. That is, if at least one of the amounts per unit time changes by a threshold value or more, it is determined that there is a connected slave unit 400.

[0064] When an update file 211 is transmitted from the controller 200 in response to the update start request, the AGT control unit 320 uses it to update the FW. After the update is completed, a completion notification is transmitted to the controller 200. Also, the version information of the installed FW stored in the AGT storage unit 310 described later is updated.

[0065] The AGT storage unit 310 stores information (FW type) specifying the type of the FW of the own device and version information.

[0066] [FW Update Process] The flow of the FW update process of this embodiment will be described. FIG. 4 shows the process flow of the FW update process of this embodiment. This process is started, for example, when the controller 200 is activated. Here, as an example, the agent 300 is described as a representative. Also, here, it is assumed that only the controller 200 is not updated to the latest version of the FW.

[0067] The controller 200 accesses the external server 800 to obtain the update information 520 (step S1101).

[0068] The CNT control unit 220 determines whether an update is required (step S1102). Here, the version 523 in the update information 520 is compared with the version 513 of the FW installed in the own device registered in the FW management table 510. If the version 523 is newer, it is determined that an update is required.

[0069] Here, if an update is not required, the CNT control unit 220 repeats the acquisition of the update information 520 at a predetermined time interval.

[0070] If an update is required, the CNT control unit 220 accesses the external server 800 to obtain the FW update file 211 (step S1103). The obtained update file 211 is saved in the CNT storage unit 210 (step S1104).

[0071] Thereafter, the type discrimination unit 230 transmits an FW inquiry 530 to each agent 300 (step S1105). Here, as described above, the type and version information of the installed FW are inquired. Note that the FW inquiry 530 is transmitted to all the agents 300 in the network 100.

[0072] When the AGT control unit 320 of each agent 300 receives the FW inquiry 530, it generates and returns an FW response 540 (step S1106). Here, it includes the type (FW type 542) and the version 543 of the FW currently installed in the own device.

[0073] The type discrimination unit 230 that has received the FW response 540 discriminates whether the installed FWs are of the same type (step S1107). Here, it discriminates by comparing the FW type 542 of the FW response 540 with the FW type 512 installed in the own device. Then, it registers the discrimination result in the FW management table 510. If it is discriminated that they are not of the same type (different types), it proceeds to step S1117 described later.

[0074] Note that the type discrimination unit 230 may discriminate as different types for the agent 300 that does not return within a predetermined period after transmitting the FW inquiry 530.

[0075] When it is discriminated that they are of the same type, the agent update unit 240 discriminates whether an update is required (step S1108). Here, it compares the version 543 included in the FW response 540 with the version 523 of the update information 520. If the version 523 is newer, it is discriminated that an update is required. If it is discriminated that an update is not required, it proceeds to step S1117 described later.

[0076] When it is discriminated that an update is required, the agent update unit 240 transmits the update information 550 to the agent 300 that is the transmission source of the FW response 540 as an update instruction (step S1109).

[0077] The agent 300 that has received the update information 550 has its AGT control unit 320 discriminate whether there is a slave unit 400 connected to the own device (step S1110). That is, it discriminates by the above method whether there is a slave unit 400 performing wireless communication via the agent 300.

[0078] Here, when the AGT control unit 320 discriminates that there is a slave unit 400 to be connected (yes), it repeats the process as it is. On the other hand, when it discriminates that there is no slave unit 400 to be connected (no), it transmits an update start request to the controller 200 (step S1111). That is, the agent 300 transmits an update start request when the state becomes such that there is no slave unit 400 connected to the own device.

[0079] Upon receiving the update start request, the controller 200 causes the agent update unit 240 to transmit the update file 211 to the agent 300 at the source (step S1112). Then, in the agent 300 that has received the update file 211, the AGT control unit 320 performs an update using the update file 211 (step S1113).

[0080] Then, when the update is completed, the AGT control unit 320 sends a completion notification to the controller 200 (step S1114), restarts (step S1115), and resumes the mesh connection (step S1116).

[0081] In the controller 200 that has received the completion notification, the agent update unit 240 determines whether completion notifications have been received from all the agents 300 determined to be of the same type in step S1107 (step S1117). Here, the completion flag 514 of the agent 300 that is the source of the completion notification in the FW management table 510 is set. Also, the version 513 is updated to the latest version. Then, the determination is repeated until the completion flag 514 is set for all the agents 300 determined to have the same type of FW.

[0082] When the update of all the agents 300 in which the same type of FW is installed is completed, the CNT control unit 220 updates the FW of the own device (step S1118). For the update, the update file stored in the CNT storage unit 210 is used. Then, after the update is completed, the update file 211 is deleted (step S1119). Thereafter, the controller 200 is restarted (step S1120), and the process ends. At this time, the content of the FW management table 510 is also updated. That is, the version 513 of the controller 200 is updated to the latest version, and the completion flag 514 is deleted (cleared).

[0083] [Specific Example of Update Process] Here, a specific example of the update process will be described with reference to FIG. 5. Here, it is assumed that there are three agents 300 in the network 100. Each of them is denoted as agent 301, 302, and 303. Also, agents 301 and 302 are the same type of agent 300 that needs to be updated, and agent 303 is a different type of agent. The process after the controller 200 acquires the update file 211 from the external server 800 and stores it in the CNT storage unit 210 will be described.

[0084] First, the controller 200 sends a FW inquiry 530 to the agent 301 (step S1201), and in turn, receives a FW response 540 (step S1202). The controller 200 analyzes the FW response 540 and registers the FW type 512 and the version 513 in association with the AGT ID 511 of the agent 301 in the FW management table 510. Here, as described above, the same type of FW is installed in the agent 301, and the agent 301 is determined to require an update (step S1203).

[0085] Next, the controller 200 sends a FW inquiry 530 to the agent 302 (step S1301) and receives a FW response 540 (step S1302). Similar to the above, the FW type 512 and the version 513 are registered in association with the AGT ID 511 of the agent 302 in the FW management table 510. Similar to the above, the same type of FW is installed in the agent 302, and the agent 302 is determined to require an update (step S1303).

[0086] Next, the controller 200 sends a FW inquiry 530 to the agent 303 (step S1401) and receives a FW response 540 (step S1402). The FW type 512 and the version 513 are registered in association with the AGT ID 511 of the agent 303 in the FW management table 510. As described above, it is determined that a different type of FW is installed in the agent 303 (step S1403).

[0087] Note that the order of sending FW inquiries 530 to each agent 301 to 303 does not matter.

[0088] The controller 200 transmits update information 550 to the same type of agent 300 according to the analysis result of the FW response 540.

[0089] First, update information 550 is sent to agent 301 (step S1204). Agent 301 determines whether there is a slave unit 400 to be connected. Assume that there is a slave unit 400 to be connected at the timing of receiving the update information 550 (step S1205). Agent 301 then repeatedly determines whether there is a slave unit 400 to be connected at a predetermined time interval.

[0090] On the other hand, in the controller 200, after sending the update information 550 to the agent 301, even if a predetermined period has elapsed and no update start request is returned, the update information 550 is sent to the agent 302 (step S1304).

[0091] Agent 302 determines whether there is a slave unit 400 to be connected. Here, assume that there is no slave unit 400 to be connected to agent 302 (step S1305).

[0092] Agent 302 sends an update start request to the controller 200 (step S1306), then receives the update file 211 in turn (step S1307). Then, an update is performed using the received update file 211 (step S1308), and a completion notification is sent to the controller 200 (step S1309). After that, the device itself is restarted (step S1310). After startup, a mesh connection is established (step S1312).

[0093] On the other hand, the controller 200 that has received the completion notification from the agent 302 sets (registers) a completion flag 514 in association with the AGT ID 511 of the agent 302 in the FW management table 510 (step S1311). At the same time, the version 513 is also updated.

[0094] After that, in the agent 301, when it is determined that there is no slave unit 400 to be connected (step S1206), the agent 301 sends an update start request to the controller 200 (step S1207). Then, it receives the update file 211 again (step S1208). Update is performed using the received update file 211 (step S1209), and a completion notification is sent to the controller 200 (step S1210). After that, the device is restarted (step S1211), and after startup, mesh connection is performed (step S1213).

[0095] The controller 200 that has received the completion notification from the agent 301 sets (registers) the completion flag 514 in association with the AGT ID 511 of the agent 301 in the FW management table 510 (step S1212). At the same time, the version 513 is also updated.

[0096] Then, when the update is completed in all the same-type agents 300 within the network 100, the controller 200 updates its own device using the update file 211 (step S1511), deletes the update file 211 (step S1512). After that, a restart is performed (step S1513), and the update process ends. Note that after the restart, the FW management table 510 is also updated.

[0097] As described above, according to the present embodiment, it has the same configuration as the first embodiment. Therefore, it has the same effects as the first embodiment. That is, it is possible to suppress the communication volume with the WAN 801 with a limit on the communication usage. Also, it is possible to reduce the interruption of communication of the slave unit 400 connected to the agent 300. And the processing load on the controller 200 side can also be suppressed.

[0098] Therefore, also in the present embodiment, in the network 100 composed of the controller 200 and one or more agents 300, it is possible to suppress the communication volume with the external with communication constraints and efficiently update the FW without degrading the service.

[0099] <Modification Example 1> In the above embodiment, when the controller 200 receives an update start request from the agent 300, it returns the update file 211 regardless of the status of other agents 300, but it is not limited to this.

[0100] For example, when other agents 300 are in the process of FW update, even if an update start request is received, the update file 211 may not be transmitted. That is, after the agent update unit 240 receives a completion notice from the agent 300 that has previously transmitted the update file 211, or after detecting mesh connection, the update file 211 is transmitted to the agent 300 that is the source of the update start request.

[0101] As a result, two agents 300 do not restart simultaneously. For example, in the network 100 configured as shown in FIG. 6(a), the controller 200 and the agent 303 may be outside the range of wireless communication via the CNT second communication unit 270 and the AGT second communication unit 370. At this time, the agent 303 is connected via, for example, the agent 301. In such a network configuration, if the agent 301 and the agent 302 restart simultaneously, during the restart, the mesh connection of the agent 303 within the network 100 is disconnected. Therefore, the range of the mesh Wi-Fi cannot be maintained.

[0102] However, in this modification example, after the agent 302 restarts and resumes the mesh connection, the agent 301 performs FW update and then restarts. Therefore, while the agent 301 is restarting, the agent 303 can mesh-connect to the agent 302 as shown in FIG. 6(b). As a result, the possibility of the wireless connection of the agent 303 being disconnected is reduced, and the possibility of using it while maintaining the range of the mesh Wi-Fi is increased.

[0103] <Modification Example 2> Also, in each of the above embodiments and modifications, the controller 200 performs the update after finishing the update of all the agents 300 of the same type within the network 100. However, it is not limited to this.

[0104] For example, the controller 200 may monitor the FW management table 510 and perform the update at the same time zone as the update of the last agent 300 of the same type. The flow of the update process in this case is shown in FIG. 7.

[0105] Here, as in the second embodiment, the agent 300 is provided with three units 301, 302, and 303, and 301 and 302 are agents of the same type. Since the flow of the process is basically the same as that described in FIG. 5 above, the description will focus on the different points.

[0106] In this modification, after the controller 200 transmits the update file to the agent 301 (step S1208), it does not wait for the completion notification and performs the update of its own device (step S1511). Then, it deletes the update file (step S1512) and restarts (step S1513).

[0107] In the agent 301, after restarting (step S1211), it performs mesh connection in the same manner as above (step S1213). However, at this time, in the controller 200, during the period of the process of deleting the update file 211, the mesh connection may be configured to be performed after a certain time. Alternatively, the mesh connection may be tried at a predetermined time interval.

[0108] When the controller 200 restarts after FW update, the mesh Wi-Fi within the network 100 becomes unavailable. According to this modification, by performing the FW update of the controller 200 and one agent 300 in the same time zone, the time zone during which the mesh Wi-Fi cannot be used can be reduced.

[0109] <Modification 3> In addition, in each of the above-described embodiments and modification examples, when the agent 300 inquires about the type and version of the FW in the FW inquiry 530 and analyzes the received FW response 540, the controller 200 determines whether an update is necessary. However, the determination of necessity is not limited to this.

[0110] For example, the agent 300 may be configured to inquire only about the type of FW, and the necessity of update may be determined on the side of each agent 300.

[0111] That is, in step S1107 of the second embodiment, when it is determined to be of the same type, the agent update unit 240 of the controller 200 transmits the update information 550 to the agent 300 regardless of the version.

[0112] The AGT control unit 320 of the agent 300 compares the version 523 in the update information 550 with the version information of the FW currently installed in its own device, and determines whether an update is necessary. If it is determined that an update is required, a request to start the update is transmitted to the controller 200. On the other hand, if it is determined that an update is not required, a request to start the update is not transmitted. At this time, a response indicating that an update is not required may be returned.

[0113] After transmitting the update information 550, if the agent update unit 240 of the controller 200 does not receive a request to start the update after waiting for a predetermined period, it transmits the update information to the next agent 300.

[0114] <Modification Example 4> Furthermore, in each of the above-described embodiments and modification examples, when the slave unit 400 is not connected to the agent 300, the agent 300 is configured to be updated, but it is not limited to this.

[0115] That is, when the agent 300 receives the update information 550, it creates an update schedule without determining the presence or absence of the slave device 400 to be connected. Then, it returns an update start request according to the update schedule created by its own device, and performs an update when it receives the update file 211.

[0116] In this case, for example, including the controller 200, FW updates may be performed for all devices of the same type in the network 100 at the same time zone. Thereby, the time zone when the mesh Wi-Fi cannot be used can be significantly reduced.

[0117] <Modification Example 5> Also, in the above embodiment, when the controller 200 determines that the FW of its own device needs to be updated, it checks the FW type and version information of each agent 300 in the network 100 every time. However, it is not limited to this.

[0118] For example, in the previous FW update, the created FW management table 510 may be referred to for judgment. In this case, the type discrimination unit 230 may not be provided.

[0119] After the CNT control unit 220 determines that an update is required and acquires the update file 211 from the external server 800, the agent update unit 240 refers to the FW type 512 of the FW management table 510 to identify the agents 300 of the same type. Then, based on the version 513, it determines whether each agent 300 needs to be updated, and transmits the update information 550 (and / or the update file 211) to the agents 300 that need to be updated in a predetermined order.

[0120] <Modification Example 6> Note that the CNT storage unit 210 of the controller 200 and the AGT storage unit 310 of the agent 300 may be areas connected by the NAS (Network Attached Storage) function.

[0121] <Modification Example 7> Furthermore, in each of the above embodiments and variations, when the FW of the own device needs to be updated, the controller 200 acquires the update file and performs subsequent processing. However, it is not limited to this. For example, after acquiring the update information in step S1101 above, the controller 200 periodically sends the FW inquiry of step S1105 to each agent 300. And when there is an agent 300 that needs to be updated, the controller 200 may be configured to acquire the update file from the external server 800 and perform subsequent processing.

[0122] Note that in this case, the controller 200 holds the update file in the FW management table 510 until the update of all AGTs of the same type as the agent 300 whose FW type 512 needs to be updated is completed.

[0123] Also in this variation, since each individual agent 300 does not download a large-capacity update file from the external server 800 respectively, the communication volume of the entire system can be suppressed.

[0124] <Variation 8> In addition, each agent 300 may also have the same function as the controller 200. That is, it sends an FW inquiry to another agent 300 that communicates wirelessly with the own device, and discriminates whether they are of the same type and whether an update is required. And if an update is required, it sends the update information to the other agent 300, and when receiving an update start request, it sends the update file from the agent 300.

[0125] For example, in the above network 100, since the agent 303 is outside the range of wireless communication with the controller 200 via the CNT second communication unit 270 and the AGT second communication unit 370 as described above, in each of the above embodiments and variations, it is discriminated as different types and the FW is not updated. However, according to this variation, even such an agent 303 can update the FW in the same manner as above as long as they are of the same type.

[0126] <Variation 9> Also, in each of the above-described embodiments and modifications, the case where the software to be updated is firmware has been described as an example, but the software to be updated is not limited to this. For example, it may be a certificate inside the router or the like.

[0127] [Hardware Configuration] The above-described controller 200 and agent 300 may be realized by, for example, a general-purpose information processing device.

[0128] A general-purpose information processing device includes, for example, as shown in FIG. 8, a CPU (Central Processing Unit) 691, a main storage device (memory) 692, an auxiliary storage device 693, a communication I / F 694, and an expansion I / F 695, which are interconnected by an internal bus.

[0129] The CPU 691 realizes each of the above functions and comprehensively controls the entire controller 200 and agent 300 by, for example, loading a program stored in the auxiliary storage device 693 into the main storage device 692 and executing it. Note that one or more processors such as an MPU (Micro Processing Unit) may be used instead of the CPU 691.

[0130] The main storage device 692 is a memory such as a RAM (Random Access Memory). The main storage device 692 is a work area when the CPU 691 processes programs and the like executed by each of the controller 200 and agent 300.

[0131] The auxiliary storage device 693 is, for example, a ROM (Read Only Memory), HDD (Hard Disk Drive), SSD (Solid State Drive), etc. The auxiliary storage device 693 stores various programs executed by the controller 200 and the agent 300 respectively. Note that the auxiliary storage device 693 may include storage media such as a flexible disk, hard disk, optical disk, CD-ROM, CD-R, magnetic tape, non-volatile memory card, DVD, etc.

[0132] In addition, the programs stored in the auxiliary storage device 693 can be provided as a program product recorded on a non-transitory computer-readable storage medium. The auxiliary storage device 693 can be used to store various programs recorded on a non-transitory computer-readable storage medium in the medium to long term.

[0133] The communication I / F 694 is an interface for input / output of signals and data by wire or wirelessly. For example, it realizes the CNT first communication unit 260, CNT second communication unit 270, AGT first communication unit 360, and AGT second communication unit 370.

[0134] The expansion I / F 695 is an interface for connecting a display device, an input device, etc. The display device is, for example, a liquid crystal monitor, etc. The input device is a device that accepts user operations such as a keyboard and a mouse, etc.

[0135] Each of the above functions (each server) of the controller 200 and the agent 300 is realized by the CPU 691 loading and executing the programs stored in the auxiliary storage device 693 into the main storage device 692 respectively.

[0136] Also, the CNT storage unit 210 and the AGT storage unit 310 are constructed in the auxiliary storage device 693, for example.

[0137] Note that the hardware configurations of the controller 200 and the agent 300 are not limited to this. They may include hardware not shown in the figures.

[0138] Also, the programs for implementing the respective functions of the controller 200 and the agent 300 in this embodiment can be recorded on a computer-readable storage medium. The storage medium can be a non-transient one such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, etc. The present invention can also be embodied as a computer program product.

[0139] Moreover, each function of the controller 200 and the agent 300 may be implemented by, for example, an integrated circuit (IC) dedicated to each process, an application-specific integrated circuit (ASIC), a system-on-chip (SOC), a field-programmable gate array (FPGA), etc.

[0140] In the process flow used in the above description, a plurality of steps (processes) are described in order, but the execution order of each step is not limited to the described order. For example, the order of the illustrated steps can be changed within a range that does not substantially affect the content, such as executing each process in parallel.

[0141] As described above, each embodiment and modification of the present invention have been explained. However, the present invention is not limited to the above-described embodiments, and various changes that can be understood by those skilled in the art can be made. And each embodiment and modification can be combined with other embodiments as appropriate. Also, for example, the network configurations and the configurations of each element shown in each drawing are examples for assisting the understanding of the present invention, and are not limited to the configurations shown in these drawings.

[0142] Finally, the preferred forms of the present invention are summarized. Some or all of the above embodiments can also be described as follows in the appended claims, but are not limited thereto. (Appended Claim 1) The mesh controller is A storage unit that stores update files, and a control unit that controls the update of software installed in mesh agents in a mesh network using the update files, The control unit, includes a type discrimination unit that discriminates the type of the software installed in the mesh agent, and an agent update unit that controls the update of the same-type agent, which is the mesh agent in which the same-type software as the own device is installed, The agent update unit, discriminates whether the update of the same-type agent is necessary, sends update information to the same-type agent for which the update is determined to be necessary, when a start update request is returned from the same-type agent after the transmission of the update information, sends the update file to the same-type agent that is the reply source, The start update request is transmitted when no terminal device is connected to the same-type agent. (Supplementary Note 2) In the mesh controller according to Supplementary Note 1 or 11, the agent update unit, even if the start update request is received, when another same-type agent is in the process of updating, it is desirable not to send the update file to the same-type agent that is the reply source. (Supplementary Note 3) In the mesh controller according to any one of Supplementary Notes 1, 2, and 11, it is desirable that the control unit perform the update of the own device using the update file after the update of all the same-type agents in the mesh network is completed. (Supplementary Note 4) In the mesh controller according to any one of Supplementary Notes 1 to 3, 11, and 12, it is desirable that the software to be updated is firmware. (Supplementary Note 5) The mesh agent, It is provided with a control unit that controls the update of the software of the device, The control unit, when receiving update information from a mesh controller in a mesh network, discriminates whether there is a connection to a terminal device, and if there is no connection, transmits an update start request to the mesh controller, uses the update file transmitted from the mesh controller in response to the update start request to perform the update of the device itself, when the update is completed, transmits an update completion notification to the mesh controller. (Appendix 6) In the mesh agent described in Appendix 5 or Appendix 13, it is desirable that the control unit transmits the update start request at a predetermined time interval after transmitting the update start request until receiving the update file. (Appendix 7) A mesh network system including a mesh controller and a mesh agent, The mesh controller, has a storage unit that stores an update file, and a controller-side control unit that controls the update of the software of the mesh controller and the mesh agent using the update file, The mesh agent is provided with an agent-side control unit that controls the update of the device itself, The controller-side control unit, has a type discrimination unit that discriminates the type of the software installed in the mesh agent, and an agent update unit that controls the update of the same-type agent, which is the mesh agent in which the same type of software as the mesh controller is installed, The agent update unit, discriminates the necessity of the update of the same-type agent, transmits update information to the same-type agent determined to require the update, When an update start request is returned from the same type of agent after the transmission of the update information, the update file is transmitted to the same type of agent that is the source of the return. The agent side control unit When receiving the update information from the mesh controller, it determines the presence or absence of a connection to a terminal device. If there is no connection, it transmits the update start request to the mesh controller. Using the update file transmitted from the mesh controller in response to the update start request, it performs the update of the own device. When the update is completed, it transmits an update completion notification to the mesh controller. (Appendix 8) A software update method for updating the software of a mesh controller and a mesh agent in a mesh network system including a mesh controller and a mesh agent, comprising: The mesh controller Determines the type of software to be installed in the mesh agent. Determines the necessity of updating the mesh agent in which the same type of software as the own device is installed. Transmits update information to the mesh agent determined to require the update. When the mesh agent receives the update information, it determines the presence or absence of a connection to a terminal device. If there is no connection, it transmits an update start request to the mesh controller. When the mesh controller receives the update start request, it transmits the update file of the software stored in the own device to the mesh agent that is the source of the return. The mesh agent performs the update using the update file received from the mesh controller, and when the update is completed, it transmits an update completion notification to the mesh controller. (Appendix 9) The computer built into the mesh controller Type discrimination means for discriminating the type of software installed in a mesh agent within a mesh network, A program for functioning as agent update means that discriminates whether software update is necessary for a same-type agent which is the mesh agent installed with the same type of software as the mesh controller, transmits update information to the same-type agent for which it is determined that the update is necessary, and when an update start request is returned from the same-type agent when no terminal device is connected to the same-type agent after the transmission of the update information, transmits the update file stored in its own device to the same-type agent that is the source of the reply. (Appendix 10) A computer built into a mesh agent, When receiving update information from a mesh controller within a mesh network, discriminates whether a terminal device is connected, and when there is no connection, transmits an update start request to the mesh controller, updates the software installed in the mesh agent using the update file transmitted from the mesh controller in response to the update start request, and when the update is completed, transmits an update completion notification to the mesh controller. A program for functioning as control means. (Appendix 11) The mesh controller, A storage unit for storing an update file, Comprises a control unit for controlling the update of software installed in a mesh agent within a mesh network using the update file. The control unit, A type discrimination unit for discriminating the type of the software installed in the mesh agent, Comprises an agent update unit for controlling the update of the same-type agent which is the mesh agent installed with the same type of software as its own device. The agent update unit, Discriminates whether the update of the same-type agent is necessary, Send update information to the homogeneous agent for which the update is determined to be necessary, When an update start request is returned from the homogeneous agent after the transmission of the update information, send the update file to the homogeneous agent that is the source of the reply. (Appendix 12) In the mesh controller according to Appendix 11, After receiving the update request from a plurality of the homogeneous agents, the agent update unit transmits the update file to the homogeneous agent that is the source of the update request, and also performs the update of its own device. A mesh controller. (Appendix 13) A mesh agent, Comprises a control unit for controlling the update of the software of its own device, The control unit, When receiving update information from a mesh controller in a mesh network, send an update start request to the mesh controller, Using the update file transmitted from the mesh controller in response to the update start request, perform the update of the own device, When the update is completed, send an update completion notification to the mesh controller. Note that the forms of Appendices 7, 8, and 10 can be developed into the forms of Appendices 2-4 in the same manner as Appendix 1. The forms of Appendices 7, 8, and 11 can be developed into the form of Appendix 6 in the same manner as Appendix 5.

[0143] In addition, the disclosures of the above patent documents and the like are incorporated herein by reference. Within the scope of the entire disclosure of the present invention (including the claims), modifications and adjustments of the embodiments or variations can be made based on the basic technical idea. Also, within the scope of the disclosure of the present invention, various combinations or selections of various disclosure elements (including each element of each claim, each element of each embodiment or variation, each element of each drawing, etc.) are possible. That is, the present invention naturally includes the entire disclosure including the claims, and various modifications and corrections that could be made by those skilled in the art according to the technical idea. In particular, regarding the numerical ranges described in this document, any numerical value or small range included within the range should be construed as specifically described even without separate description.

Explanation of Signs

[0144] 100: Network, 100a: Network, 200: Controller, 200a: Controller, 210: CNT Storage Unit, 211: Update File, 220: CNT Control Unit, 230: Type Discrimination Unit, 240: Agent Update Unit, 260: CNT First Communication Unit, 270: CNT Second Communication Unit, 300: Agent, 300a: Agent, 301: Agent, 302: Agent, 303: Agent, 310: AGT Storage Unit, 320: AGT Control Unit, 360: AGT First Communication Unit, 370: AGT Second Communication Unit, 400: Subordinate Device, 510: FW Management Table, 511: ID, 512: FW Type, 513: Version, 514: Completion Flag, 520: Update Information, 522: FW Type, 523: Version, 530: FW Inquiry, 531: AGT ID, 532: Inquiry Content, 540: FW Response, 541: AGT ID, 542: FW Type, 543: Version, 550: Update Information, 551: AGT ID, 691: CPU, 692: Main Memory Device, 693: Auxiliary Storage Device, 694: Communication I / F, 695: Expansion I / F, 800: External Server, 801: WAN

Claims

1. A storage unit that stores an update file, A control unit that controls the update of software installed in mesh agents within a mesh network using the update file, and The control unit includes A type discrimination unit that discriminates the type of the software installed in the mesh agent, An agent update unit that controls the update of the same-type agent, which is the mesh agent in which the same-type software as the own device is installed, and The agent update unit includes Determines whether the update of the same-type agent is necessary, Sends update information to the same-type agent for which the update is determined to be necessary, When an update start request is returned from the same-type agent after the transmission of the update information, transmits the update file to the same-type agent that is the source of the reply, and The update start request is transmitted when a terminal device is not connected to the same-type agent. A mesh controller.

2. The mesh controller according to claim 1, wherein The agent update unit Even if the update start request is received, when another same-type agent is in the process of updating, does not transmit the update file to the same-type agent that is the source of the reply. A mesh controller.

3. The mesh controller according to claim 1, wherein The control unit performs the update of the own device using the update file after the update of all the same-type agents within the mesh network is completed. A mesh controller.

4. The mesh controller according to claim 1, wherein The software for performing the update is firmware. A mesh controller.

5. A control unit that controls the update of the software of the own device, and The control unit includes When receiving update information from a mesh controller within a mesh network, determines the presence or absence of a connection to a terminal device, and if there is no connection, transmits an update start request to the mesh controller, Performs the update of the own device using the update file transmitted from the mesh controller in response to the update start request, and When the update is completed, transmits an update completion notification to the mesh controller. A mesh agent.

6. The mesh agent according to claim 5, wherein The control unit is a mesh agent that, after sending the update start request, sends the update start request to the mesh controller at a predetermined time interval until the update file is received.

7. A mesh network system comprising a mesh controller and a mesh agent, wherein the mesh controller comprises a storage unit for storing an update file, and a controller-side control unit for controlling the update of the software of the mesh controller and the mesh agent using the update file, the mesh agent comprises an agent-side control unit for controlling the update of the self-device, the controller-side control unit comprises a type discrimination unit for discriminating the type of the software installed in the mesh agent, and an agent update unit for controlling the update of the same-type agent, which is the mesh agent in which the same-type software as the mesh controller is installed, the agent update unit discriminates the necessity of the update of the same-type agent, sends update information to the same-type agent for which the update is determined to be necessary, and when an update start request is returned from the same-type agent after the transmission of the update information, sends the update file to the same-type agent that is the source of the return, the agent-side control unit when receiving the update information from the mesh controller, discriminates the presence or absence of a connection to a terminal device, and if there is no connection, sends the update start request to the mesh controller, performs the update of the self-device using the update file transmitted from the mesh controller in response to the update start request, and when the update is completed, sends an update completion notification to the mesh controller.

8. A software update method for updating the software of the mesh controller and the mesh agent in a mesh network system comprising a mesh controller and a mesh agent, wherein the mesh controller discriminates the type of the software to be installed in the mesh agent, discriminates the necessity of the update of the mesh agent in which the same-type software as the self-device is installed, and sends update information to the mesh agent for which the update is determined to be necessary. When the mesh agent receives the update information, it determines whether a terminal device is connected. If there is no connection, it sends a update start request to the mesh controller. When the mesh controller receives the update start request, it sends the update file of the software stored in its own device to the mesh agent that is the source of the request. A software update method in which the mesh agent performs the update using the update file received from the mesh controller, and when the update is completed, sends a update completion notification to the mesh controller.

9. A computer built into a mesh controller, is used as a type discrimination means for discriminating the type of software installed in a mesh agent within a mesh network, determines whether the software of the same type agent, which is the mesh agent installed with the same type of software as the mesh controller, needs to be updated, sends update information to the same type agent determined to need the update, and if a update start request is returned from the same type agent when no terminal device is connected to the same type agent after sending the update information, functions as an agent update means for sending the update file stored in its own device to the same type agent that is the source of the return.

10. A computer built into a mesh agent, is used as a control means for determining whether a terminal device is connected when receiving update information from a mesh controller within a mesh network, sending a update start request to the mesh controller if there is no connection, performing an update of the software installed in the mesh agent using the update file sent from the mesh controller in response to the update start request, and sending a update completion notification to the mesh controller when the update is completed.

Images