JP7613618B2 - Communication Equipment - Google Patents

Description

The technology disclosed in this specification relates to a communication device for executing communication of target data between a mobile terminal.

Patent Documents 1 and 2 disclose techniques for two communication devices to perform wireless communication. In Patent Documents 1 and 2, the two communication devices perform communication with wireless settings according to short-range wireless communication (i.e., wireless communication according to the NFC (short for Near Field Communication) method). The above-mentioned wireless settings are settings for performing wireless communication according to a communication method (e.g., IEEE 802.11a, 802.11b) different from the NFC method. This enables the two communication devices to perform wireless communication according to the wireless settings.

JP 2007-166538 A JP 2011-146991 A

“Wi-Fi Peer-to-Peer (P2P) Technical Specification Version 1.1”, Wi-Fi Alliance, 2010

This specification provides technology that enables a communication device to properly communicate with a mobile terminal.

The technology disclosed in this specification is a communication device, the communication device including: a first type of interface for performing wireless communication with a mobile terminal; a second type of interface for performing wireless communication with the mobile terminal, the second type of interface being faster than the first type of interface; a transmission unit for transmitting predetermined information to the mobile terminal via the first type of interface, the predetermined information including a first wireless setting for the mobile terminal to belong to the first wireless network when the communication device operates as a master station of a first wireless network for performing wireless communication using the second type of interface, and a second wireless setting for the mobile terminal to belong to a second wireless network formed by an access point different from the communication device and the mobile terminal when the communication device does not operate as the master station; and a communication execution unit for performing wireless communication of target data via either the first wireless network or the second wireless network.
Another communication device disclosed in this specification includes a first type interface, a second type interface, and a control unit. The first type interface is an interface for performing wireless communication with a mobile terminal. The second type interface is an interface for performing wireless communication with a mobile terminal. The communication speed of the wireless communication using the second type interface is faster than the communication speed of the communication using the first type interface. The control unit includes a determination unit and a communication execution unit. The determination unit determines whether the communication device currently belongs to a target network for performing wireless communication using the second type interface. In a first case in which it is determined that the communication device currently belongs to a first target network, the communication execution unit executes a transmission process to transmit wireless settings for making the mobile terminal belong to the first target network to the mobile terminal using the first type interface, and then executes wireless communication of target data with the mobile terminal via the first target network using the second type interface. In a second case in which it is determined that the communication device does not currently belong to the target network, the communication execution unit executes a specific process so that both the communication device and the mobile terminal belong to the second target network, and then uses a second type of interface to execute wireless communication of the target data between the mobile terminal and the second target network.

In the above configuration, when it is determined that the communication device currently belongs to the first target network, the mobile terminal can belong to the first target network by using the wireless settings received from the communication device. This allows the communication device to perform wireless communication of target data with the mobile terminal at a relatively high communication speed via the second type of interface. On the other hand, when it is determined that the communication device currently does not belong to the target network, a state in which both the communication device and the mobile terminal belong to the second target network can be realized by the identification process. This allows the communication device to perform communication of target data with the mobile terminal at a relatively high communication speed via the second type of interface. According to this configuration, the communication device can appropriately perform wireless communication with the mobile terminal by performing a process according to whether or not the communication device currently belongs to the network.

The second type of interface may be an interface for the communication device to execute specific wireless communication. The specific wireless communication may be wireless communication executed between the communication device and the mobile terminal without going through an access point different from that between the communication device and the mobile terminal. The specific process may be a process for the communication device and the mobile terminal to execute specific wireless communication using the second type of interface. According to this configuration, the communication device can execute wireless communication of target data with the mobile terminal without going through an access point.

The communication device may be selectively operable in one of a plurality of states including a parent station state in which the communication device functions as a parent station of the target wireless network, a child station state in which the communication device functions as a child station of the wireless network, and a device state different from the parent station state and the child station state. The communication device may be capable of executing specific wireless communication via the target wireless network by operating in either the parent station state or the child station state in the target wireless network. In the second case, the communication execution unit may execute a specific process for newly constructing a second target network to which the communication device and the mobile terminal should belong, which is a second target network for executing specific wireless communication. According to this configuration, when the communication device does not currently belong to the target network, the communication device can appropriately execute wireless communication of target data with the mobile terminal via the newly constructed second wireless network.

In the second case, the communication execution unit may execute a specific process including a process of determining that the communication device should operate in a master station state in the second target network, without executing a selective determination process of selectively determining whether the communication device should operate in a master station state or a slave station state in the second target network. With this configuration, it is possible to newly construct a second wireless network in which the communication device necessarily operates in a master station state. As a result, the communication device can appropriately execute wireless communication of target data with the mobile terminal by operating in a master station state in the newly constructed second wireless network.

The control unit may further include a receiving unit that receives specific information from the mobile terminal using the first type of interface. In the second case, in the specific case where the mobile terminal currently belongs to the second target network, the communication execution unit may execute a specific process for making the communication device belong to the second target network using a specific wireless setting included in the specific information, which is a specific wireless setting for the communication device to belong to the second target network. According to this configuration, the communication device can belong to the second target network to which the mobile terminal currently belongs. As a result, the communication device can properly execute wireless communication of target data with the mobile terminal via the second target network.

The communication device may be capable of using the second type of interface to perform specific wireless communication between the communication device and the mobile terminal without going through an access point different from that between the communication device and the mobile terminal. The communication execution unit may execute a specific process for making the communication device belong to a second target network using the specific wireless setting in a specific case when the specific wireless setting is included in the specific information. The communication execution unit may execute a specific process for newly constructing a second target network to which the communication device and the mobile terminal belong, which is a second target network for performing specific wireless communication by the communication device and to which the communication device and the mobile terminal should belong, in a specific case when the specific wireless setting is not included in the specific information. According to this configuration, the communication device may belong to the second target network to which the mobile terminal currently belongs when a specific wireless setting for belonging to the second target network to which the mobile terminal currently belongs is acquired. As a result, the communication device may appropriately perform wireless communication of target data with the mobile terminal via the second target network. On the other hand, the communication device may newly construct a second target network to perform specific wireless communication when the specific wireless setting is not acquired. As a result, the communication device can properly perform wireless communication of the target data with the mobile terminal via the second target network.

The communication device may be selectively operable in one of a plurality of states including a master station state in which the communication device functions as a master station of the target wireless network, a slave station state in which the communication device functions as a slave station of the target wireless network, and a device state different from the master station state and the slave station state. The communication device may be capable of performing a specific wireless communication via the wireless network by operating in either the master station state or the slave station state in the target wireless network using a second type of interface. The communication device may further be capable of performing other wireless communication between the communication device and the mobile terminal using the second type of interface. The communication execution unit may execute a transmission process to transmit wireless settings for the mobile terminal to belong to the first target network via the first type of interface in a first case in which the communication device currently belongs to a first target network for performing other wireless communication. The communication execution unit may execute a transmission process to transmit wireless settings for the mobile terminal to belong to the first target network via the first type of interface in a first case in which the communication device currently belongs to a first target network for performing a specific communication and the communication device operates in a master station state in the first target network. The communication execution unit may not execute the transmission process in a first case in which the communication device currently belongs to the first target network by performing the specific communication and the communication device operates in a slave station state in the first target network. According to this configuration, when the communication device currently belongs to a first target network for performing another wireless communication, the communication device may execute communication of target data with the mobile terminal at a relatively high communication speed via the second type of interface. Furthermore, when the communication device operates in a master station state in the first target network, the communication device may appropriately execute communication of target data with the mobile terminal via the first target network to which the communication device currently belongs. On the other hand, when the communication device is operating as a slave station in the first wireless network, the communication device can suppress the mobile terminal from joining the first wireless network.

The communication execution unit may execute a transmission process in the first case when the mobile terminal does not currently belong to the first target network. The communication execution unit may not execute a transmission process in the first case when the mobile terminal currently belongs to the first target network. According to this configuration, the communication device does not need to execute a transmission process when both the communication device and the mobile terminal currently belong to the first target network. This allows the communication device to execute communication of target data with the mobile terminal via the first target network without executing a transmission process.

The control unit may further include a receiving unit that receives specific information from the mobile terminal using the first type of interface. The determination unit may further use the specific information to determine whether or not the mobile terminal currently belongs to a first target network. The communication execution unit may execute a transmission process when it is determined in the first case that the mobile terminal does not currently belong to the first target network. The communication execution unit may not execute a transmission process when it is determined in the first case that the mobile terminal currently belongs to the first target network. According to this configuration, the communication device can appropriately determine whether or not the mobile terminal currently belongs to the first target network.

In addition, a control method for implementing the above-mentioned communication device, a computer program, and a computer-readable recording medium storing the computer program are also new and useful. Also, a communication system including the above-mentioned communication device and a mobile terminal is also new and useful.

1 shows the configuration of a communication system. 4 shows a flowchart of a communication process executed by a multi-function device according to a first embodiment. FIG. 13 shows a sequence diagram for explaining the processing executed by each device in a first situation. FIG. 11 is a sequence diagram for explaining the processing executed by each device in a second situation. FIG. 11 is a sequence diagram for explaining the processing executed by each device in a third situation. FIG. 13 is a sequence diagram for explaining the processing executed by each device in a fourth situation. FIG. 13 is a sequence diagram for explaining the processing executed by each device in a fifth situation. 13 shows a flowchart of a communication process executed by a multi-function device according to a second embodiment. A sequence diagram for explaining the processing performed by each device in a sixth situation is shown. 13 shows a flowchart of a communication process executed by a multi-function device according to a third embodiment. FIG. 13 is a sequence diagram for explaining the processing performed by each device in a seventh situation.

(First embodiment)
(Configuration of communication system)
1, the communication system 2 includes a multi-function device (hereinafter referred to as "MFP" (abbreviation of Multi-Function Peripheral)) 10, a portable terminal 50, an access point (hereinafter referred to as "AP") 6, and a PC 8. The MFP 10 and the portable terminal 50 are capable of performing short-distance wireless communication. The short-distance wireless communication is wireless communication according to the NFC method. In this embodiment, wireless communication according to the NFC method is performed based on the international standard ISO/IEC 21481 or 18092.

The MFP 10 can also perform wireless communication according to the Wi-Fi Direct method described below. Hereinafter, Wi-Fi Direct will be referred to as "WFD." In WFD, wireless communication is performed based on the IEEE (The Institute of Electrical and Electronics Engineers, Inc.) 802.11 standard and standards equivalent thereto (e.g., 802.11a, 11b, 11g, 11n, etc.). The NFC method and the WFD method (hereinafter referred to as the "WFD method") have different wireless communication methods (i.e., wireless communication standards). Also, the communication speed of wireless communication according to the WFD method is faster than the communication speed of wireless communication according to the NFC method.

For example, the MFP 10 can build a WFD network by establishing a connection with the mobile device 50 (hereinafter referred to as a "WFD connection") according to the WFD method. Similarly, the MFP 10 can build a WFD network by establishing a WFD connection with the PC 8.

The PC8, the MFP10, and the mobile terminal 50 can also perform wireless communication according to a normal Wi-Fi (e.g., IEEE802.11) system that is different from the WFD system. Generally speaking, wireless communication according to normal Wi-Fi is wireless communication that uses the AP6, and wireless communication according to the WFD system is wireless communication that does not use the AP6. For example, the MFP10 can belong to a normal Wi-Fi network by establishing a connection with the AP6 according to normal Wi-Fi (hereinafter referred to as a "normal Wi-Fi connection"). The MFP10 can perform wireless communication with other devices (e.g., the PC8, the mobile terminal 50) that belong to the normal Wi-Fi network via the AP6. Note that the NFC system and the normal Wi-Fi system (hereinafter referred to as the "normal Wi-Fi system") are different wireless communication systems (i.e., wireless communication standards). In addition, the communication speed of normal Wi-Fi is faster than the communication speed of NFC.

(WFD)
WFD is a standard established by the Wi-Fi Alliance and is described in "Wi-Fi Peer-to-Peer (P2P) Technical Specification Version 1.1" created by the Wi-Fi Alliance.

As described above, the PC 8, the MFP 10, and the mobile terminal 50 are each capable of wireless communication according to the WFD system. Hereinafter, a device capable of wireless communication according to the WFD system is referred to as a "WFD-compatible device." The WFD standard defines three states for a WFD-compatible device: Group Owner state (hereinafter referred to as "G/O state"), client state, and device state. A WFD-compatible device can selectively operate in one of the above three states.

A WFD network is made up of G/O state devices and client state devices. In a WFD network, there can be only one G/O state device, but one or more client state devices. A G/O state device manages one or more client state devices. Specifically, a G/O state device generates a management list that describes the identification information (i.e., MAC address) of each of the one or more client state devices. When a client state device newly joins the WFD network, the G/O state device adds the identification information of the device to the management list, and when a client state device leaves the WFD network, the G/O state device deletes the identification information of the device from the management list.

A device in the G/O state can wirelessly communicate target data (e.g., data including network layer information of the OSI reference model (print data, scan data, etc.)) with a device registered in the management list, i.e., a device in the client state (i.e., a device belonging to the WFD network). However, a device in the G/O state can wirelessly communicate data for an unregistered device not registered in the management list (e.g., data not including network layer information (physical layer data such as a probe request signal and a probe response signal) for the unregistered device to belong to the WFD network), but cannot wirelessly communicate the target data. For example, an MFP 10 in the G/O state can wirelessly receive print data from a mobile terminal 50 registered in the management list (i.e., a mobile terminal 50 in the client state), but cannot wirelessly receive print data from a device not registered in the management list.

A device in the G/O state can also relay wireless communication of target data (print data, scan data, etc.) between multiple devices in the client state. For example, when a mobile terminal 50 in the client state needs to wirelessly transmit print data to another printer in the client state, the mobile terminal 50 first wirelessly transmits the print data to the MFP 10 in the G/O state. In this case, the MFP 10 wirelessly receives the print data from the mobile terminal 50 and wirelessly transmits the print data to the other printer. In other words, a device in the G/O state can execute the functions of an AP of a wireless network.

Note that a WFD-compatible device that does not belong to a WFD network (i.e., a device that is not registered in the management list) is a device in device state. A device in device state can perform wireless communication of data required to belong to a WFD network (physical layer data such as a probe request signal and a probe response signal), but cannot perform wireless communication of target data (print data, scan data, etc.) via the WFD network.

Note that, below, devices that are not capable of wireless communication according to the WFD method, but are capable of wireless communication according to normal Wi-Fi, are referred to as "non-WFD compatible devices." "Non-WFD compatible devices" can also be called "legacy devices." Non-WFD compatible devices cannot operate in a G/O state. Devices in the G/O state can write identification information of non-WFD compatible devices in the management list.

(Configuration of MFP 10)
The MFP 10 includes an operation unit 12, a display unit 14, a print execution unit 16, a scan execution unit 18, a wireless LAN interface (hereinafter, the interface will be referred to as "I/F") 20, an NFC I/F 22, and a control unit 30. The operation unit 12 includes a plurality of keys. A user can input various instructions to the MFP 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. The print execution unit 16 is a printing mechanism such as an inkjet type or a laser type. The scan execution unit 18 is a scanning mechanism such as a CCD or a CIS.

The wireless LAN I/F 20 is an interface through which the control unit 30 executes wireless communication according to the WFD method and wireless communication according to normal Wi-Fi. The wireless LAN I/F 20 is physically one interface. However, the wireless LAN I/F 20 is assigned both a MAC address used in wireless communication according to the WFD method (hereinafter referred to as a "MAC address for WFD") and a MAC address used in wireless communication according to normal Wi-Fi (hereinafter referred to as a "MAC address for normal Wi-Fi"). More specifically, the wireless LAN I/F 20 is assigned a MAC address for normal Wi-Fi in advance. The control unit 30 uses the MAC address for normal Wi-Fi to generate a MAC address for WFD and assigns the MAC address for WFD to the wireless LAN I/F 20. The WFD MAC address is different from the normal Wi-Fi MAC address. Therefore, the control unit 30 can simultaneously perform both wireless communication according to the WFD method and wireless communication according to normal Wi-Fi via the wireless LAN I/F 20. As a result, a situation can arise in which the MFP 10 belongs to both the WFD network and the normal Wi-Fi network.

A G/O state device can describe in the management list not only the identification information of WFD-compatible devices in the client state, but also the identification information of WFD-incompatible devices. That is, a G/O state device can establish a WFD connection with a non-WFD-compatible device. Generally speaking, a WFD connection is a wireless connection in which the WFD MAC address of the MFP 10 is used. Also, a WFD network is a wireless network in which the WFD MAC address of the MFP 10 is used. Similarly, a normal Wi-Fi connection is a wireless connection in which the normal Wi-Fi MAC address of the MFP 10 is used. Also, a normal Wi-Fi network is a wireless network in which the normal Wi-Fi MAC address of the MFP 10 is used.

By operating the operation unit 12, the user can change the settings of the wireless LAN I/F 20 to either a mode in which wireless communication according to the WFD method using the wireless LAN I/F 20 can be performed (hereinafter referred to as "WFD=ON mode") or a mode in which wireless communication according to the WFD method using the wireless LAN I/F 20 cannot be performed (hereinafter referred to as "WFD=OFF mode"). The mode setting unit 46 sets either the WFD=ON mode or the WFD=OFF mode according to the user's operation. Specifically, the mode setting unit 46 stores in the memory 34 a mode value that indicates the mode set by the user.

When the control unit 30 is in WFD I/F OFF mode, it cannot execute processes according to the WFD method (e.g., a process for setting the MFP 10 to the spontaneous G/O mode described below, G/O negotiation, etc.). When the WFD I/F is ON, the memory 34 stores a value indicating the current state of the MFP 10 with respect to WFD (either G/O state, client state, or device state).

The NFC I/F 22 is an interface that enables the control unit 30 to perform wireless communication according to the NFC standard. The NFC I/F 22 is configured on a chip that is physically different from the W-Fi I/F 20.

The communication speed of wireless communication via the wireless LAN I/F 20 (e.g., a maximum communication speed of 11 to 454 Mbps) is faster than the communication speed of wireless communication via the NFC I/F 22 (e.g., a maximum communication speed of 100 to 424 Kbps). Furthermore, the carrier frequency in wireless communication via the wireless LAN I/F 20 (e.g., 2.4 GHz band, 5.0 GHz band) is different from the carrier frequency in wireless communication via the NFC I/F 22 (e.g., 13.56 MHz band). Furthermore, when the distance between the MFP 10 and the portable terminal 50 is approximately 10 cm or less, the control unit 30 can perform wireless communication with the portable terminal 50 according to the NFC method via the NFC I/F 22. On the other hand, even if the distance between the MFP 10 and the portable terminal 50 is 10 cm or less or 10 cm or more (for example, up to about 100 m), the control unit 30 can perform wireless communication with the portable terminal 50 according to the WFD method and wireless communication according to normal Wi-Fi via the wireless LAN I/F 20. In other words, the maximum distance over which the MFP 10 can perform wireless communication with a communication destination device (for example, the portable terminal 50) via the wireless LAN I/F 20 is greater than the maximum distance over which the MFP 10 can perform wireless communication with a communication destination device via the NFC I/F 22.

The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the programs stored in the memory 34. The functions of each of the units 40 to 46 are realized by the CPU 32 executing processes according to the programs.

The memory 34 is composed of a ROM, a RAM, a hard disk, etc. The memory 34 stores the above-mentioned programs executed by the CPU 32. The memory 34 has a work area 38. When the MFP 10 currently belongs to a WFD network, the work area 38 stores information indicating that the MFP 10 currently belongs to the WFD network, and wireless settings (including authentication method, encryption method, password, SSID (Service Set Identifier), BSSID (Basic Service Set Identifier) of the wireless network) for executing communication of target data (e.g., print data) via the WFD network. When the MFP 10 currently belongs to a normal Wi-Fi network, the work area 38 stores information indicating that the MFP 10 currently belongs to the normal Wi-Fi network, and wireless settings for executing communication of target data via the normal Wi-Fi network. The SSID of a WFD network is a network identifier for identifying the WFD network, and the SSID of a normal Wi-Fi network is a network identifier for identifying the normal Wi-Fi network. The BSSID of a WFD network is an identifier unique to a device in the G/O state (e.g., the MAC address of a device in the G/O state), and the BSSID of a normal Wi-Fi network is an identifier unique to an AP (e.g., an AP-specific identifier).

Work area 38 further stores a value indicating the current WFD state (G/O state, client state, or device state) when MFP 10 is operating according to the WFD method. Work area 38 further stores a mode value indicating WFD=ON mode or a mode value indicating WFD=OFF mode.

The user can set the MFP 10 to the spontaneous G/O mode by operating the operation unit 12. The spontaneous G/O mode is a mode in which the MFP 10 maintains operation in the G/O state. The work area 38 in the memory 34 further stores a value indicating whether the MFP 10 is set to the spontaneous G/O mode. As will be described in detail later, when a WFD-compatible device in the device state establishes a WFD connection with another WFD-compatible device in the device state, the MFP 10 normally executes G/O negotiation to selectively determine whether it should operate in the G/O state or the client state. When the MFP 10 is set to the spontaneous G/O mode, the MFP 10 maintains operation in the G/O state without executing G/O negotiation.

(Configuration of the mobile terminal 50)
The portable terminal 50 is, for example, a mobile phone (e.g., a smartphone), a PDA, a notebook PC, a tablet PC, a portable music player, a portable video player, etc. The portable terminal 50 has two wireless interfaces, a wireless LAN I/F (i.e., an interface for WFD and normal Wi-Fi) and an NFC I/F. Therefore, the portable terminal 50 can perform wireless communication with the MFP 10 using the wireless LAN I/F, and can also perform wireless communication with the MFP 10 using the NFC I/F. The portable terminal 50 has an application program for causing the MFP 10 to perform a function (e.g., a print function, a scan function, etc.). Note that the application program may be installed in the portable terminal 50 from a server provided by the vendor of the MFP 10, for example, or may be installed in the portable terminal 50 from a medium shipped together with the MFP 10.

The portable terminal 50, like the MFP 10, has a work area 58 in the memory 54. When the portable terminal 50 currently belongs to a WFD network or a normal Wi-Fi network, the work area 58 stores wireless settings (including authentication method, encryption method, password, SSID and BSSID of the wireless network) for performing communication via the network. Furthermore, when the portable terminal 50 is operating according to the WFD method, the work area 58 stores a status value that indicates the status of the portable terminal 50 (i.e., any one of G/O status, client status, and device status).

(Configuration of PC8)
The PC 8 has a wireless LAN I/F (i.e., an interface for WFD and normal Wi-Fi), but does not have an NFC I/F. Therefore, the PC 8 can communicate with the MFP 10 using the wireless LAN I/F, but cannot perform wireless communication according to the NFC method. The PC 8 has a driver program for causing the MFP 10 to execute processes (e.g., printing processes, scanning processes, etc.). The driver program is usually installed in the PC 8 from a medium shipped together with the MFP 10. However, in a modified example, the driver program may be installed in the PC 8 from a server provided by the vendor of the MFP 10.

(Configuration of AP6)
The AP6 is not a device in a WFD G/O state, but a normal access point called a wireless access point or a wireless LAN router. The AP6 can establish a normal Wi-Fi connection with a plurality of devices. This creates a normal Wi-Fi network including the AP6 and the plurality of devices. The AP6 receives data from one device among the plurality of devices belonging to the normal Wi-Fi network, and transmits the data to another device among the plurality of devices. That is, the AP6 relays communication between a pair of devices belonging to the normal Wi-Fi network.

The differences between a device in the WFD G/O state and a normal AP are as follows. That is, when a device in the WFD G/O state leaves the WFD network to which it currently belongs and newly joins another WFD network, it can operate in a state other than the G/O state (i.e., client state). In contrast, a normal AP (i.e., AP6) performs the function of relaying communications between a pair of devices, regardless of which normal Wi-Fi network the AP belongs to, and cannot operate in the client state.

(Communication Processing Executed by MFP 10)
The communication process executed by the MFP 10 will be described with reference to Fig. 2. When the MFP 10 is powered on, the control unit 30 executes the communication process. In S2, the receiving unit 40 monitors whether or not NFC information is received by performing wireless communication according to the NFC method. The receiving unit 40 receives the NFC information via the NFC I/F 22. Specifically, the receiving unit 40 monitors whether or not an NFC communication session is established between the MFP 10 and the portable terminal 50. While the MFP 10 is powered on, the receiving unit 40 causes the NFC I/F 22 to transmit radio waves to detect a device capable of performing wireless communication according to the NFC method.

The user of the portable terminal 50 starts an application program. By operating the portable terminal 50, the user causes the portable terminal 50 to generate NFC information including a process execution instruction (e.g., a print instruction, a scan instruction) indicating the process to be executed by the MFP 10. The NFC information further includes the SSID and BSSID of the wireless network to which the portable terminal 50 currently belongs, if the portable terminal 50 currently belongs to a wireless network. Note that the portable terminal 50 currently belongs to a wireless network when at least one of a WFD connection and a normal Wi-Fi connection has been established between the portable terminal 50 and another device (e.g., the AP 6, the MFP 10).

When the user brings the portable terminal 50 closer to the MFP 10 so that the distance between the portable terminal 50 and the MFP 10 becomes smaller than the distance at which radio waves can reach each other (e.g., 10 cm), the portable terminal 50 receives the radio waves from the MFP 10 and transmits a response radio wave to the MFP 10. As a result, the control unit 30 receives the response radio wave from the portable terminal 50 and establishes an NFC communication session. When the NFC communication session is established, the portable terminal 50 transmits the generated NFC information to the MFP 10.

When the NFC information is received (YES in S2), in S4 the determination unit 42 determines whether the MFP 10 currently belongs to a network. Specifically, if at least one of information indicating that the MFP 10 currently belongs to a WFD network and information indicating that the MFP 10 currently belongs to a normal Wi-Fi network is stored in the work area 38, the determination unit 42 determines that the MFP 10 currently belongs to a wireless network (YES in S4) and proceeds to S6. On the other hand, if neither information indicating that the MFP 10 currently belongs to a WFD network nor information indicating that the MFP 10 currently belongs to a normal Wi-Fi network is stored in the work area 38, the determination unit 42 determines that the MFP 10 currently does not belong to a wireless network (NO in S4) and proceeds to S8.

In S6, the determination unit 42 checks whether the mobile terminal 50 currently belongs to the network to which the MFP 10 currently belongs. Specifically, the determination unit 42 first determines whether the SSID and BSSID of the network to which the mobile terminal 50 currently belongs are included in the NFC information. If the SSID and BSSID are not included in the NFC information, the determination unit 42 determines that the mobile terminal 50 does not currently belong to the network to which the MFP 10 currently belongs (NO in S6). With this configuration, the MFP 10 can appropriately determine that the mobile terminal 50 does not currently belong to the network to which the MFP 10 currently belongs. If the SSID and BSSID of the network to which the mobile terminal 50 currently belongs are included in the NFC information, the determination unit 42 determines whether the SSID and BSSID included in the wireless settings stored in the work area 38 match the SSID and BSSID included in the NFC information.

If both the SSID and the BSSID match, it is determined that the mobile terminal 50 currently belongs to the network to which the MFP 10 currently belongs (YES in S6), and the process proceeds to S7. On the other hand, if at least one of the SSID and the BSSID does not match, it is determined that the mobile terminal 50 does not currently belong to the network to which the MFP 10 currently belongs (NO in S6), and the process proceeds to S8. With this configuration, the MFP 10 can appropriately determine whether the mobile terminal 50 currently belongs to the network to which the MFP 10 currently belongs. In addition, in S6, the determination unit 42 determines whether the SSIDs match and also determines whether the BSSIDs match. This allows the determination unit 42 to determine whether the MFP 10 and the mobile terminal 50 belong to the same wireless network built by the same AP. To be more specific, one AP may build multiple wireless networks by using multiple SSIDs. Therefore, if the BSSIDs match but the SSIDs do not match, there is a risk that the MFP 10 and the portable terminal 50 belong to different wireless networks established by the same AP. In this embodiment, by determining whether both the SSID and the BSSID match, it is possible to more reliably determine whether the MFP 10 and the portable terminal 50 belong to the same wireless network. Note that in a modified example, it is possible to determine whether the SSIDs match in S6, without determining whether the BSSIDs match. As a result, even if the MFP 10 and the portable terminal 50 belong to wireless networks established by different access points, if the SSIDs match, it can be determined that the MFP 10 and the portable terminal 50 belong to the same wireless network.

If the portable terminal 50 currently belongs to the network to which the MFP 10 currently belongs, the MFP 10 and the portable terminal 50 can communicate via the currently belonging network. That is, the portable terminal 50 can perform wireless communication with the MFP 10 using the wireless settings currently stored in the work area 58. In S7, the control unit 30 transmits, via the NFC I/F 22, setting change unnecessary information indicating that data communication can be performed without changing the wireless settings of the portable terminal 50, and proceeds to S20. The setting change unnecessary information includes the IP address of the MFP 10.

In S8, the determination unit 42 determines whether or not the WFD=ON mode is set. If the mode value stored in the memory 34 is a value representing the WFD=ON mode, the determination unit 42 determines YES in S8 and proceeds to S10. On the other hand, if the mode value stored in the memory 34 is a value representing the WFD=OFF mode, the determination unit 42 determines NO in S8 and proceeds to S9.

In S9, the communication execution unit 44 changes the mode value stored in the memory 34, thereby changing the mode from WFD=OFF mode to WFD=ON mode, and proceeds to S15. The communication execution unit 44 further stores in the memory 34 setting change information indicating that the mode value has been changed.

In S10, the determination unit 42 determines whether the MFP 10 is operating in a client state in the wireless network to which it currently belongs. Specifically, the determination unit 42 determines that the MFP 10 is operating in a client state when the state value stored in the work area 38 is a value that represents a client state (YES in S10). On the other hand, the determination unit 42 determines that the MFP 10 is not operating in a client state when the state value stored in the work area 38 is not a value that represents a client state (NO in S10). If YES in S10, proceed to S14.

On the other hand, if the answer is NO in S10, in S12, the judgment unit 42 judges whether the MFP 10 is operating in a G/O state in the wireless network to which it currently belongs. Specifically, the judgment unit 42 judges that the MFP 10 is operating in a G/O state if the status value stored in the work area 38 is a value that represents the G/O state (YES in S12). On the other hand, the judgment unit 42 judges that the MFP 10 is not operating in a G/O state (i.e., the MFP 10 is in a device state) if the status value stored in the work area 38 is not a value that represents the G/O state (NO in S12). If the answer is YES in S12, proceed to S13, and if the answer is NO in S12, proceed to S15.

In S13, the judgment unit 42 judges whether the number of devices other than the MFP 10 included in the WFD network in which the MFP 10 is operating in a G/O state (i.e., devices that have established connections with the MFP 10) is less than a predetermined maximum number of clients. If the number of pieces of device identification information stored in the management list is less than the maximum number of clients, the judgment unit 42 judges YES in S13, and if they are equal, the judgment unit 42 judges NO in S13. If YES in S13, proceed to S16, and if NO in S13, proceed to S14.

In S14, the communication execution unit 44 uses the NFC I/F 22 to send communication NG information indicating that communication between the MFP 10 and the portable terminal 50 is currently not possible to be performed to the portable terminal 50, and ends the communication process.

In S15, the communication execution unit 44 sets the MFP 10 to the spontaneous G/O mode. The spontaneous G/O mode is a mode in which the MFP 10 maintains its operation in the G/O state. Thus, although the WFD network is not constructed at the stage of S15, the MFP 10 is set to the G/O state. When the MFP 10 is set to the G/O state, the communication execution unit 44 prepares wireless settings (SSID, BSSID, authentication method, encryption method, password, etc.) for a WFD-compatible device and/or a WFD-non-compatible device to perform wireless communication with the MFP 10 operating in the G/O state via the WFD network. With this configuration, even if the device (the mobile terminal 50 in this embodiment) that receives the wireless settings from the MFP 10 is a WFD-compatible device or a WFD-non-compatible device, the MFP 10 can perform wireless communication with the device that receives the wireless settings. In general, when the MFP 10 currently belongs to a network according to a first wireless communication method (or wireless communication standard, or wireless communication protocol), the communication execution unit 44 transmits to the communication execution unit 44 wireless settings for belonging to the network, and for the mobile terminal 50 to operate according to a second wireless communication method (or wireless communication standard, or wireless communication protocol) that is different from the first wireless communication method (or wireless communication standard, or wireless communication protocol).

The authentication method and encryption method are predetermined. The communication execution unit 44 generates a password. The SSID may be generated by the communication execution unit 44 when generating the password, or may be determined in advance. The BSSID is the MAC address of the MFP 10. At this stage, the management list managed by the MFP 10 does not include identification information of devices connected to devices in the G/O state.

In S16, the communication execution unit 44 transmits the prepared wireless settings to the portable device 50 using the NFC I/F 22. When the process of S16 is executed after the process of S15, the communication execution unit 44 transmits to the portable device 50 the wireless settings prepared at the stage (S15) when the spontaneous G/O mode is set. When the process of S16 is executed after the process of S13, the communication execution unit 44 transmits to the portable device 50 the wireless settings prepared at the stage when the WFD network in which the MFP 10 operates as the G/O state is established, using the NFC I/F 22.

Next, in S18, the communication execution unit 44 establishes a WFD connection between the MFP 10 and the mobile terminal 50 using the wireless LAN I/F 20. When the mobile terminal 50 receives the wireless settings of the MFP 10 operating in the G/O state from the MFP 10, it stores the received wireless settings in the work area 58. Therefore, the mobile terminal 50 performs wireless communication according to normal Wi-Fi. Next, the communication execution unit 44 performs wireless communication with the mobile terminal 50, including an authentication request, an authentication response, an association request, an association response, and a 4-way handshake. During the above wireless communication, various authentication processes are performed, such as authentication of the SSID, authentication method and encryption method, and password authentication. If all authentications are successful, a wireless connection is established between the MFP 10 and the mobile terminal 50.

If both the MFP 10 and the portable terminal 50 are in the device state, when a WFD connection is established between the MFP 10 and the portable terminal 50, one of the MFP 10 and the portable terminal 50 is determined as the G/O, and G/O negotiation is executed to determine the other of the MFP 10 and the portable terminal 50 as the client. However, at the stage when S16 is executed, since it is determined that the MFP 10 is in the G/O state, the communication execution unit 44 establishes a WFD connection with the portable terminal 50 without executing G/O negotiation.

In the process of S18, the communication execution unit 44 acquires the MAC address of the portable terminal 50 using the wireless LAN I/F 20. When the wireless connection is established, the control unit 30 further adds the MAC address of the portable terminal 50 to the management list. The MAC address of the portable terminal 50 is included in the NFC information. This allows the MFP 10 in the G/O state to communicate target data (print data, scan data, etc.) with the portable terminal 50 according to normal Wi-Fi. The target data includes data in the network layer, which is a layer higher than the physical layer of the OSI reference model. Therefore, the MFP 10 in the G/O state can perform wireless communication in the network layer with the portable terminal 50 in the client state.

Next, in S20, the communication execution unit 44 executes data communication processing with the portable terminal 50 via the wireless LAN I/F 20. The content of the data communication processing varies depending on the content of the processing execution instruction included in the NFC information. If the processing execution instruction is a print instruction, the communication execution unit 44 receives print data from the portable terminal 50 in the data communication processing. In this case, the control unit 30 causes the print execution unit 16 to execute a print processing using the received print data.

On the other hand, if the process execution instruction is a scan instruction, the control unit 30 causes the scan execution unit 18 to scan the document set in the scan execution unit 18 and generate scan data. Next, the communication execution unit 44 transmits the generated scan data to the mobile terminal 50.

Next, in S21, the communication execution unit 44 uses the wireless LAN I/F 20 to monitor whether a disconnection request to disconnect the mobile terminal 50 is received from the mobile terminal 50. If a disconnection request is not received after a predetermined period of time has elapsed (NO in S21), the process returns to S2. On the other hand, if a disconnection request is received from the mobile terminal 50 within a predetermined period of time after the data communication process of S20 is completed (YES in S21), the communication execution unit 44 disconnects the wireless connection with the mobile terminal 50. Specifically, the communication execution unit 44 erases the MAC address of the mobile terminal 50 from the management list. Next, in S22, the communication execution unit 44 determines whether the settings of the wireless LAN I/F 20 have been changed by the process of S9. Specifically, if the setting change information is stored in the memory 34, the communication execution unit 44 determines in S9 that the mode value indicating WFD=OFF mode has been changed to the mode value indicating WFD=ON mode (YES in S22) and proceeds to S23. On the other hand, if the setting change information is not stored in the memory 34, the communication execution unit 44 determines in S9 that the mode value indicating WFD=OFF mode has not been changed to the mode value indicating WFD=ON mode (NO in S22) and returns to S2.

In S23, the communication execution unit 44 determines whether an external device other than the mobile terminal 50 (e.g., PC 8) currently belongs to the WFD network newly established in S18. Specifically, the communication execution unit 44 determines that an external device currently belongs to the WFD network (YES in S23) when the management list contains identification information other than the identification information of the mobile terminal 50. In this case, the mode value is not changed and the process returns to S2. With this configuration, it is possible to prevent the MFP 10 from leaving the WFD network when an external device currently belongs to the WFD network.

On the other hand, if the management list does not include identification information other than that of the mobile terminal 50, the communication execution unit 44 determines that no external device currently belongs to the WFD network (NO in S23) and proceeds to S24. In S24, the communication execution unit 44 changes the mode value indicating WFD=ON mode to a mode value indicating WFD=OFF mode, and returns to S2. That is, in the communication process, if it is determined in S8 that the mode is WFD=OFF mode, the mode is changed from WFD=OFF mode to WFD=ON mode in order to temporarily perform wireless communication with the mobile terminal 50 using the wireless LAN I/F 20 via the WFD network. Then, when the mode is changed from WFD=ON mode to WFD=OFF mode in S25, the WFD network established in S18 disappears. With this configuration, if the mode value is changed from a mode value indicating WFD=OFF mode to a mode value indicating WFD=ON mode during communication processing, the mode value can be returned to the setting before the change.

(Effects of this embodiment)
The effects of this embodiment in the first to fifth situations will be described with reference to Figures 3 to 7. Each of Figures 3 to 7 shows a corresponding process in the communication process of Figure 2.

(First situation)
In the first situation shown in Fig. 3, the MFP 10 and the portable terminal 50 currently belong to the same WFD network or the same normal Wi-Fi network. In this situation, when NFC information is received from the portable terminal 50 using the NFC I/F 22, the MFP 10 determines in S4 that the MFP 10 currently belongs to the network (YES in S4). Next, in S6, the MFP 10 determines that the portable terminal 50 currently belongs to the network to which the MFP 10 currently belongs (YES in S6). In S7, the MFP 10 transmits setting change unnecessary information to the portable terminal 50 using the NFC I/F 22. When the portable terminal 50 receives the setting change unnecessary information, it transmits print data to the MFP 10 using the IP address included in the setting change unnecessary information and the wireless settings stored in the work area 58. The MFP 10 receives the print data (S20) using the wireless LAN I/F 20. When the MFP 10 receives the print data, it causes the print execution unit 16 to execute a print process.

In the sequence diagrams in this specification, wireless communication in which the MFP 10 uses the NFC I/F 22 (i.e., wireless communication according to the NFC method) and wireless communication in which the MFP 10 uses the wireless LAN I/F 20 (i.e., wireless communication according to the WFD method or normal Wi-Fi) are indicated by arrows. The arrows representing wireless communication using the wireless LAN I/F 20 are drawn thicker than the arrows representing wireless communication using the NFC I/F 22.

With this configuration, when the MFP 10 determines that the mobile device 50 currently belongs to the network to which the MFP 10 currently belongs, the MFP 10 and the mobile device 50 can appropriately communicate print data via the network to which they currently belong, without changing the wireless settings currently set in the MFP 10 and the mobile device 50.

(Second situation)
In the second situation shown in Fig. 4, the MFP 10 currently belongs to the WFD network. The MFP 10 operates in a G/O state in the WFD network. A PC 8 in a client state currently belongs to the WFD network. The portable terminal 50 does not currently belong to the wireless network to which the MFP 10 currently belongs. The portable terminal 50 may or may not currently belong to a wireless network other than the wireless network to which the MFP 10 currently belongs.

In this situation, when NFC information is received from the portable terminal 50 using the NFC I/F 22, in S4, the MFP 10 determines that the MFP 10 currently belongs to a network (YES in S4). Note that the NFC information includes the SSID and BSSID of a wireless network when the portable terminal 50 currently belongs to the wireless network, but does not include the SSID and BSSID of the wireless network when the portable terminal 50 does not currently belong to the wireless network. Next, in S6, the MFP 10 determines that the portable terminal 50 does not currently belong to the WFD network to which the MFP 10 currently belongs (YES in S6). In S12, the MFP 10 determines that the MFP 10 is in a G/O state (YES in S12). In this case, in S16, the MFP 10 transmits the wireless setting of the MFP 10 stored in the work area 38 and the IP address of the MFP 10 to the portable terminal 50 using the NFC I/F 22. When the portable terminal 50 receives the wireless setting, it stores the received wireless setting in the work area 58. Next, the MFP 10 and the portable terminal 50 establish a WFD connection (S18). This allows the portable terminal 50 to belong to the WFD network to which the MFP 10 currently belongs. The MFP 10 transmits the wireless setting including the authentication method and encryption method of the MFP 10 to the portable terminal 50 using the NFC I/F 22. According to this configuration, the portable terminal 50 can perform the authentication process according to the authentication method and encryption method received from the MFP 10, and does not need to perform a process of confirming which authentication method and encryption method should be used. This allows the MFP 10 and the mobile device 50 to establish a connection relatively quickly.

Then, the portable device 50 uses the wireless settings stored in the work area 58 and the IP address received in S16 to send print data to the MFP 10. The MFP 10 receives the print data using the wireless LAN I/F 20 (S20). When the MFP 10 receives the print data, it causes the print execution unit 16 to execute the print process. With this configuration, when the MFP 10 is operating in a G/O state in the WFD network, the MFP 10 can appropriately communicate print data with the portable device 50 via the WFD network to which the MFP 10 currently belongs.

(Third Situation)
5, the MFP 10 currently belongs to the WFD network. The MFP 10 operates in a client state in the WFD network. The PC 8 in a G/O state currently belongs to the WFD network, but the portable terminal 50 does not currently belong to the WFD network. The portable terminal 50 is in the same state as in the second state.

In this situation, when NFC information is received from the portable terminal 50 using the NFC I/F 22, in S4, the MFP 10 determines that the MFP 10 currently belongs to a network (YES in S4). Next, in S6, the MFP 10 determines that the portable terminal 50 does not currently belong to the WFD network to which the MFP 10 currently belongs (NO in S6). In S10, the MFP 10 determines that the MFP 10 is in a client state (YES in S10). In this case, in S14, the MFP 10 transmits communication NG information to the portable terminal 50 using the NFC I/F 22.

In this case, the MFP 10 does not transmit the wireless settings stored in the work area 38 to the portable terminal 50. With this configuration, it is not necessary to provide the wireless settings of the PC 8 operating in a G/O state in the WFD network to the portable terminal 50. This makes it possible to prevent the portable terminal 50 from joining the WFD network. Furthermore, by receiving communication NG information from the MFP 10, the portable terminal 50 can inform the user of the portable terminal 50 that the MFP 10 will not communicate the target data with the portable terminal 50.

(Fourth Situation)
6, the wireless LAN I/F 20 of the MFP 10 is set to WFD=ON mode, but the MFP 10 does not currently belong to a WFD network. That is, the MFP 10 is operating in a device state. The MFP 10 is also not currently belonging to a normal Wi-Fi network. The mobile terminal 50 is in the same state as in the second state.

In this situation, when NFC information is received from the mobile terminal 50 using the NFC I/F 22, the MFP 10 determines in S4 that the MFP 10 does not currently belong to a network (NO in S4). The MFP 10 also determines in S10 and S12 that the MFP 10 is neither in G/O status nor in client status (NO in both S10 and S12). In this case, in S15, the MFP 10 sets the MFP 10 to spontaneous G/O mode without performing G/O negotiation.

Next, in S16, the MFP 10 transmits the wireless settings of the MFP 10 stored in the work area 38 (i.e., the wireless settings generated when the MFP 10 is set to the spontaneous G/O mode in S15) and the IP address of the MFP 10 to the portable terminal 50 using the NFC I/F 22. When the portable terminal 50 receives the wireless settings, it stores the received wireless settings in the work area 58. Next, the MFP 10 and the portable terminal 50 establish a WFD connection (S18). This allows the portable terminal 50 to belong to the WFD network in which the MFP 10 is operating as the G/O state.

Then, the portable terminal 50 uses the wireless settings stored in the work area 58 and the IP address received in S16 to send print data to the MFP 10. The MFP 10 receives the print data using the wireless LAN I/F 20 (S20). When the MFP 10 receives the print data, it causes the print execution unit 16 to execute the print process. With this configuration, the MFP 10 can newly construct a WFD network in which the MFP 10 operates as a G/O in the WFD network. This allows the MFP 10 to appropriately communicate print data with the portable terminal 50 via the newly constructed WFD network. Furthermore, since the MFP 10 necessarily operates as a G/O in the newly constructed WFD network, it can determine the authentication method to be used in the WFD network, etc.

(Fifth Situation)
7, the wireless LAN I/F 20 of the MFP 10 is set to WFD=OFF mode. The MFP 10 is not currently part of a network. The mobile terminal 50 is in the same state as in the second state.

In this situation, when NFC information is received from the portable terminal 50 using the NFC I/F 22, the result is determined as NO in S4, as in the fourth situation. The MFP 10 determines in S8 that the WFD=OFF mode is set. In this case, the MFP 10 changes the WFD=OFF mode to the WFD=ON mode in S9. Next, the MFP 10 sets the MFP 10 to the spontaneous G/O mode in S15.

From here on, the process up to the printing process is the same as in the fourth situation. With this configuration, the same effects as in the fourth situation can be achieved. When the printing process is completed, the MFP 10 determines that no external devices currently belong to the newly constructed WFD network (NO in S23), and changes from WFD=ON mode to WFD=OFF mode. With this configuration, if no external devices belong to the WFD network after the printing data is communicated, it is possible to appropriately change from WFD=ON mode to WFD=OFF mode.

In this embodiment, the MFP 10 executes processing according to whether the MFP 10 currently belongs to the same network as the portable terminal 50, i.e., whether the MFP 10 is able to communicate with the portable terminal 50, thereby enabling the MFP 10 to appropriately execute wireless communication of target data with the portable terminal 50 at a relatively fast communication speed using the wireless LAN I/F 20. In addition, the MFP 10 can execute communication of target data with the portable terminal 50 via the WFD network without going through an access point different from that between the MFP 10 and the portable terminal 50.

Furthermore, when the MFP 10 is not able to communicate with the portable device 50 and the MFP 10 currently belongs to a WFD network, the MFP 10 can appropriately communicate the target data with the portable device 50 via the WFD network to which the MFP 10 currently belongs. Also, when the MFP 10 does not currently belong to a WFD network, the MFP 10 can appropriately communicate the target data with the portable device 50 via a newly constructed WFD network.

(Correspondence)
The MFP 10 is an example of a “communication device”, the NFC I/F 22 is an example of a “first type interface”, and the wireless LAN I/F 20 is an example of a “second type interface”. From the above description, the NFC I/F 22 (i.e., the “first type interface”) can be said to be an interface used for communication between the MFP 10 (i.e., the “communication device”) and the portable terminal 50 in order to execute communication using the wireless LAN I/F 20 (i.e., the “second type interface”).

AP6 is an example of an "access point." That is, an "access point" is a device that relays communication between a pair of devices that belong to a normal Wi-Fi network in the network to which the access point belongs, i.e., a normal Wi-Fi network.

NFC information is an example of "specific information." The G/O status is an example of a "parent station status," and the client status is an example of a "child station status." When S4 in FIG. 2 is determined to be YES, the WFD network to which MFP 10 belongs is an example of a "first target network," and the WFD network constructed by the processing of S15 to S18 in FIG. 2 is an example of a "second target network."

The case where YES is selected in S4 of FIG. 2 is an example of the "first case," and the case where NO is selected in S4 of FIG. 2 is an example of the "second case."

Second Example
The following describes the differences from the first embodiment. In this embodiment, when the portable terminal 50 currently belongs to a network, the portable terminal 50 transmits NFC information, which further includes a password, an authentication method, and an encryption method, as wireless settings stored in the work area 58, to the MFP 10.

In addition, in this embodiment, the communication process of FIG. 8 is executed instead of the communication process of FIG. 2. S2 to S24 of FIG. 8 are the same as the processes of S2 to S24 of FIG. 2. If the answer is NO in S4 (i.e., if the MFP 10 does not currently belong to a network), in S82, the judgment unit 42 judges whether or not the NFC information received from the portable terminal 52 via the NFC interface 22 includes wireless settings. If it is determined that the NFC information includes wireless settings (YES in S82), in S83, setting change unnecessary information is sent to the portable terminal 50 using the NFC I/F 22. Note that if the answer is NO in S4 (i.e., if the MFP 10 does not currently belong to a network), setting change unnecessary information including the MAC address of the MFP 10 is sent to the portable terminal 50 in S83. On the other hand, if S4 is YES and S6 is NO (i.e., MFP 10 currently belongs to a network, but MFP 10 and portable terminal 50 do not currently belong to the same network), in S83, setting change unnecessary information including the IP address of MFP 10 is sent to portable terminal 50. Next, in S84, communication execution unit 44 uses the wireless settings included in the NFC information to join the network to which portable terminal 50 belongs, and proceeds to S20.

On the other hand, if it is determined that the NFC information does not include wireless settings (NO in S82), proceed to S8.

(Effects of this embodiment)
The MFP 10 of the second embodiment can achieve the same effects as the MFP 10 of the first embodiment in situations 1 to 5. The effects of this embodiment in situation 6 will be described with reference to Fig. 9. Note that Fig. 9 shows the process corresponding to the communication process in Fig. 8.

(Sixth Situation)
9, the MFP 10 is not currently part of a network, whereas the mobile terminal 50 is currently part of a normal Wi-Fi network to which the AP 6 belongs.

In this situation, when NFC information is received from the portable device 50 via the NFC I/F 22, the MFP 10 determines that the MFP 10 currently belongs to a network (YES in S4). Next, in S82 of FIG. 8, the MFP 10 determines that the NFC information includes wireless settings for belonging to the network to which the portable device 50 currently belongs (YES in S82).

Next, in S83, the MFP 10 transmits information indicating that no setting changes are required to the portable terminal 50 using the NFC I/F 22. If the answer is NO in S4 (i.e., the MFP 10 is not currently part of a network), the MFP 10 transmits information indicating that no setting changes are required, including the MAC address of the MFP 10, to the portable terminal 50. If the answer is NO in S6 (i.e., the MFP 10 is currently part of a network, but the MFP 10 and the portable terminal 50 are not part of the same network), the MFP 10 transmits information indicating that no setting changes are required, including the IP address of the MFP 10, to the portable terminal 50.

The MFP 10 establishes a normal Wi-Fi connection with the AP 6 using the wireless settings included in the NFC information (S84). If the IP address of the MFP 10 is included in the setting change unnecessary information, the mobile terminal 50 specifies the IP address as the destination and sends print data to the MFP 10 via the AP 6 (S20). If the MAC address of the MFP 10 is included in the setting change unnecessary information, the mobile terminal 50 identifies the IP address of the MFP 10 according to RARP (short for Reverse Address Resolution Protocol), specifies the identified IP address as the destination, and sends print data to the MFP 10 via the AP 6 (S20).

With this configuration, when the MFP 10 and the mobile terminal 50 do not belong to the same network, the MFP 10 can properly communicate print data with the mobile terminal 50 via the network to which the mobile terminal 50 currently belongs.

(Correspondence)
The network to which the mobile terminal 50 belongs is an example of a “second target network.” The case of YES in S4 in Fig. 8 is an example of a “first case,” the case of NO in S4 in Fig. 8 is an example of a “second case,” and the case of NO in S4 in Fig. 8 and YES in S82 is an example of a “specific case.”

(Third Example)
Differences from the first embodiment will be described. In this embodiment, the communication process of FIG. 10 is executed instead of the communication process of FIG. 2. S2 to S12 and S15 to S24 of FIG. 10 are the same as the processes of S2 to S12 and S15 to S24 of FIG. 2. If NO in S8, that is, if the MFP 10 is not set to WFD=ON mode, in S76, the determination unit 42 determines whether the MFP 10 currently belongs to a normal Wi-Fi network. If information indicating that the MFP 10 currently belongs to a normal Wi-Fi network is stored in the work area 38, the determination unit 42 determines that the MFP 10 currently belongs to a normal Wi-Fi network (YES in S76), and proceeds to S80. On the other hand, if information indicating that the MFP 10 belongs to a normal Wi-Fi network is not stored in the work area 38, the judgment unit 42 determines that the MFP 10 does not currently belong to a normal Wi-Fi network (NO in S76), and proceeds to S9.

If S12 is YES, i.e., if the MFP 10 currently belongs to the WFD network and is operating in the WFD network as a G/O, the process proceeds to S13. In S16, the communication execution unit 44 transmits the wireless settings of the MFP 10 stored in the work area 38 to the mobile device 50 via the NFC I/F 22, and the process proceeds to S18. The wireless settings of the MFP 10 transmitted in S16 include a password.

Also, if the answer to S12 is NO, i.e., if the MFP 10 is operating in the device state, the determination unit 42 executes the process of S78. The process of S78 is the same as the process of S76. If the answer to S78 is NO, the process proceeds to S15, and if the answer to S78 is YES, the process proceeds to S80.

In S80, the communication execution unit 44 transmits the wireless settings for belonging to the normal Wi-Fi network stored in the work area 38, i.e., the wireless settings of the AP (e.g. AP6) other than the password, to the mobile terminal 50 via the NFC interface 22, and proceeds to S20. When the mobile terminal 50 receives the wireless settings of the AP, it prompts the user to specify a password. When the password is specified by the user, the mobile terminal 50 establishes a connection with the AP using the wireless settings received from the MFP 10 and the password specified by the user. This enables the mobile terminal 50 to wirelessly communicate with the MFP 10 via the AP. Note that if a connection between the mobile terminal 50 and the AP is not established, the MFP 10 cannot execute wireless communication with the mobile terminal 50. In this case, the control unit 30 returns to S2 without executing the processes of S20 to S24.

(Effects of this embodiment)
The MFP 10 of the third embodiment can achieve the same effects as the MFP 10 of the first embodiment in situations 1 to 5. The effects of this embodiment in situation 7 will be described with reference to Fig. 11. Note that Fig. 11 shows the process corresponding to the communication process in Fig. 10.

(Situation 7)
11, the MFP 10 currently belongs to a normal Wi-Fi network. The MFP 10 is connected to an AP 6 in the normal Wi-Fi network. The mobile terminal 50 is in the same state as in the second state.

In this situation, when NFC information is received from the mobile terminal 50 using the NFC I/F 22, in S4, the MFP 10 determines that the MFP 10 currently belongs to a network (i.e., a normal Wi-Fi network) (YES in S4). Next, in S6, the MFP 10 determines that the mobile terminal 50 does not currently belong to the normal Wi-Fi network to which the MFP 10 currently belongs (NO in S6). In S76, the MFP 10 determines that it currently belongs to a normal Wi-Fi network (YES in S76). In this case, in S80, the MFP 10 transmits to the mobile terminal 50 the wireless settings of the AP 6 stored in the work area 38 that do not include a password, and the IP address of the MFP 10. With this configuration, it is not necessary to provide a password to the mobile terminal 50 and the user. As a result, if the mobile terminal 50 and the user do not know the password for joining the normal Wi-Fi network in which the AP 6 is used, the mobile terminal 50 can be prevented from joining the normal Wi-Fi network.

When the portable terminal 50 receives the wireless settings, it receives the wireless settings and prompts the user to specify a password, similar to the tenth situation. Next, when the password is specified by the user, the portable terminal 50 establishes a normal Wi-Fi connection with the AP 6. This allows the portable terminal 50 to belong to the normal Wi-Fi network to which the MFP 10 currently belongs. The portable terminal 50 can transmit print data to the MFP 10 via the AP 6. When the portable terminal 50 belongs to the normal Wi-Fi network, it transmits print data to the MFP 10 by performing wireless communication via the AP 6 using the wireless settings stored in the work area 58 and the IP address of the MFP 10 received in S80.

Although not shown, even if the MFP 10 is currently operating in a device state (Yes in S8, No in S10 and S12) and belongs to a normal Wi-Fi network (Yes in S78), the MFP 10 transmits the wireless settings of the AP stored in the work area 38 that do not include a password to the mobile device 50.

With this configuration, when the MFP 10 does not belong to the same network as the mobile device 50, the MFP 10 can properly communicate print data with the mobile device 50 via the normal Wi-Fi network to which the MFP 10 currently belongs.

(Correspondence)
When it is determined as YES in S4 in Fig. 10, the non-WFD network to which the MFP 10 belongs is an example of a "first target network". When it is determined as YES in S4 in Fig. 10, it is an example of a "first case", and when it is determined as NO in S4 in Fig. 10, it is an example of a "second case".

Although specific examples of the present invention have been described above in detail, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples given above. Modifications of the above examples are listed below.

(Modification)
(1) In the first to third embodiments, when the MFP 10 receives NFC information (YES in S2), it determines whether it currently belongs to a network (S4), and if it is determined that it currently belongs to a network (YES in S4), it determines whether the MFP 10 and the portable terminal 50 currently belong to the same network (S6). However, the process of S6 may be omitted. That is, in the first and third embodiments, when the MFP 10 receives NFC information (YES in S2), it determines whether it currently belongs to a network (S4), and if it is determined that it currently belongs to a network (YES in S4), it may proceed to the process of S8 and subsequent steps. Also, in the second embodiment, when it is determined that the MFP 10 currently belongs to a network (YES in S4), it may proceed to the process of S82 and subsequent steps.

(2) The "communication device" is not limited to a multi-function device, but may be other equipment equipped with a first type interface and a second type interface (e.g., a printer, a fax machine, a copier, a scanner, etc.).

(3) The MFP 10 may store an AP program for functioning as an access point. When the control unit 30 starts the AP program, the control unit 30 may store predetermined wireless settings in the work area 38. In S4 of FIG. 2, the determination unit 42 may determine that the MFP 10 is currently participating in a network (non-WFD network) when the AP program is started. In this modified example, the normal Wi-Fi network that is established while the MFP 10 is functioning as an access point is an example of a "first target network."

(4) For example, in S15 of FIG. 2, the communication execution unit 44 may start an AP program instead of setting the MFP 10 to the spontaneous G/O mode. Next, the communication execution unit 44 may transmit the wireless settings stored in the work area 38 to the portable terminal 50. Then, the communication execution unit 44 and the portable terminal 50 may establish a connection using the wireless settings stored in advance in the work area 38. In this case, the MFP 10 may establish a normal Wi-Fi connection with the portable terminal 50, and the MFP 10 may also build a normal Wi-Fi network. In this modified example, the normal Wi-Fi network built in a state in which the MFP 10 functions as an access point is an example of a "second target network."

(5) The combination of the "first type interface" and the "second type interface" is not limited to the combination of an NFC I/F and a wireless LAN I/F. For example, when a wireless LAN I/F is adopted as the "second type interface", the "first type interface" may be an interface for performing infrared communication, an interface for performing Bluetooth (registered trademark), or an interface for performing Transfer Jet. Furthermore, when an NFC I/F is adopted as the "first type interface", the "second type interface" may be an interface for performing wired communication, or an interface for performing Bluetooth (registered trademark). Generally speaking, it is sufficient that the communication speed of communication via the second type interface is faster than the communication speed of communication via the first type interface.

(6) The "first type interface" and the "second type interface" may be two physical interfaces (i.e., two separate chips) as in the above example, or may be one physical interface (i.e., one chip that realizes two types of communication).

(7) In each of the above embodiments, the interface for performing wireless communication according to the WFD method and the interface for performing wireless communication according to normal Wi-Fi were one physical interface (wireless LAN I/F 20), but they may be multiple physical interfaces (i.e., two separate IC chips). In this modified example, the multiple interfaces are an example of a "second type interface."

(8) In each of the above embodiments, in S15, the communication execution unit 44 sets the MFP 10 to the spontaneous G/O mode. However, when the mobile terminal 50 is capable of performing wireless communication according to WFD, the communication execution unit 44 may transmit WFD connection start information indicating the start of a WFD connection to the mobile terminal 50 via the NFC interface 22. A wireless connection method of WPS (abbreviation of Wi-Fi Protected Setup) may be used as a method for performing a wireless connection of WFD. The wireless connection method of WPS includes a PBC (abbreviation of Push Button Configuration) method and a PIN (abbreviation of Personal Identification Number) code method. In this modification, the PBC code method is described, but the technology of this modification is also applicable to the PIN code method. The WFD connection start information may include information indicating that the PBC code method is used as a method for performing a wireless connection of the WFD method. The WFD connection start information may further include the device ID of the MFP 10 (e.g., MAC address, serial number, etc.).

When the WFD connection start information is received, the mobile terminal 50 may determine whether the wireless LAN I/F setting of the mobile terminal 50 is a setting that allows wireless communication according to the WFD method. If the wireless LAN I/F setting is a setting that allows wireless communication according to the WFD method, the mobile terminal 50 may maintain the wireless LAN I/F setting, and if the wireless LAN I/F setting is not a setting that allows wireless communication according to the WFD method, the mobile terminal 50 may change the wireless LAN I/F setting to a setting that allows wireless communication according to the WFD method.

Then, the communication execution unit 44 may search for the mobile terminal 50. Specifically, the communication execution unit 44 may sequentially execute a scan process, a listen process, and a search process. The scan process is a process for searching for devices in a G/O state that exist around the MFP 10. Specifically, in the scan process, the communication execution unit 44 may sequentially use 13 channels, 1ch to 13ch, to wirelessly transmit a probe request signal. Note that this probe request signal may include P2P (Peer 2 Peer) information indicating that the MFP 10 is capable of executing the WFD function.

For example, if a WFD-compatible device in a G/O state (hereinafter referred to as a "specific G/O device") is present around the MFP 10, the specific G/O device may have previously determined to use one of channels 1ch to 13ch. Therefore, the specific G/O device may wirelessly receive a Probe Request signal from the MFP 10. In this case, the specific G/O device may wirelessly transmit a Probe Response signal to the MFP 10. This Probe Response signal may include P2P information indicating that the specific G/O device is capable of executing the WFD function and information indicating that the specific G/O device is in a G/O state. As a result, the communication execution unit 44 can find the specific G/O device. The above-mentioned probe response signal may further include the device name of the specific G/O device, information indicating the model of the specific G/O device (e.g., a mobile terminal, a PC, etc.), and the MAC address of the specific G/O device. As a result, the communication execution unit 44 can obtain information about the specific G/O device.

When the device ID (e.g., MAC address, serial number, etc.) of a specific G/O device included in the Probe Response signal matches the device ID of the mobile terminal 50 included in the NFC information, the communication execution unit 44 can identify that the specific G/O device is the mobile terminal 50. In other words, when the mobile terminal 50 currently belongs to a WFD network and is operating in a G/O state in the WFD network, the communication execution unit 44 can discover the mobile terminal 50 by a scan process.

For example, when a WFD-compatible device in a device state (hereinafter referred to as a "specific device") is present around the MFP 10, the specific device may have previously determined to use one of channels 1ch, 6ch, and 11ch. Therefore, the specific device may also wirelessly receive a Probe Request signal from the MFP 10. In this case, the specific device may wirelessly transmit a Probe Response signal to the MFP 10. However, this Probe Response signal may include information indicating that the device is in a device state, and may not include information indicating that the device is in a G/O state. Furthermore, even if a device in a client state wirelessly receives a Probe Request signal from the MFP 10, it may not wirelessly transmit a Probe Response signal to the MFP 10. The communication execution unit 44 can discover the mobile terminal 50 in the scan process whether the mobile terminal 50 is in a G/O state or a device state.

The Listen process is a process for responding to a Probe Request signal. A specific device can wirelessly transmit a Probe Request signal in a Search process described below. That is, when the current state of the mobile terminal 50 is a device state, the mobile terminal 50 may wirelessly transmit a Probe Request signal periodically. This Probe Request signal may include the device ID of the mobile terminal 50 (e.g., a MAC address, a serial number, etc.).

When the device ID of the specific device included in the Probe Request signal matches the device ID of the mobile terminal 50 included in the NFC information, the communication execution unit 44 can identify that the specific device is the mobile terminal 50. That is, when the mobile terminal 50 is operating in a device state, the communication execution unit 44 can discover the mobile terminal 50 by a Listen process. When the communication execution unit 44 receives a Probe Request signal from the mobile terminal 50, it may wirelessly transmit a Probe Response signal.

In the search process, the communication execution unit 44 may wirelessly transmit a Probe Request signal sequentially using three channels, 1ch, 6ch, and 11ch. As a result, the communication execution unit 44 may wirelessly receive a Probe Response signal from a specific device. This Probe Response signal may include P2P information indicating that the specific device is capable of executing the WFD function, information indicating that the specific device is in a device state, and a device ID (e.g., a MAC address, a serial number, etc.) of the specific device. When the current state of the portable terminal 50 is in a device state, the portable terminal 50 may wirelessly transmit a Probe Response signal in response to the Probe Request signal transmitted from the MFP 10.

When the device ID of the specific device included in the Probe Response signal matches the device ID of the mobile terminal 50 included in the NFC information, the communication execution unit 44 can identify that the specific device is the mobile terminal 50. In other words, when the mobile terminal 50 currently belongs to a WFD network and is operating in a device state in the WFD network, the communication execution unit 44 can discover the mobile terminal 50 by a Search process.

When the portable terminal 50 is discovered, the MFP 10 may use the wireless LAN I/F 20 to perform G/O negotiation with the portable terminal 50 and determine that either the MFP 10 or the portable terminal 50 will operate in a G/O state, and that the other device will operate in a client state.

Next, the communication execution unit 44 may establish a connection between the MFP 10 and the mobile terminal 50 according to WPS. Specifically, when the current state of the MFP 10 is the G/O state and the current state of the mobile terminal 50 is the client state (YES in S22), the communication execution unit 44 may generate wireless settings (SSID, authentication method, encryption method, password, etc.) required to establish a wireless connection and wirelessly transmit them to the mobile terminal 50. The authentication method and encryption method may be predetermined. The communication execution unit 44 may generate a password when generating the wireless settings. The SSID may be generated by the communication execution unit 44 or may be predetermined. By transmitting the wireless settings to the mobile terminal 50, the MFP 10 and the mobile terminal 50 can use the same wireless settings. That is, the MFP 10 and the portable terminal 50 may use the wireless settings to perform wireless communication including Authentication Request, Authentication Response, Association Request, Association Response, and 4-way handshake. During this process, the MFP 10 and the portable terminal 50 may perform various authentication processes such as SSID authentication, authentication method and encryption method authentication, and password authentication. If all authentications are successful, a wireless connection may be established between the MFP 10 and the portable terminal 50. As a result, the MFP 10 and the portable terminal 50 may belong to the same WFD network.

On the other hand, when the current state of the MFP 10 is the client state and the current state of the target device is the G/O state, the communication execution unit 44 may execute WPS negotiation for the client state. Specifically, the portable terminal 50 may generate wireless settings (SSID, authentication method, encryption method, password, etc.) required to establish a wireless connection and transmit them wirelessly to the MFP 10. As a result, the communication execution unit 44 may wirelessly receive the wireless settings from the portable terminal 50. Subsequent processing (communication processing such as Authentication Request) is the same as WPS negotiation for the G/O state. As a result, the MFP 10 and the portable terminal 50 may belong to the same WFD network. As a result, the MFP 10 in the client state can execute wireless communication of the target data (print data, etc.) with the portable terminal 50 in the G/O state. In this variation, G/O negotiation and WPS negotiation are examples of "specific processing."

(9) In each of the above embodiments, each of the units 40 to 46 is implemented by software, but at least one of the units 40 to 46 may be implemented by hardware such as a logic circuit.

The technical elements described in this specification or drawings have technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. The technologies illustrated in this specification or drawings achieve multiple objectives simultaneously, and achieving any one of those objectives is itself technically useful.

2: Communication system, 6: AP, 8: PC, 10: MFP, 20: Wireless LAN interface, 22: NFC interface, 30: Control unit, 50: Mobile terminal

Claims (8)

A communication device, comprising:
a first type of interface for performing wireless communication with a mobile terminal;
a second type interface for performing wireless communication with the mobile terminal, the second type interface having a communication speed faster than a communication speed of the wireless communication using the second type interface ;
a transmission unit that transmits predetermined information to the mobile terminal via the first type interface, wherein when the communication device operates as a master station of a first wireless network for performing wireless communication using the second type interface, the predetermined information includes a first wireless setting for the mobile terminal to belong to the first wireless network, and when the communication device does not operate as the master station, the predetermined information includes a second wireless setting for the mobile terminal to belong to a second wireless network formed by an access point different from that of the communication device and the mobile terminal;
a communication execution unit that executes wireless communication of target data with the portable terminal via either the first wireless network or the second wireless network ;
A communication device comprising: The communication device according to claim 1 , wherein the predetermined information includes the second wireless setting when the communication device is not operating as the master station and when the communication device currently belongs to the second wireless network. The first wireless setting includes a password;
The communication device according to claim 1 , wherein the second wireless setting does not include a password. The communication device according to claim 1 , wherein the predetermined information includes the second wireless setting when the communication device is not operating as either the master station or the slave station. The communication device according to claim 1 , wherein the first type interface is an interface for performing NFC. The communication device according to claim 1 , wherein the first type interface is an interface for implementing Bluetooth. The communication device according to claim 1 , wherein the communication device is one of a printer and a scanner. A computer program for a communication device including a first type interface for communicating with a mobile terminal and a second type interface for communicating with the mobile terminal, the second type interface having a communication speed faster than a communication speed of the first type interface,
The computer mounted on the communication device performs the following processes:
a transmission process for transmitting predetermined information to the mobile terminal via the first type interface, wherein when the communication device operates as a master station of a first wireless network for performing wireless communication using the second type interface, the predetermined information includes a first wireless setting for the mobile terminal to belong to the first wireless network, and when the communication device does not operate as the master station, the predetermined information includes a second wireless setting for the mobile terminal to belong to a second wireless network formed by an access point different from that of the communication device and the mobile terminal;
A computer program that causes the mobile terminal to execute a communication execution process for executing wireless communication of target data via either the first wireless network or the second wireless network .

Images