Radio Management Overview

Two-Way Radio Concepts and Electronics Fundamentals · Last updated · About 4 min read

Purpose

Motorola uses several products with overlapping terms such as CPS, Radio Management, OTAP, POP25, and RadioCentral. This page explains their roles and the boundaries between them.

The Basic Progression

A radio-programming environment generally progresses through these levels:

  1. CPS and a cable — one technician edits and writes one radio at a time.
  2. Centralized Radio Management — a server database stores radio records, templates, codeplug history, and jobs for a fleet.
  3. Distributed programming — Device Programmer computers are placed near users, at remote sites, or on a Wi-Fi network.
  4. Over-the-air programming — a radio receives configuration through an LMR data path, Wi-Fi, or broadband.
  5. Cloud fleet management — RadioCentral stores fleet data and programming jobs in a Motorola-operated cloud service.

These levels can coexist. An organization may use Radio Management for most work and retain CPS with USB as a recovery method.

Product Map

Product or term Ecosystem Primary purpose
MOTOTRBO CPS 2.0 MOTOTRBO/DMR Create, read, edit, clone, and write MOTOTRBO radio configurations
MOTOTRBO Radio Management 2.0 MOTOTRBO/DMR Central database, templates, fleet records, jobs, licenses, and distributed programming
MOTOTRBO OTAP MOTOTRBO/DMR Deliver supported programming changes through the MOTOTRBO RF system
MOTOTRBO Wi-Fi programming MOTOTRBO/DMR Deliver codeplug, firmware, resource, or feature updates over an IP network when supported
ASTRO 25 CPS APX/P25 Create and maintain APX codeplugs and device configuration
APX Radio Management APX/P25 Centralized APX fleet database, templates, jobs, and Device Programmers
POP25 APX/P25 Programming over an ASTRO 25 conventional or trunked data path
RadioCentral Public Safety APX/P25 Motorola-hosted cloud programming and lifecycle management for supported APX radios
RadioCentral Commercial MOTOTRBO/DMR Motorola-hosted cloud management for supported MOTOTRBO cloud-capable devices
OTAR Primarily secure P25 systems Remotely change encryption keys; not codeplug programming

Common Radio-Management Objects

Radio Record

A database record representing a particular radio. It commonly includes the serial number, model, firmware, codeplug version, assigned template, radio ID, alias, job history, and connection information.

Template

A reusable configuration applied to multiple radios. A template contains shared values such as systems, channels, talkgroups, button assignments, scan lists, security settings, and user-interface behavior.

Radio-specific values should remain individual where required. Examples include a unique radio ID, IP address, serial-number-bound entitlement, or user alias.

Codeplug

The radio's programmable configuration. A codeplug is not the same as firmware. It defines how the radio operates and which systems, channels, contacts, menus, keys, buttons, and options it uses.

Job

A requested action placed into a queue. Examples include:

  • Read the current radio configuration
  • Write pending configuration changes
  • Apply a template change
  • Clone a configuration
  • Update firmware or a software image
  • Install resource files
  • Activate a licensed feature
  • Reset or recover a device, where supported

A job can be prepared long before the radio becomes reachable. A pending job therefore does not automatically indicate a fault.

Job Processor

A service that prepares radio data for a programming job. It validates and transforms template and radio information into a format the Device Programmer can deliver.

Device Programmer

The component that communicates with the physical radio. Depending on the product and deployment, it may use USB, Wi-Fi, an LMR data path, or a cloud-connected station.

Generic Job Flow

  1. A programmer edits a template or radio record.
  2. Radio Management calculates which radios are affected.
  3. A read, write, update, or activation job is scheduled.
  4. A Job Processor validates and prepares the job.
  5. A Device Programmer or cloud service waits for the radio through the selected transport.
  6. The radio receives the data.
  7. The radio validates and applies the update, sometimes after a reboot or user acceptance.
  8. The radio reconnects or reports status.
  9. The server records completion, failure, or a retryable state.

Read, Write, Provision, and Update

Read

Retrieves the radio's current configuration and identity. A read is often necessary to establish a trustworthy baseline or bring a manually changed radio back into synchronization with the database.

Write

Sends configuration changes to the radio. Modern products may use differential writes so that only changed parameters are transferred.

Provision

A broader onboarding process that may include identity, certificates, region assignment, codeplug, feature entitlements, software, and security information. RadioCentral commonly uses the term provisioning.

Firmware or Software Update

Replaces executable radio software. Firmware is larger and riskier than a codeplug change and may require a supported battery level, additional storage, a reboot, a particular transport, or a separately licensed service.

Feature Activation

Applies a purchased entitlement or feature license. This may require an Entitlement ID, a Motorola licensing service, a cloud connection, or a read of the radio's current license state.

What Radio Management Does Not Guarantee

Radio Management does not automatically guarantee that:

  • Every radio model supports every transport
  • RF OTAP can carry firmware
  • A Wi-Fi-capable radio is already configured for the correct SSID and security type
  • A radio in the database is currently reachable
  • All settings can be changed over the air
  • A job can interrupt an emergency or voice call
  • A newer server can communicate with an older Device Programmer
  • A RadioCentral subscription includes every feature or service tier

Always confirm the radio model, firmware, system release, license, and selected programming path.

Sources and Further Reading

References

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.