telefÓnica i+d date: 25th october 2007 sergio garcí á gómez ([email protected]) © 2007 telefónica...

TELEFÓNICA I+DDate: 25th October 2007Sergio Garcí á Gómez ([email protected])

© 2007 Telefónica Investigación y Desarrollo, S.A. Unipersonal

SPIDERSSemantic P2p data Interchange with DistributedagEnts among netwoRk management Systems

W3C Workshop on RDF Access to Relational Databases

25-26 October, 2007 — Cambridge, MA, USA

2TELEFÓNICA I+D


01 Objectives

- Motivation

- Vision

- Ingredients

- Goals

02 Today’s approach

- IU Screenshots

03 Requirements

04 Conclusions

Index

3TELEFÓNICA I+D


SPIDERS motivation 01 Operations Support Systems (OSS) and Business Support Systems

(BSS) in an incumbent operator compose a complex ecosystem of legacy systems.

Each system supports different functionalities and manages and shares with other systems large amounts of data.

Data is propagated by remote invocations, message passing systems, ad-hoc interfaces and also by manual data loads. These are error prone procedures.

Problems in the quality of data may cause delays and failures in network management processes and therefore, higher operation costs (OPEX) and delays in the time-to-market.

— It also hampers the automation of management processes and the

development of autonomic communications systems and elements.

4TELEFÓNICA I+D


Vision

Local Ontology

Relational BD

P2P NetworkLocal Ontology

Relational BD

Relational BD

Local Ontology

OSS 1

OSS 2

OSS 3

01

To create a semantic layer which makes up a federated and consolidated view of information throughout the network and service management ecosystem.

5TELEFÓNICA I+D


Ingredients (some buzzwords)

Semantic technology: ontology (OWL) based data models and SPARQL queries.

P2P: each legacy OSS is a peer node in a network.

Distributed Agents: every peer system

Network Management Systems: systems are, in fact, Operations Support Systems (OSS)

NGOSS: New Generation Operations Systems and Software.

SID: NGOSS Shared Information and Data.

01

SPIDERS: Semantic P2p data Interchange with Distributed agEnts among netwoRk management

Systems

6TELEFÓNICA I+D


Goals

To model the SID as an ontology and to extend the model to the needs of information to each OSS.

To provide the mechanisms to create a federated view of all the SID-based ontologies.

To create a P2P distributed network of OSS-attached agents which are able to:

— translate relational information into semantic information through SPARQL queries.

— insert or update the relational data with information from the SPARQL query results.

To provide the mechanisms to support the needs from real systems: subscriptions to data changes, on demand queries, massive loads or validation of data integrity.

The system must be as less intrusive as possible with the existing legacy OSS's.

01

7TELEFÓNICA I+D


Today’s approach02

Relational BD

OSS 1

P2P Network

Local Ontology

Relational BD

OSS 2

D2R Mapping

SPIDERS Operation:

•Variables

•SPARQL Queries

•Assignments

SPIDERS Agent

SPIDERS Agent

SPARQL Query

SPARQL ResultSet to DB (assignment)

SPARQL Query

Federated Ontology

1

2

3

4 5

6

7

8

8TELEFÓNICA I+D


UI Screenshot (I)02

Based on Protègè and OntoSphere plugin

9TELEFÓNICA I+D


UI Screenshot (II)02

10TELEFÓNICA I+D


UI Screenshot (&III)02

11TELEFÓNICA I+D


Requirements (I)

SPARQL based access

— Efficient access.

— The data will remain relational.

Local SPARQL endpoint

— To offer a common SPARQL endpoint for multiple distributed data sources and to enable the resolution of queries joining results from all of them.

03

P2P Network

OSS 2 OSS 3

Query

OSS 1

Who answer

s?

12TELEFÓNICA I+D


Requirements (II)

Bidirectional translation

— It is required to insert, update or delete data in the relational schemas from RDF data or SPARQL results, based on an semantic to relational mapping.

— The same mapping approach for both directions would be desirable.

— Complex problems: generation/work out of primary and foreign keys, identifying properties, data types compatibilities, fulfillment of constraints, data formats, etc.

03

Ontology

Relational BD

OSS 3

OWL SchemaMapping

Relational Data to RDF / SPARQL results

RDF / SPARQL results to Relational Data

13TELEFÓNICA I+D


Requirements (&III)

Support for morphologic transformations

— Origin and destiny data must follow coherent formats (i.e., capital letters).

— It must be provided mechanisms to define and transform morphologic properties.

Propagation of data changes

— Data is dynamic.

— There are different interaction mechanisms: push, poll, subscription…

— From the semantic condition to the relational database trigger.

Security

— There must be a control over which systems access every piece of data, and under which conditions.

03

14TELEFÓNICA I+D


Conclusions and future work

The objectives of the project have created great expectation on Telefonica’s OSS domain.

But there is a long road to go:

— Bidirectional mapping.

— Standardization of mappings.

— Federated data model based on ontologies alignment/merging.

At the end, we will be enabled to:

— Automate data acquisition processes.

— Automate network management processes based on stored information.

04

telefÓnica i+d date: 25th october 2007 sergio garcí á gómez ([email protected]) © 2007 telefónica...

Documents