EP1508091A4 - Protocole de mise a jour de systeme et controleur initialisable a partir d'un c.d. a systeme d'exploitation incorpore - Google Patents

Protocole de mise a jour de systeme et controleur initialisable a partir d'un c.d. a systeme d'exploitation incorpore

Info

Publication number
EP1508091A4
EP1508091A4 EP03741823A EP03741823A EP1508091A4 EP 1508091 A4 EP1508091 A4 EP 1508091A4 EP 03741823 A EP03741823 A EP 03741823A EP 03741823 A EP03741823 A EP 03741823A EP 1508091 A4 EP1508091 A4 EP 1508091A4
Authority
EP
European Patent Office
Prior art keywords
output device
client
peripheral output
software update
packed file
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.)
Withdrawn
Application number
EP03741823A
Other languages
German (de)
English (en)
Other versions
EP1508091A1 (fr
Inventor
Vincent Wu
Sheng Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshiba Corp
Toshiba Tec Corp
Original Assignee
Toshiba Corp
Toshiba Tec Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US10/156,521 external-priority patent/US20030226005A1/en
Priority claimed from US10/156,303 external-priority patent/US20030226139A1/en
Application filed by Toshiba Corp, Toshiba Tec Corp filed Critical Toshiba Corp
Publication of EP1508091A1 publication Critical patent/EP1508091A1/fr
Publication of EP1508091A4 publication Critical patent/EP1508091A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/1203—Improving or facilitating administration, e.g. print management
    • G06F3/1204—Improving or facilitating administration, e.g. print management resulting in reduced user or operator actions, e.g. presetting, automatic actions, using hardware token storing data
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/123—Software or firmware update, e.g. device firmware management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12—Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201—Dedicated interfaces to print systems
    • G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285—Remote printer device, e.g. being remote from client or server

Definitions

  • This invention is related to a communication protocol for updating files on a printer controller, and to the field of booting operating systems, particularly the type used for controllers of output peripheral components, such as network printers.
  • a printer controller which function is to control all printing functions on a related peripheral output device, will sometimes require files to be loaded from external distribution means for the purpose of providing software upgrades, new software installations, and/or batch configurations.
  • Some printers allow these tasks to be done by physically copying the files to the printer controller via a storage distribution device (e.g., CD-ROM, floppy drive, etc.), and then executing corresponding commands for setup and configuration through conventional input devices (e.g., mouse and keyboard) and a video display panel.
  • a storage distribution device e.g., CD-ROM, floppy drive, etc.
  • a workstation user may easily apply a patch for a certain component by running the self- extracting and self-installing patch file provided by a vendor.
  • the same patch may also be applied to the printer controller with the same components.
  • the printer lacks input device accommodations (e.g., monitor, keyboard), it is not easy to initiate the install process of such software updates.
  • What is needed is a client-server networking protocol that would facilitate uploading of the required file(s) to the printer controller, and issuing of any commands necessary for installation.
  • the controllers of network printers such as models SC-2 and GL-1010 controllers available from Toshiba, use the Microsoft Embedded NT operating system (OS).
  • OS Microsoft Embedded NT operating system
  • a controller CD-ROM is installed.
  • the CD-ROM is used to boot up the system, after which the updates are made to the OS software on the controller hard drive.
  • the software update is completed, the user must remove the CD-ROM and reboot the controller from the hard drive.
  • the controller accepts print jobs from a client.
  • the controller can also network with the client to set up system and user parameters, and can store print/scan jobs on the controller hard drive.
  • the above steps of booting from the CD and rebooting from the hard drive can be cumbersome and time consuming. Also, additional time and effort may often be expended in diagnosing and troubleshooting OS problems after a software update. Also, the hard drive can be unreliable storage medium, vulnerable to computer viruses and other sources of errors or loss of data. Also, the hard drive is an additional component that adds to the size and expense of the controller.
  • the present invention disclosed and claimed herein in one aspect thereof, comprises a system update protocol.
  • a software update is packed into a packed file, which packed file includes a unique signature.
  • the packed file is uploaded from a trusted client computer to the network printer.
  • the integrity of the packed file is automatically checked on the network printer by performing a checksum and signature comparison to ensure the packed file is transmitted correctly.
  • the packed file is resent from the client when the packed file is determined to be corrupt.
  • the packed file is unpacked into a predetermined directory structure of unpacked files.
  • the client computer then signals the network printer cause installation of the software update on the network printer.
  • printer controller which includes one or more non- volatile memory elements for storing print/fax/scan data and printer controller system parameters.
  • the non-volatile memory elements can include flash memory PCMCIA cards.
  • a nonvolatile storage medium is also provided for retaining an operating system, wherein the printer controller is bootable from the non-volatile storage medium.
  • the non-volatile storage medium is preferably a CD-ROM or other removable type data disc.
  • FIG. 1 illustrates a client/server protocol exchange flow diagram of the protocol
  • FIG. 2 illustrates a client/server system block diagram utilizing the disclosed protocol architecture
  • Fig. 3 depicts a bootable CD controller in accordance with the present invention.
  • the disclosed protocol architecture provides the capability of allowing the print controller to execute the installation commands after correctly receiving the file.
  • the disclosed system update protocol is not limited to a single underlying transport. It is designed to run on, for example, TCP/IP (Transmission Control Protocol/Internet Protocol - a Microsoft® protocol suite) and EPX/SPX (Internet Packet eXchange/Sequenced Packet eXchange - a Novell® communication protocol).
  • TCP/IP Transmission Control Protocol/Internet Protocol - a Microsoft® protocol suite
  • EPX/SPX Internet Packet eXchange/Sequenced Packet eXchange - a Novell® communication protocol.
  • the protocol consists of a reduced set of commands.
  • the one or more target files are packed (i.e., compressed into a single large file) into a packed file, and a signature is prepended to the packed file for security reasons.
  • the packed file may be optionally encrypted with a special agreed-upon key for added security.
  • FIG. 1 there is illustrated a client/server protocol exchange flow diagram of the protocol.
  • the horizontal lines between a client program flow diagram 100 and server program flow diagram 102 denote the direction and type of content of the network packets exchanged between the client program on a client and server program on the print controller (also denoted as a peripheral output device), while the vertical lines between the blocks of a flow diagram denote the flow of control.
  • the disclosed protocol consists of the following commands: SEND, to transfer a chunk of the target file; SENDEND, to signal the end of transferring; ACTION, to instruct the server what to do with the file; STATUS, to check the status of the action; and STATUSREPLY, to return the status of the transfer or action.
  • the server program 102 running on the printer controller is responsible for servicing these commands.
  • the client program 100 running on a workstation (or client) is the driver of a task, i.e., the client controls the processes on the printer controller.
  • Flow begins in a function block 104 where the client program 100 first "packs" all of the appropriate files into a single packed file, which single packed file includes a file header that contains a special signature recognized only by the printer controller (i.e., server program) and trusted client programs.
  • the signature may be encrypted by a variable key (e.g., based upon file size) so that it cannot simply be copied to another file header.
  • the client program 100 also appends a checksum to the end of the packed file. Thus the integrity of the packed file can be ascertained by checking both the unique signature and the checksum.
  • the server program 102 is currently in a "listen" mode, as indicated in a function block 106, awaiting incoming commands from a client. Flow is then to a function block 108 where the client program 100 performs a connect function by initiating a synchronization (i.e., also denoted as "synch") operation over a flow line 110 to the function block 106 of the server program 102 in order to establish a reliable connection to the printer controller.
  • the server program 102 responds with synch commands over a flow line 112 to the function block 108.
  • two listening sockets will be opened; one for TCP/IP traffic, and another for IPX/SPX traffic.
  • Flow in the client program 100 is then to a function block 114 where the packed file is transmitted to the printer controller through a sequence of SEND commands.
  • the client program 100 then issues the sequence of SEND commands to the server program 102, as indicated by a signal flow line 116 to a function block 118, to transfer the packed file to the printer controller.
  • Flow in the server program 102 is to the function block 118 where the SEND commands are received, and the received file segments associated with the sequence of the SEND commands are written as a single data file set.
  • flow in the client program 100 is to a function block 120 where the client program 100 transmits a SENDEND command to the server program 102, as indicated by a signal flow line 122 to a function block 124.
  • Flow in the server program 102 is to the function block 124 where after the last file segment has been received, and the server program 102 closes the data file.
  • the server program 102 receives SENDEND command, it will have received the entire file.
  • Flow in the client program 100 is then to a function block 126 where the client program 100 queries the server program 102 for the status of the file transmission by sending the STATUS command, as indicated by a signal flow line 128 to a function block 130.
  • Flow in the server program 102 is to the function block 130 where the data file is unpacked, and a "sanity" check is performed to determine if the file was correctly transmitted, i.e., by authenticating the signature, recalculating the checksum, etc.
  • flow in the server program 102 is to a function block 132 where the printer controller sends back a "processing" Reply signal to the client program 100, as indicated by a signal flow line 134 to a function block 136.
  • flow continues to a decision block 138 to determine if the received packed file passed the sanity check. If not, flow is out the "N" path to a function block 140, where the packed file is deleted. Flow then loops back to the input of the function block 118 to receive the next retransmission of the packed file.
  • the server program 102 also signals the client program 100 in the Reply signal of packed file failing the sanity check (i.e., a "corrupted" file). Flow in the client program 100 is to the function block 136 where the status Reply is received. The client program 100 then interrogates the received status Reply signal, as indicated in a decision block 142. If the Reply signal indicates that the server program 102 is in a state of "processing,” flow is out the "P" path back to the input of the function block 126 to continue querying the server program 102.
  • the printer controller includes a readable storage medium, e.g., hard disk drive, or a sufficient amount of RAM memory to accommodate the unpacked files.
  • the ACTION instructions can further include the actions of "controller software update,” “run,” or "configure.”
  • Flow in the server program 102 is to the function block 148 where the ACTION signal is received and processed.
  • Flow in the server program 102 is to a function block 150 where the received ACTION is performed.
  • the "controller software update” action initiates a predefined installation process in the printer controller to upgrade the existing software.
  • the packed file includes at least one executable file.
  • the "run” action simply causes execution of the one or more executable files of the unpacked file set, which is suitable for installing patches for a single module.
  • the "configure” action initiates a special operating system process, e.g., a system command associated with RegEdit, to add/change some system parameters of the printer controller, as specified in the unpacked file set.
  • the client program 100 may optionally check the execution status of the ACTION in the server program 102.
  • flow is to a function block 152 of the client program 100 where a STATUS signal is transmitted to the server program 102, as indicated by a signal flow line 154 from the function block 152 to the function block 150.
  • a function block 156 where the server program 102 transmits a "processing" Reply signal to the client program 100, as indicated by a Reply signal flow line 158 to a status function block 160 of the client program 100.
  • the processing time may take longer.
  • the server program 102 may need to be rebooted.
  • flow is to a decision block 162 to determine if the server program 102 needs to be rebooted, in accordance with the particular ACTION instruction. If not, flow is out the "N" path of decision block 162 to a Continue terminal 164 of the server, and therefrom signaling an "OK" status across a signal line 166 to the status function block 160 of the client program 100 to indicate that the ACTION has been completed without a reboot.
  • flow is out the "Y" path of decision block 162 of the server program 102 to a function block 168 to terminate the connection to the client program 100 during the rebooting process.
  • a "Reset" signal is then transmitted from the server program 102 to the status function block 160 of the client program 100, as indicated by a signal flow line 170 to the status function block 160.
  • Flow is then to a reboot terminal 172 where the server program is rebooted to implement the software updates. Note that the connection between the client and server will not automatically restore after the printer controller restarts.
  • the client program 100 then takes the appropriate action in response to the signals received into the status function block 160.
  • flow is to a decision block 174 where the client program 100 interrogates the status signals received from the server program 102. If the status is "processing,” flow is out the "P” path back to the input of the function block 152 to continue querying the server program 102. If the status is either "OK" or "Reset,” flow is out the "O" path to a Continue terminal 176 of the client.
  • the details of Continue terminal 176 of the client are not shown in FIG. 1.
  • the client program 100 may choose to start another transfer on the same connection, i.e., the process associated with a new sequence of SEND commands in the function block 114, or disconnect from the server program 102 (printer controller) and start a new connection to another printer controller.
  • the server program 102 printer controller
  • the server program 102 will delete the received file and go back to wait for a new sequence of SEND commands, as associated with function block 118. If the connection is terminated by the client, the controller will return to the listening mode associated with function block 102, to wait for a new connection.
  • the disclosed protocol works well for a special-purpose printer controller running on top of the operating system having networking support.
  • a general-purpose file transfer protocol e.g., FTP (File Transfer Protocol)
  • FTP File Transfer Protocol
  • the Berkeley socket interface can be used to implement both the client program 100 and server program 102.
  • a client computer 200 is disposed on a network 202, e.g., a
  • first network peripheral output device 204 which in this particular embodiment is a printer controller.
  • first network peripheral output device 204 is not restricted to a printer controller, but can be a variety of network-based equipment suitably configured to execute the disclosed protocol architecture, for example, a multi-function output device (that includes capabilities of faxing, scanning, printing, etc.).
  • the client computer 200 includes the client protocol program 100, and the first peripheral output device 204 includes the server program 102.
  • Both of the client and server protocol programs (100 and 102) can be implemented in firmware (e.g., EEPROM) in either or both of the client computer 200 and the first peripheral output device 204.
  • the first peripheral output device 204 opens two listening sockets to accommodate either or both TCP/IP traffic and IPX/SPX traffic communicated across the network 202.
  • the client computer 200 sends only IPX/SPX traffic on the relatively local network 202
  • the first peripheral output device 204 can communicate with the client computer 200 to receive the updated software, and execute the disclosed protocol to facilitate the installation of the software and ascertain the status of the updating process on the first peripheral output device 204.
  • networks can extend great distances utilizing a global communication network (GCN) 206, e.g., the Internet, over which communication is facilitated utilizing the TCP/IP protocol suite.
  • GCN global communication network
  • a second peripheral output device 208 disposed on the GCN 206 and executing the disclosed server protocol 102 will also open the two listening sockets to accommodate either or both TCP/IP traffic and IPX/SPX traffic communicated across the GCN 206.
  • the client computer 200 can be used to upload software to the second peripheral output device 208, and monitor the software installation process.
  • Another aspect of the present invention is to simplify the aforementioned two-step boot operation.
  • the controller of the present invention uses OS and controller code from a non-volatile storage disc, preferably a CD-ROM or DVD-ROM. It utilizes external memory cards (non- volatile flash memory) to store user data and system parameters which would have been stored on hard drive. Since the static object code of the OS and controller resides on a different media than the variable user data and parameters, updating (or upgrading) the OS or
  • Controller becomes extremely trivial.
  • the administrator simply shuts down the system, replaces the CD with a new version, and restarts the system.
  • the data and system parameters remain unchanged across system restart.
  • the present bootable CD controller uses an embedded operating system, preferably "Windows NT Embedded” sold by Microsoft Corporation.
  • An embedded OS offers several benefits for this type of implementation. For example, this OS does not require the use of a keyboard, mouse or VGA monitor.
  • selectable modules can be installed on various destination media, including a hard drive, a ROM, and a CD-ROM.
  • An embedded OS is reliable in system shutdown, reboot, and boot up states. As shown in Fig. 3, a CD-ROM 306 replaces the previous function of the hard drive 318, and the OS and system services remain with the CD-ROM 306, thus making it bootable.
  • Storage for system parameters 314 and print/fax/scan data 316 is stored in a Flash memory card (not shown).
  • the Multifunction Peripheral 302 of FIG 3 comprises a Copier/Print Device.
  • Multifunction Peripheral 302 has a network card 304 for communicating over a network with other devices such as other computers, printers, clients, and servers.
  • the CPU 308 controls the operation of the Multifunction Peripheral 302 and has System Memory for storing various operating parameters.
  • the memory card (not shown), which may be a flash memory card, PCMCIA card, or other types of non- volatile RAM that are well known in the art, comprises the storage memory control 312, memory card system parameters 314 and print/fax/scan data 316.
  • the CD-ROM contains the bootable partition, the Windows NT Embedded Operating System files, the basic NT services, and the device drivers.
  • the CD-ROM also contains the controller service files for "Print,” “Fax,” “Scan” and “Network” functions, along with web page files.
  • the system parameters are directed to the system memory card. This is preferably accomplished using the embedded OS tool called “Target Designer.” Of course, this can also be accomplished with other similar tools.
  • the system memory card also includes a "Disable Page” file (i.e. a memory swap file) from the embedded OS and Windows NT activities settings (such as network setup parameters).
  • the system memory card can retain other variable data such as a "Print Spooler” temporary file storage and system event logs.
  • the data is directed to the data memory card, and can include print job data. This print job data is in a file format that encompasses the function of the "job record” that had previously been stored in the NT registry.
  • the data memory card also includes fax job data, scan data and email data, along with any job or message logs.
  • a "Storage Volume Control" utility program is preferably implemented to monitor memory card storage volume. This utility program includes software settings to limit the usage of partition, to prevent a maximum data limit to be exceeded.
  • the present bootable CD controller provides many benefits, including the phase-out and discontinuation of the hard drive controller model, resulting in reducing the size of the hardware and the cost of distribution. Also, reliability of storage media is improved by replacing the volatile hard drive with a CD-ROM.
  • the bootable CD also provides savings of time and effort for software version upgrades, and OS trouble shooting and diagnostics.
  • the invention also provides virus protection by employing read-only media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Accessory Devices And Overall Control Thereof (AREA)
  • Stored Programmes (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un protocole de mise à jour de système. Une mise à jour de logiciel est condensée dans un fichier condensé comprenant une signature unique. Ledit fichier condensé est téléchargé d'un ordinateur client fiable vers une imprimante de réseau. L'intégrité du fichier condensé est automatiquement vérifiée sur l'imprimante de réseau par exécution d'un total de contrôle et d'une comparaison de signature afin de s'assurer que le fichier condensé est transmis correctement. Le fichier condensé est renvoyé lorsqu'on détermine que ce fichier est altéré, et il se présente sous forme non condensée dans une structure de répertoire de fichiers non condensés prédéterminée. L'ordinateur client signale ensuite à l'imprimante de réseau le déclenchement de l'installation de la mise à jour du logiciel sur ladite imprimante. Dans un autre mode de réalisation, le contrôleur de l'imprimante comprend un ou plusieurs élément(s) de mémoire non volatile permettant de stocker des données d'impression/télécopie/balayage et des paramètres de système de contrôleur d'imprimante. Ledit contrôleur d'imprimante peut être initialisé à partir d'un support de stockage non volatil tel qu'un CD-ROM ou un autre disque de données du type amovible.
EP03741823A 2002-05-28 2003-05-28 Protocole de mise a jour de systeme et controleur initialisable a partir d'un c.d. a systeme d'exploitation incorpore Withdrawn EP1508091A4 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US10/156,521 US20030226005A1 (en) 2002-05-28 2002-05-28 Bootable CD controller with embedded operating system
US10/156,303 US20030226139A1 (en) 2002-05-28 2002-05-28 System update protocol
US156303 2002-05-28
US156521 2002-05-28
PCT/US2003/016752 WO2003100610A1 (fr) 2002-05-28 2003-05-28 Protocole de mise a jour de systeme et controleur initialisable a partir d'un c.d. a systeme d'exploitation incorpore

Publications (2)

Publication Number Publication Date
EP1508091A1 EP1508091A1 (fr) 2005-02-23
EP1508091A4 true EP1508091A4 (fr) 2005-12-21

Family

ID=29586318

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03741823A Withdrawn EP1508091A4 (fr) 2002-05-28 2003-05-28 Protocole de mise a jour de systeme et controleur initialisable a partir d'un c.d. a systeme d'exploitation incorpore

Country Status (4)

Country Link
EP (1) EP1508091A4 (fr)
JP (1) JP2005527908A (fr)
AU (1) AU2003273157A1 (fr)
WO (1) WO2003100610A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1564624A3 (fr) * 2004-02-10 2006-04-12 Ricoh Company, Ltd. La protection contre les virus pour les périphériques multifonctionnels
JP4508687B2 (ja) * 2004-03-15 2010-07-21 株式会社リコー カード型メモリのインターフェース回路
US7640592B2 (en) * 2004-06-12 2009-12-29 Microsoft Corporation Installation setup
JP2006011665A (ja) * 2004-06-23 2006-01-12 Ricoh Co Ltd 画像処理制御装置
SG194374A1 (en) * 2007-11-27 2013-11-29 Boeing Co Method and apparatus for loadable software airplane parts (lsap) distribution
JP2011034130A (ja) * 2009-07-29 2011-02-17 Canon Inc 情報処理装置、情報処理方法、及びプログラム
GB2483166B (en) 2010-08-27 2013-10-23 Fxi Technologies As Electronic devices
RU2495487C1 (ru) 2012-08-10 2013-10-10 Закрытое акционерное общество "Лаборатория Касперского" Система и способ для определения доверия при обновлении разрешенного программного обеспечения
JP2015053015A (ja) * 2013-09-09 2015-03-19 京セラドキュメントソリューションズ株式会社 ファームウェア、及び電子機器

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0601704A1 (fr) * 1992-11-18 1994-06-15 Canon Information Systems, Inc. Méthode et appareil pour modifier à distance des programmes logiciels mémorisés dans une carte interface couplée à un périphérique de réseau
EP1043656A2 (fr) * 1999-04-09 2000-10-11 Sun Microsystems, Inc. Méthode et appareil pour synchronisation de firmware
WO2001004749A1 (fr) * 1999-07-08 2001-01-18 Axis Ab Procede et dispositif de mise a niveau de micrologiciel dans un systeme integre
WO2001093577A2 (fr) * 2000-05-26 2001-12-06 General Instrument Corporation Autorisation par jetons de cryptogramme

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6167567A (en) * 1998-05-05 2000-12-26 3Com Corporation Technique for automatically updating software stored on a client computer in a networked client-server environment
US6718407B2 (en) * 1999-09-30 2004-04-06 Intel Corporation Multiplexer selecting one of input/output data from a low pin count interface and a program information to update a firmware device from a communication interface
US20010029530A1 (en) * 2000-03-03 2001-10-11 Yoshiko Naito System and method of managing resource in network system
US7362459B2 (en) * 2000-11-17 2008-04-22 Seiko Epson Corporation Network device and printer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0601704A1 (fr) * 1992-11-18 1994-06-15 Canon Information Systems, Inc. Méthode et appareil pour modifier à distance des programmes logiciels mémorisés dans une carte interface couplée à un périphérique de réseau
EP1043656A2 (fr) * 1999-04-09 2000-10-11 Sun Microsystems, Inc. Méthode et appareil pour synchronisation de firmware
WO2001004749A1 (fr) * 1999-07-08 2001-01-18 Axis Ab Procede et dispositif de mise a niveau de micrologiciel dans un systeme integre
WO2001093577A2 (fr) * 2000-05-26 2001-12-06 General Instrument Corporation Autorisation par jetons de cryptogramme

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of WO03100610A1 *
U.S. DEPARTMENT OF COMMERCE/NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY: "FIPS PUB 182-2 + change notice 1: Digital Signature Standard (DSS)", 27 January 2000 (2000-01-27), Gaithersburg, MD, pages 1 - 76, XP002345589, Retrieved from the Internet <URL:http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf> [retrieved on 20050915] *

Also Published As

Publication number Publication date
AU2003273157A1 (en) 2003-12-12
WO2003100610A1 (fr) 2003-12-04
WO2003100610A8 (fr) 2004-03-04
EP1508091A1 (fr) 2005-02-23
JP2005527908A (ja) 2005-09-15
AU2003273157A8 (en) 2003-12-12

Similar Documents

Publication Publication Date Title
US20030226139A1 (en) System update protocol
US7290258B2 (en) Managing multiple devices on which operating systems can be automatically deployed
US7421688B1 (en) Methods and systems for updating the firmware on a plurality of network-attached computing devices
US6259442B1 (en) Downloading software from a server to a client
US7080134B2 (en) Systems and methods for software distribution and management
US5701492A (en) Fail-safe flashing of EPROM
US20040267716A1 (en) Using task sequences to manage devices
US20040103347A1 (en) Method and apparatus for firmware restoration in modems
US20020054069A1 (en) Downloading software from a server to a client
US20140237461A1 (en) Method and apparatus for differential file based update for embedded systems
US6804773B1 (en) System and method for transferring information over a network
US20050216911A1 (en) Deployment method and system for multiple remote computers
US7349327B2 (en) System and method for remotely updating a network device
US7107331B2 (en) System and method for configuring digital image devices
US20090254641A1 (en) Network card capable of remote boot and method thereof
US20050149923A1 (en) System update protocol
EP1508091A1 (fr) Protocole de mise a jour de systeme et controleur initialisable a partir d&#39;un c.d. a systeme d&#39;exploitation incorpore
US8086659B2 (en) Task sequence interface
CN110737444A (zh) 基于固件的操作系统远程自适应动态部署方法及系统
JP2004165734A (ja) 画像形成装置及びファームウェアプログラム
US20030226005A1 (en) Bootable CD controller with embedded operating system
CN111492640A (zh) 用于从非联网的远程定位数据生成设备检索数据的系统和方法
CN119960782A (zh) 数据更新方法、装置、设备、存储介质及程序产品
CN100390736C (zh) 远端部署多部计算机的方法与系统
KR100456978B1 (ko) 에이전트의 파일 다운로드 방법

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20041126

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 06F 9/445 B

Ipc: 7G 06F 9/45 A

A4 Supplementary search report drawn up and despatched

Effective date: 20051107

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TOSHIBA TEC KABUSHIKI KAISHA

Owner name: TOSHIBA CORPORATION

17Q First examination report despatched

Effective date: 20090630

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20091111