Design Considerations on Data Oriented Communication Services for Future Network

Jinkyung Hwang Central R&D Lab. KT

Woomyun-dong, Seocho-gu, Seoul, 137-792, Korea Tel: +82-2-526-6830, Fax: +82-2-526-5759

E-mail: jkhwang@kt.com

Abstract— This paper investigates data-oriented communication services design for Future Network. We provide initial design considerations in terms of advantages and applicability with some use cases.

I. INTRODUCTION

One of the problems of the current Internet design is information sender-driven: they are overly trusted, and the network accepts anything that the sender wants to send and will make a best effort to deliver it to the receiver. This has led to increasing problems with unsolicited traffic (e.g. spam e-mail) and distributed denial of service (DDoS) attacks, forcing companies and users to conceal their e-mail addresses and place their systems behind firewalls [1].

Researches such as DONA [2], PSIRP [3] address those problems and the data oriented design can be one of the solutions for Future Network.

The data oriented architecture, which is also referred as publish/subscribe paradigm has been proposed as a remedy to the aforementioned problems facing the current Internet. Senders ‘publish’ what they want to send and receivers ‘subscribe’ to what they want to receive. Only when a subscription matches to a publication, the data is published to the subscriber. It is flexible, secure, and resilient and receiver-driven architecture.

This pub-sub paradigm is data oriented in that the main attention is ‘data’ to register and find. And it is event driven in that the ‘events’ of availability of the requested (subscribed) data is notified as it is published.

Typical data oriented applications are dissemination of information such as news, media broadcasting, messaging, etc. In this paper, we apply it to communications services such as ad-hoc audio conferencing, remote sensing, and autonomic network management services.

Future Network

Context server

User terminal

Network nodeServices server

SUBSCRIBE

PUBLISH

SUBSCRIBEPUBLISH

PUBLISHNOTIFY

NOTIFY

Fig.1. pub-sub data oriented Future Network concept

Fig.1 depicts the pub-sub based data oriented future network concept.

In this paper we investigate data oriented service network design for communications services. In Section II, design considerations are addressed. In Section III we provide use cases which will be the basis of the design requirements. We summarize in Section IV.

II. CONSIDERATIONS ON DATA ORIENTED COMMUNICATION SERVICES NETWORK DESIGN

The traditional communication model is client-server based. It is synchronous and sender driven: always sender initiated the communication. Compared to this, the data driven communication model is asynchronous and receiver driven: Only the data that the receiver is interested in is delivered at the instant it is available. This model has following advantages:

- instant and fast (real-time) communications model - secure communication (receiver oriented) - easy integration with existing data oriented services The pub-sub model may be employed in service level,

control level and/or transport level. The relevant event driven (pub-sub) technologies for each layer is shown in Fig 2.

Layer 3(Packet delivery & Routing)

Layer 4(Reliability, Flow control,

packet assembly)

Service component level pub-sube.g. ESB, CEP, WS-event

Network middleware levelpub-sube.g. OMG DDS, CORBA-event

Transport control level pub-sube.g. PSIRP, TRIAD

Layer 5(Operating System)

Layer 6(Application)

Transport level pub-sube.g. PSIRP, TRIAD

Fig.2. PUB-SUB technologies on each layer

In application layer 6, the service component level pub-sub

is mainly implemented by event based processing such as complex event processing (CEP), and web services. In layer 5, network middleware pub-sub such as DDS [4] and CORBA delivers data driven communications. In transport layer 4 and

978-1-4244-4522-6/09/$25.00 ©2009 IEEE ISCIT 2009481

3, the novel routing and forwarding with new ID mechanism [5, 6] proposed to replace current IP routing scheme.

Though technologies are different for each layer, the data oriented network design should allow each service network to select the best set of technologies of each layer: in some case, short and fast packet delivery is needed: in other case, large volume and reliable data delivery is essential.

Therefore we consider the following issues for future data oriented communication network design: l Cross layer networking: for flexible and optimized

communications l Event driven service composition: considering both

event and service model [7] l Real-time quality assurance: event driven is essential

for real-time communication l Various QoS support for different service networks l New data oriented business paradigm: considering

both socio-economic and technological viability.

III. USE CASES

In this section, we suggest three use cases for facilitating data oriented communications. Common conditions are as below.

- Preconditions: all nodes are equipped with pub-sub network middleware which may span layer 5 to 3.

- Actors: user terminals, network nodes or service systems.

A. Ad-hoc audio conferences - Description: User A, B and C make ad-hoc multi-party

conferences, and they are able to join or leave the conference at any time and any place.

- Sequences: 1. When users A and B are connected, user C finds

and joins the currently active conference of A and B.

2. As soon as C joined, he can have all conference data instantly.

3. The connection type may be N to N or centralized with audio mixer and distributors

Pub-Sub

AppPub-Sub

App

Pub-Sub

App

Pub-Sub

Mixer

Pub-Sub

Distr.

A B

C

…

Mixer Distributor

B. Remote Sensing service - Description: The sensing information collected from

various ‘things’ is processed in network and published as services. The user who is interested in the information subscribes them and receives only the necessary and processed information.

- Sequences: 1. When a user A arrives at an airport and turn on

the cell phone, he receives personalized welcome messages and location of baggage claim.

2. When a user A comes out of the airport, information of shuttle and hotel arrives to his cell phone.

Pub-Sub

App

Pub-Sub

Sensor app

Pub-Sub

Custom msg

Pub-Sub

Sensor app

A

Pub-Sub

MMS

Personalized service Hotel serviceAirport service MMS service

C. Autonomic Network Management Service - Description: Enterprise’s network facilities such as

routers and switches and network connectivity, traffic status, as well as storage and server’s usages are remotely monitored and supervised. When events of the failure or performance degradation occur, those are automatically notified and managed.

- Sequences: 1. Company K’s systems are under the remote

management by NMS. When failure occurs, the event is delivered to NMS center and it sends the appropriate controlling commands

2. Company K’s systems are overloaded and run over the threshold performance criteria. The event is delivered to NMS center and it instructs relevant commands.

Pub-Sub

Storage Configure mgr

Enterprise K’s system-1 MNS center

Failure mgr Quality mgrServersNetwork

Pub-Sub Pub-Sub…

Enterprise K’s system-N

StorageServersNetwork

IV. CONCLUSIONS

In this paper, we provides data oriented communications concepts and design considerations. The pub-sub event driven model enable receiver oriented, secure and instant communication. Three use cases are suggested for real world implementations. These are on-going work, and experimental results of the feasibility and performance expected to be available soon.

REFERENCES [1] Conceptual Architecture of PSIRP Including Subcomponent

Descriptions, PSIRP (Publish-Subscribe Internet Routing Paradigm), FP7-INFSO-IST-216173, DELIVERABLE D2.2, 2008, 8

[2] Scott Shenker, ‘A Data-Oriented (and Beyond) Network Architecture,’ SIGCOMM, 2007

[3] http://www.psirp.org/ [4] Data Distribution Service for Real-time Systems Version 1.2,

2007, OMG [5] Architecture Definition, Component Descriptions and

Requirements, PSIRP (Publish-Subscribe Internet Routing Paradigm), FP7-INFSO-IST-216173, DELIVERABLE D2.3, 2009, 2

[6] http://www-dsg.stanford.edu/triad/ [7] Sourish Dasgupta, et al, ‘Event driven service composition for

pervasive computing,’ IEEE International Conference on Pervasive Computing and Communications, 2009

482