WO2004008313A1 - Usb device - Google Patents

Usb device Download PDF

Info

Publication number
WO2004008313A1
WO2004008313A1 PCT/IB2003/002801 IB0302801W WO2004008313A1 WO 2004008313 A1 WO2004008313 A1 WO 2004008313A1 IB 0302801 W IB0302801 W IB 0302801W WO 2004008313 A1 WO2004008313 A1 WO 2004008313A1
Authority
WO
WIPO (PCT)
Prior art keywords
usb
usb device
functionality
service
auxiliary device
Prior art date
Application number
PCT/IB2003/002801
Other languages
French (fr)
Inventor
Nicolas Drabczuk
Original Assignee
Axalto Sa
Schlumberger Malco, 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 Axalto Sa, Schlumberger Malco, Inc. filed Critical Axalto Sa
Priority to US10/521,228 priority Critical patent/US20050251596A1/en
Priority to EP03764040A priority patent/EP1532525A1/en
Priority to AU2003249112A priority patent/AU2003249112A1/en
Publication of WO2004008313A1 publication Critical patent/WO2004008313A1/en

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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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/10—Program control for peripheral devices

Definitions

  • the invention relates to a system comprising a main device arranged to communicate with an auxiliary device.
  • the main device can be, for example, a USB host.
  • the auxiliary device can be, for example, a USB device, which communicates with the USB host via a USB bus using the USB protocol.
  • the system comprises a USB host, which is connected to various USB devices via a USB bus.
  • the USB host communicates with the USB devices with the USB protocol.
  • the USB protocol allows connecting several USB devices on the same USB bus using a system of time-sharing based on addressed devices.
  • the USB protocol is organized as a master/ slave architecture, the USB host is thus responsible of the time-sharing management.
  • the USB host may comprise various applications. One or several services may be needed to run an application. An application uses one or several drivers to access and use the associated services. The drivers may be on the USB host.
  • the USB device may comprise various services, in particular those, which are needed by the applications of the USB host.
  • a service may be offered, for example, at the device level (standard USB device), or at the interface level (composite USB device).
  • the USB device is organized into several levels a device level, a configuration level, an interface level and an endpoint level. Each level is represented by different USB descriptors:
  • the device descriptor may be associated to one or more configuration descriptors.
  • the configuration descriptor may be associated to one or more interface descriptors.
  • An interface may contain one or more alternate settings.
  • the interface descriptor may be associated to zero or more endpoint descriptors.
  • the USB device is plugged onto a USB port of the
  • USB descriptors are then retrieved from the USB device to the host device.
  • the enumeration step is triggered off with the modification of the voltage level on the line D+ or D- (depending on the USB device speed) due to a pull-up resistor present in the USB device on one of the lines.
  • the USB Host uses the descriptors to load all the drivers of the USB device.
  • the number of drivers loaded depends on the number of different services present in the USB device. For example, if the USB device is at the same time a scanner and a printer the USB device will have to present two interfaces during the enumeration step. In that case, two drivers, one associated to the scanner interface, and the other one associated to the printer interface, will be loaded. A main driver associated to the device itself could also be loaded.
  • An object of the invention is to reduce the costs and to enhance the security.
  • a system comprising a main device and an auxiliary device arranged to co-operate with each other, the auxiliary device being arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that at least one descriptor defines a functionality that is different from the core functionality.
  • the auxiliary device can be for, example, a USB device in the form of a smart card.
  • the main device can be, for example, a USB host, in particular a computer.
  • the smart card may comprise as a core functionality, for example, an internet login application.
  • the functionality that is different from the core functionality can be, for example, a mass storage functionality.
  • the Smart Card (USB device) is seen as a mass storage. It is then possible to install a driver and /or an application from the USB device by simulating that the USB device is a mass storage.
  • the USB device can thus be used in any USB host, even if the driver(s) are not installed nor available, since the driver (s) is (are) available in the USB device itself. A user can thus use, for example, the login application directly from the USB device.
  • an Internet Service Provider can, for example, define its own proprietary login application and store it on the Smart Card itself (USB device). The risk of hacking the login application is therefore reduced.
  • the invention thus enables an enhanced security and a reduction of the cost.
  • Fig. 1 illustrates a system comprising a USB host and a USB device.
  • Fig.2 illustrates the structure of the USB device
  • Fig. 3 illustrates a method of using the system
  • Fig. 4 illustrates a system comprising a USB host and a USB device
  • Fig. 5 illustrates a method of using the system
  • Fig. 6 illustrates a particular mode of realization.
  • the system comprises a USB host, which is connected to a USB device via a USB bus.
  • the USB host communicates with the USB devices with the USB protocol.
  • the communication between the USB host and the USB device can be made according four different transfer modes:
  • a bulk transfer offering mainly a data integrity guarantee, and a possibly good data rate
  • a isochronous transfer offering mainly a bandwidth guarantee.
  • Two of these four modes require a bandwidth reservation, which is accorded or not by the USB host after an enumeration phase, depending on the bandwidth already reserved by other USB devices, which are plugged onto the USB bus.
  • the USB host comprises various applications (AO, Al).
  • One or several services (SI, S3) are needed to run an application (Al).
  • the application Al needs, for example, to use the service SI and the service S3.
  • the services (SI, S2, S3, S4) are located on the USB device.
  • an application Al uses a driver Dl.
  • the USB host also comprises a standard application (AO) associated with a standard driver (DO).
  • AO is implemented on a big number of USB hosts.
  • the USB device comprises various services (SI, S2, S3 and S4) in particular those (SO, SI, S3), which are needed by the applications (AO, Al) of the USB host.
  • the USB device also comprises two applications, (A21) and (A22). Each of these applications is arranged to run the service (S2) using respectively a driver D21 and a driver D22.
  • the application (A21) is, for example, an application arranged to be used on a first type of computer provided with a first type of Operating System.
  • the application (A22) is, for example, the same application than (A21) but arranged to be used on a second type of computer provided with a second type of
  • the USB device is, for example, a Smart Card.
  • the USB host is, for example, a Personal Computer (PC) using a specific Operating System (OS).
  • the services (S2, S3, S4) can be any Vendor Specific services.
  • the service (S2) can be a service associated, for example, to an Internet Service Provider login application, (A21) or (A22).
  • the service (SI) is a mass storage service.
  • driver(s) and/ or application(s) contained on the USB device can be installed by simulating that the USB device is a mass storage.
  • a service can be offered, for example, at the device level, or at the interface level (S1,S2,S3,S4).
  • the USB device also comprises a standard service (SO).
  • SO standard service
  • the standard service is implemented on a big number of USB devices.
  • the USB device is connected to a USB port of a USB host.
  • a first checking step CHECK 1 the USB device checks whether a negotiation flag is activated or not. If not: in a first enumerating step ENUM1, the USB host will enumerate the USB device. In other words, as illustrated in figure 2, the USB host will retrieve from the USB device to the USB host only the descriptors (I) associated to the standard service SO and to the mass storage service SI, in a loading step LOAD, the drivers DO and D 1 are loaded into an active memory of the USB host, - in a negotiation step NEGO, the standard application AO negotiates the services (S2, S3) to activate.
  • the negotiating step comprises the following sub-steps: o a first receiving step, in which the standard application AO receives from the standard service SO a first list of all the different services (S1.S2,
  • the USB device removes its pull-up resistor in order to detach itself and then re-attach itself.
  • a second checking step CHECK2 the USB device checks whether the negotiation flag is activated or not. If yes: in a deactivating step DEACTiV, the negotiation flag is deactivated, - in a second enumerating step ENUM2, the
  • USB host enumerates the USB device.
  • descriptors (II) associated to the services (SI, S2, S3) which have been activated and the descriptor associated to the standard service (SO) will be retrieved, in a second loading step LOAD2, the standard driver DO and the drivers (D1.D21 or D22.D3) associated to the services (SI, S2, S3) which have been activated are loaded into the active memory of the USB host.
  • the Smart Card (USB device) is seen as a mass storage. It is then possible to install a driver (D21 or D22) and/or an application (A21 or A22) from the USB device by simulating that the USB device is a mass storage.
  • the USB device can thus be used in any USB host, even if the driver(s) are not installed nor available, since the driver(s) is (are) available in the USB device itself.
  • the user can thus use the Internet Service Provider login application, (A21) or (A22), directly from the USB device to access the login service (S2).
  • an Internet Service Provider can, for example, define its own proprietary login application (A21).
  • this proprietary application (A21) is stored on the Smart Card itself (USB device) and not on the computer. The risk of hacking the application (A21) is therefore reduced.
  • the invention thus enables an enhanced security.
  • the standard application (AO) can negotiate the activation of the new service (S4) in a new negotiating step.
  • OPEN In an opening step OPEN, user opens a new application (A3) requiring a service (S4), which is not available in the current configuration of the USB device.
  • the USB host activates the service (S4).
  • the USB device activates the negotiation flag.
  • the USB device removes its pull-up resistor in order to detach itself and then re-attach.
  • a checking step CHECK the USB device checks whether the negotiation flag is activated or not. If yes: in a deactivating step DEACTIV, the negotiation flag is deactivated, in an enumerating step ENUM, the USB host enumerates the USB device. As illustrated in figure 2, only the descriptors (III) associated to the services (SI, S2, S3, S4) which have been activated and the descriptor associated to the standard service (SO) will be retrieved, in a loading step LOAD, the standard driver
  • DO and the drivers (D1.D21 or D22,D3,D4) associated to the services (SI, S2, S3.S4) which have been activated are loaded into the active memory of the USB host.
  • the service (S4) was first hidden from the USB host point of view. But one can imagine that once the USB device is inserted in the USB host, all the services are automatically enumerated. Some drivers will not be available and the corresponding application will be marked as not correctly installed. In this case, after the enumeration step, the user will have to update the drivers from the USB device.
  • FIG. 6 illustrates another example wherein the smartcard (USB device) comprises a loudspeaker service, a microphone service and a decryption service.
  • the loudspeaker service is activated by the computer.
  • the computer first considers the smartcard (USB device) as a loudspeaker and sends an encrypted music file (1).
  • the loudspeaker service receives the music file and sends it (2) to the decryption service for decrypting the music file.
  • the decrypted music file is sent (2) to the microphone service so that the computer (USB host) believes now (3) that the smartcard (USB device) is a microphone wherein someone is speaking.
  • the computer then sends the decrypted music file to the real loudspeaker (4).
  • a system comprising a main device and an auxiliary device arranged to co-operate with each other, the auxiliary device being arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that the auxiliary device comprises at least one descriptor that defines a functionality that is different from the core functionality.
  • the main device is, for example, a USB host and the auxiliary device is, for example, a USB device.
  • the invention is not limited to devices communicating using the USB protocol. Other protocol like, for example, firewire based protocol may be used.
  • the functionality that is different from the core functionality is, for example, a mass storage functionality.
  • the functionality that is different from the core functionality is, for example, a microphone functionality.
  • the functionality that is different from the core functionality is, for example, a loudspeaker functionality or any other functionality that is different from the core functionality, and that can be effected by the auxiliary device.
  • the auxiliary device when it is coupled to the main device, initially presents the descriptor that defines a functionality that is different from the core functionality.
  • the USB device comprises a driver for the USB host to be installed by simulating that the USB device is a mass storage.
  • the USB device is a smartcard or any other portable object arranged to use the USB protocol, like, for example, a Personal Digital Assistant (PDA) or a cellular phone.
  • PDA Personal Digital Assistant

Abstract

A system comprises a main device and an auxiliary device arranged to co-operate with each other.The auxiliary device is arranged to effect a core functionality. The auxiliary device comprises descriptors. The system is characterised in that the auxiliary device comprises at least one descriptor that defines a functionality that is different from the core functionality.

Description

USB device
FIELD OF THE INVENTION
The invention relates to a system comprising a main device arranged to communicate with an auxiliary device. The main device can be, for example, a USB host. The auxiliary device can be, for example, a USB device, which communicates with the USB host via a USB bus using the USB protocol.
BACKGROUND OF THE INVENTION
The system comprises a USB host, which is connected to various USB devices via a USB bus. The USB host communicates with the USB devices with the USB protocol. The USB protocol allows connecting several USB devices on the same USB bus using a system of time-sharing based on addressed devices. The USB protocol is organized as a master/ slave architecture, the USB host is thus responsible of the time-sharing management.
The USB host may comprise various applications. One or several services may be needed to run an application. An application uses one or several drivers to access and use the associated services. The drivers may be on the USB host.
The USB device may comprise various services, in particular those, which are needed by the applications of the USB host. A service may be offered, for example, at the device level (standard USB device), or at the interface level (composite USB device). The USB device is organized into several levels a device level, a configuration level, an interface level and an endpoint level. Each level is represented by different USB descriptors:
- A device descriptor describing the overall device. The device descriptor may be associated to one or more configuration descriptors.
- A configuration descriptor describing the electrical characteristics of the USB device, or of a part of the USB device. The configuration descriptor may be associated to one or more interface descriptors. - An interface descriptor describing a particular service of the USB device. An interface may contain one or more alternate settings. The interface descriptor may be associated to zero or more endpoint descriptors.
- An endpoint descriptor describing a communication channel used by the service defined by the interface descriptor.
In a plugging step, the USB device is plugged onto a USB port of the
USB host.
In an enumeration step, all the USB descriptors are then retrieved from the USB device to the host device. The enumeration step is triggered off with the modification of the voltage level on the line D+ or D- (depending on the USB device speed) due to a pull-up resistor present in the USB device on one of the lines. In a loading step, the USB Host then uses the descriptors to load all the drivers of the USB device. The number of drivers loaded depends on the number of different services present in the USB device. For example, if the USB device is at the same time a scanner and a printer the USB device will have to present two interfaces during the enumeration step. In that case, two drivers, one associated to the scanner interface, and the other one associated to the printer interface, will be loaded. A main driver associated to the device itself could also be loaded.
SUMMARY OF THE INVENTION
An object of the invention is to reduce the costs and to enhance the security.
According to one aspect of the invention, a system comprising a main device and an auxiliary device arranged to co-operate with each other, the auxiliary device being arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that at least one descriptor defines a functionality that is different from the core functionality.
The auxiliary device can be for, example, a USB device in the form of a smart card. The main device can be, for example, a USB host, in particular a computer. The smart card may comprise as a core functionality, for example, an internet login application. The functionality that is different from the core functionality can be, for example, a mass storage functionality.
Thanks to the invention, the Smart Card (USB device) is seen as a mass storage. It is then possible to install a driver and /or an application from the USB device by simulating that the USB device is a mass storage. The USB device can thus be used in any USB host, even if the driver(s) are not installed nor available, since the driver (s) is (are) available in the USB device itself. A user can thus use, for example, the login application directly from the USB device.
In addition, an Internet Service Provider can, for example, define its own proprietary login application and store it on the Smart Card itself (USB device). The risk of hacking the login application is therefore reduced. The invention thus enables an enhanced security and a reduction of the cost.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 illustrates a system comprising a USB host and a USB device.
Fig.2 illustrates the structure of the USB device;
Fig. 3 illustrates a method of using the system;
Fig. 4 illustrates a system comprising a USB host and a USB device;
Fig. 5 illustrates a method of using the system; and
Fig. 6 illustrates a particular mode of realization.
DETAILED DESCRIPTION
The invention will be explained in the context of a system using the USB protocol.
As illustrated in figure 1, the system comprises a USB host, which is connected to a USB device via a USB bus. The USB host communicates with the USB devices with the USB protocol.
The communication between the USB host and the USB device can be made according four different transfer modes:
- a control transfer, offering mainly a delivery and data integrity guarantee,
- an interrupt transfer, offering mainly a periodicity and data integrity guarantee,
- a bulk transfer, offering mainly a data integrity guarantee, and a possibly good data rate, a isochronous transfer, offering mainly a bandwidth guarantee.
Two of these four modes require a bandwidth reservation, which is accorded or not by the USB host after an enumeration phase, depending on the bandwidth already reserved by other USB devices, which are plugged onto the USB bus.
As illustrated in figure 1, the USB host comprises various applications (AO, Al). One or several services (SI, S3) are needed to run an application (Al). The application Al needs, for example, to use the service SI and the service S3. The services (SI, S2, S3, S4) are located on the USB device. To use a specific service SI, an application Al uses a driver Dl. The USB host also comprises a standard application (AO) associated with a standard driver (DO). Advantageously the standard application (AO) is implemented on a big number of USB hosts.
The USB device comprises various services (SI, S2, S3 and S4) in particular those (SO, SI, S3), which are needed by the applications (AO, Al) of the USB host. The USB device also comprises two applications, (A21) and (A22). Each of these applications is arranged to run the service (S2) using respectively a driver D21 and a driver D22. The application (A21) is, for example, an application arranged to be used on a first type of computer provided with a first type of Operating System. The application (A22) is, for example, the same application than (A21) but arranged to be used on a second type of computer provided with a second type of
Operating System. The USB device is, for example, a Smart Card. The USB host is, for example, a Personal Computer (PC) using a specific Operating System (OS). The services (S2, S3, S4) can be any Vendor Specific services. The service (S2) can be a service associated, for example, to an Internet Service Provider login application, (A21) or (A22). Advantageously, the service (SI) is a mass storage service. Thus driver(s) and/ or application(s) contained on the USB device can be installed by simulating that the USB device is a mass storage.
As illustrated in figure 2, a service (S) can be offered, for example, at the device level, or at the interface level (S1,S2,S3,S4).
The USB device also comprises a standard service (SO).
Advantageously the standard service (SO) is implemented on a big number of USB devices.
As illustrated in figure 3, in a connecting step CON, the USB device is connected to a USB port of a USB host.
In a first checking step CHECK 1, the USB device checks whether a negotiation flag is activated or not. If not: in a first enumerating step ENUM1, the USB host will enumerate the USB device. In other words, as illustrated in figure 2, the USB host will retrieve from the USB device to the USB host only the descriptors (I) associated to the standard service SO and to the mass storage service SI, in a loading step LOAD, the drivers DO and D 1 are loaded into an active memory of the USB host, - in a negotiation step NEGO, the standard application AO negotiates the services (S2, S3) to activate. The negotiating step comprises the following sub-steps: o a first receiving step, in which the standard application AO receives from the standard service SO a first list of all the different services (S1.S2,
S3, S4) which are available on the USB device, o a comparing step, in which the standard application compares the first list of all the different services (SI, S2, S3, S4) which are available on the USB device with a second list of the services
(S1,S2,S3) needed by the applications (A1.A2) to deduce the services to be activated (SI , S2, S3) on the USB device, o a second receiving step, in which the USB host indicates which type of computer is used and which type of Operating System (OS) is used, so that the USB device can install the corresponding application(s) (resp. A21 or A22) and the associated driver(s) (resp. D21 or D22). o a service activating step, in which the USB device activates the services to be activated, for example, by disconnecting and reconnecting the USB device to the USB host.
- In an flag activating step ACTTV, the negotiation flag is activated.
In an initialization step INIT, the USB device removes its pull-up resistor in order to detach itself and then re-attach itself.
In a second checking step CHECK2, the USB device checks whether the negotiation flag is activated or not. If yes: in a deactivating step DEACTiV, the negotiation flag is deactivated, - in a second enumerating step ENUM2, the
USB host enumerates the USB device. As illustrated in figure 2, only the descriptors (II) associated to the services (SI, S2, S3) which have been activated and the descriptor associated to the standard service (SO) will be retrieved, in a second loading step LOAD2, the standard driver DO and the drivers (D1.D21 or D22.D3) associated to the services (SI, S2, S3) which have been activated are loaded into the active memory of the USB host.
The Smart Card (USB device) is now ready for use.
Thanks to the invention, from the user point of view, the Smart Card (USB device) is seen as a mass storage. It is then possible to install a driver (D21 or D22) and/or an application (A21 or A22) from the USB device by simulating that the USB device is a mass storage. The USB device can thus be used in any USB host, even if the driver(s) are not installed nor available, since the driver(s) is (are) available in the USB device itself.
The user can thus use the Internet Service Provider login application, (A21) or (A22), directly from the USB device to access the login service (S2).
Thanks to the invention, an Internet Service Provider can, for example, define its own proprietary login application (A21). In addition this proprietary application (A21) is stored on the Smart Card itself (USB device) and not on the computer. The risk of hacking the application (A21) is therefore reduced. The invention thus enables an enhanced security.
Note that, if a new service has to be added on the USB device, the standard service (SO) does not change and therefore the standard application (AO) does not change.
As illustrated in figure 4 and 5, if the USB device is already plugged, and the user starts a new application (A3), which requires a new service (S4), which is not activated in the USB device, the standard application (AO) can negotiate the activation of the new service (S4) in a new negotiating step.
In an opening step OPEN, user opens a new application (A3) requiring a service (S4), which is not available in the current configuration of the USB device.
In a negotiating step NEGO, the USB host activates the service (S4).
In a flag activating step ACTIV, the USB device activates the negotiation flag.
In an initialization step INIT, the USB device removes its pull-up resistor in order to detach itself and then re-attach.
In a checking step CHECK, the USB device checks whether the negotiation flag is activated or not. If yes: in a deactivating step DEACTIV, the negotiation flag is deactivated, in an enumerating step ENUM, the USB host enumerates the USB device. As illustrated in figure 2, only the descriptors (III) associated to the services (SI, S2, S3, S4) which have been activated and the descriptor associated to the standard service (SO) will be retrieved, in a loading step LOAD, the standard driver
DO and the drivers (D1.D21 or D22,D3,D4) associated to the services (SI, S2, S3.S4) which have been activated are loaded into the active memory of the USB host.
In the above-mentioned example, the service (S4) was first hidden from the USB host point of view. But one can imagine that once the USB device is inserted in the USB host, all the services are automatically enumerated. Some drivers will not be available and the corresponding application will be marked as not correctly installed. In this case, after the enumeration step, the user will have to update the drivers from the USB device.
Figure 6 illustrates another example wherein the smartcard (USB device) comprises a loudspeaker service, a microphone service and a decryption service. When the smartcard (USB device) is plugged into a computer (USB host) the loudspeaker service is activated by the computer. The computer first considers the smartcard (USB device) as a loudspeaker and sends an encrypted music file (1). The loudspeaker service receives the music file and sends it (2) to the decryption service for decrypting the music file. Then the decrypted music file is sent (2) to the microphone service so that the computer (USB host) believes now (3) that the smartcard (USB device) is a microphone wherein someone is speaking. The computer then sends the decrypted music file to the real loudspeaker (4).
The description hereinbefore illustrates the following features:
A system comprising a main device and an auxiliary device arranged to co-operate with each other, the auxiliary device being arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that the auxiliary device comprises at least one descriptor that defines a functionality that is different from the core functionality.
According to another aspect of the invention, the main device is, for example, a USB host and the auxiliary device is, for example, a USB device. It should be clear that the invention is not limited to devices communicating using the USB protocol. Other protocol like, for example, firewire based protocol may be used.
According to another aspect of the invention, the functionality that is different from the core functionality is, for example, a mass storage functionality.
According to another aspect of the invention, the functionality that is different from the core functionality is, for example, a microphone functionality. According to another aspect of the invention, the functionality that is different from the core functionality is, for example, a loudspeaker functionality or any other functionality that is different from the core functionality, and that can be effected by the auxiliary device. According to another aspect of the invention, the auxiliary device, when it is coupled to the main device, initially presents the descriptor that defines a functionality that is different from the core functionality.
According to another aspect of the invention, the USB device comprises a driver for the USB host to be installed by simulating that the USB device is a mass storage. According to another aspect of the invention, the USB device is a smartcard or any other portable object arranged to use the USB protocol, like, for example, a Personal Digital Assistant (PDA) or a cellular phone.

Claims

A system comprising a main device and an auxiliary device arranged to co-operate with each other, the auxiliary device being arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that at least one descriptor defines a functionality that is different from the core functionality.
The system according to claim 1, wherein the main device is a USB host and the auxiliary device is a USB device.
3. The system according to claim 2, wherein the functionality that is different from the core functionality is a mass storage functionality.
4. The system according to claim 1, wherein the auxiliary device, when it is coupled to the main device, initially presents the descriptor, that defines a functionality that is different from the core functionality.
5. The system according to claim 2, wherein the USB device comprises a driver for the USB host to be installed by simulating that the USB device is a mass storage.
6. The system according to claim 2, wherein the USB device is a smartcard.
7. An auxiliary device arranged to effect a core functionality, the auxiliary device comprising descriptors, characterised in that at least one descriptor defines a functionality that is different from the core functionality.
8. The auxiliary device according to claim 7, wherein the auxiliary device is a USB device.
The auxiliary device according to claim 7, wherein the auxiliary device is a smart card.
PCT/IB2003/002801 2002-07-15 2003-07-15 Usb device WO2004008313A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US10/521,228 US20050251596A1 (en) 2002-07-15 2003-07-15 Usb device
EP03764040A EP1532525A1 (en) 2002-07-15 2003-07-15 Usb device
AU2003249112A AU2003249112A1 (en) 2002-07-15 2003-07-15 Usb device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP02291778.5 2002-07-15
EP02291778 2002-07-15
EP02291795 2002-07-17
EP02291795.9 2002-07-17

Publications (1)

Publication Number Publication Date
WO2004008313A1 true WO2004008313A1 (en) 2004-01-22

Family

ID=30116926

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2003/002801 WO2004008313A1 (en) 2002-07-15 2003-07-15 Usb device

Country Status (3)

Country Link
EP (1) EP1532525A1 (en)
AU (1) AU2003249112A1 (en)
WO (1) WO2004008313A1 (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2422223A (en) * 2004-12-20 2006-07-19 Trek 2000 Int Ltd Enumerating a memory device as a human interface device to overcome system administrator blockage
WO2007076984A1 (en) * 2005-12-22 2007-07-12 Giesecke & Devrient Gmbh Method for installing an auxiliary unit on a computer
WO2007138488A2 (en) * 2006-05-25 2007-12-06 Axalto S.A. A method of patching applications on small resource-contrained secure devices
WO2008136816A1 (en) 2007-05-07 2008-11-13 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically providing an alternate usb configuration of a usb compliant peripheral device for exposure to a host computer
WO2010083257A3 (en) * 2009-01-13 2010-09-23 Qualcomm Incorporated System, apparatus, and method for fast startup of usb devices
EP2370897A2 (en) * 2008-12-29 2011-10-05 Intel Corporation Composite device emulation
GB2483167A (en) * 2010-08-27 2012-02-29 Fxi Technologies As Storage device with separate application and interface processors
US8171502B2 (en) 2006-11-29 2012-05-01 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically installing device drivers from a peripheral device onto a host computer

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6012103A (en) * 1997-07-02 2000-01-04 Cypress Semiconductor Corp. Bus interface system and method
US6199137B1 (en) * 1999-01-05 2001-03-06 Lucent Technolgies, Inc. Method and device for controlling data flow through an IO controller
US20010027500A1 (en) * 2000-03-09 2001-10-04 International Business Machines Corporation Data transmission system, data transmission terminal, controller and interface method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6012103A (en) * 1997-07-02 2000-01-04 Cypress Semiconductor Corp. Bus interface system and method
US6199137B1 (en) * 1999-01-05 2001-03-06 Lucent Technolgies, Inc. Method and device for controlling data flow through an IO controller
US20010027500A1 (en) * 2000-03-09 2001-10-04 International Business Machines Corporation Data transmission system, data transmission terminal, controller and interface method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
JOHN HOWARD; STEVE MCGOWAN: "USB Feature Specification : Dynamic Logical-Device", 27 October 1999, INTEL CORPORATION, XP002224120 *

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2422223A (en) * 2004-12-20 2006-07-19 Trek 2000 Int Ltd Enumerating a memory device as a human interface device to overcome system administrator blockage
WO2007076984A1 (en) * 2005-12-22 2007-07-12 Giesecke & Devrient Gmbh Method for installing an auxiliary unit on a computer
US7788419B2 (en) 2005-12-22 2010-08-31 Giesecke & Devrient Gmbh Method for installing an auxiliary unit on a computer
WO2007138488A2 (en) * 2006-05-25 2007-12-06 Axalto S.A. A method of patching applications on small resource-contrained secure devices
WO2007138442A1 (en) * 2006-05-25 2007-12-06 Axalto S.A. A methhod of patching applications on small resource-contrained secure devices.
WO2007138488A3 (en) * 2006-05-25 2008-05-08 Axalto Sa A method of patching applications on small resource-contrained secure devices
US8171502B2 (en) 2006-11-29 2012-05-01 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically installing device drivers from a peripheral device onto a host computer
WO2008136816A1 (en) 2007-05-07 2008-11-13 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically providing an alternate usb configuration of a usb compliant peripheral device for exposure to a host computer
EP2370897A2 (en) * 2008-12-29 2011-10-05 Intel Corporation Composite device emulation
EP2370897A4 (en) * 2008-12-29 2012-06-06 Intel Corp Composite device emulation
CN102272723A (en) * 2009-01-13 2011-12-07 高通股份有限公司 System, apparatus, and method for fast startup of USB devices
WO2010083257A3 (en) * 2009-01-13 2010-09-23 Qualcomm Incorporated System, apparatus, and method for fast startup of usb devices
JP2012515400A (en) * 2009-01-13 2012-07-05 クゥアルコム・インコーポレイテッド System, apparatus and method for fast startup of USB devices
US8713209B2 (en) 2009-01-13 2014-04-29 Qualcomm Incorporated System, apparatus, and method for fast startup of USB devices
GB2483167A (en) * 2010-08-27 2012-02-29 Fxi Technologies As Storage device with separate application and interface processors
GB2483167B (en) * 2010-08-27 2013-05-29 Fxi Technologies As Storage device with separate application and interface processors
US9069488B2 (en) 2010-08-27 2015-06-30 Fxi Technologies As Electronic devices
US9134923B2 (en) 2010-08-27 2015-09-15 Fxi Technologies As Electronics device
US9451026B2 (en) 2010-08-27 2016-09-20 Millennium Enterprise Corporation Electronic devices

Also Published As

Publication number Publication date
AU2003249112A1 (en) 2004-02-02
EP1532525A1 (en) 2005-05-25

Similar Documents

Publication Publication Date Title
US20050251596A1 (en) Usb device
US9116723B2 (en) Communication device or media device for providing phone calling service, internet access service, or digital content service
US9934049B1 (en) Method for creation of device drivers and device objects for peripheral devices
US5519851A (en) Portable PCMCIA interface for a host computer
US7921244B2 (en) Data sharing and transfer systems and methods
US6572384B1 (en) Method and apparatus for interconnecting circuit cards
US7899443B2 (en) Multi-access solid state memory devices and a telephone utilizing such
US5884086A (en) System and method for voltage switching to supply various voltages and power levels to a peripheral device
US6978335B2 (en) Smart card virtual hub
EP0552873B1 (en) Modifying system configuration in a computer system
US5797031A (en) Method and apparatus for peripheral device control by clients in plural memory addressing modes
US20120042103A1 (en) Smart card with self-detachment features and related methods
WO2006129138A1 (en) Method of connecting hard disk
US20050060490A1 (en) Apparatus for multiple host access to storage medium
WO2004008313A1 (en) Usb device
TWI361380B (en) Electronic devices and methods for managing mass storage devices
EP2372565A1 (en) Method for managing USB devices
WO2006053278A2 (en) System and method for securing the intialization of a smartcard controller
KR100705381B1 (en) Method of managing USB devices using Security Controller added into USB host controller
CN1338683A (en) Personal computer operation system for dynamic re-configuration
US20050240704A1 (en) Smart card with self-reconfiguration features and related methods
EP1394682B1 (en) Data transfer control device, program and method of fabricating an electronic instrument
KR20080017810A (en) Method and apparatus for interfacing using otg in mobile phone
Wang et al. I/O and Network Interface
JP2001256168A (en) Usb device

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 BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL 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): GH GM KE LS MW MZ 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 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
WWE Wipo information: entry into national phase

Ref document number: 2003764040

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003764040

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 10521228

Country of ref document: US

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)