BREAKING NEWS: Firecell and Accelleran Merge to Deliver Sovereignty-Compliant Industrial Private 5G Learn more

BREAKING NEWS: Firecell and Accelleran Merge to Deliver Sovereignty-Compliant Industrial Private 5G Learn more
Home > End-to-End QoS in Private 5G Networks

End-to-End QoS in Private 5G Networks

End-to-end Quality of Service (QoS) is the backbone of private 5G networks, ensuring consistent performance across devices, radio access, core networks, and applications. This reliability is critical for industries like manufacturing, healthcare, logistics, and utilities, where even minor delays or disruptions can lead to costly operational issues. Unlike public networks, private 5G networks with QoS provide deterministic connectivity through traffic prioritisation, network slicing, and dedicated spectrum.

Key Points:

  • QoS Benefits: Guarantees ultra-low latency, high reliability, and precise traffic management.
  • Network Slicing: Creates virtual "lanes" with tailored performance for specific applications.
  • Core Components: RAN, core network, and backhaul infrastructure work together to maintain performance.
  • Industries Served: Manufacturing (robot control), healthcare (remote surgery), logistics (IoT), and more.
  • Tools for QoS: Solutions like Firecell’s Orion Labkits and Pegasus Networks simplify testing and deployment.

Private 5G with QoS is transforming industrial automation by delivering reliable, secure, and high-performance connectivity tailored to mission-critical applications.

Quality of Service (QoS) in 5G Network

Core Components of End-to-End QoS Architecture

End-to-End QoS Architecture in Private 5G Networks: Three-Layer Framework

End-to-End QoS Architecture in Private 5G Networks: Three-Layer Framework

In industrial automation, delivering reliable Quality of Service (QoS) over private 5G networks relies on three interconnected layers: the Radio Access Network (RAN), the Core Network, and the Transport/Backhaul infrastructure. Each layer plays a distinct role in ensuring critical industrial traffic maintains the required performance from the moment it leaves a device to when it reaches its destination.

Radio Access Network (RAN) QoS Mechanisms

The RAN is where QoS enforcement begins. Unlike the bearer-based system of 4G LTE, 5G RAN uses a flow-based model, with the "QoS Flow" (identified by a QoS Flow Identifier, or QFI) as its finest level of granularity. The gNB (Next Generation Node B) receives QoS profiles from the 5G Core, including parameters like 5QI (5G QoS Identifier) and ARP (Allocation and Retention Priority), which guide how traffic is handled over the radio interface. Within the gNB, the Service Data Adaptation Protocol (SDAP) sublayer maps QoS flows to Data Radio Bearers (DRBs). When multiple QoS flows share identical packet forwarding requirements, they can be mapped to a single DRB, optimising resource use while meeting performance standards.

"5G-RAN and 5G-Core ensure quality of service (e.g. reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs." – Techplayon

Standardised 5QI values define specific performance metrics. For example, 5QI 82, used in discrete automation, enforces a strict packet delay budget of 10 ms, while conversational voice (5QI 1) allows up to 100 ms. ARP ensures that mission-critical devices, such as autonomous robots, can pre-empt resources used by non-essential devices during congestion. These mechanisms form the foundation for the Core Network’s slicing capabilities.

Core Network and Network Slicing for QoS

The Core Network builds on RAN mechanisms by refining QoS delivery through dynamic network slicing. This approach creates virtual, end-to-end networks with dedicated resources, ensuring that heavy traffic in one slice does not affect another. Three key Core Network functions manage this process:

  • Session Management Function (SMF): Oversees QoS flows and links Service Data Flows to authorised QoS flows.
  • User Plane Function (UPF): Enforces QoS rules, applies QFI-based packet marking, and manages traffic steering and rate control.
  • Policy Control Function (PCF): Defines policy rules that regulate network behaviour across slices.

Within each slice, QoS Flow rules defined by 5QI enable precise application-level differentiation. For example, slices designed for ultra-reliable low latency communications (URLLC) target extremely high reliability, often achieving 99.999% uptime.

Transport and Backhaul QoS

The transport and backhaul network, particularly the N3 interface, connects the RAN to the Core Network, ensuring that QoS requirements are preserved as traffic moves through the physical infrastructure. User plane traffic relies on GTP-U (GPRS Tunnelling Protocol – User Plane), which embeds the QFI in its extension header to ensure consistent packet forwarding. Since transport networks typically use standard IP/Ethernet protocols, 5G systems map 5QI values to DSCP (Differentiated Services Code Point) markings for prioritisation.

For industrial applications demanding high reliability, Deterministic Networking (DetNet), a Layer 3 technology developed by the IETF, can be employed. DetNet minimises jitter and packet loss, ensuring deterministic communication across the transport network. However, any congestion or jitter in the backhaul can undo the QoS benefits established at the RAN, making constant monitoring of the N3 interface essential.

The next section will explore how these QoS mechanisms are applied in practical scenarios to ensure end-to-end performance assurance.

How Firecell Solutions Enable End-to-End QoS

Firecell’s private 5G solutions bring the principles of end-to-end QoS to life through practical, deployable systems. By combining pre-configured hardware, open-source software, and real-time management tools, they allow businesses to test, validate, and deploy networks with guaranteed QoS. Their offerings focus on two main product lines: Orion Labkits for testing in controlled environments and Pegasus Networks for full-scale deployment. Let’s explore how each product line contributes to achieving reliable QoS.

Firecell Labkits for QoS Testing

Orion Labkits provide a controlled private 5G environment, covering areas between 10 and 1,000 m², specifically designed for testing and validating QoS configurations before rolling out full-scale networks. Built on OpenAirInterface (OAI) technology and aligned with 3GPP standards, these labkits support up to 64 devices simultaneously, delivering latency under 10 ms on 100 MHz models.

The integrated Network Management System (NMS) allows IT teams to assign priorities to different data streams. For instance, critical robot control data can be isolated from lower-priority traffic, ensuring uninterrupted operations. Additionally, Wireshark integration offers detailed, real-time diagnostics, making troubleshooting straightforward.

Dr. Richard Candell from NIST highlighted the unique capabilities of Firecell’s Labkit, stating:

"Having full visibility on the core and radio access network (RAN) and their different interfaces is unique and one of the key factors behind NIST choosing Firecell’s Labkit".

Setting up the labkit is quick, requiring less than 15 minutes with pre-installed scripts. Quarterly software updates ensure new QoS features are added without needing hardware upgrades. Pricing begins at €11,900 for the Orion Labkit 40 (40 MHz bandwidth, 160 Mbps downlink), while the Orion Labkit 100 (100 MHz bandwidth, 800 Mbps downlink) is priced at €29,900. Annual support and maintenance cost €5,580. For advanced RAN programmability, the O-RAN variant is available for €22,900, offering the same 100 MHz performance with Split 7.2 architecture.

Once QoS is validated in this controlled setting, Firecell’s Pegasus Networks take over to deliver these capabilities in demanding, real-world environments.

Firecell Pegasus Networks for Guaranteed QoS

Pegasus Networks

Pegasus Networks expand QoS capabilities to large-scale, operational settings like manufacturing plants, ports, airports, and logistics hubs. Using network slicing, these systems create isolated virtual networks for specific applications, ensuring critical traffic – like robot control – maintains sub-millisecond latency, even with simultaneous video streaming or IoT data loads. Dynamic QoS flow rules are enforced by the Session Management Function (SMF) and User Plane Function (UPF), while the NMS provides live monitoring of bit rates, resource utilisation, and SLA adherence.

Operating on private licensed frequencies, Pegasus Networks achieve latency and jitter under 20 ms, a stark improvement over the 200 ms typical of standard Wi-Fi. Coverage options range from Low Power models (30–100 m) to High Power variants (1,000–5,000 m), with seamless handovers at speeds up to 35 km/h. A notable example of this technology in action occurred in June 2025, when Inria deployed Firecell’s private 5G for smart agriculture, enabling robotic farming systems to operate with real-time control and positioning.

Pegasus Networks integrate effortlessly with existing LANs, automatically assigning IP addresses via DHCP to maintain QoS continuity. Pricing for Pegasus Pop-Up models starts at €32,900, with annual fees from €5,264. Larger deployments are customised based on specific site needs.

Following Firecell’s merger with Accelleran, the platform now incorporates AI-driven RAN optimisation and programmable network functions (xApps/rApps). These enhancements enable real-time QoS adjustments for industries like port automation and discrete manufacturing, further solidifying Firecell’s position as a leader in private 5G solutions.

Testing and Monitoring End-to-End QoS

Deploying a private 5G network with reliable QoS demands thorough testing from the initial lab phase through to continuous operational monitoring. Each stage is essential to ensure consistent QoS delivery across all network layers.

Lab Validation and Pre-Deployment Testing

Lab testing is where it all begins. It’s the stage where engineers confirm that QoS configurations work as intended. This involves validating the physical infrastructure and synchronisation mechanisms, which are crucial for maintaining steady performance. For example, precision timing – using GPS-based systems or a grandmaster clock – keeps radio units in sync, ensuring consistent results.

Another key focus is ensuring interoperability between the 5G core and Radio Access Network components. Engineers test critical performance indicators like throughput, latency, and coverage under simulated loads. Tools like Firecell’s Orion Labkits are invaluable here. They allow IT teams to assign traffic priorities, isolate critical data streams, and troubleshoot in a controlled environment. Thanks to their rapid setup and regular updates, these labkits allow for quick iterations without needing hardware replacements.

After lab tests, the next step is field testing, where configurations are checked under real-world conditions.

Field Testing and QoE Validation

Field testing takes the lab results and puts them to the test in real-world environments. This stage evaluates whether QoS translates into a high-quality user experience (QoE). Both passive and active testing methods come into play here.

  • Passive testing involves using network scanners to monitor downlink signals without a SIM card. This helps verify RF parameters like signal strength (RSRP) and quality (SINR).
  • Active testing, on the other hand, uses a connected 5G device to assess user-level performance. This includes uplink behaviour, mobility procedures, and application-level QoE.

For industrial use cases, standard ping tests just won’t cut it. Instead, engineers rely on interactivity tests based on the Two-Way Active Measurement Protocol (TWAMP). These tests mimic real-world traffic patterns by adjusting packet size and frequency. Gregor Tomic from Rohde & Schwarz highlights the importance of this approach:

"Understanding network performance closely resembling real-life scenarios (such as Industry 4.0 process automation) is possible with our interactivity test that we developed in house based on TWAMP".

In April 2023, Rohde & Schwarz engineers tested a private 5G network at their Teisnach plant. Over 24 hours, they transmitted 607,500 packets, achieving a stable median round-trip time of 16.39 milliseconds and 99.9999% availability within approximately 18.5 hours.

For throughput validation, iperf3 remains the go-to tool. It typically uses UDP streams to avoid the overhead of TCP acknowledgments. Recent tests in private 5G standalone networks have shown throughput results between 800 Mbps and 1 Gbps, with ping values occasionally dropping below 10 milliseconds. However, environmental factors like machinery and metal shelving can create dead zones, which must be factored into the testing.

The insights gained from field testing are vital for continuous monitoring, which ensures QoS is maintained over time.

Continuous Monitoring and SLA Compliance

Once the network is up and running, continuous monitoring becomes essential to maintain SLA compliance and catch any performance issues early. This involves deploying robust data collection probes across facilities or on mobile assets like AGVs. These probes provide round-the-clock performance tracking.

Real-time monitoring tools, such as Firecell’s Network Management System, offer customisable dashboards and automated alerts when QoS metrics deviate from SLA requirements. These systems track key metrics like bit rates, resource utilisation, and SLA adherence. Arnd Sibila explains the importance of this:

"Every modification in the network, e.g. moving a metal shelf or robot on the factory shop floor, will affect the signal propagation characteristics and can affect the coverage and network performance".

Best Practices for End-to-End QoS Implementation

Getting QoS (Quality of Service) right in a private 5G network means making decisions that reflect your operational goals. The key difference between a network that just works and one that fully supports mission-critical operations lies in how you prioritise traffic, use network slicing, and integrate with existing systems.

Prioritising Critical Traffic

The backbone of successful QoS is identifying which applications are most critical. Start by mapping each application – like PLC signalling, telemetry, or VoIP – to a specific 5QI (5G QoS Identifier) to define requirements around latency, jitter, and error rates. However, keep in mind that QoS on its own operates as a "best effort" system. High traffic in one area can still impact performance elsewhere, even if priorities are set.

For a more reliable approach, combine QoS rules with network slicing. By running QoS flows within dedicated slices, you can ensure that spikes in general data traffic don’t disrupt key operations. For example, industrial automation often relies on URLLC (Ultra-Reliable Low Latency Communications) slices, which are engineered for extreme reliability and aim for 99.999% uptime. This method of prioritisation ensures network slicing is used to its full potential.

Using Network Slicing Effectively

Network slicing takes QoS to the next level, turning it into a guaranteed service rather than just a priority system:

"Network slicing fundamentally changes how QoS is implemented, moving it from a ‘best effort’ priority system on a shared network to an enforced guarantee within a dedicated environment".

Think of it as creating dedicated virtual motorways instead of merely adding traffic signals to a shared road.

The choice between static and dynamic slicing depends on your operational needs. Static slicing permanently allocates resources, making it ideal for long-term industrial applications where consistent performance is non-negotiable, regardless of network load. On the other hand, dynamic slicing adjusts resources in real time, perfect for temporary services like live event streaming or video conferencing. Within these slices, QoS flows can further refine traffic handling. For instance, a single device might use an eMBB (enhanced Mobile Broadband) slice for machine vision while relying on a URLLC slice for control loops – each slice offering distinct, guaranteed performance.

Once these dedicated virtual networks are set up, the next step is to integrate QoS rules into your existing systems for smooth operations.

Integrating QoS with Existing Infrastructure

Start by setting up PDU (Protocol Data Unit) sessions with default QoS, then gradually modify active sessions to request specific QoS levels as application needs become clearer. This phased approach allows you to test configurations without disrupting live operations. In industrial settings, 5G QoS mechanisms can be aligned with established standards like Time-Sensitive Networking (TSN), OPC UA, and DetNet, ensuring the deterministic communication required for consistent industrial connectivity.

Modern industrial devices often handle multiple traffic types simultaneously – such as machine vision and control loops – with each requiring its own QFI (QoS Flow Identifier). Implement systems to monitor QoS in real time, enabling applications to adjust dynamically if network conditions shift, and ensuring compliance with SLA (Service Level Agreement) requirements. As mentioned earlier, tools like Firecell’s Network Management System can provide the necessary dashboards and alerts to maintain this level of control.

Conclusion: The Future of QoS in Private 5G Networks

End-to-end Quality of Service (QoS) is the backbone of private 5G networks, especially for mission-critical industrial applications. Every layer – radio access, core, and backhaul – needs to work seamlessly to provide the reliable performance that industries like manufacturing, logistics, and autonomous systems require. Without this, even cutting-edge robotics and IoT setups face the risk of connectivity failures, potentially bringing operations to a standstill.

The shift towards more proactive operational strategies is transforming the industry. By leveraging sensor data and AI-driven robotics, businesses are moving beyond reactive approaches, reducing costs and enabling greater autonomy. For example, predictive maintenance has the potential to lower overall maintenance expenses by up to 30%. However, despite these benefits, over half of manufacturers are either still in the experimental phase or have yet to adopt such technologies. This leaves a significant opportunity for those who embrace these advancements early.

The merger between Firecell and Accelleran in February 2026 has further strengthened the private 5G landscape. Their unified platform now integrates core and RAN capabilities into a single, streamlined solution that can be managed by standard IT teams. Whether you’re experimenting with an Orion Labkit for a small 10 m² setup or deploying a Pegasus Network across 10,000 m², the emphasis remains on delivering uninterrupted connectivity with QoS guarantees backed by Service Level Agreements.

Looking ahead, combining 5G with technologies like TSN (Time-Sensitive Networking), OPC UA, and DetNet will bring even greater levels of deterministic communication. This push for transparency and control is poised to shape the future of industrial connectivity, setting new benchmarks for reliability and performance.

FAQs

What’s the difference between QoS and network slicing in private 5G?

QoS (Quality of Service) and network slicing serve different purposes but work hand-in-hand in private 5G networks. QoS focuses on managing and prioritising network traffic to ensure that critical applications perform reliably and efficiently. On the other hand, network slicing divides a shared infrastructure into isolated virtual networks, with each slice tailored to specific use cases. While QoS operates within or even across these slices, network slicing provides the structure that allows multiple customised networks to function simultaneously.

How do I choose the right 5QI and ARP settings for my applications?

To choose the correct 5QI (5G QoS Identifier) and ARP (Allocation and Retention Priority) settings, start by determining your application’s specific QoS requirements – things like latency, reliability, and bandwidth. Then, align these requirements with the appropriate 5QI value listed in the 5QI table. For critical applications, assign a higher ARP priority to make sure they get the necessary bandwidth and low latency, even when the network is congested.

What’s the best way to test and monitor end-to-end QoS before and after go-live?

To ensure end-to-end QoS is up to par, begin by checking the private 5G network’s infrastructure. This includes verifying synchronisation and coverage to ensure the network is ready to support demanding applications. During deployment and beyond, active testing with synthetic traffic can help measure critical QoS metrics such as latency, jitter, and throughput. For continuous performance monitoring, take advantage of 5G QoS mechanisms that allow real-time adjustments to network parameters, ensuring the network remains stable and dependable.

Related Blog Posts

Share
Breaking news
Firecell and Accelleran Merge to Deliver Sovereignty-Compliant Industrial Private 5G
Want to become a Partner?
Calculate your TCO