JP2020135071A - Function execution device and computer program for terminal device - Google Patents

Abstract

To provide a technique to prevent target processing using authentication information from being executed when a function demanded by a user is not included in one or more functions executable by a function execution device.SOLUTION: A function execution device transmits, to a terminal device, screen display information to display a function screen via a first wireless interface without executing target processing using specific authentication information, when a first execution instruction is input after the function screen is displayed on the terminal device, establishes a first wireless connection with the terminal device via the first wireless interface, receives an execution request from the terminal device by using the first wireless connection via the first wireless interface without executing the target processing, executes the target processing according to the reception of the execution request from the terminal device, and after the target processing using the specific authentication information is executed, executes communication of first function execution information with the terminal device via the first wireless interface.SELECTED DRAWING: Figure 8

Description

This specification discloses a technique relating to a device capable of performing communication using specific authentication information.

Patent Document 1 discloses a communication device that executes pairing with an information processing device according to a standard of BLE (abbreviation of Bluetooth (registered trademark) Low Energy). The communication device displays a PIN (abbreviation of Personal Identification Number) code for using GATT (abbreviation of Generic Attribute Profile) communication in response to receiving a pairing request from the information processing device. The communication device receives the PIN code from the information processing device when the displayed PIN code is input to the information processing device. As a result, PIN code authentication is executed and GATT communication becomes available. The communication device uses GATT communication to supply the information processing device with a list of services supported by the communication device. The information processing device uses GATT communication to transmit a password to the communication device in order to provide the service of the remote UI included in the list. The information processing terminal displays the remote UI when the access permission response is received from the communication device as a response to the password.

Japanese Unexamined Patent Publication No. 2017-182489 Japanese Unexamined Patent Publication No. 2007-08835 Japanese Unexamined Patent Publication No. 2016-225949 Japanese Unexamined Patent Publication No. 2018-14006 JP-A-2017-59063

"Bluetooth Core Specification ver. 4.2", Bluetooth SIG, 2014 "Bluetooth Core Specification ver. 5.0", Bluetooth SIG, 2016

In the above technique, for example, even if the services supported by the communication device do not include the service desired by the user, the PIN code authentication is executed.

In the present specification, for example, in order to suppress execution of the target process using the authentication information when the function desired by the user is not included in one or more functions that can be executed by the function execution device. Providing technology.

The function executing device disclosed in the present specification does not execute the target process using the first wireless interface and the specific authentication information prepared by one of the function executing device and the terminal device. A transmission unit that transmits screen display information to the terminal device for displaying a function screen indicating one or more functions that can be executed by the function execution device on the terminal device via the first wireless interface. After the function screen is displayed on the terminal device, when the first execution instruction for causing the function executing device to execute the first function is input to the terminal device, the first wireless interface is used. Through the first establishment unit that establishes the first wireless connection with the terminal device and the first wireless connection, the specific authentication information is transmitted via the first wireless interface. A receiving unit that receives an execution request from the terminal device without executing the used target process, and the execution request causes the function execution device to execute the target process using the specific authentication information. The receiving unit, the target processing executing unit that executes the target processing using the specific authentication information in response to receiving the execution request from the terminal device, and the specific After the target process using the authentication information is executed, the communication of the first function execution information for executing the first function is executed with the terminal device via the first wireless interface. The communication execution unit of 1 may be provided.

According to the above configuration, the function executing device transmits the screen display information to the terminal device without executing the target process using the specific authentication information. As a result, the function screen is displayed on the terminal device without executing the target process using the specific authentication information. Then, when the first execution instruction is input to the terminal device after the function screen is displayed on the terminal device, the function execution device receives an execution request from the terminal device by using a specific wireless connection. After that, the target process using the specific authentication information is executed. Then, the function execution device executes the communication of the first function execution information with the terminal device after the target process is executed. That is, when the first execution instruction is not input to the terminal device because the function desired by the user is not included in one or more functions that can be executed by the function execution device, the specific authentication information Target processing using is not executed. Therefore, when the function desired by the user is not included in one or more functions that can be executed by the function execution device, it is possible to suppress the execution of the target process using the authentication information.

Further, the computer program of the terminal device disclosed in the present specification is the terminal device without executing the target process using the specific authentication information prepared by the function executing device and one of the terminal devices. A receiver that receives screen display information for displaying a function screen indicating one or more functions that can be executed by the function executing device on the terminal device from the function executing device via the first wireless interface of the above. When the screen display information is received from the function execution device, a display control unit for displaying the function screen on the display unit of the terminal device, and a display control unit after the function screen is displayed on the display unit. When the first execution instruction for causing the function executing device to execute the function of 1 is input to the terminal device, the first wireless connection with the function executing device is performed via the first wireless interface. An execution request is issued via the first wireless interface by using a supply unit that supplies an instruction for establishing The transmission unit that transmits to the function execution device, and the execution request is a request for causing the function execution device to execute the target process using the specific authentication information.
After the target process using the specific authentication information is executed, the function execution information for executing the first function is communicated with the function execution device via the first wireless interface. It may function as a communication execution unit.

According to the above configuration, the terminal device receives the screen display information from the function execution device without executing the target process using the specific authentication information. As a result, the function screen is displayed on the terminal device without executing the target process using the specific authentication information. Then, when the first execution instruction is input to the terminal device after the function screen is displayed, the terminal device transmits an execution request to the function execution device by using the first wireless connection to identify the terminal device. Let the function execution device execute the target process using the authentication information of. Then, after the target process is executed, the terminal device executes the communication of the first function execution information with the function execution device. That is, when the first execution instruction is not input to the terminal device because the function desired by the user is not included in one or more functions that can be executed by the function execution device, the specific authentication information Target processing using is not executed. Therefore, when the function desired by the user is not included in one or more functions that can be executed by the function execution device, it is possible to suppress the execution of the target process using the authentication information.

A computer program for realizing the above-mentioned function executing device, a computer-readable recording medium for storing the computer program, and a method executed by the above-mentioned function executing device are also new and useful. Further, a computer-readable recording medium for storing a computer program of the terminal device, the terminal device itself, and a method executed by the terminal device are also new and useful.

The configuration of the communication system is shown. The conceptual diagram of the Primary Service group is shown. The data structure of the Primary Service group is shown. The continuation of FIG. 3 is shown. The continuation of FIG. 4 is shown. A sequence diagram of a comparative example is shown. The continuation of FIG. 6 is shown. A sequence diagram of processing common to the first to fifth embodiments is shown. The continuation of FIG. 8 is shown. The sequence diagram of the case where the AP connection button in the function screen is selected in the first and second embodiments or the case where the BLE connection button in the function screen is selected in the fifth embodiment is shown. The continuation of FIG. 10 is shown. The continuation of FIG. 11 is shown. The sequence diagram of the case where the WFD connection button in the function screen is selected in the 1st and 2nd Examples is shown. The continuation of FIG. 13 is shown. A sequence diagram of a case where the error information button in the function screen is selected in the first to fifth embodiments is shown. The sequence diagram of the case where the AP connection button in the function screen is selected in the 3rd and 4th Examples is shown. The continuation of FIG. 16 in the 3rd Example is shown. The continuation of FIG. 16 in the 4th Example is shown.

(First Example)
(Configuration of communication system 2; FIG. 1)
As shown in FIG. 1, the communication system 2 includes a mobile terminal 10 (hereinafter, simply referred to as “terminal 10”), a printer 100, and an AP (abbreviation of Access Point) 200. The terminal 10 participates in the wireless network formed by the AP200 (hereinafter referred to as "AP network"). The AP200 stores an SSID (abbreviation of Service Set Identifier) “ap01” that identifies the AP network and a password “xxx” used in the AP network.

(Configuration of terminal 10)
The terminal 10 is a portable terminal device such as a mobile phone (for example, a smartphone), a PDA, or a tablet PC. The terminal 10 includes a display unit 12, a wireless LAN interface 14, a BT (abbreviation of Bluetooth (registered trademark)) interface 16, and a control unit 30. Each part 12 to 30 is connected to a bus line (reference numeral omitted). In the following, the interface will be simply referred to as "I / F".

The display unit 12 is a display for displaying various information. The display unit 12 also functions as a touch panel (that is, an operation unit) that receives instructions from the user.

The wireless LAN I / F14 is a wireless interface for executing wireless communication according to the Wi-Fi method (hereinafter, referred to as "Wi-Fi communication"). The Wi-Fi method is, for example, the IEEE (abbreviation of The Institute of Electrical and Electronics Engineers, Inc.) 802.11 standard and the equivalent standard (for example, 802.11a, 11b, 11g, 11n, 11ac, etc.). According to the above, it is a wireless communication method for executing wireless communication. The wireless LANI / F14 specifically supports the WFD (abbreviation of Wi-Fi Direct (registered trademark)) method developed by the Wi-Fi Alliance. The WFD method is a wireless communication method described in the standard "Wi-Fi Peer-to-Peer (P2P) Technical Specification Version 1.1" created by Wi-Fi Alliance.

The terminal 10 can operate in any of the WFD system G / O (abbreviation of Group Owner) state, CL (abbreviation of Client) state, and device state. For example, the terminal 10 operates as a WFD type client and is a wireless network formed by an external device (for example, a printer 100) operating as a WFD type G / O (hereinafter referred to as "WFD network"). It is possible to participate as a child station.

The BTI / F16 is an I / F for executing wireless communication according to the BT method. The BT method is, for example, a wireless communication method based on the standard of IEEE802.5.1 and a standard equivalent thereto. More specifically, BTI / F16 supports BLE (short for Bluetooth Low Energy). BLE is a standard realized in the BT system version 4.0 or later. In this embodiment, it is assumed that BTI / F16 supports BLE realized in version 4.2. The BTI / F16 can perform wireless communication according to BLE (hereinafter referred to as "BLE communication"). In the modified example, the BTI / F16 may support BLE realized in a version 4.2 or later (for example, 5.0).

The differences between the Wi-Fi method and the BT method will be described. The communication speed of Wi-Fi communication (for example, the maximum communication speed is 600 Mbps) is faster than the communication speed of BT communication (for example, the maximum communication speed is 24 Mbps). The frequency of the carrier wave in Wi-Fi communication is the 2.4 GHz band or the 5.0 GHz band. The frequency of the carrier wave in BT communication is the 2.4 GHz band. That is, when the 5.0 GHz band is adopted as the carrier frequency in Wi-Fi communication, the carrier frequency in Wi-Fi communication and the carrier frequency in BT communication are different. Further, the maximum distance at which Wi-Fi communication can be performed (for example, about 100 m) is larger than the maximum distance at which BT communication can be performed (for example, about several tens of m).

The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the programs 36 and 38 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, and the like, and is described as an OS (abbreviation of Operating System) program 36 (hereinafter simply referred to as “OS 36”) and a print application 38 (hereinafter simply referred to as “application 38”). ) And memorize. In this embodiment, it is assumed that OS36 is iOS (registered trademark).

The OS 36 is a program for controlling the basic operation of the terminal 10. The application 38 is an application for transmitting print data to the printer 100 by using a wireless connection according to the Wi-Fi method. The application 38 may be installed on the terminal 10 from a server on the Internet provided by the vendor of the printer 100, or may be installed on the terminal 10 from the media shipped with the printer 100, for example.

(Configuration of Printer 100)
The printer 100 is a peripheral device (for example, a peripheral device of the terminal 10) capable of executing a printing function. The printer 100 includes a display unit 112, a wireless LANI / F114, a BTI / F116, and a control unit 130.

The display unit 112 is a display for displaying various information. The display unit 112 also functions as a touch panel (that is, an operation unit) that receives instructions from the user. The wireless LANI / F114 is the same as the wireless LANI / F14 of the terminal 10. That is, the wireless LANI / F114 supports the WFD method. The BTI / F116 is the same as the BTI / F16 of the terminal 10. That is, BTI / F116 supports BLE.

The control unit 130 includes a CPU 132 and a memory 134. The CPU 132 executes various processes according to the program 136 stored in the memory 134. The memory 134 is composed of a volatile memory, a non-volatile memory, and the like, and stores the protocol stack 138, the WFD information 160, and the restart flag 162 in addition to the program 136.

The protocol stack 138 includes a protocol stack according to BLE. The printer 100 operates as a BT system server by using the protocol stack 138, and can execute BLE communication with the terminal 10 operating as a BT system client.

The protocol stack 138 has a hierarchical structure shown in FIG. L2CAP (abbreviation of Logical Link Control and Application Protocol) is a stack for establishing a wireless connection (hereinafter referred to as "L2CAP Link") via BTI / F116. SMP (abbreviation of Security Manager Protocol) and ATT (abbreviation of Attribute Protocol) are upper layers of L2CAP. SMP is a protocol for encrypting information communicated via L2CAP Link. ATT is a protocol for defining an access method between a server and a client in communication via L2CAP Link. GATT (abbreviation of Generic Attribute Profile) is an upper layer of ATT and is a protocol for defining the functions of servers and clients. GAP (abbreviation of Generic Access Profile) is an upper layer of L2CAP, SMP, ATT, and GATT, and is a protocol for defining functions common to each device capable of executing BLE communication. The Primary Service group is an upper layer of GAP and is an application for defining specific operations related to BLE communication. In the following, the Primery Service will be simply referred to as "PS".

The WFD information 160 is information used for establishing a wireless connection (hereinafter, referred to as “WFD connection”) according to the WFD method. The WFD information 160 includes an SSID “p01” that identifies the WFD network formed by the printer 100 that operates as a G / O, and a password “yyy” that is used in the WFD network. The WFD information 160 may be stored in the memory 134 in advance from the shipping stage of the printer 100, or may be generated when the power of the printer 100 is turned on.

The restart flag 162 indicates "ON" indicating that the transmission of the ADV signal is restarted immediately after stopping the transmission of the Advanced signal (hereinafter, simply referred to as "ADV signal") according to the BT method, and the transmission of the ADV signal. Indicates a value of "OFF" indicating that the transmission of the ADV signal is not resumed immediately after the stoppage of. The restart flag 162 is set to "ON" when the power of the printer 100 is turned on.

(PS group concept; Fig. 2)
The concept of the PS group included in the protocol stack 138 will be described with reference to FIG. The table in FIG. 2 conceptually shows the PS group for ease of understanding, and is different from the specific data structure of the PS group. The data structure of the PS group will be described with reference to FIGS. 3 to 5 after the description of FIG. 2 is completed. The PS group is divided into a first type PS defined by the Bluetooth SIG (that is, predetermined by the BT standard) and a second type PS defined by the vendor of the printer 100.

(Type 1 PS)
The first type of PS includes GAP Service 138A. In the following, GAP Service is simply referred to as "GA". GA138A is a PS for transmitting information regarding BTI / F116. The information includes, for example, a device name DN indicating BTI / F116, information indicating a standard supported by BTI / F116, and the like. The GA138A is assigned a UUID "0x1800" that is predetermined by the BT method standard as an identifier that identifies the PS corresponding to the GA. GA138A includes a plurality of Characteristic. Characteristic is information that defines a specific function of PS. The plurality of Characteristics included in GA138A include the Characteristic "Device Name" that defines the transmission of the device name DN. The "Device Name" is assigned a UUID "0x2A00" that is predetermined by the BT standard as an identifier that identifies the Characteristic. In FIG. 2, the description of other Characteristics included in GA138A is omitted.

(Type 2 PS)
The second kind of PS includes Function Service 138B, AP Connection 138C, WFD Connection 138D, BT Control 138E, and Eror Service 138F.

(Function Service 138B)
In the following, Function Service will be simply referred to as "FS". The FS 138B is a PS for transmitting functional information FI indicating a plurality of functions that can be executed by the printer 100. The function information FI includes information indicating a printing function, information indicating a function for establishing a wireless connection (hereinafter referred to as "AP connection") with an AP (for example, AP200), and information indicating a function for establishing a WFD connection. , Information indicating the function of transmitting the error URL, and the like. The FS138B is assigned a UUID "aaa0" defined by the vendor of the printer 100 as an identifier that identifies the PS corresponding to the FS. Also below, the UUID that identifies the second type of PS is determined by the vendor of the printer 100. The UUID "aaa0" has a number of digits larger than the number of digits of the UUID (for example, UUID "0x1800") predetermined by the standard of the BT method, and is described in a simplified manner in the present specification. There is.

FS138B includes a Characteristic "Function Information" that defines the transmission of functional information FI. The "Function Information" is assigned a UUID "aaa1" defined by the vendor of the printer 100 as an identifier for identifying the Characteristic. In the following as well, the UUID that identifies the Characteristic included in the second type PS is determined by the vendor of the printer 100.

(AP Connection 138C)
In the following, AP Connection will be simply referred to as "AC". AC138C is a PS for establishing an AP connection. A UUID "bbb0" is assigned to the AC138C. AC138C includes four Characteristic including "Connection Status", "IP Address", "Connection Information", and "Change Permission".

"Connection Status" is a Characteristic (UUID "bbb1") that defines the transmission of AP status information indicating the status related to the AP connection of the printer 100. The AP state information indicates any of a plurality of states including "File", "Enable", "Busy", and "Error". “Disable” indicates that the printer 100 is set to a state in which the establishment of the AP connection is not permitted. "Enable" indicates that the printer 100 is set to allow the establishment of the AP connection. “Busy” indicates that the process for establishing the AP connection is being executed. "Error" indicates that the process for establishing the AP connection has failed.

"IP Address" is a Characteristic (UUID "bbb2") that defines the transmission of the IP address IA of the printer 100.

The "Connection Information" is a Characteristic (UUID "bbb3") that defines the reception of the SSID and password of the AP (for example, AP200) to which the communication partner (for example, the terminal 10) has established a wireless connection.

“Change Permission” is a Characteristic (UUID “bbb4”) that defines the reception of instructions for changing the value of Attribute Permission, which will be described later. The Change Permission is used in the third and fourth embodiments, and is not used in the first and second embodiments.

(WFD Connection 138D)
In the following, WFD Connection is simply referred to as "WC". WC138D is a PS (UUID "ccc0") for establishing a WFD connection. WC138D includes four Characteristic including "Connection Characteristic", "Connection Information", "Public Key", and "Change Characteristic".

The “Connection Status” is a Characteristic (UUID “ccc1”) that defines the transmission of WFD status information indicating the status of the printer 100 regarding the WFD connection. The WFD state information indicates any of a plurality of states including "Disable", "Enable", "Ready", "Start", and "Error". “Disable” indicates that the printer 100 is set to a state in which the establishment of the WFD connection is not permitted. "Enable" indicates that the printer 100 is set to allow the establishment of a WFD connection. “Ready” indicates that the process of encrypting the WFD information 160 using the public key has been completed. “Start” indicates that the printer 100 has started operating as a G / O. "Error" indicates that the process for establishing a WFD connection has failed.

The "Connection Information" is a Characteristic (UUID "ccc2") that defines the transmission of WFD information encrypted using a public key (hereinafter referred to as "encrypted WFD information").

A "Public Key" is a Characteristic (UUID "ccc3") that defines the reception of a public key.

The “Change Character” is a Characteristic (UUID “ccc4”) that defines the reception of an instruction (for example, an instruction for operating the printer 100 as a G / O) for changing the state of the printer 100 regarding the WFD connection.

(BT Control 138E)
In the following, the BT Control will be simply referred to as "BC". BC138E is a PS (UUID "ddd0") for receiving an instruction to change the state of BTI / F116. BC138E includes two Characteristics including "Paring Control" and "Advertising Control".

The "Pailing Control" is a Characteristic (UUID "ddd1") that defines the reception of instructions for disconnecting an established L2CAP Link.

The "Advertising Control" is a Characteristic (UUID "ddd2") that defines the reception of an instruction to change the restart flag 162 from "ON" to "OFF".

(Error Service 138F)
In the following, Eror Service is simply referred to as "ES". ES138F is a PS (UUID "eeee0") for transmitting an error URL. The error URL is a URL indicating a Web page in which a method for clearing an error state (for example, a paper jam) in which the printer 100 cannot execute the printing function is described. The ES138F includes a Characteristic "Error Information (UUID" eee1 ")" that defines the transmission of an error URL.

(Data structure of PS group; FIGS. 3 to 5)
The concept of the PS group has been described with reference to FIG. Subsequently, a specific data structure of the PS group will be described with reference to FIGS. 3 to 5.

The PS group has a table structure in which Handle, Attribute Type, Attribute Value, and Attribute Permission are associated with each other. Handle is a serial number starting from "0x0001". In FIGS. 3 to 5, some data structures after "0x0002" are omitted. Therefore, Handle after "0x0002" is represented by the symbol "nk (k = 1, 2, 3, ...)" Instead of the actual value. The Attribute Type (hereinafter simply referred to as "AType") is an identifier (that is, UUID) indicating the type of information to be communicated. Attribute Value (hereinafter, simply referred to as "AColor") indicates information to be communicated. Attribute Permission (hereinafter simply referred to as "APer") is an item related to SMP, and more specifically, indicates a condition for permitting reading or writing of information.

Specifically, the APer stores values indicating each of the four items. The first item is an item indicating whether or not to allow reading or writing of information, and one value indicating one of "Readable", "Writeable", and "Readable and writeable" is stored in APer. Will be done. The second item is an item indicating whether or not to request Encryption when reading or writing information, and one value indicating either "Encryption required" or "No encryption required" is set to APer. Be remembered. The third item is an item indicating whether or not Authentication is required when reading or writing information, and one value indicating either "Authentication required" or "No authentication required" is set to APer. Be remembered. The fourth item is an item indicating whether or not Authentication is required when reading or writing information, and one value indicating either "Authorization required" or "No authorization required" is set to APer. Will be remembered. If a value indicating any of "Encryption required", "Authentication required", and "Authorization required" is stored in APer, the information is provided on condition that authentication communication according to SMP is executed. Read or write is allowed. In addition, when the values indicating "No encryption required", "No authentication required", and "No authorization required" are stored in APer, information can be read or written without executing authentication communication according to SMP. Allowed. These are simplified and described in FIGS. 3 to 5. For example, when APer indicates "Readable without authentication", the value indicating "Readable" as the first item and the value indicating "No authentication required" as the third item are the APer. Is actually remembered in. Further, the description of APer in FIGS. 3 to 5 is omitted for the second item and the fourth item. Actually, a value indicating "No encryption required" as the second item and a value indicating "No authorization required" as the fourth item are stored in each APer. In the following, unless otherwise specified, the value indicating "No encryption required" as the second item and the value indicating "No authorization required" as the fourth item are stored in APer. It is assumed that there is. When APer stores each value indicating "Readable without authentication when discoverable", the value indicating "Readable" is used as the first item and "No authentication required" is used as the third item. A value indicating "" and a value indicating "No authorization required" as the fourth item above are stored in the APer, and a condition that the state of the server is the Discoverable state described later (that is, "when"). When "discoverable") is satisfied, a value indicating that the reading of information is permitted in accordance with "No authentication required" and "No authorization required" without executing authentication communication according to SMP is given to the APer. It is remembered. As described above, it should be noted that the description of Aper in the drawings does not completely match the actual items described in the Bluetooth SIG standard, but conceptually indicates the conditions regarding SMP.

(Type 1 PS)
(GAP Service (GA) 138A)
GA138A is a data group corresponding to the range "0x0001" to a predetermined value (value immediately before "n2") of Handle. The AType corresponding to Handle "0x0001" includes a UUID "0x2800" indicating that it is the first data in the data group constituting one PS. The AVale corresponding to the Handle "0x0001" includes a UUID "0x1800" to distinguish the GA138A from other PSs. The APer corresponding to Handle "0x0001" includes each value indicating "Readable without authentication". Each of these values means that the information can be read without performing encryption of the information according to SMP.

The AType corresponding to Handle "0x0002" includes a UUID "0x2803" indicating Characteristic Specification. Characteristic Declaration is data that defines the properties of Characteristic, UUID, and the like. Here, the property includes a plurality of information including "Read" indicating that the Characteristic defines the information to be read, "Write" indicating that the Characteristic defines the information to be written, and the like. Any one of them is shown. The AVALe corresponding to the Handle "0x0002" includes a property indicating "Read", a Handle "n1" corresponding to the Characteristic information, and a UUID "0x2A00" of the Characteristic. The APer corresponding to Handle "0x0002" includes each value indicating "Readable without authentication".

The Type corresponding to the Handle "n1" includes the UUID "0x2A00" of the Characteristic "Dvice Name". AColor corresponding to Handle "n1" includes the device name DN. The APer corresponding to Handle "n1" includes each value indicating "Readable without authentication when discoverable". Each of these values can read information (here, device name DN) without executing encryption of information according to SMP when the state of the BT peripheral (that is, the printer 100) is the Discoverable state. It means that it is possible. In other words, if the peripheral state is not the Discoverable state (that is, the non-Discoverable state), the information can be read on condition that the information is encrypted according to SMP. Means. Here, the Discoverable state is a state in which the peripheral repeatedly executes the transmission of the ADV signal. In other words, the Discoverable state is a state in which the central can detect the presence of the peripheral when the ADV signal is received by the BT type central. Further, the ADV signal transmitted in the Discoverable state includes a predetermined value regarding being in the Discoverable state. Here, the "predetermined value" is, for example, the LE Limited Discoverable Mode flag "1" defined in the BT system standard, or the LE General Discoverable Mode flag "1" defined in the BT system standard. is there. On the other hand, in the non-discoverable state, the peripheral does not execute the transmission of the ADV signal, or the peripheral repeatedly executes the transmission of the ADV signal, and the ADV signal contains the above-mentioned predetermined value. In other words, the ADV signal includes both the LE Limited Discoverable Mode flag "0" and the LE General Discoverable Mode flag "0"). "Readable without authentication when discoverable" is an item defined in the standard of version 4.2 or later. In the following, unless otherwise specified, it is assumed that the ADV signal contains a predetermined value relating to the Discoverable state in the situation where the ADV signal is transmitted.

Since the GA138A has the above data structure, the device name DN in the GA138A is read as follows. When the CPU 132 (that is, the server) receives the Read By Type Request signal with the UUID "0x2803" specified from the client, the client changes to the UUID "0x2803" according to the "Readable without authentication" shown in the APer corresponding to the UUID "0x2803". Allows reading of the corresponding AVale (ie, properties "Read", Handle "n1", and UUID "0x2A00"). As a result, the client can read (that is, receive) this information, and can execute "Read" of the information corresponding to the Handle "n1" and the UUID "0x2A00" based on the information. Can be known. Then, the client transmits a Read By Type Request signal with the UUID "0x2A00" specified to the server. When the server receives the signal from the client, the client reads the AValue (that is, the device name DN) corresponding to the UUID "0x2A00" according to the "Readable without authentication when discoverable" indicated by the APer corresponding to the UUID "0x2A00". Allow. This allows the client to read the device name DN.

For the first type of PS, among the above items such as "Readable without authentication", the item predetermined by SIG is adopted. That is, for example, for the APer corresponding to Handle "n1", only "Readable without authentication when discoverable" can be adopted, and the vendor of the printer 100 cannot adopt other items. On the other hand, with respect to the second type of PS described below, the vendor of the printer 100 can adopt any of the above items.

(Type 2 PS)
(Function Service (FS) 138B)
FS138B is a data group corresponding to the range “n2” to “n4” of Handle. The AType corresponding to Handle "n2" includes a UUID "0x2800" indicating that it is the head data of FS138B. The AVALe corresponding to the Handle "n2" includes a UUID "aaa0" to distinguish the FS138B from other PSs. The APer corresponding to Handle "n2" includes each value indicating "Readable without authentication".

The AType corresponding to Handle "n3" includes a UUID "0x2803" indicating that it is a Characteristic Specification. The AValue corresponding to the Handle "n3" includes the property "Read", the Handle "n4", and the UUID "aaa1". The APer corresponding to Handle "n3" includes each value indicating "Readable without authentication".

The Type corresponding to the Handle "n4" includes the UUID "aaa1" of the Characteristic "Function Information". AColor corresponding to Handle "n4" includes functional information FI. The APer corresponding to Handle "n4" includes each value indicating "Readable without authentication".

(AP Connection (AC) 138C)
As shown in FIG. 4, AC138C is a data group corresponding to the range “n5” to “n13” of Handle. The ATtype corresponding to Handle "n5" includes a UUID "0x2800" indicating that it is the head data of AC138C. The AVALe corresponding to Handle "n5" includes a UUID "bbb0" to distinguish the AC138C from other PS. The APer corresponding to Handle "n5" includes each value indicating "Readable without authentication".

Each ATtype corresponding to Handle "n6" to "n9" includes a UUID "0x2803" indicating that it is a Characteristic Declaration. The AValue corresponding to the Handle "n6" includes the property "Read", the Handle "n10", and the UUID "bbb1". Similarly, each AValue corresponding to Handle "n7" to "n9" includes a property, a Handle, and a UUID. The property corresponding to Handle "n8" and "n9" is not "Read" but "Write". Further, each APer corresponding to Handle "n6" to "n9" includes each value indicating "Readable without authentication".

The Type corresponding to the Handle "n10" includes the UUID "bbb1" of the Characteristic "Connection Characteristic". AColor corresponding to Handle "n10" includes AP status information (for example, "Disable"). The APer corresponding to Handle "n10" includes each value indicating "Readable without authentication".

The Type corresponding to the Handle "n11" includes the UUID "bbb2" of the Characteristic "IP Address". The AVALe corresponding to Handle "n11" includes the IP address IA. The APer corresponding to Handle "n11" includes each value indicating "Readable without authentication".

The Type corresponding to the Handle "n12" includes the UUID "bbb3" of the Characteristic "Connection Information". The SSID and password of the AP (for example, 200) are written from the client to the AVale corresponding to the Handle "n12". Before the information is written, the AColor includes empty information. The APer corresponding to Handle "n12" includes each value indicating "Writeable without authentication". Each of these values means that the information (here, the SSID and password) can be written without performing encryption of the information according to SMP.

The Type corresponding to the Handle "n13" includes the UUID "bbb4" of the Characteristic "Change Permission". A Permission change instruction for changing the value of the Attribute Permission is written in the AColor corresponding to the Handle "n13". The APer corresponding to Handle "n13" includes each value indicating "Writeable without authentication".

Since the AC138C has the above-mentioned data structure, for example, information is written in the AVALe corresponding to the UUID "n12" in the AC138C as follows. When the CPU 132 (that is, the server) receives the Read By Type Request signal for which the UUID "0x2803" is specified from the client, the client causes each UUID "0x2803" according to the "Readable without authentication" indicated in the APer corresponding to each UUID "0x2803". (Ie, the property "Read (or Write)", Handle "n10" to "n13", and UUID "bbbb1" to "bbbb4") corresponding to "" are allowed to be read. As a result, the client can read out such information, and knows that it is possible to execute "Write" of the information corresponding to, for example, Handle "n12" and UUID "bbb3" based on the information. Can be done. Then, the client specifies Handle "n12" and transmits a Write Request signal including information to be written (that is, SSID and password) to the server. When the server receives the signal, it permits the information to be written to the AColor corresponding to the Handle "n12" according to the "Writeable without authentication" indicated by the APer corresponding to the Handle "n12". This allows the client to write the SSID and password.

(WFD Connection (WC) 138D)
As shown in FIG. 5, WC138D is a data group corresponding to the range “n14” to “n22” of Handle. The AType corresponding to Handle "n14" includes a UUID "0x2800" indicating that it is the head data of WC138D. The AVALe corresponding to Handle "n14" includes a UUID "ccc0" to distinguish the WC138D from other PS. The APer corresponding to Handle "n14" includes each value indicating "Readable without authentication".

Each ATtype corresponding to Handle "n15" to "n18" includes a UUID "0x2803" indicating that it is a Characteristic Declaration. The AVALe corresponding to the Handle "n15" includes the property "Read", the Handle "n19", and the UUID "ccc1". Similarly, each AValue corresponding to Handle "n16-" to "n18" includes a property, a Handle, and a UUID. Note that each property corresponding to Handle "n17" and "n18" is not "Read" but "Write". Further, each APer corresponding to Handle "n15" to "n18" includes each value indicating "Readable without authentication".

The Type corresponding to Handle "n19" includes the UUID "ccc1" of the Charactisti "Connection Status". AColor corresponding to Handle "n19" includes WFD state information (eg, "Disable"). The APer corresponding to Handle "n19" includes each value indicating "Readable without authentication".

The ATtype corresponding to the Handle "n20" includes the UUID "ccc2" of the Characteristic "Connection Information". The AVALe corresponding to Handle "n20" may include encrypted WFD information. Here, before the WFD information 160 is encrypted, the AVBlue does not include the encrypted WFD information but includes empty information. Further, the APer corresponding to Handle "n20" includes each value indicating "Readable without authentication".

The AType corresponding to the Handle "n21" includes the UUID "ccc3" of the Characteristic "Public Key". The public key is written in the AColor corresponding to the Handle "n21". In addition, the AType corresponding to the Handle "n22" includes the UUID "ccc4" of the Characteristic "Change Characteristic". Each instruction for changing the state related to the WFD connection (for example, an table instruction for changing the state of the printer 100 from "Discable" to "Enable", and the printer 100 as a G / O are given to the AVale corresponding to the Handle "n22". The Start instruction for operation) is written. Each APer corresponding to each Handle "n21" and "n22" includes a value indicating "Writeable without authentication".

(BT Control (BC) 138E)
BC138E is a data group corresponding to the range “n23” to “n27” of Handle. The AType corresponding to Handle "n23" includes a UUID "0x2800" indicating that it is the head data of BC138E. The AVALe corresponding to the Handle "n23" includes a UUID "ddd0 ..." to distinguish the BC138E from other PSs. The APer corresponding to Handle "n23" includes each value indicating "Readable without authentication".

Each ATtype corresponding to Handle "n24" and "n25" includes a UUID "0x2803" indicating that it is a Characteristic Declaration. The AVALE corresponding to the Handle "n24" includes the property "Write", the Handle "n26", and the UUID "ddd1", and similarly, the AVALE corresponding to the Handle "n25" includes the property, the Handle, and the property. Includes UUID and.

The AType corresponding to the Handle "n26" includes the UUID "ddd1" of the Characteristic "Paring Control". A disconnection instruction for disconnecting the L2CAP Link is written in the AVale corresponding to the Handle "n26". The AType corresponding to the Handle "n27" includes the UUID "ddd2" of the Characteristic "Advertising Control". A restart flag OFF instruction for changing the restart flag 162 from "ON" to "OFF" is written in the AColor corresponding to the Handle "n27". Each APer corresponding to each Handle "n26" and "n27" includes a value indicating "Writeable without authentication".

(Error Service (ES) 138F)
ES138F is a data group corresponding to the range “n28” to “n30” of Handle. The AType corresponding to Handle "n28" includes a UUID "0x2800" indicating that it is the head data of ES138F. The AVale corresponding to the Handle "n28" includes a UUID "eee0" for distinguishing the ES138F from other PSs. The APer corresponding to Handle "n28" includes each value indicating "Readable without authentication".

The AType corresponding to the Handle "n29" includes a UUID "0x2803" indicating that it is a Characteristic Specification. The AVale corresponding to the Handle "n29" includes the property "Read", the Handle "n30", and the UUID "eee1". The APer corresponding to Handle "n29" includes each value indicating "Readable without authentication".

The AType corresponding to the Handle "n30" includes the UUID "eee1" of the Characteristic "Error Information". The AValue corresponding to Handle "n30" may include an error URL. Here, when the printer 100 is not in an error state, the AVBlue does not include the error URL but includes empty information. Further, the APer corresponding to Handle "n30" includes each value indicating "Readable without authentication".

(Comparative example; FIGS. 6 and 7)
Before explaining the process executed by the terminal 10 and the printer 100 of this embodiment, the process executed by the mobile terminal 300 (hereinafter, simply referred to as “terminal 300”) and the printer 500 of the comparative example will be described. The terminal 300 includes an OS 36, but includes an application 338 different from the application 38 for realizing the processing of this embodiment (see FIGS. 8 to 18 described later). The printer 500 includes a program different from the program 136 for realizing the processing of this embodiment, and does not store the restart flag 162. In addition, the PS group of the comparative example contains at least GA138A and FS138B. In the following, from the viewpoint of ease of understanding, the processing executed by the CPU of the terminal 300 according to the OS 36 and the application 338 will be described mainly for the OS 36 and the application 338, respectively. Further, since all the communication of the comparative example is executed via the BTI / F of the terminal 300 and the printer 500, the description of "via the BTI / F" will be omitted below.

In T10, the operation of starting the application 338 is executed by the user on the terminal 300, and as a result, the application 338 is started. In this case, at T12, the app 338 supplies the Scan start command to the OS 36. The Scan start command is a command for starting the transmission of the Scan Request signal.

Further, in T14, the operation of turning on the power of the printer 500 is executed by the user on the printer 500. At T20, the printer 500 starts broadcast transmission of the ADV signal. The signal includes the connection permission parameter "ADV_IND" which is predetermined by the BT system standard. The parameter indicates that it is allowed to establish an L2CAP Link with the device that received the ADV signal. In the modified example, the connection permission parameter may be "ADV_DIRECT_IND".

When the OS 36 acquires the Scan start command from the application 338 (T12) and receives the ADV signal from the printer 500 (T20), the OS 36 transmits the Scan Request signal to the printer 500 at T22. The signal is a signal for requesting information on the device (here, printer 500) that is the source of the ADV signal.

At T24, the OS 36 receives a Scan Response signal from the printer 500 as a response to the Scan Request signal. The signal includes the model name "model0" of the printer 500. When the OS 36 receives the signal, the OS 36 supplies the signal to the application 338.

When the application 338 acquires the Scan Response signal from the OS 36, the application 338 displays the connection confirmation screen on the display unit of the terminal 300 at the T26. The connection confirmation screen is a screen for confirming with the user whether or not to establish a wireless connection (that is, L2CAP Link) according to the BT method with the printer 500. The connection confirmation screen includes a model name "model0" included in the Scan Response signal and a connection button for receiving an instruction to establish the L2CAP Link.

When the application 338 accepts the selection of the connection button in the connection confirmation screen at T28, the application 338 supplies the connection start command to the OS 36 at T30. The connection start command is a command for starting transmission of the CONNECT_IND signal. The signal is a signal for requesting the establishment of L2CAP Link. Of the processes T30 to T80 described later, which are started by the acquisition of the connection start command as a trigger, the processes executed by the OS 36 are automatically executed by the OS 36 and cannot be stopped by the command from the application 338.

When the OS 36 acquires the connection start command from the application 338 in the T30, the OS 36 transmits the CONNECT_IND signal to the printer 500 in the T32. When the signal is transmitted to the printer 500, an L2CAP Link is established between the terminal 300 and the printer 500 at the T34.

The printer 500 stops transmitting the ADV signal at T36 when the L2CAP Link is established at T34. That is, the printer 500 shifts from the Discoverable state to the non-Discoverable state. In this way, the transmission of the ADV signal is stopped in response to the establishment of the L2CAP Link, for example, according to the specifications of the BTI / F116 chip and the like.

In addition, OS36 uses the L2CAP Link established in T34 to execute the processes from T38 to T78, which will be described later. The processing of T38 to T78 is executed according to the specifications of iOS. That is, iOS has a specification that automatically acquires PS group information when L2CAP Link is established. At T38, the OS 36 transmits a Read By Group Type Request signal (hereinafter simply referred to as a “Group_Req signal”) defined by the ATT to the printer 500. The Group_Req signal is a signal for reading information indicating the configuration of the PS group in the protocol stack of the printer 500.

When the printer 500 receives the Group_Req signal from the terminal 300 at T38, the printer 500 receives the UUID of each PS, the first Handle of each PS, and the last Handle of each PS as a response to the signal at T40. Send to. Specifically, the printer 500 acquires the AValue corresponding to the UUID "0x2800" indicating that it is the head data from the PS group. As shown in FIG. 3, the UUID "0x1800" of GA138A, the "aaa0" of FS138B, and the like are acquired as the UUID corresponding to the UUID "0x2800". Further, the printer 500 has a first Handle of each PS (for example, the first Handle "0x0001" of GA138A, a first Handle "n2" of FS138B, etc.) and a last Handle of each PS (for example, the last Handle of GA138A). (Value before n2), the last Handle "n4" of FS138B, etc.) and. Then, the printer 500 transmits each acquired information to the terminal 300. As a result, the terminal 300 can know the configuration of the PS group of the printer 500.

Next, the OS 36 sequentially transmits a plurality of Read By Type Request signals (hereinafter, simply referred to as “Type_Req signals”) corresponding to the plurality of PSs to the printer 500 by using each information received by the T40. To do. The Type_Req signal is a signal for which AType is specified, and is a signal for reading the AColor corresponding to the specified AType. Specifically, the OS 36 executes the following processing.

First, the OS 36 transmits a Type_Req signal to the printer 500 for GA138A, which is a PS corresponding to Handle “0x0001” having the smallest value in T42A. Specifically, in T42A, the OS 36 prints a Type_Req signal including a UUID "0x2803" (that is, Characteristic Classification), a first Handle "0x0001" of GA138A, and a last Handle of GA138A (omitted). Send to.

When the printer 500 receives the Type_Req signal from the terminal 300 in the T42A, the printer 500 selects the Type_Req signal from the data group included in the range of the first Handle "0x0001" included in the Type_Req signal and the Handle indicated by the last Handle. The Handle "0x0002" corresponding to the included UUID "0x2803" is specified. The printer 500 then identifies the VALUE and APer corresponding to the identified Handle "0x0002". Here, the identified APer indicates "Readable without authentication". Therefore, in the T42B, the printer 500 does not perform the encryption of the information according to the SMP, and the specified Handle “0x0002” and the specified AValue (that is, the property “Read”, Handle “n1”, And, UUID "0x2A00") and are transmitted to the terminal 300 as a response to the Type_Req signal.

When the OS 36 receives the Handle "0x0002" and the AColor from the printer 500 in the T42B, the OS 36 transmits the Type_Req signal including the UUID "0x2A00" in the ABlue to the printer 500 in the T42C. The signal further includes the first Handle "0x0001" of GA138A and the last Handle of GA138A.

When the printer 500 receives the Type_Req signal from the terminal 300 in the T42C, the printer 500 selects the Type_Req signal from the data group included in the range of the first Handle "0x0001" included in the signal and the Handle indicated by the last Handle. The Handle "n1" corresponding to the included UUID "0x2A00" is specified. The printer 500 then identifies the VALUE and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". As mentioned above, at this time, the printer 500 is in a non-discoverable state. Therefore, the printer 500 is permitted to read the information on condition that the information is encrypted according to the SMP. At present, a key for executing information encryption according to SMP (Long Term Key, which will be described later in this comparative example) has not been generated. For this reason, the printer 500 cannot execute the encryption of the information according to the SMP, and as a result, the Error Response signal is transmitted to the terminal 300 at the T46.

When the OS36 receives the Error Response signal from the printer 500 at the T46, the OS36 transmits the Pairing Request signal to the printer 500 at the T48. The signal is a signal for starting processing related to SMP.

When the printer 500 receives the Pairing Request signal from the terminal 300 at T48, the printer 500 transmits the Pairing Response signal to the terminal 300 at T50. Then, the printer 500 displays the PIN code "1234" at T52. As a result, the user can know the PIN code "1234".

When the OS 36 receives the Pairing Response signal from the printer 500 at the T50, the OS 36 causes the display unit of the terminal 300 to display a PIN input screen for inputting the PIN code at the T54.

As shown in FIG. 7, in T60, the OS 36 accepts the input of the PIN code "1234" on the PIN input screen. As a result, in the T62, authentication communication according to SMP is executed between the OS 36 and the printer 500. In at least a part of the process of the authentication communication, the encrypted information which is the information encrypted by the input PIN code "1234" is communicated. Then, when the decryption of the encrypted information is successful, the printer 500 transmits a Long Term Key (hereinafter, simply referred to as “Key”) to the terminal 300. As a result, in the processing after T72, which will be described later, the information BLE-communicated between the OS 36 and the printer 500 is encrypted by the Key. In FIG. 7, the thin line arrow and the thick line arrow indicate communication of unencrypted information and communication of information encrypted according to SMP, respectively. The same applies to the following figure.

When the authentication communication of the T62 is completed, the OS36 retransmits the Type_Req signal similar to the T42C of FIG. 6 to the printer 500 at the T72. However, as described above, the information in the signal is encrypted by Key.

When the printer 500 receives the Type_Req signal from the terminal 300 on the T72, the printer 500 decodes the information in the signal by Key, and the range of the first Handle "0x0001" included in the decoded information and the Handle indicated by the last Handle. The Handle "n1" corresponding to the UUID "0x2A00" included in the Type_Req signal is specified from the data group included in the data group. The printer 500 then identifies the VALUE and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". Although the printer 500 is in a non-discoverable state, since the T62 authentication process has already been executed, it is possible to perform information encryption according to SMP. Therefore, the printer 500 is allowed to read the information (that is, the device name DN) contained in the AVBlue. Therefore, the printer 500 encrypts the device name DN by using Key, and transmits the encrypted device name DN to the terminal 300 at T74.

Subsequently, the OS 36 transmits a Type_Req signal to the printer 500 in the T76A for the PS corresponding to the Handle, which is the second smallest after the Handle “0x0001” in the PS group. That is, the Type_Req signal is transmitted to the printer 500 for FS138B (Handle “n2”), which is the next PS of GA138A (Handle “0x0001”). The signal includes a UUID "0x2803", the first Handle "n2" of the FS138B, and the last Handle "n4" of the FS138B. In the T76B, the Handle "n3" corresponding to the UUID "0x2803" and the AValue corresponding to the Handle "n3" (that is, the properties "Read", Handle "n4", and UUID "aaa1") are transmitted to the terminal 300. It is the same as T42B in FIG.

When the OS 36 receives the Handle "n3" and the AColor from the terminal 300 in the T76B, the OS 36 transmits a Type_Req signal including the UUID "aaa1" to the printer 500 in the T76C. The signal includes the first Handle "n2" of FS138B and the last Handle "n4" of FS138B.

When the printer 500 receives the Type_Req signal from the terminal 300 in the T76C, the printer 500 decodes the information in the signal by Key, and is indicated by the first Handle "n2" and the last Handle "n4" included in the decoded information. From the data group included in the range of Handle, the Handle "n4" corresponding to the UUID "aaa1" included in the Type_Req signal is specified. The printer 500 then identifies the VALUE and APer corresponding to the identified Handle "n4". Here, the identified APer indicates "Readable without authentication". Therefore, the printer 500 is permitted to read the information (that is, the function information FI) contained in the AVBlue. Therefore, the printer 500 uses the Key to encrypt the function information FI, and at T78, the encrypted function information FI is transmitted to the terminal 300.

After receiving the function information FI from the printer 500 in the T78, the OS 36 sequentially transmits each Type_Req signal corresponding to each of the remaining PSs in the PS group to the printer 500. The OS36 automatically executes the above-mentioned processing of T38 to T78 and transmission of each Type_Req signal corresponding to each of the remaining PSs, so that the information of the PS group, that is, the characteristic property of each PS, UUID, And you can know the Handle.

When all transmissions of the plurality of Type_Req signals corresponding to the plurality of PSs are completed, the OS 36 supplies a connection completion notification to the application 338 at the T80. The connection completion notification is a response to the connection start command of T30 in FIG.

When the application 338 obtains the connection completion notification from the OS36 in the T80, the application 338 supplies the OS36 with a list request for requesting a first list indicating each UUID of each PS in the T81A. As a result, the application 338 acquires the first list from the OS 36 in the T81B. Next, the app 338 selects the UUID "aaa0" of the FS138B from the first list in the T81C, and supplies the selected UUID "aaa0" to the OS36. As a result, in T81D, the application 338 is a second list including each property of each Characteristic in FS138B from OS36 and each UUID (here, a list containing only one set of properties "Read" and UUID "aaa1"). To get.

When the application 338 acquires the second list from the OS36 in the T81D, the application 338 selects the UUID "aaa1" from the second list in the T82, and has been selected according to the property "Read" corresponding to the UUID "aaa1". Requests the OS 36 to transmit a Type_Req signal including the UUID "aaa1". As a result, the OS 36 transmits a Type_Req signal including the UUID "aaa1", the first Handle "n2" of the FS138B, and the last Handle "n4" to the printer 500.

When the printer 500 receives the Type_Req signal including the UUID "aaa1" from the terminal 300 at the T82, the printer 500 transmits the function information FI to the terminal 300 as a response to the Type_Req signal at the T84, similarly to the T78.

When the OS 36 receives the function information FI from the printer 500 in the T84, the OS 36 supplies the received function information FI to the application 338.

When the application 338 acquires the function information FI from the OS 36 in the T84, the application 338 displays the function screen showing the function of the printer 500 in the T90. The function screen includes the model name "model0" of the printer 500 and character information indicating a printing function among a plurality of functions of the printer 500 indicated by the function information FI. Further, in this case, the functional information FI indicates that the printer 500 can execute the establishment of the AP connection, the establishment of the WFD connection, and the transmission of the error information. Therefore, the function screen includes an AP connection button, a WFD connection button, and an error information button as buttons for executing these functions. The AP connection button is a button for receiving an instruction to establish an AP connection. The WFD connection button is a button for receiving an instruction for establishing a WFD connection. The error information button is a button for receiving an instruction to display an error URL. The function screen also includes a Cancel button. The Candle button is a button for receiving an instruction for canceling the subsequent processing.

In this comparative example, the function desired by the user does not exist among the plurality of functions that the printer 500 can execute (that is, the printing function, the AP connection, and the WFD connection). In this case, the user selects the Cancel button in the function screen at T92. As a result, the display of the function screen ends, and the process of FIG. 7 ends.

According to this comparative example, the authentication communication of the T62 is executed before the function screen is displayed on the terminal 300 at the T90. That is, unless the user inputs the PIN code into the terminal 300 (T60), the function screen is not displayed on the terminal 300. Then, in this comparative example, the function desired by the user is not included in the plurality of functions shown in the function screen. That is, according to this comparative example, the user must input the PIN code even when the function desired by the user is not included in the plurality of functions that can be executed by the printer 500. Therefore, in the present embodiment, when the function desired by the user is not included in the plurality of functions that can be executed by the printer 100, it is suppressed that the authentication communication is executed between the printer 100 and the terminal 10. Realize that. As a result, when the function desired by the user is not included in the plurality of functions that can be executed by the printer 100, the user does not have to execute the work of inputting the PIN code. As a result, the convenience of the user is improved.

(Cancel case; FIGS. 8 and 9)
A case where the Cancel button on the function screen is selected in this embodiment will be described with reference to FIGS. 8 and 9. In the following, from the viewpoint of ease of understanding, the processes executed by the CPU 32 of the terminal 10 according to the OS 36 and the application 38 will be described mainly for the OS 36 and the application 38, respectively. The process executed by the CPU 132 of the printer 100 according to the program 136 will be described mainly for the printer 100. Further, since the communication of this embodiment is executed via each BTI / F of the terminal 10 and the printer 100, unless otherwise specified, it is referred to as "via the BTI / F16 (or 116)" below. The explanation is omitted.

T110 and T112 are the same as T10 and T12 in FIG. 6, respectively. The printer 100 sets the restart flag 162 to "ON" at T116 when the operation of turning on the power of the printer 100 is executed by the user at T114. Then, the printer 100 starts broadcast transmission of the ADV signal including the connection permission parameter "ADV_IND" at T120.

Since the OS 36 receives the ADV signal from the printer 100 (T120), the OS 36 transmits the Scan Request signal to the printer 100 at T122, and receives the Scan Response signal including the model name "model 1" from the printer 100 at T124. Supply the signal to the app 338.

T126 to T132 are the same as T26 to T32 in FIG. 6 except that the connection confirmation screen includes the model name “model1”. The OS 36 transmits a CONNECT_IND signal to the printer 100 at T132, and establishes an L2CAP Link between the terminal 10 and the printer 100 at T134.

When the L2CAP Link is established at T134, the printer 100 stops transmitting the ADV signal at T136. As mentioned above, at this time, the restart flag 162 indicates "ON". Therefore, the printer 100 resumes the transmission of the ADV signal at T137 immediately after stopping the transmission of the ADV signal at T136. That is, the printer 100 shifts to the Discoverable state again immediately after shifting from the Discoverable state to the non-Discoverable state. Here, the ADV signal after resumption does not include the connection permission parameter "ADV_IND" but includes the connection disapproval parameter "ADV_NONCONN_IND". The parameter indicates that it does not allow the establishment of an L2CAP Link with the device that received the ADV signal. The device that receives the ADV signal including the parameter does not transmit the Scan_Request signal, and as a result, the L2CAP Link is not established between the device and the printer 100. According to such a configuration, when the ADV signal after resumption is received by a device different from the terminal 10, it is possible to suppress the establishment of the L2CAP Link between the different device and the printer 100. ..

In addition, OS36 uses the L2CAP Link established in T134 to execute the processes of T138 to T178 described later. T138 to T142C are the same as T38 to T42C in FIG.

When the printer 100 receives the Type_Req signal including the UUID "0x2A00" from the terminal 10 in the T142C, the printer 100 is a group of data included in the range of the first Handle "0x0001" included in the signal and the Handle indicated by the last Handle. From the inside, the Handle "n1" corresponding to the UUID "0x2A00" included in the Type_Req signal is specified. The printer 500 then identifies the VALUE and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". As described above, at present, the printer 100 is in the Discoverable state (T137). Therefore, the printer 100 is allowed to read the information without executing the encryption of the information according to the SMP. As a result, in T144, the printer 100 transmits the device name DN, which is the AValue corresponding to the UUID "0x2A00", to the terminal 10 without executing the encryption of the information according to SMP. In this way, since the printer 100 shifts to the Discoverable state again at T137, when receiving the Type_Req signal at T142C, it does not transmit the Error Response signal to the terminal 10 as in T46 of FIG. 6, that is, PIN. The device name DN can be transmitted to the terminal 10 without asking the terminal 10 to input the code.

When the OS 36 receives the device name DN from the printer 100 at T144, the OS 36 transmits a Type_Req signal corresponding to FS138B to the printer 100 at T176A. T176A to T176C are the same as T76A to T76C in FIG. 7, except that encryption using Key is not executed.

When the printer 100 receives the Type_Req signal from the terminal 10 in the T176C, the printer 100 is selected from the data group included in the range of the Handle indicated by the first Handle "n2" and the last Handle "n4" included in the signal. The Handle "n4" corresponding to the UUID "aaa1" included in the Type_Req signal is specified. Next, the printer 100 identifies the VALUE and APer corresponding to the identified Handle "n4". Here, the identified APer indicates "Readable without authentication". Therefore, the printer 100 is permitted to read the information (that is, the function information FI) contained in the AVBlue. As a result, the printer 100 transmits the function information FI to the terminal 10 at T178 without executing the encryption of the information according to the SMP.

When the OS 36 receives the function information FI from the printer 100 in T178, the OS 36 sequentially transmits each Type_Req signal corresponding to each of the remaining PSs in the PS group to the printer 100, and the property "Read" of each remaining PS from the printer 100. ", Each Property corresponding to" is received. Then, the OS 36 supplies the connection completion notification to the application 38 at T180.

As shown in FIG. 9, when the application 38 acquires the connection completion notification from the OS 36 in T180, it executes the same processing as in T81A to T81D in FIG. 7, and in T182, the Type_Req signal including the UUID "aaa1". Requests transmission from OS36. As a result, the OS 36 transmits a Type_Req signal including the UUID "aaa1", the first Handle "n2" of the FS138B, and the last Handle "n4" to the printer 100.

When the OS36 transmits the Type_Req signal to the printer 100 at T182, the OS36 receives the function information FI from the printer 100 at T184 and supplies the received function information FI to the application 38.

When the application 38 acquires the function information FI from the OS36 in T184, it selects the UUID "ddd0" of BC138E from the first list including each UUID of each PS in T185C, and selects the selected UUID "ddd0". Is supplied to OS36. As a result, in T185D, the application 38 acquires a second list of each UUID of each Characteristic in BC138E from OS36 (that is, a list including two UUIDs "dddd1" and "ddd2").

When the application 38 acquires the second list from the OS 36 in the T185D, the application 38 selects the UUID "ddd1" from the second list in the T186 and requests the OS 36 to transmit the Write Request signal including the disconnection instruction. As a result, the OS 36 transmits a Write Request signal including the Handle “n26” corresponding to the selected UUID “ddd1” and the disconnection instruction to the printer 100.

When the printer 100 receives the Write Request signal from the terminal 10 in the T182, the printer 100 identifies the VALUE and APer corresponding to the Handle "n26" included in the signal. Here, the identified APer indicates "Writeable without authentication". Therefore, the printer 100 allows the information contained in the signal (that is, the disconnection instruction) to be written to the specified VALUE. That is, the printer 100 stores the disconnection instruction in the AVBlue.

When the disconnection instruction is stored, the printer 100 transmits a Write Response signal to the terminal 10 at T188. Further, in T189A, the printer 100 cuts the L2CAP Link established in T134 in FIG. 8 according to the stored cutting instruction.

When the L2CAP Link is disconnected, the printer 100 starts transmitting an ADV signal including the connection permission parameter "ADV_IND" in place of the ADV signal including the connection permission parameter in T189B.

Further, when the terminal 10 receives the Write Response signal from the printer 100 at T188, the terminal 10 displays a function screen indicating the function of the printer 100 at T190. The function screen of the T190 is the same as the function screen of the T90 in FIG. 7, except that the model name is different.

In this case, the function desired by the user does not exist among the plurality of functions that the printer 100 can execute (that is, the printing function, the AP connection, and the WFD connection). In this case, the user selects the Cancel button in the function screen at T192. As a result, the display of the function screen ends, and the process of FIG. 9 ends.

According to this case, the printer 100 resumes transmission of the ADV signal after establishing the L2CAP Link (T137 in FIG. 8). As a result, the state of the printer 100 becomes the Discoverable state. Therefore, when the printer 100 receives the Type_Req signal in the T142C (T142C), the printer 100 transmits the device name DN to the terminal 10 without executing the encryption of the information according to the SMP (T144). That is, unlike the comparative example of FIG. 6, the authentication communication is not executed before the function screen is displayed on the terminal 10. As a result, it is possible to prevent the authentication communication from being executed between the printer 100 and the terminal 10 when the function desired by the user is not included in the plurality of functions that can be executed by the printer 100. That is, when the function desired by the user is not included in the plurality of functions that can be executed by the printer 100, the user does not have to execute the work of inputting the PIN code. As a result, the convenience of the user is improved.

(AP connection case; FIGS. 10 to 12)
A case where the AP connection button on the function screen is selected in this embodiment will be described with reference to FIGS. 10 to 12. In this case, the AP connection function desired by the user exists among the plurality of functions that the printer 100 can execute (that is, the print function, the AP connection, and the WFD connection). In this case, the user selects the AP connection button in the function screen at T200.

When the application 38 receives the selection of the AP connection button in the T200, the application 38 supplies the connection start command to the OS 36 in the T212. As a result, the OS 36 transmits the CONNECT_IND signal to the printer 100 at T232, and establishes an L2CAP Link between the terminal 10 and the printer 100 at T234.

When the L2CAP Link is established at T234, the printer 100 stops transmitting the ADV signal at T236. Then, since the restart flag 162 indicates “ON”, the transmission of the ADV signal is restarted at T237. That is, the printer 100 shifts to the Discoverable state again.

Further, the OS 36 uses the L2CAP Link established in T234 to execute the same communication as T138 to T142B in FIG. 8 (that is, transmission of Group_Req signal and transmission of Type_Req signal including UUID "0x2803"). .. Then, in T242C, the OS 36 transmits a Type_Req signal including the UUID “0x2A00” to the printer 100, similarly to the T142C in FIG.

When the printer 100 receives the Type_Req signal from the terminal 10 in the T242C, the APer indicates "Readable without authentication when discoverable", and the printer 100 is in the Discoverable state, as in the case of the T144 in FIG. , T244, the device name DN is transmitted to the terminal 10.

When the OS 36 receives the device name DN from the printer 100 in T244, it executes the same communication as T176A to T178 in FIG. 8 and transmits each Type_Req signal corresponding to each remaining PS in the PS group to the printer 100. Send in sequence. Then, as in the case of FIG. 8, the OS 36 receives each VALUE corresponding to the property “Read” of the remaining PS from the printer 100 without receiving the Error Response signal, and notifies the connection completion at the T250. Supply to app 38.

When the application 38 acquires the connection completion notification from the OS 36 in the T250, the application 38 acquires the second list indicating each UUID of each Characteristic in the BC138E from the OS 36 in the T252. Then, the application 38 transmits a Write Request signal including the Handle “n27” corresponding to the UUID “ddd2” in the second list and the restart flag OFF instruction to the printer 100 via the OS 36.

When the printer 100 receives the Write Request signal from the terminal 10 in the T252, the APer corresponding to the Handle "n27" indicates "Writeable without authentication", so that the restart flag OFF instruction corresponds to the Handle "n27". Store in the ABlue. Then, the printer 100 transmits the Write Response signal to the terminal 10 at T254.

Further, at T256, the application 38 transmits a Write Request signal including a Handle “n26” and a disconnection instruction to the printer 100 as in T186 of FIG. 9, and at T258, as in T188 of FIG. 9, the printer 100 Receives a Write Response signal from. As a result, the disconnection instruction is stored in the VALUE corresponding to the Handle "n26".

When the restart flag OFF instruction and the disconnection instruction are stored in ABlue, the printer 100 disconnects the L2CAP Link established in T234 according to the stored disconnection instruction in T260A, and sets the connection permission parameter "ADV_IND" in T260B. The transmission of the including ADV signal is started. Further, in T262, the printer 100 changes the restart flag 162 from "ON" to "OFF" according to the stored restart flag OFF instruction. As a result, the transmission of the ADV signal is not restarted in the subsequent processing.

As shown in FIG. 11, when the application 38 receives the Write Response signal from the terminal 10 at T258, it supplies a connection start command to OS 36 at T312. T322 to T336 are the same as T132 to T134 in FIG. Here, since the restart flag 162 is changed to "OFF" at T262 in FIG. 10, the printer 100 does not restart the transmission of the ADV signal. That is, the printer 100 is in a non-discoverable state.

Further, the OS 36 uses the L2CAP Link established in T234 to execute the same communication as T138 to T142B in FIG. Then, the OS 36 transmits a Type_Req signal including the UUID "0x2A00" to the printer 100 at the T342C, similarly to the T142C of FIG.

Key is not generated at the time when the Type_Req signal is received from the terminal 10 by the T342C. Therefore, the printer 100 transmits an Error_Response signal to the terminal 10 at T346 due to the fact that the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state.

When the OS 36 receives the Error Response signal from the printer 100 at the T346, the OS 36 transmits the Pairing Request signal to the printer 100 at the T348, and receives the Pairing Response signal from the printer 100 at the T350. As a result, the printer 100 displays the PIN code "1234" at T352, and the terminal 10 displays the PIN input screen on the display unit 12 of the terminal 10 at T354.

When the OS36 receives the input of the PIN code "1234" on the PIN input screen in the T360, the OS36 executes the authentication communication according to the SMP between the OS36 and the printer 100 in the T362. In the authentication communication, the encryption information encrypted by the input PIN code "1234" is successfully decrypted, and the Key is transmitted from the printer 100 to the terminal 10. As a result, in the processing after T372, which will be described later, the information communicated between the OS 36 and the printer 100 according to the BT method is encrypted by Key.

When the authentication communication of T362 is completed, the OS 36 retransmits the Type_Req signal similar to that of T342C to the printer 500 at T372. However, as described above, the information in the Type_Req signal is encrypted by Key.

When the Type_Req signal is received from the terminal 10 at T372, the Key is generated and the information can be encrypted according to the SMP. Therefore, the printer 100 uses Key to encrypt the device name DN at T374 because the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state. The encrypted device name DN is transmitted to the terminal 300.

OS36 executes the same communication as T176A to T178 in FIG. 8 except that when the device name DN is received from the printer 100 in T374, encryption by Key is executed, and the rest of the PS group. Each Type_Req signal corresponding to each PS of is sequentially transmitted to the printer 100. As a result, the OS 36 receives each AValue corresponding to the property "Read" of each of the remaining PSs from the printer 100, and supplies a connection completion notification to the application 38 at the T380.

As shown in FIG. 12, when the application 38 acquires the connection completion notification from the OS 36 in the T380, the application 38 acquires the second list indicating each UUID of each Characteristic in the AC138C from the OS 36 in the T402. Then, the application 38 transmits a Type_Req signal including the UUID “bbb1” in the second list, the first Handle “n5” of the AC138C, and the last Handle “n13” in the second list to the printer 100 via the OS36.

In this case, the AP status information of the printer 100 is set to "Enable" at the time when the Type_Req signal is transmitted to the printer 100 by T402. Therefore, when the application 38 transmits the Type_Req signal to the printer 100 in the T402, the application 38 receives the AP state information "Enable" corresponding to the UUID "bbb1" from the printer 100 via the OS36 in the T404.

When the application 38 acquires the AP status information "Enable" from the OS 36 in T404, the application 38 displays the SSID screen on the display unit 12 in T406. The SSID screen includes a list of SSIDs that identify the AP network of the AP200 to which the terminal 10 is currently participating, and an input field for entering a password. The list includes the AP200 SSID "ap01".

In T408, the application 38 accepts an instruction to select the SSID "ap01" from the list in the SSID screen, and also accepts to enter the password "xxx" of the AP200 in the input field in the SSID screen. As a result, the application 38 selects the UUID "bbb3" from the acquired second list, and via OS36, the Handle "n12" and the SSID "ap01" corresponding to the selected UUID "bbb3" are displayed. A Write Request signal including the password "xxx" is transmitted to the printer 100. Here, the information in the Write Request signal (that is, Handle "n12", SSID "ap01", and password "xxx") is encrypted by Key.

When the printer 100 receives the Write Request signal from the terminal 10 in the T410, the printer 100 decodes the information in the signal and acquires the SSID "ap01" and the password "xxx". Then, the printer 100 stores the SSID "ap01" and the password "xxx" in the AVale corresponding to the Handle "n12". Next, at T412, the printer 100 transmits a Write Response signal to the terminal 10, and at T414, an AP connection process for establishing an AP connection is performed using the stored SSID "ap01" and password "xxx". Start and change the AP status information from "Enable" to "Busy".

When the application 38 receives the Write Response signal from the printer 100 via the OS36 in the T412, the application 38 transmits the Type_Req signal including the UUID "bbb1" to the printer 100 via the OS36 in the T416. In T416, the app 38 transmits a Type_Req signal containing the UUID "bbb1" to the printer 100 before the AP connection process is completed. As a result, in T418, the application 38 receives the AP status information "Busy" in the AVale corresponding to the UUID "bbb1" from the printer 100 via the OS36.

Since the application 38 acquires the "Busy", it can know that the AP connection process has not been completed, and in the T422, the Type_Req signal including the UUID "bbb1" is transmitted to the printer 100 again via the OS36. Here, the AP connection process is completed at T420, and the AP connection is established between the printer 100 and the AP200. In FIG. 12, the broken line arrow indicates Wi-Fi communication (that is, communication via wireless LANI / F114) using the AP network. When the AP connection is established, the printer 100 changes the AP status information from "Busy" to "Enable". Then, at T422, the app 38 transmits a Type_Req signal containing the UUID "bbb1" to the printer 100. As a result, in the T424, the application 38 receives the AP state information "Enable" in the AVale corresponding to the UUID "bbb1" from the printer 100 via the OS36.

When the application 38 receives the AP status information "Enable" from the printer 100 via the OS36 at the T424, the UUID "bbb2" of the "IP Address" of the AC138C and the first of the AC138C via the OS36 at the T426. A Type_Req signal including the Handle "n5" of the above and the last Handle "n13" is transmitted to the printer 100. As a result, the application 38 receives the IP address IA in the AVale corresponding to the UUID "bbb2" from the printer 100 via the OS 36 in the T428.

When the application 38 acquires the IP address IA from the OS 36 in T428, the application 38 requests the OS 36 to transmit a confirmation signal destined for the IP address IA in T430. As a result, the OS 36 transmits a confirmation signal via the wireless LANI / F14 using the AP network of the AP200. As described above, an AP connection has been established between the printer 100 and the AP 200. Therefore, the confirmation signal is received by the printer 100 via the AP 200.

When the printer 100 receives the confirmation signal from the AP200 via the wireless LANI / F114 at the T430, the printer 100 transmits the response signal to the confirmation signal to the terminal 10 via the wireless LANI / F114 and the AP200 at the T432.

When the application 38 receives the response signal from the printer 100 via the OS 36 in the T432, the application 38 determines that the communication with the printer 100 can be executed. T434-T438B executed after T432 is similar to T256-T260B of FIG. 10 except that the information in the Write Request signal is encrypted by Key.

The printer 100 changes the restart flag 162 from "OFF" to "ON" at T440 when the L2CAP Link is disconnected at T438A.

Further, when the application 38 receives the Write Response signal from the printer 100 via the OS36 in the T436, the print screen is displayed on the display unit 12 in the T450. Then, the application 38 accepts a print operation from the user on the print screen. The print operation includes an operation of selecting an image to be printed and an operation of accepting input of print settings (paper size, number of colors, etc.).

In T452, the application 38 prints print data including image information corresponding to the selected image and setting information indicating the input print setting via the OS36, the wireless LANI / F14, and the AP200 to the printer 100. Send to. As a result, in T454, the printer 100 prints the image corresponding to the image information received from the terminal 10 according to the print setting indicated by the setting information received from the terminal 10.

According to the configuration of this case, the printer 100 changes the restart flag 162 from "ON" to "OFF" when the AP connection button in the function screen is selected (T200 in FIG. 10) (T262). As a result, the printer 100 does not resume the transmission of the ADV signal after stopping the transmission of the ADV signal in response to the establishment of the L2CAP Link. Then, the printer 100 executes the authentication communication because the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state (T326 in FIG. 11). As a result, the terminal 10 can encrypt the SSID "ap01" and the password "xxx" of the AP200 by Key and transmit them to the printer 100 (T410). Therefore, it is possible to prevent the SSID "ap01" and the password "xxx" from being acquired by a third party.

(WFD connection case; FIGS. 13 and 14)
A case where the WFD connection button on the function screen is selected in this embodiment will be described with reference to FIGS. 13 and 14. In this case, among the plurality of functions that the printer 100 can execute (that is, the printing function, the AP connection, and the WFD connection), the WFD connection function desired by the user exists. In this case, the user selects the WFD connection button in the function screen at T200.

When the application 38 accepts the selection of the WFD connection button in the T500, the application 38 supplies the connection start command to the OS36 in the T512. T532 to T537 is the same as T232 to T237 in FIG. 10 (that is, establishment of 2CAP Link, resumption of transmission of ADV signal). Then, the OS 36 executes the same communication as T138 to T142B in FIG. 8 and T242C and T244 in FIG. 10 (that is, sequential transmission of each Type_Req signal corresponding to the PS group). That is, since the printer 100 is in the Discoverable state due to the resumption of the transmission of the ADV signal, the Error Response signal is not received and the authentication communication according to the SMP is not executed.

When the application 38 acquires the connection completion notification from the OS 36 to the connection start command of the T 512 in the T550, the application 38 acquires the second list indicating each UUID of each Characteristic in the WC138D from the OS 36 in the T552. Then, the application 38 transmits a Write Request signal including the Handle “n22” corresponding to the UUID “ccc4” in the second list and the Enable instruction to the printer 100 via the OS 36.

When the printer 100 receives the Write Request signal from the terminal 10 in the T552, the APer corresponding to the Handle "n22" indicates "Writeable without authentication", so that the Enable instruction is given to the AValue corresponding to the Handle "n22". Remember in. Then, the printer 100 transmits the Write Response signal to the terminal 10 at T554.

Further, in T556, the application 38 transmits a Write Request signal including the Handle “n21” corresponding to the UUID “ccc3” in the acquired second list and the public key to the printer 100 via the OS36. The public key may be generated in advance by the application 38 when the application 38 is started, or may be generated by the application 38 when the WFD connection button is selected.

When the printer 100 receives the Write Request signal from the terminal 10 in the T556, the APer corresponding to the Handle "n21" indicates "Writeable without authentication", so that the public key is the AValue corresponding to the Handle "n21". Remember in. T558 is similar to T554.

T560 and T562 are the same as T256 and T258 in FIG. As a result, the disconnection instruction is stored in the Character corresponding to the Handle "n26".

When the Enable instruction, the public key, and the disconnection instruction are stored in ABlue, the printer 100 disconnects the L2CAP Link established in T534 according to the stored disconnection instruction in T564A, and in T564B, the connection permission parameter " The transmission of the ADV signal including "ADV_IND" is started. Further, in T566, the printer 100 changes the state of the printer 100 from "Device" to "Enable" according to the stored Enable instruction. As a result, the WFD status information is changed from "Discable" to "Enable". In addition, the printer 100 encrypts the WFD information 160 by using the stored public key in T568. When the encryption of the WFD information 160 is completed, the printer 100 changes the state of the printer 100 from "Enable" to "Ready".

As shown in FIG. 14, when the application 38 receives the Write Response signal from the terminal 10 at the T562, the application 38 supplies a connection start command to the OS 36 at the T570. T572-T577 is the same as T532-T537 in FIG. Then, the OS 36 executes the same communication as T138 to T142B in FIG. 8 and T242C and T244 in FIG. That is, as in FIG. 13, the authentication communication according to SMP is not executed.

When the application 38 acquires the connection completion notification from OS36 to the connection start command of T570 in T580, the application 38 acquires a second list indicating each UUID of each Characteristic in WC138D from OS36 in T582. Then, the application 38 transmits a Type_Req signal including the UUID "ccc1" in the second list, the first Handle "n14" of the WC138D, and the last Handle "n22" to the printer 100 via the OS36.

In this case, the WFD status information of the printer 100 is set to "Ready" at the time when the Type_Req signal is transmitted to the printer 100 at T582. Therefore, when the application 38 transmits the Type_Req signal to the printer 100 via the OS36 in T582, the application 38 receives the WFD state information "Ready" corresponding to the UUID "ccc1" from the printer 100 via the OS36 in T584. To do.

When the application 38 acquires the WFD state information "Ready" from the OS36 in T584, the UUID "ccc2" in the acquired second list and the first Handle "n14" of the WC138D are displayed in T586 via the OS36. A Type_Req signal including the last Handle "n22" is transmitted to the printer 100. As a result, the application 38 receives the encrypted WFD information from the printer 100 via the OS 36 in the T588.

In the T590, the app 38 uses the public key to decrypt the received encrypted WFD information. As a result, the application 38 acquires the WFD information 160.

In T592, the app 38 transmits a Write Request signal including the Handle "n22" corresponding to the UUID "ccc4" in the acquired second list and the Start instruction to the printer 100 via the OS 36. As a result, the Start instruction is stored in the ALPHA corresponding to the Handle "n22", and the Write Response signal is transmitted to the terminal 10 at T594.

At T596, the printer 100 starts the operation as the G / O state according to the stored Start instruction. As a result, the state of the printer 100 is changed from "Ready" to "Start".

Further, in T598, the application 38 supplies the WFD information 160 acquired in T590 to the OS36, and requests the OS36 to establish a WFD connection. As a result, the OS 36 operates as a WFD client in the T600 and uses the WFD information 160 to establish a WFD connection with the printer 100.

Further, when the printer 100 establishes a WFD connection with the terminal 10 at the T600, the printer 100 changes the state of the printer 100 from "Start" to "Enable" at the T602.

Further, when the WFD information 160 is supplied to the OS 36 in T598, the application 38 transmits a Type_Req signal including the UUID “ccc1” to the printer 100 via the OS 36 in T604, similarly to the T582. In this case, the app 38 transmits a Type_Req signal containing the UUID "ccc1" to the printer 100 after the establishment of the WFD connection is completed. As a result, in the T606, the application 38 receives the WFD state information "Enable" in the AVale corresponding to the UUID "ccc1" from the printer 100 via the OS36.

When the application 38 receives the WFD status information "Enable" from the printer 100 in the T606, it determines that the establishment of the WFD connection is completed. T608 to T612B executed after T606 are the same as T560 to T564B in FIG.

T620 to T622 are the same as T450 to T454 in FIG. 12, except that the print data is directly transmitted from the terminal 10 to the printer 100 using the WFD connection.

According to the configuration of this case, the printer 100 transmits the public key to the printer 100 (T556) when the WFD connection button in the function screen is selected (T500 in FIG. 13). As a result, the printer 100 encrypts the WFD information 160 (T568). Then, the printer 100 transmits the encrypted WFD information to the terminal 10 (T588 in FIG. 14). Therefore, it is possible to prevent the WFD information 160 from being acquired by a third party.

Further, according to the configuration of this case, the printer 100 restarts the transmission of the ADV signal after establishing the L2CAP Link (T537 in FIG. 13). Due to the fact that the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the Discoverable state, the public key is transmitted to the printer 100 without executing the authentication communication according to the SMP (T556). ). Therefore, when the encryption by the public key should be executed, it is possible to suppress the execution of the encryption according to the SMP Key.

(In the case of error information; Fig. 15)
A case where the error information button on the function screen is selected in this embodiment will be described with reference to FIG. In this case, the user selects an error information button in the function screen to confirm whether or not the printer 100 is in an error state.

When the application 38 receives the selection of the error information button in T630, the application 38 supplies the connection start command to the OS 36 in T632. T642 to T647 are the same as T232 to T237 in FIG. Then, the OS 36 executes the same communication as T138 to T142B in FIG. 8 and T242C and T244 in FIG. That is, as in FIG. 10, the authentication communication according to SMP is not executed.

When the application 38 acquires the connection completion notification for the connection start command from OS36 to T632 in T660, the application 38 acquires a second list indicating each UUID of each Characteristic in ES138F from OS36 in T662. Then, the application 38 transmits a Type_Req signal including the UUID "eee1" in the second list, the first Handle "n28" of the ES138F, and the last Handle "n30" to the printer 100 via the OS36.

In this case, the state of the printer 100 is an error state (for example, a paper jam) at the time when the Type_Req signal is transmitted to the printer 100 at T662. Therefore, when the application 38 transmits the Type_Req signal to the printer 100 in T662, the application 38 receives the error URL corresponding to the UUID "eee1" from the printer 100 via the OS 36 in T664.

T666 to T670B executed after T664 are similar to T256 to T260B in FIG. That is, the L2CAP Link established at T644 is cleaved.

When the application 38 acquires the Write Request signal from the OS 36 in T668, the application 38 displays the error URL on the display unit 12 in T672. As a result, the user can select the displayed error URL and see the Web page in which the method for clearing the error state (for example, a paper jam) is described.

Further, according to the configuration of this case, when the error information button in the function screen is selected (T630), the printer 100 restarts the transmission of the ADV signal after establishing the L2CAP Link (T647). Since the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the Discoverable state, the authentication communication according to the SMP is not executed and the error URL is transmitted to the terminal 10 (T664). .. An error URL that is less confidential than the SSID "ap01" and the password "xxx" of the first embodiment can be transmitted to the terminal 10 without executing the authentication communication according to the SMP.

(Correspondence)
The printer 100, the terminal 10, the BTI / F116, and the wireless LANI / F114 are examples of the "function execution device", the "terminal device", the "first wireless interface", and the "second wireless interface", respectively. The function of establishing an AP connection or the function of establishing a WFD connection is an example of the "first function". The function screen of T190 in FIG. 9, the instruction to select the AP connection button or the WFD connection button in the function screen, and the function information FI are the "function screen", the "first execution instruction", and the "screen display information", respectively. This is an example. Print data is an example of "relationship data". The connection disapproval parameter "ADV_NONCONN_IND" is an example of "disapproval information". The connection start instruction is an example of an "instruction". The function to send the error URL, the instruction to select the error information button in the function screen, and the Type_Req signal of T662 in FIG. 15 are the "second function", "second execution instruction", and "second function", respectively. This is an example of "execution information". The L2CAPlink of T644 in FIG. 15 is an example of the "fifth wireless connection (and specific wireless connection)".

The correspondence between FIGS. 10 to 12 (in the case of AP connection) is as follows. The PIN code and the encrypted information are examples of "specific authentication information (and the first (or second) code)" and "related information", respectively. The printer 100 and the terminal 10 are examples of "one device" and "the other device", respectively. AP200 is an example of an "external device". The L2CAP Link of T234 in FIG. 10 and the L2CAP Link of T334 in FIG. 11 are examples of "first wireless connection" and "second wireless connection", respectively. The state in which the restart flag is "ON" and the state in which the restart flag is "OFF" are examples of the "first state" and the "second state", respectively. The flag OFF instruction of T252 in FIG. 10 is an example of an “execution request (and setting change request)”. The Type_Req signal is an example of a "specific Read request". The SSID "ap01" and password "xxx" of T410 in FIG. 12 are examples of "first function execution information".

The correspondence between FIGS. 13 and 14 (in the case of WFD connection) is as follows. The public key and PIN code are examples of "specific authentication information" and "specific code", respectively. The terminal 10 and the printer 100 are examples of "one device" and "the other device", respectively. The terminal 10 is an example of an “external device”. The L2CAP Link of T534 in FIG. 13 and the L2CAPLink of T574 in FIG. 14 are examples of "first wireless connection" and "third wireless connection", respectively. The encrypted WFD information of T588 in FIG. 14 is an example of the "first function execution information". The Write Request signal including the public key of T556 in FIG. 13 is an example of the “execution request”.

In the case of AP connection, T234 in FIG. 10, T252 in FIG. 10, T362 in FIG. 11, and T410 in FIG. 12 are "first establishment unit", "reception unit", "target processing execution unit", and "target processing execution unit", respectively. This is an example of processing realized by the "first communication execution unit". In the case of WFD connection, T534 in FIG. 13, T556 in FIG. 13, T568 in FIG. 13, and T588 in FIG. 14 are "first establishment unit", "reception unit", "target processing execution unit", and "target processing execution unit", respectively. This is an example of processing realized by the "first communication execution unit". T184 in FIG. 9 and T190 in FIG. 9 are examples of processing realized by the “reception unit” and the “display control unit”, respectively. In the case of AP connection, T212 in FIG. 10 and T410 in FIG. 12 are examples of processes realized by the "supply unit" and the "communication execution unit", respectively. In the case of WFD connection, T512 in FIG. 13 and T588 in FIG. 14 are examples of processes realized by the "supply unit" and the "communication execution unit", respectively.

(Second Example)
(For WFD connection; FIGS. 13 and 14)
The second embodiment is a modification of the first embodiment. The second embodiment is the same as that of the first embodiment except that a part of the processing in the case of WFD connection is different. In this embodiment, the application 38 and the printer 100 do not execute the processes of T560 to T564B in FIG. 13 and the processes of T570 to T580 in FIG. That is, the printer 100 encrypts the WFD information 160 without disconnecting the L2CAP Link established in T534, while maintaining the establishment of the Link (T568). Then, the printer 100 uses the L2CAP Link of T534 to transmit the encrypted WFD information to the terminal 10 (T588).

In this embodiment, it is assumed that the processing capacity of the CPU 132 of the printer 100 is relatively high. When the processing capacity of the CPU 132 is relatively high, the CPU 132 can encrypt the WFD information 160 while the establishment of the L2CAP Link is maintained. For example, when the processing capacity of the CPU 132 is relatively low, the CPU 132 cannot encrypt the WFD information 160 while the establishment of the L2CAP Link is maintained. In such a case, it is effective to adopt a configuration in which the WFD information 160 is encrypted after the L2CAP Link is disconnected (see T564A in FIG. 13) as in the first embodiment. On the other hand, in this embodiment, in consideration of the relatively high processing capacity of the CPU 132, the process of disconnecting the L2CAP Link and establishing the L2CAP Link again (that is, the process of T560 to T580 in FIG. 13). Can be omitted to prevent unnecessary processing from being executed.

(Third Example)
(In the case of AP connection; FIGS. 16 and 17)
The third embodiment is the same as the first embodiment except that a part of the processing in the case of AP connection is different.

T700 to T720 are the same as T200 to T250 in FIG. 10 (that is, establishment of 2CAP Link, resumption of ADV signal transmission, that is, sequential transmission of each Type_Req signal corresponding to the PS group). That is, since the printer 100 is in the Discoverable state due to the resumption of the transmission of the ADV signal, the Error Response signal is not received and the authentication communication according to the SMP is not executed.

When the application 38 acquires the connection completion notification from the OS36 to the connection start command of the T712 in the T720, the application 38 acquires the second list indicating each UUID of each Characteristic in the AP138C from the OS36 in the T722. Then, the application 38 transmits a Write Request signal including the Handle “n13” corresponding to the UUID “bbb4” in the second list and the Permission change instruction to the printer 100 via the OS 36. The Permission change instruction changes each value indicating "Readable without authentication" in AP138C to each value indicating "Readable with authentication" and changes each value indicating "Writeable without authentication" in AP138C to "Writeable with authentication". It is an instruction to change to each value indicating. Specifically, the instruction is an instruction for changing the value indicating "No authentication required" to the value indicating "Authentication required". In the modified example, the value indicating "No encryption required" may be changed to the value indicating "Encryption required", and the value indicating "No authorization required" may be changed to the value indicating "Authorization required" according to the instruction. May be changed to. Here, "Readable with authentication" means that the information can be read on condition that the information is encrypted according to SMP. Further, "Writeable with authentication" means that the information can be written on condition that the information is encrypted according to SMP. In the modified example, not only all the data in the AP138C but also, for example, "Readable without authentication" in at least one data (for example, the data corresponding to Handle "n10") in each data in the AP138C. Only each value indicating "Readable with authentication" may be changed to each value indicating "Readable with authentication".

When the printer 100 receives the Write Request signal from the terminal 10 in the T722, the APer corresponding to the Handle "n13" indicates "Writeable without authentication", so that the Permission change instruction corresponds to the Handle "n13". Store in ABlue. Then, the printer 100 transmits the Write Response signal to the terminal 10 at T724.

T726 and T728 are the same as T256 and T258 in FIG. As a result, the disconnection instruction is stored in the Character corresponding to the Handle "n26".

When the Parameter change instruction and the disconnection instruction are stored in the VALUE, the printer 100 disconnects the L2CAP Link established in response to the connection start instruction of the T712 according to the stored disconnection instruction in the T730A, and permits the connection in the T730B. The transmission of the ADV signal including the parameter "ADV_IND" is started. Further, in T732, the printer 100 changes each value indicating "Readable without authentication" in the APer corresponding to Handle "n11" and "n12" to each value indicating "Readable with authentication" according to the stored Permission change instruction. At the same time, each value indicating "Writeable without authentication" in the APer corresponding to Handle "n13" and "n14" is changed to each value indicating "Writeable with authentication".

As shown in FIG. 17, when the application 38 receives the Write Response signal from the terminal 10 at the T728, the application 38 supplies a connection start command to the OS 36 at the T742. As a result, the same processing as in T332 to T336 of FIG. 11 (that is, establishment of 2CAP Link and stop of transmission of ADV signal) is executed.

Since the restart flag 162 indicates "ON", the printer 100 restarts the transmission of the ADV signal at T747. That is, the printer 100 shifts to the Discoverable state again.

Further, the OS 36 uses the L2CAP Link established in response to the connection start command of the T712 to perform the same communication as the T138 to T178 of FIG. 8 (that is, the transmission of the Group_Req signal and the Type_Req signal including the UUID "0x2803". (Transmission of Type_Req signal corresponding to GA138A, Transmission of Type_Req signal corresponding to FS138B) is executed.

The application 38 receives the device name DN from the printer 100 because the APer of the GA138A indicates "Readable without authentication when discoverable" and the printer 100 is in the Discoverable state. Further, the application 38 receives the function information FI from the printer 100 because the APer of the FS138B indicates "Readable without authentication".

When the OS 36 receives the function information FI from the printer 100, the OS 36 transmits a Type_Req signal to the printer 100 for AC138C, which is a PS corresponding to the Handle “n5” having the next smallest value after the Handle “n1” in the T756A. The signal includes a UUID "0x2803", the first Handle "n5" of AC138C, and the last Handle "n13" of AC138C.

When the printer 100 receives the Type_Req signal from the terminal 10 in the T756A, the printer 100 is selected from the data group included in the range of the first Handle "n5" and the last Handle "n13" included in the Type_Req signal. The Handles "n6" to "n9" corresponding to the UUID "0x2803" included in the Type_Req signal are specified. The printer 100 has the specified Handles "n6" to "n9" in T756B because the APer corresponding to each of the specified Handles "n6" to "n9" indicates "Readable without authentication". , AColor (property "Read", Handle "n6", and UUID "bbb1") to AVALe (property "Write", Handle "n9", and corresponding to each identified Handle "n6" to "n9", and UUID "bbb4") is transmitted to the terminal 10.

When the OS 36 receives each Handle and each ABlue from the printer 500 in the T756B, the OS 36 sends a Type_Req signal including the UUID "bbb1" corresponding to the Handle "n10" having the smallest value among the AColors to the printer 100 in the T756C. Send. The signal further includes the first Handle "n5" of AC138C and the last Handle "n13" of AC138C.

When the printer 500 receives the Type_Req signal from the terminal 10 in the T756C, the printer 500 is selected from the data group included in the range of the Handle indicated by the first Handle "n5" and the last Handle "n13" included in the signal. The Handle "n10" corresponding to the UUID "bbb1" included in the Type_Req signal is specified. Here, the APer corresponding to the specified Handle "n10" indicates "Readable with authentication". At this time, no Key has been generated to perform encryption of information according to SMP. For this reason, the printer 100 cannot execute the encryption of the information according to the SMP, and as a result, the Error Response signal is transmitted to the terminal 10 at the T758.

T768 to T782 are the same as T348 to T362 in FIG. As a result, in the processing after T790, which will be described later, the information communicated between the OS 36 and the printer 100 according to the BT method is encrypted by Key.

When the authentication communication of T782 is completed, the OS 36 retransmits the Type_Req signal similar to that of the T756C to the printer 100 at the T790. However, as described above, the information in the Type_Req signal is encrypted by Key.

When the Type_Req signal is received from the terminal 10 at the T790, the Key is generated and the information can be encrypted according to the SMP. Therefore, the printer 100 encrypts the AP state information (here, "Enable") by using the Key in T792 due to the APer indicating "Readable without authentication", and the encrypted AP state. The information is transmitted to the terminal 10. T794 is the same as T380 in FIG.

When the connection completion notification is obtained from the OS 36 in T794, the same processing as in T402 to T454 in FIG. 12 is executed. As a result, the AP connection is established and printing is executed.

According to the configuration of this case, the printer 100 changes the APer of AC138C from "Readable without authentication" to "Readable with authentication" when the AP connection button in the function screen is selected (T700 in FIG. 16). (T732). As a result, the printer 100 executes the authentication communication because the APer of the AC138C indicates "Readable with authentication" (T782 in FIG. 17). As a result, the terminal 10 can encrypt the SSID "ap01" and the password "xxx" of the AP200 by Key and transmit them to the printer 100 as in the first embodiment. Therefore, it is possible to prevent the SSID "ap01" and the password "xxx" from being acquired by a third party.

(Correspondence)
The states in which the restart flag is "ON" and the APer indicates "Readable without authentication" and the restart flag is "ON" and the APer indicates "Readable with authentication" are the "first state" and the "second state", respectively. This is an example. "Readable without authentication" and "Readable with authentication" are examples of "first setting information" and "second setting information", respectively. The Permission change instruction of T722 in FIG. 16 is an example of an “execution request (setting change request)”. The L2CAP Link of T234 of FIG. 10 cited in FIG. 16 and the L2CAP Link of T334 of FIG. 11 cited in FIG. 17 are examples of a “first wireless connection” and a “second wireless connection”, respectively. T782 in FIG. 17 is an example of the processing realized by the “target processing execution unit”. T742 in FIG. 17 is an example of processing realized by the “supply unit”.

(Fourth Example)
(For AP connection; FIGS. 16 and 18)
The fourth embodiment is a modification of the third embodiment. The fourth embodiment is the same as the third embodiment except that a part of the processing in the case of AP connection is different.

As shown in FIG. 16, in this embodiment, the application 38 and the printer 100 do not execute the processes of T726 to T739B of FIG. That is, the printer 100 does not disconnect the L2CAP Link established in response to the connection start command of the T712, and the APer "Readable with authentication (or Writeable with authentication)" of the AC138C is maintained in a state where the establishment of the Link is maintained. (T732).

Upon receiving the Write Response signal at T728, the app 38 executes the processing of T800 as shown in FIG. The T800 is the same as the T402 in FIG. 12, except that encryption using Key is not executed.

When the printer 100 receives the Type_Req signal from the terminal 10 in the T800, the printer 100 is selected from the data group included in the range of the Handle indicated by the first Handle "n5" and the last Handle "n13" included in the signal. The Handle "n10" corresponding to the UUID "bbb1" included in the Type_Req signal is specified. Here, the APer corresponding to the specified Handle "n10" indicates "Readable with authentication". At this time, no Key has been generated to perform encryption of information according to SMP. For this reason, the printer 100 cannot execute the encryption of the information according to the SMP, and as a result, the Error Response signal is transmitted to the terminal 10 at the T802.

T806 to T882 are the same as T768 to T782 in FIG. When the authentication communication of the T882 is completed, the OS 36 retransmits the Type_Req signal similar to that of the T800 to the printer 100 at the T890. However, as described above, the information in the Type_Req signal is encrypted by Key. As a result, the OS 36 receives the AP status information (here, "Enable") encrypted by the Key from the printer 100 in the T892, and supplies the received information to the application 38.

When the encrypted AP status information is acquired from the OS 36 in T892, the same processing as in T406 to T454 in FIG. 12 is executed. As a result, the AP connection is established and printing is executed.

In this embodiment, it is assumed that the processing capacity of the CPU 132 of the printer 100 is relatively high. When the processing capacity of the CPU 132 is relatively high, the CPU 132 can change the value in the APer while the establishment of the L2CAP Link is maintained. For example, when the processing capacity of the CPU 132 is relatively low, the CPU 132 cannot change the value in the APer while the establishment of the L2CAP Link is maintained. In such a case, it is effective to adopt a configuration in which the value in APer is changed after disconnecting the L2CAP Link as in the third embodiment. On the other hand, in this embodiment, considering that the processing capacity of the CPU 132 is relatively high, the process of disconnecting the L2CAP Link and establishing the L2CAP Link again is omitted, and unnecessary processing is suppressed. can do.

(Correspondence)
The L2CAP Link of T234 of FIG. 10 cited in FIG. 16 is an example of the “first wireless connection”. T882 in FIG. 18 is an example of the processing realized by the “target processing execution”. T712 in FIG. 16 is an example of the processing realized by the “supply unit”.

(Fifth Example)
The fifth embodiment is the same as the first embodiment except that printing using BLE communication can be performed. As shown in FIGS. 9 and 10, in this embodiment, the function screen includes a BLE connection button. The BLE connection button is a button that executes encryption by the BLE Key and receives an instruction to transmit print data to the printer 100. Although not shown, the PS group of this embodiment includes PSs (hereinafter, referred to as “PPS”) for receiving print data from the terminal 10 in addition to the PS138A to 138F. The PPS includes a Characteristic that defines the reception (ie, write) of print data.

(In the case of printing; FIGS. 10 and 11)
In this case, among the plurality of functions that the printer 100 can execute (that is, printing function, AP connection, WFD connection), there is a printing function desired by the user. In this case, the user selects the BLE connection button in the function screen at T200.

In this case, the app 38 accepts the selection of the BLE connection button at T200. As a result, the processes of T212 to T262 and the processes of T312 to T380 of FIG. 11 are executed as in the first embodiment.

When the application 38 receives the connection completion notification from the OS 36 in T380, the application 38 displays the print screen on the display unit 12 in T390. Then, the application 38 accepts a print operation from the user on the print screen.

In T390, the app 38 acquires a second list in the PPS from the OS 36, and sends a Write Request signal including the Handle corresponding to the UUID in the second list and print data to the printer 100 via the OS 36. Send. Here, the print data in the signal is encrypted by Key.

When the printer 100 receives the Write Request signal from the terminal 10 at T392, the printer 100 decodes the information in the Write Request signal at T394 to acquire print data. Then, the printer 100 prints the image corresponding to the image information in the print data according to the print setting in the print data.

According to this case, the terminal 10 can encrypt the print data by Key and transmit it to the printer 100 (T392). Therefore, it is possible to prevent the information in the print data from being acquired by a third party.

(Correspondence)
The print function, the instruction to select the BLE connection button in the function screen, and the print data of T392 are examples of the "first function", the "first execution instruction", and the "first function execution information", respectively. ..

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

(Modification 1) The "function execution device" does not have to be the printer 100, and may be, for example, a scanner, a fax device, or a multifunctional device. For example, when the "function execution device" is a scanner, the scanner receives a scan request from the terminal 10 at T392 in FIG. 11 when the BLE connection button in the function screen is selected at T200 in FIG. You may. Then, in T394, the scanner may execute a scan according to the scan setting in the scan request to generate scan data, encrypt the generated scan data with Key, and transmit the scan data to the terminal 10. In this modification, the function of transmitting scan data and the scan data are examples of "first function" and "first function execution information", respectively.

(Modification 2) The "terminal device" does not have to be the terminal 10, and may be, for example, a stationary terminal device such as a desktop PC.

(Modification 3) The "first wireless interface" does not have to be a BTI / F, and wireless communication according to a communication method other than the BT method (for example, Zigbee (registered trademark) method, Wi-Fi method) is performed. It may be an I / F to perform. For example, when the "first wireless interface" is an I / F for executing wireless communication according to the Wi-Fi method, the PIN code according to the WPS (abbreviation of Wi-Fi Protected Setup) method is ". This is an example of "specific authentication information".

(Modification 4) In each of the above embodiments, the terminal 10 receives the function information FI from the printer 100 (T184 in FIG. 9) and displays a function screen including the character information indicated by the function information FI (T190). .. Instead of this, the terminal 10 receives specific information (for example, a model name) from the printer 100, and uses the received specific information to select the printer 100 from among a plurality of functional information stored in the terminal 10. The function information FI corresponding to may be specified. Then, the terminal 10 may display a function screen including the character information indicated by the specified function information FI. In this modification, the specific information is an example of "screen display information".

(Modification 5) In the first embodiment described above, the printer 100 displays the PIN code "1234" (T352 in FIG. 11), and the terminal 10 accepts the input of the PIN code "1234" (T354). Instead, the printer 100 displays a code image (for example, a barcode, a QR code (registered trademark)) in which the PIN code “1234” is coded, and the terminal 10 decodes the code image and PINs. You may get the code "1234". Further, the terminal 10 may acquire the PIN code "1234" from the IC tag of the printer 100 by using NFC (abbreviation of Near field communication) communication or the like.

(Modification 6) In the above first embodiment, the printer 100 prepares the PIN code “1234” (T352 in FIG. 11). Instead of this, the terminal 10 may prepare the PIN code "1234" and the PIN code "1234" may be input to the printer 100. Generally speaking, the "specific authentication information" and the "first code" may be prepared by one of the function executing device and the terminal device. Further, for example, when the terminal 10 prepares the PIN code "1234", the printer 100 transmits a Pairing Request signal to the terminal 10 before executing the authentication communication according to the SMP, and the Terminal 10 sends the Pairing Response signal. To receive. Then, the printer 100 executes the authentication communication according to the SMP in response to receiving the Pairing Response signal. In this modification, the Pairing Response signal is an example of an "execution request".

(Modification 7) In the above first embodiment, the printer 100 operates as a G / O, and the terminal 10 prepares a public key (T556 in FIG. 13). Instead, the terminal 10 may operate as a G / O and the printer 100 may prepare a public key. Then, the terminal 10 may encrypt the WFD information stored in the terminal 10 by using the public key received from the printer 100. Generally speaking, the "specific authentication information" and the "public key" may be prepared by one of the function executing device and the terminal device.

(Modification 8) The "specific Read request" does not have to be a Type_Req signal, and may be another signal defined by the ATT (for example, a Read Request signal, a Read Blob Request signal, a Read Multiple Request signal). Good.

(Modification 9) In each of the above embodiments, the application 38 transmits a Write Request signal to the printer 100 at T186 or the like in FIG. Alternatively, the app 38 may transmit other signals defined by the ATT (eg, Write Command signal, Signed Write Command signal) to the printer 100.

(Modification 10) In the above first embodiment, when the error information button in the function screen is selected (T630 in FIG. 15), the printer 100 does not perform information encryption according to SMP. , The error URL is transmitted to the terminal 10 (T664). Instead, for example, a print button is included in the function screen, and the printer 100 does not perform information encryption according to SMP when the print button in the function screen is selected. Print data may be received from the terminal 10. In this modification, the print function and the print data are examples of the "second function" and the "second function execution information".

(Modification 11) In the above first embodiment, the terminal 10 displays an error URL (T672 in FIG. 15). Instead of this, the terminal 10 may display a message indicating an error state. In this modification, the message is an example of "error information". Further, the terminal 10 receives specific information (for example, a number indicating the type of error) from the printer 100, and uses the received specific information to make a printer out of a plurality of error URLs stored in the terminal 10. The error URL corresponding to the current error state of 100 may be specified. Then, the terminal 10 may display the specified error URL. In this modification, the specific information is an example of "error display information".

(Modification 12) In the above-mentioned fourth embodiment, the printer 100 receives the Permission change instruction from the terminal 10 (T722 in FIG. 16) and changes the value in the APer (T732). Instead, the printer 100 may receive a stop instruction for stopping the transmission of the ADV signal from the terminal 10 and stop the transmission of the ADV signal according to the received stop instruction. Then, the printer 100 may receive the Type_Req signal including the UUID "0x2A00" from the terminal 10 instead of the T800 in FIG. As a result, the authentication communication may be executed because the APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state. In this modification, the stop instruction, the Discoverable state, and the non-Discoverable state are examples of the "setting change request", the "first state", and the "second state", respectively.

(Modification 13) In the first embodiment described above, the OS 36 transmits a Type_Req signal to a PS of the first type (for example, T142A in FIG. 8) and a Type_Req signal to a PS of the second type (for example, T176A in FIG. 8). ) Is executed. Instead, the OS 36 may only transmit the Type_Req signal to the Type 1 PS and may not execute the Type_Req signal to the Type 2 PS.

(Modification 14) The processes of T450 to T454 in FIG. 12 may not be executed. In this modification, it is not necessary to execute the communication of "relationship data".

(Modification 15) In the third and fourth embodiments described above, the printer 100 sets each value indicating "Readable (or Writeable) without authentication" in APer in AP138C to "Readable (or Writeable) with authentication". Change to each value shown. Instead, the printer 100 changes all the values indicating "Readable (or Writeable) without authentication" in the APer in the second type PS to the values indicating "Readable (or Writeable) with authentication". You may.

(Modification 16) OS36 may be, for example, Android (registered trademark). In this case, T138, T142A, T142C, T176A, T176C in FIG. 8, T242C in FIG. 10, T342C, T372 in FIG. 11, T652C in FIG. 15, T756A, T756C, T790 in FIG. 17 and the like are not executed. Therefore, for example, in the above-mentioned fourth embodiment, the process of T137 (the same applies to T137 to T178 of FIG. 8 cited in FIG. 16) may not be executed. That is, since the OS 36 does not automatically acquire the PS group information in response to the acquisition of the connection start command, the transmission of the ADV signal does not have to be restarted. In this modification, by indicating "Readable without authentication" by the APer of FS138B, for example, even if the Type_Req signal is received at T812 in FIG. 9, the Error Response signal is not transmitted and authentication is performed before the function screen is displayed. Communication is not executed. Then, authentication communication is executed due to the change of APer of AC138C to "Readable with authentication" by T732 of FIG. 16 (T802 to T880 of FIG. 18). In this modification, the APer of FS138B indicates "Readable without authentication" and the APer of AC138C indicates "Readable with authentication", which are examples of "first state" and "second state", respectively. is there. Further, as a further modification, the APer corresponding to Handle "n1" of FS138B is invariant with "Readable without authentication", and the APer corresponding to Handle "n10" of AC138C is invariant with "Readable with authentication". May be good. Then, the processes of T722, T724, and T732 of FIG. 16 do not have to be executed. In this modification, the "setting change request" can be omitted.

(Modification 17) In T137 of FIG. 8, the printer 100 transmits an ADV signal including the connection disallowance parameter “ADV_NONCONN_IND”. Instead, the printer 100 may transmit an ADV signal including the connection permission parameter "ADV_IND". In this modification, "disapproval information" can be omitted.

(Modification 18) In the first and second embodiments described above, the OS 36 is iOS, and after the WFD connection button is selected, the transmission of the ADV signal is restarted (T537 in FIG. 13 or FIG. 14). T572), authentication communication is not executed. Instead, when the OS 36 is, for example, Android (registered trademark), the OS 36 does not automatically acquire the PS group information in response to the acquisition of the connection start command, so that the transmission of the ADV signal is restarted (that is, that is). The process of T537 of FIG. 13 or T572 of FIG. 14) is not executed. In this case, the authentication communication is not executed because the APer of the WC138C indicates "Readable (or Writeable) without authentication". In this modification, "without executing the communication using a specific code" is realized by APer indicating "Readable (or Writeable) without authentication".

(Modification 19) In each of the above embodiments, the printer 100 and the terminal 10 can execute both the establishment of the AP connection and the establishment of the WFD connection. Instead, the printer 100 and the terminal 10 may be capable of establishing either an AP connection or a WFD connection.

(Modification 20) The process of FIG. 15 does not have to be executed. In this modification, the "fourth establishment unit" and the "second communication execution unit" can be omitted.

(Modification 21) In the above first embodiment, the printer 100 changes the restart flag 162 from “ON” to “OFF” in order to execute the authentication communication (T262 in FIG. 10), and transmits the ADV signal. Does not resume transmission of the ADV signal after stopping (T336 in FIG. 11). Instead, even if the printer 100 keeps the restart flag 162 "ON", stops the transmission of the ADV signal, and then starts transmitting the ADV signal that does not include a predetermined value related to the Discoverable state. Good. Even in this case, the state of the printer 100 becomes a non-discoverable state, and as a result, the authentication communication is executed. In this modification, the state in which the ADV signal that does not include the above-mentioned predetermined value is transmitted is an example of the “second state”.

(Modification 22) In each of the above embodiments, the printer 100 establishes an L2CAP Link (T134 in FIG. 8), and uses the established L2CAP Link to transmit the function information FI to the terminal 10 (T184). .. Instead, the printer 100 may transmit an ADV signal including the function information FI to the terminal 10. In this case, when the connection button in the connection confirmation screen is selected without executing the processes of T130 to T180 in FIG. 8, the processes after T182 are executed, and the function information FI in the ADV signal is used. , The function screen may be displayed. In this modification, receiving the ADV signal including the function information FI is an example of the process realized by the "transmitter that transmits the screen display information to the terminal device without executing the target process", and the ADV. The functional information FI in the signal is an example of "screen display information".

(Modification 23) In each of the above embodiments, the CPU 132 of the printer 100 executes the program 136 (that is, software), and the CPU 32 of the terminal 10 executes the programs 36 and 38, respectively. Processing is realized. Instead, any of the processes may be realized by hardware such as a logic circuit.

2: Communication system, 10: Mobile terminal, 12: Display unit, 14: Wireless LAN I / F, 16: BTI / F, 30: Control unit, 32: CPU, 34: Memory, 36: OS program, 38: Print application , 100: Printer, 112: Display, 114: Wireless LAN I / F, 116: BTI / F, 130: Control, 132: CPU, 134: Memory, 136: Program, 138: Protocol stack, 138A: GA: GA, 138B : FS, 138C: AC, 138D: WD, 138E: BC, 138F: ES, 160: WFD information, 162: Resume flag, 200: AP, 300: Mobile terminal, 338: App, 500: Printer, DN: Device name , FI: Function information, IA: IP address

Claims (24)

It is a function execution device
The first wireless interface and
The function execution device can be executed via the first wireless interface without executing the target process using the specific authentication information prepared by one of the function execution device and the terminal device. A transmitter that transmits screen display information to the terminal device for displaying a function screen indicating one or more functions on the terminal device, and a transmission unit.
After the function screen is displayed on the terminal device, when the first execution instruction for causing the function executing device to execute the first function is input to the terminal device, the first wireless interface is used. Through the first establishment unit for establishing the first wireless connection with the terminal device,
A receiving unit that receives an execution request from the terminal device via the first wireless interface via the first wireless connection without executing the target process using the specific authentication information. Therefore, the execution request is a request for causing the function executing device to execute the target process using the specific authentication information.
A target process execution unit that executes the target process using the specific authentication information in response to receiving the execution request from the terminal device.
After the target process using the specific authentication information is executed, communication of the first function execution information for executing the first function is performed with the terminal device via the first wireless interface. The first communication execution unit to be executed and
A function execution device. The function executing device according to claim 1, wherein the first wireless interface is an interface for executing wireless communication according to a Bluetooth (registered trademark) method. The function executing device further
It has a second wireless interface that is different from the first wireless interface.
The first function is a function of establishing a wireless connection with an external device via the second wireless interface.
The function execution device according to claim 1 or 2, wherein the first function execution information includes information for establishing the wireless connection with the external device via the second wireless interface. The one or more functions include at least one of a printing function and a scanning function.
The first function is a function of establishing the wireless connection with the external device via the second wireless interface in order to communicate related data related to the at least one function with the terminal device. The function executing device according to claim 3. The first function is at least one of a printing function and a scanning function.
The function execution device according to claim 1 or 2, wherein the first function execution information includes relational data related to at least one of the functions. The function executing device is
The first state in which the target process using the specific authentication information cannot be executed, and
A second state in which the target process using the specific authentication information can be executed, and
Set to one of the states,
The transmitting unit transmits the screen display information to the terminal device while the function executing device is set to the first state.
The execution request is a setting change request for setting the function executing device to the second state instead of the first state.
In response to receiving the setting change request from the terminal device, the target processing execution unit sets the function execution device to the second state instead of the first state, and then the specific function execution unit is set to the second state. The function execution device according to any one of claims 1 to 5, which executes the target process using the authentication information with the terminal device. The function executing device further
When the setting change request is received from the terminal device, the first disconnection portion that disconnects the first wireless connection and the first disconnection portion.
A second establishment unit that establishes a second wireless connection with the terminal device via the first wireless interface after the first wireless connection is disconnected.
With
6. The first communication execution unit executes communication of the first function execution information with the terminal device via the first wireless interface by using the second wireless connection. The function execution device described in. 6. The first communication execution unit executes communication of the first function execution information with the terminal device via the first wireless interface by using the first wireless connection. The function execution device described in. The first wireless interface is an interface for executing wireless communication according to the Bluetooth (registered trademark) method.
The function executing device according to any one of claims 6 to 8, wherein the first state includes a state in which the first wireless interface repeatedly transmits an Advanced signal according to the Bluetooth method. When a specific Read request according to the Bluetooth method is received from the terminal device and the first wireless interface has stopped transmitting the Advanced signal, the target using the specific authentication information. The process is executed,
When the specific Read request is received from the terminal device and the first wireless interface repeatedly transmits the Advance signal, the target process using the specific authentication information is not executed.
The transmitting unit receives the specific Read request from the terminal device while the function executing device is set to the first state in which the first wireless interface repeatedly transmits the Advanced signal. The function execution device according to claim 9, wherein the screen display information is transmitted to the terminal device without executing the target process using the specific authentication information. The function execution according to claim 10, wherein the first state includes a state in which the first wireless interface repeatedly transmits an Advanced signal including disapproval information that does not allow the establishment of a wireless connection according to the Bluetooth method. apparatus. When the first wireless interface has stopped transmitting the Advanced signal, the target process using the specific authentication information is executed.
When the first wireless interface repeatedly transmits the Advanced signal, the target process using the specific authentication information is not executed, and the target process is not executed.
The second state includes a state in which the first radio interface has stopped transmitting the Advanced signal.
The setting change request is a request for preventing the first wireless interface from executing the transmission of the Advanced signal.
The transmitting unit performs the target processing using the specific authentication information while the function executing device is set to the first state in which the first wireless interface repeatedly transmits the Advanced signal. The screen display information is transmitted to the terminal device without execution.
The target processing execution unit uses the specific authentication information while the function execution device is set to the second state in which the first wireless interface has stopped transmitting the Advanced signal. The function execution device according to any one of claims 9 to 11, which executes the target process. The first wireless interface is an interface for executing wireless communication according to the Bluetooth (registered trademark) method.
The first state includes a state in which the first setting information is stored in the memory.
The first setting information is the specific Read without executing the target process using the specific authentication information when a specific Read request according to the Bluetooth method is received from the terminal device. Shows the settings to send a response to a request,
The second state includes a state in which the second setting information is stored in the memory.
In the second setting information, when the specific Read request is received from the terminal device, the target process using the specific authentication information is executed, and the authentication using the specific authentication information is successful. If so, the setting to send the response to the specific Read request is shown.
The setting change request is a request for changing the first setting information in the memory to the second setting information.
When the specific Read request is received from the terminal device while the first setting information is stored in the memory, the transmission unit performs the target process using the specific authentication information. The screen display information is transmitted to the terminal device as the response to the specific Read request without being executed.
The target processing execution unit uses the specific authentication information when the specific Read request is received from the terminal device while the second setting information is stored in the memory. The function execution device according to any one of claims 6 to 11, which executes processing. The specific authentication information is a first code prepared by the one of the function executing device and the terminal device.
In the target process using the specific authentication information, after the first code is displayed on the one device, the second code is input to the other device of the function executing device and the terminal device. When the relevant information related to the second code is transmitted from the other device to the one device,
The first communication execution unit is the first when it is determined by the one device that the first code and the second code match after the communication of the related information is executed. The function execution device according to any one of claims 1 to 13, which executes communication of the first function execution information with the terminal device via a wireless interface. The specific authentication information is a public key prepared by the one of the function executing device and the terminal device.
The execution request is a request for transmitting the public key from the one device to the function executing device and the other device of the terminal device.
The function according to any one of claims 1 to 5, wherein the first function execution information is information generated by the other device when the target process using the public key is executed. Execution device. The function executing device further
When the execution request is received from the terminal device, the second disconnection portion that disconnects the first wireless connection and
A third establishment unit that establishes a third wireless connection with the terminal device via the first wireless interface after the first wireless connection is disconnected.
With
15. The first communication execution unit uses the third wireless connection to execute communication of the first function execution information with the terminal device via the first wireless interface. The function execution device described in. 15. The first communication execution unit uses the first wireless connection to execute communication of the first function execution information with the terminal device via the first wireless interface. The function execution device described in. The first wireless interface is an interface for executing wireless communication according to the Bluetooth (registered trademark) method.
The transmission unit does not execute either the target process using the public key, which is the specific authentication information, or the communication using the specific code according to the Bluetooth method, and the screen display information. To the terminal device
The function execution according to any one of claims 15 to 17, wherein the target processing execution unit executes the target processing using the public key without executing the communication using the specific code. apparatus. When the first wireless interface repeatedly transmits an Advantage signal according to the Bluetooth method, the communication using the specific code is not executed, and the communication is not executed.
The transmitting unit does not execute the communication using the specific code while the function executing device is set to the state in which the first wireless interface repeatedly transmits the Advanced signal. The screen display information is transmitted to the terminal device,
The target processing execution unit does not execute the communication using the specific code while the function execution device is set to a state in which the first wireless interface repeatedly transmits the Advance signal. , Execute the target process using the public key,
The first communication execution unit executes the communication using the specific code while the function execution device is set to a state in which the first wireless interface repeatedly transmits the Advance signal. The function execution device according to claim 18, which executes communication of the first function execution information with the terminal device without any need. The function executing device further
When the function screen is displayed on the terminal device and then a second execution instruction for causing the function executing device to execute a second function different from the first function is input to the terminal device. A fourth establishment unit that establishes a fourth wireless connection with the terminal device via the first wireless interface.
A second function for executing the second function via the first wireless interface by using the fourth wireless connection without executing the target process using the specific authentication information. A second communication execution unit that executes communication of function execution information with the terminal device, and
The function executing device according to any one of claims 1 to 19. The second function is a function of transmitting error display information for displaying error information related to the error state to the terminal device when the function executing device is in an error state.
The function execution device according to claim 20, wherein the second communication execution unit receives a request for transmitting the error display information to the terminal device from the terminal device as the second function execution information. A computer program for terminal equipment
The computer of the terminal device is referred to as the following parts, that is,
From the function executing device via the first wireless interface of the terminal device without executing the target process using the specific authentication information prepared by the function executing device and one of the terminal devices. A receiver that receives screen display information for displaying a function screen indicating one or more functions that can be executed by the function executing device on the terminal device.
A display control unit that displays the function screen on the display unit of the terminal device when the screen display information is received from the function execution device.
After the function screen is displayed on the display unit, when a first execution instruction for causing the function executing device to execute the first function is input to the terminal device, the first wireless interface is used. A supply unit that supplies an instruction for establishing a first wireless connection with the function executing device to the OS (abbreviation of Operating System) program of the terminal device via the supply unit.
A transmission unit that transmits an execution request to the function execution device via the first wireless interface by using the first wireless connection, and the execution request utilizes the specific authentication information. The transmitter, which is a request for causing the function execution device to execute the target process,
After the target process using the specific authentication information is executed, the function execution information for executing the first function is communicated with the function execution device via the first wireless interface. Communication execution part and
A computer program that acts as. The first term computer program is the computer,
When the function screen is displayed on the terminal device and then a second execution instruction for causing the function executing device to execute a second function different from the first function is input to the terminal device. A specific establishment unit that establishes a specific wireless connection with the terminal device via the first wireless interface.
A second function for executing the second function via the first wireless interface by using the specific wireless connection without executing the target process using the specific authentication information. The function execution device according to any one of claims 22, which functions as a specific communication execution unit that executes communication of function execution information with the terminal device. The second function is a function of transmitting error display information for displaying error information related to the error state to the terminal device when the function executing device is in an error state.
The function execution device according to claim 20, wherein the specific communication execution unit receives a request for transmitting the error display information to the terminal device from the terminal device as the second function execution information.

Images