Fraunhofer FOKUS

Context Management in Dynamic Environments

IWCMC 2009, June 2009Jens Tiemann

Humberto AstudilloEvgenij Belikov

Fraunhofer Institute for OpenCommunication Systems

Fraunhofer FOKUS

2 Context Management in Dynamic Environments – IWCMC 2009

Overview

Motivation and Goal

Context Management using Context Coordination and Dissemination System (CCDS) Architecture/Protocol

Continuous Data Transport using IP Flow Information eXport (IPFIX) Architecture/Protocol

Composite Approach Location Context Source Location Context Service

Conclusion and Future Work

Fraunhofer FOKUS

3 Context Management in Dynamic Environments – IWCMC 2009

Motivation and GoalC

ontext-Awareness is key enabler of self-managementS

elf-x features facilitate seamless interaction between users, services and devices in heterogeneous mobile networks and dynamic environments

Increasing mobility due to widespread wireless networks and portable devices

Location Based Services

Tracking, monitoring, navigation, Virtual Fence

Guide-, recommender-, Social-networking-systems

Always Best Connected In-network management

Fraunhofer FOKUS

4 Context Management in Dynamic Environments – IWCMC 2009

CCDS Architecture (1)

Context-Management is crucial for fulfilling the requirements of highly dynamic mobile networks

CCDS provides infrastructure for context-awareness

init / config

data

control

ContextSource

Provider Consumer

Directory

Application /Context Usage

data

requests

CCDS

Fraunhofer FOKUS

5 Context Management in Dynamic Environments – IWCMC 2009

CCDS Architecture (2)

Components• Provider – interface to source of context/information• Consumer – aggregator or end-user of context• Directory – mediator between Providers and Consumers

Communication Models• Pull – based on requests from Consumer• Push – asynchrounous event-based notifications from Provider

Message types: resolve, register, get, subscribe, notify

Prototype implementation available

Suitable for handling high-level discrete data

Fraunhofer FOKUS

6 Context Management in Dynamic Environments – IWCMC 2009

IPFIX Architecture (1)

Network context is crucial for self-configuration and optimal performance of given network

IPFIX originates from network measurement/management• information model, transport protocol, architecture

Metering /Measurement

Exporter Collector

Application

IPFIX

Fraunhofer FOKUS

7 Context Management in Dynamic Environments – IWCMC 2009

IPFIX Architecture (2)E

merging IETF-standard (RFCs 3955, 5101)U

sed in network management and accounting systemsE

fficient implementation available

Components: • Exporter – source of measurement data• Collector – sink/user of measurement data

Push-based communication model

Binary encoding based on templates• Suitable for voluminous low-level continous data• Supports extension of data formats on-the-fly

Fraunhofer FOKUS

8 Context Management in Dynamic Environments – IWCMC 2009

Composite Architecture

CCDS used to control and configure IPFIX components

IPFIX is used to accomplish measurement tasks

Context Usage may further provide aggregated context

init / config

discrete data

continuousdata

control

Metering /Measurement

config

Exporter

Provider

Collector

Consumer

Directory

Application /Context Usage

Context Preparation Context Usage

data

data

requests

IPFIX

CCDS

Fraunhofer FOKUS

9 Context Management in Dynamic Environments – IWCMC 2009

Closer Look: Location Context Source

Capable of sensing and providing location context

Adds Quality of Context (QoC) to enrich the context sent

init / config

discrete dataover CCDS

continuousdata over IPFIX

config

Exporter

Provider

Location Context Source

CCDS addressing

CCDS control

Memory / Preprocessing

GPSReceiver

otherSensor

ContextUsage /DecisionProcess

Directory

Fraunhofer FOKUS

10 Context Management in Dynamic Environments – IWCMC 2009

Scenario: Location Context Service

Fraunhofer FOKUS

11 Context Management in Dynamic Environments – IWCMC 2009

Location-Context Service (2)V

irtual Fence scenarioM

obile entities equipped with location context sourcesL

ocation context is used to alert a monitoring component whenever some forbidden area is entered by an entity

Context-aggregators play hybrid role of acquiring preprocessed location context and providing meaningful higher level context information to the application

Application is decoupled from context management tasks

Generalized architecture is moreover applicable in different further scenarios briefly mentioned before

Fraunhofer FOKUS

12 Context Management in Dynamic Environments – IWCMC 2009

Conclusion and Future WorkC

ombination of CCDS with IPFIX network measurements standard in a proof of concept implementation

Proposed architecture is suitable for dynamic environments

Supports autonomic decision-making process with focus on self-management of network nodes

Further extension of libccds and libipfix

Introducing learning and history context utilization as further support for decision-making

Node Collaboration System Toward collaborative decision-making

Fraunhofer FOKUS

13 Context Management in Dynamic Environments – IWCMC 2009

Any Questions?

Thank you for your attention!

Contact: • evgenij.belikov@fokus.fraunhofer.de• jens.tiemann@fokus.fraunhofer.de

Info:• http://www.fokus.fraunhofer.de/go/ipfix• http://www.fokus.fraunhofer.de/go/ccds

Fraunhofer FOKUS

14 Context Management in Dynamic Environments – IWCMC 2009

CCDS Protocol

Pull

Push

Fraunhofer FOKUS

15 Context Management in Dynamic Environments – IWCMC 2009

Implementation DetailsB

oth libraries implemented in C (Java Interface available for IPFIX)

Event-driven programming• main loop• event types• event handling• message handling

text objects in XML alike format

CCDS: UDP (with response messages)

IPFIX: UDP, TCP or preferably SCTP

Fraunhofer FOKUS

16 Context Management in Dynamic Environments – IWCMC 2009

AcknowledgementThis work was partly performed in project E3 which has received research funding from the Community's Seventh Framework programme. This paper reflects only the authors' views and the Community is not liable for any use that may be made of the information contained therein. The contributions of colleagues from E3 consortium are hereby acknowledged.

E3 – End-to-End Efficiency

“Evolving current heterogeneous wireless system infrastructures into an integrated, scalable and efficiently managed B3G cognitive system framework.”

https://ict-e3.eu/

Fraunhofer Institute for OpenCommunication Systems

Kaiserin-Augusta-Allee 3110589 Berlin, Germany

www.fokus.fraunhofer.de

Jens Tiemannjens.tiemann@fokus.fraunhofer.de