 Over the years, we have connected billions of people. We have laid the foundation for innovation and growth. And we have brought it everywhere. But this time, it's different. Now, our IoT, 5G, and automation technology stands ready to unlock a wave of new value. We're talking operating rooms connected across oceans, trucks communicating to increase efficiency, and factory floors going fully digital. We'll see waste reduced, accidents dramatically decrease, and remarkable new business models come to life. But we're getting ahead of ourselves. To make this a reality, we're on a quest. To make technology easy to use, adopt, and scale. To build an ecosystem together with our customers where change is easy, where standards are global, and where the full value of connectivity can be realized faster than ever. Getting to easy won't be easy, but we're determined to lead the way, to move fast, to knock down barriers, and to cut through complexity. Join us. OK, it's my pleasure to introduce Matt Carlson from Ericsson. He's the head of R&D portfolio and digital services at Ericsson. So, Matt, please welcome. So I'm very happy to be here. I think it's a good session with the Open Network and Summit, and what the Linux Foundation has done. Quest for Easy. I think one of the reasons why we started with Quest for Easy, because I think that is very much the reason why I go to work. I think we're why you go to work. I think we're all trying to make things simpler. I mean, we're trying to make a software stack simpler to kind of use. We're trying to make our products and services simpler to use, quicker to deploy. Everything should be quicker, easier, and simpler. I will be joined a bit later with Verizon, but I will start with actually talking about 5G, not as a radio standard. I think there was a lot of radio in the video, but very much as 5G as a platform for innovation. Where is the clicker? And also, talk about the role of open source when we're actually building the 5G networks. I mean, telecom has been used to provide their boxes. That is not how it works going forward. So really about also the role of open source and the community as the driving force for building the future networks. So what is the difference between 5G and what we have done before? I mean, all the telecom networks that we have done historically, like 2G, 3G, they have more or less been focused on only providing two basic services, voice and data. What is then the difference between 5G? 5G is completely use case driven. That means that we don't really know what services the 5G network would need to provide. Of course, there will still be a need to provide the basic data services, et cetera. But a lot of the new services coming in, they are not kind of, they are developed outside the network. Of course, 5G is also a technology leap. We are developing new radios. We are developing a new core. But what we also now doing is that, are we going to use the networks? Are we going to monetize the network? How do we actually make sure that we have networks that are fit for the purpose, for the use case or the services that we are using? So the network needs to have the capability to supply multiple use cases. And each use cases may have completely different characteristics needed in terms of latency, in terms of bandwidth, in terms of cost points you need to hit for that specific service. We also need to be able to have multiple monetization path. Business to consumers, of course, very much what we are doing today. But business to business, business to business, to consumers. And of course, we need to be able to create and deploy services in hours and minutes and not maybe month or weeks or years even. And of course, all is supported by a serotouch operational model. We usually divide the five use cases in what we call massive machine type communication, critical machine type communication, and enhanced mobile broadband. So if you look at massive machine type communication, that is a lot of that we can already do today with the current radio standards. But that is typically a smart meters, logistic, asset tracking, fleet management. Very much driven by low cost, low energy, small data volumes, massive numbers. I mean, to look on some of the small data, I mean, if you for instance have a birdie alarm, most cases it doesn't send any data at all, but when it needs to send the data, it better work. Then on the other side, we have the critical machine type communication. And here is more like industrial use cases, industrial robots, remote control, haptic control. I mean, this could be like requiring extremely high reliability, extremely low latency, and of course, an extremely high availability. On the bottom, we have the more or less existing business that we are today. But of course, with the enhanced mobile broadband, when bandwidth is increasing, when latency is going down, of course, we can support much more like 4K, 8K video, augmented reality, et cetera, when we're having applications that are much more kind of latencies critical than the current application. Of course, when the latency is going down from like maybe 30 milliseconds on the axis down to like two milliseconds on the axis, then of course, a lot of new cases opens up. But of course, we're talking very much about 5G, but of course the radio 5G, that is rolling out more or less like next year or 2019, 2020. But a lot of the things that I'm discussing today, for instance, on the massive machine type communication, that is already happening today, and we are rebuilding the core network already today to cater for these type of new services. And of course, the opportunities are endless. Open source, I will come back to that one on the next slide, but when you're looking on the development of the infrastructure, you will kind of see how much different open source products are needed to kind of build up this infrastructure. And also on the use case level, we talked about the AI machine learning and the apps using 5G and wireless connectivity. A lot of that ecosystem is also of course built around open source. And of course, for us, it's really about enabling the industries and the people to take the next step in the digitalization journey. So 5G, it starts today or it has already started. 5G requires a software defined networking. It requires complete programmability of the networking. And of course, it starts already with like NFE and SDN because we need to be able to have a flexibility in deployment of our application. We need to have flexibility in actually adapting the network to the needs of the applications. And of course, going forward, going into cloud native and Edge cloud. But we also, of course, doing a lot of things also on the application side, for instance, splitting up the control pane and the user plane to be able to move out the user plane further out in the network to do Edge compute. But also have more like modularized applications like, and of course, going into the microservice and container-based application. Management and orchestration, same thing. We need to break the silos that we have had in the OSS system, have a horizontalized, model-driven management and orchestration very much about what we are doing in Onup. And of course, adding the machine learning and artificial intelligence to reach to automation and serial touch. It needs to be able to distribute workloads. We need to be able to put applications further and further out at the Edge, but maybe also in some cases all the way out to the base stations. We also need to be able to have network separations, resilience and isolation to be able to handle different type of needs from the applications and use cases. Network slices, very much we are discussing. Network slices is more or less the capability to create logical isolated network within the network that you can, for instance, have for specific services. You can have that an enterprise actually owns a specific slice within an operator network or it can be done just to making sure that certain of your services are having the most optimal network infrastructure for that specific service. Of course, having the total cost of ownership for application lifecycle management reduce time to market for the service creation and the service deployment. And of course, when you're looking all this, you probably see that a lot of these areas that bring up as the past of five is depending on the role of the open source and the communities that we are talking about here today at this conference. And of course for us it's really very much about contributing, using and driving the development of a number of these open source communities. So another thing is that open source and standards and standards I mean very much the classical, you call them sometimes paper standards. But within telecom, there is a need still for, I would call like paper standards like 3DP and Etsy. And the reason is that if you're going to build a 5D ecosystem with like billions of devices, it's pretty important that the interface between the device and the network is pretty stable because there is a huge ecosystem and investment. But on the other hand, there is also a need for increasing speed in innovation. And that is where open source comes in. So I think in five years, I think this is really the first time now when we're actually combining these two forces into one. So if you look in open source, open source, what does it bring to the table? Speed, it brings code, it brings a way that we actually work together in this room. It brings innovation and it's bring merit bias. Whatever is kind of, the best thing will kind of win, so to say, it's a bit of a Darwin's law. But there is also some drawback sometimes on open source. I mean, how do we make sure that we get better interoperability between the different open source products from a lifecycle management perspective? There is sometimes competition. There is a lot of open source product that is trying to solve the same thing. And I think this is of course what the Linux Foundation Network is trying as well to kind of making sure that we can be better and quicker on that one. So standardization on the Hadan, giving a lot of global scale. I mean, the reasons why your phone works across all over the world is very much about what 3DPP has done. It's focused on interfaces and functionality, and that of course give better interoperability. And of course, it provides a bit of a long-term outlook and backwards compatibility. So if we can do this in a very smart way, I think historically this has been a part. I think now we need to bring them together. And sometimes they've even been contending for the same spot. But if we do this good, I think one plus one can be bigger than two. So I firmly believe that these two groups needs to work much, much closer together to kind of speed up that we're moving the industry quicker going forward. So I would like them to introduce, we are working very close with Verizon on 5D here in North America. I think it's also very good to sense of collaboration, how we are working together. So it's a pleasure for me to introduce Mr. Anil Guntapalli, Executive Director of Architectural Planning within Verizon. Welcome, Anil. Thank you, Matt. Thank you, Matt. And it's really great to be here. And last three days has been revealing from a lot of exciting conversations. So thank you for the Linux Foundation and team for organizing this as well. But let me give you a perspective of what Verizon, in the context of the 5G, as well as much more importantly, what the role of the open source is. And for us, how we are looking at that and some of the challenges and the opportunities. I mean, the most, the perspective I want to paint today is that our customers are demanding experiences which from our network, the ask from them is growing every day, right? I mean, they are asking for experiences which can be delivered by a network which can be driven by whether it's 5G or it's stitched together with a network and connectivity fabric. It's core of our fabric, but much more importantly, what we are kind of enabling there is trying to deliver those services for our customers which are new, which they have not experienced before but they're asking for low latency services. Whether they're asking for use cases which are like V2X was as mobility experiences which they have not kind of experienced in the past, right? The way we are driving that is obviously in the core of this one is 5G. 5G enables low latency. 5G enables ultra bandwidth but we are also kind of driving that with putting the fiber much more closer to the customers. But 5G also enables us to look at our network completely differently, right? In the, from the, we are transforming our network in the perspective of that, it gives us a way to take a step back, relook at that and the, in the perspective of like laying out, you know, whether it is like redoing the slicing of the network or building, enabling, pushing the compute much more closer to the customer because once you push the compute much more closer to the customers, we can enable services like, you know, whether it's mixed reality which demand like 10 to 20 milliseconds latency from the network, whether it's V2X which are much, much lower latency requirements. But underlining, underlining that is a fabric what we kind of fundamentally believe in three pillars and within Verizon. It's different, it's software control, right? I mean, we drive with the software defined networks but much more importantly, we are focusing on closed loop automation with cognitive fabric and putting AI up front in there and then the other most important block is not an aftermath but it's open source. The three main things what open source enables us for us is very selfishly, right? I think it takes the complexity out of the network. From the perspective, we spend a lot of the time, you know, looking at integrating the services, making sure they're working together, interoperability. That's where we spend time and we make sure that the network is up and running all the time. But then, if the standards are good and open source works as it is, we can focus much more on driving what our customer needs are, right? I mean, we want to take the cost out of the business. We want to focus on what, delivering the services on the layers up, right? Again, for us, Network OS is the core fundamental portion of it. It gives us the agility and it is driving the services what our customers are needing. But there's obviously some challenges with open source as we look at it, right? There's, I mean, we are participating in a lot of the groups, but as some of you would agree here, is that there's a lot of subgroups forming in pretty quickly. And there's very less time for us to focus on each one of these subgroups and to participate in it. I mean, our biggest challenge is that, you know, I mean, it's like almost like a new shiny object that some of us are running to that one. What I ask and probably look at inwardly is that, you know, we should not, I mean, at least for us from this community is that, let's try to make sure and work together to make a buildable solution, right? I mean, let's get the reference architecture right. Let's get the blocks right. Make sure that is working before we move on to the next project. Again, as you, whether it's a startup or a large vendor, I think everyone has resource constraints. Let's focus on the needs of the business. Again, going back to the previous conversation, it's like more about, I want to focus more on delivering the services rather than trying to fix the interoperability issues and the other challenges in the network. And inwardly looking self-critical, right? I mean, we are trying to change our mindset as well that we want to move from one single accountability. We want to be multi-vendor. We want to encourage the ecosystem to collaborate and work together and we're gonna be right there with us. Again, it's a mind-shift change and we kind of embarked on that culture and then we kind of investing in that, right? But some of these barriers about making sure that there's not too many sub-projects and there's interoperability, I think, is, I think it's slowing us down. I think we need to get to a deployable solutions. I definitely ask this community for that help. And most importantly, what am I asking my vendor community here, right? I mean, again, we're not here to drive, you know, basically it's not a race to zero, right? We want you to take the reference architectures and or the open source and innovate, but make it multi-vendor interoperable. Participate in that ecosystem, right? I mean, the end of the day, whether it's a small vendor or disruptive vendor startup, I think that's the notion what we model what we would like to embrace as well, right? We want to make sure that it's compatible. It's, at the same time, it is simple enough for me to put it in my network and then I'm able to expedite the introduction of the technologies, whether it's 5G versus any other network. End of the day, I want to focus on delivering the network. I mean, services for my customer. And we are right there by providing the commitment from our side is by we are investing in resources. We are going to commit the code back to the community as appropriate and whenever it makes sense. But we want to make sure that the networks are simple and we are able to innovate pretty quickly on top of it. That's the final last from me. And again, this great partnership in this community, I mean, a lot of the stuff would not have been done without a lot of the contribution from you guys here in this community. Again, we thank, we can't thank you enough on that, but we also see there's a lot of work left, trying to, especially when you look at 5G, there's a lot of work left for us to accelerate and make it interoperable. So thank you. And with that, probably we'll take some questions here. We have, thank you. I think we have some very limited time for questions, but one maybe. We have questions, very good. I like it. I don't know. Okay, so I'll ask a question very quickly. Fascinating progress. I know you guys are leaders in this space and all that. Give us a little bit of a timing. There's the marketing guys, 5G's here and I can make a call. And then there is the engineers, which will be 2025. What is the reality? Maybe I can start. I think actually the core network and the orchestration solution, I think we're already more or less there today with these type of networks. I think we have to wait some time for the kind of a new radio, et cetera, but I think from the core network perspective and the OSS, I think we are, I mean, we have close feedback loop thinking today. We have that in our systems. And 5G's here now. I mean, what we are re-looking radio has worked extremely well. We are progressing with the trials and I think what we are looking at is the opportunity to redefine the core network as well in a way that it can scale and work with it. And I think we are on the right path and we'll get there pretty quickly. Very good. Thank you very much. Thank you. Thanks a lot.