This application relates generally to configuring multifunction peripherals. The application relates more particularly to updating multifunction peripheral configuration via configuration codes received from a portable data device.
Document processing devices include printers, copiers, scanners and e-mail gateways. More recently, devices employing two or more of these functions are found in office environments. These devices are referred to as multifunction peripherals (MFPs) or multifunction devices (MFDs). As used herein, MFPs are understood to comprise printers, alone or in combination with other of the afore-noted functions. It is further understood that any suitable document processing device can be used.
Given the expense in obtaining and maintain MFPs, devices are frequently shared or monitored by users, servers or technicians via a data network. MFPs, while moveable, are generally maintained in a fixed location. While remote device monitoring is common, there is still a need to occasionally dispatch a service technician for on-site MFP maintenance. Maintenance may include repair, parts replacement or upgrading, or device configuration. MFPs are intelligent devices that may be configured by software, firmware or hardware settings. Such configuration may be accomplished by device codes which can control functions such as security settings, feature accessibility, activity logging, document handling, or network connectivity. Device codes can typically be entered directly on an MFP user interface once the device is placed in administrative mode. In one example, a service technician places a MFP in administrative mode via its touchscreen interface. They then can enter device codes, which can be a complex sequence of characters. Inputting of individual device codes can be very time consuming, particularly when a large number of codes are required for entry. There may also be many MFP devices on a premises that require code updates, making the process even more burdensome. When so many characters are input, there is a chance, if not a likelihood, that errors will be made. An erroneous code input can, at best, cause a misconfigured device or, at worse, damage or cripple and MFP or one or more of its functions.
Various embodiments will become better understood with regard to the following description, appended claims and accompanying drawings wherein:
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.
In accordance with an example embodiment of the subject application, a system and method for updating of device codes in a multifunction peripheral includes a processor and associated memory and a touchscreen user interface. An input receives a device code set corresponding to a desired multifunction peripheral configuration and the codes are stored in the memory. The processor generates input indicia on the touchscreen. The processor enables the input indicia for user selection input when a wireless data interface is in active communication with the multifunction peripheral. The processor determines that the input indicia has been selected and sends the device code set to the multifunction peripheral via the wireless data interface.
In accordance with the subject application,
MFP 104 includes a NFC system 124 and a Wi-Fi communication system 128. A device controller, such as that illustrated in
Turning now to
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.
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), Lightning, telephone line, or the like. Processor 202 is also in data communication with one or more sensors which provide data relative to a state of the device or associated surroundings, such as device temperature, ambient temperature, humidity, device movement and the like.
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. Hardware monitors suitably provides 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 of
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.
Intelligent controller 201 is suitably provided with an embedded web server system for device configuration and administration. A suitable web interface is comprised of TOPACCESS Controller (sometimes referred to in the subject illustrations as “TA”), available from Toshiba TEC Corporation.
Turning now to
Processor 310 is also in data communication with a storage interface 325 for reading or writing to a data storage system 316, suitably comprised of a hard disk, optical disk, solid-state disk, or any other suitable data storage as will be appreciated by one of ordinary skill in the art.
Processor 310 is also in data communication with a network interface controller (NIC) 330, which provides a data path to any suitable wired or physical network connection via physical network interface, or to any suitable wireless data connection via wireless interface 332, such as one or more of the networks detailed above. The system suitably uses location based services.
Processor 304 is also in data communication with a user input/output (I/O) interface 350 which provides data communication with user peripherals, such as display 360, as well as keyboards 352, mice, track balls, or other pointing devices 354, touch screen 370, or the like. It will be understood that functional units are suitably comprised of intelligent units, including any suitable hardware or software platform.
Next, at block 412, devices for which new codes are needed are identified, and at block 416 the required device codes are stored on the portable data device for each MFP to be updated, which may comprised different code sets for different devices or device scenarios. Device code sets are suitably labeled at block 420 for future recall for use. Next, a “tap to update” icon is suitably generated on the portable data device touchscreen at block 424 which enables a service technician to update the device code set on an MFP via a selectable one click prompt on the portable data device touchscreen. The service technician approaches a target MFP at block 428 and a host emulation service is commenced at block 432. A tag indicating transmission of device code settings is set at block 436 and the portable data device receives connection information for code transfer at block 440 and a data connection is established at block 444. While any suitable data transfer mechanism may be used, a desirable alternative is to establish a Wi-Fi direct connection between the MFP and portable data device, thus eliminating any need for routing via a network cloud. Device codes are communicated to the MFP at block 448, and a monitoring web service accepts them at block 452. Next, the monitoring web service processes the device code update at block 456 and the process ends at block 460.
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.
Number | Name | Date | Kind |
---|---|---|---|
20060098221 | Ferlitsch | May 2006 | A1 |
20090059273 | Tomita | Mar 2009 | A1 |
20100069008 | Oshima | Mar 2010 | A1 |
20140240778 | Itogawa | Aug 2014 | A1 |
20140355048 | Kang | Dec 2014 | A1 |
20150070725 | Monden | Mar 2015 | A1 |
20150138597 | Koshigaya | May 2015 | A1 |
20150212769 | Norota et al. | Jul 2015 | A1 |
20150358761 | Ito | Dec 2015 | A1 |
20170290078 | Suzuki | Oct 2017 | A1 |