Thread by @celonaio

Thread on how today's #privateLTE architectures can evolve to prioritize enterprise friendly deployment models and get ready for #enterprise5G.👇 #CBRS

In today’s definition, the primary device of choice in a #privateLTE enterprise network is assumed to be enabled via operator licensed cellular wireless - as an extension of the macro network. 📱

Extending the existing approaches to #privateLTE architectures to app level service requirements and device/user specific authentication policies in the enterprise has not been truly possible. 🧐

The option of being able to use the existing enterprise IT infrastructure as the underlay for cellular wireless have not been truly prioritized in the way today's network designs have been drafted. 🕵️‍♀️

Today, they are built custom for each enterprise, as a separate overlay. Then to stitch things together, disparate products from different vendors for radio access, packet core, management are deployed.👨‍🔧

Unfortunately such products do not always utilize the go-to-market channels that are friendly to enterprise IT: there are not many reseller/solution partners certified, able to compare competing architectural offers. 🤷‍♀️

Enter #CBRS. It allows the conversation about cellular wireless in the enterprise to actually start with IT networking and application requirements in mind. It creates an opportunity to deliver an easy to scale solution as we get ready for #enterprise5G. 👍

With an architecture that’s ready for #enterprise5G, devices and apps that are primarily used "at work" would be top of mind. This would integrate with existing device and network-level access policies and provide enterprise IT full ownership of data, analytics and insights. 💪

Such an architecture would be tightly integrated to the existing enterprise network underlay on day-1, deployed as fast as you would deploy an enterprise Wi-Fi solution today - with the primary goal of serving apps that demand guaranteed service levels. 📶

With a flexible IT-friendly approach, it can enable custom implementations across islands within the enterprise: on the road, across remote sites, at the branch locations and within the campus - indoors and outdoors. 🏢

Once the deployment and integration of the solution are simplified, with operator participation, the same architecture can enable expansion and roaming to the mobile macro network. Enterprise-only and operator-enabled services can in fact be deployed in close alignment. 🤝

Summary: when you're thinking about making the #CBRS spectrum part of your enterprise connectivity tech stack, take a closer look at today's #privateLTE architectures and get ready for #enterprise5G. ✌️

Nine months after starting the thread, what else can we add? Well, how about a double-click on the new principles of enterprise wireless, independent of the technology of choice or the underlying spectrum. 📶

We demand wireless at work with predictable reliability. And it all starts with keeping the spectrum clean. Eliminate interference as much as possible, avoid overheads, do not give "bad actors" a chance. We now have more options with spectrum sharing methods, such as #CBRS. 🕺

Some apps on your devices at work require a specific latency, jitter and error rate target, if not throughput, extending the definition of reliability. They demand real-time response from the network, and enterprise wireless needs to keep up. 🏃‍♂️🏃‍♀️

Default for enterprise wireless should not be unencrypted open networks that any device can jump on. Air needs to be protected by default. Cert based auth for wireless access at a device level should be enabled and easily controlled remotely - per policy and at scale. 🗝️

Not all devices on the network are created equal, which we know to be a fact. So the sooner we enable strong infrastructure control on devices that are used for critical use cases, the more sanity we will all have: traffic flows, mobility events, QoS/SLA enforcement & more. 🧙‍♀️🧙‍♂️

Without us noticing, our apps "move" across data centers. Services they require scale up and down dynamically, and high availability is always on. Without a 10-step config guide, by default, enterprise wireless needs similar level of flexibility as devices "move" at the edge. ⚡️

If we want private and secure mobility everywhere, we must make deploying wireless networking software as easy to deploy as an app. Anywhere between the cloud and the edge, we should be able to spin up a new wireless network backbone on-demand, at limited to no extra cost. 👩‍🔧👩‍🔧

In summary, with new spectrum and technology options available today and more on the way in the future, there will always be new opportunities to re-visit the common operational principles of enterprise wireless. 🤔 We will do our best to contribute to the evolution. 😎