Here we will cover how does communication service providers differ from the cloud service providers, and describe a little bit of trending that is happening in the industry today. On this picture, we have on one side are all those customer connected through different ways that we were covering before on how they're connected to the current network. They can be broadly categorized into consumer on one side and then enterprise and government to the other side. This is not full encompassing categories. Obviously, there is more granularity to it, but for simplicity let's give it this way. Then they are further connected onto the distributor network of communications service providers, that's again for simplicity, we will split into the core and into the edge, where core is for commSP own workloads and services, and Edge is for both comms workloads, but also for the customer workloads that need to be run from there, and on appropriate platform. So, and then on the vacant sides we have typically hyperscale cloud service providers, that there is very interesting trend that is going on for a while, so they are both building their own edge sites or providing their appliances for enterprise IT data centers on premise. So, this way they allow enterprise and government to build hybrid cloud environments, which have huge scale, easy, very clean APIs, so easy for on boarding, and provide this experience on premise on the edge, and also on the platform backends. So, somewhere in this communication service provider world, we have the core network. This is where we were applying this transformation for now about six or seven years, virtualizing and software defining these types of platforms, and from there we can now for many years in production receive those services. Where in the present government for example, there are many different verticals, very specific or on their own. Also sometimes fragmented between countries or major manufacturers for example, cars. They are running their own IT environments they have their own ecosystem of software renders and system integrators, and now the question is, where are they going to be running these type of workloads? So, they can run it on premise, they can run it on public clouds, there are these separate environments that I mentioned already, and the idea is that's on the edge of communications service provider network, we also provide edge platforms that can be hosting these type of workflows from enterprise government, and eventually this way receives some services revenue into vertical out of very rich other verticals. So, to do that, because they have their own specific ways of doing things, on one side's value of this location needs to be provided, APIs also need to be clean and consumable, and on the other sides there will be requirements coming from those verticals, and only then we can receive those workloads and run it over there. So, this is already ongoing on the edge of some specific cloud service providers, or it's already ongoing by then providing appliances on-premise so it's not that there are no other options that enterprise IT people have. So, this is how all these trends fit together, consumer and enterprise being also targeted by the cloud service providers with various over the top and hyperscale offerings. So, now if you look at very specific platforms inside this distributed network how to do that, there are different ways on how this can be achieved. The idea is that regardless of the location, and regardless of what is going to be running in software on top of those platforms, that they are exposed in this the case as virtualized in the same way. So, that's the same virtualization layer spans across different locations, and once we do the on-boarding of the application which is then in software VMs containers and some functions that we on-board it once on the platform. This way we can then, across different services domains, provide the integrated services. The reason for doing that way is that on-boarding platform is easily consumable, and we can provide the services across different domains, which would not be possible if we are building specific Edge platform for video services, and that specific platform for IoT services, and then we generate very unfortunate silos that in some cases might be also even good idea because they might generate revenue fast. So, to achieve that critical is to keep the obstruction layers very separate and clean, not to break those obstruction boundaries, so that for example this physical parts of the platform on different locations are being run by the physical infrastructure the manager, virtualization, or containers layer is being handled by the Virtualization Manager, and applications are being handled by application management services by service orchestration. So, this way not just that we have decoupled the applications from the platform and we can be of service that way based on applications that are coming from different domains, we also ensure that the whole on-boarding is easy because of the way how we layer it. All those different service application, virtualization and physical infrastructure managers. So, that way we keep those layers of obstruction between the platform infrastructure applications and services.
