Push-to-Talk over Cellular (PoC)
What It Is
PoC delivers a walkie-talkie-style push-to-talk experience over LTE/5G cellular networks (or Wi-Fi) rather than over dedicated LMR frequencies. A user presses talk, audio is captured and compressed, sent as a data packet to a PoC server, and routed to every member of the selected talkgroup — typically arriving within a fraction of a second, though generally with somewhat higher latency than a conventional LMR channel's near-instant RF channel access, since a PoC transmission has to traverse the cellular data network and a server-based call-control path rather than simply keying an RF channel directly.
Floor Control: How PoC Manages Who's Talking
Because PoC has no physical RF channel to contend for, it needs its own mechanism for deciding who currently has permission to talk in a group call — this is called floor control. A PoC server arbitrates "floor" requests from group members, granting the floor to one user at a time and queuing or rejecting others who try to key up while someone else already holds it — conceptually similar to what channel access / doubling prevention does on conventional RF, but implemented as an explicit server-mediated protocol exchange rather than physical RF contention.
Standards Landscape: PoC vs. MCPTT
Not all "push-to-talk over cellular" implementations are built to the same standard or offer the same guarantees:
- OMA PoC — the original Open Mobile Alliance standard defining basic push-to-talk-over-cellular service; many commercial/consumer-grade PoC platforms trace back to this foundation.
- 3GPP MCPTT (Mission Critical Push-to-Talk) — a more rigorous standard built specifically for public-safety/mission-critical use, layering on features basic PoC generally lacks: priority and pre-emption (so a higher-priority user/call can take the floor from a lower-priority one), emergency-call workflows, and service guarantees beyond best-effort delivery. Vendors moved through an intermediate "PCPS" (Push to Communicate for Public Safety) specification as a stepping stone from basic OMA PoC toward full 3GPP MCPTT compliance.
- Vendor-proprietary PoC apps — many commercial PoC products (including some carrier-branded offerings) implement their own feature sets on top of, or independent from, these standards, with capabilities that vary by platform.
A real, established example of this landscape: Kodiak (now part of Motorola Solutions) is a long-running PoC platform used by numerous mobile network operators, illustrating how a single vendor's PoC technology can be white-labeled/resold across multiple carriers. The key practical point for anyone evaluating PoC: a product being "PoC" does not automatically mean it meets MCPTT-grade priority, pre-emption, or emergency-call guarantees — those specifically require 3GPP MCPTT compliance (or an equivalent purpose-built implementation), not just generic PoC functionality.
PoC vs. Traditional LMR
- Infrastructure: PoC needs no repeaters, towers, coax, or FCC frequency licensing — it rides on infrastructure someone else (a cellular carrier) already built and maintains. Traditional LMR requires owning or leasing that physical infrastructure.
- Coverage: PoC coverage is essentially "wherever cellular/Wi-Fi reaches" — which can mean nationwide or international reach at low incremental cost, but also means coverage is entirely dependent on commercial network availability, unlike an independent LMR system that keeps working even if commercial cellular is down or congested.
- Reliability model: LMR is engineered for infrastructure-independent, mission-critical reliability (see Failsoft Mode for how a trunked system degrades gracefully rather than going silent) — a guarantee generic PoC generally cannot make, since it depends entirely on a third-party cellular network's availability and congestion state; even MCPTT-grade PoC's priority/pre-emption features only manage congestion on the underlying cellular network, they don't eliminate dependency on that network existing and functioning.
Common Misunderstandings
- "PoC is basically the same as a regular phone call or one-to-one VoIP" — no; PoC specifically preserves LMR-style group/one-to-many broadcast semantics (one person's transmission reaches an entire talkgroup at once) and half-duplex, floor-controlled turn-taking, rather than a full-duplex, one-to-one call.
- "All PoC apps are mission-critical-grade" — as covered above, only implementations actually built to 3GPP MCPTT (or equivalent) offer priority/pre-emption and emergency-call guarantees; a consumer/commercial PoC app is generally best-effort on the underlying public network with no such guarantees.
- "PoC and cellular direct-to-phone group messaging apps (like a generic group chat with voice notes) are the same thing" — a genuine PoC product implements real-time floor control and low-latency group voice delivery purpose-built for PTT semantics; it's a different technical animal from asynchronous voice messaging even though both might superficially resemble "talk into a phone, others hear it."
Troubleshooting Implications
- PoC quality/reliability tracks the user's cellular signal and data throughput at their specific location, not just "is the app working" — a user in a cellular dead zone or on a heavily congested cell sector will have PoC problems that have nothing to do with the PoC platform itself, analogous to (but a fundamentally different failure mode from) an LMR user out of RF coverage of any repeater.
- Floor-control contention/rejection (a user presses PTT and is denied the floor or queued) is the PoC-world equivalent of a busy channel — expected, normal behavior under load, not a fault, though excessive floor-denial complaints on a given deployment may indicate the talkgroup is oversubscribed for its use case.
Related Pages
References
See also: CTI product documentation
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.