This invention relates to computer-implemented systems for managing imaging devices, such as digital cameras, scanners, and the like. This invention also relates to graphical window user interfaces, and particularly to user interfaces used to facilitate capture and storage management of digital images. This invention further relates to operating systems and browsers that incorporate image device managers and user interfaces.
Digital imaging devices, such as scanners, cameras, video cameras, have been experiencing rapid growth in popularity as their price tags continue to decrease. Recreational photographers enjoy capturing pictures and videos and placing the digital files onto their computers for printing or emailing to friends and relatives. Businesses use scanners to digitally record documents used in day-to-day operation for archival purposes.
Other solutions to this problem already exist. For example, TWAIN and ISIS are two image acquisition systems that are available today. However, both of these solutions have problems. TWAIN lacks robustness and interoperability. ISIS is a proprietary design that renders it difficult to use with other applications.
Accordingly, a task set before the inventor was to create an image acquisition system that was based on an open architecture model and could be integrated with existing applications and operating systems to provide a convenient environment for the user.
This invention concerns an image acquisition system that offers an open architecture to integration with existing operating systems and other applications.
In an exemplary implementation, the image acquisition system is implemented on computer, such as a desktop personal computer, having a processing unit, memory, and operating system. One or more imaging devices are coupled to the computer. Examples of the imaging devices include a scanner, a digital camera, a digital video camera, and so forth. Some imaging devices, such as digital cameras, have a device memory and are capable of capturing a digital image and storing the image on its memory. Other imaging devices, such as scanners, may not have their own device memory.
The image acquisition system further includes an image device manager that is implemented in software on the computer to control operation of the imaging devices. The image acquisition system presents a user interface (UI) within the familiar graphical windowing environment. The UI presents a graphical window having a context space that pertains to a particular imaging context (e.g., scanning, photography, and video). In the camera context, the context space presents image files stored on the camera memory and/or on the computer memory. In the scanner context, the context space includes a preview scan area that reveals a preview of the image in the scanner. In the video context, the context space presents video clips stored on the computer memory, but logically represented as belonging to the video camera.
The UI also has a persistently visible imaging menu positioned within the context space that lists options particular to an imaging context. For example, if the context space pertains to the camera context, the menu lists options to take a picture, store a captured image on the computer, send the image in an email, and SO on. In the scanner context, the menu lists options to select an image type, preview an image, send the image to a particular destination, and scan the image.
The image acquisition system also includes a set of application program interfaces (APIs) that expose image management functionality to applications. The APIs enable applications to manage loading and unloading of imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the images after their capture.
This invention concerns a computer-implemented image acquisition system that manages imaging devices (such as digital cameras, scanners, digital video cameras, and the like) and the images captured by them. In a preferred implementation, the image acquisition system is implemented in a general-purpose computer (e.g., personal computer, laptop, etc.) to manage imaging devices attached locally to the computer or coupled remotely via a network. The image acquisition system supports a graphical user interface windowing environment that integrates image device management with the same look and feel of familiar browsing user interfaces for conventional file systems. In this manner, a user encounters a familiar experience when managing the imaging devices and image files from his/her computer.
Exemplary System Architecture
The imaging devices 24-30 are coupled to the computer via a serial connection to the USB 50. Illustrated examples of the imaging devices include a scanner 24, a video camera 26, and a digital camera 28. However, other imaging devices (e.g., copiers, facsimile machines, etc.) may also be used in conjunction with aspects of this invention, as represented by the generic imaging device 30. Some of the imaging devices have their own memory, as represented by memory 32 in imaging device 30. For example, the digital camera may have its own memory, whereas the scanner typically does not have a memory.
The image acquisition system 20 includes an image device manager 60, which is implemented as a software component stored on a computer-readable medium loaded on the computer 22. More particularly, the image device manager 60 is stored in program memory 46 and runs on processing unit 40 during execution. The image device manager 60 may be integrated into the operating system 52 (as shown), executed as a set of services, or implemented as a separate self-contained program.
The image acquisition system 20 also has a user interface 62, which is preferably a graphical user interface that presents a graphical window having a context space pertaining to the imaging context. Depending upon the particular context, the context space may list available imaging devices for which device drivers have been loaded onto the computer, or list digital image files captured by one or more of the imaging devices, or show an image being scanned in by the scanner.
The user interface 62 further presents a persistently visible imaging menu positioned within the context space. The imaging menu lists options that are particular to controlling the various imaging devices. For instance, when the context space pertains to the camera context, the menu lists a “Take Picture” option that is specific to operating the digital camera 28. Upon user selection of “Take Picture”, the image device manager 60 directs the digital camera 28 to record the current image obtained through the camera lens. In the scanner context, the menu lists a “Scan/Open” option that is particular to operating the scanner. Upon selection of this option, the image device manager 60 directs the scanner to scan the current image.
The image device manager 60 has an image device driver 64 and a set of APIs (application program interfaces) 66. The image device driver 64 controls operation of the imaging device in response to selected options in the context-specific menu. The driver 64 is the code that facilitates communication with the imaging device over the USB 50 and passes commands to capture an image, to read image files from the device's local memory, to obtain the device's properties, and so forth.
The APIs 66 define a set of interfaces that can be used to access the functionality of the image device manager 60. These APIs are described below in a section entitled “Image Acquisition API”.
Exemplary Software Architecture
At the user level, a device driver 74 is loaded for the particular imaging device connected to the computer. The device driver 74 includes a device object, an optional UI, and optional image processing capabilities. An image device manager object 76 is called to initialize and select an image device, and create the device interface. The image device manager object 76 performs such tasks as instantiating a device driver object 74, determining the device status, monitoring events from the device, and so forth.
A COM (component object model) layer 78 exposes the device driver object 74 and image device manager object 76 to an upper level application 80. The application layer 80 represents both traditional TWAIN based applications that utilize a TWAIN compatibility layer 82, as well as new applications that support the APIs 66. Unlike the traditional TWAIN model, however, the TWAIN compatibility layer 82 interacts with the COM-based objects 74 and 76 rather than TWAIN-based devices.
Image Acquisition User Interface
The image acquisition system may be incorporated into the operating system, exist as a set of services, or be run as a separate, self-contained application. For discussion purposes, the image acquisition system is described as being integrated into an operating system that supports a graphical user interface windowing environment.
Of interest to the image acquisition system is the integration and treatment of the imaging devices as a folder 102 organized with the other general computer components. This provides a convenient starting point for the user to access the imaging devices 24-30 that are coupled to the computer 22.
When the user activates the “Imaging Devices” folder icon 102 for the first time, an installation Wizard comes up to guide the user through the installation of an imaging device. Suppose, for example, the user has installed two scanning devices and a digital camera. Activating the “Imaging Devices” icon 102 navigates to a new “Imaging Devices” window.
The “Imaging Devices” window 110 distinguishes between devices that are currently available and those that are not available (e.g., offline, physically removed, etc.). Devices that are not available are dimmed and the user has the option of uninstalling them. In
Activating one of the imaging devices listed in window 110 causes the image acquisition system to present different windows exhibiting contexts that are specific to the selected imaging device. Within these device-oriented windows, the image acquisition system presents context-specific menus that contain items or options pertinent and relevant to the particular imaging device.
The context-specific menu 126 is always visible in the scanner window 120. The menu 126 offers options that are tailored to operating the scanner attached to the computer or remotely coupled to the computer via a network. While some of the options may be included in a context menu (i.e., a menu that appears near the pointer following a right mouse click), the persistently-visible menu 126 lists operating specific options tailored to the scanner that are not included elsewhere in the user interface.
The menu 126 includes an image type selection 128 that has a pull-down list of various image types from which a user may select. A non-exhaustive list of image types includes color photograph, black and white photograph, color line art, black and white line art, and text. The image types included in the pull-down list 128 are specific to the device. Some imaging devices may not provide support for a given format and hence the format is omitted in that particular list.
A destination selection 130 has a pull-down list of various choices on what to do with the scanned image. For instance, the list 130 might include using the image in an application, faxing the image, printing the image, copying the image to a clipboard, and saving the image in a file. The destination selection simplifies the output operation for the user. For example, selection of a choice directly affects the acquisition parameters and image quality without requiring the user to know what parameters to set.
The persistently-visible context-specific menu 126 also has a “New Preview” command 132 that directs scanners to create a preview image of an image that is currently in the scanning bed. The image is presented in the preview scan space 124. When the image appears in the scan space 124, a preview control 134 is provided to allow the user to select a region of the image for a final scan. In the illustrated implementation, the control 134 is shown as a dashed rectangular box framing the picture. The user can manipulate the box 134 to capture all or less than all of the image. Upon selection of the region, the control can proportionally resize the image to reflect the size of the scanner bed and automatically configure the scanner to make the appropriate adjustments to capture the selected image portion.
The menu 126 includes a “Scan/Open” command 136 to direct the scanner to capture the image. When this command is selected, the scanner scans the image in its bed. Concurrently with this scanning action, the image progressively appears in the preview scan space 124 to visually convey that the scanner is scanning the image. In one implementation, the image is progressively displayed row-by-row from top to bottom of the image.
The menu 126 includes a “Save” option 138, which directs the scanner to capture the image as a file and store the file in the computer memory. The last listed option is a “Send to” option 140, which allows the user to send the image to various locations (or applications) on the PC, such as for packaging in a facsimile or email.
The context-specific menu 156 is always visible in the camera window 150 and offers options that are tailored to operating the digital camera 28 attached to the computer. While some of the options may be included in a context menu (i.e., a menu that appears near the pointer following a right mouse click), the persistently-visible menu 156 lists operating specific options tailored to the camera that are not included elsewhere in the user interface.
The menu 156 is illustrated as having two tabs: a pictures tab 158 and a camera tab 160. Table 1 contains the options and corresponding functions available on the pictures tab 158.
Table 2 contains the options and corresponding functions available on the camera tab 160.
The file space 154 lists files and/or folders that pertain to digital images taken by the digital camera. The files are the images themselves (e.g., JPG files) and the folders contain image files and/or other folders with image files in them.
The file space 154 presents the files that are currently stored on the camera. In this manner, the user can easily view the camera memory as if it were another memory of the computer. The UI allows easy integration of the camera control into the familiar windowing environment.
To add a picture to the file space, the user captures a picture using the “Take Picture” command in the camera menu 160. The picture then appears as a file in the file space 154. The user can then select the image file by clicking on the file and manipulating the picture using the commands on the pictures menu 158, such as “Rotate to the Left”, “Rotate to the Right”, “Zoom”, and “Send to”. The user can also save the image file to the computer memory using the command “Save in My Pictures folder”.
Notice also that one of the files in the file space 174 is a play-in-place video file 180. This play-in-place video file 180 can be actuated to play a video clip or stream within the small area depicted as box 180. That is, the static video icon in box 180 is replaced with a streaming video at the same location in the file space. Play-in-place video files 180 were first introduced in Media Manager, a multimedia application available from Microsoft.
Table 3 contains the options and corresponding functions available on the video tab 178.
Other commands may be added to the menu. For instance, a “stop” command may be employed to halt the capture of live video.
Image Acquisition API
The image acquisition API 66 enables applications to manage loading and unloading of all imaging devices, monitor device events, query device information properties, create device objects, capture images using the devices, and store or manipulate the images after their capture.
The interfaces are accessible by high level languages (e.g., Visual Basic) as well as lower level ones (e.g., C, C++, etc.). COM is a suitable interface. In this context, each device is exposed as a COM object, whereby the object provides a number of methods and properties associated with the imaging device.
As one exemplary implementation, there are three general objects: a device manager object, a camera object, and a scanner object. The objects are described generally below. A more detailed description of the objects and methods are provided at the end of this section.
The device object contains device context and status information for a physical device. Once a device object is created for a physical device, the physical device controls what device properties are available and what values the properties may assume. There may be multiple device objects created for any physical device. However, a device object has exclusive access to a physical device before any operation (i.e., scan, take a picture, etc.) is performed. Exclusive access to a physical device is made available through a locking/unlocking mechanism.
The device manager is implemented as three objects that perform the following functions:
A CImageInDevMgr object is used to:
A CEnumImageInDevInfo object is used to:
A CImageInDevInfo object is used to:
The camera object may expose the following functions:
The scanner object may expose the following functions:
ImageIn Device Manager
The ImageIn device manager provides interfaces for enumerating devices, querying properties of installed ImageIn devices and creating ImageIn device objects. The device manager has three objects.
CImageInDevMgr is used to:
CEnumImageInDevInfo is used to:
CImageInDevInfo is used to:
Device information properties are distinct from normal device properties in that they are read from the registry and can be queried without forcing the device object to be created.
A program using its own methods to select an ImageIn device would do the following:
IImageInDevMgr Interface
EnumImageInDevInfo
EnumImageInDevInfo creates a standard enumerator for CImageInDevInfo objects. The enumerator itself is a CEnumImageInDevInfo object that has a single interface IEnumIMAGEIN_DEV_INFO. Applications can use this API to obtain device information properties from available ImageIn devices.
Parameters:
GetImageInDevInfo
Given a device ID GetImageInDevInfo returns an IPropertyStorage interface to CImageInDevInfo objects. This API gives applications a quick way to retrieve device information properties from a stored device ID.
Parameters:
CreateImageInDev
CreateImageInDev creates a device object identified by bstrDeviceID and returns an IUnknown interface to the object. The application can use QueryInterface on this IUnknown to access the other interfaces on a device.
Parameters:
SelectImageInDev
SelectImageInDev displays UI for the selection of ImageIn devices. When the user selects a device, the device object is created and an IUnknown interface is returned. The application can then use QueryInterface on this IUnknown to access the other interfaces on a device. Returns S_FALSE if the user cancels the selection dialog without making a device selection, S_OK if the user makes a device selection or an error value if the method fails.
Parameters:
GetImage
GetImage displays device selection UI allowing a user to select a device. If the user selects a device, a device is created and device UI is displayed to capture the image. Image data is returned in the pMedium structure. Image format and default image capture properties may be specified using the lIntent and cfFormat parameters. Returns S_FALSE if the user cancels the selection dialog without making a device selection, S_OK if the user makes a device selection and the data is transferred or an error value if the method fails.
Parameters:
EnumDestinationInfo
EnumImageInDestInfo creates a standard enumerator for CImageInDestInfo objects. The enumerator itself is a CEnumImageInDestInfo object that has a single interface IEnumIMAGEIN_DEST_INFO. Applications can use this API to obtain device destination properties from an ImageIn device. Destination applications are registered using RegisterDestinationApplication.
Parameters:
RegisterDestinationApplication
This method is called when an application wishes to register as an ImageIn destination.
Parameters:
UnregisterDestinationApplication
This method is called when an application that has registered an ImageIn destination wishes to be uninstalled or no longer known as an ImageIn destination.
Parameters:
IEnumIMAGEIN_DEV_INFO Interface
The IEnumIMAGEIN_DEV_INFO interface is a standard OLE enumeration interface that supports per device enumeration of device information properties.
Next
Next returns an array of IPropertyStorage interfaces to CImageInDevInfo objects. Applications can use the returned of IPropertyStorage interfaces to obtain device information properties from available ImageIn devices.
Parameters:
Skip
Skip skips device objects in the enumeration.
Parameters:
Reset
Reset sets the enumeration back to the first device.
Clone
Clone creates another IEnumIMAGEIN_DEV_INFO enumeration object and returns an interface pointer to it.
Parameters:
IEnumIMAGEIN_DEST_INFO Interface
The IEnumIMAGEIN_DEST_INFO interface is a standard OLE enumeration interface that supports enumeration of device destination properties.
Next
Next returns an array of IPropertyStorage interfaces to CImageInDestInfo objects. Applications can use the returned of IPropertyStorage interfaces to obtain destination information properties from available ImageIn devices.
Parameters:
Skip
Skip skips destination objects in the enumeration.
Parameters:
Reset
Reset sets the enumeration back to the first device.
Clone
Clone creates another IEnumIMAGEIN_DEST_INFO enumeration object and returns an interface pointer to it.
Parameters:
IPropertyStorage Interface
The IPropertyStorage interface is used to query the device information and destination properties. IPropertyStorage is a standard OLE interface and is documented in the OLE Programmers Reference. All device information properties are read only. Any attempt to modify the device information properties will result in a failure with access denied. The methods of this interface are:
Device Information Properties
All ImageIn devices support the following basic device information properties:
ImageIn Scanner Device Object
ImageIn device objects support interfaces for querying and setting device properties, displaying device UI and transferring data. ImageIn devices are required to support a small number of standard interfaces that allow applications to deal with all devices in a common manner and transfer data from the devices in a manner that is native to the (COM) application. Device objects may also support more specialized interfaces to implement custom functions. Since the application has a direct connection to the device object, this architecture does not place any strict limits on the interfaces a device object can export. Practically speaking though, applications must know about an interface for it to be useful.
IScan Interface
ScanDlg
ScanDlg presents the system or device UI needed to prepare a device for scanning. If the dialog successfully completes, the scan object will be ready to begin data transfer via the IDataObject or IimageTransfer interfaces. The default image capture properties may be specified using the optional lIntent parameter. Returns S_FALSE if the user cancels the selection dialog without making a device selection, S_OK if the user makes a device selection or an error value if the method fails.
Parameters:
IPropertyStorage Interface
The standard IPropertyStorage interface is used to query and set all scan device properties. IPropertyStorage is a standard OLE interface and is documented in the OLE Programmers Reference. The methods of this interface are:
All ImageIn scanner devices support the following basic device properties:
ImageIn scan devices may support additional device properties depending on hardware configuration.
IDevPropStream Interface
The IDevPropStream interface is used to query/set all current device properties from/to a named, non-volatile, registry based storage. The methods of this interface are:
ReadDevPropStream
ReadDevPropStream reads a device property stream from the specified value and initializes the device with these properties. The properties are per user and per device.
Parameters:
WriteDevPropStream
WriteDevPropStream writes the current device property stream to the specified value. The properties are per user and per device.
Parameters:
ListDevPropStreams
ListDevPropStreams lists the device property stream names present in non-volatile storage. The list is returned in an allocated BSTR which the application must free using SysFreeString.
Parameters:
DeleteDevPropStream
DeleteDevPropStream deletes a device property stream from non-volatile storage.
Parameters:
IDataObject Interface
The IDataObject interface is a standard OLE data transfer mechanism. This interface is used to provide an easy and natural way for applications to transfer data from a scan device. The full IDataObject interface description can be found in the OLE2 Programmer's Reference. The methods of this interface are:
IImageTransfer Interface
The IImageTransfer is a high performance data transfer interface. This interface uses a shared memory window to transfer data from the device object to the application, eliminating unnecessary data copies during marshalling. For simplicity, this interface uses the same format negotiation method as IDataObject. IImageTransfer uses two different mechanisms to transfer data:
Banded Transfers
The device breaks a large image transfer up into smaller transfers, which are performed sequentially into an application-specified buffer.
Data Callback
The device does a single large transfer, while calling back to the application as the transfer progresses.
itAllocateTransferBuffer
Allocates a buffer to use for scanning data from the device. The buffer is mapped into the address space of both the client and server process.
Parameters:
itFreeTransferBuffer
Free the buffer created by itAllocateTransferBuffer. This buffer is also freed when the device object is destroyed.
itBeginTransfer
Reset a device object context to begin an IImageTransfer.
Parameters:
ItGetImage
Perform an image transfer.
Parameters:
itGetImageCB
Perform an image transfer using a user specified callback.
Parameters:
itEndTransfer
Cleanup a device object context after an image transfer.
Parameters:
itQueryGetData
Check to see if a device supports a given format in an image transfer.
Parameters:
itEnumFormatEtc
Create a format enumerator.
Parameters:
ImageIn Camera Device Object
The ImageIn Camera is a hierarchical object. The top-level camera object is used to get basic device information and also to get access to individual images or image folders. The CCameraItem object represents images and Image folders.
ICamera Interface
TakePicture
The TakePicture method instructs a camera to take a new picture.
GetCameraRootItem
This method returns an interface to the root CCameraItem object. Using the IcameraItem interface it is possible to enumerate all images on the camera.
Parameters:
GetCameraItemByHandle
This method returns an ICameraItem interface to the specified CCameraItem object. A handle for a CCameraItem object can only be obtained through the ICameraItem interface.
Parameters:
CameraDlg
Display the camera UI. UI will select an image on a device and prepare for image transfer. The UI returns a ICameraItem interface to a CCameraItem ready for data transfer. IDataObject or IImageTransfer interfaces are then used to transfer image data.
Parameters:
ICameraItem Interface
A CCameraItem object is created for every image and directory on the camera. This is done to support full and flexible hierarchical image storage on cameras. A ICameraItem pointer is returned for each CCameraItem object. ICameraItem methods are defined below.
GetItemType
GetItemType returns the type of camera item the object represents. The two types of camera items are:
Parameters:
Parameters:
PItemHandle Item handle returned. This handle may be used by the GetCameraItemByHandle method of the ICamera interface to obtain an IcameraItem pointer.
OpenImagePropertyStorage
Returns an IPropertyStorage interface to the CCameraItem object.
Parameters:
EnumChildItems
Creates a CEnumCameraItem object and returns a IEnumCameraItem interface to it. This method only works if the camera item is a folder and the folder is not empty, as shown in the figure above.
Parameters:
IEnumCameraItem Interface
IEnumCameraItem is a standard OLE enumerator interface with the usual four methods Next, Skip, Clone and Reset. This enumerator will return an ICameraInterface for each camera item in the current camera folder (that was used in the call to EnumChildItems).
Next
Return an ICameraItem interface for each CCameraItem contained by the current folder.
Parameters:
Skip
Skip celt CCameraItem objects.
Parameters:
Reset
Begin at the first CCameraItem object.
Parameters: None
Clone
Create a new CEnumCameraItem object and return a IEnumCameraItem interface.
Parameters:
Camera Download Manager
The camera download manager monitors the connection status of camera devices. When a camera device is connected to the system, the Download Manager will attempt to immediately download all the images from the camera onto the system hard disk. The camera download manager will also maintain a data base of all images previously downloaded from a given camera and not download images that are already cached.
Caching images in this manner has several advantages.
In order for the camera download manager to work effectively, camera events must be detectable. For example, it should be easy to detect when a camera is connected or disconnected from the system. This should be detectable without loading the entire camera driver. Also any activity performed directly on the camera (through camera controls) must be reported to software so an accurate internal model of the state of the camera can be kept.
Sample Code
Get an image from an ImageIn device. Use the ImageIn device manager device selection UI and the device image acquisition UI.
Enumerate all installed ImageIn devices and get the device ID of a specific device:
Although the invention has been described in language specific to structural features and/or methodological steps, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or steps described. Rather, the specific features and steps are disclosed as preferred forms of implementing the claimed invention.
This application is a continuation of U.S. patent application Ser. No. 10/086,927, filed on Oct. 19, 2001 now U.S. Pat. No. 6,912,693, entitled “Computer-Implemented Image Acquisition System”, listing Franc J. Camara, Rick Turner, Mark Enstrom, Reed Bement and Shaun Ivory as inventors, which is a divisional of U.S. patent application Ser. No. 09/153,432, filed on Sep. 14, 1998, now U.S. Pat. No. No. 6,373,507, having common title and inventorship and each assigned to the same assignee as the present application, which patent is hereby incorporated herein by reference. This application is also related to U.S. patent application Ser. No. 10/087,257, filed on Oct. 19, 2001, having common title and inventorship, which is also a divisional of U.S. patent application Ser. No. 09/153,432, filed on Sep. 14, 1998, which is now U.S. Pat. No. 6,373,507, and is also related to U.S. patent application Ser. No. 10/990,150, filed on even date herewith, which is a continuation of U.S. patent application Ser. No. 10/086,927, and to U.S. patent application Ser. No. 10/990,780, filed on Nov. 17, 2004, which is a continuation of U.S. patent application Ser. No. 10/086,927.
Number | Name | Date | Kind |
---|---|---|---|
4837635 | Santos | Jun 1989 | A |
5191645 | Carlucci et al. | Mar 1993 | A |
5385475 | Sudman et al. | Jan 1995 | A |
5412773 | Carlucci et al. | May 1995 | A |
5630079 | McLaughlin | May 1997 | A |
5652849 | Conway et al. | Jul 1997 | A |
5657461 | Harkins et al. | Aug 1997 | A |
5706457 | Dwyer et al. | Jan 1998 | A |
5796945 | Tarabella | Aug 1998 | A |
5949411 | Doerr et al. | Sep 1999 | A |
6028604 | Matthews, III et al. | Feb 2000 | A |
6097389 | Morris et al. | Aug 2000 | A |
6118546 | Sanchez et al. | Sep 2000 | A |
6239882 | De Mangelaere et al. | May 2001 | B1 |
6249361 | Tahara | Jun 2001 | B1 |
6288716 | Humpleman et al. | Sep 2001 | B1 |
6425001 | Lo et al. | Jul 2002 | B2 |
6463426 | Lipson et al. | Oct 2002 | B1 |
6486976 | Nakamura et al. | Nov 2002 | B1 |
6504571 | Narayanaswami et al. | Jan 2003 | B1 |
6587129 | Lavendel et al. | Jul 2003 | B1 |
Number | Date | Country | |
---|---|---|---|
20050097477 A1 | May 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09153432 | Sep 1998 | US |
Child | 10086927 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10086927 | Oct 2001 | US |
Child | 10990247 | US |