JP6304323B2 - Function execution device - Google Patents

Description

  The technology disclosed in this specification relates to a function execution device.

Patent Documents 1 and 2 disclose a technique for two wireless communication apparatuses to perform wireless communication. In Patent Documents 1 and 2, the two communication devices are short-range wireless communication (that is, NFC (Near Field
Communication of wireless setting is performed according to (abbreviation of communication) wireless communication according to the method). The above wireless setting is a setting for executing wireless communication according to a communication method (for example, IEEE 802.11a, 802.11b) different from the NFC method. Thus, the two communication devices can execute wireless communication according to the wireless setting.

JP 2007-166538 A JP 2011-146991 A

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

  The present specification provides a function execution device capable of executing an appropriate operation.

  The technology disclosed by this specification is a function execution device. The function execution device includes a first type interface for executing communication with the mobile terminal, a second type interface for executing communication with the mobile terminal, and a control unit. The communication speed of communication through the second type interface is faster than the communication speed of communication through the first type interface. The control unit includes a reception unit, a state determination unit, a change unit, and a function execution unit. The receiving unit receives first information including an execution request for a specific function from the portable terminal via the first type interface. The specific function includes a communication process for communicating the target data with the mobile terminal. When the first information is received, the state determination unit determines whether the state of the function execution device is a non-error state in which the specific function can be executed or an error state in which the specific function cannot be executed. . The changing unit changes the interface for communicating with the portable terminal from the first type interface to the second type interface when it is determined that the function execution device is in a non-error state. Execute the process. The changing unit does not execute the changing process when it is determined that the state of the function execution device is an error state. The function execution unit executes a specific function including a communication process via the second type interface when the change process is executed.

According to the above configuration, when the first information is received from the mobile terminal via the first type interface, the function execution device determines whether the function execution device is in a non-error state. It is judged whether it is in a state. When it is determined that the function execution device is in a non-error state, the function execution device appropriately communicates the target data with the portable terminal via the second type interface in order to execute the change process. obtain. As a result, the function execution device can appropriately execute a specific function. On the other hand, the function execution device does not execute the change process when it is determined that the state of the function execution device is an error state. Accordingly, it is possible to suppress the occurrence of the event that the change process is executed even though the state of the function execution device is an error state in which a specific function cannot be executed. As a result, the processing load of the function execution device can be reduced. Thus, the function execution device can execute an appropriate operation according to the determination result regarding the state of the function execution device.

  The control unit further includes a storage control unit that stores permission information indicating whether or not the mobile terminal can use a specific function in the memory of the function execution device, and when the first information is received. A usage determining unit that determines whether or not the mobile terminal can use a specific function by using the permission information in the memory. The changing unit executes the changing process when the state of the function execution device is determined to be a non-error state and the mobile terminal is determined to be able to use a specific function, and the mobile terminal is specified. If it is determined that the above function cannot be used, the change process need not be executed. According to this configuration, even if the function execution device is in a non-error state, the function execution device does not execute the change process when it is determined that the specific function cannot be used by the mobile terminal. . Accordingly, it is possible to suppress the occurrence of the event that the change process is executed even though the mobile terminal cannot use the specific function. As a result, the processing load of the function execution device can be reduced. In this manner, the function execution device can execute an appropriate operation according to the determination result regarding the use of the function by the mobile terminal.

  The first information may further include related information related to the wireless network to which the mobile terminal currently belongs. The changing unit may execute the changing process using the relationship information. According to this configuration, the function execution device can appropriately execute the change process using the relationship information.

  The control unit further displays impossible information indicating that the specific function cannot be executed via the first type interface when the state of the function execution device is determined to be an error state. You may provide the transmission part which transmits to a portable terminal. According to this configuration, the function execution device can appropriately notify the mobile terminal that the specific function cannot be executed.

  The specific function may be a print function including a communication process for receiving print data that is target data from the portable terminal and a print process according to the print data. The receiving unit may further receive second information including a print function execution request from the portable terminal via the first type interface after the impossible information is transmitted to the portable terminal. When the second information is received, (A) the changing unit executes the changing process, and (B) the function executing unit receives the second type interface from the portable terminal when the changing process is executed. The communication processing for receiving the print data may be executed via the printer, and the print data may be stored in the memory of the function execution device. The function execution unit further executes print processing according to the print data in the memory when the state of the function execution device changes from an error state to a non-error state after the second information is received. Also good. According to this configuration, when the second information is received from the portable terminal via the first type interface, the function execution device executes the change process and receives the change information via the second type interface. Receive print data. At this time, since the state of the function execution device is an error state, the function execution device stores the print data in the memory without executing the print processing. Then, when the function execution device changes from the error state to the non-error state, the function execution device executes print processing according to the print data in the memory. Therefore, the function execution apparatus can appropriately execute the print function including the print data communication process and the print process even in an error state when the first information is received.

The second information may further include size information indicating the data size of the print data. The control unit further includes a size determination unit that determines whether the print data can be stored in the memory using the size information and the free space of the memory when the second information is received. You may have. When the second information is received, the changing unit executes the changing process when it is determined that (A1) the print data can be stored in the memory, and (A2) the print data is not stored in the memory. If it is determined that it is possible, the change process need not be executed. According to this configuration, the function execution device does not execute the change process when it is determined that the print data cannot be stored in the memory. Thereby, it is possible to suppress the occurrence of the event that the change process is executed even though the print data cannot be stored in the memory. As a result, the processing load of the function execution device can be reduced.

  The specific function may be a scan function including scan processing for executing scan of a document to generate scan data and communication processing for transmitting scan data as target data to the portable terminal. The receiving unit may further receive third information including a scan function execution request from the portable terminal via the first type interface after the impossible information is transmitted to the portable terminal. The function execution unit may further execute the scan function when the state of the function execution device changes from the error state to the non-error state after the third information is received. According to this configuration, when the third information is received from the portable terminal via the first type interface, the function execution device executes the scan function when the error information changes to the non-error state. Therefore, the function execution apparatus can appropriately execute the scan function including the scan process and the scan data communication process even when the first information is received in an error state.

  When the wireless network to which the mobile terminal currently belongs and the wireless network to which the function execution apparatus currently belongs are the same, the receiving unit receives the third from the mobile terminal via the first type interface. Information may be received. According to this configuration, even if the function execution device is in an error state when receiving the first information, it can receive the third information and appropriately execute the scan function.

  The function execution apparatus includes a plurality of states including a master station state that functions as a master station of a wireless network, a slave station state that functions as a slave station of the wireless network, and a device state different from the master station state and the slave station state. May be selectively operable in any of the states. The second type interface may be an interface for executing a communication process by a function execution device operating in either the master station state or the slave station state.

  In the specific wireless network to which the function execution device currently belongs, when the function execution device is operating in the master station state, the change processing is performed by the slave station device operating in the slave station state in the specific wireless network. The number of devices may be included to determine whether the number is less than a predetermined value. The changing unit continuously executes the changing process when it is determined that the number of slave station devices is less than the predetermined value, and when the number of slave station devices is determined to be equal to or greater than the predetermined value. The change process may not be executed continuously. According to this configuration, the function execution device does not continue the change process when the number of slave station devices is equal to or greater than a predetermined value. As a result, the change process continues even though the mobile terminal cannot newly join the specific wireless network due to the large number of slave station devices belonging to the specific wireless network. It is possible to suppress the occurrence of an event of being executed. As a result, the processing load of the function execution device can be reduced.

  The specific function may be a print function including a communication process for receiving print data that is target data from the portable terminal and a print process according to the print data. The state determination unit is at least one of the remaining amount of consumables for executing the printing function, the remaining amount of the printing medium for executing the printing function, and the state of the hardware for executing the printing function. May be used to determine whether the function execution device is in a non-error state or an error state. According to this configuration, the function execution device can appropriately execute the determination regarding the state of the function execution device.

  The specific function may be a scan function including scan processing for executing scan of a document to generate scan data and communication processing for transmitting scan data as target data to the portable terminal. The state determination unit may determine whether the state of the function execution apparatus is a non-error state or an error state using a hardware state for executing the scan function. According to this configuration, the function execution device can appropriately execute the determination regarding the state of the function execution device.

  The present specification further discloses a function execution device capable of executing a plurality of functions including a first function and a second function. The control unit of the function execution device includes a storage control unit, a reception unit, a usage determination unit, a change unit, and a function execution unit. The storage control unit stores, for each of the first function and the second function, permission information indicating whether or not the mobile terminal can use the function in the memory of the function execution device. The receiving unit receives first information including an execution request for a specific function from the portable terminal via the first type interface. The specific function includes a communication process for communicating the target data with the mobile terminal. When the first information is received, the usage determining unit determines whether the mobile terminal can use the specific function by using the permission information in the memory. In the first case where the specific function is the first function and the mobile terminal is determined to be able to use the first function, the changing unit sets the interface for communicating with the mobile terminal to A change process for changing from one type of interface to a second type of interface is executed. The changing unit does not execute the changing process in a second case where the specific function is the second function and the mobile terminal is determined to be unable to use the second function. The function execution unit executes a specific function including a communication process via the second type interface when the change process is executed.

  According to the above configuration, the function execution device determines whether or not the mobile terminal can use a specific function when the first information is received from the mobile terminal via the first type interface. to decide. In the first case where the specific function is the first function and the mobile terminal is determined to be able to use the first function, the function execution device executes the change process in the second case. The target data can be appropriately communicated with the portable terminal through the kind of interface. As a result, the function execution device can appropriately execute the specific function (that is, the first function). On the other hand, the function execution device does not execute the change process in the second case where the specific function is the second function and the mobile terminal is determined to be unable to use the second function. Thereby, although the portable terminal cannot use a specific function (that is, the second function), it is possible to suppress the occurrence of the event that the change process is executed. As a result, the processing load of the function execution device can be reduced. In this manner, the function execution device can execute an appropriate operation according to the determination result regarding the use of the function by the mobile terminal.

  Note that a control method, a computer program, and a computer-readable recording medium storing the computer program for realizing the function execution device are also novel and useful. A communication system including the function execution device and the mobile terminal is also new and useful.

1 shows a configuration of a communication system. 6 shows a flowchart of MFP processing. The flowchart of a normal request process is shown. The flowchart of a re-request process is shown. The flowchart of a change process is shown. A sequence diagram of case A is shown. The sequence diagram of case X1 is shown. The sequence diagram of case X2 is shown. The sequence diagram of case X3 is shown. The sequence diagram of case X4 is shown. A sequence diagram of case B is shown. A sequence diagram of case C is shown. A sequence diagram of case D is shown.

(Configuration of communication system 2)
As shown in FIG. 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, and an access point (hereinafter referred to as “
(Referred to as “AP”) 6 and a PC 8. The MFP 10 and the portable terminal 50 can execute short-range wireless communication. Near field communication is wireless communication according to the NFC system. In the present embodiment, NFC wireless communication is executed based on the international standard of ISO / IEC21481 or ISO / IEC18092.

Further, the PC 8, the MFP 10, and the portable terminal 50 can each perform wireless communication in accordance with a Wi-Fi Direct method (hereinafter referred to as “WFD method”) described later. In the WFD system, the IEEE standard of IEEE (The Institute of Electrical and Electronics Engineers, Inc.) and a standard equivalent thereto (for example, 802.11a, 11b).
, 11g, 11n, etc.) wireless communication is executed. The NFC system and the WFD system are different in wireless communication system (that is, wireless communication standard). The communication speed of WFD wireless communication is faster than the communication speed of NFC wireless communication.

  For example, the MFP 10 can establish a WFD network by establishing a connection (hereinafter referred to as “WFD connection”) with the mobile terminal 50 in accordance with the WFD method. Similarly, the MFP 10 can establish a WFD network by establishing a WFD connection with the PC 8.

  The PC 8, the MFP 10, and the portable terminal 50 can further perform wireless communication according to normal Wi-Fi, which is different from wireless communication according to the WFD scheme. Generally speaking, the normal wireless communication in accordance with Wi-Fi is a wireless communication in which AP6 is used, and the wireless communication in accordance with the WFD method is a wireless communication in which AP6 is not used. For example, the MFP 10 can belong to the normal Wi-Fi network by establishing a connection with the AP 6 (hereinafter referred to as “normal Wi-Fi connection”) according to the normal Wi-Fi. The MFP 10 can execute wireless communication with another device (for example, the PC 8 or the portable terminal 50) belonging to the normal Wi-Fi network via the AP 6. Further, the NFC scheme and normal Wi-Fi are different in wireless communication scheme (that is, wireless communication standard). Further, the communication speed of normal Wi-Fi wireless communication is faster than the communication speed of NFC wireless communication.

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

As described above, the PC 8, the MFP 10, and the portable terminal 50 can each perform wireless communication in accordance with the WFD method. Hereinafter, a device capable of performing wireless communication in accordance with the WFD method is referred to as “WFD-compatible device”. In the WFD standard, three states of a Group Owner state (hereinafter referred to as “G / O state”), a client state, and a device state are defined as states of a WFD-compatible device. The WFD compatible device can selectively operate in one of the above three states.

  A WFD network is configured by the devices in the G / O state and the devices in the client state. In the WFD network, there can be only one device in the G / O state, but there can be one or more devices in the client state. A device in the G / O state manages one or more devices in the client state. More specifically, the G / O state device generates a management list in which identification information (that is, MAC address) of each of one or more client state devices is described. When the device in the G / O state newly belongs to the WFD network, the device in the G / O state adds the identification information of the device to the management list, and when the device in the client state leaves the WFD network, the identification information of the device is added. Clear from management list.

  A device in the G / O state is registered with a device registered in the management list, that is, a device in a client state (that is, a device belonging to the WFD network) with target data (for example, in the network layer of the OSI reference model). Wireless communication of data including information (print data, scan data, etc.) can be performed. However, a device in the G / O state is connected to an unregistered device that is not registered in the management list, so that the unregistered device participates in the WFD network (for example, data that does not include network layer information ( Wireless communication of physical layer data such as a probe request signal and a probe response signal can be performed, but wireless communication of the above-described target data cannot be performed. Print data can be received wirelessly from the mobile terminal 50 registered in the client (that is, the mobile terminal 50 in the client state), but cannot be received wirelessly from a device not registered in the management list.

  In addition, a G / O state device can relay wireless communication of target data (print data, scan data, etc.) between a plurality of client state devices. For example, when the portable terminal 50 in the client state should wirelessly transmit print data to another printer in the client state, the portable 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 print data from the portable terminal 50 and transmits the print data wirelessly to the other printer. That is, a device in the G / O state can execute the function of the AP of the normal Wi-Fi network.

  Note that a WFD compatible device that does not belong to the WFD network (that is, a device that is not registered in the management list) is a device in a device state. The device in the device state can execute wireless communication of data (physical layer data such as a probe request signal and a probe response signal) for participating in the WFD network, but the target data (print data) is transmitted via the WFD network. Wireless communication of scan data, etc.).

  In the following description, a device that cannot execute wireless communication in accordance with the WFD scheme but can normally execute wireless communication in accordance with Wi-Fi is referred to as “a WFD-incompatible device”. The “non-WFD compatible device” can also be called a “legacy device”. A device that does not support WFD cannot operate in the G / O state. A device in the G / O state can describe identification information of a device that does not support WFD 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 referred to as “I / F”) 20, an NFC I / I F22 and the control part 30 are provided. The operation unit 12 includes a plurality of keys. The user operates the operation unit 12 to give various instructions to the MFP 10.
Can be entered. The display unit 14 is a display for displaying various information. The print execution unit 16 is a printing mechanism such as an inkjet method or a laser method. The scan execution unit 18 is a scan mechanism such as a CCD or CIS.

  The wireless LAN I / F 20 is an interface for the control unit 30 to perform wireless communication in accordance with the WFD method and wireless communication in accordance with normal Wi-Fi. The wireless LAN I / F 20 is physically one interface. However, the wireless LAN I / F 20 includes a MAC address used in wireless communication in accordance with the WFD method (hereinafter referred to as “MAC address for WFD”) and a MAC address used in wireless communication in accordance with normal Wi-Fi. Both addresses (hereinafter referred to as “normal Wi-Fi MAC addresses”) are assigned. More specifically, a normal Wi-Fi MAC address is pre-assigned to the wireless LAN I / F 20. The control unit 30 generates a WFD MAC address using the normal Wi-Fi MAC address, and assigns the WFD MAC address 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 execute both wireless communication in accordance with the WFD method and wireless communication in accordance with normal Wi-Fi via the wireless LAN I / F 20. As a result, a situation can be established in which the MFP 10 belongs to the WFD network and also belongs to the normal Wi-Fi network. In the modification, the interface for executing wireless communication in accordance with the WFD method and the interface for executing wireless communication in accordance with normal Wi-Fi are configured by physically different chips. Also good.

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

  The user operates the operation unit 12 to express the setting of the wireless LAN I / F 20 as a setting capable of performing wireless communication according to the WFD method (hereinafter, “WFDI / F setting is ON”). ) And a setting incapable of performing wireless communication in accordance with the WFD method (hereinafter referred to as “WFDI / F setting is OFF”). The control unit 30 stores a value (ON or OFF) indicating the WFDI / F setting set by the user in the memory 34.

  The NFC I / F 22 is an interface for the control unit 30 to execute NFC wireless communication. The W-Fi I / F 20 and the NFC I / F 22 are configured by physically different chips.

Note that the communication speed of wireless communication via the wireless LAN I / F 20 (for example, the maximum communication speed is 11 to 600 Mbps) is the communication speed of wireless communication via the NFC I / F 22 (for example, the maximum communication speed is 106 to 424 kbps). ) Faster than. Furthermore, the frequency of the carrier wave (for example, 2.4 GHz band and 5.0 GHz band) in the wireless communication via the wireless LAN I / F 20 is the frequency of the carrier wave (for example, 13.56 MHz band) in the wireless communication via the NFC I / F 22. Is different. When the distance between the MFP 10 and the portable terminal 50 is about 10 cm or less, the control unit 30 can execute NFC wireless communication with the portable terminal 50 via the NFC I / F 22. On the other hand, regardless of whether the distance between the MFP 10 and the portable terminal 50 is 10 cm or less or 10 cm or more (for example, about 100 m at the maximum), the control unit 30 uses the WFD method via the wireless LAN I / F 20. Wireless communication in accordance with the mobile terminal 50 and wireless communication in accordance with normal Wi-Fi. That is, the maximum distance that the MFP 10 can execute wireless communication with a communication destination device (for example, the portable terminal 50) via the wireless LAN I / F 20 is the maximum distance that the MFP 10 can communicate with the communication destination device via the NFC I / F 22. It is larger than the maximum distance at which wireless communication can be performed.

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

  The memory 34 includes a ROM, a RAM, a hard disk, and the like. The memory 34 stores the above program executed by the CPU 32. When the MFP 10 currently belongs to the WFD network, the memory 34 communicates information indicating that the MFP 10 currently belongs to the WFD network and target data (for example, print data, scan data) via the WFD network. Wireless settings (including an authentication method, an encryption method, a password, a wireless network SSID (Service Set Identifier), and a BSSID (Basic Service Set Identifier)) are stored. Further, when the MFP 10 currently belongs to the normal Wi-Fi network, information indicating that the MFP 10 currently belongs to the normal Wi-Fi network and target data communication via the normal Wi-Fi network are executed. Store the wireless settings. The SSID is an identifier for identifying a wireless network, and the BSSID is a unique identifier (for example, MAC in the case of a WFD network) that is an access point that constructs the wireless network. Address).

  The memory 34 further stores a value (ON or OFF) indicating the WFDI / F setting. In the state where the WFDI / F setting in the memory 34 is OFF, the control unit 30 performs each process according to the WFD method (for example, a process for setting the MFP 10 to a later-described spontaneous G / O mode, G / O negotiation). Etc.) cannot be executed. In a state where the WFDI / F setting is ON, the memory 34 further stores a value indicating the current state of the MFP 10 related to the WFD method (any one of the G / O state, the client state, and the device state). .

  Note that 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 memory 34 further stores a value indicating whether or not the MFP 10 is set to the spontaneous G / O mode. It should be noted that when a WFD compatible device in the device state should normally operate in a G / O state or a client state when establishing a WFD connection with another WFD compatible device in the device state G / O negotiation is performed to selectively determine. When the MFP 10 is set to the spontaneous G / O mode, the MFP 10 maintains the operation in the G / O state without executing the G / O negotiation.

The memory 34 further stores SFL (Secure Function Lock) information 36. The SFL information 36 includes, for each of a plurality of terminal devices including the portable terminal 50, information indicating whether the terminal device can use the printing function (OK or OK) and the ID of the terminal device (for example, ID50). NG) and ID-function information associated with information (OK or NG) indicating whether or not the terminal device can use the scan function. The SFL information 36 further includes information indicating a public terminal device (that is, a terminal device whose ID is not registered in the ID-function information) and that the terminal device cannot use the print function. And public information in which information (NG) indicating that the terminal device cannot use the scan function is associated with the information (NG). A user of the MFP 10 operates the operation unit 12 to input SFL information 36 to the MFP 10. As a result, the storage control unit 44 stores the SFL information 36 input by the user in the memory 34.

(Configuration of mobile terminal 50)
The mobile terminal 50 is, for example, a mobile phone (for example, a smartphone), a PDA, a notebook PC, a tablet PC, a portable music player, a portable video player, or the like. The portable terminal 50 includes a wireless LAN I / F (that is, an interface for WFD and normal Wi-Fi) and an NFC I / F. Accordingly, the portable terminal 50 can execute wireless communication with the MFP 10 using the wireless LAN, and can execute wireless communication with the MFP 10 using NFC I / F. The PC 8 includes an application program for causing the MFP 10 to execute a function (for example, a print function, a scan function, etc.). The application program may be installed on the portable terminal 50 from a server provided by the vendor of the MFP 10 or may be installed on the portable terminal 50 from a medium shipped with the MFP 10.

(Configuration of PC8)
The PC 8 includes a wireless LAN (that is, an interface for WFD and normal Wi-Fi), but does not include an NFC I / F. Accordingly, the PC 8 can execute communication with the MFP 10 using the wireless LAN, but cannot execute NFC wireless communication. The portable terminal 50 includes a driver program for causing the MFP 10 to execute a function (for example, a print function, a scan function, etc.). Note that the driver program is normally installed in the PC 8 from a medium shipped with the MFP 10. However, in a modification, the driver program may be installed on the PC 8 from a server provided by the vendor of the MFP 10.

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

(Processing executed by MFP 10)
A process executed by the MFP 10 will be described with reference to FIG. The control unit 30 executes the process of FIG. 2 when the MFP 10 is turned on. While the MFP 10 is turned on, the NFC I / F 22 is in a state of detecting a device capable of performing NFC wireless communication.

The user of the portable terminal 50 starts an application program. Next, the user inputs an instruction for causing the MFP 10 to execute a function (printing function or scanning function) to the portable terminal 50. In this case, the mobile terminal 50 generates NFC information. Although details will be described later, when the portable terminal 50 receives the NG information from the MFP 10 after transmitting the NFC information to the MFP 10, it can generate and transmit the NFC information again. The first NFC information includes at least information indicating a normal request, information indicating a function (printing function or scanning function) input by the user, and an ID “ID50” of the portable terminal 50. The second NFC information includes information indicating a re-request instead of information indicating a normal request. The NFC information for the second time includes at least information indicating a function (printing function or scanning function) input by the user and the ID “ID50” of the portable terminal 50. When the function input by the user is a print function (that is, when the second NFC information includes information indicating the print function), the second NFC information further includes the data size of the print data. Including size information.

  When the mobile terminal 50 currently belongs to the wireless network, the NFC information further includes the SSID and BSSID of the wireless network. Note that the case where the mobile terminal 50 currently belongs to the wireless network means that at least one of the WFD connection and the normal Wi-Fi connection is connected between the mobile terminal 50 and another device (for example, AP6, MFP10). Is established.

  The user of the mobile terminal 50 can bring the mobile terminal 50 closer to the MFP 10. As a result, when the distance between the portable terminal 50 and the MFP 10 becomes smaller than the distance (for example, 10 cm) where radio waves reach each other, the NFC I / F 22 receives the detected radio wave from the MFP 10 and transmits a response radio wave to the MFP 10. Thereafter, the control unit 30 executes communication with the portable terminal 50 via the NFC I / F 22 for establishing an NFC communication session between the MFP 10 and the portable terminal 50. When the NFC communication session is established, the portable terminal 50 transmits the generated NFC information to the MFP 10.

  In S <b> 10, the reception unit 40 monitors reception of NFC information from the mobile terminal 50 via the NFC I / F 22. When NFC information is received (YES in S10), in S12, the receiving unit 40 analyzes the NFC information, and the NFC information includes information indicating a normal request or includes information indicating a re-request. Judge whether or not. If it is determined that the NFC information includes information indicating a normal request, the process proceeds to the normal request process of S14. If it is determined that the NFC information includes information indicating a re-request, the process proceeds to the re-request process in S16.

(Normal request processing; Fig. 3)
With reference to FIG. 3, the contents of the normal request process executed in S14 of FIG. 2 will be described. In S40, the control unit 30 analyzes the NFC information and determines whether the NFC information includes information indicating a printing function or information indicating a scanning function. If it is determined that the NFC information includes information indicating the printing function, the process proceeds to S42. If it is determined that the NFC information includes information indicating the scan function, the process proceeds to S48.

  In S42, the usage determination unit 45 determines whether or not the mobile terminal 50 can use the printing function. Specifically, the usage determination unit 45 first analyzes the NFC information and identifies the terminal ID “ID50” included in the NFC information. Next, the usage determining unit 45 refers to the ID-function information of the SFL information 36 in the memory 34 to determine whether the print function associated with the terminal ID “ID50” is OK or NG. to decide. If the printing function is OK, the usage determining unit 45 determines YES in S42 and proceeds to S44. If the printing function is NG, the usage determining unit 45 determines NO in S42 and proceeds to S46. When the terminal ID “ID50” is not registered in the ID-function information, the usage determining unit 45 refers to the public information (print function = NG, scan function = NG) of the SFL information 36, and S42. It is judged as NO.

In S <b> 44, the state determination unit 41 determines whether the state of the MFP 10 is a printable state (that is, a non-error state) or a print impossible state (that is, an error state). More specifically, the state determination unit 41 checks the remaining amount of consumables mounted in the print execution unit 16 and if the remaining amount of consumables is zero, the state of the MFP 10 cannot be printed. The state is determined (NO in S44). For example, when the print execution unit 16 is an ink jet printing mechanism, the consumable item is ink in an ink cartridge. For example, when the print execution unit 16 is a laser type printing mechanism, the consumable item is toner in the toner cartridge.

  Further, the state determination unit 41 checks the remaining amount of the print medium used by the print execution unit 16 (that is, the remaining amount of the print medium in the paper feed tray), and the remaining amount of the print medium is zero. Then, it is determined that the state of the MFP 10 is not printable (NO in S44).

  Next, the state determination unit 41 checks the state of the hardware for executing the printing function, and determines that the state of the MFP 10 is an unprintable state if there is a problem with the hardware (NO in S44). ). For example, when the print medium is jammed in the print medium conveyance mechanism in the print execution unit 16 (that is, in the case of a paper jam), the state determination unit 41 determines that the state of the MFP 10 is an unprintable state. To do. In this case, the hardware described above is a print medium transport mechanism in the print execution unit 16. Further, for example, when the free space in the memory 34 is extremely small, that is, when the free space in the memory 34 is less than a predetermined value, the print data cannot be processed, so the state determination unit 41 It is determined that the state of the MFP 10 is an unprintable state. In this case, the hardware is the memory 34. Further, for example, when a cover member that needs to be closed at the time of execution of printing is opened (hereinafter referred to as “cover open”) among a plurality of members constituting the housing of the MFP 10, The determination unit 41 determines that the state of the MFP 10 is an unprintable state. In this case, the hardware is the cover member.

  When the state determination unit 41 determines that the MFP 10 is in an unprintable state due to any of the remaining amount of consumables, the remaining amount of print media, and the hardware state (NO in S44). ), The process proceeds to S46. On the other hand, if there is no problem with the remaining amount of consumables, the remaining amount of the print medium, and the hardware state, the state determination unit 41 determines that the state of the MFP 10 is a printable state (in S44). YES) Thus, in this embodiment, the MFP 10 can appropriately determine whether the state of the MFP 10 is a non-error state or an error state. If YES in S44, the normal request process of FIG. 3 ends as “normal END”.

  In S <b> 46, the transmission unit 46 transmits the print NG information including the NG reason caused by the SFL to the portable terminal 50 via the NFC I / F 22. For example, in the case of NO in S42, the NG reason indicates that the portable terminal 50 cannot use the print function. If NO in S44, the NG reason indicates that the MFP 10 is in an error state. In this case, the NG reason is a specific reason that the MFP 10 is in an error state (for example, the remaining amount of consumables is zero, the remaining amount of the print medium is zero, the print medium is jammed (paper jam), the memory 34 has a small free space, cover open, etc.). As described above, in this embodiment, the MFP 10 can appropriately notify the portable terminal 50 that the state of the MFP 10 is a non-printable state (that is, an error state) and the reason for the error. When S46 ends, the normal request process of FIG. 3 ends as “error END”.

  In S <b> 48, the usage determining unit 45 determines whether or not the mobile terminal 50 can use the scan function. More specifically, as in S42, the usage determining unit 45 refers to the SFL information 36 in the memory 34 and determines whether the scan function associated with the terminal ID “ID50” is OK or not. It is judged whether it is. If the scan function is OK, the usage determination unit 45 determines YES in S48 and proceeds to S52. If the scan function is NG, the usage determination unit 45 determines NO in S48 and proceeds to S50. When the terminal ID “ID50” is not registered in the ID-function information, the usage determining unit 45 refers to the public information (print function = NG, scan function = NG) of the SFL information 36, and S48. It is judged as NO.

In S <b> 50, the transmission unit 46 transmits scan NG information including the NG reason caused by the SFL to the portable terminal 50 via the NFC I / F 22. The NG reason indicates that the mobile terminal 50 cannot use the scan function. When S50 ends, the normal request process of FIG. 3 ends as “error END”.

  In S <b> 52, the state determination unit 41 determines whether the state of the MFP 10 is a scannable state (that is, a non-error state) or a scan-disabled state (that is, an error state). More specifically, the state determination unit 41 checks the state of hardware for executing the scan function, and determines that the state of the MFP 10 is in a scan-disabled state when there is a problem with the hardware. (NO in S52). For example, in the automatic document feeder in the scan execution unit 18, when the document is jammed, the state determination unit 41 determines that the state of the MFP 10 is a scannable state. In this case, the above hardware is an automatic document feeder in the scan execution unit 18. Further, for example, when the free space in the memory 34 is very small, that is, when the free space in the memory 34 is less than a predetermined value, the scan data cannot be processed. It is determined that the state of the MFP 10 is an unscannable state. In this case, the hardware is the memory 34. Further, for example, when a cover member that needs to be closed at the time of scanning is opened among a plurality of members constituting the casing of the MFP 10 (that is, when the cover is open), the state determination unit 41. Determines that the MFP 10 is in an unscannable state. In this case, the hardware is the cover member.

  If the state determination unit 41 determines that the state of the MFP 10 is not scannable (NO in S52), the state determination unit 41 proceeds to S54. On the other hand, if there is no problem in the hardware state, state determination unit 41 determines that the state of MFP 10 is a scannable state (YES in S52). Thus, in this embodiment, the MFP 10 can appropriately determine whether the state of the MFP 10 is a non-error state or an error state. If YES in S52, the normal request process of FIG. 3 ends as “normal END”.

  In S <b> 54, the transmission unit 46 determines whether or not the MFP 10 currently belongs to the wireless network. Specifically, the transmission unit 46 stores in the memory 34 at least one of information indicating that it currently belongs to the WFD network and information indicating that it currently belongs to the normal Wi-Fi network. If it is determined that the MFP 10 currently belongs to the wireless network (YES in S54), the process proceeds to S56. On the other hand, the transmission unit 46, when neither the information indicating that it currently belongs to the WFD network nor the information indicating that it currently belongs to the normal Wi-Fi network is stored in the memory 34. The MFP 10 determines that it does not currently belong to the wireless network (NO in S54), and proceeds to S60.

  In S <b> 56, the transmission unit 46 determines whether the MFP 10 and the portable terminal 50 belong to the same wireless network. Specifically, the transmission unit 46 first analyzes the NFC information and determines whether the NFC information includes an SSID and a BSSID. If the NFC information does not include the SSID and BSSID, the mobile terminal 50 does not currently belong to the wireless network. For this reason, the transmission unit 46 determines that the MFP 10 and the portable terminal 50 do not belong to the same wireless network (NO in S56), and proceeds to S60.

When the NFC information includes the SSID and the BSSID, the transmission unit 46 further includes the SSID in the NFC information (that is, the SSID of the wireless network (normally Wi-Fi network or WFD network) to which the mobile terminal 50 belongs). Then, it is determined whether or not the SSID included in the wireless setting in the memory 34 (that is, the SSID of the wireless network to which the MFP 10 belongs (normally Wi-Fi network or WFD network)) matches. If the two SSIDs do not match, the transmitting unit 46 determines that the MFP 10 and the portable terminal 50 do not belong to the same wireless network (NO in S56), and proceeds to S60.

  If the two SSIDs match, the transmission unit 46 further transmits the BSSID in the NFC information (that is, the BSSID of the wireless network to which the mobile terminal 50 belongs) and the BSSID ( That is, it is determined whether or not the BSSID of the wireless network to which the MFP 10 belongs matches. If the two BSSIDs do not match, the transmitting unit 46 determines that the MFP 10 and the portable terminal 50 do not belong to the same wireless network (NO in S56), and proceeds to S60.

  If the two BSSIDs match, the transmitting unit 46 determines that the MFP 10 and the portable terminal 50 belong to the same wireless network (YES in S56), and proceeds to S58. As described above, in this embodiment, in S56, both the SSID match determination and the BSSID match determination are executed. For example, one AP may construct a plurality of wireless networks by using a plurality of SSIDs. Therefore, if the BSSIDs match and the SSIDs do not match, the MFP 10 and the portable terminal 50 may belong to different wireless networks constructed by the same AP. In the present embodiment, it is possible to more appropriately determine whether the MFP 10 and the portable terminal 50 belong to the same wireless network by executing both the SSID matching determination and the BSSID matching determination. be able to. In the modification, the SSID match determination is executed in S56, but the BSSID match determination may not be executed.

  In S58 and S60, the transmission unit 46 transmits the scan NG information including the NG reason to the portable terminal 50 via the NFC I / F 22. The NG reason indicates a specific reason why the MFP 10 is in an error state (for example, the document is jammed, the memory 34 has a small free space, the cover is open, etc.). As described above, in this embodiment, the MFP 10 can appropriately notify the portable terminal 50 of the fact that the MFP 10 is in a scannable state (that is, an error state) and the reason for the error.

  The scan NG information transmitted in S58 further includes information indicating that the MFP 10 and the portable terminal 50 belong to the same wireless network (hereinafter referred to as “NW match information”). On the other hand, the scan NG information transmitted in S60 further includes information indicating that the MFP 10 and the portable terminal 50 do not belong to the same wireless network (hereinafter referred to as “NW mismatch information”). When S58 and S60 are completed, the normal request process of FIG. 3 ends as “error END”. When the normal request process in FIG. 3 (S14 in FIG. 2) ends, the process proceeds to S18 in FIG.

  When the portable terminal 50 receives the print NG information (see S46 in FIG. 3) from the MFP 10, it executes the following processes. The portable terminal 50 first analyzes the print NG information and identifies the NG reason. For example, when the NG reason indicates that the mobile terminal 50 cannot use the print function (NO in S42 of FIG. 3), the mobile terminal 50 uses the NFC information including information indicating the re-request ( The screen indicating that the user cannot use the printing function is displayed on the display unit of the portable terminal 50 without transmitting the second NFC information) to the MFP 10. Further, for example, when the NG reason indicates that the free space of the memory 34 is small, the portable terminal 50 does not transmit the NFC information including the information indicating the re-request to the MFP 10, and stores the NFC information in the memory 34 of the MFP 10. A screen indicating that the free space is insufficient is displayed on the display unit of the portable terminal 50.

On the other hand, if the NG reason indicates another reason (for example, the remaining amount of consumables is zero, the remaining amount of print media is zero, the print medium is jammed (paper jam), the cover is open, etc.) The portable terminal 50 includes information indicating a re-request, information indicating a print function, and a terminal ID “ID50.
And the size information indicating the data size of the print data is generated (the NFC information for the second time), and the NFC information is transmitted to the MFP 10.

  Further, when receiving the scan NG information (see S50, S58, and S60 in FIG. 3) from the MFP 10, the portable terminal 50 executes the following processes. First, the portable terminal 50 analyzes the scan NG information and specifies the NG reason. For example, when the NG reason indicates that the mobile terminal 50 cannot use the scan function (S50 in FIG. 3), the mobile terminal 50 receives the NFC information including the information indicating the re-request (the second time described above). The NFC information) is not transmitted to the MFP 10 and a screen indicating that the user cannot use the scan function is displayed on the display unit of the portable terminal 50. Further, for example, when the NG reason indicates that the free space of the memory 34 is small, the portable terminal 50 does not transmit the NFC information including the information indicating the re-request to the MFP 10, and stores the NFC information in the memory 34 of the MFP 10. A screen indicating that the free space is insufficient is displayed on the display unit of the portable terminal 50.

  On the other hand, if the NG reason indicates another reason (for example, the document is jammed, cover open, etc.), the portable terminal 50 further analyzes the scan NG information, and the scan NG information indicates that the NW It is determined whether the match information is included (S58 in FIG. 3) or whether the NW mismatch information is included (S60 in FIG. 3). When the scan NG information includes NW mismatch information, the portable terminal 50 does not transmit the NFC information including the information indicating the re-request (the second NFC information described above) to the MFP 10 and causes an error due to the NG reason. A screen indicating the state is displayed on the display unit of the portable terminal 50. On the other hand, when the scan NG information includes NW match information, the mobile terminal 50 generates NFC information (the second NFC information described above) including information indicating a re-request, and sends the NFC information to the MFP 10. Send.

  As described above, the portable terminal 50 can transmit the second NFC information to the MFP 10 according to the contents of the print NG information or the scan NG information. When the NG reason in the print NG information or the scan NG information indicates that the mobile terminal 50 cannot use the print function or the scan function, or indicates that the free space of the memory 34 is low. The MFP 10 cannot execute the print function or the scan function in response to a request from the portable terminal 50. Therefore, in such a case, the portable terminal 50 does not transmit the second NFC information to the MFP 10. As a result, the MFP 10 does not need to receive the second NFC information, so various processes (for example, a re-request process to be described later, a change process to be described later (S16, S20, etc. in FIG. 2)) are executed. You do n’t have to. Therefore, the processing load on the MFP 10 can be reduced.

As will be described in detail later, in the change process (see S20 in FIG. 2) described later, when the MFP 10 and the portable terminal 50 do not belong to the same wireless network, the MFP 10 and the portable terminal 50 belong to the same wireless network. A belonging state (hereinafter referred to as “NW matching state”) may be temporarily formed (see S118 in FIG. 5). In the printing function, after the communication process (that is, transmission of print data) is executed, the print process is executed. Accordingly, when the MFP 10 is in an error state where printing is not possible and the temporary NW match state is formed by the change process described later, the MFP 10 uses the temporary NW match state to perform communication processing ( In other words, after the temporary NW matching state is resolved (that is, after WFDI / F is turned off in S30 of FIG. 2), the print monitoring thread described later is executed. A printing process can be executed. On the other hand, in the scan function, after the scan process is executed, a communication process (that is, transmission of scan data) is executed. Therefore, when the MFP 10 is in an error state that cannot be scanned, the MFP 10 cannot execute communication processing unless the error state is canceled. For this reason, if the MFP 10 is in an error state that cannot be scanned, even if a temporary NW matching state is formed by a change process described later, the MFP 10 uses the temporary NW matching state. Communication processing cannot be executed.

  In view of the above situation, when the scan NG information includes the NW match information, that is, since the MFP 10 and the mobile terminal 50 belong to the same wireless network, the mobile terminal 50 may temporarily perform the change process described later. If it is not necessary to form the NW match state, the second NFC information is transmitted to the MFP 10. However, the mobile terminal 50 transmits the second NFC information to the MFP 10 when the scan NG information includes NW mismatch information, that is, when a temporary NW match state needs to be formed by a change process described later. do not do. As a result, the MFP 10 does not need to receive the second NFC information, so various processes (for example, a re-request process to be described later, a change process to be described later (S16, S20, etc. in FIG. 2)) are executed. You do n’t have to. Therefore, the processing load on the MFP 10 can be reduced.

(Re-request processing; Fig. 4)
With reference to FIG. 4, the content of the re-request process executed in S16 of FIG. 2 will be described. In S70, the control unit 30 analyzes the NFC information (the second NFC information described above) and determines whether the NFC information includes information indicating a printing function or information indicating a scanning function. When it is determined that the NFC information includes information indicating the printing function, the process proceeds to S72. When it is determined that the NFC information includes information indicating the scan function, the process proceeds to S76.

  In S72, the size determination unit 47 determines whether or not the free space in the memory 34 is equal to or larger than the data size of the print data. As described above, when the print function is determined in S70, the NFC information includes size information indicating the data size of the print data. In S72, the size determination unit 47 analyzes the NFC information and specifies the size information. Next, the size determination unit 47 determines whether or not the free space in the memory 34 is equal to or larger than the data size of the print data indicated by the size information.

  If it is determined that the free space in the memory 34 is equal to or larger than the data size of the print data (YES in S72), the re-request process in FIG. 4 ends as “normal END”. On the other hand, when it is determined that the free capacity in the memory 34 is less than the data size of the print data (NO in S72), the process proceeds to S74.

  In S <b> 74, the transmission unit 46 transmits the print NG information including the NG reason to the portable terminal 50 via the NFC I / F 22. The NG reason indicates that the free capacity in the memory 34 is less than the data size of the print data. When S74 ends, the re-request process of FIG. 4 ends as “error END”. In this case, the portable terminal 50 causes the display unit of the portable terminal 50 to display a screen indicating that the free space in the memory 34 of the MFP 10 is insufficient without transmitting further NFC information to the MFP 10.

  If the scan function is determined in S70, the function execution unit 43 activates a scan monitoring thread in S76. As will be described in detail later, in the scan monitoring thread, when the state of the MFP 10 changes from an error state to a non-error state, the function execution unit 43 scans a document to generate scan data. And a communication function for transmitting the scan data to the mobile terminal 50 via the wireless LAN I / F 20.

When the normal request process of S14 in FIG. 2 or the re-request process of S16 ends, in S18, the changing unit 42 determines whether or not the process of S14 or S16 ends as “normal END”. . When the process of S14 or S16 ends as “normal END”, the changing unit 42 determines YES in S18 and executes the changing process of S20. On the other hand, when the process of S14 or S16 ends as “error END”, the change unit 42 determines NO in S18 and does not execute the change process of S20 (and further, the processes after S22) Without executing again), the process returns to S10.

(Change processing; FIG. 5)
With reference to FIG. 5, the content of the change process performed by S20 of FIG. 2 is demonstrated. The change process is a process for changing the interface for the MFP 10 to communicate with the portable terminal 50 from the NFC I / F 22 to the wireless LAN I / F 20.

  In S100, the changing unit 42 determines whether the MFP 10 currently belongs to the wireless network. S100 is the same as S54 of FIG. If the changing unit 42 determines that the MFP 10 currently belongs to the wireless network (YES in S100), the changing unit 42 proceeds to S102. If the changing unit 42 determines that the MFP 10 does not currently belong to the wireless network (NO in S100), the changing unit 42 performs S104. Proceed to

  In S <b> 102, the changing unit 42 determines whether the MFP 10 and the portable terminal 50 belong to the same wireless network. S102 is the same as S56 of FIG. When determining that the MFP 10 and the portable terminal 50 belong to the same wireless network (YES in S102), the changing unit 42 proceeds to S120 and determines that the MFP 10 and the portable terminal 50 do not belong to the same wireless network. If yes (NO in S102), the process proceeds to S104.

  As described in S56 of FIG. 3, in S104, the changing unit 42 performs determination using the SSID and BSSID of the wireless network to which the mobile terminal 50 currently belongs. Therefore, the changing unit 42 can appropriately execute the changing process using the SSID and BSSID included in the NFC information.

  In S <b> 120, the changing unit 42 transmits information indicating that setting change is unnecessary to the portable terminal 50 via the NFC I / F 22. Thereby, the portable terminal 50 does not need to change the current wireless setting of the portable terminal 50, that is, uses the wireless network (normally Wi-Fi network or WFD network) to which the portable terminal 50 currently belongs. You can know what you need to do.

  In the change process executed through S76 of FIG. 4, the change unit 42 determines YES in S100 and S102, and always executes S120. This is because S76 in FIG. 4 is executed only when YES is determined in S54 and S56 in FIG. 3 (that is, when the MFP 10 and the portable terminal 50 belong to the same wireless network). When S120 ends, the change process of FIG. 5 ends as “normal END”.

  In S104, the changing unit 42 determines whether the WFDI / F setting in the memory 34 is ON or OFF. The changing unit 42 proceeds to S106 when the WFDI / F setting is ON (YES in S104), and proceeds to S108 when the WFDI / F setting is OFF (NO in S104).

  In S <b> 108, the changing unit 42 changes the WFDI / F setting in the memory 34 from OFF to ON without receiving an instruction from the user of the MFP 10. As a result, the control unit 30 can execute each process according to the WFD method (such as processes in S114 to S118 described later). When S108 ends, the process proceeds to S114.

At the stage where S106 is executed, since the WFDI / F setting is ON, the MFP 10 is in any one of three states of the WFD method (G / O state, client state, and device state). Operating in one state. Accordingly, the memory 34 stores a value (hereinafter referred to as “state value”) indicating the state (G / O state, client state, or device state) of the MFP 10 related to the WFD system.

  In S <b> 106, the changing unit 42 determines whether the MFP 10 is operating in the client state. Specifically, the changing unit 42 determines whether or not the state value in the memory 34 is a value indicating the client state. When the state value is a value indicating the client state (YES in S106), the changing unit 42 ends the change process as “error END” without continuously executing the change process. On the other hand, when the state value is a value indicating the G / O state or the device state (NO in S106), the changing unit 42 proceeds to S110 (that is, continuously executing the changing process).

  In S110, the changing unit 42 determines whether the MFP 10 is operating in the G / O state. Specifically, the changing unit 42 determines whether or not the state value in the memory 34 is a value indicating the G / O state. The change unit 42 proceeds to S112 when the state value is a value indicating the G / O state (YES in S110), and proceeds to S112 when the state value is a value indicating the device state (NO in S110). Proceed to

  In S112, the changing unit 42 determines whether the number of devices other than the MFP 10 included in the WFD network in which the MFP 10 is operating in the G / O state is less than a predetermined maximum number of clients. Specifically, the changing unit 42 determines NO in S112 when the number of pieces of identification information of devices registered in the management list in the memory 34 (that is, devices in the client state) is equal to or greater than the maximum number of clients. Judgment is made and the change process is terminated as “error END” without continuing the change process. On the other hand, when the above number is less than the maximum number of clients, the changing unit 42 determines YES in S112 and proceeds to S116 (that is, continuously executing the changing process).

  In S114, the changing unit 42 sets the MFP 10 to the spontaneous G / O mode. The spontaneous G / O mode is a mode in which the MFP 10 maintains operation in the G / O state. Accordingly, the WFD connection is not established at the stage of S114, but the MFP 10 is set to the G / O state (that is, the state value in the memory 34 is a value indicating the G / O state). When the MFP 10 is set to the G / O state, the changing unit 42 prepares wireless settings (SSID, BSSID, authentication method, encryption method, password, etc.) to be used in the WFD network. Note that the authentication method and the encryption method are determined in advance. Further, the changing unit 42 generates a password. Note that the SSID may be generated by the changing unit 42 or may be determined in advance. BSSID is the MAC address for WFD of MFP 10. The changing unit 42 stores the wireless setting generated in S114 in the memory 34. At this stage, the management list in the memory 34 does not describe the identification information of the device in the client state.

  Next, in S <b> 116, the changing unit 42 transmits the wireless setting in the memory 34 to the portable terminal 50 via the NFC I / F 22. In S116 executed through S114, the wireless setting in the memory 34 is the wireless setting generated in S114. In S116 executed after YES in S112, the above-described wireless setting in the memory 34 is a wireless setting generated when it is determined in the past that the MFP 10 operates in the G / O state. Thereby, the portable terminal 50 can use the same wireless setting as that of the MFP 10.

Next, in S <b> 118, the changing unit 42 establishes a WFD connection with the mobile terminal 50. Specifically, the changing unit 42 performs specific wireless communication with the portable terminal 50 via the wireless LAN I / F 20. The specific wireless communication described above is the Authentication Request, Authentication Response, Association R
request, Association Response, and 4 way handshake. In the process of the specific wireless communication, various authentication processes such as SSID authentication, authentication method and encryption method authentication, and password authentication are executed. When all the authentications are successful, a WFD connection is established between the MFP 10 and the portable terminal 50.

  If both the MFP 10 and the portable terminal 50 are in the device state, when the WFD connection is established between the MFP 10 and the portable terminal 50, one of the MFP 10 and the portable terminal 50 is set to G / In addition to determining as O, G / O negotiation for determining the other of the MFP 10 and the portable terminal 50 as a client is executed. However, since it is determined that the MFP 10 is in the G / O state at the stage where S118 is executed, the changing unit 42 does not execute the G / O negotiation and establishes the WFD connection with the portable terminal 50. Establish.

  When the WFD connection is established between the MFP 10 and the portable terminal 50, the changing unit 42 further adds the MAC address of the portable terminal 50 to the management list. Note that the changing unit 42 acquires the MAC address of the portable terminal 50 in the process of the specific wireless communication in S118. When the WFD connection is established between the MFP 10 and the portable terminal 50, the MFP 10 in the G / O state executes communication of target data (print data, scan data, etc.) with the portable terminal 50 in the client state. Will be able to. The target data includes data in the network layer, which is a higher layer than the physical layer of the OSI reference model. Accordingly, the MFP 10 in the G / O state can execute wireless communication in the network layer with the portable terminal 50 in the client state. When S118 ends, the change process of FIG. 5 ends as “normal END”.

(Continuation of MFP processing in FIG. 2)
When the change process of S20 of FIG. 2 (FIG. 5) ends, in S22, the transmission unit 46 determines whether or not the change process of S20 has ended as “normal END”. If the change process in S20 ends as “normal END”, the transmission unit 46 determines YES in S22 and proceeds to S26. On the other hand, when the change process of S20 ends as “error END”, the transmission unit 46 determines NO in S22 and proceeds to S24.

  In S <b> 24, the transmission unit 46 transmits communication NG information to the mobile terminal 50 via the NFC I / F 22. The communication NG information includes an NG reason indicating that wireless communication of target data cannot be performed. When receiving the communication NG information, the portable terminal 50 does not execute the wireless communication of the target data without transmitting the NFC information including the information indicating the re-request (the second NFC information) to the MFP 10. A screen indicating that it is possible is displayed on the display unit of the portable terminal 50.

  Next, in S26, the function execution unit 43 executes a function execution process including a communication process. When the NFC information received in S10 includes information indicating the print function, in S26, the function execution unit 43 first receives print data from the portable terminal 50 via the wireless LAN I / F 20. The communication process is executed. Next, the function execution unit 43 executes print processing according to the print data. That is, the function execution unit 43 executes various processes (color conversion process, halftone process, etc.) on the print data to generate processed data, and then supplies the processed data to the print execution unit 16. Accordingly, the print execution unit 16 prints an image on the print medium according to the processed data.

When the NFC information received in S10 includes information indicating the scan function, in S26, the function execution unit 43 first executes a scan process. That is, the function execution unit 43 causes the scan execution unit 18 to scan a document set in the scan execution unit 18. The function execution unit 43 acquires original image data obtained by scanning, executes various processes (such as correction processing) on the original image data, and generates scan data. Next, the function execution unit 43 executes a communication process for transmitting scan data to the portable terminal 50 via the wireless LAN I / F 20.

  In S26 executed through YES in S72 of FIG. 4, the function execution unit 43 executes communication processing for receiving the print data and stores the print data in the memory 34, but executes the print processing. do not do. In this case, the function execution unit 43 activates a print monitoring thread. Further, when S76 in FIG. 4 is executed (that is, when the scan monitoring thread is activated), the function execution unit 43 skips the process of S26.

  Next, in S28, the changing unit 42 determines whether or not the process of S108 (a process of changing the WFDI / F setting from OFF to ON) in FIG. 5 is executed in the changing process of S20. When the process of S108 is executed (YES in S28), the changing unit 42 changes the WFDI / F setting from ON to OFF in S30. Thereby, the change part 42 can return to WFDI / F setting before a change (namely, OFF), when a WFDI / F setting is changed to ON, without receiving a user's instruction | indication. In this case, the WFD connection established in S118 of FIG. 5 is disconnected, and the WFD network disappears.

  In addition, the change part 42 skips S30, when the process of S108 is not performed (it is NO at S28). If NO in S28, or if S30 ends, the process returns to S10.

(Print monitoring thread)
As described above, the print monitoring thread can be activated in S26 of FIG. In the print monitoring thread, the function execution unit 43 monitors that the state of the MFP 10 changes from the unprintable state to the printable state. When the user of the MFP 10 removes the cause of the MFP 10 being unable to print (for example, when the cover member is closed, the function execution unit 43 removes the print medium jammed in the print medium conveyance path. In this case, it is determined that the state of the MFP 10 has changed to a printable state when a consumable or a print medium is replenished. When the function execution unit 43 determines that the state of the MFP 10 has changed to a printable state, the function execution unit 43 executes print processing according to the print data in the memory 34.

(Scan monitoring thread)
As described above, the scan monitoring thread can be activated in S76 of FIG. In the scan monitoring thread, the function execution unit 43 monitors the change in the state of the MFP 10 from the unscannable state to the scannable state. When the user of the MFP 10 removes the cause of the MFP 10 being unable to scan (for example, when the cover member is closed, the document jammed in the automatic document feeder is removed) Etc.), it is determined that the state of the MFP 10 has changed to a scannable state. When the function execution unit 43 determines that the state of the MFP 10 has changed to a scannable state, the function execution unit 43 executes a scan process for generating scan data. Next, the function execution unit 43 executes a communication process for transmitting scan data to the portable terminal 50 via the wireless LAN I / F 20.

  Next, specific cases realized by the MFP 10 and the portable terminal 50 will be described with reference to FIGS. Each case in FIGS. 6 to 13 is realized by the MFP 10 executing the processes in FIGS. 2 to 5.

(Case A; FIG. 6)
In case A, the state of the MFP 10 is a non-error state (that is, a printable state and a scannable state), and the print function “O” is assigned to the terminal ID “ID50” in the SFL information 36.
K ”and the scan function“ OK ”are associated with each other.

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). The NFC information includes information indicating a normal request. For example, when the NFC information includes information indicating the printing function (hereinafter referred to as “printing case”), the MFP 10 determines YES in S42 of FIG. 3 and determines YES in S44. For example, when the NFC information includes information indicating the scan function (hereinafter referred to as “scan case”), the MFP 10 determines YES in S48 of FIG. 3 and determines YES in S52. In both the printing case and the scanning case, the normal request processing ends as “normal END”.

  Next, the MFP 10 executes the change process of S20 of FIG. Thereby, communication for changing the interface to be used for communication between the MFP 10 and the portable terminal 50 from NFC I / F to wireless LAN I / F (S116 to S120 in FIG. 5; hereinafter, “I / F "Communication for change") is executed. In the communication for changing the I / F, communication through the NFC I / F 22 may be executed (S116 and S120 in FIG. 5), or communication through the wireless LAN I / F 20 may be executed. Yes (S118 in FIG. 5). Therefore, both “NFC” and “wireless LAN” are described on the left side of the change process in FIG.

  In the case of printing, the MFP 10 executes communication processing for receiving print data from the portable terminal 50 via the wireless LAN I / F 20 (S26), and then executes print processing according to the print data (S26). S26). Thereby, the MFP 10 can execute the printing function in accordance with an instruction from the portable terminal 50.

  In the scan case, the MFP 10 executes a scan process for generating scan data (S26), and then executes a communication process for transmitting the scan data to the portable terminal 50 via the wireless LAN I / F 20. (S26). Thereby, the MFP 10 can execute the scan function in accordance with an instruction from the portable terminal 50.

(Case X1; FIG. 7)
Cases X1 to X4 in FIGS. 7 to 10 show an example of communication for changing the IF. In case X1, the MFP 10 and the portable terminal 50 already belong to the same wireless network (WFD network or normal Wi-Fi network) when NFC information communication is executed.

  The MFP 10 determines YES in S100 of FIG. 5 and determines YES in S102. For this reason, in S <b> 120, the MFP 10 transmits information indicating that setting change is unnecessary to the portable terminal 50 via the NFC I / F 22. In this case, the MFP 10 uses the existing wireless network to execute communication of target data (print data or scan data) with the portable terminal 50 via the wireless LAN I / F 20 (S26 in FIG. 2).

(Case X2; FIG. 8)
In case X2, the MFP 10 and the PC 8 construct a WFD network, and the MFP 10 operates in the G / O state. Note that the portable terminal 50 does not belong to the above WFD network.

The MFP 10 determines YES in S100 of FIG. 5, determines NO in S102, determines YES in S104, determines NO in S106, determines YES in S110, and determines YES in S112. For this reason, in S116, the MFP 10 uses the NFC I / F 22 to set the wireless setting for the portable terminal 50 to participate in the WFD network (that is, the wireless setting generated when the MFP 10 becomes G / O). To the mobile terminal 50. Next, in S <b> 118, the MFP 10 establishes a WFD connection with the portable terminal 50 via the wireless LAN I / F 20.

  Thereby, the portable terminal 50 can newly participate in the WFD network to which the MFP 10 and the PC 8 belong. In this case, the MFP 10 performs communication of the target data (print data or scan data) with the portable terminal 50 via the wireless LAN I / F 20 using the WFD network (S26 in FIG. 2).

(Case X3; FIG. 9)
In case X3, the MFP 10 does not belong to the wireless network, and the MFP 10 is operating in the device state (that is, the WFDI / F setting is ON). Note that the portable terminal 50 does not belong to the wireless network.

  The MFP 10 determines NO in S100 of FIG. 5, determines YES in S104, determines NO in S106, and determines NO in S110. For this reason, in S114, the MFP 10 is set to the spontaneous G / O mode. At this time, the MFP 10 generates a wireless setting to be used in the newly constructed WFD network. Next, in S116, the MFP 10 transmits the wireless setting for the portable terminal 50 to participate in the WFD network (that is, the wireless setting generated by the MFP 10 in S114) to the portable terminal 50 via the NFC I / F 22. Next, in S <b> 118, the MFP 10 establishes a WFD connection with the portable terminal 50 via the wireless LAN I / F 20.

  Thereby, a new WFD network including the MFP 10 and the portable terminal 50 is constructed. In this case, the MFP 10 performs communication of the target data (print data or scan data) with the portable terminal 50 via the wireless LAN I / F 20 using the WFD network (S26 in FIG. 2).

(Case X4; FIG. 10)
In case X4, the MFP 10 does not belong to the wireless network, and the WFDI / F setting of the MFP 10 is OFF. Note that the portable terminal 50 does not belong to the wireless network.

  The MFP 10 determines NO in S100 of FIG. 5 and determines NO in S104. For this purpose, in S108, the MFP 10 changes the WFDI / F setting from OFF to ON. Next, in S114, the MFP 10 is set to the spontaneous G / O mode. At this time, the MFP 10 generates a wireless setting to be used in the newly constructed WFD network. Next, in S116, the MFP 10 transmits the wireless setting for the portable terminal 50 to participate in the WFD network (that is, the wireless setting generated by the MFP 10 in S114) to the portable terminal 50 via the NFC I / F 22. Next, in S <b> 118, the MFP 10 establishes a WFD connection with the portable terminal 50 via the wireless LAN I / F 20.

  Thereby, a new WFD network including the MFP 10 and the portable terminal 50 is constructed. In this case, the MFP 10 performs communication of the target data (print data or scan data) with the portable terminal 50 via the wireless LAN I / F 20 using the WFD network (S26 in FIG. 2).

Next, the MFP 10 determines YES in S28 of FIG. 2, and changes the WFDI / F setting from ON to OFF in S30. As a result, the WFD network disappears. This is because G / O does not exist. That is, the WFD network described above is S2 in FIG.
6 is a wireless network that is temporarily constructed for communication processing 6.

(Case B; FIG. 11)
In case B, the state of the MFP 10 is a non-error state (that is, the printable state and the scannable state), and the print function “OK” is associated with the terminal ID “ID50” in the SFL information 36. The scan function “NG” is associated with the terminal ID “ID50”.

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). The NFC information includes information indicating a normal request and information indicating a printing function. In this case, as in the case A in FIG. 6, the MFP 10 executes the change process (S20 in FIG. 2), executes the communication process for receiving the print data (S26), and then follows the print data. A printing process is executed (S26). Thereby, the MFP 10 can execute the printing function in accordance with an instruction from the portable terminal 50.

  Next, the MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). The NFC information includes information indicating a normal request and information indicating a scan function. In this case, the MFP 10 determines NO in S48 of FIG. 3, and transmits scan NG information to the portable terminal 50 via the NFC I / F 22 in S50.

  Therefore, the normal request process ends as “error END”. Accordingly, the MFP 10 determines NO in S18 of FIG. 2 and does not execute the change process of S20. In addition, the portable terminal 50 does not transmit NFC information including information indicating a re-request to the MFP 10 in order to receive the scan NG information including the NG reason caused by the SFL.

(Case C; FIG. 12)
In case C, the state of the MFP 10 is an error state (that is, a state in which printing is not possible due to cover open), and the printing function “OK” is associated with the terminal ID “ID50” in the SFL information 36. .

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). The NFC information includes information indicating a normal request and information indicating a printing function. The MFP 10 determines YES in S42 of FIG. 3 and determines NO in S44. In this case, in S <b> 46, the MFP 10 transmits print NG information including the NG reason indicating the cover open to the portable terminal 50 via the NFC I / F 22.

  Therefore, the normal request process ends as “error END”. Accordingly, the MFP 10 determines NO in S18 of FIG. 2 and does not execute the change process of S20. On the other hand, when the portable terminal 50 receives the print NG information from the MFP 10, the MFP 10 receives NFC information including at least information indicating a re-request, information indicating a print function, and size information indicating the data size of the print data. Send to.

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). If the free space in the memory 34 is equal to or larger than the data size of the print data, the MFP 10 determines YES in S72 of FIG.

Therefore, the re-request process ends as “normal END”. Accordingly, the MFP 10 determines YES in S18 of FIG. 2, executes the change process of S20, and executes a communication process for receiving print data (S26). The MFP 10 stores the print data in the memory 34 and activates a print monitoring thread (S26). When the state of the MFP 10 changes from the unprintable state to the printable state, the MFP 10 executes print processing according to the print data in the print monitoring thread. Thereby, the MFP 10 can execute the printing function in accordance with an instruction from the portable terminal 50.

  On the other hand, if the free capacity of the memory 34 is less than the data size of the print data, the MFP 10 determines NO in S72 of FIG. In this case, in S <b> 74, the MFP 10 transmits the print NG information including the NG reason indicating the lack of free space in the memory 34 to the portable terminal 50 via the NFC I / F 22.

  Therefore, the re-request process ends as “error END”. Accordingly, the MFP 10 determines NO in S18 of FIG. 2 and does not execute the change process of S20. In addition, the portable terminal 50 does not transmit the NFC information including the information indicating the re-request to the MFP 10 in order to receive the print NG information including the NG reason indicating the insufficient free space in the memory 34.

(Case D; FIG. 13)
In Case D, the state of the MFP 10 is an error state (that is, a scan impossible state due to cover open), and the scan function “OK” is associated with the terminal ID “ID50” in the SFL information 36. . Note that the MFP 10 and the mobile terminal 50 belong to the same wireless network of WFD or normal Wi-Fi.

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). The NFC information includes information indicating a normal request and information indicating a scan function. The MFP 10 determines YES in S48 of FIG. 3, and determines NO in S52. The MFP 10 and the portable terminal 50 already belong to the same wireless network when NFC information communication is executed. Accordingly, the MFP 10 determines YES in S54 and determines YES in S56. In this case, in S58, the MFP 10 transmits scan NG information including the NG reason indicating the cover open and the NW match information to the portable terminal 50 via the NFC I / F 22.

  Therefore, the normal request process ends as “error END”. Accordingly, the MFP 10 determines NO in S18 of FIG. 2 and does not execute the change process of S20. On the other hand, when receiving the scan NG information from the MFP 10, the portable terminal 50 transmits NFC information including at least information indicating a re-request and information indicating a scan function to the MFP 10.

  The MFP 10 receives NFC information from the portable terminal 50 via the NFC I / F 22 (YES in S10 of FIG. 2). In this case, in S76 of FIG. 4, the MFP 10 activates a scan monitoring thread.

  Therefore, the re-request process ends as “normal END”. Thereby, the MFP 10 determines YES in S18 of FIG. 2 and executes the change process of S20. However, in the change process of S20, the MFP 10 determines YES in S102 of FIG. This is because the MFP 10 and the portable terminal 50 belong to the same wireless network. For this reason, in S <b> 120, the MFP 10 transmits information indicating that setting change is unnecessary to the portable terminal 50 via the NFC I / F 22. In this case, the MFP 10 skips the process of S26 of FIG.

When the state of the MFP 10 changes from the scan impossible state to the scan ready state, in the scan monitoring thread, the MFP 10 executes a scan process, and then executes a communication process for transmitting scan data. As a result, the MFP 10 causes the portable terminal 50 to
The scan function can be executed in accordance with the instructions from.

  Although not shown as a specific case, the terminal ID “ID50” included in the NFC information transmitted from the portable terminal 50 to the MFP 10 is not registered in the SFL information 36 (that is, ID-function information). In this case, the MFP 10 determines NO in S <b> 42 or S <b> 48 in FIG. 3, and transmits the print NG information or the scan NG information including the NG reason caused by the SFL to the portable terminal 50. In this case, the normal request process ends as “error END”. Accordingly, the MFP 10 determines NO in S18 of FIG. 2 and does not execute the change process of S20. Further, the portable terminal 50 does not transmit the NFC information including the information indicating the re-request to the MFP 10 in order to receive the print NG information or the scan NG information including the NG reason caused by the SFL.

(Effect of this embodiment)
As described above, when the NFC information is received from the portable terminal 50 via the NFC I / F 22, the MFP 10 determines whether the MFP 10 is in a non-error state or an error state. (S44, S52 in FIG. 3). As shown in case A of FIG. 6, when the MFP 10 determines that the state of the MFP 10 is a non-error state, the MFP 10 executes the change process of S <b> 20 of FIG. 2 and performs the change via the wireless LAN I / F 20. The target data (print data or scan data) can be appropriately executed with the portable terminal 50. As a result, the MFP 10 can appropriately execute the print function or the scan function in accordance with an instruction from the portable terminal 50. On the other hand, as shown in cases C and D of FIGS. 12 and 13, when the MFP 10 is determined to be in an error state, the MFP 10 does not execute the change process of S20 of FIG. Accordingly, it is possible to suppress the occurrence of the event that the change process is executed even though the MFP 10 is in an error state. Thereby, the processing load of the MFP 10 can be reduced. In this way, the MFP 10 can execute an appropriate operation according to the determination result regarding the state of the MFP 10.

  Further, when the NFC information is received from the portable terminal 50 via the NFC I / F 22, the MFP 10 determines whether or not the function can be used by the portable terminal 50 (S42 and S48 in FIG. 3). . As shown in case B of FIG. 11, when it is determined that the NFC information includes information indicating the print function and the portable terminal 50 can use the print function (YES in S42 of FIG. 3), The MFP 10 can appropriately execute the print data with the portable terminal 50 via the wireless LAN I / F 20 by executing the change process of S20 of FIG. As a result, the MFP 10 can appropriately execute the printing function in accordance with an instruction from the portable terminal 50. On the other hand, when it is determined that the NFC information includes information indicating the scan function and the portable terminal 50 cannot use the scan function (NO in S48 in FIG. 3), the MFP 10 performs S20 in FIG. Do not execute the change process. Thereby, although the portable terminal 50 cannot use a scanning function, it can suppress that the event that a change process is performed generate | occur | produces. Thereby, the processing load of the MFP 10 can be reduced. As described above, the MFP 10 can execute an appropriate operation according to the determination result regarding the use of the function by the portable terminal 50.

(Correspondence)
The MFP 10 is an example of a “function execution device”. The NFC I / F 22 and the wireless LAN I / F 20 are examples of the “first type interface” and the “second type interface”, respectively. In case B of FIG. 11, “printing function” and “scanning function” are examples of “first function” and “second function”, respectively. NFC information including information indicating a normal request is an example of “first information”. The SSID and BSSID included in the NFC information are an example of “relation information”. Further, NFC information including information indicating a re-request and information indicating a printing function, and NF including information indicating a re-request and information indicating a scanning function
The C information is an example of “second information” and “third information”, respectively. The SFL information 36 (that is, ID-function information and public information) is an example of “permission information”. The print NG information and the scan NG information are examples of “impossible information”. The G / O state and the client state are examples of the “master station state” and the “slave station state”, respectively. S112 in FIG. 5 is an example of “device number determination process”.

  Specific examples of the present invention have been described in detail above, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. The modifications of the above embodiment are listed below.

(Modification 1) The “function execution device” is not limited to a multi-function device capable of executing the print function and the scan function, and may be a printer that can execute only the print function of the print function and the scan function. The scanner may be capable of executing only the scan function of the print function and the scan function. The “function execution device” is a device (for example, a PC, a server, a mobile phone, a smartphone, etc.) that executes a function (for example, an image display function, a data calculation function) different from the print function and the scan function. May be.

(Modification 2) The “specific function” may be a “print function” or a “scan function” as in case A of FIG. 6, or may be a function different from the print function and the scan function. Good. For example, when the different function is an image display function, the image data representing the image is an example of “target data”. For example, when the different function is a data calculation function, the data to be calculated is an example of “target data”.

(Modification 3) The combination of the “first type interface” and the “second type interface” is not limited to the combination of the NFC I / F and the wireless LAN I / F. For example, when the wireless LAN I / F is adopted as the “second type interface”, the “first type interface” may be an interface for executing infrared communication, or Bluetooth (registered trademark). It may be an interface for executing “Transfer Jet” or an interface for executing “Transfer Jet”. In addition, when NFC I / F is adopted as the “first type interface”, the “second type interface” may be an interface for executing wired communication, or Bluetooth (registered trademark) may be used. It may be an interface for execution. Generally speaking, it is only necessary that the communication speed of communication through the second type interface is higher than the communication speed of communication through the first type interface.

(Modification 4) The “first type interface” and the “second type interface” are physically two interfaces (that is, two separate IC chips) as in the above embodiment. There may be one physical interface (that is, two types of communication are realized by one IC chip).

(Modification 5) The “change process” is not limited to each process in FIG. 5, and includes all processes for changing the interface for communicating with the mobile terminal from the first type interface to the second type interface. . For example, the following processes can be exemplified.

(Modification 5-1) For example, in the case of YES in S106 of FIG. 5 (that is, when the MFP 10 is in the client state), the changing unit 42 changes the state of the MFP 10 from the client state to the device state (ie, , The MFP 10 is removed from the WFD network), and then the process may proceed to S114 (spontaneous G / O mode) (an example of “change process”).

(Modification 5-2) For example, when YES in S106 of FIG. 5 (that is, when the MFP 10 is in the client state), the changing unit 42 uses the wireless setting used in the WFD network to which the MFP 10 currently belongs. (In other words, wireless settings generated by a G / O device different from the MFP 10) may be transmitted to the portable terminal 50 via the NFC I / F 22 (an example of “change processing”). Thereby, the portable terminal 50 can establish a WFD connection with the G / O device (that is, can participate in the WFD network). Therefore, the function execution unit 43 can execute communication processing of target data with the mobile terminal 50 via the G / O device.

(Modification 5-3) For example, in the case of YES in S100 of FIG. 5 (that is, when the MFP 10 currently belongs to a wireless network) and the wireless network to which the MFP 10 belongs is configured by the AP 6 In the case of a normal Wi-Fi network, the changing unit 42 changes the wireless setting (that is, the wireless setting generated by the AP 6) used in the normal Wi-Fi network to the mobile phone via the NFC I / F 22. You may transmit to the terminal 50 (an example of a "change process"). Thereby, the portable terminal 50 can establish a normal Wi-Fi connection with the AP 6 (that is, it can participate in the normal Wi-Fi network). Accordingly, the function execution unit 43 can execute communication processing of target data with the portable terminal 50 via the AP 6.

(Modification 5-4) For example, the NFC information may include a wireless setting used in a wireless network (WFD network or normal Wi-Fi network) to which the mobile terminal 50 currently belongs. For example, when S100 in FIG. 5 is NO (that is, when the MFP 10 does not currently belong to the wireless network) or when S102 is NO (that is, when the MFP 10 and the portable terminal 50 do not belong to the same network). The changing unit 42 may newly join the wireless network to which the mobile terminal 50 currently belongs using the wireless setting in the NFC information (an example of “change processing”). In this case, the function execution unit 43 can execute the target data communication process with the portable terminal 50 using the newly joined wireless network.

(Modification 5-5) For example, the NFC information may include the IP address of the mobile terminal 50 used in the wired network to which the mobile terminal 50 currently belongs. For example, when an interface for executing wired communication is adopted as the “second type interface”, the changing unit 42 sends information indicating that wired communication is executed via the NFC I / F 22. You may transmit to the portable terminal 50. In this case, the function execution unit 43 can execute communication processing of the target data with the portable terminal 50 via the wired network.

(Modification 6) The normal request process of FIG. 3 may be configured to skip S42 and proceed to S44 after the “printing function” is determined in S40. Further, the normal request process of FIG. 3 may be configured to skip S48 and S50 and proceed to S52 after the “scan function” is determined in S40. That is, the control unit 30 includes the state determination unit 41, but may not include the usage determination unit 45.

(Modification 7) The normal request process of FIG. 3 may be configured to skip S44 and proceed to “normal END” when YES in S42. Further, in the case of YES in S48, it may be configured to skip S52 to S60 and proceed to “normal END”. That is, the control unit 30 includes the usage determination unit 45, but may not include the state determination unit 41.

(Modification 8) The “permission information” is not limited to the SFL information 36 but includes any information indicating whether or not the mobile terminal can use a specific function. For example, the following information can be exemplified.

(Modification 8-1) The memory 34 has a user ID, information indicating whether the print function is “OK” or “NG”, and whether the scan function is “OK” or “NG”. May be stored user-function information associated with information indicating. The NFC information may include the user ID of the user of the mobile terminal 50 instead of the terminal ID of the mobile terminal 50. The usage determination unit 45 may determine whether or not the user of the mobile terminal 50 can use a specific function by using the user ID in the NFC information and the user-function information. In this modification, the user-function information is an example of “permission information”.

(Modification 8-2) The memory 34 may store the above-described user-function information and terminal-user information. The terminal-user information may be information in which a terminal ID and a user ID are associated with each other. The NFC information may include the terminal ID of the portable terminal 50. The use determination unit 45 specifies the user ID using the terminal ID in the NFC information and the terminal-user information, and then uses the specified user ID and the user-function information to carry the mobile phone. The user of the terminal 50 may determine whether or not a specific function can be used. In this modification, a combination of user-function information and terminal-user information is an example of “permission information”.

(Modification 8-3) The memory 34 may not store the SFL information 36 in which the terminal ID is associated with the function OK or NG. The user may be able to designate whether the SFL function of the MFP 10 is valid or invalid by operating the operation unit 12. The memory 34 may store valid information when the SFL function = valid is designated, and may store invalid information when the SFL function = invalid is designated. In this case, the usage determination unit 45 receives the terminal ID from the portable terminal 50 or does not receive it, and if the invalid information is stored in the memory 34, the portable terminal 50 performs all functions (ie, printing). Function, scan function) can be used, and when the valid information is stored in the memory 34, the mobile terminal 50 may determine that none of the functions can be used. In this modification, valid information and invalid information are examples of “permission information”.

(Modification 9) In the above-described embodiment, the receiving unit 40 performs information about a function (printing function or scanning function) by performing one NFC wireless communication with the portable terminal 50, and the portable terminal 50. And NFC information including related information (SSID, BSSID) related to the wireless network to which the currently belongs. Instead, the reception unit 40 performs NFC wireless communication with the mobile terminal 50 to receive NFC information including information indicating the function, and then performs NFC wireless communication with the mobile terminal 50 again. By executing, NFC information including relation information may be received. That is, the “first information” including the “function execution request” and the “related information” may be information received by one NFC wireless communication as in the above-described embodiment. However, as in this modification, the information may be received by multiple times of NFC wireless communication.

(Modification 10) In the above-described embodiment, the receiving unit 40 performs one NFC wireless communication with the mobile terminal 50, thereby indicating information indicating a re-request and size information indicating the data size of print data. NFC information including these is received. Instead, the receiving unit 40 receives NFC information including information indicating a re-request by performing NFC wireless communication with the mobile terminal 50, and then performs NFC wireless communication with the mobile terminal 50. By executing again, NFC information including size information may be received. That is, the “second information” may be information received by one-time NFC wireless communication as in the above-described embodiment, or multiple times of NFC-type as in the present modification. It may be information received by wireless communication.

(Modification 11) In the above-described embodiment, the state determination unit 41 can print by the MFP 10 using all of the three determination criteria of the remaining amount of consumables, the remaining amount of the print medium, and the hardware state. It is determined whether or not it is in a state (S44 in FIG. 3). Instead, the state determination unit 41 may execute the determination using only one determination criterion among the above three determination criteria, or two determinations among the above three determination criteria. The determination may be performed using only the reference. In other words, the state determination unit 41 may perform determination using at least one of the three determination criteria described above.

(Modification 12) In each of the above embodiments, each of the units 40 to 47 is realized by software. However, at least one of the units 40 to 47 may be realized by hardware such as a logic circuit.

  The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

  2: Communication system, 10: Multi-function device (MFP), 30: Control unit, 32: CPU, 34: Memory, 36: SFL information

Claims (7)

A function execution device,
A first type interface for communicating with a mobile terminal;
A second type interface for performing communication with the portable terminal, wherein a communication speed of communication via the second type interface is higher than a communication speed of communication via the first type interface. The second type interface;
A control unit,
The controller is
A receiving unit that receives first information including an execution request for a specific function from the portable terminal via the first type interface, wherein the specific function communicates target data with the portable terminal. Including the communication process for performing,
When the first information is received, whether the state of the function execution device is a non-error state in which the specific function can be executed or an error state in which the specific function cannot be executed, The error state includes (1) a state where printing is not possible due to the remaining amount of consumables, and (2) a state where the remaining amount of printing medium is zero , (3) a state where the print medium is jammed in the print medium conveyance mechanism, (4) a state where the free space of the memory is equal to or smaller than a third value, and (5) the cover member of the function execution device is opened. The state determination unit, which is at least one state of:
When the state of the function execution device is determined to be the non-error state, an interface for communicating with the mobile terminal is changed from the first type interface to the second type interface. A changing unit that executes a changing process, and when the state of the function execution device is determined to be the error state, the changing unit that does not execute the changing process; and
A function execution unit that executes the specific function including the communication process via the second type interface when the change process is executed;
A function execution device comprising: The control unit further includes:
A storage control unit that stores permission information indicating whether or not the portable terminal can use the specific function in a memory of the function execution device;
A usage determination unit that determines whether the mobile terminal can use the specific function using the permission information in the memory when the first information is received;
The changing unit is
When the state of the function execution device is determined to be the non-error state and the mobile terminal is determined to be able to use the specific function, the change process is executed,
The function execution device according to claim 1, wherein when the mobile terminal is determined to be unable to use the specific function, the change process is not executed. The first information further includes related information related to a wireless network to which the mobile terminal currently belongs,
The function execution device according to claim 1, wherein the change unit executes the change process using the relationship information. The control unit further includes:
When it is determined that the state of the function execution device is the error state, impossible information indicating that the specific function cannot be executed via the first type interface is stored in the portable device. The function execution apparatus as described in any one of Claim 1 to 3 provided with the transmission part which transmits to a terminal. The control unit further includes:
5. The function execution device according to claim 1, further comprising: a wireless identifier transmission unit that transmits a wireless identifier to the mobile terminal via the first type interface.   The function execution device according to claim 5, wherein the wireless identifier transmission unit transmits the wireless identifier when a distance between the function execution device and the portable terminal is smaller than a distance at which radio waves can be transmitted. The control unit further includes:
A specific information receiving unit for receiving specific information from the portable terminal via the first type interface;
The function execution device according to claim 5 or 6, wherein the wireless identifier transmission unit transmits the wireless identifier when the specific information is received.

Images