Cisco Blogs
Share

Drones and the Internet of Everything: Where Does Cisco Fit?

- September 10, 2015 - 2 Comments

Earlier this summer I was privileged to be the closing keynote speaker at the UTM Convention, sponsored by the Association for Unmanned Vehicle Systems International’s Silicon Valley chapter. The convention took place at the NASA Ames Research Center in California, and focused on the unmanned-vehicle traffic management (UTM) aspect of drones.

Helder Antunes spoke about the Internet of Everything and drones at the UTM Convention in July.  Photo Credit: NASA Ames Research Center

Helder Antunes spoke about the Internet of Everything and drones at the UTM Convention in July. Photo Credit: NASA Ames Research Center

You might be thinking, “Cisco is a networking company, why would you be involved in a drone conference?” Well, drones have to be connected, and that’s what Cisco does. They transmit massive amounts of data that must be collected, sorted, and analyzed. This is exactly where Cisco should be playing.

Drones are a nascent part of the Internet of Everything (IoE)—the intelligent connection of people, process, data, and things to create new value and opportunities. IoE represents the next wave of the Internet, and will impact virtually every part of our lives. Today, however, the use of drones is limited because the technology has far outstripped policy. Realtors may use drones to take aerial photos and videos of property for sale, and there is starting to be some use of drones for search-and-rescue missions. But on the other hand, unauthorized drones have gotten in the way of aircraft fighting fires in the western United States this year, and the City of San Jose’s police department has yet to deploy the drone it acquired nearly a year ago because of lack of clear guidelines for its proper operation. That is why the traffic management discussions at the UTM Convention were so critical.

Once an appropriate regulatory framework is in place to ensure safety, security, and privacy, drones will become a fast-growing part of the things segment of IoE that will spur innovations in how people connect, revolutionize processes in unimagined ways, and change where and how data is collected, analyzed, and used.

Here’s just one example of where Cisco and drones could come together in a “sweet spot” of innovation: Much has been said about smart vehicles connected to an intelligent transportation infrastructure in urban environments, enabling better traffic management and improving safety. However, when you go to a rural environment where cell phone towers and Wi-Fi access points are few and far between, the challenges are much greater. In this case, a drone can actually become part of the communication infrastructure to augment roadside connectivity. If it has intelligence, strong data processing, and analytics capabilities, a drone can perform many of the same services as an urban smart infrastructure—reporting emergencies, road hazards, and traffic problems to improve road efficiency and safety.

I believe Cisco will have a strong role to play, along with an ecosystem of partners, as this new element in Internet of Everything finds its place in society. What do you think? Where can Cisco make the greatest contribution to the intelligent development and deployment of drone technology?

 

Tags:

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.

2 Comments

  1. Would a drone be considered as a single IoE? A drone itself might have multiple IoT sensors. Can a drone act as a router for other drones? Do each drone connect to the gateway? Pls elaborate.

    • A drone can indeed be both. Either a part of the IoE infrastructure, for aggregations and transmission of data or as an IoE node itself. It can act as a router of information aggregated from nearby drones (think clusters). Lastly, if once again you envision a cluster of drones, one could indeed act as a gateway for the others or depending on the data/processing load, each could also have it's own gateway. All of this is predicated on the use case.