semantic technologies in the business grid collaboration lifecycle dr ioannis kotsiopoulos...

Semantic Technologies in the Business Grid

Collaboration Lifecycle Dr Ioannis [email protected]

BREIN - Semantic Week 09

Presentation Outline

• BREIN Vision, Overview, Scenarios• Guiding Principles • Business Grid Collaboration Lifecycle • Architectural Principles• BREIN Ontologies• Knowledge Aware Grid Services in BREIN• What to take away

2BREIN - Semantic Week 09

BREIN VisionO

bjec

tives

‘To take the Grid to businessTo take the Grid to business’

Enable participants to easily interact It provides an Intelligent, adaptive framework Increase the stability and dynamism of the framework through a set of innovative technologies Optimize the collaboration so as to meet the individual participant’s business objectives Provide business entities with a means to optimize their service provisioning (regarding the respective business goals)

Create an infrastructure that will increase the level and dynamism of collaborations among companies, with special focus on SMEs


BREIN Vision in Business Terms

•Business aspects will be improved with this project:

Privacy and confidentiality of data with encrypted communications and applied security policiesTrust in enterprises (enterprise historical reputation)

Negotiation between customer provider to define terms in the service provision is done as a contract.Provider should satisfy the terms agreed or penalties should be applied.

Hides the high complexity in the current Grid infrastructure to users Reduces the human interaction in business tasks by automating them Providing easy way of usage

Cost Reduction Simplicity for usersService Level Agreement

ReliabilityIncreases business competitiveness

Enhanced Security and Privacy

SLA guaranteed with penalties in case of violationsThe framework is dynamic and can adapt to changing situationsSelf-Management, Self-Configuration

Outsourcing of infrastructure capabilities, to reduce the investment in hardware and softwareSaaS model can be applied

Complex collaboration chain, driven by each party's business objectivesEnterprises pursue their own business objectives Optimized business benefits for all parties


The team• Coordinated by Telefonica I+D and technically lead by

U. Stuttgart• 16 partners with experience in Workflow Management,

Multi-agent technologies, Business Process Modelling, Security, HPC and Semantic technologies.• Strong emphasis on industrial partner scenarios; visionary scenarios (10 years vision) and the validation scenarios (what can be shown short term).

• ANSYS is leading the Virtual Engineering Scenario: use HPC and traditional computational Grid but want to increase flexibility, agility, reliability to provide new services to their customers

• Stuttgart Airport: Bring Grid Computing processes to manage ground handling services and resources: buses, passengers, airplanes, catering, fuelling, luggage transportation, etc. 5BREIN - Semantic Week 09

http://images.google.de/imgres?imgurl=http://www.china-goes-dus.de/de/duesseldorf/grafik/flugzeugstart.jpg&imgrefurl=http://www.china-goes-dus.de/de/duesseldorf/flughafen.asp&h=150&w=200&sz=8&hl=de&start=15&tbnid=VTHjn8-lhtr80M:&tbnh=78&tbnw=104&prev=/images?q=Flugzeugstart&gbv=2&ndsp=20&svnum=10&hl=de&sa=N

Semantic Grid Principles

7

Systematic management of metadata in Grid middleware

Embedding and implicit metadata is the enemy of shareability and reuse in an open and decoupled

and collaborative environment.Expose it.

Manage it.Make it a first class citizen.

Machine processable metadata is

machine actionable metadataEnrich it.

With meaning.Semantics.

Semantic enrichment of metadata in Grid middleware

Source: Carole Goble

Service-Oriented Knowledge Utility

8

A utility is a directly and immediately useable service with established functionality, performance and dependability, illustrating the emphasis on user needs and issues such as trust

Services are knowledge-assisted (‘semantic’) to facilitate automation and advanced functionality, the knowledge aspect reinforced by the emphasis on delivering high level services to the user

The architecture comprises services which may be instantiated and assembled dynamically, hence the structure, behaviour and location of software is changing at run-time

Source: David De Roure

Service Customer – Provider Interaction Lifecycle

Capture Business Process

Create Workflow

Discover Service

Negotiate

Select Service

Use Service

DissolveBOC PromoteBOC Promote

ED Workflow EngineED Workflow Engine

Semantic SLA NegotiationSemantic SLA Negotiation

SA-SLASA-SLA

QoS Service SelectionQoS Service Selection


Service Provider – Provider Interaction Lifecycle

Negotiate

Schedule resources

Outsource Resources

Monitor Resources

Adapt

DissolveSemantic SchedulerSemantic Scheduler

Multi-agent decision makingMulti-agent decision making

Semantic Service Offer Discovery

SA-SLASA-SLA

Semantic SLA NegotiationSemantic SLA Negotiation


Architecture Overview

BREIN - Semantic Week 09 14

Se

cu

rity

BR Management

SLA Management WF Management

Adaptation Planning

Infrastructure Capabilities Semantic Infrastructure

Agents based capabilities

ConfiguresTokens

Access rights

Triggers adaptation actions

Data for evaluation

Uses basic capabilities

Uses basic capabilities

Asks for providers

Triggers negotiation

Gathers SLA related info

Uses semantic components

Management Group

Infrastructure Group

Provides plan

Customer’s GOAL

Data for evaluation

The Pillars of BREIN Semantic Infrastructure

Specification for semantic Annotations (SA-SLA)

- Backward compatible

- Light weight approach




Conceptual model- Business ontology- QoS ontology-Technology ontology-Grid Resource Ontology


Architecture-S-OGSA-BREIN Semantic Infrastructure


Knowledge Aware Grid Services-Semantics Scheduling-SLA negotiation & matching-Workflow execution-Multi-agents



S-OGSA Model


Knowledge Entity

Grid EntitySemantic Binding

Is-a

0..m0..m

1..m

Grid Resource

Is-a

Is-a

Is-a

1..m

Knowledge Resource

Knowledge Service

Is-a

Is-a

Is-a

Ontology Rule-Base

Is-a

Virtual Machine

Airport Bus

Is-a

Grid Service

18 Final review, Manchester, 17th July 2007

S-OGSA Model– Semantic-OGSA– Semantic Grid Reference

Architecture– A low-impact extension of

OGSA– Mixed ecosystem of Grid

and Semantic Grid services• Services ignorant of

bindings• Services binding aware but

unable to process them• Services binding aware and

capable of processing (part of) them

– Everything is OGSA compliant

Model

Capabilities

Mechanisms

provide/consume

expose

use

The BREIN Roadmap

Semantic Week

Page 21

AkogrimoEmergencyScenario

Register as User Record ECG Transmit ECG Analyze ECG Initiate EmergencyCall

Talk to theemergency Center

Should the ECGData be

continouslyrecorded?

Wait theconfigured time

yes

no

Wait foremergency

medical service

Get first aid &diagnosis

Go to hospital Get furtherdiagnosis

Treat disease PaymentIs an additionaldiagnosis

necessary?

no

yes

Part ofSource

Metamodel

Part ofTarget

Metamodel

ReferenceLink

ReferenceDomain

reference source

reference target

has

1 * * 1

1..*

1

Part ofSource

Metamodel

Part ofTarget

Metamodel

ReferenceLink

ReferenceDomain

reference source

reference target

has

1 * * 1

1..*

1

Part ofSource

Metamodel

Part ofTarget

Metamodel

ReferenceLink

ReferenceDomain

reference source

reference target

has

1 * * 1

1..*

1

Part ofSource

Metamodel

Part ofTarget

Metamodel

ReferenceLink

ReferenceDomain

reference source

reference target

has

1 * * 1

1..*

1

...

Akogrimo

Emergency

Scenario

Register as UserRecord ECG

Transmit ECG

Analyze ECGInitiate Emergency

Call

Talk to the

emergency Center

Should the ECG

Data be

continously

recorded?

Wait the

configured time

yes

no

Wait for

emergency

medical service

Get first aid &

diagnosis

Go to hospital

Get further

diagnosis

Treat disease

Payment

Is an additional

diagnosis

necessary?

no

yes

Usa

ge

Eva

luat

ion

Structure

Process

Profiles

Business

Semantic Week

Page 22

Semantic Modelling Services

Top-down by domain experts

Bottom-up by knowledge engineers

Modelling process using BPM4SOA

Modelling process using card sorting

Ontology

Domain feedback

Ontology feedback

Ontology input

Domain input

Conceptual model

Information involved Ontologies

Domain

independent Business Ontology Technology Ontology

Sector (scenario)

dependent

QoS Ontology

VE Service VE Resource

Enterprise-specific

domain dependent ANSYS Amazon


Grid Resource

SA-SLA: Motivation, problem area

• Semantic Interoperability during negotiation of SLAs– Several competing protocols– Different terminologies between Service Providers

• Different metrics used for definition of QoS• Different types of services or resources from Service

Providers• Different benchmarking methods

– Different languages• Providers and consumers are collaborating on a global scale

– New specifications will just add more confusion and introduce new interoperability problems

– Modifying existing specifications without thinking of backward compatibility will increase interoperability problems


29

Negotiation example

Negotiatio

n

Negotiation

ANSYS request

•CPUName: IntelCore Duo•CPU Speed: 2 GHz•Capacity: 400 MB•Price: 27 euros per day•DiskSpace: 250GB

CUSTOMERSoftware engineering company

-RAMMemory: 7.5 GB-ComputeUnit: 4 ECU-Storage: 850GB-Platform: 64 bit-Price: $0.4 per instance hour

AMAZON

-MemoryPerTask: 7.5 GB-ClockCPUSpeed: 100 MHz / process-StorageCapability: 850GB-Cost: 5 euros/task/hour

BSC

Basic Principles• Use annotations only

when you need them• Ignore annotations if

your SLA negotiator does not understand them

• Use SLA mediator and Common Ontology to request matching information


SLA Negotiation Architecture

Semantic Provisioning Service: Annotation tool I

Annotation tool II

Metadata Management within the Infrastructure• Now I have an SLA, how do I deal with it?

• Need a flexible and adaptive infrastructure to support it

• Failure to satisfy an SLA means penalties and reputation damage

• Things change too frequently for administrators to react

• Need automation• Need intelligent decision making• I also need Cloud Computing as an outsourcing option


Semantic Scheduler


Allow integration with Clouds

• Outsource Service when can’t handle locally– Local resources unavailable– QoS level not available

• Customer does not see this happen– They just asked for service

• Service Provider needs…– Place that can achieve the same task– Control over QoS level, price, etc.– Ability to use multiple second-tier Service Providers


What to take away

• Semantics can be found throughout the lifecycle of business collaborations

• Metadata carry knowledge and they need to be managed in a systematic and principled manner

• BREIN brings Grids to Business and Semantic Technologies are the transport vehicle

• BREIN applies semantic technologies in order to improve automation, interoperability, simplicity, flexibility, reliability, and extensibility

• BREIN wants to apply successful Semantic Technologies from other projects (already extends OntoGrid and UniGrids)


Thank you for listening Any questions?

Acknowledgements

The Semantic Group of the BREIN Consortium

John Brooke and Carole Goble

Backup Slides


BREIN Ontologies imports

OWL-SOWL-S

S-BPMNS-BPMNBusiness layerBusiness layer

Implementation layerImplementation layer

IT WorkflowIT WorkflowServicesServices

Business OntologyBusiness Ontology

Taken from SUPERTaken from SUPER

OWL-WSOWL-WS

We could add BPMOWe could add BPMO

•Allow to link business activities with IT implementations

•Allow describe non-funtional properties

•Allow to link business activities with IT implementations

•Allow describe non-funtional properties

QoS ontologyQoS ontology •Annotate SLAT files•Annotate SLAT files

Infraestructure layerInfraestructure layer

Technical ontology

Technical ontology


Tools and components which use it

• Tools which allow for annotating non-functional descriptions– SASLAT GUI: It allow for annotating SLA parameters in TSLA by QoS ontology. – SLA translator (SLAT): Ontology manager which stores the QoS ontology.– Service description GUI: It is a GUI to create semantically service

descriptions and annotate non functional properties with the business ontology.– Workflow Editor: A tool to draw business process in terms of workflow, which

allows users to describe businesses processes properties by using business ontology.

• BREIN components which will be reasoner with business ontologies– SESS: The service selection is based on service non-functional properties (like

QoS metrics) which are annotated in SLA files by semantic metrics.– SLA Negotiator: Since the SLA files that the SLA Negotiator is working on,

are annotated semantically, it will consume the QoS ontology in order to understand the metrics semantically annotated.

– BREIN Software Agents: Software agents use semantically annotations of web services they represent when communicating with other agents; thus such annotations will also be used on the conceptual level of agent-to-agent communication. Annotations with regard to the BREIN Business Ontology are required for reason about received messages from other agents.


semantic technologies in the business grid collaboration lifecycle dr ioannis kotsiopoulos...

Documents