Private 5G on CBRS for a port terminal: remote cranes, yard tractors and scanners on one radio network
A container terminal operator at a US Gulf Coast port, a leader in its segment.
- Scale
- About 250 acres, 6 berths, 12 outdoor radios, 2 core sites, 3.55 to 3.7 GHz CBRS, 20 MHz carriers
- Engagement
- Survey, spectrum planning, a pilot on one berth and a phased terminal rollout
The challenge
The terminal's Wi-Fi mesh dropped connections as vehicles and stacked containers moved, handheld scanners lost sessions between berths, and the operator wanted to remotely operate cranes and add automated yard tractors. Steel stacks shadow radio signals, a licensed carrier network was not designed for the yard, and the terminal needed its own network that it controlled and could connect to its operating system.
A container terminal on the Gulf Coast covers about 250 acres with six berths. Its Wi-Fi mesh dropped connections as vehicles and container stacks moved, handheld scanners lost sessions when workers crossed between berths, and the operator wanted to run cranes remotely and add automated yard tractors. Steel stacks shadow radio signals, and a public carrier network is not designed for a yard. The terminal wanted a network it owned, could tune and could join to its terminal operating system.
We began with a radio survey and a propagation model that included stack heights, then placed 12 outdoor radios on towers and crane legs. They are Category B CBRS devices, which the rules in 47 CFR Part 96 permit to operate outdoors at higher power than Category A devices. CBRS uses 3.55 to 3.7 GHz, managed by a Spectrum Access System (SAS): each radio asks the SAS for channels, and the SAS grants them and can take them back. The base plan used General Authorized Access, which needs no license, and we checked whether a Priority Access License in the county would give protected channels for the most critical traffic.
A port is a coastal site, and coastal zones can be protected for federal radar. A SAS may limit or move channels near the coast, so the design assumes it will happen. We planned spare channel capacity, a fallback allocation of 20 MHz carriers and the way each radio would behave when it loses a grant, and we told the operator in plain words which parts of the yard have less margin. This is the kind of constraint that surprises owners who plan on a map instead of on a grant.
The core is a private 5G core with local breakout, so user traffic never leaves the terminal, and a second core at a backup site takes over if the first fails. Devices authenticate with SIMs and eSIMs the terminal controls. The air interface runs TDD in band n48 with an uplink-heavy frame pattern, because crane and tractor cameras send more than they receive. Quality-of-service classes protect crane control and vehicle telemetry ahead of scanner and office traffic. A firewall and 802.1X on the wired side keep the radio network, the terminal operating system and the corporate network apart.
Failure testing took as long as installation. We cut radios, backhaul links and a core, and measured what a tractor experienced while it crossed the yard from one radio to the next. The pilot on one berth ran for weeks before the rest of the terminal moved over, berth by berth, with the Wi-Fi mesh kept as a fallback until each berth was stable. Coverage and latency figures in this illustrative case are modeled for a design of this kind. Our article on private 5G versus Wi-Fi 6E and 7 explains the trade-offs.
What our team delivered
- A radio survey and propagation model of the yard, including container stack heights, then placement of outdoor Category B radios on towers and crane legs
- Spectrum planning in the Citizens Broadband Radio Service band (3.55 to 3.7 GHz, 47 CFR Part 96): a Spectrum Access System grants channels to each radio, General Authorized Access use as the base plan and a check for a Priority Access License in the county
- A coastal constraint handled up front: coastal zones can be protected for federal radar, so the SAS may limit or move channels, and the design includes a fallback plan and spare channel capacity
- A private 5G core on site with local breakout, local subscriber authentication using SIMs and eSIMs, and a second core at a backup site for failover
- TDD (band n48) configured with an uplink-heavy frame pattern for camera feeds from cranes and tractors, and quality-of-service classes for crane control, vehicle telemetry and scanner traffic
- Segmentation between the radio network, the terminal operating system and the corporate network, with firewall rules and 802.1X on the wired side
- Failure testing: radio, backhaul and core faults, and a measured handover while a tractor crossed the yard
Result
The yard had continuous coverage across stacks and berths, handhelds and tractors stayed connected as they moved, and the operator owned a network it could tune and extend. Coverage and latency figures are modeled for a design of this kind, not measurements from a client.
Failover in under a second
ISP A fails at 300 ms. BFD (RFC 5880) with a 50 ms interval and multiplier 3 declares the session down 150 ms later, BGP withdraws the routes, and the forwarding table repoints to ISP B. Traffic is back at full rate in well under a second; without BFD the router would wait for the 90 s BGP hold timer. Illustrative figures.
Private 5G across a plant floor
Radios on the shared 3.55 to 3.7 GHz CBRS band connect robots, cameras and sensors. A Spectrum Access System grants the channels, a partner-provided 5G core and a local user plane keep traffic on site, and edge compute runs vision and machine learning in milliseconds. The cloud gets only what it needs.
Round-trip times between seven cities
Round-trip time in milliseconds on direct paths between seven sites, close to what today's fibre routes deliver (light in glass covers about 100 km per millisecond one way, and real routes are longer than the map line). The darker the cell, the longer the round trip. Illustrative figures.
Separate by region and by business unit
Each business unit lives in its own VRF and VLAN in every region, so a problem in retail cannot reach finance. Traffic between units has to pass a firewall that denies by default and allows only what is written down.
Facing something similar?
Tell us about your environment. We will tell you plainly what we would do and what it would take.