[go: up one dir, main page]

WO2005038663A1 - Procede permettant d'offrir des fonctions usb etendues via une communication ums standard - Google Patents

Procede permettant d'offrir des fonctions usb etendues via une communication ums standard Download PDF

Info

Publication number
WO2005038663A1
WO2005038663A1 PCT/KR2004/002689 KR2004002689W WO2005038663A1 WO 2005038663 A1 WO2005038663 A1 WO 2005038663A1 KR 2004002689 W KR2004002689 W KR 2004002689W WO 2005038663 A1 WO2005038663 A1 WO 2005038663A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
data
standard
font data
font
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.)
Ceased
Application number
PCT/KR2004/002689
Other languages
English (en)
Inventor
Ji-Woong Choi
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.)
Telechips Inc
Original Assignee
Telechips Inc
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 Telechips Inc filed Critical Telechips Inc
Publication of WO2005038663A1 publication Critical patent/WO2005038663A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/385—Information transfer, e.g. on bus using universal interface adapter for adaptation of a particular data processing system to different peripheral devices
    • 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
    • G06F2213/00—Indexing scheme relating to interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F2213/38—Universal adapter
    • G06F2213/3812—USB port controller

Definitions

  • the present invention relates to a method of providing the extended functions of a universal serial bus device using standard universal serial bus mass storage communication, which enables a variety of extended functions using non-standard communication as well as basic functions using standard UMS communication to be provided through a USB interface with a host system while allowing the universal serial bus device to be relatively simply constructed in such a way as to provide only a software stack for a standard universal serial bus mass storage communication protocol.
  • USB Universal Serial Bus
  • PC Personal Computer
  • UMS USB Mass storage
  • USB devices were designed to support the USB communication of the above-described standard UMS specification, the USB devices could be conveniently used through Windows application programs because the PC drivers that comply with the standard UMS specification were basically installed in the operating system.
  • the standard UMS specification provides only basic functions, such as reading a file, formatting a disk and writing a file, among a plurality of functions which are provided by an existing non-standard communication protocol, but does not provide special extended functions, such as changing the font of a USB device, upgrading the firmware of a USB device and performing a special Dynamic Recovery Mode (DRM) operation.
  • DRM Dynamic Recovery Mode
  • FIG. 1 shows the software protocol stacks of a conventional USB device 110 and a conventional host system 120.
  • the software protocol stacks shown in FIG. 1 are designed to support both the communication protocol of the standard UMS specification for the basic functions and the non-standard communication protocol for the extended functions, as described above. Consequently, the protocol stack of the USB device 110 is very complicated.
  • the parts of the protocol stack embedded in the USB device 110 are classified according to functionality as follows: a file system layer, an FAT layer and a non-UMS protocol layer are classified as parts for supporting the non-standard communication protocol, a UMS protocol layer is classified as a part for supporting the communication protocol of the standard UMS specification, and an FTL system layer and an FTL I/O layer are classified as parts for supporting a mass storage medium.
  • the parts of the protocol stack embedded in the host system 120 are classified according to functionality as follows: a Windows Ul, a USB protocol layer and a USB driver layer positioned on the left side are classified as parts for supporting the non-standard communication protocol, a Windows Ul, a file system layer, an FAT layer, a UMS protocol layer and a USB driver layer positioned on the right side are classified as parts for supporting the communication protocol of the standard UMS specification.
  • the software protocol stack based on the conventional USB communication method must be provided with both the non-standard communication protocol for the extended functions as well as the communication protocol in accordance with the standard UMS specification.
  • the File System Layer and the FAT Layer are extremely complicated, a considerably long developing time is required due to the task of constructing those layers in the USB device 110 and the operating speed of the USB device 110 is significantly slowed.
  • an object of the present invention is to provide a method of providing the extended functions of a USB device using standard UMS communication, which enables a variety of extended functions using non-standard communication as well as basic functions using standard UMS communication to be supported through a USB interface with a host system while providing only a software stack for a standard UMS communication protocol, thus allowing the universal serial bus device to be relatively simply constructed.
  • FIG. 1 is a diagram showing software protocol stacks according to a conventional USB communication method
  • FIG. 2 is a diagram showing software protocol stacks according to a method of providing the extended functions of a USB device in accordance with the present invention
  • FIG. 3 shows field formats of a command packet and an ACK packet according to a standard UMS specification
  • FIG. 4 is a flowchart illustrating a common UMS process flow, which is used in the method of providing the extended functions of the USB device according to the present invention
  • FIG. 5 is a diagram showing a method of changing the font of a USB device using the method of providing the extended functions of the USB device according to the present invention
  • FIG. 6 is a diagram showing a method of upgrading the firmware of a USB device using the method of providing the extended functions of the USB device according to the present invention.
  • FIG. 2 is a diagram showing the software protocol stacks of a USB device 210 and a host system 220 in accordance with a method of providing the extended functions of the USB device in accordance with the present invention.
  • a UMS protocol layer is provided to support the communication protocol of a standard UMS specification
  • an FTL system layer and an FTL I/O layer are provided to support a mass storage medium, but a communication protocol layer for supporting a non-standard communication protocol is not provided to the USB device 210 of FIG. 2.
  • a Windows Ul, a file system layer, an FAT layer, a UMS protocol layer and a USB driver layer positioned on the right side are provided to support the communication protocol of the standard UMS specification
  • a Windows Ul, a file system layer, an FAT layer, a USB protocol layer and a USB driver layer positioned on the left side are provided to support the non-standard communication protocol.
  • the host system 220 that supports an extendible USB communication method is provided with full software protocol stacks for the communication protocol of the standard UMS specification and the non-standard communication protocol.
  • the USB communication-related programs installed in the USB device 210 are considerably simplified because it is sufficient for the programs to support only the standard UMS protocol, whereas the USB communication- related programs installed in the host system 220 are considerably complicated because the full software protocol stacks for the communication protocol of the standard UMS specification and the non-standard communication protocol, particularly the file system layer and the FAT layer corresponding to the non-standard communication protocol, must be provided as described above.
  • FIG. 3 is a diagram showing the field formats of a command packet and an ACK packet 310, 320 and 330 in accordance with the standard UMS specification.
  • the field format of a CBW command packet 310 and the field format of a CSW packet 330 are disclosed in the UMS-related specification of the USB Forum, "Universal Serial Bus Mass Storage Class-Bulk Only Transport, Revision 1.0, September 31, 1999, pp. 13-15.”
  • the field format of a CBW command block 320 is disclosed in the UMS-related specification of the USB Forum, "Universal Serial Bus Mass Storage Class-UFI Command Specification, Revision 1.0, December 14, 1998, pp. 12-14.”
  • protocol operation and packet configuration according to the standard UMS specification that is not described in the present specification, refer to the UMS-related specification provided by the USB Forum.
  • the field format of the CBW command packet 310 that is a kind of command packet, which the host systems 120 and 220 transmit to the USB device 110 and 210 in accordance with the communication protocol of the standard UMS specification, is described in detail.
  • a dCBWSignature field has a fixed value of 0x43425355, and indicates that a corresponding data packet is a command block wrapper packet based on the standard UMS specification.
  • a dCBWTag field is used to indicate the pair coupling of the CBW packet and the CSW packet.
  • a CBWCB field is a CBW command block field, and includes the detailed contents of a command that is sent by the USB devices 110 and 210.
  • the field format of the CBW command block 320 is described in brief.
  • An Operation code field that is, a command identification code, indicates the type of an operation that must be executed by the USB devices 110 and 210, such as reading a file, formatting a disk format or writing a file.
  • the contents of the fields below the Operation code field are determined by the type of operation based on the Operation code field. In the present specification, for detailed descriptions of the contents of the fields, refer to the UMS-related specification provided by the USB Forum as described above.
  • the field format of the CSW packet 330 that is, an ACK packet that the USB devices 110 and 210 provide in response to the CBW command packet, is described in brief below.
  • a dCSWSignature field has a fixed value of 0x53425355, and indicates that a corresponding data packet is a command status wrapper packet based on the standard UMS specification.
  • a dCSWTag field has the same value as the dCBWTag field of a corresponding CBW packet, and indicates the pair coupling of the CBW packet and the CSW packet.
  • a bCSWStatus field indicates whether an operation according to the Operation code field has been successfully performed.
  • FIG. 4 is a flowchart showing a common UMS process flow, which is used in the method of providing the extended functions of the USB device according to the present invention. A user selects a command at step ST410.
  • the command can be a basic function, which has been conventionally provided using the standard UMS communication, or one of various extended functions, which have been implemented using the additional non-standard communication.
  • the determination step (ST420) is optional. For example, it is determined whether the command is supported in the current operating mode of the USB device 210, or any determination based on other criteria is also possible.
  • the manager program of the host system 220 creates a command packet, that is, the CBW command packet 310, in accordance with the selected command so that it can be compatible with the field format of the communication protocol of the standard UMS specification that has been described with reference to FIG. 3, at step ST430.
  • the manager program then transports the created CBW command packet 310 to a target USB device 210 at step ST440.
  • the individual fields of the CBW command block 320 are set in the CBW command packet 310 in accordance with the selected particular command. Thereafter, a series of processes of transmitting and receiving data packets is performed between the USB device 210 and the host system 220 as necessary at step ST450.
  • the transmitted and received data may include file data, control data, font data, firmware code data and the like.
  • the value of the command identification code is a value that is defined in the standard UMS specification, it indicates the case where a "basic function" is provided.
  • the fields below the operation code field in the CBW command block 320 are set according to the standard UMS specification.
  • the value of the command identification code is a value that is not defined in the standard UMS specification, it indicates the case where an "extended function" is provided according to the present invention.
  • the fields below the operation code field in the CBW command block 320 are set according to a rule that is additionally defined by a product designer. Meanwhile, since the additional rule that is applied when the "extended function" is provided is commonly applied to the host system 220 and the USB device 210, there is no communication problem.
  • the USB device 210 creates the CSW packet 330, that is, a kind of ACK packet, so that it can be compatible with the field format of the communication protocol of the standard UMS specification that has been described with reference to FIG. 3, and then transmits the CSW packet 330 to the host system 220.
  • the host system 220 can determine whether a predetermined operation corresponding to the operation code, that is, the command identification code, has been successfully performed in the USB device 210 based on the CSW packet 330. Accordingly, information on whether the predetermined command has been successfully performed can be provided to a user through the display screen of the host system 220. Meanwhile, although not shown in FIG.
  • the step of taking the user' s specific manipulation of the USB device 210 can be selectively added before or after step ST460.
  • the step can be constructed in such a way that, in the case of a firmware upgrade operation, whether effective firmware code data have been received is displayed on the screen of the USB device 210 when the transmission and reception of firmware code data have been performed, a display screen that waits for an input directing the start of the firmware upgrade operation is provided, and the USB device 210 starts the firmware upgrade operation when the user presses a button to issue a firmware upgrade command.
  • FIG. 5 is a diagram showing a method of changing the font of a USB device using the method of providing the extended functions of the USB device according to the present invention.
  • the function of changing the font is not included in the basic function of the standard UMS specification, but is an extended function provided by the present invention.
  • the interface between a PC manager program 620 and USB device firmware 610 is achieved using the standard UMS communication protocol. Since a font change command corresponds to an extended function, a code value, which is not defined in the standard UMS specification, is used in the operation code field, that is, the command identification code of the CBW command block 320.
  • a CBW packet, which specifies a font erasion region, is transmitted from the manager program 620 to the device firmware 610 at step ST610.
  • the device firmware 610 erases font data from the erasion region specified by the CBW packet and then transmits the CSW packet, that is, a kind of ACK packet, in accordance with an erasion result at step ST620.
  • the manager program 620 determines whether the font data erase operation for the specified region has been successfully performed by parsing the internal fields of the CSW packet, such as the bCSWStatus field, and determines whether to retry the font data erase operation according to the result of the previous font data erase operation.
  • the manager program 620 transmits a CBW packet to set a font data at step ST630.
  • the device firmware 610 receives the CBW packet at step ST635, sets a font data reception environment, and then waits for the reception of the data.
  • the font data Since the transmission of data in the standard UMS communication is performed on a page basis, and the font data usually has a very large size, the font data is divided into several packets, the manager program 620 transmits the packets several times, and the device firmware 610 receives the packets several times, recombines the packets and uses the recombined packets . Meanwhile, the device firmware 610 writes the received font data in the font erasion region. Depending on implementation, whenever each font data packet is received, corresponding font data may be written in the font erasion region, or after the entire font data is recombined, the recombined front data may be written in the font erasion region.
  • the device firmware 610 writes the received font data in the font erasion region and then transmits a CSW packet, that is, a kind of ACK packet, according to a writing result at step ST640.
  • the manager program 620 receives the CSW packet, and then determines whether the font data has been successfully written in the font erasion region and whether to retry to transmit the CBW packet by parsing the internal fields of the received packet. Thereafter, the device firmware 610 sets the display screen (not shown) of the USB device 210 using the received font data. In order to provide the function of changing the font shown in FIG.
  • the manager program 620 performs a two- step operation, that is, a first operation of erasing the font region of the USB device 210, and a second operation of transmitting the font data and then writing the font data in the font erasion region.
  • different command identification codes that is, operation codes
  • FIG. 6 is a diagram showing the method of upgrading firmware of the USB device using the method of providing the extended functions of the USB device according to the present invention.
  • the firmware upgrade function is not included in the basic function of the standard UMS specification, but is included in the extended function provided by the present invention.
  • the firmware upgrade function is designed so that the interface between the PC manager program 720 and the USB device firmware 710 is achieved by the standard UMS communication protocol. Since a firmware upgrade command corresponds to the extended function, a code value that is not defined in the standard UMS specification is used in the operation code field, that is, the command identification code of the CBW command block 320.
  • the manager program 720 creates a CBW packet that specifies a firmware upgrade operation based on the extended function, and transmits the CBW packet at step ST710.
  • the manager program 720 transmits an information packet, which includes information necessary to download a download program DN_PGM that will perform a process of downloading firmware code data, to the device firmware 710 at step ST720, and the device firmware 710 sets a download program downloading environment by receiving the DN_PGM information packet at step ST725 and then parsing the information packet.
  • the download program DN_PGM is then transferred to the device firmware 710 through the transmission and reception of a series of data packet between the manager program 720 and the device firmware 710.
  • the device firmware 710 copies the data to the internal memory of the USB device 210 when individual DNJPGM data packets are received, the device firmware 710 reconstructs the download program DNJPGM by combining all the data when the transmission and reception of all the data packets are completed, and the reconstructed download program DN_PGM is preferably executed in the internal memory of the USB device 210.
  • the manager program 720 transmits a code information packet, which contains various information to which the download program refers, at the time of transmitting and receiving the firmware code data at step ST730.
  • the device firmware 710 receives the code information packet at step ST735, acquires the contained information from the code information packet, and then checks the information. If the various information is included in the above-described DN PGM information packet, steps ST730 and ST735 of transmitting and receiving the code information packet may be omitted.
  • the device firmware 710 transmits a CSW packet corresponding to the above-described CBW packet at step ST740, and the manager program 720 receives the CSW packet at step ST745, and then determines whether the information of the firmware code data has been successfully transferred and whether to retry to transmit the code information packet by parsing the internal fields of the received CSW packet. Thereafter, the firmware code data is transmitted and received between the manager program 720 and the device firmware 710 at steps ST750 and ST755, and the USB device 210 performs an operation of replacing firmware with the received firmware code data.
  • firmware code that exists in the firmware memory region of a flash memory or Electrically Erasable and Programmable Read Only Memory (EEPROM) is erased, the received firmware code data are written in the firmware memory region, and then, preferably, the firmware code data are verified.
  • the device firmware 710 transmits a CSW packet whenever each of the data packets is received at step ST760, and the manager program 720 determines whether to transmit the next packet or whether to retry to transmit a current packet by receiving the CSW packet at step ST765 and parsing the received CSW packet.
  • the data that is transmitted and received between the manager program 720 and the device firmware 710 as the firmware code data is unformatted and unchangeable.
  • the manager program 720 and the device firmware 710 can determine whether the firmware code data has been successfully transmitted and received, based on the code information.
  • the device firmware 710 uses firmware code data, which is upgraded as the device is rebooted at step ST770-1, and the manager program 720 completes the firmware download program at step ST770-2.
  • the download program DN_PGM is a program that is downloaded from the host system 220 and is executed in the USB device 210.
  • the download program is used to allow the download operation of firmware code data to be performed, the specification of the loading location of the firmware code, and the writing and erasing of a flash memory to be performed in a manner desired by the designer of the USB device 210. That is, since the download program DNJPGM is provided by the design company of the USB device 210, the download program DN_PGM is made to handle the download operation, load operation and installation of actual firmware code data, the download program DN_PGM is optimally designed to fit the USB device 210, and the download program can then be provided to a user along with the USB device 210 or through the Internet.
  • the download program DN_PGM is provided with the firmware code data through the standard UMS communicatio .
  • the USB device firmware 610 and 710 to provide the special extended functions as described with reference to FIGS. 5 and 6, it is required that the lowest communication layer follow the standard UMS specification and the layers above the lowest communication layer perform the non-standard operation.
  • the USB device firmware 610 and 710 to provide the basic functions such as reading a file, formatting a disk and writing a file, it is required that the lowest communication layer and the layers above the lowest communication layer all operate in accordance with the standard UMS specification.
  • the USB device firmware 610 and 710 switches between operations based on the standard UMS specification and non-standard operation in accordance with the circumstances .
  • An implementation can be made such that before and after the switching, important information about the USB device firmware 610 and 710, such as the values of Vendor_ID, Product ID, Interface class, Interface subclass and Interface protocol can be changed, before and after the operation in accordance with the standard UMS specification and the non-standard operation.
  • important information about the USB device firmware 610 and 710 such as the values of Vendor_ID, Product ID, Interface class, Interface subclass and Interface protocol can be changed, before and after the operation in accordance with the standard UMS specification and the non-standard operation.
  • the specific function is a basic function or an extended function
  • the specific function is set.
  • the specific function is a basic function or an extended function using an initial CBW packet and the specific function is set.
  • the protocol stack for the standard UMS communication is provided to the USB device, so that there are advantages in that both the standard UMS communication and the non-standard communication through a USB interface with the host system can be supported, the USB device capable of supporting both the standard UMS communication and the non-standard communication can be constructed simply in terms of software and cheaply in terms of hardware through the above provision, product design can be simplified because it is not necessary to design a non- standard communication protocol with respect to each USB device, and communication speed can increase due to the improvement in the performance of the host system because a complicated program task is performed in the host system.

Landscapes

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

Abstract

La présente invention concerne un procédé qui permet d'offrir des fonctions USB étendues via une communication UMS standard, et d'accéder à diverses fonctions non standard et étendues, de même qu'à des fonctions USB de base, en utilisant uniquement la communication UMS standard avec un système hôte, via une interface USB. L'invention permet de fournir les deux types de communication, c'est-à-dire la communication UMS standard et la communication non standard, en utilisant uniquement le mécanisme de transport logiciel de la communication UMS standard, et par conséquent un dispositif USB utilisant les deux types de communication peut être équipé simplement en termes de logiciel et à peu de frais en termes de matériel. En outre, selon l'invention, étant donné que les opérations complexes sur le plan logiciel peuvent être traitées dans le système hôte, la vitesse de communication peut être augmentée proportionnellement à l'augmentation de la puissance de calcul du système hôte.
PCT/KR2004/002689 2003-10-21 2004-10-20 Procede permettant d'offrir des fonctions usb etendues via une communication ums standard Ceased WO2005038663A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20030073250A KR100496506B1 (ko) 2003-10-21 2003-10-21 표준 ｕｍｓ 통신을 이용한 ｕｓｂ 장치의 확장기능제공방법
KR10-2003-0073250 2003-10-21

Publications (1)

Publication Number Publication Date
WO2005038663A1 true WO2005038663A1 (fr) 2005-04-28

Family

ID=34464723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2004/002689 Ceased WO2005038663A1 (fr) 2003-10-21 2004-10-20 Procede permettant d'offrir des fonctions usb etendues via une communication ums standard

Country Status (2)

Country Link
KR (1) KR100496506B1 (fr)
WO (1) WO2005038663A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007090269A1 (fr) * 2006-02-06 2007-08-16 Memory Experts International Inc. Procédé et protocole de transmission d'instructions étendues à des dispositifs usb
EP1866749A4 (fr) * 2005-03-02 2008-09-17 6002552 Canada Inc Procede et protocole permettant de transmettre des commandes etendues a des dispositifs usb

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100794345B1 (ko) * 2006-07-04 2008-01-15 주식회사 모빌탑 유엠에스 데이터 통신 기능을 갖는 이동통신 단말기 및 그데이터 전송 방법
KR101444070B1 (ko) * 2009-07-30 2014-09-26 에스케이플래닛 주식회사 저장장치에서 호스트 단말의 메모리 이용 시스템 및 방법, 그 호스트 단말 및 저장장치, 이를 위한 기록매체

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20000034996A (ko) * 1998-10-14 2000-06-26 루센트 테크놀러지스 인크 통신 시스템에서 재전송 근거의 억세스 우선 순위를 위한 방법과 장치
KR20010090659A (ko) * 2000-04-10 2001-10-19 김형순 신호 프로토콜 장비에 독립적인 호처리 시스템 및 방법
KR20020057292A (ko) * 2000-12-30 2002-07-11 박종섭 통합 인터넷 프로토콜 망에서의 이동 인터넷 프로토콜관련 메시지 전달 방법
US6594240B1 (en) * 1998-05-22 2003-07-15 Lucent Technologies Inc. Methods and apparatus for random backoff based access priority in a communications system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6594240B1 (en) * 1998-05-22 2003-07-15 Lucent Technologies Inc. Methods and apparatus for random backoff based access priority in a communications system
KR20000034996A (ko) * 1998-10-14 2000-06-26 루센트 테크놀러지스 인크 통신 시스템에서 재전송 근거의 억세스 우선 순위를 위한 방법과 장치
KR20010090659A (ko) * 2000-04-10 2001-10-19 김형순 신호 프로토콜 장비에 독립적인 호처리 시스템 및 방법
KR20020057292A (ko) * 2000-12-30 2002-07-11 박종섭 통합 인터넷 프로토콜 망에서의 이동 인터넷 프로토콜관련 메시지 전달 방법

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1866749A4 (fr) * 2005-03-02 2008-09-17 6002552 Canada Inc Procede et protocole permettant de transmettre des commandes etendues a des dispositifs usb
WO2007090269A1 (fr) * 2006-02-06 2007-08-16 Memory Experts International Inc. Procédé et protocole de transmission d'instructions étendues à des dispositifs usb

Also Published As

Publication number Publication date
KR20050038060A (ko) 2005-04-27
KR100496506B1 (ko) 2005-06-21

Similar Documents

Publication Publication Date Title
US6965953B2 (en) Information processing apparatus, method for controlling information processing apparatus, and storage medium storing program for realizing the method
US9170936B2 (en) Communicating to update a memory
CN101110039B (zh) 终端设备自安装及自启动系统及方法
TW318227B (fr)
US8582139B2 (en) Driver upgrading
KR101555210B1 (ko) 휴대용 단말기에서 내장 대용량 메모리를 이용한 컨텐츠 다운로드 방법 및 장치
US20040049617A1 (en) Method of firmware update by USB interface
EP1205845B1 (fr) Microordinateur et méthode pour le contrôler
EP1962189A1 (fr) Appareil et procédé de mise à jour d'image de logo dans un terminal portable
US7047283B1 (en) Apparatus and method of upgrading program of firmware board
KR20030073824A (ko) 범용 직렬 버스를 이용한 시스템의 펌웨어 업그레이드방법 및 장치
WO2005038663A1 (fr) Procede permettant d'offrir des fonctions usb etendues via une communication ums standard
JP2006285476A (ja) 情報処理装置、方法、制御プログラム、媒体
JP2004220575A (ja) カード型メモリのインターフェース回路、その回路を搭載したａｓｉｃ、及びそのａｓｉｃを搭載した画像形成装置
JP2008059238A (ja) 通信システム及びそれに使用するプリンタ
US7395357B2 (en) Information processing apparatus and computer readable medium
CN115904820A (zh) 一种失效硬盘的恢复方法及系统
US20080165380A1 (en) Host device and method of installing printer driver thereof
JP2002007152A (ja) ダウンロード方法および装置
JP4239392B2 (ja) 印刷装置、印刷システムおよび印刷方法
JP2003114807A (ja) 電子機器及び本体制御プログラムの書き換え方法
JP2005038297A (ja) デバイスドライバのインストール方法、およびこれに用いる装置
EP4485175A1 (fr) Procédé de fonctionnement, système de mémoire, système et support de stockage lisible
JP2008059239A (ja) 通信システム
CN115933969B (zh) 存储器装置控制方法、存储器装置、电子装置、存储器控制器及计算机可读媒体

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 BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE 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