TRBO_Application Partner_BR_Low Res TRBO Application Partner BR Low
TRBO_ApplicationPartner_BR_LowRes TRBO_ApplicationPartner_BR_LowRes
User Manual: TRBO_ApplicationPartner_BR_LowRes
Open the PDF directly: View PDF 
.
Page Count: 16
| Download | |
| Open PDF In Browser | View PDF |
MOTOTRBO™ Application Development Kit Overview Table of Contents Section 1 1.0 What is MOTOTRBO? 3 Section 2 2.0 Extending the MOTOTRBO Product 5 2.1 MOTOTRBO Option Board ADK 6 2.2 MOTOTRBO Telemetry ADK 7 2.3 MOTOTRBO Location Data ADK 8 2.4 MOTOTRBO Text Messaging ADK 9 2.5 Presence Notifier 10 2.6 Data Services 11 Section 3 3.0 Professional Radio Application Developer Programme 12 Section 4 4.0 Service & Support for Application Development 13 Section 5 5.0 Further Information and Contact 14 Section 6 6.0 Appendix: ADK Document Map 15 MOTOTRBO - Application Development Kit Overview Section 1 1.0 What is MOTOTRBO? MOTOTRBO is Motorola’s next generation of Professional Radio that is capable of analogue and digital two-way communications. In addition to the standard features available with Motorola’s other analogue-based products, MOTOTRBO brings digital enhancement to the voice quality as well as an expanded feature set to this product tier. While operating in digital mode, MOTOTRBO uses a two-slot Time Division Multiple Access (TDMA) air interface to transmit and receive digitised voice and air protocol control messages simultaneously. This leads to a higher quality of service (QoS) and a richer user experience with the product. With the digital mode operation of the MOTOTRBO system, customers can expect end-to-end operation of advanced features and integrated applications such as text messaging, Location-Based Services (LBS), and telemetry as well as customised capabilities provided through an internal option board. MOTOTRBO - Application Development Kit Overview Section 1 Figure 1 - MOTOTRBO System Example Sensors & Controls GPS GPIO MOTOTRBO Mobile MOTOTRBO Portable MOTOTRBO Option Board Interface MOTOTRBO Mobile MOTOTRBO Mobile Telemetry Location Data Location Data Option Board Signaling MOTOTRBO Repeater Telemetry Location Data Text Messaging MOTOTRBO Mobile MOTOTRBO Portable Text Messaging UDP/IP over USB MOTOTRBO Portable MOTOTRBO Option Board Interface Text Messaging Presence Notifier MOTOTRBO Mobile UDP/IP over USB Telemetry Application Text Messaging IP Network Text Messaging Location-Based Services MOTOTRBO - Application Development Kit Overview Section 2 2.0 Extending the MOTOTRBO Product Aside from the functionality embedded in the radio, the MOTOTRBO subscriber’s capabilities can be extended through defined application programming interfaces for 3rd party developer use. The MOTOTRBO Application Development Kits (ADKs) offer an opportunity to customise a solution specifically to a customer’s need. specific domain knowledge required to successfully implement a 3rd party application for the MOTOTRBO product. There are four primary ADKs for developer use: The MOTOTRBO ADKs are comprised of protocol specifications and development guidelines that are intended as technical references for the external vendor. These ADKs not only include software specifications, but also include electrical and mechanical specifications, where applicable. Each interface’s set of technical references also detail the • • • • MOTOTRBO Option Board ADK MOTOTRBO Telemetry ADK MOTOTRBO Location Data ADK MOTOTRBO Text Messaging ADK Please refer to the individual ADK sections for more information on the interface. Refer also to the Appendix: ADK Document Map for more information on document components for each ADK. MOTOTRBO - Application Development Kit Overview Section 2 2.1 MOTOTRBO Option Board ADK The MOTOTRBO portable and mobile radios provide a physical and logical interface to accommodate an internal option board with an onboard processor and embedded logic. This option board interface is the means by which an option board, executing its own software application, interoperates with the main board firmware to create the custom end-user solution. main board so that the option board can send and receive data during its proper timeslot. The option board interface of the MOTOTRBO product uses the Extended Command and Management Protocol (XCMP) to establish a communication mechanism between the option board device and the radio. Through this protocol, the option board can request notification of ergonomic events such as button presses or signals (i.e. carrier detect, PL detect, etc.) in order to take further action to process a customised feature. The option board can also request the radio to execute certain actions such as display text or route audio in order to present a specific ergonomic experience to the user. In addition, the option board can activate or de-activate specific functionality, such as scan, the menu system, or an over-the-air data session, to execute the behavior of a new feature. The option board interface uses a Synchronous Serial Interface (SSI) to transport the XCMP control and data messages within XCMP Network Layer (XNL) packets to and from the radio and its available services. The SSI is comprised of four logic lines: clock, sync, data in, and data out. The option board uses the SSI to transport logical and audio data to and from the radio. There are no dedicated analogue audio lines on the option board interface. Whether the MOTOTRBO radio is operating in analogue or digital mode, all audio is encoded into digital format and transported on the SSI bus. The SSI bus is a multi-slotted Time Division Multiplexed (TDM) communication channel that is shared with other chips and devices contained within or attached to the Radio Host. A separate Option Board Sync (OBSync) logic signal is provided by the Through the MOTOTRBO™ Option Board interface, custom applications can be created to achieve a desired user operation while the MOTOTRBO™ radio is operating in either analog or digital mode. The extended functionality provided by an option board can be a basic ergonomic feature, such as a “Man-Down” lone worker application, or an advanced signal processing feature, such as a custom signaling system format. The MOTOTRBO™ Option Board interface also has the extended capability to communicate with other devices within the radio system. This includes Data Applications which are integrated into the Radio Network through a PC environment. These Data Applications communicate using User Datagram Protocol over Internet Protocol (UDP/IP) sent over the Common Air Interface (CAI) of the MOTOTRBO™ Radio. Interoperation with Data Applications is only available while MOTOTRBO™ is operating in digital mode. For more information about the MOTOTRBO™ Option Board interface, please see the following references: • MOTOTRBO™ Option Board ADK Guide • MOTOTRBO™ Option Board PROIS Crossreference • MOTOTRBO™ XCMP / XNL Development Guide • MOTOTRBO™ XCMP / XNL Development Specification For more information about the other interfaces, please refer to the appropriate sections contained within this overview. MOTOTRBO Radio XCMP XCMP XNL UDP Radio Network UDP IP IP CAI Main Board (Radio Host) SSI XNL SSI SSI Bus Slot Slot Slot Slot 1 2 3 4 ... Slot N Option Board Sync MOTOTRBO Option Board Interface Figure 2 - MOTOTRBO Option Board Interface Architecture MOTOTRBO - Application Development Kit Overview Option Board (3rd Party Device) Section 2 2.2 MOTOTRBO Telemetry ADK The MOTOTRBO product can be customised for telemetry operation by developing a PC-based application using the MOTOTRBO Telemetry interface. A Telemetry Services PC application interoperates with a MOTOTRBO radio via direct USB connection and can monitor or control the general purpose inputs and outputs (GPIOs) of a radio. Telemetry operation is available while the MOTOTRBO product is operating in digital mode only. For more information about the MOTOTRBO Telemetry interface, please see the following references: • MOTOTRBO Telemetry ADK Guide • MOTOTRBO Telemetry Protocol Specification • MOTOTRBO Data Services Overview Telemetry operation is available on 3 GPIOs for the MOTOTRBO portable and on 5 GPIOs for the MOTOTRBO mobile. The status of telemetry events can be queried for inputs or outputs. The state transition of telemetry inputs can also be announced and shown on a display-capable MOTOTRBO radio. Routing of telemetry information in the radio network is accomplished using UDP/IP. The destination of the telemetry data can be either to a Telemetry Services PC application or to another device such as an option board. The Telemetry interface can also broadcast telemetry status overthe-air to specific MOTOTRBO subscribers within the radio network. For more information about the other interfaces, please refer to the appropriate sections contained within this overview. Figure 3 – MOTOTRBO Telemetry Interface Architecture Telemetry Services Application TP UDP IP RNDIS USB MOTOTRBO Radio TP UDP The Telemetry interface enables remote detection or activation of events through the MOTOTRBO system. An example of a telemetry-based solution is an irrigation system that is automatically activated based on average moisture level. IP CAI Radio Network GPIO TP UDP IP CAI MOTOTRBO Radio GPIO MOTOTRBO - Application Development Kit Overview Sensors & Controls Section 2 2.3 MOTOTRBO Location Data ADK The MOTOTRBO product features optional embedded GPS capability for Location-Based Services (LBS) with the portable and mobile radio. The location function provides latitude, longitude, altitude, velocity, and heading data for the radio. A LBS PC application can also interoperate with the MOTOTRBO product to record a timestamp of reported location data for any specified radio. The Location Data interface is available while the MOTOTRBO product is operating in digital mode only. The Location Data interface facilitates asset tracking via location-based services. For example, a LBS application can provide an Automated Vehicle Location (AVL) capability to track the position of delivery trucks in the coverage area of the MOTOTRBO system. For more information about the MOTOTRBO Location Data interface, please see the following references: • MOTOTRBO Location Data ADK Guide • MOTOTRBO Location Request and Response Protocol (LRRP) Specification • Motorola Binary XML Encoding Specification • MOTOTRBO Data Services Overview Location status can be configured for periodic or on-request reporting during normal operation. During emergency operation, the MOTOTRBO radio can be configured for more frequent reporting of location data. For more information about the other interfaces, Architecture please refer to the appropriate sections contained Messages for requests and responses for location within this overview. data are handled through the Location Request and Response Protocol (LRRP). LRRP is a location data reporting protocol that is optimised for use within the MOTOTRBO Radio Network. LRRP control and data messages are sent via the Radio Network within UDP/IP packets that are transported over the Common Air Interface (CAI). The LRRP messages are processed directly by the embedded GPS components inside the MOTOTRBO radio as well as within the LBS PC application. The Location Radio Data interface can also interoperate with the Network MOTOTRBO Option Board interface to route location data directly to a custom option board device. Figure 4 – MOTOTRBO Location Data Interface Architecture LRRP UDP IP CAI LRRP UDP IP CAI LRRP LBS Application LRRP UDP IP RNDIS USB MOTOTRBO Radio GPS Component MOTOTRBO Radio MOTOTRBO - Application Development Kit Overview Section 2 2.4 MOTOTRBO Text Messaging ADK The MOTOTRBO product includes embedded text messaging capability for one-to-one or one-tomany device destinations. This capability can be extended to interoperate with a PC-based application to provide enhanced Text Messaging Services (TMS) using the Text Messaging interface of the MOTOTRBO radio. The TMS feature is available while the MOTOTRBO product is operating in digital mode only. A text message containing up to 140 characters can be sent between a subscriber, talkgroup, subscriber with an attached PC (via USB), dispatcher client, or external network (i.e. the Internet). These messages can be pre-canned or composed along with a received message inbox for later viewing. model implementation of this interface would be a PC-based dispatch messaging center. The messaging center contains a user interface for typing text messages to be sent to an individual radio or a group of radios as well as an output screen for displaying received messages. For more information about the MOTOTRBO Text Messaging Services Interface, please see the following references: • MOTOTRBO Text Messaging ADK Guide • MOTOTRBO Text Messaging Protocol Specification • MOTOTRBO Data Services Overview Interface Architecture Text messages are routed within the Radio Network as UDP/IP packets transported over the MOTOTRBO Common Air Interface (CAI). The destination of text messages is determined by the target IP address and port number. This enables the routing of text messages to two logically different devices that are physically connected together (e.g. PC attached to MOTOTRBO radio via USB). In addition, the Text Message interface interoperates with the MOTOTRBO Option Board interface to route text messages directly to the option board for processing. For more information about the other interfaces, please refer to the appropriate sections contained within this overview. Radio Network The Text Messaging Services interface provides alternate methods for sending and receiving text messages within the MOTOTRBO system. A TMP Figure 5 – MOTOTRBO Text Messaging UDP Services Interface Architecture IP CAI UDP IP CAI TMP TMS Application TMP UDP IP RNDIS USB TMP TMS Component TMS Component MOTOTRBO Radio MOTOTRBO Radio MOTOTRBO - Application Development Kit Overview Section 2 2.5 Presence Notifier The Presence Notifier is used to notify a PC-based backend application, such as for telemetry, LBS, or text messaging, that a MOTOTRBO radio has powered on or off and has registered or deregistered with the system. This application allows for efficient bandwidth utilisation of the Radio Network – messaging only occurs between the backend application and those MOTOTRBO subscribers that are available and that the application is interested in. The Presence Notifier component is for use in digital mode only. The MOTOTRBO radio contains an Automatic Registration Service (ARS) that sends a registration message to the Presence Notifier within the Radio Network. When the MOTOTRBO radio is powered down, a de-registration message is sent. The registration and de-registration messages are sent as UDP/IP packets that are transported over the CAI. The Presence Notifier ultimately receives the UDP/IP packets and processes them for the registration state of each MOTOTRBO radio. The Presence Notifier tracks the state of each MOTOTRBO radio on the Radio Network and reports each radio’s state to each Backend Application. Each backend application must subscribe with the Presence Notifier in order to receive notifications of each MOTOTRBO radio of interest. Information between each Backend Application and the Presence Notifier is exchanged as UDP/IP packets. For more information about the Presence Notifier, please see the following references: • Presence Notifier Application User’s Guide • Presence Notifier-to-Watcher Interface Specification • MOTOTRBO Data Services Overview For more information about the other interfaces, please refer to the appropriate sections contained within this overview. Figure 6 - Presence Services Architecture IP Data Pipe Backend Application MOTOTRBO Radio UDP Automatic Registration Service IP Radio Network Notification UDP IP Subscription CAI UDP IP 10 MOTOTRBO - Application Development Kit Overview Presence Notifier Section 2 2.6 Data Services Aside from the data application capability of the MOTOTRBO product for telemetry, location, and text messaging, the MOTOTRBO radios can also be used as a generic UDP/IP “pipe” for the transport of data between multiple IP-capable devices. These devices, such as laptop or desktop PCs, must be attached to subscriber units operating within the Radio Network. The Data Services capability is available while the MOTOTRBO product is operating in digital mode only. Figure 7 – Data Services Architecture UDP/IP over USB MOTOTRBO Mobile The attached PCs are mapped to an IP space that is separate from the MOTOTRBO radio IP address range. Therefore, data intended to the attached IPcapable device or the MOTOTRBO radio can be routed to the appropriate endpoint. For more information about the Data Services capability, please see the following reference: Radio Network • MOTOTRBO Data Services Overview For more information about the other interfaces, please refer to the appropriate sections contained in this overview. MOTOTRBO Mobile 11 MOTOTRBO - Application Development Kit Overview UDP/IP over USB Section 3 3.0 Professional Radio Application Developer Programme The Professional Radio Application Developer Program now includes MOTOTRBO and is comprised of three tiers of membership: Registered Users have access to general information and resources only. Developer Programme Membership Process Flow • Registered User • Licensed Developer • Application Partner / Application Provider Each tier of membership brings greater accessibility to program information and development resources. Interested developers must be approved for Licensed Developer or Application Partner status in order to receive items such as: • Application Development Kit (ADK) documentation • Technical support, including developer forums and training • Program affiliation media, including partner logo and application directory listing • Motorola channel partner and customer information The capability assessment is based on technical competency, commercial capability, and product portfolio. Characteristics that are considered include: • Adequate commercial capability • Expertise in two-way radio communications • Expertise in hardware / software engineering development • Adequate development and test environments • Repeatable development and test processes • Quality Assurance processes Figure 8 – Professional Radio Application Registration Process Licensed Developer Capability Assessment 12 Registered User Application Partner Capability Assessment Licensed Developer Licensing Agreement Application Partner Licensing Agreement Licensed Developer Application Partner MOTOTRBO - Application Development Kit Overview Section 4 4.0 Service & Support for Application Development The MOTOTRBO Application Development Kits (ADKs) are only one component of the service and support for 3rd party developers. The Professional Radio Application Developer Programme for MOTOTRBO is staffed with full-time engineers whose primary responsibility is to support 3rd party application developers world-wide. Application developers have direct access to Motorola resources to assist in the development and certification of the 3rd party application. In order to ensure technical leadership and growth, the capabilities of the MOTOTRBO product and the developer interfaces will be continuously improved and enhanced for greater functionality and expansion. As a mechanism to support this process, Motorola will: • Technical training on the use and capability of the developer interfaces on the MOTOTRBO radio • Application notes and FAQs on relevant MOTOTRBO development topics • Technical consultation service during the design and development phases of the 3rd party product • Access to a MOTOTRBO system test environment with subscribers and infrastructure for 3rd party product verification (where supported by the local business region) Through this process, the MOTOTRBO product will be ensured to have: • Assist developers to define feature enhancements • Document and submit change requests for prioritisation This service and support includes, but is not limited • Track and oversee defect repair of application to, the following items: interfaces 13 • Clear, concise, and accurate developer documentation • Full compliance with published specifications and guides for each application interface • Compatibility audit with older release versions of published specifications MOTOTRBO - Application Development Kit Overview Section 5 5.0 Further Information and Contact For further information about MOTOTRBO and MOTODEV, please visit the following websites: As an alternative, please contact your region’s business development manager for further information on how to develop applications for the MOTOTRBO platform. • Motorola MOTOTRBO: http://www.motorola.com/mototrbo • Asia Pacific Region (APAC) - Yit-Kai Lai (APACAPP@motorola.com) • MOTODEV developer network – Professional Radio Application Developer Program: http://developer.motorola.com • Europe, Middle East, and Africa (EMEA) - Dietmar Kloss (EMEAAPP@motorola.com) • Latin American Countries Region (LACR): - Barbara Wakat (Barbara.Wakat@motorola.com) • North America (NA) - Dwain Lunau (NAGADP@motorola.com) 14 MOTOTRBO - Application Development Kit Overview Section 6 6.0 MOTOTRBO Option Board MOTOTRBO Telemetry MOTOTRBO Location Data MOTOTRBO Text Messaging Appendix: ADK Document Map MOTOTRBO ADK Overview • • • • MOTOTRBO Option Board ADK Guide • MOTOTRBO Option Board PROIS Cross-Reference • MOTOTRBO XCMP / XNL Development Guide • MOTOTRBO XCMP / XNL Development Specification • Document MOTOTRBO Telemetry ADK Guide • MOTOTRBO Telemetry Protocol Specification • MOTOTRBO Location Data ADK Guide • MOTOTRBO LRRP Specification • Motorola Binary XML Encoding Specification • MOTOTRBO Text Messaging ADK Guide • MOTOTRBO Text Messaging Protocol Specification • Presence Notifier Application User’s Guide • • • Presence Notifier-to-Watcher Interface Specification • • • MOTOTRBO Data Services Overview • • • • • • • MOTOTRBO USB Configuration Guide 15 MOTOTRBO - Application Development Kit Overview Motorola GmbH Heinrich-Hertz-Strasse 1 65232 Taunusstein Germany Tel: +49-6128-70-0 Fax: +49-6128-951087 Motorola GmbH Am Borsigturm 130 13507 Berlin Germany Tel: +49-30-6686-0 Fax: +49-30-6686-1916 Motorola Ltd. Jays Close Viables Industrial Estate Basingstoke RG22 4PD UK www.motorola.com/mototrbo MOTOROLA and the Stylised M Logo are registered in the U.S. Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2006. Motorola disclaims any liability for any use of the specification. Motorola limits all warranties to the extent allowed by law. Furthermore, Motorola reserves the right to change this specification at any time without any prior notification, and there is no guarantee that such changes will be backwards compatible with previous versions of the specification. MOTOTRBO.APPL.BR-RE (04/07) 6880309T32
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Mode : UseThumbs XMP Toolkit : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:08:23 Create Date : 2007:05:21 12:53:51+02:00 Metadata Date : 2007:05:21 14:05:31+02:00 Modify Date : 2007:05:21 14:05:31+02:00 Creator Tool : Adobe InDesign CS2 (4.0.5) Thumbnail Format : JPEG Thumbnail Width : 256 Thumbnail Height : 256 Thumbnail Image : (Binary data 11064 bytes, use -b option to extract) Instance ID : uuid:f117a60b-2e26-db48-873e-bd27fa5a49c1 Document ID : adobe:docid:indd:68e5b126-df83-11db-9571-b484e68faaaa Rendition Class : proof:pdf Derived From Instance ID : 68e5b125-df83-11db-9571-b484e68faaaa Derived From Document ID : adobe:docid:indd:bdcd47e5-60fa-11db-bf64-c9e048a637db Manifest Link Form : ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream Manifest Placed X Resolution : 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00 Manifest Placed Y Resolution : 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00 Manifest Placed Resolution Unit : Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches Manifest Reference Instance ID : uuid:4E397B95E6DFDB11B08AC524D897AEB6, uuid:0745712C87C2DB11B53DBF85CE3059CA, uuid:0745712C87C2DB11B53DBF85CE3059CA, uuid:5ad4d14a-c57d-11db-9cc1-00145103aa46, uuid:8DA69968E6DFDB11B08AC524D897AEB6, uuid:c76b5200-c57d-11db-9cc1-00145103aa46, uuid:89707bc4-c285-11db-8c34-0017f2007fca, uuid:bd8ff6ac-c28d-11db-8c34-0017f2007fca, uuid:b6c22eec-c57f-11db-9cc1-00145103aa46, uuid:de5f55ec-c57f-11db-9cc1-00145103aa46, uuid:a87a4cf0-deb6-11db-bb6e-0017f2007fca, uuid:41d301c8-c29c-11db-8c34-0017f2007fca, uuid:EA93118AE6DFDB11B08AC524D897AEB6 Manifest Reference Document ID : uuid:4D397B95E6DFDB11B08AC524D897AEB6, uuid:0645712C87C2DB11B53DBF85CE3059CA, uuid:0645712C87C2DB11B53DBF85CE3059CA, uuid:E7241A6CC3F111DB9580E4E44270C83C, uuid:8CA69968E6DFDB11B08AC524D897AEB6, uuid:E7241A6EC3F111DB9580E4E44270C83C, uuid:478046BAC3FC11DB9580E4E44270C83C, uuid:1FD4EBE6C41411DBA578E25EE66B39C2, uuid:1FD4EBE9C41411DBA578E25EE66B39C2, uuid:3473D2C0C40E11DB9C0EF1EEBD020D04, uuid:4643FD22C41F11DBA578E25EE66B39C2, uuid:4643FD26C41F11DBA578E25EE66B39C2, uuid:E993118AE6DFDB11B08AC524D897AEB6 Format : application/pdf Producer : Adobe PDF Library 7.0 Trapped : False Page Count : 16 Page Layout : TwoColumnRight Creator : Adobe InDesign CS2 (4.0.5)EXIF Metadata provided by EXIF.tools