 Hi everyone, my name is Brian Barrett and I'm a Software Engineering Manager at Facebook. I support the team at Facebook Connectivity that contributes to the MAGMA project in the MAGMA Core Foundation. So we've just heard an excellent overview from Ammar who talked about MAGMA, why it's different, how it's architected, what it's used for, and how it's designed to dramatically reduce the total cost of ownership of networks. We at Facebook Connectivity see this important bringing more people online and also to enabling the open source telco movement and catalyzing open source 5G. MAGMA is a hyperscalable and distributed core. One of the things that's different about MAGMA is designed to run at the far edge on far edge appliances to support local breakout to IP all the way at the cell site. It's open source and license free. It's cloud native containerized and features control plane, user plane separation. It's modern, vendor and transport agnostic and supports integration with existing mobile network operator cores using the optional Federation Gateway shown on the diagram as Ammar explained. And it supports all access conversions. So it's designed for LTE, for Wi-Fi, for private LTE use cases with CVRS spectrum, and also 5G use cases. But I'd like to talk a bit first about MAGMA's history, how it started, where it's gone and how it's really accelerating lately as it's really found accelerated growth in the community. So if you look two years ago when MAGMA first showed up on GitHub, it was being built by a small group of software engineers at Facebook. Around 20 or 30 people built MAGMA. The team grew until in July of 2020, MAGMA was announced as an open source project with release 1.0 backed and supported by the Open Infrastructure Foundation, the Telecom Infra project as one of possibly several open core networks, and the open air interface software alliance. And since July 2020, the community has grown rapidly. So across these three sets here of advocates, contributors and participants, these are the sets of people that participate in writing code for MAGMA as advocates, people that participate in code reviews and technical discussions as contributors, and people who engage in the community on Slack and Q&A and participate in GitHub discussions. And it's really grown dramatically. And in February 2021, we announced our next move for the community, which is to become a neutral foundation called the MAGMA Core Foundation hosted under the Linux Foundation with neutral governance. And that occurred in February 2021, which we announced at our MAGMA developers conference. We've noticed even more rapid growth since then. So as of April 2021, we had over 400 people actively engaging and contributing in the design and engineering of MAGMA. The community is actually even larger than that. If you look at the last tier in the orbit model of people who are observers of the project that are starring our repo or pulling a branch on GitHub, it's actually even larger. So we clock in over 1500 members of the community at this point that are either members of our Slack community or are starring our repo and are pulling a branch on Git. So when the MAGMA Core Foundation was founded in 2021, we're really trying to position MAGMA as the de facto open source network core. And we think we're there with the launch of the MAGMA Core Foundation. So you'll find familiar governance from the Linux Foundation with the technical steering committee and a governing board. The technical steering committee is elected, group of contributors, and the governing board is comprised of members that join to help steer the project's strategy. So we retain our affiliation with the telecom in for project as one of possibly several open core networks. Facebook community still provides a backstop of software engineering contribution to the community. We also provide a backstop of technical support to systems integrators and value-added resellers that want to deploy MAGMA who can be assured that they can receive Level 4 support from the Facebook software engineering team for any operational issues that could emerge. We have ecosystem partners at the Open Infrastructure Foundation and the Open Air Interface Software Alliance and a number of both large existing well-known companies and new startups that are participating in the MAGMA Core Foundation. So it's our belief that MAGMA will be the one open core implementation that's open source, that's converged, and that supports multiple types of access technologies and is access-agnostic, that's cloud-native across both the central cloud and the edge cloud and is multi-tenant, allowing a single instance to manage potentially multiple networks at a time. So here's how we're building the ecosystem. If you look across, we have industry groups that we partner with to help scale our developer community and help drive adoption amongst developers and operators. Developers and operators help define current use cases but also motivate future use cases and we partner with research projects as MAGMA with the academic community to help investigate some of those super future use cases. So examples are there are features that are showing up in 5G releases 16 and 17 like integrated access and backhaul networks like non-terrestrial connectivity and 5G release 17. Also work in ONF and open-air interface software alliance and ORAN alliance on software-defined radio access network and radio intelligence controller work because we've seen people building on top of MAGMA to integrate through with non-real-time radio intelligence controllers. The academic community really helps spur innovation that we see flowing into startups that want to use MAGMA to build novel solutions that they build on top of and then startups help drive adoption in industry groups. So startups often will partner and use MAGMA technology to build end-to-end solutions, new innovative solutions and take things to market as value-added resellers of the stack. We really like to invite anyone listening to consider joining and building your connectivity software as a surface or enterprise solution or end consumer solution on top of MAGMA to build your business faster and ride the 5G wave with us. So here's what's in it for you. If you're looking at yourself as a possible distro vendor of MAGMA, you're going to build your own distro around it and take it to market. So your development teams can focus on development and integration as a key part of your strategy. You can use MAGMA's production grade commercial ready building blocks to build your end-to-end solutions and lean on the MAGMA community to help kind of jumpstart your project. If you're a startup or an investor, we think the MAGMA stack is pretty compelling because it lets you build your solution faster and accelerate your product development in your total time to market. If you have an expert community you can lean on and you can explore adjacent opportunities in emerging use cases around the core problem you're trying to solve. So really it's just going to help you accelerate as a project. So you can see here some of the quotes from Boris the founder and CEO of FreedomFi and also Patrick the founder and CEO of Connect 5G who know how MAGMA helped them in their project go to market faster, deploy faster, and really act as an engine powering wireless innovation. So I know that MAGMA is partnering with academic and public domain projects. So if you think about some bleeding edge research projects that are trying to do experimentation on some of the latest things in 3GPP or other projects, it's not very practical to start from scratch recreating parts of a 4G or 5G stack only to add your new use case or differentiation or research project on top of it. And it's difficult to do that with any existing commercial solutions because you don't have access to the source code. So what we're witnessing is that a lot of the bleeding edge features are showing up first in open source. So an example there is non-terrestrial connectivity with the Satisfy project or the ESA-ALIX project by the European Space Agency to adapt cellular protocols and waveforms to be used for non-terrestrial high altitude platforms and satellite connectivity projects. We already see contributions from those projects with significant amounts of public sector funding showing up an open air interface and open core projects. Another example is public sector opportunities with DARPA and the U.S. Department of Defense. There's a lot of interest in that community on shifting security left and having more secure open source solutions deployed because you have actually access to all of the lines of code. And when there is a security vulnerability, you can very quickly patch it rapidly and spin a new build. And so that helps mitigate supply chain threats that can be of concern using vendor equipment. And so there's projects going on with DARPA and the open programmable and secure 5G opportunity where they're looking at the advantageous nature of magma and other open-ran projects for their ability to support that shift left security model and quickly have a more secure solution that has quicker turnaround time under vulnerabilities. So we support several universities as well shown here who are using magma and are contributing back to the community. So just to highlight a couple really interesting building blocks and solutions that we see happening in the community that were featured in our magma developers conference that I thought were particularly exciting. So we featured in February of this year that we now have support for Amazon's far-edge appliances to deploy the magma access gateway component. So now if you're deploying magma on AWS, you can take advantage of work that we've done together with Amazon to let you in a single click provision your magma orchestrator in the cloud, but then deploy your magma access gateway component with no upfront cost on one of Amazon's far-edge appliances that have electronic ink shipping labels right on them. You just tell Amazon where you want them shipped and one of these boxes ships out pre-provisioned with the AMI for the magma access gateway and set up for zero touch provisioning where it'll connect back to your AWS hosted orchestrator in an AWS region or on primal and outpost and set up your network for you and you're ready to go. You just connect your 4G or 5G radio to it, which I think is pretty exciting. So these are ruggedized boxes that are low-cost, you pay Amazon a monthly subscription fee to use them and Amazon replaces them if they ever go bad. Another really exciting solution that we've seen built on top of magma is from the Helium project. So Helium is a cryptocurrency that instead of burning electricity to mine their coins, you actually mine coins by connecting the unconnected and until now the Helium network's mostly been a LoraWan network for IoT where you deploy Helium hotspots to extend a community LoraWan network that anyone can use for their IoT applications. But FreedomFi together with Helium just announced at our developers conference a new solution where using CBRS spectrum, you can deploy 4G and 5G hotspots to connect the unconnected in a people's network using Citizen Broadband spectrum that's unlicensed and free for anyone to use for 4G and 5G and use that to mine coins, which is really exciting use case that I think is really going to we're going to see a lot of fast growth and adoption from. So thanks for listening. I think now it's best to turn this over to Arpit who is going to take you through some end-to-end solutions built on magma and their use cases. Thank you, Brian. That was a great overview and a great set of use cases that kind of covered the magma ecosystem from a big picture perspective. I'm excited to be here on the magma day and what I'm going to do is basically give you a quick overview on how magma fits into the end-to-end solutions across multiple open source projects and how end-to-end use cases are being developed by the community at the Linux Foundation. Joining me is Tina Sue from ARM who is the TSC chair for Acreno, a critical project under LFNCH. So before I get into the details of the roadmap as well as the end-to-end solutions and Tina will walk through the one specific example of how Acreno and magma are integrated into what's called a blueprint. Let's take a step back and look at the big picture of how vertical market adoption is happening of an end-to-end open source software. So you can see that there are lots of open source projects. Some of these are very critical, very important. It's not a comprehensive list by any means. But as these projects come together, whether through APIs, through integrations, through onboarding, lifecycle management, through use cases, through demos, you know, many different ways. One of the fundamental things that we have been doing here at the Linux Foundation is trying to get them to evolve these markets. So in the middle, you kind of see a big segmentation. You know, there's the enterprise networking users and then there's the service providers. Service providers obviously include cloud service providers, telecom carriers, etc. And then in the enterprise, you have the different verticals that each have a different need from an IoT and an edge perspective that will use magma as well as other projects slightly differently. So if you look at the specific use cases that are very important in 2021 and maybe a couple of years since then, specifically for enterprise networking, you can see we have private LTE, how workloads run across clouds, how do you get network visibility for an enterprise in these multi-cloud deployments. But then when it comes to service providers, the telecom and cloud service providers are collaborating significantly under the Linux Foundation Networking, under the Linux Foundation Edge, under CNCF, to bring, you know, an end-to-end 5G-based deployment, to train people on 5G, to develop global connectivity. Huge initiatives going on. And then as you get into some of the very important users that are taking advantage of this open-source stack, you know, government across the globe is at the forefront of building on these end-to-end open-source projects. One specific project I want to, or initiative I want to point out is the 5G Blueprints or Super Blueprints as we call it, under the Linux Foundation Networking. So this is what's happening. And when you take a project-centric view, you can see that from an end-to-end perspective, you know, I've presented this at multiple conferences, but it keeps getting better and better and as more innovation comes in. From the left, the various means of access, mobile networks, residential, small, medium, or enterprise, whether they have their own data centers or not. You come in through ORAM, a project under the LFH called Home Edge, Fledge, Eve, all these projects, I'll tell you the use cases on that, brought into an Edge integration project called Acreno and then move into the core part of the stack through a public crowd or through a telecom service provider, moving into the data plane acceleration and the infrastructure part, whether it's FDIO, Kubernetes, DPDK, etc., moving up into sort of the VIMS, which is OpenStack, Control Plane, Network Automation, Project Fallon App, all the way up into the core or network application functions, right? Now these could be VNF, CNFs, and one of the first ones that now we're showing you and talking about today is Magma, which is one of the first open mobile packet core, which is kind of an application sitting on the telco side that can be pulled into the end-to-end stack. So a very important set of projects that can be brought together and then when you can do open compliance and interoperability in an open environment under a neutral governance, that project like an Anuket is getting extreme traction. This will just speed up the deployment. So let's talk through how these projects come together from an open source perspective. As we all know, projects are hosted under neutral governance with the developer community, TSC code gets produced, documentation gets produced, a set of use cases, whatever, right? I mean, it's a set of technology that gets produced, created across the world, brought together by either products and integrators. So these could be vendors, system integrators bringing it all and then put into production where people can make money and then invest back in the community. So that's kind of the circle of project life, if you may. And one of the things that we have seen in the last three years is the need for accelerating what is the lower part of the cycle, products to production. And for that, a couple of things need to happen. The interrupt, the compliance, the verification, the testing, the certification, etc. etc. needs to happen in the open world. It's not open source software, but it is open source governance. And two initiatives that I want to point out, one is Elef Networkings. Anuket, Anuket is a project that kind of combined two existing projects, OPNFV and CNTT, I mean, I'm throwing a lot of acronyms here, but essentially they are responsible for defining architectures, reference architectures, whether it's open stack based or Kubernetes based, into a reference implementation that a solution can get tested against, whether it's an FBI, MANO or VNFs, and get certification and matching for that. So very, very interesting activities there. And then Elef Edge is a set of blueprints that bring hardware and software as an implementation of a particular use case to the community so that it can be reproduced and deployed very quickly. And we'll talk about some of these in a little bit more detail. So if I look at the specific use cases that have come around, let's talk about the projects that are highlighted here. So the first one is Oran. As you know, it's one of the largest communities and the largest alliances to disaggregate and open up the RAN, which is one of the last pieces of the puzzle in the Telco network. Linux Foundation hosts the software community for Oran, which is called Oran SC. And the use cases that are being produced, created, discussed there are RG, end to end slicing, quality of experience, optimization, how do different white boxes come in, etc. Then you move on to Kubernetes open stack, sort of the cloud layer or the virtualization layer, if you may, infrastructure layer. And then you get into Anuket, which I talked about, open compliance verification, standardization, onboarding, reference implementation. On App, I won't talk about the control plane projects. They have been proven and deployed for quite some time now. But then when you get into On App, you get into 5G network slicing, cross cloud VPN, zero touch, closed loop, control loop, lots of these real use cases that are needed for network automation. And then on top, obviously, the Magma, which is a critical piece of the open source core wireless network. So these use cases are being done in each of these projects. And our goal is to bring it all together. You move out into the edge of the network. You have a set of projects that are now trying to unify the edge across the cloud deployments, across IoT, across the enterprise and across Telco. So think of these four markets trying to solve the same problem of plumbing, lifecycle management, onboarding, et cetera, for the edge computing world. And I'll talk about the definition in just a bit. But some of the examples include virtualization on on-prem devices, anomaly detection. You have projects like Fledge that are doing extremely constrained, sensitive, IOT type predictive maintenance and base monitoring, right, turbines, transformers, pumps, et cetera. Or you have EdgeX Foundry, which is one of the large projects under LF Edge that would do IoT frameworks, again, all in the open source for building automation, industrial process control, smart city. And then of course, you have on the edge a Crano, where you're going to build blueprints for testing out these various use cases and deploying it very, very quickly. So you can see that all these use cases from core to Edge to access from telecom to enterprise, they're all solving use cases and similar issues that are important to an end user. So let's take a moment and define the edge. And this is important because you will see very quickly that when Tina comes and talks about an ICN blueprint under a Crano, it uses terminology that fits together beyond what magma defines in the core. So this diagram is one of the most screen-shotted diagram in this new world of the pandemic. I wouldn't say the most widely used, but the most screen-shotted diagram that we have seen on all these virtual presentations. And what it is is under an umbrella called LF Edge, we have taken, the community has taken the liberty to define the definitions in terms of an edge. And this is what the diagram shows. So if you look at the bottom, there's really two types of edges. And before I get into that, think of the terms that you have used in Edge, thin edge, thick edge, far edge, near edge. All these are relative terms and they don't mean the same thing to everybody. So what the community did was they standardized on definition. So we would really appreciate as magma community, as well as CNCF community, starts looking at edge computing to use and utilize these terms because that's what the edge community has done. So there's two types of edges. There's a user edge and then there's service provider edge. User edge is dedicated and operated by the user. Service provider edge is shared and as a service. Now, the last mile separates these typically, but it's not a hard cut. If you go in the user edge, it's not one implementation. And that's part of the challenge we have in the community. But we have been able to standardize across three specific implementation. There is on the extreme left an edge that really has extreme constraints, right? Physical constraints, resourcing constraints, memory, compute, etc. Hardening constraints. And that's called constraint device edge. These could be microcontroller based, this could be embedded compute, etc. Then you get into some more semi secure locations where you may have an IoT gateway sitting around still in the control of an enterprise user or an IoT user. And there you may have something called a smart device. And then if you are a large enterprise or if you have enough of these factories, buildings, homes, etc. where you have service in a semi secure location, then you have something called on-prem data center edge. These are all, again, in the control of a user, as I said. And then if you move on across the last mile, you get into a couple of edges that are very important. One is the access network, which is really the RAM. So if you're putting edge compute below the RAM, and if you're putting it in a smart central office, about say one to six servers, you can get the about 20 milliseconds of latency across the application. And that's very critical, because 5G really narrows down on the transmission latency, as we all know. So once you have that, you can now have edge computing all the way to the smart central office. Anything after that, the latency may be tricky. So I always say an IoT application that dumps sensor data once a week is not an edge application. It may be an IoT application, but it's not an edge application. So with that said, the projects shown here, and I won't go into that because some of them are relevant to Magma's community, some of them are not, some of them are relevant to the CNCF community. But the more important thing here is there is a different types of constraint edges, everything from infrastructure to application. Edgex Foundry and Acreno being the the two largest projects, most mature, if you may, stage three. And we've seen several other projects moving up the pipeline as well. If you want to download the whole LF edge report, we just published it under LF edge state of the edge. And it's huge, the market's huge. And we want to take advantage of that whole edge computing, using CNCF projects, using LF and LF edge, and more importantly, integrating with Magma. So I really wanted to take this couple of minutes to get into explanation of the edge terminology. So with that said, how do we pull this all together? We pull this all together in an end-to-end solution and a project called, or I would say an initiative called end-to-end 5G Super Blueprint. It's hosted by the Linux Foundation Networking, so you can go to www.linuxfoundationnetwork.org slash 5G Super Blueprint. It is a task force. It's a project that is extending an existing governance under the LFN demo that we did, but it's more than the demo. It's now bringing components together from an end-to-end perspective that crosses LF networking, LF edge, Magma, CNCF, Oran, and a lot more. These are just some examples. And what we're doing is we are building this blueprint in real time. So we really encourage everybody to participate in this, join as members if you want to influence this even more under LF networking, but it is an open initiative to everybody. So let me walk you through how Magma is getting integrated into these components. So here's the overall roadmap that the community has created. Lots of details are being worked in real time because these projects themselves have a roadmap. So bringing all these projects back together is obviously going to be a challenge. And the reason we want to show it in an open community is so that it can be done under a neutral governance. And then we'll have vendors, system integrators, end users doing distros, doing multiple things with it. Linux Foundation is not in the business of that. But what we want to do is show a blueprint that can easily pull projects together upstream and downstream solve specific use cases. So here's how these things look. The team is working on this quarter. It's working on getting the 5G core and some version of Mac integrated with a whole set of components that can bring an open source core stack and edge stack together. Obviously 5G fixed wireless access, private 5G, multi-access edge computing, IoT, etc. are primarily the use cases. As we move forward, we get into the end-to-end slicing, which brings not just the core, but it also brings a set of commercial rands and from an open source perspective, end-to-end slicing in play. And then finally, through the Q4 timeframe, this brings not just the end-to-end network for RAM, but it also opens up the RAM with ORAM SC software. And it's a fully disaggregated open source-based 5G stack. So with obviously all the use cases that are required by the end user. So let me walk you through the three steps. The first phase is the following. We're going to use emulators for the RAM. Easy to do. I mean, easy to say hard to do, but those are sitting right there on the left. You come in and you bring in, you know, ONAP onboarding through a project called Openness plus Anuketan Kubernetes, bring it all in into Magma, Magma Orchestrator, using the access gateway through obviously the N6 and obviously all the end interfaces. What is shown here on the Acreno side is ICN and I'll have Tina talk about this in a lot more detail on how to do it. So I won't go into this, but that's kind of the application control and application layer. And then on the bottom, you see the NFVI in the telco terms, right? Network function, virtualization infrastructure layer, which uses a whole bunch of what is called open source projects from data plane acceleration to control plane to storage, et cetera. So that's kind of the phase one. Phase two is relatively straightforward. But what you're doing is kind of adding two main things here. One is you're adding the support for commercial RAMs. And then the other thing you're doing is adding end to end network slicing, which kind of comes from the Magma roadmap. ONAP already has support for the network slicing. Magma is working on it. And I think it comes together very nicely. And then finally, in phase three, you include the ORAN community. So today, the OVA-NAVAN interfaces from ORAN to ONAP already tested and released. There are other interfaces that need to be worked out both for non-real-time RIC as well as real-time RIC, but more importantly, bringing it in such a way that it is a seamless end-to-end use case across these projects. So very ambitious to participate. It's part of LF Networking's initiative. And there's a large community that is working on it. If you need to look at anything particular or cannot find anything, you know, obviously reach out to me. But that's kind of the ambition we have on doing this end-to-end Blueprints. So with that, I'm going to hand it over to Tina to walk you through some of the specifics of one example of a Crano and Magma coming together under a blueprint called ICN. And she's going to walk you through the rest of the Blueprints as well because they are, you know, not all of them are relevant to Magma, but it gives you a good perspective of how a Crano is setting up various use cases, you know, connected cars to gaming, to augmented reality classrooms, you know, all the cool use cases that Edge is known for. So she's going to walk you through that. And again, if there's any questions, we'll come back and kind of do this. So again, I'm going to pass it over to Tina and, you know, she'll do a deep dive on this. Thank you. Thank you, Apit. This is how a Crano R4 Blueprints available now. We announced it in February 24. So from here, you can see the R4 Blueprints, which are new, are indicated in blue. So you can see the industry IoT predictive maintenance blueprint sits on the smart device edge. And it has been integrated in Fletch. So it supports for the industry IoT case, like when the temperature is up, it will give an indication and alarm to the back end, like a GCP. And then you want the AI Edge autonomous vehicle, the iVix, which support integrate the Auto.Ware, AutoWare the Auto, sorry, AutoWare the Auto. And the federated learning, which has been deployed in the financial technologies, has been widely deployed by WeBank. The other one, the ICM Private 5G LTE. I'm going to talk about this a lot in the later slides. The Covey Edge support AI and the ETC and the highway, the electronic collected control. It has been deployed in the cloud and in the edge. The public cloud edge interface here sitting above the public cloud core part and public cloud edge part, which has provided APIs, orchestrations for the tailcoats and hyperscalers to work together via PCS layer. And the other one, we have the KNI Industry Edge, which is new, to support operator in France about their deployment for the industry IoT and also the manufacturing. And the green one, the existing R1, R2, R3 enhance the blueprint. We are still developing and making them more mature and adding more use cases and hardening the code. This is Private LTE 5G ICN. The purpose is to create an EPC 5G in a box to enable enterprises and operates to deploy LTE 5G. We use OSS like Free 5GC and Magma. Magma has been used here and also Free 5GC. You can see the infrastructure orchestration includes Ironic, Mitre 3, and cluster API sync could be. This is quite wide. And also the ONAP has been used as orchestration layer. We covered the network segments all the way from UCPE using Kubernetes on the network edge number one and cross the network core, which runs the Kubernetes SDE1 with EPC 5GC there. And same as the Edge number one. And the other side of the network is the network edge number two. In this case, we can support the many industry, the manufacturing, retail, farming, and mining. So I would like to talk about this Private LTE 5G ICN blueprint. This is our MVP plan. You can see from here. The ONAP openness is orchestration layer and Kubernetes is orchestration for the containers. We have the Kubernetes plus openness with the code in for orchestration. And the Magma sits on top of it. For example, we opened the CNF number one to have a look. So we have the Magma orchestrator on the top and sitting on top of the AGW for 5G. The SMF and AMF and UPF is at the control layer and data plan layer. So it connects with the other CNF number two with the M1 interface to the 5G UE emulator and through the N2 interface to Gnode B emulator. So the N3 is between the Gnode B emulator to the UPF directly. And the UPF interconnected with the data network. So this is runs the VNF number one. And Magma sits for the CNF number one. So the workflow is like this. Number one, we first installed the KubeF number one and two. And then we installed ONAP and ENCO as the orchestrator. After that, we registered the Kube ref number two. Kube ref two with the ONAP and ENCO. And we onboard the CNF one and two. You can see from here. And also VNF number one. In this case, we can create a network service with CNF or VNFs. And we can deploy the network services like what you can think about for the 5G, private LTE, I can find the manufacturing, etc. And then we registered the AWG with the Magma orchestrator. This is important to interact with Magma. And finally manually configured AWG and run the UE Gnode B test. This is the minimum workflow, the minimum data flow for our private LTE 5G integrated Magma. Here we can see the Magma integration plan details. The Magma AWG 5G early implementation available as a VM, like here is a VNF. Also the Magma orchestrator early implementation available as a container, we call it CNF of course. And the private LTE 5G ICM team, which is our blueprint team, part of ICM blueprint family, will orchestrate this too using ONAP. The UEN and Gnode B emulator will also be orchestrated as a CNF. Let's see the previous page as a CNF number two. If available in a containerized form. So this is our detailed plan. So LF Edge and Equinox community are very excited to have Magma to join the LF and collaborate on innovative blueprints to provide this end-to-end solutions. Thank you again for the opportunity to discuss this here at the Magma Day. Thank you. Have a good one.