WO2005029319A1 - Equipement peripherique et procede de gestion correspondant munis d'une fonction pour la gestion d'un programme de pilotes internes - Google Patents

Equipement peripherique et procede de gestion correspondant munis d'une fonction pour la gestion d'un programme de pilotes internes Download PDF

Info

Publication number
WO2005029319A1
WO2005029319A1 PCT/CN2004/000459 CN2004000459W WO2005029319A1 WO 2005029319 A1 WO2005029319 A1 WO 2005029319A1 CN 2004000459 W CN2004000459 W CN 2004000459W WO 2005029319 A1 WO2005029319 A1 WO 2005029319A1
Authority
WO
WIPO (PCT)
Prior art keywords
driver
built
peripheral device
computer
readable
Prior art date
Application number
PCT/CN2004/000459
Other languages
English (en)
French (fr)
Inventor
Xin Song
Zhongsheng Jin
Original Assignee
Lenovo (Beijing) Limited
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
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Publication of WO2005029319A1 publication Critical patent/WO2005029319A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • G06F9/4413—Plug-and-play [PnP]
    • G06F9/4415—Self describing peripheral devices

Definitions

  • Peripheral device with built-in driver management function and management method thereof has built-in driver management function and management method thereof
  • the invention relates to the application technology of a computer peripheral device driver, and more particularly to a peripheral device with a built-in driver management function and a management method thereof. Background of the invention
  • the patent application with the application number of 0110390.6 discloses a peripheral device with a built-in driver and a method for installing the same.
  • the peripheral device with the built-in driver and the installation method thereof can be used by a computer system to obtain its driver from the peripheral device without installing a CD or a disk. That is, the driver of the peripheral device is stored in the read-only memory of the peripheral device itself. During the installation of the peripheral device, the driver can be transferred from the peripheral device to the computer system, and the peripheral device can be driven without using a CD or a disk.
  • the peripheral devices of the computer system mentioned here also refer to the peripheral devices of the computer.
  • there are many types of peripheral devices of the computer such as printers, optical drives, scanners, digital cameras, high-capacity disk drives, and keyboards and mice , Operating devices, etc.
  • the peripheral device with a built-in driver disclosed in this patent application stores the driver in a read-only memory, that is, the driver of the peripheral device is fixedly stored in the read-only memory at the factory. If the driver or computer operating system is upgraded, the built-in driver data package may be invalidated, making the new driver or computer operating system incompatible with the peripheral device. Summary of the invention
  • the main object of the present invention is to provide a management system with a built-in driver.
  • a functional peripheral device which can avoid the failure of the built-in driver data pack due to the operating system and driver version upgrade, and has higher scalability and compatibility.
  • Another main object of the present invention is to provide a management method for a built-in driver, to avoid the problem of failure of the built-in driver data package due to the upgrade of the operating system and the driver version, and to improve the expandability and compatibility of peripheral devices of the built-in driver.
  • the present invention provides a peripheral device with a built-in driver management function, which at least includes: a main controller, a device function module, a program memory, a data register, and a computer interface.
  • the program memory is a readable and writable memory; and the readable and writable memory further includes: a built-in driver storage module and a built-in driver management module;
  • the main controller is connected to the readable and writable memory, the data memory, and the computer interface respectively; the main controller receives commands, data, or built-in driver content sent by the computer through the computer interface, and temporarily stores the data in the data memory according to
  • the received command stores the content of the built-in driver temporarily stored in the data storage through the built-in driver management module in the readable and writable storage, and stores it in the built-in driver storage module; or according to the received command, through the built-in driver management module, Read the content of the built-in driver from the built-in driver storage module and send it to the computer through the computer interface; or according to the received command, the built-in driver management module deletes the built-in driver stored in the built-in driver storage module; or the received data Send to the equipment function module to realize the equipment function.
  • the readable and writable memory can be a flash memory.
  • the computer interface may include a standard parallel communication interface circuit; the parallel communication interface circuit is connected to the main controller; the main controller receives commands, data and built-in driver content sent by the computer through the parallel communication interface circuit; or according to the received The command passes the built-in driver management module to read the content of the built-in driver from the built-in driver storage module and sends it to the computer through the parallel communication interface circuit.
  • the computer interface may further include a serial communication interface circuit; the serial communication interface circuit is connected to the main controller; the main controller receives commands, data, and built-in driver content sent by the computer through the serial communication interface circuit; or The received command reads the content of the built-in driver from the built-in driver storage module through the built-in driver management module and sends it to the computer through the serial communication interface circuit.
  • the serial communication interface circuit may be a USB interface circuit.
  • the peripheral device may further include a network interface circuit, which is connected to the main controller; the main controller receives commands, data, and built-in driver content sent by the network through the network interface circuit; or passes the built-in driver according to the received command
  • the management module reads the content of the built-in driver from the built-in driver storage module and sends it to the network through the network interface circuit.
  • the network interface circuit may include an Ethernet transceiver and a network interface connector; the network interface connector is connected to a network, and the Ethernet transceiver is connected to a main controller.
  • the present invention provides a method for managing a built-in driver, which includes the following steps:
  • the peripheral device After receiving the operation command, the peripheral device performs management operations on the built-in driver stored in the readable and writable memory of the peripheral device according to the operation command.
  • the readable and writable memory may be a flash memory FlashROM.
  • the driver management operation command may be: a driver download command, a driver upload command, or a driver delete command.
  • the step 3) may include the following steps:
  • the peripheral device judges the type of the operation command, and if it is a driver upload command, then execute step 32); if it is a driver download command, then execute step 33); if it is a driver Program delete command, then step 34);
  • Step 32) Receive the content of the built-in driver sent by the computer, upload the content of the built-in driver to the data storage of the peripheral device, and then write the content to the readable and writable storage; end the process;
  • Step 33 Search for a matching driver in the readable and writable memory according to the driver download command, and if there is a matching driver, download the driver content to the computer; end the process; otherwise, return a download failure message to the computer End the process;
  • Step 34 According to the driver deletion command, search for a matching driver in the readable and writable memory, and if there is a matching driver, delete the driver content; end the process; otherwise, return a deletion failure message to the computer; end Process.
  • the method may further include: before receiving the driver management operation command, the peripheral device waits to receive data, and when information is input, firstly determining whether the information is a driver management operation command; if it is an operation command, performing step 31), otherwise according to the peripheral
  • the functions of the device perform subsequent processing.
  • the method may further include: establishing a driver list in the computer, recording versions of all drivers stored in the readable and writable memory of the peripheral device, and the driver list after the driver upload, download, or delete operation of the peripheral device Refreshed by computer.
  • the method may further include: after receiving the driver upload command, the peripheral device checks whether the readable and writable memory has sufficient space, and if so, uploads the driver to the data storage of the peripheral device first, and then writes the driver to the readable and writable memory. Write to the memory; otherwise, return the upload failure message to the computer.
  • the method may further include: the peripheral device performs data verification on the driver uploaded to the data storage, and if the verification is successful, writes the driver to the readable and writable storage; otherwise, returns verification failure information to the computer;
  • the method can be: use the accumulation and summation algorithm for verification.
  • the step 1) may be: storing the built-in driver in a readable and writable memory in order from front to back in a writing order.
  • the step 34) may further include: determining whether the deleted driver is at the end of the readable and writable memory, and if so, ending the process; otherwise, moving the driver stored behind the deleted driver forward.
  • the peripheral computer interface may be a standard parallel communication interface or / and a USB interface.
  • the computer sends a driver management operation command to the peripheral device through the line communication interface or / and the USB interface.
  • the axe is performed through the parallel communication interface or / and the USB interface.
  • the method may further include: setting a network interface on the peripheral device, the network interface connecting the peripheral device to the network; the computer sending a driver management operation command to the peripheral device through the network, and the peripheral device on the network through the network Upload and download drivers.
  • the peripheral device and management method with built-in driver management function of the present invention store the driver in a readable and writable memory in the peripheral device, and in the peripheral device A built-in driver management module is set up, and a management operation such as uploading, downloading, and deleting a built-in driver in a peripheral device is performed through cooperation between the computer and the management module.
  • the invention enables the peripheral devices with built-in driver programs to avoid the failure of the built-in driver data package due to the operating system and the driver version medium level, and has higher extensibility and compatibility.
  • FIG. 1 is a schematic structural diagram of a built-in driver peripheral device according to a preferred embodiment of the present invention
  • FIG. 2 is a processing flowchart of the embodiment shown in FIG. 1 in a computer
  • FIG. 3 is a processing flowchart in a built-in driver peripheral device of the embodiment shown in FIG. 1.
  • FIG. 4 is a schematic diagram of a data storage structure in a readable and writable memory of the embodiment shown in FIG. 1. Mode of Carrying Out the Invention
  • the peripheral device with a built-in driver management function of the present invention and a management method thereof store the driver in a readable and writable memory in the peripheral device, and set a built-in driver management module in the peripheral device.
  • the management module cooperates with each other to perform management operations such as uploading, downloading, and deleting the built-in driver in the peripheral device.
  • FIG. 1 is a schematic structural diagram of a built-in driver peripheral device according to a preferred embodiment of the present invention.
  • This embodiment is a printer with a built-in driver.
  • the printer includes: a main controller 107; a program memory 103; in this embodiment, the program memory 103 is a Flash ROM or other readable and writable memory; a data memory (SDRAM) 108; computer interface 109 and printing module 114.
  • SDRAM data memory
  • the readable and writable memory 103 includes, in addition to the firmware program module 104 for storing a printer firmware program, a built-in driver storage module 106 and a built-in driver management module 105.
  • the main controller 107 is respectively connected to the readable and writable memory 103, the data storage 108, and the computer interface 109.
  • the main controller 107 receives the command, data or built-in driver content sent by the computer through the computer interface 109, and temporarily stores the data in the data storage 108 According to the received command, the built-in driver content temporarily stored in the data storage 108 is stored in the built-in driver storage module 106 through the built-in driver management module 105 in the readable and writable stealer 103; or according to the received Command through built-in driver management module
  • the built-in driver management module 105 Read the content of the built-in driver from the built-in driver storage module 106 and send it to the computer through the computer interface 107. Or, according to the received command, the built-in driver management module 105 deletes the built-in driver stored in the built-in driver storage module 106. A program; if the print data is received, the main controller 107 controls the print module 114 to print.
  • the computer interface 109 of this embodiment includes a standard parallel communication interface circuit composed of an interconnected IEEE 1284 transceiver 110 and a parallel port connector 111, and a USB composed of an interconnected USB node controller 112 and a USB interface connector 113. Interface Circuit.
  • the IEEE 1284 transceiver 110 and the USB node controller 112 are connected to the main controller 107 respectively; the main controller 107 receives the computer through the IEEE 1284 transceiver 110 and the parallel port connector 111; or receives the computer through the USB node controller 112 and the USB interface connector 113 Sent commands, data, and built-in driver content; or via built-in driver management module based on received commands
  • the built-in driver storage module 106 Read the content of the built-in driver from the built-in driver storage module 106 and send it to the computer through the IEEE 1284 transceiver 110 and the parallel port connector 111; or through the USB node controller 112 and the USB interface connector 113.
  • the printer of this embodiment further includes a network interface circuit composed of a network interface connector 101 and an Ethernet transceiver 102.
  • the network interface connector 101 is connected to the Ethernet transceiver 102, and the Ethernet transceiver
  • the controller 102 is connected to the main controller 107; the main controller 107 receives commands, print data, and built-in driver content sent by the network through the Ethernet transceiver 102 and the network interface connector 101; or is managed by the built-in driver according to the received command
  • the module 105 reads the content of the built-in driver from the built-in driver storage module 106 and sends the content to the network through the Ethernet device 102 and the network interface connector 101.
  • FIG. 2 is a flowchart of processing in the computer in the embodiment shown in FIG. 1.
  • the stream The process includes the following steps:
  • Step 201 A communication port is selected. Since the printer of this embodiment has a parallel port, a USB interface, and a network interface, a communication port must be selected first.
  • Step 202 Search for a built-in printer driver on the selected communication port. If the built-in printer driver is successfully found, go to step 203; otherwise, the process ends.
  • Step 203 Select a printer connected to the communication port.
  • Step 204 Determine the task type. If the printer is configured, perform step 205: directly configure the printer. If the built-in driver is managed, perform step 206.
  • Step 206 Determine the operation type of the built-in driver of the printer. If the driver is downloaded, go to step 207; if the driver is uploaded or deleted, go to step 213.
  • Step 207 Obtain a computer (PC) operating system version
  • Step 208 Send a driver download command to the printer according to the PC operating system version, which includes a version requirement for the driver.
  • Step 209 Receive the response information from the printer. If the response information includes a version match, perform steps 210-212; otherwise, the versions do not match, and the process ends.
  • Steps 210-212 the PC receives the version of the driver downloaded by the printer, and accumulates and verifies the downloaded driver, or it can be verified by other methods. If the verification is successful, the PC automatically installs the downloaded program. Bundle process; otherwise direct process.
  • Step 213 The PC calls up a pre-established driver list, and the driver list records the versions of all the drivers stored in the readable and writable memory of the peripheral device.
  • Step 214 Determine the type of drive management. If it is uploading, go to step 215; if it is deleting, go to steps 220-222.
  • Step 215 Send the file header of the driver data packet to the printer, which includes the size of the driver data packet.
  • Step 216 Receive a response message from the printer. If the response message indicates Flash ROM If there is enough space, go to steps 217-219; otherwise, if the Flash ROM has insufficient space, end the process.
  • Steps 217-219 sending the data part of the driver data packet and the check word to the printer, receiving the response information of the printer, and if the response information indicates that the verification is successful, then adding the driver version to the driver list, Refresh the driver list to end the process; otherwise, if the verification fails, the process ends.
  • Steps 220-222 Send a deletion confirmation message to the printer, which contains the version number of the driver to be deleted, and receive a response from the printer. If the response message indicates that the deletion was successful, delete the driver version from the driver list Refresh the driver list to end the process; otherwise, the deletion fails and the process is directly ended.
  • FIG. 3 is a processing flowchart of a built-in driver peripheral device according to the embodiment shown in FIG. The process includes the following steps:
  • Step 301 The printer waits for data. After the driver built-in printer is powered on, it is always in the waiting, receiving, and processing cycle.
  • step 302 data is entered into the printer.
  • Step 303 Determine the type of data. If it is print data, execute step 304: execute a print job; if it is a driver management operation command, execute step 305.
  • Step 305 determine the type of driver operation, if the driver is downloaded to the computer, perform steps 306-308; if the driver is deleted, perform step 309; if the driver is uploaded, perform step 314;
  • Steps 306-308 According to the version requirements of the driver download command, search for a matching driver in the readable and writable memory to determine whether there is a suitable driver. If there is a matching driver, download the driver content to PC, end the process; otherwise, return the download failure message to the PC; end the process.
  • Step 309 > According to the driver delete command, search for a match in the readable and writable memory Drivers.
  • Step 310 Determine whether there is a matching driver. If there is a matching driver, perform steps 311-3 13; otherwise, return a deletion failure message to the PC; end the process.
  • Steps 311-313 delete the matching driver content, determine whether the deleted driver is at the end of the readable and writable memory, and if so, end the process; otherwise, move the driver stored after the deleted driver forward End the process after moving.
  • FIG. 4 is a schematic diagram of the data storage structure in the readable and writable memory of the embodiment shown in FIG.
  • the printer's firmware (firmware) is stored at the front of the Flash ROM
  • the built-in driver is stored in the readable and writable memory in order from the front to the back.
  • Each printer driver package consists of two parts: a file header (Header File), and a driver data compression package (Zip File).
  • the header file is 128 bytes in size and is not compressed. It contains important information about the Zip File and printer characteristics, such as the operating system, language version, driver version, and Zip File size. , Zip File decompressed original file size, printer model, printer resolution, print speed, print paper size, etc.
  • Step 314 The printer obtains the size of the uploaded driver from the driver upload command.
  • Step 315 Check whether there is enough space in the readable and writable memory. If there is, perform steps 316-318; otherwise, return the upload failure information to the PC and end the process.
  • Steps 316-318 the printer first uploads the driver to the data storage of the peripheral device, and then verifies the uploaded horse program. If the verification is successful, the driver writes the driver to the readable and writable storage to end the process. ; Otherwise, the school inspection is unsuccessful, and the process is directly ended.
  • the computer verifies the downloaded driver, and the printer verifies the uploaded driver.
  • This embodiment is a printer with a built-in driver, and other peripheral devices such as optical transceivers, Scanners, digital cameras, high-capacity disk drives, keyboards, mice, joysticks, and other operations are installed in peripheral devices and a built-in driver management module is set up.
  • the built-in driver programs in peripheral devices are Management operations such as uploading, downloading, and deleting are different from this embodiment in that the device function modules and interfaces may be different.
  • the built-in driver can be conveniently updated. For example, the old version of the driver in the readable and writable memory is deleted first, and then the new version of the driver is uploaded to the readable and writable memory by the computer. Of course, if the readable and writable memory space is large enough, it can also be uploaded first and then deleted.
  • the peripheral device with a built-in driver management function and a management method of the present invention can perform management operations such as uploading, downloading, and deleting the built-in driver in the peripheral device, so that the peripheral of the built-in driver
  • the device can avoid the failure of the built-in driver data package caused by the upgrade of the operating system and the driver version, and has high scalability and compatibility.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Description

具有内置驱动程序管理功能的外围设备及其管理方法 技术领域
本发明涉及计算机外围设备驱动程序的应用技术， 特别涉及一种具 有内置驱动程序管理功能的外围设备及其管理方法。 发明背景
随着计算机技术的迅速发展， 出现了内置驱动程序的计算机外围设 备。 申请号为 0110390.6的专利申请就公开了一种内建驱动程序的周边 装置及其安装方法。 该内建驱动程序的周边装置及其安装方法可供电脑 系统从周边装置上取得其驱动程序， 不需使用光盘或是磁盘来安装， 即 将周边装置的驱动程序存储在安装周边自身的只读存储器中 , 当安装周 边装置时， 可从周边装置上将驱动程序传送至电脑系统， 而不需使用光 盘或是磁盘即可驱动周边装置。 这里所述的电脑系统的周边装置也就是 指计算机的外围设备， 一般来说， 计算机的外围设备种类相当多， 例如 打印机、 光碟机、 扫描仪、 数码相机、 高容量磁盘机、 以及键盘、 鼠标、 操作杆等操作装置等等。
该专利申请公开的内建驱动程序的外围设备， 将驱动程序存储在只 读存储器中， 也就是说外围设备的驱动程序在出厂是已固定存储在只读 存储器中。 如果驱动程序或计算机操作系统升级， 就可能导致内置驱动 数据包失效， 使新的驱动程序或计算机操作系统无法兼容该外围设备。 发明内容
有鉴于此， 本发明的主要目的在于提供一种具有内置驱动程序管理 功能的外围设备， 该外围设备能够避免因操作系统和驱动版本升级而导 致内置驱动数椐包失效的问题， 而且具有较高的扩展性和兼容性。
本发明的另一个主要目的在于提供一种内置驱动程序的管理方法， 避免因操作系统和驱动版本升级而导致内置驱动数据包失效的问题， 提 高内置驱动程序外围设备扩展性和兼容性。
为达到上 目的的一个方面， 本发明提供了一种具有内置驱动程序 管理功能的外围设备， 其至少包含： 主控制器、 设备功能模块、 程序存 储器、 数据存條器和计算机接口，
所述的程序存储器为可读可写存储器； 且该可读可写存储器进一步 包含： 内置驱动程序存储模块和内置驱动程序管理模块；
所述的主控制器与该可读可写存储器、 数据存储器和计算机接口分 别相连； 主控制器通过计算机接口接收计算机发送的命令、 数据或内置 驱动程序内容， 并暂存到数据存储器中， 根据接收的命令， 将数据存储 器中暂存的内置驱动程序内容经过可读可写存储器中的内置驱动程序 管理模块， 存储到内置驱动程序存储模块； 或根据接收的命令， 经过内 置驱动程序管理模块， 从内置驱动程序存储模块中读取内置驱动程序内 容通过计算机接口发送给计算机； 或根据接收的命令， 由内置驱动程序 管理模块删除内置驱动程序存储模块中存储的内置驱动程序； 或将接收 的数据发送给设备功能模块实现设备功能。
其中， 所达的可读可写存储器可以为闪存 Flash ROM。
所述的计算机接口可以包含标准并行通信接口电路； 该并行通信接 口电路与主控制器相连； 主控制器通过并行通信接口电路接收计算机发 送的命令、 数椐和内置驱动程序内容； 或根据接收的命令， 经过内置驱 动程序管理模块， 从内置驱动程序存储模块中读取内置驱动程序内容通 过并行通信接口电路发送给计算机。 所述的计算机接口还可以包含串行通信接口电路； 该串行通信接口 电路与主控制器相连； 主控制器通过串行通信接口电路接收计算机发送 的命令、 数据和内置驱动程序内容； 或根据接收的命令， 经过内置驱动 程序管理模块， 从内置驱动程序存储模块中读取内置驱动程序内容通过 串行通信接口电路发送给计算机。
所述的串行通信接口电路可以为 USB接口电路。
该外围设备可以进一步包含网络接口电路， 该网络接口电路与主控 制器相连； 主控制器通过网络接口电路接收网络发送的命令、 数据和内 置驱动程序内容； 或根据接收的命令， 经过内置驱动程序管理模块， 从 内置驱动程序存储模块中读取内置驱动程序内容通过网络接口电路发 送给网络。
所述的网络接口电路可以包含以太网收发器和网络接口连接器； 该 网络接口连接器与网络相连， 该以太网收发器与主控制器相连。
为达到上述目的的另一个方面， 本发明提供了一种内置驱动程序的 管理方法， 该方法包括以下步骤：
1 )将内置驱动程序存储在外围设备的可读可写存储器中；
2 )计算机向外围设备发逸驱动程序管理操作命令；
3 )外围设备收到操作命令后，根据操作命令对存储在外围设备的可 读可写存储器中的内置驱动程序进行管理操作。
其中， 所述的可读可写存储器可以为闪存 FlashROM。
所述的驱动程序管理操作命令可以为： 驱动程序下载命令、 驱动程 序上载命令或驱动程序删除命今。
所述的步骤 3 ) 可以包括以下步骤：
31 )外围设备判断操作命令类型， 如果是驱动程序上载命令， 则执 行步骤 32 ); 如果是驱动程序下载命令， 则执行步骤 33 ); 如果是驱动 程序删除命令， 则執行步骤 34 );
步骤 32 )接收计算机发送的内置驱动程序内容， 先将该内置驱动程 序内容上载到外围设备的数据存储器， 然后写入到可读可写存储器中； 结束流程；
步骤 33 )根据驱动程序下载命令， 在可读可写存储器中搜索匹配的 驱动程序，如果有匹配的驱动程序，则将该驱动程序内容下载到计算机; 结束流程； 否则， 向计算机返回下载失败信息； 结束流程；
步骤 34 )根据驱动程序删除命令， 在可读可写存储器中搜索匹配的 驱动程序， 如果有匹配的驱动程序， 则将该驱动程序内容删除； 结束流 程； 否则， 向计算机返回删除失败信息； 结束流程。
该方法可以进一步包括： 外围设备接收驱动程序管理操作命令前， 等待接收数据， 当有信息输入时先判断该信息是否为驱动程序管理操作 命令； 如果是操作命令则执行步骤 31 ), 否则按照外围设备本身的功能 进行后续的处理。
该方法可以进一步包括: 在计算机中建立驱动程序列表, 记录该外 围设备的可读可写存储器中存储的所有驱动程序的版本， 该驱动程序列 表在外围设备的驱动程序上载、 下载或删除操作后由计算机刷新。
该方法可以进一步包括: 外围设备收到驱动程序上载命令后 , 检查 可读可写存储器是否有足够的空间， 如果有则将驱动程序先上载到外围 设备的数据存储器， 然后写入到可读可写存储器中； 否则， 向计算机返 '回上载失败信息。
该方法可以进一步包括： 外围设备对上载到数据存储器中的驱动程 序进行数据校验， 如果校验成功则将驱动程序写入到可读可写存储器； 否则向计算机返回校验失败信息；
驱动程序下载到计算机后， 计算机对对该驱动程序进行数据校验， 如果校验成功则直接安装该驱动程序； 否则向外围设备返回校验失败信 所述的校验: ^法可以为： 使用累加和算法进行校验。
所述步骤 1 ) 可以为： 将内置驱动程序按照写入顺序从前向后依次 存储到可读可写存储器中。
所述步骤 34 ) 可以进一步包括： 判断被删除的驱动程序是否在可读 可写存储器的末尾， 如果是则结束流程； 否则， 将存储在被删除的驱动 程序后的驱动程序向前移动。
所述外围设 的计算机接口可以为标准并行通信接口或 /和 USB接 口， 计算机通过 行通信接口或 /和 USB接口向外围设备发送驱动程序 管理操作命令， 斧通过并行通信接口或 /和 USB接口进行驱动程序的上 载和下载。
该方法可以进一步包括： 在所述的外围设备上设置网络接口， 该网 络接口将外围设备连接到网络上； 计算机通过网络向外围设备发送驱动 程序管理操作命 ， 并通过网络对网络上的外围设备进行驱动程序的上 载和下载。
由本发明的拔术方案可见， 本发明的这种具有内置驱动程序管理功 能的外围设备及^管理方法， 将驱动程序存储在外围设备中可读可写的 存储器中， 并在夕卜围设备中设置内置驱动程序管理模块， 通过计算机与 该管理模块的互相配合， 对外围设备中内置驱动程序进行上载、 下载、 删除等管理操作。 本发明使得内置驱动程序的外围设备能够避免因操作 系统和驱动版本介级而导致内置驱动数据包失效的问题， 而且具有较高 的扩展性和兼容性。 附图简要说明
图 1为本发明一个较佳实施例的内置驱动程序外围设备的结构示意 图；
图 2为图 1所示实施例在计算机中的处理流程图；
图 3为图 1所示实施例的内置驱动程序外围设备中的处理流程图； 图 4为图 1所示实施例的可读可写的存储器中数据存储的结构示意 图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚明白， 下面结合实施 例和附图， 对本发明进一步详细说明。
本发明的这种具有内置驱动程序管理功能的外围设备及其管理方 法， 将驱动程序存储在外围设备中可读可写的存储器中， 并在外围设备 中设置内置驱动程序管理模块， 通过计算机与该管理模块的互相配合 , 对外围设备中内置驱动程序进行上载、 下载、 删除等管理操作。
参见图 1 , 图 1为本发明一个较佳实施例的内置驱动程序外围设备 的结构示意图。本实施例是一种驱动程序内置的打印机，该打印机包括： 主控制器 107; 程序存储器 103 , 本实施例中程序存储器 103 为 Flash ROM, 也可是其他可读可写存储器； 数据存储器（SDRAM ) 108； 计算 机接口 109和打印模块 114。
其中， 可读可写存储器 103除了包含用于存储打印机固件程序的固 件程序模块 104， 还包含： 内置驱动程序存储模块 106和内置驱动程序 管理模块 105。 主控制器 107与可读可写存储器 103、 数据存储器 108 和计算机接口 109分別相连； 主控制器 107通过计算机接口 109接收计 算机发送的命令、 数据或内置驱动程序内容， 并暂存到数据存储器 108 中， 根据接收的命令， 将数据存储器 108中暂存的内置驱动程序内容经 过可读可写存偷器 103中的内置驱动程序管理模块 105, 存储到内置驱 动程序存储模块 106; 或根据接收的命令， 经过内置驱动程序管理模块
105, 从内置驱动程序存储模块 106 中读取内置驱动程序内容通过计算 机接口 107发逸给计算机； 或根据接收的命令， 由内置驱动程序管理模 块 105删除内置驱动程序存储模块 106中存储的内置驱动程序； 如果接 收的是打印数椐， 则由主控制器 107控制打印模块 114进行打印。
本实施例的计算机接口 109包含了由互相连接的 IEEE 1284收发器 110和并口连接器 111组成的标准并行通信接口电路， 以及由互相连接 的 USB 节点控制器 112和 USB接口连接器 113组成的 USB接口电路。 IEEE 1284收发器 110和 USB 节点控制器 112分别与主控制器 107相连； 主控制器 107通过 IEEE 1284收发器 110和并口连接器 111;或通过 USB 节点控制器 112和 USB接口连接器 113接收计算机发送的命令、数据和 内置驱动程序内容； 或根据接收的命令， 经过内置驱动程序管理模块
106, 从内置驱动程序存储模块 106中读取内置驱动程序内容通过 IEEE 1284收发器 110和并口连接器 111;或通过 USB 节点控制器 112和 USB 接口连接器 113发送给计算机。
如图 1所示， 本实施例的打印机还包含了由网絡接口连接器 101和 以太网收发器 102组成的网络接口电路， 该网络接口连接器 101和以太 网收发器 102相连， 该以太网收发器 102与主控制器 107相连； 主控制 器 107通过以太网收发器 102和网络接口连接器 101接收网絡发送的命 令、 打印数据和内置驱动程序内容； 或根据接收的命令， 经过内置驱动 程序管理模块 105 , 从内置驱动程序存储模块 106中读取内置驱动程序 内容通过以太网^:发器 102和网络接口连接器 101发送给网络。
参见图 2, 图 2为图 1所示实施例在计算机中的处理流程图。 该流 程包括以下步骤：
步骤 201 , 选择通信端口， 由于本实施例的打印机有并口、 USB接 口和网络接口 , 所以要先选择通信端口。
步骤 202, 在选择的通信端口上搜索是否有驱动内置打印机， 如果 成功搜索到驱动内置打印机， 则执行步骤 203; 否则结束流程。
步骤 203 , 选择该通信端口上连接的打印机。
步骤 204, 判断任务类型， 如果是配置打印机则执行步骤 205: 直接 对打印机进行配置， 如杲是对内置驱动程序进行管理， 则执行步骤 206。
步骤 206, 判断对打印机内置驱动程序的操作类型， 如果是驱动程 序下载，则执行步骤 207;如果是驱动程序上载或删除，则执行步骤 213。
步骤 207, 获取计算机（PC )操作系统版本；
步骤 208， 根据 PC操作系统版本， 向打印机发送驱动下载命令， 其 中包含对驱动程序的版^要求。
步骤 209, 接收打印机的应答信息， 如果应答信息中包含版本匹配， 则执行步驟 210 - 212; 否则版本不匹配， 则结束流程。
步骤 210 - 212, PC 接收打印机下载的该版本驱动程序， 并对下载 的驱动程序进行累加和校验， 也可以用其他方法进行校验， 如果校验成 功则 PC自动安装下载的¾动程序后束流程； 否则直接流程。
步骤 213, PC调出预先建立的驱动程序列表， 该驱动程序列表记录 该外围设备的可读可写存储器中存储的所有驱动程序的版本。
步驟 214， 判断驱动管理类型， 如果是上载则执行步驟 215; 如果是 删除则执行步骤 220 - 222。
步骤 215, 向打印机发送驱动程序数据包的文件头， 其中包含驱动 程序数据包的大小。
步骤 216，接收打印机的应答信息，如果应答信息中表明 Flash ROM 空间足够， 则执行步驟 217 - 219; 否则 Flash ROM空间不足， 则结束流 程。
步骤 217 - 219, 向打印机发送驱动程序数据包的数据部分和校验 字， 接收打印机的应答信息， 如果应答信息中表明校验成功， 则将该驱 动程序的版本镇入到驱动程序列表中， 刷新驱动程序列表， 结束流程； 否则校验失败， 则结束流程。
步骤 220 - 222, 向打印机发送删除确认信息， 其中包含要删除的驱 动程序的版本号， 接收打印机的应答信息， 如果应答信息中表明删除成 功，则将该驱动程序的版本从驱动程序列表中删除,刷新驱动程序列表， 结束流程； 否则删除失败， 直接结束流程。
参见图 3 , 图 3为图 1所示实施例的内置驱动程序外围设备中的处 理流程图。 该 程包括以下步骤：
步骤 301， 打印机等待数据。 驱动内置打印机上电运行后， 一直处 于等待、 接收、 处理的循环之中。
步骤 302, 有数据输入打印机。
步骤 303 , 判断数据类型， 如果是打印数据， 则执行步骤 304: 执行 打印作业； 如果是驱动程序管理操作命令， 则执行步驟 305。
步骤 305 , 判断驱动程序操作类型， 如果是驱动程序下载到计算机， 则执行步骤 306 - 308; 如果是驱动程序删除， 则执行步骤 309; 如果是 驱动程序上载， 则执行步骤 314;
步驟 306 - 308 , 根据驱动程序下载命令的版本要求， 在可读可写存 储器中搜索匹配的驱动程序， 判断是否有合适的驱动程序， 如果有匹配 的驱动程序， 则将该驱动程序内容下载到 PC, 结束流程； 否则， 向 PC 返回下载失败信息； 结束流程。
步骤 309, >据驱动程序删除命令， 在可读可写存储器中搜索匹配 的驱动程序。
步骤 310, 判断是否有匹配的驱动程序， 如果有匹配的驱动程序， 则执行步骤 311 - 3 13; 否则， 向 PC返回删除失败信息； 结束流程。
步骤 311 - 313 , 将匹配驱动程序内容删除， 判断被删除的驱动程序 是否在可读可写存储器的末尾， 如果是则结束流程； 否则， 将存储在被 删除的驱动程序后的驱动程序向前移动后结束流程。
驱动程序在 Flash ROM中的存储结构参见图 4, 图 4为图 1所示实 施例的可读可写的存储器中数据存储的结构示意图。 其中， 打印机的固 件程序 （firmware ) 存储在 Flash ROM的最前面， 内置驱动程序按照写 入顺序从前向后依次存储在可读可写存储器中。 每一打印机驱动包都由 两部分组成： 文件头（Header File ), 驱动数据压缩包（ Zip File )。 Header File大小为 128字节， 均未经压缩处理， 其中包含了紧随其后 Zip File 的重要信息以及打印机的特征信息， 如该驱动适合的操作系统、 语言版 本、 驱动版本、 Zip File的大小、 Zip File解压缩后的原始文件大小、 打 印机型号、 打印机分辨率、 打印速度、 打印纸张幅面等。
步骤 314，打印机从驱动程序上载命令中获得上载驱动程序的大小。 步骤 315, 检查可读可写存储器是否有足够的空间， 如果有则执行 步骤 316 - 318; 否则， 向 PC返回上载失败信息， 结束流程。
步骤 316 - 318 , 打印机将驱动程序先上载到外围设备的数据存储 器， 然后对上载的马区动程序进行校验， 如果校验成功则将该驱动程序写 入到可读可写存储器中结束流程； 否则校检不成功， 直接结束流程。
本实施例中， 计算机对下载的驱动程序进行校验， 且打印机对上载 的驱动程序进行校 3佥， 都采用了累加和的校验方法， 实现筒单有效， 在 实际应用中也可以采用其他方法进行校—检。
本实施例是一种驱动程序内置的打印机，其他的外围设备如光磔机、 扫描仪、 数码相机、 高容量磁盘机、 以及键盘、 鼠标、 操作杆等操作装 在外围设备中设置内置驱动程序管理模块， 通过计算机与该管理模块的 互相配合， 对外围设备中内置驱动程序进行上载、 下载、 删除等管理操 作， 与本实施例的区别在于设备功能模块和接口有可能有所不同。
本实施例可以 4艮方便的实现内置驱动程序的更新， 比如先将可读可 写的存储器中旧版本的驱动程序删除， 再由计算机将新版本的驱动程序 上载到可读可写的存储器中， 当然如果可读可写的存储器空间够大也可 以先上载后删除。
由上述的实施例可见， 本发明的这种具有内置驱动程序管理功能的 外围设备及其管理方法， 能够对外围设备中内置驱动程序进行上载、 下 载、 删除等管理操作， 使得内置驱动程序的外围设备能够避免因操作系 统和驱动版本升级而导致内置驱动数据包失效的问题， 而且具有较高的 扩展性和兼容性。

Claims

权利要求书
1、 一种具有内置驱动程序管理功能的外围设备， 其至少包含： 主 控制器、 设备功能模块、 程序存储器、 数据存储器和计算机接口， 其特 征在于：
所述的程序存储器为可读可写存储器； 且该可读可写存储器进一步 包含： 内置驱动程序存储模块和内置驱动程序管理模块；
所述的主控制器与该可读可写存储器、 数据存储器和计算机接口分 别相连； 主控制器通过计算机接口接收计算机发送的命令、 数据或内置 驱动程序内容， 并暂存到数据存储器中， >据接收的命令， 将数据存储 器中暂存的内置驱动程序内容经过可读可写存储器中的内置驱动程序 管理模块， 存储到内置驱动程序存储模块； 或根据接收的命令， 经过内 置驱动程序管理模块， 从内置驱动程序存储模块中读取内置驱动程序内 容通过计算机接口发送给计算机； 或根据接收的命令， 由内置驱动程序 管理模块删除内置驱动程序存储模块中存储的内置驱动程序； 或将接收 的数据发送给设备功能模块实现设备功能。
2、 如权利要求 1 所述的外围设备， 其特征在于： 所述的可读可写 存储器为闪存 Flash ROM。
3、 如权利要求 1 所述的外围设备， 其特征在于： 所述的计算机接 口包含标准并行通信接口电路； 该并行通信接口电路与主控制器相连； 主控制器通过并行通信接口电路接收计算机发送的命令、 数据和内置驱 动程序内容； 或根据接收的命令， 经过内置驱动程序管理模块， 从内置 驱动程序存储模块中读取内置驱动程序内容通过并行通信接口电路发 送给计箅机。
4、 如权利要求 1 所述的外围设备， 其特征在于： 所述的计算机接 口包含串行通信接口电路； 该串行通信接口电路与主控制器相连； 主控 制器通过串行通信接口电路接收计算机发送的命令、 数据和内置驱动程 序内容； 或冲艮据接收的命令， 经过内置驱动程序管理模块， 从内置驱动 程序存储模块中读取内置驱动程序内容通过串行通信接口电路发送给 计算机。
5、 如权利要求 1 所述的外围设备， 其特征在于： 所述的串行通信 接口电路为 USB接口电路。
6、 如权利要求 1 所述的外围设备， 其特征在于： 该外围设备进一 步包含网絡接口电路， 该网絡接口电路与主控制器相连； 主控制器通过 网络接口电路接收网络发送的命令、 数据和内置驱动程序内容； 或根据 接收的命令， 经过内置驱动程序管理模块， 从内置驱动程序存储模块中 读取内置驱动程序内容通过网络接口电路发送给网络。
7、 如杈利要求 6 所述的外围设备， 其特征在于： 所述的网络接口 电路包含以太网收发器和网络接口连接器； 该网络接口连接器与网络相 连， 该以太网收发器与主控制器相连。
8、 一种内置驱动程序的管理方法， 计算机外围设备的内置驱动程 序进行管理， 其特征在于， 该方法包括以下步骤：
1 )将内置驱动程序存储在外围设备的可读可写存储器中；
2 )计算机向外围设备发送驱动程序管理操作命令；
3 )外围设备收到操作命令后，根据操作命令对存储在外围设备的可 读可写存储器中的内置驱动程序进行管理操作。
9、 如权利要求 8 所述的管理方法， 其特征在于： 所述的可读可写 存储器为闪存 FlashROM。
10、 如权利要求 8所述的管理方法， 其特征在于： 所述的驱动程序 管理操作命令为： 驱动程序下载命令、 驱动程序上载命令或驱动程序删 除命令。
11、 如权利要求 10所述的管理方法， 其特征在于： 所述的步骤 3 ) 包括以下步骤：
31 ) 外围设备判断操作命令类型， 如果是驱动程序上载命令， 则执 行步骤 32 ); 如果是驱动程序下载命令， 则执行步骤 33 ); 如果是驱动 程序删除命令， 则执行步骤 34 );
步骤 32 )接收计算机发送的内置驱动程序内容， 先将该内置驱动程 序内容上载到外围设备的数据存储器， 然后写入到可读可写存储器中； 结束流程；
步骤 33 )根据驱动程序下载命令， 在可读可写存储器中搜索匹配的 驱动程序，如果有匹配的驱动程序，则将该驱动程序内容下载到计算机； 结束流程； 否则， 向计算机返回下载失败信息； 结束流程；
步骤 34 )根据驱动程序删除命令， 在可读可写存储器中搜索匹配的 驱动程序， 如果有匹配的驱动程序， 则将该驱动程序内容删除； 结束流 程； 否则， 向计算机返回删除失败信息； 结束流程。
12、 如权利要求 11所述的管理方法， 其特征在于， 该方法进一步包 括： 外围设备接收驱动程序管理操作命令前， 等待接收数据， 当有信息 输入时先判断该信息是否为驱动程序管理操作命令； 如果是操作命令则 执行步骤 31 ), 否则按照外围设备本身的功能进行后续的处理。
13、 如权利要求 11所述的管理方法， 其特征在于， 该方法进一步包 括： 在计算机中建立驱动程序列表， 记录该外围设备的可读可写存储器 中存储的所有驱动程序的版本， 该驱动程序列表在外围设备的驱动程序 上载、 下载或删除操作后由计算机刷新。
14、 如权利要求 11所述的管理方法， 其特征在于， 该方法进一步包 括： 外围设备收到驱动程序上载命令后， 检查可读可写存储器是否有足 够的空间， 如果有则将驱动程序先上载到外围设备的数据存储器， 然后 写入到可读可写存储器中； 否则， 向计算机返回上载失败信息。
15、 如权利要求 11或 14所述的管理方法， 其特征在于， 该方法进 一步包括： 外围设备对上载到数据存储器中的驱动程序进行数据校验， 如果校验成功则将驱动程序写入到可读可写存储器； 否则向计算机返回 校验失败信息；
驱动程序下载到计算机后， 计算机对对该驱动程序进行数据校驗， 如果校验成功则直接安装该驱动程序； 否则向外围设备返回校验失败信
16、 如权利要求 15所述的管理方法， 其特征在于， 所述的校验方法 为： 使用累加和算法进行校验。
17、 如权利要求 11所述的管理方法， 其特征在于， 所述步骤 1 )为： 将内置驱动程序按照写入顺序从前向后依次存储到可读可写存储器中。
18、 如权利要求 17所述的管理方法， 其特征在于， 所述步驟 34 ) 进一步包括： 判断被删除的驱动程序是否在可读可写存储器的末尾， 如 果是则结束流程； 否则， 将存储在被删除的驱动程序后的驱动程序向前 移动。
19、 如权利要求 8所述的管理方法， 其特征在于， 所述外围设备的 计算机接口为标准并行通信接口或 /和 USB接口， 计算机通过并行通信 接口或 /和 USB接口向外围设备发送驱动程序管理操作命令， 并通过并 行通信接口或 /和 USB接口进行驱动程序的上载和下载。
20、 如权利要求 8所述的管理方法， 其特征在于， 该方法进一步包 括： 在所述的外围设备上设置网络接口， 该网络接口将外围设备连接到 网絡上； 计算机通过网络向外围设备发送驱动程序管理操作命令， 并通 过网络对网络上的外围设备进行驱动程序的上载和下载。
PCT/CN2004/000459 2003-09-24 2004-05-09 Equipement peripherique et procede de gestion correspondant munis d'une fonction pour la gestion d'un programme de pilotes internes WO2005029319A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN03157566.8 2003-09-24
CNB031575668A CN1315067C (zh) 2003-09-24 2003-09-24 具有内置驱动程序管理功能的外围设备及其管理方法

Publications (1)

Publication Number Publication Date
WO2005029319A1 true WO2005029319A1 (fr) 2005-03-31

Family

ID=34324107

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000459 WO2005029319A1 (fr) 2003-09-24 2004-05-09 Equipement peripherique et procede de gestion correspondant munis d'une fonction pour la gestion d'un programme de pilotes internes

Country Status (2)

Country Link
CN (1) CN1315067C (zh)
WO (1) WO2005029319A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747087A (zh) * 2021-09-10 2021-12-03 湖南君瀚信息技术有限公司 远程驾驶低延时图像传输方法、装置、计算机设备及介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100524263C (zh) * 2005-03-31 2009-08-05 三菱电机株式会社 装置驱动模块
KR100694124B1 (ko) 2005-06-08 2007-03-12 삼성전자주식회사 화상형성장치의 드라이버 갱신 방법 및 장치
KR100651689B1 (ko) * 2005-11-29 2006-12-01 주식회사 애트랩 컨텐츠를 내장한 컴퓨터 주변기기와 이를 이용한 컨텐츠출력 방법
CN100465893C (zh) * 2006-08-29 2009-03-04 华南理工大学 一种嵌入式操作系统驱动程序动态升级方法
CN101382894B (zh) * 2007-09-05 2013-09-04 北京软通科技有限责任公司 下载计算机硬件设备驱动程序的方法、装置及系统
CN101227676B (zh) * 2008-02-03 2012-01-11 中兴通讯股份有限公司 一种智能终端版本软件的下载方法
CN101794234A (zh) * 2010-02-04 2010-08-04 中兴通讯股份有限公司 一种无线数据卡、无线数据卡与电脑侧的通信方法及系统
CN106383708B (zh) * 2016-09-13 2020-02-21 宇龙计算机通信科技(深圳)有限公司 模块加载方法及系统
CN110958411A (zh) * 2020-02-23 2020-04-03 武汉精立电子技术有限公司 一种基于fpga的图像采集控制方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5812857A (en) * 1996-08-28 1998-09-22 Extended Systems, Inc. Field configurable embedded computer system
US6009524A (en) * 1997-08-29 1999-12-28 Compact Computer Corp Method for the secure remote flashing of a BIOS memory
WO2001097025A1 (en) * 2000-06-16 2001-12-20 Silicom Ltd. Device-related software installation
US6370645B1 (en) * 1998-02-20 2002-04-09 Samsung Electronics Co., Ltd. Method of constructing a hard disk drive having uploadable/downloadable firmware

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5812857A (en) * 1996-08-28 1998-09-22 Extended Systems, Inc. Field configurable embedded computer system
US6009524A (en) * 1997-08-29 1999-12-28 Compact Computer Corp Method for the secure remote flashing of a BIOS memory
US6370645B1 (en) * 1998-02-20 2002-04-09 Samsung Electronics Co., Ltd. Method of constructing a hard disk drive having uploadable/downloadable firmware
WO2001097025A1 (en) * 2000-06-16 2001-12-20 Silicom Ltd. Device-related software installation

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113747087A (zh) * 2021-09-10 2021-12-03 湖南君瀚信息技术有限公司 远程驾驶低延时图像传输方法、装置、计算机设备及介质
CN113747087B (zh) * 2021-09-10 2023-09-19 湖南君瀚信息技术有限公司 远程驾驶低延时图像传输方法、装置、计算机设备及介质

Also Published As

Publication number Publication date
CN1315067C (zh) 2007-05-09
CN1601499A (zh) 2005-03-30

Similar Documents

Publication Publication Date Title
CN102750238B (zh) 存储器管理系统以及管理存储器的方法
US7876469B2 (en) Image forming apparatus and updating method
JP3666405B2 (ja) 画像形成装置、インストールプログラム、インストールプログラムを記録したコンピュータ読取可能な記録媒体およびインストール方法
KR101119320B1 (ko) 이동저장 장치의 펌웨어 업데이트 장치 및 방법
KR101959359B1 (ko) 빠른 부팅을 위한 부트 이미지를 업데이트하는 방법 및 이를 수행하는 화상형성장치
KR100774857B1 (ko) 통신단말의 소프트웨어 갱신 방법, 통신단말 및소프트웨어 갱신 시스템
JP2005508547A (ja) メモリカード上のファームウェアを更新するインシステムプログラムのインプリメンテーション
WO2005029319A1 (fr) Equipement peripherique et procede de gestion correspondant munis d'une fonction pour la gestion d'un programme de pilotes internes
US8051416B2 (en) Method for a user-specific configuration of a computer from a group of prepared computers
WO2014194865A1 (zh) 一种固件升级方法、装置及通信设备
JP2008139916A (ja) 情報処理装置、情報処理装置の制御方法、および情報処理装置の制御プログラム
KR20100096075A (ko) 로컬 플래시 메모리 및 원격 서버 하이브리드 연속 데이터 보호
JP4961288B2 (ja) 情報処理装置、情報処理プログラム、記録媒体、印刷装置及びネットワークシステム
WO2011116583A1 (zh) 一种实现对多协议通信组件管理的方法及装置
US20130067455A1 (en) Memory online update system and method
JP2018190376A (ja) 管理コントローラによるｓａｓ／ｓａｔａハードディスクドライブ更新
JP2001067228A (ja) ファームウェアダウンロード方式
US20040221024A1 (en) Apparatus and method for setting environment of client in client / server system, and program recording medium therefor
US7577766B2 (en) Method for controlling electronic apparatus, program for controlling electronic apparatus, electronic apparatus, and recording apparatus
KR100648817B1 (ko) 자동 펌웨어 업데이트 시스템 및 그 방법
US9141321B1 (en) Configurable printer server device
JPH113223A (ja) 情報処理装置及び情報格納方法
US7984236B2 (en) Data transfer
CN107908418B (zh) 光纤通道节点卡的逻辑程序升级方法及光纤通道总线设备
JP4048318B2 (ja) ソフトウェアの管理方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BW BY BZ CA CH CN CO CR CU CZ DK DM DZ EC EE EG ES FI GB GD GE GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MK MN MW MX MZ NA NI NO NZ PG PH PL PT RO RU SC SD SE SG SK SY TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SZ TZ UG ZM ZW AM AZ BY KG MD RU TJ TM AT BE BG CH CY DE DK EE ES FI FR GB GR HU IE IT MC NL PL PT RO SE SI SK TR BF CF CG CI CM GA GN GQ GW ML MR SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase