US20080243862A1 - Firmware repository for mfp devices - Google Patents
Firmware repository for mfp devices Download PDFInfo
- Publication number
- US20080243862A1 US20080243862A1 US11/695,206 US69520607A US2008243862A1 US 20080243862 A1 US20080243862 A1 US 20080243862A1 US 69520607 A US69520607 A US 69520607A US 2008243862 A1 US2008243862 A1 US 2008243862A1
- Authority
- US
- United States
- Prior art keywords
- firmware
- repository
- location
- file
- computer readable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 16
- 239000011159 matrix material Substances 0.000 claims description 21
- 238000010926 purge Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 claims description 8
- 230000004048 modification Effects 0.000 claims description 4
- 238000012986 modification Methods 0.000 claims description 4
- 238000012217 deletion Methods 0.000 claims description 2
- 230000037430 deletion Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Abstract
Description
- Many electronic devices today include firmware. Firmware may be a software program or set of instructions programmed on a hardware device. The firmware may provide instructions which are executed to determine how the device operates. The firmware may be stored in memory of a hardware device. As updated firmware is developed, the firmware stored in a device may be replaced or updated.
- Existing solutions to manage the firmware (FW) of electronic devices such, for example, multifunction printing (MFP) devices, have many limitations. MFP devices may perform imaging (scanning), printing, copying and facsimile machine functions, or some subset of these functions. FW updates may typically be distributed either on a CD or through a web site. Both the mechanisms have drawbacks. FW distribution through CD is a slow process. It takes time to create and ship the CDs for new firmware updates to individual customers. On the other hand, FW distribution through a web site may be difficult for users to navigate.
- Features and advantages of the disclosure will readily be appreciated by persons skilled in the art from the following detailed description when read in conjunction with the drawing wherein:
-
FIG. 1 diagrammatically depicts an exemplary operating environment in which a firmware repository may be utilized. -
FIG. 1A illustrates schematically an exemplary embodiment of a firmware repository, which may be used in the operating environment depicted inFIG. 1 .FIG. 1B illustrates schematically an exemplary embodiment of firmware files stored on a computer readable media. -
FIG. 2 is a flow diagram illustrating an exemplary embodiment of an algorithm for creating a firmware repository. -
FIG. 3 is a flow diagram illustrating an exemplary embodiment of an algorithm for adding new firmware in a firmware repository. -
FIG. 4 is a flow diagram illustrating an exemplary embodiment of an algorithm for modifying the properties of a firmware in a firmware repository. -
FIG. 5 is a flow diagram illustrating an exemplary embodiment of an algorithm for deleting a firmware from a firmware repository. -
FIG. 6 is a flow diagram illustrating an exemplary embodiment of an algorithm for removing a firmware repository. -
FIG. 7 is a flow diagram illustrating an exemplary embodiment of an algorithm for creating a mirror image of a firmware repository. -
FIG. 8 is a flow diagram illustrating an exemplary embodiment of an algorithm for purging firmware from a firmware repository. - In the following detailed description and in the several figures of the drawing, like elements are identified with like reference numerals. The figures are not to scale, and relative feature sizes may be exaggerated for illustrative purposes.
- A firmware repository may provide a mechanism to distribute firmware releases and make them available to machine dealers and customers in a secure, orderly and error-free manner. A firmware repository may be located on a local resource such as a CD-ROM, network drive or a remote resource accessed through the Internet.
FIG. 1 diagrammatically depicts anexemplary operating environment 10 in which a firmware repository may be utilized. - In one exemplary embodiment, the new or updated firmware may be made available through a
firmware repository 20 hosted on aweb server 22. Users with proper privileges may access, e.g. to manage or browse, this web repository through an HTTP or HTTPS connection via aweb browser 32, which may be running, by way of example, on aterminal 30, or via the Internet 12, which may be connected through afirewall 28 toweb server 22. Authorized persons may publish new firmware and remove or update existing firmware. The firmware may be obtained from aCD 24 using a CD drive, or from anetwork storage drive 26, or from another firmware repository. - Customers/users and dealers with required access privileges may access this
web repository 20 through a web browser to obtain firmware for a machine. In some applications, access privileges may not be required, so that the firmware update access is freely available to customers/users. - Customer and dealers who are running a management gateway or printer administration utility (PAU)
software application 42, running on a console, terminal orserver 40 located on a customer's intranet, for example, may have alocal firmware repository 50. Theterminal 40 is connected on the intranet behind afirewall 48 through which a connection to the Internet 12 is made. A management gateway application and techniques for remote firmware management are described in pending application Ser. No. 11/670,875, entitled “Remote Firmware Management for Electronic Devices,” filed Feb. 2, 2007, the entire contents of which are incorporated herein by this reference. A PAU from Sharp Electronics, for example, is a networked printer management tool using standard Simple Network Management Protocol (SNMP) to monitor status and enable remote configuration of networked digital printer and copier devices. This exemplary PAU may be utilized by network administrators for monitoring all Sharp network connected printers and copiers. The utility keeps a constant status check on the devices, warning when some action is necessary by the administrator, for example if paper supply is low, or toner supply is low, or if a periodical service is due, and alerting when a problem has occurred, for example paper jam or toner exhausted. By utilizing the PAU, network administrators can manage all digital printers and copiers remotely via the network from a single console. PAU users can access thislocal repository 50 to add new firmware and update existing firmware. In the example illustrated inFIG. 1 , users of a PAU can obtain new firmware from alocal CD 52, anetwork drive 54 and from theweb firmware repository 20, in order to update or install firmware ondevices devices local repository 50 from aweb firmware repository 20 by using a web browser, e.g. aweb browser 44 running on alocal terminal 46. In an exemplary embodiment, theterminal 46 may be connected to theconsole 40 through an HTTPS or HTTP connection. - The
firmware repository 50 local to the PAU and theweb firmware repository 20 are independent of each other, though they use the same technology to store, locate and retrieve the firmware. - A manufacturer may release the new firmware also on CDs. A
CD 52 may have the firmware in alocal repository 50. In an exemplary embodiment, the PAU will be able to understand the structure of the CD repository. There may also be situations in which a CD may contain the firmware without any also being on a local firmware repository. - Authorized personnel, e.g. those of a device manufacturer, can create the CD with a local repository, e.g. by using a software utility, as described below.
- In an exemplary embodiment of a firmware repository, many or all the processes related to the firmware repository may be automated. Automation of the processes in this case may reduce human errors. Most of the processes related to the firmware repository may involve interaction with a computer or computer networks. In an exemplary embodiment, one or more of the following exemplary processes may be carried out programmatically rather than manually. For example, a user may accomplish these functions using a software program or utility, in which the user initiates a given function, and the software carries out the function using inputs provided by the user through a user interface.
- 1. creation of the repository;
- 2. creation of a mirror image of the repository;
- 3. updating the repository with new firmware;
- 4. removal of firmware from the repository;
- 5. modification of the existing properties of the firmware in the repository, for example to change the release notes;
- 6. deletion of the repository; and
- 7. purging firmware from the repository.
- In an exemplary embodiment, activities related to a firmware repository may be automated by a software utility developed using an API (Application Programming Interface). For example, an automation API may be called by to access the firmware repository and make changes to the repository. Those who intend to use the firmware repository in a manual way may do so by using the web browser or client application provided by a device manufacturer or dealer. The firmware repository may be accessed programmatically, e.g. using an API called by a utility program to access and update the firmware repository. This will provide for automation so that the firmware repository may be managed programmatically, e.g., using software utility programs which call an API.
- The software utility and API called by the software utility may reside on a console or terminal such as
laptop 30, running utility/API 34, and/or onconsole 46, runningutility program 45. - In an exemplary embodiment of a firmware repository, repository automation is XML (Extensible Markup Language) based; the firmware repository may be based on an XML schema which contains the following information:
- the firmware version;
- the model and family of devices, e.g. multifunction printers (MFPs), supported by the firmware;
- the release date of the firmware;
- a description or release notes for this version, or a location of the description or location (in an exemplary embodiment, the location will be a URI (Universal Resource Identifier) which will point to a local storage, network storage or web storage);
- a location of the firmware (in an exemplary embodiment, the location will be a URI (Universal Resource Identifier) which will point to a local storage, network storage or web storage); and
- a version matrix.
-
FIG. 1A illustrates schematically an exemplary embodiment of afirmware repository 80, which may be used in the operating environment depicted inFIG. 1 . Thefirmware repository 80 may serve as any ofrepositories FIG. 1 . Therepository 80 is a computer readable media, e.g., a hard drive or server storage, a CD, or any other type of media which may be read by a computer system. Therepository 80 includes anXML description file 82, which includes the information set out above for the XML schema. Each user device or terminal, e.g.PAU 40,laptop 30 orlaptop 44, will know the location of the firmware repository, and may navigate to the location, e.g. its URI. The firmware repository may include one or more firmware files, depicted asfiles FIG. 1A . These firmware files contain the actual firmware for a particular device, e.g. device 1,device 2, . . . device N. The file format will be that format defined by the device manufacturer. - In an exemplary embodiment, the
XML description file 82 includes an information field specifying, for each device model, the location of the corresponding firmware file. This location may be on the same computer readable media as the XML description file, or may be a different location. Thefirmware repository 80 thus could be constructed without anyfirmware files medium 90 depicted inFIG. 1B . As an example,repository 80 may be installed onserver 26 inFIG. 1 , and the firmware files may be located onCD 24, or another remote web server. - An XML parser utility program such as parser 43 (
FIG. 1 ) may be running on a console used to access the firmware repository, read the XML description file, and manage or download firmware files for a given device such as device 60 (FIG. 1 ). The parser utility program is illustrated inFIG. 1 as installed onserver 40, but may also be installed onconsoles -
FIG. 2 is a flow diagram illustrating an exemplary embodiment of analgorithm 100 for creating a firmware repository. Theexemplary algorithm 100 depicted inFIG. 2 in an exemplary embodiment represents steps implemented by an API called from a software utility. At 102, the user enters an input using a user input screen generated from a software utility on a terminal, e.g. fromprogram 34 on laptop 30 (FIG. 1 ), which specifies the intended location of the firmware repository. This location may be its Uniform Resource Identifier (URI), i.e. the network or directory path or URL of the intended firmware repository location. Optionally the user credential (user name, password, digital certificates etc.) may also be entered in order to access the URI. Checks are performed at 104 and 106 to determine if the location is valid, and to determine if the user has create/write permission to set up the repository. If not, an error code is set, and operation branches to 112 to return the status. At 108, the location for the repository is created. In an exemplary embodiment, the location may be created using an operating system call, to create a virtual directory on a web server, for example. This is analogous to creation of directories and subdirectories on a PC. At 110, any setup and configuration files are created. The status is then returned at 112. In an exemplary embodiment in which the user called an API to set up the location, the returned status may be a return value of the API call. -
FIG. 3 is a flow diagram illustrating an exemplary embodiment of analgorithm 120 for adding new firmware in a firmware repository, e.g. one which has been established using the algorithm ofFIG. 2 . At 122, data is input specifying a device model (“Model”), firmware release date (“FirmwareReleaseDate”), the source location of the firmware (e.g., “MFPFirmwareLocation”), the firmware file name (“FirmwareFileName”), any release note file name (“ReleaseNotesName”), the firmware components (“FirmwareComponents”), and the firmware version matrix (“VersionMatrix”), as well as the credentials of the user seeking to add new firmware to the repository. At 124, the algorithm checks to determine if the MFPFirmwareLocation is valid. This is the location from where input firmware can be obtained. If not, the algorithm sets an error code, and branches to step 134. At 126, the algorithm checks to determine that the user has write permission to write information into the repository; if not, the algorithm sets an error code, and branches to step 134. At 128, the new path or location where new firmware will be added in the repository is created, e.g. containing “Model\FirmwareReleaseDate.”. At 130, the firmware file (FirmwareFileName) is saved in the location “Model\FirmwareReleaseDate.” At 132, the XML data related to the new firmware file is updated in the firmware repository XML description file. In an exemplary embodiment, the information to be updated in the XML description file is collected from the information provided as inputs to the API call, and this information is updated in the XML description file for that particular firmware. At 134, the status is returned. -
FIG. 4 is a flow diagram illustrating an exemplary embodiment of analgorithm 140 for modifying the properties of a firmware in a firmware repository. At 142, data is input specifying the device model, the firmware release date (“FirmwareReleaseDate”), the firmware property to modify (“PropertyToModify”), and the new firmware property value (“NewValue”). At 144, the algorithm checks to determine if the path containing “Model\FirmwareReleaseDate” exists in the firmware repository; if not, the algorithm sets an error code, and branches to step 154. At 146, the firmware checks to determine if the requester/user has write permission; if not, the algorithm sets an error code, and branches to step 154. At 150, if the firmware-related file needs to be replaced, it is replaced with the new firmware file. One example is to replace an existingfirmware file 84A (FIG. 1 A) with a new file. Another example is to modify the release notes for a particular firmware, by replacing the release note or release note file with a new release note or file. At 152, the XML data identified by PropertyToModify is updated for the specified firmware file in the firmware repository XML description file. At 154, the status is returned. -
FIG. 5 is a flow diagram illustrating an exemplary embodiment of analgorithm 160 for deleting a firmware from a firmware repository. At 162, data is input specifying the device model and firmware release date to be deleted, e.g. “Model” and “FirmwareReleaseDate.” At 164, the algorithm checks to determine if the path containing “Model\FirmwareReleaseDate” exists in the repository; if not, the algorithm sets an error code, and branches to step 172. At 166, the algorithm checks to determine if the user has write permission; if not the algorithm sets an error code, and branches to step 172. At 168, the firmware at location “Model\FirmwareReleaseDate” is deleted. At 170, the XML data related to the firmware file in the firmware repository XML file is removed. At 172, the status is returned. -
FIG. 6 is a flow diagram illustrating an exemplary embodiment of analgorithm 180 for removing a firmware repository. At 182, data specifying the location of the repository to be deleted, i.e. its URI (Network, Directory Path or URL of the intended firmware repository location) is input, with the user credentials. If the firmware location is valid and the user has create/write permission (184, 186), then at 188, the firmware directory as well as any subdirectories and their contents are removed. The status is returned at 190. -
FIG. 7 is a flow diagram illustrating an exemplary embodiment of analgorithm 200 for creating a mirror image of a firmware repository. At 202, data is input specifying the source URI (Network, Directory Path or URL of the intended firmware repository location), and the Destination URI. User Credential for both source and destination (Username, password, digital certificates etc in order to access the URI) may also be input. At 204, 206 208, the algorithm checks if the source and destination locations are valid, if the user has create/write permission for the destination location, and if the user has read permission for the source location. If not, an error code is set, and the algorithm branches to 218. If so, at 21 0, the destination location for the new repository is created. At 212, the contents of the source location are copied and saved in the destination location. At 214, all the subdirectories, present in the source location, are created at the destination location. At 216, the contents of the source location subdirectories are copied and saved in the corresponding destination location subdirectories. The status is returned at 218. -
FIG. 8 is a flow diagram illustrating an exemplary embodiment of analgorithm 220 for purging firmware from a firmware repository, identified as PurgeFirmware(PurgeDate). At 222, the purge date (“PurgeDate”) is input, with the firmware location and the user credentials. At 224, the algorithm checks if the user has write permission; the algorithm exits is not. At 226, the firmware for which “FirmwareReleaseDate” is older than “PurgeDate” is identified. At 228, all the identified firmware is deleted from the repository. At 230, the XML data related to the identified firmware is deleted in the firmware repository XML file. At 232, the status is returned. - An exemplary embodiment of a firmware repository is stored using an XML schema. An exemplary firmware repository may be accessed using one of the following methods, in an exemplary embodiment:
- 1. Firmware Repository Web Service: A firmware repository located on web may be implemented using web services. A repository web service can be accessed via a specialized web service API for programmatic access or through a web browser for manual access.
- 2. Traditional directory structure browsing: User can access an URL and browse the directory structure to locate the firmware of interest and download it.
- 3. Software Application: If firmware is distributed through CD, then a software application may be used to create and view the repository on CD.
- If the firmware repository is located on the network or on a local server then it can be accessed through any of the above mentioned methods.
- In order to ensure that only authorized entities access the repository, in an exemplary embodiment, the firmware repository provides one or more of the following security options:
- 1. Username/password based authentication.
- 2. Digital certificate based authentication.
- 3. License key based authentication.
- In an exemplary embodiment, a firmware repository may support two types of users. General users or end users may have access to only browse the repository and download the firmware including a version matrix. Advanced or administrative users may have access to all the features including creation, modification and update of the repository and user profile management.
- An exemplary embodiment of a firmware repository may include techniques for notifying the registered users when new firmware updates become available. Users can be notified using email or other messaging methods like instant messaging, SMS (Simple Messaging Service), MMS (Multi-media Messaging Service) and paging.
- As described above, an XML description file in the firmware repository may include a version matrix for each model or model of devices. An exemplary embodiment of a version matrix is a matrix of version numbers of all the firmware for different components of the whole system. It also contains the interdependencies among the various components. A representation of an exemplary version matrix is depicted in the following table.
-
Components Version MFP Firmware 7.0 Print Engine Firmware 7.0 Copier Firmware 7.0 Scanner Firmware 6.0 Fax Firmware 5.0 Job Accounting 4.0 Firmware Constituent Firmware Components Print Job Engine 7.0 Copier 7.0 Scanner 6.0 Fax 5.0 Accounting 4.0 Compatible Versions Print Engine 5.0 or greater 6.5 or greater Of Components Copier 5.0 or greater 6.5 or greater Scanner 5.5 or less 6.0 Fax 5.0 Job Accounting - The first part of the table provides the version numbers of the firmware for different components. For example, the version of the released MFP firmware package is 7.0. In this example, the MFP firmware is made up five components—Print Engine firmware, Copier firmware, Scanner firmware, Fax firmware and Job Accounting Firmware. Components of the MFP may have different versions. In this case, even though the MFP firmware version is 7.0; the Fax firmware version is 5.0.
- The bottom half of the table in this example of a version matrix provides the compatibility matrix of the version of components. The columns represent the versions of new firmware components. The rows show the versions of old firmware that are compatible with the new firmware versions shown in the columns. For example, Job Accounting version 4.0 in the new firmware is compatible with copier firmware version 6.5 or greater in the old releases.
- This dependency relationship is represented as the XML schema, and forms the version matrix. The version matrix is used in making decisions whether to update a particular component on not. For example, if a MFP has Job Accounting firmware with version 3.2 and printer firmware with version 6.7 and someone decides to update the firmware of Job Accounting to 4.0 then he also has to update the print engine firmware to 7.0 otherwise, Job Accounting firmware will not work properly.
- The following is an exemplary sample XML schema for a firmware repository, for example an XML schema for an
XML description file 82 as described above regardingFIG. 1A . -
<?xml version=“1.0” encoding=“utf-8”?> <xs:schema attributeFormDefault=“unqualified” elementForm Default=“qualified” version=“1.0” xmlns:xs=“http://www.w3.org/2001/XMLSchema”> <xs:element name=“AllFirmware”> <xs:complexType> <xs:sequence> <xs:element maxOccurs=“unbounded” name=“Model”> <xs:complexType> <xs:sequence> <xs:element maxOccurs=“unbounded” name=“Firmware”> <xs:complexType> <xs:sequence> <xs:element name=“FirmwareReleaseDate” type=“xs:date” /> <xs:element name=“MFPFirmwareLocation” type=“xs:anyURI” /> <xs:element name=“FirmwareFileName” type=“xs:string” /> <xs:element name=“ReleaseNoteName” type=“xs:string” /> <xs:element name=“FirmwareComponents”> <xs:complexType> <xs:sequence> <xs:element maxOccurs=“unbounded” name=“Component” type=“xs:string” /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=“VersionMatrix”> <xs:complexType> <xs:sequence> <xs:element maxOccurs=“unbounded” name=“MFPComponent”> <xs:complexType> <xs:sequence> <xs:element name=“Name” type=“xs:string” /> <xs:element name=“Version” type=“xs:string” /> <xs:element name=“ReleaseDate” type=“xs:date” /> <xs:element name=“FirmwareFile” type=“xs:string” /> <xs:element name=“ReleaseNote” type=“xs:string” /> <xs:element name=“FirmwareLocation” type=“xs:anyURI” /> <xs:element name=“CompatibleWith”> <xs:complexType> <xs:sequence> <xs:element maxOccurs=“unbounded” name=“SubComponent”> <xs:complexType> <xs:sequence> <xs:element name=“ComponentName” type=“xs:string” /> <xs:element name=“CompatibleVersion” type=“xs:string” /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name=“FirmwareVersion” type=“xs:string” use=“required” /> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name=“ModelName” type=“xs:string” use=“required” /> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> - The following is an exemplary sample XML description file for a firmware repository. This example relates to two particular device models, identified as MX-3501N and AR-M700U.
- As illustrated in the foregoing example, the XML description file may include information for each subcomponent of the system may include an identification of the firmware for that component, as well as information such as the location of the subcomponent firmware file.
- An exemplary embodiment of a repository for firmware updates may provide one or more of the following capabilities:
- Well defined location and storage structure to archive the firmware updates for electronic devices, e.g., MFP devices.
- Automation of repository creation and the process for populating the repository with firmware updates.
- For the devices with multiple sub-components where each component requires a separate firmware, there may be a need to update more than one firmware at the same time. Firmware for different components may have interdependencies. They may have dependency on the order in which the firmware for components is upgraded. Additionally they might have dependency across versions. A particular version of one component may only work with a particular version of firmware for another component. An exemplary embodiment of a firmware repository provides a structure which captures a matrix of firmware versions for different components and their interdependencies.
- Algorithms to manage the repository, e.g. removing elements, purging the repository periodically and deleting the repository if needed.
- Exemplary embodiments of a firmware repository and management system may include one or more of the following features:
- 1. XML schema for the structure of the firmware repository.
- 2. Algorithm to automate the process of creating and populating the firmware repository.
- 3. Algorithm to create mirror images of a repository.
- 4. Algorithm to modify/delete the repository—to remove the elements and to purge the repository periodically.
- 5. Secure and restricted access to repository.
- 6. Version matrix to capture the inter-dependencies of firmware for different components across different versions.
- Although the foregoing has been a description and illustration of specific embodiments of the invention, various modifications and changes thereto can be made by persons skilled in the art without departing from the scope and spirit of the invention as defined by the following claims.
Claims (30)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/695,206 US8019794B2 (en) | 2007-04-02 | 2007-04-02 | Firmware repository for MFP devices |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/695,206 US8019794B2 (en) | 2007-04-02 | 2007-04-02 | Firmware repository for MFP devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080243862A1 true US20080243862A1 (en) | 2008-10-02 |
US8019794B2 US8019794B2 (en) | 2011-09-13 |
Family
ID=39796100
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/695,206 Expired - Fee Related US8019794B2 (en) | 2007-04-02 | 2007-04-02 | Firmware repository for MFP devices |
Country Status (1)
Country | Link |
---|---|
US (1) | US8019794B2 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090210567A1 (en) * | 2008-02-20 | 2009-08-20 | Seiko Epson Corporation | Host apparatus and method for controlling the same |
US20110004874A1 (en) * | 2009-07-06 | 2011-01-06 | Canon Kabushiki Kaisha | Information processing apparatus, method of controlling thereof, and computer-readable storage medium storing program therefor |
JP2011022712A (en) * | 2009-07-14 | 2011-02-03 | Canon Inc | Distribution system, distribution apparatus, and distribution method |
US20110154313A1 (en) * | 2009-12-21 | 2011-06-23 | International Business Machines Corporation | Updating A Firmware Package |
KR20130104283A (en) * | 2012-03-13 | 2013-09-25 | 삼성테크윈 주식회사 | Method of updating firmware |
US20140223424A1 (en) * | 2013-02-05 | 2014-08-07 | Samsung Electronics Co., Ltd | Image forming apparatus, tracking apparatus, managing apparatus and method of updating firmware of image forming apparatus |
US20140355049A1 (en) * | 2013-05-30 | 2014-12-04 | Canon Kabushiki Kaisha | Printing system, printing service apparatus, image forming apparatus, control method, and storage medium |
US20150074815A1 (en) * | 2012-03-30 | 2015-03-12 | Hewlett-Packard Development Company, L.P. | License management of firmware-controllable features in computer systems |
US20150169310A1 (en) * | 2013-12-12 | 2015-06-18 | Lenovo (Singapore) Pte, Ltd. | Maintaining firmware |
US20150178066A1 (en) * | 2013-12-20 | 2015-06-25 | Netapp, Inc. | System, Method, and Computer Program Product For Managing Software Updates |
US20160203302A1 (en) * | 2014-09-19 | 2016-07-14 | Hewlett Packard Enterprise Development Lp | License management of firmware-controllable features in computer systems |
US9652493B1 (en) * | 2014-03-31 | 2017-05-16 | Dell Products Lp | Digitized release notes |
US20190250897A1 (en) * | 2018-02-13 | 2019-08-15 | Dell Products, Lp | Information Handling System to Treat Demoted Firmware with Replacement Firmware |
EP3588276A1 (en) * | 2018-06-27 | 2020-01-01 | Hewlett-Packard Enterprise Development LP | Selective download of a portion of a firmware bundle |
WO2021006929A1 (en) * | 2019-07-11 | 2021-01-14 | Microchip Technology Incorporated | System for improved evaluation of semiconductor hardware and corresponding method |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8271967B2 (en) * | 2008-06-09 | 2012-09-18 | Ricoh Company, Ltd. | MFP software update using web service |
US9135445B2 (en) * | 2012-03-19 | 2015-09-15 | Google Inc. | Providing information about a web application or extension offered by website based on information about the application or extension gathered from a trusted site |
BR112015016642A2 (en) * | 2013-01-11 | 2017-07-11 | La Presse Ltee | system and method for generating a digital edition |
US9535676B1 (en) | 2014-04-04 | 2017-01-03 | Seagate Technology Llc | Remote feature activation |
US9838250B1 (en) | 2014-04-04 | 2017-12-05 | Seagate Technology Llc | Recipient-specific feature activation |
US9633330B1 (en) | 2014-04-04 | 2017-04-25 | Seagate Technoglogy LLC | Late stage SKU assignment |
US9584498B1 (en) | 2014-04-04 | 2017-02-28 | Seagate Technology Llc | Feature activation using near field communication |
US10447552B2 (en) * | 2017-02-23 | 2019-10-15 | Kabushiki Kaisha Toshiba | System and method for predictive maintenance |
Citations (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5574899A (en) * | 1993-09-16 | 1996-11-12 | Fujitsu Limited | Generation number managing apparatus for adjusting generation numbers among processors or program files |
US6055632A (en) * | 1997-09-25 | 2000-04-25 | Allen-Bradley Company, Llc | Method and apparatus for transferring firmware to a non-volatile memory of a programmable controller system |
US6341143B1 (en) * | 1993-07-02 | 2002-01-22 | Multi-Tech Systems, Inc. | Modem with firmware upgrade feature |
US6360362B1 (en) * | 1998-02-20 | 2002-03-19 | Intel Corporation | Automatic update of camera firmware |
US20020052718A1 (en) * | 2000-08-04 | 2002-05-02 | Little Mike E. | Automated problem identification system |
US20020138567A1 (en) * | 2001-03-21 | 2002-09-26 | Nec Corporation | Update system, update client apparatus, update server apparatus, and programs |
US20020188934A1 (en) * | 2001-06-12 | 2002-12-12 | Nortel Networks Limited | Method and system for upgrading existing firmware on third party hardware |
US20030041127A1 (en) * | 2001-08-27 | 2003-02-27 | Turnbull Paul F. | System and methods for the automatic discovery, notification and installation of firmware upgrades |
US20030086107A1 (en) * | 2001-11-02 | 2003-05-08 | Johnson Steven Mark | Remote firmware upgrade via I/O connection |
US20030217193A1 (en) * | 2002-05-17 | 2003-11-20 | Sun Microsystems, Inc. | Method, system and article of manufacture for a firmware image |
US6671802B1 (en) * | 2000-04-13 | 2003-12-30 | Hewlett-Packard Development Company, L.P. | Performance optimization of computer system by dynamically and immediately updating a configuration setting based on detected change in preferred use |
US20040093597A1 (en) * | 2002-11-05 | 2004-05-13 | Rao Bindu Rama | Firmware update system for facilitating firmware update in mobile handset related applications |
US20040210894A1 (en) * | 2003-04-17 | 2004-10-21 | Zarco Maria F. | Image-formation device firmware having modular upgrade capability |
US20050038808A1 (en) * | 2003-08-15 | 2005-02-17 | Kutch Patrick G. | System and method for utilizing a modular operating system (OS) resident agent allowing an out-of-band server management |
US20050102660A1 (en) * | 2002-04-12 | 2005-05-12 | Shao-Chun Chen | Initialization and update of software and/or firmware in electronic devices |
US20050108700A1 (en) * | 2003-11-18 | 2005-05-19 | Yunti Chen | Method for controlling upgrade of firmware |
US20050158100A1 (en) * | 2002-04-01 | 2005-07-21 | Takehito Yamaguchi | Receiving device, printer, and firmware update system |
US6930785B1 (en) * | 2000-03-17 | 2005-08-16 | Hewlett-Packard Development Company, L.P. | Automatic remote firmware upgrade |
US6935785B2 (en) * | 2001-12-19 | 2005-08-30 | Nsk Ltd. | Linear guide rail and linear guide rolling die |
US6950875B1 (en) * | 2000-05-09 | 2005-09-27 | Sun Microsystems, Inc. | Message conductors in a distributed computing environment |
US6959416B2 (en) * | 2001-01-30 | 2005-10-25 | International Business Machines Corporation | Method, system, program, and data structures for managing structured documents in a database |
US6971095B2 (en) * | 2000-05-17 | 2005-11-29 | Fujitsu Limited | Automatic firmware version upgrade system |
US20050270560A1 (en) * | 2004-06-03 | 2005-12-08 | Ferlitsch Andrew R | Systems and methods for managing a plurality of resources across multiple printing devices |
US20050272417A1 (en) * | 2004-05-13 | 2005-12-08 | Asia Optical Co., Inc. | Handheld electronic device and method for firmware upgrade |
US6976163B1 (en) * | 2000-07-12 | 2005-12-13 | International Business Machines Corporation | Methods, systems and computer program products for rule based firmware updates utilizing certificate extensions and certificates for use therein |
US6976062B1 (en) * | 1999-09-22 | 2005-12-13 | Intermec Ip Corp. | Automated software upgrade utility |
US20060174242A1 (en) * | 2005-02-01 | 2006-08-03 | Microsoft Corporation | Publishing the status of and updating firmware components |
US7093244B2 (en) * | 2001-04-18 | 2006-08-15 | Domosys Corporation | Method of remotely upgrading firmware in field-deployed devices |
US20060242578A1 (en) * | 2003-06-27 | 2006-10-26 | Koninklijke Kpn N.V. | Method for managing content |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU6150699A (en) | 1998-09-24 | 2000-04-10 | Ericsson Inc. | Remote firmware upgrade |
GB2348987A (en) | 1998-12-11 | 2000-10-18 | Hewlett Packard Co | Upgrading firmware from a web site using an applet |
JP2008507775A (en) | 2004-07-21 | 2008-03-13 | ソフトリシティ インコーポレイテッド | System and method for extracting and creating application meta information in a software application repository |
-
2007
- 2007-04-02 US US11/695,206 patent/US8019794B2/en not_active Expired - Fee Related
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6341143B1 (en) * | 1993-07-02 | 2002-01-22 | Multi-Tech Systems, Inc. | Modem with firmware upgrade feature |
US6526092B1 (en) * | 1993-07-02 | 2003-02-25 | Multi-Tech Systems, Inc. | Modem with firmware upgrade feature |
US6928108B2 (en) * | 1993-07-02 | 2005-08-09 | Multi-Tech Systems, Inc. | Modem with firmware upgrade feature |
US5574899A (en) * | 1993-09-16 | 1996-11-12 | Fujitsu Limited | Generation number managing apparatus for adjusting generation numbers among processors or program files |
US6055632A (en) * | 1997-09-25 | 2000-04-25 | Allen-Bradley Company, Llc | Method and apparatus for transferring firmware to a non-volatile memory of a programmable controller system |
US6360362B1 (en) * | 1998-02-20 | 2002-03-19 | Intel Corporation | Automatic update of camera firmware |
US6976062B1 (en) * | 1999-09-22 | 2005-12-13 | Intermec Ip Corp. | Automated software upgrade utility |
US6930785B1 (en) * | 2000-03-17 | 2005-08-16 | Hewlett-Packard Development Company, L.P. | Automatic remote firmware upgrade |
US6671802B1 (en) * | 2000-04-13 | 2003-12-30 | Hewlett-Packard Development Company, L.P. | Performance optimization of computer system by dynamically and immediately updating a configuration setting based on detected change in preferred use |
US6950875B1 (en) * | 2000-05-09 | 2005-09-27 | Sun Microsystems, Inc. | Message conductors in a distributed computing environment |
US6971095B2 (en) * | 2000-05-17 | 2005-11-29 | Fujitsu Limited | Automatic firmware version upgrade system |
US6976163B1 (en) * | 2000-07-12 | 2005-12-13 | International Business Machines Corporation | Methods, systems and computer program products for rule based firmware updates utilizing certificate extensions and certificates for use therein |
US20020052718A1 (en) * | 2000-08-04 | 2002-05-02 | Little Mike E. | Automated problem identification system |
US6959416B2 (en) * | 2001-01-30 | 2005-10-25 | International Business Machines Corporation | Method, system, program, and data structures for managing structured documents in a database |
US20020138567A1 (en) * | 2001-03-21 | 2002-09-26 | Nec Corporation | Update system, update client apparatus, update server apparatus, and programs |
US7093244B2 (en) * | 2001-04-18 | 2006-08-15 | Domosys Corporation | Method of remotely upgrading firmware in field-deployed devices |
US20020188934A1 (en) * | 2001-06-12 | 2002-12-12 | Nortel Networks Limited | Method and system for upgrading existing firmware on third party hardware |
US20030041127A1 (en) * | 2001-08-27 | 2003-02-27 | Turnbull Paul F. | System and methods for the automatic discovery, notification and installation of firmware upgrades |
US20030086107A1 (en) * | 2001-11-02 | 2003-05-08 | Johnson Steven Mark | Remote firmware upgrade via I/O connection |
US6935785B2 (en) * | 2001-12-19 | 2005-08-30 | Nsk Ltd. | Linear guide rail and linear guide rolling die |
US20050158100A1 (en) * | 2002-04-01 | 2005-07-21 | Takehito Yamaguchi | Receiving device, printer, and firmware update system |
US20050102660A1 (en) * | 2002-04-12 | 2005-05-12 | Shao-Chun Chen | Initialization and update of software and/or firmware in electronic devices |
US20030217193A1 (en) * | 2002-05-17 | 2003-11-20 | Sun Microsystems, Inc. | Method, system and article of manufacture for a firmware image |
US20040093597A1 (en) * | 2002-11-05 | 2004-05-13 | Rao Bindu Rama | Firmware update system for facilitating firmware update in mobile handset related applications |
US20040210894A1 (en) * | 2003-04-17 | 2004-10-21 | Zarco Maria F. | Image-formation device firmware having modular upgrade capability |
US20060242578A1 (en) * | 2003-06-27 | 2006-10-26 | Koninklijke Kpn N.V. | Method for managing content |
US20050038808A1 (en) * | 2003-08-15 | 2005-02-17 | Kutch Patrick G. | System and method for utilizing a modular operating system (OS) resident agent allowing an out-of-band server management |
US20050108700A1 (en) * | 2003-11-18 | 2005-05-19 | Yunti Chen | Method for controlling upgrade of firmware |
US20050272417A1 (en) * | 2004-05-13 | 2005-12-08 | Asia Optical Co., Inc. | Handheld electronic device and method for firmware upgrade |
US20050270560A1 (en) * | 2004-06-03 | 2005-12-08 | Ferlitsch Andrew R | Systems and methods for managing a plurality of resources across multiple printing devices |
US20060174242A1 (en) * | 2005-02-01 | 2006-08-03 | Microsoft Corporation | Publishing the status of and updating firmware components |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090210567A1 (en) * | 2008-02-20 | 2009-08-20 | Seiko Epson Corporation | Host apparatus and method for controlling the same |
US20110004874A1 (en) * | 2009-07-06 | 2011-01-06 | Canon Kabushiki Kaisha | Information processing apparatus, method of controlling thereof, and computer-readable storage medium storing program therefor |
US8583559B2 (en) * | 2009-07-06 | 2013-11-12 | Canon Kabushiki Kaisha | Information processing apparatus, method of controlling thereof, and computer-readable storage medium storing program therefor |
JP2011022712A (en) * | 2009-07-14 | 2011-02-03 | Canon Inc | Distribution system, distribution apparatus, and distribution method |
US20110154313A1 (en) * | 2009-12-21 | 2011-06-23 | International Business Machines Corporation | Updating A Firmware Package |
US9639347B2 (en) * | 2009-12-21 | 2017-05-02 | International Business Machines Corporation | Updating a firmware package |
KR20130104283A (en) * | 2012-03-13 | 2013-09-25 | 삼성테크윈 주식회사 | Method of updating firmware |
KR101685425B1 (en) | 2012-03-13 | 2016-12-12 | 한화테크윈 주식회사 | Method of supplying firmware by firmware server and method of updating firmware |
US9317666B2 (en) * | 2012-03-30 | 2016-04-19 | Hewlett Packard Enterprise Development Lp | License management of firmware-controllable features in computer systems |
US20150074815A1 (en) * | 2012-03-30 | 2015-03-12 | Hewlett-Packard Development Company, L.P. | License management of firmware-controllable features in computer systems |
US9164757B2 (en) * | 2013-02-05 | 2015-10-20 | Samsung Electronics Co., Ltd. | Image forming apparatus, tracking apparatus, managing apparatus and method of updating firmware of image forming apparatus |
US20140223424A1 (en) * | 2013-02-05 | 2014-08-07 | Samsung Electronics Co., Ltd | Image forming apparatus, tracking apparatus, managing apparatus and method of updating firmware of image forming apparatus |
US9696948B2 (en) * | 2013-05-30 | 2017-07-04 | Canon Kabushiki Kaisha | Printing system, printing service apparatus, image forming apparatus, control method, and storage medium |
US20140355049A1 (en) * | 2013-05-30 | 2014-12-04 | Canon Kabushiki Kaisha | Printing system, printing service apparatus, image forming apparatus, control method, and storage medium |
US20150169310A1 (en) * | 2013-12-12 | 2015-06-18 | Lenovo (Singapore) Pte, Ltd. | Maintaining firmware |
US20150178066A1 (en) * | 2013-12-20 | 2015-06-25 | Netapp, Inc. | System, Method, and Computer Program Product For Managing Software Updates |
US9471455B2 (en) * | 2013-12-20 | 2016-10-18 | Netapp, Inc. | System, method, and computer program product for managing software updates |
US9507686B2 (en) | 2013-12-20 | 2016-11-29 | Netapp, Inc. | System, method, and computer program product for monitoring health of computer system assets |
US9612932B2 (en) | 2013-12-20 | 2017-04-04 | Netapp, Inc. | System, method, and computer program product for monitoring computer system infrastructure and assets |
US9652493B1 (en) * | 2014-03-31 | 2017-05-16 | Dell Products Lp | Digitized release notes |
US20160203302A1 (en) * | 2014-09-19 | 2016-07-14 | Hewlett Packard Enterprise Development Lp | License management of firmware-controllable features in computer systems |
US20190250897A1 (en) * | 2018-02-13 | 2019-08-15 | Dell Products, Lp | Information Handling System to Treat Demoted Firmware with Replacement Firmware |
US10613847B2 (en) * | 2018-02-13 | 2020-04-07 | Dell Products, L.P. | Information handling system to treat demoted firmware with replacement firmware |
EP3588276A1 (en) * | 2018-06-27 | 2020-01-01 | Hewlett-Packard Enterprise Development LP | Selective download of a portion of a firmware bundle |
WO2021006929A1 (en) * | 2019-07-11 | 2021-01-14 | Microchip Technology Incorporated | System for improved evaluation of semiconductor hardware and corresponding method |
US11526343B2 (en) | 2019-07-11 | 2022-12-13 | Microchip Technology Incorporated | System for improved evaluation of semiconductor hardware and corresponding method |
Also Published As
Publication number | Publication date |
---|---|
US8019794B2 (en) | 2011-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8019794B2 (en) | Firmware repository for MFP devices | |
US7272610B2 (en) | Knowledge management system | |
US7793285B2 (en) | Web installer driver and management through a remote network | |
US8069243B2 (en) | Document management server, method, storage medium and computer data signal, and system for managing document use | |
US7797335B2 (en) | Creation and persistence of action metadata | |
US8272028B2 (en) | Approach for managing access to electronic documents on network devices using document retention policies and document security policies | |
US20040204949A1 (en) | Method and system for implementing group policy operations | |
JP5428668B2 (en) | License management server, license management method and program | |
US20100211945A1 (en) | License management system, license management computer, license management method, and license management program embodied on computer readable medium | |
US20090147299A1 (en) | Status monitoring system and method | |
US20100095348A1 (en) | System and method for management and translation of technical security policies and configurations | |
US20120290544A1 (en) | Data compliance management | |
JP6167118B2 (en) | How to identify user access to a digital document using an existing rights management policy with modifications | |
KR20100115388A (en) | Image processing apparatus, control method thereof and storage medium | |
JP2006520975A (en) | Non-intrusive automatic off-site patch fingerprinting and updating system and method | |
US20090265629A1 (en) | Systems and methods for extending assistance in a multi-function peripheral device | |
WO2015051331A1 (en) | Cloud data loss prevention integration | |
US9081528B2 (en) | Information processing system, method of processing information, program, and recording medium | |
US8473755B2 (en) | Application installing method | |
JP2007048080A (en) | Service providing device, method and program | |
JP2008004041A (en) | Document management device and document management method | |
JP2011198064A (en) | Program, apparatus and system for processing information | |
US20110153671A1 (en) | Information processing apparatus, information processing method and computer readable medium | |
JP2007140958A (en) | Document management system | |
EP1250669A4 (en) | Data warehouse computing system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SHARP LABORATORIES OF AMERICA, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PATHAK, RABINDRA;OLBRICHT, ERIC THOMAS;BORCHERS, GREGORY EUGENE;REEL/FRAME:019100/0798 Effective date: 20070327 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SHARP KABUSHIKI KAISHA, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SHARP LABORATORIES OF AMERICA, INC.;REEL/FRAME:027110/0150 Effective date: 20111024 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230913 |