View handling in video surveillance systems

US9936170B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9936170-B2
Application numberUS-201514952200-A
CountryUS
Kind codeB2
Filing dateNov 25, 2015
Priority dateSep 28, 2004
Publication dateApr 3, 2018
Grant dateApr 3, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A content analysis engine receives video input and performs analysis of the video input to produce one or more gross change primitives. A view engine coupled to the content analysis engine receives the one or more gross change primitives from the content analysis engine and provides view identification information. A rules engine coupled to the view engine receives the view identification information from the view engine and provides one or more rules based on the view identification information. An inference engine performs video analysis based on the one or more rules provided by the rules engine and the one or more gross change primitives.

First claim

Opening claim text (preview).

What is claimed is: 1. A computing system comprising: one or more processors; and a memory system comprising one or more non-transitory computer-readable media storing instructions that, when executed by at least one of the one or more processors, cause the computing system to perform a method comprising: receiving a video signal comprising a plurality of frames; performing background segmentation on the video signal to extract foregrounds from the plurality of frames; determining an area of a foreground for a first frame of the plurality of frames; determining that the first frame of the plurality of frames is a bad frame based on determining that the area of the foreground is greater than a predetermined portion of a total frame area of the first frame; generating a bad frame event based on determining the first frame is a bad frame; determining a bad frame type corresponding to the first frame; storing an indication of the bad frame type in a listing of bad frame types; deleting a data packet containing the first frame based on the bad frame event; generating a gross change event based on determining that a predetermined number of consecutive bad frames occur; and clearing the listing of bad frame types based on the gross change event. 2. The system of claim 1 , the method further comprising: determining an area of a foreground for a second frame of the plurality of frames by determining a total number of pixels in the foreground of the second frame; and determining that the second frame of the plurality of frames is a good frame based on determining that the total number of pixels in the foreground of the second frame is lower than a predetermined threshold. 3. The system of claim 2 , the method further comprising: determining one or more video primitives based on the second frame; determining a view identification corresponding to the one or more video primitives based on the second frame; determining one or more rules to apply based on the view identification; determining that an event has occurred based on the one or more video primitives and the one or more rules; and determining a response to the event. 4. The system of claim 1 , the method further comprising: generating a gross change primitive in response to the gross change event. 5. The system of claim 1 , the method further comprising: resetting a gross change detector in response to the gross change event. 6. The system of claim 1 , the method further comprising: deleting each data packet that occurred after a first bad frame of the consecutive bad frames in response to the gross change event. 7. The system of claim 1 , the method further comprising: returning a content analysis engine to a warm-up state in response to the gross change event. 8. The system of claim 1 , wherein the bad frame type comprises at least one of an unknown bad frame, a light-on bad frame, a light-off bad frame, and a camera-motion bad frame. 9. The system of claim 1 , wherein the listing of bad frame types is a bad frame histogram. 10. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor of a computing system, cause the computing system to perform a method comprising: receiving a video signal comprising a plurality of frames; performing background segmentation on the video signal to extract foregrounds from the plurality of frames; determining an area of a foreground for a first frame of the plurality of frames; determining that the first frame of the plurality of frames is a bad frame based on determining that the area of the foreground is greater than a predetermined portion of a total frame area of the first frame; generating a bad frame event based on determining the first frame is a bad frame; determining a bad frame type corresponding to first frame; storing an indication of the bad frame type in a listing of bad frame types; deleting a data packet containing the first frame based on the bad frame event; generating a gross change event based on determining that a predetermined number of consecutive bad frames occur; and clearing the listing of bad frame types based on the gross change event. 11. A method comprising: receiving a video signal comprising a plurality of frames; performing background segmentation on the video signal to extract foregrounds from the plurality of frames; determining an area of a foreground for a first frame of the plurality of frames; determining that the first frame of the plurality of frames is a bad frame based on determining that the area of the foreground is greater than a predetermined portion of a total frame area of the first frame; generating a bad frame event based on determining the first frame is a bad frame; determining a bad frame type corresponding to the first frame; storing an indication of the bad frame type in a listing of bad frame types; deleting a data packet containing the first frame based on the bad frame event; generating a gross change event based on determining that a predetermined number of consecutive bad frames occur; and clearing the listing of bad frame types based on the gross change event. 12. The method of claim 11 , further comprising: determining an area of a foreground for a second frame of the plurality of frames by determining a total number of pixels in the foreground of the second frame; and determining that the second frame of the plurality of frames is a good frame based on determining that the total number of pixels in the foreground of the second frame is lower than a predetermined threshold. 13. The method of claim 12 , further comprising: determining one or more video primitives based on the second frame; determining a view identification corresponding to the one or more video primitives based on the second frame; determining one or more rules to apply based on the view identification; determining that an event has occurred based on the one or more video primitives and the one or more rules; and determining a response to the event. 14. The method of claim 11 , further comprising: generating a gross change primitive in response to the gross change event. 15. The method of claim 11 , further comprising: resetting a gross change detector in response to the gross change event. 16. The method of claim 11 , further comprising: resetting a tracker in response to the gross change event. 17. The method of claim 11 , further comprising: deleting each data packet that occurred after a first bad frame of the consecutive bad frames in response to the gross change event. 18. The method of claim 11 , further comprising: returning a content analysis engine to a warm-up state in response to the gross change event. 19. The method of claim 11 , wherein the bad frame type comprises at least one of an unknown bad frame, a light-on bad frame, a light-off bad frame, and a camera-motion bad frame. 20. The method of claim 11 , wherein the listing of bad frame types is a bad frame histogram.

Assignees

Inventors

Classifications

  • Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast · CPC title

  • Analysis of motion (motion estimation for coding, decoding, compressing or decompressing digital video signals H04N19/43, H04N19/51) · CPC title

  • involving subtraction of images · CPC title

  • Region-based segmentation · CPC title

  • H04N7/188Primary

    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) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9936170B2 cover?
A content analysis engine receives video input and performs analysis of the video input to produce one or more gross change primitives. A view engine coupled to the content analysis engine receives the one or more gross change primitives from the content analysis engine and provides view identification information. A rules engine coupled to the view engine receives the view identification infor…
Who is the assignee on this patent?
Avigilon Fortress Corp
What technology area does this patent fall under?
Primary CPC classification H04N7/188. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Apr 03 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).