Communication device, control method, and program

Abstract

To make it possible to automatically select an appropriate controller that controls a network from devices belonging to the network.SOLUTION: A communication device determines, on the basis of whether it can connect a public network without passing through another device included in a network that is constructed including the communication device and interconnects base stations that provide terminals with communication services, whether to operate as a role of a controller that controls the network or operate as a role of an agent managed by another device operating as the controller, and operates according to the determined role.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present invention relates to an automatic network setting technique. [Background technology]

[0002] The Wi-Fi (registered trademark) Alliance has established the Wi-Fi EasyMesh standard. In Wi-Fi EasyMesh, in a network consisting of multiple access points (APs), various information of the APs is acquired, and efficient network control between the multiple APs is performed based on the information. In Wi-Fi EasyMesh, each AP functions as a controller device that controls other APs to manage the entire network, or an agent device that is under the management of the controller device and notifies the controller device of network information. The controller device collects topology information and discovery information from the agent device, and controls the network by sending instructions to the agent device based on the information. In addition, the controller device performs proxy control of data communication and management of data traffic between the network controlled by the controller device and a public network (or at least a network outside the network controlled by the controller device). Patent Document 1 describes a method in which the controller device uses IEEE1905.1 to perform steering according to the wireless strength for a station (STA) to be connected to the AP. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] US Patent Application Publication No. 2018 / 0176284 Summary of the Invention [Problem to be solved by the invention]

[0004] It is assumed that a user selects a controller device from among multiple devices in a Wi-Fi EasyMesh network. However, in this case, due to the user's lack of knowledge about networks, it is possible that a device suitable for the controller device is not selected, and another device is selected as the controller. In such a case, it may become impossible to use a communication function that should be available.

[0005] According to one aspect of the present invention, it is an object of the present invention to provide a technique for transmitting data including at least network information that can be used to reconstruct a network established by a communication device functioning as a controller of Wi-Fi EasyMesh (registered trademark) to another communication device. According to another aspect of the present invention, it is an object of the present invention to provide a mechanism for transferring authority as a controller of Wi-Fi EasyMesh to a device other than itself. [Means for solving the problem]

[0006] A communication device according to one embodiment of the present invention has a management means for causing the communication device to function as a Wi-Fi EasyMesh (registered trademark) controller and managing a mesh network, and a transmission means for transmitting to another communication device, when a predetermined condition is satisfied, data including at least network information that can be used to reconstruct the network constructed by the communication device functioning as the controller. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to transmit data including at least network information that can be used to reconstruct a network constructed by a communication device functioning as a controller of Wi-Fi EasyMesh (registered trademark) to another communication device. According to one aspect of the present invention, it is possible to transfer authority as a controller of Wi-Fi EasyMesh to a device other than itself. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a first example of a configuration of a communication system. [Diagram 2] 1 is a block diagram showing an example of the configuration and external appearance of a digital camera; [Diagram 3] FIG. 2 is a block diagram showing a configuration example of a smart device. [Figure 4A] FIG. 11 is a diagram showing an example of the flow of processes executed by a digital camera and a smart device. [Figure 4B] FIG. 11 is a diagram showing an example of the flow of processes executed by a digital camera and a smart device. [Diagram 5] FIG. 11 is a sequence diagram showing a first example of a processing flow. [Figure 6] FIG. 11 is a diagram showing an example of the flow of processes executed by a digital camera and a smart device. [Figure 7] FIG. 11 is a diagram illustrating a second example of the configuration of a communication system. [Figure 8] FIG. 11 is a sequence diagram showing a second example of the processing flow. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the technical scope of the present invention is not limited to the individual embodiments described below, and the embodiments described below can be modified or changed without departing from the gist of the present invention.

[0010] (System Configuration) FIG. 1 shows an example of the configuration of a wireless communication system according to this embodiment. As an example, the wireless communication system includes a camera 101 and a smart device 102. The camera 101 and the smart device 102 are communication devices capable of transmitting and receiving signals to each other by wireless communication. The smart device 102 is connected to a public network 103. In this embodiment, the camera 101 and the smart device 102 construct a Wi-Fi EasyMesh network. The Wi-Fi EasyMesh network is an example, and the following discussion can be applied to any network that connects base stations (access points) that provide communication services to terminals. In addition, the public network in this embodiment includes a wide-area external network such as the Internet or a WAN (Wide Area Network), and includes any network outside the Wi-Fi EasyMesh network.

[0011] (Configuration of camera 101) Next, the configurations of the camera 101 and the smart device 102 will be described. FIG. 2A shows an example of the configuration of the camera 101. The camera 101 may be an imaging device such as a digital camera, but may also be any device having an imaging function such as a portable media player, a tablet computer, or a personal computer, or any information processing device other than an imaging device. In one example, the camera 101 has a control unit 201, an imaging unit 202, a non-volatile memory 203, a working memory 204, an operation unit 205, a display unit 206, a recording medium 207, a wireless communication unit 208, and a wired communication unit 209. Note that these functional units are examples, and the camera 101 may be replaced with a device of any configuration as long as it can execute various processes described below.

[0012] The control unit 201 includes, for example, one or more general-purpose processors such as a central processing unit (CPU) or a micro processing unit (MPU), or a processor such as an application specific integrated circuit (ASIC). The control unit 201 may include a gate array circuit such as a field programmable gate array (FPGA) configured to execute a predetermined process. The control unit 201 controls the entire camera 101 according to input signals and programs described below, and executes each process in a flowchart described below. Instead of the control unit 201 controlling the entire device, the entire camera 101 may be controlled by multiple hardware devices sharing the process.

[0013] The imaging unit 202 includes, for example, an optical lens unit, an optical system for controlling the aperture, zoom, focus, and the like, and an imaging element for converting light (image) introduced through the optical lens unit into an electrical image signal. Here, the imaging unit 202 may use, for example, a complementary metal oxide semiconductor (CMOS) or a charge coupled device (CCD) as the imaging element. Based on the control of the control unit 201, the imaging unit 202 converts the subject light focused by the lens into an electrical signal using the imaging element, performs noise reduction processing, and outputs digital data as image data. The camera 101 records the image data in the recording medium 207 according to, for example, the DCF (Design Rule for Camera File system) standard.

[0014] The non-volatile memory 203 is an electrically erasable and recordable non-volatile memory, and stores programs (described later) executed by the control unit 201. The working memory 204 is used as a buffer memory for temporarily storing image data captured by the imaging unit 202, an image display memory for the display unit 206, a working area for the control unit 201, etc.

[0015] The operation unit 205 is used to receive instructions from the user to the camera 101. The operation unit 205 includes, for example, a power button for the user to instruct the camera 101 to be turned on / off, a release switch for instructing shooting, and a playback button for instructing playback of image data. The operation unit 205 may further include operation members such as a dedicated connection button for starting communication with an external device via the wireless communication unit 208 described below. The operation unit 205 may also include a touch panel formed on the display unit 206 described below.

[0016] The display unit 206 displays a viewfinder image during shooting, displays captured image data, and displays characters for interactive operations. The display unit 206 also displays code information such as barcodes, two-dimensional codes, and QR codes (registered trademark). The camera 101 can be connected to an internal or external display device, and in addition to or instead of the display unit 206, the camera 101 may have a display control function for controlling the display on the display device.

[0017] Here, examples of operation unit 205 and display unit 206 will be described using examples of the external configuration of camera 101 in Figures 2(B) and 2(C). Operation unit 205 includes operation members such as release switch 205a, playback button 205b, directional keys 205c, touch panel 205d, and power switch 205e. Here, touch panel 205d also serves as display unit 206. Note that display unit 206 does not have to be a touch panel, in which case display unit 206 and operation unit 205 are physically separated.

[0018] Recording medium 207 is, for example, any device capable of recording information, and can record image data output from imaging unit 202. Recording medium 207 may be a medium such as a memory card that is detachable from camera 101, or may be a memory or the like built into camera 101. Camera 101 has at least a function of accessing recording medium 207.

[0019] The wireless communication unit 208 is a wireless communication interface for connecting to an external device. The camera 101 can directly transmit and receive data to and from an external device having a similar wireless communication interface via the wireless communication unit 208. The camera 101 can also connect to a relay device (e.g., an external AP) via the wireless communication unit 208 and communicate with a communication partner device via the relay device. The wireless communication unit 208 can communicate in, for example, either an AP (access point) mode or a STA (station) mode. When operating in the AP mode, the wireless communication unit 208 connects to another device operating as a STA, and when operating in the STA mode, it connects to another device operating as an AP. In this embodiment, the wireless communication unit 208 includes an interface for communicating with an external device via a wireless LAN compliant with the IEEE802.11 series of standards. The camera 101 can perform wireless communication with an external device by, for example, the control unit 201 controlling the wireless communication unit 208. Furthermore, the camera 101 executes a communication parameter sharing process for sharing wireless communication parameters to be set in the wireless communication unit 208 with an external device, for example, by the control unit 201 controlling the wireless communication unit 208. In the communication parameter sharing process, a communication parameter providing device provides communication parameters for wireless communication to a communication parameter receiving device. Here, the communication parameters include wireless communication parameters necessary for wireless LAN communication, such as a Service Set Identifier (SSID) as a network identifier, an encryption method, an encryption key, an authentication method, and an authentication key. The communication parameters may also include a MAC address, a passphrase, an IP address for communication at the IP layer, and information necessary for higher-level services. The communication parameter sharing process may be performed by a method conforming to the Wi-Fi Protected Setup standard (hereinafter referred to as WPS) specified by the Wi-Fi Alliance, or may be performed by a method conforming to the Device Provisioning Protocol standard (hereinafter referred to as DPP). Note that the wireless communication unit 208 performs communication by wireless LAN in this embodiment, but may perform communication by a wireless communication method / system other than wireless LAN.

[0020] The wired communication unit 209 is a wired communication interface for connecting to an external device. The camera 101 can directly transmit and receive data to and from an external device having a similar wired communication interface via the wired communication unit 209. The camera 101 can also connect to a relay device (e.g., an external router) via the wired communication unit 209 and communicate with a communication partner device via the relay device. In this embodiment, the wired communication unit 209 includes an interface for communicating with an external device via a wired LAN (Ethernet (registered trademark)) conforming to the IEEE802.3 standard. For example, the control unit 201 controls the wired communication unit 209, whereby the camera 101 can perform wired communication with the external device. The wired communication unit 209 may perform communication according to a standard other than Ethernet.

[0021] In the camera 101 of this embodiment, the control unit 201 handles the wireless communication of the wireless communication unit 208 conforming to the IEEE802.11 standard and the wired communication of the wired communication unit 209 conforming to the IEEE802.3 standard in an integrated manner in accordance with the IEEE1905.1 standard. In the camera 101 of this embodiment, the control unit 201 controls the wireless communication unit 208 to operate in the role of an EasyMesh controller device or agent device, and performs control according to the role. IEEE1905.1 is a protocol that is higher in the OSI reference model (7 layers) than the PHY / MAC layer, and is an abstraction layer for communication between the agent and the controller, regardless of whether the access points are connected to each other via a wireless LAN or a wired LAN.

[0022] (Smart Device Configuration) 3 shows a configuration example of the smart device 102. The smart device 102 is a smartphone as an example, but may be any information processing device with a wireless function other than a smartphone, such as a mobile phone, a personal computer, a tablet, a smart watch, or a camera. In one example, the smart device 102 has a control unit 301, an imaging unit 302, a non-volatile memory 303, a working memory 304, an operation unit 305, a display unit 306, a recording medium 307, a wireless communication unit 308, and a wired communication unit 309. The smart device 102 further has a public network communication unit 310, a speaker 311, and a microphone 312.

[0023] The control unit 301 includes, for example, one or more general-purpose processors such as a CPU or MPU, an application processor, an ASIC (Application Specific Integrated Circuit), or other processors. The control unit 301 may include a gate array circuit such as an FPGA configured to execute a predetermined process. The control unit 301 controls the entire smart device 102 according to input signals and programs described below, and executes each process in the flowchart described below. Instead of the control unit 301 controlling the entire device, the entire smart device 102 may be controlled by multiple hardware devices sharing the process.

[0024] The imaging unit 302 includes, for example, an optical lens unit, an optical system, and an imaging element. The imaging unit 302 has the same functions as the imaging unit 202 of the camera 101. Image data obtained by imaging is stored, for example, in a buffer memory (for example, a working memory 304), and the result of a predetermined calculation performed by the control unit 301 on the image data is recorded on the recording medium 307.

[0025] The non-volatile memory 303 is a non-volatile memory that can be electrically erased and recorded. In the non-volatile memory 303, an OS (operating system) that is basic software executed by the control unit 301 and applications that cooperate with the OS to realize applied functions are recorded. An OS is installed in the smart device 102, and the OS can execute applications installed in the smart device 102. In this embodiment, the non-volatile memory 303 also stores application software for communicating with the camera 101. The working memory 304 is used as a buffer memory that temporarily holds image data captured by the imaging unit 302, an image display memory for the display unit 306, a working area for the control unit 301, and the like.

[0026] The operation unit 305 is used to receive instructions from the user for the smart device 102. The operation unit 305 includes, for example, an operation member such as a power button for the user to instruct ON / OFF of the power of the smart device 102 and a touch panel formed on the display unit 306. The display unit 306 displays image data and characters for interactive operation. The display unit 306 can also display code information such as two-dimensional codes such as barcodes and QR codes (registered trademark). The smart device 102 can be connected to an internal or external display device, and may have a display control function for controlling the display on the display device in addition to or instead of the display unit 306.

[0027] The recording medium 307 is, for example, any device capable of recording information, and can record image data output from the imaging unit 302. The recording medium 307 may be a medium such as a memory card that is detachable from the smart device 102, or may be a memory built into the smart device 102. The smart device 102 has at least a function of accessing the recording medium 307.

[0028] The wireless communication unit 308 is a wireless communication interface for connecting to an external device. The camera 101 can directly transmit and receive data to and from an external device having a similar wireless communication interface via the wireless communication unit 308. The smart device 102 can also connect to a relay device (e.g., an external AP) via the wireless communication unit 308 and communicate with a communication partner device via the relay device. The wireless communication unit 308 can communicate in, for example, either an AP (access point) mode or a STA (station) mode. In this embodiment, the wireless communication unit 308 includes an interface for communicating with an external device via a wireless LAN conforming to the IEEE802.11 standard series. The smart device 102 can perform wireless communication with an external device by, for example, the control unit 301 controlling the wireless communication unit 308. In addition, the smart device 102 executes the above-mentioned communication parameter sharing process for sharing wireless communication parameters to be set in the wireless communication unit 308 with the external device by, for example, the control unit 301 controlling the wireless communication unit 308. The communication parameter sharing process may be performed by the WPS method defined by the Wi-Fi Alliance, or may be performed by the DPP method. Note that, although the wireless communication unit 308 performs communication by wireless LAN in this embodiment, it may perform communication by a wireless communication method / system other than wireless LAN.

[0029] The wired communication unit 309 is a wired communication interface for connecting to an external device. The smart device 102 can directly transmit and receive data to and from an external device having a similar wired communication interface via the wired communication unit 309. The smart device 102 can also connect to a relay device (e.g., an external router) via the wired communication unit 309 and communicate with a communication partner device via the relay device. In this embodiment, the wired communication unit 309 includes an interface for communicating with an external device via a wired LAN (Ethernet (registered trademark)) conforming to the IEEE802.3 standard. The smart device 102 can perform wired communication with an external device by, for example, the control unit 301 controlling the wired communication unit 309. The wired communication unit 309 may perform communication according to a standard other than Ethernet.

[0030] In the smart device 102 of this embodiment, the control unit 301 handles wireless communication conforming to the IEEE 802.11 standard by the wireless communication unit 308 and wired communication conforming to the IEEE 802.3 standard by the wired communication unit 309 in an integrated manner in accordance with the IEEE 1905.1 standard. In the smart device 102 of this embodiment, the control unit 301 controls the wireless communication unit 308 to operate in the role of an EasyMesh controller device or agent device, and performs control according to the role.

[0031] The public network communication unit 310 is a wireless communication interface used when performing public wireless communication (for example, wireless communication in a cellular system). The smart device 102 can connect to a base station device having a corresponding wireless communication interface via the public network communication unit 310 and can make a call / communicate with other devices via the base station device. At this time, the control unit 301 inputs and outputs audio signals via the microphone 311 and the speaker 312, thereby making a call using the smart device 102. In this embodiment, the public network communication unit 310 includes an antenna, and the control unit 301 can connect to a public network via the antenna. In addition, the control unit 301 can relay communication of other communication devices connected via the wireless communication unit 308 or the wired communication unit 309 using the public network communication unit 310. This allows the other communication devices to connect to the public network via the smart device 102. In this embodiment, the public network communication unit 310 communicates in accordance with the LTE-Advanced standard defined by the Third Generation Partnership Project (3GPP (registered trademark)), but may connect to a public network in accordance with a standard other than LTE-Advanced. In addition, the public network communication unit 310 may be, for example, a functional unit that connects to a second network different from a local first network to which the camera 101 and the smart device 102 are connected. In other words, the smart device 102 does not necessarily have to be able to connect to a public network.

[0032] (Processing flow) Next, an example of the flow of processing executed by the camera 101 and smart device 102 according to this embodiment will be described with reference to Figures 4A and 4B. The processing of Figures 4A and 4B is performed by the control unit 201 (control unit 301) reading and executing a computer program stored in the non-volatile memory 203 (non-volatile memory 303). Note that a part or all of the processing of Figures 4A and 4B may be realized by hardware such as an ASIC. Note that, hereinafter, when there is no need to distinguish between the camera 101 and the smart device 102, they will be called "apparatus."

[0033] First, the device starts up in response to receiving a user operation to turn on the device (S401). If the device is powered on, the process of S401 may be omitted. Then, the device determines whether or not an automatic selection function of the controller device and the agent device has been started by, for example, a user operation (S402). This automatic selection function may be started remotely from another device, and does not necessarily have to be started by a user operation. If the device determines that the automatic selection function has been started (YES in S402), the device transitions the process to S403. In S403, the device determines whether or not the device itself can be directly connected to a public network using a wireless communication unit, a wired communication unit, or a public network communication unit. This determination is made, for example, based on whether or not the public network communication unit of the device is within the service area of ​​a cellular communication service, whether or not the wireless communication unit is in a state where it can be connected to a public wireless LAN, whether or not the wired communication unit is in a state where it is connected to a public network, and the like. Also, for example, when the device has a communication unit that can connect to a public network but the function is turned off (for example, the public network communication unit is set to flight mode), the device may determine that it cannot directly connect to the public network. Note that "directly" in this determination may be interpreted as not going through other devices participating in the Wi-Fi EasyMesh network. That is, when the device can connect to the public network not going through other devices participating in the same Wi-Fi EasyMesh network as the device itself, but through other devices that do not participate in the Wi-Fi EasyMesh network, the device may determine that it can directly connect to the public network. When the device determines that it can directly connect to the public network (YES in S403), it activates the controller function (S404). That is, when the device according to this embodiment can directly connect to the public network, it operates as a controller device of Wi-Fi EasyMesh. The processes from S404 to S414 described below are examples of the process flow when the device operates as a controller device.

[0034] When the device starts to operate as a controller device, the device displays a predetermined message on the display unit to prompt the user to start the opposing device (S405). If the device detects an opposing device that has already been started, the predetermined message may not be displayed. The device may also display a screen indicating that the device is operating as a controller device and is in a state of being connected to the agent device. The information display is not limited to a visual display, and may include information presentation by sound, vibration, or the like. Next, the device determines whether or not the wired communication of the device itself is enabled (S406), and if it is determined that the wired communication is enabled (YES in S406), it starts a search process for the opposing device defined by the IEEE1905.1 standard using the wired communication unit (S407). On the other hand, if the device does not determine that the wired communication is enabled (NO in S406), it does not execute a search process for the opposing device according to the IEEE1905.1 standard. After that, the device determines whether or not the wireless communication of the device itself is enabled (S408). When the device determines that the wireless communication of the device itself is valid (YES in S408), it activates the AP mode of the wireless communication unit and constructs a Wi-Fi EasyMesh network of the fronthaul SSID. When the device constructs the network, it starts a communication parameter sharing process. In this case, since the device has started operating as a controller device in S404, it operates as a providing device in the communication parameter sharing process. That is, the device operates as a registrar in WPS and as a configurator in DPP. The device starts a WPS standby process and a search process for a counterpart device by DPP using the wireless communication unit (S409). For example, the device performs a search process by waiting to receive a WPS Probe Request and transmitting an Action Frame by DPP. Note that when the device determines that the wireless communication of the device itself is invalid (NO in S408), it does not execute the process of S409.

[0035] Thereafter, the device searches for the opposite device using the wireless communication unit or the wired communication unit, and determines whether the opposite device has been detected (S410). If the opposite device has been detected (YES in S410), the device transitions the process to S411, and if the opposite device has not been detected (NO in S410), the device transitions the process to S414.

[0036] In S411, the device performs a communication parameter sharing process with the opposite device. After performing the communication parameter sharing process with the opposite device, the device determines whether the opposite device is an agent device (S412). When the device determines that the opposite device is an agent device (YES in S412), the device connects to the opposite device (S413). When the wireless function of the device is enabled, the opposite device wirelessly connects to the network of the fronthaul SSID established in S409 using the wireless communication unit as a backhaul STA using the parameters received in the communication parameter sharing process. That is, in this case, the device operates as an AP and the opposite device operates as an STA, and they both perform AP-to-AP communication. That is, the device operates as an AP for both AP-to-AP communication of the mesh network in the Wi-Fi EasyMesh network and for STAs connecting to the Wi-Fi EasyMesh network. On the other hand, the opposite device operates as an STA in AP-to-AP communication of the mesh network in the Wi-Fi EasyMesh network, and operates as an AP for STAs connecting to the Wi-Fi EasyMesh network. Thereafter, the process defined in the IEEE 1905.1 standard is executed between the device and the opposing device to share communication parameters of the upper layer. If the wired function is enabled, the device skips the wireless connection process and executes the process defined in the IEEE 1905.1 standard to share communication parameters of the upper layer using the wired communication unit. As a result, the device and the opposing device are connected not only in the lower layer but also in the upper layer.

[0037] When the device determines that the opposing device is not an agent device (NO in S412), the device transitions the processing to Fig. 6. The processing in Fig. 6 will be described later.

[0038] In S414, the device determines whether or not a timeout has occurred in the automatic selection function. If a timeout has occurred in the automatic selection function (YES in S414), the device executes error processing (S415). In the error processing, the device notifies the user of the occurrence of the error via the display unit, for example, and stops the automatic selection function. Other error processing may also be performed. For example, the device may display a message on the display unit inquiring of the user whether or not to continue the automatic selection function. If a timeout has not occurred in the automatic selection function (NO in S414), the device returns the processing to S406.

[0039] When the device determines that it cannot directly connect to the public network (NO in S403), it activates the agent function (S416). That is, in this embodiment, the device that cannot directly connect to the public network operates as a Wi-Fi EasyMesh agent device. The process from S416 to S429 described below is an example of the process flow when the device becomes an agent device.

[0040] When the device starts to operate as an agent device, it displays a predetermined message on the display unit to prompt the user to start the opposing device (S417). If the device detects an opposing device that has already been started, it may not display this predetermined message. The device may also display a screen indicating that the device is operating as an agent device and is in a state of being connected to the controller device. The information display is not limited to a visual display, and may include information presentation by sound, vibration, or the like. Next, the device determines whether or not the wired communication of the device itself is enabled (S418), and if it is determined that the wired communication is enabled (YES in S418), it starts a search process for the opposing device defined by the IEEE1905.1 standard using the wired communication unit (S419). On the other hand, if the device does not determine that the wired communication is enabled (NO in S418), it does not execute the search process for the opposing device defined by the IEEE1905.1 standard. After that, the device determines whether or not the wireless communication of the device itself is enabled (S420). When the device determines that the wireless communication of the device itself is valid (YES in S420), it activates the STA mode of the wireless communication unit, and starts the WPS search process for the opposing device and the DPP standby process (S421). When the device starts the Wi-Fi EasyMesh network search process, it starts the communication parameter sharing process. Here, since the device is operating as an agent device in S416, it operates as a receiving device in the communication parameter sharing process. In other words, the device operates as an Enrollee in WPS and DPP. The device uses the wireless communication unit to perform the WPS search process and the DPP standby process for the opposing device. For example, the device performs the WPS Probe Request transmission process and the DPP Action Frame reception process. Note that when the device determines that the wireless communication of the device itself is invalid (NO in S420), it does not perform the process of S421.

[0041] Thereafter, the device searches for the opposite device using the wireless communication unit or the wired communication unit, and determines whether the opposite device has been detected (S422). If the opposite device has been detected (YES in S422), the device transitions the process to S423, and if the opposite device has not been detected (NO in S422), the device transitions the process to S426.

[0042] In S423, the device performs a communication parameter sharing process with the opposite device by wired communication or wireless communication. Then, after performing the communication parameter sharing process with the opposite device, the device judges whether the opposite device is a controller device (S424). When the device judges that the opposite device is a controller device (YES in S424), it connects to the opposite device (S425). When the wireless function is enabled, the device performs a wireless connection as a backhaul STA to the network of the fronthaul SSID that the opposite device has built by the wireless communication unit, using the parameters received in the communication parameter sharing process. Then, in order to share communication parameters of the upper layer between the device and the opposite device, a process specified in IEEE1905.1 is executed. When the wired connection is enabled, the device skips the wireless connection process and uses the wired communication unit to execute a process specified in IEEE1905.1 for sharing communication parameters of the upper layer. As a result, the device and the opposite device are connected not only to the lower layer but also to the upper layer.

[0043] On the other hand, if the device determines that the other device is not a controller device (NO in S424), it determines whether or not a controller device exists in the Wi-Fi EasyMesh network (S427). That is, the device determines whether or not a controller device exists beyond the other device, which is an agent device. If a controller device exists in the Wi-Fi EasyMesh network (YES in S427), the device transitions the process to S425 and performs a connection process with the other device. The device may perform a connection process with a controller device in the Wi-Fi EasyMesh network. On the other hand, if a controller device does not exist (NO in S427), the device performs an error process (S428). The error process may be, for example, the same process as S415 described above. In addition, in the error process, a message that prompts the user to specify a controller device may be displayed. The device may end the process after performing the error process in S428, or may stop the agent function and start operating as a controller device (S429).

[0044] In S426, the device determines whether or not a timeout has occurred in the automatic selection function. If a timeout has occurred in the automatic selection function (YES in S426), the device executes error processing (S428). If a timeout has not occurred in the automatic selection function (NO in S428), the device returns the process to S418.

[0045] Returning to S402, if the device determines that the automatic selection function is not activated (NO in S402), the device transitions the process to S430. In this case, the device transitions to a state in which the user can manually configure a Wi-Fi EasyMesh network without using the automatic selection function. S430 to S439 described below show an example of the process in this state.

[0046] In S430, the device waits for a Wi-Fi EasyMesh mode setting to be input by a user operation. Here, the mode setting is a setting of a mode indicating whether the device operates as a controller device or an agent device. When the device detects that the mode setting by the user operation has not been completed (NO in S431), it determines whether or not the period for accepting the user operation for the mode setting has expired (S437). When the period expires without accepting the user operation for the mode setting and the device detects a timeout (YES in S437), it executes error processing (S415). On the other hand, when the device does not detect a timeout for the user operation for the mode setting (NO in S437), it returns the processing to S431. When the device detects that the mode setting by the user operation has been completed (YES in S431), it starts the operation mode as a controller device or an agent device based on the setting (S432). Then, the device displays a predetermined message on the display unit to prompt the user to start the opposing device (S433). Then, the device determines whether or not a command to connect to the other device has been issued by a user operation (S434).

[0047] When the user instructs the device to connect to the other device (YES in S434), the device executes a communication parameter sharing process with the other device based on the user instruction (S435). After executing the communication parameter sharing process, the device determines whether the connection with the other device was successful (S436). When the connection with the other device has failed (NO in S436), the device executes an error process (S415).

[0048] If there is no instruction to connect to the opposite device by user operation (NO in S434), the device judges whether or not the period for accepting user operation related to an instruction to connect to the opposite device has expired (S438). If the period expires without accepting user operation related to an instruction to connect to the opposite device and the device detects a timeout (YES in S438), the device executes error processing (S415). Note that the above-mentioned error processing is as described above, and therefore a description thereof will be omitted here. On the other hand, if the device has not detected a timeout related to the user operation related to an instruction to connect to the opposite device (NO in S438), the device returns the processing to S434.

[0049] Next, an overview of the process of establishing a Wi-Fi EasyMesh network between the camera 101 and the smart device 102 according to the processes in Figures 4A and 4B will be described with reference to Figure 5. Note that the example in Figure 5 is an example of the process flow in the state shown in Figure 1.

[0050] In this process, the smart device 102 first accepts a predetermined user operation to select, for example, an automatic selection function between a controller device and an agent device by the operation unit 305, and starts the automatic selection function (F501). Similarly, the camera 101 accepts a predetermined operation from the operation unit 205, and starts the automatic selection function between a controller device and an agent device (F502). When the smart device 102 starts the automatic selection function, it checks the status of each of the wireless communication unit 308, the wired communication unit 309, and the public network communication unit 310, and checks whether or not the smart device 102 is in a state in which it can be directly connected to the public network (F503). Similarly, when the camera 101 starts the automatic selection function, it checks the status of each of the wireless communication unit 208 and the wired communication unit 209, and checks whether or not the smart device 102 is in a state in which it can be directly connected to the public network (F504).

[0051] In this embodiment, the smart device 102 detects that the public network communication unit 310 is connected to the public network, and the camera 101 detects that it cannot connect to the public network through the wireless communication unit 208 and the wired communication unit 209 (F505, F506). In this case, since the smart device 102 detects that the public network communication unit 310 is connected to the public network, it determines the role of its own device as a controller device and activates the controller function (F507). Then, when the smart device 102 wirelessly constructs a Wi-Fi EasyMesh network, it activates the AP mode of the wireless communication unit 308 and constructs a network with a fronthaul SSID. Since the camera 101 detects that it cannot connect to the public network, it determines the role of its own device as an agent device and activates the agent function (F508). Then, when the camera 101 wirelessly joins the Wi-Fi EasyMesh network, it activates the STA mode of the wireless communication unit 208 and starts network joining processing as a backhaul STA (F508).

[0052] When the smart device 102 starts the controller function and constructs a network, it starts the communication parameter sharing process. In the communication parameter sharing process, as described above, the parameter providing device provides the parameter receiving device with the communication parameters for wireless communication. Here, the controller device is the device that provides the communication parameters. That is, the smart device 102, which is the controller device, becomes the registrar in WPS and the configurator in DPP. Note that the communication parameter sharing process is executed using WPS and DPP here, but other protocols may be used. The smart device 102 controls the wireless communication unit 308 to start the WPS standby process and the search process for the opposing device by DPP (F509), and executes these processes in parallel (or in a time-division manner in some cases). For example, the smart device 102 controls the wireless communication unit 308 to execute the search process by receiving a Probe Request for WPS and transmitting an Action Frame for DPP. Furthermore, the smart device 102 controls the wired communication unit 309 so as to start a search process for a counterpart device as defined by the IEEE 1905.1 standard (F509).

[0053] When the camera 101 activates the agent function and starts the network joining process, it starts the communication parameter sharing process in the same way as the smart device 102. The agent device becomes a device that receives communication parameters. In other words, the camera 101, which is an agent device, becomes an Enrollee in WPS and DPP. The camera 101 controls the wireless communication unit 208 to start the search process for the partner device by WPS and the waiting process for DPP (F510), and executes these processes in parallel (or in a time-division manner in some cases). For example, the camera 101 controls the wireless communication unit 208 to perform the search process by transmitting a Probe Request and receiving an Action Frame by DPP. The camera 101 also controls the wired communication unit 209 to start the search process for the partner device defined by the IEEE1905.1 standard (F510).

[0054] The smart device 102 performs a communication parameter sharing process using the wireless communication unit 308 or the wired communication unit 309, and the camera 101 performs a communication parameter sharing process using the wireless communication unit 208 or the wired communication unit 209 (F511). Note that, although the communication parameter sharing process is performed by wireless communication here, the communication parameter sharing process may be performed by wired communication. The camera 101 wirelessly connects to the network of the fronthaul SSID established by the smart device 102 as a backhaul STA using the parameters received in the communication parameter sharing process (F512). Here, a connection is established in a lower layer such as a physical layer and a MAC (medium access control) layer. Note that, in this embodiment, the communication parameter sharing process may be performed by WPS and DPP, but only one of them may be performed.

[0055] The camera 101 transmits an IEEE1905.1 AP-Auto Configuration Search Message using the wireless communication unit 208 in order to share communication parameters of layers higher than the MAC layer (F513). When the smart device 102 receives this message, it transmits an IEEE1905.1 AP-Auto Configuration Response Message as a response signal using the wireless communication unit 308 (F514). As a result, the camera 101 and the smart device 102 recognize each other as devices that comply with IEEE1905.1. Note that the smart device 102 may transmit an IEEE1905.1 AP-Auto Configuration Search Message using the wireless communication unit 308. In this case, the camera 101 may transmit an IEEE1905.1 AP-Auto Configuration Response Message as a response signal to this using the wireless communication unit 208.

[0056] Next, in order to obtain information on the AP, the smart device 102 transmits an IEEE1905.1 AP Capability Query Message to the camera 101 using the wireless communication unit 308 (F515). Upon receiving this message, the camera 101 transmits an IEEE1905.1 AP Capability Query Report to the smart device 102 using the wireless communication unit 208 as a response signal (F516). The AP Capability Query Report includes, for example, information indicating the state of the wireless link (STA Link Metrics). The AP Capability Query Report may also include information on HT / VHT / HE Capabilities. This information may indicate whether the wireless communication unit 208 of the camera 101 supports each of IEEE802.11n (HT), IEEE802.11ac (VHT), and IEEE802.11ax (HE). The AP Capability Query Report may also include information on RCPI-based Steering. RCPI is a Received Channel Power Indicator, and this information indicates whether steering based on RCPI is supported. The AP Capability Query Report may also include information on Radio Basic Capabilities, which indicates basic capabilities related to wireless. The AP Capability Query Report may also include other information. This AP Capability Query allows the smart device 102 operating as a controller device to obtain information on the camera 101 operating as an agent device.

[0057] The smart device 102 may include information about its own device in the IEEE1905.1 AP Capability Query Message and transmit it. Alternatively, the camera 101 may transmit the IEEE1905.1 AP Capability Query Message, and the smart device 102 may transmit the IEEE1905.1 AP Capability Query Report. That is, in the above example, the camera 101 notifies the smart device 102 of various information, but the smart device 102 may notify the camera 101 of similar information. This notification may be mutual, or may be performed only for one of the devices, as long as the device that ultimately operates as the controller device can obtain the various information.

[0058] Through the above-mentioned processing, the smart device 102 can control the mesh network that connects APs, with the smart device 102 itself and the camera 101 acting as APs. Note that other devices operating as terminals (STAs) can fully receive communication services via the mesh network when connected to either the camera 101 operating as an AP or the smart device 102.

[0059] As described above, each device according to this embodiment automatically determines which device will be the controller device and which will be the agent device, based on whether the device itself can be directly connected to the public network. That is, each device operates in the role of a controller device when it can be directly connected to the public network, and operates in the role of an agent device when it cannot be connected to the public network. This eliminates the need for the user to manually set, since each device automatically determines whether it will operate as a controller device or an agent device. In addition, since a device that cannot be connected to the public network will not operate as a controller, it is possible to prevent situations where a communication function that should be available is actually unavailable. This can increase the convenience of the system.

[0060] Next, the process when a device starts operating as a controller device (S404) and the opposing device is also a controller device (NO in S412 when the opposing device is not an agent device) will be described with reference to Fig. 6. The process in Fig. 6 is also performed by the control unit of each device reading and executing a computer program stored in a non-volatile memory or the like. Note that part or all of the process in Fig. 6 may be realized by hardware such as an ASIC.

[0061] The device judges whether or not the device itself continues the automatic selection function of the controller device and the agent device (S601). If the device itself does not continue the automatic selection function (NO in S601), the device decides not to transfer the authority as the controller device to the opposite device (S615) and ends the process. On the other hand, if the device itself continues the automatic selection function (YES in S601), the device transmits an IEEE1905.1 AP Capability Query Message to the opposite device in order to obtain information about the opposite device (S602). After that, the device receives an IEEE1905.1 AP Capability Query Report from the opposite device (S603). The AP Capability Query Report includes information about the capabilities of the public network in the opposite device. This information may include, for example, information about whether the opposite device is connected to the public network, the communication speed and capacity of the public network, and the like. The AP Capability Query Report may also include other information as described above, but this will not be described in detail here. These messages are transmitted and received using a wireless communication unit or a wired communication unit.

[0062] The device compares the acquired information on the public network of the opposite device with information on the public network to which the device itself is connected (S604). Based on the information on the public network of the opposite device, the device judges whether the opposite device can directly connect to the public network (S605). In the following, the opposite device that can directly connect to the public network is called a public network opposite device. If the opposite device cannot directly connect to the public network (NO in S605), the device decides not to transfer the authority as the controller device to the opposite device (S615) and ends the process. On the other hand, if the opposite device can directly connect to the public network (YES in S605), the device subsequently judges whether the communication speed when the public network opposite device communicates on the public network is faster than the communication speed when the device itself communicates on the public network (S606). The device can perform this judgment based on the actual measured values ​​and system capacity of the throughput and communication quality of the public network of the device itself and these values ​​of the public network of the public network opposite device. When the device determines that the communication speed when the public network facing device communicates via the public network is faster (YES in S606), the device transitions the process to S607. On the other hand, when the device determines that the communication speed when the device itself communicates via the public network is faster (NO in S606), the device transitions the process to S613.

[0063] In S607, the device decides to transfer the controller device authority to the public network facing device that is determined to be capable of high-speed communication in the determination in S606, and starts a process of transmitting information to the public network facing device to transfer the network information. In this process, the device may transmit an IEEE1905.1 AP Metrics Query Message including basic setting information of APs belonging to the EasyMesh network to the target facing device (S608). Then, the device transmits an IEEE1905.1 Topology Notification Message including network topology information (configuration information) of the Wi-Fi EasyMesh network to the target facing device (S609). In addition, the device may transmit a Multi-AP Policy Config Request Message to the target facing device in IEEE1905.1 to transfer the policy information of the Wi-Fi EasyMesh network.

[0064] The device also transmits diagnostic information indicating the communication status of each device from the establishment of the Wi-Fi EasyMesh network to the present to the target device (S610). The device then transmits an IEEE1905.1 Topology Notification Message indicating that the network configuration information has been changed to each device connected to the device (S611). Note that the messages of S607 to S611 are transmitted via, for example, a wireless communication unit or a wired communication unit. Thereafter, the device stops the controller function and activates the agent function (S612).

[0065] In S613, the device judges whether the throughput performance of the public network is equivalent between the device itself and the public network facing device. When the device judges that the performance of the public network is not equivalent between the device itself and the public network facing device (NO in S613), that is, when the performance of the public network of this public network facing device is relatively low, the device does not transfer the authority as a controller device to this facing device (S615) and ends the process. On the other hand, when the device judges that the performance of the public network is equivalent between the device itself and the public network facing device (YES in S613), it then compares the wireless communication speed (e.g., throughput) between the device itself and the public network facing device (S614). Then, when the device judges that the wireless communication speed of the public network facing device is higher (YES in S614), it transitions the process to S607 and transfers the controller device authority to this public network facing device. When the device determines that the wireless communication speed of its own device is faster (NO in S614), it does not transfer the controller device authority to this public network facing device (S615) and ends the process.

[0066] Next, an overview of the process until a Wi-Fi EasyMesh network is established according to the processes of FIGS. 4A to 4B and 6 will be described with reference to FIG. 8. The example of FIG. 8 is an example of a process flow in the state shown in FIG. 7. In FIG. 7 as well, a Wi-Fi EasyMesh network is established between the camera 101 and the smart device 102 as described above. Here, the smart device 102 operates as a controller device of the Wi-Fi EasyMesh network and establishes a wireless LAN network 702 with a fronthaul SSID. The camera 101 operates as an agent device of the Wi-Fi EasyMesh network and is wirelessly connected to the wireless LAN network 702 as a backhaul STA.

[0067] In this state, a smart device 703 that can connect to the public network 701 is assumed to newly join the Wi-Fi EasyMesh network. The communication speed (throughput) of the public network 701 is assumed to be faster than the public network 103 to which the smart device 102 can connect. For example, when the public network 701 is an LTE-Advanced network and the public network 103 is an LTE network, such a difference in communication speed may occur. Also, for example, when the smart device 102 and the smart device 703 can connect to the same system (e.g., LTE-Advanced), but the smart device 102 is subject to a communication speed limit, such a difference in communication speed may occur. Also, for example, when the smart device 102 and the smart device 703 can connect to the same system, such a difference in communication speed may occur due to a difference in capability or terminal category between the smart device 102 and the smart device 703. In this way, a difference in communication speed of the smart device in the public network may occur due to various conditions including the above conditions and further conditions, but each device can recognize the difference in communication speed by determining at least one of these conditions. The smart device 703 and the smart device 102 have the same configuration as shown in FIG.

[0068] In the process of FIG. 8, the smart device 102 and the camera 101 are already in a wireless connection state (F801). At this time, it is assumed that the smart device 102 continues the above-mentioned automatic selection function of the controller device and the agent device. Here, it is assumed that the smart device 102 and the smart device 703 have established a wired connection (F802). Note that, here, it is assumed that the smart device 102 and the smart device 703 are connected by wire, but the following discussion can be applied even if the wired connection is replaced with a wireless connection. For example, the smart device 703 starts the process of S402 and subsequent steps in FIG. 4A in response to this wired connection. The smart device 703 first starts the automatic selection function of the controller device and the agent device in response to a user operation (F803), and checks the respective states of the wireless communication unit 308, the wired communication unit 309, and the public network communication unit 310 (F804). Here, the smart device 703 confirms that it is in a state in which it can directly connect to the public network using any of the communication units (for example, the public network communication unit 310) (F805), and starts up the controller function (F806).

[0069] Then, the smart device 703 transmits an IEEE1905.1 AP-Auto Configuration Search Message to the smart device 102 in order to set communication parameters of layers higher than the MAC layer (F807). The smart device 102 transmits an IEEE1905.1 AP-Auto Configuration Response Message to the smart device 703 as a response signal to this message (F808). As a result, the smart device 102 and the smart device 703 mutually recognize each other as IEEE1905.1 devices. Next, the smart device 102 transmits an IEEE1905.1 AP Capability Query Message to the smart device 102 in order to obtain AP information (F809). Then, the smart device 703 transmits an IEEE1905.1 AP Capability Query Report to the smart device 102 (F810). The IEEE1905.1 AP Capability Query Report may include information on whether the smart device 703 is connected to a public network, the communication speed and capacity of the public network, etc. Since the smart device 102 and the smart device 703 have established a wired connection, these messages may be transmitted and received using the wired communication unit 309.

[0070] The smart device 102 may transmit an IEEE1905.1 AP-Auto Configuration Search Message. In this case, the smart device 703 may transmit an IEEE1905.1 AP-Auto Configuration Response Message as a response signal to the message. The smart device 102 may transmit an IEEE1905.1 AP Capability Query Message including information about the smart device itself. The smart device 703 may transmit an IEEE1905.1 AP Capability Query Message, and the smart device 102 may transmit an IEEE1905.1 AP Capability Query Report. That is, in the above example, the smart device 703 notifies the smart device 102 of various information, but the smart device 102 may notify the smart device 703 of similar information.

[0071] The smart device 102 compares the acquired information about the public network of the smart device 703 with information about the public network to which the smart device 102 is connected. If the smart device 102 determines that the public network to which the smart device 703 is connected can provide a higher communication speed than the public network to which the smart device 102 is connected, the smart device 102 decides to transfer the controller device authority to the smart device 703 (F811). Note that the smart device 703 can also make a similar determination, but in this case, it determines that the public network to which the smart device 102 is connected has lower performance than the public network to which the smart device 102 is connected, and therefore decides not to transfer the controller device authority.

[0072] In response to the decision to transfer the controller device authority, the smart device 102 transmits information for inheriting the existing Wi-Fi EasyMesh network information to the smart device 703 (F812). The information transmitted here may include, for example, basic setting information of APs belonging to the existing Wi-Fi EasyMesh network. This information may be transmitted by, for example, an IEEE1905.1 AP Metrics Query Message. In addition, the smart device 102 may transmit, in F812, an IEEE1905.1 Topology Notification Message including Wi-Fi EasyMesh network configuration information to the smart device 703. In addition, the smart device 102 may transmit information for inheriting policy information of the Wi-Fi EasyMesh network to the smart device 703. This information may be transmitted by, for example, an IEEE1905.1 Multi-AP Policy Config Request Message.

[0073] Then, since the Wi-Fi EasyMesh network configuration is changed, the smart device 102 notifies the camera 101 of the network configuration information (F813). The network configuration information includes at least one of controller device information, agent device information, and STA information. This notification is transmitted, for example, by using an extended IEEE1905.1 Topology Notification Message. After transmitting these messages, the smart device 102 stops the controller function and activates the agent function (F814).

[0074] The smart device 703 transmits information for transmitting policy information of the Wi-Fi EasyMesh network to the camera 101 and the smart device 102 (F815, F816). Note that this information is transmitted, for example, by an IEEE1905.1 Multi-AP Policy Config Request Message. The Multi-AP Policy Config Request Message includes network policy information (e.g., STA steering, etc.).

[0075] Through such processing, the controller device authority is transferred from the smart device 102 to the smart device 703, and the Wi-Fi EasyMesh network is updated. In the above example, the smart device 102, which was a controller device in the existing Wi-Fi EasyMesh network, transfers the controller device authority to the smart device 703 that newly joins the network. On the other hand, if the public network to which the smart device 703 connects has lower performance than the public network to which the smart device 102 connects, the smart device 703 stops operating as a controller device. In this case, the smart device 703 skips the processing of S607 to S611 in FIG. 6 because there is no network that it manages at that time. Then, the smart device 703 stops the controller function and starts the agent function, and connects to the smart device 102 as an agent device and joins the existing Wi-Fi EasyMesh network. Even in this case, the smart device 102 can notify the camera 101 of the network configuration information because the topology is changed.

[0076] In the above example, a case where a new device that can connect to a public network joins an existing Wi-Fi EasyMesh network has been described, but similar processing can be performed when such a network is newly constructed. For example, when the smart device 102 and the smart device 703 construct a new Wi-Fi EasyMesh network, these devices can directly connect to the public network, and therefore initially become controller devices. After that, information on the capabilities of the public network is exchanged between these devices, and one device maintains the operation as a controller device, while the other device transitions to an agent device. Then, the controller device constructs a wireless LAN network, for example, a Fronthaul SSID, and the agent device wirelessly connects to the network as a Backhaul STA. This allows a new Wi-Fi EasyMesh network to be constructed between the two devices that can connect to the public network.

[0077] As described above, when there are multiple devices that can be connected to a public network, the device with the higher performance in communication over the public network becomes the controller device, and the device with a relatively lower performance in communication over the public network automatically transitions to an agent device. This allows the user to select an appropriate device as the controller device without having to consider which device to select, improving user convenience.

[0078] In the present embodiment, the process has been described in which the device determines the role of its own device depending on whether it can be directly connected to a public network, and then re-determines the role depending on the role of the other device, but the process is not limited to this. For example, the device may determine a provisional role depending on whether it can be connected to a public network, and then determine a formal role depending on the role of the other device, etc. In other words, the device may temporarily transition to an intermediate state that is neither a controller device nor an agent device, based on whether it can be connected to a public network, and then determine a final role.

[0079] In the present embodiment, the role determination is performed based on whether the device can be directly connected to a public network, but the same process may be performed for a specific network other than the public network. For example, the role determination may be performed based on whether the device can be directly connected (without going through other devices included in the mesh network) to a local network of a company, school, etc.

[0080] <<Other embodiments>> The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions. [Explanation of symbols]

[0081] 101: camera, 102, 703: smart device, 103, 701: public network, 702: wireless LAN network, 201, 301: control unit, 203, 303: non-volatile memory, 205, 305: operation unit, 208, 308: wireless communication unit, 209, 309: wired communication unit, 310: public network communication unit

Claims

1. A communication device, comprising: A management means for causing the communication device to function as a controller of Wi-Fi EasyMesh (registered trademark) and managing a mesh network; a transmission means for transmitting, when a predetermined condition is satisfied, data including at least network information that can be used to reconstruct a network constructed by the communication device functioning as the controller to another communication device; A communication device comprising:

2. 2. The communication device according to claim 1, further comprising a search unit that searches for a counterpart device to be connected when the communication device is made to function as an agent of the Wi-Fi EasyMesh.

3. 3. The communication device according to claim 2, wherein said search means searches for said counterpart device in accordance with the provisions of the IEEE 1905.1 standard when a wired connection of said communication device is valid.

4. The communication device according to claim 2 or 3, characterized in that the search means searches for the opposing device using at least one of a method conforming to a Wi-Fi Protected Setup (WPS) standard and a method conforming to a Device Provisioning Protocol (DPP) standard.

5. The communication device according to any one of claims 2 to 4, further comprising a control means for controlling the communication device to stop operating as the agent if a counterpart device operating as a controller of the Wi-Fi EasyMesh is not found by a search by the search means when the communication device is made to function as the agent.

6. The communication device according to claim 1 , wherein the other communication device is a smart device.

7. The communication apparatus according to claim 6, wherein the smart device is a smart device that can connect to a public network using an LTE-Advanced system.

8. 8. A communication device according to claim 1, wherein the data further includes information relating to steering of the station equipment.

9. A method for controlling a communication device, comprising: A management step of causing the communication device to function as a Wi-Fi EasyMesh (registered trademark) controller and managing a mesh network; a transmission control step of transmitting, to another communication device, data including at least network information that can be used to reconstruct a network constructed by the communication device functioning as the controller, when a predetermined condition is satisfied; A control method comprising the steps of:

10. A computer and each of the means included in the communication device according to any one of claims 1 to 8. A program to make it function as such.

Images