Professional Documents
Culture Documents
Copyright 2006 Motorola, Inc. All rights reserved. This copyright statement does not imply publication of this document.
Contents 1. Introduction ....................................................................................................4 1.1 Purpose ..................................................................................................4 1.2 Objective.................................................................................................4 1.3 Scope .....................................................................................................4 1.4 Limitations and Assumptions ..................................................................4 1.5 Acronyms, Abbreviations and Definitions ...............................................5 2. Quick Version Reference of Materials ...........................................................6 3. Customers Not Impacted by Rebanding ........................................................7 4. Customers Impacted by Rebanding...............................................................8 4.1 Rebanding Enabled ................................................................................8 4.1.1 Pre-Rebanding Requirements .........................................................8 4.1.2 During Rebanding Upgrade...........................................................11 4.1.3 Post Rebanding Cleanup...............................................................11 4.2 Control Channel Frequencies ...............................................................11 4.2.1 Pre-Reband Requirements............................................................11 4.2.2 During Rebanding Upgrade Procedure .........................................11 4.2.3 Post Reband Cleanup ...................................................................16 4.3 Failsoft Frequencies by Personality......................................................17 4.3.1 Pre Rebanding Requirements .......................................................17 4.3.2 During Rebanding Upgrade Procedure .........................................17 4.3.3 Post Rebanding Cleanup...............................................................18 4.4 Failsoft Frequencies by Announcement Group.....................................19 4.4.1 Pre Rebanding Requirements .......................................................19 4.4.2 During Rebanding Upgrade Procedure .........................................19 4.4.3 Post Rebanding Cleanup...............................................................22 4.5 Failsoft Frequencies by TalkGroup.......................................................22 4.5.1 Pre-Rebanding Requirements .......................................................22 4.5.2 During Rebanding Upgrade Procedure .........................................22 4.5.3 Post Reband Cleanup ...................................................................28 4.6 Cloning .................................................................................................28 4.6.1 Pre Rebanding Requirements .......................................................28 4.6.2 During Rebanding Upgrade Procedure .........................................28 4.6.3 Post Rebanding Cleanup...............................................................29 4.7 Shuffled Band Plan...............................................................................29 4.7.1 Pre-Rebanding Requirements .......................................................29 4.7.2 During Rebanding Upgrade Procedure .........................................30 4.7.3 Post Reband Cleanup ...................................................................31 5. Commonly Asked Questions........................................................................32
Version 1.0
List of Figures Figure 1 Rebanding Non Capable Codeplug for XTS/XTL.................................9 Figure 2 Rebanding Capable Codeplug for ASTRO ........................................10 Figure 3 Rebanding Capable Codeplug for MTS/MCS ....................................10 Figure 4 Existing Type II Control Channel for XTS/XTL and ASTRO...............12 Figure 5 Existing Type II Control Channel for MTS/MCS.................................13 Figure 6 Insert Type II Control Channel ...........................................................14 Figure 7 New Type II Control Channel.............................................................14 Figure 8 Type II Control Channel .....................................................................15 Figure 9 ASTRO 25 Control Channel for XTS/XTL and ASTRO......................16 Figure 10 Failsoft Frequency by Personality....................................................18 Figure 11 Type II Failsoft Frequency by Announcement Group.......................20 Figure 12 ASTRO 25 Failsoft Frequency by Announcement Group for XTS/XTL and ASTRO......................................................................................21 Figure 13 Failsoft Frequency by TalkGroup for XTS/XTL ................................23 Figure 14 Failsoft Frequency by TalkGroup for ASTRO ..................................24 Figure 15 Failsoft Frequency by TalkGroup for MTS/MCS ..............................25 Figure 16 Failsoft Frequency by TalkGroup with New and current Frequency values...............................................................................................26 Figure 17 ASTRO 25 Failsoft Frequency by TalkGroup for XTS/XTL .............27 Figure 18 ASTRO 25 Failsoft Frequency by TalkGroup for ASTRO ...............27 Figure 19 Shuffled Band Plan Capable Field Indicator ....................................30
Version 1.0
1. Introduction
1.1 Purpose
To provide a guideline that ensures standardized subscriber programming practices for the 800 MHz Rebanding project. To provide specific instructions for programming supplemental control channels and Failsoft frequencies into subscribers that have been upgraded to meet current FCC Rebanding guidelines.
1.2 Objective
The objective is to set forth standardized practices that will ensure supplemental frequency information is applied to subscriber units in a consistent manner, regardless of programming personnel.
1.3 Scope
The scope of this document is to provide the subscriber programmer with an understanding of the subscriber programming practices for the 800 MHz Rebanding project using Customer Programming Software (CPS) tool.
Version 1.0
o Replacing the subscriber with a unit that can accommodate the increased memory capacity requirements.
Version 1.0
The Rebanding functionality was initially supported in the CPS software listed above.
Version 1.0
Version 1.0
The customer should also verify the radios are of the proper vintage. This can easily be done by testing a couple of radios. Use the CPS to read a radio and verify if the Rebanding Enabled box is checked. This field actually identifies if the radio is Rebanding Capable.
Version 1.0
For the CPS products, this field will be grayed out until the radio is upgraded with Rebanding capable host. When that upgrade has occurred, this field will be a read-only box that is checked. You can not undo this feature; it is strictly an indication of the capability of the radio. Sample screen shots are shown in the figures below.
Version 1.0
Version 1.0
10
Version 1.0
11
Version 1.0
12
Figure 5 Existing Type II Control Channel for MTS/MCS Note: The example used in this document assumes that the Customers system is comprised totally of NPSPAC channels and all control channel frequency assignments will be changed as part of the 800 MHz Rebanding upgrade. There will be cases where systems may only require one additional control channel frequency for the upgrade and the new frequency should be inserted above the control channel being replaced by the Rebanding process.
The following steps outline the methodology to add the additional control channel frequency information into the subscriber programming template for a system comprised totally of NPSPAC channels. 1. Highlight the first control channel in the list and use the INSERT button to add a default control channel to the top of the list. 2. Repeat this insert operation until the required number of control channels allocations have been added to the list. This process can be viewed in the CPS screen images in Figures 6 & 7.
Version 1.0 13
Once the user has inserted the required additional control channels to the list, the user needs to update those new entries with the new control channel frequency information. Upon completion of the template modification for the 800 MHz Rebanding system upgrade, the control channel list must look as shown in the CPS screen image below. The newly assigned control channel frequencies must be at the top of the list and the original control channel frequencies must be at the bottom of the list. This will allow any newly assigned control channel frequencies (as a result of the upgrade) to be at the top of the control channel list and be scanned first. This will help with radio performance when it attempts to obtain a system control channel during the upgrade process.
PROJECT 25 customers should perform similar steps for 700/800 ASTRO 25 Control Channel Receive Frequency
Version 1.0
17
Figure 10 - Failsoft Frequency by Personality The following steps outline the methodology to add the additional Failsoft frequency information into the subscriber programming template.
1. The original Customer Failsoft frequencies must be copied from the Failsoft Frequency field to the Rebanded Failsoft Frequency field using the standard Windows copy and paste functionality or via manual entry. 2. The new Failsoft frequency assignments for the 800 MHz Rebanding upgrade must then be entered into the original Failsoft Frequency field.
If deletion is desired, this could be completed over time in the normal maintenance cycle. If you wish to do this, simply program the same Failsoft frequency into both fields. This process would apply to XTS/XTL, ASTRO, and MTS/MCS customers.
Version 1.0
19
Figure 11 Type II Failsoft Frequency by Announcement Group The following steps outline the methodology to add the additional Failsoft frequency information into the subscriber programming template.
1. The original Customer Failsoft frequencies must be copied from the Announcement Group Type II Failsoft Frequency field to the Rebanded Announcement Group Type II Failsoft Frequency field
Version 1.0
20
using the standard Windows copy and paste functionality or via manual entry. 2. The new Failsoft frequency assignments for the 800 MHz Rebanding upgrade must then be entered into the original Announcement Group Type II Failsoft Frequency field. PROJECT 25 customers should perform similar steps for Rebanded Announcement Group Channel ID and Rebanded Announcement Group ASTRO 25 Failsoft Frequency
Figure 12 - ASTRO 25 Failsoft Frequency by Announcement Group for XTS/XTL and ASTRO
Version 1.0
21
data in the Rebanded F/S Type II RX Frequency field can be ignored as it will be over-written in later steps.
Version 1.0
23
Version 1.0
24
Figure 15 - Failsoft Frequency by TalkGroup for MTS/MCS The following steps outline the methodology to add the additional Failsoft frequency information into the subscriber programming template or radio codeplug.
1. The original Customer Failsoft frequencies must be copied from the F/S Type II RX Frequency field to one of the Rebanded Failsoft Frequency fields listed below using the standard Windows copy and paste functionality or via manual entry. - Rebanded F/S Type II Rx Frequency for XTS/XTL - Rebanded F/S Rx Frequency for ASTRO - Rebanded F/S Frequency for MTS/MCS 2. The new Failsoft frequency assignments for the 800 MHz Rebanding upgrade must then be entered into the original Failsoft frequency field. - F/S Type II Rx Frequency for XTS/XTL - F/S Rx Frequency for ASTRO
Version 1.0 25
- F/S Frequency for MTS/MCS 3. Upon completion of the template modification for the 800 MHz Rebanding system upgrade, the Failsoft information should look as shown in the CPS screen capture below. The new Failsoft frequency assignments for the 800 MHz Rebanding upgrade should be in the first (F/S Frequency) Failsoft field and the original Failsoft frequency assignments should be in the second (Rebanded F/S Frequency) Failsoft field.
Figure 16 - Failsoft Frequency by TalkGroup with New and current Frequency values XTS/XTL Project 25 customers should perform similar steps for Rebanded Channel ID Number and Rebanded F/S ASTRO 25 Rx Frequency field. ASTRO 25 customers should perform similar steps for Rebanded Channel ID Number and Rebanded F/S Rx Frequency field
Version 1.0
26
Version 1.0
27
4.6 Cloning
4.6.1 Pre-Rebanding Requirements
The customer should verify they have the appropriate Rebanding CPS version: XTS/XTL version R07.00.02 or later ASTRO version R05.00.02 or later MTS/MCS version R02.00.01 or later
Version 1.0
28
In addition to the CPS, the customer must also have an Advanced System Key for the associated Trunking system they wish to deal with. It is important to realize that the use of the Advanced System Key simply tells the radio that it is now capable of doing Shuffled Band Plan. The Trunking System must also be configured to operate in the Shuffled Band Plan mode. It is the system that tells the radio whether it should operate in the Shuffled Band Plan or not. If the radio has been properly programmed with the Advanced System Key, the radio will automatically switch over to the Shuffled Band Plan. If the radio has not been properly programmed, the radio will not be able to operate on this system.
Version 1.0
29
This is read-only and tells the user that the radio is Shuffled Band Plan capable.
2. If the Advanced System Key is not loaded for that System ID in the codeplug, then the value shall remain disabled in the codeplug and radio. 3. The status of Shuffled Band Plan field remains unchanged in the radio after the Flashport upgrade process.
Version 1.0
31
Q2) At the end of reconfiguration, does a licensee have to go back to each radio and take out the old control channels? This answer varies by the type of channels in use in your system: trunked or conventional. For trunked systems, there is no need to remove the old Control channels or Failsoft channels from the radios after rebanding is completed. In the case of conventional systems, it is possible that licensees will have to go back and remove old channels. The key point is to avoid having radios using channels which the licensee is no longer licensed to use after rebanding.
Q3) During the reconfiguration of the systems/controllers will system have to drop down to 50% capacity? No, the amount of channels will vary based upon capacity requirements of an individual user. The 50% capacity shown on a previous Motorola presentation was an example of how to manage the reconfiguration of a controller, but is not a required level of capacity shutdown for reconfiguration. The decision about system capacity requirements during reconfiguration must be made locally and is based upon licensee preferences, system topology, and other factors that all must be taken into account.
Version 1.0
32