Ing Electronico

Service-Centric Networking
Torsten Braun
Institut für Informatik und Angewandte Mathematik
Universität Bern
Bern, Switzerland
braun@iam.unibe.ch
Abstract— Content-centric networking is a novel paradigm for
the Future Internet. This paper argues that content-centric networking should be generalized towards a service-centric networking scheme. We propose a service-centric networking designbased on an object-oriented approach, in which content and services are considered objects. We show implementation architectures for example services and how these can benefit from service-centric networking.
Keywords: Content-Centric
Networking, Future Internet

I.

Networking,

Service-Centric

INTRODUCTION

Content-centric networking (CCN) is a networking paradigm for the FutureInternet, in which routing and forwarding
are based on content identifiers rather than on host identifiers.
The CCN approach provides several benefits over the existing
network architecture: the network provides full content identifier lookup functionality; content can be cached anywhere
along the delivery path allowing better network utilization;
content itself can be secured instead of theend-to-end connection that carries it. While CCN strongly focuses on content
retrieval, the Future Internet is expected to provide a more general support of services. Content delivery is merely one example of a service; other examples are content generation and
manipulation as well as general processing services. This trend
is also driven by cloud computing. In this paper, we propose aservice-centric networking (SCN) scheme as an extension of
CCN. In our design we consider both content and services as
key design elements. SCN supports a variety of services including file storage and retrieval, audio/video streaming and
recording, processing of stored images and video, on-line
shopping, location-based services, cloud computing, and telecommunication services.
After discussing relatedwork in Section II, Section III introduces the basic principle of SCN, illustrates its potential
benefits and discusses some example applications. Section IV
describes the object-oriented SCN rationale in detail. Section V
describes how two example applications, namely video rendering and audio conferencing, can be implemented based on
SCN. Finally, Section VI concludes the paper.
II.RELATED WORK

A. Content-Centric Networking
In their work on networking named content [1] the authors
propose a content-centric architecture based on forwarding

Volker Hilt, Markus Hofmann, Ivica Rimac,
Moritz Steiner, Matteo Varvello
Bell Labs, Alcatel-Lucent
Holmdel, USA
firstname.lastname@alcatel-lucent.com
Interest messages towards content. Interest messages are disseminated alongpossible paths where the requested content
might be located. When Interest messages reach a node holding
the content, the latter is returned to the requestor along the reverse path of the Interest messages constructed via bread
crumb routing. Since each Data message carries the name of
the encapsulated object, content can be cached by any router on
the delivery path and served from there uponthe reception of
an Interest message. CCNx™ is an open source project based
on the above scheme and using the naming convention described in [2]. In the following, we use the term CCNx for the
concept described in [1], since other content-centric networking approaches such as TRIAD [7] and DONA [6] exist. Consequently, we call an implementation of any CCN approach a
CCN infrastructure.
In [2],the authors propose a scheme to encode markers to
code functional components. These command markers with the
value of 0xC1 followed by "." do usually not appear in names.
Optionally, the operation name may be followed by arguments
delimited by tilde characters “~”. An operation name may be
constructed using a reversed DNS name. As an example
%C1.org.ccnx.frobnicate~1~37 would be a command...