JP7293704B2 - Computer program for function execution device and terminal device - Google Patents

Description

This specification discloses a technology related to a device capable of executing communication using specific authentication information.

Patent Literature 1 discloses a communication device that performs pairing with an information processing device according to the BLE (abbreviation for Bluetooth (registered trademark) Low Energy) standard. 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, the PIN code is authenticated and GATT communication becomes available. The communication device uses GATT communication to supply a list of services supported by the communication device to the information processing device. The information processing device uses GATT communication to transmit the password to the communication device in order to provide the remote UI service included in the list. The information processing terminal displays the remote UI when an access permission response is received from the communication device as a response to the password.

JP 2017-182489 A JP 2007-068035 A JP 2016-225949 A JP 2018-14006 A JP 2017-59063 A

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

With the above technology, for example, communication for authentication of the PIN code is executed even if the service desired by the user is not included in the services supported by the communication device.

In this specification, for example, when a function desired by a user is not included in one or more functions that can be executed by a function execution device, the technology.

A function execution device disclosed in this specification includes: a first wireless interface; a first establishing unit that establishes a first wireless connection with a terminal device via the first wireless interface; using the first wireless connection without executing communication using specific authentication information prepared by one of the function execution device and the terminal device via the wireless interface of a transmission unit configured to transmit, via the first wireless interface, screen display information for causing the terminal device to display a function screen showing one or more functions executable by the function execution device, to the terminal device; When a first execution instruction for causing the function execution device to execute a first function is input to the terminal device after the function screen is displayed on the terminal device, the first wireless interface is enabled. a second establishing unit that establishes a second wireless connection with the terminal device via the second wireless connection; and the specific authentication information via the first wireless interface using the second wireless connection. a first communication execution unit that executes the communication using the terminal device, and the first function via the first wireless interface after the communication using the specific authentication information is executed and a second communication execution unit that executes communication of first function execution information for executing with the terminal device.

According to the above configuration, the function execution device uses the first wireless connection to transmit the screen display information to the terminal device without executing communication using specific authentication information. As a result, the function screen is displayed on the terminal device without executing communication using 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 uses the second wireless connection and uses the specific authentication information. Communication is performed with the terminal device, and then communication of the first function execution information is performed with the terminal 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 the one or more functions executable by the function execution device, the specific authentication information Communication using is not executed. Therefore, when the function desired by the user is not included in the one or more functions executable by the function execution device, execution of communication using the authentication information can be suppressed.

Further, the computer program of the terminal device disclosed in this specification causes the computer of the terminal device to communicate with the function execution device via the following units, that is, the first wireless interface of the terminal device. a first supply unit for supplying a first command for establishing a connection to an OS (Operating System) program of the terminal device; said function executing device via said first wireless interface using said first wireless connection without performing communication using specific authentication information prepared by one of the devices; a receiving unit for receiving screen display information for causing the terminal device to display a function screen showing one or more functions executable by the function execution device; and a reception unit for receiving the screen display information from the function execution device. a display control unit for displaying the function screen on a display unit of the terminal device when the function screen is displayed on the display unit; sending a second instruction to the OS program to establish a second wireless connection with the function execution device via the first wireless interface when an execution instruction of No. 1 is input to the terminal device; The communication using the second supply unit that supplies and the specific authentication information is performed with the function execution device via the first wireless interface using the second wireless connection. Later, it may function as a communication execution unit that executes communication of function execution information for executing the first function with the function execution device via the first wireless interface.

According to the above configuration, the terminal device receives screen display information from the function execution device using the first wireless connection without executing communication using specific authentication information. As a result, the function screen is displayed on the terminal device without executing communication using specific authentication information. Then, after the function screen is displayed, the terminal device uses the second wireless connection to perform communication using the specific authentication information when the first execution instruction is input to the terminal device. and then communicate 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 the one or more functions executable by the function execution device, the specific authentication information Communication using is not executed. Therefore, when the function desired by the user is not included in the one or more functions executable by the function execution device, execution of communication using the authentication information can be suppressed.

A computer program for implementing the above function execution device, a computer readable recording medium storing the computer program, and a method executed by the above function execution device are also novel and useful. Also novel and useful are computer-readable recording media storing a computer program for the terminal, the terminal itself, and methods performed by the terminal.

1 shows the configuration of a communication system; 1 shows a conceptual diagram of a Primary Service group; FIG. The data structure of the Primary Service group is shown. FIG. 3 shows a continuation of FIG. FIG. 4 shows a continuation of FIG. FIG. 4 shows a sequence diagram of a comparative example; 7 shows a continuation of FIG. FIG. 4 shows a sequence diagram of processing common to the first to fifth embodiments. FIG. 8 shows a continuation of FIG. FIG. 10 is a sequence diagram of a case in which the AP connection button within the function screen is selected in the first and second embodiments, or a case in which the BLE connection button within the function screen is selected in the fifth embodiment; FIG. 10 shows a continuation of FIG. FIG. 11 shows a continuation of FIG. FIG. 11 shows a sequence diagram of a case in which the WFD connection button in the function screen is selected in the first and second embodiments; FIG. 13 shows a continuation of FIG. FIG. 11 shows a sequence diagram of a case in which an error information button in the function screen is selected in the first to fifth embodiments; FIG. 11 shows a sequence diagram of a case in which an AP connection button in the function screen is selected in the third and fourth examples; FIG. 16 shows a continuation of FIG. 16 in the third embodiment. FIG. 16 shows a continuation of FIG. 16 in the fourth embodiment.

(First embodiment)
(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 for Access Point) 200 . The terminal 10 participates in a wireless network formed by the AP 200 (hereinafter referred to as "AP network"). The AP 200 stores an SSID (abbreviation for Service Set Identifier) 'ap01' for identifying an 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, smart phone), PDA, tablet PC, or the like. The terminal 10 includes a display unit 12 , a wireless LAN interface 14 , a BT (abbreviation for Bluetooth (registered trademark)) interface 16 , and a control unit 30 . Each unit 12 to 30 is connected to a bus line (reference numerals omitted). In the following description, the interface is 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/F 14 is a wireless interface for performing wireless communication according to the Wi-Fi system (hereinafter referred to as "Wi-Fi communication"). The Wi-Fi system is, for example, the IEEE (abbreviation of The Institute of Electrical and Electronics Engineers, Inc.) 802.11 standard and standards conforming thereto (eg 802.11a, 11b, 11g, 11n, 11ac, etc.) is a wireless communication scheme for performing wireless communication according to. The wireless LAN I/F 14 particularly supports the WFD (abbreviation for Wi-Fi Direct (registered trademark)) system established by the Wi-Fi Alliance. The WFD system is a wireless communication system described in the standard "Wi-Fi Peer-to-Peer (P2P) Technical Specification Version 1.1" created by the Wi-Fi Alliance.

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

The BTI/F 16 is an I/F for executing wireless communication according to the BT system. The BT system is, for example, a wireless communication system based on the IEEE802.15.1 standard and standards conforming thereto. More specifically, the BTI/F 16 supports BLE (short for Bluetooth Low Energy). BLE is a standard implemented in BT system version 4.0 and later versions. In this embodiment, it is assumed that the BTI/F 16 supports BLE implemented in version 4.2. The BTI/F 16 can execute wireless communication according to BLE (hereinafter referred to as “BLE communication”). In addition, in a modified example, the BTI/F 16 may support BLE implemented in versions after version 4.2 (for example, 5.0).

Describe the differences between the Wi-Fi system and the BT system. 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 carrier wave frequency in Wi-Fi communication is 2.4 GHz band or 5.0 GHz band. The frequency of carrier waves in BT communication is in the 2.4 GHz band. That is, when the 5.0 GHz band is adopted as the frequency of the carrier wave in Wi-Fi communication, the frequency of the carrier wave in Wi-Fi communication is different from the frequency of the carrier wave in BT communication. Also, the maximum distance over which Wi-Fi communication can be performed (eg, about 100 m) is longer than the maximum distance over which BT communication can be performed (eg, about several tens of meters).

The control unit 30 has a CPU 32 and a memory 34 . CPU 32 executes various processes according to programs 36 and 38 stored in memory 34 . The memory 34 comprises a volatile memory, a non-volatile memory, etc., and includes an OS (Operating System) program 36 (hereinafter simply referred to as "OS 36") and a print application 38 (hereinafter simply referred to as "application 38"). do). In this embodiment, it is assumed that the OS 36 is iOS (registered trademark).

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

(Configuration of printer 100)
The printer 100 is a peripheral device capable of executing a print function (for example, a peripheral device of the terminal 10). Printer 100 includes display unit 112 , wireless LAN I/F 114 , BTI/F 116 , and 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 LAN I/F 114 is the same as the wireless LAN I/F 14 of the terminal 10 . That is, the wireless LAN I/F 114 supports the WFD system. BTI/F 116 is similar to BTI/F 16 of terminal 10 . That is, the BTI/F 116 supports BLE.

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

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

Protocol stack 138 has the hierarchical structure shown in FIG. L2CAP (abbreviation of Logical Link Control and Application Protocol) is a stack for establishing wireless connection (hereinafter referred to as “L2CAP Link”) via BTI/F 116 . SMP (short for Security Manager Protocol) and ATT (short for Attribute Protocol) are layers above L2CAP. SMP is a protocol for encrypting information communicated over L2CAP Link. ATT is a protocol for defining an access method between a server and a client in communication via L2CAP Link. GATT (abbreviation for Generic Attribute Profile) is an upper layer of ATT and is a protocol for defining 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 addition, below, Primary Service is simply described as "PS."

The WFD information 160 is information used to establish a wireless connection according to the WFD system (hereinafter referred to as “WFD connection”). The WFD information 160 includes an SSID “p01” for identifying the WFD network formed by the printer 100 operating as G/O and a password “yyy” used in the WFD network. The WFD information 160 may be stored in the memory 134 in advance when the printer 100 is shipped, or may be generated when the power of the printer 100 is turned on.

The restart flag 162 is set to "ON" indicating that the transmission of the ADV signal is restarted immediately after the transmission of the Advertise signal (hereinafter simply referred to as "ADV signal") according to the BT system is stopped, and the transmission of the ADV signal. "OFF" indicating that the transmission of the ADV signal is not restarted immediately after stopping the ADV signal. The restart flag 162 is set to "ON" when the power of the printer 100 is turned on.

(Concept of PS group; Fig. 2)
The concept of PS groups included in the protocol stack 138 will be described with reference to FIG. The table in FIG. 2 conceptually shows the PS group for easy understanding, and differs from the concrete data structure of the PS group. The data structure of the PS group will be explained with reference to FIGS. 3 to 5 after the explanation of FIG. 2 is finished. 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. Hereinafter, GAP Service is simply referred to as "GA". GA 138A is PS for transmitting information about BTI/F 116 . The information includes, for example, the device name DN indicating the BTI/F 116, information indicating the standards supported by the BTI/F 116, and the like. The GA 138A is assigned the UUID "0x1800" predetermined by the BT standard as an identifier for identifying the PS corresponding to the GA. GA138A contains multiple Characteristics. Characteristic is information that defines specific functions of the PS. A plurality of Characteristics included in GA 138A includes a Characteristic "Device Name" that defines transmission of the device name DN. "Device Name" is assigned a UUID "0x2A00" predetermined by the BT standard as an identifier for identifying the Characteristic. Note that description of other Characteristics included in GA138A is omitted in FIG.

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

(Function Service 138B)
Hereinafter, Function Service is simply referred to as "FS". FS 138B is a PS for transmitting function information FI indicating a plurality of functions that printer 100 can execute. The function information FI includes information indicating a printing function, information indicating a function of establishing a wireless connection (hereinafter referred to as "AP connection") with an AP (for example, the AP 200), and information indicating a function of establishing a WFD connection. , and information indicating the ability to send the error URL. The FS 138B is assigned the UUID "aaa0" defined by the vendor of the printer 100 as an identifier for identifying the PS corresponding to the FS. The UUID for identifying the PS of the second type is determined by the vendor of the printer 100 also below. Note that the UUID "aaa0" has a larger number of digits than the number of digits of a UUID (for example, UUID "0x1800") predetermined by the BT standard, and is described in a simplified manner in this specification. there is

FS 138B includes Characteristic "Function Information" that defines transmission of functional information FI. "Function Information" is assigned a UUID "aaa1" determined by the vendor of the printer 100 as an identifier for identifying the Characteristic. UUIDs for identifying the Characteristic included in the PS of the second type are determined by the vendor of the printer 100 also below.

(AP Connection 138C)
Below, AP Connection is simply described as “AC”. AC 138C is a PS for establishing AP connection. AC 138C is assigned UUID "bbb0". AC138C includes four Characteristic including "Connection Status", "IP Address", "Connection Information" and "Change Permission".

“Connection Status” is a Characteristic (UUID “bbb1”) that defines transmission of AP status information indicating the status of AP connection of the printer 100 . The AP state information indicates one of a plurality of states including 'Disable', 'Enable', 'Busy', and 'Error'. "Disable" indicates that the printer 100 is set to a state that does not permit establishment of an AP connection. "Enable" indicates that the printer 100 is set to permit establishment of an AP connection. "Busy" indicates that processing for establishing AP connection is being executed. "Error" indicates that the process for establishing AP connection has failed.

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

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

"Change Permission" is a Characteristic (UUID "bbb4") that defines receiving an instruction to change the value of Attribute Permission, which will be described later. Note that Change Permission is used in the third and fourth embodiments, and not used in the first and second embodiments.

(WFD Connection 138D)
Below, WFD Connection is simply described as "WC". WC 138D is a PS (UUID “ccc0”) for establishing a WFD connection. WC138D includes four Characteristics including 'Connection Status', 'Connection Information', 'Public Key' and 'Change Status'.

“Connection Status” is a Characteristic (UUID “ccc1”) that defines transmission of WFD status information indicating the status of the WFD connection of the printer 100 . The WFD state information indicates one of a plurality of states including 'Disable', 'Enable', 'Ready', 'Start', and 'Error'. “Disable” indicates that the printer 100 is set to a state that does not permit establishment of a WFD connection. “Enable” indicates that the printer 100 is set to permit 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.

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

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

"Change Status" is a Characteristic (UUID "ccc4") that defines reception of an instruction to change the status of the WFD connection of the printer 100 (for example, an instruction to operate the printer 100 as G/O).

(BT Control 138E)
Below, BT Control is simply referred to as "BC". BC 138E is a PS (UUID “ddd0”) for receiving instructions to change the state of BTI/F 116 . BC138E includes two Characteristics including "Paring Control" and "Advertising Control".

“Pairing Control” is a Characteristic (UUID “ddd1”) that defines receiving an instruction to disconnect an established L2CAP Link.

"Advertising Control" is a Characteristic (UUID "ddd2") that defines receiving an instruction to change the resume flag 162 from "ON" to "OFF".

(Error Service 138F)
Below, Error Service is simply referred to as "ES". ES 138F is a PS (UUID “eee0”) for transmitting an error URL. The error URL is a URL indicating a web page that describes a method for solving an error state (for example, paper jam) in which the printer 100 cannot execute the print function. ES 138F contains Characteristic “Error Information (UUID “eee1”)” that defines the transmission of the error URL.

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

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". 3 to 5, some data structures after "0x0002" are omitted. For this reason, Handles after "0x0002" are represented by symbols "nk (k=1, 2, 3, . . . )" instead of actual values. 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 "AValue") 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, APer stores a value indicating each of the four items. The first item is an item indicating whether reading or writing of information is permitted, and one value indicating one of "Readable", "Writeable", and "Readable and writeable" is stored in APer. be done. The second item is an item indicating whether or not Encryption is required when reading or writing information, and one value indicating either "Encryption required" or "No encryption required" 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" remembered. A fourth item indicates whether or not authorization is required when reading or writing information, and one value indicating either "Authorization required" or "No authorization required" remembered. If a value indicating any of "Encryption required", "Authentication required", and "Authorization required" is stored in APer, information Read or write is allowed. Also, when a value indicating "No encryption required", "No authentication required", and "No authorization required" is stored in APer, it is possible to read or write information without executing authentication communication according to SMP. Allowed. 3 to 5 show these in a simplified manner. For example, when the 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 is actually stored in Also, the description of APer in FIGS. 3 to 5 is omitted for the second item and the fourth item. Actually, each APer stores a value indicating "No encryption required" as the second item and a value indicating "No authorization required" as the fourth item. Hereinafter, 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 In addition, when APer stores each value indicating "Readable without authentication when discoverable", the value indicating "Readable" as the first item and "No authentication required" as the third item. ” and a value indicating “No authorization required” as the fourth item are stored in the APer, and the server is in a discoverable state (that is, “when discoverable") is satisfied, a value indicating permission to read information without performing authentication communication according to SMP is sent to the APer in accordance with "No authentication required" and "No authorization required". remembered. As described above, it should be noted that the description of Aper in the drawings does not completely correspond to 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 of Handle from "0x0001" to a predetermined value (one value before "n2"). The AType corresponding to Handle "0x0001" includes UUID "0x2800" indicating the first data in the data group forming one PS. AValue corresponding to Handle "0x0001" includes UUID "0x1800" for distinguishing GA138A from other PSs. APer corresponding to Handle "0x0001" includes each value indicating "Readable without authentication". Each value means that the information can be read without performing encryption of the information according to SMP.

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

AType corresponding to Handle "n1" includes UUID "0x2A00" of Characteristic "Device Name". The AValue corresponding to Handle "n1" contains the device name DN. The APer corresponding to Handle "n1" contains values indicating "Readable without authentication when discoverable". Each of these values allows reading out information (here, device name DN) without executing information encryption according to SMP when the state of the BT-based peripheral (that is, the printer 100) is in the discoverable state. It means possible. In other words, when the state of the peripheral is not in the discoverable state (that is, when it is in the non-discoverable state), the information can be read on the condition that the information is encrypted according to the SMP. means Here, the Discoverable state is a state in which the peripheral repeatedly executes ADV signal transmission. In other words, the Discoverable state is a state in which when an ADV signal is received by a BT-based central, the central can detect the presence of the peripheral. 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" specified in the BT standard, or the LE General Discoverable Mode flag "1" specified in the BT standard. be. On the other hand, the non-discoverable state is a state in which the peripheral does not transmit the ADV signal, or a state in which the peripheral repeatedly transmits the ADV signal and the ADV signal includes the above-mentioned predetermined value. is not enabled (in other words, the ADV signal includes both LE Limited Discoverable Mode flag "0" and LE General Discoverable Mode flag "0"). Note that "Readable without authentication when discoverable" is an item defined in the standard after version 4.2. Hereinafter, unless otherwise specified, it is assumed that the ADV signal contains a predetermined value regarding the Discoverable state in the situation where the ADV signal is transmitted.

Since GA138A has the above data structure, the device name DN in GA138A is read as follows. When the CPU 132 (that is, the server) receives a Read By Type Request signal specifying UUID “0x2803” from the client, the client receives UUID “0x2803” according to “Readable without authentication” indicated by APer corresponding to UUID “0x2803”. Allows to read the corresponding AValue (ie property “Read”, Handle “n1” and UUID “0x2A00”). As a result, the client can read (that is, receive) these pieces of information, and based on these pieces of information, it is possible to execute a 'Read' of information corresponding to Handle 'n1' and UUID '0x2A00'. can know The client then transmits a Read By Type Request signal designating UUID "0x2A00" 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 UUID "0x2A00" according to "Readable without authentication when discoverable" indicated by APer corresponding to UUID "0x2A00". allow This allows the client to read the device name DN.

For the first type PS, among the above items such as "Readable without authentication", items predetermined by the SIG are adopted. That is, for example, for 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, for the second type 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 UUID "0x2800" indicating the leading data of FS138B. AValue corresponding to Handle "n2" includes UUID "aaa0" for distinguishing FS138B from other PSs. APer corresponding to Handle "n2" includes each value indicating "Readable without authentication".

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

AType corresponding to Handle "n4" includes UUID "aaa1" of Characteristic "Function Information". AValue corresponding to Handle "n4" includes function information FI. 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 Handle range "n5" to "n13". The AType corresponding to Handle "n5" includes UUID "0x2800" indicating that it is the leading data of AC138C. AValue corresponding to Handle "n5" includes UUID "bbb0" for distinguishing AC138C from other PSs. APer corresponding to Handle "n5" includes each value indicating "Readable without authentication".

Each AType corresponding to Handles "n6" to "n9" includes UUID "0x2803" indicating that it is a Characteristic Declaration. The AValue corresponding to Handle 'n6' includes property 'Read', Handle 'n10', and UUID 'bbb1'. Similarly, each AValue corresponding to Handles 'n7' to 'n9' includes properties, Handles, and UUIDs. Note that each property corresponding to Handles 'n8' and 'n9' is 'Write' instead of 'Read'. Also, each APer corresponding to Handles "n6" to "n9" includes each value indicating "Readable without authentication".

AType corresponding to Handle "n10" includes UUID "bbb1" of Characteristic "Connection Status". The AValue corresponding to Handle 'n10' contains AP state information (eg, 'Disable'). APer corresponding to Handle "n10" includes each value indicating "Readable without authentication".

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

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

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

Since the AC 138C has the above data structure, for example, the following information is written in the AValue corresponding to the UUID "n12" in the AC 138C. When the CPU 132 (that is, the server) receives a Read By Type Request signal specifying UUID "0x2803" from the client, the client receives each UUID "0x2803" according to "Readable without authentication" indicated by APer corresponding to each UUID "0x2803". ” (ie, property “Read (or Write)”, Handles “n10” to “n13”, and UUIDs “bbb1” to “bbb4”) corresponding to . As a result, the client can read these information, and based on these information, know that it is possible to execute "Write" of information corresponding to Handle "n12" and UUID "bbb3", for example. can be done. Then, the client sends to the server a Write Request signal specifying Handle "n12" and including the information to be written (that is, the SSID and password). Upon receiving the signal, the server permits information to be written to AValue corresponding to Handle "n12" in accordance with "Writeable without authentication" indicated in APer corresponding to 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 Handle range "n14" to "n22". The AType corresponding to Handle "n14" includes UUID "0x2800" indicating the head data of WC138D. The AValue corresponding to Handle "n14" includes UUID "ccc0" to distinguish WC138D from other PSs. APer corresponding to Handle "n14" includes each value indicating "Readable without authentication".

Each AType corresponding to Handles "n15" to "n18" includes UUID "0x2803" indicating that it is a Characteristic Declaration. The AValue corresponding to Handle "n15" includes property "Read", Handle "n19", and UUID "ccc1". Similarly, each AValue corresponding to Handles "n16~" to "n18" includes properties, Handles, and UUIDs. Note that each property corresponding to Handles 'n17' and 'n18' is 'Write' instead of 'Read'. Also, each APer corresponding to Handles "n15" to "n18" includes each value indicating "Readable without authentication".

AType corresponding to Handle "n19" includes UUID "ccc1" of Characteristi "Connection Status". The AValue corresponding to Handle "n19" contains WFD state information (eg, "Disable"). APer corresponding to Handle "n19" includes each value indicating "Readable without authentication".

The AType corresponding to Handle "n20" contains the UUID "ccc2" of the Characteristic "Connection Information". The AValue corresponding to Handle 'n20' may contain the encrypted WFD information. Here, before the WFD information 160 is encrypted, the AValue does not contain encrypted WFD information, but contains null information. Also, APer corresponding to Handle "n20" includes each value indicating "Readable without authentication".

The AType corresponding to Handle "n21" contains the UUID "ccc3" of the Characteristic "Public Key". A public key is written in AValue corresponding to Handle “n21”. Also, the AType corresponding to the Handle "n22" includes the UUID "ccc4" of the Characteristic "Change Status". The AValue corresponding to the Handle "n22" contains each instruction for changing the state of the WFD connection (for example, an Enable instruction to change the state of the printer 100 from "Disable" to "Enable", the printer 100 as G/O Start instruction for operation) is written. Each APer corresponding to each Handle "n21" and "n22" contains each 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 UUID "0x2800" indicating the leading data of BC138E. AValue corresponding to Handle "n23" contains UUID "ddd0..." to distinguish BC138E from other PSs. APer corresponding to Handle "n23" includes each value indicating "Readable without authentication".

Each AType corresponding to Handles 'n24' and 'n25' includes UUID '0x2803' indicating that it is a Characteristic Declaration. The AValue corresponding to Handle 'n24' includes the property 'Write', the Handle 'n26', and the UUID 'ddd1'; similarly, the AValue corresponding to Handle 'n25' includes the property, Handle, and UUID.

The AType corresponding to Handle 'n26' contains the UUID 'ddd1' of the Characteristic 'Paring Control'. A disconnect instruction for disconnecting the L2CAP Link is written in AValue corresponding to Handle "n26". The AType corresponding to Handle "n27" contains the UUID "ddd2" of the Characteristic "Advertising Control". A resume flag OFF instruction for changing the resume flag 162 from "ON" to "OFF" is written in AValue corresponding to Handle "n27". Each APer corresponding to each Handle 'n26' and 'n27' contains each 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 UUID "0x2800" indicating the head data of ES138F. AValue corresponding to Handle "n28" includes UUID "eee0" for distinguishing ES138F from other PSs. APer corresponding to Handle "n28" includes each value indicating "Readable without authentication".

The AType corresponding to Handle "n29" includes UUID "0x2803" indicating a Characteristic Declaration. The AValue corresponding to Handle 'n29' includes property 'Read', Handle 'n30' and UUID 'eee1'. APer corresponding to Handle "n29" includes each value indicating "Readable without authentication".

The AType corresponding to Handle "n30" contains the UUID "eee1" of the Characteristic "Error Information". The AValue corresponding to Handle "n30" may contain the error URL. Here, if the printer 100 is not in an error state, the AValue does not contain an error URL and contains null information. Also, APer corresponding to Handle "n30" includes each value indicating "Readable without authentication".

(Comparative example; FIGS. 6 and 7)
Before describing the processing performed by the terminal 10 and the printer 100 of the present embodiment, the processing performed by the portable 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 also 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 has a program different from the program 136 for realizing the processing of this embodiment, and does not store the restart flag 162 . Moreover, the PS group of the comparative example contains at least GA138A and FS138B. In the following, from the viewpoint of ease of understanding, processing executed by the CPU of the terminal 300 in accordance with the OS 36 and the application 338 will be described mainly with respect to the OS 36 and the application 338, respectively. All communications in the comparative example are performed via the BTI/Fs of the terminal 300 and the printer 500, respectively, so the description of "via the BTI/Fs" will be omitted below.

At T10, the user performs an operation on the terminal 300 to activate the application 338, and as a result, the application 338 is activated. In this case, at T12, the application 338 supplies a Scan start command to the OS36. The Scan start command is a command for starting transmission of the Scan Request signal.

At T14, the user performs an operation to turn on the power of the printer 500. FIG. At T20, the printer 500 begins broadcasting ADV signals. The signal includes a connection permission parameter "ADV_IND" predetermined by the BT standard. The parameter indicates permission to establish an L2CAP Link with the device that received the ADV signal. Note that in a modification, the connection permission parameter may be "ADV_DIRECT_IND".

When the OS 36 acquires a Scan start command from the application 338 (T12) and receives an ADV signal from the printer 500 (T20), it transmits a Scan Request signal to the printer 500 at T22. This signal is a signal for requesting information on the device that sent the ADV signal (the printer 500 in this case).

At T24, the OS 36 receives a Scan Response signal from the printer 500 in response to the Scan Request signal. The signal includes the model name of printer 500, “model0”. When OS 36 receives the signal, it provides the signal to application 338 .

When the application 338 acquires the Scan Response signal from the OS 36, the connection confirmation screen is displayed on the display unit of the terminal 300 in 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 the model name "model0" included in the Scan Response signal and a connection button for accepting an instruction to establish the L2CAP Link.

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

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

When the L2CAP Link is established at T34, the printer 500 stops transmitting the ADV signal at T36. That is, the printer 500 transitions from the discoverable state to the non-discoverable state. The reason why the transmission of the ADV signal is stopped in response to the establishment of the L2CAP Link is, for example, the specifications of the BTI/F 116 chip.

Also, the OS 36 utilizes the L2CAP Link established at T34 to execute processing from T38 to T78, which will be described later. The processing from T38 to T78 is executed according to iOS specifications. That is, iOS has specifications for automatically acquiring PS group information when an L2CAP Link is established. At T 38 , OS 36 sends a Read By Group Type Request signal defined by ATT (hereinafter simply referred to as “Group_Req signal”) to printer 500 . A Group_Req signal is a signal for reading out information indicating the configuration of the PS group within 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 transmits the UUID of each PS, the first Handle of each PS, and the last Handle of each PS to the terminal 300 as a response to the signal at T40. Send to Specifically, the printer 500 acquires the AValue corresponding to the UUID “0x2800” indicating the head data from the PS group. As shown in FIG. 3, UUID "0x1800" of GA138A, "aaa0" of FS138B, etc. are acquired as AValue corresponding to UUID "0x2800". In addition, the printer 500 can handle the first Handle of each PS (for example, the first Handle "0x0001" of GA138A, the first Handle "n2" of FS138B, etc.) and the last Handle of each PS (for example, the last Handle of GA138A). (the value before n2), the last Handle "n4" of FS138B, etc.). The printer 500 then transmits each acquired information to the terminal 300 . This allows the terminal 300 to know the configuration of the PS group of the printer 500 .

Next, the OS 36 uses each information received at T40 to sequentially transmit a plurality of Read By Type Request signals (hereinafter simply referred to as "Type_Req signals") corresponding to a plurality of PSs to the printer 500. do. The Type_Req signal is a signal specifying an AType, and is a signal for reading an AValue corresponding to the specified AType. Specifically, the OS 36 executes the following processes.

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

When the printer 500 receives the Type_Req signal from the terminal 300 at T42A, the printer 500 selects the Type_Req signal from among the data group contained within the range of Handles indicated by the first Handle "0x0001" and the last Handle included in the Type_Req signal. Identify the Handle "0x0002" corresponding to the contained UUID "0x2803". Next, the printer 500 identifies AValue and APer corresponding to the identified Handle "0x0002". Here, the specified APer indicates "Readable without authentication". Therefore, in T42B, the printer 500 encrypts the identified Handle "0x0002" and the identified AValue (that is, the property "Read", Handle "n1", and UUID "0x2A00") to the terminal 300 as a response to the Type_Req signal.

Upon receiving the Handle "0x0002" and AValue from the printer 500 at T42B, the OS 36 transmits a Type_Req signal including the UUID "0x2A00" in the AValue to the printer 500 at T42C. The signal further includes GA138A's first Handle "0x0001" and GA138A's last Handle.

When the printer 500 receives the Type_Req signal from the terminal 300 at T42C, the printer 500 selects the Type_Req signal from among the data group included in the range of Handles indicated by the first Handle "0x0001" and the last Handle included in the signal. Identify the Handle "n1" corresponding to the contained UUID "0x2A00". Next, the printer 500 identifies AValue and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". As described above, printer 500 is currently in a non-discoverable state. Therefore, the printer 500 permits information to be read on the condition that the information is encrypted according to SMP. At present, a key for executing information encryption according to SMP (Long Term Key described later in this comparative example) has not been generated. For this reason, the printer 500 cannot perform encryption of information according to SMP, and as a result, at T46, an Error Response signal is sent to the terminal 300. FIG.

Upon receiving the Error Response signal from the printer 500 at T46, the OS 36 transmits a Pairing Request signal to the printer 500 at T48. This signal is a signal for starting processing related to SMP.

Upon receiving the Pairing Request signal from the terminal 300 at T48, the printer 500 transmits a Pairing Response signal to the terminal 300 at T50. Then, the printer 500 displays the PIN code "1234" at T52. This allows the user to know the PIN code "1234".

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

As shown in FIG. 7, at T60, the OS 36 accepts input of the PIN code "1234" on the PIN input screen. As a result, at T62, authentication communication according to SMP is executed between the OS 36 and the printer 500. FIG. Encrypted information, which is information encrypted by the entered PIN code "1234", is communicated during at least a portion of the authentication communication. 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 process after T72, which will be described later, the information to be BLE-communicated between the OS 36 and the printer 500 is encrypted with the Key. In FIG. 7, thin-line arrows and thick-line arrows indicate communication of unencrypted information and communication of information encrypted according to SMP, respectively. The same applies to the following figures.

When the authentication communication of T62 is completed, the OS36 again transmits a Type_Req signal similar to that of T42C in FIG. 6 to the printer 500 in T72. However, as mentioned above, the information in the signal is encrypted with the Key.

When the printer 500 receives the Type_Req signal from the terminal 300 at T72, it decodes the information in the signal using the Key, and the range of Handles indicated by the first Handle "0x0001" and the last Handle included in the decoded information. Handle "n1" corresponding to UUID "0x2A00" included in the Type_Req signal is identified from the data group included in the Type_Req signal. Next, the printer 500 identifies AValue and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". Although the printer 500 is in the non-discoverable state, it can encrypt information according to SMP because it has already executed the authentication process of T62. Therefore, the printer 500 permits reading of the information contained in the AValue (ie device name DN). Therefore, the printer 500 encrypts the device name DN using the Key, and transmits the encrypted device name DN to the terminal 300 at T74.

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

Upon receiving Handle "n3" and AValue from the terminal 300 at T76B, the OS 36 transmits a Type_Req signal including the UUID "aaa1" to the printer 500 at 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 at T76C, the information in the signal is decoded by the Key, and the first Handle "n2" and the last Handle "n4" included in the decoded information are indicated. The Handle "n4" corresponding to the UUID "aaa1" included in the Type_Req signal is specified from among the data group included in the Handle range. Next, the printer 500 identifies AValue and APer corresponding to the identified Handle "n4". Here, the specified APer indicates "Readable without authentication". Therefore, the printer 500 permits reading of the information (that is, function information FI) contained in the AValue. Therefore, the printer 500 encrypts the function information FI using the Key, and transmits the encrypted function information FI to the terminal 300 at T78.

At T78, after receiving the function information FI from the printer 500, the OS 36 sequentially transmits each Type_Req signal corresponding to each remaining PS in the PS group to the printer 500. FIG. OS36, by automatically executing the processing of T38 to T78 described above and the transmission of each Type_Req signal corresponding to each remaining PS, obtains the PS group information, that is, the Characteristic properties contained in each PS, UUID, And the Handle can be known.

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

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

When the application 338 acquires the second list from the OS 36 at T81D, at T82, the UUID "aaa1" is selected from the second list, and according to the property "Read" corresponding to the UUID "aaa1", the selected request the OS 36 to send a Type_Req signal containing the UUID "aaa1". As a result, the OS 36 transmits to the printer 500 a Type_Req signal containing the UUID "aaa1" and the first Handle "n2" and the last Handle "n4" of the FS138B.

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

Upon receiving the function information FI from the printer 500 at T84, the OS 36 supplies the received function information FI to the application 338. FIG.

When the application 338 acquires the function information FI from the OS 36 at T84, the function screen showing the functions of the printer 500 is displayed at T90. The function screen includes the model name "model0" of the printer 500 and character information indicating the printing function among the functions of the printer 500 indicated by the function information FI. Also, in this case, the function information FI indicates that the printer 500 is capable of establishing an AP connection, establishing a WFD connection, and transmitting 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 accepting an instruction to establish an AP connection. The WFD connection button is a button for accepting an instruction to establish a WFD connection. The error information button is a button for accepting an instruction to display an error URL. Also, the function screen further includes a Cancel button. The Cancel button is a button for accepting an instruction to cancel subsequent processing.

In this comparative example, the function desired by the user does not exist among the multiple functions (that is, print function, AP connection, WFD connection) executable by the printer 500 . 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, before the function screen is displayed at T90 on the terminal 300, the authentication communication at T62 is executed. That is, unless the user inputs the PIN code into the terminal 300 (T60), the function screen is not displayed on the terminal 300. FIG. In this comparative example, the function desired by the user is not included in the plurality of functions displayed in the function screen. That is, according to this comparative example, even if the function desired by the user is not included in the plurality of functions executable by the printer 500, the user must enter the PIN code. Therefore, in this embodiment, when a function desired by the user is not included in a plurality of functions executable by the printer 100, execution of authentication communication between the printer 100 and the terminal 10 is suppressed. Realize that. As a result, the user does not have to enter the PIN code when the function desired by the user is not included in the functions executable by the printer 100 . As a result, user convenience is improved.

(Case of Cancel; Figures 8 and 9)
A case in which the Cancel button on the function screen is selected in this embodiment will be described with reference to FIGS. 8 and 9. FIG. In the following, from the viewpoint of ease of understanding, processing executed by the CPU 32 of the terminal 10 in accordance with the OS 36 and the application 38 will be described mainly with respect to the OS 36 and the application 38, respectively. Processing executed by the CPU 132 of the printer 100 according to the program 136 will be described with the printer 100 as the main subject. In addition, communication in this embodiment is executed via each BTI/F of the terminal 10 and the printer 100 unless otherwise specified, so hereinafter, it is referred to as "via the BTI/F 16 (or 116)". Description is omitted.

T110 and T112 are the same as T10 and T12 in FIG. 6, respectively. When the user performs an operation to turn on the power of the printer 100 in T114, the printer 100 sets the restart flag 162 to "ON" in T116. Then, at T120, the printer 100 starts broadcasting an ADV signal including the connection permission parameter "ADV_IND".

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

T126-T132 are the same as T26-T32 in FIG. 6 except that the connection confirmation screen includes the model name "model1". The OS 36 sends 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 described above, the restart flag 162 indicates "ON" at this time. Therefore, the printer 100 resumes transmission of the ADV signal at T137 immediately after stopping transmission of the ADV signal at T136. That is, the printer 100 transitions to the discoverable state again immediately after transitioning from the discoverable state to the non-discoverable state. Here, the ADV signal after resuming does not include the connection permission parameter "ADV_IND" but includes the connection non-permission parameter "ADV_NONCONN_IND". This parameter indicates that establishment of L2CAP Link with the device that received the ADV signal is not permitted. A device that receives an ADV signal containing the parameter does not transmit a Scan_Request signal, and as a result, an L2CAP Link is not established between the device and 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. .

Also, the OS 36 uses the L2CAP Link established at T134 to execute the processing of T138 to T178, which will be described later. T138-T142C are the same as T38-T42C in FIG.

When the printer 100 receives the Type_Req signal including the UUID "0x2A00" from the terminal 10 at T142C, the data group included in the range of the handles indicated by the first handle "0x0001" and the last handle included in the signal. Among them, Handle "n1" corresponding to UUID "0x2A00" included in the Type_Req signal is identified. Next, the printer 500 identifies AValue and APer corresponding to the identified Handle "n1". Here, the identified APer indicates "Readable without authentication when discoverable". As described above, the printer 100 is currently in the discoverable state (T137). Therefore, the printer 100 permits information to be read without executing information encryption according to SMP. As a result, at T144, the printer 100 transmits the device name DN, which is the AValue corresponding to the UUID "0x2A00", to the terminal 10 without executing information encryption according to SMP. In this way, the printer 100 shifts to the Discoverable state again at T137. Therefore, when receiving the Type_Req signal at T142C, the printer 100 does not send an Error Response signal to the terminal 10 as at T46 in FIG. The device name DN can be sent to the terminal 10 without asking the terminal 10 to enter a code.

Upon receiving 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-T176C are the same as T76A-T76C in FIG. 7 except that encryption using a key is not performed.

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

Upon receiving the function information FI from the printer 100 at T178, the OS 36 sequentially transmits each Type_Req signal corresponding to each remaining PS in the PS group to the printer 100, and the property "Read" of each remaining PS from the printer 100. , receives each AValue corresponding to . Then, the OS 36 supplies a 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 at T180, it executes the same processing as T81A to T81D in FIG. Requests transmission from OS36. As a result, the OS 36 transmits to the printer 100 a Type_Req signal containing the UUID "aaa1" and the first Handle "n2" and the last Handle "n4" of the FS138B.

After transmitting the Type_Req signal to the printer 100 at T182, the OS 36 receives the function information FI from the printer 100 and supplies the received function information FI to the application 38 at T184.

At T184, the application 38 acquires the function information FI from the OS 36. At T185C, the application 38 selects the UUID "ddd0" of the BC138E from the first list including each UUID of each PS, and selects the selected UUID "ddd0". to OS36. As a result, at T185D, the application 38 obtains from the OS 36 the second list of each UUID of each Characteristic in BC138E (that is, a list containing two UUIDs "ddd1" and "ddd2").

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

Upon receiving the Write Request signal from the terminal 10 at T182, the printer 100 identifies AValue and APer corresponding to Handle "n26" included in the signal. Here, the identified APer indicates "Writeable without authentication". Therefore, the printer 100 permits writing of the information included in the signal (that is, the disconnection instruction) to the specified AValue. That is, the printer 100 stores the disconnection instruction in the AValue.

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

When the L2CAP Link is disconnected, at T189B, the printer 100 starts transmitting an ADV signal containing the connection permission parameter "ADV_IND" instead of the ADV signal containing the connection disapproval parameter.

Further, when the terminal 10 receives the Write Response signal from the printer 100 at T188, at T190 a function screen showing the functions of the printer 100 is displayed. The T190 function screen is similar to the T90 function screen in FIG. 7, except that the model name is different.

In this case, the function desired by the user does not exist among the multiple functions executable by the printer 100 (that is, print function, AP connection, and 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 at T142C (T142C), it transmits the device name DN to the terminal 10 without executing information encryption according to SMP (T144). That is, unlike the comparative example of FIG. 6, authentication communication is not executed before the function screen is displayed on the terminal 10 . As a result, when a function desired by the user is not included in a plurality of functions executable by the printer 100, execution of authentication communication between the printer 100 and the terminal 10 can be suppressed. In other words, the user does not have to enter the PIN code when the function desired by the user is not included in the functions executable by the printer 100 . As a result, user convenience is improved.

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

When the application 38 accepts selection of the AP connection button at T200, it supplies a connection start command to the OS 36 at T212. As a result, the OS 36 transmits a 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. Since the restart flag 162 indicates "ON", transmission of the ADV signal is restarted at T237. That is, the printer 100 shifts to the discoverable state again.

In addition, OS36 uses the L2CAP Link established in T234 to perform communications similar to those of T138 to T142B in FIG. . Then, at T242C, the OS 36 transmits a Type_Req signal including the UUID "0x2A00" to the printer 100, as at T142C in FIG.

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

Upon receiving the device name DN from the printer 100 at T244, the OS 36 executes communications similar to those at T176A to T178 in FIG. Send sequentially. Then, as in the case of FIG. 8, the OS 36 receives each AValue corresponding to the property "Read" of each remaining PS from the printer 100 without receiving the Error Response signal, and at T250, sends a connection completion notification. feed the application 38;

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

When the printer 100 receives the Write Request signal from the terminal 10 at T252, the APer corresponding to Handle "n27" indicates "Writeable without authentication", so the restart flag OFF instruction corresponds to Handle "n27". stored in the AValue to be used. The printer 100 then transmits a Write Response signal to the terminal 10 at T254.

In addition, the application 38 transmits a Write Request signal including Handle "n26" and a disconnection instruction to the printer 100 at T256 as in T186 of FIG. receives a Write Response signal from As a result, the disconnection instruction is stored in the AValue corresponding to Handle "n26".

When the restart flag OFF instruction and the disconnection instruction are stored in AValue, the printer 100 disconnects the L2CAP Link established at T234 according to the stored disconnection instruction at T260A, and sets the connection permission parameter "ADV_IND" at T260B. start transmitting ADV signals containing At T262, the printer 100 changes the restart flag 162 from "ON" to "OFF" according to the stored restart flag OFF instruction. As a result, transmission of the ADV signal is not restarted in 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 the OS 36 at T312. T322-T336 are the same as T132-T134 in FIG. Here, since the restart flag 162 is changed to "OFF" at T262 in FIG. 10, the printer 100 does not restart ADV signal transmission. That is, the printer 100 is in the non-discoverable state.

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

At the time when the Type_Req signal is received from the terminal 10 at T342C, no Key has been generated. Therefore, the printer 100 transmits an Error_Response signal to the terminal 10 in T346 because APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state.

Upon receiving the Error Response signal from the printer 100 at T346, the OS 36 transmits a Pairing Request signal to the printer 100 at T348, and receives a Pairing Response signal from the printer 100 at 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 OS 36 accepts the input of the PIN code “1234” on the PIN input screen at T360, at T362, the OS 36 and the printer 100 perform authentication communication according to SMP. In the authentication communication, the encrypted information encrypted by the entered PIN code “1234” is successfully decrypted, and the Key is sent from the printer 100 to the terminal 10 . As a result, information communicated between the OS 36 and the printer 100 according to the BT method is encrypted with the Key in the processing after T372, which will be described later.

When the authentication communication of T362 is completed, OS36 again transmits the Type_Req signal similar to that of T342C to the printer 500 in T372. However, as described above, the information in the Type_Req signal is encrypted with the Key.

At the time when the Type_Req signal is received from the terminal 10 at T372, the Key has been generated and the information can be encrypted according to SMP. Therefore, in T374, the printer 100 uses the Key to encrypt the device name DN, and Send the encrypted device name DN to the terminal 300 .

In T374, when the OS receives the device name DN from the printer 100, it performs the same communication as in T176A to T178 of FIG. Each Type_Req signal corresponding to each PS is sequentially transmitted to the printer 100 . As a result, the OS 36 receives each AValue corresponding to the property "Read" of each remaining PS from the printer 100, and supplies a connection completion notification to the application 38 at T380.

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

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

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

At T408, the application 38 accepts an instruction to select the SSID "ap01" from the list on the SSID screen, and accepts input of the AP 200 password "xxx" in the entry field on the SSID screen. As a result, the application 38 selects the UUID "bbb3" from the second list that has already been acquired, and, via the OS 36, transfers the Handle "n12" and the SSID "ap01" corresponding to the selected UUID "bbb3". A Write Request signal containing the password “xxx” is sent to the printer 100 . Here, the information in the Write Request signal (ie Handle "n12", SSID "ap01" and password "xxx") is encrypted by Key.

Upon receiving the Write Request signal from the terminal 10 at 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 AValue corresponding to Handle "n12". Next, in T412, the printer 100 transmits a Write Response signal to the terminal 10, and in T414, uses the stored SSID "ap01" and password "xxx" to perform AP connection processing for establishing an AP connection. Start and change the AP state information from "Enable" to "Busy".

When the application 38 receives the Write Response signal from the printer 100 via the OS 36 at T412, it transmits a Type_Req signal including the UUID "bbb1" to the printer 100 via the OS 36 at T416. At T416, the application 38 sends a Type_Req signal including the UUID "bbb1" to the printer 100 before completing the AP connection process. As a result, at T418, the application 38 receives the AP status information "Busy" in the AValue corresponding to the UUID "bbb1" from the printer 100 via the OS36.

Since the application 38 obtains "Busy", it can know that the AP connection processing has not been completed, and in T422, it again transmits the Type_Req signal including the UUID "bbb1" to the printer 100 via the OS36. Here, the AP connection processing is completed at T420, and the AP connection is established between the printer 100 and the AP200. In FIG. 12, dashed arrows indicate Wi-Fi communication using an AP network (that is, communication via the wireless LAN I/F 114). The printer 100 changes the AP status information from "Busy" to "Enable" when the AP connection is established. After that, in T422, the application 38 sends a Type_Req signal including the UUID "bbb1" to the printer 100. FIG. As a result, at T424, the application 38 receives the AP status information "Enable" in the AValue 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 OS 36 at T424, the application 38 receives the UUID “bbb2” of the “IP Address” of the AC 138C via the OS 36 and the first and the last Handle "n13" to the printer 100. As a result, the application 38 receives the IP address IA in the AValue corresponding to the UUID "bbb2" from the printer 100 via the OS 36 at 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 addressed to the IP address IA in T430. As a result, the OS 36 uses the AP network of the AP 200 to transmit a confirmation signal via the wireless LAN I/F 14 . An AP connection is established between the printer 100 and the AP 200 as described above. Therefore, the confirmation signal is received by printer 100 via AP 200 .

Upon receiving the confirmation signal from AP 200 via wireless LAN I/F 114 at T430, printer 100 transmits a response signal to the confirmation signal to terminal 10 via wireless LAN I/F 114 and AP 200 at T432.

When the application 38 receives a response signal from the printer 100 via the OS 36 at T432, it determines that communication with the printer 100 can be executed. T434-T438B executed after T432 are the same as T256-T260B in FIG. 10 except that the information in the Write Request signal is encrypted with a Key.

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

Also, when the application 38 receives a Write Response signal from the printer 100 via the OS 36 at T436, it displays a print screen on the display unit 12 at T450. Then, the application 38 receives 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 sends print data including image information corresponding to the selected image and setting information indicating the input print settings to the printer 100 via the OS 36, the wireless LAN I/F 14, and the AP 200. Send to As a result, the printer 100 prints the image corresponding to the image information received from the terminal 10 in accordance with the print settings indicated by the setting information received from the terminal 10 at T454.

According to the configuration of this case, when the AP connection button in the function screen is selected (T200 in FIG. 10), the printer 100 changes the restart flag 162 from "ON" to "OFF" (T262). As a result, the printer 100 does not resume transmission of the ADV signal after stopping transmission of the ADV signal in response to the establishment of the L2CAP Link. Then, the printer 100 executes authentication communication because 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 AP 200 with the Key and send 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; Figures 13 and 14)
A case in which the WFD connection button on the function screen is selected in this embodiment will be described with reference to FIGS. 13 and 14. FIG. In this case, the WFD connection function desired by the user exists among a plurality of functions (that is, print function, AP connection, and WFD connection) executable by the printer 100 . In this case, the user selects the WFD connection button in the function screen at T200.

When the application 38 receives selection of the WFD connection button in T500, it supplies a connection start command to the OS 36 in T512. T532 to T537 are the same as T232 to T237 in FIG. 10 (that is, establishment of 2CAP Link and resumption of ADV signal transmission). 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 Typ_Req signal corresponding to the PS group). That is, since the printer 100 is in the Discoverable state by resuming the transmission of the ADV signal, the Error Response signal is not received and authentication communication according to SMP is not executed.

At T550, the application 38 obtains from the OS 36 a connection completion notification in response to the connection start instruction at T512, and at T552, obtains from the OS 36 a second list indicating each UUID of each Characteristic in WC138D. Then, the application 38 transmits to the printer 100 via the OS 36 a Write Request signal including Handle "n22" corresponding to the UUID "ccc4" in the second list and an Enable instruction.

When the printer 100 receives the Write Request signal from the terminal 10 at T552, the printer 100 transmits the Enable instruction to the AValue corresponding to the Handle "n22" because the APer corresponding to the Handle "n22" indicates "Writeable without authentication". memorize to The printer 100 then transmits a Write Response signal to the terminal 10 at T554.

In addition, at T556, the application 38 transmits to the printer 100 via the OS 36 a Write Request signal including the handle "n21" corresponding to the UUID "ccc3" in the obtained second list and the public key. Note that the public key may be generated in advance by the application 38 when the application 38 is activated, 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 at T556, the printer 100 sets the public key to the AValue memorize to 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 AValue corresponding to Handle "n26".

When the Enable instruction, the public key, and the disconnection instruction are stored in AValue, the printer 100 disconnects the L2CAP Link established in T534 according to the stored disconnection instruction in T564A, and sets the connection permission parameter " ADV_IND” starts transmitting ADV signals. In T566, the printer 100 changes the state of the printer 100 from "Disable" to "Enable" according to the stored Enable instruction. As a result, the WFD state information is changed from "Disable" to "Enable." Also, at T568, the printer 100 encrypts the WFD information 160 using the stored public key. 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 T562, it supplies a connection start command to the OS 36 at T570. T572 to T577 are the same as T532 to T537 in FIG. The OS 36 then executes communications similar to T138 to T142B in FIG. 8 and T242C and T244 in FIG. That is, as in FIG. 13, authentication communication according to SMP is not executed.

At T580, the application 38 obtains from the OS 36 a connection completion notification in response to the connection start instruction at T570, and at T582, obtains from the OS 36 a second list indicating each UUID of each Characteristic in WC138D. Then, the application 38 transmits to the printer 100 via the OS 36 a Type_Req signal including the UUID "ccc1" and the first Handle "n14" and the last Handle "n22" of the WC138D in the second list.

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

When the application 38 acquires the WFD status information “Ready” from the OS 36 at T584, the application 38, at T586, via the OS 36, acquires the UUID “ccc2” in the acquired second list and the first Handle “n14” of the WC138D. A Type_Req signal containing the last Handle “n22” is sent to the printer 100 . As a result, the application 38 receives the encrypted WFD information from the printer 100 via the OS 36 at T588.

In T590, the application 38 uses the public key to decrypt the received encrypted WFD information. Thereby, the application 38 acquires the WFD information 160 .

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

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

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

Also, when the printer 100 establishes a WFD connection with the terminal 10 in T600, the state of the printer 100 is changed from "Start" to "Enable" in T602.

In addition, after supplying the WFD information 160 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 in the same manner as in T582. In this case, the application 38 sends a Type_Req signal including the UUID “ccc1” to the printer 100 after the WFD connection is established. As a result, in T606, the application 38 receives the WFD status information "Enable" in the AValue 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 T606, it determines that establishment of the WFD connection is completed. T608-T612B executed after T606 are the same as T560-T564B in FIG.

T620-T622 are similar to T450-T454 in FIG. 12, except that the print data is sent directly 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). The printer 100 then 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 resumes transmission of the ADV signal after establishing the L2CAP Link (T537 in FIG. 13). Because APer indicates "Readable without authentication when discoverable" and the printer 100 is in the Discoverable state, the public key is sent to the printer 100 without performing authentication communication according to SMP (T556 ). Therefore, it is possible to suppress execution of encryption according to the SMP key when encryption using a public key is to be executed.

(For error information; Fig. 15)
A case in which 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 the error information button within the function screen to see if the printer 100 is in an error state.

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

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

In this case, when the Type_Req signal is sent to the printer 100 in T662, the printer 100 is in an error state (eg, paper jam). Therefore, when the application 38 transmits the Type_Req signal to the printer 100 at T662, it receives an error URL corresponding to the UUID "eee1" from the printer 100 via the OS36 at T664.

T666-T670B executed after T664 are the same as T256-T260B in FIG. That is, the L2CAP Link established at T644 is disconnected.

When the application 38 acquires the Write Request signal from the OS 36 at T668, it displays the error URL on the display unit 12 at T672. This allows the user to select the displayed error URL and view a web page that describes how to resolve the error condition (eg, paper jam).

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

(correspondence relationship)
The printer 100, the terminal 10, the BTI/F 116, and the wireless LAN I/F 114 are examples of the "function execution device,""terminaldevice,""first wireless interface," and "second wireless interface," respectively. A function of establishing an AP connection or a 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 respectively "function screen", "first execution instruction", and "screen display information". is an example. Print data is an example of "relational data." The connection permission parameter “ADV_IND” and the connection non-permission parameter “ADV_NONCONN_IND” are examples of “permission information” and “non-permission information”, respectively. The scan start command and connection start command are examples of the "first command" and the "second command", respectively. The L2CAPLink of T134 in FIG. 8 is an example of the "first wireless connection". The function to send an error URL, the instruction to select the error information button in the function screen, and the Type_Req signal of T662 in FIG. 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)”.

10 to 12 (for AP connection) are as follows. A PIN code and encrypted information are examples of "specific authentication information (and first (or second) code)" and "related information," respectively. The printer 100 and the terminal 10 are examples of the "one device" and the "other device", respectively. The AP 200 is an example of an "external device". The L2CAP Link of T334 in FIG. 11 and the L2CAP Link of T234 in FIG. 10 are examples of the "second wireless connection" and the "third 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 restart flag OFF instruction at T252 in FIG. 10 is an example of a "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 an example of “first function execution information”.

13 and 14 (for WFD connection) are as follows. A public key and a PIN code are examples of "specific authentication information" and "specific code", respectively. The terminal 10 and the printer 100 are examples of the "one device" and the "other device", respectively. The terminal 10 is an example of an "external device". The L2CAP Link at T534 in FIG. 13 and the L2CAP Link at T574 in FIG. 14 are examples of the "second wireless connection" and the "fourth wireless connection", respectively. The encrypted WFD information of T588 in FIG. 14 is an example of "first function execution information".

T134 in FIG. 8 and T184 in FIG. 9 are examples of processing implemented by the 'first establishing unit' and the 'transmitting unit', respectively. In the case of AP connection, T334 in FIG. 11, T362 in FIG. 11, and T410 in FIG. It is an example of the processing that is implemented. In the case of WFD connection, T534 in FIG. 13, T556 in FIG. 13, and T588 in FIG. It is an example of the processing that is implemented. T112 in FIG. 8, T184 in FIG. 9, and T190 in FIG. 9 are examples of processing implemented by the "first supply unit", the "reception unit", and the "display control unit", respectively. In the case of AP connection, T312 in FIG. 11 and T410 in FIG. 12 are examples of processing implemented by the "second supply unit" and the "communication execution unit", respectively. In the case of the WFD connection, T512 in FIG. 13 and T588 in FIG. 14 are examples of processing implemented by the "second supply unit" and the "communication execution unit", respectively.

(Second embodiment)
(For WFD connection; Fig. 13, Fig. 14)
The second embodiment is a modification of the first embodiment. The second embodiment is the same as the first embodiment, except that 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 T560 to T564B in FIG. 13 and the processes T570 to T580 in FIG. That is, the printer 100 encrypts the WFD information 160 while maintaining the establishment of the L2CAP Link established in T534 without disconnecting the L2CAP Link (T568). The printer 100 then 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 CPU 132 of the printer 100 has a relatively high processing power. If the CPU 132 has relatively high processing power, the CPU 132 can encrypt the WFD information 160 while maintaining the establishment of the L2CAP Link. For example, if the processing power of the CPU 132 is relatively low, the CPU 132 cannot encrypt the WFD information 160 while maintaining the establishment of the L2CAP Link. In such a case, as in the first embodiment, it is effective to employ a configuration that encrypts the WFD information 160 after disconnecting the L2CAP Link (see T564A in FIG. 13). On the other hand, in this embodiment, considering that the processing power of the CPU 132 is relatively high, the process of disconnecting the L2CAP Link and reestablishing the L2CAP Link (that is, the process of T560 in FIG. 13 to T580 in FIG. 14). can be omitted to prevent unnecessary processing from being executed.

(Third embodiment)
(For AP connection; Fig. 16, Fig. 17)
The third embodiment is the same as the first embodiment, except that 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 (ie, establishment of 2CAP Link, resumption of ADV signal transmission, ie, sequential transmission of Typ_Req signals corresponding to PS groups). That is, since the printer 100 is in the Discoverable state by resuming the transmission of the ADV signal, the Error Response signal is not received and authentication communication according to SMP is not executed.

At T720, the application 38 obtains from the OS 36 a connection completion notification in response to the connection start instruction at T712, and at T722, obtains from the OS 36 a second list indicating each UUID of each Characteristic in AP138C. Then, the application 38 transmits to the printer 100 via the OS 36 a Write Request signal including Handle "n13" corresponding to the UUID "bbb4" in the second list and a Permission change instruction. The Permission change instruction changes each value indicating "Readable without authentication" in the AP 138C to each value indicating "Readable with authentication" and changes each value indicating "Writeable without authentication" in the AP 138C to "Writeable with authentication". This is an instruction for changing to each value that indicates . Specifically, the instruction is an instruction for changing a value indicating "No authentication required" to a value indicating "Authentication required." In a modified example, the value indicating "No encryption required" may be changed to a value indicating "Encryption required" according to the instruction, or the value indicating "No authorization required" may be changed to a value indicating "Authorization required" may be changed to Here, "Readable with authentication" means that information can be read on condition that information is encrypted according to SMP. "Writeable with authentication" means that information can be written on condition that information is encrypted according to SMP. Note that in the modified example, not only all the data in the AP 138C, but also at least one piece of data in the AP 138C (for example, data corresponding to Handle "n10") "Readable without authentication 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 T722, the APer corresponding to Handle "n13" indicates "Writeable without authentication", so the Permission change instruction corresponds to Handle "n13". Store in AValue. The printer 100 then transmits a 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 AValue corresponding to Handle "n26".

When the Permission change instruction and the disconnection instruction are stored in AValue, the printer 100 disconnects the L2CAP Link established in response to the connection start instruction of T712 in accordance with the stored disconnection instruction in T730A, and permits connection in T730B. Start sending an ADV signal containing the parameter "ADV_IND". In T732, the printer 100 changes the values indicating "Readable without authentication" in APer corresponding to Handles "n11" and "n12" to the values indicating "Readable with authentication" in accordance with the stored Permission change instruction. Along with the change, each value indicating "Writeable without authentication" in APer corresponding to Handles "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 T728, it supplies a connection start command to the OS 36 at T742. As a result, the same processing as T332 to T336 in FIG. 11 (that is, establishment of 2CAP Link and suspension of ADV signal transmission) is executed.

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

In addition, the OS 36 uses the L2CAP Link established in response to the connection start command of T712 to perform communications similar to those of T138 to T178 in FIG. , Type_Req signal corresponding to GA138A, and Type_Req signal corresponding to FS138B).

Application 38 receives the device name DN from printer 100 because APer of GA 138A indicates "Readable without authentication when discoverable" and printer 100 is in the Discoverable state. Also, the application 38 receives the function information FI from the printer 100 because APer of the FS 138B indicates "Readable without authentication".

Upon receiving the function information FI from the printer 100, the OS 36 transmits a Type_Req signal to the printer 100 in T756A for AC138C, which is the PS corresponding to Handle "n5" having the next smallest value after Handle "n1". The signal includes the UUID '0x2803', AC 138C's first Handle 'n5', and AC 138C's last Handle 'n13'.

When the printer 100 receives the Type_Req signal from the terminal 10 in T756A, the printer 100 selects from among the data group contained within the range of Handles indicated by the first Handle "n5" and the last Handle "n13" included in the Type_Req signal, Identify Handles “n6” to “n9” corresponding to UUID “0x2803” included in the Type_Req signal. Since the APer corresponding to each of the specified Handles "n6" to "n9" indicates "Readable without authentication", the printer 100 prints each of the specified Handles "n6" to "n9" in T756B. , AValue (property 'Read', Handle 'n6', and UUID 'bbb1') to AValue (property 'Write', Handle 'n9', and UUID “bbb4”) is transmitted to the terminal 10.

Upon receiving each Handle and each AValue from the printer 500 at T756B, the OS 36 sends a Type_Req signal including UUID "bbb1" corresponding to Handle "n10" having the smallest value among AValues to the printer 100 at T756C. Send. The signal also includes AC138C's first Handle 'n5' and AC138C's last Handle 'n13'.

When the printer 500 receives the Type_Req signal from the terminal 10 in T756C, from among the data group contained within the range of Handles indicated by the first Handle "n5" and the last Handle "n13" contained in the signal, Identify the Handle "n10" corresponding to the UUID "bbb1" included in the Type_Req signal. Here, 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 perform encryption of information according to SMP, and as a result, an Error Response signal is sent to the terminal 10 at T758.

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

When the authentication communication of T782 is completed, the OS36 again transmits the Type_Req signal similar to that of T756C to the printer 100 in T790. However, as described above, the information in the Type_Req signal is encrypted with the Key.

When the Type_Req signal is received from the terminal 10 at T790, the Key has been generated, and information can be encrypted according to SMP. Therefore, due to APer indicating "Readable without authentication", the printer 100 uses the Key to encrypt the AP status information (here, "Enable") in T792, and encrypts the encrypted AP status. Send the information to the terminal 10 . T794 is similar to 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, AP connection is established and printing is executed.

According to the configuration of this case, when the AP connection button in the function screen is selected (T700 in FIG. 16), the printer 100 changes APer of AC138C from "Readable without authentication" to "Readable with authentication". (T732). As a result, the printer 100 executes authentication communication because APer of 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 AP 200 with the Key and send 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 relationship)
A state in which the restart flag is "ON" and APer indicates "Readable without authentication" and a state in which the restart flag is "ON" and APer indicates "Readable with authentication" are respectively a "first state" and a "second state." 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 at T722 in FIG. 16 is an example of a "setting change request." L2CAP Link of T334 in FIG. 11 quoted in FIG. 17 and T234 in FIG. 10 quoted in FIG. 16 are examples of "second wireless connection" and "third wireless connection", respectively. T782 in FIG. 17 is an example of processing implemented by the "first communication executing unit". T742 in FIG. 17 is an example of processing realized by the "second supply unit".

(Fourth embodiment)
(In the case of AP connection; Fig. 16, Fig. 18)
The fourth embodiment is a modification of the third embodiment. The fourth embodiment is the same as the third embodiment, except that 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 processing of T726-T739B in FIG. That is, the printer 100 does not disconnect the L2CAP Link established in response to the connection start command of T712, but maintains the establishment of the Link, and performs APer "Readable with authentication (or Writeable with authentication)" of AC138C. is changed (T732).

When the application 38 receives the Write Response signal at T728, it executes the process at T800 as shown in FIG. T800 is the same as T402 in FIG. 12 except that encryption using a key is not performed.

When the printer 100 receives the Type_Req signal from the terminal 10 at T800, from among the data group contained within the range of Handles indicated by the first Handle "n5" and the last Handle "n13" contained in the signal, Identify the Handle "n10" corresponding to the UUID "bbb1" included in the Type_Req signal. Here, 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 encrypt information according to SMP, and as a result, in T802, an Error Response signal is sent to the terminal 10. FIG.

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

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

In this embodiment, it is assumed that the CPU 132 of the printer 100 has a relatively high processing power. If the CPU 132 has relatively high processing power, the CPU 132 can change the value in APer while maintaining the establishment of the L2CAP Link. For example, if the CPU 132 has relatively low processing power, the CPU 132 cannot change the value in APer while maintaining the establishment of the L2CAP Link. In such a case, as in the third embodiment, it is effective to employ a configuration in which the value in APer is changed after disconnecting the L2CAP Link. On the other hand, in the present embodiment, considering that the processing power of the CPU 132 is relatively high, the process of disconnecting the L2CAP Link and reestablishing the L2CAP Link is omitted, thereby suppressing execution of unnecessary processes. can do.

(correspondence relationship)
The L2CAP Link of T234 in FIG. 10 quoted in FIG. 16 is an example of the "second wireless connection". T882 in FIG. 18 is an example of processing implemented by the "first communication executing unit". T712 in FIG. 16 is an example of processing implemented by the "second supply unit".

(Fifth embodiment)
The fifth embodiment is the same as the first embodiment except that printing using BLE communication can be executed. 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 for accepting an instruction to execute encryption using a BLE key and transmit print data to the printer 100 . Also, although illustration is omitted, the PS group of this embodiment includes a PS for receiving print data from the terminal 10 (hereinafter referred to as "PPS") in addition to the PSs 138A to 138F. The PPS includes Characteristics that define the reception (ie, writing) of print data.

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

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

When the application 38 acquires the connection completion notification from the OS 36 at T380, the print screen is displayed on the display unit 12 at T390. Then, the application 38 receives a print operation from the user on the print screen.

At T390, the application 38 acquires the 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 the print data to the printer 100 via the OS 36. Send. Here, the print data in the signal is encrypted with the Key.

Upon receiving the Write Request signal from the terminal 10 at T392, the printer 100 decodes the information in the Write Request signal to acquire print data at T394. The printer 100 then prints an image corresponding to the image information in the print data according to the print settings in the print data.

According to this case, the terminal 10 can encrypt the print data with the Key and send 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 relationship)
The print function, the instruction to select the BLE connection button in the function screen, and the print data in 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 the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. Modifications of the above embodiment are listed below.

(Modification 1) The "function execution device" may not be the printer 100, but may be, for example, a scanner, a FAX device, or a multi-function device. For example, if 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. may Then, in T394, the scanner may perform scanning according to the scan settings in the scan request to generate scan data, encrypt the generated scan data with the Key, and transmit the encrypted data to the terminal 10. FIG. In this modified example, the function of transmitting scan data and the scan data are examples of the "first function" and the "first function execution information", respectively.

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

(Modification 3) The “first wireless interface” does not have to be the BTI/F, and performs wireless communication according to a communication method other than the BT method (eg, Zigbee (registered trademark) method, Wi-Fi method). It may be an I/F for execution. For example, if the "first wireless interface" is an I/F for performing 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 the function screen containing the character information indicated by the function information FI (T190). . Alternatively, the terminal 10 receives specific information (for example, model name) from the printer 100, and uses the received specific information to select the printer 100 from among the plurality of pieces of function information stored in the terminal 10. may be specified. Then, the terminal 10 may display a function screen including character information indicated by the specified function information FI. In this modified example, 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 input of the PIN code "1234" (T354). Instead, the printer 100 displays a code image (e.g., bar code, QR code (registered trademark)) in which the PIN code "1234" is coded, and the terminal 10 decodes the code image to generate the PIN You may get the code "1234". Also, the terminal 10 may acquire the PIN code “1234” from the IC tag of the printer 100 using NFC (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). Alternatively, 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.

(Modification 7) In the first embodiment described above, the printer 100 operates as the G/O, and the terminal 10 prepares the public key (T556 in FIG. 13). Alternatively, the terminal 10 may act as the G/O and the printer 100 may prepare the public key. The terminal 10 may then use the public key received from the printer 100 to encrypt the WFD information stored in the terminal 10 . Generally speaking, the 'specific authentication information' and the 'public key' may be prepared by one of the function execution device and the terminal device.

(Modification 8) A "specific Read request" may not be a Type_Req signal, but may be another signal defined by ATT (eg, Read Request signal, Read Blob Request signal, Read Multiple Request signal). good.

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

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

(Modification 11) In the first embodiment described above, the terminal 10 displays the error URL (T672 in FIG. 15). Alternatively, terminal 10 may display a message indicating an error condition. In this modified example, the message is an example of "error information". In addition, 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 select the printer error URLs from among the plurality of error URLs stored in the terminal 10. Error URLs corresponding to the 100 current error states may be identified. The terminal 10 may then display the identified error URL. In this modified example, the specific information is an example of "error display information".

(Modification 12) In the above fourth embodiment, the printer 100 receives the permission change instruction from the terminal 10 (T722 in FIG. 16) and changes the value in APer (T732). Alternatively, the printer 100 may receive a stop instruction for stopping transmission of the ADV signal from the terminal 10, and stop transmission of the ADV signal according to the received stop instruction. Then, the printer 100 may receive a Type_Req signal including the UUID "0x2A00" from the terminal 10 instead of T800 in FIG. As a result, APer indicates "Readable without authentication when discoverable" and the printer 100 is in the non-discoverable state, so authentication communication may be executed. 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 the first type PS (for example, T142A in FIG. 8) and a Type_Req signal to the second type PS (for example, T176A in FIG. 8). ). Alternatively, the OS 36 may only transmit the Type_Req signal to the first type PS and not transmit the Type_Req signal to the second type PS.

(Modification 14) The processing of T450 to T454 in FIG. 12 may not be executed. In this modified example, communication of "relational data" may not be executed.

(Modification 15) In the above-described third and fourth embodiments, the printer 100 sets each value indicating "Readable (or Writeable) without authentication" in the APer in the AP 138C 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) The OS 36 may be Android (registered trademark), for example. In this case, T138, T142A, T142C, T176A, T176C of FIG. 8, T242C of FIG. 10, T342C, T372 of FIG. 11, T652C of FIG. 15, T756A, T756C, T790 of FIG. 17, etc. are not executed. Therefore, in the fourth embodiment, for example, the process of T137 (the same applies to T137 to T178 in FIG. 8 referred to in FIG. 16) may not be executed. That is, since the OS 36 does not automatically acquire the PS group information in response to acquisition of the connection start command, transmission of the ADV signal does not have to be restarted. In this modification, since APer of FS138B indicates "Readable without authentication", for example, even if the Type_Req signal is received at T182 in FIG. No communication is performed. Then, authentication communication is executed (T802 to T880 in FIG. 18) due to APer of AC 138C being changed to "Readable with authentication" by T732 in FIG. In this modification, the APer of the FS 138B indicating "Readable without authentication" and the APer of the AC 138C indicating "Readable with authentication" are examples of the "first state" and the "second state", respectively. be. As a further modification, the APer corresponding to Handle "n1" of FS138B is "Readable without authentication" and unchanged, and the APer corresponding to Handle "n10" of AC138C is "Readable with authentication" and unchanged. good too. Then, the processes of T722, T724, and T732 in FIG. 16 may not be executed. In this modified example, the "setting change request" can be omitted.

(Modification 17) At T137 in FIG. 8, the printer 100 transmits an ADV signal including a connection disapproval parameter "ADV_NONCONN_IND". Alternatively, the printer 100 may send an ADV signal containing the connection permission parameter "ADV_IND". In this modified example, the "start part" can be omitted.

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

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

(Modification 20) The process of FIG. 15 may not be executed. In this modified example, the “fifth establishment unit” and the “third communication execution unit” can be omitted.

(Modification 21) In the first embodiment described above, the printer 100 changes the restart flag 162 from "ON" to "OFF" (T262 in FIG. 10) in order to perform authentication communication, and transmits the ADV signal. after stopping ADV signal transmission (T336 in FIG. 11). Alternatively, the printer 100 may keep the restart flag 162 "ON", stop sending the ADV signal, and then start sending an ADV signal that does not contain a predetermined value related to being in the Discoverable state. good. Even in this case, the state of the printer 100 becomes the non-discoverable state, and as a result, authentication communication is executed. In this modified example, a state in which an ADV signal that does not contain the predetermined value is being transmitted is an example of the "second state."

(Modification 22) 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, so that each of FIGS. Processing is realized. Alternatively, any processing may be implemented by hardware such as logic circuits.
The features of the technology disclosed in this specification are listed below.
(Item 1)
A function performing device,
a first wireless interface;
a first establishing unit that establishes a first wireless connection with a terminal device via the first wireless interface;
Using the first wireless connection without executing communication using specific authentication information prepared by one of the function execution device and the terminal device via the first wireless interface and transmitting screen display information for causing the terminal device to display a function screen showing one or more functions executable by the function execution device to the terminal device via the first wireless interface. Department and
When a first execution instruction for causing the function execution device to execute a first function is input to the terminal device after the function screen is displayed on the terminal device, the first wireless interface is enabled. a second establishing unit for establishing a second wireless connection with the terminal device via
a first communication executing unit that executes the communication using the specific authentication information with the terminal device via the first wireless interface using the second wireless connection;
communicating first function execution information for executing the first function with the terminal device via the first wireless interface after the communication using the specific authentication information is executed; a second communication execution unit that
A function performing device comprising:
(Item 2)
The function execution device according to item 1, wherein the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system.
(Item 3)
The function execution device further
A second wireless interface 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;
3. The function execution device according to item 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.
(Item 4)
the one or more functions include at least one of a print function and a scan 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 relevant data related to the at least one function with the terminal device. 4. The function-performing device according to item 3.
(Item 5)
the first function is at least one of a print function and a scan function;
3. The function executing device according to item 1 or 2, wherein the first function executing information includes relational data relating to the at least one function.
(Item 6)
The function execution device is
a first state in which the communication using the specific authentication information cannot be performed;
a second state in which the communication using the specific authentication information can be performed;
set to one of the states of
The transmission unit transmits the screen display information to the terminal device while the function execution device is set to the first state,
The function execution device further
When the first execution instruction is input to the terminal device, the terminal device changes the function execution device to the second state instead of the first state via the first wireless interface. A receiving unit that receives a setting change request for setting to
After the function execution device is set to the second state instead of the first state in response to receiving the setting change request from the terminal device, the first communication execution unit performs the 6. The function executing device according to any one of items 1 to 5, wherein the communication using specific authentication information is executed with the terminal device.
(Item 7)
The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
Establishing a third wireless connection with the terminal device via the first wireless interface after the first execution instruction is input to the terminal device and the first wireless connection is disconnected a third establishing unit that
with
The receiving unit uses the third wireless connection to receive the setting change request from the terminal device via the first wireless interface,
The function execution device further
a second disconnection unit that disconnects the third wireless connection when the setting change request is received from the terminal device;
The second establishing unit establishes the second wireless connection after the third wireless connection is disconnected,
Item 6, wherein the second communication execution unit communicates the first function execution information with the terminal device via the first wireless interface using the second wireless connection; A device for performing the described functions.
(Item 8)
The function execution device further
a disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The receiving unit uses the second wireless connection to receive the setting change request from the terminal device via the first wireless interface,
Item 6, wherein the second communication execution unit communicates the first function execution information with the terminal device via the first wireless interface using the second wireless connection; A device for performing the described functions.
(Item 9)
the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
9. The function execution device according to any one of items 6 to 8, wherein the first state includes a state in which the first wireless interface repeatedly transmits an Advertise signal according to the Bluetooth system.
(Item 10)
said communication using said specific authentication information when a specific Read request according to said Bluetooth system is received from said terminal device and said first wireless interface has stopped transmitting said Advertise signal; is executed and
When the specific Read request is received from the terminal device and the first wireless interface repeatedly transmits the Advertise signal, the communication using the specific authentication information is not executed,
The transmission unit receives the specific Read request from the terminal device while the function execution device is set to the first state in which the first wireless interface repeatedly transmits the Advertise signal. 10. The function execution device according to item 9, wherein, when the communication is performed using the specific authentication information, the screen display information is transmitted to the terminal device.
(Item 11)
The first establishing unit establishes the first wireless connection with the terminal device when a first Advertise signal is received by the terminal device;
the first Advertise signal includes permission information that permits establishment of a wireless connection according to the Bluetooth system;
The function execution device further
a stopping unit that causes the first wireless interface to stop transmitting the first Advertise signal when the first wireless connection with the terminal device is established;
an initiator that causes the first wireless interface to start transmitting a second Advertise signal after transmission of the first Advertise signal is stopped, wherein the second Advertise signal is in accordance with the Bluetooth scheme; the initiator including non-permission information that does not permit establishment of the wireless connection;
with
11. The function executing device according to item 10, wherein the first state includes a state in which the first wireless interface repeatedly transmits the second Advertise signal.
(Item 12)
the communication using the specific authentication information is performed when the first wireless interface has stopped transmitting the Advertise signal;
when the first wireless interface repeatedly transmits the Advertise signal, the communication using the specific authentication information is not executed;
the second state includes a state in which the first wireless interface has stopped transmitting the Advertise signal;
the setting change request is a request for not causing the first wireless interface to transmit the Advertise signal;
The transmission unit executes the communication using the specific authentication information while the function execution device is set to the first state in which the first wireless interface repeatedly transmits the Advertise signal. transmitting the screen display information to the terminal device without
The first communication execution unit receives the specific authentication information while the function execution device is set to the second state in which the first wireless interface stops transmitting the Advertise signal. 12. The function executing device according to any one of items 9 to 11, which executes the communication using the .
(Item 13)
the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
The first state includes a state in which first setting information is stored in memory;
The first setting information is set so that when a specific Read request conforming to the Bluetooth system is received from the terminal device, the specific Read request is sent without executing the communication using the specific authentication information. Indicates the settings for sending responses to
the second state includes a state in which second setting information is stored in the memory;
The second setting information executes the communication using the specific authentication information when the specific read request is received from the terminal device, and the authentication using the specific authentication information is successful. indicates a setting for sending the response to the specific Read request when
the setting change request is a request to change the first setting information in the memory to the second setting information;
The transmission unit executes the communication using the specific authentication information when the specific read request is received from the terminal device while the first setting information is stored in the memory. transmitting the screen display information to the terminal device as the response to the specific Read request without
The first communication executing 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. 12. A function performing device according to any one of items 6 to 11, for performing said communication.
(Item 14)
the specific authentication information is a first code prepared by the one of the function execution device and the terminal device;
The communication using the specific authentication information is performed by inputting a second code to the other of the function execution device and the terminal device after the first code is displayed on the one device. transmitting from the other device to the one device related information related to the second code, if
If the one device determines that the first code and the second code match after communication of the related information is executed, the second communication execution unit performs 14. The function execution device according to any one of items 1 to 13, which communicates the first function execution information with the terminal device via a wireless interface.
(Item 15)
the specific authentication information is a public key prepared by the one of the function execution device and the terminal device;
the communication using the specific authentication information includes transmitting the public key from the one device to the other of the function execution device and the terminal device;
5. The function execution device according to any one of items 1 to 4, wherein the first function execution information is information generated by the other device by using the public key.
(Item 16)
The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The first communication executing unit executes communication of the public key with the terminal device via the first wireless interface using the second wireless connection,
The function execution device further
a third disconnection unit that disconnects the second wireless connection after communication of the public key is performed with the terminal device;
a fourth establishing unit that establishes a fourth wireless connection with the terminal device via the first wireless interface after the second wireless connection is disconnected;
with
Item 15, wherein the second communication execution unit uses the fourth wireless connection to communicate the first function execution information with the terminal device via the first wireless interface; A device for performing the described functions.
(Item 17)
The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The first communication executing unit executes communication of the public key with the terminal device via the first wireless interface using the second wireless connection,
Item 15, wherein the second communication execution unit uses the second wireless connection to communicate the first function execution information with the terminal device via the first wireless interface; A device for performing the described functions.
(Item 18)
the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
The transmission unit transmits the screen display information without executing neither the communication using the public key, which is the specific authentication information, nor the communication using the specific code according to the Bluetooth system. send to the terminal device;
18. Function execution according to any one of items 15 to 17, wherein the first communication executing unit executes the communication using the public key without executing the communication using the specific code. Device.
(Item 19)
when the first wireless interface repeatedly transmits the Advertise signal according to the Bluetooth system, the communication using the specific code is not executed;
The transmitting unit, while the function execution device is set to a state in which the first wireless interface repeatedly transmits the Advertise signal, does not execute the communication using the specific code. sending screen display information to the terminal device;
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 Advertise signal. performing the communication using the public key without
The second 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 Advertise signal. 19. The function execution device according to item 18, which executes communication of the first function execution information with the terminal device.
(Item 20)
The function execution device further
When a second execution instruction for causing the function execution device to execute a second function different from the first function is input to the terminal device after the function screen is displayed on the terminal device , a fifth establishing unit that establishes a fifth wireless connection with the terminal device via the first wireless interface;
using the fifth wireless connection without executing the communication using the specific authentication information via the first wireless interface using the fifth wireless connection; a third communication execution unit that communicates second function execution information for executing the second function with the terminal device via one wireless interface;
20. A function-performing device according to any one of items 1 to 19, comprising:
(Item 21)
the second function is a function of transmitting error display information to the terminal device for displaying error information related to the error state to the terminal device when the function execution device is in an error state;
21. The function execution device according to item 20, wherein the third communication execution unit receives from the terminal device a request for transmitting the error display information to the terminal device as the second function execution information.
(Item 22)
A computer program for a terminal device, comprising:
The computer of the terminal device has the following parts, that is,
supplying an operating system (OS) program of the terminal device with a first instruction for establishing a first wireless connection with the function execution device via a first wireless interface of the terminal device; a supply of
Using the first wireless connection without executing communication using specific authentication information prepared by one of the function execution device and the terminal device via the first wireless interface Then, screen display information for displaying on the terminal device a function screen showing one or more functions executable by the function execution device is received from the function execution device via the first wireless interface. a receiver for
a display control unit that displays the function screen on a display unit of the terminal device when the screen display information is received from the function execution device;
When a first execution instruction for causing the function execution device to execute a first function is input to the terminal device after the function screen is displayed on the display unit, the first wireless interface is activated. a second supply unit for supplying the OS program with a second instruction for establishing a second wireless connection with the function execution device via the
after the communication using the specific authentication information is executed with the function execution device using the second wireless connection and via the first wireless interface, the first wireless interface; a communication execution unit that communicates function execution information for executing the first function with the function execution device via
A computer program that acts as a
(Item 23)
The computer program further causes the computer to:
When a second execution instruction for causing the function execution device to execute a second function different from the first function is input to the terminal device after the function screen is displayed on the terminal device , a specific establishing unit that establishes a specific wireless connection with the function execution device via the first wireless interface;
using the specific wireless connection without executing the communication using the specific authentication information via the first wireless interface using the specific wireless connection; 23. The computer program according to item 22, functioning as a specific communication execution unit that executes communication of second function execution information for executing the second function with the function execution device via a wireless interface. .
(Item 24)
the second function is a function of transmitting error display information to the terminal device for displaying error information related to the error state to the terminal device when the function execution device is in an error state;
24. The computer program according to item 23, wherein the specific communication execution unit transmits a request for transmitting the error display information to the terminal device as the second function execution information to the function execution device.

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 Unit, 114: Wireless LAN I/F, 116: BTI/F, 130: Control Unit, 132: CPU, 134: Memory, 136: Program, 138: Protocol Stack, 138A: GA, 138B : FS, 138C: AC, 138D: WD, 138E: BC, 138F: ES, 160: WFD information, 162: Resume flag, 200: AP, 300: Mobile terminal, 338: Application, 500: Printer, DN: Device name , FI: function information, IA: IP address

Claims (24)

A function performing device,
a first wireless interface;
a first establishing unit that establishes a first wireless connection with a terminal device via the first wireless interface;
Using the first wireless connection without executing communication using specific authentication information prepared by one of the function execution device and the terminal device via the first wireless interface and transmitting screen display information for causing the terminal device to display a function screen showing one or more functions executable by the function execution device to the terminal device via the first wireless interface. Department and
When a first execution instruction for causing the function execution device to execute a first function is input to the terminal device after the function screen is displayed on the terminal device, the first wireless interface is enabled. a second establishing unit for establishing a second wireless connection with the terminal device via
a first communication executing unit that executes the communication using the specific authentication information with the terminal device via the first wireless interface using the second wireless connection;
communicating first function execution information for executing the first function with the terminal device via the first wireless interface after the communication using the specific authentication information is executed; a second communication execution unit that
A function performing device comprising: 2. The function execution device according to claim 1, wherein said first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system. The function execution device further
A second wireless interface 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;
3. The function execution device according to claim 1, wherein said first function execution information includes information for establishing said wireless connection with said external device via said second wireless interface. the one or more functions include at least one of a print function and a scan 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 relevant data related to the at least one function with the terminal device. 4. A function-performing device according to claim 3, wherein a the first function is at least one of a print function and a scan function;
3. The function execution device according to claim 1, wherein said first function execution information includes relationship data related to said at least one function. The function execution device is
a first state in which the communication using the specific authentication information cannot be performed;
a second state in which the communication using the specific authentication information can be performed;
set to one of the states of
The transmission unit transmits the screen display information to the terminal device while the function execution device is set to the first state,
The function execution device further
When the first execution instruction is input to the terminal device, the terminal device changes the function execution device to the second state instead of the first state via the first wireless interface. A receiving unit that receives a setting change request for setting to
After the function execution device is set to the second state instead of the first state in response to receiving the setting change request from the terminal device, the first communication execution unit performs the 6. The function execution device according to claim 1, wherein said communication using specific authentication information is executed with said terminal device. The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
Establishing a third wireless connection with the terminal device via the first wireless interface after the first execution instruction is input to the terminal device and the first wireless connection is disconnected a third establishing unit that
with
The receiving unit uses the third wireless connection to receive the setting change request from the terminal device via the first wireless interface,
The function execution device further
a second disconnection unit that disconnects the third wireless connection when the setting change request is received from the terminal device;
The second establishing unit establishes the second wireless connection after the third wireless connection is disconnected,
7. The second communication execution unit uses the second wireless connection to communicate the first function execution information with the terminal device via the first wireless interface. A device for performing the functions described in . The function execution device further
a disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The receiving unit uses the second wireless connection to receive the setting change request from the terminal device via the first wireless interface,
7. The second communication execution unit uses the second wireless connection to communicate the first function execution information with the terminal device via the first wireless interface. A device for performing the functions described in . the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
9. The function execution device according to claim 6, wherein said first state includes a state in which said first wireless interface repeatedly transmits an Advertise signal according to said Bluetooth system. said communication using said specific authentication information when a specific Read request according to said Bluetooth system is received from said terminal device and said first wireless interface has stopped transmitting said Advertise signal; is executed and
When the specific Read request is received from the terminal device and the first wireless interface repeatedly transmits the Advertise signal, the communication using the specific authentication information is not executed,
The transmission unit receives the specific Read request from the terminal device while the function execution device is set to the first state in which the first wireless interface repeatedly transmits the Advertise signal. 10. The function execution device according to claim 9, wherein, when the terminal device is to be authenticated, the screen display information is transmitted to the terminal device without executing the communication using the specific authentication information. The first establishing unit establishes the first wireless connection with the terminal device when a first Advertise signal is received by the terminal device;
the first Advertise signal includes permission information that permits establishment of a wireless connection according to the Bluetooth system;
The function execution device further
a stopping unit that causes the first wireless interface to stop transmitting the first Advertise signal when the first wireless connection with the terminal device is established;
an initiator that causes the first wireless interface to start transmitting a second Advertise signal after transmission of the first Advertise signal is stopped, wherein the second Advertise signal is in accordance with the Bluetooth scheme; the initiator including non-permission information that does not permit establishment of the wireless connection;
with
11. The function executing device according to claim 10, wherein said first state includes a state in which said first wireless interface repeatedly transmits said second Advertise signal. the communication using the specific authentication information is performed when the first wireless interface has stopped transmitting the Advertise signal;
when the first wireless interface repeatedly transmits the Advertise signal, the communication using the specific authentication information is not executed;
the second state includes a state in which the first wireless interface has stopped transmitting the Advertise signal;
the setting change request is a request for not causing the first wireless interface to transmit the Advertise signal;
The transmission unit executes the communication using the specific authentication information while the function execution device is set to the first state in which the first wireless interface repeatedly transmits the Advertise signal. transmitting the screen display information to the terminal device without
The first communication execution unit receives the specific authentication information while the function execution device is set to the second state in which the first wireless interface stops transmitting the Advertise signal. 12. The function execution device according to any one of claims 9 to 11, wherein the communication is performed using a. the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
The first state includes a state in which first setting information is stored in memory;
The first setting information is set so that when a specific Read request conforming to the Bluetooth system is received from the terminal device, the specific Read request is sent without executing the communication using the specific authentication information. Indicates the settings for sending responses to
the second state includes a state in which second setting information is stored in the memory;
The second setting information executes the communication using the specific authentication information when the specific read request is received from the terminal device, and the authentication using the specific authentication information is successful. indicates a setting for sending the response to the specific Read request when
the setting change request is a request to change the first setting information in the memory to the second setting information;
The transmission unit executes the communication using the specific authentication information when the specific read request is received from the terminal device while the first setting information is stored in the memory. transmitting the screen display information to the terminal device as the response to the specific Read request without
The first communication executing 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. 12. A function performing device according to any one of claims 6 to 11, for performing said communication. the specific authentication information is a first code prepared by the one of the function execution device and the terminal device;
The communication using the specific authentication information is performed by inputting a second code to the other of the function execution device and the terminal device after the first code is displayed on the one device. transmitting from the other device to the one device related information related to the second code, if
If the one device determines that the first code and the second code match after communication of the related information is executed, the second communication execution unit performs 14. The function execution device according to any one of claims 1 to 13, wherein said first function execution information is communicated with said terminal device via a wireless interface. the specific authentication information is a public key prepared by the one of the function execution device and the terminal device;
the communication using the specific authentication information includes transmitting the public key from the one device to the other of the function execution device and the terminal device;
5. The function execution device according to claim 1, wherein said first function execution information is information generated by said other device by using said public key. The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The first communication executing unit executes communication of the public key with the terminal device via the first wireless interface using the second wireless connection,
The function execution device further
a third disconnection unit that disconnects the second wireless connection after communication of the public key is performed with the terminal device;
a fourth establishing unit that establishes a fourth wireless connection with the terminal device via the first wireless interface after the second wireless connection is disconnected;
with
16. The second communication execution unit uses the fourth wireless connection to communicate the first function execution information with the terminal device via the first wireless interface. A device for performing the functions described in . The function execution device further
a first disconnection unit that disconnects the first wireless connection after the screen display information is transmitted to the terminal device;
The second establishing unit establishes the second wireless connection after the first wireless connection is disconnected,
The first communication executing unit executes communication of the public key with the terminal device via the first wireless interface using the second wireless connection,
16. The second communication execution unit uses the second wireless connection to communicate the first function execution information with the terminal device via the first wireless interface. A device for performing the functions described in . the first wireless interface is an interface for performing wireless communication according to the Bluetooth (registered trademark) system;
The transmission unit transmits the screen display information without executing neither the communication using the public key, which is the specific authentication information, nor the communication using the specific code according to the Bluetooth system. send to the terminal device;
18. The function according to any one of claims 15 to 17, wherein said first communication execution unit executes said communication using said public key without executing said communication using said specific code. execution device. when the first wireless interface repeatedly transmits the Advertise signal according to the Bluetooth system, the communication using the specific code is not executed;
The transmitting unit, while the function execution device is set to a state in which the first wireless interface repeatedly transmits the Advertise signal, does not execute the communication using the specific code. sending screen display information to the terminal device;
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 Advertise signal. performing the communication using the public key without
The second 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 Advertise signal. 19. The function execution device according to claim 18, which executes communication of said first function execution information with said terminal device. The function execution device further
When a second execution instruction for causing the function execution device to execute a second function different from the first function is input to the terminal device after the function screen is displayed on the terminal device , a fifth establishing unit that establishes a fifth wireless connection with the terminal device via the first wireless interface;
using the fifth wireless connection without executing the communication using the specific authentication information via the first wireless interface using the fifth wireless connection; a third communication execution unit that communicates second function execution information for executing the second function with the terminal device via one wireless interface;
20. A function-performing device according to any one of claims 1 to 19, comprising a . the second function is a function of transmitting error display information to the terminal device for displaying error information related to the error state to the terminal device when the function execution device is in an error state;
21. The function execution device according to claim 20, wherein said third communication execution unit receives from said terminal device a request for transmitting said error display information to said terminal device as said second function execution information. A computer program for a terminal device, comprising:
The computer of the terminal device has the following parts, that is,
supplying an operating system (OS) program of the terminal device with a first instruction for establishing a first wireless connection with the function execution device via a first wireless interface of the terminal device; a supply of
Using the first wireless connection without executing communication using specific authentication information prepared by one of the function execution device and the terminal device via the first wireless interface Then, screen display information for displaying on the terminal device a function screen showing one or more functions executable by the function execution device is received from the function execution device via the first wireless interface. a receiver for
a display control unit that displays the function screen on a display unit of the terminal device when the screen display information is received from the function execution device;
When a first execution instruction for causing the function execution device to execute a first function is input to the terminal device after the function screen is displayed on the display unit, the first wireless interface is activated. a second supply unit for supplying the OS program with a second instruction for establishing a second wireless connection with the function execution device via the
after the communication using the specific authentication information is executed with the function execution device using the second wireless connection and via the first wireless interface, the first wireless interface; a communication execution unit that communicates function execution information for executing the first function with the function execution device via
A computer program that acts as a The computer program further causes the computer to:
When a second execution instruction for causing the function execution device to execute a second function different from the first function is input to the terminal device after the function screen is displayed on the terminal device , a specific establishing unit that establishes a specific wireless connection with the function execution device via the first wireless interface;
using the specific wireless connection without executing the communication using the specific authentication information via the first wireless interface using the specific wireless connection; 23. The computer according to claim 22, which functions as a specific communication executing unit that executes communication of second function execution information for executing said second function with said function executing device via a wireless interface. program. the second function is a function of transmitting error display information to the terminal device for displaying error information related to the error state to the terminal device when the function execution device is in an error state;
24. The computer program according to claim 23, wherein said specific communication execution unit transmits a request for transmitting said error display information to said terminal device as said second function execution information to said function execution device.

Images