Motorola Rebanding Subscriber Programming Guidelines V1 1

800 MHz Rebanding Subscriber Programming

Guidelines

Version: 1.1

Date: 23-June-2006

Copyright © 2006 Motorola, Inc. All rights reserved. This copyright statement does not imply publication of this document.

Rebanding Subscriber Programming Guidelines

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 2


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 3


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.

1.4 Limitations and Assumptions

• All XTS/XTL 5000/2500/1500 and ASTRO Spectra + customers must use R07.00.02 or later version of CPS for seamless cloning functionality in Rebanding software.

• All ASTRO Spectra/Saber and XTS 3000 customers must use R05.00.02 or later version of CPS for Rebanding functionality.

• All MTS/MCS 2000 customers must use R02.00.01 or later version of CPS for Rebanding functionality.

• If the subscriber codeplug memory size is close to maximum capacity, then adding new fields for rebanding may not be possible without:

o Deleting existing information from the subscriber to allow new information to be added.

Or

Version 1.0 4


o Replacing the subscriber with a unit that can accommodate the increased memory capacity requirements.

1.5 Acronyms, Abbreviations and Definitions The following section defines some of the short-hand product labeling used through-out this document

• XTS/XTL – The XTS/XTL 5000 / 2500 / 1500, MT 1500, and ASTRO Spectra Plus family of products

• ASTRO – The ASTRO Spectra, ASTRO Saber and XTS 3000

family of products • MTS/MCS – The MTS 2000 and MCS 2000 family of products

Version 1.0 5


2. Quick Version Reference of Materials All processes defined in these guidelines assume the user has the following version of Customer Programming Software (CPS) or later.

• XTS/XTL 5000 / 2500 / 1500 and ASTRO Spectra Plus CPS - R07.00.02

• ASTRO Spectra/Saber and XTS 3000 CPS - R05.00.02

• MTS / MCS 2000 CPS - R02.00.01

The Rebanding functionality was initially supported in the CPS software listed above.

Version 1.0 6


3. Customers Not Impacted by Rebanding

Customers whose subscriber units will not undergo rebanding upgrades will need to perform the following steps to be compatible with Rebanding Enabled CPS software releases. For a 3600 Analog or Digital Type II Trunking customer, they should complete the following steps:

1. Copy the Failsoft Frequency field (located on Trunking Personality, 700/800 Failsoft tab) to the Rebanded Failsoft Frequency field.

2. Copy the Announcement Group Type II Failsoft Frequency field (located on Trunking Personality, 700/800 Failsoft tab) to the Rebanded Announcement Group Type II Failsoft Frequency field.

3. Copy the Failsoft (F/S) Type II Rx Frequency field (located on Trunking Personality, Talkgroup tab) to the Rebanded F/S Type II Rx Frequency field.

For a 9600 Digital Trunking customer, they should complete the following steps:

1. Copy the Announcement Group Failsoft Channel ID field (located on Trunking Personality, 700/800 Failsoft tab) to the Rebanded Announcement Group Failsoft Channel ID field.

2. Copy the Announcement Group ASTRO 25 Failsoft Frequency field (located on Trunking Personality, 700/800 Failsoft tab) to the Rebanded Announcement Group ASTRO 25 Failsoft Frequency field.

3. Copy the Channel ID Number field (located on Trunking Personality, Talkgroup tab) to the Rebanded Channel ID Number field.

4. Copy the Failsoft (F/S) ASTRO 25 Rx Frequency field (located on Trunking Personality, Talkgroup tab) to the Rebanded F/S ASTRO 25 Rx Frequency field.

Note: For the ASTRO Spectra/Saber, XTS 3000, and MTS/MCS 2000 customers, use your entire flash key before upgrading to the rebanding software. Rebanding software does not support old FLASHport keys that attach to the Smart RIB (SRIB). It only supports the new Enhanced FLASHport keys that attach to the Parallel port, not the Smart RIB (SRIB).

Version 1.0 7


4. Customers Impacted by Rebanding Customers whose subscriber units will be reprogrammed to support Rebanding or replaced to support Rebanding will need to perform the following steps to properly configure the subscriber units with the Rebanding Enabled CPS software releases.

4.1 Rebanding Enabled Customers should verify that they have Rebanding capable CPS and radios before starting any subscriber retuning process. If the radios have not been reprogrammed with a Rebanding capable radio operating system, a customer will not be able to properly configure the subscribers.

4.1.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

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 8


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.

Figure 1 –Rebanding Non Capable Codeplug for XTS/XTL

Version 1.0 9


Figure 2 - Rebanding Capable Codeplug for ASTRO

Figure 3 - Rebanding Capable Codeplug for MTS/MCS

Version 1.0 10


4.1.2 During Rebanding Upgrade Customers must use the Rebanding Capable CPS version (listed in Section 4.1.1) throughout the Rebanding process.

4.1.3 Post Rebanding Cleanup After the Rebanding process is completed and all of the radios are upgraded, customers can continue to use the Rebanding Capable CPS versions (listed in Section 4.1.1) or a later version.

4.2 Control Channel Frequencies 4.2.1 Pre-Reband Requirements

It is difficult to give absolute direction because the system needs and situation for each customer will be different.

In configuring the upgraded radios initially, the customer should understand if it will require additional control channels to aid in inter-system operations. If so, this information should be added to the radio codeplug information initially.

The additional control channel frequency information must be added to the top of the control channel list for all upgrades due to identified inter-system operational scenarios. 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.

4.2.2 During Rebanding Upgrade Procedure When the radio is read using a Rebanding Capable version of CPS, the user will see the existing list of control channels as shown in the CPS screen capture as shown in Fig. 4.

Version 1.0 11


Figure 4 – Existing Type II Control Channel for XTS/XTL and ASTRO

Version 1.0 12


Existing Control Channel Frequencies

Figure 5 – Existing Type II Control Channel for MTS/MCS

Note: The example used in this document assumes that the Customer’s 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


Figure 6 – Insert Type II Control Channel

Figure 7 – New Type II Control Channel

Version 1.0 14


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.

Figure 8 - Type II Control Channel

Version 1.0 15


PROJECT 25 customers should perform similar steps for 700/800 ASTRO 25 Control Channel Receive Frequency

Figure 9 - ASTRO 25 Control Channel for XTS/XTL and ASTRO

4.2.3 Post Reband Cleanup The Customer may choose to delete all old control channel frequency information once the upgrade is complete, but this is not a requirement. If deletion is desired, it could be completed over time in the normal maintenance cycle. This process would apply to XTS/XTL, ASTRO, and MTS/MCS customers.

Version 1.0 16


4.3 Failsoft Frequencies by Personality 4.3.1 Pre Rebanding Requirements


In configuring the upgraded radios initially, the customer should understand if it will require additional Failsoft Frequencies to facilitate the upgrade of the system. If so, this information should be added to the radio codeplug information initially.

Technical field personnel will be required to identify if additional Failsoft frequencies are required, and what those frequencies are. The additional Failsoft frequency information must be added to the subscriber programming template (or codeplug). This allows the newly assigned Failsoft frequencies to be first in the Failsoft list, in the event that a subscriber reverts to the Failsoft mode of operation in the future.

4.3.2 During Rebanding Upgrade Procedure When the radio is read using the Rebanding Capable version of CPS, the user will see two Failsoft frequency allocation fields as shown in Figure 10. One is labeled Failsoft Frequency and the second is labeled Rebanded Failsoft Frequency. The Failsoft Frequency field will contain the existing pre-rebanding Customer Failsoft frequency information as programmed in their subscriber units. Any data in the Rebanded Failsoft Frequency field can be ignored as it will be over-written in later steps.

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.

4.3.3 Post Rebanding Cleanup Customers may choose to delete all old Failsoft frequency information once the upgrade is complete, but this is not a requirement.

Version 1.0 18


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.

4.4 Failsoft Frequencies by Announcement Group 4.4.1 Pre-Rebanding Requirements

It is difficult to give absolute direction because the system needs and situation for each customer will be different


Technical field personnel will be required to identify if additional Failsoft frequencies are required, and what those frequencies are. The additional Failsoft frequency information must be added to the subscriber programming template (or codeplug) at the top of the list. This allows the newly assigned Failsoft frequencies to be first in the Failsoft list, in the event that a subscriber reverts to the Failsoft mode of operation in the future.

4.4.2 During Rebanding Upgrade Procedure

When the radio is read using the Rebanding Capable version of CPS, the user will see two Failsoft frequency allocation fields as shown in Figure 11. One is labeled Announcement Group Type II Failsoft Frequency and the second is labeled Rebanded Announcement Group Type II Failsoft Frequency. The Announcement Group Type II Failsoft Frequency field will contain the existing pre-rebanding Customer Failsoft frequency information as programmed in the subscriber units. Any data in the Rebanded Announcement Group Type II Failsoft Frequency field can be ignored as it will be over-written in later steps.

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


4.4.3 Post Rebanding Cleanup Customers may choose to delete all old Announcement Group Failsoft frequency information once the upgrade is complete, but this is not a requirement.

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

PROJECT 25 customers should perform similar steps for Rebanded Announcement Group Channel ID and Rebanded Announcement Group ASTRO 25 Failsoft Frequency


4.5 Failsoft Frequencies by TalkGroup 4.5.1 Pre-Rebanding Requirements



Technical field personnel will be required to identify if additional Failsoft frequencies are required, and what those frequencies are. The additional Failsoft frequency information must be added to the subscriber programming template (or codeplug) at the top of the list. This allows the newly assigned Failsoft frequencies to be first in the Failsoft list, in the event that a subscriber reverts to the Failsoft mode of operation in the future.

4.5.2 During Rebanding Upgrade Procedure When the radio is read using the Rebanding Capable version of CPS, the user will see two Failsoft frequency allocation fields as shown in Figures 13-15 as appropriate. One is labeled F/S Type II RX Frequency and the second is labeled Rebanded F/S Type II RX Frequency. The F/S Type II RX Frequency field will contain the existing pre-rebanding Customer Failsoft frequency information as programmed in the subscriber units. Any

Version 1.0 22


data in the Rebanded F/S Type II RX Frequency field can be ignored as it will be over-written in later steps.

Figure 13 - Failsoft Frequency by TalkGroup for XTS/XTL

Version 1.0 23


Figure 14 - Failsoft Frequency by TalkGroup for ASTRO

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


Figure 17 - ASTRO 25 Failsoft Frequency by TalkGroupfor XTS/XTL

Figure 18 - ASTRO 25 Failsoft Frequency by TalkGroup for ASTRO

Version 1.0 27


4.5.3 Post Rebanding Cleanup Customers may choose to delete all old Failsoft Type II frequency information once the upgrade is complete, but this is not a requirement.

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

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


4.6 Cloning 4.6.1 Pre-Rebanding Requirements

The customer should verify they have the appropriate Rebanding CPS version:




4.6.2 During Rebanding Upgrade Procedure Customers will need to FLASHport upgrade or refresh the radio using the latest Rebanding capable version of the CPS for the Rebanding functionality.

• First FLASHport upgrade with Rebanding capable radio operating system.

• Read the codeplug from upgraded radio. • Set the applicable rebanding frequencies value as described in

previous section. • Save this codeplug as a file on the computer so that it can be

referenced in the future as a radio template. • Use this template to clone other upgraded radios.

Version 1.0 28


4.6.3 Post Rebanding Cleanup This process is the traditional cloning process with a modification to ensure that the codeplug and radios are properly updated. There is no information that needs to be “cleaned up” after the cloning process beyond what was defined in previous sections.

4.7 Shuffled Band Plan

Radios that have been upgraded to be Rebanding capable are also capable of supporting the Shuffled Band Plan. The Shuffled band plan is intended to help prevent unauthorized system monitoring and access on Shuffled Band Plan enabled systems. Shuffled Band Plan shuffles all trunking numbered-channels allowed in the band plan.

Note that Shuffled Band Plan can only be enabled by the Rebanding Capable CPS program with an appropriate Advanced System Key per Trunking System. This feature is designed and implemented for Motorola 3600 Type II Trunking systems.

4.7.1 Pre-Rebanding Requirements The customer should verify they have subscribers that are Rebanding Capable and the appropriate Rebanding CPS version:




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.

Figure 19 – Shuffled Band Plan Capable Field Indicator

4.7.2 During Rebanding Upgrade Procedure During the rebanding process, the user should ensure that the Advanced System Key for their particular system is attached to their computer. The user should verify that the Shuffled Band Plan box is checked after they reprogram the radio. This field is not editable by customers. This field is set automatically via CPS and only indicates that the radio is capable.

Please note, the Shuffled Band Plan feature and the required Advanced System Key only impacts the CPS when the CPS writes or clones to the radio.

1. If the Advanced System Key is loaded for a particular System ID in the codeplug, then the CPS will enable Shuffled Band Plan in codeplug and radio.

Version 1.0 30


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.

4.7.3 Post Reband Cleanup This process is the traditional programming or cloning process with a modification to ensure that the codeplug and radios are properly updated. There is no information that needs to be “cleaned up” after the cloning process beyond what was defined in previous sections.

It is important to remember that the Shuffled Band Plan field only indicates that the radio is capable of operating in the Shuffled Band Plan. The subscriber will only operate in the Shuffled Band Plan mode if the system directs the subscriber to operate in that mode. The Shuffled Band Plan capability does not limit or change the current Motorola Type II trunking operation for non-Shuffled Band Plan systems.

Version 1.0 31


5. Commonly Asked Questions

Q1) How can a licensee manage interoperability with other licensees in their area when they migrate to their new control channels if all licensees are not reconfiguring their systems at the same time?

Motorola Recommends that all subscribers in a given area which must maintain ongoing interoperability upgrade all their subscribers prior to commencing any infrastructure work. Motorola’s Rebanding software was developed with this issue in mind. We have programmed both band plans into the radios, thus allowing the subscribers to switch back and forth between band plans as dictated by the outbound signals from the sites that the radio encounters.

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

Motorola Rebanding Subscriber Programming Guidelines V1 1

Documents

Transcript of Motorola Rebanding Subscriber Programming Guidelines V1 1