Patent Description:
The present disclosure relates to video recording and monitoring activities inside and outside of a vehicle.

Drivers of vehicles, and in particular professional drivers of tractor trailers in a fleet, may face many challenges safely navigating vehicles through traffic, congestion, weather and various road conditions. Fleet owners may want to record and monitor activities inside and outside of fleet vehicles while drivers are operating fleet vehicles. Fleet owners may use the video to provide driver training to help prevent future risky behaviors. Professional drivers may also use fleet vehicles as a private residence when the driver is off duty. With the increase in video monitoring both inside and outside of fleet vehicles, the privacy of professional drivers using a fleet vehicle as a private residence is a concern. Reference <CIT> shows a system for managing a camera comprises an input interface configured to detect a change in state; a processor configured to block transfer of data from an inward facing video camera; and an output interface configured to indicate that transfer of data is blocked. Reference <CIT> illustrates a method of disabling a driver facing camera based on a signal by the driver indicating that the driver desires to disable the camera and based on the vehicle state. The driver facing camera is disabled in response to a control input indicating the driver desires to disable the camera and a vehicle state message indicating a vehicle state does not meet a predetermined condition. <CIT> finally show systems and methods are provided for recording video of a driver in a vehicle and a surrounding visual field of the drive.

Thus, there is a need in the art for improvements in video recording and monitoring activities of vehicles, and in particular, fleet vehicles.

The following presents a simplified summary of one or more implementations of the present disclosure in order to provide a basic understanding of such implementations. This summary is not an extensive overview of all contemplated implementations, and is intended to neither identify key or critical elements of all implementations nor delineate the scope of any or all implementations. Its sole purpose is to present some concepts of one or more implementations of the present disclosure in a simplified form as a prelude to the more detailed description that is presented later.

One example implementation relates to a method. The method may include determining a duty status of a driver of the vehicle. The method may also include controlling a recording status of at least one camera of a camera system on the vehicle based on the duty status.

Another example implementation relates to a computer device. The computer device may include a memory to store data and instructions and a processor in communication with the memory. The computer device may also include a camera privacy manager and a camera control component in communication with the memory and the processor, wherein the camera privacy manager and the camera control components are operable to determine a duty status of a driver of the vehicle, and control a recording status of at least one camera of a camera system on the vehicle based on the duty status.

Another example implementation relates to a computer-readable medium storing instructions executable by a computer device. The computer-readable medium may include at least one instruction for causing the computer device to determine a duty status of a driver of the vehicle. The computer-readable medium may include at least one instruction for causing the computer device to control a recording status of at least one camera of a camera system on the vehicle based on the duty status.

Additional advantages and novel features relating to implementations of the present disclosure will be set forth in part in the description that follows, and in part will become more apparent to those skilled in the art upon examination of the following or upon learning by practice thereof.

The present disclosure provides systems and methods for controlling the recording status of cameras and microphones within a vehicle to preserve driver privacy when a driver is off duty. An owner or manager of one or more vehicles, such as a fleet owner, may want to record and monitor activities inside and outside of the vehicle while drivers are operating the vehicles. While the present disclosure will be discussed using examples relating to a fleet owner and one or more fleet vehicles, it should be understood that the systems and methods described may be utilized by any vehicle owner to monitor driver activity of any vehicle.

For example, fleet owners or managers may want to view video during critical driving events, such as, but not limited to, hard braking, speeding, hard turns, and collisions. By seeing what drivers experience during critical driving events, or at specific dates and times, fleet owners may be able to better understand exactly what occurred. In addition, fleet owners may use the video to provide driving training to help prevent future risky behaviors. In case of an accident or incident fleet owners may be able to quickly determine what caused the incident. The systems and methods may provide video cameras inside and outside the cabin of a fleet vehicles so that video and/or audio monitoring capabilities may be provided inside and outside the cabin during a critical event to capture the conditions external to the vehicle and the corresponding behavior of a driver during a critical event.

However, professional drivers may also use fleet vehicles as a private residence when the driver is off duty. As such, professional drivers may not want to have private activities and/or private conversations recorded when the driver is off duty. The systems and methods of the present disclosure may provide camera and/or audio controls to turn off the cameras and/or audio recorders inside the fleet vehicles when drivers are off duty to preserve driver privacy. In addition, the systems and methods of the present disclosure may provide camera controls to turn on the cameras and/or audio recorders inside the fleet vehicles when the drivers are on duty to capture recordings and/or corresponding audio, for example, during critical events or other specific dates and times for driver training or review. In addition, the systems and method of the present disclosure provides camera controls to turn off or on the cameras and/or audio recorders inside the fleet vehicles based on a geographic location of the fleet vehicle and/or based on a entering a geographic area defined by a geo-fence.

Referring now to <FIG>, a system <NUM> for video recording and monitoring activities inside and outside of a vehicle may include one or more fleet vehicles <NUM> with at least one on-board computer device <NUM> having a camera privacy manager <NUM> for controlling the recording and storage of video (and, optionally, audio) of a driver and/or an interior of fleet vehicle <NUM> by a camera system <NUM>. Camera system <NUM> may include one or more interior-recording cameras <NUM> and/or one or more exterior recording cameras <NUM>. Interior-recording cameras <NUM> and/or exterior recording cameras <NUM> may include, but are not limited to, a forward-facing camera, a rear-facing camera, <NUM> degree cameras, dual cameras (e.g., an integrated interior-recording camera <NUM> and exterior-recording camera <NUM>), and/or mirror mounted cameras. In some cases, camera privacy manager <NUM> may operate in coordination with a critical event application <NUM>, which may additionally control the recording and storage of video (and, optionally, audio) of the environment inside and/or around fleet vehicle <NUM> by camera system <NUM>. On-board computer device <NUM> may include a processor <NUM> and/or memory <NUM>. An example of processor <NUM> can include, but is not limited to, any processor specially programmed as described herein, including a controller, microcontroller, application specific integrated circuit (ASIC), field programmable gate array (FPGA), system on chip (SoC), or other programmable logic or state machine. An example of memory <NUM> can include, but is not limited to, a type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.

On-board computer device <NUM> may include any mobile or fixed computer device, which may be connectable in a wired or wireless manner to communication over one or more networks <NUM>. On-board computer device <NUM> may be, for example, a computer device such as a desktop or laptop or tablet computer, a cellular or satellite telephone, a gaming device, a mixed reality or virtual reality device, a music device, a television, a navigation system, a camera, a personal digital assistant (PDA), a handheld communication device, or any other computer device having wired and/or wireless connection capability with one or more other devices or networks.

In one implementation, on-board computer device <NUM> may be an electronic logging device (ELD) having a duty status application <NUM> that keeps track of a duty status <NUM> of a driver of fleet vehicle <NUM>. For example, duty status <NUM> may include, but is not limited to, on duty, on duty driving, off duty, off duty driving, sleeper berth, and unknown. Duty status application <NUM> may keep track of duty status <NUM> based on an input from a driver to indicate a duty status or a change in duty status, and/or may automatically keep track of a duty status, e.g., based on detected movement of fleet vehicle <NUM> and/or based on information received from an electronic time keeping device. Additionally, for example, in some implementations, on-board computer device <NUM> may be an Omnitracs Enterprise Services platform device, such as an Intelligent Vehicle Gateway (IVG) device, or an Omnitracs XRS platform device, each offered by Omnitracs, LLC of Dallas, TX.

Network <NUM> may provide one or more types of communication connections, such as any type of wired or wireless airlink, to on-board computer device <NUM>, fleet vehicle <NUM>, interior-recording camera(s) <NUM>, exterior-recording camera(s) <NUM>, and/or microphone(s) <NUM>. For example, interior-recording camera <NUM> and/or microphone <NUM> may communicate over a wireless connection, such as a WiFi or Bluetooth connection, or over a wired connection, with on-board computer device <NUM>. Correspondingly, on-board computer device <NUM> may communicate over a WiFi or cellular or satellite connection with network <NUM>.

Network <NUM> allows on-board computer device <NUM> to communicate with one or more remote communication devices <NUM>. In one use case, remote communication device <NUM> may be a server associated with a network management center run by an operator of system <NUM>, or remote communication device <NUM> may be a computer device of a vehicle owner, fleet owner, or fleet manager. In either case, the one or more remote communication devices <NUM> may be used to configure the operation of camera privacy manager <NUM> and/or critical event video application <NUM>, and/or to receive the resulting recorded video (and/or audio) for storage and/or analysis, such as via communications component <NUM> and network <NUM> based on operation of camera privacy controller <NUM> and critical event controller <NUM>. In this case, camera privacy controller <NUM> and critical event controller <NUM> may be computer-implemented instructions, logic, hardware, firmware, or any combination thereof that enable interfacing with, sending commands and configuration data to, and/or receiving recorded video and/or audio or other vehicle-parameter-related data from, on-board computer device <NUM>. Camera privacy controller <NUM> and critical event controller <NUM> may be stored and executed by a combination of memory <NUM> and processor <NUM> of remote computer device <NUM>.

Fleet vehicles <NUM> may include a group of one or more vehicles owned or leased by a business, government agency, or other organization or individual. Fleet vehicle <NUM> may include a camera system <NUM> of one or more cameras, such as interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM>. For example, interior-recording camera(s) <NUM> may be located on fleet vehicle <NUM> to record the environment inside fleet vehicle <NUM> (e.g., positioned to record one or more of the driver, the passenger, the dashboard, computer device <NUM>, or anything inside the cab) and exterior-recording camera(s) <NUM> may be located on fleet vehicle <NUM> to record the environment outside of fleet vehicle <NUM> (e.g.. , positioned to record one or more of an area in front of the vehicle (including the road, other vehicles, etc.), the areas at the sides of the vehicle, or the area behind the vehicle). As such, camera system <NUM> cameras may record and monitor activities inside and/or outside fleet vehicle <NUM>. In an aspect, fleet vehicle <NUM> may include a dual camera (e.g., an integrated interior-recording camera <NUM> and exterior-recording camera <NUM>) located inside a cabin of fleet vehicle <NUM> so that the dual camera may record and monitor activities inside the cabin of fleet vehicle <NUM> (e.g., driver behavior) and may record and monitor activities outside the cabin of fleet vehicle <NUM> (e.g., road and environmental conditions, and activity of other vehicles near fleet vehicle <NUM>).

Each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> may include a microphone <NUM> to record and monitor activities inside and outside, respectively, of fleet vehicle <NUM>. Each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> may also maintain a recording status <NUM> that indicates whether each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> is on and recording information or is off and is not recording information. In addition, each microphone <NUM> may include a microphone status <NUM> that indicates whether microphone <NUM> is on and recording information or microphone <NUM> is off and is not recording information. Each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> and the corresponding microphone(s) <NUM> may be controlled independently. As such, each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> may or may not be recording video while the corresponding microphone(s) <NUM> may or may not be recording sound.

On-board computer device <NUM> may include a camera control component <NUM> operable to control recording status <NUM> of each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM>. In addition, on-board computer device <NUM> may include a microphone control component <NUM> operable to control microphone status <NUM> of each of the one or more microphones <NUM>. When fleet vehicle <NUM> includes a plurality of cameras <NUM>, <NUM> and/or microphones <NUM>, each individual camera <NUM>, <NUM> or microphone <NUM> may be controlled independently. As such, different cameras <NUM>, <NUM> and/or microphones <NUM> may have a different recording status <NUM> and/or microphone status <NUM>. For example, exterior-recording camera <NUM> of fleet vehicle <NUM> may have a recording status <NUM> of on, while a driver facing interior-recording camera <NUM> of fleet vehicle <NUM> may have a recording status <NUM> of off.

Camera control component <NUM> and/or microphone control component <NUM> may communicate with a camera privacy manager <NUM> to determine the recording status <NUM> of each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> and/or the microphone status <NUM> of each microphone <NUM>. Camera privacy manager <NUM> may apply one or more rules in determining the recording status <NUM> of each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> and/or the microphone status <NUM> of each microphone <NUM>. The one or more rules may be based on, for example, the duty status <NUM> of a driver of fleet vehicle <NUM>. The one or more rules may also be based on a driving status <NUM> of fleet vehicle <NUM>. The one or more rules may also be based on geolocation information <NUM> received from fleet vehicle <NUM>.

For example, camera privacy manager <NUM> may determine duty status <NUM> of a driver of fleet vehicle <NUM>. As noted above, duty status <NUM> includes but is not limited to, on duty, on duty driving, off duty, off duty driving, sleeper berth, and unknown. In an aspect, camera privacy manager <NUM> may request and receive the duty status <NUM> from duty status application <NUM>. Duty status application <NUM> may include, but is not limited to, an hour of service application, an electronic time keeping application, an AOBRD (Automatic On-Board Recording Device), and an ELD. Duty status application <NUM> may keep track of duty status <NUM> based on an input from a driver to indicate a duty status or a change in duty status. In addition, duty status application <NUM> may automatically keep track of a duty status. For example, duty status application <NUM> may determine a duty status <NUM> of a driver based on detected movement of fleet vehicle <NUM> and/or based on electronic time keeping information received from an electronic time keeping device. For example, a driver of fleet vehicle <NUM> may use on-board computer device <NUM> and duty status application <NUM> to update a current duty status <NUM> of the driver. For example, when the driver is finished driving for the day, the driver may change the current duty status <NUM> from on duty to off duty using duty status application <NUM>. In another aspect, camera privacy manager <NUM> may automatically receive the duty status <NUM> from duty status application <NUM> that is tracking duty status <NUM> of a driver, such as based on a change in duty status <NUM>.

Further, for example, camera privacy manager <NUM> may also determine driving status <NUM> of fleet vehicle <NUM>. Driving status <NUM> may include, for example, a movement state of fleet vehicle <NUM>, such as moving or not moving. The movement state of fleet vehicle <NUM> may be a direct measure of vehicle movement, such as velocity or acceleration, or an indirect vehicle movement-related parameter, such as a brake status. For instance, a brake status may include whether a parking brake is enabled or disabled. Camera privacy manager <NUM> may communicate with vehicle movement component <NUM> to determine the movement state of fleet vehicle <NUM>.

Vehicle movement component <NUM> may receive one or more indicators of the movement state from fleet vehicle <NUM> to indicate whether fleet vehicle <NUM> is moving. For example, vehicle movement component <NUM> may receive the movement state in the form of a speed <NUM> of fleet vehicle <NUM>. In addition, vehicle movement component <NUM> may receive the movement state in the form of a parking brake status <NUM> to indicate whether a parking brake of fleet vehicle <NUM> is set, e.g., engaged or disengaged. Vehicle movement component <NUM> may receive the movement state information from one or more monitoring or control devices, such as a controller area network (CANbus) system and/or an Electronic Control Module (ECM), located on fleet vehicle <NUM>. Vehicle movement component <NUM> may use the received speed <NUM> information and/or parking brake status <NUM> to determine the movement state of fleet vehicle <NUM>.

Camera privacy manager <NUM> may then apply one or more rules or conditions for determining the recording status <NUM> of each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> and/or microphone status <NUM> of each microphone <NUM>. For example, the recording status <NUM> of interior-recording camera(s) <NUM> may be on when parking brake status <NUM> is off and the vehicle speed <NUM> is over zero, as driver privacy would not be expected when fleet vehicle <NUM> is being operated. As such, interior-recording camera(s) <NUM> may record and store video when the recording status <NUM> is on. Another example rule may include turning the recording status <NUM> of interior-recording camera(s) <NUM> to off after a predetermined time period (e.g., <NUM> seconds) when the parking brake is enabled (based on parking brake status <NUM>) on fleet vehicle <NUM>, for instance, to allow driver privacy when fleet vehicle <NUM> is not being operated. Thus, interior-recording camera(s) <NUM> may stop recording and storing video when the recording status <NUM> is off. Another example rule may include turning the recording status <NUM> of interior-recording camera(s) <NUM> to on after a predetermined time period (e.g., <NUM> seconds) when the duty status <NUM> of the driver changes to on duty and fleet vehicle <NUM> is moving, as driver privacy would not be expected when the driver is on duty and fleet vehicle <NUM> is being operated. Another example may include turning the recording status <NUM> of interior-recording camera(s) <NUM> to off after a predetermined time period (e.g., <NUM> seconds) when the duty status <NUM> of the driver changes to off duty, sleeper berth, or unknown, for instance, to allow driver privacy when the driver is not on duty. Another example rule may include turning the recording status <NUM> of exterior-recording camera(s) <NUM> to off when the duty status <NUM> of the driver changes to off duty, sleeper berth, or unknown, for instance, to allow driver privacy when the driver is not on duty. For example, if the fleet vehicle <NUM> is parked at the home of the drive while the driver is not on duty, the exterior-recording camera(s) <NUM> may be turned to off to protect the privacy of the driver at home. Another example rule may include turning the microphone status <NUM> of microphone <NUM> of interior-recording camera(s) <NUM> to off after a predetermined time period when the duty status <NUM> of the driver changes to off duty, sleeper berth, or unknown, for instance, to allow driver privacy when the driver is not on duty.

According to the invention, another rule is based on geographic location, such as turning the recording status <NUM> of camera <NUM> to off when the geolocation information <NUM> indicates that fleet vehicle <NUM> is in a restricted area or a secured facility, such as, but not limited to, a military base or chemical facility. For example, camera privacy manager <NUM> may receive the current geolocation information <NUM> of fleet vehicle <NUM> from a terrestrial and/or satellite-based positioning system (e.g., Global Positioning System (GPS)) component on fleet vehicle <NUM>. Camera privacy manager <NUM> may interface with a repository (e.g., in memory <NUM>) of landmarks and/or locations that may be identified as restricted areas or secured facilities. Camera privacy manager <NUM> may compare the current geolocation information <NUM> with the repository of landmarks and/or locations to determine whether fleet vehicle <NUM> is located in a restricted area or secured facility. In another aspect, geofences may be established around restricted areas or secured facilities so that when the current geolocation information <NUM> of fleet vehicle <NUM> indicates that fleet vehicle <NUM> enters into the geofenced area, e.g., a restricted or secured area, camera privacy manager <NUM> may update the recording status of camera <NUM> to off. It should be noted that the geofence may be defined based on locations stored in memory <NUM>, and/or based on receiving wireless signals, such as from a radio frequency identification (RFID) device or other wireless transmitter, that identify a geofenced area.

Other example rules for controlling the recording status <NUM> of each of the one or more interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> and the microphone status <NUM> of each microphone <NUM> are illustrated below in the following tables.

An example rule for controlling a recording status <NUM> of interior-recording camera(s) <NUM> when duty status <NUM> changes to "off duty driving," and having camera off and on delays, is illustrated in the below Table <NUM>. In this case, duty status <NUM> having a "<NUM>" value indicates that the driver-facing camera will be commanded to turn off when the driver's duty status changes to Off Duty Driving and a "<NUM>" value indicates that the driver-facing camera will be commanded to turn on when the driver's duty status changes to Off Duty Driving.

An example rule for controlling a recording status <NUM> of camera <NUM> when duty status <NUM> changes to "on duty," and having camera off and on delays, is illustrated in the below Table <NUM>. In this case, duty status <NUM> having a "<NUM>" value indicates that the driver-facing camera will be commanded to turn off when the driver's duty status change to On Duty Driving, a "<NUM>" value indicates that the driver-facing camera will be commanded to turn on when the driver's duty status changes to On Duty, and a "<NUM>" value indicates that the driver-facing camera will be commanded to remain in its present recording state when the driver's duty status changes to On Duty. The tertiary option allows, for example, a transition from Off Duty to On Duty to be treated differently than a transition from Driving to On Duty.

In Table, <NUM>, by having an option (e.g., duty status <NUM> having the value of "<NUM>") to have the recording status <NUM> of interior-recording camera <NUM> remain in the present state, the previous state may control the recording status <NUM> of interior-recording camera <NUM>. For example, if the driver changed the duty status <NUM> from "off duty" to "on duty," the recording status <NUM> of interior-recording camera <NUM> would remain off because the driver may be still preparing to drive. However, if the driver or on-board computer device <NUM> (e.g., hours of service (HOS) application <NUM>) changes the duty status <NUM> from "driving" to "on duty" because the fleet vehicle <NUM> remained still for a period of time, for example, <NUM> minutes, the interior-recording camera <NUM> would continue to record video because the driver is still working.

An example rule for controlling a recording status <NUM> of interior-recording camera <NUM> when duty status <NUM> changes to "on duty driving" is illustrated in the below Table <NUM>.

An example rule for controlling a microphone status <NUM> of microphone <NUM> when duty status <NUM> changes to "off duty driving" is illustrated in the below Table <NUM>.

An example rule for controlling a microphone status <NUM> of microphone <NUM> when duty status <NUM> changes to "on duty" is illustrated in the below Table <NUM>.

By having an option to have the microphone status <NUM> of microphone <NUM> remain in the present state, the previous state may control the microphone status <NUM> of microphone <NUM>. For example, if the driver changed his status from "off duty" to "on duty," the microphone status <NUM> of microphone <NUM> would remain off because the driver may be still preparing to drive. However, if the driver or the ELD changes his status from "driving" to "on duty" because the fleet vehicle <NUM> remained still for a period of time, for example, <NUM> minutes, the microphone <NUM> would continue to record video because the driver is still working.

An example rule for controlling a microphone status <NUM> of microphone <NUM> when a duty status <NUM> changes to "on duty driving" is illustrated in the below Table <NUM>.

An example rule for controlling a recording status <NUM> of interior-recording camera <NUM> when driving status <NUM> changes, based on ignition and parking brake states, along with camera on and off delays, is illustrated in the below Table <NUM>.

An example rule for controlling a microphone status <NUM> of microphone <NUM> when driving status <NUM> changes, based on ignition and parking brake states, along with camera on and off delays, is illustrated in the below Table <NUM>.

As mentioned above, on-board computer device <NUM> may also include critical event video application <NUM> operable to cause video (and audio) to be recorded, and to enable retrieval of recorded video (and audio) from interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM>. For example, critical event video application <NUM> may be configured with one or more critical event rules <NUM> that trigger interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> to record video (and/or audio). Critical event rules may include detection of one or more critical events associated with the operation of fleet vehicle <NUM>. Suitable examples of a critical event may include, but is not limited to, one or any combination of hard braking, the use of the anti-lock braking system (ABS), roll stability state, a lane departure warning, and a following time violation. A following time violation may include when a quotient of a distance to the vehicle in front of the fleet vehicle <NUM> (as measured by, for example, a radar system) divided by the speed of fleet vehicle <NUM> is less than a configurable number of seconds for a configurable period of time (e.g., <NUM> seconds for <NUM> minutes).

Critical event rules <NUM> may additionally include rules on a how long recording should be maintained, and/or rules on uploading or providing access to the recorded video (and/or audio). Further, critical event rules <NUM> may specify other vehicle parameter information that is to be collected (e.g., from a CANbus or ECM) along with the video and/or audio from one of more internal cameras <NUM> and/or external cameras <NUM>. Critical event controller <NUM> at remote computer device <NUM> can configure one or more critical event rules <NUM>, and/or can generate a request for video to be sent to on-board computer device <NUM> in response to a user request (e.g., for video associated with a critical event, or for video associated with a specific date/time). In some cases where interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> may be recording continuously, the amount of video retrieved before and/or after a critical event may be configured by a user or may be predetermined by critical event controller <NUM> or critical event video application <NUM>. Critical event video application <NUM> may retrieve and upload video automatically upon the occurrence of one or more critical events. Thus, fleet owners or managers, via operation of critical event controller <NUM> at remote computer device <NUM>, may receive reliable information quickly to help identify a cause of the critical event, help defend a driver who was involved in an accident, and/or to identify unacceptable driving behaviors.

Because camera privacy manager <NUM> may communicate with camera control component <NUM> and/or microphone control component <NUM> to update the recording status <NUM> of interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> or microphone status <NUM> of each microphone <NUM> based on one or more of the duty status <NUM> and/or the driving status <NUM>, when critical event video application <NUM> retrieves and uploads video based on the critical event rules <NUM> and/or in response to a user request, driver privacy may be maintained because interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> may be inactive when the driver uses the fleet vehicle <NUM> as a private residence or based on one or video recording rules designed to ensure driver privacy.

In another aspect, instead of camera privacy manager <NUM> controlling the recording status <NUM> of interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> or each microphone <NUM> based on the duty status <NUM> and/or driving status <NUM>, camera privacy manager <NUM> may communicate with critical event video application <NUM> to prevent video being retrieved from interior-recording camera(s) <NUM> and/or exterior-recording camera(s) <NUM> during the time periods the duty status <NUM> changes to off duty, sleeper berth, or unknown to preserve driver privacy.

Referring now to <FIG>, a method <NUM> for controlling a recording status of a camera and/or a microphone on a vehicle may be executed by on-board computer device <NUM> (<FIG>).

At <NUM>, method <NUM> may include determining a duty status of a driver of a vehicle. A duty status may include, for example, on duty, on duty driving, off duty, off duty driving, sleeper berth, and unknown. Camera privacy manager <NUM> may determine a duty status <NUM> of a driver of fleet vehicle <NUM>. Camera privacy manager <NUM> may request and receive the duty status <NUM> from duty status application <NUM>. A driver of fleet vehicle <NUM> may use on-board computer device <NUM> and duty status application <NUM> to update a current duty status <NUM> of the driver. For example, when the driver is finished driving for the day, the driver may change the current duty status <NUM> from on duty to off duty using duty status application <NUM>. In another aspect, camera privacy manager <NUM> may automatically receive the duty status <NUM> from duty status application <NUM> that is tracking the duty status <NUM> of a driver, such as based on a change in duty status <NUM> and/or from an electronic time keeping device. In another aspect, camera privacy manager <NUM> may receive the duty status <NUM> from an electronic logging device (ELD) tracking a number of hours the driver has driven.

At <NUM>, method <NUM> may optionally include determining a driving status of the vehicle. For example, in one implementation, camera privacy manager <NUM> may determine a driving status <NUM> of fleet vehicle <NUM>. Driving status <NUM> may include, for example, a movement state of fleet vehicle <NUM>, such as moving or not moving. The movement state of fleet vehicle <NUM> may be a direct measure of vehicle movement, such as velocity or acceleration, or an indirect vehicle movement-related parameter, such as a brake status. For instance, a brake status may include whether a parking brake is enabled or disabled. Camera privacy manager <NUM> may communicate with vehicle movement component <NUM> to determine the movement state of fleet vehicle <NUM>.

At <NUM>, method <NUM> may include controlling a recording status of at least one camera of a camera system on the vehicle based on the duty status. Fleet vehicle <NUM> may include a camera system <NUM> with a plurality of cameras, such as one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording cameras <NUM>. In addition, one or more cameras on fleet vehicle <NUM> may be a dual camera that integrates interior-recording camera <NUM> and exterior-recording camera <NUM> so that the dual camera may record and monitor activities inside the cabin of fleet vehicle <NUM> and may record and monitor activities outside the cabin of fleet vehicle <NUM>. A recording status <NUM> of interior-recording camera <NUM>, exterior-recording camera <NUM>, and/or dual camera may include on or off.

A camera control component <NUM> may control a recording status <NUM> of cameras in camera system <NUM>. For example, camera control component <NUM> may control one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording cameras <NUM>. Camera control component <NUM> may communicate with a camera privacy manager <NUM> to determine the recording status <NUM> of one or more interior-recording camera(s) <NUM> and one or more exterior-recording cameras <NUM>. Camera privacy manager <NUM> may apply one or more rules or conditions in determining the recording status <NUM> of each of one or more interior-recording camera(s) <NUM> and one or more exterior-recording cameras <NUM>. The one or more rules may be based on, for example, a duty status <NUM> of a driver of fleet vehicle <NUM> and, optionally, a driving status <NUM> of fleet vehicle <NUM>. An example rule may include turning the recording status <NUM> of one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording cameras <NUM> to off after a predetermined time period (e.g., <NUM> seconds) when the duty status <NUM> of the driver changes to off duty, sleeper berth, or unknown. Another rule may include turning the recording status <NUM> of one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> to off after a predetermined time period (e.g., <NUM> seconds) when the parking brake is enabled on fleet vehicle <NUM>. Thus, one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> may stop recording and storing video when the recording status <NUM> is off. Another rule may include turning the recording status <NUM> of one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> to on when the duty status <NUM> of the driver changes to on duty or on duty driving. As such, one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> may record and store video when the recording status <NUM> is on.

At <NUM>, optionally, method <NUM> may include controlling a microphone status of a microphone located inside the vehicle based on the duty status. Microphone control component <NUM> may control a microphone status <NUM> of microphone <NUM>. Microphone control component <NUM> may communicate with a camera privacy manager <NUM> to determine the microphone status <NUM> of microphone <NUM>. Camera privacy manager <NUM> may apply one or more rules or conditions in determining the microphone status <NUM> of microphone <NUM>. The one or more rules may be based on, for example, a duty status <NUM> of a driver of fleet vehicle <NUM> and, optionally, a driving status <NUM> of fleet vehicle <NUM>. One example rule may include turning the microphone status <NUM> of microphone <NUM> to off after a predetermined time period when the duty status <NUM> of the driver changes to off duty, sleeper berth, or unknown.

Referring now to <FIG>, a method <NUM> for controlling a recording status of a camera and/or a microphone on a fleet vehicle based on the geolocation of the fleet vehicle may be executed by on-board computer device <NUM> (<FIG>). It should be noted that method <NUM> may be executed in conjunction with method <NUM> such that the geographic location of fleet vehicle <NUM> is another factor that determines whether or not a camera and/or microphone are turned on or off.

At <NUM>, method <NUM> may include receiving geolocation information of a vehicle. For example, camera privacy manager <NUM> may receive the current geolocation information <NUM> of fleet vehicle <NUM> from a terrestrial and/or satellite-based positioning system component on fleet vehicle <NUM>.

At <NUM>, method <NUM> may include controlling a recording status of at least one camera on the vehicle based on the geolocation information. Camera privacy manager <NUM> may determine that the recoding status <NUM> of one or more cameras in camera system <NUM>, such as one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> may need to change based on the geolocation information <NUM> of fleet vehicle <NUM>. For example, if the geolocation information <NUM> indicates that fleet vehicle <NUM> may be in a restricted area or a secured facility, such as, but not limited to, a military base or chemical facility, camera privacy manager <NUM> may notify camera control component <NUM> that the recording status <NUM> of one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording cameras <NUM> should be changed to off, if the current recording status <NUM> of the respective camera is on. As such, one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording camera(s) <NUM> may stop recording and storing video when the recording status <NUM> is off. Another example may include, if the geolocation information <NUM> indicates that fleet vehicle <NUM> may be on a highway or road, camera privacy manager <NUM> may notify camera control component <NUM> that the recording status <NUM> of one or more interior-recording camera(s) <NUM> and/or one or more exterior-recording cameras <NUM> should be changed to on, if the current recording status <NUM> of the respective camera is off.

At <NUM>, method <NUM> may include controlling a microphone status of a microphone associated with the at least one camera based on the geolocation information. Camera privacy manager <NUM> may determine that the microphone status <NUM> of microphone <NUM> may need to change based on the geolocation information <NUM> of fleet vehicle <NUM>. For example, if the geolocation information <NUM> indicates that fleet vehicle <NUM> may be in a restricted area or a secured facility, camera privacy manager <NUM> may notify microphone control component <NUM> that the microphone status <NUM> of microphone <NUM> should be changed to off, if microphone <NUM> is not already off.

Referring now to <FIG>, illustrated is an example on-board computer device <NUM> in accordance with an implementation, including additional component details as compared to <FIG>. In one example, on-board computer device <NUM> may include processor <NUM> for carrying out processing functions associated with one or more of components and functions described herein. Processor <NUM> can include a single or multiple set of processors or multicore processors. Moreover, processor <NUM> can be implemented as an integrated processing system and/or a distributed processing system.

On-board computer device <NUM> may further include memory <NUM>, such as for storing local versions of applications being executed by processor <NUM>. Memory <NUM> can include a type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.

Further, on-board computer device <NUM> may include a communications component <NUM> that provides for establishing and maintaining communications with one or more parties utilizing hardware, software, and services as described herein. Communications component <NUM> may carry communications between components on on-board computer device <NUM>, as well as between on-board computer device <NUM> and external devices, such as devices located across a communications network and/or devices serially or locally connected to on-board computer device <NUM>. For example, communications component <NUM> may include one or more buses, and may further include transmit chain components and receive chain components associated with a transmitter and receiver, respectively, operable for interfacing with external devices.

Additionally, on-board computer device <NUM> may include a data store <NUM>, which can be any suitable combination of hardware and/or software, that provides for mass storage of information, databases, and programs employed in connection with implementations described herein. For example, data store <NUM> may be a data repository for camera control component <NUM> (<FIG>), microphone control component <NUM> (<FIG>), vehicle movement component <NUM> (<FIG>), critical event video application <NUM> (<FIG>), camera privacy manager <NUM> (<FIG>), and/or duty status application <NUM> (<FIG>).

On-board computer device <NUM> may also include a user interface component <NUM> operable to receive inputs from a user of on-board computer device <NUM> and further operable to generate outputs for presentation to the user. User interface component <NUM> may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition component, any other mechanism capable of receiving an input from a user, or any combination thereof. Further, user interface component <NUM> may include one or more output devices, including but not limited to a display, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.

In an implementation, user interface component <NUM> may transmit and/or receive messages corresponding to the operation of camera control component <NUM>, microphone control component <NUM>, vehicle movement component <NUM>, critical event video application <NUM>, camera privacy manager <NUM>, and/or duty status application <NUM>. In addition, processor <NUM> executes camera control component <NUM>, microphone control component <NUM>, vehicle movement component <NUM>, critical event video application <NUM>, camera privacy manager <NUM>, and/or duty status application <NUM>, and memory <NUM> or data store <NUM> may store them.

As used in this application, the terms "component," "system" and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computer device and the computer device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Furthermore, various implementations are described herein in connection with a device (e.g., on-board computer device <NUM>), which can be a wired device or a wireless device. A wireless device may be a cellular telephone, a satellite phone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, a computer device, a mixed reality or virtual reality device, or other processing devices connected to a wireless modem.

Various implementations or features may have been presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches may also be used.

The various illustrative logics, logical blocks, and actions of methods described in connection with the embodiments disclosed herein may be implemented or performed with a specially-programmed one of a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may also be implemented as a combination of computer devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor may comprise one or more components operable to perform one or more of the steps and/or actions described above.

Further, the steps and/or actions of a method or algorithm described in connection with the implementations disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. Further, in some implementations, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal. Additionally, in some implementations, the steps and/or actions of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.

In one or more implementations, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. A storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers.

Claim 1:
A method of controlling a camera system on a vehicle, comprising:
determining, by a processor, a duty status of a driver of the vehicle, wherein the duty status is one of on duty, on duty driving, off duty, off duty driving, sleeper berth or unknown, the duty status being automatically obtained from a duty status application that keeps track automatically of the duty status of a driver in an electronic log tracking a number of hours the driver has driven;
obtaining, by a processor, from a terrestrial and/or satellite-based positioning system geolocation information of the vehicle;
obtaining, by a processor, one or more location that are identified as restricted areas;
determining, by a processor, whether the vehicle is in a restricted area using the obtained geolocation information of the vehicle;applying, by the processor, one or more rules based at least upon the duty status of the driver for determining a recording status of at least one interior-recording camera of the camera system, wherein the recording status includes an on status corresponding to recording and an off status corresponding to not recording; and
in response to determining that the vehicle is in a restricted area using the obtained geolocation information of the vehicle
applying, by the processor, a rule to set the recording status to the off status;
controlling, by the processor, the recording status of the at least one interior-recording camera based on the one or more rules, wherein the camera system records activities inside the vehicle.