| Previous | TOC | Next |
4. INFORMATION PROCESSING
4.1 Introduction
4.2 Mandates
4.2.1 Information Processing (Soft-Real Time)
4.2.1.1 Software Engineering Services
4.2.1.1.1 Programming Languages
4.2.1.1.2 User Interface Services
4.2.1.1.3 Data Management Services
4.2.1.1.4 Data Interchange Services
4.2.1.1.5 Graphics Services
4.2.1.1.6 Communication Services
4.2.1.1.7 Operating System Services
4.2.1.1.8 Information Management Resources
4.2.1.1.9 Distributed Computing Services
4.2.2 Information Processing (Hard-Real Time)
4.2.3 Data
4.2.3.1 Shared Data Environment (SHADE)
4.2.3.2 Digitized Audio
4.2.3.2.1 Digital Audio Routing to Support Integrated
Tactical SIGINT Architecture (ITSA) Systems
4.2.3.2.1.1 Asynchronous Distribution
4.2.3.2.1.2 Synchronous Distribution
4.2.3.2.2 Digital Audio Encoding Schemes
4.2.3.3 Data Formats
4.2.3.3.1 Signal and Signal Related Information
4.2.3.3.2 Digitized Pre-detected Intermediate
Frequency Data
4.2.3.4 Dissemination Reports
4.3 Emerging Technologies
4.3.1 Operating Systems Services
4.3.2 Distributed Computing Services
4.3.3 Object Oriented Software Development
4.3.4 Communications Geolocation Data Exchange Formats
4.3.5 Signal Related Information (SRI)
4.3.6 Common Signal External Data (SED) Format
The information SIGINT systems process is perishable and the processing of this information must be done in real time. Real time is a relative term and can range from days to microseconds depending on the frame of reference. The following two definitions of real time are widely accepted and provide a frame of reference for the discussion of real-time information processing.
The purpose of implementing information-processing standards is to improve interoperability and reduce the effort required to develop, integrate, and maintain software. The JTA mandates the Defense Information System Agency's (DISA) Defense Information Infrastructure (DII) Common Operating Environment (COE) as the primary mechanism to implement software standardization. An overview of the DII COE is provided in the following paragraphs. Documents and additional information can be obtained from the DII COE home page (http://spider.osfl.disa.mil/dii/ ).
The DII COE is a not a system; it is a foundation for building open systems. It encompasses architecture, standards, specifications, software reuse, shareable data, interoperability, and automated integration in a cohesive framework for system development.
The DII COE consists of the following layers:
The COE is designed to allow developers to concentrate their efforts on building mission area applications rather than duplicating system infrastructure services. Common standards support the objective of interoperability. The use and evolution of the COE and the standards it embodies will advance the goal of building systems that are compatible, while minimizing program costs through systematic software reuse.
|
|
Software engineering services provide system developers with the tools for the development and maintenance of applications. Language services provide the basic syntax and semantic definition to describe the software function.
|
|
In addition to the software engineering services identified in the JTA, the following guidance is provided.
Software design shall emphasize ANSI standards for high-level software coding to allow maximum portability of the code. To facilitate software reuse, a standard coding process (e.g., Object Oriented Design) will be utilized to ensure maximum portability.
The acceptable options for High Order Language (HOL) programming language is:
|
|
|
|
|
|
User interface services define how users may interact with an application. Depending on the capabilities that users require and the applications, these interfaces may include the following specifications: user interface, graphical client server, object definition management, character-based user interface, and window management.
|
|
Central to most systems is the management of data that can be defined independently of the processes that create or use it, that can be maintained indefinitely, and that can be shared among many processes. Data management services may include data dictionary/directory, database management system, and transaction processing.
|
|
Data interchange services provide specialized support for the interchange of information between applications and to/from the external environment. These services handle data interchange between applications on the same platform and applications on different (heterogeneous) platforms. These services include document interchange, characters and symbols, product data interchange, optical digital technologies, technical data interchange, hardware applications, raster/image data interchange, mapping, compression, etc.
|
|
Graphics services provide functions required for creating and manipulating pictures. These services include raster graphics, vector graphics, and device interfaces.
|
|
Communication services support distributed applications requiring data access and applications interoperability in heterogeneous or homogeneous networked environments. These services may include application-oriented network services, transport-oriented network services, and subnetwork technologies services.
|
|
Operating system services are the core services needed to execute and administer the application platform and provide an interface between the application software and the platform. Application programmers will use operating system services to access operating system functions. Operating system services may include kernel operations, real-time extensions, clock/calendar, fault management, shell and utilities, operating system object services, and media handling.
|
|
Information Management Resources provide data containers and data storage, retrieval, replication, and removal. Containers may be used for databases, collected data, or for finished reports. All forms of data may be stored within the same container or distributed across multiple containers. Distributed data storage allows linked data and corresponding metadata to reside in different data containers. Metadata standards allow all forms of data to be located regardless of where they reside. This supports ease of access and processing by appropriate users and resources.
|
|
These services allow various tasks, operations, and information transfers to occur on multiple, physically-or logically-dispersed, computer platforms. These services include, but are not limited to, global time; data, file, and name services; thread services; and remote process services. There are two categories of Distributed Computing Services, Remote Procedure Computing and Distributed Object Computing.
|
|
The JTA has mandated DISA's DII COE, and it is successfully being used in client server applications. The many benefits derived from its use have been well documented. The DII COE has not yet developed a kernel around a real-time operating system; therefore, it cannot be directly applied to real-time software development. However, the concepts employed by the DII COE can be applied in principle to real-time software applications development with the same resulting benefits. Standardizing on APIs written in accordance with the mandated JTA POSIX standards will significantly enhance the probability of successfully porting the software application for reuse.
During the software development process, a primary emphasis must be placed on writing reusable and extensible software applications. Standard functions and services should be used by the developers and not rewritten for each new application.
It is recognized that imposing standards on real-time software development increases the associated overhead. Wherever possible, this additional overhead should be accounted for in the design (i.e., during hardware selection). When event timing or throughput requirements cannot be met within the purview of a mandated standard, an exemption from that specific portion of the standard shall be requested.
The DII COE does not currently support real time operating systems, however the real-time software development standards listed in the JTA are applicable.
|
|
Annex 6 provides an overview of each of the JTA mandated and emerging software standards.
SHADE was developed for the DII COE for data handling. For true interoperability, all data users must be able to use the data received without having to reformat or translate it. SHADE is a strategy for data management, data sharing, and it provides the mechanisms needed to access existing large legacy databases on mainframes. It includes the required data access architectures, data share methodology, reusable software and data components, and guidelines and standards for the development and migration of systems that meet the user's requirements for timely, accurate, and reliable data (See Figure 4-2). Documents and additional information can be obtained from the DII COE home page (http://spider.osfl.disa.mil/dii/).
|
|
Digitized audio refers to the formatting techniques and encoding schemes used to convert analog audio sensor data into digital audio for data transmission and storage.
There are two primary methods of providing digital audio data to ITSA processing and analysis systems at Regional SIGINT Operations Centers (RSOC): (1) USSID 126 Collected Signals Data Format (CSDF) formatted digital audio files forwarded asynchronously via the wide area network (WAN) and, (2) Real-time continuous synchronous T1 digital audio trunks.
Some JASA systems currently employ USSID 126 formatting techniques to provide collected audio data to ITSA systems. USSID 126 and JSH Signal Related Information (SRI) mandates are used to convert mission data into rigidly formatted files. The main computer center (MCC) then transmits the files over the WAN to UNIX-based client/server subscribers for processing and analysis.
Numerous Government-Off-The-Shelf (GOTS) products support the distribution of asynchronous CSDF compliant audio files. Formatting mission data into CSDF compliant audio improves interoperable distribution and storage among ITSA systems. In subsequent versions of the JSH, a small sub-set of mandates will be listed to improve asynchronous audio encoding, distribution, and storage.
JASA systems are not currently providing digital audio via standard T1 feeds to ITSA client-server processing and analysis systems, but this option requires consideration for future operations. The JSWG Interoperability Subcommittee, in collaboration with the Regional SIGINT Operations Center Program Management Office, is currently leading efforts to define a standard community digital audio format for storage and transmission -- synchronous and asynchronous. The current de facto standard for real-time remoted collection feeds utilizes an 8 bit µ-law digital audio encoding scheme in accordance with ITU G.711. The encoded audio is transported via 1544 kbit/s trunks in accordance with ITU G.703 and G.733.
Real-time audio collection and transmission from JASA systems to ITSA processing centers shall be capable of complying with:
|
|
Real-time audio transmission from JASA systems to the tactical SIGINT Internet shall comply with a synchronous T1/E1 rate structure as specified in the following:
|
|
|
|
|
|
The current digital audio encoding scheme for basic system-to-system audio interoperability is 8 bit µ-law in accordance with ITU G.711. For system internal use and common application sharing, other audio encoding formats (e.g., A-law, Linear, CVSD, and CELP) may be more appropriate. Future versions of JSH will provide additional mandates in this area.
Standard data formats are critical to sharing and exploiting unprocessed or semi-processed cryptologic intelligence data between JASA-compliant sensors and ground/surface stations. Moreover, standard data formats are a key to enhanced national and tactical integration efforts under the UCA and ITSA concepts. The CSDF manual prescribes overall format guidance for collected signals and associated Signal Related Information (SRI).
The CSDF manual, promulgated by USSID 126, provides specifications for data formats that facilitate the exchange of collected signals data and SRI between processing subsystems. The formats prescribe rigid record and field-format requirements that enable networked computer systems to share data. The supplemental references listed in Section 4.2.3.3.1 provide CSDF implementation details.
Data formats of SRI reports shall comply with the following:
|
|
|
|
The following supplemental government documents provide CSDF implementation references:
Data formats for pre-detected IF or baseband data shall comply with the following:
TBD
The following SIGINT directives apply when the associated reporting function is required:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Communications Geolocation Data Exchange Formats identify information to be passed between similar or dissimilar collectors to enable TDOA/FDOA geolocations on pre-D data.
To facilitate data sharing and worldwide signal fusion and analysis, a common Signal External Data (SED) Descriptor Word (DW) format is required. This format is a subset of the Interactive ELINT Processor (IEP) format being developed to support cross-mission geolocation efforts. The SED DW is consistent with both the IEP file structure and field. The modular nature is designed to support signal parameterization while providing the flexibility to add or delete individual data types without effecting the others. The format mandates only the minimum set of fields for each data set. This enables the collector to add system unique fields (i.e., calibration, unique collection capabilities and maintenance functions) to the format without disturbing interoperability.
| Previous | TOC | Next |
