nato unclassified unis technical exchange meeting december, 1-3, 2009 unis technical exchange...

29
NATO UNCLASSIFIED UNIS Technical Exchange Meeting UNIS Technical Exchange Meeting December, 1-3, 2009 December, 1-3, 2009 US-NATO Air C2 Interoperability The Current & The Future Mutlu Uysal C2 Systems Group NATO C3 Agency

Upload: dina-lewis

Post on 11-Jan-2016

277 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

NATO UNCLASSIFIED

UNIS Technical Exchange MeetingUNIS Technical Exchange MeetingDecember, 1-3, 2009December, 1-3, 2009

US-NATO Air C2 Interoperability The Current & The Future

Mutlu UysalC2 Systems GroupNATO C3 Agency

UNIS Technical Exchange MeetingUNIS Technical Exchange MeetingDecember, 1-3, 2009December, 1-3, 2009

US-NATO Air C2 Interoperability The Current & The Future

Mutlu UysalC2 Systems GroupNATO C3 Agency

Page 2: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 2

OVERVIEWOVERVIEW

Introduction Interoperability Challenge NATO Network Enabled Capability Concept NATO Integrated Command & Control (ICC) System

Interface Means for the interoperability Formatted Message-based (ADatP3, USMTF) Chat capabilities (JCHAT-Traverse) Near real time data exchange (through NIRIS) NEC mechanisms such as web services etc.

Lessons Learned & Challenges

Summary & Conclusion

Introduction Interoperability Challenge NATO Network Enabled Capability Concept NATO Integrated Command & Control (ICC) System

Interface Means for the interoperability Formatted Message-based (ADatP3, USMTF) Chat capabilities (JCHAT-Traverse) Near real time data exchange (through NIRIS) NEC mechanisms such as web services etc.

Lessons Learned & Challenges

Summary & Conclusion

Page 3: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED

Interoperability ChallengeInteroperability Challenge

Information is available from many sources and is needed by many different systems/users. It must be:Securely SharedCommonly Understood

…challenge is how?

?

Page 4: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 4

Network Enabled Capability (NEC)The Theory

Network Enabled Capability (NEC)The Theory

The right information at right time at right place to right users.

Improve operational effectiveness through the federation of individual capabilities.

Seamless linking of sensors, weapon systems, C2 systems and decision makers in a collaborative environment for planning, assessment and execution.

The right information at right time at right place to right users.

Improve operational effectiveness through the federation of individual capabilities.

Seamless linking of sensors, weapon systems, C2 systems and decision makers in a collaborative environment for planning, assessment and execution.

Page 5: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 5

Service Oriented Architecture (SOA) and Web Services

The RealityService Oriented Architecture (SOA) and Web Services

The Reality

NETWORKNETWORK

Service

Producer 1 Service

Producer 2 Service

Producer n SERVICE SERVICE

PROVIDERSPROVIDERS

Service Consumers1

Service Consumers 2

Service Consumers n

SERVICE SERVICE CONSUMERSCONSUMERS

Service Service RequestRequest

Service Service ResponseResponse

XMLXMLMachine to Machine interfaceMachine to Machine interface

Web Web Services:Services:

HTMLHTMLWeb Web Browsing:Browsing: Machine to Human interfaceMachine to Human interface

Service Registry

PublishPublish

FindFind

Page 6: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 6

Applying theory to an Existing NATO Integrated Command & Control (ICC)

System The Example

Applying theory to an Existing NATO Integrated Command & Control (ICC)

System The Example Operational NATO system

Wide spread usage at NATO ~400 sites in 23 countries, including ISAF theater.

Supports planning, tasking, and execution process for NATO air operations

Integrated tool across all levels of command

Networked

Interoperable with many systems

Operational NATO system

Wide spread usage at NATO ~400 sites in 23 countries, including ISAF theater.

Supports planning, tasking, and execution process for NATO air operations

Integrated tool across all levels of command

Networked

Interoperable with many systems

Page 7: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 7

ICC Architecture for NNEC ExtensionsICC Architecture for NNEC Extensions

ICC Web Application Server

ICC Server (Database,COSI)

OracleOracle CO

SI

++

ICC Client

CORBA

Web Service Clients

XML

Clients consuming ICC NEC Capabilities

Standard ICC ArchitectureStandard ICC Architecture NEC Extension modulesNEC Extension modules

TOMCAT

WISI

WS

DL

ICC WEB U

RL

++

HTML

Clients viewing ICC Web pages

Systems can be enhanced to utilize NEC by adding a service layer to their current architecture in order to increase their interoperability with external systems.

Systems can be enhanced to utilize NEC by adding a service layer to their current architecture in order to increase their interoperability with external systems.

++

Page 8: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 8

ICC Interface SolutionsICC Interface Solutions

Formatted Messages ADatP3, USMTF

• e.g. ATO, ACO, AIRSTAR, SSREP, ASACSTAT, MISREP, etc.

ICC Import/Export (IXI) ICC format (similar to ADatP3)

• mostly limited to SETUP and ORBAT XML format

• bulk format for JTS target data• .max format for MAOP data• .mix format for ICC memory dump

TDL/DL via NIRIS L1, L11, L16, OTH Gold

ICC Standard Interface (ISI) Software Development Kit (C/C++ or CORBA)

ICC Web Services ATO, ACO, Targeting, Common Mission Definition (CMD), etc.

Page 9: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 9

ICC - TBMCS Interface in ISAFICC - TBMCS Interface in ISAF

USMTF 98/2000 ATO

USMTF 98/2000 ACO

TheaterSet-up Data

ICC 2.7

USAFEDeveloped

Conversion Tool

ICC ATO/ACO Loader

(part of ICC 2.7+)

TBMCS 1.1.3

ICCExportFiles

ATO Missions are IMPORTED into ICC DB as an ATO and can be viewed in

SALTO and MTOTE, modified, amended, previewed, etc.

ICC Database ATO / ACO / Resources

ImportTool

ACM Airspaces are IMPORTED into ICC DB as an ACO and can be viewed

in ASMAN, modified, amended, previewed, etc.

NATO AdatP3 ATO and ACO

MTOTESALTOASMAN

USMTF 2000 ACO

ACM Requests

Page 10: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 10

Summary of ICC - TBMCS Interface in ISAF

Summary of ICC - TBMCS Interface in ISAF

Message Message Type Provider Consumer

FROB ICC Export US-TBMCS NATO-ICC

ATO USMTF2000 US-TBMCS NATO-ICC

ACO USMTF2000 US-TBMCS NATO-ICC

ACMREQ USMTF2000 NATO-ICC US-TBMCS

Page 11: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 11

JCHAT- Transverse CollaborationJCHAT- Transverse Collaboration

Potential interoperability capabilities:- Supported XMPP chat standard (Presence, one-to-one chat, group chat ..)-Web based Chat -Cross Domain Multiple Domain (>2) Support-Whiteboard (SVG vice NVG)-Bi-Directional Language Translation

Potential interoperability capabilities:- Supported XMPP chat standard (Presence, one-to-one chat, group chat ..)-Web based Chat -Cross Domain Multiple Domain (>2) Support-Whiteboard (SVG vice NVG)-Bi-Directional Language Translation

Page 12: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 12

GCCS / ICC Interface through NIRIS

GCCS / ICC Interface through NIRIS

ICC can consume OTH-GOLD data sent by GCCS through NIRIS and display it on its map.

ICC can consume OTH-GOLD data sent by GCCS through NIRIS and display it on its map.

GCCSNIRISICCOTH-GOLD

Page 13: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 13

NEC related Experiments1. ICC/TBMCS/ACCS Mission Exchange

NEC related Experiments1. ICC/TBMCS/ACCS Mission Exchange

•Same interface for all systems using common models!

ICC Mission Services

ICC Mission Services

ICC ServerICC Server

NETWORKNETWORK

SERVICE SERVICE PRODUCERSPRODUCERS

SERVICE SERVICE CONSUMERSCONSUMERS

ICC ClientICC Client

TBMCS ServerTBMCS Server

TBMCS Mission Services

TBMCS Mission Services

ACCS ServerACCS Server

ACCS Mission Services

ACCS Mission Services

TBMCS ClientTBMCS Client ACCS ClientACCS Client

Experimented at NATO CWID 07/08 (Lillehammer, Norway). Mission data was exchanged using common models (CMD) and

mechanisms (RSS). Also extended for FROB and ACO exchange, however ICC had limited

support for them.

Experimented at NATO CWID 07/08 (Lillehammer, Norway). Mission data was exchanged using common models (CMD) and

mechanisms (RSS). Also extended for FROB and ACO exchange, however ICC had limited

support for them.

Page 14: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 14

Really Simple Syndication or Rich Site Summary

Format for Syndicating Content, de-facto XML standard for “advertising” data

Format for delivering summaries of regularly changing web contents

Includes a list of items with some meta-data and explicit URL links for retrieving details of each individual item.

What is RSS?What is RSS?

Page 15: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 15

Example RSS feed for ICC missionsExample RSS feed for ICC missions

Meta-data for mission 1

Meta-data for mission 2

This URL link providesdetails of ICC Mission 1 in

CMD XML format.

This URL link providesdetails of ICC Mission 2 in

CMD XML format.

Page 16: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 16

NEC related Experiments 2. ICC/JASMAD ACO Exchange

NEC related Experiments 2. ICC/JASMAD ACO Exchange

ACO Web ServicesACO Web Services

ICC ServerICC Server

NETWORKNETWORK

SERVICE SERVICE PRODUCERSPRODUCERS

SERVICE SERVICE CONSUMERSCONSUMERS

JASMADJASMADJASMAD is a new USAF airspace management and deconfliction application.

ACO Request ACO Data

Experimented at NATO CWID 08 (Lillehammer, Norway). JASMAD successfully consumed ICC ACO web services. ICC web services were providing ACO data using its own schema.

Therefore, transformation was required by JASMAD.

Experimented at NATO CWID 08 (Lillehammer, Norway). JASMAD successfully consumed ICC ACO web services. ICC web services were providing ACO data using its own schema.

Therefore, transformation was required by JASMAD.

Page 17: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 17

JTS ServerJTS Server

ICC Import Tool

ICC Import Tool Step 3: Get the results from JTT target web

Services

JTT Web ServicesJTT Web Services

JTT ServerJTT Server

Step 4: Insert target list to the JTS database

using JTS web services

Step 5: Read imported target list/target using JTS client

JTS Web ServicesJTS Web Services

JTS Client Web-based ICC Import Tool

Step 2: Invoke JTT target web Services

CORBA ServicesCORBA Services

Step 1: Import JTT Targets/Lists using ICC Import Tool

NEC related Experiments 3. NATO JTS/ US JTT Target Exchange

NEC related Experiments 3. NATO JTS/ US JTT Target Exchange

Experimented at JFEX-08 (WPC Germany / Langley US). Successfully demonstrated the capability to exchange

targets between NATO JTS & US JTT using web services. An Import tool was developed by ICC for this purpose.

Experimented at JFEX-08 (WPC Germany / Langley US). Successfully demonstrated the capability to exchange

targets between NATO JTS & US JTT using web services. An Import tool was developed by ICC for this purpose.

Page 18: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 18

Lessons Learned from NNEC ExperimentsLessons Learned from NNEC Experiments

•Service Definition - Web service interface should be well-defined. - Good balance on the granularity of the services. - Refer to common models as much as possible.

•Service Definition - Web service interface should be well-defined. - Good balance on the granularity of the services. - Refer to common models as much as possible.

•Quality of Service-Critical. -Load balance testing activities. -Compression techniques to minimize the bandwidth usage. -Still need to use the native interfaces for internal tasks for performance matters.

•Quality of Service-Critical. -Load balance testing activities. -Compression techniques to minimize the bandwidth usage. -Still need to use the native interfaces for internal tasks for performance matters.

•Service Provisioning - Complexity of the maintainability for the support staff. - Need for a global service registry.-The role of Enterprise service buses (ESB) in future.

•Service Provisioning - Complexity of the maintainability for the support staff. - Need for a global service registry.-The role of Enterprise service buses (ESB) in future.

Page 19: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 19

Quality of service- Mechanisms to ensure that quality of service is at

an acceptable level and it should be continually monitored especially in WAN.

Security- Data should be securely shared among the

providers and consumers.

Requires change in the way the software is traditionally developed.- The focus is reuse rather than re-implement.

Still emerging - All the supporting technology for the SOA is still

emerging.

Challenges of SOAChallenges of SOA

Page 20: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 20

Towards Service Oriented ArchitectureTowards Service Oriented Architecture

PAST FUTURE

Should be moved from an inefficient model - with vertical, stovepipe applications - to an enterprise-wide model that delivers a reusable suite of interoperable services.

Should be moved from an inefficient model - with vertical, stovepipe applications - to an enterprise-wide model that delivers a reusable suite of interoperable services.

Page 21: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009

Future Interoperability with ESB’sFuture Interoperability with ESB’s

NATO UNCLASSIFIED 21

US Interoperability Bus NATO Interoperability Bus

JOCWatchJTS Intel FS

EVE

ICC

CORSOMJADOCS

C2PC CPOF

GCCS Others

• Rather than having a point to point connections between all systems, Rather than having a point to point connections between all systems, the interoperability is achieved through the enterprise service buses.the interoperability is achieved through the enterprise service buses.

Others

TBMCS JTT

Page 22: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 22

Interoperability between NATO & US C2 systems in theater is crucial.

Experimentation in theater is impossible. Need to have experimentation & validation of solutions prior to

fielding. Lab environment for experimentation. Events such as CWID etc. are important for validation and

demonstrations.

NATO attendance to AirOps COI is crucial. NATO is not authorized to attend STRIKE COI. COI models are very important to achieve interoperability.

Some Remarks About NATO-US C2 Systems Interoperability

Some Remarks About NATO-US C2 Systems Interoperability

Page 23: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009

Summary of the presentation Summary of the presentation

•There are different means of interoperability between NATO and US systems such as messaging, chat capabilities, web services etc.

• SOA and web services enable loosely coupled integration between the information providers and consumers. More effort needed to support these technologies for seamless integration.

•Some topics to study on in future are: - COI data models

-the role of ESB’s in the architecture

- security issues in cross domain(WS-Security, WS-Trust)

•Experimentation at lab environments, validation & demonstration at exercises such as CWID is crucial for enhancing the interoperability between NATO & US.

NATO UNCLASSIFIED23

Page 24: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 24

COMMENTS?

QUESTIONS?

COMMENTS?

QUESTIONS?WHEN?

HOW?

Could you...?

That’s not right!

For more information contact: ICC Project NC3A, The Hague, The Netherlands www.nc3a.nato.int email: [email protected] CRONOS: NC3A Support ICC tel +31-70-374 3740 fax +31-70-374 3079

Page 25: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 25

Contacting NC3AContacting NC3A

NC3A Brussels

Visiting address:

Bâtiment ZAvenue du Bourget 140B-1110 BrusselsTelephone +32 (0)2 7074111Fax +32 (0)2 7078770

Postal address:NATO C3 AgencyBoulevard Leopold IIIB-1110 BrusselsBelgium

NC3A The Hague

Visiting address:

Oude Waalsdorperweg 612597 AK The Hague

Telephone +31 (0)70 3743000Fax +31 (0)70 3743239

Postal address:NATO C3 AgencyP.O. Box 1742501 CD The HagueThe Netherlands

Page 26: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 26

BACKUP SLIDESBACKUP SLIDES

Page 27: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 27

NEC related Experiments Joint Common Operational Picture (JCOP)

NEC related Experiments Joint Common Operational Picture (JCOP)

JCOP Light JCOP Light Client (IGEOSIT)Client (IGEOSIT)

ICC WSICC WS

ICCICC

JCOP Web JCOP Web Client (JWEB)Client (JWEB)

JCOP Rich JCOP Rich Client (ICC)Client (ICC)

NETWORKNETWORK

SERVICE SERVICE PRODUCERSPRODUCERS

SERVICE SERVICE CONSUMERSCONSUMERS

LC2IS WSLC2IS WS

LC2ISLC2IS

MCCIS WSMCCIS WS

MCCISMCCIS

IGEOSIT WSIGEOSIT WS

IGEOSITIGEOSIT

NIRIS WSNIRIS WS

NIRISNIRIS

• Aims to provide a common operational picture to the NATO users to increase the situational awareness.• Utilized NEC concepts as much as possible.

• Aims to provide a common operational picture to the NATO users to increase the situational awareness.• Utilized NEC concepts as much as possible.

Page 28: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009 NATO UNCLASSIFIED 28

NEC related Experiments JTS/ACCS Target Data Exchange

NEC related Experiments JTS/ACCS Target Data Exchange

Usage of Enterprise Service Bus tool for orchestration.

Prevents point-to-point connections, however should also be maintained separately.

Usage of Enterprise Service Bus tool for orchestration.

Prevents point-to-point connections, however should also be maintained separately.

Page 29: NATO UNCLASSIFIED UNIS Technical Exchange Meeting December, 1-3, 2009 UNIS Technical Exchange Meeting December, 1-3, 2009 US-NATO Air C2 Interoperability

UNIS-TEM-2009

FAST XML Data Store

FAST XML Data Store

NATO UNCLASSIFIED 29

FAST Web Services

FAST Web Application Server (TOMCAT)FAST Alert

Server

FA

ST

Na

tiv

e I

nte

rfa

ce

FAST Client

WS

DL

SOAP/XML

FAST Web Service Consumers

Standard FAST ArchitectureStandard FAST Architecture FAST NNEC ExtensionFAST NNEC Extension

NEC related Experiments Time Sensitive Targeting (TST) Data Exchange

NEC related Experiments Time Sensitive Targeting (TST) Data Exchange

FAST NetworkFAST Network

FAST XML Data Store

FAST XML Data Store

FAST XML Data Store

FAST XML Data Store

FAST Client

FAST Notification

Producer

FAST WS Consumer

FAST WS Notification

Consumer

SOAP/XML

O

AS

ISW

SN

WS

DL

Invoking notify method

getAllKillboxes request

getAllKillboxes response

Notification Subscription Resource File

OASIS Web service Notification (WS-N) standard is used for notifications.

OASIS Web service Notification (WS-N) standard is used for notifications.