NON-NETWORKED MULTI-TENANT MULTI-FUNCTION DEVICES

Abstract

A non-networked multi-function device (MFD) is disclosed. For example, the non-networked MFD includes a communication interface to establish a communication session with a mobile endpoint device, a memory to store authentication information, and a processor. The processor is to receive a connection request from a mobile endpoint device, establish a connection with the mobile endpoint device, authenticate the mobile endpoint device via authentication information received from the mobile endpoint device that matches authentication information stored in the memory, provide available functions to the mobile endpoint device, receive a request from the mobile endpoint device to execute a function from the available functions, and execute the function.

Description

Claims

1. A non-networked multi-function device (MFD), comprising: a communication interface to establish a local communication session with a mobile endpoint device;a memory to store authentication information; anda processor to: receive a connection request from the mobile endpoint device;establish a connection with the mobile endpoint device via the local communication session;authenticate the mobile endpoint device via authentication information received from the mobile endpoint device that matches the authentication information stored in the memory;provide available functions to the mobile endpoint device;receive a request from the mobile endpoint device to execute a function from the available functions; andexecute the function.

2. The non-networked MFD of claim 1, wherein the communication interface comprises a near field communication interface, a Bluetooth radio, or a WiFi Direct connection.

3. The non-networked MFD of claim 1, wherein the communication interface comprises a combination of two or more of: a near field communication interface, a Bluetooth radio, or a WiFi Direct connection.

4. The non-networked MFD of claim 1, wherein the authentication information comprises a username and password.

5. The non-networked MFD of claim 1, wherein the authentication information comprises a key associated with a tenant of a multi-tenant building where the MFD is located.

6. The non-networked MFD of claim 1, wherein the processor is further to: disconnect the connection with the mobile endpoint device after the function is executed;receive a second connection request from a second mobile endpoint device;establish a second connection with the second mobile endpoint device via a second local communication session;authenticate the second mobile endpoint device via authentication information received from the second mobile endpoint device that matches the authentication information stored in the memory;provide available functions for the second mobile endpoint to the second mobile endpoint device, wherein the available functions for the second mobile endpoint device are different from the available functions for the mobile endpoint device that was previously connected;receive a request from the second mobile endpoint device to execute a function from the available functions for the second mobile endpoint device; andexecute the function from the available functions for the second mobile endpoint device.

7. The non-networked MFD of claim 1, wherein the processor is further to: track usage for different users; andgenerate a usage report for the different users.

8. The non-networked MFD of claim 1, wherein the processor is further to: lock a local user interface on the MFD while the connection with the mobile endpoint device is established.

9. The non-networked MFD of claim 1, wherein the available functions comprise job functions and workflows created by a user of the mobile endpoint device.

10. A method, comprising: receiving, via a process of a non-networked multi-function device (MFD), a connection request from a mobile endpoint device;establishing, via the processor, a connection with the mobile endpoint device;authenticating, via the processor, the mobile endpoint device via authentication information received from the mobile endpoint device that matches authentication information stored in a memory of the non-networked MFD;providing, via the processor, available functions to the mobile endpoint device;receiving, via the processor, a request from the mobile endpoint device to execute a function from the available functions; andexecuting, via the processor, the function.

11. The method of claim 10, wherein the connection comprises a near field communication session a Bluetooth radio, or a WiFi Direct connection.

12. The method of claim 10, wherein the connection comprises a combination of two or more of: a near field communication interface, a Bluetooth radio, or a WiFi Direct connection.

13. The method of claim 10, wherein the authentication information comprises a username and password.

14. The method of claim 10, wherein the authentication information comprises a key associated with a tenant of a multi-tenant building where the MFD is located.

15. The method of claim 10, further comprising: detecting, via the processor, that the mobile device is out of range of a communication interface of the MFD;disconnecting, via the processor, the connection with the mobile endpoint device.

16. The method of claim 15, further comprising: receiving, via the processor, a second connection request from a second mobile endpoint device;establishing, via the processor, a second connection with the second mobile endpoint device;authenticating, via the processor, the second mobile endpoint device via authentication information received from the second mobile endpoint device that matches authentication information stored in the memory;providing, via the processor, available functions for the second mobile endpoint device to the second mobile endpoint device, wherein the available functions for the second mobile endpoint device are different from the available functions for the mobile endpoint device that was previously connected;receiving, via the processor, a request from the second mobile endpoint device to execute a function from the available functions for the second mobile endpoint device; andexecuting, via the processor, the function from the available functions for the second mobile endpoint device.

17. The method of claim 10, further comprising: tracking, via the processor, usage for different users; andgenerating, via the processor, a usage report for the different users.

18. The method of claim 10, further comprising: locking, via the processor, a local user interface on the MFD while the connection with the mobile endpoint device is established.

19. The method of claim 10, wherein the available functions comprise job functions and workflows created by a user of the mobile endpoint device.

20. A non-networked multi-function device (MFD), comprising: a communication interface to establish a local communication session with a mobile endpoint device;a memory to store authentication information associated with a plurality of different tenants of a multi-tenant office building where the MFD is located; anda processor to: receive a connection request from a first mobile endpoint device associated with a first tenant of the plurality of different tenants;establish a first connection with the first mobile endpoint device;authenticate the first mobile endpoint device via first authentication information received from the first mobile endpoint device that matches authentication information associated with the first tenant stored in the memory;provide available functions associated with the first tenant to the first mobile endpoint device;receive a first request from the first mobile endpoint device to execute a first function from the available functions associated with the first tenant;execute the first function;disconnect the first connection;receive a second connection request from a second mobile endpoint device associated with a second tenant of the plurality of different tenants;establish a second connection with the second mobile endpoint device;authenticate the second mobile endpoint device via second authentication information received from the second mobile endpoint device that matches authentication information associated with the second tenant stored in the memory;provide available functions associated with the second tenant to the second mobile endpoint device, wherein the available functions associated with the first tenant are different from the available functions associated with the second tenant;receive a request from the second mobile endpoint device to execute a second function from the available functions associated with the second tenant;execute the second function.