ls, itg_pres.ppt, 20/06/01

An Architecture enabling spontaneous Wireless Services

An Architecture enabling spontaneous Wireless Services

Lars Schrixschrix@imst.de

IMST GmbH

June 21st, 2001

The WINE GLASS Ad-hoc Service Platform

ls, itg_pres.ppt, 20/06/01

Conventional Services Hierarchic service

structure C/S-Architecture Strict distinction

between provider and consumer role

Predefined service relationships

Closed platform Efficient support of pre-

installed networks Modest integration of

nomadic users

ContentProvider A

ContentProvider B

PlatformOperator

User A User B User C

Administrative Relation

Content Relation

ls, itg_pres.ppt, 20/06/01

Spontaneous Services

DefinitionDefinition Based on community of nomadic users (Service

Community), no C/S-Architecture No predefinition of provider and consumer role User-to-user relationship (Peer-to-Peer-Approach) Focus on user Open platform

ls, itg_pres.ppt, 20/06/01

Use Cases

Nomadic Scenarios– Mobile Office/Mobile Meeting– Ad-Hoc Location Services

Community Chat Infotainment Online Games

ls, itg_pres.ppt, 20/06/01

Service Community

Group of users willing to share services Network interconnection between users Service Community may be characterized by:

– Regional size– Access type– Type of interest– Efficiency– Terminal Type

ls, itg_pres.ppt, 20/06/01

Architecture

No pre-installed service infrastructure

Administrative tasks distributed among community

Administrative tasks– Discovery

– Lookup

– Neighbourhood

ExplorationAdministrative Tasks (Distributed)

Discovery, Lookup, Neighbourhood Exploration

Administrative Tasks (Distributed)Discovery, Lookup, Neighbourhood Exploration

Service AService A Service B(e.g. Mobile

Office)

Service B(e.g. Mobile

Office)Service C

(e.g. Printer)

Service C(e.g. Printer)

Accounting &Authorization

Accounting &Authorization

Network(e.g. OMAN)

Network(WINE GLASS Network)

ls, itg_pres.ppt, 20/06/01

Architecure II

User C

User A

User B

User D

User E

Community B

Lookup

Lookup

User F

ServiceProxy

Community A

Service Relation

Bridged Service Relation

Lookup Database Binding

ls, itg_pres.ppt, 20/06/01

Service Proxy

Bridging element between Service Communities

Service Proxies can be assigned dynamically, no static setup necessary

Service entities inherited from Service Proxy:– Content Provider (providing content from CMS)– Bridging User (accessing legacy services)

ls, itg_pres.ppt, 20/06/01

Discovery & Lookup Process

„Bootstrap“ for Service Communities Lookup Process distributed within Service Community Network requirements:

– Conventional Broadcast/Multicast (sub-optimal)– Regional announcement mechanism of future networks

Appropriate real network testbed available in

WINE GLASS project

ls, itg_pres.ppt, 20/06/01

Discovery Procedure

IPNotebook

PDA

WLAN

IncomingUser

WLANRegister

Discovery

Announce

ServiceProxy

ls, itg_pres.ppt, 20/06/01

Testbed Architecture

InternetIPv6

Ethernet

Administrative Domain A

Appl.Server

HA

UTRAN Emulator

DM-AP

WLAN subnet: Ethernet

PC 1( MT)Lower Layer

Emulator

Ethernet

RDM-AP

WLAN subnet: Ethernet

Intra -domain macro-mobility between access networks of the same type (Mobile IPv6)

Intra -domain macro-mobility between access networks of different types (Mobile IPv6)

TE

UTRAN Emulator

DECT

AD Backbone

IPv6Ethernet

UTRAN Emulator

R

R

R

IWU

PC 2R

EthernetEthernet

DM-B

DM-AP DECT Module acting as Access Point DM-B DECT Module acting as Bridge

Ethernet

Linux

Linux

RNC Emulated

ls, itg_pres.ppt, 20/06/01

RB & NPQ Architecture

IP Backbone

IP subnet 3

IP subnet 2

IP subnet 4

IP subnet 1

IP subnet 5

Geographical Location associatedto the corresponding IP subnetO

N

E

S

Subnet 1: Loc. 1; RB-proxy1Subnet 2: Loc. 2; RB-proxy2...Subnet 4: Loc. 4; RB-proxy4Subnet 5: Loc.5; RB-proxy5

Location Server

NPQ request and replyRB messages

Unicast

IPv6 multicast to theAll-Nodes address

RB proxies

IPv6 multicast to theAll-Nodes address

Unicast

Unicast

ls, itg_pres.ppt, 20/06/01

The End

Thanks for your attention