The present invention relates generally to telecommunication services and more specifically to a new system and method for home automation and security.
Home automation and security systems currently are controlled by equipment installed at a customer premises. By programming an in-house device, a user controls the operation of appliances connected to the system. For example, a user can program an in-house device to turn on a light at a specific time. The in-house device also can monitor sensors located throughout the house and can sound an alarm or phone a monitoring agency when the sensors are triggered. Some systems offer a remote access feature allowing a user to access the in-house device through the public switched telephone system.
There are several disadvantages associated with conventional home automation and security systems. First, most systems use relatively simple user interfaces that limit the user's control over the system. To provide a more elaborate and friendly user interface, some systems incorporate, or provide a connection to, a device comparable to a personal computer. While these systems provide the user with better home automation and security functionality, their high cost limits their wide-spread use. Additionally, changing built-in control programs typically requires a change to the in-house equipment itself. Further, using the remote-access feature of the conventional systems interferes with normal use of the home telephone.
There is, therefore, a need for a new system and method for home automation and security that will overcome the disadvantages described above.
Now turning to the drawings,
With such redistributed functionality, the network-based structure of this home automation and security system overcomes the disadvantages of conventional home automation and security systems. First, the system described below offers a more intensive computational facility as compared to current systems. Because the computational resources are centralized, updating or replacing control software does not require changes to customer premises equipment. Further, the system has access to external databases, allowing more powerful and versatile forms of home automation and security. Second, this system offers a more sophisticated user interface (such as an elaborate, graphical or speech-based user interface) without requiring the use of a personal computer or comparably powerful and expensive dedicated processor at the customer premises. Third, unlike the remote access feature of a conventional system which typically requires input of touch-tone signals with only tones as prompts, the remote access feature of these preferred embodiments supports user-friendly Interactive Voice Response units and allows users to access their home system using a personal computer. Additionally, because the access line has a data channel separate from the voice channel, the remote access feature of these preferred embodiments does not interfere with normal use of the home telephone.
Referring again to the drawings,
Remotely located from the customer premises 305 is a second data-over-voice modem 335, which is coupled to a central office 340 with a POTS line 343 and a gateway 345 (preferably with a T1 line). The second data-over-voice modem 335 separates the data and voice traffic and sends the signals to the gateway 345 and a line card in the central office 340, respectively. The central office 340 is coupled to the public switched telephone network (“PSTN”) 395. The gateway 345 is coupled with a home automation and security server 350, which comprises a home automation and security application 355, through a data network 360. The data network 360 (which can be SONET with ATM or any other comparable network technology) can comprise any number of computer data network devices or can be a single connection directly coupling the gateway 345 with the server 350. The data network 360 also can couple a speech processing server 390 and an Internet service provider 385 coupled with the Internet 375.
Unlike conventional systems, the controller 310 at the customer premises 305 is responsible for monitoring and applying control signals to devices in the home and for supporting a human interface, while the computational and database resources of the system 300 are provided to the controller 310 (and controllers of other customer premises) by the application 355. It is important to note that controller 310-server 350 communication does not involve the POTS line or the public switched telephone network 395. As described below, even communication with a user in the customer premises 305, whether via dialed digits or a spoken command, is sent as packets over the data channel.
The system 300 of
Additionally, the system 300 of
As mentioned above, the system 300 of
Computational and Database Resources
With conventional systems, in-house devices have limited computational capabilities due to size and cost constraints. In contrast to in-house devices, the server 350 and application 355 of this preferred embodiment offer greater computational and database resources. Additionally, because the application 355 is centralized and is not part of the controller 310, a user is not limited to applications built into the controller 310 and can use applications from third-party vendors that may be better tailored to his needs. Unlike current systems, changing applications does not require change to customer premises equipment. Because the application 355 is centralized, these benefits can be shared by many users.
Because the computational resources of the centralized application server 350 are much larger than those of conventional in-house devices, the home security and automation application 355 can be written to take more intelligent action. For example, suppose that the application 355 is in an armed state and a window is opened at the time of day that children normally return home from school. Rather than immediately raising an alarm, the application 355 can use a speaker in the customer premises 305 to prompt the possible intruder/possible child-without-key to enter a security pass code. The application 355 also can have access to a much more complete database of information about home usage. For example, the application 355 can know that a cleaning service enters the home every Thursday at 1 p.m. If someone unlocks a door and enters at that time but does not enter a pass code, the application 355 would not necessary raise an alarm. The application 355, for example, can call the house and, using an interactive voice response system, prompt the service company personnel to enter his pass code over the telephone 3 15.
As another example, if other residences were equipped with the home automation and security system 300 of
In another application, the application 355 can send messages to the controller 310 to turn on certain devices and activate certain alerting devices 327 in response to receiving an alert (e.g., civil defense warnings and severe weather alerts) from an information source coupled to the data network 360 or the PSTN 395. For example, if the controller 310 receives a “take cover” warning from a weather source because a tornado has been spotted in the vicinity, the controller 310 can turn on all the lights in the house, sound a siren, and broadcast an appropriate spoken message over the home public address system. Additionally, the application 355 can monitor a news channel and announce events in the news that are thought to be of pressing interest to the occupants. For example, a home owner can be told of train or traffic delays, and a family can be told of weather-related school closings.
As described above, the data network 360 can be coupled with larger databases than are available to the conventional home automation and security systems. With access to a larger database, a user has more control over, for example, VCR programming. The application 355 can monitor and track changes in the scheduled time of a program to automatically adjust the VCR programming to ensure that a desired program is recorded. Additionally, the application 355 can provide the user with a better interface through which to program the VCR. With conventional systems, program schedules are sent to a cable box or a specially-equipped television set for display to the user. The user navigates through a typically grid-like display on the television set and selects programs for recording. Because of memory limitations in set-top boxes or the circuitry of specially-equipped television sets, users typically have access to only a few days of program listings, and the listings include only terse descriptions of the programs. In contrast, the application 355 of this preferred embodiment can have access (via the data network 360) to information about many weeks of programming and detailed information about each program.
User Interface
Because the user interface is supported by a centralized server 350, the cost and size of the controller 310 does not limit the user interface, as in conventional systems. Accordingly, the computational resources available to the application 355 of this preferred embodiment can provide a more sophisticated user interface as compared to conventional systems. The system 300 of this preferred embodiment can communicate with a user via an interactive voice session, and because the server 350 can be a larger and more versatile machine than a conventional in-house unit, the dialog can be vastly easier for the user. When the application 355 is aware that it must communicate with the user over a standard telephone, it initiates an interactive voice session. An initial greeting is sent, and the user can respond by either dialing a touchtone digit or by speaking Processing of voice commands can be done by a speech processing server 390 coupled with the data network 360. Using readily-available current technology, the speech processing server 390 can perform speaker-independent recognition or speaker verification.
In the course of the user's interaction with the home automation and security system 300, the user may inquire about the status of devices in the home, issue commands to change device status, or may change the way in which the application 355 responds to reported events. The user's dialog with the application 355 can result in messages being sent to the controller 310. For example, the user can call from a bedside phone to instruct the application 355 to enter a “night mode.” The application 355 then can send a message to the controller 310 instructing it to turn off all lights under its control. A user instruction to enter night mode also can configure the application 355 to immediately respond to reports from in-home sensors 325 that a door or window was opened or that a motion detector was tripped. The nature of a response to an unexpected sensor event can be whatever the user deems appropriate. The application 355 can place a telephone call to the house, turn on house lighting, sound an alarm in the house, or place a call to a monitoring bureau. As described above, the service logic that determines what should be done when an event is detected in the home is in the application server 350. The controller 310 is responsible only for reporting events and sending control signals to devices when instructed to do so.
A user can access the server 350 from within his home using the telephone 315 (e.g., a standard telephone station set 100 shown in
In another embodiment, a user can access the application 355 with his home computer 313. As shown in
In yet another embodiment, a dedicated user interface device 600 (
While the dedicated user interface device 600 and the controller 310 comprise some processing capability, the application 355 in the server 350 is in complete control of the user interface device 600. The application 355 determines what the user will see on the display 610 and hear over the speaker 630. The application 355 interprets all user inputs, button presses, touch-screen contacts and spoken commands. The application 355 can send a complete bit map of the screen or can send a character image showing which of a set of characters (e.g., ASCII characters, extended ASCII drawing characters, and pre-determined icons) should be displayed at a particular location on the display 610. The application 355 also can send a more abstract markup language representation. As is well known in the art, tradeoffs can be made either to conserve bandwidth by sending a higher-level representation or to minimize the need for processing capacity in the dedicated user interface device 600 by sending more literal descriptions of the screen.
The application 355 also can be accessed from a location remote from the customer premises 305. When the user is off premises, he can use an ordinary touchtone telephone to call the application 355. A user can place a telephone call to an access number, which can be routed from the central office 340 directly to the server 350 through a T1 line, for example, or indirectly through the gateway 345. The application 355 can communicate with the user via tone or speech prompts, and user responses can be either dialed touch-tone digits or spoken words. When a telephone is used to remotely access the application 355, a talking path can be established between the remote user and either a specialized voice I/O device in the customer premises 305 (e.g., a loudspeaker and microphone) or the regular home telephone 315. Speech to and from the home can be routed through the data channel of the access line 333 without using a normal telephone connection into the home. In this way, the remote user can talk to someone in the home, and the other home telephones still can be used for normal telephone calls. Additionally, a remote user can use the data channel to monitor activity in the house by receiving signals sent from the microphone of the specialized voice I/O device.
The user also can use a personal computer to remotely access the application. The computer can be coupled to the server 350 over the Internet 375 (or a private data network) or over a dial-up connection through the PSTN 395. In one embodiment, the server 350 functions as a Web server. After entering the server's 350 public home page, the user (after passing through a security check) can go to the page for their home automation and security system. This page can be designed to provide the appropriate status information and controls. In the course of the user's interaction with the application 355, the user can inquire about the status of devices in the home, issue commands to change device status, or change the way in which the application 355 manages home devices or responds to reported events. The application 355 is ultimately responsible for controlling all automated systems in the home. Alternatively, the application 355 can send commands to devices in the home to pre-program them to respond to local events.
In all of the above embodiments, because the application 355 communicates with the controller 310 using a data channel separate from the voice channel, someone on the premises 305 can use the telephone 315 at the same time that the application 355 is exchanging messages with the controller 310. The continuous connectivity access line 333 provides the system with additional advantages, as described below.
The Continuous Connectivity Access Line
The use of a continuous connectivity access line 333 also allows several services to be offered that are unavailable with current systems. For example, the system 300 of
As another feature, the system 300 can maintain a log of customer premises' entries and exits. A remote user can be provided with either real-time notification of changes in the security system status (e.g., the kids are home) or can peruse historical records. Further, cut-line protection can be provided at practically no additional cost because the application 355 will immediately be alerted if the access line becomes inoperable for any reason. The application 355 also can receive immediate notification of loss of residential power and can monitor the status of the backup system.
While the embodiments have been described in reference to a continuous connectivity access line supported by data-over-voice modems, as mentioned above, the access line can also be supported by a digital subscriber line.
It is important to note that while the preferred embodiments were described above in terms of a home automation and security system, these two functions can exist independently. For example, while the home automation and security controller 310 is shown as one element, a system can comprise two controllers—one for home automation and one for home security. Alternatively, a customer premises may only have one controller, functioning as either a home automation controller or a home security controller.
It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a definition of the invention. It is only the following claims, including all equivalents, that are intended to define the scope of this invention.
This patent arises from a continuation of U.S. patent application Ser. No. 13/546,754, filed Jul. 11, 2012, now U.S. Pat. No. 8,922,361, which is a continuation of U.S. patent application Ser. No. 13/250,597, filed on Sep. 30, 2011, now U.S. Pat. No. 8,242,900, which is a continuation of U.S. patent application Ser. No. 12/425,273, filed on Apr. 16, 2009, now U.S. Pat. No. 8,063,761, which is a continuation of U.S. patent application Ser. No. 11/438,265, filed on May 22, 2006, now U.S. Pat. No. 7,551,071, which is a continuation of U.S. patent application Ser. No. 08/999,106, filed on Dec. 29, 1997. U.S. patent application Ser. No. 13/546,754, U.S. patent application Ser. No. 13/250,597, U.S. patent application Ser. No. 12/425,273, U.S. patent application Ser. No. 11/438,265, and U.S. patent application Ser. No. 08/999,106 are hereby incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4021615 | James et al. | May 1977 | A |
4442319 | Treidl | Apr 1984 | A |
4511886 | Rodriguez | Apr 1985 | A |
4540851 | Hashimoto | Sep 1985 | A |
4653085 | Chan et al. | Mar 1987 | A |
4656655 | Hashimoto | Apr 1987 | A |
4658096 | West et al. | Apr 1987 | A |
4683460 | Nakatsugawa | Jul 1987 | A |
4885766 | Yasuoka et al. | Dec 1989 | A |
5086385 | Launey et al. | Feb 1992 | A |
5109407 | Fujita et al. | Apr 1992 | A |
5164982 | Davis | Nov 1992 | A |
5268666 | Michel et al. | Dec 1993 | A |
5287515 | Murai | Feb 1994 | A |
5291479 | Vaziri et al. | Mar 1994 | A |
5311507 | Bedrossian | May 1994 | A |
5349633 | Katz | Sep 1994 | A |
5369700 | Kaura et al. | Nov 1994 | A |
5392345 | Otto | Feb 1995 | A |
5400246 | Wilson et al. | Mar 1995 | A |
5434395 | Storck et al. | Jul 1995 | A |
5461372 | Busak et al. | Oct 1995 | A |
5469496 | Emery et al. | Nov 1995 | A |
5475735 | Williams et al. | Dec 1995 | A |
5479491 | Herrero Garcia et al. | Dec 1995 | A |
5506892 | Kojima et al. | Apr 1996 | A |
5526413 | Cheston, III et al. | Jun 1996 | A |
5528258 | Moon | Jun 1996 | A |
5528666 | Weigand et al. | Jun 1996 | A |
5550649 | Wong et al. | Aug 1996 | A |
5553223 | Greenlee et al. | Sep 1996 | A |
5555258 | Snelling et al. | Sep 1996 | A |
5570085 | Bertsch | Oct 1996 | A |
5572438 | Ehlers et al. | Nov 1996 | A |
5572572 | Kawan et al. | Nov 1996 | A |
5577118 | Sasaki et al. | Nov 1996 | A |
5581593 | Engelke et al. | Dec 1996 | A |
5583920 | Wheeler, Jr. | Dec 1996 | A |
5592538 | Kosowsky et al. | Jan 1997 | A |
5598456 | Feinberg | Jan 1997 | A |
5602837 | Takahashi | Feb 1997 | A |
5603095 | Uola | Feb 1997 | A |
5610910 | Focsaneanu et al. | Mar 1997 | A |
5610972 | Emery et al. | Mar 1997 | A |
5640444 | O'Sullivan | Jun 1997 | A |
5644629 | Chow | Jul 1997 | A |
5664003 | Foladare et al. | Sep 1997 | A |
5742756 | Dillaway et al. | Apr 1998 | A |
5774357 | Hoffberg et al. | Jun 1998 | A |
5917405 | Joao | Jun 1999 | A |
5939980 | Heitmann et al. | Aug 1999 | A |
5971597 | Baldwin et al. | Oct 1999 | A |
6021324 | Sizer, II et al. | Feb 2000 | A |
6032034 | Rabina et al. | Feb 2000 | A |
6058104 | Snelling et al. | May 2000 | A |
6097966 | Hanley | Aug 2000 | A |
6130620 | Pinnow et al. | Oct 2000 | A |
6141356 | Gorman | Oct 2000 | A |
6188895 | Schmitz et al. | Feb 2001 | B1 |
6226368 | Teich et al. | May 2001 | B1 |
6343217 | Borland | Jan 2002 | B1 |
6389292 | Biedermann | May 2002 | B2 |
6470179 | Chow et al. | Oct 2002 | B1 |
6532361 | Kamperschroer | Mar 2003 | B1 |
6542753 | Swenson | Apr 2003 | B1 |
6546253 | Chow et al. | Apr 2003 | B1 |
6556586 | Sipila | Apr 2003 | B1 |
6594488 | Chow et al. | Jul 2003 | B1 |
6625443 | Kamperschroer et al. | Sep 2003 | B1 |
7027566 | Bossemeyer et al. | Apr 2006 | B2 |
7174175 | Uang et al. | Feb 2007 | B2 |
7346682 | Bennett, III | Mar 2008 | B2 |
7349682 | Bennett, III et al. | Mar 2008 | B1 |
7525990 | Bossemeyer et al. | Apr 2009 | B2 |
7596129 | Bossemeyer et al. | Sep 2009 | B2 |
7738872 | Chow et al. | Jun 2010 | B1 |
7912447 | Bennett, III | Mar 2011 | B2 |
8063761 | Bennett, III | Nov 2011 | B2 |
8242900 | Bennett, III | Aug 2012 | B2 |
8922361 | Bennett et al. | Dec 2014 | B2 |
20020037004 | Bossemeyer et al. | Mar 2002 | A1 |
20030027565 | Bossemeyer et al. | Feb 2003 | A1 |
20030206102 | Joao | Nov 2003 | A1 |
20050108091 | Sotak et al. | May 2005 | A1 |
20050109091 | Steinbichler et al. | May 2005 | A1 |
20060140356 | Bossemeyer et al. | Jun 2006 | A1 |
20060220830 | Bennett et al. | Oct 2006 | A1 |
20070127510 | Bossemeyer et al. | Jun 2007 | A1 |
20080074258 | Bennett et al. | Mar 2008 | A1 |
20090201921 | Bossemeyer et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
3529167 | Feb 1987 | DE |
7-103493 | Apr 1995 | JP |
9953654 | Oct 1999 | WO |
Entry |
---|
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Nov. 16, 1998 (5 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Jun. 8, 1999 (5 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Sep. 28, 1999 (5 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Nov. 8, 1999 (12 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Jul. 5, 2000 (10 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Jul. 30, 2003 (10 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Jan. 12, 2005 (5 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Oct. 3, 2005 (2 pages). |
Office Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Oct. 4, 2005 (2 pages). |
Office Action, issued in connection with U.S. Appl. No. 11/438,265, mailed Sep. 28, 2007 (6 pages). |
Office Action, issued in connection with U.S. Appl. No. 11/438,265, mailed Jun. 10, 2008 (5 pages). |
Office Action, issued in connection with U.S. Appl. No. 11/438,265, mailed Jan. 14, 2009 (4 pages). |
Examiner Interview Summary, issued in connection with U.S. Appl. No. 08/999,106, mailed Oct. 24, 2000 (1 page). |
Advisory Action, issued in connection with U.S. Appl. No. 08/999,106, mailed Oct. 26, 2000 (2 pages). |
Office Action, issued in connection with U.S. Appl. No. 13/250,597, mailed on Dec. 8, 2011, (6 pages). |
Notice of Allowance, issued in connection with U.S. Appl. No. 13/250,597, mailed on Apr. 11, 2011 (5 pages). |
Notice of Allowance issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Dec. 12, 2007 (4 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Aug. 15, 2007 (3 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Jun. 7, 2007 (17 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Dec. 4, 2006 (13 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Nov. 30, 2004(18 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Aug. 2, 2001 (12 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on May 18, 2001 (12 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Jan. 10, 2001 (3 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Nov. 22, 2000 (10 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 09/096,560 on Jul. 10, 2000 (7 pages). |
“Computers and Telecomunications—More, Better, Faster, Cheaper,” A Bulletin issued on Sep. 13, 1997 (9 pages). |
AT&T Learning Network, Blueprint of the Technology Diagrams issued, May 27, 1997 (2 pages). |
Lucent Technologies, “Bell Labs Technology, Trends, and Developments,” Apr. 1997 (11 pages). |
Perry Laforge, “What is in a Name?” Column One Article, Aug. 20, 1997 (3 pages). |
The specification, claims, abstract, and figures for U.S. Appl. No. 09/061,833, filed Apr. 16, 1998, and abandoned on Feb. 24, 2003, for failure to respond to an Office action (47 pages). |
The Yankee Group, “Wireless as Access: AT&T Reaches for the Holy Grail,” vol. 14, No. 2 of the Consumer Communications Bulletin issued in Mar. 1997 (5 pages). |
Reitman, AT&T Announces Fixed Wireless Alternative to Local Service, Edge Publishing, Mar. 3, 1997, vol. 12 pp. 1-5. |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 11/952,830 on May 24, 2010 (7 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 11/952,830 on Jul. 22, 2010 (8 pages). |
Office action issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 08/999,106 on Oct. 26, 2000 (3 pages). |
Examiner Interview Summary, issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 08/999,106, mailed Oct. 24, 2000 (1 page). |
Advisory Action, issued by the United States Patent and Trademark Office in connection with U.S. Appl. No. 08/999,106, mailed Oct. 26, 2000 (2 pages). |
Notice of Allowance issued by the United States Patent and Trademark Office on Dec. 30, 2010 in connection with U.S. Appl. No. 11/952,830 (5 pages). |
Notice of Allowance issued by the United States Patent and Trademark Office on Jul. 8, 2011 in connection with U.S. Appl. No. 12/425,273 (7 pages). |
Office Action issued by the United States Patent and Trademark Office on Jan. 3, 2011 in connection with U.S. Appl. No. 12/425,273 (5 pages). |
Office Action issued by the United States Patent and Trademark Office on Sep. 20, 2010 in connection with U.S. Appl. No. 12/425,273 (5 pages). |
Office Action issued by the United States Patent and Trademark Office on Sep. 13, 2012 in connection with U.S. Appl. No. 13/546,754 (9 pages). |
Office Action issued by the United States Patent and Trademark Office on May 7, 2013 in connection with U.S. Appl. No. 13/546,754 (34 pages). |
Office Action issued by the United States Patent and Trademark Office on Aug. 15, 2013 in connection with U.S. Appl. No. 13/546,754 (13 pages). |
Office Action issued by the United States Patent and Trademark Office on Jan. 31, 2014 in connection with U.S. Appl. No. 13/546,754 (8 pages). |
Notice of Allowance issued by the United States Patent and Trademark Office on Aug. 20, 2014 in connection with U.S. Appl. No. 13/546,754 (9 pages). |
Number | Date | Country | |
---|---|---|---|
20150070163 A1 | Mar 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13546754 | Jul 2012 | US |
Child | 14549539 | US | |
Parent | 13250597 | Sep 2011 | US |
Child | 13546754 | US | |
Parent | 12425273 | Apr 2009 | US |
Child | 13250597 | US | |
Parent | 11438265 | May 2006 | US |
Child | 12425273 | US | |
Parent | 08999106 | Dec 1997 | US |
Child | 11438265 | US |