1. Field of the Invention
This invention pertains generally to configuration ROM implementations for IEEE Standard 1394 nodes. More particularly, the invention is a method and apparatus for presenting a plurality of link devices as separate nodes within a singe serial bus module by generating individual or a distinct configuration ROM image for each link device in the module.
2. The Prior Art
The Institute of Electrical and Electronics Engineers, Inc. (IEEE) defines the IEEE Standard 1394-1995 serial bus architecture in the document “IEEE Standard for a High Performance Serial Bus” published Aug. 30, 1996 that is incorporated herein by reference. In IEEE 1394, the serial bus architecture is defined in terms of nodes. In general, a node is an addressable entity (i.e., a logical entity with a unique address), which can be independently reset and identified. More than one node may reside on a single module, and more than one unit may reside in a single node.
A module is a physical device, comprising one or more nodes that share a physical interface. The address space provided by a node can be directly mapped to one or more units. A unit is a logical entity, such as a disk controller, which corresponds to unique I/O (input/output) driver software. On a multifunction node, for example, a processor and I/O interfaces could be different units on the same node.
Modules and/or nodes can be “interconnected” with each other using an appropriate physical topology suitable for use with the serial bus, such as a “backplane environment” and/or “cable environment”, for example. These environments are described in further detail in Institute of Electrical and Electronics Engineers (IEEE) Standard 1394-1995 “IEEE Standard for a High Performance Serial Bus” published Aug. 30, 1996. Interconnected nodes may reside in either environment without restriction.
Configuration ROM implementations are well known in the field of serial bus devices and provide the hardware and software specifications of a serial bus node and its associated units. For example in IEEE Standard 1394, two configuration ROM formats are supported: minimal and general. The minimal ROM format provides a 24-bit company identifier. The general ROM format provides additional information in a bus_info_block and a root_directory. Entries within the root_directory may provide information or may provide a pointer to another directory (root-dependent directory and/or unit_directory), which has the same structure as the root_directory. Entries within the root directory may also provide a pointer to a leaf, which contains information. The unit_directories contain information about the units associated with the node, such as their software version number and their location within the address space of the node, for example.
In general, the bus_info_block provides specific information about the node. For example, the bus_info_block may indicate whether the node carries out isochronous data transfers. Additionally, the bus_info_block provides a node_vendor_id field, a chip_id_hi field, and a chip_id_lo field, among other things. Together, the node_vendor_id, chip_id_hi, and chip_id_lo fields form a 64-bit node unique identifier. Other node specific information may be provided in the root_directory and the root leaves of the ROM. Unit specific information is normally provided in the unit_directory and the unit leaves of the ROM. For example, the specification identification and the version number may be provided for a particular protocol in the unit_directory and the unit leaves. IEEE Standard 1394-1995 “IEEE Standard for a High Performance Serial Bus” published Aug. 30, 1996 describes the general ROM format and its associated blocks in further detail and is incorporated herein by reference.
According to the prior art, a serial bus module may include one or more nodes. For example,
Presently, the configuration ROM described above is managed by software operating at the transaction layer 6 in module 1. However, current transaction layer implementations which support multiple link devices (such as depicted in
Other node or module devices (not shown) attached to serial bus 8 may query module 1 to ascertain certain configuration data associated with module 1. For example, a remote node may query module 1 to ascertain, among other things, the node configuration of module 1 and/or the units presented by the nodes of module 1. These remote nodes query module 1 using one of various request commands. Some remote nodes request information “by quadlet” and other nodes request information “by block”, for example.
When a request is made by quadlet, the corresponding link devices 3a, 3b provide the requested data from the hardware registers 9a, 9b associated with the respective link device 3a, 3b. In this manner, link device 3a provides the requested data from its hardware registers 9a, and link device 3b provides the requested data from its hardware registers 9b.
However, when a request is made by block, the requested data is provided from the configuration ROM 7 which is normally managed by the transaction layer software 6. As noted above, present transaction layer implementations provide a single configuration ROM 7 for multiple link devices 3a, 3b. Thus the data provided in conjunction with a request by block may be different and inconsistent with that provided had the request been made by quadlet.
Accordingly, there is a need for a method for presenting a plurality of link devices as separate nodes within a single serial bus module by generating an individual or distinct configuration ROM image for each link device in the module so that when a request is made to the module, accurate and consistent data is provided to the requesting device. The present invention satisfies these needs, as well as others, and generally overcomes the deficiencies found in the background art.
An object of the invention is to provide a method for supporting multiple link devices in a single module that overcomes the deficiencies of the prior art.
Another object of the invention is to provide a method for presenting a plurality of link devices as separate nodes within a single serial bus by providing an individual configuration ROM for each link device in the module.
Further objects and advantages of the invention will be brought out in the following portions of the specification, wherein the detailed description is for the purpose of fully disclosing the preferred embodiment of the invention without placing limitations thereon.
The present invention is a method and apparatus embodied in transaction layer software suitable for use with serial bus devices, such as IEEE standard 1394 serial bus devices. The invention further relates to machine readable media on which are stored embodiments of the present invention. It is contemplated that any media suitable for retrieving instructions is within the scope of the present invention. By way of example, such media may take the form of magnetic, optical, or semiconductor media. The invention also relates to data structures that contain embodiments of the present invention, and to the transmission of data structures containing embodiments of the present invention.
In its most general terms, the invention comprises software for supporting multiple link devices in the same physical module as separate nodes by presenting individual or distinct configuration ROMs for each link device to the serial bus. In the preferred embodiment, the software comprises IEEE standard 1394 transaction layer software (TNF kernel) for a serial bus module attachable to an IEEE standard 1394 bus. The software is executed by a conventional processor within the module device as is known in the art.
The serial bus module may include one or more link devices operatively coupled for communication with the TNF kernel. In other exemplary embodiments, device driver services may be used to manage communication between the TNF kernel and the link devices as is known in the art.
The TNF kernel carries out the operation of ascertaining or becoming aware of the link devices in the modules, creating an individual configuration ROM for each link device, and presenting the created configuration ROMs to the other devices on the 1394 bus to thereby present each link device in the module as a separate node.
The TNF kernel ascertains each link device normally during initialization of the module, either through a predefined startup routine or through notification from device driver services, if such services are implemented in the module. The TNF kernel ascertains, among other things, each link device's GUID (globally unique identifier).
For each link device, the TNF kernel creates a data structure suitable for storing data associated with each link device. In an exemplary embodiment of the invention, the TNF kernel uses a data structure comprising a list of link data records, one record for each link device. Each link data record includes a CSR (control and status register) address map and Configuration ROM image storage and/or support thereof. Each Configuration ROM image is constructed using, among other things, the information for each link device and includes an entry for the link device GUID. The CSR address map is a data structure that, among other things, points to the active configuration ROM. In one of a number of possible embodiments, the present invention may employ dynamic configuration ROM using double image buffers which is described in copending application Ser. No. 09/431,703 having the title “A SYSTEM AND METHOD FOR PROVIDING DYNAMIC CONFIGURATION ROM USING DOUBLE IMAGE BUFFERS” filed on Nov. 1, 1999 and is incorporated herein by reference.
Requests by other devices to the module are communicated from the serial bus to the physical layer device in the present module. Communications for layers higher than the physical layer are then communicated to the link layer device for further processing.
When a request by quadlet is made to the module, the appropriate link device provides the appropriate information from the link device's registers as is conventionally carried out.
However, when a request by block is made to the module, the request is communicated from the corresponding link device to the TNF kernel. In addition, the link device provides its unique software ID (Link ID) along with the request. In response to the block request, the TNF kernel provides the configuration ROM for the appropriate link device according to the Link ID. Since individual configuration ROMs are created for each link device in the module, the information provided by the TNF kernel via the individual configuration ROM is consistent with information provided in response to requests made by quadlet as described above.
The present invention will be more fully understood by reference to the following drawings, which are for illustrative purposes only.
Persons of ordinary skill in the art will realize that the following description of the present invention is illustrative only and not in any way limiting. Other embodiments of the invention will readily suggest themselves to such skilled persons having the benefit of this disclosure.
Referring more specifically to the drawings, for illustrative purposes the present invention is embodied in the apparatus shown
Referring now to
The module 10 further includes one or more unit architectures 20 to present to other devices on the serial bus 18. Unit architectures 20 may comprise conventional units, such as a disk controller or some other storage device and a scanner controller, for example. These unit architectures 20 are presented to the serial bus by the generated configuration ROM as described further below and described above in conjunction with
The unit architectures 20 and the LINKS 14a, 14b are operatively coupled for communication to TNF kernel 22. The TNF kernel 22 provides transactional services for module 10 and the method of the invention as described herein and in further detail in conjunction with
Each of the LINKs 14a, 14b further includes a respective global unique identifier (GUID) 24a, 24b that identifies each node 12a, 12b to other nodes on the serial bus.
The TNF kernel 22 becomes aware of each link device normally during initialization of the module 10, either through a predefined startup routine or through notification from device driver services, if such services are implemented in the module. The TNF kernel 22 ascertains, among other things, each link device's GUID 24a, 24b.
The TNF kernel 22 then creates, normally within RAM (not shown), a data structure for storing configuration ROM data for each link device 14a, 14b. Various data structures may be used for storing configuration ROM data, however, in the preferred embodiment, the TNF kernel 22 uses a linked list of “link data records”, one data record for each link device 14a, 14b. Thus, TNF kernel 22 creates a configuration ROM 26a, 26b corresponding to each link device 14a, 14b. For each configuration ROM 26a, 26b, the TNF kernel 22 creates a GUID entry for the corresponding link device 14a, 14b. Thus, ROM 22a which is associated with link 14a includes an entry for GUID124a, and ROM 22b which is associated with link 14b includes an entry for GUID124b. With this arrangement, a one-to-one mapping is made with LINK 14a to node 12a via configuration ROM 26a, and with LINK 14b to node 12b via configuration ROM 26b.
The CSR address map of node 10 includes pointers to various items associated with node 10, including the ROM associated with each link device 14a, 14b.
As noted above, the present invention may be used in conjunction with the dynamic configuration ROM implementation described in copending application Ser. No. 09/431,703 having the title “A SYSTEM AND METHOD FOR PROVIDING DYNAMIC CONFIGURATION ROM USING DOUBLE IMAGE BUFFERS” filed on Nov. 1, 1999 and is incorporated herein by reference. This embodiment is one of a number of possible embodiments.
Referring now to
System 30 includes a module 10 structured and configured as described above in conjunction with
Module 10 is connected to the serial bus 18 via lines 28a and 28b, where line 28a is coupled to PHY 16a (Node 12a) and line 28b is coupled to PHY 16b (Node 12b). As depicted in
Module 10 further includes Nodes 30a, 30b each operatively coupled to the serial bus 18. Nodes 30a, 30b may comprise any serial bus device capable of communication with Module 10. Other modules having a plurality of nodes (not shown) may also be connected to the serial bus 18 and communicate with Module 10 in substantially the same manner as described herein with respect to nodes 30a, 30b. As shown, node 30a is structured and configured for 1394 IP communication, while node 30b is structured and configured for 1394 AV/C communication.
In operation, when node 30a makes a block read request (1394 IP) to module 10, such request is communicated along bus 18 and line 28a to PHY 16a. PHY 16a then communicates the request to LINK 14a, for further processing. LINK 14a then communicates the request to TNF kernel 22, along with Link ID of LINK 14a. In response, TNF kernel 22 provides the configuration ROM information associated with LINK 14a from ROM 26a. As noted above, ROM 26a includes the GUID associated with LINK 14a. This configuration ROM information is then communicated back to Node 30a via LINK 14a, then through PHY 16a, line 28a, and bus 18 ultimately to the requesting node 30a.
In contrast to the previous data path outlined above for node 30a, when node 30b makes a block read request (1394 AV/C) to module 10, such request is communicated along bus 18 and line 28b to PHY 16b. PHY 16b then communicates the request to LINK 14b, for further processing. LINK 14b then communicates the request to TNF kernel 22, along with Link ID of LINK 14b. In response, TNF kernel 22 provides the configuration ROM information associated with LINK 14b from ROM 26b, which includes the GUID associated with LINK 14b. This configuration ROM information is then communicated back to Node 30b via LINK 14b, then through PHY 16b, line 28b, and bus 18 ultimately to the requesting node 30b.
As illustrated above, TNF kernel 22 provides the corresponding configuration ROM (including correct GUID data) for the link device in which the request is carried out and in which communication is carried through. As such, a consistent one-to-one mapping between link devices and nodes is provided within the multiple-link device module (in the above example module 10) even when the request is a request “by block”.
The method and operation of the invention will be more fully understood by reference to the flow chart of
At box 100, the TNF kernel 22 operating in module 10 becomes aware of the link devices in the module. As noted above, this is carried out normally during initialization of the module 10, either through a predefined startup routine or through notification from device driver. The TNF kernel 22 ascertains, among other things, each link device's GUID 24a, 24b. Box 110 is then carried out.
At box 110, the TNF kernel 22 creates or otherwise generates a configuration ROM image for each link device within the module 10. Thus, in
At box 120, the module 10 receives a block request from another node (or module) on the serial bus. The request is received in respective PHY 16a, 16b. Which PHY receives the request varies according to various factors, including which protocol is supported, for example as illustrated in
At box 130, the TNF kernel 22 determines which configuration ROM 26a, 26b is requested according the LINK ID communicated from the LINK device from box 120. The TNF kernel 22 then provides the configuration ROM associated with the LINK ID to the requesting node. If the module uses the dynamic configuration ROM using double image buffers, noted above, then the TNF kernel provides the “active” ROM image according the LINK ID provided. Step 120 may then be carried out again for additional block requests.
Accordingly, it will be seen that this invention provides a method which supporting multiple link devices in the same physical module as separate nodes by presenting individual or distinct configuration ROMs for each link device to the serial bus. Although the description above contains many specificities, these should not be construed as limiting the scope of the invention but as merely providing an illustration of the presently preferred embodiment of the invention. Thus the scope of this invention should be determined by the appended claims and their legal equivalents.
This application is a continuation of and claims priority to co-owned U.S. patent application Ser. No. 10/944,265, now U.S. Pat. No. 7,191,266, of the same title filed Sep. 15, 2004, which is a continuation of co-owned U.S. patent application Ser. No. 09/432,869, now U.S. Pat. No. 6,813,663, filed Nov. 2, 1999, each of which are herein incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4156798 | Doelz | May 1979 | A |
4194113 | Fulks et al. | Mar 1980 | A |
5014262 | Harshavardhana | May 1991 | A |
5274631 | Bhardwaj | Dec 1993 | A |
5321812 | Benedict et al. | Jun 1994 | A |
5343461 | Barton et al. | Aug 1994 | A |
5394522 | Sanchez-Frank et al. | Feb 1995 | A |
5394556 | Oprescu | Feb 1995 | A |
5406643 | Burke et al. | Apr 1995 | A |
5452330 | Goldstein | Sep 1995 | A |
5490250 | Reschke et al. | Feb 1996 | A |
5490253 | Laha et al. | Feb 1996 | A |
5493568 | Sampat et al. | Feb 1996 | A |
5495481 | Duckwall | Feb 1996 | A |
5524254 | Morgan et al. | Jun 1996 | A |
5539390 | Nagano et al. | Jul 1996 | A |
5541670 | Hanai | Jul 1996 | A |
5568487 | Sitbon et al. | Oct 1996 | A |
5568641 | Nelson et al. | Oct 1996 | A |
5583922 | Davis et al. | Dec 1996 | A |
5621659 | Matsumoto et al. | Apr 1997 | A |
5630173 | Oprescu | May 1997 | A |
5632016 | Hoch et al. | May 1997 | A |
5640595 | Baugher et al. | Jun 1997 | A |
5642515 | Jones et al. | Jun 1997 | A |
5654657 | Pearce | Aug 1997 | A |
5684715 | Palmer | Nov 1997 | A |
5701476 | Fenger | Dec 1997 | A |
5701492 | Wadsworth et al. | Dec 1997 | A |
5706278 | Robillard et al. | Jan 1998 | A |
5712834 | Nagano et al. | Jan 1998 | A |
5719862 | Lee et al. | Feb 1998 | A |
5754765 | Danneels et al. | May 1998 | A |
5764930 | Staats | Jun 1998 | A |
5784648 | Duckwall | Jul 1998 | A |
5802048 | Duckwall | Sep 1998 | A |
5802057 | Duckwall et al. | Sep 1998 | A |
5802365 | Kathail et al. | Sep 1998 | A |
5805073 | Nagano et al. | Sep 1998 | A |
5805822 | Long et al. | Sep 1998 | A |
5809331 | Staats et al. | Sep 1998 | A |
5819115 | Hoese et al. | Oct 1998 | A |
5826027 | Pedersen et al. | Oct 1998 | A |
5832298 | Sanchez et al. | Nov 1998 | A |
5835761 | Ishii et al. | Nov 1998 | A |
5854152 | Anderson et al. | Dec 1998 | A |
5867730 | Leyda | Feb 1999 | A |
5875301 | Duckwall et al. | Feb 1999 | A |
5923663 | Bontemps et al. | Jul 1999 | A |
5930480 | Staats | Jul 1999 | A |
5935208 | Duckwall et al. | Aug 1999 | A |
5938764 | Klein | Aug 1999 | A |
5940600 | Staats et al. | Aug 1999 | A |
5954796 | McCarty et al. | Sep 1999 | A |
5968152 | Staats | Oct 1999 | A |
5970052 | Lo et al. | Oct 1999 | A |
5987605 | Hill et al. | Nov 1999 | A |
5991842 | Takayama | Nov 1999 | A |
6006275 | Picazo, Jr. et al. | Dec 1999 | A |
6009480 | Pleso | Dec 1999 | A |
6012084 | Fielding et al. | Jan 2000 | A |
6032202 | Lea et al. | Feb 2000 | A |
6032261 | Hulyalkar | Feb 2000 | A |
6038234 | LaFollette et al. | Mar 2000 | A |
6038625 | Ogino et al. | Mar 2000 | A |
6070187 | Subramaniam et al. | May 2000 | A |
6073206 | Piwonka et al. | Jun 2000 | A |
6091726 | Crivellari et al. | Jul 2000 | A |
6115764 | Chisholm et al. | Sep 2000 | A |
6122248 | Murakoshi et al. | Sep 2000 | A |
6131129 | Ludtke et al. | Oct 2000 | A |
6131134 | Huang et al. | Oct 2000 | A |
6131163 | Wiegel | Oct 2000 | A |
6133938 | James | Oct 2000 | A |
6138163 | Nam et al. | Oct 2000 | A |
6138196 | Takayama et al. | Oct 2000 | A |
6141702 | Ludtke et al. | Oct 2000 | A |
6141767 | Hu et al. | Oct 2000 | A |
6145018 | LaFollette et al. | Nov 2000 | A |
6157972 | Newman et al. | Dec 2000 | A |
6160796 | Zou | Dec 2000 | A |
6167532 | Wisecup | Dec 2000 | A |
6173327 | De Borst et al. | Jan 2001 | B1 |
6188700 | Kato et al. | Feb 2001 | B1 |
6192189 | Fujinami et al. | Feb 2001 | B1 |
6199119 | Duckwall et al. | Mar 2001 | B1 |
6202210 | Ludtke | Mar 2001 | B1 |
6212171 | LaFollette et al. | Apr 2001 | B1 |
6212633 | Levy et al. | Apr 2001 | B1 |
6219697 | Lawande et al. | Apr 2001 | B1 |
6226680 | Boucher et al. | May 2001 | B1 |
6233615 | Van Loo | May 2001 | B1 |
6233624 | Hyder et al. | May 2001 | B1 |
6243778 | Fung et al. | Jun 2001 | B1 |
6247063 | Ichimi et al. | Jun 2001 | B1 |
6247083 | Hake et al. | Jun 2001 | B1 |
6253114 | Takihara | Jun 2001 | B1 |
6253255 | Hyder et al. | Jun 2001 | B1 |
6256059 | Fichtner | Jul 2001 | B1 |
6260063 | Ludtke et al. | Jul 2001 | B1 |
6266334 | Duckwall | Jul 2001 | B1 |
6266344 | Fujimori et al. | Jul 2001 | B1 |
6266701 | Sridhar et al. | Jul 2001 | B1 |
6275889 | Saito | Aug 2001 | B1 |
6282597 | Kawamura | Aug 2001 | B1 |
6292840 | Blomfield-Brown et al. | Sep 2001 | B1 |
6295479 | Shima et al. | Sep 2001 | B1 |
6298057 | Guy et al. | Oct 2001 | B1 |
6308222 | Krueger et al. | Oct 2001 | B1 |
6311228 | Ray | Oct 2001 | B1 |
6314461 | Duckwall et al. | Nov 2001 | B2 |
6343321 | Patki et al. | Jan 2002 | B2 |
6345315 | Mishra | Feb 2002 | B1 |
6347362 | Schoinas et al. | Feb 2002 | B1 |
6353868 | Takayama et al. | Mar 2002 | B1 |
6356558 | Hauck et al. | Mar 2002 | B1 |
6363085 | Samuels | Mar 2002 | B1 |
6373821 | Staats | Apr 2002 | B2 |
6385679 | Duckwall et al. | May 2002 | B1 |
6405247 | Lawande et al. | Jun 2002 | B1 |
6411628 | Hauck et al. | Jun 2002 | B1 |
6418150 | Staats | Jul 2002 | B1 |
6425019 | Tateyama et al. | Jul 2002 | B1 |
6426962 | Cabezas et al. | Jul 2002 | B1 |
6442630 | Takayama et al. | Aug 2002 | B1 |
6445711 | Scheel et al. | Sep 2002 | B1 |
6446116 | Burridge | Sep 2002 | B1 |
6446142 | Shima et al. | Sep 2002 | B1 |
6452975 | Hannah | Sep 2002 | B1 |
6457086 | Duckwall | Sep 2002 | B1 |
6466982 | Ruberg | Oct 2002 | B1 |
6496862 | Akatsu et al. | Dec 2002 | B1 |
6502144 | Accarie | Dec 2002 | B1 |
6513085 | Gugel et al. | Jan 2003 | B1 |
6516465 | Paskins | Feb 2003 | B1 |
6519657 | Stone et al. | Feb 2003 | B1 |
6529522 | Ito et al. | Mar 2003 | B1 |
6574588 | Shapiro et al. | Jun 2003 | B1 |
6587874 | Golla et al. | Jul 2003 | B1 |
6587904 | Hauck et al. | Jul 2003 | B1 |
6591300 | Yurkovic | Jul 2003 | B1 |
6606320 | Nomura et al. | Aug 2003 | B1 |
6618750 | Staats | Sep 2003 | B1 |
6618764 | Shteyn | Sep 2003 | B1 |
6618785 | Whitby-Streves | Sep 2003 | B1 |
6621832 | Staats | Sep 2003 | B2 |
6628607 | Hauck et al. | Sep 2003 | B1 |
6631426 | Staats | Oct 2003 | B1 |
6636914 | Teener | Oct 2003 | B1 |
6639918 | Hauck et al. | Oct 2003 | B1 |
6643714 | Chrysanthakopoulos | Nov 2003 | B1 |
6671768 | Brown | Dec 2003 | B1 |
6686838 | Rezvani et al. | Feb 2004 | B1 |
6691096 | Staats | Feb 2004 | B1 |
6700895 | Kroll | Mar 2004 | B1 |
6711574 | Todd et al. | Mar 2004 | B1 |
6718497 | Whitby-Strevens | Apr 2004 | B1 |
6745256 | Suzuki et al. | Jun 2004 | B2 |
6813663 | Brown | Nov 2004 | B1 |
7032014 | Thiyagarajan et al. | Apr 2006 | B2 |
7191266 | Brown | Mar 2007 | B1 |
20010001151 | Duckwall et al. | May 2001 | A1 |
20010019561 | Staats | Sep 2001 | A1 |
20010024423 | Duckwall et al. | Sep 2001 | A1 |
20020057655 | Staats | May 2002 | A1 |
20020085581 | Hauck et al. | Jul 2002 | A1 |
20020101231 | Staats | Aug 2002 | A1 |
20020101885 | Pogrebinsky et al. | Aug 2002 | A1 |
20020103947 | Duckwall et al. | Aug 2002 | A1 |
20020172226 | Staats | Nov 2002 | A1 |
20020188780 | Duckwall | Dec 2002 | A1 |
20020188783 | Duckwall et al. | Dec 2002 | A1 |
20030037161 | Duckwall et al. | Feb 2003 | A1 |
20030055999 | Duckwall et al. | Mar 2003 | A1 |
20040037309 | Hauck et al. | Feb 2004 | A1 |
20050060391 | Kaminsky et al. | Mar 2005 | A1 |
Number | Date | Country |
---|---|---|
1 805 706 | Mar 2001 | EP |
1 805 706 | Oct 2002 | EP |
Number | Date | Country | |
---|---|---|---|
20070186013 A1 | Aug 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10944265 | Sep 2004 | US |
Child | 11717374 | US | |
Parent | 09432869 | Nov 1999 | US |
Child | 10944265 | US |