Avaya Tech Talk: The ‘Internet of Things’ Needs a Network

In order for the Internet of things to actually do anything, it’s going to need a ‘Network of Things’ to operate upon. If you are going to connect the millions of devices that will need to communicate with each other, a radical shift in the way we deploy networks is going to be required.

Just to support the number of these things will be a monumental task that is beyond our current ability today, but not for long. IPv6 will solve the problem of the number of the number of IP addresses required as the current IPv4 schema won’t carry us too much further into the future. Network connectivity is slated to possibly be the next ”utility service” required to exist, just like power, water, and cable TV. There is a primary difference here though. While definable owners of public utility services exist, and we all know who the Power and Water Companies are, the internet’s network has evolved to be something that is considered by many to ‘just be there’ and potentially free in the public space. Hey, it’s all in the cloud anyway, right?

While I agree that most users understand someone has to pay for the network, who exactly that someone is may not be on customer’s mind as they use the service.

You can think of this like the streetlights downtown. Obviously the power company is not providing that service free of charge. The Township or Municipality most likely pays the bill for it, and that funding is taken from the tax base and is a line item on the budget. Visitors who may be the primary consumers of that service don’t actually contribute directly in the payment of that bill. It is considered to be a normal, expected amenity, similar to pubic water fountains and public bathrooms. While they may not be the nicest places you have ever visited, they are none the less still there and available to the general public.

In today’s connected society a similar model maybe evolving for the Internet. For example, my cable provider in New Jersey happens to provide free Wi-Fi service in public spaces. They also partner with several other cable providers who act as a consortium to pool their resources for their customer’s connectivity capability.

For example, on a recent trip to California I was able to use the outdoor Wi-Fi hotspots from the local cable provider there and establish Internet connectivity free of charge in quite a few public places. I began to wonder if this was so easily possible through a simple peering agreement with the cable providers. How far away are we from a ubiquitous agreement between all carriers? And is the service being provided by the endpoints on their networks free of charge? For those who can’t read between the lines, I’m talking about crowd sourcing the LTE Internet connection on your wireless device on your hip or in your vehicle.

Think about the power outlets at the airport. Just a few short years ago these were a hot commodity. Their locations were secretly hidden, and shared only after giving the proper handshake between passing road warriors.

Today, many airlines are investing in passenger comfort at the gate, which often includes charging stations in the gate areas, and long tables with power strips for plugging in and connecting. The travel industry has realized this was a minimal investment in passenger convenience and comfort that they could market to their base or travelers. They realized that most travelers today have several devices that need recharging before their long flight, and if you are traveling with a family that can easily add up to 10 or more devices. Having a place to connect and recharge is a nice amenity that makes their airline more appealing, at a minimal cost of investment.

Another example in airports is the open and free Wi-Fi coverage commonly available. Where it was difficult to find at all, let alone find it free, just a few years ago it’s available in many major airports today. This is typically through the airport authority itself, or taken care of by the presence of several local retail vendors like Starbucks or Dunkin Donuts to name a few of the more common entities that consider this a customer amenity that drives business.

We have already acknowledged that the next big technology in wireless connectivity (from a cellular perspective) is the 4G LTE technology. If you have a newer cell phone, and your carrier supports LTE, you already know the incredible speeds that can be delivered. In fact, I find myself tethering my laptop to my phone more often than searching for a hotspot that has decent bandwidth and throughput.

It was this practice that got me thinking. What if we were to take all of the LTE enabled devices that existed, consolidate them into one fabric backbone network, and then share that network with the Internet of Things? We would effectively create the Backbone of Things, or crowd sourced Internet.

Connectivity would become as ubiquitous as the electric in the wall sockets in a public place, drinking fountains and bathrooms. Does anyone still remember the pay toilet? Do they even still exist anywhere? Or have they gone the way of the pay phone?

This might just work, and I challenge those who may know better to come up with some flaws in my master plan for world domination and open access.

Related Articles:

Kari’s Law: An Emotional Journey Leads to a Bittersweet Ending

Our long journey leading up to the presidential signing of Kari’s Law began well before the precious life of Kari Hunt tragically ended on Dec. 1, 2013. (Learn about Kari’s story.)

For me, it actually began in the spring of 2013 when I noticed a sign on my hotel door, which read: “In case of an emergency, dial 0 for the operator.” I remember thinking, “The operator isn’t trained to handle an emergency. I should be able to dial 9-1-1 from my room phone.”

Sadly, this occurrence wasn’t an anomaly. I found it to be a common bad practice adopted by too many hotels across the United States.

There’s no doubt their intentions were good. Hotels were looking to be proactive, and they wanted to expedite not delay emergency response times. To make matters worse, direct access to 9-1-1 from Multi Line Telephone System (MLTS) was flawed because guests couldn’t dial 9-1-1 directly. They needed to dial an extra 9 just to get an outside line. That proved to be a fatal flaw in Kari’s case because her 9-year-old daughter couldn’t get through to 9-1-1. MLTS legislation also didn’t exist or, if it did, it was limited to a handful of states, and much of that dealt with the reporting location. It didn’t address the issue of access and notification.

Throughout the year, I used social media to increase awareness and drive meaningful change. I spoke at conferences and even began a podcast series dedicated to this very topic.

Then one day in December 2013, everything changed. My Google Alerts for 9-1-1 came up with a Change.org petition that was raised by Hank Hunt after his daughter Kari was brutally murdered in her hotel room.

I reached out to Hank on Facebook and offered to help him in his cause. Having an innovative tech leader like Avaya backing me increased Hank’s confidence in my ability to help him bring about the changes he sought.

My previous experience immediately proved useful, and we were able to go straight to the top at the FCC. (I had served on the Emergency Access Advisory Committee under Chairman Julius Genechowski, who had just turned the agency over to Chairman Tom Wheeler. Talk about timing!)

Following a number of tweets and letters, including an Open Letter to the FCC Chairman Wheeler, we received a call from Commissioner Ajit Pai’s office and a meeting was scheduled for Jan. 10, 2014. That meeting turned into a 45-minute discussion on the issues, the fix, and the challenges we faced.

Over the next several months, Hank and I garnered the interest of legislators in cities and states across the country: Suffolk County in Long Island, the state of Illinois, Maryland, et al.

In Texas, Avaya participated in hearings, and offered our unique expertise. We introduced the idea of a “Waiver Clause,” which stated that a business could obtain an exemption if they showed financial hardship. With the exemption was the requirement to register the make and model number of the system. This uncovered many systems that were actually capable of being compliant, and eased the adoption of the new law.

More states followed embraced the legislation—it was a full-on domino effect—except at the federal level where every attempt to bring a bill to life stalled. But then in 2018, that changed too.

After an all-night session ending on Feb. 9 on what would have been Kari’s 36th birthday, the House of Representatives passed the Senate amendment of H.R. 582, and it was officially on the way to the president of the U.S. for signature.

We quietly celebrated, knowing Kari’s murder would not be in vain.

The cherry on the cake was being invited by Hank, Kari’s father, to witness the president sign the bill into law on Feb. 16, 2018. I was both humbled and honored, and invited my former colleague Avaya Sales Engineer Dan Wilson to enjoy the moment with us. Dan had worked tirelessly on this legislation, clocking 12 miles of walking in the Maryland House and Senate.

The West Wing is everything you’d imagine: intimidating, wonderful and a once-in-a-lifetime experience. It was a pleasure to not only stand beside Hank and witness the signing, but to also be in the company of people who supported our endeavor since day one: Ajit Pai, my good friend and now Chairman of the FCC, Congressman Louie Gohmert who introduced the bill, as well as other Congressional reps with interest in public safety. After reading a prepared statement, President Trump uncapped the ceremonial pen and placed it on the paper. As it started to move, we were overcome with emotion. To think, 50 years to the day, and quite nearly the minute, following the first ever 9-1-1 call, Kari’s Law had become the “Law of the Land.”

Transforming Online Meetings for Team Collaboration

I find it interesting how companies choose to measure team collaboration. Most use surveys, some productivity data, and others standard review processes. Yet team collaboration is about so much more than all of this. If you ask us, it’s about putting people first.

We mean this quite literally. It’s important to provide employees with a suite of face-to-face collaboration capabilities that enable dynamic, real-time team collaboration. Communication staples like voice and chat are surely important, along with the endless other tools teams use to connect and share information. Meeting via video, however, is arguably the best way to collaborate, build relationships, create momentum and build morale. Face-to-face collaboration may not always be needed, but companies will want to make sure they have the best tools in place for when it is.

When done right, online meetings enhance team collaboration in several ways. Consider the most basic of them all: a good part of communication is non-verbal. Being able to observe team members’ body language can help prevent miscommunication and connect across languages and cultures. The technology has also evolved to the point where teams can flexibly share data, documents and other project details via screen sharing or virtual whiteboards. All the while, there’s the opportunity to initiate private chat sessions between team members to discuss simultaneously.

The bottom line: online meetings enable authentic human interaction that delivers real value, time and cost savings, and better business outcomes.

Now, imagine being able to quickly implement an easy-to-use, cost-effective service that skips the capital investment and technical hassle of a traditional video solution. This is exactly what Avaya Equinox Meetings Online offers: a cloud-delivered application that allows users—both employees and outside contacts—to connect with their browsers (no plug-ins required) or mobile apps to effortlessly initiate and/or participate in online meetings. The service places priority back on people, which is where it belongs. Simple as that.

Don’t believe us? Read Nemertes Q4 2017 Enterprise Business Value Matrix for Unified Communications and Collaboration to see what they had to say. If you like what you see, or if you have any questions, please feel free to reach out to our team for more information via our webchat.

The Easy Button for IoT

I am sure that I don’t have to tell you how the Internet of Things (IoT) is revolutionizing our world. Stop by any electronics retailer and you will find smart TVs, smart lights, smart refrigerators, and smart thermostats. Open up the brochure for a new car and you will find more space dedicated to intelligent sensors than horsepower. Tour a modern manufacturing plant and you will quickly discover that nearly every machine used in production has been equipped with an IP address. From the consumer to the enterprise, IoT is the driving force of innovation.

Of course, there is a dark side to this revolutionary technology: It’s not all that easy. As a consumer, it’s not a big deal to have one smart dryer that sends a text message when your clothes are dry. It’s also pretty simple to have your refrigerator email you a photo of its contents. In these cases, it’s just you and your machine.

However, what if you had a thousand dryers and ten thousand refrigerators. Let’s take it further. What if you were American Airlines and your fleet of airplanes had five hundred thousand different sensors reporting information every second. Now, imagine that some devices reported data using Bluetooth while others used Zigbee, WiMAX, LTE, WiFi, and NFC. Want to make it even more challenging? These different sensors report data reading using SOAP, REST, WebSockets, and a myriad of proprietary protocols. It quickly becomes an engineering nightmare to collect, store, and take the appropriate actions on this constant stream of data.

One Bite at a Time

Question. How do you eat an elephant? Answer. One bite at a time.

As with an elephant, the best way to conquer the IoT problem is to break it down into bite-sized pieces. Instead of trying to directly deal with all those different sensors and their unique forms of communication, have those sensors talk to gateways that understand multiple IoT dialects. Those gateways could then normalize the data before sending it off to a central cloud repository. Next, wrap the IoT cloud with web services that allow for a consistent and uniform way to access IoT data. Finally, use those web services to create a suite of applications for data visualization, event processing, analytics, etc.

Now, instead of being inundated with terabytes of data that may or may not be important, you only see what you need to see and only when you need to see it. You also have a scalable platform that allows you to add new sensors without having to constantly redesign and redeploy your business applications.

At Arrow Systems Integration (ASI), an Avaya A.I.Connect partner, we call this distributed architecture of sensors, gateways, and cloud services Arrow Connect™.

Arrow Connect

Arrow Connect is a software architecture that connects any device over any protocol to any cloud. Designed and developed by Arrow with security, scale, flexibility, device management, multi-tenancy, hierarchy, open APIs, and extensibility as its core principles, Arrow Connect is helping customers across multiple industries bring their products to market faster.

The Arrow Connect software development kit (SDK) helps enterprises leverage the full capabilities of any device while an extensible software gateway allows developers to add support for protocols and sensors not currently supported by Arrow Connect.

The Arrow Connect cloud platform enables secure provisioning and management of all its devices. It runs on multiple public cloud platforms and seamlessly integrates with Microsoft Azure, IBM Watson Bluemix/Softlayer, Amazon Web Services, and private data center solutions.

Breeze and Zang Workflows

While support for RESTful web services is essential to being an open and secure cloud solution, this comes with a price and that price is complexity. Despite being an open standard understood by most software developers, the fact that you must be a developer to use web services confines them to a very select group of people.

In our quest to find every possible way to simplify IoT, ASI has partnered with Avaya to add support for Arrow Connect IoT devices, sensors, and gateways into Avaya Breeze and the Zang Workflow Designer. With both of these platforms, access to IoT data and Arrow Connect services becomes as simple as drag and drop and non-developers can create powerful IoT solutions in a matter of minutes. Better still, this simplification does not come at the cost of accuracy, reliability, speed, security, or scalability. The visual tasks embedded in these workflow tools employ the same Arrow Connect web services a skilled software developer would use. The difference is that there is no need to learn Java, .Net, Python, or any other programming language.

 

The Easy Button for IoT

With integrated workflow technology, you can quickly turn an idea on a whiteboard into a fully functional and easily deployable solution.

Next Steps

McKinsey recently said that “Any business that fails to invest heavily in the IoT in the next 10 years is unlikely to be able to remain competitive.” While these may seem like strong words, industry after industry has taken them to heart and the IoT revolution is everywhere. As I stated at the beginning of this article, IoT is becoming pervasive for both consumers and businesses.

The simplification, scalability, and security of IoT offered by Avaya and Arrow Systems Integration helps an enterprise to create the solutions it needs to enhance its business, grow its customer base, and stay competitive.

Andrew Prokop is the Director of Emerging Technologies at Arrow Systems Integration. Andrew is an active blogger and his widely-read blog, SIP Adventures, discusses every imaginable topic in the world of unified communications. Follow Andrew on Twitter at @ajprokop, and read his blog, SIP Adventures.