Contextualized Information-Centric Home Networking (draft-ravindran-cibus-01.txt) IRTF/ICN-RG (IETF-89) Ravi Ravindran,

1. Contextualized Information-Centric Home Networking(draft-ravindran-cibus-01.txt)IRTF/ICN-RG (IETF-89)Ravi Ravindran, Asit Chakraborti, G.Q.Wang

2. Current Home Networking Status • Usually single subnet scenario • Multiple subnets possible for better signal quality • Service discovery restricted to one subnet, require infrastructure multicast support for multiple subnet case. • Routing another requirement • Heterogenous systems are silo or costly integration • Climate Control (Honeywell), Video Surveillance (third party), Entertainment systems etc. • Security and Trust issues • Several non-interoperable standard: DLNA, Zigbee, Zwave, AllJoyn • No easy way to integrate them [1] • Lack unified Naming/Addressing or scheme • Homenet working group focuses on IPv6 enablement, and not on enabling intelligent home networks. [1] Colin Dixon et al, “An operating system for the Home”, NSDI, 2012

3. What should HomeNet focus on ? • Zero Configuration • Except for connecting to the closest access point authentication. • Easy to introduce heterogeneous devices/services • Any IoT things: Appliances, Cars, Thermostats, G-Glasses • Service inside or outside home • Policy Configurations • Home user should be able to configure service policies easily and enforce them. • Inter-connect services at will. • e.g. refrigerator should be able to create an event, and any other application/service should be able to consume and act on it. • Service composition should be integral • E.g. entertainment system should discover, lights/shades in room, and offer choices to compose it.

4. Why ICN is more apt ? • ICN can elevate home networking to a new level of experience. ICN features that helps Home Networking • Configuration-less: ICN can operate in configuration less mode. • Local interfaces (BT, Wifi-Di, etc) can be equally exploited as infrastructure ones (Wifi, LTE) • Homogeneity : Potential homogenous protocol working at different scale (BAN/PAN/LAN/WAN). • Distributed Intelligence: Distributed Caching/Storage, Computing, Bandwidth resources can be leveraged equally. • Low computing devices (terminals, appliances) and high power devices (Gateways, Internal Routers) can participate equally in information dissemination. • Security/Trust Models: Varying Security/Trust models can be applied based on application/service requirements. • Contextualization : Receiver oriented communication can augment context. • Service Composition: Service composition can be made easy as services can be discovered easily within local space or over infrastructure. • Multi-homing/Mobility Handling : Integral part of ICN design

5. Context Handling in Home Networks • Intelligent home networks have to adapt to various contexts. • Home devices (services) in/out • Foreign devices in/out • Device proximity (ad hoc versus infrastructure) • Device/Service Location in the home • Enabling new devices (appliances, sensors etc.) • User mobility to different rooms • Social context (Personal/Professional Groups) • Service adaptation to device change context • Service context changes (Spatial, Temporal) • ..and more

6. Policy Handling in HomeNets • Service Accessibility • Authentication/Authorization (Guest, Home members etc.) • Privacy • Service Scope • Limiting service to a specific local space • Time constraints • Service Reachability • Only local or Global from the Internet (e.g. setting thermostat) • Service Composition • The service has limitation on who can leverage it • …

7. Contextualized Information-Centric BUS (CIBUS) HomeNet Devices Applications Services [CIBUS API] Smart Grid Smart Health Smart Transport • CIBUS is a middleware that spans Terminals, Internal Routers, Gateways and/or into the network • CIBUS allows devices/applications/services to interact in a contextual manner CIBUS Service Management Context Monitoring Processing Name Management Policy Based Routing and Forwarding CIBUS [ICN API] ICN CIBUS Contextualized Adaptive MAC Layer Internet ICN Edge Cloud Services L2 (BT, Wifi-Di, Wifi, LTE, 802.15.4)

8. CIBUS Functions • Service Management • Policy based Discovery • Service Publication • Service Subscription • Service Notification • Content Query/Response Processing • Context Monitoring and Processing • Context Monitoring • Context Subscription • Context Notification • Name Management • Service Naming (Scope: local, Global) • Secure, Human Friendly • Policy Based Routing and Forwarding • Forwarding interests based on satisfying contextual/policy requirement • Heterogenous MAC Layer Adaptation • Contextualized Adaptive MAC Layer • Link Management • i/f Selection • MAC Encoding/Decoding/Data Rate/MTU

9. CIBUS API • CIBUS API • Service_Publish(Name, {context}, {Policy}) • Profile, Policies, Services • Service_discovery({filters(name ..)}, {Policy}) • Discover services which meet some policy requirements • For Home Nets, Service Discovery can also set the policy based reachability • Service_Subscribe(Name, {context}, {Policy}) • Subscribe to specific events (contents, context change etc.) • Service_Notify(Name, {context}, {Policy}) • Notify applications or services when a specific event or context change happens • Service_Policy(Name, {Policies}) • Triggered due to user or context change • Content_Primitive(Name, {context}, {Policy}) • Receive content request and respond by invoking the right service * Context and Policy changes with different scenarios and ecosystems such as Homnets, Smart Grid, Transport etc.

10. ICN API • ICN API • Certain Context and Policy enforcements can be applied in the ICN plane, e.g. multicast/broadcast, name-based firewall • Get (Name, {Context}, {Policy(routing-scope, security, ..)}) • Service_get(Name, {Context}, {Policy(…)}) • Seek service in the local or global scope • Content_get(Name, {Context}, {Policy(…)}) • Seek content that satisfies certain requirements • Put (Name, {Context}, {Policy(routing-scope, security, caching ..)}) • Service_put(Name, {Context}, {Policy(...)}) • Establish reachability while enforcing context, and policy requirements • Content_put(Name, {Context}, {Policy(...}) • Establish content reachability while enforcing context and policy to its accessibility

11. ICN Based HomeNet Prototype • A subset of CIBUS features is realized to demonstrate the flexibility ICN provides to handle heterogeneous radios, D2D and infrastructure communication modes. Scenarios: Health Monitoring Trusted D2D (Group-ID, Group Key) In-home Sensor Service CCNx over 802.15.4/Wifi/Infrastructure Trisha Biswas et al, “Contextualized information-centric Home networks”, SIGGCOMM, 2013

12. Conclusions and Future Actions • The draft presents at a high level functional view of a intelligent service layer over ICN to accommodate heterogenous Devices, Applications, and Services. • Requires standardization on Service profiles, Contexts, Policies representation and expression. • As a future ICN-IoT work item • Consider HomeNet as the ICN-IoT work item, formalize the middleware framework ? • Protocol design and CIBUS platform development ? • More complex use case HomeNet + Smart Grid + Health Care work item ?

13. Thank You