Table of Contents
Industry 4.0 networks fail when you judge them by the consumer metric of “download speed.”
In a copper mine in Northern Ontario or an automotive assembly plant in Southern Ontario, the download speed of a Netflix stream is irrelevant. What matters is outcome-based performance. Can the network sustain a 20ms round-trip time for a tele-operated dozer with 99.999% reliability? Can it prioritize an emergency stop signal over a gigabyte log file transfer?
The answer depends entirely on your architectural choice: Non-Standalone (NSA) or Standalone (SA).
This distinction is frequently glossed over in marketing materials that focus solely on “5G speeds,” yet for the industrial architect, the difference is as fundamental as the difference between a hybrid vehicle and a fully electric, software-defined platform. One is a bridge technology tethered to the past; the other is an architecture designed for autonomous control and massive device density.
Quick Definitions Without the Telecom Jargon
To navigate the strategic decision between NSA and SA, you must first understand the architectural underpinnings. Understanding the functional relationship between the radio and the core is paramount.
What is 5G NSA
5G Non-Standalone (NSA) is a hybrid deployment model. It uses modern 5G New Radio (NR) hardware to transmit data, but these radios cannot operate independently. They are “anchored” to an existing 4G LTE radio and controlled by a 4G Core Network (EPC).
Think of NSA as a modern high-performance engine retrofitted into an older chassis.
- Control Plane: All signaling (authentication, mobility management) flows through the LTE radio.
- User Plane: Data flows through the 5G radio but is routed and managed by the legacy 4G EPC.
This creates a critical dependency. If the LTE control signal is lost or congested, the 5G data pipe collapses. For industrial users, NSA is essentially “LTE Advanced Pro.” It offers higher throughput but inherits the architectural limitations of the 4G Core: higher latency and limited Quality of Service (QoS).
What is 5G SA
5G Standalone (SA) is the “true” 5G architecture. It severs all ties with LTE. The 5G Radio connects directly to a 5G Core. This is a ground-up redesign based on Cloud-Native principles and a Service-Based Architecture (SBA).
- Service-Based Architecture: Unlike the hardware-centric 4G Core, the 5G Core is composed of software microservices that communicate via standard HTTP/2 APIs.
- End-to-End 5G: Both signaling and data are handled natively by 5G protocols, eliminating the overhead of translating between generations.
The So What for Industrial Teams
The architectural divergence manifests in three operational realities:
- Complexity vs. Simplicity: NSA requires managing two radio technologies simultaneously. If the LTE signal is weak in a specific corner of a warehouse, the 5G connection cannot be established, even if the 5G signal is strong. SA simplifies the RF environment to a single technology.
- The Performance Ceiling: NSA hits a performance ceiling defined by the 4G Core. It delivers bandwidth but fails to deliver the ultra-low latency or massive connection density promised by 5G marketing.
- The Edge Paradigm: SA is designed with Control and User Plane Separation (CUPS) as a native feature. You can push traffic processing to a small server rack right on the factory floor while keeping the “brain” of the network in the cloud.
The Industrial Outcomes That Change Between NSA and SA
Industrial leaders must evaluate connectivity on the operational outcomes those specifications enable. The shift from NSA to SA alters the physics of data transmission.
Latency Improvements
Latency is the single most critical metric in industrial automation.
The NSA Latency Floor
In 5G NSA, the latency improvement is marginal. The requirement to negotiate signaling through the LTE anchor adds overhead, resulting in a typical latency of 20–30 ms. This is adequate for tablets but fails for machine-to-machine interaction.
The SA Revolution
5G SA supports flexible Sub-Carrier Spacing and shorter Transmission Time Intervals. The network sends data in “mini-slots” rather than waiting for a full frame, drastically reducing the time a packet waits to enter the airwaves. Combined with edge integration, SA delivers typical latency of 5–15 ms.
Jitter Matters More
SA offers superior determinism. In test environments, SA networks maintain jitter below 2-3ms. High jitter causes robotic arms to shudder or safety systems to trip. For a mining operator remotely controlling a rock breaker, 30ms latency feels “spongy,” leading to over-correction. 10ms latency feels instantaneous.
Reliability and Determinism
Manufacturing demands Six Nines (99.9999%) reliability.
NSA relies on the retransmission mechanisms of LTE (HARQ). If a packet is corrupted, the network asks for it to be sent again. This ensures delivery but ruins reliability regarding time. The packet arrives, but it arrives late.
SA introduces Ultra-Reliable Low-Latency Communication (URLLC) features that change how reliability is achieved:
- Packet Duplication: The network sends the exact same packet over two different frequencies simultaneously. If one fails, the other arrives.
- Pre-emption: The SA Core can identify a critical safety packet and interrupt a lower-priority download in the very next millisecond to ensure the critical data gets through. This is impossible in the “first-come, first-served” scheduler of a 4G Core.
Uplink Performance
The traffic profile of an industrial site is the inverse of a consumer user. A smart factory uploads 4K video from inspection cameras rather than downloading streams.
In NSA deployments, the device is often forced to transmit control signals over LTE while trying to upload data over 5G. Because the device has a limited power budget, it splits its transmit power, and the narrow LTE uplink spectrum creates a bottleneck at the cell edge.
SA unleashes Uplink-Centric TDD frame structures and Supplementary Uplink (SUL). SUL allows the device to use a low-band frequency exclusively for uplink data when the mid-band signal gets weak. This enables sustained uplink throughputs of 100+ Mbps per device further from the tower.
Network Control and Policy
Who dictates which packet matters?
NSA uses QoS Class Identifiers (QCI), a rigid bucket-based system. All traffic in “Bucket 9” fights for bandwidth equally. You cannot easily distinguish between a critical machine log and a worker’s YouTube stream.
SA introduces a Flow-Based framework. The network identifies specific data flows within a single application. For an autonomous forklift, the SA network can assign:
- Flow 1 (Safety Stop): Critical priority (0.7ms budget).
- Flow 2 (Video Feed): High bandwidth.
- Flow 3 (Diagnostics): Best effort.
Advanced Capabilities like Slicing
Network Slicing is the virtualization of the physical network into multiple logical networks.
In NSA, slicing is essentially a marketing term for using different Access Point Names (APNs). It provides logical separation but not resource isolation. If the radio network becomes congested, all “slices” suffer.
In SA, the Network Slice Selection Function (NSSF) directs traffic to specific instances of the User Plane and Control Plane. A mine can run an “Autonomous Haulage Slice” and a “Contractor Wi-Fi Slice” on the same towers. Even if the contractors saturate their slice, the Haulage Slice is mathematically guaranteed its reserved processing power.
Mapping SA vs NSA to Industry 4.0 Use Cases
Robotics and Real Time Control Loops
Collaborative robots are moving to wireless control to enable flexible manufacturing cells. The defining requirement is Isochronous Real-Time (IRT) communication.
NSA fails here because its inherent jitter (5-10ms variance) disrupts the synchronization between the master controller and the robot servo. If a “move” packet arrives late, the robot must pause, leading to “micro-stops.”
SA is designed to integrate with Time Sensitive Networking (TSN) standards. It acts as a deterministic bridge, enabling cycle times of <10ms with jitter <1ms.
Machine Vision and Video Analytics
Automated Quality Control (AQC) systems require massive aggregate uplink. A factory floor might have 50 cameras each needing 15-25 Mbps.
NSA networks often have a TDD configuration favoring downlink (e.g., 3:1 ratio). They simply run out of uplink airtime. SA allows for Uplink-Centric TDD frame structures (e.g., 2:2 or 1:3), where more time slots are allocated to upload.
AGVs and AMRs
Autonomous Mobile Robots (AMRs) constantly move behind metal racks and concrete pillars.
Wi-Fi uses a “break-before-make” handover, causing 100ms+ gaps where the robot stops for safety. NSA handovers are better but still involve complex signaling; at the cell edge, the device often drops 5G and reverts to LTE-only.
SA utilizes the Xn interface to perform “Make-Before-Break” handovers. The robot maintains connection with the source tower until the target tower connection is fully active, ensuring the AMR glides through the facility with zero operational hesitation.
Safety Systems and Emergency Response
Wireless E-Stop buttons do not consume much bandwidth, but they require infinite reliability.
SA allows the creation of a dedicated Safety Slice or the use of URLLC high-priority flags. Even if the network is 100% saturated with video traffic, the scheduler will discard video packets to ensure the Safety packet is transmitted immediately. NSA lacks this absolute pre-emption capability.
OT Telemetry
NSA is designed for broadband. Connecting thousands of low-power sensors forces them to use 4G IoT standards rooted in the EPC. A signaling storm from 10,000 devices can crash a standard 4G control plane.
SA is architected to support 1,000,000 devices per square kilometer. It introduces “connectionless” data transmission modes, allowing sensors to send small bits of data without the heavy battery drain of a full connection setup.
Decision Guide When NSA is Enough vs When SA is Essential
Right-sizing the network prevents over-spending on unneeded capabilities while ensuring critical requirements aren’t missed.
NSA is usually enough when
- The Goal is “Better Connectivity for Workers”: If you are replacing spotty Wi-Fi for worker tablets and digital forms, NSA is sufficient. These applications tolerate 30ms latency.
- Broadband is the Only KPI: If the site simply needs high download speeds for blueprints or manuals, NSA leverages the mature LTE ecosystem effectively.
- Legacy Device Fleet: If you have a massive investment in LTE-only scanners, sticking with an NSA core allows continued use of these assets.
SA becomes essential when
- Machine Control is Critical: Any application involving autonomy (AGVs, drones) requires deterministic low latency.
- Uplink is King: Multi-camera video surveillance requires the uplink-centric capabilities exclusive to SA.
- IT/OT Separation is Mandatory: If the CISO requires certified isolation between the “Office Network” and “Plant Network,” SA Slicing is the only valid architecture.
- Greenfield Sites: Building NSA from scratch is inefficient because it requires deploying both 4G and 5G hardware.
Decision Checklist
| Operational Requirement | If YES, select Architecture… | Why? |
| Is Latency < 15ms Required? | Standalone (SA) | NSA cannot reliably break the 20ms floor due to LTE core overhead. |
| Is Jitter < 5ms Required? | Standalone (SA) | Only SA offers the deterministic scheduling needed for control loops. |
| Are Uplink Workloads Heavy? | Standalone (SA) | SA supports Uplink-Centric TDD and Supplementary Uplink (SUL). |
| Do You Need Network Slicing? | Standalone (SA) | Slicing is a native feature of the 5G Core (5GC). |
| Is Reliability Critical (Safety)? | Standalone (SA) | URLLC features like packet duplication and pre-emption are SA-native. |
| Is the Focus Human Connectivity? | NSA / Private LTE | Humans don’t notice 30ms latency; the LTE ecosystem is mature. |
A Practical Roadmap Right Size Today Build an Upgrade Path to SA
Galaxy Broadband advocates for a “Right-Sized” strategy that delivers immediate value while securing the future.
Phase 1: The Foundation (Now) Deploy Private LTE or 5G NSA if the immediate need is worker connectivity. Most importantly, secure NCLL Spectrum immediately. This guarantees your “lane” on the highway regardless of the technology you run. Ensure your Radio Access Network (RAN) hardware is software-upgradeable to SA.
Phase 2: The Hybrid Pilot (12-18 Months) Introduce a Dual-Mode Core. Platforms like Nokia’s DAC can run a 4G and 5G SA network simultaneously. Keep worker tablets on the 4G layer and spin up a small 5G SA “slice” to pilot the first batch of AGVs.
Phase 3: Full SA Migration (24-36 Months) Transition fully to 5G SA when your fleet of autonomous vehicles scales up. Phase out the LTE anchor and repurpose the spectrum to widen the 5G pipe.
How Galaxy Broadband Supports SA vs NSA Planning
Galaxy Broadband sells connectivity outcomes, not just boxes.
- Discovery & Requirements Mapping: We parse the difference between “we need 5G” and “we need 5ms latency,” helping you avoid the “over-build” trap.
- NCLL Spectrum Strategy: Galaxy manages the entire ISED application process, securing the localized, licensed spectrum that makes Private 5G possible.
- Network Design for Outcomes: Utilizing carrier-grade Nokia hardware, we design networks that solve the “uplink problem” of mines and the “reflection problem” of factories.
FAQs
Is 5G SA always better than NSA for industry?
In terms of raw capability, yes. However, for basic worker connectivity, NSA is often more than sufficient and supports cheaper legacy devices.
What’s the biggest practical difference industrial teams will notice?
Predictability. SA networks don’t “stutter.” It feels like a wired connection that happens to be wireless.
Does SA automatically mean ultra-low latency?
No. SA enables it, but the network must be designed for it with the right TDD frame structure and Edge Core deployment.
Do you need SA for network slicing?
Yes. While NSA can use APNs for logical separation, only SA provides Hard Slicing—the guarantee of dedicated computing and radio resources.
Can you start with NSA and upgrade later without replacing everything? Yes, provided you deploy SA-Ready Hardware today. The upgrade becomes a software license activation and the introduction of a 5G Core.
Conclusion
NSA is for connectivity; SA is for control. If your roadmap includes autonomous robots, advanced machine vision, or massive sensor arrays, 5G Standalone is the foundational requirement. However, you don’t need to make a reckless leap. By leveraging the NCLL framework and partnering with experts, you can right-size your network today while laying the rails for the autonomous future.
Talk to Galaxy Broadband today to design a Private Network strategy that solves your connectivity headaches now, with a built-in bridge to the Industry 4.0 future.
