Mesh network system and mesh network operation method

Abstract

Create a schedule that maximizes power saving across the entire network, and then configure power saving settings according to that schedule. [Solution] In a mesh network system in which a mesh controller and mesh agents relay wireless communication, the mesh controller and mesh agents collect the amount of wireless communication and signal strength in the mesh network, the mesh agents transmit statistical information of the amount of wireless communication and signal strength to the mesh controller, and the mesh controller uses the statistical information of the amount of wireless communication and signal strength to determine whether or not to enable power saving mode for the mesh controller and mesh agents.

Description

Technical Field

[0001] The present invention relates to a mesh network system and a method for operating a mesh network.

Background Art

[0002] In recent years, the opportunity for various devices to communicate with the Internet has increased. Also, due to the spread of mesh networks, multiple APs (Access Points) are being installed indoors so that multiple devices can perform Internet communication anywhere in the house. However, installing multiple APs increases the environmental load.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] Note that each disclosure of the above prior art documents is incorporated herein by reference. The following analysis was made by the inventors of the present invention.

[0005] By the way, various methods have been proposed as methods for performing power saving settings. However, the conventional methods for performing power saving settings have the following problems.

[0006] The first challenge is the inconvenience it creates for the user. One method involves the user specifying the transition and deactivation times for power saving settings, and then enabling the power saving settings within those times. During power saving mode, communication is reduced to a slower speed or communication functions are disabled to conserve power. However, this method requires the user to recognize the connection and communication information of the wireless client terminals before configuring the settings, thus requiring user intervention. Furthermore, as the number of access points (APs) increases, the settings must be configured for each AP individually, increasing the user's workload.

[0007] The second challenge is that it is difficult to achieve power saving effects during periods of low communication volume. For example, Patent Document 1 proposes a method to reduce unnecessary power consumption by pre-associating and registering the optimal mesh agent for each wireless client terminal, and then returning the target mesh agent from power-saving mode to normal mode when the terminal is in use. However, since this method makes a determination based only on the connection status of the wireless client terminal, even if multiple wireless client terminals are each connected to different APs, all APs will operate in normal mode during periods when none of the terminals are using the internet, resulting in a situation where it is difficult to achieve power saving effects.

[0008] The third challenge is the inability to construct an effective network configuration in a multi-stage setup (a configuration in which wireless client terminals communicate via multiple access points (APs) to perform internet communication). Patent document 2 proposes a method to reduce power consumption while meeting transmission speed requirements by measuring the signal strength of the wireless client terminal, measuring the signal strength with standby APs if the signal strength is below a threshold, and switching APs with signal strength above the threshold to an active state. However, even in a multi-stage setup, this method results in situations where internet communication does not occur because APs not connected to wireless client terminals enter a standby state.

[0009] The object of the present invention is, in view of the above-mentioned problems, to provide a mesh network system and a mesh network operation method that contribute to creating a schedule that maximizes the power saving effect of the entire network and to performing power saving settings in accordance with the schedule. [Means for solving the problem]

[0010] In a first aspect of the present invention, a mesh network system is provided in which a mesh controller and mesh agents relay wireless communication, wherein the mesh controller and mesh agents collect the amount of communication and signal strength of wireless communication in the mesh network, the mesh agents transmit statistical information of the amount of communication and signal strength of wireless communication to the mesh controller, and the mesh controller uses the statistical information of the amount of communication and signal strength of wireless communication to determine whether or not to enable power saving mode for the mesh controller and mesh agents.

[0011] A second aspect of the present invention provides a mesh network operation method in which a mesh controller and mesh agents relay wireless communication, wherein the mesh controller and mesh agents collect the amount of communication and signal strength of wireless communication in the mesh network, the mesh agents transmit statistical information of the amount of communication and signal strength of wireless communication to the mesh controller, and the mesh controller uses the statistical information of the amount of communication and signal strength of wireless communication to determine whether or not to enable power saving mode for the mesh controller and mesh agents. [Effects of the Invention]

[0012] According to each aspect of the present invention, it is possible to provide a mesh network system and a mesh network operation method that contribute to creating a schedule that maximizes the power saving effect of the entire network and to performing power saving settings in accordance with the schedule. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a schematic diagram of the network environment constructed according to an embodiment of the present invention. [Figure 2] Figure 2 is a flowchart of an embodiment of the present invention. [Figure 3] Figure 3 illustrates the configuration of a mesh network. [Figure 4] Figure 4 is a schematic diagram of the network environment constructed according to an embodiment of the present invention. [Figure 5] Figure 5 is a flowchart for determining which device should be in normal mode in an embodiment of the present invention. [Figure 6] Figure 6 is a flowchart showing the mode determination process for all devices in the embodiments of the present invention. [Figure 7] Figure 7 is a flowchart for classifying the power saving modes of the embodiment of the present invention. [Figure 8] Figure 8 shows an example of a schedule generated in an embodiment of the present invention. [Figure 9] Figure 9 is a schematic diagram of a network environment used in another embodiment of the present invention. [Figure 10] Figure 10 is a flowchart of another embodiment of the present invention. [Figure 11] Figure 11 shows a sequence of mode determination for each device for a wireless terminal 1 in another embodiment of the present invention. [Figure 12] Figure 12 shows the sequence for determining the mode of each device for wireless terminals 2 and 3 in another embodiment of the present invention. [Modes for carrying out the invention]

[0014] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention is not limited by the embodiments described below. Also, in each drawing, the same or corresponding elements are appropriately assigned the same reference numerals. Furthermore, it should be noted that the drawings are schematic, and the dimensional relationships, ratios of each element, etc. may be different from the actual ones. There may also be parts where the dimensional relationships and ratios are different between the drawings.

[0015] FIG. 1 is an overview diagram of a network environment constructed in an embodiment of the present invention. FIG. 2 is a flowchart of an embodiment of the present invention. As shown in FIG. 1, the network environment constructed in the embodiment of the present invention includes a mesh controller (3100), a mesh agent (3200), a mesh agent 2 (3201), a mesh agent 3 (3202), a wireless terminal 1 (3300), a wireless terminal 2 (3301), and a wireless terminal 3 (3302). And the network environment constructed in the embodiment of the present invention performs the processes shown in the flowchart of FIG. 2.

[0016] The mesh controller (3100), the mesh agent (3200), the mesh agent 2 (3201), and the mesh agent 3 (3202) collect statistical information such as the time, traffic volume, and radio wave intensity when performing wireless communication with the wireless terminal 1 (3300), the wireless terminal 2 (3301), the wireless terminal 3 (3302), other mesh controllers (3100), the mesh agent (3200), the mesh agent 2 (3201), and the mesh agent 3 (3202) (S201).

[0017] The mesh controller (3100) analyzes the collected statistical information of wireless communication with wireless terminals and classifies each device into either normal mode or power saving mode (S202). The mesh controller (3100) analyzes the collected statistical information between the mesh controller (3100), mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202) and classifies each device into either partial power saving mode or full power saving mode (S203).

[0018] The mesh controller (3100) performs these classifications for each schedule and creates a schedule (S204). The mesh controller (3100), mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202) switch to power saving mode according to the schedule (S205).

[0019] Figure 3 is a diagram illustrating the configuration of a mesh network. As shown in Figure 3, the mesh network (3000) comprises a mesh controller (3100), a mesh agent (3200), a mesh agent 2 (3201), a mesh agent 3 (3202), a wireless terminal 1 (3300), a wireless terminal 2 (3301), and a wireless terminal 3 (3302).

[0020] The mesh controller (3100) is a device that manages the mesh network (3000) and includes a fronthaul wireless access point interface (IF) (3110), a backhaul wireless access point interface (IF) (3120), a WAN (Wide Area Network) interface (3130), a monitoring unit (3140), a management unit (3150), a schedule generation unit (3160), and a control unit (3170).

[0021] The fronthaul wireless access point IF (3110) is the physical interface for wireless communication with wireless terminal 1 (3300). The backhaul wireless access point IF (3120) is the physical interface for wireless communication with the backhaul wireless station IF (3230) of the mesh agent (3200). The WAN IF (3130) is the physical interface for connecting the mesh controller (3100) to the internet.

[0022] The monitoring unit (3140) monitors communication statistics of the fronthaul wireless access point IF (3110) and backhaul wireless access point IF (3120), and includes a fronthaul statistics monitoring unit (3141) and a backhaul statistics monitoring unit (3142). The fronthaul statistics monitoring unit (3141) monitors statistics such as communication volume and communication speed when the fronthaul wireless access point IF (3110) communicates with wireless terminal 1 (3300). The backhaul statistics monitoring unit (3142) monitors statistics such as communication volume and communication speed when the backhaul wireless access point IF (3120) communicates with the mesh agent (3200)'s backhaul wireless station IF (3230).

[0023] The Management Unit (3150) manages statistical information acquired by the Monitoring Unit (3140), information on connected wireless terminals 1 (3300), information on mesh agents (3200) that constitute the mesh network (3000), and schedules for power saving settings. It comprises a Fronthaul Statistics Management Unit (3151), a Backhaul Statistics Management Unit (3152), a Terminal Information Management Unit (3153), a Mesh Agent Information Management Unit (3154), and a Schedule Management Unit (3155). The Fronthaul Statistics Management Unit (3151) manages statistical information acquired by the Fronthaul Statistics Monitoring Unit (3141). The Backhaul Statistics Management Unit (3152) manages statistical information acquired by the Backhaul Statistics Monitoring Unit (3142). The Terminal Information Management Unit (3153) manages unique information such as MAC (Media Access Control) addresses of wireless terminals 1 (3300) present in the mesh network (3000).

[0024] The Mesh Agent Information Management Unit (3154) manages unique information such as MAC addresses of mesh agents (3200) present within the mesh network (3000), as well as statistical information managed by the Mesh Agent (3200) Management Unit (3250), for each mesh agent (3200). The Schedule Management Unit (3155) manages the schedule for power saving settings of the mesh controller (3100) and mesh agents (3200).

[0025] The schedule generation unit (3160) generates a power saving setting schedule for the entire network from the statistical information managed by the fronthaul statistical information management unit (3151), the backhaul statistical information management unit (3152), and the mesh agent information management unit (3154).

[0026] The control unit (3170) has a function to switch the fronthaul wireless access point IF (3110) and backhaul wireless access point IF (3120) of the mesh controller (3100) to power-saving settings according to the power-saving schedule.

[0027] The mesh agent (3200) is a device that relays wireless communication in a mesh network (3000) and includes a fronthaul wireless access point IF (3210), a backhaul wireless access point IF (3220), a backhaul wireless station IF (3230), a monitoring unit (3240), a management unit (3250), and a control unit (3260).

[0028] The fronthaul wireless access point IF (3210) is a physical interface that communicates wirelessly with wireless terminals 1 (3300), 2 (3301), and 3 (3302). The backhaul wireless access point IF (3220) is a physical interface that communicates wirelessly with the backhaul wireless station IF (3230) of other mesh agents (3200). The backhaul wireless station IF (3230) is a physical interface that communicates wirelessly with the backhaul wireless access point IF (3120) of the mesh controller (3100) and the backhaul wireless access point IF (3220) of other mesh agents (3200).

[0029] The monitoring unit (3240) monitors communication statistics for the fronthaul wireless access point IF (3210), backhaul wireless access point IF (3220), and backhaul wireless station IF (3230), and includes a fronthaul statistics monitoring unit (3241) and a backhaul statistics monitoring unit (3242). The fronthaul statistics monitoring unit (3241) monitors statistics such as communication volume and communication speed when the fronthaul wireless access point IF (3210) communicates with wireless terminal 1 (3300). The backhaul statistics monitoring unit (3242) monitors statistics such as communication volume and communication speed when the backhaul wireless access point IF (3220) and backhaul wireless station IF (3230) communicate with the mesh controller (3100) and other mesh agents (3200).

[0030] The Management Unit (3250) manages statistical information and connected terminal information acquired by the Monitoring Unit (3240), as well as the schedule for power saving settings generated by the Mesh Controller (3100). It comprises the Fronthaul Statistical Information Management Unit (3251), Backhaul Statistical Information Management Unit (3252), Terminal Information Management Unit (3253), and Schedule Management Unit (3254). The Fronthaul Statistical Information Management Unit (3251) manages statistical information acquired by the Fronthaul Statistical Information Monitoring Unit (3241). The Backhaul Statistical Information Management Unit (3252) manages statistical information acquired by the Backhaul Statistical Information Monitoring Unit (3242). The Terminal Information Management Unit (3253) manages terminal information present within the Mesh Network (3000). The Schedule Management Unit (3254) manages the schedule for power saving settings for its own device.

[0031] The control unit (3260) has a function to switch the fronthaul wireless access point IF (3210), backhaul wireless access point IF (3220), and backhaul wireless station IF (3230) of the mesh agent (3200) to power saving settings in accordance with the power saving schedule managed by the schedule management unit (3254).

[0032] Mesh agent 2 (3201) is a device that relays wireless communication in the mesh network (3000) and has the same functions as mesh agent (3200). Mesh agent 3 (3202) is a device that relays wireless communication in the mesh network (3000) and has the same functions as mesh agent (3200).

[0033] Wireless terminal 1 (3300) is a device connected to the mesh controller (3100) or mesh agent (3200), and refers to a device that performs internet communication, such as a smartphone or IoT (Internet of Things) device such as a home appliance.

[0034] Wireless terminal 2 (3301), like wireless terminal 1 (3300), is a device connected to the mesh controller (3100) or mesh agent (3200), and refers to a device that performs internet communication, such as a smartphone or IoT (Internet of Things) device like a home appliance.

[0035] Wireless terminal 3 (3302), like wireless terminal 1 (3300), is a device connected to the mesh controller (3100) or mesh agent (3200), and refers to a device that performs internet communication, such as a smartphone or IoT (Internet of Things) device such as a home appliance.

[0036] Note that while Figure 3 shows a configuration with three mesh agents and three wireless terminals, there may be one mesh agent and one wireless terminal, or three or more.

[0037] Next, the operation of an embodiment of the present invention will be described. Figure 4 is a schematic diagram of the network environment constructed in an embodiment of the present invention. The network environment constructed in an embodiment of the present invention includes a mesh controller (3100), a mesh agent (3200), a mesh agent 2 (3201), a mesh agent 3 (3202), a wireless terminal 1 (3300), a wireless terminal 2 (3301), and a wireless terminal 3 (3302).

[0038] Wireless terminal 1 (3300) is connected to the mesh controller (3100), wireless terminal 2 (3301) is connected to mesh agent 3 (3202), and wireless terminal 3 (3302) is connected to mesh agent 2 (3201). Furthermore, mesh agent (3200) is assumed to relay communication between the mesh controller (3100) and mesh agent 3 (3202). Additionally, the unique information of the devices within the mesh network is assumed to be as shown in Table 1 below.

[0039] [Table 1]

[0040] The mesh controller (3100) monitors the communication volume and radio wave strength of wireless terminal 1 (3300), which is connected to its own device and is managed by the terminal information management unit (3153) as shown in Table 2 below, when it communicates via the fronthaul wireless access point IF (3110), using the fronthaul statistical information monitoring unit (3141).

[0041] [Table 2]

[0042] The mesh controller (3100) then formats the time, along with the MAC address of the wireless terminal, into a CSV (Comma-Separated Values) format, as shown in Table 3 below, and manages it in the fronthaul statistical information management unit (3151).

[0043] [Table 3]

[0044] Furthermore, the mesh controller (3100) communicates with mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202) via the backhaul wireless access point IF (3120). The communication volume and signal strength are monitored by the backhaul statistical information monitoring unit (3142), and the data, along with the time and MAC address of mesh agent (3200), is formatted into CSV format as shown in Table 4 below, and managed by the backhaul statistical information management unit (3152).

[0045] [Table 4]

[0046] Furthermore, a wireless communication device will receive all wireless communications taking place near it and discard communications not intended for itself. Since the signal strength at this time can be measured, this function is utilized in this embodiment.

[0047] The mesh controller (3100) monitors the communication between the mesh agent 3 (3202) and the wireless terminal 2 (3301), which is not connected to the mesh controller (3100), using the fronthaul wireless access point IF (3110).

[0048] The mesh controller (3100) monitors the signal strength with respect to wireless terminal 2 (3301) using the fronthaul statistical information monitoring unit (3141). As shown in Table 5 below, it formats the signal strength along with the MAC address of wireless terminal 1 (3300) at that time into CSV format and manages it using the fronthaul statistical information management unit (3151).

[0049] [Table 5]

[0050] The mesh controller (3100) monitors the communication between the mesh agent 2 (3201) and the wireless terminal 3 (3301), which is not connected to the mesh controller (3100), using the fronthaul wireless access point IF (3110).

[0051] The mesh controller (3100) monitors the signal strength with respect to wireless terminal 2 (3301) using the fronthaul statistical information monitoring unit (3141). As shown in Table 5 above, it formats the signal strength along with the MAC address of wireless terminal 1 (3300) at that time into CSV format and manages it using the fronthaul statistical information management unit (3151).

[0052] Furthermore, the data format of the statistical information managed by the Fronthaul Statistical Information Management Department (3151) and the Backhaul Statistical Information Management Department (3152) may be managed in formats other than CSV, such as JSON (JavaScript® Object Notation) format or XML (Extensible Markup Language) format.

[0053] The mesh agent (3200) does not manage statistical information as shown in Table 3 above, because there are no wireless terminals connected to its own device among the wireless terminals managed by the terminal information management unit (3253) as shown in Table 2 above.

[0054] Meanwhile, the mesh agent (3200) communicates with the mesh controller (3100) and mesh agent 3 (3202) via the backhaul wireless access point IF (3220), and the communication volume and signal strength are monitored by the backhaul statistical information monitoring unit (3142). The mesh agent (3200) formats this information, along with the time and MAC address of the mesh agent (3200), into CSV format as shown in Table 4 above, and manages it with the backhaul statistical information management unit (3152).

[0055] Furthermore, a wireless communication device will receive all wireless communications taking place near it and discard communications not intended for itself. Since the signal strength at this time can be measured, this function is utilized in this embodiment.

[0056] The mesh agent (3200) monitors the communication between wireless terminal 1 (3300), which is not connected to the mesh agent (3200), and the mesh controller (3100) using the fronthaul wireless access point IF (3210). The mesh agent (3200) monitors the signal strength to wireless terminal 1 (3300) using the fronthaul statistical information monitoring unit (3141), and formats it into CSV format along with the MAC address of wireless terminal 1 (3300) at that time, as shown in Table 5 above, and manages it with the fronthaul statistical information management unit (3151).

[0057] The mesh agent (3200) monitors the communication between wireless terminal 2 (3301), which is not connected to the mesh agent (3200), and mesh agent 3 (3202) using the fronthaul wireless access point IF (3210). The mesh agent (3200) monitors the signal strength between wireless terminal 2 (3301) and the mesh agent (3200) using the fronthaul statistical information monitoring unit (3241), and formats this information, along with the MAC address of wireless terminal 2 (3301) at that time, into CSV format as shown in Table 5 above, and manages it with the fronthaul statistical information management unit (3251).

[0058] The mesh agent (3200) transmits the statistical information managed by the fronthaul statistical information management unit (3251) in CSV format to the mesh controller (3100) via the backhaul wireless station IF (3230) using IPv4 (Internet Protocol version 4) TCP (Transmission Control Protocol).

[0059] The mesh agent (3200) transmits the statistical information managed by the fronthaul statistical information management unit (3251), and then transmits the statistical information managed by the backhaul statistical information management unit (3252) to the mesh controller (3100) via the backhaul wireless station IF (3230) using the IPv4 TCP protocol.

[0060] The mesh agent (3200) processes and transmits this statistical information every hour. The transmission cycle can be any desired interval, such as daily or weekly. Furthermore, the protocol can be other than IPv4 TCP, and the data format can be converted from CSV to JSON or XML before transmission.

[0061] The mesh controller (3100) formats the statistical information of the mesh agents (3200) received by the backhaul wireless access point IF (3120) into CSV format and manages it in the mesh agent information management unit (3154).

[0062] Mesh agent 2 (3201) and mesh agent 3 (3202) similarly measure statistical information during communication with wireless terminals connected to their own device, statistical information during communication with mesh controllers (3100) and mesh agents (3200) that communicate with their own device, and radio wave strength with wireless terminals not connected to their own device.

[0063] Mesh agent 2 (3201) and mesh agent 3 (3202) periodically transmit statistical information managed by the fronthaul statistical information management unit (3251) and backhaul statistical information management unit (3252) to the mesh controller (3100) via the backhaul wireless station IF (3230).

[0064] The mesh controller (3100) manages statistical information of mesh agent 2 (3201) and mesh agent 3 (3202) received by the backhaul wireless access point IF (3120) in the mesh agent information management unit (3154).

[0065] In this way, statistical information necessary to determine the power saving status of the mesh network system is collected. The above process corresponds to step (S201) in the flowchart shown in Figure 2.

[0066] Next, we will explain a method for classifying all devices within the mesh network (mesh controller (3100), mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202)) based on statistical information, determining whether to put them into normal mode or power-saving mode. This process corresponds to step (S202) in the flowchart shown in Figure 2.

[0067] First, we will explain the method for determining which devices should be set to normal mode using Figure 5. Figure 5 is a flowchart for determining which devices should be set to normal mode in an embodiment of the present invention.

[0068] The mesh controller (3100) uses statistical information managed by the fronthaul statistical information management unit (3151), backhaul statistical information management unit (3152), and mesh agent information management unit (3154) to determine which mesh controllers (3100) and mesh agents (3200) should be put into power saving mode. The mesh controller (3100) makes this determination for each terminal one by one according to the terminal list shown in Table 2 above, which is managed by the terminal information management unit (3153) (S501).

[0069] First, a determination is made regarding wireless terminal 1 (3300). The mesh controller (3100) sets a threshold for the minimum guaranteed signal strength based on the communication volume of wireless terminal 1 (3300) (S503). At this time, the threshold for the minimum guaranteed signal strength is set higher the more communication volume there is, and lower the less communication volume there is. The mesh controller (3100) checks the signal strength with wireless terminal 1 (3300) from the information managed by the fronthaul statistical information management unit (3151) as shown in Tables 3 and 5 above.

[0070] Furthermore, the mesh controller (3100) checks the signal strength between wireless terminal 1 (3300) and mesh agents (3200), mesh agent 2 (3201), and mesh agent 3 (3202) based on information managed by the mesh agent information management unit (3154) (S504).

[0071] In the network configuration shown in Figure 4, the signal strength to wireless terminal 1 (3300) is above the threshold only for the mesh controller (3100), while the signal strengths to mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202) are below the threshold.

[0072] Since there is only one device whose radio signal strength to wireless terminal 1 (3300) is above the threshold (the branch in (S504) is yes), the mesh controller (3100) determines that the mesh controller (3100) is in normal mode (S505). Subsequently, the mesh controller (3100) determines that wireless terminal 1 (3300) is a classified terminal (S506).

[0073] The mesh controller (3100) makes a determination regarding the next terminal, wireless terminal 2 (3301), according to the terminal list managed by the terminal information management unit (3153) (S508). The mesh controller (3100) sets a threshold for the minimum guaranteed signal strength based on the communication volume of wireless terminal 2 (3301) (S503). The mesh controller (3100) checks the signal strength with wireless terminal 2 (3301) from the information managed by the fronthaul statistical information management unit (3151) as shown in Tables 3 and 5 above.

[0074] Furthermore, the mesh controller (3100) checks the signal strength between wireless terminal 1 (3300) and mesh agents (3200), mesh agent 2 (3201), and mesh agent 3 (3202) based on information managed by the mesh agent information management unit (3154) (S504).

[0075] In the network configuration shown in Figure 4, the signal strength to wireless terminal 2 (3301) is assumed to be above the threshold for mesh agent (3200) and mesh agent 3 (3202), while the signal strength to mesh controller (3100) and mesh agent 2 (3201) is below the threshold.

[0076] Since there are two devices whose radio signal strength to wireless terminal 2 (3301) is above the threshold (resulting in a "no" at the branch in (S504)), the mesh controller (3100) determines that wireless terminal 1 (3300) is an unclassified terminal (S507).

[0077] The mesh controller (3100) makes a determination regarding the next terminal, wireless terminal 3 (3302), according to the terminal list managed by the terminal information management unit (3153) (S508). The mesh controller (3100) sets a threshold for the minimum guaranteed signal strength based on the communication volume of wireless terminal 3 (3302) (S503). The mesh controller (3100) checks the signal strength with wireless terminal 3 (3302) from the information managed by the fronthaul statistical information management unit (3151) as shown in Tables 3 and 5 above.

[0078] Furthermore, the mesh controller (3100) checks the signal strength between wireless terminal 3 (3302) and mesh agent (3200), mesh agent 2 (3201), and mesh agent 3 (3202) based on information managed by the mesh agent information management unit (3154) (S504).

[0079] In the network configuration shown in Figure 4, the signal strength to wireless terminal 3 (3302) is assumed to be above the threshold for mesh agent 2 (3201) and mesh agent 3 (3202), while the signal strength to mesh controller (3100) and mesh agent (3200) is below the threshold.

[0080] Since there are two devices whose radio signal strength to wireless terminal 3 (3302) is above the threshold (resulting in a "no" result at the branch in (S504)), the mesh controller (3100) determines that wireless terminal 1 (3300) is an unclassified terminal (S507).

[0081] The mesh controller (3100) attempts to determine the next terminal according to the terminal list managed by the terminal information management unit (3153) (S508). However, since all terminals in the terminal list have been determined (resulting in a "no" branch in (S502)), the mesh controller (3100) terminates processing.

[0082] After performing the above steps, the terminal detection status will be as shown in Table 6 below, and the device detection status will be as shown in Table 7 below.

[0083] [Table 6]

[0084] [Table 7]

[0085] Next, the mesh controller (3100) classifies all wireless terminals and determines whether all devices should be in normal mode or power-saving mode. This method will be explained using Figure 6. Figure 6 is a flowchart for determining the mode of all devices in an embodiment of the present invention.

[0086] The mesh controller (3100) performs a check on each terminal one by one according to the terminal list shown in Table 2 above, which is managed by the terminal information management unit (3153) (S601).

[0087] First, a determination is made regarding wireless terminal 1 (3300). The mesh controller (3100) checks whether wireless terminal 1 (3300) is an unclassified terminal (S603). Since wireless terminal 1 (3300) is a classified terminal (resulting in "no" at the branch in (S603)), the mesh controller (3100) proceeds to check the next terminal (S607).

[0088] The mesh controller (3100) makes a determination regarding the next terminal, wireless terminal 2 (3301), according to the terminal list managed by the terminal information management unit (3153). The mesh controller (3100) checks whether wireless terminal 2 (3301) is an unclassified terminal (S603). Since wireless terminal 2 (3301) is an unclassified terminal (the branch in (S603) is yes), the mesh controller (3100) checks the determination status of devices whose radio wave strength is above the threshold (S604).

[0089] Since the devices whose radio signal strength to wireless terminal 2 (3301) is above the threshold are mesh agent (3200) and mesh agent 3 (3202), the mesh controller checks whether mesh agent (3200) and mesh agent 3 (3202) are determined to be in normal mode (S604).

[0090] Since neither Mesh Agent (3200) nor Mesh Agent 3 (3202) is determined to be in normal mode, the Mesh Controller (3100) determines that the device with the highest signal strength to Wireless Terminal 2 (3301) is in normal mode.

[0091] In the network configuration shown in Figure 4, if mesh agent 3 (3202) is the device with the highest signal strength to wireless terminal 2 (3301), the mesh controller (3100) determines that mesh agent 3 (3202) is in normal mode (S605).

[0092] The mesh controller (3100) determines that wireless terminal 2 (3301) is a classified terminal (S606), and the mesh controller (3100) checks the next terminal (S607). The mesh controller (3100) makes a determination about the next terminal, wireless terminal 3 (3302), according to the terminal list managed by the terminal information management unit (3153). The mesh controller (3100) checks whether wireless terminal 3 (3302) is an unclassified terminal (S603).

[0093] Since wireless terminal 3 (3302) is an unclassified terminal (the branch in (S603) is yes), the mesh controller (3100) checks the status of devices whose radio wave strength is above the threshold (S604). Since the devices whose radio wave strength to wireless terminal 3 (3302) is above the threshold are mesh agent 2 (3201) and mesh agent 3 (3202), the mesh controller (3100) checks whether mesh agent 2 (3201) and mesh agent 3 (3202) are determined to be in normal mode (S604).

[0094] Since mesh agent 3 (3202) is determined to be in normal mode (resulting in a yes at branch (S604)), the mesh controller (3100) determines that wireless terminal 3 (3302) is a classified terminal (S606), and the mesh controller (3100) proceeds to check for the next terminal (S607).

[0095] The mesh controller (3100) attempts to determine the next terminal according to the terminal list managed by the terminal information management unit (3153), but since it has finished determining all terminals in the terminal list (resulting in a "no" result in branch (S602)), the mesh controller (3100) terminates processing (S608).

[0096] After performing the above steps, the terminal status will be classified as a "classified terminal" for all terminals, and the device mode determination results will be as shown in Table 8 below.

[0097] [Table 8]

[0098] In this way, statistical information is used to classify all devices within the mesh network into either normal mode or power-saving mode. The above process corresponds to step (S202) in the flowchart shown in Figure 2.

[0099] Next, the process of classifying the power saving modes of the mesh network system (S203) will be explained using Figure 7. Figure 7 is a flowchart for classifying the power saving modes in an embodiment of the present invention.

[0100] In this invention, two types of power saving modes are provided: a power saving mode that disables fronthaul communication for communication with wireless terminals and enables only backhaul communication for communication between mesh controllers and mesh agents (hereinafter referred to as the partial power saving mode), and a power saving mode that disables both fronthaul communication for communication with wireless terminals and backhaul communication for communication between mesh controllers and mesh agents (hereinafter referred to as the full power saving mode).

[0101] The mesh controller (3100) first performs a determination process on the mesh controller (3100) (S701). The mesh controller (3100) checks whether the mesh controller (3100) is determined to be in power saving mode (S703). As shown in Table 8 above, the mesh controller (3100) is determined to be in normal mode (resulting in a "no" at the branch in (S703)), so the mesh controller (3100) performs a determination on the next device (S710).

[0102] The mesh controller (3100) performs a determination process on the mesh agent (3200). The mesh controller (3100) checks whether the mesh agent (3200) has been determined to be in power saving mode (S703). As shown in Table 8 above, the mesh agent (3200) has been determined to be in power saving mode (the branch in (S703) is yes), so the mesh controller (3100) checks from the backhaul communication information managed by the mesh agent information management unit (3154) as shown in Table 4 above whether the mesh agent (3200) is relaying communication between the mesh controller (3100) and mesh agent 2 (3201), between the mesh controller (3100) and mesh agent 3 (3202), and between mesh agent 2 (3201) and mesh agent 3 (3202) (S704).

[0103] In the network configuration shown in Figure 4, the mesh agent (3200) relays communication between the mesh controller (3100) and mesh agent 3 (3202) (the branch at (S704) is set to yes), so the mesh controller (3100) identifies the source of the communication that mesh agent (3200) is relaying (S705).

[0104] The mesh controller (3100) sets the minimum guaranteed signal strength of mesh agent 3 (3202) to the mesh agent based on the amount of communication between mesh agent 3 (3202) and mesh agent (3200) (S706). The mesh controller (3100) checks the signal strength between mesh agent 3 (3202) and mesh controller (3100) from the information managed by the backhaul statistical information management unit (3152) as shown in Table 4 above (S707).

[0105] The signal strength between Mesh Agent 3 (3202), Mesh Agent (3200), and Mesh Agent 2 (3201) is checked using information managed by the Mesh Agent Information Management Unit (3154) (S707).

[0106] In the network configuration shown in Figure 4, the signal strength to mesh agent 3 (3202) is assumed to be above the threshold only for mesh agent (3200), while the signal strengths to mesh controller (3100) and mesh agent 2 (3201) are below the threshold.

[0107] Since the only device whose radio signal strength to mesh agent 3 (3202) is above the threshold is mesh agent (3200) (which results in "no" at the branch in (S707)), the mesh controller (3100) determines that mesh agent (3200) is in partial disconnection mode (S709) and makes a determination for the next device (S710).

[0108] The mesh controller (3100) checks whether mesh agent 2 (3201) is determined to be in power saving mode (S703). As shown in Table 8 above, mesh agent 2 (3201) is determined to be in power saving mode (the branch in (S703) is yes), so the mesh controller (3100) checks from the backhaul communication information managed by the mesh agent information management unit (3154) as shown in Table 4 above whether mesh agent 2 (3201) is relaying communication between mesh controller (3100) and mesh agent (3200), mesh controller (3100) and mesh agent 3 (3202), and mesh agent (3200) and mesh agent 3 (3202) (S704).

[0109] In the network configuration shown in Figure 4, Mesh Agent 2 (3201) does not relay any communications (resulting in a "no" at branch (S704)), so the Mesh Controller (3100) does nothing and makes a determination about the next device (S710).

[0110] The mesh controller (3100) checks whether mesh agent 3 (3202) is determined to be in power saving mode (S703). As shown in Table 8 above, mesh agent 3 (3202) is determined to be in normal mode (resulting in a "no" at the branch in (S703)), so the mesh controller (3100) makes a determination about the next device (S710).

[0111] Since there is no next device (resulting in a "no" at branch (S702)), the mesh controller (3100) determines that mesh agent 2 (3201), which is not determined to be in normal mode or partial power saving mode, is in full power saving mode (S711), and terminates processing. By performing these processes, a network as shown in Figure 1 is constructed.

[0112] In this embodiment of the present invention, the power saving mode of the mesh network system is classified in this manner. The above process corresponds to step (S203) in the flowchart shown in Figure 2.

[0113] Next, we will explain the procedure for creating a schedule (S204).

[0114] The mesh controller (3100) performs the processes shown in Figures 5, 6, and 7 for each schedule, and the schedule generation unit (3160) generates the schedule. The schedule may be created on a weekly basis or on a daily basis. Furthermore, the time divisions for each day may be created on an hourly basis or as one schedule for the entire day. For example, if a schedule for one week is generated hourly, something like Figure 8 will be generated.

[0115] The mesh controller (3100) formats the created schedule into CSV format and manages it in the schedule management unit (3155). The mesh controller (3100) also creates this schedule for the mesh agent (3200) and sends the created schedule to the mesh agent (3200) via IPv4 TCP in CSV format through the backhaul wireless access point IF (3120). The mesh agent (3200) receives this schedule at the backhaul wireless station IF (3230) and manages it in CSV format in the schedule management unit (3254).

[0116] The mesh controller (3100) similarly creates schedules for mesh agent 2 (3201) and mesh agent 3 (3202), sends the created schedules, and mesh agent 2 (3201) and mesh agent 3 (3202) manage their schedules using their respective schedule management units.

[0117] Furthermore, the schedules to be managed may be in formats other than CSV, such as JSON or XML. The protocol used to send the schedules may also be other than IPv4 TCP, and the data format may be converted from CSV to JSON or XML before transmission.

[0118] Finally, the procedure (S205) for switching to power-saving mode according to the schedule will be explained. The mesh controller (3100) controls the fronthaul wireless access point IF (3110) and backhaul wireless access point IF (3120) from the control unit (3170) according to the schedule managed by the schedule management unit (3155).

[0119] For example, when switching to full power saving mode, the mesh controller (3100) is controlled by the control unit (3170) to disable the fronthaul wireless access point IF (3110) and the backhaul wireless access point IF (3120). When switching to partial power saving mode, the mesh controller (3100) is controlled by the control unit (3170) to disable the fronthaul wireless access point IF (3110) and enable the backhaul wireless access point IF (3120). When switching to normal mode, the mesh controller (3100) is controlled by the control unit (3170) to enable the fronthaul wireless access point IF (3110) and disable the backhaul wireless access point IF (3120).

[0120] The above describes the operation of the first embodiment of the present invention. In the first embodiment of the present invention, as described above, a mesh network configuration can be constructed that ensures communication speed while achieving maximum power saving effect by using statistical information of the mesh network to determine power saving for the entire network, creating a schedule, and controlling power saving settings.

[0121] As described above, the present invention provides the following effects.

[0122] The first benefit is that it becomes possible to configure power saving settings for multiple access points (APs) without user intervention. The second benefit is that it becomes possible to implement effective power-saving settings and network construction even in multi-stage configurations where wireless client terminals relay signals through multiple access points (APs) for internet communication. The third benefit is that it becomes possible to implement effective power-saving settings and network configurations even when wireless client terminals are connected, or during periods of low communication activity.

[0123] (Other examples) The operation of other embodiments of the present invention will now be described. The basic configuration of the other embodiments of the present invention is the same as that of the first embodiment, but further improvements have been made to accommodate the increase and movement of wireless terminals.

[0124] Figure 9 is a schematic diagram of a network environment used in another embodiment of the present invention. In Figure 9, the operation when wireless terminal 1 (3300) moves from a state where it is connected to mesh controller (3100) to the vicinity of mesh agent 2 (3201) will be described. In this embodiment, in order to be able to receive requests from mesh controller (3100) even in full power saving mode, mesh agent 2 (3201) in full power saving mode will operate with only the reception processing of backhaul wireless station IF (3230) enabled, and the transmission processing of fronthaul wireless access point IF (3210), backhaul wireless access point IF (3220), and backhaul wireless station IF (3230) disabled.

[0125] The operation of other embodiments of the present invention will be described below with reference to Figures 10, 11, and 12. Figure 10 is a flowchart of another embodiment of the present invention. Figure 11 is a sequence of mode determination for each device with respect to wireless terminal 1 in another embodiment of the present invention. Figure 12 is a sequence of mode determination for each device with respect to wireless terminals 2 and 3 in another embodiment of the present invention.

[0126] The mesh controller (3100) monitors the amount of communication and radio wave strength when wireless terminal 1 (3300), which is connected to its own device and is managed by the terminal information management unit (3153) as shown in Table 2 above, communicates via the front-haul wireless access point IF (3110) using the front-haul statistical information monitoring unit (3141) (S1001) (S1101).

[0127] Furthermore, the mesh agent 3 (3202), operating in normal mode, monitors the radio signal strength when the wireless terminal 1 (3300) is communicating with the mesh controller (3100) using the fronthaul wireless access point IF (3210) (S1102).

[0128] The mesh controller (3100) sets a threshold for the minimum guaranteed signal strength based on the amount of communication with the wireless terminal 1 (3300) (S1002) (S1103). At this time, the threshold for the minimum guaranteed signal strength is set higher when the amount of communication is large and lower when the amount of communication is small. The mesh controller (3100) checks the signal strength with the wireless terminal 1 (3300) and determines whether it is above the threshold for the minimum guaranteed signal strength (S1003) (S1104).

[0129] Assume that the radio signal strength between the mesh controller (3100) and the wireless terminal 1 (3300) has fallen below the minimum guaranteed signal strength threshold due to the movement of wireless terminal 1 (3300) (the branch in (S1003) was set to yes). The mesh controller (3100) sends a signal via IPv4 TCP from the backhaul wireless access point IF (3120) to the mesh agent 3 (3202), which is operating in normal mode, requesting the result of the signal strength measurement with wireless terminal 1 (3300) (S1004) (S1105).

[0130] When mesh agent 3 (3202) receives a request signal from mesh controller (3100) received by backhaul wireless station IF (3230), it formats the radio wave strength measurement results previously monitored in (S1102) into CSV format and sends them to mesh controller (3100) via IPv4 TCP from backhaul wireless station IF (3230) (S1106).

[0131] Furthermore, the transmission of request signals from the mesh controller (3100) and the transmission of measurement results from the mesh agent 3 (3202) may be implemented using protocols other than IPv4 TCP, and the data format may be transmitted in formats other than CSV, such as JSON or XML.

[0132] The mesh controller (3100) checks the signal strength of the mesh agent 3 (3202) and wireless terminal 1 (3300) received by the backhaul wireless access point IF (3120), and determines whether the signal strength is equal to or greater than the minimum guaranteed signal strength threshold (S1005) (S1107).

[0133] Assume that mesh agent 3 (3202) is at a distance from wireless terminal 1 (3300), and therefore its signal strength is below the minimum guaranteed signal strength threshold. The mesh controller (3100) determines that there are no devices within the mesh network (3000) whose signal strength to wireless terminal 1 (3300) is above the minimum guaranteed signal strength threshold (this was determined as "yes" at the branch in (S1005)), and therefore sends a Wake up signal to the devices in power-saving mode (S1006). The Wake up signal sent by the mesh controller (3100) is a signal with the Power Management bit in the 802.11 header set to 0, as defined by IEEE (Institute of Electrical and Electronics Engineers) 802.11.

[0134] First, the mesh controller (3100) sends a wake-up signal from the backhaul wireless access point IF (3120) to the mesh agent (3200) which is in partial power saving mode (S1108). When the mesh agent (3200) receives the wake-up signal at the backhaul wireless station IF (3230), the control unit (3260) controls the fronthaul wireless access point IF (3210), which is disabled in partial power saving mode, to enable it in normal mode (S1109).

[0135] Next, the mesh controller (3100) sends a wake-up signal from the backhaul wireless access point IF (3120) to the mesh agent 2 (3201), which is in full power saving mode (S1110). When the mesh agent 2 (3201) receives the wake-up signal at the backhaul wireless station IF (3230), the control unit (3260) controls the fronthaul wireless access point IF (3210), backhaul wireless access point IF (3220), and backhaul wireless station IF (3230), which are disabled in full power saving mode, to enable transmission processing so that they can operate in normal mode (S1111).

[0136] The mesh agent (3200) monitors the signal strength at the fronthaul wireless access point IF (3210) while wireless terminal 1 (3300) is communicating with the mesh controller (3100) because the fronthaul wireless access point IF (3210) has been enabled (S1112).

[0137] Furthermore, since the fronthaul wireless access point IF (3210) has been enabled, Mesh Agent 2 (3201) monitors the signal strength of wireless terminal 1 (3300) while it is communicating with the mesh controller (3100) using the fronthaul wireless access point IF (3210) (S1113). Mesh Agent (3200) formats the measured signal strength of wireless terminal 1 (3300) that it has monitored into CSV format and sends it to the mesh controller (3100) via IPv4 TCP from the backhaul wireless station IF (3230) (S1114).

[0138] Furthermore, Mesh Agent 2 (3201) formats the measured signal strength with the monitored wireless terminal 1 (3300) into CSV format and transmits it to the Mesh Controller (3100) via IPv4 TCP from the backhaul wireless station IF (3230) (S1115). Note that the protocol for the measured signal strength with wireless terminal 1 (3300) transmitted from Mesh Agent (3200) and Mesh Agent 2 (3201) may be implemented using a protocol other than IPv4 TCP, and the data format may be a format other than CSV, such as JSON or XML.

[0139] The mesh controller (3100) receives the radio wave strength measurement results from mesh agent (3200) and mesh agent 2 (3201) at the backhaul wireless access point IF (3120) (S1007). The mesh controller (3100) searches for devices whose radio wave strength to wireless terminal 1 (3300) is equal to or greater than the minimum guaranteed radio wave strength threshold based on the received radio wave strength measurement results (S1008).

[0140] At this time, assume that the signal strength between mesh agent (3200) and wireless terminal 1 (3300) is below the minimum guaranteed signal strength threshold, and the signal strength between mesh agent 2 (3201) and wireless terminal 1 (3300) is above the minimum guaranteed signal strength threshold. The mesh controller (3100) determines that mesh agent 2 (3201), which has the highest signal strength among the devices that sent the Wake up signal and whose signal strength is above the minimum guaranteed signal strength threshold, will operate in normal mode, and that the other mesh agents (3200) will operate in power saving mode (S1009).

[0141] The mesh controller (3100) sends a Sleep signal (S1010) to devices that it has determined are operating in power-saving mode, instructing them to return to power-saving mode. The Sleep signal sent by the mesh controller (3100) is a signal with the Power Management bit in the 802.11 header set to 1, as defined in IEEE 802.11.

[0142] The mesh controller (3100) transmits a Sleep signal from the backhaul wireless access point IF (3120) to the mesh agent (3200) (S1117). When the mesh agent (3200) receives the Sleep signal at the backhaul wireless station IF (3230), the control unit (3260) controls the fronthaul wireless access point IF (3210) to switch it to a disabled state in order to return to the power saving mode before receiving the Wake up signal, i.e., the partial power saving mode. Note that the Wake up signal and Sleep signal transmitted from the mesh controller (3100) may be implemented in a manner other than signals that control the Power Management bit in the 802.11 header as defined in IEEE 802.11.

[0143] Next, the mesh agent 3 (3202) monitors the communication volume and signal strength when wireless terminal 2 (3301), which is connected to its own device and is managed by the terminal information management unit (3253) as shown in Table 2 above, communicates via the fronthaul wireless access point IF (3210) using the fronthaul statistical information monitoring unit (3241) (S1001) (S1201). The mesh controller (3100) formats a signal requesting the communication volume and signal strength with wireless terminal 2 (3301) to the mesh agent 3 (3202) into CSV format and transmits it via IPv4 TCP from the backhaul wireless access point IF (3120) (S1202).

[0144] When mesh agent 3 (3202) receives a signal from backhaul wireless station IF (3230) requesting communication volume and signal strength, it transmits the measured communication volume and signal strength with wireless terminal 2 (3301) from backhaul wireless station IF (3230) to mesh controller (3100) (S1203). Mesh controller (3100) sets the minimum guaranteed signal strength for wireless terminal 2 (3301) based on the communication volume between wireless terminal 2 (3301) and mesh agent 3 (3202) received at backhaul wireless access point IF (3120) (S1002) (S1204).

[0145] The mesh controller (3100) checks the signal strength of wireless terminal 2 (3301) and mesh agent 3 (3202) received by the backhaul wireless access point IF (3120), and verifies whether the signal strength is above the minimum guaranteed signal strength threshold (S1003) (S1205). At this time, since wireless terminal 2 (3201) has not moved, the signal strength with mesh agent 3 (3202) remains above the threshold (resulting in a "no" at the branch in (S1003)). The mesh controller (3100) does not take any action as it did not observe any environmental changes for wireless terminal 2 (3301) and terminates processing.

[0146] Next, the mesh agent 3 (3202) monitors the communication volume and signal strength when wireless terminal 3 (3302), which is connected to its own device and is managed by the terminal information management unit (3253) as shown in Table 2 above, communicates via the fronthaul wireless access point IF (3210) using the fronthaul statistical information monitoring unit (3241) (S1001) (S1201). The mesh controller (3100) formats a signal requesting the communication volume and signal strength with wireless terminal 3 (3302) to the mesh agent 3 (3202) into CSV format and transmits it via IPv4 TCP from the backhaul wireless access point IF (3120) (S1202).

[0147] When mesh agent 3 (3202) receives a signal from backhaul wireless station IF (3230) requesting communication volume and signal strength, it transmits the measured communication volume and signal strength with wireless terminal 3 (3302) from backhaul wireless station IF (3230) to mesh controller (3100) (S1203).

[0148] The mesh controller (3100) sets the minimum guaranteed signal strength for wireless terminal 3 (3302) based on the amount of communication between wireless terminal 3 (3302) and mesh agent 3 (3202) received by the backhaul wireless access point IF (3120) (S1002) (S1204).

[0149] The mesh controller (3100) checks the signal strength of wireless terminal 3 (3302) and mesh agent 3 (3202) received by the backhaul wireless access point IF (3120), and verifies whether the signal strength is above the minimum guaranteed signal strength threshold (S1003) (S1205). At this time, since wireless terminal 2 (3201) has not moved, the signal strength with mesh agent 3 (3202) remains above the threshold (resulting in a "no" at the branch in (S1003)). The mesh controller (3100) does not take any action as it did not observe any environmental changes for wireless terminal 3 (3302) and terminates processing.

[0150] Thus, in this embodiment, even when a wireless terminal moves, the system uses information on communication volume and signal strength to change only the devices that should operate in normal mode among those in power-saving mode to normal mode, while the other devices maintain power-saving mode. This allows for the reconstruction of a network configuration that maximizes power saving while ensuring communication speed. In this configuration, the process of reconstructing the network configuration described above may be performed continuously or periodically, such as daily or weekly.

[0151] The following embodiments are possible in the present invention, as noted below, but are not limited thereto. (Note 1) As stated in the first perspective. (Note 2) The mesh network system as described in Appendix 1, wherein the mesh controller determines whether the mesh controller and the mesh agent are in a full power saving mode or a partial power saving mode using statistical information on the amount of communication and signal strength of the wireless communication. (Note 3) The mesh network system as described in Appendix 1, wherein the mesh controller and the mesh agent collect communication volume and radio wave strength, including wireless communications in the mesh network that are not connected to their own devices. (Note 4) The mesh network system according to any one of the appendices 1 to 3, wherein the mesh controller classifies the power saving mode at regular intervals, creates a schedule, and the mesh controller and mesh agents switch to the power saving mode according to the schedule. (Note 5) As stated in the second perspective. (Note 6) The mesh network operation method described in Appendix 5, wherein the mesh controller determines whether the mesh controller and the mesh agent are in a full power saving mode or a partial power saving mode using statistical information on the amount of communication and radio wave intensity of the wireless communication. (Note 7) The mesh network operation method according to Appendix 5 or 6, wherein the mesh controller and the mesh agent collect communication volume and radio wave strength, including wireless communications in the mesh network that are not connected to their own devices. (Note 8) The mesh network operation method described in any of Appendix 5 to 7, wherein the mesh controller classifies the power saving modes at regular intervals, creates a schedule, and the mesh controller and mesh agents switch to power saving mode according to the schedule.

[0152] Furthermore, the disclosures of the above-mentioned patent documents and other materials cited are incorporated into this document by reference. Within the framework of the full disclosure of the present invention (including the claims), further modifications and adjustments to the embodiments or examples are possible based on the fundamental technical concept. Also, within the framework of the full disclosure of the present invention, various combinations or selections (including partial deletions) of various disclosure elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes the full disclosure, including the claims, and various modifications and alterations that a person skilled in the art could make in accordance with the technical concept. In particular, with respect to the numerical ranges described in this document, any numerical value or sub-range included within that range should be interpreted as being specifically described, even if not otherwise stated. Furthermore, the disclosures of the above-mentioned cited documents may, if necessary, be used in part or in whole as part of the disclosure of the present invention, in accordance with the spirit of the present invention, and these may also be considered to be included in the disclosures of this application. [Explanation of symbols]

[0153] 3100 Mesh Controller 3200 Mesh Agents 3201 Mesh Agent 2 3202 Mesh Agent 3 3300 Wireless Terminal 1 3301 Wireless Terminal 2 3302 Wireless terminal 3 3000 Mesh Network 3110 Front Haul Wireless Access Point Interface 3120 Backhaul Wireless Access Point IF 3130 WAN IF 3140 Monitoring Department 3141 Front Hall Statistics Monitoring Department 3142 Backhaul Statistics Monitoring Department 3150 Management Department 3151 Front Hall Statistics and Information Management Department 3152 Backhaul Statistics Management Department 3153 Terminal Information Management Department 3154 Mesh Agent Information Management Department 3155 Schedule Management Department 3160 Schedule Generation Unit 3170 Control Unit 3210 Front Haul Wireless Access Point Interface 3220 Backhaul Wireless Access Point IF 3230 Backhaul Wireless Station IF 3240 Monitoring Department 3241 Front Hall Statistics Monitoring Department 3242 Backhaul Statistics Monitoring Department 3250 Management Department 3251 Front Hall Statistics Management Department 3252 Backhaul Statistics Management Department 3253 Terminal Information Management Department 3254 Schedule Management Department 3260 Control Unit

Claims

1. A mesh network system in which a mesh controller and mesh agents relay wireless communication, The mesh controller and the mesh agent collect the communication volume and signal strength of wireless communication in the mesh network. The mesh agent transmits statistical information on the amount of wireless communication and radio wave strength to the mesh controller. The mesh network system includes a mesh controller that uses statistical information on the amount of wireless communication and radio wave intensity to determine whether or not to enable power saving mode for the mesh controller and the mesh agent.

2. The mesh network system according to claim 1, wherein the mesh controller determines whether the mesh controller and the mesh agent are in a full power saving mode or a partial power saving mode using statistical information on the amount of communication and radio wave intensity of the wireless communication.

3. The mesh network system according to claim 1, wherein the mesh controller and the mesh agent collect communication volume and radio wave intensity, including wireless communications in the mesh network that are not connected to their own devices.

4. The mesh network system according to claims 1 and 2, wherein the mesh controller classifies the power saving modes at regular intervals, creates a schedule, and the mesh controller and mesh agents switch to power saving mode according to the schedule.

5. A mesh network operation method in which a mesh controller and mesh agents relay wireless communication, The mesh controller and the mesh agent collect the communication volume and signal strength of wireless communication in the mesh network. The mesh agent transmits statistical information on the amount of wireless communication and radio wave strength to the mesh controller. A mesh network operation method comprising the mesh controller determining whether or not to enable power saving mode for the mesh controller and the mesh agent using statistical information on the amount of communication and signal strength of the wireless communication.

6. The mesh network operation method according to claim 5, wherein the mesh controller determines whether the mesh controller and the mesh agent are in a full power saving mode or a partial power saving mode using statistical information on the amount of communication and radio wave intensity of the wireless communication.

7. The mesh network operation method according to claim 5, wherein the mesh controller and the mesh agent collect communication volume and radio wave strength, including wireless communications in the mesh network that are not connected to their own devices.

8. The mesh network operation method according to claims 5 and 6, wherein the mesh controller classifies the power saving modes at regular intervals, creates a schedule, and the mesh controller and mesh agents switch to power saving mode according to the schedule.

Images