🗊Презентация Motorola solutions learning. Network application interface (NAI). Radio management (RM)

MOTOTRBOTM MOTOTRBOTM

SECTIONS 1. Introduction: High Level Overview / Demo Network Application Interface (NAI) Radio Management (RM) Technical: Network Application Interface (NAI) Radio Management (RM)

INTRODUCTION

NAI & RM ON THE LCP DEMO SYSTEM

NETWORK APPLICATION INTERFACE (NAI)

FEATURE SUMMARY

FEATURE SUMMARY Requires a software upgrade of repeaters: Repeaters must have 32MB of flash memory Compatible with current and next generation MOTOTRBO radios Requires feature activation in the repeater: HKVN4211A DR 3000 NAI for Voice/CSBK License Key HKVN4212A DR 3000 NAI for Data License Key HKVN4214A MTR3000 NAI for Voice/CSBK License Key HKVN4215A MTR3000 NAI for Data License Key ADK documentation for the following interfaces is maintained and made available via the Application Developers Program: Network Application Interface for Voice/CSBK* MNIS interface (to access the Network Application Interface for Data) The MNIS / DDMS software is released via the MOTOTRBO MOL website (* to selected 3rd party application developers)

NETWORK APPLICATION INTERFACE – VOICE/CSBK 3rd party Wireline Voice Consoles utilizing the Network Application Interface can support following types of calls: Group Call Private Call or Confirmed Private Call All Call Voice Privacy (Basic and Enhanced) CSBK calls – Radio Check , Call Alert, Remote Monitor, Radio Inhibit/Inhibit, Voice Console Enable/Disable The Interface allows 3rd party Wireline Voice Consoles to interrupt or impolitely takeover on-going Voice calls. Where a Wireline Voice Console is required to interface to a given system site then all Voice Capable repeaters at that site must have their “Network Application Interface for Voice/CSBK” feature enabled using the CPS. Where a Wireline Voice Console is not required to interface to a given system site, then repeaters at that site do not need to have this feature enabled. NOTES: Voice Capable repeaters are all repeaters except for data revert repeaters and repeaters where both slots are GPS revert slots. A Wireline Voice Console counts as 1 site, so the total number of IPSC/LCP sites plus Wireline Voice Consoles should not exceed 15. Support for Telephone calls (similar to Digital Telephone Patch) via this interface is a future roadmap feature.

NETWORK APPLICATION INTERFACE – VOICE/CSBK A Wireline Voice Console is required to interface directly to the radio system. Motorola Solutions does not provide middleware for Wireline Voice Consoles. A Wireline Voice Console is also required to support AMBE vocoding. The above requirements add complexity to the Wireline Voice Console, so to ensure high quality fully supported implementations, Motorola provides support to selected 3rd party application developers as follows: By making available the “Network Application Interface for Voice/CSBK”. By providing the necessary technical training and support.

NETWORK APPLICATION INTERFACE – DATA The Network Application Interface for Data is an internal interface between the MNIS and the Repeaters. The MNIS provides 3rd party vendors with an ADK for accessing the Network Application Interface for Data (i.e. 3rd party applications do not access the interface directly). The interface between a data application and MNIS is very similar to the interface between a data application and control station for the case where the data application uses the MCDD and MOTOTRBO Presence Notifier.

MNIS OVERVIEW The MNIS is supported by Windows XP, Windows 7, Windows Server 2003 & 2008 The MNIS supports the following MOTOTRBO data features: Layer 2 confirmed and unconfirmed data message delivery Individual and Group data messages Basic and Enhanced Privacy Data message IP/UDP header compression Data Precedence and Data over Voice Interrupt access priority Compared to Control stations, the advantages of using MNIS for data are: The deployment is simpler – no extra hardware The data application does not need to be within the RF coverage area of the system Data revert channels can be configured to be local – Increases GPS capacity MNIS connectivity with the system can be monitored via RDAC Customers not wishing to use the Network Application Interface for Data feature shall still have the option of using Control Stations.

MNIS OVERVIEW The MNIS connects with the repeater system using the Link Establishment procedure of the repeater system. This requires the MNIS to be configured with the Master repeater’s IP address and UDP port number. Upon connection with the Master repeater, the MNIS discovers the IP addresses and port numbers of all the repeaters in the system then establishes links with all the repeaters in the system. Upon connection with the repeaters, the MNIS uses the repeater’s Network Application Interface and its underlying services to support data transmit and receive through the repeaters. The Link Establishment and Network Application Interface procedures are transparent to the data application. Where a MNIS is required to interface to a given system site then all repeaters at that site must have their “Network Application Interface for Data” feature enabled using the CPS. Where MINS is not required to interface to a given system site, then repeaters at that site do not need to have this feature enabled. The MNIS Configuration GUI allows configuration of system link establishment parameters such as Master IP Address, Port, Peer ID, etc.

MNIS APPLICATION ID The MNIS has an identifier, called the MNIS Application ID. The ID is configured in the MNIS using the MNIS configuration GUI. The ID is used by the MNIS to receive and transmit on the radio network. Whenever a radio needs to communicate with the data application (or vice versa) the MNIS Application ID is used. For example, the ARS and TMS Radio ID fields in a radio need to be configured with the MNIS Application ID such that data messages from a radio to the ARS or TMS applications contain the MNIS Application ID as the destination address. Likewise, data messages from the ARS or TMS applications to a radio need to have the MNIS Application ID as the source address. The MNIS application ID is akin to the Radio ID of a control station. Fielded radios should not be configured with a Radio ID that matches the MNIS Application ID.

DDMS OVERVIEW The DDMS is supported by Windows XP, Windows 7, Windows Server 2003 & 2008. The DDMS replaces the legacy Presence Notifier (PN) application. The DDMS is backward compatible with the Presence Notifier such that existing applications that interface with the Presence Notifier do not require any changes to receive presence notifications from the DDMS. The DDMS can be deployed with a Control Station or the MNIS. When deployed with a Control Station, the DDMS supports only radio presence notifications. When deployed with the MNIS, the DDMS supports both presence notifications and mobility notifications. A presence notification indicates a radio’s presence or absence in the radio system. A mobility notification indicates the channel/site from which a radio transmits its ARS Device Registration message. When transmitting messages to a radio from a data application, the MNIS uses a radio’s mobility information (supplied by the DDMS) to determine the channel/site to use. Besides the MNIS, other applications can also receive a radio’s mobility information from the DDMS.

DDMS WATCHER INTERFACE The DDMS maintains both the radio presence and mobility information. The DMMS provides a Watcher interface to enable applications to obtain radios’ presence and mobility information and notifications of changes in radios’ presence and mobility information.  Presence Information: The MNIS forwards a radio’s ARS message to the DDMS which updates the radios presence information. The DDMS notifies data applications that have subscribed for presence through the Watcher interface. Mobility Information: The MNIS forwards a radio’s ARS message to the DDMS which updates the radios mobility information. The DDMS notifies data applications (including the MNIS) that have subscribed for mobility through the Watcher interface.

RADIO MANAGEMENT (RM)

RADIO MANAGEMENT OVERVIEW

RADIO MANAGEMENT (RM) SOFTWARE LICENSES The Radio Management (RM) Server can store and manage up to 5,000 radio codeplug archives Initial installation contains licenses for 10 radio archives by default To add additional radio archives to RM for Wired or OTAP management and programming – additional licenses have to be purchased

IMPORTING RM LICENSES

TECHNICAL

NETWORK APPLICATION INTERFACE (NAI)

DATA FLOW

SYSTEM CONFIGURATIONS

MULTIPLE CONVENTIONAL SYSTEMS TOPOLOGY

(LINKED) CAPACITY PLUS SYSTEM TOPOLOGY

SYSTEM TOPOLOGY WITH MULTIPLE MNIS

SYSTEM TOPOLOGY WITH MNIS AND CONTROL STATIONS

DATA APPLICATIONS ON DIFFERENT PC

OTAP WITH MNIS DEPLOYMENT

DEPLOYMENT WITH OTHER APPS MNIS, DDMS, RDAC, Remote Repeater Programming and Radio Management can be deployed on the same PC May require hair pinning router for certain deployments MNIS and Wireline Voice Console can be deployed on the same PC Assumes there are no restrictions imposed by Wireline Voice Console May require hair pinning router for certain deployments MNIS and Control Station (for voice dispatch) can be deployed on the same PC Assumes the Control Station is not used for data Only one MNIS can be deployed per PC Only one DDMS can be deployed per PC

RADIO CONFIGURATION

REPEATER CONFIGURATION

MNIS CONFIGURATION - GENERAL

MNIS CONFIGURATION - SECURITY

MNIS CONFIGURATION – GROUP LIST

MNIS CONFIGURATION - CONVENTIONAL SYSTEM

MNIS CONFIGURATION - MULTIPLE CONVENTIONAL SYSTEMS

MNIS CONFIGURATION - CAPACITY PLUS

MNIS CONFIGURATION - LINKED CAPACITY PLUS

MNIS CONFIGURATION - LINKED CAPACITY PLUS

MNIS CONTROLS

DDMS CONFIGURATION

RADIO MANAGEMENT (RM)

RADIO MANAGEMENT OVERVIEW

RADIO MANAGEMENT CONFIGURATION EXAMPLE

CONTROL STATION / RADIO CONFIGURATION EXAMPLE

RM CLIENT SCREEN

CONFIGURATION MANAGEMENT CONSIDERATIONS If the radio user is allowed to make changes via the radio front panel, these updates will not be retained after an OTAP or Wired Write (delivery). The configuration in the RM Server will overwrite what is in the radio when delivered Similar to current CPS - the OTAP user must Read (retrieve) the radios over the air first, make individual updates to each, and then Write (deliver) the new configurations in order to retain the previous changes made by the radio user. If using a Template configuration to program a group of radios, there is no way to retain any individual changes that the radio users had made All radios will be updated to match what is in the Template, with the exception of the radio identity information. Programming radios with an unmanaged (not connected to RM Server) wired CPS will make the radio to be out of sync with the RM Server. This will cause the next over the air operation to take longer since the entire configuration must be Read (retrieved) or Written (delivered)

DELIVER / WRITE MODIFIED RADIO CONFIGURATIONS RM allows scheduling of multiple radio configurations to be delivered over the air unattended. RM will start the delivery at a scheduled time and continue until all selected radios are either Complete, Errored, or Cancelled. Voice can coexist with the OTAP data, although system performance (voice access time, and data throughput) may be degraded slightly. It is recommended that OTAP operations are scheduled during time of low radio system activity After the delivery is successful, the radio status will be “Switchover Required”

APPLY (SWITCH OVER) OF DELIVERED RADIO CONFIGURATIONS Delivery with Switchover - radio will apply the changes after delivery Use when changing non-critical parameters: address book entries or button configurations Switchover timer is set to zero by default in which case the switchover occurs immediately upon receiving the switchover message. If the switchover timer is set greater than zero, the radio user will receive a prompt to Accept or Delay the Switchover Accept- immediately reset and apply the changes Delay, or no selection, the radio will wait until the switchover timer expires to reset and apply the changes Delivery without Switchover - radio will not apply the changes after delivery. Switchover job must scheduled separately Use when changing critical communication parameters: TX or RX frequencies, color codes, privacy keys, etc.

CONFIGURATION - GENERAL Unless using NAI, the Device Programmer and Control Stations must be within RF coverage of target units (note: the Server does not). Continuous direct network connection is required between the Server and Device Programmers(VPN or Private Network) . If a continuous network connection is not possible, a Remote Client Configuration with Multiple Servers is required. If a PN is used, the Device Programmer where the target radio is registered will service jobs for that radio. If a PN is not uses the Device Programmer can be configured to service a specified set of radios (defined by a group within the Server).

UNIQUE RADIO ID When using a centralized RM Server to communicate to multiple systems with remote Device Programmers, then all radios across these systems must contain unique radio IDs. If this is not achievable, then: A separate CPS Server must be used for each system or Radios must be combined into Groups in the RM Server and each remote Device Programmer set to service a specific Group NOTE: The requirement that within the SAME System there are no duplicate Radio IDs remains, however for duplicate Radio ID’s across different Systems, the Group assignment can be used.

RM DEVICE PROGRAMMER - AUTOMATICALLY PROCESS JOBS (WIRED MODE) RM Device Programmer in Wired mode: Check “Automatically Process Jobs” to execute Read/Write jobs immediately Otherwise Manually clicking the Play button will be required for every new Read/Write

MANAGE TEMPLATES Radio View Radio Button Import New Radios Edit Radio Alias / ID / CIA / IP Address Select Groups / Templates Edit Templates (Voice Announce, Channels, Talkgroups, Privacy, RAS, etc) Schedule Jobs

MANAGE VOICE ANNOUNCEMENTS To view and manage VA (Voice Announcement) files in RM Server go to: Actions > Manage > Voice Announcements Import VA files from RM Client to RM Server (local or remote) Edit Templates to select required VA files Schedule Jobs to Write to radios

MANAGE LANGUAGE PACKS To view and manage Language Pack files in RM Server go to: Actions > Manage > Language Packs Import Language Pack files from RM Client to RM Server (local or remote) From Template View, select required Language Packs for Templates Schedule Jobs to Write to required radios

MANAGE KEYS To view and manage Secure keys in RM Server go to one of the following: Actions > Manage > OTAP Keys Actions > Manage > Privacy Keys (Enhanced Privacy) Actions > Manage > RAS Keys Key repository shows all keys available for all radios in RM Server

MANAGE FIRMWARE To view and manage Firmware Packages in RM Server go to: Actions > Manage > Firmware Import Firmware Packages from RM Client to RM Server (local or remote) From Template View, select required firmware versions for Templates Schedule Jobs to Write to required radios

MULTI-RADIO PROGRAMMING (WIN 7) Automatic sequential programming of up to 16 radios simultaneously connected via USB Each radio MUST have a unique Radio ID and a unique Radio IP (in a unique subnet) RM Device Programmer MUST run on a Windows 7 machine Preparation (from Radio View): For each new radio, click Actions > New Radio and enter serial number Select all new radios, then right click Schedule Job > Read (‘Wired’ mode) and connect each radio in turn to be read Select all new radios, then right click Select Template and select a single common template Assign a unique Radio ID and a unique Radio IP (in a unique subnet) to each new radio Select all new radios, then right click Schedule Job > Write (‘Wired’ mode) and connect each radio in turn to be written Once they have been prepared, up to 16 radios (assigned to a common template) can be connected simultaneously via USB and automatically ‘programmed in sequence.