1 1 Emergency Data Exchange Language – Distribution Element (EDXL-DE) David E. Ellis Sandia National Laboratories.

Slides:



Advertisements
Similar presentations
1 Emergency Response Management Systems (ERMS)versus(ERSM) Emergency Response Systems Management: Identifying the Critical Path to Improved Decision Support.
Advertisements

Summary Introduction The protocols developed by ITU-T E-Health protocol Architecture of e-Health X.th1 X.th2 to X.th6 Common Alerting Protocol Conclusion.
OASIS Organization for the Advancement of Structured Information Standards Elysa Jones, Chair OASIS Emergency Management Technical Committee
Our mission is to enable public safety managers everywhere to help people and save lives by providing the best value interoperable solution. We are dedicated.
SOAP.
NAT TRAVERSAL FOR IPSEC Research Seminar on Datacommunications Software HIIT
Technologies for PubSub Application Format (PSAF) Leonardo Chiariglione CEDEO.net Kenichi Nakamura (Panasonic) Giuseppe Tropea (CNIT) Valencia, ES, 2014/04/01.
Sibiu– November th International Conference of the Romanian Medical Informatics Society MEDINF 2007 SIUMSIUM EMIL STĂNESCU National Institute for.
Security Policy Implementation Strategies for Common Carrier Monitoring Service Providers Short Position Paper for IEEE POLICY 2009 Carl A. Gunter University.
Continuing through Emergency: eBiz/eGov continuity and contingency functioning throughout emergency incidents Presented by: Michelle.
Copyright © 2006, Open Geospatial Consortium, Inc., All Rights Reserved. The OGC and Emergency Services: GML for Location Transport & Formats & Mapping.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
Integrated Public Alert and Warning System Mark Lucero, Chief Engineer IPAWS Division March 6, 2013.
Just a collection of WS diagrams… food for thought Dave Hollander.
SOA, BPM, BPEL, jBPM.
Trade Software Developer Technical Seminar Document Imaging System March 7, 2012.
® Making Location Count EDXL-SitRep and OWS Context - Opportunity for Collaboration 75th OGC Technical Committee Sydney, Australia Lew Leinenweber, Evolution.
COMCARE1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath, Technical Director, COMCARE Emergency Services SDO Workshop.
An XMPP (Extensible Message and Presence Protocol) based implementation for NHIN Direct 1.
MPEG-21 : Overview MUMT 611 Doug Van Nort. Introduction Rather than audiovisual content, purpose is set of standards to deliver multimedia in secure environment.
Disaster Management eGov Initiative (DM) Program Overview December 2004.
Authority Vectors David E. Ellis. U.S. Geo-Political Example Geographic AreaPolitical Authority (Jurisdictions) Solar System, Galaxy, Universe: Are definedSolar.
Disaster Management - Open Platform for Emergency Networks (DM OPEN)‏ Introduction to the Interoperability Environment.
A National Effort on Emergency Data Distribution David E. Ellis Information Management Architect (505) ,
WS-Security: SOAP Message Security Web-enhanced Information Management (WHIM) Justin R. Wang Professor Kaiser.
The OSI Model An ISO (International standard Organization) that covers all aspects of network communications is the Open System Interconnection (OSI) model.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
NENA Development Conference | October 2014 | Orlando, Florida Emergency Incident Data Document (EIDD) Transfer Protocols Jerry Schlesinger, PMP – City.
OV Copyright © 2011 Element K Content LLC. All rights reserved. Network Security  Network Perimeter Security  Intrusion Detection and Prevention.
Delegation of Intent via Conversation David E. Ellis.
Building Information Exchange with First Responders (BIEFR) David Holmberg, NIST June 11, 2009 Slides credit to Alan Vinh.
Disaster Management e-Gov Initiative Program A Deceptively Simple Approach to an Emergency Data Exchange Language Distribution Element (EDXL-DE) Based.
Understanding Emergency Routing Policies with EDXL Using the Distribution Element and the ValueListURN Tutorial Example Policy Implementation: Sensors.
How Federal Data Programs Support Each Other Patrick Gannon – President & COO, Warning Systems, Inc. – OASIS Emergency Management Adoption Committee Christopher.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
Emergency Data Exchange Language (EDXL) International Free Open.
Trans-enterprise Service Grid (TSG) Active Interoperability Across Independent Partners David E. Ellis Information Management Architect (505) ,
William Stallings Data and Computer Communications
Chapter 9 Hardware Addressing and Frame Type Identification 1.Delivering and sending packets 2.Hardware addressing: specifying a destination 3. Broadcasting.
Common Alerting Protocol (CAP) v. 1.0 Emergency Management Technical Committee.
Building Blocks for the NG9-1-1 PSAP MICHAEL SMITH - DSS CORP. RICK BLACKWELL, ENP - GREENVILLE COUNTY, SC.
1 Chapter Overview Network Communications The OSI Reference Model.
OASIS Organization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines.
2 October 2007 Improving Rapid Emergency First Response with SOA 4 th SOA for E-Government Conference 1 Improving Rapid Emergency Response Systems with.
Sensor Standards Harmonization Working Group Report Summary of Sensor Standards Harmonization Working Group (SSHWG) Meeting held on Sensor Standards Harmonization.
CHAPTER 4 PROTOCOLS AND THE TCP/IP SUITE Acknowledgement: The Slides Were Provided By Cory Beard, William Stallings For Their Textbook “Wireless Communication.
Timothy Putprush Baltimore, MD September 30, 2009 Federal Emergency Management Agency (FEMA) Integrated Public Alert and Warning System Presentation to.
AMQP, Message Broker Babu Ram Dawadi. overview Why MOM architecture? Messaging broker like RabbitMQ in brief RabbitMQ AMQP – What is it ?
9-1-1 ASSOCIATION - STEPS COMMITTEE 1/3/2013 NG9-1-1 TECHNOLOGY & PROCESS.
Copyright © 2002 Pearson Education, Inc. Slide 3-1 Internet II A consortium of more than 180 universities, government agencies, and private businesses.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
21 February 2006 Semantic Interoperability Architecture Geospatial Context 1 Semantic Interoperability at Work: Improving Rapid First Response What Does.
Emergency Data Exchange Language (EDXL) Internationally Available Free Standards Open and Non-Proprietary.
OASIS Organization for the Advancement of Structured Information Standards Emergency Management Presentation Guidelines.
23 May 2006 SOA for E-Gov Interoperability at Work: Improving Rapid First Response 1 SOA for E-Government Interoperability at Work: Improving Rapid First.
Emergency Data Exchange Language (EDXL) Internationally Available Free Standards Open and Non-Proprietary.
EDXL Header Usage Element Element Purpose Core Message Routing Usage Delivery Selection distributionIDMessage Identification None senderIDMessage Identification.
TCP/IP Protocol Suite Suresh Kr Sharma 1 The OSI Model and the TCP/IP Protocol Suite Established in 1947, the International Standards Organization (ISO)
8 D E C E M B E R E M E R G E N C YM A N A G E M E N TS T A N D A R D S O V E R V I E W Open Floor Plan Display / Exchange (OFPD/X) Emergency.
OASIS Organization for the Advancement of Structured Information Standards Introduction Slide Decks.
The Emergency Incident Data Document (EIDD)
Integrated Public Alert and Warning System
CompTIA Security+ Study Guide (SY0-401)
How Federal Data Programs Support Each Other
CompTIA Security+ Study Guide (SY0-401)
OASIS, Emergency Management Technical Committee
Mark Epstein Senior Vice President Qualcomm
Presentation transcript:

1 1 Emergency Data Exchange Language – Distribution Element (EDXL-DE) David E. Ellis Sandia National Laboratories

2 2 Overview The Emergency Data Exchange Language is a Family of Standards which addresses two fundamental needs. Interoperable content for emergency situations Secure policy-based distribution of any content type Most advanced EDXL-DE capacities use SOA-based publish/subscribed software on jurisdictionally controlled routing hardware to create a communications grid to accomplish diverse interoperability solutions for both now and for the future. Today’s discussion will cover the basic capabilities of EDXL- DE distribution with emphasis of the versatility of non- emergency information delivery. Please hold questions to panel discussion or contact me after is session

3 3 Structure of EDXL-DE The EDXL-DE is designed to encapsulate multiple content objects with metadata allowing policy-based distribution to recipients regardless of network or reception technology EDXL-DE is an XML schema which has the following: Header section One or more target sections One or more content sections Each content section has the following: Header section with either xmlContent (using schema and namespace of content) or nonXMLContent ( embedded or referenced elsewhere) Signing and/or encrypting of document and/or content

4 4 EDXLDistribution distributionID senderID dateTimeSent distributionStatus distributionType combinedConfidentiality language senderRole * recipientRole * keyword * distributionReference * explicitAddress * targetArea circle * polygon * country * subdivision * locCodeUN * nonXMLContent mimeType size digest uri derefUri xmlContent keyXMLContent embeddedXMLContent OR contentObject contentDescription contentKeyword * incidentIdentifier incidentDescription originatorRole * consumerRole * confidentiality * Specific Message Content - CAP CAP EDLX-RM - HAVE - N25 - EDXL-SA - VOIP - Images - Sensor track data - etc. 0..* Bold indicates required element. * indicates multiple instances allowed EDXL-DE Schema Structure

5 5 Delivery Concepts Each EDXL-DE delivery solution will tailor the requirements for distribution grid based on publisher injection capability and potential recipient capability. Human created EDXL-DE documents can tailor content Sensor and other fixed content sources need adapters For non-trivial point-to-point information exchanges, the EDXL-DE document acts like an IP Packet where: EDXL-DE documents are network agnostic EDXL-DE document elements must conform to COI and grid specific syntax and semantics Mediation hardware and software must: understand EDXL-DE structure Implement policies on transiting EDXL–DE document

6 6 EDXL-DE Element Usage Message Identification distributionID senderID dateTimeSent distributionReference Delivery Filtering distributionStatus distributionType Security Filtering combinedConfidentiality confidentiality Redistribution Routing explicitAddress Complex Policy Formation senderRole recipientRole keyword contentKeyword originatorRole consumerRole Area for Content delivery circle polygon country subdivision locCodeUN

7 7 Notional Layout of Grid

8 8 Decoupling Sender - Receiver

9 9 EDXL-DE Conclusion EDXL-DE enables unprecedented XML and nonXML document-based information exchange flexibility Distribution can include diverse content and even translate synchronous to asynchronous protocol Grid communities can develop solution specific delivery policies, topologies and EDXL-DE semantics and syntax OASIS Infrastructure sub-committee is developing next generation of the EDXL-DE based on developmental pilots like: Integrated Public Alert and Warning System (IPAWS) Spiral One testbed South-east Transportation Corridor Pilot (SETCP)

10 SETCP and Usage Backup Slides South-east Transportation Corridor Pilot Coverage These are some content type from SETCP Columbia County, GA – 35 Attachments Weigh Station Camera Gamma and Neutron Location Detection Information Uniform Hazard Waste Manifest XML Element Usage EDXL Header Usage contentObject Elements Usage Payload Element Usage

11 SETCP Coverage

12 Columbia County, GA – 35 Attachments Caller Information: Officer Name: Agency: Call Back #: ( ) – Incident Information: Case ID: A9d93d5de d07-bc05-c11d96212a3e Time: T20:31:32.948Z How may JAC assist you? Alarm Information: Radiation Type: Gamma & Neutron Primary Screen Equipment: SAIC RPM PRD Reading: Secondary Screen Equipment: n/a Distance From Source: Additional Information: Narrative: Comments: Spectroscopic Findings:

13 Weigh Station Camera

14 Gamma and Neutron Location

15 Detection Information

16 Uniform Hazard Waste Manifest

17 EDXL Header Usage Element Element Purpose Core Message Routing Usage Delivery Selection distributionIDMessage Identification None senderIDMessage Identification None dateTimeSentMessage Identification None distributionStatusAction Level None - TBD Application Filtering distributionTypeFunctional Type None - TBD Application Filtering combinedConfidentialityInformational None Security Filtering languageInformational None Nationality Filtering senderRoleFunctional RoleExp/Imp Pub/SubCOI Filtering recipientRoleFunctional RoleExp/Imp Pub/SubCOI Filtering keywordContent IdentificationExp/Imp Pub/SubCOI Filtering distributionReferenceMessage Identification ExperimentingFixed explicitAddressExternal deliveryExplicitFixed

18 contentObject Elements Usage contentObject Element Element Purpose Core Message Routing Usage Delivery Selection contentDescriptionInformationalNoneSpecial * contentKeywordContent IdentificationExp/Imp Pub/Sub COI Filtering incidentIDInformationalNone incidentDescriptionInformationalNone originatorRoleFunctional RoleExp/Imp Pub/SubCOI Filtering cosumerRoleFunctional RoleExp/Imp Pub/SubCOI Filtering confidentialityInformationalNoneSecurity Filtering any*Message SecurityNoneCertificate Holders

19 Payload Element Usage nonXMLContent Element Element Purpose Core Message Routing Usage Delivery Selection mimeType Content IdentificationNoneApplication Filtering sizeInformationalNone Distribution Filtering digestMessage SecurityNone uriInformationalNone contentDataPayloadNone xmlContent Element Element Purpose Message Routing Usage Delivery Selection keyXMLContent Expose specific Payload elements None COI Filtering embeddedXMLContentPayload None