Contextualized Information-Centric Home...
2
Contextualized Information-Centric Home Network Trisha Biswas † , Asit Chakraborti ‡ , Ravishankar Ravindran ‡ , Xinwen Zhang ‡ , and Guoqiang Wang ‡ † North Carolina State University, Raleigh, NC, USA. [email protected] ‡ Huawei Research Center, Santa Clara, CA, USA. {asit.chakraborti, ravi.ravindran, xinwen.zhang, gq.wang}@huawei.com ABSTRACT We deploy information-centric networks (ICN) to serve sev- eral applications including content distribution, vehicle-to- vehicle communication (V2V), home networks (homenet), and sensor networks. These applications require policy and context-based interaction between service producers and consumers. We visualize the ICN service layer as a contextu- alized information-centric bus (CIBUS), over which diverse sets of service producers and consumers co-exist. We de- velop a prototype and demonstrate several desirable features of ICN for homenets such as contextual service publishing and subscription, zero-configuration based node and service discovery, policy based routing and forwarding with name- based firewall, and device-to-device communication. Fur- thermore the prototype is applicable to both ad hoc and infrastructure settings, and can deal with diverse devices and services. Categories and Subject Descriptors C.2.1 [Computer-Communication Networks]: Network Architecture and Design; C.2.2 [Computer-Communication Networks]: Network Protocols—Protocol architecture General Terms Design Keywords Information-centric networks; content centric networking; home networks; named data networks; node discovery; pol- icy based routing; service discovery; zero-configuration 1. INTRODUCTION Several features provided by information-centric networks (ICN) [2] make it suitable for diverse application environ- ments such as home network (homenet), vehicle-to-vehicle (V2V), and Internet-of-things (IoT), including receiver-oriented Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage, and that copies bear this notice and the full ci- tation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the owner/author(s). Copyright is held by the author/owner(s). SIGCOMM’13, August 12–16, 2013, Hong Kong, China. ACM 978-1-4503-2056-6/13/08. communication, enforcing security policies at service, device, and content levels, and naming entities according to appli- cation requirements. These features make ICN suitable not only for existing applications such as content distribution, but also for emerging applications such as sensor or ad hoc networks. We envision ICN as a contextual information-centric bus (CIBUS) spanning diverse applications, over which context- aware interaction is enabled among service producers and consumers. Such interaction requires service framework over ICN to discover, publish, and subscribe resources, which dif- fer with the types of applications and contexts. This paper discusses CIBUS in homenet scenario. Among our contribu- tions, we design and develop light-weight name-based node and service discovery protocols overlaying ICN, which allows policy and context based interaction between distributed service producers and consumers. 2. CIBUS BASED HOME NETWORK A high level view of ICN based homenet architecture is shown in Figure 1(a). ICN supports primitives such as re- quest name-based services and content, name-based routing, in-network content caching, multi-homing and multi-path routing. We propose a service management layer allow- ing contextual auto-node and service discovery, and policy- based service publishing and subscription. ICN-based home- net provides the following novel features: (1) Being a name- based networking architecture, ICN-based homenet requires no configuration for local communication among producers and consumers, within and crossing router boundary, but service access over Internet requires ISP support; (2) The service management layer allows consumers to discover ser- vices based on their contexts. A home gateway learns ser- vices through the discovery process, expose APIs to manage service policies and compose rich new services; (3) With its configuration-less nature and support for various communi- cation modes such as 1:M and M:1, ICN can be used for various situations including sensor networks, achieving the objective of single network layer protocol in homenet; (4) Being receiver-oriented, ICN allows consumers to express contexts, and producers to generate appropriate responses, therefore enabling contextual communication; (5) ICN inte- grates security with data requests and responses, which can be bound at service, device, or content level. 2.1 Prototype The prototype setup is shown in Figure 1(b), where mul- tiple internal routers (IRs) are rooted to a home gateway 461
-
Upload
nguyenhanh -
Category
Documents
-
view
216 -
download
2
Transcript of Contextualized Information-Centric Home...
Contextualized Information-Centric Home Network
Trisha Biswas†, Asit Chakraborti‡, Ravishankar Ravindran‡,Xinwen Zhang‡, and Guoqiang Wang‡
†North Carolina State University, Raleigh, NC, USA. [email protected]‡Huawei Research Center, Santa Clara, CA, USA.
{asit.chakraborti, ravi.ravindran, xinwen.zhang, gq.wang}@huawei.com
ABSTRACTWe deploy information-centric networks (ICN) to serve sev-eral applications including content distribution, vehicle-to-vehicle communication (V2V), home networks (homenet),and sensor networks. These applications require policyand context-based interaction between service producers andconsumers. We visualize the ICN service layer as a contextu-alized information-centric bus (CIBUS), over which diversesets of service producers and consumers co-exist. We de-velop a prototype and demonstrate several desirable featuresof ICN for homenets such as contextual service publishingand subscription, zero-configuration based node and servicediscovery, policy based routing and forwarding with name-based firewall, and device-to-device communication. Fur-thermore the prototype is applicable to both ad hoc andinfrastructure settings, and can deal with diverse devicesand services.
Categories and Subject DescriptorsC.2.1 [Computer-Communication Networks]: NetworkArchitecture and Design; C.2.2 [Computer-CommunicationNetworks]: Network Protocols—Protocol architecture
General TermsDesign
KeywordsInformation-centric networks; content centric networking;home networks; named data networks; node discovery; pol-icy based routing; service discovery; zero-configuration
1. INTRODUCTIONSeveral features provided by information-centric networks
(ICN) [2] make it suitable for diverse application environ-ments such as home network (homenet), vehicle-to-vehicle(V2V), and Internet-of-things (IoT), including receiver-oriented
Permission to make digital or hard copies of part or all of this work for personal orclassroom use is granted without fee provided that copies are not made or distributedfor profit or commercial advantage, and that copies bear this notice and the full ci-tation on the first page. Copyrights for third-party components of this work must behonored. For all other uses, contact the owner/author(s). Copyright is held by theauthor/owner(s).SIGCOMM’13, August 12–16, 2013, Hong Kong, China.ACM 978-1-4503-2056-6/13/08.
communication, enforcing security policies at service, device,and content levels, and naming entities according to appli-cation requirements. These features make ICN suitable notonly for existing applications such as content distribution,but also for emerging applications such as sensor or ad hocnetworks.
We envision ICN as a contextual information-centric bus(CIBUS) spanning diverse applications, over which context-aware interaction is enabled among service producers andconsumers. Such interaction requires service framework overICN to discover, publish, and subscribe resources, which dif-fer with the types of applications and contexts. This paperdiscusses CIBUS in homenet scenario. Among our contribu-tions, we design and develop light-weight name-based nodeand service discovery protocols overlaying ICN, which allowspolicy and context based interaction between distributedservice producers and consumers.
2. CIBUS BASED HOME NETWORKA high level view of ICN based homenet architecture is
shown in Figure 1(a). ICN supports primitives such as re-quest name-based services and content, name-based routing,in-network content caching, multi-homing and multi-pathrouting. We propose a service management layer allow-ing contextual auto-node and service discovery, and policy-based service publishing and subscription. ICN-based home-net provides the following novel features: (1) Being a name-based networking architecture, ICN-based homenet requiresno configuration for local communication among producersand consumers, within and crossing router boundary, butservice access over Internet requires ISP support; (2) Theservice management layer allows consumers to discover ser-vices based on their contexts. A home gateway learns ser-vices through the discovery process, expose APIs to manageservice policies and compose rich new services; (3) With itsconfiguration-less nature and support for various communi-cation modes such as 1:M and M:1, ICN can be used forvarious situations including sensor networks, achieving theobjective of single network layer protocol in homenet; (4)Being receiver-oriented, ICN allows consumers to expresscontexts, and producers to generate appropriate responses,therefore enabling contextual communication; (5) ICN inte-grates security with data requests and responses, which canbe bound at service, device, or content level.
2.1 PrototypeThe prototype setup is shown in Figure 1(b), where mul-
tiple internal routers (IRs) are rooted to a home gateway
461
Climate
Control
Security
Surveillance
Entertain
ment
Custom
Apps
Apps
Service Management
(Name Based Auto- Node/Service
Discovery)
ICN
(Policy Based Routing/Forwarding)
L2
Devices
(a) ICN based homenet architecture.
App
BT
CCNx
Service
Proxy
NDP +
SPDP
ASP (Health
M it i
Smart Client
(Light/Accelerometer
i )
CCNx
CCNx
NDP +
SPDP
BT
Monitoring
Service)
HGw
ICN SP
PGwIR-1
sensing)
IEEE 802.15.4
CCNx
802.15.4
App
BT
ICN-SP
IR-2Consumer 1
Sensor Network
Wifi
Service NDP + Name
App
IR 2Consumer -1
(Local)
Consumer -2
(Remote)
Wifi
CCNx
Proxy SPDP Based
Firewall
Service
Management
NDP/SPDP App
CCNx NDP: Neighbor Discovery Protocol
SPDP: Service Publish and Discovery Protocol
IR : Internal Router
HGw/PGw : Home Gateway/Provider Gateway
CCNx
NDP/SPDPSocial
D2D
SHome Domain ISP
(b) CCNx based homenet prototype.
Figure 1: ICN based homenet architecture and prototype.
(HGw), and each is deployed with CCNx [1]. The HGwconnects to an ISP’s provider gateway (PGw). The IRsprovide gateway support to connected resource-constrainedsensors. The prototype demonstrates the following func-tionalities: (1) Home-wide zero-configuration through name-based neighbor and service discovery protocols across routerboundary; (2) Context and policy based routing and for-warding at the HGw/IRs, where routing tables are set asthe result of the service discovery protocol; (3) Name-basedfirewall at the HGw, where flows are inspected based on ser-vice names rather than ports and IP addresses; (4) Layer-2agnostic operations realizing end-to-end ICN operations overany L2 technology.
Zero-configuration discovery protocol: We developtwo name-based CCN protocols, namely, neighbor discoveryprotocol (NDP) and service publishing and discovery proto-col (SPDP). The objective of NDP is ad hoc and contextualassociation of devices, while SPDP allows efficient discoveryof services over ICN. Further details on these protocols canbe found in [3].
Policy-based routing: ICN-based homenet uses policybased routing and forwarding, wherein service entries in theFIB of the CCN router are a result of service discovery re-quested by consuming applications. In the HGw, a name-based firewall is realized by extending CCNx’s FIB logic tosubject incoming requests to policies associated with ser-vices. For example, if a service is marked for private access,i.e. valid only within the homenet scope, any interest fromoutside is dropped by the HGw.
Device-to-device communication: While demonstrat-ing the applicability of ICN towards different scenarios, ourprototype supports location based service publishing andsocial-aware device-to-device (D2D) interaction.
2.2 Demonstration ScenariosHealth monitoring service: In this scenario, a consumerdiscovers a health monitoring service through the HGw. Theuser then subscribes to this service. The interaction be-tween the consumer and the service results in another ser-vice instantiation on the consumer device, which makes thehealth monitoring data accessible to the healthcare serviceprovider. The consumer device service is published for pub-lic access.
Sensor service: A set of wireless sensor motes are de-ployed which generate data of temperature, light, and hu-midity. This data is made accessible through a sensor ser-vice. The service is proxied by the internal router (IR-1) asshown in Figure 1(b), and published for public access.
Trusted D2D interaction: This application demonstratesICN-based ad hoc trusted and social device-to-device inter-action. Two devices discover each other and their servicesthrough the neighbor and service discovery protocols. Dataaccess is restricted through group-ID based access control,and data confidentiality is enforced using a group key.
3. REFERENCES[1] CCNx code release, http://www.ccnx.org.
[2] B. Ahlgren, C. Dannewitz, C. Imbrenda, D. Kutscher,and B. Ohlman. A survey of information-centricnetworking. Communications Magazine, IEEE, 50:26 –36, 2012.
[3] R. Ravindran, T. Biswas, X. Zhang, G. Wang, andA. Chakraborti. Information-centric networking basedhomenet. In IFIP/IEEE ManFI Workshop onManagement of the Future Internet, May, 2013.
462
