# US 2014/0192192 A1 · Systems and methods for managing video data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0192192 A1
- Document ID: US20140192192A1
- Status: Published application
- Kind: A1
- Application number: 14/237,278
- Filed: 2012-08-03
- Published: 2014-07-10
- Earliest claimed: 2011-08-05
- Assignees: Honeywell International Inc.
- Inventors: Joshua Worrill; Graeme Laycock; Amelia Masters; Mark Flannery
- Web page: https://patentgrep.com/patent/US20140192192A1

## CPC

- H04N 5/76: Television signal recording
- G08B 13/19669: {Event triggers storage or change of storage policy}
- H04N 7/181: {for receiving images from a plurality of remote sources}
- H04N 7/188: {Capturing isolated or intermittent images triggered by the occurrence of a predetermined event, e.g. an object reaching a predetermined position (signal generation from motion picture films H04N5/253)}
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS

## Abstract

Described herein are systems and methods for managing video data. Embodiments are described by reference to a Digital Video Management (DVM) system, for example in terms of methods for providing incident-centric recording in a DVM system. In overview, a DVM system is configured to include an incident trigger, which is actuated either manually or automatically in response to an “incident”. In the case of manual actuation, the definition of an incident may be subjectively determined by an operator (for example based on training and/or protocols). In the case of automatic actuation, an incident is defined by predefined criteria (for example a signal from analytics software, and alarm, or the like). In response to the actuation of the trigger, an incident identifier is defined. During the period of actuation, a plurality of recordings is automatically made, based on an incident recording protocol. These recordings are all associated with the incident identifier. The automation allows an operator to, at the time of the incident, focus on factors other than ensuring important video evidence is being recorded (such as following a subject through a building by looking at various cameras). The association streamlines subsequent review of an incident, as recordings relevant to the incident are commonly identifiable based on the incident identifier.

## Claims

### Claim 1

A method, performed by a computing device, for controlling a DVM system, the method including:
providing an incident trigger which is configured to be selectively actuated;
in response to actuation of the incident trigger, defining an incident identifier;
during a period of time for which the incident trigger is actuated, applying an incident recording protocol, thereby to automatically make recordings in accordance with the incident recording protocol; and
associating each of the DVM recordings with the incident identifier.

### Claim 2 (depends on 1)

A method according to claim 1 wherein applying the incident recording protocol includes:
(i) monitoring activity at a DVM client;
(ii) identifying a set of one or more cameras for which live video is being accessed by the DVM client;
(iii) making recordings for the identified cameras.

### Claim 3 (depends on 2)

A method according to claim 2 wherein the set of one or more cameras include a camera for which live video is displayed in a major video display object and one or more cameras for which live video is displayed in respective minor video display objects.

### Claim 4 (depends on 1)

A method according claim 1 wherein applying the incident recording protocol includes making recordings of activity at a DVM client.

### Claim 5 (depends on 4)

A method according to claim 4 wherein making recordings of activity at the DVM client includes making recordings of one or more screen images presented to a user of the DVM client.

### Claim 6 (depends on 5)

A method according to claim 5 wherein the one or more screen images define a video of what is presented to the user of the DVM client during the period of time for which the incident trigger is actuated.

### Claim 7 (depends on 1)

A method according to claim 1 wherein applying the incident recording protocol includes associating all image snapshots created at a DVM client with the incident identifier.

### Claim 8 (depends on 1)

A method according to claim 1 wherein the incident trigger is selectively manually actuated by a user of a DVM client.

### Claim 9 (depends on 1)

A method according to claim 1 wherein the incident trigger is automatically actuated in response to predefined criteria being met.

### Claim 10 (depends on 1)

A method according to claim 1 including providing an incident review interface via a DVM client for providing a user with access to all of the recordings associated with a given incident identifier.

### Claim 11

A DVM system configured to perform a method including:
providing an incident trigger;
in response to actuation of the incident trigger, defining an incident identifier;
during a period of time for which the incident trigger is actuated, applying an incident recording protocol, thereby to automatically make recordings in accordance with the incident recording protocol; and
associating each of the DVM recordings with the incident identifier.

### Claim 12 (depends on 11)

A DVM system according to claim 11 including:
a plurality of camera servers, wherein each camera server is configured to make available video data from an assigned one or more video streaming units; and
a plurality of video streaming units, wherein each streaming unit is configured to stream, onto a network, video data for a respective camera.

### Claim 13 (depends on 11)

A system according to claim 11 wherein applying the incident recording protocol includes:
(i) monitoring activity at a DVM client;
(ii) identifying a set of one or more cameras for which live video is being accessed by the DVM client;
(iii) making recordings for the identified cameras.

### Claim 14 (depends on 13)

A system according to claim 13 wherein the set of one or more cameras include a camera for which live video is displayed in a major video display object and one or more cameras for which live video is displayed in respective minor video display objects.

### Claim 15 (depends on 11)

A system according claim 11 wherein applying the incident recording protocol includes making recordings of activity at a DVM client.

### Claim 16

A tangible non-transitive carrier medium carrying computer executable code that, when executed via one or more processes, allows the performance of a method including:
providing an incident trigger;
in response to actuation of the incident trigger, defining an incident identifier;
during a period of time for which the incident trigger is actuated, applying an incident recording protocol, thereby to automatically make recordings in accordance with the incident recording protocol; and
associating each of the DVM recordings with the incident identifier.

### Claim 17 (depends on 16)

A tangible non-transitive carrier medium according to claim 16 wherein applying the incident recording protocol includes:
(i) monitoring activity at a DVM client;
(ii) identifying a set of one or more cameras for which live video is being accessed by the DVM client;
(iii) making recordings for the identified cameras.

### Claim 18 (depends on 17)

A tangible non-transitive carrier medium according to claim 17 wherein the set of one or more cameras include a camera for which live video is displayed in a major video display object and one or more cameras for which live video is displayed in respective minor video display objects.

### Claim 19 (depends on 16)

A tangible non-transitive carrier medium according to claim 16 wherein applying the incident recording protocol includes making recordings of activity at a DVM client.

### Claim 20

(canceled)