System and method for capturing audio or video data

[0001] This application is a continuation of U.S. patent application Ser. No. 15/378,710, filed on Dec. 14, 2016, which claims benefit to U.S. Provisional Patent Application No. 62/271,057, filed Dec. 22, 2015, the entirety of all of which are hereby incorporated by reference herein.

[0002] The recording of personally significant events through video and/or audio recording devices is a common occurrence. Typically, recordings of organized events, such as a surprise party or a piano recital, may be planned for in advance and the recording devices prepared ahead of time for the best position and amount of recording media appropriate for the event. However, many everyday events tend not to take place on a schedule or begin on command. Also, the significance of a given event may not be recognized until after that event has already started to unfold. To keep track of everything that happens to or around a person on a given day, one could carry camera and attempt to bring that camera out quickly to capture a particular moment or event. Taking out the recording device too late or the recording device being at a location just out of reach is a common issue with spontaneous events. Alternatively, a recording device may be positioned at a location that seems likely to capture interesting events and left on continuously during the hours that something of interest might occur. This latter approach to capturing more spontaneous events may run into the problem of not having the recording device in quite the right location and the expense of the large amounts of recording media needed or large amount of time needed to manually review the unattended recording.

[0003] According to one aspect, a video recording apparatus is disclosed. The video recording apparatus may comprise a video recorder configured to record video data, a memory configured to store the video data, and a processor in communication with the memory. The processor may be configured to control storage of the video data in a video segment on the memory, determine whether a trigger event is detected during storage of the video data in the video segment, and in response to detecting the trigger event during storage of the video data in the video segment, flag at least a portion of the video segment for preservation, and implement a trigger event protocol.

[0004] According to another aspect, a method for recording continuous video segments is disclosed. The method may comprise controlling a video recorder to record video data, and controlling a processor to store the video data in a video segment on a memory, determine whether a trigger event is detected during storage of the video data in the video segment, and in response to detecting the trigger event during storage of the video data in the video segment, flag at least a portion of the video segment for preservation and implement a trigger event protocol.

[0017] The methods, devices, and systems discussed below may be embodied in a number of different forms. Not all of the depicted components may be required, however, and some implementations may include additional, different, or fewer components from those expressly described in this disclosure. Variations in the arrangement and type of the components may be made without departing from the spirit or scope of the claims as set forth herein.

[0018] In order to capture spontaneous events without the distraction of manually handling a camera, and without the risk of missing the beginning of an event, a wearable recording device is disclosed. According to some embodiments, the wearable recording device is a pair of glasses including a digital video recording component for recording events and objects from the user's point of view through the glasses. The wearable glasses embodiment is advantageous for recording events and objects from the user's own viewing field. In other words, events that are viewable by the user may be recorded by the digital video recording component of the wearable glasses. According to other embodiments, the wearable recording device may be attached to other locations on the user's body to enable the digital video recording component to record events and objects surrounding the user.

[0019] FIG. 1 illustrates a wearable recording device 100 that may, for example, take the form of eye wear configured to be worn over a user's eyes (for example, Google® glasses). The wearable recording device 100 may include any combination of the components illustrated in FIG. 1, including arm portions 101, a computing system 102, a display unit 103, a camera unit 104, and lenses 105. The components of wearable recording device 100 may include one or more components described in computer 700 illustrated in FIG. 7, as will be described in further detail below.

[0020] The components of wearable recording device 100 may be integrated into wearable recording device 100, or may be discrete elements removably attached to wearable recording device 100. The electrical components of wearable recording device 100 (e.g., computing system 102, display unit 103, and camera unit 104) may be configured to communicate with each other via wired or wireless communication protocols.

[0021] In particular, arm portions 101 may be configured to wrap, at least in part, around a user's ears. Computing system 102 may include one or more components described in computer 700 illustrated in FIG. 7. For example, computing system 102 may include a memory configured to store instructions, a processor configured to execute the instructions stored on the memory to implement one or more processes described herein, a network interface for communicating with other electronic devices within a network, and one or more input devices such as a scroll wheel, button(s), or touchpad for receiving user inputs. Display unit 103 may display or project information within the user's field of view. Lenses 105 may be prescription or non-prescription lenses made out of glass or a plastic based polymer, and allows the user to focus on objects (e.g. object 110) within the user's field of view. And camera unit 104 may capture image data within camera unit 104's field of view 120. The image data captured by camera unit 104 may include digital images and/or digital video. Images captured by camera unit 104 may include most, if not all, of the user's field of view through lenses 105. For example, camera unit 104 may capture image(s) of object 110 within camera unit 104's field of view. Digital image(s) and digital video(s) recorded by camera unit 104 may be stored in a memory of computing system 102.

[0022] Camera unit 104 may support capture of image data digitally, in analog, and/or according to any number of lossy or lossless image or video formats, such as Joint Photographic Experts Group (jpeg or jpg), Tagged Image File Format (tiff), Portable Network Graphics (png), Graphics Interchange Format (gif), Moving Picture Experts Group (mpeg, mpeg-2), or any other image or video file format. Camera unit 104 may also support capture image data for various forms of image, such as ultra-violet images, infrared images, night vision, thermal scans, and more.

[0023] Referring to FIG. 2, wearable recording device 100 may be in wireless communication with other wearable and/or portable devices to form a local user-based network system 200. The user-based network system 200 illustrated in FIG. 2 includes wearable recording device 100, smart watch 210, and smart phone 220. Each of the devices within user-based network system 200 may communicate with each other either directly or indirectly via another device within the user-based network system 200. Each of the devices within user-based network system 200 may also communicate with secure server 240, either directly or indirectly through another device within the user-based network system 200, via network 230.

[0024] Smart watch 210 may be configured to support wireless communication (e.g. cellular, Wi-Fi, Bluetooth, NFC, etc.) capabilities and data processing and memory abilities. The components of smart watch 210 may include one or more components described in computer 700 illustrated in FIG. 7. For example, smart watch 210 may include a camera, display, accelerometer, gyroscope, and one or more biometric sensors for sensing a biometric reading of the user (e.g., user's body temperature, user's heartbeat, etc.). A more detailed description of the components that may comprise smart watch 210 is provided below with reference to FIG. 7. When communication between wearable recording device 100 and smart watch 210 is established, wearable recording device 100 may receive data obtained by smart watch 210. For example, digital images or digital videos recorded by smart watch 210 may be transmitted to wearable recording device 100 and stored on a memory of wearable recording device 100. Wearable recording device 100 may also receive information obtained by smart watch 210 such as audio information obtained through a microphone on smart watch 210, acceleration information sensed by the accelerometer on smart watch 210, orientation information sensed by the gyroscope of the smart watch 210, or biometric information sensed by biometric sensors on smart watch 210.

[0025] Smart phone 220 may be configured to support wireless communication (e.g. cellular, Wi-Fi, Bluetooth, NFC, etc.) capabilities and data processing and memory abilities. The components of smart phone 220 may include one or more components described in computer 700 illustrated in FIG. 7. For example, smart phone 220 may include a camera, display, accelerometer, gyroscope, and one or more biometric sensors for sensing a biometric reading of the user (e.g., user's body temperature, user's heartbeat, etc.). A more detailed description of the components that may comprise smart phone 220 is provided below with reference to FIG. 7. When communication between wearable recording device 100 and smart phone 220 is established, wearable recording device 100 may receive data obtained by smart phone 220. For example, digital images or digital videos recorded by smart phone 220 may be transmitted to wearable recording device 100 and stored on a memory of wearable recording device 100. Wearable recording device 100 may also receive information obtained by smart phone 220 such as audio information obtained through a microphone on smart phone 220, acceleration information sensed by the accelerometer on smart phone 220, orientation information sensed by the gyroscope of the smart phone 220, or biometric information sensed by biometric sensors on smart phone 220.

[0026] When communication between wearable recording device 100 and secure server 240 is established via network 230, data being captured or received by wearable recording device may be uploaded to secure server 240 to be stored on a memory of secure server 240. For example, digital video recorded by camera unit 104 may be uploaded to secure serve 240 and stored on a memory of secure server 240. The components of secure server 240 may include one or more components described in the computer 700 illustrated in FIG. 7.

[0027] Communication between devices within the user-based network system 200 may be through any of a number of standard wireless communication protocols. For example, Bluetooth communication, RF communication, NFC communication, telecommunication network communication, or any other wireless mechanism may be used.

[0028] As described in greater detail below, the present disclosure describes wearable recording device 100 that supports real-time recording of objects and events occurring with a user's field of view. In order to maximize limited on-board memory storage capabilities, a data storage strategy is disclosed that allows for recording continuous video segments by utilizing data overwriting strategies to overwrite previously recorded video segments. However, the disclosure further discloses a data storage strategy that detects specific trigger events (e.g., sounds, objects, facial recognition, biometric readings, acceleration readings, orientation readings) during the recording of a video segment that may cause the video segment to be stored separately and saved from the overwriting feature. This allows for the smart conservation of memory and storage of video segments that may include significant events that warrant longer term data storage.

[0029] The video recording strategies, data storing strategies, and other related processes described herein may be implemented by a data storage strategy tool. The data storage strategy tool may be, for example, software, hardware, firmware, or some combination thereof, running on one or more of the devices that comprise the user-based network system 200 or secure server 240.

[0030] FIG. 3 illustrates a timeline 300 describing a baseline data storage strategy for storing video segment recordings within a dedicated memory space. For purposes of describing the timeline 300, reference will be made to a video segment recorded by camera unit 104 of wearable recording device 100. Timeline 300 further assumes the video segment is stored on a memory of wearable recording device 100. However, it is within the scope of this disclosure for the video segment recordings to have been recorded by a camera unit of smart watch 210, a camera unit of smart phone 220, or a camera unit of another device having established communication with wearable recording device 100. In such embodiments, the video segment recordings may then be transmitted to wearable recording device 100 for viewing through display unit 103. It is also within the scope of this disclosure for the video segment recordings to be stored on another device in communication with wearable recording device 100 such as, for example, a memory of secured server 240, a memory of smart watch 210, or a memory of smart phone 220.

[0031] Referring back to timeline 300 illustrated in FIG. 3, data storage strategy tool may control the storage of continuously recorded video segments over a dedicated portion in memory such as a first data block 1 and a second data block 2. It follows that a first video segment 1 recording events occurring during a first time period T1 lasting from time t₁ to t₂, may be stored within a first data block 1. A subsequent second video segment 2 recording events occurring during a second time period T2 lasting from time t₂ to t₃, may be stored within a second data block 2, where second data block 2 is different from first data block 1.

[0032] A subsequent third video segment 3 recording events occurring during a third time period T3 lasting from time t₃ to t₄, may be stored to overwrite all, or substantially all, of the first video segment 1 by storing the third video segment 3 over first data block 1. Similarly, a subsequent fourth video segment 4 recording events occurring during a fourth time period T4 lasting from time t₄ to t₅, may be stored to overwrite all, or substantially all, of the second video segment 2 by storing the fourth video segment 4 over second data block 2. In this way, the data storage strategy tool is configured to overwrite previously recorded video segments as a strategy for efficiently conserving limited memory storage space. For example, due to the limits of on-board memory available on wearable recording device 100, without a data storage strategy that includes overwriting previously recorded video segments, the ability to continuously record video segments will be severely limited.

[0033] So with the data storage strategy described by timeline 300, video segments may continue to be recorded and stored, for at least a known period of time before it is overwritten. This enables the continuous recording of events occurring within the field of view of camera unit 104 while also limiting the memory dedicated to the storage of such video recording to a fixed (i.e., known) limit.

[0034] Each of the time periods T1-T4 may be designed to last the same length of time. For example, one or more of time periods T1-T4 may last for 15 minutes or some other predetermined length of time. Further, although timeline 300 is described to repeat the memory overwriting cycle to every two subsequent time periods, the data storage strategy tool may be configured to repeat the memory overwriting cycle according to other intervals. For example, the data storage strategy tool may control the memory overwriting cycle so that each subsequent video recording segment is stored to overwrite the previously recorded video segment.

[0035] The data storage strategy described by timeline 300 may be desirable and effective for continuously recording video segments that do not include a significant event that may be considered for more permanent storage. However, when a significant event (e.g., a predetermined trigger event) is detected during the recording of a video segment, a different data overwriting strategy may be desirable. Accordingly, the identification of a trigger event may initiate the data storage strategy tool to implement a trigger event protocol that may, for example, separately save a video segment lasting a predetermined length of time prior to the triggering event and/or lasting a predetermined length of time following the triggering event. In addition or alternatively, the identification of a triggering event may initiate the data storage strategy tool to continue recording the video segment past a default time period until a subsequent trigger event is detected. The timelines illustrated in FIGS. 4A-4C describe such data storage strategies that utilize data overwriting strategies that allow for separately storing video segments that include detected trigger events.

[0036] FIG. 4A illustrates a timeline 410 describing a first data storage strategy implemented by the data storage strategy tool when a trigger event is detected while recording a video segment. The trigger event may be a predetermined sound or voice command recognized by a speech recognition device operated by the data storage strategy tool, a predetermined object recognized by a video recognition device operated by the data storage strategy tool, a predetermined person recognized by a facial recognition device operated by the data storage strategy tool, a predetermined gesture command recognized by a video recognition device operated by the data storage strategy tool, a predetermined user input command received via an input device and recognized by the data storage strategy tool, a predetermined acceleration measurement measured by an accelerometer and recognized by the data storage strategy tool, a predetermined orientation measurement detected by a gyroscope and recognized by the data storage strategy tool, a user's biometric reading obtained by one or more biometric sensors and recognized by the data storage strategy tool, or some other trigger event that may be detected by the data storage strategy tool from the current video segment being recorded. The detection of the trigger event may be accomplished by the data storage strategy tool running on the wearable recording device 100. Alternatively, the detection of the trigger event may be accomplished by the data storage strategy tool running, at least in part, on another device in communication with the wearable recording device 100 (e.g., smart watch 210, smart phone 220, or secure server 240).

[0037] According to the first data storage strategy, after a trigger event is detected, the data storage strategy tool may automatically save a first video portion lasting a first predetermined length of time prior to the trigger event. In addition or alternatively, after the trigger event is detected, the data storage strategy tool may automatically save a second video portion lasting a second predetermined length of time following the trigger event. The first predetermined length of time may be equal to the second predetermined length of time (e.g., 7.5 minutes). Alternatively, the first predetermined length of time may be different from the second length of time.

[0038] According to timeline 410, a first video segment 1 may be recorded to capture events occurring during a first time period T1 lasting from time t₁ to t₂. As illustrated in timeline 410, a trigger event is not detected during recording of the first video segment 1 during the first time period T1. Therefore, the data storage strategy tool controls storage of the first video segment 1 into a first data block 1.

[0039] Following storage of the first video segment 1 into first data block 1, the data storage strategy tool commences recording a second video segment 2 starting at time t₂. During the recording of the second video segment 2, a trigger event may be detected at time t₃. According to the first data storage strategy, the detection of the trigger event at time t₃ may automatically initiate the data storage strategy tool to save a first video portion of previously recorded video content that goes back a first predetermined length of time from the trigger event detection time at t₃. In addition or alternatively, according to the first data storage strategy the detection of the trigger event at time t₃ may also initiate the data storage strategy tool to continuing storing video content (i.e., a second video portion) following the detection of the trigger event at time t₃ for a second predetermined length of time. Timeline 410 illustrates the first predetermined length of time lasting from time t₂ to time t₃, and the second predetermined length of time lasting from time t₃ to time t₅. In the embodiment illustrated by timeline 410, the first predetermined time length is equal to the second predetermined time length. However, in alternative embodiments the first predetermined time length may be different from the second predetermined time length, where the first predetermined time length may be longer or shorter than the second predetermined time length.

[0040] So whereas the second video segment 2 may have lasted from time t₂ to time t₄ under the baseline data storage strategy described in timeline 300, because the trigger event was detected during the second time period T2 at time t₃ in timeline 410, the second video segment 2 is recorded from time t₂ to time t₅ according to the first data storage strategy. The combination of the first video portion (lasting from time t₂ to time t₃ prior to the trigger event) and the second video portion (lasting from time t₃ to time t₅ following the trigger event) may then be stored as second video segment 2 (i.e., trigger event video segment) into data block 2. Alternatively, according to some embodiments the first video portion may be stored as the second video segment 2 into data block 2. Alternatively, according to some embodiments the second video portion may be stored as the second video segment 2 into data block 2.

[0041] A subsequent third video segment 3 may be recorded to capture events occurring during a third time period T3 lasting from time t₅ to t₆. The data storage strategy tool allows the third video segment 3 to overwrite all, or substantially all, of the first video segment 1 by storing the third video segment 3 over first data block 1. The data storage strategy tool allows for first video segment 1 to be overwritten in first data block 1 because a trigger event was not detected in first video segment 1.

[0042] A subsequent fourth video segment 4 may be recorded to capture events occurring during a fourth time period T4 lasting from time t₆ to t₇. Whereas under the baseline data storage strategy described in timeline 300 the fourth video segment 4 was stored to overwrite second video segment 2 in second data block 2, because the trigger event was detected during the recording of the second video segment 2 in timeline 410, the data storage strategy tool will not overwrite the second video segment 2 in data block 2. Rather, the data storage strategy tool controls storage of the fourth video segment 4 into a third data block 3, where the third data block 3 may be different from the first data block 1 and/or second data block 2. In this way, the second video segment 2 including the trigger event will be saved from overwriting and preserved until a later action to overwrite it is taken.

[0043] FIG. 4B illustrates a timeline 420 describing a second data storage strategy implemented by the data storage strategy tool when a trigger event is detected while recording a video segment. The trigger event may be any one or more of the trigger events described herein.

[0044] According to the second data storage strategy, after a trigger event is detected, the data storage strategy tool may automatically save a first video portion lasting a first predetermined length of time prior to the trigger event. In addition or alternatively, after the trigger event is detected, the data storage strategy tool may automatically save a second video portion lasting a second predetermined length of time following the trigger event. The first predetermined length of time may be equal to the second predetermined length of time (e.g., 10 minutes). Alternatively, the first predetermined length of time may be different from the second length of time.

[0045] According to timeline 420, a first video segment 1 may be recorded to capture events occurring during a first time period T1 lasting from time t₁ to t₂. As illustrated in timeline 420, a trigger event is not detected during recording of the first video segment 1 during the first time period T1. Therefore, the data storage strategy tool controls storage of the first video segment 1 into a first data block 1.

[0046] Following storage of the first video segment 1 into first data block 1, the data storage strategy tool commences recording of a second video segment 2 starting at time t₂. During the recording of the second video segment 2, a trigger event may be detected at time t₃. According to the first data storage strategy, the detection of the trigger event at time t₃ may automatically initiate the data storage strategy tool to save a first video portion of previously recorded video content that goes back a first predetermined length of time from the trigger event detection time at t₃. In addition or alternatively, according to the first data storage strategy, the detection of the trigger event at time t₃ may also automatically initiate the data storage strategy tool to continuing storing video content (i.e., a second video portion) following the detection of the trigger event at time t₃ for a second predetermined length of time. Timeline 420 illustrates the first predetermined length of time lasting from time t_1-2 to time t₃, where time t_1-2 extends back into the first time period T1. The second predetermined length of time lasts from time t₃ to time t₅. In the embodiment illustrated by timeline 420 the first predetermined time length is equal to the second predetermined time length. However, in alternative embodiments the first predetermined time length may be different from the second predetermined time length, where the first predetermined time length may be longer or shorter than the second predetermined time length.

[0047] So whereas the second video segment 2 may have lasted from time t₂ to time t₄ under the baseline data storage strategy described in timeline 300, because the trigger event was detected during the second time period T2 at time t₃ in timeline 420, the second video segment 2 is recorded from time t_1-2 to time t₅ according to the second data storage strategy. The combination of the first video portion (lasting from time t_1-2 to time t₃ prior to the trigger event) and the second video portion (lasting from time t₃ to time t₅ following the trigger event) may then be stored as second video segment 2 (i.e., trigger event video segment 2) into data block 2. Alternatively, according to some embodiments the first video portion may be stored as the second video segment 2 into data block 2. Alternatively, according to some embodiments the second video portion may be stored as the second video segment 2 into data block 2.

[0048] A subsequent third video segment 3 may be recorded to capture events occurring during a third time period T3 lasting from time t₅ to t₆. The data storage strategy tool controls the storage of the third video segment 3 into a third data block 3. The third data block 3 may include portions of the first data block 1 that wasn't utilized to store portions of the second video segment (i.e., video segment where a trigger event was identified) as well as any additional data block portions to allow for storage of the third video segment 3. It follows that the data storage strategy tool allows the third video segment 3 to overwrite portions of the first video segment 1 that were not saved as part of the second video segment 2.

[0049] A subsequent fourth video segment 4 may be recorded to capture events occurring during a fourth time period T4 lasting from time t₆ to t₇. Whereas under the baseline data storage strategy described in timeline 300 the fourth video segment 4 was stored to overwrite second video segment 2 in second data block 2, because the trigger event was detected during recording of the second video segment 2 in timeline 420, the data storage strategy tool will not overwrite the second video segment 2 in data block 2. Rather, the data storage strategy tool controls storage of the fourth video segment 4 into a fourth data block 4, where the fourth data block 4 may be different from the first data block 1, second data block 2, and/or third data block 3.

[0050] FIG. 4C illustrates a timeline 430 describing a third data storage strategy implemented by the data storage strategy tool when a trigger event is detected while recording a video segment. The trigger event may be any one or more of the trigger events described herein.

[0051] According to the third data storage strategy, after a trigger event is detected, the data storage strategy tool may automatically save a first video portion lasting a first predetermined length of time prior to the trigger event. In addition or alternatively, after the trigger event is detected, the data storage strategy tool may automatically save a second video portion lasting from the trigger event at time t₃ until a subsequent trigger event is detected. The subsequent trigger event may be a predetermined sound or voice command recognized by a speech recognition device operated by the data storage strategy tool, a predetermined object recognized by a video recognition device operated by the data storage strategy tool, a predetermined person recognized by a facial recognition device operated by the data storage strategy tool, a predetermined gesture command recognized by a video recognition device operated by the data storage strategy tool, a predetermined user input command received via an input device and recognized by the data storage strategy tool, a predetermined acceleration measurement measured by an accelerometer and recognized by the data storage strategy tool, a predetermined orientation measurement detected by a gyroscope and recognized by the data storage strategy tool, a user's biometric reading obtained by one or more biometric sensors and recognized by the data storage strategy tool, or some other trigger event that may be detected by the data storage strategy tool from the current video segment being recorded. The detection of the subsequent trigger event may be accomplished by the data storage strategy tool running on the wearable recording device 100. Alternatively, the detection of the subsequent trigger event may be accomplished by the data storage strategy tool running, at least in part, on another device in communication with the wearable recording device 100 (e.g., smart watch 210, smart phone 220, or secure server 240).

[0052] According to timeline 430, a first video segment 1 may be recorded to capture events occurring during a first time period T1 lasting from time t₁ to t₂. As illustrated in timeline 430, a trigger event is not detected during recording of the first video segment 1. Therefore, the data storage strategy tool may control storage of the first video segment 1 into a first data block 1.

[0053] Following storage of the first video segment 1 into first data block 1, the data storage strategy tool commences recording a second video segment 2 starting at time t₂. During the recording of the second video segment 2, a trigger event may be detected at time t₃. According to the third data storage strategy, the detection of the trigger event at time t₃ may automatically initiate the data storage strategy tool to save a first video portion of previously recorded video content that goes back a first predetermined length of time from the trigger event detection time at t₃. In addition or alternatively, according to the third data storage strategy, the detection of the trigger event at time t₃ may also automatically initiate the data storage strategy tool to continuing storing video content (i.e., a second video portion) following the detection of the trigger event at time t₃ until a subsequent trigger event is identified. Timeline 430 illustrates the first predetermined length of time lasting from time t₂ to time t₃. Timeline 430 also illustrates the recording of the second video portion from the time of the trigger event detection at time t₃ and continuing until a subsequent trigger event is detected at time t₅. The subsequent trigger event may be any one or more of the subsequent trigger events described herein.

[0054] So whereas the second video segment 2 may have lasted from time t₂ to time t₄ under the baseline data storage strategy described in timeline 300, because the trigger event was detected during the second time period T2 at time t₃ in timeline 430, the data storage strategy tool's implementation of the third data storage strategy results in the second video segment 2 being recorded from time t₂ until the subsequent trigger event is detected at time t₅. The combination of the first video portion (lasting from time t₂ to time t₃ prior to the trigger event) and the second video portion (lasting from time t₃ to time t₅ following the trigger event) may then be stored as second video segment 2 (i.e., trigger event video segment) into data block 2. Alternatively, according to some embodiments the first video portion may be stored as the second video segment 2 into data block 2. Alternatively, according to some embodiments the second video portion may be stored as the second video segment 2 into data block 2.

[0055] A subsequent third video segment 3 may be recorded to capture events occurring during a third time period T3 lasting from time t₅ to t₆. The data storage strategy tool allows the third video segment 3 to overwrite all, or substantially all, of the first video segment 1 by storing the third video segment 3 over first data block 1. The data storage strategy tool allows for first video segment 1 to be overwritten in first data block 1 because a trigger event was not detected in first video segment 1.

[0056] FIG. 5 illustrates flowchart 500 describing a data storage strategy process implemented by, for example, the data storage strategy tool described herein.

[0057] At 501, the data storage strategy tool may control recording to a first video segment into a first data block. The recording of the first video segment may correspond to any one of the processes for recording a first video segment described herein.

[0058] At 502, the data storage strategy tool determines whether a trigger event is detected during the recording of the first video segment. The detection of the trigger event may correspond to any of the processes for detecting a trigger event described herein. More particularly, 502 may include detecting a user input to the wearable recording device 100, and recognizing the manual input as a manual trigger event for identifying the trigger event. For example, during recoding of the first video segment, a user may input a command into wearable recording device 100 signaling that a trigger event has been manually detected.

[0059] In addition or alternatively, 502 may include detecting an object or person from the first video segment, and recognizing the detected object or person as a predetermined trigger event. For example, the user's child may be recognized during recoding of the first video segment, where the recognition of the user's child within a recorded video segment is known to be a predetermined trigger event. Similarly, a specific object such as a birthday cake or famous landmark may be recognized during recording of the first video segment, where recognition of special object within a recorded video segment is known to be a predetermined trigger event.

[0060] In addition or alternatively, 502 may include detecting an audible user command or sound, and recognizing the audible user command or sound as a predetermined trigger event. For example, a specific audible command such as “trigger event detected” from the user may be detected and recognized as a predetermined command for identifying a trigger event. In addition, a specific sound such as tires screeching, a baby's cry, a gunshot, or sirens may be detected and recognized as a predetermined trigger event.

[0061] In addition or alternatively, 502 may include detecting an acceleration, deceleration, and/or orientation measurement of wearable recording device 100 (or another device in communication with wearable recording device 100 as described herein), and recognizing the acceleration, deceleration, and/or orientation measurement as a predetermined trigger event. For example, detection of a sudden acceleration or deceleration may correspond to a traffic accident scenario, and therefore detection of a sudden acceleration or declaration may be recognized as a predetermined trigger event. In addition, a prolonged stillness (i.e., lack of acceleration, lack of deceleration, or no change in orientation) may correspond to a health issue where the user cannot move, and therefore detection of a prolonged stillness may be recognized as a predetermined trigger event.

[0062] In addition or alternatively, 502 may include detecting certain biometric levels and recognizing certain biometric levels as being predetermined trigger events. For example, if a high heartbeat is measured this may correspond to the user being in a stressful, or even dangerous situation. Therefore, the detection of certain biometric measurements that are known as being harmful to the user may be recognized as predetermined trigger events.

[0063] If a trigger event is detected at 502, then at 503 the data storage strategy implements a trigger event protocol. The recognition of a trigger event indicates that the current video segment being recorded will be saved rather than made available for overwriting by a subsequent video segment recording. The trigger event protocol may correspond to any one of the data storage strategies (i.e., data overwriting strategies) initiated by the data storage strategy based on the detection of a trigger event described herein.

[0064] In addition to the trigger event protocol, according to some embodiments an additional action may be implemented by the data storage strategy tool based on the type of trigger event that is recognized. For example, if the trigger event corresponds to a traffic accident scenario (e.g., sudden increase in acceleration or sudden deceleration), the data storage strategy tool may additionally control smart phone 220 to call a predetermined number (e.g., emergency contact identified in smart phone 220, known emergency services number). As another example, if the trigger event corresponds to a potentially harmful situation for the user, the data storage strategy tool may additionally control smart phone 220 to call a predetermined number (e.g., emergency contact identified in smart phone 220, known emergency services number) and/or control wearable recording device 100 to transmit the first video segment including the recognized trigger event to emergency services.

[0065] In addition to the trigger event protocol, according to some embodiments an additional action may be implemented by the data storage strategy tool based on the detection of the trigger event. For example, the detection of the trigger event may cause the data storage strategy tool to begin uploading or saving video data to a new remote system and/or database.

[0066] If a trigger event is not detected at 502, then at 504 the data storage strategy continues to record the first video segment.

[0067] At 505, the data storage strategy tool determines whether a recording period for the first video segment has ended. If it is determined that the recording period for the first video segment has ended, then at 506 the data storage strategy tool controls the recording of a second video segment. If it is determined that the recording period for the first video segment has not ended, then the data storage strategy tool may revert back to 502 to again determine whether a trigger event has occurred during the recording of the first video segment.

[0068] At 507, the data storage strategy tool determines whether a trigger event is detected during the recording of the second video segment. The detection of the trigger event may correspond to any of the processes for detecting a trigger event described herein.

[0069] If a trigger event is detected at 507, then at 508 the data storage strategy implements a trigger event protocol. The trigger event protocol may correspond to any one of the data storage strategies initiated by the data storage strategy based on the detection of a trigger event described herein.

[0070] If a trigger event is not detected at 507, then at 509 the data storage strategy continues to record the second video segment.

[0071] At 510, the data storage strategy tool determines whether a recording period for the second video segment has ended. If it is determined that the recording period for the second video segment has ended, then at 511 the data storage strategy tool controls the recording of a third video segment to overlap the first video segment, or some other previously recorded video segment. Controlling the recording of the third video segment to overlap a previously recorded video segment may correspond to any one of the data storage strategies (i.e., data overwriting strategies) initiated by the data storage strategy tool based on the detected of a trigger event described herein.

[0072] If it is determined that the recording period for the second video segment has not ended, then the data storage strategy tool may revert back to 507 to again determine whether a trigger event has occurred during the recording of the second video segment.

[0073] According to some embodiments, certain trigger events may be recognized as a command to cease recording of the current video segment being recorded, and/or deleting the current video segment being recording. For example, if an input prompt that asks for personal or private information (e.g., personal identification number (PIN), social security number, passwords, documents labeled as being confidential) is detected from the current video segment being recorded by a video recognition device, the data storage strategy tool may recognize this as a predetermined trigger event for ceasing the recording of the current video segment and/or deleting the current video segment recording. It follows that the recognition of such a predetermined trigger event will cause the data storage strategy tool to implement a trigger event protocol that ceases the recording of the current video segment and/or deletes the current video segment recording.

[0074] In addition, the user's location may be tracked via the wearable recording device 100 (or another device in communication with the wearable recording device), such that the detection of the user at certain predetermined locations (e.g., banks or other financial institutions) may be recognized by the data storage strategy tool as a trigger event for ceases the recording of the current video segment and/or deletes the current video segment recording.

[0075] In addition, facial recognition of certain predetermined people, or the audible recognition of certain people, may be recognized by the data storage strategy tool as a trigger event for ceases the recording of the current video segment and/or deletes the current video segment recording.

[0076] FIG. 6A illustrates a flowchart 600 that describes a trigger event protocol implemented, for example, at 503 and/or 508 in the process described by flowchart 500 in FIG. 5. The trigger event protocol described by flowchart 600 may be implemented by, for example, the data storage strategy tool described herein.

[0077] At 601, the data storage strategy tool may save a first video portion going back a first predetermined time period prior to the detection of a trigger event. The first video portion may go back into a previously recorded video segment, or the first video portion may go back to a time within the video segment currently being recorded.

[0078] At 602, the data storage strategy tool may continue to record and save a second video portion starting from the time when the trigger event was detected. The second video portion may continue to record for a second predetermined time period following the detection of the trigger event.

[0079] At 603, the data storage strategy tool may save the first video portion and the second video portion as a trigger event video segment. The data storage strategy tool may further control a data storage strategy to prevent future video segment recordings from overwriting the trigger event video segment for at least a predetermined time period or until a user provides instructions allowing for the overwriting of the trigger event video segment.

[0080] At 604, the data storage strategy tool may commence recording subsequent video segments according to any of the data storage strategies described herein.

[0081] FIG. 6B illustrates a flowchart 610 that describes a trigger event protocol implemented, for example, at 503 and/or 508 in the process described by flowchart 500 in FIG. 5. The trigger event protocol described by flowchart 610 may be implemented by, for example, the data storage strategy tool described herein.

[0082] At 611, the data storage strategy tool may save a first video portion going back a predetermined time period prior to the detection of a trigger event. The first video portion may go back into a previously recorded video segment, or the first video portion may go back to a time within the video segment currently being recorded.

[0083] At 612, the data storage strategy tool may continue to record and save a second video portion starting from the time when the trigger event was detected. The second video portion may continue recording until a subsequent trigger event signifying the end to the significant event corresponding to the initial trigger event is detected.

[0084] So at 613, the data storage strategy tool determines whether the subsequent trigger event is detected. If the subsequent trigger event is detected, then at 614 the data storage strategy tool ceases recording the second video portion. However, if the subsequent trigger event is not detected, the data storage strategy tool may revert back to 612 and continue recording the second video portion.

[0085] At 615, the data storage strategy tool may save the first video portion and the second video portion as a trigger event video segment. The data storage strategy tool may further control a data storage strategy to prevent future video segment recordings from overwriting the trigger event video segment for at least a predetermined time period or until a user provides instructions allowing for the overwriting of the trigger event video segment.

[0086] At 616, the data storage strategy tool may commence recording subsequent video segments according to any of the data storage strategies described herein.

[0087] Although description has been provided for the data storage strategy tool controlling storage of video data (e.g., image and sound data), it is within the scope of this disclosure for the data storage strategy tool to control storage of additional data concurrently with the video data. For example, the data storage strategy tool may control storage of smell data, weather data, humidity data, gyroscope measurement data, and other sensor data obtained by sensors accessible by the data storage strategy tool according to any one or more of the data storage strategies described herein. Further, when the data storage strategy tool is configured to control the storage of video data and additional data, the data storage strategy tool may select which data to store and which data not to store in accordance to any one or more of the data storage strategies described herein.

[0088] Referring to FIG. 7, a block diagram is illustrated of an exemplary computer 700 configured to have an exemplary computer architecture in which embodiments and aspects of the wearable/portable/server devices described herein may be implemented. This computer 700 is only one example of a suitable computer architecture and is not intended to suggest any limitation as to the scope of use or functionality. Numerous other general purpose or special purpose computer architectures or configurations may be used. Examples of well known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, smart phones, tablet computers, personal computers (PCs), server computers, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputers, mainframe computers, embedded systems, distributed computing environments that include any of the above systems or devices, and the like.

[0089] In one implementation, the wearable recording device 100, smart watch 210, or smart phone 220 may communicate directly with the secure server 240. In other implementations, the wearable recording device 100, smart watch 210, or smart phone 220 may communicate with the secure server 240 only after downloading an authenticating software application or token from the secure server 240. Thus, computer-executable instructions, such as program modules, being executed by a processor or other computing capability on one or more of the devices illustrated in the system of FIG. 2 may be used to implement the features described herein. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular data types. Distributed computing environments may be used where tasks are performed by remote processing devices that are linked through a communications network or other data transmission medium. In a distributed computing environment, program modules and other data may be located in both local and remote computer storage media including memory storage devices.

[0090] With reference to FIG. 7, each wearable recording device 100, smart watch 210, smart phone 220, or secure server 240 may be represented by a combination of one or more components that comprise computer 700. Computer 700 includes a network work interface 720 that enables communication with other computers via a network 726, where network 726 may be represented by network 230 in FIG. 2. The computer 700 may include a processor 702, a main memory 704, a static memory 706, the network interface device 720, an output device 710 (e.g., a display or speaker), an input device 712, and a storage device 716, all connected via a bus 708.

[0091] The processor 702 represents a central processing unit of any type of architecture, such as a CISC (Complex Instruction Set Computing), RISC (Reduced Instruction Set Computing), VLIW (Very Long Instruction Word), or a hybrid architecture, although any appropriate processor may be used. The processor 702 executes instructions and includes portions of the computer 700 that control the operation of the entire computer 700. The processor 702 may also represent a controller that organizes data and program storage in memory and transfers data and other information between the various parts of the computer 700.

[0092] The processor 702 is configured to receive input data and/or user commands from the input device 712. The input device 712 may be a keyboard, mouse or other pointing device, trackball, scroll, button, touchpad, touch screen, keypad, microphone, speech recognition device, video recognition device, or any other appropriate mechanism for the user to input data to the computer 700 and control operation of the computer 700 and/or operation of the data storage strategy tool described herein. Although only one input device 712 is shown, in another embodiment any number and type of input devices may be included. For example, input device 712 may include an accelerometer, a gyroscope, and a global positioning system (GPS) transceiver.

[0093] The processor 702 may also communicate with other computers via the network 726 to receive instructions 724, where the processor may control the storage of such instructions 724 into any one or more of the main memory 704, such as random access memory (RAM), static memory 706, such as read only memory (ROM), and the storage device 716. The processor 702 may then read and execute the instructions 724 from any one or more of the main memory 704, static memory 706, or storage device 716. The instructions 724 may also be stored onto any one or more of the main memory 704, static memory 706, or storage device 716 through other sources. The instructions 724 may correspond to, for example, instructions that make up the data storage strategy tool described herein.

[0094] Although computer 700 is shown to contain only a single processor 702 and a single bus 708, the disclosed embodiment applies equally to computers that may have multiple processors and to computers that may have multiple busses with some or all performing different functions in different ways.

[0095] The storage device 716 represents one or more mechanisms for storing data. For example, the storage device 716 may include a computer readable medium 722 such as read-only memory (ROM), RAM, non-volatile storage media, optical storage media, flash memory devices, and/or other machine-readable media. In other embodiments, any appropriate type of storage device may be used. Although only one storage device 716 is shown, multiple storage devices and multiple types of storage devices may be present. Further, although the computer 700 is drawn to contain the storage device 716, it may be distributed across other computers, for example on a server.

[0096] The storage device 716 may include a controller (not shown) and a computer readable medium 722 having instructions 724 capable of being executed by the processor 702 to carry out the functions as previously described herein with reference to the data storage strategy tool. In another embodiment, some or all of the functions are carried out via hardware in lieu of a processor-based system. In one embodiment, the controller is a web browser, but in other embodiments the controller may be a database system, a file system, an electronic mail system, a media manager, an image manager, or may include any other functions capable of accessing data items. The storage device 716 may also contain additional software and data (not shown), which is not necessary to understand the other features.

[0097] Output device 710 is configured to present information to the user. For example, the output device 710 may be a display such as a liquid crystal display (LCD), a gas or plasma-based flat-panel display, or a traditional cathode-ray tube (CRT) display or other well-known type of display in the art of computer hardware. Accordingly, in some embodiments the output device 710 displays a user interface. In other embodiments, the output device 710 may be a speaker configured to output audible information to the user. In still other embodiments, any combination of output devices may be represented by the output device 710.

[0098] Network interface device 720 provides the computer 700 with connectivity to the network 726 through any suitable communications protocol. The network interface device 720 sends and/or receives data from the network 726 via a wireless or wired transceiver 714. The transceiver 714 may be a cellular frequency, radio frequency (RF), infrared (IR) or any of a number of known wireless or wired transmission systems capable of communicating with a network 726 or other computer device having some or all of the features of computer 700. Bus 708 may represent one or more busses, e.g., USB, PCI, ISA (Industry Standard Architecture), X-Bus, EISA (Extended Industry Standard Architecture), or any other appropriate bus and/or bridge (also called a bus controller).

[0099] Computer 700 may be implemented using any suitable hardware and/or software, such as a personal computer or other electronic computing device. In addition to the various types of wearable devices described herein, computer 700 may also be a portable computer, laptop, tablet or notebook computer, PDA, pocket computer, appliance, telephone, or mainframe computer. Network 726 may be any suitable network and may support any appropriate protocol suitable for communication to the computer 700. In an embodiment, network 726 may support wireless communications. In another embodiment, network 726 may support hard-wired communications, such as a telephone line or cable. In another embodiment, network 726 may support the Ethernet IEEE (Institute of Electrical and Electronics Engineers) 802.3x specification. In another embodiment, network 726 may be the Internet and may support IP (Internet Protocol). In another embodiment, network 726 may be a LAN or a WAN. In another embodiment, network 726 may be a hotspot service provider network. In another embodiment, network 726 may be an intranet. In another embodiment, network 726 may be a GPRS (General Packet Radio Service) network. In another embodiment, network 726 may be any appropriate cellular data network or cell-based radio network technology. In another embodiment, network 726 may be an IEEE 802.11 wireless network. In still another embodiment, network 726 may be any suitable network or combination of networks. Although one network 726 is shown, in other embodiments any number of networks (of the same or different types) may be present.

[0100] According to some embodiments, certain public use modes of the wearable recording device 100 in combination with at least one other wearable recording device 800 are disclosed. The wearable recording device 800 may include any combination of the components illustrated in FIG. 8, including arm portions 801, a computing system 802, a display unit 803, a camera unit 804, and lenses 805.

[0101] In the party event scenario illustrated in FIG. 8 (e.g., a wedding), wearable recording device 100 and wearable recording device 800 may be handed out to multiple attendees of the party event to record and automatically share aspects of the same event from multiple perspective offered by the different recording locations of the different attendees. With wearable recording device 100 recording the same event (e.g., same object 810) as wearable recording device 800 from different locations, the video segments recorded by wearable recording device 100 and wearable recording device 800 may be centrally gathered combined to provide a unique, or at least clearer, view of the event. Assuming that both wearable recording device 100 and wearable recording device 800 are in communication with secure server 240, video segments recorded by both wearable recording device 100 and wearable recording device 800 may be uploaded to secure server 240. Secure server 240 may then combine the received video segments to generate a new video recording that includes portions from both video segments recorded by wearable recording device 100 and wearable recording device 800.

[0102] Another public use mode available when multiple wearable recording devices are communicating with each other may include a 3D capability for later viewing an event in three dimensions by combining the multiple different perspective views recorded by at least three different wearable recording devices of a same event. This may be a post processing procedure implemented by secure server 240 after receiving video segment recordings from at least three different wearable recording devices.

[0103] Another public use mode available when multiple wearable recording devices are communicating with each other may include the ability of, for example, wearable recording device 100 being able to view video being recorded by wearable recording device 800. The video being recorded by wearable recording device 800 may be transmitted to wearable recording device 100 and displayed on display unit 103 of wearable recording device 100. Similarly, video being recorded by wearable recording device 100 may be transmitted to wearable recording device 800 and displayed on display unit 803 of wearable recording device 800. In this way, a public use mode may allow a first wearable recording device to view video being recorded by another wearable recording device to provide different viewing perspectives of a common event. This public use mode may be useful to give users an option of switching to someone else's view replay if their own view is blocked.

[0104] It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the presently disclosed subject matter, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the presently disclosed subject matter. In the case of program code execution on programmable computers, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. One or more programs may implement or use the processes described in connection with the presently disclosed subject matter, e.g., through the use of an API, reusable controls, or the like. Such programs may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language and it may be combined with hardware implementations.

[0105] Although exemplary embodiments may refer to using aspects of the presently disclosed subject matter in the context of one or more stand-alone computer systems, the subject matter is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment. Still further, aspects of the presently disclosed subject matter may be implemented in or across a plurality of processing chips or devices, and storage may similarly be spread across a plurality of devices. Such devices might include personal computers, network servers, and handheld devices, for example.