The present disclosure generally relates to removable component systems, including removable component systems that may be used in connection with vehicles.
This background description is set forth below for the purpose of providing context only. Therefore, any aspect of this background description, to the extent that it does not otherwise qualify as prior art, is neither expressly nor impliedly admitted as prior art against the instant disclosure.
Some systems are not configured for removable components and/or for communicating effectively and efficiently with removable components.
There is a desire for solutions/options that minimize or eliminate one or more challenges or shortcomings of removable component systems. The foregoing discussion is intended only to illustrate examples of the present field and is not a disavowal of scope.
In embodiments, a removable component system may include a removable component selectively connectable to a mounting surface and including a component electrical unit; an antenna; a system controller configured to communicate with the component electrical unit and the antenna; and/or a track assembly configured to be fixed to said mounting surface. The removable component may be selectively connectable to said mounting surface via the track assembly. The removable component may be configured for selective connection with, removal from, and movement (e.g., sliding) along the track assembly. The system controller may be configured to obtain a position of the removable component relative to said mounting surface via the antenna and the component electrical unit (e.g., via a component controller, a sensor, and/or a communication device thereof).
With embodiments, a vehicle may include a vehicle controller configured to control operation (e.g., propulsion) of the vehicle and a removable component system. A mounting surface may include a floor of the vehicle. The removable component may be configured as a vehicle seat. The system controller may be configured to communicate with and/or may be incorporated with the vehicle controller.
In embodiments, a method of operating a removable component system may include obtaining the position and the orientation of a removable component, obtaining information about any child seats in the removable component system, creating a system model of the removable component system, obtaining crash information, and/or controlling one or more safety devices according to the position of the removable component, the orientation or the removable component, the crash information, and the information about any child seats. The system model may include models of the removable component, the one or more safety devices, and/or a mounting surface.
The foregoing and other potential aspects, features, details, utilities, and/or advantages of examples/embodiments of the present disclosure will be apparent from reading the following description, and from reviewing the accompanying drawings.
While the claims are not limited to a specific illustration, an appreciation of various aspects may be gained through a discussion of various examples. The drawings are not necessarily to scale, and certain features may be exaggerated or hidden to better illustrate and explain an innovative aspect of an example. Further, the exemplary illustrations described herein are not exhaustive or otherwise limiting, and are not restricted to the precise form and configuration shown in the drawings or disclosed in the following detailed description. Exemplary illustrations are described in detail by referring to the drawings as follows:
Reference will now be made in detail to embodiments of the present disclosure, examples of which are described herein and illustrated in the accompanying drawings. While the present disclosure will be described in conjunction with embodiments and/or examples, they do not limit the present disclosure to these embodiments and/or examples. On the contrary, the present disclosure covers alternatives, modifications, and equivalents.
In embodiments, such as generally illustrated in
With embodiments, a system electrical unit 22 may include one or more of a variety of configurations. For example and without limitation, and as generally illustrated in
With examples, such as generally illustrated in
With embodiments, such as generally illustrated in
With embodiments, such as generally illustrated in
In embodiments, a track/rail assembly 40 may include one or more tracks/rails 42 that may be connected (e.g., fixed) to the mounting surface 26. The one or more tracks/rails 42 may, for example and without limitation, extend generally in a longitudinal direction (e.g., an X-direction) of the mounting surface 26, may be disposed in parallel with each other, and/or may be offset from each other, such as in a lateral direction (e.g., a Y-direction). A power source 36 may be connected to the track/rail assembly 40 and/or may provide power to one or more tracks/rails 42 of the track/rail assembly 40 (see, e.g.,
In examples, it may be desirable to provide information from and/or about a removable component 24 to the system controller 30 and/or to provide commands from the system controller 30 to a component 24. For example and without limitation, it may be desirable to provide occupancy and/or seatbelt status information of the one or more components 24 to the system controller 30. With some embodiments, the one or more components 24 and the system controller 30 may be configured for wireless communication, such as via respective communication devices 32, 54.
With examples, such as generally illustrated in
In embodiments, an orientation of a removable component 24 may, for instance, include directed/facing forward, directed/facing rearward, disposed at an angle (e.g., in an X-Y plane) relative to the mounting surface 26, such as an oblique or right angle relative to an X-direction of the mounting surface 26 if the removable component 24 is not facing forward or rearward.
With embodiments, a removable component system 20 may be configured to determine positions and/or orientations of removable components 24 via one or more methods in addition to or instead of RSSI. For example and without limitation, the removable component system 20 may be configured to utilize global positioning system (GPS) devices 70 associated with one or more removable components 24, time-of-flight determinations (e.g., via communication devices 32, 54), angle-of-arrival determinations (e.g., via communication devices 32, 54), encoder features 72 of the track assembly 40 (e.g., metal formations, colors, barcodes, etc.) and corresponding encoder sensors 74, orientation sensors 76 (e.g., gyroscopes, accelerometers, magnetometers, etc.), and/or different voltages provided to the track assembly 40 (e.g., via the power source 36), among other methods.
With embodiments, a removable component 24 may be configured for selective connection (e.g., electrical and/or mechanical connection) with the mounting surface 26 in a plurality of orientations/configurations. The plurality of configurations may include a first configuration facing a first direction (see, e.g., removable components 244-246 of
In embodiments, a removable component system 20 may include one or more child seats 96 (e.g., a car seat for a child) that may be configured as or connected to a removable component 24. A system controller 30 and/or a component controller 52 may be configured to determine the position and/or orientation of a child seat 96, such as via a sensor 60 that may be included with a removable component 24 or the child seat 96, an antenna 34 and a communication device 54 of the removable component 24 or the child seat 96 (e.g., as described above), and/or via a sensor 98 of the mounting surface 26 and/or a vehicle 28. The sensor 98 may, for example and without limitation, include a camera, which may include one or more of a variety of image and/or video capturing devices.
In examples, a removable component system 20 may be configured to control one or more devices in the removable component system 20. For example and without limitation, the system controller 30 and/or a component controller 52 may be configured to control one or more safety devices, such as a safety device 56 of a removable component 24 and/or a safety device 80 associated with the mounting surface 26 and/or a vehicle 28 (e.g., a vehicle safety device), and/or may be configured to control an actuator 58 of a removable component 24. Controlling a safety device 56, 80 may include determining whether to activate a safety device according to, at least in part, the position, the orientation, and/or the occupancy status of the removable component 24. For example and without limitation, a system controller 30 and/or a component controller 52 may not activate a safety device 56 of a removable component 24 if the removable component 24 is not occupied (e.g., as determined via an occupancy sensor 60A) and/or may not activate a safety device 80 if an occupied removable component 24 is not disposed proximate the safety device 80, such as to limit waste (e.g., some safety devices may only be used one time before replacement may be needed). Safety devices 80 of a mounting surface 26 and/or vehicle 28 may, for example and without limitation, include airbags, such as curtain airbags, and/or may be disposed in a fixed manner relative to the mounting surface 26 (e.g., may be fixed to the vehicle 28).
In embodiments, a system controller 30 and/or a component controller 52 may each include a single controller (e.g., that performs all functions) or may include a plurality of controllers that may each perform at least some different functions. For example and without limitation, a system controller 30 may include a first controller 30A that may monitor, determine, and/or control position and/or orientation of one or more removable components 24 (see, e.g.,
With embodiments, a removable component system 20 may be configured to determine which safety devices 56, 80 to activate in the event of a crash or imminent crash. For example, a vehicle controller 90 may obtain crash information, such as from one or more crash sensors 82 (e.g., accelerometers, sensors of other vehicles, GPS sensors, etc.), and may provide the crash information to the system controller 30, which may provide the crash information or related information (e.g., trigger signals) to one or more component electrical units 50 and/or component controllers 52 thereof. The system controller 30 and/or component controllers 52 may be configured to activate safety devices 56, 80 of or proximate certain removable components 24. For example, the system controller 30 may activate safety devices 80 of a vehicle 28 that are proximate removable components 24 that include occupied seats and/or respective component controllers 52 may activate one or more respective safety devices 56 of removable components 24.
In embodiments, a system controller 30 and/or a component controller 52 may obtain and/or include information about the size and/or shape of an activated safety device 56, 80. The system controller 30 and/or a component controller 52 may use such information and/or the crash information (e.g., a direction of impact) to determine if the activated safety device 56, 80 would be sufficiently close to an occupant 100 that activating the safety device 56, 80 would improve the safety (e.g., help restrain movement) of the occupant 100 during the crash. For example, if the activated safety is expected to overlap with the current position of the occupant 100 or expected movement of the occupant 100 during the crash, the system controller 30 and/or the component controller 52 may activate the safety device 56, 80. Additionally or alternatively, the system controller 30 and/or a component controller 52 may determine if a removable component 24 and/or an occupant 100 thereof is too close to a safety device 56, 80 for the safety device 56, 80 to be deployed in a safe manner, and may not activate the safety device 56, 80 if the removable component 24 or occupant 100 is too close.
In embodiments, a system controller 30 and/or a component controller 52 may be configured to determine whether to activate one or more safety devices 56 that may be connected to and/or included with a removable component 24. A system controller 30 and/or a component controller 52 may be configured to activate some or all safety devices 56 of a removable component 24 if the removable component 24 is a seat and is occupied by a user/occupant 100 (e.g., as determined via an occupancy sensor 60A). Additionally or alternatively, a component controller 52 and/or the system controller 30 may determine if activation of one or more safety devices 56 of a removable component 24 may impact other removable components 24, such as adjacent or nearby removable components 24. For example, if the system controller 30 and/or a component controller 52 determines that a safety device 56 of a removable component 24, when activated, is expected to contact another removable component 24 or an occupant 100 thereof (e.g., via a determination of the position of the other removable component 24 and information about the safety device 56), the component controller 52 and/or the system controller 30 may determine if the safety device 56, when activated, would be too close to the other removable component(s) 24 or a child seat 96 or occupant 100 associated therewith. If the safety device 56, when activated, would be too close to another removable component 24 or a child seat 96 or an occupant 100 associated therewith, the system controller 30 and/or the component controller 52 may not activate that safety device 56.
With embodiments, a system controller 30 and/or a component controller 52 may determine if safety devices 56 of other removable components 24 are sufficiently close to a certain removable component 24 such that safety devices 56 of the other removable components 24 could be activated to improve the safety of the occupant 100 of the certain removable component 24, which may supplement safety devices 56, if any, of the certain removable component 24. A system controller 30 and/or a component controller 52 may activate such safety devices 56 of other removable components 24 in the event of a crash or imminent crash, such as if such activation would not reduce the safety of the occupant(s) 100 of the other removable component(s) 24.
With examples, a removable component system 20 may be configured to determine the position/orientation of a plurality of removable components 24 relative to the mounting surface 26. The removable component system 20 may be configured to control movement of a removable component 24 according, at least in part, to the current position/orientation of the removable component 24 and the current positions/orientations of the other removable components 24. For example and without limitation, the system controller 30 may be configured to control movement of removable components 24 such that the removable components 24 do not contact and/or damage each other, and/or do not materially interfere with movement of other removable components 24. Controlling movement of a removable component 24 may include controlling one or more actuators 58 (e.g., electric motors) of the removable component 24.
In examples, such as generally illustrated in
With examples, a system controller 30 may be configured to update the map/model 120 and/or create a new map/model 120 if the system controller 30 detects a change in the system 20. For example and without limitation, if the system controller 30 receives information from a removable component 24 that indicates that an occupancy status or seatbelt status of the removable component 24 has changed, and/or if system controller 30 determines that the position/orientation of a removable component 24 has changed, the system controller 30 may update the system map/model 120 accordingly. The system controller 30 may be configured to check for system updates automatically, such as at certain time intervals and/or with the occurrence of certain events (e.g., a user 100 actuates an actuator 58 of a removable component 24, a vehicle 28 is turned on or off, a seatbelt is buckled, etc.).
In embodiments, a map/model 120 may include models 156, 180 of safety devices 56, 80 of the mounting surface 26 and/or the vehicle 28, and/or of the removable components 24. The models 156, 180 of the safety devices 56, 80 may include an inactive state and an activated state, which may include larger dimensions and/or a different position than the inactive state. The system controller 30 and/or a component controller 52 may utilize the models 156, 180 of the safety devices 56, 80 in determining which safety devices 56, 80 to activate in the event of a crash or imminent crash.
With some embodiments, such as generally illustrated in
An embodiment of a method 200 of operating a removable component system 20 is generally illustrated in
While some exemplary embodiments are shown in the drawings for illustrative purposes with a track assembly 40, embodiments of the current disclosure are not limited to configurations with track assemblies 40. While some exemplary embodiments of track assemblies 40 are shown in the drawings for illustrative purposes as extending in the X-direction, embodiments of removable component systems 20 may include tracks that extend in other directions (e.g., the Y-direction, the Z-direction, etc.) and/or that include a matrix-type configuration that may allow for a wide range of movement.
In examples, a controller (e.g., a system controller 30, a component controller 52) may include an electronic controller and/or include an electronic processor, such as a programmable microprocessor and/or microcontroller. In embodiments, a controller may include, for example, an application specific integrated circuit (ASIC). A controller may include a central processing unit (CPU), a memory (e.g., a non-transitory computer-readable storage medium), and/or an input/output (I/O) interface. A controller may be configured to perform various functions, including those described in greater detail herein, with appropriate programming instructions and/or code embodied in software, hardware, and/or other medium. In embodiments, a controller may include a plurality of controllers. In embodiments, a controller may be connected to a display, such as a touchscreen display.
Various examples/embodiments are described herein for various apparatuses, systems, and/or methods. Numerous specific details are set forth to provide a thorough understanding of the overall structure, function, manufacture, and use of the examples/embodiments as described in the specification and illustrated in the accompanying drawings. It will be understood by those skilled in the art, however, that the examples/embodiments may be practiced without such specific details. In other instances, well-known operations, components, and elements have not been described in detail so as not to obscure the examples/embodiments described in the specification. Those of ordinary skill in the art will understand that the examples/embodiments described and illustrated herein are non-limiting examples, and thus it can be appreciated that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.
Reference throughout the specification to “examples, “in examples,” “with examples,” “various embodiments,” “with embodiments,” “in embodiments,” or “an embodiment,” or the like, means that a particular feature, structure, or characteristic described in connection with the example/embodiment is included in at least one embodiment. Thus, appearances of the phrases “examples, “in examples,” “with examples,” “in various embodiments,” “with embodiments,” “in embodiments,” or “an embodiment,” or the like, in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more examples/embodiments. Thus, the particular features, structures, or characteristics illustrated or described in connection with one embodiment/example may be combined, in whole or in part, with the features, structures, functions, and/or characteristics of one or more other embodiments/examples without limitation given that such combination is not illogical or non-functional. Moreover, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the scope thereof.
It should be understood that references to a single element are not necessarily so limited and may include one or more of such element. Any directional references (e.g., plus, minus, upper, lower, upward, downward, left, right, leftward, rightward, top, bottom, above, below, vertical, horizontal, clockwise, and counterclockwise) are only used for identification purposes to aid the reader's understanding of the present disclosure, and do not create limitations, particularly as to the use of examples/embodiments.
Joinder references (e.g., attached, coupled, connected, and the like) are to be construed broadly and may include intermediate members between a connection of elements and relative movement between elements. As such, joinder references do not necessarily imply that two elements are directly connected/coupled and in fixed relation to each other. The use of “e.g.” in the specification is to be construed broadly and is used to provide non-limiting examples of embodiments of the disclosure, and the disclosure is not limited to such examples. Uses of “and” and “or” are to be construed broadly (e.g., to be treated as “and/or”). For example and without limitation, uses of “and” do not necessarily require all elements or features listed, and uses of “or” are inclusive unless such a construction would be illogical.
While processes, systems, and methods may be described herein in connection with one or more steps in a particular sequence, it should be understood that such methods may be practiced with the steps in a different order, with certain steps performed simultaneously, with additional steps, and/or with certain described steps omitted.
All matter contained in the above description or shown in the accompanying drawings shall be interpreted as illustrative only and not limiting. Changes in detail or structure may be made without departing from the present disclosure.
It should be understood that a controller (e.g., a system controller 30, a component controller 52), a system, and/or a processor as described herein may include a conventional processing apparatus known in the art, which may be capable of executing preprogrammed instructions stored in an associated memory, all performing in accordance with the functionality described herein. To the extent that the methods described herein are embodied in software, the resulting software can be stored in an associated memory and can also constitute means for performing such methods. Such a system or processor may further be of the type having ROM, RAM, RAM and ROM, and/or a combination of non-volatile and volatile memory so that any software may be stored and yet allow storage and processing of dynamically produced data and/or signals.
It should be further understood that an article of manufacture in accordance with this disclosure may include a non-transitory computer-readable storage medium having a computer program encoded thereon for implementing logic and other functionality described herein. The computer program may include code to perform one or more of the methods disclosed herein. Such embodiments may be configured to execute via one or more processors, such as multiple processors that are integrated into a single system or are distributed over and connected together through a communications network, and the communications network may be wired and/or wireless. Code for implementing one or more of the features described in connection with one or more embodiments may, when executed by a processor, cause a plurality of transistors to change from a first state to a second state. A specific pattern of change (e.g., which transistors change state and which transistors do not), may be dictated, at least partially, by the logic and/or code.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/910,663, filed on Oct. 4, 2019, the disclosure of which is hereby incorporated by reference in its entirety as though fully set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
2126143 | McGregor | Aug 1938 | A |
2263554 | Brach | Nov 1941 | A |
2480622 | Warnock | Aug 1949 | A |
2678082 | Nathan | May 1954 | A |
3181102 | Fehr | Apr 1965 | A |
3213403 | Hermann | Oct 1965 | A |
3268848 | Adams | Aug 1966 | A |
3603918 | Woertz | Sep 1971 | A |
3933403 | Rubesamen et al. | Jan 1976 | A |
3940182 | Tamura | Feb 1976 | A |
4020769 | Keir | May 1977 | A |
4198025 | Lowe et al. | Apr 1980 | A |
4243248 | Scholz et al. | Jan 1981 | A |
4282631 | Uehara et al. | Aug 1981 | A |
4511187 | Rees | Apr 1985 | A |
4575295 | Rebentisch | Mar 1986 | A |
4618808 | Ish-Shalom et al. | Oct 1986 | A |
4707030 | Harding | Nov 1987 | A |
4711589 | Goodbred | Dec 1987 | A |
4763360 | Daniels et al. | Aug 1988 | A |
4776809 | Hall | Oct 1988 | A |
4830531 | Condit et al. | May 1989 | A |
4853555 | Wheat | Aug 1989 | A |
4961559 | Raymor | Oct 1990 | A |
4969621 | Munchow et al. | Nov 1990 | A |
4987316 | White et al. | Jan 1991 | A |
5106144 | Hayakawa et al. | Apr 1992 | A |
5137331 | Colozza | Aug 1992 | A |
5167393 | Hayakawa et al. | Dec 1992 | A |
5192045 | Yamada et al. | Mar 1993 | A |
5222814 | Boelryk | Jun 1993 | A |
5302065 | Vogg et al. | Apr 1994 | A |
5322982 | Leger et al. | Jun 1994 | A |
5332290 | Borlinghaus et al. | Jul 1994 | A |
5348373 | Stiennon | Sep 1994 | A |
5362241 | Matsuoka et al. | Nov 1994 | A |
5446442 | Swart et al. | Aug 1995 | A |
5466892 | Howard et al. | Nov 1995 | A |
5489173 | Hofle | Feb 1996 | A |
5582381 | Graf et al. | Dec 1996 | A |
5599086 | Dutta | Feb 1997 | A |
5618192 | Drury | Apr 1997 | A |
5655816 | Magnuson et al. | Aug 1997 | A |
5676341 | Tarusawa et al. | Oct 1997 | A |
5696409 | Handman et al. | Dec 1997 | A |
5701037 | Weber et al. | Dec 1997 | A |
5796177 | Werbelow et al. | Aug 1998 | A |
5800015 | Tsuchiya et al. | Sep 1998 | A |
5899532 | Paisley et al. | May 1999 | A |
5918847 | Couasnon | Jul 1999 | A |
5921606 | Moradell et al. | Jul 1999 | A |
5964442 | Wingblad et al. | Oct 1999 | A |
5964815 | Wallace et al. | Oct 1999 | A |
6008547 | Dobler et al. | Dec 1999 | A |
6036157 | Baroin et al. | Mar 2000 | A |
6081044 | Anthofer et al. | Jun 2000 | A |
6142718 | Kroll | Nov 2000 | A |
6150774 | Mueller et al. | Nov 2000 | A |
6166451 | Pigott | Dec 2000 | A |
6216995 | Koester | Apr 2001 | B1 |
6227595 | Hamelin et al. | May 2001 | B1 |
6290516 | Gerber | Sep 2001 | B1 |
6296498 | Ross | Oct 2001 | B1 |
6299230 | Oettl | Oct 2001 | B1 |
6318802 | Sjostrom et al. | Nov 2001 | B1 |
6325645 | Schuite | Dec 2001 | B1 |
6357814 | Boisset et al. | Mar 2002 | B1 |
6393348 | Ziegler et al. | May 2002 | B1 |
6400259 | Bourcart et al. | Jun 2002 | B1 |
6405988 | Taylor et al. | Jun 2002 | B1 |
6422596 | Fendt et al. | Jul 2002 | B1 |
6439531 | Severini et al. | Aug 2002 | B1 |
6480144 | Miller et al. | Nov 2002 | B1 |
6565119 | Fogle, Jr. | May 2003 | B2 |
6566765 | Nitschke et al. | May 2003 | B1 |
6588722 | Eguchi et al. | Jul 2003 | B2 |
6693368 | Schumann et al. | Feb 2004 | B2 |
6696943 | Elrod et al. | Feb 2004 | B1 |
6710470 | Bauer et al. | Mar 2004 | B2 |
6719350 | Duchateau et al. | Apr 2004 | B2 |
6736458 | Chabanne et al. | May 2004 | B2 |
6772056 | Mattes et al. | Aug 2004 | B2 |
6799100 | Burns et al. | Sep 2004 | B2 |
6805375 | Enders et al. | Oct 2004 | B2 |
6809643 | Elrod et al. | Oct 2004 | B1 |
6851708 | Kazmierczak | Feb 2005 | B2 |
6869057 | Matsumoto et al. | Mar 2005 | B2 |
6882162 | Schirmer et al. | Apr 2005 | B2 |
6960993 | Mattes et al. | Nov 2005 | B2 |
7012533 | Younse | Mar 2006 | B2 |
7042342 | Luo et al. | May 2006 | B2 |
7083437 | Mackness | Aug 2006 | B2 |
7086874 | Mitchell et al. | Aug 2006 | B2 |
7113541 | Lys et al. | Sep 2006 | B1 |
7159899 | Nitschke et al. | Jan 2007 | B2 |
7170192 | Kazmierczak | Jan 2007 | B2 |
7188805 | Henley et al. | Mar 2007 | B2 |
7207541 | Frohnhaus et al. | Apr 2007 | B2 |
7271501 | Dukart et al. | Sep 2007 | B2 |
7288009 | Lawrence et al. | Oct 2007 | B2 |
7293831 | Greene | Nov 2007 | B2 |
7300091 | Nihonmatsu et al. | Nov 2007 | B2 |
7322605 | Ventura et al. | Jan 2008 | B2 |
7348687 | Aichriedler et al. | Mar 2008 | B2 |
7363194 | Schlick et al. | Apr 2008 | B2 |
7370831 | Laib et al. | May 2008 | B2 |
7388466 | Ghabra et al. | Jun 2008 | B2 |
7389960 | Mitchell et al. | Jun 2008 | B2 |
7416042 | Czaykowska et al. | Aug 2008 | B2 |
7434883 | Deptolla | Oct 2008 | B2 |
7454170 | Goossens et al. | Nov 2008 | B2 |
7455535 | Insalaco et al. | Nov 2008 | B2 |
7503522 | Henley et al. | Mar 2009 | B2 |
7505754 | Kazmierczak et al. | Mar 2009 | B2 |
7523913 | Mizuno et al. | Apr 2009 | B2 |
7556233 | Gryp et al. | Jul 2009 | B2 |
7560827 | Jacas-Miret et al. | Jul 2009 | B2 |
7633301 | Steenwyk et al. | Dec 2009 | B2 |
7643913 | Taki et al. | Jan 2010 | B2 |
7661637 | Mejuhas et al. | Feb 2010 | B2 |
7665939 | Cardona | Feb 2010 | B1 |
7739820 | Frank | Jun 2010 | B2 |
7744386 | Speidel et al. | Jun 2010 | B1 |
7980525 | Kostin | Jul 2011 | B2 |
7980798 | Kuehn et al. | Jul 2011 | B1 |
8010255 | Darraba | Aug 2011 | B2 |
8146991 | Stanz et al. | Apr 2012 | B2 |
8179274 | Rork et al. | May 2012 | B2 |
8190332 | Saban | May 2012 | B2 |
8278840 | Logiudice et al. | Oct 2012 | B2 |
8282326 | Krostue et al. | Oct 2012 | B2 |
8376675 | Schulze et al. | Feb 2013 | B2 |
8463501 | Jousse | Jun 2013 | B2 |
8536928 | Gagne et al. | Sep 2013 | B1 |
8648613 | Ewerhart et al. | Feb 2014 | B2 |
8702170 | Abraham et al. | Apr 2014 | B2 |
8757720 | Hurst, III et al. | Jun 2014 | B2 |
8800949 | Schebaum et al. | Aug 2014 | B2 |
8816845 | Hoover et al. | Aug 2014 | B2 |
8857778 | Nonomiya | Oct 2014 | B2 |
8936526 | Boutouil et al. | Jan 2015 | B2 |
8967719 | Ngiau et al. | Mar 2015 | B2 |
RE45456 | Sinclair et al. | Apr 2015 | E |
9010712 | Gray et al. | Apr 2015 | B2 |
9018869 | Yuasa et al. | Apr 2015 | B2 |
9045061 | Kostin et al. | Jun 2015 | B2 |
9162590 | Nagura et al. | Oct 2015 | B2 |
9174604 | Wellhoefer et al. | Nov 2015 | B2 |
9242580 | Schebaum et al. | Jan 2016 | B2 |
9251631 | Thompson et al. | Feb 2016 | B2 |
9318922 | Hall et al. | Apr 2016 | B2 |
9340125 | Stutika et al. | May 2016 | B2 |
9346428 | Bortolin | May 2016 | B2 |
9422058 | Fischer et al. | Aug 2016 | B2 |
9519905 | Basir | Dec 2016 | B2 |
9561770 | Sievers et al. | Feb 2017 | B2 |
9608392 | Destro | Mar 2017 | B1 |
9610862 | Bonk et al. | Apr 2017 | B2 |
9663232 | Porter et al. | May 2017 | B1 |
9673583 | Hudson et al. | Jun 2017 | B2 |
9691250 | Trang et al. | Jun 2017 | B2 |
9701217 | Eckenroth et al. | Jul 2017 | B2 |
9731628 | Rao et al. | Aug 2017 | B1 |
9758061 | Pluta et al. | Sep 2017 | B2 |
9789834 | Rapp et al. | Oct 2017 | B2 |
9796304 | Salter et al. | Oct 2017 | B2 |
9815425 | Rao et al. | Nov 2017 | B2 |
9821681 | Rao et al. | Nov 2017 | B2 |
9840220 | Van Buskirk et al. | Dec 2017 | B2 |
9919624 | Cziomer et al. | Mar 2018 | B2 |
9950682 | Gramenos et al. | Apr 2018 | B1 |
10034631 | Gallagher et al. | Jul 2018 | B1 |
10059232 | Frye et al. | Aug 2018 | B2 |
10160351 | Sugimoto et al. | Dec 2018 | B2 |
10479227 | Nolte et al. | Nov 2019 | B2 |
10493243 | Braham | Dec 2019 | B1 |
10547135 | Sugiura | Jan 2020 | B2 |
10549659 | Sullivan et al. | Feb 2020 | B2 |
10654378 | Pons | May 2020 | B2 |
20050046367 | Wevers et al. | Mar 2005 | A1 |
20050089367 | Sempliner | Apr 2005 | A1 |
20050150705 | Vincent et al. | Jul 2005 | A1 |
20050211835 | Henley et al. | Sep 2005 | A1 |
20050215098 | Muramatsu et al. | Sep 2005 | A1 |
20050230543 | Laib et al. | Oct 2005 | A1 |
20050236899 | Kazmierczak | Oct 2005 | A1 |
20050258676 | Mitchell et al. | Nov 2005 | A1 |
20060131470 | Yamada et al. | Jun 2006 | A1 |
20060208549 | Hancock et al. | Sep 2006 | A1 |
20060220411 | Pathak et al. | Oct 2006 | A1 |
20080021602 | Kingham et al. | Jan 2008 | A1 |
20080084085 | Mizuno et al. | Apr 2008 | A1 |
20080090432 | Patterson et al. | Apr 2008 | A1 |
20080157940 | Breed | Jul 2008 | A1 |
20090014584 | Rudduck et al. | Jan 2009 | A1 |
20090129105 | Kusu et al. | May 2009 | A1 |
20090251920 | Kino et al. | Oct 2009 | A1 |
20090302665 | Dowty | Dec 2009 | A1 |
20090319212 | Cech et al. | Dec 2009 | A1 |
20100117275 | Nakamura | May 2010 | A1 |
20100256835 | Mudalige | Oct 2010 | A1 |
20110024595 | Oi et al. | Feb 2011 | A1 |
20110225773 | Hearn et al. | Sep 2011 | A1 |
20120112032 | Kohen | May 2012 | A1 |
20130020459 | Moriyama et al. | Jan 2013 | A1 |
20130035994 | Pattan et al. | Feb 2013 | A1 |
20130049955 | Hoover et al. | Feb 2013 | A1 |
20130153735 | Ruthman et al. | Jun 2013 | A1 |
20140085070 | Schoenberg | Mar 2014 | A1 |
20140110554 | Oya et al. | Apr 2014 | A1 |
20140263920 | Anticuar et al. | Sep 2014 | A1 |
20140265479 | Bennett | Sep 2014 | A1 |
20150048206 | Deloubes | Feb 2015 | A1 |
20150069807 | Kienke | Mar 2015 | A1 |
20150077561 | Schulz | Mar 2015 | A1 |
20150083882 | Stutika et al. | Mar 2015 | A1 |
20150191106 | Inoue et al. | Jul 2015 | A1 |
20150236462 | Davidson, Jr. et al. | Aug 2015 | A1 |
20160039314 | Anticuar et al. | Feb 2016 | A1 |
20160154170 | Thompson et al. | Jun 2016 | A1 |
20160236613 | Trier | Aug 2016 | A1 |
20160304045 | Cuddihy et al. | Oct 2016 | A1 |
20160379466 | Payant et al. | Dec 2016 | A1 |
20170080825 | Bonk et al. | Mar 2017 | A1 |
20170080826 | Bonk | Mar 2017 | A1 |
20170166093 | Cziomer et al. | Jun 2017 | A1 |
20170261343 | Lanter et al. | Sep 2017 | A1 |
20170291507 | Hattori et al. | Oct 2017 | A1 |
20180017189 | Wegner | Jan 2018 | A1 |
20180039917 | Buttolo et al. | Feb 2018 | A1 |
20180072188 | Yamada | Mar 2018 | A1 |
20180086232 | Kume | Mar 2018 | A1 |
20180105072 | Pons | Apr 2018 | A1 |
20180148011 | Zaugg et al. | May 2018 | A1 |
20180154799 | Lota | Jun 2018 | A1 |
20180183623 | Schoenfeld et al. | Jun 2018 | A1 |
20180244175 | Tan | Aug 2018 | A1 |
20180275648 | Ramalingam | Sep 2018 | A1 |
20190001846 | Jackson et al. | Jan 2019 | A1 |
20190084453 | Petit et al. | Mar 2019 | A1 |
20190126786 | Dry et al. | May 2019 | A1 |
20190337413 | Romer | Nov 2019 | A1 |
20190337414 | Condamin et al. | Nov 2019 | A1 |
20190337415 | Condamin et al. | Nov 2019 | A1 |
20190337416 | Condamin et al. | Nov 2019 | A1 |
20190337417 | Condamin et al. | Nov 2019 | A1 |
20190337418 | Condamin et al. | Nov 2019 | A1 |
20190337419 | Condamin et al. | Nov 2019 | A1 |
20190337420 | Condamin et al. | Nov 2019 | A1 |
20190337421 | Condamin et al. | Nov 2019 | A1 |
20190337422 | Condamin et al. | Nov 2019 | A1 |
20190337471 | Brehm | Nov 2019 | A1 |
20190379187 | Christensen et al. | Dec 2019 | A1 |
20190389336 | Malinowski et al. | Dec 2019 | A1 |
20200009995 | Sonar | Jan 2020 | A1 |
20200047641 | D'Eramo et al. | Feb 2020 | A1 |
20200055423 | Prozzi et al. | Feb 2020 | A1 |
20200079244 | Carbone et al. | Mar 2020 | A1 |
20200171979 | Yetukuri | Jun 2020 | A1 |
20200180516 | Moulin | Jun 2020 | A1 |
20200180517 | Moulin | Jun 2020 | A1 |
20200189504 | Ricart et al. | Jun 2020 | A1 |
20200189511 | Ricart et al. | Jun 2020 | A1 |
20200194936 | Ricart et al. | Jun 2020 | A1 |
20200194948 | Lammers et al. | Jun 2020 | A1 |
20200207241 | Moulin et al. | Jul 2020 | A1 |
20200247275 | Yetukuri et al. | Aug 2020 | A1 |
20200262367 | Fernandez Banares et al. | Aug 2020 | A1 |
20200269754 | Ricart et al. | Aug 2020 | A1 |
20200282871 | Ricart et al. | Sep 2020 | A1 |
20200282880 | Jones et al. | Sep 2020 | A1 |
20200298780 | Kanegae | Sep 2020 | A1 |
20220063555 | Kanegae | Mar 2022 | A1 |
Number | Date | Country |
---|---|---|
203190203 | Sep 2013 | CN |
203799201 | Aug 2014 | CN |
202005013714 | Dec 2005 | DE |
102005007430 | Mar 2006 | DE |
102006022032 | Dec 2006 | DE |
102010017038 | Feb 2011 | DE |
102011056278 | Feb 2013 | DE |
202014102336 | Jun 2014 | DE |
102015212100 | Dec 2015 | DE |
102016113409 | Apr 2017 | DE |
0783990 | Jul 1997 | EP |
1176047 | Jan 2002 | EP |
1310407 | May 2006 | EP |
2298609 | Mar 2011 | EP |
3150426 | Apr 2017 | EP |
2762814 | Nov 1998 | FR |
2951329 | Apr 2011 | FR |
2986751 | Aug 2013 | FR |
2327914 | Feb 1999 | GB |
2396944 | Jul 2004 | GB |
3314591 | Aug 2002 | JP |
2003227703 | Aug 2003 | JP |
2005119518 | May 2005 | JP |
2007112174 | May 2007 | JP |
2008158578 | Jul 2008 | JP |
4222262 | Feb 2009 | JP |
2013230721 | Nov 2013 | JP |
0187665 | Nov 2001 | WO |
2003002256 | Jan 2003 | WO |
2005068247 | Jul 2005 | WO |
Entry |
---|
Co-Pending U.S. Appl. No. 16/597,187, filed Oct. 9, 2019. |
Co-Pending U.S. Appl. No. 16/672,989, filed Nov. 4, 2019. |
Co-Pending U.S. Appl. No. 16/711,661, filed Dec. 12, 2019. |
Co-Pending U.S. Appl. No. 17/060,566, filed Oct. 1, 2020. |
Co-Pending U.S. Appl. No. 17/060,635, filed Oct. 1, 2020. |
Don't Forget Your Baby in the Car! There's an App for That; https://www.parents.com/baby/all-about-babies/dont-forget-your-baby-in-the-car-theres-an-app-for-that/; Jul. 25, 2014. |
Number | Date | Country | |
---|---|---|---|
20210101562 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
62910663 | Oct 2019 | US |