JP6919738B2 - Communication device - Google Patents

Description

The technology disclosed in the present specification relates to an NFC method, which is a communication method according to an NFC (Near Field Communication) standard, and relates to a communication device that executes communication of target data to be communicated with an external device.

Patent Document 1 discloses a technique for two communication devices to execute wireless communication. In this technique, the two communication devices execute wireless communication of communication information by the NFC method. The communication information includes information for executing wireless communication according to a communication method different from the NFC method (for example, IEEE802.11a) (that is, information indicating the communication method, information indicating the encryption method). As a result, the two communication devices can execute wireless communication according to a communication method different from the NFC method.

JP-A-2007-166538

The present specification provides a technique for a communication device to appropriately communicate target data to be communicated with an external device by an NFC method.

One technique disclosed herein is a computer program for communication equipment. The computer program sets the computer of the communication device to the following parts, that is, the first communication method according to the first communication method between the communication device and the external device via the first communication interface of the communication device. After the first establishment unit for establishing the communication link and the first communication link are established, the first communication link is used from the external device via the first communication interface. A Read unit that reads communication setting information, the communication speed of the first communication method is slower than the communication speed of the second communication method, and the communication setting information is different from that of the first communication method. With the Read unit, which is communication according to a different second communication method and is information for the communication device to execute the communication via a second communication interface different from the first communication interface. After reading the communication setting information from the external device, the external device is made to function as a Write unit that writes a response indicating that the communication setting information has been read to the external device via the first communication interface. May be good.
Further, another technique disclosed by the present specification is an NFC method, which is a communication method according to an NFC standard, and is a communication device that executes communication of target data to be communicated with an external device. The communication device includes an NFC interface for executing NFC-type communication, a processor, and a memory for storing a program.
The processor follows each of the following steps, i.e., according to the program.
A first establishment command for establishing a first communication link between the communication device and the external device is communicated with the external device via the NFC interface to obtain the first communication link. The first establishment step to establish and
A first communication step of communicating the first target data with the external device via the NFC interface by using the first communication link.
A disconnection step of disconnecting the first communication link after communicating the first target data with the external device, and
After disconnecting the first communication link, a second establishment command for establishing a second communication link between the communication device and the external device is issued to the external device via the NFC interface. A second establishment step of communicating and establishing the second communication link,
It is a second communication step of communicating the second target data with the external device via the NFC interface by using the second communication link, and the second target data is the second target data. The second communication step, which is the data generated by processing the target data of 1.
To execute.

According to the above configuration, the communication device uses the first communication link to communicate the first target data with the external device, and then uses the same first communication link to perform the second target data. Instead of communicating, the first communication link is temporarily disconnected. After that, the communication device newly establishes a second communication link and uses the second communication link to communicate the second target data with the external device. Therefore, the communication device can appropriately communicate both the first target data and the second target data generated by processing the first target data with the external device.

When the NFC interface executes a Listen operation of receiving a polling signal from the external device and transmitting a response signal to the polling signal to the external device, the first establishment step is the first establishment. It may include a step of receiving a command. When the NFC interface executes a Poll operation of transmitting a polling signal to the external device and receiving a response signal for the polling signal from the external device, the first establishment step is the first establishment. It may include a step of sending a command. According to this configuration, the communication device can appropriately communicate the first establishment command with the external device depending on whether the NFC interface executes the Listen operation or the Poll operation.

In the first establishment step, when the first establishment command is received from the external device, the disconnection step disconnects the first communication link by using the first disconnection method. It may include steps. In the second case of transmitting the first establishment command to the external device in the first establishment step, the cutting step uses a second cutting method different from the first cutting method. The step of disconnecting the first communication link may be included. According to this configuration, the communication device responds to each of the first case of receiving the first establishment command from the external device and the second case of transmitting the first establishment command to the external device. , Use different cutting methods. For this purpose, the communication device can appropriately disconnect the first communication link by using an appropriate disconnection method.

The first communication link may be a communication link for each of the communication device and the external device to communicate in accordance with the P2P mode of the NFC standard. According to this configuration, the communication device can appropriately communicate the first target data with the external device according to the P2P mode of the NFC standard.

According to the program, in the first establishment step, the processor receives the first establishment command from the external device, while the first communication link is established. A confirmation command for confirming whether or not to maintain the first communication link is received from the external device via the NFC interface, and a response command to the confirmation command is sent via the NFC interface. Then, the first confirmation step of transmitting to the external device may be executed. In the first case, the disconnect step stops execution of the first confirmation step, and then disconnects from the external device via the NFC interface to disconnect the first communication link. It may include a step of receiving a command and transmitting a response command to the disconnect command to the external device via the NFC interface. According to this configuration, the communication device can appropriately disconnect the first communication link in the first case of receiving the first establishment command from the external device.

In the first establishment step, when the first establishment command is received from the external device, the disconnection step may include a step of temporarily stopping the operation of the NFC interface. .. According to this configuration, the communication device can appropriately disconnect the first communication link in the first case of receiving the first establishment command from the external device.

In the second case of transmitting the first establishment command to the external device in the first establishment step, the disconnection step sends a disconnect command for disconnecting the first communication link to the NFC interface. It may include a step of transmitting to the external device via the above and receiving a response command for the disconnect command from the external device via the NFC interface. According to this configuration, the communication device can appropriately disconnect the first communication link in the second case of transmitting the first establishment command to the external device.

According to the program, the processor further transmits the first establishment command to the external device in the first establishment step while the first communication link is established. , A confirmation command for confirming whether or not to maintain the first communication link is transmitted to the external device via the NFC interface, and the external device sends a confirmation command to the external device via the NFC interface. A second confirmation step may be performed to receive a response command to the confirmation command. In the second case, the cutting step may include a step of stopping the execution of the second confirmation step. According to this configuration, the communication device can appropriately disconnect the first communication link in the second case of transmitting the first establishment command to the external device.

In the first communication link, one of the communication device and the external device communicates according to the Reader / Writer mode of the NFC standard, and the other of the communication device and the external device communicates according to the Card Emulsion mode of the NFC standard. It may be a communication link for the purpose. According to this configuration, the communication device can appropriately communicate the first target data with the external device according to the Reader / Writer mode of the NFC standard or the Card Emulation mode.

In the first establishment step, when the first establishment command is received from the external device, the disconnection step is performed from the external device via the NFC interface. It may include a step of receiving a disconnect command for disconnecting and transmitting a response command to the disconnect command to the external device via the NFC interface. According to this configuration, the communication device can appropriately disconnect the first communication link in the first case of receiving the first establishment command from the external device.

In the second case of transmitting the first establishment command to the external device in the first establishment step, the disconnection step sends a disconnect command for disconnecting the first communication link to the NFC interface. It may include a step of transmitting to the external device via the above and receiving a response command for the disconnect command from the external device via the NFC interface. According to this configuration, the communication device can appropriately disconnect the first communication link in the second case of transmitting the first establishment command to the external device.

The NFC interface may perform a Listen operation of receiving a polling signal from the external device and transmitting a response signal to the polling signal to the external device. According to the program, after executing the disconnection step, the processor executes an operation control step for controlling the operation of the NFC interface so that the NFC interface does not execute the Listen operation for a predetermined period of time. You may. According to this configuration, the communication device does not allow the NFC interface to perform a Listen operation for a predetermined period of time. Therefore, the communication device can properly operate the external device after communicating the first target data.

The NFC interface may perform a Poll operation of transmitting a polling signal to the external device and receiving a response signal to the polling signal from the external device. According to the program, after executing the disconnection step, the processor executes an operation control step for controlling the operation of the NFC interface so that the NFC interface does not execute the Poll operation for a predetermined period of time. You may. According to this configuration, the communication device does not allow the NFC interface to perform the Poll operation for a predetermined period of time. Therefore, the communication device can properly operate the external device after communicating the first target data.

When the communication device should receive the first target data from the external device, (A) in the first establishment step, the communication device communicates according to the Card Emulation mode of the NFC standard, and the communication device communicates with the external device. The external device may include a step of establishing the first communication link for communicating according to the Writer mode of the NFC standard, and (B) the first communication step utilizes the first communication link. Then, the step of receiving the first target data from the external device may be included. (C) In the second establishment step, the communication device communicates according to the Writer mode of the NFC standard, and the communication device is used. The external device may include a step of establishing the second communication link for the external device to communicate according to the NFC standard Card Emulation mode. (D) The second communication step is the second communication link. May include a step of transmitting the second target data to the external device by utilizing the above. According to this configuration, the communication device can appropriately receive the first target data from the external device and appropriately transmit the second target data to the external device.

When the communication device should transmit the first target data to the external device, (A) in the first establishment step, the communication device communicates according to the Card Emulation mode of the NFC standard, and the communication device communicates with the external device. The external device may include a step of establishing the first communication link for communicating according to the Reader mode of the NFC standard, and (B) the first communication step utilizes the first communication link. Then, the step of transmitting the first target data to the external device may be included. (C) In the second establishment step, the communication device communicates according to the Reader mode of the NFC standard, and the communication device communicates with the external device. The external device may include a step of establishing the second communication link for the external device to communicate according to the NFC standard Card Emulation mode. (D) The second communication step is the second communication link. May include a step of receiving the second target data from the external device by utilizing the above. According to this configuration, the communication device can appropriately transmit the first target data to the external device and appropriately receive the second target data from the external device.

When the communication device should receive the first target data from the external device, (A) in the first establishment step, the communication device communicates according to the Reader mode of the NFC standard, and the external device is used. The device may include the step of establishing the first communication link for communicating according to the NFC standard Card Emulation mode, and (B) the first communication step utilizes the first communication link. Then, the step of receiving the first target data from the external device may be included. (C) In the second establishment step, the communication device communicates according to the Writer mode of the NFC standard, and the communication device is used. The external device may include a step of establishing the second communication link for the external device to communicate according to the NFC standard Card Emulation mode. (D) The second communication step is the second communication link. May include a step of transmitting the second target data to the external device by utilizing the above. According to this configuration, the communication device can appropriately receive the first target data from the external device and appropriately transmit the second target data to the external device.

When the communication device should receive the first target data from the external device, (A) the first establishment step is that the communication device operates according to the Reader mode of the NFC standard and the external device. The device may include the step of establishing the first communication link for operating according to the NFC standard Card Emulation mode, and (B) the first communication step utilizes the first communication link. Then, the step of receiving the first target data from the external device may be included. (C) In the second establishment step, the communication device operates according to the Card Emulation mode of the NFC standard. The external device may include a step of establishing the second communication link for operating according to the Reader mode of the NFC standard. (D) The second communication step is the second communication link. May include a step of transmitting the first target data to the external device by utilizing the above. According to this configuration, the communication device can appropriately receive the first target data from the external device and appropriately transmit the second target data to the external device.

When the communication device should transmit the first target data to the external device, (A) in the first establishment step, the communication device communicates according to the Writer mode of the NFC standard, and the external device is used. The device may include the step of establishing the first communication link for communicating according to the NFC standard Card Emulation mode, and (B) the first communication step utilizes the first communication link. Then, the step of transmitting the first target data to the external device may be included. (C) In the second establishment step, the communication device communicates according to the Reader mode of the NFC standard, and the communication device communicates with the external device. The external device may include a step of establishing the second communication link for the external device to communicate according to the NFC standard Card Emulation mode. (D) The second communication step is the second communication link. May include a step of receiving the second target data from the external device by utilizing the above. According to this configuration, the communication device can appropriately transmit the first target data to the external device and appropriately receive the second target data from the external device.

When the communication device should transmit the first target data to the external device, (A) in the first establishment step, the communication device communicates according to the Writer mode of the NFC standard, and the external device is used. The device may include the step of establishing the first communication link for communicating according to the NFC standard Card Emulation mode, and (B) the first communication step utilizes the first communication link. Then, the step of transmitting the first target data to the external device may be included. (C) In the second establishment step, the communication device communicates according to the Card Emulation mode of the NFC standard. The external device may include a step of establishing the second communication link for communicating according to the Writer mode of the NFC standard. (D) The second communication step is the second communication link. May include a step of receiving the second target data from the external device by utilizing the above. According to this configuration, the communication device can appropriately transmit the first target data to the external device and appropriately receive the second target data from the external device.

The processor may further perform a determination step according to the program to determine whether transmission information indicating that data transmission should be executed is stored in the memory. When it is determined in the determination step that the transmission information is stored in the memory when the first target data should be communicated with the external device, the first communication step is the said. It may include a step of transmitting the first target data to the external device by using the first communication link. When it is determined in the determination step that the transmission information is not stored in the memory when the first target data should be communicated with the external device, the first communication step is the said. The first communication link may be used to include a step of receiving the first target data from the external device. When the second target data should be communicated with the external device, when it is determined in the determination step that the transmission information is stored in the memory, the second communication step is the said. A step of transmitting the second target data to the external device by using the second communication link may be included. When the second target data should be communicated with the external device, if it is determined in the determination step that the transmission information is not stored in the memory, the second communication step is described. The second communication link may be used to include a step of receiving the second target data from the external device. According to this configuration, the communication device can appropriately transmit or receive the target data according to the determination result regarding whether or not the transmission information is stored in the memory.

When it is determined in the determination step that the transmission information is stored in the memory when the first target data should be communicated with the external device, the first establishment step is the said. It may include the step of establishing the first communication link according to the transmission mode for the communication device to perform data transmission. When it is determined in the determination step that the transmission information is not stored in the memory when the first target data should be communicated with the external device, the first establishment step is the said. It may include the step of establishing the first communication link according to the receiving mode for the communication device to perform data reception. When it is determined in the determination step that the transmission information is stored in the memory when the second target data is to be communicated with the external device, the second establishment step is the said. It may include the step of establishing the second communication link according to the transmission mode. When it is determined in the determination step that the transmission information is not stored in the memory when the second target data should be communicated with the external device, the second establishment step is the determination step. It may include a step of establishing the second communication link according to the receiving mode. According to this configuration, the communication device can appropriately establish a communication link according to the transmission mode or the reception mode, depending on the determination result regarding whether or not the transmission information is stored in the memory.

According to the program, the processor erases the transmission information from the memory when transmitting the first target data to the external device in the first communication step, and the first communication step. In the above, when the external device is received from the first target data, a memory control step of storing the transmission information in the memory may be executed. According to this configuration, the communication device appropriately transmits the transmission information according to each case of transmitting the first target data to the external device and receiving the first target data from the external device. Can be managed.

It is determined that the processor should operate according to the program and further according to the NFC standard P2P mode, and in the determination step, the transmission information is stored in the memory. In this case, the external device is notified that the communication device executes data transmission, the communication device should operate in accordance with the P2P mode of the NFC standard, and the transmission is performed in the determination step. If it is determined that the information is not stored in the memory, a notification step may be performed to notify the external device that the communication device will perform data reception. According to this configuration, when the communication device should operate according to the P2P mode of the NFC standard, the communication device executes data transmission according to the determination result regarding whether or not the transmission information is stored in the memory. It is possible to appropriately notify the external device whether to execute data reception or data reception. For this reason, the communication device can properly operate the external device.

According to the processor, the communication device should operate according to the Reader / Writer mode of the NFC standard, and the transmission information is stored in the memory in the determination step. When it is determined, it is determined that the communication device should operate according to the Writer mode, the communication device should operate according to the Reader / Writer mode of the NFC standard, and the transmission in the determination step. If it is determined that the information is not stored in the memory, a determination step may be performed to determine that the communication device should operate according to the Reader mode. According to this configuration, when the communication device should operate according to the Reader / Writer mode of the NFC standard, whether the communication device should operate according to the Reader mode according to the judgment result regarding whether or not the transmission information is stored in the memory. It is possible to appropriately determine whether or not to operate according to the Writer mode.

According to the program, when the processor receives the first target data from the external device in the first communication step, the processor processes the first target data to obtain the second target data. A processing step for generating the target data may be executed. According to this configuration, the communication device can appropriately generate the second target data by processing the first target data.

One technique disclosed in the present specification is the NFC method, which is a communication method according to the NFC standard, and is a communication device that executes communication of target data to be communicated with an external device.
Communication equipment
The first communication link for establishing the first communication link according to the NFC method is communicated with the external device between the communication device and the external device to establish the first communication link. The first means of establishment and
A first communication means for communicating the first target data with the external device by using the first communication link, and
A disconnecting means for disconnecting the first communication link after communicating the first target data with the external device.
After disconnecting the first communication link, a second establishment command for establishing a second communication link according to the NFC method between the communication device and the external device is transmitted to the external device. The second establishment means for establishing the second communication link and
A second communication means for communicating the second target data generated by processing the first target data with the external device by using the second communication link.
To be equipped.

According to the above configuration, the communication device can appropriately communicate both the first target data and the second target data generated by processing the first target data with the external device. can.

One technique disclosed in the present specification is the NFC method, which is a communication method according to the NFC standard, and is a communication device that executes communication of target data to be communicated with an external device. The communication device includes an NFC interface for executing NFC-type communication, a processor, and a memory for storing a program.
The processor follows each of the following steps, i.e., according to the program.
Transmission information indicating that data transmission should be executed when the establishment command for establishing a communication link between the communication device and the external device is communicated with the external device via the NFC interface. A determination step for determining whether or not the data is stored in the memory, and
In the determination step, when it is determined that the transmission information is not stored in the memory, the first target data is transmitted from the external device via the NFC interface by using the communication link. Receive step to receive and
A processing step of generating the second target data by processing the first target data when receiving the first target data from the external device, and
A memory control step for storing the transmission information in the memory when the first target data is received from the external device, and
A disconnection step of disconnecting the communication link after receiving the first target data from the external device, and
In the determination step, when it is determined that the transmission information is stored in the memory, the second target data is transmitted to the external device via the NFC interface by using the communication link. Send to send step and
A communication device that executes.

According to the above configuration, the communication device can appropriately receive the first target data from the external device and then appropriately transmit the second target data to the external device by using the transmission information. ..

A control method for realizing the above-mentioned communication device, a computer program, and a computer-readable recording medium for storing the computer program are also new and useful. In addition, a communication system including the above-mentioned communication device and an external device is also new and useful.

The configuration of the communication system is shown. The flowchart of the Listen processing of the MFP is shown. The following flowchart of FIG. 2 is shown. The flowchart of the Poll processing of the MFP is shown. The following flowchart of FIG. 4 is shown. The sequence chart of case A1 which is an example of communication of P2P mode is shown. The sequence chart of case A2 which is an example of communication of P2P mode is shown. The sequence chart of case A3 which is an example of communication of P2P mode is shown. The sequence chart of case A4 which is an example of communication of P2P mode is shown. The sequence chart of case B1 which is an example of communication of R / W mode and CE mode is shown. The sequence chart of case B2 which is an example of communication of R / W mode and CE mode is shown. The sequence chart of cases B3 to B8 which is an example of communication of R / W mode and CE mode is shown.

(Configuration of communication system 2)
As shown in FIG. 1, the communication system 2 includes a multifunction device (hereinafter referred to as "MFP (abbreviation of Multi-Function Peripheral)") 10 and a mobile terminal 50. The MFP 10 and the mobile terminal 50 can execute communication of the NFC standard communication method (that is, the NFC method). In this embodiment, the NFC standard is an ISO / IEC21481 or ISO / IEC18092 international standard. NFC communication is wireless communication using radio waves in the 13.56 MHz band. Further, the MFP 10 and the mobile terminal 50 can execute wired communication or wireless communication by using a communication network different from the NFC type communication link, respectively.

(Configuration of MFP10)
The MFP 10 includes an operation unit 12, a display unit 14, a network interface (hereinafter, the interface is referred to as "I / F") 16, a print execution unit 18, a scan execution unit 20, and an NFC I /. It includes an F22 and a control unit 30. The operation unit 12 includes a plurality of keys. The user can input various instructions to the MFP 10 by operating the operation unit 12. The display unit 14 is a display for displaying various information. The network I / F 16 may be an I / F for connecting to a wired network or an I / F for connecting to a wireless network. This wireless network is a network for executing wireless communication different from NFC communication. For example, the IEEE (Institute of Electrical and Electronics Engineers, Inc.) standard of 802.11 and , A network that complies with standards (for example, 802.1a, 11b, 11g, 11n, etc.). The print execution unit 18 is a printing mechanism such as an inkjet method or a laser method. The scan execution unit 20 is a scanning mechanism for a CCD, CIS, or the like.

The NFC I / F22 is an interface for executing NFC-type communication. The NFC I / F22 is composed of a chip different from the network I / F16. When the network I / F16 is an I / F for connecting to a wireless network, the network I / F16 and the NFC I / F22 are different from each other in the following points.

That is, the communication speed of wireless communication via the network I / F16 is faster than the communication speed of wireless communication via the NFC I / F22. Further, the frequency of the carrier wave in the wireless communication via the network I / F16 is different from the frequency of the carrier wave in the wireless communication via the NFC I / F22. Further, when the distance between the MFP 10 and the mobile terminal 50 is about 10 cm or less, the MFP 10 can execute NFC-type communication with the mobile terminal 50 via the NFC I / F22. On the other hand, regardless of whether the distance between the MFP 10 and the mobile terminal 50 is 10 cm or less or 10 cm or more, the MFP 10 can execute wireless communication with the mobile terminal 50 via the network I / F16. That is, the maximum distance that the MFP 10 can perform wireless communication with the communication destination device (for example, the mobile terminal 50) via the network I / F 16 is the maximum distance that the MFP 10 can perform wireless communication with the communication destination device via the NFC I / F 22. And greater than the maximum distance that wireless communication can be performed. In the following, wireless communication via the network I / F16 will be referred to as "network wireless communication".

The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the programs 36 and 38 stored in the memory 34. The memory 34 is composed of a ROM, a RAM, a hard disk, and the like. The memory 34 stores the above programs 36 and 38 executed by the CPU 32. The application program 36 is a program for the CPU 32 to execute the processing of the application layer of the OSI reference model.

The protocol stack 38 is a program for the CPU 32 to execute processing in a layer lower than the application layer of the OSI reference model. The protocol stack 38 includes a P2P (abbreviation of Peer to Peer) program, an R / W program, and a CE program. The P2P program is a program for executing processing according to the P2P mode of the NFC standard. The R / W program is a program for executing processing according to the Reader / Writer mode of the NFC standard. The CE program is a program for executing processing according to the CE (abbreviation of Card Emulation) mode of the NFC standard. These programs are programs for executing processing conforming to the NFC standard defined by the NFC Forum.

The memory 34 further stores "0" or "1" as a transmission flag. The transmission flag is a flag indicating whether or not the MFP 10 should transmit the target data to be communicated. That is, in the situation where the MFP 10 should transmit the target data, the transmission flag is set to "1". Further, in the situation where the MFP 10 should not transmit the target data, the transmission flag is set to "0".

The memory 34 further stores "0" or "1" as the communication completed flag. As will be described in detail later, between the MFP 10 and the mobile terminal 50, after the first target data is transmitted from one device to the other device by NFC communication, the other device sends the first target data to the other device. The second target data is transmitted to the device by NFC communication. Hereinafter, the execution of the communication of the first target data and then the communication of the second target data in this way is referred to as "one set of communication". The communication completed flag is a flag indicating whether the communication of the first target data is executed or the communication of the first target data is not executed in one set of communication. That is, in the situation where the communication of the first target data is executed, the communication completed flag is set to "1". Further, in the situation where the communication of the first target data is not executed, the communication completed flag is set to "0".

(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 playback device, a portable moving image playback device, or the like. The mobile terminal 50 includes a network I / F for connecting to a wireless network and an NFC I / F. Therefore, the mobile terminal 50 can execute wireless communication with the MFP 10 via the network I / F, and can execute wireless communication with the MFP 10 using the NFC I / F.

The mobile terminal 50 includes an application program (hereinafter, referred to as an “MFP application”) for causing the MFP 10 to execute various functions (for example, a printing function, a scanning function, etc.). The application for the MFP may be installed on the mobile terminal 50 from the server provided by the vendor of the MFP 10, or may be installed on the mobile terminal 50 from the media shipped together with the MFP 10.

(Target data to be communicated)
Various data can be considered as the first and second target data that are the targets of the above-mentioned one set of communication. Examples of the first and second target data are listed below.

(First example)
It is assumed that the MFP 10 receives print data from the mobile terminal 50 and should execute a print function according to the print data. The user of the mobile terminal 50 starts the application for the MFP of the mobile terminal 50 and inputs an instruction for causing the MFP 10 to execute the printing function to the mobile terminal 50. In this case, the mobile terminal 50 transmits the print execution instruction to the MFP 10 by using the NFC method communication. The print execution instruction does not include print data.

The MFP 10 receives a print execution instruction from the mobile terminal 50 via the NFC I / F22. As described above, the communication speed of NFC communication is slower than the communication speed of network wireless communication. Therefore, if the NFC method communication is used for the communication of the print data from the mobile terminal 50 to the MFP 10, it may take a long time to communicate the print data. Therefore, in this example, the MFP 10 adopts a configuration in which print data is received from the mobile terminal 50 by using network wireless communication. In order to adopt such a configuration, the mobile terminal 50 needs to know the wireless setting for executing network wireless communication with the MFP 10. Therefore, when the MFP 10 receives the print execution instruction from the mobile terminal 50, the MFP 10 transmits a response including the above radio setting to the mobile terminal 50 via the NFC I / F22.

As a result, the MFP 10 and the mobile terminal 50 can execute network wireless communication instead of the NFC method communication to communicate the print data. Therefore, the MFP 10 can execute the printing function. In this example, the response including the print execution instruction and the wireless setting is an example of the "first target data" and the "second target data", respectively.

(Second example)
It is assumed that the MFP 10 should execute a scan function of executing a scan to generate scan data and transmitting the scan data to the mobile terminal 50. The user of the mobile terminal 50 starts the application for the MFP of the mobile terminal 50 and inputs an instruction for causing the MFP 10 to execute the scanning function to the mobile terminal 50. In this case, the mobile terminal 50 transmits a scan execution instruction to the MFP 10 by using NFC communication.

The MFP 10 receives a scan execution instruction from the mobile terminal 50 via the NFC I / F22. Similar to the first example above, if the NFC method communication is used for the communication of the scan data from the MFP 10 to the mobile terminal 50, it may take a long time to communicate the scan data. For this purpose, in this example, the MFP 10 adopts a configuration in which the scan data is transmitted to the mobile terminal 50 by using network wireless communication. Therefore, when the MFP 10 receives the scan execution instruction from the mobile terminal 50, the MFP 10 transmits a response including the wireless setting to the mobile terminal 50 via the NFC I / F22.

As a result, the MFP 10 and the mobile terminal 50 can execute network wireless communication instead of the NFC method communication to communicate the scan data. Therefore, the MFP 10 can execute the scanning function. In this example, the response including the scan execution instruction and the wireless setting is an example of the "first target data" and the "second target data", respectively.

(Third example)
It is assumed that the mobile terminal 50 should transmit the setting information to be used by the MFP 10 to the MFP 10. As the above setting information, for example, print setting information for the MFP 10 to execute the print function (for example, print resolution, paper size, etc.), scan setting information for the MFP 10 to execute the scan function (for example, scan resolution, etc.). , Communication setting information (for example, IP address, subnet mask, gateway address, etc.) for the MFP 10 to execute the communication function can be mentioned.

The user of the mobile terminal 50 activates the application for the MFP of the mobile terminal 50 and inputs the setting information to be used by the MFP 10 into the mobile terminal 50. In this case, the mobile terminal 50 transmits the above setting information to the MFP 10 by using the NFC method communication.

The MFP 10 receives the setting information from the mobile terminal 50 via the NFC I / F22. The MFP 10 stores the received setting information in the memory 34 as the setting information that the MFP 10 should use. As a result, the MFP 10 can execute various functions by using the received setting information. When the MFP 10 receives the setting information from the mobile terminal 50, the MFP 10 transmits a response indicating that the setting information has been received to the mobile terminal 50 via the NFC I / F22. In this example, the setting information and the response are examples of "first target data" and "second target data", respectively.

(Fourth example)
It is assumed that the mobile terminal 50 should transmit the address information included in the address book currently used by the mobile terminal 50 to the MFP 10. The user of the mobile terminal 50 activates the application for the MFP of the mobile terminal 50 and inputs an instruction for transmitting the address information to the MFP 10 to the mobile terminal 50. In this case, the mobile terminal 50 transmits the address information to the MFP 10 by using the NFC method communication.

The MFP 10 receives the address information from the mobile terminal 50 via the NFC I / F22. The MFP 10 adds the received address information to the address book currently used by the MFP 10 (that is, the address book in the memory 34). As a result, the MFP 10 can execute the communication function by using the received address information. When the MFP 10 receives the address information from the mobile terminal 50, the MFP 10 transmits a response indicating that the address information has been received to the mobile terminal 50 via the NFC I / F22. In this example, the address information and the response are examples of "first target data" and "second target data", respectively.

(Fifth example)
In the above first example, the MFP 10 adopts a configuration in which print data is transmitted to the mobile terminal 50 by using network wireless communication. Instead, for example, the MFP 10 may receive print data from the mobile terminal 50 via the NFC I / F22. In this case, the MFP 10 may transmit a response indicating that the print data has been received to the mobile terminal 50 via the NFC I / F22. In this example, the print data and the response are examples of the "first target data" and the "second target data", respectively.

(6th example)
In the above first to fifth examples, in one set of communication, the transmission of the first target data from the mobile terminal 50 to the MFP 10 is executed, and then the second target data from the MFP 10 to the mobile terminal 50 is transmitted. The transmission is executed. However, in one set of communication, the transmission of the first target data from the MFP 10 to the mobile terminal 50 may be executed, and then the transmission of the second target data from the mobile terminal 50 to the MFP 10 may be executed. For example, the MFP 10 may transmit scan data to the mobile terminal 50 via the NFC I / F22 and receive a response from the mobile terminal 50 via the NFC I / F22. In this example, the scan data and the response are examples of "first target data" and "second target data", respectively.

The combination of the "first target data" and the "second target data" is not limited to the first to sixth examples described above, and may be other combinations. That is, the "first target data" may be any kind of data as long as it is the data to be communicated, and the "second target data" is obtained by processing the first target data. Any kind of data may be used as long as it is generated data (that is, data different from the first target data). The subject that generates the second target data may be the MDP 10 or the mobile terminal 50.

(NFC standard mode)
Next, each mode adopted in the NFC standard will be described. In the NFC standard, P2P mode, Reader / Writer mode (hereinafter, simply referred to as "R / W mode"), and CE mode are used. In the following, a device (MFP10, mobile terminal 50, etc.) capable of executing NFC-type communication will be referred to as an "NFC device".

Among NFC devices, there are devices that can use all of the above three modes, and there are devices that can use only one or two of the above three modes. In this embodiment, the MFP 10 is a device that can use all of the above three modes. However, the mobile terminal 50 may be a device that can use all of the above three modes, and of the above three modes, only two modes, the R / W mode and the CE mode, can be used. There may be.

(P2P mode)
The P2P mode is a mode for executing bidirectional communication between a pair of NFC devices.
For example, assume a situation in which both the first NFC device and the second NFC device operate according to the P2P mode. In this case, a communication link for executing communication according to the P2P mode is established between the first NFC device and the second NFC device. For example, the first NFC device transmits data to the second NFC device using a communication link. After that, the second NFC device usually uses the same communication link to transmit other data to the first NFC device. As a result, two-way communication is realized. NFC devices with a tag type of type A and NFC devices with a tag type of type F defined by the NFC Forum can operate according to P2P mode, while NFC devices with a tag type of type B are P2P. Cannot operate according to the mode.

(R / W mode, CE mode)
The R / W mode and the CE mode are modes for executing unidirectional communication between a pair of NFC devices. The CE mode is a mode for the NFC device to operate as a "card", which is a format defined by the NFC forum. An NFC device having a tag type of type A, an NFC device having a tag type of type F, and an NFC device having a tag type of type B can all operate according to the CE mode. The R / W mode is further divided into a Reader mode and a Writer mode. The Reader mode is a mode for reading data from an NFC device that operates as a card in the CE mode. The Writer mode is a mode for writing data to an NFC device that operates as a card in the CE mode. In Reader mode, data can also be read from an NFC standard card. In the Writer mode, data can also be written to an NFC standard card.

For example, assume a situation in which the first NFC device operates according to the Reader mode and the second NFC device operates according to the CE mode. In this case, a communication link is established between the first NFC device and the second NFC device to execute communication according to the Reader mode and the CE mode. The first NFC device receives the data from the second NFC device by executing an operation for reading data from the pseudo card in the second NFC device.

Further, for example, it is assumed that the first NFC device operates according to the Writer mode and the second NFC device operates according to the CE mode. In this case, a communication link is established between the first NFC device and the second NFC device to execute communication according to the Writer mode and the CE mode. The first NFC device transmits the data to the second NFC device by executing an operation for writing data to the pseudo card in the second NFC device.

As described above, in order for a pair of NFC devices to execute NFC-type communication, various combinations of modes can be considered. For example, as a combination of modes of the MFP 10 and the mobile terminal 50, the following five patterns, that is, "P2P mode, P2P mode", "Reader mode, CE mode", "Writer mode, CE mode", "CE mode, Reader" "Mode", "CE mode, Writer mode" can be considered.

(Poll operation and Listen operation)
The NFC device can perform the Poll operation and the Listen operation. More specifically, for example, in the MFP10, the NFC I / F22 executes the Poll operation and the Listen operation instead of the CPU 32 executing the Poll operation and the Listen operation according to the programs 36 and 38. The Poll operation is an operation of transmitting a polling signal and receiving a response signal to the polling signal. The Listen operation is an operation of receiving a polling signal and transmitting a response signal to the polling signal.

The NFC I / F22 of the MFP10 has a Poll mode for executing the Poll operation, a Listen mode for executing the Listen operation, and a mode in which neither the Poll operation nor the Listen operation is executed (hereinafter referred to as "non-execution mode"). (Call) and can operate in any of the modes. The NFC I / F22 operates sequentially in the Poll mode, the Listen mode, and the non-execution mode. For example, the NFC I / F22 performs a set of operations: operating in Poll mode, then operating in Listen mode, and then operating in non-execution mode. The NFC I / F22 repeatedly executes the above set of operations.

In Poll mode, the NFC I / F 22 transmits a polling signal and monitors the reception of the response signal. Specifically, the NFC I / F22 (1) transmits a polling signal (that is, a polling signal corresponding to the type A) that can be responded to by an NFC device having a tag type of type A, and receives the response signal. After monitoring for a predetermined time, (2) if no response signal is received, an NFC device of type B sends a responsive polling signal (that is, a polling signal corresponding to type B) and receives the response signal. (3) If the response signal is not received, an NFC device having a tag type of type F transmits a responsive polling signal (that is, a polling signal corresponding to the type F) of the response signal. The operation of monitoring reception for a predetermined time is repeated. When the NFC I / F 22 receives a response signal from the NFC device within a predetermined time, it can be said that the NFC device is a type of NFC device corresponding to the polling signal received immediately before the transmission of the response signal. When receiving the response signal, the NFC I / F 22 further transmits an inquiry signal to the NFC device asking which mode the NFC device that is the source of the response signal can operate. As a result, the NFC I / F 22 receives the operable mode signal from the NFC device. The operable mode signal indicates that the NFC device can operate in P2P mode and CE mode, or indicates that the NFC device can operate only in CE mode.

In the Listen mode, the NFC I / F22 monitors the reception of the polling signal, and when the polling signal is received, transmits a response signal. The NFC I / F22 transmits a response signal to the NFC device that is the source of the polling signal only when the polling signal of the type corresponding to the NFC I / F22 is received. When transmitting a response signal to the NFC device, the NFC I / F 22 receives an inquiry signal from the NFC device and transmits an operable mode signal to the NFC device. In the non-execution mode, the NFC I / F22 does not transmit the polling signal, and even if it receives the polling signal, it does not transmit the response signal.

The mobile terminal 50 also repeatedly executes the above set of operations. Therefore, for example, the distance between the MFP 10 and the mobile terminal 50 is less than 10 cm, and the period during which the NFC I / F 22 operates in Poll mode and the period during which the mobile terminal 50 operates in Listen mode coincide with each other. In this case, the NFC I / F 22 executes a Poll operation of transmitting the polling signal to the mobile terminal 50 and receiving the response signal from the mobile terminal 50. Further, for example, when the distance between the MFP 10 and the mobile terminal 50 is less than 10 cm and the period during which the NFC I / F 22 operates in the Listen mode and the period during which the mobile terminal 50 operates in the Poll mode match, the NFC The I / F 22 executes a Listen operation of receiving the polling signal from the mobile terminal 50 and transmitting the response signal to the mobile terminal 50.

When the NFC I / F 22 executes the Poll operation or the Listen operation, each process for subsequent communication is taken over by the CPU 32. Specifically, when the NFC I / F22 of the MFP 10 executes the Poll operation and the mobile terminal 50 executes the Listen operation, information indicating which mode of the operation the mobile terminal 50 can execute () That is, the received information indicated by the operable mode signal) is passed from the NFC I / F 22 to the CPU 32. The CPU 32 determines in which mode the MFP 10 should operate based on the information passed from the NFC I / F 22. Specifically, when the MFP10 indicates that it can operate in all modes and that the received operable mode signal can operate in the P2P mode and the CE mode, the CPU 32 indicates that the MFP10 is in the P2P mode. Decide what to do with. In the modified example, in this case, the CPU 32 may determine that the MFP 10 should operate in the CE mode. Further, when the MFP 10 can operate in all modes and the received operable mode signal indicates that it can operate only in the CE mode, the CPU 32 operates the MFP 10 in the R / W mode. Decide what to do. If it is assumed that the MFP10 can operate only in the R / W mode and the received operable mode signal can operate in the CE mode, the CPU32 has the MFP10 in the R / W mode. Decide what to do with. As will be described in detail later, after that, the CPU 32 transmits an activation command corresponding to the mode in which the MFP 10 should operate (that is, the mode determined by the CPU 32) to the mobile terminal 50 (see S112 in FIG. 4 and S160 in FIG. 5). .. The Activation command is a command adopted in the NFC standard, and is a command for establishing an NFC-type communication link between the MFP 10 and the mobile terminal 50.

In the NFC standard, an NFC device that has executed a Poll operation (hereinafter referred to as a "Poll device") can operate in P2P mode and R / W mode, but cannot operate in CE mode. Therefore, as described above, when the MFP 10 is a Poll device, the CPU 32 determines that the MFP 10 should operate in P2P mode or R / W mode.

On the other hand, when the NFC I / F22 of the MFP 10 executes the Listen operation and the mobile terminal 50 executes the Poll operation, the CPU 32 issues an Activation command corresponding to the mode in which the mobile terminal 50 should operate. Received from (see S10 in FIG. 2). The CPU 32 determines that the MFP 10 should operate in the P2P mode when receiving the activation command corresponding to the P2P mode, and operates in the CE mode when the MFP 10 receives the activation command corresponding to the R / W mode. Decide what to do.

According to the NFC standard, an NFC device that has executed the Listen operation (hereinafter referred to as a "Listen device") can operate in the P2P mode and the CE mode, but cannot operate in the R / W mode. Therefore, as described above, when the MFP 10 is a Poll device, the CPU 32 determines that the MFP 10 should operate in P2P mode or CE mode.

As described above, the CPU 32 can know that the mobile terminal 50 exists in the vicinity of the MFP 10 if the NFC I / F 22 executes the Poll operation or the Listen operation, and further, in which mode the MFP 10 should operate. Can be known, and each process for subsequent communication (see FIGS. 2 to 5 described later) is executed.

(Processes executed by MFP10; FIGS. 2 to 5)
Subsequently, the process executed by the MFP 10 will be described with reference to FIGS. 2 to 5. The CPU 32 executes each process of FIGS. 2 to 5 according to the programs 36 and 38 in the memory 34. In the following, first, when the NFC I / F22 executes the Listen operation, the contents of the process executed by the CPU 32 (FIGS. 2 and 3; hereinafter referred to as “MFP Listen process”) will be described, and then the NFC The contents of the process (FIGS. 4 and 5; hereinafter referred to as "MFP Poll process") executed by the CPU 32 when the I / F 22 executes the Poll operation will be described.

(Listen processing of MFP; FIGS. 2 and 3)
As described above, when the NFC I / F 22 executes the Listen operation (that is, when the mobile terminal 50 executes the Poll operation), the mobile terminal 50 has an Activation command corresponding to the mode in which the mobile terminal 50 should operate. Is transmitted to the MFP 10. In S10, the CPU 32 receives an activation command from the mobile terminal 50 via the NFC I / F22.

Next, in S12, the CPU 32 determines whether the MFP 10 should operate in the P2P mode or the CE mode. As described above, the MFP 10 is an NFC device that can use all three modes of P2P mode, R / W mode, and CE mode. On the other hand, the mobile terminal 50 may be a device that can use all three modes, or may be a device that can use only the R / W mode and the CE mode. When the CPU 32 receives the activation command corresponding to the P2P mode, the CPU 32 determines that the MFP 10 should operate in the P2P mode (YES in S12 of FIG. 2), and proceeds to S14. On the other hand, when the CPU 32 receives the activation command corresponding to the R / W mode, the CPU 32 determines that the MFP 10 should operate in the CE mode (NO in S12 of FIG. 2), and proceeds to S62 of FIG.

(Listen processing of MFP; P2P mode)
In S14, the CPU 32 transmits a response command (that is, an OK command) to the Activation command to the mobile terminal 50 via the NFC I / F22. As a result, an NFC communication link is established between the MFP 10 and the mobile terminal 50. That is, the CPU 32 can appropriately establish the communication link by receiving the Activation command and transmitting the OK command.

In the Listen process of the MFP, the Activation command cannot be transmitted from the MFP 10 to the mobile terminal 50. This is because the Poll device can send the Activation command, but the Listen device cannot send the Activation command.

Next, in S16, the CPU 32 starts the confirmation command response process. The confirmation command is a command sent from the Poll device to the Listen device, and is a command for confirming whether or not to maintain the communication link. As described above, at present, the MFP 10 is a Listen device and the mobile terminal 50 is a Poll device. Therefore, in the confirmation command response processing, the CPU 32 receives the confirmation command from the mobile terminal 50 via the NFC I / F22, and issues a response command (that is, an OK command) to the confirmation command via the NFC I / F22. , Transmit to the mobile terminal 50.

Although not shown in the flowchart, when the CPU 32 starts the confirmation command response process in S16, the confirmation command response is performed until S38 described later is executed or the communication link is disconnected in S44 described later. Continue processing.

Next, in S18, the CPU 32 determines whether or not the transmission flag in the memory 34 is "1". In the above one set of communication, the transmission flag is usually set to "0" in the situation where the communication of the first target data is not executed. For example, in the above-mentioned first to fifth examples regarding the target data, the first target data is transmitted from the mobile terminal 50 to the mobile terminal 10, and the second target data is transmitted from the MFP 10 to the mobile terminal 50. In such a case, the transmission flag is usually set to "0" in the situation where the communication of the first target data is not executed. As a result, as will be described later, it is realized that the MFP 10 receives the first target data from the mobile terminal 50 (see S22 and the like). Further, in such a case, the transmission flag is set to "1" in the situation where the communication of the first target data is executed (see S28 and the like). As a result, as will be described later, the MFP 10 can transmit the second target data to the mobile terminal 50 (see S32 and the like).

However, in the above sixth example regarding the target data, the first target data is transmitted from the mobile terminal 10 to the mobile terminal 50, and the second target data is transmitted from the mobile terminal 50 to the MFP 10. For example, when the CPU 32 generates scan data (that is, the first target data) according to the sixth example above, the transmission flag is changed from "0" to "0" in the process not shown in the flowcharts of FIGS. Change to "1". In such a case, the transmission flag is set to "1" even in the situation where the communication of the first target data is not executed in the above-mentioned one set of communication. As a result, as will be described later, the MFP 10 can transmit the first target data to the mobile terminal 50 (see S32 and the like). Further, in such a case, the transmission flag is set to "0" in the situation where the communication of the first target data is executed (see S36 and the like). As a result, as will be described later, it is realized that the MFP 10 receives the second target data from the mobile terminal 50 (see S22 and the like).

When the transmission flag in the memory 34 is "1", the CPU 32 determines YES in S18 and proceeds to S30. On the other hand, when the transmission flag in the memory 34 is "0", the CPU 32 determines NO in S18 and proceeds to S20.

In S20, the CPU 32 negotiates with the mobile terminal 50 via the NFC I / F22. Specifically, the CPU 32 first determines that the MFP 10 operates as a client in P2P mode. Next, the CPU 32 executes communication according to the Simple NDEF Exchange protocol so that the MFP 10 operates as a client and the mobile terminal 50 operates as a server in P2P mode. As a result, the mobile terminal 50 operates as a server that executes processing in response to a request from the client (that is, the MFP 10). NDEF is an abbreviation for NFC data Exchange Format.

In S20, the CPU 32 further notifies the mobile terminal 50 that the MFP 10 executes data reception (that is, the mobile terminal 50 executes data transmission). As a result, the mobile terminal 50 can know that the target data should be transmitted to the MFP 10, and transmits the target data to the MFP 10. In the following, the "target data" may be any first target data among the above-mentioned first to sixth examples relating to the target data, or any second target data. good.

Next, in S22, the CPU 32 receives the target data from the mobile terminal 50 via the NFC I / F 22 by using the communication link established in S14.

Next, in S24, the CPU 32 processes the target data received in S22. For example, in the first or second example described above, the CPU 32 interprets the print execution instruction or scan execution (that is, the first target data) received in S22, and wirelessly sets (that is, the second target data). Generate a response that includes. Further, for example, in the above third example, the CPU 32 stores the setting information (that is, the first target data) received in S22 in the memory 34, and responds indicating that the setting information has been received (that is, the second target data). Target data) is generated. Further, for example, in the fourth example described above, the CPU 32 adds the address information (that is, the first target data) received in S22 to the address book in the memory 34, and responds indicating that the address information has been received. (That is, the second target data) is generated. Further, for example, in the fifth example described above, the CPU 32 executes a print function according to the print data received in S22 (that is, the first target data), and responds indicating that the print data has been received (that is, that is). Second target data) is generated.

In the sixth example described above, the CPU 32 interprets the response received in S22 (that is, the second target data) and confirms that the mobile terminal 50 has received the scan data. In this case, unlike the first to fifth examples described above, the CPU 32 does not execute the process of generating the second target data. That is, the second target data is the data generated by the mobile terminal 50.

Next, in S26, the CPU 32 determines whether or not the communication completed flag in the memory 34 is "1". When the communication completed flag in the memory 34 is "1", the CPU 32 determines YES in S26 and proceeds to S40. On the other hand, when the communication completed flag in the memory 34 is "0", the CPU 32 determines NO in S26 and proceeds to S28.

In S28, the CPU 32 sets the transmission flag in the memory 34 to "1" and sets the communication completed flag in the memory 34 to "1". After finishing S28, the process proceeds to S38.

In S38, the CPU 32 executes a disconnection process for disconnecting the communication link established in S14. As a method of the cutting process of S38, two methods, a software-like cutting process and a hardware-like cutting process, can be considered. The CPU 32 may execute the disconnection process of either method.

When the CPU 32 executes the software disconnection process, the CPU 32 ends the confirmation command response process started in S16. That is, even if the CPU 32 receives the confirmation command from the mobile terminal 50, the CPU 32 does not transmit the response command (that is, the OK command) to the confirmation command to the mobile terminal 50. As a result, the mobile terminal 50 can know that the MFP 10 does not want to maintain the communication link, and transmits a Deactivation command for disconnecting the communication link to the MFP 10.

Therefore, the CPU 32 receives the Deactivation command from the mobile terminal 50 via the NFC I / F22. In this case, the CPU 32 transmits a response command (that is, an OK command) to the Deactivation command to the mobile terminal 50 via the NFC I / F22. As a result, the communication link established in S14 is disconnected. The CPU 32 can appropriately disconnect the communication link by executing software-like disconnection processing (termination of confirmation command response processing, reception of activation command, transmission of OK command).

In the Listen process of the MFP, the Deaction command cannot be transmitted from the MFP 10 to the mobile terminal 50. This is because the Poll device can send a Deaction command, but the Listen device cannot send a Deaction command.

On the other hand, when the CPU 32 executes the hardware disconnection process, the CPU 32 temporarily stops the operation of the NFC I / F 22. Specifically, for example, the CPU 32 transmits an instruction for the NFC I / F 22 to stop the operation to the NFC I / F 22. As a result, the NFC I / F 22 temporarily stops all operations including reception of signals from the outside, transmission of signals to the outside, Poll operation, Listen operation, and the like. Therefore, the CPU 32 cannot execute the confirmation command response process started in S16 via the NFC I / F22.

When the hardware disconnection process is executed, the mobile terminal 50 cannot receive the response command (that is, the OK command) for the confirmation command, as in the case of the software disconnection process. In this case, the mobile terminal 50 transmits the Deaction command to the MFP 10, but cannot receive the response command (that is, the OK command) to the Deaction command because the operation of the NFC I / F 22 of the MFP 10 is stopped. Therefore, the mobile terminal 50 determines that the time-out has occurred, and ends the process for maintaining the communication link (that is, the process of transmitting the confirmation command, etc.). As a result, the communication link established in S14 is disconnected. The CPU 32 can appropriately disconnect the communication link by executing the hardware disconnection process (that is, stopping the operation of the NFC I / F 22).

The method of stopping the operation of the NFC I / F 22 is not limited to the method of transmitting an instruction from the CPU 32 to the NFC I / F 22 as described above. For example, the CPU 32 may temporarily stop the operation of the NFC I / F 22 by temporarily stopping the power supply to the NFC I / F 22. This method is also an example of hardware disconnection processing. When S38 ends, the Listen processing of the MFP ends.

On the other hand, when YES in S18 (that is, when the transmission flag is "1"), in S30, the CPU 32 operates the MFP 10 as a client in the P2P mode and the mobile terminal 50 operates in the P2P mode as in the case of S20. Negotiate to act as a server for. In S30, the CPU 32 further notifies the mobile terminal 50 that the MFP 10 executes data transmission (that is, the mobile terminal 50 executes data reception). As a result, the mobile terminal 50 waits until the target data is received from the MFP 10.

Next, in S32, the CPU 32 transmits the target data to the mobile terminal 50 via the NFC I / F 22 using the communication link established in S14. For example, in the first to fifth examples described above, the CPU 32 processes the first target data in, for example, S24 of the Listen processing of the previous MFP or S124 of the Poll processing (FIG. 4) of the previous MFP. Then, the second target data is generated. In this case, in S32, the CPU 32 transmits the generated second target data to the mobile terminal 50. Further, for example, in the sixth example described above, scan data is generated as the first target data. In this case, in S32, the CPU 32 transmits the generated first target data to the mobile terminal 50.

Next, in S34, the CPU 32 determines whether or not the communication completed flag in the memory 34 is "1". When the communication completed flag in the memory 34 is "1", the CPU 32 determines YES in S34 and proceeds to S40. On the other hand, when the communication completed flag in the memory 34 is "0", the CPU 32 determines NO in S34 and proceeds to S36.

In S36, the CPU 32 sets the transmission flag in the memory 34 to "0" and sets the communication completed flag in the memory 34 to "1". When the CPU 32 finishes S36, it proceeds to S38 and executes the above-mentioned disconnection process.

On the other hand, in S40, the CPU 32 sets the transmission flag in the memory 34 to "0" and the communication completed flag in the memory 34 to "0".

When S40 is executed (that is, when the communication completed flag is "1"), the communication of the second target data is completed (that is, the communication of the above one set is completed). There is). Therefore, the mobile terminal 50 determines that it is not necessary to maintain the communication link, and transmits a Deactivation command to the MFP 10. As a result, in S42, the CPU 32 receives the Deaction command from the mobile terminal 50 via the NFC I / F22.

Next, in S44, the CPU 32 transmits a response command (that is, an OK command) to the Deactivation command to the mobile terminal 50 via the NFC I / F22. As a result, the communication link established in S14 is disconnected. When S44 ends, the Listen processing of the MFP ends.

(Listen processing of MFP; CE mode (Fig. 3))
Subsequently, with reference to FIG. 3, the content of the process when NO is determined in S12 of FIG. 2 (when it is determined that the MFP 10 should operate in the CE mode) will be described. S62 is the same as S14 in FIG. When the MFP 10 operates in the CE mode and the mobile terminal 50 operates in the R / W mode, the confirmation command response process (see S16 in FIG. 2) is not executed unlike the case of the P2P mode. This is because it is not necessary to confirm whether or not to maintain the communication link because it is a mode for unidirectional communication (that is, it is a mode in which only one communication of the target data is executed). ..

S64 to S72 are the same as S18 and S22 to S28 in FIG. S74 to S78 are the same as S32 to S36 in FIG. Further, S86 to S90 are the same as S40 to S44 in FIG. When S90 ends, the Listen processing of the MFP ends.

In S80, the CPU 32 executes a software disconnection process for disconnecting the communication link established in S62. That is, the CPU 32 receives the Deactivation command from the mobile terminal 50 via the NFC I / F22, and transmits a response command (that is, an OK command) to the Deactivation command to the mobile terminal 50 via the NFC I / F22. do. As a result, the communication link established in S62 is disconnected. The CPU 32 can appropriately disconnect the communication link by executing the software disconnection process (reception of the Deactivation command and transmission of the OK command).

Next, in S82, the CPU 32 executes an operation control process for controlling the operation of the NFC I / F 22. The CPU 32 transmits an instruction for stopping the operation of the NFC I / F 22 to the NFC I / F 22. As a result, the NFC I / F 22 temporarily stops all operations including reception of signals from the outside, transmission of signals to the outside, Poll operation, Listen operation, and the like.

When the communication link is disconnected in S80, the mobile terminal 50 sequentially operates again in the Poll mode and the Listen mode. However, in S82, since the operation of the NFC I / F22 of the MFP10 is temporarily stopped, the mobile terminal 50 does not receive the response signal even if the polling signal is transmitted. Further, the mobile terminal 50 does not receive the polling signal from the MFP 10. Therefore, the mobile terminal 50 can detect that the distance between the MFP 10 and the mobile terminal 50 has increased, that is, that the communication partner has separated.

The reason why the mobile terminal 50 detects the separation of the communication partner (that is, the operation control process of S82 is executed) is as follows. In the communication link corresponding to the CE mode and the R / W mode, it is premised that the communication of the target data is executed only once. Therefore, when each of the pair of NFC devices executes the communication of the target data according to the CE mode and the R / W mode, the communication link is usually disconnected. After that, if the pair of NFC devices continue to be kept close to each other, the pair of NFC devices re-execute the Poll operation and the Listen operation to reestablish the communication link and execute the communication of the same target data. Can be. That is, when the state in which the pair of NFC devices are kept close to each other is maintained, an event that the same target data is communicated many times may occur.

Therefore, normally, if the NFC device does not detect the separation of the communication partner after disconnecting the communication link corresponding to the CE mode and the R / W mode, the communication link can be executed even if the Poll operation and the List operation are executed again. Is programmed not to be established again. Then, for example, when the NFC device does not receive the response signal from the communication partner even if the polling signal is transmitted several times, or when the polling signal is not received from the communication partner for a predetermined period, the communication partner is separated. Is detected. When the NFC device detects the separation of the communication partner in this way, the NFC device can reestablish the communication link with the same communication partner.

In this embodiment, after the communication of the first target data is executed, the communication of the second target data is executed (that is, one set of communication is executed). Therefore, even if the state in which the MFP 10 and the mobile terminal 50 are kept close to each other is maintained after the communication link for the communication of the first target data is disconnected, a new communication for the communication of the second target data is performed. A mechanism is needed to reestablish a good communication link. This mechanism is the operation control process of S82. That is, if the MFP 10 executes the operation control process of S82, the mobile terminal 50 can detect the separation of the MFP 10 even if the state in which the MFP 10 and the mobile terminal 50 are close to each other is maintained. After that, if the MFP 10 and the mobile terminal 50 execute the Poll operation and the Listen operation, the communication link can be reestablished between the MFP 10 and the mobile terminal 50.

The operation control process of S82 is not limited to the method of transmitting an instruction from the CPU 32 to the NFC I / F 22 as described above. For example, the CPU 32 may temporarily stop the operation of the NFC I / F 22 by temporarily stopping the power supply to the NFC I / F 22. This method is also an example of motion control processing. When S82 is completed, the Listen processing of the MFP is completed.

(Poly processing of MFP; FIGS. 4 and 5)
Subsequently, the content of the Poll processing of the MFP will be described with reference to FIGS. 4 and 5. As described above, when the NFC I / F 22 performs the Poll operation, the MFP 10 operates in either the P2P mode or the R / W mode according to the received operable mode signal. In S110, the CPU 32 determines whether the MFP 10 should operate in the P2P mode or the R / W mode based on the received operable mode signal. When the CPU32 determines that the MFP10 should operate in the P2P mode (YES in S110), the CPU32 proceeds to S112 and determines that the MFP10 should operate in the R / W mode (NO in S110). , Proceed to S160 of FIG.

(Mliple processing of MFP; P2P mode (Fig. 4))
In S112, the CPU 32 transmits an activation command corresponding to the P2P mode to the mobile terminal 50 via the NFC I / F22. Next, in S114, the CPU 32 receives a response command (that is, an OK command) to the Activation command from the mobile terminal 50 via the NFC I / F22. As a result, an NFC communication link is established between the MFP 10 and the mobile terminal 50.

Next, in S116, the CPU 32 starts the confirmation command transmission process. In the confirmation command transmission process, the CPU 32 transmits the confirmation command to the mobile terminal 50 via the NFC I / F22, and the response command to the confirmation command (that is, OK) from the mobile terminal 50 via the NFC I / F22. Command) is received. When the confirmation command transmission process is started in S116, the CPU 32 continues to execute the confirmation command transmission process until S138 described later is executed or the communication link is disconnected in S144 described later.

S118 to S128 are the same as S18 to S28 in FIG. S130 to S136 are the same as S30 to S36 in FIG. Further, S140 is the same as S40 in FIG. In S142, the CPU 32 transmits a Deactivation command to the mobile terminal 50 via the NFC I / F 22. Next, in S144, the CPU 32 receives a response command (that is, an OK command) to the Deactivation command from the mobile terminal 50 via the NFC I / F22. As a result, the communication link established in S114 is disconnected.

In S138, the CPU 32 executes a disconnection process for disconnecting the communication link established in S114. As a method of the cutting process of S138, two methods, a software-like cutting process and a hardware-like cutting process, can be considered. The CPU 32 may execute the disconnection process of either method.

When the CPU 32 executes the software disconnection process, the CPU 32 transmits a Deactivation command to the mobile terminal 50 via the NFC I / F22, and the Deactivation command is transmitted from the mobile terminal 50 via the NFC I / F22. Receives a response command (that is, an OK command) to. As a result, the communication link established in S114 is disconnected. The CPU 32 can appropriately disconnect the communication link by executing the software disconnection process (transmission of the Deactivation command and reception of the OK command).

The software disconnection process is not limited to the method in which the CPU 32 transmits a Deactivation command as described above. For example, the CPU 32 may end the confirmation command transmission process started in S116. That is, the CPU 32 does not send the confirmation command to the mobile terminal 50. When the mobile terminal 50 does not receive the confirmation command from the MFP 10 for a predetermined period of time, the mobile terminal 50 determines that the time-out has occurred. As a result, the mobile terminal 50 ends the processing related to the communication link (that is, monitoring the reception of the confirmation command, etc.), and as a result, the communication link is disconnected. This method is also an example of software-like disconnection processing.

On the other hand, when the CPU 32 executes the hardware disconnection process, the CPU 32 temporarily stops the operation of the NFC I / F 22. Specifically, for example, the CPU 32 transmits an instruction for the NFC I / F 22 to stop the operation to the NFC I / F 22. Therefore, the CPU 32 cannot execute the confirmation command transmission process started in S116 via the NFC I / F22. In this case, the mobile terminal 50 determines that the time-out has occurred, ends the processing related to the communication link (that is, monitoring the reception of the confirmation command, etc.), and as a result, the communication link is disconnected. The CPU 32 can appropriately disconnect the communication link by executing the hardware disconnection process (stopping the operation of the NFC I / F 22).

The method of stopping the operation of the NFC I / F 22 is not limited to the method of transmitting an instruction from the CPU 32 to the NFC I / F 22 as described above. For example, the CPU 32 may temporarily stop the operation of the NFC I / F 22 by temporarily stopping the power supply to the NFC I / F 22. This method is also an example of hardware disconnection processing. When S138 is completed, the Poll processing of the MFP is completed.

(Poly processing of MFP; R / W mode (Fig. 5))
Subsequently, with reference to FIG. 5, the content of the process when NO is determined in S110 of FIG. 4 (that is, when it is determined that the MFP 10 should operate in the R / W mode) will be described. S160 to S164 are the same as S112, S114, and S118 in FIG. However, in S160, the CPU 32 transmits an Activation command corresponding to the R / W mode.

In the case of NO in S164 (that is, when the transmission flag is "0"), in S165, the CPU 32 determines that the MFP 10 should operate according to the Reader mode. As a result, the CPU 32 can read the target data from the pseudo card of the mobile terminal 50, that is, can receive the target data from the mobile terminal 50. S166 to S172 executed after this are the same as S66 to S72 in FIG.

On the other hand, if YES in S164 (that is, when the transmission flag is "1"), in S173, the CPU 32 determines that the MFP 10 should operate according to the Writer mode. As a result, the CPU 32 can write the target data to the pseudo card of the mobile terminal 50, that is, can transmit the target data to the mobile terminal 50. S174 to S182 executed after this are the same as S74 to S82 in FIG. Note that S186 to S190 are the same as S140 to S144 in FIG.

(Specific case)
Subsequently, a specific case realized by this embodiment will be described. Each of the following cases is realized by the MFP 10 executing each of the processes of FIGS. 2 to 5.

(Case A1; Fig. 6)
In case A1, the MFP 10 executes the Listen operation (that is, the mobile terminal 50 executes the Poll operation), and the mobile terminal 50 can operate according to the P2P mode.

The MFP 10 receives the Activation command from the mobile terminal 50 (S10 in FIG. 2) and transmits the OK command to the mobile terminal 50 (S14). As a result, the communication link L1 is established between the MFP 10 and the mobile terminal 50. In this case, the MFP 10 starts the confirmation command response process (S16). That is, the MFP 10 receives the confirmation command from the mobile terminal 50 and transmits the OK command to the mobile terminal 50.

In case A1, the transmission flag is "0" when the communication link L1 is established. In this case, the MFP 10 determines NO in S18 of FIG. 2, then executes negotiation to notify the mobile terminal 50 that the MFP 10 executes data reception (S20). The MFP 10 receives the first target data from the mobile terminal 50 (S22) and generates the second target data by processing the first target data (S24). In this case, the MFP 10 sets the transmission flag to "1" and the communication completed flag to "1" (S28).

Next, the MFP 10 executes a software disconnection process (S38). That is, even if the MFP 10 receives the confirmation command from the mobile terminal 50, it does not send the OK command. In this case, the MFP 10 receives the Deaction command from the mobile terminal 50 and transmits the OK command to the mobile terminal 50. As a result, the communication link L1 is disconnected.

After that, the MFP 10 executes the Listen operation again (that is, the mobile terminal 50 executes the Poll operation again). The MFP 10 receives the Activation command from the mobile terminal 50 (S10) and transmits the OK command to the mobile terminal 50 (S14). As a result, the communication link L2 is established between the MFP 10 and the mobile terminal 50.

When the first target data is communicated, the transmission flag is set to "1". In this case, the MFP 10 determines YES in S18 of FIG. 2, and then executes negotiation to notify the mobile terminal 50 that the MFP 10 executes data transmission (S30). The MFP 10 transmits the second target data to the mobile terminal 50 (S32). In this case, the MFP 10 sets the transmission flag to "0" and the communication completed flag to "0" (S40). Next, the MFP 10 receives the Deaction command from the mobile terminal 50 (S42) and transmits the OK command to the mobile terminal 50 (S44). As a result, the communication link L2 is disconnected.

As described above, the P2P mode is a mode for bidirectional communication. Therefore, it is conceivable that the same communication link L1 is used to communicate both the first and second target data. However, there is a possibility that the mobile terminal 50 cannot properly perform bidirectional communication according to the P2P mode. For example, the OS (Operating System) of the mobile terminal 50 uses the communication link L1 to transmit the first target data, and then uses the same communication link L1 to receive the second target data. May not be tolerated.

In view of such a possibility, in the present embodiment, as shown in Case A1, when the MFP 10 receives the first target data from the mobile terminal 50 by using the communication link L1 corresponding to P2P, The communication link L1 is disconnected. Next, the MFP 10 reestablishes the communication link L2 corresponding to P2P, and uses the communication link L2 to transmit the second target data to the mobile terminal 50. Therefore, even if the mobile terminal 50 does not allow bidirectional communication in the P2P mode, the MFP 10 processes the first target data and the second target data according to the P2P mode to generate the second target data. And both can be appropriately communicated with the mobile terminal 50.

(Case A2; Fig. 7)
Case A2 is different from case A1 in that the MFP 10 executes a hardware disconnection process (S38 in FIG. 2) instead of the software disconnection process.

That is, the MFP 10 temporarily stops the operation of the NFC I / F 22 in the hardware disconnection process. Therefore, even if the MFP 10 receives the confirmation command from the mobile terminal 50, it does not send the OK command. Further, even if the MFP 10 receives the Deaction command from the mobile terminal 50, it does not transmit the OK command. As a result, the mobile terminal 50 determines that the time-out has occurred, and as a result, the communication link L1 is disconnected. Other points are the same as in case A1. In case A2, the same action and effect as in case A1 can be obtained.

If the hardware disconnection process of Case A2 is executed, it may take a long time for the NFC I / F 22 to recover. Therefore, from the viewpoint of speeding up the process, it is preferable to execute the software-like disconnection process of Case A1. However, according to the hardware disconnection process of case A2, the communication link L1 can be reliably disconnected. Therefore, from the viewpoint of ensuring the disconnection of the communication link, it is preferable to execute the hardware disconnection process of Case A2. In other cases (for example, case A4 in FIG. 4), either software-based disconnection processing or hardware-based disconnection processing may be adopted depending on the viewpoint emphasized by the vendor of the MFP 10.

(Case A3; Fig. 8)
In case A3, the MFP 10 executes the Poll operation (that is, the mobile terminal 50 executes the Listen operation), and the mobile terminal 50 can operate according to the P2P mode.

The MFP 10 transmits an activation command to the mobile terminal 50 (S112 in FIG. 4), and receives an OK command from the mobile terminal 50 (S114). As a result, the communication link L1 is established between the MFP 10 and the mobile terminal 50.

In case A3, the transmission flag is "0" when the communication link L1 is established. In this case, the MFP 10 determines NO in S118 of FIG. 4, and then executes negotiation to notify the mobile terminal 50 that the MFP 10 executes data reception (S120). The MFP 10 receives the first target data from the mobile terminal 50 (S122) and generates the second target data by processing the first target data (S124). In this case, the MFP 10 sets the transmission flag to "1" and the communication completed flag to "1" (S128).

Next, the MFP 10 executes a software disconnection process (S138). That is, the MFP 10 transmits a Deactivation command to the mobile terminal 50 and receives an OK command from the mobile terminal 50. As a result, the communication link L1 is disconnected.

After that, the MFP 10 executes the Poll operation again (that is, the mobile terminal 50 executes the Listen operation again). The MFP 10 transmits an activation command to the mobile terminal 50 (S112), and receives an OK command from the mobile terminal 50 (S114). As a result, the communication link L2 is established between the MFP 10 and the mobile terminal 50.

When the first target data is communicated, the transmission flag is set to "1". In this case, the MFP 10 determines YES in S118 of FIG. 4, and then executes negotiation to notify the mobile terminal 50 that the MFP 10 executes data transmission (S130). The MFP 10 transmits the second target data to the mobile terminal 50 (S132). In this case, the MFP 10 sets the transmission flag to "0" and the communication completed flag to "0" (S140). Next, the MFP 10 transmits a Deactivation command to the mobile terminal 50 (S142) and receives an OK command from the mobile terminal 50 (S144). As a result, the communication link L2 is disconnected.

In case A3 as well, the MFP 10 appropriately communicates both the first target data and the second target data generated by processing the first target data with the mobile terminal 50 according to the P2P mode. be able to.

(Case A4; Fig. 9)
In case A4, the content of the software disconnection process is different from that in case A3. When the communication link L1 is established, the MFP 10 starts the confirmation command transmission process (S116). That is, the MFP 10 transmits a confirmation command to the mobile terminal 50 and receives an OK command from the mobile terminal 50.

In the software disconnection process of case A3, the MFP 10 transmits a Deactivation command to the mobile terminal 50 and receives an OK command from the mobile terminal 50 (see FIG. 8). Instead, in case A4, in the software disconnection process, the MFP 10 ends the confirmation command transmission process (S138). As a result, the mobile terminal 50 determines that the time-out has occurred, and as a result, the communication link L1 is disconnected. Other points are the same as in case A3. In case A4, the same action and effect as in case A3 can be obtained.

As described above, the MFP 10 may execute a hardware disconnection process for temporarily stopping the operation of the NFC I / F 22 (S138). Also in this case, since the confirmation command is not transmitted to the mobile terminal 50, the mobile terminal 50 determines that the time-out has occurred, and as a result, the communication link L1 is disconnected. Similar actions and effects can be obtained with such a configuration.

(Other cases)
In cases A1 to A4 of FIGS. 6 to 9, the MFP10 is the same device (that is, in FIG. 6) both when establishing the first communication link L1 and when establishing the second communication link L2. And in FIG. 7, it operates as a Listen device, and in FIGS. 8 and 9, it operates as a Poll device). However, for example, the MFP 10 may operate as a Listen device when establishing the first communication link L1 and as a Poll device when establishing the second communication link L2. Further, for example, the MFP 10 may operate as a Poll device when establishing the first communication link L1 and as a Listen device when establishing the second communication link L2.

Further, in cases A1 to A4 of FIGS. 6 to 9, the MFP 10 receives the first target data from the mobile terminal 50 and transmits the second target data to the mobile terminal 50. That is, cases A1 to A4 correspond to the above-mentioned first to fifth examples regarding the target data. However, the MFP 10 may transmit the first target data to the mobile terminal 50 and receive the second target data from the mobile terminal 50. That is, the above-mentioned sixth example regarding the target data may be realized. In any case, the same actions and effects as in cases A1 to A4 can be obtained.

(Case B1; FIG. 10)
In case B1, the MFP 10 executes the Listen operation (that is, the mobile terminal 50 executes the Poll operation), and the mobile terminal 50 can operate only according to the R / W mode and the CE mode. Therefore, the MFP 10 operates according to the CE mode, and the mobile terminal 50 operates according to the R / W mode.

The MFP 10 receives the activation command from the mobile terminal 50 (S10 in FIG. 2) and transmits the OK command to the mobile terminal 50 (S62). As a result, the communication link L1 is established between the MFP 10 and the mobile terminal 50.

In case B1, the transmission flag is "0" when the communication link L1 is established. In this case, the MFP 10 determines NO in S64 of FIG. 3, receives the first target data from the mobile terminal 50 (S66), and generates the second target data by processing the first target data. (S68). In this case, the MFP 10 sets the transmission flag to "1" and the communication completed flag to "1" (S72).

Next, the MFP 10 executes a software disconnection process (S80). That is, the MFP 10 receives the Deaction command from the mobile terminal 50 and transmits the OK command to the mobile terminal 50. As a result, the communication link L1 is disconnected.

Next, the MFP 10 executes the operation control process (S82). That is, even if the MFP 10 receives the polling signal from the mobile terminal 50, it does not transmit the response signal (that is, the NFC I / F 22 does not temporarily execute the Listen operation). Further, the MFP 10 does not transmit the polling signal to the mobile terminal 50 (that is, the NFC I / F 22 does not temporarily execute the Poll operation). As a result, the mobile terminal 50 detects the separation of the MFP 10. As a result, even if the state in which the MFP 10 and the mobile terminal 50 are kept close to each other is maintained, the communication link L2 described later can be appropriately established.

After that, the MFP 10 executes the Listen operation again (that is, the mobile terminal 50 executes the Poll operation again). The MFP 10 receives the activation command from the mobile terminal 50 (S10 in FIG. 2) and transmits the OK command to the mobile terminal 50 (S62). As a result, the communication link L2 is established between the MFP 10 and the mobile terminal 50.

When the first target data is communicated, the transmission flag is set to "1". In this case, the MFP 10 determines YES in S64 of FIG. 3 and transmits the second target data to the mobile terminal 50 (S74). In this case, the MFP 10 sets the transmission flag to "0" and the communication completed flag to "0" (S86). Next, the MFP 10 receives the Deaction command from the mobile terminal 50 (S88) and transmits the OK command to the mobile terminal 50 (S90). As a result, the communication link L2 is disconnected.

As described above, the R / W mode and the CE mode are modes for unidirectional communication. Therefore, it is not possible to communicate both the first and second target data using the same communication link L1. In this embodiment, as shown in case B1, the MFP 10 disconnects the communication link L1 when it receives the first target data from the mobile terminal 50 by using the communication link L1. Next, the MFP 10 reestablishes the communication link L2 and uses the communication link L2 to transmit the second target data to the mobile terminal 50. Therefore, even when the MFP 10 and the mobile terminal 50 operate according to the R / W mode and the CE mode, the MFP 10 has the first target data and the second target data generated by processing the first target data. , Both can be appropriately communicated with the mobile terminal 50. That is, the MFP 10 can realize pseudo bidirectional communication.

(Case B2; FIG. 11)
In case B2, the MFP 10 executes the Poll operation (that is, the mobile terminal 50 executes the Listen operation), and the mobile terminal 50 can operate only according to the R / W mode and the CE mode. Therefore, the MFP 10 operates according to the R / W mode, and the mobile terminal 50 operates according to the CE mode.

The MFP 10 transmits an activation command to the mobile terminal 50 (S160 in FIG. 5), and receives an OK command from the mobile terminal 50 (S162). As a result, the communication link L1 is established between the MFP 10 and the mobile terminal 50.

In case B2, the transmission flag is "0" when the communication link L1 is established. In this case, the MFP 10 determines NO in S164 of FIG. 5 and determines that the MFP 10 should operate according to the Reader mode (S165). The MFP 10 receives the first target data from the mobile terminal 50 (S166) and generates the second target data by processing the first target data (S168). In this case, the MFP 10 sets the transmission flag to "1" and the communication completed flag to "1" (S172).

Next, the MFP 10 executes a software disconnection process (S180). That is, the MFP 10 transmits a Deactivation command to the mobile terminal 50 and receives an OK command from the mobile terminal 50. As a result, the communication link L1 is disconnected.

Next, the MFP 10 executes the operation control process (S182). As a result, the mobile terminal 50 detects the separation of the MFP 10. After that, the MFP 10 executes the Poll operation again (that is, the mobile terminal 50 executes the Listen operation again). The MFP 10 transmits an activation command to the mobile terminal 50 (S160), and receives an OK command from the mobile terminal 50 (S162). As a result, the communication link L2 is established between the MFP 10 and the mobile terminal 50.

When the first target data is communicated, the transmission flag is set to "1". In this case, the MFP 10 determines YES in S164 of FIG. 5, and determines that the MFP 10 should operate according to the Writer mode (S173). The MFP 10 transmits the second target data to the mobile terminal 50 (S174). In this case, the MFP 10 sets the transmission flag to "0" and the communication completed flag to "0" (S186). Next, the MFP 10 transmits a Deactivation command to the mobile terminal 50 (S188), and receives an OK command from the mobile terminal 50 (S190). As a result, the communication link L2 is disconnected.

In case B2, the same action and effect as in case B1 can be obtained. That is, even when the MFP 10 and the mobile terminal 50 operate according to the R / W mode and the CE mode, the MFP 10 can realize pseudo bidirectional communication.

(Other cases)
In cases B1 and B2 of FIGS. 10 and 11, the MFP10 is the same device (that is, in FIG. 10) both when establishing the first communication link L1 and when establishing the second communication link L2. In, it operates as a Listen device, and in FIG. 11, it operates as a Poll device). However, for example, as shown in case B3 of FIG. 12, the MFP 10 operates as a Listen device (that is, CE mode) when establishing the first communication link L1 and establishes the second communication link L2. At that time, it may operate as a Poll device (that is, a Writer mode). Further, for example, as shown in case B4 of FIG. 12, the MFP 10 operates as a Poll device (that is, Reader mode) when establishing the first communication link L1 and establishes the second communication link L2. At that time, it may operate as a Listen device (that is, CE mode).

Further, in cases B1 and B2 of FIGS. 10 and 11, the MFP 10 receives the first target data from the mobile terminal 50 and transmits the second target data to the mobile terminal 50. That is, cases B1 and B2 correspond to the above-mentioned first to fifth examples regarding the target data. However, as in cases B5 to B8 of FIG. 12, the MFP 10 may transmit the first target data to the mobile terminal 50 and receive the second target data from the mobile terminal 50. That is, the above-mentioned sixth example regarding the target data may be realized. In any case, the same actions and effects as in cases B1 and B2 can be obtained.

(Correspondence)
The MFP 10 and the mobile terminal 50 are examples of a “communication device” and an “external device”, respectively. The Activation command is an example of the "first establishment command" and the "second establishment command". The Deaction command is an example of a "disconnect command". Further, the transmission flag = 1 is an example of "transmission information". Further, in cases A1 to A4 of FIGS. 6 to 9, the P2P mode is an example of the “transmission mode” and the “reception mode”. Further, in case B1 of FIG. 10, the CE mode is an example of the “transmission mode” and the “reception mode”. Further, in case B2 of FIG. 11, the Writer mode and the Reader mode are examples of the “transmission mode” and the “reception mode”, respectively.

S10 and S14 in FIG. 2, S62 in FIG. 3, S112 and S114 in FIG. 4, and S160 and S162 in FIG. 5 are "first establishment step (further first establishment means)" and "second establishment step (second establishment means). Further, it is an example of "second establishment means)". S22 and S32 in FIG. 2, S66 and S74 in FIG. 3, S122 and S132 in FIG. 4, and S166 and S174 in FIG. 5 are "first communication step (further first communication means)" and "second communication". This is an example of "step (further second communication means)". Further, S38 in FIG. 2, S80 in FIG. 3, S138 in FIG. 4, and S180 in FIG. 5 are examples of the “cutting step (further cutting means)”. For example, S38 in FIG. 2 and S138 in FIG. 4 are examples of a "first cutting method" and a "second cutting method," respectively. Further, for example, S80 in FIG. 3 and S180 in FIG. 5 are examples of the "first cutting method" and the "second cutting method", respectively.

Further, the confirmation command response process started in S16 of FIG. 2 and the confirmation command transmission process started in S116 of FIG. 4 are examples of the "first confirmation step" and the "second confirmation step", respectively. .. S82 in FIG. 3 and S182 in FIG. 5 are examples of "motion control steps". Further, S18 in FIG. 2, S64 in FIG. 3, S118 in FIG. 4, and S164 in FIG. 5 are examples of the “judgment step”. S28 and S36 of FIG. 2, S72 and S78 of FIG. 3, S128 and S136 of FIG. 4, and S172 and S178 of FIG. 5 are examples of the “memory control step”. S20 of FIG. 2 and S120 of FIG. 4 are examples of the “notification step”. S165 and S173 in FIG. 5 are examples of “decision steps”. S24 of FIG. 2, S68 of FIG. 3, S124 of FIG. 4, and S168 of FIG. 3 are examples of “processing steps”. Further, S22 in FIG. 2, S66 in FIG. 3, S122 in FIG. 4, and S166 in FIG. 5 are examples of the “reception step”. S32 of FIG. 2, S74 of FIG. 3, S132 of FIG. 4, and S174 of FIG. 5 are examples of the “transmission step”.

Although specific examples of the present invention have been described in detail above, these are merely examples and do not limit the scope of claims. The techniques described in the claims include various modifications and modifications of the specific examples illustrated above. Modifications of the above embodiment are listed below.

(Modification 1) The "communication device" is not limited to a multifunctional machine (that is, MFP10) capable of executing a printing function and a scanning function, but is a printer capable of executing only a printing function among the printing function and the scanning function. Alternatively, the scanner may be capable of executing only the scanning function among the printing function and the scanning function. Further, the "communication device" is a device (for example, a PC, a server, a mobile terminal (mobile phone, smartphone, PDA) that executes a function different from the printing function and the scanning function (for example, an image display function and a data calculation function). Etc.)). That is, the "communication device" includes any device capable of performing NFC communication.

(Modification 2) The MFP 10 may not be able to use the P2P mode, and may be able to use only the R / W mode and the CE mode. In this case, the CPU 32 may execute each of the processes of FIGS. 3 and 5 without executing each of the processes of FIGS. 2 and 4. Further, the MFP 10 may not be able to use the R / W mode and the CE mode, and may be able to use only the P2P mode. That is, the "communication device" does not have to be able to use all the modes of the NFC standard, and may be able to use at least one mode.

(Modification 3) In each of the above embodiments, each process of FIGS. 2 to 5 is realized by software (that is, programs 36 and 38), but at least one of each process of FIGS. 2 to 5 is logical. It may be realized by hardware such as a circuit.

In addition, the technical elements described in the present 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 techniques illustrated in this specification or drawings achieve a plurality of objectives at the same time, and achieving one of the objectives itself has technical usefulness.

2: Communication system, 10: Multifunction device (MFP), 30: Control unit, 32: CPU, 34: Memory, 50: Mobile terminal, L1, L2: Communication link

Claims (3)

A computer program for communication equipment
The computer of the communication device is referred to as the following parts, that is,
A first establishment unit that establishes a first communication link according to the first communication method between the communication device and the external device via the first communication interface of the communication device.
After said first communication link is established, via the first communication interface, by using the first communication link, wherein a Read unit communication setting information from an external device to Read, before The communication setting information is communication according to a second communication method different from the first communication method, and the communication device is via a second communication interface different from the first communication interface. communication speed information der is, the first communication system for performing communication is slower than the communication speed of the second communication scheme, and the Read section,
After reading the communication setting information from the external device, a write unit that writes a response indicating that the communication setting information has been read to the external device via the first communication interface.
A computer program that acts as. The computer program according to claim 1, wherein the first communication method is an NFC (abbreviation of Near Field Communication) method. The computer program further adds to the computer.
After reading the communication setting information from the external device, a cutting portion that disconnects the first communication link, and
After the first communication link is disconnected, a second communication link according to the first communication method is established between the communication device and the external device via the first communication interface. To function as a second establishment part,
A claim that the Write unit writes the response to the external device by using the second communication link via the first communication interface after the second communication link is established. The computer program according to 1 or 2.

Images