>> Narrator: TheCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (light airy music) >> Hi, everybody, welcome back to the Fira in Barcelona. My name is Dave Vellante. I'm here with my co-host Dave Nicholson. Lisa Martin is in the house. John Furrier is pounding the news from our Palo Alto studio. We are super excited to be talking about cloud at the edge, what that means. Charles Tsai is here. He's the Senior Director of product management at Dell Technologies and Peter Fetterolf is the Chief Technology Officer at ACG Business Analytics, a firm that goes deep into the TCO and the telco space, among other things. Gents, welcome to theCUBE. Thanks for coming on. Thank you. >> Good to be here. >> Yeah, good to be here. >> So I've been in search all week of the elusive next wave of monetization for the telcos. We know they make great money on connectivity, they're really good at that. But they're all talking about how they can't let this happen again. Meaning we can't let the over the top vendors yet again, basically steal our cookies. So we're going to not mess it up this time. We're going to win in the monetization. Charles, where are those monetization opportunities? Obviously at the edge, the telco cloud at the edge. What is that all about and where's the money? >> Well, Dave, I think from a Dell's perspective, what we want to be able to enable operators is a solution that enable them to roll out services much quicker, right? We know there's a lot of innovation around IoT, MEG and so on and so forth, but they continue to rely on traditional technology and way of operations is going to take them years to enable new services. So what Dell is doing is now, creating the entire vertical stack from the hardware through CAST and automation that enable them, not only to push out services very quickly, but operating them using cloud principles. >> So it's when you say the entire vertical stack, it's the integrated hardware components with like, for example, Red Hat on top- >> Right. >> Or a Wind River? >> That's correct. >> Okay, and then open API, so the developers can create workloads, I presume data companies. We just had a data conversation 'cause that was part of the original stack- >> That's correct. >> So through an open ecosystem, you can actually sort of recreate that value, correct? >> That's correct. >> Okay. >> So one thing Dell is doing, is we are offering an infrastructure block where we are taking over the overhead of certifying every release coming from the Red Hat or the Wind River of the world, right? We want telcos to spend their resources on what is going to generate them revenue. Not the overhead of creating this cloud stack. >> Dave, I remember when we went through this in the enterprise and you had companies like, you know, IBM with the AS400 and the mainframe saying it's easier to manage, which it was, but it's still, you know, it was subsumed by the open systems trend. >> Yeah, yeah. And I think that's an important thing to probe on, is this idea of what is, what exactly does it mean to be cloud at the edge in the telecom space? Because it's a much used term. >> Yeah. >> When we talk about cloud and edge, in sort of generalized IT, but what specifically does it mean? >> Yeah, so when we talk about telco cloud, first of all it's kind of different from what you're thinking about public cloud today. And there's a couple differences. One, if you look at the big hyperscaler public cloud today, they tend to be centralized in huge data centers. Okay, telco cloud, there are big data centers, but then there's also regional data centers. There are edge data centers, which are your typical like access central offices that have turned data centers, and then now even cell sites are becoming mini data centers. So it's distributed. I mean like you could have like, even in a country like say Germany, you'd have 30,000 soul sites, each one of them being a data center. So it's a very different model. Now the other thing I want to go back to the question of monetization, okay? So how do you do monetization? The only way to do that, is to be able to offer new services, like Charles said. How do you offer new services? You have to have an open ecosystem that's going to be very, very flexible. And if we look at where telcos are coming from today, they tend to be very inflexible 'cause they're all kind of single vendor solutions. And even as we've moved to virtualization, you know, if you look at packet core for instance, a lot of them are these vertical stacks of say a Nokia or Ericson or Huawei where you know, you can't really put any other vendors or any other solutions into that. So basically the idea is this kind of horizontal architecture, right? Where now across, not just my central data centers, but across my edge data centers, which would be traditionally my access COs, as well as my cell sites. I have an open environment. And we're kind of starting with, you know, packet core obviously with, and UPFs being distributed, but now open ran or virtual ran, where I can have CUs and DUs and I can split CUs, they could be at the soul site, they could be in edge data centers. But then moving forward, we're going to have like MEG, which are, you know, which are new kinds of services, you know, could be, you know, remote cars it could be gaming, it could be the Metaverse. And these are going to be a multi-vendor environment. So one of the things you need to do is you need to have you know, this cloud layer, and that's what Charles was talking about with the infrastructure blocks is helping the service providers do that, but they still own their infrastructure. >> Yeah, so it's still not clear to me how the service providers win that game but we can maybe come back to that because I want to dig into TCO a little bit. >> Sure. >> Because I have a lot of friends at Dell. I don't have a lot of friends at HPE. I've always been critical when they take an X86 server put a name on it that implies edge and they throw it over the fence to the edge, that's not going to work, okay? We're now seeing, you know we were just at the Dell booth yesterday, you did the booth crawl, which was awesome. Purpose-built servers for this environment. >> Charles: That's right. >> So there's two factors here that I want to explore in TCO. One is, how those next gen servers compare to the previous gen, especially in terms of power consumption but other factors and then how these sort of open ran, open ecosystem stacks compared to proprietary stacks. Peter, can you help us understand those? >> Yeah, sure. And Charles can comment on this as well. But I mean there, there's a couple areas. One is just moving the next generation. So especially on the Intel side, moving from Ice Lake to the Sapphire Rapids is a big deal, especially when it comes to the DU. And you know, with the radios, right? There's the radio unit, the RU, and then there's the DU the distributed unit, and the CU. The DU is really like part of the radio, but it's virtualized. When we moved from Ice lake to Sapphire Rapids, which is third generation intel to fourth generation intel, we're literally almost doubling the performance in the DU. And that's really important 'cause it means like almost half the number of servers and we're talking like 30, 40, 50,000 servers in some cases. So, you know, being able to divide that by two, that's really big, right? In terms of not only the the cost but all the TCO and the OpEx. Now another area that's really important, when I was talking moving from these vertical silos to the horizontal, the issue with the vertical silos is, you can't place any other workloads into those silos. So it's kind of inefficient, right? Whereas when we have the horizontal architecture, now you can place workloads wherever you want, which basically also means less servers but also more flexibility, more service agility. And then, you know, I think Charles can comment more, specifically on the XR8000, some things Dell's doing, 'cause it's really exciting relative to- >> Sure. >> What's happening in there. >> So, you know, when we start looking at putting compute at the edge, right? We recognize the first thing we have to do is understand the environment we are going into. So we spend with a lot of time with telcos going to the south side, going to the edge data center, looking at operation, how do the engineer today deal with maintenance replacement at those locations? Then based on understanding the operation constraints at those sites, we create innovation and take a traditional server, remodel it to make sure that we minimize the disruption to the operations, right? Just because we are helping them going from appliances to open compute, we do not want to disrupt what is have been a very efficient operation on the remote sites. So we created a lot of new ideas and develop them on general compute, where we believe we can save a lot of headache and disruptions and still provide the same level of availability, resiliency, and redundancy on an open compute platform. >> So when we talk about open, we don't mean generic? Fair? See what I mean? >> Open is more from the software workload perspective, right? A Dell server can run any type of workload that customer intend. >> But it's engineered for this? >> Environment. >> Environment. >> That's correct. >> And so what are some of the environmental issues that are dealt with in the telecom space that are different than the average data center? >> The most basic one, is in most of the traditional cell tower, they are deployed within cabinets instead of racks. So they are depth constraints that you just have no access to the rear of the chassis. So that means on a server, is everything you need to access, need to be in the front, nothing should be in the back. Then you need to consider how labor union come into play, right? There's a lot of constraint on who can go to a cell tower and touch power, who can go there and touch compute, right? So we minimize all that disruption through a modular design and make it very efficient. >> So when we took a look at XR8000, literally right here, sitting on the desk. >> Uh-huh. >> Took it apart, don't panic, just pulled out some sleds and things. >> Right, right. >> One of the interesting demonstrations was how it compared to the size of a shoe. Now apparently you hired someone at Dell specifically because they wear a size 14 shoe, (Charles laughs) so it was even more dramatic. >> That's right. >> But when you see it, and I would suggest that viewers go back and take a look at that segment, specifically on the hardware. You can see exactly what you just referenced. This idea that everything is accessible from the front. Yeah. >> So I want to dig in a couple things. So I want to push back a little bit on what you were saying about the horizontal 'cause there's the benefit, if you've got the horizontal infrastructure, you can run a lot more workloads. But I compare it to the enterprise 'cause I, that was the argument, I've made that argument with converged infrastructure versus say an Oracle vertical stack, but it turned out that actually Oracle ran Oracle better, okay? Is there an analog in telco or is this new open architecture going to be able to not only service the wide range of emerging apps but also be as resilient as the proprietary infrastructure? >> Yeah and you know, before I answer that, I also want to say that we've been writing a number of white papers. So we have actually three white papers we've just done with Dell looking at infrastructure blocks and looking at vertical versus horizontal and also looking at moving from the previous generation hardware to the next generation hardware. So all those details, you can find the white papers, and you can find them either in the Dell website or at the ACG research website >> ACGresearch.com? >> ACG research. Yeah, if you just search ACG research, you'll find- >> Yeah. >> Lots of white papers on TCO. So you know, what I want to say, relative to the vertical versus horizontal. Yeah, obviously in the vertical side, some of those things will run well, I mean it won't have issues. However, that being said, as we move to cloud native, you know, it's very high performance, okay? In terms of the stack, whether it be a Red Hat or a VMware or other cloud layers, that's really become much more mature. It now it's all CNF base, which is really containerized, very high performance. And so I don't think really performance is an issue. However, my feeling is that, if you want to offer new services and generate new revenue, you're not going to do it in vertical stacks, period. You're going to be able to do a packet core, you'll be able to do a ran over here. But now what if I want to offer a gaming service? What if I want to do metaverse? What if I want to do, you have to have an environment that's a multi-vendor environment that supports an ecosystem. Even in the RAN, when we look at the RIC, and the xApps and the rApps, these are multi-vendor environments that's going to create a lot of flexibility and you can't do that if you're restricted to, I can only have one vendor running on this hardware. >> Yeah, we're seeing these vendors work together and create RICs. That's obviously a key point, but what I'm hearing is that there may be trade offs, but the incremental value is going to overwhelm that. Second question I have, Peter is, TCO, I've been hearing a lot about 30%, you know, where's that 30% come from? Is it Op, is it from an OpEx standpoint? Is it labor, is it power? Is it, you mentioned, you know, cutting the number of servers in half. If I can unpack the granularity of that TCO, where's the benefit coming from? >> Yeah, the answer is yes. (Peter and Charles laugh) >> Okay, we'll do. >> Yeah, so- >> One side that, in terms of, where is the big bang for the bucks? >> So I mean, so you really need to look at the white paper to see details, but definitely power, definitely labor, definitely reducing the number of servers, you know, reducing the CapEx. The other thing is, is as you move to this really next generation horizontal telco cloud, there's the whole automation and orchestration, that is a key component as well. And it's enabled by what Dell is doing. It's enabled by the, because the thing is you're not going to have end-to-end automation if you have all this legacy stuff there or if you have these vertical stacks where you can't integrate. I mean you can automate that part and then you have separate automation here, you separate. you need to have integrated automation and orchestration across the whole thing. >> One other point I would add also, right, on the hardware perspective, right? With the customized hardware, what we allow operator to do is, take out the existing appliance and push a edge optimized server without reworking the entire infrastructure. There is a significant saving where you don't have to rethink about what is my power infrastructure, right? What is my security infrastructure? The server is designed to leverage the existing, what is already there. >> How should telco, Charles, plan for this transformation? Are there specific best practices that you would recommend in terms of the operational model? >> Great question. I think first thing is do an inventory of what you have. Understand what your constraints are and then come to Dell, we will love to consult with you, based on our experience on the best practices. We know how to minimize additional changes. We know how to help your support engineer, understand how to shift appliance based operation to a cloud-based operation. >> Is that a service you offer? Is that a pre-sales freebie? What is maybe both? >> It's both. >> Yeah. >> It's both. >> Yeah. >> Guys- >> Just really quickly. >> We're going to wrap. >> The, yeah. Dave loves the TCO discussion. I'm always thinking in terms of, well how do you measure TCO when you're comparing something where you can't do something to an environment where you're going to be able to do something new? And I know that that's always the challenge in any kind of emerging market where things are changing, any? >> Well, I mean we also look at, not only TCO, but we look at overall business case. So there's basically service at GLD and revenue and then there's faster time to revenues. Well, and actually ACG, we actually have a platform called the BAE or Business Analytics Engine that's a very sophisticated simulation cloud-based platform, where we can actually look at revenue month by month. And we look at what's the impact of accelerating revenue by three months. By four months. >> So you're looking into- >> By six months- >> So you're forward looking. You're just not consistently- >> So we're not just looking at TCO, we're looking at the overall business case benefit. >> Yeah, exactly right. There's the TCO, which is the hard dollars. >> Right. >> CFO wants to see that, he or she needs to see that. But you got to, you can convince that individual, that there's a business case around it. >> Peter: Yeah. >> And then you're going to sign up for that number. >> Peter: Yeah. >> And they're going to be held to it. That's the story the world wants. >> At the end of the day, telcos have to be offered new services 'cause look at all the money that's been spent. >> Dave: Yeah, that's right. >> On investment on 5G and everything else. >> 0.5 trillion over the next seven years. All right, guys, we got to go. Sorry to cut you off. >> Okay, thank you very much. >> But we're wall to wall here. All right, thanks so much for coming on. >> Dave: Fantastic. >> All right, Dave Vellante, for Dave Nicholson. Lisa Martin's in the house. John Furrier in Palo Alto Studios. Keep it right there. MWC 23 live from the Fira in Barcelona. (light airy music)

(soft corporate jingle) >> Announcer: theCUBE's live coverage is made possible by funding from Dell Technologies. Creating technologies that drive human progress. (upbeat jingle intro) >> Welcome back to Barcelona. We're here live at the Fira. (laughs) Just amazing day two of MWC23. It's packed today. It was packed yesterday. It's even more packed today. All the news is flowing. Check out siliconangle.com. John Furrier is in the studio in Palo Alto breaking all the news. And, we are here live. Really excited to have Udayan Mukherjee who's the Senior Fellow and Chief Architect of wireless product at Network and Edge for Intel. And, Manish Singh is back. He's the CTO of Telecom Systems Business at Dell Jets. Welcome. >> Thank you. >> Thank you >> We're going to talk about greening the network. I wonder, Udayan, if you could just set up why that's so important. I mean, it's obvious that it's an important thing, great for the environment, but why is it extra important in Telco? >> Yeah, thank you. Actually, I'll tell you, this morning I had a discussion with an operator. The first thing he said, that the electricity consumption is more expensive nowadays that total real estate that he's spending money on. So, it's like that is the number one thing that if you can change that, bring that power consumption down. And, if you talk about sustainability, look what is happening in Europe, what's happening in all the electricity areas. That's the critical element that we need to address. Whether we are defining chip, platforms, storage systems, that's the number one mantra right now. You know, reduce the power. Electricity consumption, because it's a sustainable planet that we are living in. >> So, you got CapEx and OpEx. We're talking about the big piece of OpEx is now power consumption? >> Power Consumption >> That's the point. Okay, so in my experience, servers are the big culprit for power consumption, which is powered by core semiconductors and microprocessors. So, what's the strategy to reduce the power consumption? You're probably not going to reduce the bill overall. You maybe just can keep pace, but from a technical standpoint, how do you attack that? >> Yeah, there are multiple defined ways of adding. Obviously the process technology, that micro (indistinct) itself is evolving to make it more low-power systems. But, even within the silicon, the server that we develop, if you look in a CPU, there is a lot of power states. So, if you have a 32 code platform, as an example, every code you can vary the frequency and the C-states, power states. So, if you look into any traffic, whether it's a radio access network, packet code. At any given time the load is not peak. So, your power consumption, actual what we are drawing from the wall, it also needs to vary with that. So, that's how if you look into this there's a huge savings. If you go to Intel booth or Ericson booth or anyone, you will see right now every possible, the packet code, radio access network, everything network. They're talking about our energy consumption, how they're lowering this. These states, as we call it power states, C-state P-state they've built in intel chip for a long time. The cloud providers are taking advantage of it. But Telcos, with even two generation before they used to actually switch it off in the bios. I say no, we need peak. Now, that thing is changing. Now, it's all like, how do I take advantage of the built in technologies? >> I remember the enterprise virtualization, Manish, was a big play. I remember PG&E used to give rebates to customers that would install virtualized software, VMware. >> And SSDs. >> Yeah. And SSDs, you know, yes. Because, the spinning disc was, but, nowhere near with a server consumption. So, how virtualized is the telco network? And then, what I'm saying is there other things, other knobs, you can of course turn. So, what's your perspective on this as a server player? >> Yeah, absolutely. Let me just back up a little bit and start at the big picture to share what Udayan said. Here, day two, every conversation I've had yesterday and today morning with every operator, every CTO, they're coming in and first topic they're talking about is energy. And, the reason is, A, it's the right thing to do, sustainability, but, it's also becoming a P&L issue. And, the reason it's becoming a P&L issue is because we are in this energy inflationary environment where the energy costs are constantly going up. So, it's becoming really important for the service providers to really drive more efficiency onto their networks, onto their infrastructure. Number one. Two, then to your question on what all knobs need to be turned on, and what are the knobs? So, Udayan talked about within the intel, silicon, the C-states, P-states and all these capabilities that are being brought up, absolutely important. But again, if we take a macro view of it. First of all, there are opportunities to do infrastructure audit. What's on, why is it on, does it need to be on right now? Number two, there are opportunities to do infrastructure upgrade. And, what I mean by that is as you go from previous generation servers to next generation servers, better cooling, better performance. And through all of that you start to gain power usage efficiency inside a data center. And, you take that out more into the networks you start to achieve same outcomes on the network site. Think about from a cooling perspective, air cooling but for that matter, even liquid cooling, especially inside the data centers. All opportunities around PUE, because PUE, power usage efficiency and improvement on PUE is an opportunity. But, I'll take it even further. Workloads that are coming onto it, core, RAN, these workloads based on the dynamic traffic. Look, if you look at the traffic inside a network, it's not constant, it's varied. As the traffic patterns change, can you reduce the amount of infrastructure you're using? I.e. reduce the amount of power that you're using and when the traffic loads are going up. So, the workloads themselves need to become more smarter about that. And last, but not the least. From an orchestration layer if you think about it, where you are placing these workloads, and depending on what's available, you can start to again, drive better energy outcomes. And, not to forget acceleration. Where you need acceleration, can you have the right hardware infrastructures delivering the right kind of accelerations to again, improve those energy efficiency outcomes. So, it's a complex problem. But, there are a lot of levers, lot of tools that are in place that the service providers, the technology builders like us, are building the infrastructure, and then the workload providers all come together to really solve this problem. >> Yeah, Udayan, Manish mentioned this idea of moving from one generation to a new generation and gaining benefits. Out there on the street, if you will. Most of the time it's an N plus 2 migration. It's not just moving from last generation to this next generation, but it's really a generation ago. So, those significant changes in the dynamics around power density and cooling are meaningful? You talk about where performance should be? We start talking about the edge. It's hard to have a full-blown raised data center floor edge everywhere. Do these advances fundamentally change the kinds of things that you can do at the base of a tower? >> Yeah, absolutely. Manish talked about that, the dynamic nature of the workload. So, we are using a lot of this AIML to actually predict. Like for example, your multiple force in a systems. So, why is the 32 core as a system, why is all running? So, your traffic profile in the night times. So, you are in the office areas, in the night has gone home and nowadays everybody's working from remote anyway. So, why is this thing a full blown, spending the TDP, the total power and extreme powers. You bring it down, different power states, C-states. We talked about it. Deeper C-states or P-states, you bring the frequency down. So, lot of those automation, even at the base of the tower. Lot of our deployment right now, we are doing a whole bunch of massive MIMO deployment. Virtual RAN in Verizon network. All actually cell-site deployment. Those eight centers are very close to the cell-site. And, they're doing aggressive power management. So, you don't have to go to a huge data centers, even there's a small rack of systems, four to five, 10 systems, you can do aggressive power management. And, you built it up that way. >> Okay. >> If I may just build on what Udayan said. I mean if you look at the radio access network, right? And, let's start at the bottom of the tower itself. The infrastructure that's going in there, especially with Open RAN, if you think about it, there are opportunities now to do a centralized RAN where you could do more BBU pooling. And, with that, not only on a given tower but across a given given coverage area, depending on what the traffics are, you can again get the infrastructure to become more efficient in terms of what traffic, what needs are, and really start to benefit. The pooling gains which is obviously going to give you benefit on the CapEx side, but from an energy standpoint going to give you benefits on the OpEx side of things. So that's important. The second thing I will say is we cannot forget, especially on the radio access side of things, that it's not just the bottom of the tower what's happening there. What's happening on the top of the tower especially with the radio, that's super important. And, that goes into how do you drive better PA efficiency, how do you drive better DPD in there? This is where again, applying AI machine learning there is a significant amount of opportunity there to improve the PA performance itself. But then, not only that, looking at traffic patterns. Can you do sleep modes, micro sleep modes to deep sleep modes. Turning down the cells itself, depending on the traffic patterns. So, these are all areas that are now becoming more and more important. And, clearly with our ecosystem of partners we are continuing to work on these. >> So we hear from the operators, it's an OpEx issue. It's hitting the P&L. They're in search of PUE of one. And, they've historically been wasteful, they go full throttle. And now, you're saying with intelligence you can optimize that consumption. So, where does the intelligence live? Is it in the rig. Where is it all throughout the network? Is it in the silicon? Maybe you could paint a picture as to where those smarts exist. >> I can start. It's across the stack. It starts, we talked about the C-states, P-states. If you want to take advantage of that, that intelligence is in the workload, which has to understand when can I really start to clock things down or turn off the cores. If you really look at it from a traffic pattern perspective you start to really look at a rig level where you can have power. And, we are working with the ecosystem partners who are looking at applying machine learning on that to see what can we really start to turn on, turn off, throttle things down, depending on what the, so yes, it's across the stack. And lastly, again, I'll go back to cannot forget orchestration, where you again have the ability to move some of these workloads and look at where your workload placements are happening depending on what infrastructure is and what the traffic needs are at that point in time. So it's, again, there's no silver bullet. It has to be looked across the stack. >> And, this is where actually if I may, last two years a sea change has happened. People used to say, okay there are C-states and P-states, there's silicon every code. OS operating system has a governor built in. We rely on that. So, that used to be the way. Now that applications are getting smarter, if you look at a radio access network or the packet core on the control plane signaling application, they're more aware of the what is the underlying silicon power state sleep states are available. So, every time they find some of these areas there's no enough traffic there, they immediately goes to a transition. So, the workload has become more intelligent. The rig application we talked about. Every possible rig application right now are apps on xApps. Most of them are on energy efficiency. How are they using it? So, I think lot more even the last two years. >> Can I just say one more thing there right? >> Yeah. >> We cannot forget the infrastructure as well, right? I mean, that's the most important thing. That's where the energy is really getting drawn in. And, constant improvement on the infrastructure. And, I'll give you some data points, right? If you really look at the power at servers, right? From 2013 to 2023, like a decade. 85% energy intensity improvement, right? So, these gains are coming from performance with better cooling, better technology applications. So, that's super critical, that's important. And, also to just give you another data point. Apart from the infrastructure what cache layers we are running and how much CPU and compute requirements are there, that's also important. So, looking at it from a cache perspective are we optimizing the required infrastructure blocks for radio access versus core? And again, really taking that back to energy efficiency outcomes. So, some of the work we've been doing with Wind River and Red Hat and some of our ecosystem partners around that for radio access network versus core. Really again, optimizing for those different use cases and the outcomes of those start to come in from an energy utilization perspective >> So, 85% improvement in power consumption. Of course you're doing, I don't know, 2, 300% more work, right? So, let's say, and I'm just sort of spit balling numbers but, let's say that historically powers on the P&L has been, I don't know, single digits, maybe 10%. Now, it's popping up the much higher. >> Udayan: Huge >> Right? >> I mean, I don't know what the number is. Is it over 20% in some cases or is it, do you have a sense of that? Or let's say it is. The objective I presume is you're probably not going to lower the power bill overall, but you're going to be able to lower the percent of cost on the OpEx as you grow, right? I mean, we're talking about 5G networks. So much more data >> Capacity increasing. >> Yeah, and so is it, am I right about that the carriers, the best they can hope for is to sort of stay even on that percentage or maybe somewhat lower that percentage? Or, do you think they can actually cut the bill? What's the goal? What are they trying to do? >> The goal is to cut the bill. >> It is! >> And the way you get started to cut the bill is, as I said, first of all on the radio side. Start to see where the improvements are and look, there's not a whole lot there to be done. I mean, the PS are as efficient as they can be, but as I said, there are things in DPD and all that still can be improved. But then, sleep modes and all, yes there are efficiencies in there. But, I'll give you one important, another interesting data point. We did a work with ACG Research on our 16G platform. The power edge service that we have recently launched based on Intel's Sapphire Rapids. And, if you look at the study there. 30% TCR reduction, 10% in CapEx gains, 30% in OpEx gains from moving away from these legacy monolithic architectures to cloud native architectures. And, a large part of that OpEx gain really starts to come from energy to the point of 800 metric tonnes of carbon reduction to the point of you could have, and if you really translate that to around 160 homes electric use per year, right? So yes, I mean the opportunity there is to reduce the bill. >> Wow, that's big, big goal guys. We got to run. But, thank you for informing the audience on the importance and how you get there. So, appreciate that. >> One thing that bears mentioning really quickly before we wrap, a lot of these things we're talking about are happening in remote locations. >> Oh, back to that point of distributed nature of telecom. >> Yes, we talked about a BBU being at the base of a tower that could be up on a mountain somewhere. >> No, you made the point. You can't just say, oh, hey we're going to go find ambient air or going to go... >> They don't necessarily... >> Go next to a waterfall. >> We don't necessarily have the greatest hydro tower. >> All right, we got to go. Thanks you guys. Alright, keep it right there. Wall to wall coverage is day two of theCUBE's coverage of MWC 23. Stay right there, we'll be right back. (corporate outro jingle)