In-vehicle device for controlling a movable barrier operator

In one aspect, an in-vehicle device is provided that includes a sensor configured to detect a vehicle characteristic indicative of the vehicle being in proximity to a location associated with a movable barrier operator. The in-vehicle device includes communication circuitry to communicate an open command to the movable barrier operator that causes the movable barrier operator to open a movable barrier connected to the movable barrier operator. A memory is configured to store a vehicle arrival condition indicative of whether the vehicle arrived at the location associated with the movable barrier operator. A processor is configured to determine satisfaction of the vehicle arrival condition and, upon the vehicle arrival condition not being satisfied, cause the communication circuitry to communicate a close command to the movable barrier operator that causes the movable barrier operator to close the movable barrier.

FIELD

The subject matter of this application relates to movable barrier operators and, more particularly, to in-vehicle devices for controlling movable barrier operators.

BACKGROUND

Various types of remote controls for movable barrier operators are known in the art for controlling the position of a movable barrier associated with the movable barrier operator such as a radio frequency transmitter. The transmitter may be part of or connected to in-vehicle hardware, such as an infotainment or navigation system, that allows a user to set a geographic area associated with the user's home such that the transmitter will transmit a signal to open or close the movable barrier upon the vehicle entering or exiting the area. In this manner, the user does not need to manually actuate the transmitter each time the vehicle enters or exits the area.

DETAILED DESCRIPTION

In accordance with one aspect of the present disclosure, a system is provided for controlling access to a secured area. The system may include a first movable barrier operator configured to control movement of a first movable barrier, a second movable barrier operator configured to control movement of a second movable barrier, and a server computer in communication with the first and second movable barrier operators. The system further includes a remote control configured to communicate with the movable barrier operators and/or the server computer. The remote control may include, for example, a device associated with a vehicle.

The remote control and/or the server computer may communicate a state change request to one or more of the movable barrier operators upon a satisfaction of one or more vehicle parameters. The vehicle parameters may include, for example, the proximity of the remote control relative to the secured area, the speed of the vehicle, and the direction of travel of the vehicle.

The server computer, remote control, and/or movable barrier operators include one or more processors configured to select a movable barrier operator from among the first and second movable barrier operators to operate in response to the state change request. The movable barrier operator may be selected at least in part based upon a behavior profile associated with a user. The behavior profile may be compiled at least in part based upon historical data (e.g., the user's prior operation of the movable barrier operators). For example, the particular user typically operates a particular movable barrier operator at a particular time (e.g., at 6 P.M.) on a particular day of the week (e.g., Monday).

Upon selecting the movable barrier operator from among the first and second movable barrier operators to operate, the system may perform an obstacle detection process. The obstacle detection process may be performed, for example, using a camera directed at an area associated with the selected movable barrier. In response to detecting an obstacle (e.g., another vehicle) at the area associated with the selected movable barrier, one or more of the server computer, remote control, and movable barrier operators may operate a movable barrier operator different than the initially-selected movable barrier operator.

In another aspect of the disclosure, a method is provided for operating a movable barrier operator. The method includes determining satisfaction of a predetermined relative proximity of the in-vehicle device relative to a movable barrier operator. If the relative proximity determination is satisfied, the method may include transmitting a control command (e.g., an open or close command) via RF transmission or other short-range transmission. If the relative proximity determination is not satisfied, the method may include transmitting a command via a wide area transmission.

Referring now toFIG.1, a garage14having a movable barrier operator system10is shown. The movable barrier operator system10may include a movable barrier operator12. Examples of movable barrier operators12include chain or belt-driven garage door openers, gate operators, roller shutter systems, and jackshaft garage door operators.

The movable barrier operator12may be mounted within a secured area, such as within the garage14. More specifically, the movable barrier operator12may be mounted to a ceiling16of the garage14. The movable barrier operator12may include, or may be connected to, a rail18. A releasable trolley20may be attached to the rail18. The releasable trolley20may have an arm22extending to a movable barrier, such as a multiple-paneled garage door24, positioned for movement along a door tracks26and28. The movable barrier operator12may have a motor configured to open and close the garage door24via a coupling such as a belt, chain or screw shaft, the trolley20, and the arm22. Operation of the motor produces movement of the garage door24. Although described herein as a garage door24, other forms of movable barriers may be controlled by the movable barrier operator12.

The movable barrier operator12may also include circuitry such as, for example, processing circuitry72(FIG.2) with a processor and a non-transitory computer readable memory to control the motor and manage other hardware and/or software features. The movable barrier operator system10may include one or more remote controls. The processing circuitry72of the movable barrier operator12may be configured to determine whether to operate in response to commands from the remote controls. The one or more remote controls may include portable transmitter units30,32configured to send radio frequency control commands for reception by communication circuitry including an antenna34of the movable barrier operator12. The remote controls may also include an external control pad36, with a button or buttons thereon, that may be positioned on the outside of the garage14. The external control pad36may communicate control commands via radio frequency transmission for reception by the antenna34of the movable barrier operator12. Other examples of remote controls include user devices such as smartphones, tablet computers, personal computers, and wearable devices (e.g., smartwatches) that are operable to control operation of the movable barrier operator12over the internet via a server computer.

A wall control or switch module40is connected to the movable barrier operator12by one or more wires42. In another aspect, the switch module40may communicate with the movable barrier operator12wirelessly or via a combination of wired and wireless signals. The switch module40may include one or more of a light switch44, a lock switch46, and a command switch48.

An optical emitter50may be connected via a power and signal line52to the movable barrier operator12. An optical detector54may be connected via a line56to the movable barrier operator12. Alternatively, at least one of the optical emitter50and the optical detector54may communicate wirelessly with the movable barrier operator12. Furthermore, the optical emitter50and the optical detector54may be combined as a single unit (e.g., as a retroreflector).

The movable barrier operator12may communicate via wired or wireless protocols with one or more remote controls and/or one or more remote devices. The movable barrier operator12includes communication circuitry74(FIG.2), which may include a receiver, transmitter, and/or a transceiver. The communication circuitry74may be configured to communicate via one or more approaches, such as radio frequency communications utilizing different frequencies and one or more protocols. For example, the communication circuitry74may communicate via 300 MHz-400 MHz radio frequency signals with transmitters30,32, and with user devices via a Wi-Fi connection to a local wireless network and the internet. The communication circuitry74may be configured to communicate with remote controls and other remote devices using other approaches such as Bluetooth®, ZigBee, ultrasonic signals, infrared (IR) signals, or combinations thereof. A wired or wireless gateway may permit the movable barrier operator12to access an external network, such as the internet. The gateway may be a router, modem, access point, digital assistant, or a smart house hub, as some examples.

RegardingFIG.1, the movable barrier operator system10may include a camera module70. The camera module70may include a camera that is situated to capture security data such as still images/pictures, video, and/or audio within the garage14. The camera module70may be configured to continuously capture security data. Alternatively, the camera module70may capture security data at certain times. For example, the camera module70may be configured to start capturing security data when the movable barrier operator system10opens the garage door24or shortly before the movable barrier operator12starts to open the garage door24. The camera may continue to capture security data when the garage door24is open until the garage door24is closed or for a predetermined amount of time after the garage door24is closed. In further examples, the camera module70may be configured to capture security data based on sensed motion within the garage14, or to start capturing security data in response to the movable barrier operator system10receiving an open command that includes information indicating an entity with limited access permission has requested opening of the garage door24.

In some forms, the camera module70may further include a speaker and/or a microphone such that verbal communications may be exchanged between a person located in or near the garage14and a remote user.

RegardingFIG.2, the movable barrier operator12is configured to communicate with different external devices. For example, the communication circuitry74may include at least one antenna34configured to communicate with one or more switch modules40, the transmitters30,32, and one or more remote server computers92. The communications may utilize, for example, one or more of WiFi, Bluetooth®, ZigBee, infrared, cellular, WiMax, or LoRaWAN.

The communication circuitry74may also be capable of communicating via wired approaches, such as communications involving telephone systems, cable systems, power line transmission, or fiber optic lines. Additional forms of wired and wireless communication may also be utilized.

The processing circuitry72operates the movable barrier operator12in response to authorized state change requests being received at the communication circuitry74. The processing circuitry72may also be configured to provide commands to control one or more peripheral devices76. Such peripheral devices76may include object detectors (e.g., optical emitter50and/or optical detector54), battery chargers, external lights, fans, air compressors, cameras, motion sensors, and alarm systems to name but a few examples. Additional peripheral devices common to households and garages may also be controlled by the movable barrier operator12.

Referring now toFIG.3, a vehicle80includes an in-vehicle device82, such as a human-machine interface of the vehicle80. The in-vehicle device82may be configured to communicate directly with the movable barrier operator12via radio frequency signals or indirectly via a network90and a server computer, such as remote server computer92, connected thereto. The network90may include one or more networks such as the internet and wide area networks. The direct and/or indirect communications between the in-vehicle device82and the movable barrier operator permit the in-vehicle device82to initiate a change of state (e.g., open or closed) of the garage door24when the vehicle80is near the garage14, or distant from the garage14(e.g., via indirect communication over a wide area network).

A user84may also communicate with the movable barrier operator12via the network90and the remote server computer92; for example, via a user device86(e.g., smartphone, smartwatch, tablet, or another portable device). Other devices, such as a computing device94, may communicate with the network90, as discussed in greater detail elsewhere herein. The computing device94may be, for example, a security system, a personal digital assistant, a desktop computer, a smartphone, smartwatch, or tablet computer.

Referring toFIG.4, the in-vehicle device82may include a sensor100to detect a vehicle parameter of the vehicle80. It is intended that “a” may refer to “at least one” such that references to “the sensor” encompass one, two, or more sensors. Similarly, references to “the vehicle parameter” encompass one, two, or more vehicle parameters.

In one example with reference toFIG.3, the sensor100includes a global navigation satellite system (GNSS) receiver, such as a GPS receiver. The GNSS receiver receives location and/or timing data from one or more satellites78, and the in-vehicle device82determines the location of the vehicle80based on the received data. Alternatively or additionally, the in-vehicle device82may determine the location of the vehicle80based on data from other sources, such as data from a nearby stoplight88or cellular tower98. The sensor100may also include a sensor that detects a rotation of or otherwise communicates with a vehicle powertrain component that corresponds to the vehicle speed. The sensor100may also include an optical instrument, such as a standard optical camera or a thermographic camera, that may be configured to capture still or moving imagery within or outside of the vehicle.

The in-vehicle device82may further include communication circuitry110configured to communicate directly or indirectly with the movable barrier operator12. For example, the communication circuitry110may include a radio frequency signal transmitter112(e.g., operable within the 300 MHz-900 MHz radio frequency band) configured to send a control command directly to the movable barrier operator12to cause a state change of the garage door24. For example, the communication circuitry110may be configured to automatically initiate a state change of the garage door24based upon a parameter of the vehicle80such as the vehicle being within a predetermined proximity of the garage14. The radio frequency signal transmitter112may be a universal transmitter configured to operate a plurality of different operator types. As one example, the radio frequency signal transmitter112may be a Homelink®-style transmitter.

The communication circuitry110may further include a wide area network interface114configured to communicate with the network90to send a state change request to the remote server computer92. The state change request causes the remote server computer92to send a control command to the movable barrier operator12to cause the movable barrier operator12to change the state of the garage door24(e.g., close to open or vice versa). The wide area network interface114may communicate using, for example, cellular (3G, 4G, 4G LTE, 5G), WiMAX, LoRaWAN, and/or LTE-M. Additionally, the communication circuitry110may include a short-range wireless interface such as a short-range wireless transceiver116for communicating with the movable barrier operator12using one or more protocols including, for example, Bluetooth, Bluetooth Low Energy (BLE), Near Field Communication (NFC), WiFi, Z-wave, and ZigBee protocols.

The in-vehicle device82may further include a memory120and a processor122. The memory120is configured to store information, such as information pertaining to one or more of a user (or users), the vehicle80, and a secured area such as the garage14. The processor122is configured to perform instructions stored in the memory120, such as determining satisfaction of a user account condition.

The in-vehicle device82may further include a user interface130. The user interface130may include a visual display132, a user input interface134, a microphone136, and/or a speaker138. In one approach, the visual display132and the user input interface134may be an integrated interface. An integrated interface may be, for example, in the form of a touch-sensitive display screen. For example, the touch-sensitive display screen may display a virtual button, a virtual keyboard, or a virtual keypad that allows a user to provide an input. In this manner, the same interface that conveys information to a user can also receive a user input. In still another approach, the user input interface is a dedicated user input interface. Such a dedicated user input134may include a single button, a keyboard, a keypad, or a touch-sensitive surface responsive to a user's touch. The microphone136may receive voice commands from a user in the vehicle. The speaker138may convey audible messages to the user.

The processor122may be operatively coupled to one or more of the sensor100, the communication circuitry110, the memory120, and one or more components of the user interface130(e.g., visual display132, user input interface134, microphone136, and speaker138).

In another aspect, the in-vehicle device82is a user's smartphone or other portable electronic device such as a media player. The smartphone may communicate with the vehicle80to receive data, such as the location and speed of the vehicle80. The smartphone may also be configured to retrieve the data itself. For example, the smartphone may receive location data from GPS satellites or cellular towers and determine the location of the vehicle80and determine whether the vehicle80has entered or exited a geofenced area. The smartphone may communicate a state change request to the movable barrier operator12via the remote server computer92or connect to the vehicle80, such as via Bluetooth, and cause a radio frequency transmitter of the vehicle80to transmit a control command to the movable barrier operator12.

The in-vehicle device82may be configured to communicate with the movable barrier operator12(either directly with radio frequency signals or indirectly via the remote server computer92and network90) to cause the movable barrier operator12to control movement of the garage door24. According to one aspect, operation of a movable barrier operator12may be automated. The term “automatic operation” of the movable barrier operator12is used herein to mean the user does not have to manually operate the in-vehicle device82to open or close the garage door24. The in-vehicle device82may thereby autonomously, and without user intervention, operate the movable barrier operator12upon the in-vehicle device82determining satisfaction of one or more user account conditions. For example, the in-vehicle device82may be configured to communicate with the movable barrier operator12to cause the movable barrier operator12to open the garage door24as the vehicle80approaches the garage14. The in-vehicle device82may also be configured to communicate with the movable barrier operator12to cause the movable barrier operator12to close the garage door24, for example, as the vehicle80departs the garage14. According to another aspect, operation may be partially- or semi-automated. For example, a user may be prompted (e.g., at the in-vehicle device82) prior to the in-vehicle device82communicating a control signal to the movable barrier operator12. The user may then confirm the user's desire (e.g., via an explicit response such as an acknowledgment (ACK) or negative acknowledgement (NACK), or by a passive response such as taking no action such that the prompt expires) to operate the movable barrier operator12.

The in-vehicle device82may automatically trigger operation of the movable barrier operator12upon the sensor100of the in-vehicle device82detecting a vehicle parameter that indicates or relates to an automatic operation of the movable barrier operator12. The vehicle parameter may be, for example, the location of the vehicle80, and the in-vehicle device82may determine where the vehicle80is within a predetermined area associated with the movable barrier operator system10. The vehicle parameter may include a parameter instead of or in addition to vehicle location, such as vehicle speed and/or orientation with respect to the garage14. As such, communication between the in-vehicle device82and the movable barrier operator12may provide automatic operation of movable barrier operator12to control movement of the garage door24.

With reference toFIG.5, the communications between the in-vehicle device82and the movable barrier operator12may include information related to one or more pre-determined user account conditions140set by a user that specify parameters for prompted or automatic operation of the movable barrier operator12. The user account condition140is a condition that affects the user's interaction with the system10. The user account condition140may be set with regard to parameters unrelated to the vehicle80, such as weather, time of day, and who is (or is not) present in a building associated with the garage14or area secured by the movable barrier operator12and garage door24. The user account condition140may be set at the in-vehicle device82or at the computing device94. For example, if the vehicle80enters a geofenced area associated with the movable barrier operator12and the user account condition140is satisfied, then the in-vehicle device82, the user device86, remote server computer92, and/or computing device94cause a control command to be automatically communicated to the movable barrier operator12to open the garage door24. Conversely, if the vehicle80enters the geofenced area and the user account condition140is not satisfied, then a control command is not communicated to the movable barrier operator12despite the vehicle80entering the geofenced area. A user account condition140may operate as a check on whether or not the in-vehicle device82automatically operates the movable barrier operator12independent of whether the sensed vehicle parameter indicates automatic operation of the movable barrier operator12. By utilizing user account conditions140to inform automatic operation of the movable barrier operator12, the in-vehicle device82is less likely to operate the movable barrier operator12when undesired by the user.

An account user condition140may be entered at a user interface142. The user interface142may be provided, for example, at one or both of the in-vehicle device82and at the computing device94. The user interface142may include, for example, a touch screen144, a microphone, speaker, and/or a keyboard. A user may enter account information such as credentials including a username and password at the user interface142to access a user account146. Upon successful log in, the user interface142may display a graphical user interface for receiving user account conditions140. For example, the user interface142may have a list with one or more user conditions140that the user may select. In this example, the user account conditions140refer to three parameters: vehicle speed threshold140A, user identity140B, and ambient weather140C. The user may select (e.g., by touching the touch screen144of the user interface142) which conditions140the user wants to have considered for automatic operation of the movable barrier operator12. The user may also leave unchecked parameters (e.g. schedule parameter140D) that may not be satisfied for automatic operation of the movable barrier operator12. As shown inFIG.5, the user has selected the vehicle speed threshold140A as being a user account condition140that will be considered. The user has further selected that the speed threshold140E of the vehicle80as it approaches the garage14be under 20 mph. The user has also selected the user identity140B to be considered for automatic operation of the movable barrier operator12. For example, the sensor100of the in-vehicle device82may include a sensor configured to detect the identity of the user device86(seeFIG.1) associated with a user in the vehicle80, such as a smartphone, smart watch, key, or key fob. The processor122determines if the selected user identity140F matches the in-vehicle identity detected by the sensor100. Alternatively or additionally, the sensor100may be operable to detect a specific user/driver via weight, biometrics (e.g., facial, iris, fingerprint recognition) and/or seat adjustment, pedal height adjustment, steering wheel adjustment, or other vehicle-personalization selection or settings. The user has also indicated the ambient weather conditions outside of the garage14to be one of the user account conditions140considered for automatic operation of the movable barrier operator12. The in-vehicle device82may receive ambient weather data via the communication circuitry110, such as from a satellite or from the user device86. The user has specified that it not be snowing140G as a condition for automatically operating the movable barrier. Thus, the in-vehicle device82will not automatically operate the movable barrier operator12if snow is falling. The selected user account conditions140A,140B,140C may be stored in the memory120of the in-vehicle device82. Other examples of user account conditions140are described below.

In one application, as the vehicle80approaches the garage14, the processor122uses GPS data from the sensor100to first determine whether the vehicle80is within a geofenced area associated with the garage14. In one example, the location of the vehicle80is a vehicle parameter that must be satisfied before the one or more user account conditions140are checked. The processor122then determines whether the user account conditions140A,140B,140C are satisfied. More specifically, if (1) the speed of the vehicle80is below 20 mph, (2) the user is “dad,” and (3) it is not snowing outside, then the user account conditions140A,140B,140C have been satisfied. The processor122will then cause the communication circuitry110to automatically transmit the control command from the radio frequency transmitter to the movable barrier operator12to open the garage door24. In another example, if the user conditions140A,140B,140C are satisfied, the processor122will cause the communication circuitry110to transmit the state change request to the remote server computer92via the network90, and the remote server computer92will communicate a control command to the movable barrier operator12.

The remote server computer92may facilitate operation of the movable barrier operator12. The remote server computer92may make decisions in conjunction with or in place of decision-making at the in-vehicle device82, such as whether the vehicle parameter detected by the sensor100indicates automatic operation of the movable barrier operator12and whether the user account condition140has been satisfied. For example, and with reference toFIG.6, the remote server computer92includes a network or communication interface150configured to communicate via the network90with the movable barrier operator12and cause the movable barrier operator12to move the garage door24. The communication interface150is further configured to receive data from the in-vehicle device82via the network90regarding the vehicle parameter of the vehicle80. Additionally, the communication interface150receives the user account condition140from the in-vehicle device82, the computing device94, or the user device86. The remote server computer92also includes a memory152to store information such as user account conditions140, as well as a processor154that is operatively coupled to the communication interface150and the memory152. The processor154may determine whether the vehicle parameter of the vehicle80indicates automatic operation of the movable barrier operator12, and whether the user account condition140is satisfied. If the vehicle parameter indicating automatic operation of the movable barrier operator12has been received and the user account condition140has been satisfied, then the remote server computer92will communicate a state change command to the movable barrier operator12via the network90to open the garage door24. For example, the remote server computer92may send a message to the movable barrier operator12. However, in one aspect, no state change command is sent if the vehicle parameter indicates automatic operation but fewer than all of the user account conditions have been satisfied.

With reference toFIG.7, the movable barrier operator12may have a motor160configured to be connected to a movable barrier, such as the garage door24. The movable barrier operator12may also include a memory162. The memory162may store identification and security (e.g. rolling code) information for authorized remote controls.

The movable barrier operator12may also include the communication circuitry74. The communication circuitry74may be configured to receive the parameter of the vehicle80and the user account condition140, for example, from the remote server computer92or directly from the in-vehicle device82. The communication circuitry74includes a radio frequency signal receiver or transceiver172that may receive a command signal from the radio frequency signal transmitter112of the in-vehicle device82to change the state of the garage door24.

The communication circuitry74may further include a long-range wireless transceiver174. The long-range wireless transceiver174may be configured to communicate with the remote server computer92over the network90. The transceiver174may receive a state change command from the remote server computer92(via the network90) to cause the movable barrier operator12to change the state of the garage door24. The transceiver174may also communicate information to other devices via the network90, such as information identifying a user of the vehicle80to the computing device94. The transceiver174may communicate with the network90via a wireless gateway or access point, such as a WiFi router. Additionally, the communication circuitry74may include a short-range wireless transceiver176for communication with the short-range wireless transceiver116of the in-vehicle device82. For example, the short-range wireless transceiver116may be configured to receive the command signal from the in-vehicle device82over a short-range wireless protocol, such as Bluetooth.

The long-range wireless transceiver174and the short-range wireless transceiver176may both be configured to receive parameters of the vehicle80from a plurality of other devices. For example, the long-range wireless transceiver174and/or the short-range wireless transceiver176may be in communication with other local devices (e.g., home appliances, other vehicles, smartphones, etc.) to exchange and collect data that the in-vehicle device82provides. The long-range wireless transceiver174and the short-range wireless transceiver176may receive data from the other devices as part of a mesh network.

For example, the long-range wireless transceiver174of the movable barrier operator12may receive a signal from a LoRa-based sensor for wireless, long-range radio transmissions with low power consumption mounted to a stoplight, or from a V2X (vehicle to anything) component mounted to a stop sign at an intersection near the garage14upon the sensor detecting a beacon signal from the in-vehicle device82. The movable barrier operator12would thereby be able to determine the vehicle80is nearby.

The movable barrier operator12also includes the processing circuitry72operatively coupled to the motor160and the communication circuitry74. The movable barrier operator12may make decisions in conjunction with or in place of decision-making at the in-vehicle device82and/or the remote server computer92. The decisions may include deciding whether the vehicle parameter identified by the sensor100indicates automatic operation of the movable barrier operator12and whether the user account condition140has been satisfied. For example, the processing circuitry72may be configured to cause the motor160to move the movable barrier24upon receiving the parameter of the vehicle80indicating automatic operation of the movable barrier operator12and the user account condition140being satisfied. Conversely, the processing circuitry72may be configured to not effect movement of the movable barrier24upon the received parameter of the vehicle80indicating automatic operation of the movable barrier operator12but fewer than all of the user account conditions being satisfied.

The movable barrier operator12may include a movable barrier position sensor75configured to detect the position of the garage door24. The movable barrier position sensor75may include, for example, a tilt sensor mounted to the garage door24and configured to wirelessly transmit orientation data to the communication circuitry74. In other embodiments, the movable barrier position sensor75may include a contact closure switch and/or a hall effect sensor on the tracks of the garage door24having a wired connection to the communication circuitry74. As yet another example, the movable barrier position sensor75may include a sensor that detects rotation or translation of a component of a transmission of the movable barrier operator12as the motor160moves the garage door24. An example of a sensor that detects movable barrier position includes a rotary encoder constituted by a light source directed toward a barrier operator transmission component and a detector that detects when the light is interrupted by the rotation of the component.

The movable barrier operator12may include an imminent motion notification apparatus77configured to output an alert upon reception of a remote closure command, message or signal and/or a remote open command, message or signal of the garage door24. The imminent motion notification apparatus77may include, for example, a light that flashes or strobes, a speaker that emits a sound, or a combination thereof.

Referring now toFIG.8, a garage204having a movable barrier operator system200is shown. The movable barrier operator system200may include multiple movable barrier operators202A,202B, and202C, collectively referred to as movable barrier operators202. One or more of the movable barrier operators202may generally correspond to the movable barrier operator12previously discussed. As such, the movable barrier operators202may be provided with the various components and/or operability of the movable barrier operator12.

Each of the movable barrier operators202may be associated with a corresponding movable barrier206A,206B, and206C, collectively referred to as movable barriers206. The movable barriers206may generally correspond to the garage door24, previously discussed. Although depicted as having three movable barrier operators202A,202B,202C that are respectively associated with (e.g., mechanically connected to operate) movable barriers206A,206B,206C, the movable barrier operator system200may be provided with one, two, or more movable barrier operators and one, two, or more movable barriers. Furthermore, although depicted as being provided in a single garage204, individual movable barrier operators202may be provided in separate garages (e.g., separate structures). In some instances the system200may be used or adapted for a non-garage or non-residential context, for example, a commercial structure or building such as a warehouse, transportation/freight hub, fulfillment center, logistics center or the like that employs a plurality of the movable barrier operator(s)202and a plurality of the movable barrier(s)206.

The movable barrier operator system200may be informed of a location of the vehicle80. For example, the movable barrier operator system200may receive location data from the vehicle80(e.g., via the in-vehicle device82or user device86), or from the remote server computer92via the network90. In one aspect, the movable barrier operator system200may receive location data or projected location data from a navigation system of the vehicle80. The navigation system of the vehicle80may be part of, or in communication with, an autonomous or “self-driving” vehicle control system of the vehicle80.

The movable barrier operator system200may be configured to determine a location of the vehicle80and/or the in-vehicle device82according to a location-check routine. The location-check routine may be performed frequently to provide an accurate vehicle location for the movable barrier operator system200. In one aspect, the location-check routine may be automatically performed (for example, according to a predetermined schedule). According to another aspect, the location-check routine may be initiated when a user interface of the in-vehicle device82is initiated or presented to a user that permits the user to select which movable barrier operator202to operate. According to another aspect, the location-check routine may be initiated on a random or periodic basis. In another example, the location-check routine may be initiated upon the vehicle traveling at a particular velocity or range of velocities. For example, the movable barrier operator system200may initiate a location-check routine approximately once every ten seconds while a vehicle80is traveling within a range of approximately 40 miles-per-hour and 60 miles-per-hour, and may initiate a location-check routine approximately once every second while the vehicle80is traveling less than 30 miles-per-hour. In another aspect, the movable barrier operator system200may initiate a location-check routine more frequently while the vehicle80is traveling at a relatively higher speed as compared to when the vehicle80is traveling at a relatively lower speed.

The movable barrier operator system200may be in communication with a navigation system (e.g., including sensor100) of the vehicle80that provides the current location of the vehicle80to the system200. The user may provide a destination to the navigation system, which the navigation system communicates to the system200. The destination may include, for example, a street address and/or longitude and latitude of the destination. The destination may be a saved destination stored within the navigation system (e.g., “Home”), or may be manually input by the user for a given trip.

In one approach, the system200is configured to compare the destination to the location of the garage204. Upon determining the garage204is the destination, the system200may be configured to automatically open a movable barrier206of the garage204in response to determining the vehicle80has entered the geofenced area218. Conversely, upon determining the garage204is not the destination, the system200may not automatically open a movable barrier206of the garage204in response to determining the vehicle80has entered the geofenced area218.

In one aspect, the movable barrier operator system200may be configured to predict a particular user-desired movable barrier operator for actuation among the multiple movable barrier operators202and automatically or semi-automatically operate the predicted movable barrier operator. For example, the movable barrier operator system200may be configured to select an individual movable barrier operator202A,202B,202C at least in part as a function of the user's historical interactions with the movable barrier operator system200. The movable barrier operator system200may be configured to select the individual movable barrier operator202A,202B,202C in response to determining the vehicle80is within a predetermined proximity of the garage204(e.g., within a geofenced area218), or in response to determining the vehicle80has entered or exited a geofenced area218.

In one approach, the movable barrier operator system200may operate the movable barrier operators202based at least upon a behavior profile208. The behavior profile208may be associated with a user account146of a user. The user account146may also include the user account conditions140previously discussed.

In one aspect, the behavior profile208is stored at a remote server (e.g., remote server computer92ofFIG.3) or multiple remote servers. Alternatively or additionally, the behavior profile208may be stored in the memory120of the in-vehicle device82. Alternatively or additionally, the behavior profile208may be stored in a memory of one or more movable barrier operators202.

The behavior profile208may be based at least in part upon prior user interactions with the movable barrier operator system200. For example, each time a movable barrier operator202is operated in response to an interaction with a user, the behavior profile208for that user may be updated to include attributes associated with that operation. As such, the behavior profile208may be built using interaction data including a user parameter210, a schedule parameter212, and/or a vehicle parameter214for individual ones of user interactions with the movable barrier operator system200. The user parameter210may include, or may be associated with, identifying parameters of a user that interacts with the system200. The user parameter210may include a username associated with a user account; for example, as provided with the user account conditions140discussed elsewhere herein. The user parameter210may also include, for example, biometric information (fingerprint, retina, facial appearance, weight, seat position), identifying information for a key fob or key associated with the user, and/or identifying data of a device carried on the person such as a smartphone, a smart watch, or fitness tracker. The user parameter210may also include historical user selection information that identifies the signal frequency (e.g., 390 MHz) emitted by a remote control of a user to operate an individual movable barrier operator202A,202B,202C from among the movable barrier operators202. In this way, the user parameter210may inform the movable barrier operator system200of a user's preference for parking the vehicle80at a particular location within the garage204.

The schedule parameter212may include, or be associated with, a temporal parameter of a user interaction with the system200. In one example, the schedule parameter212may include, or may be based on, the date, time of day, day of the week, month, and/or year when one or more commands from the in-vehicle device82are communicated to operate a particular movable barrier operator (e.g., movable barrier operator202A).

The vehicle parameter214may include, for example, the speed, direction, and/or location of the vehicle80as the user interacts with the system200. The vehicle parameter214may also include proximity data indicative of whether the vehicle80is within a predetermined area associated with the movable barrier operator system10.

Additionally or alternatively, the vehicle parameter214may include a vehicle heading or orientation with respect to the garage204. As such, the vehicle parameter214may inform the movable barrier operator system200not to operate a movable barrier operator202despite the vehicle80being within a predetermined proximity of the movable barrier operator system200(e.g., within the geofenced area218). For example, when the vehicle speed exceeds a predetermined threshold while the vehicle80is within the geofenced area218, the movable barrier operator system200may not operate any of the movable barrier operators202. In one example, this operability may be set by the user account condition140A. Similarly, when the vehicle80is a heading in a direction away from the movable barrier operator system200while the vehicle80is within the geofenced area218, the movable barrier operator system200may not operate a movable barrier operator202.

Alternatively or additionally, the vehicle parameter214may include a vehicle identification information, which may correspond, for example, to a vehicle identification number (VIN), vehicle description, or license plate number.

The behavior profile208may be compiled over time as the user interacts with the movable barrier operator system200. For example, the behavior profile208of a user may be updated with user interaction data including a user parameter210, a schedule parameter212, and a vehicle parameter214each time the vehicle80driven by the user enters the geofenced area218and the in-vehicle device82automatically causes the movable barrier operator202A to operate. Similarly, the behavior profile208may be updated with user interaction data including a user parameter210, a schedule parameter212, and a vehicle parameter214each time the vehicle80enters the geofenced area218, the in-vehicle device82prompts the user to select which movable barrier operator202to operate, and the user provides a user input to the in-vehicle device82. Additionally or alternatively, the behavior profile208may be configured and/or updated to reflect one or more of user behavior trends and/or probabilities, machine learning, and at least one of positive training examples and negative training examples.

Referring toFIG.9, an illustration of parameters used in an example selection process250for selecting a movable barrier operator from a plurality of barrier operators based at least in part on the behavior profile208is provided. One or more operations of the selection process250may be performed, for example, at the in-vehicle device82, the user device86, the remote server computer92, the computing device94, and/or one or more of the movable barrier operators202. For example, the in-vehicle device82and/or the remote server computer92may employ a respective instance of the behavior profile208that are continuously or periodically synced to contain similar data. In the example ofFIG.9, the remote server computer92may perform the selection process250using data from the in-vehicle device82and one of the movable barrier operators202.

The selection process250may consider historical user interaction data, including user parameters210, schedule parameters212, and vehicle parameters214. In this example, the user parameters210include data associated with four users including Dad, Mom, Daughter, Son, although any suitable number of users may be included. A user may be identified, for example, by a user-input (e.g., user selection or username input) provided to the in-vehicle device82or may be detected by a sensor (e.g., sensor100ofFIG.4).

The schedule parameters212may include temporal data associated with the different users' interactions with the system200. The schedule parameters212may include, for example, the date and time each user caused operation of one of the movable barrier operators202. The schedule parameter212may be, for example, the time of day as shown inFIG.9.

The vehicle parameters214may include information identifying the vehicles the users are driving when the users interact with the system200. For example, the vehicle parameter214may include a transmitter ID of a radio frequency control command transmitted from an in-vehicle device82of a vehicle. The server computer92may determine which vehicle operated a particular movable barrier operator202at a particular time of day based on the transmitter ID of a radio frequency control command received by the movable barrier operators202. In this example, the vehicle parameters214include identifiers for three vehicles, car, truck, and van, although any suitable number of vehicles may be included.

With reference toFIGS.8and9, the system200is configured to trigger a door open event when a vehicle80enters the geofenced area218. In one example, the server computer92receives location information of a vehicle80indicating the vehicle80has entered the geofenced area218. The server computer92determines the Daughter is driving the vehicle based on the presence of the Daughter's smartphone in the vehicle. The identity of the Daughter's smartphone is utilized as a user parameter210. The server computer determines the time of day when the vehicle80entered the geofenced area. The time of day is utilized as a schedule parameter212. The server computer92determines the identity of the vehicle the Daughter is driving by way of a transmitter ID that one of the movable barrier operators202detects from a radio frequency control command sent from the in-vehicle device82upon the vehicle80entering the geofenced area218. The transmitter ID is utilized as a vehicle parameter214.

The selection process250includes predicting which movable barrier operator202the Daughter wants to have actuated based at least on the behavior profile208. In the example ofFIG.9, the server computer92selects movable barrier operator202A to open in response to the radio frequency control command sent by the in-vehicle device82. The server computer92selects movable barrier operator202A because the Daughter has historically operated the movable barrier operator202A eighty percent of the time when these user, schedule, and vehicle parameters210,212,214are present. That is, the selection process250determines that there is a high probability, likelihood, or confidence level that identified schedule, user, and vehicle parameters correspond to a user/driver desire to open a particular barrier. Additional fact-based data (such as in-vehicle sensing with a camera to identify the user) may also be considered in assessing a probability that a predicted action is the user-desired action.

The user may desire a different movable barrier operator202to operate than the movable barrier operator202selected by the server computer92. In this situation, the user may operate the desired movable barrier operator202upon reaching the garage204. The behavior profile208will update to reflect this alternative selection by the user. Over time, if the Daughter starts using movable barrier operator202B more frequently than the movable barrier operator202A in these situations (e.g., due to Daughter occasionally or persistently driving a different one of the vehicles), the behavior profile208will change to indicate that the selection process250should select movable barrier operator202B when these user, schedule, and vehicle parameters210,212,214are present.

In another example ofFIG.9, the server computer92determines Dad is arriving at a particular time driving a van. The server computer92selects movable barrier operator202B and causes movable barrier operator202B to open the garage door206B because, historically, Dad has operated movable barrier operator202B fifty-five percent of the time in similar situations.

As such, the movable barrier operator system200may automatically predict a user-desired movable barrier operator from among a plurality of movable barrier operators202. The prediction may be based on various variables (e.g., user parameters210, schedule parameters212, and vehicle parameters214) described herein including but not limited to current/sensed data, historical data, and/or trends. The selection process250may be based on or more of the user parameters210, schedule parameters212, and vehicle parameters214. In some approaches, only one or two types of parameters210,212,214may be used. In other approaches, the prediction or selection may be based on additional or alternative parameters, such as weather parameters.

In response to predicting the user-desired movable barrier operator from among a plurality of movable barrier operators, a method of operating the system200in one approach may include prompting the user for a confirmation that the predicted user-desired movable barrier operator is the actual user-desired movable barrier operator. In another approach, the method may include automatically actuating the predicted user-desired movable barrier operator without providing a prompt to the user. In either approach, the method may include providing a confirmation notification to the user of a movable barrier operation.

The movable barrier operator system200may include one or more cameras. One or more of the cameras may generally correspond to camera module70ofFIG.1. In one aspect, the movable barrier operator system200includes cameras220A,220B,220C, collectively referred to as cameras220, with each camera220A,220B,220C having a respective field of view222A,222B, and222C that covers at least a portion of the garage204. Each field of view222A,222B,222C may encompass at least a portion of a respective area224A,224B,224C within the garage204. The areas224A,224B,224C may be, for example, parking spaces within the garage204. Each field of view222A,222B,222C may also extend outside of the garage204when the respective movable barrier206A,206B,206C is open. In another aspect, the movable barrier operator system200may include fewer cameras than movable barrier operators; for example, one camera for observing areas associated with multiple movable barriers. The movable barrier operator system200may also include one or more cameras disposed on and/or within a vehicle to capture imagery outside of and/or within the vehicle.

In certain instances, the movable barrier operator system200may be configured to automatically operate a particular movable barrier operator202that is not the movable barrier operator predicted by the movable barrier operator system200according to the behavior profile208. Such a “next-best” operation may occur, for example, when a camera determines an object is in or blocking an area associated with the selected movable barrier operator. For example, the camera220A may detect that another vehicle230is already parked in the area224A associated with the movable barrier operator202A which the remote server computer92predicts the user will want to operate. As another example, the remote server computer92may predict the user will want to operate movable barrier operator202C but the camera220C detects an object232, such as a package or bicycle, blocking the area224C. In response to the unexpected object232, the remote server computer92decides to cause movable barrier operator202B to open the movable barrier206B. The remote server computer92may cause the in-vehicle device82to provide a notification to the user that the user should park in the area224B rather than area224C due to the object232. Alternatively, the in-vehicle device82may cooperate with one or more vehicle systems or components to facilitate autonomous or semi-autonomous parking of the vehicle in the vacant/available area224B once the movable barrier206B is opened by associated movable barrier operator202B.

In this regard, a method of operating a movable barrier operator system200may include, responsive to receiving a barrier operator state change request, determining a first movable barrier operator associated with one or more parameters of a behavior profile208. The first movable barrier operator may be determined from among a plurality of movable barrier operators. The method may further include observing, via at least one camera, a first garage area associated with the first movable barrier operator. The method may further include, responsive to determining an obstruction located within the first garage area, determining a second movable barrier operator. In one approach, the second movable barrier operator may be associated with one or more parameters of the behavior profile208. Alternatively, the second movable barrier operator may be located adjacent (e.g., “next closest”) to the first movable barrier operator. In an optional approach, the method may further include observing, via at least one camera, a second garage area associated with the second movable barrier operator. The camera may be the same camera as, or different camera than, the camera that observed the first garage area. In response to determining an obstruction located within the second garage area, the method may proceed to evaluate a third location associated with a third movable barrier operator, and so on until a suitable location is determined.

If the movable barrier operator system200determines that no obstruction is located within the second garage area (or other subsequently-observed garage location), the method may include operating the second movable barrier operator to move the associated movable barrier. In an optional approach, the method may include transmitting a notification to the user regarding which movable barrier operator has been actuated. The method may still further include an indication of why that movable barrier operator was actuated. For example, the method may include transmitting an image captured by a camera indicating a vehicle or object obstructing the location of the first movable barrier operator.

In addition to the cameras220, or as an alternative to the cameras220, the movable barrier operator system200may communicate with one or more peripheral devices to determine whether any obstructions are located within a garage area associated with a predicted movable barrier operator. The one or more peripheral devices may include optical systems (optical emitter50and/or optical detector54ofFIG.1), loop detectors, motion sensors, and alarm systems to name but a few examples.

Upon determining that a geolocation condition has been satisfied (e.g., vehicle80has entered the geofenced area218) and that door open event is appropriate (e.g., no obstructions detected in an area224associated with a movable barrier operator202), the movable barrier operator system200triggers a door open event. In one aspect, the system200monitors various attributes associated with the triggered door open event. For example, the system200may monitor attributes pertaining to the vehicle80and/or movable barrier operator(s)202associated with the trigger event. Vehicle attributes may include one or more of a vehicle speed, vehicle location, vehicle heading, and steering wheel position. Movable barrier operator attributes may include a door position (e.g., open or closed), a door operating state (e.g., opening or closing), and/or a state of one or more peripheral devices (e.g., optical emitter50and/or optical detector54ofFIG.1).

In one approach, upon triggering the door open event, the system200monitors for an auto-close event. As used herein, an auto-close event refers to automatic operation of a movable barrier operator202to close a movable barrier206in the absence of a close command from a user. An auto-close event may occur, for example, when the system200detects vehicle behavior that is not associated with a vehicle parking in a garage. For example, if the system200opens a movable barrier206upon a vehicle entering the geofenced area218and subsequently detects a vehicle speed exceeding a threshold vehicle speed for a given location (e.g., a predetermined proximity to a garage204), the system200triggers an auto-close event to thereby close the movable barrier206previously opened by the system200.

Additionally or alternatively, an auto-close event may occur when the system200does not detect vehicle behavior that is associated with a vehicle parking in a garage. For example, the system200may monitor one or more peripheral devices to confirm a vehicle80has entered the garage204. The peripheral devices may include optical systems (e.g., the camera of camera module70, optical emitter50and/or optical detector54ofFIG.1), loop detectors, and motion sensors to name but a few examples. The system200may monitor the one or more peripheral devices for a predetermined time period relative to the initiation of the door open event. For example, the system200may monitor a peripheral device for two minutes, five minutes, or ten or more minutes after initiating the door open event. If the peripheral device does not detect a vehicle (e.g., the photo beam between the optical emitter50and the optical detector54is not interrupted) within the predetermined period of time, the system200triggers an auto-close event to thereby close the movable barrier206previously opened in response to the door open event.

In one approach, the monitored vehicle behavior may be compared to a parking routine profile216associated with a user profile. The parking routine profile216associated with a user profile may be compiled over time, and may be saved within one or more memory devices of the system200(e.g., memory120of the in-vehicle device82, memory152of the remote server computer92, and/or memory162of the movable barrier operator12). The vehicle behavior may be monitored, for example, using the camera module70.

Different users may have different parking routine profiles216based on respective driving routines. A driving routine may include vehicle driving attributes (e.g., vehicle location, vehicle speed, vehicle acceleration and/or deceleration, vehicle heading), days of the week and/or times associated with one or more of the vehicle attributes, and/or system conditions associated with a garage.

In one example, the system200compiles a parking routine profile216for Dad that is based on Dad's driving routine. For example, Dad's parking routine profile216may indicate that the vehicle80operated by Dad typically enters the geofenced area218while traveling at approximately 45 miles per hour (MPH) The vehicle80subsequently slows to approximately 15 MPH and makes a right-hand turn, and further slows to approximately 5 MPH and makes a left-hand turn to arrive home between 4:10 PM and 6:20 PM on weekdays. The parking routine profile216may further indicate that upon door opening, Dad's vehicle interrupts the photo beam between the optical emitter50and the optical detector54.

The system200may be configured to initiate an auto-close event in response to the monitored parking routine deviating from a user's parking routine profile216. The deviation that triggers an auto-close event may include, for example, a change in a vehicle parameter during an operation outside of a tolerance for the operation, such as a vehicle speed more than five MPH above an expected speed. Another example of a deviation that triggers an auto-close event may include an omission of an expected operation, such as the vehicle not turning at an intersection where the system200expects the vehicle to turn. The system200may also monitor the time of day and day of the week to compare against the user's parking routine profile216. A deviation from the user's parking routine profile216may include the vehicle initiating a door open event outside of the day(s) of the week and/or times of day expected by the user's parking routine profile216. Based on one or more deviations from the user's parking routine profile216, the system200may assume the user does not intend to park the vehicle in the garage.

For example, upon the system200(e.g., at the server computer92) determining Dad is driving the vehicle80(e.g., based on the presence of Dad's smartphone in the vehicle80) that has entered the geofenced area218, the system200operates a movable barrier operator to open a predicted movable barrier. The system200then monitors for behavior associated with Dad's parking routine profile216to determine if Dad is parking (or will be parking) in the predicted garage. Using the previous example of Dad's parking routine profile216, if upon slowing to approximately 5 MPH, Dad's vehicle80does not subsequently make a left-hand turn, the system200may initiate an auto-close event. Or, if Dad did make the left-hand turn, but did not interrupt the photo beam between the optical emitter50and the optical detector54(e.g., within a predetermined time period), the system200may initiate an auto-close event.

In this way, the system200determines the vehicle80has not parked, or is not going to park, in the garage204associated with a predicted movable barrier206. As such, the system200closes the movable barrier206to limit access to the garage204.

Referring toFIG.10, a method300is provided for operating a movable barrier operator that may be utilized with the system200discussed above. In one approach, the method may include an optional operation of communicating301a control command. The control command may be communicated, for example, from a transportable device (e.g., the transmitter30or the in-vehicle device82). As discussed elsewhere herein, the communication of the control command may be user-initiated, or may be automatically or semi-automatically initiated by the in-vehicle device82, for example, based on a location of the vehicle80.

The control command may direct the movable barrier operator to toggle or change a state of the movable barrier (e.g., from “open” to “closed” or vice versa). The control command may instead be a state-specific command (e.g., “open” or “close”). In the latter approach, the method may include determining a position of the movable barrier. If, for example, movable barrier operator receives an “open” command while the movable barrier is in the open position, the method may end. Similarly, if movable barrier operator receives a “close” command while the movable barrier is in the closed position, the method may end.

The method300may include determining302satisfaction of a predetermined relative proximity of the transportable device relative to a secured area. For example, the determining302may include determining whether the in-vehicle device82is within a set distance of the garage204or geofenced area.

If, at step302, the relative proximity determination is not satisfied, the method300may further include determining304a condition (e.g., an open or closed position) of a target barrier. As used herein, a target barrier may refer to a user-selected barrier, or may refer to a predicted barrier (e.g., as predicted by movable barrier operator system200).

If, at step304, the target barrier is in a closed position, the method may include transmitting306(e.g., via the in-vehicle device82) a control command to open the movable barrier. If, at step304, the target barrier is in an open position, the method may include transmitting308(e.g., via the in-vehicle device82) a command to close the movable barrier. Because the vehicle is not within a set distance of the garage204, one or both of the open and the close commands of steps306and308may be transmitted, for example, via a wide area transmission (e.g., wide area network interface114configured to communicate with the remote server computer92via the network90).

If, at step302, the relative proximity determination is satisfied, the method may further include determining310a condition (e.g., an open or closed position) of the target barrier. If, at step310, the target barrier is in a closed position, the method may include transmitting312(e.g., via the in-vehicle device82) a control command to open the movable barrier. If, at step310, the target barrier is in an open position, the method may include transmitting314(e.g., via the in-vehicle device82) a command to close the movable barrier. One or both of the open and the close commands of steps312and314may be transmitted, for example, via a RF transmission (e.g., via radio frequency signal transmitter112), or via other short-range transmissions (e.g., via short-range wireless transceiver116).

As discussed, the control command may be a state-change command that directs the movable barrier operator to change a state of the movable barrier (e.g., from “open” to “closed” or vice versa). In one aspect, the method may include determining a heading of the vehicle to predict a desired movable barrier position. In this way, when the vehicle80is traveling in a direction of the movable barrier and the movable barrier is already in an open position, the movable barrier operator may not operate the movable barrier upon receiving a state-change command.

In one approach, the method300may further include, after transmitting312the control command to open or close the target movable barrier, determining320a door moving state. The determination may be made, for example, after a predetermined period of time. The predetermined period of time may be, for example, approximately, one second, two seconds, or three or more seconds. In response to determining the door moving state is not moving, the method300may further include, transmitting322a repeat open command to the movable barrier. The repeat open command may be transmitted, for example, via a wide area transmission (e.g., wide area network interface114configured to communicate with the remote server computer92via the network90).

In one approach, the method300may further include, after transmitting314the command to close the movable barrier, determining330a door moving state. The determination may be made, for example, after a predetermined period of time. The predetermined period of time may be, for example, approximately, one second, two seconds, or three or more seconds. In response to determining the door moving state is not moving, the method may further include, transmitting332a repeat close command to the movable barrier. The repeat close command may be transmitted, for example, via a wide area transmission (e.g., wide area network interface114configured to communicate with the remote server computer92via the network90).

In one approach, an auto-close method may be performed by the in-vehicle device82described with respect toFIG.3. The sensor100of the in-vehicle device82may be configured to detect a vehicle characteristic indicative of the vehicle80being in proximity to an area associated with the movable barrier operator, such as entering a geofenced area near the garage204. Vehicle characteristics may include at least one of the location of the vehicle80, a distance between the vehicle80and a location (such as a garage) associated with the movable barrier operator202, the speed of the vehicle80, the heading of the vehicle80, and a programmed vehicle destination of the vehicle80.

Communication circuitry110of the in-vehicle device82may be configured to communicate directly or indirectly with a movable barrier operator202. For example, the communication circuitry110may communicate an open command to a movable barrier operator202that causes the movable barrier operator202to open a movable barrier206connected to the movable barrier operator202. The communication circuitry110may also be configured to receive data indicative of a position of the movable barrier206from a server computer, such as the server computer92ofFIGS.2and6.

The processor122is operatively coupled to the sensor100, communication circuitry110, and a memory120of the in-vehicle device82. The memory120of the in-vehicle device82is configured to store one or more vehicle arrival conditions that are indicative of whether the vehicle80arrived at the location associated with the movable barrier operator202. The processor122of the in-vehicle device82, the processor154of the server computer92, and/or the processor circuitry72of the movable barrier operator may be configured to determine satisfaction of the one or more vehicle arrival conditions. The vehicle arrival conditions may include, for example, whether the vehicle80arrived at the location associated with the movable barrier operator202, whether the vehicle movement corresponds to the vehicle parking routine, whether the vehicle destination corresponds to the location associated with the movable barrier operator202, whether a distance of the vehicle80from the location associated with the movable barrier operator202corresponds to an expected distance, whether a speed of the vehicle80corresponds to an expected speed, and/or whether a heading of the vehicle80corresponds to an expected heading.

Upon the vehicle arrival condition not being satisfied, the processor122is configured to cause the communication circuitry110to communicate a close command to the movable barrier operator202that causes the movable barrier operator202to close the movable barrier206. The vehicle arrival condition not being satisfied may indicate that the user has decided to drive past her home and does not desire to enter the garage14. For example, communication circuitry110may communicate the close command directly to the movable barrier operator using a radio frequency signal. In another embodiment, the processor122causes the communication circuitry110to communicate the close command indirectly to the movable barrier operator via the network90and the server computer92. In still another embodiment, the processor154of the server computer92determines whether the vehicle arrival condition is satisfied and, if not, communicates a close command to the movable barrier operator.

In one approach, the memory120of the in-vehicle device82is further configured to store a time period within which a vehicle arrival condition is expected to occur. The processor122may cause the communication circuitry110to communicate the close command upon the vehicle arrival condition not being satisfied within the time period. The time period may be, for example, measured from the time the communication circuitry110communicates the close command to the movable barrier operator. As an example, the time period may be two, three, or four minutes. The time period may be fixed or variable. In one embodiment, the time period varies depending on the speed of the vehicle so that the time period is shorter when the vehicle is traveling at a higher speed toward the garage, and the time period is longer when the vehicle is traveling at a slower speed toward the garage.

The sensor100may include a global navigation satellite system receiver, and the processor122may to determine location information of the vehicle80based on information from the sensor100. For example, the processor122may receive data from the sensor100regarding movement of the vehicle80upon the vehicle80being in proximity to the location associated with the movable barrier operator202.

Although method steps may be presented and described herein in a sequential fashion, one or more of the steps shown and described may be omitted, repeated, performed concurrently, and/or performed in a different order than the order shown in the figures and/or described herein. It will be appreciated that computer-readable instructions for facilitating the methods described above may be stored in various non-transitory computer readable mediums as is known in the art.

Uses of singular terms such as “a,” “an,” are intended to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “including,” and “containing” are to be construed as open-ended terms. It is intended that the phrase “at least one of” as used herein be interpreted in the disjunctive sense. For example, the phrase “at least one of A and B” is intended to encompass A, B, or both A and B.

While there have been illustrated and described particular embodiments of the present invention, it will be appreciated that numerous changes and modifications will occur to those skilled in the art, and it is intended for the present invention to cover all those changes and modifications which fall within the scope of the appended claims.