Method and apparatus for primary driver verification

Information

  • Patent Grant
  • 9789788
  • Patent Number
    9,789,788
  • Date Filed
    Friday, January 18, 2013
    11 years ago
  • Date Issued
    Tuesday, October 17, 2017
    7 years ago
  • CPC
  • Field of Search
    • US
    • 701 029600
    • 701 045000
    • 701 049000
    • CPC
    • B60N2/0232
    • B60N2/0244
    • B60N2/0248
    • B60N2/0252
    • B60N2/02
    • B60Q2300/112
    • B60R21/013
    • B60R21/0132
    • B60R21/0134
    • B60R21/015
    • B60R2021/01516
  • International Classifications
    • B60N2/02
    • Term Extension
      692
Abstract
A system includes a processor configured to examine one or more vehicle settings having been changed after a driver enters a vehicle. Also, the processor is configured to compare the examined settings to settings associated with currently stored driver profiles and verify the driver as a previously stored primary vehicle driver based at least in part on the comparison.
Description
TECHNICAL FIELD

The illustrative embodiments generally relate to a method and apparatus for primary driver verification.


BACKGROUND

Modern vehicle technologies offer unprecedented opportunities for customization. For instance, drivers can set their preferred seating positions, lumbar support, and steering wheel tilts, not to mention ever increasing on-board infotainment features ranging from center stack/cluster display appearance and radio station presets to the adaptive cruise control gap and lane-keeping aid sensitivity. The concept of customization can also be extended to information services and delivery, ranging from customized news coverage and music play lists to traffic information tailored to frequently visited POI (Points of Interest). While some of the features can be set once and remain valid for a long period of time, such as infotainment system's unit of measure (e.g., metric vs. English), others require frequent updates because of various changing factors.


One of the very important such factors is the driver. If the vehicle knows who is driving, it would be possible to tailor the vehicle seamlessly to the driver preferences.


SUMMARY

In a first illustrative embodiment, a system includes a processor configured to examine one or more vehicle settings having been changed after a driver enters a vehicle. Also, the processor is configured to compare the examined settings to settings associated with currently stored driver profiles and verify the driver as a previously stored primary vehicle driver based at least in part on the comparison.


In a second illustrative embodiment, a computer-implemented method includes examining one or more vehicle settings having been changed after a driver enters a vehicle. The method also includes comparing the examined settings to settings associated with currently stored driver profiles and verifying the driver as a previously stored primary vehicle driver based at least in part on the comparison.


In a third illustrative embodiment, a non-transitory computer-readable storage medium stores instructions that, when executed by a processor, cause the processor to perform the method including examining one or more vehicle settings having been changed after a driver enters a vehicle. The method also includes comparing the examined settings to settings associated with currently stored driver profiles and verifying the driver as a previously stored primary vehicle driver based at least in part on the comparison.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows an illustrative vehicle computing system;



FIG. 2 shows an illustrative process for driver profile creation;



FIG. 3 shows an illustrative process for data collection and updating;



FIG. 4 shows an illustrative process for driver verification; and



FIG. 5 shows another illustrative process for driver verification.





DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.



FIG. 1 illustrates an example block topology for a vehicle based computing system 1 (VCS) for a vehicle 31. An example of such a vehicle-based computing system 1 is the SYNC system manufactured by THE FORD MOTOR COMPANY. A vehicle enabled with a vehicle-based computing system may contain a visual front end interface 4 located in the vehicle. The user may also be able to interact with the interface if it is provided, for example, with a touch sensitive screen. In another illustrative embodiment, the interaction occurs through, button presses, audible speech and speech synthesis.


In the illustrative embodiment 1 shown in FIG. 1, a processor 3 controls at least some portion of the operation of the vehicle-based computing system. Provided within the vehicle, the processor allows onboard processing of commands and routines. Further, the processor is connected to both non-persistent 5 and persistent storage 7. In this illustrative embodiment, the non-persistent storage is random access memory (RAM) and the persistent storage is a hard disk drive (HDD) or flash memory.


The processor is also provided with a number of different inputs allowing the user to interface with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24 and a BLUETOOTH input 15 are all provided. An input selector 51 is also provided, to allow a user to swap between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor. Although not shown, numerous of the vehicle components and auxiliary components in communication with the VCS may use a vehicle network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).


Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9. Output can also be made to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.


In one illustrative embodiment, the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., cell phone, smart phone, PDA, or any other device having wireless remote network connectivity). The nomadic device can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, tower 57 may be a WiFi access point.


Exemplary communication between the nomadic device and the BLUETOOTH transceiver is represented by signal 14.


Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.


Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with nomadic device 53. Alternatively, it may be desirable to include an onboard modem 63 having antenna 18 in order to communicate 16 data between CPU 3 and network 61 over the voice band. The nomadic device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, the modem 63 may establish communication 20 with the tower 57 for communicating with network 61. As a non-limiting example, modem 63 may be a USB cellular modem and communication 20 may be cellular communication.


In one illustrative embodiment, the processor is provided with an operating system including an API to communicate with modem application software. The modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device). Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols. IEEE 802 LAN (local area network) protocols include WiFi and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle. Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.


In another embodiment, nomadic device 53 includes a modem for voice band or broadband data communication. In the data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of with Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domain Multiple Access (SDMA) for digital cellular communication. These are all ITU IMT-2000 (3G) compliant standards and offer data rates up to 2 mbs for stationary or walking users and 385 kbs for users in a moving vehicle. 3G standards are now being replaced by IMT-Advanced (4G) which offers 100 mbs for users in a vehicle and 1 gbs for stationary users. If the user has a data-plan associated with the nomadic device, it is possible that the data-plan allows for broad-band transmission and the system could use a much wider bandwidth (speeding up data transfer). In still another embodiment, nomadic device 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31. In yet another embodiment, the ND 53 may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802.11g network (i.e., WiFi) or a WiMax network.


In one embodiment, incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3. In the case of certain temporary data, for example, the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.


Additional sources that may interface with the vehicle include a personal navigation device 54, having, for example, a USB connection 56 and/or an antenna 58, a vehicle navigation device 60 having a USB 62 or other connection, an onboard GPS device 24, or remote navigation system (not shown) having connectivity to network 61. USB is one of a class of serial networking protocols. IEEE 1394 (firewire), EIA (Electronics Industry Association) serial protocols, IEEE 1284 (Centronics Port), S/PDIF (Sony/Philips Digital Interconnect Format) and USB-IF (USB Implementers Forum) form the backbone of the device-device serial standards. Most of the protocols can be implemented for either electrical or optical communication.


Further, the CPU could be in communication with a variety of other auxiliary devices 65. These devices can be connected through a wireless 67 or wired 69 connection. Auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, and the like.


Also, or alternatively, the CPU could be connected to a vehicle based wireless router 73, using for example a WiFi 71 transceiver. This could allow the CPU to connect to remote networks in range of the local router 73.


In addition to having exemplary processes executed by a vehicle computing system located in a vehicle, in certain embodiments, the exemplary processes may be executed by a computing system in communication with a vehicle computing system. Such a system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device. Collectively, such systems may be referred to as vehicle associated computing systems (VACS). In certain embodiments particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system. By way of example and not limitation, if a process has a step of sending or receiving information with a paired wireless device, then it is likely that the wireless device is not performing the process, since the wireless device would not “send and receive” information with itself. One of ordinary skill in the art will understand when it is inappropriate to apply a particular VACS to a given solution. In all solutions, it is contemplated that at least the vehicle computing system (VCS) located within the vehicle itself is capable of performing the exemplary processes.


Modern vehicle technologies offer unprecedented opportunities for customization. For instance, drivers can set their preferred seating positions, lumbar support, steering wheel tilts, center/stack cluster appearance, radio station presets, adaptive cruise control gap, lane-keeping aid sensitivity, etc. Customization can also be extended to information services and delivery, ranging from customized news coverage and music play lists to traffic information tailored to frequently visited points of interest (POIs). While some of the features can be set once and remain valid for a long period of time, others may require frequent changes due to various changing factors.


One common “changing factor” is the vehicle driver. If the vehicle knows who is driving, it would be possible to tailor the vehicle seamlessly to the driver preferences. For instance, as soon as the driver sits down in the vehicle and starts the engine, the vehicle could adjust the seat position, pedal positions, steering wheel tilt, climate control settings, driving mode, radio station presets, etc., based on registered driver preferences. In such a case, the driver may not even need to press a button or enter a request for settings changes, the vehicle “knows” who is driving and prepares the environment as the driver prefers.


When a vehicle is first delivered to a customer, the driver can be asked a few questions in an initialization phase. These can include, for example, whether or not to store presets and preferences, and for a profile name. The profile will correspond to a default driver.


In one embodiment, the vehicle will have one or more “primary” drivers. These include people who commonly use the vehicle. The vehicle also may have one or more secondary drivers, which correspond to people who may, for example, occasionally borrow the vehicle. In this example, the vehicle is able to use the illustrative embodiments to verify a member of the primary group and provide settings based on that verification.


After an initialization phase, data can be collected continuously during the usage of the vehicle for development of user profiles. This data can not only be used to set the vehicle to the desired preferences when a driver is verified, but the data itself can be used to verify a driver, as shown in the illustrative embodiments. Data can include, but is not limited to, seat positions, steering wheel tilt, mirror positions, pedal positions, driver weight, climate control settings, climate control settings, radio station tuning, route selection, operation data, shifting styles, driver voice signature, facial images, GPS data (preferences, predictions, etc.), driver smartphone controls, etc.



FIG. 2 shows an illustrative process for driver profile creation. In this example, a new driver may be added to the vehicle. If a driver profile doesn't exist, or if the driver isn't recognized by the vehicle (after a certain measure of analysis, for example), the process may attempt to create a new profile 201.


First, in this example, the process queries the driver to determine if the present driver is a primary driver of the vehicle. The driver doesn't necessarily need to benefit from the vehicle remembering setting information. In this illustrative example, the process determines if there is any primary driver set at all 203. If there isn't, the process initiates a user profile 209. Similarly, even if there is a primary driver, the process asks if the driver is an additional primary driver 205. If so, the process also initiates a profile for the new primary driver.


If the driver is not a primary driver, the process may gather data for a secondary driver 207. In this example, if a secondary driver is using the vehicle, the process may provide a “common” set of interfaces and vehicle environmental settings. Since the settings are for general use by vehicle borrowers, the process may gather data from secondary drivers to provide a secondary profile that is representative of the aggregate choices of secondary users. In another example, the process may simply provide a factory preset secondary setting, for example.


In the event of a primary (or in this case, secondary) driver, the process may collect some basic data about the driver 211. This can be as simple as asking the driver to provide a profile identification. It could also include, for example, recording seat weight sensor data, recording facial profile data, etc. This could be especially useful with respect to primary drivers.


Once any initialization data has been gathered, the process may begin data gathering 213, to record information based on what the driver enters/changes during a trip.



FIG. 3 shows an illustrative process for data collection and updating. As previously mentioned, the processes described herein may gather and adjust vehicle settings to a variety of driver-preferred standards. Since this data may change over time, even for a particular driver, the process may need to track changes in the data. In this example, both “fixed” and variable settings are considered.


The fixed settings are not technically “fixed,” but are settings that are typically left alone once set. These include, but are not limited to, seat settings, mirror settings, radio presets, etc. The variable settings, on the other hand, correspond to things that commonly change over a drive, such as radio volume, temperature settings, etc. Even if these variables commonly change over a drive, they may have typical settings in the average, or may change in a predictable manner.


Once data tracking has begun 301, the process determines if a change has been detected to a fixed setting 303 or a variable setting 313. If no discernible change has been made to either setting, the process will continue to monitor for changes to either setting type.


If a change to a fixed setting, for example, has been detected 303, the process determines if a time period of some predetermined amount has elapsed 305. Since the setting could have been briefly changed, or the change could be detected during the process of changing the setting (but the setting having not yet reached a final setting), the process may not record/register a detected change until after a predetermined time period has passed.


While the time is passing, the process may also determine if the detected change remains 307. In this manner, if the process detects a change in progress, but that has not reached a final setting, then the change (to the intermediate setting) should not remain over the pre-determined period of time. Accordingly, until the change reaches a setting for which it remains for some period of time, the process will ignore the intermediate changes and continue to look for a finalization of the change.


If the change has remained for the predetermined period of time, the process has to determine whether or not to update the setting 309. This could be a decision of the vehicle system itself, or it could be a result of asking a driver if the new setting should be saved to replace the old setting. If the update has been requested/decided on, the process will change the setting 311. In some cases, the process may determine that an aggregate setting should be used, in other cases the process can merely adopt the new setting.


In another case, the process determines if a variable setting (such as volume) has changed. Variable settings are often affected by vehicle/environmental context. For example, a loud environment could cause a user to increase radio volume. A cold environment could cause a user to increase temperature. Since the context may have bearing on the variable, the process may track and even record the context so that the vehicle can apply certain changes based on correspondences to environment.


Once context data has been gathered (either generally all available context data, or data relating to the changed variable), the process again attempts to determine if a predetermined time period has elapsed 317. As with the fixed settings, it may only be desirable to record a change in data if some time period has elapsed, although the time period may be different for the fixed versus variable settings. If the time period has not elapsed, and the setting still remains 319, the process continues waiting for the predetermined amount of time to elapse. If, however, the setting changes, before the time is up, the process continues monitoring for changes to a setting.


As with the fixed settings, if the time period elapses and the setting has been maintained, the process must decide whether an update is in order. If the update is appropriate, the process will update the settings and make any adjustments to context variables associated with those settings. Context variables can also be associated with fixed settings, although it is more likely that they will be associated with these variable settings, since these are elements that commonly change over the course of a journey, often in reaction to an environmental event.



FIG. 4 shows an illustrative process for driver verification. In this illustrative example, the process describes a primary driver verification system (PDVS) 407. The PDVS tracks the driver interaction with interior features, settings, vehicle preferences and verifies who the driver is based on one or more decision systems and/or algorithms.


Once the driver has been verified, the PDVS can set vehicle preferences with a relative degree of confidence. The PDVS consists of a number of primary driver verifiers PDVs. The PDVs are collected from a number of information services, such as, but not limited to, driver and interior features 401, vehicle response 403, additional driver based information sources 405, etc.


Example PDVs include, but are not limited to Driver Positioning Verifier (DPV) 409, Driver Interior Setting Verifier (DISV) 411, Driver Style Verifier (DSV) 413, etc. 415. These PDVs are based on data gathered from the numerous vehicle systems and feedback processes provided to the vehicle. Any point where the driver interacts with the vehicle, data can be gathered and used for driver verification if appropriate.


The output (or settings of) the various PDVs aggregate to determine which of the primary drivers are operating the vehicle 417. In some cases, depending on the number of drivers and inputs, the aggregation determination could be determined after only one or two variable inputs. If, for example, there were only two drivers of a vehicle, there are likely a number of easily discernible differences. On the other hand, if the two drives were twins of relatively similar weights, for example, the process may require more inputs to determine which of the twins is driving at a given time.


Once a particular driver has been verified, the process can then proceed with feature and function customization based on the preferences of the verified driver. The process can also monitor and update changes to fixed or variable settings.



FIG. 5 shows another illustrative process for driver verification. This process describes in greater detail one exemplary manner for verifying a driver. In this example, the process uses one or more DPV inputs such as, but not limited to, memory seat positions, steering wheel tilt, mirror positions, pedal positions, etc. Once a drive has begun, the process can gather and analyze data 501. Once the drive has begun 501, it is assumed that the seats and mirrors are likely in the proper position to use one or more of these as driver verification data points.


In one example, a seat position could be used as an example for driver verification. For example, over a period of time, it could be observed that driver A has a mean seat position of 30 cm with a standard deviation of 2 cm, while driver B has a mean seat position of 40 cm with a standard deviation of 1.5 cm. Similar likelihood and frequency distribution data may be computed for additional DPVs. The likelihood of various DPVs for a particular driver can be combined to provide a DPV input component to a verification equation 503.


Another source of verification data may include driver interior setting verifiers (DISVs). These examples include, for instance, climate control settings, radio station tuning, etc. For example, if climate temperature targets were used for verification, climate target setting data and probability data may be gathered 505. This can be compared to data gathered over a number of drive cycles.


For example, driver A may have a mean target setting of 70 degrees with a standard deviation of 2 degrees, and driver B may have a mean target setting of 68 degrees with a standard deviation of 3 degrees.


Yet another piece/pieces of usable information may include driving style verifiers (DSVs). These can be gathered 507 based on observed driving behavior, such as braking habits, acceleration habits, etc. For any given feature, the feature dependent PDV aggregation to obtain the overall likelihood of a verified driver may be given by:







PDV
j

=





i
=
1

N








w
i



y
i







i
=
1

N







w
i







Where:


j=number of drivers to verify (e.g., number of primary drivers);


PDVj=the aggregated likelihood of a driver verified value (0-1)


N=the number of PDVs


yi=PDV values for a potential driver


wi=weight attributed to each PDV indicator


For example, using the exemplary PDVs described herein, DPV, DISV and DSV, along with 2-stage driver verification (A,B; where A and B are the potential drivers), the likelihood of the driver being driver A is given by:







PDV
A

=




DPV
A



w
DPV


+


DISV
A



w
DISV


+


DSV
A



w
DSV





w
DPV

+

w
DISV

+

w
DSV







and the likelihood of the driver being driver B is given by:







PDV
B

=




DPV
B



w
DPV


+


DISV
B



w
DISV


+


DSV
B



w
DSV





w
DPV

+

w
DISV

+

w
DSV







When a tunable minimum PDV threshold is achieved, the particular driver can be verified based on the highest PDV value. Feature, function settings and recommendations are then provided based on the verified driver. The illustrative embodiments can modify a number of vehicle settings and HMI settings, including, but not limited to, HMI displays (radio presets, for example), physical system settings (seat/wheel/mirror presets), airbag deployment pressure, adaptive vehicle modes, climate controls, etc.


While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.

Claims
  • 1. A system comprising: a processor configured to:record data relating to drive style after a vehicle is in motion;compare the drive style to drive styles associated with currently stored driver profiles; andverify the driver as a previously stored primary vehicle driver based at least in part on the comparison.
  • 2. The system of claim 1, wherein the processor is further configured to repeat the examining and comparing until a likelihood of a given driver exceeds a predetermined threshold.
  • 3. The system of claim 1, wherein the processor is further configured to tailor features and functions of HMI displays, vehicle physical system settings, adaptive vehicle modes, and climate controls based on the verified driver.
  • 4. A computer-implemented method comprising: recording data relating to drive style after a vehicle is in motion;comparing the drive style to drive styles associated with currently stored driver profiles, via a vehicle-associated computer; andverifying the driver as a previously stored primary vehicle driver based at least in part on the comparison.
  • 5. The method of claim 4, wherein the method further includes repeating the examining and comparing until a likelihood of a given driver exceeds a predetermined threshold.
  • 6. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the method comprising: recording data relating to drive style after a vehicle is in motion;comparing the drive style to drive styles associated with currently stored driver profiles; andverifying the driver as a previously stored primary vehicle driver based at least in part on the comparison.
  • 7. The storage medium of claim 6, wherein the method further includes repeating the examining and comparing until a likelihood of a given driver exceeds a predetermined threshold.
US Referenced Citations (179)
Number Name Date Kind
6028537 Suman et al. Feb 2000 A
6278772 Bowater et al. Aug 2001 B1
6385535 Ohishi et al. May 2002 B2
6411899 Dussell Jun 2002 B2
6430488 Goldman et al. Aug 2002 B1
6438472 Tano Aug 2002 B1
6459969 Bates et al. Oct 2002 B1
6505780 Yassin et al. Jan 2003 B1
6600975 Moriguchi et al. Jul 2003 B2
6629033 Preston et al. Sep 2003 B2
6728349 Chang et al. Apr 2004 B2
6845251 Everhart et al. Jan 2005 B2
6928428 De Vries Aug 2005 B1
6993490 Chen et al. Jan 2006 B2
7065533 Arrouye et al. Jun 2006 B2
7120928 Sheth et al. Oct 2006 B2
7127259 Ueda et al. Oct 2006 B2
7129825 Weber Oct 2006 B2
7139722 Perrella et al. Nov 2006 B2
7142664 Seligmann Nov 2006 B2
7143058 Sugimoto et al. Nov 2006 B2
7145998 Holder et al. Dec 2006 B1
7162237 Silver et al. Jan 2007 B1
7283813 Hamanaga et al. Oct 2007 B2
7340691 Bassett et al. Mar 2008 B2
7346630 Eichstaedt Mar 2008 B2
7370079 Murata et al. May 2008 B2
7376226 Holder et al. May 2008 B2
7433714 Howard et al. Oct 2008 B2
7444384 Horvitz Oct 2008 B2
7469827 Katragadda et al. Dec 2008 B2
7474264 Bolduc et al. Jan 2009 B2
7535344 Obradovich May 2009 B2
7552009 Nelson Jun 2009 B2
7574195 Krasner et al. Aug 2009 B2
7586956 Mishra et al. Sep 2009 B1
7725480 Bassett et al. May 2010 B2
7747246 Zellner et al. Jun 2010 B2
7801283 Harwood et al. Sep 2010 B2
7813950 Perrella et al. Oct 2010 B2
7864029 Huang Jan 2011 B2
7889096 Breed Feb 2011 B2
7917285 Rothschild Mar 2011 B2
7985911 Oppenheimer Jul 2011 B2
8112720 Curtis Feb 2012 B2
8126889 Pitt Feb 2012 B2
8223975 Marko Jul 2012 B2
8233890 Zellner et al. Jul 2012 B2
8301108 Naboulsi Oct 2012 B2
8316046 Huang et al. Nov 2012 B2
20010037174 Dickerson Nov 2001 A1
20020068583 Murray Jun 2002 A1
20020107032 Agness et al. Aug 2002 A1
20020143879 Sommerer Oct 2002 A1
20030131023 Bassett et al. Jul 2003 A1
20030212480 Lutter et al. Nov 2003 A1
20040073643 Hayes et al. Apr 2004 A1
20040090121 Simonds et al. May 2004 A1
20040092253 Simonds et al. May 2004 A1
20040093154 Simonds et al. May 2004 A1
20040093155 Simonds et al. May 2004 A1
20040192270 Kreitzer Sep 2004 A1
20040220768 Klein Nov 2004 A1
20040254715 Yamada Dec 2004 A1
20040268270 Hill et al. Dec 2004 A1
20050019228 Myers et al. Jan 2005 A1
20050088284 Zai et al. Apr 2005 A1
20050119030 Bauchot et al. Jun 2005 A1
20050149520 De Vries Jul 2005 A1
20050222933 Wesby Oct 2005 A1
20060058948 Blass et al. Mar 2006 A1
20060071804 Yoshioka Apr 2006 A1
20060165015 Melick et al. Jul 2006 A1
20060168627 Zeinstra et al. Jul 2006 A1
20060258377 Economos Nov 2006 A1
20060290490 Kraus et al. Dec 2006 A1
20070004387 Gadamsetty et al. Jan 2007 A1
20070016362 Nelson Jan 2007 A1
20070042812 Basir Feb 2007 A1
20070044037 Amari et al. Feb 2007 A1
20070053513 Hoffberg Mar 2007 A1
20070061067 Zeinstra et al. Mar 2007 A1
20070120948 Fujioka et al. May 2007 A1
20070140187 Rokusek et al. Jun 2007 A1
20070233725 Michmerhuizen et al. Oct 2007 A1
20070238491 He Oct 2007 A1
20070264990 Droste et al. Nov 2007 A1
20070281603 Nath et al. Dec 2007 A1
20070285256 Batra Dec 2007 A1
20070294304 Bassett et al. Dec 2007 A1
20070299882 Padgett et al. Dec 2007 A1
20080005680 Greenlee Jan 2008 A1
20080036580 Breed Feb 2008 A1
20080057927 Han Mar 2008 A1
20080086455 Meisels et al. Apr 2008 A1
20080140488 Oral et al. Jun 2008 A1
20080143497 Wasson et al. Jun 2008 A1
20080150685 Desai et al. Jun 2008 A1
20080159503 Helbling et al. Jul 2008 A1
20080255722 McClellan Oct 2008 A1
20080263069 Harris et al. Oct 2008 A1
20080281518 Dozier et al. Nov 2008 A1
20080294483 Williams Nov 2008 A1
20080294663 Heinley et al. Nov 2008 A1
20080319653 Moshfeghi Dec 2008 A1
20080319665 Berkobin et al. Dec 2008 A1
20090002145 Berry et al. Jan 2009 A1
20090005966 McGray et al. Jan 2009 A1
20090011799 Douthitt et al. Jan 2009 A1
20090056525 Oppenheimber Mar 2009 A1
20090074168 Henry Mar 2009 A1
20090075624 Cox et al. Mar 2009 A1
20090094088 Chen et al. Apr 2009 A1
20090111422 Bremer et al. Apr 2009 A1
20090112608 Abu-Hakima et al. Apr 2009 A1
20090144622 Evans et al. Jun 2009 A1
20090157615 Ross et al. Jun 2009 A1
20090157717 Palahnuk et al. Jun 2009 A1
20090158200 Palahnuk et al. Jun 2009 A1
20090193149 Khosravy Jul 2009 A1
20090248285 Baur Oct 2009 A1
20090267757 Nguyen Oct 2009 A1
20090284359 Huang Nov 2009 A1
20090312901 Miller et al. Dec 2009 A1
20100017543 Preston et al. Jan 2010 A1
20100062714 Ozaki Mar 2010 A1
20100086112 Jiang et al. Apr 2010 A1
20100087987 Huang Apr 2010 A1
20100125801 Shin May 2010 A1
20100136944 Taylor et al. Jun 2010 A1
20100148920 Philmon et al. Jun 2010 A1
20100152950 Chin Jun 2010 A1
20100159964 Ferro Jun 2010 A1
20100169432 Santori, Jr. et al. Jul 2010 A1
20100209881 Lin Aug 2010 A1
20100209882 Lin Aug 2010 A1
20100209892 Lin Aug 2010 A1
20100210302 Santori et al. Aug 2010 A1
20100227629 Cook et al. Sep 2010 A1
20100228803 Quinn Sep 2010 A1
20100233957 Dobosz Sep 2010 A1
20100235891 Oglesbee et al. Sep 2010 A1
20100274689 Hammad et al. Oct 2010 A1
20100274865 Frazier et al. Oct 2010 A1
20100287024 Ward et al. Nov 2010 A1
20100323657 Barnard et al. Dec 2010 A1
20100330975 Basir Dec 2010 A1
20110021234 Tibbitts et al. Jan 2011 A1
20110039581 Cai et al. Feb 2011 A1
20110040707 Theisen et al. Feb 2011 A1
20110045810 Issa et al. Feb 2011 A1
20110072492 Mohler et al. Mar 2011 A1
20110087705 Swink et al. Apr 2011 A1
20110121991 Basir May 2011 A1
20110137520 Rector et al. Jun 2011 A1
20110137773 Davis, III et al. Jun 2011 A1
20110144980 Rysenga Jun 2011 A1
20110176670 Kaplan et al. Jul 2011 A1
20110257881 Chen et al. Oct 2011 A1
20110289522 Pontual et al. Nov 2011 A1
20110298924 Miller et al. Dec 2011 A1
20110300843 Miller et al. Dec 2011 A1
20110300884 Ollila et al. Dec 2011 A1
20120010805 Wilkerson Jan 2012 A1
20120041633 Schunder et al. Feb 2012 A1
20120044089 Yarnold et al. Feb 2012 A1
20120050028 Mastronardi et al. Mar 2012 A1
20120053793 Sala Mar 2012 A1
20120130953 Hind et al. May 2012 A1
20120149441 Saito et al. Jun 2012 A1
20120158658 Wilkerson Jun 2012 A1
20120158918 LeBlanc et al. Jun 2012 A1
20120172009 Wilkerson Jul 2012 A1
20120202525 Pettini Aug 2012 A1
20120225677 Forstall et al. Sep 2012 A1
20120271676 Aravamudan et al. Oct 2012 A1
20120272176 Nielsen et al. Oct 2012 A1
20130024109 Hosotani et al. Jan 2013 A1
20130124085 Mochizuki et al. May 2013 A1
Foreign Referenced Citations (6)
Number Date Country
1969458 Sep 2008 EP
2470147 Nov 2010 GB
2007205872 Aug 2007 JP
2008172820 Jul 2008 JP
03107129 Dec 2003 WO
2011016886 Feb 2011 WO
Non-Patent Literature Citations (1)
Entry
Search Report for German Applications 102011089349.0 (corresponding DE appln) dated Jan. 8, 2013, 7 pgs.
Related Publications (1)
Number Date Country
20140207342 A1 Jul 2014 US