Communication terminal and program

Abstract

To provide a mechanism to improve user convenience when logging in from a communication terminal to a surrounding external device.SOLUTION: A communication terminal 102 having a short-range radio communication function can transmit to an external device a log-in request by the short-range radio communication. Also, in communication terminal 102, it is possible to set whether a radio communication function is validated, as the operation setting of the communication terminal. On accepting a user operation to transfer to a screen to request the external device to log in and if an OFF setting to at least invalidate a short-range radio communication function is set, the communication terminal 102 controls to display a predetermined notification before displaying the log-in request screen.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present invention relates to a communication terminal that logs in to an external device via short-range wireless communication. [Background technology]

[0002] An image processing device provides a user with various functions such as a printing function, a copying function, and a file transmission function. When a user wishes to use a function provided by an image processing device, the user must log in to the image processing device. As a method for a user to log in to an image forming device, a method is known in which a communication terminal such as a mobile terminal transmits a login request to the image forming device when the communication terminal approaches the image processing device, thereby logging the user in to the image processing device (for example, see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-66217 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the series of login processes using a communication terminal shown in Patent Document 1, detailed control during login processes, such as guidance when a user logs in or notification of an error, is not disclosed. As such, there is a concern that the login process using a conventional communication terminal is difficult for users to understand. For example, the control sequence is not taken into consideration when the short-range wireless communication settings required for logging in to an image processing device are not correctly set in the communication terminal, and there may be cases where the user cannot understand why the login has failed.

[0005] The present invention has been made in consideration of at least one of the above problems, and aims to provide a mechanism for improving user convenience when logging in to a surrounding external device from a communication terminal.

[0006] Another object of the present invention is to provide a mechanism for preventing unnecessary user operations by notifying the user before making a login request when the settings used for login processing are not properly configured. [Means for solving the problem]

[0007] In order to achieve at least one of the above-mentioned objects, a communication terminal of the present invention is a communication terminal that transmits a login request to an external device, and is characterized in having: a short-range wireless communication means; a setting means that sets whether or not to enable a wireless communication function by the short-range wireless communication means as an operation setting of the communication terminal; and a display control means that, when a user operation to transition to a screen for making a login request to an external device is received, and at least if the setting means has not set the operation setting of the communication terminal to enable the wireless communication function by the short-range wireless communication means, controls to display a predetermined notification before displaying the screen for making the login request. Effect of the Invention

[0008] According to the present invention, it is possible to provide a mechanism for improving user convenience when logging in to a surrounding external device from a communication terminal.

[0009] In addition, as one aspect of the present invention, when the settings used for the login process are not properly configured, a mechanism can be provided that notifies the user before making a login request, thereby preventing unnecessary user operations. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an overview of a system. [Diagram 2] FIG. 2 illustrates an example of a hardware configuration of a communication terminal 102. [Diagram 3] FIG. 2 is a diagram illustrating an example of a software configuration of a communication terminal 102. [Figure 4] FIG. 2 is a diagram illustrating an example of the hardware configuration of an MFP 101. [Diagram 5] 2 is a diagram illustrating an example of a screen displayed on an operation unit of the communication terminal 102. FIG. [Figure 6] 2 is a diagram illustrating an example of a screen displayed on an operation unit of the communication terminal 102. FIG. [Figure 7] 2 is a diagram illustrating an example of a screen displayed on an operation unit of the communication terminal 102. FIG. [Figure 8] 4 is a flowchart showing the control of the communication terminal 102. [Figure 9] 4 is a flowchart showing the control of the communication terminal 102. [Figure 10] 4 is a flowchart showing the control of the communication terminal 102. [Figure 11] 4 is a flowchart showing the control of the MFP 101. [Figure 12] FIG. 1 is a diagram for explaining data communication using BLE. [Figure 13] 1A and 1B are diagrams illustrating an example of a screen displayed on an operation unit of the MFP 101. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiments for carrying out the present invention will be described with reference to the drawings. Note that the following embodiments do not limit the invention according to the claims, and all of the combinations of features described in the embodiments are not necessarily essential to the solution of the invention.

[0012] <First embodiment> First, the configuration of a communication system according to the present invention will be described with reference to Fig. 1. The system according to this embodiment includes a communication terminal 102, an MFP (Multi Function Peripheral) 102, and an AP (Access Point) 103.

[0013] The communication terminal 102 is capable of performing wireless communication based on the IEEE 802.11 standard (hereinafter referred to as the 802.11 standard). When a user inputs an SSID (Service Set Identifier) ​​and a security key for connecting to the AP 103 into the communication terminal 102, the communication terminal 102 can connect to a network provided by the AP 103.

[0014] The MFP 101 is a multi-function device having functions such as scanning, printing, copying, etc. When an SSID and a security key for connecting to the AP 103 are set as the wireless network settings of the MFP 101, the communication terminal 102 and the MFP 101 can perform wireless communication via the AP 103. The MFP 101 can receive print data from the communication terminal 102 via wireless communication and perform printing.

[0015] Moreover, from the viewpoint of security, the MFP 101 of this embodiment can perform user authentication management on the premise of a user logging in. When a user is not logged in, an MFP with user authentication management set to ON displays a login screen on the operation unit, and each function of the MFP 101 becomes unavailable. The MFP 101 determines whether or not to permit the user's login based on user authentication information (also called user credentials) received from the user in a state in which the login screen is displayed. When the user's login is permitted, the MFP 101 displays a main screen (also called a main menu) on the operation unit of the MFP. The user becomes able to use each function of the MFP, such as a copy or transmission function, via the main screen displayed on the operation unit. Hereinafter, in this embodiment, having a user log in and transitioning to a state in which each function of the MFP can be used via the operation unit of the MFP is referred to as local login.

[0016] The communication system of the present embodiment also includes a mobile link function that provides functions to a user by linking the communication terminal 102 and the MFP 101. For example, a user who owns a communication terminal can execute a linked login function that logs a specific user into the MFP 101 by bringing the communication terminal 102 close to the MFP 101. The communication terminal 102 can perform data communication with the MFP 101 using short-range wireless communication. For example, the communication terminal 102 performs data communication related to the linked login using short-range wireless communication.

[0017] In addition, a scan cooperation function can be executed in which the MFP 101 and the communication terminal 102 cooperate to scan a paper document and transmit or store it. Also, a print release function can be executed in which a print instruction is issued from an operation unit of the communication terminal 102 to print data reserved in the MFP 101.

[0018] The communication terminal 102 communicates with the MFP 101 via the AP 103. For example, the communication terminal 102 can transmit and receive print data and scan data to and from the MFP 101 via the AP 103.

[0019] Furthermore, the MFP 101 can also operate in an access point mode. When operating in the access point mode, the MFP 101 operates as a software access point. By connecting to a software AP provided by the MFP 101, the communication terminal 102 can execute direct wireless communication with the MFP 101 without going through a relay device such as the AP 103. By connecting to the MFP 101 using direct wireless communication with the MFP 101, the communication terminal 102 can execute various linking functions without going through the AP 103.

[0020] In this embodiment, a smartphone and a tablet PC (Personal Computer) are exemplified as examples of communication terminals, but the present invention is not limited to these. A smartphone and a tablet PC are examples of communication terminals capable of performing short-range wireless communication, and other communication terminals such as a wearable device may also be used.

[0021] In addition, in this embodiment, an MFP is exemplified as an example of an external device that cooperates with a communication terminal, but the present invention is not limited to this. For example, the present invention can be applied to a case where a user logs in to a single-function scanner, printer, 3D printer, etc. In addition, the present invention can be applied to a terminal of a remote conference system, a car navigation device, an interactive whiteboard, and other home appliances, etc.

[0022] <Communication terminal> 2, a hardware configuration of the communication terminal 102 will be described. A CPU (Central Processing Unit) 111 included in a control unit 110 reads out a control program stored in a ROM (Read Only Memory) 112 or a storage 114 to control the communication terminal 102.

[0023] The control unit 110 includes a CPU 111, a ROM 112, a RAM (Random Access Memory) 113, a storage 114, an operation unit I / F 115, and a camera I / F 117, all connected to a bus. The control unit 110 also has a wireless LAN I / F (interface) 122 and a Bluetooth (registered trademark) I / F 123 as communication interfaces for communicating with an external device. In this embodiment, the wireless LAN I / F 122 and the Bluetooth I / F 123 are described as separate hardware, but are not limited to this. A combo chip that realizes both wireless communication by wireless LAN and short-distance wireless communication by Bluetooth with one hardware may be mounted to realize wireless communication by wireless LAN and short-distance wireless communication by Bluetooth.

[0024] The CPU 111 is a central processing unit (processor) that controls the overall operation of the control unit 110. The RAM 113 is a volatile memory, and is used as a work area, and a temporary storage area for expanding various control programs stored in the ROM 112 and the storage 114.

[0025] The ROM 112 is a non-volatile memory and stores a boot program and the like of the communication terminal 102. The storage 114 is a non-volatile flash memory having a larger capacity than the RAM 113. The storage 114 stores a control program for the communication terminal 102. The storage 114 also stores an OS (Operating System) 300 and a cooperative application 310, which will be described later.

[0026] When the communications terminal is started up, the CPU 111 executes a boot program stored in the ROM 112. This boot program is for reading out the program of the OS 300 stored in the storage 114 and expanding it on the RAM 113. After executing the boot program, the CPU 111 subsequently executes the program of the OS 300 expanded on the RAM 113 and controls the communications terminal 102. The CPU 111 also stores data used for operations according to the control program on the RAM 113 and reads and writes it.

[0027] In addition, in the communication terminal 102, one CPU 111 executes each process shown in the flowcharts described later, but other configurations are also possible. For example, it is also possible for multiple CPUs or microprocessors (MPUs) to cooperate with each other to execute each process shown in the flowcharts described later. Also, some of the processes may be executed using a hardware circuit such as an ASIC (Application Specific Integrated Circuit).

[0028] The operation unit I / F 115 connects the operation unit 116 and the control unit 110. The operation unit 116 is equipped with a touch panel capable of detecting a user's touch operation and a display panel for displaying various screens. The operation unit 116 functions as a display unit for displaying information and a reception unit for receiving instructions from the user. Various screens provided by the OS 300 and the cooperative application 310 are displayed on the operation unit 116. In addition, the user can input a desired operation instruction to the communication terminal 102 by performing a touch operation on the operation unit 116 using an object such as a finger. The operation unit 116 is also equipped with a hardware key. The user can also input an operation instruction to the communication terminal 102 by pressing the hardware key.

[0029] The camera I / F 117 connects the control unit 110 and the camera 118. The camera 118 captures an image in response to an image capture instruction from a user. The photograph captured by the camera 118 is stored in a predetermined area of ​​the storage 114.

[0030] The wireless LAN I / F 122 provides a wireless client function for performing wireless communication conforming to the 802.11 standard. The wireless LAN I / F 122 also connects to an external AP to perform wireless communication conforming to the 802.11 standard. The external AP may be the MFP 101 operating in an access point mode or the AP 103.

[0031] The Bluetooth I / F 123 is an interface for transmitting and receiving data to and from various peripheral devices through short-range wireless communication. In the present embodiment, as an example, a linked login function for logging in a specific user to the MFP 101 is executed using wireless communication compliant with Bluetooth (IEEE802.15.1), particularly Bluetooth Low Energy (hereinafter, BLE).

[0032] <Software Configuration of Communication Terminal 102> Next, the software configuration of the communication terminal 102 will be described with reference to Fig. 3. Fig. 3 is a functional block diagram of software that is realized when the CPU 111 reads out a control program stored in the ROM 112 or storage 114.

[0033] The OS 300 is basic software for controlling the overall operation of the communication terminal 102. The OS 300 is configured, for example, with Android (registered trademark) provided by Google Inc. or iOS (registered trademark) provided by Apple Inc.

[0034] Various applications, including a cooperative application 310 described later, can be installed in the communication terminal 102. The OS 300 exchanges information with these applications, and can change the screen displayed on the operation panel 205 according to instructions received from the applications.

[0035] The OS 300 has a framework for controlling the hardware of the communication terminal 102 from various applications, and provides functions for utilizing various hardware to applications running on the OS 300. The OS 300 also has a Bluetooth control unit 301 and a wireless network control unit 302 for controlling various hardware from the applications. The Bluetooth control unit 301 interprets instructions from the applications, controls the Bluetooth I / F 123, and controls short-range wireless communication with external terminals.

[0036] For example, when data transmission / reception with an external device (e.g., MFP 101) is performed through BLE communication, the cooperative application 310 requests the OS 300 to perform data transmission / reception with the external device through BLE communication. Upon receiving the request, the Bluetooth control unit 301 of the OS 300 controls the Bluetooth I / F 123 to realize BLE communication. Furthermore, the Bluetooth control unit 301 cooperates with the Bluetooth I / F 123 to derive a received signal strength (RSSI: Received Signal Strength Indication) of Bluetooth received from an external device. Each application refers to the derived received signal strength by calling a function provided by the OS 300.

[0037] Furthermore, the cooperative application 310 can call functions provided by the OS as an API (Application Program Interface) or a framework for applications. By calling the functions, the cooperative application 310 can switch the AP with which the wireless LAN I / F 122 communicates, and control transmission and reception of data via wireless communication conforming to IEEE802.11. The wireless network control unit 302 controls the wireless LAN I / F 122 based on instructions from the application, and controls wireless communication with an external terminal.

[0038] The cooperative application 310 stores information indicated by 311 and 312 as internal information. The user authentication information 311 is user authentication information used for a login request to the MFP 101. These pieces of user authentication information are set via a setting screen of the cooperative application 310. The device list information 312 stores external devices such as MFPs that are to be coordinated by the cooperative application 310. The device list stores management information of the external devices including the device names, capabilities, and connection information for connecting to the external devices of the external devices registered by user operations. The cooperative application 310 can register external devices such as MFPs in the device list by accepting a search process for MFPs by the user or manual input. When the cooperative application 310 accepts a user operation to select an external device such as MFP registered in the device list from a selection screen (not shown), the cooperative application 310 changes the external device to be the coordinated device to the selected external device.

[0039] <mfp> Next, a description will be given of the MFP 101. Fig. 4 is a block diagram showing the hardware configuration of the MFP 101. The MFP 101 has a reading function for reading an image and a printing function for printing an image on a sheet.

[0040] The control unit 130 including the CPU 131 controls the overall operation of the MFP 101. The CPU 131 reads out a control program stored in the ROM 132 or the storage 134, and performs various controls such as print control and read control. The ROM 132 stores a control program executable by the CPU 131. The RAM 133 is the main storage memory of the CPU 131, and is used as a work area or a temporary storage area for expanding the commands of the various control programs. The storage 134 is a storage unit that stores print data, image data, various programs, and various setting information. The storage 134 also stores a user management database for performing user authentication management.

[0041] In the MFP 101 of this embodiment, one CPU 131 executes each process shown in the flowcharts described later using one memory (RAM 133), but other configurations are also possible. For example, each process shown in the flowcharts described later can be executed by using multiple processors, RAMs, ROMs, and storages in cooperation with each other.

[0042] The operation unit I / F 135 connects the operation unit 136 and the control unit 130. The operation unit 136 is provided with a liquid crystal display unit having a touch panel function, various hard keys, and the like, and functions as a display unit that displays information and a reception unit that receives user instructions.

[0043] The reading unit I / F 137 connects the reading unit 138 and the control unit 130. The reading unit 138 reads an original document and generates a read image. The generated read image is sent to an external device or used for printing.

[0044] A printing unit I / F 139 connects a printing unit 140 and the control unit 130. The printing unit 140 prints an image on a sheet based on print data received from an external source.

[0045] The control unit 130 is also connected to a network (not shown) via a wired LAN I / F 141. The wired LAN I / F 141 transmits images and information to an external device on the network (not shown) and receives print data and information from the external device.

[0046] Furthermore, the control unit 130 includes a wireless LAN I / F 142 and a Bluetooth I / F 143. The wireless LAN I / F 142 provides a wireless client function for connecting to an external AP and performing wireless communication, and a software AP function in which the MFP 101 behaves as an AP.

[0047] The Bluetooth I / F 143 is an interface for transmitting and receiving data to and from various peripheral devices through short-range wireless communication. The MFP 101 of this embodiment communicates with the communication terminal 102 using short-range wireless communication conforming to BLE, and executes a linked login function for logging in the user to the MFP 101 using the communication terminal 102.

[0048] <Linked login function> Next, the linked login function of the present embodiment will be described. Conventionally, a method has been considered in which a communication terminal and an MFP cooperate to allow a user to log in to the MFP, but detailed control that takes user convenience into consideration has not been considered in a series of login processes using a conventional communication terminal. For example, a control sequence such as when the short-range wireless communication settings required for logging in to the MFP are not correctly set in the communication terminal is not taken into consideration, and a case may arise in which the user cannot understand why the login has failed.

[0049] In consideration of the above problems, in this embodiment, it is possible to improve user convenience by performing detailed control that was not fully taken into account in a series of login processes using a conventional communication terminal.

[0050] First, an overview of the cooperative application 310 of the communication terminal 102 will be described. Fig. 5 to Fig. 7 show examples of screens displayed on the operation unit 116 of the communication terminal 102. Fig. 5(a) to (d) show examples of screens provided to the user by the cooperative application. When an icon of the cooperative application is selected by a user operation via an application list screen (also called a drawer) or a home screen of the communication terminal 102, the CPU 111 starts the cooperative application 310. When the start-up process is completed, the cooperative application 310 displays a top menu screen shown in Fig. 5(a) on the screen of the communication terminal 102.

[0051] First, the functions of the cooperative application 310 will be described using the top menu screen. In the area 501, the currently selected MFP to be linked is displayed. In the present embodiment, a case where the MFP 101 is designated as the linked destination is illustrated as an example. By selecting the area 501, the user can change the linked MFP or check the status and capabilities of the linked MFP. The add key 503 is a key that provides a function of registering a new MFP to be linked. The user can use the add key 503 to register a new MFP to be linked. The cooperative application 310 stores information on the MFP that is instructed to be registered as a linked destination by a user operation in the device list information 312. The registered MFP can be selected as a linked MFP thereafter.

[0052] The cooperative application 310 can execute various cooperative functions in cooperation with an MFP (e.g., MFP 101) designated as a cooperative destination. For example, cooperative functions such as print cooperation and scan cooperation can be executed. The document key is a key used when transmitting image data or document data stored in the communication terminal to the cooperative destination MFP and printing. The scan key is a key used when executing a scan cooperative function that scans an original in the cooperative destination MFP and captures the scanned data in the storage 114 of the communication terminal. The capture key is a key used when capturing an image of a document, a whiteboard, or the like using the camera 118. The print release key is a key used when issuing a print instruction for print data reserved in the MFP 101 from the operation unit of the communication terminal 102.

[0053] Key 502 is a key used when executing a linked login function that allows a specific user to log in. When key 502 is selected, the linked application 310 transitions the screen displayed on the operation unit 116 to a panel login screen shown in FIG.

[0054] The panel login screen displays MFPs around the communication terminal 102. In an area 511, information indicating MFPs that are candidates for login destinations that the cooperative application 310 has determined to be around the communication terminal 102 is displayed in a list.

[0055] Also, on the panel login screen, information is displayed that prompts the user to bring the communication device closer to the external device to which the user wishes to log in. Therefore, in this embodiment, it is possible to visually notify a user who wishes to use the linked login function that there is an external device nearby that is a candidate for the linked login function. Also, the information indicating the MFP includes a reception level that indicates the strength of the received signal. Therefore, in a case where a user approaches an MFP to which the user wishes to log in but is unable to find a candidate for a login destination with a high reception level, it is possible to suggest to the user that the user cannot log in to the MFP.

[0056] The cooperative application 310 determines whether or not there is an MFP that is a candidate for a login destination in the vicinity of the communication terminal 102 based on BLE advertising packets sent by a surrounding external device (e.g., MFP 101) at a predetermined interval (e.g., 30 millisecond intervals).

[0057] The advertising packet sent by the MFP 101 includes, for example, the information shown in Table 1.

[0058] [Table 1]

[0059] The cooperative application 310 refers to the Local Name and Manufacturer Specific Data included in the advertising packet of the received Bluetooth radio wave. Based on the information obtained by referring to the Local Name and Manufacturer Specific Data, the cooperative application 310 extracts external devices that it supports from among the external devices that are transmitting advertising packets and displays the extracted devices on the panel login screen. That is, even if the cooperative application 310 receives an advertising packet sent from an external device that cannot provide a login function, the cooperative application 310 controls so that the advertising packet is not displayed in the area 511.

[0060] The sensitivity adjustment key 512 is a key used to adjust the sensitivity of Bluetoothn. For example, when the connection to the MFP is unstable, the user can select the sensitivity adjustment key 512 to adjust the sensitivity of Bluetoothn. This function allows the user to calibrate the threshold value used to determine whether the communication terminal 102 is in proximity to the MFP, taking into consideration individual differences in the Bluetooth I / F of the communication terminal 102, the material of the housing, the influence of the protective case, the surrounding radio wave environment, and the like. When the sensitivity adjustment key is selected, the cooperative application 310 displays a sensitivity adjustment screen shown in FIG. 7(a). Information 701 indicating a method for performing sensitivity adjustment is displayed on the sensitivity adjustment screen. When the OK key 702 is selected, the sensitivity adjustment of Bluetoothn is performed.

[0061] Returning to Fig. 5, a method for executing a linked login will be described. When the linked application 310 determines that the communication terminal 102 is sufficiently close (proximity) to the MFP 101 that transmits an advertising packet, it transmits a login request to the MFP 101. The MFP 101 that accepts the login request determines whether or not to permit the login based on the login request. The MFP 101 notifies the communication terminal 102 of the login result via BLE communication. If the login is successful, the linked application 310 displays a login success screen shown in Fig. 5(c), and if the login is unsuccessful, it displays an authentication error screen shown in Fig. 5(d).

[0062] Pop-up 521 is information indicating that login has been successful. Pop-up 531 is a notification indicating that login has failed, and is information suggesting to the user that they should recheck the settings or status of communication terminal 102 or MFP 101.

[0063] In this way, the user can log in to the MFP 101 simply by bringing the communication terminal 102 close to the MFP 101. After the user logs in, a main screen is displayed on the operation unit 136 of the MFP 101. FIG. 13 shows an example of a screen displayed on the operation unit 136 of the MFP 101, and FIG. 13(a) shows an example of the main screen. A user who has executed the linked login function described with reference to FIG. 5 can use each function of the MFP 101 via the operation unit 136 of the MFP 101. This function allows the user to log in to the MFP simply by holding the communication terminal he or she owns over the MFP. This reduces the effort required for entering a user ID and password when logging in to the MFP.

[0064] Furthermore, in this embodiment, more detailed control is performed in addition to the basic login control described with reference to Fig. 5. A specific control method will be described below with reference to the flowcharts of Figs.

[0065] 8 to 10 are flowcharts showing the control of the communication terminal 102. Each operation (step) shown in the flowcharts of Fig. 8 to 10 is realized by the CPU 111 reading into the RAM 113 a program for implementing each control module stored in the ROM 112 or the storage 114 and executing it. Note that the processing shown in the flowcharts is realized mainly by the cooperative application 310 in cooperation with the OS 300, which is a control program. Note that when clearly indicating the control program that is the main entity that causes each operation, each operation will be described with the OS 300 or the cooperative application 310 as the main entity.

[0066] Moreover, Fig. 11 is a flowchart showing the control of MFP 101. Each operation shown in the flowchart of Fig. 11 is realized by CPU 131 reading into RAM 133 a program for implementing each control module stored in ROM 132 or storage 134 and executing the program.

[0067] 8 is a flowchart showing the operation of the communication terminal 102 when an icon of a cooperative application is selected via a drawer or a home screen of the communication terminal 102. In S801, the CPU 111 displays a top menu screen on the operation unit 116. In S802, the CPU 111 determines whether or not a user instruction to use the cooperative login function has been accepted. If a user instruction to use the cooperative login function has been accepted, the process proceeds to S803. If a user instruction to use the cooperative login function has not been accepted, the process proceeds to S804. A user operation to use the cooperative login function is, for example, an operation of selecting the key 502 displayed on the top menu screen of FIG. 5(a). Details of the cooperative login process in S803 will be described later. When the cooperative login process is completed in S803, the CPU 111 transitions the screen displayed on the operation unit 116 to the top menu screen, and returns to the process of S801.

[0068] In S804, the CPU 111 determines whether a user instruction to use another function has been received. If a user instruction to use another function has been received, the process proceeds to S805. If a user instruction to use another function has not been received, the process proceeds to S806. In S805, the CPU 111 executes another function based on the user instruction. For example, the CPU 111 can execute a print cooperation function in which image data or document data stored in the communication terminal 102 is transmitted to a cooperation destination MFP and printed. Also, the CPU 111 can execute a scan cooperation function in which the MFP 101 and the communication terminal 102 cooperate to scan a paper document and transmit or store the scanned data. Also, for example, the CPU 111 can execute a print release function in which a print instruction is issued from an operation unit of the communication terminal 102 to the print data reserved in the MFP 101. When the execution of the function based on the user instruction is completed, the CPU 111 transitions the screen displayed on the operation unit 116 to a top menu screen and returns to the process of S801.

[0069] Next, in S806, CPU 111 determines whether or not an instruction to end the application has been received. If an instruction to end the application has been received, CPU 111 stops execution of cooperative application 310, transitions the screen displayed on operation unit 116 to a home screen provided by the OS home application, and ends the series of controls. On the other hand, if an instruction to end the application has not been received, the process returns to S801.

[0070] In this manner, with the cooperative application 310 running, the user can execute various cooperative functions including the cooperative login function.

[0071] Next, specific control of the linked login function will be described with reference to Fig. 9. The flowchart in Fig. 9 describes exception processing when the linked login function cannot be executed due to settings or status on the communications terminal 102 side.

[0072] In S901, the CPU 111 determines whether or not the wireless communication function using the Bluetooth I / F 123 is enabled as an operation setting of the communication terminal 102. The cooperative application 310 inquires of the OS 300 whether or not the wireless communication function is enabled. If it is determined based on the result of the inquiry that the wireless communication function is enabled, the process proceeds to S904. If it is determined based on the result of the inquiry that the wireless communication function is not enabled (i.e., disabled), the process proceeds to S902.

[0073] In S902, the CPU 111 displays an error notification screen related to the Bluetooth function. Fig. 6C shows an example of the error notification screen displayed in S902. The error notification screen displays a pop-up 621 notifying the user that the Bluetooth of the communication terminal 102 should be turned on.

[0074] In S903, the CPU 111 switches the screen displayed on the operation unit 116 to a Bluetooth setting screen provided by the OS. Specifically, when the cooperative application 310 accepts the selection of the OK key by the user, it requests the OS 300 to transition the screen displayed on the operation unit 116 to a Bluetooth setting screen provided by the OS. The OS 300 switches the screen displayed on the operation unit 116 to the Bluetooth setting screen while the cooperative application 310 is running in the background. The user can change the setting of the wireless communication function using the Bluetooth I / F 123 to enable (on) or disable (off) via the Bluetooth setting screen. Note that, in the present embodiment, as an example, the screen transitions to the setting screen of the OS after the pop-up of S902 is displayed, but is not limited to this. The screen transitions to the setting screen of the OS of S903 without displaying the pop-up of S902 may be performed.

[0075] When the OS 300 receives an operation to return from the setting screen to the original screen (for example, a user operation to close the setting screen), the OS 300 switches the screen displayed on the operation unit 116 to the screen of the cooperative application 310. The cooperative application 310 transitions the screen displayed on the operation unit 116 to the top menu screen, and ends the process of S803.

[0076] Through the processing of S902 to S903, the user can enable the wireless communication function that uses the Bluetooth I / F 123 simply by performing operations following a series of screen transitions provided by the cooperative application 310.

[0077] Next, in S904, the CPU 111 determines whether or not user authentication information is set. If the user authentication information is set in the user authentication information 311 of the cooperative application 310, the CPU 111 advances the process to S908. On the other hand, if the user authentication information is not set in the user authentication information 311 of the cooperative application 310, the CPU 111 advances the process to S905.

[0078] In S905, the CPU 111 displays an error screen notifying the user that the user information has not been set. Fig. 6B shows an example of the error screen displayed in S905. The error screen displays a pop-up 611 notifying the user that the user information needs to be set.

[0079] In S906, when the CPU 111 accepts the selection of the OK key by the user, it switches the screen displayed on the operation unit 116 to a user information setting screen. Fig. 7B illustrates an example of the user information setting screen provided by the cooperative application 310 and displayed in S906.

[0080] The user can input user authentication information in area 711 to set the user authentication information. In S911, CPU 111 accepts the input of user authentication information. When the OK key is selected, CPU 111 updates user authentication information 311 based on the user authentication information input in area 711. When the update is complete, CPU 111 transitions the screen displayed on operation unit 116 to a top menu screen, and ends the processing of S803. Through these processing steps S905 to S907, the user can perform user authentication settings required for the linked login function by following a series of screen transitions.

[0081] In S908, the CPU 111 determines whether or not there is an external device registered as a link destination. If one or more pieces of management information are stored in the device list information 312 of the link application 310, the process proceeds to S912. On the other hand, if one or more pieces of management information are not stored in the device list information 312 of the link application 310, the process proceeds to S909.

[0082] In S909, the CPU 111 displays an error screen notifying the user that there is no MFP registered as a linked destination. Fig. 6D shows an example of the error screen displayed in S909. The error screen displays a pop-up 631 notifying the user that an MFP needs to be registered as a linked destination.

[0083] In S910, when the CPU 111 accepts the selection of the OK key by the user, it switches the screen displayed on the operation unit 116 to a registration screen for registering a nearby MFP as a cooperation destination. Fig. 7(c) illustrates an example of the registration screen for registering a nearby MFP provided by the cooperation application 310 and displayed in S910.

[0084] The registration screen displays items indicating MFPs around communication terminal 102. Here, an example is shown in which MFP 101 and MFP 102, which is an external device other than MFP 101, are found by searching advertising packets. The user can select item 721 or 722 to register the MFP corresponding to the selected item as a linked external device.

[0085] Returning to the explanation of FIG. 9, in S911, the CPU 111 accepts registration processing of an external device based on a user operation via a registration screen. The CPU 111 stores information on the MFP for which an instruction to register as a link destination has been given in device list information 312 managed by the link application 310. The registered MFP can be selected as a link destination MFP thereafter. In addition, in the series of registration processing, a pairing process between BLE devices is performed, and a Long Term Key (LTK), which is an encryption key for keeping communication between the devices secure, is exchanged. This process can reduce the effort of inputting a Personal Identification Number (PIN) code required for pairing in subsequent BLE communication.

[0086] When the registration process is completed, the CPU 111 transitions the screen displayed on the operation unit 116 to the top menu screen, and ends the process of S803.

[0087] If there is no MFP to be linked that has been registered in advance by the processing of S909 to S912, processing can be performed to register the MFP to be used as the link destination before using the login link function. In addition, because pairing between devices is performed in advance in a series of registration processes, it is possible to prevent the need to enter a PIN code when performing the subsequent link login processing using BLE communication.

[0088] In cases where the processing of each of the above steps makes it possible to determine in advance that the settings to be used for login processing are not appropriate, the user can be notified at a stage prior to searching for nearby external devices, thereby preventing unnecessary user operations.

[0089] Next, in S912, control is executed regarding a search for an actual surrounding external device and a login process. The process of S912 will be described with reference to the flowchart of FIG.

[0090] In S1001, the CPU 111 displays the panel login screen described in FIG. 5B. In S1002, the CPU 111 starts receiving radio waves of BLE communication. Specifically, the cooperative application 310 requests the OS 300 to start receiving radio waves of BLE communication in order to receive radio waves of BLE communication. The OS 300 controls the Bluetooth I / F 123 via the Bluetooth control unit 301 to start receiving Bluetooth advertising packets. The OS 300 notifies the cooperative application 310 of the received Bluetooth advertising packet and the reception signal strength of the advertising packet. The cooperative application 310 temporarily stores the received advertising packet and the reception strength of the packet.

[0091] In S1003, the CPU 111 determines whether or not an MFP with a received signal strength equal to or greater than Near has been detected. In this embodiment, for example, Near is defined as a received signal strength that is assumed to be approximately 3 m away from the MFP 101 and the communication terminal 102. If the packet is transmitted from a supported MFP based on the analysis result of the advertising packet and the received signal strength of the packet is equal to or greater than Near, the cooperative application 310 advances the process to S1004. On the other hand, if the packet is transmitted from an unsupported external device or the received signal strength of the advertising packet is less than Near, the cooperative application 310 skips the process of S1004 and advances the process to S1005.

[0092] In S1004, CPU 111 displays information indicating the MFP to be logged in on the panel login screen displayed in S1001. When advertising packets with received signal strengths of Near or higher are received from multiple MFPs, information indicating the multiple MFPs is displayed. Note that the priority order for displaying the information may be appropriately changed, for example, to the order of received signal strength.

[0093] In S1005, CPU 111 determines whether or not an MFP with a received signal strength equal to or greater than Touchlike has been detected. In this embodiment, Touchlike is defined as a received signal strength that is assumed to be approximately 3 cm away from MFP 101 and communication terminal 102, for example. If, based on the analysis result of the advertising packet, it is determined that the packet was sent from a supported MFP and the received signal strength of the packet is equal to or greater than Touchlike, cooperative application 310 advances the process to S1008. On the other hand, if the packet was sent from an unsupported external device or the received signal strength of the advertising packet is less than Touchlike, the process advances to S1006.

[0094] It is assumed that the Touchlike and Near thresholds have been calibrated in advance for the communication terminal 102 by the sensitivity adjustment function described in Fig. 7(a). If sensitivity adjustment has never been performed, the initial values ​​set when the application was installed are used.

[0095] In S1006, the CPU 111 determines whether a certain time has elapsed since the start of BLE radio wave reception. If the certain time has elapsed since the start of BLE radio wave reception, the process proceeds to S1007, and if the certain time has not elapsed since the start of BLE radio wave reception, the process returns to S1003 and continues the MFP search process.

[0096] In S1007, CPU 111 displays a detection error screen indicating that the proximity of the MFP and the communication terminal could not be detected. Fig. 6(a) shows an example of the detection error screen displayed in S1007. The detection error screen displays a pop-up 601 notifying that the communication terminal needs to be brought closer, and that if the situation does not improve, sensitivity adjustment should be performed. When CPU 111 detects that the OK button has been selected, it returns to S1002 and resumes searching for a nearby MFP. Note that if an MFP with a received signal strength of Near or greater is not found, a pop-up indicating that no MFP was found in the vicinity may be displayed.

[0097] Next, in S1008, CPU 111 determines whether there is one MFP whose received signal strength is Touchlike or greater detected in S1005. If there is one MFP whose received signal strength is Touchlike or greater detected in S1005, the process proceeds to S1009, and if there is not one MFP whose received signal strength is Touchlike or greater detected in S1005, the process proceeds to S1007. Note that the process of S1008 is an exception process for preventing a login request from being sent to multiple MFPs.

[0098] In S1009, CPU 111 determines whether or not the MFP detected in S1005 is an MFP stored in device list information 312. If the detected MFP is an MFP stored in device list information 312, the process proceeds to S1010, and if the detected MFP is not an MFP stored in device list information 312, the process proceeds to the MFP registration sequence from S909 onwards.

[0099] In S1010, the CPU 111 establishes a BLE connection with the MFP detected in S1005. For the sake of explanation, the following steps will be described using an example in which the communications terminal 102 detects an advertising packet from the MFP 101 with a reception strength of Touchlike or higher.

[0100] When a BLE connection with the MFP 101 is established, the MFP 101 and the communication terminal 102 are in a state where they can perform GATT (Generic Attributes) communication. Specifically, in order to start BLE communication, the cooperative application 310 requests the OS 300 to start BLE communication with the MFP 101. The OS 300 controls the Bluetooth I / F 123 via the Bluetooth control unit 301 to start BLE communication with the MFP 101.

[0101] Here, GATT communication will be described. The MFP 101 of this embodiment includes a GATT server that publishes various services defined in a GATT profile for transmitting and receiving data with an external terminal via BLE. Fig. 12 is a diagram for explaining GATT communication, and shows an example of a GATT server published by the MFP 101. The GATT server publishes a user authentication service 1200, a Wi-Fi AP mode start / stop service 1207, and a Wi-Fi (registered trademark) connection information acquisition service 1208.

[0102] The user authentication service 1200 has the following characteristics defined in a GATT profile. In GATT, the profile and characteristics have a relationship similar to that of an object-oriented class and member variables. When there is a change in the login status of the user of the MFP 101, the CPU 131 of the MFP 101 reads and writes the value of each characteristic.

[0103] StatusID 1201 is a characteristic that indicates the state of MFP 101 related to whether login is possible. The communications terminal 102 reads StatusID 1201 to acquire the state of MFP 101 related to whether login is possible. The MFP 101 stores the values ​​shown in Table 2 (login possibility state list) as the value of StatusID 1201.

[0104] [Table 2]

[0105] This value is changed by the CPU 131 when there is a change in the user login state or screen transition state of the MFP 101. When there is a change in the value of the StatusID 1201, the change in value is notified to the communication terminal 102 in BLE connection by a notification in the Attribute Protocol (ATT). The StatusID of "4" will be described with reference to FIG. 13(b). FIG. 13(b) illustrates an example of an administrator setting screen of the MFP 101. The MFP 101 of this embodiment can switch ON / OFF of a user authentication function and ON / OFF of a linked login function as operation settings of the MFP 101. The administrator of the MFP 101 can change the operation settings of the MFP 101 via the screen of FIG. 13(b). The MFP 101 switches the operation of the user authentication function according to the settings.

[0106] Here, when user authentication is set to OFF, MFP 101 does not request the user to log in, and each function of MFP 101 can be used via operation unit 136. Therefore, MFP 101 stores "4" in StatusID. Even if user authentication is set to ON, if the linked login function is set to OFF, local login linked with communication terminal 102 must be prohibited. Therefore, MFP 101 stores "4" in StatusID.

[0107] 12, a description will be given of other characteristics of the user authentication service 1200. UserName 1202, Password 1203, and DomainName 1204 are each characteristics for writing user identification information when the communication terminal 102 makes a login request.

[0108] RequestID 1205 is a characteristic for the communication terminal 102 to write a request to a user authentication service. 1202 to 1205 are configured to allow values ​​to be written from an external device that has established BLE communication. 1202 to 1205 may be configured as characteristics that require encryption for access.

[0109] The communications terminal 102 writes, for example, 1 indicating a login request or 2 indicating a logout request to RequestID 1205. When the CPU 131 of the MFP 101 receives an instruction from the communications terminal 102 to write 1 to RequestID 1205, it performs user authentication based on the user identification information written in 1202 to 1204 (i.e., authentication information received via BLE communication).

[0110] ResultId 1205 is a characteristic that stores an authentication result (success or failure of the login result) when the MFP 101 receives a login request from the communication terminal 102 and performs user authentication. For example, the MFP 101 writes a value indicating login success, login failure, etc., in ResultId 1205 as the authentication result. When the MFP 101 stores the authentication result in ResultId 1205, the communication terminal 102 that is currently connected via BLE is notified of the change in the authentication result value by Notification in ATT.

[0111] A Wi-Fi AP mode start / stop service 1207 is a service used when switching the operation mode of the access point of the MFP 101 from a communication terminal. Also, a Wi-Fi connection information acquisition service 1208 is a service used when acquiring connection information to the MFP from a communication terminal. These services are used as appropriate when handing over from BLE communication to wireless communication compliant with IEEE802.11.

[0112] In this way, the communication terminal 102 performs bidirectional BLE communication with the MFP 101 by reading and writing the characteristics of the GATT server published by the MFP 101.

[0113] 10, in S1011, the CPU 111 acquires the local login status of the MFP. Specifically, the cooperative application 310 and the OS 300 cooperate to access the user authentication service 1200 published by the MFP 101, and acquire the value of the characteristic (StatusID 1201 in FIG. 12) indicating the local login status.

[0114] Next, in S1012, CPU 111 determines whether the target MFP 101 is in a state where login is possible, based on the local login status acquired in S1009. Specifically, if StatusID 1201 is "1", CPU 111 determines that login is possible, and proceeds with the process to S1013. On the other hand, if StatusID 1201 is other than "1", CPU 111 determines that login is not possible (login is not possible), and proceeds with the process to S1016.

[0115] In S1013, the CPU 111 transmits a login request to the MFP 101 using BLE communication. Specifically, the cooperative application 310 and the OS 300 cooperate to write to the UserName 1202, Password 1203, and DomainName 1204 of the MFP 101 based on the user credentials stored in the user authentication information 311. Furthermore, the cooperative application 310 and the OS 300 cooperate to write to the RequestID 1205 a value indicating the login request.

[0116] In S1014, the CPU 111 determines whether the login is successful. When authentication based on the login request is performed on the MFP 101 side and a value is written to the ResultId 1205 as a result, the communication terminal 102 is notified by the ATT's Notification that a value change has occurred. In response to this notification, the CPU 111 obtains the ReultID 1206 from the MFP 101 via BLE communication and determines whether the login is successful. If a value indicating successful login is obtained as the ReultID, the process proceeds to S1015. If a value indicating failed login is obtained as the ReultID, the process proceeds to S1016.

[0117] In S1015, the CPU 111 displays the login success screen illustrated in FIG. 5(c). On the other hand, in S1016, the CPU 111 displays the authentication error screen illustrated in FIG. 5(d). Note that the content of the pop-up 531 displayed on the authentication error screen varies depending on the type of login error. In FIG. 5(d), as an example, an error screen when it is determined that authentication has failed in S1014 is illustrated. The pop-up in FIG. 5(d) can suggest to the user that there may be a mistake in setting the user authentication information in the linked application 310. Subsequently, other cases of login errors will be described. For example, the CPU 111 notifies the user of why an error has occurred according to the value of the StatusID obtained in S1011. For example, when the value of the StatusID is "2", a notification such as "Since the user is already logged in, the login failed." is issued. Also, when the value of the StatusID is "3", a notification such as "Since another screen is being displayed, the login failed. Please try again after switching to the login screen." is issued. Also, when the value of the StatusID is "4", a notification such as "Since the multifunction printer panel login function is not permitted, the login failed. Please contact the MFP administrator for details." is issued.

[0118] <Processing on the MFP side> Next, control on the MFP 101 side that receives a login request from the communication terminal 102 will be described with reference to Fig. 12. For the sake of explanation, Fig. 12 illustrates an example of control in the case where the MFP 101 can accept a login request from a mobile terminal.

[0119] In S1101, the CPU 131 receives a login request from the communication terminal 102 by BLE communication. In S1202, the CPU 131 executes a user authentication process based on the login request received in S1101. Specifically, the CPU 131 acquires user authentication information obtained by reading values ​​of 1202 to 1204, which are characteristics of the user authentication service 1200. Based on the acquired user authentication information, it is determined whether a matching user account is managed in a user management database stored in the storage 134. If a matching user account is found, the authentication is OK. If a matching user account is not found, the authentication is NG. In S1103, the CPU 131 determines whether or not to permit login based on the result of the authentication in S1102. If the authentication result is OK, the process proceeds to S1105. If the authentication result is NG, the process proceeds to S1104. Note that, here, a case where a user management database inside the MFP 101 is used for user authentication is illustrated, but is not limited thereto. For example, an external LDAP (Lightweight Directory Access Protocol) server or the like can be used for user authentication. In this case, the MFP 101 transmits user authentication information to the LDAP server and requests the LDAP server to perform authentication processing for the user. The MFP 101 may determine whether to permit login based on the result of authentication received from the LDAP server.

[0120] In S1104, CPU 131 updates the authentication result and notifies the mobile terminal of the authentication result. CPU 131 writes information indicating login failure to ResultId 1205. When a value is written to ResultID 1206, the communication terminal 102 is notified by ATT Notification that the value has been changed. When the process of S1104 is completed, a series of processes at the time of receiving a login request is terminated. Furthermore, in addition to notifying the mobile terminal, CPU 131 displays a pop-up on operation unit 136 to notify that login has failed.

[0121] In S1106, CPU 131 displays a main screen on operation unit 136. Note that the user can use each function of MFP 101 via the main screen displayed on operation unit 136. Note that the screen displayed in S1105 can be appropriately changed according to the authority of the logged-in user or the personal settings of the logged-in user.

[0122] Through the series of processes described above, a user can log in to the MFP 101 simply by holding his / her own communications terminal over the MFP 101, instead of having to enter a user ID and password when logging in to the MFP.

[0123] Next, in S1106, CPU 131 updates the authentication result, updates the local login information, and notifies the mobile terminal of the authentication result. CPU 131 writes a value indicating successful login to ResultId 1205. When the value is written to ResultID 1206, the communication terminal 102 is notified by ATT Notification that the value has been changed. CPU 131 also writes "2" to StatusID 1201 as the local login information. When the process is completed, proceed to S1107.

[0124] In S1107, CPU 131 determines whether or not a user instruction to execute a function has been accepted via operation unit 136. If a user instruction to execute a function has been accepted via operation unit 136, the process proceeds to S1108, and if a user instruction to execute a function has not been accepted via operation unit 136, the process proceeds to S1109.

[0125] In S1108, CPU 131 executes a function according to a user instruction. For example, a copy function for printing an image obtained by scanning an original on printing unit 140, a facsimile function for facsimile transmitting an image obtained by scanning, etc. are executed according to the user instruction. When execution of the function is completed, the process proceeds to S1109.

[0126] In S1109, CPU 131 determines whether or not an instruction to log out the user has been accepted. If an instruction to log out the user has been accepted, the process proceeds to S1110, and if an instruction to log out the user has not been accepted, the process returns to S1107.

[0127] In S1110, the CPU 131 performs logout processing and updates the local login status. In StatusID, "1" is written, which indicates that login is possible.

[0128] In S1111, the CPU 131 displays a login screen (not shown) on the operation unit 136, and ends the series of processes.

[0129] As described above, in this embodiment, appropriate notification control is performed when logging in to a surrounding external device from a communication terminal, thereby improving user convenience. Also, according to this embodiment, the linked login function with the communication terminal 102 makes it possible to appropriately notify the user of various error factors that occur due to a combination of the settings and statuses of each device.

[0130] 9, the user can be notified at an early stage in the sequence for performing the login process, thereby preventing the user from performing unnecessary operations.

[0131] <Modification> In the first embodiment, the local login status is checked in S1011 of Fig. 10, and if a user is already logged in, a local login using a communication terminal is rejected. However, the present invention is not limited to this. For example, even if a user is already logged in to MFP 101, a configuration can be adopted in which a local login using a communication terminal is prioritized. In this case, communication terminal 102 writes a logout request to RequestID 1205 to log out the user currently logged in to MFP 101. After that, the process from S1013 onward can be executed again.

[0132] In the present embodiment, the case where the reception signal strength of the advertising packet is used to determine the proximity of an external device such as an MFP around the communication terminal 102 is illustrated, but the present invention is not limited to this. For example, the distance between the devices may be estimated from the ratio between the transmission signal strength (Tx) and the reception signal strength included in the advertising packet, and the proximity may be determined based on the distance. Also, for example, the proximity between the communication terminal and the external device to be logged in may be determined using other methods such as Wi-Fi Aware (registered trademark).

[0133] <Other embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of each of the above-mentioned embodiments to a system or device via a network or a storage medium, and having one or more processors in a computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC or FPGA) that realizes one or more functions. [Explanation of symbols]

[0134] 101 MFP 102 Communication terminal 111 CPU 114 Storage 123 Bluetooth I / F< / mfp>

Claims

1. A computer, a detection step of performing a process for detecting an external device by wireless communication via the wireless communication interface; a notification step for performing a notification after the processing is executed in the detection step; a determination step of determining whether the notification to be performed in the notification step is a first notification or a second notification; a registration procedure for registering the external device detected in the detection procedure, the first notification is a notification for accepting an operation from a user for registering the external device detected in the detection procedure, The second notification is a notification for accepting an operation from the user to adjust the sensitivity of the wireless communication. A program characterized by:

2. A computer, a detection step of performing a process for detecting an external device by wireless communication via the wireless communication interface; a notification step for performing a notification after the processing is executed in the detection step; a determination step of determining whether the notification to be performed in the notification step is a first notification or a second notification; a registration procedure for registering an external device; and a program for executing the registration procedure, the first notification notifies the external device detected in the detection procedure; the registration step is a step of registering the notified external device based on an operation by a user, The second notification is a notification for accepting an operation from the user to adjust the sensitivity of the wireless communication. A program characterized by:

3. A computer, a detection step of performing a process for detecting an external device by wireless communication via the wireless communication interface; a registration procedure for registering an external device; a first notification procedure for performing a first notification of the external device detected in the detection procedure; a second notification procedure for issuing a second notification for receiving an operation from a user to adjust sensitivity of the wireless communication when an external device is not detected in the detection procedure, The registration step is a step of registering the external device notified in the first notification step based on an operation from the user. A program characterized by:

4. The first notification notifies an external device detected in the detection procedure, The registration procedure is a procedure for registering the notified external device based on an operation by the user.

2. The program according to claim 1 .

5. The first notification is a notification for accepting an operation from a user to register the external device detected in the detection procedure.

4. The program according to claim 2 or 3.

6. The registration of the external device in the registration procedure is registration of information about the external device.

6. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

7. The registration step is a step of registering the external device detected in the detection step as a usable external device.

7. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

8. The term "registering as an available external device" means registering as an external device that can send instructions from the computer to the external device to execute processing using the functions of the external device.

8. The program according to claim 7,

9. The operation in response to the first notification is an operation of selecting the external device to be registered.

9. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

10. It is possible to set authentication information for the external device registered in the registration procedure.

10. The program according to claim 1, wherein the program is a program for executing a program.

11. The authentication information setting is a setting for logging in to the registered external device. The program according to claim 10 .

12. The computer is further caused to execute a third notification procedure for issuing a notification urging registration of an external device when there is no registered external device.

12. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

13. The external device is a printer.

13. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

14. The external device includes at least one of a printing unit and a reading unit.

13. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

15. The wireless communication is Bluetooth communication.

15. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

16. The wireless communication is short-range wireless communication.

15. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

17. The wireless communication is communication via wireless LAN.

15. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

18. The computer is further caused to execute a fourth notification procedure for issuing a notification urging the user to turn on a setting value for using the wireless communication interface when the setting value is off.

18. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

19. The method further comprises causing the computer to execute a fifth notification procedure for issuing a notification urging the user to bring the computer closer to an external device.

19. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

20. The first notification includes information about the detected external device.

20. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

21. The computer is caused to execute the first notification when the result of executing the process is a first result, and to execute the second notification when the result of executing the process is a second result.

21. The program according to claim 1 , 22. A program for causing the computer to further execute a communication procedure for wirelessly communicating with an external device, comprising: The computer is caused to issue the first notification when the state of the wireless communication with the external device is a first state, and to issue the second notification when the state of the wireless communication with the external device is a second state.

22. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

23. A first display control procedure for controlling a display means to display the first notification; and a second display control step of controlling the display means to display the second notification.

23. The program according to claim 1, wherein the program is a program for executing a program.

24. The first display control procedure is a procedure for, when a plurality of external devices are detected in the detection procedure, displaying the detected plurality of external devices on the display means as the first notification.

24. The program according to claim 23.

25. The program is an application program installed on a communication terminal.

25. The program according to claim 1, wherein the program is a program for executing a program for executing a program.

26. A communication terminal having a wireless communication interface, a detection means for executing a process for detecting an external device by wireless communication via the wireless communication interface; a notification means for issuing a notification after the processing is executed by the detection means; a determining means for determining whether the notification to be made by the notifying means is a first notification or a second notification; a registration means for registering the external device detected by the detection means, the first notification is a notification for accepting an operation from a user to register the external device detected by the detection means, The second notification is a notification for accepting an operation from the user to adjust the sensitivity of the wireless communication. A communication terminal characterized by:

27. A communication terminal having a wireless communication interface, a detection means for executing a process for detecting an external device by wireless communication via the wireless communication interface; a notification means for issuing a notification after the processing is executed by the detection means; a determining means for determining whether the notification to be made by the notifying means is a first notification or a second notification; a registration means for registering an external device; the first notification notifies the external device detected by the detection means; the registration means registers the notified external device based on an operation by a user; The second notification is a notification for accepting an operation from the user to adjust the sensitivity of the wireless communication. A communication terminal characterized by:

28. A communication terminal having a wireless communication interface, a detection means for executing a process for detecting an external device by wireless communication via the wireless communication interface; a registration means for registering an external device; a first notification means for performing a first notification of an external device detected by the detection means; a second notification means for issuing a second notification to receive an operation from a user to adjust the sensitivity of the wireless communication when the external device is not detected by the detection means, The registration means registers the external device notified by the first notification means based on an operation by the user. A communication terminal characterized by:

Images