Security and Digital Recording System Students: Gadi Marcu, Tomer Alon Number:D1123 Supervisor: Erez Zilber Semester:Spring 2004 Mid Semester Presentation

Project Goals Creating a management system for data, originating from:  Cameras (Movies).  Sensors and possibly other devices (Alerts). This system will enable:  Watching and storing the movies.  On-line response to incoming alerts.

System’s Major Modules Database Server Camera Remote System Sensor Web Server End User Web Application - User Interface The Heart of The System – Main Logic & Algorithms

System Basic Principles Camera Work Profile Schedule  24hrs schedule.  Determines camera’s shooting properties (zoom, pan, tilt, frame rate) and movie storage properties (severity, days to store) in different time slots. Camera Standard Work Profile Schedule  Specifies a standard schedule for specific dates, days of the week and a default schedule.  Lower movie-severity classification (Alerts are of higher priority).

System Basic Principles (cont.) Server – Cameras Interaction  Cameras send data in the following cases only: Data should be stored Real Time watching Movies Storage Policy  Limited by size  New movie upon work profile change  Automatic old data disposal

System Basic Principles (cont.) Alerts Handling Policy  The user specifies which cameras to activate,how (work profiles schedules) and how long - in response to which alerts.  When different alerts occur simultaneously and affect the same camera, the highest severity latest alert will be served, while the others will wait in a special queue.

System Basic Principles (cont.) Problems & Questions Devices Identification:  IP?  Data sent by device? Real Time Watching:  Page reload?  Streaming (WM SDK needed)?  Controlling cameras in Real Time – multiple users? Alerts Initiator Types & Alert Types:  Hard coded?  Entered by user (administrator)?  Received on request?

Web Application – User Interface Users Permissions Hierarchy 1)Real Time Access. 2)Stored Data Access (Read Only) + (1) 3)Devices Working Profiles Configuration Stored Data Removal + (2) 4)Users Hierarchy Management Devices Management System Log Management + (3)

Web Application – User Interface Site Map Login Movie Watching  Watching Real Time Video (Choosing from an authorized list of cameras)  Watching (& Deleting) Stored Video (Choosing from a list of stored videos, filtered / sorted by different parameters)

Web Application – User Interface Site Map (cont.) Devices Configuration  Cameras Configuration (Add / Remove / Edit)  Alerts Initiators Configuration (Add / Remove / Edit)  Alerts Initiators Types Configuration (Add / Remove / Edit)

Web Application – User Interface Site Map (cont.) Cameras Work Profiles Schedules  Work Profiles Schedule Configuration (Add / Remove / Edit)  Cameras Standard Work Profiles Schedules Configuration (Setting a predetermined work profile – default / specific day / specific date)  Alerts Handling Work Profiles Schedules (Setting appropriate responses to various alerts: Which cameras to activate and how)

Web Application – User Interface Site Map (cont.) Users Management (Add / Remove / Edit) Groups Management  Devices Groups (Add / Remove / Edit)  Users Groups (Add / Remove / Edit)  Users Groups Devices Groups Binding (Giving users groups access to certain devices groups)

Web Application – User Interface Site Map (cont.) System Log Watching (Filtered by different parameters / Deleting records) Logout

Database Diagram Users, Devices & Groups Helps enforcing user permissions Stores essential details

Database Diagram (cont.) Work Profiles Schedules & Alerts Handling The schedule consists of different work profiles in different time slots

Database Diagram (cont.) Recorded Movies The recorded movie Severity Classification Days to Store Movie Source Time & Date of Creation

General Class Design Each camera has 1 instance A work profile schedule consists of several work profiles

General Class Design (cont.) Incoming Alerts Creates a communication handling thread Specific handling threads for each camera Implements the camera work profile policy

General Class Design (cont.) Camera Communication Incoming frames Communication handling thread Passing frames to specialized handlers

General Class Design (cont.) Other Important Classes Database connection class:  Connects to the Database.  Executes stored procedures. “Garbage Collection” class:  Removes old movies from database, according to expiration date. AVI movie creator class:  Wraps an existing I263 API.

System View Bandwidth Considerations  QCIF Jpeg takes about 48kb to store.  A camera, filming at 30 fps, consumes 1440kbps worth of bandwidth.  A 10Mbps Bandwidth network can support up to 7 cameras filming at 30 fps simultaneously. Storage Considerations  Using I263 video Codec, storing one second of a 30 fps movie would consume 360kb.  A 20 GB HD could contain 16 hours of video.

System View (cont.) Network Configuration  Two network adapters: Server – Devices Communication Web Server  Transport Layer protocols: TCP for Alerts Initiators communication UDP for incoming video communication

System Implementation Microsoft.NET Microsoft SQL Server 2000

Project Schedule Estimated End Date Phase June 20 th 1 st Iteration May 31 th  Stored procedures  Stored procedures wrapper class  Testing program for the above June 7 th  Server implementation June 14 th  Class testing  Web application skeleton June 20 th  Server testing (simulator)  Release 1.0

Project Schedule (cont.) Estimated End Date Phase July 27 th 2 nd Iteration July 7 th  Improving server implementation July 20 th  Web application improvements July 27 th  Release 1.1  Final Report