Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Effective priority

Effective priority

Services →

Effective priority is the final priority level determined by a transmission control server for MCPTT services, based on parameters like transmission priority, participant type, and call type.

Introduced
Rel-13
Where
Services
Specifications
2 specs
Effective priority Description Purpose What changed Neighbours Specifications

Description

Effective priority is a concept defined in 3GPP specifications for mission-critical communication services, particularly in the context of the transmission control server (TCS) for services like Mission Critical Push To Talk (MCPTT), Mission Critical Video (MCVideo), and Mission Critical Data (MCData). It represents the final priority decision made by the transmission control server when arbitrating among multiple transmission requests. Unlike a simple priority value, the effective priority is computed dynamically based on a combination of factors, including the transmission priority requested by the user, the type of participant (e.g., dispatcher, first responder), the type of call (e.g., emergency, normal), the current state of the session, and local policy configured by the operator. This computed priority determines which user is granted the right to transmit when multiple requests are pending.

The transmission control server is the central entity in MCPTT and related services that manages the floor (the right to transmit). When a user requests to transmit, they send a floor request message to the TCS. The TCS evaluates the request against other pending requests and the current floor holder. The effective priority is the result of this evaluation. It is not simply the priority level included in the request; rather, it is a derived value that takes into account the context. For example, an emergency call may have a higher effective priority than a normal call, even if the requested transmission priority is the same. Similarly, a dispatcher may have a higher effective priority than a regular user. The TCS uses the effective priority to decide whether to grant the floor, queue the request, or reject it.

The calculation of effective priority involves several input parameters. These include the transmission priority (a numerical value indicating the importance of the transmission), the participant type (e.g., MCPTT user, dispatcher, supervisor), the type of call (e.g., group call, private call, emergency call), the current participant to which transmission is granted (if any), and the local policy of the TCS. The local policy can define rules such as 'emergency calls always preempt normal calls' or 'dispatchers have priority over users'. The TCS combines these inputs according to a standardized algorithm or operator-defined rules to produce the effective priority. This allows for flexible and context-aware prioritization, ensuring that critical communications are handled appropriately.

The concept of effective priority is essential for the correct operation of mission-critical services. In emergency situations, it is vital that the most important communication gets through. For instance, a first responder at the scene of an incident should be able to preempt other users. The effective priority mechanism ensures that such preemption is possible based on a holistic view of the situation, rather than just a static priority level. It also allows operators to implement their own policies, such as giving priority to certain agencies or roles. The term was introduced in Release 13 as part of the initial MCPTT specifications, and it has been refined in subsequent releases. In Release 14, the terminology was updated from 'floor control server' and 'floor priority' to 'transmission control server' and 'transmission priority' to reflect the broader applicability to MCVideo and MCData. The definition has remained stable since then, indicating the maturity of the concept.

In summary, effective priority is a dynamic, context-aware priority value computed by the transmission control server to arbitrate transmission requests in mission-critical services. It ensures that the most important communication is granted the floor, taking into account a variety of factors and operator policies. This mechanism is crucial for the reliability and effectiveness of mission-critical communications, where every second counts.

Purpose & Motivation

The effective priority concept was created to address the need for sophisticated prioritization in mission-critical push-to-talk (MCPTT) and related services. Traditional push-to-talk systems often used simple priority levels, where a user could request a high priority, but this could be abused or not reflect the actual urgency. In emergency situations, it is essential that the communication system can dynamically determine who should get the floor based on the context, such as the type of call, the role of the user, and the current situation. Effective priority solves this by allowing the transmission control server to compute a priority that considers multiple factors, ensuring that critical communications are not blocked by less important ones.

The motivation for effective priority came from the requirements of public safety and mission-critical users. These users need a system that can guarantee that a first responder at an incident scene can communicate with their team even if the network is congested with other traffic. Simple priority schemes could not handle the complexity of such scenarios. For example, a dispatcher might need to override a user, or an emergency call might need to preempt all other calls. Effective priority provides a standardized way to implement these policies. It also allows operators to customize the behavior to match their operational procedures, by defining local policies that influence the computation.

Before effective priority, MCPTT systems might have used static priority levels, which were inflexible and could lead to incorrect arbitration. For instance, if two users requested the floor with the same priority, the system might grant it to the first one, even if the other was in a more critical situation. Effective priority introduces a dynamic evaluation that can consider the type of call (e.g., emergency vs. normal), the participant type (e.g., dispatcher vs. user), and other factors. This ensures fair and appropriate access to the channel. The concept was introduced in Release 13 as part of the first MCPTT specifications, and it has since been adopted for MCVideo and MCData. The change in terminology in Release 14 reflects the expansion of the concept beyond just floor control to transmission control in general. Effective priority is now a fundamental building block for prioritization in all mission-critical services, enabling reliable and responsive communication when it matters most.

What changed in its specifications

The latest release-to-release comparison of specifications that define Effective priority. Each summary describes the whole specification, not only this term.

TS 24.380Rel-17 → Rel-18

Rel-18 adds media plane multiplexing via mc_floor_ssrc fmtp and Audio SSRC in floor control. It adds an MBS subchannel control protocol. It also adds invited user identity, group call setup, and floor control SSRC/SDP fields.

Full comparison in TS 24.380 →
TS 24.581Rel-17 → Rel-18

Rel-18 added SSRC-related fields, fmtp attributes, and procedures for MCVideo transmission control and multiplexing. It also introduced the MBS subchannel control protocol with messages, fields, timers, counters, and term mappings.

Full comparison in TS 24.581 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-13 Initial

Initial definition introduced as 'The priority decision determined by the floor control server based on multiple input parameters like floor priority, participant type, type of call etc. of the current floor request and of the current participant to which floor is granted if any and the local policy.'

Wording changed to replace 'floor control server' with 'transmission control server' and 'floor priority' with 'transmission priority', reflecting the expansion to MCVideo and MCData services. The technical meaning remained the same.

Definition carried over unchanged from Rel-14, with only minor formatting differences in the specification text.

Definition carried over unchanged from Rel-15.

Definition carried over unchanged from Rel-16, with only minor formatting differences in the specification text.

Definition carried over unchanged from Rel-17.

Definition carried over unchanged from Rel-18.

Defining Specifications

3GPP specifications that define or reference Effective priority, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 24.380 vk10 MCPTT Media Plane Control Protocols Rel-20 read
TS 24.581 vj30 MCVideo Media Plane Control Rel-19 read