Project Proposal: Internet of Things uxing XMPP

INTRODUCTION BACKGROUND XMPP EXTENDED PROTOCOLS PROJECT MILESTONES CONCLUSION

Project ProposalThe Internet of Things using XMPP

******** ********************* *******

April 23, 2014


TABLE OF CONTENTS IINTRODUCTION

BACKGROUND

Internet of Things (IoT)XMPP

XMPP EXTENDED PROTOCOLS

Base IoT ProtocolsExtra IoT Protocols

PROJECT

Research QuestionImplementationTests

MILESTONES

RealisticCaffeineAdderall

CONCLUSION


TABLE OF CONTENTS IIConclusion


IOT: DEFINITION

“The Internet of Things represents a vision in which theInternet extends into the real world embracing everydayobjects. Physical items are no longer disconnected from thevirtual world, but can be controlled remotely and can act asphysical access points.”[1]


IOT: PROBLEMS

I Lower PowerI ScalabilityI InteroperabilityI Rolling UpdatesI Security


PROBLEM: LOW POWER

I Good batteries don’t exist yetI Want any potential device to be able to connect to the

network and stay connectedI Physically small like a wrist watchI Limited battery space and mW hours with possibly

infrequent charging like an umbrella


PROBLEM: SCALABILITY

I Expected every person is connected to the InternetI Each person reasonable to have at least 5 devices

connected to the Internet at any given timeI Needs to scale to Billions of devicesI Layer 1 - 3 needs to be able to handle number of active

devices being routed and addressableI IoT protocols need to be able to be inherently cache-able,

distributable, and redundant


PROBLEM: INTEROPERABILITY

I Need to be able to communicate with functionallycompatible protocols

I Protocol needs to work on tiny devicesI Agnostic of Layers 1-3


PROBLEM: ROLLING UPDATES

I Even harder to change once as widely adopted as IPv4I Infinite backwards compatibility shouldn’t be expectedI Goal having the same quality of service as mainframes

with 0% downtime


PROBLEM: SECURITY

I PrivacyI AnonymityI Robust protocolI Fail close protocolI Semantics of protocol need to be as simple as possible not

Turing ComleteI Protocol pushes for better coding practices if where-ever

possible


XMPP

I Extensible Messaging and Presence ProtocolI Communications protocol for message-oriented

middleware based on XMLI Core Features

I Channel EncryptionI AuthenticationI Error HandlingI Communication primitives for messagingI Network AvailabilityI Request-Response interactions


XMPP: PROTOCOL OVERVIEW

1. Determine IP and port to connect2. Open TCP Connection3. Open XML Stream over TCP (TLS Optional)4. Authenticate using Simple Authentication and Security

Layer (SASL) mechanism5. Bind resource to the stream6. Exchange XML Data7. Close XML Stream and TCP Connection


XEP-0325: IOT CONTROL

I IoT requires all devices to have actuatorsI Devices that can be controlled through the network and act

as with outside worldI Example - Control door locks


XEP-0323: IOT SENSOR DATA

I Basic operations and data structures for sensor datacommunication

I Sensor networks contain many different architecturesI Temperature Sensor - Analog Value value with

precision/physical unitI Annoying censors on CSL doors - digital value (0 or 1)I XEP 0323 is designed to be simple due to different

architectures and scalability


XPE-0326: IOT CONCENTRATORS

I Used for concentrating management of a sub set of devices(usually sensors) to one point

I Devices will be of different makes and modelsI XEP 0326 has a small set of reduced operations for basic

maintenance and interoperabilityI Set of devices can be

I Small connecting all the windows in a houseI Medium all of the locks at a businessI Large all the devices at a college campusI Massive all of the sensors and actuators at a power plant

I ConvenienceI Ability to work with massive quantities of entitiesI Effective syncronization between interested parties


XPE-0324: IOT PROVISIONING

I Used for efficient management of access rights andprivileges

I What things can read data from what other things, andwhat data

I User Control and privileges But wait! Not all sensors canprovide a user interface to control privileges

I Distributed third partyI Provide rich user interface and configurable optionsI Control communication and available content Relies on

Sensor Data & Control XMPP ExtensionsI Example- Only the owner of the car may tell the car to start


XEP-0347: DISCOVERY

I Used for secure installation, configuration, and connectionof massive amounts of things

I Goal is for 0 configuration networkingI Trade off is simplicity vs security


RESEARCH QUESTION

Does the existing XEP IoT protocols solve the the majorproblems of IoT?


XMPP IMPLEMENTATION

I Use existing XMPP base codeI Implement XEP 0325 - ControlI Implement XEP 0323 - Sensor DataI Note: Protocols are experimental and were updated last

week.


TEST BED

I NS-3I Form of WAN and LAN emulation (e.g. CORE)


SCALABILITY TESTS

I Test overhead of protocol for dataI Test how many devices can simultaneously be connected

to one XMPP Server


SECURITY TESTS

I Test how identifiable a person/device is from plain textand TLS encryption

I Test where can privacy can be broken, most likelyassuming compromised server or concentrator


REALISTIC: MILESTONE 1

I Implement Sensor/Control XEPsI Scalability no concentratorsI Security anonymity and privacy no concentrators


CAFFEINATED: MILESTONE 2

I Implement ConcentratorI Test scalability improvements with concentratorsI Test Security with concentrators


CAFFEINATED: MILESTONE 3

I Implement ProvisioningI Test Scalability what additional traffic added?I Test Security what data is leaked by provisioning?


ADDERALL: MILESTONE 4

I Implement DiscoveryI Test Scalability what additional traffic added?I Test Security what data is leaked by provisioning?


CONCLUSION

Fin


COMMENTS & QUESTIONS

What do you think?


REFERENCES I

C. F. Friedman Mattern, “From the internet of computer tothe internet of things,” Distributed Systems Group.

Engineering

Project Proposal: Internet of Things uxing XMPP