of 85

DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED.

Document Optical Systems Group AIRBORNE NETWORK CAMERA STANDARD ABERDEEN TEST CENTER DUGWAY PROVING GROUND REAGAN TEST SITE WHITE SANDS MISSILE RANGE YUMA PROVING GROUND NAVAL AIR WARFARE CENTER
0 views85 pages
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Documenttranscript
Document Optical Systems Group AIRBORNE NETWORK CAMERA STANDARD ABERDEEN TEST CENTER DUGWAY PROVING GROUND REAGAN TEST SITE WHITE SANDS MISSILE RANGE YUMA PROVING GROUND NAVAL AIR WARFARE CENTER AIRCRAFT DIVISION NAVAL AIR WARFARE CENTER WEAPONS DIVISION NAVAL UNDERSEA WARFARE CENTER DIVISION, KEYPORT NAVAL UNDERSEA WARFARE CENTER DIVISION, NEWPORT PACIFIC MISSILE RANGE FACILITY 30TH SPACE WING 45TH SPACE WING 96TH TEST WING 412TH TEST WING ARNOLD ENGINEERING DEVELOPMENT COMPLEX NATIONAL AERONAUTICS AND SPACE ADMINISTRATION DISTRIBUTION A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED. Report Documentation Page Form Approved OMB No Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. 1. REPORT DATE 10 JUN TITLE AND SUBTITLE Airborne Network Camera Standard 2. REPORT TYPE 3. DATES COVERED 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER 5e. TASK NUMBER OS-038 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Range Commanders Council Bldg 1510 Headquarters Ave White Sands Missile Range, NM PERFORMING ORGANIZATION REPORT NUMBER RCC SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR S ACRONYM(S) 12. DISTRIBUTIOVAILABILITY STATEMENT Approved for public release, distribution unlimited. 13. SUPPLEMENTARY NOTES The original document contains color images. 11. SPONSOR/MONITOR S REPORT NUMBER(S) 14. ABSTRACT The deployment of network-based airborne instrumentation systems is leading to cost-efficient replacement for legacy equipment. One application of airborne data acquisition that has to this point been developed without the focus of standardization for interoperable command and control, storage, and data streaming has been the airborne network camera systems used throughout all DoD MRTFBs. This RCC OSG standard has been developed to facilitate compliancy and interoperability between airborne cameras and components. This standard defines queries, action commands, recording format, and data streaming requirements for cameras utilized in airborne applications by both industry and DoD ranges. Not all requirements may be applicable to all types of camera implementations. The intent of this standard is primarily to cover terminology included in or consistent with the GigE Vision (GEV) and IRIG Chapter 10 standards for command and control over a variety of different interfaces. Functionality associated with this standard include the acquisition, processing, recording, streaming, and timing of high-speed airborne imagery. When an OSG-compliant airborne camera simultaneously supports multiple interfaces, it must comply with the interface and command precedence specified in this standard. 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT SAR a. REPORT unclassified b. ABSTRACT unclassified c. THIS PAGE unclassified 18. NUMBER OF PAGES 97 19a. NAME OF RESPONSIBLE PERSON Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18 This page intentionally left blank. Document Airborne Network Camera Standard June 2015 Prepared by Optical Systems Group Range Commanders Council Published by Secretariat Range Commanders Council US Army White Sands Missile Range New Mexico This page intentionally left blank. Table of Contents Preface... vii Acronyms... ix Chapter 1. Introduction Scope Purpose Chapter 2. General Overview s and Requirements Matrix System Architecture Overview Chapter 3. System Devices and Operational Environments Useful Terms Types of On-Board Cameras Type I Camera Type II Camera Type III Camera Type IV Camera Chapter 4. Operational Requirements Bootstrap Registers Device Discovery Static IP Device Discovery Message Device Discovery IP Address Chapter 5. GenICam Features Device Control Device Control Parameters Device Control Custom Features Image Format Control Acquisition Control Continuous Single Frame Multi-Frame Acquisition Control Features Acquisition Control Custom Features Exposure Control Exposure Control Features iii 5.4.2 Exposure Control Custom Features Buffer Control Buffer Control Features Buffer Control Custom Features Local Media Control Local Media Control Features Local Media Custom Features Digital I/O Control Event Control Event Control Features Event Control Custom Features Analog Control Analog Control Features Analog Custom Features Transport Layer Control User Set Control Time Source Control Time Source Control Features Time Source Control Custom Features File File Features File Control Custom Features Chapter 6. GEV Control Protocol Control Channel Command and Acknowledge Message Channel Message Channel Bootstrap Registers Chapter 7. Streaming Protocol Continuous Live Streaming Continuous Memory Acquisition Multi-Frame Acquisition Acquisition Data Storage Timing Source and Synchronization Relative Time Counter Acquisition Data Storage - Setup Record Packets Acquisition Data Storage - Time Packets Acquisition Data Storage - Index/Event Packets Acquisition Data Storage - Dynamic Image Packets iv Chapter 8. User Test Cases Live Preview/Local Storage/Multiple Buffers/Buffer Automation Live Preview/Buffer Recording/No Local Storage Live Preview/Local Storage Recording Appendix A. Definitions... A-1 Appendix B. References... B-1 List of Figures Figure 1. Airborne Network Camera Standard Network... vii Figure 2. Requirement Categories Figure 3. Functional Diagram Figure 4. Device Discovery Process Figure 5. Image Format Control Figure 6. Acquisition Control Process Figure 7. Trigger Capture Point Figure 8. Data Transfer Path Figure 9. Buffered Acquisition and Streaming Figure 10. Event Message Figure 11. Acquisition Data Storage Directory/File List of Tables Table 1. Requirement s Table 2. Optical Systems Group-Standard-Compliant Registers Table 3. Message Numerical v This page intentionally left blank. vi Preface The deployment of network-based airborne instrumentation systems is leading to costefficient replacement for legacy equipment. One application of airborne data acquisition that has to this point been developed without the focus of standardization for interoperable command and control, storage, and data streaming has been the airborne network camera systems used throughout all Department of Defense (DoD) Major Range and Test Facility Bases (MRTFBs). This Range Commanders Council (RCC) Optical Systems Group (OSG) standard has been developed to facilitate compliancy and interoperability between airborne cameras and components. This standard defines queries, action commands, recording format, and data streaming requirements for cameras utilized in airborne applications by both industry and DoD ranges. Not all requirements may be applicable to all types of camera implementations. The intent of this standard is primarily to cover terminology included in or consistent with the GigE Vision 1 (GEV) and IRIG Chapter 10 2 standards for command and control over a variety of different interfaces. Functionality associated with this standard include the acquisition, processing, recording, streaming, and timing of high-speed airborne imagery. When an OSGcompliant airborne camera simultaneously supports multiple interfaces, it must comply with the interface and command precedence specified in this standard. An OSG-compliant system may consist of a single camera or multiple cameras in a network. A camera may support a single or multiple network interfaces, as illustrated in Figure 1. Strict adherence to the GEV standard and requirements of this standard is required to enable interoperability of cameras from different manufacturers. This allows a plug-and-play system environment between devices and implementations. This standard does not define control application or requirements. Although the GEV standard provides for a wide spectrum of network topologies, this standard will only focus on a topology representative of an aircraft configuration. Other topologies may be included as a separate standard of the OSG for other onboard or ground systems. Figure 1. Airborne Network Camera Standard Network 1 Automated Imaging Association. GigE Vision Standard Specification. Version 2.0. November May be superseded by update. Available at 2 Range Commanders Council. Telemetry Standards. Chapter 10, Digital Recording Standard. IRIG June May be superseded by update. Available at vii The OSG prepared this standard, which provides the ranges with a standards-based solution for implementation of network-based airborne cameras from multiple vendors and an improvement in cost competitiveness. Any range that requires cameras will benefit from this standard. The purpose of this OSG effort is the identification of the needs of the MRTFB community for standardized data acquisition and recording from airborne cameras. This document presents a common standard for use by industry to ensure interoperability and competition for a more cost-effective solution for the ranges. Use of this document will also eliminate the need to rely on a single source for critical equipment in the support of range missions within the MRTFBs. For the development of this standard, the RCC gives special recognition to Mr. Alfredo Berard, 96 TW, 96 RANSS/RNRE, Eglin AFB, Florida, and the OSG Digital Imager Working Group chair, Mr. Nestor Portilla. For their exceptional technical support during the developmental effort, the RCC is also indebted to the following individuals: Mark Buckley, Telspan Data Stephen Csaszar, Parks Photographic Laboratory Reto Huber, AOS Technologies Rick Southerland, IDT Inc Peter Chen, Ampex Corp. Eric Lamphear, Telspan Data Boris Nalibotski, A&B Software LLC Dr. Joe Stufflebeam, TRAX WSMR Eric Buckthal, 96 TW Craig Bidstrup, 96 TW For general information about this document or the OSG, you may contact the following. Secretariat, Range Commanders Council ATTN: TEDT-WS-RCC 1510 Headquarters Avenue White Sands Missile Range, New Mexico Telephone: (575) , DSN viii Acronyms µs microseconds ANCS Airborne Network Camera Standard DHCP Dynamic Host Configuration Protocol DoD Department of Defense GenICam Generic for Cameras GEV GigE Vision GVCP GigE Vision Control Protocol GVSP GigE Vision Streaming Protocol IAW in accordance with IPH intra-packet header MRTFB Major Range and Test Facility Base OSG Optical Systems Group RAM random-access memory RCC Range Commanders Council ROI region of interest RTC relative time counter TCP Transmission Control Protocol UDP Universal Datagram Protocol XML extensible markup language ix This page intentionally left blank. x 1.1 Scope CHAPTER 1 Introduction This standard addresses airborne on-board cameras operated in a networked architecture. The sections of this standard are devoted to camera network discovery, camera configuration, data streaming, and local data recording. 1.2 Purpose The purpose of this document is to define the minimum standardization and parameter requirements in a manner that allows for multiple cameras from different vendors to be utilized on the same platform or across all MRTFBs. It is not the intent of this standard to require that all ANCS-compliant cameras provide the same capability. Rather, it is to establish minimum threshold requirements that will facilitate plug-n-play systems integration and data interoperability. This standard does not define system architecture as it only defines the standard queries, action commands, recording format, and data streaming requirement for airborne separation video cameras utilized in vehicle applications. Not all requirements may be applicable to all types of ANCS implementations. The intent of this standard is primarily to cover terminology included in or consistent with the GEV standard and the IRIG 106 Chapter 10 standard document. 1-1 This page intentionally left blank. 1-2 CHAPTER 2 General Overview This standard will leverage the GEV standard employing a proven set of Open Systems Interconnection layer protocols. The GEV standard was ratified in May 2006 by members of the Automated Imaging Association. The GEV standard provides an open framework for transferring images and control signals between cameras and a control application over Gigabit Ethernet connections and now 10-Gigabit Ethernet in Version 2.0. The GEV standard has been adopted by dozens of leading hardware and software companies that develop and sell equipment, high-performance video, and imagery applications. The value of the GEV standard in highperformance, real-time video and imagery applications has been proven in thousands of deployments in the military, aerospace, medical, and manufacturing sectors. The GEV standard is based on Ethernet protocol; however, it is customized for machine vision applications with a goal to offer more reliable image data transmission and a uniform camera control standard. The GEV standard uses Universal Datagram Protocol (UDP) to handle transport at Layer 4 rather than Transmission Control Protocol (TCP). The UDP was selected for its simplicity, low overhead, and multicast support. A benefit to an on-board application are low-latency networked video. The GEV standard includes an optional mechanism that allows video sources to resend undelivered data to video receivers. This mechanism, together with other areas of the standard, allows performance-oriented implementations of the GEV standard to guarantee video transport and achieve low and predictable latency, even during a resend. The GEV standard consists of four major parts plus it incorporates the Generic for Cameras (GenICam) standard 3 to describe the features supported by the camera. Critical to interoperability between GEV cameras and GEV application software, any OSG GEV device MUST provide an extensible markup language (XML) device description file compliant to the syntax of the GenICam as mandated by this standard. This standard will define unique GenICam features of cameras that are required for MRTFB interoperability. requirements are divided into three categories as follows. a. Mandatory: This category contains the minimum set of requirements for interoperability. In this standard, (M) means mandatory. b. Optional: This category contains requirements that may or may not be implemented and may be shown as references. In this standard, (O) means optional. c. Conditional: A conditional requirement is mandatory if an optional requirement is being met. In this standard, (C) means conditional. This standard will provide clear definition of mandatory, optional, and conditional requirements. Features that are unique to this standard will be denoted in bold italic. Features that are standard to the GEV and GenICam standards will be provided for each functional category. This standard requires at a minimum for a camera to be compliant with GEV 1.2 and 3 European Machine Vision Association. Generic for Cameras. Version June May be superseded by update.available at 2-1 GenICam 2.0 specifications. Specific categories provided by this standard are displayed in Figure 2. Figure 2. Requirement Categories Device Discovery: Covers the sequence of events for a controllable device to get a connection through its network interface and obtain a valid IP addressing standard IP protocols and for a control application to enumerate devices on the network. This standard provides specific discovery requirements from the GEV standard. Critical to onboard applications are the ability of the system to automatically recover from camera cycles and for cameras to be discovered as they may be replaced during pre-flight operations. Section 4.2 outlines the mandated requirements for discovery. GigE Vision Control Protocol (GVCP): An application layer protocol replying on the UDP transport layer protocol. It allows an application to configure a device (typically a camera) and instantiate stream channels (GVSP transmitters or receivers, when applicable) on the device and for the device to notify an application when specific events occur. Specific GVCP requirements applicable to an ANCS-compliant camera are provided in Chapter 6. GigE Vision Streaming Protocol (GVSP): The GVSP is an application layer protocol. It allows a GVSP receiver to receive image data, image information, or other information from a GVSP transmitter. The GVSP packets always travel from a GVSP transmitter to a receiver. Specific GVSP requirements applicable to an ANCS-compliant camera are provided in Chapter 7. Bootstrap Registers: Provides configuration of a device via read/write registers. These registers are common to GEV devices and are located at fixed addresses. This standard utilizes contents of bootstrap registers for identification and tracking of data from the devices. For example, a bootstrap register may indicate location of an ANCS-compliant camera. The image data stream or acquisition storage file is tagged with the location name, providing identification and position 2-2 of an on-board camera. Specific bootstrap register requirements applicable to an ANCScompliant camera are provided in Section 4.1. GenICam Features: All GEV-compliant devices must provide a GenICam XML file to describe the features supported by the device. To allow interoperability of on-board cameras within the MRTFB, this standard outlines specific and mandated features within the GenICam XML file. The XML device description file provides the mapping between a device feature and the device register supporting it. There are specific and mandatory features that must be provided from a device to allow for compliance with this standard. Tables will be provided where applicable, defining OSG-mandatory features. Additional features may be added to the XML file as required; however, additional features shall not duplicate functionality of mandated features. 2.1 s and Requirements Matrix This standard establishes the following for an ANCS-compliant camera utilized by MRTFB organizations: a common interface; command and control; and acquisition. This standard does not imply specific hardware architecture or components such as the coupling of data acquisition, multiplexing, and media storage. Rather, interface levels and their requirements are put forth to achieve standardization and interoperability of system devices and data. The requirements interface levels provided by this standard are outlined in Table 1. Table 1. Requirement s Requirement Applicable Section Bootstrap Registers (M) 4.1 Device Discovery (M) 4.2 Device Control (M) 5.1 Image Format Control (M) 5.2 Acquisition Control (M) 5.3 Exposure Control (M) 5.4 Buffer Control (C) 5.5 Local Media Control (C) 5.6 Digital I/O Control (M) 5.7 Event Control (M) 5.8 Analog Control (O) 5.9 Transport Layer Control (M) 5.10 User Set Control (M) 5.11 Time Source Control (M) 5.12 File (M) 5.13 GigE Vision Control Protocol (M) Chapter 6 Control Channel Command and Acknowledge (M) 6.1 Message Channel (M) 6.2 GigE Vision Streaming Protocol (M) Chapter 7 Live Streaming (M) 7.1 Multi-Frame Acquisition (M) 7.3 Acquisition Data Storage (C) 2.2 System Architecture Overview An ANCS-compliant camera may operate in stand-alone mode or as an integral component of a network. A network may have a single or multiple cameras. Strict adherence to the GEV standard and requirem
Advertisement
MostRelated
View more
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks
SAVE OUR EARTH

We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

More details...

Sign Now!

We are very appreciated for your Prompt Action!

x