Internet of Things (IoT) technology will be significant in many ways. One benefit of IoT technology is to help relieve some of the daily pressures and make life a little easier. Last week at the IoT Korea Exhibition 2015, InterDigital demonstrated how IoT could assist athletes as well as attendees on the day of a sporting event. &nbsp;
A lot of information is available on the day of a sporting event that can already be collected by IoT devices and uploaded to cloud-based storage.&nbsp; Information such as an athlete&rsquo;s health, transportation to the event, stadium information and more. If only all this data could be made easily available and accessible to app developers, an app could be developed to alleviate stress and improve the overall experience. &nbsp;
Storing data on a standards-based platform such as InterDigital&rsquo;s <a href="/solutions/onempower-platform">oneMPOWER&trade; IoT platform</a>, enables application developers to spend more time dreaming up new apps and less time worrying about where to find the data, how is it formatted, and how to access it.
Take a closer look at each use case and application for the oneMPOWER IoT platform presented at IoT Korea Exhibition 2015:
<ul>
<li><a href="/presentations/onempower-iot-platform-standardsbased-solutions-with-valueadded-services">oneMPOWER IoT Platform</a>&nbsp;&mdash;Explore this overview of the oneMPOWER IoT platform.</li>
<li><a href="/presentations/iot-week-korea-2015--easy-application-development-">Easy Applications</a>&nbsp;&mdash; Discover how the oneMPOWER IoT solution App Developers Kit (ADK) powered by <a href="http://www.thingworx.com/">ThingWorx</a>&nbsp;supports a powerful "drag and drop" Mashup Builder.</li>
<li><a href="/presentations/iot-week-korea-2015-">IoT Mash-Up</a> &ndash; Learn how the oneMPOWER platform can be used to develop horizontal mash-up applications.</li>
<li><a href="/presentations/iot-week-2015--building-automation-">Building Automation </a>&mdash; Discover how the oneMPOWER IoT platform can be interworked with existing networking technologies such as <a href="http://www.systech.com/">Systech</a>'s Z-Wave home and building automation gateway solution.</li>
<li><a href="/presentations/iot-platform-">Personal Connected Health</a>&nbsp;-&nbsp; See how the oneMPOWER IoT platform is used to enable a <a href="http://www.continuaalliance.org/">Continua Alliance</a>&nbsp;certified personal connected health solution from <a href="http://lampreynetworks.com/">Lamprey Networks, Inc.</a> with oneM2M services.</li>
<li><a href="/presentations/onetransport-a-new-dimension-for-integrating-transport-iot-week-korea-2015-">oneTRANSPORT&trade; IoT Solution</a>&nbsp;&ndash; Learn the key role that the oneMPOWER IoT platform is serving in the&nbsp;<a href="http://ir.interdigital.com/releasedetail.cfm?ReleaseID=927882">EU funded project.</a></li>
<li><a href="/presentations/iot-week-korea-2015--iot-advanced-research-areas">Advanced Features</a>&nbsp;&mdash; Get a peek into the advanced features for the oneMPOWER IoT platform that InterDigital is working on in its lab. &nbsp;</li>
</ul>
What&rsquo;s up next? InterDigital will demonstrate its oneMPOWER IoT platform at the <a href="http://www.etsi.org/news-events/events/966-2015-12-etsi-m2m-workshop-2015-featuring-onem2m">ETSI M2M Workshop 2015 featuring oneM2M</a>&nbsp;on December 9-11, 2015 in Sophia Antipolis, France. The workshop will be focused on ETSI&rsquo;s standardization for M2M as well as Smart Cities and Smart Living. &nbsp;
For more on InterDigital&rsquo;s work in IoT, please visit <a href="http://www.interdigital.com/vault_results?search_query=iot">the vault</a>.

InterDigital IoT Meets Athletics at IoT Korea Exhibition 2015

InterDigital's Senior Principal Engineer Ravi Pragada details in <a href="https://www.architectureandgovernance.com/app-tech/iot-sensors-for-iot-systems-what-you-need-to-know/">Architecture and Governance Magazine</a> all you need to know about IoT systems as 5G networks unlock a new wave of opportunity for IoT.
Ravi explains that the introduction of 5G networks has fostered three key waves of opportunities and applications for IoT, as well as their own unique deployment challenges. The first applies to the &lsquo;massive IoT&rsquo; market, which relies on the small data payloads of numerous deployments of low-cost devices in use cases like connected agriculture, smart utilities, and smart cities. The second wave, or &lsquo;critical IoT,&rsquo; involves systems that support real-time control of machinery, robot interactions, and intelligent transport systems. The third wave, encompassing &lsquo;Broadband IoT&rsquo;, supports higher throughput applications associated with larger data volumes and lower latency requirements, like wearable devices, industrial sensors, and surveillance videos.
The expanding range of applications, capabilities, and challenges for IoT sensors has been addressed in 3GPP standards like NB-IoT and LTE-M, New Radio Ultra-Reliable Low Latency Communications (NR URLLC), and New Radio Reduced Capability (NR RedCap). Aside from the critical solutions codified in standards, Ravi argues that business decision-makers must consider other aspects when designing and deploying IoT systems.
For example, even though they are constrained by limited processing and data storage capabilities, the affordability of low-cost IoT devices lowers barriers to their adoption. Many low-cost IoT devices will remain in the field for as long as ten years, requiring new solutions for long service lives, remote operations, and energy and communication efficiency in the form of sleep-mode and energy-harvesting technologies.
Moreover, network operations must consider the necessary support for large populations of IoT sensors. The requirements should include rules of operation between sensors and networks to ensure network intelligence can offload its operational overhead activities, treating an IoT device as a system that works with other systems.
As the density of IoT sensors increases in the future, we will require a technical framework that simplifies the ability for IoT applications to discover and access IoT sensors and enables the interoperability of different sensors &ndash; key challenges addressed by the international standards development organization for end-to-end IoT systems, oneM2M.
Simply put, the design intention of the oneM2M standard is to allow any IoT application to connect to any IoT device, as long as both conform to the oneM2M standard. The process of including oneM2M software in devices and applications solves the basic connectivity challenge, allowing entities to communicate with one another through syntactic and semantic interoperability.
The advent of 6G IoT will demand support for highly constrained heterogeneous devices such as true wireless sensors that can be embedded for instance in walls, bridges, and other structures at the point of construction. To enable these deployments, it is critical to understand battery life, alternative energy sources like radio frequency (RF)-based energy harvesting and zero-energy air interfaces in IoT devices, as they may hold a key to supporting our future of nearly 1 trillion connected devices worldwide.
Read Ravi&rsquo;s full editorial on Architecture and Governance Magazine <a href="https://www.architectureandgovernance.com/app-tech/iot-sensors-for-iot-systems-what-you-need-to-know/">here</a>.

IoT Sensors for IoT Systems – What You Need to Know

In my <a href="http://labs.wot.io/an-architecture-for-internet-of-things-applications/">last blog post</a>, I discussed a sample architecture for an IoT application:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/architecture-1.png" alt="Sample IoT Architecture" />
where in the data is passed through a series of successive stages:
<ul>
<li>Acquisition - receiving data from the sensor farm</li>
<li>Enhancement - augmenting data in motion with data at rest</li>
<li>Analysis - applying machine learning and statistics to the data</li>
<li>Filtering - removing non-actionable data and noise</li>
<li>Transformation - converting it into an actionable format</li>
<li>Distribution - delivering to the end user or application</li>
</ul>
This architecture is based on a number of real world deployments that have been in production for more than a couple years. Each of these deployments share a number of problems in common relating to how the system architecture influences the tradeoffs between cost, throughput, and latency. These three factors are the most common real world constraints that must be taken into account when designing an IoT solution:
<ul>
<li>Cost - the money, time, and mindshare sunk into the system</li>
<li>Throughput - the volume of messages over time the system can handle</li>
<li>Latency - the time it takes for data to translate to action</li>
</ul>
At <a href="http://wot.io">wot.io</a>, we have found it necessary to build new software test equipment to better model the behavior of our production systems. Most existing load testing and modeling tools do not deal well with highly heterogenous distributed networks of applications. Towards this end, we have produced tooling like <a href="https://github.com/wotio/ripple">wotio/ripple</a> for modeling the behavior of data services:
<iframe src="https://www.youtube.com/embed/NPO5oiJoCjc" frameborder="0" width="560" height="315" allowfullscreen="allowfullscreen"></iframe>
In the above video, I simulated an application in which 1750 messages per minute, were generated in a spiky fashion similar to a couple real world systems we have encountered. Anyone who has seen a mains powered sensor farm come on after a blackout will recognize this pattern.
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/ripplea.png" alt="exchange A" />
This is a typical pattern which results when the device designers assume that the devices will come online at random times, or decide to lockstep the message sending to a GPS clock. This acquisition phase behavior can be very noisy depending on the environmental characteristics.
The next step, we simulate some acquisition and enhancement phase activity of adding data to the data in motion by querying a database. To do this, we add a 10 second delay to each of the messages. The time shifted signal looks like:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/rippleb.png" alt="exchange B" />
The ripple software allows for simulating a delay ramp, wherein the delay increases over time based on the number of messages through the system as well. This can be invaluable for simulating systems that suffer from performance degradation due to the volume of data stored in the system. For this sample simulation, however, I've stuck with a fixed 10 second delay. Being able to simulate delays in processing can be invaluable when multiple streams of data must be coordinated.
Another common constraint one encounters is a cost vs throughput constraint. For example, you may want to license a software application that is restricted in the number of CPUs per unit price. The business may only be able to afford enough CPU licenses to account for sufficient throughput of the per minute volume, but not the instantaneous volume.
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/ripplec.png" alt="exchange C" />
For these sorts of applications, we can simulate a maximum rate limit on the application. The ripple.c exchange above demonstrates the stretching of the input signal due to queueing that data between exchanges B and C. Here, we're simulating a 40 messages per second throughput limit. Theoretically, this system could process 40 * 60 = 2400 messages per minute, which is sufficient to handle our 1750 messages per minute load, but at a cost of adding latency:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/latency.png" alt="Latency over Time" />
Here we can see the impact of this queuing on the per message latency over time. The above graph shows about 4 minutes of messages, and the per message latency of each. The reason for this is the messages are enqueued due to not being able to process them as fast as they are coming in briefly:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/queueb.png" alt="Queue B" />
This sawtooth graph is a result of feeding more data into the system than the rate limited process can remove it. This behavior results in highly variable latency across the lifespan of the application:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/hist.png" alt="Latency Historgram" />
In this histogram of the 4 minute sample, you can see a spike around 10s of latency. This spike accounts for roughly 1/8th of all of the messages.The other 7/8ths of the messages however, range from 10s of latency to over 35s of latency. This variability in latency is a classic tradeoff that many IoT systems need to make in the real world. If you are expecting to act upon this data, it is important to understand how that latency impacts the timeliness of your decision.
By combining both delays and rate limits, along with different generator patterns, we can better develop models of how our systems behave under load long before they go to production. With <a href="https://github.com/wotio/ripple">wotio/ripple</a>, we were careful to keep our test generation, application simulation, and our analysis phases decoupled. The message generator and the latency report generators are separate servers capable of being run on different hardware. As the software is written in <a href="http://www.erlang.org/">Erlang</a>, it is easy to distribute across a number of Erlang VMs running on a cluster, and through Erlang's built in clustering, can be coordinated from a single shell session.
The test program used to generate the above graphs and topology is as follows:
<script src="https://gist.github.com/cthulhuology/d3f709612e1d3e6a7f10.js"></script>
This sample file demonstrates the following features:
<ul>
<li>consume, Source, Filename - consumes messages from Source and logs their latency to Filename</li>
<li>pipe, Source, Sink - consume messages from Source and forward to Sink as fast as possible</li>
<li>limit, Source, Sink, Rate - consume messages from Source and forward to Sink at a maximum rate of Rate messages per second</li>
<li>delay, Source, Sink, Base, Ramp - consume messages from Source and forward to Sink with a Base delay in ms with Ramp ms delay added for each message processed</li>
<li>generate, Message, Pattern - send the sample test message (with additional timestamp header) at a rate of messages per second specified in the Pattern.</li>
</ul>
In the near future, we will be adding support for message templates, sample message pools, and message filtering to the publicly released version of the tools. But I hope this gives you some additional tools in your toolbox for developing your IoT applications.

IoT Architecture in Simulation

As part of our preparation for the <a href="http://www.iotevolutionexpo.com/west/">IoT Evolution Expo</a> in Las Vegas in August, we were happy to be able to work with some of our IoT hardware and data service partners. Together, we built a demo showing how several data services from the wot.io data service exchange came together to make up a complete IoT solution.
<ul>
<li><a href="http://www.multitech.com/">Multitech</a> IoT/M2M Connectivity Hardware Devices</li>
<li><a href="http://stream-technologies.com/">Stream Technologies'</a> IoT/M2M Device Management &amp; Connectivity</li>
<li><a href="https://www.solaircorporate.com">Solair</a> IoT/M2M Application Platform</li>
<li><a href="http://www.circonus.com">Circonus</a> Event Metering and Monitoring</li>
<li><a href="http://bip.io">bip.io</a> Web API Automation</li>
<li><a href="http://scriptr.io">scriptr.io</a> Dynamic Data Scripting</li>
</ul>
This IoT Proof of Concept was based on events and readings from a coffee maker and some fans. We selected these because they are familiar and, more importantly, they demonstrate the types of instrumentation that can be applied to a wide range of use cases across many business verticals.
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/blog_wot_io/iot_evolution_coffee_maker.jpg" alt="" />
<a href="http://www.multitech.com/">Multitech</a> engineers added sensors to the coffee maker to measure the flow of water when coffee was made. These sensors were connected to a <a href="http://www.multitech.com/products/wireless">Multitech gateway</a>, which then sent data to <a href="http://stream-technologies.com/">Stream Technologies'</a> <a href="http://stream-technologies.com/iotx/">IoT-X platform</a>.
Stream sent the device data to wot.io where we routed it to a set of data services that could then operate on the data. <a href="http://bip.io">bip.io</a>, <a href="http://scriptr.io">scriptr.io</a>, and <a href="http://www.circonus.com">Circonus</a> were all configured to receive and operate on the incoming device data.
Device data was then routed to <a href="https://www.solaircorporate.com">Solair</a> where it was integrated with other information about the coffee maker in <a href="https://www.solaircorporate.com/en/product/product-features">Solair's system</a> to create a full application dashboard. This application provided all of the information you need for managing your infrastructure, combining asset data, like parts lists and schematics, with live sensor readings.
You can see a sample of the functionality provided by the various systems in the video below. Thanks to our partners for their help in putting together a great demo so quickly!
<iframe src="https://www.youtube.com/embed/3f50s-yN2Vk" frameborder="0" width="560" height="315" allowfullscreen="allowfullscreen"></iframe>
More reading on IoT Evolution:
<ul>
<li><a href="http://stream-technologies.com/blog/iot-evolution-expo-recap-blog">Stream Technologies Recap</a></li>
</ul>

IoT Evolution Partners and Demos

With bandwidth demand for video conferencing and streaming video skyrocketing and the reality of more than <a href="https://www.statista.com/statistics/1101442/iot-number-of-connected-devices-worldwide/#:~:text=The%20total%20installed%20base%20of,that%20are%20expected%20in%202021">15 billion connected IoT devices</a> worldwide doubling the <a href="https://www.statista.com/statistics/330695/number-of-smartphone-users-worldwide/">number of mobile phones</a>, the mobile industry is abuzz with encouragement to consumers to upgrade their devices and service subscriptions to 5G. With network speeds up to 100 times faster than 4G and the ability to support 500 times the number of connected devices per square kilometer compared to 4G, there are obvious benefits for both consumers and operators to transition to 5G.
However, various <a href="https://www.datacenter-forum.com/datacenter-forum/5g-will-prompt-energy-consumption-to-grow-by-staggering-160-in-10-years">studies</a> and <a href="https://www.wsj.com/articles/5g-drains-your-iphones-battery-heres-what-you-can-do-about-it-11647716969?mod=tech_lead_pos5">analyses</a> have raised concerns over the increased power consumption of 5G networks and devices compared to 4G, and the negative environmental impact this may have.
Understanding these dynamics, the engineers at InterDigital have been leading research and defining innovative solutions to mitigate and reduce power consumption of 5G networks and devices. From power optimizations that can be enabled in the lower-layer access technologies used to manage connectivity and transmit and receive data between devices and the network, to higher-layer services that can be deployed in 5G devices and distributed throughout cloud and edge compute functions in the 5G network, InterDigital&rsquo;s research has focused on several aspects of the overall 5G system.
One major focus area of InterDigital&rsquo;s research has involved connected IoT devices. When it comes to optimizing power consumption, connected IoT devices have a unique set of technical challenges that differ from smartphones. For this reason, along with the fact that connected IoT devices already outnumber smartphones 2 to 1 (a gap that is expected to widen to 4 to 1 by <a href="https://www.statista.com/statistics/1101442/iot-number-of-connected-devices-worldwide/#:~:text=The%20total%20installed%20base%20of,that%20are%20expected%20in%202021">2025</a>), optimizing power consumption for this category of device has been a top priority for InterDigital.
Power Optimization for IoT
IoT devices differ from smart phones in a few key ways. IoT devices typically handle comparatively small amounts of data and are instead optimized to prioritize battery life. Battery-powered IoT devices are required to remain operational for long durations (e.g. a decade or more) without recharging or replacing their batteries. They often have a much smaller battery or no battery at all and instead rely on harvesting ambient energy such as solar or vibrations. As such, to conserve their batteries, many of these devices need to remain disconnected and completely powered off for long durations until they are awoken to perform an operation, for instance a sensor that wakes-up monthly to report a reading and then returns to sleep. Other devices must minimize the amount of circuitry they leave powered on so they are still able to be remotely triggered to fully power-up if/when needed, for example an actuator that must be sent a remote command to close a critical valve in a timely manner. Unlike smartphones which can rely on users for daily recharging, and/or transitioning in and out of low power modes when needed(e.g., a user enabling/disabling airplane mode to turn off/on cellular, Wi-Fi or Bluetooth radios to extend the life of the battery), IoT devices typically do not interact with users. Instead, these connected IoT devices must rely on more autonomous forms of management and control within the devices themselves or the networks to which they connect.
InterDigital Solutions
At InterDigital, our research teams have been working on several key technologies over the past decade to help optimize the power consumption of the 5G system with respect to IoT devices. The following are a few examples of foundational technologies developed by innovative InterDigital engineers in collaboration with our industry and academic partners and contributed to standards bodies such as 3GPP, oneM2M, and IETF so that the 5G ecosystem may benefit from them.
IoT Device Triggering
Device triggering technology enables IoT devices to &ldquo;sleep&rdquo; for long periods of time when not in use, and intelligently &ldquo;wake up&rdquo; when needed. Specifically, IoT devices register to a service in the network and provide instructions for triggering the device. The instructions can include a device&rsquo;s contact information as well as its sleep schedule. Once registered, the IoT device powers down to sleep to conserve power. Based on its sleep schedule, the device can periodically wake up for a short duration of time to listen for triggers by optimally enabling only a small, select portion of its circuitry required to receive a trigger, but otherwise, the device consumes a relatively small amount of power. If the service in the network needs to communicate with the device (e.g., send it a command), it schedules a trigger to be sent to the device during a scheduled wake up time. If the device receives a trigger, it fully powers-up, connects to the network and communicates with, or receives a command from, the service. Afterwards, the device powers back down and goes back to sleep to continue conserving its power. To provide even further power savings and the ability to trigger an IoT device in a more on-demand manner without having to wait for a scheduled wake-up time, ultra-low power wake-up receiver technology can also be used. This technology is embedded within an IoT device and can receive a low power wake-up signal. The ultra-low power wake-up receiver circuitry does not draw power from the battery of the IoT device. Instead, the receiver is passive in nature and is powered by the energy captured from the radio waves used to transmit the wake-up signal to the IoT device. This solution is analogous to other forms of passive receiver technologies like radio frequency identification (RFID) used in applications like electronic toll collection, however, this ultra-low power wake-up receiver technology operates in longer-range wide-area cellular networks.
IoT Device Twins
Device twin technology enables physical IoT devices deployed in the field to be represented by digital counterparts that reside within services hosted in the cloud or on network edge compute nodes. These digital counterparts, or twins, are then used to exchange information between the devices themselves and the applications and services that wish to interact with them. For example, a sensor can publish readings to its digital device twin. Use of device twin technology can provide a huge power consumption benefit for IoT devices because device twins allow IoT devices to disconnect, power down and sleep for longer durations of time without impacting the functionality of applications, services and other devices that require data from these IoT devices. Even while IoT devices are sleeping, their data can be accessed from their device twin.
Device twin technology also reduces the number of requests IoT devices must send and receive, since they only need to interact directly with their device twins instead of other applications, services, or devices. An IoT device is only required to wake-up long enough to send an update to its device twin, and then can immediately go back to sleep. Even an actuator-type device, which requires receiving commands, can benefit from device twins because actuator commands can be stored within the digital twin. The IoT device can then wake-up based on its own schedule, check its device twin for any new commands, perform these commands, update its device twin with the results, and then return to sleep.
IoT Message Profiles
Many IoT devices generate a stream of sensor readings on a periodic schedule or event basis. The number of bytes of data included within each message the device sends or receives can have a major impact on the battery life of the device. The larger the message sent or received over the network, the longer that device must remain powered to send the message. Over time, this can add up and dramatically reduce the lifetime of the device battery.
In many IoT use cases, there is a certain amount of information contained within these messages that is static in nature and does not change &ndash; for example, certain fields within upper layer protocol headers of the message or in the data payload of the message. This static information is critical to processing the message and provides critical context to the services and applications, like analytics, consuming and processing the message. However, this static information can result in significant overhead on the device and the network if included in every message the device sends. To alleviate this, IoT message profiles can be used. Within a profile, static information elements can be defined along with criteria defining which device(s) and/or message type(s) a profile is applicable to. IoT message profiles can be configured within the network services to which an IoT device sends it messages, like a cloud or edge data service. As the service receives messages, it compares the messages against the profiles and if a match is found, the messages are enriched with the static information defined in the profiles and further processed by the service or applications (e.g., analytics operations are performed). This allows devices to send only the bare minimum amount of information that has dynamically changed per message (e.g., a sensor reading) and streamline the size of the message. IoT message profiles can also be configured on IoT devices themselves and used in a similar manner by the devices to enrich the messages they receive with static information. Therefore, the use of IoT message profile technology helps minimize the size of messages flowing between IoT devices and services in the network, which in turn translates into less energy consumed by the IoT devices as well as reduced load and energy consumption by the network infrastructure used by the IoT devices.
Offloading IoT Event Processing
Offloading event detection and processing from user applications to services deployed in the cloud and on edge compute nodes in the network reduces the overall number of messages exchanged over the network. Rather than an application retrieving every sensor reading published by the device(s) it is interested in and checking whether sensor readings have crossed a certain threshold value of interest, the application instead offloads an event detection rule to a service in the network. Within the rule, the application specifies the devices it is interested in, the data of interest from these devices, conditions of interest for this data, and actions that are to be performed if/when these conditions are detected. For example, if pressure within a specified boiler device exceeds a specified threshold, then power to the boiler is turned off. Using the rule, the service can efficiently offload and perform this work on behalf of the application.
Offloading eliminates the need to send individual copies of device data to each application to process, which greatly reduces the amount of messaging in the system. It also enables the pooling and reuse of compute and storage resources of the service by the IoT devices and applications in the system. For example, data offloaded by IoT devices to a service in the network can be used both for the monitoring of a single condition defined in a single rule from a single application, and also simultaneously used by the service to monitor many conditions defined in many rules from many applications. As result, offloading IoT event processing can play a major role in helping optimize energy consumption in the overall 5G system.
Radio Frequency (RF) Energy Harvesting
Many IoT devices, given their minimal power requirements, are ideal candidates for leveraging energy harvesting technologies such as solar, thermal, wind, and vibrations. Use of these different technologies however is often very use case-specific and dependent upon the availability and suitability of the energy source (e.g., solar is best suited for outdoor applications). One promising technology that InterDigital engineers have been developing enables energy to be harvested from cellular radio signals. This technology enables IoT devices to harvest energy from the very same cellular network signals they use to communicate with cell towers. Given the widespread deployment and coverage of cellular networks, this form of energy harvesting could make a huge impact and further complement existing energy harvesting technologies to revolutionize how connected IoT devices are powered. This could not only help charge and extend the battery life of these devices, but one day it may eliminate the need for batteries in these devices altogether. This could allow devices to be deployed in places that are not yet practical today, like those implanted within infrastructure like concrete walls and bridges and eliminate the need to replace batteries every five to ten years.
Conclusion
As the mass scale out of connected IoT devices within the 5G ecosystem continues, the importance of using and responsibly deploying the technologies described above will become critical. This will help reduce the power consumption of 5G systems and make these deployments more sustainable. For this reason, InterDigital is committed and actively engaged in forward looking research to identify technologies that can further optimize the sustainability of 5G and future 6G deployments.
Learn More
InterDigital&rsquo;s sustainability microsite includes the latest research and white papers exploring the impact of energy sustainability in the evolution of advanced wireless, video, IoT proliferation, and more. Learn more about InterDigital&rsquo;s sustainability thought leadership and efforts to identify innovative solutions to address energy consumption and environmental sustainability across all sectors of the technology ecosystem, <a href="https://www.globenewswire.com/Tracker?data=dQ1_9ylctunHl4t8XyItA_Qk3FbXtr9LaNfznzhvegOkNUqLeFgdePPrEs676tP27XLvXKBztrN2VHctOpSXAQB0-k-oNZgGZO3LukVGvqXazKcV5rhnyzfg3AvVvwXXLoOXHSD-nzUrpZkfEk6zEw==">here</a>.

Sustainable Solutions for 5G’s Influx of IoT: Low Power Operations in IoT Devices

We've been having some fun with the <a href="http://www2.meethue.com/">Philips Hue</a> smart lighting system and I wanted to expand the interactivity beyond the local office WiFi network. We had an <a href="http://community.imgtec.com/platforms/creator-ci20/">Imagination Creator Ci20 (version 1)</a> board available, so I thought it would work as a good gateway to pull data from the Philips Hue bridge and send it to some online services with one of the wot.io data services; bip.io.
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/ci20_smaller.jpg" alt="Imagination Creator Ci20" />
To keep it simple, I decided to share one value, the current hue setting of a single one of our lights (see the Hue documentation for details on how it <a href="http://www.developers.meethue.com/documentation/core-concepts">defines light values</a>). To get the value, I wrote a <a href="http://www.perl.org">Perl</a> program on the Ci20 to connect to the Hue gateway using the <a href="https://metacpan.org/pod/Device::Hue">Device::Hue module</a>. The program finds the correct light (we have several), pulls out the hue value, and then sends it along to our bip.io instance set up for <a href="http://shipiot.net">Ship IoT</a>. My bip then calls <a href="http://numerousapp.com/">Numerous</a> and updates my hue metric.
<h3 id="details">Details</h3>
First I set up the bip so I would have an endpoint to send data to. It's a simple one with a web hook (HTTP API) for input and a single call to Numerous. The Numerous pod configuration involves activating the pod with your Numerous developer API key, creating a number in Numerous, then providing the metric id for your number created in the Numerous app as a configuration to the configured pod (see the video for details).
<iframe src="https://www.youtube.com/embed/TyiBBq4-WWU" frameborder="0" width="560" height="315" allowfullscreen="allowfullscreen"></iframe>
If you're not familiar with Numerous, it's a mobile app that displays individual panels with important numbers on each panel. If you install the app and search on "wot.io" you'll find our shared "wot.io Buffalo Hue" number. Then you can see how our Hue changes and maybe set one of your lights to the same color as ours.
Once the bip is created, you have an endpoint. Next is to send data to it using the Ci20 board and a short Perl program.
The Ci20 board uses a MIPS processor and runs <a href="https://www.debian.org/">Debian</a> out of the box. Add a monitor, keyboard, and mouse and you're ready to go. The board has wifi connectivity, so once the Debian desktop came up, I used the desktop GUI tool to connect the board to the same network the Hue gateway runs on.
Perl is part of the standard install. There are many ways to install the Device::Hue module, <a href="https://metacpan.org/pod/App::cpanminus">cpanminus</a> is likely the fastest:
<code>sudo apt-get install curl </code> <code>curl -L https://cpanmin.us | perl - --sudo App::cpanminus </code> <code>cpanm --notest --sudo Device::Hue</code>
You can find the program I used in the <a href="https://github.com/WoTio/shipiot-hue-bipio">wot.io github project</a>. The values you need to run it are all listed at the top:
<ul>
<li>Base URL of the Hue bridge on your network</li>
<li>A username or "key" for the Hue bridge (<a href="http://www.developers.meethue.com/documentation/getting-started">instructions</a>)</li>
<li>The name of the light you want to pull data from</li>
<li>URL of your bip endpoint and token</li>
</ul>
Once it's configured, you can run and your hue value is updated on Numerous!
Another interesting idea to extend the project is to schedule a job in cron, store the hue value, and send updates only when the value changes. It would also be fun to set up an endpoint on the Ci20 to receive a value back and set the hue value. Maybe a project for next time, or maybe someone will beat me to it and send me a pull request.

Ship IoT with Imagination Creator Ci20 as IoT Gateway for Philips Hue bulb

<h2 id="setup">Setup</h2>
For this tutorial you will need to sign up for a set of accounts:
<ul>
<li><a href="https://shipiot.net/">Ship IoT</a></li>
<li><a href="http://control.littlebitscloud.cc/">LittleBits Cloud Control</a></li>
<li><a href="http://slack.com">Slack</a></li>
</ul>
You will also need to acquire a <a href="http://littlebits.cc/bits/cloudbit">CloudBit</a>, based around a Freescale i.MX23 ARM 926EJ-S processor, from <a href="https://littlebits.cc">LittleBits</a>. The parts we will use for this tutorial are:
<ul>
<li>a 5V 2amp USB power supply</li>
<li>a micro USB cable</li>
<li>p3 usb power</li>
<li>i3 button</li>
<li>w20 cloud</li>
<li>o9 bargraph</li>
</ul>
They should be assembled in series as follows:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/littlebits.JPG" alt="" />
Instructions for connecting the Cloudbit to your local WiFi network for the first time can be found on the <a href="http://littlebits.cc/cloudstart">Cloudbit Getting Started page</a>. If you have already setup your Cloudbit, you can change the WiFi settings by going to <a href="http://control.littlebitscloud.cc/">your Cloudbit's page</a> and going to Settings and selecting the following option:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/Screen-Shot-2015-07-21-at-4-46-56-PM.png" alt="http://control.littlebitscloud.cc/" />
If you don't already have a Slack account, you can <a href="https://slack.com/create">create a new team</a> and setup your own #littlebits channel for testing:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/Screen-Shot-2015-07-21-at-4-50-57-PM.png" alt="" />
So by now, you have signed up for <a href="https://shipiot.net/">Ship IoT</a>, have a <a href="http://littlebits.cc/bits/cloudbit">CloudBit</a> sitting on your desk, a <a href="http://slack.com">Slack</a> channel, and are wondering what's next?
<h2 id="creatingourfirstbip">Creating our first Bip</h2>
When you first <a href="https://shipiot.net">Sign In to Ship IoT</a>, you will encounter a friendly green button that looks like this:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/Screen-Shot-2015-07-21-at-5-00-43-PM.png" alt="" />
Clicking that button will take you to a blank canvas onto which you can install an Event Source:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/blank.png" alt="" />
By clicking on the target in the middle, you will be presented with an Event selection screen:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/eventsource.png" alt="" />
We'll select "Incoming Web Hook" to provision a URL to which our CloudBit will send messages. In the field that say "Untitled":
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/Untitled.png" alt="" />
Enter a path of "littlebits" for our Event Source, and we should now have an event trigger on our canvas:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/trigger.png" alt="" />
Next we will "Add An Action" which will bring us to an action selection screen:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/actionselect.png" alt="" />
If you scroll down a bit you will find a Slack pod which we can activate. Your first time through, it will request you to sign into your Slack account and authorize Ship IoT to access your Slack account. In the background it will provision a new access token and send you an email notifying you of that. In the future, you can deactivate this token through the Slack interface.
After you have activated the pod, you will be asked to select an action to perform:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/postmessage.png" alt="" />
In this case, our only option is to "Post to Channel". Selecting this action will result in another node in our bip:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/two.png" alt="" />
Double click on the Slack icon to open up the action's preferences:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/options.png" alt="" />
We can give the bip.io bot a name of "LittleBits":
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/botname.png" alt="" />
We can select the "Channel ID" either using the "Use Preset" button which will attempt to discover the list of channels you have created, or you can supply a custom channel id:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/customchannel.png" alt="" />
Finally, we need to specify the "Message Text", and for this we will send the full message sent by the CloudBit by selecting "Incoming Web Hook Object":
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/msgtxt.png" alt="" />
After clicking OK, we can now link these together by dragging and dropping from the purple Event Source to the Slack action:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/draganddrop.png" alt="" />
Now whenever a message is sent to <a href="https://yourname.api.shipiot.net/bip/http/littlebits">https://yourname.api.shipiot.net/bip/http/littlebits</a> it will be sent to our "Post to Channel" action!
Well not exactly. We still need allow LittleBits to send us messages. Under the "Auth" header, we can change the authentication type to "None":
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/none.png" alt="" />
Turning off auth makes our URL a shared secret that we should only share with LittleBits. Anyone with that URL will be able to send messages to our Slack channel, so some care should be taken not to share it!
<h2 id="configuringalittlebitssubscription">Configuring a LittleBits Subscription</h2>
Configuring your CloudBit to talk to bip.io requires using the command line for a little bit. First we will need a little information from our <a href="http://control.littlebitscloud.cc/">Settings panel</a>:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/cloudbitsettings.png" alt="" />
We will need to record both the Device ID and the AccessToken. These are needed to setup the subscription to our bip.iob application.
To setup a subscription requires a bit more black magic on our part. The <a href="http://developer.littlebitscloud.cc/">CloudBit API Documentation</a> describes how to make a HTTP request to register our device with a 3rd party subscriber. In our case, we would like to register our Incoming Web Hook URL as a subscriber to our CloudBit. To do so, we'll write a small bash shell script use <a href="http://curl.haxx.se/docs/manpage.html">curl</a> in a script we'll name "subscribe":
<blockquote>
#!/bin/bash
DeviceID=$1
AccessToken=$2
URL=$3
EVENTS=$4
curl -XPOST \
-H "Accept: application/vnd.littlebits.v2+json" \
-H "Authorization: bearer $AccessToken" \
<a href="https://api-http.littlebitscloud.cc/subscriptions">https://api-http.littlebitscloud.cc/subscriptions</a> \
-d publisher_id=$DeviceID \
-d subscriber_id=$URL \
-d publisher_events=$EVENTS
</blockquote>
To use this script we need only make it executeable and run it:
<blockquote>
$ chmod u+x subscribe
$ ./subscribe yourDeviceId yourAccessToken yourUrl "amplitude:delta:ignite"
</blockquote>
This will cause the the URL you supply to be contacted each time the amplitude changes from low to high. If you want to have the value periodically reported instead you can just use the value of "amplitude" to get a message roughly every 750ms.
If the script works you will get a message back like:
<blockquote>
{"publisherid":"xxxxxxxxxx","subscriberid":"<a href="http://yourname.api.shipiot.net/bip/http/littlebits">http://yourname.api.shipiot.net/bip/http/littlebits</a>","publisher_events":[{"name":"amplitude:delta:ignite"}]
</blockquote>
This means your subscription has been registered and events are now flowing through the system.
<h2 id="testingitout">Testing it out</h2>
If you push the button now:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/push.JPG" alt="" />
A message should show up in your #littlebits channel:
<img src="http://idfiles.leveelabs.com/55bd0288af0b0930ba599bd0c4b7ca38/resources/img_new/labs_wot_io/slackoutput-1.png" alt="" />
You can use this same technique to drive any number of workflows through bip.io. All at the press of a button.

Ship IoT with LittleBits and bip.io

While the IoT market, in general, was slow to capture the public's imagination prior to 2017, one area where IoT is blooming is in the smart city and smart building industry. Mass rollouts of IoT in an industrial setting, including urban environments and business hubs, are beginning to garner success. It is more important than ever to understand what smart cities are, how they get smart, what technologies have the greatest impact, potential challenges, and much more. &nbsp;
A number of InterDigital IoT experts alongside their industry peers plan to share emerging technologies, complex challenges, best practices and reasonable expectations for the future of smart cities throughout this month. Just some of the upcoming opportunities to hear from InterDigital include:
<ul>
<li>&ldquo;IoT Software: Basic Components of the Platform,&rdquo; on June 8th: <a href="http://www.m2mzone.com/iotsoftware">http://www.m2mzone.com/iotsoftware</a></li>
</ul>
<ul>
<li>&ldquo;Standardising and Integrating Smart Cities: A transport use case,&rdquo; on June 9th: <a href="http://www.indiaeu-ictstandards.in/webinars/">http://www.indiaeu-ictstandards.in/webinars/</a></li>
</ul>
<ul>
<li>Industrial Internet Smart Cities Forum Panel on June 14th: <a href="http://www.iiconsortium.org/berlin-forum-2017/">http://www.iiconsortium.org/berlin-forum-2017/</a></li>
</ul>
<ul>
<li>&ldquo;Creating a Sustainable Framework for IoT&rdquo; on June 14th: <a href="https://tmt.knect365.com/iot-world-europe/agenda/1#panel-creating-a-sustainable-framework-for-iot ">https://tmt.knect365.com/iot-world-europe/agenda/1#panel-creating-a-sustainable-framework-for-iot </a></li>
</ul>
InterDigital has been an active contributor to the development of standards-based IoT to enable multiple ecosystem partners to provide IoT solutions that range from industry specific applications to advanced data marketplaces.&nbsp; In addition, the company is actively involved in organizations that are dedicated to the acceleration of IoT including ATIS, IIC, GSMA NB-IoT, and oneM2MTM, among others.
To learn more about InterDigital&rsquo;s work in IoT, please <a href="http://www.interdigital.com/iot/">click here.</a>

InterDigital Experts Share IoT & Smart Cities Insight

The Internet of Things (IoT) is a major topic of conversation in the tech world right now, and InterDigital is involved in a big way &ndash; whether it&rsquo;s our <a href="http://www.interdigital.com/solutions/onempower-platform#home">oneMPOWER platform</a>, our commerical initiative <a href="http://wot.io/">wot.io</a>, or the efforts of our various teams to partner with industry development efforts, standards bodies and external innovation. InterDigital&rsquo;s Serhad Doken, Vice President, Innovation Partners, took a moment to reflect on the future of IoT, and the role of software in driving it, in&nbsp;<a href="http://www.wirelessweek.com/articles/2015/07/ten-truths-about-future-iot">an article</a> featured on Wireless Week today. &nbsp;
According to Serhad, IoT is not about connecting things or producing data&hellip;it&rsquo;s about what happens next. In the article, he breaks down what he believes the IoT big picture will eventually hold into ten key points. Serhad addresses how the IoT will alter enterprise, transition business models, and amplify the importance of multi-modal User Interface and User Experience. He closes the article with what he refers to as &ldquo;the crown jewel potential and real promise of IoT&rdquo; &ndash; rapid new service creation. Serhad explains that full IoT solutions will allow for a simplification that enables any user to design and add new services without needing (or even wanting) to fully understanding the mechanics.
As a pioneer in mobile technology, InterDigital is actively taking on challenges in IoT. Most recently, the company demonstrated the latest capabilities of its oneMPOWER platform solution at Internet of Things World San Francisco in May 2015. InterDigital's oneMPOWER platform provides M2M/IoT application enabling services that include connectivity, device, data, and transaction management resulting in faster time-to-market, scalable application development and lower operation costs. &nbsp;
Check out Serhad&rsquo;s full article&nbsp;<a href="http://www.wirelessweek.com/articles/2015/07/ten-truths-about-future-iot">here</a> or to learn more about IoT, visit the <a href="/vault/">vault</a>.

IoT: Ten Ways to See the Future

<a href="http://wot.io">wot.io</a> has made it much easier to Ship IoT projects with <a href="http://shipiot.net">Ship IoT</a>, currently in beta, to make it easy to prototype smaller IoT projects with maker boards and starter kits. Ship IoT is deployment of one of our wot.io data services, <a href="http://bip.io">bip.io</a>, which is a web API automation system that makes it easy to connect to open APIs for dozens of services and automate data workflows.
As an example of the types of projects we think users might be interested in, we put together a simple project using the <a href="http://kinoma.com/create">Kinoma Create</a>--which packs an 800 MHz ARM v5t processor--as the device. Using the HTTP API provided by Ship IoT Lite, we're able to send data and events from the Kinoma Create to Ship IoT Lite, and then to other services like <a href="http://twitter.com">Twitter</a>. Here's a video showing how we did it.
<iframe src="https://www.youtube.com/embed/w9QV_e5e62o" frameborder="0" width="560" height="315" allowfullscreen="allowfullscreen"></iframe>
The IDE used there is <a href="http://kinoma.com/develop/studio/">Kinoma Studio</a> which is the tool you use to deploy code to the Kinoma Create. You can find the sample code in our <a href="https://github.com/WoTio/kinoma/tree/master/shipiot">Kinoma project in github</a>. I shared <a href="https://shipiot.net/share/42645c0f-b923-4b96-97a7-13133702f5ab">the simple Twitter bip</a> in Ship IoT so you can get up and running quickly.
&nbsp;
<div class="bipio-share" data-share-id="42645c0f-b923-4b96-97a7-13133702f5ab">
<script src="https://shipiot.net/static/js/widget-loader.js" async="" type="text/javascript" data-embed-host="https://api.shipiot.net"></script>
</div>
<a href="http://shipiot.net">Ship IoT</a> is a free to sign up, so give it a try today!

Ship IoT with Kinoma Create and bip.io

The Internet of Things (IoT) is one of the most important areas of research for InterDigital, for a variety of reasons. For our technologists, we understand that it&rsquo;s a force that will in all likelihood fundamentally alter the way the world operates, much like the advent of large-scale business computing or the Internet. For our investors, we often highlight that IoT is one of the next big opportunities that the company is working to capitalize on, through a variety of approaches including our<a href="http://ir.interdigital.com/releasedetail.cfm?releaseid=731296"> Convida Wireless joint venture</a>, our ONEMPOWER M2M service delivery platform, and <a class="offsite" href="http://wot.io/">wot.io</a>, our startup focused on IoT data management.
So although it&rsquo;s still early days for IoT, we were happy to see InterDigital included in a list of IoT market leaders when it comes to intellectual property. In a blog entry yesterday, Boston-based TechIPm, LLC, a professional research and consulting company specializing in technology and intellectual property mining and management, ranked InterDigital third in its &ldquo;<a class="offsite" href="http://techipm-innovationfrontline.blogspot.com/2015/03/m2m-d2d-communications-for-iot.html?m=1">M2M for IoT Innovation Ranking</a>,&rdquo; just behind LG and Ericsson and ahead of Samsung, ETRI and Qualcomm, among others.
The ranking underscores the pioneering development and standardization work that InterDigital has done in IoT, including helping to drive the ETSI standard that is now a part of the OneM2M effort. That work has also been captured in a solution, the ONEMPOWER M2M service delivery platform,&nbsp;<a href="http://ir.interdigital.com/releasedetail.cfm?ReleaseID=899365">which was highlighted</a> at Mobile World Congress in Barcelona.
It should be noted, InterDigital does not vouch for the accuracy of third-party research or the methodologies such researchers employ &ndash; TechIPm&rsquo;s conclusions are their own. Still, it&rsquo;s nice to be noticed!

InterDigital Listed Among Early IoT IP Leaders

The majority of sample IoT applications available online, including <a href="/">many of our own</a>, use <a href="https://en.wikipedia.org/wiki/JSON">JSON</a>, <a href="https://en.wikipedia.org/wiki/XML">XML</a> or some other simple, human-readable, text-based format. It makes sense because it's easy to show the data at various parts of the application, it's easy to create new demo data, and it's easy to work with JSON data in server-side data services because it's a well-supported format for web-based services.
But in the real world of connected devices, not all IoT data will look like JSON or XML. System designers are already concerned about the bandwidth use of the oncoming wave of devices and are advocating for leaner, more compact formats. In <a href="https://www.youtube.com/watch?v=GuIyESNLACo">his keynote</a> at ARM TechCon 2015 earlier this month, Google's Colt McAnlis encouraged developers to be looking at lighter-weight binary protocols like <a href="https://google.github.io/flatbuffers/">FlatBuffers</a> or <a href="https://developers.google.com/protocol-buffers/?hl=en">protocol buffers</a>.
And of course, an increasing number of IoT solutions will incorporate audio and video streams&mdash;either as primary or as additional sources of IoT data. For example, security monitoring systems or advanced sensors attached to machinery watching product output as part of an industrial quality control system both involve the collection, transmission, and analysis of audio streams.
The following video demonstrates how binary data can be transmitted across and manipulated within the wot.io operating environment.
<iframe src="https://www.youtube.com/embed/wYte433TE8s" frameborder="0" width="420" height="315" allowfullscreen="allowfullscreen"></iframe>
Properly working with binary data isn't trivial, and it's an important aspect of an enterprise-caliber data routing system. wot.io adapters and its operating environment work independently from the payload its messages carry, and can therefore accept and route messages with payloads of arbitrary format. Allowing adapters to flexibly consider message payloads alternately as either opaque blobs or as transparent, structured data proves to be immensely valuable in real-world industrial IoT scenarios.
In fact, the wot.io data service exchange&trade; has a number of data services like <a href="http://nervve.com/">Nervve</a> and <a href="http://www.datascription.com/">Datascription</a> that provide search, transcription, and metadata extraction from binary audio and video streams. If you'd like to learn more about these and other data services, <a href="http://www.wot.io/contact/">contact wot.io</a> today!

wot.io Data Services for Binary IoT Data

InterDigital&rsquo;s Rafael Cepeda, Senior Manager, examines if 5G can become an enabler that provides flexible connectivity and core tools for IoT building blocks in&nbsp;<a href="http://www.telecomengine.com/article/how-will-5g-and-internet-things-play-together">a recent article</a> featured on TelecomEngine. Rafael states that with 5G developments well underway, the conversation has turned to how 5G will impact society and intersect with the Internet of Things (IoT). &nbsp;
In his article, Rafael utilizes examples from the transport sector and smart cities to reveal how the mobile networks of today are not designed to handle the large expansion of diverse data that will come with IoT. However, 5G networks are anticipated to provide the flexibility required for the data generated by the IoT. Therefore, IoT will drive the dynamic configuration of the 5G network. Ultimately, Rafael explains that the two will work together to deliver the ultimate efficient configuration that will serve all end user&rsquo;s needs whenever, and wherever. &nbsp;
<a href="http://www.telecomengine.com/article/how-will-5g-and-internet-things-play-together">Click here</a>&nbsp;to read the full article or to learn more about 5G and IoT, visit <a href="/vault/">the vault.</a>

InterDigital Senior Manager Examines 5G and IoT Relationship

Hofstra University will host the first presidential debate on September 26, 2016. The University, which hosted presidential debates in 2008 and 2012, will be the first university to host debates in three consecutive presidential election years. &nbsp;As a lead-up to the first 2016 presidential debate, the University has organized an interdisciplinary debate program titled, <a href="http://www.hofstra.edu/debate/debate-event-calendar.html">Debate 2016</a>.
Debate 2016 is a series of 25 events &ndash; including an Internet of Things panel featuring two experts from InterDigital &ndash; &nbsp;that addresses issues such as race relations, international trade agreements, foreign policy, public education, infrastructure, and federal budget policy.
&ldquo;Internet of Things &ndash; &nbsp;Technology, Standards, Policy, and Opportunities,&rdquo; will be a panel discussion comprised of industry experts including Jim Nolan, EVP, <a href="http://www.interdigital.com/iot/">IoT Solutions</a>, InterDigital; Bob Wild, Senior VP of Intelligent Production Solutions; Christopher Cave, Director R&amp;D, InterDigital; and Joshua Mecca, President and co-founder of M&amp;S Biotics, LLC; on Thursday, September 22. The panel will discuss the progress and challenges in merging multiple technologies together to create the IoT. The panelists will also cover how industry standards, government policies and regulations help facilitate emerging IoT use cases.
<a href="http://events.hofstra.edu/index.php?com=rsvp&amp;eID=19182">Click here</a>&nbsp;to learn more about the debate or to learn more about the IoT, please visit <a href="http://www.interdigital.com/vault_results?search_query=IoT&amp;search_button=Search+The+Vault">the vault</a>.

Hofstra University IoT Debate Features Two InterDigital Experts

If you&rsquo;ve been on the floor of a Mobile World Congress event, you&rsquo;ve likely read (or at least have seen) a copy of Mobile World Daily, the official publication of Mobile World Congress events. Mobile World Congress Shanghai 2016 kicked-off yesterday and along with it came the day one issue of Mobile World Daily featuring the latest coverage and analysis of event news. Among the top stories? Standards' role in smart cities with statistics from a <a href="http://www.interdigital.com/white_papers/Machina_2016_SmartCities">recent Machina Research report</a> commissioned by InterDigital. &nbsp;
The story, titled &ldquo;Standards can sharply lower smart city costs,&rdquo; features insight from Chris Heckscher, VP of service provider sales at Cisco, on how standardization can substantially lower costs of IoT deployment. Heckscher explains that deploying IoT solutions without interoperability standards would add $341 billion in costs worldwide by 2025. This statistic comes directly from the <a href="http://ir.interdigital.com/Cache/1500086592.PDF?O=PDF&amp;T=&amp;Y=&amp;D=&amp;FID=1500086592&amp;iid=4103938">recent Machina Research report</a>, which analyzes potential IoT deployments in smart cities. The report, which launched in early May, shows that using non-standardized versus standards-based solutions for IoT will increase cost of deployment, hinder mass scale and adoption, and stifle technology innovation for smarty city initiatives worldwide. &nbsp;
<a href="http://madaily.mobileworldlive.com/2016/day1/index.html">Click here</a>&nbsp;to read this edition of Mobile World Daily, or view the full Machina Research report <a href="http://www.interdigital.com/white_papers/Machina_2016_SmartCities">here</a>. &nbsp; &nbsp;

Search Results

Search Results

READY TO LEARN MORE ?