 So now I'm going to talk to you about what that community project evolution is going to look like. And probably a quick intro about myself. I lead the cellular programs at Facebook connectivity on the engineering team. And it's my great pleasure to thank you all for joining us today. During these times of pandemic struck at home and there really aren't a lot of things that are going on and you're all working and we still appreciate the time you're taking with us today. And hopefully you'll find it useful. And I'm quite excited to be speaking of the real keynote and this firecrack chat we just had with the greatest minds of the industry, especially when it comes to open source projects that have potential to disrupt the industry and bring the future closer to us, whereas less digital divide, less neutral network divide, and there is less division overall per se. And I'd like to talk about how we're evolving magnet. This project is very near and dear to me. Into a full blown community project with participation from a large number of contributors. We have big companies and startups, operators and service providers, industry groups and the ecosystem all aligned to build what we call the Kubernetes of the network core together. So let's do it. So let me start with a story that is actually a chapter out of the telecom project or CHIC project that Facebook connectivity has been supporting for years and in fact initiated it as well. And it's called the open and disaggregated telcos. Jio and Rakuten are the poster children of this movement and have proven to the industry that the clock is ticking against the big vendors closed and provided to the system. Dish wireless places open source right on their homepage, including a direct reference to OLAM that I've noted out at the bottom here. This rise is inevitable, especially from the standpoint of the future that we see. It's fully open in many cases open source. No software funded in the industry will be while a good part of the telecom industry may not. We know that there's been limited success of open telco or open source software in the telecom industry today. However, it is not an indicator of future by any means. On the contrary, this is precisely why we're investing and working on projects like Magma. At Facebook connectivity, our goal remains to land commercial success of Magma as well as other open source connectivity projects at scale, which help us bring more people online to a faster internet. Now let's look through how this announcement that we're making today or just made about Magma open source project becoming a neutral entity in partnerships with four major industry groups who are all lined up to support the project and disprove that status quo. So they are, once again, open interface software alliance, open interface foundation, Linux foundation, and telecom infrastructure. So as we continue that story, before going into the details, we draw an important parallel between the adoption of open source in the enterprise space versus in the telco space that we have seen over the past decade or so. The left-hand column shows the evolution of the open source in the enterprise space over the past 10 years or more. It's been triggered by Linux that is now in every part of the software industry. It's widely known that software is eating the word and we say that open source is eating software. The window of opportunity to disrupt the telco industry, especially with open source project, as we see on the right-hand column, is the next three to five years. The early indicators show there is a surprising common signature with every disruption that is happening in the industry now, whether it is Geo, Rakuten, Dish. And that is none other than open and disaggregated network and lots of open source code. This is hardly new or new to the industry and there are hundreds of open source telcom projects, perhaps more the merrier, at least in this case. However, it is very important to be mindful about potential fragmentation of certain parts of the telco stack. Today, we're gonna make a case about the core stack, which is known to be a lot faster in the closed telco systems. Going over to the next slide, now we draw a very important distinction between the RAN and the core in telco networks. A core network is naturally disaggregated and acts as the backend of the network. This is unlike RAM, which remain a black box with 3GPPs, S and N interfaces to connect the rest of the network for a very long time. We see strong open RAM movements that are currently underway and we just learned two weeks back that the four largest operators in Europe have committed to go all in with open RAM. The core lens itself to a single stack implementation distributed over different parts of the network. It is a natural open source fit and can become the base implementation to be leveraged by many commercial use cases. In other words, build once, enhance many times and thereby support all use cases you can. I wanna make sure that we're not confusing the open core here with the open core model of open source commercialization. There's a lot of open here. The open core model in the open source commercialization is about where a project is open sourcing just the core part of it but there's a lot of non-core pieces that remain proprietary. The core we're referring to here is the packet core that is commonly known as the Evolve packet core or EPC in 4G OT networks and 5G core in the 5G networks. Just wanted to clarify that for our audience before going a bit deeper. And going back to the RAM and core in the cellular networks, we know that RAM is a lot about the cosplay it's very caustic heavy at least four to five times more costly than a core backend from samples taken from a typical operator network. Core on the other hand is a lot about complexity play. Opx heavy played with licensing, networking and software complexities. Still the overall core market is a fairly healthy industry and when you combine the EPC, VPC, cloud EPC it's roughly a market between 20 and 25 billion dollars and it's growing more than 50% level over the next five years. But there's a lot of intelligence that are actually moving into core and that estimate does not include the emerging 5G core. So now having seen sort of the open source aspect of our journey and the RAM and core the telco aspects of the journey one more variable that I want to talk about and it's none of the telco cloud. And I want to switch over and talk a little bit about this important movement that is happening and it's called cloudification of the network. The title here should tell bulk of the story. Indeed the level of excitement around telco cloud is unusually high and every cloud player is jumping on the bandwidth. The diagram on the left was published recently on LinkedIn that captures how all major core vendors are now offering a cloud-based core as a service to major tier one operators around the globe. It may be difficult to see but you can probably spot all major package core vendors on the right-hand column of this picture and several tier one operators on the left-hand side. It goes a level further to show what vendors are offering against which use cases the operators are leveraging the telco cloud for. If you look at the right-hand picture, IBM published this one a few months back and with their launch of this telco cloud ecosystem for the partners, perfectly a closed ecosystem with following the likes of Microsoft Azure and Google Cloud. More than anything, it appears like a logo down to us and we see all major players except perhaps one or two like Ericsson is missing from it. I'm sure many of you could build a similar one from major public cloud marketplace and filtering by an industry segment like Telcom. And just to make the case a little bit stronger, the acquisitions of Affirm Networks and MetaSwitch Networks last year by Microsoft and offering those through Azure, they happen almost back-to-back and that coincided with the wake of the pandemic. Just underscoring the importance of improved connectivity and expanded connectivity for not just US but North American markets for the entire globe. And we'll see later today that Magma team is working closely with AWS to cover how we will be offering Magma through AWS. Our view is that these kinds of ecosystems simply shift the code and telco services from traditional box vendors to the emerging cloud vendors with relatively low impact on the evolution of the actual networks. They really don't do much in terms of disrupting the industry with any sort of open telco or open source mindset. It's more about just shifting of the one closed ecosystem to another closed ecosystem. And they do not change the network dynamics or economics drastically either except that you get a lot of cost benefits, a lot of complexities from the underlying layers are now moved over to cloud and you don't have to deal with the hardware aspects and so on. So now that we have seen the three key movements at play here, open and disaggregated networks, open source software stacks and telco cloud. This is why I want to make the case why we believe that the future core of the network will be a confluence of all these factors, especially when we look at the evolution of the network core through the physical and then virtual and then finally clarified in a pretty vendor info locked way. So if we go back around the launch of the 4GOT networks around 2008, 2009 timeframe from then to 2014, it was all about the physical packet cores of known as EPC. If we move over to 2014 to 2019, that's when the virtual packet cores of EPCs have been launched and deployed around the globe. And finally, since last year or later part of 2019, cloud native cores started appearing for both 4G and 5G. 3GPP release 15 was ratified in 2018. It was during that virtualization era and missed several important characteristics for future cellular networks. A clear path for network core stacks that is developed and deployed in a vendor, access and infragnostic manner was one of those characteristics that release 17 and 18 are working to catch up. Going forward, we need a 100% API driven, cloud native, multi-tenant core stack that convergence all kinds of networks not just cellular but Wi-Fi, satellite and private networks as well. And we shall see our journey to date as well as going forward throughout the day to day. We see the future of network core bite with open network and open source offer stack. Moving over to the next slide here. This is another title tells the whole story slide as the industry starts in tremendous benefits of open source core stacks. Even when there are parallel efforts on this and it's a good reminder that how Kubernetes won against several other open source projects. We discovered that the four projects other than magma are relevant for the network core. However, we would like to drive magma evolution in such a way that none of these projects will be competitors for magma over the next couple of years. How are we doing this? We're already consolidating as you saw with OIS stack which magma leverages and we will see a presentation on this later today. We expect further consolidation in this space and have plans to collaborate with other projects so that we can prevent fragmentation of open source network core and hopefully see magma win this race. I want to underscore the fact that this race is for the industry to win against the status quo on the network brain not for magma alone. Doing so was part of the next wave of innovation around the open source 5G movement that we heard from Arpith earlier and heard from Jonathan during the fireside chat. So let's see how we actually see that happening. Looking at deeper industries most successful open source projects had three key ingredients. Magma comfortably mixes all three and creates the best suit that any access network can use. Magma was written with open APIs such that contributing features, functionalities and use cases is super easy. We have 130 contributors and counting today only a fraction of them are from Facebook. The deaf community is where I call for our industry groups founding partners and upcoming partners who have committed development teams to focus on magma project evolution. We need member companies of OSI, OIF and LF to support the project. We need all corporate partners to establish development teams. We have several startups leveraging magma platform and contributing to it as well. We need more. We are starting to have conversations with public domain projects and excited to have the potential to work together going forward. Facebook connectivity continues to be the benevolent leader. However, as you heard the announcement we're in the process of turning the project over to a neutral leadership with a technical steering committee as well as the governing board. At this point, I call upon the startups working on 5G connectivity, networking or telecom space to consider magma as your base platform, especially if you're working on the emerging use cases like private networks, whether it's LTE or 5G, Edge and IoT networks, network convergence, service convergence, network or connectivity as a service. These are just some of the examples. There are many more like this. And I question here is that why spend time and effort in building things that will not give your startup a competitive differentiator? Consider leveraging magma so that you can focus on your secret sauce. Open source 5G is such a hot space now and there are so many opportunities up for grabs. Speedy execution will likely determine your startup's ultimate fate. So why not gain the speed by leveraging magma and commercialize your use case on top of it? And it goes back to a couple of years back we saw a great presentation by Peter Levin from Anderson Horowitz about how to commercialize a open source community project. And he described how SaaS was already open source 2.0 and the movement was moving towards 2.0. We see network and networking and connectivity as a service as a very strong component of that open source 2.0 movement. Last but not the least, I call upon the corporations, telco operators and investors to consider magma for their products as well as startups where there is a clear business case for investing in development teams on top of the platform. Which are two magma team, Jonathan, Brian, Phil, Michael, Amar, Boris and many others. And let's get engaged. This is what I'm going to close out the conversation with as we just announced the Linux Foundation and magma becoming an independent project there. It's really important to sort of like show who our founding partners are and how these entities are connected in a little bit deeper than what Yale had announced. So I'd like to take this opportunity to clarify the roles and responsibilities between TIP Open Core Network Group, magma community project and Facebook magma. Each of these entities have very specific roles and responsibilities to play towards an open and disaggregated network core as well as the open source project around magma. TIP OECN is an open and disaggregated core networking ecosystem that is addressing what 3GPP did not address along with a few adjacent blank spaces. For example, private networks and other emerging use cases. TIP OECN goal is to enable different vendor solutions to play nice with each other. And that's regardless of whether they leveraged magma code or not. And they would enable basically interoperability test, lab trial, field trial, such that we can see a smooth path forward for an open and disaggregated core network ecosystem to make it into deployment and into production with different operators around the globe. And I'd like to emphasize that magma is not as equal to open core network. And then both are necessary to complement each other towards this path of the eventual open core network in the industry. You can think of this as the orange alliance and the orange software community as a similar example, how TIP OECN and magma project would relate to each other. Now the second entity, which is at the center of this is the magma community project is the open source project that uses 3GPP standards and OECN requirements and several specs from the community to build a commercial grade converged core stack and OECN ecosystem members as well as the OIF and LF members can use components from magma projects to accelerate their product development, use this as a reference code, seed code, whenever possible. So that's the role of magma community project. And finally, Facebook magma productizes and commercializes magma open source project. We initiated the project and we basically moved it forward to a community project. However, we continue to commercialize a productize and commercialize the project for the use cases that help bring more people to a faster internet that is sort of like our focus area at Facebook connectivity. And going forward, we absolutely would like to see a thriving open source community growing around magma in the community and the industry and will continue to support it. That is sort of how Facebook magma team and Facebook connectivity are fixed into the picture. And then the very important part is justice example that we have laid out at the bottom. We're proud to be doing this today with this great companies like Deutsche Telecom ARM Qualcomm and these great startups, FreedomFi, Shoelace Wireless and Zero Chain and so on. And there'll be a series of peer press releases going out today throughout the day and will sort of like very excited to have you here today with us to see through, listen through the exciting projects and for the development. This is a developer conference and obviously we would like to keep the focus on the technologies that we're working on and the emerging use cases that we're working on. And I'd like to finish up by basically saying that we cannot build a community alone. We need all of your help and active participation for magma community to succeed. And with that, once again, I'd like to thank you for your time and wish that you find this time very useful. I hope, I believe that we have a few minutes for Q&A and I'm going to flash, I'm not gonna talk about this, but there's a couple of incubation projects that we're already on that could just flash those through as we take the questions. So with that, I'd like to hand over to Phil. No, I'm not. I think Kendall's gonna lead the Q&A for this session. Oh, I'm sorry. Yeah, please. So yes, if anyone has any questions for Shaw, you're welcome to unmute yourself and ask them or you can ask them in the chat or Slack or wherever you feel comfortable. Kendall, I see one in the chat currently. Looks like this one is actually for Irfan and OAI. There were some very great initiatives started as part of OAI, Cates, Cups, Local Breakout, et cetera. Will strategy for those programs change going forward? Irfan, would you like to take that or I can provide my perspective? Yes, Shaw, please go ahead and jump in if you need it. Yeah, so the short answer is that no, that should not. And I think this is an opportunity we're taking to also very much clarify the magma project evolution, which is gonna be in parallel and in a great partnership with the OAI focus on the course stack and the work that they're doing over there. And we have a specific press release that covers that and we wanna tell the industry that the projects are complementary to each other and we're building a commercial grade production ready core that is usable for a wide variety of use cases whereas OAI is gonna be focusing on a research core or an R&D core, whether it's the 4G version of it or whether it's the 5GSA version of it. So that's sort of the short answer. Irfan, you'd like to add anything? Yes, definitely, Shaw. So in fact, this is exactly where we are sitting right now. There's going to be a press release on the OSA website with openairinterface.org at 10 a.m. today. That is going to explain this in more detail with the perspective of different partners. So yes, open air interface software alliance as you know does has its own activities. These are part of what we build as a fully compliant 3GPP 4G 5G core that is destined for research and activities that are more in line with the research aspect of things. We are not building a commercial core which is sort of the ambition of the MAGMA project. So there's a lot of collaboration between the two activities. You will have different flavors of components that you asked about that will remain available and they will keep developing. And people can pick and choose different things for different use cases. And basically the idea is that this is very, very complimentary of both projects. Thank you, Irfan. So Prakash here, I have a question for both Arpit and Shah Raman. What are you thinking in terms of open RAN, O-RAN integration with the MAGMA core? Any thoughts on that? Sure, do you want me to start and then? Yeah, I'll pick, go ahead. Okay, yeah. So I think for those of you who are familiar with the O-RAN alliance, right? Linux Foundation hosts the software portion of it called O-RAN SC. And as I mentioned, right, as we move towards end-to-end solutions and use cases, several of these projects all the way from access to edge to the core, in this sense, packet core. And then from data planed up through the stack, they all need to either interoperate or work together to make connectivity happen. So we have to look into specific integration points as we move forward. But this is kind of again, allowing us from a neutral perspective to sort of look at it, bring the communities together and see what is possible and what is required. Yeah, thank you. Thank you, Arpit. And just to kind of like share a little bit of what's happening on the ground, we are looking at the integration between the core and the O-RAN in the lab as we speak. So there is absolutely no reason for them not to interoperate because most of the interfaces are standardized whether by 2GPP or by O-RAN. So there will be more work necessary, as Arpit pointed out. The plan is to absolutely have that in our roadmap. And actually we'll see that a little bit later in the day that we point out that at what point we can say, there is an end-to-end open network that comprises components from O-RAN, O-Core, and other components. Yeah. Thank you. A question for Shah, Suresh from Colum. Hey, a really nice presentation. I really like the vision that all of you shared to like converge all these like multiple core projects and get rid of the fragmentation, right? So like what is the high level thinking behind it? Is it like, you know, the merging of the code bases or is it like more agreements outside that like everybody starts contributing into the Magma code base? Any thoughts on that? That's a great question. And this is where we probably have to spend a lot more time together to really understand. Overall goal remains the same that let's make sure we're not fragmenting the open source community. And that's with the spirit of these different industry groups coming together to support the Magma project. Again, with the goal of that, once again, I'll underscore that piece the commercial grade production-ready packet core that can be deployed at scale, right? That's kind of like what we're looking at. And that doesn't necessarily mean that we're kind of gonna support the traditional centralized core or VPC or VPC use cases. In fact, quite the opposite. We're looking forward towards the more cloud native multi-tenant programmable core that works with open ran and so on, right? Now, when it comes to sort of like consolidating or sort of like the other open source projects that are in the play here, we are like, we did this with OAI and it was relatively easy because we've leveraged their code base, right? When it comes to the other projects, whether we talk about Free5GC or OMEG, we have conversations, we're starting to have the conversations with them to understand how that collaboration is gonna look like. I don't think that we have a clear picture yet that we're just gonna start taking code and start mingling them together. Or we're gonna just basically figure out not at the code level, but more of the documentation and other levels to figure out how to keep them together. Or there could also be that just like OAI, there's a purpose of the research core that may be certain use cases that may make sense for them to coexist. So those are various possibilities we're evaluating and we wanna be working with the project leads of those projects to make sure we do the right thing that makes sense for the industry. And we welcome all of them to participate with us in evolution of magma. If that's that we can kind of align towards the, sort of like a one strong open source project as we're calling the Kubernetes of the network core. Does that make sense? Yeah, perfect, Shana. Thank you very much. Okay, thanks. Of course, yeah. All right, we probably have time for just one more question. So if anyone wants to speak up on that question, I know we have quite a few in the chat, but continue to put your questions in the chat and Slack and we'll make sure to get them all answered. One more? Yes, let's just pick one here. If we develop software application on top of magma community edition, do we need to donate it back to community or can we commercialize it? You absolutely can. I don't believe that we're putting any sort of restrictions that you have to upstream code, but just to be clear on that, that any successful community would have to put certain level of ground rules in place. And that's what we're designing with the governing board as well as the technical steering committee. And it's driven by the developers who become maintainers and who become part of the steering committee. So there's going to be, but to your simple question, the short answer is that we don't see a problem in kind of doing what we call like the basically the forks, right? So that you don't have much intention to upstream and so on. But we do ask that to build a healthy community in order for us to build a healthy community for you to at least at the baseline contribute the bug fixes back. You may be finding a lot of bugs and that's where aligning the communities to build a strength that maybe the cool projects are able to fund and basically do in-house that gets missing on the open source project. But the power of bringing all these hundreds of thousands of developers to work together to find the box to make the stack robust is I think we're going to stand out and give us a fair chance to actually compete against those cold systems. So I think we can share more details but the short story is yes. And the longer version is that let's look at the technical steering committee to come up with their rules and sort of like the ways for rules of engagement or contribution per se, okay? Hey, Shah, can I chime in just a little bit on that one answer because that's an answer related to the license. I want to make it perfectly clear the BSD three clause license absolutely allows someone to build a project on top of magma and does not explicitly require you to share it back. That is a foundation of the license and then add on the color commentary you offered about how much we would appreciate it if you did contribute back bug fixes and derivative work. So thanks. Yeah, thanks, Phil. I kind of like deliberately avoided getting to the license response but thank you for pointing that out. And I think with that, I think I'm out of time but this is, I just want to say one thing that when many startups and many companies and public domain projects leverage magma and you can commercialize them for different use cases that is probably the key metric of success we're looking at. So there is no restriction, please don't feel any restriction is quite the opposite. Go commercialize, please do that. And we want to see many, many projects commercializing based on magma. With that, I'd like to step out and hand back to Phil and Kendall. Thank you, everybody.