Mobile terminal, control method thereof, program, and storage medium

Abstract

To solve a problem in which, when logging in using an IC card, a user is to go to a device to which the user wants to log in, hold an IC card over an IC card reader, and wait a while until the user has been authenticated, and there is also a case where the user forgets to have the IC card with the user.SOLUTION: At least one computer possessed by a mobile terminal is controlled to acquire information based on a signal transmitted from an information processing device, and transmit a login request to the information processing device on the basis of the received signal strength of the signal transmitted from the information processing device satisfying a predetermined condition, and is caused to function to perform processing such that the predetermined condition is changed on the basis of an instruction from a user.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a mobile terminal, a control method thereof, a program, and a storage medium. [Background technology]

[0002] When logging in to a conventional multifunction device, a user would log in by having a card reader connected to the multifunction device read the user's IC card, thereby authenticating the user (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] Conventionally, when logging in using an IC card, the user has to take the time to hold the IC card over a card reader. In addition, after holding the IC card over the card reader, it may take some time for the user to be authenticated, which means it takes a long time for the user to log in.

[0005] An object of the present invention is to solve the above problems of the prior art.

[0006] A feature of the present invention is to provide a technique that allows a user to log in to an information processing device simply by carrying a portable terminal and approaching the information processing device. [Means for solving the problem]

[0007] In order to achieve the above object, a program according to one aspect of the present invention has the following configuration: At least one computer included in the mobile terminal, An acquisition means for acquiring information based on a signal transmitted from an information processing device; a control means for controlling transmission of a login request to the information processing device based on a received signal strength of a signal transmitted from the information processing device satisfying a predetermined condition; The present invention is characterized in that the device functions as a processing means for performing processing so that the predetermined condition is changed based on an instruction from a user. Effect of the Invention

[0008] According to the present invention, a user can log in to an information processing device simply by approaching the information processing device using a portable terminal owned by the user.

[0009] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same reference numerals are used to designate the same or similar components throughout the drawings. [Brief description of the drawings]

[0010] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a communication system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram for explaining the hardware configuration of an MFP and a mobile terminal according to the first embodiment. [Diagram 3] 1A is a block diagram illustrating the software configuration of an MFP according to a first embodiment, and FIG. 1B is a block diagram illustrating the software configuration of a mobile terminal according to the first embodiment. [Figure 4] 4A to 4C are diagrams illustrating an example of a screen displayed on the operation unit of the MFP according to the first embodiment and screen transitions relating to login and logout. [Diagram 5] 4 is a diagram showing an example of a Bluetooth service provided in the MFP according to the first embodiment. [Figure 6] 5 is a flowchart showing a basic operation of the mobile terminal according to the first embodiment. [Figure 7] 7 is a flowchart showing details of the MFP usage process in S608 of FIG. 6. [Figure 8] A diagram showing a UI that presents alternative functions to a user on a mobile device. [Figure 9] 8 is a flowchart illustrating details of the alternative function utilization process in S710 of FIG. 7. [Figure 10] 7 is a flowchart showing details of the MFP usage termination process in S611 of FIG. 6. [Figure 11] 6 is a flowchart for explaining the operation of a local login process in the MFP according to the first embodiment. [Figure 12] 6 is a flowchart showing the operation of a logout process in the MFP according to the first embodiment. [Figure 13] 6 is a flowchart showing the operation of the MFP when it receives a login request from a mobile terminal. [Figure 14] 3A and 3B are diagrams for explaining examples of states of the MFP and the mobile terminal according to the first embodiment of the present invention. [Figure 15] 11 is a diagram for explaining a user authentication service and characteristics via Bluetooth provided in an MFP according to a second embodiment of the present invention. [Figure 16] 11 is a diagram showing a sequence when a mobile terminal according to the second embodiment makes a login request to an MFP. [Figure 17] 11 is a flowchart for explaining manual logout processing by the MFP according to the third embodiment. [Figure 18] 13 is a diagram for explaining characteristics provided in the user authentication service of the MFP according to the fourth embodiment of the present invention. [Figure 19] 10 is a flowchart showing details of the process of S608 in FIG. 6 according to the fourth embodiment. [Figure 20] 13 is a flowchart for explaining the operation of a local login process in the MFP according to the fourth embodiment. [Figure 21] FIG. 11 is a block diagram illustrating the hardware configuration of an MFP according to a fifth embodiment of the present invention. [Figure 22]13 is a flowchart for explaining the processing performed by the MFP according to the fifth embodiment, from logging in a user of a mobile terminal to logging out the user, in response to a signal from the mobile terminal. [Diagram 23] 13 is a flowchart for explaining a process in which the mobile terminal 102 according to the fifth embodiment logs in to the MFP 101. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the attached drawings. Note that the following embodiment does not limit the present invention according to the claims, and not all of the combinations of features described in the present embodiment are necessarily essential to the solution of the present invention. Note that in the following embodiment, a multi-function peripheral (MFP) will be taken as an example of an information processing device according to the present invention. However, the information processing device according to the present invention is not limited to such a multi-function peripheral, and can also be applied to, for example, communication devices such as printers, scanners, and facsimiles, and information devices such as PCs.

[0012] [Embodiment 1] FIG. 1 is a diagram showing an example of the configuration of a communication system according to a first embodiment of the present invention.

[0013] In this communication system, multiple MFPs (multifunction processors) and multiple mobile terminals exist, and for example, an office environment is assumed in which each user has his or her own mobile terminal and always carries it with them. Each MFP has functions such as copying, sending and receiving facsimile, scanning, box, sending, and printing, and is installed according to the office environment. In the system of Fig. 1, MFP 101, mobile terminal 102, and mobile terminal 103 are shown, but the number of these devices is not limited to this.

[0014] Mobile terminal 101 and mobile terminal 102 are owned by different users. MFP 101 is connected to network (LAN) 104, and can communicate with other terminals connected to LAN 104 via LAN 104. Similarly, mobile terminal 102 and mobile terminal 103 can connect to LAN 104 via wireless router 105, and can wirelessly communicate with other terminals connected to LAN 104. MFP 101 and mobile terminals 102 and 103 are also provided with Bluetooth (registered trademark) communication function as a short-range wireless communication function, and can connect to each other and communicate within the range of Bluetooth radio waves.

[0015] 2 is a block diagram for explaining the hardware configuration of the MFP 101 and the mobile terminal 102 according to the first embodiment. Note that the hardware configuration of the mobile terminal 103 is the same as that of the mobile terminal 102, so the explanation thereof will be omitted.

[0016] First, the hardware configuration of the MFP 101 will be described.

[0017] The CPU 201 controls the overall operation of the MFP 101. The CPU 201 reads out a control program stored in the ROM 202 and performs various controls such as reading control, printing control, and transmission control. The RAM 203 is a volatile memory used as a work area or the like when the CPU 201 executes various programs. The HDD 204 stores image data and various programs. The operation unit 205 includes a display unit and hard keys that operate as a touch panel that can be operated by a user's finger. The printer 206 prints an image on a sheet according to image data transferred via the internal bus 221. The scanner 207 reads an image on a document and generates image data. The IC card reader 208 reads an IC card owned by a user for user authentication. The Bluetooth I / F 209 is an interface that performs wireless communication according to the Bluetooth standard, and performs wireless communication with other devices having the Bluetooth I / F. In the first embodiment, the MFP 101 can perform mutual communication with the mobile terminals 102 and 103 according to the Bluetooth standard. The network I / F 210 has a NIC (Network Interface Card) for connecting to the LAN 104. A timer 223 measures a predetermined time according to an instruction from the CPU 201, and notifies the CPU 201 by an interrupt or the like when the specified time has elapsed. The internal bus 221 connects the CPU 201 to each of the above-mentioned components, and transmits data, control signals, and the like. The programs executed by the CPU 201 may be installed in the HDD 204, and may be expanded into the RAM 203 at the time of execution and then executed.

[0018] Next, the hardware configuration of the mobile terminal 102 will be described.

[0019] The CPU 211 controls the overall operation of the mobile terminal 102. The RAM 212 is a volatile memory used as a work area or the like when the CPU 211 executes various programs. The flash memory 213 is a non-volatile memory that stores various programs and data. The operation unit 214 includes a display unit that operates as a touch panel that can be operated by a user's finger. The Bluetooth I / F 215 is an interface for communicating via Bluetooth, and communicates with other devices having a Bluetooth interface. In the first embodiment, the mobile terminal 102 communicates with the MFP 101 via Bluetooth. The wireless network interface 216 is a wireless-compatible NIC that can be connected to and communicate with the wireless router 105. The speaker 217 converts an electric signal into sound. The microphone 218 detects sound and converts it into an electric signal. The camera 219 captures still images and videos and converts them into electronic data. The GPS 220 is a receiver for the Global Positioning System. The internal bus 222 connects the CPU 211 to each of the above-mentioned components, and transmits data, control signals, and the like.

[0020] 3A is a block diagram illustrating the software configuration of the MFP 101 according to the first embodiment, and FIG. 3B is a block diagram illustrating the software configuration of the mobile terminal 102 according to the first embodiment. Again, the software configuration of the mobile terminal 103 is the same as that of the mobile terminal 102, so the description thereof will be omitted.

[0021] FIG. 3A is a block diagram showing the software configuration of the MFP 101 and the data area managed by the software. A document 304, a print job 305, a counter 306, and a user account 313 indicate data areas that the software stores in the RAM 203 or the HDD 204 and manages. The platform 301 can be configured to include an operating system such as Linux (registered trademark), a virtual machine of JAVA (registered trademark), an OSGi (registered trademark) framework, and a group of device drivers. JAVA is a registered trademark of Oracle Corporation. The OSGi framework is a JAVA-based service platform defined by the OSGi Alliance (a standardization organization). The platform 301 includes a group of device drivers for controlling various hardware, and provides an API for using the hardware to an application running on the platform 301. For example, a Bluetooth control unit 302 is a device driver for controlling a Bluetooth I / F 209, and a network control unit 303 is a device driver for controlling a network I / F 210. Although not shown, the platform 301 also includes a printer module that controls the printer 206 and a scanner module that controls the scanner 207. The platform 301 also provides applications with APIs for reading and writing data of the document 304, the print job 305, and the counter 306.

[0022] Menu 307, copy 308, print 309, and send 310 are applications that run on platform 301, and display a user interface that provides various functions to operation unit 205. For example, copy 308 controls scanner 207 and printer 206 via platform 301 to perform copying. Print 309 provides a function to print document data stored in document 304 and print jobs stored in print job 305. Copy and print output is executed via API of platform 301, and platform 301 records the number of printed sheets in counter 306. Send 310 provides a function to transmit document data acquired from scanner 207 to the outside. Menu 307 is a module that displays a menu screen for selecting an application (e.g., copy, print, send) from operation unit 205. Remote UI 311 is a module that provides a user interface written in HTML when MFP 101 is accessed by a web browser of mobile terminal 102 or 103 via HTTP protocol. A remote UI 311 provides a user interface for managing settings of the MFP 101 and a user interface for printing document data stored in a document 304. A login service 312 is a module that provides a login function when a user uses the MFP 101.

[0023] Next, a user account 313 management function, a local login function, a remote login function, and a login function for accessing a Bluetooth service provided in the login service 312 will be described. -User account management function A user interface for registering and managing user accounts is provided to users. Information registered via the user interface is recorded and managed in user account 313. Examples of the information to be managed include user name, password, IC card number, and role, as shown in Table 1 (list of user information).

[0024] [Table 1]

[0025] -Local login function A login / logout function is provided for users who use the operation unit 205. A login screen is displayed on the operation unit 205 to prevent users who are not logged in from using the operation unit 205. Here, the number of users who can locally log in at the same time is set to "1". Therefore, multiple users cannot locally log in at the same time. If the user login is successful, the screen on the display unit of the operation unit 205 is transitioned from the login screen to a menu screen, making the MFP 101 available to the user. Multiple login means are provided as a means for performing local login. For example, the following login means are provided. (1) Logging in via keyboard The user name and password entered by the user through the login screen displayed on the operation unit 205 are acquired, and once the user is authenticated, login processing is performed. (2) Logging in with an IC card The user's IC card is held over the IC card reader 208, and an IC card number is obtained to identify the user. If the user is authenticated, a login process is performed. (3) Logging in via mobile When a login request is received from a mobile terminal via Bluetooth communication together with user authentication information, the user is authenticated and login processing is performed. Here, levels are set for login requests from mobile devices, and, for example, implementation is performed such that requests of a certain level are rejected depending on the state of the MFP 101. The MFP 101 records and manages the StatuIDs shown in Table 2 (login availability status list) below in the RAM 203. Here, as shown in Table 2, if the StatuID is "1", login is possible, but if the StatuID is "2" or "3", the login request may not be accepted depending on the login request level and the state of the MFP 101. If the StatuID is "3", after the user logs out, login requests from that user are not accepted until the user moves out of a certain distance range (for example, 10 cm to 2 m) from the MFP 101.

[0026] [Table 2]

[0027] Next, the following multiple methods are provided as methods for logout after local login. (1) A logout button (410 in FIG. 4) is displayed on the operation unit 205, and when pressing of the logout button is detected, a logout process is performed. (2) If the user does not operate the operation unit 205 for a certain period of time, a logout process is performed. (3) When a logout request is received from a mobile terminal, a logout process is performed.

[0028] After the logout process, the login screen is displayed.

[0029] Next, remote login will be described. -Remote login function It provides a login / logout function when using the remote UI 311. For example, when access to the remote UI 311 from the mobile terminal 102 is detected, a login screen written in HTML is transmitted to the mobile terminal 102. Then, the user name and password entered on the login screen are obtained to authenticate the user, and login to the remote UI 311 is permitted. It is configured to allow multiple users to remotely log in at the same time. (2)Login function for Bluetooth service access Provides login / logout functionality for accessing services published via Bluetooth.

[0030] Next, the software configuration of the mobile terminal 102 according to the embodiment will be described with reference to Fig. 3(B). Note that in the following description, the mobile terminal 102 will be taken as an example, but the same can be applied to the mobile terminal 103.

[0031] The document 320 and authentication information 319 indicate data areas that the software stores in the flash memory 213 and manages. The platform 314 can be configured with a platform such as Google's Android (registered trademark) or Apple's iOS (registered trademark). The platform 314 includes a group of device drivers for controlling various hardware, and provides an API for using various hardware to applications running on the platform 314. In the first embodiment, the device driver group includes a Bluetooth control unit 315 and a wireless network control unit 316. The Bluetooth control unit 315 is a device driver for controlling the Bluetooth I / F 215, and the wireless network control unit 316 is a device driver for controlling the wireless network I / F 216. Various applications can be installed in the mobile terminal 102 and run on the platform 314. In the first embodiment, it is assumed that an MFP connection application 317 is installed in advance. The MFP connection application 317 includes, for example, the following functions. (1) Connect to MFP101 via Bluetooth and make login and logout requests. (2) The user authentication information (user name and password) used when requesting login can be recorded in advance by the user in the authentication information 319. For example, a pair of a user name and a password as shown in Table 3 (authentication information) below is recorded.

[0032] [Table 3]

[0033] (3) A connection is made to the MFP 101 via wireless LAN, and a print request is issued for the photo data and document data recorded in the document 320. (4) The web browser 318 is launched and connected to the remote UI 311 of the MFP 101 .

[0034] It is assumed that MFP connection application 317 holds, for example, setting values ​​such as those shown in Table 4 (connection setting list) below. Table 4 below indicates that a login request is made when mobile terminal 102 is within 2 m of MFP 101, and that a logout request is made when mobile terminal 102 is 5 m or more away. This also means that different levels of login requests are used depending on the distance between mobile terminal 102 and MFP 101. Note that, as will be described later, the distance at which this request is made may be set to different values ​​depending on the user. For example, the distance at which this request is made is set shorter for a user who always works close to MFP 101 than for other users.

[0035] [Table 4]

[0036] The above distance may be configured to be changeable by the user of the mobile terminal 102, or may be configured to acquire the setting from the MFP 101. The distance from the MFP 101 is measured using Bluetooth RSSI (Received Signal Strength Indication) transmitted by the MFP 101. It is desirable to set the logout distance longer than the login distance. This is because the RSSI may become weak when an obstacle is placed between the mobile terminal 102 and the MFP 101, and this is to prevent logout due to erroneous detection caused by the presence of an obstacle between the mobile terminal 102 and the MFP 101. For example, by utilizing the property that the RSSI attenuates as the distance between the MFP 101 and the mobile terminal 102 increases, data showing the relationship between RSSI (dBm) and the distance from the MFP 101 can be created, as shown in Table 5 (RSSI and estimated distance list) below.

[0037] [Table 5]

[0038] When the strength of the Bluetooth transmission radio wave transmitted by MFP 101 is known in advance, mobile terminal 102 may be configured to have in advance data relating to the relationship between the RSSI and the distance from MFP 101 as described above. Also, mobile terminal 102 may dynamically obtain information relating to the strength of the Bluetooth transmission radio wave transmitted by MFP 101 from MFP 101 and compare it with the RSSI to calculate the distance from MFP 101.

[0039] FIG. 4 is a diagram for explaining an example of a screen displayed on the operation unit 205 of the MFP 101 according to the first embodiment and screen transitions relating to login and logout.

[0040] For example, before a user logs in, a login screen 401 is displayed on the operation unit 205, and the operation unit 205 waits for detection of an IC card or reception of a login request from the mobile terminal 102 via Bluetooth. When the IC card is detected or a login request is received via Bluetooth, login processing is performed. If the login is successful, the screen transitions to a menu screen 403, and if the login is unsuccessful, the original login screen 401 is displayed. If the login screen 401 detects pressing of a button 404 for switching to keyboard authentication, the screen transitions to a login screen 402 for inputting an account and password using a soft keyboard. The login screen 402 includes a button 405 for returning to the login screen 401. If the login screen 402 detects pressing of a login button 406, the input account and password are obtained, and login processing including user authentication processing is performed. If the login is successful, the screen transitions to a menu screen 403, and if the login is unsuccessful, the original login screen 402 is displayed.

[0041] The menu screen 403 includes buttons 407 to 409 for calling various applications, and a logout button 410. When pressing of the logout button 410 is detected, a logout process is performed and the login screen 401 is displayed.

[0042] Next, the functions and services of Bluetooth provided in the MFP 101 according to the first embodiment will be described.

[0043] When the MFP 101 according to the first embodiment is powered on, the platform 301 activates Bluetooth via the Bluetooth control unit 302 and transmits a Bluetooth advertising packet at a predetermined interval. This advertising packet includes the following data: Local Name The name of the device, for example, "(company name) MFP CXXX". Manufacturer Specific Data Stores the identifier of the manufacturer that produced the MFP and any other data. It can also include the RSSI (Received Signal Strength Indication, e.g. -59dbm) when a Bluetooth packet is received 1m away from the device. TX Power Level Transmitting signal strength, for example "-38dbm". Service UUIDs A UUID that describes the capabilities of the device.

[0044] FIG. 5 is a diagram showing an example of Bluetooth services provided in the MFP 101 according to the first embodiment.

[0045] This MFP 101 exposes a user authentication service 501, an MFP information service 502, a print service 503, and a maintenance service 504 defined in a GATT (Generic Attribute) profile to the mobile terminal 102 connected via Bluetooth. The user authentication service 501 has the following characteristics defined in the GATT profile. A login service 312 reads and writes the values ​​of each characteristic via an API provided by the platform 301 and the Bluetooth control unit 302. StatusID505 This is a characteristic that indicates the status regarding the permission of login to the MFP 101. The mobile terminal 102 reads it and uses it to acquire the status regarding the permission of login to the MFP 101. As with the login permission status list, the value shown in Table 6 (StatusID list) below is stored as this value.

[0046] [Table 6]

[0047] The login service 312 changes the value (StatusID) according to the change in the status. When the value is changed, the Bluetooth control unit 302 notifies the connected mobile terminal 102 of the change in the value by using a Notification in the Attribute Protocol (ATT). UserName506 This is a characteristic for writing a user name when the mobile terminal 102 requests login. ·Password507 This is a characteristic for writing a password when the mobile terminal 102 requests login. It may be configured as a characteristic that requires encryption of the password to be written. RequestID508 This is a characteristic for the mobile terminal 102 to write a request to the authentication service. For example, Request ID 508 as shown in the following Table 7 (Request ID list) is written. The login request level shown in Table 7 corresponds to the login request level shown in Table 4 above.

[0048] [Table 7]

[0049] ResultID509 This is a characteristic that stores the authentication result (success or failure of user authentication) when the MFP 101 receives a login request from the mobile terminal 102 and performs user authentication. For example, values ​​such as those shown in the following Table 8 (ResultID list) are stored.

[0050] [Table 8]

[0051] When the authentication result is stored, the Bluetooth control unit 302 notifies the connected mobile terminal 102 of the authentication result by using a Notification in the Attribute Protocol (ATT).

[0052] The MFP information service 502 has a URL 510 that stores the URL of the remote UI 311 in a characteristic. The value of the URL 510 is set by the platform 301 when the MFP 101 is started up.

[0053] The print service 503 is configured as a service that can be searched for from the mobile terminal 102 after successful login for Bluetooth service access. The print service 503 has the following characteristics. The print 309 reads and writes the values ​​of each characteristic via APIs provided by the platform 301 and the Bluetooth control unit 302. MyJobList511 The identifier of the print job associated with the user who has logged in for Bluetooth service access is stored from among the print jobs temporarily stored in the print job 305. If there are multiple print jobs associated with the user, the identifiers of the multiple print jobs are stored. · RequestID512 This is a characteristic for the mobile terminal 102 to request an operation on the print job 305. For example, the IDs shown in the following Table 9 (list of Request IDs for the print service) can be written. The value written by the mobile terminal 102 is notified to the print 309, which operates the print job in response to the request. Here, printing and deletion of the print job can be instructed.

[0054] [Table 9]

[0055] · RequestParameter513 This characteristic stores the identifier of the print job 305 that is the target of the operation when the mobile terminal 102 requests an operation on the print job 305. The mobile terminal 102 writes the identifier of the print job acquired from MyJobList 511.

[0056] The maintenance service 504 is configured as a service that can be searched from the mobile terminal 102 when login for Bluetooth service access is successful and the role of the logged-in user is administrator. The maintenance service 504 includes a Count 514 that stores the count of the counter 306 as a characteristic. The platform 301 detects a change in the value of the counter 306 and sets the same value to the Count 514.

[0057] Although not shown, each service and characteristic has information such as a handle, a UUID, data type information, and text information.

[0058] Next, the basic operation of the mobile terminal 102 according to the first embodiment will be described.

[0059] Fig. 6 is a flowchart showing the basic operation of the mobile terminal 102 according to the first embodiment. Below, with reference to Fig. 6, the basic operation when a user having the mobile terminal 102 approaches the MFP 101 and starts using the MFP 101 will be described. Unless otherwise specified, the subject of the operation of the mobile terminal 102 is the CPU 211. Furthermore, unless otherwise specified, the subject of the software is the MFP connection application 317, or the MFP connection application 317 calls an API provided by the platform 314 and the platform 314 performs the processing on its behalf. Here, the subject of the operation will be described as the CPU 211.

[0060] When the processing of the mobile terminal 102 is started, the CPU 211 starts scanning for Bluetooth advertising packets transmitted from the MFP 101 in S601. Then, when the CPU 211 receives an advertising packet in S602, the process proceeds to S603, where the CPU 211 determines whether the source of the advertising packet is a predetermined MFP or not. Here, it is assumed that the MFP that the user of the mobile terminal 102 usually uses is registered in advance in the mobile terminal 102. Therefore, in S603, the CPU 211 determines whether the source of the received advertising packet is this registered MFP or not. Specifically, the CPU 211 analyzes the received advertising packet, refers to the values ​​of LocalName, Manufacturer Specific Data, and Service UUIDs, and determines that the MFP is a predetermined MFP if a known value is stored. If it is determined in S603 that the MFP is not a predetermined MFP, the advertising packet is ignored and the process proceeds to S602. The reason for making this determination in S603 is to prevent the user from logging in to an MFP that he or she does not intend to use simply by approaching or passing by that MFP.

[0061] If it is determined in S603 that the packet is an advertising packet from a specific MFP 101, the process proceeds to S604, where the CPU 211 calculates the distance between the MFP 101 and the mobile terminal 102 from the RSSI. Here, the distance is calculated from the difference between the RSSI and information on the transmission radio wave intensity transmitted by the MFP 101, which is included in the TX Power Level and Manufacturer Specific Data of the advertising packet. Note that, because the RSSI has errors, the distance may be calculated by sampling a plurality of advertising packets.

[0062] Next, the process proceeds to S605, and the CPU 211 refers to the distance calculated in S604 and the settings shown in the table (Table 4) of the connection settings list to determine whether or not the MFP 101 is within a predetermined distance at which use of the MFP 101 is started. The predetermined distance in the first embodiment is, for example, within 2 m. At this time, different distances may be set depending on the user. This is because, for example, if the user A mostly works close to the MFP 101, if the distance at which the user A can log in is set to within 2 m, the user A will always log in. In this case, the distance corresponding to the user A is set to, for example, 30 cm. If the CPU 211 determines in S605 that the distance is within the predetermined distance, the process proceeds to S606, and determines whether or not the MFP 101 is in use. As a method of this determination, for example, an MFP use status flag indicating whether or not the MFP 101 is in use as shown in Table 10 (MFP use status flag) below is recorded in the RAM 212 and used. When the MFP 101 is in use, the in-use flag is set to TRUE, and when use ends, the flag is set to FALSE, and the mobile terminal 102 manages the usage state of the MFP 101.

[0063] [Table 10]

[0064] The reason for managing the usage status of MFP 101 here is to prevent a different job from being submitted when MFP 101 is executing a certain job. If the MFP usage status flag indicates that the MFP is not in use, the process proceeds to S607 where CPU 211 changes the flag to ON, indicating that the MFP is in use, and the process proceeds to S608 where the process executes processing using the MFP 101. On the other hand, if the MFP usage status flag indicates that the MFP is in use in S606, the process ends as is.

[0065] On the other hand, if the CPU 211 determines in S605 that the distance to the MFP 101 is not within the predetermined distance, the process proceeds to S609, where the CPU 211 refers to the settings shown in Table 4 of the connection setting list and determines whether the distance to the MFP 101 is equal to or greater than a predetermined distance in order to end the use of the MFP 101. In the first embodiment, the predetermined distance is, for example, 5 m or greater. If the CPU 211 determines in S609 that the distance is equal to or greater than the predetermined distance, the process proceeds to S610, where the CPU 211 refers to the above-mentioned flag and determines whether the MFP 101 is in use. If the CPU 211 determines that the MFP 101 is in use, the process proceeds to S611, where the CPU 211 performs a process to end the use of the MFP 101. Then, the process proceeds to S612, where the CPU 211 changes the above-mentioned flag to FALSE, and ends this process. If the CPU 211 determines in S609 that the distance to the MFP 101 is not equal to or greater than the predetermined distance, the process proceeds to S602. If the CPU 211 determines that the MFP 101 is not in use in S610, the process ends as is.

[0066] In step S601, the MFP connection application 317 does not necessarily have to be running. For example, the MFP connection application 317 can request the platform 314 to monitor in advance whether an advertising packet has been received from a specific MFP. Then, the platform 314 that has received an advertising packet from the specific MFP can start the stopped MFP connection application 317.

[0067] In this way, by simply bringing the mobile terminal 102 close to a specific MFP, the MFP can be brought into a usable state. The mobile terminal 102 is something that the user carries with him / her at all times, and unlike an IC card, the user will not forget to carry it with him / her.

[0068] FIG. 7 is a flowchart showing the details of the MFP usage process in S608 of FIG.

[0069] When the mobile terminal 102 starts the use process of the MFP 101, first, in S701, the CPU 211 establishes a communication connection to the MFP 101 via Bluetooth. Unless otherwise specified, subsequent data communication between the mobile terminal 102 and the MFP 101 is via Bluetooth. Next, the process proceeds to S702, where the CPU 211 acquires Bluetooth service information from the MFP 101. In the first embodiment, it is assumed that information on the user authentication service 501 and the service by the MFP 101 can be acquired at this point. Next, the process proceeds to S703, where the CPU 211 reads the StatusID 505 included in the user authentication service 501. Then, the process proceeds to S704, where the CPU 211 determines whether or not a login request can be made to the MFP 101 based on the distance calculated in S604 and the value acquired by reading the StatusID 505. Here, for example, if the calculated distance is 2 m to 30 cm, it is determined whether or not a login request can be made to the MFP 101 at login request level 1 based on the value acquired in the StatusID 505. As shown in Table 6 above, if StatusID505 is "1", a login request is possible, but if it indicates any other value, it is determined that the login request is not possible. Similarly, for example, if the calculated distance is between 30 cm and 10 cm, the possibility of a login request of login request level 2 is determined based on the value acquired from StatusID505. In this case, if StatusID505 is "1" or "2", it is determined that the login request is possible, and if StatusID505 is "3", it is determined that the login request is not possible. Also, if the calculated distance is 10 cm or less, the login request level is 3, so it is determined that the login request is possible regardless of the value of StatusID505.

[0070] If the CPU 211 determines in S704 that the login request is possible, the process proceeds to S705, where the CPU 211 requests the MFP 101 to login. Specifically, values ​​are written to the UserName 506, Password 507, and RequestID 508 of the user authentication service 501. For example, information shown in the authentication information in Table 3 is written to the UserName 506 and Password 507, and one of the values ​​"1", "2", and "3" shown in the RequestID list in Table 7 is written to the RequestID 508 according to the calculated distance. Next, the process proceeds to S706, where the CPU 211 receives updates to the ResultID 509 and StatusID 505 by Notification as a response from the MFP 101. Then, the process proceeds to S707, where the CPU 211 disconnects the connection with the MFP 101 via Bluetooth, and ends this process.

[0071] On the other hand, if it is determined in S704 that the login request is not permitted, the process proceeds to S708, where the CPU 211 displays, for example, a screen such as that shown in FIG. 8 on the operation unit 214, and presents functions that can be used instead of local login as alternative functions.

[0072] FIG. 8 is a diagram showing an example of a screen displayed on the operation unit of the mobile terminal 102 according to the first embodiment, showing an example of a presentation of an alternative function when login to the MFP is not possible.

[0073] Here, a message is displayed indicating that the MFP 101 cannot be used because another user is using the MFP 101, and a list of alternative functions are displayed. As instruction buttons for the alternative functions, a "Connect to Remote UI" button 801, a "Print" button 802, a "View Maintenance Information" button 803, and a "Cancel" button 804 are displayed.

[0074] Next, the process proceeds to S709, where CPU 211 determines whether or not the user has selected an alternative function on the screen of Fig. 8. If the user presses cancel button 804 without selecting an alternative function, the process proceeds to S707, where the connection to MFP 101 via Bluetooth is disconnected, and this process ends. On the other hand, if the user has selected any alternative function, the process proceeds to S710, and the alternative function selected by the user is provided to the user. Then, after the alternative function is provided, when the process by that function is completed, the process proceeds to S707, where the connection to MFP 101 via Bluetooth is disconnected, and this process ends.

[0075] FIG. 9 is a flowchart illustrating the details of the alternative function utilization process in S710 of FIG.

[0076] First, in S901, the CPU 211 determines the alternative function selected by the user via the screen of Fig. 8, and performs processing according to the selected alternative function. For example, if the user selects the "Connect to Remote UI" button 801, the process proceeds to S902. In S902, the CPU 211 reads the URL 510 of the MFP information service 502 and acquires the URL of the remote UI 311 of the MFP 101. Next, the process proceeds to S903, where the CPU 211 starts up the web browser 318 and connects to the remote UI 311 of the MFP 101 via the wireless network I / F 216. Then, the process proceeds to S904, where the CPU 211 performs remote login using the HTTP protocol.

[0077] On the other hand, if the user selects the "Print" button 802 in S901, the process proceeds to S905, where the CPU 211 makes a login request for Bluetooth service access to the MFP 101. Specifically, values ​​are written into the UserName 506, Password 507, and RequestID 508 of the user authentication service 501, respectively. Here, authentication information of the user of the mobile terminal 102 shown in Table 3 is written into the UserName 506 and Password 507. Also, the value "5" indicating a login request for Bluetooth service access in Table 7 is written into the RequestID 508. Next, the process proceeds to S906, where the CPU 211 receives an update of the ResultID 509 from the MFP 101 as the authentication result by Notification. Here, if the login via Bluetooth is successful, the CPU 211 acquires service information in S906 and proceeds to S907.

[0078] In the first embodiment, after Bluetooth login, the MFP 101 permits access to the print service, and information about the print service can be acquired. The CPU 211 of the mobile terminal 102 thus acquires the information about the print service, and can use the print service in S907. For example, it is also possible to acquire information about a job associated with an authenticated user from the print service. For example, it is also possible to display the user's job on the operation unit 214 and accept a print instruction from the user. When the user instructs printing, a print request is written in RequestID 508, and the MFP 101 is instructed to print.

[0079] Also, in S901, for example, if the user selects the "View Maintenance Information" button 803, the process proceeds to S908, where the CPU 211 requests the MFP 101 to login for Bluetooth service access. Next, the process proceeds to S909, where the CPU 211 acquires service information. In the first embodiment, if the login via Bluetooth is successful and the role of the authenticated user is an administrator, the MFP 101 permits access to the maintenance service, and the maintenance service can be acquired. If the access to the maintenance service is successful in this way, the process proceeds to S910, where the CPU 211 uses the maintenance service. Here, for example, information on the counter 306 can be acquired from the maintenance service, and the counter value can be displayed on the operation unit 214.

[0080] FIG. 10 is a flowchart showing details of the end-of-use process of the MFP 101 in S611 of FIG.

[0081] First, in S1001, when the CPU 211 starts the logout process, it establishes a Bluetooth connection to the MFP 101. Next, the process proceeds to S1002, where the CPU 211 acquires service information and acquires information on the user authentication service 501. Next, the process proceeds to S1003, where the CPU 211 reads the value of StatusID 505. Next, the process proceeds to S1004, where the CPU 211 determines whether or not the MFP 101 is currently locally logged in based on the value of StatusID 505. In the first embodiment, when the StatusID 505 is "2" from the list of StatusID 505 in Table 6, it indicates that the MFP 101 is currently locally logged in. Here, if it is determined that the MFP 101 is currently locally logged in, the process proceeds to S1005, where the CPU 211 issues a logout request to the MFP 101. Specifically, the CPU 211 writes the user name in UserName 506 and writes the value "4" (Table 7) indicating a logout request in RequestID 508. Then, the process proceeds to S1006, where the Bluetooth connection to the MFP 101 is disconnected, and this process ends. On the other hand, if it is determined in S1004 that local login is not in progress, the process proceeds to S1006 without issuing a logout request, the Bluetooth connection with the MFP 101 is disconnected, and this process ends.

[0082] According to the above-described process, it is possible to log in to MFP 101 and use MFP 101 simply by bringing mobile terminal 102 close to a preset MFP 101. At this time, if MFP 101 is being used by another user, selectable alternative functions are presented to the user who owns mobile terminal 102, and the user can select and execute the alternative function. In addition, after logging in to MFP 101, if the user who owns mobile terminal 102 moves a predetermined distance away from MFP 101, he or she is automatically logged out of MFP 101, which prevents the user from forgetting to log out after logging in.

[0083] 11 is a flowchart for explaining the operation of local login processing in the MFP 101 according to the first embodiment. Unless otherwise specified, the main body of the operation of the MFP 101 is the CPU 201. Furthermore, unless otherwise specified, the main body of the software is the login service 312, or the login service 312 calls an API provided by the platform 301 and the platform 301 performs the processing on its behalf.

[0084] When the CPU 201 starts accepting local login requests, it enables login using a keyboard, login with an IC card, and login from a mobile device. Specifically, in S1101, the CPU 201 enables login from a keyboard, displays a login screen on the operation unit 205, and makes it possible to detect a login operation by a user. In addition, in login using an IC card, in S1102 the CPU 201 makes the IC card detectable by the IC card reader 208. In addition, in login using a mobile device, in S1103 the CPU 201 publishes a user authentication service defined in the GATT profile of Bluetooth, and makes it possible to detect a local login request via Bluetooth.

[0085] Thus, the process proceeds to S1104, and when the CPU 201 detects a login request from any one of them, the process proceeds to S1105. In S1105, the CPU 201 identifies the issuer of the login request, and performs authentication processing according to the issuer of the login request.

[0086] If in S1105 the CPU 201 determines that the login was made using the keyboard of the operation unit 205, the process proceeds to S1106, where the CPU 201 detects an operation on the login screen of the operation unit 205 and acquires the user name and password entered on the login screen. Next, the process proceeds to S1107, where the CPU 201 authenticates the user by comparing and collating the acquired values ​​with information registered in advance in the MFP 101, for example, information registered in the list of user information shown in the above-mentioned Table 1, and then the process proceeds to S1116.

[0087] On the other hand, if in S1105 CPU 201 determines that login is by IC card, the process proceeds to S1108, where CPU 201 acquires the IC card number upon detecting that an IC card has been held over IC card reader 208. Then the process proceeds to S1109, where CPU 201 compares and collates the acquired IC card number with IC card numbers (see Table 1) registered in a user information list previously registered in MFP 101, authenticates the user who owns the IC card, and proceeds to S1116.

[0088] If the CPU 201 determines in S1105 that the login is a login by a mobile device, the process proceeds to S1110, where the CPU 201 detects that an ID indicating a login request is written in the RequestID 508 of the user authentication service 501. The CPU 201 then obtains the level of the login request (Table 7) from the value written in the RequestID 508, and compares it with the login availability status in Table 2 to determine whether the login request level is acceptable. For example, if the login availability status is not login available (StatusID=1) for a login request of level 1, but is StatusID=2 or 3, the login process is canceled. Similarly, if the login availability status indicates that the login request level 2 is not acceptable (StatusID=3) for a login request of level 2, the login process is canceled. If the login process is canceled here, the process proceeds to S1115, where the CPU 201 sets the value "3" (Table 8) indicating cancellation in the ResultID 509, and notifies the mobile terminal 102 that made the login request of the cancellation by using Notification. Also, in S1110, if the login request is of level 3, the login request is accepted unconditionally. Thus, when CPU 201 determines in S1110 that the login request level is acceptable, the process proceeds to S1111, where CPU 201 determines whether or not another user is currently logged in locally. If it is determined that another user is currently logged in, the process proceeds to S1112, where CPU 201 executes a process of forcibly logging out the currently logged in user, and proceeds to S1113. Also, when no other user is currently logged in in S1111, the process proceeds to S1113. In S1113, CPU 201 refers to UserName 506 and Password 507 written from mobile terminal 102 to acquire a user name and password. Then, the process proceeds to S1114, where CPU 201 authenticates the user by comparing and collating the acquired values ​​with information recorded in a user information list previously registered in MFP 101. Next, the process proceeds to step S1115, and the CPU 201 sets the user authentication result in ResultID 509, and transmits the result of the login process to the mobile terminal 102 that made the login request in Notification, and then the process proceeds to step S1116.

[0089] In S1116, CPU 201 determines whether user authentication has been successful, and if it is determined that authentication has failed, the process returns to the beginning of the flowchart in Fig. 11 to wait for detection of the next login request. On the other hand, if CPU 201 determines in S1116 that user authentication has been successful, the process proceeds to S1117. In S1117, CPU 201 updates StatusID 505, which indicates the login permission status, to a value of "2" indicating that "login request level 1 is not accepted because another user is logged in". Then, the process proceeds to S1118, where CPU 201 transitions the display on operation unit 205 from the login screen to a menu screen, and ends this login process.

[0090] If the mobile terminal 102 is configured to reliably check the login permission status of the MFP 101 in advance and not mistakenly issue a login request to the MFP 101, the process of determining the level of the login request in S1110 is not necessarily required.

[0091] Next, the logout operation in the MFP 101 will be described.

[0092] 12 is a flowchart showing the operation of the logout process in the MFP 101 according to the first embodiment. Unless otherwise specified, the subject of the operation of the MFP 101 is the CPU 201. Furthermore, unless otherwise specified, the subject of the software is the login service 312, or the login service 312 calls an API provided by the platform 301 and the platform 301 performs the processing on its behalf.

[0093] When a user logs in locally, the MFP 101 starts accepting logout. Here, manual logout, timer 223 logout, and mobile logout are enabled as logout methods. Specifically, in manual logout, in S1201 the CPU 201 displays the logout button 410 (FIG. 4) on the operation unit 205 and makes it possible to detect pressing of the logout button 401 by the user. In addition, in logout by the timer 223, in S1202 the CPU 201 uses timer processing to make it possible to detect the absence of any operation by the user for a certain period of time. In addition, in mobile logout, in S1203 the CPU 201 makes it possible to detect writing of a logout request to RequestID 508 from a mobile terminal via Bluetooth.

[0094] The process then proceeds to S1204, and when the CPU 201 detects a logout request, the process proceeds to S1205. In S1205, the CPU 201 determines whether the logout request is from a manual, timer, or mobile device, and performs processing according to the logout request.

[0095] If the CPU 201 detects that the logout button 410 has been pressed in S1205, the process proceeds to S1206, where the CPU 201 executes a logout process. Next, the process proceeds to S1207, where the CPU 201 updates the login permission status statusID 505 to a value "3" indicating that "login request levels 1 and 2 are not accepted because the logout has just occurred." The process proceeds to S1208, where the CPU 201 starts the timer 223 to check the passage of time. Then, the process proceeds to S1209, where the CPU 201 transitions the display on the operation unit 205 to a login screen. At this time, login using a keyboard, login using an IC card, and login using login request level 3 from Bluetooth becomes possible. After that, if the CPU 201 detects in S1210 that there is no login request for a certain period of time and that a certain period of time (for example, 10 seconds) has elapsed using the timer 223, the process proceeds to S1211. In step S1211, the CPU 201 updates the login permission status StatusID 505 to the value "1" indicating "login permitted." This returns all login methods to a valid state.

[0096] On the other hand, if in S1205 CPU 201 detects that there has been no user operation for a certain period of time based on the timing of timer 223, the process proceeds to S1212, where CPU 201 performs logout processing. Next, the process proceeds to S1213, where CPU 201 updates StatusID 505, which indicates the login availability status, to a value of "1" indicating "login possible". Then, in S1214 CPU 201 displays a login screen on operation unit 205, and ends this process.

[0097] Also, in S1205, when the CPU 201 detects that the mobile terminal 102 has written a user name to UserName 506 via Bluetooth and that a logout request has been written to RequestID 508, the process proceeds to S1215. In S1215, the CPU 201 detects a logout by mobile and judges whether the logged-in user name is the same as the user name written to UserName 506. If it is judged that the user names do not match, the process cancels the logout request, returns to the beginning of this flowchart, and waits for the next logout request. If it is judged that the user names match in S1215, the process proceeds to S1216, where the CPU 201 performs a logout process. Next, the process proceeds to S1217, where the CPU 201 updates the login availability status StatusID 505 to a value "1" indicating "login available". Then, in S1218, the CPU 201 displays a login screen on the operation unit 205 and ends this process.

[0098] 13 is a flowchart showing the operation of the MFP 101 according to the first embodiment when it receives a login request for Bluetooth service access from the mobile terminal 102. Unless otherwise specified, the subject of the operation of the MFP 101 is the CPU 201. Furthermore, unless otherwise specified, the subject of the software is the login service 312, or the login service 312 calls an API provided by the platform 301 and the platform 301 performs the processing on its behalf.

[0099] This process is started by the CPU 201 detecting in S1301 that a "login request for Bluetooth service access" has been written in the RequestID 508 of the user authentication service 501. Next, the process proceeds to S1302, where the CPU 201 references the UserName 506 and Password 507 written from the mobile terminal 102 to acquire the user name and password, which are the authentication information of the user. Then, the process proceeds to S1303, where the CPU 201 performs user authentication by comparing and collating the values ​​acquired in S1302 with information recorded in a user information list (Table 1) previously registered in the MFP 101. Then, in S1304, the CPU 201 determines whether the user authentication has been successful, and if the user authentication has been successful, the process proceeds to S1305, where the CPU 201 makes the print service available for Find from the mobile terminal 102 in the same Bluetooth connection. On the other hand, if the CPU 201 determines in S1304 that the user authentication has failed, the process proceeds to S1308. After S1305, the process proceeds to S1306, where the CPU 201 checks the role of the authenticated user. If the user's role is an administrator, the process proceeds to S1307, where the maintenance service is made available for searching from the mobile terminal 102 during the same Bluetooth connection period, and the process proceeds to S1308. On the other hand, if the CPU 201 determines in S1306 that the user's role is not an administrator, the process proceeds to S1308.

[0100] In S1308, the CPU 201 sets the user authentication result in ResultID 509, and transmits the result of the login process to the mobile terminal 102 that made the login request in a Notification. The process then proceeds to S1309, and when the CPU 201 detects a Bluetooth disconnection, the process proceeds to S1310, where the CPU 201 resets the published state of the services. Specifically, the print service and maintenance service are returned to a state in which they cannot be found via Bluetooth.

[0101] According to this process, a user of a portable terminal issues a login request for Bluetooth service access from the portable terminal to the MFP, and when the login is approved, the user can use services such as printing provided by the MFP.

[0102] 14 is a diagram for explaining an example of the states of the MFP 101 and the mobile terminal according to the first embodiment of the present invention. The effects of the first embodiment will be explained below with reference to FIG.

[0103] 14A shows a state in which a user (Alice) approaches the MFP 101 with a portable terminal 102 while no one is logged in to the MFP 101. In this case, when it is detected that Alice's portable terminal 102 has come within 2 meters of the MFP 101, it issues a login request to the MFP 101. Therefore, the login is completed when Alice arrives in front of the operation unit 205 of the MFP 101, and Alice can immediately use the MFP 101 without having to wait in front of the operation unit 205 to log in. In addition, when Alice with the portable terminal 102 moves away from the MFP 101, she is automatically logged out when she moves 5 meters or more away from the MFP 101, which prevents her from forgetting to log out.

[0104] 14B shows a state in which a user (Alice) approaches MFP 101 with mobile terminal 102 while a user (Bob) who owns mobile terminal 103 is using MFP 101. In this case, Alice's mobile terminal 102 does not make a login request to MFP 101 because MFP 101 is in use. Therefore, mobile terminal 102 does not prevent Bob from using MFP 101. On the other hand, an alternative means is presented to Alice's mobile terminal 102, so Alice can also use the functions of MFP 101 within the scope of the functions provided by the alternative means.

[0105] FIG. 14C shows a case where a user (Carol) has finished using the MFP 101 but has forgotten to log out, and so Alice approaches the MFP 101 while Carol is still logged in. In this case, if the distance between the MFP 101 and the mobile terminal 102 is 30 cm to 2 m, Alice's mobile terminal 102 does not make a login request. However, when Alice reaches the operation unit 205 of the MFP 101 and the distance between the MFP 101 and the mobile terminal 102 is within 30 cm, Alice's mobile terminal 102 makes a login request to the MFP 101. This causes the MFP 101 to forcibly log Carol out and log Alice in. This makes it possible to prevent Alice from mistakenly using the MFP 101 while Carol is still logged in. In addition, Alice does not need to press the logout button 410 displayed on the operation unit 205 on behalf of Carol.

[0106] FIG. 14D shows a state immediately after the logout button 410 displayed on the operation unit 205 of the MFP 101 is pressed. In this case, even if Bob's mobile terminal 103 is nearby, Bob's mobile terminal 103 does not issue a login request. This prevents Bob's mobile terminal 103 from logging in when Alice is in front of the operation unit 205 of the MFP 101, ensuring safety. Furthermore, if the user who pressed the logout button 410 is Alice and Alice wants to log in to the MFP 101 again immediately after performing a logout operation, Alice moves the mobile terminal 102 closer to the MFP 101 to within 10 cm. This causes Alice's mobile terminal 102 to issue a login request to the MFP 101. In this way, Alice can log in to the MFP 101 again even immediately after logging out.

[0107] [Embodiment 2] Next, a second embodiment of the present invention will be described. In the second embodiment, an example is shown in which a more secure communication method is implemented than the communication shown in the detailed flow at the time of login shown in the first embodiment. Note that the configurations of the MFP 101 and mobile terminals 102 and 103 according to the second embodiment, and the system configuration thereof are the same as those of the first embodiment, and therefore the description thereof will be omitted.

[0108] Fig. 15 is a diagram for explaining a user authentication service and characteristics by Bluetooth provided in the MFP 101 according to the second embodiment of the present invention. Here, parts common to the above-mentioned Fig. 5 are indicated by the same numbers. In the second embodiment, the user authentication service of the MFP 101 has the following two characteristics instead of the Password 507 in the above-mentioned first embodiment. The rest is the same as in the above-mentioned first embodiment. · Challenge 1501 A characteristic used to store the challenge. This value stores a random number that the MFP 101 issues each time. Hash1502 The characteristic used to store the hash value.

[0109] In the second embodiment, in order to prevent unauthorized acquisition of passwords by eavesdropping on packets or spoofing an MFP, a challenge-response type user authentication is realized using Bluetooth characteristics.

[0110] Fig. 16 is a diagram showing a sequence when the mobile terminal 102 according to the second embodiment makes a login request to the MFP 101. A method of using the characteristics of the user authentication service according to the second embodiment will be described with reference to Fig. 16. Note that the basic operation of the mobile terminal 102 here is the same as that in Fig. 7 in the first embodiment.

[0111] When the mobile terminal 102 starts the login request process in S705, in S1601, it issues a read request for Challenge1501, and in S1602, it acquires the value of the challenge. Next, in S1603, the mobile terminal 102 calculates a hash value using the acquired challenge and the user's password. Here, an algorithm for generating the challenge and calculating the hash value may be Challenge-Response Authentication Mechanism (CRAM) described in RFC2195, but the present invention is not limited to this. Next, in S1604, the mobile terminal 102 writes the user name in UserName506 and the calculated hash value in Hash1502, and also writes a login request in RequestID508. As a result, the MFP 101 detects the login request and reads the user name, hash value, and challenge from the characteristic. After reading these values, they are cleared so that they cannot be referenced when accessed by other terminals. Then, in S1605, the MFP 101 performs user authentication processing using the user name, hash value, and challenge acquired from the characteristic. Specifically, it acquires the challenge set in the characteristic and the user's password registered in the user DB, and calculates a hash value using the same algorithm as the mobile terminal 102. Then, it compares the calculated hash value with the hash value acquired from the characteristic. After completing the user authentication in this way, the MFP 101 updates the characteristic challenge with a new value in preparation for the next authentication. Subsequent operations after user authentication are the same as those in the first embodiment.

[0112] As described above, according to the second embodiment, a challenge-response type user authentication is realized using Bluetooth, which is more secure than the first embodiment and has the effect of preventing unauthorized acquisition of passwords by packet sniffing or spoofing an MFP.

[0113] [Embodiment 3] In the above-described first embodiment, in the manual logout process of S1206 to S1211 in FIG. 12, the problem occurring immediately after logout is solved by not accepting any request other than login request level 3 immediately after manual logout.

[0114] A method according to a third embodiment, which can obtain the same effect, is shown in Fig. 17. Note that the configurations of the MFP 101 and mobile terminals 102 and 103 according to the third embodiment, and the system configuration thereof are similar to those of the first embodiment, and therefore description thereof will be omitted.

[0115] 17 is a flowchart for explaining manual logout processing by the MFP 101 according to the third embodiment. Unless otherwise specified, the subject of the operation of the MFP 101 is the CPU 201. Furthermore, unless otherwise specified, the subject of the software is the login service 312, or the login service 312 calls an API provided by the platform 301 and the platform 301 performs the processing on its behalf.

[0116] First, in S1701, when the CPU 201 detects that the logout button 410 has been pressed, the CPU 201 performs a logout process. Next, the process proceeds to S1702, where the CPU 201 stops sending advertising packets of Bluetooth. Next, the process proceeds to S1703, where the CPU 201 starts the timer 223 to check the passage of time. Then, the process proceeds to S1704, where the CPU 201 changes the display of the operation unit 205 to a login screen. At this time, login by keyboard, login by IC card, and login using login request level 3 from Bluetooth are possible. After that, in S1705, when the CPU 201 detects that there is no login request for a certain period of time and that a certain period of time (for example, 10 seconds) has elapsed by the timer 223, the process proceeds to S1706. In S1706, the CPU 201 resumes sending advertising packets after the certain period of time has elapsed after the manual logout.

[0117] As a result, while the MFP 101 has stopped transmitting advertising packets, the mobile terminal 102 cannot detect the distance between the MFP 101 and the mobile terminal 102. This makes it possible to prevent the mobile terminal 102 from making a login request to the MFP 101 while the MFP 101 is performing a logout process by manual operation.

[0118] [Embodiment 4] In the above-mentioned first to third embodiments, an example has been shown in which the mobile terminal 102 checks whether login to the MFP 101 is possible and determines whether to make a login request. For example, the determination in S704 in Fig. 7 corresponds to this. In contrast, the fourth embodiment shows an example in which the mobile terminal 102 does not determine whether login is possible, but leaves the determination to the MFP 101. Note that the configurations of the MFP 101 and mobile terminals 102 and 103 according to the fourth embodiment and their system configurations are similar to those of the first embodiment, and therefore description thereof will be omitted.

[0119] FIG. 18 is a diagram for explaining characteristics provided in the user authentication service of the MFP 101 according to the fourth embodiment of the present invention. Here, parts common to the above-mentioned FIG. 5 and FIG. 15 are indicated by the same numbers, and their explanations are omitted. The user authentication service of the MFP 101 according to the fourth embodiment includes Distance1801 and Distance1802 for writing the distance calculated by the mobile terminal 102, in addition to the characteristics of the above-mentioned first and second embodiments. Also, for a login request, the levels 1 to 3 as shown in the above-mentioned first embodiment are not necessary, and one RequestID indicating a login request is used. Note that the MFP 101 according to the fourth embodiment is assumed to have stored in advance, as a setting, a list of login permission states of the fourth embodiment shown in Table 11 below.

[0120] [Table 11]

[0121] The operation of the mobile terminal 102 according to the fourth embodiment is similar to that described in the flowchart of FIG. 6 in the first embodiment, and therefore will not be described again.

[0122] Fig. 19 is a flowchart for explaining details of the process of S608 in Fig. 6 according to embodiment 4. A detailed flow of S608 in embodiment 4 will be described with reference to Fig. 19.

[0123] When the CPU 211 of the mobile terminal 102 starts the use process of the MFP 101, first in S1901, it connects to the MFP 101 via Bluetooth. Next, proceeding to S1902, the CPU 211 acquires Bluetooth service information from the MFP 101. In this fourth embodiment, it is assumed that information on the user authentication service 501 and the MFP information service 502 can be acquired at this point. Next, proceeding to S1903, the CPU 211 issues a login request to the MFP 101. In the fourth embodiment, at the time of this login request, the distance from the MFP 101 calculated by the CPU 211 of the mobile terminal 102 is written in Distance (1801 or 1802). Next, proceeding to S1904, the CPU 211 receives updates to the ResultID and StatusID from the MFP 101 as a result of the login process by Notification.

[0124] Then, in S1905, the CPU 211 determines from the received result whether the login has been successful. If it is determined that the login has been successful, the process proceeds to S1906, where the CPU 211 disconnects the connection with the MFP 101 via Bluetooth, and ends this process.

[0125] On the other hand, if the CPU 211 determines in S1905 that the login has failed, the process proceeds to S1907, where the CPU 211 presents the user with a usable function as an alternative function instead of locally logging in to the MFP 101. This is the same as in FIG. 8 described above. Then, the process proceeds to S1908, where the CPU 211 determines whether or not the user has selected an alternative function. Here, if the user presses the cancel button 804 without selecting an alternative function, the process proceeds to S1906, where the CPU 211 disconnects the connection to the MFP 101 via Bluetooth, and ends this process. On the other hand, if the CPU 211 determines in S1908 that the user has selected an alternative function, the process proceeds to S1909, where the CPU 211 provides the user with the alternative function selected by the user, as described with reference to the flowchart in FIG. 9 described above. Then, after providing this alternative function, the process proceeds to S1906, where the CPU 211 disconnects the connection to the MFP 101 via Bluetooth, which is no longer required, and ends this process.

[0126] Fig. 20 is a flowchart for explaining the operation of local login processing in MFP 101 according to embodiment 4. In Fig. 20, the same processes as those in Fig. 11 described above are given the same numbers and their explanations are omitted. In the above-mentioned embodiment 1, upon receiving a login request, MFP 101 compared the login request level with the login permission status in S1110 in Fig. 11 to determine whether the login request level is an acceptable level.

[0127] In response to this, when the CPU 201 of the MFP 101 according to the fourth embodiment detects a login request from the mobile terminal 102, the process proceeds to S2001, and the CPU 201 acquires the distance information written in Distance (1801, 1802). Next, the process proceeds to S2002, and the CPU 201 refers to the login availability state list (Table 11) of the fourth embodiment, and determines whether or not the distance between the mobile terminal 102 and the MFP 101 is a distance at which the login request can be accepted. For example, when the acquired distance is between 2 m and 30 m, and when the login availability state is not the value "1" indicating that login is possible, but indicates "2" or "3" according to Table 11, the CPU 201 determines that login is impossible and cancels the login process. Also, for example, when the acquired distance is between 30 cm and 10 cm, and the login availability state indicates "3", the CPU 201 determines that login is impossible and cancels the login process. When the login process is canceled, the CPU 201 sets the value "3" indicating that login has been canceled in ResultID, and notifies the mobile terminal 102 of the result in S2003.

[0128] As described above, according to the fourth embodiment, the mobile terminal 102 does not need to perform judgment or processing according to the distance from the MFP 101, which has the effect of simplifying the processing of the mobile terminal 102.

[0129] [Embodiment 5] Next, a fifth embodiment of the present invention will be described. In the first to fourth embodiments described above, the MFP 101 transmits an advertising packet, and the mobile terminal 102 receives it to determine the distance between the MFP 101 and the mobile terminal 102. In contrast, in the fifth embodiment, an example will be described in which the mobile terminal 102 transmits an advertising packet, the MFP 101 receives it, and the MFP 101 determines the distance between the MFP 101 and the mobile terminal 102. Note that, although the description will be given here as processing between the mobile terminal 102 and the MFP 101, it goes without saying that the same can be done in the case of the mobile terminal 103 as in the above-mentioned embodiments.

[0130] Fig. 21 is a block diagram for explaining the hardware configuration of an MFP 101 according to a fifth embodiment of the present invention. The hardware configuration of a mobile terminal 102 and the configuration of a system including the MFP 101 and the mobile terminal 102 are the same as those in the first embodiment, and therefore their explanation will be omitted. Since the MFP 101 according to the fifth embodiment is basically the same as the MFP 101 according to the above-mentioned embodiment, parts common to those in Fig. 2 above are indicated by the same symbols, and their explanation will be omitted.

[0131] The control unit 2100 of the MFP 101 has the following configuration. The CPU 201, RAM 203, ROM 202, SRAM 2101, network interface 210, RIP 2103, scanner image processing unit 2104, printer image processing unit 2105, and storage controller 2108 are connected via a system bus 2114. The CPU 201 is also connected to the operation unit 205 via a UART interface 2101, and is also connected to a Bluetooth module 2113 of the operation unit 205 via a USB interface 2109 and a USB connector 2110. The scanner image processing unit 2104 receives image data obtained by reading an original with the scanner 207 via a scanner I / F 2106, performs image processing, and outputs the image data to the system bus 2114. The printer image processing unit 2105 performs color conversion and the like on the image data received via the system bus 2114 in accordance with the characteristics of the printer 206, and then outputs the image data to the printer 206 via the printer I / F 2107 for printing. The storage controller 2108 controls access to the HDD 204. The CPU 201 executes a boot program stored in the ROM 202, and loads the OS and programs installed in the HDD 204 into the RAM 203 and executes them, thereby executing the processes described below.

[0132] Next, the configuration of the operation unit 205 will be described.

[0133] The sub CPU 2111 controls the operation of the operation unit 205. The key display panel 2112 is a display panel equipped with a touch panel function, and receives user operations and notifies the sub CPU 2111. The ROM 2115 stores programs executed by the sub CPU 2111, various data, etc. The RAM 2116 provides a work area for storing various data when the sub CPU 2111 executes processing. The Bluetooth module 2113 communicates with the Bluetooth I / F 215 of the mobile terminal 205 in accordance with the Bluetooth standard.

[0134] The operation of the MFP 101 based on the above configuration will be briefly described. The network interface 210 receives PDL data, which is print data, via the LAN 104. The CPU 201 writes the received PDL data once in the RAM 203, and stores it in the HDD 204 via the storage controller 2108. The PDL data stored in the HDD 204 is converted into a display list by the CPU 201, and written again to the HDD 204 via the RAM 203. Next, the display list in the HDD 204 is read by the CPU 201, sent to the RIP 2103, converted into raster data, and written again to the HDD 204. In this way, the print job input to the MFP 101 is printed by the printer 206 when the user logs into the MFP 101 by a login method described later. When printing, the raster data is read from the HDD 204 via the system bus 2114, and after density and screen processing and the like are performed in the printer image processing unit 2105, it is output to the printer 206 via the printer I / F 2107.

[0135] Next, a procedure for a user to log in to the MFP 101 will be described.

[0136] The CPU 201 controls the Bluetooth module 2113 via the USB connector 2110. Specifically, the CPU 201 receives an advertising packet of Bluetooth Low Energy communication transmitted from the mobile terminal 102 and executes services in response to a login request or print job input from the mobile terminal 102. By authenticating to the MFP 101 using the mobile terminal 102 owned by the user, the user can obtain authority to use the MFP 101 not only to execute a print job but also to transition the operation screen of the MFP 101 to an operation menu screen or the like.

[0137] Next, a communication process between the MFP 101 according to the fifth embodiment and the mobile terminal 102 will be described.

[0138] 22 is a flowchart for explaining the processing performed by MFP101 according to the fifth embodiment, in response to a signal from mobile terminal 102, to allow the user of mobile terminal 102 to log in and out. Note that a program for executing this processing is stored in HDD204, and is loaded into RAM203 and executed by CPU201 when executed.

[0139] In the fifth embodiment, the MFP 101 and the mobile terminal 102 communicate with each other using the Bluetooth Low Energy communication standard. Here, the service requested from the mobile terminal 102 to the MFP 101 includes a control such that the MFP 101 automatically logs in according to a user ID transmitted from the mobile terminal 102 within a predetermined distance from the MFP 101, and automatically logs out when the mobile terminal 102 moves beyond the predetermined distance.

[0140] First, in S2201, the CPU 201 transitions to a standby state of Bluetooth Low Energy. Next, the process proceeds to S2202, where the CPU 201 determines whether or not the user can be authenticated. If the user can be authenticated, the process proceeds to S2203. If not, the process proceeds to S2203 after waiting until the user can be authenticated. In S2203, the CPU 201 determines whether or not a service that can receive a request from the mobile terminal 102, in this case, authentication processing, is set. If not set, the process proceeds to S2204, where the administrator is prompted to set the service so that authentication can be performed, and the process proceeds to S2203. Thus, in S2203, when the service that can receive a request from the mobile terminal 102 has been set, the CPU 201 proceeds to S2205, where the CPU 201 determines whether or not a distance that is a criterion for login is set. If it is determined that the distance is not set, the process proceeds to S2206, where the administrator of the MFP 101 is prompted to set the distance. When the distance, which is a condition for connecting to the sender of the received Bluetooth advertising packet, is set in the MFP 101 in this way, the process proceeds to S2207. In S2207, the CPU 201 transitions to a scanning state and waits to receive an advertising packet. Then, in S2208, when the CPU 201 receives an advertising packet, the process proceeds to S2209, where the CPU 201 analyzes the received advertising packet. Here, the CPU 201 acquires the distance from the sender, the service UUID, and the user ID. Then, the process proceeds to S2210, where the CPU 201 determines whether the distance from the sender of the received advertising packet is within the value set in S2205. If it is determined that the distance is within the set value, the process proceeds to S2211, but if not, the process proceeds to S2208. Here, too, the distance to be set may be changed according to the user ID. That is, as described in the first embodiment, the distance for user A who always works near the MFP 101 may be, for example, 30 cm, and the distance set for other users may be, for example, 2 m. Therefore, in this case, in S2210, it is determined whether or not the distance is within the connection distance according to the user ID.In S2211, the CPU 201 determines whether the service UUID described in the received advertising packet is a service that is set in the MFP 101 and can be supported, in this case, whether the request is for an authentication service. If so, the process proceeds to S2212, but if not, the process proceeds to S2208.

[0141] In S2212, the CPU 201 transitions to an int state and proceeds to S2213, where the CPU 201 transmits a Connect Req (connection request) packet to the mobile terminal 102 that transmitted the advertising packet. Then, when the CPU 201 receives a Connect Req (connection request) packet from the mobile terminal 102 in S2214, the process proceeds to S2215. In S2215, the CPU 201 executes login processing with the user ID requested by the mobile terminal 102. Here, the CPU 201 refers to the user information list in Table 1 described above and determines whether to permit the user's login. Then, the process proceeds to S2216, where the CPU 201 notifies the mobile terminal 102 of the result of the login processing, that is, authentication success or authentication failure. Next, the process proceeds to S2217, where the CPU 201 transitions to a scanning state as in S2207, waits for reception of an advertising packet in S2218, and proceeds to S2219 when the advertising packet is received. In S2219, the CPU 201 analyzes the received advertising packet, similarly to S2209, and obtains the distance from the sender, the service UUID, and the user ID. Next, the process proceeds to S2220, where the CPU 201 determines whether the distance is sufficient for logging out. In S2220, if the CPU 201 determines that the sender of the advertising packet received in S2218 is the same as the logged-in user ID and is a predetermined distance or greater, the process proceeds to S2221. In S2221, the CPU 201 logs out the user of the mobile terminal 102, and returns to S2201.

[0142] In this way, the user of the mobile terminal 102 can log in to the MFP 101 simply by approaching the MFP 101 within a preset distance while holding the mobile terminal 102. At this time, it is assumed that the distance to the sender at which login is possible, the service UUID that can be accepted, and the user information to be authenticated are registered in the MFP 101 in advance.

[0143] Next, the operation of the mobile terminal 102 according to the fifth embodiment will be described.

[0144] 23 is a flowchart for explaining a process in which the mobile terminal 102 according to the fifth embodiment logs in to the MFP 101. Note that a program for executing this process is stored in the flash memory 213, and is loaded into the RAM 211 at the time of execution and executed by the CPU 211.

[0145] First, in S2301, the CPU 211 starts an application stored in the mobile terminal 102. The application is started by the user operating the mobile terminal 102. Next, the process proceeds to S2302, where the CPU 211 determines whether or not a user ID for logging in to the MFP 101 is set. If it is determined that a user ID is not set, the process proceeds to S2303, where the CPU 211 prompts the mobile terminal 102 to set a user ID to be authenticated by the user, and then proceeds to S2302. Once the user ID has been set in this way, the process proceeds to S2304, where the CPU 211 determines whether a service UUID to be requested of the MFP 101 is set, in this case, whether a request for an authentication service to the MFP 101 is set. If it is determined that a service UUID is not set, the CPU 211 advances the process to S2305, where the CPU 211 prompts the user of the mobile terminal 102 to set a service UUID, and then proceeds to S2304. Once the service ID has been set in S2304, the process proceeds to S2306, where the CPU 211 transitions to a state in which it transmits an advertising packet.

[0146] Next, the process proceeds to S2307, where the CPU 211 waits to receive a Connect Req packet from the MFP 101. Upon receiving the Connect Req packet, the process proceeds to S2308, where the CPU 211 transitions to a state connected to the MFP 101. The process then proceeds to S2309, where the CPU 211 transmits a Connect Res packet to the MFP 101, and the process proceeds to S2310, where the CPU 211 waits to receive an authentication result indicating whether the login process was successful or not. Upon receiving the authentication result in S2310, the process proceeds to S2311, where the result is displayed on the operation unit 214 of the mobile terminal 102. Here, if the authentication is successful, for example, "Login has been completed" is displayed, and if the authentication is unsuccessful, "Login has failed" is displayed. The process then proceeds to S2312, where the CPU 211 transitions to an advertising state, and the process proceeds to S2307.

[0147] In this way, the user of the mobile terminal 102 can execute processing for logging in to the MFP 101 using the user ID set in the mobile terminal 102 simply by bringing the mobile terminal 102 close to the MFP 101 .

[0148] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0149] The present invention is not limited to the above-described embodiments, and various modifications and variations can be made without departing from the spirit and scope of the present invention. Therefore, the following claims are appended to apprise the public of the scope of the present invention. [Explanation of symbols]

[0150] 101...MFP, 102, 103...mobile terminal, 104...LAN, 105...wireless router, 201...CPU of MFP 101, 211...CPU of mobile terminal, 205, 214...operation unit, 302, 315...Bluetooth control unit

Claims

1. At least one computer included in the mobile terminal, An acquisition means for acquiring information based on a signal transmitted from an information processing device; a control means for controlling transmission of a login request to the information processing device based on a received signal strength of a signal transmitted from the information processing device satisfying a predetermined condition; A program that functions as a processing means for processing so that the predetermined condition is changed based on an instruction from a user.

2. The program described in claim 1, characterized in that, of the first range and second range in which the mobile terminal can receive the signal transmitted from the information processing device, the first range in which the mobile terminal can transmit the login request to the information processing device is closer to the information processing device than the second range in which the mobile terminal does not transmit login information to the information processing device.

3. 3. The program according to claim 2, wherein the predetermined condition corresponds to the mobile terminal entering the first range.

4. 4. The program according to claim 3, wherein the first range is changeable by a user.

5. The control means controlling the information processing device to transmit a login request when the received signal strength satisfies the predetermined condition and the information acquired by the acquisition means satisfies a specific condition; The program according to any one of claims 1 to 4, characterized in that when the received signal strength satisfies the specified condition and the information acquired by the acquisition means does not satisfy the specific condition, the program controls so as not to send a login request to the information processing device.

6. 6. The program according to claim 5, wherein the specific condition includes a condition that another user is not logged in to the information processing device.

7. The program according to claim 6, further comprising a display control means for controlling the display of information indicating that logging in to the information processing device is not possible when the received signal strength satisfies the specified condition and another user is logged in to the information processing device.

8. The program according to any one of claims 1 to 7, characterized in that the control means controls so as not to send a login request to the information processing device based on the received signal strength if the received signal strength does not satisfy the specified condition.

9. 9. The program according to claim 1, wherein the predetermined condition includes a condition that the received signal strength is equal to or greater than a predetermined strength.

10. 10. The program according to claim 1, wherein the predetermined condition includes a condition that the received signal strength is a strength corresponding to a distance between the information processing device and the mobile terminal being within a predetermined distance.

11. The program according to any one of claims 1 to 10, characterized in that the control means controls to send a login request to the information processing device based on the received signal strength when no other user is logged in to the information processing device.

12. 12. The program according to claim 1, wherein the control means controls the portable terminal so that, when transmitting the login request, identification information and a password of the user of the portable terminal are also transmitted.

13. The program according to any one of claims 1 to 12, characterized in that the control means controls whether or not to send the login request based on the received signal strength from an information processing device that has been pre-registered in the mobile terminal, and does not control the transmission of the login request based on the received signal strength from an information processing device that is not registered.

14. 14. The program according to claim 1, wherein the login request is a login request for enabling use of a function of the information processing apparatus by operating an operation unit of the information processing apparatus.

15. 15. The program according to claim 1, wherein the received signal strength is a received signal strength in Bluetooth Low Energy communication.

16. The program according to any one of claims 1 to 15, characterized in that the control means controls the transmission of the login request based on status information indicating whether other users are logged in to the information processing device, which is included in an advertising packet acquired from the information processing device.

17. 17. The program according to claim 1, wherein the information processing apparatus further comprises a print control unit that controls a printing unit to print an image on a sheet.

18. 18. The program according to claim 1, wherein the information processing apparatus further comprises a scan control unit that controls a reading unit to read an image on a document.

19. A method for controlling a mobile terminal, comprising: An acquisition step of acquiring information based on a signal transmitted from an information processing device; a control step of controlling to transmit a login request to the information processing device based on a received signal strength of a signal transmitted from the information processing device satisfying a predetermined condition; A processing step of processing so that the predetermined condition is changed based on an instruction from a user; A method for controlling a mobile terminal comprising:

20. A mobile terminal comprising each of the program means according to any one of claims 1 to 18.

21. A computer readable storage medium storing the program according to any one of claims 1 to 18.

Images