PETITION FOR INTER PARTES REVIEW OF U.S. PATENT NO. 8,185,964
`
`Exacq Technologies, Inc.
`Exhibit 1002
`
`                        
`
`

`
`Doc code: IDS
`
`PTO!SBf08a (01-10)
`Approved for use through 07l31!2012. OMB 0651-0031
`Doc description: Information Disclosure Statement (IDS) Filed
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`IN FORMATION DISCLOSU RE
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Application Number
`
`Filing Date
`First Named Inventor
`A“ Unit
`
`Examiner Name
`
`Joe Robert Marchese
`|
`
`Attorney Docket Number
`
`| 1883-3001?!
`
`Examiner Cite
`.
`.
`,,
`Initial
`No
`
`Patent Number
`
`Kind
`Code1
`
`Issue Date
`
`Name of Patentee or Applicant PageS’C°|umn5'Lme5 Where
`.
`Relevant Passages or Relevant
`of cited Document
`.
`Figures Appear
`
`U.S.PATENTS
`
`-
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`4814869
`
`1989-03-21
`
`Oliver
`
`4991193
`
`1991-02-05
`
`Cecil, et al.
`
`5311306
`
`1994-05-10
`
`Tanaka, et al.
`
`5512974
`
`1996-04-30
`
`Abe, et al.
`
`5561476
`
`1996-10-01
`
`Kershaw, et al.
`
`5625410
`
`1997-04-29
`
`Washino, et al.
`
`5724475
`
`1998-03-03
`
`Kirsten
`
`5761655
`
`1998-06-02
`
`Hoffman
`
`EFS Web 2.1.17
`
`Exacq
`Ex. 1002
`Page 1
`
`Exacq
`Ex. 1002
`Page 1
`
`

`
`Application Number
`
`Filing Date
`
`INFORMATION DISCLOSURE
`
`First Named Inventor
`
`Joe Robert Marchese
`
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Art Unit
`
`Examiner Name
`
`Attorney Docket Number
`
`| 1883-3001?!
`
`5786872
`
`1998-07-28
`
`5805801
`
`1998-09-08
`
`Miyazaki, et al.
`
`Holloway, et al.
`
`5861924
`
`1999-01-19
`
`Pan, et al.
`
`6002428
`
`1999-12-14
`
`Matsumura, et al.
`
`6002995
`
`1999-12-14
`
`Suzuki, et al.
`
`6092078
`
`2000-07-18
`
`Adolfsson
`
`61 15035
`
`2000-09-05
`
`Compton, et al.
`
`6175622
`
`2001-01-16
`
`6178419
`
`2001-01-23
`
`Chiniwala, et al.
`
`Legh-Smith, et al.
`
`6233428
`
`2001-05-15
`
`Fryer
`
`A
`
`AA"'4-'100N)
`
`A ‘.71
`
`A
`
`6269309
`
`2001-07-31
`
`Buckingham
`
`EFS Web 2.1.17
`
`Exacq
`Ex. 1002
`Page 2
`
`Exacq
`Ex. 1002
`Page 2
`
`

`
`IN FORMATION DISCLOSU RE
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Application Number
`
`Filing Date
`First Named Inventor
`A“ Unit
`
`Examiner Name
`
`Joe Robert Marchese
`|
`
`Attorney Docket Number
`
`| 1883-3001?!
`
`2002-05-28
`2003-02-04
`2003-06-24
`
`Enright,etal.
`
`2005-05-10
`
`6396533
`6516340
`6583813
`6891566
`
`If you wish to add additional U.S. Patent citation information please click the Add button.
`
`Add
`
`U.S.PATENT APPLICATION PUBLICATIONS
`
`Publication
`Number
`
`Publication
`Kind
`Code1 Date
`
`Name of Patentee or Applicant
`of cited Document
`
`Pages,Co|umns,Lines where
`Relevant Passages or Relevant
`Figures Appear
`
`
`
`1
`
`2
`
`3
`
`20010008014
`
`2001-07-12
`
`Farrell, et al.
`
`20050200714
`
`2005-09-15
`
`20060106729
`
`2006-05-18
`
`Roberts,Jr.
`
`If you wish to add additional U.S. Published Application citation information please click the Add button.
`
`FOREIGN PATENT DOCUMENTS
`
`Examiner Cite Foreign Document
`|nitia|*
`
`Country
`Code2 i
`
`Kind
`Publication
`Code4 Date
`
`Name of Patentee or
`Applicant of cited
`Document
`
`Pages,Co|umns,Lines
`where Relevant
`Passages or Relevant
`Figures Appear
`
`EFS Web 2.1.17
`
`Exflcq
`Ex. 1002-a
`Page J
`
`Exacq
`Ex. 1002
`Page 3
`
`

`
`IN FORMATION DISCLOSU RE
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Application Number
`
`Filing Date
`First Named Inventor
`Ar, Uni,
`
`Examiner Name
`
`Joe Robert Marchese
`l
`
`Attorney Docket Number
`
`| 1883-3001?!
`
`JP2004178565
`
`JP
`
`2004-00-24
`
`.E”9"5“ Abstract
`included
`
`Add
`
`GB2329541
`
`1999-03-24
`
`SonyUKLtd.
`
`W098/34360
`
`wo
`
`1998-08-06
`
`'”te'e°t Ne.‘W°”‘
`Technologies
`
`W001/69405
`
`2001-09-20
`
`Marchese
`
`If you wish to add additional Foreign Patent Document citation information please click the Add button
`
`NON-PATENT LITERATURE DOCUMENTS
`
`.
`.
`Examiner Cite
`.
`.
`,,
`Initials
`No
`
`Include name of the author (in CAPITAL LETTERS), title of the article (when appropriate), title of the item
`.
`.
`.
`.
`.
`(book, magazine, Journal, serial, symposium, catalog, etc}, date, pages(s), volume-issue number(s),
`.
`.
`.
`publisher, city and/or country where published.
`
`T5
`
`1
`
`2
`
`3
`
`4
`
`5
`
`EFS Web 2.1.17
`
`International Search Report for PCT/US01/08133, 26 July 2001, 3 pages
`
`Supplemental European International Search Report for EP 01 91 6650, 4 February 2009, 1 page
`
`BISDIKIAN et al. "On the Effectiveness of Priorities in Token Ring for Multimedia Traffic," in Proc_ 18th Annual
`Conference Local Computer Networks, Minneapolis, MN, Sept. 1993, pp. 25-31
`
`A Brief History of the Cygwin Project, retrieved from httpzl/cygwin.com/history.htm|, June 14, 2994, 18 pages
`
`|:|
`
`|:|
`
`D
`
`|:|
`
`MARSHALL K. MCKUSICK, et al. "A Fast File System for UNIX," ACM Transactions on Computer Systems, Vol. 2, No. D
`3, August 1984, Pages 181-187
`
`Exflcq
`Ex. 1002
`Page 4
`
`Exacq
`Ex. 1002
`Page 4
`
`

`
`Application Number
`
`Filing Date
`
`INFORMATION DISCLOSURE
`
`First Named Inventor
`
`Joe Robert Marchese
`
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Art Unit
`Examiner Name
`
`|
`
`Attorney Docket Number
`
`| 1883-3001?!
`
`AR(4) Man Page, retrieved Sept. 2, 2003 from http:/ldocs.sun.comldb/doc/801—6680—01/6i11qc0m|?a=view, 4 pages
`
`Tar(1) Man Page for Solaris 2.4, retrieved Sept. 2, 2003 from httpzlldocssun.com/db/doc/801-6680-01/6i11qc0m|?
`a=view, 8 pages
`
`AR(1) Man Page, retrieved Sept. 2, 2003 from http:/ldocs.sun.comldb/doc/801—6680—01/6i11qc0m|?a=view, 3 pages
`
`Beausoft Main Page Archive (February 29, 2000), retrieved from http://web.archive.org/webl200022920571llhttpz/I
`beausoftcoml, 2 pages
`
`R. FIELDING, et al., "Request for Comments (RFC) 2068", Hypertext Transfer Protocol —— H'|‘|'P/1 .1, January 1997,
`162 pages
`
`JPEG Standard, ISO/IEC IS 10918-1 |TU—T Recommendation T.81, September 1992, 186 pages
`
`Webcam Watcher Online Help, Webcam Watcher Version 3.0, Copyright 2001 Beau Software, date unknown, 6 pages
`
`Beausoft Webcam Watcher Description Page (February 29, 2000), retrieved from http:llweb.archive.orgl
`web/2000620224026/www.webcam—watcher.com/wcwindex.html, 4 pages
`
`If you wish to add additional non-patent literature document citation information please click the Add button
`EXAMINER SIGNATURE
`
`*EXAM|NER: Initial if reference considered, whether or not citation is in conformance with MPEP 609. Draw line through a
`citation if not in conformance and not considered.
`Include copy of this form with next communication to applicant.
`
`2 Enter office that issued the document, by the two-letter code (WIPO
`1 See Kind Codes of USPTO Patent Documents at www.USPTO.GOV or MPEP 901.04.
`Standard ST.3). 3 For Japanese patent documents, the indication of the year of the reign of the Emperor must precede the serial number of the patent document.
`4 Kind of document by the appropriate symbols as indicated on the document under WIPO Standard ST.16 if possible.
`5 Applicant is to place a check mark here if
`English language translation is attached.
`
`EFS Web 2.1.17
`
`Exacq
`Ex. 1002
`Page 5
`
`Exacq
`Ex. 1002
`Page 5
`
`

`
`IN FORMATION DISCLOSU RE
`STATEMENT BY APPLICANT
`
`( Not for submission under 37 CFR 1.99)
`
`Application Number
`
`Filing Date
`First Named Inventor
`Ar, Uni,
`
`Examiner Name
`
`Joe Robert Marchese
`l
`
`Attorney Docket Number
`
`| 1883—3001—7
`
`CERTIFICATION STATEMENT
`
`Please see 37 CFR 1.97 and 1.98 to make the appropriate se|ection(s):
`
`|:I
`
`That each item of information contained in the information disclosure statement was first cited in any communication
`from a foreign patent office in a counterpart foreign application not more than three months prior to the filing of the
`information disclosure statement. See 37 CFR 1.97(e)(1).
`
`OR
`
`That no item of information contained in the information disclosure statement was cited in a communication from a
`
`foreign patent office in a counterpart foreign application, and, to the knowledge of the person signing the certification
`after making reasonable inquiry, no item of information contained in the information disclosure statement was known to
`any individual designated in 37 CFR 1.56(c) more than three months prior to the filing of the information disclosure
`statement. See 37 CFR 1.97(e)(2).
`
`II
`
`|:| See attached certification statement.
`
`|:| Fee set forth in 37 CFR 1.17 (p) has been submitted herewith.
`
`None
`
`SIGNATURE
`
`A signature of the applicant or representative is required in accordance with CFR 1.33, 10.18. Please see CFR 1.4(d) for the
`form of the signature.
`
`Signature
`NamelPrint
`
`Date WW-MM-00>
`Registration Number
`
`2°10-02-18
`35691
`
`This collection of information is required by 37 CFR 1.97 and 1.98. The information is required to obtain or retain a benefit by the
`public which is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR
`1.14. This collection is estimated to take 1 hour to complete, including gathering, preparing and submitting the completed
`application form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you
`require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S.
`Patent and Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND
`FEES OR COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria,
`VA 22313-1450.
`
`EFS Web 2.1.17
`
`Exflcq
`Ex. 1002
`Page 6
`
`Exacq
`Ex. 1002
`Page 6
`
`

`
`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the
`attached form related to a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised
`that:
`(1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited
`is voluntary; and (3) the principal purpose for which the information is used by the U.S. Patent and Trademark Office is to
`process and/or examine your submission related to a patent application or patent.
`If you do not furnish the requested
`information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act
`(5 U.S.C. 552) and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the
`Department of Justice to determine whether the Freedom of Information Act requires disclosure of these record s.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a
`court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of settlement
`negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a
`request involving an individual, to whom the record pertains, when the individual has requested assistance from the
`Member with respect to the subject matter of the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for
`the information in order to perform a contract. Recipients of information shall be required to comply with the
`requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records
`may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant
`to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of
`National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or
`his/her designee, during an inspection of records conducted by GSA as part of that agency's responsibility to
`recommend improvements in records management practices and programs, under authority of 44 U.S.C. 2904 and
`2906. Such disclosure shall be made in accordance with the GSA regulations governing inspection of records for this
`purpose, and any other relevant (i.e., GSA or Commerce) directive. Such disclosure shall not be used to make
`determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of
`the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record
`may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record was filed in
`an application which became abandoned or in which the proceedings were terminated and which application is
`referenced by either a published application, an application open to public inspections or an issued patent.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law
`enforcement agency, if the USPTO becomes aware of a violation or potential violation of law or regulation.
`
`EFS Web 2.1.17
`
`Exzrcq
`Ex. 1002
`Page 7
`
`Exacq
`Ex. 1002
`Page 7
`
`

`
`1883-3001-7
`
`DIGITAL VIDEO SYSTEM USING NETWORKED CAMERAS
`
`CROSS-REFERENCE TO RELATED APPLICATION
`
`[0001]
`
`This application is a continuation of U.S. Application Number 11/125,795 filed May
`
`10, 2005, which is a continuation of U.S. Application Number 09/808,543, filed March 14,
`
`2001, now U.S. Patent No. 6,891,566, which claims the benefit of Provisional Patent
`
`Application 60/189,162 filed March 14, 2000. The entire disclosure of these applications are
`
`hereby incorporated by reference.
`
`TECHNICAL FIELD
`
`[0002]
`
`This invention relates to systems for accessing, recording, and displaying camera
`
`images fiom any of a number of remotely located cameras and, more particularly, to such
`
`systems that provide access to images from one or more remote cameras over a public or
`
`private computer network.
`
`BACKGROUND OF THE INVENTION
`
`[0003]
`
`With the continuing expansion and availability of public and private computer
`
`networks it is becoming increasingly common to use these networks for remote video and
`
`image surveillance. Historically, analog systems have been used for CCTV systems for
`
`purposes such as surveillance. They include an analog video camera, a video cable, and a
`
`monitor/ TV and/or a VCR recording device. Multiple cameras can be hooked to multiple
`
`recording VCRs for complete coverage of one or more target areas. Specialized equipment
`
`known as a multiplexer or ‘MUX’ can be used to allow multiple cameras to be hooked to a
`
`single recording/view device. The multiplexer takes all video feeds in a sequential fashion,
`
`recording from one camera at a time. This allows the quantity of cameras to share a single
`
`recording tape. Besides the limitations of a serial tape system, additional limitations are
`
`introduced when the sequencing rate of the multiplexer is too slow to allow sufficient video
`
`record/view speed of a given camera view. Multiplexers are typically expensive and have
`
`limited expandability without purchasing additional
`
`complete
`
`systems.
`
`Also,
`
`the
`
`Exacq
`Ex. 1002
`Page 8
`
`Exacq
`Ex. 1002
`Page 8
`
`

`
`1883-3001-7
`
`configuration of these systems usually requires a skilled technician to be available at the
`
`systems site which increases the total cost of implementing such systems.
`
`[0004]
`
`Digital systems have become more prevalent with the advent of standardized digital
`
`componentry. These systems utilize the same analog cameras and cabling, but introduce a
`
`capture card based collector. This collector can be a proprietary digital device or a PC based
`
`computer, either of which has analog video inputs directly connected to it. These inputs
`
`convert the video to digital for viewing and recording and may even retransmit the signal to
`
`analog tape for recording purposes. A factor limiting these digital systems is that an
`
`autonomous computer is required relatively near the video sources, sometimes with user
`
`intervention required at regular intervals. These machines are also hardware bound. The
`
`number of capture cards is limited to the specific design of the collecting equipment. These
`
`systems are usually proprietary to a particular manufacturer and can be very expensive.
`
`Remote viewing is usually not available. Failover or redundancy function is also limited and
`
`expensive, due to the fact that the system is usually duplicated for redundancy. As with the
`
`analog systems discussed above, these systems also have configuration requirements that
`
`typically require a skilled technician.
`
`[0005]
`
`There now exists commercially available networkable cameras that can be accessed
`
`over networks running TCP/IP,
`
`including both LANs and global networks such as the
`
`Internet. Ethemet-based digital video servers are now common that are small, autonomous,
`
`and usually contain a web-based configuration utility, as well as administration software.
`
`These cameras can be accessed and, in the case of pan/tilt/zoom (PTZ) cameras, controlled
`
`over the network using an assigned IP address and standard CGI-based URL syntax or other
`
`manufacturer-specified addressing protocols. This allows an authorized user to control the
`
`product from anywhere via the Internet or a dialup connection, and allows live images and
`
`image streams (video) to be accessed remotely using standard web browsers.
`
`[0006]
`
`The video servers exist in two forms. One is a camera server that is a complete
`
`product containing both a camera and a web server with an Ethernet port. The other is a
`
`component based video server with inputs for one or more analog video feeds, which the user
`
`can connect to conventional camera PAL or NTSC video feeds. The inputted analog video
`
`feeds are converted to digital signals and sent from the video servers’ Ethernet port. Thus, the
`
`-2-
`
`Exacq
`Ex. 1002
`Page 9
`
`Exacq
`Ex. 1002
`Page 9
`
`

`
`l883-3001-7
`
`video servers (whether integrated in as part of a camera server or as a standalone unit) can be
`
`connected to the Ethemet-based networks commonly used in businesses and other computer
`
`enabled sites. These video servers can be connected to these network segments and are fully
`
`compatible with existing data on these networks. The video data can be received by standard
`
`PC computers which require no special hardware other than an Ethernet connection. The
`
`cameras can be easily configured by a novice user who has very basic experience with the
`
`Internet.
`
`[0007]
`
`Ethernet video servers connect to an Ethernet connection and deliver digital video
`
`based on user requests or internal scripting agents. A user requests video images via standard
`
`CGI enhanced URL syntaxes. These syntaxes control the image metrics and other features of
`
`the requested video stream. The images are sent to the user as either static JPG snapshots, or
`
`as continuous JPG streams. Rates to 30 FPS are easily attainable. Since these images are
`
`delivered by Ethernet, the camera servers are very robust. Although a requested image may
`
`not be received completely in an expected time frame, the video server will wait for the user
`
`to complete its requests and processing. This virtually guarantees delivery of video, except
`
`where a connection to the video server is terminated.
`
`[0008]
`
`When the user requests a video image or stream, the user is actually requesting a static
`
`image that appears to exist as a file in a directory structure on the video server. When the user
`
`requests a copy of this image, the video server actually updates it with a new image from the
`
`camera source, and the user receives a picture that is up to date. Subsequent requests are to
`
`the identical file name, and the server does the updating of its content.
`
`[0009]
`
`Although IP-based network cameras and camera servers have now evolved to a
`
`relatively advanced state, the use of a browser-based interface to this hardware has seemingly
`
`impeded development of user interfaces that provide simplified, automated control over the
`
`acquisition of snapshot and streaming images over the network. Access to the camera images
`
`typically requires knowledge of the manufacturer's CGI-based syntax to access snapshot or
`
`streaming images. For example, to access a particular camera, the user may have to specify to
`
`the
`
`browser
`
`an
`
`address
`
`in
`
`the
`
`form
`
`of
`
`http//Uid:PW@l l l . l l l.l l l . l l l/cgi-
`
`bin/fullsize.jpg?camera=l&compression=l.
`
`While this may be handled easily enough for a
`
`single camera by bookmarking or pulling the URL out of the browser's history buffer, the task
`
`-3-
`
`Exacq
`Ex. 1002
`Page 10
`
`Exacq
`Ex. 1002
`Page 10
`
`

`
`1883-3001-7
`
`becomes more difficult when the user desires to change the access parameters or where
`
`different cameras need to be accessed. Where the identified camera cannot be accessed, such
`
`as for example due to an improper address being specified, the user may simply receive a
`
`standard "404 not found" error message that is not helpful in diagnosing either the error or
`
`actual reason why access was not available.
`
`[0010]
`
`Moreover, browser-based access is typically limited to either a snapshot mode or
`
`streaming images.
`
`In the snapshot mode, a single image is returned when the appropriate
`
`URL is entered into the browser. Subsequent images from the camera are then accessed using
`
`the browser's "reload" or "refresh" button.
`
`In the streaming mode, once the appropriate URL
`
`is specified, the remote server or camera simply begins streaming image files back to the
`
`browser. This results in relatively high network utilization that may be undesirable in a
`
`shared network environment.
`
`[0011]
`
`It is therefore a general object of this invention to provide an improved user interface
`
`and approach to the network transmission of images from commercially available network
`
`cameras.
`
`SUMMARY OF THE INVENTION
`
`[0012]
`
`In accordance with the invention, there is provided a digital video system which
`
`includes a client computer, one or more video servers accessible by the client computer over a
`
`network, and a plurality of cameras connected to the video servers. The one or more video
`
`servers provide an interface between the cameras and client computer, with images from the
`
`cameras being accessed by the video servers and then sent to the client computer upon request
`
`by the client computer. The client computer provides a user interface display on the computer
`
`that includes a display window for each of the cameras accessed over the network and that
`
`displays in each of the display windows an image received from the camera associated with
`
`that display window.
`
`[0013]
`
`In accordance with another aspect of the invention, there is provided a computer
`
`readable medium for use by the client computer in providing the user interface display. The
`
`computer readable medium includes a digital storage device and a user interface program
`
`Exacq
`Ex. 1002
`Page 1 1
`
`Exacq
`Ex. 1002
`Page 11
`
`

`
`1883-3001-7
`
`stored on the digital storage device in computer readable form. The program is operable upon
`
`execution by the computer to access camera data uniquely identifying the cameras and to
`
`attempt access to the cameras over the network using the camera data. The program is further
`
`operable to verify access to those ones of the cameras that are accessible over the network and
`
`to generate the user interface display and to display in each of the display windows an image
`
`received from the camera associated with that display window.
`
`[0014]
`
`In accordance with another aspect of the invention, there is provided a computer
`
`readable medium and method for use by a computer in detecting motion in a sequence of
`
`color video images received by the computer. The computer readable medium includes a
`
`digital storage device containing a program that is operable to carry out the motion detection.
`
`The program selects one of the video images as a reference image and another of the video
`
`images as a selected image to be compared to the reference image. The program then
`
`accesses a color component value for each of a number of pixels from the reference image and
`
`for each of a number of corresponding pixels from the selected image, with the program being
`
`operable to perform pixel comparisons using the color component values and to generate a
`
`motion detect signal when the difference in color component values for corresponding pixels
`
`from the reference and selected images differ by more than a preselected amount.
`
`[0015]
`
`In accordance with yet another aspect of the invention, there is provided a computer
`
`readable medium and method for use by a computer in recording a sequence of images, each
`
`of which comprises an individual image file in which the image is represented in a graphics
`
`file format that includes a first marker identifying the start of the image and a second marker
`
`identifying the end of the image. The computer readable medium includes a digital storage
`
`device containing a program that is operable to carry out the recording. The program stores
`
`the images together as a single file that comprises the group of images concatenated together
`
`in sequential order. The program is operable to index the file using the first and second
`
`markers. This index can then be used to provide quick access to individual images stored
`
`within the single file.
`
`Exacq
`Ex. 1002
`Page 12
`
`Exacq
`Ex. 1002
`Page 12
`
`

`
`1883-3001-7
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0016]
`
`Preferred exemplary embodiments of the invention will hereinafter be described in
`
`conjunction with the appended drawings, wherein like designations denote like elements, and
`
`wherein:
`
`[0017]
`
`Figure l is a block diagram showing a preferred embodiment of a digital video system
`
`of the present invention;
`
`[0018]
`
`Figures 2 and 3 together depict the process flow of the user interface client application
`
`ofFig. 1;
`
`[0019]
`
`Figure 4 shows the contents of the initialization file used by the user interface client
`
`application of Fig. 1;
`
`[0020]
`
`Figure 5 is a diagram depicting the main menu structure of the user interface client
`
`application;
`
`[0021]
`
`Figure 6 is a flow chart showing the process used by the user interface client to
`
`provide hardware setup information;
`
`[0022]
`
`Figure 7 is a diagram depicting the server setup form displayed by the user interface
`
`client;
`
`[0023]
`
`Figure 8 is a diagram depicting the camera setup form displayed by the user interface
`
`client;
`
`[0024]
`
`Figure 9 is a flow chart showing the process used to display a motion form that allows
`
`the user to display and record video streams from one of the cameras;
`
`[0025]
`
`Figure 10 is a flow chart showing the process flow for the image viewer program of
`
`Fig. 1 ;
`
`[0026]
`
`Figure ll is a diagram depicting the menu structure of the image viewer program;
`
`Exacq
`Ex. 1002
`Page 13
`
`Exacq
`Ex. 1002
`Page 13
`
`

`
`l883-3001-7
`
`[0027]
`
`Figure 12a is a flow chart of the autoindexing setup process used by the image viewer
`
`program;
`
`[0028]
`
`Figure 12b is a flow chart of the archive delete process used by the image viewer
`
`program;
`
`[0029]
`
`Figure 13 is an overview of an OCX control used by the user interface client and
`
`stream recorder client applications of Fig. l;
`
`[0030]
`
`Figure 14a is a flow chart of a portion of the OCX control that is used to access
`
`individual snapshot images from the cameras used in the digital video system of Fig. l;
`
`[0031]
`
`Figure 14b is a flow chart of a portion of the OCX control that is used to intermittently
`
`access images from a streaming image server;
`
`[0032]
`
`Figure l4c is a flow chart of a portion of the OCX control that is used to access full
`
`video streams from a streaming image server;
`
`[0033]
`
`Figure l5 is a flow chart of a portion of the OCX control that is used in the processing
`
`and recording of received images and image streams;
`
`[0034]
`
`Figure 16 is a flow chart showing the process flow for the stream recorder client
`
`application of Fig. l; and
`
`[0035]
`
`Figures 17a and 17b together depict the motion detection routine used by the user
`
`interface client application of Fig. l.
`
`DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
`
`[0036]
`
`Referring to Fig. l, there is shown a network setup of a digital video system 20 of the
`
`present invention. The video system 20 includes a client computer 22, a plurality of cameras
`
`24, and one or more standalone video servers 26. The client computer is connected to the
`
`cameras 24 and video servers 26 via a network 28 which can include a private network
`
`segment 30 and a public network such as the Internet 32. Other networked components can
`
`be used such as a networked storage device 34 and a networked file server 36. Some of the
`
`cameras 24 comprise camera servers 38 which include both a video server and camera in a
`
`-7-
`
`Exacq
`Ex. 1002
`Page 14
`
`Exacq
`Ex. 1002
`Page 14
`
`

`
`l883-3001-7
`
`single integrated unit. The camera servers 38 can be, for example, AxisTM 200, 200+, or 2100
`
`Ethernet cameras, available from Axis Communications Inc., Chelmsford, Massachusetts
`
`(www.axis.com). The video servers 26 can be AxisTM 2400, 2401, or 240 video servers, also
`
`available from Axis Communications, Inc. The cameras 24 that are connected to the video
`
`servers 26 can be industry standard PAL or NTSC video cameras. Client computer 22 can be
`
`a conventional personal computer having an IntelTM or compatible CPU running a WindowsTM
`
`operating system and including a network interface card (not shown) for connecting to the
`
`l0/l00 Mb Ethernet network 30 that uses the TCP/IP network protocol.
`
`[0037]
`
`In accordance with the invention, client computer 22 includes a computer readable
`
`memory, such as a fixed hard drive shown at 40 containing magnetic media for digital storage
`
`of a user interface client application 42 that includes a user interface program along with a
`
`number of additional software components. The user interface program is in computer
`
`readable form (such as an .exe file). The additional software components include MicrosoftTM
`
`Internet ExplorerTM Internet extensions (included with WindowsTM 95, 98, ME, 2000 and
`
`revisions),
`
`the Win32API
`
`libraries (included with WindowsTM operating systems),
`
`the
`
`WinInet.dll (also included with WindowsTM operating systems), and a compression library
`
`such as IJLll5.dll (available from IntelTM) to decode and recompress jpeg images received
`
`from the cameras 24.
`
`[0038]
`
`Although the user interface client program 42 is shown as being stored on a hard drive
`
`40, it will be appreciated that it can be stored on other digital storage devices as well. As used
`
`in the specification and claims, "digital storage device" includes any of a variety of different
`
`digital storage devices, including magnetic media such as a hard disk or removable disk,
`
`optical storage media such as a CDROM or DVD, or magneto-optical media.
`
`[0039]
`
`In general, the user interface client program 42 is operable to access locally stored
`
`camera data that uniquely identifies the cameras 24 and then attempts access to those cameras
`
`over the network 28. The program 24 is operable to verify access to at least those cameras 24
`
`that are currently accessible, and to generate a user interface display 44 (on the computer's
`
`monitor) that includes a display window 46 for each of the cameras 24 accessed over the
`
`network 28, and to display in each of the display windows 46 an image 48 received from the
`
`camera associated with that display window. As used in the specification and claims in
`
`-8-
`
`Exacq
`Ex. 1002
`Page 15
`
`Exacq
`Ex. 1002
`Page 15
`
`

`
`1883-3001-7
`
`reference to the program 42 or other executable program code, the phrase "operable to" [carry
`
`out some action] means that, when executed by a microprocessor or other processing device
`
`of the computer, the program directs the microprocessor to carry out or otherwise cause
`
`execution of the specified action.
`
`[0040]
`
`In addition to the user interface client application 42, the hard drive 40 also contains a
`
`stream recorder client application 50 and an image viewer 52. Stream recorder client 50
`
`permits high speed recording of streamed images (video) in a manner that minimizes network
`
`bandwidth utilization.
`
`Image viewer 52 permits browsing and viewing of archived images
`
`and video using a playback screen display 54. These two programs 50, 52 are discussed
`
`farther below in connection with Figs. 10-12 (for viewer program 52) and Fig. 16 (for stream
`
`recorder client 50). All three programs 42, 50, and 52 can be develop