CLONING SYSTEM AND METHOD FOR MULTIFUNCTION PERIPHERALS

Abstract

A system and method for multifunction peripheral cloning includes a device controller with a processor and associated memory and a network interface. Device configuration data is stored on the device for configuring device components such as a scan engine and a print engine. A controller processor of a multifunction peripheral designated as a leader device generates a master clone file from a copy of its device configuration data and communicates it to at least one networked multifunction peripheral via the network interface via a push to targeted devices or responsive to a request for a copy of the master clone file from follower devices.

Claims

1. A multifunction peripheral comprising: a device controller including a processor and associated memory configured to store device configuration data; a network interface; the processor configured to reconfigure the multifunction peripheral with received configuration data; a scanner configured in accordance with received configuration data; a printer configured in accordance with the received configuration data; wherein, when the multifunction peripheral is designated as a leader, the processor is further configured to generate a cloning copy of a device configuration of the reconfigured multifunction peripheral, receive a cloning copy request from each of a plurality of networked multifunction peripherals; communicate the cloning copy of the device configuration data to each of the plurality of networked multifunction peripheral via the network interface responsive to each cloning copy request, and upload the cloning copy to an associated cloud server; wherein, when the multifunction peripheral is designated as a follower, the processor is further configured to send a cloning file request to a designated leader multifunction peripheral, send a cloning file request to a cloud server when no cloning file is received responsive to a cloning file request to the designated leader multifunction peripheral, receive a cloning file, and reconfigure the multifunction peripheral with a received cloning file; wherein the controller is configured to scan a tangible document into electronic form via operation of the configured scanner; wherein the controller is configured to print a tangible document from an electronic document via operation of the configured printer.

2. The multifunction peripheral of claim 1 wherein the memory further stores received device identification data for each networked multifunction peripheral, and wherein the processor is further configured to send each copy of the received device configuration data to each networked multifunction peripheral in accordance with the device identification data.

3. (canceled)

4. (canceled)

5. (canceled)

6. The multifunction peripheral of claim 1 wherein the memory stores data corresponding to a synchronization schedule, and wherein the processor is further configured to communicate each copy of the cloning file to each one networked multifunction peripheral in accordance with the synchronization schedule.

7. The multifunction peripheral of claim 1 wherein the clone file is comprised of device configuration data copied from memory firmware.

8. A method comprising: storing received device configuration data in a memory of a multifunction peripheral; reconfiguring the multifunction peripheral in accordance with received device configuration data, the reconfiguring including configuring a scanner of the multifunction peripheral in accordance with the received device configuration data and, configuring a printer of the multifunction peripheral in accordance with the received device configuration data; when the multifunction peripheral is designated as a leader, generating a cloning copy of a device configuration of the reconfigured multifunction peripheral via a processor, uploading the cloning copy to an associated cloud server, receiving a cloning copy request from each of a plurality of networked multifunction peripheral and communicating the cloning copy to each requesting networked multifunction peripheral via a network interface; when the multifunction peripheral is designated as a follower sending a cloning file request to a designated leader multifunction peripheral, sending a cloning file request to a cloud server when no cloning file is received responsive to a cloning file request sent to the leader multifunction peripheral, receive a cloning file, and reconfigure the multifunction peripheral with a received cloning file, scanning a tangible document into electronic form with a configured scanner; and printing a tangible document from an electronic document with a configured printer.

9. The method of claim 8 further comprising: storing device identification data for each networked multifunction peripheral in the memory; and sending cloning file to each networked multifunction peripheral in accordance with corresponding device identification data.

10. (canceled)

11. (canceled)

12. (canceled)

13. The method of claim 9 further comprising: storing data corresponding to a synchronization schedule; and communicating the cloning copy to each networked multifunction peripheral in accordance with the synchronization schedule.

14. (canceled)

15. (canceled)

16. (canceled)

17. (canceled)

18. (canceled)

19. (canceled)

20. (canceled)

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Various embodiments will become better understood with regard to the following description, appended claims and accompanying drawings wherein:

[0007] FIG. 1 an example embodiment of a cloning system;

[0008] FIG. 2 is an example embodiment of functional device components of a multifunction peripheral;

[0009] FIG. 3 is a flowchart of operations of an example embodiment of a device controller;

[0010] FIG. 4 is an example embodiment of a master clone list; and

[0011] FIG. 5 is an example embodiment of a master clone assignment list.

DETAILED DESCRIPTION

[0012] The systems and methods disclosed herein are described in detail by way of examples and with reference to the figures. It will be appreciated that modifications to disclosed and described examples, arrangements, configurations, components, elements, apparatuses, devices methods, systems, etc. can suitably be made and may be desired for a specific application. In this disclosure, any identification of specific techniques, arrangements, etc. are either related to a specific example presented or are merely a general description of such a technique, arrangement, etc. Identifications of specific details or examples are not intended to be, and should not be, construed as mandatory or limiting unless specifically designated as such.

[0013] In accordance with the subject application, FIG. 1 illustrates an example embodiment of a MFP device cloning system 100 including two or more MFPs as illustrated by MFPs 104, 108 and 112. MFPs are suitably connected for data communication among and between them with any suitable wireless or wired data interfaces. In the example embodiment of FIG. 1, the MFPs are members of a local area network (LAN) serviced by network router 116 which also suitably provides a gateway to a wide area network (WAN) 120 which suitably comprises data communication via the Internet. MFP service manager 124 can access MFP configurations via any suitable network connection. Remote connection can allow a technician to configure devices without the need to physically access them. While remote configuration is an improvement, it still requires a technician to login to each device to complete configuration. This would need to be done for each device each time a system-wide configuration modification is desired by a device user.

[0014] In the example embodiment of FIG. 1, a master clone file is created. The master clone file is comprised of an electronic backup file that contains MFP settings and may also include device firmware. Master clones are suitably created by a technician who accesses a device's web interface or a device management cloud service 128. To create a master clone through the device web interface, a service manager logs in to the web interface and requests for a master clone file to be created. The device creates the master clone file from its current settings and makes it available for download. To create a master clone through the device management cloud service 128, the service manager suitably logs in to the device management cloud service 128 and requests for a master clone to be created. The device then creates a master clone and uploads it to the device management cloud service 128. Master clones can then be applied to other devices through their web interfaces or the device management cloud service 128. This allows multiple MFPs to be quickly and easily created to mirror a source device's settings.

[0015] By way of further example, in the illustration of FIG. 1, a service manager 124 designates a leader MFP device and one or more follower MFPs. In the example, MFP 104 is designated as the leader device which, in turn, creates a master clone and uploads it to device management cloud service 128. Each follower device, MFPs 108 and 112 in the illustrated example, periodically check for a new master clone on the leader device. This may be accomplished at any suitable schedule which may be set on each MFP or following a prompt from device management cloud service 128. If a follower device cannot find the leader device on the local area network, it suitably checks device management cloud service 128 for a new master clone. In ether event, if there is a new master clone, the follower device will download and apply the master clone.

[0016] Turning now to FIG. 2, illustrated are functional device components 200 suitably comprising a multifunctional peripheral such as MFPs 104, 108 and 112 of FIG. 1. Included is controller 201 comprised of one or more processors, such as that illustrated by processor 202. Each processor is suitably associated with non-volatile memory such as ROM 204, and random access memory (RAM) 206, via a data bus 212.

[0017] Processor 202 is also in data communication with a storage interface 208 for reading or writing to a storage 216, suitably comprised of a hard disk, optical disk, solid-state disk, cloud-based storage, or any other suitable data storage as will be appreciated by one of ordinary skill in the art.

[0018] Processor 202 is also in data communication with a network interface 210 which provides an interface to a network interface controller (NIC) 214, which in turn provides a data path to any suitable wired or physical network connection 220, or to a wireless data connection via wireless network interface 218. Example wireless connections include cellular, Wi-Fi, Bluetooth, NFC, wireless universal serial bus (wireless USB), satellite, and the like. Example wired interfaces include Ethernet, USB, IEEE 1394 (FireWire), Apple Lightning, telephone line, or the like.

[0019] Processor 202 can also be in data communication with any suitable user input/output (I/O) interface 219 which provides data communication with user peripherals, such as displays, keyboards, mice, track balls, touch screens, or the like.

[0020] Also in data communication with data bus 212 is a document processor interface 222 suitable for data communication with MFP functional units 250. In the illustrated example, these units include copy hardware 240, scan hardware 242, print hardware 244 and fax hardware 246 which together comprise MFP functional hardware 250. It will be understood that functional units are suitably comprised of intelligent units, including any suitable hardware or software platform.

[0021] Hardware monitors suitably provide device event data, working in concert with suitable monitoring systems. By way of further example, monitoring systems may include page counters, sensor output, such as consumable level sensors, temperature sensors, power quality sensors, device error sensors, door open sensors, and the like. Data is suitably stored in one or more device logs, such as in storage 216.

[0022] FIG. 3 is a flowchart of operations 300 of example embodiments of the device controllers in connection with the MFPs of FIG. 1. Each device commences the process at block 304 and a determination is made at block 308 as to whether a master clone policy has been implemented. If not, the process ends at block 312. If it determined that a master clone policy exists at block 308, then a determination is made as to whether the MFP is a follower at block 316. If not, then the device is designated a leader device and a master clone file is created and uploaded to the device management cloud service at block 320 and the process ends at block 312. If the device is designated as a follower as determined at block 316, then a determination is made as to whether the device can access a leader MFP at block 324. An identifier, such as a network address, of a leader MFP is suitably preset in each follower MFP, or placed in a network repository where it can be pulled by each follower MFP. Alternatively, when a device is designated as a leader MFP, it suitably broadcasts its identity to corresponding follower MFPs.

[0023] If the determination made at block 324 is that a leader MFP is accessible, or defined, then the master clone file is downloaded from the leader MFP at block 328 and this is applied to the device at block 332. The process then ends at block 312. If no leader MFP is accessible or defined, a master clone file is suitably downloaded from the device management cloud service at block 336 and this file is applied to the device instead at block 332. The process then terminates at block 312.

[0024] FIG. 4 illustrates an example embodiment of a master clone list 400 such as may be available to a service manager. Master clone files are identified in column 410 and a corresponding device type appears in column 420. A corresponding firmware version appears in column 430. A corresponding device description is suitably provided in column 440 and a creation date for a current master clone file appears in column 450. In the illustrated example, there may be more than one leader clone device.

[0025] A device may serve as a leader for a subset of devices, such as those devices that are identical to it or devices that are located on a particular premises. Leader devices may also be selected to balance workloads for distribution of clone files when a large number of follower devices exist.

[0026] FIG. 5 illustrates an example embodiment of a master clone assignment list 500 such as may be available to a service manage. Column 510 lists compatible devices and a corresponding model type appears at column 520. Firmware versions appear in column 530 and a description may be provided at column 540. Finally, a creation date is suitably specified at column 550.

[0027] While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the spirit and scope of the inventions.