A Prototype for An Intelligent Information System for Jamming and Anti-jamming Applications of Electromagnetic Spectrum. Mohamed O. Abo Khozium Egyptian Air Force [email protected] Hesham Ahmed Hassan Faculty of Computers & Information, Cairo University [email protected]

Khaled F. Shaalan Institute of informatics, The British University in Dubai (BUiD) [email protected]

Mokhtar Boshra Riad Faculty of Computers & Information, Cairo University [email protected]

Abstract As the pace of modern battle has increased, headquarters and Electronic Warfare (EW) staff need to process increasing volumes of information in a decreasing amount of time. Assistance in this critical task is proposed by developing the Electronic Warfare Intelligent Information System (EWIIS) that deals with processing of electronic warfare, communications, radar, maps, war missions … etc. This system is aimed at achieving the best performance with a friendly system in spite of the existence of hostile actions. EWIIS deals with different sources of data. It helps visualize mission scenarios and suggests the best combination of weapons to successfully complete the mission with minimum loss. Keywords EW, Radar, ESM, ECM, ECCM, SAM, Jamming, Jamming Pods, Pulse, Pulse width, FEBA, Knowledge base, Intelligent system.

(  )          ! "  #     $          ! " ! #"           %! &' !% #%()*  % % "  & #" + ,  , -$ #& #" %) %")* #&      23 (  4 … ( + *!. !! #/0 ' %& .8!  #) "! ," , +  8!)& 8!& 9 3  #& 56 7) -  * %"  0% #2!,' ;! <  #  +"   => &  8!( ;! ( + ( 9 )/ ? B!%.' %" #  #!! A * *!.  "  ;! ( + 9 & .@    "  < &>) " #!! C < ' #   !D  & E!. 
1.

Introduction

In a modern war activity, large number of offensive or defensive weapon systems rely on heavy traffic of information, also through radio links, and on high speed reaction of these systems, whatever the weather and daylight conditions may be. This trend of modern war has led to a sustained development of Electronic Warfare (abridged EW), the goal of which is to gain – as completely as possible – the air superiority for electronic signal transmission. Electronic Warfare (EW) [1, 3, 4,5] describes techniques that exploit an adversary’s use of the electromagnetic spectrum or defend friendly use of the electromagnetic spectrum. There are three subdivisions of EW: Electronic Support, Electronic Attack and Electronic Protection. 1.1 Electronic Support (ES), previously known as Electronic Support Measures (ESM), is considered the eyes and ears of the EW effort, in that electronic support is responsible for the detection, processing, recording and identification of electromagnetic energy transmitted by hostile, friendly and neutral radar systems. The main aim of Electronic Support is to gain sufficient information about radar sensors to allow an understanding of the radar’s characteristics including its role, its method of operation, and its strengths and weaknesses. With this information, the Electronic Support system can identify the radar, assess its relative threat and provide information to the operator on how best to manage the radar’s presence. Many factors have impact on the effectiveness of Electronic Support, but all factors can be classified under one of the following categories [14]: * Transmitter characteristics including transmitted power, operating frequency, polarization, signal bandwidth; * Transmitting antenna characteristics including beam width, side lobe levels, and scan patterns; * Environmental characteristics between the radar and the electronic support equipment including atmospheric and meteorological conditions; and the capability of the electronic support equipment including the receiving antenna characteristics, and the receiver capabilities and sensitivity. Electronic support is a passive activity as the electronic support equipment does not transmit any electromagnetic energy in the performance of its roles. It is important that the adversary remains unaware of the ES activity; because there are many tactics an adversary radar system can employ to make the Electronic Support role even more difficult than it is normally. Additionally, remaining passive lessens the opportunity for the adversary radar to plant false information into the transmissions in an attempt to corrupt or confuse the Electronic Support effort. 1.2 Electronic Attack (EA) [1,5] previously known as Electronic Counter Measures (ECM) is conducted on radar systems to reduce or prevent the radar’s use of the electromagnetic spectrum effectively. Enemy sensors are the main focus of EW action. Active sensors are particularly vulnerable as these sensors are designed to transmit and receive electromagnetic energy. EA tactics and tools look to exploit active sensors by analyzing the transmission (ES) and then attacking the receiver. EA can be conducted against all electromagnetic systems including communications systems. Radar systems are operated to detect, acquire and track targets with the ultimate view to engaging and destroying the target. To that end, interfering and degrading the performance of radar systems is often of critical value to the targeted platform’s survival and ability to carry out its intended role.

-2-

1.3 Electronic Protection (EP) [1,5] previously known as Electronic Counter Counter Measures (ECCM), is to ensure continued friendly use of the electromagnetic spectrum despite adversary EA and ES. Countering EA efforts is the main focus of electronic protection although some electronic protection techniques are also designed to make adversary ES more challenging. EP and EA fields tend to be complimentary and reactive fields of endeavor in that an advance in technology and techniques in one field necessarily results in research, development and advancement in the other. The designers of military radar systems assume that their systems operate in the most hostile of electronic environments and therefore design the radar with EA and EP in mind. EP is not solely a military concern, however. Civilian radar systems also have to operate in hostile electronic environments and must therefore have EP built-in. The civilian environment is often hostile due to the operation of other radar and electromagnetic systems in the same physical location as the radar system. EP techniques developed for the military domain can allow civilian radar to operate in the presence of other sources of potentially disruptive electromagnetic energy. The rest of the paper is structured as follows . Section two discusses the motivation behind the effort to develop the system. Global view of the system and its interaction with its environment is given in section three. Detailed discussion about the different components of the system and how they are related is given in section four. Data movement and communications are shown in section five. Section six gives a case study to show the system operation. Section seven concludes the paper and suggests future work. 2.

Motivations

To develop intelligent information system that can store, retrieve, process, report information about attacking scenarios that could be placed by users of the system. The system should be robust, efficient, and capable of working in a multi-user environment. Also the system should be capable of detecting and analyzing modern threats and developing the proper techniques. These systems can provide the developing countries with capabilities that not easily reachable. From now on we call our proposed system Electronic Warfare Intelligent Information System (EWIIS). 3.

Typical Environment for EWIIS

As normal information system development life cycle [6,9,22] we need to analyze the requirements and tasks of the proposed system, the different input sources, output expected in order to guarantee the fulfillment of the requirements. Figure 1 shows the main input/ processing/output of EWIIS and the different categories of users expected to interact with it. For EWIIS to fulfill its mission which is to suggest and test tactics to complete a mission with the suggestion of the best platform to use among set of prescribed platforms; it should be fed with parameters about the ESM. This input is supplied by the EW officers. Mission data and an initial plan is given by the Planning officers. Information about the different platforms available for the system is given once and may be updated by technical officers. EWIIS starts from the initial scenario and with the information given about the type and location of radar starts to analyze this scenario and looks for opportunities for enhancement. The successive enhancement processes depend on studying the different

-3-

parameters for all of platforms, radar and geographical area of the target stored in EWIIS knowledge base. Possibly ending with more than one scenario; EWIIS recommends best path for certain platforms that guarantees successful completion of the mission. Suggested tactics, results reports and suitable techniques will be offered to EW, planning and technical officers. More elaboration of knowledge base system will be given in the next section.

INPUT

EW Officers

OUTPUT

Electronic Support Measures Electronic Intelligence

Suggested tactics

EW Officers

Results Result Report Report

Planning Officers

Suitable Techniques

Technical Officers

EWIIS Planning and Mission Data

Planning Officers

Technical Officers

Electronic Warfare Intelligent Information System.

Available Equipment and Pods

Output Verifier

KBS

Selector

. Position Identification

Library of EA &Pods Library of Jammer andTechnique Way points EP s Library of Threats Data

Figure 1. EWIIS Environment

-4-

Result Analyzer

4.

The Proposed EWIIS Architecture

This section introduces the components of EWIIS and their functionality. It also describes the interactions among these components. Figure 2 summarizes these components and their relationships.

Threats Library

Threats Data

Data Acquisition & Manipulation

Pods Library

Platforms Technical Data

Mission Plan Data

User Adaptive Refinement

Intelligent Information System (IIS)

Available Decisions

Reporting & Documentation

Plan Doc.

Map info.

Radar coverage pattern

Figure 2 Overall Architecture of EWIIS

-5-

4.1 Data Acquisition and storage requirements This component is responsible for accepting all the data about threats, Electronic support measures of the scenario needed to be tested. As most of these data are of visual nature as maps, radar locations, target locations; it should be taken into consideration that they must be fed to the system in the same way as they are dealt with in real life. Due to Data visualization [16] and their huge volume, we have to store the following data, among others: * Map information. * Radar location. * Target location. * Mission path. we have to choose between storing all these information in one container for each mission scenario, or to divide this information into layers where each layer is concerned with separate aspect of the mission data. The second choice provides high level of reusability. Reusability comes from the fact that the same map is needed to be stored once in the map layer and can be linked to more than one scenario. Indeed this also leads to another big benefit of storage optimization which is a challenge for any system that deals with massive information. For our case study, presented in section 6, the standalone data file needed 6443 KB every mission scenario while the layered method took only 5KB to store the differences between sequenced mission scenarios. The 6443 KB is stored once in all scenarios. 4.2

Intelligent Information System (IIS)

This is the major component of EWIIS that makes the analysis of mission paths and makes suggestions of enhancements. This is the component where the intelligence comes into the scene in EWIIS. The Knowledge Base contains four different parts; verifier , selector, position identifier , and result analyzer . 4.2.1 The Verifier : Plays two roles : Firstly it checks the input data consistency such as ensuring the correctness of radar parameters. Secondly it ensures the consistency between the given input and the resulted output data based on set of rules which were given by the planner. For example air craft should have 10% of fuel after finishing mission. 4.2.2 The Selector : Simply the objective of this part is to select between alternatives (choose best radar to be jammed by fighter) or select between mutually exclusive options (choose which radars will be jammed by support jammer and which radar will be jammed by fighter). 4.2.3 The Position identification : specifies the optimum location of some activities such as optimum location of support jammer umbrella based on some rules related to the victim radar . 4.2.4 The Result analyzer : It analyzes and evaluates EWIIS results then proposes suitable recommendations to get better solutions. 5.

Data Movement and System Components

From a data-oriented point of view we have developed a categorization of the different battle field variables: * Radar - Early Warning radar. - Acquisition radar. - Fire control radar. EWIIS uses the following list to differentiate between radar.

-6-

List of Radar parameters : Min. Frequency Power Polarization Pulse repetition frequency Radar cross section Reception losses Max. range

Max. Frequency Gain transmitted Wave length Beam width Scan rate Azimuth antenna coverage ECCM techniques

Pulse width Gain received Band width Listening time Transmission losses Elevation antenna coverage

* Platforms: by platforms we mean the planes that will do the mission and it could be one from the following; 1 - Bomber and fighter. * Bomber; which carry bombs in order to destroy the target in addition to self protection jamming pod. * Fighter; which carry missiles in order to protect the bombers in addition to self protection jamming pod. 2 - EW Aircraft; which carry supporting jamming pods to deal with early warning radar from out of missile ranges. EWIIS uses the following list to differentiate among platforms. List of Platform parameters : Range Armament Radar type Max. weight

Endurance Speed EW equipment Base

ECM pod Ceiling

* Jamming Pods. - Self protection pods. - Supporting jamming pods. EWIIS uses the following list to differentiate among jamming pods. List of Jamming pods parameters : Platform Azimuth antenna coverage Victim radar Losses

Power Elevation antenna coverage Available techniques Internal / external

Frequency range Gain transmitted

To introduce the system in a simple and clear way, we may look at the system from the data movement point of view[10]. Data moves as shown in Figure 3 from users (raw mission data) and from library (radar, platforms, jamming pods, terrain heights, maps and restricted areas data) through interfaces module to calculation module. Results will be verified

-7-

by the rules which were fed to the knowledge base system. Then a report will be printed including recommendations for solving the possible problems. Figure 4 shows the main two components of the system : data component and manipulation and control component. USERS

Interfaces Module Radar Data Platform data Pods data Terrain Heights Maps

Library

Raw mission data (Radar locations, Cross country path, heights and Target Restricted areas) Calculation Module

Input Verifier

Knowledge Base System

Results

Domain Knowledge DK

KBS Output Verifier

Selector

. Position

Identification

Results Analyzer

Inference Knowledge (IK)

Data Consistency

Best Alternatives

Optimum Locations

Figure 3 Data Flow and Interaction

-8-

Reports

System Components

Manipulation & control component

Data Component

Radar Data

Platforms & Pods Data

Mission & Maps Data Intelligence Component

Interfaces module

Mission planning area

Traditional Component

Calculation & Conversion module

Restricted Areas

Jamming & techniques area

Figure 4 Main System Components

5.1

Data Component This component includes radar, platforms, jamming pods, mission and maps data which were stored in the library and updated frequently. These data were discussed in section 5 and some examples of parameters were mentioned.

-9-

5.2

Manipulation & Control Component This component includes mainly different types of modules to provide an environment

for mission data filling in addition to a set of aiding tools to support users with all utilities which cover their requirements. This component contains two main modules: traditional and intelligent modules. 5.2.1 Traditional module The traditional module contains all interfaces module in addition to calculation module. Interfaces module This module will represent the main menus seen by the user and they are the connection between the user and the library, and the other modules. Mission plan generator ( calculation and conversion module ) This module is used to calculate different required calculations such as Radar ranges and jamming effects. Figure 5 shows the algorithm used for Radar range calculation and Figure 6 shows the algorithm used to calculate the effects of jamming pods on radar [3, 4, 17, 21]. Initialization (default values, variables zeroising) Get radar frequency (Fr)

: from radar library

Compute wave length (λ)

: λ = light speed / Fr

Get gain received (Gr)

: from radar library

Compute area equivalent(Ae)

: Ae = (2*λ)/ (4* π)

Get power transmitted (Pt)

: from radar library

Get gain transmitted (Gt)

: from radar library

Get radar cross section (σ)

: from radar library

Get radar sensitivity (s Min)

: from radar library

Compute radar range value = ((Pt * Gt * σ * Ae) / ((4 π)**3 * s Min))**0.25 Figure 5 The Algorithm for Radar Range Calculation

- 10 -

Initialization (default values, variables zeroising) Get radar power transmitted (Pt)

: from radar library

Get radar gain transmitted (Gt)

: from radar library

Get radar cross section (σ)

: from radar library

Get radar band width

(Bwr)

: from radar library

Get power of jamming pod (Pj)

: from pods library

Get gain of jamming pod (Gj)

: from pods library

Get jamming pod band width (Bwj)

: from pods library

Compute radar burn through range value = ((Pt * Gt * σ * Bwj) / (Pj * Gj * Bwr* 4 π ))**0.5 Figure 6 The Algorithm for Jamming Calculation

5.2.2 Intelligent module ( Knowledge Base Component ) According to the common KADS methodology [2, 10,12,16,18], a knowledge base system is a collection of different component types(domain, inference and task knowledge), each of which has its own nature and role. Since our proposed tool is designed to be used in a specific application domain which is the Electronic Warfare field, the knowledge base component would contain the knowledge related to this application area. Our knowledge base component plays an important role in three areas : mission planning, jamming techniques area and restricted areas avoidance.

In these areas the knowledge base component plays three roles . First role is to check and fix any mission plan parameters such that the mission plan becomes verified and validated to form a safe plan at the end. The second role of the knowledge component is to monitor and verify the jamming activity. The third role is to monitor the selected set of way points such that they do not pass across some restricted areas. So, a part of this knowledge base contains knowledge about these restricted regions and how to avoid them. Example of rule types used in this part are given in Figure 7 [3, 4, 7, 17, 21].

- 11 -

1.

If Fighter is close to built-in restricted areas by 15 Km then mission will not be accepted.(Ex.for restricted areas rules).

2.

If the remaining fuel after calculating the required fuel for the mission is more than 10% from the total air craft fuel capacity then the mission is successful else mark the mission as not safe.(Ex.for mission planning area rules).

3.

If radar type which protects the target equal fire control type or Acquisition type then deal with self protection jammer else deal with support jammer.(Ex. for jamming area rules).

4.

If the platform carries the required jamming pod then accept the mission else reject.(Ex.for jamming area rules).

5.

If the ground terrain height during the cross country is higher than flight height then mark the flight as not safe and suggest suitable actions.(Ex.for mission planning area rules).

Figure 7 Example of Rule Types The first rule, As shown in Figure 7, means that the fighter air craft should fly away by 15 kilo meters from the built-in restricted areas. Indeed, the information required to activate this type of rules, is obtained by executing another type of rules ( chained ), which monitor and calculate dynamically the position of the plane from the center of any built-in restricted area. Also this type of rules activates its result which will be passed to another set of rules that concern the report generator to explain the reasons behind the acceptance / rejection of the mission plan. As indicated above we referred to the rules as types, not as occurrences, for instance there is a number of instances for the built-in restricted area (18 built-in restricted areas) and about 30 occurrences for the user-defined restricted areas). The second rule means that after calculating the fuel used during the trip, 10% from the total quantity (capacity) should remain for safety to guarantee the safe return to the base. This type of rules is used to predict the safety factor of the mission. Calculating the fuel consumption for completing the mission safely is based on a set of flight parameters (height, velocity, weight). This rule type is highly related to another set of rules which generate reports about the actions to be taken when violation occurs. The third rule means that the self protection jamming pod will deal only with fire control radar and acquisition radar but support jamming pod will deal with early warning radar. The objective of this type of rules is to specify the jammer type based on radar type and target location. Again this type of rules has several instances according to the number of radar around the victim target (usually up to 32 radar). - 12 -

The fourth rule means that the fighter air craft should carry the suitable jamming pod. This type of rule plays a role of hard constraint. It measures the mission plan compatibility between platform ( air craft type ) and jamming pod. This rule occurs several times in the knowledge base based on the number of available platforms and jamming pods types. The fifth rule means that the fighter air craft altitude should be higher than the terrain to guarantee safety. The goal of this rule is to specify the terrain heights through the flight path ( cross country ) and the plane height, The system reports suitable recommendations in case of risks due to unsafe heights. This type of rules is related to cross country, height of flight and ground features heights during the flight path. In fact all these mentioned type of rules are distributed among the four inferences knowledge; verifier, selector, position identifier, and result analyzer, which appear in figure 3 and represented using a table structure in which the columns of this table play the role of rule premises (conditions) and conclusions (actions). In such representation a tuple of this table represents a single rule in which its premises are all “ended”. It is worth noticing that rules are running in a data driven (forward chaining) manner since they receive data and proceed toward their actions.

6.

Case Study

The objective of this case study is to verify the normal operation of EWIIS and to be sure that it accepts the inputs data ( map, radars, mission plan ), accepts map calibration, calculates radars ranges and jamming effects in accurate way and generate and saves outputs in normal and safety way that achieves storage optimization. Figure 8 shows main user interface in EWIIS. 6.1

Inputs and procedures of the EWIIS :

The steps of the mission are the following : 12-

3-

456-

Insert available map (Figure 9). Calibrate1 the map (Figure 10) by choosing two different points and inserting the correct locations of the two points then be sure that the correct location of the cross point location is displayed in the cursor location window (Figure 11) 31-46-7-N & 32-14-8-E. In the position indicators on the map, N means north (Y axis) and E means east (X axis). Locate the target pointed to by the letter T which is protected by acquisition radar with range of 91.38 kilometers ... This radar should discover any aircraft that approaches T (Figure 12) . Draw the mission plan to attack T starting from waypoint # 1 to waypoint # 2 to T to waypoint # 3 ending with waypoint # 4 (Figure 13). Use the bomber air craft as platform and the self-protection jamming pod. Save the mission in the two ways standalone way and layering way ( refer to section 4.1).

1

Map calibration is used to allow location adjustment of points on the map as well as the interactive manipulation of the map on the screen.

- 13 -

6.2

Results

1-

The self protection jamming pod successfully activated against the victim acquisition radar.

2-

The radar range will be reduced from 91.38 Km to 22.84 Km then the bomber will not be detected during its mission to the target. (Figure 14).

3-

The remaining fuel is sufficient for safety return of the plane.

4-

Successful avoidance of restricted areas during the mission.

5-

Saving the mission data in layering method will clearly reduce the storage size. Normally we have repeated missions for different situations and we need to save the data about the mission and this need huge storage size, so we adopted a layered technique to optimize the storage space (specially for the maps). We keep one copy of the basic map and generate files for the differences between the issues of the missions. Differences are about target, radar, mission plan, FEBA, heights, user-defined restricted areas….etc.

6.2

Functions concerning map usage

1-

Authorization is found to provide security for the package and differentiate among the access rights of the users.

2-

Front Edge of Battle (FEBA) is plotted automatically as a red line by the system due to some stored constraints.

3-

There are many types of jamming pods for self protection and support jamming, then user has to choose the suitable pod for the mission.

4-

Trajectory of the plane performing the mission displayed in real-time or as simulated.

5-

Cursor location and ground heights at cursor position appears in the left console (cursor location window and height window).

6-

Distance of aircraft from FEBA appears in the left console (distance from FEBA window).

7-

Height of flight during the mission appears in the left console (height of flight window).

8-

Pointing to the center of the radar by mouse shows name, range, type, and location of the radar.

9-

Pointing to any way points by mouse shows way point name, location and height.

10-

Right click on any way point allows the user to update on line (among the rights given to the mission planner).

11-

Appropriate report are generated according to the case.

12-

The system provides the mission administrator with the function of determining the location of the plane at any point or time during the mission.

- 14 -

2 1

4 3

6 5

8 7

10 9

12 11

14 13

16 15

18 17

20 19

Main Menu Tool Bar

Task Bars

Fire Control Radar 1

Map Data Windows

Left console

FEBA

2

Acquisition Radar

3 4

Restricted areas

Main Menu 1 – file (new, open, save, save as and exit). 2 – library (platform, radar, pods, restricted areas and edit automatic options). 3 – pre-mission aids (standard conversions, fuel consumption, distance and direction,,,,calculator) 4 – users (edit user, log off users, log on users, minimize all, cascade windows and tile H & V). 5 – help ( contents and tip of the day).

Left Console

Tool Bar

Task Bars 1 – Map (New map, map calibration, load map , save map and hide map). 2 – Radar (Radar setting, open list and save list). 3 – Mission (way points setting, support jammer, FEBA, start mission). 4 – Restricted areas (built-in and user input).

Map Data Windows 1 – Cursor location. 2 – Cursor position height. 3 – Distance between plane and FEBA. 4 – Height of flight.

1 – New mission. 2 – Open mission. 3 – Save mission. 4 – Air craft simulated speed. 5 – Play/pause fighter. 6 - Play/pause support jammer. 7 - Manual jamming for support j. 8 – Early warning radar. 9 – Acquisition radar. 10- Fire control radar. 11- open activity. 12- Save activity. 13- Reset the mission start time. 14- Get real status now. 15- Get real status every specific time. 16- Get real status after specific time. 17- Cross country report. 18- EW report. 19- Restricted areas report. 20- EW diagram.

Figure 8 Main User Interface - 15 -

PALESTINE

Figure 9 Raw Map, No Data (latitude and longitude) for (

) Sign in Cursor Location Window

PALESTINE

Figure 10 Calibration Process - 16 -

PALESTINE

Figure 11 Map After Calibration, Correct Data (latitude and longitude) for (

) Sign in Cursor Location Window

Figure 12 Acquisition Radar with Range (red circle) of 91.38 km - 17 -

2

1

4 3

Figure 13 Mission Plan Path (black line) Showing Waypoints in Sequence 1,2,T,3 and 4

2

1

4 3

120.00 m

Figure 14 Reduction of The Acquisition Radar Range from 91.38 km to 22.84 km due to Jamming Effect - 18 -

7.

Conclusion and Future Work

This paper has addressed the problem of dealing with the processing of the huge data of electronic warfare communications, radar, airplanes missions .. etc to achieve the best performance with our system in spite of the existence of hostile actions. An intelligent information system has been designed and built to store, retrieve, process, correct, analysis and report information about attacking scenarios that could be placed by users of the system. The system is robust and efficient. It is capable of analyzing all kinds of modern threats and capable of working in a multi – user environment. The proposed system is called Electronic Warfare Intelligent Information System (EWIIS) . EWIIS deals with a graphical user interface in a convenient way. A case study is used to demonstrate the capability of EWIIS and to verify its normal operation. The case study has achieved accurate and promising results . EWIIS currently supports missions that work with self protection pods where it selects the best platform for the mission. It selects best pods and mission path and the suitable altitude. To summarize, the manual system of mission planning and execution suffers from slow processing and difficulties of choosing the best between the alternatives of the mission plans and also the possible errors in calculations. On the other hand the proposed system overcomes these shortcomings and makes use of the visual presentation and manipulation of the required maps. Also EWIIS provides the possibilities of saving and retrieving the different experienced situations to improve the productivity and the efficiency of the EW officers. We suggest as future work to support these functionalities with Early Warning radar. The reporting component with reasonable recommendations for ideal missions is intended as a future work for our research. References [1]

D. Adamy, Introduction to Electronic warfare modeling and simulation, Artech house, Norwood MA, 2003.

[2]

C. Basu, "Technical Paper Recommendation: A Study in Combining Multiple Information Sources", Volume 14, pages 231-252, Journal of Artificial Intelligence Research, 2001.

[3]

L. Brunt, Applied ECM ( Electronic Counter Measure ) Volume 1, EW Engineering, Inc,1985.

[4]

L. Brunt, Applied ECM ( Electronic Counter Measure ) Volume 2, EW Engineering, Inc,1985.

[5]

L. Brunt,The Glossary of Electronic Warfare, EW Engineering , Inc, 1984.

[6]

P. Clarke , “Integration of tactical EW elements”, proceedings of technical tracks of 39th annual AOC international symposium and convention, October 20002.

- 19 -

[7]

R. Fitts , The Strategy of Electromagnetic Conflict, Peninsula Publishing,1980.

[8]

B. Gunston and M. Spick, Modern Air Combat, Crescent Books , New York,1983.

[9]

S. Kenneth, “When weapons cheat”, Journal of Electronic Defense, July 2000.

[10]

M. Khozium, Computer-based System for Unmanned Air Vehicle Mission Planning, M.Sc. Thesis, I.S.S.R.,Cairo university, 2001.

[11]

D. Leake, “Artificial Intelligence”, http://www.cs.indiana.edu/~leake/papers/p-0107/p-01-07.html, 2002, last visit April 2003.

[12]

M. Negnevitsky , Artificial Intelligence, Addison-Wesley, 2002.

[13]

J. Pike, “Anti-Missile System Won't Work, USA Today”, 27 January 1999, http://www.fas.org/interstore/anti-missile system won't work.htm, last visit October 2001.

[14]

J. Pitts, “Electronic warfare in the information age congressman”, Journal of Electronic Defense, July 2000.

[15]

M.Ryan, “The roles of artificial intelligence in battlefield command systems”, journal of battlefield technology , web http://www.argospress.com/jbt, last visit in March 2004.

[16]

E. Sciascio, "Structured Knowledge Representation for Image Retrieval", Volume 16, pages 209-257, Journal of Artificial Intelligence Research, 2002.

[17]

M. Skolnik, Introduction To Radar Systems, Library of Congress Cataloging in Publication Data, 1986.

[18]

U. Straccia, "Reasoning within fuzzy description logics", Volume 14, pages 137-166, Journal of Artificial Intelligence Research, 2001.

[19]

W. Taylor, “understanding the Infrared threat”, Journal of Electronic Defense, February, 1999.

[20]

B. Travis, “A Research Agent Architecture for Real Time Data Collection and Analysis”,16 March, 2002, http://www.cs.indiana.edu/~leake/papers/p-0105_dir.html/agents01.html, 2002, last visit October 2003.

[21]

Air Force Manual, USA, NAV AIR, Air Navigation, March 1983.

[22]

J. Whitten and L.Bently, "Systems Analysis and Design Methods", Irwin/McGrawHill, 1998.

[23]

T. Wilson, “Threats to United Space Capabilities”, http://www.fas.org/interstore/threats to united states space capabilities. htm, 2001, last visit October 2001.

[24]

S. Zaloga,” The evolving SAM threat : Kosovo and beyond”, Journal of Electronic Defense, May, 2000.

[25]

S. Zaloga, “Air-Defense Missile : Recent trends in the threat”, Journal of Electronic Defense, November, 1998.

- 20 -

A Prototype for An Intelligent Information System for ...

for Jamming and Anti-jamming. Applications of Electromagnetic Spectrum. .... As normal information system development life cycle [6,9,22] we need to analyze.

2MB Sizes 1 Downloads 261 Views

Recommend Documents

A Prototype for An Intelligent Information System for ...
Data. Acquisition. & Manipulation. Threats Data. Platforms Technical Data. Threats Library. Pods Library. Intelligent. Information System. (IIS). Mission Plan. Data. Reporting &. Documentation. User Adaptive. Refinement. Available Decisions. Plan Doc

An Instructor-Oriented Prototype System for Virtual ...
Proceedings of the Sixth International Conference on Advanced Learning Technologies (ICALT'06). 0-7695-2632-2/06 ... course & instructor and the data from the client in real time. So the ..... videos are displaying on big screen, the server will.

An initial prototype system for Chinese spoken ...
network will include all the information activities for human life, from real-time information to knowledge archive, from working environment to private services,.

Designing an intelligent tutoring system for database ...
Abstract. Database (DB) modelling is the cornerstone of an efficient database. Students require extensive practice to excel in modelling databases due to the ...

Thermo-Tutor: An Intelligent Tutoring System for ... - Semantic Scholar
The Intelligent Computer Tutoring Group (ICTG)1 has developed a ... the years in various design tasks such as SQL queries [9], database ..... Chemical and Process Engineering degree at the University of ..... J. Learning Sciences, vol. 4, no. 2,.

An intelligent real-time vision system for surface defect detection ...
challenging in real-time in a hot rolling process: (1) The ... sampling requires a data acquisition rate of 80 MB per .... Unlike traditional classifiers such as artificial ...

An Agent-based Intelligent Tutoring System for Nurse
developed by the USC/Information Sciences Institute's Center for Advanced Research in ..... Each proactive agent observes the user interface with respect to one single aspect. ... the agent will call for the time values of those subtask numbers.

Thermo-Tutor: An Intelligent Tutoring System for ... - Semantic Scholar
hard to master for novices. In addition to ... in the best funded institutions, the student-to-teacher ratio is ... best. Low achieving students find the work difficult and never ... complement to traditional courses: it assumes that the students hav

Thermo-Tutor: An Intelligent Tutoring System for ... - Semantic Scholar
developed several ITSs for procedural skills, such as data normalization within relational ..... transmission and temporary storage of data. ASPIRE uses the ..... “Intelligent Tutoring Goes to School in the Big City”. Int. J. Artificial. Intellig

An Intelligent Energy Management System for PHEVs Considering ...
An Intelligent Energy Management System for PHEVs Considering Demand Response.pdf. An Intelligent Energy Management System for PHEVs Considering ...

An Intelligent Search Agent System for Semantic ...
networks and we describe a prototype system based on the. Intelligent Agent ... H.3.3 [Information Storage and Retrieval]: Informa- tion Search Retrieval; H.4 ... Keywords. Information Retrieval, Semantic Network, Web Agents, On- tology. 1.

an intelligent vision system on a mobile manipulator
AN INTELLIGENT VISION SYSTEM ON A. MOBILE ... sweeper the most powerful intelligent mobile robot in doing the expected tasks, with ..... TABLE 3. Detected Objects Information. Object. Type. X of Cent. Of. Object. Y of Cent. Of Object. Number of. Pixe

An Intelligent Interface Agent for an Airline Company ...
Interface Agent to support the use of a web portal in an airline company. The interface agent ... TAP Portugal - Portal DOV [1] is currently a hub of information and services to all crewmembers. ... TAP installations or by telephone. For instance ...

Intelligent Mobile Agent for Intrusion Detection System - CiteSeerX
a finished intelligent tool prototype for intrusion detection. Intrusion ..... They receive alerts from correlator agents, analyse ... Monitoring and Surveillance.

Method and system for building and using intelligent vector objects
Nov 6, 2001 - maintenance, repair and operations (MRO) Work Within an equipment-related ?eld ..... 8. class %ClassList; #IMPLIED. 9. style %StyleSheet; # ..... commercially available auto-tracing programs knoWn to those skilled in the art, ...

Intelligent Mobile Agent for Intrusion Detection System - CiteSeerX
Therefore, JAVA language will be chosen for its .... the same time, a language and a knowledge base, also called .... php?action view=submenu&option=tree&id.

Executive Information System For Monitoring Building Construction ...
EXECUTIVE INFORMATION SYSTEM FOR MONITORING BUILDING ... For Monitoring Building Construction Work Progress : Wan Zahran Zakaria - ttp.pdf.

A Prototype Structured but Low-viscosity Editor for Novice ... - eWiC
Many beginners learn with Java, a traditional text-based language. ... Programming, Greenfoot, Java, Scratch, Alice, CogTool, viscosity, cognitive dimensions. ..... 6. DISCUSSION. 6.1 Comparison – Greenfoot. Greenfoot programs are written in Java s

a description of prototype models for content-based ...
3. (. . .) The use of coherently developed content sources allows students to ... paradigm has proved to be a valid approach for language teaching at all stages of .... around the selected topics in a meaningful, coherent and interwoven manner.

bakhra gyan – a management information system for goat ... - GitHub
the listed here have been used in this work. ... Goat rearing is a local business section being practiced by the large volume ... web application where admin can collect the information about goat farming ..... Since this is web based application use

A Content-Based Information Retrieval System for ... - Springer Link
This paper deals with the elaboration of an interactive software which ... Springer Science + Business Media B.V. 2008 .... Trend boards offer a good representation of the references used ..... function could be fulfilled by mobile devices.

probabilistic plan recognition for intelligent information ...
Towards proactive software assistant agents ... a software assistant agent that can proactively manage information on behalf of cog- ..... reduce email overload.

A Prototype Structured but Low-viscosity Editor for ...
not possible to enter an invalid statement). Parameters can be added or changed through blocks' context menus, but the structure of the statement itself cannot ...