Celona Orchestrator with AI – Automated Service Management

Let's look at what the simplest private, cellular cel land deployment would look like. We'd call, we would call something like this, a site, like a single deployment where you have access points, you'll have your cellular devices, you'll have your CEL access point, a CEL Edge on site, and all we need is power and someway to the internet. And we're ready, we're ready to demonstrate or show, right?

So in this type of environment, when you have a cel slow edge on site, whether it's physical in a one or multiple servers for clustering or redundancy, or whether it's virtual, I'm going to talk about these dots. So when your cellular device attaches, it obviously connects to the CEL access point. The CEL access point has an encrypted tunnel to the edge.

And so data coming in and out of your device actually comes in and out of the Barcelona Edge. Now, think about how horrible performance would be if I took this edge and moved it to another site or in the cloud. Knowing this, you would have to, what we call hairpin to hairpin to get traffic to come to a local server.

Let's say we move this edge all the way out, you still have to have that, have to have that encrypted tunnel. So the other, think of the cel, ap and Edge as like basically one big box in this type of solution, right? But how can we remove some of the friction in these deployments?

We wanna do that by getting rid of this edge box. So as, as Parit mentioned, how you would do this and not getting too, too deep in the weeds, like summarizing, you would take the parts that you need to actually handle traffic, some IP addressing, maybe some, a little bit of routing, move those services into the ap such that hopefully you have enough horsepower in your AP to access point, to run that, to run that. And then whatever else doesn't need to be local, move that somewhere else to the cloud as an example.

And that's what I have here on the table. So today I have two devices. I have my Apple iPhone 16 Pro.

I have a Zebra TC 78 with a built-in barcode scanner. Uh, they're both attached to this CEL access point. CEL access point is directly connected to this.

I'm, I'm combining these two boxes. It's actually one device. It's a cellular router with a public provider ate.

I'm going straight to the, straight to the internet on this setup. Uh, also connected to this, uh, cellular router is this laptop from which I'm presenting. This laptop will re be running, I perf, so that we can do a little bit of throughput today in this demonstration.

Then, uh, in the cloud, we'll have the portions that, that we've taken out in the edge, in the cloud, as well as the SOO Orchestrator, which is a cloud-based service to manage all of your SOA deployments. So let's look at that. Okay, so when you first log into the SOO Orchestrator, uh, you'll be greeted by the sites.

Kind of a summary information about what's running. I've got edge out in the cloud access point and two of my devices. Let's drill into the devices.

All right, so I have two active devices, my Apple iPhone and Zebra TC 78, the I-C-C-I-D identifier for the SIM on the Apple iPhone. I'll start with that. 2 54.

Someone's serving that somewhere. We'll, we'll talk about that in a day. What I'm gonna do now is I'm going to screen cast my iPhone and then screen cast.

It takes over the, the whole screen that, and there, so this is my phone. Let's go to the web. We can see on the upper right, we are connected to a 5G network.

That's cel. I'm telling you, it's cel, but yes. But now seeing whole bars 5G, I'm clicking on the CEL website.

That's going, let's look at 5G plan, overview. Great, all connected. Let's see some attributes on this device.

So in settings, you can go to general, you, you can go to about, and if you scroll to the very bottom of that, you can see what sims are installed. Again, this is on the CEL non-public network. It's a standalone 5G network.

And again, we see the ICC ID of 8 4, 4 8 proving this device is actually connected on, on, on this, on this network. That's pretty much all I wanted to show for iPhone for Apple. Now I'm going to switch over to another device.

Let's stop mirroring that. And let's go to our Zebra. Now, interesting thing about Android based phones, you get a little bit more information.

So I'm going to, uh, share this screen. The numbers we wanna remember here for the Zebra TC 78, uh, 8 3 6 1, and this, oh, there's that, that one's easy to remember. 82 point 82 for an IP address.

So let's look at this device. I'm going to do a screen copy the phone. Stop that.

This one I want to pull up, orchestrator, we'll just bring this down just a little bit so you can see the device. Okay, so in, let's make sure we're up and running here again on the, on the device itself. All right.

We're able to, again, browse the CEL homepage, look at something, a little bit of information on Orchestrator. Okay, I'm connected. Great.

Let's look at the attributes again, in settings about phone, we can scroll to the bottom. We can see our IP address of 82. 82.

So that's the same device. And in terms of the sims, scroll up a little bit. You can click on CEL Sim and 8 3 6 1 8 3 6 1.

Same device. Okay, great. Let's do something a little exciting.

So this 1 69, 2 54, 82 82 IP address. Where does that come from? In the default settings for cel, CEL issues, that IP address, just like you can purchase a commodity wifi device, you know, at the store, plug it in at home and get internet connectivity and get an IP address from that device, which nets you out into the internet.

You can do the same thing with a CEL access point. Now, plug it in, give it internet access. It comes up, you get an IP address in this 1 69 range.

Now, in enterprise networks, perhaps that's not the IP address range you want, maybe you want your devices to have the same kind of ad IP addressing that your, for example, iot devices are running. So let's do that Back to the CEL Orchestrator. What I'm going to do is I'm gonna disable or deactivate the Zebra TC 78 Dev, uh, sim for the D for the zebra.

And I'm, I'm going to reactivate it with a different device profile. So the, the default device, the default device profile by default, gives you an IP address from cel. And we're gonna change this to a different device profile, which instead of getting an IP address from cel, so on your behalf will perform A-D-H-C-P request upstream and get an IP address from there, like with the rest of your devices.

And just to call out in cellular, there is no DHCP, there is no DHCP. Like where do you, where do you get these IP addresses from the provider? It's part of the cellular standard.

When the phone connects, there's a session to, to give the IP addresses. And of course, with a public cellular provider, you're not able to control that addressing at all. You get whatever blocks of addressing the public provider has allocated with cel and I have choices.

You can use CEL itself to give you an IP address from the, from the, uh, uh, from Sloan itself, or you can forward a dates of request. We can forward a DHP request on your behalf to get an IP address. So let's do that.

Let's make sure we authorize it for all sites. Do that, give that a little bit to propagate. Let's see here.

I have bars without 5G while I'm waiting for, uh, that configuration to propagate a little bit of silence while we're waiting. Okay. That was exciting, wasn't it?

I was getting, I was getting a little nervous, but no, it came wrong back on online. Okay, let's, let's, let's prove it. Let's prove it.

Okay. Okay. That's working industries, oil and gas.

Cool. Working attributes back to about phone. We go here, we go to the bottom.

And now you see we are getting an IP address, not from cel, but the enterprise network. 1 72, 1 23 0 1 20. Great.

Now let's go into what we just mentioned earlier regarding local breakout. So what local breakout means for us is back in this diagram that the AP itself doesn't need. The, doesn't need an encrypted connection to some other entity and hairpin to get traffic back.

The access point itself can route traffic directly. So this device, this laptop that we're looking at, that I'm sharing, uh, is running, I perf this laptop. I'm also doing a direct ping to the internet.

So the laptop is directly connected to the router. It's going straight out to, I'm pinging Google here. Okay, so let's do some, let's do a little bit of throughput.

No, not with that. With this, okay. Hit and run here.

And we are, we are running. Great. So your data now doesn't have to traver if you're, if you're not using, so essentially you don't have to use a public network provider.

Your data stays on your network. Your data doesn't have to go to someone else's network. That's essentially what a public network provider is, right?

Public cellular network provider's, your data in someone else's network routing and IP addressing. You can't control it all with this now that all the data stays local, but that's great. So how I want to end this, I wanna end this on a, on an exciting note.

I'm gonna do something really daring here. What I'm going to do is I'm gonna log into this cellular router Disconnect, And I'm gonna cut off the wan, I'm going to turn off the cellular network. I'm gonna let it drop pings for say, three or four pings, and I'm gonna come back.

So zoom folks out there in video land, I'm going to disappear for a few seconds, but I will be right back starting now. Mm-hmm. Little bit, a little bit of nervous tension, a few pings, drop re-enable the modem.

Give me a little bit. I should, I should come back. I should come back to the presentation.

I can't see it. Am I coming back? Not yet.

Sweet. As you can see here, we dropped a bunch of pings from this laptop, but when I scroll over to the, I perf, oh, there was a little, little blip right there. I'll take it This point.

So Those 30 meg were important. Very good. We should have, we should have.

There was, that was a, Ooh, that, that was very cool. Yeah. Yeah.

In terms of the local breakout capability, I see that as a competitive differentiator advantage. And I, I guess, I think I would go beyond that. I would say as of right now, we're the first anybody in the whole world to present edgeless private cellular 5G land.

I hear you. And marketing, but, and also, uh, uh, this is kind of a another and observation. Uh, how are you presenting this?

Like, okay, this could help you with IT budgets, so this could help you with cost savings, you know, that those considerations, the h how's that being positioned? Yeah, I think going back to what Mammoth was saying earlier, right? If you go back to the, from a private network perspective, let's keep the neutral host aside for a second.

Just from a private network perspective, why are customers deploying a private 5G network, right? Mm-hmm. And as I said, a hundred percent of the cases today, it's, it's a complimentary, it's an, and they're doing that one because outdoor deployments, they don't have an option.

It's either no connectivity or some connectivity. And now they have the option of deploying a private 5G oil and gas refineries, yards, uh, distribution centers, parking lots. You now actually have the ability to deploy a private 5G network and start to, uh, digitize your workflows, right?

So that's the reason why they're actually deploying. And in that case, it happens to be an an because typically outdoor will be private 5G. Mm-hmm.

Indoor will be wifi. Now, some of the other use cases that Mamu was talking about earlier is when you look at manufacturing, right? And you're starting to deploy humanoids, you're starting to deploy AGVs, you realize that you're starting to run into limits of what your current wireless architecture and wireless infrastructure can do for you.

And that's why you're looking at alternatives and a more reliable option in terms of private 5G, in which case, again, it becomes more of an end where you have certain critical applications which need reliability, which need a very, very specific SLA that you need to deliver. And hence you're looking at a private 5G network to actually deliver that. Very good One aspect that, uh, you know, can be challenging with the private, uh, LT is how you issue those eems.

Um, yeah. And I know we haven't talked about it today. We've talked in the past.

Yes. Could you just, uh, yeah, describe what you guys do to, uh, try to make it as easy as possible for the IT manager? Absolutely.

Thank you. And it seems like the question is planted because that's, again, a value prop that we are very, very proud of in terms of how we can allow customers to actually deploy, uh, devices at scale. Because when I see people deploying private 5G networks and they have to do it physical sims, you know, taking out the nano sim and putting it in and labeling it manually, it's a very, very manual process.

And then if you think about doing that for hundreds of devices, you start to see why that would be a challenge. So we invested in EIM almost three years ago. We actually demonstrated that to you guys in the last two years.

And, uh, one of the big reasons, and at that time, the footprint for EIM devices was very, very low, right? So we invested in that quite early because we knew that was the only way private 5G networks, when they go at scale, that's the only way it's gonna be adopted at scale. So one thing was enabling customers the ability to actually use eims.

Number two, again, if you, you have to scan QR codes every single time, that can be a challenge. It's still better than dealing with a physical sim, but QR codes can be a challenge. So QR code is one way of onboarding eims onto the device.

What we realized was customers have MDMs that they're looking, that are using to manage their private devices today. Why can't we use that? Or why can't customers use that to actually deploy eims at scale for all the devices that they actually want, uh, to be onboard onto the private 5G network.

So we have actually built APIs that can be integrated into existing MDM systems where customers can actually push eims at scale to hundreds and thousands of devices. And whenever that device enters the private network for the first time, it'll automatically be able to download the, uh, the eim and then connect to the private 5G network. So we've kind of really made it very, very simple and we are starting to see customers completely automate the entire workflow of somebody requesting connectivity to private 5G using ServiceNow, going through getting approved, that profile being added to NAC like Cisco ICE or Aruba ClearPass.

And when the device, uh, and that MDM being used to push the ESM onto of the device, and when the device now connects to the network, everything is now a closed loop because the profile is already defined on your network access control system. The EIM allows you to connect, and it, all of this was being done in a zero touch manner. So we are starting to see customers actually utilize what we had actually built out for them.

That's good. And then do you have any limitation in terms of how many eims you can generate or it's like on demand? Uh, it's on demand, uh, with every access point.

Customers do get, uh, they're entitled to a certain number of physical and certain number of eims. Okay. And all of those are available to them on demand, and if they want additional, they can always get more with subscription, Do you have to pay more If beyond a certain limit?

Yes. Yeah, I've kind of a a two part question. Yeah.

It's in the same realm in the US we have CBRS, all those other countries you had don't have CBRS, but they have something else. Yes. So the question is h how difficult have you found finding frequency and getting it and maintaining it and not having to fight over it?

Yeah, good point. And I think, again, when Mammoth presented that global, it, it, it couldn't have been just us creating radios with different spectrum, right? It had to happen with countries opening up private spectrum.

And that has actually happened at a pretty large scale. 9, and that's for the, in the cellular world, it'll be Band 48, which is CBRS band 78, band 77, band 79. So there are on four bands that are actually being used around the world and being opened up for enterprise use.

A lot of them have A-C-B-R-S like model. It's not automated, but you can actually go apply for Spectrum, and it is dedicated spectrum that is for that customer, for that particular location. In some countries, you actually have to still work with the operator and procure that spectrum.

And we actually have gone out, and I think some of the partnerships were mentioned, we've actually gone and signed those, uh, operators up from a partnership perspective so that we can serve our customers as in when a need arises in those countries. So there are a few different models. I don't think there's one size fits all, but the good thing is private spectrum is actually opened up in most of the parts of the world.

And in the US any issues with, I mean CBRS is a little flexible, as in it's not yours. You may have it today, You may have it today, but you're sharing it and somebody might not be using it, but they have mm-hmm. Right.

To use it, but they're not and then they do in the future. Just wondering how you're dealing with that flexibility. Yeah, yeah.

So I mean, honestly, the US framework is the most automated and scalable framework across the globe, honestly. 'cause we have deployments in Germany, uk, France, Japan, Korea, we have seen it all, and Canada, Right? Mm-hmm.

And, uh, in the US the model is, there's the SaaS always right spectrum access system. And as the AP comes up with the location information, it gets granted for the spectrum, and there's 150 megahertz of spectrum. And you may be in situations where may be a neighboring building or neighboring refinery, maybe using CBRS two.

So there's some sharing going on. But, uh, in the so-called GA eight tier, the general authorized access tier, uh, we have, we have a lot of deployments, like in your refineries and so forth. You may have like adjacent refineries using CBRS spectrum.

And, uh, the, the SaaS system is, is really helping in terms of how the spectrum is coordinated across these different sites because each AP needs to register with the SaaS. So it's well coordinated actually. And we have, like in, in Houston area, in the Louisiana area, we have a lot of refinery deployments next door to each other with the outdoor, uh, aps.

And they're working 24 7, uh, pretty robustly. So the experience has been really good. Good.

And you can, and we have built automation in the systems, especially when incumbents, uh, want to use their spectrum or pal actually get activated. There's automation built in the system to, we get notified by SaaS and we can always move to another channel that is available in the spectrum. So if you have enough automation built out, I think you can still deliver a very reliable network to enterprise customers.

Thank you.