User's Manual
Table Of Contents
- Introduction
- The Integrator’s Task
- Installing the Modem
- Using the Modem Test Jig
- Testing
- Desense
- Application Development
- Message Routing and Migration
- Appendix A - NCL Interface
- Appendix B - Software Development Kit
- SDK Contents
- System Requirements
- SDK Software Architecture
- NCL Application Programmer’s Interface
- Implementation
- Logical Architecture
- Application Interface
- Opening a Session
- Close Session
- Send Data to a Radio Host
- Receive Data From RPM
- Get RPM Status Information
- Set Configuration ITEMS Within the RPM
- Reset RPM
- Register Event Callback Function
- Enable / Disable Events
- Get Error Description
- Register Wakeup Application
- Deregister Wakeup Application
- Switch RPM On/Off
- Send Generic NCL Command To RPM
- Get Software Version
- SCR Application Programmer’s Interface
- A
- Appendix C – Sample programs
- Appendix D - Wavenet Application Loader
- Appendix E - Numeric Conversion Chart
- Appendix F - Specifications
- Appendix H - Glossary
Message Routing and Migration ________________________________ Boomer II User Manual & Integrator’s Guide
Wavenet Technology 94 BM210012WT27
SCR Message Types
Fleet mode of communications uses three types of messages:
Commands / Host Requests (host-to-network)
EXAMPLE: Send Message #1 to LLI 87654321
Responses / Host Confirmations (network-to-host)
EXAMPLE: Message #1 to LLI 87654321 was ACKed
Events / Mobile Information (terminal-to-network-to-host)
EXAMPLE: Message received from LLI 12345678
A fourth type of message, the status message, is allowed on DataTAC
4000 and 5000 systems, but it is not supported on DataTAC 6000
systems.
Each message type must include a unique header; small differences
within each type of header exist among the systems. The charts
graphically compare the headers for each system.
Highlights of SCR Differences
The following topics explain:
Which system or systems implement a particular function.
What this function does and how it varies by system.
How to migrate an application from one system to another.
Nomenclature
When migrating applications, use the correct message type codes.
Because DataTAC systems were originally designed for unique
markets during different development periods, each shows its separate
lineage and is described using inconsistent terminology. For example,
this occurs at the beginning of the SCR header, where the code
designating the message type varies by system, as shown in the
following table.
Message Type
(direction)
DataTAC 4000
System
DataTAC 5000
System
DataTAC 6000
System
Command
(host-to-network)
IB
(inbound basic)
HR
(host request)
HR
(host request)
Response
(network-to-host)
AB
(acknowledgment basic)
HC
(host confirmation)
HC
(host confirmation)
Event
(terminal-to-host)
OB
(outbound basic)
MI
(mobile information)
MI
(mobile information)
Note: The DataTAC 4000 system designates the direction of the
command message as inbound from the host to the network and
outbound from the network to the host (opposite from current industry
terminology).