Finger on the IoT Pulse: ‘Presence’ Functionality

We talk a lot about connecting, networking, and securing the Internet of Things, and the billions of devices spread across the globe. Another essential piece of the IoT puzzle is monitoring those devices, specifically with what we call presence. 

Presence functionality gives IoT developers a way to monitor individual or groups of IoT devices in realtime. Whenever the state of the device changes, the change is reflected in realtime to a dashboard, with an alert, or any other way you want to display your tracking.

What Can Presence Monitor?

As soon as you start streaming large volumes of data, or signaling and trigger actions to devices, you need to know what devices are connected. So what kinds of device states can you monitor with presence functionality? Pretty much anything you want! With Presence functionality, you can build out custom device states including:

• Online/offline status
• Device health
• Capacity for fleet management
• Total device count in field
• Battery/location status
• Machine status (eg. currently working on X task, driver driving/offline)
• Temperature and weather data from IoT sensors

With presence data, you can also log a history of device connectivity for audits and analytics. It’s not just about having realtime insight into your devices, but also tracking and logging performance, health, and other key metrics.

Why Is It Important?

Devices may get expensive: IoT devices can be expensive, so keeping tabs on your investment is essential. Device health presence monitoring gives you up to the millisecond health reports for device temperature, connectivity, battery life, etc, ensuring you that your device is 100% operational, all the time. And if any issues arise, you’ll know immediately that maintenance is required.

Devices may be imperative to operations/business: If IoT devices are at the core of business and operations, monitoring their health and status is paramount. Whether it’s agriculture readings, security sensors, or delivery fleet management, up to the millisecond device status can make or break a business.

Device Analytics: Accurate and up to date statistics and analytics is important to any IoT application or business. Presence functionality can store, retrieve, and playback collected analytics, for example, to give a history of device connectivity or health for audits.

Machine-to-Machine and IoT Use Cases for Presence

As we know, connected devices come in all shapes and sizes. And as IoT devices get smarter, more connected, more secure, and faster, they’re use in the field is skyrocketing across the globe. And as we add more devices into the field, realtime presence functionality is just as important as our device networks and IoT security.

Agriculture: As with other connected technologies, the Internet of Things has found heavy adoption in the agricultural industry. Sensors and monitoring devices for temperature, irrigation, weather patterns, and harvest management give farmers a realtime, accurate data stream, giving them full control over their agriculture system. As a result, keeping tabs on their vast system of IoT devices with presence functionality is key.

Connected Car/Shipping & Freight: Smart cars are shifting IoT boundaries and constitutes a disruptive and transformative environment. Connected car represents a large number of IoT use cases for automobiles including taxi, fleet management, shipping and freight, and delivery service. Connected cars require a secure and reliable connection to counter the various roadblocks that arise in the wild, such as constantly changing cell and network towers and dropped connections.

For taxi, shipping, freight, and delivery management, custom presence functionality is a vital component of the business, providing realtime custom vehicle and device states, such as vehicle and cargo capacity, location data, and device health.

Home Automation: We’re well aware that our homes are getting smart. It seems today, every appliance has an IP address. It’s safe to say that the smart home market is prepared to take the world by storm. Especially for applications that enable users to control their homes remotely, presence functionality is essential. In the smart home, presence gives users a realtime view of their devices status (lights on, doors locked, water leak, thermostat, fridge temperature, etc). And that’s the basis of a solid home automation solution.

Presence on the PubNub Data Stream Network

PubNub Channel Presence is one of the core features of the PubNub Data Stream Network. It enables developers to add user and device detection to their web, mobile, and IoT applications, giving realtime instant detection and notification of user/device status. Built on the global PubNub Data Stream Network, no matter where the devices are located, you can get an accurate and reliable reading on any custom device state you want.

For a quick tutorial on using Presence for IoT devices, whether it’s a network of 1000 connected devices or a single Arduino, check out our blog post: Realtime IoT Monitoring for Devices with PubNub Presence.

The Internet of Things and energy conservation

Humans are creative, and adaptive. We’ve done it all our lives, and all our existence. We needed more food, and so we created agriculture. We needed to live together, and so we created architecture. We needed to communicate, and so we created hundreds of ways to do just that; Internet, mobile telephone networks, computers. We are so fond of computers that we have them everywhere, often without noticing them. Yes, you might have a bulky desktop computer at home, or maybe even a flashy new laptop, but those are not the only computers. Your mobile telephone is a computer, but technically, so is your microwave, your car, your television set, and even your washing machine.

Our lives have changed greatly. We’ve all seen pictures and even films of medieval castles, and we know how we used to live. Today, our lives are made more comfortable by scores of machines; when was the last time you washed your clothes by hand? The clothes go in the washing machine, then in the dryer, and then in the cupboard. This all comes at a cost; financially, of course, but also in terms of energy.

Energy. The art of creating electrical power and delivering it to our homes and cities. For most people, this is as simple as having overhead power lines here and there, and paying a bill at the end of the month. Unfortunately, it is much more complicated than that. Power stations require scores of people to operate, and something surprising, data. In France, we have “too many” power stations, and most run at low capacity. When it gets hot, those who have air conditioning like to put it on, consuming electricity. Multiply that by a few thousand, and you get an idea of how much energy the power station needs to produce. When it gets cold, people like to heat their homes and businesses, and since everyone has radiators, electrical consumption soars. Imagine the amount of radiators an entire city can contain, and imagine even 50% of them turned on at the same time. Imagine.

Data is needed from other sources, not just from the weather. Imagine the amount of power required to let all the football fans watch the world cup. Our problem is that we can generate electricity, but we cannot store it (at least, not on this kind of scale). When everything gets turned on, the power station must be able to respond. If it can’t, bad things happen; the lights dim, or sometimes everything goes dark. We now know we cannot live without electricity.

We all know that we need to reduce our energy dependence, even if some of us don’t want to. To make more people aware, some cities turn off all the lights for an hour. It’s called Earth Hour. For one hour, people are encouraged to use as little electricity as possible; turning off the lights, for example. This does have an impact, but it is a double-edged sword. For one hour, the electricity usage drops considerably, while everyone thinks about the planet, and what we will leave behind for our children. At the end of the hour, everything goes back on, and this is where things get tricky. When electrical devices are first turned on, some can generate what is called an energy spike; a large consumption at first, before something more stable. It is visible just after Earth Hour, but it actually happens every day.

Peak hours. In my house, my electric water heater is connected to a peak-hour detection system. At 11:30 PM, my electricity provider starts “off-peak” hours, a time where electricity costs less. It costs less, an incentive to make me use power-hungry devices at a time when other devices are not needed. At this time of night, most businesses are closed, and so there is less demand. It is all about normalizing energy requirements, and to stop peaks during the day. At 7:30 AM, peak hours start, the water heater turns off, businesses start up, and my kettle turns on, the day is about to begin.

Energy is available, that isn’t the problem. Our problem is our use of energy. If only we had a way of using energy when it was available. Imagine, a certain amount of energy available. When I need light, I want my light to be usable immediately. I need a start time; now. However, when I put my clothes in the washing machine generally, I need them to be ready for the next day. I need and “end” time; I need the device to get the work done before a certain time. When will the washing machine start? Well, I don’t actually mind when it starts, and this is where I need help. This is where the IoT can help us, because we really need help.

The IoT will give us millions of connected sensors. This will also supply us with data, lots and lots of it. Why wouldn’t a small device in my house have direct control over my washing machine, or even better, actually be inside my washing machine? It could be programmed to start at a specific time, talking to other devices on the energy grid? Or even in my home; it could tell the water heater to wait until it has finished, and then the water heater gets its chance. The possibilities are endless.

IoT will give us an incredible amount of data, and data that can be used to help up control, and maybe even overcome our need to energy. But wait a minute, doesn’t the IoT itself need energy? It does, but the amount of energy that it will save outweighs the amount of energy it uses, and by a large factor. Take, for example, Atmel’s SAM D21 microcontroller. It uses less than 70µA per MHz, and that is when it is running at full speed. Of course, these devices have advanced power management, and with careful coding, they can last for months on cell batteries. Low power does not mean no power; it has enough flex to get the job done, and more. With built-in USB, ADCs, DACs and enough RAM and ROM for the most complex programs, it gets the job done. It also has the Atmel Event system, a powerful system that lets the microcontroller react to external events without the need to constantly look at inputs.

We need a little help in our lives to make simple decisions; when should I turn the heating on? When is the best time to turn on the air conditioner? We think we know, but we don’t. IoT will allow us to know exactly when the cold weather is coming. IoT will know when to turn the lights off. In short, IoT will generate enough data that it will know better than us what to do, and when. What we have seen so far is only the beginning.

The Microcosm of IoT and connected cars in Formula 1 (Part 2)

…Continued from The Microcosm of IoT in Formula 1 (Part 1)

The typical F1 racing car embodies the sophisticated engineering — designed to win and only but win. The racing platform itself (both team, driver, and car) executes every deductive decision vetted against one pillar called “performance.”

Here’s the quantified car and driver. At 1.5 gigabytes of data wirelessly transmitted per connected car during a race, the ECU (electronic control unit) generates 2-4 megabytes per second of data from the F1 cars’ 120+ various sensors, which also include the drivers’ heartbeat and vitals.  Now let’s add the upgraded network fiber deployed across each race of the year set forth to ensure every turn and tunnel can stream and broadcast this telemetry and data.

Source: ESPN Formula 1 News Computers, Software, and BI [Visualization and Data]

These embedded systems comprise of technology not limited to neither automotive nor Formula 1; embedded systems are used in the aero industry, marine, medical, emergency, industrial, and in the larger home entertainment industry. Therefore, advanced technology, little by little take place in the devices that we use every day. There are many useful products that are used in the industry — even though they first surfaced — as an application in F1 racing [the proven, moving lab].

F1 electronic devices used may be generally regarded in groups [using embedded systems] by the following:

Source – nph / Dieter Mathis/picture-alliance/dpa/AP Images

Here is an example Formula 1 steering wheel. It’s the embedded electronic enchilada, serving information [resulting from actuators and sensors] to a driver [on a need to know basis]. The driver coincides his race style and plan [tire management, performance plan, passing maneuvers, aggressive tactic] to every bit of data and resulted in a formatted display. These are literally at his fingers.

What are some of the F1 connected car implications?

Drivers in Formula 1 have access to functionality through their race platforms, which helps improve speed and increase passing opportunities. The DRS (Drag Reduction System) helps control and manage moveable rear wing. For a driver, in conjunction with Pirelli tires and KERS, it has proven successful in its pursuit of increasing overtaking which is all good for the fan base and competitive sport. The DRS moves an aerodynamic wing on a Formula 1 race car. When activated via the driver’s steering wheel, the DRS system alters the wing profile shape and direction, greatly reducing the drag on the wing by minimizing down force [flattening of the wing and reduce drag by 23%.]. Well, now coupled with the reduction in drag, this enables faster acceleration and a higher top speed while also changes variably the driving characteristics and style for over-taking. These are called driver and protocol adjustable body works.

How it works? Like all movable components of an F1 pure breed, the system relies on hydraulic lines tied to embedded control units, and actuators to control the flap. Managed by a cluster of servo valves manufactured by Moog, the Moog valves are interfaced via an electronic unit receiving a secure signal from the cockpit. Of course, this all happens under certain circumstances. When two or more cars pass over timing loops in the surface of the track, if a following car is measured at less than one second behind a leading car it will be sent a secure signal [encrypted then transmitted via RF] that will allow its driver to deploy the car’s active rear wing. Since the timing loops will be sited after corners, drivers will only be able to deploy the active rear wing as a car goes down a specific straight paths in many tracks.  In essence, the modern day Formula 1 car is a connected platform dynamically enabled to produce a stronger driver, appealing more to both driver performance and fan engagement.

Moveable aerodynamic components are nothing new. But still, for an Airbus A320 or even a modern UAV or fighter jet, there is a huge amount of space to work in. On a grand prix car, it’s quite different. This is also achieved in a very hyper fast, mobile, and logistically drained environment of Formula 1, where performance, equipment, and configuration are a demanded at all times. Next we’ll summarize how this relates to the broader connected car concept…

F1 showcases the finer elements of connected cars, making it possible

Just discussed, cars in general are going to become literally the larger mobile device. They will be connected to all sorts of use-cases and applications. Most importantly, we are the drivers, and we will become connected drivers. Both driver and connected car will become more seamless.

The next phase where smart mobility is going to change how we do and behave after we before or after we reach our destination. In Wired Magazine’s column named Forget the Internet of Things: Here Comes the ‘Internet of Cars’, Thilo Koslowski discusses the improvements and why connected cars are inevitably near. Thilo, a leading expert on the evolution of the automotive industry and the connected vehicle says, ““Connected vehicles” are cars that access, consume, create, enrich, direct, and share digital information between businesses, people, organizations, infrastructures, and things. Those ‘things’ include other vehicles, which is where the Internet of Things becomes the Internet of Cars.”

Yes, for the connected car, there still exist a number of technology challenges and legislative issues to build out a successful broader impact. Like Formula 1, we attribute many of its tech surfacing into main stream markets [previously discussed in part 1]. This next automotive revolution stems on current and related industry trends such as the convergence of digital lifestyles, the emergence of new mobility solutions, demographic shifts, and the rise of smartphones and the mobile internet.Thilo further claims “As these vehicles become increasingly connected, they become self-aware, contextual, and eventually, autonomous. Those of you reading this will probably experience self-driving cars in your lifetime — though maybe not all three of its evolutionary phases: from automated to autonomous to unmanned.”

Actually, a consumer shift is happening. Consumers now expect to access relevant information ranging from geo location, integration of social data, way points, destination, sites of interest, recommendations, ones digital foot print integrated into the “connected car” experience. The driver will become connected with all the various other touch points in his/her digital life. Moreover, this will happen wherever they go — including in the automobile. Thilo even goes to as far as claiming, “At the same time, these technologies are making new mobility solutions – such as peer-to-peer car sharing – more widespread and attractive. This is especially important since vehicle ownership in urban areas is expensive and consumers, especially younger ones, don’t show the same desire for vehicle ownership as older generations do.

To be successful, connected vehicles will draw on the leading technologies in sensors, displays, on-board and off-board computing, in-vehicle operating systems, wireless and in-vehicle data communication, machine learning, analytics, speech recognition, and content management. (That’s just to name a few.) “

All together, the build out of the connected car, [aspects proven in F1], contributes considerable business benefits and opportunities:

•  Lowered emissions & extended utility of EVs — remote Battery swap stations, cars as (Internet as a service), peer to peer car sharing, cars with payment capabilities, subscription of energy, vehicles as power plants back to the grid, KERS, and other alternative fuel savings displaced with electrical motors and emerging consumer conscience accountability to clean energy
• New entertainment options — countless integration opportunities with mobile (M2M and IoT) ecosystem of value added connected Apps and mobile services (i.e. Uber disrupted an old traditional market)
• New marketing and commerce experiences — countless use-cases in increasing the engagement and point of arrival offerings
• Reduced accident rates — albeit found in crash avoidance systems, location based services, driver monitoring, emergency response automation, early warning automation, telemetry to lower insurance cost, or advanced assisted driving
• Increased productivity — gains achieved via efficiencies/time management towards more sustainable commutes
• Improved traffic flow — efficient system merging various datasets to advance navigation to minimize and balance capacity or re-route traffic

Like all technology, old ideas will progress, evolve to newer platforms to bring new functionality that can adapt to the latest popular ecosystem [simply being mobile & connected]. Connected cars will expand automotive business models augmenting new services and products to many industries — retail, financial services, media, IT, and consumer electronics. The traditional automotive business model can be significantly transformed for the betterment of the consumer experience. Today, emphasis is placed much purely on the  output, sale, and maintenance of a vehicles.  Later on, once connected cars reach market maturity with wide adoption, companies will focus on the sum of business opportunities [value add chain ecosystem] leveraged from the connected vehicles and the connected driver.

Are you a product maestro or someone with domain expertise for your company seeking to improve processes or developing value added services to build IoT enabled products? Perhaps, you are in a vertical intended to accelerate business and customer satisfaction? With all this business creation stirring up, it’s quite clear the connected car platform will open new customer connected services or product enhanced offerings.

That all being said, we are already in this moment of the future with Formula 1. Connected cars will eventually come. It’s just a matter of time…

(Interested in reading more? Don’t forget to check out Part 1.)

5 challenges of IoT connectivity

At last month’s MIT Technology Review Digital Summit, PubNub CEO Todd Greene discussed the importance of connecting Internet of Things embedded devices on a reliable and secure realtime network. CPU, battery, and bandwidth consumption, as well as security are all paramount considerations that need to be taken into account when connecting low-powered embedded devices.

You’ll find that when developing and networking Internet of Things devices in the lab, connectivity is fairly seamless. You may have a few embedded devices connected to a backend server, so latency isn’t an issue.

However, deploying that IoT app on a global scale, to thousands or even millions of users simultaneously, is a whole other ball game. Unfortunately, the Internet isn’t just one big network, but rather is composed of an infinite amount of heterogeneous networks, including proxy servers, firewalls, cell towers, and WiFi networks, all slower and faster than one another.

As a result, there are 5 major challenges when it comes to Internet of Things connectivity. Keep scrolling down to see them, or watch the video below:

At PubNub, we think a lot about IoT connectivity and how we can make it as reliable, secure, and fast as possible. So to make PubNub the best network for connecting and signaling between Internet of Things devices, we first had to understand the challenges of doing so. Presenting the 5 challenges of IoT connectivity:

1. Signaling

When connecting IoT embedded devices, you need to start with bidirectional signaling to collect and route data between devices. Whether it’s embedded devices talking to a server to collect data, or devices signaling one another, you need to stream IoT signals and data quickly and reliably. You need to be 100% sure that that stream of data or signal is going to arrive at its destination every time.

2. Security

Security is a huge umbrella, but it’s paramount in Internet of Things connectivity and should be forethought, not an afterthought. For example, what good is a smart home if anyone can open your garage door? Here are three considerations for IoT security:

• Authorization: When publishing or subscribing to stream of data or IoT signal, it’s essential to make sure that the IoT device or server has proper authorization to send or receive that stream of data.
• Encryption: You need end-to-end encryption between devices and servers.
• Open ports: An IoT device is dangerously vulnerable when it’s sitting and listening to an open port out to the Internet. You need birectional communication, but you don’t want to have open ports out to the Internet.

3. Presence Detection

Who’s there, (or in terms of IoT, what device is there)? It’s important to immediately know when an IoT device drops off the network and goes offline. And when that device comes back online, you need to know that as well.

Presence detection of IoT devices gives an exact, up to the second state of all devices on a network. This gives you the ability to monitor your IoT devices and fix any problems that may arise with your network.

4. Power consumption

IoT embedded devices are small and expensive, so CPU and power consumption need to be considered. When you have hundreds or even thousands of devices sending data and signaling one another, it takes a toll on power and CPU consumption. You need to maximize efficiency while minimizing power and CPU drain.

5. Bandwidth

In addition to power and CPU, bandwidth consumption is another challenge for IoT connectivity. Bandwidth on a cellular network is expensive, especially with hundreds of thousands of IoT devices on a network sending request/response signals to your server.

That’s a huge server issue and a requires a large scale server farm handling all this data. You need a lightweight network that can seamlessly transfer data between devices and servers.

Connecting IoT Devices with PubNub

Connecting devices in the lab is one thing, but once they’re out in the wild, it’s a whole new ballgame. So where do you start? Having a scalable IoT network to connect embedded devices and servers is especially critical for IoT applications with a large user base.

These are the types of Internet of Things challenges we’ve solved at PubNub. With over two hundred million connected devices connected to our global realtime network in fourteen data centers, we average 50 to 60 thousand transactions per second, peaking at over 3 million. PubNub is used to stream data and signal for hundreds of different IoT uses cases including:

• Automotive: Connected cars need a realtime communication layer to stream data and signal between their fleet, dispatch, and the consumer on the app. Examples: Sidecar, Lyft, Easy Taxi, Gett, Zoomy
• Home Automation: A realtime network can be used to signal and trigger actions for smart devices and home automation solutions. Examples: Insteon, Revolv, Vivint
• Wearables: IoT wearables require a low latent, lightweight network to stream data between the device and a server. Battery, CPU, and bandwidth consumption are all important considerations that must be taken into account. Examples: 3rd Eye

By 2020, it’s estimated that there will be between 20 and 30 billion connected devices on the Earth. As a result, how we connect those devices should take precedence as the IoT field grows exponentially.

1:1 Interview with Michael Koster

---

Three-part Interview Series (Part 2)

---

Series 2 – IoT Toolkit and Roadmap

Tom Vu (TV):  What is in the roadmap for IoT Toolkit?

Michael Koster (MK):

The IoT Toolkit is an Open Source project to develop a set of tools for building multi-protocol Internet of Things Gateways and Service gateways that enable horizontal co-operation between multiple different protocols and cloud services. The project consists of the Smart Object API, gateway service, and related tools.

IoT Smart Object Structure

The foundation of the platform is purely bottom up, based on applying best practices and standards in modern web architecture to the problem of interoperability of IoT data models. I believe that the practice of rough consensus and running code results in better solutions than a top-down standard, once you know the basic architecture of the system you’re building.

To that end, I created a public github and started building the framework of the data model encapsulations and service layer, and mapped out some resourceful access methods via a REST interface. The idea was to make a small server that could run in a gateway or cloud instance so I could start playing with the code and build some demos.

The next step is to start building a community consensus around, and participation in, the data models and the platform. The IoT Toolkit is a platform to connect applications and a mixture of devices using various connected protocols.  It’s real power lies in its broader use, where it can span across all of our connected resources in industry, ranging from commerce, education, transportation, environment, and us. It’s a horizontal platform intended to drive Internet of Things more widely as an eventual de facto standard, built for the people who are interested in building out Internet of Things products and services based on broad interoperability.

IoT Applications Run on Cloud or On Gateway

We intend to create a Request For Comment (RFC), initiate a formal process for the wider Internet of Things platform and standards.  An community agreed upon process similar to the world wide web that we use today, based on rough consensus and running code, with RFCs serving as working documents and de facto standards that people can obtain reference code, run in their system to test against their needs, and improve and modify if necessary, feeding back into the RFC for community review and possible incorporation of the modifications.

The Internet of Things interoperability platform stands as an ideal candidate, leveraging the power of the open source community’s development process.  In turn, community involvement is taken to a new level, across many fields of discipline, and in many directions. Here is where we can get the most benefit of an agile community.  Crowdsource the development process based on principles of open communication and free of the need for participants to protect interests toward proprietary intellectual property.

We need to build the platform together meshed around the community of Makers, DIY, Designers, Entrepreneurs, Futurist, Hackers, and Architects to enable prototyping in an open ecosystem.  Proliferation then occurs; a diverse background of developers, designers, architects, and entrepreneurs have many avenues of participation. They can create a new landscape of IoT systems and products.

This broad participation extends to industry, academia and the public sector.  We are aiming for broad participation from these folks, build a global platform based on common needs. As a member of the steering committee, when I participated in the IoT World Forum, I heard from the technical leaders of enterprise companies (Cisco and others), research departments, and IoT service providers. They believe an open horizontal platform would be needed to enable applications that span across their existing vertical markets and M2M platforms.

Instead of a top-down approach, where people from corporations and institutions get together in a big meeting and put all their wish lists together to make a standard, we’re taking an overall bottom-up approach, bringing together a diverse community ranging from makers to open source developers, and entrepreneurs. Together with corporations, academia, and public sector, we all will participate in a very broad open source project to develop a platform that can be ubiquitous that everyone can use.

In many ways, this is modeled after the Internet and World Wide Web itself.  As we need to create a more formal standard, it will likely engage with the IETF and W3C. A good example is the semantic sensor network incubator project, which is an SSN ontology that describes everything about sensors and sensing. This enables broad interoperability between different sensor systems and platforms, based on common data models and descriptions. What we want to do is something similar to that, only on a more comprehensive scale and intended for the Internet of Things.

Tom Vu (TV):  Can you take us through a tour of the Data Object model importance and how it yields significance for simple and sophisticated connected devices?

Michael Koster (MK):

The Internet of Things today consists of many different sensor networks and protocols, connected to dedicated cloud services, providing access through smartphone and browser apps. It is rare for these separate “silos” to cooperate or interact with each other.

We abstract the complexity of sensor nets connecting devices and hardware by adding a layer of semantic discovery and linkage. This enables the sensors and actuators on disparate sensor nets to be easily combined to build integrated applications.

The way this works is using a few techniques. First, the different sensor nets are integrated through a common abstraction layer. This works a lot like device drivers in an operating system, adapting different devices and protocols to a common system interface. Only in this case, they are adapted to a common data model.

The common data model for sensor nets is based on the new IETF CoRE application protocol and sensor descriptions. This provides standard ways for common types of sensors to be discovered by their attributes, and standard ways for the data to be linked into applications, by providing descriptions of the JSON or BSON data structure the sensor provides as it’s output.

We use the W3C Linked Data standard to provide web representations of data models for sensor data and other IoT data streams. Linked data representations of IETF CoRE sensor descriptions are web-facing equivalents of CoRE sensor net resources. Linked data provides capabilities beyond what CoRE provides, so we can add functions like graph-based access control, database-like queries, and big data analysis.

Internet Smart Object

Internet of Things Applications are essentially graph-structured applications. By using Linked data descriptions of JSON structures and the meaning of the data behind the representation, we can create applications that link together data from different disparate sources into single application graphs.

Then we enable the platform with an event-action programming model and distributed software components. The common semantic language enables the data sources and software components to easily be assembled and make data flow connections. The result is an event-driven architecture of self-describing granular scale software objects. The objects represent sensors, actuators, software components, and user interaction endpoints.

Interent of Things with FOAT Control Graph

Tom Vu (TV):  Who and what companies should be involved?

Michael Koster (MK):

Whoever wants to participate in the building out of the Internet of Things. The people that use the infrastructure should build it out; the people who want to provide products and services based on interoperability, along with those who provide the backplane of thinking low power microcontrollers / microprocessors, connected sensors, and importantly the network infrastructure.

We want to enable all avenues of participation to allow corporations, academia, policy and standards makers, entrepreneurs and platform developers, makers, and DIY hackers all to be involved in building the platform as a community.

For corporations, we will provide an important role, to build a vendor-neutral platform for data sharing and exchange, an open horizontal platform that will allow the integration of what were traditionally vertical markets into new horizontal markets.

Anyone participating or expecting to participate in the emerging Internet of Things, Internet of Everything, Industrial Internet, Connected World, or similar IoT ecosystems initiatives, could benefit by participating in creating this platform. Companies that provide network infrastructure and want to build in value add can adopt this standard platform and provide it as infrastructure. Companies that want to provide new services and new connected devices that can use the IoT Toolkit to easily deploy and connect with existing resources could benefit.

All companies, organizations, and people that can benefit from an open Internet of Things are welcome to participate in the creation of a platform that everyone can use.

Tom Vu (TV):  How important is Open Source to Internet of Things evolution?

Michael Koster (MK):

I don’t see how the Internet of Things can evolve into what everyone expects it to without a large open source component. We need to go back to Conway’s law and look at it from both the system we’re trying to create and the organization that creates it. Interoperability and sharing are key in the system we want to create. It’s only natural that we create an open development organization where we all participate in both the decisions and the work.

Removing the attachment of intellectual property, changes the dynamics of the development team, keeps things engaged and moving forward solving problems. It’s important for software infrastructure projects like this to remove the barrier to cooperation that arises from the self-protection instinct around proprietary Intellectual Property, or even egoism associated with soft intellectual property, “my” code.

Instead, we turn the whole project into a merit-based system as opposed to being ego driven.  Rather than worry about guarding our property, we are motivated to solve the problems and contribute more to the deliverable. The limits to participation are removed and there is a more rapid exposure of intentions and goals. Engagement and innovation can rule in this environment of deep collaboration.

Tim Berners-Lee said that he was able to achieve the creation of the World Wide Web system because he didn’t have to ask permission or worry about violating someone’s copyright. We are creating the same environment for people who want to build our platform, and even for those who want to build their services and applications on top of the platform.

We are going to create the service enabled layer as open source as well so that any one of the companies can help proliferate the idea and everyone has influence and access to the development of the underlying IoT platform.  If it’s open source infrastructure and platform software, you can make a service on top of that software that can contain proprietary code. With our license, you can even customize and extend the platform for your own needs as a separate project.

Tom Vu (TV):  Describe your work with the EU IoT organization and how you are involved as a voice for the Internet of Things?

Michael Koster (MK):

I work with the IoT Architecture group within the overall EU Internet of Things project. The IoT-A group is closely related to the Future Internet project. They have an Architecture Reference Model describing different features one might build in an IoT platform, a sort of Architecture for Architectures. Since their process mirrors my own design process to a large extent, I found their reference model to be compatible with my own architecture modeling process.

They are conducting a Top-Down activity, stewarding the participation in the architecture and standardization model.  One of the ways I work with IoT-A is to use the Smart Object API as a validation case for the Architecture Reference Model. They are building the reference model top down, and we’re building the architecture bottom-up, based on a common expression of architecture relationships and descriptions.

I am also involved in advocating open source of IoT and building of local IoT demonstrator projects, educating around IoT, open data, etc. as well as user controlled resource access and privacy.  I am providing a voice for open source and open standards, into the standards movement going forward.

Here in the USA, there is not anything like what they have in Europe. Here the process will be to engage corporations and institutions and create a participatory structure that enables fair and open opportunity for influence and access to both the development process and the final products.

Tom Vu (TV):  How important is an open standard – building of an RFC in which all industries can agree upon ultimately serving to a wider scale factors of adoption and proliferation?

Michael Koster (MK):

To simply put it, the construction of a formal RFC is something that describes part of system.  A Request for Comments (RFC) is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.  It is a process or evolution in achieving a more widely adopted standard.  The founders of the Internet created this process, and http, etc are all built using original RFC process from many years ago.

Through the Internet Engineering Task Force, engineers and computer scientists may publish discourse in the form of an RFC, either for peer review or simply to convey new concepts, information, or (occasionally) engineering humor. The IETF adopts some of the proposals published as RFCs as Internet standards.

If the IoT Toolkit platform becomes adopted, it may eventually be as many as 10-12 different RFCs, but it’s important to get people to agree on common first set.  This is the initial phase into a more pervasively used universal standard.  In fact, it’s sort of like a strawman platform.  It’s intent is to describe and collaborate, but also invoke and seek out broader participation…  We are at the stage of putting proposals together over the next few weeks and setting up meetings to talk to many people around collaboration and participation in building an Internet of Things platform.

We believe that an open standard platform for horizontal interoperability is key to achieving the promise of the Internet of Things. Everyone needs to be able to present and process machine information in machine understandable formats on the IoT, just as we humans enjoy commonly understandable web data formats and standardized browsers on today’s WWW. It’s important that developers be able to focus on solving problems for their clients and not waste resources on communication and translation.

Read Part Three to Learn More about Why IoT (Internet of Things) Matters?

Here are Part 1 and Part 2 of the Interview Series.