Contact Us

A 5G router should not be selected for edge video by comparing a modem’s peak specification with a camera’s average bitrate. The real engineering question is whether the complete deployed path can sustain the video workload when traffic peaks, radio conditions, cell loading and local network bottlenecks are included .

For remote surveillance, machine vision, transport video and other edge-computing projects, start with the application rather than the router brochure. Define how much traffic the system actually produces, how many streams can operate at the same time, what delay behaviour the receiving application can tolerate and which parts of the local network may limit traffic before it reaches the cellular uplink.

Once those conditions are understood, router selection becomes much more useful. Instead of asking which device has the largest headline speed, the project team can match the required uplink, local interfaces, redundancy and installation conditions to the right industrial 5G router architecture.

Direct answer

Estimate the real video workload first, then prove that sustainable field uplink remains above that workload under representative conditions. Treat latency, packet delay variation and packet loss as separate acceptance variables, and isolate Ethernet, Wi-Fi and processing limits before assuming the cellular router is the bottleneck.

Why the modem specification is not the project throughput

A modem specification describes what a radio platform may support under defined technical conditions. It does not tell a video integrator how much sustained application traffic will reach a remote server from a particular factory, roadside cabinet, vehicle or unattended monitoring site.

The real path contains several independent stages. Video must be captured and encoded, moved through the edge platform, passed over Ethernet or Wi-Fi, processed by the router, scheduled onto the cellular uplink, carried through the mobile network and delivered to the receiving application. Any one of those stages can become the limiting point.

Fixed surveillance site
The practical question is whether a continuous group of streams can stay inside the available uplink envelope during the periods when remote viewing or recording actually matters.
Machine vision
Average traffic may hide short bursts created by inspection events, image uploads or processing results. Timing can matter as much as total data volume.
Mobile video backhaul
Performance needs to be judged across the operating route or coverage area rather than from one stationary test in a favorable location.

The same router can therefore produce different field results at different locations or times without anything being wrong with the hardware. Radio quality changes, network demand changes and local processing load changes. For project planning, the useful value is not the fastest result observed once; it is the performance envelope the application can depend on.

1. Separate encoded bitrate from the traffic the network must actually carry

Camera count alone is not a bandwidth calculation. Two installations with the same number of cameras may place very different loads on the uplink because encoded bitrate, scene complexity, stream concurrency and application behaviour differ.

Begin with the streams that can operate at the same time. Record the normal encoded bitrate for each active stream, whether traffic varies significantly, and whether the stream is continuous, event-driven or transmitted only when an operator requests it. Include other traffic sharing the same connection, such as telemetry, control messages, file uploads or remote management.

Build the requirement from the video system

Use a traffic envelope rather than one average bitrate

Work in Mbps throughout: add the design bitrate of every simultaneous video stream, other WAN traffic, protocol overhead and a project-specific operating reserve. Use measured peaks where available so variable-rate traffic is not counted twice.

Simultaneous Video Sum of concurrent stream design bitrates, in Mbps
+
Other WAN Traffic Uploads, control and telemetry sent at the same time, in Mbps
+
Overhead & Reserve Protocol overhead and project-specific operating margin, in Mbps
→
Required Uplink Envelope Total planned capacity to validate under field conditions
Illustrative calculation (not a product benchmark): suppose four concurrent streams are each budgeted at a 5 Mbps design bitrate: 4 × 5 = 20 Mbps of video. Add an assumed 2 Mbps of simultaneous non-video traffic, a 2 Mbps protocol-overhead allowance and a project-selected 6 Mbps operating reserve. The resulting planning budget is 20 + 2 + 2 + 6 = 30 Mbps uplink. These figures are hypothetical, not measured camera traffic or E-Lins router performance. Verify the actual traffic peaks, overhead and reserve, then confirm that sustainable application-level uplink meets the budget during representative field conditions; the modem’s advertised peak rate is not that measurement.

Variable-rate encoding makes this distinction more important. A stream can have an acceptable average bitrate while still creating higher bursts during visually complex scenes. If several streams peak at roughly the same time, the resulting queue can affect both throughput and delay.

Edge processing changes the WAN calculation only when it changes what leaves the site. A system that performs analytics locally and sends selected events can create a very different cellular workload from a system that still uploads every full video stream. Budget the behaviour of the deployed workflow, not the theoretical benefit of having an edge computer available.

Edge video is often uplink-heavy, so a generic download-speed result is a poor substitute for project validation. What matters is the uplink available from the real installation position while the mobile network is operating under conditions the project is likely to encounter.

Field throughput can be lower than a modem specification because radio conditions, network configuration, spectrum resources, uplink scheduling and cell loading all influence usable capacity. The design should therefore compare the video workload with sustainable measured uplink, not with the largest number shown in a modem data sheet.

1
What is the busiest normal video workload?

Test the combination of video streams and other traffic that the site can realistically generate during normal operation.

2
When does network performance matter most?

A test performed only during a convenient quiet period may not represent the conditions that matter to production, security or remote monitoring.

3
Is the router fixed or mobile?

A fixed cabinet can be characterised at its installation site. A vehicle or transport-video project needs measurements across the route or operating area.

4
Does performance remain above the workload long enough?

One fast test proves only that capacity was available briefly. Video projects normally need repeatable performance across a longer operating period.

The lower, repeatable performance seen under realistic conditions is often more useful for engineering than a single peak result. It shows whether the connection still has enough operating headroom when conditions are less favorable but remain within normal operation.

3. Define the latency and delay-variation budget before judging the router

Throughput answers only one part of the performance question. A connection may carry enough bits per second and still perform poorly for a time-sensitive video workflow if delay varies excessively or packet loss disrupts delivery.

There is no universal latency value that makes every industrial video system acceptable. Remote surveillance, interactive mobile video and machine-vision workflows can have very different tolerance for end-to-end delay.

End-to-end latency budget

The cellular router is only one part of the delay path

Measure the complete chain before assigning the entire latency result to 5G.

01
Capture Camera timing
02
Encode Processing and buffering
03
Local LAN Ethernet or Wi-Fi
04
5G Path Router and mobile network
05
Remote WAN Path to server
06
Application Decode or analysis

Start by defining the maximum capture-to-display or capture-to-analysis delay the workflow can tolerate. The estimated end-to-end budget covers capture, encoding, local networking, cellular transport, the remote path and application decoding or analysis. A ping result measures network round-trip time (RTT), not one-way delay or glass-to-glass video latency. For acceptance, measure frame capture and display or processing times with synchronized timestamps or a suitable camera-to-screen method, while the intended video workload is running. Compare repeated results, especially during the required operating periods, with the project’s delay limit. Define acceptable packet delay variation separately: irregular packet arrival can increase buffering needs and make real-time behaviour less predictable.

Technical reference: the RFC Editor’s RFC 3393 defines IP packet delay variation and provides a useful technical framework for discussing variable packet arrival rather than treating all delay as one number.

Packet loss should also be recorded separately. Depending on the application and transport method, loss may appear as visual degradation, additional buffering, retransmission effects or interrupted control behaviour. Throughput, latency, packet delay variation and packet loss should therefore remain separate acceptance variables rather than being compressed into one vague idea of network speed.

4. Isolate Ethernet, Wi-Fi and processing limits before blaming the cellular link

Poor remote-video performance does not automatically prove that the cellular connection is the bottleneck. Traffic may already be constrained before it reaches the router.

Confirm the video source first

Check that the encoder or edge computer is actually producing the traffic assumed by the bandwidth plan. If the source is already throttling, buffering or dropping traffic, the WAN test begins with the wrong baseline.

Check the wired local path

Verify that Ethernet interfaces, switching and local configuration can carry the target traffic without creating an unexpected rate limit or queue before packets reach the router.

Separate Wi-Fi performance from 5G performance

When cameras or edge computers connect over Wi-Fi, local wireless conditions become an independent variable. A weak or congested WLAN can make a healthy cellular connection appear slow.

Observe edge-processing load

Encoding, analytics, encryption and other workloads may compete for compute resources. A processing bottleneck will remain even if the cellular router or data plan is changed.

Then measure the cellular segment

Once the local path can carry the intended load cleanly, throughput and latency measurements across the 5G connection become much easier to interpret.

When replacing the router is unlikely to solve the problem

If the video source cannot sustain the required output, or the Ethernet or Wi-Fi path already falls below the target load before traffic reaches the cellular router, changing the 5G router does not address the root cause. Fix the bottleneck that the measurements actually identify.

5. Test with the traffic pattern the edge-video deployment will really use

A generic speed test answers a generic network question. An edge-video acceptance test should answer a project question.

Where practical, reproduce the intended stream count, encoding settings and transmission behaviour. Run the test long enough to observe whether throughput, latency, packet delay variation or loss changes as radio and network conditions move.

Weak evidence

A short speed test reaches a high result once. This proves that capacity was briefly available, but not that the real video application will remain inside its required performance envelope.

Useful project evidence

The intended video load runs under representative site or route conditions while uplink throughput, latency, delay variation, packet loss and local-path behaviour are recorded together.

Keep the conditions with the result

A throughput number is more useful when another engineer can reproduce it

Installation location or vehicle route
Stationary or mobile operating state
Number of concurrent video streams
Encoder settings used during the test
Observed sustainable uplink
Latency and packet delay variation
Packet-loss behaviour
Ethernet or Wi-Fi local connection
Other traffic sharing the router
Time period and relevant network conditions
Testing reference: the RFC Editor’s RFC 6349 provides a framework for end-to-end TCP throughput testing. Its end-to-end approach reinforces an important field rule: a useful throughput result should be tied to the complete path and the conditions under which it was measured. Because RFC 6349 addresses TCP testing, it does not replace application-level validation with the actual video transport protocol and traffic pattern.

The test pattern should follow the project. A fixed remote surveillance site may need observations across different network-loading periods. A mobile deployment should be tested across the real operating area. A machine-vision system should reproduce the traffic bursts and timing behaviour created in production rather than substitute an unrelated download benchmark.

Match the measured video requirement to the router architecture

Once the workload, local topology and field acceptance conditions are known, product selection becomes much more specific. The products below represent different deployment directions rather than a simple good-better-best ranking.

Move from calculation to hardware

Choose the router according to the network it must sit inside

A larger multi-interface edge site, a compact remote cabinet and a mobile or embedded installation do not necessarily need the same router architecture. Start from the local devices, redundancy requirement, power arrangement and installation space, then confirm the exact ordered configuration.

Multi-device edge networking

H900f Dual SIM Industrial 5G Router

The H900f direction makes sense when the cellular router sits between several local devices and the mobile WAN. Its product architecture includes multiple Ethernet interfaces and dual-SIM cellular networking, so it is more relevant to a larger edge site than a simple single-device handoff.

Suitable for Video system integrators connecting an NVR, edge computer, industrial camera network or several wired devices at one remote location, especially where cellular failover is part of the network design.

Check first: confirm the exact Ethernet, Wi-Fi, PoE, serial and SIM options required by the project before ordering. Optional features should not be assumed to be included in every configuration.

View H900f Product Details
Mobile and distributed video

H900uf Industrial 5G Router

The H900uf is a more compact industrial 5G router direction for deployments where the network edge may move or where installation space is more limited. Its Ethernet, cellular and optional wireless capabilities make it relevant to distributed and in-vehicle network architectures.

Suitable for Transport-video projects, vehicle systems, mobile surveillance, temporary monitoring points and distributed edge sites where operating conditions may change with location.

Check first: confirm the RJ45 interface count, SIM, Wi-Fi, serial and positioning options against the exact H900uf configuration and datasheet before ordering.

Explore H900uf
Compact remote-site direction

H685f-P2 5G Router with PoE In

H685f-P2 is a different fit from the larger H900 architecture. Its compact format and PoE-input product direction make it relevant where installation space, simplified power delivery and a smaller local network are more important than a larger multi-device router layout.

Suitable for Compact CCTV cabinets, remote monitoring points, embedded industrial systems and edge locations where the router needs to sit close to the video equipment.

Check first: confirm PoE input and any required Wi-Fi, serial or other optional functions for the exact configuration being ordered.

View H685f-P2
Procurement decision

Use the workload to narrow the wider industrial 5G router range

Product selection should now follow the network architecture that the earlier calculation and testing established. Before requesting a final model confirmation, define the following requirements.

Video workload Concurrent streams, encoded bitrate behaviour and peak traffic conditions.
Uplink acceptance Sustainable field throughput required under representative conditions.
Local interfaces Number of wired devices, Wi-Fi use, serial connections and PoE requirements.
Cellular redundancy Whether the site needs dual-SIM failover or another WAN resilience strategy.
Installation type Compact cabinet, larger fixed edge site, vehicle or other mobile deployment.
Latency sensitivity Maximum acceptable end-to-end delay and delay variation for the workflow.

Use an application-level acceptance check before the site goes live

A successful internet connection is not enough for edge-video acceptance. The final test should compare the observed workload, sustainable uplink, end-to-end delay, delay variation and loss with the project’s agreed limits, and record whether each requirement passes during representative conditions before the site goes live.

Edge-video go-live check

✓
Concurrent video load is known

The bandwidth budget reflects the streams that can actually operate together.

✓
Sustainable uplink has been measured

Testing reflects the site, route and operating period that matter to the project.

✓
Latency, delay variation and loss have limits

The project uses application requirements rather than a generic promise of low latency.

✓
Local bottlenecks have been isolated

Ethernet, Wi-Fi and processing performance are checked before cellular troubleshooting begins.

✓
The real traffic pattern has been tested

The validation run reflects the intended stream count, transmission behaviour and deployment state.

✓
The exact router configuration has been confirmed

Ethernet, Wi-Fi, SIM, PoE, serial and other project-specific options are checked against the selected model before purchase.

The purchasing rule is straightforward: start with encoded traffic, concurrent streams, uplink conditions and the latency/delay-variation budget; then choose the router architecture that fits the measured workload and local network.

This keeps the industrial 5G router decision tied to the actual edge-video project rather than to an isolated modem specification.

Frequently asked questions

Why is measured 5G throughput lower than the modem specification?
A modem specification describes platform capability under defined conditions. Field throughput depends on radio conditions, uplink scheduling, network configuration, cell loading and the rest of the end-to-end path. Local Ethernet, Wi-Fi or processing limits can also reduce the application result. Use sustained measurements from representative conditions rather than a modem’s peak rate for video planning.
What latency should an industrial 5G router deliver?
There is no single latency value that is correct for every industrial video application. Define the maximum acceptable end-to-end delay for the workflow, then determine how much delay is introduced by capture, encoding, the local network, cellular transport and the receiving application. Delay variation and packet loss should be evaluated alongside average latency.
How should multiple video streams be included in a throughput budget?
Include the measured encoded traffic of every stream that can operate concurrently, then account for normal traffic variation, other traffic sharing the connection and an appropriate operating margin. Do not multiply by total camera count unless every camera actually uploads at the same time.
Which bottlenecks should be isolated before blaming the cellular link?
Check the video source or encoder, the edge-processing platform, Ethernet and any local Wi-Fi connection first. If traffic is already constrained before it reaches the 5G router, replacing the cellular router is unlikely to solve the root cause.

Send the video workload, not just a request for a fast 5G router

E-Lins can narrow the hardware more effectively when the inquiry includes the conditions that actually determine edge-video performance and installation fit. A short but specific requirement is more useful than asking for the highest-speed model.

Number of concurrent video streams
Encoded bitrate or measured traffic
Fixed-site or mobile deployment
Country and cellular network requirement
Required Ethernet and Wi-Fi topology
PoE input or output requirement
Dual-SIM or failover requirement
Latency-sensitive application requirement

With those details defined, the project can move from theoretical modem capability to a router choice that matches the real video workload, local interfaces and field conditions.

Leave a Reply

Your email address will not be published. Required fields are marked *

Contact Us

Have a question or need assistance? Fill out the form below, and we’ll get back to you as soon as possible.