Purak: This is, basically, the general access tier of the CBRS spectrum, which is Citizens Broadband Radio Spectrum, started by the FCC few years back, where the Navy is using a certain amount of spectrum, like, 150 MHz of spectrum, in the 3.5 GHz, 3.55 GHz range. And for their military operations, when they're on coast, they're using that. But inside the U.S., once you're beyond 25 miles, and now that has obviously grown, this spectrum is free for enterprises to use. And, in the true spirit of innovation, this has been allocated.

So, in this case, it was using the generally available access tier of that 150 MHz. So, what we would normally do is look at the location, look at this available spectrum, and then plan the network. Yes, I'm kind of going into that second question, if, you know, PALs, if there was a priority access license tier, which is a second tier. So, the first tier is incumbents, which is the Navy spectrum so that, if there is some operation in the area, you would be asked to move the channels.

But again, as part of the planning of the network, we would work with the customer to understand location, the application and all that, and design it. If there is a flag on some of this, then we would work accordingly. And so, if the customer has a PAL already, Celona's solution can work with that as well.

Purak: So, the access points were located in specific areas, where the cameras were. I can go back to that slide, just to kind of highlight it. And Celona's 5G core was on-prem at that point. So, these are the access point, as you can see, AP1, AP2, AP3, and we've labeled these cameras. There were, in some cases — initially in the conversation — there was an old location of the camera, then customer revised, came back with this location. So, specific locations were identified for the cameras, and specific AP locations were discussed and proposed.

So, Celona's 5G core basically has the control plane, data plane, as well as the spectrum management, and auto configuration. So, all that within the local data center over here, that was done. And from a bandwidth requirement, some quad-stream cameras required 18 Mbps, so we had considered that, okay, if there is an 18 Mbps UL requirement per camera, then possibly three or four cameras that can be addressed by a single AP. And that way, you’re not overloading the network, as, usually customers land and expand, so based on the use cases, it’s a "build it and they'll come" kind of a thing.

So, this started off with the camera use case, but there are already discussions on the staff using tablets to make sure that work order management is also done on site.

Purak: Roaming is very similar to — if you're familiar with the 5G cellular network — where devices are basically attached to the network, and then, based on the network reading information, it starts scanning different channels available, neighbors available, and so on. And it starts sending measurement reports, and the access point would look at the measurements from all these devices that are attached to it.

It will also have knowledge of other access points on the network because of the system information, that has all these channels and AP information, that it would broadcast to the devices, and then the devices in turn would send their signal levels of all the channels that they're seeing.

Based on that information, as the device is moving, and the serving cell threshold becomes lower than a certain agreed threshold, it would then decide that, okay, the neighboring cell, or neighboring AP, is providing a better quality. In order to make sure the application's throughput requirements and general bandwidth requirements are served smoothly, it will make sure that the handover command is sent to the device. And the device would then move smoothly over to the other access point. So, not a proprietary solution. You're using all the 3GPP 5G concepts and then making sure that the MicroSlicing and ability to flexibly put it into different device groups and enterprise VLANs. That's the piece where Celona's solution really tries to bond the 5G concepts with the enterprise capabilities. So, hope that answers that.

Purak: Yeah, I can give examples of a couple of them. One is, as we talked about, the industrial perimeter security. So, the camera stream would basically be, as the device connects to the network, the camera stream would receive that 5G network, and connect to the camera — you know, a vision AI server — and be able to do what it's supposed to do. The other environment would be, like, a humanoid robot, like in a factory. In fact, one of the networks that I've been working with is in a large auto manufacturer, because of the dearth of labor, you actually have a robot that is running a certain modem that connects to the private 5G network, and receives machine commands, to be able to close that gap between a little bit of automated labor and the existing labor. So, these applications can be from a simple machine command application to a vision AI camera application, that actually takes a real-time decision and is able to use the 5G network to that advantage.

Amir: I can take that one. And the slides are already up, so even better. Yeah, we've actually got multiple deployments running this backhaul setup. And it's working great. I would say, as the best practice, we have a service called Digi Containers, and it's really edge computing on our gateways. And so, I would say the best practice is to use the container service and then implement management by exception.

So, you're not just streaming live video 24/7. You're only uploading what's most important. So, like, safety incidents, or security violations, those are the ones that get sent, not every single thing. That definitely helps. And then, luckily, a lot of the carriers are starting to offer unlimited plans. That helps with budgeting. So, I would say those two things.

Purak: That's a good question. From a deployment standpoint, there are these access points using the existing enterprise switching and routing infrastructure. And we always try to work with the customer to understand the existing cabling already laid out, or mounting structures available. And so that actually really helps in deploying the network within days, versus, like, trenching the cable, working with a contractor, actually doing that. And looking at the code, evaluating low voltage, high voltage — those kind of things. So, there is a lot of flexibility in that, versus deploying, like, a solution where you cannot use existing cabling infrastructure. So, that is the unique sort of differentiator, and we've had instances of deploying the entire private 5G network within a few hours or a day, because of this flexibility that it provides. And it’s very Wi-Fi-like, right? Like I was saying, we want to emulate that, and so enterprises feel comfortable deploying this network, having visibility, control, and reachability on every aspect of this network. Think of it as an extension of the LAN, wired, Wi-Fi, or private 5G.

Purak: Yeah. So, as I would put it, we obviously work with specific camera application, the camera device. We would work with the customer to understand what are the areas that this needs to be deployed. So, all that consideration needs to be taken into account. You're pretty much doing a lot of math there, where you have specific bandwidth requirements, and you would look at the AP capabilities, making sure that, based on the codec being used, the frames per second, and the general number of streams of the camera, you would actually look at that, and then propose this particular solution, making sure that, at that bandwidth, the right amount of resources from the 5G can be allocated, in order to service that.

And so, from a latency standpoint, it's actually more about bandwidth than latency at that point. But from a latency standpoint, we're able to service tens of milliseconds, versus, the hundreds of milliseconds in a different network, where, especially with cameras and everything, wanting to take the decision real-time, and providing that action, using the same 5G network, you need to have that serviceability.