Patent Application
20090228962
None.
This invention pertains to methods, apparatus and software for improved security and other benefits in the remote management of imaging devices, multi-function peripherals (“MFP”) and the like over a network.
Remote management of MFP's and other imaging devices is advantageous for several reasons. It is time consuming and often impractical for managers to have to physically get in front of each MFP to interact with the front panel interface. While remote management of devices offers great benefits like flexibility, convenience and efficiency, it also exposes the devices to security risks. “Remote front panel” is an important feature of remote management capability. Historically, user had to walk up to the MFP and manually operate the front panel on the device to accomplish many configuration and troubleshooting activities. Now these tasks can be performed remotely, but the tools lack adequate security mechanisms to prevent unauthorized access to remote front panel applications. Additional problems and limitations of the prior art are discussed below.
The present disclosure, in various embodiments and implementations, pertains to improvements in remote device management, including but not limited to improvements in security, to prevent unauthorized remote management activity. Another aspect of the present disclosure provides for tracking remote device access activity. Still a further aspect of the present disclosure addresses the problem of resolving simultaneous access to the same device either remotely or through a combination of remote and local access. Yet a further aspect of this disclosure relates to enabling concurrent remote access to multiple devices using a single login procedure.
Additional aspects and advantages of this invention will be apparent from the following detailed description of preferred embodiments, which proceeds with reference to the accompanying drawings.
In this application, we will simply use the term “MFP” to mean any imaging device, including but not limited to multi-function peripheral devices, that is capable of remote management. While MFP's often are connected to a network, e.g., via an Ethernet or wireless interface, we also include in our definition devices that may be directly connected to a user's computer or server, sometimes called attached or local peripherals. In such cases, attached devices are accessible through a network to which the host computer is coupled, and thereby can be accessed remotely.
We use the term “remote management” herein to refer to management of an MFP through a software interface running on a device (typically a computer) other than the MFP itself. The term “remote” in other words means interacting with the MFP though an electronic interface other than manually operating a front panel on the machine. “Management” of a peripheral for present purposes refers broadly to any interaction (unidirectional or bidirectional) with the peripheral for a purpose other than simply sending a user job for processing, such as a print or fax job. Management of an MFP can include without limitation changing configuration settings, collecting current status or operating statistics, and troubleshooting various potential MFP problems.
Limited technologies exist for remote control of certain devices. In general, known remote management solutions require a user login, and password or similar validation, each time a user remotely accesses a given device. To access a second device, the user must “start over” and has to separately log into the second device, often using a different user name, password or other credentials to access the second device. Examples of such solutions are disclosed, for example, in JP 2005-011090, JP 2006-246408 and others. Additional prior art references can be found in the record of the present application.
In the network 100, there are computers 102, 104 or other computing devices, interconnected via the medium 110. The number of such devices is immaterial here. The network 100 may also include one or more servers 106. Computer 108 may be a user (client) machine with an attached printer 130. In another implementation, computer 108 may serve as a network printer server/spooler for utilization of the printer 130. The network 100 also includes at least one MFP 120, 122 which can be remotely accessed as explained below.
In some implementations, the MFP 122 may be managed from a client device, for example 102, while in other systems the MFP may be managed from a remote location via the local network interface 140, for example in the case of a WAN. In some embodiments, a user/manager can access multiple different MFP's from any location on the network, using a single login, as further explained below.
The device view display 400 also includes an “RFP” or remote front panel action button 410. When the user clicks this button 410, the graphical remote front panel display for the current device is displayed and becomes active. Preferably, the device view module will launch the remote front panel as a new process which runs in a separate browser or window. Details of such a display are known, and may employ, for example, HTML technologies for interacting with the remote MFP. However, before RFP is enabled, the capability is subject to access control as follows.
Referring again to
In
Preferably, the user need only log into the device management application 300 once in order to gain access to all remote devices the user is authorized to access in accordance with that user's credentials. The access control module 310 also manages the MFP or device credentials. An MFP credential as used herein is the information needed for a user to login to a corresponding MFP device. Typically, each MFP (120, 122 in
The access control module 310 implements a mechanism by which service level users can provide the necessary MFP credentials, just one time (until an update is needed). The access control module stores the MFP credentials in the user profile database 312. Once the user is logged in to the management application, the user can switch MFP's or access additional MFP devices as needed, without additional login procedures or credentials. Instead, the access control module will fetch the username and password information appropriate to each device the user seeks to access. The access control module preferably interacts with each remote device, performing the required login procedure in each instance for the user automatically. These credentials can be stored in the user profile database 312. The database is maintained and update as appropriate by the access control module. In this way, the user need not remember or provide login information separately for each MFP device.
There may be, in some embodiments, multiple levels or classes of users or user privileges. In one example, a “general user” in one scheme is permitted to access only a limited amount of information about an MFP device, and they may not have permission to perform any action on that device. For example, they might view a job queue or toner level, but lack authority to change configurations or cancel a job. In fact, to access generic information, login may not be required at all. In another case, “service level” users will have access to more detailed information about the device, and will have permission to perform certain actions on the device such as upgrading the firmware, changing device settings or rebooting the device.
These features can be implemented using the software described above. Separate login for particular features or services on a device need not be required of the user. Rather, automatic login will be conducted on behalf of the user by the management application as needed. Once the user has logged into the management system, that user's privileges for each device (in the device list 306) are known the access control module. That module, in turn, may interact with the device view module to modify the device view display in accordance with the user's credentials for each device. In the example above, the user is granted (or denied) front panel access entirely, and this is reflected in the device view by displaying (or not) the front panel access action button. In another example, even though the user has front panel access, only certain actions may be permitted by her credentials. In some embodiments, those limitations may be reflected by modifying the front panel display presented to the user. Specific variations in the user interface display can be arranged by those skilled in the art in view of the present disclosure.
When a user directly accesses the physical front panel of an MFP device, and a second user or application remotely accesses the same device, a conflict can arise. Similarly, remote access my multiple users can result in conflicts. In one embodiment, the present software can prevent multiple simultaneous accesses to the front panel (physical or virtual) of a particular MFP. In order to avoid multiple concurrent accesses to the front panel of the same MFP device, in some embodiments, the access control module ensures that only one window or browser is open for a given MFP at one time. This is one additional benefit of the centralized management system disclosed herein. If a remote front panel is already open in a current window or browser (or other textual, graphic or equivalent UI), a request by a user for front panel access to the same device (e.g. clicking the RFP button) will be denied. In some implementations, concurrent use prevention is conveniently supported by interaction with user access tracking and logging, described below.
The access control module preferably also ensures that if a front panel is being accessed locally (manually), then it denies remote access to the same device until the local front panel is closed. When the user clicks on the RFP button, the access control model in one embodiment first checks via the network to determine whether the corresponding physical front panel is then being accessed locally. Only if the physical front panel is not being accessed locally, the device view module will launch the separate process to run RFP for that device. Otherwise, it may display a message to the user that the front panel is not currently available for remote access.
Most device management applications display the remote front panel as part of the parent user interface (“UI”) screen. For example, they display the remote front panel as a frame within a browser or as a UI control within the Windows® UI. This restricts the user to accessing only one device remote front panel at a time. In accordance with some embodiments of the present invention, as mentioned above, when the user activates a remote front panel button, the device view module preferably launches the RFP as a new process in a separate browser. This embodiment enables the user to launch as many simultaneous front panel interfaces as needed. Thus the user can manage multiple MFP devices simultaneously.
Remote front panel is a powerful feature by which a user gains access to various features of a device from a remote location. For example, RFP can be used to change or update firmware, change settings, reboot the device, and even disable the device completely. With these capabilities come serious security risks, as mentioned earlier. The access control software and methods described above help to address those risks. It would also be helpful to track which users are remotely accessing which devices, and in some embodiments logging what specific actions those users are taking. Toward that end, we refer once again to
In one embodiment, the log file module 322 maintains two log files, namely backup and running log files. The size of these files preferably is configurable by user. Log file module uses the running log file to log access information as described on an ongoing basis. Whenever this file size exceeds the predetermined limit, the log file module copies the contents of the log file into the backup log file. After backup, the running log contents may be deleted or over-written going forward to make space for new data. Many different variations and details for data storage are known and are omitted here so as to avoid obscuring the present inventive disclosure.
A user logs into the management application, step 206, and then selects a device or MFP in step 208. In some embodiments, a list of candidate devices may be displayed to the user. The system checks the user profile credentials for authorization to remotely access the selected device, step 210. If the user is not so authorized, the system may display a message to that effect, step 212, and then loop back to invite another selection at 208. If the user is authorized to access the selected device, the system checks for a conflict at 220, such as a prior user already logged into that same device. This conflict check may be done in various ways. In one example, a device list database is updated to maintain current information including front panel login status. The device list status may be updated on a scheduled or interrupt basis. In an alternative embodiment, the management application may query the selected device in real time to check the current front panel login status. If there is a conflict, a message may be displayed at 222, and again control loops back to 208 to invite a different selection.
If there is no conflict at step 220, the application displays a device view screen for the selected device, step 224. If remote front panel access is permitted, an RFP action button or equivalent user input means may be included in the screen display. The user may then invoke a remote front panel process, step 226, for remote management operations. At that point, the management application looks up the user login credentials for the selected device and conducts automatic login, step 228. The user can then access the front panel to manage the selected device, step 240. The user may request access to a second device, step 242. If so, the application loops via path 250 back to step 208 to enable selection of a second device. The prior RFP may remain open with access to the first device. The process outlined above continues with regard to the second selected device. assuming no conflict, proper credentials, etc., a second RFP window can be opened, and indeed additional windows can be opened so as to enable concurrent remote access to multiple remote devices. The number of such devices is not limited.
It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments without departing from the underlying principles of the invention. The scope of the present invention should, therefore, be determined only by the following claims.
