JP2024004361A - Computer program for first communication device, and second communication device - Google Patents

Abstract

To provide a technique to properly perform again DPP processing when a Wi-Fi connection is not established.SOLUTION: A first communication device is configured so as to, when a first bootstrapping key and a piece of one-time information are acquired, execute DPP processing according to DPP. When the Wi-Fi connection is not established and when one-time information is a first case indicating that the first bootstrapping key is a one-time key, a second bootstrapping key is acquired. When the Wi-Fi connection is not established and when the one-time information is a second case indicating that the first bootstrapping key is not a one-time key, the second bootstrapping key is not acquired. In the first case, when the second bootstrapping key is acquired, DPP processing using the second bootstrapping key is executed. In the second case, the DPP processing using the first bootstrapping key may be re-executed.SELECTED DRAWING: Figure 21

Description

This specification discloses a technique for establishing a wireless connection between a communication device and an external device.

Patent Document 1 discloses a technique for establishing a Wi-Fi connection between a pair of devices according to DPP (abbreviation for Device Provisioning Protocol).

JP 2019-205021 Publication

Patent Document 1 does not disclose any means for re-executing the process according to DPP when the process according to DPP fails, that is, when a Wi-Fi connection is not established between a pair of devices. It has not been. This specification provides a technique for appropriately re-executing DPP processing when a Wi-Fi connection is not established.

This specification discloses a computer program for a first communication device. The first communication device may include a Wi-Fi interface for performing Wi-Fi communication in accordance with the Wi-Fi standard, and a computer. The computer program may cause the computer to operate the following units, that is, when a predetermined operation is executed, the first bootstrapping key of the second communication device and the first bootstrapping key are one-time a first obtaining unit that obtains one-time information indicating whether or not the key is a key; and a first obtaining unit that obtains one-time information indicating whether or not the key is a A first DPP processing execution unit that executes DPP processing according to DPP (abbreviation for Device Provisioning Protocol), wherein the DPP processing is performed when the first bootstrapping key is transmitted via the Wi-Fi interface. A process of transmitting the used authentication request to the second communication device, and a process of transmitting the authentication request to the second communication device via the Wi-Fi interface. and when the authentication response is received from the second communication device, communication of first connection information with the second communication device via the Wi-Fi interface. A process to be executed, wherein the first connection information establishes a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface. If the Wi-Fi connection is not established and the one-time information includes the first bootstrapping key, a second acquisition unit that acquires a second bootstrapping key of the second communication device that is different from the first bootstrapping key in the first case indicating that the one-time key is the one-time key; in a second case where the Wi-Fi connection is not established and the one-time information indicates that the first bootstrapping key is not the one-time key; the second obtaining unit, in which the second bootstrapping key is not obtained; and in the first case, when the second bootstrapping key is obtained, the second a second DPP processing execution unit that executes the DPP processing using the bootstrapping key; and in the second case, re-running the DPP processing using the acquired first bootstrapping key; It may also function as a third DPP processing execution unit.

According to the above configuration, the first communication device acquires the first bootstrapping key and one-time information, and executes the DPP process using the first bootstrapping key. If the first communication device does not establish a Wi-Fi connection between the first communication device or the second communication device and the external device, and the first bootstrapping key is a one-time key. Next, a second bootstrapping key is obtained, and DPP processing using the second bootstrapping key is executed. On the other hand, the first communication device determines that a Wi-Fi connection is not established between the first communication device or the second communication device and the external device, and the first bootstrapping key is not a one-time key. In this case, the DPP processing using the acquired first bootstrapping key is executed again. In this way, the first communication device is configured such that the first bootstrapping key is a one-time key when a Wi-Fi connection between the first communication device or the second communication device and the external device is not established. Depending on whether or not the second bootstrapping key is acquired, it is possible to switch whether or not to acquire the second bootstrapping key. Therefore, the first communication device can appropriately re-execute the DPP process when a Wi-Fi connection is not established.

This specification also discloses a second communication device. A second communication device is obtained using a first bootstrapping key of the second communication device and one-time information indicating that the first bootstrapping key is a one-time key. an output control unit that causes the output unit to output first output information; and in response to the first output information being output by the output unit, the first bootstrapping key and the one-time information a first DPP processing execution unit that executes DPP processing according to DPP (Device Provisioning Protocol) of the Wi-Fi standard when the data is acquired by the first communication device; a process of receiving an authentication request using the first bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device; a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when an authentication request is received; and a process of transmitting an authentication response to the first communication device when the authentication request is received; A process of communicating first connection information with the first communication device via the Wi-Fi interface, wherein the first connection information is communicated with the first communication device or the second communication device. The first DPP processing execution unit includes the processing, which is information for establishing a Wi-Fi connection between the communication device and the external device via the Wi-Fi interface; a second bootstrapping key of the second communication device, the second bootstrapping key being different from the first bootstrapping key obtained when an Fi connection is not established; a second output control unit that causes the output unit to output second output information; a second DPP processing execution unit that executes the DPP processing in which the second bootstrapping key is used instead of the first bootstrapping key when the first bootstrapping key is acquired by the first communication device; You may prepare.

According to the above configuration, the second communication device outputs the first bootstrapping key and one-time information indicating that the first bootstrapping key is a one-time key. The second communication device outputs a second bootstrapping key when a Wi-Fi connection between the first communication device or the second communication device and the external device is not established, and the second communication device outputs a second bootstrapping key. Execute DPP processing using the strapping key. In this way, the second communication device may output the second bootstrapping key when a Wi-Fi connection is not established between the first communication device or the second communication device and the external device. Can be done. Therefore, the second communication device can appropriately re-execute the DPP process when a Wi-Fi connection is not established.

Other second communication devices are also disclosed herein. A second communication device outputs output information obtained using the bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key to an output unit. a Wi-Fi output control unit that outputs a Wi-Fi signal when the bootstrapping key and the one-time information are acquired by the first communication device in response to the output information being output by the output unit; A first DPP processing execution unit that executes DPP processing according to a standard DPP (abbreviation for Device Provisioning Protocol), the DPP processing is performed from the first communication device to the Wi-Fi of the second communication device. A process of receiving an authentication request using the bootstrapping key via the Wi-Fi interface, and a process of receiving an authentication request using the bootstrapping key via the Wi-Fi interface when the authentication request is received from the first communication device a process of transmitting a response to the first communication device; and when the authentication response is transmitted to the first communication device, communication of connection information to the first communication device via the Wi-Fi interface; and the connection information is for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface. the first DPP processing execution unit including the processing that is information; and a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key when the Wi-Fi connection is not established. The DPP processing execution unit may also be provided.

According to the above configuration, the second communication device outputs a bootstrapping key and one-time information indicating that the bootstrapping key is not a one-time key. The second communication device re-executes the DPP process using the bootstrapping key when a Wi-Fi connection is not established between the first communication device or the second communication device and the external device. . In this way, the second communication device can appropriately re-execute the DPP process if a Wi-Fi connection is not established.

Other second communication devices are also disclosed herein. The second communication device has a code image obtained by encoding the bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key. The bootstrapping key and the one-time information are acquired by the first communication device in response to the affixed casing and the code image being photographed by the first communication device. a first DPP processing execution unit that executes DPP processing according to DPP (abbreviation of Device Provisioning Protocol) of the Wi-Fi standard, the DPP processing is carried out from the first communication device to the second communication device; a process of receiving an authentication request using the bootstrapping key via the Wi-Fi interface of the first communication device; and a process of receiving the authentication request using the bootstrapping key from the first communication device; a process of transmitting an authentication response to the first communication device via an interface; and, when the authentication response is transmitted to the first communication device, communication of connection information via the Wi-Fi interface; The process is executed with the first communication device, and the connection information includes a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface. A Wi-Fi connection between the first DPP processing execution unit, the first communication device or the second communication device, and the external device includes the processing, which is information for establishing a connection. The apparatus may further include a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key if the bootstrapping key is not established.

According to the above configuration, the second communication device has a code image pasted on which a bootstrapping key and one-time information indicating that the bootstrapping key is not a one-time key are encoded. Equipped with a casing. The second communication device re-executes the DPP process using the bootstrapping key when a Wi-Fi connection is not established between the first communication device or the second communication device and the external device. . In this way, the second communication device can appropriately re-execute the DPP process if a Wi-Fi connection is not established.

A computer-readable recording medium storing a computer program for the first communication device, the first communication device itself realized by the computer program, and a method executed by the first communication device are also novel. It is useful in Also novel and useful are a computer program for the second communication device, a computer-readable recording medium storing the computer program, and a method executed by the second communication device. Further, a communication system including the above first communication device and the above second communication device is also new and useful.

An overview of the communication system is shown. The characteristics of each printer are shown below. The control configuration of each device is shown. Shows a flowchart of processing performed by the app. A sequence diagram of case A1 is shown. A sequence diagram continuing from FIG. 5 is shown. A sequence diagram of case A2 is shown. A sequence diagram of case A3 is shown. A sequence diagram of case B1 and case B2 is shown. A sequence diagram of case C is shown. A sequence diagram of case D1 and case D2 is shown. A sequence diagram of case E1 and case E2 is shown. A sequence diagram of case F1 is shown. A sequence diagram of case F2 is shown. A sequence diagram of case G1 and case G2 is shown. A sequence diagram of case H1 and case H2 is shown. A sequence diagram of case I1 and case I2 is shown. A sequence diagram of case J1 is shown. A sequence diagram of case J2 is shown. A sequence diagram of case K1 and case K2 is shown. A summary of each case of this example is shown.

(Outline of communication system; Figure 1)
As shown in FIG. 1, the communication system 2 includes an AP (abbreviation for Access Point) 6, a plurality of printers 10A to 10K, and a terminal 100. Below, when the printers 10A to 10K are not particularly distinguished, they may be simply referred to as "printer 10." In this embodiment, a situation is described in which a wireless connection according to the Wi-Fi standard (hereinafter referred to as "Wi-Fi connection") is established between each of the printers 10A to 10K and the AP 6 using the terminal 100. I am assuming that.

(Characteristics of each printer; Figure 2)
The characteristics of each printer 10A to 10K will be explained with reference to FIG. FIG. 2 shows the combination of setup information output means and one-time information for each of the printers 10A to 10K. The setup information output means indicates means by which each printer 10A to 10K outputs setup information. Here, the setup information means information used when establishing a Wi-Fi connection between each of the printers 10A to 10K and the AP 6, and includes, for example, the public key of each of the printers 10A to 10K. Details of the setup information will be described later. The one-time information includes "YES" indicating that the public key included in the setup information is a one-time key (i.e., a key that can be used only once), and "YES" indicating that the public key is not a one-time key (i.e., a permanent key). "NO" indicates that the key is available for public use.

Each of the printers 10A and 10B can output setup information by displaying a QR code (registered trademark) obtained by encoding the setup information. In particular, the public key of printer 10A is a one-time key, and the public key of printer 10B is not a one-time key. The printer 10C also includes a housing 50 (see FIG. 1) on which a QR code obtained by encoding setup information is pasted.

The printers 10D to 10G can output setup information by using wireless communication in accordance with the Bluetooth (registered trademark) standard. Hereinafter, Bluetooth will be referred to as "BT", and wireless communication according to the BT standard will be referred to as "BT communication". The BT standard is, for example, the IEEE802.15.1 standard and standards conforming thereto. More specifically, each printer 10D to 10G supports BLE (abbreviation for Bluetooth Low Energy). BLE is realized by version 4.0 or a later version of the BT standard. In particular, each of printers 10D and 10E transmits setup information to terminal 100 using an advertisement signal. Each of the printer 10F and the printer 10G transmits setup information to the terminal 100 using a one-to-one connection by BT (for example, GATT (abbreviation for Generic Attribute Profile)). Furthermore, the public keys of printer 10D and printer 10F are one-time keys, and the public keys of printer 10E and printer 10G are not one-time keys.

Each of the printers 10H to 10K can output setup information by using communication based on the NFC (Near Field Communication) method (hereinafter referred to as "NFC communication"). The NFC method is a wireless communication method based on the international standard of ISO/IEC21481 or 18092, for example. Each of printers 10H and 10I directly transmits setup information to terminal 100 using NFC communication. Further, each of the printer 10J and the printer 10K uses NFC communication to send information for establishing a Wi-Fi connection with the printer to the terminal 100, and uses the Wi-Fi connection to perform setup. Send the information to the terminal 100. In this way, information for establishing a Wi-Fi connection is communicated between a pair of devices using NFC communication, and then the desired data is communicated using the Wi-Fi connection. is sometimes referred to as "NFC handover." Further, the public keys of the printers 10H and 10J are one-time keys, and the public keys of the printers 10I and 10K are not one-time keys.

(Control configuration of each device; Figure 3)
Next, the control configuration of the printer 10 (that is, each of the printers 10A to 10K) and the terminal 100 will be described with reference to FIG.

(Configuration of printer 10)
The printer 10 is a peripheral device (for example, a peripheral device of the terminal 100) that can execute a printing function. In a modification, the printer 10 may be a multi-function device capable of performing a scanning function, a facsimile function, and the like. The printer 10 includes an operation section 12, a Wi-Fi interface 16, and a print execution section 18. In the following, the interface will be referred to as "I/F". The operation unit 12 includes a plurality of keys. A user can input various instructions to the printer 10 by operating the operation unit 12. The printing execution unit 18 includes a printing mechanism such as an inkjet type or a laser type.

The Wi-Fi I/F 16 is a wireless I/F for performing Wi-Fi communication according to the Wi-Fi standard. Wi-Fi standards include, for example, the IEEE (Institute of Electrical and Electronics Engineers, Inc.) 802.11 standard and standards equivalent to it (e.g. 802.11a, 11b, 11g, 11n, 11ac, etc.) is a wireless communication standard for performing wireless communication. In particular, the Wi-Fi I/F 16 supports DPP (abbreviation for Device Provisioning Protocol) developed by the Wi-Fi Alliance. Details of DPP are described in the standard "Wi-Fi Easy Connect (trademark) Specification Version 2.0" created by the Wi-Fi Alliance.

Further, the Wi-Fi I/F 16 of the printer 10J and the printer 10K further supports WFD (abbreviation for Wi-Fi Direct (registered trademark)) developed by the Wi-Fi Alliance. The reason will be explained later. Details of WFD are described in the standard “Wi-Fi Direct (registered trademark) Specification Version 1.9” created by the Wi-Fi Alliance. In the following, a Wi-Fi connection established according to WFD will be referred to as a "WFD connection." Note that the Wi-Fi I/F 16 of each of the other printers 10A to 10I may or may not support WFD.

The printers 10A and 10B also include a display section 14. The display unit 14 is a display for displaying various information. The display section 14 is a so-called touch panel, and also functions as the operation section 12. In this embodiment, a QR code is displayed on the display unit 14. Note that each of the other printers 10C to 10K may or may not be provided with the display section 14.

Further, each printer 10D to 10G includes a BTI/F 20. The BTI/F 20 is an I/F for executing BT communication. Note that each of the other printers 10A to 10C and 10H to 10K may or may not be provided with the BTI/F 20.

Further, each printer 10H to 10K includes an NFC I/F 22. The NFC I/F 22 is an I/F for performing NFC communication. Note that each of the other printers 10A to 10G may or may not be provided with the NFC I/F 22.

Here, the differences between Wi-Fi communication, BT communication, and NFC communication will be described. The communication speed of each communication is the communication speed of Wi-Fi communication (for example, the maximum communication speed is 600 Mbps), the communication speed of BT communication (for example, the maximum communication speed is 24 Mbps), the communication speed of NFC communication (for example, the maximum communication speed (424 kbps). The frequency of carrier waves in each communication is 2.4 GHz band or 5.0 GHz band in Wi-Fi communication, 2.4 GHz band in BT communication, and 2.4 GHz band in NFC communication. It is 13.56MHz. That is, when the 5.0 GHz band is adopted as the carrier wave frequency in Wi-Fi communication, the carrier wave frequencies in each communication are different from each other. In addition, the maximum distance at which each communication can be executed is the maximum distance at which Wi-Fi communication can be executed (for example, 100 m), the maximum distance at which BT communication can be executed (for example, about several tens of meters), and the maximum distance at which NFC communication can be executed. In descending order of maximum possible distance (for example about 10 cm).

The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the program 36 stored in the memory 34. The memory 34 is composed of volatile memory, nonvolatile memory, and the like. The memory 34 further stores its own model name MN.

(Configuration of terminal 100)
The terminal 100 is a portable terminal device such as a mobile phone (for example, a smartphone), a PDA, or a tablet PC. In a modification, the terminal 100 may be a stationary PC, a notebook PC, or the like. The terminal 100 includes an operation section 112, a display section 114, a Wi-Fi I/F 116, a camera 118, and a control section 130. Each part 112 to 130 is connected to a bus line (numerals omitted).

The operation unit 112 is an I/F for inputting various instructions to the terminal 100. The display unit 114 is a display for displaying various information. The display section 114 is a so-called touch panel, and also functions as the operation section 112. Camera 118 is a device for photographing objects. In this embodiment, the camera 118 is used to photograph the QR code of the printer 10. The Wi-Fi I/F 116 supports DPP and WFD.

The control unit 130 includes a CPU 132 and a memory 134. CPU 132 executes various processes according to programs 136 and 138 stored in memory 134. The memory 134 is composed of volatile memory, nonvolatile memory, and the like.

The OS (abbreviation for Operating System) program 136 is a program for realizing the basic operations of the terminal 100. The application 138 is a program for establishing a Wi-Fi connection between the terminal 100 and the AP 6, and for establishing a Wi-Fi connection between the printer 10 and the AP 6. Hereinafter, the OS program and the application will be referred to as "OS" and "application", respectively. The application 138 is installed on the terminal 100, for example, from a server on the Internet (not shown) provided by the vendor of the printer 10 or a server on the Internet (not shown) provided by the vendor of the OS 136.

Note that by supplying instructions to the OS 136, the application 138 can cause the OS 136 to execute various processes, or cause other apps to execute various processes via the OS 136. Therefore, each process executed by the OS 136 or other apps in response to an instruction from the app 138 can also be said to be a process realized by the app 138 (that is, the CPU 132 is made to function as an execution unit that executes the process).

(App processing; Figure 4)
Next, with reference to FIG. 4, the processing realized by the CPU 132 of the terminal 100 executing the application 138 will be described. FIG. 4 shows a process for establishing a Wi-Fi connection between the printer 10 and the AP 6 according to DPP. In the following, a printer to which a Wi-Fi connection is established will be referred to as a "target printer." Furthermore, in the following description of the process shown in FIG. 4, the application 138 will be described as the main subject instead of the CPU 132. The process in FIG. 4 is started when a Wi-Fi setup operation is accepted from the user.

In S10, the application 138 displays a notification screen SC1 (see FIG. 5) on the display unit 114. The notification screen SC1 includes a message prompting the user to select the target printer, and options for specific means for selecting the target printer (ie, QR code photography, BT, NFC, and model name selection). The option "QR code photography" means selecting a target printer by photographing a QR code displayed or pasted on the target printer. The option "BT" means that the target printer is selected by executing BT communication with the target printer. The option "NFC" means selecting the target printer by performing NFC communication with the target printer. The option "model name selection" means to select the target printer by selecting the model name of the target printer.

In S12, the application 138 receives from the user a selection of means for selecting a target printer. Specifically, the application 138 first receives from the user the selection of one option from among the options on the notification screen SC1. In this case, processing according to the selected option is executed.

For example, when the option "QR code photography" is selected, the application 138 receives an operation from the user to photograph the QR code displayed or pasted on the target printer. As a result, the application 138 obtains setup information by decoding the QR code. When the option "BT" is selected, the application 138 receives setup information from the target printer using BT communication with the target printer. When the option "NFC" is selected, the application 138 receives setup information from the target printer using NFC communication with the target printer in response to the terminal 100 being brought closer to the target printer. If the option "model name selection" is selected, the application 138 accepts the selection of the model name of the target printer from the user. In this case, no setup information is obtained.

Here, as shown in FIG. 4, the setup information includes means information, a public key, one-time information, and DPP automatic migration information. The means information is information indicating the setup information acquisition means (that is, QR code photography, BT communication, or NFC communication). The public key is information used when performing authentication according to DPP. The one-time information indicates either "YES" indicating that the public key is a one-time key, or "NO" indicating that the public key is not a one-time key. The DPP automatic transition information includes "YES" indicating that the target printer will transition from a DPP non-responsive state to a DPP response state without accepting a DPP transition operation from the user, and "YES" indicating that the target printer will transition from a DPP non-responsive state to a DPP response state without accepting a DPP transition operation from a user. "NO" indicating that the DPP non-response state is to be shifted to the DPP response state. The DPP response state is a state in which DPP processing can be executed, that is, a DPP Authentication Request can be received and a DPP Authentication Response can be transmitted. The DPP non-response state is a state in which DPP processing cannot be executed, that is, a DPP Authentication Response cannot be transmitted. Acquisition of the setup information described above corresponds to bootstrapping of DPP.

In S14, the application 138 determines whether setup information has been acquired. Specifically, when any of the options "QR code", "BT", and "NFC" is selected, the application 138 acquires setup information by executing processing according to the option. Therefore, YES is determined in S14, and the process proceeds to S20, where the setup information is stored. On the other hand, when the option "model name selection" is selected, the application 138 determines NO in S14 because no setup information is acquired, and proceeds to S16.

The application 138 displays the setup information acquisition means on the display unit 14 in S16. The application 138 stores, for each printer model name, a setup information output means (see FIG. 2) for the printer having the model name. The application 138 specifies the setup information acquisition means (i.e., one or more means of QR code photography, BT, and NFC) from the setup information output means of the printer having the selected model name (i.e., the target printer). do. The application 138 then displays the identified acquisition means on the display unit 14. By viewing the display, the user can learn the means for acquiring setup information from the target printer. After completing the process in S16, the application 138 executes the process in S10 again.

In S22, the application 138 determines whether the means information included in the acquired setup information indicates "QR code" and the DPP automatic migration information indicates "NO". If the means information indicates "QR code" and the DPP automatic transfer information indicates "NO", the application 138 determines YES in S22 and proceeds to S24. On the other hand, the application 138 determines NO in S22 and proceeds to S30 in cases other than the above (that is, when the means information is different from "QR code" or when the DPP automatic transfer information indicates "YES"). move on.

In S24, the application 138 causes the display unit 114 to display a screen that asks the user whether or not the DPP migration operation has been performed on the target printer. The screen includes a message asking the user whether or not the DPP migration operation has been executed for the target printer, a YES button, and a NO button.

In S26, the application 138 determines whether the YES button or the NO button on the above screen has been selected. The application 138 proceeds to S30 if the YES button is selected (YES in S26), and proceeds to S28 if the NO button is selected (NO in S26). Note that the situation in which the YES button is selected on the above screen is a case in which the target printer displays a QR code in response to accepting a DPP transition operation from the user (for example, see case A2 described below). On the other hand, the situation in which the NO button is selected on the above screen is a case where a QR code is pasted on the casing of the target printer (see Case C below).

In S28, the application 138 causes the display unit 114 to display a screen prompting the user to perform a DPP migration operation on the target printer. As a result, after the user viewing the screen executes a DPP migration operation for the target printer, the processes from S30 onwards are executed.

The application 138 starts DPP processing in S30. Specifically, the application 138 first sends an Authentication Request using the acquired public key to the target printer. As a result, various processes according to DPP (hereinafter referred to as ``DPP processing'') such as DPP Authentication (hereinafter referred to as ``Auth'') and Configuration (hereinafter referred to as ``Config'') are performed on the terminal. 100 and the target printer.

In S32, the application 138 determines whether a Wi-Fi connection has been established between the target printer and an AP (for example, AP6). Specifically, when a Wi-Fi connection is established between the target printer and the AP, the application 138 receives a Status Query Result (hereinafter referred to as "Status Query Result") containing information indicating that the Wi-Fi connection has been established from the target printer. (hereinafter simply written as "Result") is received. On the other hand, if a Wi-Fi connection is not established between the target printer and the AP, the application 138 receives a Result containing information indicating that the Wi-Fi connection has not been established from the target printer. When the application 138 receives a Result containing information indicating that a Wi-Fi connection has been established from the target printer, it determines YES in S32 and ends the process of FIG. 4. On the other hand, when the application 138 receives a Result containing information indicating that a Wi-Fi connection has not been established from the target printer, it determines NO in S32 and proceeds to S34.

In S34, the application 138 causes the display unit 114 to display a screen representing a means for re-executing the DPP process (for example, retaking a QR code, etc.) based on the means information included in the setup information stored in S20. A specific example of the screen and its details will be described later. Since the re-execution means determined based on the means information is displayed, an appropriate re-execution means can be presented to the user.

In S36, the application 138 determines whether execution of the re-execution means has been received from the user. If the application 138 accepts the execution of the re-execution means from the user, it determines YES in S36 and re-executes the process in S30. On the other hand, when the application 138 receives an operation from the user to cancel the re-execution of the DPP process, the application 138 determines NO in S36 and ends the process of FIG. 4.

(Case A1; Figures 5 and 6)
Next, a specific case realized by the process of FIG. 4 will be described with reference to FIGS. 5 to 20. First, case A1 will be explained with reference to FIGS. 5 and 6. Case A1 is a case where DPP processing is executed between the terminal 100 and the printer 10A. In particular, case A1 is a case in which the DPP migration information indicates "YES" because the printer 10A does not store the DPP Configuration Object (hereinafter referred to as "CO").

Although not shown, in the initial state of FIG. 5, DPP processing is being executed between the terminal 100 and the AP 6, and a Wi-Fi connection has been established between the terminal 100 and the AP 6. In the following description of FIG. 5, for ease of understanding, the operations executed by the CPUs of each device (e.g., CPU 32, 132, etc.) will not be described with the CPU as the main character. 100 etc.) are mainly listed. The same applies to the explanations of FIGS. 6 to 20.

At T100 in FIG. 5, when the user performs an operation to turn on the power of the printer 10A, the power of the printer 10A is turned on at T102. In this case, the printer 10A generates the public key PKA1 at T104, generates the QR code QRA1 at T106, transitions from the DPP non-response state to the DPP response state at T110, and displays the QR code QRA1 at T112. Displayed in section 14. QR code QRA1 is a code image (i.e., setup information) obtained by encoding means information "QR code", public key PKA1, one-time information "YES", and DPP automatic migration information "YES". (code image obtained by encoding).

Although not shown, the printer 10A generates a private key corresponding to the public key PKA1 at T104. The public key PKA1 and the private key are used when performing authentication according to DPP. In this way, since the public key PKA1 is generated at T104 when the printer 10A is powered on, the printer 10A does not need to store the public key PKA1 in advance.

The terminal 100 receives an operation to start the application 138 from the user at T120. As a result, when the application 138 is started, the application 138 displays the notification screen SC1 on the display unit 114 at T122 (S10 in FIG. 4).

At T124, the terminal 100 receives a selection of the option "QR code photography" on the notification screen SC1 from the user. In this case, the terminal 100 activates the camera 118. Then, at T126, the terminal 100 receives an operation to photograph the QR code QRA1 displayed on the printer 10A using the camera 118 (S12). In this case, the terminal 100 acquires the setup information by decoding the photographed QR code QRA1 (YES at S14), and stores the acquired setup information in the memory 134 at T128 (S20). The process at T126 corresponds to bootstrapping of DPP.

Further, when the terminal 100 stores the setup information in T128, the DPP automatic migration information included in the stored setup information indicates "YES" (NO in S22), so in T130, the terminal 100 stores the setup information via the Wi-Fi I/F 116. Then, an Auth Request using the public key PKA1 is sent to the printer 10A (S30). Hereinafter, Request will be referred to as "Req".

Auth Req is a signal requesting execution of authentication of the terminal 100 of the transmission source. Specifically, the terminal 100 first generates a shared key using the private key of the terminal 100 (not shown) and the public key PKA1 of the printer 10A, and encrypts a random value using the shared key. Generate encrypted data by Then, the terminal 100 transmits an Auth Req including the public key of the terminal 100 (not shown), the encrypted data, and the capability of the terminal 100 to the printer 10A. Capability of the terminal 100 includes a value indicating that it can operate only as a DPP Configurator.

Upon receiving the Auth Req from the terminal 100 via the Wi-Fi I/F 16 at T130, the printer 10A performs authentication of the encrypted data included in the Auth Req. Specifically, the printer 10A generates a shared key using the public key of the terminal 100 and the private key of the printer 10A included in the Auth Req, and decrypts the encrypted data using the shared key. If the decryption of the encrypted data is successful, the printer 10A determines that the authentication has been successful, and executes the processes from T132 onwards.

The printer 10A transitions from the DPP response state to the DPP non-response state at T132. This is because the authentication of the encrypted data has been successful, so there is no need to maintain the DPP response state. Since the DPP response state has a higher processing load on the printer 10A than the DPP non-response state, the processing load on the printer 10A can be reduced by shifting from the DPP response state to the DPP non-response state.

Further, at T134, the printer 10A transmits an Auth Response including the capability of the printer 10A to the terminal 100 via the Wi-Fi I/F 16. Hereinafter, Response will be referred to as "Res". Capability of the printer 10A includes a value indicating that it can operate only as a DPP Enrollee.

When the terminal 100 receives the Auth Res from the printer 10A at T134, the terminal 100 determines that the Capability (ie, Enrollee) of the printer 10A included in the Auth Res does not conflict with the Capability (ie, Configurator) of the terminal 100 itself. Then, the terminal 100 transmits Auth Confirm to the AP 6 via the Wi-Fi I/F 116 at T135. Auth Confirm includes information indicating that the terminal 100 operates as a configurator and that the printer 10A operates as an enrollee. As a result, the terminal 100 determines to operate as a configurator at T136. The Configurator is a device responsible for sending the CO to the Enrollee.

Further, at T138, the printer 10A determines to operate as an Enrollee. The Enrollee is a device that is responsible for receiving CO from the Configurator. The processes T130 and T134 to T138 correspond to DPP Auth.

The printer 10A transmits the Config Req to the terminal 100 via the Wi-Fi I/F 16 at T140. Config Req is a signal requesting transmission of a CO.

When the terminal 100 receives the Config Req from the printer 10A at T140, it generates a CO for the printer. Specifically, the terminal 100 first generates a printer Signed Connector (hereinafter referred to as "SC"), which is information to be used by the printer 10A to establish a Wi-Fi connection. The printer SC includes, for example, a group ID that is an identifier for identifying a wireless network. Then, the terminal 100 generates a printer CO including the printer SC, and transmits Config Res including the printer CO to the printer 10A via the Wi-Fi I/F 116 at T142.

Upon receiving the Config Res from the terminal 100 via the Wi-Fi I/F 16 at T142, the printer 10A transmits the Config Result to the terminal 100 via the Wi-Fi I/F 16 at T144. Config Result includes information indicating that Config was successful. The processing from T140 to T144 corresponds to DPP Config.

At T150, the printer 10A transmits a Discovery Req including the printer SC to the AP 6 via the Wi-Fi I/F 16. Discovery Req is a signal requesting transmission of the other party's SC. However, in this case, the AP 6 does not receive the Discovery Req due to the poor radio wave environment of the AP 6. As a result, the AP 6 does not send Discovery Res to the printer 10A.

At T152, if the printer 10A does not receive a Discovery Res from the AP 6 even after a predetermined period of time has elapsed after sending the Discovery Req to the AP 6, the printer 10A sends a Result to the terminal 100. The Result includes information "error" indicating that a Wi-Fi connection was not established between the printer 10A and the AP 6. Although not shown in the figure, if a Wi-Fi connection is not established between the printer 10A and the AP 6, the printer 10A deletes the received printer CO at T142.

(Continuation of Figure 5; Figure 6)
When the terminal 100 receives a Result containing an error from the target printer via the Wi-Fi I/F 116 at T152 in FIG. 5, the terminal 100 displays the notification screen SC2 on the display unit 114 at T154 in FIG. S34). Specifically, first, the terminal 100 identifies a message indicating that the setup has failed (that is, the Wi-Fi connection was not established between the printer 10A and the AP 6). Next, since the means information included in the stored setup information indicates "QR code" and the one-time information indicates "YES", terminal 100 specifies a message prompting re-photography of the QR code. This is because the public key of the printer 10A is a one-time key, so it is necessary to obtain the public key again. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation. As a result, the notification screen SC2 includes a message indicating that the setup has failed and a message prompting to retake the QR code, but does not include a message prompting the DPP transition operation. That is, the notification screen SC2 includes messages specified by the terminal 100 and does not include messages not specified by the terminal 100. This notifies the user that the setup has failed and that the QR code should be photographed again.

When the printer 10A sends the error-containing Result to the terminal 100, the printer 10A generates a public key PKA2 different from the public key PKA1 at T156, generates a QR code QRA2 at T158, and returns the DPP from the DPP non-response state at T160. Transitioning to the response state, the QR code QRA2 is displayed on the display section 14 at T162. That is, if the printer 10A does not receive a Discovery Res from the AP 6 even after a predetermined period of time has elapsed after transmitting the Discovery Req to the AP 6 at T150 in FIG. Execute the process. In this way, when the Wi-Fi connection between the printer 10A and AP6 is not established, the public key PKA2 is automatically generated at T156 (that is, without accepting any operation from the user), so that the user's Improved convenience. QR code QRA2 is a code image obtained by encoding setup information including public key PKA2 instead of public key PKA1.

In response to viewing the notification screen SC2, the user re-photographs the QR code QRA2 at T164. The processes at T164 and T166 are similar to the processes at T126 and T128 in FIG. 5, except that the setup information is different (specifically, the public key PKA2 is used). Thereafter, processing similar to the processing from T130 to T144 in FIG. 5 is executed, except that the public key PKA2 is used.

At T166, the printer 10A transmits a Discovery Req including the printer SC to the AP 6 via the Wi-Fi I/F 16. At the stage T166, the radio wave environment of AP6 has been improved. Therefore, the AP 6 receives the Discovery Request from the printer 10A at T166.

Upon receiving the Discovery Req from the printer 10A at T166, the AP 6 uses the AP SC to authenticate the printer SC included in the Discovery Req. When the printer SC authentication is successful, the AP 6 generates a connection key. Then, at T168, the AP transmits Discovery Res including the SC for AP to the printer 10A.

Upon receiving the Discovery Res from the AP 6 at T168, the printer 10A uses the printer SC to authenticate the AP SC included in the Discovery Res. When the AP SC authentication is successful, the printer 10A generates a connection key. The connection key generated here is the same as the connection key generated by AP6. That is, the connection key is shared by the printer 10A and the AP 6.

Next, the printer 10A uses the connection key to perform 4-way-handshake communication with the AP 6. As a result, a Wi-Fi connection is established between the printer 10A and the AP 6 at T170. Since a Wi-Fi connection has also been established between the terminal 100 and the AP 6, the terminal 100 and the printer 10A can communicate with each other via the AP 6. The processing from T166 to T170 corresponds to Network Access of DPP.

Further, although not shown, when the Wi-Fi connection with the AP 6 is established, the printer 10A stores the received printer CO in the memory 34. Therefore, from now on, the printer 10A uses "NO" instead of "YES" as the DPP automatic migration information. In a situation where the printer CO is stored, a Wi-Fi connection is established between the printer 10A and the device (AP6 in this case). If the DPP automatic transition information is "YES" in such a situation (that is, if the printer automatically transitions to the DPP response state), there is a possibility that the printer 10A may execute DPP processing in a situation that is not intended by the user. As a result, for example, the QR code of the printer 10A may be photographed by a third party different from the user of the printer 10A. When the printer 10A executes DPP processing in a situation not intended by the user, the printer 10A deletes the stored printer CO by receiving a new printer CO, and the Wi-Fi connection with the AP 6 is interrupted. May be disconnected. In order to suppress such an event, when a Wi-Fi connection is established between the printer 10A and the AP 6, that is, when the printer 10A stores the printer CO, the DPP automatic transition information changes from "YES" to " It will be changed to “NO”.

Further, when the Wi-Fi connection with the AP 6 is established, the printer 10A sends a Result containing information "success" indicating that the Wi-Fi connection has been established to the terminal 100 via the Wi-Fi I/F 16. Send.

At T172, the terminal 100 receives a Result indicating success from the printer 10A via the Wi-Fi I/F 116 (YES at S32 in FIG. 4).

As described above, the printer 10A can establish a Wi-Fi connection with the AP 6. For this purpose, the printer 10A can receive print data representing an image to be printed from the terminal 100 via the AP 6 and print the image represented by the print data.

(Case A2; Figure 7)
Next, case A2 will be explained with reference to FIG. Case A2 is a case where DPP processing is executed between the terminal 100 and the printer 10A. In particular, case A2 is a case where the DPP migration information indicates "NO" because the printer 10A has already stored the CO.

At T200 in FIG. 7, when the user performs an operation to turn on the power of the printer 10A, the power of the printer 10A is turned on at T202. In this case, since the printer 10A has already stored the CO, the printer 10A does not automatically transition to the DPP response state. When the printer 10A receives the DPP migration operation from the user at T203, it executes the processes from T204 to T212. The processes from T204 to T212 are the same as those from T104 to T112 in FIG. 5, except that the public key PKA3 is used and the QR code QRA3 is used. Since the printer 10A generates a public key when accepting a DPP migration operation from a user, it can generate the public key at an appropriate timing. The QR code QRA3 is a code image obtained by encoding setup information that includes the public key PKA3 instead of the public key PKA1 and includes the DPP automatic migration information "NO". Thereafter, processing similar to T120 to T128 in FIG. 5 is executed.

In this case, since the means information included in the stored setup information indicates "QR code" and the DPP automatic migration information indicates "NO" (YES in S22 of FIG. 4), the terminal 100 at T214 , an inquiry screen (see FIG. 4) is displayed on the display unit 114 (S24). In this case, since the user has already performed the DPP migration operation on the printer 10A (see T203), the terminal 100 accepts the user's selection of the YES button on the inquiry screen at T216 (YES at S26). In this case, the same processing as T130 to T152 in FIG. 5 is executed, except that the public key PKA3 is used. That is, the Wi-Fi connection between the printer 10A and the AP 6 is not established.

In this case, the terminal 100 displays the notification screen SC3 on the display unit 114 at T254 (S34 in FIG. 4). Specifically, first, the terminal 100 identifies a message indicating that setup has failed. Next, since the means information included in the stored setup information indicates "QR code" and the one-time information indicates "YES", terminal 100 specifies a message prompting re-photography of the QR code. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation. Therefore, the notification screen SC3 includes a message indicating that the setup has failed, a message prompting to retake the QR code, and a message prompting the DPP transition operation. This notifies the user that the setup has failed, that the QR code should be photographed again, and that the DPP migration operation should be performed.

In response to viewing the notification screen SC3, the user performs a DPP migration operation on the printer 10A at T255. The subsequent processes from T256 to T266 are performed from T156 to T266 in FIG. 6, except that the public key PKA4 is used, the QR code QRA4 is used, and the DPP automatic migration information "NO" is used. It is similar to T166. Since the printer 10A generates a public key when accepting a DPP migration operation from a user, it can generate the public key at an appropriate timing. Thereafter, the same processes as those in T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKA4 is used, and a Wi-Fi connection is established between the printer 10A and AP6. Established.

(Case A3; Figure 8)
Next, case A3 will be explained with reference to FIG. Case A3 is a case where DPP processing is executed between the terminal 100 and the printer 10A. In particular, case A3 is a case where "model name selection" is selected as the target printer selection means. The initial state of case A3 is similar to the initial state of case A1. In case A3, first, the same processing as T100 to T112 in FIG. 5 is executed. The processing at T320 and T322 is similar to the processing at T120 and T122 in FIG.

At T324, the terminal 100 accepts the selection of the option "model name selection" in the notification screen SC1, and then accepts the selection of the model name MNA of the printer 10A (S12 in FIG. 4). In this case, since the terminal 100 does not acquire setup information (NO in S14), it first specifies the setup information output means (ie, QR code) of the printer 10A. Then, at T326, the application 138 displays the notification screen SC4 on the display unit 114 (S16). The notification screen SC4 includes a message prompting the user to take a picture of the QR code. The user can know that the QR code should be photographed by viewing the notification screen SC4. Thereafter, the processing from T126 to T152 in FIG. 5 and the same processing as in FIG. 6 are executed, and a Wi-Fi connection is established between the printer 10A and the AP 6.

(Case B1; Figure 9)
Next, case B1 will be explained with reference to FIG. Case B1 is a case where DPP processing is executed between the terminal 100 and the printer 10B. In particular, case B1 is a case in which the DPP migration information indicates "YES" because the printer 10B does not store CO. As shown in FIG. 2, the public key of printer 10B is not a one-time key. The printer 10B stores the public key PKB in advance from the time the printer 10B is shipped.

The processing at T400 and T402 is similar to the processing at T100 and T102 in FIG. Furthermore, the processes from T406 to T412 are the same as those from T106 to T112 in FIG. 5, except that the setup information is different (specifically, the public key PKB is used and the one-time information "NO" is used). The process is similar to that of . Note that in a modified example, the printer 10B may store the QR code QRB1 from the time the printer 10B is shipped. In this modification, the process at T406 can be omitted. Thereafter, the same processes as T120 to T152 in FIG. 5 are executed, except that the public key PKB is used and the main body of the process is the printer 10B. That is, a Wi-Fi connection between the printer 10B and the AP 6 is not established.

At T422, the terminal 100 displays the notification screen SC5 on the display unit 114 (S34 in FIG. 3). Specifically, since the means information included in the stored setup information indicates "QR code" and the one-time information indicates "NO", the terminal 100 specifies a message prompting re-photography of the QR code. A message prompting the user to perform the DPP re-execution operation is identified. This is because the public key of the printer 10B is not a one-time key, so there is no need to reacquire the public key. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation. As a result, the notification screen SC5 includes a message indicating that the setup has failed and a message prompting the execution of the DPP re-execution operation, but does not include a message prompting the DPP migration operation.

When the printer 10B sends a Result containing an error to the terminal 100 (T152 in FIG. 5, referred to in FIG. 9), the printer 10B shifts from the DPP non-response state (see T132 in FIG. 5) to the DPP response state in T423.

In response to viewing the notification screen SC5, the user performs a DPP re-execution operation on the terminal 100 at T424. In this case, the same processes as T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKB is used and the main body of the process is the printer 10B. A Wi-Fi connection is established between the printer 10B and the AP 6.

(Case B2; Figure 9)
Next, case B2 will be explained with reference to FIG. Case B2 is a case where DPP processing is executed between the terminal 100 and the printer 10B. In particular, case B2 is a case in which the DPP migration information indicates "NO" because the printer 10B has already stored the CO. In case B2, first, the same processes as T200 to T203 and T206 to T212 in FIG. 7 are executed, except that the public key PKB is used. After that, the process is similar to T120 to T128 in FIG. 5, T214, T216 in FIG. 7, and T130 to T152 in FIG. 5, except that the public key PKB is used and the main body of processing is the printer 10B. Processing is executed. That is, a Wi-Fi connection between the printer 10B and the AP 6 is not established.

At T432, the terminal 100 displays the notification screen SC6 on the display unit 114 (S34 in FIG. 3). Specifically, since the means information included in the stored setup information indicates "QR code" and the one-time information indicates "NO", the terminal 100 specifies a message prompting re-photography of the QR code. A message prompting the user to perform the DPP re-execution operation is identified. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation. As a result, the notification screen SC6 includes a message indicating that the setup has failed, a message prompting the DPP re-execution operation, and a message prompting the DPP migration operation.

In response to viewing the notification screen SC6, the user performs a DPP migration operation on the printer 10B at T434. In this case, the printer 10B transitions from the DPP non-responsive state to the DPP responsive state at T436. The processing at T438 is similar to the processing at T424. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKB is used and the main body of the process is the printer 10B. A Wi-Fi connection is established between 10B and AP6.

(Case C; Figure 10)
Next, case C will be explained with reference to FIG. Case C is a case where DPP processing is executed between the terminal 100 and the printer 10C. As described above, the printer 10C includes the housing 50 to which the QR code QRC is pasted (see FIG. 1). Therefore, the printer 10C stores the public key PKC, which is not a one-time key, from the time the printer 10C is shipped (see FIG. 2). Furthermore, regardless of whether the printer 10C stores the CO or not, the DPP automatic migration information indicates "NO".

The processing at T500 and T502 is similar to the processing at T100 and T102 in FIG. Thereafter, processing similar to T120 to T128 in FIG. 5 is executed. In this case, since the means information included in the stored setup information indicates "QR code" and the DPP automatic migration information indicates "NO" (YES in S22 of FIG. 4), the terminal 100 , an inquiry screen (see FIG. 4) is displayed on the display unit 114 (S24). In this case, since the user has not performed the DPP migration operation on the printer 10C, the terminal 100 accepts the selection of the NO button on the inquiry screen from the user at T506 (NO at S26). In this case, at T508, the terminal 100 causes the display unit 114 to display a screen (see FIG. 4) prompting the DPP transition operation (S28).

When the printer 10C receives a DPP transition operation from the user who viewed the screen at T510, the printer 10C transitions to the DPP response state at T512. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKC is used and the main body of the process is the printer 10C. That is, the Wi-Fi connection between the printer 10C and the AP 6 is not established.

At T522, the terminal 100 displays the notification screen SC6 on the display unit 114 (see S34 in FIG. 3 and FIG. 9). The specific process is the same as the process at T432 in FIG. The processing from T530 to T534 is similar to the processing from T434 to T438 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKC is used and the main body of the process is the printer 10C. A Wi-Fi connection is established between 10C and AP6.

(Case D1; Figure 11)
Next, case D1 will be explained with reference to FIG. 11. Case D1 is a case where DPP processing is executed between the terminal 100 and the printer 10D. In particular, case D1 is a case in which the DPP migration information indicates "YES" because the printer 10D does not store CO. In case D1, first, the same processing as T100 to T104 and T110 in FIG. 5 is executed, except that public key PKD1 is used.

The printer 10D supplies setup information to the BT I/F 20 at T612. In the setup information of this case, the means information indicates "BT (ADV_EXT)", the public key indicates PKD1, the one-time information indicates "YES", and the DPP automatic migration information indicates "YES". The means information "BT (ADV_EXT)" is information indicating that setup information is transmitted from the printer 10D to the terminal 100 using an advertisement signal.

The printer 10D repeatedly transmits BLE_ADV_EXT, which is an advertising signal including setup information. At stage T614, the advertisement signal is not received by the terminal 100.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). At T624, the terminal 100 receives the selection of the option "BT" in the notification screen SC1 from the user (S12). In this case, the terminal 100 changes the state of the BTI/F 120 of the terminal 100 from a state in which it cannot receive an advertisement signal to a state in which it can receive an advertisement signal. As a result, the terminal 100 receives the advertisement signal from the printer 10D and acquires the setup information at T626 (YES at S14), and stores the acquired setup information in the memory 134 at T628 (S20). After that, since the setup means included in the stored setup information indicates "BT (ADV_EXT)" (NO in S22), the exceptions are that the public key PKD1 is used and that the main body of the process is the printer 10D. Then, the same processing as T130 to T152 in FIG. 5 is executed. In particular, at T132 cited in FIG. 11, when the printer 10D enters the DPP non-responsive state, the printer 10D stops transmitting the advertisement signal.

At T654, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (ADV_EXT)", the terminal 100 identifies a message prompting the execution of the DPP re-execution operation. This is because if the user executes the DPP re-execution operation on the terminal 100, the terminal 100 can obtain setup information including a new public key by receiving an advertisement signal from the printer 10D. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The processes at T656 and T660 are similar to the processes at T156 and T160 in FIG. 6, except that the public key PKD2 is used. The process at T662 is similar to the process at T612, except that the setup information is different (specifically, the public key PKD2 is used). The process at T664 is similar to the process at T424 in FIG. Thereafter, the same processes as T626 and T628 are executed, and the terminal 100 acquires and stores new setup information. Furthermore, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10D and AP6.

(Case D2; Figure 11)
Next, case D2 will be explained with reference to FIG. 11. Case D2 is a case where DPP processing is executed between the terminal 100 and the printer 10D. In particular, case D2 is a case in which the DPP migration information indicates "NO" because the printer 10D has already stored the CO. In case D2, first, the same processing as T200 to T204 and T210 in FIG. 7 is executed, except that public key PKD3 is used. The process at T672 is similar to the process at T612, except that the setup information is different (specifically, the public key PKD3 is used and the DPP automatic migration information "NO" is used). Thereafter, T120 and T122 in FIG. 5 are executed, and the same processes as T624 to T628 are executed. As a result, the terminal 100 acquires and stores the setup information. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKD3 is used and the main body of the process is the printer 10D.

At T674, the terminal 100 displays the notification screen SC6 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (ADV_EXT)", the terminal 100 identifies a message prompting the execution of the DPP re-execution operation. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation. The process at T675 is similar to the process at T255 in FIG. Also, the processing at T676 is similar to the processing at T156 in FIG. 6, except that the public key is PKD4.

Thereafter, processes similar to T660 to T664 are executed, processes similar to T626 and T628 are executed, and the terminal 100 acquires and stores new setup information (that is, setup information including public key PKD4). Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10D and AP6.

(Case E1; Figure 12)
Next, case E1 will be explained with reference to FIG. 12. Case E1 is a case where DPP processing is executed between the terminal 100 and the printer 10E. In particular, case E1 is a case in which the DPP migration information indicates "YES" because the printer 10E does not store CO. As shown in FIG. 2, the public key of printer 10E is not a one-time key. The printer 10E stores the public key PKE in advance from the time the printer 10E is shipped. In case E1, first, processes similar to T100, T102, and T110 in FIG. 5 are executed.

The processes at T712 and T714 are similar to the processes at T612 and T614 in FIG. 11, except that the setup information is different (specifically, the public key PKE is used). Thereafter, processes similar to those at T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). The processing from T724 to T728 is similar to the processing from T624 to T628 in FIG. 11, except that the setup information is different and the main body of the processing is the printer 10E. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKE is used and the main body of the process is the printer 10E.

At T754, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (ADV_EXT)", the terminal 100 identifies a message prompting the execution of the DPP re-execution operation. In this way, when the means information indicates "BT (ADV_EXT)", the terminal 100 performs DPP replay regardless of whether the one-time information indicates "YES" or "NO". Identify messages that prompt you to perform an action. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The processing at T760 and T764 is similar to the processing at T660 and T664 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKE is used and the main body of the process is the printer 10E. A Wi-Fi connection is established between 10E and AP6.

(Case E2; Figure 12)
Next, case E2 will be explained with reference to FIG. 12. Case E2 is a case where DPP processing is executed between the terminal 100 and the printer 10E. In particular, case E2 is a case in which the DPP migration information indicates "NO" because the printer 10E has already stored the CO. In case E2, first, the same processing as T200 to T203 and T210 in FIG. 7 is executed. The process at T772 is similar to the process at T712, except that the setup information is different (specifically, the DPP automatic migration information "NO" is used). After that, T120 and T122 in FIG. 5 are executed, and the same processes as T724 to T728 are executed. As a result, the terminal 100 acquires and stores the setup information. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKE is used and the main body of the process is the printer 10E.

At T774, the terminal 100 displays the notification screen SC6 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (ADV_EXT)", the terminal 100 identifies a message prompting the execution of the DPP re-execution operation. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation.

The processing from T775 to T784 is similar to the processing from T434 to T438 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKE is used and the main body of the process is the printer 10E. A Wi-Fi connection is established between 10E and AP6.

(Case F1; Figure 13)
Next, case F1 will be explained with reference to FIG. 13. Case F1 is a case where DPP processing is executed between the terminal 100 and the printer 10F. In particular, case F1 is a case in which the DPP migration information indicates "YES" because the printer 10F does not store CO. In case F1, first, the same processing as T100 to T104 and T110 in FIG. 5 is executed, except that public key PKF1 is used. The process at T812 is the same as the process at T612 in FIG. 11, except that the setup information is different (specifically, the means information "BT (GATT)" is used and the public key PKF1 is used). The same is true. The means information "BT (GATT)" is information indicating that setup information is transmitted from the printer 10F to the terminal 100 using a one-to-one connection by BT.

The printer 10F repeatedly transmits the advertisement signal BLE_ADV_IND. The advertisement signal does not include setup information. At stage T814, the advertisement signal is not received by the terminal 100.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). At T824, the terminal 100 receives a selection of the option "BT" in the notification screen SC1 from the user (S12). In this case, the terminal 100 moves the BTI/F 120 of the terminal 100 from a state in which it cannot receive an advertisement signal to a state in which it can receive an advertisement signal. As a result, the terminal 100 receives an advertisement signal from the printer 10F at T825, and establishes a one-to-one connection by BT (ie, GATT connection) at T826.

At T827, the terminal 100 uses the GATT connection to transmit a setup information request to the printer 10F via the BTI/F 120.

Upon receiving the setup information request from the terminal 100 at T827, the printer 10F transmits the setup information to the terminal 100 via the BTI/F 20 using the GATT connection at T828.

When the terminal 100 receives the setup information from the printer 10F at T828 (YES at S14 in FIG. 4), the terminal 100 stores the received setup information in the memory 134 (S20). After that, since the means information included in the stored setup information indicates "BT (GATT)" (NO in S22), the exceptions are that the public key PKF1 is used and that the main body of processing is the printer 10F. Then, the same processing as T130 to T152 in FIG. 5 is executed. In particular, when the printer 10F transitions to the DPP non-responsive state at T132 cited in FIG. 13, the printer 10F stops transmitting the advertisement signal.

At T854, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information is "BT (GATT)", the terminal 100 specifies a message prompting execution of the DPP re-execution operation. This is because if the user executes the DPP re-execution operation on the terminal 100, the terminal 100 can obtain setup information including a new public key from the printer 10F using the GATT connection. Next, since the DPP automatic migration information included in the stored setup information is "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The processes at T856 and T860 are similar to the processes at T156 and T160 in FIG. 6, except that the public key PKF2 is used. The process at T862 is similar to the process at T812, except that the setup information is different (specifically, the public key PKF2 is used). The process at T864 is similar to the process at T424 in FIG. Thereafter, the same processing as T827 to T830 is executed, and the terminal 100 acquires and stores new setup information. Furthermore, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10F and AP6.

(Case F2; Figure 14)
Next, case F2 will be explained with reference to FIG. 14. Case F2 is a case where DPP processing is executed between the terminal 100 and the printer 10F. In particular, case F2 is a case in which the DPP migration information indicates "NO" because the printer 10F has already stored the CO. In case F2, first, the same processing as T100 and T102 in FIG. 5 is executed.

When the printer 10F is powered on, it repeatedly transmits the advertisement signal BLE_ADV_IND. The advertisement signal does not include setup information. At stage T874, the advertisement signal is not received by the terminal 100.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). At T876, the terminal 100 receives the selection of the option "BT" in the notification screen SC1 from the user (S12). In this case, the terminal 100 moves the BTI/F 120 of the terminal 100 from a state in which it cannot receive an advertisement signal to a state in which it can receive an advertisement signal. As a result, the terminal 100 receives an advertisement signal from the printer 10F at T877, and establishes a one-to-one connection by BT (ie, GATT connection) at T826.

At T880, the terminal 100 uses the GATT connection to transmit a serial number request to the printer 10F via the BTI/F 120, requesting transmission of the serial number of the printer 10F.

Upon receiving the serial number request from the terminal 100 at T880, the printer 10F transmits the serial number of the printer 10F to the terminal 100 via the BT I/F 20 using the GATT connection at T882.

When the terminal 100 requests a serial number from the printer 10F at T882, the terminal 100 transmits a password to the printer 10F via the BTI/F 120 using the GATT connection at T884. The password may be stored in advance in the terminal 100 in association with the serial number of the printer 10F, or may be input by the user after the process at T882.

Upon receiving the password from the terminal 100 at T884, the printer 10F authenticates the password. In this case, since the password authentication is successful, the printer 10F transmits a signal indicating that the authentication is OK to the terminal 100 via the BT I/F 20 using the GATT connection at T886. Note that if the authentication fails, the printer 10F does not execute the processes from T886 onwards.

When the terminal 100 receives a signal indicating authentication OK from the printer 10F at T886, the terminal 100 transmits a DPP migration request to the printer 10F via the BTI/F 120 using the GATT connection at T888. The DPP transition request is a signal requesting the printer 10F to transition the state of the printer 10F from the DPP non-responsive state to the DPP responsive state. In this way, in this case, there is no need to directly execute the DPP transition operation on the printer 10F in order to transition the state of the printer 10F from the DPP non-responsive state to the DPP responsive state.

The reason for executing the above authentication processes T880 to T886 is as follows. That is, as described above, in case F2, the printer 10F stores the printer CO. Further, there is no need to directly execute the DPP migration operation on the printer 10F. Therefore, if the above authentication process is not executed, the printer 10F receives a DPP transition request from a third party's terminal and stores a new CO in place of the already stored CO for the printer. There is a possibility that it will be stored away. As a result, the Wi-Fi connection between the printer 10F and the device may be disconnected. On the other hand, in this case, since the above authentication is performed, only the authorized user of the printer 10F can use the terminal 100 to send a DPP migration request to the printer 10F. For this reason, the occurrence of the above phenomenon can be suppressed.

The processes at T889 and T890 are similar to the processes at T104 and T110 in FIG. 5, except that the public key is PKF3. In addition, the processing of T891 to T894 is the same as the processing of T812 and T827 to T830 in FIG. 13, except that the setup information is different (specifically, public key PKF3 and DPP automatic migration information "NO" are used). It is similar to Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKF3 is used and the main body of the process is the printer 10F.

At T895, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (GATT)," the terminal 100 specifies a message prompting the execution of the DPP re-execution operation, and also specifies a message prompting the DPP migration operation. not specified. This is because, as described above, in this case, the terminal 100 uses the GATT connection to send the DPP migration request to the printer 10F, so there is no need to directly execute the DPP migration operation on the printer 10F. The process at T896 is similar to the process at T424 in FIG. Furthermore, the processing of T897 and T898 is similar to the processing of T888 and T889, except that the public key is PKF4.

Thereafter, the same processing as T890 to T894 is executed, except that the public key PKF4 is used, and the terminal 100 acquires and stores new setup information. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10F and AP6.

(Case G1; Figure 15)
Next, case G1 will be explained with reference to FIG. 15. Case G1 is a case where DPP processing is executed between the terminal 100 and the printer 10G. In particular, case G1 is a case in which the DPP migration information indicates "YES" because the printer 10G does not store CO. As shown in FIG. 2, the public key of printer 10G is not a one-time key. The printer 10G stores the public key PKG in advance from the time the printer 10G is shipped. In case G1, first, processes similar to T100, T102, and T110 in FIG. 5 are executed.

The process of T912 is similar to the process of T812 in FIG. 13, except that the setup information is different (specifically, the public key PKG is used and the one-time information "NO" is used). be. Further, the process at T914 is similar to the process at T814 in FIG.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to T824 to T830 in FIG. 13 is executed, and the terminal 100 receives setup information from the printer 10G using the GATT connection, and stores the setup information (YES in S12 and S14, S20). . Next, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKG is used and the main body of the process is the printer 10G.

At T954, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (GATT)," the terminal 100 specifies a message prompting the execution of the DPP re-execution operation, and also specifies a message prompting the DPP migration operation. not specified. In this way, when the means information indicates "BT (GATT)", the terminal 100 performs DPP replay regardless of whether the one-time information indicates "YES" or "NO". Identify messages that prompt you to perform an action.

The process at T960 is similar to the process at T160 in FIG. Further, the process at T964 is similar to the process at T424 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10G and AP6.

(Case G2; Figure 15)
Next, case G2 will be explained with reference to FIG. 15. Case G2 is a case where DPP processing is executed between the terminal 100 and the printer 10G. In particular, case G2 is a case in which the DPP migration information indicates "NO" because the printer 10G has already stored the CO. In case G2, first, the same processing as T100 and T102 in FIG. 5 is executed. The processing at T974 is similar to the processing at T874 in FIG.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to T876 to T894 in FIG. 14 is executed, and the terminal 100 receives setup information from the printer 10G using the GATT connection, and stores the setup information (YES in S12 and S14, S20). . Next, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKG is used and the main body of the process is the printer 10G.

At T992, the terminal 100 displays the notification screen SC5 on the display unit 114 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "BT (GATT)," the terminal 100 specifies a message prompting the execution of the DPP re-execution operation, and also specifies a message prompting the DPP migration operation. not specified.

The process at T995 is similar to the process at T424 in FIG. When the terminal 100 receives the execution of the DPP re-execution operation from the user at T995, the terminal 100 transmits a DPP migration request to the printer 10G via the BTI/F 120 using the GATT connection at T996.

Upon receiving the DPP transition request from the terminal 100 at T996, the printer 10G transitions from the DPP non-responsive state to the DPP responsive state at T997. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10G and AP6.

(Case H1; Figure 16)
Next, case H1 will be explained with reference to FIG. 16. Case H1 is a case where DPP processing is executed between the terminal 100 and the printer 10H. In particular, case H1 is a case in which the DPP migration information indicates "YES" because the printer 10H does not store CO. In case H1, first, the same processing as T100 to T104 and T110 in FIG. 5 is executed, except that public key PKH1 is used.

At T1012, the printer 10H supplies the setup information to the NFC I/F 22 and shifts the state of the NFC I/F 22 from a state in which NFC communication is not possible to a state in which NFC communication is possible. In the setup information of this case, the means information indicates "NFC (direct communication)", the public key is PKH1, the one-time information indicates "YES", and the DPP automatic migration information indicates "YES". The means information "NFC (direct communication)" is information indicating that the setup information is directly transmitted from the printer 10H to the terminal 100 using NFC communication.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). At T1024, the terminal 100 receives a selection of the option "NFC" in the notification screen SC1 from the user (S12). In this case, the terminal 100 shifts the state of the NFC I/F 122 of the terminal 100 from a state in which NFC communication is not possible to a state in which NFC communication is possible. Thereafter, at T1026, the user of the terminal 100 touches the printer 10H with the terminal 100 to establish an NFC connection between the terminal 100 and the printer 10H. Then, at T1027, the terminal 100 receives setup information from the printer 10H via the NFC I/F 122 using the NFC connection, and at T1028, stores the received setup information in the memory 134 (S20). After that, since the method information included in the stored setup information indicates "NFC (direct communication)" (NO in S22), it is confirmed that the public key PKH1 is used and that the main body of the process is the printer 10H. Except for this, the same processing as T130 to T152 in FIG. 5 is executed. In particular, at T132 cited in FIG. 16, when the printer 10H shifts to the DPP non-responsive state, the printer 10H shifts the state of the NFC I/F 22 from a state where NFC communication is possible to a state where NFC communication is not possible. let

At T1054, the terminal 100 displays the notification screen SC7 on the display unit 114 (S34 in FIG. 4). Specifically, since the means information included in the stored setup information indicates "NFC (direct communication)" and the one-time information indicates "YES", the terminal 100 connects the terminal 100 to the printer 10H again. Identify messages that prompt you to touch. This is because if the terminal 100 touches the printer 10H again, setup information including a new public key can be obtained using the NFC connection. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation. Therefore, the notification screen SC7 includes a message indicating that the setup has failed and a message prompting the user to touch the terminal 100 to the printer 10H again.

The processes at T1056 and T1060 are similar to the processes at T156 and T160 in FIG. 6, except that the public key PKH2 is used. Furthermore, the process at T1062 is similar to the process at T1012, except that the setup information is different (specifically, the public key PKH2 is used). The processing at T1064 is similar to the processing at T1026.

Thereafter, the processes of T1027 and T1028 are executed, and the terminal 100 receives and stores the setup information including the public key PKH2 via the NFC connection. Then, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10H and AP6.

(Case H2; Figure 16)
Next, case H2 will be explained with reference to FIG. 16. Case H2 is a case where DPP processing is executed between the terminal 100 and the printer 10H. In particular, case H2 is a case in which the DPP migration information indicates "NO" because the printer 10H has already stored the CO. In case H2, first, the same processing as T200 to T204 and T210 in FIG. 7 is executed, except that public key PKH3 is used. The process at T1072 is similar to the process at T1012, except that the setup information is different (specifically, the public key PKH3 is used and the DPP automatic migration information "NO" is used).

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to the processing from T1024 to T1028 is executed, except that the setup information is different, and the terminal 100 receives and stores the setup information. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKH3 is used and the main body of the process is the printer 10H.

At T1074, the terminal 100 displays the notification screen SC8 on the display unit 114 (S34 in FIG. 4). Specifically, since the means information included in the stored setup information indicates "NFC (direct communication)" and the one-time information indicates "YES", the terminal 100 connects the terminal 100 to the printer 10H again. Identify messages that prompt you to touch. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation. Therefore, the notification screen SC8 includes a message indicating that the setup has failed, a message prompting the user to touch the terminal 100 to the printer 10H again, and a message prompting the DPP migration operation. The process at T1075 is similar to the process at T255 in FIG. Further, the process at T1076 is similar to the process at T156 in FIG. 6, except that the public key PKH4 is used.

After that, the same processes as T1060 to T1064 are executed, and then the same processes as T1027 and T1028 are executed, and setup information including the public key PKH4 is received and stored via the NFC connection. Then, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10H and AP6.

(Case I1; Figure 17)
Next, case I1 will be explained with reference to FIG. 17. Case I1 is a case where DPP processing is executed between the terminal 100 and the printer 10I. In particular, case I1 is a case in which the DPP migration information indicates "YES" because the printer 10I does not store the CO. As shown in FIG. 2, the public key of printer 10I is not a one-time key. The printer 10I stores the public key PKI in advance from the time the printer 10I is shipped. In case I1, first, the same processes as T100, T102, and T110 in FIG. 5 are executed. The process of T1112 is the same as the process of T1012 in FIG. 16, except that the setup information is different (specifically, the public key PKI is used and the one-time information "NO" is used). .

Thereafter, processes similar to those at T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). The processing from T1124 to T1128 is similar to the processing from T1024 to T1028 in FIG. 16, except that the setup information is different and the main body of the processing is the printer 10I. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKI is used and the main body of the process is the printer 10I.

At T1154, the terminal 100 causes the display unit 114 to display the notification screen SC5 (see S34 in FIG. 4 and FIG. 9). Specifically, since the method information included in the stored setup information indicates "NFC (direct communication)" and the one-time information is "NO", the terminal 100 executes the DPP re-execution operation. Identify prompting messages. This is because the public key of the printer 10I is not a one-time key, so there is no need to reacquire the public key. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The process at T1160 is similar to the process at T160 in FIG. Furthermore, the process at T1164 is similar to the process at T424 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKI is used and the main body of the process is the printer A Wi-Fi connection is established between 10I and AP6.

(Case I2; Figure 17)
Next, case I2 will be explained with reference to FIG. 17. Case I2 is a case where DPP processing is executed between the terminal 100 and the printer 10I. In particular, case I2 is a case in which the DPP migration information indicates "NO" because the printer 10I has already stored the CO. In case HI, first, the same processing as T200 to T203 and T210 in FIG. 7 is executed. The process at T1172 is similar to the process at T1112, except that the setup information is different (specifically, the DPP automatic migration information "NO" is used).

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to the processing from T1124 to T1128 is executed, except that the setup information is different, and the terminal 100 receives and stores the setup information. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKI is used and the main body of the process is the printer 10I.

At T1174, the terminal 100 causes the display unit 114 to display the notification screen SC6 (see S34 in FIG. 4 and FIG. 9). Specifically, since the method information included in the stored setup information indicates "NFC (direct communication)" and the one-time information indicates "NO", the terminal 100 executes the DPP re-execution operation. Identify prompting messages. Next, since the DPP automatic migration information included in the stored setup information indicates "NO", the terminal 100 specifies a message prompting a DPP migration operation. The processing from T1175 to T1184 is similar to the processing from T434 to T438 in FIG.

Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKI is used and the main body of the process is the printer A Wi-Fi connection is established between 10I and AP6.

(Case J1; Figure 18)
Next, case J1 will be explained with reference to FIG. 18. Case J1 is a case where DPP processing is executed between the terminal 100 and the printer 10J. In particular, case J1 is a case in which the DPP migration information indicates "YES" because the printer 10J does not store CO. In case J1, first, the same processing as T100 to T104 and T110 in FIG. 5 is executed, except that public key PKJ1 is used. Although details will be described later, the setup information for case J1 includes means information "NFC handover." The means information "NFC handover" uses NFC communication to communicate information for establishing a Wi-Fi connection, and then uses the Wi-Fi connection to send setup information from the printer 10J to the terminal 100. This is information indicating that

The printer 10J supplies the WFD connection information to the NFC I/F 22 at T1212. The WFD connection information is information used to establish a WFD connection between the printer 10J and the terminal 100 (for example, the SSID (Service Set Identifier) of the wireless network in which the printer 10J operates as a WFD master station). It is.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). The processing at T1224 and T1226 is similar to the processing at T1024 and T1026 in FIG. 16.

At T1227, the terminal 100 receives WFD connection information from the printer 10H via the NFC I/F 122 using the NFC connection, and at T1028, the terminal 100 uses the received WFD connection information to establish a WFD connection with the printer 10J. Establish a connection.

At T1230, the terminal 100 uses the WFD connection to transmit a setup information request to the printer 10J via the Wi-Fi I/F 116.

Upon receiving the setup information request from the terminal 100 at T1230, the printer 10J supplies the setup information to the Wi-Fi I/F 16 at T1231, and at T1232 uses the WFD connection via the Wi-Fi I/F 16. , sends setup information to the terminal 100. In the setup information of this case, the means information indicates "NFC handover", the public key is PKJ1, the one-time information indicates "YES", and the DPP automatic transition information indicates "YES".

When the terminal 100 receives the setup information from the printer 10J (YES in S14 of FIG. 4), the terminal 100 stores the setup information in T1234 (S20). Thereafter, at T1236, the WFD connection between the terminal 100 and the printer 10J is disconnected.

After that, since the means information included in the stored setup information indicates "NFC handover" (NO in S22), the following steps are performed, except that the public key PKJ1 is used and the main body of the process is the printer 10J. Processing similar to T130 to T152 in FIG. 5 is executed.

At T1254, the terminal 100 causes the display unit 114 to display the notification screen SC7 (see S34 in FIG. 4 and FIG. 16). Specifically, since the means information included in the stored setup information indicates "NFC handover" and the one-time information indicates "YES", the terminal 100 touches the printer 10H again. Identify messages that encourage This is because if the terminal 100 touches the printer 10H again, setup information including a new public key can be received using the WFD connection established by NFC handover. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The processes at T1256 and T1260 are similar to the processes at T156 and T160 in FIG. 6, except that the public key PKJ2 is used. The processing at T1262 is similar to the processing at T1212. Furthermore, the processing at T1264 is similar to the processing at T1226.

Thereafter, processing similar to T1227 to T1236 is executed, and the terminal 100 acquires and stores setup information including the public key PKJ2. Then, the same processes as those in T130 to T144 in FIG. 5 and T166 to T172 in FIG. 6 are executed, except that the public key PKJ2 is used and the main body of the process is the printer A Wi-Fi connection is established between 10J and AP6.

(Case J2; Figure 19)
Next, case J2 will be explained with reference to FIG. 19. Case J2 is a case where DPP processing is executed between the terminal 100 and the printer 10J. In particular, case J2 is a case in which the DPP migration information indicates "NO" because the printer 10J has already stored the CO. In case J2, first, the same processing as T100 to T104 in FIG. 5 is executed, except that public key PKJ3 is used. The processing at T1272 is similar to the processing at T1212 in FIG.

After that, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). The processes in T1274 to T1278 are the same as those in T1224 to T1228 in FIG. It is.

At T1280, the terminal 100 uses the WFD connection via the Wi-Fi I/F 116 to transmit a serial number request to the printer 10J, requesting transmission of the serial number of the printer 10J.

Upon receiving the serial number request from the terminal 100 at T1280, the printer 10J transmits the serial number of the printer 10J to the terminal 100 via the Wi-Fi I/F 16 using the WFD connection at T1282.

Upon receiving the serial number from the printer 10J at T1282, the terminal 100 transmits a DPP migration request to the printer 10J via the Wi-Fi I/F 116 using the WFD connection at T1284. Although not shown, the DPP migration request includes a password. The password may be stored in advance in the terminal 100 in association with the serial number of the printer 10J, or may be input by the user after the process at T1282. In this way, in this case, there is no need to directly execute the DPP migration operation on the printer 10J.

When the printer 10J receives the DPP migration request from the terminal 100 at T1282, it performs authentication of the password included in the DPP migration request. In this case, the password authentication is successful, so the printer 10J executes the processes from T1286 to T1288. Note that if the authentication fails, the printer 10J does not execute the processes from T1286 onwards. The processes at T1286 and T1287 are similar to the processes at T156 and T160 in FIG. 6, except that the public key PKJ3 is used. Furthermore, the process at T1288 is the same as the process at T1231 in FIG. 18, except that the setup information is different (specifically, the public key PKJ3 is used and the DPP automatic migration information "NO" is used). The same is true.

The processing from T1289 to T1292 is the same as the processing from T1230 to T1236 in FIG. 18, except that the setup information is different. Thereafter, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKJ3 is used and the main body of the process is the printer 10J.

At T1254, the terminal 100 causes the display unit 114 to display the notification screen SC7 (see S34 in FIG. 4 and FIG. 16). Specifically, since the means information included in the stored setup information indicates "NFC handover" and the one-time information indicates "YES", the terminal 100 touches the printer 10J again. Identify messages that encourage Next, since the means information included in the stored setup information indicates "NFC handover", the terminal 100 does not specify a message prompting the DPP transition operation. As described above, in this case, the terminal 100 uses the WFD connection established by NFC handover to send the DPP transition request to the printer 10J, so it is not necessary to directly execute the DPP transition operation to the printer 10J. That's because there isn't. The processing at T1296 is similar to the processing at T1276. Thereafter, processing similar to T1277 and T1278 is executed, and a WFD connection is established between the terminal 100 and the printer 10J.

The processing at T1297 is similar to the processing at T1284. Further, the process at T1298 is similar to the process at T156 in FIG. 6, except that the public key PKJ4 is used. Thereafter, processing similar to T1287 to T1292 is executed, and the terminal 100 acquires and stores setup information including the public key PKJ4. Then, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10J and AP6.

(Case K1; Figure 20)
Next, case K1 will be explained with reference to FIG. 20. Case K1 is a case where DPP processing is executed between the terminal 100 and the printer 10K. In particular, case K1 is a case in which the DPP migration information indicates "YES" because the printer 10K does not store CO. As shown in FIG. 2, the public key of printer 10K is not a one-time key. The printer 10K stores the public key PKK in advance from the time the printer 10K is shipped. In case K1, first, processes similar to T100, T102, and T110 in FIG. 5 are executed. The process at T1312 is similar to the process at T1212 in FIG.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to T1224 to T1236 in FIG. 18 is executed, and the terminal 100 receives setup information from the printer 10K using the WFD connection established by NFC handover, and stores the setup information (S12, YES in S14, S20). Next, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKK is used and the main body of the process is the printer 10K.

At T1354, the terminal 100 causes the display unit 114 to display the notification screen SC5 (see S34 in FIG. 4 and FIG. 9). Specifically, since the means information included in the stored setup information indicates "NFC handover" and the one-time information indicates "NO", the terminal 100 sends a message prompting the execution of the DPP re-execution operation. Identify. This is because the public key of the printer 10K is not a one-time key, so there is no need to reacquire the public key of the printer 10K. Next, since the DPP automatic migration information included in the stored setup information indicates "YES", the terminal 100 does not specify a message prompting a DPP migration operation.

The process at T1360 is similar to the process at T160 in FIG. Further, the process at T1364 is similar to the process at T424 in FIG. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10K and AP6.

(Case K2; Figure 20)
Next, case K2 will be explained with reference to FIG. 20. Case K2 is a case where DPP processing is executed between the terminal 100 and the printer 10K. In particular, case K2 is a case in which the DPP migration information indicates "NO" because the printer 10K has already stored the CO. In case K2, first, the same processing as T100 and T102 in FIG. 5 is executed. The processing at T1372 is similar to the processing at T1312 in FIG.

Thereafter, the same processes as T120 and T122 in FIG. 5 are executed, and the notification screen SC1 is displayed (see S10 in FIG. 4 and FIG. 5). Next, processing similar to T1274 to T1292 in FIG. 19 is executed, and the terminal 100 receives setup information from the printer 10K using the WFD connection established by NFC handover, and stores the setup information (S12, YES in S14, S20). Next, the same processes as T130 to T152 in FIG. 5 are executed, except that the public key PKK is used and the main body of the process is the printer 10K.

At T1394, the terminal 100 causes the display unit 114 to display the notification screen SC7 (see S34 in FIG. 4 and FIG. 16). Specifically, since the means information included in the stored setup information indicates "NFC handover" and the DPP automatic transition information indicates "NO", the terminal 100 touches the printer 10K again. Messages that prompt DPP migration operations are specified, and messages that prompt DPP migration operations are not specified. The processing at T1396 is similar to the processing at T1026 in FIG.

Thereafter, processes similar to T1277, T1278, T1284, T1287, and T1292 in FIG. 19 are executed, and the state of the printer 10K is shifted from the DPP non-responsive state to the DPP responsive state. Thereafter, the same processes as the processes T130 to T144 in FIG. 5 and T166 to T172 in FIG. A Wi-Fi connection is established between 10K and AP6.

(Summary of this example; Figure 21)
FIG. 21 shows a summary of this example. FIG. 21 shows a combination of the setup information output means, one-time information, DPP automatic migration information, and notification contents of the re-execution means. For example, the second line of FIG. 21 shows that the setup information can be output by displaying a QR code obtained by encoding the setup information, and for the printer 10A whose public key is a one-time key, the DPP automatic In a situation where the migration information indicates "YES", if a Wi-Fi connection is not established between the printer 10A and the AP 6, a notification screen (SC2, see FIG. 6) containing a message prompting to take a QR code is displayed. (Case A1, see FIGS. 5 and 6). The same applies to other lines.

In particular, in cases A1 and A2, the notification screen includes a message prompting to take a QR code (see notification screen SC2 in Figure 6 and notification screen SC3 in Figure 7), and in cases B1, B2, and C, the notification screen includes a message prompting the user to take a photo of the QR code. The message does not include a message prompting to take a picture, but includes a message prompting a DPP re-execution operation (see notification screens SC5 and SC6 in FIG. 9). Furthermore, in cases A1 and B1, the notification screen does not include a message prompting the user to execute the DPP migration operation (see notification screen SC2 in FIG. 6 and notification screen SC5 in FIG. 9), and in cases A2, B2, and C, The notification screen includes a message prompting the user to execute the DPP migration operation (see notification screen SC3 in FIG. 7 and notification screen SC6 in FIG. 9). In this way, when the setup information output means is QR code display (or pasting), the terminal 100 can display an appropriate notification screen according to the one-time information and DPP transition information.

In addition, in cases D1 to G2, regardless of whether the one-time information indicates "YES" or "NO", the notification screen includes a message prompting the execution of the DPP re-execution operation (see FIGS. 11 to 15). (See notification screens SC5 and SC6 in FIG. 9). In particular, in cases D1, E1, and F1 to G2, the notification screen does not include a message prompting the user to execute the DPP migration operation (notification screen SC2 in FIG. 6, referred to in FIGS. 11 to 15, notification screen SC2 in FIG. 9). In cases D2 and E2, the notification screen includes a message prompting the user to perform the DPP migration operation (see notification screen SC6 in FIG. 9, referred to in FIGS. 11 and 12). In this way, the terminal 100 can display an appropriate notification screen when the setup information output means is BT (that is, BT (ADV_EXT) or BT (GATT)).

Furthermore, in cases H1 and H2, the notification screen includes a message prompting the user to touch the terminal with the printer (see notification screens SC7 and SC8 in FIG. 16), and in cases I1 and I2, the notification screen includes a message prompting the user to touch the terminal with the printer. The message does not include a message prompting the DPP re-execution operation, but includes a message prompting the execution of the DPP re-execution operation (see notification screens SC5 and SC6 in FIG. 9 referred to in FIG. 17). In particular, in cases H1, I1, J1 to K2, the notification screen does not include a message prompting the user to execute the DPP migration operation (notification screen SC7 in FIG. 16, notification screen SC5 in FIG. 9 referred to in FIGS. 17 to 20). and notification screen SC7 in FIG. 16), in cases H2 and I2, the notification screen includes a message prompting the user to execute the DPP migration operation (notification screen SC8 in FIG. 16, notification screen SC6 in FIG. 9 referred to in FIG. 17). reference). In this way, the terminal 100 can display an appropriate notification screen when the setup information output means is NFC (that is, NFC (direct communication) or NFC handover).

(Effects of this example)
According to the above configuration, the printer 10A displays the QR code QRA1 obtained by encoding the public key PKA1 of the printer 10A and the one-time information "YES" on the display unit 14 (T112 in FIG. 5). . The terminal 100 acquires the public key PKA1 of the printer 10A and one-time information "YES" by photographing the QR code QRA1 (T126 in FIG. 5), and executes the DPP process using the public key PKA1. (T130 to T144 in FIG. 5). The printer 10A can be obtained by encoding a public key PKA2 different from the public key PKA1 since the one-time information indicates "YES" when the Wi-Fi connection between the printer 10A and the AP 6 is not established. The QR code QRA2 is displayed on the display unit 14 (T162 in FIG. 6). The terminal 100 acquires the public key PKA2 by photographing the QR code QRA2 (T164 in FIG. 6), and executes the DPP process using the public key PKA2 (T130 to T144 in FIG. 5 referred to in FIG. 6). ). Further, the printer 10B causes the display unit to display the QR code QRB1 obtained by encoding the public key PKB of the printer 10B and the one-time information "NO" (T412 in FIG. 9). The terminal 100 acquires the public key PKB of the printer 10B and the one-time information "NO" by photographing the QR code QRB1 (T126 in FIG. 5, referred to in FIG. 9), and acquires the DPP using the public key PKB. Processing is executed (T130 to T144 in FIG. 5, referred to in FIG. 9). Since the one-time information indicates "NO" when the Wi-Fi connection between the printer 10B and the AP 6 is not established, the terminal 100 re-executes the DPP process using the acquired public key PKB. The same is true when a QR code QRC obtained by encoding the public key PKB of the printer 10C and the one-time information "NO" is pasted on the housing 50 of the printer 10C (the case in FIG. 10). (See C). In this way, when the Wi-Fi connection between the printer 10 (that is, each printer 10A to 10K) and the AP 6 is not established, the terminal 100 automatically generates a new public key depending on whether the public key is a one-time key or not. You can switch whether or not to obtain a public key. Therefore, the terminal 100 can appropriately re-execute the DPP process when a Wi-Fi connection is not established between the printer and the AP 6.

Further, according to the above configuration, the terminal 100 has a plurality of Wi-Fi connections for re-executing the DPP process when a Wi-Fi connection is not established between the first communication device or the second communication device and the external device. A notification screen showing one method determined based on the bootstrapping key acquisition method (for example, see notification screen SC2 in FIG. 6) among the methods (in this example, QR code photography, BT, NFC) ) is displayed. In this way, the user can appropriately re-execute the DPP process according to the notification screen when the Wi-Fi connection is not established.

(correspondence)
The terminal 100, the printer 10 (ie, the printers 10A to 10K), and the AP 6 are examples of a "first communication device," a "second communication device," and an "external device," respectively. The public key PKA1 and the public key PKA2 are examples of a "first bootstrapping key" and a "second bootstrapping key", respectively. QR code QRA1, QR code QRA2, QR code QRB1, and QR code QRC are examples of "first output information,""second output information,""outputinformation," and "code image," respectively. BT communication and NFC communication are examples of "first communication" and "second communication", respectively. A DPP non-response state and a DPP response state are examples of a "non-response state" and a "response state", respectively. DPP automatic migration information is an example of "migration information". The notification screen SC2 is an example of a "method screen." The notification screen SC3 is an example of a "method screen" and a "notification screen." Auth Req, Auth Res, and printer CO are examples of "authentication request,""authenticationresponse," and "first connection information (and connection information)," respectively. The processing from T130 to T144 in FIG. 5 is an example of "DPP processing." The CO stored in the printer 10A in the initial state of FIG. 7 is an example of "second connection information." Selection of "QR code" on the notification screen SC1 and photographing of the QR code are examples of "predetermined operations." The DPP transition operation is an example of a "predetermined instruction."

The processing at T126 and the processing from T130 to T144 in FIG. 5 are examples of processing executed by the "first acquisition section" and "first DPP processing execution section" of the "computer program", respectively. In particular, the processing of T130, the processing of T134, and the processing of T142 are examples of "processing of transmitting an authentication request," "processing of receiving an authentication response," and "processing of executing communication of first connection information," respectively. It is. The processes T130 to T144 in FIG. 5 cited in FIG. 6 and the processes T130 to T144 in FIG. 5 cited in FIG. This is an example of a process executed by the process execution unit. The processing at T254 in FIG. 7 and the processing at T154 in FIG. 6 are executed by the "first display control section (and second display control section)" and "second display control section" of the "computer program", respectively. This is an example of the processing performed.

The processing at T112 and the processing from T130 to T144 in FIG. 5 are examples of processing executed by the "first output control section" and "first DPP processing execution section" of the "second communication device", respectively. be. In particular, the processing of T130, the processing of T134, and the processing of T142 are "processing for receiving an authentication request," "processing for transmitting an authentication response," and "executing communication of the first connection information (or connection information)," respectively. This is an example of "processing to do." The processing from T130 to T144 in FIG. 5 cited in FIG. 6 and the processing from T130 to T144 in FIG. , the "second DPP processing execution unit" and the "third DPP processing execution unit" of the "second communication device". The process at T162 in FIG. 6 is an example of the process executed by the "second output control unit" of the "second communication device". The process at T104 in FIG. 5, the process at T204 in FIG. 7, the process at T156 in FIG. 6, and the process at T256 in FIG. This is an example of processing executed by the "generation unit", the "third generation unit", and the "fourth generation unit".

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

(Modification 1) In the above embodiment, for example, DPP processing was executed between the terminal 100 and the printer 10A in order to establish a Wi-Fi connection between the printer 10A and the AP 6. In a modification, DPP processing may be performed between the terminal 100 and the printer 10A in order to establish a Wi-Fi connection between the terminal 100 and the AP 6. In this modification, the printer 10A may operate as a configurator, the terminal 100 may operate as an enrollee, and the printer 10A may transmit the terminal CO to the terminal 100. In this modification, the terminal CO is an example of "first connection information (and connection information)." In another modification, DPP processing may be performed between the terminal 100 and the printer 10A in order to establish a Wi-Fi connection between the terminal 100 and the printer 10A. In this modification, the terminal 100 or the printer 10A is an example of an "external device." In another modification, the terminal 100 may send a printer CO including the SSID and password of AP6 to the printer 10A instead of sending the printer CO including the printer SC to the printer 10A. . In this modification, the printer CO including the SSID and password of AP6 is an example of "first connection information (and connection information)."

(Modification 2) The terminal 100 may include a message prompting the user to execute the DPP migration operation, regardless of whether the DPP automatic migration information indicates "YES" or "NO". In particular, in this modification, the setup information does not need to include DPP automatic migration information. In this case, each notification screen SC2 and the like may include a message urging the user to execute the DPP migration operation. Generally speaking, the "first display control section" of the "computer program" can be omitted.

(Modification 3) The setup information may not include means information. In this case, each notification screen SC2 etc. does not include a message specified based on the setup information output means of each printer 10 (for example, a message prompting to take a QR code, etc.), but only a message prompting to re-execute the setup. It's okay to stay. In this modification, the "second display control section" of the "computer program" can be omitted. In another modification, the setup information may not include means information, and the terminal 100 itself may determine the means for acquiring the setup information. For example, when setup information is acquired in response to a QR code being photographed (see T126 in FIG. 5), the terminal 100 may specify a "QR code" as the setup information acquisition means. That is, the terminal 100 determines by itself which method (i.e., QR code, BT (ADV_EXT), BT (GATT), NFC (direct communication), and NFC handover) was used when acquiring the setup information, and uses this method. may be memorized.

(Modification 4) The printer 10A may automatically generate a public key when the printer 10A is powered on, regardless of whether or not the CO has been stored. In this modification, the "second generation unit" of the "second communication device" can be omitted. In another modification, the printer 10A generates a public key when a DPP migration operation is accepted from the user after the printer 10A is powered on, regardless of whether the CO has been stored. You may. In this modification, the "first generation unit" of the "second communication device" can be omitted.

(Modification 5) Regardless of whether the printer 10A has stored the CO or not, if a Wi-Fi connection is not established between the printer 10A and the AP 6, the printer 10A may automatically generate a public key. good. In this modification, the "fourth generation unit" of the "second communication device" can be omitted. In another modification, the printer 10A is configured to accept a DPP migration operation from the user after a Wi-Fi connection is not established between the printer 10A and the AP 6, regardless of whether or not the CO has been stored. If accepted, a public key may be generated. In this modification, the "third generation unit" of the "second communication device" can be omitted.

(Variation 6) In this embodiment, an example has been described in which each printer 10 can execute one setup information output means (that is, any one of QR code, BT, and NFC). In a modification, the printer 10 may be configured to be able to execute two or more of the setup information output means described above. Also in this modification, a notification screen (for example, SC2) is displayed based on the setup information acquisition means, so if a Wi-Fi connection is not established, the user can appropriately re-execute the DPP process according to the notification screen. be able to.

(Modification 7) In this embodiment, the terminal 100 simultaneously acquired setup information including four pieces of information: means information, public key, one-time information, and DPP automatic migration information (for example, see T126 in FIG. 5). In a modification, the terminal 100 may acquire these pieces of information at different timings, rather than at the same time. For example, the printer 10A generates and displays four QR codes by encoding each piece of information, and acquires setup information (i.e., four pieces of information) by sequentially photographing these QR codes. good.

(Modification 8) In the above embodiment, each of the processes shown in FIGS. 4 to 20 is realized by software such as the program 36, but at least one of these processes may be realized by hardware such as a logic circuit. may be done.

The technical elements described in this specification or the drawings exhibit technical utility alone or in various combinations, and are not limited to the combinations described in the claims as filed. Further, the techniques illustrated in this specification or the drawings can simultaneously achieve multiple objectives, and achieving one of the objectives has technical utility in itself.

Even if each claim is dependent on only some of the claims in the scope of claims as of the filing of this patent application, each claim can be dependent on only some of the claims. Not limited. To the extent not technically inconsistent, each claim may be dependent on other claims to which it was not dependent as filed. That is, the techniques of each claim can be combined in various ways as follows.
(Item 1)
A computer program for a first communication device, the computer program comprising:
The first communication device includes:
a Wi-Fi interface for performing Wi-Fi communication in accordance with the Wi-Fi standard;
computer and
Equipped with
The computer program causes the computer to run the following parts:
When a predetermined operation is performed, a first bootstrapping key of a second communication device and one-time information indicating whether the first bootstrapping key is a one-time key are acquired. a first acquisition unit that
a first DPP processing execution unit that executes DPP processing according to DPP (abbreviation for Device Provisioning Protocol) of the Wi-Fi standard when the first bootstrapping key and the one-time information are acquired; And,
The DPP processing is
a process of transmitting an authentication request using the first bootstrapping key to the second communication device via the Wi-Fi interface;
a process of receiving an authentication response from the second communication device via the Wi-Fi interface when the authentication request is sent to the second communication device;
A process of communicating first connection information with the second communication device via the Wi-Fi interface when the authentication response is received from the second communication device, the process comprising: 1, the connection information is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface; ,
the first DPP processing execution unit,
the first bootstrapping key in a first case where the Wi-Fi connection is not established and the one-time information indicates that the first bootstrapping key is the one-time key; a second acquisition unit configured to acquire a second bootstrapping key of the second communication device different from the second communication device, wherein the Wi-Fi connection is not established and the one-time information is the second obtaining unit, wherein the second bootstrapping key is not obtained in a second case indicating that the bootstrapping key of is not the one-time key;
In the first case, when the second bootstrapping key is obtained, executing the DPP process in which the second bootstrapping key is used instead of the first bootstrapping key. a second DPP processing execution unit;
In the second case, a third DPP processing execution unit that re-executes the DPP processing using the acquired first bootstrapping key;
A computer program that functions as
(Item 2)
The first acquisition unit further determines whether a user needs to perform a transition operation on the second communication device in order to transition the state of the second communication device from a non-responsive state to a responsive state. Get migration information indicating
The non-response state is a state in which the second communication device is unable to transmit the authentication response,
The response state is a state in which the second communication device can transmit the authentication response,
The computer program further causes the computer to
If the Wi-Fi connection is not established and the migration information indicates that the user needs to perform the migration operation on the second communication device, the user a first display control unit that causes a notification screen to be displayed on a display unit of the first communication device to prompt the user to perform the migration operation, the first display control unit configured to display a notification screen prompting the user to perform the migration operation when the Wi-Fi connection is not established; The computer program according to item 1, wherein the computer program is configured to function as the first display control unit so that the notification screen is not displayed when the second communication device indicates that there is no need to execute the above.
(Item 3)
The computer program further causes the computer to
If the Wi-Fi connection is not established, one of the plurality of methods for causing the first communication device to re-execute the DPP process is determined based on the bootstrapping key acquisition means. The computer program according to item 1 or 2, which functions as a second display control unit that causes a display unit of the first communication device to display a method screen showing the method.
(Item 4)
The acquisition means is one of the following: first communication including photographing a code image, Bluetooth (registered trademark) communication, and second communication including NFC (abbreviation for Near Field Communication) communication. Computer program according to item 3.
(Item 5)
The first acquisition unit further acquires means information indicating the acquisition means,
The second display control unit displays, on the display unit, the method screen showing the one method determined based on the acquisition means indicated by the acquired means information among the plurality of methods. The computer program according to item 3 or 4, which displays the computer program.
(Item 6)
A second communication device,
Outputting first output information obtained using a first bootstrapping key of the second communication device and one-time information indicating that the first bootstrapping key is a one-time key. a first output control section that outputs an output to the section;
When the first bootstrapping key and the one-time information are acquired by the first communication device in response to the first output information being output by the output unit, the Wi-Fi standard A first DPP processing execution unit that executes DPP processing according to DPP (abbreviation of Device Provisioning Protocol),
The DPP processing is
a process of receiving an authentication request using the first bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
A process of communicating first connection information with the first communication device via the Wi-Fi interface when the authentication response is transmitted to the first communication device, the process comprising: 1, the connection information is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface; ,
the first DPP processing execution unit,
when the Wi-Fi connection is not established, using the second bootstrapping key of the second communication device, the second bootstrapping key being different from the first bootstrapping key; a second output control unit that causes the output unit to output second output information obtained by
In response to the second output information being output by the output unit, when the second bootstrapping key is obtained by the first communication device, the first bootstrapping key a second DPP processing execution unit that executes the DPP processing using the second bootstrapping key instead;
A second communication device comprising:
(Item 7)
The second communication device further includes:
a first bootstrapping key that generates the first bootstrapping key when the second communication device is powered on in a state where the second connection information is not stored in the memory of the second communication device; The second connection information is information for establishing a Wi-Fi connection between the second communication device and the external device via the Wi-Fi interface, The first generation unit does not generate the first bootstrapping key when the second communication device is powered on in a state where the second connection information is stored in the memory. The second communication device according to item 6, comprising:
(Item 8)
The second communication device further includes:
In a state where the second connection information is stored in the memory, the first bootstrapping key is activated when a user gives a predetermined instruction after the second communication device is powered on. The second communication device according to item 7, comprising a second generation unit that generates the data.
(Item 9)
The second communication device further includes:
a third generation unit that generates the second bootstrapping key when the Wi-Fi connection is not established in a state where the second connection information is not stored in the memory of the second communication device; The second connection information is information for establishing a Wi-Fi connection between the second communication device and the external device via the Wi-Fi interface; Items 6 to 8, comprising the third generation unit, wherein the second bootstrapping key is not generated if the Wi-Fi connection is not established in a state where connection information is stored in the memory. The second communication device according to any one of the items.
(Item 10)
The second communication device further includes:
Generating the second bootstrapping key when a predetermined instruction is given by a user after the Wi-Fi connection is not established in a state where the second connection information is stored in the memory. The second communication device according to item 9, comprising a fourth generation unit.
(Item 11)
A second communication device,
an output control unit that causes an output unit to output output information obtained using a bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key;
When the bootstrapping key and the one-time information are acquired by the first communication device in response to the output information being output by the output unit, DPP (Device Provisioning Protocol) of the Wi-Fi standard is used. A first DPP processing execution unit that executes DPP processing according to
The DPP processing is
a process of receiving an authentication request using the bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
When the authentication response is sent to the first communication device, a process of communicating connection information with the first communication device via the Wi-Fi interface, wherein the connection information is transmitted to the first communication device. The processing is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface;
the first DPP processing execution unit,
a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key when the Wi-Fi connection is not established;
A second communication device comprising:
(Item 12)
A second communication device,
A casing to which a code image obtained by encoding a bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key is pasted. and,
When the bootstrapping key and the one-time information are acquired by the first communication device in response to the code image being photographed by the first communication device, the Wi-Fi standard DPP ( A first DPP processing execution unit that executes DPP processing according to Device Provisioning Protocol (Device Provisioning Protocol),
The DPP processing is
a process of receiving an authentication request using the bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
When the authentication response is sent to the first communication device, a process of communicating connection information with the first communication device via the Wi-Fi interface, wherein the connection information is transmitted to the first communication device. The processing is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface;
the first DPP processing execution unit,
a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key when the Wi-Fi connection is not established;
A second communication device comprising:

2: Communication system, 6: AP, 10, 10A to 10K: Printer, 12, 112: Operation unit, 14, 114: Display unit, 16, 116: Wi-Fi I/F, 18: Print execution unit, 20, 120 : BTI/F, 22, 122: NFC I/F, 30, 130: Control unit, 32, 132: CPU, 34, 134: Memory, 36: Program, 100: Terminal, 118: Camera, 136: OS program, 138 :application

Claims (12)

A computer program for a first communication device, the computer program comprising:
The first communication device includes:
a Wi-Fi interface for performing Wi-Fi communication in accordance with the Wi-Fi standard;
computer and
Equipped with
The computer program causes the computer to run the following parts:
When a predetermined operation is performed, a first bootstrapping key of a second communication device and one-time information indicating whether the first bootstrapping key is a one-time key are acquired. a first acquisition unit that
a first DPP processing execution unit that executes DPP processing according to DPP (abbreviation for Device Provisioning Protocol) of the Wi-Fi standard when the first bootstrapping key and the one-time information are acquired; And,
The DPP processing is
a process of transmitting an authentication request using the first bootstrapping key to the second communication device via the Wi-Fi interface;
a process of receiving an authentication response from the second communication device via the Wi-Fi interface when the authentication request is sent to the second communication device;
A process of communicating first connection information with the second communication device via the Wi-Fi interface when the authentication response is received from the second communication device, the process comprising: 1, the connection information is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface; ,
the first DPP processing execution unit,
the first bootstrapping key in a first case where the Wi-Fi connection is not established and the one-time information indicates that the first bootstrapping key is the one-time key; a second acquisition unit configured to acquire a second bootstrapping key of the second communication device different from the second communication device, wherein the Wi-Fi connection is not established and the one-time information is the second obtaining unit, wherein the second bootstrapping key is not obtained in a second case indicating that the bootstrapping key of is not the one-time key;
In the first case, when the second bootstrapping key is obtained, executing the DPP process in which the second bootstrapping key is used instead of the first bootstrapping key. a second DPP processing execution unit;
In the second case, a third DPP processing execution unit that re-executes the DPP processing using the acquired first bootstrapping key;
A computer program that functions as The first acquisition unit further determines whether a user needs to perform a transition operation on the second communication device in order to transition the state of the second communication device from a non-responsive state to a responsive state. Get migration information indicating
The non-response state is a state in which the second communication device is unable to transmit the authentication response,
The response state is a state in which the second communication device can transmit the authentication response,
The computer program further causes the computer to
If the Wi-Fi connection is not established and the migration information indicates that the user needs to perform the migration operation on the second communication device, the user a first display control unit that causes a notification screen to be displayed on a display unit of the first communication device to prompt the user to perform the migration operation, the first display control unit configured to display a notification screen prompting the user to perform the migration operation when the Wi-Fi connection is not established; 2. The computer program product according to claim 1, wherein the computer program is configured to function as the first display control section so that the notification screen is not displayed when the second communication device indicates that there is no need to execute the above notification screen. The computer program further causes the computer to
If the Wi-Fi connection is not established, one of the plurality of methods for causing the first communication device to re-execute the DPP process is determined based on the bootstrapping key acquisition means. 2. The computer program according to claim 1, which functions as a second display control section that causes a display section of the first communication device to display a method screen showing the method. The acquisition means is one of the following: first communication including photographing a code image, Bluetooth (registered trademark) communication, and second communication including NFC (abbreviation for Near Field Communication) communication. The computer program according to claim 3. The first acquisition unit further acquires means information indicating the acquisition means,
The second display control unit displays, on the display unit, the method screen showing the one method determined based on the acquisition means indicated by the acquired means information among the plurality of methods. The computer program according to claim 3, which displays the computer program. A second communication device,
Outputting first output information obtained using a first bootstrapping key of the second communication device and one-time information indicating that the first bootstrapping key is a one-time key. a first output control section that outputs an output to the section;
When the first bootstrapping key and the one-time information are acquired by the first communication device in response to the first output information being output by the output unit, the Wi-Fi standard A first DPP processing execution unit that executes DPP processing according to DPP (abbreviation of Device Provisioning Protocol),
The DPP processing is
a process of receiving an authentication request using the first bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
A process of communicating first connection information with the first communication device via the Wi-Fi interface when the authentication response is transmitted to the first communication device, the process comprising: 1, the connection information is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface; ,
the first DPP processing execution unit,
when the Wi-Fi connection is not established, using the second bootstrapping key of the second communication device, the second bootstrapping key being different from the first bootstrapping key; a second output control unit that causes the output unit to output second output information obtained by
In response to the second output information being output by the output unit, when the second bootstrapping key is obtained by the first communication device, the first bootstrapping key a second DPP processing execution unit that executes the DPP processing using the second bootstrapping key instead;
A second communication device comprising: The second communication device further includes:
a first bootstrapping key that generates the first bootstrapping key when the second communication device is powered on in a state where the second connection information is not stored in the memory of the second communication device; The second connection information is information for establishing a Wi-Fi connection between the second communication device and the external device via the Wi-Fi interface, The first generation unit does not generate the first bootstrapping key when the second communication device is powered on in a state where the second connection information is stored in the memory. The second communication device according to claim 6, comprising:. The second communication device further includes:
In a state where the second connection information is stored in the memory, the first bootstrapping key is activated when a user gives a predetermined instruction after the second communication device is powered on. The second communication device according to claim 7, further comprising a second generation unit that generates. The second communication device further includes:
a third generation unit that generates the second bootstrapping key when the Wi-Fi connection is not established in a state where the second connection information is not stored in the memory of the second communication device; The second connection information is information for establishing a Wi-Fi connection between the second communication device and the external device via the Wi-Fi interface; 7. The second bootstrapping key is not generated when the Wi-Fi connection is not established in a state where connection information is stored in the memory, the third generation unit comprising: the second bootstrapping key. a second communication device. The second communication device further includes:
Generating the second bootstrapping key when a predetermined instruction is given by a user after the Wi-Fi connection is not established in a state where the second connection information is stored in the memory. The second communication device according to claim 9, comprising a fourth generation unit. A second communication device,
an output control unit that causes an output unit to output output information obtained using a bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key;
When the bootstrapping key and the one-time information are acquired by the first communication device in response to the output information being output by the output unit, DPP (Device Provisioning Protocol) of the Wi-Fi standard is used. A first DPP processing execution unit that executes DPP processing according to
The DPP processing is
a process of receiving an authentication request using the bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
When the authentication response is sent to the first communication device, a process of communicating connection information with the first communication device via the Wi-Fi interface, wherein the connection information is transmitted to the first communication device. The processing is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface;
the first DPP processing execution unit,
a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key when the Wi-Fi connection is not established;
A second communication device comprising: A second communication device,
A casing to which a code image obtained by encoding a bootstrapping key of the second communication device and one-time information indicating that the bootstrapping key is not a one-time key is pasted. and,
When the bootstrapping key and the one-time information are acquired by the first communication device in response to the code image being photographed by the first communication device, the Wi-Fi standard DPP ( A first DPP processing execution unit that executes DPP processing according to Device Provisioning Protocol (Device Provisioning Protocol),
The DPP processing is
a process of receiving an authentication request using the bootstrapping key from the first communication device via the Wi-Fi interface of the second communication device;
a process of transmitting an authentication response to the first communication device via the Wi-Fi interface when the authentication request is received from the first communication device;
When the authentication response is sent to the first communication device, a process of communicating connection information with the first communication device via the Wi-Fi interface, wherein the connection information is transmitted to the first communication device. The processing is information for establishing a Wi-Fi connection between the first communication device or the second communication device and an external device via the Wi-Fi interface;
the first DPP processing execution unit,
a third DPP processing execution unit that re-executes the DPP processing using the bootstrapping key when the Wi-Fi connection is not established;
A second communication device comprising:

Images