Patent Description:
Privacy is a concern for users of such computing devices including cameras. For instance, control may be gained of a camera in a computing device for a variety of undesired reasons. For instance, control may be acquired of the camera included in the computing device and/or access may be gained to electronic images captured by the camera, unbeknownst to a user of the computing device. In some approaches, this may be possible because the camera may be visible and accessible to the user at all times during operation of the computing device. For example, in some approaches the camera may be mounted on an exterior portion of the computing device (e.g., on a display of the computing device), where it may be visible and accessible to the user during operation of the computing device.

Examples disclosed herein provide the ability for a user to intuitively trigger a privacy solution, for example, to cover an image sensor of an image capture device, according to an example. As an example of being intuitive, natural user interactions may cycle between engaging and disengaging the privacy solution, such as a shutter. For example, referring to the webcam on a computing device, if a user desires to engage a privacy solution to cover the image sensor of the webcam, a first gesture, such as a tap on the webcam, may engage the privacy solution. Similarly, if the user desires to later disengage the privacy solution, in order to make use of the webcam, a second gesture, such as a swipe (or long press), may disengage the privacy solution. As a result, rather than searching for the trigger that cycles between engaging and disengaging the privacy solution (e.g., a function key), the user's intuitive reaction with the webcam itself may control the privacy solution, as will be further described.

In addition, rather than relying on a trigger separate from the webcam to engage and disengage the privacy solution, by integrating the trigger with the webcam itself, for example, via the gestures, control of the privacy solution may be electrically isolated from rest of the computing device, including the operating system of the device. As a result, the triggering of the privacy solution may be removed from malicious agents, such as hackers. For example, even if the webcam is hacked, where images can be captured without knowledge of the user, as the triggering of the privacy solution is electrically isolated from the rest of the computing device, particularly the operating system, when the privacy solution is covering the image sensor of the webcam, such capture may be prevented from occurring.

With reference to the figures, <FIG> illustrate the use of gestures to trigger a privacy solution comprising a shutter <NUM>, to cover the image sensor of an image capture device <NUM> of a computing device <NUM>, such as the webcam, according to an example. Referring to <FIG>, the image sensor of the image capture device <NUM> is exposed, and available for use by the user of the computing device <NUM>. However, when the user desires to engage the shutter <NUM> to cover the image sensor of the image capture device <NUM>, natural user touch interactions, such as a tap on the image capture device <NUM>, trigger the shutter <NUM> to cover the image sensor of the image capture device <NUM>. As an example of the natural touch interaction by the user, when the user desires privacy, the user may naturally use their finger to block the image capture device <NUM>. This action, or tap of the finger by the user, may correspond to a first gesture <NUM> performed by the user (e.g., depicted by hand). However, gestures besides a tap may be used to engage the shutter <NUM> to cover the image sensor of the image capture device <NUM>. <FIG> illustrates engagement of the shutter <NUM> to cover the image sensor of the image capture device <NUM>, upon detection of the first gesture <NUM> performed by the user. The shutter <NUM> may be actuated by various sources, such as by a solenoid, or it may be electrically-controlled.

Referring to <FIG>, when the user desires to disengage the shutter <NUM>, in order to expose the image sensor of the image capture device <NUM> for use, a second gesture <NUM> different from the first gesture <NUM>, is used to disengage the shutter <NUM>. As an example of a natural user touch interaction when a user desires to utilize the image capture device <NUM>, a second gesture <NUM>, such as a finger swipe, or an attempt to "slide" open or "wipe" the image capture device <NUM> may be registered as a trigger to disengage the shutter <NUM> from covering the image sensor of the image capture device <NUM>. However, gestures besides the finger swipe may be used to disengage the shutter <NUM>. For example, a controller utilized to detect the gestures may determine the complexity of the gesture that may be used to engage and disengage the shutter <NUM>, as will be further described. In addition, if a gesture besides the first or second gesture is detected, the gesture may be ignored. For example, if the gesture detected is neither a tap (e.g., first gesture) nor a swipe (e.g., second gesture), the image capture device <NUM> may determine that the gesture is an inadvertent action performed by the user, or a false trigger to actuate the shutter <NUM>. <FIG> illustrates the image sensor of the image capture device <NUM> made available for use by the user.

<FIG> illustrates the image capture device <NUM> coupled to a controller <NUM> for cycling between engaging and disengaging the shutter (not shown), according to an example. As described above, the shutter (e.g., shutter <NUM>) is used to cover or expose an image sensor <NUM> of the image capture device <NUM>, based on the gesture detected from a user touch interaction on the image capture device <NUM>. As an example of registering user touch interactions, the image capture device <NUM> includes a touch-enabled layer <NUM> disposed above the image sensor <NUM> for detecting touch events on the image capture device <NUM>. As will be further described, the controller <NUM> may be connected to the touch-enabled layer <NUM>, to register user touch interactions and detect gestures, in order to control the shutter (e.g., to switch between covering and exposing the image sensor <NUM>).

As an example, the touch-enabled layer <NUM> includes a capacitive mesh for detecting user touch interactions. For example, a mesh, capacitive-interlaced plastic layer may be disposed above the image sensor <NUM>. In order for the image sensor <NUM> to capture images, the touch-enabled layer <NUM> may be a translucent plastic cover, having a capacitive mesh inside. This capacitive mesh may be connected to the controller <NUM> that registers the user touch interactions. The density of the capacitive mesh, illustrated in a grid-like fashion on the touch-enabled layer <NUM> in <FIG>, may vary. The density of the capacitive mesh may determine a sensitivity for the controller <NUM> to detect the user touch interactions with the touch-enabled layer <NUM>, and a transparency of the touch-enabled layer <NUM> to expose the image sensor <NUM>. For example, enough spacing should be allowed between the metallic wires of the capacitive mesh, in order to allow the touch-enabled layer <NUM> to still be transparent and see-through, for images to be captured by the image sensor <NUM>. However, the spacing between the metallic wires should be narrow enough for the controller <NUM> to correctly register the user touch interactions with the touch-enabled layer <NUM>. As a result, the sensitivity of the touch-enabled layer <NUM> and the transparency of the touch-enabled layer <NUM> may be inversely proportional to each other, so a balance approach may be desirable between the sensitivity and transparency.

As mentioned above, the controller <NUM> may determine the complexity of the gesture that may be used to engage and disengage the shutter of the image capture device <NUM>. For example, a first gesture, such as a tap on the image capture device <NUM>, may engage the shutter, as described above. Similarly, if the user desires to later disengage the shutter, in order to make use of the image capture device <NUM>, a second gesture, such as a swipe, may disengage the shutter. However, if the controller <NUM> lacks the complexity to differentiate between a tap and a swipe, then the differentiation, whether to engage or disengage the shutter, may be made by simply measuring the length of time that the user maintains contact with the touch-enabled layer <NUM>. For example, when a user presses and holds its touch on the touch-enabled layer <NUM>, the controller <NUM> may interpret the gesture as an indication to engage the shutter to cover the image sensor <NUM>. Similarly, when the user performs a quick press on the touch-enabled layer <NUM>, the controller <NUM> may interpret the gesture as an indication to disengage the shutter to expose the image sensor <NUM>. As mentioned above, if a gesture besides the first or second gesture is detected, the gesture may be ignored.

As an example, the controller <NUM> is electrically isolated, for example, from the operating system (OS) of the computing device housing the image capture device <NUM>. Since the controls described above are built directly into the image capture device <NUM>, there is electrical isolation between the image capture device <NUM> and other components of the computing device, such as the operating system. As a result, the triggering of the shutter may be removed from malicious agents, such as hackers, providing a safe and secure environment for users of the computing device.

<FIG> illustrates an image capture device <NUM> for registering user touch interactions with touch-enabled layer <NUM> to control shutter <NUM>, according to an example. The image capture device <NUM> may correspond to the image capture device <NUM> illustrated in <FIG> and <FIG>. The image capture device <NUM> depicts the controller <NUM> and a memory device <NUM> and, as an example of the image capture device <NUM> performing its operations, the memory device <NUM> includes instructions <NUM>-<NUM> that are executable by the controller <NUM>. Thus, memory device <NUM> can be said to store program instructions that, when executed by controller <NUM>, implement the components of the image capture device <NUM>. As mentioned above, since controls are built directly into the image capture device <NUM>, there is electrical isolation between the image capture device <NUM> and other components of the computing device housing the image capture device <NUM>, such as the operating system. The executable program instructions stored in the memory device <NUM> include, as an example, instructions to register user touch interaction (<NUM>), instructions to detect gesture (<NUM>), and instructions to engage/disengage shutter (<NUM>).

Instructions to register user touch interaction (<NUM>) represent program instructions that when executed by the controller <NUM> cause the image capture device <NUM> to detect touch events with the touch-enabled layer <NUM>. As described above, the touch-enabled layer <NUM> includes a capacitive mesh for detecting user touch interactions.

Instructions to detect gesture (<NUM>) represent program instructions that when executed by the controller <NUM> cause the image capture device <NUM> to detect gestures from the user touch interaction on the touch-enabled layer <NUM>. As an example, the controller <NUM> determines the complexity of the gesture that may be used to engage and disengage the shutter <NUM> of the image capture device <NUM>.

Instructions to engage/disengage shutter (<NUM>) represent program instructions that when executed by the controller <NUM> cause the image capture device <NUM> to cycle between engaging the shutter <NUM> to cover the image sensor and disengaging the shutter <NUM> to expose the image sensor, based on whether the gesture is of a first type or second type. For example, a gesture of a first type, such as a tap on the touch-enabled layer <NUM>, may engage the shutter <NUM>. Similarly, if the user desires to later disengage the shutter, in order to make use of the image capture device <NUM>, a gesture of a second type, such as a swipe, may disengage the shutter. However, the gestures for engaging and disengaging the shutter <NUM> may vary. In addition, the first and second gestures may be the same, where each time the gesture is performed, the shutter <NUM> alternates between engaging and disengaging, to switch between covering and exposing the image sensor of the image capture device <NUM>. As mentioned above, if a gesture is of a type besides the first type or the second type, the gesture may be ignored.

Memory device <NUM> represents generally any number of memory components capable of storing instructions that can be executed by controller <NUM>. Memory device <NUM> is non-transitory in the sense that it does not encompass a transitory signal but instead is made up of at least one memory component configured to store the relevant instructions. As a result, the memory device <NUM> may be a non-transitory computer-readable storage medium.

<FIG> is a flow diagram <NUM> of steps taken by an image capture device to implement a method for cycling between engaging and disengaging a shutter to cover and expose an image sensor of the image capture device, according to an example. Although the flow diagram of <FIG> shows a specific order of execution, the order of execution may differ from that which is depicted. For example, the order of execution of two or more blocks or arrows may be scrambled relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention.

At <NUM>, the image capture device registers a user touch interaction with a touch-enabled layer disposed above the image sensor of the image capture device. At <NUM>, the image capture device detects a gesture from the user touch interaction. As described above, gestures of varying degrees of complexity may be used.

At <NUM>, the image capture device cycles between engaging the shutter to cover the image sensor and disengaging the shutter to expose the image sensor, based on whether the gesture is of a first type or a second type. As an example of being intuitive, natural user interactions may cycle between engaging and disengaging privacy solutions for the image capture device, such as the shutter. For example, referring to an image capture device on a computing device (e.g., webcam), if a user desires to engage the shutter to cover the image sensor of the image capture device, a gesture of the first type, such as a tap on the touch-enabled layer of the image capture device, may engage the shutter. Similarly, if the user desires to later disengage the shutter, in order to make use of the image capture device, a gesture of the second type, such as a swipe (or long press) on the touch-enabled layer of the image capture device, may disengage the shutter.

Claim 1:
An image capture device (<NUM>, <NUM>) comprising:
an image sensor (<NUM>);
a privacy solution comprising a shutter (<NUM>);
a touch-enabled layer (<NUM>) disposed above the image sensor (<NUM>); and
a controller (<NUM>) to:
register a user touch interaction with the touch-enabled layer (<NUM>); and
based on a gesture detected from the user touch interaction, cycle between engaging the shutter (<NUM>) to cover the image sensor (<NUM>) and disengaging the shutter (<NUM>) to expose the image sensor (<NUM>), wherein when the controller (<NUM>) detects a first type of gesture from the user touch interaction, the controller (<NUM>) is to engage the shutter (<NUM>) to cover the image sensor (<NUM>) and when the controller (<NUM>) detects a second type of gesture different from the first gesture, the controller (<NUM>) is to disengage the shutter (<NUM>) to expose the image sensor (<NUM>).