Abstract:
A network document processing device includes an embedded controller. The controller monitors one or more document processing devices occurring on the device. The controller is further operable to probe one or more networked document processing devices to determine if it or they are operable to monitoring other network document processing devices. If not, the controller suitably undertakes monitoring of some or all of the networked devices. This monitoring may be concluded when another document processing device becomes active. Multiple document processing devices may also share all or part of monitoring of document processing devices for redundancy, load sharing or integrity checking

Description:
TECHNICAL FIELD 
       [0001]    The subject application teaches example embodiments that relate generally to monitoring of networked document processing devices. 
       SUMMARY 
       [0002]    In an example embodiment, a document processing device includes an embedded controller, memory and a network interface, and a monitor to monitor internal document processing operations completed by the document processing device. The embedded controller generates internal device operation data in accordance with an output of the monitor and receives networked device operation data corresponding to associated document processing operations from at least a second networked document processing device. The embedded controller further processes internal device operation data. The memory stores identity data representative of at least a second networked document processing device configured for processing of device operation. The embedded controller initiates a network probe to the second networked document processing device in accordance with the identity data to determine whether the second networked document processing device is operational for processing of device operation data. The embedded controller processes internal and networked device operation data when the probe indicates that the second networked document processing device is not operational. In an embodiment, the embedded controller initiates the probe based on prescribed timing. In an embodiment, network device operation data includes data about document processing operations completed by the second networked document processing device. In an embodiment, the embedded controller is in data communication with, and receives parameter data from, an administrative control via the network interface. The embedded controller receives network device operation data from a plurality of networked document processing devices identified in the received parameter data. In an embodiment, the embedded controller cedes processing of networked device operation data to the second networked document device when the probe results indicate that the second networked document processing device is operational. In an embodiment, the embedded controller receives data corresponding to the prescribed timing from the administrative control terminal. In an embodiment, the embedded controller receives content data from the administrative control terminal that specifies the content of the networked device operation data. 
         [0003]    In another example embodiment, a method includes monitoring internal document processing operations by a document processing device, and generating internal device operation data based on the monitored operations. The method further includes generating, by an integrated controller, a probe that includes probe data corresponding to operation of at least a second document processing device of a number of document processing devices, and outputting the probe onto a network via a network interface. The method further includes receiving remote device operation data via the network interface from at least one of the document processing devices when the probe indicates that at least the second document processing devices is not operational for processing document operation data, and processing internal and networked device operation data by the integrated controller upon receiving the remote device operation data. In an embodiment, the method includes monitoring internal document processing operations such as photocopying, printing, faxing, or scanning In an embodiment, the method include generating the internal device operation data that includes internal page count data, receiving networked device operation data that includes networked page count data, and outputting report data processed from the internal and networked device operation data. In an embodiment, the method further includes sending the report data to an administrator. In an embodiment, monitoring internal document processing operations includes monitoring consumables. In an embodiment, monitoring internal document processing operations includes monitoring paper, ink, or toner. 
         [0004]    In an example embodiment, a document processing device includes a controller, a memory, a network interface, and a monitor that monitors document processing operations of the document processing device. The network interface is configured to allow data communication with local networked document processing devices using a local area network, and remote networked document processing devices using a remote local area network. The controller generates internal device operation data based on the output of the monitor, and processes the internal device operation data. The controller receives remote operation data for document processing operations of a document processing device in the local area network and a document processing device from the wide area network. The memory stores identity data of a second networked document processing device that processes device operation data of multiple networked document processing devices. The controller initiates a probe, via the network interface, to the second networked document processing device based on the stored identity data to determine whether the second networked processing device is operational for processing of the device operation data of the multiple networked document processing devices. The controller is configured to process internal and remote device operation data when the problem indicates the second networked device is not operational for processing device operation data. In an embodiment, the controller can initiate the probe via the wide area network interface. In an embodiment, the probe is a Simple Network Management Protocol Request (SNMP request). In an embodiment, the controller receives an ordered device list and suppresses probe initiation when an internal identifier of the document processing device is identified as the primary controller device in the list. In an embodiment, the controller processes at least a portion of the internal and remote device operation data cooperatively with one or more load-sharing document processing devices. 
         [0005]    In an example embodiment, a document processing system includes a number of multifunction peripherals, each of which include an embedded controller having a processor and a memory, a network interface capable of communicating with one or more networked multifunction peripherals, and an embedded monitor for monitoring internal document processing operations completed by the multifunction peripheral itself and at least one of the networked multifunction peripherals. The embedded controller generates internal device operation data based on the output of the embedded monitor, and receives networked device operation data regarding document processing operations for one or more of the networked multifunction peripherals. The embedded controller processes internal and networked device operation data which is output via the network interface. In an embodiment, the network interface receives monitor instruction data, and the controller selectively enables or disables processing of networked device operation data in response to the received monitor instruction data. 
       BACKGROUND 
       [0006]    Document processing devices are in widespread use in many businesses and office settings. Such devices include copiers, scanners, printers and facsimile machines. Today, one or more functions associated with such devices are combined in a single unit, referred to as multifunction peripheral (“MFP”). 
         [0007]    Document processing devices can be not only costly to purchase, but also expensive to maintain. This is particularly true in connection with devices that include moving, mechanical parts such as are necessary for interacting with tangible media, such as paper, film, transparencies or interfacing with removable media, such as removable drives, memory cards, flash memory devices, bar code readers, magnetic card readers, and the like. Devices require periodic maintenance operations which may include cleaning, resupplying, repairing or upgrading. Failure to provide maintenance in a timely manner can result in significant expense for repair or loss of device use. 
         [0008]    Operations such as printing, faxing or copying may include depletion of consumables, such as paper, ink or toner. Monitoring of device operation facilitates replacement of such consumables. In other situations, monitoring of device operation facilitates assessing charges for device use. In other situations, monitoring of device operation facilitates imposition of usage quotas. 
         [0009]    Document processing devices may include counters or other usage monitoring systems to allow for attending to maintenance or servicing operations at known intervals. An administrator would approach individual devices to determine a level of usage from its associated monitor. Third party vendors, such as Pharos™ and PaperCut™, provide solutions for centrally managing jobs, tracking usage for a number of MFPs, and enforcing usage quotas among those MFPs. However, third party solutions require a dedicated server for performing those tasks. A dedicated server not only increases management costs, but also introduces a potential point of failure in the network. When all jobs are routed through a single monitor, failure of a network or failure of a monitoring workstation would either stop document processing operations or result in lost monitoring data during the outage. In some instances, the dedicated server may be managed by a third party, further complicating management for IT professionals within an organization. Also, depending upon the capabilities of the MFP and the configuration of the network, users may be able bypass a third party&#39;s dedicated server and print to a MFP directly, which can lead to quotas not being enforced properly or job accounting discrepancies that must be rectified. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0010]      FIG. 1  is a diagram of an example of a document processing system that includes a multifunction peripheral. 
           [0011]      FIG. 2  is a block diagram of an example of components of a multifunction peripheral. 
           [0012]      FIG. 3  is a block diagram of an example of functional components of a multifunction peripheral. 
           [0013]      FIG. 4  is a diagram of an example of a networked document processing system. 
           [0014]      FIG. 5  is a diagram of an example of a networked document processing system. 
           [0015]      FIG. 6  is a flow diagram of an example process for assignment of data collectors. 
           [0016]      FIG. 7  is a flow diagram of an example process for data collection. 
           [0017]      FIG. 8  is a diagram of an example template for specification for data collection. 
           [0018]      FIG. 9  is an example specification for data collection. 
           [0019]      FIG. 10  is an example specification for hierarchical assignment of data collectors. 
       
    
    
     DETAILED DESCRIPTION 
       [0020]    Turning to  FIG. 1 , illustrated is example embodiment of a document processing system  100  that includes a network  102  that is in data communication with one or more document processing devices such as that illustrated by document processing device  104 , suitably comprised of a multifunction peripheral (“MFP”) as illustrated. MFP  104  is suitably operable for printing, faxing, scanning, copying, e-mailing, or any other document processing operation will be understood by one of ordinary skill in the art. In the illustrated embodiment, MFP  104  includes a user interface  106 . Operation of the device is suitably managed by an embedded controller  108  and embedded data storage  110  as will be detailed further below. 
         [0021]    In the example embodiment of  FIG. 1 , MFP  104  is coupled for data communication  112  with network  104 , suitably comprised of a local area network (LAN), a remote local area network (RLAN), a wide area network (WAN) which may comprise the Internet, or any combination thereof. In the example embodiment of  FIG. 1 , a computer, terminal, workstation, tablet computer, smartphone, or the like, such as that illustrated by computer  114  is also suitably placed in data communication  116  with network  102 . Computer  114  suitably provides an interface for an operator or technician to access MFP  104  for control, administration or accounting relative to device operation. 
         [0022]    The architecture of the example embodiment of  FIG. 1  illustrates an overview of document processing management system wherein an administrator is suitably in communication with one or more MFPs for monitoring, accounting, configuring or controlling operations. With a network-based administration system, a technician can connect with multiple devices over long distances for efficient and cost-effective management. 
         [0023]    Turning now to  FIG. 2 , illustrated are functional components  200  suitably comprising a multifunctional peripheral such as MFP  104  of  FIG. 1 . Included is an example embodiment of controller  108  which is suitably comprised of a computer. Included in example controller  108  are one or more processors, such as illustrated by central processor unit (CPU)  202 . Also included are non-volatile memory, such as read-only memory (ROM)  204 , random access memory (RAM)  206 , a storage interface  208  and a network interface  210 . In the example embodiment, CPU  202 , ROM  204 , RAM  206 , storage interface  208  and network interface  210  are in mutual data communication via bus  212 . Storage interface  208  facilitates data access with a bulk data storage, such as one or more disks  216 , or any other suitable data storage such as a flash drive, CD, DVD or the like. Network interface  210  suitably provides for external data communication, such as with a network interface connection (NIC)  214  or WiFi interface  218 . NIC  214  or WiFi interface  218  suitably provide for connection to an associated network  220 . 
         [0024]    In the example embodiment of  FIG. 2 , a document processor interface  222  is also in data communication with bus  212 , and provides a gateway to copy hardware  224 , scan hardware  226 , print hardware  228  and fax hardware  230  which together comprise MFP functional hardware  232 . MFP functional hardware  232  suitably includes embedded monitors, such as resource monitors or counters to facilitate metering or maintenance intervals as will be detailed further below. 
         [0025]    Turning now to  FIG. 3 , illustrated is a functional block diagram  300  of an example MFP. Included is a print/copy/scan engine  302  which interfaces with print control  304 , fax control  306 , and scan control  308 , all of which are suitably interfaced with job queue  312 . Print/copy/scan engine  302  is suitably provided with user access via user interface  310 . Job queue  312  is suitably interfaced with raster image processor (RIP) and page description language (PDL) functionality  316 , as well as job parser  318 . Job queue  312  is also suitably interfaced with network services  314 , which in turn is interfaced with client network services  320 . Job parser  318  is suitably interfaced with client device services  322 . 
         [0026]    Turning now to  FIG. 4 , illustrated is an example embodiment of a networked document processing system  400  that includes one or more local area networks such as LAN  404  suitably in data communication with a wide-area network such as WAN  408  which may comprise connection via the Internet. In the illustrated embodiment, WAN  408  suitably comprises a service cloud that couples cloud database storage  412  and one or more administrators  416 . LAN  404  includes one or more document processing devices, such as MFPs  420  and  422 , as well as printer  428 , label printer  440 , or any other suitable networked document processing device as will be appreciated by one of ordinary skill in the art. The example embodiment of  FIG. 4  provides for networked management of document processing devices, illustrating devices that can be managed by one or more administrators covering multiple locations and disparate devices. 
         [0027]    Turning now to  FIG. 5 , illustrated is an example embodiment of a networked document processing system  500  employing distributed data collection functionality to assist in monitoring or reporting of devices. An administrator or technician  502  is enabled to access document processing devices via a LAN, WAN, RLAN or any combination thereof. In the illustrated example MFPs  510 ,  520  and  530  are in networked data communication. Each device suitably includes an embedded controller such as that detailed above. One, two, three or more MFPs are configured so as to be enabled to function as a monitor of other devices on the network. By way of further example, MFP  510  is designated as a collector of other MFP devices. Such designation is suitably assigned by an administrator and includes specification for devices to be monitored, such as via a range of IP addresses, which will be further detailed below. In another example embodiment, monitoring is specified for one or more operations of a document processing device. By way of further example, device may monitor only device operations that include consumables such as paper, toner or ink. 
         [0028]    In the example embodiment of  FIG. 5 , MFP  510  is configured as a primary collector to monitor MFP  520  and MFP  530 , although it will be appreciated that more or different devices are suitably monitored as detailed above. MFP  510  suitably retrieves device data on occasion, such as periodically or other set or selected intervals. As detailed above, device information suitably comprises count information, such as copy count or page count, consumable usage, service intervals, device maintenance information, service interruptions, malfunctions, or the like. Device information further facilitates enforcement of usage policies or job accounting. Accumulated device data is suitably made available locally or via network connection, such as to administrator or technician  502 . 
         [0029]    MFP  520  is suitably configured as a secondary collector analogously to MFP  510  for network device monitoring, but is not initially enabled for such purpose. MFP  520  occasionally probes MFP  510  to determine if it is functioning as needed for network device monitoring. This is suitably accomplished at prescribed or periodic intervals. This is suitably accomplished by a SNMP query, a device ping, or any other suitable probe as will be appreciated by one of ordinary skill in the art. When MPF  520  determines that MFP  510  is not performing as required, MFP  520  suitably enables its system monitoring capabilities so as to eliminate or minimize monitoring interruption. When a probe from MFP  520  results in a determination that MFP  510  is once again functional for monitoring of network devices, it suitably cedes its monitoring operation back to MFP  510 . 
         [0030]    In the example embodiment of  FIG. 5 , MFP  530  is suitably enabled to initiate a probe to MFP  520 . If MFP  520  is not operational, MFP  530  as a tertiary collector suitably undertakes network device monitoring as described above. 
         [0031]    In the example embodiment of  FIG. 5 , one or more MFPs are suitably enabled for concurrent monitoring of network devices. Such concurrency, while duplicative of monitoring, facilitates fault tolerance in the event that one or more monitoring devices become disabled. One or more devices are suitably used to generate reports, such as to a technician or system administrator. In yet a further example embodiment, devices are suitably assigned a complementary or overlapping set of devices for monitoring. Monitoring information so acquired is suitably aggregated. Redundant monitoring information is suitably used for cross-checking or error reporting. 
         [0032]    In view of the forgoing example embodiment, it will be appreciated that, when MFP  510  is operational, device monitoring is accomplished via that device. While MFP  510  is operational, probes from MFP  520  determine that there is no need to take over monitoring. Similarly, probes from MFP  530  will cause it to determine that there is no need to take over monitoring. It will be appreciated that any number of devices are suitably implemented for backup monitoring and such devices are suitably connected in a LAN, RLAN, WLAN or Internet connection. 
         [0033]    Turning now to  FIG. 6 , illustrated is an example embodiment of operation of a monitoring operation  600 . Operation commences at  610 . At  620 , device data for data collection is input. Next, at  630 , a determination is made as to optimal primary and secondary data collectors. Tertiary and other data collectors can similarly be determined as would be understood in the art. Collection instructions are relayed to the devices at  640  and the operation ends at  650 . 
         [0034]      FIG. 7  illustrates an example embodiment of backup collection operation  700 . Operation commences at  710 . At  720 , one or more devices, such as MFPs, receive collection instructions, suitably from an administrative terminal as detailed above. Next, at  730 , a determination is made whether the primary collector is active. If it is, the process suitably ends at  750 , and the determination is repeated again at selected or set intervals. If the primary collector is not active, the device will become the collector and collect data in place of the primary collector at  740 . The backup collection process can be repeated for tertiary and other data collectors. 
         [0035]      FIG. 8  illustrates an example embodiment of a user interface  800  that facilitates association of a list of IP addresses, ranges or subnets, or any other suitable network demarcation, to define collectors. The primary collector is suitably denoted, as are any backup collectors. 
         [0036]      FIG. 9  illustrates an example embodiment of an IP address list as entered by a service cloud user. In this example, the set of IP addresses defines the devices to be polled and collected in accordance with a selected or predetermined schedule. The list is suitably created by a service cloud user and stored in the cloud, such as via cloud database storage  412  of  FIG. 4 . At a scheduled time, a collector device will discover a network to find the devices in the list. Data is suitably collected and the list updated in the cloud. Thus, devices that were discovered will be monitored and data updated. 
         [0037]    Turning now to  FIG. 10 , illustrated is an example embodiment of collector settings  1000  suitably providing a hierarchical ordering of document processing device having monitoring function, or concurrent, redundant or overlapping monitoring capability. This information is suitably communicated to one or more document processing devices having network device monitoring capability, such as device listing  1010 . In the illustrated example, a leading or initial IP address 10.1.22.21 designates a primary monitoring device. Each receiving device suitably compares its own IP address with the listed information in the device listing  1010 . In a case when the receiving device determines that it is the primary collector, 10.1.22.21, it need only commence monitoring of device information for specified devices. A second device having IP address 10.1.86.5 suitably probes device 10.1.22.21 and commences collection when that probe reveals a fault. Similarly, other devices down the line, 10.1.86.7 and so on, suitably probe one or more, or all of the devices ahead of it in the hierarchy to determine whether it should commence monitoring operations. As noted above, device listing  1010  also suitably defines devices for concurrent monitoring of all or some of the networked devices or subsets of their functionality. 
         [0038]    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.