INFOD Use Case Scenario

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum JSDL 1.0: Parameter Sweeps OGF 23, June 2008, Barcelona, Spain.
Advertisements

© 2006 Open Grid Forum Network Services Interface OGF30: Connection Services Guy Roberts, 27 th Oct 2010.
© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
© 2006 Open Grid Forum JSDL 1.0: Parameter Sweeps: Examples OGF 22, February 2008, Cambridge, MA.
© 2006 Open Grid Forum GridRPC Interoperability Test Response to comments Yusuke Tanimura.
© 2006 Open Grid Forum OGF19 Federated Identity Rule-based data management Wed 11:00 AM Mountain Laurel Thurs 11:00 AM Bellflower.
© 2006 Open Grid Forum INFOD Extended Specifications OGF21, Seattle, WA, USA
© 2006 Open Grid Forum INFOD for Wide-Area Sensor Networks OGF21, Seattle, WA, USA M. Shankar, ORNL,
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources OGF 20 - Manchester, 7 May 2007.
© 2007 Open Grid Forum JSDL-WG Session OGF21 – Activity schema session 17 October 2007 Seattle, U.S.
© 2008 Open Grid Forum Resource Selection Services OGF22 – Boston, Feb
© 2006 Open Grid Forum JSDL Optional Elements OGF 24 Singapore.
© 2006 Open Grid Forum INFOD-WG Status and Plans OGF21, Seattle, WA, USA
Common Alerting Protocol (CAP) based Emergency Alerts using the Session Initiation Protocol (SIP) draft-ietf-ecrit-data-only-ea-02.
© 2006 Open Grid Forum INFOD Use Case Scenario OGF22, Boston, MA, USA
Architecture of Grid File System (GFS) - Based on the outline draft - Arun swaran Jagatheesan San Diego Supercomputer Center Global Grid Forum 11 Honolulu,
1 ©2013 Open Grid Forum OGF Working Group Sessions Security Area – FEDSEC Jens Jensen, OGF Security Area.
Event Processing A Perspective From Oracle Dieter Gawlick, Shailendra Mishra Oracle Corporation March,
Designing the Architecture for Grid File System (GFS) Arun swaran Jagatheesan San Diego Supercomputer Center Global Grid Forum 12 Brussels, Belgium.
Resource Management in OGSA Authored by the CMM-WG.
© 2006 Open Grid Forum Network Measurements Working Group Summary of the Version 2 Schemata Richard Hughes-Jones Martin Swany, Jason.
Presented February 21, 2006 at NOAA RSS, Podcast/Vodcast, Blog Workshop by Eliot Christian, United States Geological Survey Using RSS for Public Warnings.
© 2006 Open Grid Forum Network Services Interface OGF 32, Salt Lake City Guy Roberts, Inder Monga, Tomohiro Kudoh 16 th July 2011.
© 2006 Open Grid Forum BES 1.1 Andrew Grimshaw. © 2006 Open Grid Forum 2 OGF IPR Policies Apply “ I acknowledge that participation in this meeting is.
© 2007 Open Grid Forum Kick Off BOF Reference Model Working Group Paul Strong 1 st Feb, 2007.
© 2006 Open Grid Forum FEDSEC-CG Andrew Grimshaw and Jens Jensen.
© 2006 Open Grid Forum Activity Instance Schema Philipp Wieder (with the help of the JSDL-WG) Activity Instance Document Schema BoF Monday, 25 February,
© 2006 Open Grid Forum INFOD Use Case Scenario OGF21, Seattle, WA, USA
© 2006 Open Grid Forum Network Services Interface OGF 33, Lyon Guy Roberts, Inder Monga, Tomohiro Kudoh 19 th Sept 2011.
Nomenclature for the OGSA Platform document Fred Maciel.
Grid File System Working Group SAGA and GFS-WG Grid File System Working Group (GFS-WG) Global Grid Forum (GGF)
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources OGF 21, Seattle, Tuesday 16 October 2007.
© 2006 Open Grid Forum BES, HPC, JSDL and GLUE Profiling OGF 23, Barcelona, Tuesday 16 October 2007.
First Responder Use Case March, 2008.
© 2006 Open Grid Forum Network Services Interface CS Errata Guy Roberts, Chin Guok, Tomohiro Kudoh 29 Sept 2015.
© 2006 Open Grid Forum OGSA-WG: EGA Reference Model GGF18 Sept. 12, 4-5:30pm, #159A-B.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2006 Open Grid Forum WS-Agreement Advance Reservation Profile Oliver Waeldrich OGF 26, 26. May, Chapel Hill.
© 2007 Open Grid Forum OGF Management Area Meeting OGF20 7 May, am-12:30pm Manchester, UK.
© 2006 Open Grid Forum VOMSPROC WG OGF36, Chicago, IL, US.
© 2007 Open Grid Forum OGF20 Levels of the Grid Workflow Interoperability OGSA-WG F2F meeting Adrian Toth University of Miskolc NIIF 11 th May, 2007.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2007 Open Grid Forum JSDL-WG Session OGF26 – General Session 11:00-12:30, 28 May 2009 Chapel Hill, NC.
Network Services Interface
OGSA HPC cluster usecase for reference Model v.02
Models for Resources and Management
RISGE-RG use case template
Resource Management in OGSA
Management and Manageability in OGSA
OGF session PMA, Florence, 31 Jan 2017.
Sharing Topology Information
Network Services Interface
OGSA Service Classifications
Network Services Interface Working Group
INFOD-WG Implementation
Network Measurements Working Group
Designing the Architecture for Grid File System (GFS)
Activity Delegation Kick Off
Enterprise Adoption and Outreach
OGF20 Information Model Joint Session
Network Services Interface Working Group
OGSA-RSS-WG EPS Discussion.
INFOD Use Case Scenario
Introduction to OGF Standards
Use Case for controlling the Pierre Auger Observatory remotely
Network Services Interface
UR 1.0 Experiences OGF 24, Singapore.
Graphical Modeling of INFOD applications
OGF 40 Grand BES/JSDL Andrew Grimshaw Genesis II/XSEDE
THE PWSD PROGRAMME.
Presentation transcript:

INFOD Use Case Scenario OGF22, Boston, MA, USA raghul@utk.edu

Overview INFOD Status & Extended Specification Dieter Gawlick (Oracle) INFOD reference implementation First Responder - Use Case Scenario INFOD Registry Implementation Demo INFOD on GME Andras Nadas( Vanderbilt) 2

Information Dissemination Software/ Hardware Source Event Stream: X Temporary or Local Archival Storage Event Stream: Y Event Stream: Z Consumer + Subscriber Publisher/Node/ Computation/ Processing Data Center Traditional Query to Data Center Distributed/Federated Queries - is this technology mature enough? Software/ Hardware Source Event Stream: X Temporary or Local Archival Storage Event Stream: Y Event Stream: Z Consumer + Subscriber Publisher/Node/ Computation/ Processing Subscription Notify to Publishers INFOD Model 3

An Information Dissemination Scenario Notification Message differs based on the entries created and the subscriptions Registers as a Publisher Notification Message Registers as a Subscriber and defines subscription identifying dynamic consumers Notification Message Matches Entities based on entries created Police ABC Chemicals INFOD Registry Service Registers as a Subscriber, defines subscription based on client necessities. Notification Message County Office Notification Message Registers as a Subscriber, defines subscription identifying consumers and describes message format. Registers as a Consumer Service Providers Notification Message Hospital Notification Message NotificationMessage Registers as a Consumer Notification Message Registers as a Consumer Fire Station Weather Station Fire Station Registers as a Publisher Notification Message 4

An Information Dissemination Scenario Alert Msg: Category: Chemical Fire Urgency: Immediate Action: Evacuate Sends Alert message Alert Msg: Category: Fire, Chemical Urgency: Immediate Alert Msg: Category: Fire Urgency: Immediate Action: Stop Police ABC Chemicals INFOD Registry Service Alert Msg: Category: Fire, Chemical Urgency: Immediate Alert Msg: Category: Fire Urgency: Immediate Action: Detour County Office Alert Msg: Category: Fire, Chemical Service Providers Hospital Alert Msg: Category: Fire Urgency: Immediate Action: Detour Alert Msg: Category: Fire Urgency: Expected Action: Evacuate Notification Message Fire Station Weather Station Fire Station Alert Msg: Category: Fire, Chemical Severity: Extreme, (Minor ,Moderate) Chemical Types: XXX Alert Msg: Category: Fire, Chemical Severity: Extreme Chemical Types: XXX 5

INFOD Registry Service An Information Dissemination Scenario Alerting Consumers based on dynamically changing events Alert Msg: Category: Chemical Fire Urgency: Immediate Action: Evacuate Alert Msg: Category: Chemical Fire Action: Stay Indoors Alert Msg: Category: Fire, Chemical Urgency: Immediate Alert Msg: Category: Fire Urgency: Immediate Action: Stop Police ABC Chemicals INFOD Registry Service Alerting System Alert Msg: Category: Fire Urgency: Immediate Action: Detour County Office Alert Msg: Category: Fire, Chemical Service Providers Hospital Alert Msg: Category: Fire Urgency: Expected Action: Evacuate Alert Msg: Category: Fire, Chemical Urgency: Immediate Alert Msg: Category: Fire Urgency: Immediate Action: Detour Alert Msg: Category: Fire Urgency: Immediate Action: Detour East Weather Station Fire Station Alert Msg: Category: Fire, Chemical Severity: Extreme, (Minor ,Moderate) Chemical Types: XXX Alert Msg: Category: Fire, Chemical Severity: Extreme Chemical Types: XXX Fire Station 6 6

INFOD Registry Service An Information Dissemination Scenario Sending alert messages processing multiple streams of events Accident Police ABC Chemicals INFOD Registry Service Alerting System Alert Msg: Category: Fire Urgency: Immediate Action: Detour South/West Alert Msg: Category: Fire Urgency: Immediate Action: Detour SOUTH County Office Service Providers Service Providers Hospital Weather Station Fire Station Evacuation Route Fire Station 7 7

First Responder Use Case Scenario Weather Station Sensor Fusion Center Chemical Sensor 1 INFOD Registry Publisher First Responder 1 First Responder 2 APD 2000 Chemical Sensor 2 Alerting System Plume Analysis Consumer Subscriber/Consumer/Publisher INFOD Message Exchange Information Notification E911 Center Subscriber/Consumer 8

Property Vocabulary Instance INFOD Resources Subscribers and Consumers are modeled as independent entities. Subscriptions are created by a subscribers, conforming to a subset of consumer. Publisher Consumer Consumer Subscriber Subscription defines the event of interest at the publisher, the message to be generated in response to an event and helps identify consumers dynamically. INFOD Registry Publisher Entry Subscriber Entry Subscription Consumer Entry Structured Information Model, user communities are identified by property and data vocabularies. Data Source Entry Property Vocabulary Instance Entries characterize real world entities and define constraints identifying other entities of interest Data Vocabulary Property Vocabulary Also, data source entry details on the publishers information - associated to a data vocabulary. Entry Resource – not an entry Creation of resource Reference (EPR) Vocabulary instances characterize entities and constraints are evaluated on instances created. Notification (by INFOD registry) Notification (by Publishers) 9

The Registry Property Vocabulary – schema for characterizing an external entity (Publisher/Consumer/Subscriber) Data Vocabulary – schema for characterizing an event or information from the publisher Publisher – source of information Publisher Entry Property Vocabulary Instance Data Source Entry Publisher 2 Publisher 3 Publisher Publisher 4 Publisher Entry Data Source Data Source Data Source Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Prop. Vocab. Inst. Prop. Vocab. Inst. Property Vocabulary Data Vocabulary INFOD Registry 10

The Registry Consumer Subscriber Consumer Entry Property Vocabulary Instance Subscriber Subscriber Entry Subscription An update to the Registry triggers matching between entries. Entities receive notification message Publisher sends information to consumer Sensor 5 Sensor 4 Publisher 2 Publisher Consumer Subscriber Subscriber Entry Consumer Entry Publisher Entry 1 Subscription Subscription Prop. Vocab. Inst. Prop. Vocab. Inst. Prop. Vocab. Inst. Data Source Property Vocabulary Data Vocabulary INFOD Registry 11

Constraints Constraints are for expressing entities and data of interest. Property Constraint Used for matching within the INFOD registry Identifies other entries of interest defining constraints on entry properties. Data Constraint Part of the subscription; evaluated by the publisher Describes an event of interest and the message to be generated by the publisher Dynamic Consumer constraint Identifies consumers based on certain characteristics from a set of consumer identified by the INFOD registry. 12

Property Vocabulary Instance First Responder Use Case Scenario Weather Station First Responder First Responder First Responder Sensor 5 Sensor 4 Sensor 1 Alerting System Plume Analysis E911 Center Chemical Sensor 2 Chemical Sensor 1 INFOD Registry Publisher Entry Subscriber Entry Subscription Consumer Entry Data Source Entry Property Vocabulary Instance Data Vocabulary Property Vocabulary Entry Resource – not an entry Creation of resource Reference (EPR) 13 Notification (by INFOD registry) Notification (by Publishers)

First Responder Use Case Scenario Vocabularies are based on NIEM (National Information Exchange Model) CAP (Common Alerting Protocol) Property Vocabulary Sensor property vocabulary (NIEM) Community user property vocabulary (NIEM) Data Vocabulary Sensor / Alert message vocabulary (NIEM + CAP) Weather information vocabulary (DWML–Digital Weather Markup language) 14

Community User Property Vocabulary Sensor Property Vocabulary Property Vocabulary Predicates Comments Sensor Identification Unique id for sensor Sensor Description Details on the sensor Location Physical location of sensor Contact Information Person to be contacted Associated Organization The owner of the sensor Community User Property Vocabulary Property Vocabulary Predicates Comments Identification Identifier for the Organization Name Name of the Organization Description Text Description Location Physical location information Contact Information Person to me contacted Vocabulary predicates are an abstraction from NIEM (National Information Exchange Model) 15

Data Vocabulary Sensor/Alert Data Vocabulary (NIEM and CAP - Common Alerting Protocol) Data Vocabulary Predicates Comments Activity Description between time period Event Description at a specific time Substance Description of a chemical material Status Actual, Exercise, System, Test Message Type Alert, Update, Cancel, Ack, Error Scope Public, Restricted, Private, Urgency Immediate, Expected, Future, Past Response Type Shelter, Evacuate, Prepare, Execute, Monitor, Assess, None Severity Extreme, Severe, Moderate, Minor Certainty Very likely, Likely, Possible, Unlikely Category Geo, Met, Safety, Security, Rescue, Fire, Health, Env, Transport, Infra, CBRNE, Other Weather Sensor Data Vocabulary ( DWML –Digital Weather Markup Language) Data Vocabulary Predicates Comments Location Weather information at a location Time Information at a specific date & time Temperature Temperature unit as an attribute Wind Speed With units as an attribute Wind Direction As an angular measure Humidity As a relative or specific value 16

Implementation specifics JAVA Subscriber Service(s) INFOD Registry Service Subscriber Service Create Subscription Reasoning Component Registry Manager Component Publisher Service(s) Vocabulary Manager Publisher Service Notify Client Create & Monitor INFOD Entry’s Manager Notify Meta Data Manager Consumer Service(s) Create & Monitor Consumer Service Create/ Replace/Drop ORACLE PL/SQL ORACLE Test Environment TOMCAT Oracle Application Server Publisher, Subscriber and Consumers are modeled as web services 17

DEMO First Responder Use Case 18

Overview Status & Extended Specification Dieter Gawlick (Oracle) INFOD reference implementation First Responder - Use Case Scenario INFOD Registry Implementation Demo INFOD on GME Andras Nadas( Vanderbilt) 19

Full Copyright Notice Copyright (C) Open Grid Forum (2006). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. The limited permissions granted above are perpetual and will not be revoked by the OGF or its successors or assignees. OGF Full Copyright Notice if necessary 20