Gesture access system for a motor vehicle

A gesture access system includes at least one ultra wide band transceiver to be mounted to a motor vehicle, and a processor to operate in either of (i) a gesture access mode to control an actuator associated with an access closure of the motor vehicle to lock, unlock, open or close the access closure in response to an object within a sensing region of the at least one UWB transceiver exhibiting a predefined gesture, and (ii) an inactive mode in which the at least one processor does not receive or does not act on UWB radiation detection signals, the at least one processor to operate in the gesture access mode in response to known mobile communication device being within a perimeter defined about the motor vehicle, and to otherwise operate in the inactive mode.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to motor vehicle-mounted wireless access systems and, more particularly, to such systems in which transmitted and reflected wireless signals are used to detect the presence of an in-range mobile device and to then detect a predefined gesture for unlocking and/or opening at least one vehicle closure.

BACKGROUND

Many vehicles today are equipped with a passive entry system, or “PES.” In some PES implementations, a key fob communicates with a computer of the motor vehicle, and the motor vehicle computer operates to automatically unlock one or more door locks of the motor vehicle in response to detection of the key fob being in close proximity to the motor vehicle. This allows an operator of the vehicle to approach the vehicle and open the door without having to manually unlock the door with a key or to manually press a button on the key fob. In some such applications, the motor vehicle computer is also configured to automatically lock the vehicle in response to detection of the key fob being outside of the close proximity of the motor vehicle.

Another known type of hands-free vehicle access or entry system employs an infrared (“IR”) detector assembly. Typically, such systems may use an active near infrared arrangement including multiple IR LEDs and one or more sensors in communication with a computer or other circuitry. The computer is typically operable in such an assembly to calculate the distance of an object from the assembly by timing the interval between emission of IR radiation and reception by the sensor(s) of at least a portion of the emitted IR radiation that is reflected by the object back to the sensor(s), and then interpreting the timing information to determine movement of the object within the IR field. Exemplary IR movement recognition systems are disclosed in US Patent Application Publication 20120200486, US Patent Application Publication 20150069249, and US Patent Application Publication 20120312956, and US Patent Application Publication 20150248796, the disclosures of which are incorporated herein by reference in their entireties.

SUMMARY

This disclosure comprises one or more of the features recited in the attached claims, and/or one or more of the following features and any combination thereof. In one aspect, a gesture access system for a motor vehicle may comprise at least one ultra wide band (UWB) transceiver configured to be mounted to the motor vehicle, the at least one UWB transceiver responsive to activation signals to emit UWB radiation signals outwardly away from the motor vehicle, and to produce UWB radiation detection signals, the UWB radiation detection signals including at least one reflected UWB radiation signal if at least one of the emitted UWB radiation signals is reflected by an object toward and detected by the at least one UWB transceiver, at least one processor, and at least one memory having instructions stored therein executable by the at least one processor to cause the at least one processor to: monitor a mobile device status signal produced by a control computer of the motor vehicle or by the at least one processor based on a determination by the control computer or the at least one processor of a proximity, relative to the motor vehicle, of a mobile communication device known to the control computer or to the at least one processor, in response to the mobile device status signal corresponding to the known mobile communication device being within a perimeter defined about the motor vehicle, operate in a gesture access mode by processing the activation and UWB radiation detection signals to determine whether an object is within a sensing region of the at least one UWB transceiver and, upon determining that the object is within the sensing region, controlling at least one actuator associated with an access closure of the motor vehicle to lock, unlock, open or close the access closure in response to the object within the sensing region exhibiting a predefined gesture, and in response to the mobile device status signal corresponding to the known mobile communication device being beyond the perimeter defined about the motor vehicle, operate in an inactive mode in which the at least one processor does not receive or does not act on UWB radiation detection signals.

In another aspect, a gesture access system for a motor vehicle, may comprise at least one ultra wide band (UWB) transceiver configured to be mounted to the motor vehicle, the at least one UWB transceiver responsive to activation signals to emit UWB radiation signals outwardly away from the motor vehicle, and to produce UWB radiation detection signals, the UWB radiation detection signals including at least one reflected UWB radiation signal if at least one of the emitted UWB radiation signals is reflected by an object toward and detected by the at least one UWB transceiver, at least one processor, and at least one memory having instructions stored therein which, when executed by the at least one processor, cause the at least one processor to be operable in either of (i) a gesture access mode to control an actuator associated with an access closure of the motor vehicle to lock, unlock, open or close the access closure in response to an object within a sensing region of the at least one UWB transceiver exhibiting a predefined gesture, and (ii) an inactive mode in which the at least one processor does not receive or does not act on UWB radiation detection signals, the at least one memory further having instructions stored therein executable by the at least one processor to cause the at least one processor to operate in the gesture access mode upon determining by the control computer or the at least one processor that a mobile communication device known to the control computer or the at least one processor is within a perimeter defined about the motor vehicle, and to cause the at least one processor to operate in the inactive mode upon determining by the control computer or the at least one processor that the known mobile communication device is outside of a perimeter defined about the motor vehicle.

DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS

For the purposes of promoting an understanding of the principles of this disclosure, reference will now be made to a number of illustrative embodiments shown in the attached drawings and specific language will be used to describe the same.

This disclosure relates to object detection system mountable to or carried by a motor vehicle in any of various locations at or about the motor vehicle. In some embodiments, the object detection system may implemented solely in the form of a hands-free vehicle access system. In some such embodiments, one or more illumination devices may be implemented to provide visual feedback of objects being detected. In other embodiments, the object detection system may be implemented in the form of a combination hands-free vehicle access system and an object impact avoidance system. In such embodiments, the object detection system operates in a hands-free vehicle access mode under some conditions and in an object impact avoidance mode under other operating conditions.

Referring now toFIG. 1, an embodiment of an object detection system10is shown. The object detection system10illustratively includes an object detection module12having at least one processor or controller14, at least one memory16and a communication circuit18for receiving vehicle access signals wirelessly transmitted by a transmitter22of a key fob20. The object detection module12further illustratively includes object detection circuitry, and various example embodiments of such object detection circuitry will be described below with respect toFIGS. 2, 6A, 7 and 8.

In some embodiments, the object detection system10may include a vehicle control computer24electrically connected to the object detection module12and having at least one processor or controller26and at least one memory28. In some embodiments, the vehicle control computer24may include a communication circuit30for receiving the vehicle access signals wirelessly transmitted by the transmitter22of the key fob20. In some embodiments, the communication circuit18of the object detection module12and the communication circuit30of the vehicle control computer24may be configured to wirelessly communicate with one another in a conventional manner so that the processors14,26may conduct information transfer wirelessly via the communication circuits18,30.

In some embodiments, the object detection system10may include one or more actuator driver circuits40for controllably driving one or more corresponding actuators46. In some such embodiments, the one or more actuator driver circuits40may include at least one processor or controller42and at least one memory44in addition to one or more conventional driver circuits, although in other embodiments the processor or controller42and the memory44may be omitted. In some embodiments, one, some or all of the one or more driver circuits40may be electrically connected to the vehicle control computer24so that the processor or controller26of the vehicle control computer24may control the operation of one or more actuators46via control of such one or more driver circuits40. Alternatively or additionally, at least one, some or all of the one or more driver circuits40may be electrically connected to the object detection module12as illustrated by dashed-line connection inFIG. 1, so that the processor or controller14of the object detection module12may control operation of one or more actuators46via control of such one or more driver circuits40. In any case, the one or more actuators46are operatively coupled to one or more conventional, actuatable devices, mechanisms and/or systems48. Examples of such actuators and actuatable devices, mechanisms and/or systems may include, but are not limited to, one or more electronically controllable motor vehicle access closure locks or locking systems, one or more electronically controllable motor vehicle access closure latches or latching systems, an automatic (i.e., electronically controllable) engine ignition system, an automatic (i.e., electronically controllable) motor vehicle braking system, an automatic (i.e., electronically controllable) motor vehicle steering system, an automated (i.e., electronically controllable) motor vehicle driving system (e.g., “self-driving” or “autonomous driving” system), and the like.

In some embodiments, the object detection system10may include one or more conventional vehicle operating parameter sensors, sensing systems and/or switches50carried by the motor vehicle and electrically connected to, or otherwise communicatively coupled to, the vehicle control computer24. Examples of such vehicle operating parameter sensors, sensing systems and/or switches50may include, but are not limited to, an engine ignition sensor or sensing system, a vehicle speed sensor or sensing system, a transmission gear selector position sensor, sensing system or switch, a transmission gear position sensor, sensing system or switch, and the like.

In some embodiments, the object detection system10may include one or more conventional audio and/or illumination device driver circuits60for controllably driving one or more corresponding audio (or audible) devices and/or one or more illumination devices66. In some such embodiments, the one or more audio and/or illumination device driver circuits60may include at least one processor or controller62and at least one memory64in addition to one or more conventional driver circuits, although in other embodiments the processor or controller62and the memory64may be omitted. In some embodiments, one, some or all of the one or more driver circuits60may be electrically connected to the vehicle control computer24so that the processor or controller26of the vehicle control computer24may control the operation of one or more audio and/or illumination devices66via control of such one or more driver circuits60. Alternatively or additionally, at least one, some or all of the one or more driver circuits60may be electrically connected to the object detection module12as illustrated by dashed-line connection inFIG. 1, so that the processor or controller14of the object detection module12may control operation of one or more of the audio and/or illumination devices66via control of such one or more driver circuits60. In any case, examples of such audio devices may include, but are not limited to, one or more electronically controllable audible warning device or systems, one or more electronically controllable audio notification devices or systems, one or more electronically controllable audio voice messaging devices or systems, one or more electrically controllable motor vehicle horns, and the like. Examples of such illumination devices may include, but are not limited to, one or more exterior motor vehicle illumination device, one or more interior motor vehicle illumination devices, one or more warning illumination devices, and the like.

Referring now toFIG. 2, one example embodiment121is shown of the object detection module12illustrated inFIG. 1. In the illustrated embodiment, the object detection module121includes a radiation emission and detection assembly100electrically connected to the at least one processor or controller141via a number M of signal paths, wherein M may be any positive integer. The radiation emission and detection assembly100illustratively includes a plurality of radiation transmitters102in the form of an array of two or more infrared light-emitting diodes (“IR LEDs”), and a plurality of radiation detectors104in the form of an array of two or more infrared light sensors (“IR sensors”). The IR LEDs102are conventional and are configured to be responsive to control signals produced by the processor or controller141to emit radiation outwardly from the assembly100. The IR sensors104are likewise conventional and are configured to produce radiation detection signals. The radiation detection signals produced by the IR sensors104illustratively include reflected radiation signals if the emitted radiation is reflected by an object in a sensing region of the IR sensors104, in accordance with a time sequence in which one or more of the IR LEDs102is activated to emit radiation and at least a portion of such emitted radiation is reflected by the object toward and detected by at least one of the IR sensors104.

In the embodiment illustrated inFIG. 2, the plurality of IR LEDs102and the plurality of IR sensors104are arranged in pairs with each IR LED102emitting the IR radiation for detection by an associated IR sensor104paired therewith. In some such embodiments, an array of IR LEDs102and an array of IR sensors104of the radiation emission and detection assembly100may be provided together in the form of a preformed IR sensor module. In alternate embodiments, the plurality of IR LEDs102may be provided in the form of a preformed IR LED array. In some such embodiments, the plurality of IR sensors104may be provided individually and in other embodiments the plurality of IR sensors104may be provided in the form of an IR sensor array separate from the IR LED array. In still other alternate embodiments, the plurality of IR sensors104may be provided in the form of a preformed IR sensor array, and the plurality of IR LEDs102may be provided individually or in the form of an IR LED array. In embodiments in which the plurality of IR LEDs102is provided in the form of an array, such an array may be arranged linearly, e.g., in a continuous row. Likewise, in embodiments in which the plurality of IR sensors104is provided in the form of an array of IR sensors, such an array may be arrange linearly, e.g., in a continuous row. In the embodiment illustrated inFIG. 2for example, the IR LEDs102and the IR sensors104are both arranged in the form of linear arrays. In alternate embodiments in which the plurality of IR LEDs102is provide in the form of an array, and/or in which the plurality of IR sensors104is provided in the form of an array, either or both such arrays may be arranged non-linearly and/or non-continuously, e.g., in groups of two or more spaced apart LEDs and/or sensors.

Radiation emission and detection assemblies100are conventionally associated with processors or controllers141as depicted inFIG. 2, and at least one associated memory161includes conventional instructions which, when executed by the processor or controller141, cause the processor or controller141to determine from the IR sensor104such things as, without limitation, (a) when an object has been detected in a sensing region of the sensors104IR, (b) whether the object is of a predetermined type, and (c) whether the object has moved within the sensing region. Examples of known IR detector systems are disclosed in US Patent Application Publication 20120200486, US Patent Application Publication 20150069249, US Patent Application Publication 20120312956, and US Patent Application Publication 20150248796, the disclosures of which are incorporated herein by reference in their entireties.

In some embodiments, the IR LEDs102and IR sensors104illustratively take the form of an IR sensor module available from NEONODE, INC. (San Jose, Calif.). The modules typically contain multiple pairs of IR emitter LEDs102and IR sensors104for receiving reflected IR radiation. Such modules typically have a range of about 200 millimeters (mm) of off-surface detection and arranging IR LEDs102and the IR sensors104in pairs permits a higher resolution of detection. For instance, the assembly100of IR LEDs102and IR sensors104is capable of detecting the difference between a single finger and multiple fingers. As a result, the assembly100of IR LEDs102and IR sensors104is capable of detecting gesturing by a user's hand, for instance.

The embodiment of the object detection module121illustrated inFIG. 2further includes a plurality of illumination devices112. In some embodiments, the illumination devices112are spaced apart at least partially across the sensing region of the IR sensors104, and in other embodiments one or more of the illumination devices112may be positioned remotely from the sensing region. In some embodiments, the illumination devices112may be arranged in the form of a linear or non-linear array110of equally or non-equally spaced-apart illumination devices. In some embodiments, the plurality of illumination devices include at least one LED configured to emit radiation in the visible spectrum. In such embodiments, the at least one LED may be configured to produce visible light in a single color or in multiple colors. In alternate embodiments, the plurality of illumination sources may include one or more conventional non-LED illumination sources.

In the embodiment illustrated inFIG. 2, the plurality of illumination devices112is provided in the form of an array110of visible light LEDs equal in number to the number of IR LEDs102and arranged such that each visible light LED112is co-extensive with a respective one of the plurality of IR LEDs102paired with a corresponding IR sensor104. In the illustrated embodiment, each visible light LED112is positioned adjacent to and above a respective one of the plurality of IR LEDs102which is itself positioned adjacent to and above a respective paired one of the IR sensors104. In alternate embodiments, the visible light LEDs112, the IR LEDs102and the IR sensors104may be positioned in any order relative to one another and arranged horizontally, as shown inFIG. 2, vertically, diagonally or non-linearly. In some alternate embodiments, more or fewer visible light LEDs112than the IR LEDs102and/or the IR sensors104may be provided.

The one or more illumination devices112is/are illustratively included to provide visual feedback of one or more conditions relating to detection by the radiation emission and detection assembly100of an object within a sensing region of the assembly100. In one example embodiment, two illumination devices112may be provided for producing the desired visual feedback. In one implementation of this example embodiment, a first one of the illumination devices112may be configured and controlled to illuminate with a first color to visibly indicate the detected presence by the radiation emission and detection assembly100of an object within the sensing region, and the second illumination device112may be configured and controlled to illuminate with a second color, different from the first, to visibly indicate that the detected object exhibits a predefined gesture. In another example embodiment, three illumination devices112may be provided. In this embodiment, a first one of the illumination devices112may be controlled to illuminate with a first color to visibly indicate the detected presence of an object within an area of the sensing region in which the radiation emission and detection assembly100is unable determine whether the detected object exhibits a predefined gesture (e.g., the object may be within a sub-region of the sensing region which is too small to allow determination of whether the object exhibits the predefined gesture), a second one of the illumination devices112is controlled to illuminate with a second color to visibly indicate the detected presence of an object within an area of the sensing region in which the radiation emission and detection assembly100is able to determine whether the detected object exhibits a predefined gesture, and a third one of the illumination devices is controlled to illuminate with a third color to visibly indicate that the object within the sensing region is detected by the radiation emission and detection assembly100as exhibiting a predefined gesture.

In other embodiments, the one or more illumination devices112may include any number of illumination devices10. Multiple illumination devices112, for example, may be illuminated in one or more colors to provide a desired visual feedback. In any such embodiments, in one or more illumination devices112may be LEDs, and one or more such LEDs may illustratively be provided in the form of RGB LEDs capable of illumination in more than one color. According to this variant, it will be appreciated that positive visual indication of various modes of operation of the radiation emission and detection assembly100may be carried out in numerous different colors, with each such color indicative of a different state of operation of the object detection module121. As one non-limiting example, the color red may serve to indicate that the radiation emission and detection assembly100has detected an object (e.g., a hand or foot) within the sensing region, but is unable to determine whether the detected object is exhibiting a predefined gesture. The color green, in contrast, may serve to indicate that the detected object is exhibiting a predefined gesture and, consequently, that the predefined vehicle command associated with that predefined gesture (e.g., unlocking the vehicle closure, opening the vehicle closure, etc.) is being effected. In addition to green, other colors might be uniquely associated with different predefined commands. Thus, while green illumination might reflect that a closure for the vehicle is being unlocked, blue illumination, for example, may reflect that a fuel door latch has been opened, purple illumination may reflect that a window is being opened, etc.

In still other embodiments, in addition to or alternatively to color distinction, different operating modes, i.e., different detection modes, of the radiation emission and detection assembly100may be visually distinguished from one another by controlling the at least one illumination device112to switch on and off with different respective frequencies and/or duty cycles. In some embodiments which include multiple illumination devices112, the different operating modes of the radiation emission and detection assembly100may be additionally or alternatively distinguished visually from one another by activating different subsets of the multiple illumination devices112for different operating or detection modes, and/or by sequentially activating the multiple illumination devices112or subsets thereof with different respective activation frequencies and/or duty cycles.

The object detection module121further illustratively includes a number N of conventional supporting circuits (SC) and conventional driver circuits (DC)1141-114N, wherein N may be any positive integer. The supporting circuit(s) (SC) is/are each electrically connected to the processor or controller141, and may include one or more conventional circuits configured to support the operation of the processor or controller141and/or other electrical circuits and/or components of the object detection module121. Example supporting circuits may include, but are not limited to, one or more voltage supply regulation circuits, one or more capacitors, one or more resistors, one or more inductors, one or more oscillator circuits, and the like. The driver circuit(s) (DC) include one or more inputs electrically connected to the processor or controller141and one or more outputs electrically connected to the one or more illumination devices112and the plurality of IR LEDs104. The driver circuit(s) DC is/are conventional and is/are configured to be responsive to one or more control signals supplied by the processor or controller141to selectively drive, i.e., activate and deactivate, the plurality of IR LEDs102and the one or more illumination devices112.

It will be understood that the terms “processor” and “controller” used in this disclosure is comprehensive of any computer, processor, microchip processor, integrated circuit, or any other element(s), whether singly or in multiple parts, capable of carrying programming for performing the functions specified in the claims and this written description. The at least one processor or controller141may be a single such element which is resident on a printed circuit board with the other elements of the inventive access system. It may, alternatively, reside remotely from the other elements of the system. For example, but without limitation, the at least one processor or controller141may take the form of a physical processor or controller on-board the object detection module121. Alternately or additionally, the at least one processor or controller141may be or include programming in the at least one processor or controller26of the vehicle control computer24illustrated inFIG. 1. Alternatively or additionally still, the at least one processor or controller141may be or include programming in the at least one processor or controller42of the actuator driver circuit(s)40and/or in the at least one processor or controller62of the audio/illumination device driver circuit(s)60and/or in at least one processor or controller residing in any location within the motor vehicle in which the system10is located. For instance, and without limitation, it is contemplated that one or more operations associated with one or more functions of the object detection module121described herein may be carried out, i.e., executed, by a first microprocessor and/or other control circuit(s) on-board the object detection module121, while one or more operations associated with one or more other functions of the object detection module121described herein may be carried out, i.e., executed, by a second microprocessor and/or other circuit(s) remote from the object detection module121, e.g., such as the processor or controller26on-board the vehicle control computer24.

In the embodiment illustrated inFIG. 2, the IR LEDs102, the IR sensors104, the illumination devices112, the at least one processor or controller141and the supporting/driver circuits1141-114Nare all mounted to a conventional circuit substrate116which is mounted within a housing118. In some such embodiments, the IR LEDs102, IR sensors104and visible LEDs112may be combined and provided in the form of a radiation assembly or module120mounted to the circuit substrate116as illustrated by example inFIG. 2. In alternate embodiments, the circuit substrate116may be provided in the form of two or more separate circuit substrates, and in such embodiments one or more of the IR LEDs102, the IR sensors104, the illumination devices112, the at least one processor or controller141and the supporting/driver circuits1141-114Nmay be mounted to a first one of the two or more circuit substrates and remaining one(s) of the one or more of the IR LEDs102, the IR sensors104, the illumination devices112, the at least one processor or controller141and the supporting/driver circuits1141-114Nmay be mounted to other(s) of the two or more circuit substrates. In some such embodiments, all such circuit substrates may be mounted to and/or within a single housing118, and in other embodiments at least one of the two or more of the circuit substrates may be mounted to and/or within the housing118and one or more others of the two or more circuit substrates may be mounted to or within one or more other housings. In embodiments which the object detection module121includes multiple housings, two or more such housings may be mounted to the motor vehicle at or near a single location, and in other embodiments at least one of the multiple housings may be mounted to the motor vehicle at a first location and at least another of the multiple housings may be mounted to the motor vehicle at a second location remote from the first location. As one non-limiting example, at least the plurality of IR LEDs102and the plurality of IR sensors104may be mounted to or within a first housing mounted to the motor vehicle at a first location suitable for detection of one or more specific objects, and at least the one or more illumination devices may be mounted to or within a second housing mounted to the motor vehicle at a second location suitable for viewing by one or more users and/or operators of the motor vehicle.

In one embodiment, electrical power for the object detection module12, the vehicle control computer24, the actuator driver circuit(s)40, the actuator(s)46, the audio/illumination device driver circuit(s)60and the audio/illumination device(s)66is illustratively provided by a conventional electrical power source and/or system on-board the motor vehicle. In alternate embodiments, electrical power for the object detection module12, the actuator driver circuit(s)40, the actuator(s)46, the audio/illumination device driver circuit(s)60and/or the audio/illumination device(s)66may be provided by one or more local power sources, e.g., one or more batteries, on-board the associated module(s), circuit(s) and/or device(s).

Referring now toFIGS. 3A-5, the radiation emission and detection assembly100is illustratively operable, under control of the processor or controller141, to detect an object OB within a sensing region R (depicted schematically in dashed lines inFIGS. 3A-5) of the assembly100, and to provide corresponding object detection signals to the processor or controller141. In some embodiments, the processor or controller141is, in turn, operable, e.g., by executing corresponding instructions stored in the memory161, to (1) determine from the object detection signals whether the object OB is within the sensing region R, (2) determine whether the object OB detected as being within the sensing region R exhibits a predefined gesture, and (3) if the detected object OB exhibits a predefined gesture, to (i) control the illumination devices112to selectively illuminate one or more of the illumination devices112to visibly indicate detection of the predefined gesture, and (ii) control, via the actuator control driver circuit(s), at least one of the actuators46associated with an access closure of the motor vehicle to lock or unlock the access closure and/or to open or close the access closure.

In some embodiments, the processor or controller141is operable upon detection of the object OB within the sensing region R to selectively illuminate the at least one illumination device112in a manner which visibly indicates the detected presence of the object OB within the sensing region R. In some such embodiments, the processor or controller141is operable upon detection of the object OB within the sensing region to selectively illuminate the at least one illumination device in a manner which indicates that the object OB is within a sub-region of the sensing region R that is too small to make a determination of whether the object OB exhibits the predefined gesture, and is operable to selectively illuminate the at least one illumination device in a manner which indicates that the object OB is within a sub-region of the sensing region R in which a determination can be made of whether the object OB exhibits the predefined gesture. In embodiments in which the at least one illumination device112is provided in the form of an array110of illumination devices spaced apart at least partially across the sensing region R, the processor or controller141is illustratively operable to selectively illuminate illumination devices112in the array10in a manner which correlates the location of the detected object OB within the sensing region R to a corresponding location or region along the illumination device array110. In any case, the memory16illustratively has instructions stored therein which, when executed by the processor141, causes the processor141to carry out the functions described below. It will be understood that in other embodiments, such instructions may be stored, in whole or in part, in one or more other memory units within the system10and/or may be executed, in whole or in part, by one or more other processors and/or controllers within the system10.

In a first example state of operation illustrated inFIG. 3A, an object OB—in this example, a user's hand, foot or other object that is part of or controlled by the user—has entered the sensing region R of the radiation emission and detection assembly100. Due to limitations of the assembly100, however, the object is insufficiently positioned within the sensing region R, and/or is positioned within a sub-region sensing region R that is too small, for the assembly100to be able to determine if and when the object OB exhibits a predefined gesture. As a result, the processor or controller141is operable to control the illumination driver circuits DC to activate at least one of the illumination devices112—in this example, the illumination devices112′,112′ proximate the IR LED/sensor pairs which detected the object OB— with a first color to visually indicate to the user that the object OB has been detected within a sub-region of the sensing region R, but is insufficiently positioned in the sensing region R such that the sub-region R is too small to enable to the assembly100to determine whether the object OB exhibits a predefined gesture. In this example, the applicable illumination devices112′ are controlled to illuminate with the color red. Illustratively, red serves as a generally universal indicator of warning and so is appropriate as a visual indicator to the user that the object OB is insufficiently positioned in the sensing region R. As noted above, however, one or more other colors may alternatively be employed as desired. Alternatively or additionally still, one or more of the illumination devices112′ (or112generally) may be controlled in another visually distinctive manner to provide the visual indicator that the object OB is insufficiently positioned in the sensing region R such that the sub-region R is too small to enable to the assembly100to determine whether the object OB exhibits a predefined gesture, e.g., sequentially activating and deactivating the illumination devices112′ (or one or more of the illumination devices112generally) with a predefined frequency, activating and deactivating one or more of the illumination devices112′ (or one or more of the illumination devices112generally) with a predefined frequency and/or duty cycle, and/or activating in any manner only a subset of the illumination devices112′ (or one or more of the illumination devices112generally).

As illustrated by example inFIG. 3B, the object OB is detectable within a distance D1of the assembly100, where D1defines a maximum axial sensing region R; that is, a maximum distance away from the assembly100at which the object OB is horizontally and vertically aligned with the assembly100, i.e., directly opposite the assembly100. As briefly described above, the radiation emission and detection assembly100made up of multiple IR LEDs102and IR sensors104illustratively has a range of about 200 millimeters (mm) of off-surface detection, and D1is thus approximately equal to 200 mm. It is to be understood, however, that the object OB is also detectable by the assembly distances less than D1at least partially off-axis vertically and/or horizontally relative to the assembly100.

In a second example state of operation illustrated inFIG. 4, the object OB is positioned centrally within the sensing region R. In some cases, the user may have initially positioned the object OB in the location illustrated inFIG. 4, and in other cases the user may have moved the object OB to the location illustrated inFIG. 4in response to visual feedback provided by illumination of one or more of the illumination devices112, such as depicted in the example ofFIG. 3A. In any case, in the position illustrated inFIG. 4, the object OB is sufficiently in the sensing region and/or otherwise within a sub-region of the sensing region R in which the radiation emission and detection assembly100is capable of detecting whether and when the object OB exhibits a predefined gesture. As a result, the processor or controller141is operable to control the illumination driver circuits DC to activate at least one of the illumination devices112—in this example, the illumination devices112″ proximate the IR LED/sensor pairs which detected the object OB—with a second color to visually indicate to the user that the object OB is detected within the sensing region R and is within a sub-region thereof in which the processor or controller141is capable of determining whether the object OB exhibits a predefined gesture.

In this example, the illumination devices112″ are illuminated in the color amber (or yellow or gold), which serves as a visual feedback indication that the object OB is positioned within the sensing region R such that any subsequent gestures made by the object OB can be recognized by the processor or controller141as a predefined gesture or any of multiple different predefined gestures. As noted above, however, one or more other colors may alternatively be employed as desired. Alternatively or additionally still, one or more of the illumination devices112″ (or one or more of the illumination devices112generally) may be controlled in another visually distinctive manner to provide the visual indication that the object OB is positioned within the sensing region R such that any subsequent gestures made by the object OB can be recognized by the processor or controller141as a predefined gesture or any of multiple different predefined gestures, e.g., sequentially activating and deactivating the illumination devices112′ (or one or more illumination devices112generally) with a predefined frequency, activating and deactivating one or more of the illumination devices112′ (or one or more illumination devices112generally) with a predefined frequency and/or duty cycle, and/or activating in any manner only a subset of the illumination devices112′ (or any subset of the illumination devices112generally).

In a third example state of operation illustrated inFIG. 5, the object OB positioned centrally within the sensing region R (e.g., seeFIG. 4) has exhibited a predefined gesture which has been detected by the assembly100and determined by the processor or controller141as correspond to a predefined gesture. As a result, the processor or controller141is operable to control the illumination driver circuits DC to activate at least one of the illumination devices112—in this example, the illumination devices112′″ proximate the IR LED/sensor pairs which detected the object OB (e.g., the same illumination devices112″ illuminated inFIG. 4)—with a third color to visually indicate to the user that the detected object OB has exhibited a predefined gesture. Illumination in this instance is in the color green, which illustratively serves as a generally universal indicator of acceptance and so is appropriate as a visual indicator to the user that the gesture has been recognized. As noted above, however, one or more other colors may alternatively be employed as desired. Alternatively or additionally still, one or more of the illumination devices112′″ (or one or more of the illumination devices112generally) may be controlled in another visually distinctive manner to provide the visual indication that the object OB positioned within the sensing region R has exhibited a predefined gesture, e.g., sequentially activating and deactivating the illumination devices112′″ (or one or more illumination devices112generally) with a predefined frequency, activating and deactivating one or more of the illumination devices112′″ (or one or more illumination devices112generally) with a predefined frequency and/or duty cycle, and/or activating in any manner only a subset of the illumination devices112′″ (or any subset of the illumination devices112generally). In any case, the processor or controller141is further responsive to detection of the predefined gesture to control at least one of the actuator control driver circuit(s)40to control at least one of the actuators46associated with an access closure of the motor vehicle, e.g., to lock or unlock the access closure and/or to open or close the access closure.

The memory16illustratively has stored therein a vehicle access condition value which represents the predefined gesture. In alternate embodiments, the vehicle access condition value may be stored in one or more of the memory16, the memory28, the memory44and the memory64. In some embodiments, the vehicle access condition value is illustratively stored in the form of a predefined set or sequence of values, and the processor141is illustratively operable to process the signal(s) produced by the assembly100to convert such signals to a detected set or sequence of values, to then compare the detected set or sequence of values to the stored, predefined set or sequence of values and to then determine that the predefined gesture has been exhibited and detected by the assembly100if the detected set or sequence of values matches the vehicle access condition value in the form of the stored, predefined set or sequence of values. In some such embodiments, the object detection module121may have a “learning” mode of operation in which the predefined gesture may be programmed by exhibiting the predefined gesture within the sensing region R of the assembly100, then converting the signals produced by the assembly100in response to the exhibited gesture to a learned set or sequence of values, and then storing the learned set or sequence of values as the predefined set of sequence or values corresponding to the predefined gesture. In some embodiments, two or more different vehicle access condition values may be stored in the memory16(and/or any of the memories28,44and64) each corresponding to a different one of two or more corresponding predefined gestures, and the processor141may be operable to compare detected sets or sequences of values produced by the assembly100to each of the two or more different stored vehicle access condition values to determine whether one of the two or more predefined gestures has been exhibited. In some such embodiments, each of the multiple predefined gestures may be associated with a different user of the motor vehicle, and in other such embodiments any single user may have two or more predefined gestures store in the memory141.

In some embodiments, the processor or controller141may be responsive to (i) detection of the object OB within a sub-region of the sensing region R but insufficiently positioned in the sensing region R such that the sub-region R is too small to enable to the assembly100to determine whether the object OB exhibits a predefined gesture, (ii) detection of the object OB positioned within the sensing region R such that any subsequent gestures made by the object OB can be recognized by the processor or controller141as a predefined gesture or any of multiple different predefined gestures, and/or (iii) detection of the predefined gesture, to control at least one of the audio/illumination device driver circuits60to activate one or more respective audio and/or illumination devices66in addition to the one or more illumination devices112or in instead of the one or more illumination devices112.

While the foregoing example illustrates the selective illumination of several of the illumination devices112simultaneously, it will be appreciated that the number of lights illuminated in any given situation may vary depending on the type of feedback desired, the number and/or type of illumination devices112being employed in the system, etc. Likewise, although one or more of the illumination devices112may activated with one or more colors and/or be activated and deactivated, i.e., switched on and off, to provide visual feedback of the position of the object OB, one or more illumination devices112may alternatively be activated (and deactivated) in any manner which visually directs, e.g., coaxes, the user to move the object OB is a particular direction and/or to a particular position relative to the assembly100.

In one embodiment, the at least one processor or controller141is illustratively operable, upon determining from the radiation emission and detection assembly100that a predefined gesture has been exhibited by an object OB within the sensing region R of the assembly100, to communicate instructions to the vehicle control computer24to effect the desired operation (e.g., to unlock or lock a closure—such as a door, rear hatch, tailgate, etc., to open a closure—such as a rear hatch, tailgate, etc. and/or to activate, i.e., turn on, one or more interior and/or exterior vehicle illumination devices). In some alternate embodiments, the at least one processor or controller141may be operable, upon such determination, to control one or more actuator driver circuits40and/or one or more audio/illumination device driver circuits60directly to effect the desired operation. In other alternate embodiments, the at least one processor or controller141may be operable, upon such determination, to communicate instructions to the vehicle to one or more other processors or controllers, e.g., the at least one processor or controller42and/or the at least one processor or controller62, to effect the desired operation. In still other alternate embodiments, the at least one processor or controller141may be operable, upon such determination, to effect the desired operation in part and to instruct one or more other processors or controllers, e.g.,26,42,62, to also effect the desired operation in part.

In some embodiments, one or more aspects of the gesture access process described above and illustrated by example with respect toFIGS. 3A-5may be implemented in combination with, or integrated with, one or more existing vehicle access devices, techniques or processes. One non-limiting example of such an existing vehicle access device, technique and process is a conventional intelligent “key fob”-type remote used in PES-type access systems. Such access systems may typically operate in a conventional manner by issuing a short-range “challenge” signal to a “key fob” remote20carried by a user. If the “key fob” remote20is one that is authorized for the vehicle, the “challenge” response from the remote20results in the vehicle control computer24being placed in a mode where it will accept subsequent “commands” from the remote20, such as unlocking or locking the vehicle, unlatching the trunk or rear hatch, or the like. The gesture access process described above and illustrated by example with respect toFIGS. 3A-5may operatively interface with the vehicle control computer24so as to permit execution of the gesture access process by the processor or controller141only in circumstances when an authorized user seeks to use the system, e.g., such as when the user conveying gesture access movements to the radiation emission and detection assembly100is also carrying a key fob remote20or other remote device, e.g., a smart phone or other mobile device, which may communicate with the vehicle control computer24to allow the user to access the vehicle using predefined gesture access movements. Alternatively, the object detection module121may further include the necessary components to enable independent authentication of the user; that is, the electronics, hardware, firmware and/or software necessary to issue a challenge signal and to receive and evaluate the response from a user's key fob20and/or to otherwise communicate with one or more other mobile electronic devices20carried by the user for purposes of authenticating the user for subsequent recognition by the combination of the radiation emission and detection assembly100and the processor or controller141of a predefined gesture movement carried out by the user.

In embodiments in which the gesture access process illustrated by example inFIGS. 3A-5and descried above is permitted only in circumstances when an authorized user seeks to use the system, e.g., such as when the user conveying gesture access movements to the radiation emission and detection assembly100is also carrying a key fob remote20or other such remote device, the memory161illustratively has a key fob code stored therein, and the processor or controller141is illustratively operable to receive a key fob signal(s) wirelessly transmitted by a key fob or other such remote device20within a key fob signal detection area of the motor vehicle, to determine a code based on the received key fob signal and to activate the IR LED(s)102and process the radiation detection signals detected by the IR sensor(s)104only if the determined code matches the stored key fob code. Illustratively, the key fob signal detection area is defined by a transmission/detection range of the key fob or other such remote device20, which may typically be up to about 20-30 yards (or more). In some such embodiments, the key fob code is illustratively associated in the memory161with a vehicle access condition value, corresponding to a predefined gesture, also stored in the memory161, and in such embodiments the processor or controller141is illustratively operable to process the radiation detection signals produced by the assembly100as described above and actuate a corresponding one of the actuators46only if the object OB in the sensing region R of the assembly100exhibits the predefined gesture corresponding to the vehicle access condition value associated in the memory161with the stored key fob code. In embodiments in which multiple key fob codes are stored in the memory161, each such stored key fob code is illustratively associated in the memory161with a different vehicle access condition value mapped to or associated with a different corresponding predefined gesture. In such embodiments, the processor or controller141is illustratively operable to activate one or more of the actuators46, as described above, only upon detection of a key fob code which matches one of the multiple stored key fob codes, followed by detection by the assembly100of a gesture exhibited within the sensing region R which matches the predefined gesture mapped to or associated with the vehicle access condition value associated in the memory with the matching key fob code.

Referring now toFIG. 6A, another example embodiment122is shown of the object detection module12illustrated inFIG. 1. In the illustrated embodiment, the object detection module122includes a radiation emission and detection assembly130electrically connected to the at least one processor or controller142via a number Q of signal paths, wherein Q may be any positive integer. The radiation emission and detection assembly130illustratively includes at least one radiation transmitter132in the form of a radar transmitter, and a plurality of radiation detectors134in the form of an array of two or more radar detectors. In some embodiments, a single radar transmitter132is positioned adjacent to or proximate to the plurality of radar detectors134, and in other embodiments two or more radar transmitters132may be positioned adjacent to or proximate to the plurality of radar detectors as illustrated by dashed-line representation inFIG. 6A. In other embodiments, the one or more radar transmitters132may be spaced apart from the plurality of radar detectors134.

The at least one radar transmitter132is illustratively conventional, and is configured to be responsive to control signals produced by the processor or controller141to emit radio frequency (RF) radiation outwardly from the assembly100. In one embodiment, the at least one radar transmitter132is configured to emit radiation in the so-called short-range-radar (SRR) band, e.g., at and around 24 gigahertz (GHz). Alternatively or additionally, the at least one radar transmitter132may be configured to emit radiation in the so-called long-range-radar (LRR) band, e.g., at and around 77 GHz. It will be understood, however, that these numerical frequency ranges are provided only by way of example, and that the at least one radar transmitter132may be alternatively or additionally configured to emit radiation at radar frequencies less than 1 GHz and up to or greater than 300 GHz. In any case, each of the plurality of radar detectors134is configured to detect radar signals in frequency range(s) corresponding to that/those of the at least one radar transmitter132, and to produce radiation detection signals corresponding thereto.

The radiation detection signals produced by the radar detectors134illustratively include reflected radar signals if the emitted radiation is reflected by an object in a sensing region of the assembly130, in accordance with a conventional time sequence in which the at least one radar transmitter132is activated to emit radiation and at least a portion of such emitted radiation is reflected by the object toward and detected by at least one of the radar detectors134. As illustrated by example inFIG. 6B, an object OBJ is detectable within a distance D2of the assembly130, where D2defines a maximum axial sensing region; that is, a maximum distance away from the assembly130at which the object OB is horizontally and vertically aligned with the assembly130, i.e., directly opposite the assembly130. Within this distance D2, radar signals133emitted by the at least one radar transmitter132propagate outwardly away from the assembly130and from the motor vehicle MV, and at least a portion of such signals133which strike the object OBJ are reflected by the object OBJ back toward the assembly130in the form of reflected radar signals135which are detected by one or more of the plurality of radar detectors134. The distance D2between the assembly130mounted to the motor vehicle MV and a detectable object is illustratively several meters, and in some embodiments D2may be greater than several meters. It is to be understood, however, that the object OBJ is also detectable by the assembly130at distances less than D2and at least partially off-axis vertically and/or horizontally relative to the assembly130.

Referring again toFIG. 6A, the illustrated object detection module122is illustratively otherwise identical in structure and operation to the object detection module121illustrated inFIGS. 2-5and described above. For example, the object detection module122further illustratively includes a plurality of illumination devices112which may (or may not) be arranged in the form of a linear or non-linear array110of equally or non-equally spaced-apart illumination devices as illustrated inFIG. 6A. The plurality of illumination devices112are illustratively as described above with respect toFIG. 2. As another example, the object detection module122further illustratively includes a number R of conventional supporting circuits (SC) and conventional driver circuits (DC)1141-114R, wherein R may be any positive integer. The supporting circuit(s) (SC) and the driver circuit(s) (DC) is/are each as described above with respect toFIG. 2. As yet another example, the components of the object detection module122are illustratively mounted to at least one circuit substrate136, which is as described with respect to the circuit substrate116ofFIG. 2, and the combination is illustratively mounted to or within a housing138, which is as described with respect to the housing118ofFIG. 2. In some embodiments, as also described above with respect to the object detection module122illustrated inFIG. 2, the at least one radar transmitter132, the plurality of radar detectors134and the one or more visible LEDs112may be combined and provided in the form of a radiation assembly or module140mounted to the at least one circuit substrate136as illustrated by example inFIG. 6A.

Referring now toFIG. 7, yet another example embodiment123is shown of the object detection module12illustrated inFIG. 1. In the illustrated embodiment, the object detection module123includes the radiation emission and detection assembly100illustrated inFIG. 2and described above, which is electrically connected to the at least one processor or controller143via a number M of signal paths, wherein M may be any positive integer. Unlike the object detection module121illustrated inFIG. 2, the object detection module123does not include the plurality of illumination devices112. The object detection module123is otherwise identical in structure and operation to the object detection module121illustrated inFIGS. 2-5and described above. For example, the object detection module123further illustratively includes a number T of conventional supporting circuits (SC)1141-114T, wherein T may be any positive integer. In some embodiments, the object detection module123may further include one or more conventional driver circuits, as described above with respect toFIG. 2, in such embodiments in which the object detection module123includes one or more drivable devices. In any case, the supporting circuit(s) (SC) is/are each as described above with respect toFIG. 2. As another example, the components of the object detection module123are illustratively mounted to at least one circuit substrate146, which is as described with respect to the circuit substrate116ofFIG. 2, and the combination is illustratively mounted to or within a housing148, which is as described with respect to the housing118ofFIG. 2. In some embodiments, as also described above with respect to the object detection module121illustrated inFIG. 2, the plurality of IR LEDs102and the plurality of IR sensors104may be combined and provided in the form of a radiation assembly or module150mounted to the at least one circuit substrate146as illustrated by example inFIG. 7.

Referring now toFIG. 8, still another example embodiment124is shown of the object detection module12illustrated inFIG. 1. In the illustrated embodiment, the object detection module124includes the radiation emission and detection assembly130illustrated inFIG. 6Aand described above, which is electrically connected to the at least one processor or controller144via a number M of signal paths, wherein M may be any positive integer. Unlike the object detection module122illustrated inFIG. 6A, the object detection module124does not include the plurality of illumination devices112. The object detection module124is otherwise identical in structure and operation to the object detection module122illustrated inFIGS. 6A, 6Band described above. For example, the object detection module124further illustratively includes a number V of conventional supporting circuits (SC)1141-114V, wherein V may be any positive integer. In some embodiments, the object detection module124may further include one or more conventional driver circuits, as described above with respect toFIG. 2, in such embodiments in which the object detection module124includes one or more drivable devices. In any case, the supporting circuit(s) (SC) is/are each as described above with respect toFIG. 2. As another example, the components of the object detection module124are illustratively mounted to at least one circuit substrate156, which is as described with respect to the circuit substrate116ofFIG. 2, and the combination is illustratively mounted to or within a housing158, which is as described with respect to the housing118ofFIG. 2. In some embodiments, as also described above with respect to the object detection module122illustrated inFIG. 6A, the at least one radar transmitter132and the plurality of radar detectors134may be combined and provided in the form of a radiation assembly or module160mounted to the at least one circuit substrate156as illustrated by example inFIG. 8.

The object detection module12, as described above with respect toFIG. 1and various example embodiments121-124of which are described above with respect toFIGS. 2-8, may be implemented in a motor vehicle in any number of ways. As one example, and without limitation, the object detection module123or the object detection module124may be embodied in a motor vehicle access handle (e.g., a door handle) assembly200as illustrated by example inFIGS. 9-12. Referring now toFIG. 9, the motor vehicle access handle assembly200is illustratively a strap-style handle of the type comprising a stationary base202fixable to a motor vehicle door and a movable portion204adapted to be grasped by a user and pulled outwardly away from the door to release the door latch and, thus, open the door. A handle base206is coupled to a pivot mount210configured to be pivotally mounted to the motor vehicle door and a latch actuator208operatively coupled with a door latch assembly located within the motor vehicle door. A grip cover212is mountable to and over the handle base206, and the grip cover212carries a lens214through which radiation is emitted outwardly in the direction of a user approaching or positioned proximate the lens214and through which reflected radiation passes into the handle200. Together, the grip cover212and the handle base206form a grip configured to be grasped by a human hand. As will be described in greater detail below, the grip cover212and handle base206together form a housing which carries the object detection module123or124. In one embodiment, the radiation emission and detection assembly100, including the plurality of IR LEDs102and the plurality of IR sensors104, is housed within the movable portion204of the handle assembly200, and in another embodiment the radiation emission and detection assembly130, including the at least one radar transmitter132and the plurality of radar detectors134, is housed within the movable portion204.

Referring now toFIG. 10, the grip cover212includes an opening222therein in which the lens214is mounted. The lens214may be secured within the opening222in any known fashion. In the illustrated embodiment, lens214includes a base portion that is wider than the opening222, whereby the lens214is inserted through the opening222from the inside of the grip cover212and the base portion secured to the grip cover212with epoxy or other suitable adhesive.

As further illustrated inFIGS. 10 and 11, the object detection module123or124is shown including the respective radiation emission and detection assembly100,130mounted to a respective circuit substrate146,156. The radiation emission and detection assembly100,130is illustratively mounted to the circuit substrate146,156, and the circuit substrate146,156is illustratively mounted to a support member216. The radiation emission and detection assembly100,130, the circuit substrate146,156and the support member216are all illustratively configured such that, when assembled, the radiation emission and detection assembly100,130is aligned with the opening222and the lens214described above. Illustratively, the support member16is dimensioned to be sandwiched between the handle base206and the grip cover212so as to securely position the object detection module123,124within the housing defined by the handle base206and the grip cover212.

Referring now toFIGS. 10 and 12, the support member216can be seen to include a plurality of outwardly facing locking tabs218which engage with corresponding locking tabs220defined on the handle base206to securely capture the support member216in place within the housing defined by the handle base206and the grip cover212. And as shown best inFIG. 11, an opening224defined in the support member216provides a pass-through for wiring (not depicted) for electrically connecting the components mounted to the circuit substrate146,156to a power source (e.g., the vehicle battery) and, optionally, to one or more of the motor vehicle's onboard computers, e.g.,24, in order to effect vehicle commands, in some embodiments, as described herein.

As another example implementation of the object detection module12in a motor vehicle, the object detection module121or the object detection module122may likewise be embodied in a motor vehicle access handle assembly (e.g., a door handle)300as illustrated by example inFIGS. 13-16. Referring toFIGS. 13 through 16, the motor vehicle access handle assembly300is illustratively a strap-style handle of the type including a stationary base302fixable to a motor vehicle door and a movable portion304adapted to be grasped by a user and pulled outwardly away from the door to release the door latch and, thus, open the door. A handle base306is coupled to a pivot mount310configured to be pivotally mounted to the motor vehicle door and a latch actuator308operatively coupled with a door latch assembly located within the motor vehicle door. A grip cover312is mountable to and over the handle base306, and the grip cover312illustratively carries a lens314through which radiation is emitted outwardly in the direction of a user approaching or positioned proximate the lens314, through which reflected radiation passes into the handle assembly300and through which illumination of at the at least one illumination source112is visible. Together, the grip cover312and the handle base306form a grip configured to be grasped by a human hand. As will be described in greater detail below, the grip cover312and handle base306together form a housing which carries the object detection module121or122. In one embodiment, the radiation emission and detection assembly100, including the plurality of IR LEDs102and the plurality of IR sensors104, is housed within the movable portion304of the handle assembly300, and in another embodiment the radiation emission and detection assembly130, including the at least one radar transmitter132and the plurality of radar detectors134, is housed within the movable portion304. In both embodiments, the array110of illumination sources112is also housed within the movable portion304of the handle assembly, although in alternate embodiments the array110may be replaced by one or more individual illumination sources112as described above.

As in the door handle assembly200, the grip cover312includes an opening322therein configured to receive the lens314, and the lens314may be secured to the grip cover312within the opening322via any conventional means. As further illustrated inFIGS. 14 and 15, the object detection module121or122is shown including the respective radiation emission and detection assembly100,130mounted to a respective circuit substrate116,136. The illumination device array110is also illustratively mounted to the circuit substrate116,136adjacent to the radiation emission and detection assembly100,130as described above, and in the illustrated embodiment a light-transmissive cover or lens315is mounted to the circuit substrate116,136over the illumination device array110. In one embodiment, the array110of illumination devices112is aligned with and relative to the radiation emission and detection assembly100,130such that each of the illumination devices112is positioned adjacent to a corresponding one of the plurality of IR sensors104, in the case of the assembly100, or adjacent to a corresponding one of the plurality of radar detectors134in the case of the assembly130.

The circuit substrate116,136is illustratively mounted to a support member316between sidewalls324of the grip cover312. In some embodiments, the radiation emission and detection assembly100,130, the illumination device array110and the circuit substrate116,136are all illustratively configured such that, when assembled, the radiation emission and detection assembly100,130and the illumination device array110are together aligned with the opening322and the lens314described above. In alternate embodiments, the grip cover312may be at least partially light transmissive, and in such embodiments illumination of the one or more illumination devices112is viewable through the grip cover312. In still other embodiments, the grip cover312may define another opening and be fitted with another lens through which illumination of the one or more illumination devices112may be viewed. In any case, the support member316is illustratively dimensioned to be sandwiched between the handle base206and the grip cover212so as to securely position the object detection module121,122within the housing defined by the handle base206and the grip cover212.

With particular reference toFIGS. 15 and 16, secure positioning of the circuit substrate116,136carrying the radiation emission and detector assembly100,130and the illumination device array110220is accomplished via the support member316which extends inwardly from the grip cover312so as to be positioned inside the moveable portion304of the handle assembly300. The support member316includes sidewalls on which are disposed a plurality of outwardly facing locking tabs318which engage with corresponding locking tabs326defined on the base portion306to securely connect the and handle base306to the grip cover312. The circuit substrate116,136is sandwiched between the support member316and the handle base312, while the radiation emission and detection assembly100,130and the illumination device array110are IR received between the sidewalls of the support member316.

In either of the motor vehicle access handle assemblies200,300illustrated inFIGS. 9-16, it will be understood that some embodiments may include the at least one respective processor or controller141-144mounted to the respective circuit substrate116,136,146,156as described above with respect toFIGS. 1-8. In some alternate embodiments, the at least one respective processor or controller141-144may be positioned elsewhere on the vehicle and operatively connected to the radiation emission and detection assembly100,130and, in the embodiment illustrated inFIGS. 13-16, to the illumination device array110. In either case, it will also be understood that some embodiments may include the support circuit(s) and, in the case of the modules121,122,114also mounted to the respective circuit substrate116,136,146,156as described above with respect toFIGS. 1-8. In alternate embodiments, at least one of the support circuit(s) and/or at least one of the driver circuit(s) (in embodiments which include at least one driver circuit) may be positioned elsewhere on the vehicle and operatively connected to the respective circuit components of the modules121-124. In any such embodiment, the respective processor or controller141-144is operable as described above with respect toFIGS. 2-8to actuate at least one actuator46upon detection of a predefined gesture, to controllably illuminate the one or more illumination sources112, as also described above, in embodiments which include the one or more illumination sources112and, in some embodiments, to control activation of one or more audio and/or illumination devices66.

As yet another example implementation of the object detection module12in a motor vehicle, any of the object detection modules121-124may be embodied in a motor vehicle access assembly400as illustrated by example inFIGS. 17-21. Referring toFIGS. 17 through 19, the motor vehicle access assembly400is illustratively provided in the form of a housing118,138,148,158of a respective one of the object detection modules121-124adapted to be mounted to a support member406of the motor vehicle, e.g., a pillar, positioned between two access closures, e.g., doors,402,404of the motor vehicle. As most clearly shown inFIG. 19, the housing118,138,148,158of any of the respective object detection modules121-124is illustratively provided in the form of a first housing portion408mounted to the vehicle structure406, and a second elongated housing portion410mounted to the first housing portion408such that a free elongated end of the second elongated housing410is vertically oriented with a vertical seam415defined between the vehicle doors402,404. In alternate embodiments, the vertical seam415may be defined between an access closure of the motor vehicle and a stationary panel of the motor vehicle.

In embodiments in which the object detection module12is provided in the form of the object detection module123or124, the radiation emission and detection assembly100,130is illustratively provided in the form of a radiation assembly or module150,160as described above, and in embodiments in which the object detection module12is provided in the form of the object detection module121or122, the radiation emission and detection assembly100,130and the one or more illumination devices112are together provided in the form of a radiation assembly or module120,140as also described above. In the embodiment illustrated inFIGS. 18 and 19, the radiation assembly or module120,140,150,160is illustratively an elongated assembly or module mounted to the elongated free end of the housing portion410such that the elongated radiation assembly or module120,140,150,160is vertically oriented with the vertical seam415, and such that the housing portion410and the radiation assembly or module120,140,150,160together are illustratively recessed within the motor vehicle relative to an outer surface of the motor vehicle. In alternate embodiments, the housing portion410and the radiation assembly or module120,140,150,160are configured such that the housing portion410is recessed within the motor vehicle relative to the outer surface of the motor vehicle but at least a portion of the radiation assembly or module120,140,150,160extends at least partially into the vertical seam415. In some such embodiments, the radiation assembly or module120,140,150,160may at least partially protrude from the vertical seam415and thus extend outwardly from the outer surface of the motor vehicle adjacent one either side of the vertical seam415, and in other such embodiments the radiation assembly or module120,140,150,160may at least partially extend into the vertical seam415, but not protrude outwardly therefrom and thus not extend outwardly from the outer surface of the motor vehicle. In some embodiments, an elongated lens412may cover the radiation assembly or module120,140,150,160to protect the same from the outside environment, as illustrated by example inFIG. 19.

Thusly positioned, the at least one radiation transmitter, e.g., the plurality of IR LEDs102or the at least one radar transmitter, is positioned relative to the vertical seam415such that, when activated, radiation is emitted outwardly through the vertical oriented seam415at least partially along its length and, if an object is positioned within a sensing region of the radiation assembly or module120,140,150,160, at least some reflected radiation signals are reflected back towards (and in some embodiments, through) the vertically oriented seam415to be detected by one or more of the radiation receivers, e.g., one or more of the IR sensors104or one or more of the radar detectors134. Otherwise, the respective processor or controller141-144is operable as described above with respect toFIGS. 2-8to actuate at least one actuator46upon detection of a predefined gesture, to controllably illuminate the one or more illumination sources112, as also described above, in embodiments which include the one or more illumination sources112and, in some embodiments, to control activation of one or more audio and/or illumination devices66.

As further illustrated by example inFIGS. 20 and 21, the vehicle access closure402, e.g., door, which partially defines the vertically oriented seam415may be fitted with a passive handle420along an inside edge425of the closure402, i.e., along an interior, side surface of the door402which is not seen or accessible outside of the motor vehicle when the door402is closed but which is seen and accessible when the door402is at least partially open. In the illustrated embodiment, the passive handle420is illustratively provided in the form of a pocket422surrounded by a flange426which is attached to the inside edge425of the door402. The pocket422illustratively has a sidewall which extends into the inside edge425of the door402to a bottom surface424so as to form a cavity428bound by the sides and bottom424of the pocket422. Illustratively, the cavity428of the pocket402is sized to receive at least two or more fingers of a human hand therein to allow the human hand to facilitate opening the door402. In the illustrated embodiment, the processor or controller141-144is illustratively operable, upon exhibition of a predefined gesture detected by the radiation assembly or module120,140,150,160, to control at least one actuator driver circuit40to activate at least one actuator46associated with the door402to at least partially open the door402sufficiently to allow the two or more fingers of a human hand to access and engage the pocket402.

As a further example implementation of the object detection module12in a motor vehicle, any of the object detection modules121-124may be embodied in a motor vehicle access assembly400as illustrated by example inFIGS. 22-31. In the embodiment shown inFIGS. 21-31, the motor vehicle access assembly400illustratively takes the form of a license plate bracket and sensor assembly500,500′ for providing hands-free access to a rear access closure, e.g., door, of a motor vehicle522. It should be appreciated that the terms “rear access closure” and “rear access door” as used herein may include any rear access door for a motor vehicle such as, but not limited to, a lift gate, trunk and tailgate. Additionally, the term “motor vehicle” as used herein may encompass various types of motor vehicles including, but not limited to, automobiles, trucks, all-terrain vehicles and the like.

With specific reference toFIG. 23, the assembly500includes a generally rectangular-shaped back plate524that extends along a plane C. The back plate524presents a front surface526, a rear surface528, a top530, a bottom532and a pair of sides534that extend between the top530and bottom532. It should be appreciated that the back plate524could have other shapes, such as, but not limited to, an oval shape.

As best shown inFIG. 24, a first flange536extends from the top530of the back plate524over the front surface526at a viewing angle α. The viewing angle α is acute relative to the plane C of the back plate524. As best shown inFIG. 27, the first flange536extends between a pair of edges538that are spaced inwardly from the sides534of the back plate524. A protrusion540extends transversely from the front surface526of the back plate524adjacent to each of the edges538of the first flange536.

An object detection assembly542, in the form of one of the object detection module121-124, overlies the first flange536. The object detection assembly542illustratively includes a radiation emission and detection assembly544, e.g., in the form of one of the radiation assemblies or modules120,140,150,160, at the viewing angle α relative to the plane C for detecting movement in a sensing region in front of the assembly544. It should be appreciated that since the viewing angle α is acute relative to the plane C of the back plate524, once the assembly500is attached or mounted to the motor vehicle522, the radiation emission and detection assembly544is pointed generally toward the feet of an operator that is standing behind the motor vehicle522, thus allowing the assembly544to detect movement in the region of the feet of the operator.

As best shown inFIGS. 27 and 29, the object detection assembly542extends between a pair of extremities546, with each of the extremities546aligned with one of the edges538of the first flange536. A pair of tabs548extend away from the object detection assembly542, each aligned with one of the extremities546and disposed against one of the protrusions540. A pair of first fasteners552each extend through one of the tabs548and one of the protrusions540to secure the object detection assembly542to the first protrusions540. In the example embodiment, the first fasteners552are bolts, however, it should be appreciated that they could be other types of fasteners including, but not limited to, screws or adhesives.

As best shown inFIG. 25, the bottom532of the back plate524and the lower segment558of the plate frame554define a plate slot562therebetween for receiving a license plate525between the back plate524and the plate frame554. Said another way, a license plate525may be inserted into the object detection assembly520through the plate slot562.

As best shown inFIGS. 23 and 27, a plurality of connection orifices559are defined by the plate frame554and the back plate524. A plurality of second fasteners561extend through the connection orifices559and the license plate525for connecting the assembly500and the license plate525to the motor vehicle522. In the example embodiments, the second fasteners561are bolts; however, it should be appreciated that other types of fasteners could be utilized.

As best shown inFIGS. 23 and 24, a generally rectangular-shaped cover member566extends from the lower segment558into the window564toward the upper segment556. The cover member566defines a linear slit568that extends parallel to the lower segment558of the plate frame554.

The processor or controller141-142of the object detection assembly542is depicted in the example embodiment illustrated inFIGS. 22-30in the form of a controller570,571, which is electrically connected to the object detection assembly542for processing information received by the radiation emission and detection assembly544. In the first example embodiment illustrated inFIGS. 22-30, the controller includes a circuit board570that is disposed in alignment with the cover member566and is electrically connected to the assembly544. The circuit board570illustratively includes a microprocessor571(schematically shown) for processing information received by the assembly544.

In the illustrated embodiment, the one or more illumination devices112is/are depicted in the form of a plurality of light emitting diodes572mounted to the circuit board570in alignment with the slit568. Each LED in the plurality of light emitting diodes572is electrically connected to the circuit board570for emitting light in response to the detection of movement by the assembly544as described above. A lens574is illustratively disposed between the circuit board570and the cover member566, and overlies the plurality of light emitting diodes572for holding the light emitting diodes572in place and for protecting the light emitting diodes572while allowing light from the light emitting diodes572to pass through the lens574. It should be appreciated that other light emitting devices could be utilized instead of light emitting diodes572.

In addition to, or as an alternative to the light emitting diodes572, an audible device573(schematically shown and which may be one of the audio devices66depicted inFIG. 1) such as a speaker or piezoelectric element may also be disposed on the circuit board570or other location of the assembly to provide feedback to an operator of the motor vehicle522during use of the object detection assembly542.

A plurality of first ribbon wires576and a jumper board578extend between and electrically connect the circuit board570and the radiation emission and detection assembly544. The first ribbon wires576extend along the lower and flank segments558,560of the plate frame554. A first potting material582is disposed between back plate524and ribbon wires580and jumper board578for damping vibrations between the back plate524and the assembly544, first ribbon wires576and jumper board578and for holding the first ribbon wires576and jumper board578in place relative to the back plate524.

As best shown inFIGS. 24 and 25, a support member579is disposed beneath and engages the first flange536. The support member579extends between the flank segments557for supporting the first flange536. A second flange584extends from the upper segment556of the plate frame554at the viewing angle α and overlies the first flange536. The second flange584and the support member579define a detector slot581therebetween receiving the object detection assembly542for protecting the assembly542.

As best shown inFIG. 27, the back plate524defines a wire opening588adjacent to the bottom532of the back plate524. A plurality of second ribbon wires586extend from circuit board570along the front surface526of the back plate524adjacent to the bottom532of the back plate524and through the wire opening588and across the rear surface528of the back plate524. A second potting material590overlies the second ribbon wires586for damping vibrations of the plurality of second ribbon wires586and for holding the second ribbon wires586in place relative to the rear surface528of the back plate524.

As best shown inFIGS. 23 and 24, a pocket insert592of a metal material is fixed to the rear surface528of the back plate524for being received by a mounting hole on the vehicle522for connecting the license plate bracket and sensor assembly500to the motor vehicle522. The pocket insert592has a tube portion594that extends between a rearward end596and a forward end598. A lip600extends outwardly from the forward end598of the tube portion594and fixedly engages the rear surface528of the back plate524for connecting the pocket insert592to the back plate524. A lid602is disposed across the rearward end596of the tube portion594to close the rearward end596. The lid602defines a passage604that extends therethrough.

The second ribbon wires586further extend through the passage604for allowing the second ribbon wires586to be connected to a computer of the motor vehicle522for electrically connecting the circuit board570to the computer, e.g., the vehicle control computer24, of the motor vehicle522. More specifically, the second wires576,580,586electrically connect the license plate bracket and sensor assembly500to the existing passive entry system of the motor vehicle522.

Operation of the license plate bracket and sensor assembly500is as described above with respect toFIGS. 2-8in that the microprocessor571is programmed to identify a recognizable, predetermined, position, motion or reflection base on signals provided by the object detection assembly542. Upon recognition of such a position, motion or reflection, the microprocessor571illustratively sends one or more signals to the computer24of the motor vehicle522to open the rear access enclosure. In other words, the microprocessor571is configured to receive signals from the object detection assembly542, and to open the rear access closure in response to the reception and recognition of one or more predetermined signals corresponding to a predefine gesture, e.g., a hand wave or foot wave, within a detection range of the object detection assembly542.

In embodiments in which the object detection assembly542is implemented in the form of the object detection module121or122illustrated inFIGS. 2-6Band described above, the microprocessor571is further illustratively configured to cause the one or more illumination devices112, i.e., the light emitting diodes572, to emit light, as described above, in a manner which directs the operator to the proper position or motion to open the rear access enclosure of the motor vehicle522. As one illustrative example, which should not be considered limiting in any way, as the user approaches the side of the assembly500the light emitting diodes572may initially be controlled to illuminate in red. As the user moves a hand or foot toward the middle of the assembly500, the light emitting diodes572may be controlled to illuminate in amber, and finally to illuminate in green to indicate actuation of an opening mechanism48of the rear access closure of the motor vehicle522. Additionally or as an alternative, the audible device573may be activated to further guide the user to the proper position or through the proper predetermined movement to open the rear access closure. Of course, other configurations and/or control techniques of the light emitting diodes571may be alternatively or additionally be implemented, several examples of which are described hereinabove.

In embodiments in which the object detection assembly542is implemented in the form of the object detection module123or124illustrated inFIGS. 7 and 8respectively, operation of the assembly500may be as just described except with no visual feedback from the module123,124due to the absence of the one or more illumination devices112, e.g., in the form of the light emitting diodes571.

In the second example embodiment of the license plate bracket and sensor assembly500′ illustrated inFIG. 31, the plate frame only extends across the top of the back plate524′, such that only an upper portion of a license plate is covered by the plate frame. In this embodiment, the object detection module121-124may be incorporated into an upper segment556′ of the plate frame. Furthermore, a pair of visibility lights605may be connected to the upper segment556′ of the plate frame for illuminating the license plate in the event that the assembly500′ casts a shadow on the license plate by blocking the factory installed lights of the motor vehicle522. It should be appreciated that the first example embodiment of the assembly500could also include or more of such visibility lights605.

Referring now toFIG. 32, a motor vehicle630is shown depicting various example locations on and around the motor vehicle630to or at which all or part of the object detection module12(e.g., in any of its example forms121-124) may be attached, affixed, mounted, integrated or otherwise positioned (collectively “mounted”). For example, one or more object detection modules12may be mounted at or to one or more of a side door632, a rocker panel634, a so-called “A pillar”636, a so-called “B pillar”638, a so-called “C pillar”640and a side window642. Referring toFIG. 33, another motor vehicle650is shown depicting other various example locations on and around the motor vehicle650to or at which all or part of the object detection module12(e.g., in any of its example forms121-124) may be attached, affixed, mounted, integrated or otherwise positioned (collectively “mounted”). For example, one or more object detection modules12may be mounted at or to one or more of an emblem or plaque654affixed to a front grille654of a hood652or front end of the vehicle650, the front grille654or hood652itself, a front bumper656, one or both of the front headlights660(or other light fixture(s) on the front of the vehicle650and/or on the side of the vehicle650adjacent to the front of the vehicle650), a front windshield662and one or more side mirror housings664. Referring toFIG. 34, yet another motor vehicle670is shown depicting still other various example locations on and around the motor vehicle670to or at which all or part of the object detection module12(e.g., in any of its example forms121-124) may be attached, affixed, mounted, integrated or otherwise positioned (collectively “mounted”). For example, one or more object detection modules12may be mounted at or to one or more of a handle or handle area674of a rear closure672, e.g., rear door or hatch, of the motor vehicle670, an accessory area676, e.g., in or to which a license plate and/or lighting may be mounted, a license plate frame678, a license plate lamp assembly or other rear lamp assembly680, an emblem or plaque682affixed to the rear closure672, a rear spoiler684, a brake lamp assembly686mounted to the rear spoiler684or to the rear closure672, a rear window688, the rear bumper690, a main or auxiliary license plate area692of or adjacent to the rear bumper690, a rear lamp assembly694mounted to or within the rear bumper690, at least one rear lamp assembly696mounted to the rear closure672and at least one rear lamp assembly698mounted to the body of the motor vehicle670adjacent to the rear closure672.

In some embodiments, at least one object detection module12illustrated in any ofFIGS. 13-34may include at least one illumination device112, and in such embodiments the at least one object detection module12may be implemented in the form of the object detection module121and/or the object detection module122operable to provide for gesture access to the motor vehicle with visual feedback provided by the at least one illumination device112as described hereinabove. In some such embodiments and/or in other embodiments, at least one object detection module12illustrated in any ofFIGS. 9-12 and 17-34may not include any illumination device(s)112, and in such embodiments the at least one object detection module12may be implemented in the form of the object detection module123and/or the object detection module124operable to provide for gesture access to the motor vehicle with no visual feedback provided by the object detection module123and/or the object detection module124as also described hereinabove. An example process for providing for such gesture access is illustrated inFIG. 35and will be described in detail below. In some such embodiments and/or in still other embodiments, at least one object detection module12illustrated in any ofFIGS. 9-34may be implemented in the form of the object detection module122and/or the object detection module124which include the radiation emission and detection assembly130, in the form of at least one radar transmitter132and a plurality of radar detectors or receivers134, to selectively provide for (i) gesture access to the motor vehicle, with or without visual feedback when, e.g., movement of the motor vehicle is disabled, and (ii) object detection for object impact avoidance when, e.g., the motor vehicle is moving or is enabled to move, as briefly described above. Example processes for selectively providing for gesture access and object impact avoidance are illustrated inFIGS. 36 and 37and will be described in detail below.

Referring now toFIG. 35, a simplified flowchart is shown of a process700for providing gesture access to one or more access closures of a motor vehicle in or to which at least one object detection module12is mounted. In one embodiment, the process700is illustratively stored in the at least one memory16of the object detection module12in the form of instructions which, when executed by the at least one processor or controller14of the object detection module12, cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 1, e.g., in one or more of the memory16of the object detection module12, the memory28of the vehicle control computer24, the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and provided to the at least one processor or controller14for execution thereby. In other alternate embodiments, such instructions, wherever stored, may be executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 1, e.g., by one or more of the processors or controllers14,26,42and62. For purposes of the following description, the process700will be described as being executed by the processor or controller14, it being understood that the process700may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62.

It will be further understood that the process700may be executed using any of the object detection modules121-124. In this regard, dashed-line boxes are shown around some of the steps or groups of steps of the process700to identify steps which are part of the process700when the object detection module12is implemented in the form of the object detection module121or the object detection module122to include at least one illumination device112. As will be described below, such steps are illustratively omitted in embodiments in which the object detection module12is implemented in the form of the object detection module123or the object detection module124which do not include any such illumination devices112.

The process700illustratively begins at step702where the processor or controller14is operable to determine whether a Key Fob signal has been detected. As described above, the Key Fob signal is illustratively produced by a conventional Key Fob20or other mobile electronic device. In some embodiments, the Key Fob signal is received by the communication circuit30of the vehicle control computer24and passed, processed or unprocessed, to the processor or controller14. In other embodiments in which the object detection module12includes a communication circuit18, the Key Fob signal may be received directly by the processor or controller14. In any case, until the Key Fob signal is detected, the process700loops back to step702.

If the Key Fob signal is received by the communication circuit30of the vehicle control computer24, the processor or controller26of the vehicle control computer24is illustratively operable to decode the received Key Fob signal and determine whether it matches at least one Key Fob code stored in the memory28. If not, the processor or controller26disregards or ignores the Key Fob signal and the process700loops back to step702. Likewise, if the Key Fob signal is received by the communication circuit18of the object detection module12, the processor14is similarly operable to determine whether the received Key Fob signal matches at least one Key Fob code stored in the memory16or in the memory28. If not, the process700likewise loops back to step702. Thus, the process700advances along the “YES” branch of step702only if the received Key Fob signal matches at least one stored Key Fob code, such that the gesture access process proceeds only for authorized users, i.e., only for users carrying a Key Fob20that is recognizable by the object detection system10. It will be understood that some embodiments of the process700may not include step702, and in such embodiments the process700begins at step704.

Following the “YES” branch of step702(in embodiments which include step702), the process700advances to step704where the processor or controller14is operable to monitor the object detection assembly; more specifically, to monitor the radiation emission and detection assembly100,130of the respective object detection module121-124for object detection signals produced thereby, if any. In some embodiments, the processor or controller14is operable at step704to activate the radiation emission and detection assembly100,130to begin transmitting radiation following step702, and in other embodiments the radiation emission and detection assembly100,130may already be operating and the processor or controller14may be operable at step704to begin monitoring the signals being produced by the previously activated radiation emission and detection assembly100,130.

In any case, following step704the processor or controller14is operable at step706to determine whether any object detection signals have been produced by the radiation emission and detection assembly100,130of the respective object detection module121-124. If not, then an object has not been detected within the sensing region of the radiation emission and detection assembly100,130of the respective object detection module121-124. In some embodiments, the process700advances from the “NO” branch of step706back to the beginning of step702as illustrated by example inFIG. 35. In some alternate embodiments, the process700may advance from the “NO” branch of step706back to the beginning of step706such that the process700continually checks for an object detection until an object is detected. In such embodiments, a timer or counter may illustratively be implemented such that the process700exits the loop of step706, e.g., by looping back to the beginning of step702, after a predefined time period has elapsed since detecting the Key Fob signal without thereafter detecting an object. If, at step706, the signal(s) received from the radiation emission and detection assembly100,130of the respective object detection module121-124indicate that an object is detected within the sensing region of thereof, the process700proceeds from step706along the “YES” branch.

In embodiments in which the object detection module12is implemented in the form of the object detection module121or the object detection module122, the process700illustratively includes step708. Conversely, in embodiments in which the object detection module12is implemented in the form of the object detection module123or the object detection module124, the process700does not include step708. In implementations of the process700which include it, step708illustratively includes step710in which the processor or controller14is operable to identify one or more illumination devices112to illuminate based on the received object detection (OD) signal(s) produced by the radiation emission and detection assembly100,130of the respective object detection module121,122. Thereafter at step712, the processor or controller14is operable to control one or more of the driver circuit(s) DC to illuminate the identified illumination device(s)112according to a predefined detection scheme.

In one embodiment, the processor or controller14is operable at steps710and712to identify and illuminate at least one of the illumination devices112according to various different detection or illumination schemes. For example, if an object is determined, based on the object detection signals produced by the radiation emission and detection assembly100,130, to be within the sensing region of the radiation emission and detection assembly100,130but within a sub-region of the sensing region that is too small to allow determination by the radiation emission and detection assembly100,130and/or by the processor or controller14of whether the object within the sensing region exhibits a predefined gesture, the processor or controller14is operable to control illumination of the one or more illumination devices112according to an “insufficient detection” illumination scheme. In one embodiment in which the object detection module121or122includes a plurality of illumination devices in the form of an array110extending at least partially across the sensing region as described above with respect to the example illustrated inFIG. 3A, the processor or controller14is operable to identify for illumination according to the “insufficient detection” scheme those of the illumination devices112which occupy the same or substantially the same sub-region of the sensing region as that occupied by the object, and to control such identified illumination devices112to illuminate with a predefined color, e.g., red. Alternatively or additionally, the controller14may be operable at step712to control the identified illumination devices112to illuminate according to the “insufficient detection” scheme by switching on and off at a predefined frequency and/or with a predefined duty cycle, and/or to illuminate only a subset of the illumination devices. In embodiments which include more or fewer illumination devices, the processor or controller14may be operable at steps710and712to control at least one illumination device112to illuminate according to the “insufficient detection” illumination scheme by illuminating with at least one of a predefined color, a predefined frequency and a predefined duty cycle.

As another example, if an object is determined, based on the object detection signals produced by the radiation emission and detection assembly100,130, to be within the sensing region of the radiation emission and detection assembly100,130and also within a sub-region of the sensing region in which the radiation emission and detection assembly100,130and/or by the processor or controller14can determine whether the object therein exhibits a predefined gesture, the processor or controller14is operable to control illumination of the one or more illumination devices112according to an “object detection” illumination scheme. In one embodiment in which the object detection module121or122includes a plurality of illumination devices in the form of an array110extending at least partially across the sensing region as described above with respect to the example illustrated inFIG. 4, the processor or controller14is operable to identify for illumination according to the “object detection” scheme those of the illumination devices112which occupy the same or substantially the same sub-region of the sensing region as that occupied by the object, and to control such identified illumination devices112to illuminate with a predefined color that is different from any that may be used in other illumination schemes, e.g., in this case, amber. Alternatively or additionally, the controller14may be operable at step712to control the identified illumination devices112to illuminate according to the “object detection” scheme by switching on and off at a predefined frequency and/or with a predefined duty cycle different from any such predefined frequency and/or duty cycle used in different illumination schemes, and/or to illuminate only a subset of the illumination devices different from any subset used in other illumination schemes. In embodiments which include more or fewer illumination devices, the processor or controller14may be operable at steps710and712to control at least one illumination device112to illuminate according to the “object detection” illumination scheme by illuminating with at least one of a predefined color, a predefined frequency and a predefined duty cycle which is/are different that that/those used in other illumination schemes.

In embodiments which include step708, the process700advances from step712to step714, and in embodiments which do not include step708the process700advances from the “YES” branch of step706to step714. In any case, the processor or controller14is operable at step714to compare the received object detection signals (OD), i.e., received from the radiation emission and detection assembly100,130, to one or more vehicle access condition (VAC) values stored in the memory16(or the memory28,42and/or64), and to determine at step716whether the VAC is satisfied. In some embodiments, for example, the stored VAC is satisfied if the object detected within a suitable sub-region of the sensing region of the radiation emission and detection assembly100,130exhibits a predefined gesture which, when processed by the processor or controller14to determine a corresponding vehicle access value, matches the stored VAC as described above. Alternatively or additionally, as also described above, one or more VAC values stored in the memory16,28,42and/or64may be associated in the memory with a corresponding Key Fob code, and in some embodiments multiple VAC values are stored in the memory16,28,42,64with each associated with a different Key Fob code. In some such embodiments, vehicle access may be granted only if the combination of the Key Fob code and associated VAC are satisfied.

In embodiments in which the object detection module12is implemented in the form of the object detection module121or the object detection module122, the process700illustratively includes step718to which the process700advances from the “YES” branch of step716. Conversely, in embodiments in which the object detection module12is implemented in the form of the object detection module123or the object detection module124, the process700does not include step718. In implementations of the process700which include it, step718illustratively includes step720in which the processor or controller14is operable to control one or more of the driver circuit(s) DC to illuminate the identified illumination device(s)112according to another predefined detection or illumination scheme different from the “insufficient detection” and “object detection” schemes described above. For example, if an object previously determined to be within the sensing region of the radiation emission and detection assembly100,130is determined, based on the object detection signals produced by the radiation emission and detection assembly100,130, to exhibit a predefined gesture as described above, the processor or controller14is illustratively operable to control illumination of one or more illumination devices112according to an “access grant” illumination scheme. In one embodiment in which the object detection module121or122includes a plurality of illumination devices in the form of an array110extending at least partially across the sensing region as described above with respect to the example illustrated inFIG. 5, the processor or controller14is operable to identify for illumination according to the “access grant” scheme those of the illumination devices112which occupy the same or substantially the same sub-region of the sensing region as that occupied by the object, and to control such identified illumination devices112to illuminate with a predefined color that is different from any that may be used in other illumination schemes, e.g., in this case, green. Alternatively or additionally, the controller14may be operable at step718to control the identified illumination devices112to illuminate according to the “access grant” scheme by switching on and off at a predefined frequency and/or with a predefined duty cycle different from any such predefined frequency and/or duty cycle used in other illumination schemes, and/or to illuminate only a subset of the illumination devices different from any subset used in other illumination schemes. In embodiments which include more or fewer illumination devices, the processor or controller14may be operable at step718to control at least one illumination device112to illuminate according to the “access grant” illumination scheme by illuminating with at least one of a predefined color, a predefined frequency and a predefined duty cycle which is/are different that that/those used in other illumination schemes.

In embodiments which include step718, the process700advances from step718to step724, and in embodiments which do not include step718the process700advances from the “YES” branch of step716to step724. In any case, the processor or controller14is operable at step724to control one or more of the actuator driver circuits40to activate one or more corresponding vehicle access actuators46in order to actuate one or more corresponding vehicle access closure devices. Examples of such vehicle access closure devices may include, but are not limited to, one or more access closure locks, one or more access closure latches, and the like. At step724, the processor or controller14may be operable to, for example, control at least one lock actuator associated with at least one access closure of the motor vehicle to unlock the access closure from a locked state or condition and/or to lock the access closure from an unlocked state or condition, and/or to control at least one latch actuator associated with at least one access closure of the motor vehicle to at least partially open the access closure from a closed position or condition and/or to close the access closure from an at least partially open position or condition.

In some embodiments, the process700may optionally include a step726to which the process700advances from step724, as illustrated by dashed-line representation inFIG. 35. In embodiments which include it, the processor or controller14is operable at step724to control one or more of the audio and/or illumination device driver circuits60to activate one or more corresponding audio and/or illumination devices66in addition to controlling one or more vehicle access actuators to activate one or more vehicle access devices at step724following detection at step716of exhibition of a predefined gesture by the object within the sensing region of the radiation emission and detection assembly100,130. Example audio devices which may be activated at step726may include, but are not limited to, the vehicle horn, an audible device configured to emit one or more chirps, beeps, or other audible indicators, or the like. Example illumination devices which may be activated at step726in addition to one or more illumination devices112(in embodiments which include one or more such illumination devices112) may include, but are not limited to, one or more existing exterior motor vehicle lights or lighting systems, e.g., headlamp(s), tail lamp(s), running lamp(s), brake lamp(s), side marker lamp(s), or the like, and one or more existing interior motor vehicle lights or lighting systems, e.g., dome lamp, access closure-mounted lamp(s), motor vehicle floor-illumination lamp(s), trunk illumination lamp(s), or the like. In any case, following step726, or following step724in embodiments which do not include step726, the process700illustratively loops back to step702.

In embodiments in which the object detection module12is implemented in the form of the object detection module121or the object detection module122, the process700may illustratively include step722to which the process700advances from the “NO” branch of step716. Conversely, in embodiments in which the object detection module12is implemented in the form of the object detection module123or the object detection module124, the process700does not include step72. In implementations of the process700which include it, the processor or controller14is illustratively operable at step722to control one or more of the driver circuit(s) DC to illuminate the identified illumination device(s)112according to another predefined detection or illumination scheme different from the “insufficient detection,” “object detection” and “access grant” schemes described above. For example, if an object previously determined to be within the sensing region of the radiation emission and detection assembly100,130is determined, based on the object detection signals produced by the radiation emission and detection assembly100,130, to fail to exhibit a predefined gesture as described above within a predefined time period following execution of step712, the processor or controller14may illustratively be operable to control illumination of one or more illumination devices112according to a “fail” illumination scheme. In one embodiment in which the object detection module121or122includes a plurality of illumination devices in the form of an array110extending at least partially across the sensing region as described above with respect to the example illustrated inFIGS. 3A-5, the processor or controller14is operable to identify for illumination according to the “fail” scheme those of the illumination devices112which occupy the same or substantially the same sub-region of the sensing region as that occupied by the object, and to control such identified illumination devices112to illuminate with a predefined color that is different from any that may be used in other illumination schemes, e.g., in this case, red. Alternatively or additionally, the controller14may be operable at step722to control the identified illumination devices112to illuminate according to the “fail” scheme by switching on and off at a predefined frequency and/or with a predefined duty cycle different from any such predefined frequency and/or duty cycle used in other illumination schemes, and/or to illuminate only a subset of the illumination devices different from any subset used in other illumination schemes. In embodiments which include more or fewer illumination devices, the processor or controller14may be operable at step722to control at least one illumination device112to illuminate according to the “fail” illumination scheme by illuminating with at least one of a predefined color, a predefined frequency and a predefined duty cycle which is/are different that that/those used in other illumination schemes.

Referring now toFIG. 36, a simplified flowchart is shown of a process800for selectively providing for (i) gesture access to the motor vehicle, with or without visual feedback, under some operating conditions of the motor vehicle, and (ii) object impact avoidance under other operating conditions of the motor vehicle in or to which at least one object detection module12is mounted. Any such object detection module12will illustratively be implemented in the form of the object detection module122and/or the object detection module124, either of which include the radiation emission and detection assembly130in the form of at least one radar transmitter132and a plurality of radar detectors or receivers134. In one embodiment, the process800is illustratively stored in the at least one memory16of the object detection module12in the form of instructions which, when executed by the at least one processor or controller14of the object detection module12, cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 1, e.g., in one or more of the memory16of the object detection module12, the memory28of the vehicle control computer24, the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and provided to the at least one processor or controller14for execution thereby. In other alternate embodiments, such instructions, wherever stored, may be executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 1, e.g., by one or more of the processors or controllers14,26,42and62. For purposes of the following description, the process800will be described as being executed by the processor or controller14, it being understood that the process800may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62.

The process800illustratively begins at step802where the processor or controller14is operable to determine whether a Key Fob signal has been detected. Illustratively, the processor or controller14is operable to execute step802as described above with respect to step702of the process700. Thus, the process800advances along the “YES” branch of step802only if the received Key Fob signal matches at least one stored Key Fob code, such that the process800proceeds from step802only for authorized users, i.e., only for users carrying a Key Fob20that is recognizable by the object detection system10. It will be understood that some embodiments of the process800may not include step802, and in such embodiments the process800begins at step804.

Following the “YES” branch of step802(in embodiments which include step802), the process800advances to step804where the processor or controller14is operable to monitor one or more of the vehicle operating parameter sensors and/or switches50mounted to or within or otherwise carried by the motor vehicle. Illustratively, signals produced by the one or more monitored sensors and/or the status(es) of the one or more switches monitored at step804are indicative of an operating condition or state, e.g., engine running or not, and/or of a moving condition or state of the motor vehicle, e.g., motor vehicle stationary, moving, enabled to move, etc. As described above with respect toFIG. 1, examples of such sensors and/or switches50may include, but are not limited to, an engine ignition sensor or sensing system, a vehicle speed sensor or sensing system, a transmission gear selector position sensor, sensing system or switch, a transmission gear position sensor, sensing system or switch, vehicle brake sensor, sensing system or switch, and the like. Those skilled in the art will recognize other sensors and/or switches from which an operating condition or state of the motor vehicle may be determined, implied or estimated and/or from which a moving condition or state of the motor vehicle may be determined, implied or estimated, and it will be understood that monitoring of any such other sensors and/or switches at step804is intended to fall within the scope of this disclosure.

Following step804, the process800advances to step806where the processor or controller14is operable to determine a mode based on the monitored vehicle sensor(s) and/or switch(es). Generally, the mode determined by the processor or controller14at step806is a gesture access (GA) mode if the signal(s) produced by the monitored vehicle sensor(s) and/or the operational state(s) of the monitored switch(es) correspond to a state or condition of the motor vehicle conducive to gesture access operation of the system10, and is an object impact avoidance (OIA) mode of signal(s) produced by the monitored vehicle sensor(s) and/or the operational state(s) of the monitored switch(es) correspond to a state or condition of the motor vehicle conducive to object impact avoidance operation of the system10. In the former case, for example, the processor14may operate in the gesture access mode if the motor vehicle is stationary and disabled from moving, and in the latter case, for example, the processor14may operate in the object impact avoidance mode if the motor vehicle is moving or is enabled to move.

For purposes of this disclosure, the phrase “disabled from moving” should be understood to mean at least that the engine of the motor vehicle may or may not be running and, if the engine is running, that one or more actuators are preventing the motor vehicle from moving in the forward or reverse direction. In some embodiments, for example, an engine ignition switch in the “off” position means that the motor vehicle is disabled from moving, and the processor14may be operable at step806under such conditions to set mode=GA. In other example embodiments, an engine ignition switch in the “run” or “on” position means that the engine is running, and the processor14may be then operable at step806under such conditions to determine the status of one or more other vehicle operating parameters such as the transmission selection lever, the vehicle brakes and/or vehicle road speed. In some such embodiments, the processor14may be operable at step806when the engine is running to set mode=GA if, and as long as, the transmission selection lever is in “park” or otherwise not in a selectable gear (e.g., in the case of a manual transmission) and/or the vehicle brakes are engaged and/or the vehicle speed is zero. The phrase “enabled to move,” on the other hand, should be understood to mean at least that the engine of the motor vehicle has been started, and in some embodiments the processor14may be operable at step806under conditions in which the engine ignition switch is in the “run” or “on” position to set mode=OIA. In some embodiments in which the processor or controller14has determined that the engine has been started, the processor14may then be further operable at step806to determine the status of at least one other vehicle operating parameter such as the transmission selection lever, the vehicle brakes or vehicle road speed. In some such embodiments, the processor14may be operable at step806when the engine is running to set mode=OIA if, and as long as, a drive gear (forward or reverse) of the motor vehicle transmission has been selected, and/or the vehicle brakes are disengaged and/or vehicle speed is greater than zero. Those skilled in the art will recognize other vehicle operating parameters which may be used alone, in combination with one or more of the above-described vehicle operating parameters and/or in combination with other vehicle operating parameters to determine when and whether the motor vehicle is disabled from moving or enabled to move, and it will be understood that any such other vehicle operating parameters are intended to fall within the scope of this disclosure. Moreover, those skilled in the art will recognize other vehicle operating conditions conducive to gesture access mode of operation or in which gesture access mode may be safely executed, and it will be understood that the processor or controller14may be alternatively configured to set mode=GA at step806according to any such other vehicle operating conditions. Further still, those skilled in the art will recognize other vehicle operating conditions conducive to object impact avoidance mode of operation or in which object impact avoidance mode may be safely executed, and it will be understood that the processor or controller14may be alternatively configured to set mode=OIA at step806according to any such other vehicle operating conditions. It will be appreciated that configuring the processor or controller14to set mode=GA or OIA based on any such other vehicle operating conditions will involve only mechanical steps for a skilled programmer.

If, at step806, the processor or controller14has set mode=GA, the process800advances to step808to execute a GA control process. In some embodiments, the GA control process may be the process700illustrated inFIG. 35and described above. As described above, the process700may be executed by or for object detection modules122, i.e., having one or more illumination devices112, and by or for object detection modules124, i.e., which do not have any illumination devices112. It will be understood, however, that the process800does not specifically require the GA control process700illustrated inFIG. 35, and that other gesture access control processes using a radiation emission and detection assembly130having at least one radar transmitter and a plurality of radar detectors may therefore be alternatively executed at step808.

If, at step806, the processor or controller14has set mode=OIA, the process800advances to step810to execute an OIA control process. An example of one such OIA process is illustrated inFIG. 37and will be described with respect thereto, although it will be understood that the process800does not specifically require the OIA control process illustrated inFIG. 37, and that other object impact avoidance control processes using a radiation emission and detection assembly130having at least one radar transmitter and a plurality of radar detectors may therefore be alternatively executed at step810. In any case, the process800illustratively loops back from either of steps808and810to step804.

Referring now toFIG. 37, a simplified flowchart is shown of another process900for selectively providing for (i) gesture access to the motor vehicle, with or without visual feedback, under some operating conditions of the motor vehicle, and (ii) object impact avoidance under other operating conditions of the motor vehicle in or to which at least one object detection module12is mounted. As with the process800illustrated inFIG. 36, any such object detection module12will illustratively be implemented in the form of the object detection module122and/or the object detection module124, either of which include the radiation emission and detection assembly130in the form of at least one radar transmitter132and a plurality of radar detectors or receivers or detectors134. In one embodiment, the process900is illustratively stored in the at least one memory16of the object detection module12in the form of instructions which, when executed by the at least one processor or controller14of the object detection module12, cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 1, e.g., in one or more of the memory16of the object detection module12, the memory28of the vehicle control computer24, the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and provided to the at least one processor or controller14for execution thereby. In other alternate embodiments, such instructions, wherever stored, may be executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 1, e.g., by one or more of the processors or controllers14,26,42and62. For purposes of the following description, the process800will be described as being executed by the processor or controller14, it being understood that the process900may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62.

The process900illustratively begins at step902where the processor or controller14is operable to determine whether a Key Fob signal has been detected. Illustratively, the processor or controller14is operable to execute step902as described above with respect to step702of the process700. Thus, the process900advances along the “YES” branch of step902only if the received Key Fob signal matches at least one stored Key Fob code, such that the process900proceeds from step902only for authorized users, i.e., only for users carrying a Key Fob20that is recognizable by the object detection system10. It will be understood that some embodiments of the process900may not include step902, and in such embodiments the process900begins at steps904and906.

Following the “YES” branch of step902(in embodiments which include step902), the process900advances to steps904and906. At step904, the processor14is illustratively operable to execute a GA control process. In some embodiments, the GA control process may be the process700illustrated inFIG. 35and described above. As described above, the process700may be executed by or for object detection modules122, i.e., having one or more illumination devices112, and by or for object detection modules124, i.e., which do not have any illumination devices112. It will be understood, however, that the process900does not specifically require the GA control process700illustrated inFIG. 35, and that other gesture access control processes using a radiation emission and detection assembly130having at least one radar transmitter and a plurality of radar detectors may therefore be alternatively executed at step904.

At step906, the processor or controller14is operable to determine, e.g., by monitoring the engine ignition switch included in the vehicle sensors/switches50, whether the engine ignition status IGN is “on” or “running.” If not, the process900loops back to the beginning of step906. Thus, as long as the engine of the motor vehicle is not running, the processor or controller14will continue to execute the GA control process at step904. If, however, the processor or controller14determines at step906that the engine ignition status IGN is “on” or “running,” thus indicating that the engine of the motor vehicle has been started and is running, the process900advances to step908where the processor or controller14is operable to monitor one or more vehicle sensors and/or switches. Thereafter at step910, the processor or controller14is operable to compare the signal(s) and/or state(s) of the monitored vehicle sensor(s) and/or switch(es) to gesture access (GA) and/or object detection (OD) conditions, and thereafter at step912the processor or controller14is operable to determine a mode as either gesture access (GA) or object impact avoidance (OIA) based on the comparison. Illustratively, the processor or controller14is operable to execute steps908-912as described above with respect to step806of the process800.

Following step912, the processor or controller14is illustratively operable to determine whether the mode determined at step912is GA or OIA. If GA, the process900loops back to the beginning of steps904and906. Thus, with the engine running, as long as the vehicle operating parameters correspond to gesture access operating conditions, the processor or controller14will continue to execute the GA control process at step904. However, if the processor or controller14determines at step914that the mode determined at step912is OIA, the process900advances to step916where the processor or controller14is operable to suspend execution of the GA control process executing at step904and to execute an object impact avoidance control process beginning at step918.

At step918, the processor or controller14is operable to monitor the object detection assembly; more specifically, to monitor the radiation emission and detection assembly130of the respective object detection module122,124for object detection signals produced thereby, if any. Thereafter at step920, the processor or controller14is operable to compare the object detection signal(s) produced by the assembly130to one or more object detection parameters (ODP) stored in the memory16(and/or stored in the memory28,44or64). In some embodiments, for example, the one or more stored ODPs is/are satisfied by an object detected anywhere within the distance D2of the radiation emission and detection assembly130as illustrated inFIG. 6Band described above with respect thereto. In such embodiments, the detected object signal(s), when processed by the processor or controller14to determine a corresponding object detection value, thus matches at least one of the one or more stored ODPs.

Following step920, the processor or controller14is operable at step922to determine whether the one or more stored ODPs has/have been satisfied. If so, the process900advances to step924where the processor or controller14is operable to control one or more of the actuator driver circuits40to control one or more corresponding actuators48to activate one or more corresponding object avoidance devices, mechanisms and/or systems50of the motor vehicle. Examples of such object avoidance devices, mechanisms and/or systems50may include, but are not limited to, one or more electronically controllable motor vehicle access closure latches or latching systems, an automatic (i.e., electronically controllable) engine ignition system, an automatic (i.e., electronically controllable) motor vehicle braking system, an automatic (i.e., electronically controllable) motor vehicle steering system, an automated (i.e., electronically controllable) motor vehicle driving system (e.g., “self-driving” or “autonomous driving” system), and the like. Thus, depending upon the location of the object detection module12on and relative to the motor vehicle, the processor or controller14may execute step924by locking one or more electronically controllable access closure latches or latching systems, by automatically turning off the engine ignition system, by activating an electrically controllable motor vehicle braking system to automatically apply braking force to stop or slow the motor vehicle, by controlling an automatic steering system so as to avoid impact with the detected object and/or by controlling an automated vehicle driving system so as to avoid impact with the detected object. Those skilled in the art will recognize other object impact avoidance devices, mechanisms and/or systems which may be controlled at step924to avoid or mitigate impact with the detected object, and it will be understood that any such other object impact avoidance devices, mechanism and/or systems are intended to fall within the scope of this disclosure. In any case, the process900illustratively loops from step924back to the beginning of step918so that the processor or controller14continues to execute the object impact avoidance control process of steps918-924as long as the one or more stored ODP conditions continue to be satisfied.

In some embodiments, the processor or controller14may be additionally operable at step926to control one or more audio and/or illumination driver circuits60to activate one or more corresponding audio devices and/or illumination devices66. Examples of the one or more audio devices66which the processor or controller14may activate at step926may include, but are not limited to, a vehicle horn, one or more electronically controllable audible warning devices, e.g., in the form of one or more predefined alarm sounds, sequences or the like, one or more electronically controllable audio notification devices or systems, one or more electronically controllable audio voice messaging devices or systems, or the like. Examples of the one or more illumination devices66which the processor or controller14may activate at step926may include, but are not limited to, one or more electronically controllable visible warning devices, one or more exterior vehicle lights, one or more interior vehicle lights, or the like.

If at step922, the processor or controller14determines that the one or more stored ODPs is/are not, or no longer, satisfied, the process900advances to step926where the processor or controller14is operable to control the one or more actuator driver circuits40to reset the corresponding one or more actuators46activated at step924. If, at step924, the process or controller14activated one or more audible and/or illumination devices66, the processor or controller14is further operable at step926to reset or deactivate such one or more activated audible and/or illumination devices66. Following step926, the process900loops back to steps904and906where the processor or controller14is operable at step904to again execute the GA control process and at steps906-914to determine whether to continue to execute the GA control process or whether to again suspend the GA process and execute the OIA process of steps918-924. It will be understood that if step924has not yet been executed prior to determining at step922that the ODPs is/are not satisfied, step926may be bypassed and the process900may proceed directly from the “NO” branch of step922to steps904and906.

In some embodiments of the process800illustrated inFIG. 36, the OIA control process executed at step810thereof may be similar or identical to the OIA control process executed at steps916-924of the process900. In other embodiments of the process800, the OIA control process executed at step810may be or include other OIA control processes as described above.

While some of the foregoing embodiments illustrated in the attached drawings are described above as including at least one illumination device112for providing visual feedback during gesture access operation, any of the object detection modules12which include at least one illumination device112may alternatively include at least one audible device responsive to at least one control signal to produce at least one audible signal. In some such embodiments, at least one audible device may be configured to produce sounds of different volumes and/or frequencies. In other such embodiments, two or more audible devices may be included, each producing sound with a different volume and/or frequency. In any such embodiments, the at least one audible device may be controlled to switch on and off with a predefined frequency and/or duty cycle. In some such embodiments which include multiple audible devices, at least two of the multiple audible devices may be controlled to switch on and off with different frequencies and/or duty cycles.

Referring now toFIG. 38, another embodiment of a gesture access system for a motor vehicle10′ is shown which includes another embodiment of an object detection module12′. The gesture access system10′ is identical in many respects to the object detection system10illustrated inFIG. 1and described above. Components of the system10′ in common with those of the system10are accordingly identified with like reference numbers, and descriptions thereof will be omitted here for brevity, it being understood that the above descriptions of such components apply equally to those of the system10′ illustrated inFIG. 38.

The system10′ illustrated inFIG. 38differs from that of the system10in at least three respects; (1) the system10′ utilizes ultra-wide band (UWB) circuitry and signals to determine the proximity, relative to the motor vehicle, of a UWB circuit-equipped mobile communication device (MCD)34known to the system10′, (2) the system10′ is operable in a gesture access mode to utilize the same and/or additional UWB circuitry perform object detection for the purpose of evaluating gestures based on emitted36and reflected38UWB signals and, upon recognition of at least one predetermined gesture, unlocking, locking, automatically opening and/or automatically closing an access closure of a motor vehicle, and (3) the system10′ is operable only in the gesture access mode if the MCD is determined to be within a perimeter defined about the motor vehicle and is otherwise operable in an inactive mode in which reflected UWB signals are not received or are not acted upon. Such operational features of the system10′ are described in detail below.

To accomplish the foregoing operational features, the system10′ illustratively includes a number, M, of conventional ultra-wide band (UWB) signal transceivers32, where M may by any positive integer. Illustratively, each transceiver32operates in the conventional UWB range, e.g., any frequency or frequency range greater than 500 MHz, and is configured to wirelessly transmit and receive UWB signals. In alternate embodiments, one or more of the transceivers32may instead be provided in the form of a conventional UWB signal transmitter and a conventional (separate or paired) UWB receiver. In some embodiments, the one or more UWB transceiver(s) is/are operatively (i.e., communicatively, via hardwire and/or wireless connection) connected solely to the vehicle control computer24as depicted inFIG. 38by the solid-line connection. In some alternate embodiments, at least one UWB transceiver32is connected solely to, and/or carried solely by, the object detection module12′ as depicted inFIG. 38by the dash-line connection33, and in other alternate embodiments one or more UWB transceiver(s)32is/are operatively connected to the vehicle control computer24and at least one UWB transceiver is connected to, and/or carried by, the object detection module12′. It will be understood that any embodiment of the system10′ may include one or more of the object detection modules12′, each of which is operatively (i.e., communicatively, via hardwire and/or wireless connection) connected to the vehicle control computer24as depicted inFIG. 38by the solid-line connection31. Each of the one or more object detection modules12′ includes, at a minimum, a processor or controller14and a memory16as described above with respect toFIG. 1. Various example embodiments of the object detection module12′ are illustrated inFIGS. 40-43and will be described in detail below.

Referring now toFIG. 39, an example embodiment of the system10′ ofFIG. 38is shown implemented in a motor vehicle70. It will be understood that while not all of the components of the system10′ illustrated inFIG. 38are shown inFIG. 39, such non-illustrated components are present in the system10′ ofFIG. 39. In the illustrated embodiment, the motor vehicle70illustratively has five access closures in the form of two conventional forward vehicle doors72A,72B, two rearward vehicle doors76A,76B and a conventional rear hatch80. The forward doors72A,72B illustratively each have an access handle74A,74B respectively mounted thereto, the rearward doors76A,76B each have72C and72D each having an access handle78A,78B respectively mounted thereto and the rear had80has an access handle82mounted thereto. In some embodiments, either or both of the rearward doors76A,76B may be provided in the form of conventional hinged (i.e., swinging) doors, and in other embodiments either or both of the rearward doors76A,76B may be provided in the form of conventional sliding doors which may or may not include power-assisted or power-controlled opening/closing. In other alternate embodiments, either or both of the rearward doors76A,76B may be omitted. In some alternate embodiments, the rear hatch80may instead by a conventional trunk lid. In either case, the rear hatch or trunk lid80may include power-assisted or power-controlled opening and/or closing, and in such cases the motor vehicle70includes a power module84, including at least one drive motor.

The vehicle control computer24is suitably mounted in the motor vehicle70, and is electrically connected to number, N, of object detection modules12,12′ as well as to a number, M, of UWB transceivers32. In this example, the UWB transceivers32are operatively connected, e.g., via any number of conventional electrical wires or wirelessly, to the vehicle control computer24but not to any of the object detection modules12,12′, although in alternate embodiments one or more of the UWB transceivers32may alternatively or additionally operatively connected directly, e.g., wired or wirelessly, to a respective one or more of the object detection modules12,12′. In the illustrated example, N=5 as an object detection module12,12′ is mounted to or near each access handle74A,74B,76A,76B and82, although in alternate embodiments more or fewer object detection modules12,12′ may be mounted to the motor vehicle70at any desired location. Also in the illustrated example, M=8 as eight UWB transceivers321-328are mounted to the motor vehicle70at various different locations. For example, a UWB transceiver321at the front of the vehicle70, UWB transceivers322-326at each closure72A,76A,80,76B,72B respectively, and UWB transceivers327,328centrally on and along the top of the vehicle70. In alternate embodiments, more or fewer UWB transceivers32may be mounted to the motor vehicle70at various locations.

As also illustrated inFIG. 39, the mobile communication device (MCD)34illustratively has at least a conventional processor or controller86and a UWB transceiver88. The MCD34and the vehicle control computer24(and/or one or more of the object detection modules12,12′ in some embodiments) are both capable of wirelessly communicating with one another via control of their respective UWB transceivers32,88according to conventional UWB communication protocol. In one embodiment, the MCD34is a smart phone equipped with a UWB transceiver88, although in other embodiments the MCD may be any mobile electronic device equipped with a UWB transceiver88and additional circuitry configured to communicate with the vehicle control computer24via a conventional UWB communication protocol, such as a key fob or other mobile electronic device carried by or on an operator of the motor vehicle.

In the context of this disclosure, a particular MCD34will be capable of UWB communications with a particular vehicle control computer24(and/or by the processor/controller14of at least one of the object detection modules12,12′) of a particular motor vehicle70and/or vice versa if the particular MCD34and/or component(s) thereof is/are known to the particular vehicle control computer24(and/or by the processor/controller14of at least one of the object detection modules12,12′) and/or if the particular vehicle control computer24and/or the motor vehicle70itself and/or the processor/controller14of at least one of the object detection modules12,12′) is/are known to the MCD34. In the former case, the particular MCD34will be, for example, owned by, or otherwise in the possession of, an operator of the motor vehicle70, and in the latter case the particular motor vehicle70(carrying the particular vehicle control computer24and/or process/or controller14of at least one of the objection detection modules12,12′) will be, for example, a motor vehicle70for which the owner or possessor of the particular MCD34is an operator.

The particular MCD34will be known to the vehicle control computer24(and/or by the processor/controller14of at least one of the object detection modules12,12′) of the particular motor vehicle70if the two have been previously linked, paired or otherwise configured, in a conventional manner, for UWB communications with the other to the exclusion, with respect to the particular MCD34, of vehicle control computers24of other motor vehicles70, and to the exclusion, with respect to the particular motor vehicle70, of other MCD's34that have not been previously linked, paired or otherwise configured for UWB communications therewith. It is contemplated that two or more particular MCD's34may be so linked, paired or otherwise configured for UWB communications with the vehicle control computer24(and/or with the processor/controller14of at least one of the object detection modules12,12′) of a particular motor vehicle70, e.g., to accommodate 2nd, 3rd, etc. operators of the motor vehicle70.

In one embodiment, the particular MCD(s)34linked, paired or otherwise configured for UWB communications with the particular vehicle control computer24(and/or with the processor/controller14of at least one of the object detection modules12,12′) is/are, as a result of the linking, pairing or configuration process, illustratively operable to thereafter transmit unique identification information as part of, or appended to, UWB signals transmitted by the UWB transceiver(s)88. Alternatively or additionally, the particular vehicle control computer24(and/or the processor/controller14of at least one of the object detection modules12,12′) linked, paired or otherwise configured for UWB communications with the particular MCD(s)34may be, as a result of the linking, pairing or configuration process, thereafter operable to transmit unique identification information as part of, or appended to, UWB signals transmitted by one or more of the UWB transceivers32. Such identification information may be or include, for example, but not limited to, information identifying the processor/controller86of the particular MCD34, the UWB transceiver88of the particular MCD34, information identifying the particular MCD34itself, information identifying the particular vehicle control computer24(and/or with the processor/controller14of at least one of the object detection modules12,12′) of the particular motor vehicle70, information identifying one or more of the UWB transceivers32of the particular motor vehicle70, information identifying the particular motor vehicle70itself, any combination thereof, and/or other identification information unique to the particular MCD34/motor vehicle70pair. In any case, UWB communication, via one or more of the UWB transceivers32of a particular motor vehicle70and a UWB transceiver88of a particular MCD34, in the context of this disclosure, may only be conducted between the vehicle control computer24(and/or the processor/controller14of at least one of the object detection modules12,12′) of that particular motor vehicle70and the processor/controller14of that (or those) particular MCD(s)34by transmitting by one or the other or both, as part of or along with transmitted UWB signals, unique identification information known to the other resulting from having been previously linked, paired or otherwise configured for UWB communications with one another. In this regard, in the context of the example implementation illustrated inFIG. 39, it will be understood that the MCD34(or one or more components thereof) is thus known to the vehicle control computer24(and/or to the processor/controller14of at least one of the object detection modules12,12′) of the illustrated motor vehicle70and/or vice versa, having been previously linked, paired or otherwise configured for UWB communications with one another.

Further illustrated inFIG. 39is a perimeter, P, surrounding the motor vehicle70, which represents a boundary within which UWB communications between the processor/controller86of the MCD34and the processor26(and/or the processor/controller14of at least one of the object detection modules12,12′) of the motor vehicle70can take place or are permitted to take place, and beyond which such UWB communications cannot take place or are not permitted. Generally, UWB communications has a range of approximately 30 feet. In one embodiment the perimeter, P, accordingly defines approximately a 30 feet boundary about the motor vehicle such that when the MCD34is within the perimeter, P, as illustrated by example inFIG. 39, the MCD34is generally within UWB communication range of the motor vehicle70(and is thus considered to be “in-range”), and when the MCD34is beyond or outside of the perimeter, P, the MCD34is generally outside of UWB communication range of the motor vehicle70(and is thus considered to be “out-of-range”). In this embodiment, the perimeter, P, is thus defined as approximately the boundary of UWB communications between the MCD34and the motor vehicle70. In alternate embodiments, the perimeter P may be defined to be any arbitrary boundary about the motor vehicle70(or about any particular one, set or subset of the UWB transceivers32). In any case, for purposes of this disclosure, when the MCD34is determined to be within the perimeter, P, the object detection module(s)12,12′ is/are configured to operate in the gesture access mode, and when the MCD34is otherwise determined to be beyond or outside of the perimeter, P, the object detection module(s)12,12′ is/are configured to operate in the inactive mode, as these modes are briefly described above. In this regard, a convenient perimeter, P, is approximately the communication range of the UWB transceivers32,88, although alternate perimeters are contemplated as described above. Moreover, in some alternate embodiments, the perimeter, P, may be defined only by and about one or a subset of the total set of UWB transceivers32, and/or the perimeter, P, may not be smooth as illustrated by example inFIG. 39, but may instead be non-smoothly formed by piecewise, intersecting segments.

Referring now toFIG. 40, one example embodiment12′1is shown of the object detection module12′ illustrated inFIG. 38. In the illustrated embodiment, the object detection module12′1includes an embodiment14′1of the at least one processor or controller14as well as an embodiment16′1of the at least one memory unit16, as illustrated inFIG. 38. As described hereinabove, it will be understood that the terms “processor” and “controller” used in this disclosure is comprehensive of any computer, processor, microchip processor, integrated circuit, or any other element(s), whether singly or in multiple parts, capable of carrying programming for performing the functions specified in the claims and this written description. The at least one processor or controller14′1may be a single such element which is resident on a printed circuit board with the other elements of the inventive access system. It may, alternatively, reside remotely from the other elements of the system. For example, but without limitation, the at least one processor or controller14′1may take the form of a physical processor or controller on-board the object detection module12′1. Alternately or additionally, the at least one processor or controller14′1may be or include programming in the at least one processor or controller26of the vehicle control computer24illustrated inFIG. 38. Alternatively or additionally still, the at least one processor or controller14′1may be or include programming in the at least one processor or controller42of the actuator driver circuit(s)40and/or in the at least one processor or controller62of the audio/illumination device driver circuit(s)60and/or in at least one processor or controller residing in any location within the motor vehicle in which the system10′ is located. For instance, and without limitation, it is contemplated that one or more operations associated with one or more functions of the object detection module12′1described herein may be carried out, i.e., executed, by a first microprocessor and/or other control circuit(s) on-board the object detection module12′1, while one or more operations associated with one or more other functions of the object detection module12′1described herein may be carried out, i.e., executed, by a second microprocessor and/or other circuit(s) remote from the object detection module12′1, e.g., such as the processor or controller26on-board the vehicle control computer24.

The example object detection module12′1illustrated inFIG. 40further illustratively includes number N of conventional supporting circuits (SC)1141-114N, wherein N may be any positive integer. The supporting circuit(s) (SC) is/are each electrically connected to the processor or controller14′1, and may include one or more conventional circuits configured to support the operation of the processor or controller14′1as described above with respect toFIGS. 2, 6A, 7 and 8. Example supporting circuits SC may include, but are not limited to, one or more voltage supply regulation circuits, one or more capacitors, one or more resistors, one or more inductors, one or more oscillator circuits, and the like. In embodiments in which one or more of the UWB transceivers32is/are operatively connected to the object detection module12′1, the supporting circuits SC may further include conventional circuitry for conditioning or otherwise pre-processing signals produced by the UWB transceiver(s)32and fed directly or sent by the control computer24to the object detection module12′1or, in embodiments in which UWB transceiver signals are sent wireless to the object detection module12′1by the UWB transceiver(s)32and/or the control computer24, the supporting circuits SC may further include conventional circuitry for wirelessly receiving the UWB transceiver signals. In the embodiment illustrated inFIG. 40, the at least one processor or controller14′1and the supporting/driver circuits1141-114Nare all mounted to a conventional circuit substrate116′ which is illustratively mounted within a housing118′.

In the example embodiment12′1illustrated inFIG. 40, the UWB transceiver(s) of the system10′ are external to the object detection module12′1and is/are illustratively mounted to the motor vehicle, e.g., as illustrated by example inFIG. 39. In one implementation of this embodiment, the memory device(s)16′1illustratively has/have instructions stored therein executable by the processor(s) or controller(s)14′1to process signals produced by the UWB transceiver(s)32to operate in the gesture access or inactive mode as described above, depending upon whether a known mobile communication device34is determined, as described above, to be within or outside of the perimeter P, e.g., within or out of UWB signal communication range. In some such implementations, the UWB transceiver signals may be raw or conditioned transceiver signals sent by the UWB transceiver(s)32or the control computer24. In such implementations the memory device(s)16′1includes instructions stored therein executable by the processor(s) or controller(s)14′1to process such UWB signals to determine time difference values each between a different one of a plurality of UWB activation signals, i.e., control signals produced by the control computer24or the processor(s)/controller(s)14′1to cause the UWB transceiver(s)32to emit one or more UWB radiation signals outwardly away from the motor vehicle, and a respective UWB radiation detection signal, i.e., a UWB radiation signal reflected by an object back toward and detected by the respective UWB transceiver32, as described hereinabove with respect to the system10. If operating in the gesture access mode, as briefly described above and as will be described in greater detail below, the at least one memory device16′1further has stored therein instructions executable by the at least one processor or controller14′1to process a plurality of successive ones of the time difference values to determine whether an object is within the sensing region of the respective UWB transceiver32(wherein the sensing region is as described above with respect to the system10) and to determine whether the object within the sensing region of the respective UWB transceiver32is exhibiting a predefined gesture (also as described above with respect to the system10). The predefined gesture is illustratively stored in the memory device(s)16′1in the form of a predefined sequence of time difference values or other suitable form. If operating in the inactive mode, as briefly described above and as will be described in greater detail below, the at least one memory device16′1further has instructions stored therein executable by the at least one processor or controller14′1to not act on, i.e., ignore, UWB radiation detection signals if received directly from the UWB transceiver(s)32and/or from the control computer24in any form. In some alternate embodiments in which the object detection module12′1receives the UWB detection signals from the control computer24, the control computer24may be configured to withhold, i.e., to not send or transmit, the UWB detection signals to the object detection module12′1when operating in the inactive mode, and in such embodiments the object detection module12′1does not receive UWB detection signals when operating in the inactive mode. In some alternate implementations, the UWB transceiver signals may be processed by the control computer24to determine the time difference values, and to then send or transmit the UWB transceiver activation and reflection signals to the object detection module12′1in the form of a plurality of time difference values, and the instructions stored in the memory device(s)16′1include instructions executable by the processor(s) or controller(s)14′1to process the received time difference values as just described.

Referring now toFIG. 41, another one example embodiment12′2is shown of the object detection module12′ illustrated inFIG. 38. In the illustrated embodiment, the object detection module12′2includes an embodiment14′2of the at least one processor or controller14as well as an embodiment16′2of the at least one memory unit16, wherein the terms “processor” and “controller” are as described above with respect to the embodiment12′1of the object detection module12′. The object detection module12′2further illustratively includes number N of conventional supporting circuits (SC)1141-114Nand driver circuits (DC) operatively connected to the at least one processor14′2, wherein N may be any positive integer. The supporting circuit(s) (SC) may be as described above with respect to the embodiment12′1of the object detection module12′. In the example embodiment12′2illustrated inFIG. 41, the UWB transceiver(s) of the system10′ are, like the embodiment12′1, external to the object detection module12′2and is/are illustratively mounted to the motor vehicle, e.g., as illustrated by example inFIG. 39.

The embodiment of the object detection module12′2illustrated inFIG. 41further includes one or more illumination devices112. In some embodiments which include a plurality of illumination devices112, the illumination devices112may be spaced apart at least partially across the sensing region of the nearest UWB transceiver(s)32, and in other embodiments the illumination devices112may be positioned remotely from the sensing region. In some embodiments, the illumination devices112may be arranged in the form of a linear or non-linear array110of equally or non-equally spaced-apart illumination devices. In some embodiments, the at least one illumination device112includes at least one LED configured to emit radiation in the visible spectrum. In such embodiments, the at least one LED may be configured to produce visible light in a single color or in multiple colors. In alternate embodiments, the plurality of illumination sources may include one or more conventional non-LED illumination sources.

The one or more illumination devices112is/are illustratively included to provide visual feedback of one or more conditions relating to detection of an object within a sensing region of the UWB transceiver(s)32. In one example embodiment, two illumination devices112may be provided for producing the desired visual feedback. In one implementation of this example embodiment, a first one of the illumination devices112may be configured and controlled to illuminate with a first color to visibly indicate the detected presence of an object within the sensing region, and the second illumination device112may be configured and controlled to illuminate with a second color, different from the first, to visibly indicate that the detected object exhibits a predefined gesture. In another example embodiment, three illumination devices112may be provided. In this embodiment, a first one of the illumination devices112may be controlled to illuminate with a first color to visibly indicate the detected presence of an object within an area of the sensing region in which it is not possible to determine whether the detected object exhibits a predefined gesture (e.g., the object may be within a sub-region of the sensing region which is too small to allow determination of whether the object exhibits the predefined gesture), a second one of the illumination devices112is controlled to illuminate with a second color to visibly indicate the detected presence of an object within an area of the sensing region in which it is possible to determine whether the detected object exhibits a predefined gesture, and a third one of the illumination devices is controlled to illuminate with a third color to visibly indicate that the object within the sensing region is exhibiting a predefined gesture.

In other embodiments, the one or more illumination devices112may include any number of illumination devices. Multiple illumination devices112, for example, may be illuminated in one or more colors to provide a desired visual feedback. In any such embodiments, in one or more illumination devices112may be LEDs, and one or more such LEDs may illustratively be provided in the form of RGB LEDs capable of illumination in more than one color. According to this variant, it will be appreciated that positive visual indication of various states of operation may be carried out in numerous different colors, with each such color indicative of a different state of operation of the object detection module12′2. As one non-limiting example, the color red may serve to indicate detection of an object (e.g., a hand or foot) within a portion of the sensing region in which it cannot be determined whether the detected object is exhibiting a predefined gesture. The color green, in contrast, may serve to indicate that the detected object is exhibiting a predefined gesture and, consequently, that the predefined vehicle command associated with that predefined gesture (e.g., unlocking the vehicle closure, opening the vehicle closure, etc.) is being effected. In addition to green, other colors might be uniquely associated with different predefined commands. Thus, while green illumination might reflect that a closure for the vehicle is being unlocked, blue illumination, for example, may reflect that a fuel door latch has been opened, purple illumination may reflect that a window is being opened, etc.

In still other embodiments, in addition to or alternatively to color distinction, different operating modes, i.e., different detection or operating modes may be visually distinguished from one another by controlling the at least one illumination device112to switch on and off with different respective frequencies and/or duty cycles. In some embodiments which include multiple illumination devices112, the different detection or operating modes may be additionally or alternatively distinguished visually from one another by activating different subsets of the multiple illumination devices112for different operating or detection modes, and/or by sequentially activating the multiple illumination devices112or subsets thereof with different respective activation frequencies and/or duty cycles. In any case, the output(s) of the driver circuit(s) (DC) is/are operatively connected to the one or more illumination devices112as illustrated by example inFIG. 41. The one or more driver circuits DC may illustratively be or include any conventional circuits for driving, i.e., actuating, the one or more illumination devices112.

In the embodiment illustrated inFIG. 41, the at least one processor or controller14′2, the supporting/driver circuits1141-114Nand the one or more illumination devices112are all mounted to a conventional circuit substrate116′ which is illustratively mounted within a housing118′. In alternate embodiments, the circuit substrate116′ may be provided in the form of two or more separate circuit substrates, and in such embodiments one or more of the illumination devices112, the at least one processor or controller14′2and the supporting/driver circuits1141-114Nmay be mounted to a first one of the two or more circuit substrates and remaining one(s) of the one or more of the illumination devices112, the at least one processor or controller14′2and the supporting/driver circuits1141-114Nmay be mounted to other(s) of the two or more circuit substrates. In some such embodiments, all such circuit substrates may be mounted to and/or within a single housing118′, and in other embodiments at least one of the two or more of the circuit substrates may be mounted to and/or within the housing118′ and one or more others of the two or more circuit substrates may be mounted to or within one or more other housings. In embodiments which the object detection module12′2includes multiple housings, two or more such housings may be mounted to the motor vehicle at or near a single location, and in other embodiments at least one of the multiple housings may be mounted to the motor vehicle at a first location and at least another of the multiple housings may be mounted to the motor vehicle at a second location remote from the first location.

In one implementation of the embodiment12′2illustrated inFIG. 41, the memory device(s)16′2illustratively has/have instructions stored therein executable by the processor(s) or controller(s)14′2to process signals produced by the UWB transceiver(s)32to operate in the gesture access or inactive mode, according to any of the different ways described above with respect to the embodiment12′1, depending upon whether a known mobile communication device34is determined, as described above, to be within or outside of the perimeter P, e.g., within or out of UWB signal communication range. Additionally in this embodiment, the memory device(s)16′2further illustratively has/have instructions stored therein executable by the processor(s) or controller(s)14′2to control the illumination device(s)112according to any of the different ways just described.

Referring now toFIG. 42, yet another example embodiment12′3is shown of the object detection module12′ illustrated inFIG. 38. In the illustrated embodiment, the object detection module12′3includes an embodiment12′3of the at least one processor or controller14as well as an embodiment12′3of the at least one memory unit16, wherein the terms “processor” and “controller” are as described above with respect to the embodiment12′1of the object detection module12′. As with the example object detection module12′1illustrated inFIG. 40, the object detection module12′3further illustratively includes number N of conventional supporting circuits (SC)1141-114Noperatively connected to the at least one processor12′3, wherein N may be any positive integer. The supporting circuit(s) (SC) may be as described above with respect to the embodiment12′1of the object detection module12′.

In the example embodiment illustrated inFIG. 42, the object detection module12′3illustratively includes a number, M, of UWB transceivers100′, where M many be any positive integer. In some embodiments, the motor vehicle may also include any number of the UWB transceivers32, e.g., as illustrated by example inFIG. 39, and in other embodiments the motor vehicle may not include any UWB transceivers32such that all of the UWB transceivers carried by the motor vehicle is/are that/those included with the one or more object detection modules12′3. In any case, the UWB transceiver(s)100′ may be as described above with respect to the UWB transceivers32.

In the embodiment illustrated inFIG. 42, the at least one processor or controller12′3, the supporting/driver circuits1141-114Nand the one or more UWB transceivers100′ are all mounted to a conventional circuit substrate116′ which is illustratively mounted within a housing118′. In alternate embodiments, the circuit substrate116′ may be provided in the form of two or more separate circuit substrates, and in such embodiments one or more of the UWB transceiver(s)100′, the at least one processor or controller12′3and the supporting/driver circuits1141-114Nmay be mounted to a first one of the two or more circuit substrates and remaining one(s) of the one or more of the UWB transceiver(s)100′, the at least one processor or controller12′3and the supporting/driver circuits1141-114Nmay be mounted to other(s) of the two or more circuit substrates. In one example of this alternate embodiment, which should not be considered to be limiting in any way, the UWB transceiver(s)100′ may all be mounted to a one substrate and the remaining components may be mounted to a separate substrate. In any such embodiments, all such circuit substrates may be mounted to and/or within a single housing118′, and in other embodiments at least one of the two or more of the circuit substrates may be mounted to and/or within the housing118′ and one or more others of the two or more circuit substrates may be mounted to or within one or more other housings. In embodiments which the object detection module12′3includes multiple housings, two or more such housings may be mounted to the motor vehicle at or near a single location, and in other embodiments at least one of the multiple housings may be mounted to the motor vehicle at a first location and at least another of the multiple housings may be mounted to the motor vehicle at a second location remote from the first location.

In embodiments in which one or more UWB transceivers32is/are mounted to the motor vehicle in addition to the one or more UWB transceivers100′, and as illustrated by example inFIG. 39, the memory device(s)12′3illustratively has/have instructions stored therein executable by the processor(s) or controller(s)12′3to control activation of the one or more UWB transceivers100′ and to process corresponding reflected UWB radiation signals, i.e., reflected by an object, to operate in the gesture access or inactive mode as described above, depending upon whether a known mobile communication device34is determined, either by the control computer24via the UWB transceivers32or by the processor(s)/controller(s)12′3via the UWB transceiver(s)32and/or via the UWB transceiver(s)100′, to be within or outside of the perimeter P, e.g., within or out of UWB signal communication range. In other embodiments in which no UWB transceivers32is/are mounted to the motor vehicle, the memory device(s)12′3illustratively has/have instructions stored therein executable by the processor(s) or controller(s)12′3to control activation of the one or more UWB transceivers100′ and to process corresponding reflected UWB radiation signals to operate in the gesture access or inactive mode as described above, depending upon whether a known mobile communication device34is determined, by the processor(s)/controller(s)12′3via the UWB transceiver(s)100′, to be within or outside of the perimeter P.

Referring now toFIG. 43, still another example embodiment12′4is shown of the object detection module12′ illustrated inFIG. 38. In the illustrated embodiment, the object detection module12′4includes an embodiment14′4of the at least one processor or controller14as well as an embodiment16′4of the at least one memory unit16, wherein the terms “processor” and “controller” are as described above with respect to the embodiment12′1of the object detection module12′. As with the example object detection module12′2illustrated inFIG. 41, the object detection module12′4further illustratively includes number N of conventional supporting circuits (SC)1141-114Nand driver circuits (DC) operatively connected to the at least one processor14′4, wherein N may be any positive integer. The supporting circuit(s) (SC) and driver circuits (DC) may be as described above.

In the example embodiment illustrated inFIG. 43, the object detection module12′4illustratively includes a number, M, of UWB transceivers100′, where M many be any positive integer, where the UWB transceivers100′ may be as described above. In some embodiments, the motor vehicle may also include any number of the UWB transceivers32, e.g., as illustrated by example inFIG. 39, and in other embodiments the motor vehicle may not include any UWB transceivers32such that all of the UWB transceivers carried by the motor vehicle is/are that/those included with the one or more object detection modules12′4. Also in the example embodiment illustrated inFIG. 43, the object detection module12′4further includes one or more illumination device112operatively connected to the one or more driver circuits (DC). The one or more illumination devices may take any of the forms, and be controlled to operate, as described above with respect to the embodiment12′2illustrated inFIG. 41.

In the embodiment illustrated inFIG. 43, the at least one processor or controller14′4, the supporting/driver circuits1141-114N, the one or more UWB transceivers100′ and the one or more illumination devices112are all mounted to a conventional circuit substrate116′ which is illustratively mounted within a housing118′. In alternate embodiments, the circuit substrate116′ may be provided in the form of two or more separate circuit substrates, and in such embodiments one or more of the UWB transceiver(s)100′, the one or more illumination devices112, the at least one processor or controller14′4and the supporting/driver circuits1141-114Nmay be mounted to a first one of the two or more circuit substrates and remaining one(s) of the one or more of the UWB transceiver(s)100′, the one or more illumination devices112, the at least one processor or controller14′4and the supporting/driver circuits1141-114Nmay be mounted to other(s) of the two or more circuit substrates. In such embodiments, all such circuit substrates may be mounted to and/or within a single housing118′, and in other embodiments at least one of the two or more of the circuit substrates may be mounted to and/or within the housing118′ and one or more others of the two or more circuit substrates may be mounted to or within one or more other housings. In embodiments which the object detection module12′4includes multiple housings, two or more such housings may be mounted to the motor vehicle at or near a single location, and in other embodiments at least one of the multiple housings may be mounted to the motor vehicle at a first location and at least another of the multiple housings may be mounted to the motor vehicle at a second location remote from the first location.

In embodiments in which one or more UWB transceivers32is/are mounted to the motor vehicle in addition to the one or more UWB transceivers100′, and as illustrated by example inFIG. 39, the memory device(s)16′4illustratively has/have instructions stored therein executable by the processor(s) or controller(s)14′4to control activation of the one or more UWB transceivers100′ and to process corresponding reflected UWB radiation signals, i.e., reflected by an object, to operate in the gesture access or inactive mode as described above, depending upon whether a known mobile communication device34is determined, either by the control computer24via the UWB transceivers32or by the processor(s)/controller(s)14′4via the UWB transceiver(s)32and/or via the UWB transceiver(s)100′, to be within or outside of the perimeter P, e.g., within or out of UWB signal communication range, and to control operation, i.e., activation and deactivation, of the one or more illumination devices112as described above with respect to the object detection module12′2illustrated inFIG. 41. In other embodiments in which no UWB transceivers32is/are mounted to the motor vehicle, the memory device(s)16′4illustratively has/have instructions stored therein executable by the processor(s) or controller(s)14′4to control activation of the one or more UWB transceivers100′ and to process corresponding reflected UWB radiation signals to operate in the gesture access or inactive mode as described above, depending upon whether a known mobile communication device34is determined, by the processor(s)/controller(s)14′4via the UWB transceiver(s)100′, to be within or outside of the perimeter P, and to control operation, i.e., activation and deactivation, of the one or more illumination devices112as described above with respect to the object detection module12′2illustrated inFIG. 41.

Referring now toFIG. 44, a simplified flowchart is shown of a process930for determining whether a known mobile communication device (MCD)34, i.e., known to the control computer24of the motor vehicle and/or to the at least one processor or controller14of one or more object detection modules12′ mounted to the motor vehicle, is within our outside of the perimeter, P, illustrated by example in FIG.39. An MCD34will be known to the control computer24of the motor vehicle and/or to the at least one processor or controller14of one or more object detection modules12′ mounted to the motor vehicle if, as described above with respect toFIG. 39, the MCD34has been previously paired, linked or otherwise configured in a conventional manner for UWB communications with the control computer24and/or with the at least one processor or controller14of one or more object detection modules12′ to the exclusion, with respect to the particular MCD34, of vehicle control computers24and/or object detection modules12′ of other motor vehicles, and to the exclusion, with respect to the control computer24of the particular motor vehicle, of other MCD's34that have not been previously linked, paired or otherwise configured for UWB communications therewith. In any case, the at least one processor or controller26of the vehicle control computer24, or in some embodiments, the at least one processor or controller14of one or more of the object detection modules12′, is configured to produce a mobile device status signal (MDSS) having a state or value which depends on whether the particular MCD34is within or outside of the perimeter P.

In the example process930illustrated inFIG. 44, the perimeter, P, is illustratively implemented in the form of a communication boundary defined by the range of UWB signal communications, i.e., within the perimeter, P, the UWB transceiver88of a known MCD34is within UWB communication range of one or more of the UWB transceivers32mounted to the motor vehicle and/or the UWB transceiver100′ of one or more object detection modules12′ mounted to the motor vehicle, and outside of the perimeter, P, the UWB transceiver88is outside of UWB communication range with the transceivers32,100′. The actual range of UWB signal communications, and thus the boundary, P, defined thereby, illustratively depends on a number of factors including, for example, but not limited to, the actual UWB frequency or frequencies used, the signal strengths implemented in the UWB transceivers34and88, battery charge level (in the case of the MCD34), and the environment in which the motor vehicle is located (e.g., in a garage or other indoor location vs. outside, in an open area vs. crowded parking garage, etc.). It will be understood that whereas the process930illustrated inFIG. 44will be described with respect to the perimeter, P, being defined as the boundary of UWB signal communications as just described, other perimeters, based on one or more additional or alternative criteria, may alternatively be defined and implemented in the process930.

In embodiments in which the control computer24of the motor vehicle is configured to determine the proximity thereto of a known MCD34, the process930is illustratively stored in the at least one memory28of the vehicle control computer24in the form of instructions executable by the at least one processor or controller26of the vehicle control computer24to cause the at least one processor or controller26to execute the corresponding functions. In other embodiments in which the at least one processor or controller14of one or more of the object detection modules12′ mounted to the motor vehicle is configured to determine the proximity thereto of a known MCD34, the process930is illustratively stored in the at least one memory16of one or more of the object detection modules12′ in the form of instructions executable by the at least one processor or controller14thereof to cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 38, e.g., in one or more of the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 38. For purposes of the following description, the process930will be described as being executed by the at least one processor or controller26of the vehicle control computer24, it being understood that the process930may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers14,42,62.

The process930illustratively begins at step932where the processor or controller26is operable to determine whether an in-range mobile communication device (MCD)34, i.e., an MCD34known to the processor or controller26, has been detected. In some embodiments, the processor or controller86of an MCD34is configured to continually or periodically initiate or attempt UWB communications with a vehicle control computer24known to it by activating the UWB transceiver88to emit one or more UWB radiation signals and then waiting for a time period to determine whether a matching or otherwise expected return UWB radiation signal, emitted by one or more UWB transceivers32under the control of a vehicle control computer24known to the MCD34, is received by the UWB transceiver88. In alternate embodiments, the processor or controller26of a vehicle control computer24is configured to continually or periodically initiate or attempt UWB communications with an MCD34known to it by activating one or more of the UWB transceivers32to emit one or more UWB radiation signals and then waiting for a time period to determine whether a matching or otherwise expected return UWB radiation signal, emitted by the UWB transceiver88under the control of a processor or controller86of an MCD34known to the processor or controller26of a vehicle control computer24, is received by one or more of the UWB transceivers32. In any case, until such and in-range MCD34is detected, the process930loops back to step932. Upon detection of such an in-range MCD34, the process930advances to step934where the at least one processor or controller26of the vehicle control computer24is operable to produce and transmit to the at least one processor or controller14of one or more of the object detection modules12′ the mobile device status signal, MDSS, having a state or value corresponding to detection of the mobile communication device34, e.g., corresponding to the known MCD34being within the perimeter, P, defined about the motor vehicle70as illustrated by example inFIG. 39. This state of the MDSS signal may illustratively be any signal that notifies the at least one processor or controller14of one or more of the object detection modules12′ of an in-range MCD34, examples of which include, but are not limited to, one or more analog signals, one or more analog or digital flags, one or more digital data values, or the like.

Following step934, the processor or controller26is operable at step936to determine whether the previously in-range mobile communication device (MCD)34is now out of range. As long as the in-range MCD34remains in-range, i.e., remains within the perimeter P illustrated inFIG. 39, the processor or controller86of the in-range MCD34and the at least one processor or controller26of the corresponding vehicle control computer24continue to exchange UWB communication signals, i.e., by continually or periodically activating the respective UWB transceiver88and one or more UWB transmitters32and then waiting for corresponding time periods for return UWB signals emitted by the other, and in this manner the at least one processor or controller26of the vehicle control computer24is configured to determine whether an MCD34detected as being in-range remains in-range. As long as this is the case, the process930loops back on step936. If/when the at least one processor or controller26of the corresponding vehicle control computer24no longer receives return UWB radiation signals emitted by the MCD34within an expected time period following activation of one or more of the UWB transceivers32, and/or following a predefined number of such attempts, the at least one processor or controller26of the vehicle control computer24determines that the previously in-range MCD34is now out of range, the process930advances to step938where the at least one processor or controller26of the vehicle control computer24is operable to produce and transmit to the at least one processor or controller14of one or more of the object detection modules12′ the mobile device status signal, MDSS, having a state or value corresponding to an out-of-range mobile communication device34, e.g., corresponding to the known MCD34being outside of the perimeter, P, defined about the motor vehicle70as illustrated by example inFIG. 39. This state of the MDSS signal may illustratively be any signal that notifies the at least one processor or controller14of one or more of the object detection modules12′ of a now out-of-range MCD34, examples of which include, but are not limited to, one or more analog signals, one or more analog or digital flags, one or more digital data values, or the like. Following step938, the process930illustratively loops back to step932. It will be understood that in embodiments in which the at least one processor or controller14of one or more of the object detection modules12′ is configured to determine the proximity of a known MCD34to the motor vehicle as described above, the at least one processor or controller14is configured to produce the MDSS signal but need not “transmit” the MDSS signal elsewhere unless it is to another object detection module12′.

Referring now toFIG. 45, a simplified flowchart is shown of a process940for determining whether one or more of the object detection modules12,12′ is/are to operate in the gesture access mode or the inactive mode, as these modes are described above. In the illustrated embodiment, the determination of whether to operate in the gesture access mode or the inactive mode is dependent upon the outcome of the process930illustrated inFIG. 44, i.e., whether the known mobile communication device (MCD)34, i.e., known to the control computer24of the motor vehicle and/or to the at least one processor or controller14of one or more object detection modules12′ mounted to the motor vehicle, is within our outside of the perimeter, P, illustrated by example inFIG. 39, and is thus dependent upon the state or value of the module device status signal (MDSS) produced by the at least one processor26of the vehicle control computer24(or in some alternate embodiments, produced by the at least one processor or controller14of one or more of the object detection modules12′ mounted to the motor vehicle). In alternate embodiments, notification of whether a known MCD34is within or outside of the perimeter, P, defined about the motor vehicle, e.g., is in-range or out-of-range for UWB signal communications, may be generated by the MCD34or by another processor or controller mounted to the motor vehicle.

The process940is illustratively stored in the at least one memory16of one or more of the object detection modules12′ in the form of instructions executable by the at least one processor or controller14thereof to cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 38, e.g., in one or more of the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 38. For purposes of the following description, the process940will be described as being executed by the at least one processor or controller14of the one or more of the object detection modules12′, it being understood that the process940may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62.

The process940illustratively begins at step942where the at least one processor or controller14is operable to determine whether a mobile device detection signal has been received; that is, whether the mobile device status signal (MDSS) produced and transmitted to the at least one processor or controller14by the processor26of the vehicle control computer24corresponds to detection of a known MCD34within the perimeter, P, defined about the motor vehicle in which the one or more object detection modules12′ is/are mounted, e.g., whether the MDSS signal corresponds to detection of an in-range, known MCD34. If not, the process940follows the “NO” branch of step942and advances to steps944and946where the processor or controller14enters an INACTIVE operating mode in which the processor or controller14deactivates the corresponding object detection module12′. In some embodiments, the processor or controller14is operable at step946to produce and transmit one or more control signals to the remaining object detection modules12′ mounted to the motor vehicle to which the processors or controllers14thereof are responsive to deactivate the respective one of those object detection modules12′. In some alternate embodiments, such one or more control signals may be transmitted to the vehicle control computer24which, in turn, transmits such one or more control signals to the remaining object detection modules12′ to which the processors or controllers14thereof are responsive to deactivate the respective one of those object detection modules12′. In any such embodiments, the processor(s) or controller(s)14of the one or more object detection modules12′ is/are illustratively operable to “deactivate” the one or more object detection modules12′ by any conventional process or technique which causes the processor or controller14thereof to ignore or otherwise not act upon any reflected UWB radiation signals received from one or more UWB transceivers32or from any other source (e.g., from the vehicle control computer24), or in any other form, e.g., time difference signals received from the vehicle control computer24or from any other source. In alternate embodiments in which one or more of the object detection modules12′ includes at least one UWB transceiver100′ as described above, the processor(s) or controller(s)14of such one or more object detection modules12′ is/are illustratively operable to “deactivate” their respective object detection modules12′ by not activating the respective UWB transceivers100′ for purposes of granting gesture access to a closure of the motor vehicle, i.e., so that no UWB radiation signals will be emitted by any UWB transceiver100′ and ergo no reflected UWB radiation signals will be detected thereby. In any case, following step946, the process940illustratively loops back to step942.

If, at step942, the most recent MDSS signal received corresponds to detection of an in-range and known MCD34, the process940advances to steps948and950where the processor or controller14enters a GESTURE ACCESS operating mode to execute a gesture access control process. An example implementation of the gesture access control process is illustrated inFIG. 46and will be described in detail below. Following step950, the process942illustratively advances to step952where the processor or controller14continues to monitor the mobile device status signal (MDSS). As long as the MDSS signal continues to correspond to in-range detection of the known MCD34, the process940loops back to the beginning of step952. At some point, e.g., when the possessor of the in-range MCD34exits the motor vehicle and advances beyond the perimeter P defined about the motor vehicle, the processor or controller26of the vehicle control computer24(or, in some embodiments, the processor or controller14of one or more of the object detection modules12′) changes the mobile device status signal (MDSS) produced and transmitted thereby to a state or value corresponding to the previously in-range MCD34now being out of range, i.e., beyond perimeter P. When this occurs, the processor or controller14of the one or more object detection modules12′ is responsive to the now out of range MDSS state or value to loop from the “NO” branch of step952to steps944and946where the processor or controller14enters the INACTIVE mode described above.

Referring now toFIG. 46, a simplified flowchart is shown of an embodiment of a gesture access control process960that may be executed at step950of the process940illustrated inFIG. 45. The process960is illustratively stored in the at least one memory16of one or more of the object detection modules12′ in the form of instructions executable by the at least one processor or controller14thereof to cause the at least one processor or controller14to execute the corresponding functions. It will be understood that in some alternate embodiments, such instructions may be stored, in whole or in part, in any one or more of the memory units illustrated inFIG. 38, e.g., in one or more of the memory28of the vehicle control computer24, the memory44of the actuator driver circuit(s)40and the memory64of the audio/illumination device driver circuit(s)60, and executed, in whole or in part, by any one or more of the processors or controllers illustrated inFIG. 38. For purposes of the following description, the process960will be described as being executed by the at least one processor or controller14of the one or more of the object detection modules12′, it being understood that the process960may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62. For purposes of the following description, the process960will be described as being executed by the processor or controller14, it being understood that the process960may alternatively or additionally be executed, in whole or in part, by one or more of the processors or controllers26,42,62.

The process960is illustratively executed by any one or more, or all, of the object detection modules12,12′ mounted to the motor vehicle, e.g., any of the object detection modules12,12′ mounted to the motor vehicle in the example illustrated inFIG. 39. In this regard, decisions and commands made or generated by the processor or controller14of one object detection module12,12′ may be communicated to others of the object detection modules12,12′ so that the processors or controllers14of such other object detection modules12,12′ can act on the same decisions and/or carry out the same commands. It will be understood that some embodiments of the object detection module12,12′ may not include one or more components of other object detection modules12,12′. In this regard, dashed-line boxes are illustratively shown around some of the steps or groups of steps of the process960to identify steps which are part of the process960when the object detection module12′ includes at least one illumination device112. With the exception of step986, such steps are illustratively omitted in embodiments in which the object detection module12′ does not include any such illumination devices112.

The process960illustratively begins at step962. In some embodiments of the object detection module(s)12′, the processor or controller14is operable at step962to activate one or more of the UWB transceivers32to emit UWB radiation and to then monitor the one or more UWB transceivers32for detection of reflected UWB radiation signals. In other embodiments, the object detection module(s)12,12′ may include(s) one or more object detection transceivers, e.g.,102,104or132,134in the case of the object detection module(s)12, and100′ in the case of the object detection module(s)12′, and in such embodiments the processor or controller14may be operable at step962to activate one or more of the transmitter(s)102,132or transceiver(s)100′ to emit radiation and to monitor the one or more transmitter(s)104,134or transceivers100′ for detection of reflected radiation signals. In still other embodiments, the UWB transceivers32are activated, i.e., to emit UWB radiation, by operation of the processor or controller26of the vehicle control computer24or other processor/controller, and in such embodiments the processor or controller14is operable to receive the timing or other indicator of UWB transceiver activation from the processor or controller26or other processor/controller, and to then monitor for reflected UWB radiation signals. In some such embodiments, the processor or controller14of the object detection module(s)12′ is operable at step962to monitor the one or more UWB transceivers32directly for reflected UWB radiation signals, and in other embodiments the processor or controller14is operable to monitor the vehicle control computer24or other processor/controller to receive the from the control computer24or other processor/controller the reflected UWB radiation signals received thereby. In some embodiments, the reflected UWB radiation signals received from the control computer24or other processor/controller are the raw or pre-conditioned transceiver signals, and in other embodiments the reflected UWB radiation signals are received from the control computer24or other processor/controller in the form of timing, relative to the timing of transceiver activation, of receipt by the control computer24or other processor/controller of the reflected UWB radiation signals. In the latter case, the processor or controller14may receive the UWB transceiver information in the form of timing values of each of the UWB transceiver activation signals and the corresponding reflected UWB radiation signals, or in the form of time difference values each corresponding to a difference between a UWB transceiver activation signal and receipt of a corresponding reflected UWB radiation signal. In any case, the process960advances from step962to step964where the processor or controller14is operable to determine whether reflected radiation signals, e.g., in any of the forms described above, have been received. If not, the process960loops back to the beginning of step964.

In embodiments in which the object detection module12,12′ includes one or more illumination devices, the process960illustratively includes step966to which the process960advances following the “YES” branch of step964. In other embodiments in which the object detection module12,12′ does not include one or more illumination devices112, the process960does not include step966and the process960advances from the “YES” branch of step964to step972. If included, step966illustratively includes step968in which the processor or controller14is operable to identify one or more illumination devices112to illuminate based on the received object detection (OD) signal(s) produced by the radiation emission and detection assembly100,130in the case of object detection module(s)12or based on reflected UWB radiation signals received, in any of the forms described above, from one or more of the UWB transceivers32in the case of object detection module(s)12′. Thereafter at step970, the processor or controller14is operable to control one or more of the driver circuit(s) DC to illuminate the identified illumination device(s)112according to a predefined detection scheme. The predefined detection scheme may illustratively take any of the forms described above with respect to step708of the process700illustrated inFIG. 35.

Following step966, in embodiments which include step966, and otherwise following the “YES” branch of step964, the processor or controller14is operable at steps972,974and976to process (at step972) the activation and reflected radiation signals, as these signals are described above with respect to step962, to compare (at step974) the processed signals to one or more vehicle access condition (VAC) values stored in the memory16(or the memory28,42and/or64), and to then determine (at step976) whether VAC is satisfied. In some embodiments, the processor or controller14is operable to process the activation and reflected radiation signals to determine time difference values between the activation and reflected radiation signals if not already provided in this form to the processor or controller14, e.g., by the processor or controller26of the vehicle control computer24and/or by another processor or controller, and in such embodiments the stored VAC value(s) illustratively correspond to a predetermined sequence or other collection of time difference values suitable for comparison with the time difference values determined by the processor or controller14based on the activation and reflected radiation signals. In other embodiments, the processor or controller14may be operable to process the activation and reflected radiation signals according to one or more alternate signal processing strategies, and in such embodiments the stored VAC value(s) illustratively correspond to a predetermined sequence or other collection of like signals and/or values suitable for comparison with the processed signals and/or values determined by the processor or controller14based on the activation and reflected radiation signals.

If, at step976, the processor or controller14determines that, resulting from comparison of the processed activation and reflected radiation signals with the stored VAC value(s), VAC is not satisfied; that is, the processed activation and reflected radiation signals do not match the stored VAC value(s), the process960illustratively advances to step978where the processor or controller14is operable to determine whether a time limit has been exceeded. In some embodiments, the time limit at step978is a stored time limit within which the processor or controller14is expected to execute steps972-976. In alternate embodiments, the time limit may be a dynamic time limit determined by the processor or controller14as a function of any of one or more operating conditions within the system10′, one or more components of the system10′ and/or one or more environmental or other conditions external to the system10′. In any case, if the processor or controller14determines at step978that the time limit has not been exceeded, the process960illustratively loops back to step966, in embodiments which include step966, or to step972in embodiments which do not include step966, to process additional activation and reflected radiation signals.

In embodiments in which the object detection module12,12′ includes one or more illumination devices, the process960illustratively includes step980to which the process960advances following the “YES” branch of step978, i.e., if the processor or controller determines at step978that the time limit has been exceeded. In such embodiments, the processor or controller14is illustratively operable at step980operable to control one or more illumination devices112, e.g., as described above, to illuminate based on a predetermined, i.e., stored, fail scheme, wherein the processed activation and reflected radiation signals are determined by the processor or controller14, to fail to exhibit a predefined gesture as described above within the predefined time period following the first execution of step972. The fail scheme may illustratively take any of the forms described above with respect to step722of the process700illustrated inFIG. 35.

If, at step976, the processor or controller14determines that, resulting from comparison of the processed activation and reflected radiation signals with the stored VAC value(s), VAC is satisfied; that is, the processed activation and reflected radiation signals match the stored VAC value(s), the process960illustratively advances to step984where the processor or controller14is operable to control one or more of the actuator driver circuits40to activate one or more corresponding vehicle access actuators46in order to actuate one or more corresponding vehicle access closure devices. Examples of such vehicle access closure devices may include, but are not limited to, one or more access closure locks, one or more access closure latches, and the like. At step984, the processor or controller14may be operable to, for example, control at least one lock actuator associated with at least one access closure of the motor vehicle to unlock the access closure from a locked state or condition and/or to lock the access closure from an unlocked state or condition, and/or to control at least one latch actuator associated with at least one access closure of the motor vehicle to at least partially open the access closure from a closed position or condition and/or to close the access closure from an at least partially open position or condition. In some embodiments, the processor or controller14of each of the object detection modules12,12′ mounted to the motor vehicle may execute the process960, or at least some portion(s) thereof, and in such embodiments the processor or controller14of each object detection module12,12′ may, at step984, control at least one actuator driver circuit40to activate the one of the vehicle access actuators46associated therewith. In alternate embodiments, the processor or controller14of any of the object detection modules12,12′ that executes step984may communicate a vehicle access actuation command to the processor(s) or controller(s)14of other object detection modules12,12′ mounted to the motor vehicle.

In embodiments in which the object detection module12,12′ includes one or more illumination devices112, the process960may further include step982which may be executed prior to step984or along with step984. In such embodiments, the processor or controller14is illustratively operable to control one or more of illumination devices112, e.g., via control of one or more of the driver circuit(s) DC, according to an “access grant” illumination scheme. Illustratively, the “access grant” illumination scheme may take any of the forms described above with respect to step720of the process700illustrated inFIG. 35.

In some embodiments, the process960may optionally include a step986to which the process960advances from step984, as illustrated by dashed-line representation inFIG. 46. In embodiments which include it, the processor or controller14is illustratively operable at step724to control one or more of the audio and/or illumination device driver circuits60to activate one or more corresponding audio and/or illumination devices66in addition to controlling one or more vehicle access actuators to activate one or more vehicle access devices at step984following detection at step976of exhibition of a predefined gesture by the object within the sensing region of at least one of the radiation transceivers. Example audio devices which may be activated at step986may include, but are not limited to, the vehicle horn, an audible device configured to emit one or more chirps, beeps, or other audible indicators, or the like. Example illumination devices which may be activated at step986, in addition to one or more of the illumination devices112(in embodiments which include one or more such illumination devices112) or in any embodiment instead of one or more of the illumination devices112, may include, but are not limited to, one or more existing exterior motor vehicle lights or lighting systems, e.g., headlamp(s), tail lamp(s), running lamp(s), brake lamp(s), side marker lamp(s), or the like, and one or more existing interior motor vehicle lights or lighting systems, e.g., dome lamp, access closure-mounted lamp(s), motor vehicle floor-illumination lamp(s), trunk illumination lamp(s), or the like. In any case, following step986, or following step984in embodiments which do not include step986, the process960illustratively returns to the process940illustrated inFIG. 45.

While this disclosure has been illustrated and described in detail in the foregoing drawings and description, the same is to be considered as illustrative and not restrictive in character, it being understood that only illustrative embodiments thereof have been shown and described and that all changes and modifications that come within the spirit of this disclosure are desired to be protected. Obviously, many modifications and variations of this disclosure are possible in light of the above teachings, and it is to be understood that the various features described herein may be practiced in any combination whether or not specifically recited in the appended claims.