So, we've mentioned some of those 5G use cases and we've driven the point home, that they're going to have different requirements under the network itself, and particularly into the core of the network. This is not only how we build the network, but how we're going to operate the network. So, we mentioned Network Slices. So, when we look at this plethora of devices that are going to be out here, they're going to be classified into a variety of different areas, where there's a massive IoT, Home Sensors, Cameras, Mobile Broadband, Mission Critical IoT. In each of those use cases is going to place a different expectations, different demand, a different level of service requirement onto that network itself. We certainly don't want to build infrastructure that supports those uniquely, but rather common infrastructure across them. If you've got for example a massive IoT because it's associated with industrial application, you're supporting a factory that has a lot of sensory activity that's flowing back to the network. You may allocate a very large slice of those resources in the core of that network from the radio itself, all the way back into the deep portions of the core of the network for that capability that's in there, whereas if you've got another application location, let's say it's more of an educational institution. Their utilization may be somewhat different and their expectations and you would allocate the slice of that network as a different percentage of those resources that you've got in there. So, that finally go this and from the random, the network itself, all the way into the core of the network. Certainly, in 5G, we're going to see that deployed from the beginning as a network slice or you may even see some use cases. We're going to take that concept of Network Slicing and we'll get back into some of the support systems from a legacy standpoint into that network, but it's certainly going to impact us when we begin deploying at 5G network. So, there's vertical slices, again we've talked about this a little bit. I'm going to allow us to distribute the functionality, and not only with EPC. We're starting to see applications themselves even in today's environment in pre-5G, where functionality from the EPC is starting to be drawn closer to the edge to support the upcoming demand of those types of slices. So, whether those are smart phone connected cars or wherever that happens to be, that functionality is going to be distributed in a variety of areas. That may in fact, also allow us not only to distribute the functionality, but it's not distributed discretely as we may have bits of functionality from the EPC, that particular use cases get distributed very close to the edge, and for other use cases that Network Slicer, that EPC functionality may actually reside deeper into the core of the network. All of that is going to be latency, based that is the closer we get to the edge, the lower the latency is going to be for that type of service. So a round trip delay for things, either from a signaling standpoint or from a data standpoint are going to be lower, and that may be necessary, again, depending on the use case. But that doesn't eliminate the fact that we can also display, for example, that distributed EPC, where elements of that can be deeper into the core of the network where we've got the ability to supply a greater number of users. So, for example, you might want to think then about the typical Mobile Broadband user password handset. There EPC functionality deep in the core of the network is going to be sufficient, but for connected car, you may need that functionality of the MME to be closer to that endpoint, and from a single radio tower, you can have a mummy action access inside that EPC distributed and based on the class of service and the type of user that is subscribed to that service that point in time. So, this SlideShare it gives us an idea that it's not necessarily a one size fits all. That's a revolutionary bit of thinking in the way we play and operate our network. So, again transforming that network, and that's taking place from our legacy purpose-built, custom proprietary, and hardware. Then, using the technologies of NFP and orchestration to desegregate to decouple those workloads from the standard network compute and storage so that it looks more like a cloud ready type of an operation where we can grow the compute resources. We can plan those things out a longer-term without saying, okay, this resources is actually going to be demanded in six months of time because I know that we're going to have a particular bit of functionality as we may be able to build those computer network resources independent of the actual use case itself that's there. Then similarly, use our analytics that are coming about the platforms themselves, have platform awareness capabilities that provide more information back into an operations team than they did in the previous generations. So, those planners can derive analytics in a more Cloud native way that tell us about the consumption of those resources so that our planning cycles are more manageable, and certainly that's part of the transformational and organizational change. It's not just about the technology, but about the way we build and operate those networks themselves, and 5G is going to be the first place where we get to test that, where we get to try it, and it's going to come into play and provide a significant improvement over the business models of the past. So, really what is 5G? From that standpoint is that, it's going to give us that modern software-defined infrastructure, sometimes called SDI. This is an area did until this very much engaged and its needs to be supported from the foundation of the technology itself. So, just like when you're building a strong building, you've got to have a strong foundation underneath it as we've got to put technologies into our compute resources into our network resources. And enable those through APIs that drive that into the upper layers of the infrastructure so that we can do things like monitor for power and control the devices, power consumption based on their utilization of the time of day or the amount of traffic that's in there, have very tight control over the performance so that we can detect when a system is reaching those predetermined threshold ahead of time, and then use controls inside orchestration to spin up additional resources. Security is never-ending concern that we've got, you built and tested trust from the bottom up. We talked about how platform themselves coming out of manufacturers can be certified as known good entities, and at any regular maintenance activity, those can be re-validated in addition to taking that technology of security all the way up through the application level itself, where you've had to a very tight security signatures that can be placed on those excusable images. When they get instantiated those can be validated and be assured that they've not been tampered with along the way. Their mostly utilization obviously are very important, as we mentioned before in some geographies so is the location of those devices itself. So, there's a way to sign those devices and ensure that they are functioning correctly for the security requirements that certain regulatory agiles and may place on on data sovereignty. All of this pushes back onto the software of the orchestration layer that controls and manages plaques, consolidation point for this, ultimately to allow us to look at those service delivery elements into that environment. So that again, we can do things like the Network Slicing that we talk about. We're spinning up particular functionality for content delivery or firewall implementation that may be necessary is. We're providing services through let say, a fixed 5G interface into some type of enterprise where it would be too costly or location prohibited to dig the ditch or build the trench and bury the cables. You may also want to think about emergency type situations where you're going to spin that up. These are all types of elements of an Agile service delivery that's going to be enabled. But through this SDI, that's coming into the network as a result of some of the pressures that we see in the opportunities of that 5G network. So, as a conclusion of that portion or a consequence of that portion we see that we're actually opening up the network itself to look more like a Cloud can enable service. So, we're unleashing that potential, and the comp service providers are looking for that opportunity opened up new business opportunities for them. It is going to give them more control over the workload and usage than they've had in the past, which is a very good thing for them to be able to manage your business in new and creative ways. The opportunity to create new services in the Cloud also is there, because now we've talked about the platforms themselves and how these are going to be decoupled platforms with computer network resources in there, and it's certainly possible that those resources can be utilized in new and innovative way. So, we've not thought of today. In the end of that is to enable those Cloud deeper insights, that allow us to innovate into that network in a more robust way possibly. So again, Network Slices are going to be critical in that network to provide us with high-capacity broadband connectivity for those devices that needed, the ultra low latency for those the devices that have that type of requirement. The change in the protocols to themselves, to allow low energy consumption devices that are out there as well as extreme ultra high bandwidth utilization. So, whether that's some type of gaming or e-sports type of experience in building all that technology into the core of the network. So, putting it all together. So, we've got Radio changes that are coming on. This is new spectrum, this is new set of protocols. We're looking at changing the way we build those radios. Again, we can distribute bits of functionality, and that radio we can break it a layer one layer, two layer, three layer, and put the functionality as required at that radio tower that's necessary from a power standpoint or utilization standpoint, or geographical location standpoint. Increasing the compute and storage opportunities in the network, that allow for that growth of opportunities in there, and then the support that wide range of devices that are out there. All the end of it is to build that network as we continue to move forward revolutionary but incremental way so that we've got a better user experience, lower latency, and then still support that data that's streamlined in a global approach to a standard that will scale.