User authentication based on proximity of multifunctional device

Abstract

To provide a method and device for authentication based on proximity of a user and a multifunctional device.SOLUTION: A multifunction device (MFD) includes a local communication interface, a proximity sensor for detecting a user within a detection range, a processor, and a non-transitory computer readable medium for storing a plurality of instructions. The instructions make the processor execute operations including: detecting a user within the detection range through the proximity sensor; scanning a mobile device of the user about device identification information through the local communication interface; determining that the device identification information is associated with the user authorized for the MFD; and making the user automatically log in the MFD.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE This disclosure relates generally to multifunction devices, and more particularly, to methods and apparatus for proximity-based authentication of users and multifunction devices. [Background technology]

[0002] A multi-function device (MFD) can be used to perform a variety of different functions. For example, an MFD can print documents, copy documents, fax documents, scan documents, scan and email documents, etc. MFDs have evolved from isolated machines to more complex networked machines that can be connected to other MFDs or to print servers that can manage the operation of several different MFDs.

[0003] The MFD may also include a more complex user interface. The user interface may be customized for different users. A user may have a user account on the MFD, and the MFD may be customized based on the user account that is logged into the MFD. Summary of the Invention

[0004] According to aspects set forth herein, a multifunction device (MFD) and method for automatically logging in a user on the MFD based on proximity is provided. One disclosed feature of an embodiment is an MFD comprising a local communications interface, a proximity sensor for detecting a user within a detection range, a processor, and a non-transitory computer-readable medium storing a plurality of instructions. The instructions, when executed by the processor, cause the processor to perform operations including detecting a user within the detection range via the proximity sensor, scanning the user's mobile device for device identification information via the local communications interface, determining that the device identification information is associated with a user authorized for the MFD, and automatically logging the user into the MFD.

[0005] Another disclosed feature is a method of automatically logging in a user on the MFD based on proximity. The method performed by a processor of the MFD includes receiving a signal that a user is within detection range of a proximity sensor of the MFD, scanning the user's mobile device for a device identification via a local communications interface, determining that the device identification is associated with a user who is authorized for the MFD, and automatically logging the user into the MFD.

[0006] Another disclosed feature is a method for automatically logging in a user on an MFD based on proximity. The method, performed by a processor in a mobile device, includes detecting a multifunction device (MFD) Bluetooth signal broadcast in response to a proximity sensor in the MFD detecting a user of the mobile device within detection range, receiving a Bluetooth identification of the MFD, sending a request to automatically log in the user on an authorized MFD, and sending a pending print job to the authorized MFD. [Brief description of the drawings]

[0007] The teachings of the present disclosure can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which: [Figure 1] 1 illustrates a block diagram of an example network of the present disclosure. [Diagram 2] 1 illustrates a block diagram of an example MFD of the present disclosure. [Diagram 3] 1 illustrates, from the perspective of an MFD, a flow chart of a proximity-based method of automatically logging in a user on an MFD of the present disclosure. [Figure 4] 1 illustrates a flowchart of a proximity based method for automatically logging in a user on an MFD of the present disclosure from the perspective of the user's mobile device. [Diagram 5] FIG. 1 illustrates a high-level block diagram of an exemplary computer suitable for use in performing the functions described herein. To facilitate understanding, wherever possible, the same reference numbers have been used to designate the same elements that are common to the drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] This disclosure broadly discloses methods and apparatus for proximity-based authentication of users and multifunction devices. As discussed above, MFDs may also include more complex user interfaces. This user interface may be customized for different users. Users may have user accounts on the MFD, and the MFD may be customized based on the user accounts logged into the MFD.

[0009] However, currently, a user must manually log into the MFD. For example, a user may access a user interface of the MFD and enter a username and password. The user interface of the MFD may be relatively small, and entering a username and password using the MFD's small touch screen interface may be difficult. Furthermore, it may be cumbersome for a user to manually log into and out of the MFD each time they wish to use the MFD.

[0010] The present disclosure provides an apparatus and method for automatically logging a user into an MFD using proximity-based authentication. For example, the MFD can leverage short-range or local wireless communication with the user's mobile device to authenticate the user. The user can register his or her mobile device with the MFD, and the MFD can detect whether the mobile device is authorized to access the MFD based on information exchanged via short-range wireless communication and pre-registered information.

[0011] In addition, the MFD may include a proximity sensor. Thus, while short-range wireless communication may have a relatively long range, the proximity sensor may ensure that the user is present at the MFD. The combination of short-range wireless communication and the proximity sensor may ensure that the user is present at the MFD and automatically authenticate the user. Thus, the present disclosure may eliminate the need for a user to manually log into the MFD each time they wish to access the MFD.

[0012] 1 illustrates an example network 100 of the present disclosure. In one embodiment, network 100 may include one or more multifunction devices (MFDs) 1021 and 1022 (hereinafter also referred to individually as MFDs 102 or collectively as MFDs 102), one or more mobile devices 104 and 108, and an Internet protocol (IP) network 150. In one embodiment, IP network 150 may be any type of packet network. IP network 150 may include an application server (AS) 152 and a database (DB) 154.

[0013] It should be noted that IP network 150 is simplified for ease of explanation and may include additional networks and / or network components not shown. For example, IP network 150 may include additional access networks (e.g., a broadband access network, a cellular access network, etc.) or additional network elements (e.g., routers, border elements, firewalls, network switches, etc.).

[0014] In one embodiment, the AS 152 may be an authentication server or a print server that manages print jobs. For example, the AS 152 may manage print jobs of the MFDs 1021 and 1022 communicatively coupled to the IP network 150.

[0015] In one embodiment, DB 154 can store user account information and settings. For example, a user may store personalized workflow and / or user interface settings in DB 154. When a user logs into an MFD 1021 or 1022, the user settings can be retrieved from DB 154 and implemented on the MFD 1021 or 1022.

[0016] As mentioned above, network 100 may also include MFDs 1021 or 1022. Note that although two MFDs are illustrated in FIG. 1, any number of MFDs may be deployed in network 100. In one embodiment, MFDs 1021 or 1022 may be located in a common building, but may be located in different areas. For example, MFDs 1021 and 1022 may be located on different floors of a building, or at opposite ends of the same floor for different departments.

[0017] MFDs 1021 and 1022 may be electronic devices capable of performing a variety of different functions. For example, MFDs 1021 and 1022 may perform print, scan, copy, fax, scan to email, scan to cloud, etc. MFDs 1021 and 1022 may include printer hardware and / or document scanning hardware.

[0018] In one embodiment, the MFDs 1021 and 1022 may each include a local communications interface 112 (e.g., a Bluetooth (BT) transceiver), a user interface 114, and a proximity sensor (PS) 116. Note that while the user interface 114 is illustrated as part of the MFD 1021, the user interface may be presented on the mobile device 104. For example, a personalized user interface may be displayed on the mobile device 104 to allow the user 106 to provide input via the mobile device 104 rather than the user interface 114 of the MFD 1021.

[0019] In one embodiment, the proximity sensor 116 can wirelessly detect objects or people near the MFDs 1021 and 1022. In one embodiment, "near" can be defined as being within a detection range 118 of the proximity sensor 116. The detection range 118 can include a two-dimensional area or can include a set distance from the proximity sensor 116. The detection range 118 can be predefined (e.g., the range can be set via an installed application or user interface 114 of the MFD 102) or can be determined based on the type and / or range of the proximity sensor 116.

[0020] The proximity sensor 116 may be a sensitive proximity sensor, a capacitive proximity sensor, or a magnetic proximity sensor. Sensitive, capacitive, and magnetic proximity sensors may be used to detect nearby electrical devices such as the mobile devices 104 and / or 108. In another example, the proximity sensor 116 may be an ultrasonic proximity sensor to detect the presence of a user 106 or 110 near the MFD 1021 or 1022.

[0021] 2 illustrates a block diagram of one example of an MFD 1021 or 1022. In one embodiment, the MFD 102 may include a processor 202, a memory 204, a local communication interface 112, a wide area network (WAN) communication interface 212, a proximity sensor 116, a user interface 114, and a print / scan / copy component 218. The processor 202 may be communicatively coupled to the memory 204, the local communication interface 112, the WAN communication interface 212, the proximity sensor 116, the user interface 114, and the print / scan / copy component 218. The processor 202 may control operations for and / or send / receive data for automatically logging in a user 106 or 110 via the local communication interface 112, the WAN communication interface 212, the proximity sensor 116, the user interface 114, and / or the print / scan / copy component 218.

[0022] In one embodiment, communication interface 112 may be a wired or wireless communication interface. For example, local communication interface 112 may be a low energy signal, such as a Bluetooth® radio signal. Bluetooth radio signals may be broadcast within a particular frequency range (e.g., 2.40 GHz to 2.48 GHz) using the Bluetooth communication protocol.

[0023] In one embodiment, WAN communication interface 212 may be a wireless or wired connection for establishing a communication connection to IP network 150. For example, WAN communication interface 212 may be a WiFi wireless, an Ethernet connection, a fax over IP connection using an RJ-111 connection, cellular radio, etc.

[0024] As mentioned above, the proximity sensor 116 may be any type of sensor that detects the presence of an electronic device or a person. For example, the proximity sensor 116 may be an inductive proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor, an ultrasonic proximity sensor, etc.

[0025] In one embodiment, the user interface 114 may be a graphical user interface (GUI). The user interface 114 may be a touch screen interface or a GUI that receives input via a keyboard, mouse, trackpad, etc. The user interface 114 may provide notifications, prompts, and / or data fields for the user, as described herein. The user interface 114 may be configured based on personalization settings of the user 106 or user 110 after the user 106 or user 110 automatically logs into the MFD 1021 or 1022, as described in more detail below.

[0026] In one embodiment, print / scan / copy components 218 may include various components, as described above, for performing the print, scan, and copy functions of MFDs 1021 and 1022. For example, print / scan / copy components 218 may include various printing components, document scanning hardware, an optical scanner, a digital front end, a paper path, ink or toner, paper trays, one or more finishing modules, etc.

[0027] In one embodiment, memory 204 may be any type of non-transitory computer readable medium. For example, memory 204 may be a hard disk drive, a solid state drive, a random access memory, a read only memory, etc. Memory 204 may store instructions 206 and authorized device identification (ID) and / or users 208. In one embodiment, authorized device ID and / or users 208 may also be stored in DB 154 in IP network 150.

[0028] In one embodiment, the instructions 206 may be executed by the processor 202 to perform the functionality described herein for automatically logging in a user on the MFD based on proximity. For example, the instructions 206 may cause the processor to perform the operations of a method 300 illustrated in FIG. 3 and discussed in further detail below.

[0029] 1, in one embodiment, the MFDs 1021 and 1022 can automatically detect the proximity of the user 106 and / or 110 and automatically log the user 106 or 110 into the MFD 1021 or 1022. Additionally, the mobile devices 104 and 108 can include an application that can be used to automatically log into the MFD 1021 or 1022 based on detected proximity to the MFD 1021 or 1022. The application can be executed by a processor (not shown) of the mobile device 104 or 108.

[0030] Illustrative examples are described below with respect to MFD 1021. However, it should be noted that MFD 1022 is equally capable of performing the functions described herein.

[0031] In one embodiment, users 106 and 110 can pre-register their account information on the MFD 1021 or on the IP network 150 via the AS 152 and DB 154. The account information may include login information (e.g., username and password), mobile device identification information (e.g., a unique Bluetooth identifier), personalized user interfaces, personalized workflows, pending print jobs, and the like.

[0032] In one embodiment, the proximity sensor 116 of the MFD 1021 may continuously scan for a user (e.g., user 106 or 110) or a mobile device (e.g., mobile device 104 or 108). The user 106 may move within a detection range 118 of the proximity sensor 116. In response to detecting the user 106 and / or the mobile device 104, the local communication interface 112 may be activated to begin broadcasting a signal. For example, the signal may be a Bluetooth® signal to exchange information with the mobile device 104. The MFD 1021 may scan the mobile device 104 for a unique Bluetooth identifier associated with the mobile device 104.

[0033] In one embodiment, the MFD 1021 can locally store authorized users and associated Bluetooth identifiers associated with the users' mobile devices. In another embodiment, the MFD 1021 can store authorized users and associated Bluetooth identifiers in DB 154 in IP network 150. The MFD 1021 can match the Bluetooth identifier from the mobile device 104 against authorized device IDs / users 208 stored locally in memory 204 or can establish a communication path to the IP network 150 and match against the list stored in DB 154.

[0034] If a match is found for the Bluetooth identifier of the mobile device 104, the MFD 1021 may automatically log the user 106 into the MFD 1021. For example, the MFD 1021 may locally retrieve the username and password of the user 106 from memory 204 or DB 154 and automatically log the user 106 into the MFD 1021.

[0035] When a user 106 logs into the MFD 1021, the MFD 1021 can automatically configure the MFD 1021 according to information associated with the account of the user 106. For example, configuring the MFD 1021 can include configuring a user interface (the user interface 114 of the MFD 1021 or a user interface on the mobile device 104 of the user 106), retrieving and running any pending jobs associated with the user's account, providing custom notifications or status information, and the like.

[0036] For example, the personalized user interface may have a desired layout, a personalized arrangement of icons on the home screen, a desired language other than English, a desired color scheme, etc. After the user 106 logs into the MFD 1021, the MFD 1021 can retrieve the personalization settings associated with the user 106 from the AS 152 of the DB 154 and temporarily apply the personalization settings while the user 106 is logged into the MFD 1021. The MFD 1021 can also include personalized workflows within the user interface 114.

[0037] In one embodiment, configuring the MFD 1021 may include loading pending print jobs of the user 106 into a local print queue of the MFD 1021. For example, the user 106 may have sent a print job to the AS 152 in a managed print server environment. The MFD 1021 may retrieve any pending print jobs associated with the user 106's account when the user 106 automatically logs into the MFD 1021.

[0038] In one embodiment, configuring the MFD 1021 may include configuring the MFD 1021 to provide particular notifications or information based on the job type of the user 106. For example, the user 106 may be a technician. After the MFD 1021 automatically logs the user 106 into the MFD 1021, the MFD 1021 may determine that the user 106 is a technician based on the login information and may display status information of the MFD 1021 on the user interface 114 or send to the mobile device 104. For example, the status information may indicate any errors on the MFD 1021, the printing capabilities of the MFD 1021 (e.g., color printing, paper sizes available for printing, photo printing, etc.), the size of the print queue (e.g., the number of print jobs currently pending), etc.

[0039] The level of detail of the status information may be set based on the job type of the logged in user 106. For example, a technician may receive a notification with detailed error reports and system diagnostic information. A non-technical employee may receive general error information. Thus, if the user 106 is non-technical, the user 106 may be provided with enough information to indicate that the MFD 1021 is malfunctioning and may be provided with the option to redirect any pending print jobs to another printer (e.g., MFD 1022) that is functioning. In another example, the MFD 1021 may provide the non-technical user 106 with the print queue size and the option to redirect pending print jobs to another MFD 102 that may have a smaller print queue.

[0040] In one embodiment, while a user 106 is logged into the MFD 1021, a second user 110 may enter the detection range 118 of the MFD 1021. In one embodiment, the MFD 1021 may be configured to ignore the mobile device 108 of the user 110 if another user is already logged into the MFD 1021.

[0041] In one embodiment, the MFD 1021 may be configured to ignore the mobile device 108 if the user 110 is within the detection range 118 for a period of time less than a threshold (e.g., 5 seconds). For example, the user 110 may be walking by the MFD 1021.

[0042] In one embodiment, when the user 110 remains within the detection range 118, the MFD 1021 may emit a Bluetooth signal via the local communication interface 112 to scan for the mobile device 108. The MFD 1021 may display a notification on the user interface 114 that includes the Bluetooth identification information of the mobile device 104 and the mobile device 108. The notification may include an option to select whether the mobile device 104 or 108 should be logged into the MFD 1021.

[0043] For example, user 110 may simply stop to talk to user 106. User 106 may therefore select the Bluetooth identity of mobile device 104 and remain logged into the MFD 1021. In another example, user 110 may be waiting to use the MFD 1021 and user 106 may quit. User 110 may therefore select the Bluetooth identity of mobile device 108 to automatically log user 106 out and log user 110 into the MFD 1021.

[0044] In one embodiment, when multiple users are detected by the proximity sensor 116, a personal identification number associated with the user 110 may be requested via the user interface 114. The personal identification number may be a four-digit numeric code or any other alphanumeric passcode that may be stored in the memory 204 of the MFD 1021 or in the DB 154 within the user's account information. The personal identification number may prevent a user from accessing another user's account when the other user is within the detection range 118 of the MFD 1021.

[0045] In one embodiment, the automatic login may be controlled by an application on the mobile device 104. For example, the user 106 may enter the detection range 118 of the proximity sensor 116. In response, the MFD 1021 may broadcast a Bluetooth signal. The mobile device 104 may receive the Bluetooth identification information of the MFD 1021 and determine that the MFD 1021 is an authorized MFD. In other words, the user 106 is authorized to access the MFD 1021. A list of authorized MFDs may be stored locally in the memory of the mobile device 104 via the application.

[0046] The application can have the mobile device 104 send a request to automatically log the user in on the authorized MFD. The MFD 1021 can then check to see if the user 106 is authorized, as described above. If the user 106 is authorized, the MFD 1021 can automatically log the user 106 in to the MFD 1021. The user 106 can then send a pending print job to the authorized MFD 1021, or send other job requests that the MFD 1021 can execute.

[0047] Thus, the present disclosure provides an MFD 102 having a combination of a local communication interface 112 and a proximity sensor 116 to automatically log a user into the MFD 102. The combination of the proximity sensor 116 and the local communication interface 112 can help reduce energy consumption and ensure that the local communication interface 112 is activated when the user is near the MFD 102. For example, the local communication interface 112, such as a Bluetooth radio, can have a relatively wide range. However, the proximity sensor 116 can limit the detectable range 118 to an area in close proximity to the MFD 102 (e.g., immediately adjacent and up to 5 feet or less). This can prevent false detections when the user walks by the MFD 102, or constant processing by the MFD 102 to initiate an automatic login process when the user walks by the MFD 102. Typically, when the user intends to use the MFD 102, the user can be close to the MFD 102 (e.g., within 1-2 feet of the MFD 102).

[0048] As a result, the combination of the proximity sensor 116 and the local communications interface 112 can provide a convenient way for a user to automatically log into the MFD 102. This can create a more enjoyable and efficient user experience around the MFD 102.

[0049] 3 illustrates a flow chart of an example method 300 for automatically logging in a user on an MFD based on proximity of the present disclosure. In one embodiment, the method 300 may be performed by the MFD 102 or by an apparatus such as the apparatus 500 illustrated in FIG. 5 and discussed below.

[0050] In one embodiment, method 300 begins at block 302. At block 304, method 300 detects a user within a detection range via a proximity sensor. For example, the proximity sensor may detect when a user or electronic device is near the MFD (e.g., less than 5 feet away from the MFD).

[0051] In one embodiment, the proximity sensor may wirelessly detect objects or people near the MFD. In one embodiment, "near" may be defined as being within a detection range of the proximity sensor. The detection range may include a two-dimensional area or may include a set distance from the proximity sensor. The detection range may be predefined or may be determined based on the type and / or range of the proximity sensor.

[0052] The proximity sensor may be an inductive proximity sensor, a capacitive proximity sensor, or a magnetic proximity sensor. Inductive, capacitive, and magnetic proximity sensors may be used to detect nearby electrical devices, such as a user's mobile device. In another example, the proximity sensor may be an ultrasonic proximity sensor to detect the presence of a user near the MFD.

[0053] At block 306, the method 300 scans the user's mobile device for device identification information via the local communication interface. For example, detection of the user or the user's mobile device may activate the local communication interface. The local communication interface may be a Bluetooth radio operating on a radio frequency allocated for Bluetooth wireless communications. The MFD may broadcast a Bluetooth signal to establish communication with the user's mobile device.

[0054] The user's mobile device may be scanned via Bluetooth signals to capture the device identity of the mobile device. The device identity may be a unique Bluetooth identifier. However, other device identities, such as, for example, a device serial number, a media access control (MAC) identification number, etc., may also be used.

[0055] At block 308, the method 300 determines that the device identification is associated with a user that is authorized for the MFD. In one embodiment, the determination that the user is authorized may be made locally. For example, the MFD may store a list of authorized device IDs and / or users in the MFD's memory. The MFD may then compare the device identification of the mobile device to the stored list. If a match is found, the user may be authorized for the MFD.

[0056] In another embodiment, the MFD can establish a communications session with an authentication server or a print server via a wide area network communications interface. The authentication server may include a database that stores a list of authorized device IDs and / or users. The MFD can send device identification information to the authentication server to be matched against the list of authorized device IDs and / or users.

[0057] At block 310, the method 300 automatically logs the user into the MFD. For example, if the device identification matches an entry in a list of authorized device IDs and / or users, the MFD may automatically enter a username and password associated with the user into a login prompt on the MFD. In one embodiment, if authentication is performed remotely by an authentication server, the MFD may receive the username and password from the authentication server.

[0058] After a user logs into the MFD, the MFD can automatically configure portions of the MFD with account information associated with the user. If authentication is performed locally, the account information may be stored in memory of the MFD. If authentication is performed remotely, the MFD can request account information from an authentication server and then configure the MFD according to the account information. For example, the account information may include login information (e.g., username and password), mobile device identification information (e.g., unique Bluetooth identifier), personalized user interface, personalized workflows, pending print jobs, etc.

[0059] In one embodiment, configuring the MFD can include customization actions to personalize certain components of the MFD. For example, after a user automatically logs into the MFD, the MFD can apply the user's personalized user interface to the MFD's user interface. The personalized user interface can rearrange icons, display preferred icons on the home screen, display icons associated with personalized workflows, etc.

[0060] In one embodiment, configuring the MFD may include retrieving and executing pending jobs associated with the user's account. Pending jobs may be pending print jobs, retrieving scanned documents from other MFDs, etc. For example, the MFD may check a print server to see if there are pending print jobs associated with the user. If a pending print job is found, the pending print job may be retrieved and automatically executed to print the pending print job.

[0061] In one embodiment, the status of the MFD can be displayed to the user. This status may include any errors or pending print queue. The user may be presented with the option to redirect pending print jobs to a nearby MFD that has fewer pending print jobs in the print queue. Thus, using a combination of the proximity sensor and the local communications interface, the MFD can automatically log in a user, automatically configure the MFD based on account information, and / or automatically execute pending print jobs.

[0062] In one embodiment, when the user is finished on the MFD, the user may manually log out of the MFD. In another embodiment, the MFD may automatically log the user out of the MFD as soon as the user moves out of range of the proximity sensor. Thus, if the user moves away from the MFD without logging out, the MFD may detect the user's departure via the proximity sensor and automatically log the user out. At block 312, the method 300 ends.

[0063] 4 illustrates a flowchart of an example method 400 for automatically logging in a user on an MFD based on proximity of the present disclosure. In one embodiment, the method 400 may be performed by the mobile device 104 or 108, or by an apparatus such as the apparatus 500 illustrated in FIG. 5 and discussed below.

[0064] In one embodiment, method 400 begins at block 402. At block 404, method 400, via a mobile device processor, detects a multifunction device (MFD) Bluetooth signal that is broadcast in response to a proximity sensor of the MFD detecting a user of the mobile device within detection range. For example, a user may walk within detection range of the MFD's proximity sensor. In response, the MFD may activate a local communications interface to broadcast a signal (e.g., a Bluetooth signal) to scan for mobile devices.

[0065] At block 406, the method 400 receives a Bluetooth identification of the MFD. In one embodiment, the broadcast signal from the MFD may include the Bluetooth identification of the MFD.

[0066] At block 408, the method 400 determines that the MFD is an authorized MFD. For example, the mobile device may store a list of authorized MFDs in the mobile device's memory. The user may know which MFDs the user is authorized to use, which may include the Bluetooth identities of those MFDs. In one embodiment, an application on the mobile device may scan for the Bluetooth identities of authorized MFDs during a registration process performed by the application.

[0067] At block 410, method 400 transmits a request to automatically log the user in on the authorized MFD. If the MFD is an authorized MFD, the mobile device may transmit a request to the MFD to automatically log the user in to the MFD. For example, the mobile device may transmit a device identification (e.g., a Bluetooth identification of the mobile device) to the MFD. The MFD may then authenticate the user as described in method 300.

[0068] After the MFD automatically logs the user into the MFD, the MFD may be configured using the account information associated with the user. For example, the MFD's user interface may be personalized, the default language may be changed to the user's preferred language, pending print jobs may be automatically retrieved, etc.

[0069] At block 412, the method 400 sends the pending print job to the authorized MFD. For example, the mobile device may have pending print jobs stored locally within the mobile device. When the user logs into the MFD, the pending print job on the mobile device may be sent to the MFD for execution. When the user is finished, the user may log out of the MFD, or the MFD may automatically log the user out when the user moves out of range of the proximity sensor. At block 414, the method 400 ends.

[0070] FIG. 5 depicts a high level block diagram of a computer dedicated to carrying out the functions described herein. As shown in FIG. 5, the computer 500 includes one or more hardware processor elements 502 (e.g., a central processing unit (CPU), microprocessor, or multi-core processor), memory 504, e.g., random access memory (RAM) and / or read only memory (ROM), a module 505 for automatically logging in a user on the MFD based on proximity, and various input / output devices 506 (e.g., storage devices including, but not limited to, a tape drive, floppy drive, hard disk drive, or compact disk drive, receivers, transmitters, speakers, displays, voice synthesizers, output ports, input ports, and user input devices (keyboard, keypad, mouse, microphone, etc.)). It should be noted that while only one processor element is shown, multiple processor elements may be employed in the computer.

[0071] It should be noted that the present disclosure may be implemented in software and / or in a combination of software and hardware, for example using a programmable logic array (PLA) including an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a state machine deployed on a hardware device, a computer, or any other hardware equivalent, such as computer readable instructions that may accompany the methods discussed above and be used to configure a hardware processor to perform the steps, functions, and / or operations of the methods disclosed above. In one embodiment, instructions and data (e.g., a software program including computer executable instructions) for this module or process 505 for automatically logging in a user on the MFD based on proximity may be loaded into memory 504 and executed by the hardware processor element 502 to implement the steps, functions, or operations discussed above. Additionally, when a hardware processor executes instructions to perform an "operation," this may include the hardware processor directly performing the operation and / or facilitating, directing, or collaborating with another hardware device or component (e.g., a coprocessor, etc.) to perform the operation.

[0072] A processor that executes computer-readable or software instructions related to the above methods may be recognized as a programmed or specialized processor. Thus, the present module 505 for automatically logging in a user on an MFD based on proximity (including associated data structures) of the present disclosure may be stored on a tangible or physical (generally non-transitory) computer-readable storage device or medium, such as volatile memory, non-volatile memory, ROM memory, RAM memory, and magnetic or optical drives, devices, or diskettes. More specifically, a computer-readable storage device may comprise any physical device that provides the ability to store information, such as data and / or instructions, to be accessed by a processor or a computing device, such as a computer or application server.

[0073] It will be appreciated that variations of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements may be made thereafter by those skilled in the art that are intended to be encompassed by the following claims.

Claims

1. A multifunction device (MFD) having printing and scanning hardware, comprising: A local communication interface; A proximity sensor that detects a user within a detection range; A processor; and a non-transitory computer-readable medium storing a plurality of instructions, the plurality of instructions, when executed by the processor, causing the processor to: Detecting the user within the detection range via the proximity sensor; scanning the user's mobile device for device identification information via the local communications interface; determining that the device identification information is associated with the user who is authorized for the MFD; and automatically logging the user into the MFD.

2. The MFD of claim 1 , wherein the local communication interface includes a Bluetooth communication interface.

3. The MFD of claim 2 , wherein the device identification information includes a Bluetooth ID of the mobile device.

4. The MFD of claim 1 , further comprising a wide area network communication interface for establishing a connection to an authentication server.

5. The operations performed by the processor include: requesting account information associated with the user from the authentication server; The MFD of claim 4 , further comprising: configuring the MFD according to the account information.

6. Configuring the MFD in accordance with the account information includes: The MFD of claim 5 , further comprising performing operations further comprising applying the user's personalized user interface to a user interface.

7. Configuring the MFD in accordance with the account information includes: retrieving a pending print job for the user; and The MFD of claim 5 , further comprising: executing the pending print job for the user on the MFD.

8. A second user is detected within the detection range via the proximity sensor, and the operation performed by the processor includes the processor: determining a second device identification associated with a second mobile device of the second user; 2. The MFD of claim 1, further comprising: performing operations including: displaying a notification on the user interface having the device identification information of the mobile device of the user and the second device identification information of the second mobile device of the second user to enable the user to determine the device identification information associated with the user.

9. The operations performed by the processor include: The MFD of claim 8 , further comprising: if multiple users are detected within the detection range, requesting a personal identification number associated with the user.

10. 1. A method comprising: receiving, by a processor of a multifunction device (MFD), a signal that a user is within range of a proximity sensor of the MFD; scanning, by the processor, the user's mobile device for device identification information via a local communications interface; determining, via the processor, that the device identification information is associated with the user who is authorized for the MFD; and automatically logging the user into the MFD via the processor.

11. The method of claim 10 , wherein the local communication interface comprises a Bluetooth communication interface.

12. The method of claim 11 , wherein the device identification information includes a Bluetooth ID of the mobile device.

13. establishing, via the processor, a connection to an authentication server via a wide area network communication interface of the MFD; via the processor, requesting account information associated with the user from the authentication server; The method of claim 10 , further comprising: via the processor, configuring the MFD according to the account information.

14. configuring the MFD in accordance with the account information; The method of claim 13 , comprising applying, via the processor, a personalized user interface for the user to a user interface.

15. configuring the MFD in accordance with the account information; retrieving a pending print job for the user via the processor; and executing, via the processor, the pending print job for the user on the MFD.

16. receiving, via the processor, a second signal that a second user has been detected within the detection range via the proximity sensor; determining, via the processor, a second device identification associated with a second mobile device of the second user; 11. The method of claim 10, further comprising: displaying, via the processor, a notification on the user interface having the device identification information of the mobile device of the user and the second device identification information of the second mobile device of the second user to enable the user to determine the device identification information associated with the user.

17. The method of claim 16 , further comprising: via the processor, when multiple users are detected within the detection range, requesting a personal identification number associated with the user.

18. 1. A method comprising: detecting, via a mobile device processor, a Bluetooth signal of a multifunction device (MFD) broadcast in response to a proximity sensor of the MFD detecting a user of the mobile device within a detection range; receiving, via the processor, a Bluetooth identification information of the MFD; determining, via the processor, that the MFD is an authorized MFD; sending, via the processor, a request to automatically log in the user on the authorized MFD; and transmitting, via the processor, a pending print job to the authorized MFD.

19. 20. The method of claim 18, further comprising receiving, via the processor, status information of the MFD prior to sending the pending print job.

20. 20. The method of claim 19, further comprising, if the status information indicates that a print queue has a number of pending print jobs greater than a threshold, redirecting, via the processor, the pending print jobs to another authorized MFD.

Images