Marine vessel traffic system

[0002] The invention described herein may be manufactured and used by or for the Government of the United States of America for governmental purposes without payment of any royalties thereon or therefor.

[0003] 1. Field of Invention

[0004] The invention relates to an improved radar harbor surveillance sensor, computer and display system to monitor marine harbor traffic and provide advisories to vessels in the areas selected by the system operators, and notify the operators of early warnings of unacceptable traffic conflicts in the confined waterways of the harbor. More particularly the invention relates to the collection of harbor traffic information from multiple remote sensor collection sites around the harbor and the integration, recording, merging and presentation of that remote site data onto a single operator display, selected from a plurality of operator displays. The invention provides a quick, accurate computer generated graphic display of the harbor traffic, possible surface and subsurface conflicts, and key vessel identification information.

[0005] 2. Description of the Prior Art

[0006] A wide variety of sensor information, radio, radar, and camera, has been used in the past to monitor marine traffic from a shore based station and ensure safe passage and the orderly passage of vessels. The technology is based on the direct visual observation and radar sensing techniques and upon procedures developed for collision avoidance of mobile craft and vessels on the high seas. Typically, such harbor surveillance systems consist of one or more shore-based azimuth scanning radar systems, supported in the plural configuration by broadband data linking systems such as microwave relay links or co-axial cable wherever the radar data from a multiplicity of sensors is to be viewed at a single control or operational surveillance center.

[0007] The marine traffic pattern is viewed at one or more shore-based radar plan position indicators by operators whose function is to interpret the traffic situation and to generate alerts when unacceptable ship movements occur or more importantly are about to occur, and to communicate with and to receive communications from ships within their spheres of coverage, such communications being concerned with the identification of specific ships in relation to their present positions and future maneuver intentions. In the special conditions where ships lack and are unable to acquire information necessary to their safe navigation, the operators provide such information in a form intelligible to and convenient to the shipmaster or pilot on board the cooperating vessel. A specific function of the shore-based radar surveillance system is to provide information which is available to the shore station by virtue of the selected location of its radar sensors and which may not therefore be available by examination of similar radar equipment on a specifically located ship because of restricted radar coverage in land-locked constricted canals, rivers, or narrow estuaries.

[0008] Recent concern with the promotion of improved safety of marine operations for the purposes of environmental protection and preservation has also added encouragement to governmental agencies of the leading nations to promote legislation governing the establishment and efficient operation of maritime traffic surveillance systems. Initially, such systems will monitor traffic and issue advisory communications to voluntarily participating vessels. It can be expected that vessel participation will become mandatory.

[0009] Even though shore-based surveillance systems may possess advantages over shipborne equipment devoted to acquiring navigational and traffic information by reason of their carefully-planned deployment and of the deliberate sophistication of equipment matched to high orders of reliability and availability and supported by application of the accurate and rapid data processing capability of the digital computer, certain impediments occur. The individual vessel negotiating an area of difficulty in terms of navigation or traffic density may exercise some discretion in applying its available resources to address those problems of most immediate concern and consequence. In contrast, the shore-based surveillance system must perform its functions with respect to its total surveillance region. When traffic densities are high, the work load generated is known to reach overwhelming levels. The combination of all of the threats posed by encounters of all the traffic elements taken a pair at the time can reach high numerical values.

[0010] More recent shipboard collision threat assessment techniques use automatic target trackers to acquire radar target data and a digital computer to process the radar target data and to provide easily-assimilated presentations of collision threat information to the shipmaster. Efforts to exploit these techniques at the shore-based location have revealed severe limitations. In shipboard systems designed to cope with the pattern of encounters which occur in the open sea, it has been discovered that a more limited applicability results in situations where ships are forced to abandon their normal operating pattern, which is to proceed in general on steady courses with steady speed and to follow the sometimes torturous channels of an estuary or harbor.

[0011] In the latter situations, the likelihood of the ship continuing on at least a steady course is curtailed severely. Reliance upon the convention of prediction of future events based upon the extrapolation of the present positions, speeds, and courses of vessels becomes impossible. Instead, reliance is based on the convention that vessels will follow a predicted set of courses and speeds and normal radar displays are therefore used to monitor the situation to see that the ships do in fact follow the predicted courses. This allows prediction of the vessels future positions even in the usual situation in which a number of bends or changes in channel configuration intervene.

[0012] U.S. Pat. No. 3,971,018 issued to Isbister et al. discloses a marine traffic conflict assessment system that monitors harbor traffic with radar surveillance and permits rapid and accurate assessment of the degree of hazard or safety in the movement of the monitored vessels through the monitored harbor.

[0013] Other radar anti-collision systems for ships in ships in waters adjacent to land areas are focused on mounting the radar and display system on the vessel. U.S. Pat. No. 3,890,616 issued to Kojima et al., U.S. Pat. No. 4,706,090 issued to Hashiguchi et al., U.S. Pat. No. 4,081,802 issued to Elmore et al., and U.S. Pat. No. 4,339,751 issued to Pease.

[0014] The invention relates to an improved radar harbor urveillance sensor, computer and display system to monitor arine harbor traffic, provide advisories to vessels in areas elected by the system operators, and provide the operators of he system with an early warning of unacceptable traffic conflicts in the confined waterways of the harbor. Each marine Vessel Traffic System (VTS) consists of a number of remote sites providing radar, camera video, and audio communicated to a central Vessel Traffic Center (VTC). VTC data integration and display provides the ability to identify, monitor, and advice of potentially dangerous vessel traffic conditions and fuse multi-radars on a single display. Although the primary purpose of VTS is to insure safe passage of vessels throughout these waterways, the system also provides the ability to document incidents and traffic conditions.

[0015] It is an object of the present invention to monitor vessel traffic and provide advisories to vessels in transit or anchorage in key waterways. To accomplish this task, the VTS is capable of acquiring data from one to, in the initial fielded system, 18 (and scaleable beyond 18) remote sites in the form of radar track data, digitized radar image data, camera video, and audio. Data is processed and displayed in a form that provides for early recognition of potentially dangerous situations and communication of the impending condition to vessels of concern. This feature is intended to provide the capability to allow advised vessels to implement corrective actions in a timely manner. Each VTS functions continually, 24 hours a day, seven days a week with a system availability of 99.9%.

[0016] It is a further object of this invention to provides an aid to waterway authorities in the conduct of other mission roles including search and rescue, law enforcement, pollution control, and marine safety. Through data collection, the VTS system facilitates waterway authorities command and control capabilities to detect events and coordinated responses. Included as part of this secondary object is the need to provide operational and administrative reports for both local VTC use and for use by selected governmental authorities external to the VTCs. Report generation includes a query capability of the VTS database and provides integrated outputs of recent vessel tracking and support data. Reports include a summary of vessel traffic data, VTS equipment status, and vessel incident reports for selected periods of time.

[0017] The invention is described in more detail, by way of example only, with reference to the following drawings. Additional features necessary to the invention will be evident from the drawings.

[0018] FIG. 1 is a VTS Overview

[0019] FIG. 2 is the VTS Top-Level HWCI/CSCI Block Diagram

[0020] FIG. 3 is the Front End Switch Block Diagram

[0021] FIG. 4 is a Typical Remote Site Configuration

[0022] FIG. 5 is the VTCS Functional Overview

[0023] FIG. 6 is the VTCS Functional Block Diagram

[0024] FIG. 7 is the SDP Hardware Configuration

[0025] FIG. 8 is the Video Distribution/Control Block Diagram

[0026] FIG. 9 is the Audio Distribution Block Diagram

[0027] FIG. 10 is the Display Console Block Diagram

[0028] FIG. 11 is the Display Console Configuration

[0029] FIG. 12 is the Overview of CSCI Relation to HWCIs

[0030] FIG. 13 Software Context Diagram

[0031] FIG. 14 is the VTS CSCI Data Flow

[0032] FIG. 15 is the Sensor Data Software

[0033] FIG. 16 is the Sensor Data Software Functions

[0034] FIG. 17 is the Remote Site Processing Functions

[0035] FIG. 18 is the Sensor Data Software Functions

[0036] FIG. 19 is the Command and Control CSC (SDP)

[0037] FIG. 20 is the Command and Control CSC (DBP)

[0038] FIG. 21 is the Data Acquisition CSC

[0039] FIG. 22 is the Track Processing CSC

[0040] FIG. 23 is the Track Data Correlation CSC

[0041] FIG. 24 is the Estimated Position Processing CSC

[0042] FIG. 25 is the Alarm Processing CSC

[0043] FIG. 26 is the Data Distribution CSC

[0044] FIG. 27 is the Distribute Video Data CSC

[0045] FIG. 28 is the Distribute Playback Audio Data

[0046] FIG. 29 is the Record and Replay Data Flow

[0047] FIG. 30 is the Menu Hierarchy Diagram

[0048] FIG. 31 is the Main Menu

[0049] FIG. 32 is the System Administration Menu

[0050] FIG. 33 is the Equipment Administration Menu

[0051] FIG. 34 is the Vessel Status Menu

[0052] FIG. 35 is the Reports Menu

[0053] FIG. 36 is the Vessel Administration Menu

[0054] FIG. 37 is the Logs Menu

[0055] FIG. 38 is the User Administration Form

[0056] FIG. 39 is the Sector Administration Menu

[0057] FIG. 40 is the Docks Administration Menu

[0058] FIG. 41 is the Anchorage Administration Menu

[0059] FIG. 42 is the Equipment Configuration Menu

[0060] FIG. 43 is the Remote Site Configuration Menu

[0061] FIG. 44 is the Radar Configuration Menu

[0062] FIG. 45 is the Radar Configuration Menu con_t

[0063] FIG. 46 is the Radar Set Form

[0064] FIG. 47 is the Radar Configuration Form

[0065] FIG. 48 is the Record Replay Configuration Form

[0066] FIG. 49 is the Remote Site Equipment Status Form

[0067] FIG. 50 is the Camera Configuration Form

[0068] FIG. 51 is the Video Insertion Configuration Form

[0069] FIG. 52 is the Video Switcher Configuration Form

[0070] FIG. 53 is the Prospective List Form

[0071] FIG. 54 is the Anchored List Form—A

[0072] FIG. 55 is the Anchored List Form—B

[0073] FIG. 56 is the Anchored List Form—C

[0074] FIG. 57 is the Anchored List Form—D

[0075] FIG. 58 is the Anchored List Form—E

[0076] FIG. 59 is the Docked List Form—A

[0077] FIG. 60 is the Docked List Form—B

[0078] FIG. 61 is the Docked List Form—C

[0079] FIG. 62 is the Docked List Form—D

[0080] FIG. 63 is the Docked List Form—E

[0081] FIG. 64 is the Traffic Summary Form

[0082] FIG. 65 is the Vessel Support Data Form

[0083] FIG. 66 is the Vessel Registry Type Administration Form

[0084] FIG. 67 is the Vessel Country Administration Form

[0085] FIG. 68 is the Vessel Category Administration Form

[0086] FIG. 69 is the Vessel Special Category Administration Form

[0087] FIG. 70 is the Vessel Units Administration Form

[0088] FIG. 71 is the VTS Error Log

[0089] FIG. 72 is the Pilot Form

[0090] FIG. 73 is the Vessel Transit History Form

[0091] FIG. 74 is the Identify Vessel Form

[0092] FIG. 75 is the Traffic Summary Report

[0093] FIG. 76 is the CGVTS Inter-CSCI Data Flow

[0094] FIG. 77 is the Operator Display Software Intra-CSCI Data Flow

[0095] FIG. 78 is the ODS Interface CSC Data Flow

[0096] FIG. 79 is the ODS Display Data Flow

[0097] FIG. 80 is the ODS Database Data Flow

[0098] FIG. 81 is the ODS-UB CSC Data Flow

[0099] FIG. 82 is the Radar Image Daemon Dataflow

[0100] FIG. 83 is the Chart Interface Daemon Dataflow

[0101] FIG. 84 is the Command Status Daemon Dataflow

[0102] FIG. 85 is the TP Dataflow

[0103] FIG. 86 is the TPAD CSC Dataflow

[0104] FIG. 87 is the TPOI CSC Dataflow

[0105] FIG. 88 is the CSD Status Window

[0106] System Overview.

[0107] The VTS is comprised of multiple Remote Site Subsystems (RSS) 1 providing vessel tracking and communication sensors; and a centralized Vessel Traffic Control Subsystem (VTCS) 2 that integrates, processes, and displays RSS data.

[0108] An overview of the VTS system is shown in FIG. 1. This embodiment of the VTS can accommodate not less than 18 RSSs; all providing data to the VTCS 2 where data is merged, processed, recorded, and displayed. The VTS is modular in construction allowing any VTS to be configured with 1 to 18 remote sites and from 1 to 16 display consoles. In addition, each remote site may be configured to acquire sensor data from up to four video cameras 3; one radar 4 providing both digitized radar image data and track data for up to 60 tracks (and easily scaleable beyond the current 60 tracks); and audio for up to two transceivers and four guard receivers.

[0109] Sensor data will be multiplexed at each site for transmission to the VTC via terrestrial data links (for example T1 lines, Fiber Optic lines or a microwave link). Upon acquisition at the VTC, the VTCS will integrate, record, process, and display data, as denoted below:

[0110] Record Data

[0111] All incoming data including radar image data, radar track data, audio, and camera video are recorded for playback in an integrated and time correlated manner.

[0112] Process Data Track and alarm data processing are performed. Data processing functions include:

[0113] Track data correlation

[0114] Estimated vessel position calculations

[0115] Projected vessel encounters

[0116] Alarm processing

[0117] Display Data

[0118] All four types of sensor data are provided to the display consoles, including:

[0119] Camera Video Data.

[0120] Selectively acquired from the video switcher for routing up to four video monitors and a VCR at each display console.

[0121] Radar Image Data.

[0122] Acquired in compressed form. Each display console will decompress, integrate, and overlay chart displays with radar image data.

[0123] Radar Track Data.

[0124] Integrate and selectively overlay chart displays with radar track data.

[0125] Audio.

[0126] Acquired via the audio routing system and selectively routed to display console headsets and speakers.

[0127] Display Console operations shall provide the following capabilities:

[0128] Process and display chart data, radar data, and operational/administration vessel reports.

[0129] Control remote site sensors

[0130] Control audio selection and routing

[0131] Control camera video selection and routing

[0132] Hardware/Software Configuration

[0133] A top-level VTS system block diagram showing the primary Hardware Configuration Items (HWCI) and Computer Software Configuration Items (CSCI) are shown in FIG. 2. An overview of each area is provided below:

[0134] Remote Site Subsystem:

[0135] The Remote Site Subsystem (RSS) 1 consists of all components resident at a VTS remote site necessary for the setup, acquisition, and transmission of audio, camera, and radar sensor data to the VTCS. HWCIs comprising the RSS, include:

[0136] Radar Sensor System (RDSS) 10—HWCI 1:

[0137] The RDSS is composed of those components that provide radar image and track data to the remote site processor HWCI. Components include:

[0138] Radar Processor

[0139] Radar Control Unit

[0140] Radar Transmitter/Receiver

[0141] Radar Antenna

[0142] Remote Site Processor (RSP) 12—HWCI 2:

[0143] Processing system used for setup and control of RSS equipment and the acquisition and pre-processing of radar data, video data, and equipment status.

[0144] Wide Area Network Data Communications (DATAWAN) 14—HWCI 3:

[0145] Hardware consists of a data communications multiplexers and terrestrial data links used for the transmission of data between the VTCS and RSS.

[0146] Visual Sensor System (VSS) 16—HWCI 9:

[0147] The VSS is composed of the equipment needed to provide visual surveillance. Equipment, includes:

[0148] Color, B&W, and Low-Level-Light TV (LLLTV) cameras

[0149] Pan/Tilt camera bases and enclosures

[0150] Video compression hardware

[0151] VHF Radio System (VRS) 18—HWCI 10:

[0152] The VRS consists of the VHF radio equipment needed to transmit and receive audio signals, including:

[0153] VHF-FM transceivers

[0154] VHF-FM guard receivers

[0155] Radio control interfaces

[0156] Antennas

[0157] VTR transceiver audio is routed through the RSS communications multiplexor.

[0158] Sensor Data Software (SDS) 15A—CSCI 1:

[0159] Sensor Data Software resident on the RSP is responsible for:

[0160] direct setup and control of all sensor equipment.

[0161] sensor data acquisition including radar scan and track data.

[0162] sensor equipment status acquisition.

[0163] track pre-processing.

[0164] communication of data to and from the VTCS.

[0165] data recording

[0166] Vessel Traffic Control Subsystem 2:

[0167] The Vessel Traffic Control Subsystem (VTCS) consists of all hardware located at the VTC necessary for the setup, acquisition, control, processing, and display of data from RSSs. As illustrated in FIG. 2 the primary hardware components comprising the VTCS, include:

[0168] Sensor Data Processor (SDP) 20—HWCI 4:

[0169] The SDP provides for the acquisition of RSS sensor data; setup and control of RSSs; record/replay of data; and processing and distribution of sensor data to other VTCS components.

[0170] Database Processor (DBP) 22—HWCI 5:

[0171] The DBP performs alarm data estimated track position processing as well as hosting the system's two resident databases, consisting of:

[0172] ORACLE database that provides a relational database for vessel information storage.

[0173] A Track Database Manager (Tdbm) for storage and distribution of vessel track data.

[0174] Visual Image Routing System (VIRS) 24—HWCI 6:

[0175] The VIRS performs the distribution of camera video data within the VTCS. It also includes video character insertion of camera azimuth, time, and site ID.

[0176] Audio Routing System (ARS) 26—HWCI 7:

[0177] The ARS is responsible for routing of audio to and from the RSSs as well as within the VTCS. This includes VHF-FM audio information, VTCS intercommunications, telephone, audio alarms, audio callback, and systems playback of recorded audio. The ARS is composed of an audio matrix switch and controlling hardware/software.

[0178] Operator Display Processor (ODP) 28—HWCI 8:

[0179] The ODP comprises all equipment making up the VTCS operator consoles including hardware for the setup and control of VTS; display of data including integrated radar track data, radar image data, and alarms; control and viewing of camera video data; and ability to communicate via audio with vessels and other VTS personnel.

[0180] Sensor Data Software 15B—CSCI 1:

[0181] The Sensor Data Software (SDS) performs sensor data acquisition and processing. SDS software resident capabilities on the SDP and DBP of the VTCS, include:

[0182] RSS Setup/Control

[0183] acquisition of RSS sensor data

[0184] track processing

[0185] control of selected VTS functions

[0186] data distribution to other VTCS components

[0187] data record/replay

[0188] Database Software 17—CSCI 2:

[0189] Database Software (DBS) resident on the DBP is responsible for maintaining the VTS database. This database provides for the storage of vessel information used in the generation of database reports, lists, and logs; and is integral to the VTS vessel control man-machine interface. Other key DBS capabilities, include:

[0190] anchorage reservation

[0191] external prospective data interface

[0192] database redundancy

[0193] database backup and recovery

[0194] Operator Display Software 19—CSCI 3:

[0195] The Operator Display Software (ODS) provides a VTS man-machine interface and integrated data display capability for VTS personnel conducting vessel monitoring and advisory operations. Capabilities include:

[0196] setup and control of equipment.

[0197] setup and control of track processing.

[0198] control of geographical chart data and data displays, including radar image data, radar track data, map features overlay, and display processing functions.

[0199] External Interfaces.

[0200] The VTS external interfaces are shown in FIG. 2 and consists of the following:

[0201] UPS communication interface 30

[0202] An Uninterruptable Power Supply (UPS) communication interface is required to acquire power loss signals from the UPS resident at each RSS and the VTCS. The UPS at the RSS is interfaced to the RSP for conveying UPS status back to the VTCS.

[0203] remote site security system 31

[0204] An interface to the security system is required for each RSS. The system provides alarms for intrusion, smoke detection, and environmental alarms (over temperature, under temperature, humidity). Individual sensors are integrated with the control panel which interfaces directly to the data WAN multiplexer at each RSS. Although the Site Security System is routed through the multiplexer, signals are essentially reconstructed at the VTCS data WAN multiplexer and are routed through an alarm notification system exclusive from the rest of the VTCS.

[0205] radar interface 32

[0206] The radar interfaces to the Radar Processor (RP) and Radar Control Unit (RCU). The radar processor interface receives radar video, trigger, and azimuth position data from the radar. The Radar Control Unit interface is an RS-232 interface.

[0207] wide-area network interface 33

[0208] An X.25 Wide Area Network interface is provided to allow remote access of the VTS vessel database and related database reports. This interface may additionally provide a future means of automatic access of external vessel database sources such as Lloyds of London and the Marine Safety Management System (MSMS).

[0209] external prospective data interface 34

[0210] An X.25 interface is provided for the input/output of vessel prospective data with other VTSs. The interface will involve the ability to handle fixed format prospective data messages and free text general information (mail) messages.

[0211] System Modes of Operation.

[0212] The VTS functions in the following modes of operation:

[0213] live processing:

[0214] This mode provides for the acquisition, integration, processing, recording, and display of vessel tracking data in real-time to allow VTS operators to monitor and advise vessels.

[0215] data playback:

[0216] Replays recorded radar image data, radar track data, camera video, and audio. The playback is fully integrated in a manner similar to the live mode of operation. Data playbacks are based on operator selected time periods and are restricted to a single but selectable operator display console.

[0217] Data Simulation

[0218] A simulation capability will be provided that allows operator training on the display console. Data simulation is restricted to a single but selectable operator display console.

[0219] The VTS shall be capable of concurrent live processing with either a data playback or data simulation.

[0220] In addition, the VTS shall include an integrated built-in- test capability to assist in identifying and localizing system hardware failures. This function uses software to localize equipment problems to an area where more detailed system diagnostic software can further identify problems to the board level.

[0221] System Design

[0222] This section details the system design for the primary HWCIs and CSCIs of the VTS as detailed in FIG. 2.

[0223] Hardware Configuration Item Identification.

[0224] The HWCIs for the Remote Site Subsystem (RSS) and the Vessel Traffic Control Subsystem (VTCS) are detailed in the following subparagraphs.

[0225] Remote Site Subsystem.

[0226] Each Remote Site Subsystem (RSS) is configured with the same set of modular hardware components as shown in a typical RSS configuration in FIG. 4, although sensor requirements will vary for individual remote sites. The RSS involves five HWCIs consisting of three types of sensors, a Remote Site Processor (RSP), and a communications HWCI, each of which are defined within the following paragraphs.

[0227] Radar Sensor System (RDSS) 10—HWCI 1.

[0228] Radar video is acquired from remote sites in a run-length encoded format from both the Radar processor and the radar processor. In addition to radar image data, 1 to 60 vessel tracks are available from each radar processor. The typical RSS radar configuration will have a primary and back-up radar with only one radar operating at a time. Some sites may not include a backup radar.

[0229] Use of the radar processor requires a separate Radar Control Unit (RCU) to be interfaced to the radar system.

[0230] Remote Site Processor 12—HWCI 2.

[0231] The Remote Site Processor (RSP) 12 provides an intelligent interface for the setup and control of all remote site sensor hardware. It consists of a 7-slot VME chassis with the following boards:

[0232] VME 35 Processor and 8 channel serial I/O daughter board. This board set provides a 68040 communications processor and eight serial channels configurable for synchronous or asynchronous operation. In addition, the processor board provides two additional asynchronous serial ports providing a total of 10 available serial I/O ports.

[0233] VCOM-8 serial I/O board 36. This board provides eight asynchronous serial I/O ports.

[0234] The RSP serial I/O ports 37 are configured as shown in Table 1. Software processing functions performed by the RSP are detailed within the Sensor Data Software CSCI.

[0235] Wide Area Network Data Communications—HWCI 3.

[0236] The Wide Area Network Data Communications 14 (DATAWAN) consists of the data WAN data communication multiplex unit interconnecting RSSs and VTCS, and a front-end data communications switch at the VTCS. All sensor data, control data, and equipment status are communicated between each RSS and the VTCS via a full duplex link. An Intraplex data WAN multiplex unit will typically be used at both ends of each link.

[0237] A breakdown of the data communications multiplexer input/outputs is presented in Table 2. Three types of multiplexer interface cards are used. The wide band interface provides for synchronous data rates ranging from 64 Kbps to 1.536 Mbps, while an RS-232 interface accommodates asynchronous data up to 19.2 Kbps. The third interface board provides a dual full-duplex channel.

[0238] The multiplexer bandwidth allocated for each video camera is shown as 768 Kbps in Table 2. Actual camera video bandwidth will, however, depend on the number and type of other RSS data sources including transceivers and guard receivers used.

[0239] In addition, the DATAWAN consists of a front-end data communications switch as shown in FIG. 3 and an order wire system. The switch will control which VTCS SDP is primary. The switch controls all SDP data communications, including:

[0240] data communications with all RSSs

[0241] Ethernet connection to Digital Voice Recording System

[0242] SCSI interface to helical scan recorder data recorder

[0243] video insertion unit

[0244] video switcher

[0245] IRIG-B time

[0246] UPS

[0247] RS-232 connection to DBPS for automatic switch over

[0248] Visual Sensor System (VSS) 16—HWCI 9.

[0249] Typical remote sites will be configured with one black and white (BW) camera as shown in FIG. 4. Video signals shall be compressed prior to transmission to the VTCS. Once decompressed at the VTCS, this data will provide video for viewing at the display consoles. In some instances full bandwidth camera video is provided to the VTCS via dedicated communication links Operators may manually control the cameras and associated pan/tilt units, including:

[0250] Azimuth

[0251] Elevation

[0252] Zoom In/Out

[0253] Focus

[0254] Wash/Wipe Lens Cover

[0255] Control Heater/Defogger

[0256] In addition, cameras may be slaved to individual radar tracks as selected by the display console operator. This feature is a future capability enhancement.

[0257] VHF Radio System (VRS) 18—HWCI 10.

[0258] A remote site will consist of up to two VHF-FM transceivers and four guard receivers. For sites having two transceivers, one transceiver shall be active while the other serves as a back-up for both the local and adjacent sites. Each transceiver has a separate antenna with all guard receivers sharing a common antenna. The transceiver employed is the will provide a selectable synthesized frequency, three configurable output power selections squelch control, and full duplex setup and control via RS-232. Up to four guard receivers can be employed at each site.

[0259] Vessel Traffic Control Subsystem.

[0260] The VTCS hardware, shown in FIG. 5, includes data communications and audio routing; front-end hardware consisting of dual sensor data processors 40 and database processors ; video distribution 42; and operator display consoles 43. The following paragraphs define the hardware employed in each of these areas.

[0261] Sensor Data Processor 20—HWCI 4.

[0262] A functional block diagram of the VTCS is shown in FIG. 6. As shown, the front-end consists of four processors consisting of dual (primary and backup) Sensor Data Processors (SDP) 50 and dual (primary and backup) Database Processors (DBP) 52 interconnected via a Fiber Distributed Data Interface (FDDI) high-speed LAN 53.

[0263] The SDP performs the following functions:

[0264] setup, control, and communications with remote sites.

[0265] track processing.

[0266] distribution of data to the database processor and display consoles.

[0267] interface and control of other VTS components such as video switcher, video insertion unit, and helical scan data recorder.

[0268] record and playback of integrated VTS data.

[0269] In addition, a backup SDP is provided that can perform all SDP functions in case of failure of the primary SDP.

[0270] A breakdown of an SDP chassis and its board-level components is shown in FIG. 7. The SDP consists of a general purpose RISC Computer System employing a 20-slot 6U VME chassis. Integral components include:

[0271] Processor Board 55. This board is a standard Motorola processor board employing a single RISC processor with integral SCSI, Ethernet, printer port, and four RS-232 ports.

[0272] FDDI LAN Board 56. A class-A FDDI LAN interface.

[0273] VME Communications processor 57 and 8-channel serial I/O board. This board set provides a 68040 processor and 8-channels of synchronous/asynchronous configurable serial ports for interconnection with remote sites for data acquisition (radar image data, radar track data, compressed camera video data, and status) and providing setup/control of remote site hardware. Each board set accommodates up to 8 remote sites. Each port will be configured as a full duplex 128 Kbps channel employing the HDLC LAPB protocol for insuring data transfer integrity.

[0274] GPS time board set 60. This board set provides for time acquired via the GPS satellite system. Time is distributed via FDDI to the database processor, display consoles, and remote sites as well as in IRIG-B form to the video insertion unit.

[0275] 8 Channel Async Serial Board 58. 8-channel asynchronous serial I/O board. This board provides RS-232 ports used for the direct control of RSS VHF-FM radios in VTSPS RSS configurations not employing an RSP.

[0276] One 1.3 Gbyte system disk 57.

[0277] One 150 Mbyte tape drive 58.

[0278] Peripherals attached to the SDP include the mass storage system 59, and the Digital Voice Recording System (DVRS). The helical scan mass stoarage system, a 580 Gbyte storage system consists of 120 8mm tapes configured in a jukebox style recorder with four tape record/replay head assemblies. The EXB-120 interfaces to the SDP via a SCSI interface and provides over 30 days of total data storage.

[0279] The Digitical Voice Recording System (DVRS) 60 digitizes and compresses up to 64 channels of audio and provides reconstructed playback audio for up to 5 channels. For an initial capability, the DVRS is provided in a stand-alone configuration with integral recording and playback of audio data. As a future capability enhancement the DVRS will be integrated into the SDP via Ethernet as part of the integrated systems data record/playback capability utilizing the EXB-120 data recorder.

[0280] Database Processor 22—HWCI 5.

[0281] The Database Processor (DBP) performs track data alarm processing, track data distribution, and all database functions associated with the VTS database. A high performance commercial workstation is used as the DBP.

[0282] Visual Image Routing System 24—HWCI 6.

[0283] Distribution of camera video at the VTCS is performed by the Visual Image Routing System (VIRS) as shown in FIG. 8. The VIRS can be configured to accommodate input of up to 36 cameras from all remote sites and selectivitely route video to the operator display console video monitors and VCR. Full motion camera data acquired directly from RSSs using a dedicated camera data communications links are input directly into the video insertion unit for subsequent routing to the VIRS. RSS camera data that is received in compressed and routed through the VIDEO decompression unit prior to input into the video insertion unit. The video insertion unit overlays the site ID, camera azimuth pointing angle, and the current time of day onto each video image.

[0284] The VIRS output consists of up to five outputs to each display console, consisting of four video channels; one for each of up to four display console video monitors, and an output for the display console VCR. Any of the four video channels can be selected for routing to the VCR. In a similar manner, VCR playback video can be routed to any of the four monitors. All VIRS controls are initiated by the display console touch panel and conveyed to the SDP which provides direct control over the VIRS.

[0285] In addition, the SDP provides compressed playback video to the video decompression unit in a manner identical to live video except that playback video may be further frame rate reduced. The VIRS unit employed is the Grass Valley Group, Horizon Routing System. The system is expandable to accommodate up to 36 inputs and 36 outputs.

[0286] Audio Routing System 26—HWCI 7.

[0287] The ARS will provide routing of audio to and from the data communications multiplexer, DVRS, and ODPs in support of both live VTS operations and system playbacks. An overview of the ARS is shown in FIG. 9. It provides the capability to accommodate the following audio input/outputs:

[0288] Audio Inputs:

[0289] Up to two transceivers for each of 18 sites Up to four guard receiver channels for each of 18 sites

[0290] Up to sixteen audio alarms signals—One audio alarm being provided from each of the display consoles.

[0291] Up to sixteen audio callback signals—One from each of the display consoles.

[0292] Up to sixteen audio inputs—One from each of the display console operator's microphone/headset.

[0293] Two standard telephone lines.

[0294] One order wire audio input.

[0295] Up to five audio playback channels from the SDP's Digital Voice Recording System.

[0296] Audio Outputs:

[0297] Up to seven audio outputs per display console, consisting of four speakers, one headset, and two audio callback channels for recording at the display console. FIG. 9

[0298] Up to 36 composite transceiver audio signals for efficient recording of audio data.

[0299] To reduce the number of audio input channels required of the audio recording system, the ARS will function as a mixer providing one composite signal for each transceiver. In addition, each display console will provide an audio alarm signal to the ARS for distribution to the console speakers/headset. In this way, alarms can be directed to individual speakers or mixed for inclusion over the headset. Alarms normally specific to a display console can be mixed and provided to the supervisor over his respective speaker/headset. In a similar manner, “Audio Callback”, which is stored at the individual display consoles, is played back through the ARS for output on selected speakers/headsets.

[0300] For integrated data playbacks, reconstructed audio data is output from the audio digitizing system and distributed to the playback console via the ARS. Up to five ADS audio playback channels can be selected for system playback. This design approach is intended to provide an audio replay capability to drive all four console speakers and operator headset during a systems playback.

[0301] In general, the ARS provides the capability for watch operators to selectively communicate with vessels using any transceiver within the local VTS system; to setup communication networks involving two or more watch operators; and to establish individual networks between operators and the supervisor as might be required. Normal telephone service is also integrated with the ARS for use as necessary by operations personnel.

[0302] The ARS provides each operator the capability to monitor and/or transmit audio over pre-assigned channels. The operator will also have the capability to assign specific channels for monitoring via console speakers and headset. Each defined audio channel has a visual indicator of channel activity.

[0303] Operator Display Processor 28—HWCI 8.

[0304] This section details the hardware configuration for the VTS operator display processor (display console).

[0305] The display console provides an integrated means of conducting VTS operations. It provides the ability to setup and control remote sites, and to selectively acquire, process, and display data from any combination of remote site sensors, including audio, camera video, and radar data. A functional overview of the display console illustrating its major components is shown in FIG. 10. The TAC-3 computer system is employed as the operator display processor for the display console. The system is a UNIX based HP 700 Series processor configured with dual-headed graphics and an FDDI LAN interface for communicating with the SDP and DBP.

[0306] The display console shown in FIG. 11 has been ergonomically designed for ease of use. It incorporates internal forced air ventilation and easy access to all hardware maintenance areas from the rear of the cabinet. Display console/processor characteristics include:

[0307] identical processor and operating system compatibility as that defined for the database processor

[0308] dual-head graphics driving two 21″ high resolution (1280×1024) color monitors 70

[0309] Pro Audio Spectrum 16 audio digitizer board with dual input/outputs. Inputs are used for digitizing and recording up to two audio channels for use in audio callback. Outputs include audio alarm and playback of one selected audio recall channel.

[0310] FDDI, class A interface

[0311] up to four 13″ color monitors for video display 72

[0312] four speakers with individual volume controls and channel activity indicators 74

[0313] Four audio headset jacks located under counter-top 76

[0314] push-to-talk foot strip switch 78

[0315] video control touch panel 80

[0316] ARS control panel

[0317] keyboard and mouse/trackball

[0318] shatter-proof glass counter top capable of supporting 200 lbs

[0319] recessed casters

[0320] For purposes of clarity in understanding the display console, selected key operational features are briefly discussed below:

[0321] Display Consoles are identical and are operator selectable for use as an operational console, a data playback console, or training console.

[0322] Two high-resolution 21″ color graphic displays 70 are provided in each display console. Any combination of chart displays and tabular report/displays may be concurrently selected for viewing and multiple radar images may be fused onto a single display. The VTS design accommodates the inherent geographical and operational diversity between VTSs. It may be desirable, for example, for sectors involving large anchorage areas to display a large overview chart display on one CRT with more detailed chart or tabular data selected for viewing on the second CRT. In this example, the operator may zoom in on selected chart areas of interest on the second CRT without losing the overall context of vessel traffic flow presented on the first CRT. Alternatively, for sectors involving long waterways, operators may elect to subdivide CRT displays into displays that partition multiple legs of the waterways. CRT 1, for example, might be divided into a top and bottom half with each half providing coverage of a selected leg. The second CRT could just as easily be used for displaying additional legs of a waterway or used for tabular report/displays. In effect, each VTS will be able to configure chart displays without the need for software programming or system re-configuration.

[0323] Operational guidelines and policies concerning configuration of displays should be developed at each VTS.

[0324] Each display console may be configured to receive any camera video, audio, radar image data, or radar track data available within the system.

[0325] Computer Software Configuration Item Identification.

[0326] The VTS is partitioned into three Computer Software Configuration Items (CSCI), consisting of:

[0327] Sensor Data Software (SDS)

[0328] Database Software (DBS)

[0329] Operator Display Software (ODS)

[0330] FIG. 12 illustrates the relationship of CSCIs to HWCIs as discussed within the following paragraphs. The overall software context diagram is shown in FIG. 13 and the three main components of the VTS data flow are shown in FIG. 14.

[0331] Sensor Data Sofware

[0332] Overview

[0333] The Sensor Data Software CSCI (FIG. 15) is the central point for receiving and processing remote sensor data. Sensor processing attributes are defined by system configuration information received from the DBS.

[0334] The SDS inputs video, radar, and site status at each remote site, packages the remote site data, and transmits it to SDS functions running on the Sensor Data Processor and Data Base Processor. Audio data is received from the digital audio recording system. Radar track data is converted, correlated, checked for alarm conditions, and recorded along with audio, video, radar scan data, vessel identification data, alarms, and GPS time. Correlated track data, alarms, time, and status information is transmitted to the Database Processor for database recording. Correlated track data, radar scan data, alarms, and time are transmitted to the ODS for display and audio alarm generation.

[0335] In playback mode, video data is transmitted to the video switcher, and audio data is transmitted to the digital audio recording system.

[0336] Sensor control commands are received from the ODS, formatted for the specific device, and transmitted to the remote site or local hardware as necessary. Sensor control command status is returned to the ODS.

[0337] CSCI Architecture

[0338] The Sensor Data Software (SDS) exists on four separate processors:

[0339] Sensor Data Processor (SDP)

[0340] Database Processor (DBP)

[0341] Data Acquisition Processor (DAP)

[0342] Remote Site Processor (RSP)

[0343] The Sensor Data Software CSCI is composed of the following CSCs:

[0344] CSC Processor

[0345] Command and Control, FIG. 19 SDP, DBP

[0346] Remote Site Processing, FIG. 17 RSP

[0347] Data Acquisition, FIG. 21 SDP (DAP)

[0348] Track Processing, FIG. 22 DBP

[0349] Data Distribution, FIG. 26 SDP

[0350] Record and Replay, FIG. 29 SDP

[0351] The top level flow diagrams of the Sensor Data Software is illustrated in data flow diagrams: FIG. 15, FIG. 16, FIG. 17, and FIG. 18.

[0352] Command and Control CSC (FIG. 19)

[0353] The Command and Control CSC manages inter-processor communications and sensor command processing. It produces the corresponding Uninterrupted Power Supply (UPS), radio, video, and radar control commands, which are routed to the appropriate devices. System configuration information is retrieved from the ORACLE database.

[0354] Responses to system commands are sent to the ODS. Status information provided by the various devices is collected and analyzed. If an error condition is detected, an alarm notification is generated. All device status information is stored in the database equipment status log.

[0355] The Command and Control CSC also handles notification from the UPS that power has been interrupted and passes the notification on. Time is received from the GPS and is broadcast periodically to other VTS components as the current system time.

[0356] The Command and Control CSC obtains functional performance statistics from each CSC and stores them in the ORACLE database. These statistics are used in system performance reports which indicate the level of usage of system resources and processing capacity.

[0357] Remote Site Processing CSC (FIG. 17)

[0358] The Remote Site Processing CSC executes on the Remote Site Processor. It gathers data and status information from the radar processor and video cameras at the remote site. This information is site-tagged and time-tagged, and then transmitted to the VTC. This CSC also controls the various sensors based on control commands received from the Command and Control CSC and is also designed for Automated Dependance Survielance (ADS).

[0359] Data Acquisition CSC (FIG. 21)

[0360] The Data Acquisition CSC accepts the following data from the remote sites: audio data from radios, video data from CCTV cameras, and radar data from the radar scan converter. It places the incoming data into the Acquisition Buffers for access by other CSCs. Functional performance statistics are produced for the Command and Control CSC.

[0361] Track Processing CSC (FIG. 22)

[0362] The Track Processing CSC obtains raw and filtered radar track data from the Acquisition Buffers and performs track processing to produce correlated track data. The correlated track data is compared with system configuration data (zone definitions, etc.) to determine whether the position, heading, or speed of any vessels warrant generating alarms. Functional performance statistics are produced for the Command and Control CSC.

[0363] Data Distribution CSC (FIG. 26)

[0364] The Data Distribution CSC obtains audio and video data (playback only), along with radar scan data from the Acquisition Buffers. Correlated track data is also retrieved from the Correlated Track Data table. Based on system configuration information, the playback audio is sent to the audio routing system, the playback video is sent to the Video Switcher, and the radar scan data and correlated track data are routed to the appropriate console. This CSC also controls the video insertion unit, which inserts the current time, along with remote site identification and camera azimuth into the video data. Functional performance statistics are produced for the Command and Control CSC.

[0365] Record and Replay CSC (FIG. 29)

[0366] The Record and Replay CSC obtains radar scan data, compressed video data, and audio data from the Acquisition Buffers, as well as correlated track data from the Correlated Track Data table. This data is continually recorded along with system configuration data, operator commands, and vessel data in mass storage during real-time operation. During system replay, the data is extracted from mass storage and deposited in the Acquisition Buffers, where it is treated just like real-time data. Functional performance statistics are produced for the Command and Control CSC.

[0367] System States and Modes

[0368] The Sensor Data Software supports operation in the live and replay modes. The live mode supports continuous uninterrupted system operation, including: remote site sensor control, remote site sensor data transmission, data acquisition, track processing, data recording, data distribution to the DBS and ODS CSCIs, and performance monitoring. The replay mode provides a data replay capability that runs concurrently with the live mode. The data flow between CSCs supporting the live and replay modes is illustrated in the data flow diagrams in FIG. 16 through FIG. 18.

[0369] Memory and Processing Time Allocation

[0370] SDS program processes operating on the SDP have available up to 32 Mbytes of memory to perform system operations. SDS program processes operating on the RSP have available up to 4 Mbytes of memory to perform system operations. SDS and DBS program processes operating on the DBP have available up to 96 Mbytes (in the current implementation expandable to 384 Mbytes) of memory to perform system operations.

[0371] Processes supporting live operations have priority over processes supporting replay operations.

[0372] CSCI Design Description

[0373] The following subparagraphs provide a design description of this CSCI.

[0374] Command and Control CSC

[0375] The Command and Control CSC of the Sensor Data Software (SDS) CSCI is responsible for controlling sensors as directed by operator commands, monitoring the status of all remote site sensors and devices, storing sensor status and system performance information in the database for report generation, distributing system time, and monitoring the UPS for power failure indication. It also manages inter-process network communication.

[0376] The Command and Control CSC data flow is shown in data flow diagrams in FIG. 19 and FIG. 20. The Command and Control CSC is composed of the following CSUs:

[0377] Command/Response Processing

[0378] Control Sensors

[0379] Monitor Sensors

[0380] Monitor UPS Status

[0381] Distribute System Time

[0382] System Performance Logging

[0383] Message Logging

[0384] The Command/Response Processing, System Performance and Message Logging CSUs also run on the DBP in support of the Track Processing CSC.

[0385] Remote Site Processing CSC

[0386] The Remote Site Processing CSC of the Sensor Data Software (SDS) CSCI is responsible for controlling the various sensors and devices at the remote site (radars, radar processor, CCTV video cameras and radios) based on control commands received from the Sensor Data Processor (SDP), relaying the status of all remote site sensors to the SDP, and ingesting radar track and radar scan data and compressed video data, all of which is site tagged and transmitted to the SDP.

[0387] The Remote Site Processing CSC data flow is shown in the data flow diagram 17. The Remote Site Processing CSC is composed of the following CSUs:

[0388] Remote Site Processor Initialization

[0389] Remote Site Processor Main

[0390] Receive from VTC

[0391] Transmit to VTC

[0392] Dispatch Commands

[0393] Control Cameras

[0394] Control Radars

[0395] Control Radios

[0396] Monitor UPS

[0397] Ingest Compressed Video Data

[0398] Ingest Radar Data

[0399] Common Coordinate Conversion

[0400] Data Acquisition CSC

[0401] The Data Acquisition CSC collects multiplexed sensor data and status information from each of the remote sites and compressed audio data from the Digital Audio Recording System. The multiplexed remote site sensor information is placed in circular sensor information input buffers while waiting to be demultiplexed and distributed to other CSCs. Once the data is separated, sensor status information is routed to the Command and Control CSC, and the audio, video, radar track data, and radar scan data is placed in circular acquisition buffers for use by the Track Processing, Data Distribution, and Record and Replay CSCs.

[0402] The Data Acquisition CSC data flow is shown in the data flow diagram in FIG. 21. The Data Acquisition CSC is composed of the following CSUs:

[0403] RSP to VTC Data Transmission CSU

[0404] VTC to RSP Data Transmission CSU

[0405] RSP To VTC Data Transmission CSU

[0406] VTC To RSP Data Transmission CSU

[0407] Input Audio Data CSU

[0408] Input Video Data CSU

[0409] Track Processing CSC

[0410] The Track Processing CSC uses radar track data deposited in the acquisition buffers to perform track processing functions, including: target acquisition, drop track processing, track data correlation, position estimation, radar calibration, and alarm generation. The Command and Control CSC handles transferring the data from the acquisition buffers on the SDP over the network and into the acquisition buffers on the DBP.

[0411] Radar track data is extracted from the acquisition buffers and placed into the SDS Track Table by the Target Acquisition CSU. The Drop Track processing CSU deletes track table entries when target contact is lost by a radar, or when a system operator chooses to drop a track. The Sector Monitoring CSU determines the sector(s) containing a tracked vessel. The Track Data Correlation CSU checks vessel handoff criteria, checks for tracked vessels in radar overlap areas, and correlates the data from multiple radars. The Estimated Position sub-level CSC computes estimated position (EP) information for vessels on EP routes. The Radar Calibration CSU tracks objects which reside at a known, stationary location, and provides calibration error statistics. The Alarm Processing sub-level CSC checks for the existence of vessel alarm conditions.

[0412] The Track Processing CSC data flow is shown in the data flow diagram FIG. 22. The Track Processing CSC is composed of the following sub-level CSCs and CSUs:

[0413] Track Data Correlation sub-level CSC

[0414] Estimated Position Processing sub-level CSC

[0415] Alarm Processing sub-level CSC

[0416] Target Acquisition CSU

[0417] Drop Track Processing CSU

[0418] Radar Calibration CSU

[0419] Sector Monitoring CSU

[0420] Track Data Correlation CSC (FIG. 23)

[0421] The Track Data Correlation Sub-level CSC uses radar track data and system configuration data to determine when a vessel enters or exits a radar overlap area. When a vessel enters a radar overlap area, vessel tracking is started on the overlapping radar. The vessel is tracked by multiple radars until it exits the radar overlap area. Single radar vessel tracking is resumed when the vessel exits a radar overlap area.

[0422] Radar track data from the SDS Track Table is monitored, checking for any tracked vessel that has entered a radar overlap area. If a vessel has entered a radar overlap area, a request is made of the overlapping radar processor to start tracking that vessel. Once the multiple tracking is established, duplicate tracking data from all tracking radars is correlated to obtain a best estimate of the vessel tracking information. While the vessel is in the radar overlap area, its position and direction is monitored to determine when radar overlap area exit occurs. When the vessel does exit the radar overlap area, it is automatically handed off to the radar coverage area into which it emerges.

[0423] The Track Data Correlation Sub-level CSC data flow is shown in the data flow diagram FIG. 23. The Track Data Correlation Sub-level CSC is composed of the following CSUs:

[0424] Overlap Area Monitoring

[0425] Locate Duplicate Tracks

[0426] Correlated Position Estimation

[0427] Automatic Radar Handoff

[0428] Estimated Position Processing CSC (FIG. 24)

[0429] The Estimated Position Processing Sub-level CSC uses radar track data, EP track data, system configuration data and operator supplied commands to generate EP tracking data which follow an operator specified EP route. When a vessel enters an area with no radar coverage, the operator can assign the vessel to a pre-defined EP route. From that point on, the vessells position, direction, and speed are estimated following the pre-defined EP route. As the vessel travels along the EP route, a system operator may correct the estimated track data to reflect the actual vessel position or speed. EP track data is generated until the vessel reaches the end of the assigned EP route, or the vessel is assigned to a track by a system operator. If the vessel is not assigned to a track before it reaches the end of the EP route, an automatic re-assignment attempt will be made.

[0430] The Estimated Position Processing Sub-level CSC data flow is shown in the data flow diagram FIG. 24. The Estimated Position Processing Sub-level CSC is composed of the following CSUs:

[0431] Automatic Vessel Re-Assignment

[0432] EP Route Processing

[0433] Alarm Processing CSC (FIG. 25)

[0434] The Alarm Processing Sub-level CSC uses processed track data, EP track data, and system configuration data to monitor vessel traffic safety parameters. When a vessel triggers an alarm condition, an alarm is sent to the system operator. The alarm will continue to be sent until the system operator acknowledges the alarm and the alarm condition no longer exists.

[0435] The Traffic Lane Monitoring CSU checks for any tracked vessel that is crossing a traffic lane and triggers the traffic lane violation alarm as necessary. The Stationary Safety Zone Monitoring CSU checks for any vessel crossing a stationary safety zone boundary and triggers the safety zone alarm as necessary. The Moving Safety Zone Monitoring CSU checks for any vessel crossing a moving safety zone boundary and triggers the safety zone alarm as necessary. The Collision Monitoring CSU checks tracked vessels for impending collisions and triggers the collision alarm as necessary. The Radar Contact Monitoring CSU checks for vessel tracks which have been lost by the radar and triggers the radar contact lost alarm flag as necessary. The radar contact lost flag is cleared when the vessel is reassigned or tracking discontinued by the system operator. The Sudden Course/Speed Change Monitoring CSU checks tracked vessels for course or speed changes exceeding operational parameters and triggers the course or speed change alarms as necessary. The Excessive Speed Monitoring CSU checks for tracked vessel speed violations and triggers the excessive speed alarm as necessary.

[0436] The Alarm Processing Sub-level CSC data flow is shown in the data flow diagram FIG. 25. The Alarm Processing Sub-level CSC is composed of the following CSUS:

[0437] Traffic Lane Monitoring

[0438] Safety Zone Monitoring

[0439] Moving Safety Zone Monitoring

[0440] Collision Monitoring

[0441] Radar Contact Monitoring

[0442] Sudden Course/Speed Change Monitoring

[0443] Excessive Speed Monitoring

[0444] Data Distribution CSC (FIG. 26)

[0445] This CSC maintains routing information for playback video and audio data based on operator playback setup commands. It extracts playback audio and video data deposited in the Acquisition Buffers by the Record and Replay CSC. Audio data is sent to the Audio Digitizing System for output to the Audio Distribution System, which sends it to the console for playback. Note that setup and control of the audio routing system is not a Sensor Data Software function. Video data is sent to the JPEG boards for decompression and output to the Video Insertion Unit.

[0446] Data for the Video Insertion Unit is provided for both live and playback video. The Video Insertion Unit inserts the time, remote site and camera ID, and camera azimuth into the video data. For live video data, camera azimuth data from the remote site is received for output to the Video Insertion Unit. For playback video data, the camera azimuth is obtained from the video buffer header.

[0447] The Data Distribution CSC data flow is shown in the data flow diagram FIG. 26. The Data Distribution CSC is composed of the Distribute Playback Video Data sub-level CSC, the Distribute Playback Audio Data sub-level CSC, and the Video Switcher and Character Inserter CSUs.

[0448] Distribute Playback Video Data CSC (FIG. 27)

[0449] The Distribute Playback Video Data sub-level CSC is responsible for managing the insertion of video information into the live and replay video data using the Video Insertion Unit, and routing video to the specified console monitors and VCRs using the Video Switcher hardware.

[0450] Routing of the video data is controlled by routing information which is specified by Video Routing Commands and Video Switch Commands. The playback video data is contained in video data buffers which consist of the compressed video image data and a header containing the site, camera, azimuth, and time stamp.

[0451] The Distribute Video Data sub-level CSC data flow is shown in the data flow diagram FIG. 27. The Distribute Video Data sub-level CSC is composed of the following CSUs:

[0452] Load Video Config From Database CSU

[0453] Modify Video Routing CSU

[0454] Update Camera Azimuth CSU

[0455] Insert Video ID Info CSU

[0456] Output Playback Video CSU

[0457] Control Video Switcher CSU

[0458] Distribute Playback Audio Data CSC (FIG. 28)

[0459] The Distribute Playback Audio Data sub-level CSC controls the distribution of recorded audio data during a playback operation. The routing is controlled by Audio Routing Commands, which are received when the operator sets up a playback operation. The digital audio data is sent to the Digital Voice Recording System for conversion to analog and playback on the designated console.

[0460] The Distribute Playback Audio Data sub-level CSC data flow is shown in the data flow diagram in FIG. 28. The Distribute Playback Audio Data sub-level CSC is composed of the following CSUs:

[0461] Modify Playback Audio Routing CSU

[0462] Output Playback Audio CSU

[0463] Record and Replay CSC (FIG. 29)

[0464] The Record and Replay CSC provides continuous recording of VTS operation data and also provides the capability to replay any existing VTS operation data. All VTS messages, audio data, video data, radar scan data, vessel data, and vessel alarms are recorded on 8 millimeter tape. Up to 116 tapes reside in an helical scan recorder jukebox containing four tape recorder/player units. All tapes in the helical scan recorder jukebox with write access will be recorded upon. If a blank tape exists in the jukebox, it is selected for recording first. If no blank tapes exist, VTS data tapes are overwritten in a circular manner by selecting the tape with the oldest data for recording. Recorded data may be archived by extracting the tape from the jukebox or leaving the tape in the jukebox and marking it read only.

[0465] All data assigned for recording (including audio data, video data, radar scan data, vessel data, and vessel alarms) is extracted from the acquisition buffers and recorded onto a single tape. If a replay request is received which involves data on the tape currently being recorded, data recording is initiated on a second tape. Once the second tape is recording data, recording on the first tape is terminated and the replay request can be processed. If a replay request is received which involves older data, the appropriate tape is loaded and played. Tape identification information is maintained in the ORACLE database, so database reports may be generated to view history tape identification data.

[0466] When performing replay operations all requested data is time correlated, marked as replay data, and placed in the appropriate acquisition buffers.

[0467] The Record and Replay CSC data flow is shown in the data flow diagram FIG. 29. The Record and Replay CSC is composed of the following CSUS:

[0468] Tape Controller

[0469] Jukebox Processing

[0470] Jukebox Control

[0471] Data Recording

[0472] Data Replay

[0473] Tape Processing

[0474] Detailed Design

[0475] Command and Control CSC

[0476] The following subparagraphs identify and describe each of the CSUs that form the Command and Control CSC. Data flows between CSUs that form the Command and Control CSC and external CSU interfaces are shown in data flow diagram 19.

[0477] Command/Response Processing CSU

[0478] The Command/Response Processing CSU initiates the SDS by activating inter-processor communications using UNIX networking routines and the following tasks:

[0479] Message and System Performance Logging (DBP and SDP)

[0480] Character Inserter

[0481] Monitor Sensors

[0482] Data Acquisition

[0483] Monitor UPS Status

[0484] Video Switcher

[0485] Distribute System Time

[0486] Record and Replay

[0487] Track Processing (DBP)

[0488] It then concentrates on its main task of accepting commands from the operator consoles via the FDDI network interface. Each VTS message is dispatched to the appropriate Sensor Data Software function based on the message type:

[0489] Sensor Control Commands are sent to the Control Sensors CSU.

[0490] Track Processing Commands are sent to the Track Processing CSC on the DBP.

[0491] Video Switcher Commands are sent to the Data Distribution Video Switcher CSU.

[0492] Record and Replay Commands are sent to the Record and Replay CSC.

[0493] Command Responses are returned to the originating ODP.

[0494] Vessel Alarm and system error messages are sent to all ODPS.

[0495] System Time messages are sent to all ODPs, RSPs and DBPs.

[0496] UPS Alarm messages are sent to all DBPs and ODPs. A ten minute timer is set for system termination. On the DBP, Command and Control initiates a script to generate the necessary database reports when the UPS Alarm is received. UPS Alarm Cancellation message will deactivate the timer. This message can be sent by the Supervisor or the UPS Monitor CSU when normal status is encountered.

[0497] System Termination message is sent to all DBPs and ODPs, and an orderly shutdown of the SDP/DBP software/hardware is executed.

[0498] Radar scan data is retrieved from the acquisition buffer and transmitted to all ODPs.

[0499] Radar track data is received from Data Acquisition and sent to the DBP Command and Control. It is then placed in an acquisition buffer for use by Track Processing. Command and Control is split into two programs. SDP_CmdCtl handles I/O with the Command Status Daemon on the ODP and Command and Control on the DBP. SDP_RidCtl handles radar scan data transmittal to the Radar Image Daemon on the ODP. This is necessary because UNIX does not allow two communication lines (sockets) from one program. SDP_RidCtl exists only to manage the one-way communication to the ODS Radar Image Daemon.

[0500] An invalid sensor command results in a sensor command response, indicating the error, being returned to the source of the command.

[0501] All VTS messages are stored in an acquisition buffer for recording.

[0502] If this CSU detects any error condition, it generates a message and sends it to the Message Logging CSU for processing.

[0503] System configuration information is retrieved from the equipment_config database table and passed on to the appropriate tasks.

[0504] This CSU manages inter-processor communications using UNIX networking routines. These lines of communication allow data to flow between the SDP and ODP, and the DBP and SDP. VTS messages can be up to 8192 bytes in length, and all must follow the format defined in the Interface Design Document. All Command and Control communications with other CSCs on the SDP are managed through UNIX message queues.

[0505] SDP Switchover is handled automatically by Command and Control. At initialization, Command and Control remotely starts up a backup process on the backup SDP. Communication is initiated between the two to perform a health check. If it is interrupted, the backup SDP can assume control as the server after positively determining the other SDP is no longer the server, and the cycle begins again. All other processors will be made aware of the switched SDP-UNIX notifies a process if an attempt is made to communicate over a downed communication line. These processors will then attempt a reconnection to the new server.

[0506] DBP Switchover is handled by the Database Software.

[0507] Command and Control also handles building of the Radar Configuration command from the ODP. When an operator modifies the Radar Configuration via the SQL Form, the ODS is alerted and passes the site and radar ID that was modified to the SDS. Command and Control retrieves the radar configuration information from the database, builds the Radar Configuration command and submits it to the Control Sensors CSU for transfer to the remote site.

[0508] Message Logging CSU

[0509] The Message Logging CSU receives all error, warning and information messages generated by Sensor Data Software CSCs. Each of these messages is displayed at the generating machine's (SDP or DBP) system console and inserted into the vts_error_log database table. The error and warning messages are then sent on to the Command/Response Processing CSU for transmittal to each ODP.

[0510] The information messages are intended to assist the System Administrator when starting up the Sensor Data Software on the SDP and DBP, and general trouble-shooting.

[0511] There is a maximum number of messages allowed in the table at one time. Once this maximum has been reached, some of the oldest records are deleted allowing space for future messages.

[0512] A sequence number is created by the ORACLE Database Administrator and incremented by the RDBMS. Each time a record is inserted into the table, this sequence number is used for the new record. This uniquely identifies the record (from any task on any processor). Time is only accurate up to seconds and there could be more than one entry in a second. Only the Message Logging task running on the SDP will handle the removal of records.

[0513] System Performance Logging CSU

[0514] The System Performance Logging CSU receives functional performance statistics from the various Sensor Data Software CSCs and stores them in the system_perf_log database table. These statistics are used in system performance reports which indicate the level of usage of system resources and processing capacity. The System Performance Report is operator selectable from the ODS

[0515] System Administration menu.

[0516] Control Sensors CSU

[0517] The Control Sensors CSU transfers sensor commands to the appropriate remote site. It verifies the command contains an appropriate site number, and if it is found to be incorrect, sends a response message to the originator of the request.

[0518] This CSU is also used by the Monitor Sensors CSU to transfer initialization commands requested by a particular remote site. If an error occurs, the Monitor Sensors CSU sends an error message to all operator consoles.

[0519] Upon request for system termination, reboot messages are sent to each Remote Site Processor.

[0520] Monitor Sensors CSU

[0521] The Monitor Sensors CSU receives requests from the remote site for down-loading of the RSP software to the remote site and for device initialization. This CSU also receives sensor status information from the various remote sites, including camera azimuth data.

[0522] Camera azimuth data is passed on to the Data Distribution Character Inserter CSU for processing.

[0523] Sensor command responses are returned to the requesting operator through the Command/Response Processing CSU.

[0524] Remote site alarm notification is logged into the database through the Message Logging CSU and passed on to the ODPs by the Command/Response Processing CSU.

[0525] Sensor status information is stored in the remote_site_equipment_status table in the database. This information includes site number, device ID, device type, time of the status, and text explaining the status. This information is explained in detail in the Interface Design Document. Remote site alarms, software down-load and initialization requests are also entered into this table.

[0526] System performance data is sent to the System Performance Logging CSU for processing.

[0527] System Configuration Information for the Remote Site

[0528] initialization commands are retrieved from the various database configuration tables (remote_site, radar_config, radio_config and camera_config). Sensor initialization commands are formulated using this information and sent to the Control Sensors CSU for transfer to the remote site.

[0529] Monitor UPS Status CSU

[0530] The Monitor UPS Status CSU monitors the VTC UPS for low voltage indication. If such an indication is received, this CSU sends an UPS alarm notification to the Command/Response Processing CSU for transmittal to all remote site processors, operator consoles, and the Database Processor. If an indication of normal status is received, the Command/Response Processing CSU is also notified. All warning messages from the UPS are sent to the Message Logging CSU for processing.

[0531] Distribute System Time CSU

[0532] The Distribute System Time CSU obtains the GPS time from the TPRO-VME Time Board and updates the Sensor Data Processor system time. It then sends it to the Command/Response Processing CSU for transfer to all RSPs, DBPs and ODPs as system time. If the system time and the GPS time difference is greater than five minutes, a warning message is generated and the system time is not updated. The interface to the GPS Time Board is described in the TPRO-VME Synchronizable Time Generator with VME Interface Operation and Maintenance Manual.

[0533] Remote Site Processing CSC

[0534] The following subparagraphs identify and describe each of the CSUs that form the Remote Site Processing CSC. Data flows between CSUs that form the Remote Site Processing CSC and external CSU interfaces are shown in the data flow diagram FIG. 17.

[0535] Remote Site Processor Initialization CSU

[0536] The Remote Site Processor operating system is stored in ROM and begins execution automatically upon power up or reboot. Once the RSP operating system is initialized, it invokes the program RspInit, (also stored in ROM), which performs the following operations:

[0537] 1. Initializes the ram disk.

[0538] 2. Copies the synchronous I/O (RS-422) driver from ROM to RAM.

[0539] 3. Copies the RspServer program from ROM to RAM.

[0540] 4. Starts the RspServer program.

[0541] The purpose of the RspServer program is to receive the RSP application modules that are downloaded from the SDP, as follows:

[0542] 1. Open the synchronous I/O channel to the SDP.

[0543] 2. Send a message to the SDP requesting a download to RSP modules.

[0544] 3. Read messages from the SDP containing the modules being downloaded or commands to be executed. Reset the watchdog timer whenever a message is received.

[0545] 4. If no messages from the SDP are received during a timeout period, the watchdog timer will expire, causing the RSP to reboot.

[0546] 5. The final messages from the SDP cause the RspServer to start the RSP application and terminate itself. At this point, the RSP main task takes control of the RSP.

[0547] RSP Main CSU

[0548] The RSP Main CSU is the “main” program for the RSP software, the RspMain task. It is started after the SDP downloads the RSP executable programs. RspMain creates and initializes the shared memory region which is used for communication between all RSP tasks, including initialization of the buffer queues used to pass messages between RSP tasks. RspMain then creates the other RSP tasks:

[0549] RcvTask:RSP receive message (via RS-422 link) task

[0550] CmdTask:RSP command processing task

[0551] XmtTask:Transmit message (via RS-422 link) task

[0552] CamTask: Camera control task

[0553] CamSioTask:Camera serial I/O task

[0554] RdoTask:Radio control task

[0555] RdrTask:Radar control task

[0556] RdrGetData:Radar data ingest task

[0557] UpsTask:UPS control task

[0558] UpsMonTask:UPS monitoring task

[0559] VidGetData: Video data ingest task (not implemented)

[0560] Once all the RSP tasks are started, RspMain enters an “idle” loop, continuing to run until the termination flag gets set. While in this loop, RspMain sends out NEEDINIT messages to the SDP until the SDP responds with an INITSTRT message.

[0561] When the termination flag gets set, RspMain breaks out of its loop, then kills all the RSP tasks and exits.

[0562] The primary means of interprocess communication within the RSP is using buffer queues to pass messages between tasks. The buffer queues are maintained in a shared memory region. Each task reads its input messages from one queue and sends its output messages to one or more other queues. When a task tries to read from an empty input queue, that task will be suspended until some other task sends a message to that queue.

[0563] The following information lists all the RSP tasks and their corresponding input and output queues:

[0564] The MutexQ module provides primitive queue operations which synchronize access to the queues and ensure queue structure integrity. The primitives in MutexQ encapsulate the operating system features that are used to implement the queue operations, enhancing the portability of RSP source code. Each queue structure uses two semaphore:

[0565] AVAIL—This semaphore maintains a count of the number of buffers in the queue and causes a task to suspend if it tries to read from the queue when the queue is empty. It is decremented when a buffer is removed from the queue (by GetQ) and incremented when a buffer is added to the queue (by PutQ).

[0566] MUTEX—This semaphore provides mutually exclusive access to the queue structure ensuring that only a single task may access or modify the pointers in the queue structure at one time.

[0567] MutexQ provides the following operations:

[0568] IniQ—Initialize a queue structure:

[0569] Set number of entries to 0.

[0570] Set head pointer to NULL.

[0571] Set tail pointer to NULL.

[0572] Create AVAIL semaphore; set its value to zero.

[0573] Create MUTEX semaphore; set its value to zero.

[0574] GetQ—Get Buffer from Queue:

[0575] Wait on AVAIL semaphore for a queue node to be available.

[0576] Wait on MUTEX semaphore for exclusive use of the queue.

[0577] Remove node from head of the queue.

[0578] Decrement the queue counter.

[0579] Signal the MUTEX semaphore to release the queue structure.

[0580] Return the queue node.

[0581] PutQ—Put Buffer on Queue:

[0582] Wait on MUTEX semaphore for exclusive use of the queue.

[0583] Add node to the tail of the queue.

[0584] Increment the queue counter.

[0585] Signal the MUTEX semaphore to release the queue structure.

[0586] Signal the AVAIL semaphore to indicate that a queue node is available.

[0587] The RspBufQ module provides a set of buffer get/put routines for each buffer queue. RSP tasks call these routines to perform all message passing operations. RspBufQ hides all the details from the RSP tasks. The following information lists the Get and Put routines defined in RspBufQ that are used to access each of the queues:

[0588] The RspShm module defines the structure of the shared memory region and provides a set of functions that RSP tasks can call to get the addresses of various items in the shared memory area:

[0589] SHM_CreShm( )—Create Shared Memory.

[0590] SHM_AddrCamCfg( )—Get address of camera configuration.

[0591] SHM_AddrRdoCfg( )—Get address of radio configuration.

[0592] SHM_AddrRdrCfg( )—Get address of radar configuration.

[0593] SHM_AddrRspCfg( )—Get address of RSP configuration.

[0594] SHM_AddrUpsCfg( )—Get address of UPS configuration.

[0595] SHM_AddrQueues( )—Get addresses of buffer queues.

[0596] The SysShrMem module provides routines to create or attach to a shared memory region. Since these operations are highly specific to the operating system, this module hides the details from the RSP tasks.

[0597] SYS_CreShm( )—Create shared memory region.

[0598] SYS_AccShm( )—Access (existing) shared memory region.

[0599] The VME Sys module provides a set of VME or OS-9 operating system specific functions, hiding the details of these operations from the RSP tasks that call these functions:

[0600] RSP_CreateTask)( )—Create an RSP Task.

[0601] RSP_Delay( )—Sleep in {fraction (1/64)} second intervals.

[0602] RSP_BumpDog( )—Reset the Watchdog Timer.

[0603] RSP_ReadDog( )—Read the Watchdog Timer Value.

[0604] RSP_Reboot( )—Reboot RSP (this function never returns!).

[0605] RSP_SetTime( )—Set Time on RSP.

[0606] Receive from VTC CSU

[0607] The Receive from VTC CSU handles the input interface between the Remote Site Processor and the Sensor Data Processor at the VTC.

[0608] This CSU is implemented as a task, called RcvTask, spawned by the RSP main task. It opens the synchronous I/O port for read access, then enters its processing loop, in which it gets an empty buffer from the free command buffer queue, waits for an incoming message from the SDP over the RS-422 synchronous communications link, then puts the command buffer on the RSP command queue for processing by the Dispatch Commands CSU.

[0609] Transmit to VTC CSU

[0610] The Transmit to VTC CSU receives data from the other remote site CSUs and transmits it to the VTC via the RS-422 synchronous communications link.

[0611] This CSU is implemented as a task, called XmtTask, spawned by the RSP main task. It opens the synchronous I/O port for write access, then enters its processing loop in which it reads a buffer from the full transmit buffer queue (it waits if the queue is empty). It gets an empty sync I/O write buffer, then copies the transmit data, enters the site ID and current time into the message header and transmits the buffer to the SDP. The transmit data buffer is then recycled onto the appropriate free buffer queue based on the buffer type.

[0612] Dispatch Commands CSU

[0613] The Dispatch Commands CSU handles the distribution of commands to the appropriate task for processing (e.g., radar commands to the Control Radars CSU), and the execution of some miscellaneous RSP commands.

[0614] This CSU is implemented as a task, called CmdTask, spawned by the RSP main task. It loops indefinitely, reading command messages from the command buffer queue and processing the command messages as follows:

[0615] Camera control commands are sent to the Control Camera CSU (CamTask) via the camera command buffer queue.

[0616] Radio control commands are sent to the Control Radio CSU (RdoTask) via the radio command buffer queue.

[0617] Radar control commands are sent to the Control Radar CSU (RdrTask) via the radar command buffer queue.

[0618] UPS control commands are sent to the Monitor UPS CSU (UpsTask) via the UPS command buffer queue.

[0619] Miscellaneous RSP commands are processed directly (boot, exit, set clock, self-test, bump watchdog, file transfer, etc.).

[0620] Note that the reason this CSU is separate from the Dispatch Commands CSU is to allow command input from sources other than the RS-422 synchronous link. In particular, this arrangement allows for the implementation of a local diagnostics program, which can place commands directly into the RSP command buffer queue.

[0621] Control Cameras CSU

[0622] The Control Cameras CSU controls the CCTV video cameras and mounts at the remote site. It also obtains current azimuth data from each camera mount for transmission to the SDP.

[0623] Camera control is performed using the American Dynamics AD1983 Code Converter, which can support up to 64 cameras. This CSU interfaces with the AD1983 via an RS-232 serial line, as specified in the Interface Design Document. Camera control is effected by inserting the camera number into a two-byte raw code, then transmitting the resulting code over the serial line either continuously or for a specific number repetitions. This CSU supports the following camera control operations:

[0624] Note that the AD1983 does not provide any response to the control codes, so correct operation of the camera can be verified only by observing the camera or its video output.

[0625] A device to read a raw azimuth value is installed in each camera mount. The interface to the camera azimuth feedback unit is described in the Interface Design Document. The camera azimuth feedback device reads a value (in the range 0 to 1023) representing the raw camera azimuth. This value is transmitted to the RSP via an RS-232 serial line at a rate of four updates per second. The format of the azimuth message is as follows:

[0626] Xdddr where:

[0627] X is the ASCII character ‘X’

[0628] d is a hexadecimal digit

[0629] \r is a carriage return

[0630] This CSU reads the azimuth input messages, performs a linear scaling to convert the value to an azimuth in degrees, and transmits the result to the SDP. The coefficients for the scaling operation are supplied as configuration data by the SDP. This CSU also supports manual calibration by allowing the operator to pan the camera to two known positions and “mark” those positions as calibration points. Using the known azimuth values and the raw data values at those two points, this CSU calculates the scaling coefficients, which may be retrieved by the SDP for storage in the database and later retrieval.

[0631] The Control Cameras CSU is implemented by two tasks which communicate through a camera configuration structure in shared memory.

[0632] 1.CamTask

[0633] This task processes incoming camera control commands received from the SDP via the Dispatch Command CSU. This task causes camera control operations to be executed by placing the proper control codes into the camera configuration structure in shared memory, where they are read and transmitted by the CamSioTask. This task supports the following functions, as specified in the IDD:

[0634] Initialize Camera (MSG_CAM_INIT)—Indicates the serial I/O ports to be used for sending control codes and receiving azimuth feedback for the specified camera. This command causes the RSP to initiate serial communication with the given camera control and feedback devices and is required following an RSP reboot before any camera control commands will be accepted.

[0635] Control Camera (MSG_CAM_CTRL)—Specifies one or more camera control operations to be performed. In addition to the operations listed above, the following functions are supported:

[0636] Set Scaling Coefficients

[0637] Mark Calibration Point

[0638] Return Camera Configuration Data

[0639] 2.CamSioTask

[0640] This task continually scans the camera configuration structure for command codes (inserted by CamTask) to be transmitted to the AD1983 and reads the camera azimuth feedback units to obtain raw azimuth data values. Whenever a raw azimuth data value changes, this task scales the data to obtain an azimuth in degrees and transmits a message to the SDP. To support various radio models, the Control Camera CSU is divided into a generic command processing module and a camera-specific (AD1983) module, which contains a set of functions to implement each of the control operations for the particular camera control model.

[0641] In response to a camera initialization command, the command processing module will open the I/O ports to the specified devices and establish a connection to the camera-specific module for the given camera model. It will then return a response message and device status message to the SDP.

[0642] Once camera initialization is complete, the command processing module handles control commands by invoking the camera-specific function corresponding to each bit set in the command operation mask. The operation bit mask allows the SDP to direct the RSP to execute one or more radio control functions with a single camera control command. Each camera-model specific function sets the appropriate command code in the camera configuration data structure for transmission by the CamSioTask.

[0643] A bit corresponding to each operation mask bit is set in the response bit mask to indicate which functions were successfully performed. The response message and a device status message are then sent to the SDP.

[0644] Control Radars CSU

[0645] The Control Radars CSU controls the radar processor and the radar(s) at the remote site. The interface with the radar processor is described in the Interface Design Document. The following operations with the radar processor are supported:

[0646] Setup Scan Converter

[0647] Radar Site Name (20 alphanumeric characters)

[0648] Latitude (ddd:mm:ss.cc N/S)

[0649] Longitude (ddd:mm:ss.cc E/W)

[0650] Range (0.5-300 nm)

[0651] Azimuth Correction

[0652] Distance Offset (0.0-300 nm)

[0653] Azimuth Offset (0.0-359.9 degrees)

[0654] Threshold (0-63)

[0655] STC Range (0.2-25.0 nm)

[0656] STC Level (0.0-48.0 db)

[0657] Clutter Mode (0-7)

[0658] Clutter Level (0-255)

[0659] Fade Rate (0-120 seconds)

[0660] Define Automatic Target Acquisition Zones

[0661] Change range setting

[0662] Test Scan Converter

[0663] Get Track Table Data

[0664] Get Scan Data

[0665] Manually establish track

[0666] Switch to Backup Radar, Switch to Main Radar

[0667] Radar Calibration

[0668] This CSU also accepts status data from the radar processor for transmission to the VTC.

[0669] Control Radios CSU

[0670] The Control Radios CSU controls the VHF-FM radio equipment (transceivers and guard receivers) at the remote site, based on commands received from the SDP via the Dispatch Command CSU. The following radio control commands are supported, as specified in the IDD:

[0671] Initialize Radio (MSG_RDO_INIT)—Indicates the serial I/O port and device address used to control the specified radio unit. This command causes the RSP to initiate serial communication with the given radio and is required following an RSP reboot before any radio control commands will be accepted.

[0672] Control Radio (MSG_RDO_CTRL)—Specifies one or more radio configuration items to be modified, or radio operations to be performed. The following operations are supported.

[0673] Set power (low, medium, high)

[0674] Set mode (U.S. or International)

[0675] Set squelch (adjust up/down or set absolute level)

[0676] Set push to talk (enable, disable)

[0677] Execute built-in test

[0678] Report status

[0679] Select channel (channel number, normal/private/weather, implex/duplex)

[0680] To support various radio models, the Control Radio CSU is divided into a generic command processing module and one or more radio-specific modules, each of which contains a set of functions to implement each of the control operations for the particular radio model.

[0681] In response to a radio initialization command the command processing module will open the I/O port to the specified device, and establish a connection to the radio-specific module for the given radio model. It will then return a response message and device status message to the SDP.

[0682] Once radio initialization is complete, the command processing module handles control commands by invoking the radio-specific function corresponding to each bit set in the command operation mask. The operation bit mask allows the SDP to direct the RSP to execute one or more radio control functions with a single radio control command. Each radio-model specific function transmits the appropriate command code to the radio via the RS- 232 interface and reads the radio response.

[0683] A bit corresponding to each operation mask bit is set in the response bit mask to indicate which functions were successfully performed. The response message and a device status message are then sent to the SDP.

[0684] The control interface with the radios is described in the vendor's interface document.

[0685] Monitor UPS CSU

[0686] The Monitor UPS CSU monitors the Uninterruptible Power Supply (UPS) at the Remote Site. The UPS status is transmitted to the SDP at regular intervals. This unit also accepts commands from the SDP to control the monitoring of the UPS. The following UPS monitoring control commands are supported, as specified in the IDD:

[0687] Initialize UPS (MSG_UPS_INIT)—Indicates the serial port used to monitor the UPS. This command causes the RSP to initiate serial communications with the UPS and begin monitoring the UPS status.

[0688] Control UPS (MSG_UPS_CTRL)—Used to control monitoring of the UPS. The following operations are supported.

[0689] Disable Monitoring

[0690] Enable Monitoring

[0691] Set Monitoring Interval

[0692] To support various possible UPS models, the Monitor UPS CSU is divided into a generic command processing module and one or more UPS-specific modules, each of which contains a set of functions to implement each of the control operations for the particular UPS model.

[0693] In response to an UPS initialization command, the command processing module will open the I/O port to the specified device and establish a connection to the UPS-specific module for the given UPS model. It will then return a response message and device status message to the SDP.

[0694] Once UPS initialization is complete, the command processing module handles control commands by invoking the UPS-specific function corresponding to each bit set in the command operation mask. The operation bit mask allows the SDP to direct the RSP to execute one or more UPS monitoring control functions with a single UPS control command.

[0695] A bit corresponding to each operation mask bit is set in the response bit mask to indicate which functions were successfully performed. The response message and a device status message are then sent to the SDP.

[0696] The UPS Monitoring Unit is composed of two tasks which communicate through the UPS configuration structure in shared memory. The first task, UpsTask, handles incoming UPS commands and controls the other task, UpsMonTask, by placing flags and control values in the UPS configuration structure. The UpsMonTask runs cyclicly. It queries the UPS, reads back the status, and sends a status message to the SDP, then sleeps for the specified interval. If the status is other than nominal, an alarm message is generated and sent to the SDP.

[0697] The interface with the UPS is described in the vendor's interface document.

[0698] Ingest Compressed Video Data CSU

[0699] The Ingest Compressed Video Data CSU reads compressed video data from the JPEG compression board into a buffer. Each buffer of compressed video data is then passed to the Transmit to VTC CSU via a circular buffer queue that is maintained in shared memory.

[0700] Ingest Radar Data CSU

[0701] The Ingest Radar Data CSU is responsible for obtaining radar scan and track data from the Radar Scan Converter. The interface with the Radar Scan Converter is described the Interface Design Document.

[0702] The radar track data is corrected to compensate for uncorrected radar azimuth and range errors, using coefficients determined by the radar calibration procedure, then converted to a common x-y-z coordinate system that is centered at an operator- selected reference point using factors supplied by the Sensor Data Processor as part of the system configuration.

[0703] This CSU then fills a buffer with the stream of data from the Radar Scan Converter. A circular buffer queue is maintained in shared memory between the Ingest Radar Track Data CSU and the Transmit to VTC CSU. The full buffer is passed to the Transmit to VTC CSU.

[0704] The Ingest Radar Scan Data CSU accepts scan data from the Radar Scan Converter. The interface with the Radar Scan Converter is described the Interface Design Document. This CSU fills a buffer with the data received. Each buffer of radar scan data is then passed to the Transmit to VTC CSU via a circular buffer queue that is maintained in shared memory.

[0705] Common Coordinate Conversion CSU

[0706] The Common Coordinate Conversion CSU converts range and bearing data (relative to a specified radar) to the equivalent latitude and longitude for a target. It is invoked by the Ingest Radar Data CSU for each track data sample. The process uses the radar location (latitude, longitude, and height above MSL) and the range and bearing derived from the pixel location provided by the radar processor and uses the WGS-84 earth model as the basis for conversion to geocentric latitude and longitude.

[0707] The longitude is easily calculated using the geocentric y and x coordinates of a target. Calculation of the latitude is too time-consuming to be done in real time. Instead, the latitude is approximated using Bowring's Method. Bowring's method applies correction terms incorporating the eccentricity of the earth ellipsoid to the geocentric coordinates of the target. Once these easily computed correction terms are added in, calculating latitude is as simple as calculating longitude.

[0708] Test results showed average latitude and longitude errors less than one-tenth of a yard for ranges up to 30,000 meters. This degree of accuracy far exceeds that provided by the radar processor.

[0709] Data Acquisition CSC

[0710] The following subparagraphs identify and describe each of the CSUs that form the Data Acquisition CSC. CSUs that form the Data Acquisition CSC include VME RSP to VTC Data Transmission, VME VTC to RSP Data Transmission, RSP to VTC Data Transmission, VTC to RSP Data Transmission, and Input Audio Data. Data flows between CSUs that form the Data Acquisition CSC and external CSU interfaces are shown in the data flow diagram in FIG. 21.

[0711] Data Acquisition communicates with the Remote Site Processing CSC using up to three VME I/O processors residing in the VME chassis. Data is transferred between the processor and VME I/O processors through shared memory.

[0712] VME RSP to VTC Data Transmission CSU

[0713] The VME RSP to VTC Data Transmission CSU collects the remote sensor information that was multiplexed on the RSP and transferred to the SDP by the Remote Site Processing CSC. Sensor information received from each of the remote sites is placed in a shared memory between the and VME, where it resides until it is demultiplexed and processed by other Data Acquisition CSUs.

[0714] As data input occurs, transfer rates are calculated for each remote site and a cumulative transfer rate is calculated for all remote sites, and placed in the performance data tables for status logging. Error messages are written to the status log file if a data transfer error or data overrun occurs.

[0715] VME VTC to RSP Data Transmission CSU

[0716] The VME VTC to RSP Data Transmission CSU distributes remote site commands and configuration data that are received from the VTC to RSP Data Transmission CSU in the form of messages. Remote site messages are received through memory which is shared between the and VME. The remote site number in the message header is used to route the messages.

[0717] As data input occurs, transfer rates are calculated for each remote site and a cumulative transfer rate is calculated for all remote sites, and placed in the performance data tables for status logging. Error messages are written to the status log file if a data transfer error or data overrun occurs.

[0718] RSP to VTC Data Transmission CSU

[0719] The RSP to VTC Data Transmission CSU demultiplexes the sensor information that was multiplexed at each remote site. Sensor information from each site is extracted from the shared memory sensor information input buffers, separated according to sensor type, and placed in acquisition buffers for further processing. Sensor status data is sent to the Sensor Status Routing CSU for transfer to the Command and Control CSC.

[0720] As the remote site data is demultiplexed, ingest rates are calculated for each sensor type from each remote site. If a sensor information input buffer overflow occurs, a message is written to the status log file.

[0721] VTC to RSP Data Transmission CSU

[0722] The VTC to RSP Data Transmission CSU receives remote site commands and configuration data from the Command and Control or Track Processing CSCs in the form of messages. Remote site messages are received through mail boxes. The remote site number in the message header is used to route the messages to the appropriate VME shared memory.

[0723] Error messages are written to the status log file if a data overrun occurs.

[0724] Input Audio Data CSU

[0725] The Input Audio Data CSU receives digitized and compressed audio communication data which originated from remote radios and VTS operators. This audio data is used for recording and transfer rate reporting purposes only. No other use is made of this audio data for live operations.

[0726] Compressed audio data is read from the Digital Voice Recording System, and deposited into circular acquisition buffers for recording by the Record and Replay CSC. As the audio data is input, transfer rates are calculated for channels defined in the system configuration tables. These transfer rates are placed in the performance data tables for performance and status monitoring. If an input errors occurs, an error message is written to the status log file.

[0727] Track Processing CSC

[0728] The following subparagraphs identify and describe each of the CSUs that form the Track Processing CSC. CSUs that form the Track Processing CSC include Overlap Area Monitoring, Locate Duplicate Tracks, Correlated Position Estimation, Automatic Radar Handoff, Target Acquisition, Automatic Vessel Re-Assignment, Drop Track Processing, EP Route Monitoring, Collision Monitoring, Radar Calibration, Traffic Lane Monitoring, Safety Zone Monitoring, Moving Safety Zone Monitoring, Radar Contact Monitoring, Sudden Course/Speed Change Monitoring, Excessive Speed Monitoring, and Sector Monitoring. The Track Processing CSC executes on the Database Processor.

[0729] Overlap Area Monitoring CSU

[0730] The Overlap Area Monitoring CSU checks for, identifies and monitors tracked vessels which are located in an area serviced by multiple radars. Using operator supplied radar overlap definition data, each tracked vessel is checked to see if it resides in a radar overlap area. When a vessel resides in a radar overlap area, a request to identify the vessel on any overlapping radars which are not currently tracking the vessel, is sent to the Locate Duplicate Tracks CSU. This request is repeated periodically until all overlapping radars are tracking the vessel or the vessel exits the radar overlap area.

[0731] Locate Duplicate Tracks CSU

[0732] The Locate Duplicate Tracks CSU starts the multiple radar tracking of vessels which reside in a radar overlap area. A request to identify a vessel on all overlapping radars is received from the Overlap Area Monitoring CSU when a vessel resides in a radar overlap area, but is not being tracked by all overlapping radars. Using operator supplied radar overlap definition data, a command to start vessel tracking on each non-tracking radar is sent through the Remote Site Processing CSC. Once target tracking is started on an overlapping radar, the new track data is validated to insure that the new track data does represent the desired vessel. If the new track data does not represent the desired vessel, a command to drop the track is sent to the Remote Site Processing CSC. If the new track data is validated to represent the desired vessel, duplicate track identification information is placed into the Duplicate Track Table.

[0733] Correlated Position Estimation CSU

[0734] The Correlated Position Estimation CSU correlates radar track data from overlapping radar coverage areas to produce a single best estimate of a vessel's position and velocity. This correlated track data is then written to the SDS track table and is sent to Command and Control for insertion into the INRI Track Database.

[0735] Duplicate track data generated by the Locate Duplicate Tracks CSU is used to identify track data requiring correlation. Track data correlation is performed for each multiply tracked vessel, and the correlated track data is placed into the SDS track table and sent to Command and Control.

[0736] Target Acquisition CSU

[0737] The Target Acquisition CSU extracts live radar data from the data acquisition buffers and writes it to the SDS track table. It also places correlated track data, EP track data, and Vessel ID data into the acquisition buffer for recording. Replay data is read from the acquisition buffer by this CSU and routed accordingly. Replay radar data, which has already been correlated, and replay EP data is sent directly to Command and Control for insertion into the Track Database. Replay vessel identification data and replay vessel alarms are sent to the ODS.

[0738] For each live radar data acquisition buffer record, the track ID is compared to those IDs currently contained in the SDS track table. If a match is found, the position and velocity data associated with the ID in the SDS track table is updated with position and velocity data extracted from the buffer. If no match is found, then new track table records are created for the new track and initialized with the position data extracted from the buffer. A response message is then issued. This message will contain the new SDS track ID if a new track was created. When a command is received that vessel identification information has changed, an SQL*Net call is made to read the updated information from the ORACLE database.

[0739] Automatic Radar Handoff CSU

[0740] The Automatic Radar Handoff CSU hands off radar coverage responsibility when a multiply tracked vessel exits an overlapping radar coverage area. Using operator supplied radar overlap definition data, each vessel identified as residing in a radar overlap area is checked to see if it still resides in that radar overlap area. When a vessel exits a radar overlap area, tracking termination commands are sent through the Remote Site Processing CSC to all radars tracking the vessel except the radar which covers the area in which it emerges. The Duplicate Track Table is updated to indicate that multiple radar tracking is no longer provided.

[0741] If a vessel emerges into an area with no radar coverage, all radars except the original tracking radar are commanded to discontinue tracking. This will give the Radar Contact Monitoring CSU an opportunity to report a radar contact lost alarm.

[0742] Drop Track Processing CSU

[0743] The Drop Track Processing CSU deletes tracks from the SDS track table when commanded to do so. When a message is received to drop a track, the track ID is searched for in the SDS track table. If a track with the requested ID is found, then a pending drop flag is set in the track record. Each cycle (every three seconds), the current status of each track is checked. If the status of a track is TRK_LOST, and its pending drop flag has been set, then the track record is removed from the SDS track table. If the pending drop flag has not been set, an alarm message is issued. In the case of EP tracks, if the pending drop flag is set, the track is deleted. Alarm messages are also issued by this CSU when a track status goes from TRK_TRACKING to TRK_COAST.

[0744] Automatic Vessel Re-Assignment CSU

[0745] The Automatic Vessel Re-Assignment CSU attempts to automatically restart vessel tracking when the EP route transition is complete. When a vessel completes a EP route, a request is received from the EP Route Checking CSU to automatically start tracking the vessel. Using operator supplied radar coverage zone definition data and EP tracking data, a determination is made as to which radar should attempt vessel tracking. A target acquisition command is sent to that radar through the Remote Site Processing CSC. If target acquisition occurs, the track data is validated to ensure that it does represent the desired vessel. If the track data does not fall within expected parameters, a command to drop the track is sent through the Remote Site Processing CSC.

[0746] EP Route Processing CSU

[0747] The EP Route Processing CSU automatically generates EP track data when a vessel is traveling along an operator assigned EP route. When a vessel enters an area without radar coverage, an operator command is received from the ODS to assign that vessel to a predefined EP route. Using operator supplied EP route definition data read from the ORACLE database, last known vessel speed, and an operator assigned location on the EP route, EP track data is generated following the EP route. While the vessel travels the EP route, the operator may make adjustments to the vessel speed or location on the route. When the vessel reaches the EP route end, EP track data generation is stopped, and a request is made of the Automatic Vessel Re-Assignment CSU to restart vessel radar tracking.

[0748] Collision Monitoring CSU

[0749] The Collision Monitoring CSU monitors vessel tracking data to determine when two tracked vessels are in danger of colliding. A circular zone with radius specified by the operator is first constructed about each vessel being tracked. This first screening zone is used to prevent the setting of alarm flags in non-critical situations. For each such zone, if no other vessels are within the zone, the check is halted. If another vessel is found to be within the zone, the closest point of approach and time until closest point of approach for the two vessels is calculated. If this closest point of approach is less than an operator selectable minimum distance, and the TCPA is less than an operator selectable minimum time, a collision alarm message is issued. This alarm message continues to be issued until the alarm condition ceases to exist.

[0750] Calculation of the CPA and TCPA is done in the following way:

[0751] For each vessel, a project-ahead time is available for zone violation and collision monitoring. For collision monitoring, this time can be multiplied by the vessel's velocity to give a distance d. For two vessels having associated distances d1 and d2, a collision check must be performed if the sum of d1 and d2 is greater than the actual distance between the vessels, i.e., if the circle of radius d1 about vessel 1 overlaps the circle of radius d2 about vessel 2.

[0752] Let s1 and s2 be two vessels requiring a collision check. At time t=0, vessel sl is at position (x,y) and s2 is at position (a,b). At time t, s1 is at position (x,y)+t(vx,vy) and s2 is at position (a,b)+t(va,vb), where

[0753] vx=velocity of s1 in x direction

[0754] vy=velocity of s1 in y direction

[0755] va=velocity of s2 in x direction

[0756] vb=velocity of s2 in y direction

[0757] At time t, the distance S between s1 and s2 is given by

[0758] S=([x+tvx−(a+tva)]2+[y+tvy−(b+tvb)]2)½

[0759] What we want to do is to find the time of the closest point of approach. This will be the time at which S is smallest. To calculate it, we need to differentiate the above expression with respect to t and set the result to 0, then solve for t. Let U equal everything inside the radical. Then

[0760] dS/dt=(½)U−1/2dU/dt

[0761] This will be 0 when the numerator is 0, i.e., when dU/dt=0. Now,

[0762] dU/dt=2(xvx−avx−xva+ava+yvy−bvy−yvb+bvb)+2(vx2−vavx−vxva+va2+vy2−vbvy−vyvb+vb2)t

[0763] Setting this to 0 and solving for t gives $t=\frac{-\mathrm{xvx}+\mathrm{avx}+\mathrm{xva}-\mathrm{ava}-\mathrm{yvy}+\mathrm{bvy}+\mathrm{yvb}-\mathrm{bvb}}{\mathrm{vx2}-2\mathrm{vxva}+\mathrm{va2}+\mathrm{vy2}-2\mathrm{vyvb}+\mathrm{vb2}}$

[0764] If two vessels are sufficiently close to require a collision check, the TCPA is computed using the equation above. If the TCPA is less than the threshold value specified by the operator, the CPA is computed. This is done by substituting the TCPA into the distance function. If the resulting CPA is less than the threshold value specified by the operator, then an alarm is issued.

[0765] Radar Calibration CSU

[0766] The Radar Calibration CSU validates the location of multiple fixed targets residing in each radar's coverage area. For each radar, operator supplied system configuration information is maintained which specifies surveyed locations and maximum error offsets for fixed targets. At 1 hour intervals, the Radar Calibration CSU starts tracking the fixed targets for each radar, then calculates the error difference between the surveyed location and the radar return location. The error amount for each surveyed location is placed in the performance and status tables, where it can be requested for display by a system operator. If any error amount is greater then the maximum allowed error amount for the surveyed location, a radar calibration error message is broadcast to all operator consoles for display and written to the status log.

[0767] Traffic Lane Monitoring CSU

[0768] The Traffic Lane Monitoring CSU monitors vessel tracking data to determine when a vessel approaches within an operator selected distance of either side of a traffic lane. Using operator supplied traffic lane definition data read from the ORACLE database and vessel tracking data, each tracked vessel's position and direction is checked to see if the vessel is within an operator selected distance from a traffic lane and is heading toward the traffic lane. A traffic lane violation alarm message is issued for any vessel which violates a traffic lane. This alarm continues to be issued until the alarm condition no longer exists.

[0769] Safety Zone Monitoring CSU

[0770] The Safety Zone Monitoring CSU monitors vessel tracking data to determine when a vessel violates a stationary or circular moving safety zone. Using operator supplied safety zone definition data and vessel tracking data, each tracked vessel's position and direction is checked to see if the vessel is within an operator selectable distance from a safety zone and is heading toward the safety zone boundary. Safety zones can be defined as multiple line segments, as a distance from a stationary point, or as a distance from a tracked object. A safety zone violation alarm message is issued for any vessel which violates a safety zone. This alarm message continues to be issued until the alarm condition no longer exists.

[0771] The algorithm used to monitor safety zones (as well as traffic lanes) is as follows:

[0772] Safety zones can be either circular or polyline; circular zones are defined by a center point and radius, while polyline zones are defined by a set of line segment endpoints.

[0773] The potentially large numbers of tracks and zones processed by VTS makes it impractical to check every zone for each vessel on every cycle. For a given vessel, the majority of safety zones likely will be “far away”, so such exhaustive checking really isn't necessary. What Track Processing does, then, is to determine the zones that are “near” (determined by alarm criteria provided by the operator) to a vessel. These near zones are checked each cycle, while far zones are checked less frequently.

[0774] Two algorithms are required: one to check for nearness to a zone, and the other to check for an actual zone violation. The first determines if a vessel is within a given distance of a zone, and the second determines if, when the vessel is projected ahead an operator defined time using its speed and heading, it will cross a zone boundary.

[0775] First, the nearness algorithm:

[0776] Consider a vessel at point (a,b); a segment of a safety zone having endpoints (x0,y0) and (x1,y1); and a distance r. The vessel is within a distance r of the segment if:

[0777] (A) Either endpoint of the segment lies within the circle of radius r about (a,b), or

[0778] (B) If neither endpoint lies within the circle, but a subsegment of the segment does; in other words, if the segment intersects the circle at two points.

[0779] Checking for (A) is straightforward. To check for (B), we can start with the equation of the circle and the line segment. For the circle we have:

[0780] (x−a)2+(y−b)2=r2  (1)

[0781] and for the line segment, parameterized by the variable t, we have:

[0782] (x0,y0)+t(x1−x0,y1−y0)0<=t<=1.  (2)

[0783] The circle and segment intersect if there exists a value t between 0 and 1 such that the resulting coordinate pair in (2) also satisfies (1). This value, if it exists, can be found by substituting the coordinates from (2) into (1) and solving for t, i.e., solving the following equation:

[0784] (x0+t(x1−x0)−a)2+(y0+t(y1−y0)−b)2=r2  (3)

[0785] This is a quadratic equation with roots

[0786] t0=(−B+sqrt(B2−4AC))/2A

[0787] t1=(−B−sqrt(B2−4AC))/2A

[0788] where

[0789] A=(x1−x0)2+(y1−y0)2

[0790] B=2[(x0−a) (x1−x0)+(y0−b) (y1−y0)]

[0791] C=(x0−a)2+(y0−b)2−r2

[0792] Note that if the discriminant is negative, then there are no real roots and therefore no intersection. The algorithm is then:

[0793] 1. Check if either endpoint of the segment is inside the circle. If so, flag the zone as a near zone. If not, go to step 2.

[0794] 2. Calculate the discriminant. If it is negative, then the equation has no real solutions, exit; otherwise, go to step 3.

[0795] 3. Calculate the roots t0 and t1. If either lies between 0 and 1, then flag the zone as near. Here is the zone violation algorithm:

[0796] The first step is to project the vessel ahead using its speed, heading, and project-ahead time. If the vessel has speed s, then in time t it will have moved a distance d=st. If the vessel has heading b, then its new X coordinate will be dsin(b) and its new Y coordinate will be dcos (b).

[0797] For circular safety zones, the radius of the zone is then compared to the distance between the project-ahead vessel position and the zone's center. If the radius is larger, then a zone violation has occurred.

[0798] For polyline zones, a line segment is drawn between the vessel's current location and project-ahead location. This line segment is then checked for intersection with each line segment in the zone definition, or until an intersection is found. An intersection indicates a zone violation.

[0799] Whether or not two segments intersect is determined in the following way:

[0800] Let segment 1 have endpoints (x0,y0) and (x1,y1), and segment 2 have endpoints (a0,b0) and (a1,b1). Using the variables t and w, where t and w are in [0,1], we can parameterize the segments:

[0801] segment 1: (x0,y0)+(x1−x0,y1−y0)t

[0802] segment 2: (a0,b0)+(a1−a0,b1−b0)t

[0803] The two segments intersect if there exists t and w in [0,1] such that

[0804] (x0,y0)+(x1−x0,y1−y0)t=(a0,b0)+(a1−a0,b1−b0)w.  (4)

[0805] Using a vessel-centered coordinate system, we can set x0=0 and y0=0. We then solve the following two equations (from 4 above) simultaneously for t and w:

[0806] x1t=a0+(a1−a0)w

[0807] y1t=b0+(b1−b0)w

[0808] The solution is

[0809] w=(b0x1−a0y1)/(y1(a1−a0)−x1(b1−b0))

[0810] t=(a0+w(a1−a0))/x1

[0811] If both w and t are in [0,1], then the segments intersect.

[0812] Moving Safety Zone Monitoring CSU

[0813] The Moving Safety Zone Monitoring CSU monitors vessel tracking data to determine when a vessel violates a non-circular moving safety zone. Simple circular moving safety zone monitoring is done by the Stationary Safety Zone Monitoring CSU. A non-circular moving safety zone is defined by the operator as a set of line segments about a given vessel. As the vessel moves, the line segments retain their relative positions about it. The position of each tracked vessel is checked to see if the vessel is within an operator selectable distance from any moving safety zone, and if it is heading toward the safety zone boundary. If both conditions are met, then a safety zone violation alarm flag is set in the track data table for the vessel. The alarm flag remains set until an operator command acknowledging the alarm is received from the ODS, and the alarm condition no longer exists.

[0814] Radar Contact Monitoring CSU

[0815] The Radar Contact Monitoring CSU checks incoming track data to determine if radar contact has been lost. With each pass of each radar, the track status fields returned by the RSP are checked for LOST or COASTING tracks. When a track is found to be COASTING, an alarm message is issued to the ODS. When a track is found to be LOST, if the drop pending flag in the SDS track table has been set for the track (indicating that a drop track message has been received), the track is removed from the SDS track table and no further track updates are made to the Track Database. If the drop pending flag has not been set, an alarm message is issued to the ODS.

[0816] Sudden Course/Speed Change Monitoring CSU

[0817] The Sudden Course/Speed Change Monitoring CSU monitors vessel course and/or speed changes to determine if they violate change criteria. To start course/speed change monitoring, an operator command is received from the ODS identifying the vessel to monitor, course change limit, course change time, speed change limit, and speed change time. For the specified vessel, a table of most recent track data is maintained which contains enough samples to cover the longest specified time. As each new track data sample is received it is compared with the sample separated by the operator specified time to see if a course or speed change violation has occurred. If a violation occurs, a course or speed change alarm flag is set in the track data table for the violating vessel. These alarms remain set until an operator command acknowledging the alarm is received from the ODS, and the alarm condition no longer exists.

[0818] Excessive Speed Monitoring CSU

[0819] The Excessive Speed Monitoring CSU monitors vessel speed to determine if it violates an operator defined maximum. To start speed monitoring, an operator command is received from the ODS identifying the vessel to monitor and maximum allowed speed. As each new track data sample for the specified vessel is received, vessel speed is compared with the maximum allowed vessel speed to see if a speed violation has occurred. If a violation occurs, a maximum speed violation alarm flag is set in the track data table for the violating vessel. This alarm remains set until an operator command acknowledging the alarm is received from the ODS, and the alarm condition no longer exists.

[0820] Sector Monitoring CSU

[0821] The sector monitoring CSU performs two tasks: the first is to determine which sector(s) a vessel is contained in, and the second is to notify the operator when a vessel is approaching a sector boundary.

[0822] The first task is accomplished in the following way:

[0823] Let C be a closed curve (sector) in the plane, Y a point in the plane outside of C, and X any other point in the plane. Let L be the line segment with endpoints X and Y. Then X is inside of C if L intersects C an odd number of times; otherwise, X is outside of C.

[0824] A point Y is selected with latitude and longitude clearly outside all operator sectors. For each vessel, a line segment L is constructed between the vessel and Y. For each sector S, the number of intersections between L and S is counted. If this number is odd, then the vessel is inside of S; otherwise, the vessel is outside of S.

[0825] The second task is performed exactly the same as for stationary safety zones.

[0826] Data Distribution CSC

[0827] The following subparagraphs identify and describe each of the CSUs that form the Data Distribution CSC. Data flows between CSUs that form the Data Distribution CSC and external CSU interfaces are shown in the data flow in FIGS. 26, 27, and 28.

[0828] Load Video Config From Database CSU

[0829] The Load Video Config From Database CSU is invoked at system startup to retrieve the stored video routing and video insertion setup information from the system configuration database. Embedded Oracle SQL*Net commands are used to obtain the information from the Database Processor. The information retrieved is entered into the Video Insertion Info Table, which contains the data to be inserted into each video channel, as well as routing data for playback video.

[0830] Modify Video Routing CSU

[0831] The Modify Video Routing CSU accepts video routing commands from the operator which specify the routing of video data during a playback operation. It updates the Video Insertion Info Table with the data.

[0832] Update Camera Azimuth Info CSU

[0833] The Update Camera Azimuth Info CSU accepts messages from the RSP to update the azimuth value for a specified camera and updates the Video Insertion Info Table accordingly. Note that camera azimuth information messages are received only for live video channels. For playback video channels, the azimuth is obtained from the video buffer header.

[0834] Insert Video ID Info CSU

[0835] The Insert Video ID Info CSU handles the interface to the Video Insertion Unit hardware. It retrieves video insertion info from the table and transmits corresponding control commands to the Video Insertion Unit, and monitors the status information returned. The control commands for the Video Insertion Unit and the status information returned is described in the Interface Design Document.

[0836] Output Playback Video CSU

[0837] The Output Playback Video CSU reads buffers of playback video data from the Acquisition Buffers. Using the site and camera identification from the buffer header, it extracts the playback channel information from the Video Insertion Info Table to determine the correct playback channel for this buffer. The video identification information (site, camera, azimuth, and time) are sent to the Insert Video Id Info Unit, along with an indicator that this is playback data, so that playback data may be easily distinguished from live data by the operator. The video data buffer is then sent to the proper playback channel for decompression and display. The interface to the JPEG video compression/decompression hardware is described in the Interface Design Document.

[0838] This CSU also maintains a count of the number of live and playback video data buffers processed in a given time period and checks how full the video data queues in the Acquisition Buffers are. This information is placed in the performance data tables for performance and status monitoring.

[0839] Control Video Switcher CSU

[0840] The Control Video Switcher CSU manages the interface with the Video Switcher hardware. It accepts video channel assignment commands from the ODS. Based on the given commands, control signals are sent to the Video Switcher to direct specified video inputs to be routed to specified CCTV monitors and VCRs. The status returned from the Video Switcher is used to provide responses to the user. The control commands for the Video Switcher and the status information returned are described in the Interface Design Document.

[0841] Modify Playback Audio Routing CSU

[0842] The Modify Playback Audio Routing CSU maintains a table of routing information which specifies which playback audio data is to be sent to the audio digitizing system for decompression and conversion to analog. This CSU maintains a table for the audio channels allocated to playback. Each playback channel is assigned to playback audio data recorded from a given remote site transceiver/receiver. It accepts audio distribution commands from an operator at a display console as part of setting up a playback operation.

[0843] Output Playback Audio CSU

[0844] The Output Playback Audio CSU reads playback audio data buffers from the playback Acquisition Buffers. The buffer header is examined to determine which remote site radio is the source of the data. The routing table is then used to determine which audio channel is to receive the audio data from that source. The playback audio data is then transmitted to the audio routing system. The interface to the audio routing system is described in the Interface Design Document.

[0845] This CSU also maintains a count of the number of playback audio data buffers processed in a given time period and checks how full the playback audio data queues in the Acquisition Buffers are. This information is placed in the performance data tables for performance and status monitoring.

[0846] Video Switcher CSU

[0847] The Video Switcher CSU routes video input signals to operator selected video output channels. Using the ODP touch panel, the operator selects the input signal and a monitor for display. Initial set-up information is retrieved from the video_switcher_input and video_switcher_output database tables.

[0848] Character Inserter CSU

[0849] The Character Inserter CSU initializes the location for channel numbers, azimuth position and time for the Video Character Inserter. After initialization, it awaits camera azimuth position data from each RSP, and updates the Video Character Inserter camera azimuth as necessary. Initial set-up information is retrieved from the video_insertion database table.

[0850] Record And Replay CSC

[0851] The following subparagraphs identify and describe each of the CSUs that form the Record and Replay CSC. CSUs that form the Record and Replay CSC include: Tape Controller, Jukebox Control, Data Recording, Data Replay, and Tape Processing.

[0852] Tape Controller CSU

[0853] The Tape Controller CSU coordinates all accesses to the helical scan recorder Jukebox and all helical scan recorder Tape drives. The Tape Controller CSU provides the following functions for Data Recording (automated mode):

[0854] 1. Queries the Tape Information Database to determine what tape will be used next for recording data.

[0855] 2. Assigns the next available helical scan recorder drive unit for recording and loads the designated tape into the drive.

[0856] 3. Commands the Data Record CSU to initiate recording on the selected drive and tape.

[0857] When a new tape for recording is required, blank tapes are selected first. If no blanks are available, the tape containing the oldest data and having write access is chosen. The Tape Controller CSU also provides manual operation for assigning tapes to specific drives for recording.

[0858] For Data Replay, the Tape Controller CSU performs the following functions:

[0859] 1. Queries the Tape Information Database to determine on what tape the requested replay data resides.

[0860] 2. Assigns an available helical scan recorder drive unit for replay and loads the designated tape into the drive.

[0861] 3. Commands the Data Replay CSU to initiate replay on the selected drive and tape.

[0862] Operator generated tape manipulation commands are received by the Tape Controller CSU from the ODS or via a stand-alone utility running on the SDP. These commands include allowing the operator to add new tapes to the jukebox, extract tapes from the jukebox, and switch a tape's status between read/write and read only, and various other system administrator commands. Operators may view the tape database contents using reports that are available through standard ORACLE report generation features.

[0863] Jukebox Control CSU

[0864] The Jukebox Control CSU provides the interface between the off the shelf Jukebox processing CSU and the Tape Controller CSU. Tape control commands received from the Tape Controller CSU are converted into the actual command sequences required to perform the requested function. These command sequences are then sent to the Jukebox which performs the requested function. Status information received from the Jukebox is returned to the Tape Controller CSU for analysis and distribution. Any command that results in changing the location or content of a tape causes updates to the tape database, which maintains an up to date record of all tapes.

[0865] Data Recording CSU

[0866] The Data Recording CSU performs sequential recording of audio data, video data, radar scan data, radar track data, vessel data, vessel alarms, and all VTS messages. Data is obtained from acquisition buffers and written to a temporary disk file. The Tape Processing CSU is then commanded to record the temporary disk file onto the tape. Two temporary disk files are used to facilitate a double-buffering scheme for recording data to tape. Once the tape is full (or recording is terminated upon request), the Data Recording CSU terminates the recording process for the specified tape, updates the Tape Information Database, ejects the tape, and sends a “finished with tape” response back to the Tape Controller CSU. Note: the Tape Controller CSU is responsible for returning the tape to the appropriate Jukebox bin and initiating other recording requests (i.e., the Data Recording CSU is controlled by the Tape Controller CSU).

[0867] Upon completion of data recording on a tape, the Data Recording CSU updates the Tape Information Database that resides in the ORACLE database and includes tape ID, recording start date/time, recording stop date/time, tape location, and write access permissions. This information is kept for all tapes residing within the jukebox or extracted from the jukebox.

[0868] Data Replay CSU

[0869] The Data Replay CSU provides sequential replay of audio data, video data, radar scan data, radar track data, vessel data, vessel alarms, and all VTS messages. Data is obtained by issuing a Tape Read Request to the Tape Driver. Data thus obtained from tape is written to one of two temporary disk files. Two temporary disk files are used to facilitate a double-buffering scheme for replaying data.

[0870] In the future, it is planned for the sensor data to be provided to the Data Distribution CSC. Audio data, video data, and radar scan data may be placed in parallel replay acquisition buffers. Radar track data and alarms may be placed in parallel replay track and alarm data tables, and the vessel data may be placed in a parallel replay section of the ORACLE database.

[0871] Tape Processing CSU

[0872] The Tape Processing CSU provides the interface between the helical scan recorder tape drives and both the Data Recording and Data Replay CSUs. All tape drive control commands are received by the Tape Processing CSU, processed, and then the specific helical scan recorder tape drive function (or functions) is performed. A status response is then returned to the initiating CSU.

[0873] CSCI Data Files

[0874] This following subparagraphs contain descriptions of each of the shared data files of this CSCI.

[0875] Data File to CSC/CSU Cross Reference

[0876] ORACLE Database

[0877] The ORACLE Database is accessed by this CSCI using a structured query language. Information residing in the ORACLE Database that is used by this CSCI includes: system configuration data, tape tracking data, video data, vessel data, alarm data, and VTS error and system performance logs.

[0878] Long Term History

[0879] Long Term History files are recorded onto and replayed from multiple 8 millimeter tapes. Tape recording and replay is performed with sequential access methods using record sizes dependent upon the data volume requiring recording.

[0880] Database Software Overview

[0881] The Database Software CSCI is responsible for database design, report processing, vessel identification processing, database synchronization and recovery, database archive and restore, and performance tuning of the Oracle database.

[0882] DBS interfaces with the SDS and ODS CSCIs are primarily through embedded SQL calls to Oracle tables. Since these calls are a part of the SDS and ODS software, the DBS role is a passive one—limited to providing appropriate table designs. The ODS CSCI also invokes DBS forms and the DBS main menu and gains access to all DBS menus, forms, and reports. The DBS role, as mentioned earlier, is a passive one because these calls can also be made from the Unix command line.

[0883] There are three external interfaces that directly involve DBS software. One of these involves the radar configuration form. When radar configuration data is modified, DBS communicates the change to SDS through a C user exit. The other two involve the vessel ID and search screens. ODS calls a C program that invokes the vessel search form and returns status information. When a vessel is selected, the vessel search form calls a C user exit that updates the Tactical Database Manager (TDBM)

[0884] The DBS provides the following capabilities:

[0885] Database mirroring, shutdown, and recovery. Redundant disk and processor configurations to minimize database server downtime. The DBS performs UPS/VTS shutdown processing based on an input from SDS.

[0886] Non-Map definition storage is provided by the DBS for all ODS display consoles.

[0887] Maintenance screens are provided for the transit movement database.

[0888] System configuration definition is maintained in the ORACLE database.

[0889] User access definition is provided for authorization, security control and classification of users.

[0890] The traffic summary report provides traffic movement information.

[0891] Log Recording and detail report data support.

[0892] Ad Hoc Query for casual reporting requirements and extraction of data in special formats for further processing.

[0893] On-line Built-in-test functions for ensuring operability and performance monitoring for troubleshooting.

[0894] Printer output for all ODS display and all other VTS printed reports.

[0895] CSCI Architecture

[0896] The DBS architecture utilizes the ORACLE Relational Database Management System. It is derived from a methodology that is well- suited for ORACLE and the associated development tools.

[0897] The logical database design is the central focus of DBS architecture. It is the basis for most of the CSUs in the subsystem. Physical database design and performance tuning is conducted after CSU development and data conversion. Tasks and CSUs required for operational support are also addressed. This CSCI contains the following CSC's:

[0898] SQL*MENU CSC

[0899] SQL*FORMS CSC

[0900] C&PRO*C CSC

[0901] Data Conversion CSC

[0902] Operational Support CSC

[0903] Methodology

[0904] The application development methodology used for DBS is data-driven and predicated on the use of Oracle 4GL development tools, including SQL*Forms, SQL*Menu, Pro*C, and SQL*Loader. It entails logical database design, application design and development, data conversion, and physical database design.

[0905] Logical database design starts with a study of both data and processes. The goal is to identify and define entities and attributes. A preliminary implementation of the application database is done by creating a table for each entity, where each attribute becomes a column.

[0906] The definition of entities is a prerequisite for application design using SQL*Forms. This is because a form contains one or more blocks, where each block is based on a table. SQL*Menu is used to tie together SQL*Forms modules and provide user-based access privileges to both menus and forms. SQL and PL/SQL scripts are used for simple processing and report generation. When more complex logic is required, C and Pro*C functions are used.

[0907] SQL*Loader is used for data conversion involving large volumes. Code tables are loaded using SQL*Forms modules.

[0908] Physical database design involves the definition of indexes and space management. This is done during performance tuning which includes both application and Oracle kernel tuning.

[0909] Logical Database Design

[0910] Logical database design involves the identification and definition of entities and attributes. An entity is an abstraction of interest to the application. An attribute is a fact about an entity.

[0911] While studying the data and processes of the application, the rules of data normalization are applied to the entities initially identified. In theory, an entity relationship model (logical database design) is complete when it is in fifth normal form. Since such a high degree of normalization is never practical due to performance reasons, the database is de- normalized during performance tuning.

[0912] This entails substantial modifications to SQL*Forms modules, which are table-based. To avoid this re-work, it is more practical to leave the database in second or third normal form. A database is in third normal form when each attribute is a fact about the complete concatenated key.

[0913] Application Modules

[0914] DBS application modules are written in SQL*Forms, SQL*Menu, SQL, PL/SQL, C, and Pro*C. SQL*Forms provides full-screen access to VTS tables, including a powerful ad-hoc capability. SQL is used for simple reports and batch-processing. PL/SQL is used for more complex processing and for triggers in SQL*Forms. Pro*C functions are used for user exits in SQL*Forms, and for reports and processing that are beyond the capabilities of SQL and PL/SQL. C functions are used to provide bridges between DBS modules and the ODS/SDS subsystems. SQL*Menu ties the DBS modules together and provides secured access to VTS users.

[0915] SQL*Forms provides default I/O and query capabilities for each block in a form. The query capabilities in particular are very powerful and would take many person-years of effort to duplicate in a custom application. To avail of these default capabilities, it is necessary to adhere to the block-based structure of SQL*Forms. In practice, this requires some stringent design and layout restrictions. Very seldom do these restrictions constrain the functionality of an application. In those rare cases where they do, it is more economical to use Pro*C instead of SQL*Forms, rather than try to circumvent them. In the DBS subsystem, all modules that involve screen I/O are written in SQL*Forms.

[0916] SQL*Menu provides a consistent and easy-to-develop means of tying together the DBS modules. It also provides a layer of security at the application level, in addition to that implemented at the database level. Depending on the user's access level, the contents of a menu can be dynamically changed at run-time.

[0917] SQL is the standard interface to an RDBMS. PL/SQL introduces procedural capabilities in SQL, which is non-procedural by design. Pro*C allows SQL to be embedded in C functions. All of these tools are used in developing DBS modules.

[0918] Data Conversion

[0919] Data from the Marine Safety Management System is used for the initial load of vessel information. This data is obtained in flat files and loaded into Oracle tables using SQL*Loader.

[0920] DBS also uses several code tables to validate input data.

[0921] These tables contain small volumes of data. Both SQL*Loader and SQL*Forms modules are used to load this data.

[0922] Physical Database Design

[0923] Physical Database Design involves the definition of indexes and space management. It is done during performance tuning, which includes both application and Oracle kernel tuning.

[0924] Data volume estimates are compiled and reviewed for each of the logical tables. Application modules and SQL statements are reviewed to define transactions and usage frequencies. This information is the basis for denormalization, clustering, index definition, block organization, data and index segment definitions, and tablespace and data file definitions.

[0925] Application tuning is focused primarily on the construction of SQL statements so that the use and non-use of indexes is deliberate. The wording of an SQL statement can cause the query optimizer to follow different access paths. Application tuning also involves array processing, cursor management, and transaction definition.

[0926] Oracle database tuning entails the management of kernel parameters to ensure optimal through-put for all applications. Optimization involves efforts in the following areas: data buffer cache, dictionary cache, rollback segments, redo logs, disk drive contention, sorts, free lists, checkpoints, and init.ora parameters such as sessions, processes, transactions, Data Manipulation Locks, Data Definition Locks, etc.

[0927] Operations Support

[0928] This category includes activities that are critical to DBS performance. This includes shutdown processing, database processor shadowing, printer output, and built in test.

[0929] System States and Modes

[0930] The Database Software supports operation in both live and data simulation modes. The live mode supports continuous uninterrupted system operation, including: configuration updates, log information, vessel information, shutdown processing, hardcopy display prints, and built in test. The live mode provides for reports and data administration.

[0931] Memory and Processing Time Allocation

[0932] There are two DBPs. Each DBP has 96 megabytes, in the current implementation expandable up to 384 Mbytes, of memory to perform system, DBS, and other operations. DBS program processes share application memory with the SDS track processes and the Government Off The Shelf (GOTS) TDBM server executing on the DBP.

[0933] CSCI Design Description

[0934] The DBS CSCI is divided into five CSCs. The following sections describe each of these components.

[0935] SQL*Menu CSC

[0936] The DBS menus are written in SQL*Menu. They provide access to all DBS forms and reports. Based upon a user's access level, the same menu may show a different set of selections.

[0937] SQL*Forms CSC

[0938] A form provides access to one or more tables. There will be, at a minimum, one form designed for each table residing on the DBP for the purpose of maintaining the data contained in that table. As a result,even when a table is expected to be accessed only through SDS or ODS software, a default form will still be provided.

[0939] C & Pro*C CSC

[0940] These modules represent functions written in C or Pro*C. This includes user exits called from SQL*Forms, bridge functions used to call SQL*Forms from ODS, and reports programs.

[0941] Data Conversion CSC

[0942] This component uses SQL*Loader modules to initially load data from flat files. This includes vessel data and code table information. Where data volumes are small, SQL*Forms screens developed for maintenance are also used for the initial data load.

[0943] Operations Support CSC

[0944] These modules provide operational support and fulfill one or more DBS requirements. The CSUs included in this component are shutdown processing, database processor shadowing, printer output, built in test, backup/recovery, and archive/restore functionality for vessel ID, vessel transit, remote site equipment status, and VTS error log tables.

[0945] Detailed Design

[0946] This section defines all computer software units that comprise the DBS subsystem. These units are grouped into five computer software components: menus, forms, C & Pro*C functions, data conversion, and operations support.

[0947] General detailed design information includes: input/output data elements, local data elements, interrupts and signal, algorithms, error handling, data conversion, logic flow, data structures, local data files, and limitations. Not all of these items apply to the DBS CSCI. The use of Oracle 4GL tools results in most of this information being standardized and moved from the application to the database, (e.g., interrupts and signals, logic flow, local data files). Consequently, these considerations are covered at the CSU level on an exception basis only. The INP and DMM files generated for forms and menus contain detail information on input/output data elements, edit algorithms, and error handling.

[0948] SQL*Menu CSC

[0949] The DBS menus are written in SQL*Menu. They provide access to all DBS forms and reports. Based upon a user's access level, the same menu may show a different set of selections.

[0950] The DBS main menu is invoked from the Unix command line. It may also be called from the ODS CSCI.

[0951] DBS Main Menu CSU

[0952] This is the main database menu that is displayed to users when they log into the system. The main menu consists of sub- menus and forms available to the users allowing them to utilize the system. The selections are System Administration Menu, Vessel Status Menu, Reports Menu, Vessel Administration Menu, Pilot Screen, and Vessel Transit History Screen. Refer to FIGS. 30 and 31 for both a flowchart showing what is called from this menu and a picture of the actual menu.

[0953] System Administration Menu CSU

[0954] This menu is called from the DBS main menu. It consists of selections for the following screens: user authorization, equipment administration, sector administration, docks administration, anchorage administration. Upon selecting an option, the menu transfers control to the corresponding SQL*Forms module, which in turn, provides access to an Oracle table. See FIG. 32 for a sample of this menu.

[0955] Equipment Administration Menu CSU

[0956] This menu is called from the system administration menu. It is used to access the forms that add and maintain the equipment configuration, remote site configuration, radar configuration, radio configuration, record replay configuration, remote site equipment status, camera configuration, video insertion configuration, and video switcher configuration. Upon selecting an option the menu transfers control to the corresponding SQL*Forms module, which, in turn, provides access to an Oracle table. See FIG. 33 for a sample of this menu.

[0957] Vessel Status Menu CSU

[0958] This menu is called from the main menu. It consists of selections for the anchored list, docked list, and prospective list forms, and for previous menu. After a list selection is made the appropriate SQL*Forms screen is presented. See FIG. 34 for a picture of the menu screen.

[0959] Report Menu CSU

[0960] This menu is called from the DBS main menu. It consists of selections for the traffic summary reports. Upon making a selection, a SQL*Forms screen is presented to obtain parameters for the selected report. See FIG. 35 for a sample of this menu.

[0961] Vessel Administration Menu CSU

[0962] This menu is called from the DBS main menu. It consists of selections for the vessel support data screen, registry type, country, category, special category, and units. Upon selecting any of these options, the menu transfers control to the corresponding SQL*Forms module, which in turn, provides access to an Oracle table. While working with the support data screen, the screens are also accessible as pop-up windows. See FIG. 36 for a sample of this menu.

[0963] Logs Menu CSU

[0964] This menu is called from the DBS main menu. It consists of the VTS error log. Upon selecting an option, the menu transfers control to the corresponding SQL*Forms module, which, in turn, provides access to an Oracle table. See FIG. 37 for a sample of this menu.

[0965] SQL*Forms CSC

[0966] A form provides access to one or more tables. There usually will be at least one form designed for each table residing on the DBP for the purpose of maintaining the data contained in that table. Some tables are actively used and maintained by ODS and SDS. These tables have no form created for them unless the user needs to see the information in the table.

[0967] User Authorization CSU

[0968] This form is called from the system administration menu. It is used by the administrator for enrolling new users, granting privileges, deleting users, and revoking privileges. This data is stored in the cgvts_auth table. See FIG. 38 for a sample of this screen.

[0969] Sector Administration

[0970] The sector administration form is used to configure the system. The sectors are set up and associated with remote sites. A copy of this screen is in FIG. 39.

[0971] Docks CSU

[0972] This form is used to access and update the docks table. The 15 table contains all valid dock locations. The form can be accessed from the docks administration menu. See FIG. 40 for a sample of this screen.

[0973] Anchorage CSU

[0974] This form is used to access and update the anchor table. The table contains all valid anchor locations. The form can be accessed from the anchorage administration menu. See FIG. 41 for a sample of this screen.

[0975] Equipment Configuration CSU

[0976] This form is called from the equipment configuration menu. It allows the user to query and maintain the equipment_config table. See FIG. 42 for a sample of this screen.

[0977] Remote Site Configuration CSU

[0978] This form is called from the system administration menu. It is used to maintain the configuration of remote sites. The form is used to query, add, and modify data in the remote_site table. See FIG. 43 for a sample of this screen.

[0979] Radar Configuration CSU

[0980] This is a 2 page form and is called from the equipment configuration menu and allows the user to query and update the radar configuration data. This form is only used by the system administrator. This data is stored in the radar_config table. See FIGS. 44 and 45 for a sample of this form.

[0981] Radar Set CSU

[0982] This form is called from GOTS and allows the user to query and update the radar operation data. This data is stored in the radar_config table. See FIG. 46 for a sample of this form.

[0983] Radio Configuration CSU

[0984] This form, called from the equipment administration menu, is used to configure, monitor, and maintain the configuration of the radio equipment. It is used to query, add, and modify data in the radio_config table. See FIG. 47 for a sample of this screen.

[0985] Record/Replay Initialization CSU

[0986] This form allows for the input of initial states or checking of the helical scan recorder tape jukebox and the helical scan recorder tape units 1 through 4 and setting the paths for record and replay. See FIG. 48 for a sample of this screen.

[0987] Remote Site Equipment Status CSU

[0988] This form allows for checking the status of the remote site equipment. This form interfaces with the remote_site_equipment_status table. The information in this table is inserted and maintained by the SDS. See FIG. 49 for a sample of this screen.

[0989] Camera Configuration CSU

[0990] This form is called from equipment configuration menu. It is used to query and update the information in the camera_config table. See FIG. 50 for a sample of this screen.

[0991] Video Insertion Configuration CSU

[0992] This form, called from the equipment administration menu, allows input to set up the configuration of the sites with camera IDs and video channels. This form is used to insert, query, update and delete data from the video_insertion table. See FIG. 51 for a sample of this screen.

[0993] Video Switcher Configuration CSU

[0994] This form allows for input to the video_switcher_input and video_switcher_output tables and also allow for the configuration of the video switcher. See FIG. 52 for a sample of this screen.

[0995] Prospective List CSU

[0996] This form is used to access and update the vessel_track table. The form can be accessed either from the vessel status menu or from GOTS. See FIG. 53 for a sample of this screen.

[0997] Anchored List CSU

[0998] This form is used to access and update the vessel_track table. The form can be accessed either from the vessel status menu or from GOTS. This screen is a scrolling screen. The right half of the screen changes to view or enter information giving the appearance of 5 screens. See FIGS. 54, 55, 56, 57 and 58 for samples of this screen.

[0999] Docked List CSU

[1000] This form is used to access and update the vessel track_table. The form can be accessed either from the vessel status menu or from GOTS. This screen is a scrolling screen. The right half of the screen changes to view or enter information giving the appearance of 5 screens. See FIGS. 59, 60, 61, 62, and 63 for samples of this screen.

[1001] Traffic Summary CSU

[1002] The Traffic Summary form, see FIG. 64, is used to enter the time period for the Traffic Summary Report.

[1003] Vessel Support Data Screen CSU

[1004] This form is used to insert, update, query, and delete all vessel identification and configuration information stored in the vessel_id table. This form is called both from the vessel administration menu and the GOTS vessel data card screen. In addition to the vessel ID table, this form is also responsible for inserts to and deletes from the alternate vessel ID table which tracks old vessel identification information. See FIG. 65 for a sample of this screen.

[1005] Vessel Registry Type CSU

[1006] This form is used to access and update the vessel_registry_type table. The table contains all valid vessel registry types. The form can be accessed from the vessel administration menu. See FIG. 66, page for a sample of this screen.

[1007] Vessel Country CSU

[1008] This form is used to access and update the vessel_country table. The table contains all valid vessel country codes. The form can be accessed from the vessel administration menu. See FIG. 67, page for a sample of this screen.

[1009] Vessel Category Code CSU

[1010] This form is used to access and update the vessel_category_code table. The table contains the valid categories and category codes. This form can be accessed from the vessel administration menu. See FIG. 68, page for a sample of this screen.

[1011] Vessel Special Category CSU

[1012] This form is used to access and update the vessel_spec_cat table. The table contains all valid vessel registry types. The form can be accessed from the vessel administration menu. See FIG. 69, page for a sample of this screen.

[1013] Vessel Units CSU

[1014] This form is used to access and update the vessel_units table. The table contains all valid vessel tonnage units. The form can be accessed from the vessel administration menu. See FIG. 70, page for a sample of this screen.

[1015] VTS Error Log CSU

[1016] This form, called from the logs menu, allows system errors encountered by the SDS, which have previously been recorded in the VTS Error Log Table, to be queried or purged as required. See FIG. 71, page for a sample of this screen.

[1017] Pilot CSU

[1018] This form is called from the DBS Main Menu. It is used to query, add, and modify data in the pilot table. See FIG. 72, page for a sample of this screen.

[1019] Vessel Transit History CSU

[1020] This form is used to query all vessel transit information stored in the vessel_transit table. The vessels are identified by vessel registry number and call sign, which, through the use of the vessel ID table, are further identified by the vessel name. Information as to point of origination, destination, estimated time of arrival, estimated time of departure, configuration of vessel, cargo, etc. are tracked for the transit. This form is accessed from the reports menu only and is used to provide access to the transit history of a vessel. See FIG. 73, page for a sample of this screen.

[1021] Identify Vessel CSU

[1022] This form, called from the GOTS vessel data card (VDC), is used by the console operator to search the vessel_ID table or prospective list and identify a vessel. If the vessel is not found in the table, the operator may create an unknown temporary vessel id. This is accomplished by using the NEXT key. Once a vessel is selected, the form passed the information to GOTS. See FIG. 74 for a sample of this screen.

[1023] C & Pro*C CSC

[1024] These modules represent functions written in C or Pro*C. This includes user exits, bridge function, and reports.

[1025] Radar Configuration User Exit CSU

[1026] This user exit is called from the radar configuration form, once for each radar_config table row that is modified. It calls an ODS function and passes it the site number and radar ID of the modified row. ODS then notifies SDS of the change.

[1027] Traffic Summary CSU

[1028] This CSU produces the traffic summary report. An example report can be found in FIG. 75, on page. It can be generated for any time period that is valid. The transit movement data in the vessel_transits table are read for the specified time period and the number of transits are summed for each vessel type. The report is executed via a form mentioned earlier in this document. The program that extracts the data and formats the report.is written in C. Pro*C functions are used to execute SQL select statements that extract data from the log tables.

[1029] Data Conversion CSC

[1030] This component uses SQL*Loader modules to initially load data from flat files. This includes vessel data and code table information. Where data volumes are small, SQL*Forms screens developed for maintenance are also used for the initial data load.

[1031] MSMS Initial Load CSU

[1032] Data from the Marine Safety Management System is used for the initial load of requested vessel information. This data is obtained in flat files and loaded in to Oracle tables using SQL*Loader.

[1033] USCG Data CSU

[1034] DBS also uses several code tables to validate input data. These tables contain small volumes of static look up data. When table sizes are small, SQL*forms will be used to manually enter this data, however for larger tables either SQL*Loader or SQL*Forms modules may be used to load this data.

[1035] Operations Support CSC

[1036] These modules provide operational support and fulfill one or more DBS requirements. They require little or no custom software. The CSUs included in this component are shutdown processing, database processor shadowing, printer output, built in test, archive/restore, and backup/recovery.

[1037] Shutdown Processing CSU

[1038] Database shutdown is part of the shutdown script for the 15 UNIX system. The command to shutdown the Oracle database is placed in the “/etc/shutdown” directory. Before shutdown begins, a hardcopy listing of vessels currently being tracked by the system is produced. This enables manual tracking of these vessels.

[1039] Database Processor Shadowing CSU

[1040] To minimize downtime due to equipment failure, redundancy is provided in the database processor and associated disks. The backup processor and disks are maintained under Oracle and TDBM control.

[1041] The Oracle redo logs are operated under archive mode on the active database processor. These logs are copied to the shadow processor. The Oracle database on the shadow processor is run in recovery mode, fed by the redo logs from the active processor.

[1042] TDBM has a similar built-in feature. The GOTS software senses database processor failure and signals activation of the backup processor. After completing recovery, Oracle is brought up followed by TDBM.

[1043] Printer Output CSU

[1044] The VTS printer is connected to the database processor. All printer output from both ODS and SDS is directed to this printer via the DBP.

[1045] Built in Test CSU

[1046] Oracle database and UNIX system performance statistics are accumulated for the DBP. These statistics are used for performance tuning and trouble-shooting. Utility programs supplied with Oracle and Unix can be configured to accumulated and tabulate this information.

[1047] Backup and Recovery CSU

[1048] A three tier backup scheme is used to provide protection against data loss up to the last committed transaction.

[1049] The first level consists of image backups that are performed on a monthly basis or anytime the physical structure of the database is changed. This consists of copying all database files to tape. Recovery from this backup consists of restoring from tape a consistent set of files.

[1050] The next level of backup consists of complete exports performed on an hourly basis. The Oracle Export utility is used to make the complete export. Recovery from this backup consists of several steps. First, the tables are dropped from the current database. The export dump file is then imported, without grants and indexes. Index definitions are extracted into a separate SQL script and run after importing the table definitions and data rows. Finally, the SQL scripts containing the public synonym definitions and grants are run.

[1051] The third tier backup consists of running redo logs in the archive mode. Recovery from the current redo log is automatically done whenever Oracle is brought up. Recovery from older redo logs requires an image backup. After restoring from the image backup, each redo log file generated since the backup is applied to the database.

[1052] CSCI DATA

[1053] Detailed descriptions of global data elements within this CSCI are provided in the Interface Design Document. The Oracle DBMS maintains the data described below for use by the ODS and SDS. The following data by category is maintained for the ODS and SDS:

[1054] Alarm Defintion Storage

[1055] The DBS maintains user defined alarm conditions accessed by SDS at initialization and upon completion of changes or addition of new alarm defintions by the operator.

[1056] Configuration Data

[1057] The DBS maintains configuration data for the purposes of identifying the display and remote site hardware configuration and user options. These configuration tables are described in the IDD. The ODS creates and maintains these entries. After any modification is made to adapt to real time operating environment, these tables are updated so that in case of system recovery, these configuration settings will be used.

[1058] The DBS maintains the number of remote sensor sites for the port. Configuration data for remote sites is maintained in the IDD. The DBS maintains initial configuration data for the video system and video insertion unit.

[1059] The DBS indicates the number of workstations, their network addresses, and the initial default radar and sector map display for each ODP.

[1060] User Access Definition

[1061] The DBS maintains a list of users and provides the ability to create and update the user access information. A password for each user is provided in encrypted form. Users are classified according to authorization level into the following categories:

[1062] 1. system administrator

[1063] 2. watch supervisor

[1064] 3. watch operator

[1065] 4. external operator

[1066] Log Recording

[1067] The DBS maintains a history of log entries. Log entries are classified by log type and the log entry refers to one or more participating vessels. Log entry types supported include: opnotices (in GOTS), VTS error log, and pass down log (in GOTS)

[1068] A maintenance function is provided to allow modification, and addition to the log entries. The maintenance function is restricted to only authorized users. An audit history record is kept for each modification.

[1069] Operator Display Software Overview

[1070] The Operator Display Software (ODS) CSCI is responsible for command and control, map and vessel displays, playback control of recorded sensor data, performing alarm notification, . generating training scenario vessel data, configuration of sensors, maps, operators, and sectors, and monitoring the performance of the Operator Display Processor.

[1071] Architecture

[1072] The ODS dataflow is shown in Figures la and lb. The ODS CSCI is split into four groups, the ODS Interface, ODS Display, ODS Database, and ODS-Unified Build (UB) CSCs.

[1073] The ODS-UB CSCs consists of the following (see FIG. 81):

[1074] Tactical Database Manager (TDBM)

[1075] Radar Image Draw Module (RIDMO)

[1076] Vessel Data Card (VDC)

[1077] Track List

[1078] System Chart

[1079] The ODS Interface CSCs consist of the following (see FIG. 78):

[1080] Radar Image Daemon (RID)

[1081] Chart Interface Daemon (CID)

[1082] Command/Status Daemon (CSD)

[1083] Touch Panel (TP)

[1084] The ODS Display CSCs consist of the following (see FIG. 79):

[1085] Shutdown

[1086] Alarm Zone Control

[1087] Alarm Criteria

[1088] Estimated-Positioning Route Control

[1089] Track Control

[1090] Playback Control

[1091] X-Window Print (XPWIN)

[1092] The ODS Database CSCs consist of the following (see FIG. 80):

[1093] Logon/Logoff

[1094] Database Form Interface

[1095] Radar Configuration Interface

[1096] Database Forms

[1097] Database Menus

[1098] Radar Image Daemon (RID) CSC

[1099] The radar image daemon is responsible for receiving up to 18 radar images from the Sensor Data Software (SDS) and storing them in the ODS shared memory buffer. In addition, it provides a status input to the Command/Status Daemon CSC for error messages and an update signal.to the RIDMO CSC. Each RIDMO process sends a request to enable or disable signals to it. The format of images from the SDS is described in the CGVTS Interface Design Document (IDD). The storage formats for the radar images and Command/Status Daemon CSC messages are described infra. The RIDMO actually displays the image.

[1100] Chart Interface Daemon (CID) CSC

[1101] The chart interface daemon is responsible for maintaining alarm zone and EP route information on the map displays. It retrieves definition information from the Oracle database and instructs the Unified Build chart manager to plot the appropriate lines and circles. When updates occur, the CID is notified via a defined signal mechanism.

[1102] Command/Status Daemon (CSD) CSC

[1103] The command/status daemon is responsible for receiving SDS commands from ODS CSC's, notifying operators of alarm conditions and remote site status, and sending valid commands to the SDS. Command status from the SDS is then relayed back to the appropriate ODS CSC.

[1104] A status window appears in the righthand monitor display that is resizable and can be minimized to an icon if desired. It cannot be removed from the display completely, however.

[1105] A message queue receives status updates from ODS CSC's that are displayed in the status window. If a system status message (e.g. UPS notification) is received from the SDS, it is displayed in the status window as well. An audible indicator is sounded when new status messages are displayed; this can be disabled by the operator.

[1106] Remote site status is retrieved from the Oracle database at 30 second intervals and displayed in tabular format in the-upper portion of the status window.

[1107] Vessel alarms received from the SDS are displayed in small windows next to the vessel icon on the screen. If the icon is not on the screen, the window is placed on the screen using a simple tiling formula. Detailed information is displayed in the status message list. Both visual and audible alarm notification can be enabled/disabled by the operator for each class of alarm through pull-down menus in the status window. The default is to notify both audibly and visually for all alarm classes.

[1108] The following commands are routed by the command/status daemon:

[1109] Camera Commands

[1110] Pan left/right

[1111] Stop panning

[1112] Tilt up/down

[1113] Stop tilt

[1114] Zoom in/out

[1115] Stop zoom

[1116] Focus in/out

[1117] Stop focus

[1118] Turn wiper/washer/defogger on/off

[1119] Get camera status/state

[1120] Video Switcher Commands (console specific)

[1121] Select video source for monitor 1-4

[1122] Get switcher status/state

[1123] Tracking Commands

[1124] Add track at specified position, radar or EP

[1125] Drop or swap track

[1126] Modify EP track to specified position, route, speed

[1127] Update track vessel data from DBS

[1128] Radar Commands

[1129] Update radar configuration from DBS

[1130] Get radar status/state

[1131] Playback Commands

[1132] Start playback at specified time and date

[1133] Stop playback

[1134] Select sensors for playback

[1135] Get playback status/state

[1136] Radio Setup Commands

[1137] Set/get radio configuration

[1138] Get radio status/state

[1139] Alarm Commands

[1140] Update alarm generation criteria

[1141] Update zone or EP route definitions from DBS

[1142] Shutdown Commands

[1143] UPS Alarm, Cancel

[1144] Terminate System Operations

[1145] Touch Panel (TP) CSC

[1146] The touch panel CSC is responsible for Closed-Circuit TeleVision (CCTV) camera, Video Cassette Recorder (VCR), video switcher, and radio control. It also provides an audio callback capability (up to 10 minutes) for the primary and secondary radio transceiver frequencies. Operator commands are initiated from a touch panel located in the console turret and sent to the Command/Status Daemon CSC (for camera, radio, and video switching commands), to the VCR via RS-232C (for VCR commands), or to the Touch Panel Audio Device (for audio callback).

[1147] The touch panel display uses site name abbreviations from the DBS configuration tables. Site access control is provided through the site mask table initialized by the Logon/Logoff CSC in shared memory.

[1148] Shutdown CSC

[1149] The shutdown CSC allows a supervisor to shutdown the console or entire VTS. It also allows the supervisor to cancel a pending VTS shutdown before the 10 minute grace period has expired. The shutdown of a console occurs immediately without printing vessel data cards, sector summary, or screen images. The shutdown of the VTS causes the printout of all reports and starts a 10 minute countdown on the SDS before a shutdown of the VTS processors occurs.

[1150] Alarm Zone Control CSC

[1151] The alarm zone control CSC allows the operator to define or delete stationary and traffic lane safety zones composed of line segments or swing circle zones composed of a circle of specified radius (‘shots’). Alarm zones are enabled for the sector or sectors an operator is presently logged onto. Zones are colored by zone type: red for stationary safety zones, magenta for traffic lanes, orange for swing circles.

[1152] Alarm Criteria CSC

[1153] The alarm criteria CSC allows the supervisor to adjust the global alarm generation criteria for CPA/TCPA alarms.

[1154] Estimated-Positioning Route Control CSC The EP route control CSC allows the operator to define or delete EP routes composed of line segments. EP routes are one- way and cause EP-tracked vessels to move from the first to last defined point along the route. Arrows are drawn at each waypoint on the route to indicate direction of movement. EP route lines are colored light blue.

[1155] Track Control CSC

[1156] The track control CSC allows the operator to add a radar or EP track and swap, handoff, accept, drop, dock, anchor, or ‘out-of-area’ tracked vessels. Only those vessels with sector masks matching the current console sector mask may be manipulated.

[1157] Playback Control CSC

[1158] The playback control CSC allows the replay of VTS data from the SDS for vessel, audio, radar, and CCTV video data. The operator selects the time, type of data, and sensors of interest, and may start and stop playback at will. When playback is active, a visual indicator is provided on both screens.

[1159] X-Windows Print (XPWIN) CSC

[1160] The X-Windows Print CSC is a standalone program that outputs an X window on a screen to an Hewlett-Packard (HP) Page Control Language (PCL) or compatible printer or to a file in PC Paintbrush (PCX) format. By default, it prints the window the ouse pointer is in, but can be instructed to print a specific indow or screen.

[1161] Logon/Logoff CSC

[1162] The logon/logoff CSC provides an interface to the operator for changing the sector(s) which a console controls and logging onto and off of the Oracle database. Each operator has an Oracle account with a password; the password is encrypted by Oracle and may contain up to 30 characters. Once an operator's login to Oracle has been accepted, a checklist of available sectors is displayed for the operator to select.

[1163] The operator name, password, and sector mask are stored in a shared memory buffer along with site control masks and site names that are generated for the sector(s) the operator has selected. The site control masks are used to limit use of sensors to those who need them.

[1164] Database Form Interface CSC

[1165] The database form interface CSC is a ‘C’ program that gets the current Oracle username and password from the Logon/Logoff shared memory buffer and starts the specified database form.

[1166] Radar Configuration Interface CSC

[1167] The radar configuration interface CSC is a ‘C’ program that sends a radar configuration update message to the SDS. The radar configuration form passes the remote site ID to this CSC on the command-line.

[1168] Database Forms CSC

[1169] The database forms CSC contains the DBS SQL*FORM CSCs used for database access.

[1170] Database Menus CSC

[1171] The database menus CSC contains the DBS SQL*MENU CSCs used for database access.

[1172] Tactical Database Manager (TDBM) CSC

[1173] TDBM is the component of the Unified Build software that provides multi-source correlation and database management of tactical track data. The records of the Unified Build software are non-homogeneous and are grouped into separate types of track information. Other CSC's and their relationship to the TDBM CSC are as follows:

[1174] Vessel Data Card CSC: Functions as support for TDBM, i.e., provides a mechanism for adding, editing, updating, deleting and archiving TDBM's tactical track data.

[1175] Track List CSC: Receives track data from TDBM which it sorts and displays.

[1176] System Chart CSC: TDBM provides information to this CSC for display of tracks on the chart.

[1177] Track Control CSC: This CSC provides track information (e.g., add radar track, add EP track, swap track, etc.) to TDBM either directly or through SDS.

[1178] Radar Image Draw Module (RIDMO) CSC

[1179] The RIDMO CSC provides the capability to display a composite radar bitmap image on the VTS operator display. RIDMO supports the required manual target acquisition function. Other CSC's and their relationship to the RIDMO CSC are as follows:

[1180] System Chart CSC: Radar bitmaps are sent to the System Chart CSC from the RIDMO. The System Chart CSC then sends the bitmap objects to the display.

[1181] Vessel Data Card (VDC) CSC

[1182] The VTS operator is required to keep track of certain information related to all VTS participant vessels within a harbor area. This information must be included in any automated vessel tracking system. The VTS operator is already familiar and comfortable with the paper version of the vessel data card. Therefore, the electronic vessel data card mimics the familiar paper version. Hence, the Vessel Data Card CSC provides an electronic user interface for entering track data information. Other CSC's and their relationship to the Vessel Data Card CSC are as follows:

[1183] TDBM CSC: refer to section 3.1.1.17 of this document.

[1184] System Chart CSC: The System Chart CSC controls the actual display of the Vessel Data Card.

[1185] Track List CSC: The Track List CSC provides a means for user access to the Vessel Data Card.

[1186] Track List CSC

[1187] The Track List CSC provides the operator with the ability to monitor vessel traffic within an area of interest. This is accomplished by maintaining a list of all vessels that are within a defined sector along with all pertinent associated data. The Track List CSC updates vessel data and keeps the operator notified of tracks that go into a “coast” mode. It also allows the operator to select entries from the list and access more detailed data via the Vessel Data Card. Other CSC's and their relationship to the Track List CSC are as follows:

[1188] TDBM CSC: refer to section 3.1.1.17 of this document

[1189] Vessel Data Card CSC: refer to section 3.1.1.19 of this document.

[1190] System Chart CSC: The System Chart CSC displays Track List data on the operator's screen.

[1191] System Chart CSC

[1192] The System Chart is responsible for drawing objects to a indow on the display. It is structured so that there is a Chart anager which performs the actual drawing functions. There are “chart clients” (which are simply application programs) which communicate various commands to the Chart Manager to accomplish the drawing of various objects on the screen. Other CSC's and their relationship to the System Chart CSC are as follows:

[1193] TDBM CSC: refer to section 3.1.1.17 of this document.

[1194] Radar Image Draw Module CSC: refer to section 3.1.1.18 of this document.

[1195] Vessel Data Card CSC: refer to section 3.1.1.19 of this document.

[1196] Track List CSC: refer to section 3.1.1.20 of this document.

[1197] System States and Modes

[1198] The Operator Display Software supports operation in the live and playback modes.

[1199] Live Mode

[1200] While in live mode, realtime vessel, radar, and alarm data is displayed at the console. Control commands (radar configuration, track control, etc) are active in this mode.

[1201] Playback Mode

[1202] While in playback mode, a visual indicator is displayed on both screens. Since processed vessel data is stored for replay, only those alarms that occurred at the time of recording are indicated. Control commands are disabled in this mode.

[1203] CSCI Design Description

[1204] Radar Image Daemon CSC

[1205] The Radar Image Daemon (RID) receives digitized radar images from the SDS via FDDI and stores these images in a shared memory buffer. As soon as a new image has been received by the RID, a signal is sent to each Radar Image Draw Module (RIDMO) so that it can update the image on the screen if necessary; each RIDMO process sends a request message telling the RID which process and signal it is to send (see FIG. 82).

[1206] The RID handles up to 18 real-time and 4 playback digitized radar images. Each image is 512 by 512 or 1024 by 1024 pixels in size; each pixel is composed of two bits for a total of 64 kilobytes (kb) or 256 kb respectively per image (total of 1.13 or 4.5 Mb). Images are received in compressed format; the algorithm used is a modified run-length encoding. The image is decompressed and stored in its literal form in the buffer. Each image has a header describing the dimensions, location, offset, range, and site ID of the image. [260]

[1207] Chart Interface Daemon CSC

[1208] The Chart Interface Daemon (CID)is responsible for nteracting with the Chart Manager. The user interface routines for alarm zones and EP routes send an event to the CID which then interacts with the Chart Manager through application program interfaces (api's). The CID opens connections to each of the charts and handles user mouse and keyboard input to define and delete safety zones and EP routes. The CID also stores and deletes the information in the database and then sends appropriate commands to SDS for alarm zone activation.

[1209] Command/Status Daemon CSC

[1210] The Command/Status Daemon (CSD) receives status updates from the SDS and ODS CSC's and sends ODS commands to the SDS for processing. It also maintains a status window with audible and visible indicators for system errors and alarm conditions (see FIG. 84).

[1211] Each command/status message consists of approximately 1024 bytes of data. One command/status message is sent per operator control request (pan/tilt, etc). [120, 150, 340, 470]

[1212] Each alarm message consists of approximately 32 bytes of data. One alarm message is sent for each alarm condition per SDS update. No indication is provided for cessation of an alarm condition.

[1213] Touch Panel CSC

[1214] The Touch Panel is composed of two sub-level CSCs; the first handles the low-level interface to the audio board, and the second handles operator commands through the touch panel (see FIGS. 85, 86, and 87).

[1215] Touch Panel Audio Device (TPAD) CSC

[1216] The TPAD is a collection of three UNIX device drivers that provide a standard interface for 8-bit stereo sound playback and recording, FM synthesized tones (notes), and input/output mixer control. Normally, read( ) and write( ) calls are used to record and playback audio, respectively. An ioctl( ) interface provides configuration of volume, configuration of frequency, reset & flush buffers, and block/noblock mode. The TPAD maintains 1024 kb recording and playback buffers, which is roughly 32 seconds of audio at 16.384 kHz frequency (32 seconds×16,384 samples/second×2 channels×1 byte/channel sample=1024 kb). [230, 240, 250, 940]

[1217] Touch Panel Operator Interface (TPOI) CSC

[1218] The TPOI CSC receives operator commands through a touch panel mounted in the console turret via RS-232C. The touch panel sends three-byte escape sequences when the operator touches, drags, or takes his finger off the panel. The escape sequences identify the position and type of contact made on the touch panel.

[1219] The TPOI CSC communicates to a VHS VCR via RS-232C. Commands to and responses from the VCR consist of ASCII strings 5 to 16 bytes in length.

[1220] Finally, the TPOI CSC polls the Touch Panel Audio Device (TPAD) for radio audio and places the digitized audio into a 10 inute circular buffer (1024 kb in length). During callback, audio data is sent to the TPAD to be played over the console speakers. [230, 240, 250]

[1221] Shutdown CSC

[1222] The shutdown CSC allows a supervisor or system administrator to shutdown a console, shutdown the VTS, or cancel a VTS shutdown. Console shutdown is immediate using the HP/UX rebooto system call with the halt-and-sync option. VTS shutdown and cancel shutdown are messages sent to the SDS to start and stop a 10 minute shutdown counter; the VTS shutdown message triggers reports and console shutdowns in a manner identical to an UPS power alarm.

[1223] Alarm Zone Control CSC

[1224] The alarm zone control CSC allows a system operator to create or delete a stationary safety zone, a traffic lane or a swing circle. The user interface for each of these programs interprets the requested action and sends an appropriate user event to the Chart Interface Daemon (CID).

[1225] Alarm Criteria CSC

[1226] The alarm criteria CSC allows a supervisor or system administrator to set the desired time and distance values to be used in proximity alarm calculations. A user interface retrieves the previously set values from the database and displays them for review. The new values are then saved in the database and a command sent to SDS to initiate the change in the calculations.

[1227] Estimated-Positioning Route Control CSC

[1228] The estimated-positioning route control CSC allows a system operator to create or delete a route upon which an estimated position track can be placed. The user interface interprets the requested action from the operator and sends an appropriate user event to the Chart Interface Daemon (CID)

[1229] Track Control CSC

[1230] The track control CSC is composed of sub-CSCs to do the following:

[1231] Add radar track

[1232] Add EP track

[1233] Swap track

[1234] Change To Radar track

[1235] Change To EP track

[1236] Handoff track

[1237] Accept track

[1238] Drop track

[1239] Dock track

[1240] Anchor track

[1241] Out-of-area track

[1242] Only those vessels with sector masks matching the current console sector mask may be manipulated.

[1243] Add Radar Track CSC

[1244] Add Radar Track CSC allows an operator to command the VTS radars to begin tracking a certain object based on radar returns as reflected by the Radar Image Draw Module. The requirement is for a VTS operator to have the capability to perform manual track acquisition. The execution/data flow is as follows: the Add Radar Track CSC sends latitude/longitude, sector mask and radar site ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor of the desired acquisition. The radar processor then sends data on the acquired track back to SDS.

[1245] Add EP Track CSC

[1246] Add EP Track CSC allows an operator to command the SDS to begin calculating the position of a track along an estimated positioning route. The requirement is for a VTS operator to have the capability to designate the initial position and speed of the EP track. The execution/data flow is as follows: the Add EP Track CSC sends latitude/longitude, speed and EP route ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS then initiates the track and updates the track's movement within the track database.

[1247] Swap Track CSC

[1248] The Swap Track CSC allows an operator to command the SDS to swap the track information for two specific tracked objects. The execution/data flow is as follows: the Swap Track CSC sends the track ID's to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS then swaps the track information in the track database which causes the operator display to reflect the icon and track tags displayed for the selected objects to be swapped.

[1249] Change To Radar Track CSC

[1250] Change To Radar Track CSC allows an operator to command the VTS radars to begin tracking an object that had previously been calculated as an EP track. The execution/data flow is as follows: the Change to Radar Track CSC sends an EP track ID, latitude /longitude, sector mask and radar site ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor of the desired acquisition. The radar processor then sends data on the acquired track back to SDS. The SDS then performs a swap track that attaches the track information of the EP track to the new radar acquisition and then deletes the extraneous extra track.

[1251] Change To EP Track CSC

[1252] Change To EP Track CSC allows an operator to command SDS to begin performing an estimated positioning calculation on an object that had previously been an active radar track. The execution/data flow is as follows: the Change to EP Track CSC sends a track ID and EP route ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor to drop the designated track. SDS then begins an EP track at the last position of the track at its last reported speed. The SDS then performs a swap track that attaches the track information of the radar track to the new EP track and then deletes the radar track.

[1253] Handoff Track CSC

[1254] The handoff track CSC is supplied with a Tdbm track ID. If the vessel associated with the Tdbm track has a sector mask matching that of the current console sector mask, the following steps are performed:

[1255] a. The Tdbm sector mask field is changed to all one's.

[1256] b. The SDS is notified that vessel information has changed.

[1257] Otherwise, an error message is displayed in the command-status daemon window notifying the operator of the problem.

[1258] Accept Track CSC

[1259] The accept track CSC is supplied with a Tdbm track ID. If the vessel associated with the Tdbm track has a sector mask of all one's, the following steps are performed:

[1260] a. The Tdbm sector mask field is changed to match the console sector mask.

[1261] b. The SDS is notified that vessel information has changed.

[1262] c. The DBS VESSEL_TRACK table is updated to contain the new sector mask and sector mask history.

[1263] Otherwise, an error message is displayed in the command-status daemon window notifying the operator of the problem.

[1264] Drop Track CSC

[1265] The Drop Track CSC provides the operator the capability of dropping a track that is either no longer of interest or was begun inadvertently. Once the track is designated for dropping, it will be removed from the track database and the display. The data flow for the Drop Track CSC consists of a message sent to SDS to stop generating updates for the track.

[1266] Dock Track CSC

[1267] The Dock Track CSC enables the operator to indicate that a vessel in his/her area of responsibility has docked. Once a vessel has reached a destination within the port where it will dock, the operator will choose the “DOCK” option from the Vessel Action Menu. The status of the vessel in the track database will then be changed to “docked”.

[1268] Anchor Track CSC

[1269] Within a VTS operator's area of responsibility, when a vessel has reached an anchorage destination, the Anchor Track CSC provides a mechanism for entering anchorage information into the system. The Anchor Track CSC is invoked from the Vessel Action Menu. This CSC will cause the selected vessel's status to change in the track table to “anchored”. It also changes the traffic count and causes the swing circle user interface to be invoked, allowing the operator to construct a swing circle for that vessel.

[1270] Out-of-Area Track CSC

[1271] When a vessel exits the port, the Out-of-Area Track CSC, enables the VTS operator to enter this information into the system. The Out-of-Area Track CSC is invoked from the Vessel Action Menu. A status change to “OutofAOR” will occur in the track database upon execution. Additionally, the traffic count will be altered.

[1272] Playback Control CSC

[1273] The playback CSC allows the replay of VTS data from the SDS, including vessel, audio, radar, and CCTV video data. No additional storage is required.

[1274] X-Windows Print (XPWIN) CSC

[1275] The XPWIN CSC is a standalone utility program that provides greyscale hardcopy or PCX output of a window or screen. Several command-line options are provided to alter the output and are documented in the XPWIN(LX) manual page.

[1276] If no window ID is specified on the command-line, XPWIN first queries the window manager for the window ID the mouse pointer resides in.

[1277] Next, the window location, attributes, and image are obtained from the window manager.

[1278] Once the image has been retrieved, the colormap used by the window is converted to a series of grey levels using the National Television Standards Committee (NTSC) mapping G=0.30R+0.59G+0.11B. The grey level table is then contrast expanded using the equation G=contrast(G−mean-grey-level)+mean-grey-level.

[1279] Using the grey level table, the image is dithered to the printer using the Burke dithering coefficients. The printer bitmap is compressed if the output printer supports that feature (LaserJet 4, III, IIp, and DeskJet all support compression).

[1280] The XPWIN program requires approximately (width×height×2) bytes of additional storage to copy a window image.

[1281] Logon/Logoff CSC

[1282] The logon/logoff CSC provides database and display access control for each operator at the VTC. It also allows an operator to select the sector(s) to control at the console. [350-387]

[1283] The user is first presented with a window containing username and password boxes; the operator types the username and password on the keyboard, but only the username text is echoed on the screen. Once the operator has entered the password, an embedded SQL connect call to Oracle is performed to attempt the login. If the connection fails, an error message is displayed and the username, password, and authorization level in the console configuration buffer are cleared.

[1284] If the connection succeeds, a query of the user authorization table is performed to get the operator's authorization level and real name which is then placed in the console configuration buffer. A second window is displayed listing the available sectors in the database for the operator to choose from. Once chosen, a sector mask is built using the sector ID(s) of the selected sector(s), where bit 0 corresponds to sector 1, bit 1 corresponds to sector 2, etc.

[1285] The console configuration buffer is a shared-memory buffer that contains the current user name, password, authorization level, sector mask, remote site masks, and remote site names. For those remote sites that are not accessible from the current sector(s), the masks and names are cleared.

[1286] Database Form Interface CSC

[1287] The database form interface CSC first checks for the current user that is logged onto the database (via the Logon/Logoff CSC). If no user is presently logged on, an error message is displayed. Otherwise, the specified database form is run using the current username/password. No additional storage is required.

[1288] Radar Configuration Interface CSC

[1289] The Radar Configuration Interface CSC is executed from the Radar Configuration database form when a change has been posted by a user. The form passes the radar ID and remote site ID affected by the change to the radar configuration interface. A radar command is then constructed and sent to SDS through the command status daemon.

[1290] Database Forms CSC

[1291] The database forms CSC consists of all applicable DBS SQL*FORMs that reside on the ODP. Consult the DBS SDD for details.

[1292] Database Menus CSC

[1293] The database menus CSC consists of all applicable DBS SQL*MENUs that reside on the ODP. Consult the DBS SDD for details.

[1294] Tactical Database Manager (Tdbm) CSC

[1295] The Tactical Database Manager, as stated in section 3.1.1.17, is the component of the Unified Build software that provides multi-source correlation and database management of tactical track data. There is a copy of Tdbm executing on the VTS Database processor (DBP) as well as a copy executing on each Operator Display Processor (ODP). Tdbm on the DBP handles all system track data while Tdbm on each ODP handles track data for the sector(s) currently being handled by the operator on that particular ODP. For more information on Tdbm execution control consult the TDBM . . . .

[1296] Radar Image Draw Module (RIDMO) CSC

[1297] The Radar Image Draw Module CSC creates and integrates a draw module that provides the capability to display a composite bitmap image of an operators area of responsibility. The Radar Image Draw Module CSC is begun when a signal is generated by the Radar Image Daemon. RIDMO gets radar data from shared memory (where Radar Image Daemon stored the data). RIDMO then sends radar bitmaps to the Chart Manager. RIDMO also receives data input by the operator indicating radar selection and attribute changes.

[1298] Vessel Data Card CSC

[1299] The Vessel Data Card CSC assists the operator in keeping track of certain information related to all VTS participant vessels within a harbor area. The Vessel Data Card will appear in a window when the VTS operator performs any of several track manipulation functions. These functions can be found in the CGVTS Software Users Manual.

[1300] Track List CSC

[1301] The Track List CSC provides the operator with the ability to monitor vessel traffic within an area of interest by displaying a list, on the screen, of all vessels currently in track within his/her sector. The Track List is executed after selection on the TRACKS pull-down menu. Once the user selects Track List, control will pass to another module and the Track List window will appear on the screen.

[1302] System Chart CSC

[1303] The System Chart CSC manages object drawing to a window on the VTS operator display. The System Chart is started up with the VTS system and awaits commands from “clients”. Once the system chart receives this command, it creates a window. The client then sends commands to the system chart to draw objects. The System Chart draws the objects, the client waits for any events and upon receipt sends a command to System Chart to destroy the window. For more information on this CSC refer to the “GOTS 2.0 Chart Service Programming Guide.”

[1304] CSCI Detailed Design

[1305] For all system inter-process communication (IPC) resources that use a 4 byte ‘key’ to identify the resource, the CSC abbreviation and a resource number are used; for example, the RID shared memory IPC resource key would be:

[1306] ‘R’ ‘I’ ‘D’ 0 (5249440016)

[1307] If an IPC resource is shared by all ODS CSCS, the abbreviation ‘CSC’ is used.

[1308] All CSUs shall be coded in the ANSI-standard C language.

[1309] Radar Image Daemon CSC

[1310] The Radar Image Daemon is composed of five CSU's:

[1311] RID Initialize

[1312] RID Receive Image

[1313] RID Receive Request

[1314] RID Error Handler

[1315] RID Shutdown

[1316] Each radar image is placed in the RID shared memory buffer as it is formatted in the Radar Scan Data Update message (described in the CGVTS IDD).

[1317] RID Initialize CSU

[1318] The RID Initialize CSU creates, attaches, and maps the shared memory buffer for up to 18 radar images, opens connections to the CSD incoming and outgoing IPC message queues, opens a connection to the SDS via FDDI, creates the RID incoming IPC message queue, and resets the list of RIDMO processes. The shared memory key for the RID is 5249440016. The message queue key for the RID is 5249440116. The CSD incoming and outgoing message queue keys are 4353440016 and 4353440116 respectively.

[1319] The RID message is 4 bytes long and is used to enable and disable signals to a RIDMO process:

[1320] Process ID=Process to signal when a new image is received

[1321] Format: 16-bit unsigned integer

[1322] Range: 1 to 30000

[1323] Signal Control=

[1324] Format: 16-bit unsigned integer

[1325] Range:0=remove process from signal list, 1 to 65535=send this signal # to the process when an update occurs (see signal(3C)).

[1326] RID Receive Image CSU

[1327] The RID Receive Image CSU monitors the SDS connection and reads update messages when they are available. If no update messages are received within 1 minute, or if an image transfer is interrupted for more than 5 seconds, a status message is sent to the CSD with the text, “Radar Image Daemon: FDDI timeout!”. The update message format is described in the CGVTS IDD.

[1328] RID Receive Request CSU

[1329] Each RIDMO process sends a RID request on initialization and shutdown. The RID polls the message queue for incoming requests and processes them as necessary. If the requested signal is 0, the process is removed from the signal list; if the process has already made a request and the requested signal is non-zero, the process's signal is reset to the new value; if the process is not in the signal list, it is added to the list. The signal list will be an array of MAX_RID_REQUESTS signal entries; if the signal list becomes full, the requesting process will be killed and a message string sent to the CSD stating, “RID Error: Too many processes using radar images!”

[1330] RID Error Handler CSU

[1331] If for some reason the RID should fail to initialize, have a bad request, or have a data timeout, the error handler is called to send a message string to the CSD and the system log file.

[1332] RID Shutdown CSU

[1333] If RID receives a signal requesting its termination, the shutdown routine provides for a clean termination by dropping the network connection, detaching from shared memory and deleting it, and removing the message queues used to receive requests. Then the error handler is called to send a message string to the CSD and the system log file stating, “RID: Shutdown complete”.

[1334] Chart Interface Daemon CSC

[1335] The Chart Interface Daemon is composed of five CSU's:

[1336] CID Initialize

[1337] CID Create Template

[1338] CID Map Interaction

[1339] CID Error Handler

[1340] CID Shutdown

[1341] A user event from the safety zones or estimated positioning routes interfaces is received by CID and directs the path of execution in the Initialize and Map Interaction CSUs.

[1342] Command/Status Daemon CSC

[1343] The CSD is composed of the following CSUs:

[1344] CSD Initialize

[1345] CSD Receive Commands

[1346] CSD Receive Responses

[1347] CSD Receive Status Messages

[1348] CSD Update Status Window

[1349] CSD Update Remote Status

[1350] CSD Alarm Notify

[1351] CSD Initialize CSU

[1352] The CSD Initialize CSU opens a connection to the SDS, creates the command, response, and status message queues, and opens the CSD status window. The CSD command message queue key is 4353440016; the response message queue key is 4353440116; the status message queue key is 4353440216.

[1353] CSD Receive Commands CSU

[1354] After initialization, the CSD polls the command message queue; when messages are available, the CSD puts the SDS message header at the top of the command message, assigns the message a unique ID, places the message in a ‘waiting for response’ queue, and sends the message to the SDS via FDDI. The SDS message header is described in the CGVTS IDD; the CSD message header is as follows:

[1355] Process ID of Sender=

[1356] Format: 32-bit unsigned integer

[1357] Range: 1 to 30000

[1358] Message Type=

[1359] Format: 16-bit unsigned integer Rang

[1360] e: See CGVTS IDD SDS message format description

[1361] Message Length=

[1362] Format: 16-bit unsigned integer

[1363] Range: 16 to 4096 bytes

[1364] Message Time Seconds=

[1365] Format: 32-bit unsigned integer

[1366] Range: 0 to 232-1 seconds (since Jan. 1, 1970)

[1367] Message Time Microseconds=

[1368] Format: 32-bit unsigned integer

[1369] Range: 0 to 999999 microseconds

[1370] Message Data=

[1371] Format: varies

[1372] Range: varies; see CGVTS IDD SDS message format description

[1373] CSD Receive Responses CSU

[1374] After initialization, the CSD polls the SDS FDDI connection; when messages are available, the CSD puts the CSD message header at the top of the response message, removes the message from a ‘waiting for response’ queue, and sends the message to the ODS process via the CSD response message queue. The SDS message header is described in the CGVTS IDD; the CSD message header is as described in Section 4.3.2.

[1375] CSD Receive Status Messages CSU

[1376] Any system errors are logged to the system log file and sent the CSD for display in the status window. The CSD polls the status message queue for new messages and sends each new message to the CSD Update Status Window CSU. The status message format is as follow:

[1377] Message Type=

[1378] Format: 16-bit unsigned integer

[1379] Range:

[1380] 0=System error

[1381] 1=Hardware error

[1382] 2=Miscellaneous error

[1383] Message Length=

[1384] Format: 16-bit unsigned integer

[1385] Range: 8 to 4096 bytes

[1386] Message Time=

[1387] Format: 32-bit unsigned integer

[1388] Range: 0 to 232-1 seconds (since Jan. 1, 1970)

[1389] Message Text=

[1390] Format: Variable length nul-terminated ASCII string

[1391] Range:

[1392] 0016=end of text

[1393] 0916=tab to next 8th column

[1394] 0A16=end of line

[1395] 2016 to 7F16=ASCII text

[1396] All other values ignored

[1397] CSD Update Status Window CSU

[1398] As status messages are received from ODS CSCs and alarm messages are received from the SDS, they are displayed in the Status Window. The Status Window is divided into two halves.

[1399] The top half of the status window contains a list of statuses for each sensor connected to the VTS. When the sensor is online and operating properly, the word ‘UP’ is displayed; when the sensor is offline and not available, the word ‘DOWN’ is displayed. This portion of the screen is only updated by SDS alarm messages.

[1400] The bottom half of the status window contains a scrollable text window displaying status messages from the ODS CSCs; messages are coded as to their nature (system error, hardware error, miscellaneous error) and are time-tagged. Messages may be erased by the operator.

[1401] When the status window is updated, an audible indicator is sounded; this feature may be disabled by the operator. A toggle button is provided for this purpose (see FIG. 88).

[1402] CSD Update Remote Status CSU

[1403] The CSD Update Remote Status CSU performs a database query of the REMOTE_SITE_CURRENT_STATUS table for all records that have been added since the last update; updates occur at approximately 30 second intervals.

[1404] For each remote site status record, the appropriate radar, radio, or camera status is updated in static storage. Once all records have been processed, the remote site status list in the upper portion of the command-status daemon window is updated to reflect any changes.

[1405] CSD Alarm Notify CSU

[1406] As alarm messages are received from SDS, CSD allocates alarm message queue nodes to hold the alarm messages. There are five different alarm types:

[1407] 1. Track Lost

[1408] 2. Proximity

[1409] 3. Zone Traffic

[1410] 4. Zone Stationary

[1411] 5. Zone Swing

[1412] Once CSD receives an alarm message, it checks for the alarm in the message queue. If it is already allocated in the message queue, it will not be added. Elements in the message queue contain alarm type, track id, zone id, zone type, window id, time stamp, widget id, and display status.

[1413] Visual and audio alarm indicators can also be disabled or enabled by the operator. The operator can set each indicator individually.

[1414] The CSD also has three push buttons: Clear msgs, Reset alarms, Ack alarms. The Clear msgs button only clears messages from the status window. The Reset alarms button removes all alarm pop-ups from the display map(s) and all alarm message queue nodes from the message queue. The Ack alarms button clears all alarm pop-ups from the display map(s) and resets all alarm flags to false.

[1415] The System Audio radio button toggles audio sounds on or off.

[1416] Alarm pop-ups are displayed on all maps present. The CSD will display alarm pop-ups only on one map if there is only one map present.

[1417] Touch Panel CSC

[1418] Touch Panel Audio Device CSU

[1419] Initialization

[1420] Device availability and configuration is determined during the HP-UX boot phase called “attach”. EISA configuration information is made available to the driver and used to configure interrupt level, DMA channel and base address for 10 control. This information is utilized to initialize data structures within the device driver, map memory addresses to access board control registers in ISA data space and to configure the board's hardware registers. Following successful detection and configuration of the board, a confirmation message is provided indicating status of the audio board and of the driver.

[1421] Open access to the audio driver by a user routine, administrative checking is made of setup parameters, following which two 16 element FIFO's of 64 KB buffer elements are constructed as doubly linked lists. These lists are used for playback and recording operations. These are only constructed on first “open” of the device, or upon specific request to resize either FIFO queue.

[1422] These queues are the memory constructs from which actual interaction with the sound board are accomplished, in background processing modes. Foreground operations, in service to user calls to read( ), write( ), and ioctl( ) routines, influence and control operation of the background data acquisition modes without ever directly dealing with the audio board hardware. This is necessary in order to prevent gaps in audio signal due to lapses in Pulse Code Modulation (PCM) operation.

[1423] Operation of the mixer and synthesizer circuitry on the audio board is under direct control of the foreground processing routines, without buffering of any kind. These operations are also independent of PCM function in order to allow concurrent operation.

[1424] Record

[1425] Record operations are intended to initiate DMA transfer operations in background mode. Following request, recording continues under interrupt control until flags are set to stop data acquisition.

[1426] Playback

[1427] Playback operations are initiated by loading the playback buffers and initiation of the background processing mode. Background processing continues to drain the playback buffer until flags are set to abort or stop, or until the playback buffer is empty. Users may request playback in a blocking mode, which will return control to the user program when playback has ceased, or non-blocking, which allows user processing while playback buffers are being drained in background.

[1428] Tone Generator

[1429] Tones are generated through ioctl( ) calls to the synthesizer module. This module sends controls to the synthesizer circuitry on the audio board resulting in tone generation. Controls include duration, decay and attack.

[1430] Mixer Control

[1431] Volume Control is accomplished through ioctl() calls to the mixer module. This module sends controls to the mixer circuitry on the audio board resulting in volume level controls. This includes control for the master volume, bass, treble, fm, PCM, recording monitor and others.

[1432] Touch Panel Operator Interface CSC

[1433] TPOI Initialize CSU

[1434] The TPOI Initialize CSU clears the 10-minute audio buffer, opens the TPAD for reading and writing, opens the serial ports to the Touch Panel and VCR for reading and writing, and sends the primary screen to the Touch Panel. Site name abbreviations are retrieved from the DBS via embedded SQL queries. The TPOI Record Audio CSU is setup to be called when audio data is available. Playback is disabled.

[1435] The 10-minute audio buffer is stored in an array of audio data records and has a head and tail pointer into the array for recording (head) and playback (tail). The Touch Panel is connected to the first serial port /dev/tty01; the VCR is connected to the second serial port /dev/tty02

[1436] TPOI Record Audio CSU

[1437] The TPOI Record Audio CSU is activated from the main loop or from the TPOI Receive Commands CSU and reads audio data from the TPAD into the 10-minute audio buffer. The head pointer is then updated to the next position in the buffer, wrapping around to the beginning of the buffer if necessary. The tail pointer is updated if necessary.

[1438] TPOI Playback Audio CSU

[1439] The TPOI Playback Audio CSU is activated from the main loop or from the TPOI Receive Commands CSU and writes audio data to the TPAD out of the 10-minute audio buffer. The tail pointer is then updated to the next position in the buffer, wrapping around to the beginning of the buffer if necessary.

[1440] During playback the corresponding callback buttons on the touch panel are flashed.

[1441] TPOI Receive Commands CSU

[1442] The TPOI Receive Commands CSU waits for input from the Touch Panel and decodes the sequence of characters from it into operator commands. The Touch Panel returns a status and position sequence for each operator finger action; the status can be press, drag, or release. If a valid button on the touch panel is pressed, a short tone is sounded as feedback to the operator.

[1443] If the command directly involves the VCR, the appropriate command is sent to the VCR through the TPOI Control VCR CSU. The Touch Panel screen is updated to reflect the new VCR status (e.g. Recording . . . ).

[1444] If the command involves audio callback, the TPOI Playback CSU is setup to start or stop output at a specific time.

[1445] Playback continues until stopped.

[1446] Otherwise, the command is sent to the TPOI Send Commands CSU for processing by the SDS. These include the camera and video commands.

[1447] TPOI Send Commands CSU

[1448] The TPOI Send Commands CSU sends commands to the CSD to be sent to the SDS and then waits for a response (if necessary) and returns it.

[1449] TPOI Error Handler CSU

[1450] The TPOI Error Handler CSU receives error statuses from the various TPOI CSUs and sends these messages to the CSD and system log file.

[1451] TPOI Control VCR CSU

[1452] The TPOI Control VCR CSU passes VCR commands to the VCR through the serial port, waits up to 1 second for a response, and returns a status to the caller. If no response from the VCR is received, a timeout status is returned.

[1453] TPOI VCR Status CSU

[1454] The TPOI VCR Status CSU queries the VCR for the current playback/record mode and tape counter value and updates the touch panel display accordingly. If no tape is loaded in the VCR, the tape counter is replaced with the message “NO TAPE”. If the VCR is powered off or in an unknown condition, all VCR control buttons are highlighted and disabled.

[1455] Shutdown CSC

[1456] The Shutdown CSC is composed of three CSU's:

[1457] VTS Shutdown

[1458] Console Shutdown

[1459] Shutdown Override

[1460] VTS Shutdown CSU

[1461] The VTS Shutdown CSU allows a system supervisor or administrator to request a complete system shutdown be initiated. A confirmation interface is displayed and upon acknowledgement, a command is sent to SDS requesting a system shutdown begin. This would result in the same series of events to occur as when an UPS low battery alarm is received by SDS. The Vessel Data Cards for any active vessels are queued to the system printer, the database is secured, and a Unix shutdown of all machines begin. This process may be interupted by the Override Shutdown CSU.

[1462] Console Shutdown CSU

[1463] The Console Shutdown CSU allows a system supervisor or administrator to request a shutdown of the current ODP console. A confirmation interface is displayed and upon acknowledgement, the processes currently running on that ODP are terminated and a Unix shutdown command is initiated. There is no interuption to this task.

[1464] Shutdown Override CSU

[1465] The Shutdown Override CSU allows a system supervisor or administrator to request a shutdown of the system to be aborted. A confirmation interface is displayed and upon acknowledgement, a command is issued to SDS to abort the proceeding system shutdown. If the override is requested before the Unix shutdown commands have been issued, the SDS will interupt shutdown proceedings and resume processing. If the Unix shutdown commands have been issued by the SDS there is no override and the shutdown of the system proceeds.

[1466] Alarm Zone Control CSC

[1467] The Alarm Zone Control CSC is composed of three CSUs:

[1468] Stationary Safety Zone CSU

[1469] Traffic Lane Safety Zone CSU

[1470] Swing Circle Safety Zone CSU

[1471] Stationary Safety Zone CSU

[1472] The Stationary Safety Zone CSU allows the operator to construct or delete a stationary safety zone. An operator interface menu allows the operator to select the desired action. A corresponding user event is then issued to the Chart Interface Daemon to allow the appropriate map, database, and SDS interaction to occur. Upon successful creation of the zone, alarm notification will occur if a vessel is in close proximity of the Safety Zone boundary.

[1473] Traffic Lane Safety Zone CSU

[1474] The Traffic Lane Safety Zone CSU allows the operator to construct or delete a traffic lane safety zone. An operator interface menu allows the operator to select the desired action, A corresponding user event is then issued to the Chart Interface Daemon to allow the appropriate map, database, and SDS interaction to occur. Upon successful creation of the zone, alarm notification will occur if a vessel is in close proximity of the Traffic Lane boundary.

[1475] Swing Circle Safety Zone CSU

[1476] The Swing Circle Safety Zone CSU allows the operator to construct or delete a swing circle safety zone. An operator interface menu allows the operator to select the desired action. A corresponding user event is then issued to the Chart Interface Daemon to allow the appropriate map, database, and SDS interaction to occur. If the operator has requested to create a swing circle, an additional interface is displayed to allow the operator to input the number of shots of chain to be used in the calculation of the swing circle radius. This interface is automaticly invoked when a vessel is anchored through the Vessel Action Menu. Upon successful creation of the zone, alarm notification will occur if a vessel is in close proximity of the swing circle perimeter.

[1477] Alarm Criteria CSC

[1478] The alarm criteria CSC allows a supervisor or system administrator to set the desired time and distance values to be used in proximity alarm calculations. A user interface retrieves the previously set values from the database and displays them for review. The user logon information is retrieved from shared memory and the authorization level is verified. IF the user is logged on with as a supervisor or administrator then the values may be changed. If the values are changed then the new values are saved in the database and a command sent to SDS to initiate the change in the calculations.

[1479] Estimated-Positioning Route Control CSC

[1480] The estimated-positioning route control user interface allows the user to add or delete an EP route. The interface interprets the requested action from the operator and sends an appropriate track message to CSD, which in turn sends a track message to the SDS for track initiation.

[1481] Track Control CSC

[1482] Add Radar Track CSC

[1483] Add Radar Track CSC allows an operator to command the VTS radars to begin tracking a certain object based on radar returns as reflected by the Radar Image Draw Module. The requirement is for a VTS operator to have the capability to perform manual track acquisition. The execution/data flow is as follows: the Add Radar Track CSC sends latitude/longitude, sector mask and radar site ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor of the desired acquisition. The radar processor then sends data on the acquired track back to SDS.

[1484] Add EP Track CSC

[1485] Add EP Track CSC allows an operator to command the SDS to begin calculating the position of a track along an estimated positioning route. The requirement is for a VTS operator to have the capability to designate the initial position and speed of the EP track. The execution/data flow is as follows: the Add EP Track CSC sends latitude/longitude, speed and EP route ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS then initiates the track and updates the track's movement within the track database.

[1486] Swap Track CSC

[1487] The Swap Track CSC allows an operator to command the SDS to swap the track information for two specific tracked objects. The execution/data flow is as follows: the Swap Track CSC sends the track ID's to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS then swaps the track information in the track database which causes the operator display to reflect the icon and track tags displayed for the selected objects to be swapped.

[1488] Change Radar Track CSC

[1489] Change To Radar Track CSC allows an operator to command the VTS radars to begin tracking an object that had previously been calculated as an EP track. The execution/data flow is as follows: the Change to Radar Track CSC sends an EP track ID, latitude/longitude, sector mask and radar site ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor of the desired acquisition. The radar processor then sends data on the acquired track back to SDS. The SDS then performs a swap track that attaches the track information of the EP track to the new radar acquisition and then deletes the extraneous extra track.

[1490] Change EP Track CSC

[1491] Change To EP Track CSC allows an operator to command SDS to begin performing an estimated positioning calculation on an object that had previously been an active radar track. The execution/data flow is as follows: the Change to EP Track CSC sends a track ID and EP route ID to the Command Status Daemon, which in turn sends a track message to the SDS. The SDS notifies the radar processor to drop the designated track. SDS then begins an EP track at the last position of the track at its last reported speed. The SDS then performs a swap track that attaches the track information of the radar track to the new EP track and then deletes the radar track.

[1492] Handoff Track CSC

[1493] The Handoff Track CSC is passed the Tdbm track ID of the vessel to handoff. The following pseudocode demonstrates its functioning:

[1494] get the Tdbm track ID from the command-line

[1495] get the Tdbm track information for the specified track ID

[1496] get the current logon data

[1497] IF the vessel's sector mask matches the current console sector mask THEN

[1498] change the sector mask to all one's

[1499] update the Tdbm track information

[1500] send an ‘Update Track’ message to the SDS with the specified track ID

[1501] ELSE

[1502] send an error message to the command-status daemon

[1503] ENDIF

[1504] Accept Track CSC

[1505] The Accept Track CSC is passed the Tdbm track ID of the vessel to accept. The following pseudocode demonstrates its functioning:

[1506] get the Tdbm track ID from the command-line

[1507] get the Tdbm track information for the specified track ID

[1508] get the current logon data

[1509] IF the vessel's sector mask is all one's THEN

[1510] change the sector mask to the console sector mask

[1511] update the Tdbm track information

[1512] send an ‘Update Track’ message to the SDS with the specified track ID

[1513] get the SECTOR_MASK_HISTORY field from the VESSEL_TRACK table from the database for the specified vessel

[1514] bitwise OR the sector_mask_history with the console sector mask update the SECTOR_MASK and SECTOR_MASK_HISTORY fields in the VESSEL_TRACK table in the database for the specified vessel

[1515] ELSE

[1516] send an error message to the command-status daemon

[1517] ENDIF

[1518] Drop Track CSC

[1519] The Drop Track CSC provides the operator the capability of dropping a track that is either no longer of interest or was begun inadvertently. Once the track is designated for dropping, it will be removed from the track database and the display. The data flow for the Drop Track CSC consists of a message sent to SDS to stop generating updates for the track.

[1520] Dock Track CSC

[1521] The Dock Track CSC enables the operator to indicate that a vessel in his/her area of responsibility has docked. Once a vessel has reached a destination within the port where it will dock, the operator will choose the “DOCK” option from the Vessel Action Menu. The status of the vessel in the track database will then be changed to “docked”.

[1522] Anchor Track CSC

[1523] Within a VTS operator's area of responsibility, when a vessel has reached an anchorage destination, the Anchor Track CSC provides a mechanism for entering anchorage information into the system. The Anchor Track CSC is invoked from the Vessel Action Menu. This CSC will cause the selected vessel's status to change in the track table to “anchored”. It also changes the traffic count and causes the swing circle user interface to be invoked, allowing the operator to construct a swing circle for that vessel.

[1524] Out-of-Area Track CSC

[1525] When a vessel exits the port, the Out-of-Area Track CSC, enables the VTS operator to enter this information into the system. The Out-of-Area Track CSC is invoked from the Vessel Action Menu. A status change to “OutofAOR” will occur in the track database upon execution. Additionally, the traffic count will be altered.

[1526] X-Windows Print (XPWIN) CSC

[1527] The XPWIN CSC is divided into 4 CSUS:

[1528] XPWIN Mainline

[1529] XPWIN Decolorize Image

[1530] XPWIN Print Window

[1531] XPWIN Print Line

[1532] XPWIN Mainline CSU

[1533] The XPWIN mainline CSU parses command-line arguments, determines the window to print, gets a copy of the window to print, opens a connection to the printer, and calls the Decolorize Image and Print Window CSUs to print the window.

[1534] XPWIN Decolorize Image CSU

[1535] The XPWIN decolorize image CSU converts the window colormap to greyscale values and finds the minimum, maximum, and mean grey levels in the window. Using the mean grey level, it then performed a linear contrast expansion on each greyscale value; the amount of expansion is selectable from the command-line and defaults to 110%.

[1536] XPWIN Print Window CSU

[1537] The XPWIN print window CSU scales and dithers a window image to fit the size of the page and outputs the resulting image to the printer. The scaling assumes a 1:1 pixel aspect ratio. The dithering uses the Burke coefficients and a serpentine scan over the window image. The Burke coefficients are as follows:

[1538] These coefficients allow the use of bit-shift operations to distribute the brightness error in the output image. For more information on dithering, consult “Bit-Mapped Graphics”, McGraw-Hill, Rimmer, ISBN 0-8306-3558-0.

[1539] XPWIN Print Line CSU

[1540] The XPWIN print line CSU outputs a line of bitmapped graphics to the printer. If compression is not enabled, the line of graphics is sent straight through. Otherwise, it is run-length encoded as specified for ‘Mode 2’ compression and then sent to the printer; compression generally achieves a 75% reduction in output data size.

[1541] For more information on sending graphics to an HP LaserJet printer, consult “HP LaserJet Programming”, Hewlett Packard, Binstock, Babcock, & Luse, ISBN 0-201-57736-4.

[1542] Logon/Logoff CSC

[1543] The logon/logoff CSC provides database and display access control for each operator at the VTC. It also allows an operator to select the sector(s) to control at the console. [350-387]

[1544] The user is first presented with a window containing username and password boxes; the operator types the username and password on the keyboard, but only the username text is echoed on the screen. Once the operator has entered the password, an embedded SQL connect call to Oracle is performed to attempt the login. If the connection fails, an error message is displayed and the username, password, and authorization level in the console configuration buffer are cleared.

[1545] If the connection succeeds, a query of the user authorization table is performed to get the operator's authorization level and real name which is then placed in the console configuration buffer. A second window is displayed listing the available sectors in the database for the operator to choose from. Once chosen, a sector mask is built using the sector ID(s) of the selected sector(s), where bit 0 corresponds to sector 1, bit 1 corresponds to sector 2, etc.

[1546] The console configuration buffer is a shared-memory buffer that contains the current user name, password, authorization level, sector mask, remote site masks, and remote site names. For those remote sites that are not accessible from the current sector(s), the masks and names are cleared.

[1547] Database Form Interface CSC

[1548] The Database Form Interface CSC retrieves the current Oracle username and password from the Logon/Logoff shared-memory buffer and runs the specified form. The following pseudocode demonstrates its functioning:

[1549] get the logon/logoff data

[1550] get the form filename from the command-line

[1551] change to the form directory

[1552] create a command string of the form “hpterm -e runform30

[1553] USERNAME/PASSWORD FORM-NAME”

[1554] execute the command string

[1555] Radar Configuration Interface CSC

[1556] The Radar Configuration Interface CSC is executed from the Radar Configuration database form when a change has been posted by a user. The form passes the radar ID and remote site ID affected by the change to the radar configuration interface. A radar command is then constructed and sent to SDS through the command status daemon.

[1557] Tactical Database Manager (Tdbm) CSC

[1558] The Tdbm CSC software is considered COTS. Therefore, contents of this section are considered completed by Tdbm manuals available from INRI.

[1559] Radar Image Draw Module (RIDMO) CSC

[1560] The Radar Image Draw Module CSC creates and integrates a draw module that provides the capability to display a composite bitmap image of an operators area of responsibility. The Radar Image Draw Module CSC is begun when a signal is generated by the Radar Image Daemon. RIDMO gets radar data from shared memory (where Radar Image Daemon stored the data). RIDMO then sends radar bitmaps to the Chart Manager. RIDMO also receives data input by the operator indicating radar selection and attribute changes.

[1561] Vessel Data Card CSC

[1562] The Vessel Data Card CSC assists the operator in keeping track of certain information related to all VTS participant vessels within a harbor area. The Vessel Data Card will appear in a window when the VTS operator performs any of several track manipulation functions.

[1563] CSCI Data

[1564] Internal CSCI data elements and structures are documented with the relevant CSC or CSU discussions in this document.

[1565] CSCI Data Files

[1566] This following subparagraphs contain descriptions of each of the shared data files of this CSCI.

[1567] Data File to CSC/CSU Cross Reference

[1568] Oracle Database

[1569] The Oracle Database is accessed by this CSCI using embedded structured query language (SQL-ANSI standard xxxx) calls. The Oracle Database provides the following information to this CSCI:

[1570] Operator authorization data

[1571] Remote site equipment configuration

[1572] VTC equipment configuration

[1573] Vessel identification and transit data

[1574] The method of access is through embedded SQL calls from the ANSI C language. Oracle's PRO*C manages the communications to and from the SQL server. Oracle's SQL*Net provides access transparently over the network to the database processor as if the database was local. This is accomplished using the SQL*NET alias file, /etc/sqlnet.

[1575] Tdbm Data

[1576] The Tdbm data is maintained by the SDS and is loaded on each console in shared memory by the Tdbm CSC.

[1577] Radar Scan Data

[1578] The radar scan data (image) is maintained by the SDS and is loaded on each console in shared memory by the RID. Each RIDMO process uses this data to update the UB CHART displays.

[1579] UB Map Files

[1580] UB Map Files reside on each ODP in the directory /home2/mapdata. The UB CHART process manages access to these files.

[1581] Menu files

[1582] The menu files reside on each odp in the directory /h/Nauticus/data/local/System/Menus and describe the menus and menubar of the ub finder program.