DMR Digital Mobile Radio Talkgroup Sync

Overview#

Organisations running DMR digital mobile radio networks can pull their live talkgroup topology straight into the operational picture, so dispatchers and command staff stop maintaining radio configuration in a spreadsheet that is out of date the moment it is saved.

Public safety bodies, utilities, transport operators, and security teams all depend on Digital Mobile Radio for day-to-day voice coordination, yet the structure of that network, its talkgroups, colour codes, time slots, member counts, and the management system behind them, usually lives entirely outside the operational platform. This capability reaches into your DMR network management system over an authenticated connection, reads each talkgroup's configuration, and writes it into the platform as part of the shared operational view. The result is that the radio estate appears alongside every other source of operational data, kept current with each synchronisation rather than re-keyed by hand.

Every record is scoped to your organisation, every returned talkgroup is filtered to the requesting user's clearance level, and every synchronisation writes an audit record, so the radio picture is both live and accountable.

Key Features#

• Talkgroup Topology Import: Reads each talkgroup's identifier, name, network name, colour code, time slot, member count, and status from the DMR management system and brings it into the operational platform without manual entry.

• Authenticated Management Connection: Connects to DMR network management APIs over HTTPS with a bearer token and certificate verification, so configuration is read securely from the system of record rather than transcribed.

• Tenant-Scoped Persistence: Talkgroup data is written into a relational store keyed to your organisation, with an upsert so repeated synchronisations update existing records in place rather than duplicating them.

• Clearance-Level Filtering: Returned talkgroups are filtered against the requesting user's authorisation level, so personnel only see talkgroups they are cleared to view.

• Operational Entity Emission: Each synchronised talkgroup is published as an operational network node into the shared entity graph, so the radio estate appears in the same operational picture as other data sources.

• Aggregate Network Stats: A stats view reports the total number of talkgroups and how many are active, giving command staff a quick read on radio network health.

• Full Synchronisation Audit: Every synchronisation writes an interop ingest audit record capturing who ran it, for which organisation, against which talkgroup, and at what classification, so each change is accountable.

• ETSI-Aligned Integration: The management client explicitly targets ETSI TS 102 361 DMR management interfaces, so the integration speaks to standards-conformant systems rather than a single vendor's proprietary shape.

Use Cases#

• Public Safety Dispatch: A control room running a DMR fleet imports its talkgroup structure so dispatchers see live radio groupings alongside incidents, units, and other operational feeds in one workspace.

• Utility Field Operations: A power or water utility coordinating crews over DMR keeps its talkgroup topology current in the operational view, so a supervisor knows which group reaches which work area without checking the radio console separately.

• Transport and Rail Coordination: A transport operator maps its line and depot talkgroups into the platform, giving the operations centre a single picture of voice groupings during disruption or planned works.

• Security and Guarding Operations: A security provider running guarded sites over DMR brings site and patrol talkgroups into the command view, with member counts visible at a glance.

• Clearance-Aware Visibility: Personnel at different authorisation levels view the same radio estate, with each person only shown the talkgroups appropriate to their clearance, so sensitive groupings stay restricted.

• Compliance and Oversight: An oversight or compliance function reviews the audit trail to confirm who synchronised which talkgroups and when, demonstrating that the radio picture is maintained under control rather than ad hoc.

Integration#

• GraphQL Read and Write: Customers read their radio estate through the talkgroup listing and aggregate stats fields, and bring a talkgroup into the platform through a single synchronisation operation. Plain field names are dmrTalkgroups, dmrStats, and the synchronisation mutation, all requiring an authenticated session.

• Authenticated API Connection: The platform reaches the customer's DMR network management system over HTTPS using a bearer token and the management API base URL, so the customer simply points the platform at their existing management endpoint and supplies a token.

• OAuth2 and JWT Sessions: Access to the platform is protected by OAuth2 with JWT-bearer sessions, and every read and write is authenticated and organisation-scoped, so radio data never crosses tenant boundaries.

• Normalised Operational Model: Each talkgroup is mapped to a shared operational network node entity, so radio infrastructure is described in the same normalised model as other operational sources and benefits from the same downstream views.

• Shared Entity Graph: Synchronised talkgroups land in the common entity graph that other domains also populate, so the radio estate is correlated with the wider operational picture rather than siloed.

• Audited Ingest Pipeline: Every synchronisation passes through the shared interop ingest audit path, giving the customer a consistent, reviewable record across radio and all other integrated standards.

Open Standards#

• ETSI TS 102 361 (DMR): The Digital Mobile Radio air interface and network management specification; the management integration explicitly targets ETSI TS 102 361 management APIs to read talkgroup configuration, including colour code and time slot.

• HTTP/1.1 and TLS: Talkgroup configuration is retrieved over standard HTTP with transport-layer security and certificate verification, so the management connection follows ordinary secure-web conventions.

• OAuth 2.0 Bearer Tokens (RFC 6750): The management API connection presents a bearer token in the standard Authorization header, and platform access itself is protected by OAuth2 bearer sessions.

• JSON (RFC 8259): Talkgroup detail is exchanged as JSON, the lingua franca for the management API responses the integration parses.

• JSON Web Token (RFC 7519): Platform sessions are carried as JWTs, so authentication state is portable and verifiable across the read and write paths.

• GraphQL: The read and write interface is a GraphQL schema, giving customers a typed, introspectable contract for listing talkgroups, reading stats, and synchronising a talkgroup.

Security & Compliance#

• Tenant Data Sovereignty: Every read and write is scoped to the requesting organisation, so one customer's radio estate is never visible to another.

• Clearance Enforcement: Returned talkgroups are filtered to the requesting user's classification level, and each record carries its own secrecy level, so sensitive groupings are withheld from under-cleared personnel.

• Authenticated Operations: Listing, stats, and synchronisation all require an authenticated session, with no anonymous access to radio configuration.

• Comprehensive Audit Trail: Each synchronisation records the acting user, the organisation, the talkgroup, the classification, and the timestamp, so radio network changes are fully accountable for compliance review.

Last Reviewed: 2026-05-26 Last Updated: 2026-05-26