1. A computer-implemented method, comprising:
exposing a set of USB driver interfaces that are exposed by a USB core driver stack, the USB driver interfaces including USB driver interface functions configured to interface with USB client function drivers that correspond to one or more client USB devices;
registering a composite device driver that registers itself and requests a function handle for each individual function of a client USB device; and
enumerating the USB client function drivers to generate the function handles that each correspond to an individual function of the client USB device.
2. A computer-implemented method as recited in claim 1, further comprising:
exposing extensions for the USB driver interface functions, the extensions exposed by the USB core driver stack to interface with the USB client function drivers; and
interfacing, with the extensions for the USB driver interface functions, the USB core driver stack with at least legacy and current versions of the USB client function drivers.
3. A computer-implemented method as recited in claim 1, further comprising identifying a USB client function driver that causes a runtime failure, the USB client function driver being identifiable by a function handle that corresponds to the individual function of the client USB device that is associated with the USB client function driver.
4. A computer-implemented method as recited in claim 1, further comprising notifying the USB core driver stack, via an extension of the USB driver interface functions, that the composite device driver will control suspending each of the individual functions of the client USB device.
5. A computer-implemented method as recited in claim 1, further comprising enforcing a check first protocol that directs a USB client function driver to check for availability of a USB driver interface function before interfacing with the USB core driver stack via the USB driver interfaces.
6. A computer-implemented method as recited in claim 1, further comprising receiving a contract version identifier from a USB client function driver via an extension of the USB driver interface functions, the contract version identifier indicating a set of operation rules by which the USB client function driver interfaces with the USB core driver stack.
7. A computer-implemented method as recited in claim 1, further comprising:
receiving a capability version request from a USB client function driver; and
returning an indication that the USB core driver stack supports extensions for the USB driver interface functions.
8. A computer-implemented method as recited in claim 1, further comprising:
implementing the USB core driver stack for inputoutput of computer instructions and data exchange;
allocating multiple data stream queues to an endpoint for the inputoutput; and
managing the inputoutput of the multiple data stream queues.
9. A computer-implemented method as recited in claim 1, further comprising:
receiving a request from a USB client function driver to allocate a URB (USB Request Block); and
allocating the URB for the USB client function driver.
10. A computer-implemented method as recited in claim 9, further comprising:
allocating additional buffer space that is associated with the URB; and
utilizing the additional buffer space to manage the inputoutput associated with the USB client function driver.
11. A computer-implemented method, comprising:
exposing a set of USB driver interfaces that are exposed by a USB core driver stack, the USB driver interfaces including USB driver interface functions configured to interface with USB client function drivers that correspond to one or more client USB devices; and
enforcing a check first protocol that directs a USB client function driver to check for availability of a USB driver interface function before interfacing with the USB core driver stack via the USB driver interfaces.
12. A computer-implemented method as recited in claim 11, further comprising identifying a USB client function driver that causes a runtime failure, the USB client function driver being identifiable by a function handle that corresponds to an individual function of the client USB device that is associated with the USB client function driver.
13. A computer-implemented method as recited in claim 11, further comprising registering a composite device driver that registers itself and requests a function handle for each individual function of a client USB device, the composite device driver notifying the USB core driver stack that the composite device driver will control suspending each of the individual functions of the client USB device.
14. A computer-implemented method as recited in claim 11, further comprising:
exposing extensions for the USB driver interface functions, the extensions exposed by the USB core driver stack to interface with the USB client function drivers; and
receiving a contract version identifier from a USB client function driver via an extension of the USB driver interface functions, the contract version identifier indicating a set of operation rules by which the USB client function driver interfaces with the USB core driver stack.
15. A computer-implemented method as recited in claim 11, further comprising:
receiving a capability version request from a USB client function driver; and
returning an indication that the USB core driver stack supports the extensions for the USB driver interface functions.
16. A computer-implemented method, comprising:
exposing a set of USB driver interfaces that are exposed by a USB core driver stack, the USB driver interfaces including USB driver interface functions configured to interface with USB client function drivers that correspond to one or more client USB devices; and
receiving a contract version identifier from a USB client function driver via an extension of the USB driver interface functions, the contract version identifier indicating a set of operation rules by which the USB client function driver interfaces with the USB core driver stack.
17. A computer-implemented method as recited in claim 16, further comprising notifying the USB core driver stack that a composite device driver will control suspending individual functions of a client USB device, the composite device driver said notifying the USB core driver stack via an extension of the USB driver interface functions.
18. A computer-implemented method as recited in claim 16, further comprising enforcing a check first protocol that directs a USB client function driver to check for availability of a USB driver interface function before interfacing with the USB core driver stack via the USB driver interfaces.
19. A computer-implemented method as recited in claim 16, further comprising:
exposing extensions for the USB driver interface functions, the extensions exposed by the USB core driver stack to interface with the USB client function drivers;
receiving a capability version request from the USB client function driver; and
returning an indication that the USB core driver stack supports the extensions for the USB driver interface functions.
20. A computer-implemented method as recited in claim 16, further comprising identifying a USB client function driver that causes a runtime failure, the USB client function driver being identifiable by a function handle that corresponds to an individual function of the client USB device that is associated with the USB client function driver.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
We claim:
1. An anti-idiotypic antibody having specific reactivity with an idiotope common to at least three types of human anti-HIV-antibody of differing specificities, but not significantly reactive with idiotypes of human non-HIV-1 antibodies.
2. The antibody of claim 1 wherein said antibody is a monoclonal antibody.
3. The antibody of claim 1 wherein the idiotope is a clonotype of human polyclonal anti-HIV-1 antibodies.
4. The antibody of claim 2 wherein said antibody is designated 1F7 produced by hybridoma ATCC Accession No. HB 11286.
5. A hybridoma cell line capable of expressing the antibody of claim 2.
6. The hybridoma cell line of claim 5 wherein said cell line is designated by ATCC Accession No. HB 11286.
7. The idiotope recognized by the antibody of claim 1.
8. A compound which is specifically reactive with the idiotope of claim 7, and not reactive with idiotypes found on human non-HIV-1 antibodies.
9. A method of detecting HIV-related pathologies comprising detecting the expression of the idiotope of claim 7 on the immunoglobins of an HIV infected individual.
10. The method of claim 9 wherein the idiotope is detected on immunoglobins by reacting the immunoglobins with the 1F7 antibody.
11. The method of claim 10 wherein the pathology is HIV-related lymphoma.
12. A method of monitoring the occurrence of HIV-1 related lymphoma in HIV patients comprising detecting the expression of the idiotope of claim 7 on the immunoglobins of an HIV infected individual over time.
13. A method of restoring oligoclonality in the immune response to HIV-1 infection comprising administering the antibody of claim 1 to an HIV individual.
14. The method of claim 13 wherein the antibody is 1F7.
15. The method of claim 13 comprising administering a compound which is specifically reactive with an idiotope common to at least three types of human anti-HIV-antibody of differing specificities, but not significantly reactive with idiotypes of human non-HIV-1 antibodies to an HIV individual.
16. A method of regulating the composition of T cell lymphocytes in HIV sera comprising enhancing apoptosis of T cells lymphocytes in HIV sera by administering a sufficient amount of the antibody of claim 1.
17. The method of claim 15 wherein the antibody is 1F7.
18. The method of claim 16 wherein the cells undergoing apoptosis are CD8 cells.
19. A method of reducing T cell-mediated cytotoxicity in HIV sera comprising administering a sufficient amount of the antibody of claim 1.
20. The method of claim 19 wherein the antibody is 1F7.
21. A method for detecting human anti-HIV-1 antibodies having a common idiotope not found on human non-HIV-1 antibodies comprising the steps of:
a) contacting an antibody-containing sample obtained from a subject with the antibody of claim 1; and
b) determining if the antibody of claim 1 binds to the antibody-containing sample, wherein binding indicates the presence of HIV-1 antibodies having a common idiotope.
22. A pharmaceutical composition comprising an effective amount of the antibody of claim 1 in a physiologically acceptable carrier.
23. A pharmaceutical composition comprising an effective amount of the compound of claim 8 in a physiologically acceptable carrier.
24. A method for the prevention or treatment of HIV-related disease comprising administrating an effective amount of the composition of claim 23 to an HIV-infected individual.
25. A method for the prevention or treatment of HIV-related disease comprising administering an effective amount of the composition of claim 24 to an HIV-infected individual.