English 
Dutch 
German 
Spanish 
An operator offers your production a dedicated slice for the tournament. The proposal describes guaranteed uplink, bounded latency and isolation from the crowd, which is a precise description of every problem a contribution feed has at a full venue.
The questions worth asking before signing come next, and they tend to be unwelcome. Does that slice exist at every venue on the fixture list, or at this one stadium. What happens at the border. Which modem in the flight case can actually attach to it. And what carries the feed on the seventeen fixtures the proposal does not cover.
Network slicing is real technology with genuine value for live production, and it is also frequently discussed as though it were already the default. This article sets out what 5G Standalone actually changes, what a slice is and where its boundaries sit, and how it fits with the way broadcast connectivity is built today.
What 5G Standalone actually is
Most 5G a production has used so far is Non-Standalone. NSA puts a 5G radio in front of a 4G core network: the air interface is new, the intelligence behind it is the existing LTE core. That delivers higher throughput, and it inherits the behaviour of the core it runs on.
Standalone replaces the core as well. A 5G radio attaches to a 5G core, and the capabilities that get discussed as 5G features live there rather than in the radio. Network slicing, tightly bounded latency and per-application traffic policy all depend on the 5G core, which is why they arrived years after the first 5G logo appeared on a handset.
The distinction matters commercially. An operator can accurately advertise 5G coverage across a country and still have SA available in a fraction of it. For a production evaluating a slicing proposal, the coverage figure in the marketing material and the SA footprint at the specific venue are separate questions, and only the second one matters.
What a network slice is
A network slice is a logically separate virtual network running over shared physical infrastructure, with its own performance characteristics and its own isolation from other traffic. The physical radio and transport are the same. The treatment is different, defined end to end from device through radio to core.
The standards define broad slice categories: high throughput for general mobile broadband, low latency and high reliability for control-type applications, and high density for large numbers of low-bandwidth devices. A contribution feed sits awkwardly across the first two, because it needs sustained uplink throughput and consistent timing at the same time, which is a combination the categories were not written around.
Isolation is the property that matters for live production. A slice with allocated capacity is insulated from what the crowd is doing on the public slice, which addresses the exact failure mode that makes venues difficult: public capacity collapsing when the audience arrives, with the uplink direction suffering first. That mechanism is covered in the article on remote and live sports production.
The boundary problem
A slice is a construct within one operator’s network. That single sentence determines most of where slicing fits in broadcast.
It does not follow a device onto another operator’s network. Roaming onto a partner network means leaving the slice behind and landing on ordinary public treatment, because the slice was never a property of the device. It was a property of the network the device was attached to. Cross-border productions inherit this directly: the slice negotiated for a domestic tournament has no standing the moment the fixture list crosses into the next market.
It also concentrates dependency. A production carried entirely on one operator’s slice is a production with one access network, however well specified that network is. A mast fault, a backhaul problem or a core issue at that operator takes the whole path, and the guarantee describes performance rather than immunity from faults. Where redundancy has to survive a real event, that concentration is the thing to examine, and the reasoning is set out in the article on redundancy and backup connectivity.
None of this makes slicing unattractive. It defines the shape of the opportunity: strongest at a fixed venue, in one market, for a production important enough to justify a commercial arrangement, and weakest across a moving fixture list in several countries.
What has to be true before a slice carries your feed
Five conditions, all of which are checkable in advance and any one of which ends the conversation.
SA has to be live at that venue, on that operator, with usable coverage at the actual camera positions rather than in the car park. The operator has to offer a commercial slicing product covering the dates, which is a narrower thing than having the technology deployed. The modems have to support SA and the specific slice configuration, which quietly excludes a lot of encoder hardware still in active service. The device policy that steers traffic onto the slice has to be provisioned correctly, because a device that attaches to the network without applying the slice rules is using public treatment and reporting success. And the slice has to be specified for uplink, since a profile written around download performance solves a problem contribution does not have.
The fifth condition catches more proposals than the other four. Sustained uplink at a consistent rate is the requirement, and it is a different specification from the throughput figures that lead most commercial material.
Where slicing realistically fits today
Set against the kinds of production that make up a season of sports broadcasting connectivity, the picture is uneven.
| Production type | Slice realistic | What carries the feed in practice |
|---|---|---|
| Major tournament, fixed venue, single market | Often yes | Slice as primary, bonding across carriers as the backup path |
| Domestic league across many grounds | Rarely | Multi-carrier bonding, with a slice at the two or three largest venues |
| Cross-border competition | No | Multi-network SIMs that work in every market on the calendar |
| Breaking news at short notice | No | Bonded cellular, since there is no time to arrange anything |
| Moving events on a route | No | Multi-network bonding along the whole course |
| Remote or rural venue | No | Bonding where coverage exists, satellite where it does not |
Where the last row applies and the answer becomes satellite, the trade-offs in latency, notice period and cost per event are set out where bonded cellular and satellite are compared.
The other route to isolation: a private network at the venue
Slicing is one way to get contribution traffic off the public network. A private 5G network at the venue is the other, and for permanent installations it is often the more practical of the two.
The arrangement is different in kind. A private network uses dedicated spectrum, either licensed to the venue or provided by an operator, with equipment installed on site and coverage engineered around the building. The capacity belongs to the venue rather than being carved out of a public network, so crowd traffic is a separate problem on separate infrastructure. Several large stadiums and arenas have gone this route for exactly that reason.
The trade is that it exists at one address. A private network serves the venue that installed it, which makes it valuable to the venue and to whoever produces there regularly, and irrelevant to a production company arriving next week at a ground that has none. It also becomes a question of access rather than procurement: whether the visiting production is permitted onto the venue network, on what terms, and with what capacity guaranteed during the event.
For a broadcaster the practical consequence is the same as with slicing. Where it exists, use it and keep an independent path alongside. Across a season, the kit still has to work at the grounds that have neither.
Slicing and bonding solve different halves of the problem
The two are frequently presented as competing answers, and they address different failure modes. A slice protects a feed from contention on one network. Bonding protects a feed from the failure of any one network. A venue can produce both problems in the same afternoon.
That is why the mature arrangement uses them together where slicing is available: the slice carries the primary feed with allocated capacity, and a bonded set of connections across other carriers runs alongside it so a fault at the slice operator degrades the picture instead of ending it. The design principles are the same ones that apply to any live path, covered in the batch 1 article on multiple carrier SIMs in one encoder.
For the large majority of fixtures, where no slice is on offer, network diversity remains the mechanism that answers venue congestion. Weconnect provides non-steered access across 700+ carrier partnerships in 195+ countries, so an encoder uses whichever networks are performing at that location, in whichever market the fixture list has reached. Congestion at a venue is rarely uniform across operators, and the network that saturates first varies by site and by hour.
What to ask an operator offering a slice
Six questions, in the order they tend to matter.
Which venues on our calendar have SA coverage at camera positions, evidenced rather than asserted. What uplink is allocated, sustained rather than peak, and what happens when the venue is full. Which modems are certified for this slice, checked against the encoders we own. What the arrangement is at the other twelve grounds on the fixture list. What happens when the fixture is in another country. And what the fallback is when the slice is unavailable on the day, including who notices and how quickly.
A supplier who answers all six cleanly is offering something worth having for the venues it covers. The answers also tend to make the size of the remaining problem clear, which is the part a production still has to solve.
Frequently Asked Questions
What is the difference between 5G NSA and 5G Standalone?
Non-Standalone puts a 5G radio in front of an existing 4G core, so it delivers higher throughput while inheriting the behaviour of the LTE core behind it. Standalone connects a 5G radio to a 5G core, which is where network slicing, tightly bounded latency and per-application traffic policy live. An operator can advertise wide 5G coverage while having SA available in only part of it, so the SA footprint at a specific venue is the figure that matters.
What is network slicing in 5G?
A network slice is a logically separate virtual network running over shared physical infrastructure, with its own performance characteristics and isolation from other traffic, defined end to end from device through radio to core. For live production the valuable property is isolation, because a slice with allocated capacity is insulated from crowd traffic on the public network. It requires 5G Standalone, since the capability lives in the 5G core.
Does network slicing work when roaming or across borders?
No. A slice exists within one operator’s network, so a device roaming onto another operator lands on ordinary public treatment. A slice arranged for a domestic tournament has no standing once the fixture list crosses into another market, which is why cross-border productions are carried on multi-network SIMs that work in every country on the calendar.
Can a 5G slice replace bonded cellular for live contribution?
For the venues where a slice is available it can carry the primary feed, and bonding still has a role as the path that survives a fault at that one operator. A slice protects against contention on one network; bonding protects against the failure of any one network, and a live event can produce both problems on the same day. Across a full fixture list, most grounds will have no slice on offer at all.
What do you need to check before using a 5G slice for a broadcast?
Whether SA is live at the actual camera positions on that operator, whether a commercial slicing product covers the dates, whether the encoder modems support SA and that slice configuration, whether the device policy steering traffic onto the slice is provisioned correctly, and whether the slice is specified for sustained uplink rather than download. The uplink specification is the condition that catches the largest number of proposals.
Next steps
Weconnect provides the connectivity that has to work at every venue on the calendar, including the ones no slice covers: non-steered multi-network SIMs across 700+ carrier partnerships in 195+ countries, upload-focused performance for contribution feeds, consumption-based data that follows the fixture list, and every SIM visible from one platform. Tell us where the productions are and which venues have caused problems, and we will map coverage per location and design the connectivity around the season. Challenge us with your connectivity requirements. Direct response within 4 business hours.