A private 5G lab can use conducted level tests to investigate receiver margin before site deployment. The bench result needs a clearly defined relationship to the field question.
Why this matters in the industry
Factory or campus users care about reliable service at required locations. A conducted test can isolate a radio's level behavior, while the installed network also depends on propagation and network conditions.
The technical reasoning
Private-network coverage questions include building layout, radio placement, traffic and interference. A bench experiment can isolate receiver behavior or a defined path-loss tolerance but cannot encompass the entire deployment. Map each coverage concern to the kind of evidence needed: controlled radio tests, propagation measurements or network-level observations.
A controlled link is not a complete propagation environment
Static attenuation changes signal level but does not reproduce all channel impairments. A real wireless link can include time-varying fading, multipath, Doppler, interference and changing antenna geometry. Receiver behavior also depends on acquisition, tracking and adaptation loops. A conducted experiment is valuable because it isolates selected variables, but its controlled simplicity must remain visible when interpreting a result for a deployment or moving platform.
How to structure the investigation
Define a wanted-signal level range and an application metric such as packet delivery or latency. Sweep loss in a controlled bench setup, then compare those results with an approved site survey. Keep radio configuration and traffic load in the report.
State which impairment is deliberately varied and which conditions stay fixed. Define the observed outcome, sample duration and receiver state, then repeat the experiment under relevant configurations. Use a channel emulator or field observations when the question requires time variation or spatial effects. Tie bench findings to a stated deployment model rather than converting a laboratory loss value directly into a guaranteed distance or availability percentage.
Worked example or engineering scenario
A sensor passing a laboratory test with 80 dB path loss does not guarantee operation at a particular factory distance; antennas, obstructions, interference and channel variation change the field situation.
Evidence to collect
| Record | Purpose |
|---|---|
| Define the application metric | Defines the tested state and scope of the comparison. |
| Record radio configuration | Makes the stimulus or route condition reproducible. |
| Measure input level | Supports interpretation of variation and possible confounding effects. |
| Plan a separate site survey | Connects the observation with the stated engineering decision. |
Trade-offs and common interpretation errors
A working static link may fail to acquire after an abrupt change, or may behave differently in interference than in noise. Report those experiments separately. A bench threshold is evidence about the defined test, while coverage and availability conclusions require additional assumptions and representative environmental evidence.
What the result can support
Use bench findings as inputs to a deployment study, with site conditions recorded independently.
Static bench loss cannot account for every obstruction, interferer or scheduler behavior in a deployed network.
Further technical reading
- NIST: Wireless Systems in Industrial Environments
- Keysight: Cellular Base Station Performance Testing
Related industry knowledge
- Distributed Antenna Systems: Measuring Passive Path Loss
- Bias-Fed Cellular Test Paths: Where a DC Block Belongs
Numerical scenarios are illustrative assumptions, not reported measurements of a supplied product or installation.