Touch screen devices, and in particular touch screen cell phones, have grown in popularity over the past few years because they enable a user to interact directly with content displayed on the display, rather than through an intermediary, such as a hardware QWERTY keyboard. Touch screen devices generally comprise software keys (e.g., icons displayed on the display) and touch sensors, integrated into the display, that detect the presence and location of a user's touch within the display. Software correlates the location of the touch to an icon displayed in the vicinity of the touch to determine what a user intended to select.
Several manufacturers of touch screen devices have opted to eliminate or substantially reduce the number of hardware keys integrated into touch screen devices. Instead, manufacturers create software keys that may be selectively displayed on the screen (e.g., when user input is desired). There are several advantages to reducing the number of hardware keys, particularly for manufacturers of cell phones and other small handheld devices. For example, manufacturers may be able to offer devices that are more sleek (e.g., relative to bulkier devices that may have a full, hardware QWERTY keyboard) and/or have a larger screen (e.g., because available space is not consumed by hardware keys). Manufacturers may also reduce the cost of producing the device because less hardware components are needed. Additionally, consumers may benefit because the cost of the device may be cheaper and the software keys may offer more flexibility with regards to key arrangement (e.g., users may switch between a numerical keyboard, a full QWERTY keyboard, a compact QWERTY, and since they generally comprise icons on a touch sensitive screen, software keys may be added, subtracted, resized, rearranged, reconfigured with different functionality, etc.) than hardware keys. Also, there may be fewer software key failures relative to hardware key failures (e.g., buttons becoming corroded and/or stuck), thus prolonging the useful life of the device.
While there are numerous benefits to software keys, there are also several disadvantages that have discouraged some consumers from purchasing touch screen devices that predominately rely on software keys for user input. For example, the development of software keys lags behind hardware keys. Therefore, touch screen devices still have some difficulty in determining the precise location of the user's touch on the display (e.g., causing a key other than the user's intended key to be selected). Additionally users that use the device primarily for text messaging and/or email, such as enterprise users, tend to prefer hardware keys that provide haptic feedback over software keys that do not provide a sense of touch. Some users also prefer hardware keys because software keys take up valuable display space that could display other content, such as a larger portion of an email the user is typing, for example. Therefore, the potential markets for touch screen devices that utilize software keys may be limited.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
As provided herein, a protective shroud may be configured to enclose a portion of a handheld device. In this way, the protective shroud may provide protection to the handheld device against incidents (e.g., drops, scratches, etc.) that commonly cause damage to the device. The protective shroud may be selectively removed from the handheld device when a user does not want the protective shroud to enclose the handheld device, for example.
An input component (e.g., keyboard, mouse, etc.), integral with the protective shroud (e.g., physically attached or embedded), may be configured to receive user input from which a signal is generated and transmitted from the protective shroud to the handheld device through a wireless transceiver and/or an electrically operable contact point connecting the input component to the handheld device.
A wireless transceiver, integral with the protective shroud, may be configured to transmit a signal from the one or more components integral to the protective shroud (e.g., the input component, a sound transceiver, a storage device, etc.) to the handheld device. Similarly, the wireless transceiver allows signals (e.g., from the handheld device) to be received by the protective shroud. In this way, effective communication can be maintained between the handheld device and the protective shroud when the protective shroud is removed or otherwise physically decoupled from the handheld device.
To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects may be employed. Other aspects, advantages, and novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings.
The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, structures and devices are illustrated in block diagram form in order to facilitate describing the claimed subject matter.
The system 100 also comprises a protective shroud 104. The protective shroud 104 is configured to enclose at least a portion of the handheld device 102, when it is attached or otherwise physically coupled to the device 102. In this way, the protective shroud 104 is configured to provide protection for the device 102 from incidents (e.g., drops, scratches, liquids, etc.) that may ordinarily cause damage to the handheld device 102 if the device 102 is otherwise not protected. It will be appreciated that the percentage of surface area of the handheld device 102 that is enclosed by the protective shroud 104 may vary to allow a user to interact with the device 102. For example, a display screen of the device 102 may not be enclosed by the protective shroud 104 so the user can interact directly with the display screen, such as might occur on a touch screen cellular telephone, for example.
The appearance of the protective shroud 104 (e.g. the material used, the color of the protective shroud 104, etc.) may be a function of utility and/or aesthetic appeal. In one embodiment, the material (e.g., leather, plastic, acrylic, silicone, etc.) of the protective shroud 104 may depend upon the type(s) of incidents the protective shroud 104 is designed to protect against. For example, a protective shroud configured to protect the handheld device 102 from a ten foot fall may comprise a high-impact plastic material, whereas a protective shroud configured to protect the handheld device 102 from rubbing against coins (e.g., preventing scratches), when the device 102 is stored in a user's pocket, may comprise silicone. Consumer demand may also dictate the appearance of the protective shroud. For example, consumer's may prefer a black leather protective shroud because it looks more professional, or consumer's may prefer a silicone protective shroud because the protective shroud may be very thin. In this way, protective shroud's having a plurality of different appearances may be produced (e.g., allowing the protective shroud 104 to be more personalized to a user's interests relative to a protective shroud that is only available in one design).
The protective shroud 104 is also configured to be selectively removable from the handheld device 102. That is, the protective shroud 104 is configured so that it may be physically detached from the handheld device 102. It will be appreciated that the protective shroud 104 may not offer protection to the handheld device 102 when the protective shroud 104 is not physically attached to the handheld device 102. The means by which the protective shroud 104 is attached and/or detached to the device 102 may vary depending upon the composition of the protective shroud 104 (e.g., the material used), the incidents that shroud 104 is intended to offer protection against, the type of handheld device 102 the protective shroud 104 is configured to enclose, etc. For example, the protective shroud 104 may be configured to stretch so that the handheld device 102 may slip into and out of the protective shroud 104. In another example, the protective shroud 104 comprises a hook and latch 118 mechanism, wherein the protective shroud 104 opens when that latching mechanism is unlatched, so that the device 102 may be put into and taken out of the shroud 104.
An input component 106 may be integral with (e.g., embedded in or physically attached to a surface of) the protective shroud 104. In this way, the input component 106 may remain physically attached to the protective shroud 104 when the protective shroud 104 is detached from the handheld device 102. That is, the input component 106 may not be in close physical proximity to (e.g., physically touching) the handheld device 102 except when the handheld device 102 is enclosed in the protective shroud 104.
The input component 106 is configured to receive user input from a user 107. The input component 106 may comprise an alphanumeric keypad (e.g., a full QWERTY keypad, compact QWERTY keypad, numerical keypad, etc.), a touch sensitive surface (e.g., a touchpad, a handwriting input component, etc.), a game controller, and/or other input mechanism, and the input may be received when the user 107 touches a particular location or key on the input mechanism, for example.
The input component 106 may also be configured to generate an input signal based upon the received user input. This signal may be transmitted to the handheld device 102, wherein the handheld device 102 translates the input signal into a usable format (e.g., assisting the handheld device 102 in generating a user specified text message or email, to initialize a program, etc.). In one embodiment, the input signal is transmitted to the handheld device 102 through an electrically operable contact point, such as a mini-USB cable or other transmission cable that operably connects the input component 106 to the handheld device 102. In another embodiment, the input signal generated by the input component 106 is transmitted to the handheld device 102 wirelessly (e.g., where both the protective shroud 104 and the handheld device 102 comprise transceivers capable of sending and receiving signals through a wireless protocol).
The input component 106 may comprise one or more user programmable portions. That is, the user 107 may designate a function that may be executed when a particular portion of the input component 106 is touched and/or selected (e.g., where the designation is stored by the input component 106 and/or a portion of the handheld device 102 that translates the signal into a usable format). For example, the user 107 may designate that a “Return” key on the input component 106 activates a recording mechanism on the handheld device 102 when it is selected (e.g., so that the user 107 can record an address that is being spoken to him/her during a phone conversation). In this way, portions of the input component 106 may be personalized based upon the user's preferences.
In one embodiment, the input component 106 comprises one or more touch sensors (e.g., embedded into the input component 106). The touch sensor(s) may be similar to touch sensors used in a touch screen device (e.g., resistive, capacitive, etc.). In this way, the input component 106 may comprise a solid surface, for example, so that debris and/or dust particles are unable to get behind keys. Additionally, the input component 106 may have an uneven or non-uniform surface (e.g., with brail and/or a raised border surrounding each key) so that the user 107 can differentiate between keys.
In another embodiment, the input component 106 comprises one or more mechanical keys. It will be appreciated that the terms “mechanical keys” is used herein in a broad sense to describe keys that are selected when a user physically presses down on the keys. Generally, mechanical keys comprise a spring, or other mechanism, that causes a selected key to return to its position prior to being selected by the user 107.
It will be appreciated that the input component 106 may comprise a material similar to the protective shroud 104 and/or it may be comprised of a different material. For example, where the protective shroud 104 is comprised of a material that may also be used for mechanical keys (e.g., silicon, polyester film, hard plastic, etc.) the input component 106 and the protective shroud 104 may comprise similar materials. However, where the protective shroud 104 comprises leather, for example, the input component 106 may comprise a different material because it may be difficult to make mechanical keys that are both small and leather bound and/or it may be difficult to embed touch sensors in leather, for example.
A wireless transceiver 108 may be integral with (e.g., embedded in or physically attached to) the protective shroud 104. The wireless transceiver 108 is configured to facilitate selective wireless communications with the handheld device 102 (e.g., wherein the handheld device 102 comprises a wireless transceiver). That is, the wireless transceiver 108 may be configured to send signals to the handheld device 102 and/or receive signals from the handheld device 102. For example, the wireless transceiver 108 may be configured to receive input signals from the input component 106 and transmit the received signals to the handheld device 102. In one example, the wireless transceiver 108 communicates with the handheld device 102 through IEEE Standard 802.15.1 protocol (e.g., Bluetooth®). However, it will be appreciated that other protocols, such as IEEE Standard 802.11, for example, are also contemplated.
It will be appreciated that other components may also be integral to the protective shroud. For example, a sound transceiver 110 may be integral to the protective shroud 104. The sound transceiver 110 may comprise a microphone configured to detect sound waves (e.g., emitted by the user 107) and generate detection signals. The sound transceiver 110 may then transmit the detection signals to the handheld device 102 through the wireless transceiver 108 and/or a contact point (e.g., a mini-USB or other transmission cable) configured to operably couple the sound transceiver 110 to the handheld device 102. The sound transceiver 110 may additionally or instead of, comprise a speaker configured to receive emission signals from the handheld device 102, through the wireless transceiver 108 and/or an electrically operable contract point, and emit sound waves. In another example, a storage device 112 (e.g., a flash drive) configured to store data may be integral to the protective shroud 104. The storage device 112 may be operably coupled to the handheld device 102 through the wireless transceiver 108 and/or a contact point. In this way, the storage device 112 may provide storage capacity for the handheld device 102 (e.g., a cellular telephone), for example. In yet another example, a computer processing unit (CPU) may be integral to the protective shroud 104. The CPU may be operably coupled to the handheld device 102 through a contact point, for example, that may be configured to perform operations that are unable to be performed by the handheld device 102, for example (e.g., the CPU additive with a handheld device's capabilities).
It will be understood to those skilled in the art that the wireless transceiver 108 may provide a mechanism to operably couple components integral to the protective shroud 104 (e.g., the sound transceiver 110, input component 106, etc.) with devices other than the handheld device 102 (e.g., a second device 116) when the components are not operably coupled to the handheld device 102. For example, if a television is capable of receiving and/or sending signals wirelessly, the wireless transceiver 108 may be operably coupled to the television, and the input component 106 may be used as remote control.
A power source 114 may be configured to supply power to the input component 106, the wireless transceiver 108, and/or other components integral to the protective shroud 104. In the exemplary system 100, the power source 114 (e.g., a battery) is integral to the protective shroud 104. That is, the power source is embedded in and/or physically attached to the protective shroud 104. In this way, the power source 114 may continue to supply power to the input component 106, the wireless transceiver 108 and/or other components integral to the protective shroud 104 when the protective shroud 104 is not physically attached to the handheld device 102.
It will be appreciated that if the power source 114 is integral to the protective shroud 104, the power source 114 may also be configured to supply power to the handheld device 102 through an electrically operable contact point (e.g., a mini-USB cable or other power transmission conduit) configured to operably couple the power source 114 to the handheld device 102. For example, a battery embedded in the protective shroud 104 may serve as a backup battery for a cellular telephone if the main battery for the cellular telephone (e.g., integral to the handheld device) is not charged.
In another embodiment, the power source 114 is integral to the handheld device 102. That is, the main battery for a cellular phone, for example, may supply power to the input component 106, the wireless transceiver 108, and/or other components integral to the protective shroud 104 through a contact point operably coupling the power source 114 to one or more components integral to the protective shroud that consumer power.
It will be understood to those skilled in the art that other components commonly placed on protective shrouds for handheld devices may also be physical attached to the protective shroud 104 herein described. For example, the protective shroud 104 may comprise a belt clip and/or a wrist strap. In another example, the protective shroud 104 comprises a stand 120 configured to support the handheld device 102 in a vertical position.
An input component (e.g., 106 in
It will be appreciated that
Various operations of embodiments are provided herein. The order in which some or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated by one skilled in the art having the benefit of this description. Further, it will be understood that not all operations are necessarily present in each embodiment provided herein.
Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims may generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”
This application is a continuation of U.S. patent application Ser. No. 13/540,558, filed on Jul. 2, 2012, entitled “Protective Shroud for Handheld Device,” which is a continuation of Ser. No. 12/394,852, filed on Feb. 27, 2009, entitled “Protective Shroud for Handheld Device,” now U.S. Pat. No. 8,229,509, all of which are hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
6168331 | Vann | Jan 2001 | B1 |
6266241 | Van Brocklin | Jul 2001 | B1 |
6456487 | Hetterick | Sep 2002 | B1 |
6477274 | Kim | Nov 2002 | B1 |
6480377 | Genest et al. | Nov 2002 | B2 |
6671170 | Webb et al. | Dec 2003 | B2 |
6693626 | Rosenberg | Feb 2004 | B1 |
6976799 | Kim et al. | Dec 2005 | B2 |
7002553 | Shkolnikov | Feb 2006 | B2 |
7102614 | Sandbach et al. | Sep 2006 | B2 |
7203467 | Siddiqui | Apr 2007 | B2 |
7286860 | Harris | Oct 2007 | B2 |
7289083 | Canova, Jr. | Oct 2007 | B1 |
7327255 | Kassiedass | Feb 2008 | B2 |
7479902 | Wang et al. | Jan 2009 | B2 |
7535459 | You et al. | May 2009 | B2 |
7612997 | Diebel et al. | Nov 2009 | B1 |
8522965 | Hsiung | Sep 2013 | B1 |
9621214 | Paek et al. | Apr 2017 | B2 |
20010011995 | Hinkley et al. | Aug 2001 | A1 |
20020039922 | Nelson | Apr 2002 | A1 |
20030025674 | Watanabe | Feb 2003 | A1 |
20030027517 | Callway | Feb 2003 | A1 |
20030100338 | Lee | May 2003 | A1 |
20030186746 | Chuang | Oct 2003 | A1 |
20040097256 | Kujawski | May 2004 | A1 |
20040136149 | Wang | Jul 2004 | A1 |
20040178989 | Shahoian et al. | Sep 2004 | A1 |
20040203486 | Shepherd et al. | Oct 2004 | A1 |
20050125083 | Kiko | Jun 2005 | A1 |
20060003709 | Wood | Jan 2006 | A1 |
20060279924 | Richardson et al. | Dec 2006 | A1 |
20070008118 | Kassiedass | Jan 2007 | A1 |
20070097014 | Solomon | May 2007 | A1 |
20070173197 | Hsuing | Jul 2007 | A1 |
20080063456 | Lahr | Mar 2008 | A1 |
20080096620 | Lee et al. | Apr 2008 | A1 |
20080123287 | Rossell et al. | May 2008 | A1 |
20080136716 | Annamaa et al. | Jun 2008 | A1 |
20080146206 | Pichardo et al. | Jun 2008 | A1 |
20080225006 | Ennadi | Sep 2008 | A1 |
20080246731 | Chechelniker | Oct 2008 | A1 |
20080263363 | Jueneman et al. | Oct 2008 | A1 |
20080300013 | Raines et al. | Dec 2008 | A1 |
20090027346 | Srivastava | Jan 2009 | A1 |
20090120980 | Calayo | May 2009 | A1 |
20090124308 | Lee | May 2009 | A1 |
20100039388 | Ku | Feb 2010 | A1 |
20100039764 | Locker et al. | Feb 2010 | A1 |
20100079379 | Demuynck et al. | Apr 2010 | A1 |
20110222109 | Yamagishi | Sep 2011 | A1 |
Number | Date | Country |
---|---|---|
2602549 | Feb 2004 | CN |
1527569 | Sep 2004 | CN |
201114710 | Sep 2008 | CN |
201185725 | Jan 2009 | CN |
0852356 | Jul 1998 | EP |
1130245 | Sep 1989 | JP |
06-301447 | Oct 1994 | JP |
H11146049 | May 1999 | JP |
2006-502471 | Jan 2000 | JP |
2000-253122 | Sep 2000 | JP |
2001-100892 | Apr 2001 | JP |
2001-147745 | May 2001 | JP |
2001-154990 | Jun 2001 | JP |
2002-0149312 | May 2002 | JP |
2002-287862 | Oct 2002 | JP |
2002-366284 | Dec 2002 | JP |
2003-058278 | Feb 2003 | JP |
2003-290553 | Oct 2003 | JP |
2004-180093 | Jun 2004 | JP |
2004-336140 | Nov 2004 | JP |
2005-079607 | Mar 2005 | JP |
2008-022191 | Jan 2008 | JP |
2008-096620 | Apr 2008 | JP |
2009267490 | Nov 2009 | JP |
1020070001529 | Jan 2007 | KR |
1020080094779 | Oct 2008 | KR |
1020080100312 | Nov 2008 | KR |
WO 9749040 | Dec 1997 | WO |
WO 0175572 | Apr 2002 | WO |
WO 2004017613 | Feb 2004 | WO |
Entry |
---|
Office Action (w/English translation) received in Japanese Patent Application No. 2014-180974, dated Mar. 22, 2016, 4 pages. |
Smith, “HP's Slim Keyboard for the HP iPAQ,” pocketnow, dated Jun. 18, 2003, 9 pages. http://pocketnow.com/review/hps-slim-keyboard-for-the-hp-ipaq. |
“Bluetooth Frog Pad,” 1999-2006 Frogpad, Inc., Dec. 29, 2008, 2 pages. http://www.frogpad.com/information/bluefroginfo.asp. |
“Folding Keyboard for Phones and PDAs,” Reed Business Information, dated Jun. 24, 2003, 1 page. http://www.ferret.com.au/c/Targus-Australia/Folding-keyboard-for-phones-and-PDAs-n692237. |
Lee, Nicole, “Verizon Wireless goes official with the LG Versa,” clnet, dated Feb. 25, 2009, pp. 1-3. http://news.cnet.com/8301-17938_105-10172497-1.html?part=rss&tag=feed&subj=Crave. |
International Search Report received in related PCT Application No. PCT/US2010/02359, dated Dec. 7, 2010, 9 pages. |
First Office Action received in related Chinese Application No. 201080009733.1, (w/English Translation) dated Jun. 11, 2012, 8 pages. |
Second Office Action, received in related Chinese application No. 201080009733.1, (w/English Translation) dated Aug. 27, 2012, 10 pages. |
International Preliminary Report on Patentability received in PCT Application No. PCT/US2010/023259 dated Aug. 30, 2011, 5 pages. |
Third Chinese Office Action received in Chinese Application No. 201080009733.1 (w/English Translation) dated Nov. 5, 2012, 8 pages. |
Final Chinese Office Action received in Chinese Application No. 201080009733.1 (w/English Translation) dated Apr. 7, 2013, 8 pages. |
EP Search Report received in EP Application No. 10746620.3, dated Jun. 13, 2012, 2 pages. |
EP Communication received in EP Application No. 10746620.3, dated Jul. 12, 2012, 1 page. |
Japanese Office action received in Japanese Application No. 2011-552061, (w/English Translation) dated Jun. 25, 2013, 8 pages. |
Japanese Office Action received in Japanese Application No. 2011-552061,(w/English Translation) dated Mar. 11, 2014, 6 pages. |
Japanese Notice of Allowance (w/translated allowed claims) received in Japanese Application No. 2011-552061, dated Jul. 8, 2014, 7 pages. |
First Chinese Office Action received in Chinese Application No. 201310003712.4, (w/English Translation) dated Jul. 29, 2014, 15 pages. |
Second Chinese Office Action with English translation received in Chinese Patent Application No. 201310003712.4, dated Jan. 5, 2015, 16 pages. |
Korea Office Action, received in related Korea Patent Application No. 10-2011-7019778 (w/English Translation), dated Dec. 15, 2015, 11 pages. |
Japanese Office Action, received in Japan Application No. 2014-180974 (w/English translation), dated Jun. 23, 2015, 12 pages. |
Saito, “Why the Nintendo DS sells well—Gamenics changes the interface,” Shuwa System Co., Ltd, Aug. 1, 2007, first edition, pp. 56-57 (in Japanese). |
Canada Office Action, received in counterpart Canadian Application No. 2749676, dated Feb. 23, 2016, 4 pages. |
“User's Guide diNovo Mini Keyboard,” retrieved from: http://download01.logitech.com/web/ftp/pub/pdf/keyboards/diNovo_productguide_eng-fre.pdf, Jan. 5, 2008, 42 pages. |
“User Guide Palm® Wireless Keyboard with Bluetooth® Wireless Technology,” retrieved from: http://www.hpwebos.com/us/support/handboods/btwk/btwk_ug_en.pdf, 2006, 40 pages. |
“ThinkOutside Stowaway Universal Bluetooth Keyboard Review,” retrieved from: https://www.youtube.com/watch?v=awJyCPt1NOI, Dec. 28, 2004, 2 pages. |
Notice of Allowance with translated allowed claims received in Japanese counterpart application No. 2014-180974, dated Jul. 12, 2016, 7 pages. |
Office Action received in counterpart Canadian Patent Application No. 2,749,676, dated Sep. 20, 2016, 5 pages. |
Number | Date | Country | |
---|---|---|---|
20160191100 A1 | Jun 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13540558 | Jul 2012 | US |
Child | 14984887 | US | |
Parent | 12394852 | Feb 2009 | US |
Child | 13540558 | US |