A Real-Time Community-of-Interest (COI) Framework for Command-and- Control Applications

Transcription

1 A Real-Time Community-of-Interest (COI) Framework for Command-and- Control Applications Ray Paul Department of Defense Washington, DC 5/22/2004 1

2 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/2004 2

3 NCES Vision Users Support real-time & near-real-time warrior needs needs and and business users users Dynamically Created COIs C2 Intel Weapon Systems Logistics Sensors Personnel Finance Etc. Communityof-Interest (COI) Capabilities Levels of Services above core level Comms Backbone ESM Messaging Mediation Security/IA Discovery Collaboration Storage App User Asst Core Enterprise Services (CES) 5/22/2004 3

4 Requirements Modern warfighting is agile These services need to change at runtime in real time when new services are created and obsolete services become deactivated. A COI is a place where interested parties can get related information in real time each party can contribute to the discussion and share information A DoD commander can receive/download the needed information, participate in conferencing and decision-making, make strategic, operational, and tactical plans, issue commands, and monitor progress in real time Creation of a variety of COIs in real time 5/22/2004 4

5 Requirements (cont d) Service-Oriented Architecture (SOA): The COI will be implemented using SOA and an application running on SOA is inherently more survivable Situation awareness and analysis: Each COI has its own situation assessment algorithms to determine the current situation. The COI also allows participants to contribute and present new situation assessment algorithms to meet the changing environment. 5/22/2004 5

6 Requirements (cont d) Real-time messaging and alerts: Commanders participating in COIs can send/receive time-critical messages, and Each COI can send and receive real-time alerts to and from other COIs. Fault-tolerant computing: Be survivable in case of enemy s attacks Be able to recover occasional failures by dynamic reconfiguration 5/22/2004 6

7 Requirements (cont d) Database support: Each COI has its own database, and can receive, process, filter, and retrieve information from its database in real time, and It can send its data to other concerned COIs. Knowledge engineering and processing: A processed knowledge is knowledge that can be used, interpreted, and applied. 5/22/2004 7

8 Requirements (cont d) Data mining: The abnormal data, trends, statistical characteristics, and relationships among data can be automatically classified and detected Network computing: Each COI will run on a network-centric enterprise system for interoperability, survivability, and knowledge sharing Multimedia: The data (video, photos, voices, map, pictures, and texts) need to be transmitted reliably and securely over a DoD enterprise network. 5/22/2004 8

9 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/2004 9

10 COI Architecture Template Each COI consists of core services that represent the main capabilities and common services that are shared among most COIs SOA based design and implementation 5/22/

11 COI Architecture Template (cont d) 5/22/

12 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/

13 Mission Services Layer Contains mission-specific services for specific C2 applications Logistical services Personal services Weapon systems Services in this layer provide individualized COI services for warfighting They exchange data, information, decisions, knowledge and alerts with each other to achieve the overall mission. 5/22/

14 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/

15 COI Service Layer The COI Service Layer contains common services needed to implement specific C2 COIs that may be created at runtime in real time Membership management, C2 policy management, Dynamic reconfiguration, Situation awareness management, Service mining Data classification 5/22/

16 COI Service Layer (cont d) Membership Management Service: Provides mechanisms for users to register/unregister with specific COIs, Manages connection and collaboration among individual COIs. A COI may register with another COI to get realtime data and alerts. A COI may be a supervisor of another COI, and a steady stream of data will flow from one COI to another COI. 5/22/

17 COI Membership Services (cont d) Supervisor-to-subordinate relationship: The supervisor COI can send command to and impose control policy on the subordinate COI, which needs to report the results back. Peer-to-Peer: Each COI has unique characteristics and provides specific services to the other. Competitor-to-competitor: Each COI has similar characteristics and provides similar capabilities regarding the requests. Winner-to-Winner: Although each COI may achieve its goal by itself, the cooperation with others provides better solutions. The goals are independent, and without resource competition. 5/22/

18 COI Membership Services (cont d) 5/22/

19 COI Action Initiation COI services may be initiated in the following ways: Mission-driven activities: This may happen when a commander issues a new C2 policy in a COI, and such change of the C2 policy will immediately trigger a series of actions in the COI framework. Situation-driven activities: These kinds of activities start with a detection of a concerned situation such as abnormal/suspicious/attack behaviors based on data received from data collection services or sensors. Collaboration-driven activities: These kinds of activities will be generated based on collaboration among commanders and decision makers participating in various COIs. 5/22/

20 COI Coordinator Services Provides COI coordination including: Mediation within a COI, collaboration among COIs, and overall optimization in terms of benefit/cost analysis under C2 policies and constraints. 5/22/

21 Mediator Services within a COI The COI coordinator needs to interact with other services, such as PSS, SAS and DRS, within the COI. The mediation can follow the blackboard model or priority model. In the blackboard, participating services will interact with each other by sharing a common working space The priority model assigns priorities to each service, and each participating service will get its turn for execution according to the priorities 5/22/

22 Collaboration Services Each COI focuses on a specific area of applications or data Each COI has its own unique data and knowledge processing rules, deductive capabilities, filtering, and classification rules for its specific data. However, these COI also can cooperate with each other by providing real-time alerts and data to fellow COIs in the network 5/22/

23 COI Service Layer (cont d) Policy Specification/Evaluation Service (PSS): Supports policy-based computing where C2 policies are specified and used in various computing Specified using a Policy Specification and Execution Language (PSEL), Policies stated in this language can be executed in real time at runtime to determine system properties such as security and reliability. PSS allows decision makers and commanders to issue appropriate commands without specifying the details of the command. C2 policies in this framework can be changed at runtime by participating COIs. 5/22/

24 COI Service Layer (cont d) Dynamic Reconfiguration Service (DRS): Supports dynamic reconfiguration in a SOA in real time at runtime. Existing SOA products do not provide services can continuously monitor each participating service, initiate a reconfiguration process, and implement the process using the stated policies. With DRS individual services can be added, removed, and replaced at runtime without interrupting the system operations. 5/22/

25 COI Service Layer (cont d) Situation Awareness Service (SAS): Collects data from sensors and other participating services, analyze the data received, and issue alerts to concerned COIs and participants. An SAS consists of a SA decision manager (SADM), and a set of distributed SA action managers (SAAM): SADM specifies reconfigurable policy/rules for situation analysis and communicates with other services Each of SAAMs controls a group of sensors or any data collectors by gathering and fusing data input 5/22/

26 Situation-Awareness Service (cont d) Policy/Commander Data Mining COI Coordinator High-level command/control COI-related request Feedback SA Decision Manager Use Scheduler Simulation Specify Verification Feedback Policy /rules Reconfigurator Security Services Issue command Issue command Issue command Risk Analysis Use SA Action Manager 1 SA Action Manager n Data SA Action Manager k Pull data Send data Request Request Request Request Send data Send data Send data Store Data Data Global Information Grid (GIG) Data Data Sensors/Monitors 1 Sensors/Monitors i Sensors/Monitors 2 Sensors/Monitors m 5/22/

27 COI Service Layer (cont d) Service Mining Service: During reconfiguration, new services must be identified to replace the failed services. This can be done by mining the existing services to find an effective mapping between a request and the existing services. 5/22/

28 Service Mining Service mining is different from the traditional data mining in several ways: It deals with runtime services rather than static data because each service needs not only static but also dynamic information; The selected services may need to be verified at runtime; If the failed service has some state information, it is necessary for the replacement service to start from this particular state. 5/22/

29 COI Service Layer (cont d) Data Classification Service: Uses the data mining approach to classify the data collected into appropriate categories for decision-making 5/22/

30 Data mining Data mining (knowledge discovery in databases) non-trivial process of identifying valid, implicit, previously unknown, and potentially useful information and ultimately understandable patterns in data. Data mining has the following steps: Raw data, transformed data, pre-processed data, data mining, postprocessed data, knowledge. Different types of raw data can be distributed data, textual data,web data, images, audio/video etc. 5/22/

31 Data mining contd... Data mining fills the huge gap between the stored data and the knowledge that can be construed from the data. Data mining is increasingly used in applications related to business, intelligence medical diagnosis, security scientific discovery, telecommunications. Commercially available data mining tools: Intelligent Miner, SurfAid Analysis by IBM Corp, Darwin by Oracle Corp., MineSet by Silicon Graphic Inc., Visualizer Workstation by Computer Science Innovations, Inc. 5/22/

32 Data preprocessing Data preprocessing can be classified into Data cleaning Data reduction Data cleaning deals with the following Noisy data Missing data Inconsistent data Data reduction can be classified into Instance selection Dimension reduction 5/22/

33 Data classification Data classification algorithms can be classified as supervised algorithms unsupervised algorithms. Supervised algorithms use training data which has correct answers and create a model by running the algorithm on the training data. They identify a class label for the incoming new data. Some of the supervised algorithms are Bayesian, Neural network, decision tree algorithms, genetic algorithms, fuzzy set, K-Nearest Neighbor. Unsupervised algorithms do not use training data and classes may not be known in advance. Examples are association rules and clustering. 5/22/

34 Data Classification Data can be classified according to the attributes, such as frequency of sending/receiving (sparse, often, intensive), level (Low, Guarded, Elevated, High, Severe), source (Top, Peer, Subordinate), and type (Warning, Alerting, Mandatory). 5/22/

35 Data Classification (cont d) The first step of classification is to build the model to tune the parameters in the classification rules using training data with the classification algorithms. In the second step, the accuracy of the rule-based model needs to be estimated. First Step Training Data Classification Algorithm Classification Rules Second Step Test Data New Data 5/22/

36 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/

37 Support Service Layer Provides basic services needed to support common COI services. Many of these services provide similar functionalities as those of core enterprise services in NCES. Many of these basic services need to have real-time behavior and must be involved in continuous monitoring and data collection. 5/22/

38 Support Service Layer (cont d) Discovery Service Messaging Service Security Service Scenario Specification Service Test and Evaluation Service Simulation Service Data Acquisition Service Storage Service 5/22/

39 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/

40 Prototype of COI Extended SOA for COI model: each service will be specified using the Interface, Scenario, and Constraint (ISC) Interface Specification Input/Output parameters Communication protocols Interfaces with other sub-systems Scenarios Specification Specify the service scenarios Specify interactions with other sub-systems Constraints Specification Specify the properties of the services must have such as Reliability, availability, security, timing, concurrency, performance, sequence, safety These constraints must be addressed at runtime to assure dependable computing 5/22/

41 COI Prototype Design Presentation Layer Data Visualization/ Analysis Report Generation Query Support Analysis Layer Predictions Messaging/ Action Situation Awareness Data Analysis Decision Making Pattern Detection Data Organization Layer Data Acquition Data Storage Data Filtering 5/22/

42 Agenda Requirements of COIs COI architecture template Mission Service Layer COI Service Layer Membership Management Services COI Coordinator Services Dynamic Reconfiguration Services Situation awareness services Service mining services Data classification services Support Service Layer Prototype of COI Conclusion and future research 5/22/

43 Conclusion and Future Research A SOA based real-time COI framework for C2 application, which consists of three layers including mission layer, COI service layer and support layer, is described. This paper focuses on COI service layer. A prototype is developed to demonstrate the main techniques Implement the COI architecture template for NCES and GES 5/22/