Vehicle controller delivery mode

A vehicle may detect vehicle actions, compare the vehicle actions to first vehicle actions associated with first mode settings of a vehicle controller and to second vehicle actions associated with second mode settings of a vehicle controller, and transition the mode settings of the vehicle controller to the first mode settings responsive to the vehicle actions matching the first vehicle actions. The controller may be a vehicle body controller, and the mode settings may describe a locking behavior of the body controller. A mobile device may set vehicle actions configured to cause the controller to transition from the first mode settings to the second mode settings. The mobile device may also display an alert responsive to the controller detecting presence of an unauthorized user within vicinity of the vehicle.

TECHNICAL FIELD

Aspects of the disclosure generally relate to vehicles having multiple mode settings to configure operation of a vehicle controller, such as settings for a delivery mode and settings for a non-delivery mode.

BACKGROUND

Cargo vans may be used by package, flower, or other delivery services due to their carrying capacity and ease of loading and unloading. However, cargo vans may suffer from theft issues when the driver is delivering mail or other parcels, or when the driver is at an office and the van is unattended. As another possibility, the vehicle itself may be stolen while the user is making a delivery. Many of these thefts go unpunished and, in many cases, may not be covered by insurance. In many cases, the driver has no proof that a theft has been committed.

SUMMARY

In a first illustrative embodiment, a system includes a controller of a vehicle; first mode settings defining lock operation of the controller when the vehicle is performing delivery; and second mode settings defining lock operation of the controller otherwise, wherein the controller is configured to switch to the first mode settings from the second mode settings responsive to vehicle actions received by the controller indicative of the vehicle being operated to perform delivery.

In a second illustrative embodiment, a computer-implemented method includes detecting vehicle actions including operator proximity and vehicle door lock status; comparing the vehicle actions, as detected, to first vehicle actions associated with first mode settings of a vehicle body controller and to second vehicle actions associated with second mode settings of a vehicle body controller; and transitioning the mode settings of the vehicle body controller to the first mode settings responsive to the vehicle actions matching the first vehicle actions.

In a third illustrative embodiment, a system includes a mobile device configured to set vehicle actions to cause a controller of a vehicle to transition from first mode settings describing a first locking behavior of the controller to second mode settings of the controller describing a second locking behavior of the controller; and display an alert user interface responsive to the controller detecting presence of an unauthorized user within vicinity of the vehicle.

DETAILED DESCRIPTION

A system may be configured to provide a driver or other operator with knowledge of vehicle surroundings when the driver is away from the vehicle for a delivery. The system may also record video surroundings of the vehicle if an unauthorized entry is attempted, and communicate to the driver/operator that an unauthorized entry is being attempted. The system may also communicate with a remote server to enable evidence gathering or a central team to call for help if the vehicle user is unable to do so. The system may be further configured to automatically activate and deactivate the delivery mode based on detected actions performed in relation to the vehicle. Further aspects of the system are described in detail with respect to the Figures below.

FIG. 1illustrates an example passive entry system100for a vehicle102including delivery mode settings166-A and normal mode settings166-B. The vehicle102may be one of various types of passenger vehicles, such as a full size van (e.g., a delivery van), crossover utility vehicle (CUV), a sport utility vehicle (SUV), a truck, a recreational vehicle (RV), or other mobile machine for transporting people or goods. The passive entry system100may support identification of authorized users through various techniques, such as key fob108proximity, keypad122code entry, mobile device134proximity, and media content captured by vehicle capture devices158. The passive entry system100may be further configured to identify a vehicle actions168performed by the vehicle102responsive to user input. Based on the identification of the vehicle actions168, the system100may determine which mode settings166to apply to the controller104to control vehicle access. In an example, based on the vehicle actions168, the controller104may determine whether to use the delivery mode settings166-A or the normal mode settings166-B to specify operation of the passive entry system100. It should be noted that the illustrated system100is merely an example, and more, fewer, and/or differently located elements may be used.

The body controller104may be configured to manage various power control functions, such as exterior lighting, interior lighting, and point of access status verification. The point of access status verification may include, as some possibilities, identification of open or closed status of the hood, doors and/or trunk of the vehicle102. In an example, the body controller104may include or be connected to a radio frequency (RF) transceiver106. A key fob108may be in communication with the RF transceiver106of the controller104utilizing a fob transceiver110powered by a battery112. An antenna114of the RF transceiver106may receive RF signals from an antenna116of the fob transceiver110, and may deliver the signals to the RF transceiver106. An unlock/lock mechanism118may be operably coupled to the controller104. The controller104may be configured to control the unlock/lock mechanism118to unlock/lock doors of the vehicle102in response to the RF signals transmitted by the key fob108. The key fob108may include one or more fob controls120, such as a lock switch and an unlock switch. Accordingly, the controller104controls the unlock/lock mechanism118to lock the doors of the vehicle102in response to a user depressing a lock fob control120of the key fob108, and to unlock the doors of the vehicle102in response to the user depressing an unlock fob control120of the key fob108.

The key fob108of the passive entry system100may be implemented in connection with a base remote entry system, a passive entry passive start (PEPS) system or a passive anti-theft system (PATS). With the PEPS system, the controller104may control the unlock/lock mechanism118to unlock the door in response to the controller104determining that the key fob108is a predetermined distance away from the vehicle102. In such a case, the key fob108automatically (or passively) transmits encrypted RF signals (e.g., without user intervention) in order for the controller104to decrypt (or decode) the RF signals and to determine if the key fob108is within the predetermined distance and are authorized. It is to be noted that with the PEPS implementation, the key fob108also generate RF signals which correspond to encoded lock/unlock signals in response to a user depressing a lock fob control120or an unlock fob control120. In addition, with the PEPS system, a key may not be needed to start the vehicle102. The user in this case may be required to depress the brake pedal switch or perform some predetermined operation prior to depressing a start switch after the user has entered into the vehicle102. In the PATS implementation, the key fob108may operate as a conventional key fob in order to unlock/lock the vehicle102. With the PATS implementation, a keys (not shown) is generally needed to start the vehicle102. The key may include a RF transmitter embedded therein to authenticate the key to the vehicle102.

The system100may also include a keypad122in communication with the controller104. The keypad122may be positioned on an exterior portion or section of the vehicle102. In one example, the keypad122may be hardwired to the controller104. In another example, the keypad122may be in RF communication with the controller104(e.g., via the RF antenna114). The keypad122may include a plurality of mechanical pads, capacitive pads or other switches124a-124nwhich correspond to numeric characters, alpha characters or any combination of alpha-numeric characters. In an example, the keypad122may transmit commands via hardwired signals to the controller104which correspond to a sequence of numeric characters, alpha characters, or alpha-numeric characters in response to the user selecting various switches124a-124n. In another example, the keypad122may transmit commands via RF signals which correspond to the alpha, numeric, or alpha-numeric characters to the controller104in response to the user selecting various switches124a-124n. Responsive to receiving the commands, e.g., two or more signals (RF or hardwired) which correspond to a valid sequence of alpha, numeric, or alpha-numeric characters, the controller104may control the unlock/lock mechanism118to unlock/lock one or more vehicle102doors.

The controller104may further include an ignition switch authentication device128. The ignition switch authentication device128may also include an RF receiver (not shown) and an antenna (not shown) for receiving RF signals transmitted by the RF transmitters of the keys. It should be noted that the ignition switch authentication device128may be implemented as a standalone controller (or module). The ignition switch authentication device128may be configured to authenticate the particular type of mechanism used to start the vehicle102. For example, with the PATS implementation, the key may be inserted into an ignition switch130to start the vehicle102. In such a case, the RF transmitter of the key transmits RF signals having encrypted data therein to the receiver of the ignition switch authentication device128. The ignition switch authentication device128may accordingly decrypt the data to authenticate the key prior to allowing the user to start the vehicle102.

With the PEPS implementation, as noted above, a key may not be required to start the vehicle102. In such a case, the ignition switch authentication device128may authenticate the RF encrypted data passively transmitted by the transmitter to allow the user to start the engine of the vehicle102. As noted above, in addition to the authentication device128authenticating the RF encrypted data, the user may perform a predetermined operation (e.g., pull handle of a door, or open door, toggle the brake pedal switch, or other operation) prior to depressing a start switch to start the vehicle102. The system100contemplates a number of other operations from those listed prior to depressing the start switch to start the vehicle102.

The controller104may be in communication with a wireless controller132configured to communicate with mobile devices134. The mobile devices134may be any of various types of portable computing device, such as cellular phones, tablet computers, smart watches, laptop computers, portable music players, or other devices capable of communication with the wireless controller132. In many examples, the wireless controller132may include a wireless transceiver136(e.g., a BLUETOOTH module, a ZIGBEE transceiver, a Wi-Fi transceiver, an IrDA transceiver, an RFID transceiver, etc.) having an antenna138and configured to communicate with a compatible wireless transceiver140and antenna142of the mobile device134.

The communications network144may provide communications services, such as packet-switched network services (e.g., Internet access, VoIP communication services), to devices connected to the communications network144. An example of a communications network144may include a cellular telephone network. Mobile devices134may provide network connectivity to the communications network144via a device modem146of the mobile device134. To facilitate the communications over the communications network144, mobile devices134may be associated with unique device identifiers (e.g., mobile device numbers (MDNs), Internet protocol (IP) addresses, etc.) to identify the communications of the mobile devices134over the communications network144.

Occupants of the vehicle102or users outside the vehicle102may be identified by the wireless controller132according to paired device data148maintained in a storage medium of the wireless controller132. The paired device data148may indicate, for example, the unique device identifiers of mobile devices134previously paired with the wireless controller132of the vehicle102, such that the wireless controller132may automatically reconnected to the mobile devices134referenced in the paired device data148without user intervention.

When a mobile device134that supports network connectivity is paired with the wireless controller132, the mobile device134may allow the wireless controller132to use the network connectivity of the device modem146to communicate over the communications network144with a remote server174or other remote computing devices. In one example, the wireless controller132may utilize a data-over-voice plan or data plan of the mobile device134to communicate information between the wireless controller132and the communications network144. Additionally or alternately, the wireless controller132may utilize a vehicle modem (not shown) to communicate information between the wireless controller132and the communications network144, without use of the communications facilities of the mobile device134.

The mobile device134may include one or more processors150configured to execute instructions of mobile applications loaded to a memory152of the mobile device134from storage medium154of the mobile device134. In some examples, the mobile applications may be configured to communicate with the wireless controller132via the wireless transceiver136and/or with the remote server174or other network services via the device modem146.

The controller104and/or the wireless controller132may further be on communication with a media content controller156. The media content controller156may be configured to send requests to capture devices158of the vehicle102to capture media content such as images, audio, and/or video, and to receive the requested media content from the capture devices158in response. The capture devices158may include any of various types of devices configured to capture media content. In an example, the capture devices158may include a 360 degree view camera or a set of cameras configured to provide a panoramic view of the vehicle102surroundings. Other types of capture devices158may include microphones to capture audio content, such as a microphone in the vehicle cabin used to receive voice commands from users or one or more other microphones external to the vehicle102cabin. In some cases, a capture device158may be configured to capture a single type of media content (e.g., video, audio, still images, etc.), while in other cases the capture device158may be able to capture multiple types of media content instance (e.g., both audio and video). The vehicle102may include one or more capture devices158. The media content controller156may be further configured to include metadata information in the captured media content, and store and transfer the captured media content for use by the vehicle102systems.

The controller104may also include various types of computing apparatus to facilitate the performance of the functions of the controller104. In an example, the controller104may include a processor160configured to execute computer instructions loaded to a memory162of the controller104, and a storage medium164on which the computer-executable instructions may be maintained. A computer-readable storage medium164(also referred to as a processor-readable medium164or storage164) includes any non-transitory (e.g., tangible) medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by the processor160). In general, a processor160receives instructions, e.g., from the storage164, etc., and executes these instructions, thereby performing one or more processes, including one or more of the processes described herein. Computer-executable instructions may be compiled or interpreted from computer programs created using a variety of programming languages and/or technologies, including, without limitation, and either alone or in combination, Java, C, C++, C#, Fortran, Pascal, Visual Basic, Java Script, Perl, PL/SQL, etc.

The mode settings166may be stored to the storage medium164of the controller104, and may be used by the controller104to control the locking and unlocking functionality of the vehicle102. In an example, the controller104may include delivery mode settings166-A configured to control locking, unlocking, and media capture behavior of the vehicle102when vehicle actions168are indicative of delivery of persons, packages or other items, and normal mode settings166-B configured to control locking, unlocking, and media capture behavior of the vehicle102when the sequence of operations being performed by the driver is not indicative of delivery.

The vehicle actions168may include a machine-readable representation of one or more operations performed by or to the vehicle102, optionally specified in a predetermined order, that when identified by the controller104cause the controller104to select an associated set of mode settings166to be used by the controller104. In an example, the vehicle actions168may include one or more operations indicative of the driver initiating delivery of packages (e.g., messages indicative of an operator stopping the vehicle102, opening a driver door, closing the driver door, opening a cargo door, closing the cargo door, etc.). In another example, the vehicle actions168may include one or more operations indicative of the driver discontinuing delivery of packages (e.g., vehicle102detection of the operator completing or discontinuing travel along a delivery route programmed to a navigation unit of the vehicle102). In yet further examples, the vehicle actions168may be indicative of other modes for which mode settings166should be adjusted for use by the controller104. As a non-delivery example, the vehicle actions168may be indicative of the driver stopping at a school to pick up children at a predetermined pickup time.

The mode control application170may be an application installed to the storage medium164of the body controller104. (In other examples, the mode control application170application or functionality may be implemented in whole or in part by other modules of the vehicle102, such as by a separate mode control module, by the engine control module, as an application installed to a telematics control unit, etc.) When executed by the processor160, the mode control application170may be configured to cause the controller104to monitor vehicle bus activity and/or other inputs to the vehicle102to detect the vehicle actions168. When detected, the mode control application170may be configured to apply mode settings166to the controller104that are associated with the identified vehicle actions168. For instance, the mode control application170may identify that the vehicle102has stopped for delivery and may transition the controller104to utilize the delivery mode settings166-A. Or, the mode control application170may identify that the vehicle102has completed a delivery route and may transition the controller104to utilize the normal mode settings166-B.

The notification application172may be an example of a mobile application installed to the mobile device134and configured to interact with the vehicle102via the wireless controller132. The notification application172may be configured to facilitate configuration of the settings of the controller104, aid in the identification by the mode control application170of the location of the operator, and receive alerts generated by the vehicle102regarding unexpected events occurring at the vehicle102.

FIG. 2illustrates a diagram200of an example user interface202-A for selecting a set of vehicle action168criteria for configuration. As illustrated, the user interface202-A may be presented to the user by the notification application172via a display of the mobile device134. As another possibility, the user interface202-A may be provided to the user via a display of the vehicle102(not shown). The user interface202-A may be displayed upon various conditions, such as when the mobile device134is connected to the vehicle102for the first time, when the mobile device134is connected to the vehicle102and the vehicle102has not yet set up vehicle actions168, or upon user selection of a function to update the vehicle actions168configured for transitioning the mode settings166of the controller104of the vehicle102.

The user interface202-A may include a list control204configured to display a listing of the sets of vehicle action168criteria that may be configured by the user. As shown, each of the sets of vehicle action168is displayed as one of several selectable list entries206. The user interface202-A may also include a title label208to indicate to the user that the user interface202-A is for selection of vehicle action168criteria.

As illustrated, the list control204of the notification application172includes an entry206-A for normal mode vehicle actions168, an entry206-B for delivery mode vehicle actions168, and an entry206-C for school mode vehicle actions168. It should be noted that the exact commands, number of commands, and command order is merely an example. The list control204may operate as a menu, such that a user of the user interface202-A may be able to scroll through list entries of the list control204to adjust a currently selected list entry210(e.g., using up and down arrow buttons) as well as to invoke the currently selected list entry210(e.g., using a select button). In some cases, the list control204may be displayed on a touch screen display, such that the user may be able to touch the list control204to select and invoke a menu item. As another example, the user interface206-A may support voice command selection of the menu items. For example, to invoke configuration of the delivery mode vehicle actions168, the user may press a push-to-talk button or say a voice command initiation keyword, and may speak the voice command “delivery mode action criteria.”

FIG. 3illustrates a diagram300of an example user interface202-B for adjustment of criteria for a selected set of vehicle actions168. As with the user interface202-A, the user interface202-B may be presented to the user via display features of mobile device134(or vehicle102). The user interface202-B may be displayed, for example, based upon a user selection of the delivery mode vehicle actions168entry206-B of the user interface202-A. The user interface202-B may also include a title label208to indicate to the user that the user interface202-B is for adjustment of the selected set of vehicle action168criteria.

As illustrated, the list control204of the notification application172includes entries for the configuration of specific aspects of the vehicle actions168, that when detected, cause the mode control application170to transition the controller104to use of mode settings166corresponding to the vehicle actions168. These options may include, for example, an entry206-A for configuring engine idle time, an entry206-B for configuring vehicle routing, an entry206-C for configuring key fob108proximity detection, an entry206-D for configuring mobile device134proximity detection, and an entry206-E for configuring the delivery mode settings166-B.

FIG. 4illustrates a diagram400of an example user interface202-C for configuring vehicle102operation for a set of vehicle mode settings166. As with the user interfaces202-A and202-B, the user interface202-C may be presented to the user via display features of mobile device134(or vehicle102). The user interface202-C may be displayed, for example, based upon a user selection from the user interface202-B of the entry206-E for configuring the delivery mode settings166-B. The user interface202-C may also include a title label208to indicate to the user that the user interface202-C is for adjustment of the selected set of vehicle action168criteria.

As illustrated, the list control204of the notification application172includes entries for the configuration of specific aspects of the mode settings166that may be applied to the controller104. These options may include, for example, an entry206-A for configuring automatic locking and unlocking behavior of the vehicle102, an entry206-B for configuring automatic engine start/stop behavior for the vehicle102, an entry206-C for configuring a timeout after which the vehicle102may determine that the mode is abandoned and may return to a normal mode, and an entry206-D for configuring alert settings in case of detection of unauthorized persons when the vehicle102is in the mode and the driver is away from the vehicle102.

Using the user interfaces202, a user may accordingly be able to manage criteria used to transition the vehicle102into and out of the different modes (e.g., normal mode, delivery mode, school mode, etc.), as well as the specific functioning of the controller104while in the various modes.

For example, when in the delivery mode, the controller104may be configured to automatically unlock vehicle102doors when the operator of the vehicle102approaches and automatically lock the vehicle102doors when the operator of the vehicle102. Or, when in the normal mode, the controller104may be configured to unlock the doors responsive to operator feedback, such as use of the key fob108or keypad122to request door unlock. Or, when in the school mode, the controller104may be configured to automatically adjust climate control settings when parked.

FIG. 5illustrates a diagram500of an example user interface202-D for alerting the user of an unauthorized user in proximity to the vehicle102. As with the user interfaces202-A,202-B, and202-C, the user interface202-D may be presented to the user via display features of mobile device134. The user interface202-D may be displayed, for example, responsive to the controller104determining that an unauthorized person is in proximity of the vehicle102. The user interface202-D may also include a title label208to indicate to the user that the user interface202-D is for the display of an alert.

The user interface202-D may also include a display control502configured to display media content captured by the capture device158of the vehicle102. In an example, the vehicle102may utilize the wireless transceiver136to transmit the captured media content to the mobile device134, which may be received by the wireless transceiver140, provided to the notification application172, and trigger the display of the user interface202-D. In another example, the captured media content may be provided by the wireless transceiver136(or an in-vehicle modem) to the remote server174via the communications network144, and may be retrieved from the remote server174by the mobile device134via the communications network144.

Regardless of how the captured media content is received, the user interface202-D may be configured to provide an indication to the user of the condition causing the alert. In an example, the capture devices158may include a 360 degree view camera or a set of cameras configured to provide a panoramic view of the vehicle102surroundings, and the display control502may display the panoramic view to the user of the mobile device134.

FIG. 6illustrates an example process600for adjusting mode settings166of the controller104based on detection of vehicle actions168. The process600may be performed, in an example, by the controller104in communication with other systems of the vehicle102.

At operation602, the controller104detects vehicle actions168. In an example, the mode control application170may determine the presence or lack of presence of the driver according to detection or lack of detection of the driver's mobile phone134or key fob108. In another example, the mode control application170may determine for how long the vehicle102remains in a location based on global positioning data, lack of movement recorded by wheel sensors, presence of the vehicle102within a predefined geo-fence area at a predetermined time, etc.

At operation604, the controller104compares the detected vehicle actions168to maintained mode settings166. In an example, the mode control application170may identify whether the vehicle actions168match vehicle actions168associated with mode settings166of the controller104. For instance, the mode control application170may compare the vehicle actions168to vehicle actions168associated with normal mode, to vehicle actions168associated with delivery mode, and to vehicle actions168associated with school mode.

At operation606, the controller104determines whether the actions require a change in mode settings166of the controller104. In an example, the mode control application170may determine that the vehicle actions168match vehicle actions168associated with one of the mode settings166of the controller104. If so, control passes to operation608. Otherwise, control passes to operation602.

At operation608, the controller104transitions to the mode settings166matching the identifier vehicle actions168. In an example, the controller104may transition to operation using the normal mode settings166-B, the delivery mode settings166-A, other settings such as school mode settings166, etc. After operation608, control passes to operation602.

FIG. 7illustrates an example process700for controlling a vehicle using delivery mode settings166-A. As with the process600, the process700may be performed, in an example, by the controller104in communication with other systems of the vehicle102.

At operation702, the controller104receives an indication of a vehicle action168relating to access to the vehicle102. As some examples, the mode control application170may receive the vehicle actions168from sources such as lock/unlock mechanism118, the keypad122, the ignition switch130, the RF transceiver106, the wireless controller132, or one or more other vehicle modules in communication with the controller104over a vehicle network such as a vehicle CAN bus. The vehicle actions168may include one or more of parking the vehicle102/unlocking the vehicle102, opening the driver door of the vehicle102, closing the driver door of the vehicle102, opening the cargo door of the vehicle102, closing the cargo door of the vehicle102.

At operation704, the controller104determines whether the driver or other vehicle102operator is at least a predetermined threshold distance away from the vehicle102. In an example, the mode control application170may determine the distance of the vehicle102from the key fob108according to signal strength received by the RF transceiver106from the key fob108. In another example, the controller104may determine the distance of the operator to the vehicle102using the mobile device134(e.g., according to a global position determined by the mobile device134and provided to the vehicle102). As some non-limiting examples, the predetermined threshold distance may be one meter, two meters, or ten meters. In another example, the predetermined threshold distance may be configurable, e.g., via the user interface202of the notification application172. If the operator is at least the predetermined threshold distance away, control passes to operation706. Otherwise, control passes to operation712.

At operation706, the controller104automatically secures the vehicle102. In an example, the mode control application170may lock the doors of the vehicle102, may shut off the engine of the vehicle102(e.g., if the vehicle102is not equipped with start/stop technology), and may enable the media capture functionality of the capture device158(e.g., via bus command from the controller104to the media content controller156).

At operation708, the controller104determines whether unexpected access to the vehicle102is detected. In an example, the mode control application170may receive an indication of attempted vehicle access (e.g., a pull of a door handle) while operator is at least a predetermined threshold distance away from the vehicle102. If an unexpected access is detected, control passes to operation710. Otherwise, control passes to operation718.

At operation710, the controller104sends an alert to the user. In an example, the mode control application170may utilize the wireless transceiver136to transmit the captured media content to the mobile device134. In another example, the captured media content may be provided by the wireless transceiver136(or an in-vehicle modem) to the remote server174via the communications network144, and may be retrieved from the remote server174by the mobile device134. An example user interface202-D for alerting the operator of an unauthorized user in proximity to the vehicle102is described above with respect toFIG. 5.

At operation712, the controller104determines whether the driver or other vehicle102operator has responded to the alert. In an example, the user may verify the cause of the alert, and may clear the alert using the user interface202-D. If the user selects to clear the alert within a predefined period of time (e.g., five seconds, thirty seconds, two minutes, an amount of time preconfigured by the user of the mobile device134, an amount of time preconfigured etc.), control passes to operation714. Otherwise, control passes to operation716.

At operation714, the controller104clears the alert. With the alert condition cleared, control passes to operation704.

At operation716, the controller104sends an alert to a central hub. In an example, the mode control application170may utilize the wireless transceiver136to transmit the captured media content to the remote server174for access by a central hub user. The central hub user may accordingly receive the media content and determine whether to call for assistance for the vehicle102. In an example, the central hub user may call police or another authority to inform them of the situation with the vehicle102. When doing so, the central hub user may be able to provide evidence in the form of the media content collected by the vehicle102with respect to the alert.

At operation718, the controller104determines whether the driver or other vehicle102operator is at least a predetermined threshold distance away from the vehicle102. The distance determination may be performed as discussed above with respect to operation704. If the operator is not at least the predetermined threshold distance away, control passes to operation720. Otherwise, control passes to operation704.

At operation720, the controller104automatically unsecures the vehicle102. In an example, the mode control application170may unlock the doors of the vehicle102, may restart the engine of the vehicle102(e.g., if the vehicle102is not equipped with start/stop technology), and may disable the media capture functionality of the capture device158(e.g., via bus command from the controller104to the media content controller156). After operation720, control passes to operation704.