© 2006 Open Grid Forum INFOD Use Case Scenario OGF22, Boston, MA, USA [email protected].

© 2006 Open Grid Forum

INFOD Use Case ScenarioOGF22, Boston, MA, USA

[email protected]

2© 2006 Open Grid Forum

• 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)

Overview


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?

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

Subscription

Notify to Publishers

INFOD Model


An Information Dissemination Scenario

ABC Chemicals

Fire StationFire Station

Hospital

Police

INFOD Registry Service

County Office

Registers as a Publisher

Registers as a Consumer

Registers as a Consumer

Registers as a Subscriber, defines subscription identifying consumers and describes message format.

Registers as a Subscriber and defines subscription identifying dynamic consumers

Service Providers

Notification Message differs based on the entries created and the subscriptions Notification

Message

Notification Message




Registers as a Subscriber, defines subscription based on client necessities.

Matches Entities based on entries created

Registers as a ConsumerNotification

MessageWeather Station

Registers as a Publisher

NotificationMessage





ABC Chemicals

Fire StationFire Station

Hospital

Police

Alert Msg: Category: Fire, Chemical Severity: Extreme Chemical Types: XXX

Alert Msg: Category: Fire Urgency: Immediate Action: Stop

Alert Msg: Category: Fire Urgency: Immediate Action: Detour

Alert Msg: Category: Fire Urgency: Expected Action: Evacuate


Alert Msg: Category: Fire, Chemical Severity: Extreme, (Minor ,Moderate) Chemical Types: XXX

Sends Alert message

County Office

Alert Msg: Category: Fire, ChemicalService Providers

Alert Msg: Category: Fire, Chemical Urgency: Immediate


Alert Msg: Category: Chemical Fire Urgency: Immediate Action: Evacuate

Weather Station



6© 2006 Open Grid Forum 6

ABC Chemicals

Fire Station

Fire Station

Hospital

Police

Alert Msg: Category: Fire, Chemical Severity: Extreme Chemical Types: XXX

Alert Msg: Category: Fire Urgency: Immediate Action: Stop


Alert Msg: Category: Fire, Chemical Severity: Extreme, (Minor ,Moderate) Chemical Types: XXX

County Office

Alert Msg: Category: Fire, ChemicalService Providers



Alert Msg: Category: Chemical Fire Urgency: Immediate Action: Evacuate

Weather Station


Alert Msg: Category: Fire Urgency: Expected Action: Evacuate

Alerting System

Alerting Consumers based on dynamically changing events


Alert Msg: Category: Chemical Fire Action: Stay Indoors

Alert Msg: Category: Fire Urgency: Immediate Action: Detour East


7© 2006 Open Grid Forum 7

ABC Chemicals

Fire Station

Fire Station

Hospital

Police

County Office

Service Providers

Weather Station

Alerting System

Accident

Sending alert messages processing multiple streams of events


Evacuation Route

Service Providers

Alert Msg: Category: Fire Urgency: Immediate Action: Detour South/West

Alert Msg: Category: Fire Urgency: Immediate Action: Detour SOUTH



First Responder Use Case Scenario

Weather StationSensor Fusion Center

Chemical Sensor 1

INFOD Registry

Publisher Publisher

First Responder 1

First Responder 2

APD 2000Chemical Sensor 2

Alerting System

Plume Analysis

Publisher

Consumer

Consumer

Subscriber/Consumer/Publisher

INFOD Message Exchange Information Notification

E911 Center

Subscriber/Consumer


Subscription defines the event of interest at the publisher, the message to be generated in response to an event and helps identify consumers dynamically.

Entries characterize real world entities and define constraints identifying other entities of interest

Also, data source entry details on the publishers information - associated to a data vocabulary.

Subscribers and Consumers are modeled as independent entities. Subscriptions are created by a subscribers, conforming to a subset of consumer.

Structured Information Model, user communities are identified by property and data vocabularies.

INFOD Resources

Consumer

Subscription

Data Vocabulary

Data SourceEntry

Property Vocabulary Instance

Creation of resource

Notification (by INFOD registry)

Reference (EPR)

Notification (by Publishers)

INFOD Registry

Entry Resource – not an entry

ConsumerPublisher

Subscriber

Property Vocabulary

PublisherEntry

SubscriberEntry

ConsumerEntry

Vocabulary instances characterize entities and constraints are evaluated on instances created.


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

• Property Vocabulary Instance

Publisher

Property Vocabulary Data Vocabulary

INFOD Registry

Publisher Entry

Prop. Vocab. Inst. Data Source

Publisher 3

Publisher 4

Data SourceData Source

Data Source

Publisher 2

Prop. Vocab. Inst.Prop. Vocab. Inst.

Prop. Vocab. Inst.


• Consumer • Consumer Entry• Property Vocabulary Instance

• Subscriber• Subscriber Entry• Property Vocabulary Instance• Subscription

• An update to the Registry triggers matching between entries.

• Entities receive notification message

• Publisher sends information to consumer

The Registry

Sensor 5

INFOD Registry

Publisher

Prop. Vocab. Inst.

Sensor 4Publisher 2

Publisher Entry 1

Data Source

Consumer Entry

Prop. Vocab. Inst.

Subscriber Entry

SubscriptionSubscription

Prop. Vocab. Inst.

Consumer

Subscriber

Property Vocabulary Data Vocabulary


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• Part of the subscription; evaluated by the publisher• Identifies consumers based on certain characteristics from a set of

consumer identified by the INFOD registry.


Subscription

Data Vocabulary

Data SourceEntry

Property Vocabulary Instance

Creation of resource

Notification (by INFOD registry)

Reference (EPR)

Notification (by Publishers)

INFOD Registry

Entry Resource – not an entry

Property Vocabulary

PublisherEntry

SubscriberEntry

ConsumerEntry

Sensor 5

Chemical Sensor 2

Sensor 4Sensor 1

Chemical Sensor 1

Weather Station

Alerting System

Plume Analysis

First ResponderFirst ResponderFirst Responder

E911 Center



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)



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

Sensor 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

Community User Property Vocabulary

Vocabulary predicates are an abstraction from NIEM (National Information Exchange Model)


Data Vocabulary

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

Sensor/Alert Data Vocabulary (NIEM and CAP - Common Alerting Protocol)

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

Weather Sensor Data Vocabulary ( DWML –Digital Weather Markup Language)


Implementation specifics

Publisher, Subscriber and Consumers are modeled as web services

Publisher Service(s)Publisher

Service

Consumer Service(s)Consumer

Service

NotifyClient Create

& Monitor

Create & Monitor

Notify

Subscriber Service(s)Subscriber

ServiceCreate

Test Environment

JAVA

ORACLE PL/SQL

Create/ Replace/Drop


Subscription Reasoning Component

Registry Manager Component

Vocabulary Manager

INFOD Entry’s Manager

Meta Data Manager

ORACLEOracle Application ServerTOMCAT


DEMOFirst Responder Use Case


• Status & Extended Specification• Dieter Gawlick (Oracle)

• INFOD reference implementation• First Responder - Use Case Scenario• INFOD Registry Implementation• Demo

• INFOD on GME• Andras Nadas( Vanderbilt)

Overview


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.

© 2006 Open Grid Forum INFOD Use Case Scenario OGF22, Boston, MA, USA [email protected].

Documents

Transcript of © 2006 Open Grid Forum INFOD Use Case Scenario OGF22, Boston, MA, USA [email protected].