Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola, Inc. reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Motorola products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Motorola intends to announce such Motorola products, programming, or services in your country.
Copyrights
This instruction manual, and the Motorola products described in this instruction manual may be, include or describe copyrighted Motorola material, such as computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted Motorola material contained herein or in the Motorola products described in this instruction manual may not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola, as arises by operation of law in the sale of a product.
Copyrighted Materials
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola, Inc.
Trademarks
and Motorola are registered trademarks of Motorola, Inc. Product and service names profiled herein are trademarks of Motorola, Inc. Other manufacturers products or services profiled herein may be referred to by trademarks of their respective companies.
Copyright
Copyright 2001 Motorola, Inc. All Rights Reserved
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patent Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1 4-2
i
4-5
ii
June 2001
Figure 1-1: Functional Block Diagram of a CDMA Network . . . . . . . . . . . . . . Figure 1-2: Flow Diagram for Generic Capacity Engineering Process . . . . . . . Figure 2-1: Admission Rate Control NonOverload Condition . . . . . . . . . . . . . Figure 2-2: Admission Rate Control Overload Condition . . . . . . . . . . . . . . . . . Figure 2-3: Capacity Control Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-4: CBSC Splitting Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-5: New OMCR and CBSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-6: New CBSC with an existing OMCR . . . . . . . . . . . . . . . . . . . . . . . Figure 2-7: Alternating OMCR Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-8: New CBSC with same OMCR, new BTS IDs . . . . . . . . . . . . . . . Figure 2-9: New CBSC with the same OMCR, same BTS IDs . . . . . . . . . . . . Figure 2-10: New CBSC with the same OMCR, same BTS IDs in two steps Figure 2-11: New CBSC with an existing OMCR, new MIB, same BTS IDs Figure 2-12: Four Carriers, threesector BTS Example . . . . . . . . . . . . . . . . . . . Figure 2-13: Threesector Multicarrier BTS Example . . . . . . . . . . . . . . . . . . . Figure 2-14: BTSs per CBSC vs. Avg. Erlangs per BTS . . . . . . . . . . . . . . . . . . Figure 2-15: Puma MM Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-16: Layered CBSC Architecture Design . . . . . . . . . . . . . . . . . . . . . . . Figure 2-17: Fourcarrier, Twolayer Example . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2-18: Typical Eightcarrier Tx and Rx Configuration . . . . . . . . . . . . . . Figure 2-19: System Redundancy in a Layered CBSC Architecture . . . . . . . . . Figure 2-20: InterCBSC Handoff from Multiple Layers to a Single Layer . . . Figure 2-21: Uneven CBSC overlay in the third Carrier Application . . . . . . . . Figure 3-1: SC9600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-2: Single RF Modem Frame Mounting Order . . . . . . . . . . . . . . . . . . . Figure 3-3: Multiple RF Modem Frame Mounting Order . . . . . . . . . . . . . . . . . Figure 3-4: SC4800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-5: Combiner 2:1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-6: Combiner 4:1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001 CDMA SC Products System Resource Guide (CSSRG)
1-8 1-10 2-6 2-7 2-11 2-34 2-34 2-35 2-35 2-36 2-37 2-37 2-38 2-40 2-41 2-41 2-42 2-44 2-45 2-46 2-49 2-52 2-54 3-28 3-30 3-30 3-34 3-36 3-36
iii
Figure 3-7: SC4812 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-8: Examples of SC4812 Combining Schemes . . . . . . . . . . . . . . . . . . . Figure 3-9: SC2400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-10: SC614 RF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-11: Multiple Carrier PicoCell RF Antenna Configuration . . . . . . . . . . Figure 3-12: One and Two Carrier MicroCell RF Antenna Configurations . . . . Figure 3-13: Three Carrier MicroCell RF Antenna Configuration . . . . . . . . . . Figure 3-14: Four Carrier MicroCell RF Antenna Configuration . . . . . . . . . . . Figure 3-15: SC4840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-16: SC2440 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3-17: Multiple Carrier PicoCell RF Antenna Configuration . . . . . . . . . Figure 3-18: One and Two Carrier MicroCell RF Antenna Configurations . . . . Figure 3-19: Three Carrier MicroCell RF Antenna Configuration . . . . . . . . . . Figure 3-20: Four Carrier MicroCell RF Antenna Configuration . . . . . . . . . . . Figure 7-1: Cell Split Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-2: MicroCell Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-3: Ubiquitous Carrier Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-4: NonUbiquitous Carrier Example #1 . . . . . . . . . . . . . . . . . . . . . . . Figure 7-5: NonUbiquitous Carrier Example #2 . . . . . . . . . . . . . . . . . . . . . . . Figure 7-6: Transition Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-7: Example of Forward CDMA Channels . . . . . . . . . . . . . . . . . . . . . . Figure 7-8: Example of Reverse CDMA Channels . . . . . . . . . . . . . . . . . . . . . . Figure 7-9: Slotted Mode Structure Example . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7-10: Access Channel Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-1: Validation and Terrestrial Circuit Assignment . . . . . . . . . . . . . . . . Figure A-2: Circuit Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-3: Traffic Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-4: Ringback and Conversation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-5: Paging and Control Messages though the Subsystems . . . . . . . . . . Figure A-6: Validation and Circuit Assignment . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-7: Alerting and Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-8: Pilot Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-9: Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure A-10: Handoff Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-38 3-41 3-43 3-48 3-53 3-53 3-53 3-54 3-59 3-62 3-65 3-65 3-65 3-66 7-27 7-28 7-29 7-29 7-30 7-31 7-33 7-34 7-39 7-41 A-1 A-2 A-3 A-4 A-5 A-6 A-8 A-9 A-10 A-11
iv
June 2001
Table 1-1: Template for Typical Measurement Schedule . . . . . . . . . . . . . . . . . . Table 2-1: Standard Transcoder Maximum and Planning Erlang Capacities . . . Table 2-2: MM Capacity Limits Calculation Example . . . . . . . . . . . . . . . . . . . Table 2-3: Example CBSC Erlang Forecast . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-4: CBSC Load Balancing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-5: Summary of Advantages and Disadvantages of the layered CBSC approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-6: Handoff Transition Method Example . . . . . . . . . . . . . . . . . . . . . . . . Table 2-7: Recommended Values for the Rate Overload Parameters . . . . . . . . . Table 2-8: Summary of CBSC Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1: Logical BTS Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-2: Example Spreadsheet to Forecast Traffic Usage . . . . . . . . . . . . . . . . Table 3-3: Example Spreadsheet to Forecast Required Channelization . . . . . . . Table 3-4: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-5: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-6: Output Power/Sector vs. Number of Modules . . . . . . . . . . . . . . . . . Table 3-7: SC9600 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-8: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-9: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-10: SC4852/4850/4820 Operating Frequencies . . . . . . . . . . . . . . . . . . . Table 3-11: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-12: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-13: SC4812 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-14: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-15: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-16: SC2450 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-17: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-18: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-19: SC614 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001 CDMA SC Products System Resource Guide (CSSRG)
1-12 2-18 2-24 2-26 2-30 2-51 2-53 2-60 2-65 3-7 3-17 3-18 3-28 3-29 3-32 3-33 3-35 3-35 3-37 3-39 3-39 3-42 3-44 3-44 3-45 3-46 3-47 3-49
v
List of Tables
continued
Table 3-20: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-21: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-22: SC611 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-23: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-24: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-25: SC300 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-26: BTS Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-27: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-28: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-29: SC4840 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-30: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-31: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-32: SC2440 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-33: CDMA Carrier Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-34: Physical Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-35: SC340 Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-36: Pilot Beacon Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-37: Pilot Beacon Operating Frequencies . . . . . . . . . . . . . . . . . . . . . . . . Table 5-1: OMCR Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-2: UNO 2.2 Planning Recommendations . . . . . . . . . . . . . . . . . . . . . . . Table 7-1: Guidelines for Maximum Limit of Conversation Erlangs . . . . . . . . Table 7-2: Guidelines for Walsh Code Erlangs Maximum Limits . . . . . . . . . . . Table 7-3: Guidelines for Walsh Code Usage Maximum Limits (in minutes) . . Table 7-4: Guidelines for Walsh Code Usage Planning Limits (in minutes) . . . Table 7-5: Example Spreadsheet to Forecast WC Usage . . . . . . . . . . . . . . . . . . Table 7-6: Paging Message Type Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-7: Slot Cycle Index Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-8: Cell Radius to PamSz (up to 60 km maximum) . . . . . . . . . . . . . . . . Table 7-9: Access Message Type Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-10: Paging Channel Workload Model Scenario . . . . . . . . . . . . . . . . . . . Table 7-11: pmC_10 Records, General Data . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-12: pmC_10 Records, Origination Data . . . . . . . . . . . . . . . . . . . . . . . . Table 7-13: pmC_52 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-14: pmC_70 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-15: pmC_10 Records, General Data . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-16: pmC_10 Records, Termination Data . . . . . . . . . . . . . . . . . . . . . . . . Table 7-17: pmC_10 Records, Registration Data . . . . . . . . . . . . . . . . . . . . . . . .
vi CDMA SC Products System Resource Guide (CSSRG)
3-50 3-50 3-51 3-52 3-52 3-54 3-55 3-57 3-58 3-59 3-61 3-61 3-63 3-63 3-64 3-66 3-67 3-68 5-4 5-19 7-6 7-7 7-7 7-12 7-14 7-35 7-37 7-39 7-41 7-48 7-52 7-52 7-54 7-55 7-57 7-57 7-59
June 2001
Table 7-18: pmC_52 Record for ADDS Page . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-19: pmC_52 Record for Feature Notification . . . . . . . . . . . . . . . . . . . . Table 7-20: pmC_52 Records for Shared Secret Data Update . . . . . . . . . . . . . . Table 7-21: pmC_20 Records for Base Station Challenge . . . . . . . . . . . . . . . . . Table 7-22: pmC_52 Records for Unique Challenge . . . . . . . . . . . . . . . . . . . . . Table 7-23: Paging Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-24: Access Channel Slots per Hour/Halfhour versus PamSz . . . . . . . Table 7-25: Access Channel Workload Model Scenarios . . . . . . . . . . . . . . . . . . Table 7-26: pmC_10 Records for ADDS Page Ack . . . . . . . . . . . . . . . . . . . . . . Table 7-27: pmC_20 Records for Authentication Acknowledgements . . . . . . . Table 7-28: Access Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-29: Projected Paging Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . Table 7-30: Projected Access Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . Table B-1: Erlangs per Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table B-2: Erlang B Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table C-1: Erlangs per Blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table C-2: Erlang C Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-62 7-64 7-65 7-66 7-66 7-67 7-69 7-71 7-73 7-73 7-74 7-80 7-81 B-1 B-13 C-1 C-13
June 2001
vii
List of Tables
continued
Notes
viii
June 2001
Product Information
Model Chart
This table provides model numbers, descriptions of model numbers and the quantity of each kit for Product XYZ.
Model Complement For Product A Models X, Y, Z Model Description Quantity
Options
Specifications
The following tables list general, receiver and transmitter performance specifications for Product XYZ.
General Specifications for Product A Specification Description
June 2001
ix
Foreword
Scope of manual This manual is intended for use by cellular telephone system craftspersons in the day-to-day operation of Motorola cellular system equipment and ancillary devices. It is assumed that the user of this information has a general understanding of telephony, as used in the operation of the Public Switched Telephone Network (PSTN), and is familiar with these concepts as they are applied in the cellular mobile/portable radiotelephone environment. The user, however, is not expected to have any detailed technical knowledge of the internal operation of the equipment. This manual is not intended to replace the system and equipment training offered by Motorola, although it can be used to supplement or enhance the knowledge gained through such training. Text conventions The following special paragraphs are used in this manual to point out information that must be read. This information may be set-off from the surrounding text, but is always preceded by a bold title in capital letters. The four categories of these special paragraphs are: NOTE Presents additional, helpful, non-critical information that you can use.
IMPORTANT
Presents information to help you avoid an undesirable situation or provides additional information to help you understand a topic or concept.
CAUTION Presents information to identify a situation in which equipment damage could occur, thus avoiding damage to equipment.
WARNING Presents information to warn you of a potentially hazardous situation in which there is a possibility of personal injury. . . . continued on next page
x CDMA SC Products System Resource Guide (CSSRG) June 2001
Foreword continued
The following typographical conventions are used for the presentation of software information:
S In text, sans serif BOLDFACE CAPITAL characters (a type style S In text, typewriter style characters represent prompts and the
system output as displayed on an operator terminal or printer.
without angular strokes: i.e., SERIF versus SANS SERIF) are used to name a command.
Foreword continued
Reporting manual errors In the event that you locate an error or identify a deficiency in your manual, please take time to write to us at the address above. Be sure to include your name and address, the complete manual title and part number (located on the manual spine, cover, or title page), the page number (found at the bottom of each page) where the error is located, and any comments you may have regarding what you have found. We appreciate any comments from the users of our manuals. 24-hour support service If you have any questions or concerns regarding the operation of your equipment, please contact the Customer Network Resolution Center for immediate assistance. The 24 hour telephone numbers are: Arlington Heights, IL . . . . . . . . . . Arlington Heights, International . . Cork, Ireland . . . . . . . . . . . . . . . . . Swindon, England . . . . . . . . . . . . . 800-433-5202 +1847-632-5390 441793565444 441793565444
xii
June 2001
General Safety
Remember! . . . Safety depends on you!! The following general safety precautions must be observed during all phases of operation, service, and repair of the equipment described in this manual. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture, and intended use of the equipment. Motorola, Inc. assumes no liability for the customer s failure to comply with these requirements. The safety precautions listed below represent warnings of certain dangers of which we are aware. You, as the user of this product, should follow these warnings and all other safety precautions necessary for the safe operation of the equipment in your operating environment. Ground the instrument To minimize shock hazard, the equipment chassis and enclosure must be connected to an electrical ground. If the equipment is supplied with a three-conductor ac power cable, the power cable must be either plugged into an approved three-contact electrical outlet or used with a three-contact to two-contact adapter. The three-contact to two-contact adapter must have the grounding wire (green) firmly connected to an electrical ground (safety ground) at the power outlet. The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards. Do not operate in an explosive atmosphere Do not operate the equipment in the presence of flammable gases or fumes. Operation of any electrical equipment in such an environment constitutes a definite safety hazard. Keep away from live circuits Operating personnel must:
Use caution when exposing or handling the CRT Breakage of the CathodeRay Tube (CRT) causes a high-velocity scattering of glass fragments (implosion). To prevent CRT implosion, avoid rough handling or jarring of the equipment. The CRT should be handled only by qualified maintenance personnel, using approved safety mask and gloves. Do not substitute parts or modify equipment Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola Warranty and Repair for service and repair to ensure that safety features are maintained. Dangerous procedure warnings Warnings, such as the example below, precede potentially dangerous procedures throughout this manual. Instructions contained in the warnings must be followed. You should also employ all other safety precautions that you deem necessary for the operation of the equipment in your operating environment. WARNING
Dangerous voltages, capable of causing death, are present in this equipment. Use extreme caution when handling, testing, and adjusting .
xiv
June 2001
Revision History
Manual Number 68P09298A50A Manual Title CDMA SC Products System Resource Guide (CSSRG) CDMA SC Products System Resource Guide (CSSRG) Version Information The following table lists the manual version, date of version, and remarks on the version. Version Level O A Date of Issue December 2000 June 2001 Original. Revised version. Remarks
Cellular Manual Revision Information The following table lists Cellular Manual Revision (CMR) number, date of CMR, and remarks on the CMR. Revision Level CMR No. Date of Issue Remarks
June 2001
xv
Patent Notification
Patent numbers This product is manufactured and/or operated under one or more of the following patents and other patents pending:
4128740 4193036 4237534 4268722 4282493 4301531 4302845 4312074 4350958 4354248 4367443 4369516 4369520 4369522 4375622 4485486 4491972 4517561 4519096 4549311 4550426 4564821 4573017 4581602 4590473 4591851 4616314 4636791 4644351 4646038 4649543 4654655 4654867
4661790 4667172 4672657 4694484 4696027 4704734 4709344 4710724 4726050 4729531 4737978 4742514 4751725 4754450 4764737 4764849 4775998 4775999 4797947 4799253 4802236 4803726 4811377 4811380 4811404 4817157 4827507 4829543 4833701 4837800 4843633 4847869 4852090
4860281 4866710 4870686 4872204 4873683 4876740 4881082 4885553 4887050 4887265 4893327 4896361 4910470 4914696 4918732 4941203 4945570 4956854 4970475 4972355 4972432 4979207 4984219 4984290 4992753 4998289 5020076 5021801 5022054 5023900 5028885 5030793 5031193
5036515 5036531 5038399 5040127 5041699 5047762 5048116 5055800 5055802 5058136 5060227 5060265 5065408 5067139 5068625 5070310 5073909 5073971 5075651 5077532 5077741 5077757 5081641 5083304 5090051 5093632 5095500 5105435 5111454 5111478 5113400 5117441 5119040
5119508 5121414 5123014 5127040 5127100 5128959 5130663 5133010 5140286 5142551 5142696 5144644 5146609 5146610 5152007 5155448 5157693 5159283 5159593 5159608 5170392 5170485 5170492 5182749 5184349 5185739 5187809 5187811 5193102 5195108 5200655 5203010 5204874
5204876 5204977 5207491 5210771 5212815 5212826 5214675 5214774 5216692 5218630 5220936 5222078 5222123 5222141 5222251 5224121 5224122 5226058 5228029 5230007 5233633 5235612 5235614 5239294 5239675 5241545 5241548 5241650 5241688 5243653 5245611 5245629 5245634
5247544 5251233 5255292 5257398 5259021 5261119 5263047 5263052 5263055 5265122 5268933 5271042 5274844 5274845 5276685 5276707 5276906 5276907 5276911 5276913 5276915 5278871 5280630 5285447 5287544 5287556 5289505 5291475 5295136 5297161 5299228 5301056 5301188
5301353 5301365 5303240 5303289 5303407 5305468 5307022 5307512 5309443 5309503 5311143 5311176 5311571 5313489 5319712 5321705 5321737 5323391 5325394 5327575 5329547 5329635 5339337 D337328 D342249 D342250 D347004 D349689 RE31814
xvi
June 2001
CDMA SC Products Expansion Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Expansion Planning Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Capacity Engineering Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
Table of Contents
continued
Notes
June 2001
Introduction
Because its the natural progression of a wireless system to expand over time, the Systems Engineer needs current, and pertinent, information covering various aspects of system expansion planning. Increased traffic demands are a function of new subscribers being added to the network and of the greater usage of the subscribers. This increased traffic demand drives the requirement for more physical hardware to be installed in the system. The added equipment not only supports the additional voice connections required but also supports the increase of call processing messaging that results due to the additional traffic. Additional RF coverage is a function of increasing service area of the wireless system. This increase in service area can take the form of:
S S S S
Providing RF inside of buildings Increasing the boundaries of the wireless system Providing coverage in tunnels Providing coverage in parking garages.
An additional aspect is migrating the system from one that was designed initially for vehicular use to one that now provides for overall better inbuilding penetration. The result of this additional RF coverage typically takes its form as additional cell sites. These cell sites can take the form of macro cells, micro cells, or repeaters. Each network element (Base Transceiver Station, Base Site Controller, Mobile Switching Center, Home Location Register, etc.) can be impacted with an increase to the traffic or RF coverage. The Systems Engineer needs to examine each of the network elements to determine if it is sized sufficiently to support the new demands or if additional equipment is required. Additional equipment can take the form of:
S S S S
Additional card(s) Additional cage(s) Additional frame(s) Additional network element(s) (BTS, BSC, MSC, etc.).
As traffic increases, additional voice channels are required at the BTS. One of the first steps in expansion is to add additional channel elements. In a CDMA system, an additional carrier is required at stages of the systems development. If the additional equipment is not installed in the system and subscriber traffic keeps increasing, the system experiences excess blocking. Excess blocking can cause many system problems. For instance, a subscriber unit may be unable to place or receive a call because there are no voice channels available or the subscriber may attempt to access the system several times before a voice channel is assigned. Another potential problem involves a situation where a call is dragged into a nonoptimum RF area because there are no channels available in
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-1
the desired target cell. This may cause an increased amount of dropped calls. Since the subscriber is outside of its preferred site of service, the subscriber is most likely at its full power and therefore increases the noise in the nearby vicinity. Since the subscriber is closer to an adjacent site and operating at full power, it is more likely to cause interference (uplink). As a system grows from one to two to three carriers, etc., the Erlang capacity of each site increases (for example, from eighteen to thirtysix to fifty four Erlangs, respectively). If one assumes that the initial system started with ten sites, each offering eighteen Erlangs, the CBSC would need to be able to support 180 Erlangs. If the second carrier is added to all ten sites, the CBSC now needs to support 360 Erlangs. As more carriers are installed at each BTS, the CBSC needs to expand. There comes a point where the processing and port capabilities of the CBSC will be exceeded. At this point, another CBSC needs to be added to the network. The MSC is also impacted with the additional traffic load. Like the CBSC, there comes a point where the processing and port capabilities of the MSC will be exceeded. At this point, another MSC needs to be added to the network. Other items also need to be considered as the system grows, such as:
S S S S
Leased T1 facilities Increased equipment power demands Operation and maintenance support Subscriber database management, billing, statistics, etc.
Plan for Growth The big question is this: When does the engineer/operator know that the system needs to expand? If the BTSs are beginning to block or shed traffic (assuming that hardware failures are not causing an overload condition), the operator has waited too long because some amount of potential revenue has been lost. The system operator needs to anticipate the growth of the wireless market and stay several steps ahead of the subscriber demands. Ongoing projections of the wireless system growth should be made on a periodic basis. The speed at which the system is growing has some correlation to how often the periodic projections should be done. Marketing Projections The wireless systems marketing team may have projections on the number of subscribers to which they intend to provide services. In addition, they should have an understanding of how these subscribers use the wireless service. Other factors that the marketing team can provide include information on whether the provider is planning a marketing blitz or if buying incentives for the consumer are going to be offered to entice subscribers to sign on at a faster rate. This could
1-2 CDMA SC Products System Resource Guide (CSSRG) June 2001
drastically impact the time available to order, install, and test any new equipment to support future growth requirements. The marketing team may also be able to provide information concerning requirements for any change to the area of wireless service. For instance, new BTS(s) may be necessary if a new subdivision or shopping mall is being built and the area currently has inadequate signal levels. Another situation might involve the improvement of coverage within specific buildings. Statistics The System/Traffic Engineer monitors the system statistics to judge when additional capacity is needed at a cell site. With the goal of expanding the system in mind, the statistics need to be viewed from a growth perspective and not for troubleshooting. Unusual data should be filtered out so the projections wont be flawed. For example, an accident occurring in a given cells coverage area may cause an increase in traffic. Holidays, conventions, or other events also tend to skew the statistics and the judgement of the engineer, if not properly addressed. Adjustments should also be made for seasonal variations. For instance, the summer months may show less traffic than the fall months. New subdivisions, office complexes, or newly builtup areas need to be examined in order to:
S Ensure that RF coverage is available S Determine the impact on the traffic requirements.
Much care needs to be taken when reviewing system statistics so as not to arrive at erroneous conclusions. For instance, faulty equipment may be a factor in misrepresenting traffic location. Traffic seen on a given cell may best be served by another site if that other site was operating properly. Examples of one site not operating properly include:
S Misaligned antennas S Power out of the site is not correct S Some channel elements are out of service.
The coverage, capacity, or quality of a nonoptimal site may be reduced and therefore require the assistance from a neighboring site. Customer Complaints Customer complaint reports can be filtered for issues which identify areas where coverage is desired but is not currently available. This is one indication of where a new cell site might be required. Customer complaints can also show areas where blocking is occurring. The statistics should indicate the specific cell/sector where the blocking is occurring, but the customer complaint reports may give a better indication of where the users are located within the sector. If all of the complaints are in a given area within the cell, this may indicate the need for:
S Desired grade of service for the wireless system S Usage pattern of the average subscriber S Existing traffic capacity of each site.
Using the appropriate traffic measurement data, the Systems Engineer has the ability to predict the time progression of a systems growth and can therefore predict when various capacity limitations will be reached. The overall system should not be viewed as one entity but rather, individual network elements should be reviewed to predict the amount of additional traffic each can support prior to exhausting its resources. For instance, one cell site may already be blocking calls. Another cell sites resources may be under utilized and far below its traffic capacity threshold. The following summarizes the minimum requirements needed for generating a growth plan for a system. This data is used for predicting the amount of channels and cell sites needed to accommodate a given number of subscribers and only addresses the capacity requirement. RF coverage and interference in the system can be addressed if additional information is supplied for each cell site (RF link budget, antennas, height, etc.).
1-4 CDMA SC Products System Resource Guide (CSSRG) June 2001
Minimum Information Requirements for Capacity Planning The following are minimum capacity planning requirements: S Present quantity of cell sites. S Present configuration of site (omni or sector). S Present quantity of channels equipped and CDMA carriers persite or persector. S Location of cell sites The general location and relation of each cell is required if propagation studies are not being done. S Present quantity of subscribers. S Predicted quantity of subscribers (on a monthly basis) for growth periods out to six months minimum; one year to two year projections are preferred. S Present traffic for each cell and/or sector Determine if this traffic is from the busy or low usage period. S Any special requirements of the customer: Grade of service for which to design. Which traffic model to use (for example, Erlang B and Erlang C) Assumes linear growth throughout the system unless otherwise specified. S Spectrum availability, if additional carriers are to be considered. Traffic load projections are absolutely necessary for predicting system capacity. If a service provider delays an expansion effort until the system exhibits a degradation in system performance and/or blocking, a significant amount of revenue may be lost as a result of blocked calls and/or churn. Projections are required to allow time to properly plan for a system expansion. Time needs to be allotted for the following: S Plan and engineer the expansion S Order and obtain the necessary equipment S Obtain the space/building (including necessary permits and licensing) S Order and install the facilities S Install, test, and optimize the equipment. Implementation Proper implementation of the new equipment is essential for optimum performance of a wireless system. Implementation can involve hardware (ensuring proper bolt down, grounding and cabling, as well as calibration of the equipment, etc.) and software. The system administrator needs to ensure that cell sites are added appropriately to the MSC and Centralized Base Station Controller (CBSC) databases and that all necessary database updates are made to other sites which may be impacted. Impacts to other sites include changes to neighbor lists. Too few of neighbor sites can cause dropped calls due to no neighbor cell available to accept the handoff.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-5
Introduction
The CDMA SC Products System Resource Guide (CSSRG) provides Systems Engineers with information on:
S S S S S
What these resources are How to monitor resource utilization Possible actions which may reduce that utilization Impacts of many significant features Growth planning.
This information allows the engineer to identify which resources may limit the capacity of the system, and those which may be near overload or have already been overloaded. The CSSRG contains seven chapters and three appendices:
S S S S S S S S S S
Introduction Centralized Base Station Controller (CBSC) Base Transceiver Station (BTS) Intelligent Network (IN) Operations and Maintenance Data Services CDMA RF Carrier Appendix A CDMA Call Flow Appendix B Erlang B Tables Appendix C Erlang C Tables.
The guide provides guidelines for managing system expansion. It describes considerations to be made when additions and changes are needed for a growing system.
1-6
June 2001
Introduction The following describes a generic capacity engineering strategy to use for all of the network elements covered by the CSSRG. The basic premise to this strategy involves an analysis of traffic measurements and utilization measurements that can reasonably determine the busy period statistical traffic values, and the sensitivity of the network element utilization to carried traffic. Current network utilization combined with market estimates of traffic or subscriber growth can be used to estimate future network element utilization. A comparison of current and/or future estimated network element utilization with the maximum specified limits determines when this network element will reach its operating limits with respect to growth. Traffic Environment Figure 1-1 provides a functional block diagram of a typical CDMA network. Each network element consists of subsystems that are sensitive to carried traffic. In a cellular/PCS network, carried traffic may consist of multiple traffic variables that have varying degrees of correlation to each other. For example, during a given observation period, the number of handoffs correlates highly to the number of call attempts while the number of registrations has little correlation to the number of call attempts. An environment with highly correlated multiple traffic variables lends itself to a simpler characterization between network element utilization and one of the dominant traffic variables. Network Element and Traffic Capacity A typical network element has different subsystems designed to handle different subsets of the offered traffic. Examples of trafficsensitive subsystems include:
S S S S S S S
Processors Signaling links Trunks I/O buses Memory and storage Switch fabrics Transcoders.
An example of a nontraffic sensitive subsystem is the clock subsystem. Each subsystem may be sensitive to different constituent components of the carried traffic. Some subsystems are sensitive to event traffic, some are sensitive to Erlang traffic, and some are sensitive to both types of traffic. Consequently, internal measurements and capacity engineering models differ between subsystems. The differences in engineering models between subsystems include the:
Voice Signaling/Data/Control
Network Communication
Common Control
Administration
Tandem HLR
Application Processing
Disks
Network Communication
CBSC
TO OMC-R MM
Mobility (Radio)
XC Selector / Vocoder
CDMA BTS
ANALOG BTS
Capacity Engineering Approach The capacity engineering strategy described here provides a means to determine the:
S S S S
1-8
Traffic carried by each network element Current level of utilization for each network element Sensitivity to traffic growth for each network element A process for estimating future utilization with traffic growth.
June 2001
Given these results, it is then an easy matter to determine which network element is currently limiting offered traffic and which might limit traffic growth in the future. A key point to be repeated is that the upper limits of a network resource, as stated in terms of carried traffic, may be different for other network elements of the same type due to the different intensity levels of traffic subcomponents in each network element and differences in traffic sensitivity functions. The result is that similar types of network elements may limit at different traffic levels due to these traffic component pattern differences. As such, it is critical to actually determine the traffic sensitivity of each network element to the traffic actually occurring in that network element and to define what is meant by measured traffic levels. This strategy uses the concept of statistical traffic busy periods, requiring analysis of carried traffic in a network element measured many times during the observed day and for a sufficient number of observed days to get a reasonable sample of traffic levels. Overview of a Six Step Capacity Engineering Strategy The following provides a generic six step capacity engineering strategy that can be applied towards capacity engineering for each type of network element. The six steps are: 1. Collect traffic and network element utilization data 2. Determine present status Analyze traffic sensitivity using least squares method and determine busy period traffic intensity statistics 3. Forecast utilization Calculate estimated future utilization based upon market growth estimates, traffic sensitivity, and current busy period traffic intensity statistics 4. Identify current and future network elements that exceed or will exceed maximum specified utilization limits 5. Evaluate relief alternatives 6. Implement appropriate relief alternative(s). Each of the strategys six steps are described in further detail with a procedure or guideline for each step. General notes are included to aid in understanding the use of the procedures and guidelines. Figure 1-2 provides a flow diagram summarizing the procedures and guidelines used in each step of the strategy.
June 2001
1-9
Determine Load Line Analysis (LLA) parameters (Method of Least Squares linear function) according to equation U = a + bx, where: U is level of utilization a is idle level (yintercept) param b is traffic sensitivity param (slope) x is traffic level
Determine busy period traffic stats: Busy period Hour/Day/Week/Season Busy period attempts per subscriber (Batt/Ns) Average and standard deviation of busy period attempts per subscriber.
Forecast utilization:
Determine: Number of Subscriber (Ni) for a particular month Calculate average busy period traffic for month (i) by multiplying Batt/Ns*Ni Create utilization forecast: Average busy period traffic for month (i) applied to Least Squares function estimates future utilization.
Identify bottlenecks: Evaluate results: Identify elements that exceed limits in engineering period
Deploy alternative:
Implement solution(s)
Solve capacity problems by evaluating solutions: Reduce traffic to element Balance traffic between elements Upgrade element(s) Add element(s)
Collect data and network element utilization data The following generic data collection procedure applies to each network element: S Identify the data to be collected.
Determine collection intervals and start times Use this to specify traffic and utilization measurement periods. Which periods are specified depends on whether the measurements being performed are for an initial baseline or for ongoing observations. Measurements for an initial baseline typically include a broader set of data as to characterize busy periods over time. Measurements for ongoing observations, where busy period characteristics are already known, typically include samples from those busy periods. Cellular traffic statistics may not be stationary over a onehour period and, as such, it is recommended, wherever possible, to take traffic and utilization measurements over a onehalf hour period, rather than a onehour period. The busy period is therefore ideally a onehalf hour period. Collect the data according to determined times Use this to systematically collect data to reveal the (at least) Daily Busy Period and Busy Day. Typically ten or more calendar days are required. Table 1-1 provides a collection schedule template for systematically collecting the data. This data is used in Busy Period Traffic Analysis described in the following Determine present status topic. It is important to collect traffic measurements for all traffic variables that can load the given network element and to collect enough periods throughout the day to ensure subsequent capture of the busy period for each traffic variable as well as the busiest period for network element utilization.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-11
Busy week, busy month, and busy season are important as well, but these items might not be readily distinguishable in rapidly growing systems unless normalization calculations are made. Normalization calculations are made by dividing dominant traffic intensity busy period values by the population of subscribers offering the traffic during the observation period. Table 1-1: Template for Typical Measurement Schedule Hour 00 03 04 05 09 10 11 12 14 15 16 17 18 19 20 21 Adjust collection according to observed measurements In networks where busy periods are known, data is collected to monitor traffic patterns and to identify the most likely overloaded situations. These periods are determined following Busy Period Traffic Analysis described in the following Determine present status topic. Changes detected in traffic patterns indicate the potential for uncharacterized loading. In this case, a new baseline may need to be established. Determine present status This step utilizes the data collected from the previous step to determine two very important results: the traffic sensitivity function parameters and the busy period statistics. The following generic data collection procedure applies to each network element: S Validate the data
1-12 CDMA SC Products System Resource Guide (CSSRG) June 2001
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Record data points for each measurement period Determine network elements traffic sensitivity Analyze busy period traffic Determine traffic correlation Calculate the regression line for each network element.
Validate the data Validation of the collected data is important to assure consistent statistics for all of the traffic variables that are available for the measurement period. Missing or incomplete traffic data for a specific period should not be counted in the busy period statistical analysis. Furthermore, the data should be checked for any unusual traffic loading or utilization values that may be indicative of environmental changes, such as administrative actions, restarts, or failures. This may invalidate the data for normal operation predictive purposes. Any special indications regarding incentives, etc., that may make the data deviate from normal traffic environments should also be considered as abnormal traffic environments that are not useful for future traffic estimates. The suspect data can be removed from the data to be analyzed if this special situation is not considered to be part of the normal traffic environment. Nevertheless, try to determine the reason for any suspect data values before discarding them since this data may represent a new traffic pattern or a recurring pattern (such as, afternoon sporting events, concerts, etc.). Record data points for each measurement period For each measurement time period, record data points that compare network element utilization versus traffic. If using a spreadsheet, create a column for the each traffic measurement variable and create a column for the measured utilization or calculated utilization. The rows then represent the set of values for each measurement period, traffic and utilization. Ideally, the capacity of a given network element is sensitive to a single traffic variable. For instance, the EMXs Common Channel Manager (CCM) processor is sensitive to call attempts at the switch. In these cases, single variable models sufficiently describe the relationship between capacity and load. Frequently, a given network element is sensitive to a set of traffic variables rather than just a single variable. Also, in these cases, multivariable models better describe the elements capacity/load relationship. Multivariable models require measurement and statistical analysis of each traffic variable as well as statistical analysis of the aggregate of traffic variables comprising the elements load. Many procedures in this document are based on singlevariable models; those procedures based on multivariable models are noted. Determine network elements traffic sensitivity The Busy Period Traffic Analysis is very dependent upon the network operators operations engineering objectives and performance objectives. There are a number of busy period statistical analysis techniques that can
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-13
be used that are more or less conservative in their calculation of average busy period traffic. The two most commonly used are the Time Consistent Busy Hour Analysis and Bouncing Busy Hour Analysis. To determine the time consistent busy period, calculate the average across all the observed days for each time period. The time period with the highest average is termed the busy hour for this study. Also, calculate the standard deviation of these values. To determine the bouncing busy period, find the time period for each day with the highest traffic value. Calculate the average across all of these traffic values. In addition, calculate the standard deviation of these values. Another variant of these two approaches is to consider the use of only the highest traffic days of the analysis period and then perform an analysis only for these days. Ultimately, the choice of approach is up to the network operator. The average busy period traffic values, when divided by the number of subscribers, define the average busy traffic levels per subscriber and can be used for estimating traffic growth from subscriber growth. The average busy period traffic, when plotted against the utilization traffic sensitivity curve, defines the current baseline traffic and utilization point of operation for engineering purposes. If the busy period utilization value is near the maximum specified limit, the network element requires capacity relief. NOTE Normal operation may not be guaranteed and is dependent on the congestion relief mechanism(s) being activated.
Analyze busy period traffic If the data is to represent baseline measurements for the network, busy period analysis should be performed first to determine the periods most likely for overload situations. Here, additional correlation analysis is performed to determine the dominant traffic variables loading the network element under study. For data representing an observational busy period, an analysis is performed to assure that stress periods remain constant. Correlation analysis for this data assures that uncharacterized traffic variables have not changed the pattern for the traffic load on the network element. If uncharacterized variables are detected, the network measurements should be baselined again. New baseline measurements are not necessary if the busy period changes but the traffic pattern has not. The results of the above analyses are used to determine subsequent data collection. Determine traffic correlation Next, the pairwise correlations coefficients, or Pearson Product Moment Correlation Coefficients, for each pair of traffic variables should be calculated. Equation 11 shows the calculation made to
1-14 CDMA SC Products System Resource Guide (CSSRG) June 2001
determine the Pearson Product Moment Correlation Coefficient (commonly referred to as the sample correlation coefficient). A good statistics book describes the linear least squared regression calculations to derive correlation coefficient. Commercially available spreadsheets also provide functions that will compute this value for the supplied data pairs. xi yi (xi yi ) / n rxy = p x2i (xi )2 / n Where: xi is the value of the x variable for the ith observation yi is the value of the y variable for the ith observation n is the total number of observations. Correlation values greater than 0.9 for each traffic variable with the dominant traffic variable indicate sufficient confidence for using a singlevariable linear regression line through the data points (in other words, the scatter chart showing utilization versus the single dominant variable). For correlation values less than 0.9, revalidate the data to verify that there is not some abnormal situation causing the low correlation value. If the data appears accurate, a multiplevariable regression line should be used, and its parameters for each traffic variable should be calculated. Calculate the regression line for each network element The following calculates the parameters of a linear least square function. In a graphical sense, a linear line is drawn through a scatter diagram plotting utilization versus the dominant traffic variable, typically call attempts. The expression for the regression line is U(x) = a + bx, where the parameters a and b are statistically calculated from the data pairs of utilization and corresponding traffic values for each measurement period. Refer to the following equations. Slope Calculation xi yi (xi yi ) / n b= x2i (xi )2 / n yintercept Calculation a = y bx Where: x is the mean (average) value of all the x points y is the mean (average) value of all the y points.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-15
[EQ 11]
p y2i (yi )2 / n
[EQ 12]
[EQ 13]
Any good statistics book describes the linear least squared regression calculations to derive the slope and yintercept of the above function. Commercially available spreadsheets also provide functions that will compute these parameters for the supplied data pairs. Forecast utilization The following requires an additional set of data to be able to forecast network element utilization. The data required can be obtained from market forecasts of subscriber growth over the planning period. The following generic steps can be followed for each network element: S Determine subscriber growth over the forecast period S Derive traffic growth over the forecast period S Calculate the estimated future utilization S Graph utilization versus growth for the forecast period S Assess the validity of the measurement and the data. Determine subscriber growth over the forecast period Subscriber growth is typically projected on a monthtomonth basis, and is provided by the operator s marketing department. However, in the absence of such market projections, subscriber growth can be approximated from existing baseline data if the number of subscribers in the baseline period is known. The following technique describes how to calculate subscriber growth in this scenario: 1. Divide the average busy period traffic value by the number of baseline subscribers to arrive at the average busy period traffic intensity per subscriber (xb / Nb ). 2. Calculate a threesigma value by adding three standard deviations of the daily average busy period standard deviation value at the baseline date to the average, and then dividing by the number of subscribers. (xb + 3sb ) / Nb [EQ 14]
3. sb is the standard deviation of the daily busy period traffic value. Use this to estimate an upper limit curve and an average curve of utilization versus traffic for growth scenarios. 4. Calculate the future offered average busy period traffic level for each growth date by multiplying the average busy period traffic intensity per subscriber by the number of subscribers for that date in the market forecast. x(i) = (xb / Nb) ( Ni) [EQ 15]
5. Calculate the upper limit traffic growth curve to account for daily busy period variances by multiplying the threesigma average busy period per subscriber intensity levels by the number of subscribers at that growth date. x3s (i) = [(xb + 3s) / Nb] ( Ni) [EQ 16]
1-16
June 2001
6. Do this for each traffic growth date found in the variable i. Derive traffic growth over the forecast period Add the incremental average busy period traffic growth estimate for that growth date to the baseline average busy period traffic growth value. Assume that the variance to average busy period ratio stays the same and calculate the new daily standard deviation values for the growth point, with the following expression: sb / xb = si / xi [EQ 17]
Where sb and xb are baseline standard deviation and average traffic values, respectively, for the busy period. xi and si are the new values for the growth date. Therefore, si = xi( sb / xb) [EQ 18]
Add three times the si value to the new average traffic value to estimate the upper traffic busy period value. Perform this calculation for each traffic growth date. Calculate the estimated future utilization Using the above new average and threesigma traffic values for the growth dates, calculate the future estimated network element utilization for each growth date by use of the utilization traffic sensitivity function, U(x) = a +bx [EQ 19]
Where x is the estimated busy period traffic for each growth date. Graph utilization versus growth for the forecast period Draw a graph with the estimated utilization versus the growth traffic for the average and upper threesigma curve, including the baseline traffic values. Add the upper maximum specified limit to the plot and compare with the growth trend curve. At this point, the technical analysis for the network element under study has been completed. Assess the validity of the measurement and the data A premise underlying the validity of the capacity engineering framework is that the measurement and statistical analysis of current cellular traffic, and the network element average utilization traffic sensitivity parameters calculated in the baseline, provide a reasonable basis for estimating future network utilization under traffic growth conditions. This actually relies on the two assumptions:
June 2001
1-17
Traffic Pattern The capacity engineering framework assumes that the current statistical characteristics are scalable to estimate future statistical values. One example of a scalable characteristic is the average number of call attempts in the busy period. The future average number of call attempts (CA) at a calendar date, T, is the current average CA multiplied by some growth factor, g, raised to the number of growth periods, k, from now to T. This relationship is expressed by the equation. CA(T) = CA(now) * (1 + g) k [EQ 110]
Another example is the daily variance around the busy period average for a traffic variable which is also assumed to be scalable by the growth factor squared, for example, (1+g)2k. A third example under this assumption is that the average proportion of soft handoffs to total call attempts for a CBSC would remain the same. For cases where load is determined by multiple traffic variables, an assumption is made that the average proportions of all traffic event occurrences is constant. In turn, the statistical characteristics of the traffic event pattern are also assumed to remain constant. NOTE Changes in the average pattern can be ignored if the specific direction of change does not significantly affect the network elements utilization.
Traffic Sensitivity Assume that the method of least squares provides an acceptable means to estimate traffic sensitivity parameters for a network element given that these parameter values remain constant over the growth estimation period. Also assume that the network element technology, the software, and the statistical characteristics of the traffic pattern remain the same throughout the growth estimation period. This latter assumption is necessary to simplify the sensitivity model from a multivariable model to a univariate model. Some deviations in the average traffic pattern are acceptable, for the same reasons mentioned previously, since the deviations being considered do not significantly affect network utilization and, therefore, wont affect the traffic sensitivity parameter values. Identify current and future network elements that exceed, or will exceed, the maximum specified utilization limits The following analyzes the growth line curves from the Forecast Utilization topic and determines whether this network element exceeds the maximum specified operating limits in the growth projection period. Those elements that exceed their maximum limits are considered bottlenecks. The following generic steps can be followed for each network element:
1-18 CDMA SC Products System Resource Guide (CSSRG) June 2001
S Identify network elements where, during the analysis period, the trend
line is in the highest category; these elements are the bottleneck(s).
which are already shedding and not allowing new traffic are considered bottlenecks. If corrective action is taken for this network element, then additional capacity for the system is allowed until the next bottleneck occurs. Those elements operating near the recommended maximum limit processor utilization are not bottlenecks at the moment but will become bottlenecks to the traffic growth that they control in the near term. Prioritize bottlenecks according to level of severity versus time In prioritizing the bottlenecks, various aspects need to be considered. Each market may have different strategies for determining which network element to address first. The following are some different items to be considered as an aid in the prioritizing process:
relief mechanisms available for that element. After the individual relief possibilities are determined, a networkwide relief plan can be devised. Generic guidelines for evaluating relief alternatives are as follows:
S Determine suitable capacity relief mechanisms for each bottleneck. S Evaluate and note the anticipated effect of relief of one network
element on the other elements in the network (for example, will upgrading a processor just move the bottleneck to the other end of the link?). NOTE Providing capacity relief to a bottleneck shifts the bottleneck to a different element. Within a network, there will always be a limiting element.
While describing specific relief mechanisms is beyond the scope of this chapter, this step provides an interface point between capacity engineering and network planning. Network planning processes should come into play in cases where the networks topology changes (for example, adding a new network element) to effect capacity relief. Capacity Relief Mechanisms Some reasons why a network element has reached its limit include:
S Suboptimal traffic distribution across network elements S Higher traffic intensities for certain traffic components than were
originally expected
S Insufficient capacity configuration of the network element subsystems S Faulty equipment or inappropriate parameter settings.
A typical sequence of capacity relief steps to consider for a network element is:
S S S S S
Ensure that the network element is functioning properly Decrease traffic to network element Rebalance traffic to network elements Increase capacity of limiting network element Increase network capacity by adding network elements.
The case of adding network elements indicates a change in network topology. At this point, the capacity engineering study becomes part of a broader network planning study. Network Efficiency One reason that a network has reached its capacity limit is that certain proportions of traffic are handled by multiple network elements and, as such, the overall potential network capacity is limited. In these situations, it may be possible to provide capacity relief by network structure modifications, by rerouting traffic, or by rebalancing the
June 2001 CDMA SC Products System Resource Guide (CSSRG) 1-21
offered traffic to network entry elements. In this latter case, no added network elements or additional capacity is required, but only rebalancing of the mapping of offered traffic to the network elements. A capacity engineering effort therefore not only identifies current limiting network elements, but also the mapping between offered traffic and the network element carried traffic. This aids the investigation of any capacity relief alternatives at the network level. A periodic review of the mapping of offered traffic to network element carried traffic and respective network element utilization should be performed to determine the network resource capacity usage efficiency. The highest efficiency occurs when uniform increases in network offered traffic result in uniform increase of network resource utilization and when, on average, the network elements utilization are at similar percentages of their maximum capacity. There are many reasons why this ideal is not possible. Some include nonuniform traffic distribution through the network, uneven offered traffic levels at different network entry points, and different busy periods during the day for different regional traffic sources. Assumptions Regarding Traffic Distribution When evaluating the effect of projected traffic load on the current network, an assumption is made that the distribution (routing) of the projected traffic is similar to the distribution of the measured baseline traffic. However, adding network elements, whether these elements are new or similar to existing elements, requires that the traffic distribution be reevaluated. NOTE As projected traffic load is forecasted, it is typically assumed that all network elements experience the same percentage increase. In fact, it is very likely that one region experiences a higher percentage of traffic load than another region. This produces a different loading effect on those network elements supporting the two different regions.
Adding Similar Network Elements When similar network elements are added, traffic is typically redistributed to balance the load between similar network element types. In this case, an assumption can be made that the new network element added will have the same traffic sensitivity parameters as the average of the current network elements of this type. Adding New Network Elements When new network element types are added, additional traffic may occur on the existing network elements that did not experience this traffic before. This change may then impact the overall network traffic pattern. In this situation, an investigation would have to be made for each network element to determine whether the new traffic that is generated
1-22 CDMA SC Products System Resource Guide (CSSRG) June 2001
by the new network element type could be carried by the existing network elements that support it. In addition, it needs to be determined if a significant change to the carried traffic pattern and/or the traffic sensitivity parameters results. If the traffic variable associated with the new traffic does not have a dominant effect on the network element utilization, then the previous baseline traffic sensitivity parameters can be utilized with confidence. If the traffic variable is a dominant traffic variable for this network element, the new traffic has to be added to this traffic element. It does not necessarily mean that the traffic sensitivity parameters would change if the dominant variable is significantly dominant compared to the other dominant traffic variables. Implement appropriate relief alternative(s) The following establishes schedules and contingencies for the relief mechanisms decided in the Evaluate Relief Alternatives topic. Generic guidelines for implementing relief mechanisms are as follows:
S Identify dates for scheduling the changes. S Identify backup plans for schedule changes. S Make changes according to schedule.
NOTE Making any change to the network requires reevaluation of the processes established in the first five steps of the strategy. Therefore, it is recommended to make changes to the process concurrently with changes in the physical network.
June 2001
1-23
Notes
1-24
June 2001
Centralized Base Station Controller (CBSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility Manager (MM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility Manager (MM) Overload Control . . . . . . . . . . . . . . . . . . . . . Overload Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder Subsystem (XC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CBSC Capacity Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CBSC Capacity Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CBSC Capacity Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1 2-1 2-2 2-2 2-5 2-13 2-14 2-18 2-18 2-22 2-22 2-30 2-30 2-58 2-58
June 2001
Table of Contents
Notes
continued
June 2001
Introduction
The Centralized Base Station Controller (CBSC) is a part of a Base Station System (BSS) and is made up of the following two elements: 1. Transcoder Subsystem (XC) 2. Mobility Manager (MM). The CBSC controls the following functions:
S S S S
When doing growth planning for the CBSC, the first item that must be determined is the capacity limit of the CBSC. Because the Transcoder can be equipped in many different configurations and the MM processing capacity is highly dependent on the call model a System Engineer needs to establish a set of individual CBSC capacity limits for each and every CBSC of an entire system. In order to determine the capacity limit of a CBSC, the engineer needs to determine the individual capacity limits of the MM and the XC, and identify which one of the two elements is the limiting factor. The following sections describe the Transcoder Subsystem (XC) and the Mobility Manager (MM), their components, and how they function. NOTE The information provided in this chapter also applies to a Wireless Access Manager (WAM) of a Wireless Local Loop (WiLL) system.
June 2001
2-1
Introduction
The Mobility Manager (MM), which provides the radio management function for the CBSC, is connected to the:
S Transcoder Subsystem (XC) through a Control Link S Mobile Switching Center (MSC) via an A+ data link.
The MM manages all of the call processing activities for all of the BTSs under its control. This causes the capacity of the MM to be highly dependent upon the Call Model Performance of the system. Limiting Factors CPU processing capacity is the limiting factor of the MM. The CBSC/OMCR Equipment Planning Guide recommends a 70% MM CPU utilization planning limit. It also recommends that the MM not exceed a maximum limit of 85% CPU utilization for a sustained period of time. The current recommendation is to correlate the CPU utilization to carried Erlang traffic, and establish a set of maximum and planning Erlang limits for the MM. Correlating Erlang traffic to CPU utilization takes into account the Call Model Performance of the system, which can be different from system to system, as well as from MM to MM within a system. Use the following approach to determine a planning Erlang limit and a maximum Erlang limit for the MM. Use this approach with any type of MM (in other words, any Helix or PUMA type). The recommended approach to project the Erlang capacity of the MM is to use the following generic Erlang capacity projection equation.
Erlang Limit Equation = (Util_Limit Base_Util)/(BBH_SAR_Util Base_Util) * BBH_Erlangs [EQ 21]
Where: Util_Limit is equal to Chosen MM CPU Utilization limit (70% or 85%) Base_Util is equal to CPU Utilization that doesnt scale with call processing traffic (3%) BBH_SAR_Util is equal to Measured BBH CPU Utilization from the SAR Utility BBH_Erlangs is equal to Measured BBH Erlangs from the MM_UTIL_PERIOD SQL script. The SAR utility and the MM_UTIL_PERIOD script are described in following topics.
2-2 CDMA SC Products System Resource Guide (CSSRG) June 2001
Use the above generic equation, EQ 21, to establish a Maximum Erlang Limit by projecting to a 85% MM utilization which produces the following equation:
Maximum Erlang Limit = (82)/(BBH_SAR_Util 3) * BBH_Erlangs [EQ 22]
Also use the generic equation, EQ 21, to establish a Planning Erlang Limit by projecting to a 70% MM utilization which produces the following equation:
Planning Erlang Limit = (67)/(BBH_SAR_Util 3) * BBH_Erlangs [EQ 23]
Since it is typical to size the MM for peak system usage, its recommended to analyze the performance of the MM during the Bouncing Busy Hour (BBH) for a particular MM. Since the call model performance of a system can vary throughout the day, its important to analyze the MM performance with a typical call model performance during the BBH. As a result, the MM capacity equations utilize BBH data to project the Maximum and Planning Erlang limits. The measured Erlang data thats recommended to use for the MM capacity equations comes from the MM_UTIL_PERIOD SQL script which is designed to estimate MM utilization from existing Performance Measurement (pmC) traffic peg counts. This script was created by a SuperCell System Performance group in order to understand the network loading and provide an accurate account of all of the significant call processing events. It uses pmC peg counts from the Relational DataBase Management System (RDBMS) database and applies a software releasedependent set of work load model algorithms to estimate the utilization for the individual call processing events. The Erlang calculation that the SQL script performs is as follows:
BBH_Erlangs = (peg_count_3 of pmC_71_hr) / 1800 [EQ 24]
OR
BBH_Erlangs = (peg_count_4 of pmC_51_hr) / 1800
Since the data is provided in half hour increments, the data analysis period used for the MM capacity equations is 30 minutes. In the absence of the SQL script being set up to collect the data, the same Erlang data can be produced from the Transcoder Channel Group Report (pmC_71_hr) by using the following calculation for a 30 minute data sample on a perCBSC basis:
BBH_Erlangs = (Group Usage from Transcoder Channel Group Report) / 30 [EQ 25]
NOTE The data in the RDBMS database, from which the SQL script gets its data, is stored in seconds. The Group Usage data displayed from the Transcoder Channel Group Report is derived from the same peg count source but it is displayed in minutes.
June 2001
2-3
The System Activity Report (SAR) data comes from a Tandem UNIX utility which monitors processor utilization and records CPU measurement data in ten minute intervals. There are four fields of data provided for each ten minute interval: S %usr S %sys S %wio S %idle. Since the data analysis period is 30 minutes, it is recommended to take three or four %idle data points for the particular half hour in question and average them together. Subtract this from 100 to get an average MM utilization for that half hour time period:
BBH_SAR_Util = 100 (Avg %idle from SAR for half hour time period) [EQ 26]
To determine the maximum MM capacity, use the 30 minute BBH Erlang data from the SQL script along with the 30 minute BBH averaged SAR data (for the same time period as the Erlang data) and plug it into the Maximum Erlang Limit equation, EQ 22, to get one data point for the analysis. Repeat the above calculations in order to obtain 40 data points which can be averaged together to establish the resultant Maximum MM Erlang Limit. The 40 data points come from four weeks worth of data under the following constraints: S Only BBH data is used S Two 30 minute data points per BBH per day S Use the five busiest days of the week S Exclude any data that is anomalous (in other words, partial or obviously bad data) S Exclude any data that does not conform to normal traffic patterns (in other words, holidays, weekends, outages, etc.). The minimum recommended data set sample is 20 data points from two weeks worth of data. However, the four week sample is preferred. Use the above process to determine the MM planning limit. The only difference is that the Planning Erlang Limit equation, EQ 23, is used instead of the Maximum Erlang Limit equation, EQ 22. Contact Motorola System Engineering for further assistance in determining MM capacity limits. Determining Utilization The MM has the standard Unix System Activity Report (SAR) utility, which provides measured CPU utilization. Refer to the Unix Manual (Man) page for more details on the usage and format of the SAR utility. The data is available on the MM and is typically transferred offplatform on a regular basis for further processing and storage of the data. Planning Limits As shown in the CBSC/OMCR Equipment Planning Guide (EPG), the MM CPU utilization planning limit is 70% and is not to exceed 85% for a sustained period.
2-4 CDMA SC Products System Resource Guide (CSSRG) June 2001
Refer to the previous Limiting Factors section and the following CBSC Capacity Planning section for more information regarding Planning Limits. Symptoms of Resource Overload There are two alarms that are triggered by the MM overload algorithm:
Admission Rate Overload Control Admission Rate Overload Control limits the rate at which the CBSC accepts Call Processing work (in other words, mobile originations, mobile terminations, page requests from the MSC, mobile registrations). Admission rate is calculated by assigning a WEIGHT to each type of Call Processing request. This weight is based on how much CPU unit time this particular request takes on average including future external handovers. There are weights for:
S S S S S
Mobile originations Mobile terminations Page requests from the MSC Mobile registrations Authentication and Feature Delivery (AFD) messages.
Each time one of these requests is processed, the weight for that action is added to the appropriate rate counters. There are three Admission Rate counters:
Every second the Admission Rate Counters are decremented by the appropriate Decrement Step Value. This allows additional requests to be handled every second. The Admission Rate Thresholds prevent the CBSC from accepting too much work in a one second timeframe. By not zeroing out the Admission Rate Counters every second, and using the Decrement Step instead, causes the Admission Rate checks to account for work already accepted in the previous second. This decrement step approach allows the Overload Feature to allow short bursts but is smart enough to detect a continuous overload condition by allowing less work in if the CBSC is overloaded. Originations, page acknowledgements, pages, AFD messages, and registrations each have an individual weight associated with them. Whenever work of these types is accepted into the system, their weights are added to running counters. The running rate counters are maintained by periodically (every second) decreasing each by a configurable amount, as demonstrated in Figure 2-1. Figure 2-1: Admission Rate Control NonOverload Condition
1 second interval
Admission Threshold
Weight
Decrement Step
These counters are then continuously compared against overload thresholds. When a threshold is exceeded, additional work is rejected and alarms set. The counters continue to be decreased every second, potentially allowing new work to be admitted into the system while existing processes are in progress and being completed. Although the counter may drop below the threshold limit, the alarm itself wont clear until the running counters have been continuously below the admission thresholds for a recent changeable number of consecutive one second periods. See Figure 2-2.
2-6
June 2001
1 second interval
Weight
Decrement Step
The Rate Alarm Clear Interval is used by all Admission Rate checks and is used to clear the Admission Rate Overload Alarm. This parameter specifies how many consecutive one second intervals that the specified rate counter must stay below the rate threshold before clearing the alarm. Parameterization Before demonstrating how to successfully incorporate rate overload parameters into the call processing flow, it is necessary to first define all of the involved parameters. In order to display the current system settings, execute the following command from an OMCR CLI session:
OMCR > display cbscx rateovld (where x = cbsc number)
INFO:1 Command Received and Accepted COMMAND=DISPLAY CBSC4 RATEOVLD CBSC # 4 ORIG W 106 PAGEACK W 116 REG W 6 PAGE W 13 CALL DEC 800 CALL T 5040 REG DEC 250 REG T 416 AGG DEC 800 AGG T 5040 CLR INTERVAL 60 SHED PAGE Y AFD W 2 AFD DIST W 2
ORIG W
This is also referred to as OrigWeight. This factor is the estimated average CPU time (in milliseconds) the MM spends on one mobiletoland call, including handoffs during the call. The averaging is done over all mobiletoland calls, both successful and failed. PAGEACK W Page Acknowledgement Weighting Factor This is also referred to as PageAckWeight. This factor is the estimated average CPU time (in milliseconds) the MM spends on one landtomobile call, including handoffs, after a page acknowledgement is received from the BTS (the time spent on the page itself is excluded).
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-7
REG W
This is also referred to as RegWeight. This factor is the estimated average CPU time (in milliseconds) the MM spends on one registration. PAGE W Page Weighting Factor
This is also referred to as PageWeight. This factor is the estimated average CPU time (in milliseconds) the MM spends on one page. CALL DEC Call Decrement Amount
This is also referred to as CallDecStep. This is the amount decremented from the call admission rate counter on a periodic (onesecond) basis. CALL T Call Denial Threshold
This is also referred to as CallAdmThld. This threshold is used to determine when new call requests into the CBSC shall be denied. A call request will be denied if the call admission rate counter is greater than or equal to CALLT when an origination or page acknowledgement arrives. REG DEC Registration Decrement Amount
This number is also referred to as RegDecStep. This number is the amount decremented from the registration admission rate counter on a periodic (onesecond) basis. REG T Registration Denial Threshold
This is also referred to as RegAdmThld. This threshold is used to determine when new registration requests into the CBSC shall be denied. A request will be denied if the registration admission rate counter is greater than or equal to REGT when a registration arrives. AGG DEC Aggregate Decrement Amount
This is also referred to as AggDecStep. This number is the amount decremented from the aggregate call processing admission rate counter on a periodic (onesecond) basis. AGG T Aggregate Denial Threshold
This is also referred to as AggAdmThld. This threshold is used to determine when new call processing requests into the CBSC shall be denied. A request is denied if the aggregate admission rate counter is greater than or equal to AGGT when a new request (origination, page ack, registration or page) arrives. CLR INTERVAL Clear Interval
This is the number of consecutive onesecond intervals that must elapse with the rate counters below their corresponding threshold values before the overload alarm will be cleared. An alarm will not clear until the associated count is below the threshold for the full interval period.
2-8 CDMA SC Products System Resource Guide (CSSRG) June 2001
SHED PAGE Page Message Shedding This field specifies whether page messages from the MSC should be discarded when call shedding is in effect from exceeding the aggregate admission threshold. AFD W Factor Authentication and Feature Delivery Weighting
This factor is the estimated average CPU time (in milliseconds) the MM spends on one authentication and feature delivery message. AFD DIST W Authentication and Feature Delivery Distributed Weighting Factor This factor is the estimated average CPU time (in milliseconds) the MM spends on one authentication and feature delivery message in distributed mode. The decrement steps (CallDecStep, RegDecStep, AggDecStep) set the limits on the average rate at which different types of call processing activities the Mobility Manager admits. Since each process (origination, page acknowledgement, registration, AFD, and page) has its own associated weight value, the decrement steps in effect determine how the load is accepted into the system. The admission threshold parameters (CallAdmThld, RegAdmThld, AggAdmThld), aside from setting the maximum allowable work on the system, also function to manage how bursts of activity are controlled. Using RegAdmThld as an example, the maximum number of registrations contained in a burst that is recognized by the MM is RegAdmThld/RegWeight (assuming that the counters are initially set at zero). From then on, the Mobility Manager acknowledges exactly RegDecStep/RegWeight registrations per second. Decrement steps, as previously explained, establish the rate at which callrelated processes are accepted as load into the MM. These values are also a representation of what is the maximum desired call processing CPU utilization on the Mobility Manager. The following formula demonstrates how to determine the value for AggDecStep:
AggDecStep = maximum desired CPU utilization* overhead utilization*
Where utilization values are represented as the percentage utilization, multiplied by 1000. For example, using 85% as the total maximum utilization and reserving 5% for various overhead, noncall processing related activities on the MM, then:
AggDecStep = 850 50 = 800
In other words, AggDecStep is the maximum CPU load due to call processing that the Mobility Manager admits. It is a general rule to set both AggDecStep and CallDecStep (AGG DEC and CALL DEC) to the same values. To explain this theory, remember that call admission
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-9
threshold (CALL T or CallAdmThld) is a measure of the number of originations and page acknowledgements that come into the system. Aggregate admission rate threshold (AGG T or AggAdmThld) encompasses ALL call processing entities. In order to allow the most emphasis to be placed on actual call activity (originations and terminations), the values for the aggregate variables should equal what is calculated for the callonly parameters. This allows the maximum number of possible calls through the system. The flexibility of the Admission Rate Overload feature offers the ability to lower the call variables to allow for higher paging and registration activity. One important distinction to make is that when the Admission Rate Overload alarms have been triggered, causing some type of activity to be rejected, the only work that is denied is NEW call processing requests. All existing, inprogress activities continue. For example, handoff requests from the mobile are processed normally by the MM, and operations and maintenance commands are still forwarded to and from the BTS devices. In other words, the purpose of properly setting and maintaining the Admission Rate Overload parameters is to guarantee that if/when an overload situation is encountered, current processes are preserved. Refer to the CBSC Capacity Monitoring section and Table 27 for more information on the recommended settings and the monitoring of these settings. Other CPUIntensive Activities Although Admission Rate Overload functions by using a representation of what the MMs maximum desired call processing CPU utilization should be, it is important to remember that fluctuations in the actual utilization will not necessarily trigger the overload mechanism. In other words, the algorithm does not do any realtime measurements on actual Mobility Manager CPU utilization. A System Activity Report (SAR) on the MM may show utilization variances over the recommended 85% maximum usage, but these utilization spikes can also be attributed to other noncall processing related activities on the MM. For example, every Mobility Manager has a cronjob set up (under user scadm) that monitors disk space on the MM. When usage reaches a certain threshold, large Supercell process files are cleared out in order to maintain adequate disk space. BSS System Release 7 introduced improvements to the Supercell process file storage procedure so that the actual amount of stored data is kept to a minimum but, under rare circumstances, it is possible for the file system to fill up. When this happens, CPU time is taken away from call processing and dedicated toward purging the overloaded files. This can potentially cause call processing queues to fill up so that when the file clearing is complete, a burst of pending, new call processing jobs comes into the Mobility Manager. If the burst of activity is great enough, Rate Overload alarms are falsely triggered whereas under normal circumstances the amount of activity is acceptable. Because other file and system maintenance commands, such as compressing large data files, can also falsely trigger the overload mechanism, exercise caution when using these commands.
2-10 CDMA SC Products System Resource Guide (CSSRG) June 2001
Capacity Load Control Capacity Load Control functions by monitoring the quantity of concurrent activities and determining whether accepting new call processing work (originations, page acknowledgements, or registrations) to the Mobility Manager exceeds allowable ceiling thresholds. The number of current registrations and call counts are accumulated in running counters. Once the counters (individually or combined) exceed the associated threshold or ceiling, new activity is rejected. When the inprogress workload decreases by an amount that allows new work into the system without compromising the MMs capabilities, work is again accepted. Although shedding no longer occurs once counter values drop beneath the ceiling and shedding threshold, alarms that are set due an overload condition are not cleared until current counts are adequately beneath the alarm clear threshold. See Figure 2-3. Figure 2-3: Capacity Control Example
Reject Reject Alarm Set
Alarm Clear
Parameterization As with Admission Rate Overload, Capacity Overload has its own associated parameters. To display the current settings, execute the following command from an OMCR CLI session:
OMCR > display cbscx capovld (where x designates the cbsc number) INFO:1 Command Received and Accepted COMMAND=DISPLAY CBSC1 CAPOVLD CBSC CALL (cbsc) ACLR 1 994 CALL SCLR 1024 CALL MAX 1024 REG ACLR 150 REG SCLR 200 REG MAX 200 SHED PAGE Y
Given that Capacity Overload is a more simplified procedure than Admission Rate Overload in that it measures the number of concurrent calls (including both originations and terminations) and registrations, the parameter definitions can be combined since the process behaves the same for both types of call activities.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-11
This is also referred to as Call/RegCeilingAClrT. This threshold clears an overload alarm condition after the maximum allowable number of concurrent calls or registrations has been exceeded. The alarm, once set, persists until the current activity level drops below this clear threshold. CALL SCLR/REG SCLR Call/Registration Shedding Clear This is also referred to as Call/RegCeilingSClrT. This is the threshold that clears shedding after concurrent calls or registrations have exceeded the acceptable amount and new activity is being denied. Once the current counts fall below the callsclr/regsclr values, new work will again be accepted into the system. CALL MAX/REG MAX Call/Registration Maximum
This is also known as Call/RegCeiling. This is the maximum number of simultaneous calls or registrations allowed. Once this has been surpassed, an alarm is set and new work is rejected. SHED PAGE Page Message Shedding.
This field specifies whether or not page messages from the MSC are discarded when call shedding is in effect from reaching the callceiling threshold. Capacity Overload parameters were designed, as Figure 2-3 shows, to alarm and start rejecting new work once the number of current call processing tasks surpass desired values. Once the activity levels fall back below the ceiling (shedding clear) thresholds, new calls and registrations will again be admitted to the system. However, the alarm continues to be active until the call processing operations are sufficiently beneath the alarm clear threshold values. This serves as a warning to the system operator that the CBSC is still running at higher than normal activity levels. In order to make optimum use of the Capacity Overload feature, the following guidelines are observed:
Admission Rate/Capacity Overload Alarms When an Admission Rate/Capacity Overload threshold has been exceeded and new call processing work is being rejected, the CBSC will store statistics on what type and how much work was denied during the overload period. These statistics are reported in two ways: through the Alarm Clear message written to the Event Log, and in the Integrity Report automatically generated every ten minutes (also written to the Event Log). Following are examples of the Aggregate Rate Exceeded alarm and the associated Clear message.
CBSC1 980610 15:01:21 dot61 MM1 A000000.00000 483895/245929 ALARM: 135172 Admission Rate Overload: Aggregate Rate Exceeded ORIGINATIONS_DISCARDED=0 PAGE_ACKS_DISCARDED=0 REGS_DISCARDED=0 PAGES_DISCARDED=0 AFD_DISCARDED=0 AFD_ACK_DISCARDED=0 CBSC1 980610 15:03:13 dot61 MM1 A000000.00000 483927/245984 ALARM: 135172 Admission Rate Overload: Aggregate Rate Exceeded ORIGINATIONS_DISCARDED=3 PAGE_ACKS_DISCARDED=0 REGS_DISCARDED=8 PAGES_DISCARDED=3 AFD_DISCARDED=0 AFD_ACK_DISCARDED=0
**
CLR
There are three types of Admission Rate Overload alarms that can occur:
S Admission Rate Overload: Call Rate Exceeded S Admission Rate Overload: Registration Rate Exceeded S Admission Rate Overload: Aggregate Rate Exceeded.
There are also two types of Capacity Overload alarms that can occur:
S Capacity Overload: Call Ceiling Reached S Capacity Overload: Registration Ceiling Reached.
The example above is for an Admission Rate Overload alarm where the Aggregate Rate threshold was exceeded. All of the Admission Rate Overload or Capacity Overload alarms will look similar to the example above. The differences between the various alarms are the triggering mechanisms that are used to set the alarm. An active alarms corresponding clear indication (CLR displayed) includes statistics on work shed during the alarm period.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-13
The Integrity Report prints out automatically or it can be requested manually using the new GENERATE CBSCx IREPORT command. Use the IRINTERVAL variable, in the EDIT CPPARMS command, to set the Integrity Reporting interval. The interval is in seconds with the current default being set to 600 seconds (10 minutes). A manually requested Integrity Report is a snapshot of what has happened since the last automatic Integrity Report was generated. An Integrity Report details what transpired during that tenminute interval. The structure of the Integrity Report shows which call processing tasks were denied due to either Capacity Overload (ORIGS_DISCARDED_CAP) or Admission Rate Overload (ORIGS_DISCARDED_RATE). Also included are pegs on current activity, as well as the high water marks reached during the time period for various counters. After the Integrity Report has been automatically generated, pegs associated with discarded work, either due to Capacity Overload or Admission Rate Overload, are reset to zero. Maximum activity counters (for example, MAX_AGGREGATE_RATE_CNTR) are set to its current value. Starting in release R7.1, two new counters have been added. These are:
S CURRENT_ICBSC_TGT_TK_COUNT S MAX_ICBSC_TGT_TK_COUNT.
See the following Integrity Report Format section. Starting in release R9, two new counters have been added to the Integrity Report:
2-14
June 2001
Integrity Report Definitions LAST_REPORT_GENERATED This field contains the time when this reporting interval was started. All the fields were reset at that time. MAX_AGGREGATE_RATE_CNTR This field contains the maximum value this counter reached during any one second rate interval in this reporting interval. Evaluate this counter against the aggregate admission rate threshold (AGGT) setting. ORIGS_DISCARDED_CAP This field contains the total number of mobile origination requests discarded during this reporting interval because of an Overload Condition exceeding the Call Capacity limit. PAGE_ACKS_DISCARDED_CAP This field contains the total number of mobile termination requests discarded during this reporting interval because of an Overload Condition exceeding the Call Capacity limit REGS_DISCARDED_CAP This field contains the total number of mobile registration requests discarded during this reporting interval because of an Overload Condition exceeding the Registration Capacity limit. PAGES_DISCARDED_CAP This field contains the total number of page requests from the MSC discarded during this reporting interval because of an Overload Condition exceeding the Call Capacity limit. ORIGS_DISCARDED_RATE This field contains the total amount of mobile origination requests discarded during this reporting interval because of an Overload Condition exceeding the Call or Aggregate Admission Rate limit. PAGE_ACKS_DISCARDED_RATE This field contains the total amount of mobile termination requests discarded during this reporting interval because of an Overload Condition exceeding the Call or Aggregate Admission Rate limit. REGS_DISCARDED_RATE This field contains the total amount of mobile registration requests discarded during this reporting interval because of an Overload Condition exceeding the Registration or Aggregate Admission Rate limit.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-15
PAGES_DISCARDED_RATE
This field contains the total amount of page requests from the MSC discarded during this reporting interval because of an Overload Condition exceeding the Aggregate Admission Rate limit. AFD_ACKS_DISCARDED_RATE This field contains the number of authentication and feature delivery acknowledgements discarded during this reporting interval because of an Overload Condition exceeding the Aggregate Admission Rate limit. AFD_DISCARDED_RATE This field contains the number of authentication and feature delivery messages discarded during this reporting interval because of an Overload Condition exceeding the Aggregate Admission Rate limit. CURRENT_CALL_COUNT This field contains the current number of mobile originations, mobile terminations, and external handovers in progress. Evaluate this counter against the capacity call parameter (CALLMAX, CALLSCLR, CALLACLR). MAX_CALL_COUNT This field contains the maximum number of concurrent mobile originations, mobile terminations, and handovers detected during this reporting interval. Evaluate this counter against the capacity call parameters (CALLMAX, CALLSCLR, CALLACLR). CURRENT_ICBSC_TGT_TK_COUNT This field contains the number of active CDMA interCBSC soft handoff (trunking) target calls. MAX_ICBSC_TGT_TK_COUNT This field contains the high water mark of the number of active CDMA interCBSC soft handoff (trunking) target calls. CURRENT_REG_COUNT This field contains the current number of registrations in progress. Evaluate this counter against the capacity registration parameters (REGMAX, REGSCLR, REGACLR). MAX_REG_COUNT This field contains the maximum number of concurrent mobile registrations detected during this reporting interval. Evaluate this counter against the capacity registration parameters (REGMAX, REGSCLR, REGACLR).
2-16 CDMA SC Products System Resource Guide (CSSRG) June 2001
MAX_CALL_RATE_CNTR This field contains the maximum value this counter reached during any one second rate interval in this reporting interval. Evaluate this counter against the call admission rate threshold (CALLT) setting. MAX_REG_RATE_CNTR This field contains the maximum value that this counter reached during any one second rate interval in this reporting interval. Evaluate this counter against the registration admission rate threshold (REGT) setting. Reducing Utilization/Capacity Improvement Refer to the following CBSC Capacity Management Options section for information on reducing utilization and capacity improvement. Contact Motorola System Engineering for assistance in determining CBSC capacity and the options available for reducing utilization/ capacity improvements.
June 2001
2-17
Introduction
The Transcoder Subsystem (XC), which performs speech encoding and decoding for the Centralized Base Station Controller (CBSC), is connected to the: S Base Transceiver Station(s) (BTS)
S Mobile Switching Center (MSC) S Mobility Manager (MM) through a Control Link S Operations and Maintenance Center Radio (OMCR) through an
Operations Manager Process (OMP) link S Other CBSCs for interCBSC soft handoffs. The XC interfaces the CBSC with the Mobile Switching Center (MSC) and a BTS cluster. Key functions are provided by the following circuit cards: S Transcoder (XCDR)
Table 2-1: Standard Transcoder Maximum and Planning Erlang Capacities Cages 6 6a 6b 8 8 8a 8b 10b 10b 10b 10b 12b 12b 12b 12b XCDRs Per Cage 5 6 7c 4 5 6 7c 4 5 6 7c 4 5 6 7c Total XCDRs 30 36 38 32 40 48 52 40 50 60 66 48 60 72 80 Total Circuits 720 864 912 768 960 1152 1248 960 1200 1440 1584 1152 1440 1728 1920 Maximumd Erlang Limit 659 798 845 706 891 1078 1172 891 1125 1359 1500 1078 1359 1641 1829 Planning e Erlang Limit 593 719 761 635 802 970 1054 802 1012 1223 1350 970 1223 1477 1646
NOTE
a b c d e
Available with R9.2 using DSWs without EGPs Targeted for G15 using DSWs and EGPs First four cages (0 3) have a limit of six XCDRs per cage Maximum Erlang limit calculated using Erlang B at 0.1% Planning Erlang limit calculated to be 90% of the maximum limit As new features become available to expand the capacity of the XC, the CBSC/OMCR Equipment Planning Guide is updated with a new set of standard configurations so that the maximum number of XCDR cards supported with the new configuration again determines the maximum XC capacity limit. Determining Utilization Obtain the total Erlang utilization of the XC for a given time period from the Transcoder Channel Group Report (which is derived from pmC_71_hr peg count 3). To determine the total Erlang utilization, add all the Group Usage time in minutes for all the various channel groups for a given time period. Then divide the total usage by the number of minutes in the given time period. These channel groups are:
June 2001
2-19
The Erlang utilization can also be obtained from the MM_UTIL_PERIOD SQL script (as described in the Mobility Manager (MM) section). Even though processor utilization is not the limiting factor if the standard XC configuration is used, Generic Processor (GPROC) utilization can be measured via TTY port connections. In R9.0 and later, this utilization will be remotely accessible from the OMCR. Planning Limits The recommended Planning Limit for the standard XC is 90% of the maximum Erlang Limit (see Table 2-1 for specific values). Use the Planning Limit in a forecasted growth plan (if the XC is the limiting factor of the CBSC) to determine when capacity relief mechanisms need to be implemented. If circuit and/or packet data hardware is equipped, an additional level of planning for the voice and data Erlangs will be necessary. Separate traffic engineering of the voice and data (circuit and/or packet) traffic usage of the XC must also be performed to properly maintain a desired Grade of Service for each service option. This is in addition to the maximum and planning Limit engineering of the total voice and data usage. Refer to the CBSC/OMCR Equipment Planning Guide and the Data Services chapter of this guide for additional information regarding circuit and packet data planning limits and capacity planning guidelines. The following are required for more detailed XC planning: S Expected Erlang load at the CBSC for: Voice Data InterCBSC soft handoff S Blocking probability at the MSC S The ratio of Busy Hour Call Attempts (BCHA) to CBSC Erlangs S Number of BTSs per CBSC S Total number of BTS span lines at the CBSC S Types of all span lines connected to the CBSC. Refer to the CBSC/OMCR Equipment Planning Guide (EPG) for additional XC subsystem guidelines and information on Planning Limits. Symptoms of Resource Overload Resource Overload can be detected by looking at the PM pegs for Terrestrial Circuit (TerCkt) blocking or from Transcoder Channel Group
2-20 CDMA SC Products System Resource Guide (CSSRG) June 2001
Overflows (pmC_71_hr peg count 2). The Call Failure Class (CFC) field in the Call Data Log (CDL) can also indicate failures. Reducing Utilization/Capacity Improvement Since the standard XC is considered to be hardwarelimited by the maximum number of XCDRs supported, the following options are available to reduce utilization and increase capacity:
June 2001
2-21
Introduction
The steps provided below are intended to provide a Systems Engineer with a set of guidelines for CBSC capacity planning. It utilizes some of the strategies from the Six Step Capacity Engineering Strategy topic to perform capacity management planning. With a CDMA system, CBSC capacity management planning and monitoring is required to be performed on an ongoing basis. Perform and analyze each of the following steps for each individual CBSC in a system: 1. Collect Data to Determine Capacity Limits 2. Determine Present Status 3. Forecast Utilization 4. Identify When Bottlenecks Will Occur 5. Evaluate Relief Alternatives 6. Implement Relief Mechanisms. The analysis should typically forecast out in time, up to one to two years from the present date. Repeat the analysis on a periodic basis. The recommended frequency of performing a growth planning exercise is quarterly, but the frequency can be increased or decreased depending upon how fast the system usage grows. Collect Data to Determine Capacity Limits Determine the CBSC capacity by identifying the limiting factor between the MM Erlang capacity limits and the standard XC Erlang capacity limits. For most standard XC configurations, use Table 2-1 to determine the XC Erlang capacity limits. For a nonstandard XC configuration, determine an estimate of the XC capacity by adding up the total number of circuits provided by all of the XCDRs. Then, calculate the Erlang load that can be supported by these circuits using an Erlang B table with a 0.1% blocking Grade Of Service. This becomes the Maximum Erlang Limit. Calculate the Planning Erlang Limit by using 90% of the Maximum Erlang Limit. Since this is a nonstandard XC configuration, these limits are an estimate of the true limits. This is because it is not known if one of the processor may be limiting the XC to a lower limit. A more detailed procedure to determine the XC capacity for nonstandard configurations wont be covered and is beyond the scope of this guide. Once the XC Erlang capacity limitations are determined, the next step is to collect the data to calculate the MM Erlang capacity limits. As stated earlier, the minimum recommendation is to collect two weeks worth of data but four weeks worth is preferred. Collect SAR data from the MM and Erlang data either from the MM_UTIL_PERIOD SQL script or derived from the Transcoder Channel Group Report (both of which are derived from the pmC_71_hr performance management peg count). If the system supports voice and data, verify that voice, circuit data, and
2-22 CDMA SC Products System Resource Guide (CSSRG) June 2001
packet data are recorded separately and totaled together in to the Erlang data calculation. For initial baseline measurements, the measurement interval for collecting Erlang data should be large enough to capture the bouncing busy hour for each MM. The SAR utilization data should be used to determine the bouncing busy hour for each MM. The busy hour as determined from SAR utilization should typically match the busy hour from the Erlang data. If the bouncing busy hour from the two sources of data do not match, investigate the validatity of the data and/or validate the performance of the MM. Once the bouncing busy hour characteristics for each MM have been established, a smaller window of data collection could be implemented for collecting the Erlang data. Since SAR data is automatically collected for a 24 hour period, seven days a week, no special requirements are needed in order to capture the required bouncing busy hour SAR data. Save the data in a storage location so that it can be processed at a later date. Determine Present Status One of the first things to do is to validate the integrity of the data collected. Investigate partial data or anomalous data and eliminate it from the analysis. If the data represents an abnormal traffic period, it should not be considered as part of the normal traffic environment. Abnormal data is not be useful for future traffic forecast estimates. Prior to using the SAR data to establish MM capacity limits, validate the performance of the MM by comparing the SAR performance of the MM against the call model projections. Compare collected SAR data for the busy periods to call model estimated utilization results from the MM_UTIL_PERIOD SQL script. Comparing the SAR data against the call model predictions may identify an MM performing below expectations. This may indicate a potential problem with that particular MM. An acceptable range for the delta between the SAR data and the call model prediction is a delta that is lower than seven percentage points (where SAR is greater than the call model prediction). The ideal case is a delta around zero or if the SAR data is actually lower than the call model prediction. There is cause for concern if the delta is in the range of seven to ten percentage points and the actual utilization of the MM is close to the 70% planning limit. Contact a Network Engineering Services group or a development group to conduct an investigation into the performance of the MM, if this condition exists. Investigate the performance of the MM if the delta is greater than ten percentage points, regardless of the actual utilization of the MM. At a minimum, the investigation should analyze all of the processes and scripts running on the MM to verify that there are no extra noncall processing related processes or scripts running, which are not required. Once the data is validated, the next step is to determine the maximum and planning MM capacity limits. To determine the maximum MM
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-23
capacity, take the 30 minute BBH Erlang data from the SQL script along with the 30 minute BBH averaged SAR data (for the same time period as the Erlang data) and plug it into the Maximum Erlang Limit equation [EQ 22] and the Planning Erlang Limit equation [EQ 23] to get one data point for each limit calculation. Repeat the above calculations in order to obtain either 20 or 40 data points each (20 data points for a two week analysis or 40 data points for a four week analysis) which can be averaged together to establish the resultant Maximum and Planning MM Erlang Limits. Table 2-2 shows an example of a spreadsheet (with only 10 data points) which can be created to calculate the Maximum and Planning MM Erlang Limit calculations. Table 2-2: MM Capacity Limits Calculation Example A
CBSC 1 1 1 1 1 1 1 1 1 1
B
DATE 4/5/99 4/5/99 4/6/99 4/6/99 4/7/99 4/7/99 4/8/99 4/8/99 4/9/99 4/9/99
C
BBH Time 17:00 17:30 17:00 17:30 17:00 17:30 17:00 17:30 17:00 17:30
D
SAR1 67 67 70 67 66 64 65 64 63 60
E
SAR2 66 67 67 65 60 63 64 62 59 62
F
SAR3 67 67 69 66 62 62 64 65 61 63
G
SAR Avg 66.7 67.0 68.7 66.0 62.7 63.0 64.3 63.7 61.0 61.7
H
SAR Util 33.3 33.0 31.3 34.0 37.3 37.0 35.7 36.3 39.0 38.3
I
SQL Erl. 202 197 189 208 215 223 212 218 231 235 Avg=>
J
Max Limit 546 538 547 550 513 538 532 536 526 545 537
K
Plan Limit 446 440 447 450 420 439 435 438 430 446 439
The following steps explain the information in the spreadsheet example. MM Capacity Limits Calculation Example 1. Columns A through C provide a CBSC reference along with the date and time of the data points. Note that this example only uses 10 data points in the average calculation where 2040 data points are recommended. 2. Columns D through F are %idle SAR data points taken during the 30 minute time period starting at the time shown in Column C. 3. Column G is the average of the three SAR data points (in other words, AVERAGE(D1:F1)). Using the first line of data from the example above: SAR Avg = (67+66+67)/3 = 66.7. 4. Column H converts the %idle value to a percent utilization value (in other words, 100 G1). Using the first line of data from the example above: SAR Util = 10066.7 = 33.3.
2-24 CDMA SC Products System Resource Guide (CSSRG) June 2001
5. Column I is the Erlang measurement for the 30 minute period starting at the time shown in Column C. The Erlang data comes from the MM_UTIL_PERIOD SQL script or it can be derived from the Transcoder Channel Group Report. 6. Column J calculates the 85% Maximum MM Erlang Limit from the data in columns H and I (in other words, (82/(H13))*I1). Using [EQ 22] and the first line of data from the example above: Max Limit = (82/(33.33))*202 = 546. 7. Column K calculates the 70% Planning MM Erlang Limit from the data in columns H and I (in other words, (67/(H13))*I1). Using [EQ 23] and the first line of data from the example above: Plan Limit = (67/(33.33))*202 = 446. 8. At the bottom of column J is the Maximum MM Erlang Limit which is calculated by averaging the Max Limit results for all of the data points collected (in other words, AVERAGE(J1:J10)). Using all of data from the example above: Avg Max Limit = (546+538+547+550+513+538+532+536+526+545)/10 = 537. 9. At the bottom of column K is the Planning MM Erlang Limit which is calculated by averaging the Plan Limit results for all of the data points collected (in other words, AVERAGE(K1:K10)). Using all of data from the example above: Avg Plan Limit = (446+440+447+450+420+439+435+438+430+446)/10 = 439. To continue this example, lets assume the CBSC was equipped with a standard XC with six cages and five XCDRs per cage. Thus, the XC Erlang capacity limits (per Table 2-1) are as follows:
provides the Systems Engineer with subscriber projections for a CBSC growth analysis, the following procedure can be used to forecast Erlangs on a perCBSC basis. Table 2-3 shows an example of a spreadsheet which can be used to perform a forecast of CBSC Erlangs. Table 2-3: Example CBSC Erlang Forecast A B C D E F G H I J K L M Future
CBSC #1 CE #2 CE #3 CE #4 CE AVG CE STD CE CBSC %Sys Load 22.1% 17.5% 20.3% 20.8% 19.3% Current System Subs 50000 50000 50000 50000 50000 AVG mE/Sub per CBSC 30.43 30.43 30.43 30.43 30.43 AVG + 3 STD mE/Sub per CBSC 31.77 33.46 31.67 31.89 31.75 System Subs %Sys Load AVG Erl. 3 STD Erl.
1 2 3 4 5
5 9 4 5 4
The following steps explain the information in the spreadsheet example. Example CBSC Erlang Forecast 1. Column A identifies all of the CBSCs supporting the system under analysis. 2. The data in columns B through E is total carried Erlang data for the busy hour, of the busy day of the week, for four weeks. Two 30 minute samples of Erlang data for the busy hour are averaged together. The Erlang data comes from the MM_UTIL_PERIOD SQL script or it can be derived from the Transcoder Channel Group Report. If applicable, verify that voice and data Erlangs are added together. 3. Columns F and G provide the average (in other words, AVERAGE(B1:E1)) and standard deviation (in other words, STDEV(B1:E1)) of the carried Erlangs for each CBSC. Using the first line of data from the example above: AVG CE = (330+337+342+336)/4 = 336.25 ~ 336 and STD CE = STDEV(330,337,342,336) = 4.92 = ~5. 4. Column H is the distribution percentage of the average carried Erlangs for the CBSC when compared to the total system average carried Erlangs (in other words, F1/SUM(F1:F5)). Using all of the data in column F from the example above: CBSC %Sys Load = 336/ (336+266+310+317+293) = 0.2207 = ~22.1%. 5. Column I is the average number of subscribers using the system associated with the four weeks of data being analyzed. 6. Column J is the average milliErlangs of usage per subscriber for the system (which will be applied for each CBSC) for the busy hour of the busy day of the week (in other words, (F1/ (I1*H1))*1000).
2-26 CDMA SC Products System Resource Guide (CSSRG) June 2001
7.
8.
9.
10.
11.
Using the first line of data from the example above: AVG mE/Sub per CBSC = (336.25/(50000*0.2210))*1000 = ~30.43. Column K is the average milliErlangs plus three standard deviations of usage per subscriber for the CBSC for the busy hour of the busy day of the week (in other words, ((F1+(3*G1))/ (I1*H1))*1000). Using the first line of data from the example above: AVG+3STD mE/ Sub per CBSC = ((336.25+(3*4.92))/(50000*0.2210))*1000 = ~31.77. Column L is the total number of system subscribers projected for a future date which is based upon customer provided subscriber growth projections. Column M is the future distribution percentage of the average carried Erlangs for the CBSC when compared to the total system average carried Erlangs. Currently, this column represents the same distribution as shown in column H. The purpose of this column is to be able to adjust the system load distribution to account for new CBSC(s) added to the system which allow the growth plan to continue beyond the first bottleneck CBSC. Column N is the projected Erlang usage for the CBSC based upon the future system subscriber growth projection (column L), the future CBSC system load percentage (column M), and the average milliErlangs of usage per subscriber for the system (column J) (in other words, (L1*M1)*(J1/1000)). Using the first line of data from the example above: AVG Erl. = (75000*0.2210)*(30.43/1000) = 504.37 = ~504. Column O is the projected Erlang usage for the CBSC based upon the future system subscriber growth projection (column L), the future CBSC system load percentage (column M), and the average milliErlangs plus three standard deviations of usage per subscriber for the CBSC (column K) (in other words, (L1*M1)*(K1/1000)). Using the first line of data from the example above: 3STD Erl. = (75000*0.2210)*(31.77/1000) = 526.5 = ~527.
If the customer s marketing department provides the Systems Engineer with something other than subscriber projections, modifications to the approach above can be made to project a linear relationship according to the customersupplied projection parameter. If the customer requires a nonlinear growth projection, modifications to the approach above are necessary. The modifications depend upon the specified nonlinear growth projection requirements. For example, the customer may specify a variable subscriber growth rate along with a variable usage rate which may be based upon seasonal changes and/or marketing promotions. In either case, the desired outcome projects an average Erlang usage and a threesigma Erlang usage for each CBSC in the system. The current recommendation is to project Erlang usage for a one to two year period beyond that of the data collection period. The example in Table 2-3 projects Erlang usage on a perCBSC basis based upon a subscriber estimate for a future date. If subscriber growth
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-27
estimates are provided on a monthly basis, columns L, M, N, and O can be repeated for each month where a subscriber growth estimate is provided. With monthly projections, an estimate of when a particular CBSC will exceed the planning or maximum limit can be performed. Although the frequency of performing a full analysis depends upon the rate of growth for the system being monitored, perform a full one to two year projection analysis on a quarterly basis. For large systems, which are growing at a rapid rate, a monthly full analysis may be necessary. Identify When Bottlenecks Will Occur The next step is to compare the individual CBSC planning and maximum Erlang limits established in the Determine Present Status section to the average Erlang usage projection. Also, compare the threesigma Erlang usage projection for each CBSC in the system to determine when each CBSC will reach the different limits. Implement a CBSC capacity relief mechanism before it is projected to reach the planning limit using average Erlang usage data projections or the maximum limit, using the threesigma Erlang usage data projections (whichever one is projected to occur first). Evaluate Relief Alternatives A decision needs to be made whether to: S Reparent BTSs onto new CBSC(s) to offload traffic
S Reparent BTSs onto existing CBSC(s) to offload and balance out the
traffic S Add a new carrier onto a new CBSC layer to offload traffic
S Create a method of procedure. S Identify backup plans for schedule changes. S Make changes according to schedule.
June 2001
2-29
Introduction
The appropriate CBSC capacity management option to choose can depend upon many different factors:
S S S S S S S
Customer inputs and requests Cost of implementation Market size Terrain The current design of the system Rate of market growth The number and location of the CBSCs which exceed the planning limit.
CBSC Load Balancing thru BTS ReParenting For markets which are not growing at a rapid rate, a load balancing effort of the existing CBSCs may be a viable option. If the Erlang distribution for the CBSCs of a system are disproportionate, it may be possible to analyze the future Erlang projections to determine if a load balancing effort will extend the timeframe when a CBSC will reach its planning limit. As a general guideline, a large scale load balancing project should not be implemented unless the effort is projected to extend the planning limit timeframe of a CBSC by at least six months (refer to the example in Table 2-4). Table 2-4: CBSC Load Balancing Example Before Load Balancing CBSC1 Current busy hour Erlangs Percent of system Planning Limit (Erlangs) Projected Erlang growth per month Projected time to reach planning limit 350 70% 480 21 6.2 months CBSC2 150 30% 550 9 44.4 months
After Load Balancing CBSC1 Projected busy hour Erlangs Projected percent of system Erlangs Planning Limit (Erlangs) Projected Erlang growth per month Projected time to reach planning limit
2-30
In Table 2-4, the projected time to reach the planning limit for CBSC1 was extended by ~9 months (from 6.2 to 15.3 months), but the projected time for CBSC2 to reach the planning limit was reduced by ~24 months (from 44.4 to 20 months). NOTE A load balancing effort extends the planning limit timeframe of one CBSC by reducing the planning limit timeframe of another CBSC. Since it does not add actual Erlang capacity to the system, CBSC load balancing is not a very effective capacity relief option. It provides capacity relief for one CBSC by taking away some capacity headroom from another CBSC. Unless there are other circumstances within the system design which influence the relocation of an interCBSC border, CBSC load balancing for capacity relief purposes should be proposed as a low priority option.
It is also important to note some of the implementation issues surrounding a CBSC load balancing effort. The following three implementation options explain some of these issues for a basic two CBSC example where sites are reparented from one CBSC to another. For situations where more than two CBSCs are involved, these concepts can still be applied or a combination of multiple options may need to be applied as appropriate. Implementation Option 1 If the two CBSCs involved with the reparenting effort are managed by two different OMCR databases, the reparented BTSs can be easily added to the reparented OMCR database with the same BTS IDs. This allows toy cell call processing verification testing of the reparented BTSs on the new OMCR/CBSC prior to the actual cutover activity. NOTE A typical toy cell is a minimally configured, fully functional, spare BTS colocated within the same facility/building as the MSC/CBSC hardware. For those sites utilizing a toy cell, it is used for various different types of testing, including call processing verification testing.
During the cutover procedure, only those sites that are being reparented are subjected to an outage as the sites are disabled on one CBSC, the spans for the sites are redirected to the new CBSC, and the sites are enabled on the new CBSC. This is a preferred option since it minimizes the affected outage area to just those sites which are being reparented and it maximizes the precutover verification testing capabilities.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-31
Implementation Option 2
If the two CBSCs involved with the reparenting effort are managed by one OMCR database and it is acceptable to permanently change the BTS IDs for the reparented sites, the reparented BTSs can be easily added to the same OMCR database with a different BTS ID. This will also allow toy cell call processing verification testing of the reparented BTSs on the new CBSC (same OMCR) prior to the actual cutover activity. During the cutover, only those sites that are being reparented are subjected to an outage as the sites are disabled on one CBSC, the spans for the sites are redirected to the new CBSC, and the sites are enabled on the new CBSC. This is also a preferred option since it minimizes the affected outage area to just those sites which are being reparented and it maximizes the precutover verification testing capabilities. Implementation Option 3 If the two CBSCs involved with the reparenting effort are managed by one OMCR database and it is not acceptable to permanently change the BTS IDs for the reparented sites, it becomes more difficult to implement a reparenting effort. There are basically three approaches to implement this option:
S The first approach, which is preferred, involves deleting the BTS from
one CBSC and immediately readding the BTS onto the new CBSC. This is done for one or more sites at a time, over a period of several nights (maybe weeks, if the size of the project is large). This approach minimizes the outage area to one or a few sites at a time (depending upon the deployment strategy). However, it still lacks the capability of performing verification testing of the database changes with the actual hardware configuration prior to deploying it into a commercial system. Even though this is a time and resourceconsuming activity, this approach reduces the risk factors because it affects only one or more sites at a time in those situations where the exact same BTS IDs need to be reparented from one CBSC to another CBSC under one OMCR.
for the renumbering step). Since this approach is even more of a time and resourceconsuming activity than that of the first approach, this approach should be recommended as a secondary alternative to the first approach. S The third approach involves creating new OMCR/CBSC and XC databases offline from the system. During the cutover, the entire portion of the system under the one OMCR is disabled, the old databases are removed, the new databases are installed, the spans for the reparented sites are redirected to the new CBSC, and the system is brought back up. Although this is a viable approach for Implementation Option 3, this type of approach is typically not recommended due to the high risk factors associated with creating a new database without thoroughly testing it with the actual hardware configuration before deploying it into a commercial system. It also causes a larger outage area since all of the sites under an OMCR are affected instead of just those sites that need to be reparented. In general, the process of managing all of the parameter and neighbor list database modifications associated with a large scale reparenting activity is a difficult task, regardless of which reparenting option is chosen. Because of this difficulty, a Motorola internal tool was developed to help simplify this task. A CDMA cellular database restructuring tool, called Raven, is currently available to help create most of the database commands (in other words, parameters and neighbor lists) necessary to reparent BTSs from one CBSC parent to another. It provides the capability of keeping the BTS ID the same or to renumber the BTS ID as part of the move operation. Although Raven helps to eliminate some of the human error involved with duplicating a sites parameters and neighbors from one CBSC to another, there is still a significant amount of effort involved with managing the appropriate usage of the tool. The results must also be validated in order to verify that the final reparenting activity is successful. The reparenting option approach that is chosen should take into account the usage of this tool in order to simplify the deployment process. CBSC Splitting Since the Erlang call processing capacity of a CBSC is basically fixed, the BTS Erlang usage will exceed the planning limit of a CBSC as the carriedErlang usage of the BTSs under a CBSC increases over time (which is enabled through the expansion of CDMA RF carriers). When this occurs, CBSC splitting can be used to offload existing CBSC(s) by reparenting sites onto new CBSC(s) which are added to a system. This reduces the number of BTSs that are controlled by the CBSC which reduces the BTS footprint coverage area of the CBSC. It is also the most common method of expanding the Erlang call processing capacity of a system, which in effect increases the number of subscribers that can be supported by the system. Figure 2-4 shows a CBSC splitting example where sites from two existing CBSCs are reparented to a new third CBSC. Figure 2-4 shows
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-33
2
Figure 2-4: CBSC Splitting Example
that the total system capacity increases from 1200 Erlangs to 1800 Erlangs (if we assume a CBSC capacity of 600 Erlangs). It also shows that the BTS footprint coverage area for CBSCs 1 and 2 reduce from supporting 62 BTSs before the CBSC splitting expansion effort to 44 BTSs after the addition of a new CBSC.
62 CBSC #1 Sites
62 CBSC #2 Sites
44 CBSC #1 Sites
44 CBSC #2 Sites
36 CBSC #3 Sites
Total system capacity = 1200 Erlangs (assuming 600 erlangs per CBSC)
Total system capacity = 1800 Erlangs (assuming 600 erlangs per CBSC)
Because the addition of a new CBSC into a network requires reparenting sites from an existing CBSC to the newly added CBSC, the same implementation issues surrounding a CBSC load balancing reparenting activity also affect a CBSC splitting reparenting activity. The following three implementation options explain some of these issues for a basic two CBSC example where sites are reparented from one existing CBSC to a newly added CBSC. For situations where more than two CBSCs are involved, the concepts below can still be applied or a combination of multiple options below may need to be applied as appropriate. Implementation Option 1 If the two CBSCs involved with the CBSC splitting/reparenting effort are managed by two different OMCR databases, the reparented BTSs can be easily added to the reparented OMCR database with the same BTS IDs. If a new OMCR is added along with the new CBSC (see Figure 2-5), a new database is created for the new OMCR/CBSC hardware. Figure 2-5: New OMCR and CBSC
OMC-New CBSC-3
Re-parent BTSs with same BTS IDs
CBSC-New
= New Hardware
2-34
June 2001
If a new CBSC is added to an existing OMCR (see Figure 2-6), the existing OMCR database needs to be modified to add a new CBSC platform (via a MIB Only Mode modification to the OMCR MIB). Figure 2-6: New CBSC with an existing OMCR
OMC-2 CBSC-3
Re-parent BTSs with same BTS IDs
CBSC-New CBSC-4
= New Hardware
CBSC-5
In either case, adding a new CBSC with this approach allows toy cell call processing verification testing and/or cluster call processing verification testing of the reparented BTSs on the new OMCR/CBSC prior to the actual cutover of the new OMCR/CBSC into commercial service. During the cutover, only those sites being reparented will be subjected to an outage as the sites are disabled on one CBSC, the spans for the sites are redirected to the new CBSC, and the sites are enabled on the new CBSC. Since it minimizes the affected outage area to just those sites which are being reparented and it maximizes the precutover verification testing capabilities, this is the preferred implementation option. The larger amount of precutover testing that is performed, the greater the chances are of executing a successful CBSC deployment. This implementation option of reparenting BTSs onto different OMCRs leads toward a strategy where a Systems Engineer should attempt to design a system expansion plan with adjacent CBSCs being controlled by different OMCRs (see Figure 2-7). This alternating OMCR strategy enables a Systems Engineer to more easily implement Option 1 where BTSs are reparented with the same BTS IDs. Figure 2-7: Alternating OMCR Strategy
Striped OMC-1 / CBSC-1 OMC-2 / CBSC-3 OMC-3 / CBSC-5 OMC-1 / CBSC-2 OMC-2 / CBSC-4 OMC-3 / CBSC-6
= OMC-1
Checkerboard
OMC-1 CBSC-1 OMC-2 CBSC-4 OMC-3 CBSC-7 OMC-1 CBSC-3 = OMC-2 OMC-2 CBSC-5 OMC-3 CBSC-8 OMC-1 CBSC-2 OMC-2 CBSC-6 = OMC-3
The striped alternating OMCR strategy shown in Figure 2-7 can be implemented with horizontal (as shown), vertical, or even diagonal stripes to segment the BTSs in a system under different OMCR/CBSCs.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-35
From a CBSC capacity perspective (regardless of the OMCR strategy), the striped CBSC strategy can be effective if it is possible to grow the system with an adequate CBSC coverage area. If the area between two ICSHO borders becomes too narrow with the striped approach, the CBSC may be burdened with too much interCBSC handoff activity, which may reduce the capacity potential of the CBSC. A checkerboard CBSC approach increases the required number of physical IC links between CBSCs, but this should not have a negative effect on MM processor capacity. It is an increase in the ratio of interCBSC handoff activity to intraCBSC handoff activity, which reduces the processor capacity potential of the MM. The MM utilizes more processor CPU time to process interCBSC handoff messages than it does for intraCBSC handoff messages. One of the goals of a CBSC layout design is to minimize the ratio of interCBSC handoff activity to intraCBSC handoff activity. For most applications, a hybrid type of approach may be implemented to help minimize this ICSHO activity. Implementation Option 2 If the two CBSCs involved with the CBSC splitting/reparenting effort are managed by one OMCR database and it is acceptable to permanently change the BTS IDs for the reparented sites, the reparented BTSs can be easily added to the same OMCR database with a different BTS ID. Figure 2-8: New CBSC with same OMCR, new BTS IDs
OMC-1
Re-parent BTSs
CBSC-1
CBSC-2
CBSC-New
This type of approach also allows toy cell call processing verification testing and/or cluster call processing verification testing of the reparented BTSs on the new CBSC (same OMCR) prior to the actual cutover activity. During the cutover, only those sites that are being reparented are subjected to an outage as the sites are disabled on one CBSC, the spans for the sites are redirected to the new CBSC, and the sites are enabled on the new CBSC. This is also a preferred option since it minimizes the affected outage area to just those sites which are being reparented and it maximizes the precutover verification testing capabilities. Implementation Option 3 If the two CBSCs involved with the reparenting effort are managed by one OMCR database and it is not acceptable to permanently change the BTS IDs for the reparented sites, it becomes more difficult to implement a reparenting effort. There are basically three approaches to implement this option.
2-36 CDMA SC Products System Resource Guide (CSSRG) June 2001
OMC-1
Gradually Re-parent BTSs
CBSC-1
CBSC-2
CBSC-New
= New Hardware
This approach minimizes the outage area to one or more sites at a time (depending upon the deployment strategy), but it still lacks the capability of performing verification testing of the database changes with the actual hardware configuration prior to deploying it into a commercial system. Even though this is a time and resourceconsuming activity, the risk factor is reduced to affecting only one or more sites at a time. That makes this the preferred approach where the exact same BTS IDs need to be reparented from one CBSC to another CBSC under one OMCR.
S The second approach involves two major steps (see Figure 2-10).
Figure 2-10: New CBSC with the same OMCR, same BTS IDs in two steps
2-Step approach: 1. Re-parent all BTSs w/temp IDs 2. Re-number BTS IDs One or more a night
CBSC-New
= Existing Hardware
= New Hardware
1. The first step is to reparent all of the sites to the new CBSC using temporary BTS IDs. 2. Once the performance of these temporary sites have stabilized, each temporary BTS ID can be deleted and readded back to the same CBSC with the original BTS ID (prior to executing step one above). This approach does allow for precutover verification testing for the step one reparenting activity, but it does not allow for precutover verification testing for the step two above renumbering activity. This approach is not as efficient as other approaches since it requires two major activities in order to accomplish the overall CBSC deployment. It also requires two outages for each site being reparented to the new CBSC (one outage for the reparenting step and another outage for the renumbering step). Since this approach is even more of a time and resourceconsuming activity than that of the first approach, this approach should be recommended as a secondary alternative to the first approach.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-37
Figure 2-11: New CBSC with an existing OMCR, new MIB, same BTS IDs
CBSC-2
= New Hardware
CBSC-New
During the cutover, the entire portion of the system under the one OMCR is disabled, the old databases are removed, the new databases are installed, the spans for the reparented sites are redirected to the new CBSC, and the system is brought back up. Although this is a viable approach for this option, this type of approach is typically not recommended due to the high risk factors associated with creating a new database without thoroughly testing it with the actual hardware configuration before deploying it into a commercial system. It also causes a larger outage area since all of the sites under an OMCR (all sites on CBSCs 1 and 2 in the above example) are affected instead of just those sites that need to be reparented. Regardless of the chosen CBSC splitting option, its a difficult task managing all of the parameter and neighbor list database modifications connected with a large scale reparenting activity associated with the addition of a new CBSC. There are two internal Motorola tools available that can be used to help the deployment of a new CBSC into a commercial system. The Configuration Management (CM) tool can be used to create a new database for the new CBSC. The Raven tool can help create most of the database commands (in other words, parameters and neighbor lists) necessary to reparent BTSs from one CBSC parent to a new CBSC. It provides the capability of keeping the BTS ID the same or to renumber the BTS ID as part of the move operation. Although the tools help eliminate some of the human error involved with duplicating a sites parameters and neighbors from one CBSC to another, there is still a significant amount of effort involved with managing the appropriate usage of the tool and validating the desired results from the tool in order to verify that the final CBSC splitting activity will be successful. The chosen CBSC splitting approach should take into account the usage of this tool in order to simplify the deployment process. Layered CBSC Overlay The layered CBSC overlay approach provides two important capacity benefits when deployed: S CBSC capacity relief
2-38 CDMA SC Products System Resource Guide (CSSRG) June 2001
S S S S
System Configuration: 3sector, 800 MHz, 100% 8kb mobiles BTS Maximum Erlang Limit per sector = 15.5 Erlangs BTS Maximum Erlang Limit per cell = 46.5 Erlangs Average Percentage Loading of BTS Max. Limit for All Cells Under the CBSC = 50%
S Number of Carriers per BTS = 4 S Number of BTSs per CBSC = 600/(46.5*0.50*4) = 6.45 = ~6 cells.
It is obvious from the example that a CBSC should not be designed with four carriers under the conditions stated if the maximum number of BTSs supported by the CBSC is about six. In order to maintain a reasonable CBSC coverage area, the minimum recommended planning guideline of BTSs under one CBSC is a cluster of about 19 cells (ideally, one core cell surrounded by six inner ring cells and 12 outer ring cells). Obviously, this is not a hard limit of any sort. A lower number of BTSs per CBSC may need to implemented for certain high capacity situations. The 19 BTS per CBSC guideline is a target minimum below which one should try not to go. For a sectored BTS, it is very unlikely for the Erlang traffic growth to be evenly distributed among all of the sectors of a BTS. Therefore, the BTS typically wont reach its maximum Erlang limit potential. It is even more unlikely for the Erlang traffic growth to be evenly distributed such that all of the BTSs (including all sectors) under a CBSC reach their maximum Erlang limit all at the same time. Since the growth rates for the individual BTSs under a CBSC are different, an analysis of the number of BTSs per CBSC can be
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-39
performed using an average percentage loading of the BTS maximum Erlang limit. Figure 2-12 plots the number of BTSs per CBSC versus the average percentage loading of the cells for all of the different threesector configurations with each of them having four carriers per BTS. The legend displays the maximum assumed BTS load used for the analysis. Figure 2-12: Four Carriers, threesector BTS Example
Number of BTSs per CBSC
(4 Carriers, 3 Sector BTS, CBSC Limit = 600Erl.)
45
42
40
35
800 MHz, 13kb, 18 Erl/BTS Max. 800 MHz, 8kb, 46.5 Erl/BTS Max.
32
1900 MHz, 13kb, 21.6 Erl/BTS Max. 1900 MHz, 8kb, 55.8 Erl/BTS Max.
25 20
23 21
17
17 14 14 12 12 10 10 9 9 6 5 8 5 4 5 4 4 3 4 3 3 3 8 7
15
13
16
10 5 0 0% 10% 20%
11 9 8 7
30%
40%
50%
60%
70%
80%
90% 100%
The results above show that a threesector site (with any type of system configuration) wont support four carriers if the following design assumptions are required: CBSC Erlang limit is 600 Erlangs, 19 cells minimum per CBSC, and an average loading of 50% of the maximum BTS load. Consider the example in Figure 2-13 which plots the number of BTSs per CBSC versus the average percentage loading of the cells for multiple carriers under one BTS/system configuration (threesector BTS at 800 MHz with a 13kb vocoder and a CBSC limit of 600 Erlangs).
2-40
June 2001
2
4 Carriers 3 Carriers 2 Carriers 1 Carrier
120
111 111
80 60
42 37
67
56
56
56 48
40 20 0 0% 10%
42 33 28 28 21 17 14 12 22 28 24 19 16
42 37 33
21 14 10
19 17 12 9 11 8
20%
30%
40%
50%
60%
70%
80%
90% 100%
The system configuration shown can support up to three carriers and still meet the 19 cell minimum per CBSC with an average of 50% for the maximum BTS loading. If the minimum cells per CBSC is reduced to 17 or the average BTS loading is reduced to less than 50%, a fourcarrier system could be supported by the CBSC. Figure 2-14 plots the number of BTSs per CBSC versus the average Erlangs per BTS (independent of the system or BTS configuration) for multicarrier configurations with a CBSC Erlang limit of 600 Erlangs (an assumed value for a Helix MM). Figure 2-14: BTSs per CBSC vs. Avg. Erlangs per BTS
Number of BTSs per CBSC 120 100 # of BTSs per CBSC
120
80
60
60
40 30
60
40 20 0 0
40
30 20 15 20 13 10
30 24 20 15 10 8 12 8 6 10 7 5 17 9 6 4 15 8 5 4 13 7 4 4 13 6 4 3
10
15
20
25
30
35
40
45
50
June 2001
2-41
NOTE
The average Erlangs presented in Figure 2-14 is based upon conversation Erlangs and not on traffic channel or Walsh code Erlangs. As shown in Figure 2-14, if the desired minimum number of BTSs per CBSC were 20, then a: S Onecarrier CBSC could support an average of 30 conversation Erlangs percarrier, per BTS S Twocarrier CBSC could support an average of 15 conversation Erlangs percarrier, 30 Erlangs total per BTS S Threecarrier CBSC could support an average of 10 conversation Erlangs percarrier, 30 Erlangs total per BTS S Fourcarrier CBSC could support an average of 7.5 conversation Erlangs percarrier, 30 Erlangs total per BTS (again, assuming the CBSC limit is 600 Erlangs). As an alternate option, an upgrade to a Puma MM can be performed in order to gain an estimated 1.9 times the capacity of the Helix MM (assuming that the planned port capacity features are available to make the Puma MM processing capability the limiting factor). Figure 2-15 is an example of the Puma capacity. It plots the number of BTSs per CBSC versus the average Erlangs per BTS for multicarrier configurations with an estimated Puma CBSC Erlang limit of 1100 Erlangs (1.83 times the previous Helix estimate). Figure 2-15: Puma MM Example
Number of BTSs per CBSC
(assume Puma CBSC Limit = 1100 Erlangs)
120
110 110
80
73 73
60
55
55
55
44
40
28
37
37 28 24 18 18 14 11 22 15
37 31 28 24 18 16 12 9 10 8 14 9 7 12 8 6 22
20 0 0 5 10
11 7 6
15
20
25
30
35
40
45
50
As shown in Figure 2-15, if the desired minimum number of BTSs per CBSC were 20, then a: S Onecarrier CBSC could support an average of 55 conversation Erlangs percarrier, per BTS
2-42 CDMA SC Products System Resource Guide (CSSRG) June 2001
S Decrease CBSC traffic capacity S Generate more interCBSC handoffs S Increase the complexity of interCBSC border planning and
optimization
S Increase the number of paging areas S Increase frequency of CBSC load balancing through BTS reparenting S Increase complexity of database management, etc.
In most cases where a system is planned to grow beyond four carriers, the layered CBSC overlay approach is a necessity. As a result, the Systems Engineer supporting a design of a multicarrier system should analyze the growth of the individual system and start planning on how and when to implement the layered CBSC overlay approach. Once it has been determined that a layered CBSC overlay system design is necessary, network planning can be performed to simplify the migration from the current system design to the overlay system design. System Architecture The layered CBSC architecture links two BTSs to two different CBSCs. Each CBSC is considered to be on a different layer of carriers. The new system architecture is shown in Figure 2-16. In this example, a BTS has four carriers in service. The first two carriers, F1 and F2, reside on one of the BTS frames. This frame is linked to CBSC#1, which is in turn controlled by MSC#1. The second two carriers, F3 and F4, reside on the second BTS frame. This frame is served by CBSC #2, which in turn is linked with MSC#2. Utilizing a layered MSC approach (a different MSC per layer as shown Figure 2-16) is not necessarily required for a layered CBSC implementation, but it does have some advantages of its own. In this case, each layer has its own virtually independent endtoend service from the MSC to the mobile.
June 2001
2-43
In this approach, adding layers vertically provides for system growth, instead of reducing the CBSC coverage size horizontally by reducing the number of BTSs connected to the CBSC by reparenting BTSs to new CBSC(s). As an added benefit, this also provides redundancy in service and enhances system reliability. The enhanced system reliability is due to the fact that if one CBSC fails, the other CBSC on the other layer is still be able to provide service to the affected CBSC outage area. The details of these advantages and disadvantages are described in the Advantages and Disadvantages section. The layered CBSC structure is not limited to two carriers per layer or two layers per system (shown in Figure 2-16). Although two carriers per layer presents a more ideal system configuration, up to four carriers per layer can be supported. This is typically limited by the maximum number of carriers that the highest density BTS product deployed in the system can currently support in one frame. With the current CBSC capacity combined with the current spectrum availability, the maximum number of carriers per layer should be limited to four or less carriers per layer. Aside from any antenna combining restrictions and spectrum availability, there is no limit to the number of layers that can be deployed in a system. BTS Hardware In a layered configuration, a maximum of eight CDMA carriers at the BTS location can still be duplexed together to share the same set of two antennas persector. As a result, the cell RF coverage footprint can be the same across all eight carriers regardless of which CBSC layer the carrier is on. In a fourcarrier, twolayer example system (shown in Figure 2-17), the fourcarrier BTS hardware actually consists of two colocated BTS
2-44 CDMA SC Products System Resource Guide (CSSRG) June 2001
frames. These two frames have a separate BTS ID. The Logical BTS feature (FR# 970B) cannot be used with the layered CBSC approach because this feature requires both BTS frames to be connected to the same CBSC/OMCR. The BTS IDs for the two frames can share the same BTS ID (even without the logical BTS feature) if the two CBSCs are interfaced to two different EMXs (similar to what is shown in Figure 2-16) as well as two different OMCRs. As seen in Figure 2-17, each BTS frame is linked to a different CBSC. Using a Tx combiner, the RF output from each frame can be combined onto the same Tx antenna, while the Rx path can be split between the two frames. By using a duplexer to combine Tx and Rx paths onto one antenna, a single pair of antennas per sector can be used to feed both BTS frames. Depending upon the amount of redundancy desired, a second GPS antenna can be used to feed the second frame or one GPS antenna can be used to feed both frames. Refer to the latest version of the CDMA RF Planning Guide for more information on multiple frame antenna and GPS configurations that are supported by the various BTS product lines. Figure 2-17: Fourcarrier, Twolayer Example
GPS
GPS
CBSC #1
F1 & F2 Frame F3 & F4 Frame
CBSC #2
Most of the current BTS products (see the Base Transceiver Station (BTS) chapter for more details) can be expanded to eight carriers with a single pair of antenna per sector. For example, a fourcarrier system using the SC4800 series BTS is shown in Figure 2-18. Four Tx carriers are combined and duplexed onto the primary Rx antenna. The second set of four Tx carriers from the 2nd combiner are duplexed onto the diversity receive antenna. Refer to the latest version of the CDMA RF Planning Guide for further information regarding antenna duplexing and isolation considerations.
June 2001
2-45
Duplexer
To RX A
To RX B
Duplexer
(F5) F1 F3
(F7) F2 F4
(F6)
(F8)
Mobile Hashing Mobile hashing among carriers in idle mode is controlled by the number of carriers in the CDMA Channel List Message. All of the available carriers in service for all layers should be listed in the channel list message. All mobiles are uniformly distributed among all of the carriers listed in the channel list message based upon the mobiles International Mobile Station Identity (IMSI). The IMSI is comprised of the mobile country code (MCC), the mobile network code (MNC), and the mobile station identification number (MSIN). Refer to ANSI standard JSTD008 for further definition on the operation of the hashing algorithm. All the carriers in the same BTS site location broadcast an identical CDMA Channel List Message with all of the available carriers listed. Upon receiving this message from the paging channel, a mobile calculates the corresponding carrier based on the hashing equation. Advantages and Disadvantages of the layered CBSC Overlay Approach The following provides some of the advantages and disadvantages of the layered CBSC Overlay approach. CBSC Coverage Area In a layered overlay approach, the number of BTSs per CBSC is maximized and can stay fairly fixed. The actual coverage area benefit from using a layered approach depends on the system configuration and the number of carriers per layer. In a nonlayered approach, the number of BTSs per CBSC may constantly need to change. The CBSC is limited in the amount of traffic
2-46 CDMA SC Products System Resource Guide (CSSRG) June 2001
(BHCA, Erlang) that it can support. As the traffic increases at a physical BTS location (in other words, more RF carriers added), the CBSC is able to support fewer BTSs (due to greater Erlangs per BTS). For example, consider a CBSC with 600 Erlangs of capacity which can support 40 onecarrier BTSs carrying 15 Erlangs each. This same CBSC would only be able to support 20 twocarrier BTSs carrying 30 Erlangs each. This causes the CBSC coverage area to shrink (in other words, a reduction in the number of BTSs supported by the CBSC). Optimization In a layered overlay approach, the overlaid CBSCs can be designed to be the same as the underlaid carriers such that the interCBSC soft handoff borders occur at the same locations for all layers. In this case, the optimization effort of an ICSHO border for a new layer is minimized since the same optimization parameters of a previously optimized layer can be reused for the new layer. Even if the ICSHO borders of a new layer are partially aligned with an existing layer, there is still a significant benefit in the border optimization process. In a nonlayered approach, CBSC borders are frequently changing due to reparenting in order to add new CBSCs into the network to expand Erlang capacity, along with the reparenting of BTSs across existing CBSCs in order to balance Erlang traffic. These reparenting events create a significant amount of border optimization work, where not only does the new ICSHO borders need to be optimized, but the old ICSHO borders may need to be verified and/or reoptimized. Database Management In a layered overlay approach with the overlaid CBSCs designed to correspond on a onetoone basis with the underlaid carriers, database management is simplified since basically the same database parameters can be reused for each layer. If the colocated BTS frames in a layered CBSC approach are also interfaced in a layered EMX and a layered OMCR approach (in other words, each BTS layer is supported by a different CBSC, OMCR, and EMX), an added benefit is introduced where the BTS IDs for each of the colocated BTS frames supporting each layer can now reuse the same BTS ID. Since the EMX is limited to 511 BTS IDs, reusing BTS IDs on different layers can simplify the BTS numbering scheme of colocated BTS frames without the need of a Logical BTS feature. If this numbering scheme is used, most of the neighbor lists and XCSECT table entries could be reused with just minor modifications. The Logical BTS feature (FR# 970B) cannot be used with the layered CBSC overlay approach because it cannot be implemented unless both BTS frames are be connected to the same CBSC/OMCR. The logical BTS feature does provide some additional advantages aside from the BTS ID advantage, and as a result, those advantages wont be available when the layered CBSC overlay approach is used. In a nonlayered approach, there are frequent, significant, and complex database modifications involved with the reparenting activities
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-47
associated with adding new CBSCs or load balancing CBSCs. Although there is currently a Motorola internal tool available, named Raven, to help simplify the task, managing and verifying the neighbor list databases associated with a CBSC reparenting activity is still a challenging effort. One advantage of the nonlayered approach is that the logical BTS feature can be implemented to allow the system to treat multiple frames at a physical location (up to four frames) as a single logical site. Refer to feature request number 970B for more information regarding the details of the Logical BTS feature. System Redundancy In a layered overlay approach, one of the main advantages involves the extra level of inherent redundancy built into the technique which can enhance system reliability and availability. With this technique, each cells coverage area is essentially served by at least two CBSCs at one time. Consider a redundant system design where layered MSCs and CBSCs are present, shown in Figure 2-19. If an outage occurred on one layer (see points a, b, or c in Figure 2-19), 50% of the idle mobiles in the failed area remain in service and 50% of the mobiles with calls in progress in the failed area will not drop their calls (assuming there is equal traffic on each layer). For point c, the failed area is just one BTS. For point b, the failed area covers all of the BTSs under one CBSC. For point a, the failed area covers all of the BTSs under all of the CBSCs under the MSC. The key point to note about the builtin redundancy is that all of the active calls on the nonfailed layer(s) will not drop (which should improve system reliability) and all of the idle mobiles utilizing the nonfailed layer(s) stay in service (which should improve system availability). Furthermore, if the other CBSC(s) on the other layer(s) were not close to operating at its maximum capacity or the outage occurred during a nonbusyhour timeframe, the subscribers being served by the outageinflicted CBSC could be manually moved to one of the other operating layers. Although it is currently a form of manual redundancy, reestablishing service by moving subscribers from an outageinflicted layer to a nonfailed layer, in a timely fashion, further enhances the availability of the system. In this situation, full RF service would still be available, but potentially at a degraded grade of service (in other words, more blocking). Once the subscribers supported by the failed CBSC have been manually relocated to another layer, this allows more time to troubleshoot the root cause of the outage since it is no longer necessary to immediately restore service to the failed CBSC. Therefore, as an added benefit, the layered CBSC approach enables a more thorough analysis in troubleshooting the root cause of outages.
2-48
June 2001
c a
Switch#1
b
CBSC#1
Switch#2
CBSC#2
In a nonlayered approach, there is no CBSClevel or systemlevel redundancy built into the system design. If a CBSC fails, a hole in coverage results which causes 100% of the active calls to drop and 100% of the idle mobiles to lose service in the area of the BTSs controlled by the failed CBSC. Disaster Recovery In a layered overlay approach, the system can be designed with the hardware to support the different CBSC/EMX layers located in different physical MTSO building locations. With this type of system design, creating and implementing a disaster recovery plan is significantly simplified. In a nonlayered approach, designing and implementing a disaster recovery plan could be very difficult. Maintenance and Upgrade In a layered overlay approach, scheduled maintenance and software release upgrades can be performed with zero downtime with proper maintenance operation procedure planning. The maintenance window, to conduct outagerelated activities, can be significantly extended since an actual outage wont occur due to service being reallocated to another layer prior to performing an outage activity. New software releases can also be deployed to one layer at a time with zero downtime and with an extended maintenance window timeframe. A thorough analysis and soak period can be performed on one layer, which limits the potential subscriber impact prior to deploying it to another layer. For large systems, the software release upgrade process is significantly reduced due to the extended maintenance window timeframe, which has the potential to reduce an upgrade task that would normally take several weeks down to several days. In a nonlayered approach, scheduled outage related maintenance activities still need to be performed in the limited maintenance window
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-49
timeframes. This will also apply to software release upgrades as well. As the number of CBSCs in a system significantly grows, the ability to perform a system software release upgrade becomes difficult to manage within the timeframes of the limited maintenance windows. For large systems, the software release upgrade process may take several weeks to complete in order to minimize subscriber impact by managing the upgrade process within the required maintenance window timeframes (typically on weekends only). Adding a New CBSC In a layered overlay approach, adding a new CBSC to an existing layered CBSC network allows a combination of several previous advantages (database management, optimization, and extended maintenance windows) to be implemented to simplify the deployment process. Since the subscriber impact is minimized, a thorough verification testing and optimization process can be performed due to the extended maintenance window timeframe. Assuming there is enough capacity on the other layers during the extended maintenance window timeframe, drive testing BTSs reparented to new CBSC hardware on one layer can be performed with test mobiles without affecting subscriber service on the other layer(s). This allows a more gradual implementation of new hardware into the network as opposed to a flash cut type of approach that is typically used. In a nonlayered approach, adding a new CBSC to an existing nonlayered network combines all of the previously stated disadvantages involving database management, optimization, and limited maintenance windows on top of the requirement of deploying a CBSC with the flash cut approach. The flash cut approach is a highstress, highrisk, complex activity. However, it can also be a very effective deployment approach if it is planned and implemented properly. CBSC Capacity In a layered overlay approach, the capacity of the CBSC is more likely to stabilize at a certain level once the layer has matured to the point where adding new CBSCs is no longer necessary to handle the capacity of the layer. At this point, the call model of the CBSC should stabilize which in turn should stabilize the Erlang capacity of all of the CBSCs on the layer. In a nonlayered approach, the frequency of adding new CBSCs or performing load balancing reparenting activities increases. This also impacts the call model of the CBSC. As the number of BTSs per CBSC decreases, the amount of ICSHO and registration activity typically increases which, depending upon the system design, can have a significant negative effect on the overall CBSC Erlang capacity. Carrier Overflow Trunking Efficiency In a nonlayered approach with a fourcarrier BTS, all of the MCC channel card resources are available to all of the four carriers through the
2-50 CDMA SC Products System Resource Guide (CSSRG) June 2001
overflow option in the setup of the inroute table. When all of the traffic channels on any one carrier are busy, any new incoming call is assigned to one of the other three carriers as configured in the inroute table. This allows for a higher carrier overflow trunking efficiency when implemented properly. In a layered overlay approach, the pool of traffic channel resources is limited by the number of carriers on the layer. For example, if the system is designed with two carriers per layer, overflow is still permitted, but it is only from one carrier to another (in other words, from F1 to F2 or vice versa). The carrier overflow trunking efficiency for a twocarrier case is lower than that of the fourcarrier case. Therefore, a layered CBSC overlay approach with less than four carriers per layer has a lower carrier overflow trunking efficiency than that of a fourcarrier BTS. Summary Table 2-5 summarizes the advantages and disadvantages of the Layered CBSC approach as opposed to system expansion without layering the CBSCs. Table 2-5: Summary of Advantages and Disadvantages of the layered CBSC approach Topic CBSC Coverage Area Optimization Database Management Layered CBSC Expansion Maximizes BTSs per CBSC coverage area Minimal efforts where CBSC borders are aligned between layers No major changes for matching layers, potential BTS ID reuse if layered EMXs and OMCRs are implemented System/CBSC redundancy maintains degraded service during outage, subscribers can be moved to another layer to troubleshoot outage Built in if CBSC/EMX hardware is located in different buildings Allows an extended maintenance window and zero downtime with proper planning Easier to test and deploy with a gradual cutover of new hardware Expansion without Layering Minimizes BTSs per CBSC coverage area Reoptimizing required as borders change frequently Constant modification to neighbor lists, ICSHO, etc. for reparenting
System Redundancy
No System/CBSC redundancy
Difficult to design and implement a plan Downtime required during a limited maintenance window More difficult to deploy due to data base, optimization, and flash cutover of new hardware . . . continued on next page
June 2001
2-51
Table 2-5: Summary of Advantages and Disadvantages of the layered CBSC approach
Layered CBSC Expansion Potential to stabilize at the current capacity level Carrier overflow may be limited if < four carriers per layer Partial CBSC Overlay Design
Expansion without Layering Potential reduction in capacity with increasing ICSHO and registration activities No carrier overflow limitations
Multiple carriers/layers may be required in high traffic areas to support the traffic demands. However, multiple carriers/layers may not be necessary in remote areas. A remote area may only need one or two carriers to handle the relatively small traffic requirement. As a result, a hard handoff needs to be established between the multiple carriers on the multiple layers in the core area and a single layer in the remote area. Figure 2-20 shows a diagram of an example of going from multiple layers (two carriers per layer) to a single layer. Figure 2-20: InterCBSC Handoff from Multiple Layers to a Single Layer
DAHO Approach
Pilot Beacon CBSC 7 F7 & F8 CBSC 6 F5 & F6 CBSC 4 F3 & F4 CBSC 1 F1 & F2 MAHO Approach Pilot Beacon
ICSHO ICSHO
CBSC 3 F1 & F2
For the CBSCs operating on the same carrier frequency, interCBSC soft handoff are enabled. For CBSCs operating on different carrier frequencies, a DAHO approach or a MAHO approach with pilot beacons should be utilized to initiate an interCBSC hard handoff in order to switch carrier frequencies. In general, the MAHO using pilot beacons approach is preferred for better call reliability (fewer dropped calls) and performance. The pilot beacon can be established by using an actual BTS sector hardware or using a standalone pilot beacon unit. Frequency hopping pilot beacon units (when available) are highly recommended for these applications. As a result, the handoff methods to transition from four layers (two carriers each) to a single layer is listed in Table 2-6 (for the same example in Figure 2-20). Table 2-6: Handoff Transition Method Example Originated Carrier
F1 / F2 F3 / F4 F5 / F6 F7 / F8
Handoff Transition Method Example In the reverse direction from onelayer rural sites to multiplelayer core sites, the subscriber unit transitions through the system using interCBSC soft handoff, staying on the same layer that the call originated on while in the rural area. Once the subscriber terminates the call in the core area, the mobile tunes to the appropriate carrier frequency and layer, based on the hashing algorithm. If the mobile traverses the reverse direction in the idle mode, the mobile:
S Crosses the boundary between CBSCs S Gets a new CDMA Channel List Message S Recalculates the hashing algorithm S Retunes to the corresponding carrier frequency and layer.
Uneven Overlay For some situations, the traffic demand requires only one carrier to be deployed onto a new layer. Because of lower traffic density (one carrier per CBSC), the CBSC(s) supporting the new onecarrier layer typically have a larger coverage area than that of the CBSC(s) serving the multicarrier layer. It is very likely that the CBSCs footprints between layers may not match. A diagram depicting this type of configuration using two carriers per layer is shown in Figure 2-21. Again, it is recommended to use a pilot beacon unit to initiate the interCBSC hard handoff between the F3 carrier down to the F1 or F2 carrier.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-53
DAHO Approach 2 DAHO CBSC 5 F3 CBSC 2 F1 & F2 ICSHO CBSC 3 F1 & F2 DAHO
CBSC 1 F1 & F2
ICSHO
ICSHO
CBSC 4 F1 & F2
Pilot Beacon
CBSC 1 F1 & F2
Pilot Beacon
ICSHO
ICSHO
CBSC 4 F1 & F2
It should be noted that utilizing an uneven overlay approach does add some complexity to the deployment process of this approach. Since the CBSC borders from the initial layer to the uneven overlay layer are not aligned, the process used to create the neighbor list databases for the uneven overlay layer is more difficult to generate from the initial layer. The advantage of essentially duplicating most of the already optimized parameters and neighbor lists from the initial layer is significantly reduced. This also causes some additional effort required in the deployment process of an uneven layer in order to optimize the areas where the borders do not align with the initial layer. Part of this process involves the optimization of a DAHO border or a MAHO with pilot beacon border which can be a challenging effort depending upon the system design. However, the optimization of DAHO or MAHO with pilot beacon borders is not unique to the layered CBSC deployment approach. This same type of optimization is required with any nonuniform RF carrier deployment. Finally, the uneven overlaid approach can also add some complexity to the design and implementation of paging areas to the system. This is especially true, if a layered MSC approach is also used where two different MSC switches are used to support the two different layers. Other Issues to Consider Current multiple carrier assignment and carrier overflow features are typically not designed to function across different CBSCs. For example, the round robin carrier assignment access feature which can be used in
2-54 CDMA SC Products System Resource Guide (CSSRG) June 2001
an attempt to evenly distribute access attempts in a multiple carrier system currently wont work across different carriers on different CBSCs. For a layered CBSC system, the mobile hashing method has to be used. This method has been shown to be fairly effective at evenly distributing traffic across all of the carriers of a multiple carrier system. However, for a system with two CBSC layers and two or more carriers per layer, it is possible to use mobile hashing to distribute traffic between layers and use the round robin approach to distribute traffic between the carriers within the layer. Any future features which attempt to provide load detection and balancing across carriers also need to function across multiple CBSCs in order for it to be compatible with the Layered CBSC approach. In addition, the carrier overflow feature which allows a blocked access attempt on one carrier to overflow to another carrier currently wont work across carriers on different CBSCs. Similar to the round robin feature, the carrier overflow feature works for multiple carriers within one layer, which is controlled by one CBSC. In a layered CBSC system, this has an effect of reducing the overall trunking efficiency of the system since blocked calls wont be able to overflow from one layered CBSC to another. For systems using different BTS product lines for different layers, the sharing of antennas becomes a more difficult task to implement (if it is even possible). Different BTS product lines may not be compatible to easily allow the sharing of Rx and/or Tx antennas between multiple frames colocated at the same location. If a redundant antenna scheme is not used, the appropriate splitting and combining of the RF paths to the Rx and/or Tx antennas can be difficult to implement without degrading the performance of one or both of the colocated BTS frames. Refer to the latest version of the CDMA RF Planning Guide for more information on some of the preapproved antenna combining configurations for multiple frame SCTM BTS products. If a redundant antenna scheme is used, there is an extra level of redundancy provided by the second set of antennas used for the second layer. The reduction in redundancy also applies to the GPS antenna. One GPS antenna can be used to feed multiple colocated BTS frames with a loss of GPS antenna redundancy. Obviously, the more redundancy implemented with the layered CBSC approach, the more it costs to deploy due to the added hardware. The level of redundancy required depends upon the level desired by the service provider. For systems utilizing a fourcarrier BTS product, the typical layered CBSC deployment approach is to implement all of the four carriers of the first BTS frame before adding a new layer with a second frame. This creates a disproportionate amount of traffic being served by the two different layers (in other words, four carriers on one layer and one carrier on the new layer). Since the new onecarrier layer wont be able to support the traffic capabilities of the existing fourcarrier layer, this reduces the redundancy benefit provided by the layered approach, where the fourcarrier BTS frame might have an outage that the onecarrier frame (or layer) wont be able to provide adequate redundant support. For long term planning and growth, an ideal scenario would be to launch a system with a four carrier BTS for carrier one on CBSC layer one, and
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-55
deploy a second fourcarrier BTS for carrier two on CBSC layer two. As the system grows, one can alternate the addition of a carrier from one layer to the next, which automatically balances the load between layers when an even number of carriers exists in the system. Of course, the negative side of this approach is the cost associated with deploying the second carrier with a complete overlay of CBSCs and BTSs. There are also some ways to achieve some of the benefits of a layered approach with a nonubiquitous overlay system. For long term planning, a view of what the network will look like in the future helps determine when a layered approach is beneficial. For systems utilizing two SCTM 9600 modem frames feeding only one highpower LPA frame, there is a reduction in BTS redundancy since the one LPA frame is controlled by only one of the modem frames. The two modem frames can be controlled by two different CBSC layers but if only one LPA frame is used, there is no LPA redundancy. For this configuration, the second modem frame is added with an LPA in a ghost mode where the first modem frame has full control and alarming functionality of the one LPA. Within 800 MHz cellular systems, if the layer with the CBSC which controls the primary channel goes out of service, all of the current mobiles using the primary channel and all of the future mobiles attempting to acquire service from the primary channel are redirected to analog service. XC Upgrades There are several upgrades in the product roadmap of the CBSC to increase the Erlang capacity of the XC. Some of the major planned capacity upgrades are:
S Upgrade from KSW cards to DSW cards S Upgrade from GPROC cards to EGP cards S Upgrade from an 8 cage maximum to a 12 cage maximum
configuration. The upgrade from KSWs to DSWs allows a Standard XC configuration to use a maximum of six XCDR cards per cage. The upgrade from GPROCs to EGPs in conjunction with the DSW upgrade allows a Standard XC configuration to use a maximum of seven XCDR cards per cage. Finally, an upgrade from 8 to 12 cages allows a maximum Erlang capacity of the XC to exceed 1800 Erlangs (see Table 21 for more details). Additional details regarding specific modifications to the Standard XC configuration are provided in the software releasespecific CBSC/OMCR Equipment Planning Guide as each of these upgrades are rolled out. Helix to Puma MM Upgrade Another option used to add MM processing capacity to a system is to upgrade a Helix MM to a Puma MM. As far as CPU processing capacity
2-56 CDMA SC Products System Resource Guide (CSSRG) June 2001
is concerned, the Puma MM (R10K model) is projected to increase the call processing capacity by a factor of 1.9 times that of the Helix MM. For example, if the call model performance of a Helix MM produced an 85% CPU maximum capacity limit of 600 Erlangs, a Puma MM operating under the same call model conditions would have an 85% CPU maximum capacity limit of 1140 Erlangs. Under these conditions, the CPU capacity of the new Puma MM may no longer be the limiting factor of the CBSC. The CBSC may now be XClimited. Therefore, the 1140 Erlangs in the previous example may not be the new maximum capacity limit to use for planning purposes. With a Puma MM using a standard Helix transcoder configuration, typically the CBSC is now XC hardware limited by either the KSW port and/or the XCDR card capacity. The new CBSC capacity limit depends upon the systemspecific XC configuration. Capacity enhancing features are being planned for future releases which are projected to expand the current XC and Puma MM capacity limitations to support around 1800 Erlangs (the actual limit depends upon the call model performance of the system). As a result, the actual Erlang capacity benefit that can be achieved from a Helix to Puma MM upgrade must be analyzed on a casebycase basis, depending upon the specific system configuration and the availability of certain capacity enhancing features for the MM or XC at the time of the upgrade.
June 2001
2-57
Introduction
The MM processing capacity can be the limiting factor of the CBSC. As a result, various call model performance parameters which have an impact on the MM capacity should be monitored on a periodic basis and stored for future trending and analysis purposes. Although the MM or XC is typically the limiting factor, some of the other devices within the CBSC should also be monitored on a periodic basis and verified that its capacity is within the defined limits. Data for the other devices should also be stored for future trending and analysis purposes. The following sections identify the data that should be monitored, verified to be within limits, and stored. Most of the data recommended to be monitored comes from output of SQL scripts. The SQL scripts have been developed by a SuperCell System performance group to provide CPU and link utilization estimates directly related to measured traffic intensity. Estimated device utilization is reported with no additional equipment required (no sniffers, no monitors, etc.) and with no additional software in the network devices (no added statistics, no code instrumentation, etc.). The scripts simply use existing PM traffic intensity measurements which are combined with workload model specifics hardcoded into the SQL scripts. The SQL scripts are CBSC system software release dependent and are typically setup to run on the AP/SC UNO or UNO offline platform. For Motorola Systems Engineers, the release dependent scripts can be found at the SuperCell System performance groups internal Motorola web page currently at the following URL:
http://scwww.cig.mot.com/people/platform/ArchPerf/performance/
Look under the Estimating Device Utilization AP SQL Scripts link in the Tools section. For more information on the setup and usage of these scripts refer to the above web page. Service providers can contact their account team Systems Engineer for copies of the SQL scripts and for more information. Monitoring Levels Implement a twolevel approach to CBSC capacity monitoring:
limit to forecast when CBSC capacity relief is required, Level 2 monitoring may not be necessary, if CBSC capacity relief options are actually implemented at or near the CBSC planning limit. The following sections provide both Level 1 and Level 2 monitoring recommendations for the timeframe of data, which type of data should be collected, and the frequency of how often to process or analyze the particular data. MM CPU Monitoring There are two sets of data that should be monitored and stored for MM CPU monitoring: S The first set of data comes from the MM_UTIL_PERIOD SQL script. This script provides the key statistics associated with the call model performance of the MM. S The second set of data comes from the System Activity Report (SAR) which comes from a Tandem UNIX utility which monitors processor utilization and records CPU measurements data in ten minute intervals. The %idle data from the SAR report should be converted to a percent utilization by averaging the three or four %idle data points for a particular half hour period and subtracting it from 100 (also see the supporting information associated with [EQ 26]). The maximum MM utilization data derived from the SAR report should be monitored to verify that the MM utilization is less than the 70% planning limit and it should not exceed the 85% maximum limit. The performance of the MM should be validated by comparing the SAR performance of the MM against the call model projections. The SAR data that is collected for the busy periods should be compared to call model estimated utilization results from the MM_UTIL_PERIOD SQL script. Comparing the SAR data against the call model predictions may identify an MM performing below expectations which may indicate a potential problem with that particular MM or it may indicate a need to fine tune the call model equation to achieve better accuracy. An acceptable range for the delta between the SAR data and the call model prediction is a delta that is lower than seven percentage points (where SAR is greater than the call model prediction). The ideal case is a delta around zero or if the SAR data is actually lower than the call model prediction. There is cause for concern if the delta is in the range of seven to ten percentage points and the actual utilization of the MM is close to the 70% planning limit. Contact a Network Engineering Services group or a development group to conduct an investigation into the performance of the MM if this occurs. If the delta is greater than ten percentage points an investigation into the performance of the MM should be performed, regardless of the actual utilization of the MM. At a minimum, the investigation performed on the MM should analyze all of the processes and scripts running on the MM to verify that there are no extra noncall processing related processes or scripts running on the MM, which are not required.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-59
For Level 1 monitoring, process and analyze the SAR and MM_UTIL_PERIOD data for each MM on a weekly basis. The SAR data timeframe is already designed to collect 24 hours of data, but a process needs to be implemented to save the data to an offline storage location on a daily basis. Set up the MM_UTIL_PERIOD data to collect a window of data (in half hour segments) around the normal busy hour of the day and saved on a daily basis. Usually, three hours of data (six half hour segments) centered around the normal busy hour of the day is adequate to capture any busy hour fluctuations. For Level 2 monitoring, process and analyze the SAR and MM_UTIL_PERIOD data for each MM on a daily basis. Set up the MM_UTIL_PERIOD data to collect and store a full 24 hours worth of data (48 half hours). Since the SAR data already collects 24 hours of data, no change is required to the SAR data collection process for Level 2 monitoring. CBSC Rate Overload Parameters Monitoring The CBSC rate overload parameters are designed to prevent the MM from reaching dangerously high CPU utilization by discarding originations, page acknowledgments, pages, and registrations once the MM reaches a specified call volume threshold. The parameters control the weighting and threshold used for the detection of admission rate overload and thresholds used for clearing of admission rate overload alarms and shedding. Some of the rate overload parameters are dependent upon the current call model performance of the MM. If the rate overload parameters are set properly, the overload algorithm should shed traffic at the desired maximum MM utilization percentage (approximately), which is based upon the real time admission rate levels of originations, page acknowledgments, pages, and registrations. Table 2-7 provides a list of the recommended values for the rate overload parameters for the different available MM types. Table 2-7: Recommended Values for the Rate Overload Parameters CLI Field ORIG W PAGEACK W REG W PAGE W PAGE W (UDP) CALL DEC CALL T Parameter Name Origination Weighting Factor Page Acknowledgment Weighting Factor Registration Weighting Factor Page Weighting Factor Page Weighting Factor (for UDP mode) Call Decrement Amount Call Denial Threshold Helix MM Adjusteda Adjustedb 6 13 3 820d Adjustedc Puma MM R10K Adjusteda Adjustedb 3 7 2 820d Adjustedc . . . continued on next page
2-60 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 2-7: Recommended Values for the Rate Overload Parameters CLI Field REG DEC REG T AGG DEC AGG T CLR INTERVAL SHED PAGE AFD W (UDP) AFD DIST W (UDP) Parameter Name Registration Decrement Amount Registration Denial Threshold Aggregate Decrement Amount Aggregate Denial Threshold Clear Interval Page Message Shedding Authentication and Feature Delivery Weighting Factor Authentication and Feature Delivery Distributed Weighting Factor Helix MM 250 490 820d Adjustedc 60 Y 3 3 Puma MM R10K 250 490 820d Adjustedc 60 Y 2 2
NOTE
a b c d
Calculated from the OrigWeight_Period SQL script Calculated from the PageAckWeight_Period SQL script Calculated from the CallAdmThld_Period SQL script A value of 820 reflects a recommended maximum utilization of 85%
Since the call model performance of the MM can change as the system grows (in other words, system design changes for growth expansion, subscriber usage pattern changes, etc.), some of the rate overload parameters need to be adjusted on a periodic basis, so the algorithm can accurately reflect the current call model performance and shed traffic at the desired level. The OrigWeight_Period, PageAckWeight_Period, and CallAdmThld_Period SQL scripts are used to monitor the current call model performance of the system and calculates the rate overload parameters for ORIG W, PAGEACK W, CALL T, and AGG T. The calculated CallAdmThld value should be used for both, the CALL T and AGG T parameter settings. Set up these scripts to collect busy hour data for each MM on a daily basis. If a particular MM operates below the 70% planning limit (Level 1), compare the calculated parameters from the script outputs to the current rate overload settings on a weekly basis. Make adjustments to the rate overload settings if there is a difference between the current and new settings of +/ 10%. If a particular MM is operating above the 70% planning limit (Level 2), compare the calculated parameters from the script outputs to the current rate overload settings on a daily basis. Adjustments to the rate overload settings should be made if there is a difference between the two settings of +/ 10% for two consecutive days in a row. Abnormal or anomalous data should be investigated and eliminated from the analysis.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-61
CPP Monitoring
Use the CPP_UTIL_PERIOD SQL script to monitor the estimated utilization of the CPPs. Monitor the maximum CPP utilization derived from the SQL script to verify that the CPP utilization is less than the 70% planning limit. It should not exceed the 85% maximum limit. If the CPP is measured by the SQL script to be greater than the 70% planning limit, perform an analysis to determine if the CPP is the limiting factor of the CBSC. For Level 1 monitoring, set up the CPP_UTIL_PERIOD script to collect a window of data (in half hour segments) around the normal busy hour of the day. Save this data on a daily basis. Usually, three hours of data (six half hour segments) centered around the normal busy hour of the day is adequate to capture any busy hour fluctuations. Although the data is collected and stored on a daily basis, monitoring the data on a monthly basis to verify the CPP utilization is below the planning limit is adequate. For Level 2 monitoring, set up the CPP_UTIL_PERIOD script to collect and store a full 24 hours worth of data (48 half hours). Also, monitor the data on a daily basis to verify the CPP utilization is below the planning limit. FEP Monitoring For FEP monitoring, know the BTS to FEP layout assignments for each CBSC prior to setting up the scripts. As new BTSs are added to the system and brought into service, change the script setup to add any new BTSs. If any configuration changes are made to the BTS to FEP layout, modify the script setup accordingly. There are three SQL scripts that need to be set up:
exceed the 85% maximum limit. If the FEP is measured by the SQL script to be greater than the 70% planning limit, perform an analysis to determine if the FEP is the limiting factor of the CBSC. For Level 1 monitoring, set up the FEP scripts to collect a window of data (in half hour segments) around the normal busy hour of the day and saved on a daily basis. Usually, three hours of data (six half hour segments) centered around the normal busy hour of the day is adequate to capture any busy hour fluctuations. Although the data is collected and stored on a daily basis, monitor the data on a monthly basis to verify the FEP utilization is below the planning limit. For Level 2 monitoring, set up the FEP scripts to collect and store a full 24 hours worth of data (48 half hours). Also, monitor the data on a daily basis to verify the FEP utilization is below the planning limit. SS7 (A+) Link Monitoring For SS7 (A+) link monitoring, there are two SQL scripts that need to be set up. The A+_UPLINK_PERIOD SQL script estimates the utilization of each A+ link in the uplink direction which is defined as from the MM to MSC. The A+_DNLINK_PERIOD SQL script estimates the utilization of each A+ link in the downlink direction which is defined as from the MSC to MM. Monitor the maximum uplink or downlink A+ link utilization derived from the SQL scripts to verify that the A+ link utilization is less than 40%. There are two SS7 cards in a CBSC. Each one is able to support up to four links each (eight links total). It is recommended to add the A+ links in pairs (one for each SS7 card). Since the SS7 subsystem provides load balancing across all of the links, the maximum utilization for the A+ link is set to 40% to allow for an SS7 card failover condition, where each link in failover mode needs to support an 80% maximum utilization load in the event of an SS7 card failure. If the A+ link is measured by the SQL script to be greater than the 40%, perform an analysis to determine if the A+ link is the limiting factor of the CBSC and to determine if an additional set of A+ links are required. For Level 1 monitoring, set up the SS7 (A+) link scripts to collect a window of data (in half hour segments) around the normal busy hour of the day and saved on a daily basis. Usually, three hours of data (six half hour segments) centered around the normal busy hour of the day is adequate to capture any busy hour fluctuations. Although the data is collected and stored on a daily basis, monitor the data on a monthly basis to verify the FEP utilization is below the planning limit. For Level 2 monitoring, set up the SS7 (A+) link scripts to collect and store a full 24 hours worth of data (48 half hours). Also, monitor the data on a daily basis to verify the SS7 (A+) link utilization is below the planning limit. InterCBSC Soft Handoff Link Monitoring There are two monitoring processes that need to be performed in order to adequately monitor the InterCBSC soft handoff (IC) links:
June 2001 CDMA SC Products System Resource Guide (CSSRG) 2-63
2-64
June 2001
Table 2-8: Summary of CBSC Monitoring Utility or SQL Script SAR Utility MM_UTIL_PERIOD CPP_UTIL_PERIOD BTS_FEP_UTIL_PERIOD CPP_FEP_UTIL_PERIOD A+_UPLINK_PERIOD A+_DNLINK_PERIOD LAPD_BTS_UPLINK_UTIL_PERIOD LAPD_BTS_DNLINK_UTIL_PERIOD OrigWeight_Period PageAckWeight_Period CallAdmThld_Period Level 1 Frequency Weekly Weekly Monthly Monthly Monthly Monthly Monthly Bimonthly Bimonthly Weekly Weekly Weekly Level 1 Time Frame 24 Hours Busy Hour Busy Hour Busy Hour Busy Hour Busy Hour Busy Hour 24 Hours 24 Hours Busy Hour Busy Hour Busy Hour Level 2 Frequency Daily Daily Daily Daily Daily Daily Daily Monthly Monthly Daily Daily Daily Level 2 Time Frame 24 Hours 24 Hours 24 Hours 24 Hours 24 Hours 24 Hours 24 Hours 24 Hours 24 Hours Busy Hour Busy Hour Busy Hour
Summary of CBSC Monitoring Because the SQL scripts generate a great deal of data, it is highly recommended to create an automated script/process to condense and reformat the data for storage, trending, and monitoring purposes.
June 2001
2-65
Notes
2-66
June 2001
Base Transceiver Station (BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Expansion Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Expansion Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Products other than Japan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC9600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC4800 (excluding the SC4812) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC4812 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC2400/2450 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC614/SC614T/SC604 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC611/SC601 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC300 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reduction of BTS Offerings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTS Products for Japan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC4840 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC2440 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SC340 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pilot Beacon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1 3-1 3-9 3-9 3-10 3-11 3-24 3-26 3-26 3-27 3-33 3-37 3-43 3-46 3-49 3-51 3-54 3-56 3-56 3-56 3-60 3-63 3-67 3-67
June 2001
Table of Contents
Notes
continued
June 2001
Introduction
For CDMA systems, the Base Station System (BSS) itself is comprised of two parts:
S A Centralized Base Station Controller (CBSC) S A number of Base Transceiver Stations (BTS).
The BTS is an essential part of a Base Station System (BSS) and is the interface between the Centralized Base Station Controller (CBSC) lines and the site antennas. NOTE The BTS may consist of many variations. It is not possible to detail all these variations in this topic. Please refer to the documentation for the particular BTS to be installed for specific details.
S Routes voice and data traffic to and from the Public Switched
Telephone Network (PSTN) through the CBSC.
S Supports the network interface with the CBSC in order to send and
receive traffic and control information
Limiting Factors Various BTS products exist and can be tailored for certain types of applications. These products include:
S Microcell BTS for small capacity microcell applications S Macrocell BTS for highpowered, highcapacity applications.
Some BTS products are designed for operation in certain frequency bands. Also, different BTS products are designed for different capacity growth capabilities. The primary subelements of the BTS that may limit the capacity of the BTS are:
S Number of CDMA carrier frequencies that can be supported S Site configuration (omni, threesector, sixsector) that can be
supported
S Number of frames/cabinets that can be supported 3 S Maximum PA power available S Number of T1/E1 interfaces S Control link statistics.
The capacity of the CDMA RF air interface is a physical limitation which determines how many users can be supported via the air interface regardless of the BTS product. This may limit how much traffic the BTS is ultimately able to support. Though more channels can be equipped at the site, the additional subscribers using these channels increase the level of interference which results in poor performance. As traffic increases at a given site and the RF air interface capacity has not been reached, the site eventually begins blocking calls unless corrective action is taken. Blocking occurs because of a higher traffic demand than what the site is currently able to handle. For example, there may not be enough channel elements. In order to avoid blocking at the BTS level, the system designer must improve the traffic handling capacity of the BTS. The Systems Engineer can investigate the following several options that are available to increase the offered traffic capability of the site or area:
S Equipping additional BTS channel elements (MCC or MAWI) S Adding new CDMA carrier frequencies S Changing the BTS configuration (omni, threesector, sixsector) S Deploying an additional site(s).
As a means to add new CDMA carrier frequencies to the site, the engineer needs to ensure there is frequency spectrum available to use and that the existing BTS can support the additional carriers. Its possible that another frame or cabinet will be required at the site to house the new carrier. A new site may be required to provide additional traffic capability in an area where there is blocking. The longterm requirement for the site should be considered so that an appropriate BTS product is selected. The number of T1/E1 spans must also be considered. The T1/E1 span is the physical connection between the BTS and the CBSC (transcoder cage). The number of T1/E1 spans required is a function of the number of channel elements required. Refer to the specific BTS product documentation as to the number of T1/E1 connections that are possible. As a means to minimize the number of span lines required, three or four traffic channels can be compressed into one DS0 timeslot.
3-2 CDMA SC Products System Resource Guide (CSSRG) June 2001
Determining Utilization BTS utilization can be determined using the following three measurements:
The Walsh Code Usage field, peg count 2 from the pmC_20 record, indicates the total time, in seconds, that the Walsh code was in use (in other words, not on the idle list). This usage time includes the period between disconnect and when the device is finally restored to an idle status. This measurement characterizes the distribution of carried traffic across the sectors. Also, a percent softer handoff can be calculated. Together with the Walsh Code Equipped measurement, also contained in pmC_20, the number of Walsh codes can be engineered for this sector. In the short term, Walsh codes may be used to artificially limit traffic on a persector basis until a more sophisticated pole response mechanism can be created. Refer to the SC CDMA Product Family Performance Analysis manual for further information. Traffic Channel Usage Refer to the following BTS Expansion section for information concerning Traffic Channel Usage and Traffic Channel Element Capacity planning.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-3
Control Link Statistics With CDMA Release 2.9, the following statistics are available for the various interprocessor links within the BTS (IntraBTS Link Diagnostic, Feature #316): S GLI to GLI
S S S S S
MGLI to LCLI GLI to BBX GLI to MCC GLI to FEP 485 Bus.
These statistics are collected and stored in the BTS. They can be retrieved by the OMC/UNO user with the DIAGNOSE CLI command. These statistics include such measurements that can assess: S Utilization S Single endpoint anomalies S Physical layer problems. Planning Limits Refer to the BTS product documentation regarding the specific BTS for the capabilities of the BTS product. Items to note are: S Number of channel cards that can be equipped (MCC or MAWIs)
additional channel elements can be placed onto the leased facility (T1/E1) back to the CBSC. Its possible that an additional T1/E1 may be required. Compression of traffic channels occurs on each DS0. Depending on the configuration of the T1/E1, either three or four traffic channels can be compressed into one DS0 timeslot. The addition of more traffic channels at a BTS generates more traffic to the CBSC. The impact upon the CBSC needs to be considered to ensure that the CBSC has sufficient resources available, such as:
S S S S
Symptoms of Resource Overload Monitor the All Traffic Channel Element Busy Time for each site to assess those times when the channel element resources are all occupied. This is an indication that:
S Not enough channel elements are equipped at the site S Some existing channel elements are out of service S Some traffic needs to be offloaded onto another carrier or site.
The All Channels Busy time, in seconds, is acquired from peg count 4 of the Performance Measurement (PM) pmC_61 record or pmC_60 record (for older software releases), which is obtained from the OMCR. The All Traffic MCC Channel Elements Busy Time field indicates the time, in seconds, during which all traffic channel elements were not idle. This time defines the probability of blocking and must include OOS time, as well as traffic use, or all nonidle time. The MM starts the All Traffic Channel Elements Busy Time when the last available channel element is removed from the idle MCC Channel Element resource list. This could be due to call processing (MCC Channel Element to service a mobile) or fault management (MCC Channel Element OOS). The count stops when at least one MCC Channel Element is placed back on the idle MCC Channel Element resource list. The timer is reset at the start of the collection period with the state of All Traffic Channel Busy preserved. Refer to the SC CDMA Product Family Performance Analysis manual for further information. Other PM data available to show the lack of resources:
S S S S
Call Redirection Walsh Code Overflows, pmC_20 peg count 16 Call Redirection Channel Element Overflows, pmC_62 peg count 5 Walsh Code Overflows, pmC_20 peg count 4 Traffic MCC Channel Element Overflows, pmC_62 peg count 2.
Call Failure Class (CFC) codes, which are recorded in the Call Detail Logs (CDL), are another source for monitoring symptoms of resource overload. A CFC20, No Radio Resource Available, is an indication that
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-5
the system was not able to acquire all of the necessary radio resources to set up the call. Call Failure Class code 33 (CFC33) is available in CDMA release 2.9. CFC33 is defined as... The CBSC did not have a channel element or Walsh Code available to assign for a mobile origination or a mobile termination and the call attempt was redirected to an analog system with automatic reaccess.
Reducing Utilization/Capacity Improvement Calibrate each BTS to compensate for sitespecific cabling and normal equipment variations. Calibration guarantees that all gains and losses of all cables and devices does not cause improper site operation. The appropriate BTSlevel capacity relief management plan to choose depends upon many different factors, such as:
S S S S S
Customer inputs and requests Cost of implementation Site acquisition availability Design of the system Rate of market growth.
Its up to the system designer to choose the appropriate capacity management options to create a capacity management plan that best fits the particular situation. Refer to the BTS Expansion section for additional information on capacity relief management options. Software Features Software features will be introduced over time to improve the capabilities of the BTS, such as:
S Logical BTS (Feature 970A/B) S Multiple Carriers per CCP cage in BSS Release 2.8.3 (Feature #945) S Multiple Spans per CCP cage in BSS Release 2.8.3 and 2.9 (Feature
#949)
Common hardware such as span lines, timing sources, and modems will be shared among frames and managed by the system. Common configuration and alarm information, available for the entire site, simplifies operation, maintenance, and performance. Logical BTS Support is a software feature which provides system support for multiple modem frames in a BTS. This feature enhances the BTS configuration database to support up to four modem frames in a single BTS. Performance management software will be updated so that the performance statistics for the carrier/sectors of each modem frame can be view as one integrated BTS. Fault management alarms are correlated to the same BTS, and frame level alarms contain a frame ID. Table 3-1: Logical BTS Advantages Prior to logical BTS Channels assignment between frames is not supported. Each BTS can share a GPS antenna but requires an independent GPS receiver. Separate dialup modem and telephone lines are required for each RFMF. Configuration databases is set up for each RFMF. DAHOs can only be set to carrier supported by an RFMF. DSOs with excess capacity cannot be groomed to second RFMF. Performance statistics are logged by each RFMF (each has its own BTS ID). Frame alarms do not designate a specific frame. With logical BTS Channel assignment can be directed to any carrier in the site. The BTS can operate with a single GPS and backup timing source. (Requires additional hardware.) The BTS supports a single dialup modem for all RFMFs. The BTS has an integrated configuration database (for example, neighbor lists). All carriers can act as DAHO targets. Unused DSO capacity may be groomed to a second RFMF. Performance statistics are logged for the entire BTS. Frame alarming contain a Frame ID so alarms are framespecific.
Multiple Carriers per CCP cage in BSS Release 2.8.3 (Feature# 945) The Multiple Carriers per Cage feature supports more than one CDMA carrier per cage in the SC4812(T), SC4840, and SC2440 base stations to provide double density capacity. Multiple Carriers per Cage allows a CCP 12 Cage to support more than one carrier depending on the sector configuration, such as: S One sector (omni) with up to four CDMA carriers
S Six sectors with up to two CDMA carriers S Three sectors with up to four CDMA carriers.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-7
Refer to the Release Notes for further information. Multiple Spans per CCP cage in BSS Release 2.8.3 and 2.9 (Feature# 949) This feature provides the system support needed to terminate multiple span lines at each cage of a BTS. Refer to the Release Notes for further information.
Multiple PAs per Sector in BSS Release 2.9 (Feature# 1174) This feature provides capability of more than one PA per sector to be provisioned and managed in a BTS (LBTS). Refer to the Release Notes for further information.
3-8
June 2001
BTS Expansion
Introduction
The BTS comprises the necessary RF infrastructure equipment that supports the airinterface. This equipment includes such items as the radio channel transceivers, power amplifiers, and control processors needed to translate the voice/data traffic between the CBSC and the subscriber units. BTSs are designed according to IS95 and IS97 standards for the CDMA cellular airinterface and base stations, respectively. The purpose of the BTS is to provide the RF coverage over a given area and to support the subscribers within that area. The BTS provides the RF interface between the subscriber units and the Mobile Switching Network (MSN). The function of the BTS is to create the network interface with the CBSC for the transmission and reception of traffic and control information. Before the Systems Engineer can start expanding the RF portion of the system, they have to understand the present state of the system and what is truly necessitating an expansion to the system. The following highlevel questions are a few of the many questions the system designer needs to ask:
S S S S
Is an additional area of coverage required? Is an improved signal level desired? Are more users required to be supported? Are current users using the wireless service more?
The desired coverage area is the region in which the wireless service provider wishes to provide service to a group of subscribers. This has a direct relationship to the number of cell sites required. Generally speaking, the larger the area to be covered, the more sites that are required. As areas of coverage expand, or as improvements in signal levels are desired, the system requires additional BTS equipment to support this increase of RF coverage or improved RF signal level. Additionally, traffic forecasts impact the number of sites and the number of CDMA carriers required at each site. Traffic requirements may also dictate the specific configuration required (omni, sector) at each site. In some situations, traffic may be the driving force in the quantity of sites. In this case, while the desired coverage area may yield only the requirement for a few sites, the traffic demands may dictate that additional sites are required to provide for the subscriber usage. As traffic demands grow, the system eventually needs additional BTS equipment to support this traffic increase. The additional equipment can be BTS equipment required to:
S Add additional traffic channels to a site S Add additional carriers to a sector (adding second, third, fourth, etc.
carrier)
The following topics highlight the various BTS products offered by Motorola. Some products are designed for operation in certain frequency bands or designed for a limited capacity growth capability.
BTS Expansion Coverage
A new site may be required to provide coverage in an area where the RF signal is inadequate. Consider the long term requirement for the site so that an appropriate BTS product is selected. Regard this new site as an expansion to the total number of BTS network elements in the system. This increase of BTS network elements impacts the network elements which control and monitor the BTS devices. Therefore, the Systems Engineer must be aware of the impact the new BTS elements have upon the other network elements (such as, CBSC, MSC, etc.). Once the new BTS hardware is installed and calibrated, it is necessary to make the updates to the OMCR/CBSC database and to download the software and data to the new modules. Modify the database so that the neighbor lists of adjacent sites recognize the new site(s). If there are multiple CBSCs in the network, determine to which CBSC the new site is to connect. If the new site is physically located next to sites that are all connected to one CBSC, then that CBSC is the best candidate for this new site. If the new site happens to be physically located along the border between two CBSCs, this site can potentially connect to either of the CBSCs. The engineer needs to investigate the resources available on both of the CBSCs, determine the predominant handoff situations, and then make an educated determination as to the proper CBSC for the new site to be connected. Before adding a new site(s) to a CBSC, the engineer needs to ensure the new site wont overburden the CBSC. Its possible the engineer needs to relocate some of the sites onto a different CBSC in order to allow the new site(s) to be added. The process of relocating a site(s) from one CBSC to another requires the deletion of the site from one CBSC database and entering the site information into the database of a different
3-10 CDMA SC Products System Resource Guide (CSSRG) June 2001
CBSC (a process referred to as reparenting or rehoming the database). In addition to the database change, the physical span connection between the BTS and CBSC needs to be disconnected from the old CBSC and connected to the new CBSC.
BTS Expansion Traffic
As traffic demand increases at a given site, the site eventually begins to block calls due to a higher traffic demand than what is currently offered. In order to avoid this blocking, the system designer must improve the traffic handling capacity of the system. The CDMA RF Carrier chapter addresses methods to improve the traffic capacity of the CDMA RF carrier. This section addresses methods to increase traffic capability of the BTS site so that it can support the additional RF capacity. The Systems Engineer can investigate several options that are available to increase the offered traffic capability of the site or area:
S S S S
Equipping additional BTS channel elements Adding new CDMA carrier frequencies Changing the BTS configuration (Omni, threesector, sixsector) Deploying an additional site(s).
A new site may be required to provide additional traffic capability in an area where there is blocking. Consider the long term requirement for the site in order to select the appropriate BTS product. Both an expansion to an existing BTS or the addition of a new BTS impacts the supporting CBSC. Investigate CBSC resources to determine if sufficient resources are available to support the new traffic or if additional resources are required. The following topics highlight the methods that can be investigated by the Systems Engineer to increase the traffic capacity of a BTS. NOTE Not all of the methods will be available for a given BTS.
BTS Channel Elements Installing additional channel elements is the simplest method for adding capacity to a site. This takes the form of:
S Replacing an MCC8E(s) with an MCC24(s) S Replacing a 16 channel MAWI board(s) with a 36 channel MAWI
board(s). Channel element cards support the paging and sync channels in addition to the traffic channels. Also, the traffic channel elements are required to support the primary link and any soft handoff links.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-11
A threesector site minimally equipped with three MCC8 cards can support two overhead channels for each sector (page and sync) and eighteen traffic channels. These eighteen traffic channels are necessary to support the primary link to the subscriber and any soft handoff links with subscribers connected to another site. These eighteen channels offer 11.5 Erlangs of traffic with a 2% GOS (assuming Erlang B). These 11.5 Erlangs serve those subscribers in a oneway or a soft handoff condition with this site.
Table 71 shows that the maximum Erlang limit for one sector of a threesector site operating at 1900 MHz and supporting only 13 Kbps users is 7.2 Erlangs. If you assume 50% additional traffic is used for soft handoff, the maximum traffic channel elements required at this site is 42: 7.2 Erlangs sector * 3 sectors * 1.5 = 32.4 Erlangs
32.4 Erlangs (assuming Erlang B and 2% GOS) yields 42 circuits. Six overhead channels plus the 42 traffic channels requires six MCC8 cards to be installed at the site. 42 TrafficChannels + 6 Overhead = 48 ChannelElements 48 ChannelElements 8 ChannelElementsperMCC 8 =6
If a site was initially implemented with a minimum number of channel element cards (for example, three MCC8 cards), the full RF capacity of the site is not realized until additional channel element cards are installed. Monitor the traffic usage (which includes soft handoffs) for each site to assess the number of channel elements required. The traffic usage, in seconds, is obtained from the Performance Measurement (PM) record pmC_61 or pmC_60 (for older software releases) obtained from the OMCR. Traffic channel usage, in minutes, is obtained by dividing this value by 60 seconds. Erlangs are obtained by dividing this value by the number of seconds in the collection period (the PM data is collected every halfhour or 1800 seconds). The Systems/Traffic Engineer can perform traffic calculations to determine the number of channel elements required at the site to maintain performance criteria. NOTE For those BTS products which share channel elements across multiple carriers, the pmC peg count provides total usage across all carriers of the channel element resource pool. The pmC peg count also provides total usage for all of the service options that are available (for example, voice, circuit data, and/or packet data).
Additional items need to be addressed before installing incremental channel element equipment. For example, adding the additional channel
3-12 CDMA SC Products System Resource Guide (CSSRG) June 2001
elements, the linear power amplifier (LPA) may or may not be able to support the additional users. Since these channel elements allow more users to be served by the site, more PA power is required. If the PA is already near its rated limit, this suggests an additional carrier may be required. Propagation characteristics may exist that wont allow the sector to reach the RF capacity guidelines of a given CDMA carrier as detailed in Table 71. If this is the case, an additional carrier may also be required. If additional channel elements can be added to the site without exceeding the PA capabilities or RF capacity, ensure that the additional channel elements can be placed onto the leased facility (T1/E1) back to the CBSC. It is possible that an additional T1/E1 may be required. Compression of traffic channels occurs on each DS0. Depending on the configuration of the T1/E1, either three or four traffic channels can be compressed into one DS0 timeslot. The addition of more traffic channels at a BTS generates more traffic to the CBSC. This impact upon the CBSC should also be considered to ensure that the CBSC has sufficient resources available (CPU utilization, port capacity, MSI capacity, XCDR capacity, etc.). Once the physical changes to a BTS are complete, it is necessary to make updates to the OMCR/CBSC database and to download software and data to the new modules. The following steps, provided below, are intended to provide a Systems Engineer with a set of guidelines for channel element planning on a BTS level: 1. Collect Data 2. Determine Present Status 3. Forecast Utilization 4. Identify Bottlenecks 5. Evaluate Relief Alternatives 6. Implement Relief Mechanisms. These guidelines utilize strategies from the SixStep Capacity Engineering Strategy (from the General Capacity Engineering Strategy Introduction) to perform the planning. Perform and analyze the following steps individually, on a percarrier basis, for those systems with multiple carriers already deployed. Analyze each carrier like its own separate system. For those BTS products which share channel elements across multiple carriers, the total usage across all of the BTS carriers are analyzed. The analysis should forecast out in time from the present date and should be repeated on a periodic basis. The frequency of the planning and monitoring exercise depends upon how fast the system usage grows. The more frequent the monitoring, the sooner a plan can be formulated and implemented to minimize any capacity management issues before growth causes performance degradation.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-13
Collect Data Collect and monitor, as the primary data, the BTS traffic channel element minutes of usage data on a perBTS basis. For systems which already have multiple carriers deployed, collect and analyze the data on a percarrier basis (depending upon the BTS product being used). Since the analysis being performed is on a cell site level, the measurement collection interval should be large enough to identify the Bouncing Busy Hour (BBH) peak traffic period for each cell.
Additionally, the measurement collection interval should be large enough to capture the Busy Day Bouncing Busy Hour (BDBBH) for the week for each cell/carrier. If the system being monitored has a significant drop in subscriber usage as well as a shift in the traffic pattern for the weekend, perform an analysis on only the weekday data. Collect the BBH and BDBBH usage data for each cell/carrier on an ongoing weekly basis. However, for the initial baseline measurement, collect and fully analyze a minimum of four weeks of data. Collect and monitor, as the secondary data, the BBH performance statistics on a percarrier basis. The performance statistics consist of a blocked call rate and a grade of service. As a result, the typical data collection process stores BBH traffic usage data and performance statistics. It also stores, on an ongoing weekly basis, the BBH time of day for each sector/cell in the system for Monday through Friday data (assuming weekend data can be disregarded). Although the frequency of performing a full analysis depends upon the rate of growth for the system being monitored, the minimum recommendation is to perform a full year projection analysis on a quarterly basis. A monthly full analysis is preferred. In either case, perform a weekly review of the present status to keep track of any current sites requiring more channel elements. Refer to the PMTRAF User s Manual for CDMA PM Statistics/Traffic Report for further information regarding the data to be collected. PMTRAF is a program which produces a bouncing busy hour traffic report based on the OMCR PM peg counts, showing various statistics such as:
S S S S
Determine Present Status Validate the integrity of the data being collected. Investigate and eliminate missing data or anomalous data from the analysis. If the data represents an abnormal traffic period, the abnormal data wont be useful for future traffic forecast estimates. Three planning limits exist that should concern the Systems/Traffic Engineer:
3-14 CDMA SC Products System Resource Guide (CSSRG) June 2001
The appropriate BTSlevel capacity relief management plan to choose can depend upon many different factors, such as:
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-15
Customer inputs and requests Cost of implementation Site acquisition availability The design of the system Rate of market growth.
The system designer chooses the appropriate capacity management options to create a capacity management plan that best fits the particular situation. The following is a summary of the capacity management/relief options: S Add additional channel element cards S Replace existing site with an EMAXX supported product (EMAXX may improve reverse link capacity, trunked PA may offer additional forward link capacity assuming that the forward link capacity was not a limiting factor beforehand) S Readjust Pilot powers to distribute traffic to underutilized sites S Reorient and/or downtilt antennas to distribute traffic to underutilized sites S Modify parameters to distribute traffic to underutilized sites or to reduce power requirements S Sectorize S Implement a microcell (new site) S Implement a cell split (new site). Forecast Utilization There are several different strategies that forecast utilization. Each of them has different figures of merit to justify their usage. The marketing departments of cellular operators typically project future growth through subscriber projections, which are then used as the baseline parameter to gauge future system utilization. Ultimately for channel element planning, what is required is a forecasted estimate of traffic usage minutes on a percarrier, percell basis. For sites which can share channel elements across multiple carriers, an estimate of total usage across all of the carriers is required. If the customer s marketing department provides the Systems/Traffic Engineer with subscriber projections for the analysis, the following procedure can be used to forecast traffic usage minutes on a percell basis. Table 3-2 shows an example of a spreadsheet which can be easily created to perform the following forecast of traffic usage minutes. Procedure to forecast traffic usage minutes: 1. Collect the BDBBH traffic usage minute data (including voice and circuit/packet data usage) for four weeks worth of current data (four data points per site, one per week), for each cell in the system on a percarrier basis (on a multiple carrier basis if the channel elements are shared across carriers). See columns B thru E in Table 3-2. 2. Baseline the system by calculating the average BDBBH traffic usage minutes from the four weeks worth of current data for each cell in
3-16 CDMA SC Products System Resource Guide (CSSRG) June 2001
the system [in other words, AVERAGE(B1:E1)]. See column F in Table 3-2. 3. Calculate the standard deviation (1sigma) for the average BDBBH traffic usage minutes for each cell in the system. See column G in Table 3-2. 4. Obtain the average number of subscribers using the system associated with the four weeks of data being analyzed. See column H in Table 3-2. 5. Calculate the Average BDBBH traffic usage per subscriber on a percell basis [in other words, F1/ H1]. See column I in Table 3-2. 6. Calculate the Average BDBBH traffic usage + 3sigma per subscriber on a percell basis [in other words, (F1+(3*G1))/H1]. See column J in Table 3-2. 7. Obtain the projected subscriber growth for the system. See column K in Table 3-2. 8. Calculate the projected Average BDBBH traffic usage on a percell basis [in other words, K1*I1]. See column L in Table 3-2. 9. Calculate the projected 3sigma Average BDBBH traffic usage on a percell basis [in other words, K1*J1]. See column M in Table 3-2. Table 3-2: Example Spreadsheet to Forecast Traffic Usage A
BTS ID
B
Week 1 BDBBH Trf. Min. 1092 536 704 340 605
C
Week 2 BDBBH Trf. Min. 957 490 709 325 633
D
Week 3 BDBBH Trf. Min. 1012 524 743 374 634
E
Week 4 BDBBH Trf. Min. 982 447 779 380 577
F
AVG
G
STD
H
Current Subs
I
AVG Trf. Usage per Sub 0.02022 0.00999 0.01468 0.00710 0.01225
J
AVG + 3 STD Trf. Usage per Sub 0.02373 0.01238 0.01676 0.00869 0.01387
K
Future Subs
L
AVG Trf.Min Future 1516 749 1101 532 918
M
AVG + 3 STD Trf.Min Future 1780 928 1257 651 1040
1 2 3 4 5
59 40 35 27 27
If the customer s marketing department provides the Systems/Traffic Engineer with something other than subscriber projections, modifications can be made to the above approach to project a linear relationship according to the customersupplied projection parameter. If the customer requires a nonlinear growth projection, modifications are necessary to the above approach which depend upon the specified nonlinear growth projection requirements. For example, the customer may specify a variable subscriber growth rate along with a variable usage rate which may be based upon seasonal changes and/or marketing promotions. In either case, the desired outcome projects an average BDBBH traffic usage and a 3sigma average BDBBH traffic usage (in minutes) for each cell. The example in Table 3-2 projects traffic utilization based upon a subscriber estimate for a future date. If subscriber growth estimates are
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-17
provided on a monthly basis, then columns K, L, and M can be repeated for each month where a subscriber growth estimate is provided. With a monthly analysis, an estimate of when a particular cell will exceed its current channel element capacity or maximum limit can be performed. This type of analysis can be helpful in determining whether a BTSlevel or a systemlevel capacity relief mechanism should be implemented. Table 3-3: Example Spreadsheet to Forecast Required Channelization
A
BTS ID
L
AVG Trf.Min Future 1516 749 1101 532 918
M
AVG + 3 STD Trf.Min Future 1780 928 1257 651 1040
N
AVG Erlang Future 25.3 12.5 18.3 8.9 15.3
O
Channel Elements Future 34 20 26 15 23
P
CE and Overhead Future 40 26 32 21 29
Q
MCC 8 Future
R
AVG + 3 Erlang Future 29.7 15.5 21.0 10.9 17.3
S
Channel Elements Future 39 23 29 18 25
T
CE and Overhead Future 45 29 35 24 31
U
MCC 8 Future
1 2 3 4 5
5 4 4 3 4
6 4 5 3 4
The following steps are used to continue the analysis (channel element forecast) based on the forecasted traffic usage: 1. Calculate the projected Average BDBBH Erlang requirement on a percell basis [in other words, L1/ 60]. See column N in Table 3-3. 2. From an Erlang table determine the number of channel elements required to support the Erlang requirement [in other words, determine number of circuits required for a given grade of service to offer the Erlang requirement in column N]. See column O in Table 3-3 (this assumes an Erlang B table with a desired 2% grade of service). 3. Increase the calculated channel element requirement by the number of channel elements required for the control channels (page and sync). See column P in Table 3-3. [Assuming a threesector site, six overhead channels are added.] For multiple carrier sites which share channel elements across all carriers, include the control channel requirements for all of the carriers that are supported. 4. Determine the number of channel element cards required. [In other words, column P divided by the number of channel elements provided by the channel element card]. See column Q in Table 3-3. (MCC8s were assumed for this scenario.) 5. Calculate the projected 3sigma Average BDBBH Erlang requirement on a per cell basis [in other words, M1/60]. See column R in Table 3-3. 6. From an Erlang table, determine the number of channel elements required to support the 3sigma Erlang requirement. [In other words, determine number of circuits required for a given grade of service to offer the Erlang requirement in column R]. See column S in Table 3-3 (this assumes an Erlang B table with a desired 2% grade of service).
3-18 CDMA SC Products System Resource Guide (CSSRG) June 2001
7. Increase channel element requirement by the number of channel elements required for the control channels (page and sync). See column T in Table 3-3. [Assuming a threesector site, six overhead channels are added.] For multiple carrier sites which share channel elements across all carriers, include the control channel requirements for all of the carriers that are supported. 8. Determine the number of channel element cards required. [in other words, column T divided by the number of channel elements provided by the channel element card]. See column U in Table 3-3. (MCC8s were assumed for this scenario.) HighSpeed Packet Data Considerations The following guidelines apply towards systems with HighSpeed Packet Data (HSPD) deployed and still have a low penetration rate of HSPD usage ( < 1%). There are two site equippage configurations which need to be considered: S Site is equipped to handle the maximum limit
level, any sites which exceed either of the Existing Channelization, BTS Hardware, or Walsh Code Usage Maximum Limits. Establish the planning limit into category regions which represent a stoplight level of urgency applied to the forecasted traffic usage data (for both average and 3sigma values). The green region represents a low level of urgency with the BTS traffic usage ranging from low usage up to the Existing Channelization planning limit. The yellow region represents a moderate level of urgency with the BTS traffic usage ranging from the Existing Channelization planning limit to the BTS Hardware or Walsh Code Usage Maximum limits. Finally, the red region represents a high level of urgency with the BTS traffic usage greater than the BTS Hardware or Walsh Code Usage Maximum limits. NOTE The BTS Hardware Maximum Limit and the Walsh Code Usage Maximum Limit do not necessarily occur at the same point or level. Depending on the BTS product and application (mobile, fixed, mixed, etc.), one of these limits will be reached first and determines the actual limit for the BTS.
Evaluate Relief Alternatives A decision needs to made as to how to increase the traffic capacity of the system to resolve the bottleneck conditions. The options include:
S The addition of channel elements to the site S A replacement of the existing BTS product with a different BTS
product that provides for more channel element capacity
S The addition of more CDMA sites S The addition of another CDMA carrier.
At this point, make a plot showing the traffic usage data in a Red/Yellow/Green stoplight fashion onto a System/CBSC level BTS location map. This plot is useful in identifying isolated cells and/or determining areas which have exceeded the BTS Hardware or Walsh Code Usage Maximum Limit and are candidates for adding a new CDMA carrier or site. Create an individual traffic usage location map as described above for each carrier deployed in the system. The appropriate capacity management plan to choose on a BTS or System level is dependent upon many different factors, some of which are:
S S S S S
3-20
Customer inputs and requests Cost of implementation Market size Terrain Site acquisition availability
June 2001
S S S S
Identify dates for scheduling the changes Create a method of procedure Identify backup plans for schedule changes Make changes according to schedule. NOTE Making any change to the network requires reevaluation of the previously established processes. Make changes to the process concurrently with changes in the physical network.
Addition of a New CDMA Carrier Frequency The addition of a new CDMA carrier (1.25 MHz RF channel) to a BTS requires the addition of various equipment at the BTS location. The CDMA RF Carrier chapter described in detail how to determine when a new RF carrier needs to be introduced into the system. The Systems Engineer needs to ensure that the BTS product has the capability of expanding to the new carrier and that there is frequency spectrum available to utilize. This section highlights the requirements needed at the site to support the additional carrier. [Analysis as to whether it is possible for the system to support another carrier (frequency spectrum, equipment, etc.) needs to be considered.] Some of the basic components are:
S S S S S
June 2001
Interframe Cabling (for both the transmit and receive RF paths) Filters and Cables in the Appropriate BTS Frame LPA/ELPA Shelves Bandpass Filters Directional Couplers (if new antennas are required)
3-21
Duplexers (if new antennas are required) Transceiver Modules (BBX cards or MAWI cards) Channel Element Cards Transmit Combiners Only CDMA Channels which are at a minimum of 2.5 MHz spacing, center frequency to center frequency, can be combined onto the same TX combiner. Additional CCP Cage (the CCP12 cage can support multiple carriers) Expansion BTS Frame or Cabinet (as required) 19 inch Rack for the Combiners Directional Antennas (if new antennas are required) New Tower Cable Transmission Runs (if new antennas are required) Additional DC power.
S S S S S S
Once the physical changes are complete, it is necessary to make updates to the OMCR/CBSC database and to download software and data to the new modules. RF calibration is required for the new hardware. The addition of a CDMA RF carrier at a BTS generates more traffic to the CBSC. This impact upon the CBSC needs to be considered to ensure that the CBSC has sufficient resources available. Converting Cell Site Configurations Converting a cell site from an omni configuration to a sector configuration provides for greater capacity at the site. Other benefits of sectorizing a site are:
S Potential for having higher gain base antennas to provide for better
inbuilding coverage, longer subscriber battery life, or greater range. The Systems Engineer determines if the existing BTS product at the site is capable of the sector conversion desired. The available BTS product may limit the options that are available to the Systems Engineer. Furthermore, the conversion of a BTS to a different configuration may result in more traffic to the CBSC. This impact upon the CBSC needs to be considered to ensure that the CBSC has sufficient resources available. Omni to ThreeSector Expanding an omniconfigured BTS to threesector coverage requires the addition of various equipment at the BTS location. The reader is cautioned that there are some BTS products that wont allow threesector operation (for instance, the SC611). Some of the basic components, which may be required to convert the cell from Omni to threesector, are:
S Interframe Cabling (for both the transmit and receive RF paths) S Filters and Cables in the Appropriate BTS Frame
3-22 CDMA SC Products System Resource Guide (CSSRG) June 2001
LPA/ELPA Shelves Bandpass Filters Directional Couplers Duplexers Transceiver Modules (BBX cards or MAWI cards) Channel Element Cards Directional Antennas (for both transmit and receive frequencies) New Tower Cable Transmission Runs Additional DC power.
The standard omni BTS/SIF includes filter paths for one sector of three antennas (one transmit, two receive). To convert this to threesector operation requires the addition of cables and filters for two more sectors. Once the physical changes are complete, make updates to the OMCR/CBSC database and download software and data to the new modules. The new hardware requires RF calibration. Omni to SixSector Expanding an omniconfigured BTS to sixsector coverage is similar to the omni to threesector conversion. The only difference is in the amount of equipment required. Again, the reader is cautioned that not all of the BTS products are able to be configured as a sixsector site. Some of the basic components, which may be required to convert the cell from threesector to sixsector, are: S Interframe Cabling (for both the transmit and receive RF paths) S Filters and Cables in the Appropriate BTS Frame S LPA/ELPA Shelves S Bandpass Filters S Directional Couplers S Duplexers S Transceiver Modules (BBX cards) S Channel Element Cards S Directional Antennas (for both transmit and receive frequencies) S New Tower Cable Transmission Runs S Additional DC power. The standard omni BTS/SIF includes filter paths for one sector with three antennas (one transmit, two receive). To convert this to sixsector operation requires the addition of cables and filters for five more sectors. Once the physical changes are complete, make updates to the OMCR/CBSC database and download software and data to the new modules. The new hardware requires RF calibration. ThreeSector to SixSector Expanding a threesector BTS to sixsector coverage is similar to the omni to sixsector conversion except that three sectors as opposed to
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-23
five sectors of equipment are required. (Refer to the Omni to SixSector section). Once the physical changes are complete, make updates to the OMCR/CBSC database and download software and data to the new modules. The new hardware requires RF calibration. New Site for Traffic
When an existing site can no longer be expanded to offer the amount of traffic required, a new site or several new sites may be required as a means to add the additional system capacity to the wireless network. Consider the long term requirement for the site(s) in order to select the appropriate BTS product. Refer to the BTS Expansion Coverage section for additional items to be considered when a new site is added to the system. RF Optimization Verify any BTS hardware expansion done in the field for proper operation by drive testing and collecting data from the new equipment. Some optimization may be required to tailor the new equipment to the particular system. This is necesary to ensure that all of the new equipment, and its associated new cabling, is properly installed before commercial users begin to utilize the newly installed equipment. The following list gives various items that can be verified or performed to ensure proper operation of the equipment: S Verify Proper Sector/Carrier Topology
S Development Handoff Zone Drive Routes S Coordinate PreCommercial Testing and Launch S For testing purposes, set up the new CDMA carrier such that only S
mobiles with security class 10 or above have access to the system. Create drive routes and drive the system on an existing CDMA carrier frequency (preferably at night when there is little traffic) and the new CDMA carrier frequency. With certain diagnostic monitors (DMs), two phones can be connected to allow the data to be collected at the same time. Otherwise, the system needs to be driven once for the existing carrier and a second time for the new carrier. Collect (log) drive test data and post process it. Generate plots of FER, Ec/Io, TGA, Tx Power along with the Averages and Standard Deviations for the entire drive. If any differences are seen, further testing may be required in that area. Monitor statistics between the carriers to ensure the load is balanced across the carriers. The performance of the carriers should be similar. Each CDMA carrier can be viewed as a separate CDMA system which needs to be monitored.
June 2001
S S
3-24
S Analyze the new site with respect to the surrounding sites. Make
adjustments to the surrounding sites, if required.
June 2001
3-25
Introduction
Before planning the BTS network, the Systems Engineer needs an awareness of the various different Motorola BTS products at their disposal. There are differences in the BTS products which may make one BTS product more suitable for an application as opposed to another BTS product. The Systems Engineer needs to weigh all of these factors, in addition to the customer s desires, when selecting the appropriate BTS product. The following highlights some of the differences between the available BTS products: S Spectrum of Operation 800 MHz 900 MHz 1700 MHz 1900 MHz S Site Configuration Omni Threesector Sixsector S Mixed Mode (CDMA/Analog) Operation S Size and Number of Frames
S Power Amplifier
Enhanced Linear Power Amplifier (ELPA) Single Tone Linear Power Amplifier Trunked LPA S Tower Top Amplifier
S Number of CDMA Carriers Supported per Frame or cabinet S Number of Channel Elements Supported.
Certain products are meant for different types of applications. For example: S Only a few BTS products support a mixed mode (Analog and CDMA) configuration (SC9600, SC2400) S The SC611 is designed mainly for spot coverage
described, however, and other products may resemble those which are listed below. The BTS specifications and descriptions in this section are based on the current structure of the various BTS CDMA products.
SC9600
The SC9600 CDMA BTS is a three frame (minimum), indoor base station designed to support medium to highdensity cell sites. These frames include the:
S Analog (AMPS/NAMPS) supports only analog subscriber units S Code Division Multiple Access (CDMA) supports only CDMA
subscriber units
June 2001
3-27
Carrier 3
BBX MCC GLI
Shelf 6 LPA Shelf 3 Shelf 5 Shelf 4 LPA Shelf 2 Shelf 3 Shelf 2 LPA Shelf 1 Shelf 1 ELPA Frame
CCP 2 Carrier 4
BBX MCC GLI
SC9600 CDMA Carrier Support The CDMA Only SC9600 BTS Hardware can be equipped with up to two Modem Frames, two LPA frames or two ELPA Frames, and one SIF to support a maximum of eight CDMA carriers. One mixed mode (CDMA and analog) SC9600 Modem Frame supports one CDMA carrier. Alternatively, the SC4812 Expansion Modem Frame (no LPAs) may be used as the SC9600 Modem Frame expansion. Table 3-4: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames 4 1 1 N/A 4 (see Note)
NOTE
Basic site equipment is able to support up to four RFMFs. The amount of frequency spectrum available may limit the number of CDMA carriers and, therefore, the number of frames needed. SC9600 Channel Element Support The MCC8 card contains the circuitry necessary to implement CDMA channels of any type specified in the IS95 standard, except the pilot channel. The supported channel types are the:
Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame
Each CCP shelf can be connected to two span lines, or a total of eight span lines for an RFMF with all four CCP shelves installed. SC9600 RF Cabling When two RF Modem frames feed a single LPA or ELPA frame, a Dual LPA TX Input kit must be installed on the top of the LPA or ELPA frame. The installation takes place after the frames are mounted but before installing the cabling. Install the Dual LPA TX Input kit by following the procedure given in the Dual LPA TX Input Kit manual. When more than two RF Modem frames feed a single LPA or ELPA frame, a MultiInput Combiner Kit must be installed on the top of the LPA or ELPA frame. The installation will take place after the frames are mounted but before the cabling is installed. When more than thirty IP addresses are required, a RFM LAN Repeater Option must be installed on the top of the Expansion RF Modem frame. The installation will take place after the frames are mounted but before the cabling is installed. Install the RFM LAN Repeater Option by following the procedure given in the RFM LAN Repeater Option manual. For multiple RF Modem frame systems, there are two transmit cabling philosophies: S Combine the output of the RF Modem frames at the input of the ELPA/LPA (using the Dual or MultiPort LPA TX Input Option). This shares the ELPAs/LPAs and antennas between the RF Modem frames.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-29
The recommended orders of the frames for single RF Modem frame systems are shown in Figure 3-2. Figure 3-2: Single RF Modem Frame Mounting Order
RF Modem Frame
SIF
SIF
RF Modem Frame
For sites that require the LAN Repeater option, the general rule is: S Keep the Master RF Modem frame and all LPA (or ELPA) frames on the same side of the LAN Repeater Option (same Ethernet LAN).
S Keep the expansion RF Modem frames and SIF on the other side of
the LAN Repeater Option (same Ethernet LAN). The recommended orders of the frames for multiple RF Modem frame systems are shown in Figure 3-3. ELPA frames must not be mounted next to any other rearexhaust frame (like another ELPA). Figure 3-3: Multiple RF Modem Frame Mounting Order
SIF
SIF
SC9600 Power Amplifier Capabilities Each SCLPA Frame can house up to three SCLPAs and is capable of supporting up to threesectors. Two SCLPA Frames (with three SCLPAs each) can be used to support sixsector sites. NOTE The SCLPA hardware is no longer available.
3-30
June 2001
Up to two SCLPAs can operate on each sector, or up to a total of six SCLPAs in a threesector cell with two TX antennas per sector. A sixsector cell may expand to up to 12 SCLPAs (or four SCLPA frames). However, once the number of SCLPAs exceeds six, a second SIF and RFDS is required. (If the RFDS is not used, a second SIF is not required.) SC9600 SCLPAs are available as either high power (125W) or low power (70W). The SC Series Expandable Linear Power Amplifier (ELPA) is a multicarrier linear power amplifier which is effective at large, capacitylimited cell sites where combining many channels onto a common antenna is desirable. Motorola ELPAs can support both linear and nonlinear modulation formats. This means that it is possible to use an ELPA to combine and amplify both analog and digital carriers in a cell site and transmit with the same antenna. The ELPA amplifier supports all known techniques of modulation, including both wide band and narrow band FDMA, TDMA, and CDMA. The ELPA frame is designed to replace existing SC9600 LPA products. One ELPA frame can replace two SC9600 LPA frames containing the same number and type of inputs and outputs at the top of the frame(s). The ELPA frames can contain from one to six ELPA shelves. Each shelf can support from two to four ELPA modules. Each shelf represents a sector, which can be placed on its own individual antenna or combined with other sectors on a single antenna. Two ELPA Frames can be supported per cellular base station or BTS site. Minimum number of ELPAs at a BTS site The following is the minimum number of ELPAs required for each type of site transmit antenna system:
S Omnitransmit site
At least one shelf with a minimum of two ELPA modules installed (one ELPA frame). The minimum number of modules for this site configuration is two.
will be derated from 120 W. Refer to the ELPA Functional Description or CDMA RF Planning Guide for further information concerning the derated power. Multiple ELPA Modules on a sector If the desired number of RF carriers and the per carrier power output to be used on a sector exceeds the limits of two ELPA Modules, it is necessary to equip the sector with additional ELPA Modules. The standard maximum number of ELPA Modules per sector is four. The ELPA Multicage option allows the standard maximum of four ELPA Modules per sector to increase to eight modules per sector by combining two shelves. This option requires additional hardware to couple shelves together in pairs. Maximum ELPAs at a Site The ELPA RF output power varies depending on the number of modules within a sector. In practical applications, the RF carrier capacity of the sectors at most sites requires the minimum number of ELPA Modules. There are many applications with some sites having certain sectors equipped with several ELPAs for additional RF carrier capacity. If a site requires multiple ELPA Frames, the maximum number of ELPA Modules at a BTS site is 48 (two frames with a total of 12 ELPA shelves or six Multicages). Each ELPA Frame sector power output is generated from the equipped ELPA Modules of one or two (Multicage option) shelves. Standard configurations allow for 60, 90, or 120 Watts per sector. The Multicage option allows for 100, 150, or up to 200 Watts per sector. A sector s power can be increased by adding more ELPA Modules. The Multicage option combines the power of two ELPA shelves per sector. It can be ordered from the factory new or can be retrofit in the field. Table 3-6: Output Power/Sector vs. Number of Modules Number of ELPA Modules Maximum Output Power Per Sector (at Top of Frame) 234 RF Network Configuration 2 3 4 6 8 60 Watts 90 Watts 120 Watts N/A N/A 468 RF Network Configuration N/A N/A 100 Watts 150 Watts 200 Watts
NOTE
A minimum of two ELPA modules is required for each sector to provide soft fail redundancy. Multicage option supports the 468 RF Network configurations.
3-32 CDMA SC Products System Resource Guide (CSSRG) June 2001
S SC9600 Hardware Installation, Analog/CDMA S SC9600 RF Modem Frame (RFMF) Functional Description S SC9600 Site Interface Frame (SIF) Functional Description S SC9600 Linear Power Amplifier (LPA) Functional Description S SC9600 ELPA Functional Description S SC9600 BTS Optimization/ATP S SC9600 BTS Field Replaceable Unit (FRU) Procedure.
SC4800 (excluding the SC4812)
The Motorola SC4800 is provided for either an indoor or outdoor configuration. The SC4800 model represents the standard model installed and housed inside a customerdesignated cell site. The SC4800E model is designed for direct outdoor installations. The SC4800 indoor base station supports medium to high density cell sites in a single frame. The SC4800 CDMA BTS supports either omni transmit/omni receive or threesector transmit/threesector receive. The SC4800 frame can hold up to two CDMA Channel Processor (CCP) cages (also referred to as shelves). Each cage supports one omni or threesector CDMA carrier. Each of these cages, or CDMA Channel Processing Shelf (CCP), house the control cards, channel processing cards, and transceivers required to support one CDMA carrier. One linear singletone power amplifier cage is installed for each CDMA carrier. For each CCP cage equipped, there is a corresponding Linear Power Amplifier (LPA) shelf. The SC4800E enclosure provides a weatherresistant, vandalresistant, selfcontained BTS mounted on a prepared site. In order to fully configure and install the system, its necessary to route the AC power, telephone span lines, and RF antenna cables to the appropriate entry point of the SC4800E. The SC4800E BTS comes equipped with dual Environmental Control Units (ECUs) that control heating and cooling of the components inside. The SC4800/4800Es are delivered in the following model types and all
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-33
operate in the North American PCS frequency bands: S SC4850 S SC4852 S SC4852R S SC4850E S SC4852E S SC4852ER
In addition, the SC4820 and SC4820E operate in the Korean PCS frequency bands. S SC4820 S SC4820E. The E version corresponds to outdoor enclosures. The R version incorporates the required equipment to support Tower Top receive Amplifiers (TTA) and optional 40 Watt transmit output. There are also expansion frames for the SC4852 and SC4820. The expansion frames provide the capability to add more than two CDMA carriers to a cell site. Figure 3-4: SC4800
Distribution Shelf Carrier 2
BBX MCC GLI
Carrier 1
BBX MCC GLI
CCP 2
RF Modem Frame
SC48xx CDMA Carrier Support An SC4800 BTS can support up to two CDMA carriers. Each CCP shelf (or, cage) supports one CDMA carrier. If needed, up to three expansion frames can be added to the first SC4800 BTS frame. The SC485X expansion frames are identical to the first frame except for the RF connection and distribution. In a maximum configuration, this allows for 8 CDMA carriers. For the SC4800E, two additional enclosures can be installed for a maximum configuration of six CDMA carriers. Alternatively, the SC4812T may be used to expand SC485X sites and the SC4812ET to expand SC485XE sites.
3-34 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 3-8: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames: SC48xx SC48xxE SC48xx Channel Element Support The channel element support is provided by the MCC8 card, same as in the SC9600, in the CCP cages of the SC4800. The MCC channels can be pooled across the sectors within a given CCP cage, but cannot be pooled across cages. In other words, the MCC cards are dedicated to a cage and carrier frequency. Table 3-9: Physical Traffic Channels Physical Traffic Channels per MCC24 Physical Traffic Channels per MCC8 Minimum Number of MCC/Shelf N/A 8 1 per sector + 1 for redundancy 17 136 2 272 2 1 1 N/A 4 3
Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame SC48xx RF Cabling
The SC4800 frame is capable of supporting a maximum of six receive antenna input ports. Two RX (Ntype) connectors are provided for each sector within a cell, using a diversity receive scheme that minimizes signal fading. This provides threesector operation with full diversity receive. The Expansion Frames receive input signals from the Starter Frame through an expansion cable that connects the ports (EXP1, EXP2, or EXP3) on the Starter Frame to the appropriate ports on the Expansion Frame. There is a maximum of six transmit antenna ports: three for the first carrier and three for the second carrier. Figure 3-5 and Figure 3-6 demonstrate the transmit combining that can be used to combine up to eight carriers on a single set of antennas. Use a 4:1 or 2:1 cavity combiner to combine four or two nonadjacent CDMA carriers onto a single TX antenna. Use a combiner only when the carriers
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-35
to be combined are not adjacent (alternate). The combiner for the SC4800 is external to the frame. Figure 3-5: Combiner 2:1
Duplexer
Duplexer
3
To RX A To RX B 2:1 Combiner 2:1 Combiner
F1
F3
F2
F4
Duplexer
Duplexer
F1
F3
(F5) (F7)
F2
F4 (F6) (F8)
Maximum spacing between a Starter and Expansion Frame is limited by the 15.5 foot intercabinet cable between frames. Each Expansion Frame requires its own GPS and LFR (if used) Antenna. SC48xx Power Amplifier Capabilities The lower section of the SC4800 frame can contain one or two Linear Power Amplifier (LPA) shelves. The top LPA shelf is associated with the first CDMA carrier, positioned in the right cage. LPAs for the second CDMA carrier are in the bottom LPA shelf. This is the same whether the carriers are omni or threesector. Each sector requires two single tone Linear Power Amplifier (LPA) modules which operate in parallel. The module outputs are combined and filtered before being routed to the top of the frame. Together, the
3-36 CDMA SC Products System Resource Guide (CSSRG) June 2001
LPA modules produce 20 watts of average output power per sector. Add two additional LPA modules to provide a total of 40 watts per sector. This is especially useful for link balance on the extended range models (those with the Tower Top Amplifier, or TTA). The 20 Watts of average output power per sector holds true for all SC48XX models except the extended range models (SC4852R/4852ER) which offer 3040 watts per sector. There are up to four linear power amplifiers (LPAs) per sector combined in softfail redundancy. In softfail redundancy, if an LPA module fails, the sector is not out of service but operating at reduced power. Each SC4850 and SC4820 amplifier delivers 7.5 Watts. Each SC4852 amplifier delivers 10 watts. The SC4850 and SC4852 amplifiers can be mixed without adverse affects. Each amplifier operates independently. SC48xx Operating Frequency Table 3-10 shows the operating frequencies of this BTS product. Table 3-10: SC4852/4850/4820 Operating Frequencies Base Receive (MHz) SC4820 SC485x 1750 to 1780 1850 to 1910 Base Transmit (MHz) 1840 to 1870 1930 to 1990
SC48xx Documentation The following is a list of documentation, available from Motorola, which provides further detail on this BTS product: S SC4800 Hardware Installation
S S S S S S
SC4812
SC4800/4800E BTS Functional Description SC4800E BTS Indoor Outdoor Enclosure Hardware Installation SC4800/4800E BTS Optimization/ATP SC4800 BTS Field Replaceable Unit (FRU) Procedure SC4800 CDMA 2nd Carrier Installation SC2450/4850/4852/4820 Starter Frame to Expansion Frame Conversion.
The SC4812 single frame CDMA BTS is an 800 MHz High Capacity, indoor, CDMA base station product designed to support medium to high density cell sites.The Motorola SC4812 Base Transceiver Subsystem (BTS) starter frame contains RX frontend and LPAs housed in one frame. An expansion frame may be added to the SC4812 starter frame for increased carrier and channel capacity. The SC4812 Standalone Frame (SAF) is designed for use with internal singletone LPAs. The SC4812 CDMA BTS can be configured as an omni transmit/omni receive, threesector transmit/ threesector receive, or sixsector transmit/sixsector receive site.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-37
The SC4812T BTS is available as an 800 MHz or 1900 MHz indoor BTS designed for use with internal singletone LPAs. The SC4812T uses a new RF trunking technique that reduces the number of LPAs required and provides increased forward power capability. The SC4812T (800 MHz) replaces the nontrunked version of the SC4812, SC2450, CDMA SC2400 with ELPA, and the CDMA SC9600. The SC4812T (1900 MHz) replaces the SC485X BTS. There is also an outdoor version of the SC4812T, the SC4812ET, available in both the 800 MHz and 1900 MHz frequency bands. The trunked LPA cage, trunking module, and trunked LPA sets will not be available to retrofit in the product that was originally shipped with the conventional SC4812 (in other words, nontrunked) LPA scheme. Figure 3-7: SC4812
Carrier 1, (2)
BBX MCCE, GLI
Carrier 3, (4)
BBX, MCCE, GLI
CCP 1
LPA Cages
SC4812 CDMA Carrier Support The SC4812T (800 MHz) supports up to four CDMA carriers per frame in omni through threesector configuration and up to two CDMA carriers per frame in four through sixsector configurations (nonadjacent carriers). SC4812T (800 MHz) sites can expand to a maximum of two frames for a total of eight CDMA carriers per omni or threesector site or up to four CDMA carriers per sixsector site. The SC4812T (1900 MHz) supports up to four CDMA carriers per frame in omni through threesector configurations and up to two CDMA carriers per frame in four through sixsector configurations (nonadjacent carriers). SC4812T (1900 MHz) sites can expand to a maximum of three frames for a total of 12 CDMA carriers for a threesector site or up to six CDMA carriers for a sixsector site. The single SC4812 Combined CDMA Channel Processor (CCCP) cage supports up to a total of twelve sectorcarriers (for example, threesector, fourcarrier or sixsector, twocarrier).
3-38 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 3-11: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames: SC4812T 800 SC4812T 1900 SC4812 Channel Element Support The MCC24 and MCC8E (EMAXX) cards contain the circuitry necessary to implement CDMA channels of any type specified in the IS95A standard, except the pilot channel. The supported channel types are the: 1 4 4 2 2 3
S S S S
A single CDMA channel on an MCC card is referred to as a channel element. An MCC8E supports up to eight channel elements while MCC24 supports up to twentyfour channel elements. The MCC channels are pooled within a given CCCP cage. Since the CCCP cage can serve more than one CDMA carrier, the MCC cards are shared between all of the carriers and sectors in that cage. Channel Elements are shared across carriers and sectors within a frame with up to 288 physical channels per frame (assuming 12 MCC24E cards). These twelve MCC cards are treated as a one large trunk group of channels that can be used by any sector and any carrier within the CCCP cage. Table 3-12: Physical Traffic Channels Physical Traffic Channels per MCC24 Physical Traffic Channels per MCC8 Minimum Number of MCC/Shelf: Threesector Sixsector Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame
June 2001 CDMA SC Products System Resource Guide (CSSRG)
24 8 2 3 12 288 1 288
3-39
Because the SC4812T uses a single cage design with only 12MCC slots available, use the MCC24 in place of the MCC8E to provide added capacity across all the carriers within the frame. Choosing either the MCC24 or the MCC8E also provides the ability to grow at different increments since both, the MCC24 and MCC8E can be intermixed in the cage. NOTE
The original MCC8 is not compatible with the SC4812T family due to the new EMAXX and sixsector capable design features. Therefore, if a system has a mixture of SC4812s and some other BTS product, separate channel element spares are required.
SC4812 RF Cabling There are a maximum of twelve receive antenna input ports and a maximum of six transmit antenna ports. The BTS requires two MPC cards. The expansion and modem frame require two EMPC cards. Use a 4:1 or 2:1 cavity combiner to combine four or two nonadjacent CDMA carriers onto a single TX antenna. NOTE A combiner can be used only when the carriers that need to be combined are not adjacent (in other words, alternate channels).
Odd channels can be combined on one antenna and even channels on another. These combiners are installed in the SC4812 frame; a separate frame is not required. Figure 3-8 illustrates the use of the 2:1 and 4:1 combiners.
3-40
June 2001
BP
BP
BP
3
F1
SC4812
F1
F2
SC4812
F1 F3
F2
SC4812
F1 F3
F2 F4
SC4812
1 Carrier
2 Carrier
3 Carrier
4 Carrier
F1 F3 F5 F7
SC4812
F2 F4 F6 F8
SC4812 Exp.
8 Carrier
2:1 Combiner 4:1 Combiner
BP
SC4812 Power Amplifier Capabilities The SC4812T uses a Trunking Module and a set of four LPA modules per threesectors of one carrier to provide 20 watts simultaneously per carriersector post duplex (60 watts total for a threesector, one carrier BTS). Trunked Power is supported on BSS CDMA Release 2.8.1/2.8.3. Like trunked channels, trunking LPAs enables the BTS station to serve more traffic with fewer physical resources. For instance, in the nontrunked design, a single carrier is typically served by six LPA modules. A trunked LPA serves the same configuration with four modules, thereby improving both power consumption and reliability. The power consumption savings are simply due to the reduction in the number of modules. Even when serving little or no traffic, LPA modules consume considerable power. Therefore, the elimination of two modules per carrier reduces the average power consumption of the base station considerably. Another significant benefit of trunking is operational flexibility. The nature of CDMA provides that when the surrounding sites/sectors are lightly loaded, any particular sector can carry a load well over its design
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-41
capability. Trunked power enables LPA power to be directed to any sector in nearly any ratio. Therefore, when one sector of the site needs more power than is typical, it can borrow power instantaneously from the other sectors of the site not experiencing a peak load. Without this feature, the additional traffic goes unserved. This ability to handle traffic peaks that would otherwise go unserved allows operators to generate more revenue with Motorola infrastructure than with that of competitors.
The Conventional (NonTrunked) SC4812 frame cannot be upgraded to the trunked SC4812T. Each SC4812T CDMA frame can be equipped with up to two trunked LPA (TLPA) shelves, which are also known as cages. Each shelf contains two trunked LPA Sets. Each SC4812T CDMA frame can be equipped with up to four trunked LPA Sets. Each trunked LPA Set consists of four LPA modules, two fans, and a trunking module. A trunked LPA Set provides 60W of TX power (at the top of the frame post duplexer) shared among threesectorcarriers (in other words, threesectors of one carrier). The trunking module dynamically allocates power across sectors as the subscriber load changes. The variable nature of CDMA transmit power requirements means that at any point in time one or more sectors are likely to be experiencing less than a peak load. Therefore, when any sector needs more power than is typical, it can borrow power instantaneously from sectors not experiencing a peak load. A single sector can have a maximum of 40 Watts available for its use as long as the other sectors have a very light load of traffic. SC4812 Operating Frequency Table 3-13 shows the operating frequencies of this BTS product: Table 3-13: SC4812 Operating Frequencies Base Receive (MHz) SC4812T SC4812 /T 1850 to 1910 824.70 to 848.31 Base Transmit (MHz) 1930 to 1990 869.70 to 893.31
SC4812 Documentation The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this BTS product.
S S S S S
3-42
SC4812 BTS Hardware Installation SC4812 BTS Functional Description SC4812 BTS Optimization/ATP SC4812 BTS Field Replaceable Unit (FRU) Procedure SC4812T BTS Hardware Installation
June 2001
SC4812T BTS Optimization/ATP SC4812T BTS Field Replaceable Unit (FRU) Procedure SC4812T Expansion/Modem Frame Install SC4812ET BTS Hardware Installation SC4812ET BTS Optimization/ATP SC4812ET BTS Field Replaceable Unit (FRU) Procedure SC4812ET Battery/Heater Installation.
The SC2450 CDMA BTS is a single frame, indoor base station designed to support medium to highdensity cell sites. Each CCP cage contains the control cards, channel processing cards, and transceivers required to support one CDMA carrier. One singletone linear power amplifier (STLPA) shelf is required per CDMA carrier. A twocarrier BTS must therefore be equipped with two CCP cages and two STLPA shelves. The SC2450 CDMA BTS supports the 800 MHz CDMA air interface in either omni transmit/omni receive or threesector transmit/threesector receive configurations. The SC2450 platform allows for the combination of two, three, or four SC2450 frames at a single cell site utilizing the same set of antennas (when properly combined utilizing combiners and duplexers). Expansion allows for the combination of up to eight CDMA carriers at a single cell site. Figure 3-9: SC2400
Carrier 1
BBX MCC GLI
Carrier 1
BBX MCC GLI
CCP 2
CCP 2
SC2450 CDMA Carrier Support Each SC2450 CDMA frame supports up to two CDMA RF (CCP) cages, and each CCP cage provides one CDMA carrier in either an omni or threesector configuration. The mixed mode (CDMA and analog) SC2400 frame supports a maximum of one CDMA carrier.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-43
Table 3-14: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames 2 1 1 N/A 4
3
SC2450 Channel Element Support The MCC8 card contains the circuitry necessary to implement CDMA channels of any type specified in the IS95A standard, except the pilot channel. The supported channel types are the:
S S S S
A single CDMA channel on an MCC 8 is referred to as a channel element, and an MCC8 supports up to eight channel elements. The MCC channels can be pooled across the sectors within a given CCP cage, but cannot be pooled across cages. In other words, the MCC cards are dedicated to a cage and carrier frequency. Table 3-15: Physical Traffic Channels Physical Traffic Channels per MCC24 Physical Traffic Channels per MCC8 Minimum Number of MCC/Shelf N/A 8 1 per sector + 1 for redundancy 20 160 2 320
Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame SC2450 RF Cabling
Up to four TX carriers can be combined onto one antenna with a 2:1 or 4:1 transmit combiner. The combiner for the SC2450 is external to the frame. SC2450/SC2400 Power Amplifier Capabilities The lower section of the SC2450 frame can contain one or two Linear Power Amplifier (LPA) shelves. The top LPA shelf is associated with the
3-44 CDMA SC Products System Resource Guide (CSSRG) June 2001
first CDMA carrier, located in the right cage position. The second PA shelf is associated with the second CDMA carrier, located in the left cage position. Each sector uses two 12.6 watt Single Tone Linear Power Amplifier (STLPA) modules combined in the Combiner/Filter unit. A softfail redundancy scheme is used to achieve the desired 20 Watt CDMA carrier power. The two STLPA modules are placed in adjacent slots in the PA shelf. Each STLPA is independently controlled and monitored. When an STLPA module fails, it takes itself out of service, and the total carrier power then drops to 5 Watts (by about 6 dB). The SC2400 ELPA retains all of the features offered by single channel amplifiers (in other words, output power level control) while adding new capabilities, such as the elimination of standardized channel spacing. The SC2400 ELPA units are also compatible with mixed mode operation, such that a customer using both analog and CDMA carriers in a cell site can use an ELPA module to combine and amplify both types of carriers and transmit on the same antenna. The lower section of the SC2400 frame can contain up to three ELPA shelves for threesector configurations (one shelf per sector) or up to two ELPA shelves for omni configurations. In a threesector configuration, the bottom ELPA shelf is associated with sector 1, the middle ELPA shelf is associated with sector two and the top ELPA shelf is associated with sector three. There are two to four 30W ELPA modules per shelf. Failure of any one module does not reduce the performance of the other modules. However, it limits the output power capability of the sector. The number of ELPA modules in the sector determines the total output power capability for the sector. SC2450 Operating Frequency Table 3-16 shows the operating frequencies of this BTS product: Table 3-16: SC2450 Operating Frequencies Base Receive (MHz) 824.70 to 848.31 SC2450 Documentation The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this BTS product. Base Transmit (MHz) 869.70 to 893.31
S S S S
BTS Hardware Installation, SC2400 CDMA 800/900 MHz BTS Functional Description, SC2400 CDMA 800/900 MHz BTS Optimization/ATP, SC2400 CDMA 800/900 MHz BTS Field Replaceable Unit (FRU) Guide, SC2400 CDMA 800/900 MHz
3-45
June 2001
The SC6x4 is a selfcontained, standalone base station. All ancillary equipment required to support a typical cell site installation is included in the SC6x4. The SC604 version is an older version of this BTS product but functions similarly to the SC614. The T version incorporates trunked PAs and operates in the 1.9 GHz PCS spectrum of operation. The SC6x4 supports one complete CDMA carrier in a twosector or threesector configuration with N+1 redundancy. A second carrier is supported by adding a second SC6x4 and cabling it to the first unit, maintaining the minimum two antennas per sector. Configurations above two carriers are supported by adding additional antennas and cabinets. An onni SC614 at 800 MHz is available. The omni configuration is upgradable to two and threesector configurations through OmniSector Expansion and Growth Sector upgrades. Unless specifically mentioned, the SC614 designation applies for the SC614, SC614T, and the SC604. SC614 CDMA Carrier Support A second carrier is added to a site by adding an expansion enclosure. The expansion enclosure is identical to the starter enclosure except for the RF connection and distribution. Table 3-17: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames 1 1 1 N/A 4
NOTE
The maximum number of four CDMA cabinets is dictated by the logical BTS feature up to four carriers can be viewed logically as one cell site. The maximum number of receive paths in the RXDC is three, so a four carrier site looks like two 2 carrier sites from an RF plumbing perspective. There are two expansion frame configurations so it depends on what carrier is being added to determine which expansion frame type to order. The span line can be daisy chained up to the maximum number of DSOs available on the span line (not dependent on the number of 614/Ts) and the Remote GPS/HSO can be daisy chained up to five 614/Ts.
3-46 CDMA SC Products System Resource Guide (CSSRG) June 2001
Maximum Number of MAWI/Cabinet Maximum Physical Traffic Channels/Cabinet Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame SC614 RF Cabling
The SC614 uses a dedicated pair of LPAs for each of the threesectors. The two LPA modules are phase coupled by means of the Splitter/Combiner (S/C) module, which splits the TRX drive into two equal components for application to the LPA module inputs and combines the amplified outputs of the LPA modules for transmission via the antenna. The use of two LPA modules per sector provides a failsoft capability.
June 2001
3-47
TRX MAWI
SC614(T)
TRX MAWI
SC614(T)
TRX MAWI
SC614(T)
1 Carrier
2 Carrier
TRX MAWI
SC614(T)
TRX MAWI
SC614(T)
TRX MAWI
SC614(T)
3 Carrier
Duplexer
The SC614T uses four LPA modules in a trunked configuration. All threesectors share the resources of the trunked LPA bank. The trunking technique allows more efficient use of the total available LPA power capability than conventional approaches using dedicated LPA modules for each of the threesectors. The use of multiple LPA modules in the power amplifier assembly also prevents total loss of power in the event of a single point failure. Failure of a single LPA module reduces power output by approximately 1.5 dB across all threesectors. Timing information is derived from the GPS satellite signals by means of a remotely located GPS head, which contains a GPS engine, antenna, and digital interface circuitry. Communication between the Remote GPS (RGPS) head and the BTS is provided by an RS485 link that allows up to 2000 feet of physical separation between the BTS and the RGPS unit. A single RGPS head can supply timing signals for multiple SC614 /T BTS cabinets connected in a Master/Slave/Slave configuration. SC614 Power Amplifier Capabilities The SC614 provides a maximum of 20 Watts of continuous power per sector (two LPAs per sector, with each LPA producing 10 Watts). The SC614T uses the LPA trunking modules to provide 16 watts simultaneously per carriersector post duplex (48 watts total for a
3-48 CDMA SC Products System Resource Guide (CSSRG) June 2001
threesector, one carrier BTS). Trunked Power is supported on BSS CDMA Release 2.8.1/2.8.3. Like trunked channels, trunking LPAs enables the BTS station to serve more traffic with fewer physical resources. A single sector can have a maximum of 40 Watts available for its use as long as the other sectors have a very light load of traffic. SC614 Operating Frequency Table 3-19 shows the operating frequencies of this BTS product: Table 3-19: SC614 Operating Frequencies Base Receive (MHz) SC614T SC614 1850 to 1910 824.70 to 848.31 Base Transmit (MHz) 1930 to 1990 869.70 to 893.31
SC614 Documentation The following is a list of documentation, available from Motorola, which provides further detail on this BTS product:
S S S S
SC611/SC601
SC614/614T BTS Hardware Installation SC614/614T BTS Optimization/ATP SC614/614T BTS Field Replaceable Unit (FRU) Procedure SC614T Second Carrier Instruction Manual.
The SC6x1 products support a maximum of four carriers per site (only for one sector; in other words, omnisite). Additional cabinets can be located at the same physical site location but this additional equipment is treated as a separate BTS entity. The SC601 version is an older version of this BTS product but functions similarly to the SC611. The SC611 is a selfcontained base station for either indoor or outdoor installations. It is designed for microcell applications such as infill coverage, underground and inbuilding applications where space and installation flexibility are tantamount. The SC611 supports one CDMA carrier (omni) configuration and is expandable to four CDMA carriers through the addition of SC611 Expansion Frames. SC611 CDMA Carrier Support The SC611 supports one complete CDMA carrier in an omni (single sector) configuration but with no redundancy. A second carrier is supported by adding a second SC611 and cabling it to the first unit, maintaining the minimum two antennas per sector. Configurations above two carriers are supported by adding additional antennas and cabinets. A second carrier is added to a site by adding an expansion enclosure. The expansion enclosure is identical to the starter enclosure except for the RF connection and distribution.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-49
The SC611 Expansion Frame allows the SC611 to be expanded to two carriers using only two antennas and up to four carriers using four antennas. The Logical BTS feature for threedigit BTS products allows up to four SC611 BTS units to be configured as one fourcarrier cell site on BSS CDMA Release 2.9.2. However, softer handoffs wont be supported between multiple SC611 BTS units in a sectorized deployment. The SC611 Expansion Frame supports 800 MHz, 1.7 MHz, and 1.9 GHz frequency bands.
Table 3-20: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames 1 1 N/A N/A 4
NOTE
The maximum number of four CDMA cabinets is dictated by the logical BTS feature up to four carriers can be viewed logically as one cell site. There is only one expansion frame configuration and can be daisy chained together for as many carriers as desired. The span line can be daisy chained up to the maximum number of DSOs available on the span line (not dependent on the number of 611s) and the Remote GPS/HSO can be daisy chained up to 10 611s. SC611 Channel Element Support The MAWI is the central controller and data processing module. It integrates many functions of the current SC CDMA platforms onto a single field replaceable unit. There are two sizes for the MAWI card, either a 16channel element or a 36channel element card. The SC611 is capable of physically supporting 16 or 36 physical channels. Table 3-21: Physical Traffic Channels Physical Traffic Channels per MAWI36 Physical Traffic Channels per MAWI16 Minimum Number of MAWI/Cabinet Maximum Number of MAWI/Cabinet Number of CDMA Shelves in Cabinet Maximum Physical Traffic Channels/Cabinet SC611 RF Cabling The configuration of either one SC611 and one SC611 Expansion Frame or two SC611 Expansion Frames shares receive paths in order to maintain a minimum of two antennas per twocarrier cell site. One antenna is required for each additional SC611 BTS supporting from
3-50 CDMA SC Products System Resource Guide (CSSRG) June 2001
36 16 1 1 1 36
three to four carriers. The SC611 Expansion Frames connect to the SC611 Starter Frame similarly as the SC614 configurations. SC611 Power Amplifier Capabilities The SC611 provides a maximum of seven Watts of continuous power. SC611 Operating Frequency Table 3-22 shows the operating frequencies of this BTS product. Table 3-22: SC611 Operating Frequencies Base Receive (MHz) 1850 to 1910 1750 to 1780 824.70 to 848.31 SC611 Documentation The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this BTS product. Base Transmit (MHz) 1930 to 1990 1840 to 1870 869.70 to 893.31
S S S S S
SC300
SC611 CDMA BTS Hardware Installation SC611 CDMA BTS Functional Description SC611 (1.9 GHz) CDMA BTS Optimization/ATP SC611 (1.7 GHz) CDMA BTS Optimization/ATP SC611 (800 MHz) CDMA BTS Optimization/ATP.
The SC300 is an omni, single carrier product. The SC300 portfolio includes two Field Replaceable Units (FRUs) with two different power output options. The PicoCell provides up to 200 mW of transmit power out and the MicroCell provides up to 10 Watts of transmit power out. The PicoCell is ideal for low power applications such as subway, underground, or inbuilding areas. For higher power applications such as rural or hole filling areas, the MicroCell can be deployed. The MicroCell FRU is similar to the PicoCell FRU, however it includes a power amplifier to increase the maximum transmit power level to 10 Watts and the necessary circuitry to support receive diversity. SC300 CDMA Carrier Support The SC300 currently supports one complete CDMA carrier in an omni (single sector) configuration with no redundancy. A second carrier can be added to a site by adding an additional FRU. The SC300 can support up to four CDMA carriers by daisychaining four FRUs.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-51
Table 3-23: CDMA Carrier Support Number of Shelves per BTS Cabinets Number of Carrier per Shelf Omni Number of Carrier per Shelf Three Sector Number of Carrier per Shelf Six Sector Maximum Number of CDMA Cabinets 1 1 N/A N/A 4
3
SC300 Channel Element Support The MicroCell/PicoCell FRU contains the RF equipment, channel elements, backhaul interface, alarming, and a power supply to support a single omni/onesector carrier. An optional High Stability Oscillator (HSO) is also available for maintaining synchronization for up to 24 hours, if the loss of the Global Positioning System (GPS) signal should occur. The maximum number of physical traffic channels that can be supported by an SC300 FRU is 32 channels. Table 3-24: Physical Traffic Channels Physical Traffic Channels per MicroCell FRU Physical Traffic Channels per PicoCell FRU Minimum Number of FRUs/Cabinet Maximum Number of FRUs/Cabinet Number of CDMA Shelves in Cabinet Maximum Physical Traffic Channels/Cabinet 32 32 1 1 1 32
SC300 RF Cabling The Site Input/Output (I/O) and Junction Box acts as the main interface between the FRU and external connections. The external interfaces are categorized in the following four main functional areas:
Figure 3-11: Multiple Carrier PicoCell RF Antenna Configuration Tx/Rx Tx/Rx Tx/Rx Tx/Rx
FRU F1
FRU F2
FRU F3
FRU F4
1 Carrier Tx/Rx Rx
Tx/Rx
2 Carriers Tx/Rx T T
FRU F1
T T = 50 Ohm Terminator
FRU F1
Rx
FRU F2
Tx/Rx T
3 Carriers Tx/Rx T
Tx/Rx
Rx
FRU F1
Rx
FRU F2
FRU F3
T T = 50 Ohm Terminator
June 2001
3-53
4 Carriers Tx/Rx T
3
Tx/Rx T
Tx/Rx T
Tx/Rx T
FRU F1
Rx
FRU F2
FRU F3
Rx
FRU F4
T = 50 Ohm Terminator
SC300 Power Amplifier Capabilities As stated earlier, the SC300 can be ordered with two different power output options. The PicoCell provides up to 200 mW of transmit power out and the MicroCell provides up to 10 Watts of transmit power out. SC300 Operating Frequency Table 3-25 shows the operating frequencies of this BTS product. Table 3-25: SC300 Operating Frequencies Frequency Band 800 MHz 1.9 GHz SC300 Documentation The following is a list of documentation that is available from Motorola Technical Education and Documentation that provides further detail on this BTS product: Base Receive (MHz) 824.70 to 848.31 1850 to 1910 Base Transmit (MHz) 869.70 to 893.31 1930 to 1990
S S S S
Reduction of BTS Offerings
SC300 BTS Hardware Installation, ATP, and FRU Procedures CDMA LMF Operator s Guide CDMA LMF CLI Reference Grounding Guidelines.
Many of the BTS products mentioned above are to be phased out. The latest version BTS, the SC4812T is the replacement product. Refer to Table 3-26 to determine the BTS product to use for new sites as well as expansion to an existing site.
3-54 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 3-26: BTS Selection If using this Base Station SC2450 SC4850/52E SC4812 (nontrunked) SC2400 (CDMA) SC9600 (CDMA) SC2400/SC9600 (Mixed Mode) Use this substitute for new sites SC4812T SC4812T/ET SC4812T SC4812T SC4812T SC9600 Analog AND SC4812 Modem Frame SC9600 Analog Use this substitute for expanding sites SC4812TX SC4812TX SC4812TX SC4812TX (Separate LPAs) SC4812T SC9600 Analog OR SC4812 Modem Frame SC9600 Analog OR SC4812 Modem Frame
SC9600 (Analog)
June 2001
3-55
Introduction
The BTS products for Japan have many similarities to the BTS products previously described. Some differences are:
S S S S S S
Support of the Japan CDMA air interface Marinet/LoTACS and HiTACS bands supported SC4840 available in sixsector, threesector, or Omni configurations SC2440 available in threesector or Omni configurations SC340 available in an Omni configuration Filtering and Combining equipage for: JCDMA only Colocated JCDMA and Analog Colocated JCDMA and PDC Colocated JCDMA, PDC and Analog.
SC4840
This product is designed for the Japan market. The SC4840 CDMA BTS is a twoframe, indoor base station designed to support medium to highdensity cell sites. These frames are the Site Interface Frame (SIF) and the SC4840 Frame. Cable entry and exit is at the top of the frames, and all frames are front accessible. The SIF contains the:
S S S S S S S S S S S
Cell Site Filters Multicouplers Duplexers Directional Couplers RFDS. Time synchronization Call processing Multitone Expandable Linear Power Amplifiers (ELPAs) Module Alarm Communication Hub (MACH) cards Base station fault management The dialup modem.
The SC4840 Frame houses the control and radio equipment for:
The SC4840 CDMA BTS supports the Japan CDMA air interface in omni transmit/omni receive, threesector transmit/threesector receive or sixsector transmit/sixsector receive configurations. SC4840 CDMA Carrier Support The SC4840 RFMF and SIF frames can support up to seven carriers in a threesector or Omni configuration or up to four carriers in a sixsector
3-56 CDMA SC Products System Resource Guide (CSSRG) June 2001
configuration. Additionally, a sixsector system can support up to seven carriers by adding a second SC4840 RFMF Frame. The SC4840 RF Modem Frame supports two multiple carrier CDMA shelves. One spanline is routed to each CCP shelf, so two spanlines are supported within the frame. The BBX card supports one sector (diversity receive) and one CDMA carrier. The MCC24E cards support 24 physical traffic channels, the MCC8E cards support 8 physical traffic channels. Table 3-27: CDMA Carrier Support Number of shelves per BTS modem frame Number of carriers per shelf Omni Number of carriers per shelf threesector Number of carriers per shelf sixsector Maximum number of CDMA modem frames 2 4 4 2 4 (see note)
NOTE
Basic site equipment is able to support up to four modem frames. The amount of frequency spectrum available may limit the number of CDMA carriers and, therefore, the number of frames needed. SC4840 Channel Element Support There are two MCC cards available (MCC8E and MCC24E) for the SC4840 Frame. The MCC card contains the circuitry necessary to implement CDMA channels of any type specified in the ARIB STDT53, except the pilot. The MCC8E contains eight channel elements and the MCC24E contains 24 channel elements. Each channel element contains circuitry to provide the CDMA modulation and demodulation for the supported channel types. These are the:
S S S S
Each overhead group uses two channels: 1. Synchronization 2. Paging and access. There is one overhead group required percarrier, persector. A maximum of three overhead groups can be provisioned per MCC card. Traffic channel redundancy is presently supported by equipping N+1 MCCs, where N is equal to the number of traffic supporting MCCs as required. A minimum of one redundant MCC card is needed per CCP shelf. A CCP shelf can be populated with up to twelve MCCs, for a total of 24 MCC cards in the SC4840 Frame. CCP shelves can contain a mixture of
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-57
either MCC version (MCC8E and /or MCC24E). Therefore, a CCP shelf, originally configured with only MCC8Es, can later be expanded with the MCC24E to grow capacity. Channel Elements are shared across carriers and sectors within a CCP12 cage. Pooling of the MCC resources is the same as SC4812, all channel elements can be pooled across all carriers within a CCP12 shelf.
Table 3-28: Physical Traffic Channels Physical Traffic Channels per MCC24 Physical Traffic Channels per MCC8 Minimum Number of MCC/Shelf 24 8 1 per sector + 1 for redundancy 12 288 2 576
Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame SC4840 RF Cabling
The Site Interface Frame (SIF) supports the Marinet, LoTACS, and HiTACS bands and is used with the SC4840 platform. The SIF provides the transmit and receive RF path functions necessary to interface the SC4840 Frame to the antennas. It also contains RF path diagnostic equipment (RFDS). Up to twelve receive and twelve transmit antennas can be brought to the SIF for distribution to the SC4840 Frame. This is sufficient to support omni, three or sixsector configurations. There are three ways to add additional SC4840 frames in a BTS using the logical BTS function:
S Add HiTACS SC4840 BTS to existing LoTACS SC4840 BTS S Add LoTACS SC4840 BTS to existing HiTACS SC4840 BTS S Add a HiTACS expansion SC4840 BTS to existing HiTACS SC4840
BTS. By using the logical BTS feature, up to four Modem Frames can be connected to a single SIF.
3-58
June 2001
Distribution Shelf
BBX, MCC, GLI BBX, MCC, GLI
RFDS
3
Triplexers/Duplexers ELPA Shelves LNAs & Site Filters Site Interface Frame RF Modem Frame
SC4840 Power Amplifier Capabilities The SC4840 Frame supports up to six 2Up ELPA shelves or up to three 4Up ELPA shelves. A single 2Up ELPA shelf is loaded with two ELPA modules and a Bandpass filter which provide the necessary amplification and filtering for the CDMA carriers for a single sector. A single 4Up ELPA shelf is loaded with up to four ELPA modules and a Bandpass filter which provide the necessary amplification and filtration for the CDMA carriers for a single sector. Each SC4840 Frame can support either Single Density ELPA modules in the Marinet and LoTACS band or Single Density ELPA modules in the HiTACS band. Double Density ELPA modules are supported in the HiTACS band only. Double Density ELPA modules can only be used with 2Up ELPA shelves. Single Density and Double Density ELPA modules cannot be mixed in the same ELPA shelf. Marinet/LoTACS modules and HiTACS modules can not be mixed in the same frame, nor can 2Up and 4Up ELPA shelves be mixed in the same frame. The maximum allowable average power is 70 watts per sector using two SD ELPA modules, or 140 watts per sector using four SD ELPA modules or two DD ELPA modules (measured at the top of the SC4840 frame). SC4840 Operating Frequency Table 3-29 shows the operating frequencies of this BTS product. Table 3-29: SC4840 Operating Frequencies Frequency Band Marinet LoTACS HiTACS
June 2001
The RF Modem frame is the interface between the span lines to/from the CBSC. The ELPA portion of the frame is the interface between the RF Modem frame and the SIF. A total of two RFMFs are allowed. A CSM (GPS) is required for each RFMF. SC4840 Documentation The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this BTS product.
S S S S S S
SC2440
SC4840 BTS Hardware Installation SC4840 RF Modem Frame (RFMF) Functional Description SC4840 Site Interface Frame (SIF) Functional Description SC4840 BTS Optimization/ATP SC4840 ELPA Guide SC4840 BTS Field Replaceable Unit (FRU) Procedure.
The SC2440 CDMA BTS is a singleframe, indoor base station designed to support mediumdensity cell sites. Cable entry and exit is at the top of the frame, and the frame is front accessible. The SC2440 CDMA BTS Frame contains the:
S S S S S S S S S S S
Cell Site Filters Multicouplers Duplexers Directional Couplers RFDS. Time synchronization Call processing Multitone Expandable Linear Power Amplifiers (ELPAs) Module Alarm Communication Hub (MACH) cards Base station fault management The dialup modem.
The SC2440 CDMA BTS supports the Japan CDMA air interface in omni transmit/omni receive and threesector transmit/threesector receive. Each SC2440 Frame can support Single Density ELPA modules in either the LoTACS band or HiTACS band. Double Density ELPA modules are supported in the HiTACS band only. LoTACS modules and HiTACS modules cannot be mixed in the same frame. Therefore, the entire ARIB STDT53 frequency allocation is not serviced by a single frame. The capacity of an SC2440 Frame is related to the:
3-60 CDMA SC Products System Resource Guide (CSSRG) June 2001
1 4 4 N/A 1
Maximum Number of MCC/Shelf Maximum Physical Traffic Channels/Shelf Number of CDMA Shelves in Frame Maximum Physical Traffic Channels/Frame
June 2001 CDMA SC Products System Resource Guide (CSSRG)
S Sites with CDMA only use the JCDMA/PDC Triplexers S Sites with colocated JCDMA and PDC use the JCDMA/PDC
Triplexers with the externally mounted Hybrid Duplexer. Figure 3-16: SC2440
Distribution Shelf
BBX, MCC, GLI
RFDS
SC2440 Power Amplifier Capabilities The SC2440 Frame supports up to three 2Up ELPA shelves. A single 2Up ELPA shelf is loaded with two ELPA modules and a Bandpass filter, which provides the necessary amplification and filtering for the CDMA carriers for a single sector. Up to six ELPA modules are supported per frame. Each SC2440 Frame can support either Single Density ELPA modules in the Marinet/LoTACS band or Single Density ELPA modules in the HiTACS band. Double Density ELPA modules are supported in the HiTACS band only. Marinet/LoTACS modules and HiTACS modules cannot be mixed in the same frame. Single Density and Double Density ELPA modules cannot be mixed in the same ELPA shelf. The maximum allowable average transmitter power output is 50 watts per sector using two SD ELPA modules or 100 watts per sector using two DD ELPA modules (measured at the top of the SC2440 frame). SC2440 Operating Frequency Table 3-32 shows the operating frequencies of this BTS product.
3-62 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 3-32: SC2440 Operating Frequencies Frequency Band Marinet LoTACS HiTACS Base Receive (MHz) 887 to 889 898 to 901 915 to 925 Base Transmit (MHz) 832 to 834 843 to 846 860 to 870
SC2440 Documentation The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this BTS product. S SC2440 BTS Hardware Installation S SC2440 BTS Optimization/ATP S SC2440 BTS Field Replaceable Unit (FRU) Procedure.
SC340
The SC340 is an omni single carrier product. The product portfolio includes two Field Replaceable Units (FRUs) with two different power output options. The PicoCell provides up to 200 mW of transmit power out and the MicroCell provides up to five Watts of transmit power out. The PicoCell is ideal for low power applications such as subway, underground, or inbuilding areas. For higher power applications such as rural or hole filling areas, the MicroCell can be deployed. The MicroCell FRU is similar to the PicoCell FRU. However, it includes a power amplifier to increase the maximum transmit power level to five Watts and the necessary circuitry to support receive diversity. SC340 CDMA Carrier Support The SC340 currently supports only one complete CDMA carrier in an omni (single sector) configuration with no redundancy. In the future, a second carrier can be added to a site by adding an expansion/additional FRU. Table 3-33: CDMA Carrier Support Number of Shelves per BTS Cabinets Number of Carrier per Shelf Omni Number of Carrier per Shelf Three Sector Number of Carrier per Shelf Six Sector Maximum Number of CDMA Cabinets 1 1 N/A N/A 1
NOTE
Future multiple carrier expansions will be available with feature 1165D. With this feature, which is targeted for Release 15, up to four carriers can be supported by adding expansion/additional SC340 FRUs.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-63
Table 3-34: Physical Traffic Channels Physical Traffic Channels per MicroCell FRU Physical Traffic Channels per PicoCell FRU Minimum Number of FRUs/Cabinet Maximum Number of FRUs/Cabinet Number of CDMA Shelves in Cabinet Maximum Physical Traffic Channels/Cabinet 16 16 1 1 1 16
NOTE
Future channel element expansions are proposed with feature 1165E. With this feature, an SC340 FRU option with 32 physical channel elements will be available. SC340 RF Cabling The Site Input/Output (I/O) and Junction Box acts as the main interface between the FRU and external connections. The external interfaces are categorized in the following four main functional areas:
S S S S
The unit contains a separate diagnostic interface that provides a single location for service personnel to interface with the FRU. The PicoCell option of the SC340 does not support receive diversity. The RF antenna configurations for multiple carrier PicoCell sites consists of adding a new RF antenna for each carrier/FRU that is added up to a maximum of four FRUs (as shown in Figure 3-17).
3-64
June 2001
Figure 3-17: Multiple Carrier PicoCell RF Antenna Configuration Tx/Rx Tx/Rx Tx/Rx Tx/Rx
FRU F1
FRU F2
FRU F3
FRU F4
1 Carrier Tx/Rx Rx
Tx/Rx
2 Carriers Tx/Rx T T
FRU F1
T T = 50 Ohm Terminator
FRU F1
Rx
FRU F2
Tx/Rx T
3 Carriers Tx/Rx T
Tx/Rx
Rx
FRU F1
Rx
FRU F2
FRU F3
T T = 50 Ohm Terminator
June 2001
3-65
4 Carriers Tx/Rx T
3
Tx/Rx T
Tx/Rx T
Tx/Rx T
FRU F1
Rx
FRU F2
FRU F3
Rx
FRU F4
T = 50 Ohm Terminator
SC340 Power Amplifier Capabilities As stated earlier, the SC340 can be ordered with two different power output options. The PicoCell provides up to 200 mW of transmit power out and the MicroCell provides up to five Watts of transmit power out. SC340 Operating Frequency Table 3-35 shows the operating frequencies of this BTS product. Table 3-35: SC340 Operating Frequencies Frequency Band LoTACS (see Note) HiTACS Base Receive (MHz) 898 to 901 915 to 925 Base Transmit (MHz) 843 to 846 860 to 870
NOTE
Future features 4108 will allow for LoTACs support SC340 Documentation The following is a list of documentation that is available from Motorola Technical Education and Documentation that provides further detail on this BTS product:
S S S S
SC340 BTS Hardware Installation, ATP, and FRU Procedures CDMA LMF Operator s Guide CDMA LMF CLI Reference Grounding Guidelines.
3-66
June 2001
Pilot Beacon
Introduction
The application for Pilot Beacon is in coverage areas where Hard Handoff (HHO) is required from a CDMA Carrier to another CDMA Carrier on a different frequency or a CDMA Base Transceiver Station (BTS) to an Analog BTS. Motorolas Pilot Beacon is a transmitonly product that acts as a trigger mechanism for HHO by generating a pilot, paging, and synchronization signal on the same frequency as the CDMA carrier currently servicing the mobile subscriber. The 800 MHz and 1.9 GHz Indoor Pilot Beacons are omni, nonredundant CDMA transmitters providing Pilot, Paging, and Synchronization information for overtheair interface to a CDMA subscriber unit. The Pilot Beacon is designed to facilitate hard handoffs (HHO) between carriers within a CDMA system and/or from a CDMA system to an analog/(AMPS/TACS) system. The indoor unit may be used with the SC9650, SC2450, SC4812, and SC4852 systems, as well as indoor applications of the SC611 and SC614 base stations. Multisector indoor sites are supported by installing one Pilot Beacon box for each sector requiring a Beacon. The Pilot Beacon may be colocated at a cell site with a BTS or may be located at a remote site. The Pilot Beacon is designed to support omni and multisectored RF configurations. The Pilot Beacon product can share the existing cell site antennas via connection to directional couplers in each desired RF path of the BTS. The Pilot Beacon product supports separate antennas connected directly to the Beacon unit. Pilot Signaling Power The Pilot Beacon is capable of supplying an output pilot power as indicated in Table 3-36. The output power is scaleable in increments of 0.25 dB steps. Table 3-36 lists the powers for the different frequency bands. Table 3-36: Pilot Beacon Output Power Frequency Band 800 MHz 1.9 GHz Maximum 2.5 W 2W
Typical installations consist of a coupler being used to feed the RF signal from the pilot beacon into an existing antenna at the site. The loss of the coupler is typically 10 dB. Therefore the maximum output power provided in the preceding table would be decreased by 10 dB. Number of Pilot Signals The Pilot Beacon is capable of supporting up to three unique carrier frequencies per sector (application dependent and BSS CDMA Release 2.9.2).
June 2001 CDMA SC Products System Resource Guide (CSSRG) 3-67
Table 3-37: Pilot Beacon Operating Frequencies Base Transmit (MHz) 1930 to 1990 869.70 to 893.31 Pilot Beacon Documentation
The following is a list of documentation available from Motorola Technical Education and Documentation which provides further detail on this product.
S Indoor Pilot Beacon Instruction Manual CDMA 800/1900 MHz S Outdoor Pilot Beacon Instruction Manual CDMA 1.9 GHz.
3-68
June 2001
Intelligent Network (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DMXHLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Register (MR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Register (MR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
Table of Contents
Notes
continued
June 2001
Introduction
The Intelligent Network is made up of many different components. Some of these components are the:
S Distributed Mobile Exchange Home Location Register (DMXHLR) S Message Register (MR).
June 2001
4-1
DMXHLR
Introduction
The Home Location Register (HLR) is an Intelligent Network (IN) element that stores, manages, and controls the subscriber database. The HLR also performs call processing, mobility management, and special resource data functions therefore interfacing to other IN elements. The HLR/VLR/SCP functionality is responsible for controlling the services and features throughout the network. The HLR can be acquired in two different versions:
S Management Interface
The HLR offers an efficient, userfriendly subscriber information management interface.
S The number of CPUs installed S The amount of main memory per CPU S The number of communications links between the EMXs and the
HLR.
4-2 CDMA SC Products System Resource Guide (CSSRG) June 2001
DMXHLR
continued
Because the Exception Reporting and Alarms Distribution (ERAD) changes from release to release, please check the back of the customer documentation manual in order to determine what the ERADs for the system mean. Determining Utilization Utilization can be determined by executing VIEWSYS and checking the following: S CPU utilization (press F1)
S Disk I/O rate (press F8) S Cache hit rate (press F7).
Perform PUP LISTCACHE $DATAn, STAT to check cache memory utilization. Because the ERADs change from release to release, please check the back of the customer documentation manual in order to determine what the ERADs for the system mean. Planning Limits Nonmated pair HLRs should be kept at under 80% utilization. Mated pair HLRs can use one processor to do call processing while the other is idle. In this case, the active HLR should be kept at under 80% utilization while the other HLR is at 0%. Refer to the DMX/HLR B1 document for any planning limits. Symptoms of Resource Overload Overload can be determined by viewing the IPR785 messages which are output from the EMX. Execute VIEWSYS and then check the following: S CPU Utilization (press F1) CPU Utilization should be under 80%. The presence of persistently higher CPU rates indicate that the system is undersized. S Disk I/O Rate (press F8) The Disk I/O Rate should be one or below in all Call Processing CPUs. The presence of higher disk rates indicates insufficient cache. S Page Fault Rate (press F3) Page faults should be at zero in all Call Processing CPUs. The presence of page faults indicates that memory is oversubscribed. Because the ERADs change from release to release, please check the back of the customer documentation manual in order to determine what the ERADs for the system mean. Reducing Utilization/Capacity Improvement The capacity planning for the DMX HLR is determined by the performance characteristics of the platform, the applications, and parameters that characterize the targeted customer environment.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 4-3
DMXHLR
continued
Link capacity is determined by calculating the total amount of inbound and outbound traffic to the HLR. These results are then used to determine the minimum number of links required at the HLR. All HLRs should be sized to measure capacity and hardware requirements. This sizing should be done by the HLR Product Group and is based upon information that determines the capacity requirements of the market and customer. The capacity of the HLR is a mathematical model, which may be found in the B1 document. This model is used to determine configuration information based on capacity requirements such as:
S S S S S S
Call mix Transaction ratios Feature useage Configuration options Expected subscriber levels Expected busy hour call attempts (BHCA).
4-4
June 2001
The Message Register (MR), which supports the IS637 protocol, provides messaging services to Narrowband Advanced Mobile Phone Service (NAMPS) and Code Division Multiple Access (CDMA) cellular subscribers. The MR is connected, via a DMX link, to a single EMX 2500/5000 gateway that supports Enhanced DMX Messaging. The Message Register interfaces with Intelligent Peripheral Devices (IPD) that adhere to Cellular Digital Messaging Protocol (CDMP), Telocator Alphanumeric Protocol (TAP), Telocator Network Paging Protocol (TNPP), or Octel Command Language (OCL) specifications. The MR supports the following features:
S S S S S S
Digital Page Custom Text Message Voice Mail Notification Fax Notification Call Completion Service (within a DMX network only) Mobile Activity Status (within a DMX network only).
See the Message Register Operations Manual for detailed information about these features. Limiting Factors Load balancing is the most common limiting factor for the Message Register. Load balancing problems can be caused by any of the following:
S Disk utilization
Heavy disk utilization is usually caused by: Increased subscriber activity or the hardware and software configuration Poor cache setting Excessive memory utilization which can create adverse impacts on disk utilization. Correcting the above usually fixes any disk utilization problems.
S Batch Schedules
Schedule batch activities outside of peak activity periods.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 4-5
Get expert help from and work with Motorolas Core System Engineering (CSE) group. Planning Limits Planning limits for the Message Register are the following:
S 30 pages per second for a subscriber base of 200,000 S 25 pages per second for a subscriber base of 500,000 S 20 pages per second for a subscriber base of 1,000,000.
Symptoms of Resource Overload The following are usually symptoms of overload:
S Poor response time S Transactions timeouts S CPU utilization greater than 60%.
The ERAD subsystem monitors and scrolls system and application error messages. Support procedures should include the monitoring of all ERAD messages. Refer to the Message Register Operation Manual Alarms and Messages (ERAD) for details. Reducing Utilization/Capacity Improvement Any factor which limits system utilization must be uncovered and corrected. The most useful source for gaining a perspective of system utilization is through the ongoing monitoring of ERADs. Refer to the ERAD manual for information regarding errors and possible corrective measures.
4-6
June 2001
Operations and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Center Radio (OMCR) . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SwitchMATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Universal Network Operations (UNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
Table of Contents
Notes
continued
June 2001
Introduction
Providing Operations and Maintenance support preserves data and corrects data or network faults when they occur. The following elements maintain the SuperCell system as it expands:
June 2001
5-1
Introduction
The Operations and Maintenance Center Radio (OMCR) interfaces directly to the Centralized Base Station Controller (CBSC) and acts as a data collection and mediation device for SuperCell events, statistics, and configuration. The OMCR also supports a command line interface for fault management, configuration management, performance management, and network monitoring functions. In addition, it contains the Management Information Base (MIB) which is the master of all configuration data in the SuperCell system. The OMCR provides the following functionality:
S Event/Alarm Management
Event Management logs events for future use. Alarm Management presents the operator with a toolset to manage the alarms.
S Performance Management
Performance Management provides for the collection of statistics and call information. These are placed into a database and logging file and may be be viewed using tabular or graphical reports.
S Configuration Management
Configuration Management provides the operator the ability to display or modify data in the database and to distribute data changes to the involved network elements.
S Security Management
Security Management provides password and login access to the system.
S Fault Management
Fault Management provides the OMCR with the support for the CLI commands necessary to enable or disable devices in the network and to determine their status. A small number of Tandem Helix PeaceMaker 2 (PM 2) platforms are still in use, but the PM 2 platform is not considered here. However, two OMCR platforms are currently supported:
the same code in lockstep. The PeaceMaker 3 processor operates at 100 MHz and has 128 Mbytes of RAM. S Sun E4500 The Sun E4500 is supported in a two processor Symmetric MultiProcessing (SMP) configuration. In the SMP configuration, a process may run on either processor. The two processor configuration does not provide twice the throughput of a single processor because of process scheduling and control overhead, but more significantly, serialized operations and singlethreaded processes are essentially limited to a single processor. The significance of this limitation is that the event manager, which is involved in most OMCR based activities, can never utilize more than 50% of the total CPU capacity (100% of one processor) because it is singlethreaded. This is also true of other processes, most notably the MIB process, but the event manager typically utilizes more CPU capacity than any other OMCR process. However, the two processor configuration provides significantly greater throughput than a single processor configuration. In the sections that follow, suggested OMCR limits are presented based upon an allocation of processor resource that has been found experimentally to provide adequate performance. Information is provided to explain how the suggested limits were derived and to permit the operator to estimate the impact of modifying one or more of the limits. The operator may choose either to use the suggested limits or to establish alternate limits based upon his assessment of the impact given his understanding of the way he will be utilizing the OMCR. Mechanisms for determining the growth potential for the OMCR domain given the limits the operator accepts are then described. Limiting Factors The processor capacity on the OMCR imposes limits on the call processing load supported by the CBSCs in the domain of the OMCR. Processing of CDLs is the single most expensive OMCR load component, and limits must be placed on the CDL generation to assure adequate processing capacity. The limit on CDL generation rate translates directly to a limit on the number of calls that can be processed by the CBSCs under the OMCR. Processor memory also limits the size of the system administered through the OMCR, but only to the extent that increasing system size reduces OMCR performance in terms of response times for CLI command execution. Disk space limitations are important only to the extent that the duration that CDL and event logs can be stored is reduced as the size of the OMCR increases. For the majority of network configurations, the CDL limits will be dominant. It is unlikely to encounter system size limitations before the CDL limits are reached as the system grows. The CDL and system size limitations are shown in Table 5-1 for both the Tandem Helix PM 3 platform and the Sun E4500 platform. The number
June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-3
of CBSCs is constrained to eight by software limitations, but the other limits specified in the table are based primarily upon empirical data from the lab and field as described in the following sections. The hourly CDL limit is established by limiting the CPU utilization for CDLs to approximately 40% on the Helix and 50% of one processor on the Sun. An additional 10% of the CPU capacity is allocated to the processing of alarms and events on the Helix and 30% of one processor is allocated on the Sun. The remaining CPU capacity is reserved for CLI and script execution, PM data collection and processing, and bursts in CDL and event traffic. It is important to note the OMCR can be operated at CDL rates above the limits presented in Table 5-1, but the OMCR response time to operator CLI commands will increase and may become unacceptable. Similarly, the operator may find the response time to commands unacceptable at the suggested limits and may elect to size the system so that a lower CDL load will be presented to the OMCR. Equations required to approximate the relationship between CLI response time and nonCLI utilization are provided below. Table 5-1: OMCR Capacities
5
Maximum CDLs:
Peacemaker 3
The hourly CDL rate may be estimated by adding the mobile origination attempts and mobile termination assignment attempts together. In terms of PM data, this is equivalent to sum(pmc_10_hr.peg_count_1 + pmc_10_hr.peg_count_6) summed for the two half hours during the busy hour and summed for all MMs under the OMCR. The rate should be determined by averaging the bouncing busy hour (BBH) data for the five busiest days in a one week period, eliminating any days that are abnormal (for example, holidays, etc.). The daily CDL rate assumes approximately 10 busy hour equivalents per day and is used to estimate the maximum storage duration for CDL
5-4 CDMA SC Products System Resource Guide (CSSRG) June 2001
records. With an average of approximately 970 bytes per CDL record, the Tandem Helix OMCR platform provides storage for 2,000,000 CDL records for a nominal period of 32 hours, assuming two pairs of 4G (gigabyte) disk drives are used on the OMCR and a 2G disk partition for CDL storage. The Sun OMCR platform provides storage for 26,000,000 CDL records for a nominal period of 80 hours, assuming five pairs of 18G (gigabyte) disk drives are used on the OMCR and a 25G disk partition is used for CDL storage. The number of traffic channels (TCHs) is the total number of equipped TCHs in the system. The number of traffic channels can be determined using the following command:
display cbsccbsc# siteconf
This command returns one line per BTS under the CBSC. The rightmost entry on the line represents the number of equipped noninhibited Maintenance Control Center Channel Elements (MCCCE) at the BTS. This data may be imported into a spreadsheet to facilitate generating a total traffic channel count. The number of carriersectors is the total number of carriers equipped in all sectors. For example, a BTS with six sectors and two carriers would have 12 carriersectors. In an active system, the number of carriersectors may be determined by executing the following CLI command on the OMCR:
display omcr allstatus | grep v BBXR | egrep c BBX|MAWI
The number of sectors is the total number of equipped sectors in the system. The display cbsc siteconf command used above to obtain a count of traffic channels may also be used to count the number of sectors, but the method is a bit more involved. For each BTS, the command returns the number of traffic channels equipped per sector. This data may be imported to a spreadsheet to facilitate generating a sector count. The maximum number of CLI sessions that can be created is limited by software to 16 for both the Tandem Helix and Sun platforms. An active CLI session is one that is executing CLI commands or scripts containing CLI commands. The CLI limits were established assuming a target average response time of at most 10 seconds for simple CLI commands. An event subscription represents a CLI session that has events enabled. Determining Utilization Two primary utilization factors are of significance on the OMCR platform: 1. The CPU resource required for processing CDLs, alarms, events, PM data, and browse server traffic (all referred to below as events). 2. The CPU resource required to process CLI workload. The CLI and event processing activities are treated differently because the method of assessing their impact differs. The event processing load
June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-5
can be assessed by estimating the fraction of total CPU resource used, in other words, CPU utilization. On the other hand, the CLI load typically utilizes all available CPU resource; the less CPU resource available, the longer the execution time of each CLI. Delays in processing events are generally not important as long as the desired throughput is maintained with no loss of data. Delays in processing CLI activity must be kept within limits tolerable to the operator. Methods are given below to estimate the CPU utilization for processing event workloads and to estimate the response times for CLI activities. CLI response times are related to CPU utilization for event workloads, because the CPU resource used to process event workloads is not available for CLI processing and thereby increases CLI response times. Although budgets were established for event processing CPU utilization and targets were established for CLI response times in the Limiting Factors section to provide meaningful load limits, the operator may engineer for higher CDL loads at the expense of longer CLI response times or vice versa. The number of active CLI sessions may also be reduced either to improve the CLI response times or to increase the CDL load with no impact to response times. The number of CLIs that can be executed in parallel with a given average response time also increases if they are executed during a maintenance window when the call processing load is low. As previously mentioned, the recommended CDL and event processing limits are established to keep the CPU utilization below 50% on the Helix and below 80% of one processor (40% of total CPU resource) on the Sun for processing these workloads. The CDL component, which is dominant, is limited to 40% utilization on the Helix and 50% of one processor on the Sun. The CDL and event processing utilization may be estimated using the following equations. Overhead for PM data collection and CDL browse server is also included. The Helix PM 3 CPU utilization, excluding CLI execution, may be estimated as follows:
Utilization = CDL * 0.0102 + Alarm * 0.0228 + Auto * 0.0134 + Status * 0.0297 + Manual * 0.0111 + Log * 0.0113 + Subscriptions * 0.00125 * (Alarm + Auto + Status + Manual) + PM + Browse [EQ 51]
Where: CDL is the per second CDL arrival rate Alarm is the per second alarm arrival rate Auto is the per second arrival rate of Automatic type events (excluding alarms) Status is the per second arrival rate of Status type events (excluding Manual types) Manual is the per second arrival rate of Manual type events Log is the per second arrival rate of Log Only type events
5-6 CDMA SC Products System Resource Guide (CSSRG) June 2001
Subscription is the number of CLI sessions with events enabled PM is the CPU utilization for PM data collection, about 0.05 Browse is the CPU utilization for the portable browser (cdl_browse_server), about 0.05. The recommended utilization resulting from CDL and event traffic is 50% on the Helix. The data used to create the above equation, coupled with the CDL processing budget, have been used to establish a recommended limit of 140,000 CDLs per hour. The steady state Alarm rate is assumed to be 1800 per hour, and the steady state event rate (total of Auto, Status, Manual, and Log types as defined previously) is assumed to be 3600 per hour. A limit of four subscriptions is also assumed. The Sun E4500 CPU utilization for one processor may be estimated as follows:
Utilization = CDLs * 0.00272 + Alarm * 0.00674 + Auto * 0.00484 + Status * 0.00796 + Manual * 0.00353 + Log * 0.00342 + Subscriptions * 0.00037 * (Alarm + Auto + Status + Manual) + PM + Browse [EQ 52]
Where: CDL is the per second CDL arrival rate Alarm is the per second alarm arrival rate Auto is the per second arrival rate of Automatic type events (excluding alarms) Status is the per second arrival rate of Status type events (excluding Manual types) Manual is the per second arrival rate of Manual type events Log is the per second arrival rate of Log Only type events Subscription is the number of CLI sessions with events enabled PM is the CPU utilization for PM data collection, about 0.02 Browse is the CPU utilization for use of the portable browser, about 0.05. NOTE Since the Sun E4500 utilizes two processors, the full utilization hard limit for the Sun E4500 equation is 200%.
On the Sun, as on the Helix, the utilization is important because it influences the CLI response times. On the Sun, the utilization of the event manager is also important because the event manager is singlethreaded and cannot utilize two processors. Therefore, the utilization of the event manager should never exceed 80% of one processor even with no CLI load. The event manager utilization for one processor can be approximated as follows:
Utilization EM = CDLs * 0.00231 + Alarm * 0.00527 + Auto * 0.00463 + Status * 0.00385 + Manual * 0.0033 + Log * 0.0032 + Subscriptions * 0.00014 *(Alarm + Auto + Status + Manual) [EQ 53] June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-7
Where: CDL is the per second CDL arrival rate Alarm is the per second alarm arrival rate Auto is the per second arrival rate of Automatic type events (excluding alarms) Status is the per second arrival rate of Status type events (excluding Manual types) Manual is the per second arrival rate of Manual type events Log is the per second arrival rate of Log Only type events Subscription is the number of CLI sessions with events enabled. NOTE Since the Event manager is singlethreaded to use one processor, the full utilization hard limit for the Event manager equation is 100%.
A budget of 80% CPU utilization of one processor for CDL and event processing leads to a recommended limit of 700,000 CDLs per hour. The steady state Alarm rate is assumed to be 36,000 per hour, and the steady state event rate is assumed to be 72,000 per hour. A limit of 16 subscriptions is also assumed. These alarm and event rates are expected to be well above those experienced in the field. Typical event arrival rates may be determined through analysis of event logs for periods considered typical for a busy hour averaged over a one week period. The following UNIX commands may be used to acquire the desired data:
Subtract the alarm count from the count of total automatic events
The influence of CLI response times may be estimated using the equations below. The response times provided by the equations are average response times. The 95th percentile may be about twice the average, and the worst case could be three to four times higher than the average response time. NOTE These equations are approximations that are a best fit for the data available.
Average CLI response times for the Helix PM 3 can be estimated as follows: S For CLI commands that do not act on the MIB
RT = (RTNL * CLI0.9) / (1.0 Utilization(1 + Utilization)) [EQ 54]
Where: RT is the average response time RTNL is the average response time with no CLI or event traffic CLI is the number of CLIs being executed in parallel. Utilization is as described by the equation for the Tandem Helix above.
[EQ 55]
Where: RT is the average response time RTNL is the average response time with no CLI or event traffic TCH is the number of traffic channels in thousands CLI is the number of CLIs being executed in parallel. Utilization is as described by the equation for the Tandem Helix above. Total number of traffic channels (TCHs) may be determined as described in the Limiting Factors Section above. The following are observations: 1. Response time varies nearly linearly with the number of CLIs being executed in parallel. The increase becomes more linear as the utilization increases. 2. Response time of commands acting on the MIB are strongly influenced by MIB size. Going from a small MIB (less than 30% of the maximum for TCHs/BTSs/CarrierSectors/Sectors) to a large MIB (greater than 70% of the maximum for TCHs/BTSs/CarrierSectors/Sectors) increases response times by a factor of nearly five. 3. For simple display commands, response times of under 10 seconds average can be achieved with six concurrent CLIs with no CLI or event traffic, four CLIs at half rated load, and two CLIs at rated load.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-9
4. With a medium to large MIB, commands that act on the MIB produce response times on the order of 10 seconds only if limited to one command execution at a time with load levels at half the rated load. With a large MIB, the ADD BTS command requires about 30 seconds on average with no CLI or event traffic. These equations are intended to give an indication of the impact of adding CDL/event loads and increasing the MIB size. However, they do not give absolute CLI response times without a knowledge of the response time with no CDL/event load and a small MIB (RTNL ). The following may be used for an approximate reference.
These equations are true only for commands that are executed within the OMCR. They do not account for MM, BTS, or XC response times for commands that act on these network nodes.
Average CLI response times on the Sun E4500 can be estimated as follows:
Where: RT is the average response time RTNL is the average response time under noload conditions CLI is the number of CLIs being executed in parallel. Utilization is as described by the equation for the Sun above. NOTE This equation is valid only for two or more concurrent CLIs. Because there are two processors available and each CLI can effectively utilize only one processor, the average execution time for one CLI and two CLIs is essentially the same under noload conditions.
Where: RT is the average response time RTNL is the average response time under noload conditions and a small MIB CLI is the number of CLIs being executed in parallel TCH is the number of traffic channels in thousands. Utilization is as described by the equation for the Sun above. Because the execution time of CLIs that act on the MIB is driven primarily by the MIB process and the MIB process is singlethreaded, these CLIs cannot, in effect, utilize two processors. As a result, the event manager load has little impact on the response time of these CLIs, but the CLIs compete with the nonevent manager load for CPU resource. The following are observations: 1. For commands that do not act on the MIB, the response time is nearly linear with half the number of concurrent CLIs at low load levels. As the load level increases, the increase in response time becomes nearly linear with the increase in concurrent CLIs. 2. For commands that act on the MIB, the response times increase nearly linearly with the number of concurrent CLIs being executed. Load levels have little impact on the response times. 3. For commands that act on the MIB, the response times increase by about a factor of 5 in going from a small MIB to a large MIB. 4. For simple display commands, response times of under 10 seconds average can be achieved with 16 concurrent CLIs at rated load. 5. With a medium to large MIB, commands that act on the MIB will produce response times on the order of 10 seconds only if limited to about 6 commands at a time independent of the load levels. With a large MIB, a single ADD BTS command requires about 10 seconds on average independent of the load levels. The limits on MIB size (BTS, sector, carriersector, and traffic channels) and the number of simultaneous CLIs in execution were determined primarily from limits established on response times as provided by these equations. These equations are intended to give an indication of the impact of adding CDL/event loads and increasing the MIB size, but they do not give absolute CLI response times without a knowledge of the response time with no CDL/event load and a small MIB (RTNL ). The following may be used for an approximate reference.
Planning Limits The planning limits are based primarily on the CPU resource available for CDL and event processing and the desired CLI response time performance. The CLI response times are, in turn, influenced by the CPU utilized for CDL and event processing, the number of CLIs executing concurrently, and the size of the MIB. As a system grows, more CDLs will be generated, the MIB will increase in size, and the amount of CLI activity will also tend to increase. The operator can estimate how much growth capacity is available on an OMCR by gauging the reserve CPU resource available for event processing, determining the MIB growth potential by comparing the current system size to the accepted limits, and by estimating the increase in CLI activity. The accepted limits may be determined by utilizing the values provided in Table 5-1, or the operator may use the utilization and response time equations provided above to establish his own limits. Symptoms of Resource Overload The primary symptom of overload is excessive response times to CLI commands, either in scripts or direct entry. If the CDL load is not above the recommended limits, poor response times most likely indicate too many CLIs are being executed concurrently. NOTE Scripts running as cron jobs or scripts executing on remote platforms that invoke OMCR CLIs must be counted when determining the number of concurrent CLIs.
If excessive CLI activity is initiated, especially during high traffic periods, the OMCR internal event queues may overflow causing events to be lost. In overload situations, events may also be discarded by the MMs if they cant be forwarded to the OMCR before the queues overflow. If overloading is suspected, the operator may perform the following checks to determine if events have been lost:
5-12 CDMA SC Products System Resource Guide (CSSRG) June 2001
1. 2. 3. 4.
5. 6. 7. 8. 9.
Login to the OMCR Enter the command dbapi At the dbapi prompt, enter status A list similar to the following displays: 0 PID: 637 Name: gcmgr qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 1 PID: 594 Name: scemlogd qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 2 PID: 595 Name: monitorApi qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 3 PID: 597 Name: omcgw qLen: 0 qMax: 250 qHigh: 0 qDrop: 0 4 PID: 2398 Name: dbapi qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 5 PID: 635 Name: omcfm qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 6 PID: 634 Name: slm qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 7 PID: 615 Name: mit qLen: 0 qMax: 100 qHigh: 0 qDrop: 0 8 PID: 621 Name: omctad qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 9 PID: 620 Name: pm_rqst qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 10 PID: 636 Name: mmi_ping qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 11 PID: 616 Name: TestQueue qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 12 PID: 618 Name: sdc qLen: 0 qMax: 1000 qHigh: 0 qDrop: 0 13 PID: 617 Name: agent qLen: 0 qMax: 500 qHigh: 0 qDrop: 0 14 PID: 598 Name: omcmib qLen: 0 qMax: 5000 qHigh: 0 qDrop: 0 15 PID: 1980 Name: scevmgr qLen: 0 qMax: 2400 qHigh: 4 qDrop: 0 If the scevmgr (event manager) process qDrop count is nonzero, the OMCR has experienced overload. If the scevmgr qHigh count is within 90% of the qMax for the respective process, the processor has been running near overload. Enter the command clrstat. This resets the counters. Repeat the above procedure for each subtending MM, but look at the qDrop and QHigh data for the omcgw (OMC gateway) process. If the omcgw process qDrop count is nonzero for any MM or the qHigh is within 90% of qMax for the process, the OMCR is likely in or near overload.
5-13
June 2001
This should be done on a daily basis, preferably at the same time each day during a low call traffic period. No action should be undertaken unless the checks indicate an overload for two or more days in a one week interval. Reducing Utilization/Capacity Improvement Regular utilization of the CLI browser is not recommended. Online CDL browsing, in particular, is CPUintensive and will degrade OMCR performance. OMCR performance also degrades if the number of active CLI sessions or scriptinitiated sessions exceeds the recommended limit. Such overload conditions may be alleviated by assessing the way the OMCR is being utilized and making modifications as necessary. If overload conditions are encountered, it may be necessary to add an OMCR and redistribute the CBSCs. See the System Configuration section of the most recent release manual for additional information concerning this topic.
Operators of Tandem Helix PM 3 systems that have been upgraded from PM 2 systems should verify their SCSI disk controllers have been upgraded as well. The SCSI controller version maybe determined by executing the following commands in a UNIX shell:
5-14
June 2001
SwitchMATE
Introduction
SwitchMATE is an intelligent message processor connected to the EMX 2500/5000 switch. SwitchMATE provides a user interface that gives the use the ability to view a full picture of the entire system status at one time and then detect and correct any network faults. All SwitchMATE and selected EMX commands are available through menus and dialog boxes which enables fast and easy command entry. Instead of just one usable console, SwitchMATE users can define other consoles and the types of messages to be displayed in each of them. Limiting Factors Limiting factors for SwitchMATE are:
S Report and log files take a long time to complete. S Accumulated SwitchMATE files must be deleted periodically by the
Cleanup utility. Determining Utilization CPU power can be affected by the following: S Calculations using spreadsheet programs and others
S The CPU must dedicate about 30% of its power to serial ports.
Planning Limits The number of CAT instances that can be open at the same time on the MSWindows desktop depends on the use of resources in each instance. Symptoms of Resource Overload The following are some problems that may arise when using SwitchMATE. Please refer to the Troubleshooting Problems and Solutions section in the SwitchMATE 2500 Operation Manual for a complete listing of problems and instructions concerning how to resolve them. S SwitchMATE does not appear to be getting IPRs or alarm panel updates.
S SwitchMATE reports, via the SwitchMATE alarm, that the AMA DAS
link is bad. However, on the switch, its indicated as inservice.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-15
SwitchMATE continued
S SwitchMATE reports, via the SwitchMATE alarm, that the TM&M
DAS link is bad. However, on the switch, its indicated as inservice.
S SwitchMATE reports messages that the switch and CAT version or the
SwitchMATE host and switch version do not match.
S Data from the switch get lost before being processed by the
SwitchMATE host.
S The usere needs to reboot the CAT but pressing the <Ctrl+Alt+Del>
key sequence doesnt succeed.
S SwitchMATE tries to log into the EMX using an invalid password . S An MMI command fails with the message LINE ERROR ON LINE,
followed by a SwitchMATE alarm. Also, refer to the SwitchMATE Command Reference manual for a detailed listing of all IPRs and their settings. Reducing Utilization/Capacity Improvement
S Ensure that network traffic is kept to a minimum. S The Subscribers functionality is used when a problem arises. This 5
feature, used for both local and roamer subscribers, allows the operator to see a customer s currently assigned characteristics and change them if necessary.
5-16
June 2001
Introduction
Universal Network Operations (UNO) is a powerful tool used to manage Code Division Multiple Access (CDMA) and Analog networks. UNO offers the equivalent functionality previously available with SCUNO. UNO will be introduced as the SCUNO replacement when release R8.1 is available. However, UNO will be required as a replacement beginning with release R8.3. UNO was developed using the Telecommunications Management Network Q3 (TMN Q3) international standard for telephony management. UNO uses industrystandard software and hardware and is a GUI interface to the entire cellular system. UNO provides the following capabilities across managed, multivendor elements:
Number of managed elements Event arrival rate CDL arrival rate Amount of performance statistics transferred.
Determining Utilization Determining UNO utilization consists of analyzing system utilization and the network being managed. The current set of tools being used include:
S The UNIX utilities sar and vmstat for assessing CPU and memory
utilization
S Maximum BTS*Sector*Carrier (this is the only true hard limit) S Steady State CDL /Hour S UNO Managed Elements.
5-18
June 2001
Table 5-2: UNO 2.2 Planning Recommendations Supported Platforms Processors RAM Disk Space Rec. Max. CMIP Agents (OMCR/SM) 1 (OMCR only*) * Only UNOEM 1 (OMCR only*) * Only UNOEM 1 (OMCR only*) * Only UNOEM 6 6 6 6 6 6 6 6 6 6 6 Rec. Max. Steady Steady UNO Max. BTS* State State Managed BTS Sector* Events/ CDL/ Elements Carrier Sec. Hour 200 2400 1 35,000 17,000
Sparc20
2*75 MHz
256MB 12 GB
200
2400
55,000
24,000
Sun Ultra 2
2*300 MHz
256MB 12 GB
200
2400
75,000
24,000
Sun Ultra 2 2*167/200MHz Sun Ultra 2 Sun E250 Sun E3000 Sun E3000 Sun E3000 Sun E3000 Sun E3500 Sun E3500 Sun E3500 Sun E3500 2*300 MHz 2*300 MHz 2*250 MHz 2*250 MHz 2*250 MHz 2*250 MHz 2*336 MHz 2*336 MHz 2*336 MHz 2*336 MHz
1 GB 1 GB 1 GB 1 GB 1 GB 2 GB 2 GB 1 GB 1 GB 2 GB 2 GB
20 GB 20 GB 27 GB 20 GB 20 GB 20 GB 20 GB 27 GB 27 GB 27 GB 27 GB
600 600 600 600 600 600 600 600 600 600 600
7200 7200 7200 7200 7200 7200 7200 7200 7200 7200 7200
2 2 2 2 2 2 3 2 2.5 2.5 3
75,000 120,000 120,000 120,000 180,000 180,000 240,000 120,000 180,000 180,000 240,000
30,000 50,000 50,000 50,000 75,000 75,000 100,000 50,000 75,000 75,000 100,000
NOTE S OMCR: Operations and Maintenance Radio (CDMA) S SM: SwitchMATE S Max. Agents equals the total OMCR and SM combined S Max. Steady State Event/Second equals the total of all agents S Max. Call Detail Logs (CDL) Steady State equals the total of all OMCRs.
Table 5-2 provides numbers that the UNO development group has tested in hardware configurations that utilize system simulators in order to
June 2001 CDMA SC Products System Resource Guide (CSSRG) 5-19
verify that the UNO application software operates within acceptable performance levels. The values selected for these tests are based on average and slightly above average system sizes experienced in the CDMA market place. It is possible that these values can be exceeded and that operators would still experience the performance they consider to be acceptable. As deployment of the system continues and additional laboratory testing is executed, these numbers may be adjusted upward as larger system configurations are verified. For all of the tests performed, which generated the numbers above, it was assumed that operators would be utilizing all of the UNO software functionalities available on each platform, including multiple instances of some applications like the Alarm Manager. For deployments of UNOMM systems where some key applications are not utilized, such as performance management and performance management thresholding, it is expected that an increase of events per second will rise by a factor of two and the number of managed elements will increase by a factor of 25%. These estimates are based on statistical analysis of system performance and not actual maximum configuration tests.
S Slow response time to user requests in UNO applications S Long start up times.
Reducing Utilization/Capacity Improvement Reducing Utilization and Capacity Improvement depends on the reason why the system is overloaded. If there are too many users or applications, the basic approach should be reducing the number of users and open applications. Also, replacing X terminals with workstations improves user response time. If the system is receiving too much data (events, CDL, or statistics), splitting the number of agents across multiple UNO platforms can help. In most cases, the customer will be impacted by user response time due to the number of users, not the amount of data being received.
5-20
June 2001
June 2001
Table of Contents
Notes
continued
June 2001
Data Services
Introduction
June 2001
6-1
Introduction
In analog systems, its a straightforward task to connect communications equipment designed for the Public Switched Telephone Network (PSTN) and obtain a reasonable quality of service. For analog cellular systems, specialized modems have been created to handle the demand of sending data. CDMA and TDMA technologies require special treatment of data since voiceband modems cannot be used. The CDMA Interworking Unit (IWU) is a device that provides functions and services so circuitmode data originating in a CDMA system can interwork with the PSTN. The IWU supports the circuitmode data functions compliant with TIA/EIA IS99. It connects to the Centralized Base Station Controller (CBSC) by the subset of the L_interface (TIA/EIA IS658) required to support circuitmode data services. The IWU can be thought of as a combination of a data gateway and a modem bank. The data gateway supports the standard data network protocols and signalling such as Frame Relay (FR) and ISDN to support the Linterface and the upper layers of the IS99 UM protocol stack. These upper layers include AT command application support to emulate locally connected modems. The connection between the computer and subscriber unit is RS232 serial data, with no modem required. The serial data stream is packetized by the TCP/IP software in the phone, and is sent to the IWU. The modem is in the Interworking Unit and is a shared resource used by all subscribers. The CBSC establishes a connection from the IWU to the PSTN and the modem begins communications.
S S S S
6-2
Device State Management The following can be statemanaged via a GUI on the IWU Management Workstation:
S S S S
Dual T1 Card Individual DS0 of a T1 interface Quad Modem Card Individual Modem of a Quad Modem Card.
The following can be viewed via a GUI on the IWU Management Workstation:
S S S S S
Dual T1 Card Individual DS0 of a T1 interface Quad Modem Card Individual Modem of a Quad Modem Card Power Supplies.
Performance Management A set of measurements and reports are used to deliver information on IWU and data/fax usage. These statistics are associated with Transcode Channel Groups. Three new measurements have been implemented: 1. Transcoder Channel Group Attempts Transcoder Channel Group Attempts is the number of attempted transcoder channel allocations within a particular transcoder channel group. 2. Transcoder Channel Group Overflows Transcoder Channel Group Overflows is the number of failed transcoder channel allocations within a particular transcode channel group. 3. Transcoder Channel Group Usage Transcoder Channel Group Usage is the total usage of all individual transcoder channels for this group. Planning Limits The detailed rules, calculations, and examples for planning an IWU can be found in the Feature Equipment Planning Guide (FEPG) and the Ordering Guide. Symptoms of Resource Overload Not applicable. Fault Management The following describes the impact to the logical IWU service if a particular board goes out of service:
June 2001 CDMA SC Products System Resource Guide (CSSRG) 6-3
6-4
June 2001
CDMA RF Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Limiting Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establishing Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Determining Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collect Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine Present Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Planning Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Walsh Code Usage Planning Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . Establish a system-level Planning Limit . . . . . . . . . . . . . . . . . . . . . . . . BTS- and system-level Planning Guidelines . . . . . . . . . . . . . . . . . . . . . Forecast Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify Bottlenecks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Evaluate Relief Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implement Relief Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Symptoms of Resource Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF Carrier Reducing Utilization/Capacity Improvement . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Limiting Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum Recommended Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Determining Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collect Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining Paging Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . Determining Access Channel Utilization . . . . . . . . . . . . . . . . . . . . . . . Determine Present Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Planning Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001 CDMA SC Products System Resource Guide (CSSRG)
7-1 7-1 7-2 7-2 7-3 7-3 7-3 7-9 7-9 7-9 7-10 7-12 7-12 7-12 7-12 7-13 7-13 7-15 7-16 7-18 7-20 7-20 7-21 7-21 7-32 7-32 7-33 7-33 7-43 7-44 7-44 7-44 7-47 7-68 7-76 7-78
Table of Contents
continued Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Limit Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forecast Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify Network Elements Exceeding Limits . . . . . . . . . . . . . . . . . . . 7-78 7-78 7-78 7-84 7-85 7-85 7-86 7-86 7-86 7-92
Control Channel Symptoms of Resource Overload . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Channel Reducing Utilization/Capacity Improvement . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Evaluate Relief Alternatives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Collection Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
CDMA RF Carrier
Introduction
CDMA RF carrier capacity and expansion addresses a number of issues and includes an analysis of the CDMA control channels. A process is provided which attempts to predict the time when an additional CDMA RF carrier or an additional control channel is required. The approach analyzes data from Performance Management (PM) reports to forecast BTS-level utilization based upon a service providersupplied marketing projection. For RF carrier planning, guidelines are provided on how to establish RF carrier capacity limits and then how to apply these limits on a BTS- and system/CBSC-level to help a Systems Engineer determine when to implement RF carrier capacity relief mechanisms, up to the point of adding a new CDMA RF carrier. For control channel planning, guidelines are provided on how to determine the current utilization of the paging and access control channels on a per-BTS basis, as well as how to determine future utilization from forecasted growth projections.
June 2001
7-1
RF Carrier Planning
Introduction
7-2
June 2001
Introduction
RF Carrier Limiting Factors are a combination of several types of limits. This topic describes the limits that the engineer must be aware of as the CDMA system is planned and forecasted for future growth.
Establishing Limits
Due to the dynamic nature of CDMA, many items can influence the Erlang capacity of a CDMA carrier. With this in mind, each cell may be different and the Erlang capacity limit obtained in one site may be unreachable in another. The following are some of the items that can impact the CDMA RF carrier capacity that can be achieved at a site: S Distribution of traffic
S Speed of traffic
Mobile Pedestrian Fixed
S BTS configuration
Omni Two-sector Three-sector Six-sector S Propagation characteristics
S S S S S S S S
Antenna characteristics (front-to-back, horizontal beamwidth) Targeted Frame Erasure Rate (1%, 2%, etc.) Grade Of Service (GOS) CSM or EMAXX chipset being utilized TAdd and TDrop settings Soft handoff percentage Paging channel rate and its power allocation Other interference (in other words, InterSystem Interference, or ISI).
Since the true RF carrier capacity may be different for each site, two different approaches are provided with varying degrees of implementation complexity. The first approach is to generalize most of the items above which affect RF capacity and develop a set of capacity design guidelines (Generic Site Capacity Limits) associated with a limited matrix of site configurations and system design. The second approach involves creating sitespecific capacity limits through the analysis of Forward Load Detection (FLD) and Reverse Load Detection (RLD) quality metrics to determine a maximum Erlang load capacity on a per-sector basis. Establishing a set of generic site capacity limits is the simplest approach and is, therefore, the recommended approach. A hybrid model to the proposed approach is to combine both approaches by establishing a set of generic site capacity limits for a limited matrix of
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-3
site configurations. Then, use RLD/FLD results to validate or adjust the limits according to actual capacity performance being observed from the RLD/FLD field data. In this hybrid approach, the RLD/FLD data for only those sites showing a high correlation of load to the quality performance metrics are used. The resultant capacity limits derived from the RLD/FLD analysis for those sites can be averaged together for sites of the same configuration in order to establish an average capacity limit. The RLD/FLD average capacity limits can then be compared to the generic set of limits and adjustments to the generic set of limits can be made if considered appropriate. Generic Capacity Limits At the present time, a convenient measurement parameter of RF capacity utilization does not exist. As a result, a generic set of site capacity limits is established. These limits are based upon the dominant RF traffic variable for a BTS, which is Walsh Code usage minutes. New load detection measurement parameters are planned for a future software release. When the new parameters are available, modify the capacity limits and the capacity planning approach in order to take advantage of these new parameters. To appropriately monitor RF carrier capacity, analyze data on a per-carrier, per-sector basis. Since the Performance Management reports from the CBSC provide Walsh Code usage on a per-carrier, per-sector basis, establish an RF carrier capacity limit based upon data from these reports. There are two capacity limits that need to be established for various different BTS/system design configurations:
S Walsh Code Usage Maximum Limit S Walsh Code Usage Planning Limit.
Walsh Code Usage Maximum Limit
There are three steps involved in establishing a general set of guidelines for a Walsh Code Usage Maximum Limit that can be applied to the Walsh Code minutes of usage on a per-sector basis. These steps are: 1. Establish a general set of guidelines Establish a Maximum Limit of Erlang usage on a per-sector basis. Table 7-1 provides a set of general guidelines for the maximum limit of Erlangs. These have been established through simulations for various different BTS/system design configurations. The generalized system simulation parameters used to create these limits provided for a mobile environment, with a high speed profile, using a full rate paging channel, and designed for a 95% RF reliability. In addition, the system was designed to be interference limited (in other words, the sites were spaced relatively close together). Another point to be made is that the system had ideal cell placement (all on grid) and assumed flat terrain. The values in Table 7-1 reflect maximum capacity design limitations. Some systems may have traded capacity for coverage (to obtain a larger RF footprint) to reduce the number of sites initially
7-4 CDMA SC Products System Resource Guide (CSSRG) June 2001
deployed. Adjustments to the values in Table 7-1 can be made if different system design parameters are assumed. If a system has been designed, per a service provider request, to carry a certain amount of BTS/sector-level of Erlang traffic, such design guidelines can be used to establish a maximum limit. Use caution when discussing the type of Erlang traffic being considered (in other words, conversation Erlangs, traffic channel Erlangs, or Walsh Code Erlangs). Remember, that traffic channel Erlangs are conversation Erlangs with Soft Handoff (SHO) usage added to them and that Walsh Code Erlangs are conversation Erlangs with Soft and Softer Handoff (SSHO) usage added to them. BTS/sector-level Erlang design guidelines which are in the form of Walsh Code Erlangs are given in Table 7-2. As an alternate approach, use the Reverse Load Detection/Forward Load Detection (RLD/FLD) metrics to develop a generic set of guidelines (refer to the application note titled Forward and Reverse Link Load Detection Metrics, version 1.0, dated July 2, 1997). If RLD/FLD metrics are available and there is a significant amount of sites/sectors which demonstrate sufficient correlation, then averaging together the RLD/FLD Erlang projection results to establish a generic set of guidelines is also a viable option. In the absence of service provider design guidelines, RLD/FLD results, or any other approved method of measuring the maximum Erlang guideline for a particular system, the following guidelines in Table 7-1 are a reasonable nominal set of values to use on a per-sector, per-carrier basis. NOTE A set of Maximum Limit of Erlangs guidelines is provided below, but the values can be adjusted per specific service provider request or design criteria (as required).
June 2001
7-5
Table 7-1: Guidelines for Maximum Limit of Conversation Erlangs Frequency Vocoder Omni ThreeSector SixSector 800 MHz 13 kb 8.4 6.0 5.2 800 MHz 8 kb 20.6 15.5 14.2 1900 MHz 13 kb 10.6 7.2 6.6 1900 MHz 8kb 26.0 (a) 18.6 (a) 18.0 (a)
NOTE
(a) Interpolated from the 13kb data.
S S S S
Mobile Environment 95% RF Reliability High Speed Profile Full Rate Paging. The above guidelines do not apply to Wireless Local Loop (WiLL) systems utilizing Fixed Wireless Terminals (FWTs) or to systems with mixed rate vocoders deployed. These deployed vocoders can be 8 kb voice and 13 kb voice or 8kb voice and 13 kb High Speed Packet Data via IS95B. For those systems, guidelines need to be established either through simulations and/or field data, along with the service provider design criteria. Refer to the latest version of the CDMA Design Rules for Mobile and Fixed Systems document for additional information regarding Erlang capacities for different system design configurations. For systems designed to provide data services, its important to use a Walsh Code usage value for RF carrier planning that is a combined total of voice and data usage. 2. Convert conversation Erlangs to Walsh Code Erlangs The next step is to apply a system-level Soft and Softer Handoff factor (SSHO) which is then multiplied by the Maximum Limit of Erlangs per sector to establish a Walsh Code Erlangs Maximum Limit per sector. For those situations where a fully loaded SSHO value is not readily available, use a budgetary value of 2.0 for estimating purposes (as is used in the data below). If a system is not under a fully loaded condition, obtaining a measured value of the SSHO factor from a partially loaded system is not an appropriate value to use, since the natural trend for a growing system is for the SSHO value to decrease as the traffic on the system increases. For most mobile applications, apply a budgetary value of 2.0.
7-6
June 2001
Table 7-2: Guidelines for Walsh Code Erlangs Maximum Limits Frequency Vocoder Omni ThreeSector SixSector 800 MHz 13 kb 16.8 12.0 10.4 800 MHz 8 kb 41.2 3.0 28.4 1900 MHz 13 kb 21.2 14.4 13.2 1900 MHz 8kb 52.0 37.2 36.0
NOTE S SSHO = 2 S Mobile Environment S 95% RF Reliability S High Speed Profile S Full Rate Paging.
3. Convert the Walsh Code Erlangs to Walsh Code usage minutes Since the typical traffic report provides Walsh Code usage data in minutes for the Bouncing Busy Hour, the measurement period for RF carrier capacity data analysis is 60 minutes. Therefore, the final step is to convert the maximum limit of Walsh Code Erlangs per sector to a Walsh Code usage maximum limit (in minutes) per sector by multiplying the Walsh Code Erlang limit by 60 minutes.
Table 7-3: Guidelines for Walsh Code Usage Maximum Limits (in minutes) Frequency Vocoder Omni ThreeSector SixSector 800 MHz 13 kb 1008 720 624 800 MHz 8 kb 2472 (a) 1860 1704 1900 MHz 13 kb 1272 864 792 1900 MHz 8kb 3120 (a) 2232 (a) 2160 (a)
NOTE
(a) Configuration may be Walsh Code limited to 1970 minutes (see the following note).
S S S S S
SSHO = 2 Mobile Environment 95% RF Reliability High Speed Profile Full Rate Paging.
CDMA SC Products System Resource Guide (CSSRG) 7-7
June 2001
7-8
June 2001
Introduction
In order to determine RF Carrier utilization, the engineer needs to collect data about how the system is functioning and also determine the present status of the system.
Collect Data
The primary data to collect and monitor is the Walsh Code minutes of usage data on a per-carrier, per-sector basis. For systems with voice and data services (circuit or packet data) deployed, it is important to use a combined total of both voice and data Walsh Code usage for RF carrier planning. For sectored sites, collecting and analyzing just the busiest sector of the entire site should be adequate. For systems which already have multiple carriers deployed, the data needs to be collected and analyzed on a per-carrier basis. Since the analysis is being performed on a cell site/sector-level, the measurement collection interval should be large enough to identify the Bouncing Busy Hour (BBH) peak traffic period for each individual cell. Because traffic patterns vary from site to site, some outer fringe sites BBH may occur in the morning busy period during the subscriber s drive into work, while other core area sites BBH occurs in the afternoon busy period during the subscriber s drive home from work. Additionally, the measurement collection interval should be large enough to capture the Busy Day Bouncing Busy Hour (BDBBH) for the week for each cell. If the monitored system has a significant drop in subscriber usage as well as a shift in the traffic pattern for the weekend, only analyze the weekday data. Collect the BBH and BDBBH usage data for each cell on an ongoing weekly basis, but for the initial baseline measurement, collect and analyze a minimum of four weeks of data. Also, collect and monitor peformance statistics on a per-carrier, per-sector basis (if possible, BBH performance data for each site is desired). The performance statistics consist of a dropped call rate and an access failure (or success) rate (including originations and terminations). Use these statistics to validate the performance of a particular cell or sector as it approaches or exceeds the generic planning or maximum limit. As a result, the typical data collection process stores total BBH Walsh Code usage data (for voice and data) and performance statistics on an ongoing weekly basis. It also stores the BBH time of day for each sector/cell in the system. This is data for Monday through Friday, assuming weekend data can be disregarded. Although the frequency of performing a full analysis depends upon the rate of growth for the monitored system, the minimum recommendation is to perform a full one to two year projection analysis on a semi-annual basis. However, a quarterly full analysis is preferred. In either case,
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-9
perform a weekly review of BDBBH usage data to keep track of any current sites exceeding the maximum limits.
Determine Present Status
Validating the integrity of the data collected is one of the first things to do when determining the present status of the system. Investigate and eliminate partial data or anomalous data from the analysis. If the data represents an abnormal traffic period which should not be considered as part of the normal traffic environment, the abnormal data will not be useful for future traffic forecast estimates. Once the data is validated, analyze the four week average of BDBBH data for each sector (on a per-carrier basis for systems with multiple carriers). Identify any sectors which exceed either of the Walsh Code Usage Planning or Maximum Limits. If one or more sectors exceed the Walsh Code Usage Planning or Maximum Limit, monitor the BBH performance statistics trend for those cells/sectors. Determine if there is an increase in performance degradation occurring with elevated BBH Walsh Code usage. At this point, an evaluation review of the planning and maximum limits may be necessary. This determines if adjustments need to be made to either of the limits to better reflect the desired performance, capacity, or service providerdesired results. Regardless of the performance statistics results, start investigating the capacity management options for those cells/sectors exceeding the limits. Determine if a capacity management plan is required. The objective of capacity management planning is to implement capacity relief mechanisms before a performance degradation occurs. Therefore, performance degradation should not be a requirement for determining or implementing a capacity management plan. Use performance degradation to increase the priority of implementing capacity relief options to those cells/sectors exhibiting the performance degradation. Those sites which exceed the maximum limit but do not reflect any performance degradation should be next on the priority list for implementing capacity management/relief options. Establish the planning limit and the maximum limit into category regions which represent a stoplight level of urgency. Apply these limits to the BDBBH Walsh Code usage data and analyze the data on a weekly basis. The green region represents a low-level of urgency with the BTS Walsh Code usage ranging from low usage up to the planning limit. The yellow region represents a moderate-level of urgency with the BTS Walsh Code usage ranging from the planning limit to the maximum limit. Finally, the red region represents a high-level of urgency with the BTS Walsh Code usage being greater than the maximum limit. Monitoring the Walsh Code usage data in this fashion can be used to simplify the notification of potential problem areas. The appropriate capacity relief management plan to choose on a BTS-level can depend upon many different factors, such as the:
Market size Terrain Site footprint Desired in-building penetration Site acquisition availability Design of the system Rate of market growth Number and location of the sites/sectors which exceed the planning or maximum limit.
The system designer chooses among the appropriate capacity management options to create a capacity management plan that best fits the particular situation. A summary of the capacity management/relief options are listed below. Also, refer to the RF Capacity Management Options section for more details on the options stated below.
June 2001
7-11
Introduction
RF Carrier Planning Limits are determined by evaluating several limits, identifying any bottlenecks, and then applying the remedies that alleviate those bottlenecks. This topic describes the limits, bottlenecks, and remedies that the engineer can expect to encounter.
Walsh Code Usage Planning Limit
The following establishes a general set of guidelines for a Walsh Code Usage Planning Limit. Apply these guidelines to the Walsh Code minutes of usage on a percarrier, per-sector basis. The Planning Limit is typically a certain percentage of the Walsh Code usage Maximum Limit. The Planning Limit is recommended to be 80% of the Maximum Limit. Again, the values can be adjusted per specific service provider design criteria (as required). Table 7-4: Guidelines for Walsh Code Usage Planning Limits (in minutes) Frequency Vocoder Omni ThreeSector SixSector 800 MHz 13 kb 806 576 499 800 MHz 8 kb 1978 (a) 1488 1363 1900 MHz 13 kb 1018 691 634 1900 MHz 8kb 2496 (a) 1786 1728
NOTE
(a) Configuration may be Walsh Code limited to 1970 minutes.
S S S S S
80% Maximum Mobile Environment 95% RF Reliability High Speed Profile Full Rate Paging.
When the system-level Planning Limit is exceeded, the primary RF capacity management option is to add an additional CDMA RF carrier to the system. The purpose of the systemlevel Planning Limit is to establish a minimum set of requirements needed to deploy a new carrier. Use the previously established BTS-level limits to create a system-level planning limit. Several different approaches can be used to establish a general set of guidelines for a system-level Planning Limit. These can be applied to the
7-12 CDMA SC Products System Resource Guide (CSSRG) June 2001
number of sectors or sites, which exceed one or both of the BTS-level Walsh Code limits. Some of the options are listed below. The system-level Planning Limit can be established from one or more of these options. Again, the values can be adjusted per specific service provider design criteria (as required).
S A minimum cluster of seven sites (one core and six surrounding sites)
with at least one sector in each site which exceed the Walsh Code Usage Planning Limit. Discuss the system-level Planning Limit with the service provider and try to establish a mutually feasible limit which allows plenty of time to perform capacity management on a system-level magnitude.
BTS- and system-level Planning Guidelines
The Systems Engineer can do the following to create a set of guidelines used to perform RF carrier capacity management planning on a BTSand system-level:
S S S S
Forecast Utilization Identify Bottlenecks Evaluate Relief Alternatives Implement Relief Mechanisms.
These steps utilize strategies to perform capacity management planning, along with the site- and system-level limits established in the Establishing Limits section. They also allow some flexibility to adjust some of the recommendations to optimize the approach to a particular service provider s desire. With a CDMA system, RF carrier capacity management planning and monitoring is required to be performed on an ongoing basis. Perform and analyze the following steps individually, on a per-carrier basis, for those systems with multiple carriers already deployed. Analyze each carrier like its own separate system. The analysis should typically forecast out in time up to one to two years from the present date and should be repeated on a periodic basis. The frequency of the planning and monitoring exercise depends upon how fast the system usage grows. The more frequent the monitoring, the sooner a plan can be formulated and implemented to resolve any capacity management issues before it causes severe performance degradation.
Forecast Utilization
Several different strategies can be used to forecast RF link utilization. Each of them has different merits. The marketing departments of cellular
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-13
operators typically project future growth through subscriber projections, which are then used as the baseline parameter to gauge future system utilization. Ultimately, for RF carrier planning, what is required is a forecasted estimate of total Walsh Code usage minutes (for voice and data) on a per-carrier, per-cell/sector basis. If the service provider s marketing department provides the Systems Engineer with subscriber projections for an RF carrier growth analysis, then the following procedure can be used to forecast Walsh Code usage minutes on a per-cell/sector basis. Table 7-5 shows an example of a spreadsheet which can be easily created to perform the following forecast of Walsh Code usage minutes. Table 7-5: Example Spreadsheet to Forecast WC Usage A
BTS ID
B
Week 1 BDBBH WC Min 1092 536 704 340 605
C
Week 2 BDBBH WC Min 957 490 709 325 633
D
Week 3 BDBBH WC Min 1012 524 743 374 634
E
Week 4 BDBBH WC Min 982 447 779 380 577
F
AVG
G
STD
H
Current Subs
I
AVG WC Usage per Sub 0.02022 0.00999 0.01468 0.00710 0.01225
J
AVG + 3 STD WC Usage per Sub 0.02373 0.01238 0.01676 0.00869 0.01387
K
Future Subs
L
AVG WC Min Future 1516 749 1101 532 918
M
AVG + 3 STD WC Min Future 1780 928 1257 651 1040
1 2 3 4 5
59 40 35 27 27
1. Collect the Busy Day Bouncing Busy Hour (BDBBH) Walsh Code usage minute data for four weeks worth of current data (four data points per sector, one per week), for each cell/sector in the system on a per-carrier basis. Alternatively, one data point per week, per carrier, per site, using the busiest sector of the site can also be used (in other words, trending just the busiest sector of a site instead of all sectors is adequate). See columns B thru E. 2. Baseline the system by calculating the average BDBBH Walsh Code usage minutes from the four weeks worth of current data for each cell/sector in the system [in other words, AVERAGE(B1:E1)]. See column F. 3. Calculate the standard deviation (one-sigma) for the average BDBBH Walsh Code usage minutes for each cell/sector in the system [in other words, in MS Excel STDEV(B1:E1)]. See column G. 4. Obtain the average number of subscribers using the system associated with the four weeks of data being analyzed. See column H. 5. Calculate the Average BDBBH WC usage per subscriber on a per-cell/sector basis [in other words, F1/H1]. See column I. 6. Calculate the Average BDBBH WC usage + three-sigma per subscriber on a per-cell/sector basis [in other words, (F1+(3*G1))/H1]. See column J.
7-14 CDMA SC Products System Resource Guide (CSSRG) June 2001
7. Obtain the projected subscriber growth for the system. See column K. 8. Calculate the projected Average BDBBH WC usage on a per-cell/sector basis [in other words, K1*I1]. See column L. 9. Calculate the projected 3-sigma Average BDBBH WC usage on a per-cell/sector basis [in other words, K1*J1]. See column M. If the service provider s marketing department provides the Systems Engineer with something other than subscriber projections, modifications to the approach above can project a linear relationship according to the service providersupplied projection parameter. If the service provider requires a non-linear growth projection, modifications to the above approach depend upon the specified non-linear growth projection requirements. For example, the service provider may specify a variable subscriber growth rate along with a variable usage rate. These rates may be based upon seasonal changes and/or marketing promotions. In either case, the desired outcome is to project an average BDBBH Walsh Code usage and a three-sigma average BDBBH Walsh Code usage (in minutes) for each cell/sector on a per-carrier basis. Make adjustments to the process of forecasting utilization when judged appropriate. For instance, if a larger statistical data sample is desired, more than four BBH data points can be used for the calculation of the monthly average and the standard deviation. Using additional data captured during lesser busy days of the week reduces the overall average and provides a less conservative prediction. Also, a different multiplication factor other than three can be used for the standard deviation multiplier. Using a lower multiplier (X) for the X-sigma average calculation provides a less conservative prediction. Several adjustments to the process, as specified above, can be made depending upon how conservative the engineer wishes to be. These adjustments are:
Once the Walsh Code usage has been forecasted on a per-cell/sector, per-carrier basis, it is time to again identify, on a BTS-level, any sectors which exceed either of the Walsh Code Usage Planning or Maximum Limits. On a system/CBSC-level, analyze the data to determine if the system-level Planning Limit has been exceeded. Establish the planning
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-15
limit and the maximum limit into category regions which represent a stoplight level of urgency which is applied to the forecasted Walsh Code usage data (for both average and threesigma values) and analyzed. The green region represents a low-level of urgency with the BTS Walsh Code usage ranging from low usage up to the planning limit. The yellow region represents a moderate-level of urgency with the BTS Walsh Code usage ranging from the planning limit to the maximum limit. Finally, the red region represents a high-level of urgency with the BTS Walsh Code usage being greater than the maximum limit.
Evaluate Relief Alternatives
Decide whether to add more CDMA sites, add another CDMA carrier, or some other option listed in the RF Capacity Management Options section. By adding additional CDMA sites to offload high traffic CDMA sites, capacity is gained in an incremental stage. For a mixed-mode analog/CDMA system, this scenario is more likely done when the CDMA system is not a 1:1 ratio with the analog sites. When an additional carrier is implemented system-wide, the capacity of the system increases overnight by the capacity offered by the new carrier. For instance, if a second carrier is added throughout the system, the RF carrier capacity of the system could double overnight, depending upon the number of channel elements equipped on the second carrier. This might not be ideal since spectrum may need to be cleared and it is a major expense to install the additional carrier equipment at every site. Plot the Walsh Code usage data in a red/yellow/green stoplight fashion onto a system/CBSC-level BTS location map. Analyze this map to identify isolated cells and/or determine areas which have exceeded the system-level Planning Limit. These areas are candidates for adding a new CDMA carrier. Create two separate plots using:
S Projected average Walsh Code usage data S Projected average plus three-sigma Walsh Code usage data.
A set of Walsh Code usage location maps as described above should be created for each carrier deployed in the system. For evaluation purposes, create a set of Walsh Code usage location maps for a series of key dates in the future (in other words, 6, 12, 18, and 24 months out in time). If the map creation can be simplified through automation, perform a more thorough evaluation by creating a set of Walsh Code usage maps for a higher frequency of future dates (in other words, on a quarterly or monthly basis). The amount of dates analyzed (or maps created) depends upon the level of detail desired. In general, use the average forecasted Walsh Code usage data to identify isolated cells which require capacity management options. Use the average three-sigma forecasted Walsh Code usage data to identify region(s) which require an additional carrier (in other words, areas which exceed the systemlevel Planning Limit). Isolated cells or sectors with average forecasted data which exceed the planning or maximum limits are candidates for capacity management options mentioned in the Determine Present Status section and expanded
7-16 CDMA SC Products System Resource Guide (CSSRG) June 2001
upon in the RF Capacity Management Options section. If the isolated sectors which exceed the Walsh Code limits are scattered throughout a CBSC boundary or a multiple CBSC boundary, adding a localized additional carrier to cover the entire affected region may be the best choice. If most of the sectors which exceed the Walsh Code limits are localized to one or two large regions within a CBSC boundary or a multiple CBSC boundary, adding a localized additional carrier to the affected regions is probably the best choice. Perform this type of analysis for both the average and three-sigma forecasted Walsh Code usage data. Analyze results from both sets of data to identify BTSs in a logical region or regions which are target candidates for a new carrier. Region(s) identified by using the average data can be considered the minimum region to deploy a new carrier. Region(s) identified by using the three-sigma data, while considered a more conservative result, can also be considered as a recommended region to deploy a new carrier. Since the effort of planning, deploying, and optimizing a new carrier is significant, employ a more conservative approach and use the three-sigma data to determine the new carrier region(s). If the system is setup for a 13kb vocoder rate and if a significant percentage of subscribers already deployed in the system are EVRC compatible, implementing a system-wide 8kb EVRC deployment may be an alternate choice to delay the deployment of an additional carrier. It is difficult to determine the benefit impact of deploying EVRC as a system-level capacity management option since the number of EVRC users, their traffic patterns, and usage patterns are all variables which impact the overall EVRC capacity benefit. If 100% of the subscribers in the system are EVRCcompatible, the benefit can be determined by comparing the 13kb to 8kb Walsh Code capacity limits in the Establishing Limits section for the particular BTS/system configuration. If its decided to add an additional carrier (either in a localized area or ubiquitous), the next decision to make is how to add the supporting CBSC infrastructure required to support the additional capacity provided by the new carrier. There are basically three approaches to expanding CBSC capacity to support a new carrier added to a system (refer to Centralized Base Station Controller (CBSC) chapter for more information): S Implement the new RF carrier within the existing CBSC infrastructure or layer to expand the RF carrier capacity. Add additional CBSCs through CBSC splitting at a later date to expand the infrastructures call processing capacity. S Implement the new RF carrier within the existing CBSC infrastructure or layer to expand the RF carrier capacity. Upgrade the CBSC(s) to a higher capacity model (if possible). S Implement the new RF carrier with a Layered CBSC Overlay approach (see the Centralized Base Station Controller (CBSC) chapter for more details on this approach). This expands the RF carrier capacity and the associated CBSC infrastructures call processing capacity at the same time.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-17
From an engineering perspective, add both the RF carrier capacity along with the supporting CBSC infrastructure capacity at the same time by using the Layered CBSC Overlay approach. This typically depends upon the maximum carrier capacity per frame for the BTS product predominantly deployed in the system. Adding a new carrier with the Layered CBSC Overlay approach requires a new BTS frame to be installed at each and every site which requires the new carrier. From a cost of deployment perspective, it may make more sense to maximize the number of RF carriers per frame for the particular BTS product line. Do this by installing additional hardware into the existing BTS frame to add the new carrier to the existing CBSC layer. This does not mean maximizing the total number of carriers a BTS product line can support, but maximizing the total number of carriers that the BTS product line can support in one frame. If it has been determined that additional frames are required for most of the BTSs in order to add the new carrier, implement the new carrier (new frames) with the Layered CBSC Overlay approach. In summary, the recommended solution is to add RF carriers onto a single CBSC layer to maximize the carrier capacity of the particular BTS product line predominately deployed in the region. Then, implement a Layered CBSC Overlay approach for the next carrier beyond the BTS product line single frame maximum carrier capacity. The appropriate capacity management plan to choose on a BTS- or system-level depends upon many different factors, such as the: S Service provider inputs and requests S Cost of implementation S Market size S Terrain S Site footprint S Desired in-building penetration S Site acquisition availability S Design of the system S Rate of market growth S Number and location of the sites/sectors which exceed the planning or maximum limit. It is up to the Systems Engineer to choose among the appropriate capacity management options to create a capacity management plan that best fits the particular situation.
Implement Relief Mechanisms
Establish schedules and contingencies for the relief mechanisms. Generic guidelines for implementing relief mechanisms are as follows: S If relief includes enhancing elements, determine availability of new equipment. S For any relief mechanism, determine length of time needed to implement change.
7-18 CDMA SC Products System Resource Guide (CSSRG) June 2001
Identify dates for scheduling the changes. Create a method of procedure. Identify backup plans for schedule changes. Make changes according to the schedule. NOTE Making any change to the network requires re-evaluation of the processes previously established. Therefore, make changes to the process concurrently with changes in the physical network.
June 2001
7-19
Introduction
As a cell site approaches its maximum RF carrier capacity, several different symptoms help to identify an overload condition. The following symptoms are a sample of those indicating an RF link overload condition:
S S S S S
LPA/PA equipment overload in the transmit link The Ec/Io of the carrier degrades Interference/noise rise in the reverse link Blocking due to Walsh Code limitations Excess analog overflow redirections (assuming the system has analog overflow capability) (cell/sector basis)
S High Frame Error Rate (FER) Rate on the forward and reverse link S The coverage area gets smaller causing coverage holes S May see an increase in dropped call, handoff failure, and/or access
failure rates. As the traffic level of a site increases closer to its capacity limit, the resulting performance may vary from site to site. Typically, the performance of the site just gradually degrades. In sites that are way outside the core, the statistics may get steadily worse as the traffic increases. In some sites close to the freeways, the statistics may get better when the site is loaded up with more traffic. In general, degradation in quality is gradual and not a step function.
7-20
June 2001
Introduction
The engineer can reduce RF Carrier utilization and improve system capacity by developing an RF capacity management plan to address all of the issues identified in the RF Carrier Planning Limits section. The appropriate capacity management plan to choose on a BTS- or system-level depends upon many different factors. This section provides more detail on the various different capacity management options available and some of the logic for determining when to choose a particular option. It is up to the Systems Engineer to choose among the appropriate capacity management options available to create an overall capacity management plan that best fits the particular market and situation. Optimization For isolated situations requiring immediate attention, utilizing optimization techniques for capacity management relief is a viable option. This is because it is relatively easy and quick to implement optimization parameter changes. Since the capacity benefit is too difficult to estimate, this type of capacity relief is typically applied to resolving a present status situation. It is not usually part of a forecasted capacity management plan. It can be implemented on a permanent basis or it may also be used as a temporary capacity relief mechanism until a longer term option can be implemented. Because coverage, capacity, and quality are all inter-related functions of a CDMA system, to increase capacity, the engineer must decrease coverage or quality. Since reducing quality is typically not a desired option, the optimization techniques provided focus on reducing coverage for the area of concern. The primary objectives in using optimization techniques for capacity relief is to optimize and reduce the overall power requirements (to decrease the overall interference level if possible) and/or to reduce the coverage area for the area of concern. For areas which have multiple pilots causing some degree of pilot pollution, the optimization process includes a power reduction for some of the undesired sources of pilot pollution interference. NOTE Reducing power levels and/or the coverage area could have a negative impact on system performance. A cautious approach should be employed when implementing capacity relief optimization techniques in order to ensure adequate system performance.
June 2001
7-21
Power Control Parameter Adjustments If the system, or area of concern, appears to be forward link limited, forward link power control optimization may provide some capacity relief. In an attempt to reduce the overall forward power requirements for a particular area, the optimization engineer may try adjusting the Target FER parameter within the SECGEN command (starting with Release 7). The Target FER can be changed by the customer in order to get a higher capacity while trading off average forward FER. The values for the Target FER parameter range from FER_A to FER_D. A value of FER_A provides the most aggressive quality parameters which produce a lower average FER. A value of FER_D provides parameters designed to optimize capacity while still providing an acceptable average FER. The regions that benefit the most from Target FER changes are those with high traffic load and/or high multi-pilot interference. These regions experience less degradation during loaded conditions and are able to handle more capacity before they experience degradation in RF loss system performance. Even though the Target FER parameters are service provider changeable parameters, implement adjustments to these parameters cautiously in order to ensure adequate system performance. Adjustments to the Target FER parameters are normally considered a short term capacity relief option. However, if after making the Target FER adjustments, a service provider determines (through field testing and/or performance metrics) that the voice quality and system performance is acceptable, this option may be considered as a long term solution. If the system, or area of concern, appears to be reverse link limited, the optimization engineer may adjust the reverse power control (BTSRPC and MSRPC) parameters in a direction which lowers the overall power transmitted to the base station. The BTSRPC and MSRPC parameters are not recommended as service provider changeable parameters. Adjusting the reverse link power control parameters in an attempt to increase the reverse link capacity is not recommended. A Target FER feature for the reverse link is required, but currently does not exist. Coverage Area Adjustments If the particular area of concern has one sector carrying a higher amount of traffic (when compared to other sectors in the same area), it may be possible to shift some of the traffic from a busy sector to some other less busy sector(s). Make adjustments to the coverage area to reduce coverage or shift traffic through one or a combination of both of the following approaches:
either case, monitor the system performance of the area for any significant degradation after making any coverage area optimization adjustments. Modify Existing Site RF carrier capacity management options on a BTS-level can take various different forms:
See the Base Transceiver Station (BTS) chapter for more details on adding traffic channels. Sectorization
7
Increasing the sectorization of the site is one way of expanding the RF carrier capacity of an existing site (if it is supported by the particular BTS product line). Expansion takes the form of converting an omni site to a three-sectored site. Or, converting a three-sectored site to a six-sectored site. The capacity benefit for this type of option can be estimated by calculating the differences in generic capacity limits from one configuration to the other. For example, an omni site at 800 MHz with an 8kb vocoder is estimated to carry 20.6 Erlangs while a three-sector site under the same conditions is estimated to carry 15.5 Erlangs per sector or 46.5 Erlangs per site. In this example, the BTS can more than double its Erlang capacity by converting the site from an omni to a three-sector configuration (assuming the traffic is distributed equally to each sector). Since the capacity benefit for sectorization can be estimated, this type of capacity relief can be applied towards a forecasted capacity management plan. The maximum benefit typically occurs when the traffic is equally distributed to each sector of the site.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-23
Although there is still some planning and preparation required to sectorize a site, this type of capacity relief can also be applied towards resolving a present status situation as well, if sectorization hardware is readily available. Add PA Capacity Some BTS product lines have an expandable PA which can be sized for different power requirement applications. For most applications under normal conditions, the designed power output capacity of the PA should be adequate to handle the maximum limit loading requirements for the CDMA carrier. For those sectors operating at or above the maximum Walsh Code usage limit, analyze the BTS PA power requirements and determine if additional PA power capacity is required (if it is possible for the particular BTS product). The additional analysis takes the form of making field measurements of the actual output power requirements or analyzing forward power requirements from simulation results, such as those provided by the NetPlan CDMA simulation tool. Refer to the CDMA RF Planning Guide and to the CDMA RF System Design Procedure for more information on simulating the PA power requirements. If the results of either analysis show the site is operating close to the maximum rated output power capacity for the particular BTS product, implement additional PA capacity (if possible). If the performance of the PAs coverage area allows a power reduction, adjust the SIF_Pilot_Power parameter to reduce the overall PA output power requirements. This is an alternate method of providing PA capacity relief. Prior to the LPA Overload Protection feature, this type of capacity management option is typically not applied until after the PAs for a particular sector have already exceeded their maximum power limit, triggered a high power alarm, and then taken themselves out of service. With the introduction of Phase 1 of the LPA Overload Protection feature (FR 1225A), single tone LPAs for the four digit BTS product line no longer require manual intervention to bring the LPAs back in service when a high power alarm occurs. Phase 1 of this feature provides auto recovery for an overload condition and then calculates a threshold level used to prevent the forward transmit power from reaching a level that overdrives the impacted LPAs again. Phase 2 of this feature (FR 1225B) supports all BTS product lines and also provides userspecified call blocking criteria and adjustable RF power thresholds. For systems using a software release supporting the LPA Overload Protection feature,
7-24 CDMA SC Products System Resource Guide (CSSRG) June 2001
adding PA capacity is still option (if possible), but it becomes less of a priority when compared to those systems without the feature. NOTE Consider adding PA capacity as a temporary safeguard measure since the site is already operating at the maximum limit. Plan other capacity relief mechanisms for any site near or exceeding the maximum limit. This type of capacity management option is typically applied towards resolving a present status situation.
Walsh Code Limiting The designed power output capacity of the PA should be adequate to handle the maximum limit loading requirements for the CDMA carrier, for most applications under normal conditions. With the introduction of the LPA Overload Protection feature, Walsh Code limiting is no longer necessary in order to protect the LPA from an overload condition. For LPAs without the Overload Protection feature, Walsh Code limiting can be implemented to restrict the maximum number of simultaneous users of a site/sector which can limit the power requirements of an LPA. For those sectors operating near or above the maximum Walsh Code usage limit and where the BTS product line does not have an expandable PA or the LPA Overload Protection feature, analyze the BTS PA power requirements and determine if Walsh Code limiting needs to be implemented. Additional analysis takes the form of making field measurements of the actual output power requirements or of analyzing forward power requirements from simulation results, as provided by the NetPlan CDMA simulation tool. Refer to the CDMA RF Planning Guide and to the CDMA RF System Design Procedure for more information on simulating the PA power requirements. If the results of either analysis show that the site is operating close to the maximum rated output power capacity for the particular BTS product, then implement Walsh Code limiting. This type of capacity management option is typically not applied until after the PAs for a particular sector have already exceeded their maximum power limit, triggered a high power alarm, and then taken themselves out of service. NOTE Consider this option as a temporary safeguard measure. Also plan other capacity relief mechanisms for this site. This type of capacity management option is typically applied towards resolving a present status situation.
June 2001
7-25
This option limits the capacity of the site. Therefore, it blocks from service any traffic growth beyond the Walsh Code limit setting. Adding a New Carrier to a BTS To add carriers to an existing BTS requires the installation of additional equipment. Depending upon the BTS product and software available, this could take the form of a new:
S S S S
CCP shelf and associated cards (BBXs, MCCs, etc.) BTS frame and CCP shelf and associated cards SC6xx cabinet BBX cards and associated cabling for the double density CCP-12 cages.
Refer to the Base Transceiver Station (BTS) chapter to determine the number of carriers that can be supported by the specific BTS product. Various RF cabling is required to connect the receive and transmit signals to the appropriate location. There are different requirements which depend upon whether or not the carrier being added is within the same RF frame or in a new RF frame. It may be necessary to provide a new span line connection to the new shelf and/or frame in order to implement a new carrier. In some cases, it may be possible to utilize the existing span by using a grooming function to provide the span connectivity to the new shelf/frame. The appropriate span configuration depends upon the span interface requirements for the particular BTS product used and the number of time slots required to support all of the channel elements for all of the carriers supported. New hardware requires RF calibration. Therefore, a service outage is recommended. Once the physical changes are complete, make updates to the OMC-R/CBSC database and download software and data to the new modules. Add a New Site The following provides information about adding a new site as a capacity relief option. The two basic options provided are to:
S Cell split by adding a new macro-site to the area S Add one or multiple micro-site(s) to the area.
Cell split by adding a new macrosite to the area Use the cell split option to offload the coverage area of two or more existing cells/sectors. Use this option in forecasted growth plans by estimating the percentage of capacity relief the new cell site provides when it is implemented. The growth plan takes into account the amount of capacity relief provided by a new site. This allows the plan to continue into the future until the next site/sector exceeds the planning or maximum limit. Figure 7-1 shows a typical example where a cell split is used to offload three high traffic sectors within a network.
7-26 CDMA SC Products System Resource Guide (CSSRG) June 2001
Cell B 1 3 2
Cell A 1 3 2 1
Cell C Before
Cell C After
Isolated high traffic sites/sectors are the typical areas to apply a cell split capacity relief option. The implementation of a cell splitting option also improves the RF coverage in the area of the new cell site. This added benefit may influence the usage of the cell splitting option. For example, in the early stages of a system initially designed for in-vehicle coverage, the cell splitting option may be the predominant option chosen. This is to migrate the system into providing desired in-building coverage. Some of the coveragerelated benefits are listed below:
S Improve an existing marginal coverage area S Improve general in-building coverage S Improve coverage/capacity for a high profile business district.
Typically, a large cluster grouping of several high traffic sites/sectors requiring capacity relief are more suitable for adding an additional carrier. Add one or multiple micro-site(s) to the area Use the micro-site(s) for the following areas which are within the coverage area of an existing macro-site:
S S S S
The micro-cell option, when applied towards capacity relief, is typically used to offload the coverage area of one existing cell/sector of the system. Use this option in forecasted growth plans by estimating the percentage of capacity relief the new micro-cell provides when implemented in the future. Therefore, the growth plan takes into account the amount of capacity relief a new micro-site provides. This allows the plan to continue with the growth plan into the future until the next site/sector exceeds the planning or maximum limit. In order to accomplish this, generic planning and maximum Walsh Code usage limits need to be established for a micro-cell configuration.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-27
Figure 7-2 shows a typical example where a micro-cell is used to offload two high traffic areas within an existing macro-cell coverage area. Figure 7-2: MicroCell Example
Macro-Cell A
Macro-Cell A Micro-Cell B
Micro-Cell C
Before
NOTE
After
Implementing a CDMA micro-cell is different than implementing an analog micro-cell. Typically in analog, implementing a micro-cell provides fixed BTS hardware deployment for that particular location with a fixed amount of capacity. In CDMA, adding capacity by implementing an additional CDMA carrier to an area (which has micro-cells deployed), requires additional micro-cell carrier hardware to be installed to support the additional carrier capacity.
Site planning for a CDMA micro-cell needs to take into account the carrier growth potential and the hardware associated with supporting a multiple carrier micro-cell configuration. Investigate the multiple carrier micro-site configuration limitations prior to deploying a micro-cell in an area which most likely requires multiple carrier service. The capacity of the micro-cell depends upon the RF signal from the macro-cell. The micro-cell may see the macro-cell as interference and therefore limit the capacity potential of the micro-cell. Deploy a New Carrier If a network continues to grow its subscriber population, the RF capacity of the network dictates the need to add a new RF carrier to the network. Depending upon the size of the network and if there are isolated sectors exceeding the Walsh Code limits scattered throughout the entire network, adding a ubiquitous carrier which covers the entire network may be the best choice (see Figure 7-3).
7-28
June 2001
RF Carrier Analysis
If most of the sectors from an RF carrier analysis exceeding the Walsh Code limit are grouped together to one or two large regions within a CBSC boundary or a multiple CBSC/System boundary, adding a new non-ubiquitous carrier to the affected regions is probably the best choice (see Figure 7-4). Figure 7-4: NonUbiquitous Carrier Example #1
RF Carrier Analysis
If there are isolated sectors exceeding the limit scattered throughout a CBSC boundary or a multiple CBSC/System boundary, but not spanning the entire network, these sectors are also candidates for a new non-ubiquitous carrier to be implemented to the affected region (see Figure 7-5).
June 2001
7-29
RF Carrier Analysis
Since the effort of planning, installing, optimizing, and deploying a new carrier is significant, employ a more conservative approach when establishing the new carrier region(s). From an engineering perspective, it is recommended to build out a new carrier deployment to a larger conservative area than actually needed before it is needed. Its better to allow the system to grow gracefully into a new carrier region, rather than continuously expanding the new carrier region to keep up with a growing demand. Implementing a Non-Ubiquitous Carrier
Implementing a non-ubiquitous carrier requires the non-ubiquitous multiple carrier region to be surrounded by a transition zone (see Figure 7-6). This creates an added level of complexity to the system design through the requirement of a transition zone border design and management. Transition zones are required to perform a hard handoff from one carrier frequency to another in order to transition from a non-ubiquitous multiple carrier region to a ubiquitous multiple/single carrier region. Subscribers leaving the non-ubiquitous region need to transition to the ubiquitous region to maintain the call going to the fringe of the system. The back-to-back transition sites labeled 1, 2, and 3 shown in Figure 7-6 provide an example of how not to design a transition border. For most applications, those three sites would be better off being designed as fullyequipped multiple carrier sites rather than transition sites.
7-30
June 2001
Ubiquitous Carrier
Transition Carrier
1 2 3
Multiple Carrier
There are currently two methods used to transition from one carrier to another. The transition from a multiple carrier region to a ubiquitous carrier region can be performed with:
S Mobile Assisted HandOffs (MAHO) using pilot beacon hardware S Database Assisted HandOffs (DAHO) using additional sector-carrier
hardware. Both approaches require additional hardware to be installed at each transition site, although all of the sectors of the transition sites may not need to be equipped. For both approaches, perform a propagation study in order to verify that the non-ubiquitous carrier is completely surrounded by coverage from the designated sectors of the transition sites. The hard handoff performance of the MAHO with pilot beacon approach is slightly better than that of the DAHO approach. In general, the MAHO with pilot beacon approach is best suited for multiple carrier seams/hard handoff borders which have a high probability of not moving in the future. This is because the beacon hardware associated with the transition sites needs to be relocated along the new border. For multiple carrier seams/hard handoff borders which do have a high probability of moving in the future, the DAHO approach is probably the best choice. This is because the sector-carrier hardware used for the DAHO transition sites easily converts to a regular traffic carrier. Refer to the latest version of the Cellular Application Note, titled Multiple Carrier Support, for more details on how to deploy an additional carrier using the DAHO or MAHO with pilot beacon approach.
June 2001
7-31
Control Channel
Introduction
Control channel performance directly affects overall system performance because no calls are set up in the system without first utilizing the control channels. Two major aspects of systems performance which are impacted are:
S System Capacity
Too little control channel capacity can limit system capacity Too many control channels can generate interference to the traffic channels and thereby reduce system capacity.
7-32
June 2001
Introduction
There are four different types of control channels associated with the cdmaOne air interface (IS95 air interface specification):
S Pilot Channel
Provides a reference which the mobile station uses for acquisition, timing, and as a phase reference for coherent demodulation.
S Sync Channel
Provides the MS with system configuration and timing information.
S Paging Channel
Used to send control information to subscriber units that have not been assigned to a traffic channel.
S Access Channel
Used for the subscriber unit to send short signaling messages during call setup and registration. Figure 7-7 shows an example of the code channels transmitted by a base station (Forward CDMA Channel). Out of the 64 code channels available for use, the example depicts the Pilot Channel (always required), one Sync channel, seven Paging Channels (the maximum allowed), and fifty-five Traffic Channels. Figure 7-7: Example of Forward CDMA Channels
Access Channels and Reverse Traffic Channels compose the Reverse CDMA Channel. These channels share the same CDMA frequency assignment. A distinct user long code sequence identifies each Traffic Channel. A distinct Access Channel long code sequence identifies each Access Channel. Figure 7-8 shows an example of the signals received by a base station on the Reverse CDMA Channel.
June 2001
7-33
ACCESS CH 0
ACCESS CH N
TCH 1
TCH M
Paging Channel Structure Overhead, subscriber termination, subscriber origination, registration, authentication, and Short Message Service (SMS) messages are factors contributing to paging channel utilization. The following are specifics regarding the paging channel:
S The paging channel data rate is fixed at 9600 bits/second (768 bits per 7
slot or 96 bits per half-frame) or 4800 bits/second (384 bits per slot or 48 bits per half-frame).
S The number of bits that can fit into a half frame is the key factor in
determining PCH utilization.
MessageSize 12
Where:
[EQ 71]
MessageSize is the size of the message in bytes including 5 bytes overhead (1 byte for message length and 4 bytes for CRC + SCI).
7-34 CDMA SC Products System Resource Guide (CSSRG) June 2001
12
is the number of bytes per half-frame at 9600 baud (96 bits divided by 8 bits per byte). NOTE The symbol I > means to round up the number to the nearest integer.
Paging Channel Messaging and Traffic Flow Table 7-6 depicts five events that take place on the paging channel. Table 7-6: Paging Message Type Events BTS MS Paging Message Types Overhead Message > > > > > > > Systems Parameters Message Access Parameters Message Neighbor List Message CDMA Channel List Message Extended Systems Parameters Message Global Service Redirect Message Null Message Mobile Terminated (L to M) Message > < > > General Page (multiple sectors) Page Response Base Station ACK Order Channel Assignment Message Mobile Originated (M to L) Message < > > Origination Message Base Station ACK Order Channel Assignment Message Registration Message < > Registration Message Base Station ACK Order 2 . . . continued on next page
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-35
3 2 3a 1b 2 2c 1
7
2 2
2 2
Table 7-6: Paging Message Type Events BTS > MS Paging Message Types Registration Accept Order SMS/ADDS Page Message > < > Data Burst Message (multiple sectors) Mobile Station ACK Order Base Station ACK Order Feature Notification > < > Feature Notification Feature Notification ACK Order Base Station ACK Order Shared Secret Data (SSD) Update > < > > < > SSD Update Base Station Challenge Order Base Station ACK Order BS Challenge Confirmation Order SSD Update Confirm/Reject Order Base Station ACK Order Unique Challenge 2 2 2 2 2 2 2 215 d Number of HalfFrames (9600 bps) 2
Note S a The number of half-frames is dependent on the number of neighbors. Three half-frames
accommodate 17 neighbors.
S b The number of half-frames is dependent on the number of carriers. One half-frame accommodates
three carriers, two half-frames are necessary if there are 8 carriers.
S c The number of half-frames is dependent on the number of carriers. Two half-frames accommodate
less than six carriers, an additional half-frame is required with six or more carriers.
S d The number of half-frames is dependent on the number of characters being sent. Twelve half-frames
accommodate 120 characters.
7-36
June 2001
Depending upon the paging mode and mobile programming, all or a specific slot may be monitored by the mobile. Two types of paging modes may be implemented: S Non-slotted S Slotted. Non-Slotted Mode Paging and control messages for a mobile station operating in the non-slotted mode can be received in any of the Paging Channel slots. Therefore, the non-slotted mode of operation requires the mobile station to monitor all slots (2048 slots). While this provides the facility for the system to send paging messages on any slot at any time, it also requires the mobile expend more energy in this process, which causes shorter battery life. The response time for a mobile operating in non-slotted mode is the equivalent to the sum of the two-way propagation delay and the required processing time at both the mobile and CBSC. Slotted Mode The paging channel protocol provides for scheduling the transmission of messages for a specific mobile station in certain assigned slots. Support of this feature is optional and may be enabled by each mobile station. A mobile station that monitors the paging channel only during certain assigned slots is referred to as operating in the slotted mode. During the slots in which the paging channel is not being monitored, the mobile station can stop or reduce its processing in order to conserve battery life. This is one advantage of operating in slotted mode. The trade-off for this power conservation is potential page delays and processing overhead due to the fact that the mobile and mobility manager (MM) are required to wait for the assigned slot cycle to send/receive a page. If the system operates in slotted paging mode, the subscriber unit is required to be programmed with a preferred slot cycle index. The larger the slot cycle index (SCI), the longer the potential delay. Table 7-7 indicates the mobiles activity per SCI setting. Currently only SCI values of 0 through 3 are supported for call processing due to the maximum allowable EMX timer setting of 15 seconds for the Repage Time-out Value. Table 7-7: Slot Cycle Index Time Slot Cycle Index SCI=0 SCI=1 SCI=2 SCI=3 SCI=4 Slot Cycle Period 1 2 4 8 16 Duration (secs) 1.28 2.56 5.12 10.28 20.48 Slots per Cycle 16 32 64 128 256 . . . continued on next page
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-37
Table 7-7: Slot Cycle Index Time Slot Cycle Index SCI=5 SCI=6 SCI=7 Slot Cycle Period 32 64 128 Duration (secs) 40.96 81.92 163.84 Slots per Cycle 512 1024 2048
The IS-95 specification defines a slot cycle index of 0 to 7, hence the maximum number of paging channel slots is specified as follows: Paging Channel Slots = 2 (maxium slot cycle index) * 16 slots per cycle = 2 7 * 16 = 2048 A mobile station operating in slotted mode generally monitors the paging channel for one or two slots per slot cycle. The mobile can specify its preferred slot cycle using the SCI. The preferred slot cycle index is a number that a CDMA mobile, in slotted mode, reports every time it originates a call, responds to a page, or registers with the system. It is assigned on a per-mobile basis and may differ from mobile-to-mobile. The slot cycle index used by the subscriber unit is the smaller of the preferred slot cycle index of the mobile and the maximum slot cycle index allowed by the BTS (as communicated in the System Parameters Message). The Paging Channel is divided into 80 ms slots. The slots are grouped into cycles of 2048 slots (163.84 seconds) which are referred to as maximum slot cycles. A mobile station operating in the slotted mode monitors the paging channel using a slot cycle with a length that is a submultiple of the maximum slot cycle length (see Table 7-7). Figure 7-9 shows an example for a slot cycle length of 1.28 seconds and where the mobile stations slot cycle begins with slot 6. The mobile station begins monitoring the paging channel at the start of slot 6. The next slot in which the mobile station must begin monitoring the paging channel is 16 slots later (in other words, slot 22).
7-38
June 2001
The mobile uses a hash function to select the page slot between 0 to 2047. Slotted Mode requires the mobile to monitor a dedicated paging slot within a preferred slot cycle (every 1.28 seconds with an SCI = 0). The mobile is programmed with a preferred slot cycle (the number of cycles between scans of paging channel) using the Slot Cycle Index (SCI) field. This SCI field is stored in the subscriber record. The SCI is assigned on a per mobile basis, therefore multiple SCIs may be in use within a particular system. Access Channel Structure The access channel differs from the paging channel in that all access channel messages are the same size and are referred to as an access channel slot. Each slot is made up of a number of frames. A frame is 20 ms in duration. The number of frames that defines the slot size is equal to 4 + PamSz + MaxCapSz, where the PamSz (Preamble Size) typically is one to two frames and MaxCapSz (Maximum Capsule Size) is three frames. PamSz is directly related to the cell radius of the cell as shown by Table 7-8. Table 7-8: Cell Radius to PamSz (up to 60 km maximum) Motorola Chipset Cell Radius (kilometers) 0.0 3.9 4.0 7.9 8.0 13.9 14.0 18.9 PamSz (frames) 0 1 2 3 . . . continued on next page
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-39
Table 7-8: Cell Radius to PamSz (up to 60 km maximum) Cell Radius (kilometers) 19.0 24.9 25.0 29.9 30.0 33.9 34.0 39.9 40.0 44.9 45.0 50.9 51.0 55.9 56.0 59.9 PamSz (frames) 4 5 6 7 8 9 10 11
A longer preamble is required for mobiles that are farther away from the cell. This gives the base station a better chance of acquiring the mobile message. Events on the access channel are associated with the events that take place on the paging channel:
S Use the access channel for short signaling message exchanges, such
as, call originations, responses to pages, and registrations.
S The access channel is a slotted random access channel. S The access channel data rate is fixed at a rate of 4800 bps. S Each access probe sequence can consist of several probes. If no 7
acknowledgment is received by the subscriber from the BTS, another access probe is transmitted after an additional backoff delay. Each subsequent access probe within the access probe sequence has an increase in power. If a response is not obtained within the access probe sequence, another access probe sequence is transmitted after a time delay and the process continues. Figure 7-10 shows the minimum and maximum number of frames that can exist in one access channel slot.
7-40
June 2001
One Access Channel Slot Access Channel Preamble (Modulation Symbol 0) Access Channel Message Capsule
Access Probe
Access Channel Frame (20 ms) 1 + PamSz (1 to 16 frames) 4 + PamSz + MaxCapSz (8 to 26 frames) 3 + MaxCapSz (3 to 10 frames)
System Time
Actual Access Probe Transmission PN Randomization Delay = RN chips = RN * 0.8138 us
For the access channel, determine the frame size from the size of the preamble and the message capsule. As IS-95 describes, preamble is 1 + PamSz and the message capsule is 3 + MaxCapSz. However, if the MaxCapSz is set to six on the CBSC, then the IS-95 MaxCapSz would be equivalent to three. PamSz is derived from the cell radius parameter. If the converted value of PamSz from the CBSC is two (derived from the cell radius value), then the IS-95 PamSz would be equivalent to one. Table 7-9 describes some of the main events carried on the access channel. Table 7-9: Access Message Type Events BTS MS Access Message Types Mobile Terminated (L to M) Message > < > > General Page (multiple sectors) Page Response Base Station ACK Order Channel Assignment Message . . . continued on next page
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-41
Slots
Table 7-9: Access Message Type Events BTS MS Access Message Types Mobile Originated (M to L) Message < > > Origination Message Base Station ACK Order Channel Assignment Message Registration Message < > > Registration Message Base Station ACK Order Registration Accept Order SMS/ADDS Page Message > < > Data Burst Message (multiple sectors) Mobile Station ACK Order Base Station ACK Order Feature Notification > < > Feature Notification Feature Notification ACK Order Base Station ACK Order Shared Secret Data (SSD) Update 1 1 1 1 Slots
SSD Update Base Station Challenge Order Base Station ACK Order BS Challenge Confirmation Order SSD Update Confirm/Reject Order Base Station ACK Order Unique Challenge 1 1
7-42
June 2001
Paging Channel The limiting factor for the paging channel is channel utilization. This utilization is based upon the total number of halfframes transmitted (to all of the subscribers on a persector/carrier basis) divided by the maximum number of halfframes available for a particular time period of interest. The maximum utilization recommended for the paging channel is 70%. This maximum utilization is an average utilization calculated from data from a 30 minute time period. Access Channel The limiting factor for the access channel is channel utilization. This utilization is based upon the total number of slots transmitted (from all of the subscribers on a persector/carrier basis) divided by the maximum number of slots available for a particular time period of interest. Since the access channel is less efficient than the paging channel (primarily due to blocking and collisions), the maximum utilization recommended for the access channel utilization is 40%. This maximum utilization is an average utilization calculated from data from a 30 minute time period.
June 2001
7-43
Introduction
In order to determine Control Channel utilization, the engineer needs to collect data about how the system is functioning and also determine the present status of the system.
Collect Data
Collect the necessary data to be used for monitoring the control channels. Identifying Data and Traffic Variables To monitor the paging and access channel utilization, use a set of SQL scripts designed to estimate paging and access channel utilization on a per-sector basis from existing Performance Management (pmC) traffic peg counts. The SQL scripts were developed by a SuperCell System Performance group to provide paging and access channel link utilization estimates directly related to measured traffic intensity. These scripts use the Application Processor (AP), SCUNO, or UNO platforms to access the Performance Management peg counts through the Relational Data Base Management System (RDBMS) database. The scripts also apply a software releasedependent set of work load model algorithms to estimate the utilization for individual call processing events. For Motorola Systems Engineers, the releasedependent scripts can be found at the SuperCell System performance groups internal Motorola web page (currently found at the following URL):
http://scwww.cig.mot.com/people/platform/ArchPerf/performance/
Look under the Estimating Device Utilization -- AP SQL Scripts link in the Tools section. For more information on the setup and usage of these scripts refer to the above web page. Service providers can contact their account team Systems Engineer for copies of the SQL scripts and for more information. Starting with Release 15, these scripts will come packaged with the UNO software product. Measurement Intervals Collect data to determine the Daily Busy Period and Busy Day (at least). It is important to collect measurements for all traffic variables that load the paging and access channels and to collect enough time periods throughout the day to ensure subsequent capture of the busy period. The minimum recommendation is to monitor the paging and access channel link utilization on a per-carrier, per-sector basis for each BTS in the system on a monthly basis. Collect busy hour data for the busy day of the month for the CBSC/system being analyzed. For systems which are growing at a rapid rate, or ones that have deployed features which may add significant loading to the paging or access channel (in other words, short messaging service), executing the SQL scripts on a bi-weekly basis for the busy hour, busy day of the week is preferred. If a design change is made to a CBSC/system affecting the paging or access channel performance, execute the SQL scripts for the affected
7-44 CDMA SC Products System Resource Guide (CSSRG) June 2001
area before and after the change. If there are a few sites exhibiting a higher than normal amount of utilization than the rest of the sites in the CBSC/system (or if there are a few sites that are close to or exceeding the maximum recommended paging or access channel utilization limits), determine if the utilization reported is valid. The following are some items to check: S Is there an issue with the system design?
S Is the database for these sites accurate? S Is the SQL script functioning properly?
If the utilization has been validated, the engineer should monitor and trend those higher than normal sites on a weekly basis until a capacity relief mechanism or design change can be implemented. For this situation, it may be necessary to customize the SQL script setup in order to collect the data for just those selected sites of interest. In networks where busy periods are known, collect data to monitor the traffic patterns and, most likely, overload situations. Changes detected in traffic patterns indicate potential for uncharacteristic loading; in this case, a new baseline may need to be established. Paging and Access Channel Monitoring at OMC-R Use the PCH_UTIL SQL script to monitor the utilization of the paging channel (PCH) on a per-carrier, per-sector basis. This SQL script calculates the total utilization percentage for the paging channel. The maximum recommended utilization percentage for the paging channel is 70%. The script also breaks down the total utilization into several different components of individual utilization percentages for certain call model terms. Use these percentages to analyze the contribution of each call model component to the overall utilization of the paging channel. Use the ACC_UTIL SQL script to monitor the utilization of the access channel (ACC) on a per-carrier, per-sector basis. This SQL script calculates the total utilization percentage for the access channel. Since the random access behavior of the access channel causes blocking and collisions to occur, the maximum recommended utilization percentage for the access channel is limited to 40%. Similar to the paging script, this script also breaks down the total utilization into several different components of individual utilization percentages for certain call model terms. NOTE Both of these SQL scripts generate large amounts of data. They create approximately 30 lines of data for each sector of each BTS in the system. As a result of the large output files, it is recommended to post-process the data to condense the output file to a smaller size for easier analysis and storage purposes.
Invoking either script results in output consisting of a series of two-column tables. Each sector under the userspecified CBSC has its
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-45
own table. The first column of each table contains the ACC or PCH utilization call model terms which contribute to the messaging on the ACC or PCH. The second column contains the calculated values of these terms (the utilization values are given as a percentage). The following shows a command line typed by a user and the resulting output with only the one sector s worth of output for both the ACC_UTIL and PCH_Util scripts.
ACC_UTIL 2 5 03/12/99 18:00 < Entered by user omcnum 2 cbscnum 5 date 03/12/99 period 18:00 accs 3 bts 18 sector 2 att 5238.00000000000 moa 114.000000000000 mta 5124.00000000000 cc 200.000000000000 moc 111.000000000000 mtc 89.0000000000000 cf 5038.00000000000 mof 3.00000000000000 mtf 5035.00000000000 reg 263.000000000000 adds_page_ack 193.000000000000 ssd_upd_pch_ack 75.0000000000000 uniq_chlg_pch_ack 85.0000000000000 moc_util 1.11000000000000 mof_util 0.03000000000000 mtc_util 0.89000000000000 mtf_util 0.00000000000000 reg_util 2.63000000000000 adds_page_ack_util 1.93000000000000 upd_pch_ack_util 0.75000000000000 chlg_pch_ack_util 0.85000000000000 total_util 8.19000000000000 PCH_UTIL 2 5 03/12/99 18:00 9600 1,2,3,4 < Entered by user omcnum 2 cbscnum 5 date 03/12/99 period 18:00 baud 9600 carrlist 3 bts 18 sector 2 carrier 3 moc 111 mof 3 mtc 89 page 5124.00000000000 reg 263 mwn_pch 412.000000000000 adds_page 1933.00000000000 7-46 CDMA SC Products System Resource Guide (CSSRG) June 2001
upd_pch upd_pch_ack chlg_pch moc_util mof_util mtc_util page_util reg_util mwn_pch_util adds_page_util upd_pch_util upd_pch_ack_util chlg_pch_util base_util total_util
70.0000000000000 75 86.0000000000000 0.24666666666667 0.00666666666667 0.19777777777778 1.42333333333333 0.58444444444444 0.91555555555556 4.29555555555556 0.15555555555556 0.16666666666667 0.19111111111111 10.16 18.3433333333333
NOTE Depending upon the version of the script, the base_util value may be 17.02 versus the 10.16 shown above. The total_util will be adjusted accordingly. The base utilization calculation in some older versions of the PCH_Util script includes a null General Page message. That null General Page message is only present if there is no useful General Page message. Therefore, it is not considered part of the PCH Overhead (Base) Utilization. These PCH_Util scripts generate a base_util value of 17.02%. This value adds a level a conservatism to the PCH_Util total utilization calculation.
7
Paging Channel Workload Model Events such as page failures, page successes, SMS, etc. have at least one message in the message flow that broadcasts to all BTSs either in the paging area or the CBSC (depending on whether broadcast or location area paging is turned on in the CBSC). The following expression, made up of N different classes of signaling traffic, gives the utilization of the paging channel under various traffic rates and mixes. This equation can be considered as the PCH Workload Model:
[EQ 72]
refers to the Arrival Rate (number of occurrences) for a certain class or grouping of signaling traffic (for example, mobile originations).
7-47
June 2001
Si Overhead
refers to the Resource Demand that Ai places on the paging channel link. refers to any Resource Demand that does not scale as a function of call processing Arrival Rates.
The Arrival Rates are available from the Performance Management (PM) peg counts. Determine the Resource Demands by which messages are present in each of the classes of signaling traffic, their sizes in units of half frames, and the baud rate (refer to Table 7-10). This equation highlights the PCH Workload Model and how it may be used to estimate PCH utilization for any arbitrary traffic rate and mix. The PCH Workload Model is the basis of the PCH_Util script. The following sections highlight what the PCH_Util script does or what is required to do in the absence of the script. Table 7-10 details the messages and message sizes per scenario to determine the resource requirement for each scenario and the PM equation used to determine the Arrival Rate. The Performance Management (PM) report peg counts are given in the form of table#. peg_count# (for example, 10.1 refers to table 10, peg count 1). Refer to the Performance Analysis, SC Product Family - CDMA manual available from Technical Education and Documentation for further information about PM reports. Table 7-10: Paging Channel Workload Model Scenario Scenario Overhead Message Number of Half-Frames (9600 bps) 3 2 3 1 2 2 2 2 2 2 . . . continued on next page
7-48 CDMA SC Products System Resource Guide (CSSRG) June 2001
PM Report Data
S S S S S
System Parameter Msg Access Parameter Msg Neighbor List Msg CDMA Channel List Msg Extended Sys.Parameters Msg Msg
mof
10.1 10.3
Table 7-10: Paging Channel Workload Model Scenario Scenario Message Base Station Ack Order Mobile Terminated Completions Pages Channel Assignment Message General Page Message Base Station Ack Order Registrations Registration Accepted Order Data Burst Message SMS/ADDS Page Feature Notification Shared Secret Data Update Base Station Ack Order Feature Notification Message Base Station Ack Order SSD Update Message Base Station Ack Order BS Challenge Confirm Order Base Station Ack Order Unique Challenge Authentication Challenge Msg Base Station Ack Order 2 215 2 2 2 2 2 2 2 2 2
chlg_pch (52.29 + 52.30) / (# of carriers) *
page reg
10.8 + 10.9 + 10.10 + 10.11 + 10.12 + 10.13 + 10.17 + 10.18 52.20 / (# of carriers)*
52.18 / (# of carriers) *
adds_page
mwn_pch
upd_pch
upd_pch_ack
NOTE
* Assuming no more than one paging area per CBSC, the pmC_52 PM pegs are divided by the number of carriers to get the correct rate per PCH. All the other PM pegs already reflect the rate per PCH since they are gathered at the carrier/sector level. Use the number of messages and the associated number of half-frames required per message to determine the total number of half-frames required. Since the messages are collected for half-hour periods in the PM reports, 180,000 half-frames can occur in a half-hour (360,000 half-frames in an hour). 30 min * 60s * 1000ms min s NumberHalfFramesHalfHour = 10ms HalfFrame
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-49
Determine the impact on paging channel utilization (expressed as a percentage) in a half-hour for each signaling scenario with the following equation. HalfFramesScenario PCHUtili = Ai * 180,000 HalfFramesScenario PCHUtili = Ai * 1800 Where: Ai refers to the Arrival Rate (number of occurrences within a half-hour period) for a certain class or grouping of signaling traffic as shown by the PM Report Data calculation provided in Table 7-10. refers to the number of half-frames each occurrence of Ai requires. [EQ 75] * 100 [EQ 74]
HalfFramesScenario
The total paging channel utilization is the sum of the various call model components described above. (Refer to Table 7-10 for the number of half-frames required for each scenario.)
PCHUtilTotal
moc * (4 / 1800) + [EQ 76] mof * (4 / 1800) + mtc * (4 / 1800) + (page / #_carrier) * (2 / 1800) + reg * (4 / 1800) + (mwn_pch / #_carriers) * (4 / 1800) + (adds_page / #_carriers) * (4a / 1800) + (upd_pch / #_carriers) * (4 / 1800) + upd_pch_ack * (4 / 1800) + (chlg_pch / #_carriers) * (4 / 1800) + Overhead
NOTE The adds_page can vary from 417 half frames. This minimum value of four can be adjusted higher with a measured average value.
Its possible to sum moc, mof, mtc, reg, and upd_pch_ack then multiply by 4/1800 to simplify the calculation for arriving at PCHUtilTotal . However, by doing this, the engineer loses valuable insight into understanding the impact of each of the scenarios on the paging channel. Therefore, calculate the impact on the paging channel for each scenario individually. Then, add the individual components together to obtain the total paging channel utilization. As new features are deployed in the system, new messages could be added to the paging channel. If so,
7-50 CDMA SC Products System Resource Guide (CSSRG) June 2001
arrival rates and resource demands for these new features need to be added to the equation. There are 100 half-frames transmitted per second. If a system experiences a peak of 25 pages per second, the paging channel is 50% utilized just for the general paging messages alone: 25pages/s * 2halfframe/page 100halfframe/s NOTE The PCH_Util script processes data for a given half-hour period. Data could be collected for two half-hour periods comprising the busy hour and then combined in an external process/spreadsheet. Combining the data from the two half-hour periods tends to smooth out the peaks of the data.
* 100 = 50%
Overhead The overhead (base) workload sent over the paging channel (PCH) consists of the Overhead Messages that are sent at least once every 1.28 seconds (1800/1.28 = 1406.25 overhead message groups in a half-hour). Table 7-6 shows the Overhead Messages and the number of half frames associated with each of these messages. Excluding the Null Message, the overhead messages comprise of a total of 13 half-frames. The overhead (Base Paging Channel) utilization resulting from these messages (workload) is calculated as follows:
7
Overhead = 1 1.28 s 1800 s 13 halfframes 1800 = 10.16%
Overhead =
* 100 = 10.16%
Mobile Origination Completions (PCH_Util Script:moc) The contribution of originations to the paging channel load is a factor in the PCH Workload Model. There are two forms of originations to be accounted for:
7
BTS subj_id_1 18 18 18 18 18 18 18 Sector
Table 7-12: pmC_10 Records, Origination Data Carrier subj_id_3 1 2 3 4 1 2 3 Orig Attempt peg_count_1 34 28 26 35 102 83 114 Orig Assign Attempt peg_count_2 34 28 26 35 100 83 113 Orig Assign Complete peg_count_3 33 28 25 34 95 80 111
subj_id_2 1 1 1 1 2 2 2
Table 7-12: pmC_10 Records, Origination Data subj_id_1 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 subj_id_2 2 3 3 3 3 1 1 1 1 2 2 2 2 3 3 3 3 subj_id_3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 NOTE The first half of the data corresponds to the first half-hour (18:00 to 18:30). The second half of the data corresponds to the second half-hour (18:30 to 19:00). peg_count_1 113 85 119 79 101 35 30 28 32 100 82 110 114 84 120 80 102 peg_count_2 113 84 119 79 101 35 30 28 32 101 82 110 114 84 119 80 101 peg_count_3 107 80 116 78 100 34 30 27 30 97 82 110 109 80 117 79 101
From Table 7-12, a paging channel on BTS-18 sector two, carrier three is impacted by 111 origination assignment completions (peg_count_3) in the busy half-hour, or 111 + 110 = 221 in the busy hour. Using Table 7-10, the number of half-frames on the paging channel attributed to origination assignment completions are:
S Two half-frames for the Base Station Ack Order S Two half-frames for the Channel Assignment Message.
Therefore, the number of half-frames required on BTS-18 sector two, carrier three for the half-hour is:
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-53
111 111
* *
2= 2=
The percentage of the paging channel utilized for mobile originated completions is then: (2 + 2) PCHUtilmoc = 111* 1800 Mobile Originated Failures (PCH_Util Script: mof) From Table 7-12, a paging channel on BTS-18 sector two, carrier three is impacted by 114 - 111 = 3 origination failures (peg_count_1 peg_count_3) in this half-hour, which is also the value for the busy hour. Similar to mobile origination completions, this shows that two half-frames are required for the Base Station Ack Order and two half-frames for the Channel Assignment Message. Therefore, the total number of half-frames required for origination failures on BTS-18 sector two,carrier three is 3 * 2 + 3 * 2 = 12 for the half-hour or the hour. The percentage of the paging channel utilized for mobile originated failures is: PCHUtilmof = (2 + 2) 3* 1800 Pages (PCH_Util Script: page) Retrieve the total number of pages (success and failures) from the performance management statistics (pmC_52 and pmC_70 from the OMC-R). The pmC_52 tables record the number of pages handled by the CBSC. The pmC_70 tables record the number of pages handled by each location area defined under that CBSC, if broadcast paging is turned off in the CBSC. Below are examples of portions of the pmC_52 and pmC_70 tables. = 0.007% [EQ 78] = 0.247% [EQ 77]
Table 7-13: pmC_52 Records pmC_52 record_num 52 52 Date record_date 3/12/99 3/12/99 Start Interval Start_of_int 18:00 18:30 End Interval end_of_int 18:30 19:00 OMC OMC_id 2 2 MM MM_id 5 5 Slotted Page peg_count _1 5124 4821 Unslotted Page peg_count _2 0 0
7-54
June 2001
Table 7-14: pmC_70 Records pmC_70 Date Start Interval start_of _int 18:00 18:00 18:00 18:00 18:30 18:30 18:30 18:30 End Interval end_of_i nt 18:30 18:30 18:30 18:30 19:00 19:00 19:00 19:00 OMC MM Location Area Code subj_id_ 1 9 8 7 1 9 8 7 1 Pages Page Acks
record_ num 70 70 70 70 70 70 70 70
record_ date 3/12/99 3/12/99 3/12/99 3/12/99 3/12/99 3/12/99 3/12/99 3/12/99
OMC_id 5 5 5 5 5 5 5 5
MM_id 3 3 3 3 3 3 3 3
NOTE
These tables do not distinguish between original pages, re-pages, or neighbor re-pages. Define broadcast paging in the PAGEPARMS parameter of the CBSC database. If broadcast paging is enabled, information will be found in the pmC_52 tables. If broadcast paging in disabled, information will be found in both the pmC_52 and pmC_70 tables. NOTE The PCH_Util script assumes broadcast paging and therefore collects paging data only from the pmC_52 table.
Assuming broadcast paging, in the above example, each sector of a BTS under OMC-2 MM-5 carries 5,124 pages in the busy half-hour or 5,124 + 4,821 = 9,945 pages in the hour (see Table 7-13). Determine the number of pages each paging channel carries by dividing the number of pages by the number of active paging channels in that sector. Determine which carriers in the sector have paging channels. The number of paging channels on each carrier can be seen in the CHANCONF of the CBSC database. NOTE In the future, it may be possible to put more than one paging channel on a carrier. However, current CBSC releases only supports one paging/access channel per carrier.
June 2001
7-55
For each of these carriers with paging channels, verify that the CHANNELLIST lists the other carriers with paging channels in the sector. This forms the CDMA Channel List message that the mobile uses to determine how many carriers with paging channels are in the sector. If the BTS has a single carrier in the sector with a single paging channel, the paging channel carries 5,124 pages in a half-hour. If the site has four carriers, each with a paging channel, then each paging channel carries 5,124 / 4 = 1,281 pages in the half-hour. Using Table 7-10, the number of half-frames on the paging channel attributed to pages are two half-frames for the General Page Message. Therefore, the total number of half-frames required on BTS-18 sector two, carrier three for the half-hour (assuming broadcast paging) is 1,281 * 2 = 2,562. The percentage of the paging channel utilized for paging is: PCHUtilpage =
5124 4
* 1800
(2) NOTE
= 1.423%
[EQ 79]
The symbol I > means to round up the number to the nearest integer.
For Location Area Paging, determine which paging areas are associated with each BTS. This can be seen in the LOCAREAS record of the database. It lists the location areas associated with each BTS. This table is derived from the SECGEN table of the database. The SECGEN table allows location areas to be defined on the carrier-level, but the software does not currently support using this data. The FEP at the CBSC receives a page from the EMX and strips out the location area information before sending it to the appropriate BTSs. This has two affects: 1. The BTS sends the page to all sectors. If a page for paging area one (PA1) is sent, and the BTS defined sector one as PA1 and sectors two and three as paging area two (PA2), the page is sent to all sectors since there is no location information at this level. 2. The sectors at this BTS are required to handle pages for both PA1 and PA2. Paging Area One (LAC 1) shows 20,508 pages in a half-hour and 20,508 + 20,235 = 40,743 pages in its busy hour which need to be supported by each sector of every cell in this paging area. If a BTS within this paging area has four carriers in a sector and there is a paging channel on each carrier, each paging channel carries approximately 5,127 pages in the half-hour and 10,186 pages in an hour. Mobile Terminated Completions (PCH_Util Script: mtc) The total number of pages has been determined so far. The next step is to determine the number of page responses that occur for mobile terminated
7-56 CDMA SC Products System Resource Guide (CSSRG) June 2001
completed calls in order to calculate the number of Base Acknowledgments (Ack) and Channel Assignment messages required. This information is found in the pmC_10 tables of the Performance Management statistics. Inapplicable columns are not shown for brevity. Table 7-15: pmC_10 Records, General Data pmC_10 record_num 10 10 Date record_date 3/12/99 3/12/99 Start Interval Start_of_int 18:00 18:30 End Interval end_of_int 18:30 19:00 OMC OMC_id 2 2 MM MM_id 5 5
Table 7-16: pmC_10 Records, Termination Data BTS Sector Carrier Term Attempt Slotted peg_count_4 16 20 18 28 62 62 89 90 60 65 60 47 17 22 19 26 Term Attempt Nonslotted peg_count_5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Term Assign Attempt peg_count_6 16 20 18 28 62 59 89 86 59 63 59 47 17 22 19 26 Term Assign Complete peg_count_7 16 20 17 28 60 59 89 85 58 63 59 47 17 22 19 26
subj_id_1 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
subj_id_2 1 1 1 1 2 2 2 2 3 3 3 3 1 1 1 1
subj_id_3 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
Table 7-16: pmC_10 Records, Termination Data subj_id_1 18 18 18 18 18 18 18 18 subj_id_2 2 2 2 2 3 3 3 3 subj_id_3 1 2 3 4 1 2 3 4 peg_count_4 62 61 92 89 60 66 58 50 peg_count_5 0 0 0 0 0 0 0 0 peg_count_6 62 59 91 87 59 64 58 50 peg_count_7 60 59 91 87 58 63 58 50
Using Table 7-16, a paging channel on BTS-18 sector two, carrier three is impacted by 89 completed mobile assignments (peg_count_7) in the busy half-hour or 89 + 91 = 180 (if an hour is analyzed). Using Table 7-10, the number of half-frames on the paging channel attributed to termination assignment completions are the:
S Two half-frames for the Base Station Ack Order S Two half-frames for the Channel Assignment Message.
Therefore, the total number of half-frames required on BTS-18 sector two, carrier three for the half-hour is: Base Station Ack Order: 89 * 2 = 178
356 half-frames The percentage of the paging channel utilized for mobile terminated completions is: (2 + 2) = 0.198% 1800 Registrations (PCH_Util Script: reg) Registration information is also located in the pmC_10 tables of the Performance Management reports. Table 7-17 shows the additional peg counts associated with the registration data. [EQ 710]
PCHUtilmtc = 89*
7-58
June 2001
subj_ id_1
subj_id _2
subj_id_ 3
peg_cou nt_8
peg_co unt_12
18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
1 1 1 1 2 2 2 2 3 3 3 3 1 1 1 1 2 2 2 2 3 3
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2
12 10 15 6 23 31 29 20 11 27 15 34 15 14 13 8 25 33 28 23 14 30
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
43 24 30 43 202 153 234 159 194 147 164 201 44 26 32 42 200 160 240 150 190 137
0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 1 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7
June 2001
7-59
peg_cou nt_8
peg_co unt_9
peg_cou nt_10
peg_cou nt_11
peg_co unt_12
peg_co unt_13
peg_co unt_17
peg_cou nt_18
18 18
3 3
3 4
15 35
0 0
0 0
0 0
159 213
0 0
0 0
0 0
From this table, a paging channel on BTS-18 sector two, carrier three has 29 + 234 = 263 registrations (peg_count_8 + peg_count_9 + peg_count_10 + peg_count_11 + peg_count_12 + peg_count_13 + peg_count_17 + peg_count_18) in the half-hour and 29 + 234 + 28 + 240 = 531 registrations in the hour. Using Table 7-10, the number of half-frames on the paging channel that can be attributed to registrations are the:
S Two half-frames for the Base Station Ack Order S Two half-frames for the Registration Accepted Order.
Therefore, the total number of half-frames required on BTS-18 sector two, carrier three for the half-hour to support the registrations is: Base Station Ack Order: 263 * 2 = 526
Registration Accepted Order: 263 * 2 = 526 1,052 half-frames The percentage of the paging channel utilized for registrations is: PCHUtilreg = 263 * (2 + 2) = 0.584% 1800 [EQ 711]
7
SMS Prior to R9 SMS messages are very similar to pages in that they are broadcast to all BTSs either in the paging area or to all BTS under the CBSC, depending on the configuration of the CBSC paging scheme. Prior to CDMA BSS Release 9, there were no peg counts recorded by the CBSC for the SMS messages. For these systems, the proposed approach to estimating the contribution of SMS to the paging load is to distribute the total number of SMS messages (information from the Message Register) according to the traffic distribution. For example, assume that the total number of SMS messages sent from the Message Register (MR) during the busy hour is 2,500. The distribution of these to the different paging areas is as follows: PS PLA + PB
7-60
June 2001
Where: PS PLA PB SMS SMSL corresponds to pages to the specific location (or CBSC) of interest corresponds to pages to all location areas corresponds to pages to CBSCs with broadcast on corresponds to the total number of SMS messages sent corresponds to SMS messages sent to the specific location of interest.
In the following example, if the paging area containing BTS-18 has 40,743 pages and the sum of all the paging areas is 400,000 pages, this paging area handles 10.19% of the SMS messages, or 255 SMS messages in the busy hour. 40,743 400,000 + 0 * 2,500 255
Since SMS message delivery is similar to page delivery, each sector in the paging area handles up to 255 SMS messages. Since BTS-18 is assumed to be a fourcarrier site (each having a paging channel), 255 SMS messages are divided by four to get 64 SMS messages per carrier. The paging channel for BTS-18 sector two, carrier three handles 64 SMS messages in the busy hour. The number of SMS responses to this carrier also needs to be estimated. If the number of SMS messages is small, the acknowledgments to each sector is also small and is insignificant in the contribution to the overall paging channel load. If the number of SMS messages are substantial, use the same procedure for distributing the SMS responses thats used for the messages. The distribution should use the page acknowledgments to this carrier compared to all page acknowledgments to all carriers as the weighting factor. The worst case assumption is that all SMS messages are received and acknowledged. PAcksS PAcks [EQ 713] * SMS = SMSAcksS
corresponds to page acks received that are associated with the specific paging channel corresponds to page acks to the system corresponds to the total number of SMS messages sent corresponds to SMS messages sent to the specific location of interest.
Assuming that the number of busy hour page acks for BTS-18 sector two, carrier three was 89 + 92 = 181 and the total number of acks for the system was 240,000, then the SMS acks on this paging channel is 1.88. 181 240,000
June 2001
* 2,500 1.88
7-61
Based on this example, the paging channel on BTS-18 sector two, carrier three carries 64 SMS messages and two SMS acknowledgments. The number of half-frames each message uses are 12 and 2 respectively. Therefore, the total number of half-frames required in an hour is 772 (386 for the half-hour). SMS SMS Acks 64 2 * * 12 = 2= 768 4 772 half-frames in an hour (386 half-frames in a half-hour) The percentage of the paging channel utilized for SMS in a half-hour is: PCHUtilSMS =
255 4
[EQ 714]
PCHUtilSMSAcks =
8 4
[EQ 715]
NOTE The symbol I > means to round up the number to the nearest integer.
Starting with CDMA BSS Release 9, the Short Message Service (SMS) feature is now considered part of an Application Data Delivery Service (ADDS) feature. In addition to delivering data on the paging channel (similar to the SMS feature), this feature also allows data delivery to occur on the traffic channel. As far as the paging channel is concerned, the ADDS Page messages can be considered the same as SMS messages and are the only ADDS messages which impact the paging channel. The ADDS Page information is located in the pmC_52 tables of the Performance Management reports. Table 7-18 shows the peg count associated with the ADDS Page feature. Table 7-18: pmC_52 Record for ADDS Page pmC_52 record_num 52 52
7-62
OMC OMC_id 2 2
MM MM_id 5 5
The ADDS Page is very similar to normal pages, where the information in the Pages section would apply to this section as well. Therefore, the information on broadcast paging and location area paging in the Pages section also applies here and therefore will not be repeated. The ADDS Page message can vary from 215 half frames. There is also two half frames sent on the paging channel for the base station acknowledgement. Therefore the total range is 417 half frames. The PCH_Util script uses the minimum value of four half frames. Using Table 7-18 (assuming broadcast paging), a paging channel on BTS18 sector two, carrier three for the halfhour is impacted by 7730 / 4 = 1933 ADDS Page messages (assuming a four carrier system). Therefore, the percentage of the paging channel utilized for ADDS pages is: PCHUtiladds_page =
7730 4
(2 + 2) 1800 NOTE
= 4.296%
[EQ 716]
The symbol I > means to round up the number to the nearest integer.
If a measured average value of half frames sent for a particular system is known, then the minimum value that the PCH_Util script uses can be adjusted to the meassured value. For example, if the measured average value of half frames sent is seven half frames, the following calculation can be made instead. PCHUtiladds_page =
7730 4
(7 + 2) 1800 NOTE
= 9.665%
[EQ 717]
The symbol I > means to round up the number to the nearest integer.
Message Waiting Notification Feature Motorola offers a method of voice mail notification called Message Retrieval Service, which only works within a Distributed Mobile Exchange (DMX) network. Starting with CDMA BSS Release 9, the Message Waiting Notification (MWN) feature is available, which provides a voice mail notification method that will work for IS41 networks. The MWN messages can be delivered to the subscribers on the traffic channel or paging channel. For traffic channel delivery, a Flash with Information message is delivered to the subscriber. For paging
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-63
channel delivery, a Feature Notification message is delivered to the subscriber. For a control channel analysis, the Feature Notification delivery method is the only one that needs to be considered. Feature Notification (PCH_UTIL Script: mwn_pch) Feature Notification information is located in the pmC_52 tables of the Performance Management reports. Table 7-19 shows the additional peg counts associated with the Feature Notification messages. Table 7-19: pmC_52 Record for Feature Notification pmC_52 record_num 52 52 Date record_date 3/12/99 3/12/99 Start Interval start_of_int 18:00 18:30 End Interval end_of_int 18:30 19:00 OMC OMC_id 2 2 MM MM_id 5 5 Feature Notification peg_count_18 1648 1579
Referring back to Table 710, the Feature Notification and Base Station Ack messages each require two half frames for a total of four half frames. Using Table 7-19 (assuming broadcast paging), a paging channel on BTS18 sector two, carrier three for the halfhour is impacted by 1648 / 4 = 412 Feature Notification messages (assuming a four carrier system). Therefore, the percentage of the paging channel utilized for Feature Notification is: PCHUtilmwn_pch =
1648 4
(2 + 2) 1800 NOTE
= 0.916%
[EQ 718]
The symbol I > means to round up the number to the nearest integer.
Authentication Feature The Authentication Feature provides fraud protection to system operators. Authentication provides the ability to perform both Unique Challenge and Shared Secret Data (SSD) Update operations on the CDMA traffic or control channels. Starting with CDMA BSS Release 9, new peg counts are provided to monitor the Authentication Feature messaging on the control channels. There are two groups of Authentication messaging that impact the paging channel:
Shared Secret Data Update (PCH_UTIL Script: upd_pch, upd_pch_ack) There are two parts to an SSD update activity: 1. SSD Update Request (PCH_UTIL Script: upd_pch) 2. Base Station Challenge Response (PCH_UTIL Script: upd_pch_ack). For the first part, the SSD Update Request information is located in the pmC_52 tables of the Performance Management reports. Table 7-20 shows the additional peg counts associated with the SSD Update messages. Table 7-20: pmC_52 Records for Shared Secret Data Update
pmC_52 Date Start Interval End Interval OMC MM Slotted SSD Update Request
record_num
record_date
start_of_int
end_of_int
OMC_id
MM_id
peg_count_ 27
52 52
3/12/99 3/12/99
18:00 18:30
18:30 19:00
2 2
5 5
280 257
Referring back to Table 710, the SSD Update and Base Station Ack messages each require two half frames for a total of four half frames. Using Table 7-20 (assuming broadcast paging), a paging channel on BTS18 sector two, carrier three for the halfhour is impacted by (280 + 0) / 4 = 70 SSD Update messages (assuming a four carrier system). Therefore, the percentage of the paging channel utilized for SSD Update is: PCHUtilupd_pch =
280 + 0 4
(2 + 2) 1800
= 0.156%
[EQ 719]
NOTE The symbol I > means to round up the number to the nearest integer.
For the second part of an SSD Update activity, the Base Station Challenge Response information is located in the pmC_20 tables of the Performance Management reports. The pmC_20 report provides a break down of the data on a percarrier basis. Table 7-21 shows the additional peg count associated with the Base Station Challenge message (the SSD Update Ack peg count is used to track the number of Base Station Challenges).
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-65
record_num
record_date
OMC_id
MM_id
subj_id_1
subj_id_2
subj_id_ 4
20 20
3/12/99 3/12/99
18:00 18:30
18:30 19:00
2 2
5 5
18 18
2 2
3 3
Referring back to Table 710, the Base Station Challenge and Base Station Ack messages each require two half frames for a total of four half frames. Using Table 7-21, a paging channel on BTS18 sector two, carrier three for the halfhour is impacted by 75 SSD Update Ack messages. Therefore, the percentage of the paging channel utilized for Base Station Challenges is: PCHUtilupd_pch_ack = 75 * (2 + 2) = 0.167% 1800 Unique Challenge (PCH_UTIL Script: chlg_pch) The Unique Challenge information is located in the pmC_52 tables of the Performance Management reports. Table 7-22 shows the additional peg counts associated with the Unique Challenge messages. Table 7-22: pmC_52 Records for Unique Challenge
pmC_52 Date Start Interval End Interval OMC MM Slotted Authen tication Request [EQ 720]
7
record_num record_date start_of_int end_of_int OMC_id MM_id peg_count_ 27
52 52
3/12/99 3/12/99
18:00 18:30
18:30 19:00
2 2
5 5
344 329
Referring back to Table 710, the Unique Challenge and Base Station Ack messages each require two half frames for a total of four half frames. Using Table 7-22 (assuming broadcast paging), a paging channel on BTS18 sector two, carrier three for the halfhour is impacted by (344 + 0) / 4 = 86 Unique Challenge messages (assuming a four carrier system). Therefore, the percentage of the paging channel utilized for Unique Challenge is: PCHUtilchlg_pch =
344 + 0 *
4
(2 + 2) = 0.191% 1800
[EQ 721]
7-66
June 2001
Total Paging Channel Utilization The total paging channel utilization is the sum of the various call model components described above, as illustrated in Table 7-23. Table 7-23: Paging Channel Utilization A Scenario Halfframes per Scenario 13 4 4 2 4 4 9* 4 4 4 B Msgs per Scenario (halfhour) 1,800/1.28 111 3 5,124 89 263 7,730 1,648 280 75 C Carriers D Half-frames Required (Half-hour) 18,282 444 12 2,562 356 1,052 17,397 1,648 280 300 E PCH Utilized
Overhead Origination Completions (moc) Origination Failures (mof) Pages Termination Completions (mtc) Registrations (reg) SMS/ADDS Page (adds_page) Feature Notification (mwn_pch) SSD Update (upd_pch) Base Station Challenge (upd_pch_ack) Unique Challenge (chlg_pch) Total
4 4 4 4
10.16% 0.25% 0.01% 1.42% 0.20% 0.58% 9.67% 0.92% 0.16% 0.17%
344
344 42,677
0.19% 23.71%
NOTE
* An adjusted value of seven half frames for data plus two for the ack is used.
June 2001
7-67
Where: D = A * (B / C) [If there is no carrier listed in column C, C can be removed from the equation.] [(A / 180,000) * (B / C)] * 100 (D / 180,000) * 100 NOTE The Carriers column corresponds to the number of paging channels. Assume that each carrier has one paging channel. In a future release, it may be possible to have more than one paging channel per carrier. The maximum recommended aggregate utilization percentage for the paging channel is 70%.
= =
The Access Channel (ACC) Workload Model is the basis of the ACC_Util script. The following sections highlight what actions the script performs and what the engineer is required to do in the absence of the script. Calculate the number of access channel slots occurring in a specified time duration to determine access channel utilization. Determine the number of slots occurring in a half-hour interval from the following relationship: 30 min * 60s * 1000ms min s NumberSlotsHalfHour = [(1 + PamSz) + (3+ MaxCapSz)] frames slot * 20ms frame [EQ 722]
The previous equations shows that the size of each slot, in terms of frames, is dependent on the cell radius of the cell (PamSz is a function of the cell radius) where the access channel is located. For example, a cell radius of 13 km has a PamSz of two frames (see Table 7-8 ). If the MaxCapSz is set at three, the slot size is 9 frames (180 ms). The number of slots occurring in a half-hour duration, in this case, is 10,000 (20,000 slots in an hour). Using Equation [EQ 722], the total number of access channel slots per hour and per halfhour for the full range of PamSz frames is shown in Table 7-24 (assuming MaxCapSz is set to the default level of three).
7-68 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 7-24: Access Channel Slots per Hour/Halfhour versus PamSz Slots per Hour 25,714 22,500 20,000 18,000 16,363 15,000 13,846 12,857 12,000 11,250 10588 10,000 Slots per half hour 12,857 11,250 10,000 9,000 8,181 7,500 6,923 6,428 6,000 5,625 5,294 5,000 PamSz (frames) 0 1 2 3 4 5 6 7 8 9 10 11
NOTE
MaxCapSz = 3 The ACC_Util script assumes the sum of (1 + PamSz + 3 + MaxCapSz) is 12. The number of slots occurring in a half-hour, based on this assumption, is 7,500. If MaxCapSz is set to 6 in the CBSC, the IS-95 MaxCapSz is equivalent to three. Display MaxCapSz from the CBSC with one of the following commands:
display carrierbts#sector#carrier# pachgen display sectorbts#sector# pachgen display btsbts# pachgen
The value displayed from the CBSC would be substituted for the 3 + MaxCapSz sum shown in Equation 722. PamSz is derived from the cell radius parameter. If the displayed value of the cell radius from the CBSC results in a PamSz of two, then the IS-95 PamSz would be equivalent to 1. The cell radius can be displayed from the CBSC with one of the following commands:
display carrierbts#sector#carrier# secgen display sectorbts#sector# secgen display btsbts# secgen
From the cell radius, determine the PamSz by using the conversion provided in Table 7-8. This converted value is substituted for the 1 + PamSz sum shown in Equation [EQ 722].
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-69
A particular mobile may send a probe sent at the same time another mobile sends its probe. In this case, the base station decodes: 1. One of the probes 2. Neither of these probes. These phenomena are classified as blocking and collisions, respectively. If all mobiles were perfectly synchronized and could schedule each other s access attempts, the total number of accesses the base station could process would be 10,000 messages (with PamSz = 2 and MaxCapSz = 3) in a half-hour. Since blocking and collisions occur, this limit is a theoretical upper bound that will never be reached. Traffic load is the actual number of messages (probes) sent to the cell and throughput is the number of messages the cell decodes. For example, the results of a study show that a traffic load of 0.3 msg/slot yields a throughput of 0.2 msg/slot. NOTE As the traffic load increases, the throughput peaks at a point and then begins to decrease. This is because of the increased occurrences of collisions. The peak is generally between 0.4 and 0.5 msg/slot in throughput.
The messages occurring on the access channel can be obtained from Performance Management records. These messages are the throughput messages. The basic calculation for determining the utilization is to sum all of the different access messages occurring in a specified time period (half-hour or one-hour period) and compare it to the theoretical upper bound:
7
ACCUtil =
[EQ 723]
In the previous example, 10,000 slots occurred in a half-hour period (with PamSz = 2 and MaxCapSz = 3). If one msg/slot is considered 100% utilized, the engineer expects the peak throughput to occur when the utilization, as calculated above, reaches 40% to 50%. The ACC_Util script assumes the number of slots in a half-hour to be 7,500. So, if the sum of the PamSz and MaxCapSz parameters (as obtained from the CBSC) is less than 12 for a cell, the ACC_Util script will overestimate the access channel utilization. Each individual event needs to be addressed to formulate the ACC Workload Model. This is illustrated in Table 7-25.
7-70 CDMA SC Products System Resource Guide (CSSRG) June 2001
Table 7-25: Access Channel Workload Model Scenarios Scenario Mobile Originated Completions Mobile Originated Failures Mobile Terminated Completions Registrations Message Origination Message Origination Message Page Response Registration Message ACC_Util Script Name moc mof mtc reg PM Report Data 10.3 10.1 10.3 10.7 10.8 + 10.9 + 10.10 + 10.11 + 10.12 + 10.13 + 10.17 + 10.18 10.19 20.14 20.15 N/A*
Mobile Station Ack Order SSD Update Conf/Rej Order Authentication Challenge Feature Notification Ack
NOTE
* There is currently no peg counts available to track the Feature Notification acknowledgements. Originations (ACC_Util Script: moc and mof) As with the originations on the paging channel, the two origination scenarios that impact the access channel are: S Mobile origination completions (peg_count_3) S Mobile origination failures (peg_count_1 - peg_count_3). Obtain the number of mobile origination completions and origination failures quantities from the pmC_10 table for each carrier (refer to Table 7-12). The number of messages is the same as required for the paging channel calculation. For this portion of the ACC workload, the number of origination completion messages that BTS-18 sector two, carrier three received is 111 for the half-hour. In addition, there are 114 - 111 = 3 origination failures. The percentage of the access channel utilized for originations is: ACCUtilmoc = 111 10000 3 10000 * 100 = 0.03% * 100 = 1.11% [EQ 725] [EQ 724]
ACCUtilmof =
Terminations (ACC_Util Script: mtc) The number of termination messages impacting the ACC workload is the same as the number of mobile terminated completions on the PCH. The
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-71
number of page response messages for mobileterminated completions can be obtained from peg_count_7 of the pmC_10 table for each carrier (refer to Table 7-16). For this portion of the ACC workload, the number of page response messages received by BTS-18 sector two, carrier three received is 89 for the half-hour (refer to the Pages (PCHUtil Script:page section). The percentage of the access channel utilized for terminations is: ACCUtilmtc = 89 10000 * 100 = 0.89% [EQ 726]
Registration (ACC_Util Script: reg) The number of registrations messages impacting the ACC and the PCH are the same. Obtain the number of registration messages from peg_count_8 + peg_count_9 + peg_count_10 + peg_count_11 + peg_count_12 + peg_count_13 + peg_count_17 + peg_count_18 of the pmC_10 table for each carrier. A paging channel on BTS-18 sector two, carrier three has 263 (29 + 234) registration messages in the half-hour. The percentage of the access channel utilized for registrations is: ACCUtilreg = 263 10000 * 100 = 2.63% [EQ 727]
SMS Prior to R9
Calculations from the paging channel on SMS are used again for the access channel. Refer to Equation [EQ 713] . The number of page acks for BTS-18 sector two, carrier three in the busy hour was 181 (89 + 92). If the total number of acks for the system was 240,000 acks, the SMS acks at this paging channel is 1.88 responses (181/240,000 * 2500) in an hour or 0.94 responses in a half-hour. The percentage of the access channel used for SMS is: ACCUtilSMS = 1 10000 * 100 = 0.01% [EQ 728]
SMS/ADDS Page Post R9 (ACC_Util Script: adds_page_ack) The number of SMS or ADDS Page Response messages impacting the ACC workload is obtained from peg_count_19 from the pmC_10 table for each carrier (refer to Table 7-26).
7-72 CDMA SC Products System Resource Guide (CSSRG) June 2001
record_num
record_date
OMC_id
MM_id
subj_id_1
subj_id_2
subj_id_ 3
10 10
3/12/99 3/12/99
18:00 18:30
18:30 19:00
2 2
5 5
18 18
2 2
3 3
For this portion of the ACC workload, the number of ADDS Page Response messages received by BTS18 sector two, carrier three received is 193 for the halfhour. The percentage of the access channel utilized for ADDS Page Responses is: ACCUtiladds_page_ack = 193 10000 Base Station Challenge (ACC_Util Script: upd_pch_ack) The number of SSD Update Order messages impacting the ACC workload is the same as the number of SSD Update Ack (upd_pch_ack) messages impacting the PCH. The number of SSD Update Ack messages is obtained from peg_count_14 from the pmC_20 table for each carrier (refer to Table 7-21). For this portion of the ACC workload, the number of SSD Update Order messages received by BTS18, sector two, carrier three received is 75 for the halfhour. The percentage of the access channel utilized for SSD Update Orders is: ACCUtilupd_pch_ack = 75 10000 Unique Challenge (ACC_Util Script: chlg_page_ack) The number of Authentication Challenge Response messages from Unique Challenges, which impact the ACC workload is obtained from peg_count_15 from the pmC_20 table for each carrier (refer to Table 7-27). Table 7-27: pmC_20 Records for Authentication Acknowledgements
pmC_20 record_num Date record_date Start Interval start_of_int End Interval end_of_int OMC OMC_id MM MM_id BTS Id subj_id_1 Sector Id subj_id_2 Carrier Authen. Acks peg_count_ 15 85 83
* 100 = 1.93%
[EQ 729]
* 100 = 0.75%
[EQ 730]
subj_id_ 4
20 20
3/12/99 3/12/99
18:00 18:30
18:30 19:00
2 2
5 5
18 18
2 2
3 3
June 2001
7-73
For this portion of the ACC workload, the number of Authentication Challenge Response messages received by BTS18, sector two, carrier three received is 85 for the halfhour. The percentage of the access channel utilized for Authentication Challenge Responses is: ACCUtilchlg_page_ack = 85 10000 * 100 = 0.85%
[EQ 731]
Feature Notification There is currently no peg counts available to track the Feature Notification acknowledgements for the access channel. As a result, the ACC_Util script cannot estimate the access channel utilization for this type of load. An evaluation of the amount of Feature Notification messages (pmC_52, peg_count_18) on the paging channel is needed to determine if this load should be considered. If the load appears to be significant, then the current approach is to distribute the total number of Feature Notification messages according to the measured traffic distribution of page acknowledgements (similar to the approach performed for the SMS messages prior to CDMA BSS Release 9, refer to the SMS Prior to R9 section for the Paging channel). Total Access Channel Utilization Summing all of the access channel messages results in 467 messages in the half-hour. Table 7-28 shows the various scenarios and their impact upon access channel utilization. Table 7-28: Access Channel Utilization Scenario Msgs per Scenario (half-hour) 111 3 89 263 193 75 85 Number of Access Channels ACC Utilized 1.11% 0.03% 0.89% 2.63% 1.93% 0.75% 0.85% . . . continued on next page
7-74 CDMA SC Products System Resource Guide (CSSRG) June 2001
Origination Completions (moc) Origination Failures (mof) Termination Completions (mtc) Registrations (reg) SMS/ADDS Page (adds_page_ack) Base Station Challenge (upd_pch_ack) Unique Challenge (chlg_pch_ack)
Table 7-28: Access Channel Utilization Scenario Feature Notification Total Msgs per Scenario (half-hour) 819 This example assumes: PamSz = 2 MaxCapSz = 3 Then: From Equation [EQ 722], From Equation [EQ 723] NOTE Assume each carrier has one access channel. In a future release, it may be possible to have more than one access channel per carrier. Typically, the largest contributor to the utilization of the access channel involves registrations. Access channels with a utilization of 40% are considered to be at the maximum level. NumberSlotsHalfHour = 10,000 AccUtil = AccMsgs/100 Number of Access Channels ACC Utilized 8.19%
Paging and Access Channel Monitoring at MSC Paging Load Indicator (PLI) is a purchasable feature on the EMX2500/5000. It allows the operator to evaluate the performance of the paging facility by gathering statistics on the number of different types of pages and page acknowledgments. The Report EMX Page MMI command is as follows:
REPORT EMX PAGE (Requires the PLI feature)
This MMI enables the operator to obtain an online display of the EMX PLI statistics. The PLI statistics included under this MMI are:
S S S S S S S S
June 2001
Originating Page Attempts Non-Originating Page Attempts Page Acks Repage Acks Late Page Acks CCS Pages and Repages CCS Page and Repage Acks Search Requests
7-75
If the paging load indicator feature has not been purchased, the output displays the following data according to paging area:
S S S S S S S S S S S S S S S S
Determine Present Status
LKA Pages LKA Repages LKA Page Acks LKA Repage Acks CCS Pages CCS Repages CCS Page Acks CCS Repage Acks Two Word Pages Neighbor Pages Neighbor Repages Neighbor Page Acks Neighbor Repage Acks Unsolicited Page Acks Unsolicited Page Acks - No Neighbor Unsolicited Page Acks - Successful and High Water Mark of pages.
For each time measurement period, record data points comparing the paging and access channel utilization versus call model parameters. If using a spreadsheet, create a column for each call model scenario and the calculated utilization. The rows represent the set of values for each measurement period of a given BTS-sector-carrier. In determining the present status, validate data to ensure its integrity. Investigate partial data or anomalous data and eliminate it from the analysis. Remove any data that represents an abnormal traffic period not considered part of the normal traffic environment. The next item to consider is establishing the control channel utilization planning and maximum limits (see the following section on Planning Limits). Use these limits to define category regions to represent a
7-76 CDMA SC Products System Resource Guide (CSSRG) June 2001
stoplight level of urgency. The green region represents a low-level of urgency, where the control channel utilization ranges from a low level up to the planning limit. The yellow region represents a moderate-level of urgency with the control channel utilization, ranging from the planning limit to the maximum limit. Finally, the red region represents a high-level of urgency with the control channel utilization being greater than the maximum limit. Apply these category regions to the Bouncing Day Bouncing Busy Hour (BDBBH) utilization data and analyze it on a weekly basis. Monitoring the control channel utilization data in this fashion can simplify the notification of potential problem areas. After the data has been validated, analyze the four week average of BDBBH data for each sector (on a per-carrier basis for systems with multiple carriers) to identify any sectors exceeding any of the control channel planning or maximum limits. If one or more sectors exceed the control channel planning or maximum limits, monitor the BBH performance statistics trend for those cells/sectors to determine if there is an increase in performance degradation occurring as a result of elevated BBH control channel usage. It is at this point where an evaluation review of the planning and maximum limits may be necessary. The review determines if adjustments need to be made to either of these limits to better reflect the desired performance, capacity, or service provider desired results. Regardless of the performance statistics results, investigate options for those cells/sectors exceeding the limits and determine if a control channel management plan is required. The objective of control channel management planning is to implement relief mechanisms before a performance degradation actually occurs. Therefore, the existence of performance degradation should not be a prerequisite for determining or implementing an control channel management plan. Use the existence of performance degradation to increase the priority of implementing the relief options to those cells/sectors exhibiting the performance degradation. If the analysis of the present status contains several sites/sectors which exceed the maximum limit but do not reflect any performance degradation, those sites should be next on the priority list for implementing relief options. Choosing the appropriate relief plan, with respect to a BTS sector-carrier level, depends upon many different factors. Some factors include: S Service provider inputs and requests S Cost of implementation S Market size S Terrain S The design of the system S Rate of market growth S The number and location of the sites/sectors which exceed the planning or maximum limit. It is up to the system designer to effectively choose control channel management options to create a relief plan that best fits the particular situation.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-77
Introduction
Control Channel Planning Limits are determined by evaluating several limits, identifying any bottlenecks, and then applying the remedies that alleviate those bottlenecks. This topic describes the limits, bottlenecks, and remedies that the engineer can expect to encounter.
Planning Limit Recommendations
A paging channel utilization of 70% is considered to be a typical maximum level with 55% representing the planning limit (equivalent to approximately 80% of maximum level). A typical maximum access channel utilization is 40% with 30% representing the access channel utilization planning limit.
Forecast Utilization
There are several different strategies used to forecast control channel utilization. Each of them has different merits. The marketing departments of cellular operators typically project future growth through subscriber projections. Use these projections as the baseline parameter to gauge future system utilization. Ultimately, for control channel planning, a forecasted number of messages is required. This is the number of messages to be transmitted over the control channels on a per-cell/sector/carrier basis. If the service provider s marketing department provides the Systems Engineer with subscriber projections, the following procedure can be used to forecast control channel utilization on a per-cell/sector/carrier basis. To forecast the paging and access channel utilization, the engineer should not sum all of the messages together to generate one total utilization value for each sector-carrier. If such summing is done, the engineer loses the insight as to which component has the most impact upon utilization. In performing any relief measures, focus on the scenario with the best chance of relieving the situation. Another purpose of keeping the items separate is to determine the impact of making a change to a system parameter. For instance, consider a situation where registrations occur every hour. What is the impact if registrations are made every fifteen minutes instead? In the later case, the engineer inflates the hour registration data four times over the former case and then determines its impact upon the total paging channel utilization. With this in mind, a spreadsheet can be created to keep track of the information and to also aid in a forecast for the future. Collect the following data:
S BTS id, Sector, Carrier S Number of Mobile Originated Completions (pmC10 peg count 3) S Number of Mobile Originated Failures (difference of pmC10 peg
count 1 and 3)
7-78 CDMA SC Products System Resource Guide (CSSRG) June 2001
S Number of SMS/ADDS Page Messages (pmC52 peg count 20) S Number of Feature Notification Messages (pmC52 peg count 18) S Number of SSD Update Messages (the sum of pmC52 peg counts 27
and 28)
S Number of BS Challenge Confirm Orders (pmC20 peg count 14) S Number of Authentication Challenge Messages (the sum of pmC52
peg counts 29 and 30)
S Number of ADDS Page Mobile Station Ack Orders (pmC10 peg count
19)
S S S S S S S S S S S S S S S S S S S S
Paging channel utilization for mobile originated completions Paging channel utilization for mobile originated failures Paging channel utilization for mobile terminated completions Paging channel utilization for pages Paging channel utilization for registrations Paging channel utilization for SMS/ADDS Pages Paging channel utilization for Feature Notifications Paging channel utilization for SSD Updates Paging channel utilization for Base Station Challenges Paging channel utilization for Unique Challenges Total paging channel utilization Access channel utilization for mobile originated completions Access channel utilization for mobile originated failures Access channel utilization for mobile terminated completions Access channel utilization for registrations Access channel utilization for SMS/ADDS Pages Access channel utilization for Base Station Challenges Access channel utilization for Unique Challenges Access channel utilization for Feature Notifications (if significant) Total access channel utilization.
To project an increase to the level of paging or access channel utilization due to an increase in the number of subscribers, scale the data (except the amount due to the paging channel overhead) by the ratio of projected subs for the system to the current subs for the system:
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-79
GrowthFactor(GF) =
ProjectedSubs CurrentSubs
If subscriber growth estimates are provided on a monthly basis, repeat the calculations for each month where a subscriber growth estimate is provided. Using a monthly analysis, perform an estimate of when a particular cell or sector will exceed the planning or maximum limit. To understand how the simple growth of the subscriber base affects the paging channel, each of the events, listed in Table 7-23, (except overhead messaging) needs to be scaled up, as shown in Table 7-29. Table 7-29: Projected Paging Channel Utilization A Scenario Overhead Origination Completions (moc) Origination Failures (mof) Pages Termination Completions (mtc) Registrations (reg) SMS/ADDS Page (adds_page) Feature Notification (mwn_pch) Halfframes per Scenario 13 4 4 2 4 4 9 4 B Msgs per Scenario (halfhour) 1800/1.28 111 3 5,124 89 263 7,730 1,648 C Growth Factor of 1.67 1800/1.28 186 5 8,557 149 439 12,909 2,752
a
D Carriers
E Half-frames Required (Half-hour) 18,282 744 20 4,280 596 1,756 29,052 2,752
F PCH Utilized 10.16% 0.41% 0.01% 2.38% 0.33% 0.98% 16.14% 1.53%
4 4 4
Table 7-29: Projected Paging Channel Utilization Scenario SSD Update (upd_pch) Base Station Challenge (upd_pch_ack) Unique Challenge (chlg_pch) Total Halfframes per Scenario 4 4 Msgs per Scenario (halfhour) 280 75 Growth Factor of 1.67 468 125 Carriers Half-frames Required (Half-hour) 468 500 PCH Utilized 0.26% 0.28%
344
574
574 59,024
0.32% 32.79%
NOTE
a. The amount of overhead messages does not change due to an increase in the number of subscribers. Where: C = E = F = =
For a quick calculation for the total paging channel utilization, the engineer can scale the paging channel utilization directly and not scale the number of half-frames. The paging channel utilization for the overhead messages (10.16%) is not to be increased though. Use the following equation to project a new total paging channel utilization based on a projected subscriber growth: (CurrentUtilizationOverhead) * ProjectedSubs CurrentSubs [EQ 734] + Overhead = ProjectedUtilization
To understand how the simple growth of the subscriber base affects the access channel, each of the events, listed in Table 7-28, needs to be scaled up (as shown in Table 7-30).
June 2001
7-81
Table 7-30: Projected Access Channel Utilization A Scenario Origination Completions (moc) Origination Failures (mof) Termination Completions (mtc) Registrations (reg) SMS/ADDS Page (adds_page_ack) Base Station Challenge (upd_pch_ack) Unique Challenge (chlg_pch) Feature Notification Total Msgs per Scenario (half-hour) 111 3 89 263 193 75 B Growth Factor of 1.67 186 5 149 439 322 125 C Number of Access Channels D ACC Utilized
85 819
142 1,368 This example assumes: PamSz = 2 = 3 MaxCapSz Then: From Equation [EQ 722]: From Equation [EQ 723]:
1.42% 13.68%
10,000
AccUtil = AccMsgs/100
NOTE Assume each carrier has one access channel. In a future release, it may be possible to have more than one access channel per carrier.
For a quick calculation for the total access channel utilization, the engineer can scale the access channel utilization directly and not scale the number of messages. Use the following equation to project a new
7-82 CDMA SC Products System Resource Guide (CSSRG) June 2001
total access channel utilization based on a projected subscriber growth: (CurrentUtilization) * ProjectedSubs CurrentSubs [EQ 735] = ProjectedUtilization
For the messages per scenario used for the paging and access channel utilization calculations, use a four week average of the Busy Day Bouncing Busy Hour (BDBBH) data for each sector/carrier. From this data, calculate the standard deviation (onesigma) for this four week average. Using the onesigma result, calculate an average plus threesigma value for the messages per scenario data. The growth factor is then applied to both an average value and a threesigma average value. The desired result is to forecast an average utilization and a threesigma average utilization based upon the BDBBH data. Use a graph showing the estimated utilization versus the growth of traffic for the average and upper threesigma curve, including the baseline traffic values and the maximum specified limit, as a visual aid to identify when the paging and access channels will run out of capacity. If the service provider s marketing department provides the Systems Engineer with something other than subscriber projections, make modifications to the above approach to project a linear relationship according to the service providersupplied projection parameter. If the service provider requires a non-linear growth projection, modifications to the above approach are dependent upon the specified non-linear growth projection requirements. For example, the service provider may specify a variable subscriber growth rate along with a change to how often registrations occur. In either case, the desired outcome is to project an average BDBBH paging and access channel utilization and a three-sigma average BDBBH paging and access channel utilization for each cell/sector on a per-carrier basis. Make adjustments to the forecasting utilization process when judged appropriate. For instance, if a larger statistical data sample is desired, more than four BBH data points can be used for the calculation of the monthly average and the standard deviation. Using additional data captured during less busy days of the week reduces the overall average and provides a less conservative prediction. Also, use a different multiplication factor other than three for the standard deviation multiplier. Using a lower multiplier (X) for the X-sigma average calculation also provides a less conservative prediction. Make several adjustments to the above process, depending upon the level of conservatism desired. It is not only the increase in the number of subscribers that can have an impact upon the paging and access channel utilization. Various changes to the system can impact the number of messages carried by the paging and access channels. The following examples of changes to the system require the engineer to consider the impact to the control channels:
S Addition of a CBSC (if each CBSC has its own paging zone) S Addition of a carrier
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-83
Reparenting a cell from one CBSC to a different CBSC Change in when registrations occur Change to where pages are sent and if repages are sent Change to SMS that impacts the number of messages sent or length of message
Once the ACH and PCH utilization has been forecasted on a per-cell/sector, per-carrier basis, it is time to again identify (on a BTS-level) any sectors exceeding either of the control channel planning or maximum limits. Establish the planning limit and the maximum limit into category regions which represent a stoplight level of urgency. Apply this to the forecasted control channel utilization data (for both average and three-sigma values) and analyze it. The green region represents a low-level of urgency, with the control channel utilization ranging from low utilization up to the planning limit. The yellow region represents a moderate-level of urgency, with the control channel utilization ranging from the planning limit to the maximum limit. Finally, the red region represents a high-level of urgency, with the control channel utilization being greater than the maximum limit. The recommendation is to plan on implementing a control channel capacity relief mechanism before it is projected to reach the planning limit using the average utilization projection or the maximum limit using the threesigma average utilization projection (whichever one is projected to occur first).
7-84
June 2001
Introduction
As a cell site approaches its maximum paging or access channel capacity limit, the primary symptom of resource overload is a degradation in access performance. There are two sources of data where access failure performance can be measured:
S Performance Management (PM) peg counts S Call Failure Class (CFC) peg counts from Call Detail Logs (CDLs).
Ideally, it is recommended to separately monitor and trend the origination and termination failure performance on a perBTS/sector/carrier level during the busy hour of each cell site. Performance Management (PM) peg counts For the PM peg counts, the following origination and termination failure rates can be calculated using data from the pmC_10 table.
Orig Fail % = [(10.1 10.3) / 10.1] * 100 Term Fail % = [(10.4 + 10.5 10.7) / (10.4 + 10.5)] * 100
Where: 10.1 is Origination Attempts 10.3 is Origination Assignment Completes 10.4 is Termination Attempts Slotted 10.5 is Termination Attempts Nonslotted 10.7 is Termination Assignment Completes. The performance calculations above should be recorded and trended on a daily basis. An analysis of the busy hour for each cell site is preferred, but an analysis of a full days worth of data can be performed as well. A degradation in the origination failure rate and/or the terminnation failure rate may be an indication of an overload condition of the paging and/or access channel. Call Failure Class (CFC) peg counts For the CFC peg counts from the Call Detail Logs, the primary CFCs to monitor are as follows:
S CFC 5 No TCH Preamble Detected S CFC 9 No Valid Speech from MS During Call Setup S CFC 13 CP Timeout Awaiting Service Option Ack.
The PM peg count data is preferred over the CFC data, because it is easier to post process the PM peg count data to achieve the desired origination and termination failure performance data on a perBTS/sector/carrier level.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-85
Introduction The engineer can reduce Control Channel utilization and improve system capacity by developing a Control Channel capacity management plan to address all of the issues identified in the Control Channel Planning Limits section.
Evaluate Relief Alternatives
Some reasons why the paging or access channels may have reached their limits include:
S Suboptimal traffic distribution across network elements S Higher-than-expected traffic intensities for certain traffic components
than were originally expected
S Re-definition of paging area boundaries S Re-definition of registration zones S Implementation of zonebased paging (if the system currently has a
broadcast paging scheme implemented). Prior to implementing any relief measures, the system designer should be knowledgeable with respect to the characteristics of the system. These characteristics ultimately have an impact upon the paging and access channels.
7
Determine System Characteristics To properly evaluate the various relief alternatives that might be feasible, the System Engineer needs to analyze various system characteristics that affect the paging or access channel utilization. The purpose of this analysis is to characterize the performance and configuration design of the system to identify a nonoptimum configuration. To characterize the performance, break down the total utilization into smaller components and analyze the individual events that utilize the channel (similar to a pareto analysis). If an individual event (for example, registrations) is dominating the utilization of either the paging or access channel, focus on identifying a nonoptimum configuration which may contribute to the load of the dominant event. If a nonoptimum configuration is identified, implement a relief alternative targeted at reducing the dominant event. To further analyze the system, characterize the following:
S Are turned off (if power-down de-registration is not available) S Have left the paging area and unsuccessfully registered.
Additionally, if a neighboring paging area has the same registration zone as the current paging area, the mobiles may move into the neighbor without registering. Therefore, some of the unacknowledged pages to the current paging area can be attributed to a registration zone that does not match the Paging Area Location. Re-Page Success Rate The re-page success rate corresponds to the number of re-page acknowledgments to the number of re-pages. Re-page is a feature of the EMX. Here, the Max Slot Cycle Index needs to be verified as non-zero. If the Max Slot Cycle Index is 0, the BTS uses the QREPEAT found in BTS PACHGEN. Neighbor Page Success Rate The neighbor page success rate corresponds to the number of neighbor page acknowledgments to the number of neighbor pages. This information helps to determine the number of mobiles in the wrong paging area. The number of mobiles saved by this feature needs to be compared to the amount of excess pages required to implement the feature. If only 1% of the mobiles are saved but the paging load goes from 40% to 80%, re-paging neighbors may cause more problems than it fixes. Special Paging Zones Details concerning any special paging zones that currently exist in the system should be understood. These special paging zones could be in the system due to subways/trains, registration boundaries, or pockets of single carrier sites surrounded by multi-carrier sites. Paging and Access Channel Capacity Management Options The effects of adding carriers and the changing of paging area boundaries on the events utilizing the paging channel are two relief measures to be considered.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-87
Paging channel utilization problems may appear for only a few sites in a paging area or for an entire paging area. This depends on how even the carriers (paging channels) are distributed across the paging area. If, for example, there is a one carrier (one paging channel) site in a paging area and the rest of the sites in that paging area are all four carrier (four paging channels), the one carrier site has a load approximately four times that of all the others. The means to reduce a paging channel load are to: 1. Increase the number of paging channels for that sector. 2. Reduce the size of the paging area that the site is located (reduce number of pages). 3. Reduce the number of unnecessary pages to that paging area. 4. Reduce the number of registrations for that sector. 5. Reduce the number of SMS messages or the size of these messages. Increasing the number of paging channels for that sector has the greatest effect when going from one to two paging channels. This increases the available resources 100%. When going from four to five paging channels, the increase is only 25%. Reducing the size of the paging area where the site is located will create more paging area boundaries. Placing a paging area boundary where many mobiles frequently cross back and forth will have adverse affects on the access channel. Reducing the number of unnecessary pages to that paging area can be achieved by looking at the EMX re-page statistics and evaluating whether or not it is performing optimally. If the EMX is contributing 30% of the pages to a neighbor paging area but only receives a handful of acknowledgments for those pages, this neighbor page setting is causing more problems than it is solving and, therefore, should be redefined. Access channel utilization problems may appear for only a few sites in a paging area or for an entire paging area. This depends on how even the carriers (access channels) are distributed across the paging area. If, for example, there is a one carrier (one access channel) site in a paging area and the rest of the sites in that paging area are all four carrier (four access channels), then the one carrier site will have a load approximately four times that of all the others. The means to reduce the access channel load are to:
S S S S
Increase the number of access channels for that sector Reduce the number of registrations for that sector Reduce the number of pages for that sector Increase the sectorization for the site.
Again, examine the control channels (paging and access) in terms of the events that utilize the channel, keeping in mind the means to reducing the load.
7-88 CDMA SC Products System Resource Guide (CSSRG) June 2001
Carrier Addition Address the addition of carriers, and subsequently a paging and access channel, by using the same method mentioned previously. For example, the section Pages: (PCHUtil Script: page) showed BTS-18 having 5,124 pages in a half-hour. The BTS has four carriers in the sector and therefore each paging channel carries 1,281 pages. If an additional carrier is added to this site, the sector now has an additional carrier with a paging channel. Each paging channel now carries 1,025 pages. From Table 7-16, a paging channel on BTS-18 sector two, carrier three is impacted by 91 completed mobile assignments (peg_count_7) in the busy half-hour. The other three carriers have mobilecompleted assignment values of 60, 59, and 87. The total of all four carriers is 297. Assuming nothing else changes except for adding an additional carrier and that the completed mobile assignments are distributed equally across the five carriers, each carrier has 60 completed mobile assignments. NOTE The fourcarrier data does not show an equal distribution of completions and therefore the engineer can multiply each of the four carrier s value by 4/5. The fifth carrier is then the difference between 297 and the sum of the adjusted carriers value.
297
91
4 5
+ 60
4 5
+ 59
4 5
+ 87
4 5
7
297 [73 + 48 + 47 + 70] = 59 The total number of half-frames required on BTS-18 sector two, carrier three for the half-hour is: Base Station Ack Order Channel Assignment Msg. General Page Msg. 60 60 1,025 * 2 = 120 * 2 = 120 * 2 = 2,050 2,290 half-frames Therefore, the utilization of the paging channel for terminations is now 1.27%. That is down from 1.62% using four carriers. This example only demonstrates one scenario for the paging channel. By adding an additional carrier, the mobile origination completions and failures, registrations and SMS messages are also impacted in the same way. This holds true for both the paging and access channels.
June 2001 CDMA SC Products System Resource Guide (CSSRG) 7-89
Paging Area Re-Definitions Changing the paging area boundary involves predicting the paging load for the redefined paging area(s) or CBSC. Therefore, the characteristics of each of the existing paging areas must be understood. These characteristics include:
S Page success rate S Re-page success rate S Neighbor page success rate.
The EMX paging configuration as well as the CBSCs paging configuration must also be defined. The predicted paging load can then be used in determining the paging channel utilization. Determining the number of registrations between two sectors, that have never been boundary sectors in the past, is difficult. The difficulty comes from the fact that the mobiles are in the idle state. Within a paging area, if an idle mobile travels from one site to another, the system does not keep track of this. Special Paging Zones Subways, registration boundaries, and pockets of single carrier sites surrounded by multi-carrier sites may be candidates for special paging zones. Special paging areas are established to either reduce the number of pages sent to that area or to establish overlap between registration zones. One special type of a paging zone is an imbedded paging area. The intent of this paging zone is to reduce the number of pages sent to these areas. These areas typically have single carrier sites surrounded by multi-carrier sites. Currently, there is only one paging channel per carrier. All sites within a particular paging area are required to send the same number of pages. The multiple-carrier sites have the advantage of multiple paging channels (there is a paging channel for each carrier frequency). The pages are distributed among the multiple carriers by means of a hashing algorithm. When a one carrier site is in a paging area containing sites with, for example, four carriers, the onecarrier site has four times the paging load of the fourcarrier sites (assuming each carrier has a separate paging channel). One approach to alleviate the paging load on these single carrier sites is to establish a special paging area within the main paging area. These sites have a different Location Area Code (LAC) but the same registration zone as the main paging area. The EMX is then configured for Re-page Your Neighbor, specifying this special paging area as a neighbor to the main paging area. This configuration reduces the number of pages sent to this area to the number of unacknowledged pages sent to the main paging area. The idea is that this will be a significantly smaller number. The drawback to this configuration is that since the mobiles coming from the main paging area do not register when entering this special paging area, they would not receive the initial page which therefore increases the setup time for mobile terminated calls.
7-90 CDMA SC Products System Resource Guide (CSSRG) June 2001
Another special paging zone scenario that can be established is to insure that a mobile on the registration boundary receives the page. A mobile has a zone list and a zone timer it uses to keep track of the zones that it is in and has been in. Total zones, sent in the Systems Parameters Message, represent the number of zones a mobile keeps in memory. The zone list represents the actual zones the mobile keeps in memory. Zones are uniquely identified by a combination of the SID, NID, and zone number. The zone timer is the amount of time the mobile keeps the other zones (the zones not currently in) before removing them. These parameters keep a mobile from ping-ponging back and forth between registration zones. A mobile will not re-register if the zone is in its zone list and the zone timer has not expired. This keeps the registrations lower but increases the chance that the mobile is in the wrong paging area when the page is sent. One method to get around this is to use the Re-page Your Neighbor feature. By putting the other paging area in the neighbor list of the EMX, the second page is sent to the other paging area and the calls are completed. However, if the paging areas have a large number of unacknowledged pages, each paging area contributes a substantial number of pages to the other and increases the paging load. Another situation that may exist is when trains or subways cross registration boundaries that have a different call model than that of other boundary locations. All of the users on a train cross the registration boundary at specific times (train schedule). This puts the access channel into an overload condition while the train is crossing the boundary. Having a boundary between subway stations reduces the number of mobiles that ping-pong back and forth between paging areas. Registration Re-Definitions Registrations can be triggered with the occurrence of various events. For instance, the system may be set up where a subscriber unit registers every 15 minutes while it is turned on. As a means to reduce the paging and access channel load, it may be possible to change the registration time to be every 30 or 60 minutes. The following example lists various items that can be changed to alter how often registrations will take place: S Register based on time
practical option. For systems that are not heavily loaded, a broadcast paging scheme can be an effective scheme from a performance standpoint. If a subscriber is registered in a broadcast paging system, the chances of a subscriber receiving a page are maximized, since pages are broadcast to every base station in the system. In a zonebased system, there can be scenarios where a subscriber may be paged in one zone, but located in another. As the subscriber and paging load increases over a long period of time, converting to a zonebased paging scheme may be unavoidable. The borders for the paging and registration zones for a zonebased paging scheme must be designed carefully. Sites along a paging/registration zone border typically exhibit a higher paging/access channel utilization due to being on the border of two zones. As a result, the border sites must be strategically selected to be able to handle this increase of traffic due to the border effects. As mentioned earlier, the usage of special paging zones may be necessary for some systems. Ultimately, the design of a particular zonebased paging system should attempt to optimize the performance of the following:
S Page Success Rate S RePage Success Rate S Neighbor Page Success Rate.
A zonebased paging system should also attempt to optimize the paging and access channel utilization. Perform a reanalysis of the paging system after converting to a zonebased paging scheme. Additional optimization may be necessary after the conversion has been performed. Increase Sectorization The typical sectorization conversions are as follows:
Performance Management information needs to be collected in order to monitor the paging and access channels. The other information will be required when relief alternatives need to be investigated.
7-92 CDMA SC Products System Resource Guide (CSSRG) June 2001
S S S S S S S S
pmC_10_hr pmC_20_hr pmC_52_hr pmC_70_hr. REPORT PAGING AREA (specific requires PLI feature) REPORT SYSTEM LOAD REPORT EMX PAGE REPORT IMDREG STATS.
EMX:
S S S S S S S S S S S S S S S S S S S S
DISPLAY CBSC CBSCGEN DISPLAY CBSC PAGPARMS DISPLAY CBSC REGPARMS DISPLAY CBSC REGTYPE DISPLAY CBSC ALLSTATUS DISPLAY CBSC LOCAREAS DISPLAY CBSC AUTHENTIC DISPLAY CBSC LOCATION DISPLAY BTS CHANCONF DISPLAY BTS CHANNELLIST DISPLAY BTS SECGEN DISPLAY BTS PACHGEN DISPLAY BTS SECTOP DISPLAY SCH DIRECT. DISP CP ROAMPKG DISP BSS BSSRTE DISP CP PAGMOD (Defines Broadcast or Directed Paging) DISP MOB DGLOBL (Timers) DISP BSS TIMER (Timers) DISP CELNET NPAGE (Repage neighbor definitions).
EMX:
Other Information
Site names Latitude and longitude Subscriber base BTS type (SC9600, etc.).
7-94
June 2001
CDMA Call Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MobiletoLand Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LandtoMobile Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handoff in a LandtoMobile Call . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
Table of Contents
continued
Notes
June 2001
MobiletoLand Set Up
PSTN
MSC
3, 5
OMCR
BSS
2, 4
XC
MM
CBSC
BTS
BTS
BTS
MS
1. The Mobile Station (MS) sends the Origination message and dialed digits on the access channel through the BTS and the Transcoder (XC) to the Mobility Manager (MM). 2. The MM routes the registration data to the Mobile Services Switching Center (MSC) through the XC. 3. The MSC sends the Origination message through the XC to the MM. 4. The MM routes the dialed digits to the MSC through the XC. 5. The MSC sends the terrestrial circuit assignment through the XC to the MM.
June 2001
A-1
PSTN
MSC
OMCR
BSS
6, 7
XC
MM
CBSC
BTS
BTS
BTS MS
6. The MM assigns the circuits and BTS channel element. Circuit The Kiloport Switch (KSW) connections correspond to Transcoder (XC) circuit mapped to the terrestrial circuit allocated by the MSC and the T1 subtimeslot associated with the traffic channel MCC allocated by the MM. BTS channel element Walsh code assignment and long code assignment. 7. The MM sends the Mobile Channel Assignment message through the XC to the BTS.
A-2
June 2001
PSTN
MSC
OMCR
BSS
XC
MM
CBSC
10
BTS
BTS
BTS
8 9
MS
8. The Base Station System (BTS) sends the Traffic Assignment message on the paging channel. 9. The Mobile Station receives the message and begins to transmit with the Preamble message spread with its long code. 10. The BTS waits for the mobile signal to be of sufficient strength at the rake receiver and routes the preamble data to the XC.
June 2001
A-3
PSTN
MSC
17 13
OMCR
BSS
12, 18
XC
11 15, 19 14
MM
CBSC
BTS
BTS
BTS
16
MS
The XC acknowledges the receipt of the preamble to the MM. The MM alerts the MSC through the XC. The MSC directs the MM to send/generate the ringback message. The MM routes the message to the BTS though the XC. The BTS transmits the message on the traffic channel. The mobile generates the ringback. The MSC sends the offhook to the MM through the XC. The MM sends the connection acknowledge to the MSC through the XC. The call is completed through the XC.
June 2001
PSTN
MSC
2
OMCR
BSS
2, 5
XC
3 3 3
MM
CBSC
BTS
BTS
BTS
4
MS
1. The PSTN sends an incoming call to the MSC. 2. The MSC determines if the mobile is valid. The MSC identifies the mobile and the cell in which the mobile is to be paged. The MSC sends the message to the MM of the BSS in which the MS is located. 3. The MS is paged in all of the cells under control of the CBSC by sending one page message to each BTS. 4. The BTS sends the page out on each paging channel equipped and monitors access for a response. 5. The BTS sends the page acknowledgment to the MM through the XC.
June 2001 CDMA SC Products System Resource Guide (CSSRG) A-5
PSTN
MSC
8
OMCR
BSS
6, 7
XC
11
MM
9, 10, 12
CBSC
BTS
BTS
BTS MS
6. The MM verifies the requested service option is supported. 7. The MM sends all validation information to the MSC along with the circuit assignment request through the XC. 8. The MSC performs the validation and sends the circuit assignment to the MM. 9. The MM assigns the circuits and BTS channel element. Circuit The Kiloport Switch (KSW) connections correspond to the Transcoder (XC) circuit mapped to the terrestrial circuit allocated by the MSC and the T1 sub timeslot associated with the traffic channel MCC allocated by the MM. BTS channel element Walsh code assignment and long code assignment.
A-6
June 2001
The MM sends the Channel Assignment message and sends preamble data. The data is detected through to the XC. The MM informs the MSC of the channel assignment. The MSC waits for the MM to indicate the MS is being alerted.
June 2001
A-7
PSTN
MSC
14
OMCR
BSS
13
XC
MM
CBSC
15
BTS
BTS
BTS MS
The MM sends the Alert message through the XC for the MS to alert the subscriber and the MS generates the ringback to the subscriber. When the MS subscriber answers the call, the MS sends a connect message to the MM which forwards it to the MSC. The MSC indicates to the land party that the subscriber has answered and connects to the PSTN.
A-8
June 2001
PSTN
MSC
OMCR
BSS
XC
2
MM
CBSC
BTS
BTS
BTS MS
1. The pilot channel measurement is reported from the mobile to the MM when the measured pilot strength exceeds T_Add parameter. NOTE
PSTN
MSC
OMCR
BSS
XC
3 4
MM
CBSC
BTS
BTS
BTS
MS
3. The MM recognizes the add in the adjacent sector, assigns the Walsh code in the target sector, and sends the Handoff Direction message to the XC. 4. The XC sends the Handoff Channel Assigned message, including the power control loop threshold and forward channel gain. 5. The MCC sets up the channel element to operate in the new sector. 6. The BTS messages the XC with a forward channel transmission indication. 7. The BTS transmits on both forward links.
A-10
June 2001
PSTN
MSC
OMCR
BSS
XC
14 15
MM
CBSC
9, 13
BTS
BTS
BTS
10, 12
11
MS
8. The Handoff Direction message, sent via the BTS for the mobile, contains the new T_ADD, T_Drop pilots, and Walsh codes of the active channel element. 9. The MS is instructed to combine the power control bits. 10. The MS sends the Handoff Completion message to the XC. 11. The acknowledgement is sent to the MS. 12. The BTS sends the MM the CDMA Handoff Successful message. 13. The MM instructs the XC to update the parameters. 14. The XC sends the neighbor list to the MS. 15. The Power Control parameters are sent and acknowledged.
June 2001
A-11
Notes
A-12
June 2001
Erlang B Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking Erlangs using the Erlang B Model . . . . . . . . . . . . . . . . . . . . . Erlang B Table for T1/E1 Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
June 2001
Table of Contents
continued
Notes
June 2001
B
Table B-1: Erlangs per Blocking
Channels N 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
0.1% 0.00 0.05 0.19 0.44 0.76 1.15 1.58 2.05 2.56 3.09 3.65 4.23 4.83 5.45 6.08 6.72 7.38 8.05 8.72 9.41 10.11 10.81 11.52 12.24 12.97 13.70 14.44 15.18 15.93
0.15% 0.00 0.06 0.22 0.49 0.84 1.25 1.70 2.20 2.73 3.28 3.86 4.46 5.08 5.71 6.36 7.03 7.70 8.39 9.08 9.79 10.50 11.22 11.95 12.68 13.42 14.17 14.92 15.68 16.44
0.2% 0.00 0.07 0.25 0.54 0.90 1.33 1.80 2.31 2.85 3.43 4.02 4.64 5.27 5.92 6.58 7.26 7.95 8.64 9.35 10.07 10.79 11.53 12.26 13.01 13.76 14.52 15.29 16.05 16.83
0.3% 0.00 0.08 0.29 0.60 0.99 1.45 1.95 2.48 3.05 3.65 4.27 4.90 5.56 6.23 6.91 7.61 8.32 9.03 9.76 10.50 11.24 11.99 12.75 13.51 14.28 15.05 15.83 16.62 17.41
0.5% 0.01 0.11 0.35 0.70 1.13 1.62 2.16 2.73 3.33 3.96 4.61 5.28 5.96 6.66 7.38 8.10 8.83 9.58 10.33 11.09 11.86 12.63 13.42 14.20 15.00 15.79 16.60 17.41 18.22
1.0% 0.01 0.15 0.46 0.87 1.36 1.91 2.50 3.13 3.78 4.46 5.16 5.88 6.61 7.35 8.11 8.88 9.65 10.44 11.23 12.03 12.84 13.65 14.47 15.30 16.12 16.96 17.80 18.64 19.49
1.5% 0.02 0.19 0.54 0.99 1.52 2.11 2.74 3.40 4.09 4.81 5.54 6.29 7.05 7.82 8.61 9.41 10.21 11.02 11.84 12.67 13.51 14.35 15.19 16.04 16.89 17.75 18.62 19.48 20.35
2.0% 0.02 0.22 0.60 1.09 1.66 2.28 2.94 3.63 4.34 5.08 5.84 6.61 7.40 8.20 9.01 9.83 10.66 11.49 12.33 13.18 14.04 14.90 15.76 16.63 17.50 18.38 19.26 20.15 21.04
3.0% 0.03 0.28 0.72 1.26 1.88 2.54 3.25 3.99 4.75 5.53 6.33 7.14 7.97 8.80 9.65 10.51 11.37 12.24 13.11 14.00 14.89 15.78 16.68 17.58 18.48 19.39 20.31 21.22 22.14
5.0% 0.05 0.38 0.90 1.52 2.22 2.96 3.74 4.54 5.37 6.22 7.08 7.95 8.83 9.73 10.63 11.54 12.46 13.39 14.31 15.25 16.19 17.13 18.08 19.03 19.99 20.94 21.90 22.87 23.83
Channels N
0.1% 16.68 17.44 18.20 18.97 19.74 20.52 21.30 22.08 22.86 23.65 24.44 25.24 26.04 26.84 27.64 28.45 29.25 30.07 30.88 31.69 32.51 33.33 34.15 34.98 35.80 36.63 37.46 38.29 39.12 39.96 40.79 41.63
0.15% 17.21 17.98 18.76 19.54 20.32 21.11 21.90 22.70 23.50 24.30 25.10 25.91 26.72 27.53 28.35 29.17 29.99 30.81 31.63 32.46 33.29 34.12 34.95 35.79 36.63 37.46 38.31 39.15 39.99 40.84 41.68 42.53
0.2% 17.61 18.39 19.18 19.97 20.76 21.56 22.36 23.17 23.97 24.78 25.60 26.42 27.23 28.06 28.88 29.71 30.54 31.37 32.20 33.04 33.88 34.72 35.56 36.40 37.25 38.09 38.94 39.79 40.64 41.50 42.35 43.21
0.3% 18.20 19.00 19.80 20.61 21.42 22.23 23.05 23.87 24.69 25.52 26.35 27.18 28.01 28.85 29.68 30.52 31.37 32.21 33.06 33.91 34.76 35.61 36.47 37.32 38.18 39.04 39.90 40.76 41.63 42.49 43.36 44.23
0.5% 19.03 19.85 20.68 21.50 22.34 23.17 24.01 24.85 25.69 26.53 27.38 28.23 29.08 29.94 30.80 31.66 32.52 33.38 34.25 35.11 35.98 36.85 37.72 38.60 39.47 40.35 41.23 42.11 42.99 43.87 44.76 45.64
1.0% 20.34 21.19 22.05 22.91 23.77 24.64 25.51 26.38 27.25 28.13 29.01 29.89 30.77 31.66 32.54 33.43 34.32 35.21 36.11 37.00 37.90 38.80 39.70 40.60 41.50 42.41 43.31 44.22 45.13 46.04 46.95 47.86
1.5% 21.23 22.10 22.98 23.87 24.75 25.64 26.53 27.42 28.32 29.22 30.12 31.02 31.92 32.83 33.73 34.64 35.55 36.47 37.38 38.30 39.21 40.13 41.05 41.97 42.89 43.82 44.74 45.67 46.59 47.52 48.45 49.38
2.0% 21.93 22.83 23.72 24.63 25.53 26.43 27.34 28.25 29.17 30.08 31.00 31.92 32.84 33.76 34.68 35.61 36.53 37.46 38.39 39.32 40.26 41.19 42.12 43.06 44.00 44.94 45.88 46.82 47.76 48.70 49.64 50.59
3.0% 23.06 23.99 24.91 25.84 26.78 27.71 28.65 29.59 30.53 31.47 32.41 33.36 34.30 35.25 36.20 37.16 38.11 39.06 40.02 40.97 41.93 42.89 43.85 44.81 45.78 46.74 47.70 48.67 49.63 50.60 51.57 52.54
5.0% 24.80 25.77 26.75 27.72 28.70 29.68 30.66 31.64 32.62 33.61 34.60 35.58 36.57 37.56 38.56 39.55 40.54 41.54 42.54 43.53 44.53 45.53 46.53 47.53 48.54 49.54 50.54 51.55 52.55 53.56 54.57 55.57
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
B-2
June 2001
Channels N 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
0.1% 42.47 43.31 44.16 45.00 45.84 46.69 47.54 48.39 49.24 50.09 50.94 51.80 52.65 53.51 54.37 55.23 56.09 56.95 57.81 58.67 59.54 60.40 61.27 62.14 63.00 63.87 64.74 65.61 66.48 67.36 68.23 69.10
0.15% 43.38 44.23 45.09 45.94 46.80 47.65 48.51 49.37 50.23 51.09 51.96 52.82 53.69 54.55 55.42 56.29 57.16 58.03 58.90 59.77 60.65 61.52 62.40 63.27 64.15 65.03 65.91 66.79 67.67 68.55 69.43 70.31
0.2% 44.07 44.93 45.79 46.65 47.51 48.38 49.24 50.11 50.98 51.85 52.72 53.59 54.46 55.34 56.21 57.09 57.96 58.84 59.72 60.60 61.48 62.36 63.24 64.13 65.01 65.90 66.78 67.67 68.56 69.44 70.33 71.22
0.3% 45.10 45.97 46.84 47.72 48.59 49.47 50.34 51.22 52.10 52.98 53.87 54.75 55.63 56.52 57.40 58.29 59.18 60.07 60.95 61.85 62.74 63.63 64.52 65.42 66.31 67.21 68.10 69.00 69.90 70.79 71.69 72.59
0.5% 46.53 47.42 48.30 49.19 50.09 50.98 51.87 52.77 53.66 54.56 55.46 56.35 57.25 58.15 59.05 59.96 60.86 61.76 62.67 63.57 64.48 65.39 66.29 67.20 68.11 69.02 69.93 70.84 71.76 72.67 73.58 74.50
1.0% 48.77 49.69 50.60 51.52 52.44 53.35 54.27 55.19 56.11 57.03 57.96 58.88 59.80 60.73 61.65 62.58 63.51 64.43 65.36 66.29 67.22 68.15 69.08 70.02 70.95 71.88 72.81 73.75 74.68 75.62 76.56 77.49
1.5% 50.31 51.24 52.17 53.11 54.04 54.98 55.92 56.85 57.79 58.73 59.67 60.61 61.55 62.49 63.43 64.38 65.32 66.27 67.21 68.16 69.10 70.05 71.00 71.95 72.90 73.84 74.79 75.75 76.70 77.65 78.60 79.55
2.0% 51.53 52.48 53.43 54.38 55.33 56.27 57.23 58.18 59.13 60.08 61.04 61.99 62.94 63.90 64.86 65.81 66.77 67.73 68.69 69.65 70.61 71.57 72.53 73.49 74.45 75.42 76.38 77.34 78.31 79.27 80.24 81.20
3.0% 53.51 54.48 55.45 56.42 57.39 58.37 59.34 60.32 61.29 62.27 63.24 64.22 65.20 66.18 67.16 68.14 69.12 70.10 71.08 72.06 73.04 74.02 75.01 75.99 76.97 77.96 78.94 79.93 80.91 81.90 82.89 83.87
5.0% 56.58 57.59 58.60 59.61 60.62 61.63 62.64 63.65 64.67 65.68 66.69 67.71 68.72 69.74 70.75 71.77 72.79 73.80 74.82 75.84 76.86 77.87 78.89 79.91 80.93 81.95 82.97 83.99 85.01 86.04 87.06 88.08
June 2001
B-3
Channels N
0.1% 69.98 70.85 71.73 72.61 73.48 74.36 75.24 76.12 77.00 77.88 78.77 79.65 80.53 81.42 82.30 83.19 84.07 84.96 85.85 86.73 87.62 88.51 89.40 90.29 91.18 92.07 92.96 93.86 94.75 95.64 96.54 97.43
0.15% 71.20 72.08 72.96 73.85 74.74 75.62 76.51 77.40 78.29 79.18 80.07 80.96 81.85 82.75 83.64 84.53 85.43 86.32 87.22 88.11 89.01 89.91 90.81 91.70 92.60 93.50 94.40 95.30 96.20 97.10 98.01 98.91
0.2% 72.11 73.00 73.90 74.79 75.68 76.57 77.47 78.36 79.26 80.16 81.05 81.95 82.85 83.75 84.65 85.55 86.45 87.35 88.25 89.15 90.06 90.96 91.86 92.77 93.67 94.58 95.48 96.39 97.30 98.20 99.11 100.02
0.3% 73.49 74.39 75.30 76.20 77.10 78.01 78.91 79.81 80.72 81.63 82.53 83.44 84.35 85.26 86.17 87.08 87.99 88.90 89.81 90.72 91.63 92.54 93.46 94.37 95.29 96.20 97.12 98.03 98.95 99.86 100.78 101.70
0.5% 75.41 76.32 77.24 78.16 79.07 79.99 80.91 81.83 82.75 83.67 84.59 85.51 86.43 87.35 88.28 89.20 90.12 91.05 91.97 92.89 93.82 94.75 95.67 96.60 97.53 98.45 99.38 100.31 101.24 102.17 103.10 104.03
1.0% 78.43 79.37 80.31 81.24 82.18 83.12 84.06 85.00 85.95 86.89 87.83 88.77 89.72 90.66 91.60 92.55 93.49 94.44 95.38 96.33 97.28 98.22 99.17 100.12 101.07 102.01 102.96 103.91 104.86 105.81 106.76 107.71
1.5% 80.51 81.46 82.41 83.37 84.32 85.28 86.23 87.19 88.15 89.10 90.06 91.02 91.98 92.94 93.90 94.86 95.82 96.78 97.74 98.70 99.66 100.62 101.58 102.55 103.51 104.47 105.43 106.40 107.36 108.33 109.29 110.26
2.0% 82.17 83.13 84.10 85.07 86.04 87.00 87.97 88.94 89.91 90.88 91.85 92.82 93.79 94.76 95.73 96.71 97.68 98.65 99.62 100.60 101.57 102.54 103.52 104.49 105.47 106.44 107.42 108.39 109.37 110.35 111.32 112.30
3.0% 84.86 85.85 86.84 87.83 88.82 89.80 90.79 91.78 92.77 93.76 94.76 95.75 96.74 97.73 98.72 99.71 100.71 101.70 102.69 103.69 104.68 105.68 106.67 107.66 108.66 109.66 110.65 111.65 112.64 113.64 114.64 115.63
5.0% 89.10 90.12 91.15 92.17 93.19 94.22 95.24 96.26 97.29 98.31 99.34 100.36 101.39 102.42 103.44 104.47 105.49 106.52 107.55 108.57 109.60 110.63 111.66 112.69 113.71 114.74 115.77 116.80 117.83 118.86 119.89 120.92
94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125
B-4
June 2001
Channels N 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157
0.1% 98.33 99.22 100.12 101.01 101.91 102.81 103.71 104.60 105.50 106.40 107.30 108.20 109.10 110.00 110.90 111.81 112.71 113.61 114.51 115.42 116.32 117.23 118.13 119.04 119.94 120.85 121.75 122.66 123.57 124.47 125.38 126.29
0.15% 99.81 100.71 101.62 102.52 103.43 104.33 105.24 106.14 107.05 107.96 108.86 109.77 110.68 111.59 112.50 113.41 114.32 115.23 116.14 117.05 117.96 118.87 119.78 120.69 121.61 122.52 123.43 124.35 125.26 126.18 127.09 128.01
0.2% 100.93 101.84 102.75 103.66 104.57 105.48 106.39 107.30 108.22 109.13 110.04 110.95 111.87 112.78 113.70 114.61 115.53 116.44 117.36 118.28 119.19 120.11 121.03 121.95 122.86 123.78 124.70 125.62 126.54 127.46 128.38 129.30
0.3% 102.62 103.53 104.45 105.37 106.29 107.21 108.13 109.05 109.97 110.89 111.82 112.74 113.66 114.58 115.51 116.43 117.35 118.28 119.20 120.13 121.05 121.98 122.91 123.83 124.76 125.69 126.61 127.54 128.47 129.40 130.33 131.25
0.5% 104.96 105.89 106.82 107.75 108.68 109.62 110.55 111.48 112.42 113.35 114.28 115.22 116.15 117.09 118.02 118.96 119.90 120.83 121.77 122.71 123.64 124.58 125.52 126.46 127.40 128.33 129.27 130.21 131.15 132.09 133.03 133.97
1.0% 108.66 109.61 110.57 111.52 112.47 113.42 114.38 115.33 116.28 117.24 118.19 119.14 120.10 121.05 122.01 122.96 123.92 124.88 125.83 126.79 127.75 128.70 129.66 130.62 131.58 132.53 133.49 134.45 135.41 136.37 137.33 138.29
1.5% 111.22 112.19 113.15 114.12 115.09 116.05 117.02 117.99 118.95 119.92 120.89 121.86 122.83 123.80 124.77 125.74 126.70 127.67 128.64 129.62 130.59 131.56 132.53 133.50 134.47 135.44 136.41 137.39 138.36 139.33 140.30 141.28
2.0% 113.28 114.25 115.23 116.21 117.19 118.17 119.15 120.12 121.10 122.08 123.06 124.04 125.02 126.00 126.98 127.97 128.95 129.93 130.91 131.89 132.87 133.86 134.84 135.82 136.80 137.79 138.77 139.75 140.74 141.72 142.70 143.69
3.0% 116.63 117.63 118.62 119.62 120.62 121.62 122.62 123.61 124.61 125.61 126.61 127.61 128.61 129.61 130.61 131.61 132.61 133.61 134.61 135.61 136.61 137.61 138.61 139.62 140.62 141.62 142.62 143.62 144.63 145.63 146.63 147.63
5.0% 121.95 122.98 124.01 125.04 126.07 127.10 128.13 129.16 130.19 131.22 132.25 133.28 134.32 135.35 136.38 137.41 138.44 139.48 140.51 141.54 142.57 143.61 144.64 145.67 146.71 147.74 148.77 149.81 150.84 151.87 152.91 153.94
June 2001
B-5
Channels N
0.1% 127.20 128.11 129.01 129.92 130.83 131.74 132.65 133.56 134.48 135.39 136.30 137.21 138.12 139.04 139.95 140.86 141.77 142.69 143.60 144.52 145.43 146.35 147.26 148.18 149.09 150.01 150.93 151.84 152.76 153.68 154.59 155.51
0.15% 128.92 129.84 130.75 131.67 132.59 133.50 134.42 135.34 136.26 137.18 138.09 139.01 139.93 140.85 141.77 142.69 143.61 144.53 145.45 146.38 147.30 148.22 149.14 150.06 150.99 151.91 152.83 153.76 154.68 155.60 156.53 157.45
0.2% 130.22 131.14 132.07 132.99 133.91 134.83 135.75 136.68 137.60 138.52 139.45 140.37 141.30 142.22 143.15 144.07 145.00 145.92 146.85 147.78 148.70 149.63 150.56 151.49 152.41 153.34 154.27 155.20 156.13 157.06 157.99 158.91
0.3% 132.18 133.11 134.04 134.97 135.90 136.83 137.77 138.70 139.63 140.56 141.49 142.42 143.36 144.29 145.22 146.16 147.09 148.02 148.96 149.89 150.83 151.76 152.70 153.63 154.57 155.50 156.44 157.38 158.31 159.25 160.19 161.12
0.5% 134.91 135.86 136.80 137.74 138.68 139.62 140.57 141.51 142.45 143.39 144.34 145.28 146.23 147.17 148.11 149.06 150.00 150.95 151.89 152.84 153.79 154.73 155.68 156.62 157.57 158.52 159.46 160.41 161.36 162.31 163.25 164.20
1.0% 139.25 140.21 141.17 142.13 143.09 144.05 145.01 145.97 146.93 147.89 148.86 149.82 150.78 151.74 152.71 153.67 154.63 155.60 156.56 157.52 158.49 159.45 160.42 161.38 162.34 163.31 164.27 165.24 166.21 167.17 168.14 169.10
1.5% 142.25 143.22 144.20 145.17 146.15 147.12 148.09 149.07 150.04 151.02 151.99 152.97 153.94 154.92 155.90 156.87 157.85 158.82 159.80 160.78 161.75 162.73 163.71 164.69 165.66 166.64 167.62 168.60 169.58 170.55 171.53 172.51
2.0% 144.67 145.66 146.64 147.63 148.61 149.60 150.58 151.57 152.55 153.54 154.53 155.51 156.50 157.48 158.47 159.46 160.44 161.43 162.42 163.41 164.39 165.38 166.37 167.36 168.35 169.33 170.32 171.31 172.30 173.29 174.28 175.27
3.0% 148.64 149.64 150.64 151.65 152.65 153.66 154.66 155.66 156.67 157.67 158.68 159.68 160.69 161.69 162.70 163.70 164.71 165.71 166.72 167.72 168.73 169.73 170.74 171.75 172.75 173.76 174.77 175.77 176.78 177.79 178.79 179.80
5.0% 154.98 156.01 157.05 158.08 159.12 160.15 161.19 162.22 163.26 164.29 165.33 166.36 167.40 168.43 169.47 170.50 171.54 172.58 173.61 174.65 175.69 176.72 177.76 178.79 179.83 180.87 181.91 182.94 183.98 185.02 186.05 187.09
158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189
B-6
June 2001
Channels N 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221
0.1% 156.43 157.35 158.27 159.19 160.10 161.02 161.94 162.86 163.78 164.70 165.62 166.54 167.47 168.39 169.31 170.23 171.15 172.07 173.00 173.92 174.84 175.77 176.69 177.61 178.54 179.46 180.38 181.31 182.23 183.16 184.08 185.01
0.15% 158.38 159.30 160.23 161.15 162.08 163.00 163.93 164.86 165.78 166.71 167.64 168.56 169.49 170.42 171.35 172.27 173.20 174.13 175.06 175.99 176.92 177.85 178.78 179.71 180.64 181.57 182.50 183.43 184.36 185.29 186.22 187.15
0.2% 159.84 160.77 161.70 162.64 163.57 164.50 165.43 166.36 167.29 168.22 169.15 170.09 171.02 171.95 172.88 173.82 174.75 175.68 176.62 177.55 178.49 179.42 180.36 181.29 182.22 183.16 184.10 185.03 185.97 186.90 187.84 188.77
0.3% 162.06 163.00 163.94 164.87 165.81 166.75 167.69 168.63 169.57 170.51 171.45 172.39 173.33 174.27 175.21 176.15 177.09 178.03 178.97 179.91 180.85 181.80 182.74 183.68 184.62 185.56 186.51 187.45 188.39 189.34 190.28 191.22
0.5% 165.15 166.10 167.05 168.00 168.95 169.90 170.85 171.79 172.74 173.69 174.64 175.60 176.55 177.50 178.45 179.40 180.35 181.30 182.25 183.21 184.16 185.11 186.06 187.01 187.97 188.92 189.87 190.83 191.78 192.73 193.69 194.64
1.0% 170.07 171.03 172.00 172.97 173.93 174.90 175.87 176.84 177.80 178.77 179.74 180.71 181.67 182.64 183.61 184.58 185.55 186.52 187.48 188.45 189.42 190.39 191.36 192.33 193.30 194.27 195.24 196.21 197.18 198.15 199.12 200.09
1.5% 173.49 174.47 175.45 176.43 177.41 178.39 179.37 180.35 181.33 182.31 183.29 184.27 185.25 186.23 187.21 188.19 189.17 190.15 191.13 192.11 193.10 194.08 195.06 196.04 197.02 198.01 198.99 199.97 200.95 201.93 202.92 203.90
2.0% 176.26 177.25 178.24 179.23 180.22 181.21 182.20 183.19 184.18 185.17 186.16 187.15 188.14 189.13 190.12 191.11 192.10 193.10 194.09 195.08 196.07 197.06 198.06 199.05 200.04 201.03 202.02 203.02 204.01 205.00 206.00 206.99
3.0% 180.81 181.81 182.82 183.83 184.84 185.85 186.85 187.86 188.87 189.88 190.89 191.89 192.90 193.91 194.92 195.93 196.94 197.95 198.96 199.97 200.97 201.98 202.99 204.00 205.01 206.02 207.03 208.04 209.05 210.06 211.07 212.08
5.0% 188.13 189.17 190.20 191.24 192.28 193.32 194.35 195.39 196.43 197.47 198.51 199.55 200.58 201.62 202.66 203.70 204.74 205.78 206.82 207.85 208.89 209.93 210.97 212.01 213.05 214.09 215.13 216.17 217.21 218.25 219.29 220.33
June 2001
B-7
Channels N
0.1% 185.93 186.86 187.78 188.71 189.64 190.56 191.49 192.42 193.34 194.27 195.20 196.13 197.05 197.98 198.91 199.84 200.77 201.69 202.62 203.55 204.48 205.41 206.34 207.27 208.20 209.13 210.06 210.99 211.92 212.85 213.78 214.72
0.15% 188.09 189.02 189.95 190.88 191.81 192.75 193.68 194.61 195.55 196.48 197.41 198.35 199.28 200.21 201.15 202.08 203.02 203.95 204.89 205.82 206.76 207.69 208.63 209.56 210.50 211.44 212.37 213.31 214.25 215.18 216.12 217.06
0.2% 189.71 190.65 191.58 192.52 193.46 194.40 195.33 196.27 197.21 198.15 199.09 200.02 200.96 201.90 202.84 203.78 204.72 205.66 206.60 207.54 208.48 209.42 210.36 211.30 212.24 213.18 214.12 215.06 216.00 216.94 217.88 218.83
0.3% 192.17 193.11 194.05 195.00 195.94 196.89 197.83 198.78 199.72 200.67 201.61 202.56 203.50 204.45 205.40 206.34 207.29 208.23 209.18 210.13 211.07 212.02 212.97 213.92 214.86 215.81 216.76 217.71 218.65 219.60 220.55 221.50
0.5% 195.59 196.55 197.50 198.46 199.41 200.37 201.32 202.28 203.23 204.19 205.14 206.10 207.05 208.01 208.97 209.92 210.88 211.83 212.79 213.75 214.70 215.66 216.62 217.58 218.53 219.49 220.45 221.41 222.36 223.32 224.28 225.24
1.0% 201.06 202.04 203.01 203.98 204.95 205.92 206.89 207.86 208.84 209.81 210.78 211.75 212.72 213.70 214.67 215.64 216.61 217.59 218.56 219.53 220.51 221.48 222.45 223.43 224.40 225.37 226.35 227.32 228.30 229.27 230.25 231.22
1.5% 204.88 205.87 206.85 207.83 208.82 209.80 210.78 211.77 212.75 213.74 214.72 215.70 216.69 217.67 218.66 219.64 220.63 221.61 222.60 223.58 224.57 225.55 226.54 227.52 228.51 229.49 230.48 231.46 232.45 233.44 234.42 235.41
2.0% 207.98 208.97 209.97 210.96 211.95 212.95 213.94 214.94 215.93 216.92 217.92 218.91 219.91 220.90 221.90 222.89 223.88 224.88 225.87 226.87 227.86 228.86 229.85 230.85 231.84 232.84 233.84 234.83 235.83 236.82 237.82 238.81
3.0% 213.09 214.10 215.11 216.12 217.14 218.15 219.16 220.17 221.18 222.19 223.20 224.21 225.22 226.23 227.25 228.26 229.27 230.28 231.29 232.30 233.32 234.33 235.34 236.35 237.36 238.38 239.39 240.40 241.41 242.43 243.44 244.45
5.0% 221.37 222.41 223.45 224.48 225.52 226.56 227.60 228.65 229.69 230.73 231.77 232.81 233.85 234.89 235.93 236.97 238.01 239.05 240.09 241.13 242.17 243.21 244.25 245.29 246.34 247.38 248.42 249.46 250.50 251.54 252.58 253.62
222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253
B-8
June 2001
Channels N 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285
0.1% 215.65 216.58 217.51 218.44 219.37 220.31 221.24 222.17 223.10 224.04 224.97 225.90 226.83 227.77 228.70 229.64 230.57 231.50 232.44 233.37 234.31 235.24 236.17 237.11 238.04 238.98 239.92 240.85 241.79 242.72 243.66 244.59
0.15% 217.99 218.93 219.87 220.81 221.74 222.68 223.62 224.56 225.50 226.44 227.37 228.31 229.25 230.19 231.13 232.07 233.01 233.95 234.89 235.83 236.77 237.71 238.65 239.59 240.53 241.47 242.41 243.35 244.30 245.24 246.18 247.12
0.2% 219.77 220.71 221.65 222.59 223.54 224.48 225.42 226.36 227.31 228.25 229.19 230.14 231.08 232.02 232.97 233.91 234.86 235.80 236.74 237.69 238.63 239.58 240.52 241.47 242.41 243.36 244.30 245.25 246.19 247.14 248.09 249.03
0.3% 222.45 223.40 224.35 225.30 226.24 227.19 228.14 229.09 230.04 230.99 231.94 232.89 233.84 234.79 235.74 236.69 237.64 238.60 239.55 240.50 241.45 242.40 243.35 244.30 245.26 246.21 247.16 248.11 249.06 250.02 250.97 251.92
0.5% 226.20 227.16 228.11 229.07 230.03 230.99 231.95 232.91 233.87 234.83 235.79 236.75 237.71 238.67 239.63 240.59 241.55 242.51 243.47 244.43 245.39 246.35 247.31 248.27 249.24 250.20 251.16 252.12 253.08 254.04 255.00 255.97
1.0% 232.19 233.17 234.14 235.12 236.09 237.07 238.04 239.02 239.99 240.97 241.95 242.92 243.90 244.87 245.85 246.82 247.80 248.78 249.75 250.73 251.71 252.68 253.66 254.64 255.61 256.59 257.57 258.54 259.52 260.50 261.48 262.45
1.5% 236.39 237.38 238.37 239.35 240.34 241.33 242.31 243.30 244.29 245.27 246.26 247.25 248.24 249.22 250.21 251.20 252.19 253.17 254.16 255.15 256.14 257.13 258.11 259.10 260.09 261.08 262.07 263.06 264.04 265.03 266.02 267.01
2.0% 239.81 240.81 241.80 242.80 243.80 244.79 245.79 246.78 247.78 248.78 249.77 250.77 251.77 252.77 253.76 254.76 255.76 256.75 257.75 258.75 259.75 260.74 261.74 262.74 263.74 264.74 265.73 266.73 267.73 268.73 269.73 270.72
3.0% 245.47 246.48 247.49 248.50 249.52 250.53 251.54 252.56 253.57 254.58 255.60 256.61 257.62 258.64 259.65 260.66 261.68 262.69 263.71 264.72 265.73 266.75 267.76 268.78 269.79 270.80 271.82 272.83 273.85 274.86 275.88 276.89
5.0% 254.67 255.71 256.75 257.79 258.83 259.87 260.91 261.96 263.00 264.04 265.08 266.12 267.17 268.21 269.25 270.29 271.33 272.38 273.42 274.46 275.50 276.55 277.59 278.63 279.67 280.72 281.76 282.80 283.84 284.89 285.93 286.97
June 2001
B-9
Channels N
0.1% 245.53 246.47 247.40 248.34 249.28 250.21 251.15 252.09 253.02 253.96 254.90 255.84 256.77 257.71 258.65 305.70 352.99 400.49 448.16 495.97 543.90 591.94 640.07 688.28 736.57 784.92 833.33 881.80 930.33 978.89
0.15% 248.06 249.00 249.95 250.89 251.83 252.77 253.72 254.66 255.60 256.54 257.49 258.43 259.37 260.32 261.26 308.58 356.13 403.87 451.77 499.80 547.94 596.19 644.52 692.93 741.40 789.94 838.54 887.19 935.88 984.62
0.2% 249.98 250.92 251.87 252.82 253.76 254.71 255.66 256.60 257.55 258.50 259.44 260.39 261.34 262.29 263.23 310.76 358.50 406.43 454.50 502.70 551.01 599.42 647.90 696.46 745.09 793.77 842.51 891.29 940.13 989.00
0.3% 252.87 253.83 254.78 255.73 256.69 257.64 258.59 259.55 260.50 261.45 262.41 263.36 264.31 265.27 266.22 314.06 362.10 410.31 458.66 507.12 555.68 604.33 653.06 701.85 750.71 799.61 848.57 897.57 946.61 995.69
0.5% 256.93 257.89 258.85 259.82 260.78 261.74 262.70 263.67 264.63 265.59 266.55 267.52 268.48 269.44 270.41 318.69 367.16 415.78 464.52 513.36 562.29 611.30 660.37 709.51 758.69 807.92 857.20 906.51 955.86
1.0% 263.43 264.41 265.39 266.36 267.34 268.32 269.30 270.28 271.25 272.23 273.21 274.19 275.17 276.15 277.13 326.15 375.33 424.63 474.04 523.52 573.08 622.69 672.36 722.08 771.84 821.63 871.46 921.32 971.20
1.5% 268.00 268.99 269.98 270.97 271.96 272.94 273.93 274.92 275.91 276.90 277.89 278.88 279.87 280.86 281.85 331.42 381.13 430.94 480.83 530.79 580.82 630.89 681.01 731.17 781.36 831.59 881.84 932.12 982.42
2.0% 271.72 272.72 273.72 274.72 275.72 276.72 277.71 278.71 279.71 280.71 281.71 282.71 283.71 284.71 285.71 335.74 385.89 436.13 486.44 536.81 587.24 637.71 688.22 738.76 789.33 839.93 890.55 941.19 991.85
3.0% 277.91 278.92 279.93 280.95 281.96 282.98 283.99 285.01 286.02 287.04 288.05 289.07 290.09 291.10 292.12 342.94 393.86 444.85 495.90 547.00 598.13 649.30 700.50 751.73 802.97 854.24 905.53 956.83
5.0% 288.01 289.06 290.10 291.14 292.18 293.23 294.27 295.31 296.36 297.40 298.44 299.49 300.53 301.57 302.62 354.82 407.08 459.40 511.75 564.14 616.55 668.98 721.43 773.89 826.37 878.86 931.36 983.87
286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 350 400 450 500 550 600 650 700 750 800 850 900 950 1000 1050 1100 1150
1008.14 1036.39
1027.50 1033.40 1037.91 1044.81 1054.66 1071.05 1083.08 1093.23 1110.80 1141.45 1076.16 1082.22 1086.85 1093.95 1104.10 1121.01 1133.43 1143.94 1162.15 1193.99 ... continued on next page
B-10
June 2001
Channels N 1200 1250 1300 1350 1400 1450 1500 1550 1600 1650 1700 1750 1800 1850 1900 1950 2000 2050 2100 2150 2200 2250 2300 2350 2400 2450 2500 2550 2600 2650 2700 2750
0.1%
0.15%
0.2%
0.3%
0.5%
1.0%
1.5%
2.0%
3.0%
5.0%
1124.85 1131.07 1135.83 1143.13 1153.57 1170.98 1183.81 1194.66 1213.51 1246.53 1173.57 1179.96 1184.84 1192.33 1203.06 1220.98 1234.19 1245.39 1264.87 1299.08 1222.33 1228.87 1233.88 1241.56 1252.57 1270.99 1284.59 1296.14 1316.25 1351.63 1271.12 1277.82 1282.95 1290.81 1302.10 1321.02 1335.01 1346.89 1367.63 1404.19 1319.93 1326.79 1332.04 1340.09 1351.66 1371.06 1385.43 1397.66 1419.02 1456.75 1368.78 1375.79 1381.15 1389.39 1401.23 1421.12 1435.87 1448.44 1470.42 1509.31 1417.65 1424.81 1430.29 1438.71 1450.82 1471.19 1486.32 1499.22 1521.82 1561.88 1466.55 1473.85 1479.45 1488.05 1500.43 1521.27 1536.78 1550.01 1573.22 1614.45 1515.47 1522.91 1528.62 1537.40 1550.05 1571.36 1587.24 1600.81 1624.64 1667.02 1564.41 1572.00 1577.82 1586.78 1599.69 1621.47 1637.72 1651.62 1676.05 1719.59 1613.37 1621.10 1627.04 1636.17 1649.34 1671.58 1688.20 1702.43 1727.48 1772.17 1662.35 1670.23 1676.27 1685.58 1699.00 1721.71 1738.70 1753.25 1778.90 1824.75 1711.35 1719.37 1725.52 1735.00 1748.68 1771.84 1789.20 1804.08 1830.33 1877.33 1760.37 1768.53 1774.79 1784.43 1798.37 1821.99 1839.70 1854.91 1881.77 1929.92 1809.41 1817.70 1824.07 1833.88 1848.07 1872.14 1890.22 1905.75 1933.21 1982.50 1858.46 1866.89 1873.36 1883.34 1897.78 1922.30 1940.74 1956.59 1984.65 2035.09 1907.54 1916.10 1922.67 1932.82 1947.50 1972.47 1991.26 2007.44 2036.09 2087.68 1956.62 1965.31 1972.00 1982.31 1997.24 2022.65 2041.79 2058.29 2087.54 2140.27 2005.72 2014.55 2021.33 2031.81 2046.98 2072.83 2092.33 2109.15 2138.99 2192.86 2054.84 2063.79 2070.68 2081.31 2096.73 2123.02 2142.87 2160.01 2190.44 2245.46 2103.97 2113.05 2120.04 2130.84 2146.49 2173.22 2193.42 2210.87 2241.90 2298.05 2153.11 2162.32 2169.41 2180.37 2196.26 2223.42 2243.97 2261.74 2293.36 2350.65 2202.27 2211.61 2218.79 2229.91 2246.04 2273.63 2294.53 2312.61 2344.82 2403.24 2251.43 2260.90 2268.19 2279.46 2295.82 2323.84 2345.09 2363.49 2396.28 2455.84 2300.61 2310.21 2317.59 2329.02 2345.62 2374.06 2395.66 2414.37 2447.75 2508.44 2349.80 2359.52 2367.00 2378.58 2395.42 2424.29 2446.23 2465.25 2499.22 2561.04 2399.01 2408.85 2416.43 2428.16 2445.23 2474.52 2496.80 2516.14 2550.69 2613.64 2448.22 2458.18 2465.86 2477.75 2495.04 2524.76 2547.38 2567.02 2602.16 2666.25 2497.44 2507.53 2515.30 2527.34 2544.87 2575.00 2597.96 2617.92 2653.63 2718.85 2546.68 2556.88 2564.75 2576.94 2594.69 2625.24 2648.55 2668.81 2705.11 2771.45 2595.92 2606.25 2614.21 2626.55 2644.53 2675.49 2699.14 2719.71 2756.59 2824.06 2645.18 2655.62 2663.68 2676.16 2694.37 2725.75 2749.73 2770.61 2808.07 2876.66 ... continued on next page
June 2001
B-11
Channels N
0.1%
0.15%
0.2%
0.3%
0.5%
1.0%
1.5%
2.0%
3.0%
5.0%
2800 2850 2900 2950 3000 3050 3100 3150 3200 3250 3300 3350 3400 3450 3500 3550 3600 3650 3700 3750 3800 3850 3900 3950 4000
2694.44 2705.00 2713.15 2725.79 2744.22 2776.01 2800.32 2821.51 2859.55 2929.27 2743.71 2754.39 2762.63 2775.42 2794.07 2826.27 2850.92 2872.41 2911.03 2981.87 2792.99 2803.79 2812.12 2825.05 2843.93 2876.54 2901.52 2923.32 2962.51 3034.48 2842.28 2853.20 2861.62 2874.69 2893.79 2926.81 2952.13 2974.23 3014.00 3087.09 2891.58 2902.61 2911.12 2924.34 2943.66 2977.08 3002.73 3025.14 3065.48 3139.70 2940.88 2952.03 2960.64 2974.00 2993.54 3027.36 3053.34 3076.05 3116.97 3192.31 2990.20 3001.46 3010.15 3023.66 3043.41 3077.64 3103.95 3126.97 3168.46 3244.92 3039.52 3050.89 3059.68 3073.33 3093.30 3127.93 3154.57 3177.89 3219.95 3297.53 3088.85 3100.33 3109.21 3123.00 3143.19 3178.22 3205.19 3228.81 3271.44 3350.14 3138.18 3149.78 3158.75 3172.68 3193.08 3228.51 3255.81 3279.73 3322.93 3402.75 3187.53 3199.24 3208.29 3222.36 3242.98 3278.80 3306.43 3330.65 3374.43 3455.36 3236.88 3248.70 3257.84 3272.05 3292.88 3329.10 3357.05 3381.57 3425.92 3507.98 3286.23 3298.17 3307.39 3321.74 3342.79 3379.40 3407.68 3432.50 3477.42 3560.59 3335.60 3347.64 3356.95 3371.44 3392.70 3429.70 3458.31 3483.43 3528.91 3613.20 3384.97 3397.12 3406.52 3421.15 3442.61 3480.01 3508.94 3534.36 3580.41 3665.82 3434.34 3446.60 3456.09 3470.86 3492.53 3530.32 3559.57 3585.29 3631.91 3718.43 3483.73 3496.09 3505.67 3520.57 3542.45 3580.63 3610.21 3636.22 3683.41 3771.04 3533.12 3545.59 3555.25 3570.29 3592.38 3630.94 3660.84 3687.15 3734.91 3823.66 3582.51 3595.09 3604.83 3620.01 3642.31 3681.26 3711.48 3738.09 3786.41 3876.27 3631.91 3644.60 3654.43 3669.73 3692.24 3731.58 3762.12 3789.03 3837.91 3928.89 3681.32 3694.11 3704.02 3719.47 3742.18 3781.90 3812.76 3839.96 3889.42 3981.51 3730.73 3743.63 3753.62 3769.20 3792.12 3832.23 3863.41 3890.90 3940.92 4034.12 3780.14 3793.15 3803.23 3818.94 3842.06 3882.55 3914.05 3941.84 3992.42 4086.74 3829.57 3842.68 3852.84 3868.68 3892.01 3932.88 3964.70 3992.79 4043.93 4139.36 3878.99 3892.21 3902.45 3918.43 3941.96 3983.21 4015.35 4043.73 4095.44 4191.97
B-12
June 2001
Table B-2: Erlang B Spans Spans 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 T1 Circuits 24 48 72 96 120 144 168 192 216 240 264 288 312 336 360 384 408 432 456 480 504 528 552 576 600 624 648 672 696 720 T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 12.24 30.88 50.94 71.73 92.96 114.51 136.30 158.27 180.38 202.62 224.97 247.40 269.91 292.50 315.14 337.83 360.58 383.37 406.21 429.08 451.98 474.92 497.88 520.88 543.90 566.94 590.01 613.10 636.21 659.34 13.01 32.20 52.72 73.90 95.48 117.36 139.45 161.70 184.10 206.60 229.19 251.87 274.62 297.43 320.29 343.20 366.16 389.15 412.19 435.26 458.35 481.48 504.63 527.81 551.01 574.24 597.48 620.74 644.02 667.32 13.51 33.06 53.87 75.30 97.12 119.20 141.49 163.94 186.51 209.18 231.94 254.78 277.68 300.64 323.65 346.71 369.80 392.94 416.10 439.30 462.53 485.78 509.06 532.36 555.68 579.03 602.39 625.77 649.16 672.57 E1 Circuits 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450 480 510 540 570 600 630 660 690 720 750 780 810 840 870 900 E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 16.68 40.79 66.48 92.96 119.94 147.26 174.84 202.62 230.57 258.65 286.84 315.14 343.52 371.97 400.49 429.08 457.71 486.40 515.13 543.90 572.71 601.55 630.43 659.34 688.28 717.24 746.23 775.24 804.28 833.33 17.61 42.35 68.56 95.48 122.86 150.56 178.49 206.60 234.86 263.23 291.72 320.29 348.94 377.65 406.43 435.26 464.13 493.05 522.01 551.01 580.04 609.11 638.20 667.32 696.46 725.63 754.82 784.03 813.26 842.51 18.20 43.36 69.90 97.12 124.76 152.70 180.85 209.18 237.64 266.22 294.90 323.65 352.48 381.37 410.31 439.30 468.34 497.42 526.54 555.68 584.86 614.07 643.31 672.57 701.85 731.16 760.48 789.83 819.19 848.57
June 2001
B-13
Spans
T1 Circuits 744 768 792 816 840 864 888 912 936 960 984 1008 1032 1056 1080 1104 1128 1152 1176 1200 1224 1248 1272 1296 1320 1344 1368 1392 1416 1440 1464 1488
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 682.49 705.65 728.83 752.03 775.24 798.47 821.71 844.96 868.23 891.50 914.79 938.09 961.40 984.72 1008.06 1031.40 1054.75 1078.10 1101.47 1124.85 1148.23 1171.62 1195.02 1218.43 1241.84 1265.26 1288.69 1312.12 1335.56 1359.01 1382.46 1405.92 690.63 713.96 737.30 760.66 784.03 807.41 830.81 854.21 877.63 901.06 924.50 947.94 971.40 994.87 1018.34 1041.82 1065.31 1088.81 1112.32 1135.83 1159.35 1182.88 1206.42 1229.96 1253.50 1277.06 1300.62 1324.18 1347.75 1371.33 1394.91 1418.49 695.99 719.43 742.89 766.35 789.83 813.32 836.82 860.33 883.85 907.38 930.91 954.46 978.02 1001.58 1025.16 1048.74 1072.32 1095.92 1119.52 1143.13 1166.74 1190.36 1213.99 1237.62 1261.26 1284.90 1308.55 1332.21 1355.86 1379.53 1403.20 1426.87
E1 Circuits 930 960 990 1020 1050 1080 1110 1140 1170 1200 1230 1260 1290 1320 1350 1380 1410 1440 1470 1500 1530 1560 1590 1620 1650 1680 1710 1740 1770 1800 1830 1860
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 862.41 891.50 920.62 949.75 978.89 1008.06 1037.23 1066.42 1095.63 1124.85 1154.08 1183.32 1212.57 1241.84 1271.12 1300.40 1329.70 1359.01 1388.33 1417.65 1446.99 1476.33 1505.68 1535.04 1564.41 1593.78 1623.16 1652.55 1681.95 1711.35 1740.76 1770.18 871.77 901.06 930.36 959.67 989.00 1018.34 1047.69 1077.06 1106.44 1135.83 1165.24 1194.65 1224.07 1253.50 1282.95 1312.40 1341.86 1371.33 1400.80 1430.29 1459.78 1489.28 1518.79 1548.30 1577.82 1607.35 1636.88 1666.42 1695.97 1725.52 1755.08 1784.64 877.97 907.38 936.80 966.24 995.69 1025.16 1054.63 1084.12 1113.62 1143.13 1172.65 1202.17 1231.71 1261.26 1290.81 1320.38 1349.95 1379.53 1409.12 1438.71 1468.31 1497.92 1527.53 1557.15 1586.78 1616.41 1646.05 1675.69 1705.34 1735.00 1764.66 1794.32
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62
B-14
June 2001
Spans 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94
T1 Circuits 1512 1536 1560 1584 1608 1632 1656 1680 1704 1728 1752 1776 1800 1824 1848 1872 1896 1920 1944 1968 1992 2016 2040 2064 2088 2112 2136 2160 2184 2208 2232 2256
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 1429.38 1452.85 1476.33 1499.81 1523.29 1546.79 1570.28 1593.78 1617.29 1640.80 1664.31 1687.83 1711.35 1734.88 1758.41 1781.95 1805.49 1829.03 1852.58 1876.13 1899.68 1923.24 1946.80 1970.37 1993.94 2017.51 2041.08 2064.66 2088.24 2111.83 2135.42 2159.01 1442.08 1465.68 1489.28 1512.88 1536.49 1560.11 1583.73 1607.35 1630.98 1654.61 1678.24 1701.88 1725.52 1749.17 1772.82 1796.47 1820.12 1843.78 1867.45 1891.11 1914.78 1938.45 1962.13 1985.81 2009.49 2033.17 2056.86 2080.55 2104.24 2127.94 2151.64 2175.34 1450.55 1474.23 1497.92 1521.61 1545.30 1569.00 1592.70 1616.41 1640.12 1663.84 1687.55 1711.27 1735.00 1758.72 1782.46 1806.19 1829.93 1853.67 1877.41 1901.15 1924.90 1948.65 1972.41 1996.17 2019.92 2043.69 2067.45 2091.22 2114.99 2138.76 2162.53 2186.31
E1 Circuits 1890 1920 1950 1980 2010 2040 2070 2100 2130 2160 2190 2220 2250 2280 2310 2340 2370 2400 2430 2460 2490 2520 2550 2580 2610 2640 2670 2700 2730 2760 2790 2820
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 1799.60 1829.03 1858.46 1887.91 1917.35 1946.80 1976.26 2005.72 2035.19 2064.66 2094.14 2123.62 2153.11 2182.60 2212.10 2241.60 2271.10 2300.61 2330.13 2359.64 2389.17 2418.69 2448.22 2477.75 2507.29 2536.83 2566.37 2595.92 2625.47 2655.03 2684.59 2714.15 1814.21 1843.78 1873.36 1902.95 1932.54 1962.13 1991.73 2021.33 2050.94 2080.55 2110.17 2139.79 2169.41 2199.04 2228.67 2258.31 2287.95 2317.59 2347.24 2376.89 2406.54 2436.20 2465.86 2495.52 2525.19 2554.86 2584.53 2614.21 2643.89 2673.57 2703.26 2732.94 1823.99 1853.67 1883.34 1913.03 1942.72 1972.41 2002.10 2031.81 2061.51 2091.22 2120.93 2150.65 2180.37 2210.09 2239.82 2269.55 2299.28 2329.02 2358.76 2388.50 2418.24 2447.99 2477.75 2507.50 2537.26 2567.02 2596.78 2626.55 2656.32 2686.09 2715.86 2745.64
June 2001
B-15
Spans
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 2182.60 2206.20 2229.80 2253.40 2277.00 2300.61 2199.04 2222.74 2246.45 2270.16 2293.88 2317.59 2210.09 2233.87 2257.65 2281.44 2305.23 2329.02
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 2743.71 2773.28 2802.85 2832.42 2862.00 2891.58 2762.63 2792.33 2822.02 2851.72 2881.42 2911.12 2775.42 2805.20 2834.98 2864.77 2894.55 2924.34
95 96 97 98 99 100
B-16
June 2001
C
Erlang C Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking Erlangs using the Erlang C Model . . . . . . . . . . . . . . . . . . . . . Erlang C Table for T1/E1 Spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 C-1 C-13
June 2001
Table of Contents
continued
Notes
June 2001
Table C-1: Erlangs per Blocking Channels N 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 0.1% 0.00 0.05 0.19 0.43 0.73 1.10 1.51 1.96 2.44 2.94 3.47 4.02 4.58 5.17 5.76 6.37 6.99 7.62 8.26 8.91 9.57 10.24 10.91 11.59 12.28 12.97 13.67 14.38 15.09 0.15% 0.00 0.06 0.22 0.48 0.80 1.19 1.62 2.09 2.58 3.11 3.65 4.22 4.80 5.40 6.01 6.63 7.26 7.91 8.56 9.23 9.90 10.58 11.26 11.96 12.65 13.36 14.07 14.79 15.51 0.2% 0.00 0.06 0.24 0.51 0.86 1.26 1.71 2.19 2.70 3.23 3.79 4.37 4.96 5.57 6.19 6.82 7.47 8.12 8.79 9.46 10.14 10.83 11.52 12.22 12.93 13.65 14.36 15.09 15.82 0.3% 0.00 0.08 0.28 0.58 0.94 1.37 1.83 2.34 2.87 3.42 4.00 4.59 5.20 5.82 6.46 7.11 7.77 8.44 9.12 9.81 10.50 11.20 11.91 12.62 13.34 14.07 14.80 15.53 16.28 0.5% 0.00 0.10 0.33 0.66 1.07 1.52 2.01 2.54 3.10 3.68 4.28 4.90 5.53 6.17 6.83 7.50 8.18 8.87 9.57 10.27 10.98 11.70 12.43 13.16 13.90 14.64 15.38 16.14 16.89 1.0% 0.01 0.15 0.43 0.81 1.26 1.76 2.30 2.87 3.46 4.08 4.71 5.36 6.03 6.71 7.39 8.09 8.80 9.52 10.24 10.97 11.71 12.46 13.21 13.96 14.72 15.49 16.26 17.03 17.81 1.5% 0.01 0.18 0.50 0.91 1.39 1.92 2.49 3.08 3.70 4.34 5.00 5.67 6.35 7.05 7.76 8.48 9.20 9.94 10.68 11.42 12.18 12.94 13.70 14.47 15.25 16.03 16.81 17.60 18.39 2.0% 0.02 0.21 0.55 0.99 1.50 2.05 2.63 3.25 3.88 4.54 5.21 5.90 6.60 7.31 8.04 8.77 9.51 10.25 11.01 11.77 12.53 13.30 14.08 14.86 15.65 16.44 17.23 18.03 18.83 3.0% 0.03 0.26 0.65 1.12 1.66 2.24 2.86 3.50 4.17 4.85 5.55 6.26 6.98 7.71 8.46 9.21 9.97 10.73 11.50 12.28 13.07 13.85 14.65 15.45 16.25 17.05 17.86 18.68 19.49 5.0% 0.05 0.34 0.79 1.32 1.91 2.53 3.19 3.87 4.57 5.29 6.02 6.76 7.51 8.27 9.04 9.82 10.61 11.40 12.20 13.00 13.81 14.62 15.43 16.25 17.08 17.91 18.74 19.57 20.41
Channels N 30 31 32 33
0.1% 15.80 16.52 17.25 17.97 18.71 19.44 20.18 20.92 21.67 22.42 23.17 23.93 24.69 25.45 26.22 26.98 27.75 28.52 29.30 30.08 30.86 31.64 32.42 33.21 33.99 34.78 35.57 36.37 37.16 37.96 38.76 39.56
0.15% 16.23 16.96 17.70 18.43 19.18 19.92 20.67 21.42 22.18 22.94 23.70 24.47 25.24 26.01 26.78 27.56 28.33 29.12 29.90 30.68 31.47 32.26 33.05 33.85 34.64 35.44 36.24 37.04 37.84 38.65 39.45 40.26
0.2% 16.55 17.29 18.03 18.78 19.52 20.28 21.03 21.79 22.56 23.32 24.09 24.87 25.64 26.42 27.20 27.98 28.77 29.55 30.34 31.13 31.93 32.72 33.52 34.32 35.12 35.93 36.73 37.54 38.35 39.16 39.97 40.78
0.3% 17.02 17.77 18.52 19.28 20.04 20.80 21.57 22.34 23.11 23.89 24.67 25.45 26.24 27.02 27.81 28.60 29.40 30.19 30.99 31.79 32.60 33.40 34.21 35.02 35.83 36.64 37.45 38.27 39.08 39.90 40.72 41.54
0.5% 17.65 18.41 19.18 19.95 20.73 21.51 22.29 23.07 23.86 24.65 25.44 26.23 27.03 27.83 28.63 29.44 30.24 31.05 31.86 32.67 33.49 34.31 35.12 35.94 36.76 37.59 38.41 39.24 40.07 40.90 41.73 42.56
1.0% 18.59 19.37 20.16 20.95 21.75 22.55 23.35 24.15 24.96 25.77 26.58 27.39 28.21 29.02 29.84 30.67 31.49 32.32 33.14 33.97 34.80 35.64 36.47 37.31 38.15 38.98 39.83 40.67 41.51 42.36 43.20 44.05
1.5% 19.19 19.99 20.79 21.59 22.40 23.21 24.02 24.84 25.66 26.48 27.30 28.12 28.95 29.78 30.61 31.45 32.28 33.12 33.96 34.80 35.64 36.48 37.33 38.17 39.02 39.87 40.72 41.57 42.42 43.28 44.13 44.99
2.0% 19.64 20.45 21.26 22.07 22.89 23.71 24.53 25.35 26.18 27.01 27.84 28.68 29.51 30.35 31.19 32.03 32.87 33.72 34.56 35.41 36.26 37.11 37.97 38.82 39.67 40.53 41.39 42.25 43.11 43.97 44.83 45.70
3.0% 20.31 21.14 21.96 22.79 23.62 24.45 25.29 26.13 26.97 27.81 28.66 29.50 30.35 31.20 32.05 32.90 33.76 34.62 35.47 36.33 37.19 38.06 38.92 39.78 40.65 41.52 42.39 43.26 44.13 45.00 45.87 46.75
5.0% 21.25 22.09 22.93 23.78 24.63 25.48 26.33 27.19 28.05 28.91 29.77 30.63 31.50 32.36 33.23 34.10 34.97 35.84 36.72 37.59 38.47 39.35 40.22 41.10 41.99 42.87 43.75 44.63 45.52 46.41 47.29 48.18
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
C-2
June 2001
Channels N 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
0.1% 40.36 41.16 41.97 42.77 43.58 44.39 45.20 46.01 46.83 47.64 48.46 49.28 50.10 50.91 51.74 52.56 53.38 54.21 55.03 55.86 56.69 57.51 58.34 59.18 60.01 60.84 61.67 62.51 63.34 64.18 65.02 65.86
0.15% 41.07 41.88 42.69 43.51 44.32 45.14 45.96 46.78 47.60 48.42 49.24 50.07 50.89 51.72 52.55 53.38 54.21 55.04 55.87 56.70 57.54 58.37 59.21 60.05 60.89 61.72 62.56 63.41 64.25 65.09 65.93 66.78
0.2% 41.60 42.41 43.23 44.05 44.87 45.69 46.52 47.34 48.17 48.99 49.82 50.65 51.48 52.31 53.15 53.98 54.81 55.65 56.49 57.33 58.17 59.01 59.85 60.69 61.53 62.37 63.22 64.07 64.91 65.76 66.61 67.46
0.3% 42.37 43.19 44.02 44.84 45.67 46.50 47.33 48.16 49.00 49.83 50.67 51.50 52.34 53.18 54.02 54.86 55.70 56.55 57.39 58.24 59.08 59.93 60.78 61.63 62.48 63.33 64.18 65.03 65.88 66.74 67.59 68.45
0.5% 43.39 44.23 45.06 45.90 46.74 47.58 48.42 49.26 50.10 50.95 51.79 52.64 53.49 54.34 55.19 56.04 56.89 57.74 58.59 59.45 60.30 61.16 62.02 62.88 63.73 64.59 65.45 66.32 67.18 68.04 68.90 69.77
1.0% 44.90 45.75 46.60 47.45 48.30 49.16 50.01 50.87 51.73 52.59 53.45 54.31 55.17 56.03 56.89 57.76 58.62 59.49 60.36 61.22 62.09 62.96 63.83 64.70 65.57 66.45 67.32 68.19 69.07 69.94 70.82 71.70
1.5% 45.85 46.71 47.57 48.43 49.29 50.16 51.02 51.89 52.75 53.62 54.49 55.36 56.23 57.10 57.97 58.84 59.72 60.59 61.47 62.34 63.22 64.10 64.97 65.85 66.73 67.61 68.49 69.38 70.26 71.14 72.02 72.91
2.0% 46.56 47.43 48.29 49.16 50.03 50.90 51.77 52.65 53.52 54.39 55.27 56.14 57.02 57.90 58.77 59.65 60.53 61.41 62.30 63.18 64.06 64.94 65.83 66.71 67.60 68.48 69.37 70.26 71.15 72.04 72.92 73.81
3.0% 47.62 48.50 49.38 50.25 51.13 52.01 52.89 53.78 54.66 55.54 56.43 57.31 58.20 59.08 59.97 60.86 61.75 62.64 63.53 64.42 65.31 66.20 67.10 67.99 68.88 69.78 70.67 71.57 72.47 73.36 74.26 75.16
5.0% 49.07 49.96 50.85 51.74 52.63 53.53 54.42 55.32 56.21 57.11 58.01 58.90 59.80 60.70 61.60 62.50 63.40 64.30 65.21 66.11 67.01 67.92 68.82 69.73 70.63 71.54 72.45 73.35 74.26 75.17 76.08 76.99
June 2001
C-3
Channels N 94 95 96 97
0.1% 66.70 67.54 68.38 69.22 70.06 70.90 71.75 72.59 73.44 74.28 75.13 75.98 76.83 77.68 78.53 79.38 80.23 81.08 81.93 82.79 83.64 84.49 85.35 86.21 87.06 87.92 88.78 89.64 90.49 91.35 92.21 93.07
0.15% 67.62 68.47 69.32 70.16 71.01 71.86 72.71 73.56 74.41 75.27 76.12 76.97 77.83 78.68 79.54 80.39 81.25 82.11 82.97 83.83 84.69 85.55 86.41 87.27 88.13 88.99 89.86 90.72 91.58 92.45 93.31 94.18
0.2% 68.31 69.16 70.01 70.86 71.71 72.57 73.42 74.28 75.13 75.99 76.85 77.70 78.56 79.42 80.28 81.14 82.00 82.86 83.73 84.59 85.45 86.32 87.18 88.05 88.91 89.78 90.65 91.51 92.38 93.25 94.12 94.99
0.3% 69.30 70.16 71.02 71.88 72.74 73.60 74.46 75.32 76.18 77.04 77.91 78.77 79.64 80.50 81.37 82.23 83.10 83.97 84.84 85.71 86.58 87.45 88.32 89.19 90.06 90.93 91.81 92.68 93.55 94.43 95.30 96.18
0.5% 70.63 71.50 72.36 73.23 74.10 74.97 75.84 76.71 77.58 78.45 79.32 80.19 81.06 81.94 82.81 83.68 84.56 85.44 86.31 87.19 88.07 88.94 89.82 90.70 91.58 92.46 93.34 94.22 95.10 95.99 96.87 97.75
1.0% 72.57 73.45 74.33 75.21 76.09 76.97 77.85 78.73 79.61 80.50 81.38 82.26 83.15 84.03 84.92 85.80 86.69 87.58 88.46 89.35 90.24 91.13 92.02 92.91 93.80 94.69 95.58 96.47 97.37 98.26 99.15 100.05
1.5% 73.79 74.68 75.57 76.45 77.34 78.23 79.12 80.00 80.89 81.78 82.67 83.57 84.46 85.35 86.24 87.13 88.03 88.92 89.82 90.71 91.61 92.50 93.40 94.30 95.19 96.09 96.99 97.89 98.79 99.69 100.59 101.49
2.0% 74.70 75.60 76.49 77.38 78.27 79.17 80.06 80.95 81.85 82.74 83.64 84.54 85.43 86.33 87.23 88.13 89.03 89.93 90.83 91.73 92.63 93.53 94.43 95.33 96.23 97.14 98.04 98.94 99.85 100.75 101.66 102.56
3.0% 76.06 76.96 77.86 78.76 79.66 80.56 81.46 82.37 83.27 84.17 85.08 85.98 86.88 87.79 88.70 89.60 90.51 91.41 92.32 93.23 94.14 95.05 95.96 96.87 97.78 98.69 99.60 100.51 101.42 102.33 103.24 104.15
5.0% 77.90 78.81 79.72 80.63 81.54 82.46 83.37 84.28 85.20 86.11 87.02 87.94 88.85 89.77 90.69 91.60 92.52 93.44 94.35 95.27 96.19 97.11 98.03 98.95 99.87 100.79 101.71 102.63 103.55 104.47 105.39 106.31
98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125
C-4
June 2001
Channels N 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157
0.1% 93.94 94.80 95.66 96.52 97.38 98.25 99.11 99.98 100.84 101.71 102.58 103.44 104.31 105.18 106.05 106.91 107.78 108.65 109.52 110.39 111.26 112.14 113.01 113.88 114.75 115.63 116.50 117.37 118.25 119.12 120.00 120.87
0.15% 95.05 95.91 96.78 97.65 98.52 99.39 100.25 101.12 102.00 102.87 103.74 104.61 105.48 106.35 107.23 108.10 108.98 109.85 110.73 111.60 112.48 113.35 114.23 115.11 115.98 116.86 117.74 118.62 119.50 120.38 121.26 122.14
0.2% 95.86 96.73 97.60 98.48 99.35 100.22 101.09 101.97 102.84 103.72 104.59 105.47 106.34 107.22 108.10 108.97 109.85 110.73 111.61 112.49 113.37 114.25 115.13 116.01 116.89 117.77 118.65 119.54 120.42 121.30 122.18 123.07
0.3% 97.05 97.93 98.81 99.68 100.56 101.44 102.32 103.20 104.08 104.96 105.84 106.72 107.60 108.48 109.37 110.25 111.13 112.02 112.90 113.78 114.67 115.55 116.44 117.32 118.21 119.10 119.98 120.87 121.76 122.65 123.54 124.43
0.5% 98.63 99.52 100.40 101.29 102.17 103.06 103.94 104.83 105.72 106.60 107.49 108.38 109.27 110.16 111.05 111.94 112.83 113.72 114.61 115.50 116.39 117.28 118.18 119.07 119.96 120.85 121.75 122.64 123.54 124.43 125.33 126.22
1.0% 100.94 101.83 102.73 103.62 104.52 105.42 106.31 107.21 108.11 109.00 109.90 110.80 111.70 112.60 113.50 114.40 115.30 116.20 117.10 118.00 118.90 119.80 120.71 121.61 122.51 123.41 124.32 125.22 126.13 127.03 127.94 128.84
1.5% 102.39 103.29 104.19 105.09 105.99 106.90 107.80 108.70 109.61 110.51 111.41 112.32 113.22 114.13 115.04 115.94 116.85 117.75 118.66 119.57 120.48 121.39 122.29 123.20 124.11 125.02 125.93 126.84 127.75 128.66 129.57 130.48
2.0% 103.47 104.37 105.28 106.18 107.09 108.00 108.91 109.81 110.72 111.63 112.54 113.45 114.36 115.27 116.18 117.09 118.00 118.91 119.83 120.74 121.65 122.56 123.47 124.39 125.30 126.22 127.13 128.04 128.96 129.87 130.79 131.70
3.0% 105.07 105.98 106.89 107.81 108.72 109.64 110.55 111.46 112.38 113.30 114.21 115.13 116.04 116.96 117.88 118.80 119.71 120.63 121.55 122.47 123.39 124.31 125.23 126.15 127.07 127.99 128.91 129.83 130.75 131.67 132.59 133.51
5.0% 107.24 108.16 109.08 110.00 110.93 111.85 112.78 113.70 114.63 115.55 116.48 117.40 118.33 119.25 120.18 121.11 122.03 122.96 123.89 124.81 125.74 126.67 127.60 128.53 129.46 130.39 131.31 132.24 133.17 134.10 135.03 135.96
June 2001
C-5
0.1% 121.75 122.63 123.50 124.38 125.26 126.13 127.01 127.89 128.77 129.65 130.53 131.41 132.29 133.17 134.05 134.93 135.82 136.70 137.58 138.46 139.35 140.23 141.11 142.00 142.88 143.77 144.65 145.54 146.42 147.31 148.20 149.08
0.15% 123.02 123.90 124.78 125.66 126.55 127.43 128.31 129.20 130.08 130.96 131.85 132.73 133.62 134.50 135.39 136.27 137.16 138.05 138.93 139.82 140.71 141.60 142.49 143.37 144.26 145.15 146.04 146.93 147.82 148.71 149.60 150.49
0.2% 123.95 124.84 125.72 126.61 127.49 128.38 129.27 130.15 131.04 131.93 132.81 133.70 134.59 135.48 136.37 137.26 138.15 139.04 139.93 140.82 141.71 142.60 143.49 144.38 145.28 146.17 147.06 147.95 148.85 149.74 150.63 151.53
0.3% 125.31 126.20 127.09 127.98 128.88 129.77 130.66 131.55 132.44 133.33 134.23 135.12 136.01 136.91 137.80 138.69 139.59 140.48 141.38 142.27 143.17 144.07 144.96 145.86 146.75 147.65 148.55 149.45 150.34 151.24 152.14 153.04
0.5% 127.12 128.02 128.91 129.81 130.71 131.60 132.50 133.40 134.30 135.20 136.10 136.99 137.89 138.79 139.69 140.59 141.50 142.40 143.30 144.20 145.10 146.00 146.91 147.81 148.71 149.61 150.52 151.42 152.33 153.23 154.13 155.04
1.0% 129.75 130.65 131.56 132.46 133.37 134.28 135.18 136.09 137.00 137.91 138.82 139.72 140.63 141.54 142.45 143.36 144.27 145.18 146.09 147.00 147.91 148.82 149.74 150.65 151.56 152.47 153.38 154.30 155.21 156.12 157.03 157.95
1.5% 131.39 132.30 133.22 134.13 135.04 135.95 136.87 137.78 138.69 139.61 140.52 141.44 142.35 143.26 144.18 145.09 146.01 146.93 147.84 148.76 149.67 150.59 151.51 152.43 153.34 154.26 155.18 156.10 157.01 157.93 158.85 159.77
2.0% 132.62 133.53 134.45 135.37 136.28 137.20 138.12 139.04 139.95 140.87 141.79 142.71 143.63 144.55 145.46 146.38 147.30 148.22 149.14 150.06 150.98 151.91 152.83 153.75 154.67 155.59 156.51 157.43 158.36 159.28 160.20 161.13
3.0% 134.44 135.36 136.28 137.20 138.13 139.05 139.97 140.90 141.82 142.75 143.67 144.59 145.52 146.44 147.37 148.30 149.22 150.15 151.07 152.00 152.93 153.85 154.78 155.71 156.63 157.56 158.49 159.42 160.35 161.27 162.20 163.13
5.0% 136.90 137.83 138.76 139.69 140.62 141.55 142.48 143.42 144.35 145.28 146.21 147.15 148.08 149.01 149.95 150.88 151.81 152.75 153.68 154.62 155.55 156.49 157.42 158.36 159.29 160.23 161.16 162.10 163.04 163.97 164.91 165.84
162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189
C-6
June 2001
Channels N 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221
0.1% 149.97 150.86 151.74 152.63 153.52 154.41 155.30 156.19 157.07 157.96 158.85 159.74 160.63 161.53 162.42 163.31 164.20 165.09 165.98 166.87 167.77 168.66 169.55 170.45 171.34 172.23 173.13 174.02 174.92 175.81 176.70 177.60
0.15% 151.38 152.28 153.17 154.06 154.95 155.85 156.74 157.63 158.52 159.42 160.31 161.21 162.10 163.00 163.89 164.79 165.68 166.58 167.47 168.37 169.27 170.16 171.06 171.96 172.86 173.75 174.65 175.55 176.45 177.35 178.25 179.15
0.2% 152.42 153.32 154.21 155.11 156.00 156.90 157.80 158.69 159.59 160.49 161.38 162.28 163.18 164.08 164.97 165.87 166.77 167.67 168.57 169.47 170.37 171.27 172.17 173.07 173.97 174.87 175.77 176.67 177.57 178.47 179.38 180.28
0.3% 153.94 154.84 155.74 156.64 157.54 158.44 159.34 160.24 161.14 162.04 162.94 163.85 164.75 165.65 166.55 167.46 168.36 169.26 170.16 171.07 171.97 172.88 173.78 174.69 175.59 176.50 177.40 178.31 179.21 180.12 181.02 181.93
0.5% 155.94 156.85 157.76 158.66 159.57 160.47 161.38 162.29 163.19 164.10 165.01 165.92 166.82 167.73 168.64 169.55 170.46 171.37 172.28 173.19 174.10 175.01 175.92 176.83 177.74 178.65 179.56 180.47 181.38 182.29 183.20 184.12
1.0% 158.86 159.78 160.69 161.60 162.52 163.43 164.35 165.26 166.18 167.10 168.01 168.93 169.84 170.76 171.68 172.59 173.51 174.43 175.35 176.26 177.18 178.10 179.02 179.94 180.86 181.77 182.69 183.61 184.53 185.45 186.37 187.29
1.5% 160.69 161.61 162.53 163.45 164.37 165.29 166.21 167.13 168.05 168.97 169.89 170.81 171.74 172.66 173.58 174.50 175.42 176.35 177.27 178.19 179.11 180.04 180.96 181.89 182.81 183.73 184.66 185.58 186.51 187.43 188.36 189.28
2.0% 162.05 162.97 163.89 164.82 165.74 166.67 167.59 168.52 169.44 170.37 171.29 172.22 173.14 174.07 174.99 175.92 176.84 177.77 178.70 179.62 180.55 181.48 182.40 183.33 184.26 185.19 186.12 187.04 187.97 188.90 189.83 190.76
3.0% 164.06 164.99 165.92 166.85 167.78 168.71 169.64 170.57 171.50 172.43 173.36 174.29 175.22 176.15 177.08 178.02 178.95 179.88 180.81 181.74 182.68 183.61 184.54 185.48 186.41 187.34 188.27 189.21 190.14 191.08 192.01 192.94
5.0% 166.78 167.72 168.66 169.59 170.53 171.47 172.41 173.34 174.28 175.22 176.16 177.10 178.04 178.97 179.91 180.85 181.79 182.73 183.67 184.61 185.55 186.49 187.43 188.37 189.31 190.25 191.19 192.13 193.07 194.02 194.96 195.90
June 2001
C-7
0.1% 178.50 179.39 180.29 181.18 182.08 182.98 183.87 184.77 185.67 186.56 187.46 188.36 189.26 190.16 191.05 191.95 192.85 193.75 194.65 195.55 196.45 197.35 198.25 199.15 200.05 200.95 201.85 202.76 203.66 204.56 205.46 206.36
0.15% 180.04 180.94 181.84 182.74 183.64 184.54 185.45 186.35 187.25 188.15 189.05 189.95 190.85 191.76 192.66 193.56 194.46 195.37 196.27 197.17 198.08 198.98 199.89 200.79 201.69 202.60 203.50 204.41 205.31 206.22 207.13 208.03
0.2% 181.18 182.08 182.99 183.89 184.79 185.70 186.60 187.50 188.41 189.31 190.22 191.12 192.03 192.93 193.84 194.74 195.65 196.55 197.46 198.36 199.27 200.18 201.08 201.99 202.90 203.81 204.71 205.62 206.53 207.44 208.35 209.25
0.3% 182.84 183.74 184.65 185.56 186.47 187.37 188.28 189.19 190.10 191.01 191.91 192.82 193.73 194.64 195.55 196.46 197.37 198.28 199.19 200.10 201.01 201.92 202.83 203.74 204.66 205.57 206.48 207.39 208.30 209.21 210.13 211.04
0.5% 185.03 185.94 186.85 187.77 188.68 189.59 190.51 191.42 192.33 193.25 194.16 195.08 195.99 196.90 197.82 198.73 199.65 200.56 201.48 202.40 203.31 204.23 205.14 206.06 206.98 207.89 208.81 209.73 210.65 211.56 212.48 213.40
1.0% 188.21 189.13 190.05 190.97 191.90 192.82 193.74 194.66 195.58 196.50 197.42 198.35 199.27 200.19 201.11 202.04 202.96 203.88 204.81 205.73 206.65 207.58 208.50 209.42 210.35 211.27 212.20 213.12 214.05 214.97 215.90 216.82
1.5% 190.21 191.13 192.06 192.98 193.91 194.83 195.76 196.69 197.61 198.54 199.47 200.39 201.32 202.25 203.18 204.10 205.03 205.96 206.89 207.82 208.74 209.67 210.60 211.53 212.46 213.39 214.32 215.25 216.18 217.11 218.04 218.97
2.0% 191.69 192.62 193.54 194.47 195.40 196.33 197.26 198.19 199.12 200.05 200.98 201.91 202.85 203.78 204.71 205.64 206.57 207.50 208.43 209.36 210.30 211.23 212.16 213.09 214.03 214.96 215.89 216.82 217.76 218.69 219.62 220.56
3.0% 193.88 194.81 195.75 196.68 197.62 198.55 199.49 200.42 201.36 202.29 203.23 204.17 205.10 206.04 206.97 207.91 208.85 209.78 210.72 211.66 212.59 213.53 214.47 215.41 216.34 217.28 218.22 219.16 220.10 221.03 221.97 222.91
5.0% 196.84 197.78 198.72 199.67 200.61 201.55 202.49 203.43 204.38 205.32 206.26 207.21 208.15 209.09 210.03 210.98 211.92 212.87 213.81 214.75 215.70 216.64 217.59 218.53 219.47 220.42 221.36 222.31 223.25 224.20 225.14 226.09
226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253
C-8
June 2001
Channels N 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285
0.1% 207.26 208.17 209.07 209.97 210.87 211.78 212.68 213.58 214.49 215.39 216.30 217.20 218.11 219.01 219.91 220.82 221.72 222.63 223.54 224.44 225.35 226.25 227.16 228.07 228.97 229.88 230.79 231.69 232.60 233.51 234.42 235.32
0.15% 208.94 209.84 210.75 211.66 212.56 213.47 214.38 215.28 216.19 217.10 218.01 218.91 219.82 220.73 221.64 222.55 223.46 224.37 225.28 226.18 227.09 228.00 228.91 229.82 230.73 231.64 232.55 233.46 234.38 235.29 236.20 237.11
0.2% 210.16 211.07 211.98 212.89 213.80 214.71 215.62 216.53 217.44 218.35 219.26 220.17 221.08 221.99 222.90 223.82 224.73 225.64 226.55 227.46 228.37 229.29 230.20 231.11 232.02 232.94 233.85 234.76 235.68 236.59 237.50 238.42
0.3% 211.95 212.87 213.78 214.69 215.60 216.52 217.43 218.35 219.26 220.17 221.09 222.00 222.92 223.83 224.75 225.66 226.58 227.49 228.41 229.32 230.24 231.16 232.07 232.99 233.91 234.82 235.74 236.66 237.57 238.49 239.41 240.33
0.5% 214.32 215.23 216.15 217.07 217.99 218.91 219.83 220.75 221.66 222.58 223.50 224.42 225.34 226.26 227.18 228.10 229.02 229.94 230.86 231.79 232.71 233.63 234.55 235.47 236.39 237.31 238.24 239.16 240.08 241.00 241.92 242.85
1.0% 217.75 218.67 219.60 220.53 221.45 222.38 223.30 224.23 225.16 226.08 227.01 227.94 228.86 229.79 230.72 231.65 232.57 233.50 234.43 235.36 236.29 237.21 238.14 239.07 240.00 240.93 241.86 242.79 243.72 244.65 245.58 246.50
1.5% 219.90 220.83 221.76 222.69 223.62 224.55 225.48 226.41 227.34 228.27 229.20 230.13 231.07 232.00 232.93 233.86 234.79 235.73 236.66 237.59 238.52 239.46 240.39 241.32 242.26 243.19 244.12 245.06 245.99 246.92 247.86 248.79
2.0% 221.49 222.42 223.36 224.29 225.22 226.16 227.09 228.03 228.96 229.90 230.83 231.77 232.70 233.64 234.57 235.51 236.44 237.38 238.31 239.25 240.19 241.12 242.06 242.99 243.93 244.87 245.80 246.74 247.68 248.62 249.55 250.49
3.0% 223.85 224.79 225.73 226.67 227.60 228.54 229.48 230.42 231.36 232.30 233.24 234.18 235.12 236.06 237.00 237.94 238.88 239.82 240.76 241.70 242.64 243.59 244.53 245.47 246.41 247.35 248.29 249.23 250.18 251.12 252.06 253.00
5.0% 227.03 227.98 228.93 229.87 230.82 231.76 232.71 233.65 234.60 235.55 236.49 237.44 238.39 239.33 240.28 241.23 242.17 243.12 244.07 245.02 245.96 246.91 247.86 248.81 249.75 250.70 251.65 252.60 253.55 254.49 255.44 256.39
June 2001
C-9
0.1% 236.23 237.14 238.05 238.96 239.86 240.77 241.68 242.59 243.50 244.41 245.32 246.23 247.14 248.05 248.96 294.64 340.61 386.83 433.26 479.86 526.61 573.50 620.50 667.61 714.81 762.10 809.46 856.90 904.41 951.98 999.60
0.15% 238.02 238.93 239.84 240.76 241.67 242.58 243.49 244.40 245.32 246.23 247.14 248.06 248.97 249.88 250.80 296.64 342.77 389.14 435.70 482.43 529.31 576.31 623.43 670.65 717.96 765.35 812.82 860.36 907.96 955.62
0.2% 239.33 240.25 241.16 242.07 242.99 243.90 244.82 245.73 246.65 247.56 248.48 249.40 250.31 251.23 252.14 298.11 344.35 390.83 437.49 484.32 531.28 578.38 625.58 672.88 720.27 767.73 815.28 862.89 910.56 958.29
0.3% 241.24 242.16 243.08 244.00 244.92 245.83 246.75 247.67 248.59 249.51 250.43 251.35 252.27 253.19 254.11 300.25 346.66 393.28 440.09 487.06 534.16 581.38 628.70 676.12 723.62 771.20 818.85 866.56 914.33 962.16
0.5% 243.77 244.69 245.61 246.54 247.46 248.38 249.31 250.23 251.15 252.08 253.00 253.93 254.85 255.78 256.70 303.07 349.69 396.52 443.52 490.67 537.94 585.33 632.81 680.38 728.04 775.76 823.55 871.40 919.31 967.27
1.0% 247.43 248.36 249.29 250.22 251.15 252.09 253.02 253.95 254.88 255.81 256.74 257.67 258.60 259.53 260.46 307.17 354.10 401.22 448.49 495.90 543.42 591.05 638.76 686.56 734.43 782.36 830.35 878.40 926.50 974.64
1.5% 249.73 250.66 251.59 252.53 253.46 254.40 255.33 256.27 257.20 258.14 259.07 260.01 260.94 261.88 262.82 309.73 356.85 404.15 451.59 499.16 546.84 594.61 642.47 690.40 738.40 786.47 834.59 882.75 930.97 979.23
2.0% 251.43 252.36 253.30 254.24 255.18 256.12 257.05 257.99 258.93 259.87 260.81 261.75 262.68 263.62 264.56 311.62 358.89 406.32 453.89 501.58 549.37 597.26 645.22 693.25 741.35 789.51 837.72 885.98 934.29 982.63
3.0% 253.94 254.89 255.83 256.77 257.71 258.66 259.60 260.54 261.48 262.43 263.37 264.31 265.26 266.20 267.14 314.43 361.90 409.53 457.29 505.15 553.11 601.16 649.27 697.46 745.70 794.00 842.35 890.74 939.17 987.65
5.0% 257.34 258.29 259.24 260.18 261.13 262.08 263.03 263.98 264.93 265.88 266.83 267.78 268.73 269.68 270.63 318.21 365.96 413.85 461.86 509.96 558.14 606.40 654.73 703.11 751.55 800.03 848.56 897.13 945.74 994.38
290 291 292 293 294 295 296 297 298 299 300 350 400 450 500 550 600 650 700 750 800 850 900 950 1000 1050 1100 1150
1003.34 1006.07 1010.04 1015.27 1022.83 1027.54 1031.02 1036.15 1043.06 ... continued on next page
1047.28 1051.11 1053.90 1057.97 1063.32 1071.06 1075.88 1079.44 1084.70 1091.76
C-10
June 2001
Channels N 1200 1250 1300 1350 1400 1450 1500 1550 1600 1650 1700 1750 1800 1850 1900 1950 2000 2050 2100 2150 2200 2250 2300 2350 2400 2450 2500 2550 2600 2650 2700 2750
0.1%
0.15%
0.2%
0.3%
0.5%
1.0%
1.5%
2.0%
3.0%
5.0%
1095.01 1098.92 1101.78 1105.94 1111.42 1119.33 1124.25 1127.90 1133.27 1140.49 1142.78 1146.78 1149.70 1153.95 1159.55 1167.63 1172.66 1176.38 1181.87 1189.25 1190.60 1194.68 1197.67 1202.01 1207.72 1215.97 1221.10 1224.90 1230.50 1238.03 1238.46 1242.63 1245.67 1250.10 1255.92 1264.34 1269.57 1273.45 1279.16 1286.83 1286.36 1290.61 1293.71 1298.22 1304.16 1312.74 1318.07 1322.02 1327.84 1335.66 1334.30 1338.62 1341.78 1346.38 1352.43 1361.16 1366.60 1370.62 1376.55 1384.51 1382.27 1386.67 1389.89 1394.57 1400.73 1409.62 1415.15 1419.24 1425.27 1433.37 1430.28 1434.76 1438.03 1442.79 1449.05 1458.10 1463.72 1467.89 1474.02 1482.26 1478.31 1482.87 1486.20 1491.04 1497.41 1506.60 1512.32 1516.55 1522.79 1531.16 1526.38 1531.01 1534.40 1539.31 1545.79 1555.13 1560.94 1565.24 1571.58 1580.09 1574.48 1579.18 1582.62 1587.61 1594.19 1603.68 1609.58 1613.95 1620.38 1629.02 1622.61 1627.38 1630.87 1635.94 1642.61 1652.25 1658.24 1662.67 1669.20 1677.98 1670.76 1675.60 1679.14 1684.29 1691.06 1700.84 1706.92 1711.42 1718.04 1726.94 1718.93 1723.85 1727.44 1732.66 1739.53 1749.45 1755.62 1760.18 1766.90 1775.92 1767.13 1772.12 1775.76 1781.06 1788.02 1798.08 1804.33 1808.96 1815.77 1824.92 1815.36 1820.41 1824.11 1829.47 1836.53 1846.72 1853.06 1857.75 1864.66 1873.93 1863.61 1868.73 1872.47 1877.91 1885.06 1895.39 1901.81 1906.56 1913.56 1922.95 1911.88 1917.06 1920.85 1926.36 1933.61 1944.07 1950.57 1955.38 1962.47 1971.98 1960.17 1965.42 1969.26 1974.84 1982.18 1992.77 1999.35 2004.22 2011.40 2021.03 2008.48 2013.80 2017.68 2023.33 2030.76 2041.48 2048.14 2053.07 2060.34 2070.08 2056.81 2062.19 2066.12 2071.84 2079.36 2090.20 2096.95 2101.94 2109.29 2119.15 2105.16 2110.60 2114.58 2120.36 2127.97 2138.95 2145.77 2150.82 2158.25 2168.23 2153.52 2159.03 2163.06 2168.91 2176.60 2187.70 2194.60 2199.71 2207.23 2217.32 2201.91 2207.48 2211.55 2217.46 2225.24 2236.47 2243.45 2248.61 2256.21 2266.42 2250.31 2255.94 2260.06 2266.04 2273.90 2285.25 2292.31 2297.52 2305.21 2315.52 2298.73 2304.42 2308.58 2314.63 2322.58 2334.05 2341.18 2346.45 2354.22 2364.64 2347.16 2352.92 2357.12 2363.23 2371.26 2382.85 2390.06 2395.38 2403.23 2413.77 2395.61 2401.43 2405.67 2411.84 2419.96 2431.67 2438.95 2444.33 2452.26 2462.90 2444.08 2449.95 2454.24 2460.47 2468.67 2480.50 2487.85 2493.29 2501.30 2512.04 2492.56 2498.49 2502.82 2509.12 2517.40 2529.34 2536.77 2542.26 2550.34 2561.19 2541.05 2547.04 2551.42 2557.77 2566.13 2578.19 2585.69 2591.23 2599.40 2610.35 2589.56 2595.61 2600.02 2606.44 2614.88 2627.06 2634.62 2640.22 2648.46 2659.52 ... continued on next page
June 2001
C-11
0.1%
0.15%
0.2%
0.3%
0.5%
1.0%
1.5%
2.0%
3.0%
5.0%
2638.08 2644.19 2648.64 2655.12 2663.64 2675.93 2683.57 2689.21 2697.53 2708.69 2686.62 2692.78 2697.28 2703.81 2712.41 2724.81 2732.52 2738.22 2746.61 2757.88 2735.17 2741.38 2745.92 2752.52 2761.19 2773.71 2781.48 2787.23 2795.70 2807.06 2783.73 2790.00 2794.58 2801.23 2809.98 2822.61 2830.45 2836.25 2844.80 2856.26 2832.30 2838.62 2843.24 2849.96 2858.79 2871.52 2879.43 2885.28 2893.90 2905.46 2880.88 2887.26 2891.92 2898.69 2907.60 2920.44 2928.42 2934.32 2943.01 2954.67 2929.48 2935.91 2940.61 2947.44 2956.42 2969.37 2977.42 2983.37 2992.13 3003.89 2978.08 2984.57 2989.31 2996.20 3005.25 3018.31 3026.42 3032.42 3041.26 3053.11 3026.70 3033.24 3038.02 3044.96 3054.09 3067.25 3075.43 3081.48 3090.39 3102.34 3075.33 3081.92 3086.74 3093.74 3102.94 3116.21 3124.45 3130.55 3139.53 3151.57 3123.97 3130.62 3135.47 3142.52 3151.80 3165.17 3173.48 3179.62 3188.67 3200.81 3172.62 3179.32 3184.21 3191.32 3200.66 3214.14 3222.51 3228.71 3237.83 3250.06 3221.28 3228.03 3232.96 3240.12 3249.54 3263.12 3271.56 3277.80 3286.98 3299.31 3269.95 3276.75 3281.72 3288.93 3298.42 3312.10 3320.61 3326.89 3336.15 3348.57 3318.63 3325.48 3330.48 3337.75 3347.31 3361.10 3369.66 3375.99 3385.32 3397.83 3367.31 3374.22 3379.26 3386.58 3396.21 3410.10 3418.72 3425.10 3434.50 3447.09 3416.01 3422.96 3428.04 3435.42 3445.12 3459.10 3467.79 3474.22 3483.68 3496.37 3464.72 3471.72 3476.83 3484.26 3494.03 3508.12 3516.87 3523.34 3532.87 3545.64 3513.43 3520.49 3525.63 3533.12 3542.95 3557.14 3565.95 3572.47 3582.06 3594.93 3562.16 3569.26 3574.44 3581.98 3591.88 3606.17 3615.04 3621.60 3631.26 3644.21 3610.89 3618.04 3623.26 3630.85 3640.82 3655.20 3664.13 3670.74 3680.46 3693.51 3659.63 3666.83 3672.09 3679.72 3689.76 3704.24 3713.23 3719.88 3729.67 3742.80 3708.38 3715.63 3720.92 3728.61 3738.71 3753.29 3762.34 3769.03 3778.89 3792.10 3757.14 3764.43 3769.76 3777.50 3787.67 3802.34 3811.45 3818.19 3828.11 3841.41 3805.90 3813.24 3818.60 3826.39 3836.63 3851.40 3860.57 3867.35 3877.33 3890.72
3000 3050 3100 3150 3200 3250 3300 3350 3400 3450 3500 3550 3600 3650 3700 3750 3800 3850 3900 3950 4000
C-12
June 2001
Table C-2: Erlang C Spans Spans 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 T1 Circuits 24 48 72 96 120 144 168 192 216 240 264 288 312 336 360 384 408 432 456 480 504 528 552 576 600 624 648 672 696 720 T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 11.59 29.30 48.46 68.38 88.78 109.52 130.53 151.74 173.13 194.65 216.30 238.05 259.89 281.81 303.81 325.87 347.99 370.17 392.39 414.67 436.98 459.34 481.73 504.15 526.61 549.10 571.62 594.16 616.74 639.33 12.22 30.34 49.82 70.01 90.65 111.61 132.81 154.21 175.77 197.46 219.26 241.16 263.15 285.21 307.34 329.53 351.77 374.07 396.42 418.80 441.23 463.69 486.19 508.72 531.28 553.87 576.49 599.13 621.80 644.49 12.62 30.99 50.67 71.02 91.81 112.90 134.23 155.74 177.40 199.19 221.09 243.08 265.15 287.30 309.51 331.78 354.10 376.47 398.89 421.35 443.84 466.37 488.94 511.53 534.16 556.81 579.48 602.19 624.91 647.66 E1 Circuits 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450 480 510 540 570 600 630 660 690 720 750 780 810 840 870 900 E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 15.80 38.76 63.34 88.78 114.75 141.11 167.77 194.65 221.72 248.96 276.32 303.81 331.40 359.07 386.83 414.67 442.57 470.53 498.54 526.61 554.73 582.89 611.09 639.33 667.61 695.92 724.26 752.63 781.04 809.46 16.55 39.97 64.91 90.65 116.89 143.49 170.37 197.46 224.73 252.14 279.68 307.34 335.08 362.92 390.83 418.80 446.84 474.94 503.09 531.28 559.52 587.81 616.13 644.49 672.88 701.30 729.75 758.23 786.74 815.28 17.02 40.72 65.88 91.81 118.21 144.96 171.97 199.19 226.58 254.11 281.76 309.51 337.36 365.28 393.28 421.35 449.47 477.65 505.88 534.16 562.47 590.83 619.23 647.66 676.12 704.61 733.13 761.68 790.25 818.85
June 2001
C-13
Spans 31 32 33 34
T1 Circuits 744 768 792 816 840 864 888 912 936 960 984 1008 1032 1056 1080 1104 1128 1152 1176 1200 1224 1248 1272 1296 1320 1344 1368 1392 1416 1440 1464 1488
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 661.95 684.59 707.25 729.93 752.63 775.35 798.09 820.84 843.61 866.40 889.20 912.02 934.85 957.69 980.55 1003.41 1026.30 1049.19 1072.09 1095.01 1117.93 1140.87 1163.82 1186.78 1209.74 1232.72 1255.70 1278.70 1301.70 1324.71 1347.73 1370.76 667.20 689.93 712.68 735.45 758.23 781.04 803.86 826.70 849.55 872.42 895.30 918.19 941.10 964.02 986.95 1009.89 1032.85 1055.82 1078.79 1101.78 1124.78 1147.79 1170.80 1193.83 1216.87 1239.91 1262.96 1286.02 1309.09 1332.17 1355.25 1378.34 670.42 693.21 716.01 738.84 761.68 784.53 807.41 830.29 853.20 876.11 899.04 921.98 944.94 967.91 990.88 1013.88 1036.88 1059.89 1082.91 1105.94 1128.98 1152.03 1175.09 1198.16 1221.24 1244.32 1267.42 1290.52 1313.63 1336.75 1359.87 1383.00
E1 Circuits 930 960 990 1020 1050 1080 1110 1140 1170 1200 1230 1260 1290 1320 1350 1380 1410 1440 1470 1500 1530 1560 1590 1620 1650 1680 1710 1740 1770 1800 1830 1860
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 837.92 866.40 894.90 923.43 951.98 980.55 1009.13 1037.74 1066.37 1095.01 1123.67 1152.34 1181.04 1209.74 1238.46 1267.20 1295.95 1324.71 1353.48 1382.27 1411.07 1439.88 1468.70 1497.54 1526.38 1555.24 1584.10 1612.98 1641.86 1670.76 1699.66 1728.57 843.83 872.42 901.02 929.64 958.29 986.95 1015.63 1044.33 1073.05 1101.78 1130.53 1159.29 1188.07 1216.87 1245.67 1274.49 1303.32 1332.17 1361.02 1389.89 1418.77 1447.66 1476.56 1505.47 1534.40 1563.33 1592.27 1621.22 1650.18 1679.14 1708.12 1737.10 847.47 876.11 904.78 933.46 962.16 990.88 1019.62 1048.38 1077.15 1105.94 1134.74 1163.56 1192.39 1221.24 1250.10 1278.97 1307.85 1336.75 1365.65 1394.57 1423.50 1452.44 1481.39 1510.35 1539.31 1568.29 1597.28 1626.27 1655.28 1684.29 1713.31 1742.34
35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62
C-14
June 2001
Spans 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94
T1 Circuits 1512 1536 1560 1584 1608 1632 1656 1680 1704 1728 1752 1776 1800 1824 1848 1872 1896 1920 1944 1968 1992 2016 2040 2064 2088 2112 2136 2160 2184 2208 2232 2256
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 1393.79 1416.83 1439.88 1462.94 1486.00 1509.08 1532.15 1555.24 1578.33 1601.43 1624.53 1647.64 1670.76 1693.88 1717.01 1740.14 1763.28 1786.42 1809.57 1832.73 1855.89 1879.05 1902.22 1925.40 1948.58 1971.76 1994.95 2018.14 2041.34 2064.54 2087.75 2110.96 1401.44 1424.55 1447.66 1470.78 1493.91 1517.04 1540.18 1563.33 1586.48 1609.64 1632.80 1655.97 1679.14 1702.32 1725.51 1748.70 1771.90 1795.10 1818.30 1841.51 1864.73 1887.95 1911.18 1934.41 1957.64 1980.88 2004.12 2027.37 2050.62 2073.87 2097.13 2120.40 1406.14 1429.29 1452.44 1475.60 1498.76 1521.93 1545.11 1568.29 1591.48 1614.67 1637.87 1661.08 1684.29 1707.51 1730.73 1753.95 1777.19 1800.42 1823.66 1846.91 1870.16 1893.41 1916.67 1939.93 1963.20 1986.47 2009.75 2033.03 2056.31 2079.60 2102.89 2126.19
E1 Circuits 1890 1920 1950 1980 2010 2040 2070 2100 2130 2160 2190 2220 2250 2280 2310 2340 2370 2400 2430 2460 2490 2520 2550 2580 2610 2640 2670 2700 2730 2760 2790 2820
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 1757.49 1786.42 1815.36 1844.31 1873.26 1902.22 1931.19 1960.17 1989.15 2018.14 2047.14 2076.15 2105.16 2134.17 2163.20 2192.23 2221.27 2250.31 2279.36 2308.41 2337.48 2366.54 2395.61 2424.69 2453.77 2482.86 2511.96 2541.05 2570.16 2599.26 2628.38 2657.50 1766.10 1795.10 1824.11 1853.12 1882.15 1911.18 1940.21 1969.26 1998.31 2027.37 2056.43 2085.50 2114.58 2143.66 2172.75 2201.85 2230.95 2260.06 2289.17 2318.29 2347.41 2376.54 2405.67 2434.81 2463.96 2493.10 2522.26 2551.42 2580.58 2609.75 2638.92 2668.10 1771.38 1800.42 1829.47 1858.53 1887.60 1916.67 1945.75 1974.84 2003.93 2033.03 2062.13 2091.25 2120.36 2149.49 2178.62 2207.75 2236.89 2266.04 2295.19 2324.35 2353.51 2382.67 2411.84 2441.02 2470.20 2499.39 2528.58 2557.77 2586.97 2616.18 2645.38 2674.60
June 2001
C-15
Spans 95 96 97 98
T1 Erlangs T1 Erlangs T1 Erlangs at 0.1% at 0.2% at 0.3% 2134.17 2157.39 2180.62 2203.84 2227.08 2250.31 2143.66 2166.94 2190.21 2213.49 2236.77 2260.06 2149.49 2172.79 2196.10 2219.41 2242.72 2266.04
E1 Erlangs E1 Erlangs E1 Erlangs at 0.1% at 0.2% at 0.3% 2686.62 2715.74 2744.88 2774.01 2803.15 2832.30 2697.28 2726.46 2755.65 2784.84 2814.04 2843.24 2703.81 2733.03 2762.26 2791.49 2820.72 2849.96
99 100
C-16
June 2001
English