5G Slicing Explainer

I sometimes think the telecom industry is confusing its own customers when it talks about 5G network slicing.

 And to be honest, I’m not always convinced the industry fully knows how to explain or sell the capability yet either.

 A lot of the discussion around slicing gets presented as though it’s one single thing. In reality, I think there are at least three quite different dimensions to it, especially in a public safety context.

 The first is slicing within the RAN itself.

This is really the next evolution beyond traditional priority and pre-emption mechanisms on a commercial mobile network. It’s about being able to allocate and protect radio resources for particular users or services under congestion conditions.

 The second is slicing or partitioning within the core network.

This allows different user groups such as public safety agencies, utilities, or transport operators to share a common dedicated capability while still maintaining separation between operational environments, policies, security domains, and service characteristics.

 Then there’s a third layer that probably gets talked about far less: partitioning of the business and operational support systems around the network.

 Things like provisioning, customer care, service management, reporting, and operational workflows.

 That separation becomes extremely important once multiple critical sectors start sharing common infrastructure.

 For example, you probably don’t want a power utility field worker accidentally provisioned with a service profile intended for a police or ambulance user.

 So when people talk about “network slicing,” I think the industry sometimes compresses several very different concepts into one marketing term.

 The technology is real. The capability is useful.

 But I suspect many customers are still trying to work out exactly which “slice” problem they’re actually trying to solve.

https://www.linkedin.com/feed/update/urn:li:activity:7465884529149235200/