Motorola and Sonik Confidential Proprietary

------

RF-Audience! II

Inbound Base Receiver

MARKETING PRODUCT DESCRIPTION

By John Potocki

V1.3

Aug 03, 1998


CHANGE HISTORY

Version Date Author Summary of Changes

0.1 9/23/97 Jeff Lipschultz Initial Draft

0.2 2/16/98 John Potocki Begin to add customer specific rqts

(NWN BRII, Mobilcom)

0.5 3/5/98 John Potocki Change format and number MPD Rqmt

1.0 3/10/98 John Potocki Uprev after review with Developmnt

and Distribution

1.1 3/30/98 John Potocki Modify: MPD023, 023.1 establish sensitivity

goals at 6400, 9600 bps

1.2 6/11/98 John Potocki remove internal goals

1.3 8/3//98 John Potocki Remove Sect 3 by name only, remove

former MPD006 Datatac support,

remove former MPD031 Inbound Concentrator,

remove former MPD039-044 GPS (see

GPS Sharing Doc), remove former MPD033

Soft decision decoding for sensitivity imprv

1.0 Introduction

This document describes the market requirements for the release of the next generation Motorola RF-Audience inbound base receiver. The document’s objective is to describe the features and functions RFAII in enough detail to allow Motorola PSG and Sonik to generate a Contract Book and Requirements Document(s).

Program Feature Sections:

The sections of the RFA II feature set will be defined as follows:

Section 2: These features are required for all customers worldwide and the architecture for the next generation RFAII.

Section 3: These features are required for NWN BRII for the next channel of Skytel’s ReFLEX50 system.

Section 4: Other Asia or miscellaneous requirements.

2.0 RF-AudienceII General Requirements

MPD Feature Phase

System Features

RFAII.MPD 001 / The RFAII shall support the Inbound Paging Protocol V1.0 or later. / Phase 1
RFAII.MPD 002 / The RFAII shall support ReFLEX25 and InFLEXion OTA (over the air) interface. / Phase 1
RFAII.MPD 003 / The RFAII shall support ReFLEX50 protocol for the Skytel Two-Way network. / Phase 2
RFAII.MPD 004 / The RFAII shall support Wireless Message System - Data Version V1.0 or later. See WMS - Data MPD V1.0 or later. / Phase 1
RFAII.MPD 005 / Long Inbound Messages: The RFAII shall support multiple DU s for a system capability of long inbound messages up to 2000 characters. / Phase 1

General Receiver Features/Specifications

RFAII.MPD 006 / The RFAII shall support a reverse channel frequency of 895-902 Mhz / Phase 1
RFAII.MPD 007 / The RFAII shall support a reverse channel frequency of 915-931 Mhz / Phase 1
RFAII.MPD 008 / The RFAII shall support a channel spacing of 12.5 kHz in 6.25 kHz steps, with a user interface error notification if erroneous frequencies are attempted to be entered. / Phase 1
RFAII.MPD 009 / The RFAII shall support synthesized frequency generation. / Phase 1
RFAII.MPD 010 / The RFAII shall support two branch antenna diversity per inbound channel. / Phase 1
RFAII.MPD 011 / The RFA shall support OTA inbound data rates of 800, 1600, 6400 and 9600 bps. It is acceptable to have a phased in approach for 6400 and 9600 bps, software only. / Phase 1
RFAII.MPD 012 / Operating Temperature: The RFAII shall support -30 to
+ 60C operating condition up to 5,000 feet above sea level. Above that, a degradation of 2C in operating temperature will be allowed per 1,000 feet up to 10,000 feet total above sea level. / Phase 1
RFAII.MPD 013 / Operating Humidity: The RFAII shall support 0% to 90% non-condensing. / Phase 1
RFAII.MPD 014 / Antenna Connector: The RFAII shall support an ‘N’ Type antenna connector(s), using a BNC connector for the forward channel synch Rx (outbound Rx). / Phase 1
RFAII.MPD 015 / RF Input Impedence: The RFAII shall support a 50 Ohm input impedence. / Phase 1
RFAII.MPD 016 / FCC Emmissions Designators: Part 15 Class B. Also must be UL compliant. / Phase 1
RFAII.MPD 017 / Off Channel Acceptance: +/- 500 Hz (per ReFLEX 2.5 specifications) / Phase 1
RFAII.MPD 018 / Inbound Spurious and Image Rejection: 90 dB. See note 1. / Phase 1
RFAII.MPD 019 / Inbound Adjacent Channel Selectivity: 70 dB. See note 1 / Phase 1
RFAII.MPD 020 / Inbound Intermodulation Rejection: 80 dB. See Note 1 / Phase 1
RFAII.MPD 021 / Maximum RF Input level: -20 dB with single channel signal / Phase 1
RFAII.MPD 022 / Input VSWR: 1.5: 1 or less, reference to 50 ohms / Phase 1
RFAII.MPD 023 / Sensitivity, at typical minimum (see note 2) without multicoupler :
-134 dBm @ 800 bps (1% RAW BER)
-131 dBm @ 1600 bps (1% RAW BER)
-126 dBm @ 6400 bps (1% RAW BER)
-123 dBm @ 9600 bps (1% RAW BER)
A multicoupler package, designed by Motorola, will be required to interface to the RFA II, and is expected to add another 2 to 3 dBm to the figures above. The Motorola designed multicoupler is expected to house the required front-end filtering. / Phase 1
RFAII.MPD 024 / The RFAII shall support Network Connectivity through Ethernet (10 Base2) port. / Phase 1
RFAII.MPD 025 / Size: The RFAII must be one rack unit (1 RU) high, depth under 11”. / Phase 1
RFAII.MPD 026 / DC Operation: The RFA II will operate off of an input power source of 20-31VDC. AC input power will not be required. / Phase 1
RFAII.MPD 027 / Weight: The RFAII must weigh under 18 lbs. / Phase 1
RFAII.MPD 028 / Interconnect Points:
5/10 Mhz Ref Input: female BNC
DC Power: Phoenix 2-pin
Ethernet 10base-2: female BNC
Network Serial RS-232: male DB-9
Terminal Port: RS-232
RFA Input A: N type
RFA Input B: N type
Forward Channel Synch Rx: female BNC
GPS/Timing: RS-485 / Phase 1
RFAII.MPD 029 / Multi-channel Capable: The next generation RFAII (call it the RFA III) must support up to a four (4) channel receiver (either two 2-port Diversity Rxs or four non-diversity Rxs one used for forward channel synch) in one Rack Unit (1 RU) high. The migration plan for RFA II to RFA III is as follows: a field upgrade hardware kit is expected to be required, including a changeout of boards and additions to the backplane of the receiver. / Phase 2
RFAII.MPD 030 / Spread Spectrum Capable: The next generation RFAII (called RFA III) must be frequency hop (FH) spread spectrum capable, as the market dictates for the spread spectrum frequencies (in US the frequencies are 902-928 Mhz). / Phase 3
RFAII.MPD 031 / Error Correction Methodology: At minimum, Reed-Soloman will be used for sensitivity enhancement. / Phase 1
RFAII.MPD 032 / FRU Maintainability: The RFAII must support a plug-in field replaceable module strategy for easy maintenance, lower downtime and overall lower maintenance costs. / Phase 1
RFAII.MPD 033 / De-sync IPP packets: The RFAII shall support psuedo-randomized IPP packet launches for heavy inbound traffic environments. / Phase 2

Synchronization

RFAII.MPD 034 / Synchronization: GPS with GPS or UTC timing / Phase 1
RFAII.MPD 035 / Forward Channel Synch: The RFAII must support forward channel synchronization from 928 to 941 Mhz. / Phase 1
RFAII.MPD 036 / Frequency Stability: +/- 0.1 ppm with GPS synchronized. The RFAII shall be capable of normal operation, free wheeled, for up to 15 minutes upon loss of GPS. / Phase 1
RFAII.MPD 037 / The RFA II shall support GPS Sharing (acting as a master and a slave to the GPS feed) and all GPS Receiver requirements as stated in the Motorola GPS Sharing Document V0.6. / Phase 1
RFAII.MPD 038 / The RFAII must support Motorola UT GPS receiver, a remote GPS receiver with coaxial connectivity to the base receiver. / Phase 1
RFAII.MPD 039 / Non-Motorola GPS: The RFA II must support non-Motorola Trimble GPS receiver, model number to be supplied. / Phase 1

User Interface/ Diagnostics

RFAII.MPD 040 / User Interface: The RFA II must support lap top user interface with all receiver parameters and alarm log on one or two screens. At minimum, the feature set shall look like or function equivalent to the GL R9000 base receiver user interface. / Phase 1
RFAII.MPD 041 / The RFAII shall support local and remote metering/diagnostic functions via SNMP or Telnet for maintenance. A minimum of four (4) telenet sessions are required per RFA II. / Phase 1
RFAII.MPD 042 / Alarms: The RFAII shall support the features as stated in the NMS MPD V1.0, and be able to support the following alarms and error logs at a minimum:
* Receiver Fail
* Cabinet Intrusion
* Loss of AC power
* Alarm on Reset
* Not tracking satellites
* GPS fail
* Low traffic timeout, traffic threshold and time interval both adjustable, per channel
* External Alarm / Phase 1
RFAII.MPD 043 / UARs: The RFAII shall support unsolicited alarm reporting for the above alarm set via an SNMP alarm trap. / Phase 1
RFAII.MPD 044 / External Alarms: The RFAII must support two external alarm inputs for customer use, also called programmable I/Os. The purpose would be to provide an alarm upon loss of signal A or signal B. Inputs shall incorporate internal pull up resistor. An external contact closure to ground or resistive load of 220 ohms or less shall cause an unsolicited alarm condition to be generated. A UAR reporting status OK shall be generated upon restoring an open circuit or if the external resistive load exceeds 10,000 ohms. A separate UAR with user definable text shall be provided for each external input. / Phase 1
RFAII.MPD 045 / Noise Metering and Statistics: The RFAII must support a user settable alarm that notifies the operator that the noise floor has reached a certain limit at site. / Phase 1
RFAII.MPD 046 / Multicast Software Download: The RFAII must support the ability to download software to mutliple RFAIIs simultaneously. Software downloads shall not interfere with normal operation of receiver and downloaded software shall be permanently stored in an active register for later use. The software download for each RFA II should take no longer than 10 minutes to complete using a 19.2kbps or greater digital line. / Phase 1
RFAII.MPD 047 / The RFAII shall be able to switch between active and inactive software versions by means of local or remote control over leased line connection. / Phase 1
RFAII.MPD 048 / Quality Goal: The RFAII must be designed to have a failure rate below 0.25% per month, so as to contribute to meet the 5-9s System Availability Initiative. / Phase 1
RFAII.MPD 049 / Frequency Stability: The RFAII must support an internal frequency stability performance without GPS as follows:
+/- 10E-6 free running
+/- 10E-7 locked to the forward channel / Phase 1
RFAII.MPD 050 / Outdoor Environment: The RFAII must be form factored to be placed in an outdoor encloser. / Phase 1
RFAII.MPD 051 / Pole/Wall Mount: The RFAII form factor must be able to be wall/pole/billboard mountable in an outdoor encloser. / Phase 2
RFAII.MPD 052 / Wireline or Wireless Link: The RFAII must be able to interface to a wireline or wireless linkback to the controller for inbound paging traffic. / Phase 1
RFAII.MPD 053 / Power: The RFAII needs to use around 700 mA @ 12VDC power consumption. / Phase 1
RFAII.MPD 054 / Additional Interconnect Point: The RFAII must support an LNA Output for a 2nd Receiver (to share filters and antenna in the 2nd receiver). / Phase 1

3.0 NWN BRII Specifications

Note: Although the receiver below is referred to as NWN BRII, it can also be referred to as

the RFA III, as the two names are expected to be interchangeable.

RFAII.MPD 057 / Maximum RF Input Level: The NWN BRII shall not be damaged with an input signal level of up to +30 dBm. The receiver shall operate from -125 dBm to 0 dBm. / Phase 2
RFAII.MPD 058 / The NWN BRII shall be capable of accepting command from the network for resetting the CPU. / Phase 2
RFAII.MPD 059 / The NWN BRII shall incorporate a watchdog timer to reset the CPU in the event of lock up. / Phase 2
RFAII.MPD 060 / AC Input Power: 100-135VAC 60 Hz, 200W max. This input source is expected to be an external AC-to-DC converter that is not integrated into the RFAII chassis. Add a distribution panel for upgrade to four collocated NWN BRIIs. / Phase 2
RFAII.MPD 061 / Program Downloads: Program downloads from the Sub-Controller to the NWN BRII shall be performed using NWN dowload protocol (NDP). Refer to NWN protocol suite specification data V2.0. / Phase 2
RFAII.MPD 062 / Received Data: The NWN BRII shall send received data from PMUs to the network using the Receiver Data Protocol (RDP). Refer to NWN Protocol suite specification document V2.0. / Phase 2
RFAII.MPD 063 / Command and Alarm: The NWN BRII shall pass command and alarm data between the base receiver and the network using the Command/Alarm Protocol (CAP). Refer to NWN Protocol suite specification V2.0. / Phase 2
RFAII.MPD 064 / Transport/Network Layer Protocol: The NWN BRII shall support the transport/network layer protocol point-to-point (PPP) between it and Sub-Controller. / Phase 2
RFAII.MPD 065 / The NWN BRII shall have a flat audio monitor service jack for observation of demodulated signals, switchable among any installed channel. / Phase 2
RFAII.MPD 066 / The NWN BRII shall interface to a customer specified modem or DSU, provide power for the same, including backup power, and provide physical mounting internal to the cabinet but external to the receiver chassis. The interface shall operate reliable at speeds up to 64 kbps. / Phase 2
RFAII.MPD 067 / The NWN BRII shall incorporate an output buffer in order to prevent loss of traffic in the event of a brief network interruption or surge in traffic. Buffer size shall be 16 kbits, minimum. RTS/CTS handshaking shall be employed. / Phase 2
RFAII.MPD 068 / BER Sensitivity Test: The NWN BRII shall support a closed loop testing to facilitate a BER effective sensitivity test. Such a test will be executable over the forward channel with results readable either locally by the technician or by remote control over a network connection. / Phase 2
RFAII.MPD 069 / Third Order Intercept Point: +20 dBm IP cubed / Phase 2
RFAII.MPD 070 / Dual Mode: The RFAII must be dual mode (ReFLEX25 and ReFLEX50) capable and two-channel capable; such that the RFAII can detect an inbound signal, determine whether it is from a ReFLEX25 or ReFLEX50 device on different 12.5Khz inbound channels (between 901 and 902 Mhz), and send inbound packets back to the controller via IPP (for ReFLEX25) or RDP (for ReFLEX50) to the NOC. / Phase 2

4.0 Other Requirements including Asia Market