 I'd like to welcome you to our presentation on revolutionizing 5g infrastructure Open ran Loki in the open telecom ecosystem with me on stage. I have Jose Miguel Guzman from white stack and David Patterson from Dell Technologies On the screen now are the topics that we're going to discuss this this morning First we're going to dive into the open telecom ecosystem a new ecosystem that Supports more integrated distributed and multi-vendor solutions I will then provide a brief open ran intro and Then follow that up with a description of Loki in telecom and how it can help you create solutions for today's modern networks the next on deck is telecom edge hardware and How commercial off-the-shelf hardware is available to incorporate into your solutions and finally will provide a demo? So first topic is open tell the open telecom ecosystem at the top of the list of logos are the three organizations That promote open software Software solutions on the on the left of the slide. That's of course the open infra foundation and the cloud native computing foundation on the right is an organization that supports and Defines standard hardware Implementations, that's the open compute project And along the bottom is a list of organizations that you may be less familiar with and these are players in the telecom Space so we start the left with 3g pp Which defines the standards and then a few other organizations that implement them How you doing? I'm going to do a very high-level quick overview of Open ran and how the specifications are defined so Just I have this the slow steps top to bottom 3g pp is who is the group that defines some of the base specifications The next step downstream is the over and alliance over an alliance takes those upstream 3g pp specifications and Further defines them and they have a reference implementation Intel then took what the output from over and alliances and created Intel Flex ran which is again building upon what the work that was done in 3g pp and over and alliance and they also add some things like cups and Cots functions on virtual Infrastructure and finally what we're dealing with today is we have airspans open-range V ran, which is a license implementation of Intel flex ran the topology or we're dealing with today is a full Disaggregated 7-2 split so you can see on the left side you have the centralized unit Next you have the distributed unit Which takes care of offloading the the traffic directly off the r u and then you have the r u In in in previous releases of cellular networks It was pretty monolithic and one of the big pushes in 5g is to disaggregate the stuff Here's a little more detail on the 5g disaggregation on the left. You have the mf and upf and all of the corresponding interfaces under it and then you can see on the right side the cups architecture where you have a cu cp and cu dp and Yeah flex rain is very similar to this right here And save it So let's talk about lucky, but in telecoms Probably most of you or some of you will know what lucky is So in general luck is a cloud stack comprises of Linux open a stack and Kubernetes There is a very good article very good post from Jonathan Bryce that you can scan and see the details so But the central central piece here in lucky is open a stack and The good news is open a stack has been broadly adopted by vendors So there is operators deploying open a stack, but also vendors with products that will support Telecom infrastructure you can see a number of Manufacturers that are including that in though in their portfolios And some other projects in the community that are directly connected what as Requirements in telecom so ironic is important because it allows us to to to set up and and deploy on bare metal Cyborg is very important because it allows us to manage the acceleration layer and Magnum also very important because it drives the integration with Kubernetes So lucky it's not it doesn't it doesn't came from the From the telecom industry, but it's aligned it to what is Etsy has defined it as the stack for telecommunications So in in the Etsy nomenclature open a stack is a VIM virtualized infrastructure infrastructure manager you can see at the left side at the bottom and in the Kubernetes edition of the NFB standards Kubernetes is called a sysma container infrastructure service manager. So Loki is completely aligned it to what s Etsy has defined it as the stack for telecom in the NFB architecture Let's move to the hardware part So like to talk to you about a Evolution in the hardware that you can use to implement your solutions for telecom in an edge So today you can find commercial office off the shelf hardware from multiple vendors I've got here some that have been offered by Dell Technologies The ones on the left the PowerEdge XR 4,000 We're recently released and are available They are purpose-built For telecom and edge Their depth is very well suited for tall telecom cabinets And on the right is a previous generation that is still being offered called the XR 11 and XR 12 These are examples of what you can get commercially off the shelf And here we have some more details about the hardware designs for telecom and edge the XR So as it says that there's short depth Servers that are well suited for telecom cabinets and they have front IO and They have extended temperature support for the environments that they operate in in the telecom networks and They do comply with industry standards for telecom equipment, which is called nebs and mill standard as well and so there are the several models and The one on the far left the XR 8,000 is especially targeted at telecom Okay, we got a quick demo for you guys Okay Okay So this is a brief overview of the entire Lab that we built Right here. You're looking at White clouds open stack distribution. You can see the various instances of each Component that makes up the ran you have a kubernetes Worker nodes you have a centos worker node, which is a running this cu functions and We also have VMs for the ACP EMS, which is a airspan product and The The packet core and I believe this is based on horizon you just take horizon and it's a downstream Implementation of horizon. So I think I cover the interfaces here See as a virtual interfaces that will map to physical interfaces on the box console and logging back to the dashboard so now we're in We're in white cruiser, which is white stacks kubernetes distribution It is based on album charts and so we have applications and then you deploy an application album chart to a Deployment and then the deployment ends up in pods and then you can Dig down into each pod if you logs and you can also Get a shell into the container itself and this was super useful. We use this a lot debugging Our topology Dashboard now we're in ACP. This is airspans EMS system We're on the g-node b page Which is the the the radio and the cu du? That's a term telco term g-node b that comprises the are you see you and do you Here are the services you can see that they're in good health and ourselves. Here's our g-node b So alongside from this GUI ACP also has the ability to to give all kinds of metrics, so Various parts of the Rand stack and our radio unit itself will push metrics up there now. We're on to ramus ramus is our 5g core we're looking at the cells a cells in good health and Now users users are equivalent to user equipment so in the case of our demo here We're using a CPE which is kind of like a gateway a Wi-Fi gateway that you'd have at home But instead of Wi-Fi it's it's cellular and here's the dashboard gives you a high-level overview And here is the CPE. This is another airspan device and this is our client So at the front end it can talk Wi-Fi you can hook up to it with your phone or whatever and then it will Transmit over radio and I think I took a Yes, I have the radios here You can see it's connected to radio. This is band 78 that we're on and that's it from The bottom up we have a entire RAM deployment using white stack Rants the airspan ransack and the ramus pack a core a little bit about the context of the puck So we develop all these Implementation in the Dell hotel hotel is the open telecom ecosystem lab So there we managed to have Get some airspan hardware. So specifically the CPE a base station and their software the cu and you as a Dell provided all the compute and networking hardware servers and switches and white stack provided the cloud software in For virtual machines and for a Kubernetes containers So this is a diagram of what we did so we have at the left of the left We have a representation of a main data center where we have open stack and Kubernetes virtualize on the open stack So it's a number of virtual machines that provide the workers for the cluster Kubernetes cluster there we run the 5g core and we run the central unit At the right we have a representation of an edge site that's Kubernetes on bare metal And that case we run the distributed unit connected physically the server is physically connected to the base station Then that that runs the radio the radio part. So that's the full picture of what we did Was a very good experience. Thank you guys for for supporting the project and I don't know if there is any questions You would like to ask us Any questions, okay. Thank you very much and there's a Q&A mic up here if you do