Video Over Ip Design Guidebook
Total Page:16
File Type:pdf, Size:1020Kb
Project: 0-5942 Product: 0-5942-P1 December 2009 VIDEO OVER IP DESIGN GUIDEBOOK http://tti.tamu.edu/documents/0-5942-P1.pdf Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. FHWA/TX-10/0-5942-P1 4. Title and Subtitle 5. Report Date VIDEO OVER IP DESIGN GUIDEBOOK February 2009 Published: December 2009 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Robert E. Brydia, Byron E. Brackin, Robert F. De Roche, Jeremy D. Product 0-5942-P1 Johnson, and Gary B. Thomas. 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) Texas Transportation Institute The Texas A&M University System 11. Contract or Grant No. College Station, Texas 77843-3135 Project 0-5942 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Texas Department of Transportation Product Research and Technology Implementation Office September 2007–August 2008 P. O. Box 5080 14. Sponsoring Agency Code Austin, Texas 78763-5080 15. Supplementary Notes Project performed in cooperation with the Texas Department of Transportation and the Federal Highway Administration. Project Title: Comprehensive Guide to the Use of IP-Based Video for Traffic Operations URL: http://tti.tamu.edu/documents/0-5492-P1.pdf 16. Abstract Texas Department of Transportation (TxDOT) engineers are responsible for the design, evaluation, and implementation of video solutions across the entire state. These installations occur with vast differences in requirements, expectations, and constraints. Because the systems require extensive interoperability to other systems, agencies, and deployments, a systems engineering process (SEP) is employed to develop a consistent and structured approach to the development of concepts, needs, requirements, design, testing, and ongoing operations. The guidebook contains an accompanying CD which illustrates many aspects of video, which are more easily understood from a visual perspective. The goal of this guidebook is two-fold: (1) to establish a fundamental level of knowledge in video concepts, and (2) to frame the discussion within the concept of systems engineering to provide a logical, consistent, and structured approach to video system development and deployment. 17. Key Words 18. Distribution Statement Video, Systems Engineering, Communications No restrictions. This document is available to the public through NTIS: National Technical Information Service Springfield, Virginia 22161 http://www.ntis.gov 19. Security Classif.(of this report) 20. Security Classif.(of this page) 21. No. of Pages 22. Price Unclassified Unclassified 166 Form DOT F 1700.7 (8-72) Reproduction of completed page authorized VIDEO OVER IP DESIGN GUIDEBOOK Product Number 0-5942-P1 Performed in cooperation with the Texas Department of Transportation and the Federal Highway Administration Research conducted by Texas Transportation Institute The Texas A&M University System College Station, Texas 77843-3135 Authors Robert E. Brydia Byron E. Brackin Robert F. De Roche Jeremy D. Johnson Gary B. Thomas February 2009 Published: December 2009 DISCLAIMER This research was performed in cooperation with the Texas Department of Transportation (TxDOT) and the Federal Highway Administration (FHWA). The contents of this report reflect the views of the authors, who are responsible for the facts and the accuracy of the data presented herein. The contents do not necessarily reflect the official view or policies of FHWA or TxDOT. This report does not constitute a standard, specification, or regulation. The researcher in charge of the project was Robert E. Brydia. v ACKNOWLEDGMENTS This project was conducted in cooperation with TxDOT and FHWA. The authors gratefully acknowledge the contributions of numerous persons who made the successful completion of this project possible. Director, Office of Primary Responsibility Carlos A. Lopez, P.E., Traffic Operations Division, TxDOT Project Coordinator Al Kosik, P.E., Traffic Operations Division, TxDOT Project Director Steve Barnett, Traffic Operations Division, TxDOT Project Monitoring Committee Molli Choate, Wichita Falls District, TxDOT Juanita Daniels-West, P.E., Tyler District, TxDOT Mitch Murrell, Traffic Operations Division, TxDOT Darius Samuels, P.E., Paris District, TxDOT Research Engineer Wade Odell, P.E., Research and Technology Implementation Office, TxDOT Contract Manager Loretta Brown, Research and Technology Implementation Office, TxDOT vi TABLE OF CONTENTS Page 1. INTRODUCTION .......................................................................................... 1-1 1.1. Scope ......................................................................................................... 1-1 1.2. Organization of This Guidebook .............................................................. 1-1 1.3. Audience for This Guidebook ................................................................... 1-2 1.4. Quick Review of TCP/IP .......................................................................... 1-2 1.4.1. How It Works... .................................................................................. 1-3 1.4.2. Performance... .................................................................................... 1-4 2. A BRIEF INTRODUCTION TO SYSTEMS ENGINEERING ..................... 2-1 2.1. Introduction ............................................................................................... 2-1 2.2. What Is Systems Engineering? ................................................................. 2-2 2.3. Why Use Systems Engineering? ............................................................... 2-2 2.4. The Systems Engineering Process ............................................................ 2-3 2.5. Systems Engineering for Video Over IP ................................................... 2-6 2.6. Cited Sources and Bibliographical References ......................................... 2-7 3. EARLY PHASES OF THE SYSTEMS ENGINEERING PROCESS ........... 3-1 3.1. Introduction ............................................................................................... 3-1 3.2. Regional Architecture ............................................................................... 3-1 3.3. Feasibility Study ....................................................................................... 3-5 3.4. Concept of Operations .............................................................................. 3-6 3.5. Cited Sources and Bibliographical References ......................................... 3-7 4. THE FUNCTIONAL REQUIREMENTS PHASE ......................................... 4-1 4.1. Introduction ............................................................................................... 4-1 4.1.1. Specify What, Not How. ................................................................. 4-1 4.2. Development ............................................................................................. 4-2 4.3. System Users ............................................................................................. 4-3 4.3.1. Sample User Needs Statements ...................................................... 4-4 4.3.2. Sample Requirement Statements .................................................... 4-4 4.3.3. Sample Protocol Requirements List................................................ 4-4 4.4. Camera Control ......................................................................................... 4-6 4.4.1. Sample User Needs Statements ...................................................... 4-7 4.4.2. Sample Requirement Statements .................................................... 4-8 4.5. Distribution of Video Images.................................................................... 4-8 4.5.1. Sample User Needs Statements .................................................... 4-10 4.5.2. Sample Requirement Statements .................................................. 4-11 4.6. Image Quality.......................................................................................... 4-12 4.6.1. Sample User Needs Statements .................................................... 4-14 4.6.2. Sample Requirement Statements .................................................. 4-15 4.7. User Interface .......................................................................................... 4-15 4.7.1. Sample User Needs Statements .................................................... 4-16 4.7.2. Sample Requirement Statements .................................................. 4-17 vii 4.8. Control Room Issues ............................................................................... 4-17 4.8.1. Sample User Needs Statements .................................................... 4-18 4.8.2. Sample Requirement Statements .................................................. 4-18 4.9. Communications Infrastructure .............................................................. 4-19 4.9.1. Sample User Needs Statements .................................................... 4-20 4.9.2. Sample Requirement Statements .................................................. 4-21 4.10. Security ................................................................................................ 4-21 4.10.1. Sample User Needs Statements .................................................... 4-22 4.10.2. Sample Requirement Statements .................................................. 4-23 4.11. System Reliability and Redundancy ..................................................