401-200-112

401-200-112Issue 11June 2001

Lucent Technologies — ProprietaryThis document contains proprietary information of

Lucent Technologies and is not to be disclosed or usedexcept in accordance with applicable agreements

Copyright © 2001 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

AUTOPLEX® Cellular

Telecommunications Systems

System 1000

Time Division Multiple Access(TDMA) and Digital ControlChannel (DCCH)

Implementation Guidelines

Lucent Technologies — ProprietarySee notice on first page

This material is protected by the copyright and trade secret laws of the United States and other countries. Itmay not be reproduced, distributed or altered in any fashion by any entity, including other LucentTechnologies Business Units or Divisions, without the expressed written consent of the Customer TechnicalSupport and Information organization.

For permission to reproduce or distribute please contact:

Product Development Manager 1-800-334-0404

NoticeEvery effort was made to ensure that the information in this document was complete and accurate at the timeof printing. However, information is subject to change.

Mandatory Customer Information

Federal Communications Commission (FCC) StatementNone for this document but here to illustrate the feature.

SecurityThis is a sample security statement.

TrademarksAMPHENOL is a registered trademark of Allied Signal, Inc.AUTOPLEX is a registered trademark of Lucent Technologies.CINCH is a registered trademark of Cinch Fasteners, Radio & Electronic Parts.DataSMART is a registered trademark of Kentrox Industries.Ethernet is a registered trademark of Xerox Corp.Informix is a registered trademark of Informix Software, Inc.JFD is a registered trademark of JFD Electronics.Kentrox is a registered trademark of Kentrox Industries.LGX is a registered trademark of Lucent Technologies.LINEAGE is a registered trademark of Lucent Technologies.MS-DOS, Windows, and Windows for Workstations are registered trademarks of Microsoft Corp.POMONA is a registered trademark of POMONA Electronics.SUN, SOLARIS, and SPARCStation are trademarks of SUN Microsystems, Inc.TEXAS INSTRUMENT is a registered trademark of Texas Instruments.T-SMART is a registered trademark of Kentrox Industries.T-SERV is a registered trademark of Kentrox Industries.UL is a registered trademark of Underwriters Laboratories, Inc.UNIX is a registered trademark of Novell, Inc.WABER is a registered trademark of SL Industries.WE is a registered trademark of Lucent Technologies.

Other trademarked terms may appear in this document as well. They are marked on first usage.

WarrantyLucent Technologies provides no warranty for this product.Order InformationThe ordering number for this document is 401-200-112. To order this document, call the Lucent TechnologiesCustomer Information Center in Indianapolis, Indiana, on 1-888-582-3688.Support TelephoneLucent Technologies provides a telephone number for you to report errors or to ask questions about theinformation in this document.

Rick Essick — 708 979-7491Lucent Technologies provides a telephone number for technical assistance support from the CustomerTechnical Support Organization (CTSO). The support number is:

1-800-225-4672

How Are We Doing?

Title

Iden

Luccom

1.

2.

❒❒❒❒❒❒

Ple

3.

4.

If w

Nam

Com

Add

Whor F

: AUTOPLX Cellular Telecommunication Systems, System 1000 TDMA Implementation Guide

tification No. sue No ate

ent Technoloments can b

Please rate th

Please check

Improve theImprove theImprove theInclude morAdd more exAdd more de

ase provide

What did you

Feel free to w

e may contac

e:

pany/Organ

ress:

en you haveax to: 910 7

Ease of Use

Clarity

Completeness

Accuracy

Organization

Appearance

Examples

Illustrations

Overall Satisifa

: Is401-200-112

gies welcomes your feedback on this Cuse of great value in helping us improve our

e effectiveness of this CIP in the followin

the ways you feel we could improve this

overview/introduction ❒ Make it motable of contents ❒ Add more sorganization ❒ Add more t

e figures ❒ Make it lessamples ❒ Add more/btail ❒ Improve the

details for the suggested improvement.

like most about this CIP?

rite any comments below or on an attach

t you concerning your comments, please

T

ization:

completed this form, please fold, tape and27-3043.

Excellent Good

ction

.: D11

tomer Information PCIPs.

g areas:

CIP.

re concise/brieftep-by-step procedurroubleshooting inform

technicaletter quick referenceindex

ed sheet.

complete the follow

elephone Number:

Date

return to address o

Fair Poo

: June 2001

roduct (CIP). Your

es/tutorialsation

aids

ing:

:

n back

rNot

Applicable

////////////////////////////////////

//////////////////

//////////////////

//////////////////

//////////////////

//////////////////

BUSINESS REPLY MAILFIRST CLASS PERMIT NO. 1999 GREENSBORO, NC

POSTAGE WILL BE PAID BY ADDRESSEE

NO POSTAGENECESSARY

IF MAILEDIN THE

UNITED STATES

------------------------------------------------------------ Do Not Cut — Fold Here And Tape ---------------------------------------------------------------------

DOCUMENTATION SERVICES2400 Reynolda RoadWinston-Salem, NC 27199-2029

How Are We Doing?

Title

Iden

Luccom

1.

2.

❒❒❒❒❒❒

Ple

3.

4.

If w

Nam

Com

Add

Whor F

: AUTOPLX Cellular Telecommunication Systems, System 1000 TDMA Implementation Guide

tification No. sue No ate

ent Technoloments can b

Please rate th

Please check

Improve theImprove theImprove theInclude morAdd more exAdd more de

ase provide

What did you

Feel free to w

e may contac

e:

pany/Organ

ress:

en you haveax to: 910 7

Ease of Use

Clarity

Completeness

Accuracy

Organization

Appearance

Examples

Illustrations

Overall Satisifa

: Is401-200-112

gies welcomes your feedback on this Cuse of great value in helping us improve our

e effectiveness of this CIP in the followin

the ways you feel we could improve this

overview/introduction ❒ Make it motable of contents ❒ Add more sorganization ❒ Add more t

e figures ❒ Make it lessamples ❒ Add more/btail ❒ Improve the

details for the suggested improvement.

like most about this CIP?

rite any comments below or on an attach

t you concerning your comments, please

T

ization:

completed this form, please fold, tape and27-3043.

Excellent Good

ction

.: D11

tomer Information PCIPs.

g areas:

CIP.

re concise/brieftep-by-step procedurroubleshooting inform

technicaletter quick referenceindex

ed sheet.

complete the follow

elephone Number:

Date

return to address o

Fair Poo

: June 2001

roduct (CIP). Your

es/tutorialsation

aids

ing:

:

n back

rNot

Applicable

////////////////////////////////////

//////////////////

//////////////////

//////////////////

//////////////////

//////////////////

BUSINESS REPLY MAILFIRST CLASS PERMIT NO. 1999 GREENSBORO, NC

POSTAGE WILL BE PAID BY ADDRESSEE

NO POSTAGENECESSARY

IF MAILEDIN THE

UNITED STATES

------------------------------------------------------------ Do Not Cut — Fold Here And Tape ---------------------------------------------------------------------

DOCUMENTATION SERVICES2400 Reynolda RoadWinston-Salem, NC 27199-2029

Lucent Technologies Practices401-200-112, Issue 11

Contents

1 Introduction 1

1.1 Introduction 1-1

1.1.1 Reason for Reissue 1-1

1.1.2 Previous Issues 1-2

1.1.3 Intended Audience 1-7

1.1.4 Prerequisite Skills and Knowledge 1-7

1.1.5 Purpose 1-8

1.1.6 Document Organization 1-8

1.2 Software and Hardware Requirements 1-9

1.2.1 Software 1-9

1.2.2 Hardware 1-9

1.3 TDMA Overview 1-10

1.3.1 Radio Access Method 1-11

1.3.2 DRU and EDRU Configurations 1-12

1.3.3 Digital Mobiles 1-12

1.3.4 TDMA Call Processing 1-12

1.3.4.1 TDMA Call Setup 1-12

1.3.4.2 Handoff 1-13

1.3.4.2.1 Difference Between AMPS and TDMA Handoff 1-13

1.3.4.2.2 DCCH Information on an Analog Voice Channel 1-14

1.3.4.2.3 MAHO Translations 1-14

1.3.4.2.4 Handoff Triggers 1-15

1.3.4.2.5 Generating Handoff Candidate List 1-15

1.3.4.2.6 Digital Locate 1-15

1.3.4.3 Interhyperband Operation 1-16

1.3.4.3.1 Interhyperband Phase 1 (DIHOP1) 1-16

1.3.4.3.2 Hyperband Measurement Order 1-17


1.3.5 Dynamic Power Control with BER 1-17

1.3.6 TDMA Voice Channel Confirmation 1-18

1.3.6.1 Time Alignment 1-181-18

1-18

1-17

1-17

1-17

1-16

1-16

1-15

1-15

1-15

1-14

1-14

1-13

1-13

1-12

1-12

1-12

1-12

1-11

1-10

1-9

1-9

1-9

1-8

1-8

1-7

1-7

1-2

1-1

1-1

June 2001 iii



Contents

1.3.6.2 Digital Verification Color Code (DVCC) 1-19

1.3.6.3 Measurement Order Message 1-19

1.3.7 Digital Radio Voice Channel Processing 1-19

1.3.7.1 Forward Digital Voice Channel Processing 1-20

1.3.7.2 Reverse Digital Voice Channel Processing 1-22

1.3.7.3 Vocoder and Echo Canceller Location 1-23

1.4 Digital Control Channel (DCCH) Overview 1-25

1.4.1 Transmission Format 1-26

1.4.2 Relationship with the ACC 1-26

1.4.3 Logical Channel Structure 1-26

1.4.3.1 Reverse DCCH 1-27

1.4.3.2 Forward DCCH 1-27

1.4.4 Multiple DCCH Feature 1-28

1.4.4.1 Deployment Considerations 1-28

1.4.4.2 Turning On the Multiple DCCH Feature 1-29

1.4.4.3 Equipping Multiple DCCH Timeslots on an EDRU 1-29

1.4.4.4 Turning Multiple DCCH Feature Off 1-30

1.5 TDMA Call Processing 1-31

1.5.1 Call Processing Overview 1-32

1.5.1.1 Call Origination and Termination 1-32

1.5.1.2 Call Processing Detail Description 1-33

1.5.1.2.1 Autonomous Registration 1-33

1.5.1.2.2 Reselection 1-35

1.5.1.2.3 Separate Access Thresholds for DCCH and DTCChannels 1-38

1.5.1.2.4 Mobile Assisted Channel Allocation (MACA) 1-39

1.5.1.3 Call Setup 1-40

1.5.1.3.1 Paging 1-40

1.5.1.3.2 Accessing 1-41

1.5.1.3.3 Initial Traffic Channel Confirmation 1-41

1.5.1.3.4 Increased TDMA MAHO List 1-42

1.5.1.4 Call-In-Progress 1-45

1.5.1.4.1 Mobile Assisted Handoff (MAHO) 1-461-46

1-45

1-42

1-41

1-41

1-40

1-40

1-39

1-38

1-35

1-33

1-33

1-32

1-32

1-31

1-30

1-29

1-29

1-28

1-28

1-27

1-27

1-26

1-26

1-26

1-25

1-23

1-22

1-20

1-19

1-19

1-19

iv June 2001



Contents

1.5.1.4.2 RF Signal Quality Measurements 1-46

1.5.1.4.3 MAHO Threshold Parameter 1-47

1.5.1.4.4 Standard MAHO Candidate Selection 1-48

1.5.1.4.5 Dynamic Power Control (DPC) 1-50

1.5.1.4.6 Uplink Dynamic Power Control (UDPC) 1-50

1.5.1.4.7 Downlink Dynamic Power Control (DDPC) 1-52

1.5.2 DCCH Call Processing States 1-55

1.5.3 Advanced Features for DCCH 1-55

1.5.4 Message Center 1-56

1.6 Technician Interface 1-57

1.7 Recommendations 1-57

1.7.1 Automatic Radio Reconfiguration (ARR) 1-58

1.7.2 Dual Server Group Cells 1-58

1.7.3 MAHO Channel/Beacon Channel 1-58

1.7.4 Shortened Burst 1-59

1.7.5 Color Codes 1-60

1.7.6 Audio Levels 1-60

1.8 Conclusion 1-61

2 Traffic and RF Engineering Guidelines 2-1


2.2 DTC Traffic Engineering Guidelines 2-3

2.2.1 Introduction 2-4

2.2.2 Channel Usage Unit of Measurement 2-4

2.2.3 Blocking 2-5

2.2.4 Traffic Capacity Planning, Separated Systems 2-6

2.2.4.1 Traffic Capacity Analysis 2-6

2.2.4.2 Determining TDMA Traffic Proportion 2-7

2.2.5 Traffic Capacity Planning, Integrated Systems 2-8

2.2.6 Use of Erlang Tables 2-9

2.3 DCCH Traffic Capacity Guidelines 2-112-11

2-9

2-8

2-7

2-6

2-6

2-5

2-4

2-4

2-3

2-1

2-1

1-61

1-60

1-60

1-59

1-58

1-58

1-58

1-57

1-57

1-56

1-55

1-55

1-52

1-50

1-50

1-48

1-47

1-46

June 2001 v



Contents

2.3.1 Forward Control Channel Messages 2-11

2.3.2 Traffic Assumptions 2-12

2.3.3 Forward DCCH Capacity Evaluation 2-12

2.3.3.1 Multiple DCCHs in a Sector 2-15

2.3.3.2 Paging Load 2-16

2.3.4 Reverse DCCH Capacity Evaluation 2-18

2.4 Digital Traffic Channel (DTC) RF Planning 2-19

2.4.1 Co-Channel Reuse Factor (K) Assignment 2-19

2.4.1.1 Co-Channel Reuse Factor Tradeoffs 2-20

2.4.1.2 K Selection Process 2-20

2.4.1.3 Evaluating the Results 2-21

2.4.2 TDMA Adjacent and Alternate Channel Assignment 2-23

2.4.3 Analog/TDMA Channel Segmentation Guidelines 2-23

2.4.3.1 Analog/TDMA Adjacent Channel Interference 2-23

2.4.3.2 Analog/TDMA Co-Channel Interference 2-24

2.4.4 Trunk Assignment 2-25

2.5 RF Performance Study 2-25

2.5.1 Proprietary Statement 2-25

2.5.2 To Obtain Document 2-26

2.6 RF Channel Assignment for Mixed ACC/DCCH Systems 2-26

2.7 Flexible Channel Allocation (FLCA) Features 2-26

2.7.1 FLCA Planning and Implementation 2-28

2.8 TDMA Discontinuous Transmission with ComfortNoise Insertion (DTX/CNI) 2-29

2.8.1 Voice Activity Detection (VAD) Algorithm 2-29

2.8.1.1 DTX/CNI Activation Restrictions 2-29

2.8.1.2 Other Restrictions 2-31

2.8.2 DTX/CNI Service Measurements 2-32

2.8.3 Feature Implementation 2-32

2.8.3.1 Executive Cellular Processor (ecp) Form 2-33

2.8.3.2 Series 2 Cell (cell2) Form 2-33

2.8.3.3 Face Code Information (fci) Form 2-33

2.8.3.4 Cellular Network (net) Form 2-332-33

2-33

2-33

2-33

2-32

2-32

2-31

2-29

2-29

2-29

2-28

2-26

2-26

2-26

2-25

2-25

2-25

2-24

2-23

2-23

2-23

2-21

2-20

2-20

2-19

2-19

2-18

2-16

2-15

2-12

2-12

2-11

vi June 2001



Contents

2.8.3.5 Subscriber and feature Information (sub andsoda) Form 2-34

2.8.3.6 Visitor Registration Information (vlr) Form 2-34

2.9 Digital Control Channel (DCCH) RF Planning 2-34

2.9.1 Recommended DCCH Channel Assignments 2-34

2.9.2 Two-DCCH Radio Deployment Scheme 2-35

2.9.3 Generalized Deployment Scheme 2-40

2.9.4 Channel Assignment Examples 2-42

2.10 Alignment of DCCH Reselection and DTC HandoffBoundaries 2-46

2.10.1 DCCH Sector-Types 2-46

2.10.1.1 Preferred Neighbors 2-47

2.10.1.2 Regular Neighbors 2-47

2.10.1.3 Non-Preferred Neighbors 2-47

2.10.2 Matching Handoff and Reselection Boundaries 2-47

2.10.2.1 Limitations on DCCH and Handoff Algorithm Matching 2-47

2.10.2.2 DCCH Translation Definitions 2-48

2.10.2.3 MAHO Related Translations 2-48

2.10.2.4 DCCH Translation Settings Common to All Neighbors 2-49

2.10.2.5 MAHO Translations Common to All Neighbors 2-49

2.10.2.6 MAHO Translations for Preferred Neighbors 2-50

2.10.2.7 MAHO Translations for Regular Neighbors 2-50

2.10.2.8 MAHO Translations for Non-Preferred Neighbors 2-51

2.11 TDMA Hierarchical Cells 2-51

2.11.1 Operation Requirements 2-52

2.11.1.1 TDMA Hierarchical Cells 2-52

2.11.1.2 TDMA Full Rate 2-52

2.11.1.3 Digital Control Channel (DCCH) Feature 2-52

2.11.1.4 TDMA Periodic Best Server Locate 2-52

2.11.2 Modeled After DCCH Reselection Algorithms 2-52

2.11.3 Handoff and DCCH Reselection Boundary Misalignment 2-53

2.11.3.1 MAHO Handoff Boundary 2-53

2.11.3.2 DCCH Reselection Boundary 2-532-53

2-53

2-53

2-52

2-52

2-52

2-52

2-52

2-52

2-51

2-51

2-50

2-50

2-49

2-49

2-48

2-48

2-47

2-47

2-47

2-47

2-47

2-46

2-46

2-42

2-40

2-35

2-34

2-34

2-34

2-34

June 2001 vii



Contents

2.11.3.3 Speed-Trending Optimization 2-54

2.11.4 Hierarchical Cells Algorithm and Parameters 2-55

2.11.5 Cell Type Parameter 2-60

2.11.6 H_DELAY Parameter 2-61

2.11.7 Handoff Criteria 2-62

2.11.7.1 Criteria 1 Qualifying Algorithm 2-62


2.11.7.3 Ranking of Handoff Candidates 2-64

2.11.7.4 Intra-Cell Handoff 2-64

2.11.8 Mobile Speed Trending 2-64

2.11.9 Periodic Handoff Triggering 2-66

2.11.10 Feature Interaction 2-66

2.11.10.1 DCCH Non-Public Network Identifiers (NPNI) 2-66

2.11.10.2 Hand-Off Based on Interference TDMA (HOBIT) 2-67

2.11.10.3 DCCH Interhyperband Operations (DIHOP1 andDIHOP2) 2-67

2.12 Two Branch Intelligent Antennas (TBIA) on the EDRU 2-67

2.13 Deployment Recommendations 2-68

2.13.1 Diversity Receive 2-68

2.13.2 Time Dispersion and Equalizers 2-69

2.13.3 MAHO Channel Assignment 2-69

2.13.3.1 Using ACC as MAHO Channel 2-69

2.13.3.2 Using Voice Channel as a MAHO Channel 2-70

2.13.3.3 Using DCCH as MAHO Channel 2-70

3 Hardware Installation


3.2 DTC and DCCH Feature Activation 3-1

3.2.1 Digital Traffic Channel (DTC) 3-2

3.2.2 Digital Control Channel (DCCH) 3-2

3.3 Hardware Installation 3-23-2

3-2

3-2

3-1

3-1

2-70

2-70

2-69

2-69

2-69

2-68

2-68

2-67

2-67

2-67

2-66

2-66

2-66

2-64

2-64

2-64

2-63

2-62

2-62

2-61

2-60

2-55

2-54

viii June 2001



Contents

3.3.1 Equipment Requirements 3-3

3.3.2 Pre-Installation Cell Inspection and Diagnostics 3-4

3.3.3 Power Down RCF 3-5

3.3.4 RTU/TRTU RF Switch Assembly Installation 3-5

3.3.4.1 Version G1 Installation 3-6


3.3.4.3 Install Control Cables 3-14

3.3.4.4 Connecting DC Power Cable 3-15

3.3.5 Radio Shelf Power Upgrade 3-15

3.3.5.1 Installing DRUs. 3-15

3.3.5.2 Installing EDRUs 3-15

3.3.5.2.1 Series II Classic Radio Frame 3-16

3.3.5.2.2 Series IIm Cabinet 3-16

3.3.5.2.3 Series IImm Cabinet 3-17

3.3.6 Power Converter Unit and Circuit Breaker Replacement 3-18

3.3.6.1 Replace Shelf Designation Labels(Customer Option) 3-19

3.3.7 Install TRTU and DRU(s) 3-19

3.3.8 Install T-EDRU and EDRU(s) 3-20

3.3.9 Test EDRU (T-EDRU) Personality 3-21

3.0.1 Restore Cell 3-24

3.0.1.1 Power Up Cell 3-24

3.0.1.2 Boot Cell 3-25

3.0.2 Modify RC/V Translations 3-25

3.1 Complete the Installation Process 3-25

3.1.0.1 Download Cell Site Generic 3-26

3.1.0.2 Hardware Testing 3-26

3.1.0.3 RF Measurements 3-27

3.1.0.4 Allow Call Processing 3-29

3.2 Receive Path Gain Measurements 3-30

3.2.1 Receive Path Gain 3-303-30

3-30

3-29

3-27

3-26

3-26

3-25

3-25

3-25

3-24

3-24

3-21

3-20

3-19

3-19

3-18

3-17

3-16

3-16

3-15

3-15

3-15

3-15

3-14

3-11

3-6

3-5

3-5

3-4

3-3

June 2001 ix



Contents

4 TDMA and DCCH Translations


4.2 DTC Database Settings 4-1

4.2.1 ECP (Executive Cellular Processor) Form 4-2

4.2.1.1 Max. No. of Mobile Requested Call Mode Changes 4-2

4.2.1.2 Mobile Assisted Handoff Bias - TDMA 4-2

4.2.1.3 INLA Threshold - TDMA (RSSI) 4-2

4.2.1.4 TDMA Test Mode Active 4-3

4.2.1.5 Differential Billing for Digital and Analog Time 4-3

4.2.1.6 Append Basic Digital Module to the AMA Record 4-3

4.2.1.7 Long List Weight Factor (LLWF) 4-4

4.2.1.8 Long List Interference Measurement Interval (LLIMI) 4-4

4.2.1.9 Short List Channel Update Interval (SLCUI) 4-4

4.2.1.10 Maximum Short List Length (MSLL) 4-5

4.2.1.11 Short List Uplink Weight Factor (SLUWF) 4-5

4.2.1.12 Short List Downlink Weight Factor (SLDWF) 4-5

4.2.1.13 Short List Interference Measurement Interval (SLIMI) 4-6

4.2.1.14 Number of Downlink Measurement for Valid DownlinkList (NDM) 4-6

4.2.1.15 Downlink Measurement Interval (DMI) 4-6

4.2.1.16 Maximum Candidate Channel List Length (MCCLL) 4-6

4.2.1.17 Adjacent Channel Use on Adjacent Sector Allowed 4-7

4.2.1.18 Short Order Bias 4-7

4.2.1.19 Server Group Channel Selection (SGCS) 4-7

4.2.1.20 Maximum Interference Threshold for Call Setup- Uplink (dB) 4-7

4.2.1.21 Maximum Interference Threshold for Call Setup- Downlink (dB) 4-8

4.2.1.22 Maximum Interference Threshold for handoff-- Uplink (dB) 4-8

4.2.1.23 Maximum Interference Threshold for handoff-- Downlink (dB) 4-8

4.2.1.24 Area Wide Test Channel (AWTC) - Cellular 4-84-8

4-8

4-8

4-8

4-7

4-7

4-7

4-7

4-6

4-6

4-6

4-6

4-5

4-5

4-5

4-4

4-4

4-4

4-3

4-3

4-3

4-2

4-2

4-2

4-2

4-1

4-1

x June 2001



Contents

4.2.2 CELL2 (Series II Cell Site Database) Form 4-9

4.2.2.1 Antenna Face Trunk Group List 4-9

4.2.2.2 Cell Generic - Version Name 4-9

4.2.2.3 Cell Generic - R5 Compatible 4-9

4.2.2.4 IS-54B Allowable Call Mode Override 4-9

4.2.2.5 Number of Simultaneous NVMs - TDMA 4-10

4.2.2.6 Voice Out of Service Limit -(%) TDMA 4-10


4.2.2.8 Cell Site Optional Features 4-11

4.2.2.9 ARR is Available for: Beacon Radio 4-11

4.2.2.10 ARR is Available for: Locate EDRU(L-EDRU) Radio 4-12

4.2.2.11 Authentication is Available on: Analog Control Channel 4-12

4.2.2.12 Number of Time Slots for DVCC Presence 4-12

4.2.2.13 DVCC Detection Timeout Time Slots 4-12

4.2.2.14 Bit Error Rate Threshold (%) 4-13

4.2.2.15 Frame Error Rate Threshold (%) 4-13

4.2.2.16 Mobile Assisted Handoff Bias 4-13

4.2.2.17 Mobile Requested Call Mode Change 4-14

4.2.2.18 DVCC Verification Active 4-14

4.2.2.19 Digital Locate Radio Equipage (Read-Only) 4-14




4.2.2.23 Network Transmission Level (dB) Rx for DRU/EDRU 4-15

4.2.2.24 Network Transmission Level (dB) Tx for DRU/EDRU 4-16

4.2.2.25 Handoff at Optimum Power - TDMA 4-16

4.2.3 NNBR (Network Neighbor) Form 4-16

4.2.3.1 SMS Capable 4-16

4.2.3.2 SMS Destination MC 4-16

4.2.3.3 Destination MC SSN 4-17

4.2.3.4 Handoff/Setup Optimum Power - TDMA 4-17

4.2.4 CEQCOM2 (Series II Cell Equipage Common) Form 4-174-17

4-17

4-17

4-16

4-16

4-16

4-16

4-16

4-15

4-15

4-15

4-14

4-14

4-14

4-14

4-13

4-13

4-13

4-12

4-12

4-12

4-12

4-11

4-11

4-10

4-10

4-10

4-9

4-9

4-9

4-9

4-9

June 2001 xi



Contents


4.2.4.2 TDMA Measurement Processing Interval 4-17

4.2.4.3 TDMA RTU DVCC 4-18

4.2.5 CEQSU2 (Series II Cell Equipage Setup) Form 4-18

4.2.5.1 Digital Color Code 4-18

4.2.5.2 Color Codes - 1st TDMA Supervisory Digital (SDCC) 4-18

4.2.5.3 Color Codes - 2nd TDMA Supervisory Digital (SDCC) 4-19

4.2.6 CEQFACE (Cell Equipage Common Face) Form 4-19

4.2.6.1 TDMA Voice Radio Attenuation Level 4-19

4.2.6.2 TDMA Fade Timer 4-20

4.2.6.3 Cell Site Attenuation Code 4-20

4.2.6.4 Two Branch Intelligent Antennas Active for DCCH 71) 4-21

4.2.6.5 FLCA Monitoring 4-21

4.2.6.6 Channel Set 4-21






4.2.6.12 Adjacent Channel Use on Adjacent Sector 4-23

4.2.7 CNTG (Cellular Network Trunk Group) Form 4-23

4.2.7.1 Analog Option on Digital Terminations 4-23

4.2.8 CTG (Cell Trunk Group) Form 4-23

4.2.8.1 Technology Type 4-24

4.2.9 ITG (Inter-switch Trunk Group) Form 4-24


4.2.10 LTG (Loop-around Trunk Group) Form 4-24


4.2.11 CTM (Cell Site Trunk Member) Form 4-25

4.2.11.1 Voice Radio - Channel Number 4-25

4.2.11.2 Voice Radio - Timeslot 4-25

4.2.11.3 DCA Interfering TNNs — TDMA PP 4-25

4.2.11.4 Voice Radio - Beacon 4-254-25

4-25

4-25

4-25

4-25

4-24

4-24

4-24

4-24

4-24

4-23

4-23

4-23

4-23

4-22

4-22

4-22

4-22

4-21

4-21

4-21

4-21

4-20

4-20

4-19

4-19

4-19

4-18

4-18

4-18

4-18

4-17

4-17

xii June 2001



Contents

4.2.11.5 Voice Radio - Radio Type 4-26

4.2.11.6 Voice Radio - Slot Number 4-26

4.2.11.7 TDMA Digital Verification Color Code 4-26

4.2.12 FCI (Face Code Information) Form 4-26

4.2.12.1 TDMA Sequential Trunk Hunt 4-26

4.2.12.2 Voice Channel Candidate Selection Threshold - Primary 4-27

4.2.12.3 Primary - Class III/IV 4-27

4.2.12.4 Voice Channel Candidate Selection Threshold--Digital Primary 4-27

4.2.12.5 Voice Channel Candidate Selection Threshold-- Digital Primary -Class III/IV 4-27

4.2.12.6 Voice Channel Candidate Selection Threshold-- Secondary 4-28

4.2.12.7 Threshold (RSSI) - Interference Protection at-Handoff (INTPHO) 4-28

4.2.12.8 INTPHO - Class III/IV 4-29

4.2.12.9 Threshold (RSSI) - TDMA INLA 4-29

4.2.12.10 TDMA Upward Hysteresis Adjustment (RSSI) 4-29

4.2.12.11 HOBIT Threshold - Downlink to AMPS 4-29

4.2.12.12 HOBIT Threshold - Uplink to Dual Mode 4-30

4.2.12.13 HOBIT Threshold - Downlink to Dual Mode 4-30

4.2.12.14 Dynamic Power Control (DPC) State - TDMA Mobile 4-30

4.2.12.15 Dynamic Power Control (DPC) State - TDMA Target 4-30

4.2.12.16 Dynamic Power Control (DPC) State - TDMA Window 4-31

4.2.12.17 Dynamic Power Control (DPC) State - TDMA Slope 4-31

4.2.12.18 BER - Control DPC Feature State 4-31

4.2.12.19 Mobile BER High Threshold 4-32

4.2.12.20 Mobile BER Low Threshold 4-32

4.2.12.21 Amplifier Power Differential (RSSI) 4-32

4.2.12.22 Delay Interval Compensation 4-33

4.2.12.23 MPC Correction/Offset for Class III/IV Mobiles 4-33

4.2.12.24 L-EDRU DVCC Verification Active 4-33

4.2.12.25 Hybrid MAHO/Digital Locate TDMA Handoff

4-33

4-33

4-33

4-32

4-32

4-32

4-31

4-31

4-31

4-30

4-30

4-30

4-30

4-29

4-29

4-29

4-29

4-28

4-28

4-27

4-27

4-27

4-27

4-26

4-26

4-26

4-26

4-26

June 2001 xiii



Contents

-Algorithm Active 4-34

4.2.12.26 Append MAHO Candidates to Hybrid MAHO/Digital- Locate 4-34

4.2.12.27 Up/Downlink Ranking Method for Hybrid MAHO/Digital-Locate 4-34

4.2.12.28 TDMA Periodic Locate Type 4-34

4.2.12.29 Thresholds: Mobile Signal 4-35

4.2.12.30 Thresholds: Mobile Secondary 4-36

4.2.12.31 Thresholds: TDMA Locate Reply Threshold 4-36

4.2.12.32 Digital Voice Mobile Attenuation Code 4-37

4.2.12.33 Minimum Handoff Interval for TDMA 4-37

4.2.12.34 Mobile Reported Signal Strength Averaging Samples- - TDMA 4-37

4.2.12.35 Mobile Reported BER Averaging Samples 4-37

4.2.12.36 TDMA DTX with Comfort Noise Insertion Active 4-37


4.2.12.38 MCCLL Maximum Candidate Channel List Length-(MCCL) 4-38

4.2.12.39 Maximum Interference Threshold for Call Setup-- Uplink (dB) 4-38

4.2.12.40 Maximum Interference Threshold for Call Setup-- Downlink (dB) 4-39

4.2.12.41 Maximum Interference Threshold for handoff-- Uplink (dB) 4-39

4.2.12.42 Maximum Interference Threshold for handoff-- Downlink(dB) 4-39

4.2.12.43 Mobile Assisted Handoff List 4-39

4.2.13 SHTG (Speech Handler Trunk Group) Form 4-43

4.2.13.1 DCS-E Switch Identification 4-43

4.2.13.2 Trunk Group Number 4-43


4.2.13.4 Service Type 4-44

4.2.14 SUB (Subscriber and Feature Information) Form 4-44

4.2.14.1 Mobile Directory Number Type 4-44

4.2.14.2 Short Messess Service: Termination Restricted 4-444-44

4-44

4-44

4-44

4-43

4-43

4-43

4-43

4-39

4-39

4-39

4-39

4-38

4-38

4-38

4-37

4-37

4-37

4-37

4-37

4-36

4-36

4-35

4-34

4-34

4-34

4-34

xiv June 2001



Contents

4.2.14.3 Short Messess Service: Origination Restricted 4-44

4.2.15 TPPTM (TDMA Packet Pipe Trunk Member) Form 4-45


4.2.15.2 Packet Pipe - Trunk Group Number 4-45

4.2.15.3 Packet Pipe - Trunk Member Number 4-45

4.2.15.4 Trunk Status 4-45

4.2.15.5 Switching Module 4-46

4.2.15.6 Server Group 4-46

4.2.15.6.1 Default = 0 4-46

4.2.15.7 Physical Antenna - Receive 4-46

4.2.15.8 Physical Antenna - Transmit 4-46

4.2.15.9 Packet Pipe Data Rate Kbps 4-46

4.2.15.10 Connection - DS0 4-47

4.2.15.11 Connection - DS1 4-47

4.2.15.12 Voice Radio Information — Number 4-47

4.2.15.13 Voice Radio Information —Timeslot 1, Timeslot 2,-Timeslot 3 4-47

4.2.15.14 Voice Radio Information —Type 4-47

4.2.15.15 Voice Radio Information —Frame Number 4-48

4.2.15.16 Voice Radio Information —Shelf Number 4-48

4.2.15.17 Voice Radio Information —Slot Number 4-48

4.2.15.18 Voice Radio Information —Channel 4-48

4.2.15.19 Voice Radio Information — Beacon 4-48

4.2.15.20 Voice Radio Information — DVCC 4-49

4.2.15.21 Voice Radio Information — Mobile Power Class 4-49

4.2.15.22 Voice Radio Information — LAC Number 4-49

4.2.15.23 Dynamic Channel Allocation - Active 4-49

4.2.15.24 DCA Interfering TNNs 4-50

4.2.16 TPPTG (TDMA Packet Pipe Trunk Group) Form 4-50

4.2.16.1 Switch Identification 4-50


4.2.16.3 Cell Site Number 4-51

4.2.16.4 Number of Trunks 4-514-51

4-51

4-50

4-50

4-50

4-50

4-49

4-49

4-49

4-49

4-48

4-48

4-48

4-48

4-48

4-47

4-47

4-47

4-47

4-47

4-46

4-46

4-46

4-46

4-46

4-46

4-45

4-45

4-45

4-45

4-45

4-44

June 2001 xv



Contents

4.2.17 Summary of DTC Performance Database Translations 4-51

4.3 DCCH Performance Database Settings 4-57


4.3.1.1 Page Only if MS (Mobile Station) Last Accessed-on DCCH 4-58

4.3.1.2 DCCH Activity Timeout Interval 4-58

4.3.1.3 DCCH Activity Timeout Allowed 4-59

4.3.1.4 TDMA DCCH Information: Signal Strength Meas.-Interval 4-59

4.3.1.5 TDMA DCCH Information: Info. Word Transmission-Rate 4-59

4.3.1.6 TDMA DCCH Information: Maximum Busy/Reserved 4-59

4.3.1.7 TDMA DCCH Information: Maximum Stop Counter 4-60

4.3.1.8 TDMA DCCH Information: Maximum Repetitions 4-60

4.3.1.9 TDMA DCCH Information: Maximum Retries 4-60

4.3.2 NET (Cellular Network) Form 4-60

4.3.2.1 Technology to Page 4-61

4.3.2.2 Final Technology to Page 4-61

4.3.3 CGSA (Cellular Geographic Service Area) Form 4-61

4.3.3.1 DCCH Virtual Mobile Location Area 4-61

4.3.3.2 DCCH Alphanumeric SID (ASID) 4-61

4.3.3.3 DCCH ASID Active 4-62

4.3.3.4 System Operator Code 4-62

4.3.3.5 IS-136 Emergency Routing Number 4-62

4.3.3.6 Registration Periodicity (min.) 4-62



4.3.4.2 IS-136 Allowable Call Mode Override 4-63

4.3.4.3 Should Home Mobiles Register-DCCH 4-63

4.3.4.4 Should Roamer Mobiles Register-DCCH 4-64

4.3.4.5 TDMA DCCH Registration Periodicity (min) 4-64

4.3.4.6 Power-Up/Power-Down Registration-DCCH 4-64

4.3.4.7 Location Area ID Registration-DCCH 4-644-64

4-64

4-64

4-64

4-63

4-63

4-63

4-63

4-62

4-62

4-62

4-62

4-61

4-61

4-61

4-61

4-61

4-60

4-60

4-60

4-60

4-59

4-59

4-59

4-59

4-58

4-58

4-58

4-57

4-51

xvi June 2001



Contents

4.3.4.8 TDMA DCCH Deregistration 4-65

4.3.4.9 Series II Cell Optional Feature List 4-65

4.3.4.10 ARR Available for TDMA DCCH Radio 4-65

4.3.4.11 Authentication Available for TDMA DCCH 4-66

4.3.5 CEQCOM2 (Series II Cell Equipage Common) Form 4-66

4.3.5.1 Functional Test Interval-TDMA DCCH Radio 4-66


4.3.6.1 All Servers Busy Directed Retry-DCCH 4-66

4.3.6.2 Inadequate Signal Strength Directed Retry for DCCH. 4-66

4.3.6.3 Directed Retry Threshold-DCCH 4-67

4.3.6.4 SG0 Access Threshold-DCCH 4-67

4.3.6.5 Info. Word Transmission Rate 4-67

4.3.6.6 Mobile Attenuation Code 4-68

4.3.6.7 Mobile Access Threshold 4-68

4.3.6.8 Setup Access Threshold 4-69

4.3.6.9 Mobile Reselection Threshold 4-70

4.3.6.10 Access Burst Size 4-70

4.3.6.11 Signal Strength Meas. Interval 4-70

4.3.6.12 Reselection Delay 4-71

4.3.6.13 Mobile Desired Service Bias 4-72

4.3.6.14 Initial Selection Control 4-72

4.3.6.15 Last Try Code (Directed Retry) 4-73

4.3.6.16 Network Type - Public / Private / Residential 4-73

4.3.6.17 PSID/RSID Indicator 4-73

4.3.6.18 PSID/RSID Value 4-73



4.3.7.2 TDMA DCCH Channel Number 4-74

4.3.7.3 TDMA DCCH Digital Verification Color Code 4-74

4.3.7.4 Control Channel Reselection Parameters: Protocol-Version 4-74

4.3.7.5 Control Channel Reselection Parameters: Mobile-Attenuation Code 4-754-75

4-74

4-74

4-74

4-74

4-74

4-73

4-73

4-73

4-73

4-72

4-72

4-71

4-70

4-70

4-70

4-69

4-68

4-68

4-67

4-67

4-67

4-66

4-66

4-66

4-66

4-66

4-66

4-65

4-65

4-65

June 2001 xvii



Contents

4.3.7.6 Control Channel Reselection Parameters: Mobile-Access Threshold 4-75

4.3.7.7 Control Channel Reselection Parameters:-Mobile Reselection Threshold 4-76


4.3.8.1 DCCH Shortened Burst on Call Setup 4-76

4.3.9 DCCH (Digital Control Channel) Form 4-76

4.3.9.1 Series II Cell Site Number 4-77

4.3.9.2 Voice Radio Number 4-77

4.3.9.3 Voice Radio Channel Number 4-77

4.3.9.4 Digital Verification Color Code 4-77

4.3.9.5 Status-Timeslot 1 4-77

4.3.9.6 Physical Antenna-Receive 4-78

4.3.9.7 Physical Antenna-Transmit 4-78

4.3.9.8 Linear Amplifier Circuit Number 4-78

4.3.9.9 Frame Number 4-78

4.3.9.10 Shelf Number 4-79

4.3.9.11 Slot Number 4-79

4.3.10 RESEL (Reselection List for Control Channels) Form 4-79

4.3.10.1 Cell Site 4-79

4.3.10.2 PAF 4-79

4.3.10.3 Tech 4-79

4.3.10.4 Chan 4-80

4.3.10.5 DCC/DVCC 4-80

4.3.10.6 Directed Retry 4-80

4.3.10.7 Type 4-80

4.3.10.8 Delay 4-81

4.3.10.9 Offset Bias 4-82

4.3.10.10 Hi/Lo Freq 4-82

4.3.10.11 Extended Sys. ID - DCS/ECP/SYS 4-83

4.3.10.12 Network Type - Pub/Priv/Res 4-83

4.3.10.13 Prot Ver 4-83

4.3.10.14 Atten 4-834-83

4-83

4-83

4-83

4-82

4-82

4-81

4-80

4-80

4-80

4-80

4-79

4-79

4-79

4-79

4-79

4-79

4-78

4-78

4-78

4-78

4-77

4-77

4-77

4-77

4-77

4-76

4-76

4-76

4-76

4-75

xviii June 2001



Contents

4.3.10.15 RSS Access 4-84

4.3.10.16 RESEL Thrsh 4-85

4.3.11 Summary of DCCH Performance Database 4-85

5 Technician Interface


5.2 Status Display Pages 5-1

5.2.1 Video States for Display Pages 5-2

5.2.2 APX Index Display Page - 2100 5-6

5.2.3 Cell Site Status Summary DisplayPage - 2130 5-7

5.2.4 Cell Equipment Status Page 2131 5-9

5.2.5 Cell Software Status Page 2132 5-13

5.2.6 Series II Cell Site Voice Radio Status Page 2133 5-19

5.2.7 Cell LC/SU/BC Status Display Page2135 5-24

5.2.8 Cell DCCH Radio Status Page 2235 5-27

5.3 TDMA/DCCH Technician Interface (TI) Messages 5-30

5.3.1 TI Input Messages 5-30

5.3.2 TDMA/DCCH TI Output Messages 5-34

6 Service Measurements and System Performance Metrics


6.2 TDMA Service Measurements 6-1

6.3 System Performance Metrics 6-25

6.3.1 Busy Hour Determination 6-25

6.3.2 Cell Metrics 6-25

6.3.3 LAF Metrics 6-25

6.3.4 Performance Metrics 6-256-25

6-25

6-25

6-25

6-25

6-1

6-1

5-34

5-30

5-30

5-27

5-24

5-19

5-13

5-9

5-7

5-6

5-2

5-1

5-1

4-85

4-85

4-84

June 2001 xix



Contents

6.3.5 %Established Calls 6-26

6.3.5.1 Calculation 6-26

6.3.5.2 Goal 6-26

6.3.5.3 Typical Numbers 6-26

6.3.5.4 Possible Causes Of Low Percentage Of Established-Calls 6-26

6.3.5.4.1 Most Likely Cause 6-27

6.3.5.5 Recommended Steps For Investigation: 6-27

6.3.6 %Lost Calls Per LAF 6-28


6.3.6.2 Goal 6-28

6.3.6.3 Typical Number 6-28

6.3.6.4 Possible Causes Of High % Lost Call 6-28

6.3.6.5 Recommended Steps For Investigation 6-29

6.3.7 %Lost Calls Per Erlang 6-30


6.3.7.2 Goal 6-30


6.3.7.4 Reasons For High Lost Calls Per Assignment 6-30


6.3.8 % Handoffs Complete (Cell & LAF) 6-31

6.3.8.1 Goal 6-31


6.3.8.3 Possible Causes 6-31

6.3.8.4 Most Likely Cause 6-31


6.3.9 %Dropped At Handoff 6-32


6.3.9.2 Goal 6-32




6.3.10 %Subscriber Blocking 6-326-32

6-32

6-32

6-32

6-32

6-32

6-32

6-31

6-31

6-31

6-31

6-31

6-31

6-30

6-30

6-30

6-30

6-30

6-30

6-29

6-28

6-28

6-28

6-28

6-28

6-27

6-27

6-26

6-26

6-26

6-26

6-26

xx June 2001



Contents


6.3.10.2 Goal 6-33


6.3.10.4 What To Do Next (If You Encounter High Blocking) 6-33

6.3.11 % Cell Trunk Group Blocking 6-34



6.3.11.3 When You Should Investigate 6-36

6.3.11.4 Reasons For High Percentage 6-36

6.3.11.5 What To Do Next (When High Blocking is Encountered) 6-37

6.3.12 %Cell Trunk Group Utilization 6-37


6.3.12.2 Goal 6-38




6.3.12.6 Reasons For Low Percentage 6-39

6.3.12.7 What To Do Next 6-39

7 Optional Features


7.2 Optional Features 7-2

7.2.1 Call Number Identification Presentation (CNIP) 7-2

7.2.2 Message Waiting Indicator (MWI) 7-3

7.2.3 Interference Look Ahead (INLA) 7-3

7.2.3.1 INLA Functionality 7-3

7.2.3.2 INLA-Related Service Measurements 7-4

7.2.4 Handoff Based on Interference (HOBIT) for TDMA 7-4

7.2.4.1 HOBIT Enhancement (HOBITE) 7-5

7.2.4.1.1 HOBIT Enhancement Threshold 7-5

7.2.4.1.2 HOBIT/INLA Enhancement 7-67-6

7-5

7-5

7-4

7-4

7-3

7-3

7-3

7-2

7-2

7-1

6-39

6-39

6-39

6-38

6-38

6-38

6-37

6-37

6-37

6-36

6-36

6-36

6-34

6-34

6-33

6-33

6-33

6-33

June 2001 xxi



Contents


7.2.6 Authentication (AUTH) 7-7

7.2.7 Enhanced Registration 7-7

7.2.8 Digital Locate 7-7

7.2.9 L-EDRU Digital Locate 7-7

7.2.9.1 Digital Locate Function 7-8

7.2.9.2 DVCC Verification with Radio Signal Strength I-ndication (RSSI) 7-9

7.2.9.3 Mobile Saturation Resolution 7-9

7.2.10 Voice Privacy 7-10

7.2.11 Short Message Service (SMS) Over Digital Control-Channel (DCCH) 7-10

7.2.11.1 Mobile-Terminated Operation 7-10

7.2.11.2 Mobile-Originated Operation 7-11

7.2.12 ACELP Vocoder 7-12

7.2.13 Interhyperband Operation 7-12

7.2.13.1 Interhyperband Phase I 7-12

7.2.13.1.1 RC/V Parameters 7-13


7.2.13.2 Interhyperband Phase II 7-13

7.2.13.3 Rogue Mobile Identification 7-13

7.2.13.4 Service Measurements (SM) Overhaul 7-14

7.2.14 Non-Public Network Identifiers (NPNI) and Charging-Area Feature 7-14

7.2.15 Carrier-Specific Teleservices Transport 7-15

7.2.15.1 Interim Over-the-Air Activation 7-15

7.2.15.2 Intelligent Roaming 7-16

7.2.15.3 Expanded Sub-System Numbers 7-16

A Traffic Capacity Data A

A.1 Separated System A-1

1.2 Integrated System A-8A-8

A-1

7-16

7-16

7-15

7-15

7-14

7-14

7-13

7-13

7-13

7-13

7-12

7-12

7-12

7-11

7-10

7-10

7-10

7-9

7-9

7-8

7-7

7-7

7-7

7-7

7-6

xxii June 2001



Contents

B Handoff Candidate List Generation B

C Link Budget C

C.1 Introduction C-1

C.2 Creating the Link Budget C-1

C.2.1 Same Coverage Footprint for DTCs and DCCHs C-1

C.2.2 Balanced Link C-2

C.2.3 Receive Path C-3

C.2.4 Transmit Path C-10

Figure

1-1 Forward Digital Voice Channel Processing, Simplified BlockDiagram 1-20

1-2 Reverse Digital Voice Channel Processing, SimplifiedBlock Diagram 1-22

1-3 DCCH Logical Channels 1-271-4 dcch RC/V Form 1-301-5 DDPC Transmit Power Waveforms 1-542-1. Traffic Flow for an Integrated AMPS/TDMA Stream 2-92-2. DCCH SMS Capacity as a Function of IS-136 Mobile Penetration 2-152-3. SMS Capacity for Two DCCHs in a Sector 2-162-4. DCCH SMS Capacity with a Paging Load of 15 Pages/Seconds 2-172-5. Comparison of TDMA and Analog Channels 2-242-6 Cell Cluster Array for Reuse Factor of 7 2-282-7. Comparison of C/Ico-DTC and C/Ico-DCCH During Off-Peak Hours 2-372-8. DCCH Assignment Using Two Distinct TDMA Radios for DCCHs,

First Tier Line-Up Pattern 2-382-9. DCCH Assignment Using Two TDMA Radios for DCCHs, General

Line-up Pattern 2-392-10. DCCH Assignment Using Three Distinct TDMA Radios for DCCHs 2-412-41

2-39

2-38

2-372-282-242-172-162-152-91-541-301-271-22

1-20

C-10

C-3

C-2

C-1

C-1

C-1

June 2001 xxiii



Contents

2-11. Example of A-Band DCCH Assignment 2-442-12. Example of B-Band DCCH Assignment 2-452-13. Mobile Speed Discrimination 2-653-1. Mounting RTU/TRTU Switch Assembly, Version G1 3-63-2. AYD8 Circuit Board Layout 3-93-3. Shelf 3 Backplane Pin Layout at EQL Position 156 1-303-4. Mounting RTU/TRTU Switch Assembly, Version G2 3-125-1. Status Display Page Hierarchy 5-35-2. Example of 2100 - APX Index Page—ECP Release 7.0 5-75-3. Example of 2130 - Cell Site Status Summary Page 5-85-4. Example of 2131 - Series II Cell Site Equipment Status Pagewithout

the OTU/LMT feature—ECP Release 7.0 5-105-5. Example of 2131 - Series II Cell Site Equipment Status Page with

the OTU/LMT Feature—ECP Release 7.0 5-105-6. Example of 2132 - Series II Cell Site Software Status Page

(withoutthe OTU/LMT Feature)—ECP Release 8.0 5-145-7. Example of 2132 - Series II Cell Site Software Status Page

(with the OTU/LMT Feature)—ECP Release 8.0 5-155-8. Example of 2132 - Series II Cell Site Software Status Page (without

the OTU/LMT Feature 5-165-9. E xample of 2132 - Series II Cell Site Software Status Page

(with the OTU/LMT Feature)—ECP Release 7.0 5-175-10. Example of 2133 - Series II Cell VR Status Page—ECP Release 8.0 5-205-11. Example of 2133 - Series II Cell VR Status Page—ECP Release 7.0 5-215-12. Example of 2135 - Series II Cell Site LC/SU/BC Status Page—

ECP Release 8.0 5-255-13. Example of 2135 - Series II Cell Site LC/SU/BC Status Page—

ECP Release 7.0 5-265-14. Example of 2235 - Series II Cell Site DCCH Status Page —

ECP Release 8.0 5-285-15. Example of 2235 - Series II Cell Site DCCH Status Page—

ECP Release 7.0 5-295-29

5-28

5-26

5-25

5-215-205-17

5-16

5-15

5-14

5-10

5-10

5-85-75-33-121-303-93-62-652-452-44

xxiv June 2001



Contents

Tables

2-1 FLCA-LM RC/V Parameters 2-15

2-2 Maximum 3-Sector Total TDMA LAF-28 Countsf or One and Two L-EDRUs 2-26

2-3 Maximum Omni Cell Total TDMA LAF-28 Countsfor One L-EDRU 2-29

2-4 FLCA-DA RC/V Parameters 2-39

2-5 Test Acceptance Threshold Adjustments 2-48

2-6 User Channel Variable Assignment 2-68

2-7 Proposed Downlink Average Adjustment Determination 2-69

3-1 Channel Assignments in a Nine-Cell/27-Sector Cluster 3-10

3-2 Channel Set Assignments in a Three-Cell, Nine-Sector Cluster 3-11

3-3 Alternate Channel Set Assignments in a Three-Cell,Nine-Sector Cluster 3-12

3-4 Fixed Channel Seven-Cell, 21-Sector Cell Cluster 3-13

3-5 FLCA Three-Cell, Nine-Sector Cluster 3-14

3-6 Recommended Cell Inventory and Data Collection forFLCA Implementation 3-25

4-1 Cellular Channel Numbers 4-6

4-2 PCS Channel Numbers 4-64-6

4-6

3-25

3-14

3-13

3-12

3-11

3-10

2-69

2-68

2-48

2-39

2-29

2-26

2-15

June 2001 xxv



Contents

xxvi June 2001



Introduction


1.1.1 Reason for Reissue 1-1

1.1.2 Previous Issues 1-2

1.1.3 Intended Audience 1-7

1.1.4 Prerequisite Skills and Knowledge 1-7

1.1.5 Purpose 1-8

1.1.6 Document Organization 1-8

1.2 Software and Hardware Requirements 1-9

1.2.1 Software 1-9

1.2.2 Hardware 1-9

1.3 TDMA Overview 1-10

1.3.1 Radio Access Method 1-11

1.3.2 DRU and EDRU Configurations 1-12

1.3.3 Digital Mobiles 1-12

1.3.4 TDMA Call Processing 1-12

1.3.4.1 TDMA Call Setup 1-12

1.3.4.2 Handoff 1-13

1.3.4.2.1 Difference Between AMPS and TDMA Handoff 1-13

1.3.4.2.2 DCCH Information on an Analog Voice Channel 1-14

1.3.4.2.3 MAHO Translations 1-14

1.3.4.2.4 Handoff Triggers 1-151-15

1-14

1-14

1-13

1-13

1-12

1-12

1-12

1-12

1-11

1-10

1-9

1-9

1-9

1-8

1-8

1-7

1-7

1-2

1-1

1-1

June 2001 1-1

Contents

1.3.4.2.5 Generating Handoff Candidate List 1-15

1.3.4.2.6 Digital Locate 1-15

1.3.4.3 Interhyperband Operation 1-16




1.3.5 Dynamic Power Control with BER 1-17

1.3.6 TDMA Voice Channel Confirmation 1-18

1.3.6.1 Time Alignment 1-18

1.3.6.2 Digital Verification Color Code (DVCC) 1-19

1.3.6.3 Measurement Order Message 1-19

1.3.7 Digital Radio Voice Channel Processing 1-19

1.3.7.1 Forward Digital Voice Channel Processing 1-20

8-Bit to 14-Bit Transcoding 1-20ACELP Speech Encoder 1-21Channel Coding 1-21Voice Encryption 1-21Bit Interleaving 1-21

1.3.7.2 Reverse Digital Voice Channel Processing 1-22

Delay Equalizer, Bit-De-Interleaving and Voice Description 1-22Channel Decoding 1-23Echo Canceller 1-23

1.3.7.3 Vocoder and Echo Canceller Location 1-23

Advantage 1-24Packet Pipe Transport Mode 1-24Hardware Requirements 1-24Switch Based TDMA Vocoder Feature Implementation 1-25

1.4 Digital Control Channel (DCCH) Overview 1-25

1.4.1 Transmission Format 1-26

1.4.2 Relationship with the ACC 1-26

1.4.3 Logical Channel Structure 1-26

1.4.3.1 Reverse DCCH 1-27

1.4.3.2 Forward DCCH 1-27

1.4.4 Multiple DCCH Feature 1-28

1.4.4.1 Deployment Considerations 1-281-28

1-28

1-27

1-27

1-26

1-26

1-26

1-25

1-251-241-241-24

1-23

1-231-231-22

1-22

1-211-211-211-211-20

1-20

1-19

1-19

1-19

1-18

1-18

1-17

1-17

1-17

1-16

1-16

1-15

1-15

1-2 401-200-112, Issue 11 June 2001


Contents

1.4.4.2 Turning On the Multiple DCCH Feature 1-29

1.4.4.3 Equipping Multiple DCCH Timeslots on an EDRU 1-29

Remove DCCH Radio 1-29Remove Voice Channels 1-29dcch Form Update 1-29Restore EDRU 1-30

1.4.4.4 Turning Multiple DCCH Feature Off 1-30

Remove DCCH Radio 1-30dcch Form Update 1-31Equip Voice Channels 1-31Turn Off MDCCH Feature 1-31Restore EDRU 1-31

1.5 TDMA Call Processing 1-31

1.5.1 Call Processing Overview 1-32

1.5.1.1 Call Origination and Termination 1-32

1.5.1.2 Call Processing Detail Description 1-33

1.5.1.2.1 Autonomous Registration 1-33

1.5.1.2.2 Reselection 1-35

Cell Type 1-35Signal Strength Averaging 1-36High/Low Frequency Option 1-36Signal Strength Qualification 1-36Best-Server Algorithm 1-37Absolute Signal Strength Algorithm 1-37

1.5.1.2.3 Separate Access Thresholds for DCCH and DTC Channels 1-38

1.5.1.2.4 Mobile Assisted Channel Allocation (MACA) 1-39

Directed Retry Feature 1-39Logical Face Assigned on Dual Server Group Cells 1-40

1.5.1.3 Call Setup 1-40

1.5.1.3.1 Paging 1-40

1.5.1.3.2 Accessing 1-41

Initial Traffic Channel Designation Message 1-41Automatic Retransmission Request (ARQ). 1-41

1.5.1.3.3 Initial Traffic Channel Confirmation 1-41

Time Alignment 1-41Digital Verification Color Code (DVCC) 1-421-42

1-41

1-41

1-411-41

1-41

1-40

1-40

1-401-39

1-39

1-38

1-371-371-361-361-361-35

1-35

1-33

1-33

1-32

1-32

1-31

1-311-311-311-311-30

1-30

1-301-291-291-29

1-29

1-29

Issue 11 June 2001 1-3


Contents

Measurement Order Message 1-42

1.5.1.3.4 Increased TDMA MAHO List 1-42

FLCA Downlink Monitoring 1-43Mobile Protocol Version Distinction 1-43ITML Service Measurement 1-44

1.5.1.4 Call-In-Progress 1-45

1.5.1.4.1 Mobile Assisted Handoff (MAHO) 1-46

MAHO neighbor list 1-46MAHO Channel 1-46

1.5.1.4.2 RF Signal Quality Measurements 1-46

1.5.1.4.3 MAHO Threshold Parameter 1-47

1.5.1.4.4 Standard MAHO Candidate Selection 1-48

Signal Strength Normalizing 1-48Standard MAHO Candidate List 1-49L-EDRU Digital Locate Feature 1-49

1.5.1.4.5 Dynamic Power Control (DPC) 1-50

Feedback Mechanism 1-50Reducing Interference 1-50

1.5.1.4.6 Uplink Dynamic Power Control (UDPC) 1-50

Receiver Overload 1-50RF Interference 1-51UDPC Defining Translation Parameters 1-51

1.5.1.4.7 Downlink Dynamic Power Control (DDPC) 1-52

DDPC for All TDMA Mobiles 1-52

1.5.2 DCCH Call Processing States 1-55

1.5.3 Advanced Features for DCCH 1-55

1.5.4 Message Center 1-56

1.6 Technician Interface 1-57

1.7 Recommendations 1-57


1.7.2 Dual Server Group Cells 1-58

1.7.3 MAHO Channel/Beacon Channel 1-58

1.7.4 Shortened Burst 1-59

1.7.5 Color Codes 1-601-60

1-59

1-58

1-58

1-58

1-57

1-57

1-56

1-55

1-55

1-52

1-52

1-511-511-50

1-50

1-501-50

1-50

1-491-491-48

1-48

1-47

1-46

1-461-46

1-46

1-45

1-441-431-43

1-42

1-42

1-4 401-200-112, Issue 11 June 2001


Contents

1.7.6 Audio Levels 1-60

1.8 Conclusion 1-611-61

1-60

Issue 11 June 2001 1-5


Contents

1-6 401-200-112, Issue 11 June 2001



Introduction 1

1.1 Introduction

This document provides implementation guidelines to upgrade an existingAUTOPLEX System 1000, Series II cell site for Time Division Multiple Access(TDMA) and Digital Control Channel (DCCH) capability.

Lucent Technologies provides cellular engineering services to help you plan foreffective implementation of your cellular system. If you need assistance with anystage of planning and implementing your system, please see your LucentTechnologies Account Executive.

1.1.1 Reason for Reissue

This reissue of this manual is impacted by the maximum cell number from 222 to384 provided in release R17.0.

1.1.2 Previous Issues

Issue 10 cover the Increased TDMA MAHO List (ITML) optional feature (refer toParagraph 1.5.1.3.4) that doubled the size of the MAHO Measurement Order/Hyperband Measurement Order (MO/HMO) list from 12 to 24. This featureintroduces a new maho RC/V form to allow the entry of 12 MAHO neighbors inaddition to the 12 MAHO neighbors that are originally populated via the fci form.The ITML feature can only be used on IS-136-Rev 0 or later mobiles. Early IS-54B mobiles, which can only receive a 12-channel MAHO neighbor order list, arenot qualified to comply with the ITML feature.

June 2001 1-1

Introduction

The three IS-136 mobile protocol versions may be separately enabled to respondto the ITML feature via enabling parameters on the ecp form. Should a serviceprovider discover that, due to external conditions, a predominance of ITMLfailures are associated with a particular mobile protocol version, the ecpparameter may be set to disqualify that mobile protocol version from complyingwith the ITML feature. Any disqualified mobile protocol version will receive amaximum of 12 MAHO neighbor channels. The ITML feature introduces six newservice measurements to monitor how well each mobile protocol type responds toITML. If a high number of failures are recorded for a particular mobile protocolversion, the enabling parameter for that version may be set to "n".

Issue 9 covered the Hybrid MAHO Digital Locate (HMDL) with InterHyperbandHandoff (HMDL-IH) enhancement impacted by Release 16.0. The HMDL-IHenhancement allows service providers to utilize the existing HMDL feature anddual interhyperband operation (DIHOP) features concurrently. Prior to Release16.0, the DIHOP feature must be turned on when the MAHO neighbor list includecandidates in the other hyperband. However, when the DIHOP feature is turnedon, the HMDL feature is automatically turned off. Therefore, the service providersmust use the HMDL and DIHOP feature exclusively.

Issue 7 incorporates Multiple DCCH on one Radio impacted by Cell releaseR15.1. In addition, in lieu its dedicate planning and implementing guide (401-200-120), the detail coverage of the Flexiable Channel Allocation (FLCA) feature hasbeen curtailed for this and subsequent issues of this manual. The functions andcapabilities of FLCA have been expanded in release R15.1 to full FLCA operationon cells containing Auto-Tune Cavity Combiners (ATCC) such as the Series IImand PCS minicells, in addition to increase capacity of 36 radios per sector, ShortList preservation, and short list downlink average adjustment based on BERclass.

A brief discussion of Multiple DCCH on one Radio and the expanded FLCAcapabilities are given in the following text, however, refer to Flexiable ChannelAllocation (FLCA) Planning And Implementing Guide, 401-200-120, for a detaileddescription of the expanded FLCA capabilities.

Multiple DCCH on one Radio This feature allows the service provider to equipup to three DCCH channels on a single digital radio, permitting up to nine DCCHchannels on a sector. When used on sectors with multiple DCCH channels, thisfeature reduces interference because fewer radios will have to be on all the timeRefer to Paragraph 1.4.4),.

FLCA Cells Containing Auto-tune Cavity Combiners (ATCC)

In Series IIm minicells that uses ATCC, the transmit output of radios are amplifiedand then combined using an auto tune cavity combiner, before being routed to theantenna for transmission. The output of each radio is amplified and then fed to asingle cavity in the auto-tune cavity combiner. The cavity is separately tuned tothe radio transmit frequency by an adjuster consisting of a piston that is

1-2 401-200-112, Issue 11 June 2001


Introduction

mechanically driven to adjust the cavity resonant frequency. The mechanicaltuning time, taking up to five seconds, is too long for FLCA dynamic channelassignment.

To implement FLCA-DA on ATCC cells, two conditions must be considered:

■ Tuning time delay — Each time the FLCA radio is assigned a new channel,its associated ATCC cavity must be retuned to the new RF channel.Because mechanical tuning is used, a tuning delay is introduced.

■ RF Channel Separation — Because a number of channels feed a single 4-to-1 ATCC, or an 8- or 12-to-1 ATCC combination, channel frequencyseparation must be maintained, ensuring channel isolation to avoid carrierinteraction.

To compensate for ATCC tuning delays and to provide FLCA real-time channelallocation for call processing, unlike non-ATCC cells, FLCA radios are pre-tunedto idle channels prior to call processing assignment. In this way, when a call setupor handoff assignment is received, the radio is ready to process the call (refer toFlexiable Channel Allocation (FLCA) Planning And Implementing Guide, 401-200-120).

FLCA Short List Preservation

When the load balancing algorithm is triggered the FLCA list monitoring task maybe moved between L-EDRUs, causing the list monitoring activity to be brieflyinterrupted. This interruption is kept at minimum if a Short List already exist andwas updated within 10 minutes prior to moving the load monitoring between L-EDRUs. When these conditions exist, the Short List channel uplink averagescopied on to the Long List and normal weighted averaging of these channels areresumed. The uplink averages for the other Long List channels that are not on theShort List are initially set to zero (refer to Flexiable Channel Allocation (FLCA)Planning And Implementing Guide, 401-200-120).

FLCA Short List Downlink Average Adjustment Based On BER Class

When one or more timeslots of a FLCA radio are busy, it is not possible to usemobile-reported downlink measurements of the FLCA channel that is assigned tothe radio. The MAHO-reported measurements for that channel are discarded bythe RCC as long as at least one timeslot of the channel is active. Instead, thedownlink bit error rate (BER) class values and signal levels reported by themobiles on the active channel are used to adjust the short list downlink averagefor that channel. When all timeslots of the FLCA channel become idle, thenmobile-reported interference measurements of the channel are again used indetermining the downlink average interference level (refer to Flexiable ChannelAllocation (FLCA) Planning And Implement ion Guide, 401-200-120).

401-200-112, Issue 11 June 2001 1-3


Introduction

The major changes in Issue 7 includes: Dynamic Allocation (FLCA-DA),Hierarchical Cells Speed Trending Optimization and Dynamic Downlink PowerControl.

Flexible Channel Allocation - Dynamic Allocation (FLCA-DA) — FLCA-DA issecond of two features that are required to implement FLCA. The first featureFLCA-LM should be fully implemented and optimized before FLCA-DA is enabled.This manual only introduces and describes the concept of FLCA-LM and FLCA-DA Paragraph 2.7),. A separate manual, Flexible Channel Allocation (FLCA)Planning and Implementation Guide, 401-200-120, is dedicated to describe FLCAimplementation is detail.

Hierarchical Cells Speed Trending Optimization — Speed -TrendingOptimization introduces three new translation parameters, to the hierarchicalfeature that was introduced in release R14.0. The Hierarchical Cells feature forthe more part uses the same mechanism designed for DCCH reselection to selectan hierarchical handoff and in R14.0 used the same or similar parameters.Because the speed-trending requirement for call handoffs may differ from thespeed-trending requirement for DCCH reselection, the new parametersintroduced in R15.0 allows insertion of parameters specific to call handoff (refer toParagraph 2.11),.

Dynamic Downlink Power Control — Dynamic power control attempts tomaintain the mobile transmitted signal strength received at its serving antennaface within predefined limits independent of the distance between the mobile unitand the serving cell. The activation of DPC improves cell performance by reducingor, in some cases, completely eliminating uplink receiver overload and RFinterference (refer to Paragraph 1.5.1.4.7),.

The major changes in Issue 6 includes Flexible Channel Allocation - ListMonitoring (FLCA-LM), which is the first of two features required to achieve FLCA,Discontinuous Transmission with Comfort Noise Insertion (DTX/CNI) and TDMAHierarchical Cells.

Flexible Channel Allocation - List Monitoring (FLCA-LM) — Two fundamentalbenefits are realized from the deployment of the FLCA feature. The primarybenefit is dynamic channel allocation providing RF spectrum resources when andwhere needed to increase capacity. The second benefit is the ability to improvevoice quality by always selecting an acceptable RF channel when available(channel with acceptable level of interference) to service calls. Both benefits areobtainable at cell locations that do not use auto-tune cavity combiners in theirtransmit path. Because of the time delay inherent in tuning the auto-tune cavities,only the second benefit is obtainable in cells using the auto-tune cavity combiner.This feature reduces the RF engineering burden of assigning RF channels tospecific EDRU radios that is traditionally required when new radios are added to acell or new cells are added to the network. In addition, this feature increases

1-4 401-200-112, Issue 11 June 2001


Introduction

system capacity by dynamically allocating spectrum resource when and whereneeded.

In achieving it primary benefit, FLCA is most efficient in areas and clusters weretraffic demand series is unequally distributed. Rather than having some calls insome cells blocked due to insufficient spectrum resources while RF channelsassigned to other cells are idle, the FLCA feature creates a pool of RF channels,broadening a cell RF resources. Channels within the FLCA pool are groupedwithin channel sets. Each channel set, which may share channels in common withother channel sets, may be assigned to a number of cells within the ECP servicearea.

TDMA Discontinuous Transmission (DTX) with Comfort Noise Insertion(CNI) — The TDMA Discontinuous Transmission (DTX) with Comfort NoiseInsertion (CNI) feature permits TIA/EIA-136A compatible mobile subscribers andsubscribers with TDX/CNI modified IS-136A mobiles to increase battery life by asmuch as 30 percent. The increase in battery life is achieved by curtailing themobile time slot transmission during the period when the subscriber is notspeaking. Although TIA/EIA-136A standards allow transmission curtailment withand without truncated burst, Lucent supports DTX/CNI with truncated burst only.Because the mobile is transmitting during a portion of the time slot period, the RFco-channel interference level is reduced at neighboring cells by as much as 30percent. This reduction permits both DTX/CNI capable and non-DTX/CNI capablemobiles to operate at lower power levels to further enhance battery life andincrease battery talk time.

TDMA Hierarchical Cells — This feature introduces additional criteria that maybe considered when selecting a handoff candidate. The additional criteria allowthe service provider to exercise better control of the hand-off process. This controlallows the call to be handed off to the candidate cell best suited to handle the callin accordance with the service provider’s overall strategy. This feature isespecially useful when operating in areas with a mix of small and large cells, aswell as in areas with public and private systems in a DCCH environment.

The major changes in issue 5 were impacted by Cell release 13.0 and includetwo-branch intelligent antennas, and the test EDRU (T-EDRU).

Two Branch Intelligent Antennas — This optional feature takes advantage ofthe currently deployed two diversity receive antenna array to improve voice qualityin the presents of co-channel interference using an adaptive antenna beamforming technique. Effectively, this technique narrows the receive antenna lobewidth and aims its boresight in the direction of the mobile unit currently beingserviced. By narrowing the lobe width and directing its boresight to the mobile ofinterest, interference received from another direction is rejected.

Test EDRU — The T-EDRU feature permits a standard EDRU to be program toperform the test function performed by the TRTU. The T-EDRU is narrower to

401-200-112, Issue 11 June 2001 1-5


Introduction

reduce the slot space required on the radio shelf. Coverage of the T-EDRUinstallation procedures is given as part of the EDRU personalities discussionand is provided in Paragraph 3.3.9 .

The major changes in Issue 4 include switch based TDMA vocoder, and separateaccess threshold for DTC and DCCH. This release also introduced enhancementto the Handdoff Based on Interference (HOBIT) optional feature and adds mobile-originated data to Short Massage Service (SMS) over DCCH optional feature.

The Switch Based TDMA Vocoder — This feature move the vocoder functionfrom the enhanced digital radio unit (EDRU) to the MSC. The vocoder is usedcode/decode voice data voice data into compressed digital data and visa versa.By relocating the vocoder back to the MSC before data decompression, moreefficient use of T1 transmission lines are realized. Separate access threshold forDTC and DCCH allows SMS and DCCH communications in low signal areas.Prior to this feature, the signal strength threshold level permitting mobiles toaccess a DCCH channel was set higher than required for DCCH communication.This was done to ensure the signal level in the area is higher enough for DTCcommunication which requires a higher signal strength than DCCH. This featureeffectively allows the service provider to reduce the threshold for DCCH and thenseparately test for a higher signal strength level before a call is either originated orterminated. The advantage of this feature permits the mobile user to receive SMSwhen located in areas where the signal strength level is too weak to permit voicecommunication.

Handoff Based on Interference (HOBIT) — This feature causes the mobile tohandoff to another radio on the same antenna face when a high level ofinterference is sensed on its current radio channel. In some case the interferencethat is sensed is cause by a weak signal and not because of the presence ofinterference on the channel. Prior to this release, HOBIT handoff in this situationdoes nothing to improve voice quality and may contribute to a high drop call rate.The enhancement to the HOBIT optional feature pursuant to this release, reducesdropped call rates due to HOBIT by allowing HOBIT handoffs only after ensuringthat the interference triggering HOBIT is due to noise rather than a weak signal.This enhancement is coupled with modification to the interference look ahead(INLA) optional feature that ensures the HOBIT handoff is not handed off toanother noisy channel.

Mobile-originated Data to Short Massage Service (SMS) — The mobile-originated data optional feature allows a subscriber to send a SMS via an IS-136compliant mobile unit. Normally, message data is transmitted over the DCCHchannel. However, when the mobile is currently on a DTC voice channel, themessage is transmitted over the DTC channel. The type of message transmissionoriginating from the mobile is group into two categories: messageacknowledgment and autonomous generated. Message acknowledgments aregenerated in response to receive message (mobile terminated SMS message) toinform the sender that the SMS message is terminated and received.

1-6 401-200-112, Issue 11 June 2001


Introduction

Autonomous generation permits the mobile subscriber to generate and deliver aSMS message to another subscriber in either a wireless or land-line network.

1.1.3 Intended Audience

This document is intended for individuals who are responsible for planning,implementing, and operating TDMA on an AUTOPLEX System.

1.1.4 Prerequisite Skills and Knowledge

Since this document covers a wide range of information directed to individualsperforming different functions, we assume a level of knowledge commensuratewith each function. For example, one who is involved with radio frequencyplanning is not expected to be fully versed in translation entry via Recent Changeand Verify or in the details of collecting Service Measurements; nor is it expectedthat a cell site technician well versed in cell site hardware, status display pages,and Technician Interface (TI) commands be knowledgeable about RFengineering.

In general, it is assumed that readers of this document are familiar with cellularindustry concepts related to Advanced Mobile Phone System (AMPS) technologyand have an overall knowledge of an AUTOPLEX system. The following referencedocuments are listed for your convenience:

■ 401-610-036 - Data Base Update Guide

■ 401-610-055 - Input Messages Manual

■ 401-610-057 - Output Message Manual

■ 401-660-106 - Translations Applications Guide

■ CIB117-2C-AUTOPLEX Cellular Telecommunications Systems Analog/Digital Voice Channel Selection Algorithms

■ 401-610-006 - AUTOPLEX System 1000 Description, Requirements, andPlanning Guide

■ 401-610-160 - Operations, Administration, and Maintenance

■ 254-302-005 - AT&T 3B20D Model 2 & Model 3 Computers

■ 254-302-005 - AT&T 3B20D Model 2 & Model 3 Computers

■ 304-046 - UNIX RTR (Real Time Reliable) 3B20D & 3B21D ComputersUNIX RTR Operating System Maintenance Manual

■ 3484B - AUTOPLEX System 1000 Technical Specifications

■ 401-610-009 - System Capacity Monitoring and Engineering Guidelines

■ 401-200-100 - Radio Frequency Engineering Guidelines

401-200-112, Issue 11 June 2001 1-7


Introduction

■ 401-660-110 - Cell Site Filter Engineering Guidelines

■ 401-660-100 - Series II Cell Site Hardware Description, Operation, andMaintenance

■ 401-660-111 - Guidelines for Minimizing RF (Radio Frequency)Interference

■ CIB 228-AUTOPLEX Cellular Telecommunications Systems Dual ServerGroup Cell Applications

■ 401-610-135 - Service Measurements Manual

1.1.5 Purpose

The purpose of this document is to provide the latest comprehensive informationon planning, implementing, and performance monitoring TDMA using AnalogControl Channel (ACC), Digital Control Channel (DCCH), and Digital Locatefunctionality with an AUTOPLEX System 1000 Cellular System.Recommendations for TDMA and DCCH are provided throughout this document.

This document covers topics from the perspective of Cell Release 6.05 or later.

1.1.6 Document Organization

This guide is organized as follows:

■ Chapter 1, Introduction—This chapter introduces terms and conceptsand provides an overview of TDMA, including call setup and callprocessing, and DCCH. It provides recommendations for enhancing TDMAand DCCH performance.

■ Chapter 2, Traffic and RF Engineering Guidelines for TDMA andDCCH—This chapter provides guidelines for planning and deployingTDMA. For systems that implement DCCH, the chapter provides DCCH-specific engineering guidelines, including establishing the same coveragefootprint for DTC and DCCH. The chapter also discusses diversity receive,Carrier-to-Interference (C/I) ratio requirements, and beacon channelplanning. A link budget example of how to allocate signal losses throughoutthe RF transmit and receive paths is provided.

■ Chapter 3, Hardware Installation—This chapter provides detailedhardware installation instructions. In addition, it discusses RFmeasurements and Receive Path Gain measurements.

■ Chapter 4, TDMA and DCCH Translations—This chapter providesdescriptions of TDMA and DCCH-related translations. Translations definecell site configuration and control performance.

1-8 401-200-112, Issue 11 June 2001


Introduction

■ Chapter 5, Technician Interface—This chapter shows changes to statusdisplay pages that provide TDMA/DCCH information. It also shows howtechnician interface (TI) input and output messages are modified to supportTDMA and DCCH.

■ Chapter 6, Service Measurements and Performance Metrics—Thischapter introduces new service measurements for systems with TDMA andDCCH deployed. In addition, it describes an approach for using servicemeasurements to analyze system performance, and recommends a set ofstandard performance metrics.

■ Chapter 7, Optional Features—This chapter describes optional TDMAand DCCH features offered to TDMA service providers.

1.2 Software and HardwareRequirements

The following are software and hardware requirements for TDMA and DCCHdeployment.

1.2.1 Software

Cell Release 6.05 and Executive Cellular Processor (ECP) 7.0 with SoftwareUpdate SU 96-0004 or later are required to support TDMA, DCCH and DigitalLocate capability.

Note: Cell Release 6.05 requires 8-megabyte memory boards.

1.2.2 Hardware

Implementing TDMA on a Series II cell site requires installation of the equipmentlisted below along with associated ancillary hardware such as cables and fuses.Full installation details are provided in Chapter 3.

■ Digital Radio Units (DRUs)—Basic radio equipment to support digitalcommunication with IS-54B and IS-136 compatible dual mode mobiles.Physically, DRUs occupy two Radio Channel Frame slots. LucentTechnologies recommends two DRUs per sector.

■ Enhanced Digital Radio Units (EDRUs)—The EDRU is an enhancedversion of the DRU and is fully downward compatible with the DRU. TheEDRU supports the new Algebraic Code Excited Linear Predictive(ACELP) vocoder as well as the existing TDMA Vector-Sum Excited LinearPredictive (VSELP) vocoder. The ACELP is a new speech codingalgorithm, improving the voice quality over the existing VSELP vocoder.The EDRU presents a thinner profile than the DRU (1.5 inches vs. 3

401-200-112, Issue 11 June 2001 1-9


Introduction

inches) enabling a larger number of EDRUs to be installed on the radioshelf. Because EDRU consumes more power than an RCU or DRU, theinstallation of a number of EDRU requires upgrading the radio shelf powerdelivery system.

■ TDMA Radio Test Unit (TRTU)—Provides diagnostic capabilities for DRU/EDRUs. Group 1 units support full testing of DRU/EDRUs as Digital TrafficChannels (DTCs). Group 2 TRTU are required for Digital Control Channel(DCCH) Testing.

■ TDMA RF Switch Assembly—Provides connectivity for TRTU to testpaths in the cell site. (Not required for Series IIm or Series IImm.)

Implementing additional functionality on a Series II cell site does not requireinstallation of hardware beyond that required for TDMA. However,

■ Digital Locate functionality requires allocation of one DRU or EDRU for athree-sector cell and two DRUs or EDRUs for a six-sector cell. Theseradios can not be used simultaneously for traffic and control, since thelocate function scans different frequencies. When a radio is assignedDigital Locate functionality, it is referred to as an L-DRU or L-EDRU.

■ DCCH requires an additional radio per sector.

To support IS-136 Short Message Service (SMS) capability, a Message Center(MC) is required to collect, store, and forward the SMS information. The MCconsists of a Short Message Center and an optional lnteractive Voice Response(IVR) system. This equipment is an adjunct to the AUTOPLEX System and can beobtained from a third party source. For more information, refer to Section 1.4.6 .

1.3 TDMA Overview

This section provides an overview of TDMA, and introduces terms and conceptsunique to TDMA cellular system technology as implemented on the AUTOPLEXSystem 1000, Series II platform.

TDMA conforms to the Telecommunications Industry Association (TIA) InterimStandard 54B (IS-54B). This standard defines compatibility standards for mobileunits and cell sites intended for use in areas offering digital cellular service in theTDMA format.

The following sections provide brief overviews of key aspects of TDMA, showinghow they relate to AMPS:

■ Format

■ Radio Access Method

■ DRU and EDRU Configurations

1-10 401-200-112, Issue 11 June 2001


Introduction

■ Digital Mobiles

■ Call Processing

■ Technician Interface

■ Input/output messages

■ Status display pages

1.3.1 Radio Access Method

Advanced Mobile Phone System (AMPS) cellular technology uses FrequencyDivision Multiple Access (FDMA), whereby the RF spectrum allocated for cellularphone systems by the Federal Communications Commission (FCC) is divided into30 kHz-wide RF channels. These RF channels are allocated as setup channels orindividual voice channels. Each AMPS Radio Channel Unit (RCU) supports two-way voice communication between the mobile and the cell site:

■ Mobile unit to cell site transmission—Defined as uplink or reverse radio link

■ Cell site to mobile unit transmission—Defined as downlink or forward radiolink

TDMA Full Rate

TDMA uses the same FDMA 30-kHz voice channel allocations as AMPS, andcarries digital information that is time-division multiplexed into six “time slots.” Theterm, TDMA Full Rate, is used to refer to a time slot assignment scheme in whichpairs of time slots are used to support communications in both the uplink anddownlink directions. These time slots or time intervals are assigned in equallyspaced pairs (1&4, 2&5, and 3&6) to carry digitized voice traffic in accordancewith the standard.

This means that each TDMA channel is capable of supporting three independent,private calls. Both the cell site and the mobile use time slots for transmission:

■ At the cell site, instead of one digitized voice input modulating the RFcarrier continuously (AMPS), three digitized voice inputs take turnsmodulating the RF carrier in a time-synchronous or time-multiplexedfashion. Time multiplexing increases the call handling capacity threefoldover AMPS.

■ At the mobile end, for each call, the mobile is instructed to transmit over aparticular time slot, rather than transmitting continuously (as in AMPS).

401-200-112, Issue 11 June 2001 1-11


Introduction

1.3.2 DRU and EDRU Configurations

The TDMA DRU/EDRU provides three time division multiplexed channels (timeslots) over a given carrier frequency, that can be used to perform differentfunctions (voice, control and locate), as needed. Each DRU/EDRU can beconfigured in one of three ways:

■ Three Digital Traffic (voice) Channels (DTC)

■ Two DTC channels and one DCCH channel

■ One digital locate function (multiple functions cannot be supportedbecause the locate radio changes frequency in order to perform the locatefunction)

1.3.3 Digital Mobiles

TDMA requires compatible digital mobiles that conform to one of two standards:

■ IS-54B—Basic TDMA mobile (supports digital transmission)

■ IS-136—Enhanced TDMA mobile, capable of supporting DCCH, whichallows additional digital end -user features

TDMA mobiles are generally dual-mode, capable of supporting analog (AMPS)and digital (TDMA) transmission.

1.3.4 TDMA Call Processing

Many aspects of call processing for TDMA are the same as for AMPS. Completedetails can be obtained from Customer Information Bulletin 117-2C, AUTOPLEXCellular Telecommunications Systems Analog/Digital Voice Channel SelectionAlgorithms. The overview of TDMA call processing provided below includes:

■ Setup

■ Handoff (MAHO)

■ Digital Locate

1.3.4.1 TDMA Call Setup

In the TDMA call setup process, the mobile sends a call origination or pageresponse message on a control channel to the cell site. Depending on the type ofmobile, (IS-54B or IS-136) one of two control channels is used:

■ IS-54B—IS-54B TDMA call setup is performed by an AMPS setup radio,also referred to as an Analog Control Channel (ACC). With the addition of aProtocol Capability Indicator (PCI) message transmitted over the ACC, the

1-12 401-200-112, Issue 11 June 2001


Introduction

setup process is identical to that for AMPS. The PCI bit transmitted by themobile in the setup message (origination or termination) indicates theallowable call mode of the mobile: TDMA only, dual-mode TDMA, or AMPSonly.

■ IS-136—IS-136 call setup can be performed by an ACC or by a DigitalControl Channel (DCCH), which is discussed in Section 1.4.

In response to the call origination or page response message, the MobileSwitching Center (MSC) assigns a TDMA Digital Traffic (voice) Channel (DTC)and time slot.

Once the DTC and time slot are assigned, three additional steps are required tocomplete the call setup process and obtain voice channel confirmation. Thesethree steps are also part of the handoff process. For details, refer to Section1.3.5 .

■ Time Alignment (TA)—This process time-aligns the burst of informationtransmitted by the mobile with the expected arrival time at the serving cellsite.

■ Digital Verification Color Code (DVCC)—This process verifies that theserving cell site is communicating with the desired mobile, and not with aninterfering mobile being served on another co-channel cell site.

■ Measurement Order Message Acknowledgement (MeasAck)—Thisprocess verifies that the mobile accurately received the MAHO candidatelist from the serving cell site.

1.3.4.2 Handoff

Handoff is the process of reassigning a mobile unit to a new voice channel onanother antenna face or cell site when the quality of the current channel isdowngraded. This reassignment takes place on the voice channel duringconversation and is accomplished using the blank-and-burst mode and istransparent to the user.

The IS-136 TDMA air interface standard permits dual mode/band mobile unitsallowing handoff, both between AMPS cellular and TDMA technologies (modes)and the 850-MHz cellular and 1.9-GHz PCS bands. The preferable mode ofhandoff, as a mobile unit moves from one cell to other, is to handoff to the sametechnology, that is, from TDMA PCS to TDMA PCS and TDMA cellular to TDMAcellular.

1.3.4.2.1 Difference Between AMPS and TDMA Handoff

The most significant difference between TDMA and AMPS is the Mobile AssistedHandoff (MAHO) process, which is used to move (hand off) TDMA calls from onecell to another. TDMA handoffs differ from AMPS in that the mobile performs the

401-200-112, Issue 11 June 2001 1-13


Introduction

locate and error rate measurement functions, not the cell. In addition, AMPS andTDMA neighbor lists are managed separately. TDMA handoff candidates arebased on MAHO neighbor lists. In addition, when available, all TDMA calls aresetup via the DCCH channel as apposed to the AMPS setup analog controlchannel (ACC).

Because the location of the mobile unit within the cell antenna coverage area isnot known, any adjacent cell sector is a possible handoff candidate. Subsequentto initial deployment and testing, the MAHO neighbor list must be populated toidentify the MAHO RF channel for all adjacent cell sectors.

NOTE: It is vital to note that the population of the MAHO neighbor list isessential for call processing. At least one candidate must beentered on the MAHO neighbor for successful call throughtesting. During the initial stages of deployment and testing, anyentry on this list is sufficient for call through testing.

1.3.4.2.2 DCCH Information on an Analog Voice Channel

When a TDMA cellular mobile unit moves into an area where a TDMA digitaltraffic channel (DTC) is not available, handoff is performed from the TDMA cellularDTC to an AMPS analog voice channel (AVC). In addition, because most PCSmobiles may not be equipped with VSELP vocoders, TDMA PCS calls are alsohanded off to cellular AVCs. Mobiles that are IS-136 compatible uses call setupand other pertinent system information received over the DCCH channel.Subsequently, all handoffs are controlled through blank and burst mode data overthe current DTC or AVC channel. When an IS-136 compatible mobile call ishanded off to an AVC, the mobile continuity with a DCCH is lost. That is, unlikeAMPS where the setup RF channel is defined, an IS-136 compatible mobile mustsearch the spectrum for a DCCH channel. To minimize the search time, the DCCHinformation on an AVC feature generates a blank and burst mode episode afterthe call is completed to identify the RF frequency of the nearest DCCH channel.

Note:

In this document, all references to MAHO refer to the Enhanced Sim-plified Mobile Assisted Handoff (ESMAHO) algorithm, introduced inCell Release 6.05. ESMAHO simplifies TDMA translation manage-ment and introduces the IS-54B Encoded Unit (IEU). The IEUreplaces the Received Signal Strength Indicator (RSSI) in somecases.

1.3.4.2.3 MAHO Translations

MAHO translations are entered into the system through Recent Change andVerify (RC/V) forms and reside in the MAHO Neighbor List on the Face CodeInformation (FCI) form. These and other TDMA-related translations are discussedin Chapter 4.

1-14 401-200-112, Issue 11 June 2001


Introduction

In AMPS, the cell site Locate Radios measure only the mobile signal strength; thehandoff triggers and resulting decisions are based on these uplink signal strengthmeasurements.

1.3.4.2.4 Handoff Triggers

In TDMA, the handoff process is much more complex. Any one of the followingmeasurements or triggers can initiate the handoff process, once the threshold, asdefined in the RC/V translations database, has been crossed:

■ Mobile Threshold—The mobile continually measures the downlink signalstrength of the serving channel and signals being transmitted by neighborMAHO or beacon channels. The channels the mobile is instructed tomeasure are provided in the Measurement Order Message sent to themobile after the mobile is assigned a DTC. These downlink measurementsare reported by the mobile to the serving cell site. The cell site averagesthe serving signal strength measurements and compares them against thethresholds set by system translations. When the averaged serving signalstrength drops below the mobile threshold, a handoff trigger is generated.

■ Primary Threshold—The cell site continually measures the uplink signalstrength of the mobile and compares it against the Primary Threshold.

■ Bit Error Rate (BER)—The mobile measures the downlink Bit Error Rate(BER) of the serving signal. These downlink BER measurements arereported by the mobile to the serving cell site, which averages them andcompares them against the thresholds set by system translations. Whenthe BER exceeds the BER Threshold, a handoff trigger is generated.

■ Frame Error Rate (FER)—The cell site measures the uplink Frame ErrorRate (FER). When the FER exceeds the FER Threshold, a handoff triggeris generated.

■ Periodic Best Server Locate—If no trigger is generated within the TDMAMeasurement Processing Interval for any of the above reasons, and thePeriodic Best Server Locate feature is enabled, a periodic trigger isgenerated to check if the call could be better served on another sector orcell site.

1.3.4.2.5 Generating Handoff Candidate List

Once the handoff trigger is recognized, the system generates a handoff candidatelist. The final list includes three candidate sectors, ranked in descending order bysignal normalized signal strength. This process is detailed in Appendix B.

1.3.4.2.6 Digital Locate

Once the top three handoff candidates are determined, the system attempts tofind a radio on the first target cell (the cell receiving the handoff). If that sector isequipped with a Digital Locate Radio (L-DRU or L-EDRU), the L-DRU/EDRU

401-200-112, Issue 11 June 2001 1-15


Introduction

attempts to verify the Digital Verification Color Code (DVCC) of the mobile, andmeasures the uplink signal strength. The handoff continues only if the correctDVCC is decoded and if the uplink signal strength is above the TDMA LocateReply Threshold. Otherwise, the process is repeated for the next handoffcandidate. The installation of the L-EDRU provides additional optional featuresthat are described in Chapter 7.

1.3.4.3 Interhyperband Operation

The IS-136 TDMA air interface standard permits dual mode/band mobile unitsallowing handoff, both between AMPS cellular and TDMA technologies (modes)and the 850-MHz cellular and 1.9-GHz PCS bands. The preferable mode ofhandoff, as a mobile unit moves from one cell to other, is to hand off from TDMAPCS to TDMA PCS. However, when a mobile unit moves into an area where aTDMA PCS digital traffic channel (DTC) is not available, handoff is performedfrom the TDMA PCS to TDMA cellular band. If a TDMA cellular DTC is also notavailable, the TDMA PCS call is handed off to an AMPS (analog) cellular voicechannel.

Handoff between PCS and cellular bands is identified as interhyperband handoff.Interhyperband handoff between TDMA cellular and PCS service providers ispermitted only on those mobile units that provide dual band capabilities to operatein the TDMA cellular and PCS frequency ranges. In addition, this optional featureallows DCCH control channel reselection between the TDMA cellular and PCSservices.

Prior to the introduction of the Hybrid MAHO/Digital Locate (HMDL) withInterHyperband Handoff (HMDL-IH) enhancement in Release 16.0, DIHOP andHybrid MAHO/Digital Locate were mutually exclusive. When the DIHOP featurewas turned on because the MAHO neighbor list included candidates in the otherHyperband (Hyperband that is different from serving cell Hyperband), the HMDLfeature is automatically turned off. With this enhancement, the service providerscan have MAHO neighbors in either Cellular or PCS Hyperband, and utilize theDigital Locate capability to do the handoff using both uplink and downlink, signalstrength. It is expected that this feature will significantly benefit service providers ifused concurrently with Hierarchical Cells and DIHOP features, especially in PCSOverlay settings.

1.3.4.3.1 Interhyperband Phase 1 (DIHOP1)

The interhyperband operation optional feature is introduced in two phases. Phase1 permits handoff from a PCS DTC channel to a cellular analog voice channel(AVC). Because a TDMA cellular service provider may not be initially equippedwith the new ACELP vocoder, phase 1 handoff cannot permit DTC to DTChandoff. A vocoder is an algorithm that converts analog speech signals to a digitaldata stream. Handoff from a PCS DTC channel to a cellular AVC channel isreferred to as a hand-down because the call is handed off to an earlier technology.

1-16 401-200-112, Issue 11 June 2001


Introduction

The hand-down relies on MAHO measurements only and may occur in any bordersector that is identified on the PCS neighbor list that is broadcast on the E-BCCHlogic channel.

1.3.4.3.2 Hyperband Measurement Order

The introduction of phase 1 allows activation of PCS service prior to fulldeployment over the entire PCS service area by relying on hand-down to thecellular providers in rural areas not yet covered by the PCS service provider. Thecellular/ PCS neighboring cells receive the parameters entered through the RC/Vforms to establish the criteria under which inter-hyperband is to be performed.When a call is initiated on a PCS DCCH channel, the PCS cell solicits a CapabilityReport from the mobile unit to determine if the mobile call may be handed off to acellular AVC channel. Mobiles that respond with 800 MHz AVC return receives a“Hyperband Measurement Order” in place of standard “Measurement Order”. TheHyperband Measurement Order is issued to the cell to compensate for thedifference in signal strength between MAHO measurements made in the PCS andcellular frequency bands. This difference is the hyperband bias (HBIAS)parameter entered on the RC/V form.

1.3.4.3.3 Interhyperband Phase 2 (DIHOP2)

Phase 2 of the interhyperband operation optional feature permits bidirectionalDTC to DTC handoffs between cellular and PCS service providers. Theintroduction of Phase 2 is predicated that the mobile unit is equipped with aVSELP vocoder as well as a ACELP vocoder. When the mobile unit is solicited fora Capability Report, the mobile unit responds to identify its dual vocodercapabilities, thus, allowing the cellular provider to accept the handoff on DTCchannel.

1.3.5 Dynamic Power Control with BER

As the mobile unit moves toward the cell site and the distance between the cellsite and the mobile decreases, the mobile transmit power can be decreased. Thisdecrease in mobile transmit power is performed automatically by the dynamicpower control (DPC) feature. This feature benefits the mobile users by conservingmobile battery power, resulting in extending talk time. The DPC feature alsobenefits service provider by reducing co-channel interference. Originally, the DPCalgorithm, which is used for AMPS and pre-release 9.0 TDMA, used signalstrength measurements to determine voice quality, and thus, determine theminimum mobile transmit power required to maintain the same level of voicequality.

However, voice quality of TDMA calls is more closely related to the carrier signal-to-interference (C/I) ratio rather than carrier signal strength alone. This means thelevel of interference (noise) experience in the area in which the call is conductedmust be accounted for in determining the minimum mobile transmit power. For

401-200-112, Issue 11 June 2001 1-17


Introduction

example, at a given mobile-to-cell site distance, the mobile can transmit at a lowerpower level if operating in a low noise area, than if operating in a higher noiselevel area. The C/I ratio is inversely proportional to the bit error rate (BER), whichrefers to the percentage of erroneous DTC voice digital data bits received due tonoise interference. Thus, the BER value is factored into the DPC algorithm tomaintain a high voice quality at minimum mobile transmit power.

Three translation parameters are added to fci recent change/verify (RC/V) form tosupport DPC with BER. The first, BER - Control DPC Feature State, turns on thefeature and selects the type of DPC activity to be performed on the logicalantenna face. The DPC activities selected by this parameter are with respect tothe Voice Mobile Attenuation Code (VMAC) translation parameter that is enteredon the same fci form. The VMAC parameter specifies a nominal mobile transmitpower at setup or handoff. Subsequently, the mobile is instructed to attenuate orboost its transmit power from the initial level set by the VMAC value in accordancethe measured BER level.

The second and third parameters are mobile high and low threshold values.These values are inserted into the fci RC/V form as whole integers ranging from 0through 9999 to represent a carrier signal-to-interference (C/I) ratio as apercentage or BER ranging from 0 to100 percent to a 0.01% resolution. Forexample, to indicate a C/I ratio equivalent to 0.5%, the value of 50 (50 x 0.01%) isinserted into the fci form.

The mobile high threshold value indicates the maximum percentage of BERallowed before DPC actions are taken, requiring an increase in mobile power levelto correct a high bit error rate level. The mobile low threshold value indicates theminimum percentage of BER allowed before DPC actions are taken, requiring adecrease in mobile power level when bit error rate levels are unnecessarily toolow. The decrease in mobile power level extends the battery service time and thepossibility of co-channel intervenes at another cell site.

1.3.6 TDMA Voice Channel Confirmation

Once the system chooses a TDMA channel and time slot to serve the call, thevoice channel confirmation process described below is implemented.

In TDMA, voice channel confirmation requires three steps performed on the DTCthat do not have an equivalent in AMPS: time alignment, DVCC verification, andMeasurement Order Message Acknowledgment. These steps are performed inboth setup (independent of the control channel) and handoff.

1.3.6.1 Time Alignment

Three calls can be supported on a single TDMA Digital Radio Unit.Time alignmentis used to ensure that calls do not interfere or collide with calls on the other time

1-18 401-200-112, Issue 11 June 2001


Introduction

slots. The cell uses shortened burst mode on call setup until time alignment isachieved.

Based on where in the time slot information arrives, the system calculates therequired time alignment adjustment required to time align or “sync-up” the mobileand the cell. Once determined, the time alignment value is transmitted to themobile and the mobile retards or advances its transmissions accordingly. Oncethis is completed, the cell and the mobile enter normal burst mode. Timealignment is then monitored throughout the call and corrected as necessary.

1.3.6.2 Digital Verification Color Code (DVCC)

During call setup or handoff, after a DTC is assigned, the cell must correctlydecode the transponder 8-bit encoded DVCC that it sent to the mobile. The DVCCvalue is assigned through the RC/V translations database. It is used by thesystem to ensure that the information being received by the cell is from thedesired mobile, not from a co-channel interfering mobile; this is similar to theSupervisory Audio Tone (SAT) for analog transmission.Three related translations,DVCC value, detection thresholds, and DVCC fade timer are discussed inChapter 4.

1.3.6.3 Measurement Order Message

During call setup or handoff, the mobile receives and acknowledges theMeasurement Order Message. This message contains a list of up to twelve MobileAssisted Hand Off (MAHO) channels that the mobile will continually measure andreport to the cell while the call is being served on the assigned logical face. It iscritical that the mobile acknowledge this message by transmitting back to the cellsite the MAHO Channel Numbers (MCN), because subsequent signal strengthreports are returned without their corresponding channel number. These channelsare used in the MAHO process described in the following section.

Normally, call setup and handoff are successful. If any of the above steps are notsuccessfully completed, the system will try a second time. If this attempt fails, aCall Shutdown message is generated by the DRU/EDRU. In this case, the call isnot established and all associated resources are reallocated.

1.3.7 Digital Radio Voice Channel Processing

Because TDMA technology transmits three DTC voice channels over a single 30-kHz time share bandwidth, voice audio data most be digitized and compressedprior to transmission. After transmission, the voice digital data must beuncompressed and converted back to audio data. Vocoders are used to compressand uncompress digitized voice data for air transmission between the mobile unitand the cell site. After the voice data is transmitted, the vocoder at the cellreceiver un-compresses the voice data for digital transmission to the MSC over a

401-200-112, Issue 11 June 2001 1-19


Introduction

T1 line. The vocoder at the mobile receiver uncompresses the voice data fordigital to analog conversion for audio reproduction. Two types of vocoderalgorithms are currently in use:

■ Vector Sum Excited Linear Predictive (VSELP), and

■ Algebraic Code Excited Linear Predictive (ACELP)

A digital radio voice channel refers to the algorithms and circuits required toprocess one DTC channel of voice data in the DRU and EDRU radios. Hence,three digital radio voice channels are provided to process the three DTC voicechannels that are handled by a single DRU or EDRU radio.

1.3.7.1 Forward Digital Voice Channel Processing

Fundamentally both vocoder algorithms compress voice data by coding patternsfound in the digitized samples of the voice data to be transmitted. A simplifieddiagram of voice channel processing in the forward path (transmit mode), from thecell sit to the mobile unit, using the ACELP algorithm is shown in Figure 1-1. Forthis illustration, the primary difference between the two vocoders is the number ofbits coded by the vocoder.

Figure 1-1 Forward Digital Voice Channel Processing, Simplified Block Diagram

8-Bit to 14-Bit Transcoding. 1The analog voice signal is sampled at an 8000 per-second rate and digitized through non-linear companded pulse-code modulation(PCM). Because voice signal bandwidth frequency range from 200 Hz to 3300 Hz,sampling at 8000 Hz, which is more than twice the highest frequency, is adequatefor audio reproduction.The digital samples are then grouped into 20-ms frameswhere each frame contains 160 samples. At the cell site voice data is seriallyreceived from the DS0 channel of the T1 line as companded 8-bit samples at a 64kbps serial data-bit rate. At this rate, each bit is received every 125 us.

1-20 401-200-112, Issue 11 June 2001


Introduction

Companded sampling is a non-linear analog-to-digital conversion technique. Incompanded sampling, the bit resolution at low intensities is higher than the bitresolution at higher intensities, as oppose to linear sampling where the bitresolution is uniform throughout the sampling range. In preparation for ACELPspeech encoding the companded 8-bit samples are transcoded to 14-bit linearPCM samples. This is done by a transcoder which is part of the echo canceller. Asa result, in order to maintain the same 20-ms 160-sample frame period, the bitdata rate is increased from 64 kbps to 112 kbps. Other than its transcodingfunction, the echo canceller, which is used to eliminate transmitted powerreflected back from the T1 line, is not used in forward digital voice channelprocessing.

ACELP Speech Encoder. 1Each 160-sample frame is analyzed by the ACELPspeech encoder. Based on its analysis, the ACELP speech encoder generatesspecific parameters that best describe the frame input so that the 160-sampleframe may be reconstructed from these parameters. In essence this encodersearches for speech patterns in the 20-ms voice frame period to define fourparameters: pitch, algebraic code, linear predictive filter code and gain. Part ofthis search is performed by code books which are operated as lookup tables toprovide pitch, algebraic code, linear predictive filter and gain indices. The fourindices encoded per 20-ms frame total 148 bits of coded data which is supplied bythe ACELP speech encoder at a 7.4 kbps (148 bits/20 ms) rate. The VSELPvocoder produces 159 bits per 20-ms frame which is clocked at a 7.95 kbps rate.

Channel Coding. 1The 148 bits clocked out of the ACELP speech encoder areclassified as class I and class II bits. Those bits, which are extremely essential indecoding voice data and require additional protection over the radio link, are classI bits. There are 96 class I bits; the remaining 52 bits are class II bits. The 48 mostsignificant bits of the 96 class I bits are used to produce 7 cyclical redundancycheck (CRC) bits in the channel coding circuit. Then the 7 CRC bits are combinedwith the 96 class I bits and are fed into a half-rate convolutional coder. The outputof the convolutional coder, 208 bits, is combined with the 52 class II bits and isclocked out of the channel coder in a 260-bit, 20-ms burst at a 13 kbps rate.

Voice Encryption. 1When voice privacy is used, the speech code on the 260-bitframe burst is encrypted. This encryption uses a voice privacy key which isexchanged between the mobile unit and the cell site after an authenticationprocess. When applied to the voice privacy algorithm, the voice privacy keyconverts the 260-bit burst to an encrypted speech frame (cipher text). Essentially,this algorithm scrambles the 260 bits in the burst so that its intelligent meaning islost without the voice privacy key. The encrypted speech frame is subsequently bitinterleaved and then transmitted to the receiver where the same voice key isapplied to unscramble (decrypt) the encrypted speech frame.

Bit Interleaving. 1To reduce the effects of Rayleigh fading or any otherdisturbances that may cause a brief interruption of the received signal resulting inthe loss of a small cluster of adjacent bits, the bits within two successive transmitframes are interleaved. The interleaving process systematically scrambles and

401-200-112, Issue 11 June 2001 1-21


Introduction

stores all the odd- and even- numbered bits in separate frames. Cluster of bitsthat may be lost during transmission will appear randomly spaced across bothframes after the bits are unscrambled at the receiver. The unscrambling processscatters the lost bits to improve the chances that lost bits can be recovered.

When transmitting at full rate, the 324 bits make up the DTC data content that istransmitted over a time-slot period. So that the 324 bits can be transmitted withinthis period, which is 6.66 ms, the 324 bits must clock at the bit interleaving circuitat a 48.6 kHz rate. Thus, each digital voice channel processor must generate intwo 6.66-ms 48.6-kHz bursts during each TDMA frame. Since the DRU andEDRU radios are equipped with three digital voice channel processors, each radiogenerates six 6.66-ms 48.6-kHz bursts to fill the six time slots in each TDMAframe.

1.3.7.2 Reverse Digital Voice Channel Processing

The reverse digital voice channel processing path (receive mode) in the cell radiois effectively the reverse of the forward digital voice channel processing pathdescribed in the previous section. Except for delay equalization, each function inthe forward digital voice channel processing path has it peer in the reverse digitalvoice channel processing path as shown in Figure 1-2.

Figure 1-2 Reverse Digital Voice Channel Processing, Simplified Block Diagram

Delay Equalizer, Bit-De-Interleaving and Voice Description. 1The delay equalizercompensates for the spread in time delay due to multiples propagation. The delayspread, which may be small in urban areas, will be significantly larger inmountainous regions.The bit de-interleaving process systematically un-scattersthe 260 voice data bits that make one speech frame. The remaining 64 bits areoverhead bits, such as the synch, SACCH, and CDVCC bits. The 260 voice data-bit speech frame is clocked out at a 13 kbps rate. Each 260 voice data-bit speech

1-22 401-200-112, Issue 11 June 2001


Introduction

frame is then decrypted using the same voice privacy key used by the mobile unitin creating the speech frame.

Channel Decoding. 1The 148-bit/frame, originally generated by the mobile unitvocoder prior to coding and transmission, is reconstructed as the channel decoderthat strips off the error protection bits while performing error correction. If a smallcluster of bits were lost due to interference or Rayleigh fading, the bit scamblingscheme would randomly distribute the lost bits over two frames to enablealgorithms in the channel decoder to restore the lost bits. Recovery is furtherenhanced by separating adjacent bits into odd and even frames to minimize thechances that two successive bits will be lost. The reconstructed 148-bit/framevoice pattern data is then routed to the ACELP vocoder at a 7.4 kbps rate. Here,the code book lookup tables are used in the reverse manner to convert thecontents of the pitch, algebraic code, linear predictive filter and gain indices backto a pulse-code modulation data were each 20-ms frame is converted to 160 14-bit words.

Echo Canceller. 1The 2240-bit (14 X 160) content of each frame is serially routed tothe echo canceller at a 112-kbps rate. A transcoder in the echo canceller convertthe 14-bit linear PMC words to companded 8 bits for transmission over a T1 line.Each 20-ms frame is then serially clocked out of the 14-bit to 8-bit transcoder on aDS0 channel of the T1 line. Some of the energy transmitted on the T1 line, whichis a full-duplex, 4-wire system, is reflected back when the T1 line is coupled to ahalf-duplex, 2-wire system. This reflected energy is received by the mobile user asan echo. The echo canceller is used to remove the reflected energy.

1.3.7.3 Vocoder and Echo Canceller Location

Prior to ECP and Cell Releases 12.0, both ACELP and VSELP vocoderalgorithms were performed exclusively at the cell site. The VSELP vocoder is anearlier algorithm and is used by DRU radios, EDRU radios and in older TDMAmobile units. The ACELP vocoder is used only in EDRU radios and in newerTDMA mobile units which are normally equipped with both the VSELP andACELP algorithms. The incorporation of ECP and Cell Releases 12.0 provides aswitch based TDMA vocoder feature that moves the vocoder and echo cancellerto the digital cellular switch (DCS).

By moving the vocoder and echo canceller, compressed voice data is transmittedover the T1 line. Thus, the T1 line bandwidth required to transmit the voice databetween the cell site and the DCS is significantly reduced. This bandwidthreduction triples the utility of the T1 line. This allows voice data from three DTCchannels, handled through a single EDRU, to be multiplexed on a single DS0channel. As a result, the number of T1 lines required between the DCS and thecell site are reduced by two-thirds. Because the DRU radio does not allow itsvocoder and echo canceller process to be bypassed, the switch based TDMAvocoder feature benefits only those DTC channels handled through an EDRU.

401-200-112, Issue 11 June 2001 1-23


Introduction

Advantage. 1In addition to a two-third reduction in the number of required T1 facilitylines, other advantages of relocating the vocoder and echo canceller to the DCSare:

■ Pooling of Vocoders and Echo Cancellers — Pooling reduces thenumber of vocoders and echo cancellers required by the system. Thisnumber is system-wide engineered based on the expected traffic andblockage rate, as opposed the number of radios in at a particular cell.

■ Semi-Soft Handoff — The quality of the call is improved because thesame vocoder and echo canceller pair is used throughout the call durationregardless of the number of intra-DCS handoffs performed. Voice quality athandoff is improved in two ways:

— The amount of processing required for component switch isreduced.

— Algorithms requiring initial training periods enabling the echocanceller to adjust to voice characteristics at handoffs areeliminated.

■ Centralized Platform Allowing Multiple Vocoder Algorithms —Currently, two vocoder algorithms (ACELP and VSELP) are supported. Asnew vocoder algorithms are standardized, the algorithm is easilydownloaded or added to a centralize location in the DCS.

Packet Pipe Transport Mode. 1Voice data from all three DTC channels handledthrough a single EDRU is placed within packets. These packets are seriallytransferred between the cell and the DCS via one DS0 segment of the T1 line,which is referred to as a pipe. Each EDRU radio contains six digital signalprocessor (DSP) which were formally assigned to process the vocoder and echocanceller algorithms. When the switch based TDMA vocoder feature isimplemented, the vocoder and echo canceller algorithms are not used, and two ofthe six DSPs are reassigned to support the packet pipe transport protocolalgorithm. The packet pipe transport protocol algorithm is downloaded into all ofEDRU radios. The switch based TDMA vocoder feature cannot be mixed werevocoder and echo cancelling is performed at the cell EDRU radios for some DTCchannels, and at the DCS for other DTC channels.

Because the switch based TDMA vocoder feature can only be implemented on anEDRU radio, mixed mode operation is allowed only when the cell includes DRUradios as well as EDRU radios. To optimize vocoder utilization, priority is alwaysgiven to the vocoder and echo canceller in the DRU. When a call is originated orhanded off and VSELP coding is allowed the call is assigned to a DTC channel onthe DRU radio, if available. An exception to the above scenario is when the mobileunit requires a feature, such as TDMA data, that is dependent on the switch basedTDMA vocoder feature.

Hardware Requirements. 1No new hardware is required at the cell site. However, toimplement the packet pipe transport protocol a packet switching unit (PSU) is

1-24 401-200-112, Issue 11 June 2001


Introduction

required at the DCS. The PSU houses three types of circuit boards to handle andprocess packet data:

■ Frame Relay Packet Handler (FRPH)

■ Packet Handler for Voice (PHV)

■ Packet Handler for ATM (PHA).

The FRPH board receives and sends packet data to the cell. Packet data receivedby the FRPH is checked for errors and then relayed to the PHV board whichperforms the vocoder and echo canceller algorithms. The echo cancelleralgorithm in the PHV board may be bypassed in lieu of an optional third party echocanceller that may be installed in the PSU. The PHA board is used to enable intra-DCS semi-soft handoffs when more than one PSU is installed at the DCS. ThePHA boards provide interconnection between the PSUs using the asynchronoustransfer mode (ATM). Although inter-DCS semi-soft handoff is not currentlysupported by the switch based TDMA vocoder feature, future modification willallow semi-soft handoffs throughout the coverage area.

Switch Based TDMA Vocoder Feature Implementation. 1In addition to a number ofmodification to existing recent change/verify (RC/V) forms, two forms are createdto implement the vocoder. Additions and modifications to the RC/V data base arerequired to:

■ Designate cells with vocoder and echo canceller located in EDRU radios,and cells with vocoder and echo canceller located in the DCS

■ Assign vocoder algorithms to each PHV board

■ Assign radio time slots to packet pipes

■ Assign packet pipes to DS0s on T1 line

■ Bypass echo cancellers when optional third echo cancellers are used.

1.4 Digital Control Channel (DCCH)Overview

This section provides an overview of DCCH, and introduces terms and conceptsunique to DCCH.

DCCH conforms to the Interim Standard 136 (IS-136). In the standard, DCCH isdescribed as “a collection of logical channels conveyed on radio bearer channelsthat are used for transmission of control information and short user datamessages between the base and mobile station.”

401-200-112, Issue 11 June 2001 1-25


Introduction

1.4.1 Transmission Format

The Digital Control Channel (DCCH) can be implemented using the sameequipment required for IS-54B TDMA traffic channels. The DCCH conforms withthe existing IS-54B TDMA time slot frame structure. A given DCCH associatedwith a particular RF channel occupies one TDMA Full Rate Time Slot in a TDMAframe. For each Physical Antenna Face (PAF), up to three DCCHs (on differentradios) may be equipped.

1.4.2 Relationship with the ACC

The DCCH provides a cellular service platform that is separate from the AnalogControl Channel (ACC). The DCCH is compatible with the ACC. The DCCHperforms the same control functions as the ACC (e.g., access, setup, etc.). Inaddition, the DCCH provides for advanced end-user features as discussed inSection 1.4.5 .

1.4.3 Logical Channel Structure

The DCCH consists of a number of logical channels for communication betweenthe cell site and the mobile. These channels, implemented on a single time slotcarried on a DRU/EDRU, include two major categories:

■ Reverse link (RDCCH)—Carries uplink communications from the mobile tothe cell site.

■ Forward link (FDCCH)—Carries downlink communications from the cellsite to the mobile.

These logical channels are further subdivided as shown in Figure 1-1 below.

1-26 401-200-112, Issue 11 June 2001


Introduction

Figure 1-3 DCCH Logical Channels

1.4.3.1 Reverse DCCH

This uplink channel (reverse link) contains the Random Access Channel (RACH).Using the RACH, the mobile requests access to the system and responds tomessages sent by the cell site.

1.4.3.2 Forward DCCH

This downlink channel (forward link) handles messages from the cell site to themobile. It is subdivided into the SPACH, the BCCH, and the SCF, describedbelow:

SMS Point-to-point, Paging, and Access Response Channel (SPACH)

The SMS point-to-point, Paging, and Access response Channel (SPACH) carriesmessages from the cell site to the mobile. SPACH is itself subdivided into thefollowing channels according to the type of message carried:

■ SMS Channel—Delivers short messages to a specific mobile unit whenthe SMS feature is active.

■ Paging Channel—Delivers pages and orders.

■ Access Response Channel (ARCH)—Conveys call handling informationin response to a mobile unit attempt to access the system.

Broadcast Control Channel (BCCH)

DCCH

Reverse Link Forward Link(Uplink, RDCCH) (Downlink, FDCCH)

RACH

PCHARCH

SMSCH

F-BCCHE-BCCHS-BCCH

SCF Reserved

SPACH BCCH

401-200-112, Issue 11 June 2001 1-27


Introduction

The BCCH provides overhead control information such as system identificationand neighbor lists of other DCCHs. To access the cellular network, a mobile scansfor the DCCH, gains synchronization, and decodes the data sent over a BroadcastControl Channel (BCCH).

The BCCH includes the following three logical channels:

■ Fast Broadcast Control Channel (F-BCCH)—Provides time-criticalinformation such as DCCH structure parameters that are essential foraccessing the system.

■ Extended Broadcast Control Channel (E-BCCH)—Carries less time-critical broadcast information, such as neighbor cell lists.

■ Short Message Service Broadcast Control Channel (S-BCCH)—Reserved for future use.The channel is intended for broadcast of point-to-multipoint SMS messages to all mobiles or a fleet of mobiles.

Shared Channel Feedback (SCF)

The SCF contains information that allows mobiles to determine the availability ofthe RACH and the status messages sent on the RACH.

1.4.4 Multiple DCCH Feature

The Multiple DCCH (MDCCH) feature, which is introduced in Release 15.1 allowsthe service provider to equip up to three DCCH channels on a single EDRU,permitting up to nine DCCH channels on a sector. When used on a sectorrequiring multiple DCCH radios, this feature reduces interference because fewerradios that have to be on all the time will be used.

1.4.4.1 Deployment Considerations

Before implementing this feature on sectors having only two DCCH channels,careful consideration should be given to the advantage of having DCCH channelson separate radios over the advantage of reduced interference from having bothchannels on one radio. Although ARR may be used, the advantage of having tworadios insures that DCCH service in the sector is uninterrupted. The advantage ofone over the other will vary as a function of the sector location, its RFenvironment, and the service provider deployment market strategy. When thisfeature is deployed in sectors having three or more DCCH channels, considerusing at least two radios to take advantage of both reduced interference anduninterrupted DCCH service in the sector.

1-28 401-200-112, Issue 11 June 2001


Introduction

1.4.4.2 Turning On the Multiple DCCH Feature

The Multiple DCCH is a QFAF feature that is turned on when the TDMA MDCCHfield on the cell2 RC/V form is set to y. It is strongly recommended that the featureis turned on prior to the equipage of any DCCH timeslots on the EDRU. Otherwiseturning on this feature would cause the generation of asserts and HEH errors tobe seen on the ROP.

1.4.4.3 Equipping Multiple DCCH Timeslots onan EDRU

The RC/V translations controlling multiple DCCH timeslots are non-updatableparameters. This means that an EDRU must be removed and restored before theparameter changes take effect. In effect, the EDRU must be reinitialized. Duringthis process, data traffic channels on the EDRU would be dropped. For thisreason, it is recommended that the Multiple DCCH be implemented during off-peak hours. Perform the following to implement Multiple DCCH:

Note: Failure to follow the following procedure in the given sequence willresult in the generation of asserts and HEH errors.

Remove DCCH Radio. 1Take the DCCH associated EDRU out of service duringmaintenance window by entering the following on the TI screen:

rmv:cell x, ra y;ucl

where: x is the cell number, y is the DCCH EDRU radio number

Remove Voice Channels. 1Voice channels must be removed from those radio timeslots that are to be designated for DCCH channels. If the vocoder is located at thecell, this is done by deleting the ctm form.

If the vocoder is located at the MSC, this is done by entering n for Timeslots 1 and2 on the tpptm form when the first two radio user channels are to be assigned toDCCH channels. If all three user channels are to be assigned for DCCHoperation, relate the tpptm form.

dcch Form Update. 1Update dcch form (see Figure 1-4) for all radios whereMDCCH is deployed. On this form, indicate the status for timeslots 1, 2, and 3 byindicating e for equipped, g for growth, and u for unequipped. Timeslot 1 must bethe first timeslot assigned as a DCCH, then timeslot 2, and lastly, timeslot 3. If thetimeslot is to remain a voice channel, the field should remain blank

401-200-112, Issue 11 June 2001 1-29


Introduction

.

Figure 1-4 dcch RC/V Form

Restore EDRU. 1Restore the EDRU back to service by entering the following onthe TI screen:

rst:cell x, ra y;ucl

1.4.4.4 Turning Multiple DCCH Feature Off

Note: Turning off the MDCCH feature before removing DCCH channel fromEDRU timeslots 2 and 3 will result in the generation of asserts and HEHerrors.

Before the Multiple DCCH may be turned off, DCCH channels should be removedfrom the EDRU radio timeslots 2 and 3. Timeslot 1 may still be designate as aDCCH channel and the EDRU will operate as a standard single DCCH radio withthe capability of having one DCCH channel and two voice channels.

To turn off MDCCH, perform the following:

Remove DCCH Radio. 1Take the DCCH associated EDRU out of service duringmaintenance by entering the following on the TI screen:

rmv:cell x, ra y;ucl

AUTOPLEX Screen 1 of 1Cellular TDMA DCCH RADIO INFORMATION (dcch)System

Series II Cell Site Number..................... *1) ___

Voice Radio Number............................. *2) ___

Voice Radio Channel Number ..................... 3) ____

Digital Verification Color Code ................ 4) ___

Voice Radio Type ............................... 5) _____

Status - Timeslot 1 ............................ 6) _

Timeslot 2 ............................ 7) _

Timeslot 3 ............................ 8) _

Physical Antenna - Receive ..................... 9) _

Physical Antenna - Transmit.................... 10) _

Linear Amplifier Circuit Number................ 11) __

Frame Number .................................. 12) _

Shelf Number................................... 13) _

Slot Number.................................... 14) __

1-30 401-200-112, Issue 11 June 2001


Introduction

dcch Form Update. 1Update dcch form (see Figure 1-4) on the radio whereMDCCH channels are to be removed. On this form, remove DCCH channels fromEDRU radio timeslots 2 and 3 by leaving Status - Timeslots 2 and 3 blank. Ifdesired, Status - Timeslots 1 may remain a DCCH channel.

If EDRU radio timeslots 2 and 3 are to be designated as DTC (voice channel),perform the next step Equip Voice Channels. Otherwise, skip this step and go toTurn Off MDCCH Feature.

Equip Voice Channels. 1Voice channels may be equipped on radio timeslots leftblank on the dcch form. If the vocoder is located at the cell, this is done bycreating a ctm form for each voice channel.

If the vocoder is located at the MSC, this is done by entering e for Timeslots 2 and3 on the tpptm form when the last two radio user channels are to be designatedvoice channels. If the first user channel is also to be designated a voice channels,enter e for Timeslot 1 on the tpptm form.

Turn Off MDCCH Feature. 1Turn the Multiple DCCH feature off by entering n inthe TDMA MDCCH field on the cell2 form. When this feature is turned off, only thefirst user channel (timeslot 1) is enabled for DCCH selection.

Restore EDRU. 1Restore EDRU back to service by entering the following on the TIscreen:

rst:cell x, ra y;ucl

1.5 TDMA Call Processing

Call processing involves the establishment and maintenance of a TDMA call. Theestablishment of a call is referred to as call setup in which a radio link is set upbetween a cell and a mobile unit. Call setup is negotiated between the MSC andthe mobile unit via a DCCH radio channel. The majority of cell site call processingis performed by software residing at the cell site. This software uses performanceand operation parameters entered into the system data base via Recent Change/Verify (RC/V) forms. These parameters are discussed in detail in Chapter 4, andwhen necessary, those parameters essential for the following call processingdiscussion will be briefly described.

The following discussion on call processing assume the presents of DCCHchannels and is presented on two levels. First a general overview description isgiven to introduce terms and basic concepts. The overview description will befollowed by a detailed discussions of each concept.

401-200-112, Issue 11 June 2001 1-31


Introduction

1.5.1 Call Processing Overview

Prior to making originating or terminating calls, DCCH communication with the cellsite must be well established. When the mobile unit is turned on, the mobile unitconducts a search from an initial set of frequencies to locate a DCCH channel.When the channel is found, the mobile unit initially stays (camps) on this channeland monitors the data received over its BCCH and SPACH logical channels. Asignificant portion of the data monitored at this time is a list of neigboring DCCHchannels, identified as a reselection list. Also monitored at this time areparameters that are entered into the RC/V data base.

These parameters define the criteria that are used by the mobile unit to search forthe strongest DCCH signal in its environment. Subsequently, the mobile unit usesthe reselection list to go through a reselection routine to find the strongest DCCHchannel signal. When this channel is found, the mobile unit tunes to this channeland again monitors BCCH and SPACH logical channels. This process is referredto as reselection. To ensure that the mobile unit is continuously camped on theDCCH channel having the strongest signal, the reselection process is periodicallyrepeated. During the initial camping, autonomous registration and authenticationis performed by the mobile unit to identify the mobile cell location and authenticity.Registration is performed each time the mobile unit is turned on and turned off,and each time it enters a new service area.

After a mobile unit is tuned on and is initially camped on a DCCH channel, themobile uses the reselection list to go through a reselection routine to find thestrongest DCCH channel signal. When this channel is found, the mobile unit tunesto this channel and monitors BCCH and SPACH logical channels. This process isreferred to as reselection. To ensure that the mobile unit is continuously campedon the DCCH channel having the strongest signal, the reselection process isperiodically repeated.

1.5.1.1 Call Origination and Termination

When a TDMA subscriber makes a call, the mobile unit must notify the systemthat the subscriber wants to establish a call. This process is called accessing. Atthis time, the mobile unit must gain control of the RACH channel, which is thelogical up-link subchannel of the DCCH channel, and notify the cell site that asubscriber initiated call setup is requested. When receiving a call, the subscribermobile unit must be notified that the subscriber has an incoming call. This processis known as paging in which the cell site will page the mobile unit over the SPACHlogical down-link channel. In addition, certain housekeeping information must betransmitted to and from the subscriber mobile unit to obtain voice channelconfirmation and to ensure that the call continues uninterrupted as the mobile unitmoves from cell to cell. The call processing involving camping, autonomousregistration, reselection and call setup are described in greater detail in thefollowing paragraphs.

1-32 401-200-112, Issue 11 June 2001


Introduction

1.5.1.2 Call Processing Detail Description

In addition to the processing described in the previous section, certainhousekeeping information must be transmitted to and from the subscriber mobileunit to obtain voice channel confirmation and to ensure that the call continuesuninterrupted as the mobile unit moves from cell to cell. After a mobile is initiallycamped on a DCCH channel, call processing involves, autonomous registration,reselection and call setup are described in greater detail in the followingparagraphs.

1.5.1.2.1 Autonomous Registration

Autonomous registration is a process in which the mobile unit reports its locationwithin a specific MSC service area. This feature eliminates the need for floodpaging over several MSC service areas when an incoming call is received.Increased services are available with the enhanced autonomous registrationoptional feature which provides additional capabilities to locate and determine theon/off status of the mobile unit. The word autonomous, in this case, implies thatthe registration is independent of either the MSC or the cell site activity and is notsolicited by either. Periodic time-based registration is performed when the mobileunit is turned on, identifying that the mobile unit is on. Registration is alsoprompted when the mobile unit leaves a predetermined area such as its homeserving territory. Knowledge of the mobile unit off status enables the MSC toimmediately switch to secondary features without frustrating the calling party witha long waiting period before determining that the call can not be completed. Thesecondary features may be call forwarding, voice mail or messaging.

When a mobile unit is first turned on, an initial selection process is performed toselect the strongest DCCH channel signal. The initial selection process is a two-fold operation: First, a DCCH channel must be found so a DCCH neighbor cellreselection list of DCCH channels in the immediate service area can be read fromits extended BCCH (E-BCCH) channel. Then the signal strength of each channelon the reselection list is checked to identify the strongest signal strength. Tominimize the search time, the mobile unit tunes to the last DCCH frequency itserved on. If this DCCH frequency is out of range, the mobile unit performs aspecific channel search algorithm in which its preferred frequency block is firstsearched.

When a DCCH channel is found, the mobile unit camps on that channel to readthe DCCH neighbor cell neigboring reselection list and reselection criterionparameters that is broadcast over its enhanced broadcast logical channel(E-BCCH) and SPACH logical channel. Subsequently, the mobile unit will rundown the neigboring reselection list to check the signal strength on each channel.If necessary the mobile unit then re-camps on the DCCH channel having thehighest signal strength.

Each time the mobile unit camps on a new DCCH channel, it reads data from theBCCH and SPACH logical channels. In addition to storing the broadcast

401-200-112, Issue 11 June 2001 1-33


Introduction

ur-

d to

mred

ised

hcellnel.

icig-is

al in

reselection list, the mobile unit stores other parameters that are essential forreselection and system operation. The major parameters, which are extractedfrom the BCCH channel, are identified along with the associated RC/V form andare briefly described in Table 1-1. The description presented in the table describethe parameter to the extent required to describe the reselection process that isdiscussed in Reselection Paragraph 1.5.1.2.2. Refer to Chapter 4 for moredetailed information on any of these parameters.

Table 1-1 Reselection Parameters

ParameterIS-136

DesignationRC/VForm

Description

Mobile Access Threshold RSS_ACC_MIN ceqface Specify the minimum signalstrength required for the mobileunit to remain camped on the crent DCCH channel.

Setup Access Threshold DCCH_SETUPACC

ceqface Specify the minimum signalstrength on the DCCH channelrequired for the mobile unit toeither originate a call or respona page.

Cell Type CELLTYPE resel Specify the reselection algorithused based on Regular, Preferor Non-Preferred selection.

Mobile ReselectionThreshold

SS_SUFF ceqface Specify a threshold used for analternate reselection algorithmwhen the CELLTYE parametereither Preferred or Non-Preferr

Mobile Attenuation Code MS_ACC_PWR ceqface Specify the power level at whicthe mobile unit can access thesite over the RACH uplink chan

Signal Strength Measure-ment Interval

SCANINTERVAL ceq-face/ecp

Specify interval between periodserving and candidate DCCH snal strength measurements. Thparameter specifies time intervhyperframes which equals 1.28seconds.

1-34 401-200-112, Issue 11 June 2001


Introduction

-lue

d

ted.

ue,and

menel

e-

ate

1.5.1.2.2 Reselection

Once camped on a DCCH channel the mobile unit periodically enters areselection process where the signal strength of its serving DCCH channel, alongwith the signal strengths of candidate DCCH channels from the reselection list,are measured. The measured signal strengths of the candidate DCCH channelsare compared with the signal strength of the current serving DCCH channel todetermine the best DCCH channel to camp on.

Cell Type. 1The signal strength comparison is performed by one of two basicalgorithms in accordance with the CELLTYPE parameter received over the BCCHchannel. When the CELLTYPE parameter is regular, the Best-Server algorithm isused, and when this parameter is either preferred or non-preferred, the AbsoluteSignal Strength algorithm is used. Because of mobile measurement accuracy,which is ±8 dB, the regular CELLTYPE parameter, resulting in the Best-Serveralgorithm, is recommended.

High/Low Frequency HL_FREQ resel Indicate the frequency in whichDCCH signal strength measurements occur in respect to the vaset for the SCANINTERVALparameter.

Reselection Delay DELAY ceqface Specify minimum time that themobile unit must remain campeon its serving DCCH channelbefore reselection can be initiaIf serving DCCH signal strengthfalls below RSS_ACC_MIN valDELAY minimum is suspendedreselection will occur sooner.

Delay DELAY resel Specify minimum continuous tithat the candidate DCCH chanmust be above its associatedRSS_ACC-MIN before it can bconsidered a reselection candidate.

Offset Bias RESEL_OFFSET resel Increases or decreases prefer-ence for reselection to a candidDCCH channel.

Table 1-1 Reselection Parameters

ParameterIS-136

DesignationRC/VForm

Description

401-200-112, Issue 11 June 2001 1-35


Introduction

Signal Strength Averaging. 1Both reselection algorithms require average DCCHsignal strength values consisting of a least five measurement samples before thereselection process may occur. The frequency in which the serving and candidateDCCH signal strength are measured is specified by the SCANINTERVALparameter, which ranges between 1 and 6. The SCANINTERVAL specifies a timeinterval in hyperframes, which equals 1.28 seconds. Therefore, if theSCANINTERVAL is 2, indicating DCCH signal strength measurements arecollected every second 1.28-second hyperframe period and five samples arerequired, reselection occurs every 12.8 seconds (2 X 1.28 X 5). The exception tothis rule is if a Radio Like Failure is detected or when the serving DCCH signalstrength falls below its RSS_ACC_MIN level.

High/Low Frequency Option. 1To conserve mobile battery life, when set to low,the high/low frequency parameter (HL_FREQ) provides the mobile unit with theoption to double the SCANINTERVAL. Thus, a SCANINTERVAL of 2 is doubled,providing a 5.12-second (4 X 1.28) scan interval. The decision to accept the lowoption is determined by the mobile manufacture design. When the mobile unitexercises this option, reselection is delayed.

Signal Strength Qualification. 1After each sample collection period, the mobileunit updates its five-sample serving DCCH signal strength average (Avg_Serving)and the five-sample candidate DCCH signal strength average (Avg_Candidate)for each DCCH candidate on the reselection list. In both the Best-Server andAbsolute Signal Strength algorithms, the mobile unit subtracts theRSS_ACC_MIN value from the Avg_Serving and the Avg-Candidate values toqualify their serviceability as follows:

Serving_Sig = Avg_Serving - RSS_ACC_MIN (servings), andCandidate_Sig = Avg_Candidate - RSS_ACC_MIN (candidate)

The mobile access threshold RSS_ACC_MIN level and the mobile attenuationcode (MS_ACC_PWR) received from the candidate DCCH cell face areinterrelated in that the mobile unit may adjust the RSS_ACC_MIN level based onits Mobile Power Class and the MS_ACC_PWR code. This interrelation isintended to accommodate mobile units having a maximum transmit power of lessthan 36 dBm. For example, a class III/IV mobile unit maximum transmit power islimited to 28 dBm. This power level is equivalent to the transmit access levelspecified when the MS_ACC_PWR code is 2. The MS_ACC_PWR code 2identifies a transmit power level that is two 4-dB steps below 36 dBm. If theMS_ACC_PWR code value is either 0 or 1, which respectively requires 36 or 32dBM of mobile transmit power, the mobile unit must proportionally increase theRSS_ACC_MIN level to ensure that the mobile unit can access the candidate cellface. To further illustrate this, consider the following example:

If the RSS_ACC_MIN level of a candidate cell face is set to -99 dBm and itsMS_ACC_PWR access code is 0, a class III/IV mobile unit must do the followingcalculation to find the adjusted RSS_ACC_MIN level:

1-36 401-200-112, Issue 11 June 2001


Introduction

RSS_ACC_MIN (adjusted) = RSS_ACC_MIN + MPC code (4 dB)

where MPC code is equivalent to the MS_ACC_PWR code for the mobile powerclass which for a class III/IV mobile unit is 2. Thus, the RSS_ACC_MIN must beupward adjusted to accommodate a mobile unit with a lower power class asfollows:

RSS_ACC_MIN (adjusted) =-99 dBm + 2 (4 dB) = -91 dBm

Best-Server Algorithm. 1When the CELLTYPE is regular, the Best-Serverreselection algorithm is used. This algorithm uses the following equation todetermine if the level of any Candidate_Sig is greater than the Serving_Sig plus aRESEL_OFFSET value:

Candidate_Sig - Serving_Sig + RESEL_OFFSET > 0

In the event that the above equality is true for more than one candidate, thecandidate resulting with a more positive signal level is selected. TheRESEL_OFFSET, which can be either a positive or negative number, is a biasvalue to, respectively, decrease or increase the candidate DCCH channelpreference for reselection. Thus, if the RESEL_OFFSET is a negative value, it ispossible for the Candidate_Sig to be less than the Serving_Sig, causingreselection to the candidate DCCH channel. Effectively, the RESEL_OFFSETvalue determines the size of overlay area between adjacent cells in the same waythat the DELAY parameter on the resel form does.

The proper setting of the RESEL_OFFSET value minimize the need to use theDELAY parameter, therefore the DELAY parameter can be set to zero to optimizethe reselection process when the CELLTYPE is regular. However, this may not betrue if the CELLTYPE is either preferred or non-preferred. Non-zero delayparameters are generally used in small microcell environments with large slow-moving pedestrian mobile traffic as opposed to fast-moving vehicular traffic.

Absolute Signal Strength Algorithm. 1When the CELLTYPE is either preferred ornon-preferred the Absolute Signal Strength reselection algorithm is used. Thisalgorithm uses the mobile reselection threshold (SS_SUFF) received from thecandidate DCCH channel cell face to trigger reselection. The SS_SUFF thresholdrepresents the minimum DCCH signal strength value, received at the mobile unit,that is sufficient to trigger reselection. Two equality statements are used for thisalgorithm:

Candidate_Sig - Serving_Sig + RESEL_OFFSET > 0, andAvg_Candidate >SS_SUFF (received at the candidate DCCH cell face)

The two equalities are used in either an OR or an AND statement depending onthe preferred or non-preferred status of the CELLTYPE. When the CELLTYPE ispreferred, reselection to the candidate cell face is encouraged. Thus, if eitherstatement is true, reselection to the candidate cell face is triggered. Therefore:

401-200-112, Issue 11 June 2001 1-37


Introduction

When CELLTYPE = preferred, reselection is triggered to the candidate cell face if:

Candidate_Sig - Serving_Sig + RESEL_OFFSET > 0,OR

Avg_Candidate >SS_SUFF (Candidate)

When the CELLTYPE is non-preferred, reselection to the candidate cell face isdiscouraged. In this case, both statements must be true to trigger reselection tothe candidate cell face. Therefore:

Candidate_Sig - Serving_Sig + RESEL_OFFSET > 0,AND

Avg_Serving <SS_SUFF (Serving)

While the first statement ensures that the Candidate_Sig is greater than theServing_Sig, the values of the RESEL_OFFSET and SS_SUFF may be adjustedupwards to burdened candidate reselection.

1.5.1.2.3 Separate Access Thresholds for DCCH and DTC Channels

Separate access thresholds for DCCH and DTC channels are provided for IS-136A mobiles in Cell Release R12.0. In this release a Setup Access ThresholdRC/V parameter is provided on the ceqface form to set the minimum signalstrength required for a quality DTC voice channel, while the Mobile AccessThreshold, which set lower, sets the minimum signal strength required to maintainDCCH communication.

When a new DCCH channel is selected and when either a call is originated orterminated, the mobile unit is ordered to measure and report its current DCCHchannel downlink signal strength to the serving cell. This process, which is part ofthe IS-136 Call Setup Process, is supported by most mobile units and is calledMobile Assisted Channel Allocation (MACA), which is described in Paragraph1.5.1.2.4. When either a call is originated or terminated, the serving cell comparesthe DCCH signal reported in the MACA message with the Setup AccessThreshold. If the DCCH signal strength level exceeds this value, the call setup willproceed. However, if the threshold is not exceeded, and directed retry (Paragraph1.5.1.2.4) is enable a retry attempt is made. Directed retry is enable when theInadequate Signal Strength Directed Retry parameters on the ceqface RC/V formis set to y. If retry is not permitted, the call is dismissed.

Two new service measurements: Directed Retry on Origination, and DirectedRetry on Termination at DCCH-PAF fields 22 and 23, respectively, are added toevaluate the performance of the feature. In addition, the following existing servicemeasurements may be useful when using this feature:

■ DCCH Originations Denied at DCCH-PAF field 10

■ DCCH Reorder Messages at DCCH-PAF field 14, and

1-38 401-200-112, Issue 11 June 2001


Introduction

■ DCCH Setup Forced Release Message at DCCH-PAF field 15.

The definition of these service measurements can be found in Chapter 6, Table6-1. In addition, is recommended to observe the following performance metrics:

■ Voice Channel Confirmation Failures per Voice Channel Assignment (VCA)

■ IS 136 Designation Failures per VCA

■ Alert Confirmation Failures per VCA

■ Lost Calls per Established Calls

■ Established Calls per VCA, and

■ BER and FER Triggers per Established Calls.

When implementing this feature, the greatest benefit can be obtained in cells/systems that have many areas of weak signal strength coverage. In these areas,setup failures are more likely to occur as compared with high signal strengthcoverage areas. It should be noted that the reduction in setup failures isproportional to the number of subscribers that are denied call setup. The change(decrease) in setup failures divided by the number of call setups denied providesa ratio that can calculated to determine an acceptable benchmark for themarketplace.

1.5.1.2.4 Mobile Assisted Channel Allocation (MACA)

Because of the ongoing DCCH reselection process, the mobile unit is assumed tobe continuously camped on the best serving DCCH channel. When a new DCCHchannel is selected, the mobile unit is ordered to measure and report its currentDCCH channel downlink signal strength to the serving cell. This process, which ispart of the IS-136 Call Setup Process, is supported by most mobile units and iscalled Mobile Assisted Channel Allocation (MACA). MACA is performed for twoprimary reasons:

■ To allow custom control of the Directed Retry feature

■ To determine the logical face assigned to the mobile on dual server groupcells.

Directed Retry Feature. 1The availability of DTC channel to handle a callorigination or termination is determined by the cell based on the serving face radioequipage. In the event that a DTC channel is not available to handle a call, the cellis blocked. If Directed Retry is not permitted, origination attempts are dismissedvia a reorder tone (busy signal), informing the mobile users that the call cannot becompleted. However, if permitted, the Directed Retry feature will redirect the callto another cell.

The Directed Retry feature is permitted if the All Servers Busy Directed Retry-DCCH parameter on the ceqface RC/V form is set to y. However, if the mobile unitis close to the blocked cell site, as indicated by a high-level signal strength MACA

401-200-112, Issue 11 June 2001 1-39


Introduction

report, redirection to another cell may overload the radios in the blocked cell andinterfere with the radios in adjacent cells.

The custom control of the Directed Retry feature prevents redirection of callseizures with high MACA reported signal strength levels that has the potential tocause radio overload and interference. When custom control is used, the MACAreported signal strength level is compared with the Directed Retry Threshold-DCCH parameter set on the ceqface RC/V form. If the MACA reported signalstrength is above the threshold set by this parameter, directed retry will not bepermitted.

A Directed Retry parameter, which is similar to the All Servers Busy DirectedRetry-DCCH parameter, is located on the resel RC/V form. The Directed Retryparameter specifies in the resel form if the resel candidates are permitted toservice the dismissed redirected call attempt.

Logical Face Assigned on Dual Server Group Cells. 1Currently dual servergroups are not common in TDMA deployments. However, if dual server groupcells are deployed, the MACA reported signal strength enables the cell to assignthe mobile to inner server group SG0, when the reported signal strength is low, orouter server group SG1, when the reported signal strength is high.

1.5.1.3 Call Setup

The call setup operation, which is used to establish a call, is performed through aDCCH personality EDRU radio over its control channel prior to any conversationbeing carried over a DTC voice channel. Paging and accessing are thefundamental components used for call setup. During paging, cell sites broadcastmessages and notify the subscriber of an incoming call. During accessing, a DTCchannel and time slot are assigned to a mobile unit to complete the call. Paging isaided by autonomous registration.

1.5.1.3.1 Paging

When an incoming cellular call is received, initially, the system does not know thelocation of the intended subscriber. Therefore, a paging message must bebroadcast through the DCCH channel in all the cell sites throughout the servicearea to notify the subscriber of an incoming call. During paging, a continuousstream of the subscriber identification numbers is sent out from the pagingchannel (PCH) which is the logical subchannel of the SPACH forward DCCHchannel. The DCCH camped mobile unit monitors the paging stream. When amobile unit decodes its own subscriber identification number from the stream ofdata, it will respond to the paging over the reverse access channel (RACH). 1

1-40 401-200-112, Issue 11 June 2001


Introduction

1.5.1.3.2 Accessing

When a call is originated from a mobile unit, the mobile unit must gain access tothe system and forward the call request with its origination number. This is donevia the RACH channel which is used to transmit message data from the mobileunit to the cell site. Before the mobile unit can transmit over the RACH channel, itmust monitor the Shared Channel Feedback (SCF) and initiate an autonomousRACH transmission.

Initial Traffic Channel Designation Message. 1If suitable DTC channels areavailable, the MSC sets up the call on the PSTN and returns a message to thecell, assigning a voice DTC channel and TDMA time slot to the call. As a result,the cell assembles an Initial Traffic Channel Designation message fortransmission to the mobile unit. This message contains the DTC and time slotassignments, the cell digital verification color code (DVCC), and the mobile initialpower level. This message is transmitted to the mobile unit via the DCCHchannel.

Automatic Retransmission Request (ARQ). 1Receipt of all the items in the InitialTraffic Channel Designation message is confirmed by ARQ which causes themobile unit to respond with either a Receive/Not-Receive indication after eachframe is sent over the RACH channel. If the ARQ process fails, an IS-136Designation Confirmation Failure (CPFAIL) message is created. As a result, thesetup attempt exists with a failure indication.

1.5.1.3.3 Initial Traffic Channel Confirmation

In response to the Initial Traffic Channel Designation message, the mobile unittunes to uplink and downlink frequencies of the assigned DTC voice channel.Three additional operations, which are Time Alignment, DVCC Verification, andMeasurement Order Message Acknowledgment, are required to complete the callsetup process and obtain voice channel confirmation. These three operations arealso part of the handoff process and are discussed in the following text.

Time Alignment. 1Because of RF propagation delays, time alignment is requiredto advance or retard mobile unit time-slot transmission bursts so that thetransmissions from the three mobiles sharing time slots on the same DTC channeldo not collide with each other. Time alignment is performed when the DCCHShortened Burst on Call Setup parameter on the face code information (fci) RC/Vform is set to y. When set to y, the mobile unit is initially instructed to transmit in ashortened burst mode. As a result, the mobile transmission burst is delayed and,consequently, is shorter than the time-slot allotment. Thus, the shortened burstensures that the transmission does not interfere or collide with the transmissionsfrom the other mobile units that share the DTC channel.

Based on when in the time slot period the first bit of the shorten burst arrives, thesystem calculates the time alignment adjustment required to time align or “syncup” the mobile and the cell. Once determined, the time alignment value is

401-200-112, Issue 11 June 2001 1-41


Introduction

transmitted to the mobile and the mobile retards or advances its transmissionsaccordingly. Once this is completed, the cell and the mobile enter normal burstmode. Time alignment is then monitored throughout the call and corrected asnecessary.

Digital Verification Color Code (DVCC). 1During call setup or handoff, after aDTC is assigned, the cell site must correctly decode the transponder CDVCCcode that is fed back from the mobile. Initially, the DVCC value, which is assignedthrough the RC/V translations database, is transmitted to the mobile, coded and islooped back to the cell site within 5 seconds. This value is used by the system toensure that the information being received by the cell site is from the desiredmobile, and not from a co-channel interfering mobile. If the DVCC value is notreceived within 5 seconds, a Voice Channel Confirmation Failure (VCCF)message is generated by the assigned EDRU. As a result, the call or handoff isnot establish and all associated resources are reallocated. Three relatedtranslations, DVCC value, detection thresholds, and DVCC fade timer, arediscussed in Chapter 4.

Measurement Order Message. 1During call setup or handoff, the mobile receivesand acknowledges the Measurement Order Message. This message contains alist of a number of Mobile Assisted Handoff (MAHO) Channel Numbers (MCN)that the mobile unit periodically measures for handoff quality. The voice qualitymeasurements are then reported to the current serving cell site while the call isbeing served. This list is commonly referred to as the MAHO neighbor list. It iscritical that the mobile acknowledges this message by transmitting back to the cellsite the MCN, verbatim, because subsequent signal strength reports are returnedwithout their corresponding channel number. These MCN numbers are used inthe MAHO process described in part of the handoff process in 1.5.1.4.2.

Normally, call setup and handoff are successful. If any of the above steps are notsuccessfully completed, the system will try a second time. If this attempt fails, aCall Shutdown message is generated by the EDRU. In this case, the call is notestablished and all associated resources are reallocated.

1.5.1.3.4 Increased TDMA MAHO List

If the increase TDMA MAHO List (ITML) feature is activated, the maximum MAHOlist entry is doubled from 12 to 24. This feature introduces a new maho RC/V formto allow the entry of 12 MAHO neighbors in addition to the 12 MAHO neighborsthat are originally populated via the fci form. The 12 MAHO neighbor entries fromthe fci form are identified as the primary MAHO neighbor list, and the 12 additionalare identified as the secondary MAHO neighbor list. The new maho form is a four-screen form that allows display/update of either the primary or secondary MAHOlist. A Primary List key field on the first screen is used to query if the primary orsecondary MAHO list is to be viewed on the second, third, and fourth screens.When a y (yes) is inserted in this field, the primary MAHO list is viewed for display/update; when n (no) is inserted, the secondary MAHO list is viewed for display/update.

1-42 401-200-112, Issue 11 June 2001


Introduction

FLCA Downlink Monitoring. 1When FLCA (see Paragraph 2.7) downlinkmonitoring is used, the total number of MAHO channels that populate the primaryand secondary MAHO list must be less than 24. This is to allow the empty MAHOchannel fields to be occupied with the channels from the Short List. The FLCAShort List is a list of up to 36 FLCA channels with low interference levels and arekept on the Short List as likely candidate channels to be assigned designatedFLCA radios to service calls in the immediate future. Short List channels areautomatically placed on the MAHO list to solicit mobiles to measure interferencelevels on the channel. Thus, in addition to the MAHO channels, each qualifiedmobile currently being served by the cell is requested to monitor the downlinkinterference levels on a subset of the Short List channels. The number of ShortList channel numbers received by each mobile is equal to the number of MAHOchannels on the primary MAHO list (N1) plus the number of MAHO channels onthe secondary MAHO list (N2), less the maximum MAHO list channel length.Although the absolute maximum MAHO order list length is 24, it may be desirablethe set the actual MAHO list length to a value less than 24. Therefore, a new RC/V parameter, Maximum FLCA Measurement Order Length (MFMOL), isintroduced in Release 16.1 to set the actual MAHO list length. This parameter ison the ecp form with a default value 18.

The value set by this parameter must include the number of Short List channels tobe sent to each qualified mobile. For example, if the default value 18 is used, andN1 and N2, which are the number of channels on the primary and secondaryMAHO lists, are 6 and 8, respectively, then a different four-channel [MFMOL- (N1+ N2)] Short List subset is sent to each qualified mobile in the service area. Thechannels selected for each subset is sent in a round-robin fashion through theShort List channel entries, so as few as nine qualified mobiles are required tosupply the downlink interference measurements for a 36-channel short list.

Mobile Protocol Version Distinction. 1The ITML feature can only be used on IS-136-Rev 0 or later mobiles. Early IS-54B mobiles, which can only receive a 12-channel MAHO neighbor order list, are not qualified to comply with the ITMLfeature. When these mobiles are in service where the ITML feature and FLCAdownlink monitoring are activated, the IS-54B will receive a MAHO neighbor orderlist consisting of the MAHO channels from the primary list only. If N1 is less than12, then Short List channels are appended to MAHO neighbor order list so thatthe total number of channels set on the MAHO neighbor order list is 12. Forexample, if N1 equals eight, then four Short List channels are appended to MAHOneighbor order list.

The three IS-136 mobile protocol versions may be separately qualified to respondto the ITML feature via enabling parameters on the ecp form. Should a serviceprovider discover that, due to external conditions, a predominance of ITMLfailures are associated with particular mobile protocol version, the ecp parametermay be set to disqualify that mobile protocol version from complying with the ITMLfeature. Any disqualified mobile protocol version will receive a maximum of 12MAHO neighbor channels from the primary MAHO line. If the number of MAHOchannels on the primary list is less than 12, Short List channels are appended to

401-200-112, Issue 11 June 2001 1-43


Introduction

the MAHO neighbor order list so that the total number of channels set on theMAHO neighbor order list is 12.

The three mobile protocol version-MTLI qualifying translation parameters are asfollows:

■ Enable ITML for EIA/TIA IS-136 Mobiles — When set to “y” qualifies EIA/TIA-136 and later mobile protocol versions when set up on a DCCHchannel

■ Enable ITML for IS-136 Rev A Mobiles — When set to “y” qualifies IS-136Rev A mobiles when set up on a DCCH channel

■ Enable ITML for IS-136 Rev 0 Mobiles — When set to “y” qualifies IS-136Rev 0 mobiles when set up on either a DCCH or ACC channel

The default value for the above parameters is no (“n” ). Because the ACC channelcannot distinguish mobile protocol versions, when the Enable ITML for IS-136Rev 0 Mobiles is set to “y”, all IS-136 mobiles set up the ACC channel will qualifyfor MTLI compliance.

ITML Service Measurement. 1The ITML feature introduces six new servicemeasurement to monitor how well each mobile protocol type responds to ITML. Ifa high number of failure are recorded for a particular mobile protocol version, theenabling parameter for that version may be set to "n". These servicemeasurements are recorded for a full hour for each LAF. A summary of thisservice measurements is given in

Table 1-2 ITNL Service Measurements

ITML Service Measurement Description

Increased Measurement OrderSuccess, EIA 136 DCCH

Count indicates the number of times a validMAHO list acknowledgement is received from anEIA/TIA-136 mobile served on a DTC channeland setup on a DCCH channel.

Increased Measurement OrderFailure, EIA 136 DCCH

Count indicates the number of times a validMAHO list acknowledgement is not received,after four attempts, from an EIA/TIA-136 mobile.

Increased Measurement OrderSuccess, IS-136 Rev A DCCH

Count indicates the number of times a validMAHO list acknowledgement is received from anIS-136 mobile Rev A served on a DTC channeland setup on a DCCH channel.

1-44 401-200-112, Issue 11 June 2001


Introduction

1.5.1.4 Call-In-Progress

Subsequent to voice channel confirmation, voice conversation over the DTCchannel may be established. Once voice channel conversation over the DTCchannel is established, all future control functions take place over the DTCchannel on one of two separate forward and reverse logical subchannelsidentified as the fast associated control channel (FACCH) and the slow associatedcontrol channel (SACCH). FACCH data is time critical data and is transmittedperiodically in place of voice data in a blank-and-burst fashion. During the FACCHtransmission, the voice conversation is blanked (muted) for a brief duration whilea burst of control information is transmitted. The muted period is so brief that thesubscriber is unaware that the conversation has been interrupted. On the otherhand, SACCH data is less time critical data and is transmitted in small segmentsduring each time slot period so not to interrupt voice transmission.

The transfer of control over these two logical channels is primarily concerned withtwo functions:

■ Mobile Assisted Handoff (MAHO) — To determine if the call is beingserved on the best possible cell site and antenna face.

■ Dynamic Power Control (DPC) — To control the mobile unit transmitpower received at the cell site

Increased Measurement OrderFailure, IS-136 Rev A DCCH

Count indicates the number of times a validMAHO list acknowledgement is not received,after four attempts, from an IS-136 mobile Rev A.

Increased Measurement OrderSuccess, IS-136 Rev 0 DCCH/ACC

Count indicates the number of times a validMAHO list acknowledgement is received from anIS-136 mobile Rev 0 served on a DTC channeland setup on a DCCH channel or a later mobileprotocol version served on a DTC channel andsetup on an ACC channel.

Increased Measurement OrderFailure, IS-136 Rev 0 DCCH/ACC

Count indicates the number of times a validMAHO list acknowledgement is not received,after four attempts, from an IS-136 mobile Rev0served on a DTC channel and setup on aDCCH channel or a later mobile protocol versionserved on a DTC channel and setup on an ACCchannel.

Table 1-2 ITNL Service Measurements

ITML Service Measurement Description

401-200-112, Issue 11 June 2001 1-45


Introduction

1.5.1.4.1 Mobile Assisted Handoff (MAHO)

Handoff is the process of reassigning a mobile unit to a new DTC voice channelon another antenna face or cell site when the quality of the current DTC channel iseither degraded or can be improved by using another DTC channel. Thisreassignment takes place on the voice channel during conversation and isaccomplished using the SACCH and FACCH control data channels and istransparent to the user.

MAHO neighbor list. 1The TDMA technology uses a MAHO process to move(handoff) calls typically from one cell or cell sector to another. In this process,TDMA mobiles make periodical RF signal quality measurements on its currentDTC channel as well as on up to 12 neighbor RF channels identified on theMAHO neighbor list. This list is initially sent to the mobile unit during setup as partof the MAHO Channel Numbers (MCN) discussed in the Measurement OrderMessage Sub-Paragraph of 1.5.1.3.3. This list identifies special RF channels,which are referred to as the MAHO channels, associated with all the cell sectorswhich currently surround the serving cell site sector.

NOTE: It is vital to note that the population of the MAHO neighborlist for each logical antenna face is essential for callprocessing. At least one candidate must be entered on theMAHO neighbor list for successful call through testing.During the initial stages of deployment and testing, anyentry on this list is sufficient for call through testing. If thecell provide an island of coverage a dummy MAHO listmust be entered

Because the location of the mobile unit within the cell antenna coverage area isnot known, any adjacent cell sector is a possible handoff candidate. Subsequentto initial deployment and testing, the MAHO neighbor list must be populated toidentify the MAHO RF channel for all adjacent cell sectors.

MAHO Channel. 1A different MAHO channel is assigned to each cell sector withinthe cell cluster. The MAHO signal from each sector is generated by a DCCH ordedicated radio that is designated to continuously broadcast a beacon signal.Because the MAHO channel signals are used by the mobile unit for RSSImeasurement, it is vital that each cell sector broadcasts its MAHO signal at thesame constant power throughout the service area. The MAHO signal istransmitted by the EDRU over either a DTC or DCCH channel. Because theEDRU providing the DCCH channel is continuously on, the DCCH channel is idealto serve as a MAHO channel.

1.5.1.4.2 RF Signal Quality Measurements

Every second, RF signal quality measurements are performed by the mobile unit.As a result, the mobile unit sequentially tunes to each MAHO channel on theneighbor list to measure and record its receive signal strength indicator (RSSI).

1-46 401-200-112, Issue 11 June 2001


Introduction

gthora-thea-

d by

erag-s.istemelow

the

This information, which is assembled by the mobile unit, is formatted into achannel quality message (CQM) and is sent back to the current serving cell site.The cell site analyzes the CQM messages collected from the mobile unit for eachneighboring RF channel on the list. This analysis enables the cell site todetermine when the signal quality on the current RF channel has degraded tosuch a degree that the call can be best served by either another cell or sector.

1.5.1.4.3 MAHO Threshold Parameter

Criteria for determining the channel quality are entered as translation parametersinto the system data base Recent Change and Verify (RC/V) forms. In addition, anumber of MAHO translation parameters are entered as threshold values whichgovern when or if handoff triggers are to be generated to initiate a handoff. Thesethreshold and other TDMA-related translations are discussed in detail in Chapter4. A summary of some of the more critical parameters that may, when itsthreshold is crossed, initiate the handoff process is given in Table 1-3.

Table 1-3 Mobile Assisted Handoff Triggers

ParameterRC/VForm

Description

Threshold:Mobile Signal

fci The mobile unit continually measures the downlink signal strenof the serving channel and signals being transmitted by neighbMAHO channels. The channels the mobile are instructed to mesure are provided in the Measurement Order Message sent tomobile after the mobile is assigned a DTC. These downlink mesurements are reported by the mobile to the serving cell site.

The cell site averages the serving signal strength measure-ments.The number of samples (N) used for averaging is defineMobile Reported Signal Strength Averaging Samples - TDMAparameter which is also set on the fci form. A rolling window aving scheme is used, providing an average of the last N sampleThe average serving cell MAHO signal strength measurementthen compared against the Threshold: Mobile Signal set by systranslation. When the averaged serving signal strength drops bthe mobile threshold, a handoff trigger is generated.

Primary Thresh-old

fci The cell site continually measures the uplink signal strength ofmobile and compares it against the Primary Threshold.

401-200-112, Issue 11 June 2001 1-47


Introduction

serv-y the

d byalsoed,alue

ter.ate

enrated.

ssingrver

eck if

1.5.1.4.4 Standard MAHO Candidate Selection

The mobile unit also continually measures the downlink MAHO signal strength ofeach candidate cell to determine the best candidate for handoff. The measuredcandidate signal is then reported to the cell. The mobile-reported signal strengthfrom each candidate cell is averaged by the serving cell using a rolling windowaveraging scheme. The number of samples (N) used for averaging is defined byMobile Reported Signal Strength Averaging Samples - TDMA parameter. If themobile power class (MPC) is III/IV, the correction offset established by the MPCCorrection/Offset for Class III/IV Mobiles parameter is added to all mobile-reported signal strength measurements.

Signal Strength Normalizing. 1The serving cell normalizes all mobile-reportedsignal strength measurements. This is done by performing the followingcalculation on the mobile-reported signal strength value from each candidate:

Sn = SCA - SSA - BMAHOwhere:

Sn = Normalizes candidate signal strengthSCA = Candidate average signal strengthSSA = Serving cell average signal strengthBMAHO = MAHO bias which is entered on the neighbor list

Bit Error RateThreshold

cell2 The mobile measures the downlink Bit Error Rate (BER) of theing signal. These downlink BER measurements are reported bmobile to the serving cell site, which averages BER measure-ments.The number of samples (N) used for averaging is defineBit Error Rate Averaging Samples - TDMA parameter which isset on the cell2 form. A rolling window averaging scheme is usproviding an average of the last N samples. The average BER vis then compared against the Bit Error Rate Threshold parameWhen the averaged BER value increases above the Bit Error RThreshold, a handoff trigger is generated.

Frame ErrorRate Threshold

cell2 The cell site measures the uplink Frame Error Rate (FER). Whthe FER exceeds the FER Threshold, a handoff trigger is gene

Periodic BestServer Locate

ceqcom2 If no trigger is generated within the TDMA Measurement ProceInterval for any of the above reasons, and the Periodic Best SeLocate feature is enabled, a periodic trigger is generated to chthe call could be better served on another sector or cell site.

Table 1-3 Mobile Assisted Handoff Triggers

ParameterRC/VForm

Description

1-48 401-200-112, Issue 11 June 2001


Introduction

The candidate cell faces are subjected to a number of criteria to determine if thecell face is suitable for handoff. Candidate faces are eliminated if:

■ Its normalized value is negative,

■ Its mobile-reported signal strength measurement is less than itscorresponding interference protection threshold (INTPHT) that is typicallyset 7 (-99 dbm) on fci form as part of neighbor list, and

■ The neighbor face is not equipped for the mobile allowable call mode.

Standard MAHO Candidate List. 1The final qualification for cell face candidacy isperformed by comparing the average MAHO signal strength with the decisionthreshold entered on the fci form as part of the MAHO neighbor list. The cell faceswith signal strength values equal to or above the decision threshold are enteredon a MAHO candidate list. If the MAHO candidate list contains less than threecandidates and the serving cell signal strength is less than a secondary thresholdvalue, those candidates that where eliminated by the decision threshold test areadded to the MAHO candidate list. A more detailed discussion on generating thislist, which is sometimes referred as the Handoff Candidate List, is given inAppendix A. If the L-EDRU digital locate feature is not used, after the MAHOcandidate list is completed, the cell sends the list to the MSC as handoff requests.

L-EDRU Digital Locate Feature. 1When the L-EDRU digital locate feature is used,prior to sending the MAHO candidate list to the MSC and issuing the handoffrequest, the serving cell will first issue a Digital Locate Request Message to theMSC to initiate the digital locate function which may possibly amend the MAHOcandidate list.

The L-EDRU radios in the serving cell and in the candidate cells are used tomeasure the uplink signal strength from the handoff candidate mobile. As a result,an uplink MAHO candidates are determined modify the standard MAHOcandidate list. This is done to eliminate candidate cells were the mobile uplinksignal strength is unacceptable.

When initiated by a digital locate request, the L-EDRU locate radios in thecandidate cells tune to the frequency and time slot of the mobile handoffcandidate to perform a DVCC verification and measure its uplink signal strength. Ifall candidate faces in the MAHO handoff candidate list are not in the serving cell,a Digital Locate Request Message is relayed to the cell(s) on the MAHOcandidate list, causing its L-EDRU(s) to perform DVCC detection and uplink signalstrength measurements. The candidate cell measurements are relayed to theserving cell where the signal strength measurements are normalized to create anuplink MAHO candidate entries based on the mobile uplink signal strengthmeasured at the candidate cells.

401-200-112, Issue 11 June 2001 1-49


Introduction

1.5.1.4.5Dynamic Power Control (DPC)

Dynamic Power Control (DPC) regulates the mobile uplink and cell downlinktransmit power to maintain an adequate signal strength at the receiver as thedistance between the mobile and the cell increases or decreases. The attenuationof transmit power as the distance between the mobile and the cell decreasesreduces the amount of co-channel and adjacent channel interference introducedin the surrounding cell environment, and thereby, improves overall voice quality.Traditionally, DPC referred to the ability of the mobile to control its uplinktransmitted power only. However, the introduction of the downlink DPC (DDPC) inrelease R15.0 necessitated distinguishing between uplink and downlink DPC.

Feedback Mechanism. 1Both uplink and downlink DPC depend on a feedbackmechanism where the signal strength at the receiver is periodically reported backto the transmitter. In this manner, the transmit power can be dynamicallycontrolled in accordance with the feedback report so that the receive signalstrength is maintained within a predetermined range. The feedback mechanismfor uplink DPC is provided via the SACCH and FACCH control data channels. Thefeedback mechanism for downlink DPC is extracted from the MAHO reportedsignal strength data.

Reducing Interference. 1By dynamically controlling transmit power levels, the levelof RF energy in a given environment is kept at its minimum. As a result, theadjacent and co-channel C/I ratio is increased, improving voice quality. Theimproved C/I ratio derived from UDPC and DDPC make these two featuresessential components for increased capacity when planning to migrate to a K = 4frequency reuse pattern.

1.5.1.4.6Uplink Dynamic Power Control (UDPC)

The activation of UDPC improves cell performance by reducing, or in some cases,completely eliminating uplink receiver overload in addition to reducing RFinterference in surrounding cells. Without UDPC, mobiles transmit at a fixednominal power level. As a result, the mobile-transmitted signal level at the cellreceiver would vary inversely as the distance between a mobile unit and theserving cell antenna face varied. Greater protection is required as this distancedecreases, causing an increase in received signal strength at the cell receiver,which results in receiver overload.

When the UDPC feature is turned on, the cell sends a digital mobile attenuationcode (DMAC) to regulate the mobile transmit power so that the received powerlevel at the cell site remains within a small range. Reduction of the mobile transmitpower below its nominal level is called attenuation, and the increased mobiletransmit power is called boosting.

Receiver Overload. 1The diversity inputs to the DRU/EDRU radios are receivedthrough two one of the two diversity receive antennas. The low-noise amplifier ineach receiver unit is designed to operate at a specific input signal power levelrange. When the received signal from a mobile exceeds this power level range,

1-50 401-200-112, Issue 11 June 2001


Introduction

the receiver unit goes into a receiver overload state. When in this state, the noisefloor of its low-noise amplifier is raised, desensitizing the receiver unit to receivesignals on other DTC channels. The receive unit effectively loses its front-endgain where the receive inputs on these channels, although otherwise received atan adequate signal strength, would be too weak for good reception. In addition toreceiver desensitization, receiver overload also causes crosstalk due tointermodulation.

RF Interference. 1Because of channel reuse, the same frequencies are used in anumber of cells. Despite the fact that the cells using the same frequencies are setfar apart, a certain amount of co-channel interference is inevitable. In addition toco-channel interference, adjacent channel interference between two cells in closeproximity is also inevitable. Thus, by keeping the mobile unit transmit power at anadequate minimum level for good reception, the amount of adjacent and co-channel interference is reduced or eliminated.

UDPC Defining Translation Parameters. 1Translation parameters, which are seton the face code information (fci) RC/V form, are used to control the level ofUDPC required. These parameters define the mobile target received signalstrength at the serving antenna face, the permissible range of the received signalstrength above and below the target level, and the degree of UDPC action. Themobile target received signal strength is defined by the Dynamic Power ControlState - TDMA Target parameter which can be adjusted from 0 to 127 RSSU (-130to -30.78 dBm). The RSSUs are measurement units for the receive signal strengthindicator (RSSI) value. The target level upper and lower limits are defined by theDynamic Power Control State - TDMA Window parameter. This parameter, whichcan also be adjusted from 0 to 127 RSSU, is set in 5-RSSU increments. Theseincrements are the equivalent of 4 dB.

When the received signal strength increases above (or decreases below) itstarget window, a dynamic mobile attenuation code (DMAC) is sent out. The DMACcauses the mobile to adjust its transmit output level so as to bring the receivedsignal strength at the serving antenna face back within the target window. As thedistance between the mobile and the cell decreases, the DMAC specifies theamount of attenuation, in 4-dB increments, and the mobile unit adds to thetransmit path loss, effectively reducing the signal level at the received signal. Thedegree in which the received signal strength deviates from the outer limits of itstarget window to the amount of correction transmitted in DMAC is controlled bythe Dynamic Power Control State - TDMA Slope parameter.

The slope can be set between 0 and 2. A zero value keeps the target levelconstant. A value greater than zero will move the target level in proportion with theDMAC, so that the higher the slope, the smaller the change in mobile attenuationfor a given change in received signal strength at the serving antenna face. Therate at which the received signal strength is compared with the window outer limitsis defined by the TDMA Measurement Process Interval parameter. This may beset from 1 to 6 seconds (in 1-second increments) on the ceqcom2 RC/V form.

401-200-112, Issue 11 June 2001 1-51


Introduction

1.5.1.4.7Downlink Dynamic Power Control (DDPC)

The DDPC feature reduces downlink RF interference by controlling the celltransmit signal (power level) as a function of the mobile reported signal strength.This feature (DDPC) is introduce in release R15.0 and is discussed in detail in401-612-316.

The mobile receive signal strength may vary as a function the distances betweenthe cell site and the mobile or the number of obstacles in the RF path. Becauseeach DRU/EDRU may service up to three mobiles at a time, the DRU/EDRU mustbe able to switch power levels on a per-time-slot basis. This feature uses theMAHO signal strength and voice quality report from each mobile on the RFchannel to determine the minimum cell transmit power level required to maintainquality voice channel service with that mobile. As a result, the cell transmit poweris attenuated during each time-slot period in accordance with the MAHO reporteddata for that time-slot period.

To maintain a quality voice channel, the cell periodically monitors the mobile’sreported Bit Error Rate (BER) class codes to ensure that the reduction in transmitpower does not result in a BER increase. The voice quality at the mobile isdetermined by its reported BER class code that is extracted from its MAHO data.The cell then determines if the BER value remains with a set Target BER Classvalue entered into the RC/V database via the fci form. The DDPC algorithm willregulate the cell transmit power to keep the mobile’s reported BER value within itsset target BER class, without exceeding the VRAL setting for maximum power.

DDPC for All TDMA Mobiles. 1In this mode, the amount of transmit powerswitching (attenuation), from one time slot to another on the same RF channel,must be within the narrow range set by the IFPV RC/V parameter. This is becauseeach mobile on an RF channel must be able to receive time-slot synchronizingdata which is transmitted throughout the six-time slot TDMA Frame period. If theamount of attenuation is not limited within the IFPV range, the most distantmobile, requiring the highest transmit power level, may not be able to receivetime-slot synchronizing data other than during its time-slot period. As a result, thecall serviced by the mobile is dropped.

The total dynamic range of the transmit power is established by the DDPC RangeRC/V parameter. This parameter is set from 0 to 7, where each step correspondsto 4 dB, resulting in a dynamic transmit power range of 0 to 28 dB. This parameterdiffers from the IFPV which specifies the power range between time slots in theTDMA frame.

To ensure that the most distant mobile requiring the highest transmit powerreceives time-slot synchronizing data at an adequate signal strength levelthroughout the TDMA frame period, a narrow IFPV range parameter value mustbe used. The DDPC algorithm then subtracts the IFPV parameter value from thetransmit power level required by the most distant mobile to determine the lowesttransmit power permitted in the TDMA frame. For example, if the IFPV parameter

1-52 401-200-112, Issue 11 June 2001


Introduction

value is set to its default value, which is 6 dB, the lowest cell transmit powerrequired to service the closest mobiles cannot be attenuated more than 6 dB fromthe highest transmit power level required by the most distant mobile. Field testshave shown that the 6-dB default value ensures that all current mobiles canreceive adequate time-slot synchronizing data. The range of per-slot DDPC (whenthe IFPV parameter value is set to 6 dB) is shown in Figure 1-5 (waveform a).When the IFPV parameter value is set to 0 dB, a per-frame control is achieved asin waveform b of Figure 1-5. When this parameter value is selected, the transmitpower levels for all six time slots in the TDMA frame are fixed to the level requiredby the most distant mobile.

401-200-112, Issue 11 June 2001 1-53


Introduction

6

6

6

Figure 1-5 DDPC Transmit Power Waveforms

Waveform b shows that the most distant mobile is moving further from the cell sitecausing the power to increase and, for two reasons, is not entirely accurate in itsrepresentation:

1 2 3 4 5 6 1 2 3 4 5 61 2 3 4 5 1 2 3 4 56

1 2 3 4 5 6 1 2 3 4 5 61 2 3 4 5 1 2 3 4 5611

11 2 3 4 5 6 1 2 3 4 5 6 1 2 3 4 4b)

c)

Maximum spead between highest and lowest cell tramsmit power in the mode islimited by a low

All TDMA Mobiles

Intra Frame Power Variation RC/V parameter which is typically set to 6 dB.

40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame

40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame

40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame40-ms TDMA Frame 40-ms TDMA Frame 40-ms TDMA Frame

Special per frame mode were the Intra Frame Power Variation RC/V parameter is set to 0 dB.

6 dB Max

Maximum spead between highest and lowest cell tramsmit power in themode is expanded by a large

TIA/EIA 136 Rev A MobilesIntra Frame Power Variation RC/V parameter which may to a

maximum of 28 dB .

a)

28 dB Max

1-54 401-200-112, Issue 11 June 2001


Introduction

1. The MAHO reports are received approximately every second (25 TDMAframes), therefore, a power shift cannot occur on consecutive frames.

2. The maximum power shift to any mobile is 1 dB per slot.

1.5.2 DCCH Call Processing States

The DCCH, unlike the ACC, is actively involved with transmitting and receivinginformation to and from DCCH mobiles. The type of information varies by the callprocessing state. There are three different DCCH call processing statesassociated with the cell controlling a particular mobile. These states parallel theapplicable mobile states specified in the IS-136 Standard. For more information,refer to the IS-136 standard. The states are as follows:

■ DCCH Idle State—In this state, the cell is not processing any given mobile.Instead, the cell is performing the general DCCH-related function oftransmitting the Broadcast Control Channel (BCCH) messages that areread by all mobiles selecting or reselecting to a DCCH. The cell is alsowaiting for DCCH-related messages from either the ECP or from themobiles.

■ DCCH Registration State—In this state, the cell processes a Registrationmessage from a mobile on the DCCH. The Registration message may ormay not have other messages appended to it (i.e., Authentication, SerialNumber), which are also processed in this state.

■ DCCH Origination / Termination State— In this state, the cell processesan Origination or Page Response from a mobile on the DCCH. TheOrigination or Page Response message may or may not have othermessages appended to it (i.e., Authentication, Serial Number, MobileAssisted Channel Allocation Report), which are also processed in thisstate.

1.5.3 Advanced Features for DCCH

In addition to increased system capacity and functionality, DCCH allows for manyenhanced capabilities and services such as Short Message Service, Sleep Mode,and Public/Private System Differentiation Capability, briefly described below. Formore information on these and other advanced features, refer to Chapter 6.

■ Short Message Service (SMS)—Supports point-to-point pager-likemobile-terminated short messages. Mobile-originated short messageservice is available starting with Release 12.0.

■ Sleep Mode Capability—Allows a mobile unit monitoring a DCCH to turnits receiver off, while in the idle state, to conserve battery power. Themobile wakes up periodically to check for paging information and then

401-200-112, Issue 11 June 2001 1-55


Introduction

returns to Sleep Mode until the next predetermined interval. Sleep periodsare determined by the Paging Frame Class, which defines the length oftime that paging information is broadcast over the DCCH.

■ Public/Private System Differentiation Capability—DCCH supportsprivate and residential networks as well as public networks. With Public/Private System Differentiation, service providers can create in-buildingwireless Private Branch Exchange (PBX) environments. For instance, acell site intended for a predefined set of private users (such as an indoormicrocellular system at a corporation) could be assigned a Private SystemIdentifier and function as a private network.

1.5.4 Message Center

The Message Center (MC) is a feature that forms a logical extension of theservice provider’s cellular network, providing the ability to deliver enhanced end-user services. Lucent Technologies provides an interface to a Message Center,but does not provide Message Center equipment. Advanced services availablethrough the Message Center feature include:

■ Audio response prompts and Dual-Tone Multi-Frequency reception for dial-in access directly from the PSTN, or to a caller redirected to the MC by theservicing Mobile Switching Center (MSC).

■ User interface with menus and entry fields for dial-in or dedicated dataterminal access.

■ Short Message Service (SMS) between mobiles and cell sites.

■ Storage and forwarding facility for Short Text Messages and Reach MeNumbers. This is used when mobile is not available on first messagedelivery attempt.

■ Forwarding of Voice Mail Notification information. The information includesnotification of new voice mail messages and an indication of the number ofunheard messages targeted for a subscriber.

■ Billing and service measurements that allow a service provider to offer itscustomers a variety of products such as the ones mentioned above: ShortText Messages, Reach Me Numbers and Voice Mail.

The industry is in the process of defining three configurations of SMS:

■ Point-to-Point Service—Provides for the transmission and reception ofmessages targeted for or received from individual mobiles. A storedmessage in the MC is forwarded only to one SMS subscriber.

■ Multipoint Services—Delivers a stored message to many SMS subscriberson a group list.

1-56 401-200-112, Issue 11 June 2001


Introduction

■ Broadcast Services—Delivers a stored message to all subscribers in aservice area.

1.6 Technician Interface

The technician interface for TDMA and DCCH is similar to AMPS. There are nonew Input/Output messages or status display pages, although both have beenmodified, where appropriate. For details, refer to Chapter 5.

Input/Output Messages

Some existing Technician Interface (TI) input messages for AMPS have beenmodified to include options for TDMA and DCCH, while others are unchanged forTDMA/DCCH. For example:

■ the op:cell command, which is used to obtain the operational status ofspecific hardware, provides options for TDMA beacon radios and DCCH:

■ op:cell x,beacon

■ op:cell x,dcch

■ the dgn:cell command, on the other hand, is unchanged, but the response(output message) is customized to the unit being diagnosed (AMPS orTDMA). The system knows the type or radio being diagnosed,automatically selects the appropriate test radio (RTU or TRTU), andproduces technology-specific output messages.

Output messages have also been modified to provide appropriate responseswhen TDMA or DCCH equipment is involved with the output message. StatusDisplay Pages

Status Display Pages are also modified to provide information about TDMA andDCCH.

1.7 Recommendations

This section provides recommendations for optimal TDMA and DCCHperformance. It covers a recommended optional feature (ARR), providesguidelines for radio and cell configuration, and gives recommended values forcertain translations.

■ Automatic Radio Reconfiguration (ARR)

■ Dual Server Group Cells

■ MAHO Beacon Channels

■ Shortened Burst

401-200-112, Issue 11 June 2001 1-57


Introduction

■ Color Codes

■ Audio Levels

Note: In addition to the recommendations in this section, recommendations areprovided throughout this document.

1.7.1 Automatic Radio Reconfiguration (ARR)

Lucent Technologies strongly recommends use of the Automatic RadioReconfiguration (ARR) feature to protect beacon voice channels from serviceinterruption, which adversely affects TDMA handoff performance.

ARR provides the capability of reassigning like-technology voice radios to fill therole of a MAHO channel or DCCH when the original radio unit fails. Use of ARRensures uninterrupted MAHO or DCCH functionality. In the event of a MAHOchannel failure (a beacon channel in the case of an RCU, a DRU or an EDRU),ARR would conscript a like-technology voice radio to serve as a beacon, whilemaintaining its voice functionality. For more information on ARR, refer to Chapter6.

1.7.2 Dual Server Group Cells

In Series II cell sites, TDMA is supported on single server group or dual servergroup cell configurations. Various capabilities are provided to enhance TDMAperformance on dual cells. Normally, on dual-server group cells, the inner servergroup is generally given preference over the outer server group during call setupand handoff.

When the TDMA Affected Server Selection (TASS) feature is enabled, theopposite is true. This feature selects a TDMA radio over an AMPS radioregardless of the server group (provided the call can be properly served by thatradio).

The discussion in Chapter 4 on MAHO neighbors includes recommendations forsetting bias values for dual server group cells. For additional information on dualcells, refer to CIB 228-AUTOPLEX Cellular Telecommunications Systems DualServer Group Cell Applications.

1.7.3 MAHO Channel/Beacon Channel

In general, a MAHO channel is implemented and defined on a per-sector basis asa physical radio whose transmitter is always on, transmitting at constant power.MAHO can be implemented on an Analog Control Channel (ACC) radio, an

1-58 401-200-112, Issue 11 June 2001


Introduction

analog voice Radio Channel Unit (RCU), or a DRU/EDRU serving as a DTC or aDCCH.

When implemented on a voice RCU or voice DRU/EDRU, the MAHO channel iscommonly referred to as a beacon. The reason for this distinction is that a voiceradio has to be designated as a beacon in the RC/V Cell Trunk Member (CTM)form). The beacon designation tells the system to keep the radio transmitter on,transmitting at constant power. When assigning a voice DRU/EDRU as a beacon,the beacon designation must be made for all three time slots, since each time slothas a CTM form associated with it.

By contrast, with an ACC or DCCH, no beacon designation is required becausethe transmitter is always on by default. Using a control channel (ACC or DCCH)as a MAHO channel, or a voice channel as a MAHO channel (beacon) does notimpact its primary role.

Dual Server Group Cells

On dual server group cell sites, the MAHO or beacon channel must be assignedto the outer server group (SG1) to ensure complete coverage of the area servedby the sector. Assigning the MAHO or beacon channel to the inner server group(SG0) would reduce the coverage area of the beacon since transmitter powerlevels are lower when assigned to an inner server group. (Inner server groups aredesigned to cover a smaller area.) Information on MAHO or beacon channelplanning is provided in Chapter 2.

1.7.4 Shortened Burst

All TDMA calls transmit messages in bursts to occupy one of the radio channeltime slots; however, because the distance between the mobile and the cellantenna is initially unknown, the radio wave propagation time is also unknown.This results in a delay that is initially indeterminate.

To prevent this delay from causing the message burst to overlap into the time slotallocated to another TDMA call on the same DRU/EDRU, the transmission entersa shortened burst mode on setup and handoff (optional). Shortened burst modepads the data with multiple syncwords and guard symbols. These additionalsymbols provides enough data to ensure that the real information arrives at thecell within the assigned time slot.

Based on the time that the cell receives this shortened burst, it sends messagesto the mobile on how to adjust its timing. The process by which the cell monitorsthe received signal timing from the mobile and tells the mobile how to adjust itstiming is called Time Alignment (TA). Time alignment continues throughout theduration of a call.

401-200-112, Issue 11 June 2001 1-59


Introduction

■ For calls set up by an ACC, shortened burst always occurs during initialvoice channel confirmation, which is the final step in the call setup process.

■ For calls set up by a DCCH, shortened burst can be enabled or disabled bythe Shortened Burst during Call Setup translation.

Lucent Technologies recommends enabling shortened burst during handoff in thefollowing situations in order to avoid interference with adjacent time slots:

■ On call setup for large radius cells (e.g., five-mile radius or larger).

■ During handoff. For instance, if a large radius cell (e.g., greater than 10miles) is adjacent to a small radius cell (less than five miles) and a handoffoccurs between these two cells, it is necessary to make mobile timingadjustments just after the handoff.

1.7.5 Color Codes

Lucent Technologies recommends use of:

■ Digital Verification Color Code (DVCC) to minimize the effects of co-channel interference for IS136 mobiles. The simplest DVCC value is thecell site number. The exception to this is for cell numbers 45 and 162. Inthese case use numbers above 384 which is the maximum cell number.

■ Digital Color Code (DCC) to minimize the effects of co-channel interferenceon call setup. This translation can be combined with Supervisory ColorCodes 1 and 2 to create 64 color code combinations that provide a uniqueidentifier for each cell.

1.7.6 Audio Levels

Voice transmission levels within the AUTOPLEX system are set so that theaverage speech level of a mobile user (sender) is received by the land-sidelistener at the same volume as a land-to-land call. Average speech levels from aland-side caller fully modulate an analog Frequency Modulated (FM) signalwithout excessive clipping or distortion by the deviation limiter. To match the audiolevels between RCUs and DRU/EDRUs, the values indicated below arerecommended.

■ Analog Rx Network Transmission Level -2

■ Analog Tx Network Transmission Level -4

■ Digital Rx Network Transmission Level 0

■ Digital Tx Network Transmission Level 0

These values are based on recommendations in Engineering Letter #54, Rev. 1,The Adjustment of Voice Transmission Levels in AUTOPLEX Cell Sites.

1-60 401-200-112, Issue 11 June 2001


Introduction

1.8 Conclusion

This document is intended as a guide to various aspects of TDMA and DCCH.The following chapters include detailed technical information about specific topicsas varied as installing hardware or performing service measurements. The readermay prefer to go directly to a relevant chapter rather than reading straight throughthe document.

401-200-112, Issue 11 June 2001 1-61


Introduction

1-62 401-200-112, Issue 11 June 2001



Traffic and RF EngineeringGuidelines


2.2 DTC Traffic Engineering Guidelines 2-3

2.2.1 Introduction 2-4

2.2.2 Channel Usage Unit of Measurement 2-4

2.2.3 Blocking 2-5

2.2.4 Traffic Capacity Planning, Separated Systems 2-6

2.2.4.1 Traffic Capacity Analysis 2-6

2.2.4.2 Determining TDMA Traffic Proportion 2-7

2.2.5 Traffic Capacity Planning, Integrated Systems 2-8

2.2.6 Use of Erlang Tables 2-9

2.3 DCCH Traffic Capacity Guidelines 2-11

2.3.1 Forward Control Channel Messages 2-11

2.3.2 Traffic Assumptions 2-12

2.3.3 Forward DCCH Capacity Evaluation 2-12

2.3.3.1 Multiple DCCHs in a Sector 2-15

2.3.3.2 Paging Load 2-16

2.3.4 Reverse DCCH Capacity Evaluation 2-18

2.4 Digital Traffic Channel (DTC) RF Planning 2-19

2.4.1 Co-Channel Reuse Factor (K) Assignment 2-19

2.4.1.1 Co-Channel Reuse Factor Tradeoffs 2-202-20

2-19

2-19

2-18

2-16

2-15

2-12

2-12

2-11

2-11

2-9

2-8

2-7

2-6

2-6

2-5

2-4

2-4

2-3

2-1

June 2001 2-1

Contents

2.4.1.2 K Selection Process 2-20

2.4.1.3 Evaluating the Results 2-21

2.4.2 TDMA Adjacent and Alternate Channel Assignment 2-23

2.4.3 Analog/TDMA Channel Segmentation Guidelines 2-23

2.4.3.1 Analog/TDMA Adjacent Channel Interference 2-23

2.4.3.2 Analog/TDMA Co-Channel Interference 2-24

2.4.4 Trunk Assignment 2-25

2.5 RF Performance Study 2-25

2.5.1 Proprietary Statement 2-25

2.5.2 To Obtain Document 2-26

2.6 RF Channel Assignment for Mixed ACC/DCCHSystems 2-26

2.7 Flexible Channel Allocation (FLCA) Features 2-26

2.7.1 FLCA Planning and Implementation 2-28

2.8 TDMA Discontinuous Transmission with ComfortNoise Insertion (DTX/CNI)2-29

2.8.1 Voice Activity Detection (VAD) Algorithm 2-29

2.8.1.1 DTX/CNI Activation Restrictions 2-29

2.8.1.2 Other Restrictions 2-31

2.8.2 DTX/CNI Service Measurements 2-32

2.8.3 Feature Implementation 2-32

2.8.3.1 Executive Cellular Processor (ecp) Form 2-33

2.8.3.2 Series 2 Cell (cell2) Form 2-33

2.8.3.3 Face Code Information (fci) Form 2-33

2.8.3.4 Cellular Network (net) Form 2-33

2.8.3.5 Subscriber and feature Information (sub and soda) Form 2-34

2.8.3.6 Visitor Registration Information (vlr) Form 2-34

2.9 Digital Control Channel (DCCH) RF Planning 2-34

2.9.1 Recommended DCCH Channel Assignments 2-34

2.9.2 Two-DCCH Radio Deployment Scheme 2-35

2.9.3 Generalized Deployment Scheme 2-40

2.9.4 Channel Assignment Examples 2-422-42

2-40

2-35

2-34

2-34

2-34

2-34

2-33

2-33

2-33

2-33

2-32

2-32

2-31

2-29

2-29

2-28

2-26

2-26

2-26

2-25

2-25

2-25

2-24

2-23

2-23

2-23

2-21

2-20

2-2 401-200-112, Issue 11 June 2001


Contents

2.10 Alignment of DCCH Reselection and DTCHandoff Boundaries 2-46

2.10.1 DCCH Sector-Types 2-46

2.10.1.1 Preferred Neighbors 2-47

2.10.1.2 Regular Neighbors 2-47

2.10.1.3 Non-Preferred Neighbors 2-47

2.10.2 Matching Handoff and Reselection Boundaries 2-47

2.10.2.1 Limitations on DCCH and Handoff Algorithm Matching 2-47

2.10.2.2 DCCH Translation Definitions 2-48

2.10.2.3 MAHO Related Translations 2-48

2.10.2.4 DCCH Translation Settings Common to All Neighbors 2-49

2.10.2.5 MAHO Translations Common to All Neighbors 2-49

2.10.2.6 MAHO Translations for Preferred Neighbors 2-50

2.10.2.7 MAHO Translations for Regular Neighbors 2-50

2.10.2.8 MAHO Translations for Non-Preferred Neighbors 2-51

2.11 TDMA Hierarchical Cells 2-51

2.11.1 Operation Requirements 2-52

2.11.1.1 TDMA Hierarchical Cells 2-52

2.11.1.2 TDMA Full Rate 2-52

2.11.1.3 Digital Control Channel (DCCH) Feature 2-52


2.11.2 Modeled After DCCH Reselection Algorithms 2-52

2.11.3 Handoff and DCCH Reselection Boundary Misalignment 2-53

2.11.3.1 MAHO Handoff Boundary 2-53

2.11.3.2 DCCH Reselection Boundary 2-53

2.11.3.3 Speed-Trending Optimization 2-54

2.11.4 Hierarchical Cells Algorithm and Parameters 2-55

2.11.5 Cell Type Parameter 2-60

Preferential treatment for handoffs 2-61

2.11.6 H_DELAY Parameter 2-61

2.11.7 Handoff Criteria 2-62

2.11.7.1 Criteria 1 Qualifying Algorithm 2-622-62

2-62

2-61

2-61

2-60

2-55

2-54

2-53

2-53

2-53

2-52

2-52

2-52

2-52

2-52

2-52

2-51

2-51

2-50

2-50

2-49

2-49

2-48

2-48

2-47

2-47

2-47

2-47

2-47

2-46

2-46

401-200-112, Issue 11 June 2001 2-3


Contents


2.11.7.3 Ranking of Handoff Candidates 2-64

2.11.7.4 Intra-Cell Handoff 2-64

2.11.8 Mobile Speed Trending 2-64

2.11.9 Periodic Handoff Triggering 2-66

2.11.10 Feature Interaction 2-66

2.11.10.1 DCCH Non-Public Network Identifiers (NPNI) 2-66

2.11.10.2 Hand-Off Based on Interference TDMA (HOBIT) 2-67

2.11.10.3 DCCH Interhyperband Operations (DIHOP1and DIHOP2) 2-67

2.12 Two Branch Intelligent Antennas (TBIA)on the EDRU 2-67

2.13 Deployment Recommendations 2-68

2.13.1 Diversity Receive 2-68

2.13.2 Time Dispersion and Equalizers 2-69

2.13.3 MAHO Channel Assignment 2-69

2.13.3.1 Using ACC as MAHO Channel 2-69

2.13.3.2 Using Voice Channel as a MAHO Channel 2-70

2.13.3.3 Using DCCH as MAHO Channel 2-702-70

2-70

2-69

2-69

2-69

2-68

2-68

2-67

2-67

2-67

2-66

2-66

2-66

2-64

2-64

2-64

2-63

2-4 401-200-112, Issue 11 June 2001



Traffic and RF EngineeringGuidelines 2

2.1 Introduction

This chapter provides engineering guidelines for planning and deploying TDMAcellular systems. A wide range of disciplines are covered ranging from DTC andDCCH traffic engineering, to DCCH data format, RF planning, signal propagationand link budget analysis. Some of the major topics discussed are task oriented,where others give theoretical information which is essential for optimumperformance. Because the range of information presented is quiet broad and isaddressed to a readership of various levels of skill, the information is presented ina logical sequence so that the readers of lesser skills can develop theirknowledge as they advance through the chapter. It is recognized that not allreaders may need to, or want to, sequence through all the topics in this chapter,therefore, to aide those readers with specific task or objectives in mind, adescription of the major topics discussed is given in Table 2-1. This table alsoincludes major optional feature subsequent to ECP release R10.0.

Table 2-1 Chapter Overall View

TopicParagraph

No.Description

DTC Traffic Engi-neering Guidelines

2.2 Provides instructions in RF planning process thatinclude determining the service goals (capacity targetsand blocking goals) and the available resources (avail-able equipment and space).

June 2001 2-1

Traffic and RF Engineering Guidelines

DCCH TrafficCapacity Guide-lines

2.3 Presents a model for assessing the DCCH trafficcapacity. It discusses the assumptions underlying theanalysis, and examines the trade-offs between pagingand Short Message Service (SMS) messaging

Digital TrafficChannel (DTC) RFPlanning

2.4 Provides recommendations for Digital Traffic Channel(DTC) frequency planning. These recommendationsare based on an RF performance study conducted in alaboratory environment. For information about thereport document, refer to Paragraph 2.5.

RF PerformanceStudy

2.5 Identifies the RF performance study conducted byLucent Technologies and how a copy can be obtained.

RF ChannelAssignment forMixed ACC/DCCHSystems

2.6 Provide guidelines when both DCCH and ACC aresupported in the same network, follow the channelassignment rules below:

Flexible ChannelAllocation (FLCA)Feature

2.7 Provides an alternative to Flexed Channel Allocation(FCA) by permitting dynamic allocation of RF chan-nels to EDRU radios as the traffic need for additionalRF channels at specific cell site arises.

TDMA Discontinu-ous Transmission(DTX) with Com-fort Noise Insertion(CNI)

2.8 This feature provided in ECP and cell site releaseR14.0 permits TIA/EIA-136A compatible mobile sub-scribers and subscribers with TDX/CNI modified IS-136A mobiles to increase battery life by as much as30 percent. The increase in battery life is achieved byeither curtailing or completely eliminating the mobiletime slot transmission during the period when the sub-scriber is not speaking. Because the mobile is trans-mitting during a portion of the time slot period, the RFco-channel interference level is reduced at neighbor-ing cells by as much as 30 percent. This reductionpermits both DTX/CNI capable and non-DTX/CNIcapable mobiles to operate at lower power levels tofurther enhance battery life and increase battery talktime. Mobiles qualifying for DTX/CNI operation musthave their Station Class Mark field for discontinuoustransmission set to yes.

Table 2-1 Chapter Overall View —Continued

TopicParagraph

No.Description

2-2 401-200-112, Issue 11 June 2001



2.2 DTC Traffic EngineeringGuidelines

TDMA technology provides three voice channels over a single RF channel. Thisincreases system capacity using the same number of RF channels. Toaccommodate both analog and TDMA mobiles, a cell must be equipped with bothAMPS and TDMA technology. These systems can be either separated orintegrated. In either case, design of the appropriate mix of technology requires anassessment of the proportion of digital to analog traffic, based on the market

Digital ControlChannel (DCCH)RF Planning

2.9 Provides guidelines for DCCH channels assignmentsto minimize co-DCCH channel interference. Demon-strates co-DTC vs. co-DCCH interference, and theeffect of doubling and tripling the DCCH frequencyreuse pattern. Discusses DCCH channel frequencyallocation to reduce the time a mobile unit takes to finda DCCH channel.

Alignment ofDCCH Reselectionand DTC HandoffBoundaries

2.10 Describes how to align DCCH reselection and DTChandoff boundaries in environments such as a privatenetwork.

TDMA HierarchicalCells

2.11 Introduces additional criteria that may be consideredwhen selecting a handoff candidate. The additionalcriteria allow the service provider to exercise bettercontrol of the hand-off process. This control allows thecall to be handed off to the candidate cell best suitedto handle the call in accordance with the service pro-vider’s overall strategy. This feature is especially use-ful when operating in areas with a mix of small andlarge cells, as well as in areas with public and privatesystems in a DCCH environment.

Two Branch Intelli-gent Antenna onthe EDRU

2.12 Takes advantage of the currently deployed two diver-sity receive antenna array to improve voice quality inthe presents of interference using an adaptiveantenna beam forming technique. Effectively, thistechnique narrows the receive antenna lobe width andaims its boresight in the direction of the mobile unitcurrently being serviced.

Table 2-1 Chapter Overall View —Continued

TopicParagraph

No.Description

401-200-112, Issue 11 June 2001 2-3



penetration of TDMA mobiles requiring digital service. Other key parameters arethe amount of blocking, and whether blocked calls are cleared (dropped), queued,or overflowed to the other technology,

The following sections provides an introduction to system traffic capacity designissues, including discussions on the channel usage unit of measurement (theErlang) and blocking. Additional sections examine traffic capacity issues in detailfor both separated and integrated analog/TDMA systems.

2.2.1 Introduction

Fundamental elements of system design include determining the number ofchannels needed to meet capacity targets and call blocking objectives. In otherwords, the system is set up to accommodate a maximum number of types of callsat a specified rate of blocking. This is done using the capacity values given in thetraffic tables. Steps in the RF planning process include determining the servicegoals (capacity targets and blocking goals) and the available resources (availableequipment and space). For example:

■ Determine number of channels analog/TDMA available, taking intoconsideration any limitations on channel-assignment patterns for otherreasons, such as adjacent-channel interference

■ Determine any limitations on the number of radios at a cell site for otherreasons, such as space limitations

■ Estimate number of channels needed to ensure that capacity targets aremet (adequately service anticipated traffic loads without exceedingblocking objectives)

■ Set blocking objectives consistent with the desired grade of service for thesystem

■ Consider dualization and other arrangements that divide the pool of avail-able channels.

After setting system policy goals and determining available resources, the nextstep is to determine the allocation of analog/TDMA channels using the tablesincluded in Appendix A.

2.2.2 Channel Usage Unit of Measurement

The measure of usage for a set of channels is the dimensionless quantity calledthe Erlang. The Erlang is obtained by multiplying the average rate of incomingcalls by the average duration of the calls. One Erlang corresponds to one channelcontinuously occupied, so that the averaged interval of time between call arrivalsis exactly equal to the averaged call duration. Traffic load, used synonymouslywith channel usage, is expressed in Erlangs. It refers to the rate of incoming calls

2-4 401-200-112, Issue 11 June 2001



and their duration as described above. TDMA technology allows more Erlangs oftraffic to be handled per cell by providing more channels per radio.

2.2.3 Blocking

The capacity of the channels for a cell (or for a sector) is the maximum traffic loadthat meets blocking objectives. Blocking refers to a situation when the channels ofa set are busy, so a call is dropped, queued or overflowed to the other technology.Maximum acceptable blocking rate (the percentage of time that blocking occurs),a key element of system design, can be specified in an analog/TDMA system forthe analog channels, the digital channels, or the system as a whole.

Formulas for blocking in terms of the number of channels and the traffic load arebased on statistics of telecommunication traffic (i.e., Poisson distributed arrivaltimes and exponentially distributed call durations). Two formulas can be used:

■ When blocked calls are cleared or dropped, and do not compete forservice, the Erlang B formula applies. It has been evaluated in standardtraffic tables (referred to as Erlang B tables). Appendix A, Tables A-1through A-6 provide system capacity levels for various levels of TDMAmarket penetration and blocking.

■ When blocked calls are queued (for example, by means of a holding buffer)and still compete for service—and no limit is assumed on the length of thequeue—the Erlang C formula applies. Refer to Appendix A, Tables A-7through A-12.

The blocking rate (C) refers to the percentage of calls that enter the queue. Interms of the Erlang B values (B), the probability of a delay is given by the followingequation:

where a denotes the traffic load in Erlangs and N denotes the number ofchannels. In practice, both tables are used for determining capacity for mixedsystems.

The following subsections show how to determine capacity for mixed analog/TDMA deployments. Two kinds of system are possible:

■ Separated—AMPS/TDMA co-located, with no call overflow betweentechnologies (Erlang B applies).

C B

1aN----� �� 1 B–( )⋅–

� �� ----------------------------------------------=

401-200-112, Issue 11 June 2001 2-5



■ Integrated—TDMA calls can be overflowed to analog channels as needed(Erlang C applies).

In a separated system, blocking objectives are established for each technology. Akey element of the integrated system design is setting blocking objectives thatprovide a desired level of customer service. Blocking objectives are set for eitherthe analog system or the system as a whole.

Blocking objectives for integrated systems may set the maximum rate of blockingfor just the analog channels (Ba) or for the system as a whole (Bs). The generalrelationship between Bs and Ba shows that the system blocking rate Bsis alwaysless than the analog blocking rate Ba, when p>0%, essentially because only afraction of requests for digital channels go to the analog channels. Thus, a limit onsystem blocking results in a less stringent objective than the same limit on analogblocking. Blocking objectives are not specified for the TDMA channels because ofthe overflow to the analog channels.

As blocking objectives are not specified for the TDMA channels, their blockingrate could be relatively high. Consequently, traffic overflow from the TDMAchannels cannot be neglected as in the previous subsection, and so calculation ofcapacity gets more complicated for fully integrated systems.

2.2.4 Traffic Capacity Planning, SeparatedSystems

This subsection shows how to determine capacity for TDMA deployments in whichthe TDMA channels and analog channels are parts of a separated system. Thetwo systems are co-located but do not interact; each is governed by its ownblocking objective.

Typically, a separated system deployment has the same number of TDMA voicechannels at sectors throughout the TDMA coverage region. This approach issimple and provides uniform capacity over the TDMA region.

2.2.4.1 Traffic Capacity Analysis

Traffic capacity for the analog and TDMA parts of a separated system can bedetermined from traffic tables, as described in the preceding subsection. Forexample, a cell sector with an RF allocation of 19 channels may have two TDMAchannels overlaid on 17 RF analog channels. Table A-2, Appendix A, indicates:

■ Analog system with 17 channels can provide 10.7 Erlangs of capacitywhen blocked calls are cleared and blocking probability is 2.0% or less.

■ TDMA system with two TDMA radios, which corresponds to six TDMAvoice channels, can provide 2.28 Erlangs of capacity for the same blockingobjective.

2-6 401-200-112, Issue 11 June 2001



Adding the two capacities gives a total of 13.0 Erlangs, which is more than the12.3 Erlangs obtained when the analog system uses all 19 RF channels for thecell sector. This is a result of having 23 voice channels.

The sum of the capacities for the two individual technologies represents thegreatest possible capacity for the cell. The full capacity is used when theproportions of actual analog and TDMA traffic volume match the designedcapacities of each system; otherwise, the cell will either block or be under-used.

2.2.4.2 Determining TDMA Traffic Proportion

The ratio of TDMA traffic to analog traffic is a key quantity in determining capacityfor mixed-technology systems. Full use of separated system capacity isdependent on accurate forecasting of TDMA market penetration, so that the ratioof TDMA to analog facilities reflects the market mix.

If the proportion of TDMA traffic is denoted by p, then the proportion of analogtraffic is 1-p. The total traffic load in units of Erlangs, denoted a, splits into paErlangs for the TDMA system, and (1-p)a Erlangs for the analog system.

For a given proportion p, the maximum total traffic load for the two systems (Ct) isgiven by the following equation:

where Cd is the capacity of the TDMA system and Ca is the capacity of the analogsystem. This quantity (Ct) attains its maximum value when:

In this example, the combined TDMA/analog capacity of 13.0 Erlangs is fullyutilized when the TDMA mobile market penetration is 17.5% (p = 2.28 / 13.0), asplanned. Using the same configuration, but with an actual TDMA marketpenetration percentage that is different, efficiency will be reduced:

■ A higher percentage of TDMA mobiles in this market will result in blockedTDMA calls and underused analog capacity.

■ A lower percentage of TDMA mobiles in this market will result in underusedTDMA capacity, and blocked analog capacity.

Separated System Design Example

Ct minimumofCd

p------and

Ca

1 p–( )----------------� ��

=

pCd

Cd Ca+( )-----------------------=

401-200-112, Issue 11 June 2001 2-7



Assume that an analog system needs 17 or fewer channels over the TDMAcoverage region to handle the offered traffic load. In this case, the TDMA voicechannels provide an extra 2.28 Erlangs of capacity.

On the other hand, if analog channels have to be removed to accommodateTDMA voice channels, then the number of RF channels and possibly theproportion (p) of TDMA traffic must be carefully engineered to ensure adequatecapacity.

For example, if 15.0 Erlangs are desired at a cell sector, then at least four TDMAradios are required together with a proportion p greater than 40%. The four TDMAradios correspond to 12 TDMA voice channels, which would provide 6.61 Erlangsof capacity; the remaining 15 analog channels provide 9.01 Erlangs. Thiscombination can give a sum of 15.62 Erlangs when p=6.61/15.62=42.3%. If theactual traffic load differs from the design, then the system is less efficient:

■ When p=40%, the system provides only 15.01 Erlangs

■ When p=45%, the system provides only 14.69 Erlangs.

Thus, to achieve much higher capacity by means of a separated system, theproportion p must be tightly controlled, by controlling entry into the two systems.

In this section, traffic loads carried on the two systems were assumed to beindependent. Although handoffs generally do not occur between separatedsystems, some systems allow dual-mode mobiles attempting to set up a call on aTDMA channel to access an analog channel when no TDMA channel is available.In such systems, part of the analog traffic may consist of this overflow from theTDMA system. The magnitude of overflow should be less than 1% and can beignored in the traffic capacity calculation shown below:

Specifically, overflow is estimated as Bd p/3, where Bd is the blocking rate of theTDMA system and 1/3 is the estimate that two of every three requests for achannel are for handoffs, and one of the three is for setting up the call. With 2%blocking and p=40%, overflow equals 0.3% (a negligible amount).

Integrated systems, discussed in the next subsection, have overflow that cannotbe neglected and require a different calculation of capacity.

2.2.5 Traffic Capacity Planning, IntegratedSystems

In an integrated system, the two technologies share resources, allowing TDMAcalls to overflow to analog when TDMA blocking occurs. This is equivalent to

OverflowBd p⋅

3-------------=

2-8 401-200-112, Issue 11 June 2001



queuing a blocked call, rather than clearing or dropping it. In this situation, ErlangC tables apply for traffic capacity planning.

The traffic flow for an integrated system is shown in Figure 2-1. below.

Figure 2-1. Traffic Flow for an Integrated AMPS/TDMA Stream

In this figure, the traffic load a splits into pa Erlangs for the nd TDMA channels,and (1-p)a Erlangs for the na analog channels. When all TDMA channels arebusy, requests for service from dual-mode mobiles are sent to the analogchannels as overflow from the digital channels.

An integrated system has greater capacity than a separated system. It is alsomore efficient to expand because capacity increases whenever the proportion ofTDMA traffic p increases. By contrast, in a separated system, total capacity ofseparated systems always decreases when p increases beyond optimum.

2.2.6 Use of Erlang Tables

Tables A-1 through A-12, Appendix A, show traffic capacity levels as a function ofTDMA market penetration p for various allocations of channels and variousblocking objectives.

Tables A-1, A-2, and A-3 show traffic capacity levels for situations where blockedanalog calls are cleared and system blocking is specified as 1.0%, 2.0%, and5.0%, respectively. The channel allocations correspond to a configuration with 19RF channels, the maximum per sector for a three-sector system. The first columnof the tables gives the number (na) of analog channels, and the second columngives the number (nd) of TDMA voice channels (three times the number of TDMARF channels). Columns 3-10 give corresponding values of capacity in Erlangs forp from 0% to 100%. In general, the following observations hold for these tables:

TDMA Channels

Analog Channels

p a(1 - p) a

401-200-112, Issue 11 June 2001 2-9



■ When p=0%, all traffic goes to the analog channels, so capacity decreasesas the number of analog channels (na) decreases.

■ When p=100%, capacity increases as the total number of channels(na+nd) increases.

■ For intermediate values of p, an optimum allocation of channels providesmaximum capacity. In the tables, these optimum values are shown in boldface type. For example, in Table A-1 the combination of na=17, nd=6provides a maximum capacity of 13.55 Erlangs when p=30%. Thecombination of na=9, nd=30 provides a maximum of 25.02 Erlangs whenp=80%.

For a fixed allocation of radios, capacity increases as p increases. For example, inTable A-1, na=15, nd=12 provides 10.47 Erlangs when p=20%, and 17.69 Erlangswhen p=80%.

As the tables show,

■ When system blocking Bs increases, the relationship between capacity andthe quantities na, nd, and p is unchanged. This means that for each p,there is an optimal channel mix (shown in bold face type).

■ When blocking rate increases, the capacity values increase correspondingto the less stringent blocking objective.

■ Optimum channel allocation may change. For example, Table A-2 (Bs=2.0%) shows that the optimum capacity of 27.77 occurs for na=9, nd=30and p=80%. Table A-3 (Bs =5.0%) shows that the optimum capacity of32.77 occurs for na=8, nd=33 and p=80%.

Tables A-4, A-5, and A-6 show traffic capacity in situations where blocked analogcalls are cleared and blocking of analog channels is specified as 1%, 2%, and 5%,respectively. The format is the same as in Tables A-1 through A-3. The columnsfor p=0% match the corresponding columns in Tables A-1 through A-3 becausewhen p=0%, only analog channels are involved. Otherwise, correspondingcapacity values are lower when analog blocking objectives are specified. Forexample, in a system with p=30%, and na=17, nd=6,

■ Analog blocking Ba is 1.0%, a maximum of 13.04 Erlangs (Table A-4) isobtained.

■ System blocking Bs is 1.0%, a maximum of 13.55 Erlangs is obtained(Table A-1).

In summary, if higher blocking can be tolerated from a customer service point ofview, then using system blocking will a allow for greater system load.

Tables A-7, A-8, and A-9 give traffic capacity for situations where blocked analogcalls are queued and the probability of a delay for the system is specified as 1.0%,

2-10 401-200-112, Issue 11 June 2001



2.0%, and 5.0%, respectively. The capacity trends are similar to those that occurwhen blocked calls are cleared, as shown in Tables A-1 through A-3.

When TDMA blocked calls are queued or overflowed to analog, rather thancleared or dropped,

■ Capacity values are lower because the queue calls continue to compete forservice as new calls come in.

■ For high values of p, the optimum radio mix will change compared to thedropped call case. When Bs = 2.0% and p=80%, the optimum channel mixfor the queuing system (Table A-8) is na=10, nd=27. For the clearingsystem (Table A-2), it is na=9, nd=30.

Tables A-10, A-11, and A-12 give traffic capacity for situations where blockedanalog calls are queued and the probability of a delay for the analog channels isspecified as 1.0%, 2.0%, and 5.0%, respectively. The results are similar to theresults in Tables A-4 through A-6, except that the values of capacity are lower andoccasionally, the optimum allocations differ.

2.3 DCCH Traffic CapacityGuidelines

This section presents a model for assessing the DCCH traffic capacity. Itdiscusses the assumptions underlying the analysis, and examines the tradeoffsbetween paging and Short Message Service (SMS) messaging.

2.3.1 Forward Control Channel Messages

The forward control channel of an IS-136 DCCH carries overhead messages,standard call processing messages (paging, orders and registrationconfirmations), and point-to-point Short Message Service (SMS) messages.These messages are carried in two channels:

■ The logical Broadcast Control Channel (BCCH) of a DCCH, whichoccupies Nb (BCCH slots) of the 32 slots in a superframe, carries overheadmessages.

■ The logical SMS point-to-point, Paging, and Access response Channel(SPACH) of a DCCH occupy the remaining 32 - Nb slots in the superframe.The SPACH carries pages, orders, registration confirmations and point-to-point SMS messages. A capacity limitation in SPACH is that paging in theprimary superframe is always repeated in the secondary superframe.

401-200-112, Issue 11 June 2001 2-11



2.3.2 Traffic Assumptions

In the model for DCCH traffic capacity planning discussed in this chapter, thesystem is assumed to be operating at the following system load level:

■ 8800 Busy Hour Call Attempts (BHCA) per Cell

■ 4600 Completed Calls Per Busy Hour per Cell

■ 36000 Mobile Registrations Per Hour per Cell

■ 108000 Pages per Hour (30 pages/second)

The configuration supporting the above load is assumed to include:

■ 192 channels, a 75-second call holding time and 3% blocking

■ Three-sector cells, with each sector carrying one third of the traffic

■ Flood paging (paging replicated in all three sectors)

In the case of a mixed AMPS/TDMA environment, the above load represents thetotal traffic supported by the Series II cell. In such an environment, only a fractionof the call processing traffic is carried by the DCCH; the rest is carried by theAnalog Control Channel (ACC).

The DCCH typically carries pages intended for IS-136 compliant mobiles. Forthese mobiles, the system provides paging options such as paging on bothtechnologies (ACC and DCCH), and paging on the last technology seen at thetime of last registration. If the system knows that a mobile is an AMPS or an IS-54B mobile, it will not page that mobile on the DCCH, regardless of the pagingoption used.

2.3.3 Forward DCCH Capacity Evaluation

Table 2-1 below shows the translation values (or range) used in this section. TheSMS message length is assumed to be uniformly distributed between 16 and 194characters, which corresponds to an average of 105 characters per message. TheSMS payload size is limited by the standard to 194 characters. This is because ofthe limitation on the size of messages between the Message Center and theMobile Switching Center (MSC) (IS-41 T-CAP messages).

Table 2-2 Parameters for DCCH Capacity Evaluation

Parameter Value Parameter Value

Autonomous register/hour/cell 36000 % of BHCA that are mobile originated 65%

Pages/hour/sector 108000 % of originations that are answered 65%

2-12 401-200-112, Issue 11 June 2001



The model used in this analysis demonstrates the sensitivity of SMS capacity tovarious parameters. The calculation includes an estimate of the average numberof slots used by paging, channel assignments, and registration confirmations. Itassumes that the remaining SPACH slots may be used for SMS paging and point-to-point messages. With flood paging, the forward DCCH carries many more SMSpaging messages (SPACH notifications indicating R-DATA) than SMS contentmessages.

The following parameters are used in deriving the SPACH channel utilization:

■ Ns is the number of SPACH slots per superframe (Ns = 32 - Nb)

■ P is the number of pages per second

■ O is the number of orders

■ R is the number of registrations per second per sector

■ S is the number of SPACH notifications per second

■ M is the number of SMS messages per second per sector

■ L is the average length of an SMS message in terms of the number ofSPACH slots

■ F is the IS-136 mobile penetration factor

■ Us is the utilization of the SPACH channel

■ α is the effective packing ratio for pages (1 < α < 3)

■ β is the effective packing ratio for SPACH notifications (1 < β < 2)

Busy hour call attempts/cell 8800 % of originations that are notanswered

35%

Number of sectors/cell 3 % of BHCA that are mobileterminations

35%

Number of DCCH channels/sector

1-3 % of terminations that are paged 88%

IS-136 mobile penetration 0-100% % of pages that elicit a page response 35%

SMS message length in bytes 16-194 Number of pages/SPACH slot 1-3

Number of SPACH slots/SMSmessage

3-21 Number of SPACH notif./SPACH slot 1-2

Number of BCCH slots (Nb) 9 Number of SPACH slots/channelassignments

2

Ratio of SPACH notifications toSMS messages

30-150 Number of SPACH slots/registrationconfirmations

1

Table 2-2 Parameters for DCCH Capacity Evaluation

401-200-112, Issue 11 June 2001 2-13



The use of the SPACH channel (Us) is determined by the following equation:

■ The factor of 2 in the term for orders (O) reflects the fact that orders usetwo SPACH slots.

■ The factor of 2 in the terms for pages (P) and SPACH notifications (S)reflects the fact that Paging Channel (PCH) slots in a primary superframemust be repeated in the secondary superframe.

For a typical traffic mix of pages and SMS messages, the packing ratios α and βare both approximately 1.5. These ratios are somewhat dependent on the mix ofcall processing vs. SMS messages, and the amount of paging versus non-pagingmessages.

As the DCCH call processing load increases (IS-136 market penetrationincreases above 50%), the call processing related messages carried by theDCCH increase. This means that the page packing ratio α that can be achievedwill be higher than 1.5. At the same time, the number of SMS messages that canbe carried by the channel decreases, and the packing ratio for SPACHnotifications may decrease.

To meet the delay requirement in the IS-136 standard, channel utilization must bekept under 100%. For SMS delivery, the delay requirement specifies that the timebetween the mobile response to a SPACH notification and completion of themessage delivery must not exceed 16 seconds.

Simulation results indicate that SPACH utilization should be under 85% to ensurereasonable delay for SMS messages. Achievable SPACH utilization depends onSMS message length. The utilization percentage mentioned above correspondsto a uniform distribution between the minimum and maximum SMS messagelengths.

■ If the distribution includes a higher percentage of short messages, higherSPACH utilization can be achieved without risking delays in messagedelivery that could cause the mobile to time out.

■ If the distribution includes a higher percentage of long messages, SPACHutilization must be kept lower to ensure acceptable delays.

Figure 2-2. below shows SMS message capacity for different values of theSPACH notification rate as a function of the IS-136 mobile market penetrationfactor (F). For example, for a 50% IS-136 mobile penetration factor, and a SPACHnotification rate of 15000 SPACH notifications per hour, the DCCH can carry 600SMS messages per hour. The numbers in Figure 2-2. represent SMS capacity in

1.282Pα-------

2 O⋅ R+ +� �� F 2S

β------M L⋅+ +� �

� � 2Ns= Us

2-14 401-200-112, Issue 11 June 2001



one sector. SMS capacity per cell is three times as high as that for the initialassumption for three-sector cells.

Figure 2-2. DCCH SMS Capacity as a Function of IS-136 Mobile Penetration

2.3.3.1 Multiple DCCHs in a Sector

Paging, call processing, and SMS-related (SPACH notification) messages use asignificant portion of SPACH capacity. Using multiple DCCHs per sector allows forpaging on a DCCH-specific basis, distributing the paging load over the availableDCCHs in the sector. Doubling the number of DCCHs from one to two more thandoubles SMS capacity. Figure 2-3. illustrates the significant increase in SMScapacity gained by using two DCCHs. Lucent Technologies recommends using asecond DCCH whenever the utilization of SPACH of the first DCCH reaches 85%of its full capacity.

For example, for a 50% IS-136 mobile penetration factor, and a SPACHnotification rate of 70000 SPACH notifications per hour, a pair of DCCHs can carryapproximately 2200 SMS messages per hour, per sector.

one DCCH / sector

0

1000

2000

3000

4000

5000

6000

7000

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9 1

IS-136 mobile penetration

SMS

mes

sage

/ hr

SPACH notif / hr = 5000








401-200-112, Issue 11 June 2001 2-15



Figure 2-3. SMS Capacity for Two DCCHs in a Sector

2.3.3.2 Paging Load

A call processing (CP) paging load of 108,000 pages/hour or 30 pages/secondcan only be reached if multiple MSCs running at high capacity are networkedtogether using directed/flood or flood/flood paging schemes. With these schemes,pages are flooded to neighboring (networked) MSCs on the second attempt (inthe case of directed/flood), or on both attempts (in the case of flood/flood).

For a single (non-network) MSC using flood paging within its area, up to twopaging attempts per call termination, and a BHCA rate of 108,000, the CP pagingload is approximately 54,000 pages/hour or 15 pages/second (based on the calldisposition statistics in Table 2-1). This volume represents only half the CP pagingload capacity of an AUTOPLEX system; the remaining capacity is available forSMS. Figure 2-4. shows the SMS capacity, assuming 100% IS-136 mobile marketpenetration (all CP-related traffic is carried on a DCCH). A single DCCH can carry10,000 SPACH notifications and 400 SMS messages per hour.

2 DCCH / sector

0

2000

4000

6000

8000

10000

12000

14000

16000

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9 1

IS-136 mobile penetration

SMS

mes

sage

s / h

r

SPACH notif / hour = 10000




2-16 401-200-112, Issue 11 June 2001



Figure 2-4. DCCH SMS Capacity with a Paging Load of 15 Pages/Seconds

In summary, these results illustrate how CP paging capacity can be traded off foradditional SMS capacity. Reducing flood paging across neighboring MSCs hasadvantages and potential disadvantages:

■ Reduced SPACH capacity used by CP paging (advantage)

■ Increased SMS capacity (advantage)

■ Reduced success rate of mobile-terminated calls; however the impact isslight compared to the increase in SMS traffic carried on the DCCH.(disadvantage)

The impact on mobile-terminated calls resulting from eliminating or reducingdirected/flood and flood/flood paging is likely to decrease with IS-136 compared toAMPS because of the improved autonomous registration capabilities provided onthe DCCH. These capabilities are standard with DCCH, and, unlike with AMPS,are supported at the time of initial IS-136 deployment.

15 pages / sec

-1000

0

1000

2000

3000

4000

5000

6000

7000

8000

5000

1000

0

2000

0

3000

0

4000

0

5000

0

6000

0

7000

0

8000

0

SPACH notifications / hr

SMS

mes

sage

/ hr

1 DCCH / sector

2 DCCHs / sector

401-200-112, Issue 11 June 2001 2-17



2.3.4 Reverse DCCH Capacity Evaluation

The Reverse DCCH consists of one logical channel, the Reverse Access Channel(RACH). The RACH is used to request access to the system and to respond tomessages sent by the cell site.

In every TDMA block or frame, there are a number of time slots, one of which isused for the RACH. For full-rate TDMA, the RACH consists of six subchannels.Subchanneling is used on the RACH to allow multiple accesses to proceedconcurrently. When a mobile gains access to the RACH and has more than oneslot worth of data to transmit, it uses every sixth RACH slot (i.e., one of the sixsubchannels) to send a burst of data.

Since many mobiles can be vying for RACH access at any one time, the IS-136standard provides for collision handling and contention resolution using a protocolsimilar to the slotted ALOHA protocol, adapted for IS-136.

The RACH is used in conjunction with the Shared Channel Feedback (SCF)channel. Access is controlled and message transmission is validated byinformation provided to the mobile on the SCF. The mobile monitors the SCFchannel for appropriate indications for the various tasks (request for access,response to messages). Possible indications on the SCF are:

■ Received/Not Received Indication—The cell site received/did not receivemessage transmitted on the RACH.

■ Busy/Reserved/Idle Indication

■ The Busy indication is set to allow subsequent slots in a multi-slotaccess to be sent free of contention. This is an indication to othermobiles attempting to access the RACH that this particularsubchannel is busy or not available.

■ The Reserved indication is used by the cell site to allow the mobileto initiate a transmission in contention free mode.

■ Partial Echo Field—Allows mobiles involved in a collision to verify that theirtransmission was received at the cell site.

If the mobile cannot transmit because of data contention or data collision at thecell site, or if too many Busy/Reserved indications are encountered, the mobilebacks off and retries. The maximum number of retries allowed is a RC/Vtranslation that is broadcast on the forward control channel as part of theoverhead information. When the Maximum Retries translation is set to:

■ 1, the mobile waits a random number of time frames (fewer than 20), andthen retries.

2-18 401-200-112, Issue 11 June 2001



■ Greater than 1, the backoff interval is a randomly distributed number ofslots up to six slots after the first failed attempt, and up to 20 slots aftersubsequent attempts.

Only the first burst in a multi-slot access is sent in random access fashion, somulti-slot accesses make more efficient use of RACH bandwidth. Most RACHmessages such as registrations, originations and page responses typically requiretwo slots; however, Automatic Radio Request (ARQ) acknowledgments requireonly one slot.

For the CP traffic requirements assumed in Section 2.2.1.2, 108,000 pages/hourand 50% IS-136 market penetration, the RACH load is about 7 messages persecond. Approximately 24% of the messages are single-slot and the rest are two-slot messages. For that mix, the maximum throughput of the RACH isapproximately 14 messages per second (not accounting for capture); hence theoffered load is about 50% of the maximum channel throughput.

2.4 Digital Traffic Channel (DTC) RFPlanning

This section provides recommendations for Digital Traffic Channel (DTC)frequency planning. These recommendations are based on an RF performancestudy conducted in a laboratory environment. For information about the reportdocument, refer to Paragraph 2.5.

Major topics include:

■ Co-Channel Reuse Factor (K) Assignment

■ TDMA Adjacent and Alternate Channel Assignment

In addition, recommendations, based on field experience, are provided for:

■ Analog/TDMA Channel Segmentation

■ Trunk Assignment Tradeoffs

2.4.1 Co-Channel Reuse Factor (K)Assignment

The spectrum available for mobile communications is limited. Frequencies in cellsspaced a certain distance apart are reused to increase system call handlingcapacity. This can result in co-channel interference between those cells using thesame frequencies.

401-200-112, Issue 11 June 2001 2-19



2.4.1.1 Co-Channel Reuse Factor Tradeoffs

The amount of co-channel interference is a function of the frequency reuse factor,K. There are tradeoffs to consider in selecting the distance between co-channelcells:

■ The longer the distance between co-channel cells (i.e., the greater thereuse factor, K), the lower the co-channel interference. The tradeoff forlonger distance is lower system channel capacity.

■ The shorter the distance between co-channel cells (i.e., the smaller thereuse factor K), the higher the system channel capacity. The tradeoff forshorter distance is higher system co-channel interference. Higher co-channel interference can lead to poorer voice quality on the DTC and,possibly, poorer call completion performance on the DCCH.

The channel capacity vs. voice quality tradeoff means that evaluation of the reusefactor, K, is based on market strategy.

2.4.1.2 K Selection Process

The referenced study led to a significant conclusion: Voice quality on the DTCgenerally begins to degrade at a higher C/I than that at which call completionperformance for the DCCH begins to degrade. This means that the level of Kneeded to provide the desired voice quality on the DTC will generally be higherthan the level of K needed to provide the desired call completion performance onthe DCCH. Thus, the choice of K should be made based on providing the desiredvoice quality on the DTC, consistent with your market strategy.

The following steps will help determine the factor K to use:

1. Determine a BER that provides the desired voice quality. Typically, BERsbelow 1% provide good voice quality while BERs above 3% provide poorvoice quality.

2. Determine the propagation path loss slope (m) for the particular environ-ment in which the system is located. Urban and suburban areas generallyexhibit larger path loss slopes than do rural areas. The path loss slope canbe determined from coverage data by analyzing the signal strength vs. thedistance relationship.

3. Select the level of K that provides the most channel capacity, while stillyielding the desired voice quality, from Figure 2-3. The numbers inFigure 2-3 assume the use of three-sector cells and a 4dB diversity gain onthe uplink receive path. These numbers were derived by link budget analy-sis. (See Appendix C for an example of a link budget analysis.)

2-20 401-200-112, Issue 11 June 2001



.

2.4.1.3 Evaluating the Results

To ensure that the system is engineered properly to the chosen frequency reusepattern K, consult the tables below. Table 2-3 and Table 2-4 indicate the averagecarrier to total interference ratio (referred to as C/Ico in Appendix C) expected forthe indicated reuse factor K with the indicated path loss slope m for both three-sector and omni antenna configurations, respectively. The average C/Ico can bemeasured in the system using PLM 1 and PLM 2 reports. The measured C/Icoshould be comparable to the expected C/Ico indicated in Table 2-3 or Table 2-4.

If the measured C/Ico is smaller than the expected C/Ico indicated by Table 2-3 orTable 2-4, then:

■ either the path loss slope m is smaller than estimated (in which case agreater K may be necessary to obtain the desired voice quality), or

■ there may be some cells located closer than the required frequency reusedistance for the chosen reuse factor K.

Table 2-3 Recommended Frequency Reuse (K) for Obtaining the Indicated BER

m dB/Decade

BER 32.5 35.0 37.5 40.0

1% 12 9 7 7

2% 7 7 7 7

3% 7 7 7 7

401-200-112, Issue 11 June 2001 2-21



In summary:

1. Set BER performance goal for DTC.

2. Determine path loss slope (m) for particular cell site environment.

3. Based on choice of BER from Step 1 and path loss slope from Step 2,choose K indicated by Figure 2-3.

4. Verify that average C/Ico, based on PLM 1 and PLM 2 measurements madein the system, is comparable to expected C/Ico given in Figure 2-4 orFigure 2-5.

5. If measured C/Ico is smaller than expected C/Ico given in Table 2-3 orTable 2-4, it may be necessary to use a larger K than that chosen in Step 3.

Table 2-4 C/Ico for Three-Sector Cells

Propagation Path-loss Slope m(dB/decade)

Carrier/Co-Channel Interference Ratio (C/ICO) in dB

at Indicated Frequency Reuse Factor (K)

3 4 7 9 12

32.5 13.73 15.63. 19.36 21.05 22.99

35.0 15.00 17.05 21.08 22.89 24.98

37.5 16.26 18.47 22.79 24.74 26.98

40.0 17.52 19.88 24.50 26.58 28.97

Table 2-5 C/Ico for Omni Cells

Propagation Path-loss Slope m(dB/decade)

Carrier/Co-Channel Interference Ratio (C/ICO) in dB

at Indicated Frequency Reuse Factor (K)

12 13 16 19 21

32.5 14.94 15.61 17.34 18.75 19.56

35.0 16.68 17.41 19.27 20.76 21.66

37.5 18.43 19.21 21.20 22.83 23.76

40.0 20.18 21.01 23.14 24.87 25.81

2-22 401-200-112, Issue 11 June 2001



2.4.2 TDMA Adjacent and Alternate ChannelAssignment

Adjacent and alternate channel interference occur because the filtercharacteristics of each channel are less than ideal; some power associated witheach channel spills beyond its 30-kHz allocation. Though severely attenuated,each channel transmits some power in the adjacent (30-kHz away) and alternate(60-kHz away) channel spectrums. Similarly, each channel receives power fromadjacent and alternate channels.

To reduce adjacent and alternate channel interference, Lucent Technologiesrecommends the following guidelines for channel assignment for both DTC andDCCH:

■ Avoid use of adjacent and alternate channels in the same cell site.

■ Avoid use of adjacent channels in adjacent omni cells or adjacent sectors.

■ When adjacent channels are used in adjacent sectorized cells, assignadjacent channels to non-adjacent sectors.

2.4.3 Analog/TDMA Channel SegmentationGuidelines

Analog/TDMA channel segmentation is required to avoid adjacent channel andco-channel interference.

2.4.3.1 Analog/TDMA Adjacent ChannelInterference

TDMA digital traffic channels and analog voice channels have different frequencyspectral content as shown in the Spectrum Analyzer Plot, Comparison of TDMAand Analog Channels, Figure 2-5. below. The transmitted spectrum of the TDMAchannel, at left, is much wider than the typical spectrum of an analog FM channel,at right. As a result of these frequency spectral characteristics, interference mayoccur on adjacent channels using a different technology.

A TDMA channel is not severely affected by an adjacent analog channel;however, an analog channel is greatly affected by an adjacent TDMA channel.

401-200-112, Issue 11 June 2001 2-23



Figure 2-5. Comparison of TDMA and Analog Channels

Lucent Technologies recommends the following strategies for minimizing adjacentchannel interference between differing technologies:

■ Use at least one guard band channel to separate the set of frequenciesused for analog from the set of frequencies used for TDMA.

■ Assign the digital channels to a contiguous block, preferably at the edge ofthe normal channel spectrum or the edge of the expanded channelspectrum, so that only one side needs guard band channel protection. Oneguard band channel is sufficient, because the effect of a TDMA channel onan alternate (60-kHz away) analog channel, and vice versa, is negligible.

2.4.3.2 Analog/TDMA Co-ChannelInterference

Degraded performance may also occur when TDMA and analog radios share thesame frequencies. Lucent Technologies recommends use of a separate set offrequencies for TDMA, isolated from the analog channels.

2-24 401-200-112, Issue 11 June 2001



2.4.4 Trunk Assignment

Manage the trunk assignments for the DTC so that a minimum number of RFchannels are transmitting at the same time. To minimize RF interference in thesystem, use the following guidelines:

■ Assign sequential trunks to fill the three time slots on one TDMA RFchannel before using the next DRU.

■ Choose the sequential trunk hunt option (not the least used option) for DTCchannel assignment.

■ When DCCH is deployed, use sequential trunk hunt and place the secondand third time slots of the DCCH radio first and second on the sequentialhunt list.

■ Avoid assigning trunks or RF channels that are being used by DCCH atother cells.

2.5 RF Performance Study

The study mentioned previously was conducted in the laboratory using fadingsimulators to emulate over-the-air impairments. Tests included:

■ receiver sensitivity

■ co-channel and adjacent channel interference

■ loaded channel

■ call completion, under co-channel interference impairments for DCCH

The tests concentrated on the Bit-Error Rate (BER) and Frame-Error Rate (FER)performance for both a Digital Traffic Channel (DTC) and a Digital ControlChannel (DCCH) using a Digital Radio Unit (DRU). The tests demonstrate typical,not necessarily worst case RF performance capability of DRUs. They wereperformed using a single DRU, at one frequency, at room temperature, with alimited number of pre-production IS-136 mobiles.

2.5.1 Proprietary Statement

Because of the proprietary nature of the data collected in the RF performancestudy, the results are not included in this document. These results are contained inthe document, 6.0 Performance Study.

401-200-112, Issue 11 June 2001 2-25



2.5.2 To Obtain Document

To obtain a copy of the 6.0 Performance Study, contact your Lucent TechnologiesAccount Executive.

2.6 RF Channel Assignment forMixed ACC/DCCH Systems

If both DCCH and ACC are supported in the same network, follow the channelassignment rules below:

■ Choose RF channel from the range of 1 to 1023, as specified in EIA/TIA-553.

■ Do not choose RF channels 313 to 354, which are assigned for A- and B-band ACCs, for DCCH use if these channels are used for the ACCs in theserving area.

■ Consult the IS-136 standard, which specifies the recommended probabilityblocks that prioritize the mobile frequency search process.

2.7 Flexible Channel Allocation(FLCA) Features

Two fundamental benefits are realized from the deployment of the FLCA feature.The primary benefit is dynamic channel allocation providing RF spectrumresources when and where needed to increase capacity. The second benefit isthe ability to improve voice quality by selecting from a pool of channels having thelowest levels of interference to service calls.

FLCA is introduced in two features: FLCA-LM and FLCA-DA. The first feature,FLCA List Monitoring (FLCA-LM), which is available in Release R14.0, allows foroff-line data gathering experience to prepare for the full deployment of FLCAwhen FLCA Dynamic Allocation (FLCA-DA) becomes available in Release R15.0.FLCA-LM must be activated before FLCA-DA is enabled. The combination ofFLCA-LM and FLCA-DA is simply referred to as FLCA. The following text willaddress both FLCA features.

FLCA provides an alternative to Fixed Channel Allocation (FCA) by permittingdynamic allocation of RF channels to EDRU radios as the traffic need foradditional RF channels arises at specific cell sites. In FCA, a fixed number of RFchannels are allocated to each cell and sector where specific RF channelfrequencies are assigned to each radio. Channel interference in an FCA system iskept to an acceptable level by assigning neighboring RF channels to different cellsand sectors distributed over large distances, forming clusters as shown in

2-26 401-200-112, Issue 11 June 2001



Figure 2-6. As traffic increases, through increased usage or demographic change,the increase in call capacity is often handled through cell splitting where one ortwo cells are replaced by a larger number of smaller cells. Doing this increasesthe number of usable RF channels in a given geographical area. The addition ofsmaller cells in an FCA system requires reallocation of RF channels, involving theRF engineering burden of assigning RF channels to the new (growth) cells andreassigning RF channels to those radios surrounding cells, to maintain anacceptable level of interference.

The FLCA feature reduces the RF engineering burden of assigning RF channelsto specific EDRU radios that is traditionally required when new radios are addedto a cell, or new cells are added to the network. In addition, FLCA increasessystem capacity by dynamically allocating spectrum resources when and whereneeded for either call setup or handoff. For example, during weekday rush hours,call traffic is heavier along highway corridors leading to or from industrial worksites than at the work sites or residential areas. Rather than having some callsalong the highway corridors blocked due to insufficient spectrum resources whileRF channels assigned to other areas are idle, the FLCA feature creates a pool ofRF channels, broadening the cell RF resources. Channels within the FLCA poolare grouped within channel sets. Each provisioned channel set, which may sharechannels in common with other channel sets, may be assigned to a number ofsectors within the ECP service area. Channels from the channel sets can be usedin any of their assigned sectors throughout the system when needed as allowedby interference conditions. Thus, during routine weekday rush hours, the cells/sectors along the highway corridors draw RF channels from their assignedchannel sets as needed. The FLCA feature can also improve call throughput atevents less routine than weekday rush hour. For example, the pool of channelsmay go to the cells in and around a stadium during a major sporting event. Afterthe game, the channel pool usage is then disbursed along the highways leadingfrom the stadium. The channel pool usage then follows the major traffic flow fromthe stadium to cells in the residential areas.

401-200-112, Issue 11 June 2001 2-27



Figure 2-6 Cell Cluster Array for Reuse Factor of 7

2.7.1 FLCA Planning and Implementation

A separate dedicated FLCA Planning and Implementation Guide (401-200-120)has been prepared to provide detailed engineering guidelines for deploying FLCA.This dedicated manual, which contains RF engineering, planning, andimplementation information, should be used when initially deploying FLCA. Inaddition to helping you to optimize performance, the referred manual will presenta detailed description of FLCA with reference to its translation parameters andoutput service measurements.

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

f1

ff8

15f7

f14

f21

f6f20

f19f12

f5

f11

f4f18

f10

f13

f3

f9

f2

f17

f16

2-28 401-200-112, Issue 11 June 2001



2.8 TDMA DiscontinuousTransmission with ComfortNoise Insertion (DTX/CNI)

The TDMA Discontinuous Transmission (DTX) with Comfort Noise Insertion (CNI)feature provided in ECP and cell site release R14.0 permits TIA/EIA-136Acompatible mobile subscribers and subscribers with TDX/CNI modified IS-136Amobiles to increase battery life by as much as 30 percent. The increase in batterylife is achieved by either curtailing or completely eliminating the mobile time slottransmission during the period when the subscriber is not speaking. Although TIA/EIA-136A standards allow transmission curtailment with and without truncatedburst, Lucent supports DTX/CNI with truncated burst only. Because the mobile istransmitting during a portion of the time slot period, the RF co-channelinterference level is reduced at neighboring cells by as much as 30 percent. Thisreduction permits both DTX/CNI capable and non-DTX/CNI capable mobiles tooperate at lower power levels to further enhance battery life and increase batterytalk time. Mobiles qualifying for DTX/CNI operation must have their Station ClassMark field for discontinuous transmission set to yes.

2.8.1 Voice Activity Detection (VAD)Algorithm

DTX/CNI compatible mobiles use a Voice Activity Detection (VAD) algorithm,which detects when a voice input is not present, and determines when mobiletransmission is to be truncated. As a result, the mobile transmitter is turned offexcept for a small portion of its assigned TDMA time slot period. During this shortperiod, a truncated uplink burst is transmitted to convey signaling information andto maintain an RF link with the cell site. The truncated transmit burst causes a lossof the mobile background noise, that provides the mobile call recipient assurancethat the call connection is not broken. To maintain this assurance during DTX/CNIcalls, a comfort noise is inserted at the MSC switch to provide the mobile callrecipient sufficient background noise assuring the caller that the connection ismaintained.

2.8.1.1 DTX/CNI Activation Restrictions

DTX/CNI is a cell-based QFAF (optional) feature and activated at each cell andcell face by setting the RC/V translatable parameters (switches) as indicated inTable 2-6. Cell and sector activation is implemented by setting parameters on thecell2 and fci forms, respectively. The Allow TDMA DTX/CNI for IS-136 RevAMobile on the ecp form permits the service provider to separately enable anddisable DTX/CNI feature throughout the ECP domain for non-standard modifiedIS-136A mobiles only. The subscriber’s mobile capability are entered on thesubscriber and feature information sub and soda forms, and the visitor location

401-200-112, Issue 11 June 2001 2-29



registration (vlr) form as indicated in the Feature Implementation section of thismanual. In addition, implementation of the DTX/CNI feature requires an EDRUradio operating with a switch-based TDMA vocoder. The switch-based TDMAvocoder, introduced in release R12.0, relocates the ACELP vocoder function fromthe EDRU to the switch at the MSC. In addition, the MSC 5E switch must bebrought up to Release 13.0.

Another requirement is that the TDMA access mode is full rate. Full rate refers toa time slot assignment scheme in which pairs of time slots are used to supportcommunications in both the uplink and downlink directions. In this scheme,transmission of the three voice/control data channels is interlaced so that the firstvoice (or control data) channel is transferred during the first and fourth time slotsof the frame, the second channel during the second and fifth time slots, and thethird channel during the third and sixth time slots.

Table 2-6 RC/V Translatable Parameter Settings for DTX/CNI

Form/Name Range Default Description

ecp / AllowTDMA DTX CNIfor IS-136 Rev AMobiles

y/n y Permits the service provider to separatelyenable and disable DTX/CNI feature fornon-standard modified IS-136A mobilesonly. When set to n, this parameter inhibitsthe DTX/CNI feature on modified IS-136Amobiles throughout ECP domain.

cell2 / TDMADTX CNI

y/n n Activates the DTX/CNI feature in the cell.When a y value is entered, the softwarechecks that the system is in compliancewith the activation restrictions. Softwarealso checks the QFAF entry for this featureto determine if feature is permitted and thenumber of cells implementing feature is notexceeded, in accordance with purchaseagreement. If any of the restrictions areviolated, an appropriate warning is dis-played. All underlying fci forms have to beturned off before cell2 can be deactivatedfor this feature.

2-30 401-200-112, Issue 11 June 2001



2.8.1.2 Other Restrictions

Although there are no locate radio restrictions for a serving cell on call originationand termination, there are locate radio restrictions for call handoff. Because of thenature of DVCC Verification with RSSI, mobile saturation resolution, and hybrid/MAHO digital locate features inherent to digital locate, the locate radio in therecipient handoff cell must be aware that the mobile is transmitting DTX/CNItruncated bursts. Without being informed of the mobile transmission mode, thelocate radio in the candidate cell assumes full transmission mode and may rejectthe handoff in error due to insufficient measured signal strength. Therefore, themobile transmission mode information must be passed on to the locate radio.Only the Release 14.0 L-EDRU locate radio is capable of receiving and

fci / TDMA DTXwith ComfortNoise InsertionActive

y/n n Activates the DTX/CNI feature for a givensector. When a y value is entered, the soft-ware checks that the DTX/CNI feature isactivated on its associated cell. The soft-ware also checks for inter-vendor neigh-bors on the sector MAHO neighbor. If thesector has inter-vendor neighbors, furtherrestrictions prohibit simultaneous activationof the DTX/CNI feature with the L-EDRUdigital locate feature. If these restrictionsare violated, an appropriate error notationis displayed.

soda / MobileProtocol Capa-bility Ind

553, 54B,95, 136,136A,T136A

553 Indicates the subscriber’s mobile capabil-ity on the subscriber and feature informa-tion (soda) form. When set to T136A,indicates that the subscriber’s mobile isTIA/EIA-136A compatible.

sub/ Mobile Pro-tocol CapabilityInd

553, 54B,95, 136,136A,T136A

553 Indicates the subscriber’s mobile capabil-ity on the subscriber and feature informa-tion (sub) form. When set to T136A,indicates that the subscriber’s mobile isTIA/EIA-136A compatible.

vlr/ Mobile Proto-col Capability Ind

553, 54B,95, 136,136A,T136A

553 Indicates the subscriber’s mobile capabil-ity on visitor location register. When set toT136, indicates that the subscriber’smobile is TIA/EIA-136A compatible andsuitable for DTX operation.

Table 2-6 RC/V Translatable Parameter Settings for DTX/CNI —Continued

Form/Name Range Default Description

401-200-112, Issue 11 June 2001 2-31



interpreting this information. L-DRU locate radio may originate a DTX/CNI call;however, because the L-DRU cannot identify the mobile transmit mode onhandoff, the cell cannot receive a DTX/CNI call handoff.

Although the DTX/CNI feature is compatible with Release R14.0 L-EDRU radios,there are limitations regarding locate measurements at handoff across ECP andinter-vendor border cells. Lucent is currently applying for provisions in the IS-41standard allowing the passage mobile transmit mode information from one serviceprovider to another. However, at this time, there aren’t any such provisions. In theinterim, the net RC/V form has been modified to identify the DTX/CNI complianceof the ECP. Prior to considering handoff across the ECP border, the net form ofthe handoff candidate cell ECP is checked for DTX/CNI compliance. If the ECP isnot in compliance with DTX/CNI, the ECP for the serving cell will not issue aDigital Locate Request Message to the handoff candidate cell. Thus, the handoffcandidate cell will not perform a digital locate and handoff is based on MAHOalone.

If the DTX/CNI feature is activated without complying with its restriction, amessage appears on the RC/V screen identifying the violated restriction.

2.8.2 DTX/CNI Service Measurements

The number of DTX/CNI mode calls on a single LAF is recorded in the Number ofDTX Mode Calls (LAF-TDMA field 53) service measurement count. This count,which enables the service provider to calculate the percentage of DTX/CNI modecalls handled through the LAF, is incremented either on a call setup or call handoffinto the LAF. Because the count is incremented at handoff, a single call leavingand re-entering a sector in counted more once. Although at feature start up, thisservice measurement count will be low, the expected count will increase as thepenetration of DTX/CNI capable mobile increases. The percent of DTX/CNI modeusage is calculated by dividing this count by the total number of call setups andcall handoffs established at the LAF and multiplying the quotient by 100%. If theservice measurement is zero with a substantial number of DTX/CNI capablemobile penetration, check that the feature software is loaded and that the featureis turned on.

2.8.3 Feature Implementation

Implementation of the DTX/CNI feature requires modification of the followingrecent change/verify (RC/V) forms:

■ Executive Cellular Processor (ecp)

■ Series 2 Cell (cell2)

■ Face Code Information (fci)

■ Cellular Network (net)

2-32 401-200-112, Issue 11 June 2001



■ Subscriber and Feature Information (sub and soda)

■ Visitor Registration Information (vlr)

2.8.3.1 Executive Cellular Processor (ecp) Form

The ecp form screen allows the DTX/CNI feature to be enabled throughout theECP domain by inserting a y in the Allow TDMA DTX/CNI for IS RevA Mobile field.This parameter controls the DTX/CNI feature activation on modified IS-136Amobiles that supports DTX/CNI with truncation burst only.

2.8.3.2 Series 2 Cell (cell2) Form

The DTX/CNI feature is activated at a cell when a y value is entered in the TDMADTX CNI field in the Cell Site Optional Features section of the cell2 form. Whenthe y is entered, the software checks that the system is in compliance with theactivation restrictions. Software also checks the QFAF entry for this feature todetermine if the feature is permitted and the number of cells implementing featureis not exceeded, in accordance with purchase agreement. If any of the restrictionsare violated, an appropriate warning is displayed. All underlying fci forms have tobe turned off before cell2 can be deactivated for this feature.

2.8.3.3 Face Code Information (fci) Form

To activate the DTX/CNI feature on a given sector face, a y must be entered in theTDMA DTX with Comfort Noise Insertion Active field in the Series 2 Cell TDMAOnly Information section of the fci form. When a y value is entered, the softwarechecks that the DTX/CNI feature is activated on its associated cell. The softwarealso checks for inter-vendor neighbors on the sector MAHO neighbor. If the sectorhas inter-vendor neighbors, further restrictions prohibit simultaneous activation ofthe DTX/CNI feature with the L-EDRU digital locate feature. If these restrictionsare violated, an appropriate error message is displayed.

2.8.3.4 Cellular Network (net) Form

The net form is modified for this feature to identify that an ECP is capable ofhandling DTX/CNI. When a DTX/CNI call handoff across an ECP border isconsidered, the serving ECP checks its neighbor’s net form to determine if theECP is capable of handling DTX/CNI. If the neighboring ECP is not capable ofhandling DTX/CNI, the digital locate request message, normally sent to handoffcandidate cell, in suppressed. This prevent the handoff candidate cell fromperforming digital locate that will produce an erroneous result because the handoffcandidate cell would assume that the subject mobile is transmitting over the fulltime slot period. In this situation, handoff is based on MAHO alone.

401-200-112, Issue 11 June 2001 2-33



2.8.3.5 Subscriber and feature Information(sub and soda) Form

The subscriber and feature information (sub and soda) forms are used to indicatethe subscriber’s mobile capability. When set to T136, the Mobile ProtocolCapability Ind field indicates that the subscriber’s mobile is TIA/EIA-136Acompatible. Because DTX/CNI applies to TIA/EIA-136A compatible mobile andDTX/CNI modified IS-136A mobiles, this feature is applicable only to thosesubscribers that have T136A or 136A indicated in this field.

2.8.3.6 Visitor Registration Information (vlr)Form

The Mobile Protocol Capability Ind field on the vlr form indicates the subscriber’smobile capability on the visitor location register. Because DTX/CNI applies to TIA/EIA-136A compatible and DTX/CNI modified IS-136A mobiles, this feature isapplicable only to those subscribers that have T136A or 136A indicated in thisfield.

2.9 Digital Control Channel (DCCH)RF Planning

This section provides guidelines for DCCH channel assignments. The objective isto minimize co-DCCH interference.

Digital Control Channel (DCCH) radios transmit continuously over three timeslots.Because the DCCHs are always on, they create more interference than channelsassigned as Digital Traffic Channels, which are in use intermittently.

2.9.1 Recommended DCCH ChannelAssignments

Channel assignment schemes for DTCs are based on the assumption that at anygiven time, a random number of co-channel DTCs are not transmitting. Thismeans that only some DTCs create co-channel interference at any given time. Bycontrast, DCCH channels transmit constantly, generating worst-case interferenceand impinging on their co-DCCH neighbors. This means that channel assignmentschemes for DTC and DCCH must consider different reuse factors.

To minimize the impact of co-DCCH interference, Lucent Technologiesrecommends spacing DCCH co-channels farther apart than is necessary for DTCco-channels. The approach selected to accomplish this depends on the DCCHinterference requirements (business strategy) and the number of TDMA radios

2-34 401-200-112, Issue 11 June 2001



available in each sector. This section presents recommendations for assigningDCCHs to minimize co-DCCH interference.

■ Choose two TDMA radios (channels) from each channel group for DCCHuse.

■ Assign one of the TDMA radios to each co-channel sector in a first tier line-up fashion, as shown in Figure 2-8.. This effectively doubles the reusedistance between the two DCCHs.

■ Use sequential trunk hunt and place the second and third time slots of theDCCH radio first and second on the sequential hunt list. Voice channelsassigned to the second and third time slots of a DCCH radio will notintroduce additional interference, since no additional RF carriers are beingintroduced to the environment.

■ Avoid assigning trunks or RF channels that are being used by the DCCH atother cells.

2.9.2 Two-DCCH Radio Deployment Scheme

With properly designed sectorized cells and antenna radiation patterns, co-channel interference from DCCHs within a given line-up group is negligiblecompared with that from co-channel DCCHs in adjacent line-up groups. Hence,the use of the second DCCH at the co-channel neighbor.

In this configuration, major co-channel interference on the home DCCH comesfrom the four nearest co-DCCH sectors. These neighbor interfering sectors areseparated from the home DCCH sector by 2D, D, 2D and D. D representsthe distance between two adjacent co-channel cell sites.

The worst case carrier to total co-DCCH interference ratio (C/Ico-DCCH) caused bythese four interfering co-DCCHs is expressed as:

(EQ 1)

For K = 7, D is 4.58 R. The loss slope factor (m) may range from 2 to 5, dependingupon environmental conditions. EQ.1 can also be expressed as:

where R = cell radius

D =

K = frequency reuse pattern

m = propagation path-loss slope

3 7

C I⁄ co DCCH– worstcase( ) R m–

2D R+( ) m– 3D 0.7R+( ) m–2D( ) m– 7D( ) m–

+ + +----------------------------------------------------------------------------------------------------------------------------------=

3KR

401-200-112, Issue 11 June 2001 2-35



(EQ 2)

where q = D/R = 4.58

q is the co-channel interference reduction factor.

By comparison, the equation for the worst case carrier to total co-DTC interference(C/Ico-DTC) for three-sectored cells using K = 7 is:

(EQ 3)

EQ. 1 shows that each DTC receives co-channel interference from two adjacentco-DTCs, located at distance D + 0.7R and R.

EQ. 2 and EQ. 3, the worst case C/Ico-DCCH and C/Ico-DTC for propagation path-loss slopes (m), are illustrated in Figure 2-7.. For this configuration, C/Ico-DCCH ishigher than C/Ico-DTC by 5.84 dB when m = 3, and by 8.86 dB when m = 4. Thus,deploying DCCH in the recommended configuration will yield a higher carrier toco-channel interference ratio relative to the normal DTC reuse configuration.

C I⁄ co DCCH– worstcase( ) 1

2q 1+( ) m– 3q 0.7R+( ) m–2q( ) m– 7q( ) m–

+ + +--------------------------------------------------------------------------------------------------------------------------=

C I⁄ co DTC– worstcase( ) 1

q 0.7+( ) m– q m–+------------------------------------------=

2-36 401-200-112, Issue 11 June 2001



Figure 2-7. Comparison of C/Ico-DTC and C/Ico-DCCH During Off-Peak Hours

Figure 2-8. and Figure 2-9. below show the DCCH layout in a system using twoDCCHs, three-sectored cells and a frequency reuse factor (K) of seven.

■ Figure 2-8. shows two distinct DCCHs, DCCH#1 and DCCH#2, assigned intwo first tier line-up groups, DCCH#1-Group and DCCH#2-Group. Thegroups using the same DCCH radio (DCCH#1-Groups, for example) areseparated from each other by the group using the other DCCH radio,DCCH#2-Group.

■ Figure 2-9. shows this DCCH assignment scheme and general line-uppattern, repeated over all co-channel sectors in the network.

0

5

10

15

20

25

30

35

20.0 22.5 25.0 27.5 30.0 32.5 35.0 37.5 40.0

Propagation Path-Loss Slope (dB/decade)

C/I c

o(d

B)

C / I co -DCCH

C / I co -DTC

401-200-112, Issue 11 June 2001 2-37



Figure 2-8. DCCH Assignment Using Two Distinct TDMA Radios for DCCHs,First Tier Line-Up Pattern

DCCHDCCHDCCHDCCH#1#1#1#1







2-38 401-200-112, Issue 11 June 2001



Figure 2-9. DCCH Assignment Using Two TDMA Radios for DCCHs, GeneralLine-up Pattern

#1

#1

#1

#1

#1

#1

#1

#1

#1

#1

#1

#1

#2

#2

#2

#2

#2

#2

#2

#2

#2

#2

#2

#2

401-200-112, Issue 11 June 2001 2-39



2.9.3 Generalized Deployment Scheme

The DCCH assignment scheme explained above is used for a system with twoDCCH radios in each sector. This assignment scheme can be generalized byincreasing the number of distinct TDMA radios for DCCHs in co-DCCH cells toachieve a higher C/Ico-DCCH.

The layout of DCCH assignment for a system using three distinct TDMA radios forDCCHs in co-DCCH cells is illustrated in Figure 2-10.. The line-up co-DCCHgroups using the same DCCH radio (DCCH#1-Group) are separated from eachother by the two line-up groups using different DCCH radios (DCCH#2-Group andDCCH#3-Group).

2-40 401-200-112, Issue 11 June 2001



Figure 2-10. DCCH Assignment Using Three Distinct TDMA Radios for DCCHs

#3

#3

#3

#1

#1

#1

#1

#1

#2

#2

#2

#2

#2

#3

#2

#2

#2

#1

#3

#3

#3

#1

#3

#1

401-200-112, Issue 11 June 2001 2-41



2.9.4 Channel Assignment Examples

The following tables show how to lay out DCCHs in the first tier for a system usingthree-sectored cells and frequency reuse pattern of seven. Figure 2-7 andFigure 2-8 list the possible A Band and B-Band DCCH assignments for 21channel groups. Figure 2-11. and Figure 2-12. show the DCCH channel plans laidout for A-Band and B-Band systems.

The DCCH channel assignment scheme given above does not require frequencyreplanning on any frequency reuse pattern (e.g., K = 7) for DTCs.

In conclusion, Lucent Technologies recommends using a channel assignmentscheme for DCCHs that minimizes interference from co-channels. The scheme

Table 2-7 Example of A Band DCCH Assignment for Three-Sector and K = 7

Sector 1A 2A 3A 4A 5A 6A 7A

DCCH #1 1 2 3 4 5 6 7

DCCH #2 22 23 24 25 26 27 28

Sector 1B 2B 3B 4B 5B 6B 7B

DCCH #1 8 9 10 1 1 1 2 1 3 1 4

DCCH #2 29 30 31 32 33 34 35

Sector 1C 2C 3C 4C 5C 6C 7C

DCCH #1 15 16 17 18 19 20 21

DCCH #2 36 37 38 39 40 41 42

Table 2-8 Example of B Band DCCH Assignment for Three-Sector and K = 7

Sector 1A 2A 3A 4A 5A 6A 7A

DCCH #1 607 608 609 610 611 612 613

DCCH #2 628 629 630 631 632 633 634

Sector 1B 2B 3B 4B 5B 6B 7B

DCCH #1 614 615 616 617 618 619 620

DCCH #2 635 636 637 638 639 640 641

Sector 1C 2C 3C 4C 5C 6C 7C

DCCH #1 621 622 623 624 625 626 627

DCCH #2 642 643 644 645 646 647 648

2-42 401-200-112, Issue 11 June 2001



presented does not eliminate interference, but reduces it relative to the nominalco-channel interference level associated with the normal DTC reuse distance.

The relatively low channel activity factor for DTCs (30% on average), producesless interference than that produced by DCCHs transmitting full time.Nevertheless, Lucent Technologies recommends giving low priority in the channelassignment algorithm to DTCs representing the nearest co-channel interferers toa DCCH. One way of accomplishing this is to put these DTCs at the end of thesequential trunk hunt list. This reduces interference to the DCCH, and reduces thelikelihood that the system assigns DTCs identified as being subject to co-channelinterference from a DCCH.

During peak traffic hours when the system is nearly fully loaded, improvement willbe slight because of the high probability that a radio chosen for DCCH may beassigned for DTC use in the nearest DCCH co-channel cells. Despite that, theaverage interference will still be less using this frequency assignment plan forDCCH.

401-200-112, Issue 11 June 2001 2-43



Figure 2-11. Example of A-Band DCCH Assignment

30

30

31

23137

338

29

351

36

346

41

742 32

43933

540

2229

15

34

2027

1623

1724

3528

21 32

1825

2619

33

228

36

2337

9

2410

14 3828

4127

13

2612 39

251142

40

9

162

173

14

10

214

18

117

8

13

151

61220

195

2236

114228

8

1424

38

103723

9

2713

2640

12 3925

23

41

30

29 1622

15 2835

2133

27

20

34

1926

32

25

17

3124

36

291

187

35

37

302

424

39

3238

331

33

405

41

634

2-44 401-200-112, Issue 11 June 2001



Figure 2-12. Example of B-Band DCCH Assignment

636

636

637

608637643

609644

635

641607

642

640612

647

613648 638

610645639

611646

628635

621

640

626633

622629

623630

641634

627 638

624631

632625

639

628614

642

629643

615

630616

620 644634

647633

619

632618 645

631617648

646

615

622608

623609

620

616

627610

624

617613

614

619

621607

612618626

625611

628642

617648634

614

620630

644

616643629

615

633619

632646

618 645631

629

647

636

635 622628

621 634641

627639

633

626

640

625632

638

631

623

637630

642

635607

624613

641

643

636608

648610

645

638644

609637

639

646611

647

612640

401-200-112, Issue 11 June 2001 2-45



2.10 Alignment of DCCH Reselectionand DTC Handoff Boundaries

In certain DCCH deployment scenarios it may be necessary or desirable to alignDCCH reselection boundaries with traffic channel handoff boundaries. Oneexample is the deployment of the DCCH in a cellular office environment, wherecertain services are associated with an office building microcell that are notassociated with an outside macro cell. Under these conditions, a subscriber whoreceives service by accessing the microcell would expect to be initially served ona traffic channel associated with that cell, and not to be immediately handed off tothe outside public cell.

Within certain limitations and restrictions, Digital Traffic Channel (DTC) handoffboundaries can be made to closely approximate the DCCH reselectionboundaries. These handoffs rely on Mobile Assisted Handoff (MAHO) todetermine the signal strength of the serving cell, and of neighbor cells. Theboundaries are aligned by setting Translations associated with the MAHOalgorithm to correspond to similar translations in the DCCH reselection algorithm.Since the DCCH reselection algorithm executed by the mobile is a function of the“sector-type” (“Preferred,” “Regular” or “Non-Preferred”) associated with eachneighbor sector, the specification of some MAHO related translations will vary asa function of this designation. The following sections describe the reselectionalgorithm as a function of the sector type, and suggest translation settings foraligning handoff and reselection boundaries.

2.10.1 DCCH Sector-Types

For each DCCH equipped sector, each control channel neighbor is associatedwith a sector-type on the RESEL RC/V form. The sector-type may have the valuesof Preferred, Regular or Non-Preferred. The sector-type is broadcast to mobilescamped on the serving cell DCCH in the Neighbor Cell Message. Mobiles monitorthe neighbor control channels specified in this message for possible reselection toa “better” control channel. The algorithm that determines if and when a mobile willreselect is a function of the trigger condition for reselection, the sector-type, andother translations associated with that neighbor. For the most common triggerconditions (periodic scanning and signal strength triggers), the followingparagraphs provide high level descriptions of the control channel reselectionalgorithm executed by the mobile for the specified sector-type. (translationsshown in parentheses are IS-136 designations for the named translations.)

2-46 401-200-112, Issue 11 June 2001



2.10.1.1 Preferred Neighbors

The mobile considers a Preferred Neighbor control channel as a candidate forreselection when the signal strength of the neighbor exceeds the MobileReselection Threshold (SS_SUFF). The neighbor may also become a candidate ifit satisfies the Regular Neighbor criteria.

2.10.1.2 Regular Neighbors

The mobile considers a Regular Neighbor control channel as a candidate forreselection when the signal strength of the neighbor exceeds the Mobile AccessThreshold (RSS_ACC_MIN), and the neighbor signal strength exceeds theserving DCCH signal strength by negative Reselection Offset Bias(RESEL_OFFSET).

2.10.1.3 Non-Preferred Neighbors

The mobile considers Non-preferred Neighbor control channel as a candidate forreselection when the signal strength of the neighbor exceeds the Mobile AccessThreshold (RSS_ACC_MIN), the neighbor signal strength exceeds the servingDCCH signal strength by negative Reselection Offset Bias (RESEL_OFFSET),and the serving DCCH signal strength is below the Mobile Reselection Threshold(SS_SUFF).

2.10.2 Matching Handoff and ReselectionBoundaries

To match the handoff boundaries with the DCCH reselection boundaries, theMAHO algorithm must emulate the reselection algorithm as closely as possible foreach sector-type. In addition, when possible, it is suggested that the neighbor cellMAHO channel (the neighbor cell channel measured by the mobile while it is on atraffic channel) be a DCCH on the neighbor cell. This ensures that the handoffalgorithm and the DCCH reselection algorithm are using the same signal tocontrol their respective functions.

2.10.2.1 Limitations on DCCH and HandoffAlgorithm Matching

The matching of DTC handoff boundaries with control channel reselectionboundaries is subject to the limitations indicated below. These limitations resultwhen DCCH reselection and DTC handoff related translations are configured withthe settings suggested in the following sections.

401-200-112, Issue 11 June 2001 2-47



■ For Dual Server Group Cells, Inter-Sector Upward Handoffs (from SG1 toSG0) are not supported. This limitation is necessary because at handoff,primary server group logical sectors are given preference over secondaryserver group sectors, independent of the sector-type designation.

■ At handoff, Preferred Neighbors are not reconsidered under the Regularneighbor criteria.

■ The treatment of mobiles for DCCH selection and reselection isindependent of mobile power class.

■ The handoff related mobile power class translation that effectively booststhe signal strength reported by Class 3 and 4 mobiles is deactivated. Thistranslation (C3OFFSET) is used in some circumstances, on cells servinglarge numbers of hand-held mobiles operating in automobiles.

2.10.2.2 DCCH Translation Definitions

The following DCCH translations are used to match the DCCH reselectionboundaries with the DTC handoff boundaries.

■ Mobile Attenuation Code (MS_ACC_PWR): The nominal output power amobile station may use to initially access the neighbor control channel.

■ SCAN_INTERVAL: The interval in DCCH hyperframes (1.28 seconds)between signal strength measurements of control channels.

■ High-Low Frequency (HL_FREQ): Allows mobile to deviate fromSCAN_INTERVAL for neighbor control channel sampling.

■ Mobile Access Threshold (RSS_ACC_MIN): Minimum control channelsignal strength (received at mobile station) required to access a cell.

■ Mobile Reselection Threshold (SS_SUFF): The minimum signal strengthdeemed sufficient for a neighbor control channel to be considered forreselection.

■ DELAY: The length of time a mobile must be camped on the current controlchannel before it may initiate control channel reselection.

2.10.2.3 MAHO Related Translations

The following DTC translations are used to match the DCCH reselectionboundaries with the DTC handoff boundaries.

■ Class 3/4 Offset (C3OFFSET): A positive bias applied to neighbor andcurrent sector signal strengths reported by Class 3 and 4 mobiles.

■ Interference Protection Threshold at Handoff for TDMA (INTPHT): Afixed signal strength threshold. A candidate’s signal strength must begreater than INTPHT to be considered for handoff.

2-48 401-200-112, Issue 11 June 2001



■ Face-to-Face BIAS: Signal Strength Bias. Candidate signal strength mustbe BIAS greater than the current signal strength to be considered forhandoff.

■ Mobile Secondary Threshold (MSECONDARY) and DecisionThreshold (DTH): If the serving signal strength is above MSECONDARY,all handoff candidates for which signal strength is less than DTH areeliminated. If the serving signal strength is below MSECONDARY, allhandoff candidates for which signal strength is less than DTH are saved asSecondary Candidates. The handoff candidate list contains normalcandidates followed by secondary candidates.

■ MSIG_SAMPLES: The number of samples used to calculate averagedMAHO signal strength.

■ Periodic Best Server Locate Trigger Generation Interval: Intervalbetween handoff algorithm triggers. These triggers initiate the TDMAhandoff process.

2.10.2.4 DCCH Translation Settings Common toAll Neighbors

This section specifies suggested settings for DCCH reselection translations toalign the DCCH Reselection and Traffic Channel Handoff boundaries.Thesetranslations on the serving cell/sector should be assigned the indicated values.

■ Set SCAN_INTERVAL = 1 Hyperframe. This matches the DCCHreselection sample interval to the MAHO measurement sample interval.

■ Set HL_FREQ = High. This ensures that neighbor control channels aresampled at SCAN_INTERVAL, and not at 2*SCAN_INTERVAL.

■ Set MS_ACC_PWR = 28 dBm. This removes the DCCH Reselection offsetdue to mobile power class.

2.10.2.5 MAHO Translations Common to AllNeighbors

This section specifies suggested settings for DTC handoff translations to align theDCCH Reselection and Traffic Channel Handoff boundaries.These translations onthe serving cell/sector should be assigned the indicated values.

■ Set MSIG_SAMPLES = 5. Sets the number of samples used to calculateaveraged MAHO signal strength equal to the number of samples used tocalculated control channel reselection signal strength.

■ Set BIASsg0 = +31 for Inner Server Group Other-Sector Neighbors.Eliminates Inter-Sector Handoffs from the outer server group to the innerserver group.

401-200-112, Issue 11 June 2001 2-49



■ Set C3OFFSET = 0. Removes handoff signal strength “boost” for Class 3and 4 mobiles.

■ Set PLOTMD = DELAYcurrent. Sets the periodic trigger interval for handoffequal to the minimum time a mobile must be camped on the current controlchannel before initiating control channel reselection. If DELAYcurrent isless than 3 seconds, PLOTMD should be set to its lowest non-zero value(3 seconds).

2.10.2.6 MAHO Translations for PreferredNeighbors

The serving cell should have the following translations configured for eachPreferred Neighbor cell:

■ Set BIAS for each preferred candidate low (-31). Removes candidateelimination according to relative threshold test; puts Preferred Neighbors attop of candidate list.

■ Set INTPHT = Max (SS_SUFF, RSS_ACC_MIN). Specifies fixed thresholdfor Preferred Neighbors; normally SS_SUFF > RSS_ACC_MIN, soINTHPT = SS_SUFF

■ Set DTH low (0). Prevents candidate elimination by DTH threshold.

DCCH Reselection uses DVCC and DCC Detection to prevent “false handoffs.” Toobtain equivalent performance for MAHO, Lucent Technologies stronglyrecommends use of Digital Locate Radio for DVCC detection at the “preferred”sector. This is particularly important in a co-channel interference environment,since preferred candidates have a bias value of -31.

2.10.2.7 MAHO Translations for RegularNeighbors

The serving cell should have the following translations configured for eachRegular Neighbor cell:

■ Set BIAScand = RSS_ACC_MINcand - RSS_ACC_MINcurr -RESEL_OFFSETcand. Sets relative threshold for Regular Neighbors; putsregular neighbors after preferred neighbors in candidate list.

■ Set INTPHT = RSS_ACC_MIN. Sets fixed threshold for regular neighbors.

■ Set DTH low (0). Prevents regular candidate elimination by DTH threshold.

2-50 401-200-112, Issue 11 June 2001



2.10.2.8 MAHO Translations for Non-PreferredNeighbors

The serving cell should have the following translations configured for each Non-preferred Neighbor cell.

■ Set BIAScand = RSS_ACC_MINcand - RSS_ACC_MINcurr -RESEL_OFFSETcand. Sets relative threshold for non-preferred neighbors;puts non-preferred neighbors after preferred neighbors in candidate list.

■ Set INTPHT = RSS_ACC_MIN. Sets fixed threshold for non-preferredneighbors.

■ Set MSECONDARY = SS_SUFFcurrent and Set DTH high (31). Sincecandidate signal strength should be less than DTH, non-preferredcandidates are included after regular candidates only if the serving channelsignal strength is less than MSECONDARY.

2.11 TDMA Hierarchical Cells

TDMA hierarchical cells is an optional feature developed for Cell Release 14.0 tointroduce additional criteria that may be considered when selecting a handoffcandidate. The additional criteria allow the service provider to exercise bettercontrol of the handoff process. For the most part, these criteria were defined bythe same translation parameters that help define the DCCH reselectionboundaries. The parameters consider the speed of the mobile as a criterion indetermining DCCH reselection. In Cell Release 15.0, this feature was modified byspeed-trending optimization that introduces three new translation parameters.The new parameters are similar to those used for DCCH reselection and areintroduced to allow the service provider to set separate criteria governing DTChandoff and DCCH reselection.

In a situation where more than one handoff candidate may be available to servicea call, TDMA hierarchical cells allow the call to be handed off to the candidateneighbor cell or sector best suited to handle the call, in accordance with theservice provider’s overall strategy. This optional feature is especially useful whenoperating in areas with a mix of small and large cells, as well as in areas withpublic and private systems in a DCCH environment.

This feature provides three levels to rank the order of handoff preference from onecell to another, and a delay timing parameter to discern mobile speed. In mixedsmall and large cell areas, a call handoff from a fast-moving mobile (high mobility)is better served by a large cell than by a small cell. It is more likely that a mobilemoving rapidly through small cells will incur a greater number of subsequenthandoffs, than if the mobile were handed off to a large cell. A call from a slow-moving mobile may then be directed to a small cell to keep its uplink transmitpower at a minimum. Essentially, this feature functionally creates a hierarchical

401-200-112, Issue 11 June 2001 2-51



structure of cells for each handoff to favor a candidate cell that is the most suitablecandidate for the handoff.

2.11.1 Operation Requirements

In order to activate and operate this feature at a cell, the Feature Activation File(FAF) loaded on the ECP and the following fields on the cell2 RC/V form must beset as indicated in the following subsections.

2.11.1.1 TDMA Hierarchical Cells

The TDMA HIER CELLS field must be set to y (yes) to indicate that the TDMAHierarchical Cells feature is active at the cell. This feature is QFAF-activated atthe cell site.

2.11.1.2 TDMA Full Rate

The TDMA full rate feature must be turned on before the TDMA DCCH feature isactive. Set this field to y (yes).

2.11.1.3 Digital Control Channel (DCCH)Feature

The digital control channel feature must be activated at the cell to allow mobilesaccess to the TDMA control channels. To activate this feature, enter a y (yes) inthe TDMA DCCH field. This feature cannot be turned on if the TDMA Full Ratefeature is turned off. The TDMA DCCH feature is also FAF-activated at the ECP.

2.11.1.4 TDMA Periodic Best Server Locate

It is recommended that the TDMA periodic best server locate feature be used(refer to Paragraph 2.11.9). This feature is FAF-activated at the ECP. The way inwhich TDMA Periodic Best Server Locate is activated depends on the handoffalgorithm in effect. If the serving face has MAHO active, to turn on this feature atthe cell, enter a y (yes) in the TDMA PRC BSL field. If the serving face has HybridMAHO/Digital Locate active, TDMA PBSL is turned on by setting the per facedigital locate type field to PBSL.

2.11.2 Modeled After DCCH ReselectionAlgorithms

The hierarchical cells structure is modeled after the DCCH reselection algorithmsin IS-136 and uses the same or similar DCCH reselection parameters which arediscussed in Paragraph 1.5.1. By using the same reselection parameters, this

2-52 401-200-112, Issue 11 June 2001



feature helps to more closely align MAHO boundaries with DCCH reselectionboundaries. Similar, but separate, speed trending parameters provided in R15.0,allow the service provider to adjust the degree of alignment between the handoffand DCCH reselection boundaries.

2.11.3 Handoff and DCCH ReselectionBoundary Misalignment

To best understand the mechanism of TDMA hierarchical cells, it is helpful tobriefly review how the MAHO and DCCH reselection boundaries are established.

2.11.3.1 MAHO Handoff Boundary

Up to 12 handoff neighbors may be identified on the MAHO neighbor list (if FLCAis deployed, this number is reduced to eight). This list is transmitted to the mobilesin a LAF service area over the DTC channel whenever the mobile is confirmed onthat DTC channel. The MAHO neighbor list identifies the MAHO channels in theneighboring sectors, which are typically DCCH channels. Thus, when in search ofa handoff candidate, the cell uses the downlink MAHO channel signal strengthmeasurements, which are periodically monitored and reported by the mobile, todetermine the strongest handoff candidate. If Hybrid MAHO/Digital Locate isused, handoff is based on both downlink and uplink signal strengthmeasurements. Regardless of whether MAHO or Hybrid MAHO/Digital Locate isselected, the call handoff boundary and selection of a handoff candidate at the cellis based on measured signal strength only.

The hierarchical cells feature will operate in either the MAHO or Hybrid MAHO/Digital Locate mode. The MAHO mode selected determines if either thehierarchical cells uplink threshold (HC UTH) or downlink threshold (DTH)parameter is used for this feature as defined in Table 2-9.

2.11.3.2 DCCH Reselection Boundary

The DCCH reselection list (refer to Paragraph 1.5.1) defines the DCCHreselection boundary. This list is broadcast to the idle mobiles in a sector servicearea to identify up to 24 neighboring DCCH channels in that sector service area.Each idle mobile, which is camped on a specific DCCH channel, periodically tunesthrough all the channels on the reselection list in an attempt to find a better DCCHchannel. The DCCH reselection process is not based on signal strength alone.Therefore, the best DCCH channel may not always be the one with the strongestsignal strength, as with MAHO handoff candidates. Instead, the DCCH reselectionprocess uses criteria based on parameters, such CELL TYPE and DELAY. Theseparameters are entered via the resel form to favor the selection of a particularDCCH channel under certain conditions. Therefore, a LAF selected as a MAHO

401-200-112, Issue 11 June 2001 2-53



handoff candidate may be rejected for DCCH reselection, resulting in MAHO andDCCH reselection boundary misalignment.

To minimize this misalignment, hierarchical cells use the same type of CELLTYPE and DELAY parameters and selection algorithm in the call handoff process.In the R14.0 version of this feature, cells that were on the DCCH reselection listused the same CELL TYPE and DELAY parameters that are inserted on the reselRC/V form for DCCH selection. If the cell is not on the DCCH reselection list, newTDMA Hierarchical Cells - Type (CELL TYPE) and Delay (DELAY) parametersintroduced in Release 14.0 are used by the hierarchical cells algorithm. The newparameters are inserted via the fci form and to maintain continuity with those cellsthat are on the DCCH reselection list, the new parameters are set to the samevalues as those on the resel form.

2.11.3.3 Speed-Trending Optimization

As previously mentioned Speed -Trending Optimization introduces three newtranslation parameters, the first two of which replaces similar R14.0 parameters.Because the speed-trending requirement for call handoffs may differ from thespeed-trending requirement for DCCH reselection, the first parameter replaced byR15.0 is the Hierarchical Cells - Delay (DELAY) value which is replaced with theHierarchical Cells - Delay (H_DELAY) value. The H-DELAY value is entered onthe HC DLY field of the fci form as part of the MAHO list parameters. Therefore,each MAHO neighbor may receive a different H_DELAY value so that theH_DELAY parameter is used by all hierarchical cells regardless of whether theMAHO neighbor is (or is not) on the DCCH reselection list (refer to Table 2-9).R15.0 also provides two new threshold parameters that define minimum signalstrength levels required for handoff.

In R14.0, the DELAY value is used only on those MAHO neighbor sectors thatare not on the DCCH reselection list. Those MAHO neighbor sectors that are onthe DCCH reselection list use the delay value from the resel form (refer to Table2-9).

The second parameter introduced by speed trending optimization is TDMAHierarchical Cells Handoff (HIER_HO). This parameter replaces the TDMAHierarchical Cells - RSS Access value to indicate the minimum received signalstrength at the mobile required for the mobile to be handed off to the MAHOneighbor face. As with the H_DELAY value, the HIER_HO value, is also enteredon the fci form as part of the MAHO list parameters. The R15.0 value is enteredvia the HC HO field rather then the TDMA Hierarchical Cells - RSS Access field asfor R14.0.

The third parameter is the Serving Signal Strength Reference (HIER_HOserv).This parameter indicates the minimum mobile-reported serving signal strengthlevel required for hierarchical handoff and is inserted from the fci form.

2-54 401-200-112, Issue 11 June 2001



lt

d

)

2.11.4 Hierarchical Cells Algorithm andParameters

When the TDMA hierarchical cells feature is deployed, an algorithm similar to theDCCH reselection algorithm is used to favor the selection of a handoff candidatebased on a number of parameters, in addition to signal strength measurements.As indicated in the previous paragraph, the parameter used by the algorithm is afunction of the cell release version. When using R14.0, one of two sets of delayand threshold parameters are used as a function of whether the MAHO neighborsector is on the reselection list. If the channels on the MAHO neighbor list matchthe channels on the DCCH reselection list, some of the same parameters used forDCCH reselection are used in the TDMA hierarchical cells algorithm. If thechannels on the MAHO neighbor list are not on the DCCH reselection list, newdelay threshold parameters introduced for this feature are used.

The parameters used by the algorithms are specific for each DCCH channel. Forsuch DCCH channels, the MAHO and DCCH reselection boundaries are moreclosely aligned. For those channels on the MAHO neighbor list that are not on theDCCH reselection list, new parameters entered through the fci form are used bythe TDMA hierarchical cells algorithm. In this case, a single set of parameters isused by the TDMA hierarchical cells algorithm for all of those MAHO neighbor listchannels that are not on the DCCH reselection list.

However, in the R15.0 version, a single set of delay and threshold parameters areused for each DTC channel. Thus, the degree of boundary alignment between theMAHO neighbor list and the DCCH reselection list can be adjusted. Table 2-9 listsnew and existing RC/V parameters that must be considered when implementingTDMA hierarchical cells for R14.0 and R15.0.

Table 2-9 Parameters Associated with Hierarchical Cells

Parameter CellRelease

Description Range DefauValue

The following parameters are unique to hierarchical cells and, unless noted, are insertevia the fci form.

TDMA HierarchicalCells - Active

R14.0/R15.0

Activate hierarchical cellsfeature on the Logical AntennaFace (LAF).

y/n n (notactive

401-200-112, Issue 11 June 2001 2-55



lt

TDMA HierarchicalCells - Type (CELLTYPE)

R14.0/R15.0

Indicates cell type preference ofa MAHO neighbor face.

This parameter is used only onthose channels on the MAHOneighbor list that are not on theDCCH reselection list. If theDCCH channel is common toboth lists, the cell typepreference for each DCCHchannel is extracted from theresel form for that channel.

pre (preferred), reg(regular), and non(non-preferred)

reg

TDMA HierarchicalCells - Delay(DELAY)

R14.0only

Controls how long a neighborcell face must meet the criteriafor handoff before handoff iseligible.

This parameter is used only onthose channels on the MAHOneighbor list that are not on theDCCH reselection list. If theDCCH channel is common toboth lists, the delay for eachDCCH channel is extracted fromthe resel form for that channel.

0 to 140 = no delay; eachincrement from 1 to7 increases delayby 15 seconds, andeach incrementfrom 8 to 14increases delay by45 seconds

1

TDMA HierarchicalCells - Delay(H_DELAY)

R15.0 Controls how long a neighborcell face must meet the criteriafor handoff before handoff iseligible.

0 to 150 = no delay; eachincrement from 1 to5 increases delayby 2 seconds;each incrementfrom 6 to 15increases delay by5 seconds

1




2-56 401-200-112, Issue 11 June 2001



lt

TDMA HierarchicalCells - RSS Access(ReselectionThresholdSS_SUFF)

R14.0only

Indicates the minimum receivedsignal strength (RSS) at themobile that is required for themobile to access the MAHOneighbor face.

This parameter is used only onthose channels on the MAHOneighbor list that are not on theDCCH reselection list. If theDCCH channel is common toboth lists, the RSS Access(Reselection ThresholdSS_SUFF) value for eachDCCH channel is extracted fromthe resel form for that channel.

-111 to -51 in 2dBmincrements

-99

TDMA HierarchicalCells Handoff(HIER_HO)

R15.0 Indicates the minimum receivedsignal strength at the mobile thatis required for the mobile to behanded off to the MAHOneighbor face.

The mobile-reported signal mustexceed the HIER_HO thresholdby a time interval identified bythe H_DELAY parameter.

-113 to -51 in2dBm increments

-113

TDMA HierarchicalCells - Attenuation(MS_ACC_PWR)

R14.0/R15.0

Indicates maximum outputpower that the mobile stationuses to access the neighbor cellface.

This parameter is used only onthose channels on the MAHOneighbor list that are not on theDCCH reselection list. If theDCCH channel is common toboth lists, the Attenuation(MS_ACC_PWR) value for eachDCCH channel is extracted fromthe resel form for that channel.

0 to 10 in 4-dBincrements

0=36 dBm,1=32 dBm, 2=28dBm.....10 =-4 dBm

For PCS: 0 and 1= 30 dBm, 2 =26 dBm ....10= -4 dBm.

0




401-200-112, Issue 11 June 2001 2-57



l

lt

HC UTH(Hierarchical CellsUplink Threshold)

R14.0/R15.0

This parameter is inserted fromthe fci form and specifies theminimum uplink signal strengththreshold, as measured by theMAHO neighbor face, for theneighbor face to be consideredas a preferred cell type handoffcandidate.

This parameter is used whenoperating in the Hybrid MAHO/Digital Locate mode.

0 to 127 RSSI 54

Serving SignalStrength Reference(HIER_HOserv)

R15.0 Indicates the minimum mobile-reported serving signal strengthlevel required for hierarchicalhandoff. This parameter isinserted from the fci form.

-51 to -113 dBm in2-dB increments

-113dBm

The following parameters are pre-existing parameters and are not unique to hierarchicacells.

SG0 DTH, SG1DTH (DownlinkThreshold)

R14.0/R15.0

Specifies the minimum downlinksignal strength threshold, asmeasured by the mobile, for theneighbor server group SG0 andSG1 LAF to be considered as apreferred cell type handoffcandidate.

These parameters are insertedon the fci form and are definedas downlink threshold only whenused with the hierarchical cellsfeature. When used with otherfeatures, the SG0 and SG1 DTHparameters are referred to asDecision Threshold, which isdefined differently.

These parameters are usedwhen operating in the MAHOmode.

0 to +31, or Null Null




2-58 401-200-112, Issue 11 June 2001



lt

SG0 Bias, SG1Bias (Downlink andUplink)

R14.0/R15.0

These parameters are insertedon the fci form and indicate thehandoff bias in the MAHOneighbor list.

-31 to +31 (IS-54Bencoded units) fordownlink and-127 to +127(RSSI) for uplink, orNull

Null

Threshold - MobileSecondary(MSECONDARY)

R14.0/R15.0

Indicates the minimum mobile-measured serving signalstrength before a non-preferredcandidate is considered forhandoff.

This parameter is inserted fromthe fci form and the abovedescription applies only whenuse with the hierarchical cellsfeature.

0 - 31 in IS-54Bunits

Null

Atten (Attenuation)( MS_ACC_PWR)

R14.0/R15.0

This parameter is inserted fromthe resel form and indicates themaximum output power that themobile station may use toaccess the neighbor cell face.

The parameter in this field isonly required for non-localcandidate entries (those not onthe same MSC as the currentsector). When a local handoffcandidate (one on the sameMSC) is considered, the valueinserted in the MobileAttenuation Code field on theceqface form is used (seebelow).


For cellular:0=36 dBm,

1=32 dBm.....10 =-4 dBm


0




401-200-112, Issue 11 June 2001 2-59



lt

2.11.5 Cell Type Parameter

The principle parameter for both DCCH reselection and the TDMA hierarchicalcells handoff selection is CELL TYPE. This parameter allows the service providerto determine cell hierarchy by specifying a preference for a neighbor sectorrelative to the serving sector. The handoff preference of each DCCH channel thatis common to both the MAHO neighbor list and the DCCH reselection list isseparately designated by its CELL TYPE as Preferred, Regular, or Non-preferred.These designations, along with other handoff-related parameters, are used by the

TDMA HierarchicalCells - RSS Access(ReselectionThresholdSS_SUFF))

R14.0only

Indicates the minimum receivedsignal strength (RSS) at themobile that is required for themobile to access the MAHOneighbor face.

The parameter in this field isonly required for non-localcandidate entries (those not onthe same MSC as the currentsector). When a local handoffcandidate (one on the sameMSC) is considered, the valueinserted in the MobileReselection Threshold(SS_SUFF) field on the ceqfaceform is used (see below).

-111 to -51 in 2dBmincrements

-99

Mobile AttenuationCode

R14.0/R15.0

This parameter is inserted fromthe ceqface form and indicatesthe maximum output power thatthe mobile station uses toaccess the neighbor cell face.


0=36 dBm,1=32 dBm.....10 =-4 dBm


0

Mobile ReselectionThreshold(SS_SUFF)

R14.0only

This parameter is inserted fromthe ceqface form and indicatesthe minimum control channelsignal strength (received at themobile) required to access cell.

-51 to -111 dBm in2-dB increments

-99




2-60 401-200-112, Issue 11 June 2001



serving cell to assess the most suitable candidate for the handoff. Thesedesignations apply even if the neighbor signal strength is not the highest receivedfrom the mobile, but is of a sufficient level to provide quality service. Although thethree CELL TYPE values have been previously described as part of the DCCHreselection discussion, a brief description of the three cell type values is givenbelow as related to TDMA hierarchical cells handoff selection:

■ Preferred — A preferred cell type has the highest preference. A handoffcan be made to the preferred neighbor even if the signal strength receivedfrom the neighbor is lower than the serving cell signal strength. The maincriteria here is that the preferred neighbor cell must have signal strengthdefined by the system as sufficient to provide quality service.

■ Regular — A regular cell type has the second highest preference. Ahandoff to a regular cell may occur if its received signal strength is greaterthan the current serving cell signal strength by a bias, and there is noeligible preferred cell.

■ Non-Preferred — A non-preferred cell type has the lowest preference. Ahandoff will occur if the serving cell received signal strength drops below acertain threshold to provide service, and if the neighbor cell signal strengthis greater than the current cell signal strength by a bias.

Preferential treatment for handoffs. 2The assignment of cell type preferenceenables mobiles to be directed to cells where special services, such as privatenetworks, in-building services, and data support are available. For example, aservice provider can specify that cells within an in-building private system begiven preference for handoff relative to cells outside the network. This permitscalls to be maintained on the private network, even when there is a strongerchannel available on a public network. A mobile is no longer required to stay onthe cell or face with the strongest radio frequency (RF) signal.

2.11.6 H_DELAY Parameter

Another key parameter is H_DELAY (DELAY for R14.0), which determines howlong the signal strength measured on a candidate neighbor cell face must bebetter than the a calculated signal level before a handoff to the neighbor mayoccur. For R14.0, the DELAY value may be set between 0 and 14, where 0 equalsno delay, and each increment from 1 to 7 increases the delay by 15 seconds.Thus, the value of 7 produces a delay of 105 seconds. Each subsequentincrement from 8 to 14 further increases the delay by 45 seconds for a total delayof 420 seconds.

For R15.0, the H_DELAY value may be set between 0 and 15, where 0 equals nodelay, and each increment from 1 to 5 increases the delay by 2 seconds. Thevalue of 6 produces a delay of 15 seconds. Each subsequent increment from 7 to15 further increases the delay by 5 seconds for a total delay of 60 seconds.

401-200-112, Issue 11 June 2001 2-61



2.11.7 Handoff Criteria

The handoff algorithm used by the hierarchical cell classifies MAHO neighbor listhandoff candidates that meet timing and signal strength level handoffrequirements in two criteria. Other than signal strength requirements, the primarydifference between a criteria 1 and a criteria 2 candidate is that a criteria 1candidate must be a preferred cell type. Different algorithms are used to qualify aLAF candidate as either criteria 1 or criteria 2 candidate. If the LAF does notqualify for either criteria, the LAF is dropped from consideration. Both algorithmsuse the parameters identified in Table 2-9 and the locate radio, when available,and MAHO reported signal strengths to determine candidate eligibility. If apreferred cell type fails to qualify as a criteria 1 candidate, it is tested for criteria 2candidacy.

2.11.7.1 Criteria 1 Qualifying Algorithm

For each preferred cell type LAF to qualify as a criteria 1 candidate, an adjustedsignal strength value (C_RESELcand

*) is computed from the reported MAHOsignal strength by the serving voice EDRU radio. There are three conditions thatmust be satisfied to qualify a LAF as a criteria 1 candidate:

Note: The following conditions are expressed using R15.0 parameters,with R14.0 parameters given in italics.

1. The adjusted MAHO neighbor reported average signal strength level(NSIGcand) must be above the TDMA Hierarchical Cell Handoff Threshold(HIER_HOcand) threshold or mobile reselection threshold (SS_SUFF) forR14.0, less either mobile access power defined by MS_ACC_PWR minusthe maximum mobile output power defined by its power class OR zero,whichever is greater.

To test for the first condition, the adjusted signal strength value(C_RESELcand) is computed by the serving voice EDRU radio as follows:

For R15.0:C_RESELcand = NSIGcand -HIER_HO cand - MAX [(MS_ACC_PWRcand -P) or0]

For R14.0:C_RESELcand = NSIGcand -SS_SUFFcand - MAX [(MS_ACC_PWRcand -P) or0]

* The subscripts cand and serv indicate that the parameters apply to the candidate and theserving LAFs, respectively.

2-62 401-200-112, Issue 11 June 2001



Where (for both R14.0 and R15.0):NSIGcand =

Adjusted MAHO neighbor reported average signal strength

MAX (MS_ACC_PWRcand -P) or 0 =The larger of either (MS_ACC_PWRcand -P) or 0

P= the highest the mobile will transmit based on its Mobile Power Class

In order to qualify for the first condition, C_RESELcand must be greaterthan 0.

2. The C_RESEL cand signal strength must be maintained at the level quali-fied in condition 1 for a duration greater than the time specified by theH_DELAY [DELAY] parameter.

3. The reported MAHO signal strength must be above the downlink threshold(DTH) for whatever server group being considered. If Hybrid MAHO/ DigitalLocate is active using uplink ranking, the reported uplink MAHO signalstrength must be above the hierarchical cells uplink threshold (UTH).

2.11.7.2 Criteria 2 Qualifying Algorithm

Four conditions must be met to qualify a LAF as a criteria 2 candidate. The firsttwo conditions are identical to the first two used to qualify a criteria 1 candidate.

The third condition is that C_RESELcand must be greater than C_RESELserv +Biascand. The value C_RESELserv is an indication of the serving LAF signalstrength calculated in the same manner as the C_RESELcand is calculated, usingthe serving LAF signal strength measure and parameters as follows:

For R15.0:C_RESELserv =MSIG - HIER_HOserv - MAX [(MS_ACC_PWRserv -P) or 0]

For R14.0:C_RESELserv =MSIG - SS_SUFFserv - MAX [(MS_ACC_PWRserv -P) or 0]

Where:MSIG = Adjusted averaged serving mobile reported signal strength

MAX [(MS_ACC_PWRserv or -P) or 0] =The larger of either (MS_ACC_PWRserv -P) or 0

The Biascand is the candidate LAF downlink handoff bias on the MAHO neighborlist.

401-200-112, Issue 11 June 2001 2-63



The fourth condition is that either the candidate cell type is not non-preferred, ORthat the mobile reported serving signal strength be below the mobile secondarythreshold.

2.11.7.3 Ranking of Handoff Candidates

A candidate whose LAFs meet the requirements in Criteria 1 are listed first,followed by candidate faces that meet the requirements in Criteria 2. Candidatefaces are categorized by server group (SG0, SG1). In each case, inner servergroup candidates are listed first in descending order of signal strength. Then,outer server group candidates are listed next in descending order of signalstrength.

After all eligible candidates are categorized according to criteria, the candidate listwill be ordered as follows:

1. Criteria 1 candidates from SG0




Only the top three candidates on the list will be sent to the ECP.

2.11.7.4 Intra-Cell Handoff

If the default values for Serving Signal Strength Reference (HIER_HOserv) (- 113dBm) and HO_DELAY (0 seconds) are maintained intra-cell upward handoff willnot occur. In order to enable intra-cell upward handoffs, the following conditionmust be met for the SG0 face on the MAHO neighbor list of the SG1 face.HIER_HOcand < (HIER_HOserv + BIASsg0), where BIASsg0 is the downlink biasgoverning the handoff to the SG0 face and is located on the MAHO neighbor list.

2.11.8 Mobile Speed Trending

In areas serviced by a mix of small and large cells, mobile speed trending directshandoff from slow moving mobiles to small cells, and handoff from fast movingmobiles to large cells. The advantage of this mobile speed trending is twofold:

■ By using small cells to service low mobility intra-city calls, the talk-timebattery life of the mobiles is extended because the uplink transmissionpower required in small cells is lower. Lower uplink transmit power reducesco-channel interference.

■ The number of handoffs needed to support fast moving mobile calls inlarge cells is minimized to reduce number of dropped calls.

2-64 401-200-112, Issue 11 June 2001



The H_DELAY parameter can be used to determine the speed of the mobile to behanded off. Therefore, this parameter is used to help eliminate fast movingmobiles from being handed off to a small cell when a larger cell is available toservice the call, as shown in Figure 2-13.. Although the mix of small and largecells shown in this figure may not be typically found at the edge of a large town orcity adjacent to a less populated rural area, it is chosen to best illustrate mobilespeed discrimination that may be achieved through hierarchical cells.

Figure 2-13. Mobile Speed Discrimination

The service strategy supported by this illustration is to use small cells, providinggreater frequency reuse factor to increase capacity in densely populated areas.The small cells provide service to pedestrians, shoppers, and slow moving localtraffic. The larger cells are used to provide service to the less populated largerrural areas and to highway traffic which runs along the edge of the city or town.Because the larger cells will transmit a stronger signal, the smaller cells should begiven a higher CELL TYPE preference over their larger neighbor cells. As a result,handoff from inter-city pedestrians, shoppers, and slow moving local traffic favorsthe small cells.

401-200-112, Issue 11 June 2001 2-65



Without mobile speed discrimination, the fast moving northbound mobiles arehanded off from Cell 1 to Cell 2 to Cell 3 and to Cell 4. To eliminate handoff of fastmoving highway mobiles from one small cell to another, a relatively longH_DELAY parameter is assigned to the small cells. The length of the delay timemust be sufficient so that the signal strength from fast moving mobiles on thehighway cannot maintain its threshold requirement for the time specified by thedelay parameter. Therefore, the value of the delay parameter is a function of theaverage mobile speed on the highway and the radius of the small cell. When thisvalue is correctly set, the small cell candidacy for fast moving vehicles on thehighway is eliminated, and the call is handed off to the larger cell.

2.11.9 Periodic Handoff Triggering

It is recommended that the TDMA Periodic Best Server Locate (TDMA PBSL)feature be turned on when the hierarchical cells feature is active. To optimize theperformance of the hierarchical structure provided by this feature, the mobile mustbe able to identify potential preferred candidates for handoff, even when the callquality on the serving cell is acceptable. If the TDMA PBSL is not turned on,handoff is only triggered when channel quality on the serving face has degradedto an unacceptable level. As a result, the handoff boundaries at the Preferred andRegular (cell type) neighbor cells may be different from the DCCH Reselectionboundaries.

If the handoff algorithm is MAHO, turn on TDMA PBSL using the cell2 form. If thehandoff algorithm is Hybrid MAHO/Digital Locate, specify the periodic locate typeto be turned on for the serving logical face using the fci form.

2.11.10 Feature Interaction

In addition to TDMA PBSL, there are a number of other features that may interactwith hierarchical cells. These features are listed below:

2.11.10.1 DCCH Non-Public Network Identifiers(NPNI)

The DCCH NPNI feature allows the service provider to specify a preference formaintaining calls on antenna faces that are part of a private network. Thisfunction, which is performed at the Mobile Switching Center (MSC), continues toexist when the hierarchical cells feature is active, and a hierarchical list of handoffcandidates faces has been formulated at the cell. To insure that the call willremain in UZ domain, the Hierarchical Cells can be set up to preferentially keepcalls within a UZ. Refer to 401-612-126, DCCH Non-Public Network Identifiers(NPNI) and Charging Areas Optional Feature for a description of the NPNIfeature.

2-66 401-200-112, Issue 11 June 2001



2.11.10.2 Hand-Off Based on Interference TDMA(HOBIT)

When interference on the RF voice channel currently serving a mobile isunacceptable, HOBIT may cause a handoff to another channel on the same LAF.Because there is no DCCH reselection at the serving face, the cell type at theserving cell must be defined to support handoffs. On the fci form screen the TDMAHierarchical Cells-Type field should be defined as regular (reg),.

2.11.10.3 DCCH Interhyperband Operations(DIHOP1 and DIHOP2)

Hierarchical cells are applicable to interhyperband handoffs, where calls arealways handed off from a DTC. Like NPNI that may specify a preference for eithera public or private network, the DIHOP feature may re-prioritize candidates forhandoff based on a particular hyperband. For example, the service provider canspecify a handoff preference for either a PCS hyperband or a Cellular hyperband.This function is performed at the MSC, and should continue to operate as it doeswhen the Hierarchical Cells feature is active.

When the DIHOP1 and DIHOP2 features are turned on, the interhyperband digitallocate functionality is not applicable. Therefore, the ranking of hierarchical cellswill be done using plain MAHO (non-digital locate).

No changes have been made to the DCCH interhyperband operation parametersrelated to candidate preference for handoff. Refer to 401-612-118, DCCHInterhyperband Operations Phase 1 and Phase 2 (DIHOP1 and DIHOP2)Optional Features for a description of these features.

2.12 Two Branch Intelligent Antennas(TBIA) on the EDRU

This optional feature takes advantage of the currently deployed two diversityreceive antenna array to improve voice quality in the presence of interferenceusing an adaptive antenna beam forming technique. When implemented in aninterference environment, uplink voice quality C/I performance improvement up to3 or 4 dB at 1% bit error rate (BER) can be expected. This feature providesmaximum benefit when deployed in cells experiencing high levels of interference.

This optional feature does not require any hardware modification and isimplemented in the EDRU software which changes the manner in which the twodiversity signals are combined. The feature uses an Adaptive InterferenceRejection algorithm that converts the received RF signal into a stream of in-phaseand quadrature-phase I and Q digit values. Subsequently, the I and Q values are

401-200-112, Issue 11 June 2001 2-67



weighted by a coherent dynamic weighting factor to adjust the received RF signalphase and amplitude. The coherent weighting factor is first estimated using theknown sync sequence in the IS-136 slot and is then updated throughout theremaining slot period using decision feedback to estimate the unknown symbols.The I and Q values are then added together to maximize the received signalSignal to Interference Noise Ratio (SINR).

The EDRU currently uses Maximum-Ratio Combining (MRC) to combine the twodiversities into a single data stream. MRC is a well-known technique for diversitycombining that has the property that it maximizes the Signal to Noise Ratio (SNR)at the output of the array when noise is the sole impairment. However, MRC doespoorly in the presence of co-channel interference. This is because it treats theinterfering signal as if it were independent noise when, in fact, it behaves verymuch like the desired signal.

Since TBIA is a software back-fit into the EDRU requiring no hardware changesand is designed to function with existing antenna configurations which aretypically either two antennas spaced 10λ apart or a single antenna with two cross-polarized receivers. This optional feature is activated at the cell by setting theTDMA TBIA field in the Optional Feature section on the cell2 RC/V form to "y"(yes). The feature may be separately turned on and off at each logical antennaface (sector) by setting the TDMA Two Branch Intelligent Antennas Feature Activefield on the corresponding fci RC/V form to either y or n.

2.13 Deployment Recommendations

The previous section discussed RF frequency planning issues; this sectionprovides information and recommendations for the following TDMA deploymentissues:

■ Diversity Receive

■ Time Dispersion and Equalizer Options

■ Mobile Assisted Handoff (MAHO) Channel Implementation

2.13.1 Diversity Receive

For the highest quality TDMA reception, Lucent Technologies recommends usinga diversity receive configuration in which two antennas--one connected to each ofthe diversity receive ports--are deployed.

2-68 401-200-112, Issue 11 June 2001



2.13.2 Time Dispersion and Equalizers

To minimize the impact of signal fading, Lucent Technologies recommendsenabling built-in mobile and cell site time delay equalizers. Use of equalizerscounteracts time dispersion of received signals as explained below.

Time dispersion of received signals is caused by reflections from obstacles in theenvironment. Reflected signals arrive later than signals taking a direct path fromthe transmitter to the receiver. Cell site and mobile receivers have equalizers thatcan use signals that arrive up to one symbol period apart (41.2 µs). This intervalcorresponds to a path difference of:

In a Rayleigh fading environment, time dispersion actually helps reduce errorrates by creating a type of time diversity. Strong signals with long delays are likelyto occur in areas next to mountains or high hills. Preliminary measurements showthat significantly delayed signals may also occur in urban and suburbanenvironments. Long signal delays are more likely to occur in large sectors whereopportunities for long path lengths are more frequent.

Some mobiles offer the option of turning off the equalizer disabling the DelayInterval Compensation translation). The default condition (equalizer on) isrecommended for any environment exhibiting more than 10 µs of delay spread.The equalizer may not offer any performance advantage in environments in whichtime dispersion is less than 10 µs.

2.13.3 MAHO Channel Assignment

Mobile Assisted Handoff (MAHO), can be implemented on a variety of radio types(ACC, analog or digital voice radio, and DCCH). This section provides someguidelines for selecting among these options. Regardless of the radio typeselected for the MAHO channel, Lucent Technologies recommends use of theDigital Locate feature to minimize potential interference.

2.13.3.1 Using ACC as MAHO Channel

In an RF environment with no significant co-channel interference on the ACC(setup channel), using the ACC as the MAHO channel is an effective option. Insuch conditions, downlink RF interference is minimized, since the ACC isconstantly transmitting (i.e., another RF carrier is not being introduced into the

41.2µs 3 108m×

1s----------------------× 10

6– s1µs

-------------× 12.4km 7.7mi= =

401-200-112, Issue 11 June 2001 2-69



environment). This is an option for cells in which the voice channel configuration(omni or directional) matches the ACC configuration.

In a crowded system, use of the ACC as a MAHO channel is not recommended.Since there are only 21 ACCs in a system, reuse of setup channels is higher thanthat of most voice channels (analog or digital). This can lead to "MAHO falsing," inwhich the mobile reports back signal strength information from an interfering siteinstead of from the desired site. This in turn can lead to erroneous handoffs anddropped calls. In this case, use of a voice channel is preferred; or, if DCCH isdeployed, the DCCH is recommended for use as the MAHO channel.

2.13.3.2 Using Voice Channel as a MAHOChannel

Using a voice channel (analog or TDMA) as the MAHO channel (beacon) offersthe advantage of minimizing or eliminating MAHO falsing. With proper selection ofthe beacon voice channel frequency (usually combined with sequential trunkhunt), co-channel interference on the beacon channel can be eliminated orminimized during non-peak hours.

The potential disadvantage of using voice channels as beacons is that overall RFinterference in the system will be slightly increased, because more RF carriers willbe transmitting all the time.

When using a voice radio as a beacon channel, at least two radios that supportthe technology type of the beacon (analog or TDMA) should be equipped on eachlogical antenna face where beacon channels are employed. This will ensure that,in the event of failure of the original beacon radio, Automatic RadioReconfiguration (ARR), when active, has a radio of the proper technology toreconfigure as the beacon.

2.13.3.3 Using DCCH as MAHO Channel

Lucent Technologies recommends using the DCCH as the MAHO channel whenDCCH is deployed.

■ No additional RF interference is introduced by using a beacon voicechannel because the DCCH transmits continuously.

■ The DCCH should have less co-channel reuse than the ACC, becauseDCCHs can be assigned to any channel number (except those reserved forthe ACC). This provides improved MAHO performance since the mobile isless likely to measure a co-channel interferer instead of measuring thedesired MAHO channel (reducing MAHO falsing).

2-70 401-200-112, Issue 11 June 2001



In addition, Lucent Technologies recommends use of at least two DRUs on facesin which DCCH is deployed, for use by ARR.

401-200-112, Issue 11 June 2001 2-71



2-72 401-200-112, Issue 11 June 2001



Hardware Installation


3.2 DTC and DCCH Feature Activation 3-1

3.2.1 Digital Traffic Channel (DTC) 3-2

3.2.2 Digital Control Channel (DCCH) 3-2

3.3 Hardware Installation 3-2

Run Diagnostics 3-3

3.3.1 Equipment Requirements 3-3

3.3.2 Pre-Installation Cell Inspection and Diagnostics 3-4

3.3.3 Power Down RCF 3-5

3.3.4 RTU/TRTU RF Switch Assembly Installation 3-5



3.3.4.3 Install Control Cables 3-14

3.3.4.4 Connecting DC Power Cable 3-15

3.3.5 Radio Shelf Power Upgrade 3-15

3.3.5.1 Installing DRUs. 3-15

3.3.5.2 Installing EDRUs 3-15

3.3.5.2.1 Series II Classic Radio Frame 3-16

When to Replace +5V CONV Circuit Breaker 3-16When to Replace +12-Volt PCU 3-16

3.3.5.2.2 Series IIm Cabinet 3-163-16

3-163-16

3-16

3-15

3-15

3-15

3-15

3-14

3-11

3-6

3-5

3-5

3-4

3-3

3-3

3-2

3-2

3-2

3-1

3-1

June 2001 3-1

Contents


3.3.5.2.3 Series IImm Cabinet 3-17


3.3.6 Power Converter Unit and Circuit BreakerReplacement 3-18

3.3.6.1 Replace Shelf Designation Labels(Customer Option) 3-19

3.3.7 Install TRTU and DRU(s) 3-19

3.3.8 Install T-EDRU and EDRU(s) 3-20

3.3.9 Test EDRU (T-EDRU) Personality 3-20

3.0.1 Restore Cell 3-24

3.0.1.1 Power Up Cell 3-24

3.0.1.2 Boot Cell 3-24

3.0.2 Modify RC/V Translations 3-25

3.1 Complete the Installation Process 3-25

3.1.0.1 Download Cell Site Generic 3-26

3.1.0.2 Hardware Testing 3-26

3.1.0.3 RF Measurements 3-27

3.1.0.4 Allow Call Processing 3-29

3.2 Receive Path Gain Measurements 3-30

3.2.1 Receive Path Gain 3-303-30

3-30

3-29

3-27

3-26

3-26

3-25

3-25

3-24

3-24

3-24

3-20

3-20

3-19

3-19

3-18

3-173-17

3-17

3-173-17

3-2 401-200-112, Issue 11 June 2001



Hardware Installation 3

3.1 Introduction

This chapter describes hardware installation for TDMA and DCCH in anAUTOPLEX System 1000 cell site.

Prior to installation, activate DTC and DCCH features as described in SectionParagraph 3.2 , and run diagnostics as described. The primary tasks of TDMA/DCCH installation are:

■ Install hardware

■ Modify RC/V database translations (Chapter 4)

■ Download cell site generic and run diagnostics

■ Test hardware and RF power parameters

■ Measure Receive Path Gain (RPG)

3.2 DTC and DCCH FeatureActivation

The following DTC and DCCH features enhance TDMA performance and shouldbe activated in the Feature Activation File (FAF).

June 2001 3-1


3.2.1 Digital Traffic Channel (DTC)

Lucent Technologies strongly recommends that the following features beactivated to improve TDMA performance:

■ TDMA Full Rate

■ INLA (Interference Look Ahead)

■ HOBIT (Handoff Based on Interference)

■ Automatic Radio Reconfiguration (ARR)

■ Sequential Trunk Hunt

■ TDMA Periodic Best Server Locate

■ Digital Preference for Handoff

■ RF Calltrace for Dual Mode Mobiles

■ Mobile Station Test (MOST)

■ User Talk MOST (UTMOST)

■ Analog Option for Digital Terminations

■ TDMA Digital Locate (FAF not required)

3.2.2 Digital Control Channel (DCCH)

To use advanced features supported by DCCH, the following optional featuresmust be activated:

■ DCCH Short Message Service

■ Authentication

■ Enhanced Registration

■ Automatic Radio Reconfiguration

3.3 Hardware Installation

This section provides instructions for installing the Radio Test Unit (RTU), RTU/TRTU RF Switch Assembly, TDMA Radio Test Unit (TRTU), Digital Radio Units(DRU) and Enhanced DRUs (EDRU) in a Series II cell site. The RTU/TRTU RFSwitch Assembly is used only in the classic Series II cells to switch digital radiotest input and output (I/O) signals to the TRTU. Because this switchingmechanism is built into small cells, such as the Series IIm and Series IImm cells,these cells do not require an RTU/TRTU RF Switch Assembly.

3-2 401-200-112, Issue 11 June 2001



Run Diagnostics. 3Before installing hardware, inspect the cell and run diagnosticsto assure that the cell is functioning optimally. This is done so that if any problemis detected after hardware installation, the problem can be easily isolated to thenewly installed hardware. If the cell does not pass any of the diagnostic routines,the fault should be corrected before hardware installation is performed.

After the cell passes inspection and diagnostics, call processing is inhibited inpreparation for removing power from the cell. Hardware components should notbe installed prior to removing power. After power is removed, individual hardwarecomponents may be installed.

Lucent Technologies recommends that the TRTU or a test EDRU (T-EDRU) beinstalled before the DRUs and EDRUs are installed. A T-EDRU is an EDRU that isprogrammed to operate as a radio test device. The newly installed TRTU (T-EDRU) can then be used to run diagnostic testing on the DRU/EDRUs. BecauseDRUs and EDRUs draw more current than RCUs, upgrading to either DRU orEDRU may require upgrading the radio shelf power capacity. DRU/EDRUs maybe installed individually or all at once. If they are installed individually, rundiagnostics to ensure that each DRU/EDRU is correctly installed before installingthe next DRU/EDRU. Prior to running diagnostics, insert all relevant databasetranslations for the component being tested. (For details on translations, refer toChapter 4.)

3.3.1 Equipment Requirements

The following tools and test equipment are required to perform TDMAimplementation and testing:

■ Terminal

■ Spectrum Analyzer - TDMA compatible

■ Cellular System Monitor (CSM) - TDMA compatible

■ RF Cable Extraction Tool (C996780672)

■ 5/16 Open End Wrench (R-209 or R-418A)

■ 11/32 Open End Wrench (R-3193)

■ 5/16 Nut Driver

Technicians also need additional tools, test cables, test adapters, andtroubleshooting items (e.g., multimeters) not specified here.

! CAUTION:Proper ESD procedures including use of wrist straps must be followed whenhandling circuit packs and assemblies to prevent damage to componentsthat are sensitive to electrostatic discharges.

401-200-112, Issue 11 June 2001 3-3



3.3.2 Pre-Installation Cell Inspection andDiagnostics

The following cell inspection and diagnostic procedures should be performed priorto installing TDMA-specific hardware. Any faults discovered by the diagnosticroutines should be resolved before preceding with hardware installation. Refer toSystem Acceptance and Inspection Manual 401-600-112 for additionalinformation.

Set up dial-up terminal, log on to Mobile Switching Center (MSC), and perform cellinspection and diagnostics as follows:

1. Enter op:cell x (where x is cell number) to check status of cell site equip-ment.

2. Run diagnostics on RTU by entering the following commands:

■ rmv:cell x,rtu;ucl (where x is cell number) to remove the RTU fromservice

■ dgn:cell x,rtu to initiate RTU diagnostics

Make sure that MSC responds “ATP” (All Tests Passed) for RTU before pro-ceeding with installation. If any unit fails the diagnostic test, take the neces-sary corrective action on the failed unit to clear the fault condition.

3. Restore RTU: enter rst:cell x

4. Run diagnostics on one RCU for each Linear Amplifier Circuit (LAC) trans-mitter by entering following commands:

■ rmv:cell x, ra y;ucl (where x is cell number, y is RCU number) toremove specified RCU from service

■ dgn:cell x,ra y to initiate diagnostics on specified RCU

Make sure that MSC responds “ATP” (All Tests Passed) for each RCUtested before proceeding with installation. If any unit fails the diagnostictest, take the necessary corrective action on the failed unit to clear the faultcondition.

5. Restore RCUs to service by entering rst:cell x, ra y; ucl command foreach RCU removed from service in Step 3.

3-4 401-200-112, Issue 11 June 2001



3.3.3 Power Down RCF

! CAUTION:Because of the potential for equipment damage due to shorting pins, powerto cabinet should be turned off.

Call processing should be inhibited and any in-progress calls should becompleted prior to removing power. To power down Radio Control Frame (RCF),do the following:

1. Inhibit call processing, routine diagnostics, and functional test on cell byentering the following commands:

■ inh:cell x,cp (where x is cell number)

■ inh:cell x,rtdiag

■ inh:cell x,ft su

■ inh:cell x,ft lc

2. Wait for all in-process calls to complete [all voice RCUs Tx (Transmit) LEDsOFF].

3. Remove all beacon radios (if equipped) from service by entering the follow-ing code:

■ rmv:cell x,ra y;ucl (where x is cell number and y is radio number ofbeacon)

4. Remove cell data links to/from MSC by entering the following code:

■ rmv:cell x,dl 1

5. On power distribution bay, set all circuit breakers assigned to RCF 0, 1,and 2 (as equipped) to OFF. Wait 30 seconds for capacitor panels in RCFsto discharge.

6. On RCF 0, 1, and 2, set all circuit breakers on ED-2R826-31, G1 (G2)(front bottom of bay) to OFF (as equipped).

3.3.4 RTU/TRTU RF Switch AssemblyInstallation

Note: Small cells, such as the Series IIm and Series IImm, donot require installation of an RTU/TRTU RF Switch Assembly.

The RTU/TRTU RF switch assembly consists of two RF switches that aremounted on an RF switch bracket, an AYD8 radio control board (RCB), andconnecting cables. This RTU/TRTU switch assembly allows the cell controller to

401-200-112, Issue 11 June 2001 3-5



switch between RTU and TRTU for diagnosing voice radios. There are two groupversions of RF switch assemblies: ED3R026-30 G1 and G2 versions.

3.3.4.1 Version G1 Installation

Installation of RTU/TRTU switch assembly, version G1 involves four differenttasks. First, the switch assembly is mounted and secured to the RF switchbracket. Next, the RF coaxial cable assemblies are connected, then the AYD8radio control board (RCB) is installed, and finally the control cables areconnected.

Mounting and Securing RF Switch Bracket

The RF switch bracket consists of two RF switches, designated SW1 (top) andSW2. The two RF switches are mounted on a vertical bracket which is secured tothe 1:12 reference frequency power divider located at the rear of Shelf 4 in RCF 0as shown in Figure 3-1. below.).

Figure 3-1. Mounting RTU/TRTU Switch Assembly, Version G1

Do the following to mount and secure the RF switch bracket:

RF SwitchBracket

1:12 ReferenceFrequency PowerDivider

Cable Tie

Shelf 3

Shelf 4

RF Switch SW1

RF Switch SW2

Primary RCF, Rear View


3-6 401-200-112, Issue 11 June 2001



1. Remove machine screw, washer and nut, securing lower 1:12 referencefrequency power divider to its left supporting bracket. Keep washer and nutfor future use. Screw will be replaced with 1-inch machine screw,C840059133.

2. Re-secure lower 1:12 reference frequency power divider to left supportingbracket with C840059133 1-inch machine screw and original washer andnut.

■ Insert screw through supporting bracket first, then through 1:12reference frequency power divider and attach nut on top of 1:12reference frequency power divider.

■ Leave slack in screw/nut assembly to secure RF switch bracket.

3. Vertically mount RF switch bracket (with jacks facing left as shown inFigure 3-1. ) to left side of 1:12 reference frequency power divider. AlignRF Switch bracket slot with new machine screw and mount below 1:12divider reference frequency power bracket. Tighten machine screw andnut.

4. Using supplied 14-inch cable tie, secure RF switch bracket to cable bracketon Shelf 3 as follows:

a. Run cable tie around top RF switch (SW1) and bottom rear shelfassembly on Shelf 3.

b. Ensure that RF cables are not inside cable tie loop (i.e., run cable tieunder Shelf 3 RF cables).

c. Do not over-tighten cable tie. Cut off any excess cable tie.

5. Clean top of 1:12 reference frequency power divider on Shelf 4, then attachC846983419 CAUTION decal to top of 1:12 reference frequency powerdivider.

Connecting RF Coaxial Cable Assemblies

Coaxial cables to and from the RTU must be extended to reach the RF switches.The RF cable is extended through the coaxial cable housing that couples existingcable with new cable lengths. Do the following to connect the RF coaxial cableassemblies:

1. Remove RTU circuit pack from Shelf 3, position EQL (Equipment Level)156.

2. Using RF cable extraction tool, which is inserted from front of shelf, removeRTU IN (W150) and RTU OUT (W151) coax cables from backplane, posi-tion EQL 156. RTU OUT cable is the top coaxial cable and the RTU INcable is third cable down. Remove cables from rear.

401-200-112, Issue 11 June 2001 3-7



3. Connect coaxial cable housings (C401323167 and C996961256) togetherand secure with two machine screws (C840058283), washers(C802841395), lock washers (C803877455), and nuts (C802108282).Install lock washers next to nuts.

4. Insert RTU IN cable W150 into coaxial cable housing at position A1, andinsert RTU OUT cable W151 into coaxial cable housing (same side asW150) at position A3. Ensure that cables snap into housing.

5. Insert coaxial cable assembly (C846838126) into coaxial cable housing atposition A1 opposite RTU IN cable W150. Then, insert second coaxialcable assembly (C846838126) into coaxial cable housing at position A3opposite RTU OUT cable W151. Ensure that cables snap into housing.

6. Connect SMA jack of A1 cable (W150) to COM jack (center jack) on RFswitch SW2 (bottom).

7. Connect SMA jack of A3 cable (W151) to COM jack (center jack) on RFswitch SW1 (top).

8. Using cable ties and existing cable clamps, neatly dress W150 and W151coaxial cables. Ensure that cables are free of kinks and sharp corners, andclear of rear panels.

9. From rear, insert coaxial cable assembly (C846838142) into backplane ofShelf 3 at position EQL 156, jack Ax (top position). Ensure that cables snapinto backplane.

10. From rear, insert coaxial cable assembly (C846838142) into Shelf 3 back-plane, position EQL 156, jack Ax (third position down). Ensure that cablessnap into backplane.

11. From rear, insert coaxial cable assembly (C846838142) into Shelf 3 back-plane, position EQL 132, Jack A4 (top position). Ensure that cables snapinto backplane.

12. From rear, insert coaxial cable assembly (C846838142) into Shelf 3 back-plane, position EQL 132, Jack A2 (third position down. Ensure that cablessnap into backplane.

13. From rear, insert coaxial cable assembly (C846899276) into Shelf 3 back-plane, position EQL 132, Jack A3 (second position down). Ensure thatcable snaps into backplane.Connect SMA jacks of C846838142 cables toRF switches SW1 and SW2 as follows:

Backplane Shelf 3RF Switch Bracket

■ EQL 156, position A4 (top) RF Switch SW1, Jack J1

■ EQL 156, position A2 (third down) RF Switch SW2, Jack J1

■ EQL 132, position A4 (top) RF Switch, Jack J2

■ EQL 132, position A2 (third down)RF Switch, Jack J 2

3-8 401-200-112, Issue 11 June 2001



14. Verify that cables connected to Jacks J1 and J2 are connected to bottomjacks of RF switches. Jack J1 is away from backplane; Jack J2 is closest tobackplane.

15. Connect right angle SMB jack of cable C846899276 to 1:12 reference fre-quency power divider output, Jack J9 on Shelf 3. If Jack J9 is in use, selectany unused jack.

16. Ensure that six coaxial cables (SMA connectors) are adequately torquedonto switch assembly.

Installing AYD8 Radio Control Board (RCB)

1. Verify that backplane pins on Shelf 3 backplane position EQL 32 arestraight and clean.

2. Insert AYD8 circuit board, with its component side facing left, into Shelf 3backplane at position EQL 132. Plug circuit board into top block of pins.Ensure that board is completely seated and that all pins were captured(i.e., no pins are bent).

3. Ensure that surrounding cables are clear of circuit board.

Connecting Control Cables

1. Remove RTU IN control cable (6-pin by 2-pin connector) from Shelf back-plane, position EQL 156.

2. Remove and discard connector mounting bracket from backplane.

3. Connect RTU INT control cable (6-pin by 2-pin connector) to AYD8 circuitboard, plug P4 (fourth plug down - see Figure 3-2. ). Insert 6-pin by 2-pinconnector with wiring side facing backplane.

Figure 3-2. AYD8 Circuit Board Layout

ComponentSide

Unused

AntennaSelect

To

To RFSwitches

TTo RTUEQL 156LTT

401-200-112, Issue 11 June 2001 3-9



4. Connect 12-pin by 2-pin matrix connector of RTU control cable,C846899342, into Shelf 3 backplane at position EQL 56, pin matrix 034/134 through 045/145 (see Figure 3-3. ). Insert 12-pin by 2-pin connectorwith wiring side facing left.

Figure 3-3. Shelf 3 Backplane Pin Layout at EQL Position 156

5. Connect 3-pin by 2-pin matrix connector of RTU control cable(C846899342) to AYD8 circuit board, plug P1 (third plug down, seeFigure 3-2. .) Insert 3-pin by 2-pin matrix connector with wiring side facingbackplane.

6. Run switch assembly control cable along Shelf 4 cable bracket to left sideof frame, then up to Shelf 3 cable bracket and to AYD8 circuit board.

A1A2A3

A4

TRANSMIT

REFERENCE FREQUENCYRECEIVE DEV 0RECEIVE DEV 1

12-PIN BY 12-PIN MATRIXCABLE CONNECTOR

(PINS 034 - 045, PINS 134 - 145)(Wiring side of connector faces left)

3-10 401-200-112, Issue 11 June 2001



7. Connect 3-pin by 2-pin matrix connector of switch assembly control cableto AYD8 circuit board, plug P5 (fifth plug down, see Figure 3-2. ). Insert 3-pin by 2-pin matrix connector with wiring side facing backplane.

8. Run switch assembly power cable along Shelf 3 toward right side of frame.

9. Connect ORG wire to E9 on backplane power connector and connectORG/WHT to E7. Insure that fuse holder load side is toward switch.

10. Using cable ties and existing cable clamps, neatly dress control cables.Ensure that cables are free of kinks and sharp corners, and clear of rearpanels.

11. Reinsert RTU circuit pack into Shelf 3, EQL 156.

3.3.4.2 Version G2 Installation

The installation of RTU/TRTU switch assembly, C601449036, version G2 involvesfour different tasks. First, the switch assembly is mounted and secured to the RFswitch bracket. Next, the RF coaxial cable assemblies are connected, then theAYD8 radio control board (RCB) is installed, and finally the control cables areconnected.

Assembling RF Switch Assembly

The RF switch assembly consists of two RF switches, designated SW1 (top) andSW2 (bottom). The two RF switches are mounted on a vertical mounting bracketwith fuse and fuse holder. The mounting bracket is then secured to the 1:12 refer-ence frequency power divider located at the rear of Shelf 4 in RCF 0 (Refer toFigure 3-4. ). Do the following to assemble the RF switch assembly:

1. Using the eight C840058572 screws, mount the two C406981324 RF coax-ial switches to C847217098 mounting bracket. Ensure that switches areoriented as shown in Figure 3-4.

2. Retain parts bag for future use in section below, Step 7 (Connecting RFCoaxial Cable Assemblies to RF Switches).

3. Snap fuse holder (C406412791) into mounting bracket so that terminalsare visible from top.

4. Open fuse holder and install two fuses (C406799833) into fuse holder(main and spare).

5. Attach 4A fuse label (C846983419) to mounting bracket just above fuseholder.

6. Attach CAUTION label (C846983419) to front of mounting bracket.

7. Connect and secure connectors SW1 and SW2 on power and controlswitch cable assembly (C846983419) to connector on corresponding RFswitches on RF switch assembly.

401-200-112, Issue 11 June 2001 3-11



Figure 3-4. Mounting RTU/TRTU Switch Assembly, Version G2

8. Using rear slide connector closest to RF switches (+24 volts), connect non-labeled slide connector (orange 22-gauge wire) of switch cable assembly(C847217064) to fuse holder.

9. Using rear slide connector farthest from RF switches (+24 volts), connectunlabeled opposite end of orange 22-gauge wire labeled “E9 RTU SHLF”to fuse holder.

Connecting RF Coaxial Cable Assemblies to RF Switches

1. Connect coaxial cable housings (C401323167 and C996961256) andsecure via two machine screws (C840058283), lock washers(C803877455), and nuts (C802108282). Lock washers are installed next tonuts.

2. Using one of outer holes in coaxial cable housing, insert coaxial cableassembly (C846838126) into coaxial cable housing. Ensure that cablesnap into housing securely.

3. Using another outer hole in coaxial cable housing, insert secondC846838126 coaxial cable into coaxial cable housing. Ensure that cablesnaps securely into housing.

4. Connect SMA jack of first cable from coaxial cable housing to IN jack (cen-ter jack) RF switch SW2 (bottom) of RF switch assembly.


Shelf 3

RF Switch SW1

RF Switch SW2

Primary RCF, Rear View

Mounting

4A Fuse Label

Fuse Holder

CautionLabel

Bracket

3-12 401-200-112, Issue 11 June 2001



5. Connect SMA jack of second cable from coaxial cable housing to IN jack(center jack) RF switch SW1 (top) of RF switch assembly.

6. Connect each SMA jack of the four supplied RF coaxial cables(C847217056) to either terminal 1 or 2 of RF switches SW1 or SW2

7. Place bag saved from Step 2 of previous section over exposed ends of allcoaxial cables connected to RF switch assembly and secure.

Mount RTU/TRTU Switch Assembly

1. On Shelf 3 at rear of RCF, remove the two machine screws, washers andnuts that are securing 1:12 reference frequency power divider to bracket.Retain machine screws for future use and discard washers and nuts.

2. Vertically mount RF switch assembly on top of 1:12 reference frequencypower divider.

3. Secure RF switch assembly to 1:12 reference frequency power divider andits support bracket using two machine screws. Install screws up from bot-tom through support bracket, 1:12 reference frequency power divider andRF switch assembly bracket. RF switch assembly bracket is equipped withpem fasteners, alleviating need for external nuts.

Connecting RF Coaxial Cable Assemblies

1. Remove RTU circuit pack from Shelf 3, position EQL 156.

2. Using RF cable extraction tool, which is inserted from front of shelf, removeRTU IN (W150) and RTU OUT (W151) coaxial cables from position EQL156 on backplane. RTU OUT cable is top coaxial cable; RTU IN cable isthird cable down. Remove cables from rear.

3. Insert RTU IN cable W150 cable into coaxial cable housing that is con-nected to RF switch SW2 (bottom). Ensure that cable is secure in housing.

4. Insert RTU OUT cable W151 cable into coaxial cable housing that is con-nected to RF switch SW1 (top). Ensure that cable is secure in housing.

5. Remove bag covering cable ends from RF switch assembly and discardbag.

6. Connect coaxial cables from indicated RF switch jack to backplane as fol-lows:

RF Switch JackBackplane

RF Switch SW1, Jack 1 EQL 156, position A4 (top)

RF Switch SW2, Jack 1 EQL 156, position A2 (3rd down)

RF Switch (SW1), Jack 2 EQL 132, position A4 (top)

401-200-112, Issue 11 June 2001 3-13



7. From rear, insert coaxial cable assembly (C846899276) into Jack A3 (sec-ond position) on Shelf 3 backplane at position EQL 132. Ensure that cablesnaps securely into backplane.

8. Connect right angle SMB jack of cable (C846899276) to output Jack 9 of1:12 reference frequency power divider on Shelf 3. If Jack J9 is being used,select any unused jack.

Installing AYD8 Radio Control Board (RCB)

1. Verify that backplane pins on Shelf 3 backplane position EQL 32 arestraight and clean.

2. Insert AYD8 circuit board with its component side facing left into Shelf 3backplane at position EQL 132. Plug circuit board into top block of pins.Ensure that board is completely seated and that all pins were captured(i.e., no pins are bent).

3. Ensure that surrounding cables are clear of circuit board.

3.3.4.3 Install Control Cables

1. Remove RTU IN control cable (6-pin by 2-pin connector) and if equipped,RTU surge protector (9822DD) from Shelf 3 backplane at position EQL156. Remove and discard connector mounting bracket from backplane.

2. Install surge protector removed in Step 1 at connector P4 on AYD8 circuitboard, which is fourth connector down on component side facing back-plane.

3. Connect RTU INT control cable (6-pin by 2-pin connector) to surge protec-tor with wiring side facing left.

4. Ensure that surge protector ground wire is connected to terminal E11 onShelf 3 backplane.

5. Dress control cable to ensure that it does not interfere with rear cover whenreinstalled.

6. Connect RTU control cable (12-pin by 2-pin connector, C846899342) to pinmatrix consisting of pins 034/134 through 045/145 on Shelf 3 backplane atposition EQL 156. (Refer to Figure 3-2. ) Insert 12-pin by 2-pin connectorwith wiring side facing left.

7. Connect RTU control cable (3-pin by 2-pin connector, C846899342) to con-nector P1 on AYD8 circuit board (third plug down). Insert 3-pin by 2-pinconnector with wiring side facing backplane.

8. Connect connector P5 of switch cable assembly (C847217064) to AYD8circuit board, plug P5 (fifth plug down). Insert connector P5 with wiring sidefacing backplane.

3-14 401-200-112, Issue 11 June 2001



9. Using cable ties and existing cable clamps, neatly dress control cables.Ensure that cables are free of kinks and sharp corners, and clear of rearpanels.

3.3.4.4 Connecting DC Power Cable

1. Connect E7 - RTU SHELF connector (white-orange, Return) of switchcable assembly (C847217064) to Power connector E7, which is locatedbetween EQL 024 and EQL 012 on Shelf 3 backplane.

2. Connect E9 - RTU SHLF connector (orange, +24 volts) of switch cableassembly (C847217064) to Power connector E9, which is located betweenEQL 024 and EQL 01 on Shelf 3 backplane.

3. Using cable ties and existing cable clamps, neatly dress DC power cable.Ensure that cable is free of kinks and sharp corners, and clear of rear pan-els. Ensure that fuse can be replaced without having to cut any cable ties.

4. Reinsert RTU circuit pack into Shelf 3, EQL 156.

5. Make sure all connections are properly secured.

3.3.5 Radio Shelf Power Upgrade

The radio shelf power delivery system may require upgrading as a function of thenumber of DRUs and EDRUs installed.

3.3.5.1 Installing DRUs.

When four or more DRUs are to be installed on an RCU shelf, replace +5-voltpower converter unit (PCU) 415AA with 415AC PCU (C106761877) on each radioshelf where four or more DRUs are to be installed. If required, then replace the+5V CONV circuit breaker with a 15A circuit beaker using the procedure given inParagraph 3.3.6 .

3.3.5.2 Installing EDRUs

Power upgrade required for installing EDRUs is a function of the number ofEDRUs to be installed, and the cabinet type in which the EDRUs are installed.Power to the radio shelf is supplied by +5-volt and +12-volt power converter units(PCUs). Power upgrade involves replacing +5-volt and +12-volt PCUs and theircorresponding circuit breakers with PCUs and circuit breakers having highercurrent capacity.

401-200-112, Issue 11 June 2001 3-15



3.3.5.2.1 Series II Classic Radio Frame

! WARNING:Earlier versions of Series II Classic Radio frames , identified by having 7-pairs of power feeders, and eariler Growth Radio Channel Frames,identified by having 6-pairs of power feeders, cannot support more than 8EDRUs per shelf . The internal frame wiring in the older vintage frames isnot adequate to safely support more than 8 EDRUs per shelf and, if thiswarning is ignored, may result in a serious fire hazard. It is permissible toequip analog RCUs in the other four slots.

Two newer Series II classic radio frames are supported; Series II-01and Series II-02. These frames are identified by having 2-pairs of number 2 AWG wire powerfeeders and two 100-A circuit breakers. Regardless of the cabinet type and thenumber of EDRUs to be installed, the +5-volt PCU 415AA should be replaced with+5-volt PCU 430AB.

The two primary difference in the radio shelf power supply system between thetwo frame types are the current capacity of the 5-volt circuit breaker and the +12-volt PCU.

When to Replace +5V CONV Circuit Breaker. 3The +5-volt (+5V CONV) circuitbreaker in the Series II-01 frame is rated at 12.5A and will permit the operation ofup to eight EDRUs and two analog RCU. If nine or more EDRUs are to beinstalled, replace the +5V CONV circuit breaker with a 25A circuit beaker usingthe procedure given in Paragraph 3.3.6 .

The +5V CONV circuit breaker in the Series II-02 frame is rated at 15A and willpermit the operation of up to nine EDRUs. If ten or more EDRUs are to beinstalled, replace the +5V CONV circuit breaker with a 25A circuit beaker usingthe procedure given in Paragraph 3.3.6

When to Replace +12-Volt PCU. 3The +12-volt PCU (419AA), installed in theSeries II-01 frame, permits the operation of up to eight EDRUs and two analogRCU. If nine or more EDRUs are to be installed, replace 12-volt PCU (419AA)with PCU (419AE).

The 12-volt PCU (419AC), installed in the Series II-02 frame, permits theoperation of up to eight EDRUs. If nine or more EDRUs are to be installed,replace 12-volt PCU 419AC with PCU 419AE.

3.3.5.2.2 Series IIm Cabinet

The Series IIm primary cabinet permits a maximum of eight transmit radios, tworeceive only locate radios, and two test radios. When the cell is configured tosupport AMPS and TDMA, one locate radio must be an RCU and the other locate

3-16 401-200-112, Issue 11 June 2001



radio may be a locate EDRU (L-EDRU). The radio test unit (RTU) for the RCUmust be located in radio shelf slot 21, and the TRTU (T-EDRU) must be located inslot 22.

Two Series IIm primary and growth cabinet types are supported, which aredelineated by the cabinet production date. Cabinets manufactured prior toDecember 1995 provide 20A service to its radio shelf, and cabinets manufacturedafter this date provide 30A service to its radio shelf. Regardless of the cabinetmanufactured date and the number of EDRUs to be installed, the +5-volt PCU415AC should be replaced with +5-volt PCU 430AB.

A single circuit breaker, rated at either 20A or 30A depending on the cabinetmanufactured date, supplies power to the radio shelf 5-volt and +12-volt PCU. Ifthe 20A service in the pre-December 1995 manufactured cabinet requiredupgrading to 30A service, the feeder line to the new 30A circuit breaker must bechanged from a 12 AWG wire to twin 10 AWG feeders.

When to Replace +5V CONV Circuit Breaker. 3The 20A RCU circuit breaker(CB1) in the Series IIm primary or growth cabinet permits the operation of up tosix EDRUs and two analog RCU. If seven or more EDRUs are to be installed,replace the +5V CONV circuit breaker with a 30A circuit beaker using theprocedure given in Paragraph 3.3.6 .

When to Replace +12-Volt PCU. 3The 12-volt PCU, 419AC, in the Series IImprimary or growth cabinet permits the operation of up to nine EDRUs. If ten ormore EDRUs are to be installed, replace 12-volt PCU 419AC with PCU 419AE.

3.3.5.2.3 Series IImm Cabinet

The Series IImm primary or growth cabinet permits a maximum of 19 transmitradios, two receive only locate radios, and two test radios. When the cell isconfigured to support AMPS and TDMA, one locate radio must be an RCU andthe other locate radio may be a locate EDRU (L-EDRU). The radio test unit (RTU)for the RCU must be located in radio shelf slot 21, and the TRTU (T-EDRU) mustbe located in slot 22.

Two Series IImm primary and growth cabinet types are supported, which aredelineated by the cabinet production date. Cabinets manufactured prior toDecember 1995 provide 20A service to its radio shelf, and cabinets manufacturedafter this date provide 30A service to its radio shelf. Regardless of the cabinetmanufactured date and the number of EDRUs to be installed, the +5-volt PCU415AC should be replaced with +5-volt PCU 430AB.

A single circuit breaker, rated at either 20A or 30A depending on the cabinetmanufactured date, supplies power the radio shelf 5-volt and +12-volt PCU. If the20A service in the pre-December 1995 manufactured cabinet required upgradingto 30A service, the feeder line to the new 30A circuit breaker must be changedfrom a 12 AWG wire to twin 10 AWG feeders.

401-200-112, Issue 11 June 2001 3-17



When to Replace +5V CONV Circuit Breaker. 3The 20A RCU circuit breaker(CB1) in the Series IIm cabinet permits the operation of up to six EDRUs and twoanalog RCUs. If seven or more EDRUs are to be installed, replace the +5V CONVcircuit breaker with a 30A circuit beaker using the procedure given in Paragraph3.3.6 .

When to Replace +12-Volt PCU. 3The 12-volt PCU(419AC), installed in the SeriesIIm cabinet permits the operation of up to six EDRUs. If seven or more EDRUs areto be installed, replace 12-volt PCU 419AC with PCU 419AE.

3.3.6 Power Converter Unit and Circuit BreakerReplacement

Replacement of the +5-volt PCU and associated circuit breaker on J41660A-1and J41660B-1 bays are required for each radio shelf when four or more DRUs ormore then eight EDRUs are to be installed on the shelf. If power supply upgrade isnot necessary, proceed to next section.

To replace +5 volt circuit breaker on RCF ED-2R826-31 Circuit Breaker Panel(bottom of bay), perform the following:

1. On power distribution bay, set all circuit breakers assigned to the RCF 0, 1,and 2 (as equipped) to OFF.

2. Set all circuit breakers on RCF circuit breaker panel to ON. Wait 30 sec-onds for any residual charge in RCF capacitor panel to discharge, then setbreakers to OFF.

3. Remove four machine screws from front four corners of circuit breakerpanel and remove top cover. It may be necessary to clip (remove) cableties that secure power wires in order to provide additional installationspace.

4. Remove two machine screws from shelf +5V CONV circuit breaker for shelfbeing modified.

5. Remove circuit breaker from panel. Remove two 5/16 nuts from circuitbreaker power terminals and disconnect power wires.

6. Install new 15A circuit breaker, for DRU installation or 25A circuit breakerfor EDRU installation, by reversing the sequence in which the circuitbreaker was removed.

7. Ensure that circuit breaker is oriented correctly, and that line and loadpower wiring is correctly replaced on circuit breaker.

8. Ensure that circuit breaker power terminal nuts are adequately torqued.

9. Using an 1/8-inch stamp and white ink, stamp front, side (90 degrees) ofreplaced breaker, 15A or 25A, as applicable.

10. Replace all required circuit breakers on panel being modified.

3-18 401-200-112, Issue 11 June 2001



11. Reinstall top cover on panel; reinstall circuit breaker panel in RCF.

12. Ensure that power wiring is not kinked or pinched when sliding panel backinto RCF.

13. Secure panel using four machine screws.

14. Re-install cable ties that were previously removed.

15. Repeat this procedure on all RCF bays as required.

3.3.6.1 Replace Shelf Designation Labels(Customer Option)

1. Replace two shelf designation strips per shelf to include TDMA circuitpacks:

■ Front label on shelf designation bar identifies circuit packnomenclature and slot numbering.

■ Back label on shelf designation bar identifies circuit pack locationsand associated ED number.

2. Attach new shelf designation labels directly over original labels on RTUShelf 3 (RCF 0) and all RCU shelves in the cell under test as follows:

■ RCF 0 Shelf 0 (RCC shelf)

■ FRONT No Change

■ BACK No Change

■ RCF 0 Shelf 1, 2 and RCF 1 Shelf 4, 5 (CAT shelf)

■ FRONT C846908291

■ BACK C846908309

■ RCF 0 Shelf 3 (RTU shelf)

■ FRONT C846909489

■ BACK C846909497

■ All other RCU shelves

■ FRONT C846908069

■ BACK C846932978

3.3.7 Install TRTU and DRU(s)

This section provides installation instructions for the TRTU and the DRU(s).Diagnostic testing should be performed on each installed modular component(TRTU and DRU). Although a cell may have DRUs and EDRUs installed, the

401-200-112, Issue 11 June 2001 3-19



installation of TRTU and a T-EDRU are mutually exclusive. That is, a cell canhave either a TRTU or a T-EDRU installed, but not both.

The diagnostic test for the TRTU should be run before testing the DRU(s). Thediagnostic test for the DRU(s) may be run separately after each component isinstalled, or collectively after a group of components are installed.

1. In Series II Classic cells, insert TRTU (ED 2R921-30) into RCF 0, Shelf 3(EQL 132), Slots 11 and 12. In Series IIm and Series IImm cells, insertTRTU in slot 22 of radio shelf in primary cabinet.

2. Insert DRU(s) (ED 2R920-30) into required slots of RCF(s). DRUs requiretwo shelf slots. Lucent Technologies recommends equipping these radiosin even numbered shelf slots only (i.e., positioned in slots 2-3, 4-5, 6-7,etc.).

If four or more DRUs are to be installed in a single RCU shelf, verify thatshelf is equipped with 415AC +5 volt power supply and corresponding 15amp circuit breaker (refer to Paragraph 3.3.7 ).

3. Verify that RCF penthouse is wired correctly for each DRU installed.

3.3.8 Install T-EDRU and EDRU(s)

This section provides installation instructions for the T-EDRU and the EDRU(s).Diagnostic testing should be performed on each installed modular component (T-EDRU and the EDRU). Although a cell may have DRUs and EDRUs installed, theinstallation of TRTU and a T-EDRU are mutually exclusive. That is, a cell canhave either a TRTU or a T-EDRU installed, but not both.

The diagnostic test for the T-EDRU should be run before testing the EDRU(s).The diagnostic test for the EDRU(s) may be run separately after each componentis installed, or collectively after a group of components are installed.

1. In Series II Classic cells, insert T-EDRU (44WR8) into RCF 0, Shelf 3 (EQL132), Slot 11. In Series IIm and Series IImm cells, insert T-EDRU in slot 22of radio shelf in primary cabinet. Then refer to Paragraph 3.3.9 .

2. Insert EDRU(s) into required slots of RCF(s) or the radio shelf in the SeriesIIm/IImm cabinet. When installing in the Series IIm/IImm cabinet, EDRUs(44WR8) require two shelf slots. Lucent Technologies recommends equip-ping these radios in even numbered shelf slots only (i.e., positioned in slots2-3, 4-5, 6-7, etc.).

If five or more EDRUs are to be installed in a radio shelf or a single RCUshelf, verify that shelf power supply system is upgraded in accordance withthe information given in Paragraph 3.3.5 .

3-20 401-200-112, Issue 11 June 2001



3. Verify that RCF penthouse is wired correctly for each EDRU installed.

3.3.9 Test EDRU (T-EDRU) Personality

A test personality for the EDRU radio has been developed in Cell Release R13.When programmed with the test personality, the radio, which is referred to as a T-EDRU, can be used to replace the TRTU. The exception to the T-EDRU usabilityis that the T-EDRU cannot be used to test DRU radios. In some cases the T-EDRU, which occupies half of the radio shelf space of the TRTU, has theadvantage of freeing a slot space for another EDRU radio. To replace the TRTUwith a T-EDRU, the TRTU must first be removed from service. Then the TRTU isphysically replaced with a T-EDRU and the test personality is downloaded into theT-EDRU radio.

The T-EDRU is placed in the left hand slot of the two slots occupied by the TRTU.The test radio output must be +4 dBm, but the T-EDRU unadjusted output poweris +10 dBm. A front panel adjustment can vary the output power by +3 to –4 dB.To accommodate this difference, the cell software will automatically lower the T-EDRU output power by one VRAL step for a difference of -4dB. This will changethe T-EDRU output to +6 dBm. A manual calibration procedure is then required toset the T-EDRU output level to +4 dBm. This calibration procedure must beperformed any time a T-EDRU is placed into service.

! CAUTION:Any time a T-EDRU is installed or replaced for any reason, the power settingprocedures in this section must be performed BEFORE allowing theT-EDRU to perform diagnostics.

T-EDRU Replacement Procedure 3

The following procedure is performed at the cell site to replace a TRTU or adefective T-EDRU with a functioning T-EDRU. The cell site technician should beequipped with a PC having a dial-in connection to the OMP. If a PC dial-inconnection to the OMP is not available, the cell site technician should be in verbalcontact with an operator at the MSC to enter and read commands and messagesfrom the OMP.

To remove a TRTU or a defective T-EDRU, perform the following:

1 Remove TRTU or a defective T-EDRU from service by entering thefollowing at the OMP (where a is the cell number):

rmv:cell a, trtu;ucl <Enter>

ECP responds with:

IP all specified cell ACT

401-200-112, Issue 11 June 2001 3-21



M 30 RMV:CELL a TRTU, COMPLETEDDEVICE - tty+

MM/DD/YY HH:MM:SS #nnnnnn

*30 OP:CELL a TRTU, MANUAL, RMVDDEVICE - tty+


2. Remove TRTU or a defective T-EDRU from radio shelf and insert newEDRU.

3. On the ceqcom2 RC/V form, verify that the T-EDRU equipage is as follows:

■ TDMA RTU -Status (Indicating that the primary cabinet is equippedwith a T-EDRU radio). Set to e.

■ TDMA RTU- Slot (Indicating radio shelf slot location).

■ TDMA RTU - DVCC (Specifies digital verification code of cell).Generally the cell number is used except for 3, 45, 136, and 162.

■Radio type:edru

4. Download new generic software for T-EDRU by entering the following atthe OMP:

dnld:cell a trtu <Enter>

ECP responds with:

PF

A 34 REPT:CELL a NVM UPDATE MAIN CONTROL-LER COMPLETED

UNIT SUCCESSFULLY UPDATE TRTU

DEVICE - tty+


5. Diagnose the T-EDRU to ensure that it is working properly by entering thefollowing at the OMP:

dgn:cell a, trtu <Enter>

ECP responds with:


ALL TESTS PASSED

6. On T-EDRU front panel, set TX switch to OFF.

7. Enter the follow configuration commands on OMP:

3-22 401-200-112, Issue 11 June 2001



■ cfr:cell a, trtu;start <Enter>

ECP responds with:


M 30 CFR:CELL a TRTU, ALL WENT WELLDEVICE - tty+

■ cfr:cell a, trtu;config 150:chanl e <Enter>

Note:Channel number must be specified to configure T-EDRU

ECP responds with:


M 30 CFR:CELL a TRTU, ALL WENT WELLDEVICE -tty+

■ cfr:cell a, trtu;xmit 300 <Enter>

ECP response with:


M 30 CFR:CELL a TRTU, ALL WENT WELLDEVICE -tty+

T-EDRU Power Calibration 3

1. Set up and calibrate power meter to measure power in the +4 dBm range.

2. Disconnect cable which carries T-EDRU transmitter input at front panel ofSwitch Panel where the test radio gains access to the transmit and receivepaths – the RTU Switch Panel in a Series II classic cell, or the MATRSP inthe PCS TDMA Minicell. The jack designation varies depending on the typeof cell. For a Series II classic cell, this is J1; for a PCS TDMA Minicell, thisis J3 on the front of the RSP. Using appropriate adapter, connect powermeter sensor to the cable.

3. Estimate the length of cable in feet from the back of the T-EDRU to thepoint where the power meter is connected to the cable. Multiply the cablelength in feet by 0.2 dB to estimate the cable loss. Subtract the resultingquantity from +4dBm. This will be the desired reading on the power meterwhen the T-EDRU power is adjusted in Step 5, below. For example, if thecable length for is 4.5 feet, so the estimated cable loss is 0.9 dB. Becausethe T-EDRU output must be set to +4 dBm, the desired measured output atthe power meter is +4 dBm – 0.9 dB = +3.1 dBm.

4. Set TX switch on T-EDRU front panel to AUTO. TX green LED should light.

401-200-112, Issue 11 June 2001 3-23



5. Using potentiometer on T-EDRU front panel, adjust radio transmit outputpower to the power level determined in Step 3.

6. Set TX switch on T-EDRU front panel to OFF. TX green LED should go off.

7. Remove power meter from cable and reconnect cable on switch panel.

8. Enter the following on the OMP to turn off the configuration command:

■ stop:cfr;cell a, trtu <Enter>

ECP responds with:


M 35 CFR:CELL a ABORTED, OVERRIDE HIGHERPRIORITY

DEVICE - tty+MM/DD/YY HH:MM:SS #nnnnnn

9. Set TX switch on T-EDRU front panel to AUTO. TX green LED should light.

10. Restore T-EDRU to operational status by entering either command on theOMP:

init:cell a:sc <Enter>OR

rst:cell a, trtu;ucl <Enter>

11. Restore T-EDRU to service by entering the following at the OMP:

rst:cell a, trtu;ucl <Enter> (to restore the testradio)

ORinit:cell a:sc <Enter> (to restore all radios)

3.0.1 Restore Cell

After hardware is installed, the cell must be powered up and rebooted as follows:

3.0.1.1 Power Up Cell

1. On power distribution bay, set all circuit breakers assigned to RCF 0, 1,and 2 (as equipped) to ON.

2. On RCF 0, 1, and 2, set all circuit breakers on ED-2R826-31, G1 (G2)(front bottom of bay) to ON (as equipped).

3-24 401-200-112, Issue 11 June 2001



3. Using a multimeter, check 5V test point on all newly installed 415AC or430AB power units. Voltage reading must be between +4.80 to +5.20 voltsDC.

3.0.1.2 Boot Cell

1. Restore cell data links by entering the following commands:

■ rst:cell x,dl 0;ucl where x is cell number

■ rst:cell x,dl 1;ucl

2. MSC automatically boots cell under test. Verify by entering the followingcommand:

■ op:cell x where x is cell number

3. Wait for boot process to complete (approximately 5 minutes whenequipped with 56 kbps datalinks, and 20 minutes with 9.6 kbps datalinks).When complete, each RCU displays its channel number. Make sure thatRCFs are alarm free.

3.0.2 Modify RC/V Translations

The implementation process requires modifying RC/V translations to supportTDMA and, if applicable, DCCH. Translations fall into two categories: operationaland performance. For details, refer to Chapter 4.

■ Operational translations provide data on physical system configuration,including DRU/EDRU location in the frame, cell trunk memberassignments, out-of-service limits, etc.

■ Performance translations provide information the system uses in callprocessing such as MAHO list, signal level thresholds, timers, etc.

Translation information is provided as follows:

■ To implement DTC functionality, enter the DTC Database Settings(translations) detailed in Chapter 4.

■ To implement DCCH functionality, enter the DCCH Database Settings(translations) detailed in Chapter 4.

3.1 Complete the Installation Process

After hardware has been installed and all relevant RC/V modifications entered,the following steps are needed to complete the installation process:

■ Download cell site generic

■ Test hardware

401-200-112, Issue 11 June 2001 3-25



■ Test RF power parameters

■ Allow call processing

3.1.0.1 Download Cell Site Generic

After all the hardware is installed and the translations are entered, the followingcell site download (load reboot) procedure is performed to change the cell generic(cell form) and download the translation data into cell site controllers (CSC 0 andCSC 1) and radios.

All recommended database translations should be implemented before bootingthe TDMA generic. Follow cell site download procedures provided in Cell SiteRelease Information document provided with cell site generic software.

3.1.0.2 Hardware Testing

When all of the equipment are installed, test dignostic should be run by the TRTUor T-EDRU and each DRU and EDRU. Since the TRTU and T-EDRU are mutuallyexclusive, the same commands used to test the TRTU are used to test the T-EDRU.

Test TRTU or T-EDRU

1. Verify TRTU or T-EDRU status, as follows:

■ op:cell x,trtu (where x is cell number)

2. If TRTU or T-EDRU is ACTIVE, remove TRTU or T-EDRU from service, asfollows:

■ rmv:cell x,trtu;ucl (where x is cell number)

3. Diagnose TRTU or T-EDRU, as follows:

■ dgn:cell x,trtu (where x is cell number)

4. Verify that TRTU or T-EDRU passed diagnostics via “ATP” messagereturned from MSC.

The MSC must respond “ATP” for the TRTU or T-EDRU.

5. Restore TRTU or T-EDRU, as follows:

■ rst:cell x,trtu;ucl

Test DRU(s) and EDRU(s)

1. Verify status of each DRU and EDRU, as follows:

■ op:cell x,ra y (where x is cell number and y is radio number)

3-26 401-200-112, Issue 11 June 2001



2. If DRU or EDRU under test is ACTIVE, remove DRU or EDRU from ser-vice, as follows:

■ rmv:cell x,ra y;ucl (where x is cell number and y is radio number)

3. Diagnose DRU or EDRU, as follows:

■ dgn:cell x,ra y (where x is cell number and y is radio number)

MSC must respond “ATP” for DRU and EDRU under test, and “ATP” for thethree trunk group members associated with this radio.

4. Restore DRU or EDRU, as follows:

■ rst:cell x, ra y;ucl

Repeat DRU and EDRU diagnostics procedure for all other newly installedDRUs and EDRUs.

3.1.0.3 RF Measurements

This section describes the RF measurements to be performed on all newlyinstalled DRUs and EDRUs in the cell under test. The DRU/EDRU RFmeasurements detailed in this section are different from the RF measurementsperformed on AMPS radios. Power output adjustments, adjacent channel andmodulation accuracy verification are performed on each radio.

Power Output Verification in Series II Cells

1. Measure output power at J3 jack on RTU switch panel.

■ Use test set capable of measuring MEAN TRANSMITTER POWER.

■ Do not use peak-detecting power meter/test set.

2. Verify that cell RCU equipage per transmitter (LAC) agrees with Cell SiteTest Record Sheets.

■ Update Cell Sites Test Record Sheet with added DRU/EDRUs.

■ Verify that added units to each transmitter (LAC) do not exceed theLAC maximum allowable power output.

If Cell Site Test Record Sheet is inaccurate or missing, perform power verificationfor all radios in cell to verify that transmitter (LAC) maximum allowable outputpower is not exceeded.

Power Output Adjustment

Each DRU or EDRU consumes 1.5 times the amount of available LAC outputpower as does an RCU. Adding DRU/EDRUs to the LAC will yield less total outputpower per radio than if only RCUs are used.

401-200-112, Issue 11 June 2001 3-27



1. Obtain J3 value for transmitter (LAC) under test from cell site data sheets.

2. Connect test cable of known loss from test set (i.e., spectrum analyzer orCSM) to J3 jack on RTU switch panel. Compensate for any cable losseswhen performing this measurement.

3. Configure DRU/EDRU under test for full power output, as follows:

■ cfr:cell x,ra y;start (where x is cell number and y is radio number)

■ cfr:cell x,ra y;config 150

■ cfr:cell x,ra y;xmitc 300

■ cfr:cell x,ra y;vradpc 357

After each MSC command input, wait for MSC response message, ALLWENT WELL.

4. Adjust potentiometer on front of DRU/EDRU until MEAN TRANSMITTEROUTPUT POWER is displayed on test set. DRU/EDRU outputs a modu-lated signal under CFR commands.

Adjacent Channel Power

Adjacent Channel Power specifies and measures adjacent, first and secondalternate channel powers of channel under test to verify that the effects of theDRU/EDRU modulation format are within specifications.

The measurement specifies that a frequency-selective mean power measurementis performed at frequency offsets from the channel under test of +/- 30kHz(adjacent), +/- 60 kHz (1st alternate), and +/- 90 kHz (2nd alternate). There are atotal of six measurements. The exact characteristics of the frequency selectivemeasurement are defined in the IS-54 specification.

The test set must be capable of performing the measurement as described in theSection above. The following references to “TDMA Test Set” imply this capability.

Connect TDMA Test Set to J3 jack on RTU Switch Panel and set up test set tomeasure adjacent channel power. The DRU/EDRU under test must meet thefollowing requirements:

■ Adjacent channel power (+/ 30kHz) is a minimum of 26dB belowmean output power.

■ First alternate channel power (+/- 60 kHz) is a minimum of 45dBbelow mean output power.

3-28 401-200-112, Issue 11 June 2001



■ Second alternate channel power (+/-90kHz) is a minimum of 60dBbelow mean output power when the channel output power is greaterthan 50 watts. When the channel output power is less than or equalto 50 watts, the second alternate channel power must be a minimumof 45 dB below mean output power or -13dBm, whichever is lower.

Modulation Accuracy (Error Vector Magnitude)

Modulation Accuracy is a measurement of the difference between the transmittedsignal and the ideal signal. This test measures the RMS modulation accuracy ofthe DRU/EDRU and requires a special test set capable of performing thismeasurement.

The test set must be capable of performing the measurement as described in theSection above. The following references to “TDMA Test Set” imply this capability.

1. Connect test set to J3 jack on RTU switch panel. DRU/EDRU under testmust meet the following requirement:

■ RMS modulation accuracy is less than 12.5%.

2. Terminate DRU/EDRU under test as follows:

■ cfr:cell x,ra y;xmitc 301

■ stop:cfr;cell x,ra y (where x is cell number and y is radio number)

3. Test all additional newly installed DRU/EDRUs assigned to transmitter(LAC) under test using procedures described above (Power Output, Adja-cent Channel Power, Modulation Accuracy).

4. Test additional transmitters (LACs) using procedures described above(Power Output, Adjacent Channel Power, Modulation Accuracy).

5. Disconnect test equipment from cell. Re-terminate RTU switch panel J3jack.

6. Restore radio to service.

3.1.0.4 Allow Call Processing

1. On cell under test, allow functional tests and call processing by entering thefollowing commands:

■ alw:cell x,ft su (where x is cell number)

■ alw:cell x,ft lc

■ alw:cell x,rtdiag

■ alw:cell x,aud

■ alw:cell x,cp

2. On cell under test, verify that setup RCUs are transmitting (Tx LED ON).

401-200-112, Issue 11 June 2001 3-29



3. Using cellular phone, place call on cell under test.

■ Verify that an RCU is selected (RCUs Tx LED ON) from cell undertest.

■ Verify that call is set up in a reasonable amount of time (less than 10seconds) and that both directions of voice channel are clear.

3.2 Receive Path Gain Measurements

This section describes receive path gain measurements for TDMA. Receive pathgain (RPG) measurements are performed for each receiver antenna groupequipped with DRU/EDRUs. This procedure is provided to aid in assessing theoverall gain of the receive path. It is not required as part of the installation. RPGinformation is recorded in the Cell Site Test Record Sheet.

3.2.1 Receive Path Gain

Perform receive path gain measurement on all receiver antenna groups (if notpreviously done), as follows:

1. Set up CSM (duplexer mode) to inject signal at directional coupler J1(J4 -duplexer) port. Read output signal at cable feeding input of receive diver-sity 1:9 power divider (RCF) on receiver under test.

2. Perform receive path gain measurement as follows:

■ Measure path gain for diversity 0 receive antenna from hatchplateend of foam jumper cable to input of the diversity 0,1:9 power divider(RCF).

■ Measure path gain for diversity 1 receive antenna from hatchplateend of foam jumper cable to diversity 1, 1:9 power divider.

■ Average the two measured path gains.

■ To determine receive path, subtract 15db (average loss from 1:9power divider to each RCU receiver input) from averaged pathgains.

Since receive cable lengths (AIF 1:6 power divider to RCF 1:9 powerdivider) are equal, it is necessary to measure only one of the possible sixreceiver cables per receive antenna group. Receive Path Gains from thehatchplate to the 9:1 should be in the range of 27-35 dBm.

3. Record results on Site Test Record Sheet. For accurate MAHO calcula-tions, use these values.

3-30 401-200-112, Issue 11 June 2001



The RPG translation value is used to compensate for gain variations in thephysical receive path of each sector. Sector values must be treated consis-tently throughout the system because they are used during handoff.

401-200-112, Issue 11 June 2001 3-31



3-32 401-200-112, Issue 11 June 2001



TDMA and DCCH Translations


4.2 DTC Database Settings 4-1


4.2.1.1 Max. No. of Mobile Requested Call Mode Changes 4-2

4.2.1.2 Mobile Assisted Handoff Bias - TDMA 4-2


4.2.1.4 TDMA Test Mode Active 4-3

4.2.1.5 Differential Billing for Digital and Analog Time 4-3

4.2.1.6 Append Basic Digital Module to the AMA Record 4-3








4.2.1.14 Number of Downlink Measurement for ValidDownlink List (NDM)4-6

4.2.1.15 Downlink Measurement Interval (DMI) 4-6

4.2.1.16 Maximum Candidate Channel List Length (MCCLL) 4-64-6

4-6

4-6

4-5

4-5

4-5

4-4

4-4

4-4

4-3

4-3

4-3

4-2

4-2

4-2

4-2

4-1

4-1

June 2001 4-1

Contents

4.2.1.17 Adjacent Channel Use on Adjacent Sector Allowed 4-7



4.2.1.20 Maximum Interference Threshold for Call Setup -Uplink (dB) 4-8

4.2.1.21 Maximum Interference Threshold for Call Setup -Downlink (dB) 4-8

4.2.1.22 Maximum Interference Threshold for handoff -Uplink (dB) 4-8

4.2.1.23 Maximum Interference Threshold for handoff -Downlink (dB) 4-8

4.2.1.24 Area Wide Test Channel (AWTC) - Cellular 4-8


4.2.2.1 Antenna Face Trunk Group List 4-9

4.2.2.2 Cell Generic - Version Name 4-9

4.2.2.3 Cell Generic - R5 Compatible 4-9

4.2.2.4 IS-54B Allowable Call Mode Override 4-9

4.2.2.5 Number of Simultaneous NVMs - TDMA 4-10

4.2.2.6 Voice Out of Service Limit -(%) TDMA 4-10


4.2.2.8 Cell Site Optional Features 4-11

4.2.2.9 ARR is Available for: Beacon Radio 4-11

4.2.2.10 ARR is Available for: Locate EDRU(L-EDRU) Radio 4-12

4.2.2.11 Authentication is Available on: AnalogControl Channel 4-12

4.2.2.12 Number of Time Slots for DVCC Presence 4-12

4.2.2.13 DVCC Detection Timeout Time Slots 4-12

4.2.2.14 Bit Error Rate Threshold (%) 4-13

4.2.2.15 Frame Error Rate Threshold (%) 4-13

4.2.2.16 Mobile Assisted Handoff Bias 4-13

4.2.2.17 Mobile Requested Call Mode Change 4-14

4.2.2.18 DVCC Verification Active 4-14

4.2.2.19 Digital Locate Radio Equipage (Read-Only) 4-144-14

4-14

4-14

4-13

4-13

4-13

4-12

4-12

4-12

4-12

4-11

4-11

4-11

4-10

4-10

4-9

4-9

4-9

4-9

4-9

4-8

4-8

4-8

4-8

4-8

4-7

4-7

4-7

4-2 401-200-112, Issue 11 June 2001


Contents




4.2.2.23 Network Transmission Level (dB) Rx for DRU/EDRU 4-15

4.2.2.24 Network Transmission Level (dB) Tx for DRU/EDRU 4-16

4.2.2.25 Handoff at Optimum Power - TDMA 4-16

4.2.3 NNBR (Network Neighbor) Form 4-16

4.2.3.1 SMS Capable 4-16

4.2.3.2 SMS Destination MC 4-16

4.2.3.3 Destination MC SSN 4-17

4.2.3.4 Handoff/Setup Optimum Power - TDMA 4-17



4.2.4.2 TDMA Measurement Processing Interval 4-17

4.2.4.3 TDMA RTU DVCC 4-18


4.2.5.1 Digital Color Code 4-18

4.2.5.2 Color Codes - 1st TDMA Supervisory Digital (SDCC) 4-18

4.2.5.3 Color Codes - 2nd TDMA Supervisory Digital (SDCC) 4-19


4.2.6.1 TDMA Voice Radio Attenuation Level 4-19

4.2.6.2 TDMA Fade Timer 4-20

4.2.6.3 Cell Site Attenuation Code 4-20

4.2.6.4 Two Branch Intelligent Antennas Active for DCCH 71) 4-21

4.2.6.5 FLCA Monitoring 4-21

4.2.6.6 Channel Set 4-21






4.2.6.12 Adjacent Channel Use on Adjacent Sector 4-23

4.2.7 CNTG (Cellular Network Trunk Group) Form 4-234-23

4-23

4-23

4-22

4-22

4-22

4-21

4-21

4-21

4-21

4-20

4-20

4-19

4-19

4-19

4-18

4-18

4-18

4-18

4-17

4-17

4-17

4-17

4-17

4-16

4-16

4-16

4-16

4-16

4-15

4-15

4-15

4-14

401-200-112, Issue 11 June 2001 4-3


Contents


4.2.8 CTG (Cell Trunk Group) Form 4-24


4.2.9 ITG (Inter-switch Trunk Group) Form 4-24


4.2.10 LTG (Loop-around Trunk Group) Form 4-24


4.2.11 CTM (Cell Site Trunk Member) Form 4-25

4.2.11.1 Voice Radio - Channel Number 4-25

4.2.11.2 Voice Radio - Timeslot 4-25

4.2.11.3 DCA Interfering TNNs — TDMA PP 4-25

4.2.11.4 Voice Radio - Beacon 4-25

4.2.11.5 Voice Radio - Radio Type 4-26

4.2.11.6 Voice Radio - Slot Number 4-26

4.2.11.7 TDMA Digital Verification Color Code 4-26


4.2.12.1 TDMA Sequential Trunk Hunt 4-26

4.2.12.2 Voice Channel Candidate Selection Threshold -Primary 4-27

4.2.12.3 Primary - Class III/IV 4-27

4.2.12.4 Voice Channel Candidate Selection Threshold -Digital Primary. 4-27

4.2.12.5 Voice Channel Candidate Selection Threshold -Digital Primary - Class III/IV4-28

4.2.12.6 Voice Channel Candidate Selection Threshold -Secondary 4-28

4.2.12.7 Threshold (RSSI) - Interference Protection atHandoff (INTPHO) 4-28

4.2.12.8 INTPHO - Class III/IV 4-29

4.2.12.9 Threshold (RSSI) - TDMA INLA 4-29

4.2.12.10 TDMA Upward Hysteresis Adjustment (RSSI) 4-29

4.2.12.11 HOBIT Threshold - Downlink to AMPS 4-29

4.2.12.12 HOBIT Threshold - Uplink to Dual Mode 4-30

4.2.12.13 HOBIT Threshold - Downlink to Dual Mode 4-304-30

4-30

4-29

4-29

4-29

4-29

4-28

4-28

4-27

4-27

4-27

4-26

4-26

4-26

4-26

4-26

4-25

4-25

4-25

4-25

4-25

4-24

4-24

4-24

4-24

4-24

4-24

4-23

4-4 401-200-112, Issue 11 June 2001


Contents

4.2.12.14 Dynamic Power Control (DPC) State -TDMA Mobile 4-30

4.2.12.15 Dynamic Power Control (DPC) State -TDMA Target 4-31

4.2.12.16 Dynamic Power Control (DPC) State -TDMA Window 4-31

4.2.12.17 Dynamic Power Control (DPC) State -TDMA Slope 4-31

4.2.12.18 BER - Control DPC Feature State 4-31

4.2.12.19 Mobile BER High Threshold 4-32

4.2.12.20 Mobile BER Low Threshold 4-32

4.2.12.21 Amplifier Power Differential (RSSI) 4-32

4.2.12.22 Delay Interval Compensation 4-33

4.2.12.23 MPC Correction/Offset for Class III/IV Mobiles 4-33

4.2.12.24 L-EDRU DVCC Verification Active 4-34

4.2.12.25 Hybrid MAHO/Digital Locate TDMA HandoffAlgorithm Active 4-34

4.2.12.26 Append MAHO Candidates to HybridMAHO/Digital Locate 4-34

4.2.12.27 Up/Downlink Ranking Method for HybridMAHO/Digital Locate 4-34

4.2.12.28 TDMA Periodic Locate Type 4-35

4.2.12.29 Thresholds: Mobile Signal 4-35

4.2.12.30 Thresholds: Mobile Secondary 4-35

4.2.12.31 Thresholds: TDMA Locate Reply Threshold 4-36

4.2.12.32 Digital Voice Mobile Attenuation Code 4-37

4.2.12.33 Minimum Handoff Interval for TDMA 4-37

4.2.12.34 Mobile Reported Signal Strength Averagingamples - TDMA 4-37

4.2.12.35 Mobile Reported BER Averaging Samples 4-37

4.2.12.36 TDMA DTX with Comfort Noise Insertion Active 4-37


4.2.12.38 MCCLL Maximum Candidate Channel ListLength (MCCL) 4-38

4.2.12.39 Maximum Interference Threshold for Call Setup -Uplink (dB) 4-384-38

4-38

4-38

4-37

4-37

4-37

4-37

4-37

4-36

4-35

4-35

4-35

4-34

4-34

4-34

4-34

4-33

4-33

4-32

4-32

4-32

4-31

4-31

4-31

4-31

4-30

401-200-112, Issue 11 June 2001 4-5


Contents

4.2.12.40 Maximum Interference Threshold for Call Setup -Downlink (dB) 4-39

4.2.12.41 Maximum Interference Threshold for handoff -Uplink (dB) 4-39

4.2.12.42 Maximum Interference Threshold for handoff -Downlink(dB) 4-39

4.2.12.43 Mobile Assisted Handoff List 4-39

4.2.13 SHTG (Speech Handler Trunk Group) Form 4-43




4.2.13.4 Service Type 4-44

4.2.14 SUB (Subscriber and Feature Information) Form 4-44

4.2.14.1 Mobile Directory Number Type 4-44

4.2.14.2 Short Messess Service: Termination Restricted 4-44

4.2.14.3 Short Messess Service: Origination Restricted 4-44

4.2.15 TPPTM (TDMA Packet Pipe Trunk Member) Form 4-45


4.2.15.2 Packet Pipe - Trunk Group Number 4-45

4.2.15.3 Packet Pipe - Trunk Member Number 4-45

4.2.15.4 Trunk Status 4-45

4.2.15.5 Switching Module 4-46

4.2.15.6 Server Group 4-46

4.2.15.6.1 Default = 0 4-46

4.2.15.7 Physical Antenna - Receive 4-46

4.2.15.8 Physical Antenna - Transmit 4-46

4.2.15.9 Packet Pipe Data Rate Kbps 4-46

4.2.15.10 Connection - DS0 4-47

4.2.15.11 Connection - DS1 4-47

4.2.15.12 Voice Radio Information — Number 4-47

4.2.15.13 Voice Radio Information —Timeslot 1, Timeslot 2,Timeslot 3 4-47

4.2.15.14 Voice Radio Information —Type 4-47

4.2.15.15 Voice Radio Information —Frame Number 4-484-48

4-47

4-47

4-47

4-47

4-47

4-46

4-46

4-46

4-46

4-46

4-46

4-45

4-45

4-45

4-45

4-45

4-44

4-44

4-44

4-44

4-44

4-43

4-43

4-43

4-43

4-39

4-39

4-39

4-39

4-6 401-200-112, Issue 11 June 2001


Contents

4.2.15.16 Voice Radio Information —Shelf Number 4-48

4.2.15.17 Voice Radio Information —Slot Number 4-48

4.2.15.18 Voice Radio Information —Channel 4-48

4.2.15.19 Voice Radio Information — Beacon 4-48

4.2.15.20 Voice Radio Information — DVCC 4-49

4.2.15.21 Voice Radio Information — Mobile Power Class 4-49

4.2.15.22 Voice Radio Information — LAC Number 4-49

4.2.15.23 Dynamic Channel Allocation - Active 4-49

4.2.15.24 DCA Interfering TNNs 4-50

4.2.16 TPPTG (TDMA Packet Pipe Trunk Group) Form 4-50

4.2.16.1 Switch Identification 4-50


4.2.16.3 Cell Site Number 4-51

4.2.16.4 Number of Trunks 4-51

4.2.17 Summary of DTC Performance Database Translations 4-51

4.3 DCCH Performance Database Settings 4-57


4.3.1.1 Page Only if MS (Mobile Station) Last Accessedon DCCH 4-58

4.3.1.2 DCCH Activity Timeout Interval 4-58

4.3.1.3 DCCH Activity Timeout Allowed 4-59

4.3.1.4 TDMA DCCH Information: Signal Strength Meas.Interval 4-59

4.3.1.5 TDMA DCCH Information: Info. Word TransmissionRate 4-59

4.3.1.6 TDMA DCCH Information: Maximum Busy/Reserved 4-59

4.3.1.7 TDMA DCCH Information: Maximum Stop Counter 4-60

4.3.1.8 TDMA DCCH Information: Maximum Repetitions 4-60

4.3.1.9 TDMA DCCH Information: Maximum Retries 4-60

4.3.2 NET (Cellular Network) Form 4-60

4.3.2.1 Technology to Page 4-61

4.3.2.2 Final Technology to Page 4-61

4.3.3 CGSA (Cellular Geographic Service Area) Form 4-614-61

4-61

4-61

4-60

4-60

4-60

4-60

4-59

4-59

4-59

4-59

4-58

4-58

4-58

4-57

4-51

4-51

4-51

4-50

4-50

4-50

4-50

4-49

4-49

4-49

4-49

4-48

4-48

4-48

4-48

401-200-112, Issue 11 June 2001 4-7


Contents


4.3.3.2 DCCH Alphanumeric SID (ASID) 4-61

4.3.3.3 DCCH ASID Active 4-62

4.3.3.4 System Operator Code 4-62

4.3.3.5 IS-136 Emergency Routing Number 4-62

4.3.3.6 Registration Periodicity (min.) 4-62



4.3.4.2 IS-136 Allowable Call Mode Override 4-63

4.3.4.3 Should Home Mobiles Register-DCCH 4-63

4.3.4.4 Should Roamer Mobiles Register-DCCH 4-64

4.3.4.5 TDMA DCCH Registration Periodicity (min) 4-64

4.3.4.6 Power-Up/Power-Down Registration-DCCH 4-64

4.3.4.7 Location Area ID Registration-DCCH 4-64

4.3.4.8 TDMA DCCH Deregistration 4-65

4.3.4.9 Series II Cell Optional Feature List 4-65

4.3.4.10 ARR Available for TDMA DCCH Radio 4-65

4.3.4.11 Authentication Available for TDMA DCCH 4-66


4.3.5.1 Functional Test Interval-TDMA DCCH Radio 4-66


4.3.6.1 All Servers Busy Directed Retry-DCCH 4-66

4.3.6.2 Inadequate Signal Strength Directed Retry for DCCH. 4-66

4.3.6.3 Directed Retry Threshold-DCCH 4-67

4.3.6.4 SG0 Access Threshold-DCCH 4-67

4.3.6.5 Info. Word Transmission Rate 4-67

4.3.6.6 Mobile Attenuation Code 4-68

4.3.6.7 Mobile Access Threshold 4-68

4.3.6.8 Setup Access Threshold 4-69

4.3.6.9 Mobile Reselection Threshold 4-70

4.3.6.10 Access Burst Size 4-70

4.3.6.11 Signal Strength Meas. Interval 4-70

4.3.6.12 Reselection Delay 4-714-71

4-70

4-70

4-70

4-69

4-68

4-68

4-67

4-67

4-67

4-66

4-66

4-66

4-66

4-66

4-66

4-65

4-65

4-65

4-64

4-64

4-64

4-64

4-63

4-63

4-63

4-63

4-62

4-62

4-62

4-62

4-61

4-61

4-8 401-200-112, Issue 11 June 2001


Contents

4.3.6.13 Mobile Desired Service Bias 4-72

4.3.6.14 Initial Selection Control 4-72

4.3.6.15 Last Try Code (Directed Retry) 4-73

4.3.6.16 Network Type - Public / Private / Residential 4-73

4.3.6.17 PSID/RSID Indicator 4-73

4.3.6.18 PSID/RSID Value 4-73



4.3.7.2 TDMA DCCH Channel Number 4-74

4.3.7.3 TDMA DCCH Digital Verification Color Code 4-74

4.3.7.4 Control Channel Reselection Parameters: ProtocolVersion 4-74

4.3.7.5 Control Channel Reselection Parameters: MobileAttenuation Code 4-75

4.3.7.6 Control Channel Reselection Parameters: MobileAccess Threshold 4-75

4.3.7.7 Control Channel Reselection Parameters: MobileReselection Threshold 4-76


4.3.8.1 DCCH Shortened Burst on Call Setup 4-76

4.3.9 DCCH (Digital Control Channel) Form 4-76

4.3.9.1 Series II Cell Site Number 4-77

4.3.9.2 Voice Radio Number 4-77

4.3.9.3 Voice Radio Channel Number 4-77

4.3.9.4 Digital Verification Color Code 4-77

4.3.9.5 Status-Timeslot 1 4-77

4.3.9.6 Physical Antenna-Receive 4-78

4.3.9.7 Physical Antenna-Transmit 4-78

4.3.9.8 Linear Amplifier Circuit Number 4-78

4.3.9.9 Frame Number 4-78

4.3.9.10 Shelf Number 4-79

4.3.9.11 Slot Number 4-79

4.3.10 RESEL (Reselection List for Control Channels) Form 4-79

4.3.10.1 Cell Site 4-794-79

4-79

4-79

4-79

4-78

4-78

4-78

4-78

4-77

4-77

4-77

4-77

4-77

4-76

4-76

4-76

4-76

4-75

4-75

4-74

4-74

4-74

4-74

4-74

4-73

4-73

4-73

4-73

4-72

4-72

401-200-112, Issue 11 June 2001 4-9


Contents

4.3.10.2 PAF 4-79

4.3.10.3 Tech 4-79

4.3.10.4 Chan 4-80

4.3.10.5 DCC/DVCC 4-80

4.3.10.6 Directed Retry 4-80

4.3.10.7 Type 4-80

4.3.10.8 Delay 4-81

4.3.10.9 Offset Bias 4-82

4.3.10.10 Hi/Lo Freq 4-82

4.3.10.11 Extended Sys. ID - DCS/ECP/SYS 4-83

4.3.10.12 Network Type - Pub/Priv/Res 4-83

4.3.10.13 Prot Ver 4-83

4.3.10.14 Atten 4-83

4.3.10.15 RSS Access 4-84

4.3.10.16 RESEL Thrsh 4-85

4.3.11 Summary of DCCH Performance Database 4-854-85

4-85

4-84

4-83

4-83

4-83

4-83

4-82

4-82

4-81

4-80

4-80

4-80

4-80

4-79

4-79

4-10 401-200-112, Issue 11 June 2001



TDMA and DCCH Translations 4

4.1 Introduction

This chapter describes translations for TDMA and DCCH in an AUTOPLEXSystem 1000 cell site.

4.2 DTC Database Settings

This section provides the translation entries required to implement DTCfunctionality. These translations are entered via the AUTOPLEX Recent Change/Verify (RC/V) database access system. The translations listed below are groupedby their associated forms. The information includes a description of eachtranslation, along with its range, default value, and a recommended value.Recommended values are based on Lucent Technologies and customer fieldexperiences.

Forms covered in this section include:

■ ECP (Executive Cellular Processor)

■ Cell2 (Series II Cell Site Database)

■ NNBR (Network Neighbor)

■ CEQCOM2 (Series II Cell Equipage Common)

■ CEQSU2 (Series II Cell Equipage Setup)

■ CEQFACE (Cell Equipage Common Face)

■ CNTG (Cellular Network Trunk Group)

June 2001 4-1


■ CTG (Cell Trunk Group)

■ ITG (Inter-switch Trunk Group)

■ LTG (Loop-around Trunk Group)

■ CTM (Cell Site Trunk Member)

■ FCI (Face Code Information)

■ SHTG (Speech Handler Trunk Group) Form

■ SUB (Subscriber and Feature Information)

■ TPPTM (TDMA Packet Pipe Trunk Member) Form

4.2.1 ECP (Executive Cellular Processor) Form

Contains translations that apply to all cell sites on an ECP.

4.2.1.1 Max. No. of Mobile Requested Call ModeChanges

Maximum number of mobile requested call mode changes a mobile can makebetween handoffs.

■ Range: 0 to 3

■ Default Value: 1

■ Recommended Value: 3

4.2.1.2 Mobile Assisted Handoff Bias - TDMA

Bias value used by the cell site for the Mobile Assisted Handoff algorithm whenneither the per-cell (CELL2 Form) nor the per-face (FCI Form) bias value hasbeen entered.

■ Range: -31 to 31 IS-54B Encoded Units (IEU)

■ Default Value: 3 (~6 dB)


4.2.1.3 INLA Threshold - TDMA (RSSI)

Indicates the interference threshold above which the system will attempt to findanother channel with interference less than the threshold to set up on or hand offto. If such interference is detected on setup, the system will make two attempts tofind a channel with interference below the INLA threshold; it will make threeattempts on handoff. This is an optional feature that requires Feature ActivationFile with Qualifiers (QFAF).

4-2 401-200-112, Issue 11 June 2001



This field serves as the system-wide INLA Threshold default. It is overridden byentries in like-named fields in the CELL2 and FCI forms.

■ Range: 0 to 127 RSSI

■ Default Value: 31 RSSI

■ Recommended Value: 40-50 RSSI (-99 dBm or Target - Window -17 dB).Lucent Technologies recommends starting with a threshold of 50 andworking towards 40 as the system can accommodate it.

4.2.1.4 TDMA Test Mode Active

Indicates if all TDMA-capable mobiles are allowed to have TDMA service. Thistranslation does not force dual-mode mobiles to TDMA.

■ Range:

■ n = any dual-mode mobile can have TDMA service

■ y = only subscribers with a mobile DN type of "t" (entered on the“SUB” form) will receive TDMA service

■ Default Value: n

4.2.1.5 Differential Billing for Digital and AnalogTime

Indicates up to six auxiliary digital modules that can be appended to the Auto-mated Message Accounting (AMA) record. Each module contains one type ofnon-zero digital elapsed time.

■ Range:

■ y = yes, append to AMA record

■ n = no, do not append to AMA record


4.2.1.6 Append Basic Digital Module to the AMARecord

Indicates if the Automated Message Accounting (AMA) basic digital module thatcontains the technology type and station class mark should be appended to theAMA record.

■ Range:

■ y = yes, append module

■ n = no, do not append module


401-200-112, Issue 11 June 2001 4-3



4.2.1.7 Long List Weight Factor (LLWF)

Specifies the how latest uplink interference measurement update for all FLCA channelswithin the ECP domain is weighted for long list averaging. The larger the LLWF value, thelarger the fractional portion of the new interference measurement used to update therunning average.

When set to 255, old measurements are virtually ignored with respect to the long listinterference averages. When set to 1, new uplink measurements are ignored.

■ Range: 1 to 255


■ Recommended Value:

4.2.1.8 Long List Interference MeasurementInterval (LLIMI)

Specifies the time interval in minutes between interference measurement updateson the long list for each FLCA channel within the ECP domain. The larger theLLIMI value, updates are more infrequent the and the less responsive the long listis to RF environment change. Parameters should be set in conjunction withInterval for Short List Channel Update Interval (SLCUI).

The smaller the LLIMI value, the greater the locate radio processor load.

■ Range: 3 to 30 minutes in 1 minute steps

■ Default value: 5 minutes

4.2.1.9 Short List Channel Update Interval(SLCUI)

Defines when the short list is updated with the top candidates on the long list inmultiples of L LIMI.

Increasing and decreasing this parameter have the same effect on the short list asincreasing and decreasing the LLIMI value. The SLCUI is a whole number that ismultiplied by LLIMI to determine the short list update interval. For example, if theSLCUI is set to 2 and the LLIMI value is equal to 5 minutes, the short list will thanbe updated every (2 X 5 minutes) 10 minutes. A zero SLCUI value indicates noshort list update.

■ Range: 0, 1 to 10

■ Default: 2

4-4 401-200-112, Issue 11 June 2001



4.2.1.10 Maximum Short List Length (MSLL)

Defines the maximum number of channels that may be on the short list.

Increasing this parameter, requires more downlink measurements, increasingmobile and voice EDRU load in addition to increasing locate radio processor load.

Decreasing this parameter decreases the number of FLCA radios that may beactive simultaneously.

■ Range: 5 to 12

■ Default value: 10

4.2.1.11 Short List Uplink Weight Factor (SLUWF)

Specifies how the latest uplink interference measurement update for all channelson the face is weighted for uplink short list averaging. The larger the SLUWFvalue, the larger the fractional portion of the new interference measurement usedto update the running average.

When set to 255, old measurements are virtually ignored with respect to the shortlist interference averages. When set to 1, new uplink measurements are virtuallyignored.

■ Range:1 to 255


4.2.1.12 Short List Downlink Weight Factor(SLDWF)

Specifies how the latest downlink interference measurement update for allchannels on the face is weighted for downlink short list averaging. The larger theSLDWF value, the larger the fractional portion of the new interferencemeasurement used to update the running average.

When set to 255, old measurements are virtually ignored with respect to the shortlist interference averages. When set to 1, new uplink measurements are virtuallyignored.

■ Range:1 to 255


401-200-112, Issue 11 June 2001 4-5



4.2.1.13 Short List Interference MeasurementInterval (SLIMI)

Specifies the time interval in seconds between interference measurementupdates for each channel on the short list. The larger the SLIMI value, the moreinfrequent the update and the less responsive the short list is to uplink RFenvironment change.

The smaller the TSTLIML value, the greater the locate radio processor load.

■ Range: 7 to 60 seconds in 1-second steps

■ Default value: 10 seconds

4.2.1.14 Number of Downlink Measurement forValid Downlink List (NDM)

Specifies number of downlink interference measurements to be taken within thetime period, defined by TDM parameter, for the measurement in downlink short listto be considered valid.

■ Range:0 to 1000

■ Default value:10

4.2.1.15 Downlink Measurement Interval (DMI)

Specifies time period over which a number of downlink interferencemeasurements, defined by NDM the parameter, must be received for averagedmeasurement in downlink short list to be considered valid.

■ Range: 1 to 20 minutes

■ Default value: 10 minutes

4.2.1.16 Maximum Candidate Channel ListLength (MCCLL)

Specifies the maximum number of channels placed on the FLCA candidatechannel list.The channels on this list are FLCA candidate channels for call setupand call handoff. This parameter is set on the ecp form to define the MCCLLvalue for all the LAFs in the ECP domain. A similar parameter can be found on thefci form to define the MCCLL value for a LAF. If the MCCLL range field on the fciform is left blank, the MCCLL value on the ecp form is used. The system williterate through the selection and acceptance process for each candidate channeluntil the MCCLL number is reached, or until the number of acceptable channelsare exhausted. The ultimate number of channels on the candidate channel list isdefined as the MAXCHAN value.

4-6 401-200-112, Issue 11 June 2001



■ Range: 1 to 4

■ Default: 4

4.2.1.17 Adjacent Channel Use on AdjacentSector Allowed

Indicates whether the IBDCA algorithm is allowed to assign channels that areadjacent in frequency to either fixed channels or active FLCA channels on othersectors in the same cell

■ Valid entries: y/n

■ Default value: y

4.2.1.18 Short Order Bias

Specifies bias value to normalize uplink and downlink measurements to acommon base. Increasing this parameter increases the effect of uplinkmeasurements on channel ordering. Decreasing this parameter increases theeffect of downlink measurements on channel ordering.

■ Range: -50 dB to +50 dB

■ Default value: 0 dB

4.2.1.19 Server Group Channel Selection (SGCS)

When a channel fixed to a server group is unavailable, this parameter specifies if,and under what conditions, a call setup or handoff is switched to the other servergroup on the sector (physical antenna face). If EDRU radio transmitted ouput isrouted through an auto-tuned cavity combinner, valid entry is forced to select ownserver group channels only.

■ Valid entries:

1. Select channel independent of server group designation

2. Select own server group channels only

3. Select other server group channels after own server groupchannels.

■ Default: 3, Select other server group channels after own server groupchannels

4.2.1.20 Maximum Interference Threshold forCall Setup - Uplink (dB)

Defines maximum uplink interference signal strength allowed for call setup.

401-200-112, Issue 11 June 2001 4-7



■ Range: -130 dB to -57 dB

■ Default value: -77 dB

4.2.1.21 Maximum Interference Threshold forCall Setup - Downlink (dB)

Defines maximum downlink interference signal strength allowed for call setup.

■ Range: -113 dB to -53 dB, in 2 dB steps


4.2.1.22 Maximum Interference Threshold forhandoff - Uplink (dB)

Defines maximum uplink interference signal strength allowed for handoff.

■ Range: -130 dB to -57 dB


4.2.1.23 Maximum Interference Threshold forhandoff - Downlink (dB)

Defines maximum downlink interference signal strength allowed for handoff.

■ Range:-113 dB to -53 dB, in 2 dB steps

■ Default value: 81dB

4.2.1.24 Area Wide Test Channel (AWTC) -Cellular

Selects a single RFchannel to be dedicated exclusively for maintainance andtesting. The AWTC is used as a default channel when any test and maintainanceactivity requiring transmiting over a FLCA channel is performed. The selection ofan AWTC channel eliminates the requirement for runing channel selection andacceptance tests to insure that the selected channel is clear prior to performingmaintainance and testing on any FLCA EDRU. The selected AWTC channel willbe used throughout the ECP domain.

! CAUTION:Because when an AWTC channel is used, interference checksare not performed, care must be taken to insure that the channelselected for AWTC is not assigned as either a fixed or FLCAchannel to any cell in the ECP domain .

4-8 401-200-112, Issue 11 June 2001



■ Range: 2 - 1998

4.2.2 CELL2 (Series II Cell Site Database) Form

Contains translations that apply cell-wide.

4.2.2.1 Antenna Face Trunk Group List

Identifies the TDMA trunk group assigned to each logical face (must be aseparate trunk group from AMPS).

Range:

■ 18-254 for DEFINITY Switch Digital Cellular Switch (DCS) or NULL

■ 1-999 for 5ESS-2000 Switch DCS, or NULL

4.2.2.2 Cell Generic - Version Name

Specifies the cell generic version name as provided on the cell generic tape. Thisis the software version that will be downloaded at the next cell boot. This fieldshould never be different from the generic running on the cell except during thetransition period when the cell is being updated to the new generic. Failure tocomply with this requirement makes it impossible for the cell to successfullyinitialize or complete the boot process. To determine generic, execute op:cell x,generic on craft terminal or Maintenance Cathode Ray Tube (MCRT).

4.2.2.3 Cell Generic - R5 Compatible

This field is read-only, and its value is determined by the Cell Generic - VersionName field (above).

■ Range:

■ n = no, R5 not installed at cell site

■ y = yes, R5 installed at cell site

■ Default Value: determined by generic name (above)

4.2.2.4 IS-54B Allowable Call Mode Override

Indicates if allowable call mode override for IS-54B mobiles is enabled

■ Range:

■ y = yes, sets override for TDMA-only request from dual-modemobiles; allows mobiles to use analog channels if no TDMAchannels are available.

401-200-112, Issue 11 June 2001 4-9



■ n = no, dual-mode mobiles requesting TDMA-only service will not behanded off to AMPS channels. If neighbor cells do not have TDMA,or all TDMA time slots are busy, the call will drag.

■ Default Value: y

4.2.2.5 Number of Simultaneous NVMs - TDMA

Indicates the number of DRU/EDRUs that can be simultaneously nonvolatilememory (NVM) updated for TDMA Series II cell sites when a global NVM isrequested.

■ Range: 1 to 200



■ 10, if NMV update is done with call processing allowed

■ 192, if NVM update is done with call processing inhibited

4.2.2.6 Voice Out of Service Limit -(%) TDMA

Indicates the out-of-service (OOS) limit, in percent, for Series II TDMA voiceradios. Lucent Technologies recommends a minimum of 2 DRU/EDRUs persector. The OOS limit should be set in accordance with the number of installedDRU/EDRUs so maintenance and diagnostics can be executed on the DRU/EDRUs.

■ Range: 25 to 100



■ 100, for one DRU/EDRU per face

■ 50, for two DRU/EDRUs per face

■ 60, for two DRU/EDRUs per face and one being a DCCH

■ If more than two DRU/EDRUs per face, value should always allow atleast one DRU/EDRU to be taken out-of-service for diagnostics.

4.2.2.7 INLA Threshold - TDMA (RSSI)

Indicates the interference threshold (Interference Look Ahead or INLA) abovewhich the system will attempt to find another channel with interference less thanthe threshold to set up on or hand off to. If such interference is detected on setup,the system will make two attempts to find a channel with interference below the

4-10 401-200-112, Issue 11 June 2001



INLA threshold; it will make three attempts on handoff. This is an optional featurethat requires Feature Activation File with Qualifiers (QFAF).

When this field is left blank, the system will use the INLA Threshold translationentered in the ECP form.

■ Range: 0 - 127 RSSI (Received Signal Strength Indicator)


■ Recommended Value: 40 RSSI (-99 dBm) (Lucent Technologiesrecommends starting with a threshold of 50 (-91dBm) and working towards40 as the system can accommodate it.)

4.2.2.8 Cell Site Optional Features

These translations are used to enable and disable features for this cell.

■ Features:

4. TDMA PRC BSL (TDMA Periodic Best Server Locate feature)

5. TDMA FULLRATE (Indicates that cell is TDMA-capable)

6. HO INT TDMA (Handoff Based on Interference - TDMA)

7. ARR (Automatic Radio Reconfiguration Support for Beacon Radios)

8. INLA (Interference Look Ahead)

9. TDMA DCCH (Indicates that cell is DCCH-capable)

10. Voice Privacy

11. DCCH SMS (Short Message Service)

12. TDMA M-O SMS (TDMA Mobile-Originate SMS)

■ Range:

■ y, enable feature

■ n, disable feature


4.2.2.9 ARR is Available for: Beacon Radio

Indicates if ARR is allowed for a beacon radio.

■ Range:

■ y, ARR is allowed

■ n, ARR is not allowed

■ Default value: n

401-200-112, Issue 11 June 2001 4-11



■ Recommended Value: y

4.2.2.10 ARR is Available for: Locate EDRU(L-EDRU) Radio

Indicates if ARR is allowed for an L-EDRU radio.

■ Range:

■ y, ARR is allowed

■ n, ARR is not allowed

■ Default value: y

■ Recommended Value: n (if only one L-EDRU is used)

4.2.2.11 Authentication is Available on: AnalogControl Channel

Indicates whether global authentication (AUTH) is active on the ACC.

■ Range:

■ y, GLOBAL AUTH active

■ n, GLOBAL AUTH not active


4.2.2.12 Number of Time Slots for DVCCPresence

Indicates the required number of consecutive time slots, in which DVCC isproperly decoded, to confirm digital verification color code presence for TDMA.

■ Range: 1 to 5


■ Recommended Value: 2 - 5

4.2.2.13 DVCC Detection Timeout Time Slots

Indicates the required number of consecutive time slots, in which DVCC is notpresent, before the TDMA Fade Timer starts.

■ Range: 1 to 100 (2 seconds)



4-12 401-200-112, Issue 11 June 2001



4.2.2.14 Bit Error Rate Threshold (%)

Indicates the Bit Error Rate (BER) threshold for TDMA. A voice DRU/EDRU (V-DRU/EDRU) generates a locate trigger whenever the BER detected by the radioor reported by the mobile exceeds this threshold.

■ BER Percent Threshold Indicators:

0=BER <= 0.01% 4=BER 1-2%

1=BER 0.01-0.1% 5=BER 2-4%

2=BER 0.1-0.5% 6=BER 4-8%

3=BER 0.5-1% 7=BER > 8% (disabled)


■ Recommended Value: 3 or 4; This value will reduce the chance of handoffto analog, when there is one DRU/EDRU per logical face, or ping-ponginghandoffs, when there are more than one DRU/EDRU per logical face.

4.2.2.15 Frame Error Rate Threshold (%)

Indicates the Frame Error Rate (FER) threshold (in percent) for TDMA. A V-DRU/EDRU generates a locate trigger whenever the FER measured by the DRU/EDRUexceeds this threshold.

■ Range: 0 to 100



4.2.2.16 Mobile Assisted Handoff Bias

Every second, the mobile measures both the downlink serving signal strength andthe neighbor Mobile Assisted Handoff (MAHO) channels (beacon channels) signalstrength. These measurements are reported to the serving cell site, which willevaluate neighbors as possible handoff candidates. In order for a neighbor cellsite to be considered as a handoff candidate, the measured beacon signalstrength must exceed the downlink serving signal strength by the value set forbias. This bias value is used in the MAHO algorithm if no bias value is specified inthe FCI form.

■ Range: -31 to 31 IS-54B Encoded Units (IEU)

■ Default Value: Blank (ECP form value used)

■ Recommended Value: 3 (6 dB)

401-200-112, Issue 11 June 2001 4-13



4.2.2.17 Mobile Requested Call Mode Change

Indicates if a dual mode mobile-requested call mode change from TDMA toanalog is allowed.

■ Range:

■ y = yes; allow mobile to hand off (same face) from TDMA channel toAMPS channel

■ n = no


■ Recommended Value: y (for example, to send a FAX)

4.2.2.18 DVCC Verification Active

Enables/disables DVCC verification on handoff feature performed by the DigitalLocate Radio. Requires Digital Locate Radio Equipage to be set to “y” inCEQCOM2 form



4.2.2.19 Digital Locate Radio Equipage (Read-Only)

Indicates the number of DRU/EDRUs equipped on a cell. This value is based onthe equipage value entered in the CEQCOM2 form.

■ Range:

■ blank, no locate DRU/EDRUs equipped

■ l-dru, cell equipped with minimum required DRU/EDRUs

■ Default Value: blank

4.2.2.20 Long List Interference MeasurementInterval (LLIMI)

Specifies the time interval in minutes between interference measurement updatesfor each channel on the long list. The larger the LLIMI value, updates are moreinfrequent the and the less responsive the long list is to RF environment change.As a result, the short list will be less current as channels drop off and replacementbecomes less responsive to RF environment change. Parameters should be set inconjunction with Short List Channel Update Interval (SLCUI). If the range entryfor this parameter is left blank, the entry for this parameter defaults to the LLIMIvalue selected on the ecp form.

4-14 401-200-112, Issue 11 June 2001



The smaller the TLTLIML value, the greater the locate radio processor load.

■ Range: Blank, 3 to 30 minutes in 1 minute steps

4.2.2.21 Short List Interference MeasurementInterval (SLIMI)

Specifies the time interval in seconds between interference measurementupdates for each channel on the short list. The larger the SLIMI value, the moreinfrequent the update and the less responsive the short list is to uplink RFenvironment change. If the range entry for this parameter is left blank, the entryfor this parameter defaults to the SLIMI value selected on the ecp form.

The smaller the SLIMI value, the greater the locate radio processor load.

■ Range: Blank, 7 to 60 seconds in 1-second steps

4.2.2.22 Short List Channel Update Interval(SLCUI)

Defines when the short list is updated with the top candidates on the long list inmultiples of LLIMI.

Increasing and decreasing this parameter have the same effect on the short list asincreasing and decreasing the LLIMI value. If the range entry for this parameter isleft blank, the entry for this parameter defaults to the SLCUI value selected on theecp form. value selected on the ecp form.

■ Range: 0, 1 to 10

4.2.2.23 Network Transmission Level (dB) Rx forDRU/EDRU

Audio level adjustment in dB required to maintain a nominal -19 dBm output fromvoice DRU/EDRU receiver to the Public Switched Telephone Network (PSTN).

■ Range: -15 to +3

■ Default Value: -4 for AMPS, 0 for TDMA


■ 0 dB for DRU/EDRUs (TDMA)

■ -2 dB for AMPS (for good audio level matching between AMPS andTDMA)

401-200-112, Issue 11 June 2001 4-15



4.2.2.24 Network Transmission Level (dB) Tx forDRU/EDRU

Audio level adjustment in dB required to maintain an “R” value of 21 for a -19 dBminput from the PSTN.

■ Range: -15 to +3



■ 0 dB for DRU/EDRUs (TDMA)

■ -4 dB for AMPS (for good audio level matching between AMPS andTDMA)

4.2.2.25 Handoff at Optimum Power - TDMA

Indicates if the handoff from a channel will take place at optimum power.

■ Range: y, n


■ Recommended Value: y (Should also be set to “y” in the NNBR form.)

4.2.3 NNBR (Network Neighbor) Form

Contains information for the network neighbor database, used to determinehandoff permissions to the neighboring MSCs.

4.2.3.1 SMS Capable

Indicates if the network neigbor is SMS capable.

■ Range: y, n


4.2.3.2 SMS Destination MC

Indicates the network address for the message center to which the mobileorignated SMS message (R-DATA) is delivered. This parameter is used only forSMS messge generate be roaming SMS subscribers.

■ Range:16 - 1039 or Null

4-16 401-200-112, Issue 11 June 2001



4.2.3.3 Destination MC SSN

Indicates the Sub-System Number (SSN) of the message center to which themobile orignated SMS message (R-DATA) is delivered. This parameter is usedonly for SMS messge generate be roaming SMS subscribers. The SSN is definedper cell and varies amoung messagee centers

■ Range: 0 -255

4.2.3.4 Handoff/Setup Optimum Power - TDMA

Indicates if the Handoff at Optimum Power Level (HOPL) feature for TDMA isturned on for inter-MSC and inter-DCS handoffs.

■ Range: y, n


4.2.4 CEQCOM2 (Series II Cell EquipageCommon) Form

Defines equipment translations applied to the whole cell site.

4.2.4.1 TDMA Periodic Best Server Locate

The time in seconds between consecutive periodic checks on a stable call todetermine if another cell or face can serve the call better.

Feature must be activated through FAF, and ECP and CELL2 forms.

■ Range: 0 to 75 seconds

■ Default Value: 0 (disables the feature)

■ Recommended Value: 3 seconds

4.2.4.2 TDMA Measurement Processing Interval

Time interval at which TDMA Dynamic Power Control and handoff candidateselection take place. These are based on BER average and/or signal strengthaverage values. The averages are based on the number of samples collected asspecified in the FCI form. This interval combines the signal strength processinginterval and BER processing interval for TDMA.

■ Default Value: 2 seconds

■ Recommended Value: 2 or 4

401-200-112, Issue 11 June 2001 4-17



4.2.4.3 TDMA RTU DVCC

1. Status

Provides the status of the TDMA radio test unit.

■ Range:

■ e = equipped, to allow diagnostics and CFR (configure) commandson a DRU/EDRU

■ g = growth

■ u = unequipped

■ Default Value: e

2. Slot

Provides the slot number where the TDMA RTU is located in the Radio ChannelFrame.



3. DVCC

Specifies the digital verification color code (DVCC) used by the TRTU in self-diag-nostics.

Recommended Value: 45 and162

4.2.5 CEQSU2 (Series II Cell Equipage Setup)Form

The CEQSU2 form defines translations for the cell site setup radios.

4.2.5.1 Digital Color Code

A code, transmitted in forward and reverse control channel messages, that isused to screen out service requests from mobile units in interfering cell sites.

■ Range: 0 to 3


4.2.5.2 Color Codes - 1st TDMA SupervisoryDigital (SDCC)

This field, used in conjunction with the DCC translation, and the 2nd SDCCdiscussed below, provides 64 color code combinations (2 binary bits each field, for6 bits total, 26 = 64). Lucent Technologies recommends using these fields to

4-18 401-200-112, Issue 11 June 2001



enhance glare protection. (Recent field trials indicate that the use of SDCCreduces setup glare.) Assignment of color codes should be such that co-setup,co-DCC (including SDCC) interference is avoided.

A zero-zero (00) response from a mobile is the IS-54 standard indication that theuse of supervisory digital color code is not supported by the mobile.

■ Range (per field): 0 to 3


■ Recommended Value: 1 to 3

4.2.5.3 Color Codes - 2nd TDMA SupervisoryDigital (SDCC)

This field, used in conjunction with the two translations discussed above, providesfor a total of 64 color code combinations (2 binary bits each field, for 6 bits total,26 = 64). Lucent Technologies recommends using these fields to enhance glareprotection. (Recent field trials indicate that the use of SDCC reduces setup glare.)Assignment of color codes should be such that co-setup, co-DCC (includingSDCC) interference is avoided.

A zero-zero (00) response from a mobile is the IS-54 standard indication that theuse of supervisory digital color code is not supported by the mobile.

■ Range (per field): 0 to 3


■ Recommended Value: 1 to 3

4.2.6 CEQFACE (Cell Equipage Common Face)Form

The CEQFACE form defines translations common to all equipment on the LAF orsector.

4.2.6.1 TDMA Voice Radio Attenuation Level

Defines the transmit power of the Digital Traffic Channels, on a per-server groupbasis. For a mixed-mode DRU/EDRU (i.e., DCCH and DTC on same DRU/EDRU), this value must be equal to the Cell Site Attenuation Code (CEQFACEform).

■ Range: 0 to 7, where:

401-200-112, Issue 11 June 2001 4-19




■ Recommended Value: Equal to Cell Site Attenuation Code (CEQFACEform)

4.2.6.2 TDMA Fade Timer

Indicates the interval between the loss of DVCC and call teardown. If the DVCChas not been detected by the TDMA voice radio during this interval, a "lost call-DVCC time-out" will be pegged by Service Measurements and the time slot andtrunk released.

■ Range: 10 to 100 (200 mS increments)


■ Recommended Value: 50-100 (10-20 seconds). Set the same as AMPSSAT Fade Timer.

4.2.6.3 Cell Site Attenuation Code

Defines transmit power of DRU/EDRU(S) for a physical antenna face when DCCHis equipped. For a mixed-mode DRU/EDRU (i.e., DCCH and DTC on same DRU/EDRU), this value must be equal to the TDMA Voice Radio Attenuation Level forthe Server Group that contains the DCCH DRU/EDRU (CEQFACE form).



■ Recommended Value: Equal to TDMA Voice Radio Attenuation Level(CEQFACE form)

0 = 0 dB attenuation (full power) 4 = 16 dB attenuation

1 = 4 dB attenuation 5 = 20 dB attenuation



0 = 0 dB attenuation (full power) 4 = 16 dB attenuation




4-20 401-200-112, Issue 11 June 2001



4.2.6.4 Two Branch Intelligent Antennas Activefor DCCH 71)

Enables Two Branch Intelligent Antennas (TBIA) Feature on logical face. Thisfield will be ignored when TDMA TBIA field in the Option Feature section on thecell2 form is set no, indicating that TBIA feature is not activated.


■ Default: y

■

4.2.6.5 FLCA Monitoring

Identifies if idle channel monitoring is performed and the type of monitoring that isperformed on the antenna face. When an auto-tuned cavity combiner is notused, the Channel Set parameter must enter before the FLCA Monitoringparameter is entered.

■ Range:

0. FLCA monitoring is not enabled

1. Uplink monitoring only

2. Uplink monitoring plus downlink MACA monitoring (not available inRelease 14.0)

3. Uplink monitoring plus downlink MAHO monitoring

4. Uplink monitoring plus downlink MACA and MAHO monitoring (notavailable in Release 14.0)

■ Default: 0 — FLCA monitoring is not enabled

4.2.6.6 Channel Set

Selects from up to 100 different channel sets for use by the physical antenna face.

■ Range: Blank, 1 to 100

4.2.6.7 Long List Weight Factor (LLWF)

Specifies how latest interference measurement update for all channels on the face isweighted for long list averaging. The larger the LLWF value, the larger the fractionalportion of the new interference measurement used to update the running average.

When set to 255, old measurements are virtually ignored with respect to the long listinterference averages. When set to 1, new uplink measurements are ignored. If the rangeentry for this parameter is left blank, the entry for this parameter defaults to the LLWFvalue selected on the ecp form.

401-200-112, Issue 11 June 2001 4-21



■ Range: Blank, 1 to 255

4.2.6.8 Short List Uplink Weight Factor (SLUWF)

Specifies how latest uplink interference measurement update for all channels onthe face is weighted for uplink short list averaging. The larger the SLUWF value,the larger the fractional portion of the new interference measurement used toupdate the running average

When set to 255, old measurements are virtually ignored with respect to the longlist interference averages. When set to 1, new uplink measurements are virtualltignored. If the range entry for this parameter is left blank, the entry for thisparameter defaults to the SLUWF value selected on the ecp form.

■ Range: Blank,1 to 255

4.2.6.9 Short List Downlink Weight Factor(SLDWF)

Specifies how latest downlink interference measurement update for all channelson the face is weighted for downlink short list averaging. The larger the SLDWFvalue, the larger the fractional portion of the new interference measurement usedto update the running average.

When set to 255, old measurements are virtually ignored with respect to the longlist interference averages. When set to 1, new downlink measurements arevirtually ignored. If the range entry for this parameter is left blank, the entry for thisparameter defaults to the SLDWF value selected on the ecp form.

■ Range: 1 to 255


4.2.6.10 Short Order Bias

Specifies bias value to normalize uplink and downlink measurements to acommon base. Increasing this parameter, increases the effect of uplinkmeasurements on channel ordering. Decreasing this parameter increases theeffect of downlink measurements on channel ordering. If the range entry for thisparameter is left blank, the entry for this parameter defaults to the SOB valueselected on the ecp form.

■ Range: Blank, -50 dB to +50 dB

4.2.6.11 Maximum Short List Length (MSLL)

Defines the maximum number of channels that may be on the short list.

4-22 401-200-112, Issue 11 June 2001



Increasing this parameter, requires more downlink measurements, thus,increasing mobile and voice EDRU load, in addition to increasing locate radioprocessor load.

Decreasing this parameter, decreases the number of FLCA radios that may beactive simultaneously. If the range entry for this parameter is left blank, the entryfor this parameter defaults to the MSLL value selected on the ecp form.

■ Range: 5 to 12

4.2.6.12 Adjacent Channel Use on AdjacentSector

Indicates whether the IBDCA algorithm is allowed to assign channels that areadjacent in frequency to either fixed channels or active FLCA channels on othersectors in the same cell. If the entry for this parameter is left blank, the entry forthis parameter defaults to the Adjacent Channel Use on Adjacent Sector valueselected on the ecp form.


4.2.7 CNTG (Cellular Network Trunk Group)Form

The CNTG form defines translations related to trunks used for cellular networking.

4.2.7.1 Analog Option on Digital Terminations

Indicates if all terminations to dual-mode mobiles received on this trunk groupshould be forced to analog mode (feature must be active in FAF). RF conditionsmay seriously degrade the audio quality of TDMA to TDMA calls. If C/I is notadequate, forcing all terminations to AMPS may be advisable.

■ Range:

■ y = force to analog mode

■ n = terminate to preferred mode


■ Recommended Value: n

4.2.8 CTG (Cell Trunk Group) Form

The CTG form defines translations for all cell trunk members assigned to this celltrunk group.

401-200-112, Issue 11 June 2001 4-23



4.2.8.1 Technology Type

Defines the radio technology supported by this trunk group:

Range: AMPS, TDMA

4.2.9 ITG (Inter-switch Trunk Group) Form

The ITG form defines translations for trunk groups used for inter-switchnetworking.


Indicates if all terminations to dual-mode mobiles received on this trunk groupshould be forced to analog mode (feature must be active in FAF). RF conditionsmay seriously degrade the audio quality of TDMA-to-TDMA calls. If C/I is notadequate, forcing all terminations to AMPs may be advisable

■ Range:




4.2.10 LTG (Loop-around Trunk Group) Form

The LTG form defines translations for trunks used for calls originating andterminating within the system.


Indicates if all terminations to dual-mode mobiles received on this trunk groupshould be forced to analog mode (feature must be active in FAF). RF conditionsmay seriously degrade the audio quality of TDMA-to-TDMA calls. If C/I is notadequate, forcing all terminations to AMPs may be advisable.

■ Range:




4-24 401-200-112, Issue 11 June 2001



4.2.11 CTM (Cell Site Trunk Member) Form

The CTM form defines the association between specific Digital Services, Level 0(DS0) timeslots and cell site radios.

4.2.11.1 Voice Radio - Channel Number

Defines the channel number for the radio associated with this trunk member.

4.2.11.2 Voice Radio - Timeslot

Each DRU/EDRU has three CTM forms associated with it (one for each TDMAtime slot, 1,2 or 3).

Range: 1 to 3 (TDMA only), or NULL

4.2.11.3 DCA Interfering TNNs — TDMA PP

Used when the switch based TDMA vocoder feature is implemented to identifythat the Dynamic Channel Allocation (DCA) feature is active for the associatedcell site trunk member radio. The DCA feature minimizes radio channel frequencyinterference by preventing radios assigned to the same frequency in different cellsin close proximity, from operating simultaneously. Up to four AMPS, DRU andEDRU radios that are assigned to the same frequency in different cells may beidentified on a DCA Interfering TNN list. The EDRU radios must be located in cellswhere the switch based TDMA vocoder feature is not implemented. If the EDRUradio is located in cells where the switch based TDMA vocoder feature isimplemented, only one EDRU radio and one RCU or DRU radio may be identified.When a voice channel is needed to service a mobile, the voice channel selectionalgorithm checks the DCA active status of the radio. If the status is active and anyradio on its TNN list is currently active, the voice channel selection algorithm willselect another radio.

■ Range: y/n

4.2.11.4 Voice Radio - Beacon

Identifies the voice radio associated with this trunk member as a beacon channelfor TDMA Mobile Assisted Handoff (MAHO).

■ Range:

■ on, if this voice radio is to be used as a beacon radio

■ off (analog or TDMA)

■ Default Value: off

401-200-112, Issue 11 June 2001 4-25



4.2.11.5 Voice Radio - Radio Type

■ Identifies voice radio type as follows:

■ arcu= AMPS radio

■ sbrcu= Single Board AMPS radio

■ vdru = Voice DRU

■ etdru = (extented DRU) EDRU

■ NULL

■ Default Value: arcu

4.2.11.6 Voice Radio - Slot Number

DRUs occupy two physical slots on a shelf; the leftmost slot is specified in thisfield. Lucent Technologies recommends that this slot be even-numbered so thatradios do not have to be moved when growth radios are added to the frame.

Range: 2 to 12 or NULL

4.2.11.7 TDMA Digital Verification Color Code

Indicates the DVCC value transmitted in every message frame.

■ Range: 1 to 161, 163 to 255

■ Recommended Value: Cell site number (except 45 and162)

4.2.12 FCI (Face Code Information) Form

The FCI form contains translations that apply to this particular face or sector.

4.2.12.1 TDMA Sequential Trunk Hunt

Indicates which type of trunk hunt (sequential or most-idle) is to be performed onthe cell site TDMA trunk group assigned to this face and server group. Sequentialtrunk hunt should be set up so that all time slots on one DRU are used beforeusing next DRU. This is preferred since it minimizes RF interference. Furtherreduction of RF interference can be achieved by assigning radios in ascendingorder (relative to the trunk order) in one cell, and descending order in their re-usecells.

■ Range:

■ y = sequential trunk hunt (low to high)

■ n = most-idle trunk hunt

4-26 401-200-112, Issue 11 June 2001





4.2.12.2 Voice Channel Candidate SelectionThreshold - Primary

Indicates the minimum signal strength level (in RSSI units) to maintain satisfactoryservice. If the signal level drops below this threshold, the cell site attempt to selecta new voice channel for calls being served on this face and server group. If thecorresponding cell2 form has the MPC DEP THR optional feature field set to "y,"this threshold only applies to mobiles with a mobile power class of I or II.Otherwise, this threshold applies to all mobiles, regardless of mobile power class.

■ Range: 0-127 for -130 to -30 dBm

■ Default: 66

4.2.12.3 Primary - Class III/IV

Indicates the minimum signal strength level (in RSSI units) to maintain satisfactoryservice for mobiles of power classes III and IV. If the signal level drops below thisthreshold, the cell site to attempt to select a new voice channel for calls beingserved on this face and server group. If the corresponding cell2 form has the MPCDEP THR optional feature field set to "y," this threshold is used for mobiles with amobile power class of III or IV. Otherwise, this threshold is not used.

■ Range: 0-127 for -130 to -30 dBm

■ Default = 66

4.2.12.4 Voice Channel Candidate SelectionThreshold -Digital Primary.

Indicates the minimumTDMA signal strength level (in RSSI units) to maintainsatisfactory service. If the signal level drops below this threshold, the cell site toattempt to select a new TDMA voice channel for calls being served on this faceand server group. Note: If this field is left blank, it will be set to the same value asthe analog Voice Channel Candidate Selection Threshold-Primary field.

■ Range: 0 - 127 (or NULL)

4.2.12.5 Voice Channel Candidate SelectionThreshold - Digital Primary -Class III/IV

Indicates the minimum TDMA signal strength level (in RSSI units) to maintainsatisfactory service for mobiles of power classes III and IV. If the signal level

401-200-112, Issue 11 June 2001 4-27



drops below this threshold, the cell site to attempt to select a TDMA new voicechannel for calls being served on this face and server group. If the correspondingcell2 form has the MPC DEP THR optional feature field set to "y," this thresholdonly applies to mobiles with a mobile power class of I or II. Note: If this field is leftblank, it will be set to the same value as the analog Voice Channel CandidateSelection Threshold - Class III/IV field.


4.2.12.6 Voice Channel Candidate SelectionThreshold - Secondary

Indicates the minimum signal strength level (in RSSI units) to maintain satisfactoryservice. If the signal level drops below this threshold, the cell site to attempt toselect a new voice channel on group 2 neighbors for calls being served on thisface and server group. A value of 12 below the primary group is recommended

■ Range: 0-127 for -130 to -30 dBm

■ Default = 54

4.2.12.7 Threshold (RSSI) - InterferenceProtection at Handoff (INTPHO)

Indicates the minimum signal strength level (in RSSI units) to permit handoff tothis face and server group for mobile power class of I or II. If signal strength isbelow this level, handdoff will be denied. This parameter is used to screen outmeasurements from interfering mobiles. If the MPC Dependent INTPHO withVoice Channel Reservations feature has been FAF activated, this thresholdapplies to mobiles with a mobile power class of I or II.Otherwise, this threshold isused for all mobiles regardless of mobile power class.

This parameter is also used to indicates the minimum uplink signal strength levelmeasured at the cell in RSSI units allowing the serving face to be added to thecandidate list for AMPS service only. Two conditions must be meet before handofffrom a TDMA channel to an AMPS channel occurrs. First, the complementryHOBIT Threshold - Downlink to AMPS (see Paragraph 4.2.12.11 )parametermust be exceeded, and second, handoff to an AMPS channel must be permittedby the allowable call mode.

■ Range: 0-127 for -130 to -30 dBm

■ Recommended: 44 for -95.6 dBm)

■ Default = 44

4-28 401-200-112, Issue 11 June 2001



4.2.12.8 INTPHO - Class III/IV

Indicates the minimum signal strength level (in RSSI units) to permit handoff tothis face and server group for mobile power classes III and IV. If signal strength isbelow this level handdoff will be denied. This parameter is used to screen outmeasurements from interfering mobiles. If the MPC Dependent INTPHO withVoice Channel Reservations feature has been FAF activated, this thresholdapplies to mobiles with a mobile power class of III or IV. Otherwise, this thresholdis not used.

■ Range: 1-127 for -129.2 to -30 dBm (or NULL)

4.2.12.9 Threshold (RSSI) - TDMA INLA

Indicates threshold above which other channels are searched for, when theInterference Look Ahead (INLA) optional feature is active. Recent field studieshave indicated that the value equal to Mobile Target - Window - 17dB providesexcellent performance (for example, 70 - 8 - 22 = 40 RSSI or -99 dBm).

■ Range: 1 - 127 RSSI

■ Default Value: NULL

■ Recommended Value: 40 RSSI (-99 dBm) (Lucent Technologiesrecommends starting with a threshold of 50 RSSI (-91 dBm) and workingtowards 40 RSSI as the system can accommodate it.)

4.2.12.10 TDMA Upward Hysteresis Adjustment(RSSI)

Indicates a hysteresis offset value (in RSSI units) in which the signal strength of acall being served on the outer server group of a dual cell must exceed the primarythreshold of the inner server group in order for an upward handoff to occur.

■ Range: 0 -127 (0 to 99.2 dB)

■ Default = 8

4.2.12.11 HOBIT Threshold - Downlink to AMPS

Indicates the minimum downlink signal strength level measured at the cell inIS45B units allowing the serving face to be added to the candidate list for AMPSservice only. This parameter is used in conjuction with complementry, INTPHO -parameter (see Paragraph 4.2.12.7 ). This parameter indicates the minimumuplink signal strength level measured at the cell in RSSI units allowing the servingface to be added to the candidate list for AMPS service only. When permitted bythe allowable call mode, the call is handed off from a TDMA channel to an AMPSchannel.

■ Range: 0 - 31 (IS-54B encoded units)

401-200-112, Issue 11 June 2001 4-29



■ Default: 7

4.2.12.12 HOBIT Threshold - Uplink to DualMode

Indicates the minimum uplink signal strength level measured at the cell unit inIIS45B units allowing the serving face to be added to the candidate list. This isdone to permit daul mode mobile units to HOBIT handoff to another channel onthe serving face.

■ Range: 0 - 027

■ Default: 44

4.2.12.13 HOBIT Threshold - Downlink to DualMode

Indicates the minimum downlink signal strength level measured at the mobile inRSSI units allowing the serving face to be added to the candidate list. This is doneto permit daul mode mobile units to HOBIT handoff to another channel on theserving face.

■ Range: 0 -127 (0 to 99.2 dB)

■ Default: 7 RSSI

4.2.12.14 Dynamic Power Control (DPC) State -TDMA Mobile

Indicates type of DPC state allowed for RF Power Control of TDMA mobilesserved on this logical face.

■ Range: 0 to 2

■ Recommended value:

■ 2 (boost mode); boost mode is recommended for faces with DMACvalues greater than 2 (i.e., DMAC range = 3 to 7)

■ otherwise, use 1 because, if DMAC is 2, boost will do no good forthe vast majority of TDMA mobiles (class III/IV mobiles)

4.2.12.15 Dynamic Power Control (DPC) State -TDMA Target

Indicates the nominal received signal strength (in RSSI) at the cell site from MPC-1, TDMA mobiles served on this logical face.



4-30 401-200-112, Issue 11 June 2001



■ Recommended Value: 70 RSSI (Make sure that the target value designedfor and entered here can be achieved for the VMAC setting of the sector.)For an inner server group (SG0) of a dualized antenna face, be sure thatthis target value does not compromise the desired C/I objectives.

4.2.12.16 Dynamic Power Control (DPC) State -TDMA Window

Indicates permissible range of received signal strength above or below targetbefore DPC action is taken. The minimum increment is 4 dB or 5 RSSI, whichcorresponds to the DPC step size.



■ Recommended Value: 8 RSSI

4.2.12.17 Dynamic Power Control (DPC) State -TDMA Slope

Controls the degree of mobile dynamic power control action. The greater thevalue of slope, the smaller the change in mobile attenuation for a given change inreceived signal strength at the cell site. Use of a non-zero value for slope allowsfor a wider range of received signal strength at the cell, and fewer power changesat the mobile.

■ Range: 0 to 3



4.2.12.18 BER - Control DPC Feature State

Selects type of the BER control DPC. When set to values other than 0, limits thetype of BER controlled dynamic power control activity permitted for the logicalantenna face. The power control activities are with respect to the Voice MobileAttenuation Code (VMAC) parameter that is entered on the fci form. The VMACparameter specifies a nomial mobile transmit power as a starting point at setup orhandoff. Selected value 1 limits this activity to attenuation only. Selections 2, 3and 6 limits attenuation and/or boost to the VMAC value and selection 7 removesall VMAC restriction.

■ Range:

■ 0 = off

■ 1 = attenuate only

401-200-112, Issue 11 June 2001 4-31



■ 2 = boost only within limits of VMAC

■ 3 = attenuate and boost within of limits of VMAC

■ 6 = boost only not restricted by VMAC

■ 7 = attenuate and boost not restricted by VMAC

■ (Default = 0)


4.2.12.19 Mobile BER High Threshold

Indicates the maximum BER allowed before DPC actions are taken, requiring anincrease in mobile power level to correct a high bit error rate level.

■ Range: 0-9999 for 0 to 100 percent represented in integer increments of0.01

■ Default: 0

■ Recommended Value: 500 (5%)

4.2.12.20 Mobile BER Low Threshold

Indicates the minimum BER allowed before DPC actions are taken, requiring adecrease in mobile power level when bit error rate levels are unnecessarly toolow. The decrease in mobile power level extends the battery service time and thepssibility of co-channel interfence at another cell site.

■ Range: 0-9999 for 0 to 100 percent represented in integer increments of0.01

■ Default: 0

■ Recommended Value: 200 (2%)

4.2.12.21 Amplifier Power Differential (RSSI)

Used to derive an inferred uplink signal strength at the cell based on signalstrength measurements made by the mobile.


■ Recommended Value: Correct setting of MPDIF is important to theoperation of TDMA.

MPDIF Calculation:

MPDIF= ERPm+AGc-CLc+RPGc-ERPc

■ ERPm = mobile’s maximum effective radiated power (noattenuation) +34.5 dBm

4-32 401-200-112, Issue 11 June 2001



■ AGc = cell site receive antenna gain

■ CLc = cell site cable loss

■ RPGc = cell site receive path gain

■ ERPc = cell site’s maximum (VRAL=0) effective radiated power

ALL terms are in either dB or dBmExample: ERPm = 34.5 dBm (3W), AGc = 10 dB, CLc = 1.5 dB, RPGc = 15dB, ERPc = 50 dBm

MPDIF = 34.5 + 10 - 1.5 + 15 - 50 = 8.0 dB

4.2.12.22 Delay Interval Compensation

Cell sites and mobile units both have time delay equalizers. This field indicates if theequalizer at the mobile is used.

■ Range:

■ y = on

■ n = off



4.2.12.23 MPC Correction/Offset for Class III/IVMobiles

Indicates the offset in DTH, Mobile Signal Threshold, INTPHT, and MobileSecondary thresholds for Class III and IV dual mode mobiles on Digital TrafficChannels.

■ Range: 0 to 10 IS-54B Encoded Units



■ 6 (12 dB) (when system is designed for class I mobiles)

■ 0 (when system is designed for class III/IV mobiles)

4.2.12.24 L-EDRU DVCC Verification Active

Indicates if the L-EDRU DVCC Verification with RSSI feature is activated perlogical face.

■ Range: y or n

■ Default = n

401-200-112, Issue 11 June 2001 4-33



4.2.12.25 Hybrid MAHO/Digital Locate TDMAHandoff Algorithm Active

Allows Hybrid MAHO/Digital Locate TDMA Handoff Algorithm feature to beactivated and deactivated per logical face.

■ Range: y or n

■ Default = n

4.2.12.26 Append MAHO Candidates to HybridMAHO/Digital Locate

Indicates if the MAHO candidates should be appended to the list of good handoffcandidates when any of the following conditons are true.

a. The candidate is in the MAHO handoff candidate list, but the serving cell doesnot receive a digital locate response from the cell of the candidate.

b. The candidate is in the MAHO handoff candidate list, but the signal strengthmeasurement is 0 from the cell of the candidate.

c. The candidate is in the MAHO handoff candidate list, but the serving cell doesnot send out a digital locate request.

■ Range: y or n

■ Default = n

4.2.12.27 Up/Downlink Ranking Method forHybrid MAHO/Digital Locate

Allows the service provider to select either uplink or downlink normalized signalstrength.

Downlink normalized signal strength is based on the mobile measurement of theneighbor sector MAHO channel signal strength and is computed for eachneighbor on the MAHO neighbor list.

Uplink normalized signal strength is based on a neighbor sector L-EDRUmeasurement of the mobile signal strength and is computed for the subset ofneighbors on the MAHO neighbor list.

■ Range: (u) plink or (d) ownlink

■ Default = uplink

4.2.12.28 TDMA Periodic Locate Type

Allows for either Periodic Best Server Locate (pbsl) or Periodic Cross-FaceLocate (pcfl) to be active per logical face.

■ Range: blank, pbsl or pcfl

4-34 401-200-112, Issue 11 June 2001



■ Default = pbsl

4.2.12.29 Thresholds: Mobile Signal

Establishes the coverage area, or footprint, for the sector. This threshold value iscompared to the signal strength measured and reported by the mobile. If thereported signal strength is less than this threshold value, a handoff trigger isgenerated.

With MAHO, handoffs are initiated according to cell and mobile translations. Toprevent ping-ponging handoffs, be consistent when assigning mobile translationsand cell translations. A mobile-initiated handoff (generated because of a mobiletranslation) may result in a call arriving at the new cell only to be handed off againbecause of a cell translation. For example, if a handoff occurs because the mobilesignal falls below the mobile signal threshold, and the call arrives at the new cellbelow the cell Primary threshold, the call may ping-pong.

■ Range: 0 to 31 IS-54B Encoded Units (equivalent to 2dB)


■ Recommended Value (two approaches may be used):

■ Determine the power level in dBm at which a handoff should beinitiated. Use the table below to determine the corresponding IS-54BEncoded Units to enter as the value for this field.

■ Use a value of 31 for single-server group cell sites and SG1 of dual-cell sites to generate locate triggers at the Mobile MeasurementProcessing Interval. Use a value of 19 for SG0, in a fully dualizedconfiguration.

Table 4-1 Power Level (dBm) to IS-54B Encoded Units Conversions

Downlink Mobile-Meas.Signal Strength




-113 dBm 0 IS-54BEncoded Units

-81 dBm 16

-111 dBm 1 -79 dBm 17

-109 dBm 2 -77 dBm 18

-107 dBm 3 -75 dBm 19

-105 dBm 4 -73 dBm 20

-103 dBm 5 -71 dBm 21

401-200-112, Issue 11 June 2001 4-35



4.2.12.30 Thresholds: Mobile Secondary

Sets conditions for appending candidates to the MAHO candidate list. When thecandidate list has fewer than three entries AND the mobile signal strength isbelow the Secondary threshold, faces with signals less than the DecisionThreshold (DTH) are added to the candidate list.



4.2.12.31 Thresholds: TDMA Locate ReplyThreshold

Specifies the threshold (in RSSI units) to which the L-DRU signal strengthmeasurements for handoffs are compared at this (neighbor) cell site. If thereceived signal strength is above this threshold, the mobile is considered to bewithin the RF coverage area of the neighbor cell. If the received signal strength isbelow this threshold, the mobile is considered to be outside the RF coverage areaof the neighbor cell.

■ Range: 0 to 127 RSSI

■ Default Value: if blank, value is set to equal that of INTPHO value

-101 dBm 6 -69 dBm 22

-99 dBm 7 -67 dBm 23

-97 dBm 8 -65 dBm 24

-95 dBm 9 -63 dBm 25

-93 dBm 10 -61 dBm 26

-91 dBm 11 -59 dBm 27

-89 dBm 12 -57 dBm 28

-87 dBm 13 -55 dBm 29

-85 dBm 14 -53 dBm 30

-83 dBm 15 -51 dBm 31

Table 4-1 Power Level (dBm) to IS-54B Encoded Units Conversions





4-36 401-200-112, Issue 11 June 2001



4.2.12.32 Digital Voice Mobile Attenuation Code

Indicates the nominal Voice Mobile attenuation code assigned to dual-modemobiles on TDMA channels served by this LAF.

■ Range: 0 to 10 (4dB steps 0 to 40 dB)


4.2.12.33 Minimum Handoff Interval for TDMA

Used by the TDMA Handoff Based on Interference (HOBIT) feature. It defines theminimum time that a call is required to be on a channel before a handoff based onBER or FER can be triggered. Setting this translation to 0 disables the HOBITfeature for this face.

■ Range: 0 to 75

■ Default Value: 2 seconds


4.2.12.34 Mobile Reported Signal StrengthAveraging Samples - TDMA

Number of samples used to determine the average mobile-reported signalstrength.

■ Default Value: 6 (samples)


4.2.12.35 Mobile Reported BER AveragingSamples

Number of samples used to determine the average mobile-reported Bit Error Rate(BER).

■ Default Value: 2 (samples)

■ Recommended Value: 3 -5

4.2.12.36 TDMA DTX with Comfort NoiseInsertion Active

Enable TDMA discontinuous transmission (TDMA DTX) with Comfort NoiseInsertion Active (CNI) feature on LAF. This feature permits a TIA/EIA-136Acompatible mobile subscribers and subscribers with modified IS-136A mobiles toincrease battery life by as much as 30 percent. This is done by truncating themobile time slot transmit period when the subscriber is not speaking.

401-200-112, Issue 11 June 2001 4-37





4.2.12.37 Server Group Channel Selection (SGCS)

When a channel fixed to a server group is unavailable, this parameter specifies if,and under what conditions, a call setup or handoff is switched to the other servergroup on the sector (physical antenna face). If EDRU radio transmitted ouput isrouted through an auto-tuned cavity combinner, valid entry is forced to select ownserver group channels only. When the valid entry for this parameter is left blank,selection defults to the SGCS value selected on the ecp form.

■ Valid entries:

1. Blank

2. Select channel independent of server group designation

3. Select own server group channels only

4. Select other server group channels after own server groupchannels.

4.2.12.38 MCCLL Maximum Candidate ChannelList Length (MCCL)

Specifies the maximum number of channels placed on the FLCA candidatechannel list.The channels on this list are FLCA candidate channels for call setupand call handoff. This parameter is set on the ecp form to define the MCCLLvalue for all the LAFs in the ECP domain. A similar parameter can be found on thefci form to define the MCCLL value for a LAF. The system will iterate through theselection and acceptance process for each candidate channel until the MCCLLnumber is reached or until the number of acceptable channels are exhausted. Theultimate number of channels on the candidate channel list is defined as theMAXCHAN value. When the valid entry for this parameter is left blank, selectiondefults to the MCCL value selected on the ecp form.

■ Range: Blank: 1 to 4

4.2.12.39 Maximum Interference Threshold forCall Setup - Uplink (dB)

Defines maximum uplink interference signal strength allowed for call setup. Whenthe range for this parameter is left blank, selection defults to the MaximumInterference Threshold for Call Setup - Uplink (dB) value selected on the ecpform.

■ Range: Blank: -130 dB to -57 dB

4-38 401-200-112, Issue 11 June 2001



4.2.12.40 Maximum Interference Threshold forCall Setup - Downlink (dB)

Defines maximum downlink interference signal strength allowed for call setup.When the range for this parameter is left blank, selection defults to the MaximumInterference Threshold for Call Setup - Downlink (dB) value selected on the ecpform.

■ Range: Blank, -113 dB to -53 dB

4.2.12.41 Maximum Interference Threshold forhandoff - Uplink (dB)

Defines maximum uplink interference signal strength allowed for handoff. Whenthe range for this parameter is left blank, selection defults to the MaximumInterference Threshold for Handoff - Uplink (dB) value selected on the ecp form.


4.2.12.42 Maximum Interference Threshold forhandoff - Downlink(dB)

Defines maximum downlink interference signal strength allowed for handoff.When the range for this parameter is left blank, selection defults to the MaximumInterference Threshold for Handoff - Downlink (dB) value selected on the ecpform.


4.2.12.43 Mobile Assisted Handoff List

This section discusses the translations associated with up to 24 neighbors of thisLAF. Some of the recommended values depend on whether or not this LAF is aninner server group (SG0) or an outer server group (SG1). Where appropriate, twosets of recommendations will be given to cover these two cases.

Fields:

1. Cell Site: Neighbor cell site number

2. PAF: Physical antenna face number associated with the neighbor celldefined in (1) above

■ 0=omni, 1=alpha, 2=beta, 3=gamma, 4=delta, 5=epsilon,6=zetaSG0 (Server Group 0) Bias

3. SG0 (Server Group 0) Bias. Specifies the bias value from this serving LAFto the handoff target cell server group 0 LAF. The recommended valuesdepend on whether this serving LAF is SG0 or SG1 as mentioned above.

401-200-112, Issue 11 June 2001 4-39



■ Range: -31 to 31 IS-54B Encoded Units

■ Recommended Values:

Table indicates the recommended values for SG0 Bias as a function of theserving face. A blank space in the table means that the particular type ofhandoff is either inappropriate from the serving LAF indicated to SG0 of thetarget cell, or it is undefined (for example, upward handoff is not definedfrom a SG0 LAF).

4-40 401-200-112, Issue 11 June 2001



To ensure that the system does not attempt a handoff to an unequippedSG0 LAF, Lucent Technologies recommends a bias of +31 for unequippedSG0 LAFs.

4. SG1 Bias (Server Group 1)

Specifies the bias value from this LAF to the handoff target cell server group1 LAF. The recommended values depend on whether this serving LAF isSG0 or SG1 as mentioned above.

■ Range: -31 to 31 IS-54B Encoded Units


In the following table, N/A means that the particular type of handoff is eitherinappropriate from the serving LAF indicated to SG1 of the target cell, or it isundefined (for example, downward handoff is not defined for SG1-SG1handoffs)

5. SG0/1 VMAC (Voice Mobile Attenuation Code) (not required for 6.0+ cells)

6. SG0/1 DTH (Decision Threshold)

Defines the signal level threshold above which secondary candidates areadded to the candidate list. All neighbors cells measured above the specifiedDecision Threshold (DTH) are added to the candidate list; those below theDTH are eliminated (except when TDMA mobile-reported serving signalstrength is below Mobile Secondary Threshold as defined above).

Table 4-2 Recommended MAHO Bias Values for Dual Server Group Cell

Serving LAF From SG0 (Inner) From SG1 (Outer)

Target LAF To SG0 To SG1 To SG0 To SG1

Upward (same face) 4

Upward Cross Face 3

Cross Face 3 3 3 3

Inter Cell 3 3 3 3

Downward (same sector) 1

Downward Cross Face 3

Inner Cross Face (within SG0) 7

Unequipped LAF 31 31 31 31

401-200-112, Issue 11 June 2001 4-41



Range: 0 to 31 IS-54B Encoded Units

Recommended Value:

■ 0, except for SG0 cross-face handoffs on dual cells

■ MOTHRESH + 4, for SG0 cross-face handoffs of a dual SG cell

7. INTPHT (Interference Protection on Handoff Threshold for TDMA)

If a beacon channel is measured below this threshold, the sector will beineligible to receive a handoff.


■ Default Value: 7 (-99 dBm)


8. SG0/1 VC (Voice Channel)

Indicates the Voice Channel technologies available on neighbor LAF. Thistranslation is used to determine if a neighbor cell supports Allowable CallMode; it should be left blank for unequipped server groups.

■ Range:

■ a = AMPS

■ t = TDMA

■ at = AMPS and TDMA

■ Default Value: blank

9. SG0/1 SBI (Shortened Burst Indicator)

Specifies if shorted burst or normal burst is used for handoffs to the servergroup indicated.

■ Definitions:

■ 0 = normal burst

■ 1 = normal burst

■ 2 = shortened burst



■ 0 and 1 are used interchangeably for cross-face and mostinter-cell handoffs.

■ 2 for handoffs between cells of significantly differentdiameters (greater than 10 miles).

4-42 401-200-112, Issue 11 June 2001



10. MCN (MAHO Channel Number)

Specifies the Mobile Assisted Handoff (MAHO) channel number used formobile signal strength measurements on the physical antenna face of aneighbor cell. (For a discussion of MAHO channels and beacon channels,see Chapter 1.)

11. DCS (Digital Cellular Switch)

Defines the Digital Cellular Switch associated with this neighbor entry whenthe neighbor cell is on a different switch.

12. ECP (Executive Cellular Processor)

Defines the Executive Cellular Processor associated with this neighbor entrywhen the neighbor cell is on a different ECP/DCS.

13. System ID

Defines the System ID associated with this neighbor entry when theneighbor cell is on a different ECP/DCS.

4.2.13 SHTG (Speech Handler Trunk Group)Form

This form identifies the vocoder algorithm associated with each speech handlertruck group.

4.2.13.1 DCS-E Switch Identification

Identifies the 5ESS-2000 DCS switch to be used. This value should be the sameas that on the corresponding TDMA packet pipe trunk group (tpptg) form.

■ Range 1 through 16

4.2.13.2 Trunk Group Number

Indicates speech handler physical trunk group number.

■ Range: 18-254 for G2 DCS or 1-2000 for 5ESS(R)-2000 Switch DCS

4.2.13.3 Technology Type

This form is used both for TDMA as well as CDMA. The TDMA technology mustbe specified.

■ Range: TDMA and CDMA

401-200-112, Issue 11 June 2001 4-43



4.2.13.4 Service Type

Specifies vocoder algorithm.

Range: VSELP and ACELP

4.2.14 SUB (Subscriber and Feature Information)Form

The SUB form defines subscriber-specific information such as directory number,mobile type, optional end-user features, etc.

4.2.14.1 Mobile Directory Number Type

Identifies the Mobile Directory Number (DN) type.

Type "t" is used to identify the TDMA dual-mode mobile as a TDMA test mobile.

This translation is used in conjunction with the ECP form. If the Test Mode Activefield in the ECP form is set to “y,” only mobiles with this field set to "t" use TDMAchannels. All other dual-mode mobiles (DMMs) will use AMPS channels.

4.2.14.2 Short Messess Service: TerminationRestricted

Indicate the default restrictions on delivery of SMS messages to a roaming mobileif the SMS termination restrictions are not present in the IS-41 registrationnotification. The IS-41 registration notification, is a message received during ttheprocessing of a roaming mobile registration. A “y” enter in this field will block theIS-41 message forcing the default restriction.

■ Range: y or n

■ Defult: n

4.2.14.3 Short Messess Service: OriginationRestricted

Indicate the default restrictions on acceptance of SMS messages from a roamingmobile if the SMS origination restrictions are not present in the IS-41 registrationnotification. The IS-41 registration notification, is a message received during ttheprocessing of a roaming mobile registration. A “y” enter in this field will block theIS-41 message forcing the default restriction.

■ Range: y or n

■ Defualt: y

4-44 401-200-112, Issue 11 June 2001



4.2.15 TPPTM (TDMA Packet Pipe TrunkMember) Form

This form is to be filled out for each EDRU radio within a cell where the switchbased TDMA vocoder feature is implemented. This feature relocates theexecution of the vocoder and echo canceller algorithms from the EDRU to thedigital cellular switch (DCS). As a result, voice message compression anduncompression is performed at the DCS to reduce the number of trunks requiredto transfer voice data between the cell and the DSC. Voice data from the threeDTC channel time slots handled through a single EDRU is inserted into dataparcels that are identified as packets. The packets from the three time slots arethen transferred between the cell and the DCS over a packet pipe trunk which isone DS0 on the T1 line. The packet pipes are grouped within a packet pipe trunkgroup where each packet pipe is referred to as a TDMA packet pipe trunkmember. There are up to 64 TDMA packet pipe trunk members in each packetpipe truck group.

4.2.15.1 DCS-E Switch Identification

Identifies the 5ESS-2000 DCS switch to be used. This value should be the sameas that on the corresponding TDMA packet pipe trunk group (tpptg) form.


4.2.15.2 Packet Pipe - Trunk Group Number

Identifies the packet pipe trunk group number of the physical trunk group. Thisvalue should be the same as that on the corresponding tpptg form. The trunkgroup number must be unique for all the cells within the MSC coverage area.

■ Range: 18-254 for G2 DCS or1-2000 for 5ESS(R)-2000 Switch DCS

4.2.15.3 Packet Pipe - Trunk Member Number

Identifies the TDMA packet pipe trunk member number within a trunk group.


4.2.15.4 Trunk Status

Identifies the unequipped, growth, or equipped status of the packet pipe trunkgroup member. When this field is set to u (unequipped), the DS1 Board Numberand DS0 Channel fields are set to NULL. When this field is set to e (equipped) org (growth), the DS1 Board Number field must be set to a valid value, and two toeight unique DS0 channels must be entered into the DS0 Channels fields.

■ Range: u = unequipped, g = growth, or e = equipped

■ Default = u

401-200-112, Issue 11 June 2001 4-45



4.2.15.5 Switching Module

Identifies the switching module the associated trunk group is assigned to on the5ESS-2000 Switch DCS.


4.2.15.6 Server Group

Identifies the cell site server group (primary or secondary) associated with thetrunk group member.

■ Range: 0 = primary (preferred group), 1 = secondary (dual-cellconfiguration only)

4.2.15.6.1Default = 0

4.2.15.7 Physical Antenna - Receive

Identifies the physical cell site receive antenna face number of associated trunkgroup member. Directional antennas (alpha, beta, gamma, delta, epsilon, zeta)are numbered clockwise from antenna 1 (alpha).

■ Range: 0 = omni, 1 = alpha, 4 = delta, 2 = beta, 5 = epsilon, 3 = gamma,and 6 = zeta

■ Default = 0

4.2.15.8 Physical Antenna - Transmit

Identifies the physical cell site transmit antenna face number of associated trunkgroup member. Directional antennas (alpha, beta, gamma, delta, epsilon, zeta)are numbered clockwise from antenna 1 (alpha).

■ Range: 0 = omni, 1 = alpha, 4 = delta, 2 = beta, 5 = epsilon, 3 = gamma,and 6 = zeta

■ Default = 0

4.2.15.9 Packet Pipe Data Rate Kbps

Identifies the data transmission rate for associated packet pipe trunk member.

■ Range: 56 = 56 Kbps and 64 = 64 Kbps

■ Default = 64

4-46 401-200-112, Issue 11 June 2001



4.2.15.10 Connection - DS0

Identifies the voice EDRU radio connection DS0 assignments for associatedpacket pipe group member.

■ Range: 1 to 24

4.2.15.11 Connection - DS1

Identifies the DS1 board that contains the DS0 channel units for the associatedpacket pipe trunk group member. DS1 0 is reserved for the first data link on a celland is not permitted to be assigned on this form.

■ Range:

■ NULL when status is “u”, 1-13 when status is “e” or “g”

4.2.15.12 Voice Radio Information — Number

Identifies cell site EDRU radio number

■ Range 1 to 191

4.2.15.13 Voice Radio Information —Timeslot 1,Timeslot 2, Timeslot 3

Assign the DTC channel on radio timeslot n (where n = 1, 2, or 3) to theassociated packet pipe. This parameters identifies the three radio time slots asDTC channels as opposed to DCCH or beacon channels. A no (n) value shouldbe entered in any of the three Timeslot fields when the radio time slot isdesignated for either DCCH or beacon channel.

■ Range y and n

■ Default y

4.2.15.14 Voice Radio Information —Type

Defines the voice radio type which must by an EDRU radio. This is not achangeable parameter. For switch based TDMA vocoder systems this parametermust always be EDRU.

■ Default EDRU

401-200-112, Issue 11 June 2001 4-47



4.2.15.15 Voice Radio Information —FrameNumber

Identifies the radio frame number where the EDRU associated with this trunkgroup member is located. The radio frame number is the cabinet number were theEDRU radio located, starting with the primary cabinet which is designated framenumber 0.

■ Range: 0 - 2 (Note: The maximum number of cabinets at the cell siteinstallation may be lower than the value indicated by the range.)

4.2.15.16 Voice Radio Information —ShelfNumber

Identifies the radio shelf number where the EDRU associated with this trunk groupmember is located.

■ Range: 0 - 5 (Note: The maximum number of shelves within the cabinetat the cell site installation may be lower than the value indicated by therange.)

4.2.15.17 Voice Radio Information —Slot Number

Identifies the radio slot number where the EDRU associated with this trunk groupmember is located.

■ Range: 2 - 25

4.2.15.18 Voice Radio Information —Channel

Identifies the radio frequency channel that the EDRU radio associated with thistrunk group member is assigned.

■ Range:

— For cellular systems, the trunk group member associated EDRUradio transmits at 869-896 MHz and receives at 824-851 MHz.Cellular channels are numbered from 1 through 866 and from 991through 1023.

— For PCS systems, the trunk group member associated EDRU radiotransmits at 1855- 1910 MHz and receives at 1930-1990 MHz. PCSchannels are numbered from 1 through 1999.

4.2.15.19 Voice Radio Information — Beacon

Designates that a time slot on the EDRU radio is used as a beacon channel asopposed to a DTC channel. The beacon designation will instruct the system toalways keep the radio on. A beacon channel is used in place of a MAHO channelwhich is provided by the DCCH channel.By its nature, the DCCH or beaconchannel must always be on.

4-48 401-200-112, Issue 11 June 2001



■ Range: on/off

4.2.15.20 Voice Radio Information — DVCC

Identifies a digital verification color code transmitted by the EDRU and returned bya mobile unit to indicate the mobile unit presence on a TDMA channel.

■ Range: 1 to 255 or NULL

■ Recommended Value: Cell site number (except 3, 45, and 162)

4.2.15.21 Voice Radio Information — MobilePower Class

Specifies the mobile power class for which the EDRU radio is being reserved. Theterm reserved means that the EDRU voice radio is used predominately to servemobiles with the specified mobile power class. Reserved does NOT mean that theEDRU voice radio can only be used by mobiles with the specified mobile powerclass.

Note: To facilitate the provisioning of this field on a system-wide basis, a toolcalled DBapxvcr is provided in /1apx10/testbin. DBapxvcr accepts up to 10 cellsites and up to 10 voice radio channels as input to reserve those voice channelsfor a specific mobile power class.

Using this tool provides a more efficient interface for provisioning Mobile PowerClass reservations compared to the traditional interactive and/or text operation ofapxrcv.

■ Range:

— 0 = no reservation

— 1 = Class I/II

— 2 = Class III/IV

■ (Default = 0)

4.2.15.22 Voice Radio Information — LACNumber

Used only in cellular system to identify the linear amplifier controller used by theEDRU radio associated with the trun group member

4.2.15.23 Dynamic Channel Allocation - Active

Indicates whether the Dynamic Channel Allocation (DCA) feature is active forassociated cell site trunk member radio. The DCA feature minimizes radiochannel frequency interference by preventing radios that are assigned to the

401-200-112, Issue 11 June 2001 4-49



same frequency in different cells in close proximity from operating simultaneously.Up to four AMPS, DRU and EDRU radios that are assigned to the same frequencyin different cells may be identified on a DCA Interfering TNN list. The EDRU radiosmust be located in cells where the switch based TDMA vocoder switch basedTDMA vocoder feature is not implemented. If the EDRU radio is located in cellswhere the switch based TDMA vocoder feature is implemented, only one EDRUradio and one RCU or DRU radio may be identified. When a voice channel isneeded to service a mobile, the voice channel selection algorithm checks the DCAactive status of the radio. If the status is active and any radio on its TNN list iscurrently active, the voice channel selection algorithm will select another radio.

■ Range: y or n

■ Default = n

4.2.15.24 DCA Interfering TNNs

Radios on the DCA InterferingTNN list are identified by their cell site trunk switchidentification (Switch ID) number, the radio trunk group (Trk Grp), trunk member(Trk Mbr), and packet pipe (TDMA PP) numbers. To extend the DCA capabilitiesbeyond the DCS and MSC boundries, the DCA InterferingTNN list also identifiedthe DCS identification (DCSID), ECP identification (ECPID), and systemidentification (SID) numbers.

4.2.16 TPPTG (TDMA Packet Pipe Trunk Group)Form

This form contains the information for the TDMA packet pipe trunk data groupbase. This form is to be fill out when the switch based TDMA vocoder feature isimplemented. This feature relocates the execution of the vocoder and echocanceller algorithms from the EDRU to the digital cellular switch (DCS). As aresult, voice message compression and uncompression is performed at the DCSto reduce the number of trunks required to transfer voice data between the celland the DSC.

4.2.16.1 Switch Identification

Identifies the 5ESS-2000 DCS switch to be used. This value should be the sameas that on the corresponding TDMA packet pipe trunk member (tpptm) form.

■ Range: 1 through 16

4.2.16.2 Trunk Group Number

Identifies the packet pipe trunk group number of the physical trunk group. Thisvalue should be the same as that on the corresponding tpptm form. The trunkgroup number must be unique for all the cell within the MSC coverage area.

4-50 401-200-112, Issue 11 June 2001



■ Range: 18-254 for G2 DCS or1-2000 for 5ESS(R)-2000 Switch DCS

4.2.16.3 Cell Site Number

Identifies the cell site were the EDRU radios a located.

■ Range: 1 through 384

4.2.16.4 Number of Trunks

Indicates the total number of TDMA packet pipe trunk members (TPPTM) in thepacket pipe trunk group (TPPTG). A TPPPG must be able to accomodate themaximum number of cell site trunks, which is 192. Each DTC handled through aEDRU radio requires a cell site trunk. A cell site trunk should not be confused witha TDMA packet pipe trunk member which carries the three DTC channels. Thus,the maximum number of TPPTM in a TPPTG is 64 (192/3).

■ Range: 0 through 64, 0 indicates that there are no packet pipe trunks andthe switch based TDMA vocoder feature is not implemented.

■ Default: 0

4.2.17 Summary of DTC Performance DatabaseTranslations

The following table gives a summary of the forms and RC/V translations for DTC.

Table 4-3 DTC Translations Summary

Translation Range Default ValueRecommended

Value

ECP FormMaximum No. of Mobile RequestedCall Mode Changes

0 to 3 1 3

Mobile Assisted Handoff Bias - TDMA -31 to 31 IS-54BEncoded Units (IEU)

3 (~6 dB) 3

INLA Threshold - TDMA (RSSI) 0 to 127 RSSI 31 RSSI; seedescription,Sec.4.2.1.3

40-50

TDMA Test Mode Active n, y; see description,Sec. 4.2.1.4

n

Differential Billing for Digital and Ana-log time

y, n n

401-200-112, Issue 11 June 2001 4-51



Append Basic Digital Module to theAMA Record

y, n n

CELL2 FormAntenna Face Trunk Group List -TDMA

18 to 254 for DEFIN-ITY; 1 to 999 for5ESS-2000; or NULL

Cell Generic - Version Name See description, Sec.4.2.2.2

Cell Generic - R5 Compatible read-only; n=R5 notinstalled at cell, y=R5installed at cell

Determined bygeneric name(above)

IS-54B Allowable Call Mode Override y, n y y

Number of Simultaneous NVMs -TDMA

1 to 200 10 See description,Sec. 4.2.2.5

Voice Out of Service Limit (%)- TDMA 25 - 100 25 See description,Sec. 4.2.2.6

INLA Threshold -TDMA (RSSI) 0 to 127 RSSI 31 40- 50

Cell Site Optional Features y, n; see description,Sec. 4.2.2.8

n

ARR is Available for: Beacon Radio y, n n y

ARR is Available for: L-EDRU Radio y, n y y

Authentication is Available on: AnalogControl Channel

y, n n

Number of Time Slots for DVCC Pres-ence

1 to 5 2 2

DVCC Detection Timeout Time Slots 1 to 100 50 (2 seconds) 50

Bit Error Rate Threshold (%) 0 to 7 0 3

Frame Error Rate Threshold (%) 0 to 100 20 20

Mobile Assisted Handoff Bias -31 to 31 IS-54B IEU Blank (ECPvalue used)

3

Mobile Requested Call Mode Change y, n y y

DVCC Verification Active y, n n y

Digital Locate Radio Equipage blank, l-dru (readonly)

blank

Network Transmission Level (dB) - RXfor DRU/EDRU

-15 to +3 0 0

Network Transmission Level (dB) - TXfor DRU/EDRU

-15 to +3 0 0

Handoff at Optimum Power - TDMA y, n n y

NNBR FormHandoff/Setup Optimum Power -TDMA

y, n n y



Value

4-52 401-200-112, Issue 11 June 2001



CEQCOM2 FormTDMA Periodic Best Server Locate(sec.)

0 to 75 seconds 0 3

TDMA Measurement Processing Inter-val

2 seconds 4 to 5

TDMA RTU Status u = unequipped; g =growth; e = equipped

e

TDMA RTU Slot 11 (no change field) 11 11

TDMA RTU DVCC Range 1 to 255; orNULL

See description,Sec. 4.2.4.3

CEQSU2 FormColor Codes - Digital 0 to 3 0 See description,

Sec. 4.2.5.1Color Codes - 1st TDMA SupervisoryDigital


Color Codes - 2nd TDMA SupervisoryDigital


CEQFACE FormTDMA Voice Radio Attenuation Level 0 See description,

Sec. 4.2.6.1TDMA Fade Timer 10 to 100 (200 milli-

second increments)100 (20 sec-onds)

50-100 (20 sec-onds); set sameas AMPS FadeTimer

Cell Site Attenuation Code 0 to 7; see descrip-tion, Sec. 4.2.6.3

0 Equal to Cell SiteAttenuation Code

CNTG FormAnalog Option on Digital Terminations y, n n n

CTG FormTechnology Type amps, tdma tdma

ITG FormAnalog Option on Digital Terminations y, n n

LTG FormAnalog Option on Digital Terminations y, n n

CTM FormVoice Radio - Channel Number See description,

Sec. 4.2.11.1Voice Radio - Timeslot (TDMA only) 1 to 3, or NULL

Voice Radio - Beacon on, off off



Value

401-200-112, Issue 11 June 2001 4-53



Voice Radio - Radio Type NULL, arcu (AMPSradio), sbrcu (SingleBoard AMPS radio),tdru (TDMA DRU)

arcu

Voice Radio - Slot Number 2 to 12 See description,Sec. 4.2.11.6

TDMA Digital Verification Color Code 1 to 161, 163 to 255(TDMA only)

Cell site number(except 162)

FCI FormTDMA Sequential Trunk Hunt y, n n y

Threshold (RSSI) - TDMA INLA 1 to 127 RSSI Blank 40-50

Dynamic Power Control State (DPC)TDMA Mobile

0 to 2 See descrip-tion

2

Dynamic Power Control State (DPC)TDMA Target

0 to 127 RSSI 92 70; see descrip-tion, Sec.4.2.12.15

Dynamic Power Control State (DPC)TDMA Window

Minimum incrementis 4dB or 5 RSSI

15 8

Dynamic Power Control State (DPC)TDMA Slope

0 to 3 0 0

Amplifier Power Differential (RSSI) 12 See description,Sec.4.2.12.21

Delay Interval Compensation y, n y y

MPC Correction/Offset for Class III/IVMobiles

0 to 10 IEU 0 See description,Sec.4.2.12.23

L-EDRU DVCC Verification Active y, n n

Hybrid MAHO/Digital Locate TDMAHandoff Algorithm Active

y, n n

Append MAHO Candidates to HybridMAHO/Digital Locate

y, n n

Up/Downlink Ranking Method forHybrid MAHO/Digital Locate

u, d u

TDMA Periodic Locate Type pbsl/pcfl pbsl

Threshold: Mobile Signal 0 to 31 IEU (equiva-lent to 2dB)

1 See description,Sec.4.2.12.25

Threshold: Mobile Secondary 0 to 31 IEU (equiva-lent to 2dB)

14

Threshold: TDMA Locate Reply(RSSI)

0 to 127 RSSI, orNULL;

50



Value

4-54 401-200-112, Issue 11 June 2001



Digital Voice Mobile Attenuation Code 0 to 10 IEU; seedescription, Sec.4.2.12.32

2

Minimum Handoff Interval for TDMA(sec.)

0 to 75 2 seconds 3

Mobile Reported Signal Strength Aver-aging Samples - TDMA

6 (samples) 3

Bit Error Rate Averaging Samples -TDMA

2 (samples) 2

Mobile Assisted Handoff List See description,Sec.4.2.12.43

SHTG FormDCS-E Switch Identification 1 to 16

Trunk Group Number 18-254 for G2 DCSor 1-2000 for5ESS(R)-2000Switch DCS

Technology Type TDMA, CDMA

Service Type VCELP, ASELP

DCS-E Switch Identification 1 to 16

Trunk Group Number 18-254 for G2 DCSor 1-2000 for5ESS(R)-2000Switch DCS

Technology Type TDMA, CDMA

Service Type VCELP, ASELP

SUB FormMobile Directory Number Type See description,

Sec. 4.2.14.1

TPPTM FormDCS-E Switch Identification 1 to 16

Packet Pipe - Trunk Group Number 18-254 for G2 DCSor 1-2000 for5ESS(R)-2000Switch DCS

Packet Pipe - Trunk Member Number 1 to 64

Trunk Status u,g, e, u

Switching Module 1 - 192 (or NULL)

Server Group 0, 1 0



Value

401-200-112, Issue 11 June 2001 4-55



Physical Antenna - Receive see descriptionSec 4.2.15.7

0

Packet Pipe Data Rate Kbps 56 = 56 Kbps,64 = 64 Kbps

64

Connection - DS0 1- 24

Connection - DS1 see descriptionSec 4.2.15.11

Voice Radio Information — Number 1 to 191

Voice Radio Information —Timeslot 1,Timeslot 2, Timeslot 3

y, n y

Voice Radio Information —Type EDRU

Voice Radio Information —FrameNumber

0 to 2

Voice Radio Information —Shelf Num-ber

0 to 5

Voice Radio Information —Slot Num-ber

2 to 24

Voice Radio Information —Channel see descriptionSec 4.2.15.18

Voice Radio Information —Beacon on/off

Voice Radio Information —DVCC see descriptionSec 4.2.15.20

Voice Radio Information — MobilePower Class

see descriptionSec 4.2.15.21

Voice Radio Information — LAC Num-ber

Dynamic Channel Allocation - Active y, n

DCA Interfering TNNs see descriptionSec 4.2.15.24

TPPTG FormSwitch Identification 1 to 16

Trunk Group Number see descriptionSec 4.2.16.2

Cell Site Number 1 to 122

Number of Trunks 0 to 64 0

TPPTM FormDCS-E Switch Identification 1 to 16

Packet Pipe - Trunk Group Number 18-254 for G2 DCSor 1-2000 for5ESS(R)-2000Switch DCS



Value

4-56 401-200-112, Issue 11 June 2001



4.3 DCCH Performance DatabaseSettings

Provides the translation entries required to implement DCCH functionality. Thesetranslations are entered via the AUTOPLEX Recent Change/Verify (RC/V)database access system. Entry of DCCH translations can also be performed byusing the Translations Entry Assistant (TEA) Feature.

Translation Entry Assistant (TEA)

Translation Entry Assistant (TEA) is a tool that provides an Graphical UserInterface for entering DCCH reselect translations into the RC/V database,bypassing the RC/V screens. TEA simplifies and expedites translation entry.

TEA uses a relational database and a PC-hosted user interface that allow:

■ Data entry

■ Population rule checking

■ Parameter calculations

■ Integration of information across ECPs

TEA simplifies data entry by replacing the data-oriented organization of RC/Vforms with a new, easy-to-use design that supports specific tasks. One TEAWindow replaces several RC/V screens, and one entry on a TEA screen canupdate entries on several RC/V screens. In particular, this simplifies the ongoingadministration of DCCH reselection lists. For details on TEA, contact your LucentTechnologies Account Executive.

Packet Pipe - Trunk Member Number 1 to 64

Trunk Status u,g, e, u

Switching Module 1 - 192 (or NULL)

Server Group 0, 1 0

Physical Antenna - Receive see descriptionSec 4.2.15.7

0

Packet Pipe Data Rate Kbps 56 = 56 Kbps,64 = 64 Kbps

64

Connection - DS0 1- 24

Connection - DS1 see descriptionSec 4.2.15.11



Value

401-200-112, Issue 11 June 2001 4-57



Translation Forms

The translations listed below are grouped by their associated forms. Theinformation includes a description of each translation, along with its range, defaultvalue, and a recommended value.

Forms covered in this section include:

■ ECP (Executive Cellular Processor)

■ NET (Cellular Network)

■ CGSA (Cellular Geographic Service Area)

■ CELL2 (Series II Cell Site Database)

■ CEQCOM2 (Series II Cell Equipage Common)

■ CEQFACE (Cell Equipage Common Face)

■ CEQSU2 (Series II Cell Equipage Setup)

■ FCI (Face Code Information)

■ DCCH (Digital Control Channel)

■ RESEL (Reselection List for Control Channels)

4.3.1 ECP (Executive Cellular Processor) Form

The ECP form contains translations that apply to all cells on an ECP.

4.3.1.1 Page Only if MS (Mobile Station) LastAccessed on DCCH

When set to ” y,” the system will page an IS-136 mobile for Short Message Service(SMS) only if the mobile last accessed the system via a DCCH.

■ Range: y or n


4.3.1.2 DCCH Activity Timeout Interval

Sets activity time limit (in minutes) when using Mobile Activity Supervision. If amobile is inactive for this interval, and DCCH Activity Timeout Allowed translationis set to “y,” the inactive mobile will NOT be paged. The DCCH Activity TimeoutInterval translation must be set to a value greater than the time-basedAutonomous Registration interval.

■ Range: 10 to 2,880 minutes

4-58 401-200-112, Issue 11 June 2001




4.3.1.3 DCCH Activity Timeout Allowed

Determines if an IS-136 mobile is to be made inactive because it has notaccessed the system within the DCCH Activity Timeout Interval. When set to “y,”a mobile is marked as inactive, and will not be paged until it becomes active.When set to “n,” mobile status is not changed to inactive.

■ Range: y or n


4.3.1.4 TDMA DCCH Information: SignalStrength Meas. Interval

Specifies number of hyperframes between consecutive mobile signal strengthmeasurements of reselection list candidates. This translation can be overriddenby entering values for the like-named translation on the CEQFACE form. If novalue is entered on the CEQFACE form, the value from the ECP form is used.

■ Range: 1 to 16 hyperframes (1 hyperframe = 1.28 seconds)

■ Default Value: 6 (7.68 seconds)

■ Recommended Value: 1 (1.28 sec.)

4.3.1.5 TDMA DCCH Information: Info. WordTransmission Rate

Specifies the rate at which DCCH Information Word is broadcast on an AnalogControl Channel (ACC). This rate is specified in 800-millisecond ticks (often calledOMTs, for Overhead Message Ticks). This translation is overridden by the like-named translation on the CEQFACE form.

■ Range: 0 to 6 (0 = disable transmission of DCCH Info. Word)


■ Recommended Value: 6 (4.8 seconds)

4.3.1.6 TDMA DCCH Information: MaximumBusy/Reserved

Determines how many times an IS-136 mobile can detect a Busy/Reserved/ Idleindicator in non-Idle state before an access attempt failure is declared.

■ Range:

■ s (single)

401-200-112, Issue 11 June 2001 4-59



■ m (multiple)

■ Default Value: m

4.3.1.7 TDMA DCCH Information: MaximumStop Counter

Sets the maximum number of times that either Reserved or Idle conditions can bedetected for any given access attempt before an access attempt failure isdeclared.

■ Range: 1 to 2



4.3.1.8 TDMA DCCH Information: MaximumRepetitions

Sets the maximum number of times a specific burst within any access attemptmay be sent on the RACH before an access attempt failure is declared.

■ Range: 1 to 4



4.3.1.9 TDMA DCCH Information: MaximumRetries

Sets the maximum number of access attempts that can be made before anaccess failure is declared. Note that one “access” may be comprised of manyaccess attempts. For example, a user pressing the SEND key is making one“access,” which will contain between one and eight access attempts.

■ Range: 1 to 8


■ Recommended Value: 2 or 4

4.3.2 NET (Cellular Network) Form

This form defines the paging technology to be used for paging messagestransmitted over this cellular network trunk.

4-60 401-200-112, Issue 11 June 2001



4.3.2.1 Technology to Page

Indicates which paging technology should be used for all but the last page.

■ Range:

■ Last: Page only last accessed technology based on most recentorigination/termination/registration.

■ Digital: Page on DCCH for all cells with DCCH enabled, and pageon ACC for all non-DCCH cells.

■ Both: Page on both ACC and DCCH (wherever equipped).

■ Default Value: last

4.3.2.2 Final Technology to Page

Indicates which paging technology is to be used for last page. Refer toTechnology to Page translation description above for more details on options.

■ Range: last, digital, or both.

■ Default Value: last

■ Recommended Value: both

4.3.3 CGSA (Cellular Geographic Service Area)Form

Defines a cellular geographical service area.

4.3.3.1 DCCH Virtual Mobile Location Area

Allows the service provider to support smaller geographic location areas forregistration. Virtual Mobile Location Area (VMLA) is associated with DCCH-equipped setup faces inside of this CGSA. This translation can be overridden viathe CELL2 and CEQSU2 forms.

■ Range: 0 to 1023 or Null


■ Recommended Null

4.3.3.2 DCCH Alphanumeric SID (ASID)

Displays service provider information entered in this field on IS-136 mobiles whenDCCH (Alphanumeric System ID) ASID Active translation is set to “y.” Allowablecharacters are taken from International Reference Alphabet (IRA), which includesboth alphanumeric and special characters. Lucent Technologies recommends that

401-200-112, Issue 11 June 2001 4-61



you use only characters that do not have special meaning to RC/V in this field.Characters such as “!”, “{“, etc., can cause erroneous results because of RC/Vsystem interaction.

■ Range: any alphanumeric character, or NULL


4.3.3.3 DCCH ASID Active

Indicates if the ASID entered in DCCH Alphanumeric SID (ASID) translation is tobe displayed on IS-136 mobiles.

■ Range: y or n


4.3.3.4 System Operator Code

Identifies system operator (SOC).

■ Range:

■ 0 to 2047 for U.S.-based SOCs

■ 2048-4095 for international SOCs

■ NULL


4.3.3.5 IS-136 Emergency Routing Number

Sent when an IS-136 mobile emergency button is pressed.

■ Range:

■ 12 numeric digits

■ * and 11 numeric digits

■ NULL


■ Recommended 911

4.3.3.6 Registration Periodicity (min.)

Defines the autonomous registration (AR) interval on the DCCH. For moreinformation regarding AR, refer to Autonomous and Enhanced Registration

4-62 401-200-112, Issue 11 June 2001



Optional Features and Engineering Guide (401-601-009). This translation can beoverridden by the similar translation on the CELL2 form.



■ Recommended Value: 30 minutes (typical)

4.3.4 CELL2 (Series II Cell Site Database) Form

The CELL2 form contains translations that apply cell-wide.


Allows the service provider to support smaller geographic location areas forregistration. Virtual Mobile Location Area (VMLA) is associated with DCCH-equipped setup faces in this cell. If non-null, this translation overrides any similarCGSA translation and can be overridden by a similar translation on the CEQSU2form.

■ Range: 0 to 1023 or Null


■ Recommended: Null

4.3.4.2 IS-136 Allowable Call Mode Override

Allows the service provider to override “Digital-Only” call mode requests from IS-136 mobiles. If set to “y,” the cell assigns an Allowable Call Mode of “Dual-Mode”to dual-mode IS-136 mobiles that request “Digital-Only” service.

■ Range: y or n



4.3.4.3 Should Home Mobiles Register-DCCH

Determines Autonomous Registration flag for home mobiles. If set to “y,” homemobiles are allowed to register on the DCCH.

■ Range: y or n



401-200-112, Issue 11 June 2001 4-63



4.3.4.4 Should Roamer Mobiles Register-DCCH

Determines Autonomous Registration flag for roamer mobiles. If set to “y,” roamermobiles are allowed to register on the DCCH.

■ Range: y or n



4.3.4.5 TDMA DCCH Registration Periodicity(min)

Defines Autonomous Registration interval on DCCH. For more informationregarding Autonomous Registration, see Autonomous and Enhanced RegistrationOptional Features and Engineering Guide (401-601-009). This translationoverrides a similar translation on the CGSA form.



■ Recommended Value: 30 minutes (typical)

4.3.4.6 Power-Up/Power-Down Registration-DCCH

Toggles power-up/power-down DCCH Enhanced Registration. For moreinformation regarding Enhanced Registration, see Autonomous and EnhancedRegistration Optional Features and Engineering Guide (401-601-009).

■ Range: y or n



4.3.4.7 Location Area ID Registration-DCCH

Toggles Location Area DCCH Enhanced Registration. For more informationregarding this, refer to Autonomous and Enhanced Registration Optional Featuresand Engineering Guide (401-601-009).

■ Range: y or n


4-64 401-200-112, Issue 11 June 2001



4.3.4.8 TDMA DCCH Deregistration

Deregisters an IS-136 mobile. Deregistration occurs when an IS-136 mobile hasreselected a different control channel. Before the mobile camps or locks on thereselected new control channel, it deregisters from its current DCCH. For moreinformation regarding this, see Autonomous and Enhanced Registration OptionalFeatures and Engineering Guide (401-601-009).

■ Range: y or n



4.3.4.9 Series II Cell Optional Feature List

The following optional features must be activated for DCCH Implementation:

■ TDMA FULLRATE

■ TDMA DCCH

The following optional features may be activated to provide enhanced DCCHfunctionality:

1. CNIP (Calling Number ID Presentation)

2. MSG WAIT IND (Message Waiting Indicator)

3. ARR (Automatic Radio Reconfiguration Support for DCCH Radios)

4. GLOBAL AUTH (Authentication)

5. ENH REG (Enhanced Registration)

6. DCCH SMS (DCCH Short Message Service)

4.3.4.10 ARR Available for TDMA DCCH Radio

Indicates whether Automatic Radio Reconfiguration (ARR) is enabled for TDMADCCH radios at the cell. Lucent Technologies strongly recommends use of ARRwhen deploying DCCH. For more information on ARR, see Automatic RadioReconfiguration Optional Feature document, 401-601-027.

■ Range: y or n



401-200-112, Issue 11 June 2001 4-65



4.3.4.11 Authentication Available for TDMADCCH

Indicates whether Authentication is active for DCCH radios on this cell. For moreinformation on Authentication, see Authentication Optional Feature document,401-612-041, Issue 2.

■ Range: y or n


4.3.5 CEQCOM2 (Series II Cell EquipageCommon) Form

Defines equipment translations applied to the whole cell site.

4.3.5.1 Functional Test Interval-TDMA DCCHRadio

Specifies the interval (in seconds) between functional tests of DCCH radio.

■ Range: 0 to 86,400 seconds

■ Default Value: 3600 seconds (1 hour)

4.3.6 CEQFACE (Cell Equipage Common Face)Form

Defines translations common to all equipment on the LAF or sector.

4.3.6.1 All Servers Busy Directed Retry-DCCH

Indicates if Directed Retry is used when the All Servers Busy condition occurs foraccesses on the DCCH. The All Servers Busy condition occurs when channelsare not available to serve the allowable call mode of the access seizure.

■ Range: y or n


4.3.6.2 Inadequate Signal Strength Directed Retryfor DCCH.

Indicates whether the Inadequate Signal Strength Directed Retry feature isenabled for the digital control channel (DCCH). The service provider can enableInadequate Signal Strength directed retries so that the calls that fail the DCCHSetup Access Threshold check are given directed retry treatment where

4-66 401-200-112, Issue 11 June 2001



appropriate. If Inadequate Signal Strength directed retries are not enabled, callsthat fail the DCCH Setup Access Threshold are given reorder on origination orrelease on page response.

■ Range: y or n

■ Default = n

4.3.6.3 Directed Retry Threshold-DCCH

Sets the signal level threshold above which directed retries are not attempted forthe All Servers Busy condition. The purpose of this threshold is to prevent mobilesclose to a blocked cell from being redirected to an out-of-range neighbor cell site.This prevents the mobile from interfering with other cells using the samefrequencies as the target directed retry cell. In addition, this threshold minimizesinterference resulting from receiver overload in the blocked cell. Notice that thedefault value of -51 dBm effectively disables this capability.

■ Range: -51 to -113 dBm (2-dB increments)

■ Default Value: -51 dBm

4.3.6.4 SG0 Access Threshold-DCCH

Sets the minimum signal strength (as measured by the mobile) to set up a call onthe primary server group (SG0; also called inner server group or underlay) on aDCCH-equipped sector of a dual-mode cell (i.e., with two server groups). If thesignal strength is less than this threshold, and greater than Mobile AccessThreshold (see below), it will set up on the secondary server group (SG1; alsocalled the outer server group or overlay). This translation has no effect on singleserver group cells.



4.3.6.5 Info. Word Transmission Rate

Specifies the rate at which the DCCH Information Word is broadcast on theAnalog Control Channel (ACC). This rate is specified in 800-millisecond ticks(often called OMTs, for Overhead Message Ticks). If non-null, this translationoverrides the same translation on the ECP form.

■ Range: 0 to 6 (0 = disable transmission of DCCH Info. Word) or Null


■ Recommended: Null (set to 6 on ECP form)

401-200-112, Issue 11 June 2001 4-67



4.3.6.6 Mobile Attenuation Code

Defines the maximum transmit power of an IS-136 mobile when accessing DCCHon this sector. This translation is called MS_ACC_PWR in the IS-136.1specification; it is downloaded as part of the reselection list information wheneverassociated RESEL form entries are updated. If this translation is set to 0 or 1,Class III/IV mobiles will adjust the Mobile Access Threshold (RSS_ACC_MIN inIS-136 terms) by the difference between the value sent and 28 dBm. Thistranslation is analogous to Control Mobile Attenuation Code (CMAC) for the ACC.



■ Recommended Value: 2 or greater to avoid interaction with Mobile AccessThreshold.

4.3.6.7 Mobile Access Threshold

Indicates the minimum control channel signal strength (received at the mobile)required to access cell. This translation is called RSS_ACC_MIN in the IS-136.1specification. It is downloaded as part of the reselection list information wheneverthe associated RESEL form entries are updated. If a cell supports both DCCH andACC, Lucent Technologies recommends that the RSS_ACC_MIN for both DCCHand ACC are set to the same value so that these two control channels have thesame coverage.

0 = 36 dBm Class I maximum power)

1 = 32 dBm Class II maximum power)

2 = 28 dBm Class III/IV maximum power

3 = 24 dBm

4 = 20 dBm

5 = 16 dBm

6 = 12 dBm

7 = 8 dBm

8 = 4 dBm (Class IV only

9 = 0 dBm(Class IV only)

10 = -4 dBm(Class IV only)

4-68 401-200-112, Issue 11 June 2001



Prior to Cell Release 12.0, this threshold is set higher than required for DCCHand SMS communication. This is done to ensure that the DTC signal strengthfrom the cell signal is strong enough to ensure a quality DTC voice channel. Thevalue of the Mobile Access Threshold is determined by taking into account thedifference between the estimated maximum MS output power (i.e., MobileAttenuation Code or MS_ACC_PWR) and the actual MS output power. Theactual MS output power is defined by its power class (P) to obtain a correctreceived signal strength threshold (called RSST) for use in the control channelselection/reselection process. This interaction with MS_ACC_PWR is such that ifMS_ACC_PWR is set to 0 or 1, the coverage area of the sector is reduced forClass III/IV mobiles by the difference between the MS_ACC_PWR setting and 28dBm.

Setting this translation too high can cause a gap in DCCH coverage, forcing theIS-136 mobile to lock onto the ACC. Setting this translation too low can cause thecoverage area of the sector to be extended too far, possibly causing increasedinterference.



■ Recommended Value: -85 to -105 dBm range, based on overlappingcoverage signal strength measurements (use portable-in-carmeasurements or estimates as worst-case minimum values).

4.3.6.8 Setup Access Threshold

This parameter is created to support the separte access threshold for DCCH andDTC feature and specifies the minimum received signal strength at the mobilerequired for the mobile to set up a digital traffic channel. If the signal strengthreported is greater than this threshold, the call is set up on this sector. If the signalstrength is less than this threshold, the call is given normal Dismissal of Calltreatment. Because the value set for this parameter for any one sector dependson the strength of RF coverage in the area and the service provider’s tolerance fordismissing call setups, there is no recomended value for this parameter. It issuggested that the parameter be incrementally increased while observingperformance metrics refered to in Paragraph 1.5.1.2.3.

The separte access threshold for DCCH and DTC feature is effectly disabledwhen this parameter is set to -130 dBm.

■ Range: -51 through -111 dBm, in 2 dB increments, or -130 dBm

■ Default = -130 dBm

401-200-112, Issue 11 June 2001 4-69



4.3.6.9 Mobile Reselection Threshold

Indicates the minimum control channel signal strength (received at the mobile)sufficient for a control channel to be considered for control channel reselection.This translation is called SS_SUFF in the IS-136.1 specification, and isdownloaded as part of the reselection list information whenever associatedRESEL form entries are updated. The SS_SUFF value is used, in someinstances, to control cell reselection using an absolute threshold, such as in thecase of Preferred and/or Non-Preferred Cell Types (Refer to RESEL formdiscussion of CELLTYPE). This translation must be set greater than or equal tothe Mobile Access Threshold for proper DCCH reselection. Refer to TDMA DCCHRF Engineering Guidelines document for further information on SS_SUFF.




4.3.6.10 Access Burst Size

Indicates to mobile what size access burst to use when accessing DCCH viaRandom Access Channel (RACH).

■ Range:

■ a = abbreviated

■ n = normal


■ Recommended Value: a

4.3.6.11 Signal Strength Meas. Interval

Specifies number of hyperframes between consecutive mobile signal strengthmeasurements of reselection list candidates. This translation is calledSCANINTERVAL in the IS-136.1 specification. It is downloaded as part of thereselection list information whenever associated RESEL form entries are updated.This translation overrides the like-named translation on the ECP form. If no valueis entered on the CEQFACE form, the value from the ECP form is used.

■ Range: 1 to 16 hyperframes (1 hyperframe = 1.28 seconds).


■ Recommended Value: 1 (1.28 sec) or NULL to use overriding translations

4-70 401-200-112, Issue 11 June 2001



4.3.6.12 Reselection Delay

Defines the length of time for which a candidate control channel meets requiredsignal strength condition in periodic control channel reselection process. The levelof this translation is used to avoid the ping-pong effect at the cell boundaries. Thistranslation is called DELAY in the IS-136.1 specification. It is downloaded as partof the reselection list information whenever associated RESEL form entries areupdated. The setting of this translation is determined by the size of theoverlapping area between the cells, and the average mobility rate of the mobileswithin the area. If using appropriate values for Offset Bias (in RESEL form), noDELAY is necessary (and in fact will prevent the mobile from reselecting the bestcandidate control channel in the most timely manner). When using Preferred and/or Non-Preferred cell types in reselection list, a DELAY greater than 0 may berequired. Delay is specified in superfame periods which are 1.28 seconds induration.

401-200-112, Issue 11 June 2001 4-71



■ Range: 0 to 14 where:

Value Superframes Value Superframes

0 0 8 150

1 15 9 195

2 30 10 240

3 45 11 285

4 60 12 330

5 75 13 375

6 90 14 420

7 105


■ Recommended Value: 0, when using appropriate values of Offset Bias(RESEL form) and using REGULAR reselection candidate cell types.

4.3.6.13 Mobile Desired Service Bias

This translation is called SERV_SS in the IS-136.1 specification. It is downloadedas part of the reselection list information whenever associated RESEL formentries are updated. This translation is a non-negative offset value that can beused as a bias in the “Service Offering” cell reselection process. This translation isspecified for each current cell. If SERV_SS > 0, the candidate may reselect acandidate control channel that offers a service that the current cell does notprovide. In this case, the candidate’s signal strength (as measured by the mobile)may be up to SERV_SS dB weaker than the current control channel. If SERV_SS= 0, the mobile does not perform Service Offering-based reselection.

At the present time, no known mobile product supports this capability of IS-136.

■ Range: 0 to 30 dB (in 2-dB increments)


4.3.6.14 Initial Selection Control

Determines if mobiles are not allowed to camp on this DCCH sector initially (i.e.,at power-up or when coming from an ACC). This sector may be reselected,however, through the normal reselection process.

■ Range: y or n


4-72 401-200-112, Issue 11 June 2001



■ Recommended Value: At the present time, implementation of this capabilityvaries by mobile unit vendor, so Lucent Technologies recommends that thistranslation be set to “n” for all DCCH-equipped sectors.

4.3.6.15 Last Try Code (Directed Retry)

Sent to a mobile in the Directed Retry message. If Directed Retry is enabled (setto “y”) for the accessed sector, and that directed retry attempt is denied by the cell(for example, with All Servers Busy condition), it will not attempt any subsequentdirected retries.

■ Range: y or n


4.3.6.16 Network Type - Public / Private /Residential

Indicates which network type (public, private or residential) is supported by theDCCH(s) on this sector. At least one of the three network types must be supportedon any given sector. This translation is downloaded as part of the reselection listinformation whenever associated RESEL form entries are updated.

■ Range: y or n l

■ Default Value: y for Public Network Type; n for Private and ResidentialNetwork Types.

4.3.6.17 PSID/RSID Indicator

Indicates whether associated PSID/RSID Value represents a Private System ID ora Residential System ID.

■ Range:

■ p = Private

■ r = Residential or

■ NULL


4.3.6.18 PSID/RSID Value

Specifies either a Private System ID or a Residential System ID (as marked in thePSID/RSID Indicator field). This value is a 1- to 5-digit identifier unique to thePSID or RSID.

■ Range: 1 to 65,635 (Refer to Database Update Guide for suggestions.)

401-200-112, Issue 11 June 2001 4-73




4.3.7 CEQSU2 (Series II Cell Equipage Setup)Form

Defines translations for the cell site setup radios.


Allows the service provider to support smaller geographic location areas forregistration. The Virtual Mobile Location Area (VMLA) is associated with thisDCCH-equipped setup face. If non-null, this translation overrides the similarCGSA and CELL2 translations.

■ Range: 0 to 1023 or NULL


4.3.7.2 TDMA DCCH Channel Number

Determines channel number of the locator DCCH. It is used in the DCCHInformation Word sent in the Overhead Message Train on the ACC.

■ Range: 0, 1 to 1023 (0 disables the DCCH Information Word on the ACC).


4.3.7.3 TDMA DCCH Digital Verification ColorCode

Digital Verification Color Code (DVCC) is used to distinguish the associatedDCCH from co-channel interferers.

■ Range:

■ 1 to 161

■ 163 to 255


4.3.7.4 Control Channel Reselection Parameters:Protocol Version

Identifies the protocol supported by the sector. If this value is changed, all RESELforms that have an entry for this ACC must be updated.

■ Range: 553 (AMPS), 54B (TDMA ACC) or 136 (TDMA DCCH)

4-74 401-200-112, Issue 11 June 2001




4.3.7.5 Control Channel Reselection Parameters:Mobile Attenuation Code

Defines the maximum transmit power of the IS-136 mobile when accessing theACC on this sector. If this value is changed, all RESEL forms that have an entryfor this ACC must be updated. If this translation is set to 0 or 1, Class III/IVmobiles will adjust Mobile Access Threshold (RSS_ACC_MIN in IS-136 terms) bythe difference between the value sent and 28 dBm. This translation is analogousto the Control Mobile Attenuation Code (CMAC) for the ACC.



■ Recommended Value: 2 or greater to avoid interaction with Mobile AccessThreshold.

4.3.7.6 Control Channel Reselection Parameters:Mobile Access Threshold

Indicates the minimum control channel signal strength (received at the mobile)required to access the cell. If this value is changed, all RESEL forms that have anentry for this ACC must be updated.




3 = 24 dBm

4 = 20 dBm

5 = 16 dBm

6 = 12 dBm

7 = 8 dBm




401-200-112, Issue 11 June 2001 4-75






4.3.7.7 Control Channel Reselection Parameters:Mobile Reselection Threshold

Indicates the minimum control channel signal strength (received at the mobile)sufficient for a control channel to be considered for control channel reselection.This translation is called SS_SUFF in the IS-136.1 specification.The SS_SUFFvalue is used, in some instances, to control cell reselection using an absolutethreshold (in the case of Preferred and/or Non-Preferred Cell Types, see RESELform discussion of CELLTYPE). This translation must be set greater than or equalto Mobile Access Threshold for proper DCCH reselection. If this value is changed,all RESEL forms that have an entry for this DCCH must be updated. Refer toTDMA DCCH RF Engineering Guidelines for further information on SS_SUFF.




4.3.8 FCI (Face Code Information) Form

The FCI form contains translations that apply to this particular face or sector.

4.3.8.1 DCCH Shortened Burst on Call Setup

Indicates whether the mobile should use shortened burst initially on the assigneddigital traffic channel when setting up a call from the DCCH. This is generallyuseful on large diameter cells.

■ Range: y or n


■ Recommended Values: y

4.3.9 DCCH (Digital Control Channel) Form

Contains radio equipment information for the Digital Control Channel. Its key fieldsare cell number and radio number. The DCCH form parallels the CTM form for

4-76 401-200-112, Issue 11 June 2001



Digital Traffic Channels. Since a DCCH form identifies one particular time slot onone particular digital radio, if a CTM form has formerly been associated with thattime slot, the CTM form must be deleted before the DCCH form is inserted. Adigital radio that has both DCCH and DTC capability is called a “mixed-mode”DRU.

4.3.9.1 Series II Cell Site Number

Indicates the cell site number for this DCCH form.

■ Range: 1 to 384

■ Key Field (required!)

4.3.9.2 Voice Radio Number

Indicates the radio number for this DCCH form.

Range: 0 to 191

4.3.9.3 Voice Radio Channel Number

Indicates the FCC channel number (a pair of frequencies) over which this radiotransmits and receives.

■ Range:

■ A-Band: 1 to 333, 667 to 716, 991 to 1023;

■ B-Band: 334 to 666, 717 to 799

4.3.9.4 Digital Verification Color Code

Digital Verification Color Code (DVCC) is a supervisory code, transmitted by thecell and transponded by the mobile, that indicates the mobiles presence on theDCCH.

Range: 1 to 161, 163 to 255

4.3.9.5 Status-Timeslot 1

Specifies the status of the DCCH (which is always time slot 1).

■ Range:

■ e (equipped)

■ g (growth)

401-200-112, Issue 11 June 2001 4-77



■ u (unequipped)

■ Default Value: u

4.3.9.6 Physical Antenna-Receive

Specifies the receive antenna face for this DRU.


0 = omni face 4 = delta face1= alpha face 5 = epsilon face2 = beta face 6 = zeta face3 = gamma face


4.3.9.7 Physical Antenna-Transmit

Specifies the transmit antenna face for this DRU.

■ Range: 0 to 6, where for a single-LAC (Linear Amplifier Circuit) per faceconfigured cell:

0 = omni face 4 = delta face1 = alpha face 5 = epsilon face2 = beta face 6 = zeta face3 = gamma face


4.3.9.8 Linear Amplifier Circuit Number

Specifies the transmit antenna face for this DRU.

■ Range:

— Series II and Series IIe: 0 to 6

— Series IIm: 0 to 23

— Series IImm: 0 to 2


4.3.9.9 Frame Number

Specifies the radio channel frame where this DRU is located.

■ Range: 0 to 2


4-78 401-200-112, Issue 11 June 2001



4.3.9.10 Shelf Number

Specifies the shelf number within the frame where this DRU is located.

■ Range: 0 to 5


4.3.9.11 Slot Number

Specifies the slot number within the shelf where this DRU is located. The leftmostslot of the two slots taken up by the DRU is entered.

■ Range: 2 to 22


4.3.10 RESEL (Reselection List for ControlChannels) Form

The RESEL form contains data for up to 24 candidate reselection sectors for eachcurrent DCCH sector. The candidate sector may be either an ACC or a DCCH.Each of the translations below is defined on a per-candidate reselection sectorbasis. If the candidate sector is on the same ECP as the current sector, many ofthe following fields are automatically populated via the values entered in theCEQFACE form for the candidate sector.

4.3.10.1 Cell Site

Specifies the candidate cell number.

Range: 0 to 384

4.3.10.2 PAF

Specifies the candidate physical antenna face (PAF).


0 = omni face 4 = delta face1 = alpha face 5 = epsilon face2 = beta face 6 = zeta face3 = gamma face

4.3.10.3 Tech

Specifies the technology of the candidate control channel.

401-200-112, Issue 11 June 2001 4-79



■ Range:

■ acc (Analog Control Channel)

■ dcch (Digital Control Channel)

4.3.10.4 Chan

Specifies the FCC RF channel of the candidate control channel.

Range: 1 to 799, 991 to 1023

4.3.10.5 DCC/DVCC

Specifies the Digital Color Code for ACC or the Digital Verification Color Code forDCCH of the candidate control channel. If the candidate sector is “local” (on thesame ECP as the current sector), the field is automatically populated and must beleft blank

Range:

■ 0 to 3 for ACC

■ 1 to 161 and 163 to 255 for DCCH

4.3.10.6 Directed Retry

Specifies if this RESEL form candidate entry is to be considered a Directed Retrychannel.

■ Range: y or n


4.3.10.7 Type

Identifies the preference type of the candidate sector. This translation is calledCELLTYPE in the IS-136.1 specification. IS-136 introduces the “Hierarchical CellStructures” capability, in which multiple methods of reselection are possible. If thecandidate sector is CELLTYPE = Regular, a best-server approach is employed(using the Offset Bias or RESEL_OFFSET translation as hysteresis). If thecandidate is CELLTYPE = Preferred, an absolute threshold algorithm is used.

For a Preferred DCCH, if the candidate signal strength is above the MobileReselection Threshold or SS_SUFF, that candidate sector is selected, regardlessof the current channel signal strength. If the candidate is not Preferred, anopposing absolute threshold is used. The Non-Preferred candidate will not be

4-80 401-200-112, Issue 11 June 2001



selected until the current sector signal strength is weaker than its MobileReselection Threshold or SS_SUFF.

■ Range:

■ pre, Preferred

■ reg, Regular

■ non, Non-Preferred

■ Default Value: reg

4.3.10.8 Delay

Defines how soon a candidate control channel can be considered for reselection.This translation is called Delay in the IS-136.1 specification. The setting of thistranslation is determined by the size of the overlapping area between the cellsand the average mobility rate of the mobiles within the area. If using appropriatevalues for Offset Bias (in the RESEL form), Delay is unnecessary; it prevents themobile from reselecting the best candidate control channel in the most timelymanner). When using Preferred and/or Non-Preferred cell types in the reselectionlist, a Delay greater than 0 may be required. Delay is specified in superfameperiods which are 1.28 seconds in duration.

401-200-112, Issue 11 June 2001 4-81




Value Superfames Value Superframes

0 0 8 150

1 15 9 195

2 30 10 240

3 45 11 285

4 60 12 330

5 75 13 375

6 90 14 4207 105


■ Recommended Value: 0, when using appropriate values of Offset Bias(RESEL form) and using REGULAR reselection candidate cell types.

4.3.10.9 Offset Bias

Used to increase/decrease the preference of a candidate RESEL entry beingconsidered for reselection (analogous to control channel reselection handoffbias). It is called RESEL_OFFSET in the IS-136.1 specification. The Offset Biascan be set to either positive or negative values; positive values favor reselection,whereas negative values discourage reselection. For Offset Bias > 0, increasingthe magnitude of Offset Bias for a candidate cell will increase the likelihood of itsselection in the control channel reselection process. For Offset Bias < 0, theresult is just the opposite; increasing the magnitude of Offset Bias for a candidatecell will decrease the likelihood of its selection in the control channel reselectionprocess. If no preference is needed, set Offset Bias = 0.

■ Range: -128 to +126 dB

■ Default Value: -4 dB

4.3.10.10 Hi/Lo Freq

Controls the high/low frequency of candidate signal strength measurement asspecified in IS-136.1 (where it is called HL_FREQ). A value of “high” indicates thatthe mobile must measure the candidate signal strength every SCANINTERVALhyperframes. A value of “low” indicates that the mobile must measure thecandidate’s signal strength at a rate of 2 * SCANINTERVAL hyperframes (or atone-half the “high” rate). Setting this translation to “low” will conserve battery lifeat the expense of reselection delay.

■ Range:

4-82 401-200-112, Issue 11 June 2001



■ low

■ high

■ Default Value: high

4.3.10.11 Extended Sys. ID - DCS/ECP/SYS

Specifies the DCS, ECP and System ID (SYS) of the extended system identifieron which this candidate entry is located.These fields are only required for “non-local” candidate entries, i.e., those not residing on the same ECP as the currentsector.

Range:

■ DCS: 0 to 16

■ ECP: 0 to 15

■ SYS: 0 to 32,767

4.3.10.12 Network Type - Pub/Priv/Res

Specifies the network type of the extended system candidate entry.

These fields are only required for “non-local” candidate entries, i.e., those notresiding on the same ECP as the current sector.

Range: y or n

4.3.10.13 Prot Ver

Specifies the Protocol Version of the candidate sector control channel. Onlyapplicable if the candidate = ACC.

■ Range:

■ 553 (AMPS)

■ 54B (TDMA ACC)

■ 136 (TDMA DCCH)


4.3.10.14 Atten

Defines the maximum transmit power of the IS-136 mobile when accessing theDCCH on this sector. This translation is called MS_ACC_PWR in the IS-136.1specification. This field is only required for “non-local” candidate entries, i.e.,

401-200-112, Issue 11 June 2001 4-83



those not residing on the same ECP as the current sector. Refer to discussion inthe CEQFACE form section for more details regarding Mobile Attenuation Code.



■ Recommended Value: 2 or greater to avoid interaction with Mobile Access

4.3.10.15 RSS Access

Indicates the minimum control channel signal strength (received at the mobile)required to access the cell. This translation is called RSS_ACC_MIN in the IS-136.1 specification. This field is only required for “non-local” candidate entries,i.e., those not residing on the same ECP as the current sector. Refer to discussionin the CEQFACE form section for more details regarding Mobile AccessThreshold.







3 = 24 dBm

4 = 20 dBm

5 = 16 dBm

6 = 12 dBm

7 = 8 dBm




4-84 401-200-112, Issue 11 June 2001



4.3.10.16 RESEL Thrsh

Indicates the minimum control channel signal strength (received at the mobile)sufficient for a control channel to be considered for control channel reselection.This translation is called SS_SUFF in the IS-136.1 specification. This field is onlyrequired for “non-local” candidate entries, i.e., those not residing on the sameECP as the current sector. Refer to discussion in the CEQFACE form section formore details regarding Mobile Reselection Threshold.




4.3.11 Summary of DCCH Performance Database

The following table gives a summary of the forms and RC/V translations forDCCH.

Table 4-4 DCCH Translations Summary


Value

ECP FormPage Only if MS Last Accessed onDCCH

y, n n

DCCH Activity Timeout Interval 10 to 2880 minutes 120

DCCH Activity Timeout Allowed y, n n

TDMA DCCH Information: SignalStrength Meas. Interval

1 to 16 hyperframes(1 hyperframe = 1.28seconds)

6 (7.68) 1 (1.28 sec)

TDMA DCCH Information: InformationWord Transmission Rate

0 v 6 (0 = disabletransmission ofDCCH Info. Word)

3 (2.4 sec-onds)

TDMA DCCH Information: MaximumBusy/Reserved

s (single), m (multi-ple)

m

TDMA DCCH Information: MaximumStop Counter

1 to 2 1 2

TDMA DCCH Information: MaximumRepetitions

1 to 4 2 4

TDMA DCCH Information: MaximumRetries

1 to 8 3

401-200-112, Issue 11 June 2001 4-85



NET FormTechnology to Page last, digital or both last

Final Technology to Page last, digital or both last both

CGSA FormDCCH Virtual Mobile Location Area 0 to 1023 or NULL 0

DCCH Alphanumeric SID (ASID) any alphanumericcharacter, or NULL

NULL See description,Sec. 4.3.3.2

DCCH ASID Active y, n n

System Operator Code See description,Sec.4.3.3.4

IS-136 Emergency Routing Number 12 numeric digits, or* + 11 digits, or NULL

NULL

Registration Periodicity (min.) 2 to 513 minutes NULL 30 minutes(typical)

CELL2 Form

DCCH Virtual Mobile Location Area 0 to 1023 or NULL 0

IS-136 Allowable Call Mode Override y, n y y

Should Home Mobiles Register-DCCH y, n n y

Should Roamer Mobiles Register-DCCH

y, n n y

TDMA DCCH Registration Periodicity(min)

2 to 513 minutes NULL 30 minutes(typical)

Power-Up/Power-Down Registration-DCCH

y, n n y

Location Area ID Registration-DCCH y, n n

TDMA DCCH Deregistration y, n n y

Series II Cell Optional Features List See description,Sec. 4.3.4.9

ARR Available for TDMA DCCH Radio y, n y y

Authentication Available for TDMADCCH

y, n n

CEQCOM2 FormFunctional Test Interval-TDMA DCCHRadio

0 to 86,400 seconds 3600 seconds(1 hour)

CEQFACE FormAll Servers Busy Directed Retry-DCCH

y, n y

Directed Retry Threshold-DCCH -51 to -113 dBm (2-dB increments)

-51 dBm



Value

4-86 401-200-112, Issue 11 June 2001



SG0 Access Threshold-DCCH -51 to -113 dBm (2-dB increments)

-51 dBm

Info. Word Transmission Rate 0 to 6 or NULL 3 (2.4seconds)

Mobile Attenuation Code 0 to 10 0 See description,Sec. 4.3.6.6

Mobile Access Code -51 to -113 dBm (2-dB increments)

-99 dBm See description,Sec. 4.3.6.7

Mobile Reselection Threshold -51 to -113 dBm (2-dB increments)

-99 dBm See description,Sec. 4.3.6.9

Access Burst Size a, n n 9

Signal Strength Meas. Interval 1 to 16 hyperframes(1 hyperframe = 1.28seconds)

6 (7.68 sec-onds)

1 (1.28 sec)

Reselection Delay 0 to 14 1 0; see descrip-tion, Sec.4.3.6.12

Mobile Desired Service Bias 0 to 30 dB (in 2-dBincrements)

0 See description,Sec. 4.3.6.13

Initial Selection Control y, n n n; see descrip-tion, Sec.4.3.6.14

Last Try Code (Directed Retry) y, n n

Network Type - Public/Private/Resi-dential

y, n y, Public; n,Private / Resi-dential

PSID/RSID Indicator p, r, NULL NULL

PSID/RSID Value 1 to 65,365; seeDatabase UpdateGuide for sugges-tions

NULL

CEQSU2 FormDCCH Virtual Mobile Location Area 0 to 1,023 or NULL 0

TDMA DCCH Channel Number 0, 1 to 1,023 0

TDMA DCCH Digital Verification ColorCode

1 to 161, and 163 to255

NULL

Control Channel Reselection Parame-ters: Protocol Version

553 (AMPS), 54B(TDMA ACC) or 136(TDMA DCCH)

553

Control Channel Reselection Parame-ters: Mobile Attenuation Code


Control Channel Reselection Parame-ters: Mobile Access Threshold

-51 to -113 dBm (2-dB increments)

99 dBm See description,Sec.4.3.7.6



Value

401-200-112, Issue 11 June 2001 4-87



Control Channel Reselection Parame-ters: Mobile Reselection Threshold

-51 to -113 dBm (2-dB increments)

99 dBm See description,Sec. 4.3.7.7

FCI FormDCCH Shortened Burst on Call Setup y, n n y

DCCH FormSeries II Cell Site Number 1 to 384

Voice Radio Number 0 to 191

Voice Radio Channel Number A-Band: 1-333, 667-716, 991-1023; B-Band: 334-666, 717-799

Digital Verification Color Code 1 to 161, 163 to 255

Status-Timeslot 1 e (equipped), g(growth), u(unequipped)

u

Physical Antenna-Receive 0 to 6 0

Physical Antenna-Transmit 0 to 6 0

Linear Amplifier Circuit Number Series II/IIe: 0-6,Series IIM:0-23;SEries IImm: 0-2

0

Frame Number 0 to 2 0

Shelf Number 0 to 5 0

Slot Number 2 to 22 0

RESEL FormCell Site 0 to 384

PAF 0 to 6

Tech acc (Analog ControlChannel), dcch (Digi-tal Control Channel)

Chan 1 to 799, 991 to 1023

DCC/DVCC ACC: 0-3; DCCH: 1-161 and 163-255

Directed Retry y, n y

Type pre (Preferred), reg(Regular), non (Non-preferred)

reg

Delay 0 to 14 1 Typically 0; seedescription,Sec. 4.3.10.8

Offset Bias -128 to +126 dB -4 dB

Hi/Lo Freq low, high high



Value

4-88 401-200-112, Issue 11 June 2001



Extended Sys ID - DCS/ECP/SYS DCS: 0-16; ECP: 0-15; SYS: 0-32,767

Network Type - Pub/Priv/REs y, n

Prot Ver 553 (AMPS), 54B(TDMA ACC) or 136(TDMA DCCH)

553

Atten 0 to 10 0 See description,Sec.4.3.10.14

RSS Access -51 to -113 dBm (2-dB increments)

-99 dBm See description,Sec.4.3.10.15



Value

401-200-112, Issue 11 June 2001 4-89



4-90 401-200-112, Issue 11 June 2001



Technician Interface


5.2 Status Display Pages 5-1

5.2.1 Video States for Display Pages 5-2

5.2.2 APX Index Display Page - 2100 5-6

5.2.3 Cell Site Status Summary DisplayPage - 2130 5-7

5.2.4 Cell Equipment Status Page 2131 5-9

5.2.5 Cell Software Status Page 2132 5-13

5.2.6 Series II Cell Site Voice Radio Status Page 2133 5-19

5.2.7 Cell LC/SU/BC Status Display Page2135 5-24

5.2.8 Cell DCCH Radio Status Page 2235 5-27

5.3 TDMA/DCCH Technician Interface (TI)Messages 5-30

5.3.1 TI Input Messages 5-30

5.3.2 TDMA/DCCH TI Output Messages 5-345-34

5-30

5-30

5-27

5-24

5-19

5-13

5-9

5-7

5-6

5-2

5-1

5-1

June 2001 5-1

Contents

5-2 401-200-112, Issue 11 June 2001



Technician Interface 5

5.1 Introduction

This chapter describes the technician interface supporting the AUTOPLEXsystem. The chapter covers:

■ Status Display Pages

■ Technician Interface (TI) Input and Output Messages

System performance is monitored via status display pages (SDP) viewed on themaintenance cathode ray tube (MCRT). Status display pages also identify thecurrent system hardware and software configuration.

TI input messages consist of a set of commands that are used to perform avariety of functions; for example, to obtain operational status of a cell site or aparticular component in the cell, to initiate diagnostics, perform audits, etc.Responses to input messages are provided in output messages.

5.2 Status Display Pages

The operation and status of the TDMA equipment is summarized in equipmentstatus output message reports and on status display pages at the MCRT. Statusdisplay pages used to evaluate operation of TDMA- and DCCH-relatedequipment are summarized in this section. The information presented on thesepages is valuable for analyzing system components on a daily basis. Foradditional information, refer to Operations, Administration and MaintenanceGuide 401-610-160.

June 2001 5-1


5.2.1 Video States for Display Pages

Indicators on each display page represent the state of some system component,or the summary state of a group of components. The video states used for logicalunits and control states are shown in Table 5-1 The logical state of a systemcomponent, as it relates to a particular display, is further defined in the sectiondescribing the display page.

5-2 401-200-112, Issue 11 June 2001



Figure 5-1. Status Display Page Hierarchy

IMS

OVERLOAD SYS INHCU, CU PERPH LINK MSC CELL DCS CDN TRUNK

CCS7SYSTEM INDEX - PAGE 100

SSA - PAGE 101

COMMON PROCESSORPAGE 102

SYSTEM EQUIPAGE SUMMARYPAGE 2121

DCS STATUS SUMMARYPAGE 2140

EQUIP STATUSPAGE 2141

TMS/MC STATUSPAGE 2142

TRKGRP SUMMARYPAGE 2150

TRKGRP STATUSPAGE 2151

CELL TRKGRP STATUSPAGE 2152

APX PAGE INDEXPAGE 2100

APX SYSTEM STATUSPAGE 2120

IMS STATUS SUMMARYPAGE 1105

IMS GROUP STATUSPAGE 1106

CELL STATUS SUMMARYPAGE 2130

SOFTWARE STATUSPAGE 2132

VOICE RADIO GROUPSPAGE 2133

EQUIPMENT STATUSPAGE 2131

DS-1 UNIT STATUSPAGE 2134

LC/SU/BC STATUSPAGE 2135

OTU/LMT STATUSPAGE 2137

LAC STATUSPAGE 2136

CDN STATUS SUMMARYPAGE 2160

CCS7 LINK SET SUMMARYPAGE 2180

CCS7 LINK SUMMARYPAGE 2182

CCS7 LINK SPECIFICSPAGE 2183

CDMA EQUIP STATUSPAGE 2138

CCU STATUSPAGE 2139

DCCH STATUSPAGE 2235

CCS7 POINT CODE SUBSYSTEM STATUS

PAGE 2184

NETWORKED-MSC STATUS SUMMARY

PAGE 2170

INTER-MSC [B]X.25 LINK STATUS

PAGE 2171CCS7 LINK SET

SPECIFICSPAGE 2181

DS-1/AFAC UNIT STATUS

PAGE 2143

401-200-112, Issue 11 June 2001 5-3



Table 5-1 Video States for Status Display Pages

LogicalState

TextDisplayed

ColorTerminal

critical alarm <none>or critical

steady or flashingwhite or red

major alarm <none>or major


minor alarm <none>or minor


system normal <none> steadyblack on green

active act steadyblack on green

standby stby steadywhite on blue

out-of-service oosor <none>

steadyblack on red

unavailable unav steadyblack on cyan

alarm alarm flashingwhite on red

trouble trbl steadywhite on red

equipped equip steadywhite on black

unequipped uneqor <none>

steadymagenta on blackred on yellow (Ring)

growth growor <none>

steadywhite on magentablack on blue

initializing init steadywhite on magenta

5-4 401-200-112, Issue 11 June 2001



initializationpending

Init steadyblack on magenta

overload ovld steadyblack on white

diagnose dgn steadyblack on red

inhibit inh steadyblack on white

unknown <none> white on black

indeterminate indt or <none> black on yellow

idle idle white on black

busy busy black on green

reverse busy rbsy white on red

assigned asgn white on magenta

transient tran white on red

guard gard white on red

periodic reset rset white on red

audit aud white on magenta

warning warn or <none> black on yellow

off-line OFL blue-green on red(Ring)

OTU alarm otu steadyred on yellow

out-of-serviceisolated

OOS ISOL white on red (Ring)

OOS limit exceeded oos_ex steadyblack on red

out-of-servicenormal

OOS NORM white on red (Ring)

Table 5-1 Video States for Status Display Pages —Continued

LogicalState

TextDisplayed

ColorTerminal

401-200-112, Issue 11 June 2001 5-5



5.2.2 APX Index Display Page - 2100

Lists all of the display pages that are accessible for the application. Description ofthe pages related to TDMA and DCCH are given in this chapter.

WARNINGisolated

WARNINGor <none>

black on yellow

arr_active(automatic radioreconfiguration)

<none> steadygreen on black

arr_warning <none> steadyblue on yellow

arr_oos <none> steadywhite on red

soft fault soft black on yellow

blocked <none> steadyblue on yellow

camp_on camp_onor <none>

steadyred on green

DS1 alarm ds1a steadyblack on red

LAC alarm lacor <none>

steadyred on yellow

no_page <none> flashingyellow on red

no_psa (no pilot/sync/access)

<none> flashingwhite on red

normal norm steadywhite on green

Table 5-1 Video States for Status Display Pages —Continued

LogicalState

TextDisplayed

ColorTerminal

5-6 401-200-112, Issue 11 June 2001



Figure 5-2. Example of 2100 - APX Index Page—ECP Release 7.0

5.2.3 Cell Site Status Summary DisplayPage - 2130

Provides overall summary status for each cell site. Commands to obtain the statusof beacon channels and DCCH are now available (2135, 2235).

CMD PAGE TITLE

2131,c - Cell c Equipment Status2132,c - Cell c Software Status2133,c SI Cell c VRG Status2133,c,sg,a SII Cell c VR Status3134,c - Cell c DS-1 Unit Status2135,c - Cell c LC/SU/BC Status2136,c - Cell c LAC Status2137,c - Cell c OTU/LMT Status2138,c - Cell c CDMA Equipment Status2139,c,n- Cell c CCC n CCU Status2235,c - Cell c DCCH Status

CELLMSC

CDNDCS TRUNK

CITYSYS EMEROVERLOAD

APX-1000 GENERIC xttya-cdA

IMSLINK

MTTY00 mm/dd/yy hh:mm:ssSYS NORM

CMD< 2100 - APX INDEX

CRITICAL MAJOR MINORSYS INH CU CU PERPH

CMD PAGE TITLE

2141,d - DCS d Equipment Status2142,d - DCS d TMS/MC Status2143,d - DCS d DS-1 Status2150,d - DCS d TRKGRP Summary2151,d,t- DCS d TRKGRP t Status2152,d,t- DCS d CELL TRKGRP t Status

2171,m - MSC m [B]X.25 Link Status

2181 - SS7 Link Set Specifics2182 - SS7 Link Summary2183 - SS7 Link Specifics2184 - SS7 Point Code Subsystem Status

2120 - APX System Status

2130 - Cell Site Status Summary2121 - System Equipage Summary

2140 - DCS System Summary

2160 - CDN Status Summary

2170 - Direct Networked-MSC Summary

2180 - SS7 Link Set Summary

LEGEND

a - PHYSICAL ANTENNA FACEc - CELL SITE NUMBERd - DCS NUMBERn - CDMA CLUSTER CONTROLLER NUMBERsg - SERVER GROUPt - TRUNK GROUP NUMBERVR - VOICE RADIOVRG - VOICE RADIO GROUPm - MOBILE SWITCHING CENTER

CCS7

401-200-112, Issue 11 June 2001 5-7



Figure 5-3. Example of 2130 - Cell Site Status Summary Page

CMD DESCRIPTIONs SCREEN s OF 32131,c Cell c Equipment Status2132,c Cell c Software Status2133,c Cell c VRG StatusSERIES 2 ONLY2133,c,sg,ant VR Status2134,c Cell c DS-1 Unit Status2135,c Cell c LC/SU/BC Status2136,c Cell c LAC Status2137,c Cell c OTU/LMT Status2138,c Cell CDMA Equip Status2139,c,n Cell c CCC n CCU Status2235,c Cell c DCCH Status

401,c OP:CELL c

CELLMSC

CDNDCS

CCS7TRUNK

LEGENDant - PHYSICAL ANTENNA FACEc - CELL NUMBERn - CDMA CLUSTER CONTROLLER NUMBERs - SCREEN NUMBER (REQUEST OTHER SCREENS BY ENTERING NUMBER AT CMD PROMPT).

CELL SITES 76-150 ARE DISPLAYED ON SCREEN 2, AND 151-222 ON SCREEN)sg - SERVER GROUPVR - VOICE RADIOVRG - VOICE RADIO GROUP

NAMESYS EMEROVERLOAD


IMSLINK


CMD< 2130 - CELL SITE STATUS SUMMARY


1-uneq 16-uneq 31-uneq 46-uneq 61-uneq2-uneq 17-uneq 32-uneq 47-uneq 62-uneq3-uneq 18-uneq 33-uneq 48-uneq 63-uneq4-uneq 19-uneq 34-uneq 49-uneq5-uneq 20-uneq 35-uneq 50-uneq 65-uneq6-uneq 21-uneq 36-uneq 51-uneq 66-uneq7-uneq 22-uneq 37-uneq 52-uneq 67-uneq8-uneq 23-uneq 38-uneq 53-uneq 68-uneq9-uneq 24-uneq 39-uneq 54-uneq 69-uneq10-uneq 25-uneq 40-uneq 55-uneq 70-uneq11-act 26-uneq 41-uneq 56-uneq 71-uneq12-act 27-uneq 42-uneq 57-uneq 72-uneq

28-uneq 43-uneq 58-uneq 73-uneq14-uneq 29-uneq 44-uneq 59-uneq 74-uneq15-uneq 30-uneq 45-uneq 60-uneq 75-uneq

13-trbl

64-init

(screen 1 of 3)

5-8 401-200-112, Issue 11 June 2001



5.2.4 Cell Equipment Status Page 2131

Indicates the configuration of the cell site hardware units and provides a statussummary of each unit or group of units. This page now identifies the status ofTDMA equipment (beacon, TRTU, DCCH) as as either norm (normal) or trbl(trouble).

In addition, this page has maintenance commands which can be used to:

Table 5-2 2130 - Cell Site Status Summary Page Indicators (Series II)

SummaryState(Note) Description

uneq Cell site unequipped in ceqcom2 (Series II) RC/V form.

grow Cell is marked as growth in ceqcom2 (Series II) RC/V form.

init Cell site transient clear, stable clear, or boot initialization phase.Whether or not a cell phase is in progress is indicated by the videostate (of this indicator):

n White on magenta - Cell phase is in progress

n Black on magenta - Cell phase is pending (scheduled, but notyet started).

oos Both data links are out of service, or both reference generators arealarmed, or call processing has been inhibited.

cpinh Call Processing is inhibited.

trbl Trouble. At least one of the major cell hardware units is out of service,being initialized, or has a major alarm.

ovld Cell experiencing processor overload.

inh Inhibited. At least one cell site software controller is in the off-normalstate.

<null> (No state) Equipped, but run-time status is not known.

arr_active Automatic radio reconfiguration (ARR) active for this (active) cell site(no off-normal conditions).

act Active cell site (no off-normal conditions).

Summary states are listed in order of priority.

401-200-112, Issue 11 June 2001 5-9



■ Change the cell hardware configuration

■ Generate a cell status output message report

■ Dump the cell maintenance request administrator queue (MRAQ).

Figure 5-4. Example of 2131 - Series II Cell Site Equipment StatusPagewithout the OTU/LMT feature—ECP Release 7.0

CMD DESCRIPTION490 OP:CELL C491 DUMP:CELL C :MRAQ

CELLMSC

CDNDCS

CCS7TRUNK

NOTE 1: ALL UNITS FOR SERIES II CELL SITES CAN BE DISPLAYED IN THE equipSTATE; THIS MEANS THAT THE UNIT IS EQUIPPED BUT ITS STATUS IS NOT YET KNOWN.

LEGEND

C - CELL SITE NUMBERN - CDMA CLUSTER CONTROLLER NUMBERx - UNIT NUMBERLOCATION - DESTINATION ID FOR A PARTICULAR CELL OR DCS

(TOWN/CITY)(11 CHARS MAX)



IMSLINK


CMD< 2131,C - CELL C EQUIPMENT STATUS


DL 0

DL 1

UNIT RST RMV DGN OPCSCx 30x 20x 50x 40xDLx 31x 21x 51x 41xCATx 32x 22x 52x 42xRGx 43xRCG 440RTU 350 250 550 450TRTU 351 251 551 451

CSC 0CSNLN

CSNLN

CSC 1

LC/SU/BC

RTU

RCG

norm

RA

CAT0 s1 s act2 c act3 cLAC

norm

LOCATION: N. MIAMI

SUMMARY:

TRTU

CRTU

trbl

RG 0 norm

GPS norm

1 trbl

CDMA EQUIP

trbl2138,C

4 s act5 s

trbl

oos

oos

2135,C

2136,C

DCCH2235,C

2134,C

trblDS-1

2139,C,N

PHASE LEVEL to SOURCE cell

cdmasw_ofrdy

5-10 401-200-112, Issue 11 June 2001



Figure 5-5. Example of 2131 - Series II Cell Site Equipment Status Page withthe OTU/LMT Feature—ECP Release 7.0

CMD DESCRIPTION490 OP:CELL C491 DUMP:CELL C :MRAQ

CELLMSC

CDNDCS

CCS7TRUNK

NOTE 1: ALL UNITS FOR SERIES II CELL SITES CAN BE DISPLAYED IN THE equipSTATE; THIS MEANS THAT THE UNIT IS EQUIPPED BUT ITS STATUS IS NOT YET KNOWN.

NOTE 2: THE OTU & LMT INDICATOR IS DISPLAYED ONLY WHEN THIS FEATURE ISACTIVE.

LEGEND

C - CELL SITE NUMBERN - CDMA CLUSTER CONTROLLER NUMBERx - UNIT NUMBERLOCATION - DESTINATION ID FOR A PARTICULAR CELL OR DCS

(TOWN/CITY)(11 CHARS MAX)



IMSLINK


CMD< 2131,C - CELL C EQUIPMENT STATUS


DL 0

DL 1

UNIT RST RMV DGN OPCSCx 30x 20x 50x 40xDLx 31x 21x 51x 41xCATx 32x 22x 52x 42xRGx 43xRCG 440RTU 350 250 550 450TRTU 351 251 551 451

CSC 0CSNLN

CSNLN

CSC 1

OTU &

LC/SU/BC

RTU

RCG

norm

LMT

RA

CAT0 s1 s act2 c act3 cLAC

norm

LOCATION: N. MIAMI

SUMMARY:

TRTU

CRTU

trbl

RG 0 norm

GPS norm

1 trbl

CDMA EQUIP

trbl2138,C

4 s act5 s

trbl

oos

oos

2137,C

2135,C

2136,C DCCH2235,C

2134,C

trblDS-1

2139,C,N

PHASE LEVEL to SOURCE cell

401-200-112, Issue 11 June 2001 5-11



Table 5-3 2131 - Cell Equipment Status Page Indicators (Series II)

Indicator Description

CELL SUMMARYor SUMMARY

Indicates the summary state of the cell site. The state indicated willalso appear on the 2130 - Cell Site Status Summarypage. For ECP Release 7.0 and later, if any equipment or indicatoris alarmed or troubled, the summary state will be trbl.

PHASE LEVEL If present, shows current initialization activity for cell site. Possiblephase activity: audit (audit invoked due to internal error); boot(download to cell site RAM); bootie (unconditional download); sc(stable clear); sc-pb (partial boot following a stable clear); spp(single process purge); tc (transient clear); or <none> (no phase).

PHASE SOURCE If present, indicates source of phase origination.Possible source:cell (cell site recovery software); clsi (cell site integrity processat ECP); dlrst (data link restore); ecp (ECP recovery software);link (data link maintenance); man (manual request); cpa/i(transient clear caused by manual allow/inhibit of call processing); or<none> (no phase).

CSN/CSNE State of cell site node (CSN)/enhanced cell site node (CSNE).

DL 0/DL 1 Shows state of both cell site data links (0 and 1), if so equipped.Possible states: act (active); oos (out of service); dgn (diagnostic);init (initialized); uneq (unequipped).

CSC 0/CSC 1 State of cell site controller (CSC): act; stby (standby); oos;equip; uneq; or ovld (overload).

RG State of the two RGs (reference generators 0 and 1); act; grow;uneq (for RG1 in a SIIe, SIIm, or SIImm cell only); equip; stby;alarm. .

GPS State of Global Positioning System (GPS): norm; uneq; minor;major; critical.

DS-1 State of DS-1 boards and/or digital facilities interface (DFI): norm(normal, no DS-1 boards or DFIs are OOS or alarmed); or trbl (oneor more DS-1 boards or DFIs are OOS or alarmed). The DS-1 is acircuit board that supports the 24/30 DS0 channels on a T1/E1 trunkfacility.

RA State of voice radio (RA): norm (typically, no more than 25% ofthese units are OOS); alarm (alarmed, more than 25% of theseunits are OOS). The thresholds above can be changed/set by theservice provider.

5-12 401-200-112, Issue 11 June 2001



5.2.5 Cell Software Status Page 2132

Provides software status indicators, as listed below, and permits allow/inhibit inputcommands which now include both DCCH functional testing and DCCH radioaudit.

■ Audits

■ Audit/HEH (hardware error handler) output (Series II), or Audit/PEAR(peripheral error analysis and recovery) (Series I)

■ Boot (initialization)

■ Call processing

RTU State of radio test unit (RTU): act, oos, uneq. Status is indicatedby the unit’s video state alone.

TRTU State of TDMA radio test unit (TRTU): act; oos; uneq. Status isindicated by the SIIe unit’s video state alone.

LC/SU orLC/SU/BC

State of locate, setup, and/or beacon radios (LC/SU/BC): norm (nolocate, setup, beacon, or DCCH radio is OOS); trbl (one or morelocate, setup, beacon, or DCCH radios are OOS); arr_active(one or more locate, setup, beacon, or DCCH radios have causedautomatic radio reconfiguration [ARR] to be used).

CAT State of clock and tone (CAT) board (a c displayed next to thenumber indicates a CAT board). CAT boards 0 and 1 cannot be inthe uneq or grow states.

LAC State of linear amplifier circuit (LAC): norm (no LAC is alarmed);alarm (one or more LACs are alarmed).

OTU/LMT State of optical transceiver unit/lightguide microcell transceiver(OTU/LMT).

■ Red background—At least one OTU, or LMT, orOIF fan has a critical alarm.

■ Yellow background—At least one OTU, or LMT, orOIF fan has a major and none have a criticalalarm.

■ Cyan background—At least one OTU, or LMT, orOIF fan has a minor alarm and none have acritical or major alarm.

Table 5-3 2131 - Cell Equipment Status Page Indicators (Series II) —Continued


401-200-112, Issue 11 June 2001 5-13



■ Forward setup channel control

■ Functional tests

■ Interrupts

■ Phase monitoring

■ Routine diagnostics

■ Diversity error imbalance output (Series II).

In addition, this display page has a command to generate a cell status outputmessage report.

Figure 5-6. Example of 2132 - Series II Cell Site Software Status Page(withoutthe OTU/LMT Feature)—ECP Release 8.0

CELLMTSO

CDNDCS TRUNK

LEGEND

c - CELL SITE NUMBERSTATUS - SUMMARY (ALW OR INH) OF FUNCTION LISTED AT RIGHT


APX-1000 GENERIC xttya-cdAIMSLINK


CMD< 2132,c - CELL c SOFTWARE STATUS


CCS7

CMD DESCRIPTION490 OP:CELL c

701,<audit>702/708703704705706,<*>707,<CSC#>709710711

601,<audit>602/608603604605606,<*>607,<CSC#>609610611

ALW INH STATUS FUNCTIONalwalwalwalwalwalwalwalwalwalw

inhinhinhinhinhinhinhinhinhinh

AuditsAudit/HEH OutputBootCall Processing **Forward Setup Channel ControlFunction TestsInterruptsPhase MonitorRoutine DiagnosticsDIVERR Output

** This function is service affecting!

inh

inh

* Functional Tests: lc|su|ant|dcch|oc|tp

OMP+LK

5-14 401-200-112, Issue 11 June 2001



Figure 5-7. Example of 2132 - Series II Cell Site Software Status Page (withthe OTU/LMT Feature)—ECP Release 8.0

CELLMSC

CDNDCS TRUNK

LEGEND





CMD< 2132, c - CELL c SOFTWARE STATUS


CCS7


701,<audit>702/708703704705706,<*>707,<CSC#>709710711

601,<audit>602/608603604605606,<*>607,<CSC#>609610611




* Functional Tests: lc|su|ant|lmt|dcch|oc|tp

inh

inh


OMP+LK

401-200-112, Issue 11 June 2001 5-15



Figure 5-8. Example of 2132 - Series II Cell Site Software Status Page(withoutthe OTU/LMT Feature

CELLMTSO

CDNDCS TRUNK

LEGEND





CMD< 2132,c - CELL c SOFTWARE STATUS


CCS7


701,<audit>702/708703704705706,lc|su|dc|ant707,<CSC#>709710711

601,<audit>602/608603604605606,lc|su|dc|ant607,<CSC#>609610611





inh

inh

5-16 401-200-112, Issue 11 June 2001



)

Figure 5-9. E xample of 2132 - Series II Cell Site Software Status Page(withthe OTU/LMT Feature)—ECP Release 7.0

CELLMSC

CDNDCS TRUNK

LEGEND





CMD< 2132, c - CELL c SOFTWARE STATUS


CCS7


701,<audit>702/708703704705706,lc|su|dc|ant|lmt707,<CSC#>709710711

601,<audit>602/608603604605606,lc|su|dc|ant|lmt607,<CSC#>609610611





inh

inh

401-200-112, Issue 11 June 2001 5-17



Table 5-4 2132 - Cell Software Status Page Functions (Series II)


Audits This function controls/summarizes cell site audits. If one audit is inhibited,the status is INH. Note that individual audits may be controlled using the

menu commands (for example, 601,tepl will inhibits the TEPL audit).

For a list of up to date cell site audits, refer to INH:CELLmessage in theCell Site Input Message Manual.

Audit/HEHOutput

This function allows/inhibits Audit/HEH output. The STATUS indicator willshow whether output messages are allowed from audits at this cell site orwhether output messages from the cell hardware error handler (HEH)function are allowed. If either function is inhibited, the status indicates INH.The input commands 702/602 allow and inhibit audit output respectively;likewise, commands 708/608 allow and inhibit HEH message output.

Boot This function controls whether the cell site is allowed to be automaticallybooted (downloaded from ECP).

CallProcessing

! CAUTION:This function is SERVICE AFFECTING and a change in its statuscauses a transient clear of the cell site. This affects all call processing.

This function controls whether call processing is allowed at the specifiedcell site.

ForwardSetupChannelControl

State of forward setup channel control. This function may be used torestrict originations from the cell site. The off-normal state for this functionis ALW.

The normal state for this function is inhibited (INH).

FunctionalTests

Locate radio, setup radio, antenna controls, LMT, DCCH, overheadchannel (oc) and traffic path (tp). If either of the tests is inhibited, the statuswill be INH. Note that tests may be controlled individually using the menu

commands (specify lc for locate tests, su for setup tests, ant for antenna

tests, lmt for lightguide microcell transceiver tests, dcch for digital controlchannel tests, oc for overhead channel tests or tp for traffic pathtests).

Interrupts Controls cell site hardware interrupts. If any interrupt is inhibited, the status

will indicate INH. All interrupts may be controlled by using the menu

commands (specify 0 or 1 for desired controller for example, 707,1 allow

all interrupts for CSC 1). Use ALW:CELL or INH:CELL message to control

individual interrupts by first entering MSG command mode.

5-18 401-200-112, Issue 11 June 2001



5.2.6 Series II Cell Site Voice Radio Status Page2133

Indicates status of the voice radios at each Series II cell site. TDMA voice channelradios reconfigured by the Automatic Radio Reconfiguration (ARR) feature forDCCH operation are identified on this status display page.

The 2133 - SII Cell VR Status page displays the summary state of eachvoice radio or voice radio group at a specified cell site. This page also displays thenumber of the DCS serving the cell site, and the cell site trunk groups associatedwith each of the logical antenna faces. Each logical antenna face is identified byserver group (SG) and physical antenna face (ANT).

Series II cell site voice radios are displayed based on a particular server groupand physical antenna face (2133 - SII Cell VR Status page).

PhaseMonitor

Controls whether ECP can automatically remove cell site from service onrepeated phasing.

RoutineDiagnostics

Controls whether routine hardware diagnostics, for cell site, are allowed.

DIVERROutput

Controls diversity error imbalance output..

Table 5-4 2132 - Cell Software Status Page Functions (Series II) —Continued


401-200-112, Issue 11 June 2001 5-19



Figure 5-10. Example of 2133 - Series II Cell VR Status Page—ECP Release 8.0

RADIO CHNL BLK TG MEM-1 d 396 100 10-1 d 558 100 212B 432 100 13

474 1004-1 D 516 184 245 390 100 35

369 1007 453 100 178-3 537 184 389 579 100 6010 590 100 4011-2 512 184 1112 542 100 19-2 568 184 22

14 594 100 25

CELLMSC

CDNDCS TRUNK



IMSLINK


CMD<2133,52,0,5


CMD DESCRIPTIONs SCREEN s of 20

200,r RMV r201,r RMV r; UCL202 RMV SG ANT203 RMV SG ANT UCL300,r RST r301,r RST r; UCL303 RST TG MEM ALL302 RST SG ANT402 OP: SG ANG500,r DGN r502 DGN SG ANT

ZONE

RADIO CHNL BLK TG MEM15-1 600 184 3015-2 600 184 5215-3 600 184 14-1 642 184 36-1 642 184 45-1 642 184 54

19-1B 584 184 4319-2B 584 184 3919-3B 584 184 5820-1 621 184 5020-2 621 184 5120-3 621 184 41

663 100 5622 669 100 48

675 100

NOTE: LOCAL POKE COMMANDS 202, 203,AND 502 WILL NOT FUNCTION FOR TDMARADIOS ON AN SG AND ANT FACE. HOWEVER, THE CORRESPONDING TI COMMANDS FORTHESE LOCAL POKES WILL WORK FOR INDIVIDUAL TDMA RADIOS.

LEGEND

ANT — ANTENNAB — BEACON RADIOd, D — DCCH RADIO TYPEDCS — THE SERVING DCS FOR THIS CELLr — RADIO NUMBER (SERIES II CELL VOICE/BEACON RADIO NUMBER)s — SCREEN NUMBER (REQUEST OTHER SCREENS BY ENTERING

NUMBER AT CMD PROMPT)SG — SERVER GROUP (SG)

2

3

0

6-1

13

YES

YES

YES

YES

YES

15

46

23

181818

21

29

DCSCell

1152

SGANT

05PCS TDMA (screen s of 20)

OMP+LK

5-20 401-200-112, Issue 11 June 2001



Figure 5-11. Example of 2133 - Series II Cell VR Status Page—ECP Release 7.0

RADIO CHNL BLK TG MEM-1 d 396 100 10-1 d 558 100 21

2B 432 100 13474 100

4-1 D 516 184 245 390 100 35

369 1007 453 100 178-3 537 184 389 579 100 6010 590 100 4011-2 512 184 1112 542 100 19

-2 568 184 22

14 594 100 25

CELLMSC

CDNDCS TRUNK



IMSLINK


CMD<2133,52,0,5


CMD DESCRIPTIONs SCREEN s of 20

200,r RMV r201,r RMV r; UCL202 RMV SG ANT203 RMV SG ANT UCL300,r RST r301,r RST r; UCL302 RST SG ANT402 OP: SG ANG500,r DGN r502 DGN SG ANT

ZONE

RADIO CHNL BLK TG MEM15-1 600 184 3015-2 600 184 5215-3 600 184 14-1 642 184 36-1 642 184 45-1 642 184 54

19-1B 584 184 4319-2B 584 184 3919-3B 584 184 5820-1 621 184 5020-2 621 184 5120-3 621 184 41

663 100 5622 669 100 48

675 100

NOTE: LOCAL POKE COMMANDS 202, 203,AND 502 WILL NOT FUNCTION FOR TDMARADIOS ON AN SG AND ANT FACE. HOWEVER, THE CORRESPONDING TI COMMANDS FORTHESE LOCAL POKES WILL WORK FOR INDIVIDUAL TDMA RADIOS.

LEGEND

ANT — ANTENNAB — BEACON RADIOd, D — DCCH RADIO TYPEDCS — THE SERVING DCS FOR THIS CELLr — RADIO NUMBER (SERIES II CELL VOICE/BEACON RADIO NUMBER)s — SCREEN NUMBER (REQUEST OTHER SCREENS BY ENTERING

NUMBER AT CMD PROMPT)SG — SERVER GROUP (SG)

2

3

0

6-1

13

YES

YES

YES

YES

YES

15

46

23

181818

21

29

DCSCell

1152

SGANT

05

(screen s of 20)

CCS7

401-200-112, Issue 11 June 2001 5-21



Table 5-5 2133 - SII Cell VR Status Page Video Indicators

StatusColorTerminal

Black & WhiteTerminal

active steadyblack on green

steadywhite on black

out ofservice

steadyblack on red

steadyblack on white

warning black on yellow black on white

equipped steadywhite on black


unequipped steadymagenta on black


growth steadywhite on magenta


unav steadyblack on red

steadyblack on white

arr_active(automatic radioreconfiguration)

steadygreen on black


5-22 401-200-112, Issue 11 June 2001



Table 5-6 2133 - SII Cell VR Status Page Radio Maintenance Indicators


DCS Identity of the serving DCS (1 - 16).

SG Identity of server group (0 or 1).

ANT Identity of physical antenna face (0 - 6).

RADIO Identity of Series II cell voice radio (0 - 191). Radios are identified by radioand time slot numbers (RADIO#-time slot). Time slots do not apply toAMPS trunk groups.

BLK Indicates whether the cell site has blocked access to this trunk/voicechannel:

■ blocked: Indicated by yes.

■ unblocked: No display (normal).

CHNL Voice radio channel number (1 - 1023). (Also see RADIO descriptionabove.)

TG Identify of the trunk group (18-254).

MEM ■ Identity of the trunk member (1 - 192). The summary state for thetrunk member is indicated by its video state:

■ grow: Trunk can be tested, but not used for call processing (whiteon magenta).

■ idle: Normal state when not handling calls (white on black).busy:Normal state when in use for call processing (black on green).

■ tran: Transient audit state - In the process of changing state, onethat cannot be obtained immediately (white on red).

■ gard: Placed on guard timing after an abnormal termination in callprocessing. After guard timing expires, the trunk is restored to theidle state (white on red).

■ aud: Trunk is being audited, or waiting for periodic reset (white onmagenta).

■ reset: Periodic reset - Recovery from suspected hardware trouble(white on red).

■ oos (out of service): Removed from service, or maintenance busy(black on red).

■ uneq: Unequipped (magenta on black)

B Identifies the radio as a Beacon radio.

401-200-112, Issue 11 June 2001 5-23



5.2.7 Cell LC/SU/BC Status Display Page2135

The 2135 - Cell LC/SU/BC Status page displays the summary state ofthe cell locate, setup, and beacon radios. In addition, this page has commands to:

■ Conditionally remove and restore LC radios

■ Conditionally remove and restore SU radios

■ Diagnose LC radios

■ Diagnose SU radios

■ Generate LC/SU radios status message output reports

■ Generate cell site status message output report.

b Identifies the radio as a logical replacement for a failed (automatic radioreconfiguration [ARR]) Beacon radio.

D Indicates that the DRU associated with the voice channel displayed alsocarries a DCCH control channel.

d Indicates that the DRU associated with the displayed voice channel isreplacing a DCCH DRU due to ARR.

l Identifies the radio as a logical replacement for a failed (ARR) Locateradio.

s Identifies the radio as a logical replacement for a failed (ARR) SetupRadio.

Table 5-6 2133 - SII Cell VR Status Page Radio Maintenance Indicators—Continued


5-24 401-200-112, Issue 11 June 2001



Figure 5-12. Example of 2135 - Series II Cell Site LC/SU/BC Status Page—ECP Release 8.0

17

0 1 2 3 4 6 7 8 910 11 14 15 16 1920 21 27 28 2930 31 32 34 3533

185

0 1 2 3 4 5 6 8 910 11 12 13 14 15 16 17 18 1920 24 26 27 28 29

32 33 34 35CMD DESCRIPTION2130 CELL Status Summary2131,c CELL c Equipment Status400 OP:CELL c

CELLMSC

CDNDCS TRUNK

LEGEND

c - CELL SITE NUMBERxy - SETUP RADIO UNIT OR LOCATE RADIO UNIT NUMBERHW - HARDWARE



IMSLINK


CMD<2135,c - Cell c LC/SU/BC STATUS


Locate Radios

25

7

30

UNIT RST RMV DGN OPLCxy 3xy 2xy 5xy 4xySUxy 6xy 7xy 9xy 8xy

0 16

Beacon Radios5

Setup Radios

PCS TDMA

CCS7OMP+LK

401-200-112, Issue 11 June 2001 5-25



Figure 5-13. Example of 2135 - Series II Cell Site LC/SU/BC Status Page—ECP Release 7.0

17

0 1 2 3 4 6 7 8 910 11 14 15 16 1920 21 27 28 2930 31 32 34 3533

185

0 1 2 3 4 5 6 8 910 11 12 13 14 15 16 17 18 1920 24 26 27 28 29

32 33 34 35CMD DESCRIPTION2130 CELL Status Summary2131,c CELL c Equipment Status400 OP:CELL c

CELLMSC

CDNDCS TRUNK

LEGEND

c - CELL SITE NUMBERxy - SETUP RADIO UNIT OR LOCATE RADIO UNIT NUMBERHW - HARDWARE



IMSLINK


CMD<2135,c - Cell c LC/SU/BC STATUS


Locate Radios

25

7

30

UNIT RST RMV DGN OPLCxy 3xy 2xy 5xy 4xySUxy 6xy 7xy 9xy 8xy

0 16

Beacon Radios5

Setup Radios

CCS7

5-26 401-200-112, Issue 11 June 2001



5.2.8 Cell DCCH Radio Status Page 2235

Indicates the status of DCCH radios at each Series II cell site. The status pageincludes:

■ Radio and DCCH Channel Numbers

■ Sector (Face Number)

■ Radio Status

■ RC/V Equipage Status

Table 5-7 2135 - Cell LC/SU/BC Status Page Indicators


RadioUnitSummaryStates

The summary state for each radio type is indicated by its video display(color) state alone. The following is a list of the video summary states foreach radio type:

■ Locate Radios — uneq, grow, indetmt (indeterminate), act,oos, arr_active, or arr_oos

■ Setup Radios — uneq, grow, indetmt, act, stby, oos,arr_active, or arr_oos

■ Beacon Radios — uneq, indetmt, warn (the radio has someproblem but beacon transmitter is still operational), act, oos,arr_active, arr_warning, or arr_oos.

VideoDisplayStates

The unit summary state for the radios is implied by its video display(color) state alone. Possible video display states are as follows:

■ uneq (blank—Only equipped units are displayed on this page)

■ grow (white/magenta)

■ indetmt (white/black)

■ act (black/green)

■ oos (black/red)

■ stby (white/blue)

■ warn (black/yellow)

■ arr_active (green/black)

■ arr_oos (white/red)

■ arr_warning (blue/yellow).

401-200-112, Issue 11 June 2001 5-27



The 2235 - Cell DCCH Status page displays the summary state of thedigital control channel (DCCH) radios. Maintenance commands used to restore(conditionally or unconditionally) DCCH radios, diagnose DCCH radios, and toobtain operational status of DCCH radios are also available on this display page.

Figure 5-14. Example of 2235 - Series II Cell Site DCCH Status Page —ECPRelease 8.0

CMD DESCRIPTION2133,c,r SII VR2135,c LC/SU/BC

300,r RST r301,r RST r; UCL400 OP:CELL c DCCH500,r DGN r

CELLMSC

CDNDCS

CCS7TRUNK

LEGEND

c - CELL SITE NUMBERr - DCCH RADIO NUMBER



IMSLINK


CMD< 2235,c


RADIO PFRADIO PF RADIO PF RADIO PF-1 1 -1 6-1 1 -1 6-1 1-1 2-1 2-1 2-1 3-1 3-1 3-1 4-1 4-1 4-1 5-1 6-1 5

CELL DCCH STATUS

02581015253240708590101102104

150162

PCS TDMA

OMP+LK

5-28 401-200-112, Issue 11 June 2001



Figure 5-15. Example of 2235 - Series II Cell Site DCCH Status Page—ECPRelease 7.0

CMD DESCRIPTION2133,c,r SII VR2135,c LC/SU/BC201,r RMV r;UCL301,r RST r;UCL400 OP: c500,r DGN r

CELLMSC

CDNDCS

CCS7TRUNK

LEGEND

c - CELL SITE NUMBERr - DCCH RADIO NUMBER



IMSLINK


CMD<2235,c


RADIO PFRADIO PF RADIO PF RADIO PF-1 1 -1 6-1 1 -1 6-1 1-1 2-1 2-1 2-1 3-1 3-1 3-1 4-1 4-1 4-1 5-1 6-1 5

CELL DCCH STATUS

02581015253240708590101102104

150162

401-200-112, Issue 11 June 2001 5-29



5.3 TDMA/DCCH TechnicianInterface (TI) Messages

Technician Interface (TI) input and output messages allow the cell site technicianto interact with the system. By entering and receiving messages into and from thecell site, the technician can control, monitor and respond to system configurationand performance. This section describes TI messages as they relate to TDMAand DCCH.

5.3.1 TI Input Messages

This section provides Technician Interface (TI) input messages used to controland monitor cell sites with TDMA and, optionally, DCCH deployed. In most cases,standard AMPS messages have been modified to support TDMA and DCCHoperation; in others, standard AMPS messages are used unmodified. Thepurpose of each message is provided generically, and can be applied to AMPS orTDMA. The TDMA modification column indicates the relevance to TDMA and/orDCCH. This is not a comprehensive list. For details, refer to Input MessageManual 401-610-055 for a complete listing.

Table 5-8 2235 - Cell DCCH Status Page Indicators


RADIO Identity of DCCH radio (range 0 - 191; the maximumnumber of DCCH radios that can be assigned arecurrently 21 [three per sector]). Radios are identified asfollows: RADIO#-timeslot. The status of the radio isindicated by its video state alone:

■ equip (white on black)

■ uneq (magenta on black)

■ grow (white on magenta)

■ act (black on green)

■ oos (black on red)

■ indt (black on yellow): indeterminate

■ arr_oos (white on red)

■ arr_act (green on black).

PF Identity f physical antenna face (0 - 6).

5-30 401-200-112, Issue 11 June 2001



Table 5-9 TDMA Input Messages

InputMessage

Purpose TDMA Modification

ALW:CELL Allows specific software orhardware action at specified cellsite(s).

The FT DCCH function allows digitalcontrol channel functional tests.Message may interrupt or degradeservice.

AUD:CELL Requests audit in one or more cellsites.

ARDCCH - Audits all voice radiosthat support DCCH.

CFR:CELL Requests manual and cellconfiguration and cell test (MCAT)on voice radios. No distinction ininput message format is requiredregarding identification of voiceradios providing DCCH service.

Can be applied to TDMA radios.Requests trunk loopback or unloopon DCCH-associated TDMA radiosare rejected.

DGN:CELL Diagnoses specified cell site unit. Diagnose radio and TRTU

RA x, UC y - Radio, user channel, x= 0 to 191, y = 1 to 3

DNLD:CELL Requests non-volatile memory(NVM) update of specified unit(s) atspecified cell(s).

Applies to all TDMA units.

DUMP:CELL Dumps block of text or data memoryfrom cell.

Memory address specified forfollowing units:

0 - FFFF RCU or DRU

0 - 1FFFFF EDRU

0 - FFFF TRTU

EXC:CELL,FT

Begins execution of functional testat cell site.

DCCH - Execute functional test ondigital control channel.

EXC:CELL-RTDIAG

Requests execution of routinediagnostic sequence on TRTU andDRUs providing DCCH service.

No distinction in input messageformat is required regardingidentification of DRUs providingDCCH service.

INH:CELL Inhibits specific software orhardware action at specified cellsite(s).

FT DCCH - Inhibit functional test ondigital control channel.

ARDCCH - Inhibit audits on allvoice radios that support DCCH

401-200-112, Issue 11 June 2001 5-31



MEAS:CELL Measures on TDMA voice channelradio providing DCCH service beperformed. TDMA radio beingmeasured must be out of service.

No distinction in input messageformat is required regardingidentification of voice channel radiosproviding DCCH service

MOVE:CELL Moves functionality of setup,location, beacon, or DCCH radio tovoice radio. Cell site will select avoice radio on same logical face ofradio to be moved to take overfunctionality.

OP:CELL Requests status of cell siteequipment.

TRTU - Return status of TRTU.

OP:CELL:VERSION

Displays version of firmware and/orsoftware installed on one or moredevices at cell site.

TRTU - Display version of TRTU

RMV:CELL Removes unit from service. Remove radio and TRTU


TRTU - TDMA Radio test unit

RMV:CELL;UCL

Requests can be service-affecting.This is mainly because out-of-service limits may be exceeded;e.g., cell site last setup radio maybe removed from service.

No distinction in input messageformat is required regardingidentification of voice channel radiosproviding DCCH service.

RST:CELL Restores specified cell unit toservice.

Restore radio and TRTU to service


TRTU - TDMA Radio test unit A

RST:CELL unconditional requestcan be service affecting. Becauseno diagnostic is run before restoral,faulty equipment may be put intoservice.

STOP:CFR;CELL

Stops manual and cell configurationand cell test (MCAT) on TDMAvoice channel radios providingDCCH service.


Table 5-9 TDMA Input Messages —Continued

InputMessage


5-32 401-200-112, Issue 11 June 2001



STOP:DGN-CELL

Terminates previously requesteddiagnostic at cell site.

Terminate requested diagnostic onradio and TRTU


TRTU - TDMA Radio test unit

STOP:DNG-DCS-TR

Allows diagnostic routine, currentlyin progress on trunks assigned touser channel voice time slots 2 and3 on TDMA radios providing DCCHservice, to be aborted.


STOP:EXC-CELL

Stops diagnostic routine sequencein progress.


STOP:MEAS-CELL

Terminates previous request formeasurements.


Table 5-9 TDMA Input Messages —Continued

InputMessage


401-200-112, Issue 11 June 2001 5-33



5.3.2 TDMA/DCCH TI Output Messages

This section provides Technician Interface (TI) output messages resulting from TIinput messages and other system events at cell sites with TDMA and, optionally,DCCH deployed. In some cases, standard AMPS messages have been modifiedto support TDMA. The purpose of each message is provided generically, and canbe applied to AMPS or TDMA. The TDMA modification column indicates therelevance to TDMA and/or DCCH. For details, refer to Output Message Manual401-610-057 for a complete listing.

Table 5-10 TDMA Output Messages

Output Message Reason For Output

ALW:CELL Printed upon successful completion of functional testing or routinediagnostics performed on setup, locate radios, and antenna orlightwave microcell transceiver. This message also providessupport for DCCH functionality.

ALW:CELL-AUD Confirms that particular cell audit will be permitted to run as part ofcell routine audit cycle. This output message provides support forDCCH radio audit.

AUD:CELL-ERR-CNT

Indicates that audit has either been completed or was aborted.Error count that contains number of data errors found by audit isprinted. When ARDCCH audit is run, the AUD:CELL-ERR-CNToutput message indicates results of audit.

AUD:CELL-ERR-NO Describes errors found by audit run on cell site. AUD-CELL-ERR-NO output message includes DCCH radio audit as part of its outputformat. Message will output ARDCCH in audit name field for auditsrun on DCCH.

CFR-CELL This output message has two formats.

■ Format 1 prints primary reply from configuration controller.

■ Format 2 prints secondary replies from configuration reporter.

DGN-CELL Reports diagnostic result of specified unit at cell site.

DGN-CELL-PH Reports test results. Can be printed upon failure of cell site-controlled diagnostic phases for voice radios (phases 1-6).

DGN-CELL-RA Reports diagnostic result for voice channel at cell site (CS).

DGN-CELL-TLP When a problem is detected, produces a list of possible circuitpacks that may be the cause of the problem.

5-34 401-200-112, Issue 11 June 2001



DNLD:CELL Reports results of request to update non-volatile memory of cell unitspecified in DNLD:CELL input message. DNLD:CELL outputmessage will also indicate actions and results associated with voiceradios that support DCCH functionality.

DUMP-CELL-EVENT Provides dump of block of memory. This message can have severalorigins:

■ Audit may request dump of critical data upon finding dataerror;

■ Defensive check failure may also call for dump of suspiciousdata;

■ Single process purge can trigger dump of process controlblock (PCB); or

■ Dump of block of memory can be requested by operator.

DUMP-CELL-MRAQ Indicates which device (if any) is being diagnosed at cell, and whichdevices (if any) are waiting to be diagnosed in high and low prioritytest equipment queues.

EXC:CELL-FT Indicates successful completion of functional tests or routinediagnostics on either setup or locate radio, antenna or lightwavemicrocell transceiver. When Series II cell site has voice radios thatsupport DCCH functionality, EXC:CELL-FT output messageindicates either functional test results for all DCCHs within singlecell or the results of specific DCCH radio.

EX-CELL Gives reason for rejection of exercise request, or reports result ofinteractive diagnostic on specified unit at cell site.

EXC-CELL-RTDIAG Reports results of routine diagnostic sequence, or acknowledgesoperator request to initiate routine diagnostic sequence.

EXC-CELL Indicates successful completion of functional tests or routinediagnostics on setup radio, digital control channel radio, locationradio, antenna, or lightwave microcell transceiver.

MEAS:CELL Informs technician of completed measurement request and list ofradio units. This message is printed for locate radios, setup radios,and voice radios (including voice radios that support DCCH).

MOVE:CELL Provides move results for voice radios that support DCCH as resultof request by MOVE:CELL input message.

LOAD-CELL-ADRS Prints address of overwrite, data previously at address and datacurrently loaded at address in response to LOAD:CELL inputmessage. Enables verification that overwrite is at correct location.

Table 5-10 TDMA Output Messages—Continued


401-200-112, Issue 11 June 2001 5-35



OP-ALARM Lists all alarmed executive cellular processor (ECP), callprocessing database node (CDN), cell, and digital cellular switch(DCS) equipment in the system. Valid only if Alarm Summary Print(ASP) feature is active in system.

OP-CELL Prints status of specified cell site unit. Last three lines of report willbe printed only if requested unit is either a failed or a replacingradio, and ARR feature is active for that type of unit in specified cell.

OP-CELL-BEACON Prints status of beacon radio for each physical face. If ARR featureis active for beacon radios at specified cell and beacon radio hasbeen replaced, information about its ARR partner (or failed radio)will also be displayed.

OP-CELL-RA Prints status of voice channel. Format 2 may be printed if RA isTDMA DRU.

OP-CELL-SG Prints status of cell site voice channels. This message is for cell sitetrunk groups only.

OP-CELL-SITE-P-M-S-S

Provides technician with cell plant measurements summarycontaining data relating to component reliability. Records aremaintained for various system equipment failures and systeminitializations.

OP-CELL-VERSION Responds to manual query for firmware and/or software versionresiding in one or more devices in cell site.

OP:CELL-DCCH Prints status of all DCCH user channels (UC) for cell. If ARR featureis active for DCCH radios at the specified cell and a DCCH radiohas been replaced, information about its ARR partner will also bedisplayed.

OP-CELL-PROG-CONT

Reports trouble conditions and alarms that occur in remote cellsites. If there are no trouble conditions or alarms, the word NONEappears in second line.

REPT:CELL Reports when functional tests or routine diagnostics are completed.Completion status for DCCH of cell functional test or routinediagnostic is reported via this output message

REPT-CELL-CP-FAIL

Reports that cell is experiencing call processing problems.



5-36 401-200-112, Issue 11 June 2001



REPT-CELL-HEH Uses hardware error handler (HEH) subsystem.

■ Format 1 - Reports hardware errors and information relating tovarious boards within specific cell site.

■ Format 2 - Reports hardware errors and information relating toTRTU board within specific cell site. In reports with more than35 cell sites, multiple message will arrive, numbered in ordersent from cells.

REPT-CELL-NVM Non-volatile memory (NVM) update was manually requested, orstatus of radio NVM update was queried. Gives completion statusat end of manual NVM update, or gives progress report of radioNVM update in response to status query.

REPT-CELL-RA Reports abnormal state on voice channel.

REPT-CELL-RA-OOS

Reports that voice channel has gone out- of-service (OOS).

REPT-CELL-SG Reports aggregate HOBIT or INLA counts for radio units on specificantenna face, or range of antenna faces, of Series II cell site.

REPT-CELL-SITE-PMSS

Cell plant measurements summary provides data relating tocomponent reliability. Records are maintained for various systemequipment failures and system initializations.

REPT-CP-SETUP Reports occurrence of call setup glare for either origination ortermination.

REPT-CP-TDMA-CALL

Reports air time segment data for TDMA call while TDMA testmode feature is enabled, and optional TDMA call tracking feature isactive.

REPT-CTRC Responds to input message OP:CTRC or as result of automaticorigination or termination call trace feature activated by settingappropriate fields in SUB or VLR RC/V forms. Minor Alarm prioritylevel will be given for this response.

REPT-GENERAL Reports that general system call processing failure has occurred.

REPT-MEAS-CELL Printed as result of measurement request. Only requested ordefault measurements are printed. Measurement results for receiveantennas can have two parts depending on diversity (div 0, div 1).For TDMA voice radios, measurement results are reported by userchannel.



401-200-112, Issue 11 June 2001 5-37



REPT-SERV-MEAS-LEV

Reports summary of level-1 or level-2 service measurements.

■ Level-1 (Message Type 20) gives summary on per-office basis

■ Level-2 (Message Type 21) gives summary on per-cellulargeographic service area (CGSA) basis.

Summary is printed on an hourly basis. Operator may select type ofsummary (level-1 or level-2) and starting time for measurements.

REPT-CELL-AUTOMATIC

Informs technician of status of ARR initiation or termination request.

REPT-CELL-SFW ■ Format 1 prints result of any software (SFW) initialization stim-ulus caused by RADIO assert. Used for messages 351 and352.

■ Format 2 prints result of any software (SFW) initialization stim-ulus caused by CDMA cell assert. Used for message 362.

REPT-CELL-TRAN Reports status of update of cell translator or of AMPSmiscellaneous information (AMI) translator.

RMV-CELL Reports completion codes for removal of cell site unit.

RMV-CELL-RA Reports completion codes for removal of voice channel.

RST-CELL Specifies both diagnostic results and termination mode afterrestoration of cell site unit.

RST-CELL-PH Reports test results.

RST-CELL-VRG-RA Reports diagnostic results and termination mode after voicechannel restoration is attempted.

■ Format 1 for Series I only

■ Format 2 for Series II only

RST:CELL-STF Provides any results that relate to restoral of Series II cell site unitsrequested by RST:CELL input message. Also provides restoralresults that relate to voice radios for DCCH operation where sometests fail.

STOP-DGN-CELL Reports result of terminating diagnostic process at cell site onspecific unit.



5-38 401-200-112, Issue 11 June 2001



MEAS-CELL Informs technician of completed measurement request and listsradio units. This message type (308) is also used forEXC:RTDIAG.

INH-CELL Indicates that inhibit of functional tests or perform diagnostics hasbeen requested.

INH-CELL-AUDNAME

Confirms that particular cell audit will not be permitted to run duringcell routine audit cycle.



401-200-112, Issue 11 June 2001 5-39



5-40 401-200-112, Issue 11 June 2001



Service Measurements andSystem Performance Metrics


6.2 TDMA Service Measurements 6-1

6.3 System Performance Metrics 6-25

6.3.1 Busy Hour Determination 6-25

6.3.2 Cell Metrics 6-25

6.3.3 LAF Metrics 6-25

6.3.4 Performance Metrics 6-25

6.3.5 %Established Calls 6-26


6.3.5.2 Goal 6-26


6.3.5.4 Possible Causes Of Low Percentage OfEstablished Calls 6-26

6.3.5.4.1 Most Likely Cause 6-27

6.3.5.5 Recommended Steps For Investigation: 6-27

6.3.6 %Lost Calls Per LAF 6-28


6.3.6.2 Goal 6-28


6.3.6.4 Possible Causes Of High % Lost Call 6-28

6.3.6.5 Recommended Steps For Investigation 6-296-29

6-28

6-28

6-28

6-28

6-28

6-27

6-27

6-26

6-26

6-26

6-26

6-26

6-25

6-25

6-25

6-25

6-25

6-1

6-1

June 2001 6-1

Contents

6.3.7 %Lost Calls Per Erlang 6-30


6.3.7.2 Goal 6-30


6.3.7.4 Reasons For High Lost Calls Per Assignment 6-30


6.3.8 % Handoffs Complete (Cell & LAF) 6-31

6.3.8.1 Goal 6-31





6.3.9 %Dropped At Handoff 6-32


6.3.9.2 Goal 6-32




6.3.10 %Subscriber Blocking 6-32


6.3.10.2 Goal 6-33


6.3.10.4 What To Do Next (If You Encounter High Blocking) 6-33

6.3.11 % Cell Trunk Group Blocking 6-34





6.3.11.5 What To Do Next (When High Blocking isEncountered) 6-37

6.3.12 %Cell Trunk Group Utilization 6-37


6.3.12.2 Goal 6-386-38

6-37

6-37

6-37

6-36

6-36

6-36

6-34

6-34

6-33

6-33

6-33

6-33

6-32

6-32

6-32

6-32

6-32

6-32

6-32

6-31

6-31

6-31

6-31

6-31

6-31

6-30

6-30

6-30

6-30

6-30

6-30

6-2 401-200-112, Issue 11 June 2001


Contents




6.3.12.6 Reasons For Low Percentage 6-39

6.3.12.7 What To Do Next 6-396-39

6-39

6-39

6-38

6-38

401-200-112, Issue 11 June 2001 6-3


6-4 401-200-112, Issue 11 June 2001


Contents


Service Measurements andSystem Performance Metrics 6

6.1 Introduction

This chapter covers Service Measurements and System Performance Metrics forsystems with TDMA and, optionally, DCCH deployed. Performance managerscan use service measurements to determine how well the system is operating.These measurements provide detailed information regarding type of call trafficand usage of system resources. In addition, this chapter describes an approachfor using service measurements to analyze system performance, andrecommends a set of standard performance metrics.

6.2 TDMA Service Measurements

This section provides TDMA and DCCH-related Service Measurements. Thesemeasurements provide detailed information regarding system performance, andusage of system resources. For detailed information, refer to ServiceMeasurements 401-610-135.

June 2001 6-1

Service Measurements and System Performance

Table 6-1 TDMA Service Measurements

Service Measurement Field Description

Cell Service Measurements Miscellaneous Accumulators (CNT <- CS)

AMPS/TDMA Call Mode atSeizure

7 Count is incremented when a dual-modemobile requests AMPS or TDMA service.The MSC determines channel type.

AMPS Only Call Mode atSeizure

8 Count is incremented when an AMPS ordual-mode TDMA mobile requests AMPSservice. Also pegged for EIA-TIA--553mobiles.

TDMA Only Call Mode Seizures 34 Count is incremented when a dual-modemobile requests TDMA-only service. Analogchannel will not be assigned during call.Allowable Call Mode Override in the CELL2form overrides TDMA-only request; but thiscount is incremented anyway.

TDMA Periodic Best ServerHand-off Requested

38 Count is incremented when a handoff orderis sent to the MSC as a result of the TDMAPeriodic Best Server Locate Trigger.

TDMA Periodic Best ServerLocate Trigger

40 Count is incremented when the DRU hasnot generated a locate trigger within the“TDMA Periodic Best Server Locate”interval. V-DRU sends a locate trigger to theRCC, which executes the MAHO algorithm.

Attenuation Added -- TDMAMobile

44 Count is incremented when the mobilesuccessfully attenuated its transmit poweras commanded by the cell site.

Attenuation Removed -- TDMAMobile

45 Count is incremented when the mobilesuccessfully decreases attenuation,therefore increasing its transmit power ascommanded by the cell site.

Unsuccessful TDMA MobilePower Changes

46 Count is incremented when an unsuccessfulattempt is made to adjust mobile transmitpower.

6-2 401-200-112, Issue 11 June 2001



Cell Service Measurements Miscellaneous Accumulators (CNT <- CS) — Continued

TDMA Periodic Cross FaceLocate Triggers

50 Count is incriminated whenever a TDMAradio generates a time based PeriodicCross Face locate trigger. The TDMA radiocontinuously sets a “Periodic Cross FaceLocate” timer of duration PLOCTMDseconds (if PLOCTMD is non-zero). If noother type of locate trigger was generated inthe previous PLOCTMD seconds, theTDMA radio generates a Periodic CrossFace locate trigger.

TDMA Periodic Cross FaceHandoffs Requested

51 Count is incriminated whenever a handoffrequest is sent to the MSC as a result of theTDMA periodic cross face locate trigger.This measurement will only be peggedwhen the Hybrid MAHO/Digital LocateTDMA handoff algorithm and the PeriodicCross Face Locate features are active.

Cell Service Measurements TDMA Logical Antenna Face Counts (LAF-TDMA)

Time Alignment Failures 1 Count is incremented when a mobile fails torespond to a time alignment adjustmentrequest from the cell. During setup, 6 TAFcounts in a row will cause TDMA VCCF.

Time Alignment Messages -Mobile

2 Count is incremented when a timealignment message is sent to the mobile.

Locate Triggers - High BER atCell

3 Count is incremented when a locate triggeris generated because high a Bit Error Rate(BER) is detected by the cell. High BER atthe mobile or cell is defined in the CELL2form.

Locate Triggers - High FER atCell

4 Count is incremented when a locate triggeris generated because a high Frame ErrorRate (FER) is detected by the cell. HighFER is defined in the CELL2 form.

Table 6-1 TDMA Service Measurements —Continued


401-200-112, Issue 11 June 2001 6-3



Cell Service Measurements TDMA Logical Antenna Face Counts (LAF-TDMA) —Continued

Lost Call - DVCC Timeout 6 Count is incremented when a call is lost dueto Digital Verification Color Code (DVCC)timeout (fade). DVCC timeout intervals aredefined in the following forms:

■ CELL2: DVCC detection timeouttimeslots (number of time slots withoutDVCC detected)

■ CEQFACE: TDMA fade timer

Locate Triggers - High BER atMobile

7 Count is incremented when a locate triggeris generated because a high Bit Error Rate(BER) is reported by the mobile. High BERis defined in the CELL2 form and applies tomobile and cell BER levels.

Mobile/Cell Site ImbalanceThreshold Exceeded

8 Count is incremented when the differencebetween the mobile-reported signal strengthfor the serving channel and the cell-estimated serving signal strength is greaterthan the mobile/cell site imbalancethreshold. This count may indicate a badmobile. Count is reset each time a mobile ishanded off. Threshold is defined in theCELL2 form.

MAHO Locate Triggers 9 Count is incremented when a voice DRUgenerates a locate trigger during MAHOprocessing and sends it to the RCC. AMAHO locate trigger may be generated inresponse to LAF-TDMA fields 3, 4, 7, and10.

Low RSSI at Mobile 10 Count is incremented when a locate triggeris generated because a low Receive SignalStrength Indicator (RSSI) is reported by themobile. Low RSSI Threshold is defined inthe FCI form.

TDMA Handoff Request 11 Count is incremented when a handoffrequest is sent to the ECP for a call beingserved on a TDMA channel.



6-4 401-200-112, Issue 11 June 2001




TDMA Originations Assigned 12 Count is incremented when a call originationis assigned to a TDMA channel.

TDMA Terminations Assigned 14 Count is incremented when a calltermination is assigned to a TDMA channel.

Upward Triggers 15 Count is incremented when the servingsignal strength measured by voice DRU istoo high.

TDMA Handoff Requests Dueto Interference

16 Count is incremented when a handoffrequest is sent to the MSC. A handoffrequest is generated when either the cell-measured serving signal FER or BER, and/or the mobile-measured serving signal BERexceeds the translatable thresholds.

TDMA Voice ChannelConfirmations for MobileOriginations

17 Count is incremented when voice channelconfirmation is received from V-DRU duringTDMA call origination.

TDMA Voice ChannelConfirmations for MobileTerminations

18 Count is incremented when voice channelconfirmation is received from V-DRU duringTDMA call termination.

Call Setups with InterferenceDetected for TDMA

19 Count is incremented when a call is set upon a TDMA voice channel even though highinterference is detected. Unacceptableinterference level is defined in FCI, CELL2,and ECP forms.

Call Handoffs with InterferenceDetected for TDMA

20 Count is incremented when a TDMA call ishanded off to another voice channel eventhough high interference is detected on thetarget channel. Unacceptable interferencelevel is defined in FCI, CELL2, and ECPforms.

Locate Triggers - Low RSSI atCell Site

21 Count is pegged when a locate trigger isgenerated by a TDMA radio because thesignal strength measured by the TDMAradio for the serving channel is below thePRIMARY threshold.



401-200-112, Issue 11 June 2001 6-5




Old Cell - Handoff Orders 22 Count is incremented each time a handofforder from a TDMA traffic channel isreceived by the RCC from the MSC.

Old Cell - Handoffs Complete 23 Indicates the number of times a handoffconfirmation to a TDMA traffic channel isreceived by the RCC from the serving V-DRU.

New Cell - Handoff Orders 24 Count is incremented each time a handofforder to a TDMA traffic channel is receivedby the RCC from the MSC.

New Cell - Handoffs Complete: 25 Count is incremented each time a handoffvoice channel confirmation is received bythe RCC.

Mobile Unit Release. 26 Count is incremented each time a mobileinitiated call releases (caused by depressingthe “END” key on the mobile unit) for TDMAcalls.

Lost Call Audit Failure. 27 Count is incremented each time the mobiledoes not respond to a Mobile Unit Auditmessage.

L-DRU/LEDRU DVCCVerification RequestsProcessed

28 Count is incremented each time a requestfor DVCC verification is processed for thislogical face as part of handoff from a TDMAtraffic channel.

L-DRU/LEDRU DVCCVerification Failures:

29 Count is incremented each time a DVCCverification failure indication was generatedfor this face because either the decodedDVCC did not match the mobile's assignedDVCC or the measured signal strength wasbelow the TDMA locate reply threshold.



6-6 401-200-112, Issue 11 June 2001




L-DRU/LEDRU DVCC SignalStrength ThresholdComparison Failure:

30 Count is incremented each time a DVCCverification failure indication was generatedfor this face because the measured signalstrength was below the TDMA locate replythreshold.

L-DRU/LEDRU DVCCVerification Request Waived:

31 Count is incremented each time a DVCCverification request is passed without testingbecause resources were not available toprocess it in a timely manner.

TDMA Mobile Power Failure 32 Count is incremented each time:

■ the measured signal drops 30 RSSIunits,

■ the measured signal is at or belowinterference on the channel at the timeTx activation +5 RSSI, and

■ the DVCC fade timer expires.

TDMA Forced ReleaseConfirmation Failure duringDVCC Fade

33 This count is incremented when all of thefollowing events take place:

■ The other party (such as a land line)hangs up the call and a forced releaseis sent to the mobile,

■ A release confirmation failure occurs,and

■ The Fade Timer has not expired.



401-200-112, Issue 11 June 2001 6-7




TDMA Mobile PowerDecreases due to BER-controlled mobile DynamicPower Control (DPC)

34 Count is incremented each time a TDMAMobile Power decrease command is issueddue to the BER induced DPC. Count isincremented when the BER is lower thanthe Mobile BER Low Threshold. Since thismay be an indicator of excess mobilepower, in most cases it will beadvantageous to reduce the mobile power.When attentuation is allowed (controlled viathe BER-controlled Mobile DPC parameteron a logical antenna face, the expectedvalue of this count is non-zero and shouldbe less than or equal to the Number ofTDMA Mobile power decreases.

TDMA Mobile Power Increasesdue to BER-controlled mobileDPC:

35 Count is incremented each time a TDMAmobile power increase is issued due to theBER induced DPC. The count isincremented when the BER is higher thanthe Mobile BER High Threshold (MBERHT).When boosting is off (controlled via theBER-controlled Mobile DPC (BMDPCS)parameter) on a logical antenna face, theexpected value of this count is zero. Whenboosting is on a logical antenna face, theexpected value of this count should be lessthan or equal to the Number of TDMAMobile power increases.

Insufficient BER Induced MobilePower Increases for TDMAMobiles

36 Count is incremented each time the BER-controlled Mobile Power was increased butthe increase of power was insufficient. Sincethe BER is measured and the mobile poweris adjusted based on the BER-ControlledDPC algorithm, an insufficient change willaffect the performance of the system.



6-8 401-200-112, Issue 11 June 2001




TDMA mobile powerdecreases:

37 Count is incremented each time the mobileunit is commanded by the cell site todecrease its power. (Cell R10.0 and later.For Pre-R10.0 Cell and earlier, this countwas reported as AGGR-S field 44).

TDMA Mobile power increases: 38 Count is inseminated each time the mobileunit is commanded by the cell site toincrease its power. (Cell R10.0 and later.For Pre-R10.0 Cell and earlier, this countwas reported as AGGR-S field 45).

Unsuccessful TDMA MobilePower Change:

39 Count is incremented each time anunsuccessful attempt is made to changemobile power. (Cell R10.0 and later. ForPre-R10.0 Cell and earlier, this count wasreported as AGGR-S field 46).

Locate Triggers - High RSSI atcell site:

40 Count is incremented each time a locatetrigger is generated by a TDMA radiobecause the signal strength measured bythe TDMA radio for the serving voicechannel is above the high threshold forTDMA. These events are included in TDMAlocate triggers.

MAHO Candidates Only in theHybrid Candidate List

41 Count is incremented each time there is alocate trigger, but there are no handoffcandidates with both positive uplinknormalized signal strength (from digitallocate) and positive downlink normalizedsignal strength (MAHO). This measurementwill only be incremented when the HybridMAHO/Digital Locate TDMA handoffAlgorithm feature is active.



401-200-112, Issue 11 June 2001 6-9




Incidents of Mobile Saturation: 42 Count is incremented each time the MAHOalgorithm generates an empty handoffcandidate list when the mobile saturationresolution feature is active and the mobile-reported signal strength measurement for atleast one MAHO channel is 31.

Unattainable Mobile PowerIncreases

43 Count in incremented as a function the BER- Control DPC Feature State translationparameter entered on the fci form.

When the BER-based boosting option is onand boosting above VMAC is not allowed,this count indicates the number of times theTDMA mobile power should be increasedbased on BER, however, fails to do sobecause the mobile is operating at or belowthe maximum power level permitted by theVMAC value.

When the boosting above the VMAC valueis permitted, this count indicates the numberof times that the mobile power should beboosted based on BER, however, fails to doso because the mobile is alreadytransmitting at its highest power level.

When boosting is not permitted, thisindicates the number of times that themobile power should be boosted based onBER but no signal strength based powercontrol was performed.



6-10 401-200-112, Issue 11 June 2001




Unattainable Mobile PowerDecreases:

44 Count in incremented as a function the BER- Control DPC Feature State translationparameter entered on the fci form under thefollowing conditions:

■ When the attenuation is permitted, thiscount is incremented each time theTDMA mobile power should bedecreased based on BER, howeverany additional attenuation in mobilepower will bring the mobile signalstrength below the low signal strengththreshold.

■ When the attenuation is off, this countis incremented each time the BER isbelow the Mobile BER Low Thresholdand if attenuation were not off onelevel power attenuation will not bringthe signal strength level below the lowthreshold.

Mobile Power Increases(boosts) above DVMAC-TDMA:

45 Count is incremented each time asuccessful mobile power changes that resultin the mobile increasing (boosting) its powerlevel such that the mobile attenuation level(DMAC) is below the Digital Voice MobileAttenuation Code (DVMAC) value. This datacan be used to adjust the DVMAC for thatLAF, if necessary. The Global Mobile PowerControl Flag parameter (in the ecp form)must be set to allow the system to vary thepower of the subscriber unit transmitter. The“TDMA Mobile Power Control State” (fciform) parameter must be set to a 2 (boost)



401-200-112, Issue 11 June 2001 6-11




HOBIT to Dual Mode Request 46 Count is incremented each time a HOBIT-triggered handoff is requested on a servingLAF where both HOBIT to dual mode highand low thresholds are met or exceeded. Asresult, if the resources are available, the callis handed off to another TDMA radio. Thiscount should be slightly less than the TDMAHandoff Request Due to Interference countposted at Field 16. The difference betweenthe two counts

Hobit to AMPS Due to WeakUplink Signal Strength

47 Count is incremented each time a HOBIT-triggered handoff is requested on a servingLAF where the mobile unit signal strengthdid not met the uplink HOBIT to dual modethreshold. As result, the call is handed off toan AMPS radio. The expected count shouldbe a small fraction of TDMA HandoffRequest Due to Interference count postedat Field 16. If the count is too high, theuplink HOBIT to dual mode thresholdparameter may require fine tuning or theTDMA coverage are may need to beadjusted for weak signal areas.

Hobit to AMPS Due to WeakDownlink Signal Strength

48 Count is incremented each time a HOBIT-triggered handoff is requested on a servingLAF where the mobile unit signal strengthdid not met the downlink HOBIT to dualmode threshold. As result, the call is handedoff to an AMPS radio. The expected countshould be a small fraction of TDMA HandoffRequest Due to Interference count postedat Field 16. If the count is too high, thedownlink HOBIT to dual mode thresholdparameter may require fine tuning or theTDMA coverage are may need to beadjusted for weak signal areas.



6-12 401-200-112, Issue 11 June 2001




Serving Face Not Added toCandidate List Due to WeakUplink Signal Strength

49 Count is incremented each time the servingLAF cannot be added to the candidate listbecause the mobile unit signal strength didnot met the uplink HOBIT to AMPS modesignal strength level established by theThreshold (RSSI) - Interference Protectionat Handoff (INTPHO) parameter. This countmay be used to help determine when uplinkBER locate triggers are generate becauseof weak uplink signal rather thaninterference. Count should be a smallfraction of the HOBIT attempts. Fine tunningthe INTPHO parameter may be required. Iffine tunning is not required and the INTPHOparameter is set as intended, the HOBITtrigger is a result of weak signals rather thaninterference and the TDMA coverage aremay need to be adjusted for weak signalareas.

Serving Face Not Added toCandidate List Due to WeakDownlink Signal Strength

50 Count is incremented each time the servingLAF cannot be added to the candidate listbecause the mobile unit signal strength didnot met the downlink HOBIT to AMPS modesignal strength level established by theHOBIT Threshold - Downlink to AMPSparameter. This count may be used to helpdetermine when downlink BER locatetriggers are generate because of weakdownlink signal rather than interference.Count should be a small fraction of theHOBIT attempts. Fine tunning the HOBITThreshold - Downlink to AMPS parametermay be required. If fine tunning is notrequired and this parameter is set asintended, the HOBIT trigger is a result ofweak signals rather than interference andthe TDMA coverage are may need to beadjusted for weak signal areas.



401-200-112, Issue 11 June 2001 6-13




Number of DTX Mode Calls 53 This count, which enables the serviceprovider to calculate the percentage of DTX/CNI mode calls handled through the LAF, isincremented either on a call setup or callhandoff into the LAF. Because the count isincremented at handoff, a single callleaving and re-entering a sector in countedmore once. Although at feature start up, thisservice measurement count will be low, theexpected count will increase as thepenetration of DTX/CNI capable mobileincreases. The percent of DTX/CNI modeusage is calculated by dividing this count bythe total number of call setups and callhandoffs established at the LAF andmultiplying the quotient by 100%.

FLCA Candidate List CreationAttempts at Call Setup (FCA-CS)

54 Count is incremented each time a call pro-cessing is attempted to create an FLCAcandidate list for the best selected logicalantenna face as part of the call setup. It pro-vides a baseline view against which otherFLCA service measurements can be com-pared.

FLCA Channel AcceptanceAttempts at Call Setup (FCAA-CS)

55 Count is incremented each time duringFLCA channel is subjected to acceptancetesting for the best LAF on the cell as part ofcall setup. Refer to 401-200-120.

FLCA Channel Eliminated Dueto Uplink Channel Quality atCall Setup (CEUL-CS)

56 Count is incremented each time a candidateFLCA channel is eliminated due to unac-ceptable uplink channel quality at call setupfor the best LAF on the cell. Note that thiscount may be pegged from zero to MSLLtimes for each call setup attempt on the bestLAF. Refer to 401-200-120.



6-14 401-200-112, Issue 11 June 2001




FLCA Channel Eliminated Dueto Downlink Channel Quality atCall Setup (CEDL-CS)

57 Count is incremented each time a candidateFLCA channel is eliminated due to unac-ceptable downlink channel quality at callsetup for the best LAF on the cell. Note thatthis count may be pegged from zero toMSLL times. Refer to 401-200-120.

FLCA Candidate List CreationAttempts at Handoff (FCA-HO)

58 Count is incremented each time a call pro-cessing is attempted to create an FLCAcandidate list for the best selected logicalantenna face as part of the handoff. Thisservice measurement provides a baselineview against which other FLCA servicemeasurements can be compared. Refer to401-200-120.

FLCA Channel AcceptanceAttempts at Handoff (FCAA-HO)

59 Count is incremented each time a FLCAchannel is subjected to acceptance testingfor the best LAF on the cell as part of Hand-off. This count is used to provide a baselineview of how many FLCA channels for thebest LAF were subjected to acceptancetesting as part of call handoff. Refer to 401-200-120..

FLCA Channel Eliminated Dueto Uplink Channel Quality atHandoff (CEUL-HO)

60 Count is incremented each time a candidateFLCA channel is eliminated due to unac-ceptable uplink channel quality at call hand-off for the best LAF on the cell. Note that thiscount may be pegged from zero to MSLLtimes for each handoff attempt on the bestLAF. Refer to 401-200-120.



401-200-112, Issue 11 June 2001 6-15




FLCA Channel Eliminated Dueto Downlink Channel Quality atHandoff (CEDL-HO)

61 Count is incremented each time a candidateFLCA channel is eliminated due to unac-ceptable downlink channel quality at callhandoff for the best LAF on the cell. Notethat this count may be pegged from zero toMSLL times for each handoff attempt on thebest LAF. Refer to 401-200-120.

Report: ECP-LAF TDMA (TDMA ECP Logical Antenna Face Count)

TDMA Alert ConfirmationFailure

1 Count is incremented each time terminationfails because mobile does not return alertconfirmation (ST [10-kHz signaling tone])within the required time interval. Note thatalert confirmation must pass before thevoice channel confirmation test is done.

TDMA Origination VoiceChannel Confirmation Failure

2 Count is incremented each time originationfails because mobile does not return theproper voice channel confirmation (SAT) tothe cell in the required time interval.

TDMA Termination VoiceChannel Confirmation Failure

3 Count is incremented each time terminationfails because mobile does not return theproper voice channel confirmation (SAT) tothe cell in the required time interval.

TDMA Voice ChannelAssignment from Directed Retryof Another Cell or Face

4 Count is incremented each time a TDMAvoice channel is assigned from a direct retryof another cell or face.

ACELP Vocoder Requested 5 Count is incremented each time an IS-641ACELP voice coder (vocoder) is the firstvalid value in either the first or only vocoderrequest for call originations, terminations, orhandoffs.

ACELP Vocoder Requested butNot Assigned

6 Count is incremented each time an IS-641ACELP vocoder was the first valid value ineither the first or only vocoder request, butthe ACELP vocoder was not assigned.



6-16 401-200-112, Issue 11 June 2001



Report: ECP-LAF TDMA (TDMA ECP Logical Antenna Face Count) — Continued

VSELP Vocoder Requested 7 Count is incremented each time an IS-641VSELP voice coder (vocoder) was the firstvalid value in either the first or only vocoderrequest for call originations, terminations, orhandoffs.

VSELP Vocoder Requested butNot Assigned

8 Count is incremented each time an IS-641VSELP vocoder was the first valid value ineither the first or only vocoder request, butthe VSELP vocoder was not assigned.

FLCA Channel List Receivedfor the 1st LAF Candidate

12 Count is incremented each time a list ofradio channel numbers for the 1st LAF can-didate is sent to the ECP in response to anorigination/termination or handoff .

Non-FLCA Channel WasAssigned on the 1st LAFCandidate

13 Count is incremented each time a list ofradio channel numbers for the 1st LAF can-didate is sent to the ECP in response to anorigination/termination or handoff, and aNon-FLCA Channel is assigned to serve thecall on the 1st LAF candidate.

FLCA Channel Was Assignedon the 1st LAF Candidate

14 Count is incremented each time a list ofradio channel numbers for the 1st LAF can-didate is sent to the ECP in response to anorigination/termination or handoff, and oneof the channels on the list was assigned toserve the call.

Digital Control Channel (DCCH)-Physical Antenna Face (PAF)

Average DCCH RACHOccupancy

1 Count provides occupancy of the RandomAccess Control Channel (RACH).

RACH Occupancy = [(Busy RACH slots +reserved RACH slots) / total RACH slots)] X100



401-200-112, Issue 11 June 2001 6-17



Digital Control Channel (DCCH)-Physical Antenna Face (PAF) — Continued

Peak DCCH RACH Occupancyper 3-Minute Interval

2 Count measures maximum RACHoccupancy on any DCCH on the PAF forany interval during the recording periodusing the same formula as for AverageRACH Occupancy.

DCCH Originations Seizures 3 Count pegs the number of originationmessages received over the RACH from amobile.

DCCH Call Page ResponseSeizures.

4 Count measures the number of messagesreceived over the RACH from a mobile inresponse to paging for a call; does notinclude SMS notification.

AVERAGE DCCH SPACHOccupancy

5 SMS Point-to-Point Paging and AccessResponse Channel (SPACH) Occupancy =[1-(number of null SPACH slots / totalnumber of SPACH slots)] X 100

Peak DCCH SPACHOccupancy per 30 SecondInterval

6 Count measures maximum SPACHoccupancy on any DCCH on the PAF forany interval during the recording periodusing the same formula as for the AverageSPACH Occupancy.

Average DCCH SPACHOccupancy Due to Paging

7 Provides percentage of SPACH occupancydue to paging, calls and SMS.

SPACH Occupancy = [number of PCH slots/(total number of SPACHS slots -number ofnull SPACH slots)] X 100

Peak DCCH SPACHOccupancy per 30 SEcondInterval Due to Paging

8 Count measures maximum SPACHoccupancy due to paging, calls and SMS,on any DCCH on the PAF for any intervalduring the recording period, using the sameformula as for Average SPACH OccupancyDue to Paging.



6-18 401-200-112, Issue 11 June 2001




DCCH Call Page Requests 9 Count measures number of unique pagessent out by the associated DCCH radios forestablishing calls. Count providesinformation on PCH traffic as a componentof SPACH. A value of 1 equals 10 pagerequests.

DCCH Originations Denied 10 Count pegs number of times origination isdenied because of an empty initial serverlist.

Directed Retry on DCCHOriginations

11 Count pegs number of times an originatingmobile is sent the corresponding directedretry message.

Directed Retry on DCCHTerminations

12 Count pegs number of times a terminatingmobile is sent the corresponding directedretry message.

DCCH Intercept Messages 13 Count pegs number of times an interceptmessage is received from the MSC duringcall setup. Message could represent eitheruser error or internal error. Examplesinclude:

■ Invalid feature activation

■ Origination attempt errors, includingincorrect or incomplete dialing

■ Internal errors such as database read-ing problems.



401-200-112, Issue 11 June 2001 6-19




DCCH Reorder Messages 14 Count pegs number of times a reordermessage is sent from the MSC during callsetup. Message could represent either usererror or internal error. Examples include:

■ Invalid access

■ Origination attempt errors, includingincorrect or incomplete dialing

■ Origination restrictions

■ Automatic call reconnect

■ Internal errors such as database read-ing problems.

DCCH Setup Forced ReleaseMessage

15 Count pegs number of times Setup ForcedRelease Message is received from theMSC.

Seizures Denied - All ServersBusy

16 Count pegs number of times initial voice ortraffic channel selection was unsuccessfulbecause no voice or traffic radio wasavailable.

Total DCCH AutonomousRegistration

17 This count is pegged once for eachRegistration Accept message on thedownlink to the mobile.

Reorders on DCCHOriginations All Servers Busy -above Threshold

18 Number of times a reorder is issued onorigination because: cell site does not haveavailable resources, and signal strength ofmobile is above associated threshold fordirected retry.

Releases on DCCHTerminations All Servers Busy -above Threshold

19 The number of times a release is issued ontermination because a cell site does nothave available resources, and signalstrength of the mobile is above associatedthreshold for directed retry.



6-20 401-200-112, Issue 11 June 2001




Directed Retry on DCCHOriginations - All Servers Busy -below Threshold

20 Number of times a mobile is sent a directedretry message on originations because cellsite does not have available resources, andsignal strength of the mobile is below theassociated threshold for directed retry.

Directed Retry on DCCHTerminations - All Servers Busy- below Threshold

21 Number of times a mobile is sent a directedretry message on terminations because:

■ cell site does not have availableresources

■ signal strength of the mobile is belowthe associated threshold for directedretry.

Directed Retry on DCCHOrigination

22 The number of times a directed retrymessage is sent on origination over DCCH,because the adjusted mobile signal strengthis below the DCCH setup access thresholdfor the serving DCCH.

Directed Retry on DCCHTermination

23 The number of times a directed retrymessage is sent on termination overDCCH, because the adjusted mobile signalstrength is below the DCCH setup accessthreshold for the serving DCCH

TDMA - GPAF

Strongest Sector TDMASeizures Denied - All ServersBusy, Servers Not Available atOther Sector

1 Value is incremented for call attempt when:a) signal strength of setup radio is above theACCESS threshold of at least one sector; b)this is strongest sector for setting up call; c)desired call mode is TDMA; d) all TDMAservers for this sector are blocked; or e)servers are also blocked on all otherapplicable sectors in the cell.



401-200-112, Issue 11 June 2001 6-21



TDMA - GPAF — Continued

Strongest Sector TDMASeizures Denied - All ServersBusy, Servers Not Available atOther Sector

2 Value is incremented for call attempt when:a) signal strength of setup radio is above atleast one sector ACCESS threshold; b) thisis strongest sector for setting up call; c)desired call mode is TDMA; d) all TDMAservers for this sector are blocked; or e)servers are also blocked on all other sectorsin the cell.

TDMA Seizures Denied -Inadequate Signal Strength

3 Value is incremented for call attempt when:a) this is strongest sector for setting up call;b) desired call mode is TDMA; or c) signalstrength measured by the setup radio isbelow each sector ACCESS threshold for allsectors in the cell.

TDMA Seizures per MobilePower Class Group 1 (MPC 1and 2)

4 Number of times an attempt to set up a callfinds at least one TDMA traffic channelavailable with sufficient signal strength.

TDMA Seizures per MobilePower Class Group 2 (MPC 3and 4)

5 Number of times an attempt to set up a callfinds at least one TDMA traffic channelavailable with sufficient signal strength.



6-22 401-200-112, Issue 11 June 2001



TDMA Physical Antenna Face Counts (TDMA-PAF)

FLCA Long Term List Monitor-ing.

1 Count is incremented each time the longmeasurement cycle is completed. Duringthis cycle an interference measurement istaken for all long list channels for each PAF.

This count can be used to determine if theLocate Radio(s) is adequate to handleFLCA measurements and conventionallocate traffic.The expected value for this count is 60divided by the Long List Interference Mea-surement Interval (LLIMI) entered on thecell2 form or ecp form RC/V form. If thecount is less than 95% of the expectedvalue, the number of locate radios may haveto increase in order to satisfy the FLCA pro-cessing load. Other possible correctiveactions are to reduce the length of the long(provisioned) list for some or all of the sec-tors on the cell or to increase the value ofLong List Inerference Measurement Interval(LLIMI).



401-200-112, Issue 11 June 2001 6-23



TDMA Physical Antenna Face Counts (TDMA-PAF)

FLCA Short Term List Monitor-ing:

2 Count is incremented each time the longmeasurement cycle is completed. Duringthis cycle an interference measurement istaken for all long list channels for each PAF

This count provides an indication on the pro-cessing load on the Locate Radio(s). Theexpected value: 3600/TSTLIMI (TargetShort Term List Measurement Interval). Ifthe count is less than 95% of the expectedvalue, the number of locate radios may haveto be increased in order to satisfy the FLCAprocessing load. Other possible correctiveactions are to decrease the length of theshort list (by decreasing the value of theMSLL parameter for one or more sectors) orto increase the value of the Short List Inter-ference Measurement Interval (SLIMI) onthe cell2 or ecp RC/V.

FLCA Short List ChannelReplacement:

3 Count is incremented each time a channelthat is replaced in the Short List at short listupdate. The short list channel activity pro-vides an indication of how much churn thereis in the Short List.Three translation parameters are relevant tothe expected value of this count:

1. TLTLIMI - Target Long Term ListMeasurement Interval

2. ISLCU - Short List Channel Update

3. ) MSLL - the Maximum Short ListLength.

These parameters are described in 401-200-120.



6-24 401-200-112, Issue 11 June 2001



6.3 System Performance Metrics

This section describes an approach for using Service Measurements to evaluatesystem performance, and recommends a set of standard performance metrics. Italso includes a brief discussion of the issues involved in determining a criticalbusy hour for system evaluation.

6.3.1 Busy Hour Determination

Before using performance metrics, a busy hour must be determined. This hourprovides a baseline for evaluating service measurements. The busy hour shouldbe determined via an individual floating busy hour method; with one determinationmade for cell metrics, and another for the Logical Antenna Face (LAF) metrics.Supplemental data is provided via a 24-hour total computation of each, allowingfor comparison of system metrics for the peak busy hour vs. all hours.

6.3.2 Cell Metrics

Usage measurements are not recorded on a per cell basis; rather a figure calledArrivals is calculated. Arrivals comprises the total of Originations Assigned,Terminations Assigned, and New Cell Handoff Completes for all calls arriving intoa particular cell in a given hour.

6.3.3 LAF Metrics

Usage, the sum of Limited Spectrum Usage and Expanded Spectrum Usage, isrecorded on a per-LAF basis. Usage includes all technology types: TDMA andAMPS. Usage is calculated independently of Arrivals; and is the preferredmeasurement.

6.3.4 Performance Metrics

This section describes performance metrics that provide a standardized approachfor evaluating performance, and analyzing probable causes of poor performancein an AUTOPLEX system. Use of these metrics indicates whether the system isexperiencing any significant problems, and if so, what areas should beinvestigated further. Descriptions for each performance metric include:

■ Calculation, if applicable

■ Suggested value

■ Goal

■ Typical numbers

401-200-112, Issue 11 June 2001 6-25



■ Possible/most likely cause(s) of bad numbers

6.3.5 %Established Calls

Percentage of all seizures in the system (both Origination and Page Response)that could result in an established call. “An established call” means that the mobilecame up on a voice channel, even though the call might have failed becausePSTN trunks for the called destination were unavailable. In this case, an AMArecord is generated for an "established call."

6.3.5.1 Calculation

where:

■ TDMA Established Calls = TDMA Origination and Termination VoiceChannel Confirmations per LAF summed over all equipped LAFs on a PAF.

■ Og Sz = TDMA Origination Seizures (GPAF count per PAF)

■ Pg Rp Sz = TDMA Page Response Seizures (GPAF count per PAF)

■ SDIS = TDMA - GPAF Seizures Denied Inadequate Signal

■ SDSB_All= TDMA - GPAF Seizures Denied All Servers Busy (All Faces)

6.3.5.2 Goal

100% Established Calls

6.3.5.3 Typical Numbers

90% to 95%

6.3.5.4 Possible Causes Of Low Percentage OfEstablished Calls

AMPS and TDMA use the same setup channel, so the same problems occur forboth technology types.

1. Excessive Seizures Denied - Inadequate Signal. Access Thresh-old too high, Co-Setup/Co-DCC interference, Cell Receive PathOverload (compression), excessive Setup Channel coverage rela-

% TDMA Establ CallsTDMA Established Calls

OgSz( PgRpSz SDIS SDSB All )–+ + +--------------------------------------------------------------------------------------------------------- 100×=

6-26 401-200-112, Issue 11 June 2001



tive to voice channel coverage, hardware problems within the cellreceive signal distribution network (including antennas), insufficientRF coverage (fringe cells).

2. Excessive Voice Channel Confirmation Failures. Setup VoiceChannel Confirmation Threshold too high, Co-Setup Channel/Co-DCC interference, Cell Receive Path Overload (compression),excessive Setup Channel Coverage relative to voice channel cover-age, hardware problems within the cell receive signal distributionnetwork (including antennas), insufficient RF coverage (fringe cells);In a single ECP system, Mobile Origination Glare.

3. Excessive Seizures Denied - Servers Busy. Need more voiceradios or another cell site in this area.

4. Origination/Termination Blocked - No Voice Channel. MSC indi-cates no radios available. (Need more voice radios or another cellsite.)

5. Roamer Service Denied. Check routing.

6. Fraudulent Mobile Call Attempts.

7. Dialing/Routing Errors. For example, dialing 7 digits when 10 or11 digits are required.

8. Cell/System Overload. Including processor occupancy problems,especially at Series I cells.

6.3.5.4.1 Most Likely Cause

In a major metropolitan system, Co-Setup/Co-DCC interference; in a single ECPsystem, either Co-Setup/Co-DCC interference or coverage problems.

6.3.5.5 Recommended Steps For Investigation:

The call failure may originate at either the cell or the ECP. The primary reasons forcell failure are Seizure Denied - Inadequate Signal and Seizures Denied - ServersBusy. The "CP TDMA" portion of the service measurement data contains anumber of reasons for invalid call setup attempts from the ECP perspective; thismay be useful in identifying roamer problems and/or dialing plan problems. Toinvestigate call processing failures, take the following steps:

■ Analyze Call Processing failure messages to determine which cell and/orcell faces are experiencing the most Voice Channel Confirmation Failuresand/or Mobile Unit Origination Glare Messages.

■ Identify the Co-Setup/ Co-DCC faces of this cell/face.

■ Change the setup and/or DCC of the problem face, and continue to monitorthe CPFAIL messages and the % Established Call Rate.

401-200-112, Issue 11 June 2001 6-27



■ Monitor newly established Co-Setup/Co-DCC faces. A DCC of 3 is a validDCC; it is no more prone to bit errors than are other DCC values.

■ Temporarily disable Directed Retry while investigating this problem. Takethe problem cell/face off the directed retry list of neighboring cells.

■ Low TDMA Voice Channel Confirmation levels may be the result ofproblems with time alignment, MAHO measurements, correct DVCC, andsignal above INTP. Analyze service measurements related to these factors.

Mode 1 and 4 Power Level Measurements (PLMs) may also be used to evaluateeffects of the changes. Excessive seizure attempts at very weak signals in thecore of a system usually indicate either Co-Setup/Co-DCC interference orexcessive setup channel coverage.

If Excessive Seizures Denied - Servers Busy messages are seen, additionalradios and/or cells may be needed in the area. If sufficient RF coverage exists, trysetting up a Directed Retry list to other faces that may serve a problem area.Blocked cell faces may contribute to dragged handoffs and dropped calls once thecall is established.

6.3.6 %Lost Calls Per LAF

This number represents the percentage of Established Calls that were "lost" as aresult of a DVCC Fade or a Mobile Unit Audit Failure.

6.3.6.1 Calculation

6.3.6.2 Goal

0% (as low as possible)

6.3.6.3 Typical Number

0 to 6%

6.3.6.4 Possible Causes Of High % Lost Call

The primary causes of lost calls are poor coverage, interference and incorrectsetting of the DVCC Fade Timer. Coverage problems can be caused by cell

% TDMA Lost CallsLost_Call_DVCC_TO TDMA_Lost_Call_Audit_Fail+

TDMA(VCC_Orig VCC_Term)+-------------------------------------------------------------------------------------------------------------------------------------- 100×=

6-28 401-200-112, Issue 11 June 2001



spacing, RF shadowing (from terrain features such as mountains/hills, densefoliage, tall buildings, and tunnels). Fringe cells, especially those that don’t handoff to abutting systems, will generally have higher lost call rates caused bymobiles driving out of the service area.

Interference (co-channel or adjacent channel) or mobile overload (intermods) canimpair the ability of the voice radio to decode the DVCC, or detect increased BER(Bit Error Rate) and can result in lost calls.

Finally, incorrect setting of the DVCC Fade Timer can result in more lost calls. Thesetting of the Fade Timer must be tailored to the cell environment. The goal is topeg all "real" lost calls without forcing lost calls because of expected fades.

6.3.6.5 Recommended Steps For Investigation

Coverage problems can be identified by running PLM Modes 1 and 4, whichprofile the serving signal strength and setup signal strength respectively. If eitherhas more than 10% of the counts below -95dBm, in reference to the antenna,there could be a coverage problem. Field data gathered on both voice and setupchannels can then be used to identify the exact location/area. Field data will alsoidentify overload problems.

Interference problems can also be identified by PLMs, Mode 2 for Co-channel andMode 3 for Adjacent Channels. Usually, however, other performance indicatorssuch as handoff failures will alert the system operator to interference problemsbefore lost calls occur.

The investigation of Lost Calls should not be limited to the above. The worst LostCall rate observed by Lucent Technologies was caused by an empty neighbor list.Other neighbor list problems such as incorrect ESIDs or wrong/missing faceshave also been identified.These kinds of problems are best resolved by carefuldata base checks and the use of tools such as VCSA, HO Matrix or UXcptrace.

Resolving lost call problems, particularly those caused by coverage deficits, canbe expensive, because the solution is often to add cell sites. Possible interimsolutions may include: careful use of high gain antennas, raising antennas, down-tilting antennas, and installing a Microcell, Series IIm or Series IImm.

A solution for TDMA Lost Calls indicated by a high BER (caused by poorcoverage) may be to use the TDMA Handoff Based on Interference (HOBIT)feature. If there is more than one DRU equipped on the serving face, HOBIT willhand off to another DRU (not the same RF carrier frequency) on the same face, ifthere are no other viable candidate faces for the handoff. If only one DRU isequipped on the serving face, a handoff to an AMPS channel will be performed, ifno other candidate faces can be found.

401-200-112, Issue 11 June 2001 6-29



6.3.7 %Lost Calls Per Erlang

This number represents the percentage of voice channel assignments that were"lost" as a result of either a SAT/DVCC Fade or Mobile Unit Audit Failure.

6.3.7.1 Calculation

6.3.7.2 Goal

0% (as low as possible)

6.3.7.3 Typical Number

1 to 6%

6.3.7.4 Reasons For High Lost Calls PerAssignment

Same as for the service measurement metric, "%Lost Call Per LAF," with theaddition of failed and/or dragging handoffs. Typically, improper neighbor list(AMPS) and/or MAHO list (TDMA) cause calls to drop during handoffs.Insufficient channel capacity at neighbor sectors also contributes to lost calls atthis sector.


In addition to the "% Lost Call Per LAF" above, use the AUTOPLEX HandoffMatrix engineering tool to verify ACTUAL system handoffs. By pairing New CellTimeouts (candidate sector) and Lost Call (serving sector) call processing failuremessages that occur about the same time, poor neighbor list entries may beidentified. Remove these marginal/non-performing neighbor list entries from thesystem databases and/or use PLM Mode 2 to determine an appropriate setting forthe INTPHO parameter.

% Lost Calls/ErlangLost_Call_SAT Lost_Call_Audit Lost_Call_DVCC TDMA_Lost_Call_Audit+ + +

LS_Usage ES_Usage TDMA_Usage+ +---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ×=

% TDMA Lost Calls/ErlangLost_Call_DVCC TDMA_Lost_Call_Audit+

TDMA_Usage-------------------------------------------------------------------------------------------------------------- 100×=

% AMPS Lost Calls/ErlangLost_Call_SAT Lost_Call_Audit+

LS_Usage ES_Usage+------------------------------------------------------------------------------------ 100×=

6-30 401-200-112, Issue 11 June 2001



6.3.8 % Handoffs Complete (Cell & LAF)

The % Handoff Completes calculation is made easier with the introduction of CellRelease 6.05, because of the introduction of the following new counts:

■ Old Cell Handoff Complete and New Cell Handoff Complete

■ Old Cell Handoff Order and New Cell Handoff Order

Therefore, the calculations are:

6.3.8.1 Goal

100% completed handoffs


90 to 95% handoffs complete

6.3.8.3 Possible Causes

Low values of % TDMA Old Cell Handoff Complete are generally due to poorcoverage at the serving or “old” cell in the handoff. Front-end overload of themobile can also be a contributing factor. Low values of % TDMA New Cell HandoffComplete can be attributed to the same factors that affect the % TDMA Old CellHandoff Complete. Additional factors are co-channel interference (forward orreverse channel), or adjacent channel interference (mostly seen on the forwardchannel).

6.3.8.4 Most Likely Cause

Interference is the most likely cause.


Any cell consistently in the 80% level should be investigated. Coverage problemscan be identified by running PLM Modes 1 and 4 which profile the serving signalstrength and setup signal strength respectively. If either has more than 10% ofthe counts below -95dBm, there could be a coverage problem. Field data

% TDMA New Cell Handoffs CompleteNew_Cell_Handoff_Complete

New_Cell_Handoff_Order------------------------------------------------------------------------- 100×=

% TDMA Old Cell Handoffs CompleteOld_Cell_Handoff_Complete

Old_Cell_Handoff_Order----------------------------------------------------------------------- 100×=

401-200-112, Issue 11 June 2001 6-31



gathered on both voice and setup channels can then be used to identify the exactlocation/area.

Interference problems can also be identified by PLMs, Mode 2 for Co-channel andMode 3 for Adjacent Channels.

6.3.9 %Dropped At Handoff

The percent of calls dropped during a handoff.

6.3.9.1 Calculation

6.3.9.2 Goal

0%


0.4 to 0.7%

6.3.9.4 Possible Causes

Interference at either the new or old cell (usually the old cell), incorrect setting ofINTPHT (a per-MAHO Neighbor List translation), or MAHO falsing. MAHO falsingis a condition in which the MAHO measurements reported by the mobile arecorrupted by co-channel or adjacent interference. This causes the system to handoff the mobile to an incorrect candidate face, which often results in a lost call. Thismetric is viewed from the perspective of the “old” cell; the “old” cell is the last cellto have successfully carried the mobile before the lost call was pegged.

6.3.9.5 Most Likely Cause

Interference

6.3.10 %Subscriber Blocking

The percent of Origination and Page Response Seizures that are denied becauseof lack of available servers (radios) for a given cell site.

% TDMA Dropped at HandoffTDMA_Lost_Call_Audit_FailureTDMA_Old_Cell_Handoff_Order----------------------------------------------------------------------------------- 100×=

6-32 401-200-112, Issue 11 June 2001



Blocking seen by the end user subscriber can be measured on a system-widebasis. The following formula discounts blocking rates that are based onequipment and facility availability, with the autonomous treatment of DirectedRetry. This formula is valid only for system level measurements. It is not valid on aper-cell basis.

6.3.10.1 Calculation

where:

Service_Denied = Total_Seizures - AMPS(VCC_Orig + VCC_Term)-TDMA(VCC_Orig + VCC_Term) - DR_Last_Try_Set + Orig_Blk_Outgoing_Trk

+_Blk_Network

The peg count "Directed Retry Last Try Set" is used over other directed retrycounts to discount the service denied count because it measures calls thatsuccessfully performed the directed retry feature and produced a second seizure.

6.3.10.2 Goal

<5% (or accepted design criteria, as proposed by customer)


0 To 5%

6.3.10.4 What To Do Next (If You Encounter HighBlocking)

To investigate high subscriber blocking rates, the following peg counts should belooked at:

■ Originations Dropped

■ Seizures Denied - Inadequate Signal Strength

■ Seizures Denied - All Servers Busy

■ Origination Denied - Page

■ Origination Denied - Error

■ Origination Blocked on a Voice Channel

% Subscriber BlockingService_Denied

Total_Seizures Directed_Retry_Last_Try_Sent–--------------------------------------------------------------------------------------------------------------------- 100×=

Total Seizures Orig_Seizure_Attempt Page_Response_Seizures+=

401-200-112, Issue 11 June 2001 6-33



■ Termination Blocked on a Voice Channel

■ Origination Blocked on an Outgoing Trunk

■ Misc. Origination Ineffective Attempts

■ Misc. Incoming Ineffective Attempts

■ Incoming Call Attempts Dropped Due to Overload

■ Origination Voice Channel Confirmation Failure

■ Termination Voice Channel Confirmation Failure

■ Alert Confirmation Failure

6.3.11 % Cell Trunk Group Blocking

The percent of all service requests (origination, termination, or handoff) for a givenLogical Antenna Face (LAF) that are denied because of lack of available servers(radios) on that LAF.

A single overall blocking percentage, combining both cell and MSC (cell trunkgroup) blocking, can be calculated for the following Series II cell configurations:

■ Omni Setup / Omni Voice

■ Directional Setup / Directional Voice


where:

Total_AMPS_Overflow = AMPS(ES_Mobile_Ovfl + LS_Mobile_Ovfl)+ TDMA_Mobile_Analog_Ovfl + AMPS(Seizure_Dny_All_Server_Busy-Servers_Available + Seizure_Dny_All_Server_Busy-No_Servers Available)

Total_AMPS_Peg_Count = AMPS(ES_Mobile_Peg + LS_Mobile_Peg)+ TDMA_Mobile_Analog_Peg + AMPS(Seizure_Dny_All_Server_Busy-Servers_Available + Seizure_Dny_All_Server_Busy-No_Servers Available)

The denominator (Total AMPS Peg Count) includes the Seizure Denied-ServersBusy peg count. This is because blocking rates are typically given as apercentage in the following manner:

% Total AMPS BlockingTotal_AMPS_Overflow

Total_AMPS_Peg_Count------------------------------------------------------------- 100×=

Blocking Rate (in percent)Total_OverflowsTotal_Attempts

----------------------------------------- 100×=

6-34 401-200-112, Issue 11 June 2001



Since Attempts denied by the cell (Seizure Denied-Servers Busy and SeizureDenied-Inadequate Signal) do not generate a trunk group peg count, theseattempts have to be added via the Seizure Denied-Servers Busy term.

1. Dual (Overlaid/underlaid) CellsFor Dual (Overlaid/Underlaid) Cells, this blocking calculation holds only ona physical antenna face (PAF) basis; and only SG1 trunk overflows shouldbe considered (because SG0 overflows automatically try to obtain serviceon SG1). Modify the equation above in the following manner:

where:

Total_AMPS_Overflow = AMPS(ES_Mobile_Ovfl_SG1 + LS_Mobile_Ovfl_SG1)+ TDMA_Mobile_Analog_Ovfl_SG1 + Seizure_Dny_All_Server_Busy

Total_AMPS_Peg_Count = AMPS_ES_Peg(SG0 + SG1) + AMPS_LS_Peg(SG0 +SG1) + TDMA_Mobile_Analog_Peg(SG0 + SG1) + Seiz_Dny_Server_Busy

2. Dual Mode (AMPS/TDMA)Analog Peg Counts and Overflows are included in the Total AMPS Blockingformula. This is because Dual Mode mobiles always peg these counts(unless they originate or terminate as AMPS-only), regardless of TDMAequipage in the system.

3. Directed RetryDirected Retry can be used to lower the end-user's overall perception ofblocking, but should not be considered in using these equations for engi-neering purposes. To generate an "end-user's blocking perception" calcu-lation, subtract the Directed Retry counts (Directed Retry on Origination,Directed Retry on Termination, and Directed Retry from MSC) from thenumerator (Total AMPS Overflow) from the equation above. This is onlyvalid on a cell-cluster or system-wide basis, not on a per-cell or per-facebasis. It should NOT be used for traffic engineering purposes. The equa-tion above contains terms for handoff blocking, which is not always readilyperceivable by the end-user.

4. TDMA BlockingFor TDMA Digital blocking, use the following formula:

Where:

TDMA_Overflow = TDMA Mobile Digital Overflow

TDMA_Blocking = TDMA (SzDnd-SvBsy-ServAvail+SzDnd-SvBsy-No Serv Avail)

% Total AMPS BlockingTotal_AMPS_Overflow

Total_AMPS_Peg_Count------------------------------------------------------------- 100×=

% Total TDMA BlockingTDMA_Overflow TDMA_Blocking+TDMA_Peg_Count TDMA Factors+-------------------------------------------------------------------------------------------- 100×=

401-200-112, Issue 11 June 2001 6-35



TDMA_Peg_Count = Mbl Dig Peg Cnt

TDMA Factors = TDMA (SzDnd-SvBsy-ServAvail+SzDnd-SvBsy-No Serv Avail)

Goal

2% (or accepted design criteria, as proposed by customer)


0 to 2%

6.3.11.3 When You Should Investigate

Per LAF:

Per System:

Since blocking can cause or further aggravate voice quality impairments, it iscritical to maintain low blocking rates.

If the blocking objective is something other than 2% blocking, use that objective inthe relationships above.

6.3.11.4 Reasons For High Percentage

Not enough radios to handle the traffic.

Pct. CTG Blocking < 2% Good LAF

2% < Pct. CTG Blocking < 5% Marginal LAF

Pct. CTG Blocking > 5% Bad LAF

Pct. CTG Blocking < 2% Good System

Pct. CTG Blocking > 2% Bad System

6-36 401-200-112, Issue 11 June 2001



100

100

6.3.11.5 What To Do Next (When High Blockingis Encountered)

Add radios to the faces where blocking exceeds the blocking objective. If thiscannot accomplished without compromising the frequency plan (minimum reusedistance), alternatives are:

■ Split cells

■ Balance load via software adjustment

■ Add radios

■ Dualize cell site

Analyze blocking by cell cluster, not individually. If all faces in a given area(cluster) are blocking in excess of the blocking objective, some channels orgrowth sites need to be added. If only one or a few faces are blocking and othershave spare capacity, determine if, by power-scaling or other modifications, thetraffic can be shifted from the overloaded faces to the underloaded faces (thisimplies a coverage imbalance with respect to radio equipage).

To do proper traffic analysis, examine three indicators: Pct. Cell Blocking, Pct. CellTrunk Group Blocking, and Pct. Trunk Group Utilization (or Trunk Group Usage).Pct. Cell Blocking is closely tied to Pct. Established Calls.

■ For omnidirectional cells (one physical antenna face), Pct. Cell Blockingand Pct. Cell Trunk Group Blocking can be summed, since cell blockingand cell trunk group blocking are mutually exclusive.

■ For directional cells (more than one physical antenna face), Pct. CellBlocking and Pct. Cell Trunk Group Blocking can NOT be summed, unlessdirectional setup is employed.

6.3.12 %Cell Trunk Group Utilization

Provides the ratio of measured carried traffic to theoretical capacity (based uponan established traffic model).


% TDMA Cell Trunk Group UtilizationTDMA_Usage

Theoretical_Capacity_(function_of_members_equipped)---------------------------------------------------------------------------------------------------------------------------------------- ×=

% AMPS Cell Trunk Group UtilizationLS_Usage ES_Usage+

Theoretical_Capacity_(function_of_members_equipped)---------------------------------------------------------------------------------------------------------------------------------------- ×=

401-200-112, Issue 11 June 2001 6-37



Limited Spectrum (LS) Usage, Expanded Spectrum (ES) Usage and TDMA isUsage commonly measured in Erlangs or CCS. An Erlang can be thought of asone channel being busy for one hour. CCS is an abbreviation for hundred-call-seconds, which implies one channel busy for one hundred seconds. Therelationship between Erlang and CCS is: 1 Erlang = 36 CCS. Traditionally, NorthAmerican traffic engineers have used CCS, while Europeans have used theErlang, although many Americans now use Erlangs as well.

The theoretical capacity can be found either by direct calculation or through theuse of standard traffic tables. Several traffic models are available (Erlang-B,Poisson, Retrial).

■ Erlang-B is the most conservative model commonly used (it allows moreusage per channel at the target blocking rate).

■ Poisson is less conservative, and allows less usage per channel at thetarget blocking rate. In this context, the term "conservative" refers tochannel equipage; Erlang-B allows fewer channels to serve the sametraffic load as Poisson at the same blocking rate.

■ Retrial is a modification of Poisson that falls between Erlang-B and Poissonin terms of channel conservation.

6.3.12.2 Goal

85% (on all LAFs) This percentage depends on the system under analysis, as wellas the theoretical model used.


65 to 100%

6.3.12.4 When You Should Investigate

All percentages are based upon experience with cellular traffic; they use theErlang-B model as a reference.

Per LAF:

70% < Pct. CTG Utilization < 90% Good LAF

60% < Pct. CTG Utilization < 70% Marginal LAF

90% < Pct. CTG Utilization < 100% Marginal LAF

6-38 401-200-112, Issue 11 June 2001



Per System:

Since blocking can cause or further aggravate voice quality impairments, it iscritical to maintain low blocking rates.

6.3.12.5 Reasons For High Percentage

Indicates that there are not enough radios to handle the traffic (the system is"under-engineered").

The radios are out-of service.

6.3.12.6 Reasons For Low Percentage

Indicates that there are too many radios to handle the traffic (the system is "over-engineered").

6.3.12.7 What To Do Next

1. If You Encounter High Utilization:

Add radios to faces where utilization is > 90%. If this can’t be accomplishedwithout compromising the frequency plan (minimum reuse distance),alternatives are:

■ Split cell

■ Balance load via software adjustment

■ Add radios

■ Dualize cell site

Pct. CTG Utilization > 100% Bad LAF

Pct. CTG Utilization < 60% Bad LAF

80% < Pct. CTG Utilization < 90% Good System

70% < Pct. CTG Utilization < 80% Marginal System

90% < Pct. CTG Utilization < 100% Marginal System

Pct. CTG Utilization > 100% Bad System

Pct. CTG Utilization < 60% Bad System

401-200-112, Issue 11 June 2001 6-39



Analyze blocking by cell cluster, not individually. If all faces in a given area(cluster) are above the design criteria window, some channels or growthsites need to be added. If only one or a few faces are above it and othershave spare capacity, determine if, by power-scaling or other modifications,the traffic can be shifted from the overloaded faces to the underloaded faces(this implies a coverage imbalance with respect to radio equipage).

2. If You Encounter Low Utilization

Remove radios from service at over-engineered site. Analyze frequencyplan to see if any undesirable reuse can be eliminated (and C/I improved) bythis action.

Analyze blocking by cell cluster, not individually. If all faces in a given area(cluster) are below the design criteria window, some channels need to beremoved. If only one or a few faces are below it and others are running outof capacity, determine, if by power-scaling or other modifications, the trafficcan be shifted from the overloaded faces to the underloaded faces (thisimplies a coverage imbalance with respect to radio equipage).

3. Also Look At:

To do proper traffic analysis, you should look at three indicators: Pct. CellTrunk Group Blocking, Pct. Cell Blocking, and Pct. CTG Utilization (or CellTrunk Group Usage).

6-40 401-200-112, Issue 11 June 2001



Optional Features


7.2 Optional Features 7-2

7.2.1 Call Number Identification Presentation (CNIP) 7-2

7.2.2 Message Waiting Indicator (MWI) 7-3

7.2.3 Interference Look Ahead (INLA) 7-3

7.2.3.1 INLA Functionality 7-3

7.2.3.2 INLA-Related Service Measurements 7-4

7.2.4 Handoff Based on Interference (HOBIT) for TDMA 7-4

7.2.4.1 HOBIT Enhancement (HOBITE) 7-5

7.2.4.1.1 HOBIT Enhancement Threshold 7-5

7.2.4.1.2 HOBIT/INLA Enhancement 7-6


7.2.6 Authentication (AUTH) 7-6

7.2.7 Enhanced Registration 7-7

7.2.8 Digital Locate 7-7

7.2.9 L-EDRU Digital Locate 7-7

7.2.9.1 Digital Locate Function 7-8

7.2.9.2 DVCC Verification with Radio Signal StrengthIndication (RSSI) 7-8

7.2.9.3 Mobile Saturation Resolution 7-9

7.2.10 Voice Privacy 7-97-9

7-9

7-8

7-8

7-7

7-7

7-7

7-6

7-6

7-6

7-5

7-5

7-4

7-4

7-3

7-3

7-3

7-2

7-2

7-1

June 2001 7-1

Contents

7.2.11 Short Message Service (SMS) Over Digital ControlChannel (DCCH) 7-10

7.2.11.1 Mobile-Terminated Operation 7-10

7.2.11.2 Mobile-Originated Operation 7-11

7.2.12 ACELP Vocoder 7-11

7.2.13 Interhyperband Operation 7-12

7.2.13.1 Interhyperband Phase I 7-12

7.2.13.1.1 RC/V Parameters 7-12


7.2.13.2 Interhyperband Phase II 7-13

7.2.13.3 Rogue Mobile Identification 7-13

7.2.13.4 Service Measurements (SM) Overhaul 7-13

7.2.14 Non-Public Network Identifiers (NPNI) and ChargingArea Feature 7-14

7.2.15 Carrier-Specific Teleservices Transport 7-15

7.2.15.1 Interim Over-the-Air Activation 7-15

7.2.15.2 Intelligent Roaming 7-15

7.2.15.3 Expanded Sub-System Numbers 7-16

7.2.16 TDMA Teleservice Screening 7-167-16

7-16

7-15

7-15

7-15

7-14

7-13

7-13

7-13

7-13

7-12

7-12

7-12

7-11

7-11

7-10

7-10

7-2 401-200-112, Issue 11 June 2001



Optional Features 7

7.1 Introduction

This chapter describes optional features that enhance TDMA service that serviceproviders may offer their TDMA customers. Features discussed include:

■ Call Number Identification Presentation

■ Message Waiting Indicator

■ Interference Look Ahead

■ Handoff Based on Interference for TDMA

■ Automatic Radio Reconfiguration

■ Authentication

■ Enhanced registration

■ Digital Locate

■ L-EDRU Digital Locate

■ Voice Privacy

■ Short Message Service over DCCH

■ ACELP Vocoder

■ Interhyperband Operation

■ Rogue Mobile Identification

■ Service Measurements (SM) Overhaul

June 2001 7-1

Optional Features

■ Non-Public Network Identifiers (NPNI) and Charging Area

■ Carrier-Specific Teleservices Transport

■ TDMA Teleservice Screening

7.2 Optional Features

Descriptions of the optional features that enhance operation of TDMA areincluded in the following paragraphs. Refer to Lucent Technologies Practice402-612-500 document for additional information and release numbers of thesefeatures.

7.2.1 Call Number Identification Presentation(CNIP)

The Call Number Identification Presentation (CNIP) feature enables the serviceprovider to offer customers, on a per-subscriber basis, the ability to view either anincoming caller’s directory number (DN) or some other appropriate text on themobile unit display. This feature permits the subscriber to restrict, either on a per-call basis or in total, display of his/her mobile unit DN. CNIP benefits subscribersby allowing them to screen incoming calls and control cost. Service providers cangenerate revenue by offering this feature at a fee.

The CNIP feature is offered within the Feature Transparency Network/ExtendedFTN (FTN/EFTN) borders. There are two prerequisites for CNIP:

■ ANSI-ISUP (Integrated Service digital network User Part) signaling by theMSC and the PSTN

■ Interim Standard 54B (IS-54B) air interface compatibility by the cell anddual mode mobile units

The CNIP feature is part of the CNIP and Registration (CNIP+R) compatibility,which combines the CNIP and Per-MSC CPN (Calling Party Number)Acceptance/Delivery features. The latter feature enables the system to receiveand send CPNs, from and to the PSTN and other systems.

An additional feature, CPN Restriction (CNIR), is included at no extra charge withthe purchase of Per-MSC CPN Acceptance/Delivery. CNIR allows the mobile userto prevent display of his/her CPN and that of the called party terminal on a per-callbasis by entering a code on the mobile unit. CPN display restriction on all calls isimplemented by the service provider through an entry on the subscriber’s profiledatabase. In this case, the cell passes the access code to the MSC, which thenprevents delivery of the CPN to the called party system. The CNIR feature doesnot require new development or changes to the cell sites.

7-2 401-200-112, Issue 11 June 2001


Optional Features

7.2.2 Message Waiting Indicator (MWI)

The Message Waiting Indicator (MWI) feature provides mobile subscribernotification that one or more new voice mail messages are stored in thesubscriber voice mailbox. This feature is available only with Series II Release 1cells and IS-54B dual-mode mobile units, and some newer 553 mobile units.

The status of the subscriber voice mailbox is continuously monitored by the VoiceMail System (VMS). When a new message is stored in the subscriber’s voicemailbox, the VMS seizes a trunk to send message notification and, if known, thenumber of messages received to the MSC, where they are stored.

If the targeted mobile unit is in the:

■ Idle state, the MSC relays message information to all corresponding cells

■ Talk state, the MSC relays the message information to the appropriate cell.

The cell notifies the targeted mobile of the new message status in either IS-54Aair interface Message Waiting Order (MWO) format, or Flash With Information(FWI) format, as follows:

■ MWO to mobile units in analog mode or idle state

■ FWI to mobile units in digital mode

When the status of the subscriber’s voice mailbox is changed—because thesubscriber retrieved the new messages or additional messages came in—theVMS system will seize a trunk to update the massage information sent the MSC.

7.2.3 Interference Look Ahead (INLA)

Interference Look Ahead (INLA) provides a mechanism that increases theprobability that a call will be set up or handed off to a channel with an acceptablelevel of interference. The acceptable level of interference is determined by athreshold value defined by the service provider. INLA-related servicemeasurements are provided on a per-technology and per-Logical Antenna Face(LAF) basis. This feature is Feature Activation File (QFAF)-activated withqualifiers, activated on a per-cell basis.

7.2.3.1 INLA Functionality

INLA allows a cell site to measure the level of interference on a voice channelbefore a mobile is assigned to that channel. Interference measurements areperformed at call setup and handoff. If the interference on a candidate channelexceeds the specified technology-dependent threshold set by the serviceprovider, an attempt is made to reassign the mobile to a different channel. The

401-200-112, Issue 11 June 2001 7-3


Optional Features

INLA feature is used to provide interference management to enhance otherfeature such as the handoff based on interference (HOBIT) feature which isdiscussed in Paragraph 7.2.4.1.1.

The cell performs interference measurements on up to two different voicechannels on call setup and up to three voice channels at handoff. If theinterference measurements exceed the specified threshold on the last attempt,the last channel measured is assigned to the call. If the HIBIT/INLA enhancementfeature in not implemented, the last channel is assigned regardless of theinterference level measured and the possibility that the interference level on thatchannel may be higher than the previous measured channels.

Separate threshold translations for AMPS and TDMA mobiles provide a range ofsettings (from 0 to 127) measured in Received Signal Strength Units (RSSUs).Both thresholds are provided on a per-LAF basis.

These translations are on the fci, cell2, and ecp forms. Translation values on thefci (refer to Paragraph 4.2.12 ) form take precedence over those on the cell2(refer to Paragraph 4.2.2 ) and ecp forms (refer to Paragraph 4.2.1 ); however, ifthe INLA thresholds are left blank on the fci form, the values on the cell2 form areused. If the parameters are blank on both the fci and cell2 forms, the valuesentered on the ecp form are used. Values for these translations are mandatory onthe ecp form.

When the Interference Look Ahead feature is active, it is used in both AMPS andTDMA calls.

7.2.3.2 INLA-Related Service Measurements

With INLA, new service measurements are reported per LAF to track the numberof times interference is detected on a channel during call setup or handoff. Thesemeasurements include the number of times interference is detected on a:

■ RCU following a transmitter activation command (per-LAF)

■ DRU and EDRU following a transmitter activation command (per-LAF)

These service measurements provide the service provider with the means toevaluate the effects of interference on their system.

7.2.4 Handoff Based on Interference (HOBIT) forTDMA

The handoff based on interference for TDMA (HOBIT) feature allows call handoffto another channel on the same logical antenna face (LAF) when interferenceconditions are detected on the current channel. Interference detection is based onup and downlink bit error rate (BER) and uplink frame error rate (FER)

7-4 401-200-112, Issue 11 June 2001


Optional Features

measurements. Handoff is then triggered when any of the error ratemeasurements exceed their respective threshold values that are entered in theRC/V data base. When the mobile unit is operating in a noisy or weak signalenvironment that is not in the cell fringe area, viable handoff candidates may notbe available. If enabled, the HOBIT feature will allow the serving cell to be addedto the candidate list, thus, enabling handoff to another channel on the same LAF.The source of interference may be due to a weak signal in a nominal low noiseenvironment or high levels of noise and/or high levels of interference at aparticular RF channel. In those cases where the source of noise or interference isat a specific RF channel range, a HOBIT triggered handoff to another channel willimprove the call quality.

7.2.4.1 HOBIT Enhancement (HOBITE)

Enhancement to HOBIT will allow handoff to the same LAF in the presence ofexcessive interference only after ensuring that the high BER and FER is due tonoise rather than a weak signal. This enhancement is coupled with modification tothe interference look ahead (INLA) feature that ensures the HOBIT handoff is nothanded off to another noisy channel.

Prior to the HOBIT enhancement, HOBIT handoff to another channel may do verylittle to improve the call quality if the cause of handoff is due to a weak signalrather than interference. In fact the quality of the handoff voice channel may bepoorer. In any case, after the Minimum Handoff Interval for TDMA (refer toParagraph 4.2.12.33 ) specified on the fci form of the RC/V data base is expired,the weak signal resulting in poor quality on the new voice channel will causeanother HOBIT handoff. Because the cause the HOBIT trigger in a weak signal,HOBIT handoff will continue throughout the duration of the call without improvingvoice quality. This continuous handoff increases the potential of dropping the call,thus, contributing to a higher dropped call rate.

7.2.4.1.1 HOBIT Enhancement Threshold

The new enhancement to the HOBIT feature in Cell Release 12.0 reducesdropped call rates due to HOBIT by allowing HOBIT handoffs only after ensuringthat the interference triggering HOBIT is due to noise rather than a weak signal.The HOBIT enhancement, thus, prevents continuous handoff due to weak signalconditions. This enhancement is implemented by defining new uplink anddownlink thresholds for the signal strength values that must be exceeded topermit HOBIT handoffs. When the threshold values are exceeded, the servingface is allowed to be added to the handoff candidate list.

A set of downlink signal strength threshold values are used. The first value,HOBIT Threshold - Downlink to AMPS, is a lower and less stringent value anddefines the downlink minimum signal strength values to allow TDMA to analogonly handoff (refer to Paragraph 4.2.12.11 ). The HOBIT Threshold - Downlink toAMPS is used in conjuction with complementry, INTPHO - parameter (see

401-200-112, Issue 11 June 2001 7-5


Optional Features

Paragraph 4.2.12.8 ) that indicates the minimum uplink signal strength levelmeasured at the cell in RSSI units to allow the serving face to be added to thecandidate list for AMPS service only.

The second threshold value is a more stringent value and defines the downlinkminimum signal strength values to allow TDMA to TDMA or analog handoff (referto Paragraph 4.2.12.13 ). In addition, a HOBIT uplink threshold parameter (referto Paragraph 4.2.12.12 ) must be satisfied to allow TDMA to TDMA or analoghandoff. TDMA to analog handoff for calls that request voice privacy is denied ifthe Allow Handoffs the Terminate Voice Privacy (vpho) translation on the ecp RC/V form is set to No.

7.2.4.1.2 HOBIT/INLA Enhancement

An enhancement to the Interference Look Ahead (INLA) optional feature isprovided to work with the HOBIT enhancement and improve the dropped call rate.Although the HOBIT enhancement ensures that the signal strength of the handoffchannel is greater than the new threshold values, there is no guarantee that thecandidate channel is free of noise. The INLA feature when used with HOBITensures that amount of interference on the new channel is within acceptablelevels. Thus, prior to handing off to a new channel, the INLA feature checks thelevel of interference on the handoff candidate channel. The INLA enhancementcauses the cell to performs interference measurements on up to three differentvoice channels at handoff. Unlike the INLA feature independent of HOBIT, if theinterference measurement on the candidate channel exceeds the specifiedthreshold on the last attempt, the HOBIT attempt is aborted and the call remainson its original channel.

7.2.5 Automatic Radio Reconfiguration (ARR)

The Automatic Radio Reconfiguration (ARR) feature allows for automaticreconfiguration of technology-specific voice radios in order to replace failed setup,locate, beacon, or DCCH radios within the same cell site sector. This featureeliminates the need for installing redundant locate and setup radios to protectagainst system failure if radios fail. If necessary, reconfigure voice channel radiocan provide temporary replacement for TDMA beacon and DCCH radios.

The ARR feature benefits the service provider by eliminating the need forduplicate setup and locate radios, thus freeing slots for revenue-generating voicetraffic.

7-6 401-200-112, Issue 11 June 2001


Optional Features

7.2.6 Authentication (AUTH)

The Authentication feature provides enhanced protection against system accessby unauthorized users. It supports authentication of IS-54B mobile units operatingin either analog or digital mode.

Authentication is accomplished via per-terminal administration of a private keycalled the A key. The A key is programmed into the mobile unit, stored in theAuthentication Center (AC), and never broadcast over the air. To process calls,the mobile unit and the AC generate a random number (RANDSSD) that is sent tothe mobile unit. Both the AC and the mobile unit use the RANDSSD and the A keyvalues to independently calculate a Shared Secret Data (SSD) set. Theauthentication process cross-checks to determine if the SSD value calculated bythe mobile unit agrees with the SSD value calculated by the AC.

Because the SSD set is a function of values (the A key value, which is neverbroadcast, and the random RANDSSD value), it is difficult to reproduce.

7.2.7 Enhanced Registration

Enhanced registration allows more efficient paging by permitting the MobileSwitching Center (MSC) to track mobile unit location during power-up, power-down, and location boundary crossings. (The local boundary is defined as apredetermined geographic area in which the mobile unit can operate without theneed to reregister.)

Enhanced registration provides the MSC with a more accurate list of mobile unitlocations and activity status. When mobile units are paged, this list is consulted toidentify the location of each mobile unit and its activity status, improving pagingchannel efficiency.

7.2.8 Digital Locate

Digital Locate functionality introduced in Cell Release 6.05 validates the selectedtarget handoff radio by confirming that the DVCC is correct and that the uplinksignal strength is appropriate for the handoff. Digital Locate automaticallyswitches to the appropriate antenna face, tunes to the appropriate channel, andsynchronizes to the correct time slot.

7.2.9 L-EDRU Digital Locate

This feature enables an EDRU to take on the functionality of a locate digital radio(L-EDRU) that supports the following algorithms:

401-200-112, Issue 11 June 2001 7-7


Optional Features

■ Hybrid MAHO/digital locate handoff

■ Digital verification color code (DVCC) with receive signal strengthindication (RSSI)

■ Mobile saturation resolution.

The algorithms are individually selectable for any logical antenna face. The hybridMAHO/digital locate handoff algorithm incorporates both the digital verificationcolor code (DVCC) with receive signal strength indication (RSSI) and the mobilesaturation resolution algorithms. For this reason, the selection of the hybridMAHO/digital locate handoff algorithm is mutually exclusive with the selection ofthe other two.

A logical antenna face defines the combination of a physical antenna face and theserver group radio subset associated with the physical antenna face. Essentially,the significance of a logical antenna face is only realized in dual server groupcells. Dual cells are deployed to accommodate system, providing greaterfrequency reuse. In a dual cell configuration, the radios and radio frequenciesassigned to each physical antenna face is divided into primary and secondaryserver groups. The radios in the primary server group operate at low power toservice those mobiles that are close to the cell site. The radios in the secondaryserver group operate at high power to service those mobiles that are farther fromthe cell site. The handoff algorithm uses the mobile signal strength value todetermine the mobile distance from the cell site, hence, which server group is thebest candidate for the handoff.

7.2.9.1 Digital Locate Function

The digital locate feature was introduced in Cell Release 6.05 to complement theMAHO handoff process. This process is triggered as a function of the downlinksignal strength as measured by the mobile and reported back to the cell. Whenthe mobile measured signal strength falls below a threshold level, the mobilebecomes a candidate for handoff. As a result, a handoff sequence is triggered andthe serving cell generates an initial handoff candidate list to identify the beacon orMAHO frequencies of those neighboring cells and sectors that may service thecall better. The cell transmits this list to the mobile. In response, the mobile tunesto each frequency and measures the received signal strength of the beacon/MAHO signal. The measured signal strength from each neighboring cell or sectoris reported to the serving cell so that neighboring cells or sectors that can notbetter service the call are removed from the list.

The introduction of a locate digital radio factors the uplink signal strength values,from the mobile to the neighboring cells and sectors, into the algorithm used todetermine the best handoff candidate. When a mobile becomes a candidate forhandoff, the digital locate radios in the neighboring cells and sectors remaining onthe list are instructed, via the MSC, to tune to the mobile frequency and measurethe uplink signal strength. The digital locate radios are normally installed on a

7-8 401-200-112, Issue 11 June 2001


Optional Features

switchable radio shelf slot so that a single digital locate radio can service up tothree sectors. Thus, two digital locate radios are required in a six-sectordeployment. The reported signal strength value from each digital locate radio isthen factored into the handoff algorithm.

7.2.9.2 DVCC Verification with Radio SignalStrength Indication (RSSI)

DVCC verification with RSSI that is offered in the L-DRU and L-EDRU digitallocate radio ensures that an IS-136 compatible mobile monitors the correctneighbor MAHO or beacon channel. This is done in two ways by having each L-EDRU:

1. Decode the DVCC value transmitted by the mobile

2. Measure the mobile uplink signal strength in RSSI.

The DVCC value is unique to the mobile current serving cell. If the correct DVCCis not decoded, the locate radio is monitoring the signal from an interfering mobileat a distant cell. Under this condition, the result from the locate radio will disqualifyits cell or sector from the handoff candidate list.

Although DVCC decoding and verification is performed by either an L-DRU or anL-EDRU, measuring the mobile uplink signal strength in RSSI is a featureintroduced in ECP Release 10.0 and is performed only by an L-EDRU.The uplinksignal strength is compared with a translatable threshold known as the TDMALocate Reply Threshold value. If the measured value is not above the thresholdvalue, the locate radio will disqualify its cell or sector from the handoff candidatelist.

7.2.9.3 Mobile Saturation Resolution

The mobile saturation feature attempts to resolve a condition where the standardMAHO algorithm creates an empty handoff candidate list even through there areone or more candidate antenna faces in which the mobile reported a saturationsignal strength measurement.

The mobile signal strength measurement of candidate antenna faces is limited to31 mobile IS-54B encoded units (-51 dBm). When the measured signal strength isat or above this level, the mobile reports a saturated level to the serving cell. Thesaturated signal strength reports are factored in with other handoff criteria andtranslation values by the standard MAHO algorithm to create a handoff candidatelist. Notwithstanding that one or more saturation reports and factored in, thestandard MAHO algorithm may create an empty handoff candidate list.

The creation of an empty handoff candidate list under the described condition ispossible in light that other factors such as bias translation are also used by theMAHO algorithm. The bias translation is a parameter entered via the RC/V

401-200-112, Issue 11 June 2001 7-9


Optional Features

platform to favor handoff to a particular cell. Since the saturation report does notidentify the true signal strength, but merely that the mobile signal strengthmeasurement is -51 dBm or more, the actual signal strength may be sufficient toovercome the bias translation value. The mobile saturation feature takes thispossibility into account and initiates locate radio operation with all the antennafaces associated with saturation reports to determine if one of the candidates canbetter service the call.

7.2.10 Voice Privacy

The Voice Privacy feature enables service providers to offer subscribers themeans to protect sensitive mobile conversations from eavesdroppers. Thisfeature encrypts data sent over a TDMA digital traffic channel, preventing thesubscriber’s conversation from being overheard by someone monitoring the radiochannels. (Only the air interface portion of the call is encrypted.)

Voice Privacy requires activation of the Authentication feature. Voice Privacy isprovided on a call only when the mobile unit responds correctly to the globalauthentication challenge.

During call setup, the mobile unit indicates the subscriber’s Voice Privacypreference in the origination or page response message. The subscriber canchange Voice Privacy preference at any time during the call.

When a subscriber selects this feature, a unique voice privacy encryption mask iscalculated at the beginning of each call. The unique mask remains constantthroughout the call. During inter-MCS handoffs, the voice privacy mode isarbitrated between the anchor MSC and the target MSC. The target MSCresponds and maintains the voice privacy mode upon handoff.

Voice Privacy is supported on digital traffic channels only, so subscribers with theVoice Privacy feature are given digital channel preference.

7.2.11 Short Message Service (SMS) Over DigitalControl Channel (DCCH)

The SMS over DCCH feature supports point-to-point mobile-terminated, andsubsequent to release 12.0, mobile-terminated short messages, using the DCCHto send a message to IS-136 compatible mobile units.

7.2.11.1 Mobile-Terminated Operation

The paging feature benefits the service provider by increasing the number of callson the system and competing in the lucrative paging market. For an example, a

7-10 401-200-112, Issue 11 June 2001


Optional Features

subscriber receiving a call-me-back message on a mobile unit can be expected torespond with a call, creating more airtime revenue.

The service provider must select, deploy and maintain a message center (MC) tocollect, store, and forward SMS information. The MC contains the SMS usersubscription data base and performs billing function for SMS. The MC providesthe following:

■ Voice Response Functionality (VRF), which enables the MC to playannouncements to the caller.

■ Store and Forward Functionality (SFF), which enables the MC to store themessage/number and forward it to the MSC at the appropriate time fordelivery to the mobile subscriber.

A variety of message types are available through the MC. Examples include:

■ Short “canned” messages called Short Text Messages (STM)

■ A Reach Me Number (RMN) to contact

■ A brief message dictated by the caller.

7.2.11.2 Mobile-Originated Operation

The mobile-originated R-data optional feature available in Release R12.0 allows asubscriber to send a SMS via an IS-136 compliant mobile unit. R-data refers tothe format in which the text message is carried from sender to receiver. Normally,message data is transmitted over the DCCH channel. However, when the mobileis currently on a DTC voice channel, the message is transmitted over the DTCchannel. The type of message transmission originating from the mobile is groupinto two categories: message acknowledgment and autonomous generated.

Message acknowledgments are generated in response to receive message(mobile terminated SMS message) to inform the sender that the SMS message isterminated and received. The mobile recipient of the message may be asked torespond in one of two ways. One way would be through Delivery Acknowledgmentwhich may be an automatic reply or a selection from a menu of canned repliessuch as Message Received, Will Respond Later, Yes, No, etc. The other form ofSMS message response is a Manual Acknowledgment.This type of messageresponse enables the message recipient to generate his/her own text response.

Autonomous generation permits the mobile subscriber to generate and deliver aSMS message to another subscriber in either a wireless or land-line network. Themechanics of generating this message is similar to that in MessageAcknowledgment except that a destination address is entered along with a SubmitSMS command. After examining the destination address, the Message Centerroutes the message to its destination. The SMS message recipient then

401-200-112, Issue 11 June 2001 7-11


Optional Features

acknowledges the via a Delivery or Manual Acknowledgment. Theacknowledgment is subsequently returned to the sender.

7.2.12 ACELP Vocoder

The Algebraic Code Excited Linear Predictive (ACELP) Vocoder provides a newspeech coding algorithm, improving the voice quality over the existing TDMA Vec-tor-Sum Excited Linear Predictive (VSELP) Vocoder. The VSELP vocoder is sup-ported only by the newer EDRU. Therefore, systems using only DRUs must beupgraded to include a number of EDRU units which supports both the ACELP andVSELP vocoders. The VSELP vocoder was introduced in two phases.

Phase 1, is introduced as a standard feature to PCS service provider to supporttheir PCS TDMA customers operating at the 1.9 GHz spectrum. Since PCS is anew start-up market, initially deployed with the newer VSELP vocoder, this marketdid not need to support ACELP vocoder compatible mobiles.

Phase 2 is introduced as an optional feature enabling cellular service provider tooffer VSELP vocoder support while maintaining support to its existing customershaving mobiles with ACELP vocoder capabilities only.

7.2.13 Interhyperband Operation

Interhyperband operation permits TDMA cellular service providers to handoff andreceive handoffs from bordering TDMA Personal Communication Service (PCS)service areas. The primary difference between TDMA cellular and TDMA PCSwith respect to interhyperband operation is the RF frequency band of operation.Cellular mobiles operate at RF frequencies between 824 and 894 MHz where asPCS mobiles operate at RF frequencies between 1.85 and 1.99 Gz.Interhyperband handoff between TDMA cellular and PCS service providers ispermitted only on those mobile units that provide dual band capabilities to operatein the TDMA cellular and PCS frequency ranges. In addition, this optional featureallows DCCH control channel reselection between the TDMA cellular and PCSservices.

7.2.13.1 Interhyperband Phase I

The interhyperband operation optional feature is introduced in two phases. PhaseI permits handoff from a PCS DTC channel to a cellular analog voice channel(AVC). Because TDMA cellular service provider may not be initially equipped withthe new ACELP vocoder, phase I handoff cannot permit DTC to DTC handoff.Handoff from a PCS DTC channel to a cellular AVC channel is referred to as ahand-down because the call is handed off to an earlier technology. The hand-down relies on MAHO measurements only and may occur in any border sector

7-12 401-200-112, Issue 11 June 2001


Optional Features

that is identified on the PCS neighbor list that is broadcast on the E-BCCH logicchannel.

7.2.13.1.1 RC/V Parameters

Activation of the interhyperband operation optional feature is indicated by a yes(y) parameter for the DCCH I-H OP entry that appears on screen 9 of the cell2recent change/verify (RC/V) form. Other translation entries, such as HBIAS,DIHOPI QFAF, DIHOPACT and Maintain Hyperband Priority are entered on theceqface form. These parameters specify bias to compensate between cellular andPCS MAHO signal strength levels, activated and hyperband priority. Parametersthat identify the protocols that are to be followed for control channel reselectionare entered through the ceqsu2 and resel forms. These parameters are coveredin detail in Chapter 4 of this manual.

7.2.13.1.2 Hyperband Measurement Order

The introduction of phase I allows activation of PCS service prior to fulldeployment over the entire PCS service area by relying on hand-down to thecellular providers in rural areas not yet covered by the PCS service provider. Thecellular/ PCS neighboring cells receive the parameters entered through the RC/Vforms to establish the criteria under which inter-hyperband is to be performed.When a call is initiated on a PCS DCCH channel, the PCS cell solicits a CapabilityReport from the mobile unit to determine if the mobile call may be handed off to acellular AVC channel. Mobiles that respond with 800 MHz AVC return receives a“Hyperband Measurement Order” in place of standard “Measurement Order”. TheHyperband Measurement Order is issued to the cell to compensate for thedifference in signal strength between MAHO measurements made in the PCS andcellular frequency bands. This difference is the HBIAS parameter entered on theRC/V form.

7.2.13.2 Interhyperband Phase II

Phase II of the interhyperband operation optional feature permits bidirectionalDTC to DTC handoffs between cellular and PCS service providers. Theintroduction of Phase II is predicated that the mobile unit is equipped with aVSELP vocoder as a ACELP vocoder. When the mobile unit is solicited for aCapability Report, the mobile unit responds to identify its dual vocodercapabilities, thus, allowing the cellular provider to accept the handoff on DTCchannel.

7.2.13.3 Rogue Mobile Identification

The feature identifies a faulty (rogue) mobile on the network. Normally, a mobilebriefly accesses the setup or DCCH channel to initiate or terminate a call. In thecase of a rogue mobile, a malfunction in the mobile unit causes the mobile to staytuned to the setup or DCCH channel for a longer period, effectively blocking its

401-200-112, Issue 11 June 2001 7-13


Optional Features

access, which is essential for call processing, to other mobiles in the cell servicearea or sector. This optional feature is operated together with the rogue mobiledetection standard feature which was available in Series II software Release 5.32and ECP release 6.1. The rogue mobile detection feature detects the presence ofa suspected rogue mobile on the network. After the presence of a rogue mobile isdetected, the rogue mobile identification optional feature identifies the roguemobile by its mobile identification number (MIN) and electronic serial number(ESN).

7.2.13.4 Service Measurements (SM) Overhaul

Lucent Technologies and customer representatives have formed an SM task forcefor the purpose of addressing customer needs and continuously improvingAUTOPLEX® system performance. One outcome of previous SM discussions hasbeen a complete overhaul to the Service Measurements collection process.

The Service Measurements Overhaul moved the task of current SM collection fromthe ECP to the OMP to provide more flexible SM data storage and retrieval to:

■ Allow for finer granularity of SM (measurements down to a more specificcomponent).

■ Set up more frequent collection and reporting of some or all SM.

■ Generalize reporting functionality for greater independence from internaldata constructs.

The added flexibility permitted by frequent collection and retrieval of some or all SMenables:

■ Current counts on per physical antenna face basis to be split by technology.

■ Current counts on per cell basis to be added on per logical antenna face ba-sis.

■ Several new SM counts to be added per logical antenna face.

■ Several new SM counts to be added per physical antenna face.

7.2.14 Non-Public Network Identifiers (NPNI)and Charging Area Feature

The Non-Public Network Identifiers (NPNI) and Charging Area optional featureallow service providers to setup private/residential networks with different billingrates. A private/residential network is a virtual network were subscribers withsimilar needs or within the same organization receive special treatment such as isexpected in a landline PBX system. The Charging Area sub-component of thisfeature permits the service provider to divide a service area into different privatesystems where each subscriber may enroll for the services offered by a maximumof five private systems.

7-14 401-200-112, Issue 11 June 2001


Optional Features

The physical areas of private networks are defined by User Zones (UZ). Each UZis associated with a Private System Identifier (PSID), or a Residential SystemIdentifier (RSID). A specific UZ is identified by broadcasting its associated PSID/RSID along with the Physical Antenna Face (PAF) information for all the cellswithin the UZ area. Mobiles associated to a private network, for example, mobilesassigned to employees of a corporation, are assigned to a UZ or a group of UZs.Calls made from these mobiles within a designated UZ are billed at preferentialrates. Calls made from the same mobiles outside a designated UZ are billed atpublic network rates.

7.2.15 Carrier-Specific Teleservices Transport

The Carrier-Specific Teleservices Transport (CSTT) optional feature allowsservice providers to maintain competitive advantage by offering new proprietaryfeatures, such as Interim Over-the-Air Activation (OAA), Intelligent Roaming,Expanded Sub-System Numbers (ESSN), and others, to TDMA mobilesubscribers.

The proprietary teleservices feature offered through CSTT is transmitted on thedigital control channel (DCCH) to the mobile unit and is identified as a carrier-specific teleservice message. These messages are initiated by a network entityreferred to as a service platform that is outside the MSC-to-cell system and isowned by the carrier.

The IS-41B standard defines standardized teleservice features by uniqueidentifiers known as the Teleservice ID. Up to 128 Teleservice IDs are reserved(32640–32767) by the IS-41B standard, allowing individual service providers todefine their own proprietary teleservice-based features with procedures that arenot part of the standards.

7.2.15.1 Interim Over-the-Air Activation

Interim Over-the-Air Activation (OAA) is a useful feature that can be implementedby the service provider using the CSTT feature. Interim OAA consists ofprocedures that allow new mobile service subscribers to activate their mobilesimmediately after purchasing their mobile unit. This feature eliminates the need ofa specially trained technician or dealer at the retail outlet where the mobile unit ispurchased, allowing mobile phones to be sold through a wider range of retailoutlets. The reduction in cost, equipment, and personnel will be of substantialbenefit to the service provider. When a new mobile unit is purchased, OAAprocedures include over-the-air programming of the currently active NumberAssignment Module (NAM) to authorize cellular telecommunications service witha specific service provider.

401-200-112, Issue 11 June 2001 7-15


Optional Features

7.2.15.2 Intelligent Roaming

Intelligent Roaming is another feature that can be implemented by the serviceprovider using the CSTT feature. In any cellular telecommunications market,different service providers may be available to cellular subscribers.This featureallows mobile units to select the service provider they prefer whenever the mobilesubscriber roams out of the mobile home cellular telecommunications area.

A mobile unit using Intelligent Roaming searches for a system that is broadcastingone of the mobile preferred System Operator Codes (SOC) on its DCCH. Thisrequires mobile unit to be programmed with a list of preferred SOC. Programmingof SOC lists and other Intelligent Roaming information in mobile units can beaccomplished using the Carrier-Specific Teleservices Transport feature.

7.2.15.3 Expanded Sub-System Numbers

The CSTT feature makes use of the Expanded Sub-System Numbers (ESSN)feature, which is one of the base features of Release 9.0. The ESSN featureaugments the pool of sub-system numbers currently supported by theAUTOPLEX® System 1000. A sub-system number is a number used in the SS7system to specify a particular application within a single network entity. To supportthe Expanded Sub-System Numbers (ESSN) feature, the range of valid numbersfor the ECP SMS Sub-System Number field on the ECP RC/V form is expanded.The field now accepts numbers ranging from 0 to 255. The recommended SMSSub-System Number is either 11 or 254.

7.2.16 TDMA Teleservice Screening

TDMA Teleservice Screening is used to enhance the CSTT optional feature.Service providers can enter into agreements with other service providers to allowdelivery of teleservice messages to roamers in their service areas. This requiresthat a service provider allow teleservice-based messages entity into its MSC fromoutside networks.

A service provider, however, may not want to provide unlimited access to itsnetwork by outside entities. The TDMA Teleservice Screening feature allows aservice provider to control access to its network by specifying another networkfrom which it will accept carrier-specific teleservice messages.

This screening allows a service provider to screen incoming carrier-specificteleservice messages while still allowing interconnection with other networks. Forexample, a service provider may choose to allow a designated network entity todeliver particular types of teleservice-based features to mobiles roaming within itsservice area, while blocking features from other network entities. Thus, this

7-16 401-200-112, Issue 11 June 2001


Optional Features

feature could be used to improve system performance, by screening outunwanted teleservice traffic. Screening does not affect Short Message Service(SMS) message processing and delivery.

The teleservice messages are screened based on the originating SS7 point codeand Teleservice ID. Teleservice messages from unauthorized network addressescan be rejected by the MSC instead of being passed along to mobile units withinthe service provider’s network.

401-200-112, Issue 11 June 2001 7-17


Optional Features

7-18 401-200-112, Issue 11 June 2001



Traffic Capacity Data 1

A.1 Separated System

The following tables show the traffic capacity in Erlangs of separated andintegrated systems. For each TDMA market penetration level, the maximumcapacity values are in bold face type to indicate the optimal mix of analog/TDMARF channels.

In a separated system, TDMA channels and analog channels are co-located butdo not interact; each is governed by its own blocking objective. Calls are cleared(not queued or overflowed to the other technology). In this situation, Erlang Btables apply.

June 2001 A-1

Capacity in Erlangs of a separated system with na analog and nd digital channels,assuming blocked calls are cleared (there is no queue or overflow) and systemblocking of 1.0%, for various proportions of digital traffic.

Table A-1.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 11.23 - - - - - - -

18 3 10.44 11.63 12.36 12.62 12.71 12.79 12.82 12.84

17 6 9.65 10.88 12.34 13.55 14.09 14.35 14.43 14.47

16 9 8.88 10.01 11.45 13.25 14.92 15.90 16.06 16.12

15 12 8.11 9.15 10.47 12.21 14.46 17.35 17.69 17.80

14 15 7.35 8.30 9.51 11.09 13.26 18.49 19.33 19.49

13 18 6.61 7.46 8.55 9.99 11.96 18.49 20.95 21.19

12 21 5.88 6.64 7.62 8.91 10.67 17.23 22.52 22.91

11 24 5.16 5.84 6.70 7.84 9.41 15.25 23.96 24.64

10 27 4.46 5.05 5.81 6.80 8.18 13.30 24.99 26.38

9 30 3.78 4.29 4.94 5.79 6.97 11.40 25.02 28.13

8 33 3.13 3.55 4.09 4.81 5.81 9.54 22.63 29.89

7 36 2.50 2.84 3.29 3.87 4.68 7.75 18.71 31.66

6 39 1.91 2.18 2.52 2.98 3.62 6.04 14.80 33.43

5 42 1.36 1.56 1.81 2.15 2.62 4.43 11.09 35.21

4 45 .87 1.00 1.17 1.39 1.71 2.95 7.62 37.00

3 48 .46 .53 .62 .75 .93 1.65 4.50 38.80

2 51 .15 .18 .22 .26 .34 .63 1.91 40.60

1 54 .01 .01 .02 .02 .03 .06 .26 42.41

0 57 - - - - - - - 44.22

A-2 401-200-112, Issue 11 June 2001


Capacity in Erlangs of a separated system with na analog and nd digital channels,assuming blocked calls are cleared (no queue or overflow) and system blocking of2.0%, for various proportions of digital traffic.

Table A-2.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 12.33 - - - - - - -

18 3 11.49 12.80 13.53 13.80 13.90 13.98 14.02 14.04

17 6 10.66 12.03 13.64 14.85 15.36 15.63 15.72 15.76

16 9 9.83 11.10 12.73 14.71 16.34 17.26 17.43 17.50

15 12 9.01 10.18 11.69 13.67 16.14 18.81 19.15 19.26

14 15 8.20 9.28 10.65 12.47 14.96 20.06 20.87 21.04

13 18 7.40 8.38 9.63 11.28 13.55 20.53 22.58 22.83

12 21 6.61 7.49 8.62 10.10 12.15 19.65 24.24 24.63

11 24 5.84 6.62 7.62 8.95 10.78 17.69 25.78 26.43

10 27 5.08 5.77 6.65 7.82 9.43 15.54 27.08 28.25

9 30 4.34 4.94 5.70 6.71 8.11 13.43 27.77 30.08

8 33 3.63 4.13 4.77 5.63 6.82 11.36 26.92 31.92

7 36 2.94 3.35 3.88 4.58 5.57 9.34 23.35 33.76

6 39 2.28 2.60 3.02 3.58 4.37 7.40 18.79 35.61

5 42 1.66 1.90 2.22 2.64 3.23 5.55 14.41 37.46

4 45 1.09 1.26 1.47 1.77 2.18 3.81 10.23 39.32

3 48 .60 .70 .83 1.00 1.25 2.25 6.35 41.19

2 51 .22 .26 .32 .39 .50 .95 2.98 43.06

1 54 .02 .03 .03 .04 .06 .13 .56 44.94

0 57 - - - - - - - 46.82

401-200-112, Issue 11 June 2001 A-3


Capacity in Erlangs of a separated system with na analog and nd digital channels,assuming blocked calls are cleared and system blocking of 5.0%, for variousproportions of digital traffic.

Table A-3.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 14.32 - - - - - - -

18 3 13.39 14.90 15.65 15.92 16.04 16.13 16.17 16.19

17 6 12.46 14.14 15.96 17.14 17.63 17.94 18.03 18.08

16 9 11.54 13.10 15.10 17.34 18.84 19.71 19.91 19.99

15 12 10.63 12.08 13.93 16.38 19.10 21.40 21.78 21.90

14 15 9.73 11.06 12.77 15.05 18.16 22.89 23.65 23.83

13 18 8.83 10.05 11.61 13.70 16.61 23.88 25.51 25.77

12 21 7.95 9.05 10.47 12.36 15.01 23.95 27.33 27.72

11 24 7.08 8.06 9.34 11.04 13.42 22.75 29.07 29.68

10 27 6.22 7.09 8.22 9.73 11.86 20.18 30.68 31.64

9 30 5.37 6.13 7.12 8.45 10.31 17.65 32.00 33.61

8 33 4.54 5.20 6.04 7.18 8.79 15.14 32.77 35.58

7 36 3.74 4.28 4.99 5.95 7.30 12.68 32.26 37.56

6 39 2.96 3.40 3.98 4.75 5.85 10.27 28.83 39.55

5 42 2.22 2.56 3.00 3.60 4.46 7.93 22.91 41.54

4 45 1.52 1.77 2.08 2.52 3.14 5.69 17.01 43.53

3 48 .90 1.05 1.25 1.53 1.92 3.60 11.35 45.53

2 51 .38 .45 .55 .68 .88 1.74 6.08 47.53

1 54 .05 .07 .08 .11 .15 .36 1.67 49.54

0 57 - - - - - - - 51.55

A-4 401-200-112, Issue 11 June 2001


Capacity in Erlangs of a separated system with na analog channels and nd digitalchannels, assuming blocked calls are cleared and 1.0% blocking of the analogchannels, for various proportions of digital traffic.

Table A-4.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 11.23 - - - - - - -

18 3 10.44 11.48 12.12 12.39 12.52 12.62 12.67 12.69

17 6 9.65 10.72 11.98 13.04 13.60 13.98 14.10 14.17

16 9 8.88 9.86 11.09 12.62 14.08 15.27 15.54 15.65

15 12 8.11 9.01 10.14 11.58 13.45 16.37 16.96 17.14

14 15 7.35 8.17 9.19 10.50 12.25 16.93 18.35 18.63

13 18 6.61 7.34 8.26 9.44 11.01 16.32 19.68 20.13

12 21 5.88 6.53 7.34 8.39 9.79 14.69 20.88 21.62

11 24 5.16 5.73 6.45 7.37 8.60 12.90 21.70 23.11

10 27 4.46 4.96 5.58 6.37 7.44 11.15 21.35 24.59

9 30 3.78 4.20 4.73 5.40 6.30 9.46 18.89 26.05

8 33 3.13 3.48 3.91 4.47 5.21 7.82 15.64 27.50

7 36 2.50 2.78 3.13 3.57 4.17 6.25 12.50 28.92

6 39 1.91 2.12 2.39 2.73 3.18 4.77 9.55 30.31

5 42 1.36 1.51 1.70 1.94 2.27 3.40 6.80 31.65

4 45 .87 .97 1.09 1.24 1.45 2.17 4.35 32.92

3 48 .46 .51 .57 .65 .76 1.14 2.28 34.06

2 51 .15 .17 .19 .22 .25 .38 .76 34.97

1 54 .01 .01 .01 .01 .02 .03 .05 35.34

401-200-112, Issue 11 June 2001 A-5



Table A-5.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 12.33 - - - - _ - -

18 3 11.49 12.62 13.27 13.54 13.67 13.78 13.83 13.86

17 6 10.66 11.84 13.20 14.26 14.80 15.19 15.33 15.40

16 9 9.83 10.92 12.29 13.93 15.38 16.52 16.81 16.93

15 12 9.01 10.01 11.26 12.87 14.89 17.67 18.27 18.48

14 15 8.20 9.11 10.25 11.71 13.67 18.37 19.71 20.02

13 18 7.40 8.22 9.25 10.57 12.34 18.04 21.08 21.56

12 21 6.61 7.35 8.27 9.45 11.02 16.52 22.32 23.09

11 24 5.84 6.49 7.30 8.35 9.74 14.60 23.25 24.62

10 27 5.08 5.65 6.36 7.26 8.47 12.71 23.33 26.13

9 30 4.34 4.83 5.43 6.21 7.24 10.86 21.52 27.62

8 33 3.63 4.03 4.53 5.18 6.05 9.07 18.14 29.10

7 36 2.94 3.26 3.67 4.19 4.89 7.34 14.68 30.54

6 39 2.28 2.53 2.84 3.25 3.79 5.69 11.38 31.94

5 42 1.66 1.84 2.07 2.37 2.76 4.14 8.29 33.28

4 45 1.09 1.21 1.37 1.56 1.82 2.73 5.46 34.54

3 48 .60 .67 .75 .86 1.00 1.51 3.01 35.66

2 51 .22 .25 .28 .32 .37 .56 1.12 36.54

1 54 .02 .02 .03 .03 .03 .05 .10 36.82

A-6 401-200-112, Issue 11 June 2001



Table A-6.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 14.32 - - - - - - -

18 3 13.39 14.66 15.32 15.59 15.73 15.85 15.91 15.94

17 6 12.46 13.85 15.35 16.40 16.93 17.33 17.49 17.57

16 9 11.54 12.83 14.43 16.24 17.63 18.73 19.05 19.20

15 12 10.63 11.81 13.29 15.18 17.39 19.95 20.58 20.82

14 15 9.73 10.81 12.16 13.90 16.20 20.79 22.07 22.43

13 18 8.83 9.82 11.04 12.62 14.72 20.85 23.48 24.03

12 21 7.95 8.83 9.94 11.36 13.25 19.71 24.78 25.62

11 24 7.08 7.86 8.85 10.11 11.79 17.69 25.82 27.20

10 27 6.22 6.91 7.77 8.88 10.36 15.54 26.30 28.75

9 30 5.37 5.97 6.71 7.67 8.95 13.43 25.51 30.28

8 33 4.54 5.05 5.68 6.49 7.57 11.36 22.66 31.78

7 36 3.74 4.15 4.67 5.34 6.23 9.34 18.69 33.24

6 39 2.96 3.29 3.70 4.23 4.93 7.40 14.80 34.65

5 42 2.22 2.46 2.77 3.17 3.70 5.55 11.09 35.99

4 45 1.52 1.69 1.91 2.18 2.54 3.81 7.62 37.22

3 48 .90 1.00 1.12 1.28 1.50 2.25 4.50 38.28

2 51 .38 .42 .48 .54 .64 .95 1.91 39.06

1 54 .05 .06 .07 .08 .09 .13 .26 39.15

401-200-112, Issue 11 June 2001 A-7


1.2 Integrated System

In an integrated system, the two technologies share resources, allowing TDMAcalls to overflow to analog when TDMA blocking occurs. This is equivalent toqueuing a blocked call, rather than clearing or dropping it. In this situation, ErlangC tables apply for traffic capacity planning.

Capacity in Erlangs of an integrated system with na analog and nd digitalchannels, assuming infinite queuing capability for the analog channels and aprobability of delay for the system of 1.0%, for various proportions of digital traffic.

Table A-7.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 10.24 - - - - - - -

18 3 9.52 10.61 11.32 11.56 11.65 11.74 11.77 11.80

17 6 8.80 9.89 11.24 12.47 12.98 13.23 13.33 13.39

16 9 8.09 9.10 10.37 12.01 13.70 14.70 14.90 15.00

15 12 7.39 8.32 9.49 11.02 13.06 16.07 16.48 16.65

14 15 6.71 7.55 8.61 10.01 11.91 17.21 18.07 18.32

13 18 6.03 6.79 7.75 9.02 10.74 16.70 19.61 20.02

12 21 5.36 6.04 6.91 8.04 9.59 15.23 21.10 21.74

11 24 4.71 5.31 6.08 7.09 8.46 13.48 22.47 23.48

10 27 4.08 4.60 5.27 6.15 7.35 11.76 23.18 25.24

9 30 3.46 3.91 4.49 5.24 6.28 10.09 22.41 27.01

8 33 2.87 3.24 3.73 4.36 5.23 8.46 19.34 28.81

7 36 2.30 2.60 3.00 3.52 4.23 6.89 15.94 30.63

6 39 1.76 2.00 2.31 2.71 3.28 5.38 12.66 32.46

5 42 1.26 1.44 1.66 1.96 2.38 3.96 9.53 34.32

4 45 .81 .93 1.08 1.28 1.57 2.66 6.59 36.19

3 48 .43 .50 .58 .70 .86 1.51 3.94 38.09

A-8 401-200-112, Issue 11 June 2001


2 51 .15 .17 .21 .25 .32 .59 1.71 40.01

1 54 .01 .01 .02 .02 .03 .06 .25 41.97

Table A-7.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

401-200-112, Issue 11 June 2001 A-9



Table A-8.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 11.01 - - - - - - -

18 3 10.25 11.42 12.13 12.38 12.48 12.57 12.62 12.64

17 6 9.51 10.69 12.13 13.34 13.84 14.13 14.24 14.30

16 9 8.77 9.86 11.25 13.01 14.66 15.64 15.88 15.99

15 12 8.04 9.05 10.33 12.00 14.19 17.06 17.53 17.71

14 15 7.31 8.24 9.41 10.95 13.04 18.18 19.17 19.46

13 18 6.60 7.44 8.51 9.90 11.81 18.24 20.79 21.23

12 21 5.90 6.66 7.62 8.87 10.59 16.87 22.36 23.02

11 24 5.21 5.89 6.74 7.86 9.40 15.04 23.75 24.83

10 27 4.54 5.13 5.88 6.87 8.22 13.21 24.79 26.67

9 30 3.88 4.39 5.04 5.90 7.07 11.42 24.74 28.52

8 33 3.25 3.68 4.23 4.96 5.96 9.67 22.28 30.40

7 36 2.63 2.99 3.44 4.05 4.87 7.97 18.63 32.29

6 39 2.05 2.33 2.69 3.17 3.83 6.33 15.03 34.21

5 42 1.50 1.71 1.98 2.35 2.85 4.76 11.57 36.15

4 45 .99 1.14 1.33 1.58 1.94 3.30 8.27 38.12

3 48 .55 .64 .75 .91 1.12 1.97 5.20 40.11

2 51 .21 .25 .30 .36 .46 .86 2.50 42.14

1 54 .02 .02 .03 .04 .06 .12 .50 44.26

A-10 401-200-112, Issue 11 June 2001



Table A-9.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 12.20 - - - - - - -

18 3 11.40 12.69 13.40 13.67 13.78 13.88 13.93 13.96

17 6 10.61 11.94 13.52 14.71 15.21 15.54 15.67 15.74

16 9 9.82 11.06 12.66 14.61 16.24 17.16 17.42 17.55

15 12 9.04 10.19 11.66 13.57 16.00 18.68 19.18 19.39

14 15 8.27 9.33 10.68 12.44 14.87 20.02 20.93 21.26

13 18 7.51 8.48 9.71 11.32 13.53 20.52 22.67 23.15

12 21 6.76 7.63 8.75 10.21 12.22 19.49 24.34 25.06

11 24 6.02 6.80 7.80 9.12 10.92 17.60 25.85 27.00

10 27 5.29 5.98 6.87 8.04 9.65 15.61 27.19 28.97

9 30 4.57 5.18 5.95 6.98 8.39 13.64 27.70 30.96

8 33 3.87 4.39 5.06 5.94 7.16 11.71 26.79 32.98

7 36 3.19 3.62 4.19 4.93 5.95 9.82 23.33 35.02

6 39 2.53 2.89 3.34 3.95 4.78 7.97 19.26 37.10

5 42 1.91 2.18 2.53 3.00 3.66 6.17 15.28 39.21

4 45 1.32 1.52 1.77 2.11 2.59 4.46 11.40 41.37

3 48 .79 .91 1.08 1.30 1.61 2.85 7.68 43.59

2 51 .34 .40 .48 .59 .75 1.42 4.22 45.94

1 54 .05 .06 .08 .10 .14 .31 1.25 48.57

401-200-112, Issue 11 June 2001 A-11


Capacity in Erlangs of an integrated system with na analog channels and nddigital channels, assuming infinite queuing capability and 1.0% probability of delayfor the analog channels, for various proportions of digital traffic.

Table A-10.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 10.24 - - - - - - -

18 3 9.52 10.50 11.16 11.40 11.49 11.57 11.61 11.63

17 6 8.80 9.78 10.97 12.10 12.65 12.89 12.98 13.03

16 9 8.09 8.99 10.12 11.55 13.08 14.17 14.35 14.45

15 12 7.39 8.22 9.24 10.56 12.31 15.34 15.72 15.87

14 15 6.71 7.45 8.38 9.58 11.18 16.12 17.14 17.30

13 18 6.03 6.70 7.53 8.61 10.05 14.99 18.38 18.74

12 21 5.36 5.96 6.70 7.66 8.94 13.41 19.62 20.18

11 24 4.71 5.24 5.89 6.73 7.85 11.78 21.21 21.61

10 27 4.08 4.53 5.10 5.82 6.79 10.19 19.94 23.04

9 30 3.46 3.85 4.33 4.94 5.77 8.65 17.32 24.47

8 33 2.87 3.18 3.58 4.09 4.78 7.16 14.33 25.88

7 36 2.30 2.55 2.87 3.28 3.83 5.74 11.48 27.27

6 39 1.76 1.95 2.20 2.51 2.93 4.40 8.79 28.63

5 42 1.26 1.40 1.57 1.80 2.10 3.15 6.30 29.95

4 45 .81 .90 1.01 1.16 1.35 2.03 4.05 31.19

3 48 .43 .48 .54 .61 .72 1.07 2.15 32.33

2 51 .15 .16 .18 .21 .24 .37 .73 33.25

1 54 .01 .01 .01 .01 .02 .02 .05 33.71

A-12 401-200-112, Issue 11 June 2001



Table A-11.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 11.01 - - - - - - -

18 3 10.25 11.30 11.95 12.20 12.30 12.39 12.43 12.45

17 6 9.51 10.56 11.82 12.93 13.47 13.73 13.84 13.90

16 9 8.77 9.74 10.96 12.48 13.99 15.04 15.25 15.36

15 12 8.04 8.93 10.04 11.48 13.35 16.21 16.65 16.83

14 15 7.31 8.13 9.14 10.45 12.19 17.00 18.05 18.30

13 18 6.60 7.34 8.25 9.43 11.00 16.37 19.49 19.78

12 21 5.90 6.56 7.38 8.43 9.84 14.76 20.87 21.25

11 24 5.21 5.79 6.52 7.45 8.69 13.03 21.75 22.72

10 27 4.54 5.04 5.67 6.49 7.57 11.35 22.11 24.18

9 30 3.88 4.31 4.85 5.55 6.47 9.71 19.47 25.63

8 33 3.25 3.61 4.06 4.64 5.41 8.12 16.17 27.07

7 36 2.63 2.93 3.29 3.76 4.39 6.58 13.16 28.48

6 39 2.05 2.27 2.56 2.92 3.41 5.12 10.24 29.86

5 42 1.50 1.66 1.87 2.14 2.50 3.74 7.49 31.20

4 45 .99 1.10 1.24 1.42 1.66 2.48 4.97 32.46

3 48 .55 .62 .69 .79 .92 1.39 2.77 33.59

2 51 .21 .23 .26 .30 .35 .53 1.05 34.50

1 54 .02 .02 .02 .03 .03 .05 .10 34.89

401-200-112, Issue 11 June 2001 A-13



Table A-12.

na nd 0% 10% 20% 30% 40% 60% 80% 100%

19 0 12.20 - - - - - - -

18 3 11.40 12.55 13.20 13.45 13.56 13.65 13.70 13.72

17 6 10.61 11.79 13.16 14.25 14.75 15.06 15.18 15.25

16 9 9.82 10.91 12.30 13.96 15.46 16.43 16.66 16.78

15 12 9.04 10.05 11.30 12.92 14.97 17.66 18.12 18.31

14 15 8.27 9.19 10.34 11.82 13.81 18.69 19.59 19.84

13 18 7.51 8.35 9.39 10.73 12.52 18.46 21.08 21.37

12 21 6.76 7.51 8.45 9.65 11.26 16.89 22.54 22.90

11 24 6.02 6.68 7.52 8.59 10.03 15.04 23.65 24.42

10 27 5.29 5.87 6.61 7.55 8.81 13.21 24.95 25.92

9 30 4.57 5.08 5.71 6.53 7.61 11.42 22.56 27.41

8 33 3.87 4.30 4.84 5.53 6.45 9.67 19.35 28.87

7 36 3.19 3.54 3.99 4.55 5.31 7.97 15.94 30.31

6 39 2.53 2.81 3.16 3.62 4.22 6.33 12.66 31.72

5 42 1.91 2.12 2.38 2.72 3.18 4.76 9.53 33.07

4 45 1.32 1.47 1.65 1.88 2.20 3.30 6.59 34.34

3 48 .79 .88 .98 1.13 1.31 1.97 3.94 35.48

2 51 .34 .38 .43 .49 .57 .86 1.71 36.36

1 54 .05 .06 .06 .07 .08 .12 .25 36.64

A-14 401-200-112, Issue 11 June 2001



Handoff Candidate List Generation 2

The following is an overview of the steps performed to produce a handoffcandidate list for TDMA. The final result can be affected by active features suchas Strongest Only.

When a locate trigger is generated, the MAHO process performs the followingsteps to determine a candidate for handoff:

1. Eliminate the serving Logical Antenna Face (LAF) as a candidate.

2. Eliminate all candidate LAFs that have a BIAS of +31 (62 dB).

3. Eliminate all faces that are not equipped to handle the allowable callmode.

4. Eliminate all potential hand off candidate faces (both server groups) forwhich NSIG is below the Interference Protection Handoff Threshold(INTPH) (NSIG =NSIGavg + C3OFFSET).

where,

NSIG is the averaged mobile measurement of the neighbor MAHOchannel,

C3OFFSET is translatable and is only applied for class 3 and 4 mobiles(i.e., C3OFFSET = 0 for class 1 and class 2 mobiles).

Averaging is performed in accordance with the mobile measurementaveraging feature.

5. If the mobile is being served on the inner server group (SG0) of a dual cell,and the mobile signal (MSIG) is above the mobile signal threshold(MOTHRESH) for the serving LAF, eliminate all SG1 candidates of the

June 2001 B-1

serving cell. MSIG is the averaged serving channel signal strength asreported by the mobile. The averaging is done according to the mobilemeasurement averaging feature.

If the mobile is being served on the outer server group (SG1) of a dual cell, thesystem performs the following three steps to determine the normalized signalstrength of the inner server group (SG0), upward handoff candidate. Otherwise,steps 6, 7, and 8 are skipped and the process continues with “Selection ofRemaining Handoff Candidates (Other than Upward),” below.

Selection of Upward Handoff Candidates

6. Compute NORMSIG

NORMSIG = NSIG +2*(MCAC - D_VCACsg0) - MOTHRESHsg0 - BIASsg0

where,

all values are entered in IS-54B encoded units,

NSIG is the adjusted averaged mobile reported neighbor MAHO channelsignal strength measurement from the candidate sector. The averaging isdone according to the mobile measurement averaging feature.

MCAC is the MAHO Channel Attenuation Code for the MAHO Channel onthe candidate sector,

D_VCACsg0 is the TDMA Voice Radio Attenuation Code for Server Group0 of the candidate sector,

MOTHRESHsg0 is the Mobile Signal Threshold for the candidate sector,and

BIASsg0 is the bias specified in the MAHO neighbor list for the ServerGroup 0 candidate sector.

7. Eliminate any candidate for which NORMSIG is negative.

8. Form a “Preliminary” candidate list by ranking the remaining serving cellSG0 candidates.

Selection of Remaining Handoff Candidates (Other Than Upward)

9. Compute NORMSIG for all remaining candidates in SG1 of serving cell andother server groups of the neighbor cells.

NORMSIGcand = NSIG - MSIG - BIAScand

where the above definitions apply.

B-2 401-200-112, Issue 11 June 2001


10. Eliminate any candidate for which NORMSIGcand is negative.

11. If MSIG is greater than or equal to the mobile secondary threshold, elimi-nate all potential candidates for which NSIG is less than the candidatefaces DTH.

12. If MSIG is less than the mobile secondary threshold, mark all candidatesLAFs for which NSIG is less than the decision threshold as “Secondary”candidates.

13. Eliminate duplicate candidate LAFs, keeping the highest NORMSIG.

14. Rank all remaining inner server group candidate faces.

15. Rank all remaining outer server group candidate faces that have not beendesignated as “Secondary.”

16. Form a candidate list beginning with a list of “Preliminary” serving cell SG0upward handoff candidates (from Step 8 above), if available, and append-ing the list of inner server group candidates then the outer server groupcandidates.

17. If the list has fewer than three candidates, and there are “Secondary” can-didates, append them to the candidate list. These secondary candidatesare rank ordered, with inner server group candidates used before outerserver group candidates.

18. Truncate the candidate list to three candidates.

19. If the list is empty or has fewer than three candidates, the TDMA HandoffBased on Interference Feature is active, the minimum Interference HandoffInterval Timer has expired, and “interference” is detected, add the servingface to the candidate list.

20. Interference is determined to exist if the measured Bit Error Rate (BER) atthe cell or the averaged BER measured at the mobile is greater than theBER threshold, or if the measured Frame Error Rate (FER) at the cell ishigher than the FER Threshold.

At this point, the full candidate list generation is finished, and the system attemptsto find radios on the candidate sectors to serve the call.

401-200-112, Issue 11 June 2001 B-3


B-4 401-200-112, Issue 11 June 2001



Link Budget 3

C.1 Introduction

In this appendix, the link budget for the IS-136 system is addressed. A linkbudget is a full accounting of all signal level gains and losses, noise factors andRF impairments affecting the RF receive and transmit paths. These includepropagation loss, antenna gain, connector loss, noise, etc. The goal of the linkbudget is twofold: achieve the same coverage for DTCs and DCCHs, andobtain a balanced link.

C.2 Creating the Link Budget

Creating the link budget involves three steps:

■ Creating the same coverage footprint for DTCs and DCCHs

■ Balancing uplink and downlink

■ Evaluating transmit and receive paths

C.2.1 Same Coverage Footprint for DTCs andDCCHs

To obtain the same coverage footprint for DTCs and DCCHs, use a C/N (carrier-to-total noise power ratio) that satisfies both the BER (Bit Error Rate)requirement for DTC and the WER (Word Error Rate) requirement for DCCH,when planning the link budget. The C/N can be obtained and expressedmathematically as:

June 2001 C-1

Simulation results obtained in the laboratory, demonstrated that the (C/N)DTC isgreater than (C/N)DCCH. Therefore, EQ 1 can be simplified as:

C.2.2 Balanced Link

The balanced link balances the downlink [forward link, from Base Station (BS) toMobile Station (MS)] and the uplink (reverse link, from MS to BS), therebyachieving the same coverage in both directions. Because the maximum EffectiveIsotropic Radiated Power (EIRP) of the MS is much lower than that of the BS, thelink budget is limited by the uplink. For a given MS maximum EIRP, the requiredBS EIRP for achieving the balanced link can be determined by the followingprocedures:

1. On the uplink, calculate the allowable propagation loss based on the MSmaximum EIRP, the effective BS and MS antenna gains, the RX diversitygain at BS, and the minimum BS received signal power required for achiev-ing the acceptable carrier-to-total noise power ratio (C/N) at the BS.

2. On the downlink, calculate the allowable propagation loss based on the BSmaximum EIRP, the effective BS and MS antenna gains, and the minimumMS received signal power required for achieving an acceptable C/N ratio atthe MS.

3. To obtain the required BS EIRP for the balanced links, lower the BS trans-mitter output power by the amount equal to the difference between the pathlosses obtained in Steps 1 and 2.

Details of these calculations are shown in the link budget spread sheet presentedin Table C-1. This link budget is prepared based on the assumptions given inTable C-2.

C/N = MAX[(C/N)DTC, (C/N)DCCH] (EQ 1)

where (C/N)DTC = minimum C/N for achieving acceptable BER for DTC

(C/N)DCCH = minimum C/N for achieving acceptable WER for DCCH

C/N = (C/N )DTC (EQ 2)

C-2 401-200-112, Issue 11 June 2001


C.2.3 Receive Path

On the receive (RX) path, calculate the minimum received signal strengthrequired for achieving an acceptable C/N ratio. In order to meet the requirementsin Steps 1 and 2 above, evaluate the C/N (carrier-to-total noise power ratio)performance of the system. Because N is total noise, which includes thermalnoise and all interference coming from co-channel, adjacent channel, andalternate channel sources, C/N can be expressed as:

*Nun includes all unexpected man-made noise powers generated by motorignition, microwave appliances and other sources near the receiver.

(EQ 3)

with

Itot = Ico + Iadj + Ialt (EQ 4)

where C = carrier power (mw)

N = total noise power (mw)

Nt thermal noise power (mw)

Nun = unexpected man-made noise power (mw)*

Itot = total interference power (mw)

Ico = co-channel interference power (mw)

Iadj = adjacent channel interference power (mw)

Ialt = alternate channel interference power (mw)

CN---- = C

Nt Num Itot+ +----------------------------------------

401-200-112, Issue 11 June 2001 C-3


The J4 port is the transmit/receive port connecting the cell site to the antennaterminal through a coaxial cable; it serves as the point of reference for all powerlevels, including carrier, noise and interference. The Nt at J4 is expressed as:

[Nt] = 60 + 10 Log10 (k T B) + [NF] (EQ 5)

where: [Nt] = thermal noise at J4 (dBm)

k = Boltzmann constant

(1.38 x 10-23 J/oK)

T = room temperature (oK)

B = bandwidth (30 kHz)

[NF] = receive noise figure (dB)

Table C-1 Example of TDMA Link Budgets (Three-Sector Cells)

(K, m) = 7 3.50

100 [Km/hr] A B

RX Path Parameters Uplink2 BS

Downlink 2MS

1. Minimum Signal 2 J4 [Smin,rcvr]

a. Thermal Noise Power [Nt] 2 J4

i. Reference Thermal Temperature [T] [°K] 290 290

ii. Channel Bandwidth [B] [kHz] 30 30

iii. Noise Figure [NF] 2J4 [dB] 5 7

iv. [Nt] [dBm] -124 -122

b. [C/Itot] 2 J4

i. [C/Ico] (3-sector, N=7) [dB] 21.08 21.08

ii. [C/Iadj] (3-sector, N=7) [dB] 60 60

iii. [C/Ialt] (3-sector, N=7) [dB] 60 60

C-4 401-200-112, Issue 11 June 2001


iv. [C/Itot] (3-sector, N=7) [dB] 21.07 21.07

c. [Nun], Unexpected Noise [dBm] -200.00 -200.00

d. Desired BER [%] 2.00 2.00

e. Req’d C/N 2 J4, w/o RX Div [dB] 18.8 17.5

f. RX Diversity Gain [Gdiv] [dB] 4 0

g. [Smin,revr] [dBm] -108.24 -102.19

2. Effective Antenna Gain [Gant,eff]

a. Antenna Gain [Gant] [dBi] 13 2

b. Cable, Jumper and ConnectorLosses [Lcjc]

[dB] 3.5 0

c. Body Loss [Lbody] [dB] 0 2

d. [Gant,eff] [dB] 9.5 0

3. Minimum Signal 2 RX Antenna [Sant] [dBm] -117.74 -102.19

TX Path Parameters Uplink 2MS

Downlink2BS

4. Maximum Transmitter Output[Pmax,xmtr]

[watt] 0.6 20

[dBm] 27.78 43.01

5. Effective Antenna Gain [Gant,eff]

a. Antenna Gain [Gant] [dBi] 2 13

b. Cable, Jumper and ConnectorLosses [Lcjc]

[dB] 0 3.5

c. Body Loss [Lbody] [dB] 2 0

d. [Gant,eff] [dB] 0 9.5

6. Filter Loss [Ltx, filter] [dB] 0 0.5

7. TX EIRP [PEIRP] [dBm] 27.78 52.01

8. Margin (slow fading, shadow, etc.) (M) [dB] 5.4 5.4

Table C-1 Example of TDMA Link Budgets (Three-Sector Cells)—Continued

401-200-112, Issue 11 June 2001 C-5


9. Building Penetration [LBP] [dB] 0 0

10. Allowable Path Loss [Lp] [dB] 140.12 148.81

11. Balanced Path Loss (MIN[10.A, 10.B]) [dB] 140.12

12. Path Imbalance (ABS[10.A-10.B]) [dB] 8.69

13. BS TX Adjustment for Balanced PathLoss

a. BS TX EIRP [PBS,bal,EIRP) ][dBm] 43.32

[watt] 21.50

b. S Transmitter Output [PBS,bal,xmtr] [dBm] 34.32

[watt] 2.71

Table 3-2. Assumptions for TDMA Link Budget Analysis

Items Base (BS)Mobile(MS)

Mobile Speed [Km/hr] 100

Desired BER [%] 2.00 2.00

RX Diversity Gain [Gdiv] [dB] 4 0

Reference Thermal Noise Temperature [oK] 290 290

Channel Bandwidth [kHz] 30 30

Noise Figure [NF] 2J4 [dB] 5 7

Req'd [C/N] 2 J4 w/o RX div [dB] 18.8 17.5

Frequency Reuse Factor (N) 7 7

Attenuation slope (m) 3.50 3.50

[C/Ico], carrier to co-channel interferencepower ratio

[dB] 21.08 21.08

Table C-1 Example of TDMA Link Budgets (Three-Sector Cells)—Continued

C-6 401-200-112, Issue 11 June 2001


[C/Iadj], carrier to adjacent channel interfer-encepower ratio

[dB] 60 60

[C/Ialt], carrier to alternate channel interfer-encepower ratio

[dB] 60 60

[Nun], unexpected noise [dBm] -200 -200

Cable, Jumper and Connector Losses [Lcjc] [dB] 3.5 0

Body Loss [Lbody] [dB] 0 2

Antenna Gain [Gant] [dBi] 13 2

Maximum Transmitter Output [Pmax,xmtr] [watt] 20 0.6

TX Filter Loss [Ltx, filter] 2 BS [dB] 0.5 0

Building Penetration Loss [LBP] [dB] 0 0

Margin (slow fading, shadow, etc.) [M] [dB] 5.4 5.4

Table 3-2. Assumptions for TDMA Link Budget Analysis—Continued

Items Base (BS)Mobile(MS)

401-200-112, Issue 11 June 2001 C-7


RX diversity gain ([Gdiv], in dB) is achieved by using diversity receiving antennasto overcome deep fades. Deep fades are caused by multipaths that result whenan antenna receives multiple uncorrelated signals. Antenna diversity is used atthe BS to increase the performance of the uplink. The [Gdiv] is the difference in [C/N] to achieve an an acceptable BER with and without RX diversity. [Gdiv] isexpressed as:

For AUTOPLEX System 1000, SII-CS, the [Gdiv] is approximately 4 dB. From EQ6, the required [C/N ] at BS is expressed as:

C/N (dimensionless) is expressed as:

To achieve an acceptable BER, the following condition must be satisfied:

C/N is the calculated result, and C/N is the BER/WER performance specification;they are defined in EQ 3 and EQ 9, respectively. EQ 9 indicates that the minimumrequirement to achieve an acceptable BER/WER is C/N = C/N.

For easy manipulation, rewrite EQ 3 and EQ 4 as:

[Gdiv] = [C/N]without RX Div - [C/N]with RX Div (EQ 6)

where [C/N]with RX Div = required [C/N] at BS with RX diversity (dB)

[C/N]without RX Div = required [C/N] at BS without RX diversity(dB)

[C/N] = [C/N]without RX Div without RX diversity (EQ 7-1)

and

[C/N] = [C/N]without RX Div - [Gdiv] with RX diversity (EQ 7-2)

C/N = 10[C/N]/10 (EQ 8)

C/N > C/N at BS (EQ 9)

C-8 401-200-112, Issue 11 June 2001


(EQ 10)

and

(EQ 11)

Itot/C is determined by C/Ico, C/Iadj and C/Iatl, which are dependent on DCCHchannel assignment, frequency reuse (K), and frequency planning used.Because Itot/C, N/C, Nun and Nt are known, the minimum received carrier power Cat J4 (denoted asSmin,J4), , required to achieve an acceptable BER/WER is calculated using EQ 10as:

(EQ 12)

Smin is expressed in dBm form ([Smin]) as:

Effective antenna gain is calculated to take into account loss caused by cable,jumper, and connector for the BS, and body blocking loss for the MS. Effectiveantenna gain is expressed as:

[Smin,J4] = 10Log10 (SminJ4) (dBm) (EQ 13)

[Gant,eff] = [Gant] - [Lcfc] for BS (EQ 14-1)

and

NC----

Nt Nun+

C-----------------------

Itot

C--------+=

Itot

C--------

Ico

C------

Iadj

C--------

Ialt

C-------+ +=

SminJ4

Nt Nun+

N C⁄( ) Itot C⁄( )–--------------------------------------------=

401-200-112, Issue 11 June 2001 C-9


The minimum received signal at the RX antenna face ([Sant], in dBm) required toachieve acceptable C/N at J4 is obtained by:

[Smin] and [Gant,eff] are defined in EQ 13 and EQ 14.

C.2.4 Transmit Path

On the Transmit (TX) path, the TX EIRP is calculated using the equation below:

[Gant,eff] is defined in EQ 14, and the [Ltx,filter] is applied to BS only.

[Gant,eff] = [Gant] - [Lbody] for MS (EQ 14-2)

where: [Gant,eff] = effective antenna gain (dBi)

[Gant] = free space antenna gain (dBi)

[Lcfc] = total loss due to cable, jumper and connector (dB)

[Lbody] = loss due to human body (dB)

[Sant] = [Smin] - [Gant,eff] for BS and MS (EQ 15)

[PEIRP] = [Po,max] + [Gant,eff] - [Ltx, filter] for BS (EQ 16-1)

and

[PEIRP] = [Po,max] + [Gant,eff] for MS (EQ 16-2)

where: [PEIRP] = TX EIRP (dBm)

[Po,max] = maximum transmitter output(dBm)

[Ltx,filter] = transmit filter loss (dB)

C-10 401-200-112, Issue 11 June 2001


Margin [M] is included in the link budget analysis to account for fading andshadowing effects. The margin used is determined by the location probability ofthe MSs and the customer’s coverage area requirement, as determined bybusiness strategy. This margin is applied to both uplink and downlink.

401-200-112, Issue 11 June 2001 C-11


The allowable path loss is obtained using the following equation:

The [PEIRP] and [Sant] are defined in EQ 15 and EQ 16.

The maximum allowable path loss for the uplink is lower than that for thedownlink, as shown in Table C-1 Therefore, the transmission path is uplink-limited. The uplink path loss is considered the reference for balancing the pathloss. Balancing is achieved by lowering the BS transmit power by an amountequal to the Path Imbalance, as illustrated in Table C-2

[Lp] = [PEIRP] - [Sant] - [M] for BS and MS (EQ 17)

where: [Lp] = allowable path loss (dB)

[M] = margin (dB)

C-12 401-200-112, Issue 11 June 2001



Acronyms

AC Authentication Center

AMA Automated Message Accounting

AMPS Advanced Mobile Phone System

ARQ Automatic Radio Request

ARR Automatic Radio Reconfiguration

ASID Alphanumeric System ID(

ARQ Automatic Radio Request

ARR Automatic Radio Reconfiguration

ASID Alphanumeric System ID(

AUTH Authentication Feature

BCCH Broadcast Control Channel

BER Bit Error Rate

BS Base Station

CELL2 Form Series II Cell Site Database

CEQCOM2 Form Series II Common Equipage Form

CEQFACE Form Cell Equipage Common Face Form

CFR Centralized Flexible Rating

CGSA Form Cellular Geographic Service Area Form

Lucent Technologies— ProprietarySee notice on first page

June 2001 AC-1

401-200-112, Abbreviations and Acronyms

CMAC Control Mobile Attenuation Code

CNIP Call Number Identification Presentation

CNIR CPN Restriction

CNTG Form Cellular Network Trunk Group Form

CPN Calling Party Number

CPU Central Processing Unit

CSM Cellular System Monitor

CTG Form Cell Trunk Group Form

CTM Cell Trunk Member Form

CTM Form Cell Trunk Member Form

DCCH Digital Control Channel

DCS Digital Cellular Switch

DMAC Dynamic Mobile Attenuation Code

DN Directory Number

DPC Dynamic Power Control

DRU Digital Radio Unit

DTC Digital Traffic Channel

DTH Decision Threshold

DVCC Digital Verification Color Code

ECP Executive Cellular Processor

EDRU Enhanced Digital Radio Unit

EIRP Effective Isotropic Radiated Power

FAF Feature Activation Files

FCI Form Face Code Information Form

FDMA Frequency Division Multiple Access

FER Frame Error Rate


AC-2 December 2001AC-2 June 2001

Lucent Technologies Practices 401-200-112, Issue 11

FLCA-LM Flexible Channel Allocaton - List Monitoring

FTN Feature Transparency Network

FTN Feature Transparency Network

FWI Flash With Information

HO INT Handoff Based on Interference

HOBIT Handoff Based on Interference

IEU IS-154B Encoded Units

INLA Interference Look Ahead

INTPHT Interference Protection Handoff Threshold

IS-136 Interim Standard 136

IS-54B Interim Standard 54B

ISDN Integrated Services Digital Network

ITG Form Inter-switch Trunk Group Form

IVR Interactive Voice Response

LAC Linear Amplifier Circuit

LAF Logical Antenna Face

LDRU Local Digital Radio Unit

LED Light Emiting Diode

LTG Form Loop-around Trunk Group Form

MAHO Mobile Assisted Handoff

MC Message Center

MCN MAHO Channel Number

MCRT Maintenance Cathode Ray Tube

MOTHRESH Mobile Signal Threshold

MPDIF Mobile Power Differential

MS Mobile Station


June 2001 AC-3


MSIG Mobile Signal

MWI Message Waiting Indicator

MWO Message Waiting Order

NET Form Cellular Network Form

NVM Non-Volatile Memory

OA&M Operation, Administration and Maintenance

OMT Overhead Message Tick

PCI Protocol Bit Indicator

PIN Personal Identificatio Number

PSID Private System ID

PSTN Public Switched Telephone Network

QFAF Feature Activation File with Qualifiers

RACH Random Access Channel

RANDSSD Random Number

RC/V Recent Change/Verify

RCB Radio Control Board

RCF Radio Control Frame

RCU Radio Channel Unit

RESEL Form Reselection List for Control Channels Form

RF Radio Frequency

RMN Reach Me Number

RPG Receive Path Gain

RSID Residential System ID

RSSI Received Signal Strength Indicator

RTU Radio Test Unit

RX Receive



Lucent Technologies Practices 401-200-112, Issue 11

SAT Supervisory Audio Tone

SBI Shortened Burst Indicator

SDCC Supervisory Digital Color Code

SFF Store and Forward Functionality

SG0 Server Group 0 (inner group)

SG1 Server Group 1 (outer group)

SID System Identification Number

SMS Short Message Service

SOC System Operator Code

SPACH SMS Point-to-Point Paging and Access Response Channel

SSD Shared Secret Data

STM Short Text Message

TBIA Two Branch Inteligent Antennas

TDMA Time Division Multiple Access

TI Technician Interface

TIA Telecommunications Industry Association

TLRT RDMA Locate Reply Threshold

TRTU Test Radio Test Unit

TX Transmit

VCCF Voice Channel Confirmation Failure

V-DRU Voice Digital Radio Unit

VMAC Voice Mobile Attenuation Code

VMLA Virtual Mobile Location Area

VMLA Virtual Mobile Location Area

VMS Voice Mail System

VRF Voice Response Functionality


June 2001 AC-5


WER Word Error Rate



Documents

401-200-112