The Internet of Things (IoT) has been among us for a while, but in recent years we have seen a change in scale, in part due to cheaper sensors that are emerging. Cities are deploying sensors to improve the quality of life for their citizens, while factories are connecting more and more machines and collecting more data about the production processes. Supply chains are being revolutionized by tracking in real-time not only position but also movement (shaking, dropping), humidity, etc… In almost every industry you can see the impact of IoT.
Due to this change in scale new challenges are starting to emerge that are demanding a rethink of the Cloud only paradigm, and the silo approach to IoT.
IoT typically means deploying application intelligence and analytics at the edge (the area between Cloud/data centers and end points such as sensors, factory robots, etc…), or pushing data directly to the Cloud for processing. Both approaches have their advantages as well as potential drawbacks.
The network between the edge and the Cloud can be relatively expensive (especially if you send all data to the Cloud) or has limited capacity (capacity is of course correlated with price). Latency to the Cloud can also be relatively high, and often lacks determinism. For example changing the color of traffic lights via the Cloud might not be optimal.
More and more solutions are being deployed at the edge to address the challenges Cloud faces. But these solutions have their drawbacks too. Many different solutions (hardware and software) make it more challenging to manage these edge services in a consistent and coherent manner.
IoT deployment is typically not confined to the traditional enterprise IT domain (au contraire). This means that traditional security solutions do not always apply, resulting in potential high risk security breaches: it is not only about stealing data, but also about controlling machines For example manufacturing robots, location of vehicles, …
One of the trends that we are seeing is that providers of edge services want to focus on their service (application) as this is where their expertise is. Today however many providers also need to provide the hardware (not always a good source of revenue), a certain level of security (not always their primary level of expertise), and a way to manage their services and devices (which can pose a challenge if a customer deploys multiple silos of IoT services).
A Unified platform beyond Cloud only
To address the challenges described above, a rethink is needed. On one hand the Cloud only paradigm is not sufficient, yet such a new platform needs to support a Cloud like methodology for the edge.
Fog, a driver for IoT
The emphasis here is on “like”, as the edge differs from a Cloud/data center in several important aspects such as: limited resources, limited network capacity, security challenges, and resource distribution. However, such a platform will also have things in common with Clouds. Just like in a Cloud environment it needs to manage the (edge) service life cycle and orchestrate deployment.
With such a platform in place, edge service providers can focus on their core business as this new platform provides them with hooks to develop, deploy, scale, monitor, and manage their services in a secure and safe environment while seamlessly connecting to the Cloud.
Moving to Cloud and beyond
The vision of such a unified platform has been described by Bonomi et.al. and labeled Fog Computing. We are now seeing this vision unfold in several distinct stages.
Unified (IP based) connectivity is typically the first stage. For example, cities offering free Wi-Fi in the city center, or factories that are consolidating their different networks.
Once unified connectivity is in place, it becomes easier to deploy services at the edge by connecting hardware to this IP network. This can lead to service silos, which are sometimes difficult to avoid due to legacy applications and hardware.
The next stage is the deployment of a unified platform (Fog platform) between Cloud and the endpoints to enhance service deployment beyond the Cloud but also to spur innovation by making it easier to share data between these services. This stage is where there is a true added value, as service management is unified and hardware platforms can become more consolidated.
This paradigm shift to think beyond Cloud towards a unified platform, will lead to new products, services and business models, but can also increases the risk of fragmentation due to lack of standards, architectural vision and abstraction. In order for this paradigm shift to truly succeed it is therefore important to have a continuous conversation between the IT and OT industry.
To ensure companies capture the value of IoT, it is important to start the thought process on a Fog and IoT vision early on: service deployments, connectivity capacity beyond Cloud, data filtering and analytics at the edge, device consolidation, real-time requirements, etc…
Such an IoT vision will enable companies to better prepare and understand the risks and opportunities in an increasingly connected world.
Tags: Corporate Strategic Innovation Group, CSIG, Fog, IoT
Building an IoT company is a great opportunity to work on things you have never done before. Here is a list of my conclusions with brief anecdotes about the difficulties of building az IoT company.
Choose the size of your funding need wisely
When we started, our pre-seed angel investor suggested to close an angel round by involving other investors. The more money you attract at the beginning, the longer runway you have to develop the product that you believe in without having to take away your focus from value creation. It turned out without having the credibility of using small investments wisely and build traction with it you won’t be given the opportunity to get funded with hundreds/millions of Dollars. Build up your credibility together with your venture. One step at a time. Read More »
Tags: #ciscochampion, internet of things, IoT
Nowadays, there are billions of devices connected to the Internet, and this has led to some advances in the Electronics and Telecommunication technology developments in recent years which resulted in various kinds of very powerful devices with communication and networking capabilities that have attracted the industries to adopt this technology into their daily business to increase their efficiency. Other than the industrial sector, there are other sectors like assisted living services, public services, etc., which have a big demand for Information and Communication Technology developments. Therefore, there is the need for a new paradigm in M2M communication which enables “Things” connectivity to the Global Internet Network. This paradigm is known by the term IoT.
IoT is the network of physical objects or “Things” embedded with electronics, SW, Sensors and connectivity to enable it to achieve value and service by exchanging data with the manufacturer, operator and/or other connected devices through advanced communication protocols without human operation. The technology of IoT has been evolved according to the environment based on information communication technology and social infrastructure, and we need to know the technological evolution of IoT in the future. Read More »
Tags: #ciscochampion, Cloud Computing, Fog computing, grids, internet of things, IoT, smart, smart grids
With the adoption of overlay networks as the standard deployment for multi-tenant network, Layer2 over Layer3 protocols have been the favorite among network engineers. One of the Layer2 over Layer3 (or Layer2 over UDP) protocols adopted by the industry is VXLAN. Now, as with any other overlay network protocol, its scalability is tied into how well it can handle the Broadcast, Unknown unicast and Multicast (BUM). That is where the evolution of VXLAN control plane comes into play.
The standard does not define a “standard” control plane for VXLAN. There are several drafts describing the use of different control planes. The most commonly use VXLAN control plane is multicast. It is implemented and supported by multiple vendors and it is even natively supported in server OS like the Linux Kernel.
This post tries to summarize the three (3) control planes currently supported by some of the Cisco NX-OS/IOS-XR. My focus is more towards the Nexus 7k, Nexus 9k, Nexus 1k and CSR1000v.
Each control plane may have a series of caveats in their own, but those are not covered by this blog entry. Let’s start with some VXLAN definitions:
(1) VXLAN Tunnel Endpoint (VTEP): Map tenants’ end devices to VXLAN segments. Used to perform VXLAN encapsulation/de-encapsulation.
(2) Virtual Network Identifier (VNI): identify a VXLAN segment. It hast up to 224 IDs theoretically giving us 16,777,216 segments. (Valid VNI values are from 4096 to 16777215). Each segment can transport 802.1q-encapsulated packets, theoretically giving us 212 or 4096 VLANs over a single VNI.
(3) Network Virtualization Endpoint or Network Virtualization Edge (NVE): overlay interface configured in Cisco devices to define a VTEP
VXLAN with Multicast Control Plane
Read More »
Tags: #ciscochampion, Cisco Nexus 9000, CSR1000v, Nexus 1000, Nexus 7000, Nexus 9000, VXLAN
#CiscoChampion Radio is a podcast series by Cisco Champions as technologists. Today we’ll be talking about Collaboration and Cisco Unity Connection with Cisco Technical Marketing Engineers Chris Ward and Chris Barlow.
Listen to the Podcast.
Learn about the Cisco Champions Program HERE.
See a list of all #CiscoChampion Radio podcasts HERE.
Chris Ward, Cisco Technical Marketing Engineer
Chris Barlow, Cisco Technical Marketing Engineer
Cisco Champion Guest Hosts
Michael Aossey, @aossey, Solutions Architect
Erick Berquist, @erickbe, Senior Engineer
Kim Austin (@ciscokima)
What is Cisco Unity Collaboration?
Unity Collaboration and Secure Messaging
Unity Connection and compatibility with existing solutions
Video greeting feature and media capabilities on Unity Connection
Benefits of Unity Connection over other solutions
Cisco native SRSV and Unity Connection
Cisco Unity Collaboration Overview
Data Sheets and Literature
White Paper: MWI Normilization with Centralized CUC
Tags: #CiscoChampionRadio, Cisco collaboration, unity connection