Networks and connectivity

Quality of service and traffic priority: what to assess in a critical communications network

When voice, video and data compete for resources, the network needs policies that reflect the operation. Quality of service, priority and pre-emption are related mechanisms with different functions. Planning should verify how these policies are applied and tested, without treating a priority label as a guarantee of communications performance.

Distinguish packet treatment from admission

In LTE with EPC, QCI references QoS characteristics; in 5GS, 5QI references characteristics of QoS flows. These identifiers are not simply application names. Selection should consider the service and treatment supported by the infrastructure, rather than automatically copying codes from another deployment or a generic configuration example.

ARP addresses allocation and retention priority, including the capability and vulnerability to resource pre-emption. This is distinct from packet scheduling priority. The project should explain which flows may be admitted, retained or affected when resources are limited, according to the policies defined for the network.

Verify policies from core to application

PCRF participates in policy control in EPC; PCF performs policy control functions in 5GS. Rules must be compatible with the components that actually enforce them. Having these functions in an architecture does not demonstrate that an application received the operational priority intended by the project.

As a design recommendation, record which users, devices and services receive differentiated treatment and under which conditions. Assess radio access, transport, core and servers. A bottleneck outside the controlled segment can harm the experience even when the QoS profile is correctly configured elsewhere in the network.

Validate under load and during failures

Prepare tests with competing traffic, mobility and different radio conditions. Observe call establishment, delay, losses and essential application behavior. Criteria should be defined for the operation and measured along the complete path, rather than using only a speed test performed under favorable conditions.

Document results, limitations and alternative procedures. QoS does not create unlimited capacity or establish mission critical conformity by itself. Implementation, compatible versions and application support need confirmation. Review policies after equipment or traffic changes to keep the configuration connected to operational requirements and the observed performance.

What to assess for your project

  • Identify services and operational quality criteria.
  • Distinguish QCI or 5QI from ARP and pre-emption.
  • Verify policies and component compatibility.
  • Test competing traffic, mobility and recovery.

COM3

How COM3 can help

COM3 can support QoS and traffic priority assessment, connect requirements to available policies and organize communications tests. Subject to the infrastructure, the project can include integration and monitoring, with documented criteria and limitations and without assuming mission critical guarantees.

Topics in this article

Further reading and references

Technical sources consulted for the fundamentals of this content. Project recommendations are an editorial synthesis by COM3.

Share this article

Chat on WhatsApp