ARS (Automatic Registration Service)
What ARS Is
Automatic Registration Service (ARS) — often also called the "Presence Notifier" function — is a MOTOTRBO feature that lets a radio report its online/offline status, and current channel/site, to a control station, gateway, or backend application. It is the mechanism that lets a PC-based application know whether a specific MOTOTRBO radio is currently reachable, without that application having to guess or poll blindly. ARS is purely a presence/reachability signal — it says a radio is on the network and where, but carries no location coordinates itself (GPS position is a separate data service layered on top; see GPS (Global Positioning System) and MOTOTRBO Data Services).
When ARS Messages Are Sent
A radio sends an ARS registration message to the network's Presence Notifier:
- When the radio is first powered on (always sent).
- When the radio changes channel.
- When the radio roams to a different repeater site (see MOTOTRBO Roaming).
- On request, when another device sends an "are you online?" query.
- Periodically thereafter, as a refresh — the server conveys a refresh-timer value to the radio in its registration acknowledgement (in units of 30-minute intervals per Motorola's ARS development specification), and the radio re-registers on that schedule rather than only at power-on.
Registration retry behavior: per the same specification, a radio's initial power-on registration attempts are spaced roughly 49–91 seconds apart, for up to 5 attempts, before the radio backs off and resets its registration attempt cycle after about 300 seconds if none of those attempts succeeded. Exact numbers should be verified against the current Motorola ARS development specification for a given firmware/CPS version rather than assumed to be permanently fixed across all MOTOTRBO generations.
What Uses ARS
The Presence Notifier's job is to accept, store, and distribute this presence information to any interested data application — commonly cited examples include telemetry applications, Location-Based Services (LBS/GPS), and text messaging applications, plus fleet/battery management tools like IMPRES Battery Fleet Management. Rather than every one of these applications independently polling every radio to check if it's online, they can all subscribe to the same ARS presence data — this is also what saves an application like Radio Management or a fleet management tool from needing to check radio availability before issuing a command.
DDMS: the Software That Implements ARS on a Wireline (MNIS) System
In an IP-networked, MNIS-based deployment, the actual "ARS Server" software role is played by the Device Discovery and Mobility Service (DDMS) — a Motorola-provided Windows service that receives ARS messages relayed by MNIS, tracks each radio's registration status, serving site, and IP address as it roams, and exposes that presence/mobility information to interested applications (dispatch, GPS/AVL, telemetry, text messaging) so they can reach the right radio even as it moves between sites. In an older, control-station-based data path (no MNIS/DDMS), the connected application typically handles ARS registration state itself rather than relying on a separate dedicated presence server — so whether a deployment needs DDMS at all depends on whether it uses the modern wireline (MNIS) architecture or a legacy control-station data path. See MOTOTRBO Data Services for how MNIS and DDMS fit into the broader data-services picture, and note the RAS (Restricted Access to System) interaction already documented there: because MNIS enters the system over the wireline rather than over the air, its traffic (including ARS relayed through DDMS) is unaffected by RAS keys, unlike a control-station-based data path.
Network Details
ARS messages are sent over UDP port 4005 by default (this is one of the "cannot be changed" default ports on the network side — see Motorola MOTOTRBO Network Ports for the full port list). ARS is used by both portables and mobiles on an IP-networked MOTOTRBO system — see Motorola MOTOTRBO Portable Radios for the handheld radio families this applies to. At the protocol level, ARS messages are structured as PDUs (protocol data units) with a message-size field, header byte(s) carrying flags like acknowledgement-required and PDU type, and a type-specific payload — exact bit-level field layouts are Motorola specification detail beyond the scope of this page and should be sourced from the current Motorola ARS development specification if wire-level implementation detail is ever needed.
Common Misunderstandings
- "ARS tells you where the radio is (GPS-wise)" — no; ARS is presence/reachability and serving-site information, not GPS coordinates. GPS location is a separate data service that typically depends on ARS working (an application generally needs to know a radio is registered/reachable before it can usefully request or expect location updates from it), but the two are not the same feature.
Related Pages
- Motorola MOTOTRBO Network Ports
- Motorola MOTOTRBO Portable Radios
- MOTOTRBO Data Services
- MOTOTRBO Roaming
- GPS (Global Positioning System)
- Control Stations
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.