A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the reproduction of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates generally to vehicle platooning. More particularly, the present invention relates to systems and methods for dynamically adjusting platoon characteristics such as respective following distances for a number of vehicles such as tractor trailers based on predicted external effects or perturbations.
The benefits of driver assistive vehicle platooning are well-established, as are the heightened benefits of a reduced following distance between respective vehicles in a platoon orientation. For example, minimizing following distances can result in reduced aerodynamic drag for all vehicles in a platoon, and thereby improve respective fuel economies. At highway speeds, aerodynamic drag may be characterized as the greatest consumer of vehicle power, well in excess of the combined effects of rolling friction resistance and vehicle accessory losses. Test results have indicated that vehicles consistently achieve increased benefits correlating to closer following distances, although the energy-saving benefits may vary depending on the respective vehicle position within a platoon.
Advanced braking control systems have been implemented, along with integrated vehicle-to-vehicle communications, for the purpose of facilitating vehicle platooning and reducing the associated following distances to the extent possible. However, conventional techniques are unable to safely reduce the following distances between vehicles to a desired level, at least because of the inherent external perturbations which arise during typical traffic flow. A trailing vehicle in a platoon must implement a following distance which accounts for the successive detection of braking actions by a preceding vehicle, and the accompanying reactions by intervening vehicles. Conventional techniques, as one of skill in the art today may recognize, therefore rely on reaction to an actual braking event by a preceding vehicle within the platoon with respect to a particular trailing vehicle, or an anticipatory reaction by a driver of the trailing vehicle based upon visual investigation of the traffic and road conditions.
It would be desirable to provide and implement a platoon control system which identifies potential external perturbations to the platoon and dynamically accounts for the risk of predicted braking events, even prior to any actual braking or other reaction by another vehicle in the platoon.
It would further be preferable for such a platoon control system to cause trailing vehicles within or otherwise as part of the platoon to dynamically adjust their respective following distances in view of such predicted braking events by vehicles that are not within or otherwise part of the platoon, again without waiting for or otherwise having to detect a reaction by preceding vehicles in the platoon.
In accordance with various embodiments of a vehicle platooning control system and associated methods as described herein, a plurality of vehicles defining a platoon are configured to dynamically and automatically adjust a nominal following distance based on actual or projected perturbations to the platoon as a whole. Otherwise stated, a collective platoon unit may be defined having communications network devices, sensors, cameras and the like so as to monitor traffic, road and ambient conditions, wherein any one vehicle in the platoon unit is configured to adjust its following distance with respect to a preceding vehicle based on a braking or other form of event risk. A vehicle platooning control system as disclosed herein may therefore appropriately balance the desire to maintain a minimum effective following distance between each respective vehicle pair in the platoon, while making real-time adjustments to any one or more of said following distances with respect to potential braking events that are otherwise undetectable from the aforementioned prior art techniques.
In one aspect of various embodiments as described herein, each vehicle in a potential platoon combination may be respectively equipped with one or more vehicle braking control and platoon implementation systems and one or more sensors collectively configured to monitor at least a following distance between the vehicle and the other one or more vehicles, a relative deceleration value for the vehicle, and a pressure value with respect to a braking actuator for the vehicle.
In another aspect, a lead vehicle in a defined platoon may monitor relative position, velocity, acceleration/deceleration and the like for at least a target vehicle located directly in front of the lead vehicle and hence the platoon as a whole, wherein a braking event risk may be determined. The lead vehicle may further independently identify or otherwise provide signals whereby a back-end server may programmatically identify a type of target vehicle, wherein a braking event risk may be determined further based on a relative braking ability or likelihood of the same with respect to the target vehicle. For example, it may be appreciated that a sedan may typically have a relatively greater braking ability than a heavy truck otherwise similarly situated as a target vehicle.
In another aspect, a rear vehicle in a defined platoon may monitor relative position, velocity, acceleration/deceleration and the like for at least a target vehicle located directly behind the rear vehicle and hence the platoon as a whole, wherein an event risk associated with, e.g., potential tailgating may be determined. The rear vehicle may further independently identify or otherwise provide signals whereby a back-end server may programmatically identify a type of the target vehicle, wherein an event risk may be determined further based on inherent characteristics of the target vehicle.
In another aspect, each vehicle in a defined platoon may monitor relative position, velocity, acceleration/deceleration and the like for one or more target vehicles located to either side of the platoon as a whole, wherein a braking event risk associated with, e.g., interjection by a target vehicle among the platoon or otherwise cutting in front of the lead vehicle, etc., may be determined. A likelihood of braking event risk may further be determined further based on inherent characteristics of the respective target vehicles. In this manner, for example, a trailing vehicle within the platoon may identify and monitor one or more target vehicles approaching the platoon from either side, and determine a braking event risk for the lead vehicle in a manner that is otherwise unavailable to the lead vehicle in the case wherein the respective target vehicles are in a “blind spot” for the lead vehicle itself.
Referring generally to
Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context dictates otherwise. The meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. The meaning of “a,” “an,” and “the” may include plural references, and the meaning of “in” may include “in” and “on.” The phrase “in one embodiment,” as used herein does not necessarily refer to the same embodiment, although it may.
Referring first to
Each vehicle in a potential platoon may be considered to have at least certain minimum structural components in order for various embodiments of the present disclosure to be implemented. As shown in the example embodiment of
In the particular embodiment as shown in
In certain embodiments, otherwise conventional braking control systems 114 such as the CMS for example may be supplemented or otherwise configured to include hardware, software, or some combination thereof so as to execute a vehicle platooning algorithm in accordance with the present disclosure. Alternatively, vehicle platooning algorithms and components may be separately associated with control block 118. In various embodiments, the braking control systems, and more particularly the CMS, may be implemented for distance measurement using techniques as are known to those of skill in the art.
The vehicle sensors 116 may be configured to provide at least certain information as needed to execute functions for a particular embodiment of the platooning control system, including for example a following distance between a given pair of vehicles, relative velocity and acceleration/deceleration values for the respective vehicle, a pressure value with respect to a braking actuator for the respective vehicle, front and rear radar/LIDAR/sensors for distance measurement, image capturing and the like, side lane monitoring devices, alternative pressure sensors integrally mounted to or associated with solenoid valves, etc.
In various embodiments, vehicles in the platoon may further be equipped with display units or other devices by which notice may be visually or audibly provided to vehicles outside of the platoon. For example, while the platooning control system may be configured to dynamically adjust internal characteristics such as respective following distances within the platoon based on a tailgater or equivalent potential perturbation, a rear vehicle may further be configured to generate a display indication and thereby warn the target vehicle that it is (potentially unsafely) encroaching upon a vehicle platoon. In an embodiment, the platooning control system may direct one or more vehicles in the platoon, including at least the trailing vehicle, to collectively accelerate or to accelerate in varying degrees for extending the respective following distances there between, based on a tailgater or equivalent potential perturbation.
Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of computer-readable medium known in the art. An exemplary computer-readable medium can be coupled to the processor such that the processor can read information from, and write information to, the memory/storage medium. In the alternative, the medium can be integral to the processor. The processor and the medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the medium can reside as discrete components in a user terminal.
Referring next to
The procedure may be considered as beginning (step 301) by establishing a vehicle platoon unit comprising a plurality of vehicles 112. In the event that a platoon has already been formed, this step may be considered unnecessary, but otherwise steps may be taken to determine if a platoon is appropriate. In one embodiment, a server-based system may receive a request from one or more vehicles in a potential platoon, and subsequently collect or otherwise obtain data corresponding to pre-conditions which must be satisfied in order to establish a vehicle platoon. In a particular example, wherein each of the vehicles are already communicatively linked via V2V, the drivers may manually inform their respective systems of a desire to platoon, wherein one or more of the vehicle systems generates a request to the vehicle platooning system. As is alluded to above, this step does not require or imply that the system must reside separately from the requesting vehicle, but rather a request may in certain examples be generated by a first component within a vehicle (e.g., via manual user actuation) and received by a vehicle platooning control system component residing within the same vehicle. However, for illustrative purposes the discussion herein may typically refer to the control functions of the vehicle platooning control system as being directed separately with respect to the vehicles themselves.
In certain embodiments as disclosed herein the system may automatically identify a potential platoon orientation even in the absence of requests from the respective vehicles themselves. For example, the system may obtain and store data corresponding to each attempt by a vehicle to platoon, and then apply historical data for that vehicle in later trips to identify potential platoon partners. Having identified a potential platoon orientation, the system may perform a pre-condition check for each of the vehicles similar to that described above, and subsequently generate messages to each of the vehicles that notify the drivers and their respective systems of the potential platoon, and requesting acceptance to proceed with the platoon configuration.
In various embodiments, pre-conditions may only be checked after the vehicles have accepted the potential platoon offer, and indeed this may be required where for example the system can only obtain the information needed to confirm the pre-conditions after the vehicles have accepted the platooning offer.
Such pre-conditions may include vehicle status conditions, such as for example confirming the vehicles are each equipped with sufficiently properly functioning hardware and associated braking control systems, that the vehicles are appropriately positioned with respect to each other (e.g., in an appropriate lane of an appropriate roadway), that the vehicles are traveling at an appropriate speed such as between 50 and 65 miles per hour, etc. The system may for example verify that all wheel speed sensors associated with the plurality of vehicles have not been de-adjusted and other components are functioning properly.
Such pre-conditions may further include peripheral road conditions, such as for example a limited access highway, a nature or quality of the road surface, such as having relatively low grade and relatively straight, lack of construction or other impediments to normal travel, etc. The peripheral road conditions may in certain embodiments be confirmed by way of comparison of a particular location (as determined for example using GPS coordinates) with a road mapping database including relatively current details regarding road conditions.
Such pre-conditions may further include peripheral traffic conditions, such as for example the lack of other vehicles between or otherwise threatening the relative pairing of vehicles in the proposed platoon. Information may be provided by any one or more of the vehicles to the other vehicles, depending on the current positioning. For example, one or more vehicles in or near the rear in a current orientation may be best positioned through the use of radar and/or rear-facing cameras to identify non-platooning vehicles which have entered or may be about to enter the right lane of traffic in between a pair of vehicles in the potential platoon.
Other pre-conditions which may apply within the scope of the present disclosure may include without limitation ambient effects such as weather conditions (e.g., wind, temperature, air pressure). In various embodiments, the system may determine ambient conditions based not only on sensor and/or imaging data from one or more of the associated vehicles but also in view of information collected from third party data sources such as for example those associated with weather services. In certain embodiments, the system may still further collect information from other vehicles which have traversed the same roadway within a threshold period of time prior to the current platoon, and this information may be predictively applied by the system for determining the appropriateness of the platoon configuration in a given location.
In an embodiment, the system may further determine relative following distances of the one or more vehicles following the lead vehicle in the platoon, assuming the platoon conditions remain adequate (step 302). In certain embodiments, the system may be configured to determine an appropriate or nominal following distance for each of the respective following vehicles. If the actual following distance at a given time varies from the determined nominal following distance, or for example outside of an associated range, the system may be configured to further generate notifications for one or more of the relevant vehicles such that the vehicles are prompted to adjust their following distance or at least acknowledge notification regarding the same.
For example, with reference to
A number of variables may be considered in determining an appropriate following distance for any particular following vehicle in the platoon, including for example estimated braking performance capabilities for each following vehicle and its respective preceding vehicle, road conditions, traffic conditions, etc. Estimated braking performance capabilities may be based at least in part on certain characteristics which may be considered over time such as brake types, sizes, tractor and trailer systems, linings, tires, ambient temperature, road conditions, etc. Other parameters such as for example a nominal traveling velocity may be determined or even dynamically adjusted (as further described below) in concert with the determination of an appropriate following distance, based on similar variables as discussed above such as for example road conditions and traffic conditions. Nominal following distances and traveling velocities may further take into account projected road conditions and traffic conditions in addition to current and identified variables, such as for example based on a specific location, time of day, day of week, mapping systems or the like for indicating upcoming road construction or accidents, etc.
In certain embodiments, actual and reliable braking test data may be acquired by an onboard system for any one or more of the vehicles or alternatively an associated server system and implemented in estimated relative braking performance capabilities for at least the vehicle(s) providing such test data. Generally speaking, reliable data may typically not be available due to the constantly changing nature of vehicle conditions (e.g., tire wear on the tractor, trailer tires, varying trailer loads). However, in some contexts it may be understood that available data is sufficiently reliable, based upon criteria including for example an amount of time and/or miles traveled since the data was collected, the current load relative to a load size at the time the data was collected, etc.
In a particular embodiment, the system may even orient the vehicles within the platoon such that vehicles having the highest estimated braking performance capabilities are progressively situated from the rear of the platoon forward, such that the vehicle having the projected highest braking performance capability is situated in the rear of the platoon and the vehicle having the projected lowest braking performance capability is situated in the front of the platoon.
Referring now to
Referring now to
In one example, a target vehicle 204b may be traveling in a current direction that would indicate interjection with the platoon unit, or otherwise at least merging into the lane upon which the platoon unit is traveling. Based on the relative speeds of the target vehicle 204b and the relevant platoon vehicles, the system may calculate a likelihood that the target vehicle will merge into the lane upon which the platooning vehicles are traveling at some position 208 ahead of the lead vehicle, behind the rear vehicle, or otherwise interjected between a pair of vehicles in the platoon. As further described below, the system may further determine that even if such a maneuver were to be executed it would encompass little to no braking risk for any one or more vehicles in front of a projected interjection, but nonetheless it would encompass at least a moderate if not significant braking risk for any one or more trailing vehicles.
In another example, one lead target vehicle 204a may be positioned in front and to the side of the lead vehicle 112a, while another target vehicle 204c is positioned directly behind the lead target vehicle 204a. Based on the relative speeds of the target vehicles 204a, 204c, and a longitudinal distance between the lead platoon vehicle 112a and the lead target vehicle 204a, the system may calculate a likelihood that either or both of the target vehicles will laterally cut into the lane upon which the platooning vehicles are traveling at position 208a. As further described below, the system may further determine that even if such a maneuver were to be executed it would encompass little braking risk for the lead vehicle, but nonetheless it would encompass at least a slightly greater if not moderate braking risk for one or more trailing vehicles.
In another example, a target vehicle 204d is positioned directly behind target vehicle 204c. Based on the relative speeds of the target vehicles 204a, 204c, 204d, and a longitudinal distance between the lead platoon vehicle 112a and the lead target vehicle 204a, the system may calculate a likelihood that either or both of the target vehicles 204c, 204d, will laterally cut into the lane upon which the platooning vehicles are traveling at either or both of positions 208b, 208c. As further described below, the system may further determine that even if such a maneuver were to be executed it would encompass little to no braking risk for any one or more vehicles in front of a projected interjection, but nonetheless it would encompass at least a moderate if not significant braking risk for any one or more trailing vehicles.
Referring next to
In an embodiment, the system may further monitor traffic and ambient conditions as they would potentially affect braking performance capabilities over time for one or more of the vehicles in the platoon (step 306). This may for example involve braking data as may be gathered during normal operation and with respect to expected values or variables relative to the braking data, such as for example expected deceleration with respect to pressure applied during a braking operation, or monitoring of ABS events which may take place, during an interim period after initiation of a platoon as disclosed herein. If the system is able to determine that target vehicle conditions and characteristics, braking performance capabilities, road conditions, ambient conditions, etc., have changed such that the platoon orientation should not be maintained, the system may in various embodiments be configured to cancel the platoon orientation or other generate notifications to that effect (step 307). As but one possible alternative, rather than cancelling the platooning operation the system may merely suspend the platooning operation or otherwise dynamically modify the platooning operation such that the following distances for the respective vehicles are temporarily adjusted in compensation for transient non-optimal conditions (step 308).
The dynamic adjustments to the following distances may take various exemplary forms, dependent for example on a relative position of a particular vehicle in the platoon, a relative braking event risk, a magnitude of the likely braking risk, etc.
In one particular embodiment, an adjusted following distance Dnew may be determined according to the exemplary equation:
Dnew=Dnom+(Demer−Dnom)(α*β*τ*γ)
where Dnom is the nominal following distance determined for the associated platoon vehicle pairing; Demer is a maximum following distance as may be required in certain circumstances while still operating under a platoon configuration; α represents a likelihood of a braking event as determined in accordance with the various target vehicle inputs described above; β represents a magnitude of the braking event, wherein for example a 1.0 braking event would represent an emergency braking event; τ represents a positional amplifier wherein a following distance adjustment is amplified for vehicles being farther back in the platoon chain; and γ represents a dampening effect applied via for example a threshold comparison in order to prevent premature reactions to relatively inconsequential braking events.
In a particular example according to the previous embodiment, the system may determine that a combination of target vehicle characteristics should be calculated as providing a 5% (i.e., α=0.05) braking event likelihood for the rear platoon vehicle 112c in the example cited above. Assuming in this example that all braking events being considered are emergency braking events (i.e., B=1.0), and that an appropriate multiplier τ would be 3.0 for the third vehicle in the affected chain, that the nominal following distance was 50 feet, and that the maximum following distance was 80 feet, this would result in an equation of:
Dnew=50+(80−50)(0.05*1.0*3.0*γ),
or
Dnew=50+4.5γ.
Further assuming in this exemplary embodiment that the variable γ is determined by whether or not a threshold braking event risk is exceeded, and ranges in binary fashion between 0 and 1, the following distance for the rear platoon vehicle would either remain at the nominal value of 50 feet or be adjusted to a following distance of 54.5 feet. The threshold in question may in various embodiments be a fixed and predetermined value, or otherwise may be variable in nature and determined based upon any inherent risks associated with the platoon conditions.
It may be understood that the aforementioned example is not intended as limiting on the scope of the present invention, but merely as illustrative of a relatively simple example of the calculations which may be involved in dynamically adjusting following distances in a manner which is (1) reliant upon determined values exceeding a threshold which operates to dampen short-term and potentially unreliable compensations; and further (2) provides a degree of adjustment to the determined nominal following distances that is inversely correlated with respect to a relative proximity of the particular following vehicle to a predicted external perturbation. For example, a rear vehicle 112c may be expected to adjust its following distance at a greater degree than the adjustment for an immediately preceding vehicle in the platoon, based on a predicted perturbation to the platoon at a point in front of both vehicles.
In an embodiment, the system may additionally or in the alternative determine a nominal traveling velocity for vehicles in the platoon, and dynamically adjust the nominal traveling velocities in response to external perturbations or the like as otherwise described herein. For example, in certain conditions the system may determine that a braking event risk is generally reduced by reducing the collective traveling velocity of each vehicle in the platoon, even where the following distances themselves remain the same. In another condition, such as for example where one or more target vehicles are aggressively approaching the platoon from behind and/or from the side, one or more vehicles in the platoon may respond by increasing their traveling velocity to prevent or mitigate the likelihood of a braking event or crash, or in some cases to facilitate a temporary merge by a target vehicle in between platooning vehicles.
Upon dynamically adjusting the nominal following distances for one or more of the vehicles in the platoon, the control system may further provide signals to the respective vehicle systems or otherwise direct associated vehicle components to be regulated in a manner known to those of skill in the art, wherein vehicle speeds are adjusted based on the new following distance (step 309).
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment.
The term “communications network” as used herein with respect to data communication between two or more parties or otherwise between communications network interfaces associated with two or more parties may refer to any one of, or a combination of any two or more of, telecommunications networks (whether wired, wireless, cellular or the like), a global network such as the Internet, local networks, network links, Internet Service Providers (ISP's), and intermediate communication interfaces.
The previous detailed description has been provided for the purposes of illustration and description. Thus, although there have been described particular embodiments of a new and useful invention, it is not intended that such references be construed as limitations upon the scope of this invention except as set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5680122 | Mio | Oct 1997 | A |
5777451 | Kobayashi | Jul 1998 | A |
5781119 | Yamashita et al. | Jul 1998 | A |
5815825 | Tachibana et al. | Sep 1998 | A |
6128559 | Saitou et al. | Oct 2000 | A |
6285929 | Hashimoto | Sep 2001 | B1 |
6397149 | Hashimoto | May 2002 | B1 |
7554435 | Tengler | Jun 2009 | B2 |
8352112 | Mudalige | Jan 2013 | B2 |
8442735 | Hrovat et al. | May 2013 | B2 |
8666587 | Anderson | Mar 2014 | B2 |
8744666 | Switkes | Jun 2014 | B2 |
8948995 | Pandita et al. | Feb 2015 | B2 |
20020198632 | Breed et al. | Dec 2002 | A1 |
20040193372 | MacNeille et al. | Sep 2004 | A1 |
20050107945 | Hiller et al. | May 2005 | A1 |
20060095195 | Nishimura | May 2006 | A1 |
20060293841 | Hrovat et al. | Dec 2006 | A1 |
20070043502 | Mudalige et al. | Feb 2007 | A1 |
20070197230 | Roggero et al. | Aug 2007 | A1 |
20080059007 | Whittaker | Mar 2008 | A1 |
20090228157 | Breed | Sep 2009 | A1 |
20090287412 | Menzel et al. | Nov 2009 | A1 |
20100045482 | Strauss | Feb 2010 | A1 |
20100094509 | Lüke et al. | Apr 2010 | A1 |
20100202346 | Sitzes et al. | Aug 2010 | A1 |
20100256835 | Mudalige | Oct 2010 | A1 |
20100256852 | Mudalige | Oct 2010 | A1 |
20110118967 | Tsuda | May 2011 | A1 |
20110122244 | Cho | May 2011 | A1 |
20110208399 | Fekete et al. | Aug 2011 | A1 |
20110270514 | Shida | Nov 2011 | A1 |
20120252415 | Menzel et al. | Oct 2012 | A1 |
20130015984 | Yamashiro | Jan 2013 | A1 |
20130030606 | Mudalige et al. | Jan 2013 | A1 |
20130041567 | Yamashiro | Feb 2013 | A1 |
20130041576 | Switkes | Feb 2013 | A1 |
20130054127 | Yamashiro | Feb 2013 | A1 |
20130079953 | Kumabe | Mar 2013 | A1 |
20130080040 | Kumabe | Mar 2013 | A1 |
20130080041 | Kumabe | Mar 2013 | A1 |
20130116861 | Nemoto | May 2013 | A1 |
20130124064 | Nemoto | May 2013 | A1 |
20130218365 | Caveney et al. | Aug 2013 | A1 |
20130231820 | Solyom | Sep 2013 | A1 |
20130317676 | Cooper | Nov 2013 | A1 |
20130325306 | Caveney et al. | Dec 2013 | A1 |
20140005906 | Pandita et al. | Jan 2014 | A1 |
20140019031 | Solyom et al. | Jan 2014 | A1 |
20140100734 | Yamashiro | Apr 2014 | A1 |
20140107867 | Yamashiro | Apr 2014 | A1 |
20140140353 | Stählin et al. | May 2014 | A1 |
20140172265 | Funabashi | Jun 2014 | A1 |
20140236449 | Horn | Aug 2014 | A1 |
20140316671 | Okamoto | Oct 2014 | A1 |
20140316865 | Okamoto | Oct 2014 | A1 |
20140327775 | Cho | Nov 2014 | A1 |
20150012204 | Breuer et al. | Jan 2015 | A1 |
20150356635 | Thurston | Dec 2015 | A1 |
Number | Date | Country |
---|---|---|
10109052 | Sep 2002 | DE |
102004017603 | Oct 2005 | DE |
102004017604 | Oct 2005 | DE |
102004056724 | May 2006 | DE |
102010046236 | May 2011 | DE |
1012012022035 | May 2013 | DE |
0816168 | Jan 1998 | EP |
1296305 | Mar 2003 | EP |
1504948 | Feb 2005 | EP |
1975901 | Oct 2008 | EP |
0357963 | May 2011 | EP |
2555583 | Feb 2013 | EP |
2827316 | Jan 2015 | EP |
2007261448 | Oct 2007 | JP |
2008113836 | Sep 2008 | WO |
2008128998 | Oct 2008 | WO |
2009024563 | Feb 2009 | WO |
2009027244 | Mar 2009 | WO |
2009043643 | Apr 2009 | WO |
2012105889 | Aug 2012 | WO |
2013165297 | Nov 2013 | WO |
2013171089 | Nov 2013 | WO |
2013187834 | Dec 2013 | WO |
2013187839 | Dec 2013 | WO |
2014003630 | Jan 2014 | WO |
2014029492 | Feb 2014 | WO |
2014137270 | Sep 2014 | WO |
2014145918 | Sep 2014 | WO |